diff --git a/marked/Rel-18/38_series/38101-2/00f2e7c3d8a12df65c41a981bad8d89d_img.jpg b/marked/Rel-18/38_series/38101-2/00f2e7c3d8a12df65c41a981bad8d89d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c4eb0616acd48f5eea20c4d46c8060e338dfe225 --- /dev/null +++ b/marked/Rel-18/38_series/38101-2/00f2e7c3d8a12df65c41a981bad8d89d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be2adc3689c1f65ca7b3445909a0ab834010b66cea683973c6d61ada344eeae3 +size 42878 diff --git a/marked/Rel-18/38_series/38101-2/149f02d2530e569ed6d528bf1acc9912_img.jpg b/marked/Rel-18/38_series/38101-2/149f02d2530e569ed6d528bf1acc9912_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..220ff458b760028e56fb391b6e680cc2c1293fb0 --- /dev/null +++ b/marked/Rel-18/38_series/38101-2/149f02d2530e569ed6d528bf1acc9912_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:975f41ead11155daa8a71b90c5add4c7e6a7a84ef6498fd0a9799647a6bf8765 +size 52474 diff --git a/marked/Rel-18/38_series/38101-2/151a35d9e788ba69f2b263b91792a75d_img.jpg b/marked/Rel-18/38_series/38101-2/151a35d9e788ba69f2b263b91792a75d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc4e378a7f043d1bfa399f896235f31d1bc25277 --- /dev/null +++ b/marked/Rel-18/38_series/38101-2/151a35d9e788ba69f2b263b91792a75d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca11be579321f4fcd8a3e54974bd69c74b71fccb89bf39618e49f82e357e64a0 +size 34275 diff --git a/marked/Rel-18/38_series/38101-2/1c29dadab94c3fa552d270434db09c81_img.jpg b/marked/Rel-18/38_series/38101-2/1c29dadab94c3fa552d270434db09c81_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5e50efa251a9d69212d4f9994212bd00d0a48362 --- /dev/null +++ b/marked/Rel-18/38_series/38101-2/1c29dadab94c3fa552d270434db09c81_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e348f0366a43652667f07e2d5f2011a7ef4fda1f2bf211f01753037aa1b774ca +size 108018 diff --git a/marked/Rel-18/38_series/38101-2/25b39aa72b2c5eba0a4e8263f6e57908_img.jpg b/marked/Rel-18/38_series/38101-2/25b39aa72b2c5eba0a4e8263f6e57908_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1db912bf1bda7e9095586119d1d5e3d0bc1fbf04 --- /dev/null +++ b/marked/Rel-18/38_series/38101-2/25b39aa72b2c5eba0a4e8263f6e57908_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:949b2e81f794eaa9970112542b50e41e0e40b141d750cddbb2ea1b48ee00e4bd +size 29001 diff --git a/marked/Rel-18/38_series/38101-2/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-18/38_series/38101-2/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ad1bb2d85d0b21a9dcd62af1339c227e5565f74 --- /dev/null +++ b/marked/Rel-18/38_series/38101-2/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5afe6eaee27d16e1011c3a60c6e92e6c341fabe9cf4278758479ff231655c97a +size 26565 diff --git a/marked/Rel-18/38_series/38101-2/303fadfb9def251d1575d6221199b158_img.jpg b/marked/Rel-18/38_series/38101-2/303fadfb9def251d1575d6221199b158_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0cbd909347523827b78b0fcccedb11a4fbccdf0c --- /dev/null +++ b/marked/Rel-18/38_series/38101-2/303fadfb9def251d1575d6221199b158_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d39fc07cca6ec9ea873cf9580ae2df1284dedd81f74d0ec66ac832d64c5b372 +size 66468 diff --git a/marked/Rel-18/38_series/38101-2/3216c311c376930b9cb661d4ee835732_img.jpg b/marked/Rel-18/38_series/38101-2/3216c311c376930b9cb661d4ee835732_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b59107ca4816216df0ef2ca15aede54017a687b1 --- /dev/null +++ b/marked/Rel-18/38_series/38101-2/3216c311c376930b9cb661d4ee835732_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dc1e36f4eb64ca72194e512468ec14f95a439c86a85f9caf8ceb8440f08bea6d +size 49332 diff --git a/marked/Rel-18/38_series/38101-2/475c496c4cd20198211aeaa241af7279_img.jpg b/marked/Rel-18/38_series/38101-2/475c496c4cd20198211aeaa241af7279_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b73c6e71550fc68de776133f0cc1f933bbf0cee --- /dev/null +++ b/marked/Rel-18/38_series/38101-2/475c496c4cd20198211aeaa241af7279_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec3215e7cc9085553c7cbc01df8e3be6f35c23924c15d99c0aae3efd9dfdf971 +size 38296 diff --git a/marked/Rel-18/38_series/38101-2/4e99a3206cef1efe25cda57727183aa6_img.jpg b/marked/Rel-18/38_series/38101-2/4e99a3206cef1efe25cda57727183aa6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36e030a1621d36063b95ec8038803d3a6864f262 --- /dev/null +++ b/marked/Rel-18/38_series/38101-2/4e99a3206cef1efe25cda57727183aa6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7993f736140aa06e2ae1965fd8bd0a1ba33176afeb225432e620dfc6f63cbb03 +size 23717 diff --git a/marked/Rel-18/38_series/38101-2/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38101-2/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f339ccb6fd74604734fd856283b73cb83e7a4058 --- /dev/null +++ b/marked/Rel-18/38_series/38101-2/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da559110e1d31462cb473718c098818a2059358dbd1a28653987d6c8dc3e7612 +size 9537 diff --git a/marked/Rel-18/38_series/38101-2/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38101-2/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c15aa753ebf109916c77afeaef3bf8953e67c937 --- /dev/null +++ b/marked/Rel-18/38_series/38101-2/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf25dabea25c1d1be3baac539960bbe81f03d3485790d6e6c2ab4c72bae74323 +size 5520 diff --git a/marked/Rel-18/38_series/38101-2/6bd84b6e2e96b0d1193956b5a04b0e69_img.jpg b/marked/Rel-18/38_series/38101-2/6bd84b6e2e96b0d1193956b5a04b0e69_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac55bafa69c33cb9113a3df5a5e9ff80edeead19 --- /dev/null +++ b/marked/Rel-18/38_series/38101-2/6bd84b6e2e96b0d1193956b5a04b0e69_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:53ebb9531372fc941a5c239a39621a786943ddead92da23423cbae62ea9c9c74 +size 65736 diff --git a/marked/Rel-18/38_series/38101-2/6d7be4b2b402e079f97685869580c864_img.jpg b/marked/Rel-18/38_series/38101-2/6d7be4b2b402e079f97685869580c864_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc9c5bdca36d54e85e554fec1849c936b24f19c3 --- /dev/null +++ b/marked/Rel-18/38_series/38101-2/6d7be4b2b402e079f97685869580c864_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:81e618ef30ca1747c23a9510b5d5d93e78447e97584eeccfb7dfe09eca6b1580 +size 45666 diff --git a/marked/Rel-18/38_series/38101-2/748eb98c2d6720f0985fddd1764fa9a1_img.jpg b/marked/Rel-18/38_series/38101-2/748eb98c2d6720f0985fddd1764fa9a1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..063870f7a3e7b130ad24d04baae66944d880b66b --- /dev/null +++ b/marked/Rel-18/38_series/38101-2/748eb98c2d6720f0985fddd1764fa9a1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:360a67eb3caa4b4647d62d398e2d688e5b3647ed5b64c1cd3cb567e020ef54f2 +size 51568 diff --git a/marked/Rel-18/38_series/38101-2/790b3d1f6fbe3b4570cf1eec24db67f0_img.jpg b/marked/Rel-18/38_series/38101-2/790b3d1f6fbe3b4570cf1eec24db67f0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c5e883b8b4c21b58795d14a1ef83a95a3a0a6a9 --- /dev/null +++ b/marked/Rel-18/38_series/38101-2/790b3d1f6fbe3b4570cf1eec24db67f0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cdb56f90dd276c64abc42ce681a132e017910660bbb0ac072efde588ad98900e +size 35202 diff --git a/marked/Rel-18/38_series/38101-2/89d2e4c002294cf6ffee801e84670cc5_img.jpg b/marked/Rel-18/38_series/38101-2/89d2e4c002294cf6ffee801e84670cc5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..816a132b4fb394feb03eff86d6da2517ce855bd0 --- /dev/null +++ b/marked/Rel-18/38_series/38101-2/89d2e4c002294cf6ffee801e84670cc5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:38ac7f1837d8d4c3ce619446d3d7b580cfabe06bc09b02299b46e6c7a366fbff +size 32087 diff --git a/marked/Rel-18/38_series/38101-2/8be2969598fb65f80907b8bbc140a98f_img.jpg b/marked/Rel-18/38_series/38101-2/8be2969598fb65f80907b8bbc140a98f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e7935ece3bb958d8c289120ec9c4b3d9f9c36b43 --- /dev/null +++ b/marked/Rel-18/38_series/38101-2/8be2969598fb65f80907b8bbc140a98f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83568e3799c0c600b9e4889c48988e8ad2865b512fe020d877bf00ccde59c5ea +size 17834 diff --git a/marked/Rel-18/38_series/38101-2/931c81c99d2b5ece0876279fc1f38e42_img.jpg b/marked/Rel-18/38_series/38101-2/931c81c99d2b5ece0876279fc1f38e42_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..19645bdf34377a709df882f600dfed81dd7ffc9d --- /dev/null +++ b/marked/Rel-18/38_series/38101-2/931c81c99d2b5ece0876279fc1f38e42_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da148cdf582c320580b5c4c6e4df5ae0f8595c2e59fbc20bc37d8018b8aed918 +size 50034 diff --git a/marked/Rel-18/38_series/38101-2/9ce14e3b4651237e346d641e58e46fbc_img.jpg b/marked/Rel-18/38_series/38101-2/9ce14e3b4651237e346d641e58e46fbc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e5952087a0d8a5f5c2c4de8597fde88f70796f6f --- /dev/null +++ b/marked/Rel-18/38_series/38101-2/9ce14e3b4651237e346d641e58e46fbc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:77b2f9078d869134dd7aa8d09d39ad7175b74f02041f63e55610eb1c10fd7870 +size 69946 diff --git a/marked/Rel-18/38_series/38101-2/9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg b/marked/Rel-18/38_series/38101-2/9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0edad10f155833ab62a86b0d4cbf4b98af562f98 --- /dev/null +++ b/marked/Rel-18/38_series/38101-2/9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ef03fea63098b22621ae97c1967a758c4705f8e2d58c90c6d31f8a3d7798ebf +size 77277 diff --git a/marked/Rel-18/38_series/38101-2/a2266c471758a61aa9eeab6aab8696b4_img.jpg b/marked/Rel-18/38_series/38101-2/a2266c471758a61aa9eeab6aab8696b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4476869b52e2c7587fdb079e38439a0678ac93c1 --- /dev/null +++ b/marked/Rel-18/38_series/38101-2/a2266c471758a61aa9eeab6aab8696b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd1ca3e98a7691a1403e5db35bb15c4008144ebe20810f49b2e20477e7d88eb5 +size 38334 diff --git a/marked/Rel-18/38_series/38101-2/a25c41b4f7f77363ac12ee931fafe4c7_img.jpg b/marked/Rel-18/38_series/38101-2/a25c41b4f7f77363ac12ee931fafe4c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4086f67e96abf44ee20151d2bed92f69d2dc29e1 --- /dev/null +++ b/marked/Rel-18/38_series/38101-2/a25c41b4f7f77363ac12ee931fafe4c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0de27b268dc0bbb0b8575bcd930aade76ea0b0c6e627d8edc101876390aa5f60 +size 38337 diff --git a/marked/Rel-18/38_series/38101-2/a26216bbf0eaad4cdde1d3ea2f35b28e_img.jpg b/marked/Rel-18/38_series/38101-2/a26216bbf0eaad4cdde1d3ea2f35b28e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b5678e2a88783635bb25b3ea04d25e564a6a62c2 --- /dev/null +++ b/marked/Rel-18/38_series/38101-2/a26216bbf0eaad4cdde1d3ea2f35b28e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aaaa13348af118a66aaa4d8548bb6190ed8496701dfa020b091477b90546247d +size 15350 diff --git a/marked/Rel-18/38_series/38101-2/a4495e80db9a7e1a890da12eb8c07360_img.jpg b/marked/Rel-18/38_series/38101-2/a4495e80db9a7e1a890da12eb8c07360_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f5dcec8d20ddfd9dbdc03cb99c003a6b80258260 --- /dev/null +++ b/marked/Rel-18/38_series/38101-2/a4495e80db9a7e1a890da12eb8c07360_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e600309e0cd174dcd66e74681ebee1f3c5b3c386023d067fe26d942af1251524 +size 56777 diff --git a/marked/Rel-18/38_series/38101-2/a9a53dc4da40325b14b9ad309f317f66_img.jpg b/marked/Rel-18/38_series/38101-2/a9a53dc4da40325b14b9ad309f317f66_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7c5510f9f1c87dcf1156b6028dd40d1c690f80c --- /dev/null +++ b/marked/Rel-18/38_series/38101-2/a9a53dc4da40325b14b9ad309f317f66_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4e3fd41aff2ee4068d74b6a0e84309bd2415d10898aad2793e841dbcc9fdac6 +size 15775 diff --git a/marked/Rel-18/38_series/38101-2/cf648eab639f63a505727a234d0748d1_img.jpg b/marked/Rel-18/38_series/38101-2/cf648eab639f63a505727a234d0748d1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9ee496dda1c9f513c0fb9aed91e903e045e0f64a --- /dev/null +++ b/marked/Rel-18/38_series/38101-2/cf648eab639f63a505727a234d0748d1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5cb999a0a4ac763f89e5ad7e136a545e7ebf79b951ec30a1e33f9db8466a59c1 +size 38353 diff --git a/marked/Rel-18/38_series/38101-2/da2b6f6fb4881c57f687aaf79226e788_img.jpg b/marked/Rel-18/38_series/38101-2/da2b6f6fb4881c57f687aaf79226e788_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0da392bcdfc0dabebee8217b834bc30c482da8f --- /dev/null +++ b/marked/Rel-18/38_series/38101-2/da2b6f6fb4881c57f687aaf79226e788_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1c44c0ed6fb14c08fde7bda37c22719939b6a49328d48fa412761ee98c2eae55 +size 14034 diff --git a/marked/Rel-18/38_series/38101-2/e29665b8abcea967ef289c6aff07ae4c_img.jpg b/marked/Rel-18/38_series/38101-2/e29665b8abcea967ef289c6aff07ae4c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b939035fcf275c3ca75fab0a98c6293e94d38836 --- /dev/null +++ b/marked/Rel-18/38_series/38101-2/e29665b8abcea967ef289c6aff07ae4c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:880208c5a97f78c17915253b709198026271d8a66118b011b8c53cdf08005ff2 +size 28902 diff --git a/marked/Rel-18/38_series/38101-2/e84508be9dbee463632f183989ce79f9_img.jpg b/marked/Rel-18/38_series/38101-2/e84508be9dbee463632f183989ce79f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..531a9140aca2fb5a3ab29e3d4cb65397cfff6e24 --- /dev/null +++ b/marked/Rel-18/38_series/38101-2/e84508be9dbee463632f183989ce79f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c1b9656aff642bfe36deb1f34ed018943a593701b2acdb750018ea3405ff2e03 +size 31456 diff --git a/marked/Rel-18/38_series/38101-2/raw.md b/marked/Rel-18/38_series/38101-2/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..297664caf8cdacd40c6445bda1d4df4432e3785b --- /dev/null +++ b/marked/Rel-18/38_series/38101-2/raw.md @@ -0,0 +1,9218 @@ + + +# 3GPP TS 38.101-2 V18.4.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; User Equipment (UE) radio transmission and reception; Part 2: Range 2 Standalone (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 letter 'G', and the word 'ADVANCED' in smaller text to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|-----------------------------------------------------------------------------------------------|----| +| Foreword..... | 22 | +| 1 Scope..... | 24 | +| 2 References..... | 24 | +| 3 Definitions, symbols and abbreviations..... | 25 | +| 3.1 Definitions..... | 25 | +| 3.2 Symbols..... | 26 | +| 3.3 Abbreviations..... | 28 | +| 4 General..... | 30 | +| 4.1 Relationship between minimum requirements and test requirements..... | 30 | +| 4.2 Applicability of minimum requirements..... | 30 | +| 4.3 Specification suffix information..... | 30 | +| 5 Operating bands and channel arrangement..... | 32 | +| 5.1 General..... | 32 | +| 5.2 Operating bands..... | 32 | +| 5.2A Operating bands for CA..... | 32 | +| 5.2A.1 Intra-band CA..... | 32 | +| 5.2A.2 Inter-band CA..... | 33 | +| 5.2D Operating bands for UL MIMO..... | 33 | +| 5.2K Operating bands for simultaneous reception or transmission in multiple directions..... | 33 | +| 5.3 UE Channel bandwidth..... | 34 | +| 5.3.1 General..... | 34 | +| 5.3.2 Maximum transmission bandwidth configuration..... | 34 | +| 5.3.3 Minimum guardband and transmission bandwidth configuration..... | 35 | +| 5.3.4 RB alignment..... | 36 | +| 5.3A UE channel bandwidth for CA..... | 37 | +| 5.3A.1 General..... | 37 | +| 5.3A.2 Minimum guardband and transmission bandwidth configuration for CA..... | 37 | +| 5.3A.3 RB alignment with different numerologies for CA..... | 39 | +| 5.3A.4 UE channel bandwidth per operating band for CA..... | 39 | +| 5.3D Channel bandwidth for UL MIMO..... | 41 | +| 5.3K Channel bandwidth for simultaneous reception or transmission in multiple directions..... | 41 | +| 5.4 Channel arrangement..... | 41 | +| 5.4.1 Channel spacing..... | 41 | +| 5.4.1.1 Channel spacing for adjacent NR carriers..... | 41 | +| 5.4.2 Channel raster..... | 42 | +| 5.4.2.1 NR-ARFCN and channel raster..... | 42 | +| 5.4.2.2 Channel raster to resource element mapping..... | 42 | +| 5.4.2.3 Channel raster entries for each operating band..... | 43 | +| 5.4.3 Synchronization raster..... | 43 | +| 5.4.3.1 Synchronization raster and numbering..... | 43 | +| 5.4.3.2 Synchronization raster to synchronization block resource element mapping..... | 44 | +| 5.4.3.3 Synchronization raster entries for each operating band..... | 44 | +| 5.4A Channel arrangement for CA..... | 44 | +| 5.4A.1 Channel spacing for CA..... | 44 | +| 5.5 Configurations..... | 46 | +| 5.5A Configurations for CA..... | 46 | +| 5.5A.1 Configurations for intra-band contiguous CA..... | 46 | +| 5.5A.2 Configurations for intra-band non-contiguous CA..... | 52 | +| 5.5A.3 Configurations for inter-band CA..... | 61 | +| 5.5D Configurations for UL MIMO..... | 66 | +| 5.5K Configurations for simultaneous reception or transmission in multiple directions..... | 66 | +| 6 Transmitter characteristics..... | 67 | +| 6.1 General..... | 67 | +| 6.2 Transmitter power..... | 67 | + +| | | | +|------------|---------------------------------------------------------------------------------------|----| +| 6.2.1 | UE maximum output power..... | 67 | +| 6.2.1.0 | General..... | 67 | +| 6.2.1.1 | UE maximum output power for power class 1..... | 67 | +| 6.2.1.2 | UE maximum output power for power class 2..... | 68 | +| 6.2.1.3 | UE maximum output power for power class 3..... | 69 | +| 6.2.1.4 | UE maximum output power for power class 4..... | 71 | +| 6.2.1.5 | UE maximum output power for power class 5..... | 72 | +| 6.2.1.6 | UE maximum output power for power class 6..... | 73 | +| 6.2.1.7 | UE maximum output power for power class 7..... | 74 | +| 6.2.2 | UE maximum output power reduction..... | 75 | +| 6.2.2.0 | General..... | 75 | +| 6.2.2.1 | UE maximum output power reduction for power class 1..... | 75 | +| 6.2.2.2 | UE maximum output power reduction for power class 2..... | 77 | +| 6.2.2.3 | UE maximum output power reduction for power class 3..... | 78 | +| 6.2.2.4 | UE maximum output power reduction for power class 4..... | 80 | +| 6.2.2.5 | UE maximum output power reduction for power class 5..... | 80 | +| 6.2.2.6 | UE maximum output power reduction for power class 6..... | 80 | +| 6.2.2.7 | UE maximum output power reduction for power class 7..... | 80 | +| 6.2.3 | UE maximum output power with additional requirements..... | 80 | +| 6.2.3.1 | General..... | 80 | +| 6.2.3.2 | Void..... | 81 | +| 6.2.3.2.1 | Void..... | 81 | +| 6.2.3.2.2 | Void..... | 81 | +| 6.2.3.2.3 | Void..... | 81 | +| 6.2.3.2.4 | Void..... | 82 | +| 6.2.3.2.5 | Void..... | 82 | +| 6.2.3.3 | A-MPR for NS_202..... | 82 | +| 6.2.3.3.1 | A-MPR for NS_202 for power class 1..... | 82 | +| 6.2.3.3.2 | A-MPR for NS_202 for power class 2..... | 82 | +| 6.2.3.3.3 | A-MPR for NS_202 for power class 3..... | 82 | +| 6.2.3.3.4 | A-MPR for NS_202 for power class 4..... | 82 | +| 6.2.3.3.5 | A-MPR for NS_202 for power class 5..... | 82 | +| 6.2.3.3.6 | A-MPR for NS_202 for power class 6..... | 82 | +| 6.2.3.3.7 | A-MPR for NS_202 for power class 7..... | 82 | +| 6.2.3.4 | A-MPR for NS_203..... | 82 | +| 6.2.3.4.1 | A-MPR for NS_203 for power class 1..... | 82 | +| 6.2.3.4.2 | A-MPR for NS_203 for power class 2..... | 82 | +| 6.2.3.4.3 | A-MPR for NS_203 for power class 3..... | 82 | +| 6.2.3.4.4 | A-MPR for NS_203 for power class 4..... | 82 | +| 6.2.3.4.5 | A-MPR for NS_203 for power class 5..... | 83 | +| 6.2.3.4.6 | A-MPR for NS_203 for power class 6..... | 83 | +| 6.2.3.4.7 | A-MPR for NS_203 for power class 7..... | 83 | +| 6.2.4 | Configured transmitted power..... | 83 | +| 6.2.5 | Requirements for UL gap ( ul-GapFR2-r17 ) for TX power management..... | 84 | +| 6.2A | Transmitter power for CA..... | 85 | +| 6.2A.1 | UE maximum output power for CA..... | 85 | +| 6.2A.2 | UE maximum output power reduction for CA..... | 86 | +| 6.2A.2.1 | General..... | 86 | +| 6.2A.2.2 | Maximum output power reduction for power class 1..... | 86 | +| 6.2A.2.2.1 | Maximum output power reduction for power class 1 intra-band contiguous UL CA..... | 86 | +| 6.2A.2.2.2 | Maximum output power reduction for power class 1 intra-band non-contiguous UL CA..... | 88 | +| 6.2A.2.2.3 | Maximum output power reduction for power class 1 inter-band CA..... | 88 | +| 6.2A.2.3 | Maximum output power reduction for power class 2..... | 89 | +| 6.2A.2.4 | Maximum output power reduction for power class 3..... | 90 | +| 6.2A.2.4.1 | Maximum output power reduction for power class 3 intra-band contiguous CA..... | 90 | +| 6.2A.2.4.2 | Maximum output power reduction for power class 3 intra-band non-contiguous CA..... | 91 | +| 6.2A.2.4.3 | Maximum output power reduction for power class 3 inter-band CA..... | 92 | +| 6.2A.2.5 | Maximum output power reduction for power class 4..... | 92 | +| 6.2A.2.6 | Maximum output power reduction for power class 5..... | 92 | +| 6.2A.2.7 | Maximum output power reduction for power class 6..... | 93 | +| 6.2A.3 | UE maximum output power with additional requirements for CA..... | 93 | + +| | | | +|------------|---------------------------------------------------------------------------------------------------------|-----| +| 6.2A.3.1 | General..... | 93 | +| 6.2A.3.2 | Void..... | 94 | +| 6.2A.3.2.1 | Void..... | 94 | +| 6.2A.3.2.2 | Void..... | 94 | +| 6.2A.3.2.3 | Void..... | 94 | +| 6.2A.3.2.4 | Void..... | 94 | +| 6.2A.3.2.5 | Void..... | 94 | +| 6.2A.3.3 | A-MPR for CA_NS_202..... | 94 | +| 6.2A.3.3.1 | A-MPR for CA_NS_202 for power class 1..... | 94 | +| 6.2A.3.3.2 | A-MPR for CA_NS_202 for power class 2..... | 94 | +| 6.2A.3.3.3 | A-MPR for CA_NS_202 for power class 3..... | 94 | +| 6.2A.3.3.4 | A-MPR for CA_NS_202 for power class 4..... | 94 | +| 6.2A.3.3.5 | A-MPR for CA_NS_202 for power class 5..... | 94 | +| 6.2A.3.3.6 | A-MPR for CA_NS_202 for power class 6..... | 94 | +| 6.2A.3.4 | A-MPR for CA_NS_203..... | 94 | +| 6.2A.3.4.1 | A-MPR for CA_NS_203 for power class 1..... | 94 | +| 6.2A.3.4.2 | A-MPR for CA_NS_203 for power class 2..... | 94 | +| 6.2A.3.4.3 | A-MPR for CA_NS_203 for power class 3..... | 95 | +| 6.2A.3.4.4 | A-MPR for CA_NS_203 for power class 4..... | 95 | +| 6.2A.3.4.5 | A-MPR for CA_NS_203 for power class 5..... | 95 | +| 6.2A.3.4.6 | A-MPR for CA_NS_203 for power class 6..... | 95 | +| 6.2A.4 | Configured transmitted power for CA..... | 95 | +| 6.2A.4.1 | Configured transmitted power for intra-band UL CA..... | 95 | +| 6.2A.4.2 | Configured transmitted power for inter-band UL CA..... | 96 | +| 6.2A.5 | Requirements for UL gap ( ul-GapFR2-r17 ) for TX power management in CA..... | 97 | +| 6.2D | Transmitter power for UL MIMO..... | 97 | +| 6.2D.1 | UE maximum output power for UL MIMO..... | 97 | +| 6.2D.1.0 | General..... | 97 | +| 6.2D.1.1 | UE maximum output power for UL MIMO for power class 1..... | 98 | +| 6.2D.1.2 | UE maximum output power for UL MIMO for power class 2..... | 99 | +| 6.2D.1.3 | UE maximum output power for UL MIMO for power class 3..... | 100 | +| 6.2D.1.4 | UE maximum output power for UL MIMO for power class 4..... | 101 | +| 6.2D.1.5 | UE maximum output power for UL MIMO for power class 5..... | 102 | +| 6.2D.1.6 | UE maximum output power for UL MIMO for power class 6..... | 102 | +| 6.2D.2 | UE maximum output power reduction for modulation / channel bandwidth for UL MIMO..... | 103 | +| 6.2D.2.1 | UE maximum output power reduction for modulation / channel bandwidth for UL MIMO for power class 1..... | 103 | +| 6.2D.2.2 | UE maximum output power reduction for modulation / channel bandwidth for UL MIMO for power class 2..... | 104 | +| 6.2D.2.3 | UE maximum output power reduction for modulation / channel bandwidth for UL MIMO for power class 3..... | 104 | +| 6.2D.2.4 | UE maximum output power reduction for modulation / channel bandwidth for UL MIMO for power class 4..... | 104 | +| 6.2D.2.5 | UE maximum output power reduction for modulation / channel bandwidth for UL MIMO for power class 5..... | 104 | +| 6.2D.2.6 | UE maximum output power reduction for modulation / channel bandwidth for UL MIMO for power class 6..... | 104 | +| 6.2D.3 | UE maximum output power reduction with additional requirements for UL MIMO..... | 104 | +| 6.2D.3.1 | UE maximum output power reduction with additional requirements for UL MIMO for power class 1..... | 104 | +| 6.2D.3.2 | UE maximum output power reduction with additional requirements for UL MIMO for power class 2..... | 105 | +| 6.2D.3.3 | UE maximum output power reduction with additional requirements for UL MIMO for power class 3..... | 105 | +| 6.2D.3.4 | UE maximum output power reduction with additional requirements for UL MIMO for power class 4..... | 105 | +| 6.2D.3.5 | UE maximum output power reduction with additional requirements for UL MIMO for power class 5..... | 105 | +| 6.2D.3.6 | UE maximum output power reduction with additional requirements for UL MIMO for power class 6..... | 105 | +| 6.2D.4 | Configured transmitted power for UL MIMO..... | 105 | + +| | | | +|-----------|---------------------------------------------------------------------------------------------------------------------------|-----| +| 6.2K | Transmitter power for simultaneous transmission to multiple directions..... | 105 | +| 6.2K.1 | UE maximum output power for simultaneous transmission to multiple directions..... | 105 | +| 6.2K.2 | UE maximum output power reduction for simultaneous transmission to multiple directions..... | 106 | +| 6.2K.3 | UE maximum output power with additional requirements for simultaneous transmission to multiple directions..... | 106 | +| 6.2K.4 | Configured transmitted power for simultaneous transmission to multiple directions..... | 106 | +| 6.3 | Output power dynamics..... | 107 | +| 6.3.1 | Minimum output power..... | 107 | +| 6.3.1.0 | General..... | 107 | +| 6.3.1.1 | Minimum output power for power class 1..... | 107 | +| 6.3.1.2 | Minimum output power for power class 2, 3, and 4..... | 107 | +| 6.3.1.3 | Minimum output power for power class 5 and 6..... | 108 | +| 6.3.1.4 | Minimum output power for power class 7..... | 108 | +| 6.3.2 | Transmit OFF power..... | 108 | +| 6.3.3 | Transmit ON/OFF time mask..... | 109 | +| 6.3.3.1 | General..... | 109 | +| 6.3.3.2 | General ON/OFF time mask..... | 109 | +| 6.3.3.3 | Transmit power time mask for slot and short or long subslot boundaries..... | 109 | +| 6.3.3.4 | PRACH time mask..... | 110 | +| 6.3.3.5 | Void..... | 112 | +| 6.3.3.6 | SRS time mask..... | 112 | +| 6.3.3.7 | PUSCH-PUCCH and PUSCH-SRS time masks..... | 113 | +| 6.3.3.8 | Transmit power time mask for consecutive slot or long subslot transmission and short subslot transmission boundaries..... | 113 | +| 6.3.3.9 | Transmit power time mask for consecutive short subslot transmissions boundaries..... | 114 | +| 6.3.4 | Power control..... | 115 | +| 6.3.4.1 | General..... | 115 | +| 6.3.4.2 | Absolute power tolerance..... | 115 | +| 6.3.4.3 | Relative power tolerance..... | 115 | +| 6.3.4.4 | Aggregate power tolerance..... | 116 | +| 6.3A | Output power dynamics for CA..... | 116 | +| 6.3A.1 | Minimum output power for CA..... | 116 | +| 6.3A.1.0 | General..... | 116 | +| 6.3A.1.1 | Minimum output power for power class 1..... | 117 | +| 6.3A.1.2 | Minimum output power for power class 2, 3, and 4..... | 117 | +| 6.3A.1.3 | Minimum output power for power class 5 and 6..... | 118 | +| 6.3A.2 | Transmit OFF power for CA..... | 118 | +| 6.3A.3 | Transmit ON/OFF time mask for CA..... | 118 | +| 6.3A.4 | Power control for CA..... | 119 | +| 6.3A.4.1 | General..... | 119 | +| 6.3D | Output power dynamics for UL MIMO..... | 120 | +| 6.3D.0 | General..... | 120 | +| 6.3D.1 | Minimum output power for UL MIMO..... | 120 | +| 6.3D.1.0 | General..... | 120 | +| 6.3D.1.1 | Minimum output power for UL MIMO for power class 1..... | 120 | +| 6.3D.1.2 | Minimum output power for UL MIMO for power class 2, 3 and 4..... | 120 | +| 6.3D.1.3 | Minimum output power for UL MIMO for power class 5 and 6..... | 120 | +| 6.3D.2 | Transmit OFF power for UL MIMO..... | 120 | +| 6.3D.3 | Transmit ON/OFF time mask for UL MIMO..... | 120 | +| 6.4 | Transmit signal quality..... | 121 | +| 6.4.1 | Frequency Error..... | 121 | +| 6.4.2 | Transmit modulation quality..... | 121 | +| 6.4.2.0 | General..... | 121 | +| 6.4.2.1 | Error vector magnitude..... | 121 | +| 6.4.2.2 | Carrier leakage..... | 123 | +| 6.4.2.2.1 | General..... | 123 | +| 6.4.2.2.2 | Carrier leakage for power class 1..... | 123 | +| 6.4.2.2.3 | Carrier leakage for power class 2..... | 123 | +| 6.4.2.2.4 | Carrier leakage for power class 3..... | 124 | +| 6.4.2.2.5 | Carrier leakage for power class 4..... | 124 | +| 6.4.2.2.6 | Carrier leakage for power class 5..... | 124 | + +| | | | +|------------|-----------------------------------------------------------|-----| +| 6.4.2.2.7 | Carrier leakage for power class 6..... | 124 | +| 6.4.2.2.8 | Carrier leakage for power class 7..... | 124 | +| 6.4.2.3 | In-band emissions..... | 125 | +| 6.4.2.3.1 | General..... | 125 | +| 6.4.2.3.2 | In-band emissions for power class 1..... | 125 | +| 6.4.2.3.3 | In-band emissions for power class 2..... | 126 | +| 6.4.2.3.4 | In-band emissions for power class 3..... | 127 | +| 6.4.2.3.5 | In-band emissions for power class 4..... | 128 | +| 6.4.2.3.6 | In-band emissions for power class 5..... | 129 | +| 6.4.2.3.7 | In-band emissions for power class 6..... | 130 | +| 6.4.2.3.8 | In-band emissions for power class 7..... | 130 | +| 6.4.2.4 | EVM equalizer spectrum flatness..... | 130 | +| 6.4.2.5 | EVM spectral flatness for Pi/2 BPSK modulation..... | 131 | +| 6.4.2.6 | Phase continuity requirements for DMRS bundling..... | 132 | +| 6.4A | Transmit signal quality for CA..... | 133 | +| 6.4A.0 | General..... | 133 | +| 6.4A.1 | Frequency error..... | 134 | +| 6.4A.2 | Transmit modulation quality..... | 134 | +| 6.4A.2.0 | General..... | 134 | +| 6.4A.2.1 | Error Vector magnitude..... | 134 | +| 6.4A.2.2 | Carrier leakage..... | 134 | +| 6.4A.2.2.1 | General..... | 134 | +| 6.4A.2.2.2 | Carrier leakage for power class 1..... | 135 | +| 6.4A.2.2.3 | Carrier leakage for power class 2..... | 135 | +| 6.4A.2.2.4 | Carrier leakage for power class 3..... | 135 | +| 6.4A.2.2.5 | Carrier leakage for power class 4..... | 136 | +| 6.4A.2.2.6 | Carrier leakage for power class 5..... | 136 | +| 6.4A.2.2.7 | Carrier leakage for power class 6..... | 136 | +| 6.4A.2.3 | Inband emissions..... | 137 | +| 6.4A.2.3.1 | General..... | 137 | +| 6.4A.2.3.2 | Inband emissions for power class 1..... | 137 | +| 6.4A.2.3.3 | Inband emissions for power class 2..... | 138 | +| 6.4A.2.3.4 | Inband emissions for power class 3..... | 139 | +| 6.4A.2.3.5 | Inband emissions for power class 4..... | 140 | +| 6.4A.2.3.6 | Inband emissions for power class 5..... | 141 | +| 6.4A.2.3.7 | Inband emissions for power class 6..... | 142 | +| 6.4A.2.4 | EVM equalizer spectrum flatness..... | 142 | +| 6.4D | Transmit signal quality for UL MIMO..... | 142 | +| 6.4D.0 | General..... | 142 | +| 6.4D.1 | Frequency error for UL MIMO..... | 142 | +| 6.4D.2 | Transmit modulation quality for UL MIMO..... | 143 | +| 6.4D.3 | Time alignment error for UL MIMO..... | 143 | +| 6.4D.4 | Requirements for coherent UL MIMO..... | 143 | +| 6.5 | Output RF spectrum emissions..... | 144 | +| 6.5.1 | Occupied bandwidth..... | 144 | +| 6.5.2 | Out of band emissions..... | 144 | +| 6.5.2.0 | General..... | 144 | +| 6.5.2.1 | Spectrum emission mask..... | 144 | +| 6.5.2.2 | Void..... | 145 | +| 6.5.2.3 | Adjacent channel leakage ratio..... | 145 | +| 6.5.3 | Spurious emissions..... | 146 | +| 6.5.3.1 | Spurious emission band UE co-existence..... | 146 | +| 6.5.3.2 | Additional spurious emissions..... | 147 | +| 6.5.3.2.1 | General..... | 147 | +| 6.5.3.2.2 | Void..... | 148 | +| 6.5.3.2.3 | Additional spurious emission requirements for NS_202..... | 148 | +| 6.5.3.2.4 | Additional spurious emission requirements for NS_203..... | 148 | +| 6.5.3.2.5 | Additional spurious emission requirements for NS_204..... | 148 | +| 6.5A | Output RF spectrum emissions for CA..... | 149 | +| 6.5A.1 | Occupied bandwidth for CA..... | 149 | +| 6.5A.1.0 | General..... | 149 | + +| | | | +|------------|---------------------------------------------------------------------------------------------|-----| +| 6.5A.1.1 | Occupied bandwidth for intra-band contiguous UL CA..... | 149 | +| 6.5A.1.2 | Occupied bandwidth for intra-band non-contiguous UL CA..... | 149 | +| 6.5A.1.3 | Occupied bandwidth for inter-band UL CA..... | 149 | +| 6.5A.2 | Out of band emissions..... | 149 | +| 6.5A.2.1 | Spectrum emission mask for CA..... | 149 | +| 6.5A.2.1.0 | General..... | 149 | +| 6.5A.2.1.1 | Spectrum emission mask for intra-band contiguous UL CA..... | 149 | +| 6.5A.2.1.2 | Spectrum emission mask for intra-band non-contiguous UL CA..... | 150 | +| 6.5A.2.1.3 | Spectrum emission mask for inter-band UL CA..... | 150 | +| 6.5A.2.2 | Void..... | 150 | +| 6.5A.2.3 | Adjacent channel leakage ratio for CA..... | 150 | +| 6.5A.2.3.1 | Adjacent channel leakage ratio for CA intra-band contiguous UL CA..... | 150 | +| 6.5A.2.3.2 | Adjacent channel leakage ratio for CA intra-band non-contiguous UL CA..... | 151 | +| 6.5A.2.3.3 | Adjacent channel leakage ratio for CA inter-band UL CA..... | 151 | +| 6.5A.3 | Spurious emissions for CA..... | 151 | +| 6.5A.3.0 | General spurious emissions for CA..... | 151 | +| 6.5A.3.0.0 | General..... | 151 | +| 6.5A.3.0.1 | Spurious emissions for intra-band contiguous UL CA..... | 152 | +| 6.5A.3.0.2 | Spurious emissions for intra-band non-contiguous UL CA..... | 152 | +| 6.5A.3.0.3 | Spurious emissions for inter-band UL CA..... | 152 | +| 6.5A.3.1 | Spurious emission band UE co-existence for UL CA..... | 152 | +| 6.5A.3.2 | Additional spurious emissions..... | 153 | +| 6.5A.3.2.1 | General..... | 153 | +| 6.5A.3.2.2 | Void..... | 153 | +| 6.5A.3.2.3 | Additional spurious emission requirements for CA_NS_202..... | 153 | +| 6.5A.3.2.4 | Additional spurious emission requirements for CA_NS_203..... | 153 | +| 6.5D | Output RF spectrum emissions for UL MIMO..... | 154 | +| 6.5D.1 | Occupied bandwidth for UL MIMO..... | 154 | +| 6.5D.2 | Out of band emissions for UL MIMO..... | 154 | +| 6.5D.3 | Spurious emissions for UL MIMO..... | 154 | +| 6.6 | Beam correspondence..... | 154 | +| 6.6.1 | General..... | 154 | +| 6.6.2 | (Void)..... | 154 | +| 6.6.3 | (Void)..... | 154 | +| 6.6.4 | Beam correspondence for power class 3..... | 154 | +| 6.6.4.1 | General..... | 154 | +| 6.6.4.2 | Beam correspondence tolerance for power class 3..... | 155 | +| 6.6.4.3 | Side Conditions..... | 156 | +| 6.6.4.3.1 | Side Condition for beam correspondence based on SSB and CSI-RS..... | 156 | +| 6.6.4.3.2 | Side Condition for SSB based enhanced Beam Correspondence requirements..... | 156 | +| 6.6.4.3.3 | Side Condition for CSI-RS based enhanced Beam Correspondence requirements..... | 157 | +| 6.6.4.3.4 | Side Condition for Beam Correspondence requirements in initial access and RRC_INACTIVE..... | 157 | +| 6.6.4.4 | Applicability..... | 157 | +| 6.6.5 | (Void)..... | 158 | +| 6.6.6 | Beam correspondence for power class 5..... | 158 | +| 6.6.6.1 | General..... | 158 | +| 6.6.6.2 | (Reserved)..... | 158 | +| 6.6.6.3 | Side Conditions..... | 158 | +| 6.6.6.3.1 | Side Condition for beam correspondence based on SSB and CSI-RS..... | 158 | +| 6.6.6.3.2 | Side Condition for SSB based enhanced Beam Correspondence requirements..... | 159 | +| 6.6.6.3.3 | Side Condition for CSI-RS based enhanced Beam Correspondence requirements..... | 159 | +| 6.6.6.4 | Applicability..... | 160 | +| 6.6.7 | Beam correspondence for power class 6..... | 160 | +| 6.6.7.1 | General..... | 160 | +| 6.6.7.2 | (Void)..... | 160 | +| 6.6.7.3 | Side Conditions..... | 161 | +| 6.6.7.3.1 | (Void)..... | 161 | +| 6.6.7.3.2 | Side Condition for SSB based enhanced Beam Correspondence requirements..... | 161 | +| 6.6.7.3.3 | Side Condition for CSI-RS based enhanced Beam Correspondence requirements..... | 161 | +| 6.6.7.4 | Applicability..... | 162 | + +| | | | +|-----------|------------------------------------------------------------------------------------------|-----| +| 6.6.8 | Beam correspondence for power class 7..... | 162 | +| 6.6.8.1 | General..... | 162 | +| 6.6.8.2 | Void..... | 163 | +| 6.6.8.3 | Side Conditions..... | 163 | +| 6.6.8.3.1 | Side Condition for beam correspondence based on SSB and CSI-RS..... | 163 | +| 6.6.8.3.2 | Side Condition for SSB based enhanced Beam Correspondence requirements..... | 163 | +| 6.6.8.3.3 | Side Condition for CSI-RS based enhanced Beam Correspondence requirements..... | 164 | +| 6.6.8.4 | Applicability..... | 164 | +| 6.6A | Beam correspondence for CA..... | 164 | +| 7 | Receiver characteristics..... | 166 | +| 7.1 | General..... | 166 | +| 7.2 | Diversity characteristics..... | 166 | +| 7.3 | Reference sensitivity..... | 166 | +| 7.3.1 | General..... | 166 | +| 7.3.2 | Reference sensitivity power level..... | 166 | +| 7.3.2.1 | Reference sensitivity power level for power class 1..... | 166 | +| 7.3.2.2 | Reference sensitivity power level for power class 2..... | 167 | +| 7.3.2.3 | Reference sensitivity power level for power class 3..... | 167 | +| 7.3.2.4 | Reference sensitivity power level for power class 4..... | 168 | +| 7.3.2.5 | Reference sensitivity power level for power class 5..... | 168 | +| 7.3.2.6 | Reference sensitivity power level for power class 6..... | 169 | +| 7.3.2.7 | Reference sensitivity power level for power class 7..... | 169 | +| 7.3.3 | Void..... | 170 | +| 7.3.4 | EIS spherical coverage..... | 170 | +| 7.3.4.1 | EIS spherical coverage for power class 1..... | 170 | +| 7.3.4.2 | EIS spherical coverage for power class 2..... | 170 | +| 7.3.4.3 | EIS spherical coverage for power class 3..... | 171 | +| 7.3.4.4 | EIS spherical coverage for power class 4..... | 171 | +| 7.3.4.5 | EIS spherical coverage for power class 5..... | 172 | +| 7.3.4.6 | EIS spherical coverage for power class 6..... | 172 | +| 7.3.4.7 | EIS spherical coverage for power class 7..... | 172 | +| 7.3A | Reference sensitivity for DL CA..... | 173 | +| 7.3A.1 | General..... | 173 | +| 7.3A.2 | Reference sensitivity power level for CA..... | 173 | +| 7.3A.2.1 | Intra-band contiguous CA..... | 173 | +| 7.3A.2.3 | Inter-band CA..... | 174 | +| 7.3A.3 | EIS spherical coverage for DL CA..... | 174 | +| 7.3A.3.1 | Void..... | 174 | +| 7.3A.3.2 | Void..... | 174 | +| 7.3A.3.3 | EIS spherical coverage for inter-band CA..... | 174 | +| 7.3D | Void..... | 175 | +| 7.3K | Spherical coverage requirement for simultaneous reception from multiple directions ..... | 175 | +| 7.3K.0 | General..... | 175 | +| 7.3K.1 | (Reserved)..... | 176 | +| 7.3K.2 | (Reserved)..... | 176 | +| 7.3K.3 | 2AoA spherical coverage of power class 3..... | 176 | +| 7.3K.4 | (Reserved)..... | 176 | +| 7.3K.5 | (Reserved)..... | 176 | +| 7.3K.6 | 2AoA spherical coverage for power class 6..... | 176 | +| 7.4 | Maximum input level..... | 177 | +| 7.4A | Maximum input level for DL CA..... | 178 | +| 7.4A.1 | Maximum input level for Intra-band contiguous CA..... | 178 | +| 7.4A.2 | Maximum input level for Intra-band non-contiguous CA..... | 178 | +| 7.4A.3 | Maximum input level for Inter-band CA..... | 178 | +| 7.4D | Void..... | 179 | +| 7.5 | Adjacent channel selectivity..... | 179 | +| 7.5A | Adjacent channel selectivity for DL CA..... | 181 | +| 7.5A.1 | Adjacent channel selectivity for Intra-band contiguous CA..... | 181 | +| 7.5A.2 | Adjacent channel selectivity for Intra-band non-contiguous CA..... | 183 | +| 7.5A.3 | Adjacent channel selectivity for Inter-band CA..... | 183 | +| 7.5D | Void..... | 183 | + +| | | | +|----------|--------------------------------------------------------|-----| +| 7.6 | Blocking characteristics..... | 183 | +| 7.6.1 | General..... | 183 | +| 7.6.2 | In-band blocking..... | 184 | +| 7.6.3 | Void..... | 185 | +| 7.6A | Blocking characteristics for DL CA..... | 185 | +| 7.6A.1 | General..... | 185 | +| 7.6A.2 | In-band blocking..... | 185 | +| 7.6A.2.2 | In-band blocking for Intra-band non-contiguous CA..... | 185 | +| 7.6A.2.3 | In-band blocking for Inter-band CA..... | 186 | +| 7.6D | Void..... | 186 | +| 7.7 | Void..... | 186 | +| 7.8 | Void..... | 186 | +| 7.9 | Spurious emissions..... | 186 | +| 7.10 | Void..... | 187 | + +**Annex A (normative): Measurement channels..... 188** + +| | | | +|-----------|----------------------------------------------------------------------|-----| +| A.1 | General..... | 188 | +| A.2 | UL reference measurement channels..... | 188 | +| A.2.1 | General..... | 188 | +| A.2.2 | Void..... | 188 | +| A.2.3 | Reference measurement channels for TDD..... | 189 | +| A.2.3.1 | DFT-s-OFDM Pi/2-BPSK..... | 190 | +| A.2.3.2 | DFT-s-OFDM QPSK..... | 190 | +| A.2.3.3 | DFT-s-OFDM 16QAM..... | 191 | +| A.2.3.4 | DFT-s-OFDM 64QAM..... | 191 | +| A.2.3.5 | CP-OFDM QPSK..... | 192 | +| A.2.3.6 | CP-OFDM 16QAM..... | 192 | +| A.2.3.7 | CP-OFDM 64QAM..... | 193 | +| A.3 | DL reference measurement channels..... | 194 | +| A.3.1 | General..... | 194 | +| A.3.2 | Void..... | 197 | +| A.3.3 | DL reference measurement channels for TDD..... | 197 | +| A.3.3.1 | General..... | 197 | +| A.3.3.2 | FRC for receiver requirements for QPSK..... | 198 | +| A.3.3.2-1 | Reference measurement channels for SCS 60 kHz FR2..... | 198 | +| A.3.3.2-2 | Reference measurement channels for SCS 120 kHz FR2..... | 199 | +| A.3.3.2-3 | Reference measurement channels for SCS 480 kHz FR2..... | 200 | +| A.3.3.2-4 | Reference measurement channels for SCS 960 kHz FR2..... | 201 | +| A.3.3.2-5 | Reference measurement channels for SCS 60 kHz FR2..... | 202 | +| A.3.3.2-6 | Reference measurement channels for SCS 120 kHz FR2..... | 203 | +| A.3.3.3 | FRC for receiver requirements for 16QAM..... | 203 | +| A.3.3.4 | FRC for receiver requirements for 64QAM..... | 204 | +| A.3.3.5 | FRC for receiver requirements for 256QAM..... | 208 | +| A.4 | Void..... | 212 | +| A.5 | OFDMA Channel Noise Generator (OCNG)..... | 212 | +| A.5.1 | OCNG Patterns for FDD..... | 212 | +| A.5.2 | OCNG Patterns for TDD..... | 212 | +| A.5.2.1 | OCNG TDD pattern 1: Generic OCNG TDD Pattern for all unused REs..... | 212 | + +| | | +|----------------------------------------------------------------------------|------------| +| Annex B (informative): Void..... | 213 | +| Annex C (normative): Downlink physical channels..... | 214 | +| C.1 General..... | 214 | +| C.2 Setup..... | 214 | +| C.3 Connection..... | 214 | +| C.3.1 Measurement of Receiver Characteristics..... | 214 | +| Annex D (normative): Characteristics of the interfering signal..... | 215 | +| D.1 General..... | 215 | +| D.2 Interference signals..... | 215 | +| Annex E (normative): Environmental conditions..... | 216 | +| E.1 General..... | 216 | +| E.2 Environmental..... | 216 | +| E.2.1 Temperature..... | 216 | +| E.2.2 Voltage..... | 216 | +| E.2.3 Void..... | 217 | +| Annex F (normative): Transmit modulation..... | 218 | +| F.1 Measurement Point..... | 218 | +| F.2 Basic Error Vector Magnitude measurement..... | 218 | +| F.3 Basic in-band emissions measurement..... | 219 | +| F.4 Modified signal under test..... | 219 | +| F.5 Window length..... | 221 | +| F.5.1 Timing offset..... | 221 | +| F.5.2 Window length..... | 221 | +| F.5.3 Window length for normal CP..... | 222 | +| F.5.4 Window length for Extended CP..... | 222 | +| F.5.5 Window length for PRACH..... | 222 | +| F.6 Averaged EVM..... | 223 | +| F.7 Spectrum Flatness..... | 224 | +| F.8 Phase offset measurement for DMRS bundling..... | 224 | +| F.8.1 Measurement point..... | 224 | +| F.8.2 Symbols used..... | 225 | +| F.8.3 Modified test signal..... | 225 | +| F.8.4 Phase offset measurement..... | 225 | +| F.9 Reserved..... | 225 | +| F.10 EVM for dual transmit polarizations..... | 225 | +| F.10.1 General..... | 225 | +| F.10.2 MIMO Equalization (UL MIMO transmission)..... | 226 | +| F.10.3 Maximum Ratio combining (Tx diversity transmission)..... | 227 | +| F.10.4 Layer processing..... | 227 | + +| | | +|---------------------------------------------------------------------------------------------------------|------------| +| Annex G (normative): Difference of relative phase and power errors..... | 228 | +| G.0 General..... | 228 | +| G.1 Measurement Point..... | 228 | +| G.2 Relative Phase Error Measurement..... | 229 | +| G.2.1 Symbols and subcarriers used..... | 229 | +| G.2.2 CFO (carrier frequency offset) correction..... | 229 | +| G.2.3 Steps of the measurement method..... | 229 | +| Annex H (Normative): Modified MPR behavior..... | 230 | +| H.1 Indication of modified MPR behavior..... | 230 | +| Annex I (informative): Void 230 | | +| Annex J (normative): UE coordinate system..... | 231 | +| J.1 Reference coordinate system..... | 231 | +| J.2 Test conditions and angle definitions..... | 232 | +| J.3 DUT positioning guidelines..... | 236 | +| Annex K (informative): Void..... | 237 | +| Annex L (normative): Requirement metric for simultaneous reception from multiple directions..... | 238 | +| L.1 Spherical coverage grid for simultaneous reception or transmission in multiple directions..... | 238 | +| L.2 Probability to support 2AoA reception..... | 238 | +| Annex M (informative): Change history..... | 239 | + +## 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 requirements for NR User Equipment (UE) operating on frequency Range 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.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone" +- [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" +- [4] Void +- [5] 3GPP TS 38.521-2: "NR; User Equipment (UE) conformance specification; Radio transmission and reception; Part 2: Range 2 Standalone" +- [6] Recommendation ITU-R M.1545: "Measurement uncertainty as it applies to test limits for the terrestrial component of International Mobile Telecommunications-2000" +- [7] ITU-R Recommendation SM.329-10, "Unwanted emissions in the spurious domain" +- [8] 47 CFR Part 30, "UPPER MICROWAVE FLEXIBLE USE SERVICE, §30.202 Power limits", FCC. +- [9] 3GPP TS 38.211: "NR; Physical channels and modulation". +- [10] 3GPP TS 38.213: "NR; Physical layer procedures for control". +- [11] 3GPP TS 38.215: "NR; Physical layer measurements". +- [12] 3GPP TS 38.133: "NR; Requirements for support of radio resource management". +- [13] 3GPP TS 38.331: "NR; Radio Resource Control (RRC); Protocol specification". +- [14] 3GPP TS 38.306: "NR; User Equipment (UE) radio access capabilities". +- [15] IEEE Std 149: "IEEE Standard Test Procedures for Antennas", IEEE. + +## 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]. + +**Aggregated Channel Bandwidth:** The RF bandwidth in which a UE is configured to transmit and receive multiple contiguously aggregated carriers. + +**Bidirectional spectrum:** UL/DL common spectrum in which the UE supports the configuration of uplink or downlink CCs. + +**Beam correspondence:** the ability of the UE to select a suitable beam for UL transmission based on DL measurements with or without relying on UL beam sweeping. + +**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. + +NOTE: Carriers aggregated in each band can be contiguous or non-contiguous. + +**Cumulative aggregated channel bandwidth:** The cumulative aggregated channel bandwidth is defined as the frequency band from the lowest edge of the lowest CC to the upper edge of the highest CC of all UL and DL configured CCs inside the bidirectional spectrum of the UE. + +**EIRP(Link=Link angle, Meas=Link angle):** measurement of the UE such that the link angle is aligned with the measurement angle. EIRP (indicator to be measured) can be replaced by EIS, Frequency, EVM, carrier Leakage, In-band emission and OBW. + +**EIRP(Link=TX beam peak direction, Meas=Link angle):** measurement of the EIRP of the UE such that the measurement angle is aligned with the beam peak direction within an acceptable measurement error uncertainty. EIRP (indicator to be measured) can be replaced by Frequency, EVM, carrier Leakage, In-band emission and OBW + +**EIRP(Link=Spherical coverage grid, Meas=Link angle):** measurement of the EIRP spherical coverage of the UE such that the EIRP link and measurement angles are aligned with the directions along the spherical coverage grid within an acceptable measurement error uncertainty. Alternatively, the spherical coverage grid can be replaced by the beam peak search grid as the results from the Tx beam peak search can be re-used for spherical coverage. + +**EIS (effective 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 + +**EIS(Link=RX beam peak direction, Meas=Link angle):** measurement of the EIS of the UE such that the measurement angle is aligned with the RX beam peak direction within an acceptable measurement error uncertainty. + +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). + +**EIS(Link=Spherical coverage grid, Meas=Link angle):** measurement of the EIS spherical coverage of the UE such that the EIS link and measurement angles are aligned with the directions along the spherical coverage grid within an acceptable measurement error uncertainty. Alternatively, the spherical coverage grid can be replaced by the Rx beam peak search grid as the results from the Rx beam peak search can be re-used for spherical coverage. + +**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. + +**FWA UE:** A UE intended to be used in fixed wireless access scenario. + +**Handheld UE:** A UE intended to be used in hand held scenario. + +**IBM(Independent Beam Management):** A UE that supports inter-band CA with IBM selects its DL and UL beam(s) for all CCs in each configured band based on DL reference signals measurements made in that 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. + +**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. + +**Link angle:** a DL-signal AoA from the view point of the UE, as described in Annex J. If the beam lock function is used to lock the UE beam(s), the link angle can become any arbitrary AoA once the beam lock has been activated. + +**Measurement angle:** the angle of measurement of the desired metric from the view point of the UE, as described in Annex J + +**radiated interface boundary:** operating band specific radiated requirements reference point where the radiated requirements apply + +**radiated requirements reference point:** for the RF measurement setup, the radiated requirements reference point is located at the centre of the quiet zone. From the UE perspective the reference point is the input of the UE antenna array + +**RedCap UE:** The UE with reduced capabilities as defined in clause 4.2.21.1 from TS38.306 [14] + +**RX beam peak direction:** direction where the maximum total component of RSRP and thus best total component of EIS is found + +**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. + +**TX beam peak direction:** direction where the maximum total component of EIRP is found + +**TRP(Link=TX beam peak direction, Meas=TRP grid):** measurement of the TRP of the UE such that the measurement angles are aligned with the directions of the TRP grid points within an acceptable measurement uncertainty while the link angle is aligned with the TX beam peak direction + +NOTE: For requirements based on EIRP/EIS, the radiated interface boundary is associated to the far-field region + +**UE transmission bandwidth configuration:** Set of resource blocks located within the UE channel bandwidth which may be used for transmitting or receiving by the UE. + +**Vehicular UE:** A UE embedded in a vehicle + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|---------------------------------|----------------------------------------------------------------------------------------------------------| +| $\Delta\text{EIRP}_{\text{BC}}$ | The beam correspondence tolerance, where $\Delta\text{EIRP}_{\text{BC}} = \text{EIRP}_2 - \text{EIRP}_1$ | +| $\Delta F_{\text{Global}}$ | Granularity of the global frequency raster | +| $\Delta F_{\text{Raster}}$ | Band dependent channel raster granularity | +| $\Delta f_{\text{OOB}}$ | $\Delta$ Frequency of Out Of Band emission | +| $\Delta_{\text{RB}}$ | The starting frequency offset between the allocated RB and the measured non-allocated RB | +| $\Delta R_{\text{IB}}$ | Allowed reference sensitivity relaxation due to support for inter-band CA operation | +| $\Delta R_{\text{IBC}}$ | Allowed reference sensitivity relaxation due to support for intra-band contiguous CA operation | +| $\Delta R_{\text{IBNC}}$ | Allowed reference sensitivity relaxation due to support for intra-band non-contiguous CA operation | + +| | | +|-----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $\Delta R_{IB,P,n}$ | Allowed relaxation to reference sensitivity due to support for inter-band CA operation, per supported band in a combination. | +| $\Delta R_{IB,S,n}$ | Allowed relaxation to EIS spherical coverage due to support for inter-band CA operation, per supported band in a combination. | +| $\Delta T_{IB}$ | Allowed relaxation to EIRP requirements due to support for inter-band CA operation | +| $\Delta T_{IB,P,n}$ | Allowed relaxation to peak EIRP requirements due to support for inter-band CA operation, per supported band in a combination. | +| $\Delta T_{IB,S,n}$ | Allowed relaxation to EIRP spherical coverage due to support for inter-band CA operation, per supported band in a combination. | +| $\Delta T_{STxMP}$ | Allowed relaxation to EIRP requirements due to support for simultaneous transmission to multiple directions. | +| $\Delta MB_{P,n}$ | Allowed relaxation to each, minimum peak EIRP and reference sensitivity due to support for multi-band operation, per supported band in a combination. | +| $\Delta MB_{S,n}$ | Allowed relaxation to each, EIRP spherical coverage and EIS spherical coverage due to support for multi-band operation, per supported band in a combination. | +| $\Delta MPR$ | Allowed increase in Maximum Power Reduction for 256QAM. | +| $\Delta MPR_{STxMP}$ | Allowed relaxation to MPR requirement due to support for simultaneous transmission to multiple directions, per each of indicated TCI states. | +| $BW_{Channel}$ | Channel bandwidth | +| $BW_{Channel\_CA}$ | Aggregated channel bandwidth, expressed in MHz | +| $BW_{GB}$ | $\max( BW_{GB,Channel(k)} )$ | +| $BW_{GB,Channel(k)}$ | Minimum guard band defined in sub-clause 5.3.A.2 of carrier k | +| $BW_{interferer}$ | Bandwidth of the interferer | +| $Ceil(x)$ | Rounding upwards; $ceil(x)$ is the smallest integer such that $ceil(x) \geq x$ | +| $EIRP_1$ | The measured total EIRP based on the beam the UE chooses autonomously (corresponding beam) to transmit in the direction of the incoming DL signal, which is based on beam correspondence without relying on UL beam sweeping | +| $EIRP_2$ | The measured total EIRP based on the beam yielding highest EIRP in a given direction, which is based on beam correspondence with relying on UL beam sweeping | +| $EIRP_{max}$ | The applicable maximum EIRP as specified in sub-clause 6.2.1 | +| $Floor(x)$ | Rounding downwards; $floor(x)$ is the greatest integer such that $floor(x) \leq x$ | +| $F\_center$ | The center frequency of an allocated block of PRBs | +| $F_C$ | Center frequency of a carrier for a numerology defined by the RF reference frequency on the channel raster mapped to the carrier according to subclause 5.4.2.2 | +| $F_{C,block,high}$ | $F_C$ of the highest transmitted/received carrier in a sub-block. | +| $F_{C,block,low}$ | $F_C$ of the lowest transmitted/received carrier in a sub-block. | +| $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,block,low}$ | The lower sub-block edge, where $F_{edge,block,low} = F_{C,block,low} - F_{offset,low}$ . | +| $F_{edge,block,high}$ | The upper sub-block edge, where $F_{edge,block,high} = F_{C,block,high} + F_{offset,high}$ . | +| $F_{edge,low}$ | The lower edge of Aggregated Channel Bandwidth , expressed in MHz. $F_{edge,low} = F_{C,low} - F_{offset,low}$ . | +| $F_{edge,high}$ | The upper edge of Aggregated Channel Bandwidth , expressed in MHz. $F_{edge,high} = F_{C,high} + F_{offset,high}$ . | +| $F_{Interferer}$ | Frequency of the interferer | +| $F_{Interferer} \text{ (offset)}$ | Frequency offset of the interferer (between the center frequency of the interferer and the carrier frequency of the carrier measured) | +| $F_{Ioffset}$ | Frequency offset of the interferer (between the center frequency of the interferer and the closest edge of the carrier measured) | +| $Floor(x)$ | Rounding downwards; $floor(x)$ is the greatest integer such that $floor(x) \leq x$ | +| $F_{OOB}$ | The boundary between the NR out of band emission and spurious emission domains | +| $F_{REF}$ | RF reference frequency | +| $F_{REF-Offs}$ | Offset used for calculating $F_{REF}$ | +| $F_{UL\_low}$ | The lowest frequency of the uplink operating band | +| $F_{UL\_high}$ | The highest frequency of the uplink operating band | +| $F_{UL\_Meas}$ | The sub-carrier frequency for which the equalizer coefficient is evaluated | +| $GB_{Channel}$ | Minimum guard band defined in sub-clause 5.3.3, expressed in kHz | +| $L_{CRB}$ | Transmission bandwidth which represents the length of a contiguous resource block allocation expressed in units of resources blocks | +| $L_{CRB,Max}$ | Maximum number of RB for a given Channel bandwidth and sub-carrier spacing | +| $Max()$ | The largest of given numbers | + +| | | +|--------------------|------------------------------------------------------------------------------------------------------------------------------| +| Min() | The smallest of given numbers | +| $MPR_{f,c}$ | Maximum output power reduction for carrier $f$ of serving cell $c$ | +| $MPR_{narrow}$ | Maximum output power reduction due to narrow PRB allocation | +| $MPR_{WT}$ | Maximum power reduction due to modulation orders, transmit bandwidth configurations, waveform types | +| $n_{PRB}$ | Physical resource block number | +| NR ACLR | NR ACLR | +| $N_{RB}$ | Transmission bandwidth configuration, expressed in units of resource blocks | +| $N_{RB,low}$ | Transmission bandwidth configurations according to Table 5.3.2-1 for the lowest assigned component carrier in clause 5.3A.1 | +| $N_{RB,high}$ | Transmission bandwidth configurations according to Table 5.3.2-1 for the highest assigned component carrier in clause 5.3A.1 | +| $N_{REF}$ | NR Absolute Radio Frequency Channel Number (NR-ARFCN) | +| $N_{REF-Offs}$ | Offset used for calculating $N_{REF}$ | +| $P_{CMAX}$ | The configured maximum UE output power | +| $P_{CMAX,s,f,c}$ | The configured maximum UE output power for carrier $f$ of serving cell $c$ | +| $P_{int}$ | The intermediate power point as defined in table 6.3.4.2-2 | +| $P_{Interferer}$ | Modulated mean power of the interferer | +| $P_{max}$ | The maximum UE output power as specified in sub-clause 6.2.1 | +| $P_{min}$ | The minimum UE output power as specified in sub-clause 6.3.1 | +| $P-MPR_{f,c}$ | The Power Management UE Maximum Power Reduction for carrier $f$ of serving cell $c$ | +| $P_{PowerClass}$ | Nominal UE power class (i.e., no tolerance) as specified in sub-clause 6.2.1 | +| $P_{RB}$ | The transmitted power per allocated RB, measured in dBm | +| $P_{TMAX,f,c}$ | The measured total radiated power for carrier $f$ of serving cell $c$ | +| $P_{UMAX}$ | The measured configured maximum UE output power | +| $P_W$ | Power of a wanted DL signal | +| $RB_{start}$ | Indicates the lowest RB index of transmitted resource blocks | +| $SCS_{low}$ | SCS for the lowest assigned component carrier in clause 5.3A.1, expressed in kHz | +| $SCS_{high}$ | SCS for the highest assigned component carrier in clause 5.3A.1, expressed in kHz | +| $SS_{REF}$ | SS block reference frequency position | +| $T(\Delta P)$ | The tolerance $T(\Delta P)$ for applicable values of $\Delta P$ (values in dB) | +| $TRP_{max}$ | The maximum TRP for the UE power class as specified in sub-clause 6.2.1 | + +### 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 | +| A-MPR | Additional Maximum Power Reduction | +| AoA | Angle of Arrival | +| BCS | Bandwidth Combination Set | +| BPSK | Binary Phase-Shift Keying | +| BS | Base Station | +| BW | Bandwidth | +| BWP | Bandwidth Part | +| CA | Carrier aggregation | +| CABW | Cumulative Aggregated Channel Bandwidth | +| $CA\_nX-nY$ | Inter-band CA of component carrier(s) in one sub-block within Band X and component carrier(s) in one sub-block within Band Y where X and Y are the applicable NR operating band | +| CC | Component carrier | +| CDF | Cumulative Distribution Function | +| CP-OFDM | Cyclic Prefix-OFDM | +| CW | Continuous Wave | +| DFT-s-OFDM | Discrete Fourier Transform-spread-OFDM | +| DM-RS | Demodulation Reference Signal | +| DTX | Discontinuous Transmission | +| EIRP | Effective Isotropic Radiated Power | + +| | | +|----------|------------------------------------------------------------------------| +| EIS | Effective Isotropic Sensitivity | +| EVM | Error Vector Magnitude | +| FR | Frequency Range | +| FWA | Fixed Wireless Access | +| GSCN | Global Synchronization Channel Number | +| IBB | In-band Blocking | +| IBM | Independent Beam Management | +| IDFT | Inverse Discrete Fourier Transformation | +| ITU-R | Radiocommunication Sector of the International Telecommunication Union | +| MBW | Measurement bandwidth defined for the protected band | +| MPR | Allowed maximum power reduction | +| NR | New Radio | +| NR-ARFCN | NR Absolute Radio Frequency Channel Number | +| OCNG | OFDMA Channel Noise Generator | +| OOB | Out-of-band | +| OTA | Over The Air | +| P-MPR | Power Management Maximum Power Reduction | +| PRB | Physical Resource Block | +| QAM | Quadrature Amplitude Modulation | +| RF | Radio Frequency | +| REFSENS | Reference Sensitivity | +| RedCap | Reduced Capability | +| RIB | Radiated Interface Boundary | +| RMS | Root Mean Square (value) | +| RSRP | Reference Signal Receiving Power | +| Rx | Receiver | +| SCS | Subcarrier spacing | +| SEM | Spectrum Emission Mask | +| SRS | Sounding Reference Symbol | +| SS | Synchronization Symbol | +| TPC | Transmission Power Control | +| TRP | Total Radiated Power | +| Tx | Transmitter | +| UE | User Equipment | +| UL MIMO | Uplink Multiple Antenna transmission | +| ULFPTx | Uplink Full Power Transmission | + +## 4 General + +### 4.1 Relationship between minimum requirements and test requirements + +The present document is a Single-RAT specification for NR UE, covering RF characteristics and minimum performance requirements. Conformance to the present specification is demonstrated by fulfilling the test requirements specified in the conformance specification 3GPP TS 38.521-2 [5]. + +The Minimum Requirements given in this specification make no allowance for measurement uncertainty. The test specification TS 38.521-2 [5] defines test tolerances. These test tolerances are individually calculated for each test. The test tolerances are used to relax the minimum requirements in this specification to create test requirements. For some requirements, including regulatory requirements, the test tolerance is set to zero. + +The measurement results returned by the test system are compared - without any modification - against the test requirements as defined in 3GPP TS 38.521-2 [5]. + +### 4.2 Applicability of minimum requirements + +- a) In this specification the Minimum Requirements are specified as general requirements and additional requirements. Where the Requirement is specified as a general requirement, the requirement is mandated to be met in all scenarios +- b) For specific scenarios for which an additional requirement is specified, in addition to meeting the general requirement, the UE is mandated to meet the additional requirements. +- c) The spurious emissions power requirements are for the long-term average of the power. For the purpose of reducing measurement uncertainty it is acceptable to average the measured power over a period of time sufficient to reduce the uncertainty due to the statistical nature of the signal +- d) All the requirements for intra-band contiguous and non-contiguous CA apply under the assumption of the same slot format indicated by *TDD-UL-DL-ConfigurationCommon* and *TDD-UL-DL-ConfigurationDedicated* in the PCell and SCells for NR SA. + +For FR2 intra-band CA configurations with multiple FR2 sub-blocks, where at least one of the sub-blocks is a contiguous CA configuration: + +- if the field *partialFR2-FallbackRX-Req* is not present, the UE shall meet all applicable UE RF requirements for the highest order CA configuration and all associated fallback CA configurations; +- if the field *partialFR2-FallbackRX-Req* is present, for each FR2 intra-band CA configuration with multiple sub-blocks that the UE indicates support for explicitly in UE capability signalling: the in-gap UE RF requirements in clauses 7.5A, 7.5D, 7.6A, 7.6D apply as the equivalent requirements for the associated fallback CA configurations with the same number of sub-blocks, where at least one of the sub-blocks consists of a contiguous CA configuration. The UE shall meet all applicable UE RF requirements for fallback CA configurations with a lesser number of sub-blocks; +- regardless of the field *partialFR2-FallbackRX-Req*, the UE shall meet all DL out-of-gap requirements for all lower order fallback CA configurations. + +### 4.3 Specification suffix information + +Unless stated otherwise the following suffixes are used for indicating at 2nd level clause, shown in Table 4.3-1. + +**Table 4.3-1: Definition of suffixes** + +| Clause suffix | Variant | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------| +| None | Single Carrier | +| A | Carrier Aggregation (CA) | +| B | Dual-Connectivity (DC) | +| C | Supplement Uplink (SUL) | +| D | UL MIMO | +| K | Simultaneous reception or transmission in multiple directions | +| NOTE 1: Suffix D in this specification represents either polarized UL MIMO or spatial UL MIMO. RF requirements are same. If UE supports both kinds of UL MIMO, then RF requirements only need to be verified under either polarized or spatial UL MIMO. | | +| NOTE 2: Suffix K applies to simultaneous reception or transmission with different TCI-states and different QCL-D reference signals across the TCI-states | | + +## 5 Operating bands and channel arrangement + +### 5.1 General + +The channel arrangements presented in this clause are based on the operating bands and channel bandwidths defined in the present release of specifications. + +NOTE: Other operating bands and 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 NR can operate according to this version of the specification are identified as described in Table 5.1-1. Whenever the FR2 is referred, both FR2-1 and FR2-2 frequency sub-ranges shall be considered, unless otherwise stated. + +**Table 5.1-1: Definition of frequency ranges** + +| Frequency range designation | | Corresponding frequency range | +|-----------------------------|-------|-------------------------------| +| FR1 | | 410 MHz – 7125 MHz | +| FR2 | FR2-1 | 24250 MHz – 52600 MHz | +| | FR2-2 | 52600 MHz – 71000 MHz | + +The present specification covers FR2 operating bands. + +### 5.2 Operating bands + +NR is designed to operate in the FR2 operating bands defined in Table 5.2-1. + +**Table 5.2-1: NR operating bands in FR2** + +| Operating Band | Uplink (UL) operating band | Downlink (DL) operating band | Duplex Mode | +|----------------|------------------------------|------------------------------|------------------| +| | BS receive
UE transmit | BS transmit
UE receive | | +| | $F_{UL\_low} - F_{UL\_high}$ | $F_{DL\_low} - F_{DL\_high}$ | | +| n257 | 26500 MHz – 29500 MHz | 26500 MHz – 29500 MHz | TDD | +| n258 | 24250 MHz – 27500 MHz | 24250 MHz – 27500 MHz | TDD | +| n259 | 39500 MHz – 43500 MHz | 39500 MHz – 43500 MHz | TDD | +| n260 | 37000 MHz – 40000 MHz | 37000 MHz – 40000 MHz | TDD | +| n261 | 27500 MHz – 28350 MHz | 27500 MHz – 28350 MHz | TDD | +| n262 | 47200 MHz – 48200 MHz | 47200 MHz – 48200 MHz | TDD | +| n263 | 57000 MHz – 71000 MHz | 57000 MHz – 71000 MHz | TDD 1 | + +NOTE 1: This band is for unlicensed operation and subject to regional and/or country specific regulatory requirements. + +### 5.2A Operating bands for CA + +#### 5.2A.1 Intra-band CA + +NR intra-band contiguous and non-contiguous carrier aggregation is designed to operate in the operating bands defined in Table 5.2A.1-1, where all operating bands are within FR2. + +**Table 5.2A.1-1: Intra-band contiguous and non-contiguous CA operating bands in FR2** + +| NR CA Band | NR Band
(Table 5.2-1) | +|---------------------------------------------------------------------------------------------------------|--------------------------| +| CA_n257 | n257 | +| CA_n258 | n258 | +| CA_n259 | n259 | +| CA_n260 | n260 | +| CA_n261 | n261 | +| CA_n263 1 | n263 | +| NOTE 1: In this release of the specification, only contiguous CA is applicable for this operating band. | | + +## 5.2A.2 Inter-band CA + +NR inter-band carrier aggregation is designed to operate in the operating bands defined in Table 5.2A.2-1, where all operating bands are within FR2. + +Beam management type is according to UE capability declaration *IE beamManagementType-r16 or beamManagementType-CBM-r17*. The requirements in the following clauses are only applicable to inter-band CA with IBM type. + +**Table 5.2A.2-1: Inter-band CA operating bands in FR2** + +| NR CA Band | NR Band
(Table 5.2-1) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------| +| CA_n257-n259 1 | n257, n259 | +| CA_n258-n260 1 | n258, n260 | +| CA_n258-n261 1 | n258, n261 | +| CA_n260-n261 1 | n260, n261 | +| NOTE 1: The minimum requirements apply only when there is non-simultaneous Rx/Tx operation between inter-band NR carriers in the current version of this specification. | | + +## 5.2D Operating bands for UL MIMO + +NR UL MIMO is designed to operate in the operating bands defined in Table 5.2D-1. + +**Table 5.2D-1: NR UL MIMO operating bands** + +| UL MIMO operating band
(Table 5.2-1) | +|-----------------------------------------| +| n257 | +| n258 | +| n259 | +| n260 | +| n261 | +| n262 | + +## 5.2K Operating bands for simultaneous reception or transmission in multiple directions + +Simultaneous reception or transmission in multiple directions is enabled for the bands defined in Table 5.2K-1. + +**Table 5.2K-1: NR bands for simultaneous reception or transmission in multiple directions** + +| NR bands for simultaneous reception or transmission in multiple directions (Table 5.2-1) | +|------------------------------------------------------------------------------------------| +| n257 | +| n258 | +| n259 | +| n260 | +| n261 | +| n262 | + +### 5.3 UE Channel bandwidth + +#### 5.3.1 General + +The UE channel bandwidth supports a single NR RF carrier in the uplink or downlink at the UE. From a BS perspective, different UE channel bandwidths may be supported within the same spectrum for transmitting to and receiving from UEs connected to the BS. Transmission of multiple carriers to the same UE (CA) or multiple carriers to different UEs within the BS channel bandwidth can be supported. + +From a UE perspective, the UE is configured with one or more BWP / carriers, each with its own UE channel bandwidth. The UE does not need to be aware of the BS channel bandwidth or how the BS allocates bandwidth to different UEs. + +The placement of the UE channel bandwidth for each UE carrier is flexible but can only be completely within the BS channel bandwidth. + +The relationship between the channel bandwidth, the guardband and the transmission bandwidth configuration is shown in Figure 5.3.1-1. + +![Diagram illustrating the definition of channel bandwidth and transmission bandwidth configuration for one NR channel. It shows a horizontal axis representing frequency. The total width is labeled 'Channel Bandwidth [MHz]' between two dashed vertical lines labeled 'Channel Edge'. Within this, a solid horizontal line segment represents the 'Transmission Bandwidth Configuration N_RB [RB]'. Below this, a series of vertical bars represent 'Resource Block's. A subset of these bars is highlighted in blue and labeled 'Active Resource Blocks'. The width of this active subset is labeled 'Transmission Bandwidth [RB]'. The gaps between the active blocks and the channel edges are labeled 'Guardband, can be asymmetric'.](303fadfb9def251d1575d6221199b158_img.jpg) + +Diagram illustrating the definition of channel bandwidth and transmission bandwidth configuration for one NR channel. It shows a horizontal axis representing frequency. The total width is labeled 'Channel Bandwidth [MHz]' between two dashed vertical lines labeled 'Channel Edge'. Within this, a solid horizontal line segment represents the 'Transmission Bandwidth Configuration N\_RB [RB]'. Below this, a series of vertical bars represent 'Resource Block's. A subset of these bars is highlighted in blue and labeled 'Active Resource Blocks'. The width of this active subset is labeled 'Transmission Bandwidth [RB]'. The gaps between the active blocks and the channel edges are labeled 'Guardband, can be asymmetric'. + +**Figure 5.3.1-1: Definition of channel bandwidth and transmission bandwidth configuration for one NR channel** + +#### 5.3.2 Maximum transmission bandwidth configuration + +The maximum transmission bandwidth configuration $N_{RB}$ for each UE channel bandwidth and subcarrier spacing is specified in Table 5.3.2-1 + +**Table 5.3.2-1: Maximum transmission bandwidth configuration $N_{RB}$** + +| SCS (kHz) | 50 MHz | 100 MHz | 200 MHz | 400 MHz | 800 MHz | 1600 MHz | 2000 MHz | +|------------------|----------|----------|----------|----------|----------|----------|----------| +| | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | +| 60 | 66 | 132 | 264 | N/A | N/A | N/A | N/A | +| 120 | 32 | 66 | 132 | 264 | N/A | N/A | N/A | +| 480 1 | N/A | N/A | N/A | 66 | 124 | 248 | N/A | +| 960 1 | N/A | N/A | N/A | 33 | 62 | 124 | 148 | + +Note 1: This SCS is optional in this release of the specification. + +### 5.3.3 Minimum guardband and transmission bandwidth configuration + +The minimum guardband for each UE channel bandwidth and SCS is specified in Table 5.3.3-1. + +**Table 5.3.3-1: Minimum guardband for each UE channel bandwidth and SCS (kHz)** + +| SCS (kHz) | 50 MHz | 100 MHz | 200 MHz | 400 MHz | 800 MHz | 1600 MHz | 2000 MHz | +|-----------|--------|---------|---------|---------|---------|----------|----------| +| 60 | 1210 | 2450 | 4930 | N/A | N/A | N/A | N/A | +| 120 | 1900 | 2420 | 4900 | 9860 | N/A | N/A | N/A | +| 480 | N/A | N/A | N/A | 9680 | 42640 | 85520 | N/A | +| 960 | N/A | N/A | N/A | 9440 | 42400 | 85280 | 147040 | + +NOTE: The minimum guardbands have been calculated using the following equation: $GB_{channel} = (BW_{Channel} \times 1000 \text{ (kHz)} - N_{RB} \times SCS \times 12) / 2 - SCS/2$ , where $N_{RB}$ are from Table 5.3.2-1 and $GB_{channel}$ expressed in kHz. + +The minimum guardband of receiving BS SCS 240 kHz SS/PBCH block for each UE channel bandwidth is specified in table 5.3.3-2 for FR2. + +**Table: 5.3.3-2: Minimum guardband (kHz) of SCS 240 kHz SS/PBCH block in FR2-1** + +| SCS (kHz) | 100 MHz | 200 MHz | 400 MHz | +|-----------|---------|---------|---------| +| 240 | 3800 | 7720 | 15560 | + +NOTE: In FR2-1, the minimum guardband in Table 5.3.3-2 is applicable only when the SCS 240 kHz SS/PBCH block is received adjacent to the edge of the UE channel bandwidth within which the SS/PBCH block is located. + +### Figure 5.3.3-1: Void + +The number of RBs configured in any channel bandwidth shall ensure that the minimum guardband specified in this clause is met. + +![Figure 5.3.3-2: UE PRB utilization diagram. A horizontal axis labeled 'f' represents frequency. A solid rectangle represents the 'UE channel BW'. Inside this rectangle, two dashed vertical lines near the left and right edges define the 'Minimum guard band'. A dashed arrow points from the text 'All PRBs falling within UE channel bandwidth not covering the minimum guard band can be used' to the area between the dashed lines.](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +Figure 5.3.3-2: UE PRB utilization diagram. A horizontal axis labeled 'f' represents frequency. A solid rectangle represents the 'UE channel BW'. Inside this rectangle, two dashed vertical lines near the left and right edges define the 'Minimum guard band'. A dashed arrow points from the text 'All PRBs falling within UE channel bandwidth not covering the minimum guard band can be used' to the area between the dashed lines. + +**Figure 5.3.3-2 UE PRB utilization** + +In the case that multiple numerologies are multiplexed in the same symbol due to BS transmission of SSB, the minimum guardband on each side of the carrier is the guardband applied at the configured channel bandwidth for the numerology that is transmitted immediately adjacent to the guard band. + +If multiple numerologies are multiplexed in the same symbol and the UE channel bandwidth is $> 200$ MHz, the minimum guardband applied adjacent to 60 kHz SCS shall be the same as the minimum guardband defined for 120 kHz SCS for the same UE channel bandwidth. + +![Figure 5.3.3-3: Guard band definition when transmitting multiple numerologies diagram. A horizontal axis represents 'UE channel bandwidth'. Two adjacent rectangles, 'Numerology X' and 'Numerology Y', are shown. Dashed lines extend from the outer edges of these rectangles to define guard bands. Labels 'Guard defined for numerology X when transmitted across full UE channel BW' and 'Guard defined for numerology Y when transmitted across full UE channel BW' point to these guard bands.](e29665b8abcea967ef289c6aff07ae4c_img.jpg) + +Figure 5.3.3-3: Guard band definition when transmitting multiple numerologies diagram. A horizontal axis represents 'UE channel bandwidth'. Two adjacent rectangles, 'Numerology X' and 'Numerology Y', are shown. Dashed lines extend from the outer edges of these rectangles to define guard bands. Labels 'Guard defined for numerology X when transmitted across full UE channel BW' and 'Guard defined for numerology Y when transmitted across full UE channel BW' point to these guard bands. + +**Figure 5.3.3-3 Guard band definition when transmitting multiple numerologies** + +Note: Figure 5.3.3-3 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 numerology, its common resource blocks are specified in Clause 4.4.4.3 in [9], 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. The *UE transmission bandwidth configuration* is indicated by the higher layer parameter *carrierBandwidth* [13] and will fulfil the minimum UE guardband requirement specified in Clause 5.3.3. + +## 5.3.5 Channel bandwidth per operating band + +The requirements in this specification apply to the combination of channel bandwidths, SCS and operating bands shown in Table 5.3.5-1. The transmission bandwidth configuration in Table 5.3.2-1 shall be supported for each of the specified channel bandwidths. The channel bandwidths are specified for both the Tx and Rx path. + +**Table 5.3.5-1: Channel bandwidths for each NR band** + +| Operating band | SCS (kHz) | UE channel bandwidth (MHz) | | | | | | | +|----------------|------------------|----------------------------|-----|-----|------------------|------------------|-------------------|-------------------| +| | | 50 | 100 | 200 | 400 | 800 | 1600 | 2000 | +| n257 | 60 | 50 | 100 | 200 | | | | | +| | 120 | 50 | 100 | 200 | 400 1 | | | | +| n258 | 60 | 50 | 100 | 200 | | | | | +| | 120 | 50 | 100 | 200 | 400 1 | | | | +| n259 | 60 | 50 | 100 | 200 | | | | | +| | 120 | 50 | 100 | 200 | 400 1 | | | | +| n260 | 60 | 50 | 100 | 200 | | | | | +| | 120 | 50 | 100 | 200 | 400 1 | | | | +| n261 | 60 | 50 | 100 | 200 | | | | | +| | 120 | 50 | 100 | 200 | 400 1 | | | | +| n262 | 60 | 50 | 100 | 200 | | | | | +| | 120 | 50 | 100 | 200 | 400 1 | | | | +| n263 | 120 | | 100 | | 400 | | | | +| | 480 2 | | | | 400 | 800 1 | 1600 1 | | +| | 960 2 | | | | 400 | 800 1 | 1600 1 | 2000 1 | + +NOTE 1: This UE channel bandwidth is optional in this release of the specification. +NOTE 2: This SCS is optional in this release of the specification. + +## 5.3A UE channel bandwidth for CA + +### 5.3A.1 General + +### 5.3A.2 Minimum guardband and transmission bandwidth configuration for CA + +For intra-band contiguous carrier aggregation, *Aggregated Channel Bandwidth* and *Guard Bands* are defined as follows, see Figure 5.3A.2-1. + +![Figure 5.3A.2-1: Definition of Aggregated Channel Bandwidth for intra-band carrier aggregation. The diagram shows a frequency axis with three carrier blocks. The first block is grey, the second is green, and the third is grey. The total width of the three blocks is labeled 'Aggregated Channel Bandwidth, BW_channel_CA (MHz)'. The left edge of the first block is labeled 'F_edge, low' and the right edge of the third block is labeled 'F_edge, high'. The center frequency of the first block is labeled 'F_c, low' and the center frequency of the third block is labeled 'F_c, high'. The distance from 'F_edge, low' to 'F_c, low' is labeled 'F_offset, low'. The distance from 'F_c, high' to 'F_edge, high' is labeled 'F_offset, high'. The first block is labeled 'Lowest Carrier Transmission Bandwidth Configuration (RB)' and the third block is labeled 'Highest Carrier Transmission Bandwidth Configuration (RB)'. Vertical dashed lines extend from the edges and center frequencies to the labels.](9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg) + +Figure 5.3A.2-1: Definition of Aggregated Channel Bandwidth for intra-band carrier aggregation. The diagram shows a frequency axis with three carrier blocks. The first block is grey, the second is green, and the third is grey. The total width of the three blocks is labeled 'Aggregated Channel Bandwidth, BW\_channel\_CA (MHz)'. The left edge of the first block is labeled 'F\_edge, low' and the right edge of the third block is labeled 'F\_edge, high'. The center frequency of the first block is labeled 'F\_c, low' and the center frequency of the third block is labeled 'F\_c, high'. The distance from 'F\_edge, low' to 'F\_c, low' is labeled 'F\_offset, low'. The distance from 'F\_c, high' to 'F\_edge, high' is labeled 'F\_offset, high'. The first block is labeled 'Lowest Carrier Transmission Bandwidth Configuration (RB)' and the third block is labeled 'Highest Carrier Transmission Bandwidth Configuration (RB)'. Vertical dashed lines extend from the edges and center frequencies to the labels. + +**Figure 5.3A.2-1: Definition of *Aggregated Channel Bandwidth* for intra-band carrier aggregation** + +The *aggregated channel bandwidth*, $BW_{\text{Channel\_CA}}$ , is defined as + +$$BW_{\text{Channel\_CA}} = F_{\text{edge,high}} - F_{\text{edge,low}} \text{ (MHz)}.$$ + +The lower bandwidth edge $F_{\text{edge,low}}$ and the upper bandwidth edge $F_{\text{edge,high}}$ of the aggregated channel bandwidth are used as frequency reference points for transmitter and receiver requirements and are defined by + +$$F_{\text{edge,low}} = F_{\text{C,low}} - F_{\text{offset,low}}$$ + +$$F_{\text{edge,high}} = F_{\text{C,high}} + F_{\text{offset,high}}$$ + +The lower and upper frequency offsets depend on the transmission bandwidth configurations of the lowest and highest assigned edge component carrier and are defined as + +$$F_{\text{offset,low}} = (N_{\text{RB,low}} * 12 + 1) * \text{SCS}_{\text{low}} / 2 + \text{BW}_{\text{GB}} \text{ (MHz)}$$ + +$$F_{\text{offset,high}} = (N_{\text{RB,high}} * 12 - 1) * \text{SCS}_{\text{high}} / 2 + \text{BW}_{\text{GB}} \text{ (MHz)}$$ + +$$\text{BW}_{\text{GB}} = \max(\text{BW}_{\text{GB,Channel(k)}})$$ + +$N_{\text{RB,low}}$ and $N_{\text{RB,high}}$ are the transmission bandwidth configurations according to Table 5.3.2-1 for the lowest and highest assigned component carrier, $\text{SCS}_{\text{low}}$ and $\text{SCS}_{\text{high}}$ are the sub-carrier spacing for the lowest and highest assigned component carrier respectively. $\text{SCS}_{\text{low}}$ , $\text{SCS}_{\text{high}}$ , $N_{\text{RB,low}}$ , $N_{\text{RB,high}}$ , and $\text{BW}_{\text{GB,Channel(k)}}$ use the largest $\mu$ value among the subcarrier spacing configurations supported in the operating band for both of the channel bandwidths according to Table 5.3.5-1 and $\text{BW}_{\text{GB,Channel(k)}}$ is the minimum guard band for carrier k according to Table 5.3.3-1 for the said $\mu$ value. + +For intra-band non-contiguous carrier aggregation *Sub-block Bandwidth* and *Sub-block edges* are defined as follows, see Figure 5.3A.2-2. + +![Figure 5.3A.2-2: Definition of sub-block bandwidth for intra-band non-contiguous spectrum. The diagram shows two sub-blocks, 'Sub block n' and 'Sub block n+1', separated by a gap. Each sub-block contains multiple component carriers (CCs) represented by vertical bars. For 'Sub block n', the leftmost CC is labeled 'Transmission Bandwidth Configuration of the lowest carrier in a sub-block (RB)' and the rightmost is 'Transmission Bandwidth Configuration of the highest carrier in a sub-block'. The total width of the sub-block is labeled 'Sub-block Bandwidth, BW_Channel.block n (MHz)'. Frequency markers include F_edge.block n,low, F_C.block n,low, F_C.block n,high, and F_edge.block n,high. Frequency offsets F_offset,low and F_offset,high are indicated between the edge and carrier frequencies. The same structure is shown for 'Sub block n+1'.](1c29dadab94c3fa552d270434db09c81_img.jpg) + +Figure 5.3A.2-2: Definition of sub-block bandwidth for intra-band non-contiguous spectrum. The diagram shows two sub-blocks, 'Sub block n' and 'Sub block n+1', separated by a gap. Each sub-block contains multiple component carriers (CCs) represented by vertical bars. For 'Sub block n', the leftmost CC is labeled 'Transmission Bandwidth Configuration of the lowest carrier in a sub-block (RB)' and the rightmost is 'Transmission Bandwidth Configuration of the highest carrier in a sub-block'. The total width of the sub-block is labeled 'Sub-block Bandwidth, BW\_Channel.block n (MHz)'. Frequency markers include F\_edge.block n,low, F\_C.block n,low, F\_C.block n,high, and F\_edge.block n,high. Frequency offsets F\_offset,low and F\_offset,high are indicated between the edge and carrier frequencies. The same structure is shown for 'Sub block n+1'. + +**Figure 5.3A.2-2: Definition of sub-block bandwidth for intra-band non-contiguous spectrum** + +The lower sub-block edge of the Sub-block Bandwidth ( $\text{BW}_{\text{Channel.block}}$ ) is defined as + +$$F_{\text{edge.block,low}} = F_{\text{C.block,low}} - F_{\text{offset,low}}$$ + +The upper sub-block edge of the Sub-block Bandwidth is defined as + +$$F_{\text{edge.block,high}} = F_{\text{C.block,high}} + F_{\text{offset,high}}$$ + +The Sub-block Bandwidth, $\text{BW}_{\text{Channel.block}}$ , is defined as follows: + +$$\text{BW}_{\text{Channel.block}} = F_{\text{edge.block,high}} - F_{\text{edge.block,low}} \text{ (MHz)}$$ + +The lower and upper frequency offsets $F_{\text{offset.block,low}}$ and $F_{\text{offset.block,high}}$ depend on the transmission bandwidth configurations of the lowest and highest assigned edge component carriers within a sub-block and are defined as + +$$F_{\text{offset.block,low}} = (N_{\text{RB,low}} * 12 + 1) * \text{SCS}_{\text{low}} / 2 + \text{BW}_{\text{GB}} \text{ (MHz)}$$ + +$$F_{\text{offset.block,high}} = (N_{\text{RB,high}} * 12 - 1) * \text{SCS}_{\text{high}} / 2 + \text{BW}_{\text{GB}} \text{ (MHz)}$$ + +$$\text{BW}_{\text{GB}} = \max(\text{BW}_{\text{GB,Channel(k)}})$$ + +where $N_{\text{RB,low}}$ and $N_{\text{RB,high}}$ are the transmission bandwidth configurations according to Table 5.3.2-1 for the lowest and highest assigned component carrier within a sub-block, respectively. $\text{SCS}_{\text{low}}$ and $\text{SCS}_{\text{high}}$ are the sub-carrier spacing for the lowest and highest assigned component carrier within a sub-block, respectively. $\text{SCS}_{\text{low}}$ , $\text{SCS}_{\text{high}}$ , $N_{\text{RB,low}}$ , $N_{\text{RB,high}}$ , and + +$BW_{GB,Channel(k)}$ use the largest $\mu$ value among the subcarrier spacing configurations supported in the operating band for both of the channel bandwidths according to Table 5.3.5-1 and $BW_{GB,Channel(k)}$ is the minimum guard band for carrier k according to Table 5.3.3-1 for the said $\mu$ value. + +The sub-block gap size between two consecutive sub-blocks $W_{gap}$ is defined as + +$$W_{gap} = F_{edge,block\ n+1,low} - F_{edge,block\ n,high} \text{ (MHz)}$$ + +### 5.3A.3 RB alignment with different numerologies for CA + +### 5.3A.4 UE channel bandwidth per operating band for CA + +For intra-band contiguous carrier aggregation, a carrier aggregation configuration is a single operating band supporting a carrier aggregation bandwidth class with associated bandwidth combination sets specified in clause 5.5A.1. For each carrier aggregation configuration, requirements are specified for all aggregated channel bandwidths contained in a bandwidth combination set, UE can indicate support of several bandwidth combination sets per carrier aggregation configuration. The requirements are applicable only when Uplink CCs are configured within the frequency range between lower edge of lowest downlink component carrier and upper edge of highest downlink component carrier. + +For intra-band non-contiguous carrier aggregation, a carrier aggregation configuration is a single operating band supporting two or more sub-blocks, each supporting a carrier aggregation bandwidth class. The requirements are applicable only when Uplink CCs in each UL sub-block are configured within the frequency range between lower edge of lowest downlink component carrier and upper edge of highest downlink component carrier of a DL sub-block. + +Frequency separation class (Fs) specified in Table 5.3A.4-2 indicates the maximum frequency span between lower edge of lowest component carrier and upper edge of highest component carrier that UE can support per band in downlink or uplink (DL Fs or UL Fs) respectively in non-contiguous intra-band operation within the bidirectional spectrum. + +The DL-only frequency spectrum is the width of UE frequency spectrum available to network to configure DL CCs only, and it extends on one-side of the bidirectional spectrum in contiguous manner with no frequency gap between the two. Frequency separation class for DL-only spectrum (Fsd) specified in Table 5.3A.4-3 and is declared per band. The frequency separation class for DL-only spectrum (Fsd) can be equal but not larger than the frequency separation (DL Fs). The combined downlink spectrum (DL Fs + Fsd) cannot exceed 2400 MHz. A UE may configure DL-only spectrum only if the combined downlink spectrum (DL Fs + Fsd) exceeds 1400 MHz. When a UE configures DL-only spectrum, it shall not expect a CC to be configured across the boundary between bidirectional spectrum and DL-only spectrum UE can support respectively. + +For inter-band carrier aggregation, a carrier aggregation configuration is a combination of operating bands, each supporting a carrier aggregation bandwidth class. + +**Table 5.3A.4-1: CA bandwidth classes** + +| NR CA bandwidth class | Aggregated channel bandwidth | Number of contiguous CC | Fallback group | +|-----------------------|-----------------------------------------------------------------------|-------------------------|----------------| +| A | $BW_{\text{Channel}} \leq 400 \text{ MHz}$ | 1 | 1,2,3,4,5 | +| B | $400 \text{ MHz} < BW_{\text{Channel\_CA}} \leq 800 \text{ MHz}$ | 2 | 1 | +| C | $800 \text{ MHz} < BW_{\text{Channel\_CA}} \leq 1200 \text{ MHz}$ | 3 | | +| V (Note 4) | $1200 \text{ MHz} < BW_{\text{Channel\_CA}} \leq 1600 \text{ MHz}$ | 4 | | +| W (Note 4) | $1600 \text{ MHz} < BW_{\text{Channel\_CA}} \leq 2000 \text{ MHz}$ | 5 | | +| D | $200 \text{ MHz} < BW_{\text{Channel\_CA}} \leq 400 \text{ MHz}$ | 2 | 2 | +| E | $400 \text{ MHz} < BW_{\text{Channel\_CA}} \leq 600 \text{ MHz}$ | 3 | | +| F | $600 \text{ MHz} < BW_{\text{Channel\_CA}} \leq 800 \text{ MHz}$ | 4 | | +| R | $800 \text{ MHz} < BW_{\text{Channel\_CA}} \leq 1000 \text{ MHz}$ | 5 | | +| S | $1000 \text{ MHz} < BW_{\text{Channel\_CA}} \leq 1200 \text{ MHz}$ | 6 | | +| T | $1200 \text{ MHz} < BW_{\text{Channel\_CA}} \leq 1400 \text{ MHz}$ | 7 | | +| U | $1400 \text{ MHz} < BW_{\text{Channel\_CA}} \leq 1600 \text{ MHz}$ | 8 | | +| G | $100 \text{ MHz} < BW_{\text{Channel\_CA}} \leq 200 \text{ MHz}$ | 2 | 3 | +| H | $200 \text{ MHz} < BW_{\text{Channel\_CA}} \leq 300 \text{ MHz}$ | 3 | | +| I | $300 \text{ MHz} < BW_{\text{Channel\_CA}} \leq 400 \text{ MHz}$ | 4 | | +| J | $400 \text{ MHz} < BW_{\text{Channel\_CA}} \leq 500 \text{ MHz}$ | 5 | | +| K | $500 \text{ MHz} < BW_{\text{Channel\_CA}} \leq 600 \text{ MHz}$ | 6 | | +| L | $600 \text{ MHz} < BW_{\text{Channel\_CA}} \leq 700 \text{ MHz}$ | 7 | | +| M | $700 \text{ MHz} < BW_{\text{Channel\_CA}} \leq 800 \text{ MHz}$ | 8 | | +| O | $100 \text{ MHz} \leq BW_{\text{Channel\_CA}} \leq 200 \text{ MHz}$ | 2 | 4 | +| P | $150 \text{ MHz} \leq BW_{\text{Channel\_CA}} \leq 300 \text{ MHz}$ | 3 | | +| Q | $200 \text{ MHz} \leq BW_{\text{Channel\_CA}} \leq 400 \text{ MHz}$ | 4 | | +| R2 | $200 \text{ MHz} \leq BW_{\text{Channel\_CA}} \leq 400 \text{ MHz}$ | 2 | 5 | +| R3 | $300 \text{ MHz} \leq BW_{\text{Channel\_CA}} \leq 600 \text{ MHz}$ | 3 | | +| R4 | $400 \text{ MHz} \leq BW_{\text{Channel\_CA}} \leq 800 \text{ MHz}$ | 4 | | +| R5 | $500 \text{ MHz} \leq BW_{\text{Channel\_CA}} \leq 1000 \text{ MHz}$ | 5 | | +| R6 | $600 \text{ MHz} \leq BW_{\text{Channel\_CA}} \leq 1200 \text{ MHz}$ | 6 | | +| R7 | $700 \text{ MHz} \leq BW_{\text{Channel\_CA}} \leq 1400 \text{ MHz}$ | 7 | | +| R8 | $800 \text{ MHz} \leq BW_{\text{Channel\_CA}} \leq 1600 \text{ MHz}$ | 8 | | +| R9 | $900 \text{ MHz} \leq BW_{\text{Channel\_CA}} \leq 1800 \text{ MHz}$ | 9 | | +| R10 | $1000 \text{ MHz} \leq BW_{\text{Channel\_CA}} \leq 2000 \text{ MHz}$ | 10 | | +| R11 | $1100 \text{ MHz} \leq BW_{\text{Channel\_CA}} \leq 2200 \text{ MHz}$ | 11 | | +| R12 | $1200 \text{ MHz} \leq BW_{\text{Channel\_CA}} \leq 2400 \text{ MHz}$ | 12 | | + +NOTE 1: Maximum supported component carrier bandwidths for fallback groups 1, 2, 3, 4 and 5 are 400 MHz, 200 MHz, 100 MHz, 100 MHz and 200 MHz respectively except for CA bandwidth class A. For CA bandwidth classes of fallback groups 1, 2, 3, 4 and 5, the minimum requirements apply for the cases in which each CA bandwidth class consists of up to two contiguous blocks of spectrum each with one or more contiguous component carriers of a single channel bandwidth. + +NOTE 2: It is mandatory for a UE to be able to fallback to lower order CA bandwidth class configuration within a fallback group. 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. + +NOTE 3: In this release of the specification, the minimum requirements for intra-band contiguous CA configurations apply for aggregated channel bandwidths up to 1600 MHz for FR2-1 (this note is not relevant for UE capability parsing by the network). + +NOTE 4: This bandwidth class is applicable only for operating bands within FR2-2. + +**Table 5.3A.4-2: Frequency separation classes for non-contiguous intra-band operation** + +| Frequency separation class | Max. allowed frequency separation (Fs) | +|-------------------------------------------------------------------------------------|----------------------------------------| +| I | 800 MHz | +| II | 1200 MHz | +| III | 1400 MHz | +| IV | 1000 MHz | +| V | 1600 MHz | +| VI | 1800 MHz | +| VII | 2000 MHz | +| VIII | 2200 MHz | +| IX | 2400 MHz | +| X | 400 MHz | +| XI | 600 MHz | +| NOTE 1: Fs values larger than 1400 MHz apply only to downlink frequency separation. | | + +**Table 5.3A.4-3: Frequency separation classes for DL-only spectrum** + +| Frequency separation class | Max. allowed frequency separation (Fsd) | +|----------------------------|-----------------------------------------| +| I | 200 MHz | +| II | 400 MHz | +| III | 600 MHz | +| IV | 800 MHz | +| V | 1000 MHz | +| VI | 1200 MHz | + +## 5.3D Channel bandwidth for UL MIMO + +The requirements specified in clause 5.3 are applicable to UE supporting UL MIMO. + +## 5.3K Channel bandwidth for simultaneous reception or transmission in multiple directions + +The requirements specified in clause 5.3 are applicable to UE supporting simultaneous reception or transmission in multiple directions. + +## 5.4 Channel arrangement + +### 5.4.1 Channel spacing + +#### 5.4.1.1 Channel spacing for adjacent NR carriers + +The spacing between carriers will depend on the deployment scenario, the size of the frequency block available and the channel bandwidths. The nominal channel spacing between two adjacent NR carriers is defined as following: + +For NR operating bands with 60 kHz channel raster, + +Nominal Channel spacing = $(BW_{\text{Channel}(1)} + BW_{\text{Channel}(2)})/2 + \{-20 \text{ kHz}, 0 \text{ kHz}, 20 \text{ kHz}\}$ for $\Delta F_{\text{Raster}}$ equals to 60 kHz + +Nominal Channel spacing = $(BW_{\text{Channel}(1)} + BW_{\text{Channel}(2)})/2 + \{-40 \text{ kHz}, 0 \text{ kHz}, 40 \text{ kHz}\}$ for $\Delta F_{\text{Raster}}$ equals to 120 kHz + +For operating band n263, + +$$\text{Nominal Channel spacing} = \text{ceil}((\text{BW}_{\text{Channel}(1)} + \text{BW}_{\text{Channel}(2)})/100.8) * 50.4 \text{ MHz},$$ + +where $\text{BW}_{\text{Channel}(1)}$ and $\text{BW}_{\text{Channel}(2)}$ are the channel bandwidths of the two respective NR carriers. The channel spacing can be adjusted depending on the channel raster to optimize performance in a particular deployment scenario. + +## 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 frequency* is designated by an NR Absolute Radio Frequency Channel Number (NR-ARFCN) in the range [2016667...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** + +| Frequency range (MHz) | $\Delta F_{\text{Global}}$ (kHz) | $F_{\text{REF-Offs}}$ [MHz] | $N_{\text{REF-Offs}}$ | Range of $N_{\text{REF}}$ | +|-----------------------|----------------------------------|-----------------------------|-----------------------|---------------------------| +| 24250 – 100000 | 60 | 24250.08 | 2016667 | 2016667 – 3279165 | + +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 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 UE. + +**Table 5.4.2.2-1: Channel raster to resource element mapping** + +| | $N_{\text{RB}} \bmod 2 = 0$ | $N_{\text{RB}} \bmod 2 = 1$ | +|-------------------------------------------------|-----------------------------|-----------------------------| +| Resource element index $k$ | 0 | 6 | +| Physical resource block number $n_{\text{PRB}}$ | | | + +$k$ , $n_{\text{RB}}$ , $N_{\text{RB}}$ are as defined in TS 38.211 [9]. + +### 5.4.2.3 Channel raster entries for each operating band + +The RF channel positions on the channel raster in each NR operating band are given through the applicable NR-ARFCN in Table 5.4.2.3-1, using the channel raster to resource element mapping in clause 5.4.2.2. + +- For NR operating bands with 60 kHz channel raster above 24 GHz, $\Delta F_{\text{Raster}} = I \times \Delta F_{\text{Global}}$ , where $I \in \{1, 2\}$ . Every $I^{\text{th}}$ 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 $\langle I \rangle$ . + +- In frequency bands with two $\Delta F_{\text{Raster}}$ , the higher $\Delta F_{\text{Raster}}$ applies to channels using only the SCS that equals the higher $\Delta F_{\text{Raster}}$ and the SSB SCS that is equal to or larger than the higher $\Delta F_{\text{Raster}}$ . + +**Table 5.4.2.3-1: Applicable NR-ARFCN per operating band** + +| Operating Band | $\Delta F_{\text{Raster}}$ (kHz) | Uplink and Downlink Range of $N_{\text{REF}}$ (First – – Last) | +|----------------|----------------------------------|----------------------------------------------------------------------------| +| n257 | 60 | 2054166 – <1> – 2104165 | +| | 120 | 2054167 – <2> – 2104165 | +| n258 | 60 | 2016667 – <1> – 2070832 | +| | 120 | 2016667 – <2> – 2070831 | +| n259 | 60 | 2270833 – <1> – 2337499 | +| | 120 | 2270833 – <2> – 2337499 | +| n260 | 60 | 2229166 – <1> – 2279165 | +| | 120 | 2229167 – <2> – 2279165 | +| n261 | 60 | 2070833 – <1> – 2084999 | +| | 120 | 2070833 – <2> – 2084999 | +| n262 | 60 | 2399166 – <1> – 2415832 | +| | 120 | 2399167 – <2> – 2415831 | +| n263 | 120 | See Table 5.4.2.3-2 | +| | 480 | | +| | 960 | | + +**Table 5.4.2.3-2: Applicable NR-ARFCN for operation in band n263** + +| Channel Bandwidth | Applicable NR-ARFCN | +|-------------------|-------------------------------------------------------------------------------| +| 100 MHz | $2564083 + 1680 \cdot N$ , $N = 0:137$ | +| 400 MHz | $2566603 + 6720 \cdot N$ , $N = 0:33$ | +| 800 MHz | $2569963 + 6720 \cdot N$ , $N = 0:32$ | +| 1600 MHz | $2576683 + 6720 \cdot N$ , $N = 0:30$ | +| 2000 MHz | $2580043 + 6720 \cdot N$ , $N = 0:29$ ,
2585083, 2655643, 2692603, 2764843 | + +## 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_{\text{REF}}$ with corresponding number GSCN. The parameters defining the $SS_{\text{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_{\text{REF}}$ is given in clause 5.4.3.2. The synchronization raster and the subcarrier spacing of the synchronization block is defined separately for each band. + +**Table 5.4.3.1-1: GSCN parameters for the global frequency raster** + +| Frequency range | SS block frequency position $SS_{\text{REF}}$ | GSCN | Range of GSCN | +|--------------------|----------------------------------------------------------------------|-------------|---------------| +| 24250 – 100000 MHz | $24250.08 \text{ MHz} + N \cdot 17.28 \text{ MHz}$ ,
$N = 0:4383$ | $22256 + N$ | 22256 – 26639 | + +### 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 [9]. + +### 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. + +**Table 5.4.3.3-1: Applicable SS raster entries per operating band** + +| NR Operating Band | SS Block SCS | SS Block pattern 1 | Range of GSCN
(First – – Last) | +|-------------------|----------------------|-------------------------------|-----------------------------------------------| +| n257 | 120 kHz | Case D | 22388 - <1> - 22558 | +| | 240 kHz | Case E | 22390 - <2> - 22556 | +| n258 | 120 kHz | Case D | 22257 - <1> - 22443 | +| | 240 kHz | Case E | 22258 - <2> - 22442 | +| n259 | 120 kHz | Case D | 23140 – <1> – 23369 | +| | 240 kHz | Case E | 23142 – <2> – 23368 | +| n260 | 120 kHz | Case D | 22995 - <1> - 23166 | +| | 240 kHz | Case E | 22996 - <2> - 23164 | +| n261 | 120 kHz | Case D | 22446 - <1> - 22492 | +| | 240 kHz | Case E | 22446 - <2> - 22490 | +| n262 | 120 kHz | Case D | 23586 – <1> – 23641 | +| | 240 kHz | Case E | 23588 – <2> – 23640 | +| n263 | 120 kHz | Case D | Table 5.4.3.3-2 | +| | 480 kHz | Case F | | +| | 960 kHz 2 | Case G | 24162 – <6> – 24954 | + +NOTE 1: SS Block pattern is defined in clause 4.1 in TS 38.213 [10]. + +NOTE 2: SS Block SCS of 960 kHz is not used for initial access. + +**Table 5.4.3.3-2: Allowed GSCN for operation in band n263 for 120 kHz and 480 kHz** + +| SS Block SCS | Range of GSCN | +|--------------|-----------------------------------------------------------| +| 120 kHz | $24156 + 6 * N - 3 * \text{floor}((N+5)/18)$ , $N=0:137$ | +| 480 kHz | $24162 + 24 * N - 12 * \text{floor}((N+4)/18)$ , $N=0:33$ | + +## 5.4A Channel arrangement for CA + +### 5.4A.1 Channel spacing for CA + +For intra-band contiguous carrier aggregation with two or more component carriers, the nominal channel spacing between two adjacent NR component carriers is defined as the following unless stated otherwise: + +For NR operating bands with 60kHz channel raster: + +with + +$$n = \mu_0 - 2$$ + +and for operating band n263: + +$$\text{Nominal Channel spacing} = \text{ceil}((\text{BW}_{\text{Channel}(1)} + \text{BW}_{\text{Channel}(2)})/100.8) * 50.4 \text{ MHz.}$$ + +where $BW_{Channel(1)}$ and $BW_{Channel(2)}$ are the channel bandwidths of the two respective NR component carriers according to Table 5.3.2-1 with values in MHz, $\mu_o$ is the largest $\mu$ value among the subcarrier spacing configurations supported in the operating band for both of the channel bandwidths according to Table 5.3.5-1, and $GB_{Channel(i)}$ is the minimum guard band for channel bandwidth $i$ according to Table 5.3.3-1 for the said $\mu$ value, with $\mu$ as defined in TS 38.211 [9]. + +The channel spacing for intra-band contiguous carrier aggregation can be adjusted to any multiple of least common multiple of channel raster and sub-carrier spacing less than the nominal channel spacing to optimize performance in a particular deployment scenario. + +For intra-band non-contiguous carrier aggregation, the channel spacing between two NR component carriers in different sub-blocks shall be larger than the nominal channel spacing defined in this clause. + +## 5.5 Configurations + +### 5.5A Configurations for CA + +#### 5.5A.1 Configurations for intra-band contiguous CA + +**Table 5.5A.1-1: NR CA configurations, bandwidth combination sets, and fallback group defined for intra-band contiguous CA** + +| NR CA configuration / Bandwidth combination set / Fallback group | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------|--------------------------|-------------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|-----------------------------|-----|----------------| +| NR CA configuration | Uplink CA configurations | BW | BW | BW | BW | BW | BW | BW | BW | BW | BW | BW | BW | Maximum aggregated BW (MHz) | BCS | Fallback group | +| | | channel (MHz) | channel (MHz) | channel (MHz) | channel (MHz) | channel (MHz) | channel (MHz) | channel (MHz) | channel (MHz) | channel (MHz) | channel (MHz) | channel (MHz) | channel (MHz) | | | | +| CA_n257B | CA_n257B | 50, 100, 200, 400 | 400 | | | | | | | | | | | 800 | 0 | 1 | +| CA_n257C | CA_n257B | 50, 100, 200, 400 | 400 | 400 | | | | | | | | | | 1200 | 0 | | +| CA_n257D | CA_n257D | 50, 100, 200 | 200 | | | | | | | | | | | 400 | 0 | 2 | +| CA_n257E | CA_n257D/E | 50, 100, 200 | 200 | 200 | | | | | | | | | | 600 | 0 | | +| CA_n257F | CA_n257D/E/F | 50, 100, 200 | 200 | 200 | 200 | | | | | | | | | 800 | 0 | | +| CA_n257G | CA_n257G | 50, 100 | 100 | | | | | | | | | | | 200 | 0 | 3 | +| CA_n257H | CA_n257G/H | 50, 100 | 100 | 100 | | | | | | | | | | 300 | 0 | | +| CA_n257I | CA_n257G/H/I | 50, 100 | 100 | 100 | 100 | | | | | | | | | 400 | 0 | | +| CA_n257J | CA_n257G/H/I/J | 50, 100 | 100 | 100 | 100 | 100 | | | | | | | | 500 | 0 | | +| CA_n257K | CA_n257G/H/I/J/K | 50, 100 | 100 | 100 | 100 | 100 | 100 | | | | | | | 600 | 0 | | +| CA_n257L | CA_n257G/H/I/J/K/L | 50, 100 | 100 | 100 | 100 | 100 | 100 | 100 | | | | | | 700 | 0 | | +| CA_n257M | CA_n257G/H/I/J/K/L/M | 50, 100 | 100 | 100 | 100 | 100 | 100 | 100 | 100 | | | | | 800 | 0 | | +| CA_n257O | CA_n257O | 50, 100 | 50, 100 | | | | | | | | | | | 200 | 0 | 4 | +| CA_n257P | CA_n257O/P | 50, 100 | 50, 100 | 50, 100 | | | | | | | | | | 300 | 0 | | +| CA_n257Q | CA_n257O/P/Q | 50, 100 | 50, 100 | 50, 100 | 50, 100 | | | | | | | | | 400 | 0 | | +| CA_n258B | CA_n258B | 50, 100, 200, 400 | 400 | | | | | | | | | | | 800 | 0 | 1 | +| CA_n258C | CA_n258B | 50, 100, 200, 400 | 400 | 400 | | | | | | | | | | 1200 | 0 | | +| CA_n258D | CA_n258D | 50, 100, 200 | 200 | | | | | | | | | | | 400 | 0 | 2 | +| CA_n258E | CA_n258D/E | 50, 100, 200 | 200 | 200 | | | | | | | | | | 600 | 0 | | +| CA_n258F | CA_n258D/E/F | 50, 100, 200 | 200 | 200 | 200 | | | | | | | | | 800 | 0 | | +| CA_n258G | CA_n258G | 50, 100 | 100 | | | | | | | | | | | 200 | 0 | 3 | +| CA_n258H | CA_n258G/H | 50, 100 | 100 | 100 | | | | | | | | | | 300 | 0 | | + +| NR CA configuration / Bandwidth combination set / Fallback group | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------|---------------------------------|-------------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|-----------------------------|-----|----------------| +| NR CA configuration n | Uplink CA configurations | BW | BW | BW | BW | BW | BW | BW | BW | BW | BW | BW | BW | Maximum aggregated BW (MHz) | BCS | Fallback group | +| | | channel (MHz) | channel (MHz) | channel (MHz) | channel (MHz) | channel (MHz) | channel (MHz) | channel (MHz) | channel (MHz) | channel (MHz) | channel (MHz) | channel (MHz) | channel (MHz) | | | | +| CA_n258I | CA_n258G/H/I | 50, 100 | 100 | 100 | 100 | | | | | | | | | 400 | 0 | | +| CA_n258J | CA_n258G/H/I/J | 50, 100 | 100 | 100 | 100 | 100 | | | | | | | | 500 | 0 | | +| CA_n258K | CA_n258G/H/I/J/K | 50, 100 | 100 | 100 | 100 | 100 | 100 | | | | | | | 600 | 0 | | +| CA_n258L | CA_n258G/H/I/J/K/L | 50, 100 | 100 | 100 | 100 | 100 | 100 | 100 | | | | | | 700 | 0 | | +| CA_n258M | CA_n258G/H/I/J/K/L/M | 50, 100 | 100 | 100 | 100 | 100 | 100 | 100 | 100 | | | | | 800 | 0 | | +| CA_n258O | CA_n258O | 50, 100 | 50, 100 | | | | | | | | | | | 200 | 0 | 4 | +| CA_n258P | CA_n258O/P | 50, 100 | 50, 100 | 50, 100 | | | | | | | | | | 300 | 0 | | +| CA_n258Q | CA_n258O/P/Q | 50, 100 | 50, 100 | 50, 100 | 50, 100 | | | | | | | | | 400 | 0 | | +| CA_n258R2 | CA_n258R2 | 100, 200 | | | | | | | | | | | | 400 | 0 | 5 | +| CA_n258R3 | CA_n258R2/R3 | 100, 200 | 100, 200 | | | | | | | | | | | 600 | 0 | | +| CA_n258R4 | CA_n258R2/R3/R4 | 100, 200 | 100, 200 | 100, 200 | | | | | | | | | | 800 | 0 | | +| CA_n258R5 | CA_n258R2/R3/R4/R5 5 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | | | | | | | | | 1000 | 0 | | +| CA_n258R6 | CA_n258R2/R3/R4/R5 5 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | | | | | | | | 1200 | 0 | | +| CA_n258R7 | CA_n258R2/R3/R4/R5 5 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | | | | | | | 1400 | 0 | | +| CA_n258R8 | CA_n258R2/R3/R4/R5 5 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | | | | | | 1600 4 | 0 | | +| CA_n258R9 | CA_n258R2/R3/R4/R5 5 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | | | | | 1800 4 | 0 | | +| CA_n258R10 | CA_n258R2/R3/R4/R5 5 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | | | | 2000 4 | 0 | | +| CA_n258R11 | CA_n258R2/R3/R4/R5 5 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | | | 2200 4 | 0 | | +| CA_n258R12 | CA_n258R2/R3/R4/R5 5 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 2400 4 | 0 | | +| CA_n259B | CA_n259B | 50, 100, 200, 400 | 400 | | | | | | | | | | | 800 | 0 | 1 | +| CA_n259C | CA_n259B | 50, 100, | 400 | 400 | | | | | | | | | | 1200 | 0 | | + +| NR CA configuration / Bandwidth combination set / Fallback group | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------|-----------------------------|------------------------|----------------------------|----------------------------|----------------------------|----------------------------|------------------------|----------------------------|----------------------------|----------------------------|----------------------------|----------------------------|----------------------------|-----------------------------------|-----|-------------------| +| NR CA
configuration | Uplink CA
configurations | BW
channel
(MHz) | BW
channel
(MHz
) | BW
channel
(MHz
) | BW
channel
(MHz
) | BW
channel
(MHz
) | BW
channel
(MHz) | BW
channel
(MHz
) | BW
channel
(MHz
) | BW
channel
(MHz
) | BW
channel
(MHz
) | BW
channel
(MHz
) | BW
channel
(MHz
) | Maximum
aggregated
BW (MHz) | BCS | Fallback
group | +| | | 200, 400 | | | | | | | | | | | | | | | + +| NR CA configuration / Bandwidth combination set / Fallback group | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------|--------------------------|----------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------------|-----|----------------| +| NR CA configuration n | Uplink CA configurations | BW channel (MHz) | BW channel (MHz)
) | BW channel (MHz)
) | BW channel (MHz)
) | BW channel (MHz)
) | BW channel (MHz)
) | BW channel (MHz)
) | BW channel (MHz)
) | BW channel (MHz)
) | BW channel (MHz)
) | BW channel (MHz)
) | BW channel (MHz)
) | Maximum aggregated BW (MHz) | BCS | Fallback group | +| CA_n259G | CA_n259G | 50, 100 | 100 | | | | | | | | | | | 200 | 0 | 3 | +| CA_n259H | CA_n259G/H | 50, 100 | 100 | 100 | | | | | | | | | | 300 | 0 | | +| CA_n259I | CA_n259G/H/I | 50, 100 | 100 | 100 | 100 | | | | | | | | | 400 | 0 | | +| CA_n259J | CA_n259G/H/
I/J | 50, 100 | 100 | 100 | 100 | 100 | | | | | | | | 500 | 0 | | +| CA_n259K | CA_n259G/H/
I/J/K | 50, 100 | 100 | 100 | 100 | 100 | 100 | | | | | | | 600 | 0 | | +| CA_n259L | CA_n259G/H/
I/J/K/L | 50, 100 | 100 | 100 | 100 | 100 | 100 | 100 | | | | | | 700 | 0 | | +| CA_n259M | CA_n259G/H/
I/J/K/L/M | 50, 100 | 100 | 100 | 100 | 100 | 100 | 100 | 100 | | | | | 800 | 0 | | +| CA_n260B | CA_n260B | 50, 100,
200, 400 | 400 | | | | | | | | | | | 800 | 0 | 1 | +| CA_n260C | CA_n260B | 50, 100,
200, 400 | 400 | 400 | | | | | | | | | | 1200 | 0 | | +| CA_n260D | CA_n260D | 50, 100,
200 | 200 | | | | | | | | | | | 400 | 0 | 2 | +| CA_n260E | CA_n260D/E | 50, 100,
200 | 200 | 200 | | | | | | | | | | 600 | 0 | | +| CA_n260F | CA_n260D/E/F | 50, 100,
200 | 200 | 200 | 200 | | | | | | | | | 800 | 0 | | +| CA_n260G | CA_n260G | 50, 100 | 100 | | | | | | | | | | | 200 | 0 | 3 | +| CA_n260H | CA_n260G/H | 50, 100 | 100 | 100 | | | | | | | | | | 300 | 0 | | +| CA_n260I | CA_n260G/H/I | 50, 100 | 100 | 100 | 100 | | | | | | | | | 400 | 0 | | +| CA_n260J | CA_n260G/H/
I/J | 50, 100 | 100 | 100 | 100 | 100 | | | | | | | | 500 | 0 | | +| CA_n260K | CA_n260G/H/
I/J/K | 50, 100 | 100 | 100 | 100 | 100 | 100 | | | | | | | 600 | 0 | | +| CA_n260L | CA_n260G/H/
I/J/K/L | 50, 100 | 100 | 100 | 100 | 100 | 100 | 100 | | | | | | 700 | 0 | | +| CA_n260M | CA_n260G/H/
I/J/K/L/M | 50, 100 | 100 | 100 | 100 | 100 | 100 | 100 | 100 | | | | | 800 | 0 | | +| CA_n260O | CA_n260O | 50, 100 | 50,
100 | | | | | | | | | | | 200 | 0 | 4 | +| CA_n260P | CA_n260O/P | 50, 100 | 50,
100 | 50,
100 | | | | | | | | | | 300 | 0 | | +| CA_n260Q | CA_n260O/
P/Q | 50, 100 | 50,
100 | 50,
100 | 50,
100 | | | | | | | | | 400 | 0 | | +| CA_n260R2 | CA_n260R2 | 100, 200 | 100, | | | | | | | | | | | 400 | 0 | 5 | + +| NR CA configuration / Bandwidth combination set / Fallback group | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------|----------------------------------|---------------------------------|--------------------------------------|--------------------------------------|--------------------------------------|--------------------------------------|---------------------------------|--------------------------------------|--------------------------------------|--------------------------------------|--------------------------------------|--------------------------------------|--------------------------------------|-----------------------------------------|------------|-----------------------| +| NR CA configuratio n | Uplink CA configuration s | BW
channel
(MHz) | BW
channel
(MHz
) | BW
channel
(MHz
) | BW
channel
(MHz
) | BW
channel
(MHz
) | BW
channel
(MHz) | BW
channel
(MHz
) | BW
channel
(MHz
) | BW
channel
(MHz
) | BW
channel
(MHz
) | BW
channel
(MHz
) | BW
channel
(MHz
) | Maximum aggregate d
BW (MHz) | BCS | Fallback group | +| | | | 200 | | | | | | | | | | | | | | + +| NR CA configuration / Bandwidth combination set / Fallback group | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------|---------------------------------|-------------------|------------------|------------------|------------------|------------------|------------------|------------------|------------------|------------------|------------------|------------------|------------------|-----------------------------|-----|----------------| +| NR CA configuration n | Uplink CA configurations | BW channel (MHz) | BW channel (MHz) | BW channel (MHz) | BW channel (MHz) | BW channel (MHz) | BW channel (MHz) | BW channel (MHz) | BW channel (MHz) | BW channel (MHz) | BW channel (MHz) | BW channel (MHz) | BW channel (MHz) | Maximum aggregated BW (MHz) | BCS | Fallback group | +| CA_n260R3 | CA_n260R2/R3 | 100, 200 | 100, 200 | 100, 200 | | | | | | | | | | 600 | 0 | | +| CA_n260R4 | CA_n260R2/R3/R4 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | | | | | | | | | 800 | 0 | | +| CA_n260R5 | CA_n260R2/R3/R4/R5 5 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | | | | | | | | 1000 | 0 | | +| CA_n260R6 | CA_n260R2/R3/R4/R5 5 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | | | | | | | 1200 | 0 | | +| CA_n260R7 | CA_n260R2/R3/R4/R5 5 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | | | | | | 1400 | 0 | | +| CA_n260R8 | CA_n260R2/R3/R4/R5 5 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | | | | | 1600 4 | 0 | | +| CA_n260R9 | CA_n260R2/R3/R4/R5 5 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | | | | 1800 4 | 0 | | +| CA_n260R10 | CA_n260R2/R3/R4/R5 5 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | | | 2000 4 | 0 | | +| CA_n260R11 | CA_n260R2/R3/R4/R5 5 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | | 2200 4 | 0 | | +| CA_n260R12 | CA_n260R2/R3/R4/R5 5 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 100, 200 | 2400 4 | 0 | | +| CA_n261B | CA_n261B | 50, 100, 200, 400 | 400 | | | | | | | | | | | 800 | 0 | 1 | +| CA_n261C | CA_n261B | 50 | 400 | 400 | | | | | | | | | | 850 | 0 | 2 | +| CA_n261D | CA_n261D | 50, 100, 200 | 200 | | | | | | | | | | | 400 | 0 | | +| CA_n261E | CA_n261D/E | 50, 100, 200 | 200 | 200 | | | | | | | | | | 600 | 0 | | +| CA_n261F | CA_n261D/E/F | 50, 100, 200 | 200 | 200 | 200 | | | | | | | | | 800 | 0 | | +| CA_n261G | CA_n261G | 50, 100 | 100 | | | | | | | | | | | 200 | 0 | | +| CA_n261H | CA_n261G/H | 50, 100 | 100 | 100 | | | | | | | | | | 300 | 0 | 3 | +| CA_n261I | CA_n261G/H/I | 50, 100 | 100 | 100 | 100 | | | | | | | | | 400 | 0 | | +| CA_n261J | CA_n261G/H/I/J | 50, 100 | 100 | 100 | 100 | 100 | | | | | | | | 500 | 0 | | +| CA_n261K | CA_n261G/H/I/J/K | 50, 100 | 100 | 100 | 100 | 100 | 100 | | | | | | | 600 | 0 | | +| CA_n261L | CA_n261G/H/I/J/K/L | 50, 100 | 100 | 100 | 100 | 100 | 100 | 100 | | | | | | 700 | 0 | | +| CA_n261M | CA_n261G/H/I/J/K/L/M | 50, 100 | 100 | 100 | 100 | 100 | 100 | 100 | 100 | | | | | 800 | 0 | | + +| NR CA configuration / Bandwidth combination set / Fallback group | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------|--------------------------|------------------|------------------|------------------|------------------|------------------|------------------|------------------|------------------|------------------|------------------|------------------|------------------|-----------------------------|-----|----------------| +| NR CA configuration n | Uplink CA configurations | BW channel (MHz) | BW channel (MHz) | BW channel (MHz) | BW channel (MHz) | BW channel (MHz) | BW channel (MHz) | BW channel (MHz) | BW channel (MHz) | BW channel (MHz) | BW channel (MHz) | BW channel (MHz) | BW channel (MHz) | Maximum aggregated BW (MHz) | BCS | Fallback group | +| | I/J/K/L/M | | | | | | | | | | | | | | | | +| CA_n261O | CA_n261O | 50, 100 | 50, 100 | | | | | | | | | | | 200 | 0 | 4 | +| CA_n261P | CA_n261O/P | 50, 100 | 50, 100 | 50, 100 | | | | | | | | | | 300 | 0 | | +| CA_n261Q | CA_n261O/P/Q | 50, 100 | 50, 100 | 50, 100 | 50, 100 | | | | | | | | | 400 | 0 | | +| CA_n262G | CA_n262G | 50, 100 | 100 | | | | | | | | | | | 200 | 0 | 3 | +| CA_n262H | CA_n262G/H | 50, 100 | 100 | 100 | | | | | | | | | | 300 | 0 | | +| CA_n262I | CA_n262G/H/I | 50, 100 | 100 | 100 | 100 | | | | | | | | | 400 | 0 | | +| CA_n262J | CA_n262G/H/I/J | 50, 100 | 100 | 100 | 100 | 100 | | | | | | | | 500 | 0 | | +| CA_n262K | CA_n262G/H/I/J/K | 50, 100 | 100 | 100 | 100 | 100 | 100 | | | | | | | 600 | 0 | | +| CA_n262L | CA_n262G/H/I/J/K/L | 50, 100 | 100 | 100 | 100 | 100 | 100 | 100 | | | | | | 700 | 0 | | +| CA_n262M | CA_n262G/H/I/J/K/L/M | 50, 100 | 100 | 100 | 100 | 100 | 100 | 100 | 100 | | | | | 800 | 0 | | +| CA_n263B | CA_n263A | 400 | 400 | | | | | | | | | | | 800 | 0 | 1 | +| CA_n263C | CA_n263A | 400 | 400 | 400 | | | | | | | | | | 1200 | 0 | 1 | +| CA_n263G | CA_n263A | 100 | 100 | | | | | | | | | | | 200 | 0 | 3 | +| CA_n263H | CA_n263A | 100 | 100 | 100 | | | | | | | | | | 300 | 0 | 3 | +| CA_n263I | CA_n263A | 100 | 100 | 100 | 100 | | | | | | | | | 400 | 0 | 3 | +| CA_n263J | CA_n263A | 100 | 100 | 100 | 100 | 100 | | | | | | | | 500 | 0 | 3 | +| CA_n263K | CA_n263A | 100 | 100 | 100 | 100 | 100 | 100 | | | | | | | 600 | 0 | 3 | +| CA_n263L | CA_n263A | 100 | 100 | 100 | 100 | 100 | 100 | 100 | | | | | | 700 | 0 | 3 | +| CA_n263M | CA_n263A | 100 | 100 | 100 | 100 | 100 | 100 | 100 | 100 | | | | | 800 | 0 | 3 | + +NOTE 1: Void + +NOTE 2: For the NR CA configuration with more than two component carriers, the bandwidths in a BCS which may introduce combinations more than requested unintentionally should be listed in a row separately. + +NOTE 3: In this release of the specification, contiguous DL CA configurations within FR2-2 may only contain multiples of the same channel bandwidth. + +NOTE 4: In Rel-18 maximum aggregated downlink BW is limited to 1600 MHz. + +NOTE 5: In Rel-18 maximum aggregated uplink BW is limited to 800 MHz. + +NOTE 6: The delimiter “/” is only used in the uplink configurations for the sake of simplicity. For example, CA\_nyA/B/C denotes CA\_nyA, CA\_nyB and CA\_nyC, where ny is a FR2 NR band and A, B and C are the corresponding bandwidth classes respectively. + +## 5.5A.2 Configurations for intra-band non-contiguous CA + +Configurations listed in this clause apply to downlink carrier aggregation only. + +NOTE: Sub-blocks belonging to a CA configuration can be in any order. In other words 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. + +**Table 5.5A.2-1: NR CA configurations with single CA bandwidth class defined for intra-band non-contiguous CA** + +| NR CA configuration / Bandwidth combination set | | | | +|-------------------------------------------------|--------------------------|--------------------------------------------------|-----| +| NR configuration | Uplink CA configurations | $\Sigma(\text{BW}_{\text{Channel,block}})$ (MHz) | BCS | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|------|---| +| CA_n257(2A) | - | 800 | 0 | +| CA_n257(2G) | CA_n257(2G) | 400 | 0 | +| CA_n258(2A) | - | 800 | 0 | +| CA_n258(3A) | - | 1200 | 0 | +| CA_n258(4A) | - | 1600 | 0 | +| CA_n258(5A) | - | 2000 | 0 | +| CA_n258(2G) | CA_n258G | 400 | 0 | +| CA_n260(2A) | CA_n260(2A) | 800 | 0 | +| CA_n260(3A) | CA_n260(3A) | 1200 | 0 | +| CA_n260(4A) | - | 1600 | 0 | +| CA_n260(5A) | - | 2000 | 0 | +| CA_n260(6A) | - | 2400 | 0 | +| CA_n260(7A) | - | 2800 | 0 | +| CA_n260(8A) | - | 2900 | 0 | +| CA_n260(9A) | - | 2950 | 0 | +| CA_n260(10A) | - | 2950 | 0 | +| CA_n260(2D) | - | 800 | 0 | +| CA_n260(2G) | CA_n260G | 400 | 0 | +| CA_n260(3G) | - | 600 | 0 | +| CA_n260(4G) | - | 800 | 0 | +| CA_n260(2H) | CA_n260G/H | 600 | 0 | +| CA_n260(2O) | - | 400 | 0 | +| CA_n260(3O) | - | 600 | 0 | +| CA_n260(4O) | - | 800 | 0 | +| CA_n260(2P) | - | 600 | 0 | +| CA_n260(3P) | - | 900 | 0 | +| CA_n260(4P) | - | 1200 | 0 | +| CA_n260(2Q) | - | 800 | 0 | +| CA_n261(2A) | - | 800 | 0 | +| CA_n261(3A) | - | 800 | 0 | +| CA_n261(4A) | - | 800 | 0 | +| CA_n261(5A) | - | 800 | 0 | +| CA_n261(6A) | - | 800 | 0 | +| CA_n261(7A) | - | 800 | 0 | +| CA_n261(8A) | - | 800 | 0 | +| CA_n261(2D) | - | 800 | 0 | +| CA_n261(2G) | CA_n261G | 400 | 0 | +| CA_n261(3G) | CA_n261G | 600 | 0 | +| CA_n261(4G) | CA_n261G | 800 | 0 | +| CA_n261(2H) | CA_n261G/H | 600 | 0 | +| CA_n261(2I) | CA_n261G/H/I | 800 | 0 | +| CA_n261(2O) | - | 400 | 0 | +| CA_n261(3O) | - | 600 | 0 | +| CA_n261(4O) | - | 800 | 0 | +| CA_n261(5O) | - | 800 | 0 | +| CA_n261(6O) | - | 800 | 0 | +| CA_n261(7O) | - | 800 | 0 | +| CA_n261(2P) | - | 600 | 0 | +| CA_n261(2Q) | - | 800 | 0 | +| NOTE 1: Void | | | | +| NOTE 2: Void | | | | +| NOTE 3: Void | | | | +| NOTE 4: Void | | | | +| NOTE 5: Channel bandwidth per operating band defined in Table 5.3.5-1 | | | | +| NOTE 6: Unless otherwise stated, BCS0 is referred in each constituent CA configuration | | | | +| NOTE 7: $\sum(BW_{\text{Channel,block}})$ denotes the maximum total bandwidth from the summation of the sub-block bandwidths and shall be less than the bandwidth of the operating band. | | | | +| NOTE 8: The delimiter “/” will only be used in the uplink configurations for the sake of simplicity. For example, CA_nyA/B/C denotes CA_nyA, CA_nyB and CA_nyC, where ny is a FR2 NR band and A, B and C are the corresponding bandwidth classes respectively. | | | | + +**Table 5.5A.2-2: NR CA configurations with multiple CA bandwidth classes defined for intra-band non-contiguous CA** + +| NR CA configuration / Bandwidth combination set | | | | +|--------------------------------------------------------|--|--|--| +| | | | | + +| CA configuration | Uplink CA configurations | $\Sigma(\text{BW}_{\text{Channel,block}})$ (MHz) | BCS | +|-------------------|--------------------------|--------------------------------------------------|-----| +| CA_n257(A-G) | CA_n257G | 600 | 0 | +| CA_n257(A-D) | - | 800 | 0 | +| CA_n257(A-H) | - | 700 | 0 | +| CA_n257(A-I) | - | 800 | 0 | +| CA_n257(G-H) | - | 500 | 0 | +| CA_n257(G-I) | - | 600 | 0 | +| CA_n258(A-D) | CA_n258D | 800 | 0 | +| CA_n258(A-G) | CA_n258G | 600 | 0 | +| CA_n258(A-H) | CA_n258G/H | 700 | 0 | +| CA_n258(A-I) | - | 800 | 0 | +| CA_n258(D-G) | CA_n258D/G | 600 | 0 | +| CA_n258(G-H) | CA_n258G/H | 500 | 0 | +| CA_n258(G-I) | - | 600 | 0 | +| CA_n260(A-D) | - | 800 | 0 | +| CA_n260(A-E) | - | 1000 | 0 | +| CA_n260(2A-D) | - | 1200 | 0 | +| CA_n260(3A-D) | - | 1600 | 0 | +| CA_n260(4A-D) | - | 2000 | 0 | +| CA_n260(A-2D) | - | 1200 | 0 | +| CA_n260(2A-2D) | - | 1600 | 0 | +| CA_n260(A-D-O) | - | 1000 | 0 | +| CA_n260(A-D-G) | - | 1000 | 0 | +| CA_n260(2A-D-O) | - | 1400 | 0 | +| CA_n260(3A-D-O) | - | 1800 | 0 | +| CA_n260(A-D-2O) | - | 1200 | 0 | +| CA_n260(2A-D-2O) | CA_n260G/H | 1600 | 0 | +| CA_n260(A-G) | CA_n260G | 600 | 0 | +| CA_n260(A-G-H) | CA_n260G/H | 900 | 0 | +| CA_n260(2A-G) | CA_n260G | 1000 | 0 | +| CA_n260(A-2G) | CA_n260G | 800 | 0 | +| CA_n260(A-3G) | CA_n260G | 1000 | 0 | +| CA_n260(A-4G) | - | 1200 | 0 | +| CA_n260(2A-2G) | CA_n260G | 1200 | 0 | +| CA_n260(2A-3G) | CA_n260G | 1400 | 0 | +| CA_n260(2A-2G-O) | CA_n260G/O | 1400 | 0 | +| CA_n260(2A-2G-2O) | - | 1600 | 0 | +| CA_n260(3A-2G) | CA_n260G | 1600 | 0 | +| CA_n260(3A-2G-O) | - | 1800 | 0 | +| CA_n260(4A-G) | CA_n260G | 1800 | 0 | +| CA_n260(4A-G-O) | CA_n260G/O | 2000 | 0 | +| CA_n260(4A-2G) | CA_n260G | 2000 | 0 | +| CA_n260(5A-G) | CA_n260G | 2200 | 0 | +| CA_n260(A-2G-2O) | - | 1200 | 0 | +| CA_n260(A-2G-3O) | - | 1400 | 0 | +| CA_n260(2A-G-H) | CA_n260G/H | 1300 | 0 | +| CA_n260(2A-G-2O) | CA_n260G/O | 1400 | 0 | +| CA_n260(2A-G-3O) | - | 1600 | 0 | +| CA_n260(3A-G) | CA_n260G | 1400 | 0 | +| CA_n260(3A-G-O) | CA_n260G/O | 1600 | 0 | +| CA_n260(3A-G-2O) | - | 1800 | 0 | +| CA_n260(A-2H) | CA_n260G/H | 1000 | 0 | +| CA_n260(2A-H) | CA_n260G/H | 1100 | 0 | +| CA_n260(3A-H) | CA_n260G/H | 1500 | 0 | +| CA_n260(2A-2H) | CA_n260G/H | 1400 | 0 | +| CA_n260(A-H) | CA_n260G/H | 700 | 0 | +| CA_n260(A-H-O) | CA_n260G/H/O | 900 | 0 | +| CA_n260(A-O) | CA_n260O | 600 | 0 | +| CA_n260(A-O-P) | CA_n260O/P | 900 | 0 | +| CA_n260(A-O-P-Q) | - | 1300 | 0 | +| CA_n260(A-O-2P) | - | 1200 | 0 | +| CA_n260(A-O-3P) | - | 1500 | 0 | +| CA_n260(2A-O-P) | CA_n260O/P | 1300 | 0 | +| CA_n260(2A-O-P-Q) | - | 1700 | 0 | + +| | | | | +|--------------------|--------------|------|---| +| CA_n260(2A-O-2P) | - | 1600 | 0 | +| CA_n260(2A-O-3P) | - | 1900 | 0 | +| CA_n260(2A-2O-P) | - | 1500 | 0 | +| CA_n260(2A-2O-P-Q) | - | 1900 | 0 | +| CA_n260(A-O-Q) | CA_n260O/P/Q | 1000 | 0 | +| CA_n260(A-O-2Q) | - | 1400 | 0 | +| CA_n260(2A-O-Q) | CA_n260O/P/Q | 1400 | 0 | +| CA_n260(2A-O-2Q) | - | 1800 | 0 | +| CA_n260(2A-2O-Q) | - | 1600 | 0 | +| CA_n260(2A-O) | CA_n260O | 1000 | 0 | +| CA_n260(A-2O) | CA_n260O | 800 | 0 | +| CA_n260(A-2O-P) | CA_n260O/P | 1100 | 0 | +| CA_n260(A-2O-P-Q) | - | 1500 | 0 | +| CA_n260(A-2O-2P) | - | 1400 | 0 | +| CA_n260(A-2O-Q) | - | 1200 | 0 | +| CA_n260(A-2O-2Q) | - | 1600 | 0 | +| CA_n260(A-3O-P) | - | 1300 | 0 | +| CA_n260(A-3O-Q) | - | 1400 | 0 | +| CA_n260(2A-2O) | CA_n260O | 1200 | 0 | +| CA_n260(2A-2O-2P) | - | 1800 | 0 | +| CA_n260(2A-2O-2Q) | - | 2000 | 0 | +| CA_n260(2A-3O) | CA_n260O | 1400 | 0 | +| CA_n260(2A-3O-P) | - | 1700 | 0 | +| CA_n260(2A-3O-Q) | - | 1800 | 0 | +| CA_n260(3A-2O) | CA_n260O | 1600 | 0 | +| CA_n260(3A-2O-P) | - | 1900 | 0 | +| CA_n260(3A-2O-Q) | - | 2000 | 0 | +| CA_n260(4A-O) | CA_n260O | 1800 | 0 | +| CA_n260(4A-O-P) | - | 2100 | 0 | +| CA_n260(4A-O-Q) | - | 2200 | 0 | +| CA_n260(5A-O-P) | - | 2500 | 0 | +| CA_n260(6A-O-P) | - | 2900 | 0 | +| CA_n260(4A-3O) | - | 2200 | 0 | +| CA_n260(5A-O) | CA_n260O | 2200 | 0 | +| CA_n260(6A-O) | CA_n260O | 2600 | 0 | +| CA_n260(7A-O) | - | 2950 | 0 | +| CA_n260(8A-O) | - | 2950 | 0 | +| CA_n260(4A-2O) | CA_n260O | 2000 | 0 | +| CA_n260(4A-2Q) | - | 2400 | 0 | +| CA_n260(3A-3O) | - | 1800 | 0 | +| CA_n260(A-G-O) | CA_n260G/O | 800 | 0 | +| CA_n260(A-G-2O) | CA_n260G/O | 1000 | 0 | +| CA_n260(A-G-3O) | - | 1200 | 0 | +| CA_n260(A-G-4O) | - | 1400 | 0 | +| CA_n260(2A-G-O) | CA_n260G/O | 1200 | 0 | +| CA_n260(A-2G-O) | CA_n260G/O | 1000 | 0 | +| CA_n260(A-3G-O) | - | 1200 | 0 | +| CA_n260(A-3O) | CA_n260O | 1000 | 0 | +| CA_n260(3A-O) | CA_n260O | 1400 | 0 | +| CA_n260(3A-O-P) | CA_n260O/P | 1700 | 0 | +| CA_n260(3A-O-P-Q) | - | 2100 | 0 | +| CA_n260(3A-O-2P) | - | 2000 | 0 | +| CA_n260(3A-O-Q) | - | 1800 | 0 | +| CA_n260(3A-O-2Q) | - | 2200 | 0 | +| CA_n260(A-4O) | - | 1200 | 0 | +| CA_n260(2A-4O) | - | 1600 | 0 | +| CA_n260(3A-4O) | - | 2000 | 0 | +| CA_n260(4A-4O) | - | 2400 | 0 | +| CA_n260(5A-4O) | - | 2800 | 0 | +| CA_n260(A-P) | CA_n260O/P | 700 | 0 | +| CA_n260(A-3P) | - | 1300 | 0 | +| CA_n260(A-4P) | - | 1600 | 0 | +| CA_n260(A-P-Q) | CA_n260P/Q | 1100 | 0 | +| CA_n260(2A-P) | CA_n260O/P | 1100 | 0 | +| CA_n260(2A-P-Q) | - | 1500 | 0 | + +| | | | | +|-----------------|--------------|------|---| +| CA_n260(3A-P) | CA_n260O/P | 1500 | 0 | +| CA_n260(3A-P-Q) | - | 1900 | 0 | +| CA_n260(4A-P) | CA_n260O/P | 1900 | 0 | +| CA_n260(4A-P-Q) | - | 2300 | 0 | +| CA_n260(5A-P) | CA_n260O/P | 2300 | 0 | +| CA_n260(6A-P) | - | 2700 | 0 | +| CA_n260(7A-P) | - | 3000 | 0 | +| CA_n260(A-2P) | CA_n260O/P | 1000 | 0 | +| CA_n260(2A-2P) | CA_n260O/P | 1400 | 0 | +| CA_n260(2A-3P) | - | 1700 | 0 | +| CA_n260(2A-4P) | - | 2000 | 0 | +| CA_n260(3A-2P) | - | 1800 | 0 | +| CA_n260(3A-3P) | - | 2100 | 0 | +| CA_n260(4A-2P) | - | 2200 | 0 | +| CA_n260(5A-2P) | - | 2600 | 0 | +| CA_n260(5A-2O) | - | 2400 | 0 | +| CA_n260(6A-2O) | - | 2800 | 0 | +| CA_n260(5A-3O) | - | 2600 | 0 | +| CA_n260(6A-3O) | - | 2950 | 0 | +| CA_n260(7A-2O) | - | 2950 | 0 | +| CA_n260(7A-3O) | - | 2950 | 0 | +| CA_n260(6A-2P) | - | 2950 | 0 | +| CA_n260(8A-2O) | - | 2550 | 0 | +| CA_n260(9A-O) | - | 3000 | 0 | +| CA_n260(A-Q) | CA_n260O/P/Q | 800 | 0 | +| CA_n260(A-2Q) | - | 1200 | 0 | +| CA_n260(2A-Q) | CA_n260O/P/Q | 1200 | 0 | +| CA_n260(2A-2Q) | - | 1600 | 0 | +| CA_n260(3A-Q) | CA_n260O/P/Q | 1600 | 0 | +| CA_n260(3A-2Q) | - | 2000 | 0 | +| CA_n260(4A-Q) | CA_n260O/P/Q | 2000 | 0 | +| CA_n260(5A-Q) | - | 2400 | 0 | +| CA_n260(D-2G) | - | 800 | 0 | +| CA_n260(2D-O) | - | 1000 | 0 | +| CA_n260(D-2O) | - | 800 | 0 | +| CA_n260(A-I) | CA_n260G/H/I | 800 | 0 | +| CA_n260(D-G) | CA_n260D/G | 600 | 0 | +| CA_n260(D-H) | CA_n260D/H | 700 | 0 | +| CA_n260(D-I) | CA_n260D/I | 800 | 0 | +| CA_n260(D-O) | CA_n260D/O | 600 | 0 | +| CA_n260(D-P) | CA_n260D/P | 700 | 0 | +| CA_n260(D-Q) | CA_n260D/Q | 800 | 0 | +| CA_n260(E-O) | CA_n260E/O | 800 | 0 | +| CA_n260(E-P) | CA_n260E/P | 800 | 0 | +| CA_n260(E-Q) | CA_n260E/Q | 1000 | 0 | +| CA_n260(G-H) | CA_n260G/H | 500 | 0 | +| CA_n260(G-H-O) | CA_n260G/H/O | 700 | 0 | +| | | | | + +| | | | | +|------------------|----------------------|------|---| +| CA_n260(G-I) | CA_n260G/H/I | 600 | 0 | +| CA_n260(G-O) | CA_n260G/O | 400 | 0 | +| CA_n260(G-2O) | CA_n260G/O | 600 | 0 | +| CA_n260(2G-O) | CA_n260G/O | 600 | 0 | +| CA_n260(2G-2O) | CA_n260G/O | 800 | 0 | +| CA_n260(G-3O) | CA_n260G/O | 800 | 0 | +| CA_n260(3G-O) | CA_n260G/O | 800 | 0 | +| CA_n260(2G-3O) | - | 1000 | 0 | +| CA_n260(G-4O) | - | 1000 | 0 | +| CA_n260(2G-4O) | - | 1200 | 0 | +| CA_n260(4G-O) | - | 1000 | 0 | +| CA_n260(H-O) | CA_n260G/H/O | 500 | 0 | +| CA_n260(2H-O) | CA_n260G/H/O | 800 | 0 | +| CA_n260(O-2P) | CA_n260O/P | 800 | 0 | +| CA_n260(O-3P) | - | 1100 | 0 | +| CA_n260(O-2Q) | - | 1000 | 0 | +| CA_n260(O-P) | CA_n260O/P | 500 | 0 | +| CA_n260(O-P-Q) | - | 900 | 0 | +| CA_n260(2O-P) | CA_n260O/P | 700 | 0 | +| CA_n260(2O-P-Q) | - | 1100 | 0 | +| CA_n260(2O-2P) | - | 1000 | 0 | +| CA_n260(3O-P) | - | 900 | 0 | +| CA_n260(3O-Q) | - | 1000 | 0 | +| CA_n260(O-Q) | CA_n260O/P/Q | 600 | 0 | +| CA_n260(2O-Q) | CA_n260O/P/Q | 800 | 0 | +| CA_n260(2O-2Q) | - | 1200 | 0 | +| CA_n260(P-Q) | CA_n260O/P/Q | 700 | 0 | +| CA_n261(A-D) | - | 800 | 0 | +| CA_n261(A-E) | - | 800 | 0 | +| CA_n261(2A-D) | - | 800 | 0 | +| CA_n261(2A-D-O) | - | 800 | 0 | +| CA_n261(A-2D) | - | 800 | 0 | +| CA_n261(A-D-G) | - | 800 | 0 | +| CA_n261(A-D-H) | - | 800 | 0 | +| CA_n261(A-D-O) | - | 800 | 0 | +| CA_n261(A-D-2O) | - | 800 | 0 | +| CA_n261(A-G) | CA_n261G | 600 | 0 | +| CA_n261(A-G-H) | CA_n261G/H | 800 | 0 | +| CA_n261(A-G-I) | CA_n261G/H/I | 800 | 0 | +| CA_n261(A-G-O) | CA_n261G | 800 | 0 | +| CA_n261(2A-G-O) | CA_n261G | 800 | 0 | +| CA_n261(A-G-2O) | CA_n261G | 800 | 0 | +| CA_n261(2A-G-2O) | CA_n261G | 800 | 0 | +| CA_n261(A-2G-O) | CA_n261G | 800 | 0 | +| CA_n261(A-2G-2O) | - | 800 | 0 | +| CA_n261(A-3G) | CA_n261G | 800 | 0 | +| CA_n261(A-3G-O) | - | 800 | 0 | +| CA_n261(A-2G) | CA_n261G | 800 | 0 | +| CA_n261(A-4G) | - | 800 | 0 | +| CA_n261(A-H) | CA_n261G/H | 700 | 0 | +| CA_n261(A-2H) | CA_n261G/H | 800 | 0 | +| CA_n261(A-H-I) | CA_n261G/H/I | 800 | 0 | +| CA_n261(A-I) | CA_n261G/H/I | 800 | 0 | +| CA_n261(A-2I) | - | 800 | 0 | +| CA_n261(A-J) | CA_n261G/H/I/J | 700 | 0 | +| CA_n261(A-K) | CA_n261G/H/I/J/K | 800 | 0 | +| CA_n261(A-L) | CA_n261A/G/H/I/J/K/L | 800 | 0 | +| CA_n261(A-O) | - | 600 | 0 | +| CA_n261(A-O-P) | - | 800 | 0 | +| CA_n261(A-O-Q) | - | 800 | 0 | +| CA_n261(2A-O) | - | 800 | 0 | +| CA_n261(A-2O) | - | 800 | 0 | +| CA_n261(A-3O) | - | 800 | 0 | +| CA_n261(A-4O) | - | 800 | 0 | + +| | | | | +|------------------|--------------|-----|---| +| CA_n261(A-5O) | - | 800 | 0 | +| CA_n261(A-6O) | - | 800 | 0 | +| CA_n261(A-7O) | - | 800 | 0 | +| CA_n261(A-P) | - | 700 | 0 | +| CA_n261(A-P-Q) | - | 800 | 0 | +| CA_n261(2A-P) | - | 800 | 0 | +| CA_n261(A-2P) | - | 800 | 0 | +| CA_n261(A-Q) | - | 800 | 0 | +| CA_n261(2A-Q) | - | 800 | 0 | +| CA_n261(A-2Q) | - | 800 | 0 | +| CA_n261(2A-G) | CA_n261G | 800 | 0 | +| CA_n261(2A-2G) | CA_n261G | 800 | 0 | +| CA_n261(2A-2G-O) | CA_n261G | 800 | 0 | +| CA_n261(2A-3G) | CA_n261G | 800 | 0 | +| CA_n261(2A-2O) | - | 800 | 0 | +| CA_n261(2A-3O) | - | 800 | 0 | +| CA_n261(2A-4O) | - | 800 | 0 | +| CA_n261(2A-5O) | - | 800 | 0 | +| CA_n261(2A-6O) | - | 800 | 0 | +| CA_n261(2A-H) | CA_n261G/H | 800 | 0 | +| CA_n261(2A-I) | CA_n261G/H/I | 800 | 0 | +| CA_n261(3A-G) | CA_n261G | 800 | 0 | +| CA_n261(3A-G-O) | CA_n261G | 800 | 0 | +| CA_n261(3A-2G) | CA_n261G | 800 | 0 | +| CA_n261(3A-D) | - | 800 | 0 | +| CA_n261(3A-O) | - | 800 | 0 | +| CA_n261(3A-2O) | - | 800 | 0 | +| CA_n261(3A-3O) | - | 800 | 0 | +| CA_n261(3A-4O) | - | 800 | 0 | +| CA_n261(3A-5O) | - | 800 | 0 | +| CA_n261(4A-G) | CA_n261G | 800 | 0 | +| CA_n261(4A-O) | - | 800 | 0 | +| CA_n261(4A-2O) | - | 800 | 0 | +| CA_n261(4A-3O) | - | 800 | 0 | +| CA_n261(4A-4O) | - | 800 | 0 | +| CA_n261(5A-O) | - | 800 | 0 | +| CA_n261(5A-2O) | - | 800 | 0 | +| CA_n261(5A-3O) | - | 800 | 0 | +| CA_n261(6A-O) | - | 800 | 0 | +| CA_n261(6A-2O) | - | 800 | 0 | +| CA_n261(7A-O) | - | 800 | 0 | +| CA_n261(D-G) | CA_n261D/G | 600 | 0 | +| CA_n261(D-H) | CA_n261D/H | 700 | 0 | +| CA_n261(D-I) | CA_n261D/I | 800 | 0 | +| CA_n261(D-O) | CA_n261D/O | 600 | 0 | +| CA_n261(D-2O) | - | 800 | 0 | +| CA_n261(D-P) | CA_n261D/P | 700 | 0 | +| CA_n261(D-Q) | CA_n261D/Q | 800 | 0 | +| CA_n261(E-O) | CA_n261E/O | 800 | 0 | +| CA_n261(E-P) | CA_n261E/P | 800 | 0 | +| | | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|-----|---| +| CA_n261(E-Q) | CA_n261E/Q | 800 | 0 | +| CA_n261(G-I) | CA_n261G/H/I | 600 | 0 | +| CA_n261(G-H) | CA_n261G/H | 500 | 0 | +| CA_n261(G-J) | CA_n261A/G/H/I/J | 700 | 0 | +| CA_n261(2G-2O) | CA_n261G | 800 | 0 | +| CA_n261(G-O) | CA_n261G | 400 | 0 | +| CA_n261(G-2O) | CA_n261G | 600 | 0 | +| CA_n261(2G-O) | CA_n261G | 600 | 0 | +| CA_n261(3G-O) | CA_n261G | 800 | 0 | +| CA_n261(H-I) | CA_n261G/H/I | 700 | 0 | +| CA_n261(O-P) | - | 500 | 0 | +| CA_n261(O-Q) | - | 600 | 0 | +| CA_n261(P-Q) | - | 700 | 0 | +| NOTE 1: Void | | | | +| NOTE 2: Void | | | | +| NOTE 3: Channel bandwidth per operating band defined in Table 5.3.5-1 | | | | +| NOTE 4: Configurations for intra-band contiguous CA defined in Table 5.5A.1-1 | | | | +| NOTE 5: Configurations for intra-band non-contiguous CA defined in Table 5.5A.2-1 | | | | +| NOTE 6: Void | | | | +| NOTE 7: Unless otherwise stated, BCS0 is referred in each constituent CA configuration. | | | | +| NOTE 8: $\Sigma(BW_{Channel,block})$ denotes the maximum total bandwidth from the summation of the sub-block bandwidths and shall be less than the bandwidth of the operating band. | | | | +| NOTE 9: The delimiter ‘/’ is only used in the uplink configurations for the sake of simplicity. For example, CA_nyA/B/C denotes CA_nyA, CA_nyB and CA_nyC, where ny is a FR2 NR band and A, B and C are the corresponding bandwidth classes respectively. | | | | + +### 5.5A.3 Configurations for inter-band CA + +**Table 5.5A.3-1: NR CA configurations for inter-band CA** + +| NR CA configuration | Uplink CA configuration | NR Band | Channel bandwidth (MHz) (NOTE 1) | Bandwidth combination set | +|---------------------|-------------------------|---------|----------------------------------|---------------------------| +| CA_n257A-n259A | CA_n257A-n259A | n257 | 50, 100, 200, 400 | 0 | +| | | n259 | 50, 100, 200, 400 | | +| CA_n257A-n259G | CA_n257A-n259A | n257 | 50, 100, 200, 400 | 0 | +| | | n259 | CA_n259G | | +| CA_n257A-n259H | CA_n257A-n259A | n257 | 50, 100, 200, 400 | 0 | +| | | n259 | CA_n259H | | +| CA_n257A-n259I | CA_n257A-n259A | n257 | 50, 100, 200, 400 | 0 | +| | | n259 | CA_n259I | | +| CA_n257A-n259J | CA_n257A-n259A | n257 | 50, 100, 200, 400 | 0 | +| | | n259 | CA_n259J | | +| CA_n257A-n259K | CA_n257A-n259A | n257 | 50, 100, 200, 400 | 0 | +| | | n259 | CA_n259K | | +| CA_n257A-n259L | CA_n257A-n259A | n257 | 50, 100, 200, 400 | 0 | +| | | n259 | CA_n259L | | +| CA_n257A-n259M | CA_n257A-n259A | n257 | 50, 100, 200, 400 | 0 | +| | | n259 | CA_n259M | | +| CA_n257G-n259A | CA_n257A-n259A | n257 | CA_n257G | 0 | +| | | n259 | 50, 100, 200, 400 | | +| CA_n257G-n259G | CA_n257A-n259A | n257 | CA_n257G | 0 | +| | | n259 | CA_n259G | | +| CA_n257G-n259H | CA_n257A-n259A | n257 | CA_n257G | 0 | +| | | n259 | CA_n259H | | +| CA_n257G-n259I | CA_n257A-n259A | n257 | CA_n257G | 0 | +| | | n259 | CA_n259I | | +| CA_n257G-n259J | CA_n257A-n259A | n257 | CA_n257G | 0 | +| | | n259 | CA_n259J | | +| CA_n257G-n259K | CA_n257A-n259A | n257 | CA_n257G | 0 | +| | | n259 | CA_n259K | | +| CA_n257G-n259L | CA_n257A-n259A | n257 | CA_n257G | 0 | +| | | n259 | CA_n259L | | +| CA_n257G-n259M | CA_n257A-n259A | n257 | CA_n257G | 0 | +| | | n259 | CA_n259M | | +| CA_n257H-n259A | CA_n257A-n259A | n257 | CA_n257H | 0 | +| | | n259 | 50, 100, 200, 400 | | +| CA_n257H-n259G | CA_n257A-n259A | n257 | CA_n257H | 0 | +| | | n259 | CA_n259G | | +| CA_n257H-n259H | CA_n257A-n259A | n257 | CA_n257H | 0 | +| | | n259 | CA_n259H | | +| CA_n257H-n259I | CA_n257A-n259A | n257 | CA_n257H | 0 | +| | | n259 | CA_n259I | | +| CA_n257H-n259J | CA_n257A-n259A | n257 | CA_n257H | 0 | +| | | n259 | CA_n259J | | +| CA_n257H-n259K | CA_n257A-n259A | n257 | CA_n257H | 0 | +| | | n259 | CA_n259K | | +| CA_n257H-n259L | CA_n257A-n259A | n257 | CA_n257H | 0 | +| | | n259 | CA_n259L | | +| CA_n257H-n259M | CA_n257A-n259A | n257 | CA_n257H | 0 | +| | | n259 | CA_n259M | | +| CA_n257I-n259A | CA_n257A-n259A | n257 | CA_n257I | 0 | +| | | n259 | 50, 100, 200, 400 | | +| CA_n257I-n259G | CA_n257A-n259A | n257 | CA_n257I | 0 | +| | | n259 | CA_n259G | | +| CA_n257I-n259H | CA_n257A-n259A | n257 | CA_n257I | 0 | +| | | n259 | CA_n259H | | +| CA_n257I-n259I | CA_n257A-n259A | n257 | CA_n257I | 0 | +| | | n259 | CA_n259I | | +| CA_n257I-n259J | CA_n257A-n259A | n257 | CA_n257I | 0 | +| | | n259 | CA_n259J | | +| CA_n257I-n259K | CA_n257A-n259A | n257 | CA_n257I | 0 | +| | | n259 | CA_n259K | | +| CA_n257I-n259L | CA_n257A-n259A | n257 | CA_n257I | 0 | +| | | n259 | CA_n259L | | + +| | | | | | +|--------------------|----------------------------|------|-------------------|---| +| CA_n257I-n259M | CA_n257A-n259A | n257 | CA_n257I | 0 | +| | | n259 | CA_n259M | | +| CA_n258A-n260A | - | n258 | 50, 100, 200, 400 | 0 | +| | | n260 | 50, 100, 200, 400 | | +| CA_n258A-n260G | CA_n260G | n258 | 50, 100, 200, 400 | 0 | +| | | n260 | CA_n260G | | +| CA_n258A-n260H | CA_n260G/H | n258 | 50, 100, 200, 400 | 0 | +| | | n260 | CA_n260H | | +| CA_n258A-n260I | CA_n260G/H/I | n258 | 50, 100, 200, 400 | 0 | +| | | n260 | CA_n260I | | +| CA_n258G-n260A | CA_n258G | n258 | CA_n258G | 0 | +| | | n260 | 50, 100, 200, 400 | | +| CA_n258G-n260G | CA_n258G
CA_n260G | n258 | CA_n258G | 0 | +| | | n260 | CA_n260G | | +| CA_n258G-n260H | CA_n258G
CA_n260G/H | n258 | CA_n258G | 0 | +| | | n260 | CA_n260H | | +| CA_n258G-n260I | CA_n258G
CA_n260G/H/I | n258 | CA_n258G | 0 | +| | | n260 | CA_n260I | | +| CA_n258H-n260A | CA_n258G/H | n258 | CA_n258H | 0 | +| | | n260 | 50, 100, 200, 400 | | +| CA_n258H-n260G | CA_n258G/H
CA_n260G | n258 | CA_n258H | 0 | +| | | n260 | CA_n260G | | +| CA_n258H-n260H | CA_n258G/H
CA_n260G/H | n258 | CA_n258H | 0 | +| | | n260 | CA_n260H | | +| CA_n258H-n260I | CA_n258G/H
CA_n260G/H/I | n258 | CA_n258H | 0 | +| | | n260 | CA_n260I | | +| CA_n258(2A)-n260A | - | n258 | CA_n258(2A) | 0 | +| | | n260 | 50, 100, 200, 400 | | +| CA_n258(2A)-n260G | CA_n260G | n258 | CA_n258(2A) | 0 | +| | | n260 | CA_n260G | | +| CA_n258(2A)-n260H | CA_n260G/H | n258 | CA_n258(2A) | 0 | +| | | n260 | CA_n260H | | +| CA_n258(2A)-n260I | CA_n260G/H/I | n258 | CA_n258(2A) | 0 | +| | | n260 | CA_n260I | | +| CA_n258(A-G)-n260A | CA_n258G | n258 | CA_n258(A-G) | 0 | +| | | n260 | 50, 100, 200, 400 | | +| CA_n258(A-G)-n260G | CA_n258G
CA_n260G | n258 | CA_n258(A-G) | 0 | +| | | n260 | CA_n260G | | +| CA_n258(A-G)-n260H | CA_n258G
CA_n260G/H | n258 | CA_n258(A-G) | 0 | +| | | n260 | CA_n260H | | +| CA_n258(A-G)-n260I | CA_n258G
CA_n260G/H/I | n258 | CA_n258(A-G) | 0 | +| | | n260 | CA_n260I | | +| CA_n258(2G)-n260A | CA_n258G | n258 | CA_n258(2G) | 0 | +| | | n260 | 50, 100, 200, 400 | | +| CA_n258(2G)-n260G | CA_n258G
CA_n260G | n258 | CA_n258(2G) | 0 | +| | | n260 | CA_n260G | | +| CA_n258(2G)-n260H | CA_n258G
CA_n260G/H | n258 | CA_n258(2G) | 0 | +| | | n260 | CA_n260H | | +| CA_n258(2G)-n260I | CA_n258G
CA_n260G/H/I | n258 | CA_n258(2G) | 0 | +| | | n260 | CA_n260I | | +| CA_n258(A-H)-n260A | CA_n258G/H | n258 | CA_n258(A-H) | 0 | +| | | n260 | 50, 100, 200, 400 | | +| CA_n258(A-H)-n260G | CA_n258G/H
CA_n260G | n258 | CA_n258(A-H) | 0 | + +| | | | | | | +|--------------------|--------------------------------------------------------|------|-------------------|---|--| +| | | n260 | CA_n260G | | | +| CA_n258(A-H)-n260H | CA_n258G/H
CA_n260G/H | n258 | CA_n258(A-H) | 0 | | +| | | n260 | CA_n260H | | | +| CA_n258(A-H)-n260I | CA_n258G/H
CA_n260G/H/I | n258 | CA_n258(A-H) | 0 | | +| | | n260 | CA_n260I | | | +| CA_n258(G-H)-n260A | CA_n258G/H | n258 | CA_n258(G-H) | 0 | | +| | | n260 | 50, 100, 200, 400 | | | +| CA_n258(G-H)-n260G | CA_n258G/H
CA_n260G | n258 | CA_n258(G-H) | 0 | | +| | | n260 | CA_n260G | | | +| CA_n258(G-H)-n260H | CA_n258G/H
CA_n260G/H | n258 | CA_n258(G-H) | 0 | | +| | | n260 | CA_n260H | | | +| CA_n258(G-H)-n260I | CA_n258G/H
CA_n260G/H/I | n258 | CA_n258(G-H) | 0 | | +| | | n260 | CA_n260I | | | +| CA_n258A-n261A | - | n258 | 50, 100, 200, 400 | 0 | | +| | | n261 | 50, 100, 200, 400 | | | +| CA_n260A-n261A | CA_n260A-n261A | n260 | 50, 100, 200, 400 | 0 | | +| | | n261 | 50, 100, 200, 400 | | | +| CA_n260A-n261G | CA_n260A-n261A
CA_n261G/H/I/J/K/
L/M | n260 | 50, 100, 200, 400 | 0 | | +| | | n261 | CA_n261G | | | +| CA_n260A-n261H | | n260 | 50, 100, 200, 400 | 0 | | +| | | n261 | CA_n261H | | | +| CA_n260A-n261I | | n260 | 50, 100, 200, 400 | 0 | | +| | | n261 | CA_n261I | | | +| CA_n260A-n261J | | n260 | 50, 100, 200, 400 | 0 | | +| | | n261 | CA_n261J | | | +| CA_n260A-n261K | | n260 | 50, 100, 200, 400 | 0 | | +| | | n261 | CA_n261K | | | +| CA_n260A-n261L | | n260 | 50, 100, 200, 400 | 0 | | +| | | n261 | CA_n261L | | | +| CA_n260A-n261M | | n260 | 50, 100, 200, 400 | 0 | | +| | | n261 | CA_n261M | | | +| CA_n260G-n261A | CA_n260A-n261A
CA_n260G
CA_n261G/H/I/J/K/
L/M | n260 | CA_n260G | 0 | | +| | | n261 | 50, 100, 200, 400 | | | +| CA_n260G-n261G | | n260 | CA_n260G | 0 | | +| | | n261 | CA_n261G | | | +| CA_n260G-n261H | | n260 | CA_n260G | 0 | | +| | | n261 | CA_n261H | | | +| CA_n260G-n261I | | n260 | CA_n260G | 0 | | +| | | n261 | CA_n261I | | | +| CA_n260G-n261J | | n260 | CA_n260G | 0 | | +| | | n261 | CA_n261J | | | +| CA_n260G-n261K | | n260 | CA_n260G | 0 | | +| | | n261 | CA_n261K | | | +| CA_n260G-n261L | | n260 | CA_n260G | 0 | | +| | | n261 | CA_n261L | | | +| CA_n260G-n261M | | n260 | CA_n260G | 0 | | +| | | n261 | CA_n261M | | | +| CA_n260H-n261A | CA_n260A-n261A | n260 | CA_n260H | 0 | | + +| | | | | | +|----------------|----------------------------------------------------------------|------|-------------------|---| +| CA_n260H-n261G | CA_n260G/H
CA_n261G/H/I/J/K/
L/M | n261 | 50, 100, 200, 400 | | +| | | n260 | CA_n260H | 0 | +| | | n261 | CA_n261G | | +| CA_n260H-n261H | | n260 | CA_n260H | 0 | +| | | n261 | CA_n261H | | +| CA_n260H-n261I | | n260 | CA_n260H | 0 | +| | | n261 | CA_n261I | | +| CA_n260H-n261J | | n260 | CA_n260H | 0 | +| | | n261 | CA_n261J | | +| CA_n260H-n261K | | n260 | CA_n260H | 0 | +| | CA_n260A-n261A
CA_n260G/H/I
CA_n261G/H/I/J/K/
L/M | n261 | CA_n261K | | +| CA_n260H-n261L | | n260 | CA_n260H | 0 | +| | | n261 | CA_n261L | | +| CA_n260H-n261M | | n260 | CA_n260H | 0 | +| | | n261 | CA_n261M | | +| CA_n260I-n261A | | n260 | CA_n260I | 0 | +| | | n261 | 50, 100, 200, 400 | | +| CA_n260I-n261G | | n260 | CA_n260I | 0 | +| | | n261 | CA_n261G | | +| CA_n260I-n261H | | n260 | CA_n260I | 0 | +| | | n261 | CA_n261H | | +| CA_n260I-n261I | | n260 | CA_n260I | 0 | +| | | n261 | CA_n261I | | +| CA_n260I-n261J | | n260 | CA_n260I | 0 | +| | | n261 | CA_n261J | | +| CA_n260I-n261K | | n260 | CA_n260I | 0 | +| | | n261 | CA_n261K | | +| CA_n260I-n261L | | n260 | CA_n260I | 0 | +| | | n261 | CA_n261L | | +| CA_n260I-n261M | | n260 | CA_n260I | 0 | +| | | n261 | CA_n261M | | +| CA_n260J-n261A | CA_n260A-n261A
CA_n260G/H/I/J
CA_n261G/H/I/J/K/L/
M | n260 | CA_n260J | 0 | +| | | n261 | 50, 100, 200, 400 | | +| CA_n260J-n261G | | n260 | CA_n260J | 0 | +| | | n261 | CA_n261G | | +| CA_n260J-n261H | | n260 | CA_n260J | 0 | +| | | n261 | CA_n261H | | +| CA_n260J-n261I | | n260 | CA_n260J | 0 | +| | | n261 | CA_n261I | | +| CA_n260J-n261J | | n260 | CA_n260J | 0 | +| | | n261 | CA_n261J | | +| CA_n260J-n261K | | n260 | CA_n260J | 0 | +| | | n261 | CA_n261K | | +| CA_n260J-n261L | | n260 | CA_n260J | 0 | +| | | n261 | CA_n261L | | +| CA_n260J-n261M | | n260 | CA_n260J | 0 | +| | | n261 | CA_n261M | | +| CA_n260K-n261A | CA_n260A-n261A
CA_n260G/H/I/J/K
CA_n261G/H/I/J/K/
L/M | n260 | CA_n260K | 0 | +| | | n261 | 50, 100, 200, 400 | | +| CA_n260K-n261G | | n260 | CA_n260K | 0 | +| | | n261 | CA_n261G | | +| CA_n260K-n261H | | n260 | CA_n260K | 0 | +| | | n261 | CA_n261H | | +| CA_n260K-n261I | | n260 | CA_n260K | 0 | +| | | n261 | CA_n261I | | +| CA_n260K-n261J | | n260 | CA_n260K | 0 | +| | | n261 | CA_n261J | | +| CA_n260K-n261K | | n260 | CA_n260K | 0 | +| | | n261 | CA_n261K | | +| CA_n260K-n261L | | n260 | CA_n260K | 0 | +| | | n261 | CA_n261L | | +| CA_n260K-n261M | | n260 | CA_n260K | 0 | +| | | n261 | CA_n261M | | +| CA_n260L-n261A | CA_n260A-n261A | n260 | CA_n260L | 0 | + +| | | | | | +|----------------|----------------------------------------------------------------|------|-------------------|---| +| CA_n260L-n261G | CA_n260G/H/I/J/K/L
CA_n261G/H/I/J/K/L/M | n261 | 50, 100, 200, 400 | | +| | | n260 | CA_n260L | 0 | +| CA_n260L-n261H | | n261 | CA_n261G | | +| | | n260 | CA_n260L | 0 | +| CA_n260L-n261I | | n261 | CA_n261H | | +| | | n260 | CA_n260L | 0 | +| CA_n260L-n261J | | n261 | CA_n261I | | +| | | n260 | CA_n260L | 0 | +| CA_n260L-n261K | | n261 | CA_n261J | | +| | | n260 | CA_n260L | 0 | +| CA_n260L-n261L | CA_n260A-n261A
CA_n260G/H/I/J/K/L/M
CA_n261G/H/I/J/K/L/M | n261 | CA_n261K | | +| | | n260 | CA_n260L | 0 | +| CA_n260L-n261M | | n261 | CA_n261L | | +| | | n260 | CA_n260L | 0 | +| CA_n260M-n261A | | n261 | CA_n261M | | +| | | n260 | CA_n260M | 0 | +| CA_n260M-n261G | | n261 | 50, 100, 200, 400 | | +| | | n260 | CA_n260M | 0 | +| CA_n260M-n261H | | n261 | CA_n261G | | +| | | n260 | CA_n260M | 0 | +| CA_n260M-n261I | | n261 | CA_n261H | | +| | | n260 | CA_n260M | 0 | +| CA_n260M-n261J | | n261 | CA_n261I | | +| | | n260 | CA_n260M | 0 | +| CA_n260M-n261K | | n261 | CA_n261J | | +| | | n260 | CA_n260M | 0 | +| CA_n260M-n261L | | n261 | CA_n261K | | +| | | n260 | CA_n260M | 0 | +| CA_n260M-n261M | | n261 | CA_n261L | | +| | | n260 | CA_n260M | 0 | +| | | n261 | CA_n261M | | + +NOTE 1: The SCS of each channel bandwidth for NR band refers to Table 5.3.5-1. + +NOTE 2: Unless otherwise stated, BCS0 is referred in each constituent CA configuration. + +NOTE 3: Void. + +NOTE 4: The delimiter “/” is only 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. + +## 5.5D Configurations for UL MIMO + +The requirements specified in clause 5.5 are applicable to UE supporting UL MIMO. + +## 5.5K Configurations for simultaneous reception or transmission in multiple directions + +The requirements specified in clause 5.5 are applicable to UE supporting simultaneous reception or transmission in multiple directions. + +## 6 Transmitter characteristics + +### 6.1 General + +Unless otherwise stated, the transmitter characteristics are specified over the air (OTA) with a single or multiple transmit chains. + +Unless otherwise stated, for power class 3 UEs, the beam correspondence side condition for SSB and CSI-RS specified in clause 6.6.4 shall apply to the transmission tests. + +Transmitter requirements for CA operation apply only when the DMRS initialization parameters (including the case when the UE applies cell ID as DMRS scrambling ID) are different across all CCs. The UE may use higher MPR values outside this limitation. + +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. + +Transmitter requirements for simultaneous transmission to multiple directions apply to the power classes 1, 2, 5, and 6 only. + +The requirements for 256 QAM apply to bands defined within the frequency spectrum range of 24.25 – 43.5 GHz for power classes 1, 2 and 5. + +### 6.2 Transmitter power + +#### 6.2.1 UE maximum output power + +##### 6.2.1.0 General + +NOTE: Power classes are specified based on the assumption of certain UE types with specific device architectures. The UE types can be found in Table 6.2.1.0-1. + +**Table 6.2.1.0-1: Assumption of UE Types** + +| UE Power class | UE type | +|-----------------------------------------------------------|----------------------------------| +| 1 | Fixed wireless access (FWA) UE | +| 2 | Vehicular UE | +| 3 | Handheld UE | +| 4 | High power non-handheld UE | +| 5 | Fixed wireless access (FWA) UE | +| 6 | High Speed Train Roof-Mounted UE | +| 7 | RedCap UE | +| Note: RedCap variants of non-RedCap UEs are not precluded | | + +Power class 3 is default power class. + +##### 6.2.1.1 UE maximum output power for power class 1 + +The following requirements define the maximum output power radiated by the UE for any transmission bandwidth within the channel bandwidth for non-CA configuration, unless otherwise stated. The period of measurement shall be at least one sub frame (1ms). The minimum output power values for EIRP are found in Table 6.2.1.1-1. The requirement is verified with the test metric of EIRP (Link=TX beam peak direction, Meas=Link angle). + +**Table 6.2.1.1-1: UE minimum peak EIRP for power class 1** + +| Operating band | Min peak EIRP (dBm) | +|---------------------------------------------------------------------------|---------------------| +| n257 | 40.0 | +| n258 | 40.0 | +| n260 | 38.0 | +| n261 | 40.0 | +| n262 | 34.2 | +| n263 | 30.6 | +| NOTE 1: Minimum peak EIRP is defined as the lower limit without tolerance | | + +The maximum output power values for TRP and EIRP are found in Table 6.2.1.1-2 below. The maximum allowed EIRP is derived from regulatory requirements [8]. The requirements are verified with the test metrics of TRP (Link=TX beam peak direction, Meas=TRP grid) in beam locked mode and EIRP (Link=TX beam peak direction, Meas=Link angle). + +**Table 6.2.1.1-2: UE maximum output power limits for power class 1** + +| Operating band | Max TRP (dBm) | Max EIRP (dBm) | +|----------------|---------------|----------------| +| n257 | 35 | 55 | +| n258 | 35 | 55 | +| n260 | 35 | 55 | +| n261 | 35 | 55 | +| n262 | 35 | 55 | +| n263 | 25 | 40 | + +The minimum EIRP at the 85th percentile of the distribution of radiated power measured over the full sphere around the UE is defined as the spherical coverage requirement and is found in Table 6.2.1.1-3 below. The requirement is verified with the test metric of EIRP (Link=Spherical coverage grid, Meas=Link angle). + +**Table 6.2.1.1-3: UE spherical coverage for power class 1** + +| Operating band | Min EIRP at 85 %-tile CDF (dBm) | +|-------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| n257 | 32.0 | +| n258 | 32.0 | +| n260 | 30.0 | +| n261 | 32.0 | +| n262 | 26.0 | +| n263 | 19.1 | +| NOTE 1: Minimum EIRP at 85 %-tile CDF is defined as the lower limit without tolerance | | +| NOTE 2: The requirements in this table are verified only under normal temperature conditions as defined in Annex E.2.1. | | + +## 6.2.1.2 UE maximum output power for power class 2 + +The following requirements define the maximum output power radiated by the UE for any transmission bandwidth within the channel bandwidth for non-CA configuration, unless otherwise stated. The period of measurement shall be at least one sub frame (1ms). The minimum output power values for EIRP are found in Table 6.2.1.2-1. The requirement is verified with the test metric of EIRP (Link=TX beam peak direction, Meas=Link angle). + +**Table 6.2.1.2-1: UE minimum peak EIRP for power class 2** + +| Operating band | Min peak EIRP (dBm) | +|---------------------------------------------------------------------------|---------------------| +| n257 | 29 | +| n258 | 29 | +| n259 | 25 | +| n261 | 29 | +| n262 | 22.9 | +| n263 | 22.7 | +| NOTE 1: Minimum peak EIRP is defined as the lower limit without tolerance | | + +The maximum output power values for TRP and EIRP are found in Table 6.2.1.2-2 below. The maximum allowed EIRP is derived from regulatory requirements [8]. The requirements are verified with the test metrics of TRP (Link=TX beam peak direction, Meas=TRP grid) in beam locked mode and EIRP (Link=TX beam peak direction, Meas=Link angle). + +**Table 6.2.1.2-2: UE maximum output power limits for power class 2** + +| Operating band | Max TRP (dBm) | Max EIRP (dBm) | +|----------------|---------------|----------------| +| n257 | 23 | 43 | +| n258 | 23 | 43 | +| n259 | 23 | 43 | +| n261 | 23 | 43 | +| n262 | 23 | 43 | +| n263 | 23 | 43 | + +The minimum EIRP at the 60th percentile of the distribution of radiated power measured over the full sphere around the UE is defined as the spherical coverage requirement and is found in Table 6.2.1.2-3 below. The requirement is verified with the test metric of EIRP (Link=Spherical coverage grid, Meas=Link angle). + +**Table 6.2.1.2-3: UE spherical coverage for power class 2** + +| Operating band | Min EIRP at 60 %-tile CDF (dBm) | +|-------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| n257 | 18.0 | +| n258 | 18.0 | +| n259 | 12.5 | +| n261 | 18.0 | +| n262 | 11.0 | +| n263 | 7.6 | +| NOTE 1: Minimum EIRP at 60 %-tile CDF is defined as the lower limit without tolerance | | +| NOTE 2: The requirements in this table are verified only under normal temperature conditions as defined in Annex E.2.1. | | + +### 6.2.1.3 UE maximum output power for power class 3 + +The following requirements define the maximum output power radiated by the UE for any transmission bandwidth within the channel bandwidth for non-CA configuration, unless otherwise stated. The period of measurement shall be at least one sub frame (1ms). In case of initial access and RRC\_INACTIVE, the cumulative period of measurement shall equal or exceed 1ms. The minimum output power values for EIRP are found in Table 6.2.1.3-1. The requirement is verified with the test metric of total component of EIRP (Link=TX beam peak direction, Meas=Link angle). The requirement for the UE which supports a single FR2 band is specified in Table 6.2.1.3-1. The requirement for the UE which supports multiple FR2 bands is specified in both Table 6.2.1.3-1 and Table 6.2.1.3-4. + +**Table 6.2.1.3-1: UE minimum peak EIRP for power class 3** + +| Operating band | Min peak EIRP (dBm) | +|------------------------------------------------------------------------------|---------------------| +| n257 | 22.4 | +| n258 | 22.4 | +| n259 | 18.7 | +| n260 | 20.6 | +| n261 | 22.4 | +| n262 | 16.0 | +| n263 | 14.1 | +| NOTE 1: Minimum peak EIRP is defined as the lower limit without tolerance | | +| NOTE 2: Void | | +| NOTE 3: Minimum peak EIRP does not apply to initial access and RRC_INACTIVE. | | + +The maximum output power values for TRP and EIRP are found on the Table 6.2.1.3-2. The max allowed EIRP is derived from regulatory requirements [8]. The requirements are verified with the test metrics of TRP (Link=TX beam peak direction, Meas=TRP grid) in beam locked mode and the total component of EIRP (Link=TX beam peak direction, Meas=Link angle). + +**Table 6.2.1.3-2: UE maximum output power limits for power class 3** + +| Operating band | Max TRP (dBm) | Max EIRP (dBm) | Max EIRP (dBm/MHz) | Notes | +|----------------|---------------|----------------|--------------------|------------------------------------------------| +| n257 | 23 | 43 | | | +| n258 | 23 | 43 | | | +| n259 | 23 | 43 | | | +| n260 | 23 | 43 | | | +| n261 | 23 | 43 | | | +| n262 | 23 | 43 | | | +| n263 | 25 | 43 | | Default for "NS_200" | +| | 25 | 40 | 23 | Applies when "NS_204" is indicated in the cell | + +The minimum EIRP at the 50th percentile of the distribution of radiated power measured over the full sphere around the UE is defined as the spherical coverage requirement and is found in Table 6.2.1.3-3 below. The requirement is verified with the test metric of the total component of EIRP (Link=Beam peak search grids, Meas=Link angle). The requirement for the UE which supports a single FR2 band is specified in Table 6.2.1.3-3. The requirement for the UE which supports multiple FR2 bands is specified in both Table 6.2.1.3-3 and Table 6.2.1.3-4. + +**Table 6.2.1.3-3: UE spherical coverage for power class 3** + +| Operating band | Min EIRP at 50 %-tile CDF (dBm) | +|-------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| n257 | 11.5 | +| n258 | 11.5 | +| n259 | 5.8 | +| n260 | 8 | +| n261 | 11.5 | +| n262 | 2.9 | +| n263 | 2.3 | +| NOTE 1: Minimum EIRP at 50 %-tile CDF is defined as the lower limit without tolerance in RRC_CONNECTED. | | +| NOTE 2: Void | | +| NOTE 3: The requirements in this table are verified only under normal temperature conditions as defined in Annex E.2.1. | | +| NOTE 4: Minimum EIRP at 50%-tile CDF is defined as the lower limit minus 2 dB in initial access and RRC_INACTIVE | | + +For the UEs that support multiple FR2 bands, minimum requirement for peak EIRP and EIRP spherical coverage in Tables 6.2.1.3-1 and 6.2.1.3-3 shall be decreased per band, respectively, by the peak EIRP relaxation parameter $\Delta MB_{P,n}$ and EIRP spherical coverage relaxation parameter $\Delta MB_{S,n}$ , as defined in Table 6.2.1.3-4.. + +**Table 6.2.1.3-4: UE multi-band relaxation factors for power class 3** + +| Band | $\Delta\text{MB}_{\text{P,n}}$ (dB) | $\Delta\text{MB}_{\text{S,n}}$ (dB) | +|-------------------------------------------------------------------------------------------------|-------------------------------------|-------------------------------------| +| n257 | 0.7 3 | 0.7 3 | +| n258 | 0.6 | 0.7 | +| n259 | 0.5 | 0.4 | +| n260 | 0.5 1 | 0.4 1 | +| n261 | 0.5 2,4 | 0.7 4 | +| n262 | 0.7 | 0.7 | +| n263 | 1.0 | 1.0 | +| Note 1: n260 peak and spherical relaxations are 0 dB for UE that exclusively supports n261+n260 | | | +| Note 2: n261 peak relaxation is 0 dB for UE that exclusively supports n261+n260 | | | +| Note 3: n257 peak and spherical relaxations are 0 dB for UE that exclusively supports n261+n257 | | | +| Note 4: n261 peak and spherical relaxations are 0 dB for UE that exclusively supports n261+n257 | | | + +#### 6.2.1.4 UE maximum output power for power class 4 + +The following requirements define the maximum output power radiated by the UE for any transmission bandwidth within the channel bandwidth for non-CA configuration, unless otherwise stated. The period of measurement shall be at least one sub frame (1ms). The minimum output power values for EIRP are found in Table 6.2.1.4-1. The requirement is verified with the test metric of EIRP (Link=TX beam peak direction, Meas=Link angle). + +**Table 6.2.1.4-1: UE minimum peak EIRP for power class 4** + +| Operating band | Min peak EIRP (dBm) | +|---------------------------------------------------------------------------|---------------------| +| n257 | 34 | +| n258 | 34 | +| n260 | 31 | +| n261 | 34 | +| n262 | 28.3 | +| NOTE 1: Minimum peak EIRP is defined as the lower limit without tolerance | | + +The maximum output power values for TRP and EIRP are found in Table 6.2.1.4-2 below. The maximum allowed EIRP is derived from regulatory requirements [8]. The requirements are verified with the test metrics of TRP (Link=TX beam peak direction, Meas=TRP grid) in beam locked mode and EIRP (Link=TX beam peak direction, Meas=Link angle). + +**Table 6.2.1.4-2: UE maximum output power limits for power class 4** + +| Operating band | Max TRP (dBm) | Max EIRP (dBm) | +|----------------|---------------|----------------| +| n257 | 23 | 43 | +| n258 | 23 | 43 | +| n260 | 23 | 43 | +| n261 | 23 | 43 | +| n262 | 23 | 43 | + +The minimum EIRP at the 20th percentile of the distribution of radiated power measured over the full sphere around the UE is defined as the spherical coverage requirement and is found in Table 6.2.1.4-3 below. The requirement is verified with the test metric of EIRP (Link=Spherical coverage grid, Meas=Link angle). + +**Table 6.2.1.4-3: UE spherical coverage for power class 4** + +| Operating band | Min EIRP at 20 %-tile CDF (dBm) | +|-------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| n257 | 25 | +| n258 | 25 | +| n260 | 19 | +| n261 | 25 | +| n262 | 16.2 | +| NOTE 1: Minimum EIRP at 20 %-tile CDF is defined as the lower limit without tolerance | | +| NOTE 2: The requirements in this table are verified only under normal temperature conditions as defined in Annex E.2.1. | | + +## 6.2.1.5 UE maximum output power for power class 5 + +The following requirements define the maximum output power radiated by the UE for any transmission bandwidth within the channel bandwidth for non-CA configuration, unless otherwise stated. The period of measurement shall be at least one sub frame (1ms). The minimum output power values for EIRP are found in Table 6.2.1.5-1. The requirement is verified with the test metric of EIRP (Link=TX beam peak direction, Meas=Link angle). + +**Table 6.2.1.5-1: UE minimum peak EIRP for power class 5** + +| Operating band | Min peak EIRP (dBm) | +|---------------------------------------------------------------------------|---------------------| +| n257 | 30 | +| n258 | 30.4 | +| n259 | 27.7 | +| NOTE 1: Minimum peak EIRP is defined as the lower limit without tolerance | | + +The maximum output power values for TRP and EIRP are found in Table 6.2.1.5-2 below. The maximum allowed EIRP is derived from regulatory requirements. The requirements are verified with the test metrics of TRP (Link=TX beam peak direction, Meas=TRP grid) in beam locked mode and EIRP (Link=TX beam peak direction, Meas=Link angle). + +**Table 6.2.1.5-2: UE maximum output power limits for power class 5** + +| Operating band | Max TRP (dBm) | Max EIRP (dBm) | +|----------------|---------------|----------------| +| n257 | 23 | 43 | +| n258 | 23 | 43 | +| n259 | 23 | 43 | + +The minimum EIRP at the 85th percentile of the distribution of radiated power measured over the full sphere around the UE is defined as the spherical coverage requirement and is found in Table 6.2.1.5-3 below. The requirement is verified with the test metric of EIRP (Link=Spherical coverage grid, Meas=Link angle). + +**Table 6.2.1.4-3: UE spherical coverage for power class 5** + +| Operating band | Min EIRP at 85 %-tile CDF (dBm) | +|-------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| n257 | 22 | +| n258 | 22.4 | +| n259 | 19.7 | +| NOTE 1: Minimum EIRP at 85 %-tile CDF is defined as the lower limit without tolerance | | +| NOTE 2: The requirements in this table are verified only under normal temperature conditions as defined in Annex E.2.1. | | + +For the UEs that support multiple FR2 bands, minimum requirement for peak EIRP and EIRP spherical coverage in Tables 6.2.1.5-1 and 6.2.1.5-3 shall be decreased per band, respectively, by the peak EIRP relaxation parameter $\Delta MB_{p,n}$ and EIRP spherical coverage relaxation parameter $\Delta MB_{s,n}$ , as defined in Table 6.2.1.5-4.. + +**Table 6.2.1.5-4: UE multi-band relaxation factors for power class 5** + +| Band | $\Delta\text{MB}_{\text{P,n}}$ (dB) | $\Delta\text{MB}_{\text{S,n}}$ (dB) | +|------|-------------------------------------|-------------------------------------| +| n257 | 0.7 | 0.7 | +| n258 | 0.7 | 0.7 | +| n259 | 0.5 | 0,5 | + +### 6.2.1.6 UE maximum output power for power class 6 + +The following requirements define the maximum output power radiated by the UE for any transmission bandwidth within the channel bandwidth for non-CA configuration, unless otherwise stated. The period of measurement shall be at least one sub frame (1ms). The minimum output power values for EIRP are found in Table 6.2.1.6-1. The requirement is verified with the test metric of EIRP (Link=TX beam peak direction, Meas=Link angle). + +**Table 6.2.1.6-1: UE minimum peak EIRP for power class 6** + +| Operating band | Min peak EIRP (dBm) | +|---------------------------------------------------------------------------|---------------------| +| n257 | 30 | +| n258 | 30.4 | +| n261 | 30 | +| NOTE 1: Minimum peak EIRP is defined as the lower limit without tolerance | | + +The maximum output power values for TRP and EIRP are found in Table 6.2.1.6-2 below. The maximum allowed EIRP is derived from regulatory requirements [8]. The requirements are verified with the test metrics of TRP (Link=TX beam peak direction, Meas=TRP grid) in beam locked mode and EIRP (Link=TX beam peak direction, Meas=Link angle). + +**Table 6.2.1.6-2: UE maximum output power limits for power class 6** + +| Operating band | Max TRP (dBm) | Max EIRP (dBm) | +|----------------|---------------|----------------| +| n257 | 23 | 43 | +| n258 | 23 | 43 | +| n261 | 23 | 43 | + +The minimum EIRP measured over the spherical coverage evaluation areas specified below is defined as the spherical coverage requirement and is found in Table 6.2.1.6-3 below. UE spherical coverage evaluation areas are found in Table 6.2.1.6-3a below, by consisting of Area-1 and Area-2, in the reference coordinate system in Annex J.1. The requirement is verified with the test metric of EIRP (Link= Spherical coverage grid, Meas=Link angle). + +**Table 6.2.1.6-3: UE spherical coverage for power class 6** + +| Operating band | Min EIRP over UE spherical coverage evaluation areas (dBm) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------| +| n257 | 20 | +| n258 | 20.4 | +| n261 | 20 | +| NOTE 1: Minimum EIRP over UE spherical coverage evaluation areas is defined as the lower limit without tolerance | | +| NOTE 2: The requirements in this table are verified only under normal temperature conditions as defined in Annex E.2.1. | | +| NOTE 3: The requirements in this table are applicable to FR2 PC6 UE with the network signalling [highSpeedMeasFlag-r17] configured as [set2] . | | + +**Table 6.2.1.6-3a: UE spherical coverage evaluation areas for power class 6** + +| | \theta range (degree) | \phi range (degree) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------|-----------------------------------------| +| Area-1 | 90 to 60 | - 37.5 to + 37.5 | +| Area-2 | 90 to 60 | 142.5 to 217.5 | +| NOTE 1: When testing power class 6 UEs, DUT orientation can be determined according to the UE spherical coverage evaluation areas, not necessarily following default alignment in Figure J.1-2 or positioning guidelines in clause J.3. | | | +| NOTE 2: High speed train deployment is expected to be w.r.t. the reference coordination system: $\theta = 90$ (degree) corresponds to the ground plane the train is running on, and $\phi = 0$ or $180$ with $\theta = 90$ are the train track directions. | | | + +For the UEs that support multiple FR2 bands, minimum requirement for peak EIRP and EIRP spherical coverage in Tables 6.2.1.6-1 and 6.2.1.6-3 shall be decreased per band, respectively, by the peak EIRP relaxation parameter $\Delta MB_{P,n}$ and EIRP spherical coverage relaxation parameter $\Delta MB_{S,n}$ , as defined in Table 6.2.1.6-4. + +**Table 6.2.1.6-4: UE multi-band relaxation factors for power class 6** + +| Band | \Delta MB_{P,n} (dB) | \Delta MB_{S,n} (dB) | +|-------------|------------------------------------------|------------------------------------------| +| n257 | 0.7 | 0.7 | +| n258 | 0.7 | 0.7 | +| n261 | 0.7 | 0.7 | + +## 6.2.1.7 UE maximum output power for power class 7 + +The following requirements define the maximum output power radiated by the UE for any transmission bandwidth within the channel bandwidth for non-CA configuration, unless otherwise stated. The period of measurement shall be at least one sub frame (1ms). The minimum output power values for EIRP are found in Table 6.2.1.7-1. The requirement is verified with the test metric of total component of EIRP (Link=TX beam peak direction, Meas=Link angle). + +**Table 6.2.1.7-1: UE minimum peak EIRP for power class 7** + +| Operating band | Min peak EIRP (dBm) | +|---------------------------------------------------------------------------|----------------------------| +| n257 | 16.4 | +| n258 | 16.4 | +| n261 | 16.4 | +| NOTE 1: Minimum peak EIRP is defined as the lower limit without tolerance | | +| NOTE 2: Void | | + +The maximum output power values for TRP and EIRP are found on the Table 6.2.1.7-2. The max allowed EIRP is derived from regulatory requirements [8]. The requirements are verified with the test metrics of TRP (Link=TX beam peak direction, Meas=TRP grid) in beam locked mode and the total component of EIRP (Link=TX beam peak direction, Meas=Link angle). + +**Table 6.2.1.7-2: UE maximum output power limits for power class 7** + +| Operating band | Max TRP (dBm) | Max EIRP (dBm) | +|-----------------------|----------------------|-----------------------| +| n257 | 23 | 43 | +| n258 | 23 | 43 | +| n261 | 23 | 43 | + +The minimum EIRP at the 50th percentile of the distribution of radiated power measured over the full sphere around the UE is defined as the spherical coverage requirement and is found in Table 6.2.1.7-3 below. The requirement is verified with the test metric of the total component of EIRP (Link=Beam peak search grids, Meas=Link angle). + +**Table 6.2.1.7-3: UE spherical coverage for power class 7** + +| Operating band | Min EIRP at 50 %-tile CDF (dBm) | +|-------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| n257 | 5.5 | +| n258 | 5.5 | +| n261 | 5.5 | +| NOTE 1: Minimum EIRP at 50 %-tile CDF is defined as the lower limit without tolerance | | +| NOTE 2: The requirements in this table are verified only under normal temperature conditions as defined in Annex E.2.1. | | + +For power class 7 UEs that support multiple FR2 bands, minimum requirement for peak EIRP and EIRP spherical coverage in Tables 6.2.1.7-1 and 6.2.1.7-3 shall be decreased per band, respectively, by the peak EIRP relaxation parameter $\Delta\text{MB}_{\text{P,n}}$ and EIRP spherical coverage relaxation parameter $\Delta\text{MB}_{\text{S,n}}$ , as defined for power class 3 in Table 6.2.1.3-4. + +## 6.2.2 UE maximum output power reduction + +### 6.2.2.0 General + +The requirements in clause 6.2.2 only apply when both UL and DL of a UE are configured for single CC operation, and they are of the same bandwidth. A UE may reduce its maximum output power due to modulation orders, transmit bandwidth configurations, waveform types and narrow allocations. This Maximum Power Reduction (MPR) is defined in clauses below. The allowed MPR for SRS, PUCCH formats 0, 1, 3 and 4, and PRACH shall be as specified for QPSK modulated DFT-s-OFDM of equivalent RB allocation. The allowed MPR for PUCCH format 2 shall be as specified for QPSK modulated CP-OFDM of equivalent RB allocation. When the maximum output power of a UE is modified by MPR, the power limits specified in clause 6.2.4 apply. + +For a UE that is configured for single CC operation with different channel bandwidths in UL and DL, the requirements in clause 6.2A.2 apply. + +For all power classes, the waveform defined by BW = 100 MHz, SCS = 120 kHz, DFT-S-OFDM QPSK, 20RB23 is the reference waveform with 0 dB MPR and is used for the power class definition. + +### 6.2.2.1 UE maximum output power reduction for power class 1 + +For power class 1, MPR for contiguous allocations is defined as: + +$$\text{MPR} = \max(\text{MPR}_{\text{WT}} + \Delta\text{MPR}, \text{MPR}_{\text{narrow}})$$ + +Where, + +$\text{MPR}_{\text{narrow}} = 14.4$ dB, when $\text{BW}_{\text{alloc,RB}} \leq 1.44$ MHz, $\text{MPR}_{\text{narrow}} = 10$ dB, when $1.44$ MHz $< \text{BW}_{\text{alloc,RB}} \leq 10.8$ MHz, where $\text{BW}_{\text{alloc,RB}}$ is the bandwidth of the RB allocation size. + +$\text{MPR}_{\text{WT}}$ is the maximum power reduction due to modulation orders, transmission bandwidth configurations listed in table 5.3.2-1, and waveform types. $\text{MPR}_{\text{WT}}$ is defined in Tables 6.2.2.1-1 and 6.2.2.1-2 for FR2-1 and in Tables 6.2.2.1-3 and 6.2.2.1-4 for FR2-2. + +$\Delta\text{MPR}$ is due to phase noise for 256 QAM for all transmission bandwidth configurations and defined in Table 6.2.2.1-5 for FR2-1. + +**Table 6.2.2.1-1** MPRWT for power class 1, BWchannel ≤ 200 MHz in FR2-1 + +| Modulation | | MPR WT (dB), BW channel ≤ 200 MHz | | | +|------------|----------------------|---------------------------------------------------------|----------------------|----------| +| | | Outer RB allocations | Inner RB allocations | | +| | | | Region 1 | Region 2 | +| DFT-s-OFDM | Pi/2 BPSK | ≤ 5.5 | 0.0 | ≤ 3.0 | +| | QPSK | ≤ 6.5 | 0.0 | ≤ 3.0 | +| | 16 QAM | ≤ 6.5 | ≤ 4.0 | ≤ 4.0 | +| | 64 QAM | ≤ 6.5 | ≤ 5.0 | ≤ 5.0 | +| | 256 QAM 1 | ≤ 9.5 | ≤ 8.0 | ≤ 8.0 | +| CP-OFDM | QPSK | ≤ 7.0 | ≤ 4.5 | ≤ 4.5 | +| | 16 QAM | ≤ 7.0 | ≤ 5.5 | ≤ 5.5 | +| | 64 QAM | ≤ 7.5 | ≤ 7.5 | ≤ 7.5 | +| | 256 QAM 1 | ≤ 10.5 | ≤ 10.5 | ≤ 10.5 | + +NOTE 1: Refer to clause 6.1 for 256 QAM applicability. + +**Table 6.2.2.1-2** MPRWT for power class 1, BWchannel = 400 MHz in FR2-1 + +| Modulation | | MPR WT (dB), BW channel = 400 MHz | | | +|------------|----------------------|---------------------------------------------------------|----------------------|----------| +| | | Outer RB allocations | Inner RB allocations | | +| | | | Region 1 | Region 2 | +| DFT-s-OFDM | Pi/2 BPSK | ≤ 5.5 | 0.0 | ≤ 3.0 | +| | QPSK | ≤ 6.5 | 0.0 | ≤ 3.5 | +| | 16 QAM | ≤ 6.5 | ≤ 4.5 | ≤ 4.5 | +| | 64 QAM | ≤ 6.5 | ≤ 6.5 | ≤ 6.5 | +| | 256 QAM 1 | ≤ 9.5 | ≤ 9.5 | ≤ 9.5 | +| CP-OFDM | QPSK | ≤ 7.0 | ≤ 5.0 | ≤ 5.0 | +| | 16 QAM | ≤ 7.0 | ≤ 6.5 | ≤ 6.5 | +| | 64 QAM | ≤ 9.0 | ≤ 9.0 | ≤ 9.0 | +| | 256 QAM 1 | ≤ 12 | ≤ 12 | ≤ 12 | + +NOTE 1: Refer to clause 6.1 for 256 QAM applicability. + +**Table 6.2.2.1-3** MPRWT for power class 1, BWchannel = 100 MHz in FR2-2 + +| Modulation | | MPR WT (dB), BW channel = 100 MHz | | | +|------------|-----------|---------------------------------------------------------|----------------------|----------| +| | | Outer RB allocations | Inner RB allocations | | +| | | | Region 1 | Region 2 | +| DFT-s-OFDM | Pi/2 BPSK | ≤ 5.5 | 0.0 | ≤ 3.5 | +| | QPSK | ≤ 6.5 | 0.0 | ≤ 3.5 | +| | 16 QAM | ≤ 7.0 | ≤ 2.5 | ≤ 2.5 | +| | 64 QAM | ≤ 8.0 | ≤ 8.0 | ≤ 8.0 | +| CP-OFDM | QPSK | ≤ 8.0 | ≤ 1.5 | ≤ 3.5 | +| | 16 QAM | ≤ 8.0 | ≤ 3.5 | ≤ 4.0 | +| | 64 QAM | ≤ 9.5 | ≤ 9.5 | ≤ 9.5 | + +**Table 6.2.2.1-4** MPRWT for power class 1, BWchannel ≥ 400 MHz in FR2-2 + +| Modulation | | MPR WT (dB), BW channel = 400, 800, 1600, 2000 MHz | | | +|------------|-----------|--------------------------------------------------------------------------|----------------------|----------| +| | | Outer RB allocations | Inner RB allocations | | +| | | | Region 1 | Region 2 | +| DFT-s-OFDM | Pi/2 BPSK | ≤ 6.0 | ≤ 1.0 | ≤ 3.5 | +| | QPSK | ≤ 6.0 | ≤ 1.0 | ≤ 4.0 | +| | 16 QAM | ≤ 4.5 | ≤ 3.0 | ≤ 3.0 | +| | 64 QAM | ≤ 8.0 | ≤ 8.0 | ≤ 8.0 | +| CP-OFDM | QPSK | ≤ 6.0 | ≤ 1.5 | ≤ 3.5 | +| | 16 QAM | ≤ 6.0 | ≤ 4.0 | ≤ 5.5 | +| | 64 QAM | ≤ 10.0 | ≤ 10.0 | ≤ 10.0 | + +**Table 6.2.2.1-5 $\Delta$ MPR for FR2-1** + +| Modulation | | Band | $\Delta$ MPR (dB) | +|------------|---------|------------------|-------------------| +| DFT-s-OFDM | 256 QAM | n257, n258, n261 | 0.0 | +| | | n259, n260 | 1.0 | +| CP-OFDM | 256 QAM | n257, n258, n261 | 0.0 | +| | | n259, n260 | 1.0 | + +Where the following parameters are defined to specify valid RB allocation ranges for the RB allocations regions in Tables 6.2.2.1-1, 6.2.2.1-2, 6.2.2.1-3, and 6.2.2.1-4: + +$N_{RB}$ is the maximum number of RBs for a given Channel bandwidth and sub-carrier spacing defined in Table 5.3.2-1. + +$$RB_{end} = RB_{Start} + L_{CRB} - 1$$ + +$$RB_{Start,Low} = \text{Max}(1, \text{Floor}(L_{CRB}/2))$$ + +$$RB_{Start,High} = N_{RB} - RB_{Start,Low} - L_{CRB}$$ + +An RB allocation is an Outer RB allocation if + +$$RB_{Start} < RB_{Start,Low} \text{ OR } RB_{Start} > RB_{Start,High} \text{ OR } L_{CRB} > \text{Ceil}(N_{RB}/2)$$ + +An RB allocation belonging to table 6.2.2.1-1 and 6.2.2.1-3 is a Region 1 inner RB allocation if + +$$RB_{start} \geq \text{Ceil}(1/3 N_{RB}) \text{ AND } RB_{end} < \text{Ceil}(2/3 N_{RB})$$ + +An RB allocation belonging to table 6.2.2.1-2 and 6.2.2.1-4 is a Region 1 inner RB allocation if + +$$RB_{start} \geq \text{Ceil}(1/4 N_{RB}) \text{ AND } RB_{end} < \text{Ceil}(3/4 N_{RB}) \text{ AND } L_{CRB} \leq \text{Ceil}(1/4 N_{RB})$$ + +An RB allocation is a Region 2 inner allocation if it is NOT an Outer allocation AND NOT a Region 1 inner allocation + +For the UE maximum output power modified by MPR, the power limits specified in clause 6.2.4 apply. + +## 6.2.2.2 UE maximum output power reduction for power class 2 + +For power class 2, MPR for FR2-1 (except 256 QAM) and FR2-2 as specified in clause 6.2.2.3 applies. For FR2-1 256 QAM, MPR for contiguous allocations is defined as: + +$$MPR = \text{max}(MPR_{WT} + \Delta MPR, MPR_{narrow})$$ + +$MPR_{narrow}$ as specified in clause 6.2.2.3 applies. + +$\Delta$ MPR as specified in Table 6.2.2.1-5 applies. + +$MPR_{WT}$ is defined in Table 6.2.2.2-2 and Table 6.2.2.2-3. The RB allocation ranges for RB allocations as specified in clause 6.2.2.3 applies. + +**Table 6.2.2.2-1: Void****Table 6.2.2.2-2: $MPR_{WT}$ for power class 2, $BW_{channel} \leq 200$ MHz, FR2-1** + +| Modulation | | $MPR_{WT}$ , $BW_{channel} \leq 200$ MHz | | +|--------------------------------------------------------|----------------------|------------------------------------------|---------------------| +| | | Inner RB allocations, Region 1 | Edge RB allocations | +| DFT-s-OFDM | 256 QAM 1 | $\leq 8.0$ | $\leq 8.5$ | +| CP-OFDM | 256 QAM 1 | $\leq 10.5$ | $\leq 10.5$ | +| NOTE 1: Refer to clause 6.1 for 256 QAM applicability. | | | | + +**Table 6.2.2.2-3: MPRWT for power class 2, BWchannel = 400 MHz, FR2-1** + +| Modulation | | MPR WT , BW channel = 400 MHz | | +|--------------------------------------------------------|----------------------|-----------------------------------------------------|---------------------| +| | | Inner RB allocations, Region 1 | Edge RB allocations | +| DFT-s-OFDM | 256 QAM 1 | ≤ 9.5 | ≤ 9.5 | +| CP-OFDM | 256 QAM 1 | ≤ 12 | ≤ 12 | +| NOTE 1: Refer to clause 6.1 for 256 QAM applicability. | | | | + +### 6.2.2.3 UE maximum output power reduction for power class 3 + +For power class 3, MPR for contiguous allocations is defined as: + +$$\text{MPR} = \max(\text{MPR}_{\text{WT}}, \text{MPR}_{\text{narrow}})$$ + +For transmission bandwidth configuration less than or equal to 200MHz, and $0 \leq \text{RB}_{\text{start}} < \text{Ceil}(1/3 \text{ N}_{\text{RB}})$ or $\text{Ceil}((2/3 \text{ N}_{\text{RB}}) - \text{L}_{\text{CRB}}) < \text{RB}_{\text{start}} \leq \text{N}_{\text{RB}} - \text{L}_{\text{CRB}}$ : + +- $\text{MPR}_{\text{narrow}} = 2.5 \text{ dB}$ , when $\text{BW}_{\text{alloc, RB}}$ is less than or equal to 1.44 MHz, +- $\text{MPR}_{\text{narrow}} = 2.0 \text{ dB}$ , when $1.44 \text{ MHz} < \text{BW}_{\text{alloc, RB}} \leq 4.32 \text{ MHz}$ , +- otherwise $\text{MPR}_{\text{narrow}} = 0 \text{ dB}$ . + +MPRWT is the maximum power reduction due to modulation orders, transmission bandwidth configurations listed in Table 5.3.2-1, and waveform types. MPRWT is defined for FR2-1 in Table 6.2.2.3-1. + +**Table 6.2.2.3-1 MPRWT for power class 3, BWchannel ≤ 200 MHz, FR2-1** + +| Modulation | | MPR WT , BW channel ≤ 200 MHz | | +|------------|-----------|-----------------------------------------------------|---------------------| +| | | Inner RB allocations, Region 1 | Edge RB allocations | +| DFT-s-OFDM | Pi/2 BPSK | 0.0 | ≤ 2.0 | +| | QPSK | 0.0 | ≤ 2.0 | +| | 16 QAM | ≤ 3.0 | ≤ 3.5 | +| | 64 QAM | ≤ 5.0 | ≤ 5.5 | +| CP-OFDM | QPSK | ≤ 3.5 | ≤ 4.0 | +| | 16 QAM | ≤ 5.0 | ≤ 5.0 | +| | 64 QAM | ≤ 7.5 | ≤ 7.5 | + +MPRWT is defined for FR2-2 in Table 6.2.2.3-1b. + +**Table 6.2.2.3-1b MPRWT for power class 3, BWchannel = 100 MHz, FR2-2** + +| Modulation | | MPR WT , BW channel = 100 MHz | | +|------------|-----------|-----------------------------------------------------|---------------------| +| | | Inner RB allocations, Region 1 | Edge RB allocations | +| DFT-s-OFDM | Pi/2 BPSK | 0.0 | ≤ 0.5 | +| | QPSK | 0.0 | ≤ 0.5 | +| | 16 QAM | ≤ 3.0 | ≤ 3.0 | +| | 64 QAM | ≤ 8.5 | ≤ 8.5 | +| CP-OFDM | QPSK | ≤ 1.5 | ≤ 1.5 | +| | 16 QAM | ≤ 4.0 | ≤ 4.0 | +| | 64 QAM | ≤ 10.0 | ≤ 10.0 | + +Where the following parameters are defined to specify valid RB allocation ranges for RB allocations in Table 6.2.2.3-1 and 6.2.2.3-1b: + +- $\text{RB}_{\text{Start, Low}} = \max(1, \text{L}_{\text{CRB}})$ , where $\max()$ indicates the largest value of all arguments. +- $\text{RB}_{\text{Start, High}} = \text{N}_{\text{RB}} - \text{RB}_{\text{Start, Low}} - \text{L}_{\text{CRB}}$ , + +An RB allocation belonging to table 6.2.2.3-1 and 6.2.2.3-1b is a Region 1 inner RB allocation if: + +- $RB_{Start,Low} \leq RB_{Start} \leq RB_{Start,High}$ , and $L_{CRB} \leq \text{ceil}(N_{RB}/3)$ , where $\text{ceil}(x)$ is the smallest integer greater than or equal to $x$ . + +For transmission bandwidth configuration equal to 400MHz, + +$MPR_{narrow} = 2.5$ dB, when $BW_{alloc,RB}$ is less than or equal to 1.44 MHz, and $0 \leq RB_{start} < \text{Ceil}(1/3 N_{RB})$ or $\text{Ceil}(2/3 N_{RB}) \leq RB_{start} \leq N_{RB} - L_{CRB}$ , where $BW_{alloc,RB}$ is the bandwidth of the RB allocation size. + +$MPR_{WT}$ is the maximum power reduction due to modulation orders, transmission bandwidth configurations listed in Table 5.3.2-1, and waveform types. $MPR_{WT}$ is defined for FR2-1 in Table 6.2.2.3-2. + +**Table 6.2.2.3-2 $MPR_{WT}$ for power class 3, $BW_{channel} = 400$ MHz, FR2-1** + +| Modulation | | $MPR_{WT}, BW_{channel} = 400$ MHz | | +|------------|-----------|------------------------------------|---------------------| +| | | Inner RB allocations, Region 1 | Edge RB allocations | +| DFT-s-OFDM | Pi/2 BPSK | 0.0 | $\leq 3.0$ | +| | QPSK | 0.0 | $\leq 3.0$ | +| | 16 QAM | $\leq 4.5$ | $\leq 4.5$ | +| | 64 QAM | $\leq 6.5$ | $\leq 6.5$ | +| CP-OFDM | QPSK | $\leq 5.0$ | $\leq 5.0$ | +| | 16 QAM | $\leq 6.5$ | $\leq 6.5$ | +| | 64 QAM | $\leq 9.0$ | $\leq 9.0$ | + +$MPR_{WT}$ is defined for FR2-2 in Table 6.2.2.3-2b and 6.2.2.3-2c. + +**Table 6.2.2.3-2b $MPR_{WT}$ for power class 3, $BW_{channel} = 400$ MHz, FR2-2** + +| Modulation | | $MPR_{WT}, BW_{channel} = 400$ MHz | | +|------------|-----------|------------------------------------|---------------------| +| | | Inner RB allocations, Region 1 | Edge RB allocations | +| DFT-s-OFDM | Pi/2 BPSK | $\leq 1.0$ | $\leq 3.0$ | +| | QPSK | $\leq 1.0$ | $\leq 3.0$ | +| | 16 QAM | $\leq 4.5$ | $\leq 4.5$ | +| | 64 QAM | $\leq 9.5$ | $\leq 9.0$ | +| CP-OFDM | QPSK | $\leq 5.0$ | $\leq 5.0$ | +| | 16 QAM | $\leq 6.5$ | $\leq 6.5$ | +| | 64 QAM | $\leq 10.0$ | $\leq 10.0$ | + +**Table 6.2.2.3-2c $MPR_{WT}$ for power class 3, $BW_{channel} \geq 800$ MHz, FR2-2** + +| Modulation | | $MPR_{WT}, BW_{channel} \geq 800$ MHz | | +|------------|-----------|---------------------------------------|---------------------| +| | | Inner RB allocations, Region 1 | Edge RB allocations | +| DFT-s-OFDM | Pi/2 BPSK | $\leq 1.0$ | $\leq 4.0$ | +| | QPSK | $\leq 1.0$ | $\leq 4.0$ | +| | 16 QAM | $\leq 6.0$ | $\leq 6.0$ | +| | 64 QAM | $\leq 9.5$ | $\leq 9.0$ | +| CP-OFDM | QPSK | $\leq 6.5$ | $\leq 6.5$ | +| | 16 QAM | $\leq 8.0$ | $\leq 8.0$ | +| | 64 QAM | $\leq 10.5$ | $\leq 10.5$ | + +Where the following parameters are defined to specify valid RB allocation ranges for RB allocations in Table 6.2.2.3-2, 6.2.2.3-2b and 6.2.2.3-2c: + +$N_{RB}$ is the maximum number of RBs for a given Channel bandwidth and sub-carrier spacing defined in Table 5.3.2-1. + +$$RB_{end} = RB_{Start} + L_{CRB} - 1$$ + +An RB allocation belonging to table 6.2.2.3-2, 6.2.2.3-2b and 6.2.2.3-2c is a Region 1 inner RB allocation if + +$$RB_{start} \geq \text{Ceil}(1/4 N_{RB}) \text{ AND } RB_{end} < \text{Ceil}(3/4 N_{RB}) \text{ AND } L_{CRB} \leq \text{Ceil}(1/4 N_{RB})$$ + +For all transmission bandwidth configurations, an RB allocation is an Edge allocation if it is NOT a Region 1 inner allocation. + +#### 6.2.2.4 UE maximum output power reduction for power class 4 + +For power class 4, MPR specified in sub-clause 6.2.2.3 applies. + +##### Table 6.2.2.4-1: Void + +#### 6.2.2.5 UE maximum output power reduction for power class 5 + +For power class 5, MPR FR2-1 (except 256 QAM) specified in sub-clause 6.2.2.3 applies. MPR for FR2-1 256 QAM specified in sub-clause 6.2.2.2 applies. + +#### 6.2.2.6 UE maximum output power reduction for power class 6 + +For power class 6, MPR specified in sub-clause 6.2.2.3 applies. + +#### 6.2.2.7 UE maximum output power reduction for power class 7 + +For power class 7, MPR specified in sub-clause 6.2.2.3 for channel bandwidth less than or equal to 200MHz applies. + +### 6.2.3 UE maximum output power with additional requirements + +#### 6.2.3.1 General + +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 and an associated value in the field *additionalSpectrumEmission*. Throughout this specification, the notion of indication or signalling of an NS value refers to the corresponding indication of an NR frequency band number of the applicable operating band (the IE field *freqBandIndicatorNR*) and an associated value of *additionalSpectrumEmission* in the relevant RRC information elements. + +To meet these additional requirements, additional maximum power reduction (A-MPR) is allowed for the maximum output power as specified in clause 6.2.1. Unless stated otherwise, an A-MPR of 0 dB shall be used. + +Table 6.2.3.1-1 specifies the additional requirements with their associated network signalling values and the allowed A-MPR and applicable operating band(s) for each NS value. The mapping of NR frequency band numbers and values of the *additionalSpectrumEmission* to network signalling labels is specified in Table 6.2.3.1-2. Unless otherwise stated, the allowed total back off is maximum of A-MPR and MPR specified in clause 6.2.2. + +**Table 6.2.3.1-1: Additional maximum power reduction (A-MPR)** + +| Network Signalling label | Requirements (clause) | NR Band | Channel bandwidth (MHz) | Resources Blocks ( $N_{RB}$ ) | A-MPR (dB) | +|--------------------------|-----------------------|------------|-------------------------|-------------------------------|------------| +| NS_200 | | | | | N/A | +| NS_201 (NOTE 1) | 6.5.3.2.2 | n258 | | | 6.2.3.2 | +| NS_202 | 6.5.3.2.3 | n257, n258 | 50, 100, 200, 400 | Table 5.3.2-1 | 6.2.3.3 | +| NS_203 | 6.5.3.2.4 | n258 | 50, 100, 200, 400 | Table 5.3.2-1 | 6.2.3.4 | + +NOTE 1: NS\_201 is obsolete, the associated additional spurious emission requirements are not applicable. + +**Table 6.2.3.1-2: Mapping of Network Signalling label** + +| NR Band | Value of additionalSpectrumEmission | | | | | | | | +|---------|-------------------------------------|-----------------|--------|--------|---|---|---|---| +| | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | +| n257 | NS_200 | NS_202 | | | | | | | +| n258 | NS_200 | NS_201 (NOTE 2) | NS_202 | NS_203 | | | | | +| n259 | NS_200 | | | | | | | | +| n260 | NS_200 | | | | | | | | +| n261 | NS_200 | | | | | | | | +| n263 | NS_200 | NS_204 | | | | | | | + +NOTE 1: *additionalSpectrumEmission* corresponds to an information element of the same name defined in sub-clause 6.3.2 of TS 38.331 [13]. + +NOTE 2: NS\_201 is obsolete, the associated additional spurious emission requirements are not applicable. + +6.2.3.2 Void + +6.2.3.2.1 Void + +**Table 6.2.3.2.1-1: (Void)** + +6.2.3.2.2 Void + +**Table 6.2.3.2.2-1: (Void)** + +6.2.3.2.3 Void + +**Table 6.2.3.2.3-1: (Void)** + +6.2.3.2.4 Void + +6.2.3.2.5 Void + +6.2.3.3 A-MPR for NS\_202 + +6.2.3.3.1 A-MPR for NS\_202 for power class 1 + +For power class 1, A-MPR for NS\_202 shall be 11.0 dB. + +#### 6.2.3.3.2 A-MPR for NS\_202 for power class 2 + +For power class 2, A-MPR for NS\_202 specified in clause 6.2.3.3.3 applies. + +#### 6.2.3.3.3 A-MPR for NS\_202 for power class 3 + +For power class 3, A-MPR for NS\_202 shall be 1.0 dB. + +#### 6.2.3.3.4 A-MPR for NS\_202 for power class 4 + +For power class 4, A-MPR for NS\_202 specified in clause 6.2.3.3.3 applies. + +#### 6.2.3.3.5 A-MPR for NS\_202 for power class 5 + +For power class 5, A-MPR for NS\_202 specified in clause 6.2.3.3.3 applies. + +#### 6.2.3.3.6 A-MPR for NS\_202 for power class 6 + +For power class 6, A-MPR for NS\_202 specified in clause 6.2.3.3.3 applies. + +#### 6.2.3.3.7 A-MPR for NS\_202 for power class 7 + +For power class 7, A-MPR for NS\_202 specified in clause 6.2.3.3.3 applies. + +#### 6.2.3.4 A-MPR for NS\_203 + +##### 6.2.3.4.1 A-MPR for NS\_203 for power class 1 + +For power class 1, A-MPR for NS\_203 shall be 3.0 dB if Offset frequency < BWchannel, 0.0 dB otherwise. The Offset frequency is defined as the frequency from 24.25 GHz to the lower edge of the channel bandwidth. + +##### 6.2.3.4.2 A-MPR for NS\_203 for power class 2 + +For power class 2, A-MPR for NS\_203 specified in subclause 6.2.3.4.3 applies. + +##### 6.2.3.4.3 A-MPR for NS\_203 for power class 3 + +For power class 3, A-MPR for NS\_203 shall be 0 dB. + +##### 6.2.3.4.4 A-MPR for NS\_203 for power class 4 + +For power class 4, A-MPR for NS\_203 specified in subclause 6.2.3.4.3 applies. + +##### 6.2.3.4.5 A-MPR for NS\_203 for power class 5 + +For power class 5, A-MPR for NS\_203 specified in subclause 6.2.3.4.3 applies. + +##### 6.2.3.4.6 A-MPR for NS\_203 for power class 6 + +For power class 6, A-MPR for NS\_203 specified in subclause 6.2.3.4.3 applies. + +##### 6.2.3.4.7 A-MPR for NS\_203 for power class 7 + +For power class 7, AMPR for NS\_203 specified in subclause 6.2.3.4.3 applies. + +## 6.2.4 Configured transmitted power + +The UE can configure its maximum output power. The configured UE maximum output power $P_{\text{CMAX,fc}}$ for carrier $f$ of a serving cell $c$ is defined as that available to the reference point of a given transmitter branch that corresponds to the reference point of the higher-layer filtered RSRP measurement as specified in TS 38.215 [11]. + +The configured UE maximum output power $P_{\text{CMAX,fc}}$ for carrier $f$ of a serving cell $c$ shall be set such that the corresponding measured peak EIRP $P_{\text{UMAX,fc}}$ is within the following bounds + +$$P_{\text{Powerclass}} + \Delta P_{\text{IBE}} - \text{MAX}(\text{MAX}(\text{MPR}_{\text{fc}}, \text{A-MPR}_{\text{fc}}) + \Delta \text{MB}_{\text{P,n}}, \text{P-MPR}_{\text{fc}}) - \text{MAX}\{T(\text{MAX}(\text{MPR}_{\text{fc}}, \text{A-MPR}_{\text{fc}})), T(\text{P-MPR}_{\text{fc}})\} \leq P_{\text{UMAX,fc}} \leq \text{EIRP}_{\text{max}}$$ + +while the corresponding measured total radiated power $P_{\text{TMAX,fc}}$ is bounded by + +$$P_{\text{TMAX,fc}} \leq \text{TRP}_{\text{max}}$$ + +with $P_{\text{Powerclass}}$ the UE minimum peak EIRP as specified in sub-clause 6.2.1, $\text{EIRP}_{\text{max}}$ the applicable maximum EIRP as specified in sub-clause 6.2.1, $\text{MPR}_{\text{fc}}$ as specified in sub-clause 6.2.2, $\text{A-MPR}_{\text{fc}}$ as specified in sub-clause 6.2.3, $\Delta \text{MB}_{\text{P,n}}$ the peak EIRP relaxation as specified in clause 6.2.1 and $\text{TRP}_{\text{max}}$ the maximum TRP for the UE power class as specified in sub-clause 6.2.1. $\Delta P_{\text{IBE}}$ is 1.0 dB if UE declares support for *mpr-PowerBoost-FR2-r16*, UL transmission is QPSK, $\text{MPR}_{\text{fc}} = 0$ and when NS\_200 applies and the network configures the UE to operate with *mpr-PowerBoost-FR2-r16* otherwise $\Delta P_{\text{IBE}}$ is 0.0 dB. The requirement is verified in beam peak direction. + +*maxUplinkDutyCycle-FR2*, as defined in TS 38.306 [14], is a UE capability to facilitate electromagnetic power density exposure requirements. This UE capability is applicable to all FR2 power classes. + +If the field of UE capability *maxUplinkDutyCycle-FR2* is present and the percentage of uplink symbols transmitted including any PRACH transmission within any 1 s evaluation period is larger than *maxUplinkDutyCycle-FR2*, the UE follows the uplink scheduling and can apply $\text{P-MPR}_{\text{fc}}$ . + +If the field of UE capability *maxUplinkDutyCycle-FR2* is absent, the compliance to electromagnetic power density exposure requirements are ensured by means of scaling down the power density or by other means. + +$\text{P-MPR}_{\text{fc}}$ is the power management maximum output power reduction. The UE shall apply $\text{P-MPR}_{\text{fc}}$ for carrier $f$ of serving cell $c$ only for the cases described below. For UE conformance testing $\text{P-MPR}_{\text{fc}}$ shall be 0 dB, except for the testing of UL gap for Tx power management, where $\text{P-MPR}_{\text{fc}}$ may be non-zero dB. + +- ensuring compliance with applicable electromagnetic power density exposure requirements and addressing unwanted emissions / self desense requirements in case of simultaneous transmissions on multiple RAT(s) for scenarios not in scope of 3GPP RAN specifications; +- ensuring compliance with applicable electromagnetic power density exposure requirements in case of proximity detection is used to address such requirements that require a lower maximum output power. + +NOTE 1: $\text{P-MPR}_{\text{fc}}$ was introduced in the $P_{\text{CMAX,fc}}$ equation such that the UE can report to the gNB the available maximum output transmit power. This information can be used by the gNB for scheduling decisions. + +NOTE 2: $\text{P-MPR}_{\text{fc}}$ and *maxUplinkDutyCycle-FR2* may impact the maximum uplink performance for the selected UL transmission path. + +NOTE 3: MPE $\text{P-MPR}$ Reporting capability *tdd-MPE-P-MPR-Reporting-r16*, as defined in TS 38.306 [14], is used to report $\text{P-MPR}_{\text{fc}}$ when the reporting conditions configured by gNB are met. This UE capability is applicable to all FR2 power classes. + +The tolerance $T(\Delta P)$ for applicable values of $\Delta P$ (values in dB) is specified in Tables 6.2.4-1 and 6.2.4-2. + +**Table 6.2.4-1: PUMAX,fc tolerance for FR2-1** + +| Operating Band | ΔP (dB) | Tolerance T(ΔP) (dB) | +|------------------------------------|--------------|----------------------| +| n257, n258, n259, n260, n261, n262 | ΔP = 0 | 0 | +| | 0 < ΔP ≤ 2 | 1.5 | +| | 2 < ΔP ≤ 3 | 2.0 | +| | 3 < ΔP ≤ 4 | 3.0 | +| | 4 < ΔP ≤ 5 | 4.0 | +| | 5 < ΔP ≤ 10 | 5.0 | +| | 10 < ΔP ≤ 15 | 7.0 | +| | 15 < ΔP ≤ X | 8.0 | + +NOTE: X is the value such that PUMAX,fc lower bound, PPowerclass - ΔP - T(ΔP) = minimum output power specified in clause 6.3.1 + +**Table 6.2.4-2: PUMAX,fc tolerance for FR2-2** + +| Operating Band | ΔP (dB) | Tolerance T(ΔP) (dB) | +|----------------|--------------|----------------------| +| n263 | ΔP = 0 | [0] | +| | 0 < ΔP ≤ 2 | [1.5] | +| | 2 < ΔP ≤ 3 | [2.0] | +| | 3 < ΔP ≤ 4 | [3.0] | +| | 4 < ΔP ≤ 5 | [4.0] | +| | 5 < ΔP ≤ 10 | [5.0] | +| | 10 < ΔP ≤ 15 | [7.0] | +| | 15 < ΔP ≤ X | [8.0] | + +NOTE: X is the value such that PUMAX,fc lower bound, PPowerclass - ΔP - T(ΔP) = minimum output power specified in clause 6.3.1 + +## 6.2.5 Requirements for UL gap (*ul-GapFR2-r17*) for TX power management + +The difference of the measured peak EIRP PUMAX,fc\_GAP\_ON when UL gap for TX power management is configured and activated, and the measured peak EIRP PUMAX,fc\_GAP\_OFF when UL gap is not configured or de-activated, shall meet the following requirement: + +$$P_{\text{UMAX,fc\_GAP\_ON}} - P_{\text{UMAX,fc\_GAP\_OFF}} \max((\text{EIRP}_{\text{meas\_peak}} - 23) + 10 * \log_{10}(Z/20), 3)\text{dB}$$ + +where EIRPmeas\_peak is the measured UE peak EIRP with zero MPR/A-MPR/P-MPR as specified in clause 6.2.1 for the corresponding power class, and Z% is duty cycle of the reference measurement channel. PUMAX,fc\_GAP\_ON shall be measured outside of the UL gap symbol(s). The period of measurement shall be at least 4 seconds. The requirement is verified with the test metric of EIRP (Link=TX beam peak direction, Meas=Link angle) and in the test Z is set to 20 when maxUplinkDutyCycle-FR2 is less than 20 or not reported, and should be larger than maxUplinkDutyCycle-FR2 when maxUplinkDutyCycle-FR2 is equal to or greater than 20. The reference measurement channel is specified in Annex A.2.3. + +When UL gap for Tx power management is configured and activated, the reported P-MPRfc shall be less than 3dB. When UL gap for Tx power management is not configured and activated at the duty cycle percentage value Z of the reference measurement channel larger than maxUplinkDutyCycle-FR2, UE shall set the P bit in PHR to 1 in the test when PHR is configured. P-bit is defined in TS 38.321 clause 6.1.3.8 and 6.1.3.9. + +## 6.2A Transmitter power for CA + +### 6.2A.1 UE maximum output power for CA + +For downlink intra-band contiguous and non-contiguous carrier aggregation with a single uplink component carrier configured in the NR band, the maximum output power is specified in clause 6.2.1. + +For uplink intra-band contiguous and non-contiguous carrier aggregation for any CA bandwidth class, the maximum output power is specified in clause 6.2.1. + +For inter-band uplink CA with two NR bands with each UL band configured with a single CC, the maximum power requirements are applicable per band, with both carriers active with non-zero power UL RB allocation. The maximum output power values for TRP and EIRP are applicable per carrier and are specified in tables 6.2.1.x-2. The minimum peak values for EIRP are defined in Tables 6.2.1.x-1 and further relaxed by $\Delta T_{IB,P,n}$ specified in Table 6.2A.1-x. The peak EIRP requirements are verified with the test metric of EIRP (Link=TX beam peak direction, Meas=Link angle). + +The inter-band ULCA spherical coverage requirement for each power class is met if the intersection set of spherical coverage areas exceeds the common coverage requirement for that power class. For inter-band ULCA, the spherical coverage area for each band is the region of the sphere measured around the UE where the measured EIRP exceeds the EIRP level specified in Tables 6.2.1.x-3 and further reduced by the parameter $\Delta T_{IB,S,n}$ specified in Table 6.2A.1-x. The intersection set of spherical coverage areas is defined as a fraction of area of full sphere measured around the UE where both bands meet their individual EIRP spherical coverage requirements for inter-band CA operation. The common coverage requirement is determined as <100-percentile rank> %, where 'percentile rank' is the percentile value in the specification of spherical coverage for that power class from Tables 6.2.1.x-3. The spherical coverage EIRP requirements are verified with the test metric of EIRP (Link=Spherical coverage grid, Meas=Link angle). + +The $\Delta T_{IB}$ parameters are specified in tables 6.2A.1-x. + +**Table 6.2A.1-1: $\Delta T_{IB}$ EIRP relaxations for inter-band UL CA for power class 1** + +| NR CA configuration | NR band | $\Delta T_{IB,P,n}$ (dB) | $\Delta T_{IB,S,n}$ (dB) | +|---------------------|---------|--------------------------|--------------------------| +| CA_n260A-n261A | n260 | [1.5] | 2.5 | +| | n261 | [1.5] | 2.5 | + +**Table 6.2A.1-2: $\Delta T_{IB}$ EIRP relaxations for inter-band UL CA for power class 2** + +| NR CA configuration | NR band | $\Delta T_{IB,P,n}$ (dB) | $\Delta T_{IB,S,n}$ (dB) | +|---------------------|---------|--------------------------|--------------------------| +| CA_n257A-n259A | n257 | 2.5 | 2.5 | +| | n259 | 2.5 | 2.5 | + +**Table 6.2A.1-3: $\Delta T_{IB}$ EIRP relaxations for inter-band UL CA for power class 3** + +| NR CA configuration | NR band | $\Delta T_{IB,P,n}$ (dB) | $\Delta T_{IB,S,n}$ (dB) | +|---------------------|---------|--------------------------|--------------------------| +| CA_n257A-n259A | n257 | 6.0 | 6.0 | +| | n259 | 6.0 | 6.0 | +| CA_n260A-n261A | n260 | 6.0 | 6.0 | +| | n261 | 6.0 | 6.0 | + +**Table 6.2A.1-4: reserved for future use** + +**Table 6.2A.1-5: $\Delta T_{IB}$ EIRP relaxations for inter-band UL CA for power class 5** + +| NR CA configuration | NR band | $\Delta T_{IB,P,n}$ (dB) | $\Delta T_{IB,S,n}$ (dB) | +|---------------------|---------|--------------------------|--------------------------| +| CA_n257A-n259A | n257 | [1.5] | 2.5 | +| | n259 | [1.5] | 2.5 | + +Power class 3 is default power class. + +NOTE: UL carrier aggregation within FR2 is defined only within FR2-1 in this release of the specification. + +## 6.2A.2 UE maximum output power reduction for CA + +### 6.2A.2.1 General + +The UE is defined to be configured for CA operation when it has at least one of UL or DL configured for CA. In CA operation, the UE may reduce its maximum output power due to higher order modulations and transmit bandwidth configurations. This Maximum Power Reduction (MPR) is defined in clauses below. The allowed MPR for SRS, PUCCH formats 0, 1, 3 and 4, shall be as specified for QPSK modulated DFT-s-OFDM of equivalent RB allocation. The allowed MPR for PUCCH format 2, shall be as specified for QPSK modulated CP-OFDM of equivalent RB allocation. + +When the maximum output power of a UE is modified by MPR, the power limits specified in clause 6.2A.4 apply. The requirements in the following clauses are applicable to the following CA configurations: + +- intra-band contiguous uplink CA, with the aggregated channel bandwidth no greater than 800 MHz. +- intra-band non-contiguous uplink CA with UL frequency separation no greater than 1400 MHz, and no more than 3 sub-blocks. A sub-block may consist of single CC or multiple contiguous CCs. +- inter-band uplink CA with two NR bands, and each UL band is configured with a single CC. +- In case the CA configuration consists of a single UL CC, MPR for contiguous UL CA applies and where necessary, $BW_{\text{channel}}$ shall be used as $BW_{\text{channel\_CA}}$ . + +### 6.2A.2.2 Maximum output power reduction for power class 1 + +#### 6.2A.2.2.1 Maximum output power reduction for power class 1 intra-band contiguous UL CA + +For power class 1, MPR for intra-band contiguous UL CA with contiguous allocations within the cumulative aggregated bandwidth is defined as: + +$$MPR_{C\_CA} = \max(MPR_{\text{WT\_C\_CA}} + \Delta MPR, MPR_{\text{narrow}})$$ + +Where, + +$MPR_{\text{narrow}} = 14.4$ dB, when $BW_{\text{alloc,RB}}$ is less than or equal to 1.44 MHz, $MPR_{\text{narrow}} = 10$ dB, when $1.44$ MHz $< BW_{\text{alloc,RB}} \leq 10.8$ MHz, where $BW_{\text{alloc,RB}}$ is the bandwidth of the RB allocation size. + +$MPR_{\text{WT\_C\_CA}}$ is the maximum power reduction due to modulation orders, transmit bandwidth configurations, and waveform types. $MPR_{\text{WT\_C\_CA}}$ is defined in Tables 6.2A.2.2-1 and 6.2A.2.2-2. + +$\Delta MPR$ for FR2-1 256 QAM as specified in Table 6.2.2.1-5 applies. + +**Table 6.2A.2.2-1: Maximum power reduction (MPRWT\_C\_CA) for UE power class 1 in FR2-1** + +| Waveform Type | | Cumulative aggregated channel bandwidth | | | | +|---------------|----------------------|-----------------------------------------|-------------------------|--------------------------|---------------------------| +| | | < 400 MHz | ≥ 400 MHz and < 800 MHz | ≥ 800 MHz and ≤ 1400 MHz | > 1400 MHz and ≤ 2400 MHz | +| DFT-s-OFDM | Pi/2 BPSK | ≤ 5.5 1 | 7.7 | 8.2 | ≤ 8.7 | +| | QPSK | ≤ 6.5 1 | 8.7 | 9.7 | ≤ 9.7 | +| | 16 QAM | ≤ 6.5 | 8.7 | 9.2 | ≤ 9.7 | +| | 64 QAM | ≤ 9.0 | 10.7 | 11.2 | ≤ 11.7 | +| | 256 QAM 2 | ≤ 12.5 | ≤ 14.2 | ≤ 14.7 | ≤ 15.7 | +| CP-OFDM | QPSK | ≤ 6.5 | 8.7 | 8.7 | ≤ 9.7 | +| | 16 QAM | ≤ 6.5 | 8.7 | 8.7 | ≤ 9.7 | +| | 64 QAM | ≤ 9.0 | 10.7 | 11.2 | ≤ 11.7 | +| | 256 QAM 2 | ≤ 12.5 | ≤ 14.2 | ≤ 14.7 | ≤ 15.7 | + +NOTE 1: (Void) + +NOTE 2: Refer to clause 6.1 for 256 QAM applicability. + +**Table 6.2A.2.2-2: Maximum power reduction (MPRWT\_C\_CA) for UE power class 1 in FR2-2** + +| Waveform Type | Cumulative aggregated channel bandwidth | | | | +|---------------|-----------------------------------------|-------------------------|--------------------------|---------------------------| +| | < 400 MHz | ≥ 400 MHz and < 800 MHz | ≥ 800 MHz and ≤ 1400 MHz | > 1400 MHz and ≤ 2000 MHz | +| Pi/2 BPSK | ≤ 7.0 | ≤ 5.0 | ≤ 2.0 | ≤ 2.0 | +| QPSK | ≤ 8.0 | ≤ 6.0 | ≤ 3.0 | ≤ 3.0 | +| 16 QAM | ≤ 8.0 | ≤ 6.0 | ≤ 4.0 | ≤ 4.0 | +| 64 QAM | ≤ 10.0 | ≤ 10.0 | ≤ 10.0 | ≤ 10.0 | + +In case of a contiguous RB, DFT-s-BPSK or DFT-s-QPSK UL allocation in a single CC of a CA configuration with contiguous CCs, and whose cumulative aggregated BW ≤ 400 MHz, MPRWT\_C\_CA shall be derived instead as MAX(MPR1, MPR2), where: + +MPR1 shall be determined from Table 6.2.2.1-1 if CABW ≤ 200 MHz, from Table 6.2.2.1-2 if CABW > 200 MHz. + +MPR2 shall be determined from Table 6.2.2.1-1 if UL BWchannel\_CA ≤ 200 MHz, from Table 6.2.2.1-2 if UL BWchannel\_CA > 200 MHz. + +and assume all UL CCs use the same SCS for the purpose of determination of inner and outer RB allocations in Table 6.2.2.1-1 and Table 6.2.2.1-2: + +NRB shall be chosen as the sum of NRB of all constituent UL CCs in the CA configuration. + +LCRB shall be chosen as BWalloc,RB + +RBstart shall be derived as: RBstart\_allocatedCC+NRB\_unallocatedCC\_low + +RBstart\_allocatedCC is the index of the first allocated RB in the CC with allocation + +NRB\_unallocatedCC\_low is the sum of NRB in all UL CCs lower in frequency compared to the CC with allocation + +When different waveform types exist across CCs, the requirement is set by the waveform type used in the configuration with the largest MPRC\_CA. + +For intra-band contiguous UL CA with non-contiguous RB allocations, the following rule for MPR applies: + +$$\text{MPR} = \max(\text{MPR}_{\text{C\_CA}} + \Delta\text{MPR}, -10 * A + 14.4)$$ + +Where: + +$$A = N_{\text{RB\_alloc}} / N_{\text{RB\_agg\_C}}$$ + +NRB\_alloc is the total number of allocated UL RBs + +$N_{RB\_agg\_C}$ is the number of the aggregated RBs within the fully allocated cumulative aggregated channel bandwidth assuming lowest SCS among all configured CCs + +#### 6.2A.2.2.2 Maximum output power reduction for power class 1 intra-band non-contiguous UL CA + +For intra-band non-contiguous UL CA, the following rule for MPR applies: + +$$MPR = \max(MPR_{NC\_CA} + \Delta MPR, -10*A + 14.4)$$ + +Where: + +$MPR_{NC\_CA}$ is derived from table 6.2A.2.2.2-1 + +$\Delta MPR$ as specified in Table 6.2.2.1-5 applies. + +$$A = N_{RB\_alloc} / N_{RB\_agg\_C}$$ + +$N_{RB\_alloc}$ is the total number of allocated UL RBs + +$N_{RB\_agg\_C}$ is the number of the aggregated RBs within the fully allocated cumulative aggregated channel bandwidth assuming lowest SCS among all configured CCs + +**Table 6.2A.2.2.2-1: $MPR_{NC\_CA}$ for UE power class 1** + +| Waveform Type | | Cumulative aggregated channel bandwidth (CABW) | | | | +|---------------|----------------------|------------------------------------------------|-------------------------|--------------------------|---------------------------| +| | | < 400 MHz | ≥ 400 MHz and < 800 MHz | ≥ 800 MHz and ≤ 1400 MHz | > 1400 MHz and ≤ 2400 MHz | +| DFT-s-OFDM | Pi/2 BPSK | ≤ 6 | ≤ 7.7 | ≤ 8.2 | ≤ 8.7 | +| | QPSK | ≤ 7 | ≤ 8.7 | ≤ 9.2 | ≤ 9.7 | +| | 16 QAM | ≤ 7 | ≤ 8.7 | ≤ 9.2 | ≤ 9.7 | +| | 64 QAM | ≤ 9.0 | ≤ 10.7 | ≤ 11.2 | ≤ 11.7 | +| | 256 QAM 1 | ≤ 12.5 | ≤ 14.2 | ≤ 14.7 | ≤ 15.7 | +| CP-OFDM | QPSK | ≤ 7 | ≤ 8.7 | ≤ 9.2 | ≤ 9.7 | +| | 16 QAM | ≤ 7 | ≤ 8.7 | ≤ 9.2 | ≤ 9.7 | +| | 64 QAM | ≤ 9.0 | ≤ 10.7 | ≤ 11.2 | ≤ 11.7 | +| | 256 QAM 1 | ≤ 12.5 | ≤ 14.2 | ≤ 14.7 | ≤ 15.7 | + +NOTE 1: Refer to clause 6.1 for 256 QAM applicability. + +When different waveform types exist across CCs, the requirement is set by the waveform type used in the configuration with the largest $MPR_{NC\_CA}$ . + +#### 6.2A.2.2.3 Maximum output power reduction for power class 1 inter-band CA + +For inter-band carrier aggregation with uplink assigned to two NR bands, the MPR for each configured UL band in the UL CA band combination is: + +$$MPR_{inter-band\_CA} = \max(MPR_{SingleBand}, MPR_{PA-PA})$$ + +Where: + +$MPR_{SingleBand}$ is the MPR specified in clause 6.2.2.1 for the allocation and modulation type in that band + +$MPR_{PA-PA}$ is $\max(MPR1, MPR2)$ , where $MPR1$ and $MPR2$ are specified per band combination in Table 6.2A.2.2.2.3-1 and applies only when both bands have non-zero power UL RB allocations, 0 dB otherwise. + +**Table 6.2A.2.2.3-1: MPRPA-PA for Inter-band ULCA in FR2 for PC1** + +| NR CA Band | MPR | Value (dB) | Condition | +|----------------|------|---------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| +| CA_n260A-n261A | MPR1 | Max(0, 10 - 10*log 10 (Max(1.0, L RB,min * 12*SCS/1e6)))) | L RB,min = Min (L RB,n260 , L RB,n261 ), where L RB,n is the number of non-zero power UL RBs in band 'n' | +| | MPR2 | 6.0 if condition satisfied, 0.0 otherwise | 47.2 GHz ≤ 2*f n260 - f n261 ≤ 48.2 GHz
Where f n is any frequency inside the UL allocation in band 'n' | + +## 6.2A.2.3 Maximum output power reduction for power class 2 + +**For power class 2, MPR (except 256 QAM) specified in sub-clause 6.2A.2.4.1 applies for intra-band contiguous UL CA and sub-clause 6.2A.2.4.2 applies for intra-band non-contiguous UL CA. Table 6.2A.2.3-1: (Void)** + +For FR2-1 256 QAM, for intra-band contiguous UL CA with contiguous allocations within the cumulative aggregated bandwidth, the following rule for MPR applies: + +$$\text{MPR} = \text{MPR}_{\text{C\_CA}} + \Delta\text{MPR}$$ + +MPRC\_CA is defined in Table 6.2A.2.3-2. ΔMPR as specified in Table 6.2.2.1-5 applies. + +**Table 6.2A.2.3-2: Maximum power reduction (MPRC\_CA) for UE power class 2 in FR2-1** + +| | | Cumulative aggregated channel bandwidth (CABW) | | | | +|------------|----------------------|------------------------------------------------|-------------------------|--------------------------|---------------------------| +| | | ≤ 400 MHz | > 400 MHz and < 800 MHz | ≥ 800 MHz and ≤ 1400 MHz | > 1400 MHz and ≤ 2400 MHz | +| DFT-s-OFDM | 256 QAM 1 | ≤ 12.5 | ≤ 14.2 | ≤ 14.7 | ≤ 15.7 | +| CP-OFDM | 256 QAM 1 | ≤ 12.5 | ≤ 14.2 | ≤ 14.7 | ≤ 15.7 | + +NOTE 1: Refer to clause 6.1 for 256QAM applicability. + +For FR2-1 256 QAM, for intra-band contiguous UL CA with non-contiguous RB allocations, the following rule for MPR applies: + +$$\text{MPR} = \max(\text{MPR}_{\text{C\_CA}} + \Delta\text{MPR}, -10*A + 7.0)$$ + +Where: + +$$A = N_{\text{RB\_alloc}} / N_{\text{RB\_agg\_C}}$$ + +NRB\_alloc is the total number of allocated UL RBs + +NRB\_agg\_C is the number of the aggregated RBs within the fully allocated cumulative aggregated channel bandwidth assuming lowest SCS among all configured CCs + +For FR2-1 256QAM, for intra-band non-contiguous UL CA, the following rule for MPR applies: + +$$\text{MPR} = \max(\text{MPR}_{\text{NC\_CA}} + \Delta\text{MPR}, -8*A + 10.0)$$ + +Where: + +MPRNC\_CA is derived from table 6.2A.2.3-3. + +$$A = N_{\text{RB\_alloc}} / N_{\text{RB\_agg\_C}}$$ + +NRB\_alloc is the total number of allocated UL RBs + +NRB\_agg\_C is the number of the aggregated RBs within the fully allocated cumulative aggregated channel bandwidth assuming lowest SCS among all configured CCs. + +**Table 6.2A.2.3-3: MPRNC\_CA for UE power class 2 in FR2-1** + +| | | Cumulative aggregated channel bandwidth (CABW) | | | | +|--------------------------------------------------------|----------------------|------------------------------------------------|-------------------------|--------------------------|---------------------------| +| | | ≤ 400 MHz | > 400 MHz and < 800 MHz | ≥ 800 MHz and ≤ 1400 MHz | > 1400 MHz and ≤ 2400 MHz | +| DFT-s-OFDM | 256 QAM 1 | ≤ 12.5 | ≤ 14.2 | ≤ 14.7 | ≤ 15.7 | +| CP-OFDM | 256 QAM 1 | ≤ 12.5 | ≤ 14.2 | ≤ 14.7 | ≤ 15.7 | +| NOTE 1: Refer to clause 6.1 for 256 QAM applicability. | | | | | | + +For inter-band carrier aggregation with uplink assigned to two NR bands, the MPR for each configured UL band in the UL CA band combination is: + +$$\text{MPR}_{\text{inter-band\_CA}} = \max(\text{MPR}_{\text{SingleBand}}, \text{MPR}_{\text{PA-PA}})$$ + +Where: + +MPRSingleBand is the MPR specified in clause 6.2.2.2 for the allocation and modulation type in that band + +MPRPA-PA is specified in Table 6.2A.2.3-2 and applies only when both bands have non-zero UL RB allocations, 0 dB otherwise. + +**Table 6.2A.2.3-2: MPRPA-PA for Inter-band ULCA in FR2 for PC2** + +| NR CA Band | Value (dB) | Condition | +|----------------|---------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| +| CA_n257A-n259A | Max(0, 6 - 10*log 10 (Max(1.0, L RB,min * 12 * SCS/1e6))) | L RB,min = Min (L RB,n257 , L RB,n259 ), where L RB,n is the number of non-zero power UL RBs in band 'n' | + +## 6.2A.2.4 Maximum output power reduction for power class 3 + +### 6.2A.2.4.1 Maximum output power reduction for power class 3 intra-band contiguous CA + +For power class 3, MPR for intra-band contiguous UL CA with contiguous allocations within the cumulative aggregated bandwidth is denoted as MPRC\_CA and is defined in Tables 6.2A.2.4-1 and 6.2A.2.4-2. + +**Table 6.2A.2.4-1: Maximum power reduction (MPRC\_CA) for UE power class 3 in FR2-1** + +| | | Cumulative aggregated channel bandwidth (CABW) | | | | +|-----------------|-----------|------------------------------------------------|-------------------------|--------------------------|---------------------------| +| | | ≤ 400 MHz | > 400 MHz and < 800 MHz | ≥ 800 MHz and ≤ 1400 MHz | > 1400 MHz and ≤ 2400 MHz | +| DFT-s-OFDM | Pi/2 BPSK | ≤ 5.0 1 | ≤ 7.7 | ≤ 8.2 | ≤ 8.7 | +| | QPSK | ≤ 5.0 1 | ≤ 7.7 | ≤ 8.2 | ≤ 9.7 | +| | 16 QAM | ≤ 6.5 | ≤ 8.7 | ≤ 9.3 | ≤ 9.7 | +| | 64 QAM | ≤ 9.0 | ≤ 10.7 | ≤ 11.2 | ≤ 11.7 | +| CP-OFDM | QPSK | ≤ 5.0 | ≤ 7.5 | ≤ 8.0 | ≤ 9.7 | +| | 16 QAM | ≤ 6.5 | ≤ 8.7 | ≤ 9.2 | ≤ 9.7 | +| | 64 QAM | ≤ 9.0 | ≤ 10.7 | ≤ 11.2 | ≤ 11.7 | +| NOTE 1: (Void). | | | | | | + +**Table 6.2A.2.4-2: Maximum power reduction (MPRWT\_C\_CA) for UE power class 3 in FR2-2** + +| Waveform Type | Cumulative aggregated channel bandwidth | | | | +|---------------|-----------------------------------------|-------------------------|--------------------------|---------------------------| +| | < 400 MHz | ≥ 400 MHz and < 800 MHz | ≥ 800 MHz and ≤ 1400 MHz | > 1400 MHz and ≤ 2000 MHz | +| Pi/2 BPSK | ≤ 1.0 | ≤ 1.0 | ≤ 1.0 | ≤ 1.0 | +| QPSK | ≤ 2.0 | ≤ 2.0 | ≤ 2.0 | ≤ 2.0 | +| 16 QAM | ≤ 4.0 | ≤ 4.0 | ≤ 4.0 | ≤ 4.0 | +| 64 QAM | ≤ 10.0 | ≤ 10.0 | ≤ 10.0 | ≤ 10.0 | + +In case of a contiguous RB, DFT-s-BPSK or DFT-s-QPSK UL allocation in a single CC of a CA configuration with contiguous CCs, and whose cumulative aggregated BW $\leq 400$ MHz, $MPR_{C\_CA}$ shall be derived instead as $\max(MPR_1, MPR_2)$ , where: + +$MPR_1$ shall be determined from Table 6.2.2.3-1 if $CABW \leq 200$ MHz, from Table 6.2.2.3-2 if $CABW > 200$ MHz. + +$MPR_2$ shall be determined from Table 6.2.2.3-1 if $UL\ BW_{channel\_CA} \leq 200$ MHz, from Table 6.2.2.3-2 if $UL\ BW_{channel\_CA} > 200$ MHz. + +and assume all UL CCs use the same SCS for the purpose of determination of inner and outer RB allocations in Table 6.2.2.3-1 and Table 6.2.2.3-2: + +$N_{RB}$ shall be chosen as the sum of $N_{RB}$ of all constituent UL CCs in the CA configuration. + +$L_{CRB}$ shall be chosen as $BW_{alloc,RB}$ + +$RB_{start}$ shall be derived as: $RB_{start\_allocatedCC} + N_{RB\_unallocatedCC\_low}$ + +$RB_{start\_allocatedCC}$ is the index of the first allocated RB in the CC with allocation + +$N_{RB\_unallocatedCC\_low}$ is the sum of $N_{RB}$ in all UL CCs lower in frequency compared to the CC with allocation + +When different waveform types exist across CCs, the requirement is set by the waveform type used in the configuration with the highest contiguous MPR. + +For intra-band contiguous UL CA with non-contiguous RB allocations, the following rule for MPR applies: + +$$MPR = \max(MPR_{C\_CA}, -10*A + 7.0)$$ + +Where: + +$$A = N_{RB\_alloc} / N_{RB\_agg\_C}$$ + +$N_{RB\_alloc}$ is the total number of allocated UL RBs + +$N_{RB\_agg\_C}$ is the number of the aggregated RBs within the fully allocated cumulative aggregated channel bandwidth assuming lowest SCS among all configured CCs + +#### 6.2A.2.4.2 Maximum output power reduction for power class 3 intra-band non-contiguous CA + +For intra-band non-contiguous UL CA, the following rule for MPR applies: + +$$MPR = \max(MPR_{NC\_CA}, -8*A + 10.0)$$ + +Where: + +$MPR_{NC\_CA}$ is derived from table 6.2A.2.4.2-1 + +$$A = N_{RB\_alloc} / N_{RB\_agg\_C}$$ + +$N_{RB\_alloc}$ is the total number of allocated UL RBs + +$N_{RB\_agg\_C}$ is the number of the aggregated RBs within the fully allocated cumulative aggregated channel bandwidth assuming lowest SCS among all configured CCs + +**Table 6.2A.2.4.2-1: $MPR_{NC\_CA}$ for UE power class 3** + +| | | Cumulative aggregated channel bandwidth (CABW) | | | | +|------------|-----------|------------------------------------------------|-----------------------------|------------------------------------|----------------------------------| +| | | $\leq 400$ MHz | $> 400$ MHz and $< 800$ MHz | $\geq 800$ MHz and $\leq 1400$ MHz | $> 1400$ MHz and $\leq 2400$ MHz | +| DFT-s-OFDM | Pi/2 BPSK | $\leq 5.5$ | $\leq 7.7$ | $\leq 8.2$ | $\leq 8.7$ | +| | QPSK | $\leq 6$ | $\leq 7.7$ | $\leq 8.2$ | $\leq 8.7$ | +| | 16 QAM | $\leq 7$ | $\leq 8.7$ | $\leq 9.3$ | $\leq 9.8$ | +| | 64 QAM | $\leq 9.0$ | $\leq 10.7$ | $\leq 11.2$ | $\leq 11.7$ | +| CP-OFDM | QPSK | $\leq 6$ | $\leq 7.5$ | $\leq 8.0$ | $\leq 8.5$ | +| | 16 QAM | $\leq 7$ | $\leq 8.7$ | $\leq 9.2$ | $\leq 9.7$ | +| | 64 QAM | $\leq 9.0$ | $\leq 10.7$ | $\leq 11.2$ | $\leq 11.7$ | + +When different waveform types exist across CCs, the requirement is set by the waveform type used in the configuration with the largest $MPR_{NC\_CA}$ . + +### 6.2A.2.4.3 Maximum output power reduction for power class 3 inter-band CA + +For inter-band carrier aggregation with uplink assigned to two NR bands, the MPR for each configured UL band in the UL CA band combination is: + +$$MPR_{inter-band\_CA} = \max(MPR_{SingleBand}, MPR_{PA-PA})$$ + +Where: + +$MPR_{SingleBand}$ is the MPR specified in clause 6.2.2.3 for the allocation and modulation type in that band. + +$MPR_{PA-PA}$ is $\max(MPR1, MPR2)$ , where MPR1 and MPR2 are specified per band combination in Table 6.2A.2.4.3-1 and applies only when both bands have non-zero power UL RB allocations, 0 dB otherwise. + +**Table 6.2A.2.4.3-1: $MPR_{PA-PA}$ for Inter-band ULCA in FR2 for PC3** + +| NR CA Band | MPR | Value (dB) | Condition | +|----------------|------|---------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| CA_n257A-n259A | MPR1 | $\max(0, 6 - 10 \cdot \log_{10}(\max(1.0, L_{RB,min} \cdot 12 \cdot SCS/1e6)))$ | $L_{RB,min} = \min(L_{RB,n257}, L_{RB,n259})$ , where $L_{RB,n}$ is the number of non-zero power UL RBs in band 'n' | +| | MPR2 | 0.0 | - | +| CA_n260A-n261A | MPR1 | $\max(0, 6 - 10 \cdot \log_{10}(\max(1.0, L_{RB,min} \cdot 12 \cdot SCS/1e6)))$ | $L_{RB,min} = \min(L_{RB,n260}, L_{RB,n261})$ , where $L_{RB,n}$ is the number of non-zero power UL RBs in band 'n' | +| | MPR2 | 2.0 if condition satisfied, 0.0 otherwise | $47.2 \text{ GHz} \leq 2 \cdot f_{n260} - f_{n261} \leq 48.2 \text{ GHz}$
Where $f_n$ is any frequency inside the UL allocation in band 'n' | + +### 6.2A.2.5 Maximum output power reduction for power class 4 + +For power class 4, MPR specified in sub-clause 6.2A.2.4.1 applies for intra-band contiguous UL CA and sub-clause 6.2A.2.4.2 applies for intra-band non-contiguous UL CA. + +### 6.2A.2.6 Maximum output power reduction for power class 5 + +For power class 5, MPR (except 256 QAM) specified in sub-clause 6.2A.2.4.1 applies for intra-band contiguous UL CA and sub-clause 6.2A.2.4.2 applies for intra-band non-contiguous UL CA. For FR2-1 256 QAM, MPR specified in sub-clause 6.2A.2.3 applies for intra-band contiguous UL CA and intra-band non-contiguous UL CA. + +For inter-band carrier aggregation with uplink assigned to two NR bands, MPR for each configured UL band in the UL CA band combination is: + +$$MPR_{inter-band\_CA} = \max(MPR_{SingleBand}, MPR_{PA-PA})$$ + +Where: + +MPRSingleBand is the MPR specified in clause 6.2.2.5 for the allocation and modulation type in that band + +MPRPA-PA is the maximum of the MPR values specified per band combination in Table 6.2A.2.6-1 and applies only when both bands have non-zero UL RB allocations, 0 dB otherwise. + +**Table 6.2A.2.6-1: MPRPA-PA for Inter-band CA in FR2 for PC5** + +| NR CA Band | Value (dB) | Condition | +|----------------|----------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| +| CA_n257A-n259A | Max(0, 6 - 10*log 10 (Max(1.0, L RB,min * 12 * SCS/1e6)))) | L RB,min = Min (L RB,n257 , L RB,n259 ), where L RB,n is the number of non-zero power UL RBs in band 'n' | + +## 6.2A.2.7 Maximum output power reduction for power class 6 + +For power class 6, MPR specified in sub-clause 6.2A.2.4.1 applies for intra-band contiguous UL CA and sub-clause 6.2A.2.4.2 applies for intra-band non-contiguous UL CA. + +## 6.2A.3 UE maximum output power with additional requirements for CA + +### 6.2A.3.1 General + +Additional emission requirements can be signalled by the network with network signalling value indicated by the field *additionalSpectrumEmission*. To meet these additional requirements, additional maximum power reduction (A-MPR) is allowed for the maximum output power as specified in clause 6.2A.1. Unless stated otherwise, an A-MPR of 0 dB shall be used. Unless otherwise stated, the allowed total back off is maximum of A-MPR and MPR specified in clause 6.2A.2. + +For intra-band contiguous aggregation with the UE configured for transmissions on two serving cells, the maximum output power reduction specified in Table 6.2A.3.1-1 is allowed for all serving cells of the applicable uplink contiguous CA configurations. + +Table 6.2A.3.1-1 specifies the additional requirements and allowed A-MPR with corresponding network signalling label and operating band. The mapping between network signalling labels and the *additionalSpectrumEmission* IE defined in TS 38.331 [13] is specified in Table 6.2A.3.1-2. Unless otherwise stated, the allowed total back off is maximum of A-MPR and MPR specified in clause 6.2A.2. + +**Table 6.2A.3.1-1: Additional maximum power reduction (A-MPR)** + +| Network Signalling value | Requirements (clause) | NR Band | Channel bandwidth (MHz) | Resources Blocks ( NRB ) | A-MPR (dB) | +|-----------------------------------------------------------------------------------------------------------|-----------------------|------------|-------------------------|--------------------------------------------|------------| +| CA_NS_200 | | | | | N/A | +| CA_NS_201 | 6.5.3.2.2 | n258 | | | 6.2A.3.2 | +| CA_NS_202 | 6.5.3.2.3 | n257, n258 | | | 6.2A.3.3 | +| CA_NS_203 | 6.5.3.2.4 | n258 | | | 6.2A.3.4 | +| NOTE: CA_NS_201 is obsolete, the associated additional spurious emission requirements are not applicable. | | | | | | + +**Table 6.2A.3.1-2: Value of additionalSpectrumEmission** + +| NR Band | Value of additionalSpectrumEmission / NS number | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------|-----------|-----------|-----------|---|---|---|---| +| | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | +| n257 | CA_NS_200 | CA_NS_202 | | | | | | | +| n258 | CA_NS_200 | CA_NS_201 | CA_NS_202 | CA_NS_203 | | | | | +| n259 | CA_NS_200 | | | | | | | | +| n260 | CA_NS_200 | | | | | | | | +| n261 | CA_NS_200 | | | | | | | | +| NOTE 1: additionalSpectrumEmission corresponds to an information element of the same name defined in clause 6.3.2 of TS 38.331 [13]. | | | | | | | | | +| NOTE 2: CA_NS_201 is obsolete, the associated additional spurious emission requirements are not applicable. | | | | | | | | | + +6.2A.3.2 Void + +6.2A.3.2.1 Void + +**Table 6.2A.3.2.1-1: (Void)** + +6.2A.3.2.2 Void + +**Table 6.2A.3.2.2-1: (Void)** + +6.2A.3.2.3 Void + +**Table 6.2A.3.2.3-1: Void** + +6.2A.3.2.4 Void + +6.2A.3.2.5 Void + +6.2A.3.3 A-MPR for CA\_NS\_202 + +6.2A.3.3.1 A-MPR for CA\_NS\_202 for power class 1 + +For intra-band contiguous CA, A-MPR for CA\_NS\_202 shall be 11.0 dB. + +6.2A.3.3.2 A-MPR for CA\_NS\_202 for power class 2 + +For intra-band contiguous CA, A-MPR for CA\_NS\_202 specified in sub-clause 6.2A.3.3.3 applies. + +6.2A.3.3.3 A-MPR for CA\_NS\_202 for power class 3 + +For intra-band contiguous CA, A-MPR for CA\_NS\_202 shall be 2.0 dB. + +6.2A.3.3.4 A-MPR for CA\_NS\_202 for power class 4 + +For intra-band contiguous CA, A-MPR for CA\_NS\_202 specified in sub-clause 6.2A.3.3.3 applies. + +6.2A.3.3.5 A-MPR for CA\_NS\_202 for power class 5 + +For intra-band contiguous CA, A-MPR for CA\_NS\_202 specified in sub-clause 6.2A.3.3.3 applies. + +6.2A.3.3.6 A-MPR for CA\_NS\_202 for power class 6 + +For intra-band contiguous CA, A-MPR for CA\_NS\_202 specified in sub-clause 6.2A.3.3.3 applies. + +6.2A.3.4 A-MPR for CA\_NS\_203 + +6.2A.3.4.1 A-MPR for CA\_NS\_203 for power class 1 + +For intra-band contiguous CA, A-MPR for CA\_NS\_203 shall be 6.5 dB, if Offset frequency < BWChannel\_CA of the UL CA configuration, 0.0 dB, otherwise + +The Offset frequency is defined as the frequency from 24.25 GHz to the lower edge of the lowest CC among the configured UL CA. + +#### 6.2A.3.4.2 A-MPR for CA\_NS\_203 for power class 2 + +For intra-band contiguous CA, AMPR specified in sub-clause 6.2A.3.4.3 applies. + +#### 6.2A.3.4.3 A-MPR for CA\_NS\_203 for power class 3 + +For intra-band contiguous CA, A-MPR for CA\_NS\_203 shall be 2.5 dB, if Offset frequency < BWChannel\_CA of the UL CA configuration, 0.0 dB otherwise. + +The Offset frequency is defined as the frequency from 24.25 GHz to the lower edge of the lowest CC among the configured UL CA. + +#### 6.2A.3.4.4 A-MPR for CA\_NS\_203 for power class 4 + +For intra-band contiguous CA, AMPR specified in sub-clause 6.2A.3.4.3 applies. + +#### 6.2A.3.4.5 A-MPR for CA\_NS\_203 for power class 5 + +For intra-band contiguous CA, AMPR specified in sub-clause 6.2A.3.4.3 applies. + +#### 6.2A.3.4.6 A-MPR for CA\_NS\_203 for power class 6 + +For intra-band contiguous CA, AMPR specified in sub-clause 6.2A.3.4.3 applies. + +### 6.2A.4 Configured transmitted power for CA + +#### 6.2A.4.1 Configured transmitted power for intra-band UL CA + +A UE configured with carrier aggregation can configure its maximum output power for each uplink activated serving cell $c$ and its total configured maximum output power $P_{CMAX}$ . The definition of the configured UE maximum output power $P_{CMAX,fc}$ for each carrier $f$ of a serving cell $c$ is used for power headroom reporting for carrier $f$ of serving cell $c$ only and is in accordance with that specified in clause 6.2.4 with parameters MPR, A-MPR and P-MPR replaced with those specified in subclause 6.2A.2, 6.2A.3 and 6.2.4, respectively. The UE maximum configured power $P_{CMAX}$ in a transmission occasion is determined by the UL grants for carriers $f$ of all serving cells $c$ with non-zero granted power in the respective reference point. + +For uplink intra-band contiguous carrier aggregation, MPR is specified in clause 6.2A.2. $P_{CMAX}$ is calculated under the assumption that power spectral density for each RB in each component carrier is same. + +The configured UE maximum output power $P_{CMAX}$ shall be set such that the corresponding measured total peak EIRP $P_{UMAX}$ is within the following bounds + +$$P_{Powerclass} - \text{MAX}(\text{MAX}(\text{MPR}, \text{A-MPR}) + \Delta\text{MB}_{P,n}, \text{P-MPR}) - \text{MAX}\{\text{T}(\text{MAX}(\text{MPR}, \text{A-MPR})), \text{T}(\text{P-MPR})\} \leq P_{UMAX} \leq \text{EIRP}_{max}$$ + +with $P_{Powerclass}$ the UE minimum peak EIRP as specified in sub-clause 6.2A.1, $\text{EIRP}_{max}$ the applicable maximum EIRP as specified in sub-clause 6.2A.1, MPR as specified in sub-clause 6.2A.2, A-MPR as specified in sub-clause 6.2A.3, $\Delta\text{MB}_{P,n}$ the peak EIRP relaxation as specified in clause 6.2.1, P-MPR the power management term for the UE as described in 6.2.4. + +The measured configured power $P_{UMAX}$ for carrier aggregation is defined as + +where $p_{UMAX,fc}$ is the linear value of the measured power $P_{UMAX,fc}$ for carrier $f=f(c)$ of serving cell $c$ . The measured total radiated power $P_{TMAX}$ for carrier aggregation is defined as + +where $p_{TMAX,fc}$ is the linear value of the measured total radiated power $P_{TMAX,fc}$ for carrier $f=f(c)$ of serving cell $c$ . The total radiated power $P_{TMAX}$ is bounded by + +$$P_{TMAX} \leq \text{TRP}_{max}$$ + +where $TRP_{max}$ the maximum TRP for the UE power class as specified in sub-clause 6.2A.1. + +The tolerance $T(\Delta P)$ for applicable values of $\Delta P$ (values in dB) is specified in Table 6.2A.4.1-1 and Table 6.2A.4.1-2. + +**Table 6.2A.4.1-1: $P_{UMAX}$ tolerance for FR2-1** + +| Operating Band | $\Delta P$ (dB) | Tolerance $T(\Delta P)$ (dB) | +|----------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|------------------------------| +| n257, n258, n259, n260, n261, n262 | $\Delta P = 0$ | 0 | +| | $0 < \Delta P \leq 2$ | 1.5 | +| | $2 < \Delta P \leq 3$ | 2.0 | +| | $3 < \Delta P \leq 4$ | 3.0 | +| | $4 < \Delta P \leq 5$ | 4.0 | +| | $5 < \Delta P \leq 10$ | 5.0 | +| | $10 < \Delta P \leq 15$ | 7.0 | +| | $15 < \Delta P \leq X$ | 8.0 | +| NOTE: X is the value such that $P_{UMAX}$ lower bound, $P_{Powerclass} - \Delta P - T(\Delta P) =$ minimum output power specified in clause 6.3A.1 | | | + +**Table 6.2A.4.1-2: $P_{UMAX}$ tolerance for FR2-2** + +| Operating Band | $\Delta P$ (dB) | Tolerance $T(\Delta P)$ (dB) | +|----------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|------------------------------| +| n263 | $\Delta P = 0$ | [0] | +| | $0 < \Delta P \leq 2$ | [1.5] | +| | $2 < \Delta P \leq 3$ | [2.0] | +| | $3 < \Delta P \leq 4$ | [3.0] | +| | $4 < \Delta P \leq 5$ | [4.0] | +| | $5 < \Delta P \leq 10$ | [5.0] | +| | $10 < \Delta P \leq 15$ | [7.0] | +| | $15 < \Delta P \leq X$ | [8.0] | +| NOTE: X is the value such that $P_{UMAX}$ lower bound, $P_{Powerclass} - \Delta P - T(\Delta P) =$ minimum output power specified in clause 6.3A.1 | | | + +## 6.2A.4.2 Configured transmitted power for inter-band UL CA + +A UE can configure its maximum output power for each uplink band when it is configured for inter-band UL carrier aggregation with two NR bands each with a single UL CC. For each uplink band $n$ , the configured UE maximum output power $P_{CMAX,fc,n}$ for carrier $f$ of a serving cell $c$ is defined as that available to the reference point of a given transmitter branch that corresponds to the reference point of the higher-layer filtered RSRP measurement as specified in TS 38.215 [11]. + +The configured UE maximum output power $P_{CMAX,fc,n}$ for carrier $f$ of a serving cell $c$ in band $n$ shall be set such that the corresponding measured peak EIRP $P_{UMAX,fc,n}$ is within the following bounds + +$$P_{Powerclass} + \Delta P_{IBE} - \text{MAX}(\text{MAX}(\text{MPR}_{fc,n}, \text{A-MPR}_{fc,n}) + \Delta T_{IB,P,n}, \text{P-MPR}_{fc,n}) - \text{MAX}\{T(\text{MAX}(\text{MPR}_{fc,n}, \text{A-MPR}_{fc,n})), T(\text{P-MPR}_{fc,n})\} \leq P_{UMAX,fc,n} \leq \text{EIRP}_{max,n}$$ + +while the corresponding measured total radiated power in uplink band $n$ , $P_{TMAX,fc,n}$ , is bounded by + +$$P_{TMAX,fc,n} \leq TRP_{max,n}$$ + +with $P_{Powerclass}$ the UE minimum peak EIRP as specified in sub-clause 6.2A.1, $\text{EIRP}_{max,n}$ the applicable maximum EIRP as specified in sub-clause 6.2A.1 for uplink band $n$ and $TRP_{max,n}$ the applicable maximum TRP as specified in sub-clause 6.2A.1 for uplink band $n$ . $\text{MPR}_{fc,n}$ as specified in sub-clause 6.2A.2 for uplink band $n$ , $\text{A-MPR}_{fc,n}$ as specified in sub-clause 6.2A.3 for uplink band $n$ , $\Delta T_{IB,P,n}$ the peak EIRP relaxation as specified in clause 6.2A.1. The requirement is verified in beam peak direction. + +$\Delta P_{IBE}$ , $mpr-PowerBoost-FR2-r16$ and $maxUplinkDutyCycle-FR2$ are described in clause 6.2.4. + +$\text{P-MPR}_{fc,n}$ is the power management maximum output power reduction $\text{P-MPR}_{fc}$ in band $n$ . $\text{P-MPR}_{fc}$ is defined in clause 6.2.4. + +The tolerance $T(\Delta P)$ for applicable values of $\Delta P$ (values in dB) in each band is specified in Table 6.2.4-1. + +## 6.2A.5 Requirements for UL gap (*ul-GapFR2-r17*) for TX power management in CA + +The difference of the measured peak EIRP $P_{\text{UMAX\_GAP\_ON}}$ for CA when UL gap for TX power management is configured and activated, and the measured peak EIRP $P_{\text{UMAX\_GAP\_OFF}}$ when UL gap is not configured or de-activated, shall meet the following requirement: + +$$P_{\text{UMAX\_GAP\_ON}} - P_{\text{UMAX\_GAP\_OFF}} \max((\text{EIRP}_{\text{meas\_peak}} - 23) + 10 * \log_{10}(Z/20), 3)\text{dB}$$ + +where $\text{EIRP}_{\text{meas\_peak}}$ is the measured UE peak EIRP with zero MPR/A-MPR/P-MPR in clause 6.2A.1 for the corresponding power class, and $Z\%$ is duty cycle of the reference measurement channel. $P_{\text{UMAX\_fc\_GAP\_ON}}$ shall be measured outside of the UL gap symbol(s). The period of measurement shall be at least 4 seconds. The requirement is verified with the test metric of EIRP (Link=TX beam peak direction, Meas=Link angle) and in the test $Z$ is set to 20 when *maxUplinkDutyCycle-FR2* is less than 20 or not reported, and should be larger than *maxUplinkDutyCycle-FR2* when *maxUplinkDutyCycle-FR2* is equal to or greater than 20, assuming all CCs share the same TX beam peak direction. The reference measurement channel is specified in Annex A.2.3. + +When UL gap for Tx power management is configured and activated, the reported P-MPRfc shall be less than 3dB. + +When UL gap for Tx power management is not configured and activated, UE shall set the P bit in PHR to 1 in the test when PHR is configured. P-bit is defined in TS 38.321 clause 6.1.3.8 and 6.1.3.9. + +## 6.2D Transmitter power for UL MIMO + +### 6.2D.1 UE maximum output power for UL MIMO + +#### 6.2D.1.0 General + +The requirements in the following clauses define the maximum output power radiated by the UE with *nrofSRS-Ports* set to 2, for any transmission bandwidth within the channel bandwidth for non-CA configuration, unless otherwise stated. MPR shall be applied as specified in clause 6.2D.2 + +For the maximum output power requirement for 2-layer UL MIMO operation, a UE shall be configured for 2-layer UL MIMO transmission as specified in Table 6.2D.1.0-1. + +**Table 6.2D.1.0-1: UL MIMO configuration** + +| Transmission scheme | DCI format | Number of layers | TPMI index | +|-----------------------|----------------|------------------|------------| +| Codebook based uplink | DCI format 0_1 | 2 | 0 | + +The maximum output power requirement for single layer transmission shall apply to a UE that supports ULFPTx feature and is configured for single layer transmission in its declared full power mode [10, TS 38.213] as specified in Table 6.2D.1.0-2. + +**Table 6.2D.1.0-2: PUSCH Configuration for uplink full power transmission (ULFPTx)** + +| ULFPTx Mode | Transmission scheme | DCI format | Modulation | Number of layers | TPMI index | +|-----------------|-----------------------|----------------|----------------------------------|------------------|---------------------| +| Mode-1 | Codebook based uplink | DCI format 0_1 | DFT-s-OFDM, CP-OFDM 1 | 1 | 2 | +| Mode-2 | Codebook based uplink | DCI format 0_1 | DFT-s-OFDM, CP-OFDM | 1 | 0 or 1 2 | +| Mode-full power | Codebook based uplink | DCI format 0_1 | DFT-s-OFDM, CP-OFDM | 1 | 0,1 | + +NOTE 1: For PUSCH configured with ULFPTxModes set to Mode-1, all requirements for 1-layer CP-OFDM based modulation in subsection 6.2D are assumed to be met if the requirement for 2-layer UL MIMO has been validated. + +NOTE 2: TPMI index selected shall be based upon the full power TPMI reported by the UE [10, TS 38.213]. + +NOTE: UL MIMO for FR2 is defined only for FR2-1 in this release of the specification. + +### 6.2D.1.1 UE maximum output power for UL MIMO for power class 1 + +The following requirements define the maximum output power radiated by the PC1 UE. Requirements apply to UEs when configured for 2-layer transmission as well as when configured for single layer uplink full power transmission (ULFPTx), with configuration per clause 6.2D.1.0. + +The minimum peak EIRP requirements are found in Table 6.2D.1.1-1 below. The period of measurement shall be at least one sub frame (1ms). The requirement is verified with the test metric of EIRP (Link=TX beam peak direction, Meas=Link angle). Power class 1 UE is used for fixed wireless access (FWA). + +**Table 6.2D.1.1-1: UE minimum peak EIRP for UL MIMO for power class 1** + +| Operating band | Min peak EIRP (dBm) | +|----------------|---------------------| +| n257 | 40.0 | +| n258 | 40.0 | +| n260 | 38.0 | +| n261 | 40.0 | +| n262 | 34.2 | + +NOTE 1: Minimum peak EIRP is defined as the lower limit without tolerance + +**Table 6.2D.1.1-2: (void)** + +The maximum output power values for TRP and EIRP are found in Table 6.2D.1.1-3 below for UE with UL MIMO. The maximum allowed EIRP is derived from regulatory requirements [8]. The requirements are verified with the test metrics of TRP (Link=TX beam peak direction, Meas=TRP grid) in beam locked mode and EIRP (Link=TX beam peak direction, Meas=Link angle). + +**Table 6.2D.1.1-3: UE maximum output power limits for UL MIMO for power class 1** + +| Operating band | Max TRP (dBm) | Max EIRP (dBm) | +|----------------|---------------|----------------| +| n257 | 35 | 55 | +| n258 | 35 | 55 | +| n260 | 35 | 55 | +| n261 | 35 | 55 | +| n262 | 35 | 55 | + +The minimum EIRP at the 85th percentile of the distribution of radiated power measured over the full sphere around the UE with UL MIMO is defined as the spherical coverage requirement and is found in Table 6.2D.1.1-4 below. The requirement is verified with the test metric of EIRP (Link=Spherical coverage grid, Meas=Link angle). + +**Table 6.2D.1.1-4: UE spherical coverage for UL MIMO for power class 1** + +| Operating band | Min EIRP at 85 %-tile CDF (dBm) | +|---------------------------------------------------------------------------------------|---------------------------------| +| n257 | 32.0 | +| n258 | 32.0 | +| n260 | 30.0 | +| n261 | 32.0 | +| n262 | 26.0 | +| NOTE 1: Minimum EIRP at 85 %-tile CDF is defined as the lower limit without tolerance | | + +## 6.2D.1.2 UE maximum output power for UL MIMO for power class 2 + +The following requirements define the maximum output power radiated by the PC2 UE. Requirements apply to UEs when configured for 2-layer transmission as well as when configured for single layer uplink full power transmission (ULFPTx), with configuration per clause 6.2D.1.0. + +The minimum peak EIRP requirements are found in Table 6.2D.1.2-1 below. The period of measurement shall be at least one sub frame (1ms). The requirement is verified with the test metric of EIRP (Link=TX beam peak direction, Meas=Link angle). + +**Table 6.2D.1.2-1: UE minimum peak EIRP for UL MIMO for power class 2** + +| Operating band | Min peak EIRP (dBm) | +|------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------| +| n257 | 29 | +| n258 | 29 | +| n261 | 29 | +| n262 | 22.9 | +| NOTE 1: Minimum peak EIRP is defined as the lower limit without tolerance.
NOTE 2: Min Peak EIRP refers to the total EIRP for the UL beams peaks. | | + +The maximum output power values for TRP and EIRP are found in Table 6.2D.1.2-2 below. The maximum allowed EIRP is derived from regulatory requirements [8]. The requirements are verified with the test metrics of TRP (Link=TX beam peak direction, Meas=TRP grid) in beam locked mode and EIRP (Link=TX beam peak direction, Meas=Link angle). + +**Table 6.2D.1.2-2: UE maximum output power limits for UL MIMO for power class 2** + +| Operating band | Max TRP (dBm) | Max EIRP (dBm) | +|----------------|---------------|----------------| +| n257 | 23 | 43 | +| n258 | 23 | 43 | +| n261 | 23 | 43 | +| n262 | 23 | 43 | + +**Table 6.2D.1.2-3: (void)** + +The minimum EIRP at the 60th percentile of the distribution of radiated power measured over the full sphere around the UE is defined as the spherical coverage requirement and is found in Table 6.2D.1.2-4 below. The requirement is verified with the test metric of EIRP (Link=Spherical coverage grid, Meas=Link angle). + +**Table 6.2D.1.2-4: UE spherical coverage for UL MIMO for power class 2** + +| Operating band | Min EIRP at 60 %-tile CDF (dBm) | +|---------------------------------------------------------------------------------------|---------------------------------| +| n257 | 18.0 | +| n258 | 18.0 | +| n261 | 18.0 | +| n262 | 11.0 | +| NOTE 1: Minimum EIRP at 60 %-tile CDF is defined as the lower limit without tolerance | | + +### 6.2D.1.3 UE maximum output power for UL MIMO for power class 3 + +The following requirements define the maximum output power radiated by the PC3 UE. Requirements apply to UEs when configured for 2-layer transmission as well as when configured for single layer uplink full power transmission (ULFPTx), with configuration per clause 6.2D.1.0. + +The minimum peak EIRP requirements are found in Table 6.2D.1.3-1 below. The period of measurement shall be at least one sub frame (1 ms). The requirement is verified with the test metric of EIRP (Link=TX beam peak direction, Meas=Link angle). + +**Table 6.2D.1.3-1: UE minimum peak EIRP for UL MIMO for power class 3** + +| Operating band | Min peak EIRP (dBm) | +|----------------------------------------------------------------------------|---------------------| +| n257 | 22.4 | +| n258 | 22.4 | +| n259 | 18.7 | +| n260 | 20.6 | +| n261 | 22.4 | +| n262 | 16.0 | +| NOTE 1: Minimum peak EIRP is defined as the lower limit without tolerance. | | +| NOTE 2: Min Peak EIRP refers to the total EIRP for the UL beams peaks. | | + +The maximum output power values for TRP and EIRP are found in Table 6.2D.1.3-2 below. The maximum allowed EIRP is derived from regulatory requirements [8]. The requirements are verified with the test metrics of TRP (Link=TX beam peak direction, Meas=TRP grid) in beam locked mode and EIRP (Link=TX beam peak direction, Meas=Link angle). + +**Table 6.2D.1.3-2: UE maximum output power limits for UL MIMO for power class 3** + +| Operating band | Max TRP (dBm) | Max EIRP (dBm) | +|----------------|---------------|----------------| +| n257 | 23 | 43 | +| n258 | 23 | 43 | +| n259 | 23 | 43 | +| n260 | 23 | 43 | +| n261 | 23 | 43 | +| n262 | 23 | 43 | + +**Table 6.2D.1.3-3: (void)** + +The minimum EIRP at the 50th percentile of the distribution of radiated power measured over the full sphere around the UE is defined as the spherical coverage requirement and is found in Table 6.2D.1.3-4 below. The requirement is verified with the test metric of EIRP (Link=spherical coverage grid, Meas=Link angle). + +**Table 6.2D.1.3-4: UE spherical coverage for UL MIMO for power class 3** + +| Operating band | Min EIRP at 50 %-tile CDF (dBm) | +|-----------------------------------------------------------------------------------------------------|---------------------------------| +| n257 | 11.5 | +| n258 | 11.5 | +| n259 | 5.8 | +| n260 | 8 | +| n261 | 11.5 | +| NOTE 1: Minimum EIRP at 50 %-tile CDF is defined as the lower limit without tolerance | | +| NOTE 2: The requirements in this table are only applicable for UE which supports single band in FR2 | | + +#### 6.2D.1.4 UE maximum output power for UL MIMO for power class 4 + +The following requirements define the maximum output power radiated by the PC4 UE. Requirements apply to UEs configured for 2-layer transmission as well as UEs configured for single layer uplink full power transmission (ULFPTx), with configuration per clause 6.2D.1.0. + +The minimum peak EIRP requirements are found in Table 6.2D.1.4-1 below. The period of measurement shall be at least one sub frame (1ms). The requirement is verified with the test metric of EIRP (Link=TX beam peak direction, Meas=Link angle). + +**Table 6.2D.1.4-1: UE minimum peak EIRP for UL MIMO for power class 4** + +| Operating band | Min peak EIRP (dBm) | +|----------------------------------------------------------------------------|---------------------| +| n257 | 34 | +| n258 | 34 | +| n260 | 31 | +| n261 | 34 | +| n262 | 28.3 | +| NOTE 1: Minimum peak EIRP is defined as the lower limit without tolerance. | | +| NOTE 2: Min Peak EIRP refers to the total EIRP for the UL beams peaks. | | + +The maximum output power values for TRP and EIRP are found in Table 6.2D.1.4-2 below. The maximum allowed EIRP is derived from regulatory requirements [8]. The requirements are verified with the test metrics of TRP (Link=TX beam peak direction, Meas=TRP grid) in beam locked mode and EIRP (Link=TX beam peak direction, Meas=Link angle). + +**Table 6.2D.1.4-2: UE maximum output power limits for UL MIMO for power class 4** + +| Operating band | Max TRP (dBm) | Max EIRP (dBm) | +|----------------|---------------|----------------| +| n257 | 23 | 43 | +| n258 | 23 | 43 | +| n260 | 23 | 43 | +| n261 | 23 | 43 | +| n262 | 23 | 43 | + +**Table 6.2D.1.4-3: (void)** + +The minimum EIRP at the 20th percentile of the distribution of radiated power measured over the full sphere around the UE is defined as the spherical coverage requirement and is found in Table 6.2D.1.4-4 below. The requirement is verified with the test metric of EIRP (Link=Spherical coverage grid, Meas=Link angle). + +**Table 6.2D.1.4-4: UE spherical coverage for UL MIMO for power class 4** + +| Operating band | Min EIRP at 20 %-tile CDF (dBm) | +|---------------------------------------------------------------------------------------|---------------------------------| +| n257 | 25 | +| n258 | 25 | +| n260 | 19 | +| n261 | 25 | +| n262 | 16.2 | +| NOTE 1: Minimum EIRP at 20 %-tile CDF is defined as the lower limit without tolerance | | + +#### 6.2D.1.5 UE maximum output power for UL MIMO for power class 5 + +The following requirements define the maximum output power radiated by the PC4 UE. Requirements apply to UEs configured for 2-layer transmission as well as UEs configured for single layer uplink full power transmission (ULFPTx), with configuration per clause 6.2D.1.0. + +The minimum peak EIRP requirements are found in Table 6.2D.1.5-1 below. The period of measurement shall be at least one sub frame (1ms). The requirement is verified with the test metric of EIRP (Link=TX beam peak direction, Meas=Link angle). Power class 5 UE is used for fixed wireless access (FWA). + +**Table 6.2D.1.5-1: UE minimum peak EIRP for UL MIMO for power class 5** + +| Operating band | Min peak EIRP (dBm) | +|---------------------------------------------------------------------------|---------------------| +| n257 | 30 | +| n258 | 30.4 | +| n259 | 27.7 | +| NOTE 1: Minimum peak EIRP is defined as the lower limit without tolerance | | + +The maximum output power values for TRP and EIRP are found in Table 6.2D.1.5-3 below for UE with UL MIMO. The maximum allowed EIRP is derived from regulatory requirements. The requirements are verified with the test metrics of TRP (Link=TX beam peak direction, Meas=TRP grid) in beam locked mode and EIRP (Link=TX beam peak direction, Meas=Link angle). + +**Table 6.2D.1.5-2: UE maximum output power limits for UL MIMO for power class 5** + +| Operating band | Max TRP (dBm) | Max EIRP (dBm) | +|----------------|---------------|----------------| +| n257 | 23 | 43 | +| n258 | 23 | 43 | +| n259 | 23 | 43 | + +The minimum EIRP at the 85th percentile of the distribution of radiated power measured over the full sphere around the UE with UL MIMO is defined as the spherical coverage requirement and is found in Table 6.2D.1.5-3 below. The requirement is verified with the test metric of EIRP (Link=Spherical coverage grid, Meas=Link angle). + +**Table 6.2D.1.5-3: UE spherical coverage for UL MIMO for power class 5** + +| Operating band | Min EIRP at 85 %-tile CDF (dBm) | +|---------------------------------------------------------------------------------------|---------------------------------| +| n257 | 22 | +| n258 | 22.4 | +| n259 | 19.7 | +| NOTE 1: Minimum EIRP at 85 %-tile CDF is defined as the lower limit without tolerance | | + +## 6.2D.1.6 UE maximum output power for UL MIMO for power class 6 + +The following requirements define the maximum output power radiated by the PC6 UE. Requirements apply to UEs configured for 2-layer transmission as well as UEs configured for single layer uplink full power transmission (ULFPTx), with configuration per clause 6.2D.1.0. + +The minimum peak EIRP requirements are found in Table 6.2D.1.6-1 below. The period of measurement shall be at least one sub frame (1ms). The requirement is verified with the test metric of EIRP (Link=TX beam peak direction, Meas=Link angle). + +**Table 6.2D.1.6-1: UE minimum peak EIRP for UL MIMO for power class 6** + +| Operating band | Min peak EIRP (dBm) | +|---------------------------------------------------------------------------|---------------------| +| n257 | 30 | +| n258 | 30.4 | +| n261 | 30 | +| NOTE 1: Minimum peak EIRP is defined as the lower limit without tolerance | | + +The maximum output power values for TRP and EIRP are found in Table 6.2D.1.5-2 below for UE with UL MIMO. The maximum allowed EIRP is derived from regulatory requirements [8]. The requirements are verified with the test metrics of TRP (Link=TX beam peak direction, Meas=TRP grid) in beam locked mode and EIRP (Link=TX beam peak direction, Meas=Link angle). + +**Table 6.2D.1.6-2: UE maximum output power limits for UL MIMO for power class 6** + +| Operating band | Max TRP (dBm) | Max EIRP (dBm) | +|----------------|---------------|----------------| +| n257 | 23 | 43 | +| n258 | 23 | 43 | +| n261 | 23 | 43 | + +The minimum EIRP measured over the spherical coverage evaluation areas is defined as the spherical coverage requirement and is found in Table 6.2D.1.6-3 below. UE spherical coverage evaluation areas are found in Table 6.2.1.6-3a in clause 6.2.1.6, by consisting of Area-1 and Area-2, in the reference coordinate system in Annex J.1. The requirement is verified with the test metric of EIRP (Link= Spherical coverage grid, Meas=Link angle). + +**Table 6.2D.1.6-3: UE spherical coverage for UL MIMO for power class 6** + +| Operating band | Min EIRP over UE spherical coverage evaluation areas (dBm) | +|----------------|------------------------------------------------------------| +| n257 | 20 | +| n258 | 20.4 | +| n261 | 20 | + +NOTE 1: Minimum EIRP over UE spherical coverage evaluation areas is defined as the lower limit without tolerance + +NOTE 2: The requirements in this table are verified only under normal temperature conditions as defined in Annex E.2.1. + +NOTE 3: The requirements in this table are applicable to FR2 PC6 UE with the network signalling *[highSpeedMeasFlag-r17]* configured as *[set2]*. + +## 6.2D.2 UE maximum output power reduction for modulation / channel bandwidth for UL MIMO + +### 6.2D.2.1 UE maximum output power reduction for modulation / channel bandwidth for UL MIMO for power class 1 + +For UEs configured for 2-layer transmission as well as UEs configured for single layer uplink full power transmission (ULFPTx), the allowed Maximum Power Reduction (MPR) for the maximum output power in Table 6.2D.1.1-1 is specified in sub-clause 6.2.2.1. The requirements shall be met with configurations specified in sub-clause 6.2D.1.0. + +For the UE maximum output power modified by MPR, the power limits specified in clause 6.2D.4 apply. + +### 6.2D.2.2 UE maximum output power reduction for modulation / channel bandwidth for UL MIMO for power class 2 + +For UEs configured for 2-layer transmission as well as UEs configured for single layer uplink full power transmission (ULFPTx), the allowed Maximum Power Reduction (MPR) for the maximum output power in Table 6.2D.1.2-1 is specified in sub-clause 6.2.2.2. The requirements shall be met with configurations specified in sub-clause 6.2D.1.0. + +For the UE maximum output power modified by MPR, the power limits specified in clause 6.2D.4 apply. + +### 6.2D.2.3 UE maximum output power reduction for modulation / channel bandwidth for UL MIMO for power class 3 + +For UEs configured for 2-layer transmission as well as UEs configured for single layer uplink full power transmission (ULFPTx), the allowed Maximum Power Reduction (MPR) for the maximum output power in Table 6.2D.1.3-1 is specified in sub-clause 6.2.2.3. The requirements shall be met with configurations specified in sub-clause 6.2D.1.0. + +For the UE maximum output power modified by MPR, the power limits specified in clause 6.2D.4 apply. + +#### **6.2D.2.4 UE maximum output power reduction for modulation / channel bandwidth for UL MIMO for power class 4** + +For UEs configured for 2-layer transmission as well as UEs configured for single layer uplink full power transmission (ULFPTx), the allowed Maximum Power Reduction (MPR) for the maximum output power in Table 6.2D.1.4-1 is specified in sub-clause 6.2.2.4. The requirements shall be met with configurations specified in sub-clause 6.2D.1.0. + +For the UE maximum output power modified by MPR, the power limits specified in clause 6.2D.4 apply. + +#### **6.2D.2.5 UE maximum output power reduction for modulation / channel bandwidth for UL MIMO for power class 5** + +For UEs configured for 2-layer transmission as well as UEs configured for single layer uplink full power transmission (ULFPTx), the allowed Maximum Power Reduction (MPR) for the maximum output power in Table 6.2D.1.4-1 is specified in sub-clause 6.2.2.4. The requirements shall be met with configurations specified in sub-clause 6.2D.1.0. + +For the UE maximum output power modified by MPR, the power limits specified in clause 6.2D.4 apply. + +#### **6.2D.2.6 UE maximum output power reduction for modulation / channel bandwidth for UL MIMO for power class 6** + +For UEs configured for 2-layer transmission as well as UEs configured for single layer uplink full power transmission (ULFPTx), the allowed Maximum Power Reduction (MPR) for the maximum output power in Table 6.2D.1.6-1 is specified in sub-clause 6.2.2.6. The requirements shall be met with configurations specified in sub-clause 6.2D.1.0. + +For the UE maximum output power modified by MPR, the power limits specified in clause 6.2D.6 apply. + +### **6.2D.3 UE maximum output power reduction with additional requirements for UL MIMO** + +#### **6.2D.3.1 UE maximum output power reduction with additional requirements for UL MIMO for power class 1** + +For UEs configured for 2-layer transmission as well as UEs configured for single layer uplink full power transmission (ULFPTx), the A-MPR values specified in clause 6.2.3 shall apply to the maximum output power specified in Table 6.2D.1.1-1. The requirements shall be met with the configurations specified in sub-clause 6.2D.1.0. + +For the UE maximum output power modified by A-MPR, the power limits specified in clause 6.2D.4 apply. + +#### **6.2D.3.2 UE maximum output power reduction with additional requirements for UL MIMO for power class 2** + +For UEs configured for 2-layer transmission as well as UEs configured for single layer uplink full power transmission (ULFPTx), the A-MPR values specified in clause 6.2.3 shall apply to the maximum output power specified in Table 6.2D.1.2-1. The requirements shall be met with the configurations specified in clause 6.2D.1.0. + +For the UE maximum output power modified by A-MPR, the power limits specified in clause 6.2D.4 apply. + +#### **6.2D.3.3 UE maximum output power reduction with additional requirements for UL MIMO for power class 3** + +For UEs configured for 2-layer transmission as well as UEs configured for single layer uplink full power transmission (ULFPTx), the A-MPR values specified in clause 6.2.3 shall apply to the maximum output power specified in Table 6.2D.1.3-1. The requirements shall be met with the configurations specified in clause 6.2D.1.0. + +For the UE maximum output power modified by A-MPR, the power limits specified in clause 6.2D.4 apply. + +#### 6.2D.3.4 UE maximum output power reduction with additional requirements for UL MIMO for power class 4 + +For UEs configured for 2-layer transmission as well as UEs configured for single layer uplink full power transmission (ULFPTx), the A-MPR values specified in clause 6.2.3 shall apply to the maximum output power specified in Table 6.2D.1.4-1. The requirements shall be met with the configurations specified in clause 6.2D.1.0. + +#### 6.2D.3.5 UE maximum output power reduction with additional requirements for UL MIMO for power class 5 + +For UEs configured for 2-layer transmission as well as UEs configured for single layer uplink full power transmission (ULFPTx), the A-MPR values specified in clause 6.2.3 shall apply to the maximum output power specified in Table 6.2D.1.4-1. The requirements shall be met with the configurations specified in clause 6.2D.1.0. + +#### 6.2D.3.6 UE maximum output power reduction with additional requirements for UL MIMO for power class 6 + +For UEs configured for 2-layer transmission as well as UEs configured for single layer uplink full power transmission (ULFPTx), the A-MPR values specified in clause 6.2.3 shall apply to the maximum output power specified in Table 6.2D.1.6-1. The requirements shall be met with the configurations specified in clause 6.2D.1.0. + +### 6.2D.4 Configured transmitted power for UL MIMO + +For UEs configured for 2-layer transmission as well as UEs configured for single layer uplink full power transmission (ULFPTx), the configured maximum output power $P_{\text{CMAX},c}$ for serving cell $c$ is defined as sum of all streams and is bound by limits set in clause 6.2.4. + +## 6.2K Transmitter power for simultaneous transmission to multiple directions + +### 6.2K.1 UE maximum output power for simultaneous transmission to multiple directions + +For UEs configured for simultaneous transmission to multiple directions, the maximum output power for each of indicated joint/UL TCI states is specified in clause 6.2.1. + +### 6.2K.2 UE maximum output power reduction for simultaneous transmission to multiple directions + +For UEs configured for simultaneous transmission to multiple directions, the maximum output power reduction for each of indicated joint/UL TCI states is specified in clause 6.2.2. + +### 6.2K.3 UE maximum output power with additional requirements for simultaneous transmission to multiple directions + +For UEs configured for simultaneous transmission to multiple directions, the maximum output power with additional requirements for each of indicated joint/UL TCI states is specified in clause 6.2.3. + +## 6.2K.4 Configured transmitted power for simultaneous transmission to multiple directions + +A UE configured for simultaneous transmission to multiple directions can configure two maximum output powers. The configured UE maximum output power $P_{\text{CMAX},f,c,k}$ for each of joint/UL TCI states $k$ ( $k=0,1$ ) indicated for simultaneous transmission to multiple directions of carrier $f$ and serving cell $c$ is defined as that available to the reference point of a given transmitter branch that corresponds to the reference point of the higher-layer filtered RSRP measurement as specified in TS 38.215 [11]. + +The configured UE maximum output power $P_{\text{CMAX},f,c,k}$ shall be set such that the corresponding measured peak EIRP $P_{\text{UMAX},f,c,k}$ is within the following bounds + +$$P_{\text{Powerclass}} + \Delta P_{\text{IBE}} - \text{MAX}(\text{MAX}(\text{MPR}_{f,c,k}, \text{A-MPR}_{f,c,k}) + \Delta \text{MPR}_{\text{STxMP}} + \Delta \text{MB}_{P,n}, \text{P-MPR}_{f,c,k}) - \text{MAX}\{T(\text{MAX}(\text{MPR}_{f,c,k}, \text{A-MPR}_{f,c,k}) + \Delta \text{MPR}_{\text{STxMP}}), T(\text{P-MPR}_{f,c,k})\} - \Delta T_{\text{STxMP}} \leq P_{\text{UMAX},f,c,k} \leq \text{EIRP}_{\text{max}}$$ + +and $P_{\text{UMAX},f,c}$ , the corresponding measured peak EIRP for carrier $f$ of a serving cell $c$ , aggregated over all indicated joint/UL TCI states in a given direction, satisfies over all directions + +$$P_{\text{UMAX},f,c} \leq \text{EIRP}_{\text{max}}$$ + +while the corresponding measured total radiated power $P_{\text{TMAX},f,c}$ is bounded by + +$$P_{\text{TMAX},f,c} \leq \text{TRP}_{\text{max}}$$ + +with $P_{\text{Powerclass}}$ the UE minimum peak EIRP as specified in sub-clause 6.2K.1, $\text{EIRP}_{\text{max}}$ the applicable maximum EIRP as specified in sub-clause 6.2.1, $\text{MPR}_{f,c,k}$ as specified in sub-clause 6.2K.2, $\text{A-MPR}_{f,c,k}$ as specified in sub-clause 6.2K.3, $\Delta \text{MB}_{P,n}$ the peak EIRP relaxation as specified in clause 6.2.1 and $\text{TRP}_{\text{max}}$ the maximum TRP for the UE power class as specified in sub-clause 6.2.1. $\Delta P_{\text{IBE}}$ is 1.0 dB if UE declares support for *mpr-PowerBoost-FR2-r16*, UL transmission is QPSK, $\text{MPR}_{f,c,k} = 0$ and when NS\_200 applies and the network configures the UE to operate with *mpr-PowerBoost-FR2-r16* otherwise $\Delta P_{\text{IBE}}$ is 0.0 dB. $\Delta \text{MPR}_{\text{STxMP}}$ is [3.0] dB if two TCI states are indicated for simultaneous transmission to multiple directions, 0.0 dB otherwise. $\Delta T_{\text{STxMP}}$ is specified in sub-clause 6.2K.1. The requirement is verified in beam peak direction. + +$\text{P-MPR}_{f,c,k}$ is the power management maximum output power reduction $\text{P-MPR}_{f,c}$ for each of indicated joint/UL TCI states. $\text{P-MPR}_{f,c}$ is defined in clause 6.2.4. + +The tolerance $T(\Delta P)$ for applicable values of $\Delta P$ (values in dB) is specified in Tables 6.2.4-1 and 6.2.4-2. + +## 6.3 Output power dynamics + +### 6.3.1 Minimum output power + +#### 6.3.1.0 General + +The minimum controlled output power of the UE is defined as the EIRP in the channel bandwidth for all transmit bandwidth configurations (resource blocks) when the power is set to a minimum value. + +The minimum output power is defined as the mean power in at least one sub frame (1ms). + +#### 6.3.1.1 Minimum output power for power class 1 + +For power class 1 UE, the minimum output power shall not exceed the values specified in Table 6.3.1.1-1 for each operating band supported. The minimum power is verified in beam locked mode with the test metric of EIRP (Link=TX beam peak direction, Meas=Link angle). + +**Table 6.3.1.1-1: Minimum output power for power class 1** + +| Operating band | Channel bandwidth (MHz) | Minimum output power (dBm) | Measurement bandwidth (MHz) | +|------------------------------|-------------------------|----------------------------|-----------------------------| +| n257, n258, n260, n261, n262 | 50 | 4 | 47.58 | +| | 100 | 4 | 95.16 | +| | 200 | 4 | 190.20 | +| | 400 | 4 | 380.28 | +| n263 | 100 | 4 | 95.16 | +| | 400 | 4 | 381.12 | +| | 800 | 4 | 715.20 | +| | 1600 | 4 | 1429.44 | +| | 2000 | 4 | 1705.92 | + +### 6.3.1.2 Minimum output power for power class 2, 3, and 4 + +The minimum output power shall not exceed the values specified in Table 6.3.1.2-1 for each operating band supported. The minimum power is verified in beam locked mode with the test metric of EIRP (Link=TX beam peak direction, Meas=Link angle). + +**Table 6.3.1.2-1: Minimum output power for power class 2, 3, and 4** + +| Operating band | Channel bandwidth (MHz) | Minimum output power (dBm) | Measurement bandwidth (MHz) | +|------------------------------------|-------------------------|----------------------------|-----------------------------| +| n257, n258, n259, n260, n261, n262 | 50 | -13 | 47.58 | +| | 100 | -13 | 95.16 | +| | 200 | -13 | 190.20 | +| | 400 | -13 | 380.28 | +| n263 | 100 | -13 | 95.16 | +| | 400 | -13 | 381.12 | +| | 800 | -13 | 715.20 | +| | 1600 | -13 | 1429.44 | +| | 2000 | -13 | 1705.92 | + +NOTE 1: n260 is not applied for power class 2. +NOTE 2: n259 is not applied for power class 4. +NOTE 3: power class 4 is not applicable to n263 + +### 6.3.1.3 Minimum output power for power class 5 and 6 + +The minimum output power shall not exceed the values specified in Table 6.3.1.3-1 for each operating band supported. The minimum power is verified in beam locked mode with the test metric of EIRP (Link=TX beam peak direction, Meas=Link angle). + +**Table 6.3.1.3-1: Minimum output power for power class 5 and 6** + +| Operating band | Channel bandwidth (MHz) | Minimum output power (dBm) | Measurement bandwidth (MHz) | +|------------------------|-------------------------|----------------------------|-----------------------------| +| n257, n258, n259, n261 | 50 | -6 | 47.52 | +| | 100 | -6 | 95.04 | +| | 200 | -6 | 190.08 | +| | 400 | -6 | 380.16 | + +### 6.3.1.4 Minimum output power for power class 7 + +The minimum output power shall not exceed the values specified in Table 6.3.1.4-1 for each operating band supported. The minimum power is verified in beam locked mode with the test metric of EIRP (Link=TX beam peak direction, Meas=Link angle). + +**Table 6.3.1.4-1: Minimum output power for power class 7** + +| Operating band | Channel bandwidth (MHz) | Minimum output power (dBm) | Measurement bandwidth (MHz) | +|------------------|-------------------------|----------------------------|-----------------------------| +| n257, n258, n261 | 50 | -13 | 47.58 | +| | 100 | -13 | 95.16 | + +## 6.3.2 Transmit OFF power + +The transmit OFF power is defined as the TRP in the channel bandwidth when the transmitter is OFF. The transmitter is considered OFF when the UE is not allowed to transmit on any of its ports. + +The transmit OFF power shall not exceed the values specified in Tables 6.3.2-1 and 6.3.2-2 for each operating band supported. The requirement is verified with the test metric of TRP (Link=TX beam peak direction, Meas=TRP grid). + +**Table 6.3.2-1: Transmit OFF power for FR2-1** + +| Operating band | Channel bandwidth / Transmit OFF power (dBm) / measurement bandwidth | | | | +|------------------------------------|----------------------------------------------------------------------|-----------|------------|------------| +| | 50 MHz | 100 MHz | 200 MHz | 400 MHz | +| n257, n258, n259, n260, n261, n262 | -35 | -35 | -35 | -35 | +| | 47.58 MHz | 95.16 MHz | 190.20 MHz | 380.28 MHz | + +**Table 6.3.2-2: Transmit OFF power for FR2-2** + +| Operating band | Channel bandwidth / Transmit OFF power (dBm) / measurement bandwidth | | | | | +|----------------|----------------------------------------------------------------------|------------|---------|----------|----------| +| | 100 MHz | 400 MHz | 800 MHz | 1600 MHz | 2000 MHz | +| n263 | -35 | -35 | -35 | -35 | -35 | +| | 95.16 MHz | 381.12 MHz | 715.20 | 1429.44 | 1705.92 | + +For UE indicating *ul-GapFR2-r17*, UE shall meet OFF power requirement defined in this clause for the band for which UL transmission is stopped in the activated UL gap. + +## 6.3.3 Transmit ON/OFF time mask + +### 6.3.3.1 General + +The transmit ON/OFF time mask defines the transient period(s) allowed + +- between transmit OFF power and transmit ON power symbols (transmit ON/OFF) +- between continuous ON-power transmissions when power change or RB hopping is applied. + +In case of RB hopping, transition period is shared symmetrically. + +Unless otherwise stated the minimum requirements in clause 6.5 apply also in transient periods. + +The transmit ON/OFF time mask is defined as a directional requirement. The requirement is verified in beam locked mode at beam peak direction. The maximum allowed EIRP OFF power level is -30dBm at beam peak direction. The requirement is verified with the test metric of EIRP (Link=TX beam peak direction, Meas=Link angle). + +In the following sub-clauses, following definitions apply: + +- A slot transmission is a Type A transmission. +- A long subslot transmission is a Type B transmission with more than 2 symbols. + +- A short subplot transmission is a Type B transmission with 1 or 2 symbols. + +### 6.3.3.2 General ON/OFF time mask + +The general ON/OFF time mask defines the observation period allowed between transmit OFF and ON power. ON/OFF scenarios include: contiguous, and non-contiguous transmission, etc + +The OFF power measurement period is defined in a duration of at least one slot excluding any transient periods. The ON power is defined as the mean power over one slot excluding any transient period. + +![Figure 6.3.3.2-1: General ON/OFF time mask for NR UL transmission in FR2. The diagram shows two power level plots over time. The left plot shows a transition from an OFF power level to an ON power level at the start of a 'Start slot'. The right plot shows a transition from an ON power level to an OFF power level at the end of an 'End slot'. Both plots indicate a 5μs transient period at the boundary. Arrows indicate the 'End of OFF power requirement', 'Start of ON power requirement', 'End of ON power requirement', and 'Start of OFF power requirement'.](89d2e4c002294cf6ffee801e84670cc5_img.jpg) + +Figure 6.3.3.2-1: General ON/OFF time mask for NR UL transmission in FR2. The diagram shows two power level plots over time. The left plot shows a transition from an OFF power level to an ON power level at the start of a 'Start slot'. The right plot shows a transition from an ON power level to an OFF power level at the end of an 'End slot'. Both plots indicate a 5μs transient period at the boundary. Arrows indicate the 'End of OFF power requirement', 'Start of ON power requirement', 'End of ON power requirement', and 'Start of OFF power requirement'. + +Figure 6.3.3.2-1: General ON/OFF time mask for NR UL transmission in FR2 + +### 6.3.3.3 Transmit power time mask for slot and short or long subplot boundaries + +The transmit power time mask for slot and a long subplot transmission boundaries defines the transient periods allowed between slot and long subplot PUSCH transmissions. For PUSCH-PUCCH and PUSCH-SRS transitions and multiplexing the time masks in sub-clause 6.3.3.7 apply. + +The transmit power time mask for slot or long subplot and short subplot transmission boundaries defines the transient periods allowed between slot or long subplot and short subplot transmissions. The time masks in sub-clause 6.3.3.8 apply. + +The transmit power time mask for short subplot transmission boundaries defines the transient periods allowed between short subplot transmissions. The time masks in sub-clause 6.3.3.9 apply. + +### 6.3.3.4 PRACH time mask + +The PRACH ON power is specified as the mean power over the PRACH measurement period excluding any transient periods as shown in Figure 6.3.3.4-1. The measurement period for different PRACH preamble format is specified in Table 6.3.3.4-1. + +**Table 6.3.3.4-1: PRACH ON power measurement period** + +| Format | SCS | Measurement period | Note | +|--------------------------------|---------|--------------------------------------------------------------------|------------| +| A 1 | 60 kHz | 0.035677 ms | | +| | 120 kHz | 0.017839 ms | | +| | 480 kHz | 0.004460 ms | | +| | 960 kHz | 0.002230 ms | | +| A 2 | 60 kHz | 0.071354 ms | | +| | 120 kHz | 0.035677 ms | | +| | 480 kHz | 0.008919 ms | | +| | 960 kHz | 0.004460 ms | | +| A 3 | 60 kHz | 0.107031 ms | | +| | 120 kHz | 0.053516 ms | | +| | 480 kHz | 0.013379 ms | | +| | 960 kHz | 0.006690 ms | | +| B 1 | 60 kHz | 0.035091 ms | | +| | 120 kHz | 0.0175455 ms | | +| | 480 kHz | 0.004386 ms | | +| | 960 kHz | 0.002193 ms | | +| B 4 | 60 kHz | 0.207617 ms | | +| | 120 kHz | 0.103809 ms | | +| | 480 kHz | 0.025952 ms | | +| | 960 kHz | 0.012976 ms | | +| A 1 /B 1 | 60 kHz | 0.035677 ms for front X1 occasion
0.035091 ms for last occasion | X1 = [2,5] | +| | 120 kHz | 0.017839 ms for front X1 occasion
0.017546 ms for last occasion | | +| | 480 kHz | 0.004460 ms for front X1 occasion
0.004386 ms for last occasion | | +| | 960 kHz | 0.002230 ms for front X1 occasion
0.002193 ms for last occasion | | +| A 2 /B 2 | 60 kHz | 0.071354 ms for front X2 occasion
0.069596 ms for last occasion | X2 = [1,2] | +| | 120 kHz | 0.035677 ms for front X2 occasion
0.034798 ms for last occasion | | +| | 480 kHz | 0.008919 ms for front X2 occasion
0.008700 ms for last occasion | | +| | 960 kHz | 0.004460 ms for front X2 occasion
0.004350 ms for last occasion | | +| A 3 /B 3 | 60 kHz | 0.107031 ms for first occasion
0.104101 ms for second occasion | | +| | 120 kHz | 0.053515 ms for first occasion
0.052050 ms for second occasion | | +| | 480 kHz | 0.013379 ms for first occasion
0.013013 ms for second occasion | | +| | 960 kHz | 0.006690 ms for first occasion
0.006506 ms for second occasion | | +| C 0 | 60 kHz | 0.026758 ms | | +| | 120 kHz | 0.013379 ms | | +| | 480 kHz | 0.003345 ms | | +| | 960 kHz | 0.001672 ms | | +| C 2 | 60 kHz | 0.083333 ms | | +| | 120 kHz | 0.0416667 ms | | +| | 480 kHz | 0.010417 ms | | +| | 960 kHz | 0.005208 ms | | + +NOTE: For PRACH on PRACH occasion start from begin of 0ms or 0.5 ms boundary, the measurement period will plus 0.032552 µs + +![Figure 6.3.3.4-1: PRACH ON/OFF time mask diagram. It shows a green rectangular block labeled 'PRACH'. A blue curve represents the power level. Vertical dashed lines mark the start and end of the ON power requirement, which corresponds to the duration of the PRACH block. Horizontal arrows indicate the 'Start of ON power requirement' and 'End of ON power requirement'. Outside the ON period, the power drops to a lower level. Vertical dashed lines mark the 'End of OFF power requirement' before the start and the 'Start of OFF power requirement' after the end. Two '5μs Transient period' labels with double-headed arrows are shown at the transitions between ON and OFF power levels.](00f2e7c3d8a12df65c41a981bad8d89d_img.jpg) + +Figure 6.3.3.4-1: PRACH ON/OFF time mask diagram. It shows a green rectangular block labeled 'PRACH'. A blue curve represents the power level. Vertical dashed lines mark the start and end of the ON power requirement, which corresponds to the duration of the PRACH block. Horizontal arrows indicate the 'Start of ON power requirement' and 'End of ON power requirement'. Outside the ON period, the power drops to a lower level. Vertical dashed lines mark the 'End of OFF power requirement' before the start and the 'Start of OFF power requirement' after the end. Two '5μs Transient period' labels with double-headed arrows are shown at the transitions between ON and OFF power levels. + +Figure 6.3.3.4-1: PRACH ON/OFF time mask + +6.3.3.5 Void + +6.3.3.6 SRS time mask + +In the case a single SRS transmission, the ON power is defined as the mean power over the symbol duration excluding any transient period; Figure 6.3.3.6-1. + +![Figure 6.3.3.6-1: Single SRS time mask for NR UL transmission diagram. It shows a single green rectangular block labeled 'SRS'. A blue curve represents the power level. Vertical dashed lines mark the start and end of the 'SRS ON power requirement', which corresponds to the duration of the SRS block. Horizontal arrows indicate the 'Start of ON power requirement' and 'End of ON power requirement'. Outside the ON period, the power drops to a lower level. Vertical dashed lines mark the 'End of OFF power requirement' before the start and the 'Start of OFF power requirement' after the end. Two '5μs Transient period' labels with double-headed arrows are shown at the transitions between ON and OFF power levels.](25b39aa72b2c5eba0a4e8263f6e57908_img.jpg) + +Figure 6.3.3.6-1: Single SRS time mask for NR UL transmission diagram. It shows a single green rectangular block labeled 'SRS'. A blue curve represents the power level. Vertical dashed lines mark the start and end of the 'SRS ON power requirement', which corresponds to the duration of the SRS block. Horizontal arrows indicate the 'Start of ON power requirement' and 'End of ON power requirement'. Outside the ON period, the power drops to a lower level. Vertical dashed lines mark the 'End of OFF power requirement' before the start and the 'Start of OFF power requirement' after the end. Two '5μs Transient period' labels with double-headed arrows are shown at the transitions between ON and OFF power levels. + +Figure 6.3.3.6-1: Single SRS time mask for NR UL transmission + +In the case multiple consecutive SRS transmission, the ON power is defined as the mean power for each symbol duration excluding any transient period. See Figure 7.7.4-2 + +![Figure 6.3.3.6-2: Consecutive SRS time mask for the case when no power change is required diagram. It shows four consecutive green rectangular blocks, each labeled 'SRS'. A blue curve represents the power level, which is high during the SRS blocks and drops to a lower level between them. A long horizontal arrow labeled 'SRS ON power requirement on consecutive NR symbols' spans across all four SRS blocks. Vertical dashed lines mark the start and end of this combined ON period. Horizontal arrows indicate the 'Start of ON power requirement' and 'End of ON power requirement'. Outside the combined ON period, the power drops to a lower level. Vertical dashed lines mark the 'End of OFF power requirement' before the start and the 'Start of OFF power requirement' after the end. Two '5μs Transient period' labels with double-headed arrows are shown at the transitions between the combined ON period and the OFF power level.](151a35d9e788ba69f2b263b91792a75d_img.jpg) + +Figure 6.3.3.6-2: Consecutive SRS time mask for the case when no power change is required diagram. It shows four consecutive green rectangular blocks, each labeled 'SRS'. A blue curve represents the power level, which is high during the SRS blocks and drops to a lower level between them. A long horizontal arrow labeled 'SRS ON power requirement on consecutive NR symbols' spans across all four SRS blocks. Vertical dashed lines mark the start and end of this combined ON period. Horizontal arrows indicate the 'Start of ON power requirement' and 'End of ON power requirement'. Outside the combined ON period, the power drops to a lower level. Vertical dashed lines mark the 'End of OFF power requirement' before the start and the 'Start of OFF power requirement' after the end. Two '5μs Transient period' labels with double-headed arrows are shown at the transitions between the combined ON period and the OFF power level. + +Figure 6.3.3.6-2: Consecutive SRS time mask for the case when no power change is required + +When power change between consecutive SRS transmissions is required, then Figure 6.3.3.6-3 and Figure 6.3.3.6-4 apply. + +![Figure 6.3.3.6-3: Consecutive SRS time mask for the case when power change is required and when 60kHz SCS is used in FR2. The diagram shows four consecutive SRS transmissions. Each SRS transmission is followed by a 5us transient period. The SRS ON power requirement is indicated for each SRS. The End of OFF power requirement is shown at the beginning, and the Start of OFF power requirement is shown at the end.](3216c311c376930b9cb661d4ee835732_img.jpg) + +Figure 6.3.3.6-3: Consecutive SRS time mask for the case when power change is required and when 60kHz SCS is used in FR2. The diagram shows four consecutive SRS transmissions. Each SRS transmission is followed by a 5us transient period. The SRS ON power requirement is indicated for each SRS. The End of OFF power requirement is shown at the beginning, and the Start of OFF power requirement is shown at the end. + +Figure 6.3.3.6-3: Consecutive SRS time mask for the case when power change is required and when 60kHz SCS is used in FR2 + +![Figure 6.3.3.6-4: Consecutive SRS time mask for the case when power change is required and when 120kHz SCS is used in FR2. The diagram shows two consecutive SRS transmissions with a gap between them. The gap duration is 8.93us. Each SRS transmission is followed by a 5us transient period. The SRS ON power requirement is indicated for each SRS. The End of OFF power requirement is shown at the beginning, and the Start of OFF power requirement is shown at the end. Notes indicate that the 5us transient period will be taken in the blanked SRS symbol.](a2266c471758a61aa9eeab6aab8696b4_img.jpg) + +Figure 6.3.3.6-4: Consecutive SRS time mask for the case when power change is required and when 120kHz SCS is used in FR2. The diagram shows two consecutive SRS transmissions with a gap between them. The gap duration is 8.93us. Each SRS transmission is followed by a 5us transient period. The SRS ON power requirement is indicated for each SRS. The End of OFF power requirement is shown at the beginning, and the Start of OFF power requirement is shown at the end. Notes indicate that the 5us transient period will be taken in the blanked SRS symbol. + +Figure 6.3.3.6-4: Consecutive SRS time mask for the case when power change is required and when 120kHz SCS is used in FR2 + +### 6.3.3.7 PUSCH-PUCCH and PUSCH-SRS time masks + +The PUCCH/PUSCH/SRS time mask defines the observation period between sounding reference symbol (SRS) and an adjacent PUSCH/PUCCH symbol and subsequent UL transmissions. The time masks apply for all types of frame structures and their allowed PUCCH/PUSCH/SRS transmissions unless otherwise stated. + +![Figure 6.3.3.7-1: PUCCH/PUSCH/SRS time mask when there is a transmission before or after or both before and after SRS. The diagram shows a sequence of slots: N_b slot, N_{i-1} slot, SRS, and N_{i+2} slot. Transient periods of 5us are shown between the SRS and the adjacent PUSCH/PUCCH transmissions. The Start of N_{i-1} power PUSCH/PUCCH and the End of N_{i-1} power PUSCH/PUCCH are indicated. The Start of N_{i+2} power PUSCH/PUCCH is also indicated.](cf648eab639f63a505727a234d0748d1_img.jpg) + +Figure 6.3.3.7-1: PUCCH/PUSCH/SRS time mask when there is a transmission before or after or both before and after SRS. The diagram shows a sequence of slots: N\_b slot, N\_{i-1} slot, SRS, and N\_{i+2} slot. Transient periods of 5us are shown between the SRS and the adjacent PUSCH/PUCCH transmissions. The Start of N\_{i-1} power PUSCH/PUCCH and the End of N\_{i-1} power PUSCH/PUCCH are indicated. The Start of N\_{i+2} power PUSCH/PUCCH is also indicated. + +Figure 6.3.3.7-1: PUCCH/PUSCH/SRS time mask when there is a transmission before or after or both before and after SRS + +When there is no transmission preceding SRS transmission or succeeding SRS transmission, then the same time mask applies as shown in Figure 6.3.3.7-1. + +### 6.3.3.8 Transmit power time mask for consecutive slot or long subplot transmission and short subplot transmission boundaries + +The transmit power time mask for consecutive slot or long subplot transmission and short subplot transmission boundaries defines the transient periods allowed between such transmissions. + +![Figure 6.3.3.8-1: Consecutive slot or long subslot transmission and short subslot transmission time mask. The diagram shows three subslots: Long subslot N, Short subslot N+1, and Long subslot N+2. Transient periods of 5μs are shown at the boundaries between Long subslot N and Short subslot N+1, and between Short subslot N+1 and Long subslot N+2. Arrows indicate the 'End of power' and 'Start of power' at these boundaries.](475c496c4cd20198211aeaa241af7279_img.jpg) + +Figure 6.3.3.8-1: Consecutive slot or long subslot transmission and short subslot transmission time mask. The diagram shows three subslots: Long subslot N, Short subslot N+1, and Long subslot N+2. Transient periods of 5μs are shown at the boundaries between Long subslot N and Short subslot N+1, and between Short subslot N+1 and Long subslot N+2. Arrows indicate the 'End of power' and 'Start of power' at these boundaries. + +Figure 6.3.3.8-1: Consecutive slot or long subslot transmission and short subslot transmission time mask + +6.3.3.9 Transmit power time mask for consecutive short subslot transmissions boundaries + +The transmit power time mask for consecutive short subslot transmission boundaries defines the transient periods allowed between short subslot transmissions. + +The transient period shall be equally shared as shown on Figure 6.3.3.9-2. + +Figure 6.3.3.9-1: Void + +![Figure 6.3.3.9-2: Consecutive short subslot transmissions time mask where DMRS is not the first symbol in the adjacent short subslot transmission. The diagram shows two short subslots, Short subslot N and Short subslot N+1, separated by a gap. A 5μs transient period is shown at the boundary between the two subslots, with arrows indicating the 'End of power' and 'Start of power'.](4e99a3206cef1efe25cda57727183aa6_img.jpg) + +Figure 6.3.3.9-2: Consecutive short subslot transmissions time mask where DMRS is not the first symbol in the adjacent short subslot transmission. The diagram shows two short subslots, Short subslot N and Short subslot N+1, separated by a gap. A 5μs transient period is shown at the boundary between the two subslots, with arrows indicating the 'End of power' and 'Start of power'. + +Figure 6.3.3.9-2: Consecutive short subslot transmissions time mask where DMRS is not the first symbol in the adjacent short subslot transmission + +![Figure 6.3.3.9-3: Consecutive short subslot (1 symbol gap) time mask for the case when transient period is required on both sides of the symbol and when 120 kHz SCS is used in FR2. The diagram shows two short subslots separated by a 1-symbol gap. Transient periods of 5μs are shown on both sides of the gap. Arrows indicate the 'End of OFF power requirement', 'ON power requirement', and 'Start of OFF power requirement'. A total duration of 8.93μs is indicated for the gap and transient periods.](6d7be4b2b402e079f97685869580c864_img.jpg) + +Figure 6.3.3.9-3: Consecutive short subslot (1 symbol gap) time mask for the case when transient period is required on both sides of the symbol and when 120 kHz SCS is used in FR2. The diagram shows two short subslots separated by a 1-symbol gap. Transient periods of 5μs are shown on both sides of the gap. Arrows indicate the 'End of OFF power requirement', 'ON power requirement', and 'Start of OFF power requirement'. A total duration of 8.93μs is indicated for the gap and transient periods. + +Figure 6.3.3.9-3: Consecutive short subslot (1 symbol gap) time mask for the case when transient period is required on both sides of the symbol and when 120 kHz SCS is used in FR2 + +## 6.3.4 Power control + +### 6.3.4.1 General + +The requirements on power control accuracy apply under normal conditions and are defined as a directional requirement. The requirements are verified in beam locked mode on beam peak direction. + +### 6.3.4.2 Absolute power tolerance + +The absolute power tolerance is the ability of the UE transmitter to set its initial output power to a specific value for the first sub-frame (1 ms) at the start of a contiguous transmission or non-contiguous transmission with a transmission gap larger than 20 ms. The tolerance includes the channel estimation error RSRP estimate. + +The minimum requirements specified in Table 6.3.4.2-1 apply in the power range bounded by the minimum output power as specified in sub-clause 6.3.1 ( $P_{min}$ ) and the maximum output power as specified in sub-clause 6.2.1 as minimum peak EIRP ( $P_{max}$ ). The intermediate power point $P_{int}$ is defined in table 6.3.4.2-2 + +**Table 6.3.4.2-1: Absolute power tolerance** + +| Power Range | Tolerance | +|-------------------------------|---------------| +| $P_{int} \geq P \geq P_{min}$ | $\pm 14.0$ dB | +| $P_{max} \geq P > P_{int}$ | $\pm 12.0$ dB | + +**Table 6.3.4.2-2: Intermediate power point** + +| Power Parameter | Value | +|-----------------|---------------------| +| $P_{int}$ | $P_{max} - 12.0$ dB | + +### 6.3.4.3 Relative power tolerance + +The relative power tolerance is the ability of the UE 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. + +The minimum requirements specified in Table 6.3.4.3-1 apply when the power of the target and reference sub-frames are within the power range bounded by the minimum output power as defined in sub-clause 6.3.1 and $P_{int}$ as defined in sub-clause 6.3.4.2. The minimum requirements specified in Table 6.3.4.3-2 apply when the power of the target and reference sub-frames are within the power range bounded by $P_{int}$ as defined in sub-clause 6.3.4.2 and the measured $P_{UMAX}$ as defined in sub-clause 6.2.4. + +For a test pattern that is either a monotonically increasing or monotonically decreasing power sweep over the range specified for Tables 6.3.4.3-1 and 6.3.4.3-2, 3 exceptions are allowed for each of the test patterns. For these exceptions, the power tolerance limit is a maximum of $\pm 11.0$ dB. + +**Table 6.3.4.3-1: Relative power tolerance, $P_{int} \geq P \geq P_{min}$** + +| Power step $\Delta P$ (Up or down) (dB) | All combinations of PUSCH and PUCCH, PUSCH/PUCCH and SRS transitions between sub-frames, PRACH (dB) | +|-----------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------| +| $\Delta P < 2$ | $\pm 5.0$ | +| $2 \leq \Delta P < 3$ | $\pm 6.0$ | +| $3 \leq \Delta P < 4$ | $\pm 7.0$ | +| $4 \leq \Delta P < 10$ | $\pm 8.0$ | +| $10 \leq \Delta P < 15$ | $\pm 10.0$ | +| $15 \leq \Delta P$ | $\pm 11.0$ | +| NOTE: The requirements apply with ue-BeamLockFunction enabled. | | + +**Table 6.3.4.3-2: Relative power tolerance, $P_{\text{UMAX}} \geq P > P_{\text{int}}$** + +| Power step $\Delta P$ (Up or down) (dB) | All combinations of PUSCH and PUCCH, PUSCH/PUCCH and SRS transitions between sub-frames, PRACH (dB) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------| +| $\Delta P < 2$ | $\pm 3.0$ | +| $2 \leq \Delta P < 3$ | $\pm 4.0$ | +| $3 \leq \Delta P < 4$ | $\pm 5.0$ | +| $4 \leq \Delta P < 10$ | $\pm 6.0$ | +| $10 \leq \Delta P < 15$ | $\pm 8.0$ | +| $15 \leq \Delta P$ | $\pm 9.0$ | +| NOTE 1: The requirements apply with ue-BeamLockFunction enabled.
NOTE 2: For PUSCH to PUSCH transitions with the allocated resource blocks fixed in frequency and no transmission gaps other than those generated by downlink subframes, guard periods: for a power step $\Delta P = 1$ dB, the relative power tolerance for transmission is $\pm 1.0$ dB. | | + +### 6.3.4.4 Aggregate power tolerance + +The aggregate power control tolerance is the ability of the UE transmitter to maintain its power in a sub-frame (1 ms) during non-contiguous transmissions within 21ms in response to 0 dB TPC commands with respect to the first UE transmission and all other power control parameters as specified in 38.213 kept constant. + +The minimum requirements specified in Table 6.3.4.4-1 apply when the power of the target and reference sub-frames are within the power range bounded by the minimum output power as defined in sub-clause 6.3.1 and $P_{\text{int}}$ as defined in sub-clause 6.3.4.2. The minimum requirements specified in Table 6.3.4.4-2 apply when the power of the target and reference sub-frames are within the power range bounded by $P_{\text{int}}$ as defined in sub-clause 6.3.4.2 and the maximum output power as specified in sub-clause 6.2.1. + +**Table 6.3.4.4-1: Aggregate power tolerance, $P_{\text{int}} \geq P \geq P_{\text{min}}$** + +| TPC command | UL channel | Aggregate power tolerance within 21 ms | +|-------------|------------|----------------------------------------| +| 0 dB | PUCCH | $\pm 5.5$ dB | +| 0 dB | PUSCH | $\pm 5.5$ dB | + +**Table 6.3.4.4-2: Aggregate power tolerance, $P_{\text{max}} \geq P > P_{\text{int}}$** + +| TPC command | UL channel | Aggregate power tolerance within 21 ms | +|-------------|------------|----------------------------------------| +| 0 dB | PUCCH | $\pm 3.5$ dB | +| 0 dB | PUSCH | $\pm 3.5$ dB | + +## 6.3A Output power dynamics for CA + +### 6.3A.1 Minimum output power for CA + +**Table 6.3A.1-1: Void** + +#### 6.3A.1.0 General + +For intra-band contiguous and non-contiguous carrier aggregation, the minimum controlled output power of the UE is defined as the transmit power of the UE per component carrier, i.e., EIRP in the channel bandwidth of each component carrier for all transmit bandwidth configurations (resource blocks), when the power on both component carriers are set to a minimum value. + +The minimum output power is defined as the mean power in at least one sub frame (1ms). + +### 6.3A.1.1 Minimum output power for power class 1 + +For intra-band contiguous and non-contiguous carrier aggregation, the minimum output power shall not exceed the values specified in Table 6.3A.1.1-1 for each operating band supported. The minimum power is verified in beam locked mode with the test metric of EIRP (Link=TX beam peak direction, Meas=Link angle). + +**Table 6.3A.1.1-1: Minimum output power for power class 1** + +| Operating band | Channel bandwidth (MHz) | Minimum output power (dBm) | Measurement bandwidth (MHz) | +|------------------------------|-------------------------|----------------------------|-----------------------------| +| n257, n258, n260, n261, n262 | 50 | 4 | 47.58 | +| | 100 | 4 | 95.16 | +| | 200 | 4 | 190.20 | +| | 400 | 4 | 380.28 | +| n263 | 100 | 4 | 95.16 | +| | 400 | 4 | 381.12 | +| | 800 | 4 | 715.20 | +| | 1600 | 4 | 1429.44 | +| | 2000 | 4 | 1705.92 | + +For inter-band carrier aggregation with uplink assigned to two NR bands, and each UL band is configured with a single CC, the minimum output power is defined per carrier and is specified in clause 6.3.1.1. + +### 6.3A.1.2 Minimum output power for power class 2, 3, and 4 + +For intra-band contiguous and non-contiguous carrier aggregation, the minimum output power shall not exceed the values specified in Table 6.3A.1.2-1 for each operating band supported. The minimum power is verified in beam locked mode with the test metric of EIRP (Link=TX beam peak direction, Meas=Link angle). + +**Table 6.3A.1.2-1: Minimum output power for CA for power class 2, 3, and 4** + +| Operating band | Channel bandwidth (MHz) | Minimum output power (dBm) | Measurement bandwidth (MHz) | +|------------------------------------------------|-------------------------|----------------------------|-----------------------------| +| n257, n258, n259, n260, n261, n262 | 50 | -13 | 47.58 | +| | 100 | -13 | 95.16 | +| | 200 | -13 | 190.20 | +| | 400 | -13 | 380.28 | +| n263 | 100 | -13 | 95.16 | +| | 400 | -13 | 381.12 | +| | 800 | -13 | 715.20 | +| | 1600 | -13 | 1429.44 | +| | 2000 | -13 | 1705.92 | +| NOTE 1: n260 is not applied for power class 2. | | | | +| NOTE 2: n259 is not applied for power class 4. | | | | + +For inter-band carrier aggregation with uplink assigned to two NR bands, and each UL band is configured with a single CC, the minimum output power is defined per carrier and is specified in clause 6.3.1.2. + +### 6.3A.1.3 Minimum output power for power class 5 and 6 + +For intra-band contiguous and non-contiguous carrier aggregation, the minimum output power shall not exceed the values specified in Table 6.3A.1.3-1 for each operating band supported. The minimum power is verified in beam locked mode with the test metric of EIRP (Link=TX beam peak direction, Meas=Link angle). + +**Table 6.3A.1.3-1: Minimum output power for CA for power class 5 and 6** + +| Operating band | Channel bandwidth (MHz) | Minimum output power (dBm) | Measurement bandwidth (MHz) | +|------------------------|-------------------------|----------------------------|-----------------------------| +| n257, n258, n259, n261 | 50 | -6 | 47.52 | +| | 100 | -6 | 95.04 | +| | 200 | -6 | 190.08 | +| | 400 | -6 | 380.16 | + +NOTE 1: n261 is not applied for power class 5. +NOTE 2: n259 is not applied for power class 6. + +For inter-band carrier aggregation with uplink assigned to two NR bands, and each UL band is configured with a single CC, the minimum output power is defined per carrier and is specified in clause 6.3.1.3. + +### 6.3A.2 Transmit OFF power for CA + +For intra-band contiguous and non-contiguous carrier aggregation, the transmit OFF power is defined as the TRP in the channel bandwidth per component carrier when the transmitter is OFF. The transmitter is considered OFF when the UE is not allowed to transmit on any of its ports. + +The transmit OFF power shall not exceed the values specified in Table 6.3A.2-1 and Table 6.3A.2-2 for each operating band supported. + +**Table 6.3A.2-1: Transmit OFF power for CA for FR2-1** + +| Operating band | Channel bandwidth / Transmit OFF power (dBm) / measurement bandwidth | | | | +|------------------------------------|----------------------------------------------------------------------|-----------|------------|------------| +| | 50 MHz | 100 MHz | 200 MHz | 400 MHz | +| n257, n258, n259, n260, n261, n262 | -35 | -35 | -35 | -35 | +| | 47.58 MHz | 95.16 MHz | 190.20 MHz | 380.28 MHz | + +**Table 6.3A.2-2: Transmit OFF power for CA for FR2-2** + +| Operating band | Channel bandwidth / Transmit OFF power (dBm) / measurement bandwidth | | | | | +|----------------|----------------------------------------------------------------------|------------|---------|----------|----------| +| | 100 MHz | 400 MHz | 800 MHz | 1600 MHz | 2000 MHz | +| n263 | -35 | -35 | -35 | -35 | -35 | +| | 95.16 MHz | 381.12 MHz | 715.20 | 1429.44 | 1705.92 | + +For inter-band carrier aggregation with uplink assigned to two NR bands, and each UL band is configured with a single CC, the transmit OFF power specified in clause 6.3.2.1 is applicable for each CC when the transmitter is OFF on all CCs. The transmitter is considered to be OFF when the UE is not allowed to transmit on any of its ports. + +### 6.3A.3 Transmit ON/OFF time mask for CA + +For intra-band contiguous and non-contiguous UL carrier aggregation, the general output power ON/OFF time mask specified in clause 6.3.3.2 is applicable for each component carrier during the ON power period and the transient + +periods. The OFF period as specified in clause 6.3.3.2 shall only be applicable for each component carrier when all the component carriers are OFF. + +For inter-band carrier aggregation with uplink assigned to two NR bands, and each UL band is configured with a single CC, the general output power ON/OFF time mask specified in clause 6.3.3.1 is applicable for each CC during the ON power period and the transient periods. The OFF period is specified in clause 6.3.3.1 for each CC separately when all the CCs are OFF. + +## 6.3A.4 Power control for CA + +### 6.3A.4.1 General + +The requirements in this clause apply to a UE when it has at least one of UL or DL configured for CA operation. The requirements on power control accuracy in CA operation apply under normal conditions and are defined as a directional requirement. The requirements are verified in beam locked mode on beam peak direction. The requirements apply for one single PUCCH, PUSCH or SRS transmission of contiguous PRB allocation per configured UL CC with power setting in accordance with Clause 7.1 of [10] + +### 6.3A.4.2 Absolute power tolerance + +For intra-band contiguous and non-contiguous UL carrier aggregation, the absolute power tolerance is the ability of the UE transmitter to set its initial output power to a specific value for the first sub-frame at the start of a contiguous transmission or non-contiguous transmission with a transmission gap on each active component carriers larger than 20 ms. For SRS switching, the absolute power tolerance is the ability of the UE transmitter to set its initial output power to a specific value for the first sub-frame at the start of a contiguous transmission or non-contiguous transmission with a transmission gap on component carriers (to which SRS switching occurs) larger than 20 ms. The requirement can be tested by time aligning any transmission gaps on the component carriers. For intra-band contiguous CA, the absolute power control tolerance per configured UL CC is given in Tables 6.3.4.2-1 and 6.3.4.2-2. + +### 6.3A.4.3 Relative power tolerance + +For intra-band contiguous and non-contiguous UL carrier aggregation, the relative power tolerance is the ability of the UE transmitter to set its output power in a target sub-frame relative to the power of the most recently transmitted reference sub-frame if the transmission gap between these sub-frames is less than or equal to 20ms. + +For intra-band contiguous CA, the requirements apply when the power of the target and reference sub-frames on each component carrier exceed the minimum output power as defined in clause 6.3A.1 and the total power is limited by $P_{UMAX}$ as defined in clause 6.2A.4. For the purpose of these requirements, the power in each component carrier is specified over only the transmitted resource blocks. The UE shall meet the requirements in tables 6.3.4.3-1 and 6.3.4.3-2 for transmission on each assigned component carrier, when the average PSDs over each CC are aligned with each other in the reference sub-frame. The requirements apply per component carrier to: + +- All possible combinations of PUSCH and PUCCH transitions +- SRS and PUSCH/PUCCH transitions, only with simultaneous SRS of constant SRS bandwidth allocated in the target and reference subframes +- RACH, primary component carrier + +When applicable, the power step $\Delta P$ between the reference and target subframes shall be set by a TPC command and/or an uplink scheduling grant transmitted by means of an appropriate DCI Format. + +### 6.3A.4.4 Aggregate power tolerance + +For intra-band contiguous and non-contiguous UL carrier aggregation, the aggregate power control tolerance is the ability of the UE transmitter to maintain its power during non-contiguous transmissions within 21 ms in response to 0 dB TPC commands with respect to the first UE transmission and all other power control parameters as specified in [10] kept constant. + +For intra-band contiguous CA, the aggregate power tolerance per CC is given in Tables 6.3.4.4.1-1 and 6.3.4.4.1-2, with simultaneous PUSCH configured. The average PSDs over each assigned CC shall be aligned before the start of the test. The requirement can be tested with the transmission gaps time aligned between component carriers. + +## 6.3D Output power dynamics for UL MIMO + +### 6.3D.0 General + +The requirements in subclause 6.3D shall be met with configurations specified in sub-clause 6.2D.1.x, where 'x' depends on power class. Unless otherwise specified, the requirements shall be verified in beam locked mode with the test metric of EIRP (Link=TX beam peak direction, Meas=Link angle). + +### 6.3D.1 Minimum output power for UL MIMO + +#### 6.3D.1.0 General + +The minimum output power is defined as the mean power in at least one sub frame (1ms). The minimum controlled output power is defined as the EIRP, i.e. the sum of the power in the channel bandwidth for all transmit bandwidth configurations (resource blocks), when the UE power is set to a minimum value. + +#### 6.3D.1.1 Minimum output power for UL MIMO for power class 1 + +For UE supporting UL MIMO, the minimum output power shall not exceed the sum of the values specified in Table 6.3.1.1-1 and the quantity $10 \cdot \log_{10}(\text{Number of Layers})$ . + +#### 6.3D.1.2 Minimum output power for UL MIMO for power class 2, 3 and 4 + +minimum output power shall not exceed the sum of the values specified in Table 6.3.1.2-1 and the quantity $10 \cdot \log_{10}(\text{Number of Layers})$ . + +#### 6.3D.1.3 Minimum output power for UL MIMO for power class 5 and 6 + +For UE supporting UL MIMO, the minimum controlled output power is defined as the EIRP, i.e. the sum of the power in the channel bandwidth for all transmit bandwidth configurations (resource blocks), when the UE power is set to a minimum value. The minimum output power shall not exceed the values specified in Table 6.3.1.3-1. The minimum power is verified in beam locked mode with the test metric of EIRP (Link=TX beam peak direction, Meas=Link angle). + +### 6.3D.2 Transmit OFF power for UL MIMO + +For UE supporting UL MIMO, the transmit OFF power is defined as the TRP in the channel bandwidth when the transmitter is OFF. The transmitter is considered OFF when the UE is not allowed to transmit on any of its ports. During DTX and measurements gaps, the transmitter is not considered OFF. The minimum output power shall not exceed the values specified in Table 6.3.2-1. The requirement is verified with the test metric of TRP (Link=TX beam peak direction, Meas=TRP grid). + +### 6.3D.3 Transmit ON/OFF time mask for UL MIMO + +For UE supporting UL MIMO, the ON/OFF time mask requirements in clause 6.3.3 apply. + +## 6.4 Transmit signal quality + +### 6.4.1 Frequency Error + +The UE basic measurement interval of modulated carrier frequency is 1 UL slot. The mean value of basic measurements of UE modulated carrier frequency shall be accurate to within $\pm 0.1$ PPM observed over a period of 1 msec of cumulated measurement intervals compared to the carrier frequency received from the NR gNB. + +The frequency error is defined as a directional requirement. The requirement is verified in beam locked mode with the test metric of Frequency (Link=TX beam peak direction, Meas=Link angle). + +### 6.4.2 Transmit modulation quality + +#### 6.4.2.0 General + +Transmit modulation quality defines the modulation quality for expected in-channel RF transmissions from the UE. The transmit modulation quality is specified in terms of: + +- Error Vector Magnitude (EVM) for the allocated resource blocks (RBs) +- EVM equalizer spectrum flatness derived from the equalizer coefficients generated by the EVM measurement process +- Carrier leakage +- In-band emissions for the non-allocated RB + +All the parameters defined in clause 6.4.2 are defined using the measurement methodology specified in Annex F. + +All the requirements in 6.4.2 are defined as directional requirement. The requirements are verified in beam locked mode on beam peak direction, with parameter *maxRank* (as defined in TS 38.331 [13]) set to 1. The requirements are applicable to UL transmission from each configurable antenna port (as defined in TS 38.331 [13]) of UE, enabled one at a time. + +In case the parameter 3300 or 3301 is reported from UE via the parameter *txDirectCurrentLocation* in *UplinkTxDirectCurrentList* IE (as defined in TS 38.331 [13]), carrier leakage measurement requirement in clause 6.4.2.2 and 6.4.2.3 shall be waived, and the RF correction with regard to the carrier leakage and IQ image shall be omitted during the calculation of transmit modulation quality. + +#### 6.4.2.1 Error vector magnitude + +The Error Vector Magnitude is a measure of the difference between the reference waveform and the measured waveform. This difference is called the error vector. Before calculating the 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 EVM. + +The measured waveform is further equalised using the channel estimates subjected to the EVM equaliser spectrum flatness requirement specified in sub-clauses 6.4.2.4 and 6.4.2.5. For DFT-s-OFDM waveforms, the 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 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 basic EVM measurement interval in the time domain is one preamble sequence for the PRACH and one slot for PUCCH and PUSCH in the time domain. The EVM measurement interval is reduced by any symbols that contains an allowable power transient in the measurement interval as defined in clause 6.3.3. + +The RMS average of the basic EVM measurements over 10 subframes for the average EVM case, and over 60 subframes for the reference signal EVM case, for the different modulation schemes shall not exceed the values specified in Table 6.4.2.1-1 for the parameters defined in Table 6.4.2.1-2 or 6.4.2.1-3, depending on UE power class. For EVM evaluation purposes, all 13 PRACH preamble formats and all 5 PUCCH formats are considered to have the same EVM requirement as QPSK modulated. + +The requirement is verified with the test metric of EVM (Link=TX beam peak direction, Meas=Link angle). + +**Table 6.4.2.1-1: Minimum requirements for error vector magnitude** + +| Parameter | Unit | Average EVM level | Reference signal EVM level | +|----------------------|------|-------------------|----------------------------| +| Pi/2 BPSK | % | 30.0 | 30.0 | +| QPSK | % | 17.5 | 17.5 | +| 16 QAM | % | 12.5 | 12.5 | +| 64 QAM | % | 8.0 | 8.0 | +| 256 QAM 1 | % | 3.5 | 3.5 | + +NOTE 1: Refer to clause 6.1 for 256 QAM applicability. + +**Table 6.4.2.1-2: Parameters for Error Vector Magnitude for power class 1 in FR2-1** + +| Parameter | Unit | Level | +|------------------------|------|-------------------| +| UE EIRP | dBm | $\geq 4$ | +| UE EIRP for UL 16 QAM | dBm | $\geq 7$ | +| UE EIRP for UL 64 QAM | dBm | $\geq 11$ | +| UE EIRP for UL 256 QAM | dBm | $\geq 18$ | +| Operating conditions | | Normal conditions | + +**Table 6.4.2.1-2a: Parameters for Error Vector Magnitude for power class 1 in FR2-2** + +| Parameter | Unit | Level | | | | | +|-----------------------|------|-------------------|----------|-----------|-----------|-----------| +| | | 100 MHz | 400 MHz | 800 MHz | 1600 MHz | 2000 MHz | +| UE EIRP | dBm | $\geq 4$ | $\geq 2$ | $\geq 5$ | $\geq 8$ | $\geq 9$ | +| UE EIRP for UL 16 QAM | dBm | $\geq 7$ | $\geq 5$ | $\geq 8$ | $\geq 11$ | $\geq 12$ | +| UE EIRP for UL 64 QAM | dBm | $\geq 11$ | $\geq 9$ | $\geq 12$ | $\geq 15$ | $\geq 16$ | +| Operating conditions | | Normal Conditions | | | | | + +NOTE 1: PTRS is configured for 16 QAM and 64 QAM + +**Table 6.4.2.1-3: Parameters for Error Vector Magnitude for power class 2, 3, 4 and 7 in FR2-1** + +| Parameter | Unit | Level | +|-------------------------------------|------|-------------------| +| UE EIRP | dBm | $\geq -13$ | +| UE EIRP for UL 16 QAM | dBm | $\geq -10$ | +| UE EIRP for UL 64 QAM | dBm | $\geq -6$ | +| UE EIRP for UL 256 QAM 1 | dBm | $\geq 1$ | +| Operating conditions | | Normal conditions | + +NOTE 1: Refer to clause 6.1 for 256 QAM applicability. + +**Table 6.4.2.1-3a: Parameters for Error Vector Magnitude for power class 3 in FR2-2** + +| Parameter | Unit | Level | | | | | +|-----------------------|------|-------------------|------------|-----------|-----------|-----------| +| | | 100 MHz | 400 MHz | 800 MHz | 1600 MHz | 2000 MHz | +| UE EIRP | dBm | $\geq -13$ | $\geq -11$ | $\geq -8$ | $\geq -5$ | $\geq -4$ | +| UE EIRP for UL 16 QAM | dBm | $\geq -10$ | $\geq -8$ | $\geq -5$ | $\geq -2$ | $\geq -1$ | +| UE EIRP for UL 64 QAM | dBm | $\geq -6$ | $\geq -4$ | $\geq -1$ | $\geq 2$ | $\geq 3$ | +| Operating conditions | | Normal Conditions | | | | | + +NOTE 1: PTRS is configured for 16 QAM and 64 QAM + +**Table 6.4.2.1-3b: Parameters for Error Vector Magnitude for power class 2 in FR2-2** + +| Parameter | Unit | Level | | | | | +|-----------------------|------|-------------------|------------|-----------|-----------|-----------| +| | | 100 MHz | 400 MHz | 800 MHz | 1600 MHz | 2000 MHz | +| UE EIRP | dBm | $\geq -13$ | $\geq -11$ | $\geq -8$ | $\geq -5$ | $\geq -4$ | +| UE EIRP for UL 16 QAM | dBm | $\geq -10$ | $\geq -8$ | $\geq -5$ | $\geq -2$ | $\geq -1$ | +| UE EIRP for UL 64 QAM | dBm | $\geq -6$ | $\geq -4$ | $\geq -1$ | $\geq 2$ | $\geq 3$ | +| Operating conditions | | Normal Conditions | | | | | + +NOTE 1: PTRS is configured for 16 QAM and 64 QAM + +**Table 6.4.2.1-4: Parameters for Error Vector Magnitude for power class 5 in FR2-1** + +| Parameter | Unit | Level | +|------------------------|------|-------------------| +| UE EIRP | dBm | $\geq -6$ | +| UE EIRP for UL 16 QAM | dBm | $\geq -3$ | +| UE EIRP for UL 64 QAM | dBm | $\geq 1$ | +| UE EIRP for UL 256 QAM | dBm | $\geq 8$ | +| Operating conditions | | Normal conditions | + +## 6.4.2.2 Carrier leakage + +### 6.4.2.2.1 General + +Carrier leakage is an additive sinusoid waveform. The carrier leakage requirement is defined for each component carrier. The measurement interval is one slot in the time domain. The relative carrier leakage power is a power ratio of the additive sinusoid waveform to the power in the modulated waveform. + +The requirement is verified with the test metric of Carrier Leakage (Link=TX beam peak direction, Meas=Link angle). + +### 6.4.2.2.2 Carrier leakage for power class 1 + +When carrier leakage is contained inside the spectrum confined within the configured UL and DL CCs, the relative carrier leakage power shall not exceed the values specified in Table 6.4.2.2.2-1 and Table 6.4.2.2.2-2 for power class 1 UEs. + +**Table 6.4.2.2.2-1: Minimum requirements for relative carrier leakage power for power class 1 in FR2-1** + +| Parameters | Relative Limit (dBc) | +|---------------------------------|----------------------| +| EIRP > 17 dBm | -25 | +| 4 dBm $\leq$ EIRP $\leq$ 17 dBm | -20 | + +**Table 6.4.2.2.2-2: Minimum requirements for relative carrier leakage power for power class 1 in FR2-2** + +| Parameters | Relative Limit (dBc) | +|-------------------------------------|----------------------| +| EIRP > 13.4 dBm | -25 | +| 0.4 dBm $\leq$ EIRP $\leq$ 13.4 dBm | -20 | + +### 6.4.2.2.3 Carrier leakage for power class 2 + +When carrier leakage is contained inside the spectrum occupied by the configured UL CCs and DL CCs, the relative carrier leakage power shall not exceed the values specified in Table 6.4.2.2.3-1 and Table 6.4.2.2.3-2 for power class 2. + +**Table 6.4.2.2.3-1: Minimum requirements for relative carrier leakage power for power class 2 in FR2-1** + +| Parameters | Relative Limit (dBc) | +|----------------------------------|----------------------| +| EIRP > 6 dBm | -25 | +| -13 dBm $\leq$ EIRP $\leq$ 6 dBm | -20 | + +**Table 6.4.2.2.3-2: Minimum requirements for relative carrier leakage power for power class 2 in FR2-2** + +| Parameters | Relative Limit (dBc) | +|--------------------------------------|----------------------| +| EIRP > 5.8 dBm | -25 | +| -13.2 dBm $\leq$ EIRP $\leq$ 5.8 dBm | -20 | + +#### 6.4.2.2.4 Carrier leakage for power class 3 + +When carrier leakage is contained inside the spectrum occupied by the configured UL CCs and DL CCs, the relative carrier leakage power shall not exceed the values specified in Table 6.4.2.2.4-1 and Table 6.4.2.2.4-2 for power class 3 UEs. + +**Table 6.4.2.2.4-1: Minimum requirements for relative carrier leakage power for power class 3 in FR2-1** + +| Parameters | Relative Limit (dBc) | +|----------------------------------|----------------------| +| EIRP > 0 dBm | -25 | +| -13 dBm $\leq$ EIRP $\leq$ 0 dBm | -20 | + +**Table 6.4.2.2.4-2: Minimum requirements for relative carrier leakage power for power class 3 in FR2-2** + +| Parameters | Relative Limit (dBc) | +|---------------------------------------|----------------------| +| EIRP > -1.9 dBm | -25 | +| -14.9 dBm $\leq$ EIRP $\leq$ -1.9 dBm | -20 | + +#### 6.4.2.2.5 Carrier leakage for power class 4 + +When carrier leakage is contained inside the spectrum occupied by the configured UL CCs and DL CCs, the relative carrier leakage power shall not exceed the values specified in Table 6.4.2.2.5-1 for power class 4. + +**Table 6.4.2.2.5-1: Minimum requirements for relative carrier leakage power for power class 4 in FR2-1** + +| Parameters | Relative Limit (dBc) | +|-----------------------------------|----------------------| +| EIRP > 11 dBm | -25 | +| -13 dBm $\leq$ EIRP $\leq$ 11 dBm | -20 | + +#### 6.4.2.2.6 Carrier leakage for power class 5 + +When carrier leakage is contained inside the spectrum occupied by the configured UL CCs and DL CCs, the relative carrier leakage power shall not exceed the values specified in Table 6.4.2.2.6-1 for power class 5. + +**Table 6.4.2.2.6-1: Minimum requirements for relative carrier leakage power for power class 5 in FR2-1** + +| Parameters | Relative Limit (dBc) | +|---------------------------------|----------------------| +| EIRP > 7 dBm | -25 | +| -6 dBm $\leq$ EIRP $\leq$ 7 dBm | -20 | + +#### 6.4.2.2.7 Carrier leakage for power class 6 + +For power class 6, the carrier leakage requirement specified in clause 6.4.2.2.6 for power class 5 applies. + +#### 6.4.2.2.8 Carrier leakage for power class 7 + +When carrier leakage is contained inside the spectrum occupied by the configured UL CCs and DL CCs, the relative carrier leakage power specified in subclause 6.4.2.2.4 applies. + +### 6.4.2.3 In-band emissions + +#### 6.4.2.3.1 General + +The in-band emission is defined as the average across 12 sub-carriers and as a function of the RB offset from the edge of the allocated UL transmission bandwidth. The in-band emission is measured as the ratio of the UE output power in a non-allocated RB to the UE output power in an allocated RB. The IBE requirement does not apply if UE declares support for *mpr-PowerBoost-FR2-r16*, UL transmission is QPSK, $MPR_{fc} = 0$ and when NS\_200 applies, and the network configures the UE to operate with *mpr-PowerBoost-FR2-r16*. + +The basic in-band emissions measurement interval is identical to that of the EVM test. + +The requirement is verified with the test metric of In-band emission (Link=TX beam peak direction, Meas=Link angle). + +#### 6.4.2.3.2 In-band emissions for power class 1 + +The average of the in-band emission measurement over 10 sub-frames shall not exceed the values specified in Table 6.4.2.3.2-1 for power class 1 UEs. + +**Table 6.4.2.3.2-1: Requirements for in-band emissions for power class 1** + +| Parameter description | Unit | Limit (NOTE 1) | | | Applicable Frequencies | +|------------------------|------|----------------|-------------------------------|-----------------------------------|--------------------------------| +| General | dB | | | | Any non-allocated (NOTE 2) | +| | | | Output power for FR2-1 | Output Power for FR2-2 | | +| IQ Image | dB | -25 | > 27 dBm | > 23.4 dBm | Image frequencies (NOTES 2, 3) | +| | | -20 | ≤ 27 dBm | ≤ 23.4 dBm | | +| Carrier leakage | dBc | -25 | > 17 dBm | > 13.4 dBm | Carrier frequency (NOTES 4, 5) | +| | | -20 | 4 dBm ≤ Output power ≤ 17 dBm | 0.4 dBm ≤ Output power ≤ 13.4 dBm | | + +NOTE 1: An in-band emissions combined limit is evaluated in each non-allocated RB. For each such RB, the minimum requirement is calculated as the higher of (- 25 dB) and the power sum of all limit values (General, IQ Image or Carrier leakage) that apply. is defined in NOTE 10. + +NOTE 2: The measurement bandwidth is 1 RB and the limit is expressed as a ratio of measured power in one non-allocated RB to the measured average power per allocated RB, where the averaging is done across all allocated RBs. For pi/2 BPSK with Spectrum Shaping, the limit is expressed as a ratio of measured power in one non-allocated RB to the measured power in the allocated RB with highest PSD + +NOTE 3: The applicable frequencies for this limit are those that are enclosed in the reflection of the allocated bandwidth, based on symmetry with respect to the carrier frequency, but excluding any allocated RBs. + +NOTE 4: The measurement bandwidth is 1 RB and the limit is expressed as a ratio of measured power in one non-allocated RB to the measured total power in all allocated RBs. + +NOTE 5: The applicable frequencies for this limit depend on the parameter *txDirectCurrentLocation* in *UplinkTxDirectCurrent* IE, and are those that are enclosed in the RBs containing the DC frequency but excluding any allocated RB. + +NOTE 6: $L_{CRB}$ is the Transmission Bandwidth (see Clause 5.3). + +NOTE 7: $N_{RB}$ is the Transmission Bandwidth Configuration (see Clause 5.3). + +NOTE 8: EVM is the limit for the modulation format used in the allocated RBs. + +NOTE 9: $\Delta_{RB}$ is the starting frequency offset between the allocated RB and the measured non-allocated RB (e.g. $\Delta_{RB} = 1$ or $\Delta_{RB} = -1$ for the first adjacent RB outside of the allocated bandwidth). + +NOTE 10: is an average of the transmitted power over 10 sub-frames normalized by the number of allocated RBs, measured in dBm. + +NOTE 11: All powers are EIRP in beam peak direction. + +#### 6.4.2.3.3 In-band emissions for power class 2 + +The average of the in-band emission measurement over 10 sub-frames shall not exceed the values specified in Table 6.4.2.3.3-1 for power class 2. + +**Table 6.4.2.3.3-1: Requirements for in-band emissions for power class 2** + +| Parameter description | Unit | Limit (NOTE 1) | | | Applicable Frequencies | +|------------------------|------|----------------|--------------------------------|------------------------------------|---------------------------------------------------------------------------------------------------| +| | | | Output power for FR2-1 | Output Power for FR2-2 | | +| General | dB | | | | Any non-allocated RB in allocated component carrier and not allocated component carriers (NOTE 2) | +| IQ Image | dB | -25 | Output power > 16 dBm | Output power > 15.8 dBm | Image frequencies (NOTES 2, 3) | +| | | -20 | Output power ≤ 16 dBm | Output power ≤ 15.8 dBm | | +| Carrier leakage | dBc | -25 | Output power > 6 dBm | Output power > 5.8 dBm | Carrier frequency (NOTES 4, 5) | +| | | -20 | -13 dBm ≤ Output power ≤ 6 dBm | -13.2 dBm ≤ Output power ≤ 5.8 dBm | | + +NOTE 1: An in-band emissions combined limit is evaluated in each non-allocated RB. For each such RB, the minimum requirement is calculated as the higher of (- 25 dB) and the power sum of all limit values (General, IQ Image or Carrier leakage) that apply. is defined in NOTE 9. + +NOTE 2: The measurement bandwidth is 1 RB and the limit is expressed as a ratio of measured power in one non-allocated RB to the measured average power per allocated RB, where the averaging is done across all allocated RBs. For Pi/2 BPSK with Spectrum Shaping, the limit is expressed as a ratio of measured power in one non-allocated RB to the measured power in the allocated RB with highest PSD. + +NOTE 3: Image frequencies for UL CA are specified in relation to either UL or DL carrier frequency. + +NOTE 4: The measurement bandwidth is 1 RB and the limit is expressed as a ratio of measured power in one non-allocated RB to the measured total power in all allocated RBs. + +NOTE 5: The applicable frequencies for this limit are those that are enclosed in the RBs containing the DC frequency, or in the two RBs immediately adjacent to the DC frequency but excluding any allocated RB. + +NOTE 6: is the Transmission Bandwidth for kth allocated component carrier (see Figure 5.3.3-1). + +NOTE 7: EVM s the limit for the modulation format used in the allocated RBs. + +NOTE 8: is the starting frequency offset between the allocated RB and the measured non-allocated RB (e.g. = 1 or = -1 for the first adjacent RB outside of the allocated bandwidth), and may take non-integer values when the carrier spacing between the CCs is not a multiple of RB. + +NOTE 9: is an average of the transmitted power over 10 sub-frames normalized by the number of allocated RBs, measured in dBm. + +NOTE 10: All powers are EIRP in beam peak direction. + +**Table 6.4.2.3.3-2: Void** + +#### 6.4.2.3.4 In-band emissions for power class 3 + +The average of the in-band emission measurement over 10 sub-frames shall not exceed the values specified in Table 6.4.2.3.4-1 for power class 3 UEs. + +**Table 6.4.2.3.4-1: Requirements for in-band emissions for power class 3** + +| Parameter description | Unit | Limit (NOTE 1) | | | Applicable Frequencies | +|------------------------|------|----------------|--------------------------------|-------------------------------------|--------------------------------| +| General | dB | | | | Any non-allocated (NOTE 2) | +| | | | Output power for FR2-1 | Output Power for FR2-2 | | +| IQ Image | dB | -25 | > 10 dBm | > 8.1 dBm | Image frequencies (NOTES 2, 3) | +| | | -20 | ≤ 10 dBm | ≤ 8.1 dBm | | +| Carrier leakage | dBc | -25 | > 0 dBm | > -1.9 dBm | Carrier frequency (NOTES 4, 5) | +| | | -20 | -13 dBm ≤ Output power ≤ 0 dBm | -14.9 dBm ≤ Output power ≤ -1.9 dBm | | + +NOTE 1: An in-band emissions combined limit is evaluated in each non-allocated RB. For each such RB, the minimum requirement is calculated as the higher of (- 25 dB) and the power sum of all limit values (General, IQ Image or Carrier leakage) that apply. is defined in NOTE 10. + +NOTE 2: The measurement bandwidth is 1 RB and the limit is expressed as a ratio of measured power in one non-allocated RB to the measured average power per allocated RB, where the averaging is done across all allocated RBs. For Pi/2 BPSK with Spectrum Shaping, the limit is expressed as a ratio of measured power in one non-allocated RB to the measured power in the allocated RB with highest PSD + +NOTE 3: The applicable frequencies for this limit are those that are enclosed in the reflection of the allocated bandwidth, based on symmetry with respect to the carrier frequency, but excluding any allocated RBs. + +NOTE 4: The measurement bandwidth is 1 RB and the limit is expressed as a ratio of measured power in one non-allocated RB to the measured total power in all allocated RBs. + +NOTE 5: The applicable frequencies for this limit depend on the parameter *txDirectCurrentLocation* in *UplinkTxDirectCurrent* IE, and are those that are enclosed in the RBs containing the DC frequency but excluding any allocated RB. + +NOTE 6: $L_{CRB}$ is the Transmission Bandwidth (see Clause 5.3). + +NOTE 7: $N_{RB}$ is the Transmission Bandwidth Configuration (see Clause 5.3). + +NOTE 8: EVM is the limit for the modulation format used in the allocated RBs. + +NOTE 9: $\Delta_{RB}$ is the starting frequency offset between the allocated RB and the measured non-allocated RB (e.g. $\Delta_{RB} = 1$ or $\Delta_{RB} = -1$ for the first adjacent RB outside of the allocated bandwidth). + +NOTE 10: is an average of the transmitted power over 10 sub-frames normalized by the number of allocated RBs, measured in dBm. + +NOTE 11: All powers are EIRP in beam peak direction. + +#### 6.4.2.3.5 In-band emissions for power class 4 + +The average of the in-band emission measurement over 10 sub-frames shall not exceed the values specified in Table 6.4.2.3.5-1 for power class 4 UEs. + +**Table 6.4.2.3.5-1: Requirements for in-band emissions for power class 4 in FR2-1** + +| Parameter description | Unit | Limit (NOTE 1) | | Applicable Frequencies | +|------------------------|------|----------------|---------------------------------|--------------------------------| +| General | dB | | | Any non-allocated (NOTE 2) | +| IQ Image | dB | -25 | Output power > 21 dBm | Image frequencies (NOTES 2, 3) | +| | | -20 | Output power ≤ 21 dBm | | +| Carrier leakage | dBc | -25 | Output power > 11 dBm | Carrier frequency (NOTES 4, 5) | +| | | -20 | -13 dBm ≤ Output power ≤ 11 dBm | | + +NOTE 1: An in-band emissions combined limit is evaluated in each non-allocated RB. For each such RB, the minimum requirement is calculated as the higher of (- 25 dB) and the power sum of all limit values (General, IQ Image or Carrier leakage) that apply. is defined in NOTE 10. + +NOTE 2: The measurement bandwidth is 1 RB and the limit is expressed as a ratio of measured power in one non-allocated RB to the measured average power per allocated RB, where the averaging is done across all allocated RBs. For Pi/2 BPSK with Spectrum Shaping, the limit is expressed as a ratio of measured power in one non-allocated RB to the measured power in the allocated RB with highest PSD + +NOTE 3: The applicable frequencies for this limit are those that are enclosed in the reflection of the allocated bandwidth, based on symmetry with respect to the carrier frequency, but excluding any allocated RBs. + +NOTE 4: The measurement bandwidth is 1 RB and the limit is expressed as a ratio of measured power in one non-allocated RB to the measured total power in all allocated RBs. + +NOTE 5: The applicable frequencies for this limit depend on the parameter *txDirectCurrentLocation* in *UplinkTxDirectCurrent* IE, and are those that are enclosed in the RBs containing the DC frequency but excluding any allocated RB. + +NOTE 6: $L_{CRB}$ is the Transmission Bandwidth (see Clause 5.3). + +NOTE 7: $N_{RB}$ is the Transmission Bandwidth Configuration (see Clause 5.3). + +NOTE 8: EVM s the limit for the modulation format used in the allocated RBs. + +NOTE 9: $\Delta_{RB}$ is the starting frequency offset between the allocated RB and the measured non-allocated RB (e.g. $\Delta_{RB} = 1$ or $\Delta_{RB} = -1$ for the first adjacent RB outside of the allocated bandwidth). + +NOTE 10: is an average of the transmitted power over 10 sub-frames normalized by the number of allocated RBs, measured in dBm. + +NOTE 11: All powers are EIRP in beam peak direction. + +### 6.4.2.3.6 In-band emissions for power class 5 + +The average of the in-band emission measurement over 10 sub-frames shall not exceed the values specified in Table 6.4.2.3.6-1 for power class 5 UEs. + +**Table 6.4.2.3.6-1: Requirements for in-band emissions for power class 5 in FR2-1** + +| Parameter description | Unit | Limit (NOTE 1) | | Applicable Frequencies | +|------------------------|------|----------------|-------------------------------|--------------------------------| +| General | dB | | | Any non-allocated (NOTE 2) | +| IQ Image | dB | -25 | Output power > 17 dBm | Image frequencies (NOTES 2, 3) | +| | | -20 | Output power ≤ 17 dBm | | +| Carrier leakage | dBc | -25 | Output power > 7 dBm | Carrier frequency (NOTES 4, 5) | +| | | -20 | -6 dBm ≤ Output power ≤ 7 dBm | | + +NOTE 1: An in-band emissions combined limit is evaluated in each non-allocated RB. For each such RB, the minimum requirement is calculated as the higher of (- 25 dB) and the power sum of all limit values (General, IQ Image or Carrier leakage) that apply. is defined in NOTE 10. + +NOTE 2: The measurement bandwidth is 1 RB and the limit is expressed as a ratio of measured power in one non-allocated RB to the measured average power per allocated RB, where the averaging is done across all allocated RBs. For Pi/2 BPSK with Spectrum Shaping, the limit is expressed as a ratio of measured power in one non-allocated RB to the measured power in the allocated RB with highest PSD + +NOTE 3: The applicable frequencies for this limit are those that are enclosed in the reflection of the allocated bandwidth, based on symmetry with respect to the carrier frequency, but excluding any allocated RBs. + +NOTE 4: The measurement bandwidth is 1 RB and the limit is expressed as a ratio of measured power in one non-allocated RB to the measured total power in all allocated RBs. + +NOTE 5: The applicable frequencies for this limit depend on the parameter *txDirectCurrentLocation* in *UplinkTxDirectCurrent* IE, and are those that are enclosed in the RBs containing the DC frequency but excluding any allocated RB. + +NOTE 6: $L_{CRB}$ is the Transmission Bandwidth (see Clause 5.3). + +NOTE 7: $N_{RB}$ is the Transmission Bandwidth Configuration (see Clause 5.3). + +NOTE 8: EVM is the limit for the modulation format used in the allocated RBs. + +NOTE 9: $\Delta_{RB}$ is the starting frequency offset between the allocated RB and the measured non-allocated RB (e.g. $\Delta_{RB} = 1$ or $\Delta_{RB} = -1$ for the first adjacent RB outside of the allocated bandwidth). + +NOTE 10: is an average of the transmitted power over 10 sub-frames normalized by the number of allocated RBs, measured in dBm. + +NOTE 11: All powers are EIRP in beam peak direction. + +### 6.4.2.3.7 In-band emissions for power class 6 + +For power class 6, the in-band emissions requirement specified in clause 6.4.2.3.6 for power class 5 applies. + +### 6.4.2.3.8 In-band emissions for power class 7 + +The average of the in-band emission specified in subclause 6.4.2.3.4 applies. + +## 6.4.2.4 EVM equalizer spectrum flatness + +The EVM measurement process (as described in Annex F) entails generation of a zero-forcing equalizer. The EVM equalizer spectrum flatness is defined in terms of the maximum peak-to-peak ripple of the equalizer coefficients (dB) across the allocated uplink block. The basic measurement interval is the same as for EVM. + +For Pi/2 BPSK modulation, the minimum requirements are defined in Clause 6.4.2.5. + +The peak-to-peak variation of the EVM equalizer coefficients contained within the frequency range of the uplink allocation shall not exceed the maximum ripple specified in Table 6.4.2.4-1 for normal conditions. For uplink allocations contained within both Range 1 and Range 2, the coefficients evaluated within each of these frequency ranges shall meet the corresponding ripple requirement and the following additional requirements: the relative + +difference between the maximum coefficient in Range 1 and the minimum coefficient in Range 2 (Table 6.4.2.4-1) must not be larger than 7 dB, and the relative difference between the maximum coefficient in Range 2 and the minimum coefficient in Range 1 must not be larger than 8 dB (see Figure 6.4.2.4-1). + +The requirement is verified with the test metric of EVM SF (Link=TX beam peak direction, Meas=Link angle). + +**Table 6.4.2.4-1: Minimum requirements for EVM equalizer spectrum flatness (normal conditions)** + +| Frequency range | Maximum ripple (dB) | +|------------------------------------------------------|---------------------| +| $ F_{UL\_Meas} - F\_center \leq X$ MHz
(Range 1) | 6 (p-p) | +| $ F_{UL\_Meas} - F\_center > X$ MHz
(Range 2) | 9 (p-p) | + +NOTE 1: $F_{UL\_Meas}$ refers to the sub-carrier frequency for which the equalizer coefficient is evaluated +NOTE 2: $F\_center$ refers to the center frequency of the CC +NOTE 3: $X$ , in MHz, is equal to 30 % of the CC bandwidth + +**Table 6.4.2.4-2: (Void)** + +![Figure 6.4.2.4-1: A graph showing the limits for EVM equalizer spectral flatness. The x-axis is labeled |F_UL_Meas - F_center| and has markers at 0 and X. The graph is divided into two regions: Range 1 (from 0 to X) and Range 2 (from X to the right). In Range 1, the spectral flatness is indicated by a horizontal line with a vertical double-headed arrow labeled < 6 dB_p-p. In Range 2, the spectral flatness is indicated by a horizontal line with a vertical double-headed arrow labeled < 9 dB_p-p. The difference between the maximum coefficient in Range 2 and the minimum coefficient in Range 1 is indicated by a vertical double-headed arrow labeled max(Range 2) - min(Range 1) < 8 dB. The difference between the maximum coefficient in Range 1 and the minimum coefficient in Range 2 is indicated by a vertical double-headed arrow labeled max(Range 1) - min(Range 2) < 7 dB.](a25c41b4f7f77363ac12ee931fafe4c7_img.jpg) + +Figure 6.4.2.4-1: A graph showing the limits for EVM equalizer spectral flatness. The x-axis is labeled |F\_UL\_Meas - F\_center| and has markers at 0 and X. The graph is divided into two regions: Range 1 (from 0 to X) and Range 2 (from X to the right). In Range 1, the spectral flatness is indicated by a horizontal line with a vertical double-headed arrow labeled < 6 dB\_p-p. In Range 2, the spectral flatness is indicated by a horizontal line with a vertical double-headed arrow labeled < 9 dB\_p-p. The difference between the maximum coefficient in Range 2 and the minimum coefficient in Range 1 is indicated by a vertical double-headed arrow labeled max(Range 2) - min(Range 1) < 8 dB. The difference between the maximum coefficient in Range 1 and the minimum coefficient in Range 2 is indicated by a vertical double-headed arrow labeled max(Range 1) - min(Range 2) < 7 dB. + +**Figure 6.4.2.4-1: The limits for EVM equalizer spectral flatness with the maximum allowed variation of the coefficients indicated under normal conditions** + +## 6.4.2.5 EVM spectral flatness for Pi/2 BPSK modulation + +These requirements are defined for Pi/2 BPSK modulation. The EVM equalizer coefficients across the allocated uplink block shall be modified to fit inside the mask specified in Table 6.4.2.5-1 for normal conditions, prior to the calculation of EVM. The limiting mask shall be placed to minimize the change in equalizer coefficients in a sum of squares sense. + +**Table 6.4.2.5-1: Mask for EVM equalizer coefficients for pi/2 BPSK (normal conditions)** + +| Frequency range | Parameter | Maximum ripple (dB) | +|------------------------------------------------------|-----------|---------------------| +| $ F_{UL\_Meas} - F\_center \leq X$ MHz
(Range 1) | X1 | 6 (p-p) | +| $ F_{UL\_Meas} - F\_center > X$ MHz
(Range 2) | X2 | 14 (p-p) | + +NOTE 1: $F_{UL\_Meas}$ refers to the sub-carrier frequency for which the equalizer coefficient is evaluated +NOTE 2: $F\_center$ refers to the center frequency of an allocated block of PRBs +NOTE 3: $X$ , in MHz, is equal to 25% of the bandwidth of the PRB allocation +NOTE 4: See Figure 6.4.2.5-1 for description of X1, X2 and X3 + +![Figure 6.4.2.5-1: A graph showing the limits for EVM equalizer spectral flatness. The x-axis is labeled |F_Ul_Meas - F_center| and has markers at 0, X, and the end of Range 2. The y-axis has markers for X1, X2, and X3. Range 1 is from 0 to X, and Range 2 is from X to the end. A horizontal line at height X1 extends from 0 to X. At X, there is a vertical jump of X3 to a height of X2. From X to the end of Range 2, the line is at height X2. A label X2 = X1 + X3 is shown above the jump.](e84508be9dbee463632f183989ce79f9_img.jpg) + +Figure 6.4.2.5-1: A graph showing the limits for EVM equalizer spectral flatness. The x-axis is labeled |F\_Ul\_Meas - F\_center| and has markers at 0, X, and the end of Range 2. The y-axis has markers for X1, X2, and X3. Range 1 is from 0 to X, and Range 2 is from X to the end. A horizontal line at height X1 extends from 0 to X. At X, there is a vertical jump of X3 to a height of X2. From X to the end of Range 2, the line is at height X2. A label X2 = X1 + X3 is shown above the jump. + +**Figure 6.4.2.5-1: The limits for EVM equalizer spectral flatness with the maximum allowed variation. F\_center denotes the center frequency of the allocated block of PRBs.** + +This requirement does not apply to other modulation types. The UE shall be allowed to employ spectral shaping for Pi/2 BPSK. The shaping filter shall be restricted so that the impulse response of the transmit chain shall meet + +$$|\tilde{a}_i(t,0)| \geq |\tilde{a}_i(t,\tau)| \quad \forall \tau \neq 0$$ + +$$20\log_{10} |\tilde{a}_i(t,\tau)| < -15 \text{ dB} \quad 1 < \tau < M - 1,$$ + +Where: + +$$|\tilde{a}_i(t,\tau)| = \text{IDFT} \{ |\tilde{a}_i(t,f)| e^{j\phi(t,f)} \},$$ + +f is the frequency of the M allocated subcarriers, + +$\tilde{a}_i(t,f)$ and $\phi(t,f)$ are the amplitude and phase response, respectively of the transmit chain + +0dB reference is defined as $20\log_{10} |\tilde{a}_i(t,0)|$ + +### 6.4.2.6 Phase continuity requirements for DMRS bundling + +For bands that UE indicates the support of DMRS bundling, when the UE is configured with DMRS bundling, the maximum allowable difference between the measured phase value in any slot $p-1$ and slot $p$ shall satisfy the requirements as listed in Table 6.4.2.6-1 for the measurement conditions defined in Table 6.4.2.6-2, within a measurement time window limited by the UE capability of maximum duration for DMRS bundling [maxDurationDMRS-Bundling-r17], and defined for each frequency band separately. The phase value for each slot is measured as shown in Annex F.8. These requirements apply to PUCCH and PUSCH transmissions with DFT-s-OFDM and CP-OFDM waveforms. + +**Table 6.4.2.6-1: Maximum allowable phase difference for DMRS bundling** + +| UL channel | Modulation order | Phase difference between any slot $p-1$ and slot $p$ (NOTE 2) | +|------------|-----------------------|---------------------------------------------------------------| +| PUSCH | Pi/2 BPSK, QPSK | [25] degrees | +| PUCCH | Pi/2 BPSK, BPSK, QPSK | | + +NOTE 1: The UE capability of the length of maximum duration refers to the maximum time duration during which UE is able to meet the phase continuity requirements, assuming no phase consistency violating events defined in TS 38.214 in between. +NOTE 2: This requirement applies for TDD bands, for supported DMRS bundling configurations $\leq 8$ slots. + +The above requirements are applicable when all the following conditions are met within the measurement time window. + +- RB allocation in terms of length and frequency position does not change, and intra-slot and inter-slot frequency hopping is not activated. +- Modulation order does not change. + +- No network commanded TA takes effect. +- The TPMI precoder does not change. +- There is no change in UE EIRP level, and no change in the level of P-MPR applied by the UE. +- UE is not scheduled with uplink transmission of other physical channel/signal in-between the PUSCH or PUCCH transmissions. +- For TDD, no downlink slot(s) or downlink symbol(s) or flexible symbol(s) with/without DL monitoring occasion configured in-between the PUSCH or PUCCH transmissions. +- No uplink beam switching occurs. + +**Table 6.4.2.6-2: Measurement conditions for the maximum allowable phase difference** + +| Parameter | Unit | Level | +|----------------------------|------|----------------------------------------------------------------------| +| UE EIRP | dBm | $P_{UMAX,f,c}$ in clause 6.2.4, P-MPR = 0 | +| UE downlink received power | | Not change | +| Operating conditions | | Normal conditions | +| Transmission bandwidth | | Confined within $F_{UL\_low} + [4]$ MHz and $F_{UL\_high} - [4]$ MHz | +| DL signal frequency | | Not change before and during the measurement window | +| DL signal timing | | Maintained constant before and during the measurement window | +| UL slots for testing | | Tested on consecutive UL slots | +| PUSCH waveform for testing | | DFT-s-OFDM | + +NOTE: Phase continuity requirements for DMRS bundling is defined only within FR2-1 in this release of the specification. + +## 6.4A Transmit signal quality for CA + +### 6.4A.0 General + +For intra-band contiguous and non-contiguous carrier aggregation, the requirements in this clause apply if the UE has at least one of UL or DL configured for CA. + +### 6.4A.1 Frequency error + +The requirements in this clause apply to UEs of all power classes. + +For intra-band contiguous and non-contiguous carrier aggregation, the UE basic measurement interval of modulated carrier frequency is 1 UL slot. The mean value of basic measurements of UE modulated carrier frequencies per band shall be accurate to within $\pm 0.1$ PPM observed over a period of 1ms of cumulated measurement intervals compared to the carrier frequency of primary component carrier received from the gNB. + +For inter-band carrier aggregation with uplink assigned to two NR bands, and each UL band is configured with a single CC, the frequency error requirement is specified in clause 6.4.1 and is applicable for each CC with all CCs active with non-zero UL RB allocation. + +The frequency error is defined as a directional requirement. The requirement is verified in beam locked mode on beam peak direction. + +## 6.4A.2 Transmit modulation quality + +### 6.4A.2.0 General + +For intra-band contiguous and non-contiguous carrier aggregation, the requirements in clauses 6.4A.2.1, 6.4A.2.2, and 6.4A.2.3 apply. + +All the parameters defined in clause 6.4A.2 are defined using the measurement methodology specified in Annex F. + +All the requirements in 6.4A.2 are defined as directional requirement. The requirements are verified in beam locked mode on beam peak direction. + +The carrier leakage frequency is optionally indicated with IE *UplinkTxDirectCurrentList*, *UplinkTxDirectCurrentTwoCarrierList-r16* for CA with two component carriers configured for uplink or IE *UplinkTxDirectCurrentMoreCarrierList-r17* for any CA configuration. + +If the UE does not indicate DC location parameters, the carrier leakage measurement requirement in clauses 6.4A.2.2 and 6.4A.2.3 shall be waived and the UE's UL signal left uncorrected for carrier leakage. Any requirement relaxation to accommodate the IQ image shall be omitted. + +If the UE indicates carrier leakage frequency as 3300 or 3301 with IE *UplinkTxDirectCurrentList* or *UplinkTxDirectCurrentTwoCarrierList-r16*, or if the carrier leakage frequency is outside the configured UL and DL carriers, the carrier leakage measurement requirement in clause 6.4A.2.2 and 6.4A.2.3 shall be waived and the UE's UL signal left uncorrected for carrier leakage. Any requirement relaxation to accommodate the IQ image shall be omitted. + +For intra-band contiguous and non-contiguous carrier aggregation, the UE is defined to be configured for CA operation when it has at least one of UL or DL configured for CA. + +For inter-band carrier aggregation with uplink assigned to two NR bands, and each UL band is configured with a single CC, the transmit modulation quality requirements are specified in clause 6.4.2 and are applicable for each CC with all CCs active with non-zero UL RB allocation. + +### 6.4A.2.1 Error Vector magnitude + +The requirements in this clause apply to UEs of all power classes. For intra-band contiguous and non-contiguous carrier aggregation, the Error Vector Magnitude requirement of clause 6.4.2.2 is defined for each component carrier. Requirements only apply with PRB allocation in one of the component carriers. Similar transmitter impairment removal procedures are applied for CA waveform before EVM calculation as is specified for non-CA waveform. + +### 6.4A.2.2 Carrier leakage + +#### 6.4A.2.2.1 General + +Carrier leakage is an additive sinusoid waveform. The carrier leakage requirement is defined for each component carrier and is measured on the component carrier with PRBs allocated. The measurement interval is one slot in the time domain. + +Note: When UE has DL configured for intra-band non-contiguous CA, indicated carrier leakage may land outside the spectrum occupied by all configured UL and DL CC. In this case the requirement does not apply. + +The relative carrier leakage power is a power ratio of the additive sinusoid waveform and the modulated waveform. The requirement is verified with the test metric of Carrier Leakage (Link=TX beam peak direction, Meas=Link angle). + +#### 6.4A.2.2.2 Carrier leakage for power class 1 + +For intra-band contiguous and non-contiguous carrier aggregation, when carrier leakage is contained inside the spectrum occupied by all configured UL and DL CCs, the relative carrier leakage power shall not exceed the values specified in Table 6.4A.2.2.2-1 and Table 6.4A.2.2.2-2 for power class 1 UEs. + +**Table 6.4A.2.2.2-1: Minimum requirements for relative carrier leakage for power class 1 in FR2-1** + +| Parameters | Relative Limit (dBc) | +|---------------------------------|----------------------| +| EIRP > 17 dBm | -25 | +| 4 dBm $\leq$ EIRP $\leq$ 17 dBm | -20 | + +**Table 6.4A.2.2.2-2: Minimum requirements for relative carrier leakage for power class 1 in FR2-2** + +| Parameters | Relative Limit (dBc) | +|------------------------------------------------------------------------|----------------------| +| EIRP > 13.4 dBm | -25 | +| 0.4 dBm $\leq$ EIRP $\leq$ 13.4 dBm | -20 | +| NOTE: Not applicable for Intra-band non-contiguous carrier aggregation | | + +#### 6.4A.2.2.3 Carrier leakage for power class 2 + +For intra-band contiguous and non-contiguous carrier aggregation, when carrier leakage is contained inside the spectrum occupied by all configured UL and DL CCs, the relative carrier leakage power shall not exceed the values specified in Table 6.4A.2.2.3-1 and Table 6.4A.2.2.3-2 for power class 2. + +**Table 6.4A.2.2.3-1: Minimum requirements for relative carrier leakage power class 2 in FR2-1** + +| Parameters | Relative limit (dBc) | +|----------------------------------|----------------------| +| EIRP > 6 dBm | -25 | +| -13 dBm $\leq$ EIRP $\leq$ 6 dBm | -20 | + +**Table 6.4A.2.2.3-2: Minimum requirements for relative carrier leakage power class 2 in FR2-2** + +| Parameters | Relative limit (dBc) | +|------------------------------------------------------------------------|----------------------| +| EIRP > 5.8 dBm | -25 | +| -13.2 dBm $\leq$ EIRP $\leq$ 5.8 dBm | -20 | +| NOTE: Not applicable for Intra-band non-contiguous carrier aggregation | | + +For inter-band carrier aggregation with uplink assigned to two NR bands, and each UL band is configured with a single CC, the carrier leakage requirements are specified in clause 6.4.2.2.3 and are applicable for each CC with all CCs active with non-zero UL RB allocation. + +#### 6.4A.2.2.4 Carrier leakage for power class 3 + +For intra-band contiguous and non-contiguous carrier aggregation, when carrier leakage is contained inside the spectrum occupied by all configured UL and DL CCs, the relative carrier leakage power shall not exceed the values specified in Table 6.4A.2.2.4-1 and Table 6.4A.2.2.4-2 for power class 3 UEs. + +**Table 6.4A.2.2.4-1: Minimum requirements for relative carrier leakage power class 3 in FR2-1** + +| Parameters | Relative limit (dBc) | +|-----------------------------------------------|----------------------| +| Output power > 0 dBm | -25 | +| -13 dBm $\leq$ Output power EIRP $\leq$ 0 dBm | -20 | + +**Table 6.4A.2.2.4-2: Minimum requirements for relative carrier leakage power class 3 in FR2-2** + +| Parameters | Relative limit (dBc) | +|------------------------------------------------------------------------|----------------------| +| Output power > -1.9 dBm | -25 | +| -14.9 dBm $\leq$ Output power EIRP $\leq$ -1.9 dBm | -20 | +| NOTE: Not applicable for Intra-band non-contiguous carrier aggregation | | + +For inter-band carrier aggregation with uplink assigned to two NR bands, and each UL band is configured with a single CC, the carrier leakage requirements are specified in clause 6.4.2.2.4 and are applicable for each CC with all CCs active with non-zero UL RB allocation. + +#### 6.4A.2.2.5 Carrier leakage for power class 4 + +For intra-band contiguous and non-contiguous carrier aggregation, when carrier leakage is contained inside the spectrum occupied by all configured UL and DL CCs, the relative carrier leakage power shall not exceed the values specified in Table 6.4A.2.2.5-1 for power class 4 UEs. + +**Table 6.4A.2.2.5-1: Minimum requirements for relative carrier leakage power class 4** + +| Parameters | Relative limit (dBc) | +|------------------------------------------------|----------------------| +| Output power > 11 dBm | -25 | +| -13 dBm $\leq$ Output power EIRP $\leq$ 11 dBm | -20 | + +#### 6.4A.2.2.6 Carrier leakage for power class 5 + +For intra-band contiguous and non-contiguous carrier aggregation, when carrier leakage is contained inside the spectrum occupied by all configured UL and DL CCs, the relative carrier leakage power shall not exceed the values specified in Table 6.4A.2.2.6-1 for power class 5 UEs. + +**Table 6.4A.2.2.6-1: Minimum requirements for relative carrier leakage power class 5** + +| Parameters | Relative limit (dBc) | +|----------------------------------------------|----------------------| +| Output power > 7 dBm | -25 | +| -6 dBm $\leq$ Output power EIRP $\leq$ 7 dBm | -20 | + +For inter-band carrier aggregation with uplink assigned to two NR bands, and each UL band is configured with a single CC, the carrier leakage requirements are specified in clause 6.4.2.2.6 and are applicable for each CC with all CCs active with non-zero UL RB allocation. + +#### 6.4A.2.2.7 Carrier leakage for power class 6 + +For intra-band contiguous and non-contiguous carrier aggregation, the carrier leakage requirement specified in clause 6.4A.2.2.6 for power class 5 applies. + +### 6.4A.2.3 Inband emissions + +#### 6.4A.2.3.1 General + +For intra-band contiguous and non-contiguous carrier aggregation, the Inband emission requirement is defined over the spectrum occupied by all configured UL and DL CCs. The measurement interval is as defined in clause 6.4.2.4. The requirement is verified with the test metric of In-band emission (Link=TX beam peak direction, Meas=Link angle). + +For intra-band contiguous and non-contiguous carrier aggregation, the requirements in this clause apply with all component carriers active and with one single contiguous PRB allocation in one of uplink component carriers. The inband emission is defined as the interference falling into the non-allocated resource blocks for all component carriers. + +For inter-band carrier aggregation with uplink assigned to two NR bands, and each UL band is configured with a single CC, the in-band emissions requirements are applicable for each CC with all CCs active with non-zero UL RB allocation. + +### 6.4A.2.3.2 Inband emissions for power class 1 + +For intra-band contiguous and non-contiguous carrier aggregation, the average of the in-band emission measurement over 10 sub-frames shall not exceed the values specified in Table 6.4A.2.3.2-1 for power class 1 UEs. + +For inter-band carrier aggregation with uplink assigned to two NR bands, and each UL band is configured with a single CC, the in-band emissions requirements are specified in clause 6.4.2.3.2 and are applicable for each CC with all CCs active with non-zero UL RB allocation. + +**Table 6.4A.2.3.2-1: Requirements for in-band emissions for power class 1** + +| Parameter description | Unit | Limit (NOTE 1) | | | Applicable Frequencies | +|------------------------|------|----------------|-------------------------------|-----------------------------------|---------------------------------------------------------------------------------------------------| +| General | dB | | | | Any non-allocated RB in allocated component carrier and not allocated component carriers (NOTE 2) | +| | | | Output power for FR2-1 | Output Power for FR2-2 | | +| IQ Image | dB | -25 | Output power > 27 dBm | > 23.4 dBm | Image frequencies (NOTES 2, 3) | +| | | -20 | Output power ≤ 27 dBm | ≤ 23.4 dBm | | +| Carrier leakage | dBc | -25 | Output power > 17 dBm | > 13.4 dBm | Carrier frequency (NOTES 4, 5) | +| | | -20 | 4 dBm ≤ Output power ≤ 17 dBm | 0.4 dBm ≤ Output power ≤ 13.4 dBm | | + +NOTE 1: An in-band emissions combined limit is evaluated in each non-allocated RB. For each such RB, the minimum requirement is calculated as the higher of (- 25 dB) and the power sum of all limit values (General, IQ Image or Carrier leakage) that apply. is defined in NOTE 9. + +NOTE 2: The measurement bandwidth is 1 RB and the limit is expressed as a ratio of measured power in one non-allocated RB to the measured average power per allocated RB, where the averaging is done across all allocated RBs. For Pi/2 BPSK with Spectrum Shaping, the limit is expressed as a ratio of measured power in one non-allocated RB to the measured power in the allocated RB with highest PSD. + +NOTE 3: Image frequencies for UL CA are specified in relation to either UL or DL carrier frequency. + +NOTE 4: The measurement bandwidth is 1 RB and the limit is expressed as a ratio of measured power in one non-allocated RB to the measured total power in all allocated RBs. + +NOTE 5: The applicable frequencies for this limit are those that are enclosed in the RBs containing the DC frequency, or in the two RBs immediately adjacent to the DC frequency but excluding any allocated RB. + +NOTE 6: $B_{k,tx}$ is the Transmission Bandwidth for kth allocated component carrier (see Figure 5.3.3-1). + +NOTE 7: $EVM_{k,tx}$ is the limit for the modulation format used in the allocated RBs. + +NOTE 8: $\Delta f_{k,tx}$ is the starting frequency offset between the allocated RB and the measured non-allocated RB (e.g. $\Delta f_{k,tx} = 1$ or $\Delta f_{k,tx} = -1$ for the first adjacent RB outside of the allocated bandwidth), and may take non-integer values when the carrier spacing between the CCs is not a multiple of RB. + +NOTE 9: $P_{k,tx}$ is an average of the transmitted power over 10 sub-frames normalized by the number of allocated RBs, measured in dBm. + +NOTE 10: All powers are EIRP in beam peak direction. + +### 6.4A.2.3.3 Inband emissions for power class 2 + +For intra-band contiguous and non-contiguous carrier aggregation, the average of the in-band emission measurement over 10 sub-frames shall not exceed the values specified in Table 6.4A.2.3.3-1 for power class 2. + +For inter-band carrier aggregation with uplink assigned to two NR bands, and each UL band is configured with a single CC, the in-band emissions requirements are specified in clause 6.4.2.3.3 and are applicable for each CC with all CCs active with non-zero UL RB allocation. + +**Table 6.4A.2.3.3-1: Requirements for in-band emissions for power class 2** + +| Parameter description | Unit | Limit (NOTE 1) | | | Applicable Frequencies | +|------------------------|------|----------------|--------------------------------|------------------------------------|---------------------------------------------------------------------------------------------------| +| General | dB | | | | Any non-allocated RB in allocated component carrier and not allocated component carriers (NOTE 2) | +| | | | Output power for FR2-1 | Output Power for FR2-2 | | +| IQ Image | dB | -25 | Output power > 16 dBm | Output power > 15.8 dBm | Image frequencies (NOTES 2, 3) | +| | | -20 | Output power ≤ 16 dBm | Output power ≤ 15.8 dBm | | +| Carrier leakage | dBc | -25 | Output power > 6 dBm | Output power > 5.8 dBm | Carrier frequency (NOTES 4, 5) | +| | | -20 | -13 dBm ≤ Output power ≤ 6 dBm | -13.2 dBm ≤ Output power ≤ 5.8 dBm | | + +NOTE 1: An in-band emissions combined limit is evaluated in each non-allocated RB. For each such RB, the minimum requirement is calculated as the higher of (- 25 dB) and the power sum of all limit values (General, IQ Image or Carrier leakage) that apply. is defined in NOTE 9. + +NOTE 2: The measurement bandwidth is 1 RB and the limit is expressed as a ratio of measured power in one non-allocated RB to the measured average power per allocated RB, where the averaging is done across all allocated RBs. For Pi/2 BPSK with Spectrum Shaping, the limit is expressed as a ratio of measured power in one non-allocated RB to the measured power in the allocated RB with highest PSD. + +NOTE 3: Image frequencies for UL CA are specified in relation to either UL or DL carrier frequency. + +NOTE 4: The measurement bandwidth is 1 RB and the limit is expressed as a ratio of measured power in one non-allocated RB to the measured total power in all allocated RBs. + +NOTE 5: The applicable frequencies for this limit are those that are enclosed in the RBs containing the DC frequency, or in the two RBs immediately adjacent to the DC frequency but excluding any allocated RB. + +NOTE 6: is the Transmission Bandwidth for kth allocated component carrier (see Figure 5.3.3-1). + +NOTE 7: EVM s the limit for the modulation format used in the allocated RBs. + +NOTE 8: is the starting frequency offset between the allocated RB and the measured non-allocated RB (e.g. = 1 or = -1 for the first adjacent RB outside of the allocated bandwidth), and may take non-integer values when the carrier spacing between the CCs is not a multiple of RB. + +NOTE 9: is an average of the transmitted power over 10 sub-frames normalized by the number of allocated RBs, measured in dBm. + +NOTE 10: All powers are EIRP in beam peak direction. + +#### 6.4A.2.3.4 Inband emissions for power class 3 + +For intra-band contiguous and non-contiguous carrier aggregation, the average of the in-band emission measurement over 10 sub-frames shall not exceed the values specified in Table 6.4A.2.3.4-1 for power class 3 UEs. + +For inter-band carrier aggregation with uplink assigned to two NR bands, and each UL band is configured with a single CC, the in-band emissions requirements are specified in clause 6.4.2.3.4 and are applicable for each CC with all CCs active with non-zero UL RB allocation. + +**Table 6.4A.2.3.4-1: Requirements for in-band emissions for power class 3** + +| Parameter description | Unit | Limit (NOTE 1) | | | Applicable Frequencies | +|------------------------|------|----------------|--------------------------------|-------------------------------------|---------------------------------------------------------------------------------------------------| +| General | dB | | | | Any non-allocated RB in allocated component carrier and not allocated component carriers (NOTE 2) | +| | | | Output power for FR2-1 | Output Power for FR2-2 | | +| IQ Image | dB | -25 | Output power > 10 dBm | > 8.1 dBm | Image frequencies (NOTES 2, 3) | +| | | -20 | Output power ≤ 10 dBm | ≤ 8.1 dBm | | +| Carrier leakage | dBc | -25 | Output power > 0 dBm | > -1.9 dBm | Carrier frequency (NOTES 4, 5) | +| | | -20 | -13 dBm ≤ Output power ≤ 0 dBm | -14.9 dBm ≤ Output power ≤ -1.9 dBm | | + +NOTE 1: An in-band emissions combined limit is evaluated in each non-allocated RB. For each such RB, the minimum requirement is calculated as the higher of (- 25 dB) and the power sum of all limit values (General, IQ Image or Carrier leakage) that apply. is defined in NOTE 9. + +NOTE 2: The measurement bandwidth is 1 RB and the limit is expressed as a ratio of measured power in one non-allocated RB to the measured average power per allocated RB, where the averaging is done across all allocated RBs. For Pi/2 BPSK with Spectrum Shaping, the limit is expressed as a ratio of measured power in one non-allocated RB to the measured power in the allocated RB with highest PSD. + +NOTE 3: Image frequencies for UL CA are specified in relation to either UL or DL carrier frequency. + +NOTE 4: The measurement bandwidth is 1 RB and the limit is expressed as a ratio of measured power in one non-allocated RB to the measured total power in all allocated RBs. + +NOTE 5: The applicable frequencies for this limit are those that are enclosed in the RBs containing the DC frequency, or in the two RBs immediately adjacent to the DC frequency but excluding any allocated RB. + +NOTE 6: is the Transmission Bandwidth for kth allocated component carrier (see Figure 5.3.3-1). + +NOTE 7: EVM s the limit for the modulation format used in the allocated RBs. + +NOTE 8: is the starting frequency offset between the allocated RB and the measured non-allocated RB (e.g. = 1 or = -1 for the first adjacent RB outside of the allocated bandwidth), and may take non-integer values when the carrier spacing between the CCs is not a multiple of RB. + +NOTE 9: is an average of the transmitted power over 10 sub-frames normalized by the number of allocated RBs, measured in dBm. + +NOTE 10: All powers are EIRP in beam peak direction. + +### 6.4A.2.3.5 Inband emissions for power class 4 + +For intra-band contiguous and non-contiguous carrier aggregation, the average of the in-band emission measurement over 10 sub-frames shall not exceed the values specified in Table 6.4A.2.3.5-1 for power class 4 UEs. + +**Table 6.4A.2.3.5-1: Requirements for in-band emissions for power class 4** + +| Parameter description | Unit | Limit (NOTE 1) | | | Applicable Frequencies | +|------------------------|------|----------------|---------------------------------|--|---------------------------------------------------------------------------------------------------| +| General | dB | | | | Any non-allocated RB in allocated component carrier and not allocated component carriers (NOTE 2) | +| IQ Image | dB | -25 | Output power > 21 dBm | | Image frequencies (NOTES 2, 3) | +| | | -20 | Output power ≤ 21 dBm | | | +| Carrier leakage | dBc | -25 | Output power > 11 dBm | | Carrier frequency (NOTES 4, 5) | +| | | -20 | -13 dBm ≤ Output power ≤ 11 dBm | | | + +- NOTE 1: An in-band emissions combined limit is evaluated in each non-allocated RB. For each such RB, the minimum requirement is calculated as the higher of (- 25 dB) and the power sum of all limit values (General, IQ Image or Carrier leakage) that apply. is defined in NOTE 9. +- NOTE 2: The measurement bandwidth is 1 RB and the limit is expressed as a ratio of measured power in one non-allocated RB to the measured average power per allocated RB, where the averaging is done across all allocated RBs. For pi/2 BPSK with Spectrum Shaping, the limit is expressed as a ratio of measured power in one non-allocated RB to the measured power in the allocated RB with highest PSD. +- NOTE 3: Image frequencies for UL CA are specified in relation to either UL or DL carrier frequency. +- NOTE 4: The measurement bandwidth is 1 RB and the limit is expressed as a ratio of measured power in one non-allocated RB to the measured total power in all allocated RBs. +- NOTE 5: The applicable frequencies for this limit are those that are enclosed in the RBs containing the DC frequency, or in the two RBs immediately adjacent to the DC frequency but excluding any allocated RB. +- NOTE 6: is the Transmission Bandwidth for kth allocated component carrier (see Figure 5.3.3-1). +- NOTE 7: EVM s the limit for the modulation format used in the allocated RBs. +- NOTE 8: is the starting frequency offset between the allocated RB and the measured non-allocated RB (e.g. = 1 or = -1 for the first adjacent RB outside of the allocated bandwidth), and may take non-integer values when the carrier spacing between the CCs is not a multiple of RB. +- NOTE 9: is an average of the transmitted power over 10 sub-frames normalized by the number of allocated RBs, measured in dBm. +- NOTE 10: All powers are EIRP in beam peak direction. + +#### 6.4A.2.3.6 Inband emissions for power class 5 + +For intra-band contiguous and non-contiguous carrier aggregation, the average of the in-band emission measurement over 10 sub-frames shall not exceed the values specified in Table 6.4A.2.3.6-1 for power class 6 UEs. + +For inter-band carrier aggregation with uplink assigned to two NR bands, and each UL band is configured with a single CC, the in-band emissions requirements are specified in clause 6.4.2.3.6 and are applicable for each CC with all CCs active with non-zero UL RB allocation. + +**Table 6.4A.2.3.6-1: Requirements for in-band emissions for power class 5** + +| Parameter description | Unit | Limit (NOTE 1) | | Applicable Frequencies | +|------------------------|------|----------------|-------------------------------|---------------------------------------------------------------------------------------------------| +| General | dB | | | Any non-allocated RB in allocated component carrier and not allocated component carriers (NOTE 2) | +| IQ Image | dB | -25 | Output power > 17 dBm | Image frequencies (NOTES 2, 3) | +| | | -20 | Output power ≤ 17 dBm | | +| Carrier leakage | dBc | -25 | Output power > 7 dBm | Carrier frequency (NOTES 4, 5) | +| | | -20 | -6 dBm ≤ Output power ≤ 7 dBm | | + +- NOTE 1: An in-band emissions combined limit is evaluated in each non-allocated RB. For each such RB, the minimum requirement is calculated as the higher of (- 25 dB) and the power sum of all limit values (General, IQ Image or Carrier leakage) that apply. is defined in NOTE 9. +- NOTE 2: The measurement bandwidth is 1 RB and the limit is expressed as a ratio of measured power in one non-allocated RB to the measured average power per allocated RB, where the averaging is done across all allocated RBs. For pi/2 BPSK with Spectrum Shaping, the limit is expressed as a ratio of measured power in one non-allocated RB to the measured power in the allocated RB with highest PSD. +- NOTE 3: Image frequencies for UL CA are specified in relation to either UL or DL carrier frequency. +- NOTE 4: The measurement bandwidth is 1 RB and the limit is expressed as a ratio of measured power in one non-allocated RB to the measured total power in all allocated RBs. +- NOTE 5: The applicable frequencies for this limit are those that are enclosed in the RBs containing the DC frequency, or in the two RBs immediately adjacent to the DC frequency but excluding any allocated RB. +- NOTE 6: is the Transmission Bandwidth for kth allocated component carrier (see Figure 5.3.3-1). +- NOTE 7: EVM s the limit for the modulation format used in the allocated RBs. +- NOTE 8: is the starting frequency offset between the allocated RB and the measured non-allocated RB (e.g. = 1 or = -1 for the first adjacent RB outside of the allocated bandwidth), and may take non-integer values when the carrier spacing between the CCs is not a multiple of RB. +- NOTE 9: is an average of the transmitted power over 10 sub-frames normalized by the number of allocated RBs, measured in dBm. +- NOTE 10: All powers are EIRP in beam peak direction. + +#### 6.4A.2.3.7 Inband emissions for power class 6 + +For intra-band contiguous and non-contiguous carrier aggregation, the average of the in-band emission specified in clause 6.4A.2.3.6 applies + +#### 6.4A.2.4 EVM equalizer spectrum flatness + +For inter-band carrier aggregation with uplink assigned to two NR bands, and each UL band is configured with a single CC, the EVM equalizer spectrum flatness requirements are specified in clause 6.4.2.4 and are applicable for each CC with all CCs active with non-zero UL RB allocation. + +### 6.4D Transmit signal quality for UL MIMO + +#### 6.4D.0 General + +references to sub-clauses 6.3.1.x in clause 6.4 redirected to sub-clauses 6.3D.1.x, where 'x' depends on power class. The requirements apply when the UE is configured for 2-layer UL MIMO transmission as specified in Table 6.2D.1.0-1. + +The requirement may alternatively be verified in each of the single layer UL MIMO configurations as specified in Table 6.4D.0-1. In this case, the transmit modulation quality requirements in clause 6.4 apply without modification. + +**Table 6.4D.0-1: Alternative UL MIMO configuration for transmit signal quality tests** + +| Transmission scheme | DCI format | TPMI Index | +|-----------------------|----------------|------------| +| Codebook based uplink | DCI format 0_1 | 0 | +| Codebook based uplink | DCI format 0_1 | 1 | + +#### 6.4D.1 Frequency error for UL MIMO + +For a UE supporting UL MIMO, the UE basic measurement interval of modulated carrier frequency is 1 UL slot. The mean value of basic measurements of UE modulated carrier frequency at each layer shall be accurate to within $\pm 0.1$ PPM observed over a period of 1ms of cumulated measurement intervals compared to the carrier frequency received from the NR Node B. + +## 6.4D.2 Transmit modulation quality for UL MIMO + +For UE supporting UL MIMO, the transmit modulation quality requirements are specified per layer in terms of: + +Error Vector Magnitude (EVM) for the allocated resource blocks (RBs) + +EVM equalizer spectrum flatness derived from the equalizer coefficients generated by the EVM measurement process + +Carrier leakage (caused by IQ offset) + +For UE supporting UL MIMO, the transmit modulation quality requirements are specified as the total component of EIRP in terms of: In-band emissions for the non-allocated RB + +The requirements are defined as directional requirements. The requirements are verified in beam locked mode in the TX beam peak direction (Link=TX beam peak direction, Meas=Link angle). + +In case the parameter 3300 or 3301 is reported from UE via the parameter *txDirectCurrentLocation* in *UplinkTxDirectCurrentList* IE (as defined in TS 38.331 [13]), carrier leakage measurement requirement in clause 6.4D.2.2 and 6.4D.2.3 shall be waived, and the RF correction with regard to the carrier leakage and IQ image shall be omitted during the calculation of transmit modulation quality. + +## 6.4D.3 Time alignment error for UL MIMO + +For a UE with multiple physical antenna ports supporting UL MIMO, this requirement applies to frame timing differences between transmissions on multiple physical antenna ports in the codebook transmission scheme. + +The time alignment error (TAE) is defined as the average frame timing difference between any two transmissions on different physical antenna ports. + +For a UE with multiple physical antenna ports, the Time Alignment Error (TAE) shall not exceed 130 ns. + +## 6.4D.4 Requirements for coherent UL MIMO + +For coherent UL MIMO, Table 6.4D.4-1 lists the maximum allowable difference between the measured relative power and phase errors between different physical antenna ports in any slot within the specified time window from the last transmitted SRS on the same antenna ports, for the purpose of uplink transmission (codebook or non-codebook usage) and those measured at that last SRS. The requirements in Table 6.4D.4-1 apply when the UL transmission power at each physical antenna port is larger than 0 dBm for SRS transmission and for the duration of time window. The requirement is verified with the test metric of EIRP (Link=TX Beam peak direction, Meas=Link angle). + +**Table 6.4D.4-1: Maximum allowable difference of relative phase and power errors in a given slot compared to those measured at last SRS transmitted** + +| Difference of relative phase error | Difference of relative power error | Time window | +|------------------------------------|------------------------------------|-------------| +| 40 degrees | 4 dB | 20 msec | + +The above requirements apply when all of the following conditions are met within the specified time window: + +- UE is not signaled with a change in number of SRS ports in *SRS-config*, or a change in *PUSCH-config* +- UE remains in DRX active time (UE does not enter DRX OFF time) +- No measurement gap occurs +- No instance of SRS transmission with the usage antenna switching occurs +- Active BWP remains the same +- EN-DC and CA configuration is not changed for the UE (UE is not configured or de-configured with PCell or SCell(s)) + +## 6.5 Output RF spectrum emissions + +### 6.5.1 Occupied bandwidth + +Occupied bandwidth is defined as the bandwidth containing 99 % of the total integrated mean power of the transmitted spectrum on the assigned channel. The occupied bandwidth for all transmission bandwidth configurations (Resources Blocks) shall be less than the channel bandwidth specified in Table 6.5.1-1. + +The occupied bandwidth is defined as a directional requirement. The requirement is verified in beam locked mode with the test metric of OBW (Link=TX beam peak direction, Meas=Link angle). + +**Table 6.5.1-1: Occupied channel bandwidth** + +| | Occupied channel bandwidth / Channel bandwidth | | | | | | | +|-------------------------|------------------------------------------------|---------|---------|---------|---------|----------|----------| +| | 50 MHz | 100 MHz | 200 MHz | 400 MHz | 800 MHz | 1600 MHz | 2000 MHz | +| Channel bandwidth (MHz) | 50 | 100 | 200 | 400 | 800 | 1600 | 2000 | + +### 6.5.2 Out of band emissions + +#### 6.5.2.0 General + +The Out of band emissions are unwanted emissions immediately outside the assigned channel bandwidth resulting from the modulation process and non-linearity in the transmitter but excluding spurious emissions. This out of band emission limit is specified in terms of a spectrum emission mask and an adjacent channel leakage power ratio. Additional requirements to protect specific bands are also considered. + +The requirements in clause 6.5.2.1 only apply when both UL and DL of a UE are configured for single CC operation, and they are of the same bandwidth. For a UE that is configured for single CC operation with different channel bandwidths in UL and DL, the requirements in clause 6.5A.2.1 apply. + +All out of band emissions for frequency range 2 are TRP. + +#### 6.5.2.1 Spectrum emission mask + +The spectrum emission mask of the UE applies to frequencies ( $\Delta f_{\text{OOB}}$ ) starting from the $\pm$ edge of the assigned NR channel bandwidth. For frequencies offset greater than $F_{\text{OOB}}$ as specified in Table 6.5.2.1-1 the spurious requirements in clause 6.5.3 are applicable. + +The power of any UE emission shall not exceed the levels specified in Table 6.5.2.1-1 for the specified channel bandwidth. The requirement is verified in beam locked mode with the test metric of TRP (Link=TX beam peak direction, Meas=TRP grid). + +**Table 6.5.2.1-1: General NR spectrum emission mask for frequency range 2.** + +| $\Delta f_{\text{OOB}}$
(MHz) | Spectrum emission limit (dBm) / Channel bandwidth | | | | | | | Measurement
bandwidth | +|----------------------------------|---------------------------------------------------|------------|------------|------------|---------|----------|----------|--------------------------| +| | 50
MHz | 100
MHz | 200
MHz | 400
MHz | 800 MHz | 1600 MHz | 2000 MHz | | +| $\pm 0-5$ | -5 | -5 | -5 | -5 | -5 | -5 | -5 | 1 MHz | +| $\pm 5-10$ | -13 | -5 | -5 | -5 | -5 | -5 | -5 | 1 MHz | +| $\pm 10-20$ | -13 | -13 | -5 | -5 | -5 | -5 | -5 | 1 MHz | +| $\pm 20-40$ | -13 | -13 | -13 | -5 | -5 | -5 | -5 | 1 MHz | +| $\pm 40-80$ | -13 | -13 | -13 | -13 | -5 | -5 | -5 | 1 MHz | +| $\pm 80-100$ | -13 | -13 | -13 | -13 | -13 | -5 | -5 | 1 MHz | +| $\pm 100-160$ | | -13 | -13 | -13 | -13 | -5 | -5 | 1 MHz | +| $\pm 160-200$ | | -13 | -13 | -13 | -13 | -13 | -5 | 1 MHz | +| $\pm 200-400$ | | | -13 | -13 | -13 | -13 | -13 | 1 MHz | +| $\pm 400-800$ | | | | -13 | -13 | -13 | -13 | 1 MHz | +| $\pm 800-1600$ | | | | | -13 | -13 | -13 | 1 MHz | +| $\pm 1600-3200$ | | | | | | -13 | -13 | 1 MHz | +| $\pm 3200-4000$ | | | | | | | -13 | 1 MHz | + +NOTE 1: Void + +## 6.5.2.2 Void + +## 6.5.2.3 Adjacent channel leakage ratio + +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. ACLR requirement is specified for a scenario in which adjacent carrier is another NR channel. + +NR Adjacent Channel Leakage power Ratio (NRACLR) 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 at nominal channel spacing. The assigned NR channel power and adjacent NR channel power are measured with rectangular filters with measurement bandwidths specified in Table 6.5.2.3-1 for FR2-1 and in Table 6.5.2.3-2 for FR2-2. + +If the measured adjacent channel power is greater than $-35$ dBm then the NRACLR shall be higher than the value specified in Table 6.5.2.3-1. The requirement is verified in beam locked mode with the test metric of TRP (Link=TX beam peak direction, Meas=TRP grid). + +**Table 6.5.2.3-1: General requirements for NRACLR for FR2-1** + +| | Channel bandwidth / NR ACLR / Measurement bandwidth | | | | +|---------------------------------------------------|----------------------------------------------------------------|-------------------|-------------------|-------------------| +| | 50
MHz | 100
MHz | 200
MHz | 400
MHz | +| NR ACLR for band n257,
n258, n261 | 17 dB | 17 dB | 17 dB | 17 dB | +| NR ACLR for band n259,
n260, n262 | 16 dB | 16 dB | 16 dB | 16 dB | +| NR channel measurement
bandwidth (MHz) | 47.58 | 95.16 | 190.20 | 380.28 | +| Adjacent channel centre
frequency offset (MHz) | +50
/
-50 | +100
/
-100 | +200
/
-200 | +400
/
-400 | + +**Table 6.5.2.3-2: General requirements for NRACLR for FR2-2** + +| | Channel bandwidth / NR ACLR / Measurement bandwidth | | | | | +|------------------------------------------------|----------------------------------------------------------------|-------------------|-------------------|---------------------|---------------------| +| | 100 MHz | 400 MHz | 800 MHz | 1600 MHz | 2000 MHz | +| NR ACLR for band n263 | 15dB | 15 dB | 15 dB | 15 dB | 15 dB | +| NR channel measurement bandwidth (MHz) | 95.16 | 381.12 | 715.20 | 1429.44 | 1705.92 | +| Adjacent channel centre frequency offset (MHz) | +100
/
-100 | +400
/
-400 | +800
/
-800 | +1600
/
-1600 | +2000
/
-2000 | + +### 6.5.3 Spurious emissions + +Spurious emissions are emissions which are caused by unwanted transmitter effects such as harmonics emission, parasitic emissions, intermodulation products and frequency conversion products, but exclude out of band emissions unless otherwise stated. The spurious emission limits are specified in terms of general requirements in line with SM.329 [7] and NR operating band requirement to address UE co-existence. Spurious emissions are measured as TRP. + +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. + +Unless otherwise stated, the spurious emission limits apply for the frequency ranges that are more than FOOB (MHz) in Table 6.5.3-1 starting from the edge of the assigned NR channel bandwidth. The spurious emission limits in Table 6.5.3-2 apply for all transmitter band configurations (NRB) and channel bandwidths. The requirement is verified in beam locked mode with the test metric of TRP (Link=TX beam peak direction, Meas=TRP grid). + +NOTE: For measurement conditions at the edge of each frequency range, the lowest frequency of the measurement position in each frequency range should be set at the lowest boundary of the frequency range plus MBW/2. The highest frequency of the measurement position in each frequency range should be set at the highest boundary of the frequency range minus MBW/2. MBW denotes the measurement bandwidth defined for the protected band. + +**Table 6.5.3-1: Boundary between NR out of band and spurious emission domain** + +| Channel bandwidth | 50 MHz | 100 MHz | 200 MHz | 400 MHz | 800 MHz | 1600 MHz | 2000 MHz | +|-------------------------------------|--------|---------|---------|---------|---------|----------|----------| +| OOB boundary F OOB (MHz) | 100 | 200 | 400 | 800 | 1600 | 3200 | 4000 | + +**Table 6.5.3-2: Spurious emissions limits** + +| Frequency Range | Maximum Level | Measurement bandwidth | +|------------------------------------------------------------------------------------------------------|---------------|-----------------------| +| 30 MHz ≤ f < 1000 MHz | -36 dBm | 100 kHz | +| 1 GHz ≤ f < 12.75 GHz | -30 dBm | 1 MHz | +| 12.75 GHz ≤ f ≤ 2 nd harmonic of the upper frequency edge of the UL operating band in GHz | -13 dBm | 1 MHz | + +#### 6.5.3.1 Spurious emission band UE co-existence + +This clause specifies the requirements for the specified NR band, for coexistence with protected bands. + +NOTE: For measurement conditions at the edge of each frequency range, the lowest frequency of the measurement position in each frequency range should be set at the lowest boundary of the frequency range plus MBW/2. The highest frequency of the measurement position in each frequency range should be set at the highest boundary of the frequency range minus MBW/2. MBW denotes the measurement bandwidth defined for the protected band. + +**Table 6.5.3.1-1: Requirements** + +| NR Band | Spurious emission | | | | | | +|---------|--------------------------------|-----------------------|---|----------------------|-----------|-------| +| | Protected band/frequency range | Frequency range (MHz) | | Maximum Level (dBm) | MBW (MHz) | NOTE | +| n257 | NR Band n260 | F DL_low | - | F DL_high | -2 | 100 | +| | NR Band n263 | F DL_low | - | F DL_high | TBD | 100 | +| | Frequency range | 57000 | - | 66000 | 2 | 100 | +| | Frequency range | 23600 | - | 24000 | 1 | 200 3 | +| n258 | NR Band n263 | F DL_low | - | F DL_high | TBD | 100 | +| | Frequency range | 57000 | - | 66000 | 2 | 100 | +| n259 | NR Band 257 | F DL_low | - | F DL_high | -5 | 100 | +| | NR Band 261 | F DL_low | - | F DL_high | -5 | 100 | +| | NR Band 262 | F DL_low | - | F DL_high | -5 | 100 | +| | NR Band n263 | F DL_low | - | F DL_high | TBD | 100 | +| | Frequency range | 36000 | - | 37000 | 7 | 1000 | +| | Frequency range | 57000 | - | 66000 | 2 | 100 | +| n260 | NR Band 257 | F DL_low | - | F DL_high | -5 | 100 | +| | NR Band 261 | F DL_low | - | F DL_high | -5 | 100 | +| | NR Band 262 | F DL_low | - | F DL_high | -5 | 100 | +| | NR Band n263 | F DL_low | - | F DL_high | TBD | 100 | +| | Frequency range | 57000 | - | 66000 | 2 | 100 | +| n261 | NR Band 260 | F DL_low | - | F DL_high | -2 | 100 | +| | NR Band n263 | F DL_low | - | F DL_high | TBD | 100 | +| | Frequency range | 57000 | - | 66000 | 2 | 100 | +| n262 | NR Band 260 | F DL_low | - | F DL_high | -2 | 100 | +| | NR Band 261 | F DL_low | - | F DL_high | -5 | 100 | +| | NR Band n263 | F DL_low | - | F DL_high | TBD | 100 | +| | Frequency range | 57000 | - | 66000 | 2 | 100 | +| n263 | NR Band 257 | F DL_low | - | F DL_high | -5 | 100 | +| | NR Band 258 | F DL_low | - | F DL_high | -5 | 100 | +| | NR Band 259 | F DL_low | - | F DL_high | -5 | 100 | +| | NR Band 260 | F DL_low | - | F DL_high | -2 | 100 | +| | NR Band 261 | F DL_low | - | F DL_high | -5 | 100 | +| | NR Band 262 | F DL_low | - | F DL_high | -5 | 100 | + +NOTE 1: FDL\_low and FDL\_high refer to each NR frequency band specified in Table 5.2-1 + +NOTE 2: Void + +NOTE 3: The protection of frequency range 23600-24000 MHz is meant for protection of satellite passive services. + +## 6.5.3.2 Additional spurious emissions + +### 6.5.3.2.1 General + +These requirements are specified in terms of an additional spectrum emission requirement. Additional spurious emission requirements are signalled by the network to indicate that the UE shall meet an additional requirement for a specific deployment scenario as part of the cell handover/broadcast message. + +### 6.5.3.2.2 Void + +**Table 6.5.3.2.2-1: (Void)** + +### 6.5.3.2.3 Additional spurious emission requirements for NS\_202 + +When "NS\_202" is indicated in the cell, the power of any UE emission shall not exceed the levels specified in Table 6.5.3.2.3-1. + +**Table 6.5.3.2.3-1: Additional requirements (NS\_202)** + +| Frequency Range | Maximum Level | Measurement bandwidth | NOTE | +|----------------------------------------------------------------------------------------------------|---------------|-----------------------|------| +| 7.25 GHz $\leq f \leq 2^{\text{nd}}$ harmonic of the upper frequency edge of the UL operating band | -10 dBm | 100 MHz | | +| 23.6 GHz $\leq f \leq 24.0$ GHz | +1 dBm | 200 MHz | 1 | + +NOTE 1: This requirement also applies for the frequency ranges that are less than $F_{\text{O0B}}$ (MHz) in Table 6.5.3-1 from the edge of the channel bandwidth. The protection of frequency range 23600 - 24000 MHz is meant for protection of satellite passive services. + +### 6.5.3.2.4 Additional spurious emission requirements for NS\_203 + +When "NS\_203" is indicated in the cell, the power of any UE emission shall not exceed the levels specified in Table 6.5.3.2.4-1. This requirement also applies for the frequency ranges that are less than $F_{\text{O0B}}$ (MHz) in Table 6.5.3-1 from the edge of the channel bandwidth. + +**Table 6.5.3.2.4-1: Additional requirements (NS\_203)** + +| Frequency band (GHz) | Spectrum emission limit (dBm) | Measurement bandwidth | +|-------------------------|-------------------------------|-----------------------| +| 23.6 $\leq f \leq 24.0$ | +1 | 200 MHz | + +### 6.5.3.2.5 Additional spurious emission requirements for NS\_204 + +When "NS\_204" is indicated in the cell, the power of any UE emission shall not exceed the levels specified in Table 6.5.3.2.5-1. This requirement also applies for the frequency ranges that are less than $F_{\text{O0B}}$ (MHz) in Table 6.5.3-1 from the edge of the channel bandwidth. + +**Table 6.5.3.2.5-1: Additional requirements (NS\_204)** + +| Frequency band (GHz) | Spectrum emission limit (dBm) | Measurement bandwidth | +|-----------------------------------------------------------------------------------------------------|-------------------------------|-----------------------| +| 12.75 GHz $\leq f \leq 2^{\text{nd}}$ harmonic of the upper frequency edge of the UL operating band | -10 dBm | 100 MHz | +| 87.5 MHz $\leq f \leq 118$ MHz | -54 dBm | 100 kHz | +| 174 MHz $\leq f \leq 230$ MHz | -54 dBm | 100 kHz | +| 470 MHz $\leq f \leq 694$ MHz | -54 dBm | 100 kHz | + +## 6.5A Output RF spectrum emissions for CA + +### 6.5A.1 Occupied bandwidth for CA + +#### 6.5A.1.0 General + +The occupied bandwidth for UL CA is defined as a directional requirement. The requirement is verified in beam locked mode on beam peak direction. In case the intra-band CA configuration consists of a single UL CC, the occupied bandwidth requirement defined in subclause 6.5.1 applies. + +#### 6.5A.1.1 Occupied bandwidth for intra-band contiguous UL CA + +For intra-band contiguous UL carrier aggregation, the occupied bandwidth is a measure of the bandwidth containing 99 % of the total integrated power of the transmitted spectrum. The occupied bandwidth for UL CA shall be less than the UL aggregated channel bandwidth defined in clause 5.3A. + +#### 6.5A.1.2 Occupied bandwidth for intra-band non-contiguous UL CA + +For intra-band non-contiguous UL carrier aggregation, the occupied bandwidth requirement is met when the ratio of the transmitted power in all sub-blocks of the UL CA configuration to the total integrated power of the transmitted spectrum is greater than 99%. + +#### 6.5A.1.3 Occupied bandwidth for inter-band UL CA + +For inter-band carrier aggregation with uplink assigned to two NR bands, and each UL band is configured with a single CC, the occupied bandwidth requirements is specified in clause 6.5.1 and is applicable for each CC with all CCs active with non-zero UL RB allocation. + +### 6.5A.2 Out of band emissions + +#### 6.5A.2.1 Spectrum emission mask for CA + +##### 6.5A.2.1.0 General + +For intra-band CA, the requirements specified in this clause shall apply if the UE has at least one of UL or DL configured for CA or if the UE is configured for single CC operation with different channel bandwidths in UL and DL carriers. In case the CA configuration consists of a single UL CC, spectrum emission mask defined in subclause 6.5.2.1 applies. Spectral emission mask requirements do not apply at any frequency where IBE requirements of clause 6.4A.2.3 apply. + +The requirement is verified in beam locked mode with the test metric of TRP (Link=TX beam peak direction). + +##### 6.5A.2.1.1 Spectrum emission mask for intra-band contiguous UL CA + +For intra-band contiguous UL carrier aggregation, the spectrum emission mask of the UE applies to frequencies ( $\Delta f_{\text{OOB}}$ ) starting from the $\pm$ edge of the UL aggregated channel bandwidth (Table 5.3A.4-1). For any bandwidth class defined in Table 5.3A.4-1, the UE emission shall not exceed the levels specified in Table 6.5A.2.1.1-1. + +**Table 6.5A.2.1.1-1: General NR spectrum emission mask for intra-band contiguous CA in FR2-1 and FR2-2** + +| $\Delta f_{\text{OOB}}$ (MHz) | Spectrum emission limit (dBm)/Any carrier aggregation bandwidth class | Measurement bandwidth | +|-----------------------------------------------------------------------------------------|-----------------------------------------------------------------------|-----------------------| +| $\pm 0-0.1 \cdot \text{BW}_{\text{Channel\_CA}}$ | -5 | 1 MHz | +| $\pm 0.1 \cdot \text{BW}_{\text{Channel\_CA}} - 2 \cdot \text{BW}_{\text{Channel\_CA}}$ | -13 | 1 MHz | +| NOTE 1: (void) | | | + +#### 6.5A.2.1.2 Spectrum emission mask for intra-band non-contiguous UL CA + +For intra-band non-contiguous UL carrier aggregation, the spectrum emission mask requirement is defined as a composite spectrum emissions mask. Composite spectrum emission mask applies to frequencies up to $\pm \Delta f_{\text{OOB}}$ starting from the edge of each UL sub-block. Composite spectrum emission mask is defined as follows: + +- Composite spectrum emission mask is a combination of individual spectrum emissions masks defined for each sub-block. If for some frequency, spectrum emission masks from multiple sub-blocks overlap, the spectrum emission mask allowing the highest power spectral density applies for that frequency +- In case a sub-block comprises of multiple component carriers, the spectrum emissions mask is defined in subclause 6.5A.2.1.1 or in case of a single component carrier, the sub-block spectrum emission mask is defined in subclause 6.5.2.1 +- If for some frequency the spectrum emission mask of one sub-block overlaps another sub-block, the emission mask does not apply for that frequency. +- If carrier leakage or I/Q image lands inside the spectrum occupied by the configured UL and DL CCs, exception to the general spectrum emission mask limit applies. For carrier leakage the requirements specified in section 6.4A.2.2 shall apply. For I/Q image the requirements specified in section 6.4A.2.3 shall apply. + +#### 6.5A.2.1.3 Spectrum emission mask for inter-band UL CA + +For inter-band carrier aggregation with uplink assigned to two NR bands, and each UL band is configured with a single CC, the spectrum emission mask is specified in Table 6.5.2.1-1 for each CC separately while both CCs are active with non-zero UL RB allocation. If for some frequency spectrum emission masks of CCs overlap, then spectrum emission mask allowing higher power spectral density applies for that frequency. If for some frequency a CC spectrum emission mask overlaps with the channel bandwidth of another CC, then the emission mask does not apply for that frequency. + +#### 6.5A.2.2 Void + +#### 6.5A.2.3 Adjacent channel leakage ratio for CA + +##### 6.5A.2.3.1 Adjacent channel leakage ratio for CA intra-band contiguous UL CA + +In case the CA configuration consists of a single UL CC, the adjacent channel leakage ratio defined in subclause 6.5.2.3 applies. For intra-band contiguous UL carrier aggregation, the carrier aggregation NR adjacent channel leakage power ratio (CA NRACLR) is the ratio of the filtered mean power centred on the UL aggregated channel bandwidth to the filtered mean power centred on an adjacent UL aggregated channel bandwidth at spacing equal to the UL aggregated channel bandwidth. The assigned UL aggregated channel bandwidth power and adjacent UL aggregated channel bandwidth power are measured with rectangular filters with measurement bandwidths specified in Table 6.5A.2.3.1-1. If the measured adjacent channel power is greater than -35 dBm then the CA NRACLR shall be higher than the value specified in Table 6.5A.2.3.1-1. + +**Table 6.5A.2.3.1-1: General requirements for contiguous UL CA NRACLR** + +| | CA bandwidth class / CA NR ACLR /
Measurement bandwidth | +|-------------------------------------------------------|-----------------------------------------------------------------------| +| | Any CA bandwidth class | +| CA NR ACLR for band n257, n258, n261 | 17 dB | +| CA NR ACLR for band n259, n260, n262 | 16 dB | +| CA NR ACLR for band n263 | 15 dB | +| NR channel measurement bandwidth 1 | BW Channel_CA - 2*BW GB | +| Adjacent channel centre frequency offset (in MHz) | + BW Channel_CA
/
- BW Channel_CA | +| NOTE 1: BW GB is defined in clause 5.3A.2. | | + +### 6.5A.2.3.2 Adjacent channel leakage ratio for CA intra-band non-contiguous UL CA + +For intra-band non-contiguous carrier aggregation, adjacent channel leakage power ratio (CA NRACLR) is the ratio of the sum of the filtered mean powers centred on each sub-block bandwidth to the filtered mean power centred on an adjacent sub-block frequency at nominal spacing equal to the sub-block bandwidth. The power in the configured UL CCs and power in the sub-block bandwidth adjacent to each sub-block of configured UL CCs are measured with rectangular filters with measurement bandwidths specified in Table 6.5A.2.3.1-2. In case a sub-block consists of a single component carrier, the measurement bandwidths and adjacent frequency offset from subclause 6.5.2.3 shall be used. If the measured adjacent sub-block power is greater than -35 dBm then the CA NRACLR shall be higher than the value specified in Table 6.5A.2.3.1-2. + +No requirement applies in the gap between neighbouring sub-blocks if the frequency span between the lowest edge of the upper sub-block and the highest edge of the lower sub-block is smaller than the bandwidth of either sub-block. + +**Table 6.5A.2.3.1-2: General requirements for NC UL CA NRACLR** + +| | CA bandwidth class / CA NR ACLR /
Measurement bandwidth | +|-----------------------------------------------------|-----------------------------------------------------------------------| +| | Any CA bandwidth class | +| CA NR ACLR for band n257, n258, n261 | 17 dB | +| CA NR ACLR for band n260 | 16 dB | +| CA NR ACLR for band n263 | 15 dB | +| NR channel measurement bandwidth 1 | $\Sigma(BW_{\text{Channel,block}})$ | +| Adjacent sub-block centre frequency offset (in MHz) | $+ BW_{\text{Channel,block}}$
$/$
$- BW_{\text{Channel,block}}$ | + +NOTE 1: BWChannel\_block is defined in clause 5.3A.2. +NOTE 2: 'Adjacent sub-block centre frequency offset' is defined for each sub-block in the UL CA configuration + +### 6.5A.2.3.3 Adjacent channel leakage ratio for CA inter-band UL CA + +For inter-band carrier aggregation with uplink assigned to two NR bands, and each UL band is configured with a single CC, the NR Adjacent Channel Leakage power Ratio (NRACLR) is applicable for each CC while both CCs are active with non-zero UL RB allocation and the requirement is specified in clause 6.5.2.3. + +## 6.5A.3 Spurious emissions for CA + +### 6.5A.3.0 General spurious emissions for CA + +#### 6.5A.3.0.0 General + +This clause specifies the spurious emission requirements for carrier aggregation. The requirement is verified in beam locked mode with the test metric of TRP (Link=TX beam peak direction). + +For intra-band CA, in case the CA configuration consists of a single UL CC, spurious emissions requirements defined in subclause 6.5.3 apply. Spurious emissions requirements do not apply at any frequency where IBE requirements of clause 6.4A.2.3 apply. + +NOTE: For measurement conditions at the edge of each frequency range, the lowest frequency of the measurement position in each frequency range should be set at the lowest boundary of the frequency range plus MBW/2. The highest frequency of the measurement position in each frequency range should be set at the highest boundary of the frequency range minus MBW/2. MBW denotes the measurement bandwidth defined for the protected band. + +#### 6.5A.3.0.1 Spurious emissions for intra-band contiguous UL CA + +For intra-band contiguous UL carrier aggregation, the spurious emission limits apply for the frequency ranges that are more than FOOB (MHz) from the edge of the UL aggregated channel bandwidth, where FOOB is defined as the twice the + +UL aggregated channel bandwidth. For frequencies $\Delta f_{\text{OOB}}$ greater than $F_{\text{OOB}}$ , the spurious emission requirements in Table 6.5.3-2 are applicable. + +#### 6.5A.3.0.2 Spurious emissions for intra-band non-contiguous UL CA + +For intra-band non-contiguous UL carrier aggregation, the spurious emission requirement is defined as a composite spurious emission requirement which is a combination of individual spurious emission requirements defined for each UL sub-block. The limits in Table 6.5.3-2 apply for the frequency ranges that are more than $F_{\text{OOB}}$ (MHz) from the edge of each UL sub-block but excludes frequency ranges that coincide with another UL sub-block. No spurious emission limit applies in the gap between neighbouring UL sub-blocks if the frequency span between the lowest edge of the upper sub-block and the highest edge of the lower sub-block is smaller than $F_{\text{OOB\_L}} + F_{\text{OOB\_H}}$ . + +#### 6.5A.3.0.3 Spurious emissions for inter-band UL CA + +For inter-band carrier aggregation with uplink assigned to two NR bands, and each UL band is configured with a single CC, the spurious emission requirements are specified in clause 6.5.3 and are applicable for each CC with all CCs active with non-zero UL RB allocation. + +#### 6.5A.3.1 Spurious emission band UE co-existence for UL CA + +This clause specifies the requirements for the specified contiguous or non-contiguous UL carrier aggregation configurations for coexistence with protected bands. + +NOTE: For measurement conditions at the edge of each frequency range, the lowest frequency of the measurement position in each frequency range should be set at the lowest boundary of the frequency range plus MBW/2. The highest frequency of the measurement position in each frequency range should be set at the highest boundary of the frequency range minus MBW/2. MBW denotes the measurement bandwidth defined for the protected band. + +For intra-band contiguous, non-contiguous carrier aggregation and inter-band carrier aggregation, the requirements in Table 6.5A.3-1 apply. + +**Table 6.5A.3.1-1: Requirements for CA** + +| CA operating band | Spurious emission | | | | | | +|-------------------|----------------------------------|-----------------------|---|----------------------|-----------|-------| +| | Protected band / frequency range | Frequency range (MHz) | | Maximum Level (dBm) | MBW (MHz) | NOTE | +| CA_n257 | NR Band n260 | F DL_low | - | F DL_high | -2 | 100 | +| | Frequency range | 57000 | - | 66000 | 2 | 100 | +| | Frequency range | 23600 | - | 24000 | 1 | 200 2 | +| CA_n258 | Frequency range | 57000 | - | 66000 | 2 | 100 | +| CA_n259 | NR Band 257 | F DL_low | - | F DL_high | -5 | 100 | +| | NR Band 261 | F DL_low | - | F DL_high | -5 | 100 | +| | Frequency range | 36000 | - | 37000 | 7 | 1000 | +| | Frequency range | 57000 | - | 66000 | 2 | 100 | +| CA_n260 | NR Band 257 | F DL_low | - | F DL_high | -5 | 100 | +| | NR Band 261 | F DL_low | - | F DL_high | -5 | 100 | +| | NR Band 262 | F DL_low | - | F DL_high | -5 | 100 | +| | Frequency range | 57000 | - | 66000 | 2 | 100 | +| CA_n261 | NR Band 260 | F DL_low | - | F DL_high | -2 | 100 | +| | NR Band 262 | F DL_low | - | F DL_high | -5 | 100 | +| | Frequency range | 57000 | - | 66000 | 2 | 100 | +| CA_n262 | NR Band 260 | F DL_low | - | F DL_high | -2 | 100 | +| | NR Band 261 | F DL_low | - | F DL_high | -5 | 100 | +| | Frequency range | 57000 | - | 66000 | 2 | 100 | +| CA_n257_n259 | NR Band n260 | F DL_low | - | F DL_high | -2 | 100 | +| | Frequency range | 57000 | - | 66000 | 2 | 100 | +| | Frequency range | 23600 | - | 24000 | 1 | 200 | +| | NR Band 257 | F DL_low | - | F DL_high | -5 | 100 | +| | NR Band 261 | F DL_low | - | F DL_high | -5 | 100 | +| CA_n260_n261 | NR Band 257 | F DL_low | - | F DL_high | -5 | 100 | +| | NR Band 262 | F DL_low | - | F DL_high | -5 | 100 | +| | Frequency range | 57000 | - | 66000 | 2 | 100 | + +NOTE 1: FDL\_low and FDL\_high refer to each NR frequency band specified in Table 5.2-1 + +NOTE 2: The protection of frequency range 23600-24000 MHz is meant for protection of satellite passive services. + +NOTE 3: Void + +### 6.5A.3.2 Additional spurious emissions + +#### 6.5A.3.2.1 General + +These requirements are specified in terms of an additional spectrum emission requirement. Additional spurious emission requirements are signalled by the network to indicate that the UE shall meet an additional requirement for a specific deployment scenario as part of the cell handover/broadcast message. + +#### 6.5A.3.2.2 Void + +#### 6.5A.3.2.3 Additional spurious emission requirements for CA\_NS\_202 + +When "CA\_NS\_202" is indicated in the cell, the power of any UE emission shall not exceed the levels specified in Table 6.5.3.2.3-1. + +#### 6.5A.3.2.4 Additional spurious emission requirements for CA\_NS\_203 + +When "CA\_NS\_203" is indicated in the cell, the power of any UE emission shall not exceed the levels specified in Table 6.5.3.2.4-1. This requirement also applies for the frequency ranges that are less than FOOB (MHz) as defined in section 6.5A.3. + +## 6.5D Output RF spectrum emissions for UL MIMO + +### 6.5D.1 Occupied bandwidth for UL MIMO + +For UE(s) supporting UL MIMO, the occupied bandwidth requirement in clause 6.5.1 apply. The requirements shall be met with the UL MIMO configurations specified in Table 6.2D.1.0-1. + +### 6.5D.2 Out of band emissions for UL MIMO + +For UE(s) supporting UL MIMO, the out of band emissions requirements in clause 6.5.2 apply. The requirements shall be met with the UL MIMO configurations specified in Table 6.2D.1.0-1. + +### 6.5D.3 Spurious emissions for UL MIMO + +For UE(s) supporting UL MIMO, the spurious emissions requirements in clause 6.5.3 apply. The requirements shall be met with the UL MIMO configurations specified in Table 6.2D.1.0-1. + +## 6.6 Beam correspondence + +### 6.6.1 General + +Beam correspondence is the ability of the UE to select a suitable beam for UL transmission based on DL measurements with or without relying on UL beam sweeping. Unless explicitly addressed in subclauses below, the beam correspondence requirement is fulfilled if the UE meets the corresponding minimum peak EIRP and spherical coverage requirement for that power class with its autonomously chosen UL beams and without uplink beam sweeping. + +### 6.6.2 (Void) + +### 6.6.3 (Void) + +### 6.6.4 Beam correspondence for power class 3 + +#### 6.6.4.1 General + +The beam correspondence requirement for power class 3 UEs in RRC\_CONNECTED consists of three components: UE minimum peak EIRP (as defined in Clause 6.2.1.3), UE spherical coverage (as defined in Clause 6.2.1.3), and beam correspondence tolerance (as defined in Clause 6.6.4.2). The beam correspondence requirement is fulfilled if the UE satisfies one of the following conditions, depending on the UE's beam correspondence capability IE *beamCorrespondenceWithoutUL-BeamSweeping*, as defined in TS 38.306 [14]: + +UEs supporting FR2-2 shall support *beamCorrespondenceWithoutUL-BeamSweeping*. + +- If *beamCorrespondenceWithoutUL-BeamSweeping* is supported, the UE shall meet the minimum peak EIRP requirement according to Table 6.2.1.3-1 and spherical coverage requirement according to Table 6.2.1.3-3 with its autonomously chosen UL beams and without uplink beam sweeping. Such a UE is considered to have met the beam correspondence tolerance requirement. +- If *beamCorrespondenceWithoutUL-BeamSweeping* and *beamCorrespondenceSSB-based-r16* are supported, the UE shall meet the minimum peak EIRP requirement according to Table 6.2.1.3-1 and spherical coverage requirement according to Table 6.2.1.3-3 using the side conditions for SSB based enhanced beam correspondence requirements as defined in Clause 6.6.4.3.2. +- If *beamCorrespondenceWithoutUL-BeamSweeping* and *beamCorrespondenceCSI-RS-based-r16* are supported, the UE shall meet the minimum peak EIRP requirement according to Table 6.2.1.3-1 and spherical coverage requirement according to Table 6.2.1.3-3 using the side conditions for CSI-RS based enhanced beam correspondence requirements as defined in Clause 6.6.4.3.3. + +- If *beamCorrespondenceWithoutUL-BeamSweeping* is not present, the UE shall meet the minimum peak EIRP requirement according to Table 6.2.1.3-1 and spherical coverage requirement according to Table 6.2.1.3-3 with uplink beam sweeping. Such a UE shall meet the beam correspondence tolerance requirement defined in Clause 6.6.4.2 and shall support uplink beam management, as defined in TS 38.306 [14]. +- If *beamCorrespondenceWithoutUL-BeamSweeping* is not present and *beamCorrespondenceSSB-based-r16* is supported, the UE shall meet the minimum peak EIRP requirement according to Table 6.2.1.3-1 and spherical coverage requirement according to Table 6.2.1.3-3 with uplink beam sweeping using the side conditions for SSB based enhanced beam correspondence requirements as defined in Clause 6.6.4.3.2. Such a UE shall meet the beam correspondence tolerance requirement defined in Clause 6.6.4.2 and shall support uplink beam management, as defined in TS 38.306 [14]. +- If *beamCorrespondenceWithoutUL-BeamSweeping* is not present and *beamCorrespondenceCSI-RS-based-r16* is supported, the UE shall meet the minimum peak EIRP requirement according to Table 6.2.1.3-1 and spherical coverage requirement according to Table 6.2.1.3-3 with uplink beam sweeping using the side conditions for CSI-RS based enhanced beam correspondence requirements as defined in Clause 6.6.4.3.3. Such a UE shall meet the beam correspondence tolerance requirement defined in Clause 6.6.4.2 and shall support uplink beam management, as defined in TS 38.306 [14]. + +The beam correspondence requirement for power class 3 UEs in initial access and in RRC\_INACTIVE consists of UE spherical coverage only: + +- UE shall meet the spherical coverage requirement for initial access and RRC\_INACTIVE according to Table 6.2.1.3-3, with its autonomously chosen UL beams and without uplink beam sweeping, using the side conditions for initial access and in RRC\_INACTIVE as defined in Clause 6.6.4.3.4. + +#### 6.6.4.2 Beam correspondence tolerance for power class 3 + +The beam correspondence tolerance requirement $\Delta\text{EIRP}_{\text{BC}}$ for power class 3 UEs is defined based on a percentile of the distribution of $\Delta\text{EIRP}_{\text{BC}}$ , defined as $\Delta\text{EIRP}_{\text{BC}} = \text{EIRP}_2 - \text{EIRP}_1$ over the link angles spanning a subset of the spherical coverage grid points, such that + +- $\text{EIRP}_1$ is the total EIRP in dBm calculated based on the beam the UE chooses autonomously (corresponding beam) to transmit in the direction of the incoming DL signal, which is based on beam correspondence without relying on UL beam sweeping. +- $\text{EIRP}_2$ is the best total EIRP (beam yielding highest EIRP in a given direction) in dBm which is based on beam correspondence with relying on UL beam sweeping. +- The link angles are the ones corresponding to the top $N^{\text{th}}$ percentile of the $\text{EIRP}_2$ measurement over the whole sphere, where the value of $N$ is according to the test point of EIRP spherical coverage requirement for power class 3, i.e. $N = 50$ . + +For power class 3 UEs, the requirement is fulfilled if the UE's corresponding UL beams satisfy the maximum limit in Table 6.6.4.2-1. + +**Table 6.6.4.2-1: UE beam correspondence tolerance for power class 3** + +| Operating band | Max $\Delta\text{EIRP}_{\text{BC}}$ at 85 th %-tile
$\Delta\text{EIRP}_{\text{BC}}$ CDF (dB) | +|----------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------| +| n257 | 3.0 | +| n258 | 3.0 | +| n259 | 3.2 | +| n260 | 3.2 | +| n261 | 3.0 | +| n262 | 3.2 | +| NOTE: The requirements in this table are verified only under normal temperature conditions as defined in Annex E.2.1 | | + +### 6.6.4.3 Side Conditions + +#### 6.6.4.3.1 Side Condition for beam correspondence based on SSB and CSI-RS + +The beam correspondence requirements are only applied under the following side conditions: + +- The downlink reference signals including both SSB and CSI-RS are provided and Type D QCL shall be maintained between SSB and CSI-RS. +- The reference measurement channel for beam correspondence are fulfilled according to the CSI-RS configuration in Annex A.3. +- For beam correspondence, conditions for L1-RSRP measurements are fulfilled according to Table 6.6.4.3.1-1 and Table 6.6.4.3.1-2. + +**Table 6.6.4.3.1-1: Conditions for SSB based L1-RSRP measurements for beam correspondence** + +| Angle of arrival | NR operating bands | Minimum SSB_RP Note 2 | SSB Ês/lot | +|------------------------------|--------------------|----------------------------------|------------| +| | | dBm / SCS SSB | dB | +| | | SCS SSB = 120 kHz | | +| All angles Note 1 | n257 | -96.2 | ≥6 | +| | n258 | -96.2 | | +| | n259 | -90.7 | | +| | n260 | -91.9 | | +| | n261 | -96.2 | | +| | n262 | -88.5 | | +| | n263 | -88.0 | | + +NOTE 1: For UEs that support multiple FR2 bands, the Minimum SSB\_RP values for all angles are increased by $\Delta MB_{S,n}$ , the UE multi-band relaxation factor in dB specified in clause 6.2.1. + +NOTE 2: Values specified at the radiated requirements reference point to give minimum SSB Ês/lot, with no applied noise. + +**Table 6.6.4.3.1-2: Conditions for CSI-RS based L1-RSRP measurements for beam correspondence** + +| Angle of arrival | NR operating bands | Minimum CSI-RS_RP Note 2 | CSI-RS Ês/lot | +|------------------------------|--------------------|-------------------------------------|---------------| +| | | dBm / SCS CSI-RS | dB | +| | | SCS CSI-RS = 120 kHz | | +| All angles Note 1 | n257 | -96.2 | ≥6 | +| | n258 | -96.2 | | +| | n259 | -90.7 | | +| | n260 | -91.9 | | +| | n261 | -96.2 | | +| | n262 | -88.5 | | +| | n263 | -88.0 | | + +NOTE 1: For UEs that support multiple FR2 bands, the Minimum SSB\_RP values for all angles are increased by $\Delta MB_{S,n}$ , the UE multi-band relaxation factor in dB specified in clause 6.2.1. + +NOTE 2: Values specified at the radiated requirements reference point to give minimum CSI-RS Ês/lot, with no applied noise. + +#### 6.6.4.3.2 Side Condition for SSB based enhanced Beam Correspondence requirements + +The beam correspondence requirements for beam correspondence based on SSB are only applied under the following side conditions: + +- The downlink reference signal SSB is provided, and CSI-RS is not provided. +- For beam correspondence, conditions for L1-RSRP measurements are fulfilled according to Table 6.6.4.3.1-1. + +### 6.6.4.3.3 Side Condition for CSI-RS based enhanced Beam Correspondence requirements + +The beam correspondence requirements for beam correspondence based on CSI-RS are only applied under the following side conditions: + +- The downlink reference signals including both SSB and CSI-RS are provided. +- The reference measurement channel for beam correspondence is fulfilled according to the CSI-RS configuration in Annex A.3. +- For beam correspondence, conditions for L1-RSRP measurements are fulfilled according to Table 6.6.4.3.1-2 and SSB signal is provided according to Table 6.6.4.3.3-1. + +**Table 6.6.4.3.3-1: SSB signal conditions for CSI-RS based beam correspondence requirements** + +| Angle of arrival | NR operating bands | Minimum SSB_RP Note 2 | SSB Ês/lot | +|------------------------------|--------------------|----------------------------------|------------| +| | | dBm / SCS SSB | dB | +| | | SCS SSB = 120 kHz | | +| All angles Note 1 | n257 | -101,2 | ≥1 | +| | n258 | -101,2 | | +| | n259 | -95.7 | | +| | n260 | -96.9 | | +| | n261 | -101.2 | | +| | n262 | -93,5 | | + +NOTE 1: For UEs that support multiple FR2 bands, the Minimum SSB\_RP values for all angles are increased by $\Delta MB_{s,n}$ , the UE multi-band relaxation factor in dB specified in clause 6.2.1. + +NOTE 2: Values specified at the radiated requirements reference point to give minimum SSB Ês/lot, with no applied noise. + +### 6.6.4.3.4 Side Condition for Beam Correspondence requirements in initial access and RRC\_INACTIVE + +The beam correspondence requirements for beam correspondence in initial access and RRC\_INACTIVE are only applied under side conditions in Clause 6.6.4.3.2. + +### 6.6.4.4 Applicability + +For UEs supporting more than one type of beam correspondence in RRC\_CONNECTED, the following applicability rules apply: + +- If a UE meets enhanced beam correspondence requirements either based on SSB or based on CSI-RS, it is considered to have met the beam correspondence requirements based on SSB and CSI-RS. +- For a UE supporting either SSB based or CSI-RS based enhanced beam correspondence, the UE shall meet the supported enhanced beam correspondence requirements. +- For a UE supporting both SSB based and CSI-RS based enhanced beam correspondence, the UE shall meet both SSB based and CSI-RS based enhanced beam correspondence requirements and the following applicability rules for verifying the requirements apply: + - The enhanced beam correspondence requirements shall be verified with the SSB based enhanced beam correspondence side conditions in clause 6.6.4.3.2. If the UE meets the SSB based enhanced beam correspondence requirements using the side conditions in clause 6.6.4.3.2 and meets the minimum peak EIRP requirement as defined in clause 6.2.1.3 using the CSI-RS based side conditions in clause 6.6.4.3.3, where the link direction is determined in the SSB based enhanced beam correspondence test, the UE is considered to have met both the SSB based and CSI-RS based enhanced beam correspondence requirements. + - Otherwise, if UE does not meet the minimum peak EIRP requirement as defined in clause 6.2.1.3 using the CSI-RS based side conditions in clause 6.6.4.3.3, the enhanced beam correspondence requirements shall be + +further verified for the UE with the CSI-RS based enhanced beam correspondence side conditions in clause 6.6.4.3.3. + +For the beam correspondence requirement for power class 3 UEs in initial access and in RRC\_INACTIVE, the following applicability rules apply: + +- If a UE meets beam correspondence requirements in initial access, it is considered to have met the beam correspondence requirements in RRC\_INACTIVE. + +## 6.6.5 (Void) + +## 6.6.6 Beam correspondence for power class 5 + +### 6.6.6.1 General + +The beam correspondence requirement for power class 5 UEs consists of two components: UE minimum peak EIRP (as defined in Clause 6.2.1.5), and UE spherical coverage (as defined in Clause 6.2.1.5). The beam correspondence requirement is fulfilled if the UE satisfies one of the following conditions, depending on the UE's beam correspondence capability IE *beamCorrespondenceWithoutUL-BeamSweeping*, as defined in TS 38.306 [14]: + +- If *beamCorrespondenceWithoutUL-BeamSweeping* is supported, the UE shall meet the minimum peak EIRP requirement according to Table 6.2.1.5-1 and spherical coverage requirement according to Table 6.2.1.5-3 with its autonomously chosen UL beams and without uplink beam sweeping. Such a UE is considered to have met the beam correspondence tolerance requirement. +- If *beamCorrespondenceWithoutUL-BeamSweeping* and *beamCorrespondenceSSB-based-r16* are supported, the UE shall meet the minimum peak EIRP requirement according to Table 6.2.1.5-1 and spherical coverage requirement according to Table 6.2.1.5-3 using the side conditions for SSB based enhanced beam correspondence requirements as defined in Clause 6.6.6.3.2. +- If *beamCorrespondenceWithoutUL-BeamSweeping* and *beamCorrespondenceCSI-RS-based-r16* are supported, the UE shall meet the minimum peak EIRP requirement according to Table 6.2.1.5-1 and spherical coverage requirement according to Table 6.2.1.5-3 using the side conditions for CSI-RS based enhanced beam correspondence requirements as defined in Clause 6.6.6.3.3. + +### 6.6.6.2 (Reserved) + +*Editor's note: FFS if power class 5 UE can rely on UL beam sweeping to meet min peak EIRP and spherical requirements.* + +### 6.6.6.3 Side Conditions + +#### 6.6.6.3.1 Side Condition for beam correspondence based on SSB and CSI-RS + +The beam correspondence requirements are only applied under the following side conditions: + +- The downlink reference signals including both SSB and CSI-RS are provided and Type D QCL shall be maintained between SSB and CSI-RS. +- The reference measurement channel for beam correspondence is fulfilled according to the CSI-RS configuration in Annex A.3. +- For beam correspondence, conditions for L1-RSRP measurements are fulfilled according to Table 6.6.6.3.1-1 and Table 6.6.6.3.1-2. + +**Table 6.6.6.3.1-1: Conditions for SSB based L1-RSRP measurements for beam correspondence** + +| Angle of arrival | NR operating bands | Minimum SSB_RP Note 2 | SSB Ês/lot | +|------------------------------|--------------------|----------------------------------|------------| +| | | dBm / SCS SSB | dB | +| | | SCS SSB = 120 kHz | | +| All angles Note 1 | n257 | -103.6 | ≥6 | +| | n258 | -103.6 | | +| | n259 | -100.5 | | + +NOTE 1: For UEs that support multiple FR2 bands, the Minimum SSB\_RP values for all angles are increased by ΔMBs, the UE multi-band relaxation factor in dB specified in clause 6.2.1.5 + +NOTE 2: Values specified at the radiated requirements reference point to give minimum SSB Ês/lot, with no applied noise. + +**Table 6.6.6.3.1-2: Conditions for CSI-RS based L1-RSRP measurements for beam correspondence** + +| Angle of arrival | NR operating bands | Minimum CSI-RS_RP Note 2 | CSI-RS Ês/lot | +|------------------------------|--------------------|-------------------------------------|---------------| +| | | dBm / SCS CSI-RS | dB | +| | | SCS CSI-RS = 120 kHz | | +| All angles Note 1 | n257 | -103.6 | ≥6 | +| | n258 | -103.6 | | +| | n259 | -100.5 | | + +NOTE 1: For UEs that support multiple FR2 bands, the Minimum CSI-RS\_RP values are increased by ΔMBs, the UE multi-band relaxation factor in dB specified in clause 6.2.1.5 + +NOTE 2: Values specified at the radiated requirements reference point to give minimum CSI-RS Ês/lot, with no applied noise. + +### 6.6.6.3.2 Side Condition for SSB based enhanced Beam Correspondence requirements + +The beam correspondence requirements for beam correspondence based on SSB are only applied under the following side conditions: + +- The downlink reference signal SSB is provided, and CSI-RS is not provided. +- For beam correspondence, conditions for L1-RSRP measurements are fulfilled according to Table 6.6.6.3.1-1. + +### 6.6.6.3.3 Side Condition for CSI-RS based enhanced Beam Correspondence requirements + +The beam correspondence requirements for beam correspondence based on CSI-RS are only applied under the following side conditions: + +- The downlink reference signals including both SSB and CSI-RS are provided. +- The reference measurement channel for beam correspondence is fulfilled according to the CSI-RS configuration in Annex A.3. +- For beam correspondence, conditions for L1-RSRP measurements are fulfilled according to Table 6.6.4.3.1-2 and SSB signal is provided according to Table 6.6.6.3.1-1. + +**Table 6.6.6.3.3-1: SSB signal conditions for CSI-RS based beam correspondence requirements** + +| Angle of arrival | NR operating bands | Minimum SSB_RP Note 2 | SSB Ês/lot | +|---------------------------------|--------------------|----------------------------------|------------| +| | | dBm / SCS SSB | dB | +| | | SCS SSB = 120 kHz | | +| All angles
Note 1 | n257 | -108.6 | ≥1 | +| | n258 | -108.6 | | +| | n259 | -105.5 | | + +NOTE 1: For UEs that support multiple FR2 bands, the Minimum SSB\_RP values for all angles are increased by ΔMBs, the UE multi-band relaxation factor in dB specified in clause 6.2.1.5 + +NOTE 2: Values specified at the radiated requirements reference point to give minimum SSB Ês/lot, with no applied noise. + +### 6.6.6.4 Applicability + +For UEs supporting more than one type of beam correspondence, the following applicability rules apply: + +- If a UE meets enhanced beam correspondence requirements either based on SSB or based on CSI-RS, it is considered to have met the beam correspondence requirements based on SSB and CSI-RS. +- For a UE supporting either SSB based or CSI-RS based enhanced beam correspondence, the UE shall meet the supported enhanced beam correspondence requirements. +- For a UE supporting both SSB based and CSI-RS based enhanced beam correspondence, the UE shall meet both SSB based and CSI-RS based enhanced beam correspondence requirements and the following applicability rules for verifying the requirements apply: + - The enhanced beam correspondence requirements shall be verified with the SSB based enhanced beam correspondence side conditions in clause 6.6.6.3.2. If UE meets the SSB based enhanced beam correspondence requirements using the side conditions in clause 6.6.6.3.2 and meets the minimum peak EIRP requirement as defined in clause 6.2.1.5 using the CSI-RS based side conditions in clause 6.6.6.3.3, where the link direction is determined in the SSB based enhanced beam correspondence test, the UE is considered to have met both the SSB based and CSI-RS based enhanced beam correspondence requirements. + - Otherwise, if UE does not meet the minimum peak EIRP requirement as defined in clause 6.2.1.3 using the CSI-RS based side conditions in clause 6.6.6.3.3, the enhanced beam correspondence requirements shall be further verified for the UE with the CSI-RS based enhanced beam correspondence side conditions in clause 6.6.6.3.3. + +## 6.6.7 Beam correspondence for power class 6 + +### 6.6.7.1 General + +The beam correspondence requirement for power class 6 UEs consists of two components: UE minimum peak EIRP (as defined in Clause 6.2.1.6), and UE spherical coverage (as defined in Clause 6.2.1.6). + +Power class 6 UE shall mandatorily support *beamCorrespondenceWithoutUL-BeamSweeping* and *beamCorrespondenceSSB-based-r16*. The UE shall meet the minimum peak EIRP requirement according to Table 6.2.1.6-1 and spherical coverage requirement according to Table 6.2.1.6-3 using the side conditions for SSB based enhanced beam correspondence requirements as defined in Clause 6.6.7.3.2. + +If the UE also support *beamCorrespondenceCSI-RS-based-r16*, the UE shall also meet the minimum peak EIRP requirement according to Table 6.2.1.6-1 and spherical coverage requirement according to Table 6.2.1.6-3 using the side conditions for CSI-RS based enhanced beam correspondence requirements as defined in Clause 6.6.7.3.3. + +### 6.6.7.2 (Void) + +*Editor's note: Not need to define beam correspondence tolerance requirement because power class 6 UE shall mandatorily support beamCorrespondenceWithoutUL-BeamSweeping.* + +### 6.6.7.3 Side Conditions + +#### 6.6.7.3.1 (Void) + +*Editor's note: Not need to define the side condition for beam correspondence based on SSB and CSI-RS, because power class 6 UE shall mandatorily support SSB based enhanced beam correspondence.* + +#### 6.6.7.3.2 Side Condition for SSB based enhanced Beam Correspondence requirements + +The beam correspondence requirements for beam correspondence based on SSB are only applied under the following side conditions: + +- The downlink reference signal SSB is provided, and CSI-RS is not provided. +- For beam correspondence, conditions for L1-RSRP measurements are fulfilled according to Table 6.6.7.3.2-1. + +**Table 6.6.7.3.2-1: Conditions for SSB based L1-RSRP measurements for beam correspondence** + +| Angle of arrival | NR operating bands | Minimum SSB_RP Note 2 | SSB Ês/lot | +|------------------------------|--------------------|----------------------------------|------------| +| | | dBm / SCS SSB | dB | +| | | SCS SSB = 120 kHz | | +| All angles Note 1 | n257 | -101.4 | ≥6 | +| | n258 | -101.6 | | +| | n261 | -101.4 | | + +NOTE 1: For UEs that support multiple FR2 bands, the Minimum SSB\_RP values for all angles are increased by ΔMBs,n, the UE multi-band relaxation factor in dB specified in clause 6.2.1.6. + +NOTE 2: Values specified at the radiated requirements reference point to give minimum SSB Ês/lot, with no applied noise. + +#### 6.6.7.3.3 Side Condition for CSI-RS based enhanced Beam Correspondence requirements + +The beam correspondence requirements for beam correspondence based on CSI-RS are only applied under the following side conditions: + +- The downlink reference signals including both SSB and CSI-RS are provided. +- The reference measurement channel for beam correspondence is fulfilled according to the CSI-RS configuration in Annex A.3. +- For beam correspondence, conditions for L1-RSRP measurements are fulfilled according to Table 6.6.7.3.3-2 and SSB signal is provided according to Table 6.6.7.3.3-1. + +**Table 6.6.7.3.3-1: SSB signal conditions for CSI-RS based beam correspondence requirements** + +| Angle of arrival | NR operating bands | Minimum SSB_RP Note 2 | SSB Ês/lot | +|------------------------------|--------------------|----------------------------------|------------| +| | | dBm / SCS SSB | dB | +| | | SCS SSB = 120 kHz | | +| All angles Note 1 | n257 | -106.4 | ≥1 | +| | n258 | -106.6 | | +| | n261 | -106.4 | | + +NOTE 1: For UEs that support multiple FR2 bands, the Minimum SSB\_RP values for all angles are increased by ΔMBs,n, the UE multi-band relaxation factor in dB specified in clause 6.2.1.6. + +NOTE 2: Values specified at the radiated requirements reference point to give minimum SSB Ês/lot, with no applied noise. + +**Table 6.6.7.3.3-2: Conditions for CSI-RS based L1-RSRP measurements for beam correspondence** + +| Angle of arrival | NR operating bands | Minimum CSI-RS_RP Note 2 | CSI-RS Ês/lot | +|---------------------------------|--------------------|-------------------------------------|---------------| +| | | dBm / SCS CSI-RS | dB | +| | | SCS CSI-RS = 120 kHz | | +| All angles
Note 1 | n257 | -101.4 | ≥6 | +| | n258 | -101.6 | | +| | n261 | -101.4 | | + +NOTE 1: For UEs that support multiple FR2 bands, the Minimum CSI-RS\_RP values are increased by $\Delta\text{MB}_{\text{s,n}}$ , the UE multi-band relaxation factor in dB specified in clause 6.2.1.6 + +NOTE 2: Values specified at the radiated requirements reference point to give minimum CSI-RS Ês/lot, with no applied noise. + +## 6.6.7.4 Applicability + +For UEs supporting more than one type of beam correspondence, the following applicability rules apply: + +- If a UE meets enhanced beam correspondence requirements either based on SSB or based on CSI-RS, it is considered to have met the beam correspondence requirements based on SSB and CSI-RS. +- For a UE supporting either SSB based or CSI-RS based enhanced beam correspondence, the UE shall meet the supported enhanced beam correspondence requirements. +- For a UE supporting both SSB based and CSI-RS based enhanced beam correspondence UE shall meet the both SSB based and CSI-RS based enhanced beam correspondence requirements and the following applicability rules for verifying the requirements apply: + - The enhanced beam correspondence requirements shall be verified with the SSB based enhanced beam correspondence side conditions in clause 6.6.7.3.2. If the UE meets the SSB based enhanced beam correspondence requirements using the side conditions in clause 6.6.7.3.2 and meets the minimum peak EIRP requirement as defined in clause 6.2.1.6 using the CSI-RS based side conditions in clause 6.6.7.3.3, where the link direction is determined in the SSB based enhanced beam correspondence test, the UE is considered to have met both the SSB based and CSI-RS based enhanced beam correspondence requirements. + - Otherwise, if UE does not meet the minimum peak EIRP requirement as defined in clause 6.2.1.6 using the CSI-RS based side conditions in clause 6.6.7.3.3, the enhanced beam correspondence requirements shall be further verified for the UE with the CSI-RS based enhanced beam correspondence side conditions in clause 6.6.7.3.3. + +## 6.6.8 Beam correspondence for power class 7 + +### 6.6.8.1 General + +The beam correspondence requirement for power class 7 UEs consists of two components: UE minimum peak EIRP (as defined in Clause 6.2.1.7), and UE spherical coverage (as defined in Clause 6.2.1.7). The beam correspondence requirement is fulfilled if the UE satisfies one of the following conditions, depending on the UE's beam correspondence capability IE *beamCorrespondenceWithoutUL-BeamSweeping*, as defined in TS 38.306 [14]: + +- If *beamCorrespondenceWithoutUL-BeamSweeping* is supported, the UE shall meet the minimum peak EIRP requirement according to Table 6.2.1.7-1 and spherical coverage requirement according to Table 6.2.1.7-3 with its autonomously chosen UL beams and without uplink beam sweeping. Such a UE is considered to have met the beam correspondence tolerance requirement. +- If *beamCorrespondenceWithoutUL-BeamSweeping* and *beamCorrespondenceSSB-based-r16* are supported, the UE shall meet the minimum peak EIRP requirement according to Table 6.2.1.7-1 and spherical coverage requirement according to Table 6.2.1.7-3 using the side conditions for SSB based enhanced beam correspondence requirements as defined in Clause 6.6.8.3.2. + +- If *beamCorrespondenceWithoutUL-BeamSweeping* and *beamCorrespondenceCSI-RS-based-r16* are supported, the UE shall meet the minimum peak EIRP requirement according to Table 6.2.1.7-1 and spherical coverage requirement according to Table 6.2.1.7-3 using the side conditions for CSI-RS based enhanced beam correspondence requirements as defined in Clause 6.6.8.3.3. + +## 6.6.8.2 Void + +## 6.6.8.3 Side Conditions + +### 6.6.8.3.1 Side Condition for beam correspondence based on SSB and CSI-RS + +The beam correspondence requirements are only applied under the following side conditions: + +- The downlink reference signals including both SSB and CSI-RS are provided and Type D QCL shall be maintained between SSB and CSI-RS. +- The reference measurement channel for beam correspondence is fulfilled according to the CSI-RS configuration in Annex A.3. +- For beam correspondence, conditions for L1-RSRP measurements are fulfilled according to Table 6.6.8.3.1-1 and Table 6.6.8.3.1-2. + +**Table 6.6.8.3.1-1: Conditions for SSB based L1-RSRP measurements for beam correspondence** + +| Angle of arrival | NR operating bands | Minimum SSB_RP Note 2 | SSB Ês/lot | +|------------------------------|--------------------|----------------------------------|------------| +| | | dBm / SCS SSB | dB | +| | | SCS SSB = 120 kHz | | +| All angles Note 1 | n257 | -93.2 | ≥6 | +| | n258 | -93.2 | | +| | n261 | -93.2 | | + +NOTE 1: Void +NOTE 2: Values specified at the radiated requirements reference point to give minimum SSB Ês/lot, with no applied noise. + +**Table 6.6.8.3.1-2: Conditions for CSI-RS based L1-RSRP measurements for beam correspondence** + +| Angle of arrival | NR operating bands | Minimum CSI-RS_RP Note 2 | CSI-RS Ês/lot | +|------------------------------|--------------------|-------------------------------------|---------------| +| | | dBm / SCS CSI-RS | dB | +| | | SCS CSI-RS = 120 kHz | | +| All angles Note 1 | n257 | -93.2 | ≥6 | +| | n258 | -93.2 | | +| | n261 | -93.2 | | + +NOTE 1: For UEs that support multiple FR2 bands, the Minimum SSB\_RP values for all angles are increased by $\Delta MB_{s,n}$ , the UE multi-band relaxation factor in dB specified in clause 6.2.1. +NOTE 2: Values specified at the radiated requirements reference point to give minimum CSI-RS Ês/lot, with no applied noise. + +### 6.6.8.3.2 Side Condition for SSB based enhanced Beam Correspondence requirements + +The beam correspondence requirements for beam correspondence based on SSB are only applied under the following side conditions: + +- The downlink reference signal SSB is provided, and CSI-RS is not provided. +- For beam correspondence, conditions for L1-RSRP measurements are fulfilled according to Table 6.6.8.3.1-1. + +### 6.6.8.3.3 Side Condition for CSI-RS based enhanced Beam Correspondence requirements + +The beam correspondence requirements for beam correspondence based on CSI-RS are only applied under the following side conditions: + +- The downlink reference signals including both SSB and CSI-RS are provided. +- The reference measurement channel for beam correspondence is fulfilled according to the CSI-RS configuration in Annex A.3. +- For beam correspondence, conditions for L1-RSRP measurements are fulfilled according to Table 6.6.8.3.1-2 and SSB signal is provided according to Table 6.6.8.3.3-1. + +**Table 6.6.8.3.3-1: SSB signal conditions for CSI-RS based beam correspondence requirements** + +| Angle of arrival | NR operating bands | Minimum SSB_RP Note 2 | SSB Ês/lot | +|-------------------------------------|--------------------|----------------------------------|------------| +| | | dBm / SCS SSB | dB | +| | | SCS SSB = 120 kHz | | +| All angles
Note 1 | n257 | -98.2 | ≥1 | +| | n258 | -98.2 | | +| | n261 | -98.2 | | + +NOTE 1: For UEs that support multiple FR2 bands, the Minimum SSB\_RP values for all angles are increased by $\Delta MB_{S,n}$ , the UE multi-band relaxation factor in dB specified in clause 6.2.1. + +NOTE 2: Values specified at the radiated requirements reference point to give minimum SSB Ês/lot, with no applied noise. + +### 6.6.8.4 Applicability + +For UEs supporting more than one type of beam correspondence, the following applicability rules apply: + +- If a UE meets enhanced beam correspondence requirements either based on SSB or based on CSI-RS, it is considered to have met the beam correspondence requirements based on SSB and CSI-RS. +- For a UE supporting either SSB based or CSI-RS based enhanced beam correspondence, the UE shall meet the supported enhanced beam correspondence requirements. +- For a UE supporting both SSB based and CSI-RS based enhanced beam correspondence, the UE shall meet both SSB based and CSI-RS based enhanced beam correspondence requirements and the following applicability rules for verifying the requirements apply: + - The enhanced beam correspondence requirements shall be verified with the SSB based enhanced beam correspondence side conditions in clause 6.6.8.3.2. If UE meets the SSB based enhanced beam correspondence requirements using the side conditions in clause 6.6.8.3.2 and meets the minimum peak EIRP requirement as defined in clause 6.2.1.7 using the CSI-RS based side conditions in clause 6.6.8.3.3, where the link direction is determined in the SSB based enhanced beam correspondence test, the UE is considered to have met both the SSB based and CSI-RS based enhanced beam correspondence requirements. + - Otherwise, if UE does not meet the minimum peak EIRP requirement as defined in clause 6.2.1.7 using the CSI-RS based side conditions in clause 6.6.8.3.3, the enhanced beam correspondence requirements shall be further verified for the UE with the CSI-RS based enhanced beam correspondence side conditions in clause 6.6.8.3.3. + +## 6.6A Beam correspondence for CA + +For intra-band CA in FR2, the same beam correspondence relationship for beam management is supported across CCs in this release of the specification and no requirement is specified. Beam correspondence performance for intra-band CA is fulfilled if the beam correspondence requirements defined in clause 6.6 is met for non-CA case. + +For inter-band carrier aggregation with uplink assigned to two NR bands, and each UL band is configured with a single CC, with all CCs active with non-zero UL RB allocation, the following beam correspondence requirements apply for each CC: + +- 1 The minimum peak EIRP requirement specified for UL inter-band CA in 6.2A, based on test conditions in clause 6.6. Reference signal power adjustments by $\Delta MB_{s,n}$ are replaced by $\Delta R_{IB,s,n}$ , where referenced. +- 2 The common spherical coverage requirement specified for UL inter-band CA in 6.2A, based on test conditions in clause 6.6. Reference signal power adjustments by $\Delta MB_{s,n}$ are replaced by $\Delta R_{IB,s,n}$ , where referenced. + +## 7 Receiver characteristics + +### 7.1 General + +Unless otherwise stated, the receiver characteristics are specified over the air (OTA). The reference receive sensitivity (REFSENS) is defined assuming a 0 dBi reference antenna located at the center of the quiet zone. + +### 7.2 Diversity characteristics + +The minimum requirements on effective isotropic sensitivity (EIS) apply to two measurements, corresponding to DL signals in orthogonal polarizations. + +### 7.3 Reference sensitivity + +#### 7.3.1 General + +The reference sensitivity power level REFSENS is defined as the EIS level at the centre of the quiet zone in the RX beam peak direction, at which the throughput shall meet or exceed the requirements for the specified reference measurement channel. + +#### 7.3.2 Reference sensitivity power level + +##### 7.3.2.1 Reference sensitivity power level for power class 1 + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in Annexes A.2.3.2 and A.3.3.2 (with one sided dynamic OCGN Pattern OP.1 TDD for the DL-signal as described in Annex A.5.2.1) with peak reference sensitivity specified in Table 7.3.2.1-1. The requirement is verified with the test metric of EIS (Link=RX beam peak direction, Meas=Link Angle). + +**Table 7.3.2.1-1: Reference sensitivity for power class 1** + +| Operating band | REFSENS (dBm) / Channel bandwidth | | | | | | | +|--------------------------------------------------------------------------------------|-----------------------------------|---------|---------|---------|---------|----------|----------| +| | 50 MHz | 100 MHz | 200 MHz | 400 MHz | 800 MHz | 1600 MHz | 2000 MHz | +| n257 | -97.5 | -94.5 | -91.5 | -88.5 | N/A | N/A | N/A | +| n258 | -97.5 | -94.5 | -91.5 | -88.5 | N/A | N/A | N/A | +| n260 | -94.5 | -91.5 | -88.5 | -85.5 | N/A | N/A | N/A | +| n261 | -97.5 | -94.5 | -91.5 | -88.5 | N/A | N/A | N/A | +| n262 | -92.5 | -89.5 | -86.5 | -83.5 | N/A | N/A | N/A | +| n263 | N/A | -85 | N/A | -79 | -76 | -73 | -72 | +| NOTE 1: The transmitter shall be set to $P_{\text{UMAX}}$ as defined in clause 6.2.4 | | | | | | | | + +The REFSENS requirement shall be met for an uplink transmission using QPSK DFT-s-OFDM waveforms and for uplink transmission bandwidth less than or equal to that specified in Table 7.3.2.1-2. + +**Table 7.3.2.1-2: Uplink configuration for reference sensitivity** + +| Operating band | NR Band / Channel bandwidth / NRB / SCS / Duplex mode | | | | | | | SCS | Duplex mode | +|----------------|-------------------------------------------------------|---------|---------|---------|---------|----------|----------|---------|-------------| +| | 50 MHz | 100 MHz | 200 MHz | 400 MHz | 800 MHz | 1600 MHz | 2000 MHz | | | +| n257 | 32 | 64 | 128 | 256 | N/A | N/A | N/A | 120 kHz | TDD | +| n258 | 32 | 64 | 128 | 256 | N/A | N/A | N/A | 120 kHz | TDD | +| n260 | 32 | 64 | 128 | 256 | N/A | N/A | N/A | 120 kHz | TDD | +| n261 | 32 | 64 | 128 | 256 | N/A | N/A | N/A | 120 kHz | TDD | +| n262 | 32 | 64 | 128 | 256 | N/A | N/A | N/A | 120 kHz | TDD | +| n263 | N/A | 64 | N/A | 256 | N/A | N/A | N/A | 120 kHz | TDD | +| | N/A | N/A | N/A | 64 | 120 | 240 | N/A | 480 kHz | | +| | N/A | N/A | N/A | 32 | 60 | 120 | 144 | 960 kHz | | + +Unless given by Table 7.3.2.1-3, the minimum requirements for reference sensitivity shall be verified with the network signalling value NS\_200 (Table 6.2.3-1) configured. + +**Table 7.3.2.1-3: Reserved** + +| Operating band | Network Signalling value | +|----------------|--------------------------| +| | | + +### 7.3.2.2 Reference sensitivity power level for power class 2 + +The throughput shall be $\geq 95$ % of the maximum throughput of the reference measurement channels as specified in Annexes A.2.3.2 and A.3.3.2 (with one sided dynamic OCNG Pattern OP.1 TDD for the DL-signal as described in Annex A.5.2.1) with peak reference sensitivity specified in Table 7.3.2.2-1. The requirement is verified with the test metric of EIS (Link=RX beam peak direction, Meas=Link Angle). + +**Table 7.3.2.2-1: Reference sensitivity for power class 2** + +| Operating band | REFSENS (dBm) / Channel bandwidth | | | | | | | +|----------------|-----------------------------------|---------|---------|---------|---------|----------|----------| +| | 50 MHz | 100 MHz | 200 MHz | 400 MHz | 800 MHz | 1600 MHz | 2000 MHz | +| n257 | -92.0 | -89.0 | -86.0 | -83.0 | N.A | N.A | N.A | +| n258 | -92.0 | -89.0 | -86.0 | -83.0 | N.A | N.A | N.A | +| n259 | -88.7 | -85.7 | -82.7 | -79.7 | N.A | N.A | N.A | +| n261 | -92.0 | -89.0 | -86.0 | -83.0 | N.A | N.A | N.A | +| n262 | -86.8 | -83.8 | -80.8 | -77.8 | N.A | N.A | N.A | +| n263 | N.A | -86.3 | N.A | -80.3 | -77.3 | -74.3 | -73.3 | + +NOTE 1: The transmitter shall be set to PUMAX as defined in clause 6.2.4 + +The REFSENS requirement shall be met for an uplink transmission using QPSK DFT-s-OFDM waveforms and for uplink transmission bandwidth less than or equal to that specified in Table 7.3.2.1-2. + +Unless given by Table 7.3.2.1-3, the minimum requirements for reference sensitivity shall be verified with the network signalling value NS\_200 (Table 6.2.3-1) configured. + +### 7.3.2.3 Reference sensitivity power level for power class 3 + +The throughput shall be $\geq 95$ % of the maximum throughput of the reference measurement channels as specified in Annexes A.2.3.2 and A.3.3.2 (with one sided dynamic OCNG Pattern OP.1 TDD for the DL-signal as described in Annex A.5.2.1) with peak reference sensitivity specified in Table 7.3.2.3-1. The requirement is verified with the test metric of EIS (Link=RX beam peak direction, Meas=Link Angle). + +For the UEs that support multiple FR2 bands, the minimum requirement for Reference sensitivity in Table 7.3.2.3-1 shall be increased per band, respectively, by the reference sensitivity relaxation parameter $\Delta\text{MB}_{\text{P,n}}$ as specified in clause 6.2.1.3. The requirement for the UE which supports a single FR2 band is specified in Table 7.3.2.3-1. The requirement for the UE which supports multiple FR2 bands is specified in both Table 7.3.2.3-1 and Table 6.2.1.3-4. + +**Table 7.3.2.3-1: Reference sensitivity** + +| Operating band | REFSENS (dBm) / Channel bandwidth | | | | | | | +|----------------|-----------------------------------|---------|---------|---------|---------|----------|----------| +| | 50 MHz | 100 MHz | 200 MHz | 400 MHz | 800 MHz | 1600 MHz | 2000 MHz | +| n257 | -88.3 | -85.3 | -82.3 | -79.3 | N.A | N.A | N.A | +| n258 | -88.3 | -85.3 | -82.3 | -79.3 | N.A | N.A | N.A | +| n259 | -84.7 | -81.7 | -78.7 | -75.7 | N.A | N.A | N.A | +| n260 | -85.7 | -82.7 | -79.7 | -76.7 | N.A | N.A | N.A | +| n261 | -88.3 | -85.3 | -82.3 | -79.3 | N.A | N.A | N.A | +| n262 | -82.8 | -79.8 | -76.8 | -73.8 | N.A | N.A | N.A | +| n263 | N.A | -78 | N.A | -72 | -69 | -66 | -65 | + +NOTE 1: The transmitter shall be set to PUMAX as defined in clause 6.2.4 + +The REFSENS requirement shall be met for an uplink transmission using QPSK DFT-s-OFDM waveforms and for uplink transmission bandwidth less than or equal to that specified in Table 7.3.2.1-2. + +Unless given by Table 7.3.2.1-3, the minimum requirements for reference sensitivity shall be verified with the network signalling value NS\_200 (Table 6.2.3-1) configured. + +### 7.3.2.4 Reference sensitivity power level for power class 4 + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in Annexes A.2.3.2 and A.3.3.2 (with one sided dynamic OCGN Pattern OP.1 TDD for the DL-signal as described in Annex A.5.2.1) with peak reference sensitivity specified in Table 7.3.2.4-1. The requirement is verified with the test metric of EIS (Link=RX beam peak direction, Meas=Link Angle). + +**Table 7.3.2.4-1: Reference sensitivity for power class 4** + +| Operating band | REFSENS (dBm) / Channel bandwidth | | | | +|----------------|-----------------------------------|---------|---------|---------| +| | 50 MHz | 100 MHz | 200 MHz | 400 MHz | +| n257 | -97.0 | -94.0 | -91.0 | -88.0 | +| n258 | -97.0 | -94.0 | -91.0 | -88.0 | +| n260 | -95.0 | -92.0 | -89.0 | -86.0 | +| n261 | -97.0 | -94.0 | -91.0 | -88.0 | +| n262 | -91.0 | -88.0 | -85.0 | -82.0 | + +NOTE 1: The transmitter shall be set to PUMAX as defined in clause 6.2.4 + +The REFSENS requirement shall be met for an uplink transmission using QPSK DFT-s-OFDM waveforms and for uplink transmission bandwidth less than or equal to that specified in Table 7.3.2.1-2. + +Unless given by Table 7.3.2.1-3, the minimum requirements for reference sensitivity shall be verified with the network signalling value NS\_200 (Table 6.2.3-1) configured. + +### 7.3.2.5 Reference sensitivity power level for power class 5 + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in Annexes A.2.3.2 and A.3.3.2 (with one sided dynamic OCGN Pattern OP.1 TDD for the DL-signal as described in Annex A.5.2.1) with peak reference sensitivity specified in Table 7.3.2.5-1. The requirement is verified with the test metric of EIS (Link=RX beam peak direction, Meas=Link Angle). + +**Table 7.3.2.5-1: Reference sensitivity for power class 5** + +| Operating band | REFSENS (dBm) / Channel bandwidth | | | | +|----------------|-----------------------------------|---------|---------|---------| +| | 50 MHz | 100 MHz | 200 MHz | 400 MHz | +| n257 | -92.6 | -89.6 | -86.6 | -83.6 | +| n258 | -92.8 | -89.8 | -86.8 | -83.8 | +| n259 | -89.7 | -86.7 | -83.7 | -80.7 | + +NOTE 1: The transmitter shall be set to PUMAX as defined in clause 6.2.4 + +The REFSENS requirement shall be met for an uplink transmission using QPSK DFT-s-OFDM waveforms and for uplink transmission bandwidth less than or equal to that specified in Table 7.3.2.1-2. + +Unless given by Table 7.3.2.1-3, the minimum requirements for reference sensitivity shall be verified with the network signalling value NS\_200 (Table 6.2.3-1) configured. + +### 7.3.2.6 Reference sensitivity power level for power class 6 + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in Annexes A.2.3.2 and A.3.3.2 (with one sided dynamic OCNG Pattern OP.1 TDD for the DL-signal as described in Annex A.5.2.1) with peak reference sensitivity specified in Table 7.3.2.6-1. The requirement is verified with the test metric of EIS (Link=RX beam peak direction, Meas=Link Angle). + +**Table 7.3.2.6-1: Reference sensitivity for power class 6** + +| Operating band | REFSENS (dBm) / Channel bandwidth | | | | +|-------------------------------------------------------------------------------------|-----------------------------------|---------|---------|---------| +| | 50 MHz | 100 MHz | 200 MHz | 400 MHz | +| n257 | -92.6 | -89.6 | -86.6 | -83.6 | +| n258 | -92.8 | -89.8 | -86.8 | -83.8 | +| n261 | -92.6 | -89.6 | -86.6 | -83.6 | +| NOTE 1: The transmitter shall be set to $P_{\text{MAX}}$ as defined in clause 6.2.4 | | | | | + +The REFSENS requirement shall be met for an uplink transmission using QPSK DFT-s-OFDM waveforms and for uplink transmission bandwidth less than or equal to that specified in Table 7.3.2.1-2. + +Unless given by Table 7.3.2.1-3, the minimum requirements for reference sensitivity shall be verified with the network signalling value NS\_200 (Table 6.2.3-1) configured. + +### 7.3.2.7 Reference sensitivity power level for power class 7 + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in Annexes A.2.3.2 and A.3.3.2 (with one sided dynamic OCNG Pattern OP.1 TDD for the DL-signal as described in Annex A.5.2.1) with peak reference sensitivity specified in Table 7.3.2.7-1. The requirement is verified with the test metric of EIS (Link=RX beam peak direction, Meas=Link Angle). + +**Table 7.3.2.7-1: Reference sensitivity** + +| Operating band | REFSENS (dBm) / Channel bandwidth | | +|-------------------------------------------------------------------------------------|-----------------------------------|---------| +| | 50 MHz | 100 MHz | +| n257 | -85.3 | -82.3 | +| n258 | -85.3 | -82.3 | +| n261 | -85.3 | -82.3 | +| NOTE 1: The transmitter shall be set to $P_{\text{MAX}}$ as defined in clause 6.2.4 | | | + +The REFSENS requirement shall be met for an uplink transmission using QPSK DFT-s-OFDM waveforms and for uplink transmission bandwidth of 50MHz and 100MHz specified in Table 7.3.2.1-2. + +Unless given by Table 7.3.2.1-3, the minimum requirements for reference sensitivity shall be verified with the network signalling value NS\_200 (Table 6.2.3-1) configured. + +### 7.3.3 Void + +### 7.3.4 EIS spherical coverage + +#### 7.3.4.1 EIS spherical coverage for power class 1 + +The reference measurement channels and throughput criterion shall be as specified in clause 7.3.2.1 + +The maximum EIS at the 85th percentile of the CCDF of EIS measured over the full sphere around the UE is defined as the spherical coverage requirement and is found in Table 7.3.4.1-1 below. The requirement is verified with the test metric of EIS (Link=Spherical coverage grid, Meas=Link angle). + +**Table 7.3.4.1-1: EIS spherical coverage for power class 1** + +| Operating band | EIS at 85 th %-tile CCDF (dBm) / Channel bandwidth | | | | | | | +|----------------|---------------------------------------------------------------|---------|---------|---------|---------|----------|----------| +| | 50 MHz | 100 MHz | 200 MHz | 400 MHz | 800 MHz | 1600 MHz | 2000 MHz | +| n257 | -89.5 | -86.5 | -83.5 | -80.5 | N/A | N/A | N/A | +| n258 | -89.5 | -86.5 | -83.5 | -80.5 | N/A | N/A | N/A | +| n260 | -86.5 | -83.5 | -80.5 | -77.5 | N/A | N/A | N/A | +| n261 | -89.5 | -86.5 | -83.5 | -80.5 | N/A | N/A | N/A | +| n262 | -84.3 | -81.3 | -78.3 | -75.3 | N/A | N/A | N/A | +| n263 | N/A | -73.5 | N/A | -67.5 | -64.5 | -61.5 | -60.5 | + +The requirement shall be met for an uplink transmission using QPSK DFT-s-OFDM waveforms and for uplink transmission bandwidth less than or equal to that specified in Table 7.3.2.1-2. + +Unless given by Table 7.3.2.1-3, the minimum requirements for reference sensitivity shall be verified with the network signalling value NS\_200 (Table 6.2.3-1) configured. + +#### 7.3.4.2 EIS spherical coverage for power class 2 + +The reference measurement channels and throughput criterion shall be as specified in clause 7.3.2.2 + +The maximum EIS at the 60th percentile of the CCDF of EIS measured over the full sphere around the UE is defined as the spherical coverage requirement and is found in Table 7.3.4.2-1 below. The requirement is verified with the test metric of EIS (Link=Spherical coverage grid, Meas=Link angle). + +**Table 7.3.4.2-1: EIS spherical coverage for power class 2** + +| Operating band | EIS at 60 th %-tile CCDF (dBm) / Channel bandwidth | | | | | | | +|----------------|---------------------------------------------------------------|---------|---------|---------|---------|----------|----------| +| | 50 MHz | 100 MHz | 200 MHz | 400 MHz | 800 MHz | 1600 MHz | 2000 MHz | +| n257 | -81.0 | -78.0 | -75.0 | -72.0 | N.A | N.A | N.A | +| n258 | -81.0 | -78.0 | -75.0 | -72.0 | N.A | N.A | N.A | +| n259 | -76.2 | -73.2 | -70.2 | -67.2 | N.A | N.A | N.A | +| n261 | -81.0 | -78.0 | -75.0 | -72.0 | N.A | N.A | N.A | +| n262 | -74.9 | -71.9 | -68.9 | -65.9 | N.A | N.A | N.A | +| n263 | N.A | -71.2 | N.A | -65.2 | -62.2 | -59.2 | -58.2 | + +NOTE 1: The transmitter shall be set to PUMAX as defined in clause 6.2.4 + +NOTE 2: The EIS spherical coverage requirements are verified only under normal thermal conditions as defined in Annex E.2.1. + +The requirement shall be met for an uplink transmission using QPSK DFT-s-OFDM waveforms and for uplink transmission bandwidth less than or equal to that specified in Table 7.3.2.1-2. + +Unless given by Table 7.3.2.1-3, the minimum requirements for reference sensitivity shall be verified with the network signalling value NS\_200 (Table 6.2.3-1) configured. + +### 7.3.4.3 EIS spherical coverage for power class 3 + +The reference measurement channels and throughput criterion shall be as specified in clause 7.3.2.3 + +The maximum EIS at the 50th percentile of the CCDF of EIS measured over the full sphere around the UE is defined as the spherical coverage requirement and is found in Table 7.3.4.3-1 below. The requirement is verified with the test metric of EIS (Link=Spherical coverage grid, Meas=Link angle). + +For the UEs that support multiple FR2 bands, the minimum requirement for EIS spherical coverage in Table 7.3.4.3-1 shall be increased per band, respectively, by the EIS spherical coverage relaxation parameter $\Delta\text{MB}_{s,n}$ as specified in clause 6.2.1.3. The requirement for the UE which supports a single FR2 band is specified in Table 7.3.4.3-1. The requirement for the UE which supports multiple FR2 bands is specified in both Table 7.3.4.3-1 and Table 6.2.1.3-4. + +**Table 7.3.4.3-1: EIS spherical coverage for power class 3** + +| Operating band | EIS at 50 th %-tile CCDF (dBm) / Channel bandwidth | | | | | | | +|----------------|---------------------------------------------------------------|---------|---------|---------|---------|----------|----------| +| | 50 MHz | 100 MHz | 200 MHz | 400 MHz | 800 MHz | 1600 MHz | 2000 MHz | +| n257 | -77.4 | -74.4 | -71.4 | -68.4 | N.A | N.A | N.A | +| n258 | -77.4 | -74.4 | -71.4 | -68.4 | N.A | N.A | N.A | +| n259 | -71.9 | -68.9 | -65.9 | -62.9 | N.A | N.A | N.A | +| n260 | -73.1 | -70.1 | -67.1 | -64.1 | N.A | N.A | N.A | +| n261 | -77.4 | -74.4 | -71.4 | -68.4 | N.A | N.A | N.A | +| n262 | -69.7 | -66.7 | -63.7 | -60.7 | N.A | N.A | N.A | +| n263 | N.A | -66.2 | N.A | -60.2 | -57.2 | -54.2 | -53.2 | + +NOTE 1: The transmitter shall be set to $P_{\text{UMAX}}$ as defined in clause 6.2.4 + +NOTE 2: The EIS spherical coverage requirements are verified only under normal thermal conditions as defined in Annex E.2.1. + +The requirement shall be met for an uplink transmission using QPSK DFT-s-OFDM waveforms and for uplink transmission bandwidth less than or equal to that specified in Table 7.3.2.1-2. + +Unless given by Table 7.3.2.1-3, the minimum requirements for reference sensitivity shall be verified with the network signalling value NS\_200 (Table 6.2.3-1) configured. + +### 7.3.4.4 EIS spherical coverage for power class 4 + +The reference measurement channels and throughput criterion shall be as specified in clause 7.3.2.4 + +The maximum EIS at the 20th percentile of the CCDF of EIS measured over the full sphere around the UE is defined as the spherical coverage requirement and is found in Table 7.3.4.4-1 below. The requirement is verified with the test metric of EIS (Link=Spherical coverage grid, Meas=Link angle). + +**Table 7.3.4.4-1: EIS spherical coverage for power class 4** + +| Operating band | EIS at 20 th %-tile CCDF (dBm) / Channel bandwidth | | | | +|----------------|---------------------------------------------------------------|---------|---------|---------| +| | 50 MHz | 100 MHz | 200 MHz | 400 MHz | +| n257 | -88.0 | -85.0 | -82.0 | -79.0 | +| n258 | -88.0 | -85.0 | -82.0 | -79.0 | +| n260 | -83.0 | -80.0 | -77.0 | -74.0 | +| n261 | -88.0 | -85.0 | -82.0 | -79.0 | +| n262 | -78.9 | -75.9 | -72.9 | -69.9 | + +NOTE 1: The transmitter shall be set to $P_{\text{UMAX}}$ as defined in clause 6.2.4 + +NOTE 2: The EIS spherical coverage requirements are verified only under normal thermal conditions as defined in Annex E.2.1. + +The requirement shall be met for an uplink transmission using QPSK DFT-s-OFDM waveforms and for uplink transmission bandwidth less than or equal to that specified in Table 7.3.2.1-2. + +Unless given by Table 7.3.2.1-3, the minimum requirements for reference sensitivity shall be verified with the network signalling value NS\_200 (Table 6.2.3-1) configured. + +### 7.3.4.5 EIS spherical coverage for power class 5 + +The reference measurement channels and throughput criterion shall be as specified in clause 7.3.2.4 + +The maximum EIS at the 85th percentile of the CCDF of EIS measured over the full sphere around the UE is defined as the spherical coverage requirement and is found in Table 7.3.4.5-1 below. The requirement is verified with the test metric of EIS (Link=Spherical coverage grid, Meas=Link angle). + +**Table 7.3.4.5-1: EIS spherical coverage for power class 5** + +| Operating band | EIS at 85 th %-tile CCDF (dBm) / Channel bandwidth | | | | +|----------------|---------------------------------------------------------------|---------|---------|---------| +| | 50 MHz | 100 MHz | 200 MHz | 400 MHz | +| n257 | -84.6 | -81.6 | -78.6 | -75.6 | +| n258 | -84.8 | -81.8 | -78.8 | -75.8 | +| n259 | -81.7 | -78.7 | -75.7 | -72.7 | + +NOTE 1: The transmitter shall be set to PUMAX as defined in clause 6.2.4 + +NOTE 2: The EIS spherical coverage requirements are verified only under normal thermal conditions as defined in Annex E.2.1. + +The requirement shall be met for an uplink transmission using QPSK DFT-s-OFDM waveforms and for uplink transmission bandwidth less than or equal to that specified in Table 7.3.2.1-2. + +Unless given by Table 7.3.2.1-3, the minimum requirements for reference sensitivity shall be verified with the network signalling value NS\_200 (Table 6.2.3-1) configured. + +### 7.3.4.6 EIS spherical coverage for power class 6 + +The reference measurement channels and throughput criterion shall be as specified in clause 7.3.2.6 + +The maximum EIS measured over the spherical coverage evaluation areas is defined as the spherical coverage requirement and is found in Table 7.3.4.6-1 below. UE spherical coverage evaluation areas are found in Table 6.2.1.6-3a in clause 6.2.1.6, by consisting of Area-1 and Area-2, in the reference coordinate system in Annex J.1. The requirement is verified with the test metric of EIS (Link=Spherical coverage grid, Meas=Link angle). + +**Table 7.3.4.6-1: EIS spherical coverage for power class 6** + +| Operating band | Max EIS over UE spherical coverage evaluation areas (dBm) / Channel bandwidth | | | | +|----------------|-------------------------------------------------------------------------------|---------|---------|---------| +| | 50 MHz | 100 MHz | 200 MHz | 400 MHz | +| n257 | -82.6 | -79.6 | -76.6 | -73.6 | +| n258 | -82.8 | -79.8 | -76.8 | -73.8 | +| n261 | -82.6 | -79.6 | -76.6 | -73.6 | + +NOTE 1: The transmitter shall be set to PUMAX as defined in clause 6.2.4 + +NOTE 2: The EIS spherical coverage requirements are verified only under normal thermal conditions as defined in Annex E.2.1. + +NOTE 3: The requirements in this table are applicable to FR2 PC6 UE with the network signalling *[highSpeedMeasFlag-r17]* configured as *[set2]*. + +The requirement shall be met for an uplink transmission using QPSK DFT-s-OFDM waveforms and for uplink transmission bandwidth less than or equal to that specified in Table 7.3.2.1-2. + +Unless given by Table 7.3.2.1-3, the minimum requirements for reference sensitivity shall be verified with the network signalling value NS\_200 (Table 6.2.3-1) configured. + +### 7.3.4.7 EIS spherical coverage for power class 7 + +The reference measurement channels and throughput criterion shall be as specified in clause 7.3.2.7. + +The maximum EIS at the 50th percentile of the CCDF of EIS measured over the full sphere around the UE is defined as the spherical coverage requirement and is found in Table 7.3.4.7-1 below. The requirement is verified with the test metric of EIS (Link=Spherical coverage grid, Meas=Link angle). + +**Table 7.3.4.7-1: EIS spherical coverage for power class 7** + +| Operating band | EIS at 50 th %-tile CCDF (dBm) / Channel bandwidth | | +|------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|---------| +| | 50 MHz | 100 MHz | +| n257 | -74.4 | -71.4 | +| n258 | -74.4 | -71.4 | +| n261 | -74.4 | -71.4 | +| NOTE 1: The transmitter shall be set to P UMAX as defined in clause 6.2.4 | | | +| NOTE 2: The EIS spherical coverage requirements are verified only under normal thermal conditions as defined in Annex E.2.1. | | | + +The requirement shall be met for an uplink transmission using QPSK DFT-s-OFDM waveforms and for uplink transmission bandwidth of 50MHz and 100MHz specified in Table 7.3.2.1-2. + +Unless given by Table 7.3.2.1-3, the minimum requirements for reference sensitivity shall be verified with the network signalling value NS\_200 (Table 6.2.3-1) configured. + +## 7.3A Reference sensitivity for DL CA + +### 7.3A.1 General + +### 7.3A.2 Reference sensitivity power level for CA + +#### 7.3A.2.1 Intra-band contiguous CA + +For each component carrier in the intra-band contiguous carrier aggregation, the throughput in QPSK R = 1/3 shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in Annexes A.2.3.2 and A.3.3.2 (with one sided dynamic OCNG Pattern OP.1 TDD for the DL-signal as described in Annex A.5.2.1) with peak reference sensitivity values determined from clause 7.3.2, and relaxation applied to peak reference sensitivity requirement as specified in Table 7.3A.2.1-1. + +**Table 7.3A.2.1-1: $\Delta R_{\text{IBC}}$ EIS Relaxation for CA operation by aggregated channel bandwidth** + +| Aggregated Channel BW 'BW Channel_CA ' (MHz) | $\Delta R_{\text{IBC}}$ (dB) | +|---------------------------------------------------------|------------------------------| +| BW Channel_CA $\leq 800$ | 0.0 | +| $800 < \text{BW}_{\text{Channel\_CA}} \leq 1200$ | 0.5 | +| $1200 < \text{BW}_{\text{Channel\_CA}} \leq 1600$ | 1.0 | +| $1600 < \text{BW}_{\text{Channel\_CA}} \leq 2000$ | 1.5 | + +#### 7.3A.2.2 Intra-band non-contiguous CA + +For each component carrier in the intra-band non-contiguous carrier aggregation, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in Annexes A.2.3.2 and A.3.3.2 (with one sided dynamic OCNG Pattern OP.1 TDD for the DL-signal as described in Annex A.5.2.1) with peak reference sensitivity values determined from clause 7.3.2, and relaxation applied to peak reference sensitivity requirement as specified in Table 7.3A.2.2-1. The configured downlink spectrum is defined as the frequency band from the lowest edge of the lowest CC to the upper edge of the highest CC of all UL and DL configured CCs. + +**Table 7.3A.2.2-1: $\Delta R_{IBNC}$ EIS Relaxation for CA operation** + +| Configured DL spectrum (MHz) | $\Delta R_{IBNC}$ (dB) | +|------------------------------|------------------------| +| $\leq 800$ | 0.0 | +| $> 800$ and $\leq 1400$ | 0.5 | +| $> 1400$ and $\leq 2400$ | 1.5 | + +### 7.3A.2.3 Inter-band CA + +The inter-band requirement applies for all active component carriers. The throughput for each component carrier shall be $\geq 95$ % of the maximum throughput of the reference measurement channels as specified in Annexes A.2.3.2 and A.3.3.2 (with one sided dynamic OCN G Pattern OP.1 TDD for the DL-signal as described in Annex A.5.2.1) with peak reference sensitivity for each carrier specified in section 7.3.2, and relaxation $\Delta R_{IB,P,n}$ applied to peak reference sensitivity requirement. $\Delta R_{IB,P,n}$ is specified in Table 7.3A.2.3-1. The requirement on each component carrier shall be met when the power in the component carrier in the other band is set to its EIS spherical coverage requirement for inter-band CA specified in sub-clause 7.3A.3.3. + +For the combination of intra-band and inter-band carrier aggregation, the intra-band CA relaxation, $\Delta R_{IBC}$ and $\Delta R_{IBNC}$ , are also applied according to the clause 7.3A.2.1 and 7.3A.2.2. + +**Table 7.3A.2.3-1: $\Delta R_{IB,P,n}$ reference sensitivity relaxation for inter-band CA** + +| NR CA band combinations | NR band | $\Delta R_{IB,P,n}$ (dB) | | | | +|-------------------------|---------|--------------------------|-----|-----|-----| +| | | PC1 | PC2 | PC3 | PC5 | +| CA_n257-n259 | n257 | | 3.5 | 4.0 | 3.0 | +| | n259 | | 3.5 | 4.0 | 3.0 | +| CA_n258-n260 | n258 | | | 3.5 | | +| | n260 | | | 3.5 | | +| CA_n258-n261 | n258 | | | 3.5 | | +| | n261 | | | 3.5 | | +| CA_n260-n261 | n260 | 2.5 | | 3.5 | | +| | n261 | 2.5 | | 3.5 | | + +Note: For each power class, band combinations without specified $\Delta R_{IB,P,n}$ are not enabled for inter-band downlink carrier aggregation in this release. + +### 7.3A.3 EIS spherical coverage for DL CA + +#### 7.3A.3.1 Void + +#### 7.3A.3.2 Void + +#### 7.3A.3.3 EIS spherical coverage for inter-band CA + +The inter-band CA requirement applies per operating band, for all active component carriers with UL assigned to one band and one DL component carrier per band. The requirement on each component carrier shall be met when the power in the component carrier in the other band is set to its EIS spherical coverage requirement for inter-band CA specified in this sub-clause. + +The inter-band CA spherical coverage requirement for each power class will be satisfied if the intersection set of spherical coverage areas exceeds the common coverage requirement. Intersection set of spherical coverage areas is defined as a fraction of area of full sphere measured around the UE where both bands meet their defined individual EIS spherical coverage requirements for inter-band CA operation. The common coverage requirement is determined as $<100\text{-percentile rank}> \%$ , where ‘percentile rank’ is the percentile value in the specification of spherical coverage for that power class from clause 7.3.4. The requirement is verified with the test metric of EIS (Link=Beam peak search grids, Meas=Link angle). + +The reference measurement channels and throughput criterion shall be as specified in clause 7.3A.2.3. The requirement shall be met for an uplink transmission using QPSK DFT-s-OFDM waveforms and for uplink transmission bandwidth less than or equal to that specified in clause 7.3.2. + +Unless otherwise specified, the minimum requirements for reference sensitivity shall be verified with the network signalling value NS\_200 (Table 6.2.3.1-1) configured. + +The required spherical coverage EIS for each band in inter-band CA operation is given in clause 7.3.4 and modified by $\Delta R_{IB,S,n}$ . The value of $\Delta R_{IB,S,n}$ is defined in Table 7.3A.3.3-1. + +**Table 7.3A.3.3-1: $\Delta R_{IB,S,n}$ EIS spherical coverage requirement relaxation for inter-band CA** + +| NR CA band combination | NR band | $\Delta R_{IB,S,n}$ (dB) | | | | +|------------------------|---------|--------------------------|-----|-----|-------| +| | | PC1 | PC2 | PC3 | PC5 | +| CA_n257-n259 | n257 | | 3.5 | 3.5 | [2.5] | +| | n259 | | 3.5 | 3.5 | [2.5] | +| CA_n258-n260 | n258 | | | 3.5 | | +| | n260 | | | 3.5 | | +| CA_n258-n261 | n258 | | | 3.5 | | +| | n261 | | | 3.5 | | +| CA_n260-n261 | n260 | [2.5] | | 3.5 | | +| | n261 | [2.5] | | 3.5 | | + +Note: For each power class, band combinations without specified $\Delta R_{IB,S,n}$ are not enabled for inter-band downlink carrier aggregation in this release. + +## 7.3D Void + +## 7.3K Spherical coverage requirement for simultaneous reception from multiple directions + +### 7.3K.0 General + +For this release, the requirement applies only to FR2-1 UEs that support the following set of capabilities: + +1. simultaneousReceptionDiffTypeD-r16 +2. At least one of: + - a. singleDCI-SDM-scheme-r16 or + - b. multiDCI-MultiTRP-r16 and either of: + - i. overlapPDSCHsFullyFreqTime-r16. + - ii. overlapPDSCHsInTimePartiallyFreq-r16 + +The requirement applies for simultaneous reception of rank 2 PDSCH, where each layer uses overlapping RBs in both time and frequency and is associated with a unique TCI state and AoA. The scheduled TCI states for the rank 2 PDSCH shall be configured with different QCL type-D reference signals respectively. The DL power at the center of quiet zone from each AoA equals the EIS spherical coverage requirement from sub-clause 7.3.4. + +For UEs supporting *singleDCI-SDM-scheme-r16*, the cumulative throughput in the DL associated with both TCI-states shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified A.3.3.2-5 and A.3.3.2-6 (with one sided dynamic OCNG Pattern OP.1 TDD for the DL-signal as described in Annex A.5.2.1). + +For UEs supporting *multiDCI-MultiTRP-r16*, the throughput in the DL associated with each TCI-state shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified A.3.3.2-1 and A.3.3.2-2 (with one sided dynamic OCNG Pattern OP.1 TDD for the DL-signal as described in Annex A.5.2.1). + +The requirement shall be met for an uplink transmission using QPSK DFT-s-OFDM waveforms and for uplink transmission bandwidth less than or equal to the downlink transmission bandwidth. The UL is assigned to any one of the two TCI-states scheduled for simultaneous DL, with reference measurement channel as specified in Annex A.2.3.2. The transmitter shall be set to PUMAX as defined in clause 6.2.4. + +Unless otherwise specified, the minimum requirements shall be verified with the network signalling value NS\_200 (Table 6.2.3.1-1) configured. + +### 7.3K.1 (Reserved) + +### 7.3K.2 (Reserved) + +### 7.3K.3 2AoA spherical coverage of power class 3 + +The requirements apply to the UE when tested in a test system as described in Annex L. The requirement is verified with the test metric of throughput (Link= 2AoA spherical coverage grid, Meas=Link Angle). + +The spherical coverage requirement for simultaneous reception from multiple directions applies to the probability to support simultaneous reception of rank 2 PDSCH defined in sub-clause 7.3K.0. The probability (see Annex L) is defined as the spatial average over the full sphere around the UE of the probability of any one direction to support 2 AoA reception. In the applicable test system (see Annex L), the probability of any one direction of the UE to support 2 AoA reception for any specific AoA separation is the ratio of the number of unique AoA pairs that include that direction and can support 2 AoA reception to the total number of verified unique AoA pairs that include that direction. + +The requirement applies only for the UE's declared orientation in the positioner of the test system. The requirement for each AoA separation condition applies only for the UE's declared orientation in the positioner of the test system for that AoA separation. The minimum required overall probability to support 2 AoA reception for power class 3 UEs for any channel bandwidth is specified by AoA separation in table 7.3K.3-1. The UE is required to fulfil the requirement at any one declared AoA separation. + +**Table 7.3K.3-1: Requirement for power class 3** + +| AoA separation (degrees) | Probability (%) | +|--------------------------|-----------------| +| 30 | 18.5 | +| 60 | 13.5 | +| 90 | 12.5 | +| 120 | 20.5 | +| 150 | 28.5 | + +### 7.3K.4 (Reserved) + +### 7.3K.5 (Reserved) + +### 7.3K.6 2AoA spherical coverage for power class 6 + +The requirements for a power class 6 UE are applicable with network signalling *highSpeedDeploymentTypeFR2-r17* configured as *bidirectional*. UE spherical coverage evaluation areas are found in Table 6.2.1.6-3a in clause 6.2.1.6, by consisting of Area-1 and Area-2, in the reference coordinate system in Annex L.1. If one AoA is within Area-1 and another AoA is within Area-2, the 2AoA spherical coverage requirements apply with DL power specified in Table 7.3K.6-1 for the PDSCH of each AoA. For any AoA pair selected from Area-1 and Area-2, respectively, the throughput shall be $\geq 95$ % of the maximum throughput of the reference measurement channels which is specified in A.3.x and A.3.y for UEs supporting *singleDCI-SDM-scheme-r16* and for UEs supporting *multiDCI-MultiTRP-r16* respectively. The requirement is verified with a 150° angular separation between 2AoAs. The requirement is verified with the test metric of Throughput (Link=2AoA Spherical coverage grid, Meas=Link angle). + +**Table 7.3K.6-1: DL power for 2AoA spherical coverage requirement for power class 6** + +| Operating band | PDSCH DL power over UE spherical coverage evaluation areas (dBm) /
Channel bandwidth | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|---------|---------|---------| +| | 50 MHz | 100 MHz | 200 MHz | 400 MHz | +| n257 | -82.6 | -79.6 | -76.6 | -73.6 | +| n258 | -82.8 | -79.8 | -76.8 | -73.8 | +| n261 | -82.6 | -79.6 | -76.6 | -73.6 | +| NOTE 1: The transmitter shall be set to $P_{\text{UMAX}}$ as defined in clause 6.2.4 | | | | | +| NOTE 2: The 2AoA spherical coverage requirements are verified only under normal thermal conditions as defined in Annex E.2.1. | | | | | +| NOTE 3: The requirements in this table are applicable with the network signalling highSpeedMeasFlagFR2-r17 configured as set2 . | | | | | + +The requirement shall be met for an uplink transmission using QPSK DFT-s-OFDM waveforms and for uplink transmission bandwidth less than or equal to that specified in Table 7.3.2.1-2. + +Unless given by Table 7.3.2.1-3, the minimum requirements for 2AoA spherical coverage shall be verified with the network signalling value NS\_200 (Table 6.2.3.1-1) configured. + +## 7.4 Maximum input level + +The maximum input level is defined as the maximum mean power, for which the throughput shall meet or exceed the minimum requirements for the specified reference measurement channel. + +The maximum input level is defined as a directional requirement. The requirement is verified in beam locked mode in the direction where peak gain is achieved. + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in Annex A (with one sided dynamic OCNG Pattern OP.1 TDD for the DL-signal as described in Annex A.5.2.1) with parameters specified in Table 7.4-1. The requirement is verified with the test metric of EIS (Link=RX beam peak direction, Meas=Link angle). + +**Table 7.4-1: Maximum input level** + +| Rx Parameter | Units | Channel bandwidth | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|------------------------------|---------|---------|---------|---------|----------|----------|--|--|--|--|--|--|--| +| | | 50 MHz | 100 MHz | 200 MHz | 400 MHz | 800 MHz | 1600 MHz | 2000 MHz | | | | | | | | +| Power in transmission bandwidth configuration | dBm | -25 (NOTE 2)
-27 (NOTE 3) | | | | | | | | | | | | | | +| NOTE 1: The transmitter shall be set to 4 dB below the $P_{\text{UMAX,fc}}$ as defined in clause 6.2.4, with uplink configuration specified in Table 7.3.2.1-2. | | | | | | | | | | | | | | | | +| NOTE 2: Reference measurement channel is specified in Annex A.3.3.2: QPSK, R=1/3 variant with one sided dynamic OCNG Pattern as described in Annex A. | | | | | | | | | | | | | | | | +| NOTE 3: Reference measurement channel is specified in Annex A.3.3.5: 256QAM, R=4/5 variant with one sided dynamic OCNG Pattern as described in Annex A. | | | | | | | | | | | | | | | | + +**Table 7.4-2: Void** + +## 7.4A Maximum input level for DL CA + +**Table 7.4A-1: Void** + +**Table 7.4A-2: Void** + +### 7.4A.1 Maximum input level for Intra-band contiguous CA + +For intra-band contiguous carrier aggregation the input level is defined as the cumulative received power, summed over the transmission bandwidth configurations of each active DL CC. All DL CCs shall be active throughout the test. The input power shall be distributed among the active DL CCs so their PSDs are aligned with each other. At the maximum input level, the specified relative throughput shall meet or exceed the minimum requirements for the specified reference measurement channel over each component carrier. The minimum requirement is specified in Table 7.4A-1. + +The maximum input level is defined as a directional requirement. The requirement is verified in beam locked mode in the direction where peak gain is achieved. The requirement is verified with the test metric of EIS (Link=RX beam peak direction, Meas=Link angle). + +**Table 7.4A.1-1: Maximum input level for Intra-band contiguous CA** + +| Rx Parameter | Units | Level | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|--------------| +| Power summed over transmission bandwidth configurations of all active DL CCs | dBm | -25 (NOTE 2) | +| | | -27 (NOTE 3) | +| NOTE 1: The transmitter shall be set to 4 dB below the $P_{\text{UMAX,fc}}$ as defined in clause 6.2.4, with uplink configuration specified in Table 7.3.2.1-2 | | | +| NOTE 2: Reference measurement channel in each CC is specified in Annex A.3.3.2: QPSK, R=1/3 variant with one sided dynamic OCNG Pattern as described in Annex A. | | | +| NOTE 3: Reference measurement channel is specified in Annex A.3.3.5: 256QAM, R=4/5 variant with one sided dynamic OCNG Pattern as described in Annex A. | | | + +### 7.4A.2 Maximum input level for Intra-band non-contiguous CA + +For intra-band non-contiguous carrier aggregation the requirement of section 7.4A.1 applies + +### 7.4A.3 Maximum input level for Inter-band CA + +For inter-band carrier aggregation with one component carrier per operating band and the uplink assigned to one NR band, the maximum input level is defined with the uplink active on the band other than the band whose downlink is being tested. The UE shall meet the requirements specified in clause 7.4 for each component carrier while all downlink carriers are active. + +For the combination of intra-band and inter-band carrier aggregation and uplink carrier(s) assigned to one NR band, the requirement is defined with the uplink active on the band other than the band whose downlink is being tested. The UE shall meet the requirements specified in clause 7.4A.1 and 7.4A.2 for each band while all downlink carriers are active. + +## 7.4D Void + +## 7.5 Adjacent channel selectivity + +Adjacent Channel Selectivity (ACS) is a measure of a receiver's ability to receive a NR signal at its assigned channel frequency in the presence of an adjacent channel signal at a given frequency offset from the centre frequency of the assigned channel. ACS is the ratio of the receive filter attenuation on the assigned channel frequency to the receive filter attenuation on the adjacent channel(s). + +The requirement applies at the RIB when the AoA of the incident wave of the wanted signal and the interfering signal are both from the direction where peak gain is achieved. + +The wanted and interfering signals apply to all supported polarizations, under the assumption of polarization match. + +The UE shall fulfil the minimum requirement specified in Table 7.5-1 for all values of an adjacent channel interferer up to -25 dBm. However, it is not possible to directly measure the ACS, instead the lower and upper range of test parameters are chosen in Table 7.5-2 and Table 7.5-3 where the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in Annexes A.2.3.2 and A.3.3.2, with one sided dynamic OCNG Pattern OP.1 TDD for the DL-signal as described in Annex A.5.2.1. The requirement is verified with the test metric of EIS (Link=RX beam peak direction, Meas=Link angle). + +**Table 7.5-1: Adjacent channel selectivity** + +| Operating band | Units | Adjacent channel selectivity / Channel bandwidth | | | | | | | +|------------------|-------|--------------------------------------------------|---------|---------|---------|---------|----------|----------| +| | | 50 MHz | 100 MHz | 200 MHz | 400 MHz | 800 MHz | 1600 MHz | 2000 MHz | +| n257, n258, n261 | dB | 23 | 23 | 23 | 23 | N/A | N/A | N/A | +| n259, n260, n262 | dB | 22 | 22 | 22 | 22 | N/A | N/A | N/A | +| n263 | dB | N/A | 21 | N/A | 21 | 20 | 20 | 20 | + +**Table 7.5-2: Adjacent channel selectivity test parameters, Case 1** + +| Rx Parameter | Units | Channel bandwidth | | | | | | | +|---------------------------------------------------|-------|--------------------------|----------------------------|----------------------------|----------------------------|----------------------------|------------------------------|------------------------------| +| | | 50 MHz | 100 MHz | 200 MHz | 400 MHz | 800 MHz | 1600 MHz | 2000 MHz | +| Power in Transmission Bandwidth Configuration | dBm | REFSENS + 14 dB | | | | | | | +| $P_{\text{Interferer}}$ for band n257, n258, n261 | dBm | REFSENS + 35.5 dB | REFSENS +35.5 dB | REFSENS +35.5 dB | REFSENS +35.5 dB | N/A | N/A | N/A | +| $P_{\text{Interferer}}$ for band n259, n260, n262 | dBm | REFSENS + 34.5 dB | REFSENS +34.5 dB | REFSENS +34.5 dB | REFSENS +34.5 dB | N/A | N/A | N/A | +| $P_{\text{Interferer}}$ for band n263 | dBm | N/A | REFSENS +33.5 dB | N/A | REFSENS +33.5 dB | REFSENS + 32.5 dB | REFSENS + 32.5 dB | REFSENS + 32.5 dB | +| $BW_{\text{Interferer}}$ | MHz | 50 | 100 | 200 | 400 | | | | +| $F_{\text{Interferer}}$ (offset) | MHz | 50
/
-50
NOTE 3 | 100
/
-100
NOTE 3 | 200
/
-200
NOTE 3 | 400
/
-400
NOTE 3 | 800
/
-800
NOTE 3 | 1600
/
-1600
NOTE 3 | 2000
/
-2000
NOTE 3 | + +NOTE 1: The interferer consists of the Reference measurement channel specified in Annex A.3.2 with one sided dynamic OCNG Pattern as described in Annex A.3.2 and set-up according to Annex C. + +NOTE 2: The REFSENS power level is specified in Clause 7.3.2, which are applicable to different UE power classes. + +NOTE 3: The absolute value of the interferer offset $F_{\text{Interferer}}$ (offset) shall be further adjusted to $(\text{CEIL}(|F_{\text{Interferer}}(\text{offset})|/\text{SCS}) + 0.5) * \text{SCS}$ MHz with SCS the sub-carrier spacing of the wanted signal in MHz. Wanted and interferer signal have same SCS. + +NOTE 4: The transmitter shall be set to 4 dB below the $P_{\text{UMAX,fc}}$ as defined in clause 6.2.4, with uplink configuration specified in Table 7.3.2.1-2. + +**Table 7.5-3: Adjacent channel selectivity test parameters, Case 2** + +| Rx Parameter | Units | Channel bandwidth | | | | | | | +|-------------------------------------------------------------------------|-------|--------------------------|----------------------------|----------------------------|----------------------------|----------------------------|------------------------------|------------------------------| +| | | 50 MHz | 100 MHz | 200 MHz | 400 MHz | 800 MHz | 1600 MHz | 2000 MHz | +| Power in Transmission Bandwidth Configuration for band n257, n258, n261 | dBm | -46.5 | -46.5 | -46.5 | -46.5 | N/A | N/A | N/A | +| Power in Transmission Bandwidth Configuration for band n259, n260, n262 | dBm | -45.5 | -45.5 | -45.5 | -45.5 | N/A | N/A | N/A | +| Power in Transmission Bandwidth Configuration for band n263 | dBm | N/A | -44.5 | N/A | -44.5 | -43.5 | -43.5 | -43.5 | +| $P_{\text{Interferer}}$ | dBm | -25 | | | | | | | +| $BW_{\text{Interferer}}$ | MHz | 50 | 100 | 200 | 400 | 800 | 1600 | 2000 | +| $F_{\text{Interferer}}$ (offset) | MHz | 50
/
-50
NOTE 2 | 100
/
-100
NOTE 2 | 200
/
-200
NOTE 2 | 400
/
-400
NOTE 2 | 800
/
-800
NOTE 2 | 1600
/
-1600
NOTE 2 | 2000
/
-2000
NOTE 2 | + +NOTE 1: The interferer consists of the Reference measurement channel specified in Annex 3.2 with one sided dynamic OCNG Pattern TDD as described in Annex A and set-up according to Annex C. + +NOTE 2: The absolute value of the interferer offset $F_{\text{Interferer}}$ (offset) shall be further adjusted to $(\text{CEIL}(|F_{\text{Interferer}}(\text{offset})|/\text{SCS}) + 0.5) * \text{SCS}$ MHz with SCS the sub-carrier spacing of the wanted signal in MHz. Wanted and interferer signal have same SCS. + +NOTE 3: The transmitter shall be set to 4 dB below the $P_{\text{UMAX,f,c}}$ as defined in clause 6.2.4, with uplink configuration specified in Table 7.3.2.1-2. + +## 7.5A Adjacent channel selectivity for DL CA + +**Table 7.5A-1: Void** + +**Table 7.5A-2: Void** + +**Table 7.5A-3: Void** + +### 7.5A.1 Adjacent channel selectivity for Intra-band contiguous CA + +For intra-band contiguous carrier aggregation, the SCC(s) shall be configured at nominal channel spacing to the PCC. The input power shall be distributed among the active DL CCs so their PSDs are aligned with each other. The UE shall fulfil the minimum requirement specified in Table 7.5A.1-1 for an adjacent channel interferer on either side of the aggregated downlink signal at a specified frequency offset and for an interferer power up to -25 dBm. + +The throughput of each carrier shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in Annexes A.2.3.2 and A.3.3.2 (with one sided dynamic OCNG Pattern OP.1 TDD for the DL-signal as described in Annex A.5.2.1). The requirement is verified with the test metric of EIS (Link=RX beam peak direction, Meas=Link angle). + +**Table 7.5A.1-1: Adjacent channel selectivity for intra-band contiguous CA** + +| Operating band | Units | Adjacent channel selectivity /
CA bandwidth class | +|------------------|-------|-----------------------------------------------------------------------------------------------------| +| | | All CA bandwidth class | +| n257, n258, n261 | dB | 23 | +| n259, n260, n262 | dB | 22 | +| n263 | dB | 21
for $BW_{\text{Channel\_CA}} \leq 400$ MHz.
20
for $BW_{\text{Channel\_CA}} > 400$ MHz. | + +**Table 7.5A.1-2: Adjacent channel selectivity test parameters for intra-band contiguous CA, Case 1** + +| Rx Parameter | Units | All CA bandwidth Classes | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| Pw in Transmission Bandwidth Configuration, per CC | | REFSENS + 14 dB | +| $P_{\text{Interferer}}$ for band n257, n258, n261 | dBm | Aggregated power + 21.5 | +| $P_{\text{Interferer}}$ for band n259, n260, n262 | dBm | Aggregated power + 20.5 | +| $P_{\text{Interferer}}$ for band n263 | dBm | Aggregated power + 19.5
for $BW_{\text{Channel\_CA}} \leq 400$ MHz.
Aggregated power + 18.5
for $BW_{\text{Channel\_CA}} > 400$ MHz. | +| $BW_{\text{Interferer}}$ | MHz | $BW_{\text{Channel\_CA}}$ | +| $F_{\text{Interferer}}$ (offset) | MHz | + $BW_{\text{channel CA}}$
/
- $BW_{\text{channel CA}}$

NOTE 3 | +| NOTE 1: The interferer consists of the Reference measurement channel specified in Annex 3.2 with one sided dynamic OCNNG Pattern as described in Annex A and set-up according to Annex C. | | | +| NOTE 2: The $F_{\text{Interferer}}$ (offset) is the frequency separation between the center of the aggregated CA bandwidth and the center frequency of the Interferer signal | | | +| NOTE 3: The absolute value of the interferer offset $F_{\text{Interferer}}$ (offset) shall be further adjusted to $(\text{CEIL}( F_{\text{Interferer}}(\text{offset}) /\text{SCS}) + 0.5) * \text{SCS}$ MHz with SCS the sub-carrier spacing of the carrier closest to the interferer in MHz. The interfering signal has the same SCS as that of the closest carrier. | | | +| NOTE 4: The transmitter shall be set to 4 dB below the $P_{\text{UMAX,f,c}}$ as defined in clause 6.2.4, with uplink configuration specified in Table 7.3.2.1-2. | | | + +**Table 7.5A.1-3: Adjacent channel selectivity test parameters for intra-band contiguous CA, Case 2** + +| Rx Parameter | Units | All CA bandwidth classes | +|----------------------------------------------------------------------------------------|-------|----------------------------------------------------------------------------------------------------| +| Pw in Transmission Bandwidth Configuration, aggregated power for band n257, n258, n261 | dBm | - 46.5 | +| Pw in Transmission Bandwidth Configuration, aggregated power for band n259, n260, n262 | dBm | - 45.5 | +| Pw in Transmission Bandwidth Configuration, aggregated power for band n263 | dBm | -44.5 for $BW_{\text{Channel\_CA}} \leq 400$ MHz
-43.5 for $BW_{\text{Channel\_CA}} > 400$ MHz. | +| $P_{\text{Interferer}}$ | dBm | - 25 | +| $BW_{\text{Interferer}}$ | MHz | $BW_{\text{Channel\_CA}}$ | +| $F_{\text{Interferer}}$ (offset) | MHz | + $BW_{\text{channel CA}}$
/
- $BW_{\text{channel CA}}$

NOTE 3 | + +- NOTE 1: The interferer consists of the Reference measurement channel specified in Annex A.3.3.2 with one sided dynamic OCNG Pattern OP.1 TDD as described in Annex A.5.2.1 and set-up according to Annex C. +- NOTE 2: The $F_{\text{interferer}}$ (offset) is the frequency separation between the center of the aggregated CA bandwidth and the center frequency of the Interferer signal +- NOTE 3: The absolute value of the interferer offset $F_{\text{interferer}}$ (offset) shall be further adjusted to $(\text{CEIL}(|F_{\text{interferer}}(\text{offset})|/\text{SCS}) + 0.5) * \text{SCS}$ MHz with SCS the sub-carrier spacing of the carrier closest to the interferer in MHz. The interfering signal has the same SCS as that of the closest carrier. +- NOTE 4: The transmitter shall be set to 4 dB below the $P_{\text{UMAX,fc}}$ as defined in clause 6.2.4, with uplink configuration specified in Table 7.3.2.1-2. + +## 7.5A.2 Adjacent channel selectivity for Intra-band non-contiguous CA + +For intra-band non-contiguous carrier aggregation with two component carriers, two different requirements apply for out-of-gap and in-gap. For out-of-gap, the UE shall meet the requirements for each component carrier as specified in clauses 7.5. For in-gap, the requirement applies if the following minimum gap condition is met: + +$$\Delta f_{\text{ACS}} \geq \text{BW}_1/2 + \text{BW}_2/2 + \max(\text{BW}_1, \text{BW}_2),$$ + +where $\Delta f_{\text{ACS}}$ is the frequency separation between the center frequencies of the component carriers and $\text{BW}_k$ are the channel bandwidths of carrier $k$ , $k = 1, 2$ . + +If the minimum gap condition is met, the UE shall meet the requirements specified in clauses 7.5 for each component carrier considered. The respective channel bandwidth of the component carrier under test will be used in the parameter calculations of the requirement. In case of more than two component carriers, the minimum gap condition is computed for any pair of adjacent component carriers following the same approach as the two component carriers. The in-gap requirement for the corresponding pairs shall apply if the minimum gap condition is met. + +For every component carrier to which the requirements apply, the UE shall meet the requirement with one active interferer signal (in-gap or out-of-gap) while all downlink carriers are active and the input power shall be distributed among the active DL CCs so their PSDs are aligned with each other. + +## 7.5A.3 Adjacent channel selectivity for Inter-band CA + +For inter-band carrier aggregation with one component carrier per operating band and the uplink assigned to one NR band, the adjacent channel requirements are defined with the uplink active on the band other than the band whose downlink is being tested. The UE shall meet the requirements specified in clause 7.5 for each component carrier while all downlink carriers are active. The requirement does not apply if the interferer of the band being tested overlaps any part of the component carrier on the other band. + +For the combination of intra-band and inter-band carrier aggregation and uplink carrier(s) assigned to one NR band, the requirement is defined with the uplink active on the band other than the band whose downlink is being tested. The UE shall meet the requirements specified in clauses 7.5A.1 and 7.5A.2 for each band while all downlink carriers are active. + +## 7.5D Void + +## 7.6 Blocking characteristics + +### 7.6.1 General + +The blocking characteristic is a measure of the receiver's ability to receive a wanted signal at its assigned channel frequency in the presence of an unwanted interferer on frequencies other than those of the spurious response or the adjacent channels, without this unwanted input signal causing a degradation of the performance of the receiver beyond a specified limit. The blocking performance shall apply at all frequencies except those at which a spurious response occurs. + +The requirement applies at the RIB when the AoA of the incident wave of the wanted signal and the interfering signal are both from the direction where peak gain is achieved. + +The wanted and interfering signals apply to all supported polarizations, under the assumption of polarization match. + +## 7.6.2 In-band blocking + +In-band blocking is a measure of a receiver's ability to receive a NR signal at its assigned channel frequency in the presence of an interferer at a given frequency offset from the centre frequency of the assigned channel. + +The throughput shall be $\geq 95$ % of the maximum throughput of the reference measurement channels as specified in Annexes A.2.3.2 and A.3.3.2 (with one sided dynamic OCNG Pattern OP.1 TDD for the DL-signal as described in Annex A.5.2.1). The requirement is verified with the test metric of EIS (Link=RX beam peak direction, Meas=Link angle). + +**Table 7.6.2-1: In band blocking requirements** + +| Rx parameter | Units | Channel bandwidth | | | | | | | +|----------------------------------------------------|-------|-------------------------------------------------------|-------------------------------------------------------|---------------------------------------------------------|---------------------------------------------------------|---------------------------------------------------------|---------------------------------------------------------|-----------------------------------------------------------| +| | | 50 MHz | 100 MHz | 200 MHz | 400 MHz | 800 MHz | 1600 MHz | 2000 MHz | +| Power in Transmission Bandwidth Configuration | dBm | REFSENS + 14 dB | | | | | | | +| BW interferer | MHz | 50 | 100 | 200 | 400 | 800 | 1600 | 2000 | +| P interferer for bands n257, n258, n261 | dBm | REFSENS + 35.5 dB | REFSENS + 35.5 dB | REFSENS + 35.5 dB | REFSENS + 35.5 dB | N/A | N/A | N/A | +| P interferer for bands n259, n260, n262 | dBm | REFSENS + 34.5 dB | REFSENS + 34.5 dB | REFSENS + 34.5 dB | REFSENS + 34.5 dB | N/A | N/A | N/A | +| P interferer for band n263 | dBm | N/A | REFSENS + 33.5 dB | N/A | REFSENS + 33.5 dB | REFSENS + 33.5 dB | REFSENS + 33.5 dB | REFSENS + 33.5 dB | +| F interferer (offset) | MHz | $\leq -100$ & $\geq 100$
NOTE 5 | $\leq -200$ & $\geq 200$
NOTE 5 | $\leq -400$ & $\geq 400$
NOTE 5 | $\leq -800$ & $\geq 800$
NOTE 5 | $\leq -1600$ & $\geq 1600$
NOTE 5 | $\leq -3200$ & $\geq 3200$ | $\leq -4000$ & $\geq 4000$ | +| F interferer | MHz | F DL_low + 25 to F DL_high - 25 | F DL_low + 50 to F DL_high - 50 | F DL_low + 100 to F DL_high - 100 | F DL_low + 200 to F DL_high - 200 | F DL_low + 400 to F DL_high - 400 | F DL_low + 800 to F DL_high - 800 | F DL_low + 1600 to F DL_high - 1600 | + +NOTE 1: The interferer consists of the Reference measurement channel specified in Annex A.3.3.2 with one sided dynamic OCNG Pattern OP.1. TDD as described in Annex A.5.2.1 and set-up according to Annex C. + +NOTE 2: The REFSENS power level is specified in Clause 7.3.2, which are applicable according to different UE power classes. + +NOTE 3: The wanted signal consists of the reference measurement channel specified in Annex A.3.3.2 with one sided dynamic OCNG pattern OP.1 TDD as described in Annex A.5.2.1 and set-up according to Annex C. + +NOTE 4: Void + +NOTE 5: The absolute value of the interferer offset Finterferer (offset) shall be further adjusted $(\text{CEIL}(|F_{\text{interferer}}(\text{offset})|/\text{SCS}) + 0.5) * \text{SCS}$ MHz with SCS the sub-carrier spacing of the wanted signal in MHz. Wanted and interferer signal have same SCS. + +NOTE 6: Finterferer range values for unwanted modulated interfering signals are interferer center frequencies. + +NOTE 7: The transmitter shall be set to 4 dB below the PUMAX,f,c as defined in clause 6.2.4, with uplink configuration specified in Table 7.3.2.1-2. + +## 7.6.3 Void + +## 7.6A Blocking characteristics for DL CA + +### 7.6A.1 General + +### 7.6A.2 In-band blocking + +**Table 7.6A.2-1: Void** + +**Table 7.6A.2-2: Void** + +7.6A.2.1 In-band blocking for Intra-band contiguous CA For intra-band contiguous carrier aggregation, the SCC(s) shall be configured at nominal channel spacing to the PCC. The input power shall be distributed among the active DL CCs so their PSDs are aligned with each other. The UE shall fulfil the minimum requirement specified in Table 7.6A.2-1 for in the presence of an interferer at a given frequency offset from the centre frequency of the assigned channel and an interferer power shall not exceed -25 dBm. The throughput of each carrier shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in Annexes A.2.3.2 and A.3.3.2 (with one sided dynamic OCNG Pattern OP.1 TDD for the DL-signal as described in Annex A.5.2.1). The requirement is verified with the test metric of EIS (Link=RX beam peak direction, Meas=Link angle). + +**Table 7.6A.2.1-1: In band blocking minimum requirements for intra-band contiguous CA** + +| Rx Parameter | Units | All CA bandwidth classes | +|-------------------------------------------------------|-------|-------------------------------------------------------------------------------------------------------------------------------------------| +| Power in Transmission Bandwidth Configuration, per CC | dBm | REFSENS + 14 dB | +| P interferer for bands n257, n258, n261 | dBm | Aggregated power + 21.5 dB | +| P interferer for bands n260, n262 | dBm | Aggregated power + 20.5 dB | +| P interferer for band n263 | dBm | Aggregated power + 19.5 dB | +| BW interferer | MHz | BW Channel_CA | +| F interferer (offset) | MHz | $+2 \cdot \text{BW}_{\text{Channel\_CA}} / -2 \cdot \text{BW}_{\text{Channel\_CA}}$
NOTE 5 | +| F interferer | MHz | $F_{\text{DL\_low}} + 0.5 \cdot \text{BW}_{\text{Channel\_CA}}$
To
$F_{\text{DL\_high}} - 0.5 \cdot \text{BW}_{\text{Channel\_CA}}$ | + +NOTE 1: The interferer consists of the Reference measurement channel specified in Annex A.3.3.2 with one sided dynamic OCNG Pattern OP.1 TDD as described in Annex A.5.2.1. and set-up according to Annex C. + +NOTE 2: The REFSENS power level is specified in Table 7.3.2-1. + +NOTE 3: The wanted signal consists of the reference measurement channel specified in Annex A.3.3.2 QPSK, R=1/3 with one sided dynamic OCNG pattern OP.1 TDD as described in Annex A.5.2.1 and set-up according to Annex C. + +NOTE 4: The Finterferer (offset) is the frequency separation between the center of the aggregated CA bandwidth and the center frequency of the Interferer signal. + +NOTE 5: The absolute value of the interferer offset Finterferer (offset) shall be further adjusted to $(\text{CEIL}(|F_{\text{interferer}}(\text{offset})|/\text{SCS}) + 0.5) \cdot \text{SCS}$ MHz with SCS the sub-carrier spacing of the carrier closest to the interferer in MHz. The interfering signal has the same SCS as that of the closest carrier. + +NOTE 6: Finterferer range values for unwanted modulated interfering signals are interferer center frequencies. + +NOTE 7: The transmitter shall be set to 4 dB below the PUMAX,fc as defined in clause 6.2.4, with uplink configuration specified in Table 7.3.2.1-2. + +### 7.6A.2.2 In-band blocking for Intra-band non-contiguous CA + +For intra-band non-contiguous carrier aggregation with two component carriers, the requirement applies to out-of-gap and in-gap. For out-of-gap, the UE shall meet the requirements for each component carrier with parameters as specified + +in 7.6.2-1. The requirement associated to the maximum channel between across the component carriers is selected. For in-gap, the requirement shall apply if the following minimum gap condition is met: + +$$\Delta f_{IBB} \geq 0.5(BW_1 + BW_2) + 2 \max(BW_1, BW_2),$$ + +where $\Delta f_{IBB}$ is the frequency separation between the center frequencies of the component carriers and $BW_k$ are the channel bandwidths of carrier $k$ , $k = 1, 2$ . + +If the minimum gap condition is met, the UE shall meet the requirement specified in Table 7.6.2-1 for each component carrier. The respective channel bandwidth of the component carrier under test will be used in the parameter calculations of the requirement. In case of more than two component carriers, the minimum gap condition is computed for any pair of adjacent component carriers following the same approach as the two component carriers. The in-gap requirement for the corresponding pairs shall apply if the minimum gap condition is met. For every component carrier to which the requirements apply, the UE shall meet the requirement with one active interferer signal (in-gap or out-of-gap) while all downlink carriers are active and the input power shall be distributed among the active DL CCs so their PSDs are aligned with each other. + +### 7.6A.2.3 In-band blocking for Inter-band CA + +For inter-band carrier aggregation with one component carrier per operating band and the uplink assigned to one NR band, the in-band blocking requirements are defined with the uplink active on the band other than the band whose downlink is being tested. The UE shall meet the requirements specified in clause 7.6.2 for each component carrier while all downlink carriers are active. The requirement does not apply if the interferer of the band being tested overlaps any part of the component carrier on the other band. + +For the combination of intra-band and inter-band carrier aggregation and uplink carrier(s) assigned to one NR band, the requirement is defined with the uplink active on the band other than the band whose downlink is being tested. The UE shall meet the requirements specified in clauses 7.6A.2.1 and 7.6A.2.2 for each band while all downlink carriers are active. + +## 7.6D Void + +## 7.7 Void + +## 7.8 Void + +## 7.9 Spurious emissions + +The spurious emissions power is the power of emissions generated or amplified in a receiver. The spurious emissions power level is measured as TRP. + +The power of any narrow band CW spurious emission shall not exceed the maximum level specified in Table 7.9-1. The requirement is verified in beam locked mode with the test metric of TRP (Link=TX beam peak direction, Meas=TRP grid). + +**Table 7.9-1: General receiver spurious emission requirements** + +| Frequency range | Measurement bandwidth | Maximum level | NOTE | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------|------| +| $30\text{MHz} \leq f < 1\text{GHz}$ | 100 kHz | -57 dBm
(NOTE 2) | 1 | +| $1\text{GHz} \leq f \leq 2^{\text{nd}}$ harmonic of the upper frequency edge of the DL operating band in GHz | 1 MHz | -47 dBm
(NOTE 3) | | +| NOTE 1: Unused PDCCH resources are padded with resource element groups with power level given by PDCCH as defined in Annex C.3.1.
NOTE 2: This maximum level does not apply for Band n263 for which -36 dBm applies.
NOTE 3: This maximum level does not apply for Band n263 for which -30 dBm applies. | | | | + +## 7.10 Void + +--- + +## Annex A (normative): Measurement channels + +--- + +### A.1 General + +--- + +### A.2 UL reference measurement channels + +#### A.2.1 General + +#### A.2.2 Void + +## A.2.3 Reference measurement channels for TDD + +For UL RMCs defined below, TDD slot pattern defined in Table A.2.3-1 will be used for the requirements requiring at least one sub frame (1ms) for the measurement period. For other requirements, TDD slot patterns defined for reference sensitivity tests in Table A.3.3.1-1 will be used. + +**Table A.2.3-1: Additional reference channels parameters for TDD** + +| Parameter | Value | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------|----------------------------------------------|--------------------------------------|--------------------------------------| +| | SCS 60 kHz
( $\mu=2$ ) | SCS 120 kHz
( $\mu=3$ ) | SCS 480 kHz
( $\mu=5$ ) | SCS 960 kHz
( $\mu=6$ ) | +| TDD Slot Configuration pattern (Note 1) | DDDSUUUU | 7DS8U | 31DS32U | 63DS64U | +| Special Slot Configuration (Note 2) | S=4D+6G+4U | S=12D+2G | S=2D+12G | S=2D+12G | +| referenceSubcarrierSpacing | 60 kHz | 120 kHz | 480 kHz | 960 kHz | +| UL-DL configuration | dl-UL-TransmissionPeriodicity | 2 ms | 2 ms | 2 ms | +| | nrofDownlinkSlots | 3 | 7 | 31 | +| | nrofDownlinkSymbols | 4 | 12 | 2 | +| | nrofUplinkSlot | 4 | 8 | 32 | +| | nrofUplinkSymbols | 4 | 0 | 0 | +| Indexes of active UL slots | mod(slot index, 40) = {36,...,39} | mod(slot index, 80) = {72,...,79} | mod(slot index, 320) = {288,...,319} | mod(slot index, 640) = {576,...,639} | +| Indexes of active UL slots for UL Gap test | mod(slot index, 40) = {12,...,15, 36,...,39} | mod(slot index, 80) = {24,...,31, 72,...,79} | | | +| Indexes of the UL slots for UL Gap when UL gap pattern configuration 3 (IE UL-GapFR2-Config-r17 ) is configured | mod(slot index, 40) = {7, 28} | mod(slot index, 80) = {15, 56} | | | +| Indexes of the UL slots for UL Gap when UL gap pattern configuration 1 (IE UL-GapFR2-Config-r17 ) is configured | mod(slot index, 160) = {20, 21, 22, 23, 28, 29, 30, 31} | mod(slot index, 320) = {8, ..., 15} | | | +| NOTE 1: D denotes a slot with all DL symbols; S denotes a slot with a mix of DL, UL and guard symbols; U denotes a slot with all UL symbols. The field is for information. | | | | | +| NOTE 2: D, G, U denote DL, guard and UL symbols, respectively. The field is for information. | | | | | + +### A.2.3.1 DFT-s-OFDM Pi/2-BPSK + +**Table A.2.3.1-1: Reference Channels for DFT-s-OFDM pi/2-BPSK** + +| Parameter | Allocated | DFT-s- | Modulation | MCS | Payload | Transpor | LDPC | Number | Total | Total | +|-----------|-----------|--------|------------|-----|---------|----------|------|--------|-------|-------| +|-----------|-----------|--------|------------|-----|---------|----------|------|--------|-------|-------| + +Table A.2.3.1-2: + +| | resource blocks ( $L_{CRB}$ ) | OFDM Symbols per slot (Note 1) | | Index (Note 2) | size | t block CRC | Base Graph | of code blocks per slot (Note 3) | number of bits per slot | modulated symbols per slot | +|------|-------------------------------|--------------------------------|-----------|----------------|------|-------------|------------|----------------------------------|-------------------------|----------------------------| +| Unit | | | | | Bits | Bits | | | Bits | | +| | 1 | 11 | pi/2 BPSK | 0 | 24 | 16 | 2 | 1 | 132 | 132 | +| | 16 | 11 | pi/2 BPSK | 0 | 504 | 16 | 2 | 1 | 2112 | 2112 | +| | 32 | 11 | pi/2 BPSK | 0 | 1032 | 16 | 2 | 1 | 4224 | 4224 | +| | 60 | 11 | pi/2 BPSK | 0 | 1864 | 16 | 2 | 1 | 7920 | 7920 | +| | 64 | 11 | pi/2 BPSK | 0 | 2024 | 16 | 2 | 1 | 8448 | 8448 | +| | 120 | 11 | pi/2 BPSK | 0 | 3752 | 16 | 2 | 1 | 15840 | 15840 | +| | 128 | 11 | pi/2 BPSK | 0 | 3976 | 24 | 2 | 2 | 16896 | 16896 | +| | 144 | 11 | pi/2 BPSK | 0 | 4488 | 24 | 2 | 2 | 19008 | 19008 | +| | 243 | 11 | pi/2 BPSK | 0 | 7560 | 24 | 2 | 2 | 32076 | 32076 | +| | 256 | 11 | pi/2 BPSK | 0 | 7944 | 24 | 2 | 3 | 33792 | 33792 | + +Void + +A.2.3.2 + +Table A.2.3.2-1: Channels for QPSK + +DFT-s-OFDM QPSK +Reference DFT-s-OFDM + +Table A.2.3.2-2: + +| Parameter | Allocated resource blocks ( $L_{CRB}$ ) | DFT-s-OFDM Symbols per slot (Note 1) | Modulation | MCS Index | Payload size | Transport block CRC | LDPC Base Graph | Number of code blocks per slot (Note 3) | Total number of bits per slot | Total modulated symbols per slot | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|--------------------------------------|------------|-----------|--------------|---------------------|-----------------|-----------------------------------------|-------------------------------|----------------------------------| +| NOTE 1: PUSCH mapping Type-A and single-symbol DM-RS configuration Type-1 with 2 additional DM-RS symbols, such that the DM-RS positions are set to symbols 2, 7, 11. DMRS is [TDM'ed] with PUSCH data. DM-RS symbols are not counted. | | | | | | | | | | | +| NOTE 2: MCS Index is based on MCS table 6.1.4.1-1 defined in 38.214. | | | | | | | | | | | +| NOTE 3: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to each Code Block (otherwise L = 0 Bit) | | | | | | | | | | | +| NOTE 4: Indexes of active UL slots are given by Table A.2.3-1 with TDD UL-DL configuration specified in A.2.3 for the requirements requiring at least one sub frame (1ms) for the measurement period. For other requirements, indexes of active UL slots are given by the slots satisfying $\text{mod}(\text{slot index}+1, 5) = 0$ with TDD UL-DL configuration specified in A.3.3.1. | | | | | | | | | | | +| Unit | | | | | Bits | Bits | | | Bits | | + +Void + +A.2.3.3 + +Table A.2.3.3-1: Channels for 16QAM + +DFT-s-OFDM 16QAM +Reference DFT-s-OFDM + +| Parameter | Allocated resource blocks ( $L_{CRB}$ ) | DFT-s-OFDM Symbols per slot (Note 1) | Modulation | MCS Index | Payload size | Transport block CRC | LDPC Base Graph | Number of code blocks per slot (Note 3) | Total number of bits per slot | Total modulated symbols per slot | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|--------------------------------------|------------|-----------|--------------|---------------------|-----------------|-----------------------------------------|-------------------------------|----------------------------------| +| NOTE 1: PUSCH mapping Type-A and single-symbol DM-RS configuration Type-1 with 2 additional DM-RS symbols, such that the DM-RS positions are set to symbols 2, 7, 11. DMRS is [TDM'ed] with PUSCH data. DM-RS symbols are not counted. | | | | | | | | | | | +| NOTE 2: MCS Index is based on MCS table 6.1.4.1-1 defined in 38.214. | | | | | | | | | | | +| NOTE 3: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to each Code Block (otherwise L = 0 Bit) | | | | | | | | | | | +| NOTE 4: Indexes of active UL slots are given by Table A.2.3-1 with TDD UL-DL configuration specified in A.2.3 for the requirements requiring at least one sub frame (1ms) for the measurement period. For other requirements, indexes of active UL slots are given by the slots satisfying $\text{mod}(\text{slot index}+1, 5) = 0$ with TDD UL-DL configuration specified in A.3.3.1. | | | | | | | | | | | +| Unit | | | | | Bits | Bits | | | Bits | | +| | 16 | 11 | QPSK | 2 | 808 | 16 | 2 | 1 | 4224 | 2112 | +| | 20 | 11 | QPSK | 2 | 1032 | 16 | 2 | 1 | 5280 | 2640 | +| | 32 | 11 | QPSK | 2 | 1608 | 16 | 2 | 1 | 8448 | 4224 | +| | 60 | 11 | QPSK | 2 | 2976 | 16 | 2 | 1 | 15840 | 7920 | +| | 64 | 11 | QPSK | 2 | 3240 | 16 | 2 | 1 | 16896 | 8448 | +| | 120 | 11 | QPSK | 2 | 5896 | 24 | 2 | 2 | 31680 | 15840 | +| | 128 | 11 | QPSK | 2 | 6408 | 24 | 2 | 2 | 33792 | 16896 | +| | 144 | 11 | QPSK | 2 | 7176 | 24 | 2 | 2 | 38016 | 19008 | +| | 243 | 11 | QPSK | 2 | 12040 | 24 | 2 | 4 | 64152 | 32076 | +| | 256 | 11 | QPSK | 2 | 12808 | 24 | 2 | 4 | 67584 | 33792 | +| NOTE 1: PUSCH mapping Type-A and single-symbol DM-RS configuration Type-1 with 2 additional DM-RS symbols, such that the DM-RS positions are set to symbols 2, 7, 11. DMRS is [TDM'ed] with PUSCH data. DM-RS symbols are not counted. | | | | | | | | | | | +| NOTE 2: MCS Index is based on MCS table 6.1.4.1-1 defined in 38.214. | | | | | | | | | | | +| NOTE 3: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to each Code Block (otherwise L = 0 Bit) | | | | | | | | | | | +| NOTE 4: Indexes of active UL slots are given by Table A.2.3-1 with TDD UL-DL configuration specified in A.2.3 for the requirements requiring at least one sub frame (1ms) for the measurement period. For other requirements, indexes of active UL slots are given by the slots satisfying $\text{mod}(\text{slot index}+1, 5) = 0$ with TDD UL-DL configuration specified in A.3.3.1. | | | | | | | | | | | +| Unit | | | | | Bits | Bits | | | Bits | | +| | 16 | 11 | 16QAM | 10 | 2792 | 16 | 2 | 2 | 14784 | 2792 | +| | 20 | 11 | 16QAM | 10 | 3480 | 16 | 2 | 2 | 18408 | 3480 | +| | 32 | 11 | 16QAM | 10 | 5632 | 16 | 2 | 2 | 29808 | 5632 | +| | 60 | 11 | 16QAM | 10 | 10504 | 24 | 1 | 2 | 31680 | 7920 | + +Table A.2.3.3-2: + +| | | | | | | | | | | | +|--|-----|----|-------|----|-------|----|---|---|--------|-------| +| | 64 | 11 | 16QAM | 10 | 11272 | 24 | 1 | 2 | 33792 | 8448 | +| | 120 | 11 | 16QAM | 10 | 21000 | 24 | 1 | 3 | 63360 | 15840 | +| | 128 | 11 | 16QAM | 10 | 22536 | 24 | 1 | 3 | 67584 | 16896 | +| | 144 | 11 | 16QAM | 10 | 25104 | 24 | 1 | 3 | 76032 | 19008 | +| | 243 | 11 | 16QAM | 10 | 43032 | 24 | 1 | 6 | 128304 | 32076 | +| | 256 | 11 | 16QAM | 10 | 45096 | 24 | 1 | 6 | 135168 | 33792 | + +Void + +A.2.3.4 + +- NOTE 1: PUSCH mapping Type-A and single-symbol DM-RS configuration Type-1 with 2 additional DM-RS symbols, such that the DM-RS positions are set to symbols 2, 7, 11. DMRS is [TDM'ed] with PUSCH data. DM-RS symbols are not counted. +- NOTE 2: MCS Index is based on MCS table 6.1.4.1-1 defined in 38.214. +- NOTE 3: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to each Code Block (otherwise L = 0 Bit) +- NOTE 4: Indexes of active UL slots are given by Table A.2.3-1 with TDD UL-DL configuration specified in A2.3 for the requirements requiring at least one sub frame (1ms) for the measurement period. For other requirements, indexes of active UL slots are given by the slots satisfying $\text{mod}(\text{slot index}+1, 5) = 0$ with TDD UL-DL configuration specified in A.3.3.1. +- NOTE 5: The RMCs apply to all channel bandwidth where $L_{\text{CRB}} \leq N_{\text{RB}}$ . + +DFT-s-OFDM +64QAM + +Table A.2.3.4-1: +Channels for +64QAM + +Reference +DFT-s-OFDM + +Table A.2.3.4-2: + +| Parameter | Allocated resource blocks ( $L_{\text{CRB}}$ ) | DFT-s-OFDM Symbols per slot (Note 1) | Modulation | MCS Index (Note 2) | Payload size | Transport block CRC | LDPC Base Graph | Number of code blocks per slot (Note 3) | Total number of bits per slot | Total modulated symbols per slot | +|-----------|------------------------------------------------|--------------------------------------|------------|--------------------|--------------|---------------------|-----------------|-----------------------------------------|-------------------------------|----------------------------------| +| Unit | | | | | Bits | Bits | | | Bits | | +| | 1 | 11 | 64QAM | 18 | 408 | 16 | 2 | 1 | 792 | 132 | +| | 16 | 11 | 64QAM | 18 | 6400 | 24 | 1 | 1 | 12672 | 2112 | +| | 32 | 11 | 64QAM | 18 | 12808 | 24 | 1 | 2 | 25344 | 4224 | +| | 60 | 11 | 64QAM | 18 | 24072 | 24 | 1 | 3 | 47520 | 7920 | +| | 64 | 11 | 64QAM | 18 | 25608 | 24 | 1 | 4 | 50688 | 8448 | +| | 120 | 11 | 64QAM | 18 | 48168 | 24 | 1 | 6 | 95040 | 15840 | +| | 128 | 11 | 64QAM | 18 | 51216 | 24 | 1 | 7 | 101376 | 16896 | +| | 144 | 11 | 64QAM | 18 | 57376 | 24 | 1 | 7 | 114048 | 19008 | +| | 243 | 11 | 64QAM | 18 | 96264 | 24 | 1 | 12 | 192456 | 32076 | +| | 256 | 11 | 64QAM | 18 | 102416 | 24 | 1 | 13 | 202752 | 33792 | + +Void + +A.2.3.5 + +Table A.2.3.5-1: +Channels for +QPSK + +CP-OFDM +QPSK + +Reference +CP-OFDM + +| Parameter | Allocated resource blocks ( $L_{\text{CRB}}$ ) | DFT-s-OFDM Symbols per slot (Note 1) | Modulation | MCS Index (Note 2) | Payload size | Transport block CRC | LDPC Base Graph | Number of code blocks per slot (Note 3) | Total number of bits per slot | Total modulated symbols per slot | +|-----------|------------------------------------------------|--------------------------------------|------------|--------------------|--------------|---------------------|-----------------|-----------------------------------------|-------------------------------|----------------------------------| +| Unit | | | | | Bits | Bits | | | Bits | | +| | 1 | 11 | QPSK | 18 | 204 | 16 | 2 | 1 | 396 | 66 | +| | 16 | 11 | QPSK | 18 | 3200 | 24 | 1 | 1 | 6336 | 1056 | +| | 32 | 11 | QPSK | 18 | 6404 | 24 | 1 | 2 | 12672 | 2112 | +| | 60 | 11 | QPSK | 18 | 12036 | 24 | 1 | 3 | 23760 | 3960 | +| | 64 | 11 | QPSK | 18 | 12804 | 24 | 1 | 4 | 25344 | 4224 | +| | 120 | 11 | QPSK | 18 | 24084 | 24 | 1 | 6 | 47520 | 7920 | +| | 128 | 11 | QPSK | 18 | 25608 | 24 | 1 | 7 | 50688 | 8448 | +| | 144 | 11 | QPSK | 18 | 28688 | 24 | 1 | 7 | 57024 | 9504 | +| | 243 | 11 | QPSK | 18 | 48132 | 24 | 1 | 12 | 96216 | 16038 | +| | 256 | 11 | QPSK | 18 | 51208 | 24 | 1 | 13 | 101376 | 16896 | + +**Table A.2.3.5-2:** + +| | | | | | | | | | | | +|--|-----|----|------|---|-------|----|---|---|-------|-------| +| | 62 | 11 | QPSK | 2 | 3104 | 16 | 2 | 1 | 16368 | 8184 | +| | 66 | 11 | QPSK | 2 | 3368 | 16 | 2 | 1 | 17424 | 8712 | +| | 124 | 11 | QPSK | 2 | 6152 | 24 | 2 | 2 | 32736 | 16368 | +| | 132 | 11 | QPSK | 2 | 6536 | 24 | 2 | 2 | 34848 | 17424 | +| | 148 | 11 | QPSK | 2 | 7304 | 24 | 2 | 2 | 39072 | 19536 | +| | 248 | 11 | QPSK | 2 | 12296 | 24 | 2 | 4 | 65472 | 32736 | +| | 264 | 11 | QPSK | 2 | 13064 | 24 | 2 | 4 | 69696 | 34848 | + +Void + +**A.2.3.6** + +NOTE 1: PUSCH mapping Type-A and single-symbol DM-RS configuration Type-1 with 2 additional DM-RS symbols, such that the DM-RS positions are set to symbols 2, 7, 11. DMRS is [TDM'ed] with PUSCH data. DM-RS symbols are not counted. + NOTE 2: MCS Index is based on MCS table 5.1.3.1-1 defined in 38.214. + NOTE 3: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to each Code Block (otherwise L = 0 Bit) + NOTE 4: Indexes of active UL slots are given by Table A.2.3-1 with TDD UL-DL configuration specified in A2.3 for the requirements requiring at least one sub frame (1ms) for the measurement period. For other requirements, indexes of active UL slots are given by the slots satisfying $\text{mod}(\text{slot index}+1, 5) = 0$ with TDD UL-DL configuration specified in A.3.3.1. + NOTE 5: The RMCs apply to all channel bandwidth where $L_{\text{CRB}} \leq N_{\text{RB}}$ . + +CP-OFDM +16QAM + +**Table A.2.3.6-1:** +Channels for 16QAM + +Reference CP-OFDM + +**Table A.2.3.6-2:** + +| Parameter | Allocated resource blocks ( $L_{\text{CRB}}$ ) | DFT-s-OFDM Symbols per slot (Note 1) | Modulation | MCS Index (Note 2) | Payload size | Transport block CRC | LDPC Base Graph | Number of code blocks per slot (Note 3) | Total number of bits per slot | Total modulated symbols per slot | +|-----------|------------------------------------------------|--------------------------------------|------------|--------------------|--------------|---------------------|-----------------|-----------------------------------------|-------------------------------|----------------------------------| +| Unit | | | | | Bits | Bits | | | Bits | | +| | 1 | 11 | 16QAM | 10 | 176 | 16 | 2 | 1 | 528 | 132 | +| | 16 | 11 | 16QAM | 10 | 2792 | 16 | 2 | 1 | 8448 | 2112 | +| | 32 | 11 | 16QAM | 10 | 5632 | 24 | 1 | 1 | 16896 | 4224 | +| | 33 | 11 | 16QAM | 10 | 5760 | 24 | 1 | 1 | 17424 | 4356 | +| | 62 | 11 | 16QAM | 10 | 10760 | 24 | 1 | 2 | 32736 | 8184 | +| | 66 | 11 | 16QAM | 10 | 11528 | 24 | 1 | 2 | 34848 | 8712 | +| | 124 | 11 | 16QAM | 10 | 21504 | 24 | 1 | 3 | 65472 | 16368 | +| | 132 | 11 | 16QAM | 10 | 23040 | 24 | 1 | 3 | 69696 | 17424 | +| | 148 | 11 | 16QAM | 10 | 26120 | 24 | 1 | 4 | 78144 | 19536 | + +Void + +**A.2.3.7** + +NOTE 1: PUSCH mapping Type-A and single-symbol DM-RS configuration Type-1 with 2 additional DM-RS symbols, such that the DM-RS positions are set to symbols 2, 7, 11. DMRS is [TDM'ed] with PUSCH data. DM-RS symbols are not counted. + NOTE 2: MCS Index is based on MCS table 5.1.3.1-1 defined in 38.214. + NOTE 3: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to each Code Block (otherwise L = 0 Bit) + NOTE 4: Indexes of active UL slots are given by Table A.2.3-1 with TDD UL-DL configuration specified in A2.3 for the requirements requiring at least one sub frame (1ms) for the measurement period. For other requirements, indexes of active UL slots are given by the slots satisfying $\text{mod}(\text{slot index}+1, 5) = 0$ with TDD UL-DL configuration specified in A.3.3.1. + NOTE 5: The RMCs apply to all channel bandwidth where $L_{\text{CRB}} \leq N_{\text{RB}}$ . + +CP-OFDM +64QAM + +**Table A.2.3.7-1:** +Channels for 64QAM + +Reference CP-OFDM + +| Parameter | Allocated resource blocks ( $L_{\text{CRB}}$ ) | DFT-s-OFDM Symbols per slot (Note 1) | Modulation | MCS Index (Note 2) | Payload size | Transport block CRC | LDPC Base Graph | Number of code blocks per slot (Note 3) | Total number of bits per slot | Total modulated symbols per slot | +|-----------|------------------------------------------------|--------------------------------------|------------|--------------------|--------------|---------------------|-----------------|-----------------------------------------|-------------------------------|----------------------------------| +| Unit | | | | | Bits | Bits | | | Bits | | +| | 1 | 11 | 64QAM | 10 | 264 | 24 | 2 | 1 | 792 | 198 | +| | 16 | 11 | 64QAM | 10 | 4608 | 24 | 2 | 1 | 13824 | 3456 | +| | 32 | 11 | 64QAM | 10 | 9216 | 24 | 1 | 1 | 27648 | 6912 | +| | 33 | 11 | 64QAM | 10 | 9504 | 24 | 1 | 1 | 28512 | 7128 | +| | 62 | 11 | 64QAM | 10 | 16512 | 24 | 1 | 2 | 49536 | 12384 | +| | 66 | 11 | 64QAM | 10 | 17568 | 24 | 1 | 2 | 52704 | 13176 | +| | 124 | 11 | 64QAM | 10 | 33024 | 24 | 1 | 3 | 99072 | 24768 | +| | 132 | 11 | 64QAM | 10 | 35136 | 24 | 1 | 3 | 105408 | 26352 | +| | 148 | 11 | 64QAM | 10 | 39360 | 24 | 1 | 4 | 118080 | 29520 | + +Table + +| | | | | | | | | | | | +|--|-----|----|-------|----|--------|----|---|----|--------|-------| +| | 62 | 11 | 64QAM | 19 | 24576 | 24 | 1 | 3 | 49104 | 8184 | +| | 66 | 11 | 64QAM | 19 | 26120 | 24 | 1 | 4 | 52272 | 8712 | +| | 124 | 11 | 64QAM | 19 | 49176 | 24 | 1 | 6 | 98208 | 16368 | +| | 132 | 11 | 64QAM | 19 | 53288 | 24 | 1 | 7 | 104544 | 17424 | +| | 148 | 11 | 64QAM | 19 | 59432 | 24 | 1 | 8 | 117216 | 19536 | +| | 248 | 11 | 64QAM | 19 | 98376 | 24 | 1 | 12 | 196416 | 32736 | +| | 264 | 11 | 64QAM | 19 | 106576 | 24 | 1 | 13 | 209088 | 34848 | + +A.2.3.7-2: Void + +NOTE 1: PUSCH mapping Type-A and single-symbol DM-RS configuration Type-1 with 2 additional DM-RS symbols, such that the DM-RS positions are set to symbols 2, 7, 11. DMRS is [TDM'ed] with PUSCH data. DM-RS symbols are not counted. + +NOTE 2: MCS Index is based on MCS table 5.1.3.1-1 defined in 38.214. + +NOTE 3: If more than one Code Block is present, an additional CRC sequence of $L = 24$ Bits is attached to each Code Block (otherwise $L = 0$ Bit) + +NOTE 4: Indexes of active UL slots are given by Table A.2.3-1 with TDD UL-DL configuration specified in A2.3 for the requirements requiring at least one sub frame (1ms) for the measurement period. For other requirements, indexes of active UL slots are given by the slots satisfying $\text{mod}(\text{slot index}+1, 5) = 0$ with TDD UL-DL configuration specified in A.3.3.1. + +NOTE 5: The RMCs apply to all channel bandwidth where $L_{\text{CRB}} \leq N_{\text{RB}}$ . + +## A.3 DL reference measurement channels + +### A.3.1 General + +Unless otherwise stated, Tables A.3.3.2-1 and A.3.3.2-2 are applicable for measurements of the Receiver Characteristics (clause 7). + +Unless otherwise stated, Tables A.3.3.2-1 and A.3.3.2-2 also apply for the modulated interferer used in Clauses 7.5 and 7.6 with test specific bandwidths. + +CSI-RS configuration parameter defined in Table A.3.1-2 and Table A.3.1-3 are used for verifying the beam correspondence requirement, 2 slots of CSI-RS shall be provided at each test grid point. The DL channel shall be configured for zero power on all tones except those used by CSI-RS in slots containing CSI-RS for beam refinement, and the DL and UL channel sizes shall be the same during verification. + +**Table A.3.1-1: Test parameters** + +| Parameter | Unit | Value | +|----------------------------------------------|--------------------------------------------------------|-------------------------------------------------------------------------------------------------------| +| CORESET frequency domain allocation | | Full BW | +| CORESET time domain allocation | | 2 OFDM symbols at the begin of each slot | +| PDSCH mapping type | | Type A | +| PDSCH start symbol index (S) | | 2 | +| Number of consecutive PDSCH symbols (L) | | 12 | +| PDSCH PRB bundling | PRBs | 2 | +| Dynamic PRB bundling | | false | +| MCS table for TBS determination | | 64QAM | +| Overhead value for TBS determination | | 0 | +| First DMRS position for Type A PDSCH mapping | | 2 | +| DMRS type | | Type 1 | +| Number of additional DMRS | | 2 | +| FDM between DMRS and PDSCH | | Disable | +| CSI-RS for tracking | First subcarrier index in the PRB used for CSI-RS (k0) | 0 for CSI-RS resource 1,2 | +| | OFDM symbols in the PRB used for CSI-RS | $l_0 = 8$ for CSI-RS resource 1
$l_0 = 12$ for CSI-RS resource 2 | +| | Number of CSI-RS ports | 1 for CSI-RS resource 1,2 | +| | CDM Type | 'No CDM' for CSI-RS resource 1,2 | +| | Density (p) | 3 for CSI-RS resource 1,2 | +| | CSI-RS periodicity | Slots
60 kHz SCS: 80 for CSI-RS resources 1 and 2
120 kHz SCS: 160 for CSI-RS resources 1 and 2 | +| | CSI-RS offset | Slots
60 kHz SCS: 40 for CSI-RS resources 1 and 2
120 kHz SCS: 80 for CSI-RS resources 1 and 2 | +| | Frequency Occupation | Start PRB 0
Number of PRB = BWP size | +| | QCL info | TCI state #0 | +| PTRS configuration | | PTRS is not configured | + +**Table A.3.1-2: CSI-RS parameters for beam correspondence based on SSB and CSI-RS** + +| Resource Type | aperiodic | +|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Resource Set Config | | +| repetition | on | +| aperiodicTriggeringOffset | Depending on UE capability | +| Resource Config | | +| nzp-CSI-RS-ResourceId | 30 for resource #0
31 for resource #1
32 for resource #2
33 for resource #3
34 for resource #4
35 for resource #5
36 for resource #6
37 for resource #7 | +| powerControlOffset | 0 | +| powerControlOffsetSS | db0 | +| nrofPorts | 1 | +| firstOFDMSymbolInTimeDomain | 6 for resource #0
7 for resource #1
8 for resource #2
9 for resource #3
10 for resource #4
11 for resource #5
12 for resource #6
13 for resource #7 | +| cdm-Type | noCDM | +| density | 3 | +| nrofRBs | 48 for channel bandwidth $\geq$ 100MHz
32 for channel bandwidth=50MHz | +| qcl-info | Type D to SSB | + +CSI-RS configuration parameter defined in Table A.3.1-3 is used for verifying the beam correspondence requirement, CSI-RS shall be provided once every 10msec. + +**Table A.3.1-3: CSI-RS parameters for CSI-RS based beam correspondence** + +| Resource Type | aperiodic | +|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Resource Set Config | | +| repetition | on | +| aperiodicTriggeringOffset | Depending on UE capability | +| Resource Config | | +| nzp-CSI-RS-ResourceId | 30 for resource #0
31 for resource #1
32 for resource #2
33 for resource #3
...
...
...
29+N for resource #(N-1), where N is maxNumberRxBeam in UE capability IE of MIMO-ParametersPerBand | +| powerControlOffset | 0 | +| powerControlOffsetSS | db0 | +| nrofPorts | 1 | +| firstOFDMSymbolInTimeDomain | 6 for resource #0
7 for resource #1
8 for resource #2
9 for resource #3
...
...
...
5+N for resource #(N-1), where N= maxNumberRxBeam -1 in UE capability IE of MIMO-ParametersPerBand | +| cdm-Type | noCDM | +| density | 3 | +| nrofRBs | 48 for channel bandwidth $\geq$ 100MHz
32 for channel bandwidth=50MHz | +| qcl-info | Type D to SSB | + +## A.3.2 Void + +## A.3.3 DL reference measurement channels for TDD + +### A.3.3.1 General + +**Table A.3.3.1-1. Additional test parameters for TDD** + +| Parameter | Value | | | | | +|-----------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------| +| | SCS 60 kHz
( $\mu=2$ ) | SCS 120 kHz
( $\mu=3$ ) | SCS 480 kHz
( $\mu=5$ ) | SCS 960 kHz
( $\mu=6$ ) | | +| TDD Slot Configuration pattern (Note 1) | DDDSU | DDDSU | DDDSU | DDDSU | | +| Special Slot Configuration (Note 2) | S=4D+6G+4U | S=10D+2G+2U | S=10D+2G+2U | S=10D+2G+2U | | +| referenceSubcarrierSpacing | 60 kHz | 120 kHz | 480 kHz | 960 kHz | | +| UL-DL configuration | dl-UL-TransmissionPeriodicity | 1.25 ms | 0.625 ms | 0.3125 ms | 0.15625 ms | +| | nrofDownlinkSlots | 3 | 3 | 3 | 3 | +| | nrofDownlinkSymbols | 4 | 10 | 10 | 10 | +| | nrofUplinkSlot | 1 | 1 | 1 | 1 | +| | nrofUplinkSymbols | 4 | 2 | 2 | 2 | +| Number of HARQ Processes | 8 | 8 | 8 | 8 | | +| The number of slots between PDSCH and corresponding HARQ-ACK information (Note 3) | K1 = 4 if $\text{mod}(i,5) = 0$
K1 = 3 if $\text{mod}(i,5) = 1$
K1 = 7 if $\text{mod}(i,5) = 2$
where i is slot index per frame; $i = \{0, \dots, 39\}$ | K1 = 4 if $\text{mod}(i,5) = 0$
K1 = 3 if $\text{mod}(i,5) = 1$
K1 = 7 if $\text{mod}(i,5) = 2$
where i is slot index per frame; $i = \{0, \dots, 79\}$ | K1 = 4 if $\text{mod}(i,5) = 0$
K1 = 3 if $\text{mod}(i,5) = 1$
K1 = 7 if $\text{mod}(i,5) = 2$
where i is slot index per frame; $i = \{0, \dots, 319\}$ | K1 = 4 if $\text{mod}(i,5) = 0$
K1 = 3 if $\text{mod}(i,5) = 1$
K1 = 7 if $\text{mod}(i,5) = 2$
where i is slot index per frame; $i = \{0, \dots, 639\}$ | | + +NOTE 1: D denotes a slot with all DL symbols; S denotes a slot with a mix of DL, UL and guard symbols; U denotes a slot with all UL symbols. The field is for information. + +NOTE 2: D, G, U denote DL, guard and UL symbols, respectively. The field is for information. + +NOTE 3: i is the slot index per frame. + +### A.3.3.2 FRC for receiver requirements for QPSK + +#### A.3.3.2-1 Reference measurement channels for SCS 60 kHz FR2 + +**Table A.3.3.2-1 Fixed Reference Channel for Receiver Requirements (SCS 60 kHz, TDD)** + +| Parameter | Unit | Value | | | +|------------------------------------------------------------------------------------------------|------|---------|---------|---------| +| Channel bandwidth | MHz | 50 | 100 | 200 | +| Subcarrier spacing configuration | | 2 | 2 | 2 | +| Allocated resource blocks | | 66 | 132 | 264 | +| Subcarriers per resource block | | 12 | 12 | 12 | +| Allocated slots per Frame (NOTE 7) | | 23 / 24 | 23 / 24 | 23 / 24 | +| MCS index | | 4 | 4 | 4 | +| Modulation | | QPSK | QPSK | QPSK | +| Target Coding Rate | | 1/3 | 1/3 | 1/3 | +| Maximum number of HARQ transmissions | | 1 | 1 | 1 | +| Information Bit Payload per Slot | | | | | +| For Slots 0 and Slot i, if $\text{mod}(i, 5) = \{3,4\}$ for i from $\{0, \dots, 79\}$ (NOTE 5) | Bits | N/A | N/A | N/A | +| For Slot i, if $\text{mod}(i, 5) = \{0,1,2\}$ for i from $\{1, \dots, 79\}$ (NOTE 6) | Bits | 4224 | 8456 | 16896 | +| Transport block CRC | Bits | 24 | 24 | 24 | +| LDPC base graph | | 1 | 1 | 1 | +| Number of Code Blocks per Slot | | | | | +| For Slots 0 and Slot i, if $\text{mod}(i, 5) = \{3,4\}$ for i from $\{0, \dots, 79\}$ (NOTE 5) | CBs | N/A | N/A | N/A | +| For Slot i, if $\text{mod}(i, 5) = \{0,1,2\}$ for i from $\{1, \dots, 79\}$ (NOTE 6) | CBs | 1 | 2 | 3 | +| Binary Channel Bits Per Slot | | | | | +| For Slots 0 and Slot i, if $\text{mod}(i, 5) = \{3,4\}$ for i from $\{0, \dots, 79\}$ (NOTE 5) | Bits | N/A | N/A | N/A | +| For Slot i, if $\text{mod}(i, 5) = \{0,1,2\}$ for i from $\{1, \dots, 79\}$ (NOTE 6) | Bits | 14256 | 28512 | 57024 | +| Max. Throughput averaged over 1 frame (NOTE 8) | Mbps | 10.138 | 20.294 | 40.550 | + +NOTE 1: Additional parameters are specified in Table A.3.1-1 and Table A.3.3.1-1. +NOTE 2: If more than one Code Block is present, an additional CRC sequence of $L = 24$ Bits is attached to each Code Block (otherwise $L = 0$ Bit). +NOTE 3: SS/PBCH block is transmitted in slot 0 with periodicity 20 ms +NOTE 4: Slot i is slot index per 2 frames +NOTE 5: When this DL RMC used together with the UL RMC for the transmitter requirements requiring at least one sub frame (1ms) for the measurement period, Slot i, if $\text{mod}(i, 8) = \{3,4,5,6,7\}$ for i from $\{0, \dots, 79\}$ together with the TDD UL-DL configuration specified in A2.3. +NOTE 6: When this DL RMC used together with the UL RMC for the transmitter requirements requiring at least one sub frame (1ms) for the measurement period, Slot i, if $\text{mod}(i, 8) = \{0,1,2\}$ for i from $\{0, \dots, 79\}$ together with the TDD UL-DL configuration specified in A2.3. +NOTE 7: First number corresponds to the number slots allocated in the first frame of the RMC; second number corresponds to the number slots allocated in the second frame of the RMC. +NOTE 8: Throughput is averaged over 2nd frame of RMC. + +## A.3.3.2-2 Reference measurement channels for SCS 120 kHz FR2 + +**Table A.3.3.2-2 Fixed Reference Channel for Receiver Requirements (SCS 120 kHz, TDD)** + +| Parameter | Unit | Value | | | | +|------------------------------------------------------------------------------|------|---------|---------|---------|---------| +| Channel bandwidth | MHz | 50 | 100 | 200 | 400 | +| Subcarrier spacing configuration | | 3 | 3 | 3 | 3 | +| Allocated resource blocks | | 32 | 66 | 132 | 264 | +| Subcarriers per resource block | | 12 | 12 | 12 | 12 | +| Allocated slots per Frame (NOTE 7) | | 47 / 48 | 47 / 48 | 47 / 48 | 47 / 48 | +| MCS index | | 4 | 4 | 4 | 4 | +| Modulation | | QPSK | QPSK | QPSK | QPSK | +| Target Coding Rate | | 1/3 | 1/3 | 1/3 | 1/3 | +| Maximum number of HARQ transmissions | | 1 | 1 | 1 | 1 | +| Information Bit Payload per Slot | | | | | | +| For Slots 0 and Slot i, if mod(i, 5) = {3,4} for i from {0,...,159} (NOTE 5) | Bits | N/A | N/A | N/A | N/A | +| For Slot i, if mod(i, 5) = {0,1,2} for i from {1,...,159} (NOTE 6) | Bits | 2088 | 4224 | 8456 | 16896 | +| Transport block CRC | Bits | 16 | 24 | 24 | 24 | +| LDPC base graph | | 2 | 1 | 1 | 1 | +| Number of Code Blocks per Slot | | | | | | +| For Slots 0 and Slot i, if mod(i, 5) = {3,4} for i from {0,...,159} (NOTE 5) | CBs | N/A | N/A | N/A | N/A | +| For Slot i, if mod(i, 5) = {0,1,2} for i from {1,...,159} (NOTE 6) | CBs | 1 | 1 | 2 | 3 | +| Binary Channel Bits Per Slot | | | | | | +| For Slots 0 and Slot i, if mod(i, 5) = {3,4} for i from {0,...,159} (NOTE 5) | Bits | N/A | N/A | N/A | N/A | +| For Slot i, if mod(i, 5) = {0,1,2} for i from {1,...,159} (NOTE 6) | Bits | 6912 | 14256 | 28512 | 57024 | +| Max. Throughput averaged over 1 frame (NOTE 8) | Mbps | 10.022 | 20.275 | 40.589 | 81.101 | + +NOTE 1: Additional parameters are specified in Table A.3.1-1 and Table A.3.3.1-1. +NOTE 2: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to each Code Block (otherwise L = 0 Bit). +NOTE 3: SS/PBCH block is transmitted in slot 0 with periodicity 20 ms +NOTE 4: Slot i is slot index per 2 frames +NOTE 5: When this DL RMC used together with the UL RMC for the transmitter requirements requiring at least one sub frame (1ms) for the measurement period, Slot i, if mod(i, 16) = {7,...,15} for i from {0,...,159} together with the TDD UL-DL configuration specified in A2.3. +NOTE 6: When this DL RMC used together with the UL RMC for the transmitter requirements requiring at least one sub frame (1ms) for the measurement period, Slot i, if mod(i, 16) = {0,...,6} for i from {0,...,159} together with the TDD UL-DL configuration specified in A2.3. +NOTE 7: First number corresponds to the number slots allocated in the first frame of the RMC; second number corresponds to the number slots allocated in the second frame of the RMC. +NOTE 8: Throughput is averaged over 2nd frame of RMC. + +### A.3.3.2-3 Reference measurement channels for SCS 480 kHz FR2 + +**Table A.3.3.2-3 Fixed Reference Channel for Receiver Requirements (SCS 480 kHz, TDD)** + +| Parameter | Unit | Value | | | +|-----------------------------------------------------------------------------------------|------|-----------|-----------|-----------| +| Channel bandwidth | MHz | 400 | 800 | 1600 | +| Subcarrier spacing configuration | | 5 | 5 | 5 | +| Allocated resource blocks | | 66 | 124 | 248 | +| Subcarriers per resource block | | 12 | 12 | 12 | +| Allocated slots per Frame (NOTE 7) | | 191 / 192 | 191 / 192 | 191 / 192 | +| MCS index | | 4 | 4 | 4 | +| Modulation | | QPSK | QPSK | QPSK | +| Target Coding Rate | | 1/3 | 1/3 | 1/3 | +| Maximum number of HARQ transmissions | | 1 | 1 | 1 | +| Information Bit Payload per Slot | | | | | +| For Slots 0 and Slot i, if $\text{mod}(i, 5) = \{3,4\}$ for i from {0,...,639} (NOTE 5) | Bits | N/A | N/A | N/A | +| For Slot i, if $\text{mod}(i, 5) = \{0,1,2\}$ for i from {1,...,639} (NOTE 6) | Bits | 4224 | 8064 | 16136 | +| Transport block CRC | Bits | 24 | 24 | 24 | +| LDPC base graph | | 1 | 1 | 1 | +| Number of Code Blocks per Slot | | | | | +| For Slots 0 and Slot i, if $\text{mod}(i, 5) = \{3,4\}$ for i from {0,...,639} (NOTE 5) | CBs | N/A | N/A | N/A | +| For Slot i, if $\text{mod}(i, 5) = \{0,1,2\}$ for i from {1,...,639} (NOTE 6) | CBs | 1 | 1 | 2 | +| Binary Channel Bits Per Slot | | | | | +| For Slots 0 and Slot i, if $\text{mod}(i, 5) = \{3,4\}$ for i from {0,...,639} (NOTE 5) | Bits | N/A | N/A | N/A | +| For Slot i, if $\text{mod}(i, 5) = \{0,1,2\}$ for i from {1,...,639} (NOTE 6) | Bits | 14256 | 26784 | 53568 | +| Max. Throughput averaged over 1 frame (NOTE 8) | Mbps | 81.101 | 154.829 | 309.811 | + +NOTE 1: Additional parameters are specified in Table A.3.1-1 and Table A.3.3.1-1. +NOTE 2: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to each Code Block (otherwise L = 0 Bit). +NOTE 3: SS/PBCH block is transmitted in slot 0 with periodicity 20 ms +NOTE 4: Slot i is slot index per 2 frames +NOTE 5: When this DL RMC used together with the UL RMC for the transmitter requirements requiring at least one sub frame (1ms) for the measurement period, Slot i, if $\text{mod}(i, 64) = \{31, \dots, 63\}$ for i from {0,...,639} together with the TDD UL-DL configuration specified in A2.3. +NOTE 6: When this DL RMC used together with the UL RMC for the transmitter requirements requiring at least one sub frame (1ms) for the measurement period, Slot i, if $\text{mod}(i, 64) = \{0, \dots, 30\}$ for i from {0,...,639} together with the TDD UL-DL configuration specified in A2.3. +NOTE 7: First number corresponds to the number slots allocated in the first frame of the RMC; second number corresponds to the number slots allocated in the second frame of the RMC. +NOTE 8: Throughput is averaged over 2nd frame of RMC. + +### A.3.3.2-4 Reference measurement channels for SCS 960 kHz FR2 + +**Table A.3.3.2-4 Fixed Reference Channel for Receiver Requirements (SCS 960 kHz, TDD)** + +| Parameter | Unit | Value | | | | +|-------------------------------------------------------------------------------|------|--------------|--------------|--------------|--------------| +| Channel bandwidth | MHz | 400 | 800 | 1600 | 2000 | +| Subcarrier spacing configuration | | 6 | 6 | 6 | 6 | +| Allocated resource blocks | | 33 | 62 | 124 | 148 | +| Subcarriers per resource block | | 12 | 12 | 12 | 12 | +| Allocated slots per Frame (NOTE 7) | | 383 /
384 | 383 /
384 | 383 /
384 | 383 /
384 | +| MCS index | | 4 | 4 | 4 | 4 | +| Modulation | | QPSK | QPSK | QPSK | QPSK | +| Target Coding Rate | | 1/3 | 1/3 | 1/3 | 1/3 | +| Maximum number of HARQ transmissions | | 1 | 1 | 1 | 1 | +| Information Bit Payload per Slot | | | | | | +| For Slots 0 and Slot i, if mod(i, 5) = {3,4} for i from {0,...,1279} (NOTE 5) | Bits | N/A | N/A | N/A | N/A | +| For Slot i, if mod(i, 5) = {0,1,2} for i from {1,...,1279} (NOTE 6) | Bits | 2152 | 4032 | 8064 | 9480 | +| Transport block CRC | Bits | 16 | 24 | 24 | 24 | +| LDPC base graph | | 2 | 1 | 1 | 1 | +| Number of Code Blocks per Slot | | | | | | +| For Slots 0 and Slot i, if mod(i, 5) = {3,4} for i from {0,...,1279} (NOTE 5) | CBs | N/A | N/A | N/A | N/A | +| For Slot i, if mod(i, 5) = {0,1,2} for i from {1,...,1279} (NOTE 6) | CBs | 1 | 1 | 1 | 2 | +| Binary Channel Bits Per Slot | | | | | | +| For Slots 0 and Slot i, if mod(i, 5) = {3,4} for i from {0,...,1279} (NOTE 5) | Bits | N/A | N/A | N/A | N/A | +| For Slot i, if mod(i, 5) = {0,1,2} for i from {1,...,1279} (NOTE 6) | Bits | 7128 | 13392 | 26784 | 31968 | +| Max. Throughput averaged over 1 frame (NOTE 8) | Mbps | 82.637 | 154.829 | 309.658 | 364.032 | + +NOTE 1: Additional parameters are specified in Table A.3.1-1 and Table A.3.3.1-1. +NOTE 2: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to each Code Block (otherwise L = 0 Bit). +NOTE 3: SS/PBCH block is transmitted in slot 0 with periodicity 20 ms +NOTE 4: Slot i is slot index per 2 frames +NOTE 5: When this DL RMC used together with the UL RMC for the transmitter requirements requiring at least one sub frame (1ms) for the measurement period, Slot i, if mod(i, 128) = {63,...,127} for i from {0,...,1279} together with the TDD UL-DL configuration specified in A2.3. +NOTE 6: When this DL RMC used together with the UL RMC for the transmitter requirements requiring at least one sub frame (1ms) for the measurement period, Slot i, if mod(i, 128) = {0,...,62} for i from {0,...,1279} together with the TDD UL-DL configuration specified in A2.3. +NOTE 7: First number corresponds to the number slots allocated in the first frame of the RMC; second number corresponds to the number slots allocated in the second frame of the RMC. +NOTE 8: Throughput is averaged over 2nd frame of RMC. + +### A.3.3.2-5 Reference measurement channels for SCS 60 kHz FR2 + +**Table A.3.2.2-5: Fixed Reference Channel for Receiver Requirements (SCS 60 kHz, TDD)** + +| Parameter | Unit | Value | | | +|----------------------------------------------------------------------------------------|------|--------|--------|--------| +| Channel bandwidth | MHz | 50 | 100 | 200 | +| Subcarrier spacing configuration | | 2 | 2 | 2 | +| Allocated resource blocks | | 66 | 132 | 264 | +| Subcarriers per resource block | | 12 | 12 | 12 | +| Allocated slots per Frame | | 23 | 23 | 23 | +| MCS index | | 4 | 4 | 4 | +| Modulation | | QPSK | QPSK | QPSK | +| Target Coding Rate | | 1/3 | 1/3 | 1/3 | +| Maximum number of HARQ transmissions | | 1 | 1 | 1 | +| Information Bit Payload per Slot | | | | | +| For Slots 0 and Slot i, if $\text{mod}(i, 5) = \{3,4\}$ for i from {0,...,79} (NOTE 5) | Bits | N/A | N/A | N/A | +| For Slot i, if $\text{mod}(i, 5) = \{0,1,2\}$ for i from {1,...,79} (NOTE 6) | Bits | 8456 | 16896 | 33816 | +| Transport block CRC | Bits | 24 | 24 | 24 | +| LDPC base graph | | 1 | 1 | 1 | +| Number of Code Blocks per Slot | | | | | +| For Slots 0 and Slot i, if $\text{mod}(i, 5) = \{3,4\}$ for i from {0,...,79} (NOTE 5) | CBs | N/A | N/A | N/A | +| For Slot i, if $\text{mod}(i, 5) = \{0,1,2\}$ for i from {1,...,79} (NOTE 6) | CBs | 1 | 2 | 2 | +| Binary Channel Bits Per Slot | | | | | +| For Slots 0 and Slot i, if $\text{mod}(i, 5) = \{3,4\}$ for i from {0,...,79} (NOTE 5) | Bits | N/A | N/A | N/A | +| For Slot i, if $\text{mod}(i, 5) = \{0,1,2\}$ for i from {1,...,79} (NOTE 6) | Bits | 28512 | 57024 | 114048 | +| Max. Throughput averaged over 1 frame | Mbps | 19.449 | 38.861 | 77.777 | + +NOTE 1: Additional parameters are specified in Table A.3.1-1 and Table A.3.3.1-1. +NOTE 2: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to each Code Block (otherwise L = 0 Bit). +NOTE 3: SS/PBCH block is transmitted in slot 0 with periodicity 20 ms +NOTE 4: Slot i is slot index per 2 frames +NOTE 5: When this DL RMC used together with the UL RMC for the transmitter requirements requiring at least one sub frame (1ms) for the measurement period, Slot i, if $\text{mod}(i, 8) = \{3,4,5,6,7\}$ for i from {0,...,79} together with the TDD UL-DL configuration specified in A2.3. +NOTE 6: When this DL RMC used together with the UL RMC for the transmitter requirements requiring at least one sub frame (1ms) for the measurement period, Slot i, if $\text{mod}(i, 8) = \{0,1,2\}$ for i from {0,...,79} together with the TDD UL-DL configuration specified in A2.3. + +### A.3.3.2-6 Reference measurement channels for SCS 120 kHz FR2 + +**Table A.3.2.2-6: Fixed Reference Channel for Receiver Requirements (SCS 120 kHz, TDD)** + +| Parameter | Unit | Value | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|--------|--------|--------|---------| +| Channel bandwidth | MHz | 50 | 100 | 200 | 400 | +| Subcarrier spacing configuration | | 3 | 3 | 3 | 3 | +| Allocated resource blocks | | 32 | 66 | 132 | 264 | +| Subcarriers per resource block | | 12 | 12 | 12 | 12 | +| Allocated slots per Frame | | 47 | 47 | 47 | 47 | +| MCS index | | 4 | 4 | 4 | 4 | +| Modulation | | QPSK | QPSK | QPSK | QPSK | +| Target Coding Rate | | 1/3 | 1/3 | 1/3 | 1/3 | +| Maximum number of HARQ transmissions | | 1 | 1 | 1 | 1 | +| Information Bit Payload per Slot | | | | | | +| For Slots 0 and Slot i, if mod(i, 5) = {3,4} for i from {0,...,159} (NOTE 5) | Bits | N/A | N/A | N/A | N/A | +| For Slot i, if mod(i, 5) = {0,1,2} for i from {1,...,159} (NOTE 6) | Bits | 4096 | 8456 | 16896 | 33816 | +| Transport block CRC | Bits | 16 | 24 | 24 | 24 | +| LDPC base graph | | 2 | 1 | 1 | 1 | +| Number of Code Blocks per Slot | | | | | | +| For Slots 0 and Slot i, if mod(i, 5) = {3,4} for i from {0,...,159} (NOTE 5) | CBs | N/A | N/A | N/A | N/A | +| For Slot i, if mod(i, 5) = {0,1,2} for i from {1,...,159} (NOTE 6) | CBs | 1 | 1 | 2 | 2 | +| Binary Channel Bits Per Slot | | | | | | +| For Slots 0 and Slot i, if mod(i, 5) = {3,4} for i from {0,...,159} (NOTE 5) | Bits | N/A | N/A | N/A | N/A | +| For Slot i, if mod(i, 5) = {0,1,2} for i from {1,...,159} (NOTE 6) | Bits | 13824 | 28512 | 57024 | 114048 | +| Max. Throughput averaged over 1 frame | Mbps | 19.660 | 40.589 | 81.101 | 162.317 | +| NOTE 1: Additional parameters are specified in Table A.3.1-1 and Table A.3.3.1-1. | | | | | | +| NOTE 2: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to each Code Block (otherwise L = 0 Bit). | | | | | | +| NOTE 3: SS/PBCH block is transmitted in slot 0 with periodicity 20 ms | | | | | | +| NOTE 4: Slot i is slot index per 2 frames | | | | | | +| NOTE 5: When this DL RMC used together with the UL RMC for the transmitter requirements requiring at least one sub frame (1ms) for the measurement period, Slot i, if mod(i, 16) = {7,...,15} for i from {0,...,159} together with the TDD UL-DL configuration specified in A2.3. | | | | | | +| NOTE 6: When this DL RMC used together with the UL RMC for the transmitter requirements requiring at least one sub frame (1ms) for the measurement period, Slot i, if mod(i, 16) = {0,...,6} for i from {0,...,159} together with the TDD UL-DL configuration specified in A2.3. | | | | | | + +### A.3.3.3 FRC for receiver requirements for 16QAM + +### A.3.3.4 FRC for receiver requirements for 64QAM + +**Table A.3.3.4-1 Fixed Reference Channel for Receiver Requirements (SCS 60 kHz, TDD)** + +| Parameter | Unit | Value | | | +|-------------------------------------------------------------------------------|------|---------|---------|---------| +| Channel bandwidth | MHz | 50 | 100 | 200 | +| Subcarrier spacing configuration | | 2 | 2 | 2 | +| Allocated resource blocks | | 66 | 132 | 264 | +| Subcarriers per resource block | | 12 | 12 | 12 | +| Allocated slots per Frame (NOTE 6) | | 23 / 24 | 23 / 24 | 23 / 24 | +| MCS index | | 19 | 19 | 19 | +| Modulation | | 64QAM | 64QAM | 64QAM | +| Target Coding Rate | | 1/2 | 1/2 | 1/2 | +| Maximum number of HARQ transmissions | | 1 | 1 | 1 | +| Information Bit Payload per Slot | | | | | +| For Slots 0 and Slot i, if $\text{mod}(i, 5) = \{3,4\}$ for i from {0,...,79} | Bits | N/A | N/A | N/A | +| For Slot i, if $\text{mod}(i, 5) = \{0,1,2\}$ for i from {1,...,79} | Bits | 20496 | 40976 | 81976 | +| Transport block CRC | Bits | 24 | 24 | 24 | +| LDPC base graph | | 1 | 1 | 1 | +| Number of Code Blocks per Slot | | | | | +| For Slot i, if $\text{mod}(i, 10) = \{0,1,2\}$ for i from {1,...,79} | CBs | N/A | N/A | N/A | +| For Slot i, if $\text{mod}(i, 5) = \{0,1,2\}$ for i from {1,...,79} | CBs | 3 | 5 | 10 | +| Binary Channel Bits Per Slot | | | | | +| For Slots 0 and Slot i, if $\text{mod}(i, 5) = \{3,4\}$ for i from {0,...,79} | Bits | N/A | N/A | N/A | +| For Slot i, if $\text{mod}(i, 5) = \{0,1,2\}$ for i from {1,...,79} | Bits | 40986 | 81972 | 163944 | +| Max. Throughput averaged over 1 frame (NOTE 7) | Mbps | 49.190 | 98.343 | 196.742 | + +NOTE 1: Additional parameters are specified in Table A.3.1-1 and Table A.3.3.1-1. +NOTE 2: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to each Code Block (otherwise L = 0 Bit). +NOTE 3: SS/PBCH block is transmitted in slot 0 with periodicity 20 ms +NOTE 4: Slot i is slot index per 2 frames +NOTE 5: PTRS is configured on symbols containing PDSCH with 1 port, per 2PRB in frequency domain, per symbol in time domain. Overhead for TBS calculation is assumed to be 6. +NOTE 6: First number corresponds to the number slots allocated in the first frame of the RMC; second number corresponds to the number slots allocated in the second frame of the RMC. +NOTE 7: Throughput is averaged over 2nd frame of RMC. + +**Table A.3.3.4-2 Fixed Reference Channel for Receiver Requirements (SCS 120 kHz, TDD)** + +| Parameter | Unit | Value | | | | +|--------------------------------------------------------------------------------|------|---------|---------|---------|---------| +| Channel bandwidth | MHz | 50 | 100 | 200 | 400 | +| Subcarrier spacing configuration | | 3 | 3 | 3 | 3 | +| Allocated resource blocks | | 32 | 66 | 132 | 264 | +| Subcarriers per resource block | | 12 | 12 | 12 | 12 | +| Allocated slots per Frame (NOTE 6) | | 47 / 48 | 47 / 48 | 47 / 48 | 47 / 48 | +| MCS index | | 19 | 19 | 19 | 19 | +| Modulation | | 64QAM | 64QAM | 64QAM | 64QAM | +| Target Coding Rate | | 1/2 | 1/2 | 1/2 | 1/2 | +| Maximum number of HARQ transmissions | | 1 | 1 | 1 | 1 | +| Information Bit Payload per Slot | | | | | | +| For Slots 0 and Slot i, if $\text{mod}(i, 5) = \{3,4\}$ for i from {0,...,159} | Bits | N/A | N/A | N/A | N/A | +| For Slot i, if $\text{mod}(i, 5) = \{0,1,2\}$ for i from {1,...,159} | Bits | 9992 | 20496 | 40976 | 81976 | +| Transport block CRC | Bits | 24 | 24 | 24 | 24 | +| LDPC base graph | | 1 | 1 | 1 | 1 | +| Number of Code Blocks per Slot | | | | | | +| For Slots 0 and Slot i, if $\text{mod}(i, 5) = \{3,4\}$ for i from {0,...,159} | CBs | N/A | N/A | N/A | N/A | +| For Slot i, if $\text{mod}(i, 5) = \{0,1,2\}$ for i from {1,...,159} | CBs | 2 | 3 | 5 | 10 | +| Binary Channel Bits Per Slot | | | | | | +| For Slots 0 and Slot i, if $\text{mod}(i, 5) = \{3,4\}$ for i from {0,...,159} | Bits | N/A | N/A | N/A | N/A | +| For Slot i, if $\text{mod}(i, 5) = \{0,1,2\}$ for i from {1,...,159} | Bits | 19872 | 40986 | 81972 | 163944 | +| Max. Throughput averaged over 1 frame (NOTE 7) | Mbps | 47.962 | 98.381 | 196.685 | 393.485 | + +NOTE 1: Additional parameters are specified in Table A.3.1-1 and Table A.3.3.1-1. + +NOTE 2: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to each Code Block (otherwise L = 0 Bit). + +NOTE 3: SS/PBCH block is transmitted in slot 0 of each frame + +NOTE 4: Slot i is slot index per frame + +NOTE 5: PTRS is configured on symbols containing PDSCH with 1 port, per 2PRB in frequency domain, per symbol in time domain. Overhead for TBS calculation is assumed to be 6. + +NOTE 6: First number corresponds to the number slots allocated in the first frame of the RMC; second number corresponds to the number slots allocated in the second frame of the RMC. + +NOTE 7: Throughput is averaged over 2nd frame of RMC. + +**Table A.3.3.4-3 Fixed Reference Channel for Receiver Requirements (SCS 480 kHz, TDD)** + +| Parameter | Unit | Value | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----------|-----------|-----------| +| Channel bandwidth | MHz | 400 | 800 | 1600 | +| Subcarrier spacing configuration | | 5 | 5 | 5 | +| Allocated resource blocks | | 66 | 124 | 248 | +| Subcarriers per resource block | | 12 | 12 | 12 | +| Allocated slots per Frame (NOTE 6) | | 191 / 192 | 191 / 192 | 191 / 192 | +| MCS index | | 19 | 19 | 19 | +| Modulation | | 64QAM | 64QAM | 64QAM | +| Target Coding Rate | | 1/2 | 1/2 | 1/2 | +| Maximum number of HARQ transmissions | | 1 | 1 | 1 | +| Information Bit Payload per Slot | | | | | +| For Slots 0 and Slot i, if mod(i, 5) = {3,4} for i from {0,...,639} | Bits | N/A | N/A | N/A | +| For Slot i, if mod(i, 5) = {0,1,2} for i from {1,...,639} | Bits | 20496 | 37896 | 75792 | +| Transport block CRC | Bits | 24 | 24 | 24 | +| LDPC base graph | | 1 | 1 | 1 | +| Number of Code Blocks per Slot | | | | | +| For Slots 0 and Slot i, if mod(i, 5) = {3,4} for i from {0,...,639} | CBs | N/A | N/A | N/A | +| For Slot i, if mod(i, 5) = {0,1,2} for i from {1,...,639} | CBs | 3 | 5 | 9 | +| Binary Channel Bits Per Slot | | | | | +| For Slots 0 and Slot i, if mod(i, 5) = {3,4} for i from {0,...,639} | Bits | N/A | N/A | N/A | +| For Slot i, if mod(i, 5) = {0,1,2} for i from {1,...,639} | Bits | 40986 | 77004 | 154008 | +| Max. Throughput averaged over 1 frame (NOTE 7) | Mbps | 393.523 | 727.603 | 1455.206 | +| NOTE 1: Additional parameters are specified in Table A.3.1-1 and Table A.3.3.1-1. | | | | | +| NOTE 2: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to each Code Block (otherwise L = 0 Bit). | | | | | +| NOTE 3: SS/PBCH block is transmitted in slot 0 with periodicity 20 ms | | | | | +| NOTE 4: Slot i is slot index per 2 frames | | | | | +| NOTE 5: PTRS is configured on symbols containing PDSCH with 1 port, per 2PRB in frequency domain, per symbol in time domain. Overhead for TBS calculation is assumed to be 6. | | | | | +| NOTE 6: First number corresponds to the number slots allocated in the first frame of the RMC; second number corresponds to the number slots allocated in the second frame of the RMC. | | | | | +| NOTE 7: Throughput is averaged over 2nd frame of RMC. | | | | | + +**Table A.3.3.4-4 Fixed Reference Channel for Receiver Requirements (SCS 960 kHz, TDD)** + +| Parameter | Unit | Value | | | | +|----------------------------------------------------------------------|------|-----------|-----------|-----------|-----------| +| Channel bandwidth | MHz | 400 | 800 | 1600 | 2000 | +| Subcarrier spacing configuration | | 6 | 6 | 6 | 6 | +| Allocated resource blocks | | 33 | 62 | 124 | 148 | +| Subcarriers per resource block | | 12 | 12 | 12 | 12 | +| Allocated slots per Frame (NOTE 6) | | 383 / 384 | 383 / 384 | 383 / 384 | 383 / 384 | +| MCS index | | 19 | 19 | 19 | 19 | +| Modulation | | 64QAM | 64QAM | 64QAM | 64QAM | +| Target Coding Rate | | 1/2 | 1/2 | 1/2 | 1/2 | +| Maximum number of HARQ transmissions | | 1 | 1 | 1 | 1 | +| Information Bit Payload per Slot | | | | | | +| For Slots 0 and Slot i, if mod(i, 5) = {3,4} for i from {0,...,1279} | Bits | N/A | N/A | N/A | N/A | +| For Slot i, if mod(i, 5) = {0,1,2} for i from {1,...,1279} | Bits | 10248 | 18960 | 37896 | 46104 | +| Transport block CRC | Bits | 24 | 24 | 24 | 24 | +| LDPC base graph | | 1 | 1 | 1 | 1 | +| Number of Code Blocks per Slot | | | | | | +| For Slots 0 and Slot i, if mod(i, 5) = {3,4} for i from {0,...,1279} | CBs | N/A | N/A | N/A | N/A | +| For Slot i, if mod(i, 5) = {0,1,2} for i from {1,...,1279} | CBs | 2 | 3 | 5 | 6 | +| Binary Channel Bits Per Slot | | | | | | +| For Slots 0 and Slot i, if mod(i, 5) = {3,4} for i from {0,...,1279} | Bits | N/A | N/A | N/A | N/A | +| For Slot i, if mod(i, 5) = {0,1,2} for i from {1,...,1279} | Bits | 20466 | 38502 | 77004 | 91908 | +| Max. Throughput averaged over 1 frame (NOTE 7) | Mbps | 393.523 | 728.064 | 1455.206 | 1770.394 | + +NOTE 1: Additional parameters are specified in Table A.3.1-1 and Table A.3.3.1-1. +NOTE 2: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to each Code Block (otherwise L = 0 Bit). +NOTE 3: SS/PBCH block is transmitted in slot 0 with periodicity 20 ms +NOTE 4: Slot i is slot index per 2 frames +NOTE 5: PTRS is configured on symbols containing PDSCH with 1 port, per 2PRB in frequency domain, per symbol in time domain. Overhead for TBS calculation is assumed to be 6. +NOTE 6: First number corresponds to the number slots allocated in the first frame of the RMC; second number corresponds to the number slots allocated in the second frame of the RMC. +NOTE 7: Throughput is averaged over 2nd frame of RMC. + +### A.3.3.5 FRC for receiver requirements for 256QAM + +**Table A.3.3.5-1 Fixed Reference Channel for Receiver Requirements (SCS 60 kHz, TDD)** + +| Parameter | Unit | Value | | | +|--------------------------------------------------------------------|------|---------|---------|---------| +| Channel bandwidth | MHz | 50 | 100 | | +| Subcarrier spacing configuration | | 2 | 2 | | +| Allocated resource blocks | | 66 | 132 | | +| Subcarriers per resource block | | 12 | 12 | | +| Allocated slots per Frame (NOTE 6) | | 23 / 24 | 23 / 24 | 23 / 24 | +| MCS index | | 24 | 24 | | +| Modulation | | 256QAM | 256QAM | | +| Target Coding Rate | | 4/5 | 4/5 | | +| Maximum number of HARQ transmissions | | 1 | 1 | | +| Information Bit Payload per Slot | | | | | +| For Slots 0 and Slot i, if mod(i, 5) = {3,4} for i from {0,...,79} | Bits | N/A | N/A | N/A | +| For Slot i, if mod(i, 5) = {0,1,2} for i from {1,...,79} | Bits | 44040 | 88064 | 176208 | +| Transport block CRC | Bits | 24 | 24 | | +| LDPC base graph | | 1 | 1 | | +| Number of Code Blocks per Slot | | | | | +| For Slots 0 and Slot i, if mod(i, 5) = {3,4} for i from {0,...,79} | CBs | N/A | N/A | N/A | +| For Slot i, if mod(i, 5) = {0,1,2} for i from {1,...,79} | CBs | 6 | 11 | 21 | +| Binary Channel Bits Per Slot | | | | | +| For Slots 0 and Slot i, if mod(i, 5) = {3,4} for i from {0,...,79} | Bits | N/A | N/A | N/A | +| For Slot i, if mod(i, 5) = {0,1,2} for i from {1,...,79} | Bits | 54648 | 109296 | 218592 | +| Max. Throughput averaged over 1 frame (NOTE 7) | Mbps | 105.696 | 211.354 | 422.899 | + +NOTE 1: Additional parameters are specified in Table A.3.1-1 and Table A.3.3.1-1. +NOTE 2: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to each Code Block (otherwise L = 0 Bit). +NOTE 3: SS/PBCH block is transmitted in slot 0 of each frame +NOTE 4: Slot i is slot index per 2 frames +NOTE 5: PTRS is configured on symbols containing PDSCH with 1 port, per 2PRB in frequency domain, per symbol in time domain. Overhead for TBS calculation is assumed to be 6. +NOTE 6: First number corresponds to the number slots allocated in the first frame of the RMC; second number corresponds to the number slots allocated in the second frame of the RMC. +NOTE 7: Throughput is averaged over 2nd frame of RMC. + +**Table A.3.3.5-2 Fixed Reference Channel for Receiver Requirements (SCS 120 kHz, TDD)** + +| Parameter | Unit | Value | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|---------|---------|---------|---------| +| Channel bandwidth | MHz | 50 | 100 | 200 | 400 | +| Subcarrier spacing configuration | | 3 | 3 | 3 | 3 | +| Allocated resource blocks | | 32 | 66 | 132 | 264 | +| Subcarriers per resource block | | 12 | 12 | 12 | 12 | +| Allocated slots per Frame (NOTE 6) | | 47 / 48 | 47 / 48 | 47 / 48 | 47 / 48 | +| MCS index | | 24 | 24 | 24 | 24 | +| Modulation | | 256QAM | 256QAM | 256QAM | 256QAM | +| Target Coding Rate | | 4/5 | 4/5 | 4/5 | 4/5 | +| Maximum number of HARQ transmissions | | 1 | 1 | 1 | 1 | +| Information Bit Payload per Slot | | | | | | +| For Slots 0 and Slot i, if mod(i, 5) = {3,4} for i from {0,...,159} | Bits | N/A | N/A | N/A | N/A | +| For Slot i, if mod(i, 5) = {0,1,2} for i from {1,...,159} | Bits | 21504 | 44040 | 88064 | 176208 | +| Transport block CRC | Bits | 24 | 24 | 24 | 24 | +| LDPC base graph | | 1 | 1 | 1 | 1 | +| Number of Code Blocks per Slot | | | | | | +| For Slots 0 and Slot i, if mod(i, 5) = {3,4} for i from {0,...,159} | CBs | N/A | N/A | N/A | N/A | +| For Slot i, if mod(i, 5) = {0,1,2} for i from {1,...,159} | CBs | 3 | 6 | 11 | 21 | +| Binary Channel Bits Per Slot | | | | | | +| For Slots 0 and Slot i, if mod(i, 5) = {3,4} for i from {0,...,159} | Bits | N/A | N/A | N/A | N/A | +| For Slot i, if mod(i, 5) = {0,1,2} for i from {1,...,159} | Bits | 26496 | 54648 | 109296 | 218592 | +| Max. Throughput averaged over 1 frame (NOTE 7) | Mbps | 103.219 | 211.392 | 422.707 | 845.798 | +| NOTE 1: Additional parameters are specified in Table A.3.1-1 and Table A.3.3.1-1. | | | | | | +| NOTE 2: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to each Code Block (otherwise L = 0 Bit). | | | | | | +| NOTE 3: SS/PBCH block is transmitted in slot 0 of each frame | | | | | | +| NOTE 4: Slot i is slot index per 2 frames | | | | | | +| NOTE 5: PTRS is configured on symbols containing PDSCH with 1 port, per 2PRB in frequency domain, per symbol in time domain. Overhead for TBS calculation is assumed to be 6. | | | | | | +| NOTE 6: First number corresponds to the number slots allocated in the first frame of the RMC; second number corresponds to the number slots allocated in the second frame of the RMC. | | | | | | +| NOTE 7: Throughput is averaged over 2nd frame of RMC. | | | | | | + +**Table A.3.3.5-3 Fixed Reference Channel for Receiver Requirements (SCS 480 kHz, TDD)** + +| Parameter | Unit | Value | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----------|-----------|-----------| +| Channel bandwidth | MHz | 400 | 800 | 1600 | +| Subcarrier spacing configuration | | 5 | 5 | 5 | +| Allocated resource blocks | | 66 | 124 | 248 | +| Subcarriers per resource block | | 12 | 12 | 12 | +| Allocated slots per Frame (NOTE 6) | | 191 / 192 | 191 / 192 | 191 / 192 | +| MCS index | | 24 | 24 | 24 | +| Modulation | | 256QAM | 256QAM | 256QAM | +| Target Coding Rate | | 4/5 | 4/5 | 4/5 | +| Maximum number of HARQ transmissions | | 1 | 1 | 1 | +| Information Bit Payload per Slot | | | | | +| For Slots 0 and Slot i, if mod(i, 5) = {3,4} for i from {0,...,639} | Bits | N/A | N/A | N/A | +| For Slot i, if mod(i, 5) = {0,1,2} for i from {1,...,639} | Bits | 44040 | 83976 | 167976 | +| Transport block CRC | Bits | 24 | 24 | 24 | +| LDPC base graph | | 1 | 1 | 1 | +| Number of Code Blocks per Slot | | | | | +| For Slots 0 and Slot i, if mod(i, 5) = {3,4} for i from {0,...,639} | CBs | N/A | N/A | N/A | +| For Slot i, if mod(i, 5) = {0,1,2} for i from {1,...,639} | CBs | 6 | 10 | 20 | +| Binary Channel Bits Per Slot | | | | | +| For Slots 0 and Slot i, if mod(i, 5) = {3,4} for i from {0,...,639} | Bits | N/A | N/A | N/A | +| For Slot i, if mod(i, 5) = {0,1,2} for i from {1,...,639} | Bits | 54648 | 102672 | 205344 | +| Max. Throughput averaged over 1 frame (NOTE 7) | Mbps | 845.568 | 1612.339 | 3225.139 | +| NOTE 1: Additional parameters are specified in Table A.3.1-1 and Table A.3.3.1-1. | | | | | +| NOTE 2: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to each Code Block (otherwise L = 0 Bit). | | | | | +| NOTE 3: SS/PBCH block is transmitted in slot 0 with periodicity 20 ms | | | | | +| NOTE 4: Slot i is slot index per 2 frames | | | | | +| NOTE 5: PTRS is configured on symbols containing PDSCH with 1 port, per 2PRB in frequency domain, per symbol in time domain. Overhead for TBS calculation is assumed to be 6. | | | | | +| NOTE 6: First number corresponds to the number slots allocated in the first frame of the RMC; second number corresponds to the number slots allocated in the second frame of the RMC. | | | | | +| NOTE 7: Throughput is averaged over 2nd frame of RMC. | | | | | + +**Table A.3.3.5-4 Fixed Reference Channel for Receiver Requirements (SCS 960 kHz, TDD)** + +| Parameter | Unit | Value | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----------|-----------|-----------|-----------| +| Channel bandwidth | MHz | 400 | 800 | 1600 | 2000 | +| Subcarrier spacing configuration | | 6 | 6 | 6 | 6 | +| Allocated resource blocks | | 33 | 62 | 124 | 148 | +| Subcarriers per resource block | | 12 | 12 | 12 | 12 | +| Allocated slots per Frame (NOTE 6) | | 383 / 384 | 383 / 384 | 383 / 384 | 383 / 384 | +| MCS index | | 24 | 24 | 24 | 24 | +| Modulation | | 256QAM | 256QAM | 256QAM | 256QAM | +| Target Coding Rate | | 4/5 | 4/5 | 4/5 | 4/5 | +| Maximum number of HARQ transmissions | | 1 | 1 | 1 | 1 | +| Information Bit Payload per Slot | | | | | | +| For Slots 0 and Slot i, if mod(i, 5) = {3,4} for i from {0,...,1279} | Bits | N/A | N/A | N/A | N/A | +| For Slot i, if mod(i, 5) = {0,1,2} for i from {1,...,1279} | Bits | 22032 | 42016 | 83976 | 98376 | +| Transport block CRC | Bits | 24 | 24 | 24 | 24 | +| LDPC base graph | | 1 | 1 | 1 | 1 | +| Number of Code Blocks per Slot | | | | | | +| For Slots 0 and Slot i, if mod(i, 5) = {3,4} for i from {0,...,1279} | CBs | N/A | N/A | N/A | N/A | +| For Slot i, if mod(i, 5) = {0,1,2} for i from {1,...,1279} | CBs | 3 | 5 | 10 | 12 | +| Binary Channel Bits Per Slot | | | | | | +| For Slots 0 and Slot i, if mod(i, 5) = {3,4} for i from {0,...,1279} | Bits | N/A | N/A | N/A | N/A | +| For Slot i, if mod(i, 5) = {0,1,2} for i from {1,...,1279} | Bits | 27288 | 51336 | 102672 | 122544 | +| Max. Throughput averaged over 1 frame (NOTE 7) | Mbps | 846.029 | 1613.414 | 3224.678 | 3777.638 | +| NOTE 1: Additional parameters are specified in Table A.3.1-1 and Table A.3.3.1-1. | | | | | | +| NOTE 2: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to each Code Block (otherwise L = 0 Bit). | | | | | | +| NOTE 3: SS/PBCH block is transmitted in slot 0 with periodicity 20 ms | | | | | | +| NOTE 4: Slot i is slot index per 2 frames | | | | | | +| NOTE 5: PTRS is configured on symbols containing PDSCH with 1 port, per 2PRB in frequency domain, per symbol in time domain. Overhead for TBS calculation is assumed to be 6. | | | | | | +| NOTE 6: First number corresponds to the number slots allocated in the first frame of the RMC; second number corresponds to the number slots allocated in the second frame of the RMC. | | | | | | +| NOTE 7: Throughput is averaged over 2nd frame of RMC. | | | | | | + +## A.4 Void + +## A.5 OFDMA Channel Noise Generator (OCNG) + +### A.5.1 OCNG Patterns for FDD + +### A.5.2 OCNG Patterns for TDD + +#### A.5.2.1 OCNG TDD pattern 1: Generic OCNG TDD Pattern for all unused REs + +**Table A.5.2.1-1: OP.1 TDD: Generic OCNG TDD Pattern for all unused REs** + +| OCNG Appliance
OCNG Parameters | Control Region
(Core Set) | Data Region | +|--------------------------------------------------------------|------------------------------------------------|--------------------------------------------------------------------------------------------------------| +| Resources allocated | All unused REs (Note 1) | All unused REs (Note 2) | +| Structure | PDCCH | PDSCH | +| Content | Uncorrelated pseudo random QPSK modulated data | Uncorrelated pseudo random QPSK modulated data | +| Transmission scheme for multiple antennas ports transmission | Single Tx port transmission | Spatial multiplexing using any precoding matrix with dimensions same as the precoding matrix for PDSCH | +| Subcarrier Spacing | Same as for RMC PDCCH in the active BWP | Same as for RMC PDSCH in the active BWP | +| Power Level | Same as for RMC PDCCH | Same as for RMC PDSCH | + +Note 1: All unused REs in the active CORESETS appointed by the search spaces in use. +Note 2: Unused available REs refer to REs in PRBs not allocated for any physical channels, CORESETs, synchronization signals or reference signals in channel bandwidth. + +--- + +## Annex B (informative): Void + +## Annex C (normative): Downlink physical channels + +### C.1 General + +### C.2 Setup + +Table C.2-1 describes the downlink Physical Channels that are required for connection set up. + +**Table C.2-1: Downlink Physical Channels required for connection set-up** + +| Physical Channel | +|------------------| +| PBCH | +| SSS | +| PSS | +| PDCCH | +| PDSCH | +| PBCH DMRS | +| PDCCH DMRS | +| PDSCH DMRS | +| CSI-RS | +| PTRS | + +### C.3 Connection + +#### C.3.1 Measurement of Receiver Characteristics + +Unless otherwise stated, Table C.3.1-1 is applicable for measurements on the Receiver Characteristics (clause 7). + +**Table C.3.1-1: Downlink Physical Channels transmitted during a connection (TDD)** + +| Parameter | Unit | Value | +|--------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| SSS transmit power | W | Test specific | +| EPRE ratio of PSS to SSS | dB | 0 | +| EPRE ratio of PBCH to SSS | dB | 0 | +| EPRE ratio of PBCH to PBCH DMRS | dB | 0 | +| EPRE ratio of PDCCH to SSS | dB | 0 | +| EPRE ratio of PDCCH to PDCCH DMRS | dB | 0 | +| EPRE ratio of PDSCH to SSS | dB | 0 | +| EPRE ratio of PDSCH to PDSCH DMRS (Note 1) | dB | -3 | +| EPRE ratio of CSI-RS to SSS | dB | 0 | +| EPRE ratio of PTRS to PDSCH | dB | Test specific | +| EPRE ratio of OCN G DMRS to SSS | dB | 0 | +| EPRE ratio of OCN G to OCN G DMRS (Note 1) | dB | 0 | +| Note 1: | No boosting is applied to any of the channels except PDSCH DMRS. For PDSCH DMRS, 3 dB power boosting is applied assuming DMRS Type 1 configuration when DMRS and PDSCH are TDM'ed and only half of the DMRS REs are occupied. | | +| Note 2: | Number of DMRS CDM groups without data for PDSCH DMRS configuration for OCN G is set to 1. | | + +## Annex D (normative): Characteristics of the interfering signal + +### D.1 General + +Unless otherwise stated, a modulated full bandwidth NR downlink signal, which equals to channel bandwidth of the wanted signal for Single Carrier case is used as interfering signals when RF performance requirements for NR UE receiver are defined. For intra-band contiguous CA case, a modulated NR downlink signal which equals to the aggregated channel bandwidth of the wanted signal is used. + +### D.2 Interference signals + +Table D.2-1 describes the modulated interferer for different channel bandwidth options. + +**Table D.2-1: Description of modulated NR interferer** + +| | Channel bandwidth for Single Carrier | | | | Intra band
contiguous CA | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------|---------|---------|---------|-----------------------------| +| | 50 MHz | 100 MHz | 200 MHz | 400 MHz | | +| BW Interferer | 50 MHz | 100 MHz | 200 MHz | 400MHz | BW Channel_CA | +| RB | NOTE1 | | | | | +| NOTE 1: | The RB configured for interfering signal is the same as maximum RB number defined in Table 5.3.2-1 for each sub-carrier spacing. | | | | | + +## Annex E (normative): Environmental conditions + +### E.1 General + +This annex specifies the environmental requirements of the UE. Within these limits the requirements of the present documents shall be fulfilled. + +### E.2 Environmental + +The requirements in this clause apply to all types of UE(s). + +#### E.2.1 Temperature + +All RF requirements for UEs operating in FR2 are defined over the air and can only be tested in an OTA chamber. + +The UE shall fulfil all the requirements in the temperature range for extreme conditions, as defined in Table E.2.1-1, unless explicitly stated otherwise in any requirement. + +**Table E.2.1-1: Temperature conditions** + +| | | +|-----------------|----------------------------------------------------------------------------| +| + 25 °C ± 10 °C | For normal (room temperature) conditions with relative humidity up to 75 % | +| -10°C to +55°C | For extreme conditions | + +Outside this temperature range the UE, if powered on, shall not make ineffective use of the radio frequency spectrum. In no case shall the UE exceed the transmitted levels as defined in clause 6.2 for extreme operation. + +#### E.2.2 Voltage + +Editor's note: This requirement is incomplete. The following aspects are either missing or not yet determined: + +Methodology to control the voltage in a case which a power cable is not connected to DUT is FFS since it is not agreed whether we can connect the power cable to DUT at the OTA measurement situation yet. + +The UE shall fulfil all the requirements in the full voltage range, i.e. the voltage range between the extreme voltages. + +The manufacturer shall declare the lower and higher extreme voltages and the approximate shutdown voltage. For the equipment that can be operated from one or more of the power sources listed below, the lower extreme voltage shall not be higher, and the higher extreme voltage shall not be lower than that specified below. + +**Table E.2.2-1: Voltage conditions** + +| Power source | Lower extreme voltage | Higher extreme voltage | Normal conditions voltage | +|-----------------------------|-----------------------|------------------------|---------------------------| +| AC mains | 0,9 * nominal | 1,1 * nominal | nominal | +| Regulated lead acid battery | 0,9 * nominal | 1,3 * nominal | 1,1 * nominal | +| Nonregulated batteries: | | | | +| Leclanché | 0,85 * nominal | Nominal | Nominal | +| Lithium | 0,95 * nominal | 1,1 * Nominal | 1,1 * Nominal | +| Mercury/nickel & cadmium | 0,90 * nominal | | Nominal | + +Outside this voltage range the UE if powered on, shall not make ineffective use of the radio frequency spectrum. In no case shall the UE exceed the transmitted levels as defined in clause 6.2 for extreme operation. In particular, the UE shall inhibit all RF transmissions when the power supply voltage is below the manufacturer declared shutdown voltage. + +## E.2.3 Void + +## Annex F (normative): Transmit modulation + +### F.1 Measurement Point + +Figure F.1-1 shows the measurement point for the unwanted emission falling into non-allocated RB(s) and the EVM for the allocated RB(s). + +![Figure F.1-1: EVM measurement points. The diagram shows the signal flow from the DUT (Device Under Test) to the Test equipment. On the DUT side, two input types are shown: DFT-s-OFDM (PUSCH, PUCCH, and DFT-s-OFDM DM-RS Type 2) and CP-OFDM (PUSCH, PUCCH, and CP-OFDM DM-RS, DFT-s-OFDM DM-RS Type 1). The DFT-s-OFDM signal goes through a DFT block, then a Tone map block. The CP-OFDM signal goes through an IFFT block. Both signals are then processed by a TX Front-end block. The signal then passes through a Channel block. On the Test equipment side, the signal goes through an RF correction block, then an FFT block. The FFT output is split into two measurement paths: one for EVM measurement (Tx-Rx chain equalizer) and one for in-band emissions measurement. The EVM measurement path includes an IDFT block and results in EVM measurements for both DFT-s-OFDM and CP-OFDM signals. The in-band emissions measurement path results in in-band emissions measurements for both DFT-s-OFDM and CP-OFDM signals.](931c81c99d2b5ece0876279fc1f38e42_img.jpg) + +Figure F.1-1: EVM measurement points. The diagram shows the signal flow from the DUT (Device Under Test) to the Test equipment. On the DUT side, two input types are shown: DFT-s-OFDM (PUSCH, PUCCH, and DFT-s-OFDM DM-RS Type 2) and CP-OFDM (PUSCH, PUCCH, and CP-OFDM DM-RS, DFT-s-OFDM DM-RS Type 1). The DFT-s-OFDM signal goes through a DFT block, then a Tone map block. The CP-OFDM signal goes through an IFFT block. Both signals are then processed by a TX Front-end block. The signal then passes through a Channel block. On the Test equipment side, the signal goes through an RF correction block, then an FFT block. The FFT output is split into two measurement paths: one for EVM measurement (Tx-Rx chain equalizer) and one for in-band emissions measurement. The EVM measurement path includes an IDFT block and results in EVM measurements for both DFT-s-OFDM and CP-OFDM signals. The in-band emissions measurement path results in in-band emissions measurements for both DFT-s-OFDM and CP-OFDM signals. + +Figure F.1-1: EVM measurement points + +### F.2 Basic Error Vector Magnitude measurement + +The EVM is the difference between the ideal waveform and the measured waveform for the allocated RB(s) + +where + +is a set of modulation symbols with the considered modulation scheme being active within the measurement period, + +are the samples of the signal evaluated for the EVM, + +is the ideal signal reconstructed by the measurement equipment, and + +is the average power of the ideal signal. For normalized modulation symbols is equal to 1. + +The basic EVM measurement interval is defined over one slot in the time domain for PUCCH and PUSCH and over one preamble sequence for the PRACH. + +### F.3 Basic in-band emissions measurement + +The in-band emissions are a measure of the interference falling into the non-allocated resources blocks. The in-band emission requirement is evaluated for PUCCH and PUSCH transmissions. The in-band emission requirement is not evaluated for PRACH transmissions. + +The in-band emissions are measured as follows + +where + +is a set of OFDM symbols with the considered modulation scheme being active within the measurement period, + +is the starting frequency offset between the allocated RB and the measured non-allocated RB (e.g. 0 or for the first adjacent RB), + +(resp. ) is the lower (resp. upper) edge of the UL system BW, + +and are the lower and upper edge of the allocated BW, and + +is the frequency domain signal evaluated for in-band emissions as defined in the clause (ii) + +The relative in-band emissions are, given by + +where + +is the number of allocated RBs + +The basic in-band emissions measurement interval is defined over one slot in the time domain. When the PUSCH or PUCCH transmission slot is shortened due to multiplexing with SRS, the in-band emissions measurement interval is reduced by one OFDM symbol, accordingly. + +In the evaluation of in-band emissions, the timing is set according to , where sample time offsets and are defined in clause F.4. + +## F.4 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 DFT-s-OFDM modulated signals or PRACH signal under test is modified and, in the case of DFT-s-OFDM modulated signals, decoded according to: + +where + +is the time domain samples of the signal under test. + +The CP-OFDM modulated signals or PUSCH demodulation reference signal or CP-OFDM modulated signals under test is equalised and, in the case of PUCCH data signal decoded according to: + +where + +is the time domain samples of the signal under test. + +To minimize the error, the signal under test should be modified with respect to a set of parameters following the procedure explained below. + +Notation: + +is the sample timing difference between the FFT processing window in relation to nominal timing of the ideal signal. + +is the RF frequency offset. + +is the phase response of the TX chain. + +is the amplitude response of the TX chain. + +In the following represents the middle sample of the EVM window of length (defined in the next clauses) or the last sample of the first window half if is even. + +The EVM analyser shall + +- detect the start of each slot and estimate $\Delta f$ , +- determine $\Delta t$ so that the EVM window of length $\Delta t$ is centred + - on the time interval determined by the measured cyclic prefix minus $16\kappa$ samples of the considered OFDM symbol for symbol $l$ for subcarrier spacing configuration $\mu$ in a subframe, with $l = 0$ or $l = 7 \cdot 2^\mu$ for normal CP, i.e. the first $16\kappa$ samples of the CP should not be taken into account for this step. In the determination of the number of excluded samples, a sampling rate of $1/T_c$ is assumed. If a different sampling rate is used, the number of excluded samples is scaled linearly. + - on the measured cyclic prefix of the considered OFDM symbol for all other symbols for normal CP and for symbol 0 to 11 for extended CP. + - on the measured preamble cyclic prefix for the PRACH + +To determine the other parameters a sample timing offset equal to $\Delta t$ is corrected from the signal under test. The EVM analyser shall then + +- correct the RF frequency offset for each time slot, and +- apply an FFT of appropriate size. The chosen FFT size shall ensure that in the case of an ideal signal under test, there is no measured inter-subcarrier interference. + +The carrier leakage shall be removed from the evaluated signal before calculating the EVM and the in-band emissions; however, the removed relative carrier leakage power also has to satisfy the applicable requirement. + +At this stage the allocated RBs shall be separated from the non-allocated RBs. In the case of PUCCH and PUSCH EVM, the signal on the non-allocated RB(s), $s$ , is used to evaluate the in-band emissions. + +Moreover, the following procedure applies only to the signal on the allocated RB(s). + +- In the case of PUCCH and PUSCH, the UL EVM analyzer shall estimate the TX chain equalizer coefficients and used by the ZF equalizer for all subcarriers by time averaging at each signal subcarrier of the amplitude and phase of the reference and data symbols. The time-averaging length is 1 slot. This process creates an average amplitude and phase for each signal subcarrier used by the ZF equalizer. The knowledge of data modulation symbols may be required in this step because the determination of symbols by demodulation is not reliable before signal equalization. +- In the case of PRACH, the UL EVM analyzer shall estimate the TX chain coefficients and used for phase and amplitude correction and are selected so as to minimize the resulting EVM. The TX chain coefficients are not dependent on frequency, i.e. $\Delta f$ and $\Delta t$ . The TX chain coefficient are chosen independently for each preamble transmission and for each $\Delta f$ . + +At this stage estimates of $\Delta f$ , $\Delta t$ , and $\Delta t_{\text{ext}}$ are available. $\Delta t_{\text{ext}}$ is one of the extremities of the window $\Delta t$ , i.e. can be $\Delta t$ or $-\Delta t$ , where $\Delta t$ is odd and $\Delta t_{\text{ext}}$ is even. The EVM analyser shall then + +- calculate $\text{EVM}_l$ with $\Delta t$ set to $\Delta t$ , +- calculate $\text{EVM}_h$ with $\Delta t$ set to $\Delta t_{\text{ext}}$ . + +## F.5 Window length + +### F.5.1 Timing offset + +As a result of using a cyclic prefix, there is a range of $\Delta t$ , which, at least in the case of perfect Tx signal quality, would give close to minimum error vector magnitude. As a first order approximation, that range should be equal to the length of the cyclic prefix. Any time domain windowing or FIR pulse shaping applied by the transmitter reduces the range within which the error vector is close to its minimum. + +## F.5.2 Window length + +The window length $W$ affects the measured EVM and is expressed as a function of the configured cyclic prefix length. In the case where equalization is present, as with frequency domain EVM computation, the effect of FIR is reduced. This is because the equalization can correct most of the linear distortion introduced by the FIR. However, the time domain windowing effect can't be removed. + +## F.5.3 Window length for normal CP + +Table F.5.3-1 and Table F.5.3-2 below specify the EVM window length ( $W$ ) for normal CP for FR2. + +**Table F.5.3-1: EVM window length for normal CP for 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 1 (%) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|-------------------------------------|-----------------------|--------------------------------------------------| +| 50 | 1024 | 72 | 36 | 50 | +| 100 | 2048 | 144 | 72 | 50 | +| 200 | 4096 | 288 | 144 | 50 | +| Note 1: 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 F.5.3-2: EVM window length for normal CP for 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 1 (%) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|-------------------------------------|-----------------------|--------------------------------------------------| +| 50 | 512 | 36 | 18 | 50 | +| 100 | 1024 | 72 | 36 | 50 | +| 200 | 2048 | 144 | 72 | 50 | +| 400 | 4096 | 288 | 144 | 50 | +| Note 1: 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. | | | | | + +## F.5.4 Window length for Extended CP + +Table F.5.4-1 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 F.5.4-1: EVM window length for extended CP for 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 1 (%) | +|--------------------------------------------|----------|-------------------------------------|-----------------------|--------------------------------------------------| +| 50 | 1024 | 256 | 220 | 85.9 | +| 100 | 2048 | 512 | 440 | 85.9 | +| 200 | 4096 | 1024 | 880 | 85.9 | +| Note 1: These percentages are informative. | | | | | + +## F.5.5 Window length for PRACH + +The table below specifies the EVM window length for PRACH preamble formats for $L_{RA} = 139$ and where . + +**Table F.5.5-1: EVM window length for PRACH formats for $L_{RA} = 139$** + +| Preamble format | Cyclic prefix length | Nominal FFT size 1 | EVM window length $W$ in FFT samples | Ratio of $W$ to CP 2 | +|-----------------|-----------------------|-------------------------------|--------------------------------------|---------------------------------| +| A1 | $1152 \cdot 2^{-\mu}$ | $8192 \cdot 2^{-\mu}$ | $576 \cdot 2^{-\mu}$ | 50.0% | +| A2 | $2304 \cdot 2^{-\mu}$ | $8192 \cdot 2^{-\mu}$ | $1728 \cdot 2^{-\mu}$ | 75.0% | +| A3 | $3456 \cdot 2^{-\mu}$ | $8192 \cdot 2^{-\mu}$ | $2880 \cdot 2^{-\mu}$ | 83.3% | +| B1 | $864 \cdot 2^{-\mu}$ | $8192 \cdot 2^{-\mu}$ | $288 \cdot 2^{-\mu}$ | 33.3% | +| B2 | $1440 \cdot 2^{-\mu}$ | $8192 \cdot 2^{-\mu}$ | $864 \cdot 2^{-\mu}$ | 60.0% | +| B3 | $2016 \cdot 2^{-\mu}$ | $8192 \cdot 2^{-\mu}$ | $1440 \cdot 2^{-\mu}$ | 71.4% | +| B4 | $3744 \cdot 2^{-\mu}$ | $8192 \cdot 2^{-\mu}$ | $3168 \cdot 2^{-\mu}$ | 84.6% | +| C0 | $4960 \cdot 2^{-\mu}$ | $8192 \cdot 2^{-\mu}$ | $4384 \cdot 2^{-\mu}$ | 88.4% | +| C2 | $8192 \cdot 2^{-\mu}$ | $8192 \cdot 2^{-\mu}$ | $7616 \cdot 2^{-\mu}$ | 93.0% | + +Note 1: The use of other FFT sizes is possible as long as appropriate scaling of the window length is applied +Note 2: These percentages are informative + +## F.6 Averaged EVM + +The general EVM is averaged over basic EVM measurements for $n$ slots in the time domain. + +where $n$ is + +for PUCCH, PUSCH. + +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}$ is calculated using in the expressions above and is calculated using . + +Thus we get: + +The calculation of the EVM for the demodulation reference signal, , follows the same procedure as calculating the general EVM, with the exception that the modulation symbol set defined in clause F.2 is restricted to symbols containing uplink demodulation reference signals. + +The basic measurements are first averaged over $n$ slots in the time domain to obtain an intermediate average . + +In the determination of each $EVM_{DMRS,i}$ , the timing is set to if $EVM_l > EVM_h$ , and it is set to otherwise, where $EVM_l$ and $EVM_h$ are the general average EVM values calculated in the same $n$ slots over which the intermediate average $EVM_{DMRS}$ is calculated. Note that in some cases, the general average EVM may be calculated only for the purpose of timing selection for the demodulation reference signal EVM. + +Then the results are further averaged to get the EVM for the demodulation reference signal, $EVM_{DMRS}$ , + +The PRACH EVM, , is averaged over 2 preamble sequence measurements for long preamble formats as defined in table 6.3.3.1-1 in [9] and averaged over 10 preamble sequence measurements for short preamble formats as defined in table 6.3.3.1-2 in [9]. + +The EVM requirements shall be tested against the maximum of the RMS average at the window $W$ extremities of the EVM measurements: + +Thus $\overline{\text{EVM}}_{\text{PRACH,l}}$ is calculated using and $\overline{\text{EVM}}_{\text{PRACH,h}}$ is calculated using . + +Thus we get: + +## F.7 Spectrum Flatness + +The data shall be taken from FFT coded data symbols and the demodulation reference symbols of the allocated resource block. + +## F.8 Phase offset measurement for DMRS bundling + +### F.8.1 Measurement point + +The measurement point for phase offset measurement is defined in Figure F.8.1-1. + +![Figure F.8.1-1: Measurement point for phase offset for DMRS bundling. The diagram shows a transmitter (Tx) chain on the left and a receiver (Rx) chain on the right, connected by a channel. The Tx chain includes CP-OFDM inputs (DMRS, PUSCH, PUCCH) entering a DFT block, which then goes to a Tone Map block. The output of the Tone Map block enters an IFFT block. The output of the IFFT block goes to a TX Front-End block. The TX Front-End block outputs to a channel block. The channel block outputs to an RF Correction block. The RF Correction block outputs to an FFT block. The output of the FFT block goes to a Channel Estimation block. The output of the Channel Estimation block goes to an equalization block. The output of the equalization block is labeled 'Phase offset for DMRS bundling'.](790b3d1f6fbe3b4570cf1eec24db67f0_img.jpg) + +``` + +graph LR + subgraph Tx + CP[CP-OFDM DMRS PUSCH PUCCH] --> DFT[DFT] + DFT --> TM[Tone Map] + TM --> IFFT[IFFT] + IFFT --> TXFE[TX Front-End] + end + TXFE --> CH[channel] + CH --> RCF[RF Correction] + subgraph Rx + RCF --> FFT[FFT] + FFT --> CE[Channel Estimation] + CE --> EQ[equalization] + EQ --> PO[Phase offset for DMRS bundling] + end + +``` + +Figure F.8.1-1: Measurement point for phase offset for DMRS bundling. The diagram shows a transmitter (Tx) chain on the left and a receiver (Rx) chain on the right, connected by a channel. The Tx chain includes CP-OFDM inputs (DMRS, PUSCH, PUCCH) entering a DFT block, which then goes to a Tone Map block. The output of the Tone Map block enters an IFFT block. The output of the IFFT block goes to a TX Front-End block. The TX Front-End block outputs to a channel block. The channel block outputs to an RF Correction block. The RF Correction block outputs to an FFT block. The output of the FFT block goes to a Channel Estimation block. The output of the Channel Estimation block goes to an equalization block. The output of the equalization block is labeled 'Phase offset for DMRS bundling'. + +Figure F.8.1-1: Measurement point for phase offset for DMRS bundling + +### F.8.2 Symbols used + +Phase offset is determined based on DMRS REs (3 DMRS symbols per slot) with the option to use data symbols. + +### F.8.3 Modified test signal + +Same as described in Annex F.4. + +### F.8.4 Phase offset measurement + +The phase offset measurement is based on the phase response of the Tx chain as derived based on Annex F.4. + +The subcarrier at the carrier leakage frequency of the transmitted signal shall be excluded from the measured subcarriers. + +The phase difference for each measured subcarrier between a reference timeslot $t_{ref}$ and the measurement timeslot $t_m$ is then calculated as defined below: + +The phase offset between the reference and measurement timeslots are then calculated as the maximum over the results for all measured subcarriers as shown below: + +## F.9 Reserved + +## F.10 EVM for dual transmit polarizations + +### F.10.1 General + +A zero-forcing (ZF) MIMO receiver architecture is used so that transmissions by the UE, which are received by the test equipment on two polarizations, can be demodulated by the test equipment receiver. + +![EVM calculation block diagram for 2-Layer UL MIMO. The diagram shows two input paths (TE port 1 and TE port 2) entering RF correction blocks. The outputs then 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 to 'Decision + LS estimation per slot (1x1 per SC)' blocks, which then output NS(f,t) Layer 1 and NS(f,t) Layer 2. The other path from the RF correction blocks goes through FFT @ CP/2 +/- W/2 to a 'MIMO Equalization, Layer separation (matrix multiply)' block. This block outputs Layer 1 and Layer 2 to 'Layer 1 "Equalization" (vector multiply)' and 'Layer 2 "Equalization" (vector multiply)' blocks, which then output to EVM Layer 1 and EVM Layer 2. Green arrows indicate data flow from the channel estimation blocks to the equalization blocks.](9ce14e3b4651237e346d641e58e46fbc_img.jpg) + +EVM calculation block diagram for 2-Layer UL MIMO. The diagram shows two input paths (TE port 1 and TE port 2) entering RF correction blocks. The outputs then 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 to 'Decision + LS estimation per slot (1x1 per SC)' blocks, which then output NS(f,t) Layer 1 and NS(f,t) Layer 2. The other path from the RF correction blocks goes through FFT @ CP/2 +/- W/2 to a 'MIMO Equalization, Layer separation (matrix multiply)' block. This block outputs Layer 1 and Layer 2 to 'Layer 1 "Equalization" (vector multiply)' and 'Layer 2 "Equalization" (vector multiply)' blocks, which then output to EVM Layer 1 and EVM Layer 2. Green arrows indicate data flow from the channel estimation blocks to the equalization blocks. + +Figure F.10.1-1: EVM calculation block diagram for 2-Layer UL MIMO + +The TE receives signals from 2 different ports on two antenna polarizations in the test system. + +For UL MIMO measurements a MIMO equalization step as described in section F.10.2 is performed to separate the layers. + +For single layer transmissions received on two polarizations the MIMO equalization step as described in section F.10.2 is replaced by a maximum ratio combining step as described in section F.10.3. + +Each layer is then processed as described in section F.10.4 to receive the measurement results for each individual layer. + +## F.10.2 MIMO Equalization (UL MIMO transmission) + +The MIMO equalization is based only on reference signals (DMRS) without using any data symbols. For the equalization process all available DMRS symbols shall be used. + +The effective $2 \times 2$ channel matrix is estimated using reference signals of 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_j$ 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: + +## F.10.3 Maximum Ratio combining (Tx diversity transmission) + +The maximum ratio combining is based only on reference signals (DMRS) without using any data symbols. For the equalization process all available DMRS symbols shall be used. + +The effective $2 \times 1$ channel matrix is estimated using reference signals of different subcarriers. 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: + +## F.10.4 Layer processing + +After performing either the MIMO equalization or maximum ratio combining as described in section F.10.2 or F.10.3 respectively, each layer is processed using the existing procedure as defined in Annex E of TS 38.521-2 [5]. + +Since the channel estimation is calculated only on the DMRS symbols, 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 least square (LS) equalization method described for single layer in Annex E.3. of TS 38.521-2 [5]. + +$MS(f,t)$ and $NS(f,t)$ are processed with a 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: + +--- + +## Annex G (normative): Difference of relative phase and power errors + +--- + +### G.0 General + +This annex gives further information needed for understanding and implementing 6.4D.4. The following terms should be understood as follows: + +- Relative phase error: refers to the phase difference between signals at different antenna ports, which should be ideally 0. It should be understood as for a slot i.e. (slot) relative phase. It is calculated based on DMRS symbols of that slot or on SRS symbols. +- Difference of relative phase error: refers to the difference between the relative phase error determined per slot and the relative phase error determined based on the SRS transmitted. + +--- + +### G.1 Measurement Point + +Figure G.1-1 shows the measurement point for the difference of relative phase and power errors. To separate signals from the two transmitters, it is necessary for the test equipment to perform joint demodulation by inverting the 2x2 composite channel ('HGW') resulting from DUT precoding 'W' and antenna virtualization 'G' and OTA channel between DUT and test equipment 'H'. Post processing refers to the calculation of the phase/power errors, the averaging of phase and power errors per RB per slot per channel port and the calculation of difference between relative phases. + +![Figure G.1-1: Measurement point for difference of relative phase/power error for UL coherent MIMO. The diagram shows a DUT (Device Under Test) and Test Equipment connected via an OTA channel. The DUT has two TX Front Ends. The top path takes CP-OFDM signals (DRMS, PUSCH, PUCCH) through a DFT, Tone map, and IFFT. The bottom path takes PUCCH, PUSCH, DMRS, and CP-OFDM signals through a DFT, Tone map, and IFFT. Both paths output to the OTA channel. The Test Equipment receives the signals, performs RF Correction, and then FFT. The FFT outputs are processed by a DRMS based Channel estimation block. This block feeds into a MIMO Detector + Layer Separation block, which outputs Equalization Per Layer for both paths. The bottom path also feeds into a Post-processing block, which outputs the Difference of Relative Phase/Power Error.](6bd84b6e2e96b0d1193956b5a04b0e69_img.jpg) + +Figure G.1-1: Measurement point for difference of relative phase/power error for UL coherent MIMO. The diagram shows a DUT (Device Under Test) and Test Equipment connected via an OTA channel. The DUT has two TX Front Ends. The top path takes CP-OFDM signals (DRMS, PUSCH, PUCCH) through a DFT, Tone map, and IFFT. The bottom path takes PUCCH, PUSCH, DMRS, and CP-OFDM signals through a DFT, Tone map, and IFFT. Both paths output to the OTA channel. The Test Equipment receives the signals, performs RF Correction, and then FFT. The FFT outputs are processed by a DRMS based Channel estimation block. This block feeds into a MIMO Detector + Layer Separation block, which outputs Equalization Per Layer for both paths. The bottom path also feeds into a Post-processing block, which outputs the Difference of Relative Phase/Power Error. + +**Figure G.1-1 - Measurement point for difference of relative phase/power error for UL coherent MIMO** + +## G.2 Relative Phase Error Measurement + +Here are listed the different aspects that may lead to different interpretations. + +### G.2.1 Symbols and subcarriers used + +Phase error is determined based on DMRS REs (DMRS mapping type A with 3 DMRS symbols per slot, the REs corresponding to the odd subcarriers and DMRS symbols are non-allocated for data or DMRS) and SRS REs (with 4 SRS symbols in the SRS slot, same SRS resource mapping is used for non-codebook-based and codebook-based precoding). + +For the DMRS and SRS to occupy identical SCs and maximize their frequency density, DMRS configuration type 1 and SRS comb2 configuration are used. + +UL RMC described in Annex A.2 is used. + +### G.2.2 CFO (carrier frequency offset) correction + +The TE performs a CFO correction on a slot-by-slot basis using a common frequency correction at the two uplink layers. + +### G.2.3 Steps of the measurement method + +Below are detailed the steps necessary to obtain the maximum difference of relative phase error during the 20ms time window. + +- 1 Determination for each subcarrier and at each antenna port, the SRS relative phase error based on the last SRS transmitted on Ant1 and Ant2, that relative phase error serves as a reference for the calculation of the difference of relative phase error for each slot inside the 20 ms time window. + +The output is the “SRS relative phase error” vector for the last SRS transmitted: . + +- 2 Calculation for the last SRS transmitted, for each RB of the SRS relative phase errors based on the arithmetic mean of the subcarrier SRS relative phase errors determined in previous step. + +The output is the “SRS relative phase error” vector for the last SRS transmitted: . + +- 3 CFO correction on slot-by-slot basis using a common frequency correction for both antenna ports. + +- 4 Determination for each subcarrier and at each antenna, the phase over the slot being analyzed. The phase is extracted from the channel estimate derived from the 3 DMRS symbols of the slot using the LSE technique. + +The output is one vector of dimension $N_{ant}$ for each antenna port. + +- 5 Calculation for a slot for each subcarrier of the relative phase error (difference between the vectors determined in the previous step). + +The output is subcarrier relative phase errors of a slot: $\Delta\phi_{sc}$ . + +- 6 Calculation for a slot, for each RB of the relative phase errors based on the arithmetic mean of the subcarrier relative phase errors determined in previous step. + +The output is a “slot relative phase error” vector for a slot: $\Delta\phi_{RB}$ . + +- 7 Calculation for a slot of the difference of relative phase errors based on the “SRS relative phase error” (reference) determined in step 2 and the “slot relative phase error” determined in previous step. + +The output is a “difference of relative phase error” vector for a slot: $\Delta\phi_{diff}$ . + +- 8 Calculation for a slot of the arithmetic mean value of the “difference of relative phase error” vector determined in previous step, this value corresponds to an RB. + +The output is a “difference of relative phase error” value for a slot: $\Delta\phi_{diff\_mean}$ . + +- 9 Perform for each slot of the 20ms time window, steps 3 to 8. + +The output is a “difference of relative phase error” vector: $\Delta\phi_{diff\_vec}$ . + +- 10 Calculation of the maximum value of the “difference of relative phase error”. + +The output is the “difference of relative phase error” that should be verified as complying with the 40° maximum allowable difference of relative phase error requirement: $\Delta\phi_{max}$ . + +--- + +## Annex H (Normative): Modified MPR behavior + +### H.1 Indication of modified MPR behavior + +This annex contains the definitions of the bits in the field *modifiedMPR-Behavior* indicated per supported NR band in the IE *RF-Parameters* [13] by a UE supporting an MPR or A-MPR modified in a given version of this specification. A modified MPR or A-MPR behaviour can apply to a supported NR band in stand-alone operation (including CA and NN-DC operation) or in non-standalone operation with the said NR band as part of an EN-DC or NE-DC band combination. Moreover, the bits in the field can explicitly indicate NS value(s) supported by a UE. + +NOTE 1: In the present release, the *modifiedMPR-Behavior* is indicated [13] by an 8-bit bitmap per supported NR band. + +**Table H.1-1: Definitions of the bits in the field *modifiedMPRbehavior*** + +| NR Band | Index of field
(bit number) | Definition
(description of the supported functionality if
indicator set to one) | Notes | +|----------------|----------------------------------------|---------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------| +| n257 | 0 (leftmost bit) | - FR2 power class 3 MPR as defined in clause 6.2.2.3 of 38.101-2 | - This bit shall be set to 1 by a UE supporting n257 | +| n258 | 0 (leftmost bit) | - FR2 power class 3 MPR as defined in clause 6.2.2.3 of 38.101-2 | - This bit shall be set to 1 by a UE supporting n258 | +| | 1 | Void | | +| | 2 | - NS_203 as defined in clause 6.5.3.2.4 or both NS_203 and CA_NS_203 as defined in clause 6.5A.3.2.4 of 38.101-2 v15.11.0 | - This bit shall be set to 1 by a UE supporting n258 or both n258 and CA_n258 | +| n260 | 0 (leftmost bit) | - FR2 power class 3 MPR as defined in clause 6.2.2.3 of 38.101-2 | - This bit shall be set to 1 by a UE supporting n260 | +| n261 | 0 (leftmost bit) | - FR2 power class 3 MPR as defined in clause 6.2.2.3 of 38.101-2 | - This bit shall be set to 1 by a UE supporting n261 | + +--- + +Annex I (informative): Void + +## Annex J (normative): UE coordinate system + +### J.1 Reference coordinate system + +This annex defines the measurement coordinate system for the NR UE. The reference coordinate system as defined in IEEE Std 149 [15] is provided in Figure J.1-1 below while Figure J.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. + +![Diagram of the reference coordinate system showing axes +x, +y, +z, and polarization vectors labeled phi-polarization and theta-polarization.](a4495e80db9a7e1a890da12eb8c07360_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. 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. Two orthogonal polarization vectors are shown at a point on the sphere's surface. The $\phi$ -polarization vector is tangent to the sphere's surface, pointing in the direction of increasing $\phi$ (azimuthal angle). The $\theta$ -polarization vector is also tangent to the sphere's surface, pointing in the direction of increasing $\theta$ (polar angle). The angle $\theta$ is measured from the +z-axis down to the position vector. The angle $\phi$ is measured in the xy-plane from the +y-axis to the projection of the position vector. A dashed line indicates the projection of the position vector onto the xy-plane. A label '(To Antenna)' is placed along the $\theta$ -polarization vector. + +Diagram of the reference coordinate system showing axes +x, +y, +z, and polarization vectors labeled phi-polarization and theta-polarization. + +Figure J.1-1: Reference coordinate system + +![Diagram of a mobile device showing its default alignment to a coordinate system. The device is a vertical rectangle with a screen and three buttons at the bottom. A vertical arrow labeled '+Z' points upwards from the top of the device, with the text 'Top of phone' next to it. A horizontal arrow labeled '+Y' points to the right from the side of the device, with the text 'Side of phone' next to it. A diagonal arrow labeled '+X' points towards the bottom-left from the front of the device, with the text 'Screen looks this way' next to it.](8be2969598fb65f80907b8bbc140a98f_img.jpg) + +Diagram of a mobile device showing its default alignment to a coordinate system. The device is a vertical rectangle with a screen and three buttons at the bottom. A vertical arrow labeled '+Z' points upwards from the top of the device, with the text 'Top of phone' next to it. A horizontal arrow labeled '+Y' points to the right from the side of the device, with the text 'Side of phone' next to it. A diagonal arrow labeled '+X' points towards the bottom-left from the front of the device, with the text 'Screen looks this way' next to it. + +**Figure J.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 points inside the test chamber is needed in order to define unambiguous DUT orientation, DUT beam, signal, interference, and measurement angles + +## J.2 Test conditions and angle definitions + +Tables J.2-1 through J.2-3 below provides the test conditions and angle definitions for three permitted device alignment for the default test condition, DUT orientation 1, and two different options for each permitted device alignment to re-position the device for DUT Orientation 2 as outlined by figures in Tables J.2-1 through J.2-3. + +**Table J.2-1: Test conditions and angle definitions for Alignment Option 1** + +| Test condition | DUT orientation | Link angle | Measurement angle | Diagram | +|----------------------------------------------------------------------------|---------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Free space DUT Orientation 1 (default) | $\alpha = 0^\circ$ ;
$\beta = 0^\circ$ ;
$\gamma = 0^\circ$ | $\theta_{\text{Link}}$ ;
$\phi_{\text{Link}}$
with
polarization
reference
$\text{Pol}_{\text{Link}} = \theta$ or
$\phi$ | $\theta_{\text{Meas}}$ ;
$\phi_{\text{Meas}}$
with
polarization
reference
$\text{Pol}_{\text{Meas}} = \theta$ or
$\phi$ | Diagram for Orientation 1 (default) showing a smartphone with axes +X, +Y, +Z. Rotations are indicated by red curved arrows: Rotation Matrix R_z(gamma) around the Z-axis, Rotation Matrix R_x(alpha) around the X-axis, and Rotation Matrix R_y(beta) around the Y-axis. | +| Free space DUT Orientation 2 – Option 1 (based on re-positioning approach) | $\alpha = 180^\circ$ ;
$\beta = 0^\circ$ ;
$\gamma = 0^\circ$ | $\theta_{\text{Link}}$ ;
$\phi_{\text{Link}}$
with
polarization
reference
$\text{Pol}_{\text{Link}} = \theta$ or
$\phi$ | $\theta_{\text{Meas}}$ ;
$\phi_{\text{Meas}}$
with
polarization
reference
$\text{Pol}_{\text{Meas}} = \theta$ or
$\phi$ | Diagram for Orientation 2 – Option 1 showing a smartphone with axes +X, +Y, +Z. Rotations are indicated by red curved arrows: Rotation Matrix R_z(gamma) around the Z-axis, Rotation Matrix R_x(alpha) around the X-axis, and Rotation Matrix R_y(beta) around the Y-axis. | +| Free space DUT Orientation 2 – Option 2 (based on re-positioning approach) | $\alpha = 0^\circ$ ;
$\beta = 180^\circ$ ;
$\gamma = 0^\circ$ | $\theta_{\text{Link}}$ ;
$\phi_{\text{Link}}$
with
polarization
reference
$\text{Pol}_{\text{Link}} = \theta$ or
$\phi$ | $\theta_{\text{Meas}}$ ;
$\phi_{\text{Meas}}$
with
polarization
reference
$\text{Pol}_{\text{Meas}} = \theta$ or
$\phi$ | Diagram for Orientation 2 – Option 2 showing a smartphone with axes +X, +Y, +Z. Rotations are indicated by red curved arrows: Rotation Matrix R_z(gamma) around the Z-axis, Rotation Matrix R_x(alpha) around the X-axis, and Rotation Matrix R_y(beta) around the Y-axis. | + +NOTE 1: A polarization reference, as defined in relation to the reference coordinate system in J.1-1, is maintained for each signal angle, link or interferer angle, and measurement angle. + +NOTE 2: The combination of rotations is captured by matrix $M = R_z(\gamma) \cdot R_y(\beta) \cdot R_x(\alpha)$ + +**Table J.2-2: Test conditions and angle definitions for Alignment Option 2** + +| Test condition | DUT orientation | Link angle | Measurement angle | Diagram | +|----------------------------------------------------------------------------|----------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Free space DUT Orientation 1 (default) | $\alpha = 0^\circ$ ;
$\beta = -90^\circ$ ;
$\gamma = 0^\circ$ | $\theta_{\text{Link}}$ ;
$\phi_{\text{Link}}$
with
polarization reference
$\text{Pol}_{\text{Link}} = \theta$ or $\phi$ | $\theta_{\text{Meas}}$ ;
$\phi_{\text{Meas}}$
with
polarization reference
$\text{Pol}_{\text{Meas}} = \theta$ or $\phi$ |

Image: Diagram for Orientation 1 showing a rectangular DUT with axes +X, +Y, and +Z. Rotations are indicated by curved arrows: Matrix R_x(alpha) around the X-axis, Matrix R_y(beta) around the Y-axis, and Matrix R_z(gamma) around the Z-axis.

| +| Free space DUT Orientation 2 – Option 1 (based on re-positioning approach) | $\alpha = 180^\circ$ ;
$\beta = 90^\circ$ ;
$\gamma = 0^\circ$ | $\theta_{\text{Link}}$ ;
$\phi_{\text{Link}}$
with
polarization reference
$\text{Pol}_{\text{Link}} = \theta$ or $\phi$ | $\theta_{\text{Meas}}$ ;
$\phi_{\text{Meas}}$
with
polarization reference
$\text{Pol}_{\text{Meas}} = \theta$ or $\phi$ |

Image: Diagram for Orientation 2 Option 1 showing a rectangular DUT with axes +X, +Y, and +Z. Rotations are indicated by curved arrows: Matrix R_x(alpha) around the X-axis, Matrix R_y(beta) around the Y-axis, and Matrix R_z(gamma) around the Z-axis.

| +| Free space DUT Orientation 2 – Option 2 (based on re-positioning approach) | $\alpha = 0^\circ$ ;
$\beta = 90^\circ$ ;
$\gamma = 0^\circ$ | $\theta_{\text{Link}}$ ;
$\phi_{\text{Link}}$
with
polarization reference
$\text{Pol}_{\text{Link}} = \theta$ or $\phi$ | $\theta_{\text{Meas}}$ ;
$\phi_{\text{Meas}}$
with
polarization reference
$\text{Pol}_{\text{Meas}} = \theta$ or $\phi$ |

Image: Diagram for Orientation 2 Option 2 showing a rectangular DUT with axes +X, +Y, and +Z. Rotations are indicated by curved arrows: Matrix R_x(alpha) around the X-axis, Matrix R_y(beta) around the Y-axis, and Matrix R_z(gamma) around the Z-axis.

| + +NOTE 1: A polarization reference, as defined in relation to the reference coordinate system in J.1-1, is maintained for each signal angle, link or interferer angle, and measurement angle. + +NOTE 2: The combination of rotations is captured by matrix $M = R_z(\gamma) \cdot R_y(\beta) \cdot R_x(\alpha)$ + +**Table J.2-3: Test conditions and angle definitions for Alignment Option 3** + +| Test condition | DUT orientation | Link angle | Measurement angle | Diagram | +|-----------------------------------------------------------------------------------------------|--------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Free space
DUT
Orientation 1
(default) | $\alpha = 90^\circ;$
$\beta = 0^\circ;$
$\gamma = 0^\circ$ | $\theta_{\text{Link}};$
$\phi_{\text{Link}}$
with
polarization
reference
$\text{Pol}_{\text{Link}} = \theta$ or
$\phi$ | $\theta_{\text{Meas}};$
$\phi_{\text{Meas}}$
with
polarization
reference
$\text{Pol}_{\text{Meas}} = \theta$ or
$\phi$ |

Image: Diagram for Orientation 1 (default) showing a DUT with rotation axes X, Y, and Z. Rotations are labeled as Matrix R_x(alpha), Matrix R_y(beta), and Matrix R_z(gamma).

| +| Free space
DUT
Orientation 2
– Option 1
(based on re-
positioning
approach) | $\alpha = -90^\circ;$
$\beta = 0^\circ;$
$\gamma = 0^\circ$ | $\theta_{\text{Link}};$
$\phi_{\text{Link}}$
with
polarization
reference
$\text{Pol}_{\text{Link}} = \theta$ or
$\phi$ | $\theta_{\text{Meas}};$
$\phi_{\text{Meas}}$
with
polarization
reference
$\text{Pol}_{\text{Meas}} = \theta$ or
$\phi$ |

Image: Diagram for Orientation 2 – Option 1 showing a DUT with rotation axes X, Y, and Z. Rotations are labeled as Matrix R_x(alpha), Matrix R_y(beta), and Matrix R_z(gamma).

| +| Free space
DUT
Orientation 2
– Option 2
(based on re-
positioning
approach) | $\alpha = 90^\circ;$
$\beta = 180^\circ;$
$\gamma = 0^\circ$ | $\theta_{\text{Link}};$
$\phi_{\text{Link}}$
with
polarization
reference
$\text{Pol}_{\text{Link}} = \theta$ or
$\phi$ | $\theta_{\text{Meas}};$
$\phi_{\text{Meas}}$
with
polarization
reference
$\text{Pol}_{\text{Meas}} = \theta$ or
$\phi$ |

Image: Diagram for Orientation 2 – Option 2 showing a DUT with rotation axes X, Y, and Z. Rotations are labeled as Matrix R_x(alpha), Matrix R_y(beta), and Matrix R_z(gamma).

| + +NOTE 1: A polarization reference, as defined in relation to the reference coordinate system in J.1-1, is maintained for each signal angle, link or interferer angle, and measurement angle. + +NOTE 2: 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 J.2-1 through J.2-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 + +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. + +## J.3 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 arrays 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 the DUT by directing the beam peak away from those areas can reduce the effect of signal ripple on EIRP/EIS measurements. Figure J.3-1 and J.3-2 illustrate how to reposition the DUT in distributed axes and combined axes system, when the beam peak is directed to the DUTs upper hemisphere (DUT orientation 1) or the DUTs lower hemisphere (DUT orientation 2). While these figures are examples of different positioning systems and other implementations are not precluded, the relative orientation of the coordinate system with respect to the antennas/reflectors and the axes of rotation shall apply to any measurement setup. + +![Figure J.3-1: DUT re-positioning for an example of distributed-axes system. The figure shows two diagrams side-by-side separated by a vertical line. The left diagram is titled 'Distributed-Axes System: DUT Orientation 1' and shows a spherical DUT on a pedestal. The top half is yellow and labeled 'Top', the bottom half is white and labeled 'Bot'. A yellow curved arrow indicates rotation around the vertical axis, and a black curved arrow indicates rotation around a horizontal axis. The right diagram is titled 'Distributed-Axes System: DUT Orientation 2' and shows the same DUT, but the top half is white and labeled 'Bz', and the bottom half is yellow and labeled 'Tx'. It also has yellow and black curved arrows indicating rotation.](748eb98c2d6720f0985fddd1764fa9a1_img.jpg) + +Figure J.3-1: DUT re-positioning for an example of distributed-axes system. The figure shows two diagrams side-by-side separated by a vertical line. The left diagram is titled 'Distributed-Axes System: DUT Orientation 1' and shows a spherical DUT on a pedestal. The top half is yellow and labeled 'Top', the bottom half is white and labeled 'Bot'. A yellow curved arrow indicates rotation around the vertical axis, and a black curved arrow indicates rotation around a horizontal axis. The right diagram is titled 'Distributed-Axes System: DUT Orientation 2' and shows the same DUT, but the top half is white and labeled 'Bz', and the bottom half is yellow and labeled 'Tx'. It also has yellow and black curved arrows indicating rotation. + +Figure J.3-1: DUT re-positioning for an example of distributed-axes system + +![Figure J.3-2: DUT re-positioning for an example of combined-axes system. The figure shows two diagrams side-by-side separated by a vertical line. The left diagram is titled 'Combined-Axes System: DUT Orientation 1' and shows a spherical DUT on a pedestal. The left half is white and labeled 'Bot', the right half is yellow and labeled 'Top'. A yellow curved arrow indicates rotation around the vertical axis, and a black curved arrow indicates rotation around a horizontal axis. The right diagram is titled 'Combined-Axes System: DUT Orientation 2' and shows the same DUT, but the left half is yellow and labeled 'Top', and the right half is white and labeled 'Bot'. It also has yellow and black curved arrows indicating rotation.](149f02d2530e569ed6d528bf1acc9912_img.jpg) + +Figure J.3-2: DUT re-positioning for an example of combined-axes system. The figure shows two diagrams side-by-side separated by a vertical line. The left diagram is titled 'Combined-Axes System: DUT Orientation 1' and shows a spherical DUT on a pedestal. The left half is white and labeled 'Bot', the right half is yellow and labeled 'Top'. A yellow curved arrow indicates rotation around the vertical axis, and a black curved arrow indicates rotation around a horizontal axis. The right diagram is titled 'Combined-Axes System: DUT Orientation 2' and shows the same DUT, but the left half is yellow and labeled 'Top', and the right half is white and labeled 'Bot'. It also has yellow and black curved arrows indicating rotation. + +Figure J.3-2: DUT re-positioning for an example of combined-axes system + +For EIRP/EIS measurements, re-positioning the DUT makes sure the pedestal is not obstructing the beam path and that the pedestal is not in closer proximity to the measurement antenna/reflector than the DUT. For TRP measurements, re-positioning the DUT makes sure that the beam peak direction is not obstructed by the pedestal and the pedestal is in the measurement path only when measuring the back-hemisphere. No re-positioning during the TRP measurement is required. + +--- + +## Annex K (informative): Void + +--- + +## Annex L (normative): Requirement metric for simultaneous reception from multiple directions + +--- + +### L.1 Spherical coverage grid for simultaneous reception or transmission in multiple directions + +The reference coordinate system grid is defined as follows: The grid is the set of locations described by a source/probe from the UE's perspective when the TE completes a 3D spherical scan with a constant step size for each rotational axis of its positioner. The grid comprises intersection points of circles of fixed polar angle (geographic analog: 'latitude') and meridians of fixed azimuthal angle (geographic analog: 'longitude') and completely covers the sphere around the UE. A valid set of locations for the source/probes are those that describes the same constant step size grid from the UE's perspective over a complete spherical scan. This condition is satisfied when the active probes/sources are always contained in a plane of constant azimuthal angle ' $\phi$ ' in this reference system. The reference coordinate system with example UE orientations is shown in figures J.2-x. + +--- + +### L.2 Probability to support 2AoA reception + +For UEs required to fulfil a requirement on the probability for 2AoA reception, the metric for a given AoA separation is the spatial average: + +Where: + +$(\theta_1, \phi_1)$ are coordinates of any grid point in the UE-centered reference system described above. + +$AW(\theta_1)$ is the area weight associated with each grid point with polar angle ' $\theta_1$ ', and: + +$P_{directional}(\theta_1, \phi_1)$ is the probability that the direction given by coordinates $(\theta_1, \phi_1)$ can support 2 AoA reception under the agreed UERF test conditions. $P_{directional}(\theta_1, \phi_1)$ is given by: + +Where: + +$AoA_{pair\#x}$ represents an AoA pair with the chosen AoA separation of test that has one source at coordinates $(\theta_1, \phi_1)$ . + +'n' is the maximum number of unique AoA pairs that the TE can generate with one source at coordinates $(\theta_1, \phi_1)$ + +$PF(AoA_{pair\#x})$ is the pass/fail outcome (1/0 respectively) of the throughput verification test + +## Annex M (informative): Change history + +| Change history | | | | | | | | +|----------------|-------------|------------|------|-----|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-08 | RAN4#84 | | | | | Initial Skeleton | 0.0.1 | +| 2017-10 | RAN4#84 Bis | R4-1711979 | | | | TPs from R4#84Bis by editors | 0.1.0 | +| 2017-12 | RAN4#85 | R4-1713806 | | | | Approved TPs from R4#85
R4-1714537, TP for TS 38.101-2: Channel Bandwidth Definition, Qualcomm Incorporated
R4-1714115, TP for TS 38.101-2: Channel Arrangement, : Qualcomm Incorporated (Note: this TP was further discussed and edited in the reflector)
R4-1713205, TP on general parts for 38.101-2 NR FR, : Ericsson
R4-1712884, TP to TS38.101-2 on environmental conditions, Intel Corporation
R4-1714018, TP to TS 38.101-2 for definition of UE RF terminologies, Anritsu Corporation
R4-1714447, TP on UE power class for FR2, Intel Corporation
R4-1714372, TP to TS38.101-2 on EVM equalizer spectrum flatness requirements, Intel Corporation
R4-1714330, TP to TR 38.101-02 v0.1.0: ON/OFF mask design for NR UE transmissions for FR2, Ericsson
R4-1714364, TP to TR 38.101: NR UE transmit OFF power for FR2, CATT
R4-1714347, TP to TS38.101-2 on spurious emissions requirements for FR2, Intel Corporation (Note: this TP was further discussed and edited in the reflector)
R4-1714456, TP on REFSSENS for FR2, Intel Corporation
R4-1714337 TP to TS 38.101-2 ACS requirement for mmW (section 7.5), Qualcomm Incorporated
R4-1714338, TP to TS 38.101-2 IBB requirement for mmW (section 7.6.1), Qualcomm Incorporated
R4-1714348, TP to TS38.101-2 on Rx spurious emissions for FR2, Intel Corporation
Min power for EVM requirement according to R4-1711568, TP to TR 38.xxx - UE minimum transmit power for range 2, CATT
Band list according to R4-1714542, List of bands and band combinations to be introduced into RAN4 NR core requirements by December 2017, RAN4 Chairmen | 0.2.0 | +| 2017-12 | RAN4#85 | R4-1714570 | | | | Further corrections and alignments with 38.104 after email review | 0.3.0 | +| 2017-12 | RAN#78 | RP-172476 | | | | v1.0.0 submitted for plenary approval. Contents same as 0.3.0 | 1.0.0 | +| 2017-12 | RAN#78 | | | | | Approved by plenary – Rel-15 spec under change control | 15.0.0 | +| 2018-03 | RAN#79 | RP-180264 | 0004 | | F | Implementation of endorsed CR on to 38.101-2
Endorsed draft CRs in RAN4-NR-AH#1801
F: R4-1800918, Draft CR to 38.101-2 on channel bandwidth corrections (5.3.5), Nokia
F: R4-1801097, Modification for TS38.101-2, CATT
F: R4-1801098 Draft CR for TS38.101-2: On requirement metrics. Sumitomo Elec. Industries, Ltd
F: R4-1800401, Editorial corrections to 38.101-2, Qualcomm
F: R4-1801122: Draft pCR for TS 38.101-2 version 15.0.0: Remaining ON/OFF masks for FR2 NR UE transmissions, Ericsson
F: R4-1800418, Correction of NR SEM for FR2 table, vivo
F: R4-1800316 Draft CR to 38.101-2: Tx spurious emission for NR FR2 (section 6.5.3 ), ZTE Corporation
F: R4-1800918 Draft CR to 38.101-2 on channel bandwidth corrections (5.3.5), Nokia
F: R4-1801013, Draft CR to 38.101-2: Clarifications to UE spectrum utilization section 5.3, Ericsson
F: R4-1801229, Draft CR to 38.101-2: Channel spacing for CA for NR FR2(section 5.4.1.2), ZTE Corporation
F: R4-1801232, Correction CR for channel spacing:38.101-2, Samsung
F: R4-1801325, Draft CR to TS 38.101-2: Corrections on channel | 15.1.0 | + +| | | | | | | | | +|---------|--------|-----------|------|--|---|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| | | | | | | raster calculation in section 5.4.2, ZTE Corporation
F: R4-1800860, Corrections of GSCN, Nokia

Endorsed draft CRs in RAN4#86

R4-1803054, Draft CR for new spec structure of 38.101-2, Ericsson
R4-1801446, Modification for NR UE time mask requirement for FR2, CATT
R4-1801729, Draft CR to 38.101-2: Corrections to In-band blocking requirements, Rohde & Schwarz
R4-1801967, CR on EVM spectrum flatness for FR2, Huawei
R4-1802339, Draft CR to 38.101-2: Clarifications on peak directions and REFSENS, ROHDE & SCHWARZ
R4-1802567, Draft CR to TS 38.101-2: Clarification of mixed numerology guardband size, Ericsson
R4-1803238, Draft CR for TS 38.101-2: ACLR requirement clarification, Huawei
R4-1803365, Draft CR to 38.101-2: Clarification on REFSENS Definition, ROHDE & SCHWARZ
R4-1803453, draft CR for introduction of completed band combinations from 37.865-01-01 into 38.101-2, Ericsson
R4-1803566, Draft CR for TS 38.101-2: Sync raster offset in re-farming bands (5.4.3), Ericsson | | +| 2018-06 | RAN#80 | RP-181262 | 0010 | | F | CR to TS 38.101-2: Implementation of endorsed draft CRs from RAN4 #86bis and RAN4 #87

Endorsed draft CRs from RAN4#86Bis
R4-1803736, Draft CR on channel raster entry of band n258 for TS 38.101-2, ZTE Wistron Telecom AB
R4-1804022, CR for modifications and clarifications for NR FR2 CA BW Classes, Nokia
R4-1804585, Draft CR to 38.101-2: IBE Section Update, Qualcomm, Inc.
R4-1804657, Introduction of UE to UE coexistence requirements requirements for FR2, Qualcomm Incorporated
R4-1804949, Corrections to 5.3.3 in TS 38.101-2, Nokia
R4-1805641, Corrections of BCS for n257 intraband contiguous CA in 38.101-2, Nokia
R4-1805685, Draft CR to TS38.101-2: Channel Raster to Resource Element Mapping (Section 5.4.2.2) and RB alignment with different numerologies (Section 5.3.4), ZTE Corporation
R4-1805704, Update of UE emission requirements for FR2, Qualcomm Incorporated
R4-1805705, Draft CR to 38.101-2: Update of section 7.1, Rohde & Schwarz
R4-1805757, Update of ACS requirement for FR2, Qualcomm Incorporated
R4-1805771, Update of IBB requirement for FR2, Qualcomm Incorporated
R4-1805775, draft CR for TS 38.101-2 on US 28 GHz band number, Qualcomm Incorporated
R4-1805949, Draft CR on minimum guardband of SCS 240 kHz SSB for TS 38.101-2, ZTE Wistron Telecom AB
R4-1805982, draft CR for 38.101-2: sync raster, Samsung
R4-1804878, draft CR introduction completed band combinations 37.865-01-01 -> 38.101-2, Ericsson
R4-1803628, pi/2 BPSK related CR, IITH

Endorsed draft CRs from RAN#87

R4-1806167, Draft CR on channel raster entry of band n261 for TS 38.101-2, ZTE Corporation
R4-1806169, Draft CR on SSB clarification for TS 38.101-2, ZTE Corporation
R4-1806383, Draft CR of clarifications on TRx RF test metrics for mmWave, Anritsu Corporation
R4-1806946, Draft CR for TS 38.101-2: Channel raster and NR-ARFCN clarification (5.4.2), Ericsson
R4-1807652, FR2 UE ACLR requirement for CA, Qualcomm
R4-1807655, Further refinements for UE Rx requirements in FR2, Qualcomm
R4-1807681, Draft CR on 38.101-2 on channel raster to achieve alignment of data and SSB subcarrier grids, Nokia
R4-1807853, Draft CR to TS 38.101-2: UE maximum output power for UL CA, Nokia
R4-1807855, Draft CR on 38.101-2: Transmit ON/OFF time mask for UL CA, Nokia | 15.2.0 | + +| | | | | | | | | +|---------|--------|-----------|------|--|---|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| | | | | | | R4-1807857, Draft CR on 38.101-2: Occupied BW for UL CA, Nokia
R4-1808101, Draft CR to 38.101-2: On EVM Averaging Length, Wording, Qualcomm Incorporated
R4-1808105, Configured maximum output power for FR2, Ericsson
R4-1808124, draft CR on UE RF requirement for UE type 2 in FR2, LG Electronics
R4-1808125, Draft CR to TS 38.101-2: Minimum output and OFF Power, Nokia
R4-1808147, Draft CR for NR FR2 CA BW class modifications, MediaTek Inc.
R4-1808148, EVM equaliser spectral flatness for FR2, Ericsson
R4-1808149, UE Shaping Filter Requirement for pi/2 BPSK, Indian Institute of Tech (M)
R4-1808152, Draft CR for Finalizing UE RF Requirement for FWA, Samsung
R4-1808266, Draft CR for TS 38.101-2: Channel and sync raster corrections (5.4), Ericsson
R4-1808545, Draft CR on UE RF requirement for UE type 3 in FR2, Verizon
R4-1808546, Power class 3 Spherical coverage introduction and peak EIRP requirement update, Qualcomm
R4-1808206, Draft CR to 38.101-2: FR2 Type 1 UE Power Control, Qualcomm
R4-1808208, Draft CR to 38.101-2: FR2 Type 1 UE CA EIS update, Qualcomm
R4-1808191, TP to TS38.101-2 - UE ON/OFF masks, Ericsson
R4-1807102, draft CR introduction completed band combinations 37.865-01-01 -> 38.101-2, Ericsson | | +| 2018-09 | RAN#81 | RP-181896 | 0015 | | F | Big CR for 38.101-2

Endorsed draft CRs from RAN4#NR-AH-1807
R4-1809336, Draft CR on UL RMC for FR2 RF tests, Qualcomm Incorporated
R4-1809338, Draft CR on NR UE REFSSENS SNR FRC for FR2, Intel Corporation
R4-1809397, Draft CR on measurement of receiver characteristics for FR2 RF Tests, Qualcomm Incorporated
R4-1809566, Draft CR on OCNG pattern for FR2 REFSSENS test, Qualcomm Incorporated

Endorsed draft CR s from RAN4#88

R4-1809817, TP to TS 38.101-2 on ON/OFF time mask, Intel Corporation
R4-1809976, Draft CR for TS 38.101-2: Channel raster corrections (5.4.2), Ericsson
R4-1810092, Draft CR TS 38.101-2 - UE ON-OFF mask clean up, Ericsson
R4-1810211, Draft CR for TS 38.101-2: MPR inner and outer RB allocations formula correction, MediaTek Inc.
R4-1810228, draft CR on UL-MIMO requirement for Power Class 2 in FR2, LG Electronics Inc
R4-1810373, Draft CR to 38.101-2: Corrections on symbols and abbreviations in section 3, ZTE Corporation
R4-1810805, Draft CR to TS 38.101-2: Spurious emissions, Nokia
R4-1810863, Draft CR to 38.101-2: Addition of Transmit Modulation Annex, Rohde & Schwarz
R4-1811026, Draft CR to 38.101-2: FR2 UE CA Transmit Signal Quality update, Qualcomm Incorporated
R4-1811104, Finalization of SEM requirements in FR2, Qualcomm Incorporated
R4-1811140, FR2 ULMIMO Updates and enhancements, Qualcomm Incorporated
R4-1811322, Draft CR to 38.101-2: REFSSENS of power class 1, Intel Corporation
R4-1811456, Draft CR on DL Physical Channel for FR2 RF tests, Qualcomm Inc
R4-1811460, Draft CR to 38.101-2: Correct both Table 5.5A.2-1 and Table 5.5A.2-2, Verizon
R4-1811489, Draft CR to 38.101-2: FR2 Power Control, Qualcomm Incorporated
R4-1811499, Implementation of additional requirement to protect passive EESS in 23.6-24GHz, Qualcomm Incorporated
R4-1811515, Draft CR to TS 38.101-2: Clarification on OCNG, Keysight Technologies UK Ltd
R4-1811517, Draft CR on NR DL FRCs for FR2 UE RF requirements, Intel Corporation | 15.3.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| | | | | | | R4-1811519, Draft CR to 38.101-2: On FR2 MPR for single CC PC1 and PC3, Qualcomm
R4-1811520, Draft CR to 38.101-2: FR2 Max. Input Power, Qualcomm Incorporated
R4-1811524, Clarification of UL MIMO for FR2, OPPO
R4-1811551, Draft CR to TS 38.101-2 on channel bandwidth and spacing descriptions, Ericsson
R4-1811554, Draft CR to 38.101-2: Corrections on description of channel raster entries, ZTE Corporation
R4-1811802, Draft CR to TS 38.101-2 update the Pumax tolerance table for configured transmitted power, Intel Corporation
R4-1811807, Draft CR to 38.101-2: FR2 UE Transmit Signal Quality update, Qualcomm Incorporated
R4-1811813, Correction on UE transmitter requirement for FR2, CATT
R4-1811817, Updated ON/OFF mask for FR2, vivo
R4-1811800, DRAFT CR for PCmax FR2 correction, Qualcomm Incorporated | | +| 2018-12 | RAN#82 | RP-182899 | 0016 | 2 | F | Endorsed draft CR s from RAN4#88Bis:
R4-1812122, Draft CR for FR2 ACLR Measurement BW, Qualcomm
R4-1812134, CR on Out of Band Blocking for FR2, Intel Corporation
R4-1812426, draft CR of MPR for Power Class 2 in FR2, LG Electronics
R4-1812428, draft CR of transmit signal quality for Power Class 2 in FR2, LG Electronics
R4-1812453, Draft CR to TS 38.101-2 Adjust placement of 0dB MPR reference waveform, Intel Corporation
R4-1812495, Draft CR to 38.101-2: Corrections on channel raster & SS raster, ZTE Corporation
R4-1813470, draftCR on applicability of TDD configuratiin for CA in TS 38.101-2, Huawei
R4-1813472, draftCR on CA spectrum Emission for TS 38.101-2, Huawei
R4-1813473, draftCR on coherent UL MIMO for TS 38.101-2, Huawei
R4-1813527, Correction to FR2 spurious emission requirement, Nokia
R4-1813585, Draft CR to Specify UL Power for FR2 REFSSENS Test Cases, Keysight
R4-1813815, Draft CR to 38.101-2: Corrections on configurations for intra-band non-contiguous CA, ZTE Corporation
R4-1814149, Changes to FR2 UL MIMO, OPPO
R4-1814180, Draft CR to TS 38.101-2 on channel arrangement descriptions, LG Electronics Inc.
R4-1814181, Draft CR to 38.101-2: Corrections on the descriptions of UE channel bandwidth for CA, ZTE Corporation
R4-1814163, draft CR of operating band for Power Class 2 in FR2, LG Electronics
R4-1813834, Draft CR to 38.101-2: Update of Annex F, Rohde & Schwarz
R4-1814164, draftCR on MPR for TS 38.101-2, Huawei
R4-1814165, Draft CR to 38.101-2: FR2 Power Control for CA, Qualcomm Incorporated
R4-1814170, Draft CR to 38.101-2: FR2 UL Config for EIS Testing, Qualcomm Incorporated

Endorsed draft CR's from RAN4#89
R4-1815951, dCR on TS38.101-2 merging draft CRs from RAN4#89, Qualcomm Incorporated
R4-1814497, Correction on UL MIMO requirement for PC1 UE, Samsung
R4-1814585, Draft CR to TS 38.101-2 UL CA power control in FR2, Intel Corporation
R4-1814698, Draft CR to TS38.101-2 updating references, Apple Inc.
R4-1815623, Draft CR to 38.101-2: FR2 Max. Input Power UL Configuration, Qualcomm Incorporated
R4-1815801, draft CR editorial correction in 38.101-2, Ericsson
R4-1815810, draft Rel-15 CR to 38.101-2 to include n260 fallbacks needed, Ericsson
R4-1815942, dCR on P-MPR for FR2, Qualcomm Incorporated
R4-1815943, dCD Coherent UL MIMO parameters for FR2, Qualcomm Incorporated
R4-1816205, Draft CR to TS38.101-2 correcting the Pcmax requirement, Apple Inc.
R4-1816206, draft CR on Pcmax for ULCA and limitation on max aggregated ULCA BW, Qualcomm Incorporated | 15.4.0 | + +| | | | | | | | | +|---------|--------|-----------|------|--|---|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| | | | | | | R4-1816217, Draft CR to 38.101-2 on UE maximum output power with additional requirements, ZTE Corporation
R4-1816218, Draft CR for Introducing missing requirement for power class 4 in FR2 for TS 38.101-2, NTT DOCOMO, INC.
R4-1816219, draft CR of MPR for Power Class 2 in FR2, LG Electronics
R4-1816220, Draft CR to 38.101-2: On FR2 CA MPR v2, Qualcomm Incorporated
R4-1816239, Draft CR to 38.101-2: On FR2 EESS A-MPR for n258, Qualcomm Incorporated
R4-1816245, Draft CR to 38.101-2: FR2 EIS DL Signal Polarization Clarification, Qualcomm Incorporated
R4-1816257, Draft CR to TS38.101-2 to correct UL CA scope for FR2 in Rel-15, Apple Inc.
R4-1816605, TDD configuration for UE Tx test in FR2, Ericsson
R4-1816664, Draft CR to 38.101-2 (5.3.4) RB alignment, Huawei
R4-1816751, Draft CR for RF exposure compliance in TS38.101-2, LG Electronics France
R4-1816626, Draft CR to TS 38.101-2: Introducing multi-band applicability for PC3, Apple Inc.
R4-1816634, Draft CR to 38.101-2: FR2 EIS Spherical Coverage Requirement, Qualcomm Incorporated
R4-1816639, Verification of beam correspondence, Ericsson, Sony
R4-1816633, draft CR on UE type for Power Class 2 in FR2, LG Electronics
R4-1816644, Draft CR to TS 38.101-2: Temperature Condition for testing EIRP Spherical Coverage requirement, Apple Inc. | | +| 2019-03 | RAN#83 | RP-190747 | 0018 | | F | CR to TS 38.101-2: Implementation of endorsed draft CRs from RAN4#90 plus PC3 MPR changes to accommodate FR2 OBW

Endorsed draft CRs from RAN4#90
R4-1900049, Draft CR on UL RMC for FR2 UE RF Tests, Qualcomm Incorporated
R4-1900050, Draft CR on DL RMC for FR2 UE RF Tests, Qualcomm Incorporated
R4-1900131, draft CR to 38101-2 Correction to EVM equalizer spectrum flatness for Pi2 BPSK, Intel Corporation
R4-1900132, draft CR to 38101-2 FR2 transmit modulation quality for CA, Intel Corporation
R4-1900254, Draft CR on clarification of maxUplinkDutyCycle in FR2, OPPO
R4-1900301, Draft CR: Introduction of Annex on Characteristics of the Interfering Signal, Samsung
R4-1900386, CR to 38.101-2 on CA BW Classes fallback groups, Intel Corporation
R4-1900443, CR to chance Annex E2.1, Qualcomm Incorporated
R4-1900509, Draft CR to TS 38.101-2 on BCS definition for intra-band non-contiguous CA, ZTE Corporation
R4-1900531, draft CR on A-MPR for power class 2 in FR2, LG Electronics
R4-1900533, draft CR on maximum output power reduction for CA for power class 2 in FR2, LG Electronics
R4-1900535, draft CR on A-MPR for CA for power class 2 in FR2, LG Electronics
R4-1900542, Draft CR on Measurement period of PRACH time mask, Qualcomm Incorporated
R4-1900677, Draft CR to 38.101-2: FR2 ULMIMO max. output power, Qualcomm Incorporated
R4-1900674, Draft CR to 38.101-2: UL config for DL NC CA, Qualcomm Incorporated
R4-1900678, Draft CR to 38.101-2: EVM Requirement for PRACH, Qualcomm Incorporated
R4-1900679, Draft CR to 38.101-2: IBB requirement update, Qualcomm Incorporated
R4-1900680, Draft CR to 38.101-2: Complete Pmin requirement for CA, Qualcomm Incorporated
R4-1900728, Update to PRACH EVM window length for FR2, Rohde & Schwarz
R4-1900736, Draft CR on editorial error of TS38.101-2, LG Electronics Inc.
R4-1900755, Draft CR on spurious emission limit in 38.101-2, Qualcomm Incorporated
R4-1902005, Draft CR to 38.101-2: Add annex for UE coordinate system, Qualcomm Incorporated
R4-1902152, Editorial corrections for 38.101-2, Qualcomm Incorporated
R4-1902180, Draft CR to 38.101-2: correction of the relationship | 15.5.0 | + +| | | | | | | | | +|---------|--------|-----------|------|--|---|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| | | | | | |

between minimum requirements and test requirements, Apple Inc.

R4-1902345, draft_CR TS 38.101-2 FR1 frequency range extension, Skyworks Solutions Inc.

R4-1902474, Draft CR to 38.101-2: correction of multi-band aspects in REFSENS for PC3, Apple Inc.

R4-1902490, draftCR on maximum output power for TS 38.101-2, Huawei

R4-1902491, Draft CR for Multi-band relaxation to TS 38.101-2, NTT DOCOMO, INC.

R4-1902492, Draft CR on max input power in FR2, OPPO

R4-1902590, Draft CR to TS 38.101-2: Introduction of the requirement on beam correspondence, Apple Inc

Further changes in RAN#83:
Changes in Section 6.2.2.0 to modify the MPR=0dB waveform and Section 6.2.2.3 to modify the MPR tables to accommodate the OBW requirements

| | +| 2019-06 | RAN#84 | RP-191240 | 0021 | | F |

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

Endorsed draft CRs from RAN4#90Bis:

R4-1902932: Draft CR to TS 38.101-2 Correction to Pcmax, Intel Corporation

R4-1902976 Draft CR on PRACH and PUCCH format description for EVM in FR2 Anritsu corporation

R4-1903121 Draft CR on DL power allocation for TS 38.101-2 Intel Corporation

R4-1903242 Adding BCS definition in TS38.101-2 CATT

R4-1903474 draft CR of in-band emission for FR2 PC2 LG Electronics

R4-1903888 Draft CR: Alignment of FR2 DL scheduling of DL RMC with UL RMCEricsson

R4-1904001 Draft CR for TS 38.101-2 – UE coordinate system Rohde & Schwarz

R4-1904411 draft Rel-15 CR for editorial corrections in 38.101-2 Ericsson

R4-1904553 Draft CR to 38.101-2: FR2 power dynamics DTX removal Qualcomm Incorporated

R4-1904930 Draft CR to 38.101-2: Updating MPR wording in ULMIMO section Qualcomm Incorporated

R4-1904931 Draft CR to clarify frequency of carrier leakage in RBs for FR2 Anritsu corporation

R4-1904932 Draft CR on editorial error of TS38.101-2 LG Electronics France

R4-1904933 Draft CR on UE optional bandwidth for FR2 Huawei, HiSilicon

R4-1904956 Draft CR for TS 38.101-2: Corrections to configurations for intra-band non-contiguous CA MediaTek Inc.

R4-1904961 Draft CR for TR38.101-2 – Update to EVM averaging Rohde & Schwarz

R4-1904962 Draft CR to 38.101-2: FR2 ULMIMO EVM Qualcomm Incorporated

R4-1904966 Draft CR to TS 38.101-2 CA maximum input level Intel Corporation

R4-1904986 Draft CR for TS 38.101-2: Corrections to EVM equalizer spectrum flatness requirements MediaTek Inc.

R4-1904994 draft CR to 38.101-2 Correction to ACS and In-band Blocking notes Intel Corporation

R4-1905003 Draft CR to 38.101-2: FR2 PC3 and PC1 MPR Qualcomm Incorporated

R4-1905005 Draft CR for 38.101-2 frequency separation class Huawei, HiSilicon

Endorsed draft CRs from RAN4#91:

R4-1905504 Change description 4.2(d) in Applicability of minimum requirements for TS 38.101-2 vivo

R4-1905685 Draft CR to 38.101-2: FR2 Sensitivity Qualcomm Incorporated

R4-1905764 draft CR to 38.101-2 UE maximum output power reduction for UL-MIMO Intel Corporation

R4-1905765 draft CR to 38.101-2 UE maximum output power for UL-MIMO Intel Corporation

R4-1905796 Correction to a description of PRB for in-band emission in FR2 Anritsu Corporation

R4-1905798 Correction to power control in FR2 Anritsu

| 15.6.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| | | | | | | R4-1905821 Corporation
draft CR of loosening EIS for FR2 PC2 LG
Electronics Inc. | | +| | | | | | | R4-1907003 Draft CR for editorial corrections in TS 38.101-2
Google Inc. | | +| | | | | | | R4-1907420 draft CR of simple application for FR2 PC2 and 4
requirements with PC3 same requirements LG
Electronics Inc. | | +| | | | | | | R4-1907423 Draft CR for TS 38.101-2 Correction of channel
bandwidth set for NR CA Huawei, HiSilicon,
CMCC | | +| | | | | | | R4-1907437 Draft CR to 38.101-2: Insert definitions Qualcomm
Incorporated | | +| | | | | | | R4-1907443 Draft CR to TS38.101-2 Complete FR2 MPR/A-
MPR Intel Corporation | | +| | | | | | | R4-1907444 Amendment of the relative power tolerance
requirement Ericsson, Qualcomm Incorporated | | +| | | | | | | R4-1907446 Draft CR to 38.101-2: FR2 CA REFESNS
Qualcomm Incorporated | | +| | | | | | | R4-1907447 Draft CR to 38.101-2 on UL RMC slot patterns
Apple Inc. | | +| | | | | | | R4-1907466 Draft CR to 38.101-2: FR2 CA MPR enhancement
Qualcomm Incorporated | | +| | | | | | | R4-1907468 Draft CR to 38.101-2: FR2 MPR Wording CleanUp
Qualcomm Incorporated | | +| | | | | | | R4-1907473 Draft CR to TS38.101-2 on FR2 PC3 UE
maxUplinkDutyCycle Nokia, Nokia Shanghai Bell | | +| | | | | | | R4-1907478 Draft CR to TS 38.101-2 on configurations for intra-
band contiguous CA ZTE Corporation | | +| | | | | | | R4-1907493 Correction to Pcmx and Pumax for CA Ericsson | | +| | | | | | | R4-1907611 Draft CR to TS38.101-2 on beam correspondence
Samsung, Apple, Verizon | | +| | | | | | | R4-1907688 Correction to CA carrier spacing Ericsson | | +| 2019-06 | RAN#84 | RP-191241 | 0020 | | B | CR to REL-16 TS 38.101-2: Implementation of endorsed draft CRs
on NR combinations and dual Connectivity combinations | 16.0.0 | +| 2019-06 | RAN#84 | RP-191241 | 0022 | 1 | B | CR introduction completed band combinations 38.716-01-01 ->
38.101-2 | 16.0.0 | +| 2019-09 | RAN#85 | RP-192049 | 0028 | | A | CR to TS 38.101-2: Implementation of endorsed draft CRs from
RAN4#92 (Rel-16)
- Mirrors changes in R4-1910352 for Rel-15 TS 38.101-2

Endorsed draft CRs from RAN4#92
R4-1907999 Draft CR for NR non-contiguous CA configuration
Verizon, Nokia, Ericsson, Qualcomm
R4-1908082 draft CR to TS 38.101-2 on channel spacing for CA
Samsung, ZTE
R4-1908137 Update to FR2 EVM definition ROHDE &
SCHWARZ
R4-1908153 dCR to 38.101-2: Editorial corrections for 38.101-2
Qualcomm Incorporated
R4-1908573 Draft CR to TS 38.101-2: corrections on Rx
requirements for intra-band CA ZTE Corporation
R4-1908633 Draft CR to TS38.101-2: Corrections on EVM
window length (Section F.5)ZTE Corporation
R4-1908708 Draft CR to TS38.101-2: corrections on the receiver
spurious emission (section 7.9) ZTE Corporation
R4-1909117 Draft CR for 38.101-2 applicability for intra-band CA
Huawei
R4-1909316 Draft CR to TS 38.101-2 on symbols correction ZTE
Corporation
R4-1910235 Draft CR to TS38.101-2 for Rx RF requirements LG
Electronics Finland
R4-1910238 CR for Handling of fallbacks for combined
contiguous and non-contiguous CA in FR2 Apple
R4-1910241 Draft CR to TS 38.101-2 on NR CA configurations
for FR2 ZTE Corporation
R4-1910259 dCR to 38.101-2: Reference signal clarifications
Qualcomm Incorporated
R4-1910261 dCR to 38.101-2: FR2 AMPR updates, including
ERC 74-01 changes Qualcomm Incorporated
R4-1910287 dCR to 38.101-2: FR2 CA MPR refinement
Qualcomm Incorporated
R4-1910328 Draft CR to TS 38.101-2: Corrections for UL and DL
RMC for FR2 tests Intel Corporation
R4-1910333 Draft CR for 38.101-2 reference measurement
channel for beam correspondence Huawei | 16.1.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| | | | | | | R4-1910334 Draft CR for TS38.101-2, Editorial corrections
CATT
R4-1910412 Draft CR for 38.101-2 correction for channel raster
Huawei
R4-1910614 Draft CR for TS 38.101-2: Channel spacing for adjacent NR carriers ZTE
Conditional agreements for BC for PC1/2/4 from R4-1902252 | | +| 2019-09 | RAN#85 | RP-192027 | 0025 | 1 | F | Minor corrections of intra-band non-contiguous CA operating bands in TS 38.101-2 | 16.1.0 | +| 2019-09 | RAN#85 | RP-192027 | 0026 | | D | Rel-16 CR for further simplification of 38.101-2 Table 5.5A.2-2 | 16.1.0 | +| 2019-12 | RAN#86 | RP-193030 | 0032 | | A | CR to 38.101-2: DMRS exceptions | 16.2.0 | +| 2019-12 | RAN#86 | RP-193030 | 0036 | | A | Sync raster to SSB resource element mapping | 16.2.0 | +| 2019-12 | RAN#86 | RP-193030 | 0039 | | A | CR to 38.101-2 (Rel-16) to clarify measurement interval and observation window on frequency error | 16.2.0 | +| 2019-12 | RAN#86 | RP-193031 | 0041 | | A | CR to TS 38.101-2 on beam correspondence side condition applicability | 16.2.0 | +| 2019-12 | RAN#86 | RP-193031 | 0044 | | A | CR to TS 38.101-2: Correction on Interferer (offset) for CA ACS | 16.2.0 | +| 2019-12 | RAN#86 | RP-193030 | 0048 | | A | CR for TS 38.101-2: Editorial correction on MPR for contiguous CA notation | 16.2.0 | +| 2019-12 | RAN#86 | RP-193031 | 0050 | | A | CR for TS 38.101-2: CA bandwidth class definition amendment | 16.2.0 | +| 2019-12 | RAN#86 | RP-193030 | 0052 | | A | CR to TS 38.101-2 on corrections to channel raster entries for NR band (Rel-16) | 16.2.0 | +| 2019-12 | RAN#86 | RP-193030 | 0056 | | A | CR to transmit modulation quality in FR2 | 16.2.0 | +| 2019-12 | RAN#86 | RP-193030 | 0058 | | A | Frequency separation class clarification REL-16 | 16.2.0 | +| 2019-12 | RAN#86 | RP-193012 | 0064 | | B | CR introduction completed band combinations 38.716-01-01 -> 38.101-2 | 16.2.0 | +| 2019-12 | RAN#86 | RP-193011 | 0065 | 1 | F | CR to 38.101-2-g10 Corrections to maximum output power reduction for power class 3 | 16.2.0 | +| 2019-12 | RAN#86 | RP-193030 | 0067 | | A | CR for TS 38.101-2: power classes and maxUplinkDutyCycle-FR2 | 16.2.0 | +| 2019-12 | RAN#86 | RP-193031 | 0074 | | A | CR for agreed MPR CA for FR2 intra-band contiguous | 16.2.0 | +| 2019-12 | RAN#86 | RP-193031 | 0075 | 1 | A | CR for 38.101-2 on NS_202 band definition | 16.2.0 | +| 2019-12 | RAN#86 | RP-193031 | 0077 | | A | CR to TS 38.101-2: Correction on CA NRACLRL | 16.2.0 | +| 2020-03 | RAN#87 | RP-200395 | 0080 | | A | Correction of the FR2 RMC slot patterns for MOP test cases | 16.3.0 | +| 2020-03 | RAN#87 | RP-200395 | 0099 | | A | CR to 38.101-2 (Rel-16) MPR for CA | 16.3.0 | +| 2020-03 | RAN#87 | RP-200395 | 0106 | | F | CR FR2 CA tables REL16 | 16.3.0 | +| 2020-03 | RAN#87 | RP-200395 | 0108 | | A | CR to TS 38.101-2 on corrections to intra-band contiguous CA for FR2 bands (Rel-16) | 16.3.0 | +| 2020-03 | RAN#87 | RP-200395 | 0110 | | A | CR to 38.101-2: Align Rx CA requirements structure with TS38.101-1 | 16.3.0 | +| 2020-03 | RAN#87 | RP-200395 | 0114 | | A | CR for TS 38.101-2: Editorial addition of CBW and CABW definitions in Abbreviations section | 16.3.0 | +| 2020-03 | RAN#87 | RP-200395 | 0118 | | A | CR to TS 38.101-2: Correction on FRC table for FR2 DL 64QAM | 16.3.0 | +| 2020-03 | RAN#87 | RP-200469 | 0126 | 2 | A | CR for 38.101-2 side condition for BC_Rel16 | 16.3.0 | +| 2020-03 | RAN#87 | RP-200380 | 0132 | | F | Editorial corrections | 16.3.0 | +| 2020-03 | RAN#87 | RP-200378 | 0133 | | F | Correction of Inner Allocation Definition for Powerclass 3 | 16.3.0 | +| 2020-03 | RAN#87 | RP-200395 | 0136 | | A | R16 CR to 38.101-2: TRS and SSB configurations in FR2 | 16.3.0 | +| 2020-04 | | | 0147 | | A | Change history corrected | 16.3.1 | +| 2020-06 | RAN#88 | RP-200985 | 0148 | | F | CR on ACLR MBW definition in FR2 | 16.4.0 | +| 2020-06 | RAN#88 | RP-201046 | 0151 | | A | CR to 38.101-2: Revision to Multiband Relaxations | 16.4.0 | +| 2020-06 | RAN#88 | RP-200985 | 0164 | | A | CR to 38.101-2 on correction of reference point for beam correspondence side conditions R16 | 16.4.0 | +| 2020-06 | RAN#88 | RP-200985 | 0168 | | A | CR to 38.101-2 to correct Link and Meas Angles | 16.4.0 | +| 2020-06 | RAN#88 | RP-200985 | 0170 | | A | CR to 38.101-2: NS_202 update after changes to EU regulations | 16.4.0 | +| 2020-06 | RAN#88 | RP-200985 | 0172 | | A | CR for TS 38.101-2: Intra-band non-contiguous CA configuration clarifications | 16.4.0 | +| 2020-06 | RAN#88 | RP-200985 | 0174 | | A | CR for TS 38.101-2: Correction for configured transmitted power for CA | 16.4.0 | +| 2020-06 | RAN#88 | RP-200985 | 0175 | | F | CR for TS 38.101-2: Clarifications on transmitter power for receiver requirements | 16.4.0 | +| 2020-06 | RAN#88 | RP-200959 | 0181 | | A | CR for TS 38.101-2: Intra-band non-contiguous CA configuration clarifications | 16.4.0 | +| 2020-06 | RAN#88 | RP-200985 | 0183 | | A | Update of CSI-RS definition for FR2 DL RMCs | 16.4.0 | +| 2020-06 | RAN#88 | RP-200985 | 0184 | | F | Correction to FR2 QPSK UL RMC | 16.4.0 | +| 2020-06 | RAN#88 | RP-200985 | 0188 | | B | Correction of Rel-16 UL RMCs | 16.4.0 | +| 2020-06 | RAN#88 | RP-200972 | 0193 | | F | CR to TS 38.101-2: Introduction of FR2 DL 256QAM | 16.4.0 | +| 2020-06 | RAN#88 | RP-200985 | 0198 | | A | ACS requirement correction | 16.4.0 | +| 2020-06 | RAN#88 | RP-200985 | 0200 | | A | CR for intra-band CA DL Rx requirement-FR2_Rel-16 | 16.4.0 | +| 2020-06 | RAN#88 | RP-200985 | 0208 | | A | CR for modified MPR_Rel-16 | 16.4.0 | +| 2020-06 | RAN#88 | RP-200985 | 0162 | 1 | B | CR to TS38.101-2 on Rel-15 beam correspondence | 16.4.0 | +| 2020-06 | RAN#88 | RP-200959 | 0209 | | A | CR to 38.101-2: Introduce mmWave intra-band uplink CA configurations | 16.4.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|--------------------------------------------------------------------------------------------------------------------|--------| +| 2020-06 | RAN#88 | RP-200985 | 0161 | 1 | B | CR to K1 value in Annex A.3.3 of 38.101-2 | 16.4.0 | +| 2020-06 | RAN#88 | RP-201046 | 0211 | | A | CR to 38.101-2 on FR2 frequency separation class enhancement | 16.4.0 | +| 2020-06 | RAN#88 | RP-200985 | 0191 | 2 | B | CR on Pcmax correction for CA | 16.4.0 | +| 2020-06 | RAN#88 | RP-200978 | 0155 | 1 | B | CR to 38.101-2 for introduction of band n259 | 16.4.0 | +| 2020-06 | RAN#88 | RP-201046 | 0147 | | A | FR2 new MPR and modifiedmpr | 16.4.0 | +| 2020-09 | RAN#89 | RP-201496 | 0216 | 1 | B | Introduction of MPE related P-MPR operation in sub-clause 6.2.4 | 16.5.0 | +| 2020-09 | RAN#89 | RP-201512 | 0218 | | A | CR on Minimum output power and Off power MBW definition in FR2 | 16.5.0 | +| 2020-09 | RAN#89 | RP-201496 | 0221 | 1 | B | CR to 38.101-2 (Rel-16) intra-band non-cont. DL CA | 16.5.0 | +| 2020-09 | RAN#89 | RP-201512 | 0224 | | A | CR for R16 38.101-2: Correction of in-band emission tables | 16.5.0 | +| 2020-09 | RAN#89 | RP-201512 | 0226 | 1 | F | Correction for REL16 FR2 contiguous intra-band CA configuration table | 16.5.0 | +| 2020-09 | RAN#89 | RP-201512 | 0230 | 1 | F | modifiedMPR correction for FR2 REL16 | 16.5.0 | +| 2020-09 | RAN#89 | RP-201496 | 0231 | 2 | B | Beam correspondence enhancement | 16.5.0 | +| 2020-09 | RAN#89 | RP-201512 | 0234 | | A | CR to TS 38.101-2 on corrections to operating bands for intra-band CA (Rel-16) | 16.5.0 | +| 2020-09 | RAN#89 | RP-201506 | 0235 | | F | Correction of ACS requiremet for n259 | 16.5.0 | +| 2020-09 | RAN#89 | RP-201496 | 0237 | 2 | F | Introduction of FR2 inter-band DL CA | 16.5.0 | +| 2020-09 | RAN#89 | RP-201512 | 0239 | | A | CR for introduction of EESS protection for n257 into general spurious emission | 16.5.0 | +| 2020-09 | RAN#89 | RP-201512 | 0241 | | A | CR to TS 38.101-2: Correction on the Aggregated Channel Bandwidth | 16.5.0 | +| 2020-09 | RAN#89 | RP-201512 | 0243 | | A | CR to TS 38.101-2: Correction on the PC3 MPR description | 16.5.0 | +| 2020-09 | RAN#89 | RP-201512 | 0246 | | A | FR2 Minimum output power measurement period definition | 16.5.0 | +| 2020-09 | RAN#89 | RP-201488 | 0249 | 2 | F | CR to TS38.101-2 on ULFPTx and UE SRS port configuration clarification | 16.5.0 | +| 2020-09 | RAN#89 | RP-201496 | 0250 | 1 | F | CR to 38.101-2: DL CA BW Enhancement and CA REFSSENS | 16.5.0 | +| 2020-09 | RAN#89 | RP-201496 | 0251 | 1 | B | CR to 38.101-2: FR2 UE EIRP increase with IBE relaxation | 16.5.0 | +| 2020-09 | RAN#89 | RP-201496 | 0252 | 1 | B | FR2 intra-band non-contiguous UL CA feature | 16.5.0 | +| 2020-09 | RAN#89 | RP-201507 | 0259 | | F | Correction of corrupted table | 16.5.0 | +| 2020-12 | RAN#90 | RP-202485 | 0263 | | A | EESS protection related requirements for FR2 bands | 16.6.0 | +| 2020-12 | RAN#90 | RP-202485 | 0267 | | A | CR to 38.101-2: ULCA clarifications | 16.6.0 | +| 2020-12 | RAN#90 | RP-202485 | 0269 | | A | CR for TS38.101-2 Rel-16, Correction for definition of P-MPR | 16.6.0 | +| 2020-12 | RAN#90 | RP-202443 | 0270 | 1 | F | REL16 eBC capability alingment with 38.306 | 16.6.0 | +| 2020-12 | RAN#90 | RP-202443 | 0271 | 1 | F | CR to 38.101-2 (Rel-16) inter-band DL CA | 16.6.0 | +| 2020-12 | RAN#90 | RP-202443 | 0272 | 1 | F | Clarification of EIS spherical coverage for inter-band CA | 16.6.0 | +| 2020-12 | RAN#90 | RP-202485 | 0274 | | A | Transmission gap for relative power tolerance in FR2 | 16.6.0 | +| 2020-12 | RAN#90 | RP-202485 | 0276 | | A | CR to TS38.101-2 on DC location correction | 16.6.0 | +| 2020-12 | RAN#90 | RP-202485 | 0280 | | A | CR for TS 38.101-2: Clarification for NS_202 | 16.6.0 | +| 2020-12 | RAN#90 | RP-202509 | 0282 | 1 | F | CR to TS 38.101-2 on fallback group for intra-band contiguous CA (Rel-16) | 16.6.0 | +| 2020-12 | RAN#90 | RP-202509 | 0283 | 1 | F | CR to TS 38.101-2 on simplification for inter-band CA configuration | 16.6.0 | +| 2020-12 | RAN#90 | RP-202485 | 0289 | | A | Correction to Pcmax: total radiated power | 16.6.0 | +| 2020-12 | RAN#90 | RP-202485 | 0293 | | A | Correction to EIS definition | 16.6.0 | +| 2020-12 | RAN#90 | RP-202428 | 0297 | 1 | F | CR for editorial corrections 38.101-2 | 16.6.0 | +| 2020-12 | RAN#90 | RP-202485 | 0299 | | A | Mirror CR for 38.101-2: IBB and ACS corrections | 16.6.0 | +| 2020-12 | RAN#90 | RP-202485 | 0310 | | A | CR to DMRS position in UL RMC for FR2 | 16.6.0 | +| 2020-12 | RAN#90 | RP-202466 | 0287 | | B | CR introduction completed band combinations Rel-17 NR Intra-band - | 17.0.0 | +| 2021-03 | RAN#91 | RP-210117 | 0315 | | A | Removal of a remaining NS_201 related requirement | 17.1.0 | +| 2021-03 | RAN#91 | RP-210117 | 0319 | | A | CR to TS 38.101-2 on correction to intra-band non-contiguous CA configurations (Rel-17) | 17.1.0 | +| 2021-03 | RAN#91 | RP-210083 | 0324 | | A | P_cmax P_IBE wording refinement and terminology improvement | 17.1.0 | +| 2021-03 | RAN#91 | RP-210117 | 0334 | | A | CR to 38.101-2: correction on UL MIMO | 17.1.0 | +| 2021-03 | RAN#91 | RP-210117 | 0337 | | A | CR to 38.101-2 on beam correspondence | 17.1.0 | +| 2021-03 | RAN#91 | RP-210117 | 0346 | | A | CR on FR2 intra-band UL CA | 17.1.0 | +| 2021-03 | RAN#91 | RP-210737 | 0347 | | B | CR for FR2 FWA RF requirements | 17.1.0 | +| 2021-06 | RAN#92 | RP-211083 | 0353 | | A | P_cmax fix for the CA applicability | 17.2.0 | +| 2021-06 | RAN#92 | RP-211084 | 0359 | | A | Update of FR2 UL RMC tables | 17.2.0 | +| 2021-06 | RAN#92 | RP-211104 | 0364 | | A | Removal of CA_n260(*) notation and IE fix R17 CATA | 17.2.0 | +| 2021-06 | RAN#92 | RP-211117 | 0366 | | A | Correction of the channel raster of n259 for TS 38.101-2 | 17.2.0 | +| 2021-06 | RAN#92 | RP-211079 | 0370 | | F | CR to TS 38.101-2 on UE channel bandwidth per operating band | 17.2.0 | +| 2021-06 | RAN#92 | RP-211120 | 0371 | | B | Introduction of FR2 DL CA_n257+n259 and CA_n258-n260 | 17.2.0 | +| 2021-06 | RAN#92 | RP-211121 | 0372 | 1 | B | Introduction of n262 UE RF requirements | 17.2.0 | +| 2021-06 | RAN#92 | RP-211117 | 0378 | | A | CR to 38.101-2 on side conditions for beam correspondence based on SSB and CSI-RS for n259 (Rel-17) | 17.2.0 | +| 2021-06 | RAN#92 | RP-211080 | 0385 | 1 | F | CR Rel-17 38.101-2 to correct some errors in Table 5.5.A.2-2 | 17.2.0 | +| 2021-06 | RAN#92 | RP-211107 | 0387 | | A | CR to TS38.101-2: Some Corrections on for CA_n260-n261 | 17.2.0 | +| 2021-06 | RAN#92 | RP-211115 | 0388 | | B | CR to reflect the completed NR inter band CA DC combinations for 2 bands DL with up to 2 bands UL into TS 38.101-2 | 17.2.0 | +| 2021-06 | RAN#92 | RP-211115 | 0389 | | B | CR 38.101-2 new combinations Rel-17 NR Intra-band | 17.2.0 | +| 2021-06 | RAN#92 | RP-211114 | 0391 | | F | Rel-17 CR 38101-2-h10 corrections intra-band CA | 17.2.0 | +| 2021-06 | RAN#92 | RP-211102 | 0396 | 1 | A | CR on FR2 inter-band DL CA CBM and IBM_R17 CatA | 17.2.0 | + +| | | | | | | | | +|---------|----------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2021-06 | RAN#92 | RP-211091 | 0405 | | A | CR to 38.101-2: CABW definition addition | 17.2.0 | +| 2021-06 | RAN#92 | RP-211091 | 0408 | | A | CR for 38.101-2-h10: Removing ambiguity on MPRnarrow for PC3 MPR | 17.2.0 | +| 2021-06 | RAN#92 | RP-211120 | 0409 | | B | CR for TS 38.101-2: Introduction of FR2 new CA BW classes | 17.2.0 | +| 2021-09 | RAN#93 | RP-211921 | 0410 | | A | CR to 38.101-2 on handling of fallbacks for FR2 CA | 17.3.0 | +| 2021-09 | RAN#93 | RP-211900 | 0414 | | F | CR to TS 38.101-2 on corrections to intra-band non-contiguous CA | 17.3.0 | +| 2021-09 | RAN#93 | RP-211900 | 0418 | | B | CR 38.101-2 new combinations Rel-17 NR Intra-band | 17.3.0 | +| 2021-09 | RAN#93 | RP-211912 | 0419 | | F | Corrections of n262 UE RF requirements | 17.3.0 | +| 2021-09 | RAN#93 | RP-211923 | 0423 | | A | Big CR for TS 38.101-2 Maintenance part1 (Rel-17) | 17.3.0 | +| 2021-09 | RAN#93 | RP-211900 | 0424 | | F | Rel-17 CR 38.101-2, band combination corrections | 17.3.0 | +| 2021-09 | RAN#93 | RP-211902 | 0425 | | B | CR to 38.101-2: PC5 requirements in n259 | 17.3.0 | +| 2021-12 | RAN#94 | RP-212830 | 0427 | | B | Big CR to reflect the completed NR inter band CA DC combinations for 2 bands DL with up to 2 bands UL into TS 38.101-2 | 17.4.0 | +| 2021-12 | RAN#94 | RP-212830 | 0433 | | F | CR to TS 38.101-2 on configurations for inter-band CA | 17.4.0 | +| 2021-12 | RAN#94 | RP-212845 | 0436 | | F | Big CR for TS 38.101-2 Maintenance (Rel-17) | 17.4.0 | +| 2022-03 | RAN#95 | RP-220373 | 0441 | 1 | B | CR to introduce UE RF requirement for FR2 PC 6 UE | 17.5.0 | +| 2022-03 | RAN#95 | RP-220360 | 0442 | | B | CR on UE RF requirements for DMRS bundling in TS 38.101-2 | 17.5.0 | +| 2022-03 | RAN#95 | RP-220337 | 0445 | | A | Big CR for TS 38.101-2 Maintenance (Rel-17) | 17.5.0 | +| 2022-03 | RAN#95 | RP-220359 | 0446 | | F | Big CR to reflect the completed NR inter band CA DC combinations for 2 bands DL with up to 2 bands UL into TS 38.101-2 | 17.5.0 | +| 2022-03 | RAN#95 | RP-220360 | 0447 | | B | CR on measurement for DMRS bundling in TS 38.101-2 | 17.5.0 | +| 2022-03 | RAN#95 | RP-220360 | 0448 | | B | CR on measurement for DMRS bundling in TS 38.101-2
Note: The CR seems to be the same as CR as 0447 | 17.5.0 | +| 2022-03 | RAN#95 | RP-220371 | 0449 | | B | Big CR on RedCap UE FR2 | 17.5.0 | +| 2022-06 | RAN#96 | RP-221661 | 0450 | 1 | B | CR to 38.101-2 FR2+FR2 ULCA Feature | 17.6.0 | +| 2022-06 | RAN#96 | RP-221661 | 0451 | 1 | B | CR to 38.101-2: FR2+FR2 IBM DLCA for PC1/2/5 | 17.6.0 | +| 2022-06 | RAN#96 | RP-221654 | 0452 | 1 | F | CR 38101-2-h50 adding fallbacks | 17.6.0 | +| 2022-06 | RAN#96 | RP-221661 | 0455 | | A | CR for 38.101-2-h50: Correction for PC3 MPRnarrow | 17.6.0 | +| 2022-06 | RAN#96 | RP-221686 | 0457 | | B | Big CR to reflect the completed NR inter band CA DC combinations for 2 bands DL with up to 2 bands UL into TS 38.101-2 | 17.6.0 | +| 2022-06 | RAN#96 | RP-221695 | 0458 | 1 | B | Big CR to 38.101-2: update of simultaneous RxTx capability for band combinations | 17.6.0 | +| 2022-06 | RAN#96 | RP-221661 | 0459 | 1 | B | Addition of downlink CA_n258-n261 configuration | 17.6.0 | +| 2022-06 | RAN#96 | RP-221676 | 0460 | 1 | F | CR for 38.101-2 to correct the errors and add the missing requirements for FR2 RedCap UE | 17.6.0 | +| 2022-06 | RAN#96 | RP-221677 | 0461 | | F | CR on DMRS bundling phase offset Requirement FR2 | 17.6.0 | +| 2022-06 | RAN#96 | RP-221677 | 0462 | 1 | F | CR on DMRS bundling phase offset measurement FR2 | 17.6.0 | +| 2022-06 | RAN#96 | RP-221655 | 0468 | | A | Big CR for TS 38.101-2 Maintenance (Rel-17) | 17.6.0 | +| 2022-06 | RAN#96 | RP-221661 | 0469 | | F | Big CR on NR FR2 enhancement Rel-17 | 17.6.0 | +| 2022-06 | RAN#96 | RP-221676 | 0470 | | B | Big CR on extending NR to 71GHz for TS 38.101-2 | 17.6.0 | +| 2022-06 | RAN#96 | RP-221676 | 0471 | | F | CR on RedCap FR2 | 17.6.0 | +| 2022-09 | RAN#97 | RP-222032 | 0473 | | F | CR: Maintenance of phase continuity requirements for DMRS bundling in FR2 | 17.7.0 | +| 2022-09 | RAN#97 | RP-222036 | 0481 | | F | CR on PC2 UE RF requirements for FR2-1 inter-band UL CA | 17.7.0 | +| 2022-09 | RAN#97 | RP-222036 | 0482 | | F | CR on PC2 UE RF requirements for FR2-1 inter-band DL CA | 17.7.0 | +| 2022-09 | RAN#97 | RP-222028 | 0484 | | F | CR 38.101-2: Rel-17 Adding missing fallback combinations | 17.7.0 | +| 2022-09 | RAN#97 | RP-222036 | 0486 | 1 | F | Amendment of the requirement on TX power management | 17.7.0 | +| 2022-09 | RAN#97 | RP-222023 | 0489 | | A | CR to 38.101-2 Corrections to tables with wrong unit declarations | 17.7.0 | +| 2022-09 | RAN#97 | RP-222036 | 0493 | | F | Correction CR on UL Gap | 17.7.0 | +| 2022-09 | RAN#97 | RP-222026 | 0496 | | F | Big CR for 38.101-2 maintenance (Rel-17) | 17.7.0 | +| 2022-09 | RAN#97 | RP-222036 | 0497 | | F | R17 FR2 CR on separate REFSSENS tables for different power classes | 17.7.0 | +| 2022-09 | RAN#97 | RP-222557 | 0498 | 1 | B | Big CR of TS38.101-2 for FR2-2 UE requirements | 17.7.0 | +| 2022-12 | RAN#98-e | RP-223307 | 0500 | 1 | F | definition on RedCap | 17.8.0 | +| 2022-12 | RAN#98-e | RP-223306 | 0502 | 2 | F | CR to 38.101-2 to clarify P-MPR behavior when DMRS bundling is configured | 17.8.0 | +| 2022-12 | RAN#98-e | RP-223308 | 0505 | 2 | F | CR to TS38.101-2 PC3 TIB values for FR2 inter-band UL CA | 17.8.0 | +| 2022-12 | RAN#98-e | RP-223296 | 0506 | 1 | F | CR R17 ModifiedMPR | 17.8.0 | +| 2022-12 | RAN#98-e | RP-223290 | 0510 | | A | Annex G Clarifications on diagram related to measurement point for difference of relative phase/power error for UL coherent MIMO (Rel-17) | 17.8.0 | +| 2022-12 | RAN#98-e | RP-223308 | 0516 | | F | CR on ACS/IBB of FR2 inter-band CA | 17.8.0 | +| 2022-12 | RAN#98-e | RP-223290 | 0521 | | A | CR for Rel-17 38.101-2 to correct the side condition for CSI-RS based | 17.8.0 | +| 2022-12 | RAN#98-e | RP-223296 | 0524 | | A | CR to 38.101-2 on removing ambiguity in CA MPR definition | 17.8.0 | +| 2022-12 | RAN#98-e | RP-223308 | 0525 | 3 | F | R17 CR on introduction of FR2 CA DC location reporting | 17.8.0 | +| 2022-12 | RAN#98-e | RP-223291 | 0528 | | F | Correction to DL RMC (Rel-17) | 17.8.0 | +| 2022-12 | RAN#98-e | RP-223309 | 0529 | 2 | F | Adding DL RMC for band n263 | 17.8.0 | + +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +|---------|----------|-----------|------|-----|-----|------------------------------------------------------------------------------------------------------------------------|-------------| +| 2022-12 | RAN#98-e | RP-223324 | 0518 | | B | big CR 38.101-2 new combinations Rel-18 NR Intra-band | 18.0.0 | +| 2022-12 | RAN#98-e | RP-223325 | 0522 | | B | Big CR to reflect the completed NR inter band CA DC combinations for 2 bands DL with up to 2 bands UL into TS 38.101-2 | 18.0.0 | +| 2023-03 | RAN#99 | RP-230519 | 0532 | | A | CR on updating the name of UE capability for UL gap | 18.1.0 | +| 2023-03 | RAN#99 | RP-230543 | 0533 | 1 | F | CR 38.101-2: Rel-18 Band combinations bug fixing | 18.1.0 | +| 2023-03 | RAN#99 | RP-230514 | 0535 | | A | CR for TS 38.101-2: FR2-2 power class content | 18.1.0 | +| 2023-03 | RAN#99 | RP-230501 | 0539 | | A | Addition of FR2 UL MIMO EVM measurement description | 18.1.0 | +| 2023-03 | RAN#99 | RP-230502 | 0553 | | A | CR to F_offset and F_Interferer (offset) adjustment in ACS and IBB | 18.1.0 | +| 2023-03 | RAN#99 | RP-230502 | 0557 | | A | CR on 'Annex G Difference of relative phase and power errors' for FR2 UL coherent MIMO | 18.1.0 | +| 2023-03 | RAN#99 | RP-230502 | 0565 | | A | On handheld UE and FWA UE definitions | 18.1.0 | +| 2023-03 | RAN#99 | RP-230514 | 0567 | | A | Apply NOTE1 for n263 intra-band CA | 18.1.0 | +| 2023-03 | RAN#99 | RP-230544 | 0568 | | B | Big CR to reflect the completed NR inter band CA DC combinations for 2 bands DL with up to 2 bands UL into TS 38.101-2 | 18.1.0 | +| 2023-03 | RAN#99 | RP-230503 | 0582 | | A | CR for Rel-18 38.101-2 to correct the UL configuration for CA n258C | 18.1.0 | +| 2023-03 | RAN#99 | RP-230503 | 0591 | | A | CR to TS 38.101-2 on humidity condition for normal temperature | 18.1.0 | +| 2023-06 | RAN#100 | RP-231347 | 0598 | | A | Maintenance CR to RF requirements for n263 (Rel-18) | 18.2.0 | +| 2023-06 | RAN#100 | RP-231355 | 0603 | | A | CR for TS 38.101-2 on corrections to the minimum guardband calculation (R18_CAT_A) | 18.2.0 | +| 2023-06 | RAN#100 | RP-231374 | 0604 | | B | CR to reflect the completed NR inter band CA DC combinations for 2 bands DL with up to 2 bands UL into TS 38.101-2 | 18.2.0 | +| 2023-06 | RAN#100 | RP-231356 | 0613 | | A | Update of FR2 UL MIMO EVM measurement description | 18.2.0 | +| 2023-06 | RAN#100 | RP-231343 | 0617 | | A | CR to clarify DC location wording | 18.2.0 | +| 2023-06 | RAN#100 | RP-231373 | 0618 | | B | big CR 38.101-2 new combinations Rel-18 NR Intra-band | 18.2.0 | +| 2023-09 | RAN#101 | RP-232520 | 0621 | | B | big CR 38.101-2 new combinations Rel-18 NR Intra-band | 18.3.0 | +| 2023-09 | RAN#101 | RP-232505 | 0623 | | A | CR to TS 38.101-2 on correction of maximum input level (Rel-18) | 18.3.0 | +| 2023-09 | RAN#101 | RP-232490 | 0629 | | A | [NR_ext_to_71GHz-Core] CR to TS38.101-2: Adding FR2-2 MPR table numbers to parameters definition | 18.3.0 | +| 2023-09 | RAN#101 | RP-232490 | 0640 | | A | [NR_ext_to_71GHz-Core] Editorial modification CR for TS 38.101-2 | 18.3.0 | +| 2023-09 | RAN#101 | RP-232515 | 0641 | | B | CR for power class 6 intra-band CA requirements | 18.3.0 | +| 2023-09 | RAN#101 | RP-232501 | 0646 | | A | [NR_newRAT-Core] Correction of AMPR requirement for CA | 18.3.0 | +| 2023-09 | RAN#101 | RP-232488 | 0648 | | A | [NR_cov_enh-Core] Update of FR2 DMRS bundling measurements | 18.3.0 | +| 2023-09 | RAN#101 | RP-232515 | 0649 | 1 | B | Feature CR for RF requirements of FR2 HST multi-panel operation | 18.3.0 | +| 2023-09 | RAN#101 | RP-232501 | 0653 | | A | [NR_newRAT-Core] CR on editorial correction for UE orientation illustrations | 18.3.0 | +| 2023-09 | RAN#101 | RP-232487 | 0658 | | A | CR for clarification on maxUplinkDutyCycle-FR2 | 18.3.0 | +| 2023-12 | RAN#102 | RP-233331 | 0663 | | A | Fc terminology update | 18.4.0 | +| 2023-12 | RAN#102 | RP-233363 | 0665 | 1 | B | Feature CR for FR2 multi-Rx | 18.4.0 | +| 2023-12 | RAN#102 | RP-233363 | 0666 | 1 | B | CR for Rel-18 38.101-2 to introduce FR2-1 UL 256 QAM RF requirements | 18.4.0 | +| 2023-12 | RAN#102 | RP-233331 | 0670 | | A | CR for Rel-18 38.101-2 to correct some errors in the clause of the spectrum emission mask for CA. | 18.4.0 | +| 2023-12 | RAN#102 | RP-233331 | 0674 | | A | CR for Rel-18 38.101-2 to introduce the missed sub-clause 6.5A.2.2 as void | 18.4.0 | +| 2023-12 | RAN#102 | RP-233332 | 0678 | | A | CR to 38.101-2 on adding missing definition of EIS spherical coverage link angle(Rel-18) | 18.4.0 | +| 2023-12 | RAN#102 | RP-233351 | 0683 | | A | [NR_RF_FR2_req_enh] Removal of interlaced channel bandwidths for CA BW class fallback groups 1-4 | 18.4.0 | +| 2023-12 | RAN#102 | RP-233361 | 0684 | 1 | B | CR to introduce configured transmitted power for STxMP | 18.4.0 | +| 2023-12 | RAN#102 | RP-233368 | 0686 | | B | CR for 38.101-2 to add new configurations for the existing NR intra-band CA configurations | 18.4.0 | +| 2023-12 | RAN#102 | RP-233368 | 0687 | | B | big CR for addition of NR CA Intra-band FR2 | 18.4.0 | +| 2023-12 | RAN#102 | RP-233363 | 0689 | 2 | B | Introducing beam correspondence requirement for initial access and RRC_INACTIVE | 18.4.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38101-5/1b5a812c8aa20fd5cba28e97001d32de_img.jpg b/marked/Rel-18/38_series/38101-5/1b5a812c8aa20fd5cba28e97001d32de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..afd4cff3c5baf2f8ddb7eaf1e86003fcb90b402d --- /dev/null +++ b/marked/Rel-18/38_series/38101-5/1b5a812c8aa20fd5cba28e97001d32de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b99e1b555422ea8df37606ff0aa2070f87908097360a290a8d7fd1db38f02502 +size 29540 diff --git a/marked/Rel-18/38_series/38101-5/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38101-5/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..39d7c5b002f0a5c9865e965cdd9fe8ea3d85db35 --- /dev/null +++ b/marked/Rel-18/38_series/38101-5/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd6abe6e0aa45ffbb28ee2931f577978bbb53e32bf459ac51984427b89cde22d +size 9431 diff --git a/marked/Rel-18/38_series/38101-5/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38101-5/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28f15b81a0b2e0fc6ceb0e7421366fd348f03c16 --- /dev/null +++ b/marked/Rel-18/38_series/38101-5/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f28fbee5c8b9d467c0d09577d617a6ece55ea68ec237f86aded7e82e7a9decd6 +size 5698 diff --git a/marked/Rel-18/38_series/38101-5/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-18/38_series/38101-5/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b775536054edfb97574ee6d3525a3af445628a9e --- /dev/null +++ b/marked/Rel-18/38_series/38101-5/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:25c94ed3f06a9611436b20a8fcda3e0eb477ce6d6759717fec21d2f68752621a +size 31841 diff --git a/marked/Rel-18/38_series/38101-5/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-18/38_series/38101-5/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d085af604a647c4c2e198d5d074410d9bd35c793 --- /dev/null +++ b/marked/Rel-18/38_series/38101-5/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0bcfc79238910ef7335801a06d1950e683aef5f213b35ff22cbf2380e9b1a79b +size 62516 diff --git a/marked/Rel-18/38_series/38101-5/raw.md b/marked/Rel-18/38_series/38101-5/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e79e998b93f9ea0c3ae48598237d3c63896628e9 --- /dev/null +++ b/marked/Rel-18/38_series/38101-5/raw.md @@ -0,0 +1,2097 @@ + + +# 3GPP TS 38.101-5 V18.4.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; User Equipment (UE) radio transmission and reception; Part 5: Satellite access Radio Frequency (RF) and performance requirements (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +# **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +# --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|---------------------------------------------------------------------------------------|----| +| Foreword ..... | 9 | +| 1 Scope..... | 11 | +| 2 References..... | 11 | +| 3 Definitions of terms, symbols and abbreviations..... | 11 | +| 3.1 Terms..... | 11 | +| 3.2 Symbols..... | 12 | +| 3.3 Abbreviations ..... | 12 | +| 4 General..... | 14 | +| 4.1 Relationship between minimum requirements and test requirements..... | 14 | +| 4.2 Applicability of minimum requirements ..... | 14 | +| 4.3 Specification suffix information..... | 14 | +| 4.4 Relationship with other core specifications ..... | 14 | +| 5 Operating bands and channel arrangement..... | 14 | +| 5.1 General ..... | 14 | +| 5.2 Operating bands..... | 15 | +| 5.2.1 General ..... | 15 | +| 5.2.2 Operating bands with conducted requirements ..... | 15 | +| 5.2.3 reserved (for radiated requirements)..... | 15 | +| 5.3 UE channel bandwidth ..... | 15 | +| 5.3.1 General ..... | 15 | +| 5.3.2 Maximum transmission bandwidth configuration..... | 16 | +| 5.3.3 Minimum guardband and transmission bandwidth configuration..... | 16 | +| 5.3.4 RB alignment..... | 17 | +| 5.3.5 UE channel bandwidth per operating band..... | 17 | +| 5.3.6 Asymmetric channel bandwidths ..... | 18 | +| 5.4 Channel arrangement..... | 18 | +| 5.4.1 Channel spacing..... | 18 | +| 5.4.1.1 Channel spacing for adjacent NTN satellite carriers ..... | 18 | +| 5.4.2 Channel raster..... | 18 | +| 5.4.2.1 NR-ARFCN and channel raster ..... | 18 | +| 5.4.2.2 Channel raster to resource element mapping..... | 19 | +| 5.4.2.3 Channel raster entries for each operating band..... | 19 | +| 5.4.3 Synchronization raster ..... | 20 | +| 5.4.3.1 Synchronization raster and numbering ..... | 20 | +| 5.4.3.2 Synchronization raster to synchronization block resource element mapping..... | 20 | +| 5.4.3.3 Synchronization raster entries for each operating band..... | 20 | +| 5.4.4 TX-RX frequency separation..... | 21 | +| 6 Conducted transmitter characteristics ..... | 21 | +| 6.1 General ..... | 21 | +| 6.2 Transmitter power ..... | 21 | +| 6.2.1 UE maximum output power ..... | 21 | +| 6.2.2 UE maximum output power reduction ..... | 22 | +| 6.2.3 UE additional maximum output power reduction ..... | 22 | +| 6.2.3.1 General..... | 22 | +| 6.2.3.2 A-MPR for NS_03N ..... | 23 | +| 6.2.3.3 A-MPR for NS_04N ..... | 23 | +| 6.2.3.4 A-MPR for NS_05N ..... | 24 | +| 6.2.4 Configured transmitted power..... | 24 | +| 6.3 Output power dynamics..... | 24 | +| 6.3.1 Minimum output power..... | 24 | +| 6.3.2 Transmit OFF power ..... | 25 | +| 6.3.3 Transmit ON/OFF time mask..... | 25 | +| 6.3.4 Power control..... | 25 | + +| | | | +|---------------|----------------------------------------------------------------------|----| +| 6.4 | Transmit signal quality..... | 25 | +| 6.4.1 | Frequency error ..... | 25 | +| 6.4.2 | Transmit modulation quality ..... | 26 | +| 6.5 | Output RF spectrum emissions ..... | 26 | +| 6.5.1 | Occupied bandwidth..... | 26 | +| 6.5.2 | Out of band emission..... | 26 | +| 6.5.2.1 | General..... | 26 | +| 6.5.2.2 | Spectrum emission mask ..... | 26 | +| 6.5.2.3 | Additional spectrum emission mask..... | 27 | +| 6.5.2.3.1 | Requirements for network signalling value "NS_04N" ..... | 27 | +| 6.5.2.3.2 | Requirements for network signalling value "NS_05N" ..... | 27 | +| 6.5.2.4 | Adjacent channel leakage ratio ..... | 27 | +| 6.5.2.4.1 | NR ACLR..... | 27 | +| 6.5.2.4.2 | UTRA ACLR ..... | 28 | +| 6.5.3 | Spurious emission..... | 28 | +| 6.5.3.1 | General spurious emissions ..... | 28 | +| 6.5.3.2 | Spurious emissions for UE co-existence ..... | 29 | +| 6.5.3.3 | Additional spurious emissions ..... | 30 | +| 6.5.3.3.1 | General ..... | 30 | +| 6.5.3.3.2 | Requirement for network signalling value "NS_02N"..... | 30 | +| 6.5.3.3.3 | Requirement for network signalling value "NS_03N"..... | 30 | +| 6.5.3.3.4 | Requirement for network signalling value "NS_04N" and "NS_05N"..... | 31 | +| 6.5.4 | Transmit intermodulation ..... | 31 | +| 7 | Conducted receiver characteristics..... | 32 | +| 7.1 | General ..... | 32 | +| 7.2 | Diversity characteristics ..... | 32 | +| 7.3 | Reference sensitivity ..... | 32 | +| 7.3.1 | General ..... | 32 | +| 7.3.2 | Reference sensitivity power level..... | 33 | +| 7.4 | Maximum input level..... | 33 | +| 7.5 | Adjacent channel selectivity..... | 34 | +| 7.6 | Blocking characteristics ..... | 35 | +| 7.6.1 | General ..... | 35 | +| 7.6.2 | In-band blocking..... | 35 | +| 7.6.3 | Out-of-band blocking ..... | 36 | +| 7.6.4 | Narrow band blocking ..... | 37 | +| 7.7 | Spurious response..... | 38 | +| 7.8 | Intermodulation characteristics ..... | 38 | +| 7.9 | Spurious emissions..... | 38 | +| 8 | Conducted performance requirements ..... | 39 | +| 8.1 | General ..... | 39 | +| 8.1.1 | Relationship between minimum requirements and test requirements..... | 39 | +| 8.1.2 | Applicability of minimum requirements ..... | 39 | +| 8.1.3 | Conducted requirements..... | 39 | +| 8.1.3.1 | Introduction..... | 39 | +| 8.1.3.2 | Reference point ..... | 39 | +| 8.1.3.3 | SNR definition ..... | 39 | +| 8.1.3.4 | Noc..... | 40 | +| 8.1.3.4.1 | Introduction ..... | 40 | +| 8.1.3.4.2 | Noc for NR operating bands in FR1..... | 40 | +| 8.2 | Demodulation performance requirements..... | 41 | +| 8.2.1 | General ..... | 41 | +| 8.2.1.1 | Applicability of requirements ..... | 41 | +| 8.2.1.1.1 | General ..... | 41 | +| 8.2.1.1.2 | Applicability of requirements for optional UE features..... | 41 | +| 8.2.1.2 | PDSCH demodulation requirements..... | 41 | +| 8.2.1.2.1 | 1RX requirements ..... | 44 | +| 8.2.1.2.2 | 2RX requirements ..... | 44 | +| 8.2.1.2.2.1.1 | Minimum requirements for PDSCH Mapping Type A ..... | 44 | +| 8.3 | CSI reporting requirements ..... | 46 | + +| | | +|------------------------------------------------------------------------------|-----------| +| Annex A (normative): Measurement channels..... | 47 | +| A.1 General..... | 47 | +| A.1.1 Throughput definition ..... | 47 | +| A.2 UL reference measurement channels ..... | 47 | +| A.3 DL reference measurement channels ..... | 47 | +| A.3.1 General ..... | 47 | +| A.3.2 Reference measurement channels for PDSCH performance requirements..... | 47 | +| A.3.2.1 FDD ..... | 48 | +| A.3.2.1.1 Reference measurement channels for SCS 15 kHz FR1 ..... | 48 | +| A.4 Testing related to Satellite Access ..... | 50 | +| A.4.1 General ..... | 50 | +| A.4.2 Test condition for transmitter characteristics..... | 50 | +| A.4.3 Test condition for receiver characteristics ..... | 50 | +| A.4.4 Test condition for performance requirements ..... | 50 | +| Annex B (normative): Propagation conditions..... | 51 | +| B.1 Static propagation condition ..... | 51 | +| B.1.1 UE Receiver with 1Rx..... | 51 | +| B.1.2 UE Receiver with 2Rx..... | 51 | +| B.2.1 Delay profiles ..... | 51 | +| B.2.2 Combinations of channel model parameters ..... | 52 | +| B.2.3 MIMO Channel Correlation Matrices..... | 52 | +| B.2.3.1 MIMO Correlation Matrices using Uniform Linear Array (ULA)..... | 52 | +| B.2.3.1.1 Definition of MIMO Correlation Matrices ..... | 52 | +| B.2.3.1.2 MIMO Correlation Matrices at High, Medium and Low Level ..... | 53 | +| Annex C (normative): Downlink physical channels..... | 54 | +| C.1 General..... | 54 | +| C.2 Setup (Conducted)..... | 54 | +| C.3 Connection (Conducted) ..... | 54 | +| C.3.1 Measurement of Performance requirements ..... | 54 | +| Annex D (informative): Void..... | 55 | +| Annex E (normative): Environmental conditions ..... | 55 | +| E.1 General..... | 55 | +| E.2 Environmental (Conducted)..... | 55 | +| E.2.1 Temperature ..... | 55 | +| E.2.2 Voltage ..... | 56 | +| E.2.3 Vibration..... | 56 | +| Annex F (informative): Change history ..... | 57 | + +# 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 and performance requirements for NR User Equipment (UE) supporting satellite access operation. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 38.521-5: "NR; User Equipment (UE) conformance specification; Radio transmission and reception; Part 5: Satellite access Radio Frequency (RF) and performance requirements ". +- [3] Recommendation ITU-R M.1545: "Measurement uncertainty as it applies to test limits for the terrestrial component of International Mobile Telecommunications-2000". +- [4] 3GPP TS 38.108: "NR; Satellite Node radio transmission and reception" +- [5] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone". +- [6] 3GPP TS 38.101-4: "NR; User Equipment (UE) radio transmission and reception; Part 4: Performance requirements". +- [7] 3GPP TS 38.213: "NR; Physical layer procedures for control" +- [8] 3GPP TS 38.331: " Radio Resource Control (RRC) protocol specification". +- [9] 3GPP TS 38.300: "NR; NR and NG-RAN Overall description; Stage-2". +- [10] 3GPP TS 36.101: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception". +- [11] 3GPP TS 38.306: "User Equipment (UE) radio access capabilities". +- [12] 3GPP TR 38.811: "Study on New Radio (NR) to support non-terrestrial networks". +- [13] 3GPP TS 38.508-1: "5GS; User Equipment (UE) conformance specification; Part 1: Common test environment". + +# 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]. + +**Enhanced channel raster:** channel raster with a 10 kHz granularity in bands with a 100 kHz channel raster. + +**Geostationary satellite:** A geosynchronous satellite whose circular and direct orbit lies in the plane of the Earth's equator and which thus remains fixed relative to the Earth; by extension, a geosynchronous satellite which remains approximately fixed relative to the Earth. + +**Geostationary-Satellite Orbit:** The orbit of a geosynchronous satellite whose circular and direct orbit lies in the plane of the Earth's equator. + +**Geosynchronous Earth Orbit:** Earth-centered orbit at approximately 35786 kilometres above Earth's surface and synchronised with Earth's rotation. A geostationary orbit is a non-inclined geosynchronous orbit, i.e. in the Earth's equator plane. + +**Geosynchronous satellite:** An earth satellite whose period of revolution is equal to the period of rotation of the Earth about its axis. + +**Low Earth Orbit:** Orbit around the Earth with an altitude between 300 km, and 1500 km. + +**Non-terrestrial networks:** Networks, or segments of networks, using an airborne or space-borne vehicle to embark a transmission equipment relay node or base station. + +**Satellite:** A space-borne vehicle embarking a bent pipe payload or a regenerative payload telecommunication transmitter, placed into Low-Earth Orbit (LEO), Medium-Earth Orbit (MEO), or Geostationary Earth Orbit (GEO). + +**Satellite Access Node:** see definition in TS 38.108[4]. + +**UE transmission bandwidth configuration:** Set of resource blocks located within the UE channel bandwidth which may be used for transmitting or receiving by the UE. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------| +| $\Delta F_{\text{Global}}$ | Granularity of the global frequency raster | +| $\Delta F_{\text{Raster}}$ | Band dependent channel raster granularity | +| $BW_{\text{Channel}}$ | Channel bandwidth | +| $BW_{\text{interferer}}$ | Bandwidth of the interferer | +| $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 | +| $F_{\text{Interferer}}$ | Frequency of the interferer | +| $F_{\text{Interferer}}(\text{offset})$ | Frequency offset of the interferer (between the center frequency of the interferer and the carrier frequency of the carrier measured) | +| $F_{\text{Ioffset}}$ | Frequency offset of the interferer (between the center frequency of the interferer and the closest edge of the carrier measured) | +| $F_{\text{OOB}}$ | The boundary between the NR out of band emission and spurious emission domains | +| $F_{\text{REF}}$ | RF reference frequency | +| $F_{\text{REF-Offs}}$ | Offset used for calculating $F_{\text{REF}}$ | +| $F_{\text{uw}}(\text{offset})$ | The frequency separation of the center frequency of the carrier closest to the interferer and the center frequency of the interferer | +| $N_{\text{RB}}$ | Transmission bandwidth configuration, expressed in units of resource blocks | +| $N_{\text{REF}}$ | NR Absolute Radio Frequency Channel Number (NR-ARFCN) | +| $N_{\text{REF-Offs}}$ | Offset used for calculating $N_{\text{REF}}$ | +| $P_{\text{Interferer}}$ | Modulated mean power of the interferer | +| $P_{\text{uw}}$ | Power of an unwanted DL signal | + +## 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 | +| A-MPR | Additional Maximum Power Reduction | +| BW | Bandwidth | +| BWP | Bandwidth Part | +| CP-OFDM | Cyclic Prefix-OFDM | +| CW | Continuous Wave | +| DFT-s-OFDM | Discrete Fourier Transform-spread-OFDM | +| DM-RS | Demodulation Reference Signal | +| DTX | Discontinuous Transmission | +| EIRP | Equivalent Isotropically Radiated Power | +| EVM | Error Vector Magnitude | +| FR | Frequency Range | +| FRC | Fixed Reference Channel | +| GEO | Geosynchronous Earth Orbit | +| GSCN | Global Synchronization Channel Number | +| GSO | Geostationary-Satellite Orbit | +| IBB | In-band Blocking | +| ITU-R | Radiocommunication Sector of the International Telecommunication Union | +| LEO | Low Earth Orbiting | +| MBW | Measurement bandwidth defined for the protected band | +| MEO | Medium Earth Orbiting | +| MOP | Maximum Output Power | +| MPR | Allowed maximum power reduction | +| MSD | Maximum Sensitivity Degradation | +| NGEO | Non-Geostationary Earth Orbiting | +| NGSO | Non-Geostationary-Satellite Orbit | +| NR | New Radio | +| NR-ARFCN | NR Absolute Radio Frequency Channel Number | +| NS | Network Signalling | +| NTN | Non-Terrestrial Network | +| OCNG | OFDMA Channel Noise Generator | +| OOB | Out-of-band | +| PRB | Physical Resource Block | +| QAM | Quadrature Amplitude Modulation | +| RAN | Radio Access Network | +| RE | Resource Element | +| REFSENS | REference SENSitivity | +| RF | Radio Frequency | +| RMS | Root Mean Square (value) | +| RSRP | Reference Signal Receive Power | +| RSRQ | Reference Signal Receive Quality | +| RX | Receiver | +| SAN | Satellite Access Node | +| SC | Single Carrier | +| SCS | Subcarrier spacing | +| SEM | Spectrum Emission Mask | +| SNR | Signal-to-Noise Ratio | +| SRS | Sounding Reference Symbol | +| SS | Synchronization Symbol | +| TN | Terrestrial Network | +| TX | Transmitter | +| TxD | Tx Diversity | +| UE | User Equipment | + +# --- 4 General + +## 4.1 Relationship between minimum requirements and test requirements + +The present document is a Single-RAT specification for satellite NR UE, covering RF characteristics and minimum performance requirements. Conformance to the present specification is demonstrated by fulfilling the test requirements specified in the conformance specification 3GPP TS 38.521-5 [2]. + +The Minimum Requirements given in this specification make no allowance for measurement uncertainty. The test specification 3GPP TS 38.521-5 [2] defines test tolerances. These test tolerances are individually calculated for each test. The test tolerances are used to relax the minimum requirements in this specification to create test requirements. 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 [3]. + +## 4.2 Applicability of minimum requirements + +- a) In this specification the Minimum Requirements are specified as general requirements and additional requirements. Where the Requirement is specified as a general requirement, the requirement is mandated to be met in all scenarios +- b) For specific scenarios for which an additional requirement is specified, in addition to meeting the general requirement, the UE is mandated to meet the additional requirements. +- c) The spurious emissions power requirements are for the long-term average of the power. For the purpose of reducing measurement uncertainty, it is acceptable to average the measured power over a period of time sufficient to reduce the uncertainty due to the statistical nature of the signal. + +## 4.3 Specification suffix information + +Specification suffix information is not defined for the time being in Release 17. + +## 4.4 Relationship with other core specifications + +The present document establishes the minimum RF and performance requirements for NR User Equipment (UE) operating in a Non-Terrestrial Network. The present document for the single-RAT specification of a satellite NR UE side is used together with the technical specification 3GPP TS 38.108 [4] specifying the Satellite Access Node (SAN). + +# --- 5 Operating bands and channel arrangement + +## 5.1 General + +The channel arrangements presented in this clause are based on the operating bands and channel bandwidths defined in the present Release of specifications. + +NOTE: Other operating bands and 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 NTN satellite can operate according to this 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 | + +The present specification covers FR1 operating bands. + +## 5.2 Operating bands + +### 5.2.1 General + +NTN satellite covers FR1 operating bands in the present specification. + +### 5.2.2 Operating bands with conducted requirements + +NTN satellite is designed to operate in the operating bands defined in Table 5.2.2-1. + +**Table 5.2.2-1: NTN satellite bands in FR1** + +| NTN satellite operating band | Uplink (UL) operating band
Satellite Access Node receive / UE transmit
$F_{UL,low} - F_{UL,high}$ | Downlink (DL) operating band
Satellite Access Node 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 – 1626.5 MHz | 2483.5 – 2500 MHz | FDD | + +NOTE: NTN satellite bands are numbered in descending order from n256. + +### 5.2.3 reserved (for radiated requirements) + +[To be updated] + +## 5.3 UE channel bandwidth + +### 5.3.1 General + +The UE channel bandwidth supports a single RF carrier in the uplink or downlink at the UE. From a SAN perspective, different UE channel bandwidths may be supported within the same spectrum for transmitting to and receiving from UEs connected to the SAN. + +From a UE perspective, the UE is configured with one or more BWP / carriers, each with its own UE channel bandwidth. The UE does not need to be aware of the SAN channel bandwidth or how the SAN allocates bandwidth to different UEs. + +The placement of the UE channel bandwidth for each UE carrier is flexible but can only be completely within the SAN channel bandwidth. + +The relationship between the channel bandwidth, the guardband and the maximum transmission bandwidth configuration is shown in Figure 5.3.1-1. + +![Figure 5.3.1-1: Definition of the channel bandwidth and the maximum transmission bandwidth configuration for one channel. The diagram shows a horizontal axis representing frequency. Two vertical dashed lines mark the 'Channel Edge'. A double-headed arrow between these edges is labeled 'Channel Bandwidth [MHz]'. Inside, a solid line marks 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 rectangles represent 'Resource Block's. A group of these rectangles is highlighted in blue and labeled 'Active Resource Blocks'. The gap between the 'Transmission Bandwidth Configuration' and the 'Channel Edge' is labeled 'Guardband, can be asymmetric'.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +Figure 5.3.1-1: Definition of the channel bandwidth and the maximum transmission bandwidth configuration for one channel. The diagram shows a horizontal axis representing frequency. Two vertical dashed lines mark the 'Channel Edge'. A double-headed arrow between these edges is labeled 'Channel Bandwidth [MHz]'. Inside, a solid line marks 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 rectangles represent 'Resource Block's. A group of these rectangles is highlighted in blue and labeled 'Active Resource Blocks'. The gap between the 'Transmission Bandwidth Configuration' and the 'Channel Edge' is labeled 'Guardband, can be asymmetric'. + +**Figure 5.3.1-1: Definition of the channel bandwidth and the maximum transmission bandwidth configuration for one channel** + +### 5.3.2 Maximum transmission bandwidth configuration + +The maximum transmission bandwidth configuration $N_{RB}$ for each UE channel bandwidth and subcarrier spacing is specified in Table 5.3.2-1. + +**Table 5.3.2-1: Maximum transmission bandwidth configuration $N_{RB}$** + +| 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 | + +### 5.3.3 Minimum guardband and transmission bandwidth configuration + +The minimum guardband for each UE channel bandwidth and SCS is specified in Table 5.3.3-1, + +**Table 5.3.3-1: Minimum guardband for each UE channel bandwidth and SCS (kHz)** + +| 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 | + +NOTE: The minimum guardbands have been calculated using the following equation: $(BW_{Channel} \times 1000 \text{ (kHz)} - N_{RB} \times SCS \times 12) / 2 - SCS/2$ , where $N_{RB}$ are from Table 5.3.2-1. + +**Figure 5.3.3-1: Void** + +The number of RBs configured in any channel bandwidth shall ensure that the minimum guardband specified in this clause is met. + +![Figure 5.3.3-2: UE PRB utilization diagram](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +The diagram illustrates the frequency axis (f) and the UE channel bandwidth (UE channel BW). A central carrier is shown with a minimum guardband on each side. The UE channel BW is indicated by a double-headed arrow. A dashed line points to the guardband area, labeled 'Minimum guardband'. Another dashed line points to the PRBs within the UE channel bandwidth, with the text: 'All PRBs falling within UE channel bandwidth not covering the minimum guardband can be used'. + +Figure 5.3.3-2: UE PRB utilization diagram + +**Figure 5.3.3-2: UE 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 UE channel bandwidth for the numerology that is transmitted/received immediately adjacent to the guard band. + +![Figure 5.3.3-3: Guard band definition when transmitting multiple numerologies diagram](1b5a812c8aa20fd5cba28e97001d32de_img.jpg) + +The diagram shows the UE channel bandwidth containing two numerologies, Numerology X and Numerology Y. The total bandwidth is labeled 'UE channel bandwidth'. On the left, a guard band is defined for Numerology X when transmitted across the full UE channel BW. On the right, a guard band is defined for Numerology Y when transmitted across the full UE channel BW. The guard bands are indicated by dashed lines and arrows pointing to the respective areas. + +Figure 5.3.3-3: Guard band definition when transmitting multiple numerologies diagram + +**Figure 5.3.3-3: 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 + +The RB alignment refers to NR RB alignments as specified in 3GPP TS 38.101-1 [5] clause 5.3.4. + +### 5.3.5 UE channel bandwidth per operating band + +The requirements in this specification apply to the combination of channel bandwidths, SCS and operating bands shown in Table 5.3.5-1. The transmission bandwidth configuration in Table 5.3.2-1 shall be supported for each of the specified channel bandwidths. The channel bandwidths are specified for both the Tx and Rx path. + +**Table 5.3.5-1: Channel bandwidths for each NTN satellite band** + +| NTN satellite band | SCS kHz | UE 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.3.6 Asymmetric channel bandwidths + +The UE channel bandwidth can be asymmetric in downlink and uplink. In asymmetric channel bandwidth operation, the narrower carrier shall be confined within the frequency range of the wider channel bandwidth. + +In FDD, the confinement is defined as a maximum deviation to the Tx-Rx carrier center frequency separation (defined in table 5.4.4-1) as following: + +$$\Delta F_{TX-RX} = | (BW_{DL} - BW_{UL})/2 |$$ + +The operating bands and supported asymmetric channel bandwidth combinations are defined in table 5.3.6-1. + +**Table 5.3.6-1: FDD asymmetric UL and DL channel bandwidth combinations** + +| NR Band | Channel bandwidths for UL (MHz) | Channel bandwidths for DL (MHz) | Asymmetric channel bandwidth combination set | +|---------|---------------------------------|---------------------------------|----------------------------------------------| +| n254 | 5 | 10,15 | 0 | +| | 10 | 15 | 0 | + +NOTE 1: The assignment of the paired UL and DL channels are subject to a TX-RX separation as specified in clause 5.4.4. + +NOTE 2: As indicated in TS38.306 [15], it is mandatory for UEs to support asymmetric channel BCS0 if there is an asymmetric BCS0 defined for the band. + +## 5.4 Channel arrangement + +### 5.4.1 Channel spacing + +#### 5.4.1.1 Channel spacing for adjacent NTN satellite carriers + +The channel spacing for adjacent NTN satellite carriers refers to the NR channel spacing as specified in 3GPP TS 38.101-1 [5] clause 5.4.1.1. + +### 5.4.2 Channel raster + +#### 5.4.2.1 NR-ARFCN and channel raster + +The global frequency channel raster defines a set of RF reference frequencies $F_{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...2016666) 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** + +| Frequency range (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 refers to the NR requirements specified in 3GPP TS 38.101-1 [5] clause 5.4.2.2. + +#### 5.4.2.3 Channel raster entries for each operating band + +The RF channel positions on the channel raster in each NTN satellite operating band are given through the applicable NR-ARFCN in Table 5.4.2.3-1, using the channel raster to resource element mapping in clause 5.4.2.2. + +For NTN satellite operating bands with 100 kHz channel raster, $\Delta F_{\text{Raster}} = 20 \times \Delta F_{\text{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** + +| NTN satellite operating band | $\Delta F_{\text{Raster}}$ (kHz) | Uplink Range of $N_{\text{REF}}$ (First – – Last) | Downlink Range of $N_{\text{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 | +| NOTE : 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. | | | | + +For NTN operating bands with 100 kHz channel raster, Enhanced channel raster is defined with $\Delta F_{\text{Raster}} = 2 \times \Delta F_{\text{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-2 is given as <2>. + +**Table 5.4.2.3-2: Applicable NR-ARFCN per operating band** + +| NTN satellite operating band | $\Delta F_{\text{Raster}}$ (kHz) | Uplink Range of $N_{\text{REF}}$ (First – – Last) | Downlink Range of $N_{\text{REF}}$ (First – – Last) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|---------------------------------------------------------------|-----------------------------------------------------------------| +| n256 | 10 | 396000 – <2> – 402000 | 434000 – <2> – 440000 | +| n255 | 10 | 325300 – <2> – 332100 | 305000 – <2> – 311800 | +| NOTE: 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_{\text{REF}}$ with corresponding number GSCN. The parameters defining the $SS_{\text{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_{\text{REF}}$ is given in clause 5.4.3.2. The synchronization raster and the subcarrier spacing of the synchronization block is 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** + +| Frequency range | SS Block frequency position $SS_{\text{REF}}$ | GSCN | Range of GSCN | +|-------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------|----------------|---------------| +| 0 – 3000 MHz | $N * 1200\text{kHz} + M * 50\text{ kHz}$ ,
$N=1:2499, M \in \{1,3,5\}^1$ | $3N + (M-3)/2$ | 2 – 7498 | +| NOTE: The default value for operating bands with 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 refers to 3GPP TS 38.101-1 [5] clause 5.4.3.2. + +#### 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. + +**Table 5.4.3.3-1: Applicable SS raster entries per operating band** + +| NTN satellite operating band | SS Block SCS | SS Block pattern 1 | 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 3GPP TS 38.213 [7]. | | | | + +### 5.4.4 TX–RX frequency separation + +The default TX channel (carrier centre frequency) to RX channel (carrier centre frequency) separation for operating bands is specified in Table 5.4.4-1. + +**Table 5.4.4-1: UE TX-RX frequency separation** + +| NTN Satellite Operating Band | TX – RX
carrier centre frequency
separation | +|------------------------------|---------------------------------------------------| +| n256 | 190 MHz | +| n255 | -101.5 MHz | +| n254 | 862 – 885 MHz | + +# 6 Conducted transmitter characteristics + +## 6.1 General + +Unless otherwise stated, the transmitter characteristics for satellite access UEs are specified at the antenna connector of the UE with a single or multiple transmit antenna(s). For UE with integral antenna only, a reference antenna with a gain of 0 dBi is assumed. Handheld power class 3 UE is assumed in Release 17 for satellite access. + +All requirements in this section are applicable to devices supporting GSO and/or NGSO satellites. + +## 6.2 Transmitter power + +### 6.2.1 UE maximum output power + +The following UE Power Classes define the maximum output power for any transmission bandwidth within the channel bandwidth of NR carrier unless otherwise stated. The period of measurement shall be at least one sub frame (1ms). + +**Table 6.2.1-1: UE Power Class** + +| NR satellite band | Class 3 (dBm) | Tolerance (dB) | +|-------------------|---------------|----------------| +| n256 | 23 | ±2 | +| n255 | 23 | ±2 | +| n254 | 23 | ±2 | + +NOTE 1: $P_{\text{PowerClass}}$ is the maximum UE power specified without taking into account the tolerance +NOTE 2: Power class 3 is default power class unless otherwise stated + +The UE shall meet the following additional requirements for maximum mean transmission power density specified in Table 6.2.1-2 when NS is signaled and when the configured channel overlaps with any portion of the specified frequency range. + +**Table 6.2.1-2: Additional requirements for transmit power density** + +| NR Band | NS value | Channel bandwidth (MHz) | Frequency range (MHz) | Maximum power density | +|---------|----------|-------------------------|-----------------------|----------------------------------------------| +| n254 | NS_04N | 5 | 1610 - 1618.25 | 27dBm/4kHz (mean)
15dBm/4kHz (peak limit) | +| | NS_05N | 5 | 1618.25 - 1626.5 | | +| | | 10, 15 | 1610 – 1626.5 | | + +### 6.2.2 UE maximum output power reduction + +UE is allowed to reduce the maximum output power due to higher order modulations and transmit bandwidth configurations. For UE power class 3, the allowed maximum power reduction (MPR) is defined as Table 6.2.2-1 in 3GPP TS 38.101-1[5] clause 6.2.2. + +### 6.2.3 UE additional maximum output power reduction + +#### 6.2.3.1 General + +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 and an associated value in the field *additionalSpectrumEmission*. Throughout this specification, the notion of indication or signalling of an NS value refers to the corresponding indication of an NR satellite band number of the applicable operating band, the IE field *freqBandIndicatorNR* and an associated value of *additionalSpectrumEmission* in the relevant RRC information elements [6]. + +To meet the additional requirements, additional maximum power reduction (A-MPR) is allowed for the maximum output power as specified in Table 6.2.1-1. Unless stated otherwise, the total reduction to UE maximum output power is max(MPR, A-MPR) where MPR is defined in clause 6.2.2. Outer and inner allocation notation used in clause 6.2.3 is defined in 3GPP TS 38.101-1 [5] clause 6.2.2. In absence of modulation and waveform types the A-MPR applies to all modulation and waveform types. + +Table 6.2.3.1-1 specifies the additional requirements with their associated network signalling values and the allowed A-MPR and applicable operating band(s) for each NS value. The mapping of NR satellite band numbers and values of the *additionalSpectrumEmission* to network signalling labels is specified in Table 6.2.3.1-1A. + +**Table 6.2.3.1-1: Additional maximum power reduction (A-MPR)** + +| Network signalling label | Requirements (clause) | NR satellite Band | Channel bandwidth (MHz) | Resources blocks ( $N_{RB}$ ) | A-MPR (dB) | +|--------------------------|------------------------------------|-------------------|-------------------------|------------------------------------------|------------------------------------------------------| +| NS_01 | | Table 5.2-1 | 5, 10, 15, 20 | Table 5.3.2-1 in 3GPP TS 38.101-1 [5] | N/A | +| NS_24 | 6.5.3.3.13 in 3GPP TS 38.101-1 [5] | n256 | 5, 10, 15, 20 | Table 6.2.3.15-1 in 3GPP TS 38.101-1 [5] | Clause 6.2.3.15 in 3GPP TS 38.101-1 [5] 2 | +| NS_02N | 6.5.3.3.2 | n255 | 5, 10, 15, 20 | | N/A | +| NS_100 | 6.5.2.4.2 in 3GPP TS 38.101-1 [5] | n256 1 | | | Table 6.2.3.1-2 in 3GPP TS 38.101-1 [5] | +| NS_03N | 6.5.3.3.3 | n254 | 5, 10, 15 | | Clause 6.2.3.2 | +| NS_04N | 6.5.3.3.4 | n254 | 5 | | Clause 6.2.3.3 | +| NS_05N | 6.5.3.3.4 | n254 | 5, 10, 15 | | Clause 6.2.3.4 | + +NOTE 1: This NS can be signalled for NR bands that have UTRA services deployed. + +NOTE 2: A-MPR for the upper 5 MHz of the band is not specified, and therefore shall be used as a guard band. + +[The NS\_01 label with the field *additionalPmax* [8] absent is default for all NTN satellite bands.] + +Table 6.2.3.1-1A: Mapping of network signalling label + +| NR satellite band | Value of additionalSpectrumEmission | | | | | | | | +|-------------------|-------------------------------------|--------|--------|--------|---|---|---|---| +| | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | +| n256 | NS 01 | NS 24 | NS 100 | | | | | | +| n255 | NS 01 | NS 02N | | | | | | | +| n254 | NS 01 | NS 03N | NS 04N | NS 05N | | | | | + +NOTE: *additionalSpectrumEmission* corresponds to an information element of the same name defined in clause 6.3.2 of 3GPP TS 38.331 [8]. + +#### 6.2.3.2 A-MPR for NS\_03N + +Table 6.2.3.2-1: A-MPR regions for NS\_03N + +| Channel BW | Carrier Center Frequency | RB_start*12*SCS (MHz) | LCRB*12*SCS (MHz) | A-MPR | +|------------|--------------------------|-----------------------|-------------------|-------| +| 5MHz | 1612.5 <= fc < 1613.9 | <= 0.36 | <= 0.36 | A1 | +| | | | >= 2.88 | A2 | +| | 1613.9 <= fc < 1615.7 | | >= 3.24 | A3 | +| 10MHz | 1615 <= fc < 1620.1 | <= 1.8 | <= 5.04 | A4 | +| | | <= 1.8 | > 5.04 | A5 | +| | | > 7.2 | > 0 | A6 | +| | | > 1.8 | >= 2.88 | A2 | +| | 1620.1 <= fc < 1621.5 | | <= 6.48 | A6 | +| | fc = 1621.5 | <= 0.36 | <= 0.36 | A1 | +| 15MHz | all | | >= 7.2 | A1 | +| | | <= 3.6 | <= 5.04 | A4 | +| | | <= 3.6 | > 5.04 | A5 | +| | | > 10.44 | | A6 | +| | | > 3.6 | >= 4.32 | A2 | + +Table 6.2.3.2-2: A-MPR for NS\_03N + +| | Modulation | A1 | A2 | A3 | A4 | A5 | A6 | +|------------|------------|-------|-------|-------|-------|--------|-------| +| DFT-s-OFDM | Pi/2 BPSK | [2.5] | [3.0] | [1.0] | [4.0] | [6.5] | [1.5] | +| | QPSK | [2.5] | [4.0] | [2.5] | [6.0] | [7.0] | [2.0] | +| | 16QAM | [2.5] | [4.0] | [2.5] | [6.0] | [7.0] | [2.0] | +| | 64QAM | | [4.0] | [2.5] | [6.0] | [7.0] | [2.0] | +| | 256QAM | | | | | | | +| CP-OFDM | QPSK | [3.5] | [6.0] | [4.0] | [8.0] | [10.0] | [4.0] | +| | 16QAM | [3.5] | [6.0] | [4.0] | [8.0] | [10.0] | [4.0] | +| | 64QAM | [3.5] | [6.0] | [4.0] | [8.0] | [10.0] | [4.0] | +| | 256QAM | | [6.0] | | [8.0] | [10.0] | | + +#### 6.2.3.3 A-MPR for NS\_04N + +Table 6.2.3.3-1: A-MPR regions for NS\_04N + +| Channel BW | Carrier Center Frequency | RB_start*12*SCS (MHz) | LCRB*12*SCS (MHz) | A-MPR | +|------------|--------------------------|-----------------------|-------------------|-------| +| 5MHz | 1612.5 <= fc < 1613.9 | <= 0.36 | <= 0.36 | A1 | +| | 1613.9 <= fc < 1615.7 | | >= 2.88 | A2 | +| | | | >= 3.24 | A3 | + +Table 6.2.3.3-2: A-MPR for NS\_04N + +| | Modulation | A1 | A2 | A3 | +|------------|------------|-------|-------|-------| +| DFT-s-OFDM | Pi/2 BPSK | [2.5] | [3.0] | [1.0] | +| | QPSK | [2.5] | [4.0] | [2.5] | +| | 16QAM | [2.5] | [4.0] | [2.5] | +| | 64QAM | | [4.0] | [2.5] | +| | 256QAM | | | | +| CP-OFDM | QPSK | [3.5] | [6.0] | [4.0] | +| | 16QAM | [3.5] | [6.0] | [4.0] | +| | 64QAM | [3.5] | [6.0] | [4.0] | +| | 256QAM | | [6.0] | | + +#### 6.2.3.4 A-MPR for NS\_05N + +Table 6.2.3.4-1: A-MPR regions for NS\_05N + +| Channel BW | Carrier Center Frequency | RB_start*12*SCS (MHz) | LCRB*12*SCS (MHz) | A-MPR | +|------------|--------------------------|-----------------------|-------------------|-------| +| 5MHz | 1622.4 < fc <= 1624 | <= 3.6 | > 0.36 | A3 | +| | | | >= 2.88 | A1 | +| 10MHz | 1615 <= fc < 1620.1 | <= 1.8 | <= 5.04 | A4 | +| | | <= 1.8 | > 5.04 | A5 | +| | | > 7.2 | > 0 | A6 | +| | | > 1.8 | >= 2.88 | A2 | +| | 1620.1 <= fc <= 1621.5 | | <= 7.2 | A6 | +| | | <= 0.36 | <= 0.36 | A1 | +| | | > 7.2 | > 0 | A6 | +| | | | | | +| 15MHz | all | <= 3.6 | <= 5.04 | A4 | +| | | <= 3.6 | > 5.04 | A5 | +| | | > 10.44 | | A6 | +| | | > 3.6 | >= 4.32 | A2 | + +Table 6.2.3.4-2: A-MPR for NS\_05N + +| | Modulation | A1 | A2 | A3 | A4 | A5 | A6 | +|------------|------------|-------|-------|-------|-------|--------|-------| +| DFT-s-OFDM | Pi/2 BPSK | [1.5] | [5.0] | [1.5] | [6.5] | [6.5] | [2.0] | +| | QPSK | [1.5] | [5.0] | [1.5] | [6.5] | [7.0] | [2.5] | +| | 16QAM | [1.5] | [5.0] | [1.5] | [6.5] | [7.0] | [2.5] | +| | 64QAM | | [5.0] | | [6.5] | [7.0] | [2.5] | +| | 256QAM | | | | | | | +| CP-OFDM | QPSK | [3.0] | [6.5] | | [8.0] | [10.0] | [4.5] | +| | 16QAM | [3.0] | [6.5] | | [8.0] | [10.0] | [4.5] | +| | 64QAM | [3.0] | [6.5] | | [8.0] | [10.0] | [4.5] | +| | 256QAM | | [6.5] | | [8.0] | [10.0] | | + +### 6.2.4 Configured transmitted power + +The requirements for configured transmitted power defined in subclause 6.2.4 of 3GPP TS 38.101-1 [5] clause 6.2.4 shall apply to NTN satellite UE. + +## 6.3 Output power dynamics. + +### 6.3.1 Minimum output power + +The minimum controlled output power of the UE is defined as the power in the channel bandwidth for all transmit bandwidth configurations (resource blocks), when the power is set to a minimum value. + +The minimum output power is defined as the mean power in at least one sub-frame (1 ms). The minimum output power shall not exceed the values specified in Table 6.3.1-1. + +**Table 6.3.1-1: Minimum output power** + +| Channel bandwidth (MHz) | Minimum output power (dBm) | Measurement bandwidth (MHz) | +|-------------------------|----------------------------|-----------------------------| +| 5 | -40 | 4.515 | +| 10 | -40 | 9.375 | +| 15 | -40 | 14.235 | +| 20 | -40 | 19.095 | + +### 6.3.2 Transmit OFF power + +Transmit OFF power is defined as the mean power in the channel bandwidth when the transmitter is OFF. The transmitter is considered OFF when the UE is not allowed to transmit on any of its ports. + +The transmit OFF power is defined as the mean power in a duration of at least one sub-frame (1 ms) excluding any transient periods. The transmit OFF power shall not exceed the values specified in Table 6.3.2-1. + +**Table 6.3.2-1: Transmit OFF power** + +| | | | +|-----------------------|-------|-----------------------------------------------------| +| Channel bandwidth | (MHz) | 5, 10, 15, 20 | +| REF_SCS | (kHz) | 15 | +| Transmit OFF power | (dBm) | -50 | +| Measurement bandwidth | (MHz) | $MBW = REF\_SCS \cdot (12 \cdot N_{RB} + 1) / 1000$ | + +### 6.3.3 Transmit ON/OFF time mask + +The requirements for transmit ON/OFF time mask defined in 3GPP TS 38.101-1 [5] clause 6.3.3 shall apply for NTN satellite UE. + +### 6.3.4 Power control + +The requirements for Power control defined in 3GPP TS 38.101-1 [5] clause 6.3.4 shall apply for NTN satellite UE. + +## 6.4 Transmit signal quality + +### 6.4.1 Frequency error + +The NTN satellite UE basic measurement interval of modulated carrier frequency is 1 UL slot. The NTN satellite UE pre-compensates the uplink modulated carrier frequency by the estimated Doppler shift according to 3GPP TS 38.300 [9] clause 16.14.2. The mean value of basic measurements of NTN UE modulated carrier frequency shall be accurate to within $\pm 0.1$ PPM observed over a period of 1 ms of cumulated measurement intervals compared to ideally pre-compensated reference uplink carrier frequency. + +[NOTE: The ideally pre-compensated reference uplink carrier frequency consists of the UL carrier frequency signalled to the UE by SAN and UL pre-compensated Doppler frequency shift.] + +### 6.4.2 Transmit modulation quality + +The requirements for transmit modulation quality defined in 3GPP TS 38.101-1 [5] clause 6.4.2 shall apply for NTN satellite UE. + +## 6.5 Output RF spectrum emissions + +### 6.5.1 Occupied bandwidth + +Occupied bandwidth is defined as the bandwidth containing 99 % of the total integrated mean power of the transmitted spectrum on the assigned channel. The occupied bandwidth for all transmission bandwidth configurations (Resources Blocks) shall be less than the channel bandwidth specified in Table 6.5.1-1. + +**Table 6.5.1-1: Occupied channel bandwidth** + +| | NR NTN satellite channel bandwidth (MHz) | +|----------------------------------|--------------------------------------------| +| | 5, 10, 15, 20 | +| Occupied channel bandwidth (MHz) | Same as NR NTN satellite channel bandwidth | + +### 6.5.2 Out of band emission + +#### 6.5.2.1 General + +The Out of band emissions are unwanted emissions immediately outside the assigned channel bandwidth resulting from the modulation process and non-linearity in the transmitter but excluding spurious emissions. This out of band emission limit is specified in terms of a spectrum emission mask and an adjacent channel leakage power ratio. + +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.5.2.2 Spectrum emission mask + +The spectrum emission mask of the UE applies to frequencies ( $\Delta f_{\text{OOB}}$ ) starting from the $\pm$ edge of the assigned NR channel bandwidth. For frequencies offset greater than $\Delta f_{\text{OOB}}$ , the spurious requirements in clause 6.5.3 are applicable. + +NOTE: For measurement conditions at the edge of each frequency range, the lowest frequency of the measurement position in each frequency range should be set at the lowest boundary of the frequency range plus MBW/2. The highest frequency of the measurement position in each frequency range should be set at the highest boundary of the frequency range minus MBW/2. MBW denotes the measurement bandwidth defined for the protected band. + +The power of any UE emission shall not exceed the levels specified in Table 6.5.2.2-1 for the specified channel bandwidth. + +**Table 6.5.2.2-1: General NR spectrum emission mask** + +| $\Delta f_{\text{OOB}}$ (MHz) | Channel bandwidth (MHz) / Spectrum emission limit (dBm) | | Measurement bandwidth | +|---------------------------------------------------------|---------------------------------------------------------|------------|-----------------------| +| | 5 | 10, 15, 20 | | +| $\pm$ 0-1 | -13 | -13 | 1 % of channel BW | +| $\pm$ 1-5 | -10 | -10 | 1 MHz | +| $\pm$ 5-6 | -13 | | | +| $\pm$ 6-10 | -25 | | | +| $\pm$ 5-BW Channel | | -13 | | +| $\pm$ BW Channel -(BW Channel +5) | | -25 | | + +#### 6.5.2.3 Additional spectrum emission mask + +##### 6.5.2.3.1 Requirements for network signalling value "NS\_04N" + +When "NS\_04N" is indicated in the cell, the power of any UE emission shall not exceed the levels specified in Table 6.5.2.3.1-1 for any channel bandwidth configured within 1610-1618.25MHz. + +**Table 6.5.2.3.1-1: Additional requirements for "NS\_04N"** + +| $\Delta f_{\text{O0B}}$ (kHz) | Spectrum emission limit (dBm) | Measurement bandwidth | +|-------------------------------|-------------------------------|-----------------------| +| $\pm 0$ -160 | -2 | 30kHz | +| $\pm 160$ -2300 | -2 to -26 | | +| $\pm 2300$ -18500 | -26 | | + +NOTE 1: Spectrum emissions are linearly interpolated in dBm versus frequency offset. +NOTE 2: The EIRP requirement in regulation is converted to conducted requirement using a 0dBi antenna. + +##### 6.5.2.3.2 Requirements for network signalling value "NS\_05N" + +When "NS\_05N" is indicated in the cell, the power of any UE emission shall not exceed the levels specified in Table 6.5.2.3.2-1 for any channel bandwidth configured within 1618.25-1626.5MHz. + +**Table 6.5.2.3.2-1: Additional requirements for "NS\_05N"** + +| $\Delta f_{\text{O0B}}$ (kHz) | Spectrum emission limit (dBm) | Measurement bandwidth | +|-------------------------------|-------------------------------|-----------------------| +| $\pm 0$ -160 | -5 | 30kHz | +| $\pm 160$ -225 | -5 to -8.5 | | +| $\pm 225$ -650 | -8.5 to -15 | | +| $\pm 650$ -1365 | -15 | | +| $\pm 1365$ -1800 | -23 to -26 | | +| $\pm 1800$ -16500 | -26 | | + +NOTE 1: Spectrum emissions are linearly interpolated in dBm versus frequency offset. +NOTE 2: The EIRP requirement in regulation is converted to conducted requirement using a 0dBi antenna. + +#### 6.5.2.4 Adjacent channel leakage ratio + +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. + +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.5.2.4.1 NR ACLR + +NR Adjacent Channel Leakage power Ratio (NRACLR) is the ratio of the filtered mean power centred on the assigned NR channel frequency to the filtered mean power centred on an adjacent NR channel frequency at nominal channel spacing. + +The assigned NR channel power and adjacent NR channel power are measured with rectangular filters with measurement bandwidths specified in Table 6.5.2.4.1-1. + +If the measured adjacent channel power is greater than -50 dBm then the NRACLR shall be higher than the value specified in Table 6.5.2.4.1-2. + +**Table 6.5.2.4.1-1: NR ACLR measurement bandwidth** + +| | | | +|--------------------------------------|-------|---------------------------------------------| +| Channel bandwidth | (MHz) | 5,10,15,20 | +| REF_SCS | (kHz) | 15 | +| NR ACLR measurement bandwidth | (MHz) | $MBW = REF\_SCS * (12 * N_{RB} + 1) / 1000$ | + +**Table 6.5.2.4.1-2: NR ACLR requirement** + +| | | +|----------------|----------------------| +| | Power class 3 | +| NR ACLR | 30 dB | + +##### 6.5.2.4.2 UTRA ACLR + +UTRA adjacent channel leakage power ratio (UTRAACLR) is the ratio of the filtered mean power centred on the assigned NR channel frequency to the filtered mean power centred on an adjacent(s) UTRA channel frequency. + +UTRAACLR is specified for the first adjacent UTRA channel (UTRAACLR1) which center frequency is $\pm 2.5$ MHz from NR channel edge and for the 2nd adjacent UTRA channel (UTRAACLR2) which center frequency is $\pm 7.5$ MHz from NR channel edge. + +The UTRA channel power is measured with a RRC filter with roll-off factor $\alpha = 0.22$ and bandwidth of 3.84 MHz. The assigned NR channel power is measured with a rectangular filter with measurement bandwidth specified in Table 6.5.2.4.1-1. + +If the measured adjacent channel power is greater than $-50$ dBm then the UTRAACLR1 and UTRAACLR2 shall be higher than the value specified in Table 6.5.2.4.2-1. + +**Table 6.5.2.4.2-1: UTRA ACLR requirement** + +| | | +|-----------------------------|----------------------| +| | Power class 3 | +| UTRAACLR1 | 33 dB | +| UTRAACLR2 | 36 dB | + +UTRA ACLR requirement is applicable when signalled by the network with network signalling value indicated by the field *additionalSpectrumEmission*. + +### 6.5.3 Spurious emission + +#### 6.5.3.1 General spurious emissions + +Unless otherwise stated, the spurious emission limits apply for the frequency ranges that are more than $F_{OOB}$ (MHz) in Table 6.5.3.1-1 from the edge of the channel bandwidth. The spurious emission limits in Table 6.5.3.1-2 apply for all transmitter band configurations ( $N_{RB}$ ) and channel bandwidths. + +**Table 6.5.3.1-1: Boundary between NR out of band and general spurious emission domain** + +| | | +|--------------------------|------------------------------------------------| +| Channel bandwidth | OOB boundary F_{OOB} (MHz) | +| $BW_{Channel}$ | $BW_{Channel} + 5$ | + +Table 6.5.3.1-2: Requirement for general spurious emissions limits + +| Frequency Range | Maximum Level | Measurement bandwidth | NOTE | +|-----------------------------------------------------------------------------------------------------|---------------|-----------------------|------| +| 9 kHz $\leq f < 150$ kHz | -36 dBm | 1 kHz | | +| 150 kHz $\leq f < 30$ MHz | -36 dBm | 10 kHz | | +| 30 MHz $\leq f < 1000$ MHz | -36 dBm | 100 kHz | | +| 1 GHz $\leq f < 5^{\text{th}}$ harmonic of the upper frequency edge of the UL operating band in GHz | -30 dBm | 1 MHz | | + +#### 6.5.3.2 Spurious emissions for UE co-existence + +This clause specifies the requirements for NR NTN satellite bands for UE coexistence with protected bands. + +Table 6.5.3.2-1: Requirements for spurious emissions for UE co-existence + +| NR NTN satellite Band | Spurious emission for UE co-existence | | | | | | | +|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---|----------------|---------------------|-----------|------| +| | Protected band | Frequency range (MHz) | | | Maximum Level (dBm) | MBW (MHz) | NOTE | +| n254 | NR Band n1, n2, n3, n5, n7, n8, n12, n13, n14, n18, n20, n24, n25, n26, n28, n29, n30, n34, n38, n39, n40, n41, n48, n50, n51, n53, n54, n65, n66, n67, n70, n71, n74, n75, n76, n77, n78, n85, n90, n91, n92, n93, n94, n100, n101, n105, | $F_{DL\_low}$ | - | $F_{DL\_high}$ | -50 | 1 | | +| | E-UTRA Band 31, 54, 72, 73, 87, 88, 103 | $F_{DL\_low}$ | - | $F_{DL\_high}$ | -50 | 1 | | +| | NR Band n79, n104 | $F_{DL\_low}$ | - | $F_{DL\_high}$ | -50 | 1 | 2 | +| n255 | NR Band n1, n2, n3, n5, n7, n8, n12, n13, n14, n18, n20, n24, n25, n26, n28, n29, n30, n34, n38, n39, n40, n41, n48, n50, n51, n53, n65, n66, n67, n70, n71, n74, n75, n76, n85, n90, n91, n92, n93, n94, n100, n101 | $F_{DL\_low}$ | - | $F_{DL\_high}$ | -50 | 1 | | +| | NR Band n77, n78, n79 | $F_{DL\_low}$ | - | $F_{DL\_high}$ | -50 | 1 | 2 | +| n256 | NR Band n1, n3, n5, n7, n8, n12, n13, n14, n18, n20, n24, n26, n28, n29, n30, n38, n39, n40, n41, n48, n50, n51, n53, n54, n65, n66, n67, n71, n74, n75, n76, n78, n79, n85, n90, n91, n92, n93, n94, n101, n100, n101 | $F_{DL\_low}$ | - | $F_{DL\_high}$ | -50 | 1 | | +| | E-UTRA Band 33, 35 | $F_{DL\_low}$ | - | $F_{DL\_high}$ | -50 | 1 | | +| | NR Band n77 | $F_{DL\_low}$ | - | $F_{DL\_high}$ | -50 | 1 | 2 | +| | NR Band n2, n25, n70 | $F_{DL\_low}$ | - | $F_{DL\_high}$ | NA | NA | 3 | + +NOTE 1: The protected NR or E-UTRA bands are specified in clause 5.2 from 3GPP TS 38.101-1 [5] or 3GPP TS 36.101 [10]. $F_{DL\_low}$ and $F_{DL\_high}$ refer to each frequency band specified in Table 5.2-1 in 3GPP TS 38.101-1 [5] or 3GPP TS 36.101 [10]. + +NOTE 2: As exceptions, measurements with a level up to the applicable requirements defined in Table 6.5.3.1-2 are permitted for each assigned NR carrier used in the measurement due to 2nd, 3rd, 4th or 5th harmonic spurious emissions. Due to spreading of the harmonic emission the exception is also allowed for the first 1 MHz frequency range immediately outside the harmonic emission on both sides of the harmonic emission. This results in an overall exception interval centred at the harmonic emission of $(2 \text{ MHz} + N \times L_{CRB} \times RB_{size} \text{ kHz})$ , where N is 2, 3, 4, 5 for the 2nd, 3rd, 4th or 5th harmonic respectively. The exception is allowed if the measurement bandwidth (MBW) totally or partially overlaps the overall exception interval. + +| NR NTN satellite Band | Spurious emission for UE co-existence | | | | | +|------------------------------------------------------------------------------------------------------------|---------------------------------------|-----------------------|---------------------|-----------|------| +| | Protected band | Frequency range (MHz) | Maximum Level (dBm) | MBW (MHz) | NOTE | +| NOTE 3: The co-existence between n256 and band n2, n25 and n70 is subject to regional/national regulation. | | | | | | + +NOTE: To simplify Table 6.5.3.2-1, NR band numbers are listed for bands which are specified only for NR operation or both E-UTRA and NR operation. E-UTRA band numbers are listed for bands which are specified only for E-UTRA operation. + +#### 6.5.3.3 Additional spurious emissions + +##### 6.5.3.3.1 General + +These requirements are specified in terms of an additional spectrum emission requirement. Additional spurious emission requirements are signalled by the network to indicate that the UE shall meet an additional requirement for a specific deployment scenario as part of the cell handover/broadcast message. + +##### 6.5.3.3.2 Requirement for network signalling value "NS\_02N" + +When "NS\_02N" is indicated in the cell, the power of any UE emission shall not exceed the levels specified in Table 6.5.3.3.2-1. This requirement also applies for the frequency ranges that are less than $F_{\text{OOB}}$ (MHz) in Table 6.5.3.1-1 from the edge of the channel bandwidth. + +**Table 6.5.3.3.2-1: Additional requirements for "NS\_02N"** + +| Frequency band (MHz) | Channel bandwidth / Spectrum emission limit 1 (dBm) | Measurement bandwidth | NOTE | +|-------------------------------------------------------------------------------------------------------|----------------------------------------------------------------|-----------------------|--------------------------------------------------------------| +| | 5 MHz, 10 MHz, 15 MHz, 20 MHz | | | +| $1559 \leq f \leq 1605$ | -50 | 700 Hz | Averaged over any 2 millisecond active transmission interval | +| $1605 \leq f \leq 1610$ | $-50 + 24/5 (f - 1605)$ | 700Hz | | +| $1559 \leq f \leq 1605$ | -40 | 1MHz | Averaged over any 2 millisecond active transmission interval | +| $1605 \leq f \leq 1610$ | $-40 + 24/5 (f - 1605)$ | 1MHz | | +| NOTE: The EIRP requirement in regulation is converted to conducted requirement using a 0 dBi antenna. | | | | + +##### 6.5.3.3.3 Requirement for network signalling value "NS\_03N" + +When "NS\_03N" is indicated in the cell, the power of any UE emission shall not exceed the levels specified in Table 6.5.3.3.3-1. This requirement also applies for the frequency ranges that are less than $F_{\text{OOB}}$ (MHz) in Table 6.5.3.1-1 from the edge of the channel bandwidth. + +**Table 6.5.3.3.3-1: Additional out-of-band requirements for "NS\_03N"** + +| Frequency band (MHz) | Channel bandwidth / Spectrum emission limit 1 (dBm) | Measurement bandwidth | NOTE | +|------------------------------------------------------------------------------------------------------|----------------------------------------------------------------|-----------------------|---------------------------------------------------------------------------------| +| | 5 MHz, 10 MHz, 15 MHz | | | +| $1559 \leq f \leq 1605$ | -50 | 700 Hz | Discreet emissions averaged over any 2 millisecond active transmission interval | +| $1605 \leq f \leq 1610$ | $-50 + 60/5 (f-1605)$ | 700 Hz | | +| $1559 \leq f \leq 1605$ | -40 | 1MHz | Averaged over any 2 millisecond active transmission interval | +| $1605 \leq f \leq 1610$ | $-40 + 60/5 (f-1605)$ | 1MHz | | +| NOTE: The EIRP requirement in regulation is converted to conducted requirement using a 0dBi antenna. | | | | + +##### 6.5.3.3.4 Requirement for network signalling value "NS\_04N" and "NS\_05N" + +When "NS\_04N" or "NS\_05N" is indicated in the cell, the power of any UE emission shall not exceed the levels specified in Table 6.5.3.3.4-1. This requirement also applies for the frequency ranges that are less than $F_{\text{OOB}}$ (MHz) in Table 6.5.3.1-1 from the edge of the channel bandwidth. + +**Table 6.5.3.3.4-1: Additional out-of-band requirements for "NS\_04N" and "NS\_05N"** + +| Frequency band (MHz) | Channel bandwidth / Spectrum emission limit 1 (dBm) | Measurement bandwidth | NOTE | +|------------------------------------------------------------------------------------------------------|----------------------------------------------------------------|-----------------------|--------------------------------------------------------------| +| | 5 MHz, 10 MHz, 15 MHz | | | +| $1559 \leq f \leq 1605$ | -40 | 1MHz | Averaged over any 2 millisecond active transmission interval | +| $1605 \leq f \leq 1610$ | $-40 + 60/5 (f-1605)$ | 1MHz | | +| | | | | +| $1628.5 \leq f \leq 1631.5$ | -30 | 30kHz | | +| $1631.5 \leq f \leq 1636.5$ | -30 | 100kHz | | +| $1636.5 \leq f \leq 1646.5$ | -30 | 300kHz | | +| $1646.5 \leq f \leq 1666.5$ | -30 | 1MHz | | +| $1666.5 \leq f \leq 2200$ | -30 | 3MHz | | +| NOTE: The EIRP requirement in regulation is converted to conducted requirement using a 0dBi antenna. | | | | + +### 6.5.4 Transmit intermodulation + +The transmit intermodulation performance is a measure of the capability of the transmitter to inhibit the generation of signals in its non-linear elements caused by presence of the wanted signal and an interfering signal reaching the transmitter via the antenna. + +UE transmit intermodulation is defined by the ratio of the mean power of the wanted signal to the mean power of the intermodulation product when an interfering CW signal is added at a level below the wanted signal at each transmitter antenna port with the other antenna port(s) if any terminated. Both the wanted signal power and the intermodulation product power are measured through NR rectangular filter with measurement bandwidth shown in Table 6.5.4-1. + +The requirement of transmit intermodulation is specified in Table 6.5.4-1. + +**Table 6.5.4-1: Transmit Intermodulation** + +| | | | +|-----------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------| +| Wanted signal channel bandwidth | $BW_{\text{Channel}}$ | | +| Interference signal frequency offset from channel center | $BW_{\text{Channel}}$ | $2*BW_{\text{Channel}}$ | +| Interference CW signal level | -40 dBc | | +| Intermodulation product | < -29 dBc | < -35 dBc | +| Measurement bandwidth | The maximum transmission bandwidth configuration among the different SCS's for the channel BW as defined in Table 6.5.2.4.1-1 | | +| Measurement offset from channel center | $BW_{\text{Channel}}$ and $2*BW_{\text{Channel}}$ | $2*BW_{\text{Channel}}$ and $4*BW_{\text{Channel}}$ | + +# 7 Conducted receiver characteristics + +## 7.1 General + +Unless otherwise stated the receiver characteristics are specified at the antenna connector(s) of the UE. For UE(s) with an integral antenna only, a reference antenna(s) with a gain of 0 dBi is assumed for each antenna port(s). UE 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 UEs 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). + +The levels of the test signal applied to each of the antenna connectors shall be as defined in the respective clauses below. + +With the exception of clause 7.3, the requirements shall be verified with the network signalling value NS\_01 configured in Table 6.2.3.1-1. + +All requirements in this section are applicable to devices supporting GSO and/or NGSO satellites. + +All the parameters in clause 7 are defined using the UL reference measurement channels specified in 3GPP TS 38.101-1 [5] Annex A.2.2, the DL reference measurement channels specified in 3GPP TS 38.101-1 [5] Annex A.3.2 and using the set-up specified in 3GPP TS 38.101-1 [5] Annex C.3.1. + +## 7.2 Diversity characteristics + +The UE is required to be equipped with a minimum of two RX antenna ports in all operating bands. + +The UE shall be verified with two RX antenna ports in all supported frequency bands. + +The above rules apply for all clauses with the exception of clause 7.9. + +## 7.3 Reference sensitivity + +### 7.3.1 General + +The reference sensitivity power level REFSENS is the minimum mean power applied to each one of the UE antenna ports for all UE categories, at which the throughput shall meet or exceed the requirements for the specified reference measurement channel. + +In later clauses of Clause 7 where the value of REFSENS is used as a reference to set the corresponding requirement: + +in all bands, the UE shall be verified against those requirements by applying the REFSENS value in Table 7.3.2-1. + +### 7.3.2 Reference sensitivity power level + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in Annex A3.2.2 of 3GPP TS 38.101-1 [5], with parameters specified in Table 7.3.2-1. + +**Table 7.3.2-1: Two antenna port reference sensitivity QPSK PREFSENS for FDD bands** + +| | | Operating band / SCS / Channel bandwidth | | | | | | | | | | +|----------------|---------|------------------------------------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------| +| Operating Band | SCS kHz | 5 MHz (dBm) | 10 MHz (dBm) | 15 MHz (dBm) | 20 MHz (dBm) | 25 MHz (dBm) | 30 MHz (dBm) | 35 MHz (dBm) | 40 MHz (dBm) | 45 MHz (dBm) | 50 MHz (dBm) | +| n256 | 15 | -99.5 | -96.3 | -94.5 | -93.8 | | | | | | | +| | 30 | | -96.6 | -94.6 | -94.0 | | | | | | | +| | 60 | | -97.0 | -94.9 | -94.2 | | | | | | | +| n255 | 15 | -100.0 | -96.8 | -95.0 | -93.8 | | | | | | | +| | 30 | | -97.1 | -95.1 | -94.0 | | | | | | | +| | 60 | | -97.5 | -95.4 | -94.2 | | | | | | | +| n254 | 15 | -99.5 | -96.3 | -94.5 | | | | | | | | +| | 30 | | -96.6 | -94.6 | | | | | | | | +| | 60 | | -97.0 | -94.9 | | | | | | | | + +NOTE: The transmitter shall be set to $P_{\text{MAX}}$ as defined in clause 6.2.4 of 3GPP TS 38.101-1 [5]. + +The reference receiver sensitivity (REFSENS) requirement specified in Table 7.3.2-1 shall be met with uplink transmission bandwidth less than or equal to that specified in Table 7.3.2-2. + +less than or equal to that specified in Table 7.3.2-2. + +**Table 7.3.2-2: Uplink configuration for reference sensitivity** + +| | | Operating band / SCS (kHz) / Channel bandwidth (MHz) | | | | Duplex Mode | +|----------------|-----|------------------------------------------------------|----|----|------|-------------| +| Operating Band | SCS | 5 | 10 | 15 | 20 | | +| n256 | 15 | 25 | 50 | 75 | 100 | FDD | +| | 30 | | 24 | 36 | 50 | | +| | 60 | | 10 | 18 | 24 | | +| n255 | 15 | 25 | 50 | 75 | [75] | FDD | +| | 30 | | 24 | 36 | [36] | | +| | 60 | | 10 | 18 | [18] | | +| n254 | 15 | 25 | 50 | 75 | | FDD | +| | 30 | | 24 | 36 | | | +| | 60 | | 10 | 18 | | | + +NOTE: UL resource blocks shall be located as close as possible to the downlink operating band but confined within the transmission bandwidth configuration for the channel bandwidth (Table 5.3.2-1 of 3GPP TS 38.101-1 [5]). + +The minimum requirements specified in Table 7.3.2-1 shall be verified with the network signalling value NS\_01 (Table 6.2.3.1-1 of 3GPP TS 38.101-1 [5]) configured. + +## 7.4 Maximum input level + +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. The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in 3GPP TS 38.101-1 [5] Annex A.3.2 (with one sided dynamic OCNG Pattern OP.1 FDD as described in 3GPP TS 38.101-1 [5] Annex A.5.1.1) with parameters specified in Table 7.4-1. + +**Table 7.4-1: Maximum input level** + +| Rx Parameter | Units | Channel bandwidth (MHz) | +|--------------|-------|-------------------------| +| | | 5, 10, 15, 20 | + +| | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|------------------| +| Power in Transmission Bandwidth Configuration 3 | dBm | -40 2 | +| 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-2 with $P_{\text{CMAX\_L,f,c}}$ as defined in clause 6.2.4. | | | +| NOTE 2: Reference measurement channel is specified in 3GPP TS 38.101-1 [5] Annex A.3.2.3 for 64 QAM. | | | +| NOTE 3: Power in transmission bandwidth configuration value is rounded to the nearest 0.5dB value. | | | + +## 7.5 Adjacent channel selectivity + +Adjacent channel selectivity (ACS) is a measure of a receiver's ability to receive an NR signal at its assigned channel frequency in the presence of an adjacent channel signal at a given frequency offset from the centre frequency of the assigned channel. ACS is the ratio of the receive filter attenuation on the assigned channel frequency to the receive filter attenuation on the adjacent channel(s). + +In Release 17, only frequency bands below 2.7GHz are considered. The NR satellite UE shall fulfil the minimum requirements specified in Table 7.5-1 for NR satellite bands with $F_{\text{DL\_high}} < 2700$ MHz and $F_{\text{UL\_high}} < 2700$ MHz. These requirements apply for all values of an adjacent channel interferer in case 1 and for any SCS specified for the channel bandwidth of the wanted signal. The lower and upper range of test parameters are chosen as in Table 7.5-2 and Table 7.5-3 for verification of the requirements specified in Table 7.5-1. For these test parameters, the throughput shall be $\geq 95$ % of the maximum throughput of the reference measurement channels as specified in 3GPP TS 38.101-1 [5] Annexes A.2.2 and A.3.2 (with one sided dynamic OCNG Pattern OP.1 FDD for the DL-signal as described in 3GPP TS 38.101-1 [5] Annex A.5.1.1). + +**Table 7.5-1: ACS for NR satellite bands with $F_{\text{DL\_high}} < 2700$ MHz and $F_{\text{UL\_high}} < 2700$ MHz** + +| RX parameter | Units | Channel bandwidth (MHz) | | | +|--------------|-------|-------------------------|----|----| +| | | 5, 10 | 15 | 20 | +| ACS | dB | 33 | 30 | 27 | + +**Table 7.5-2: Test parameters for NR bands with $F_{\text{DL\_high}} < 2700$ MHz and $F_{\text{UL\_high}} < 2700$ MHz, case 1** + +| RX parameter | Units | Channel bandwidth (MHz) | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|------------------------------------------------------------------------|-------------------|----------------|--|--|--| +| | | 5, 10 | 15 | 20 | | | | +| Power in transmission bandwidth configuration | dBm | REFSENS + 14 dB | | | | | | +| $P_{\text{interferer}}^4$ | dBm | REFSENS + 45.5 dB | REFSENS + 42.5 dB | REFSENS + 39.5 | | | | +| $BW_{\text{interferer}}$ | MHz | 5 | | | | | | +| $F_{\text{interferer}}$ (offset) 2 | MHz | $BW_{\text{Channel}}/2 + 2.5$
/
$-(BW_{\text{Channel}}/2 + 2.5)$ | | | | | | +| NOTE 1: The transmitter shall be set to 4 dB below $P_{\text{CMAX\_L,f,c}}$ at the minimum UL configuration specified in clause 7.3.2 with $P_{\text{CMAX\_L,f,c}}$ defined in clause 6.2.4. | | | | | | | | +| NOTE 2: The absolute value of the interferer offset $F_{\text{interferer}}$ (offset) shall be further adjusted to $(\lceil F_{\text{interferer}} / SCS \rceil + 0.5) SCS$ MHz with SCS the sub-carrier spacing of the wanted signal in MHz. The interferer is an NR signal with 15 kHz SCS. | | | | | | | | +| NOTE 3: The interferer consists of the NR interferer RMC specified in 3GPP TS 38.101-1 [5] Annex A.3.2.2 with one sided dynamic OCNG Pattern OP.1 FDD for the DL-signal as described in 3GPP TS 38.101-1 [5] Annex A.5.1.1. | | | | | | | | +| NOTE 4: $P_{\text{interferer}}$ shall be rounded to the next higher 0.5dB value. | | | | | | | | + +**Table 7.5-3: Test parameters for NR bands with $F_{DL\_high} < 2700$ MHz and $F_{UL\_high} < 2700$ MHz, case 2** + +| RX parameter | Units | Channel bandwidth (MHz) | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|----------------------------------------------------------|-------|-------|--|--|--| +| | | 5, 10 | 15 | 20 | | | | +| Power in transmission bandwidth configuration | dBm | -71.5 | -68.5 | -65.5 | | | | +| $P_{interferer}$ | dBm | -40 | | | | | | +| $BW_{interferer}$ | MHz | 5 | | | | | | +| $F_{interferer}$ (offset) | MHz | $BW_{Channel}/2 + 2.5$
/
$-(BW_{Channel}/2 + 2.5)$ | | | | | | +| NOTE 1: The transmitter shall be set to 24 dB below $P_{CMAX\_L,f,c}$ at the minimum UL configuration specified in clause 7.3.2 with $P_{CMAX\_L,f,c}$ defined in clause 6.2.4. | | | | | | | | +| NOTE 2: The absolute value of the interferer offset $F_{interferer}$ (offset) shall be further adjusted to $(\lceil F_{interferer} / SCS \rceil + 0.5) SCS$ MHz with SCS the sub-carrier spacing of the wanted signal in MHz. The interferer is an NR signal with 15 kHz SCS. | | | | | | | | +| NOTE 3: The interferer consists of the NR interferer RMC specified in 3GPP TS 38.101-1 [5] Annex A.3.2.2 with one sided dynamic OCNG Pattern OP.1 FDD for the DL-signal as described in 3GPP TS 38.101-1 [5] Annex A.5.1.1. | | | | | | | | +| NOTE 4: $P_{interferer}$ shall be rounded to the next higher 0.5dB value. | | | | | | | | + +## 7.6 Blocking characteristics + +### 7.6.1 General + +The blocking characteristic is a measure of the receiver's ability to receive a wanted signal at its assigned channel frequency in the presence of an unwanted interferer on frequencies other than those of the spurious response or the adjacent channels, without this unwanted input signal causing a degradation of the performance of the receiver beyond a specified limit. The blocking performance shall apply at all frequencies except those at which a spurious response occurs. + +### 7.6.2 In-band blocking + +For NR satellite bands with $F_{DL\_high} < 2700$ MHz and $F_{UL\_high} < 2700$ MHz in-band blocking (IBB) is defined for an unwanted interfering signal falling into the UE receive band or into the first 15 MHz below or above the UE receive band. + +The throughput of the wanted signal shall be $\geq 95$ % of the maximum throughput of the reference measurement channels as specified in 3GPP TS 38.101-1 [5] Annexes A.2.2 and A.3.2 (with one sided dynamic OCNG Pattern OP.1 FDD for the DL-signal as described in Annex A.5.1.1) with parameters specified in Table 7.6.2-1 and Table 7.6.2-2. The relative throughput requirement shall be met for any SCS specified for the channel bandwidth of the wanted signal. + +**Table 7.6.2-1: In-band blocking parameters for NR satellite bands with $F_{DL\_high} < 2700$ MHz and $F_{UL\_high} < 2700$ MHz** + +| RX parameter | Units | Channel bandwidth (MHz) | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------------------------|----------------|----------------|--|--|--| +| | | 5, 10 | 15 | 20 | | | | +| Power in transmission bandwidth configuration 3 | dBm | REFSENS + 6 dB | REFSENS + 7 dB | REFSENS + 9 dB | | | | +| $BW_{interferer}$ | MHz | 5 | | | | | | +| $F_{offset}$ , case 1 | MHz | 7.5 | | | | | | +| $F_{offset}$ , case 2 | MHz | 12.5 | | | | | | +| NOTE 1: The transmitter shall be set to 4 dB below $P_{CMAX\_L,f,c}$ at the minimum UL configuration specified in clause 7.3.2 with $P_{CMAX\_L,f,c}$ defined in clause 6.2.4. | | | | | | | | +| NOTE 2: The interferer consists of the RMC specified in 3GPP TS 38.101-1 [5] Annex A.3.2.2 with one sided dynamic OCNG Pattern OP.1 FDD for the DL-signal as described in Annex A.5.1.1 and 15 kHz SCS. | | | | | | | | +| NOTE 3: Power in transmission bandwidth configuration shall be rounded to the next higher 0.5dB value. | | | | | | | | + +**Table 7.6.2-2: In-band blocking for NR satellite bands with $F_{DL\_high} < 2700$ MHz and $F_{UL\_high} < 2700$ MHz** + +| Operating Band | Parameter | Unit | Case 1 | Case 2 | +|------------------------|---------------------------|------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------| +| | $P_{interferer}$ | dBm | -56 | -44 | +| n254,
n255,
n256 | $F_{interferer}$ (offset) | MHz | $-BW_{Channel}/2 - F_{Ioffset, case 1}$
and
$BW_{Channel}/2 + F_{Ioffset, case 1}$ | $\leq -BW_{Channel}/2 - F_{Ioffset, case 2}$
and
$\geq BW_{Channel}/2 + F_{Ioffset, case 2}$ | +| | $F_{interferer}$ | MHz | NOTE 2 | $F_{DL\_low} - 15$
to
$F_{DL\_high} + 15$ | + +NOTE 1: The absolute value of the interferer offset $F_{interferer}$ (offset) shall be further adjusted to $(\lceil |F_{interferer}| / SCS \rceil + 0.5) SCS$ MHz with SCS the sub-carrier spacing of the wanted signal in MHz. The interferer is an NR signal with 15 kHz SCS. + +NOTE 2: For each carrier frequency, the requirement applies for two interferer carrier frequencies: a: $-BW_{Channel}/2 - F_{Ioffset, case 1}$ ; b: $BW_{Channel}/2 + F_{Ioffset, case 1}$ + +### 7.6.3 Out-of-band blocking + +For NR satellite bands with $F_{DL\_high} < 2700$ MHz and $F_{UL\_high} < 2700$ MHz out-of-band band blocking is defined for an unwanted CW interfering signal falling outside a frequency range 15 MHz below or above the UE receive band. + +The throughput of the wanted signal shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in 3GPP TS 38.101-1 [5] Annexes A.2.2 and A.3.2 (with one sided dynamic OCNG Pattern OP.1 FDD for the DL-signal as described in Annex A.5.1.1) with parameters specified in Table 7.6.3-1 and Table 7.6.3-2. The relative throughput requirement shall be met for any SCS specified for the channel bandwidth of the wanted signal. + +**Table 7.6.3-1: Out-of-band blocking parameters for NR satellite bands with $F_{DL\_high} < 2700$ MHz and $F_{UL\_high} < 2700$ MHz** + +| RX parameter | Units | Channel bandwidth (MHz) | | | +|------------------------------------------------------------|-------|-------------------------|----------------|----------------| +| | | 5, 10 | 15 | 20 | +| Power in transmission bandwidth configuration 2 | dBm | REFSENS + 6 dB | REFSENS + 7 dB | REFSENS + 9 dB | + +NOTE 1: The transmitter shall be set to 4 dB below $P_{MAX\_L,f,c}$ at the minimum UL configuration specified in clause 7.3.2 with $P_{MAX\_L,f,c}$ defined in clause 6.2.4. + +NOTE 2: Power in transmission bandwidth configuration shall be rounded to the next higher 0.5dB value. + +**Table 7.6.3-2: Out of-band blocking for NR satellite bands with $F_{DL\_high} < 2700$ MHz and $F_{UL\_high} < 2700$ MHz** + +| Operating Band | Parameter | Unit | Range 1 | Range 2 | Range 3 | +|-------------------|-----------------------|------|----------------------------------------------------------------------|-----------------------------------------------------------------------------|----------------------------------------------------------------------------------| +| | $P_{interferer}$ | dBm | -44 | -30 | -15 | +| n254 2 | $F_{interferer}$ (CW) | MHz | $-60 < f - F_{DL\_low} < -15$
or
$15 < f - F_{DL\_high} < 60$ | $-85 < f - F_{DL\_low} \leq -60$
or
$60 \leq f - F_{DL\_high} < 85$ | $1 \leq f \leq F_{DL\_low} - 85$
or
$F_{DL\_high} + 85 \leq f \leq 12750$ | +| n255 | $F_{interferer}$ (CW) | MHz | $-60 < f - F_{DL\_low} < -15$
or
$15 < f - F_{DL\_high} < 60$ | $-85 < f - F_{DL\_low} \leq -60$
or
$60 \leq f - F_{DL\_high} < 85$ | $1 \leq f \leq F_{DL\_low} - 85$
or
$F_{DL\_high} + 85 \leq f \leq 12750$ | +| n256 1 | $F_{interferer}$ (CW) | MHz | $-100 < f - F_{DL\_low} < -15$
or
$15 < f - F_{DL\_high} < 60$ | $-145 < f - F_{DL\_low} \leq -100$
or
$60 \leq f - F_{DL\_high} < 85$ | $1 \leq f \leq F_{DL\_low} - 145$
or
$F_{DL\_high} + 85 \leq f \leq 12750$ | + +NOTE 1: Band n256 lower frequency ranges are modified to enable specific implementations +NOTE 2: Band n254 power level of the interferer ( $P_{interferer}$ ) for Range 3 shall be modified to -20 dBm for $F_{interferer} > 2585$ MHz and $F_{interferer} < 2775$ MHz. +NOTE 3: void +NOTE 4: void + +For interferer frequencies across ranges 1, 2 and 3 in Table 7.6.3-1, a maximum of + +$$\lfloor \max \{24, 6 \cdot \lceil n \cdot N_{RB} / 6 \rceil\} / \min \{\lceil n \cdot N_{RB} / 10 \rceil, 5\} \rfloor$$ + +exceptions are allowed for spurious response frequencies in each assigned frequency channel when measured using a step size of $\min(\lceil BW_{channel} / 2 \rceil, 5)$ MHz with $N_{RB}$ the number of resource blocks in the downlink transmission bandwidth configuration, $BW_{channel}$ the bandwidth of the frequency channel in MHz and $n = 1, 2, 3$ for SCS = 15, 30, 60 kHz, respectively. For these exceptions, the requirements in clause 7.7 apply. + +### 7.6.4 Narrow band blocking + +This requirement is measure of a receiver's ability to receive a NR signal at its assigned channel frequency in the presence of an unwanted narrow band CW interferer at a frequency, which is less than the nominal channel spacing. The relative throughput shall be $\geq 95$ % of the maximum throughput of the reference measurement channels as specified in 3GPP TS 38.101-1 [5] Annexes A.2.2 and A.3.2 (with one sided dynamic OCNNG Pattern OP.1 FDD for the DL-signal as described in Annex A.5.1.1) with parameters specified in Table 7.6.4-1. + +**Table 7.6.4-1: Narrow Band Blocking** + +| Operating Band | Parameter | Unit | Channel Bandwidth (MHz) | | | | +|------------------------|--------------------------------------------|------|------------------------------------------------------------------------------------|----|----|----| +| | | | 5 | 10 | 15 | 20 | +| n254,
n255,
n256 | $P_w$ | dBm | $P_{REFSENS} + \text{channel-bandwidth specific value below}$ | | | | +| | | | 16 | 13 | 14 | 16 | +| | $P_{uw}$ (CW) | dBm | -55 | | | | +| | $F_{uw}$ (offset SCS= 15 kHz) 3 | MHz | $\left( \left( \frac{BW_{channel}}{2} + 0.2}{SCS} + 0.5 \right) + 0.5 \right) SCS$ | | | | +| | $F_{uw}$ (offset SCS= 30 kHz) 3 | MHz | NA | | | | + +NOTE 1: The transmitter shall be set a 4 dB below $P_{CMAX\_L,f,c}$ at the minimum UL configuration specified in clause 7.3.2 with $P_{CMAX\_L,f,c}$ defined in clause 6.2.4 +NOTE 2: The $P_{REFSENS}$ power level is specified in clause 7.3.2. +NOTE 3: $F_{uw}$ shall be rounded to half of SCS. + +## 7.7 Spurious response + +Spurious response is a measure of the ability of the receiver to receive a wanted signal on its assigned channel frequency without exceeding a given degradation due to the presence of an unwanted CW interfering signal at any other frequency for which a response is obtained, i.e. for which the out-of-band blocking limit as specified in clause 7.6.3 is not met. + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channels as specified in 3GPP TS 38.101-1 [5] Annexes A.2.2 and A.3.2 (with one sided dynamic OCNG Pattern OP.1 FDD for the DL-signal as described in Annex A.5.1.1) with parameters for the wanted signal as specified in Table 7.7-1 for NR bands with $F_{DL\_high} < 2700$ MHz and $F_{UL\_high} < 2700$ MHz for the interferer as specified in Table 7.7-2. The relative throughput requirement shall be met for any SCS specified for the channel bandwidth of the wanted signal. + +**Table 7.7-1: Spurious response parameters for NR bands with $F_{DL\_high} < 2700$ MHz and $F_{UL\_high} < 2700$ MHz** + +| RX parameter | Units | Channel bandwidth (MHz) | | | +|------------------------------------------------------------|-------|-------------------------|----------------|----------------| +| | | 5, 10 | 15 | 20 | +| Power in transmission bandwidth configuration 2 | dBm | REFSENS + 6 dB | REFSENS + 7 dB | REFSENS + 9 dB | + +NOTE 1: The transmitter shall be set to 4 dB below $P_{CMAX\_L,f,c}$ at the minimum UL configuration specified in Table 7.3.2-3 with $P_{CMAX\_L,f,c}$ defined in clause 6.2.4. + +NOTE 2: Power in transmission bandwidth configuration value is rounded to the next higher 0.5dB value. + +**Table 7.7-2: Spurious response** + +| Parameter | Unit | Level | +|-----------------------|------|-------------------------------| +| $P_{Interferer}$ (CW) | dBm | -44 | +| $F_{Interferer}$ | MHz | Spurious response frequencies | + +## 7.8 Intermodulation characteristics + +The definition and requirements for intermodulation characteristics specified in 3GPP TS 38.101-1 [5] clause 7.8 shall apply for NTN satellite UE. + +## 7.9 Spurious emissions + +The spurious emissions power is the power of emissions generated or amplified in a receiver that appear at the UE antenna connector. + +The power of any narrow band CW spurious emission shall not exceed the maximum level specified in Table 7.9-1 + +**Table 7.9-1: General receiver spurious emission requirements** + +| Frequency range | Measurement bandwidth | Maximum level | NOTE | +|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|---------------|------| +| $30\text{ MHz} \leq f < 1\text{ GHz}$ | 100 kHz | -57 dBm | | +| $1\text{ GHz} \leq f \leq 12.75\text{ GHz}$ | 1 MHz | -47 dBm | | +| NOTE: | Unused PDCCH resources are padded with resource element groups with power level given by PDCCH as defined in 3GPP TS 38.101-1 [5] Annex C.3.1. | | | + +# 8 Conducted performance requirements + +## 8.1 General + +### 8.1.1 Relationship between minimum requirements and test requirements + +The present document is a Single-RAT and interwork specification for NR UE, covering minimum performance requirements of both conducted and radiated requirements. Conformance to the present specification is demonstrated by fulfilling the test requirements specified in the conformance specification TS TBD [TBD]. + +The Minimum Requirements given in this specification make no allowance for measurement uncertainty. The test specification TS TBD [TBD] defines test tolerances. These test tolerances are individually calculated for each test. The test tolerances are used to relax the minimum requirements in this specification to create test requirements. + +The measurement results returned by the test system are compared – without any modification – against the test requirements as defined by the shared risk principle. + +The shared risk principle is defined in Recommendation ITU-R M.1545 [TBD]. + +The applicability of each requirement is described under each sub-clause in [8.2.1] and [8.3.1]. + +### 8.1.2 Applicability of minimum requirements + +The conducted minimum requirements specified in this specification shall be met in all applicable scenarios for FR1. + +Unless otherwise stated, all minimum performance requirements defined in Clauses 8 are applicable to UE power class 3 only. + +### 8.1.3 Conducted requirements + +#### 8.1.3.1 Introduction + +The requirements are defined for the following modes: + +- Mode 1: Conditions with external noise source + - Wanted signal with power level $E_s$ is transmitted. + - External white noise source with power spectral density $N_{oc}$ is used. + - $E_s$ and $N_{oc}$ levels are selected to achieve target SNR as described in Clause 8.1.3.3. + +#### 8.1.3.2 Reference point + +The reference point for SNR, $E_s$ and $N_{oc}$ of DL signal is the UE antenna connector or connectors. + +#### 8.1.3.3 SNR definition + +For Mode 1 conditions conducted UE demodulation and CSI requirements the SNR is defined as: + +$$SNR = \frac{\sum_{j=1}^{N_{RX}} E_s^{(j)}}{\sum_{j=1}^{N_{RX}} N_{oc}^{(j)}}$$ + +Where + +- $N_{RX}$ denotes the number of receiver antenna connectors and the superscript receiver antenna connector $j$ . + +- The above SNR definition assumes that the REs are not precoded, and does not account for any gain which can be associated to the precoding operation. +- Unless otherwise stated, the SNR refers to the SSS wanted signal. +- 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 power ratio of other wanted signals to the SSS is defined in clause [C.3.1]. + +#### 8.1.3.4 Noc + +##### 8.1.3.4.1 Introduction + +This clause describes the Noc power level for Mode 1 conditions conducted testing of demodulation and CSI requirements. + +##### 8.1.3.4.2 Noc for NR operating bands in FR1 + +The Noc power spectrum density shall be larger or equal to the minimum Noc power level for each operating band supported by the UE as defined in clause 8.1.3.4.2.1. + +Unless otherwise stated, a fixed Noc power level of -145 dBm/Hz shall be used for all operating bands. + +###### 8.1.3.4.2.1 Derivation of Noc values for NR operating bands in FR1 + +The minimum Noc power level for an operating band, subcarrier spacing and channel bandwidth is derived based on the following equation: + +$$Noc_{Band\_X, SCS\_Y, CBW\_Z} = REFSENS_{Band\_X, SCS\_Y, CBW\_Z} - 10 \cdot \log_{10}(12 \cdot SCS\_Y \cdot nPRB) + D - SNR_{REFSENS} + \Delta_{thermal}$$ + +where + +- $REFSENS_{Band\_X, SCS\_Y, CBW\_Z}$ is the REFSENS value in dBm for Band X, SCS Y and CBW Z specified in Table 7.3.2-1 of TS 38.101-5 [TBD] +- 12 is the number of subcarriers in a PRB +- SCS Y is the subcarrier spacing associated with the REFSENS value +- nPRB is the maximum number of PRB for SCS Y and CBW Z associated with the REFSENS value, and is specified in Table 5.3.2-1 of TS 38.101-5 [TBD] +- D is diversity gain equal to 3 dB +- $SNR_{REFSENS} = -1$ dB is the SNR used for simulation of REFSENS +- $\Delta_{thermal}$ is the amount of dB that the wanted noise is set above UE thermal noise, giving a defined rise in total noise. $\Delta_{thermal} = 16$ dB, giving a rise in total noise of 0.1dB, regarded as insignificant. + +The calculated Noc value for the baseline of Band n256, 15 kHz SCS, 10 MHz CBW is -146.5 dBm/Hz. + +An allowance of 1.5dB is made for future bands, giving an Noc power level of -145 dBm/Hz. + +## 8.2 Demodulation performance requirements + +### 8.2.1 General + +#### 8.2.1.1 Applicability of requirements + +##### 8.2.1.1.1 General + +The minimum performance requirements are applicable to all FR1 operating bands defined in clause 5.2. + +If same test is listed for different UE features/capabilities in Clauses 8.2.1.1.2, then this test shall apply for UEs which support all corresponding UE features/capabilities. + +##### 8.2.1.1.2 Applicability of requirements for optional UE features + +The performance requirements in Table 8.2.1.1.2-1 shall apply for UEs which support optional UE features only. + +**Table 8.2.1.1.2-1: Requirements applicability for optional UE features** + +| UE feature/capability [TBD] | Test type | | Test list | Applicability notes | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-------|-------------------------------------------------------------|-------------------------------------------------------------------------------------------------| +| | | | | | +| NR NTN access (nonTerrestrialNetwork-r17) | FR1 FDD | PDSCH | Clause 8.2.1.2.2.1 (Test 1-1, Test 1-2, Test 1-3, Test 1-4) | | +| NR NTN scenario support (ntn-ScenarioSupport-r17) | FR1 FDD | PDSCH | Clause 8.2.1.2.2.1 (Test 1-1, Test 1-2, Test 1-3, Test 1-4) | The requirements apply only when ntn-ScenarioSupport-r17 is “ngso” or is not configured. | +| Increasing the number of HARQ processes (max-HARQ-ProcessNumber-r17) | FR1 FDD | PDSCH | Clause 8.2.1.2.2.1 (Test 1-3) | | +| Disabled HARQ feedback for downlink transmission (harq-FeedbackDisabled-r17) | FR1 FDD | PDSCH | Clause 8.2.1.2.2.1 (Test 1-4) | | +| Note: For UE supporting NR NTN access (nonTerrestrialNetwork-r17), the requirements in TS38.101-4 also applies to UE according to applicability rules in TS38.101-4 Clause 5.1, 6.1, 7.1 and 8.1 | | | | | + +#### 8.2.1.2 PDSCH demodulation requirements + +The parameters specified in Table 8.2.1.2-1 are valid for all PDSCH tests unless otherwise stated. + +**Table 8.2.1.2-1: Common test parameters** + +| Parameter | | Unit | Value | +|--------------------------------|----------------------------------------------------------------------------------|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PDSCH transmission scheme | | | Transmission scheme 1 | +| Carrier configuration | Offset between Point A and the lowest usable subcarrier on this carrier (Note 2) | RBs | 0 | +| | Subcarrier spacing | kHz | 15 | +| DL BWP configuration #1 | Cyclic prefix | | Normal | +| | RB offset | RBs | 0 | +| | Number of contiguous PRB | PRBs | Maximum transmission bandwidth configuration as specified in clause 5.3.2 of TS 38.101-1 [6] for tested channel bandwidth and subcarrier spacing | +| Common serving cell parameters | Physical Cell ID | | 0 | +| | SSB position in burst | | First SSB in Slot #0 | +| | SSB periodicity | ms | 20 | +| PDCCH configuration | Slots for PDCCH monitoring | | Each slot | +| | Symbols with PDCCH | Symbols | 0, 1 | +| | Number of PRBs in CORESET | | Table 5.2-2 of 38.101-4 for tested channel bandwidth and subcarrier spacing | +| | Number of PDCCH candidates and aggregation levels | | 1/AL8 | +| | CCE-to-REG mapping type | | Non-interleaved | +| | DCI format | | 1_1 | +| | TCI state | | TCI state #1 | +| | PDCCH & PDCCH DMRS Precoding configuration | | Single Panel Type I, Random per slot with equal probability of each applicable $i_1, i_2$ combination, and with REG bundling granularity for number of Tx larger than 1 | +| Cross carrier scheduling | | | Not configured | +| CSI-RS for tracking | First subcarrier index in the PRB used for CSI-RS | | $k_0=0$ for CSI-RS resource 1,2,3,4 | +| | First OFDM symbol in the PRB used for CSI-RS | | $l_0 = 6$ for CSI-RS resource 1 and 3
$l_0 = 10$ for CSI-RS resource 2 and 4 | +| | Number of CSI-RS ports (X) | | 1 for CSI-RS resource 1,2,3,4 | +| | CDM Type | | 'No CDM' for CSI-RS resource 1,2,3,4 | +| | Density (p) | | 3 for CSI-RS resource 1,2,3,4 | +| | CSI-RS periodicity | Slots | 15 kHz SCS: 20 for CSI-RS resource 1,2,3,4 | +| | CSI-RS offset | Slots | 15 kHz SCS:
10 for CSI-RS resource 1 and 2
11 for CSI-RS resource 3 and 4 | +| | Frequency Occupation | | Start PRB 0
Number of PRB = $\text{ceil}(\text{BWP size}/4)*4$ | +| | QCL info | | TCI state #0 | +| NZP CSI-RS for CSI acquisition | Row index (Note 3) | | 3 for 2 CSI-RS ports and 5 for 4 CSI-RS ports | +| | First subcarrier index in the PRB used for CSI-RS | | $k_0 = 0$ | +| | First OFDM symbol in the PRB used for CSI-RS | | $l_0 = 12$ | +| | Number of CSI-RS ports (X) | | Same as number of transmit antenna | +| | CDM Type | | 'No CDM' for 1 transmit antenna
'FD-CDM2' for 2 and 4 transmit antenna | +| | Density (p) | | 1 | +| | CSI-RS periodicity | Slots | 15 kHz SCS: 20 | +| | CSI-RS offset | Slots | 0 | +| | Frequency Occupation | | Start PRB 0
Number of PRB = $\text{ceil}(\text{BWP size}/4)*4$ | +| | QCL info | | TCI state #1 | +| ZP CSI-RS for CSI acquisition | Row index (Note 3) | | 5 | +| | First subcarrier index in the PRB used for CSI-RS | | $k_0 = 4$ | +| | First OFDM symbol in the PRB used for CSI-RS | | $l_0 = 12$ | + +| | | | | +|-----------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Number of CSI-RS ports (X) | | 4 | +| | CDM Type | | 'FD-CDM2' | +| | Density (p) | | 1 | +| | CSI-RS periodicity | Slots | 15 kHz SCS: 20 | +| | CSI-RS offset | Slots | 0 | +| | Frequency Occupation | | Start PRB 0
Number of PRB = $\text{ceil}(\text{BWP size}/4)*4$ | +| PDSCH DMRS configuration | Antenna ports indexes | | {1000} for Rank 1 tests | +| | Position of the first DMRS for PDSCH mapping type A | | 2 | +| | Number of PDSCH DMRS CDM group(s) without data | | 1 for Rank 1 | +| TCI state #0 | Type 1 QCL information | SSB index | SSB #0 | +| | | QCL Type | Type C | +| | Type 2 QCL information | SSB index | N/A | +| | | QCL Type | N/A | +| TCI state #1 | Type 1 QCL information | CSI-RS resource | CSI-RS resource 1 from 'CSI-RS for tracking' configuration | +| | | QCL Type | Type A | +| | Type 2 QCL information | CSI-RS resource | N/A | +| | | QCL Type | N/A | +| PT-RS configuration | | | PT-RS is not configured | +| Maximum number of code block groups for ACK/NACK feedback | | | 1 | +| Maximum number of HARQ transmission | | | 4 | +| HARQ ACK/NACK bundling | | | Multiplexed | +| Redundancy version coding sequence | | | {0,2,3,1} | +| PDSCH & PDSCH DMRS Precoding configuration | | | Single Panel Type I, Random precoder selection updated per slot, with equal probability of each applicable $i_1, i_2$ combination, and with PRB bundling granularity | +| Symbols for all unused REs | | | OP.1 FDD as defined in Annex A.5.1.1 of 38.101-4 | +| Physical signals, channels mapping and precoding | | | As specified in Annex B.4.1 of 38.101-4 | +| Note 1: | UE assumes that the TCI state for the PDSCH is identical to the TCI state applied for the PDCCH transmission. | | | +| Note 2: | Point A coincides with minimum guard band as specified in Table 5.3.3-1 from TS 38.101-1 [6] for tested channel bandwidth and subcarrier spacing. | | | +| Note 3: | Refer to Table 7.4.1.5.3-1 in [9] | | | + +##### 8.2.1.2.1 1RX requirements + +##### 8.2.1.2.2 2RX requirements + +###### 8.2.1.2.2.1 FDD + +###### 8.2.1.2.2.1.1 Minimum requirements for PDSCH Mapping Type A + +The performance requirements are specified in Table 8.2.1.2.2.1.1-3 with the addition of test parameters in Table 8.2.1.2.2.1.1-2 and the downlink physical channel setup according to Annex A.3. + +The test purposes are specified in Table 8.2.1.2.2.1.1-1. + +**Table 8.2.1.2.2.1.1-1: Tests purpose** + +| Purpose | Test index | +|---------------------------------------------------------------------------------------------------------------------------------|--------------------| +| Verify the PDSCH mapping Type A normal performance under 2 receive antenna conditions and with different channel models and MCS | 1-1, 1-2, 1-3, 1-4 | + +Table 8.2.1.2.2.1.1-2: Test parameters + +| Parameter | | Unit | Value | +|--------------------------------------------------------------------------|---------------------------------------------------------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Duplex mode | | | FDD | +| Active DL BWP index | | | 1 | +| PDSCH configuration | Mapping type | | Type A | +| | k0 | | 0 | +| | Starting symbol (S) | | 2 | +| | Length (L) | | 12 | +| | PDSCH aggregation factor | | 1 | +| | PRB bundling type | | Static | +| | PRB bundling size | | 2 | +| | Resource allocation type | | Type 0 | +| | RBG size | | Config2 | +| | VRB-to-PRB mapping type | | Non-interleaved | +| PDSCH DMRS configuration | DMRS Type | | Type 1 | +| | Number of additional DMRS | | 1 | +| | Maximum number of OFDM symbols for DL front loaded DMRS | | 1 | +| CSI-RS for tracking | CSI-RS periodicity | Slots | 20 for CSI-RS resource 1,2,3,4. | +| | CSI-RS offset | Slots | 10 for CSI-RS resource 1 and 2
11 for CSI-RS resource 3 and 4. | +| Number of HARQ Processes | | | 16 for Test 1-1, Test 1-2
32 for Test 1-3
4 with feedback disabled, 12 with feedback enabled in 16 HARQ processes with re-Tx disable for all HARQ for Test 1-4 in which 4 disabled processes are randomly select at test configuration | +| The number of slots between PDSCH and corresponding HARQ-ACK information | | | 10 for Test 1-1, Test 1-2, Test 1-3
N/A for Test 1-4 | +| Maximum number of HARQ transmission | | | 4 for Test 1-1, Test 1-2, Test 1-3
Disabled for all HARQ processes for Test 1-4 | + +Table 8.2.1.2.2.1.1-3: Minimum performance for Rank 1 + +| Test num. | Reference channel | Bandwidth (MHz) / Subcarrier spacing (kHz) | Modulation format and code rate | Propagation condition | Correlation matrix and antenna configuration | Reference value | | +|-----------|-------------------|--------------------------------------------|---------------------------------|-----------------------|----------------------------------------------|------------------------------------|----------| +| | | | | | | Fraction of maximum throughput (%) | SNR (dB) | +| 1-1 | R.PDSCH.1-1.1 FDD | 10 / 15 | QPSK, 0.30 | NTN-TDL100-200 | 1x2, ULA Low | 70 | 0.3 | +| 1-2 | R.PDSCH.1-2.1 FDD | 10 / 15 | 16QAM, 0.48 | NTN-TDLC5-200 | 1x2, ULA Low | 70 | 7.6 | +| 1-3 | R.PDSCH.1-1.1 FDD | 10 / 15 | QPSK, 0.30 | NTN-TDLC5-200 | 1x2, ULA Low | 70 | -0.4 | +| 1-4 | R.PDSCH.1-1.1 FDD | 10 / 15 | QPSK, 0.30 | NTN-TDL100-200 | 1x2, ULA Low | 70* | 1.1 | + +## 8.3 CSI reporting requirements + +[To be updated] + + + +# Annex A (normative): Measurement channels + +## A.1 General + +### A.1.1 Throughput definition + +The throughput values defined in the measurement channels specified in Annex A, are calculated and are valid per codeword. For multi-codeword transmissions, the throughput referenced in the minimum requirements is the sum of throughputs of all codewords. + +## --- A.2 UL reference measurement channels + +## --- A.3 DL reference measurement channels + +### A.3.1 General + +The transport block size (TBS) determination procedure is described in clause 5.1.3.2 of TS 38.214 [12]. + +Unless otherwise stated, no user data is scheduled on slot #0 within 20 ms in order to avoid SSB and PDSCH transmissions in one slot and simplify test configuration. + +### A.3.2 Reference measurement channels for PDSCH performance requirements + +For PDSCH reference channels if more than one Code Block is present, an additional CRC sequence of $L = 24$ Bits is attached to each Code Block (otherwise $L = 0$ Bit). + +#### A.3.2.1 FDD + +##### A.3.2.1.1 Reference measurement channels for SCS 15 kHz FR1 + +**Table A.3.2.1.1-1: PDSCH Reference Channel for FDD (QPSK)** + +| Parameter | Unit | Value | | | | | +|------------------------------------------------------------------------|-------|-------------------|--|--|--|--| +| Reference channel | | R.PDSCH.1-1.1 FDD | | | | | +| Channel bandwidth | MHz | 10 | | | | | +| Subcarrier spacing | kHz | 15 | | | | | +| Number of allocated resource blocks | PRBs | 52 | | | | | +| Number of consecutive PDSCH symbols | | 12 | | | | | +| Allocated slots per 2 frames | Slots | 19 | | | | | +| MCS table | | 64QAM | | | | | +| MCS index | | 4 | | | | | +| Modulation | | QPSK | | | | | +| Target Coding Rate | | 0.30 | | | | | +| Number of MIMO layers | | 1 | | | | | +| Number of DMRS REs | | 12 | | | | | +| Overhead for TBS determination | | 0 | | | | | +| Information Bit Payload per Slot | | | | | | | +| For Slot i = 0 | Bits | N/A | | | | | +| For Slots i = 1, ..., 19 | Bits | 4096 | | | | | +| Transport block CRC per Slot | | | | | | | +| For Slot i = 0 | Bits | N/A | | | | | +| For Slots i = 1, ..., 19 | Bits | 24 | | | | | +| Number of Code Blocks per Slot | | | | | | | +| For Slot i = 0 | CBs | N/A | | | | | +| For Slots i = 1, ..., 19 | CBs | 1 | | | | | +| Binary Channel Bits Per Slot | | | | | | | +| For Slot i = 0 | Bits | N/A | | | | | +| For Slots i = 10, 11 | Bits | 13104 | | | | | +| For Slots i = 1, ..., 9, 12, ..., 19 | Bits | 13728 | | | | | +| Max. Throughput averaged over 2 frames | Mbps | 3.891 | | | | | +| Note 1: SS/PBCH block is transmitted in slot #0 with periodicity 20 ms | | | | | | | +| Note 2: Slot i is slot index per 2 frames | | | | | | | + +Table A.3.2.1.1-2: PDSCH Reference Channel for FDD (16QAM) + +| Parameter | Unit | Value | | | | | | +|------------------------------------------------------------------------|-------|-------------------|--|--|--|--|--| +| Reference channel | | R.PDSCH.1-2.1 FDD | | | | | | +| Channel bandwidth | MHz | 10 | | | | | | +| Subcarrier spacing | kHz | 15 | | | | | | +| Number of allocated resource blocks | PRBs | 52 | | | | | | +| Number of consecutive PDSCH symbols | | 12 | | | | | | +| Allocated slots per 2 frames | Slots | 19 | | | | | | +| MCS table | | 64QAM | | | | | | +| MCS index | | 13 | | | | | | +| Modulation | | 16QAM | | | | | | +| Target Coding Rate | | 0.48 | | | | | | +| Number of MIMO layers | | 1 | | | | | | +| Number of DMRS REs | | 12 | | | | | | +| Overhead for TBS determination | | 0 | | | | | | +| Information Bit Payload per Slot | | | | | | | | +| For Slot i = 0 | Bits | N/A | | | | | | +| For Slots i = 1, ..., 19 | Bits | 13064 | | | | | | +| Transport block CRC per Slot | | | | | | | | +| For Slot i = 0 | Bits | N/A | | | | | | +| For Slots i = 1, ..., 19 | Bits | 24 | | | | | | +| Number of Code Blocks per Slot | | | | | | | | +| For Slot i = 0 | CBs | N/A | | | | | | +| For Slots i = 1, ..., 19 | CBs | 2 | | | | | | +| Binary Channel Bits Per Slot | | | | | | | | +| For Slot i = 0 | Bits | N/A | | | | | | +| For Slots i = 10, 11 | Bits | 26208 | | | | | | +| For Slots i = 1, ..., 9, 12, ..., 19 | Bits | 27456 | | | | | | +| Max. Throughput averaged over 2 frames | Mbps | 12.411 | | | | | | +| Note 1: SS/PBCH block is transmitted in slot #0 with periodicity 20 ms | | | | | | | | +| Note 2: Slot i is slot index per 2 frames | | | | | | | | + +## A.4 Testing related to Satellite Access + +### A.4.1 General + +The following test conditions should be maintained for Satellite Access when test equipment emulates the snapshot of the satellite link channel. + +- The same ephemeris info will be maintained during each test. +- A set of ephemeris information are pre-defined for each satellite corresponding to respective epoch times in TS 38.508-1 [13]. +- The range of the selected constant delay shift is as follows: + - For NGSO an altitude of 600km and 1200km on a circular orbit are considered. The range of the one-way delay between UE and satellite is from 2ms (lowest value for LEO orbit 600km) to 6.67ms (highest value for LEO orbit 1200km). + - For GSO the range of the one-way delay from UE to satellite is within 119.375ms to 128.79ms. +- Constant delay value is derived from ephemeris info (SIB19) and UE location associated to zero Doppler or non-zero Doppler value under test. + +### A.4.2 Test condition for transmitter characteristics + +All requirements in section 6 for transmitter characteristics, other than frequency error in clause 6.4.1, shall be verified when Doppler conditions are set to zero and delay conditions are set to constant for all types of satellites. + +Frequency error requirement in clause 6.4.1 shall be verified for at least two cases: one with zero Doppler condition and the other with a constant Doppler shift where the range of the absolute value of Doppler is greater than zero and up to [0.93] ppm if the IE field *ntn-ScenarioSupport-r17* is present and indicated as GSO and up to 24 ppm if the IE field *ntn-ScenarioSupport-r17* is present and indicated as NGSO or only the IE field *nonTerrestrialNetwork-r17* is present. The delay condition is a constant. + +### A.4.3 Test condition for receiver characteristics + +All requirements in section 7 for receiver characteristics shall be verified when Doppler conditions are set to zero and delay conditions are set to constant for all types of satellites. + +### A.4.4 Test condition for performance requirements + +All requirements in section 8 for performance requirements shall be verified when Doppler conditions related to satellite motion for DL in service link are set to zero and delay conditions are set to constant for all types of NGSO satellites. + +The one-way delay between UE and satellite for NGSO at an altitude of 600km is 2ms. + +# --- Annex B (normative): Propagation conditions + +## B.1 Static propagation condition + +### B.1.1 UE Receiver with 1Rx + +For 2 port transmission the channel matrix is defined in the frequency domain by + +$$\mathbf{H} = \begin{bmatrix} 1 & 1 \end{bmatrix}.$$ + +### B.1.2 UE Receiver with 2Rx + +For 1 port transmission the channel matrix is defined in the frequency domain by + +$$\mathbf{H} = \begin{bmatrix} 1 \\ 1 \end{bmatrix}.$$ + +For 2 port transmission the channel matrix is defined in the frequency domain by + +$$\mathbf{H} = \begin{bmatrix} 1 & j \\ 1 & -j \end{bmatrix}.$$ + +## --- B.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. + +Initial channel matrix for LOS component of NTN-TDL-C channel model is equal to channel matrix of Static propagation conditions in Clause B.1. + +### B.2.1 Delay profiles + +The delay profiles are derived from the TR 38.811 [12] NTN-TDL models for the desired delay spread and tap resolution. After scaling the normalized delay spread values for each tap by the desired RMS delay spread, the tap delays are quantized to a delay resolution of 5ns by rounding to the nearest multiple of the delay resolution. + +**Table B.2.1-1: Delay profiles for NR NTN channel models** + +| Type | Model | Delay spread (r.m.s.) | Delay resolution | +|------|-------------|-----------------------|------------------| +| NLOS | NTN-TDLA100 | 100 ns | 5 ns | +| LOS | NTN-TDLC5 | 5 ns | 5 ns | + +**Table B.2.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 B.2.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 | + +Note 1: Tap #1 follows a Rician distribution. + +### B.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 B.2.2-1 show the propagation conditions that are used for the performance measurements in multi-path fading environment for NLOS and LOS propagation conditions. + +**Table B.2.2-1: Channel model parameters for NTN** + +| Combination name | Model | Maximum Doppler frequency | +|------------------|-------------|---------------------------| +| NTN-TDLA100-200 | NTN-TDLA100 | 200 Hz | +| NTN-TDLC5-200 | NTN-TDLC5 | 200 Hz | + +### B.2.3 MIMO Channel Correlation Matrices + +The MIMO channel correlation matrices defined in B.2.3 apply for the antenna configuration using uniform linear arrays at both gNB and UE. + +#### B.2.3.1 MIMO Correlation Matrices using Uniform Linear Array (ULA) + +The MIMO channel correlation matrices defined in B.2.3.1 apply for the antenna configuration using uniform linear array (ULA) at both gNB and UE. + +##### B.2.3.1.1 Definition of MIMO Correlation Matrices + +Table B.2.3.1.1-1 defines the correlation matrix for the gNB. + +**Table B.2.3.1.1-1: gNB correlation matrix** + +| | One antenna | Two antennas | +|-----------------|---------------|----------------------------------------------------------------------| +| gNB Correlation | $R_{gNB} = 1$ | $R_{gNB} = \begin{pmatrix} 1 & \alpha \\ \alpha^* & 1 \end{pmatrix}$ | + +Table B.2.3.1.1-2 defines the correlation matrix for the UE: + +**Table B.2.3.1.1-2: UE correlation matrix** + +| | One antenna | Two antennas | +|----------------|--------------|-------------------------------------------------------------------| +| UE Correlation | $R_{UE} = 1$ | $R_{UE} = \begin{pmatrix} 1 & \beta \\ \beta^* & 1 \end{pmatrix}$ | + +Table B.2.3.1.1-3 defines the channel spatial correlation matrix $R_{spat}$ . The parameters, $\alpha$ and $\beta$ in Table B.2.3.1.1-3 defines the spatial correlation between the antennas at the gNB and UE. + +**Table B.2.3.1.1-3: $R_{spat}$ correlation matrices** + +| | | +|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1x2 case | $R_{spat} = R_{UE} = \begin{bmatrix} 1 & \beta \\ \beta^* & 1 \end{bmatrix}$ | +| 2x1 case | $R_{spat} = R_{gNB} = \begin{bmatrix} 1 & \alpha \\ \alpha^* & 1 \end{bmatrix}$ | +| 2x2 case | $R_{spat} = R_{gNB} \otimes R_{UE} = \begin{bmatrix} 1 & \alpha \\ \alpha^* & 1 \end{bmatrix} \otimes \begin{bmatrix} 1 & \beta \\ \beta^* & 1 \end{bmatrix} = \begin{bmatrix} 1 & \beta & \alpha & \alpha\beta \\ \beta^* & 1 & \alpha\beta^* & \alpha \\ \alpha^* & \alpha^*\beta & 1 & \beta \\ \alpha^*\beta^* & \alpha^* & \beta^* & 1 \end{bmatrix}$ | + +##### B.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 B.2.3.1.2-1. + +**Table B.2.3.1.2-1: The $\alpha$ and $\beta$ parameters for ULA MIMO correlation matrices** + +| Correlation Model | $\alpha$ | $\beta$ | +|-------------------|----------|---------| +| Low correlation | 0 | 0 | + +The correlation matrices low correlation are defined in Table B.2.3.1.2-2 below. + +**Table B.2.3.1.2-2: MIMO correlation matrices for low correlation** + +| | | +|-----------------------------------------------------------|--------------------------| +| 1x2 case | $R_{low} = \mathbf{I}_2$ | +| 2x1 case | $R_{low} = \mathbf{I}_2$ | +| 2x2 case | $R_{low} = \mathbf{I}_4$ | +| Note: $\mathbf{I}_d$ is the $d \times d$ identity matrix. | | + +# --- Annex C (normative): Downlink physical channels + +## C.1 General + +This annex specifies the downlink physical channels that are needed for setting a connection and channels that are needed during a connection. + +## --- C.2 Setup (Conducted) + +Table C.2-1 describes the downlink Physical Channels that are required for connection set up. + +**Table C.2-1: Downlink Physical Channels required for connection set-up** + +| Physical Channel | +|------------------| +| PBCH | +| SSS | +| PSS | +| PDCCH | +| PDSCH | +| PBCH DMRS | +| PDCCH DMRS | +| PDSCH DMRS | +| CSI-RS | + +## --- C.3 Connection (Conducted) + +The following clauses, describes the downlink Physical Channels that are transmitted during a connection i.e., when measurements are done. + +### C.3.1 Measurement of Performance requirements + +Table C.3.1-1 is applicable for measurements in which uniform RS-to-EPRE boosting for all downlink physical channels, unless otherwise stated. + +**Table C.3.1-1: Downlink Physical Channels transmitted during a connection (FDD and TDD)** + +| Parameter | Unit | Value (Note 2) | +|-----------------------------------|------|-----------------------------------| +| SSS transmit power | W | Test specific | +| EPRE ratio of PSS to SSS | dB | 0 | +| EPRE ratio of PBCH to SSS | dB | 0 | +| EPRE ratio of PBCH to PBCH DMRS | dB | 0 | +| EPRE ratio of PDCCH to SSS | dB | 0 | +| EPRE ratio of PDCCH to PDCCH DMRS | dB | 0 | +| EPRE ratio of PDSCH to SSS | dB | 0 | +| EPRE ratio of PDSCH to PDSCH DMRS | dB | Test specific (Note 1) | +| EPRE ratio of CSI-RS to SSS | dB | $-10 \cdot \log_{10}(L)$ (Note 3) | +| EPRE ratio of OCNG to SSS | dB | 0 | +| EPRE ratio of PDCCH OCNG to SSS | dB | 0 | +| EPRE ratio of LTE CRS to NR SSS | dB | 0 (Note 4) | + +Note 1: Value is derived from Table 4.1-1 in TS 38.214 [12] based on "Number of DM-RS CDM groups without data" and "DMRS Type" parameters specified for each test. +Note 2: The value is the energy of per RE for a single antenna port before pre-coding. +Note 3: $L \in \{1, 2, 4, 8\}$ is the CDM group size of NZP CSI-RS specified for each test. +Note 4: It is only applicable to LTE-NR coexistence tests. + +# --- Annex D (informative): Void --- + +# Annex E (normative): Environmental conditions + +## E.1 General + +This annex specifies the environmental requirements of the UE. Within these limits the requirements of the present documents shall be fulfilled. + +## --- E.2 Environmental (Conducted) + +The requirements in this clause apply to all types of UE(s). + +### E.2.1 Temperature + +The UE shall fulfil all the requirements in the temperature range defined in Table E.2.1-1. + +**Table E.2.1-1: Temperature conditions** + +| Temperature | Temperature conditions | +|----------------|----------------------------------------------------------------| +| +15°C to +35°C | For normal conditions (with relative humidity of 25 % to 75 %) | + +Outside this temperature range the UE, if powered on, shall not make ineffective use of the radio frequency spectrum. In no case shall the UE exceed the transmitted levels as defined in clause 6.2 of TS 38.101-1 [6] for extreme operation. + +### E.2.2 Voltage + +The UE shall fulfil all the requirements in the voltage range defined in Table E.2.2-1. + +**Table E.2.2-1: Voltage conditions** + +| Power source | Normal conditions voltage | +|------------------------------------------------------------------------------|-------------------------------------| +| AC mains | nominal | +| Regulated lead acid battery | 1,1 * nominal | +| Non regulated batteries:
Leclanché
Lithium
Mercury/nickel & cadmium | Nominal
1,1 * Nominal
Nominal | + +Outside this voltage range the UE if powered on, shall not make ineffective use of the radio frequency spectrum. In no case shall the UE exceed the transmitted levels as defined in TS 38.101-1[6, Clause 6.2] for extreme operation. In particular, the UE shall inhibit all RF transmissions when the power supply voltage is below the manufacturer declared shutdown voltage. + +### E.2.3 Vibration + +The UE shall fulfil all the requirements when vibrated at the following frequency/amplitudes. + +**Table E.2.3-1: Vibration conditions** + +| Frequency | ASD (Acceleration Spectral Density) random vibration | +|-----------------|-----------------------------------------------------------------------| +| 5 Hz to 20 Hz | 0,96 m 2 /s 3 | +| 20 Hz to 500 Hz | 0,96 m 2 /s 3 at 20 Hz, thereafter –3 dB/Octave | + +Outside the specified frequency range the UE, if powered on, shall not make ineffective use of the radio frequency spectrum. In no case shall the UE exceed the transmitted levels as defined in TS 38.101-1[6] for extreme operation. + +# Annex F (informative): Change history + +| Change history | | | | | | | | +|----------------|-----------------|------------|----|-----|-----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-01 | RAN4#10 1-bis-e | R4-2203086 | | | | Draft skeleton approved | 0.0.1 | +| 2022-03 | RAN4#10 2-e | R4-2207514 | | | | Added approved TPs in RAN4#102-e including:
R4-2207332, R4-2207334, R4-2207343, R4-2207344, R4-2207391, R4-2207393, R4-2207394, R4-2207396, R4-2207400, R4-2207404, R4-2207405, R4-2207410, R4-2207411, R4-2207413, R4-2207415 | 0.1.0 | +| 2022-05 | RAN4#10 3-e | R4-2208641 | | | | Added approved TPs in RAN4#103-e including:
R4-2208662, TP to TS 38.101-5 on Conducted transmitter characteristics
R4-2209366, TP for 38.101-5 on Output RF spectrum emissions for satellite UE except for UE coexistence
R4-2210851, Draft text proposal for Clause 3 - TS 38.101-5
R4-2210874, TP to TS 38.101-5 on 7.3 Reference Sensitivity
R4-2210876, Updates to TS 38.101-5 related to n255 A-MPR clause
R4-2210877, TP for 38.101-5 on Spurious emissions for UE coexistence
R4-2210878, TP to update TS 38.101-5 clause 7.6.3 on OOB
R4-2211220, TP for 38.101-5 on frequency error | 0.2.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 38.101-5: Corrections on Rx requirements for NTN UE | 17.1.0 | +| 2022-09 | RAN#97 | RP-222035 | 0002 | | F | CR to TS 38.101-5 - Tx requirements issues fixes | 17.1.0 | +| 2022-09 | RAN#97 | RP-222035 | 0003 | 1 | F | CR to TS 38.101-5 - Rx requirements issues fixes | 17.1.0 | +| 2022-12 | RAN#98-e | RP-223306 | 0005 | 1 | F | CR: 0005 Doppler test conditions for RF requirements 38.101-5 | 17.2.0 | +| 2022-12 | RAN#98-e | RP-223306 | 0006 | | F | CR to 38.101-5: Corrections on section 5.3.3 for NTN UE | 17.2.0 | +| 2022-12 | RAN#98-e | RP-223311 | 0010 | 2 | F | CR to 38.101-5 for NTN UE RF requirements corrections | 17.2.0 | +| 2022-12 | RAN#98-e | RP-223309 | 0012 | | F | CR addition of protection for n100 and n101 into 38.101-5 | 17.2.0 | +| 2022-12 | RAN#98-e | RP-223311 | 0013 | | F | CR to 38.101-5: Corrections on reference for NTN UE | 17.2.0 | +| 2022-12 | RAN#98-e | RP-223303 | 0015 | | B | Big CR for UE NTN performance requirements (TS38.101-5, Rel-17, CAT B) | 17.2.0 | + +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +|---------|----------|-----------|------|-----|-----|-------------------------------------------------------------------------------------------|-------------| +| 2022-12 | RAN#98-e | RP-223315 | 0009 | 1 | B | CR related to Introduction of LTE TDD Band in 1670 – 1675 MHz | 18.0.0 | +| 2023-03 | RAN#99 | RP-230535 | 0016 | | B | CR related to Introduction of NR TDD Band n54 | 18.1.0 | +| 2023-03 | RAN#99 | RP-230516 | 0018 | 1 | A | Correction of the out-of-band blocking requirements | 18.1.0 | +| 2023-06 | RAN#100 | RP-231344 | 0026 | | A | Correction to reference measurement channels for NTN | 18.2.0 | +| 2023-09 | RAN#101 | RP-232494 | 0028 | | A | CR to TS38.101-5: Corrections to NR-NTN requirements (Rel-18) | 18.3.0 | +| 2023-09 | RAN#101 | RP-232494 | 0031 | | A | [NR_NTN_solutions-Core] CR to 38.101-5 corrections A-MPR requirement reference-r18 | 18.3.0 | +| 2023-09 | RAN#101 | RP-232522 | 0033 | 1 | B | CR for TS 38.101-5 – Adding 30 MHz CBW for NTN UE | 18.3.0 | +| 2023-09 | RAN#101 | RP-232494 | 0035 | 1 | A | Clarifications to 38.101-5 (Rel-18) | 18.3.0 | +| 2023-12 | RAN#102 | RP-233365 | 0039 | | B | Introduction of the enhanced channel raster to TS 38.101-5 | 18.4.0 | +| 2023-12 | RAN#102 | RP-233349 | 0042 | | A | CR to 38.101-5 on clarification for NR NTN UE RF and Demod requirements test conditions | 18.4.0 | +| 2023-12 | RAN#102 | RP-233349 | 0044 | | A | CR to 38.101-5: Correction on the reference measurement channel for NTN PDSCH requirement | 18.4.0 | +| 2023-12 | RAN#102 | RP-233349 | 0046 | | A | [NR_NTN_solutions-Core] CR for 38.101-5 to align the understanding of GEO (R18) | 18.4.0 | +| 2023-12 | RAN#102 | RP-233349 | 0052 | | A | Clarification for the Pi/2 BPSK modulation | 18.4.0 | +| 2023-12 | RAN#102 | RP-233366 | 0054 | 1 | B | Introduction of the NTN L/S-band | 18.4.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38104/0362d269cf8a825d1c65a468fcc88808_img.jpg b/marked/Rel-18/38_series/38104/0362d269cf8a825d1c65a468fcc88808_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7552c1752e9187df59ff21a700fa579ab79ed8a7 --- /dev/null +++ b/marked/Rel-18/38_series/38104/0362d269cf8a825d1c65a468fcc88808_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a48a8923504733f82be479de761b449e7a034447da431d08a1e7da52c607f25 +size 35923 diff --git a/marked/Rel-18/38_series/38104/178b298b89a3deeb2d1a8790b64379cc_img.jpg b/marked/Rel-18/38_series/38104/178b298b89a3deeb2d1a8790b64379cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53fa68084c1ec811701166dea7b098d622f687b2 --- /dev/null +++ b/marked/Rel-18/38_series/38104/178b298b89a3deeb2d1a8790b64379cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19082d10f2e72c4e78dd0614f85f687d685c1a5e1048416111f6963ff6b36c4c +size 14105 diff --git a/marked/Rel-18/38_series/38104/20136850feb70fd71c7d41cdae203ebb_img.jpg b/marked/Rel-18/38_series/38104/20136850feb70fd71c7d41cdae203ebb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69b3e6f8c7aab234694cdd08d16ef172e11c5a36 --- /dev/null +++ b/marked/Rel-18/38_series/38104/20136850feb70fd71c7d41cdae203ebb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d0534308f7a1652dca92d428ddbe8c99baabbebc8a035d50e9177676bad8b4f9 +size 43167 diff --git a/marked/Rel-18/38_series/38104/2efdbbefdd5a8f462a7866e28b50a556_img.jpg b/marked/Rel-18/38_series/38104/2efdbbefdd5a8f462a7866e28b50a556_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..63013d8d1f8f3656767d0a81f14d432c4ca2d912 --- /dev/null +++ b/marked/Rel-18/38_series/38104/2efdbbefdd5a8f462a7866e28b50a556_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0815363930cb661b09252753250f59c72c83817e18eb55ff70fe40d3230bff91 +size 38886 diff --git a/marked/Rel-18/38_series/38104/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg b/marked/Rel-18/38_series/38104/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3eb2565bfd372778fef08635f03c4cc1995f7ba5 --- /dev/null +++ b/marked/Rel-18/38_series/38104/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9553807a95c9d34fe5f60c853f00e063c4c381af586c95c4fc286efafddefc5e +size 35360 diff --git a/marked/Rel-18/38_series/38104/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38104/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab19fcdc62a51e40885f416a7e1464ee38efe06b --- /dev/null +++ b/marked/Rel-18/38_series/38104/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5d705d6424d3ab04690f0f5f94de558a43bd8026c28f1b587bcc44f75188307 +size 9561 diff --git a/marked/Rel-18/38_series/38104/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38104/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b2e98f6b3eeb06dde53a87354f1e447dfcb195d3 --- /dev/null +++ b/marked/Rel-18/38_series/38104/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:77348a79a8f9d7f4b99f7445f144189183f827985a90c77fef1e459b2aa77cb7 +size 5481 diff --git a/marked/Rel-18/38_series/38104/67ba9da7d9adb5f60447e65bf4bb74fa_img.jpg b/marked/Rel-18/38_series/38104/67ba9da7d9adb5f60447e65bf4bb74fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..613cef4ac2a5821d5b39e38d0f743d566519f1f5 --- /dev/null +++ b/marked/Rel-18/38_series/38104/67ba9da7d9adb5f60447e65bf4bb74fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6005d978808c9079d2599b0c2d35ca8d6f4043ee2cc5e3c522e746afdd47a61e +size 39053 diff --git a/marked/Rel-18/38_series/38104/7a5f8628e9bf1ad30b7257ce3785e17c_img.jpg b/marked/Rel-18/38_series/38104/7a5f8628e9bf1ad30b7257ce3785e17c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..094381a61699c2beddef254fbf280225aba3285f --- /dev/null +++ b/marked/Rel-18/38_series/38104/7a5f8628e9bf1ad30b7257ce3785e17c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a86880e4562eaa82a38446794a711088489f72ccf9d77c7a581e3edc1d46a0d +size 51498 diff --git a/marked/Rel-18/38_series/38104/818603aa875f7827229dc7ba1faee7a8_img.jpg b/marked/Rel-18/38_series/38104/818603aa875f7827229dc7ba1faee7a8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0a8695017b1e07c1ae4d462d814c5edf4cf5053 --- /dev/null +++ b/marked/Rel-18/38_series/38104/818603aa875f7827229dc7ba1faee7a8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a8c4909b6a5369152d5bec994cc107d5e74fb846ea677f63246a267171868f8 +size 43107 diff --git a/marked/Rel-18/38_series/38104/832ff030ba600d7d805d1e3dcc534373_img.jpg b/marked/Rel-18/38_series/38104/832ff030ba600d7d805d1e3dcc534373_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ac5fc95a3d0d42d702631ed7615698e2303a0b6 --- /dev/null +++ b/marked/Rel-18/38_series/38104/832ff030ba600d7d805d1e3dcc534373_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:edb531d684789b94f3a40afdb89cccdd336e31a8291d365432889954e069c2f8 +size 138952 diff --git a/marked/Rel-18/38_series/38104/88a6d9692a52989caa6b208a1ba70dc0_img.jpg b/marked/Rel-18/38_series/38104/88a6d9692a52989caa6b208a1ba70dc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ca7a79c205553391eaf3812ddca85c3d2d10797 --- /dev/null +++ b/marked/Rel-18/38_series/38104/88a6d9692a52989caa6b208a1ba70dc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c592bcf404ac9973ab86c726471406c3037a260489807ab811893bce4e219fd +size 29801 diff --git a/marked/Rel-18/38_series/38104/89065ed508d3657c36172356d9ecedb4_img.jpg b/marked/Rel-18/38_series/38104/89065ed508d3657c36172356d9ecedb4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..08049e6616daaccade3ae30ee11ac28f2ebb1da0 --- /dev/null +++ b/marked/Rel-18/38_series/38104/89065ed508d3657c36172356d9ecedb4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2768a8591468b0b639fc3cb95d959c83313df9b9aa670907892ea90b24c6ea48 +size 141213 diff --git a/marked/Rel-18/38_series/38104/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-18/38_series/38104/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ffe4bd4f87bab931df2b6cea8704a3f0f8f4fdd --- /dev/null +++ b/marked/Rel-18/38_series/38104/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00546c0fe4faa6bed377dbdff89103c4c33c4db80d3934d82186cb872317cefb +size 29164 diff --git a/marked/Rel-18/38_series/38104/9e0e01c6247122e4aeb20232ecdfe5b3_img.jpg b/marked/Rel-18/38_series/38104/9e0e01c6247122e4aeb20232ecdfe5b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9bd1cb2bb45d322f2c0b5da4394ef5c2ae7e9ac1 --- /dev/null +++ b/marked/Rel-18/38_series/38104/9e0e01c6247122e4aeb20232ecdfe5b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:afe70f65c6f52881265ada1954cba33dc6c2cb750c5038f42125c7cb9bcdfa9f +size 39401 diff --git a/marked/Rel-18/38_series/38104/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg b/marked/Rel-18/38_series/38104/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d8725e0ff0830434c1c31acf8d3198d445f4ffa0 --- /dev/null +++ b/marked/Rel-18/38_series/38104/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56306b7946d1e0a3fa3e48d271536f63c073b57dda4623812bd7dc180920c140 +size 130822 diff --git a/marked/Rel-18/38_series/38104/acfcaa452beafc856ac576f670a1f2c4_img.jpg b/marked/Rel-18/38_series/38104/acfcaa452beafc856ac576f670a1f2c4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4932f806741f23c8e25b826a9667457e25f4d41a --- /dev/null +++ b/marked/Rel-18/38_series/38104/acfcaa452beafc856ac576f670a1f2c4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:01a0934e8caab024d79eea8061fa195bacdbb7882ccefbc0f0f838a2b6e50870 +size 43938 diff --git a/marked/Rel-18/38_series/38104/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg b/marked/Rel-18/38_series/38104/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..72de7e0e4e6eeeaa3d3cea632205a93cf58b0b1e --- /dev/null +++ b/marked/Rel-18/38_series/38104/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b276c05c17134c44fb98ede00a36fe25cd389d2dc952808e9767bdaf1f74f08 +size 77242 diff --git a/marked/Rel-18/38_series/38104/c26110a289eb2c41e31c197c6ccff035_img.jpg b/marked/Rel-18/38_series/38104/c26110a289eb2c41e31c197c6ccff035_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f9e93909d3e421553d8c97ed34a9dfa320bec92 --- /dev/null +++ b/marked/Rel-18/38_series/38104/c26110a289eb2c41e31c197c6ccff035_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b71b877bd3ff1452c296756a7f505b1a27e32d24985daf64091d030b124e2873 +size 41133 diff --git a/marked/Rel-18/38_series/38104/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/marked/Rel-18/38_series/38104/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..492114f831419d024554a965f24fa7338ddb447d --- /dev/null +++ b/marked/Rel-18/38_series/38104/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c46fe8bdecc5fae97066899bd512166679beba04ed1c7230bef14eae9e44b6d +size 30195 diff --git a/marked/Rel-18/38_series/38104/cef8059e51ebeb728bca695b6f92dec3_img.jpg b/marked/Rel-18/38_series/38104/cef8059e51ebeb728bca695b6f92dec3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c3c2b9c78ca1b5162ba2419b706505f04303a78 --- /dev/null +++ b/marked/Rel-18/38_series/38104/cef8059e51ebeb728bca695b6f92dec3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:92a63cdc8a4f80e75fd952d8555fb9b1b63caa6a5f9c606220c4665e2f3a02a1 +size 63750 diff --git a/marked/Rel-18/38_series/38104/d7a98a717edbc26ca1508aaab7a566f4_img.jpg b/marked/Rel-18/38_series/38104/d7a98a717edbc26ca1508aaab7a566f4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7bf1a220bfb86bca73d94b5f157707ccbc0e1ba0 --- /dev/null +++ b/marked/Rel-18/38_series/38104/d7a98a717edbc26ca1508aaab7a566f4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:365da891453a163bef53d1faecc3ca124ecaa1e663b6668f2126b7860e247199 +size 32909 diff --git a/marked/Rel-18/38_series/38104/e6b7edf0d92a0843cc21e4ef707c50e5_img.jpg b/marked/Rel-18/38_series/38104/e6b7edf0d92a0843cc21e4ef707c50e5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fcd0494c807a5c9020e1ec9b5122bb2d55aba3ba --- /dev/null +++ b/marked/Rel-18/38_series/38104/e6b7edf0d92a0843cc21e4ef707c50e5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f58d17935af7d971703454ecf97f77cb40d6a8b9d459b5275e2c3188bca2a025 +size 49638 diff --git a/marked/Rel-18/38_series/38104/eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg b/marked/Rel-18/38_series/38104/eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..239daf65f14ac3cbf37786bee6843b5f114586f4 --- /dev/null +++ b/marked/Rel-18/38_series/38104/eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58b237d2822a0685f52c24d2dac033f5d4a4d62fb5c0eac86508327ac1b2bd35 +size 23863 diff --git a/marked/Rel-18/38_series/38104/f324fbc5d5af1e4da9cd932389f0064c_img.jpg b/marked/Rel-18/38_series/38104/f324fbc5d5af1e4da9cd932389f0064c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..222a2d59807e31d014f618ca76dd5a934436c947 --- /dev/null +++ b/marked/Rel-18/38_series/38104/f324fbc5d5af1e4da9cd932389f0064c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:54e3675e0976dd9cfe3563cfae6eb869d99bd506292aa7dea7ea88aa8337de07 +size 54310 diff --git a/marked/Rel-18/38_series/38104/fe7ce38208f739f617c272d8238c7bfa_img.jpg b/marked/Rel-18/38_series/38104/fe7ce38208f739f617c272d8238c7bfa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0f4ad2f5dc3c4ecb26e446e98b3a83ef3563ae2 --- /dev/null +++ b/marked/Rel-18/38_series/38104/fe7ce38208f739f617c272d8238c7bfa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:107dfdf3b0dbc5ed7f5504d1c1aa872b4781e1b06ddb91e99c6e0560194d4e41 +size 37727 diff --git a/marked/Rel-18/38_series/38104/raw.md b/marked/Rel-18/38_series/38104/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..31c62993e2e0ffad2120f54cae717d4212d8e58e --- /dev/null +++ b/marked/Rel-18/38_series/38104/raw.md @@ -0,0 +1,14469 @@ + + +# 3GPP TS 38.104 V18.4.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Base Station (BS) radio transmission and reception (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller text to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, stylized font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' underneath. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. +The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. +This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. +Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|---------------------------------------------------------------------------------------|----| +| Foreword..... | 13 | +| 1 Scope..... | 15 | +| 2 References..... | 15 | +| 3 Definitions, symbols and abbreviations..... | 16 | +| 3.1 Definitions..... | 16 | +| 3.2 Symbols..... | 20 | +| 3.3 Abbreviations..... | 22 | +| 4 General..... | 24 | +| 4.1 Relationship with other core specifications..... | 24 | +| 4.2 Relationship between minimum requirements and test requirements..... | 24 | +| 4.3 Conducted and radiated requirement reference points..... | 24 | +| 4.3.1 BS type 1-C ..... | 24 | +| 4.3.2 BS type 1-H ..... | 25 | +| 4.3.3 BS type 1-O and BS type 2-O ..... | 26 | +| 4.4 Base station classes..... | 26 | +| 4.5 Regional requirements..... | 27 | +| 4.6 Applicability of requirements..... | 30 | +| 4.7 Requirements for contiguous and non-contiguous spectrum ..... | 30 | +| 4.8 Requirements for BS capable of multi-band operation..... | 31 | +| 4.9 OTA co-location with other base stations..... | 32 | +| 5 Operating bands and channel arrangement ..... | 34 | +| 5.1 General..... | 34 | +| 5.2 Operating bands ..... | 34 | +| 5.3 BS channel bandwidth ..... | 37 | +| 5.3.1 General..... | 37 | +| 5.3.2 Transmission bandwidth configuration ..... | 38 | +| 5.3.3 Minimum guardband and transmission bandwidth configuration ..... | 39 | +| 5.3.4 RB alignment..... | 40 | +| 5.3.5 BS channel bandwidth per operating band ..... | 40 | +| 5.3A BS channel bandwidth for CA ..... | 45 | +| 5.3A.1 Transmission bandwidth configuration for CA ..... | 45 | +| 5.3A.2 Minimum guardband and transmission bandwidth configuration for CA ..... | 45 | +| 5.4 Channel arrangement..... | 48 | +| 5.4.1 Channel spacing..... | 48 | +| 5.4.1.1 Channel spacing for adjacent NR carriers..... | 48 | +| 5.4.1.2 Channel spacing for CA..... | 48 | +| 5.4.2 Channel raster..... | 49 | +| 5.4.2.1 NR-ARFCN and channel raster..... | 49 | +| 5.4.2.1A NB-IoT carrier frequency numbering..... | 49 | +| 5.4.2.2 Channel raster to resource element mapping..... | 50 | +| 5.4.2.3 Channel raster entries for each operating band ..... | 50 | +| 5.4.3 Synchronization raster..... | 56 | +| 5.4.3.1 Synchronization raster and numbering..... | 56 | +| 5.4.3.3 Synchronization raster entries for each operating band..... | 57 | +| 6 Conducted transmitter characteristics..... | 62 | +| 6.1 General..... | 62 | +| 6.2 Base station output power..... | 62 | +| 6.2.1 General..... | 62 | +| 6.2.2 Minimum requirement for BS type 1-C ..... | 63 | +| 6.2.3 Minimum requirement for BS type 1-H ..... | 63 | +| 6.2.4 Additional requirements (regional)..... | 63 | +| 6.3 Output power dynamics..... | 64 | +| 6.3.1 General..... | 64 | +| 6.3.2 RE power control dynamic range..... | 64 | + +| | | | +|------------|-----------------------------------------------------------------------------------------------------|-----| +| 6.3.2.1 | General..... | 64 | +| 6.3.2.2 | Minimum requirement for BS type 1-C and BS type 1-H ..... | 64 | +| 6.3.3 | Total power dynamic range..... | 64 | +| 6.3.3.1 | General..... | 64 | +| 6.3.3.2 | Minimum requirement for BS type 1-C and BS type 1-H ..... | 64 | +| 6.3.4 | NB-IoT RB power dynamic range for NB-IoT operation in NR in-band..... | 65 | +| 6.3.4.1 | General..... | 65 | +| 6.3.4.2 | Minimum Requirement..... | 65 | +| 6.4 | Transmit ON/OFF power..... | 65 | +| 6.4.1 | Transmitter OFF power..... | 65 | +| 6.4.1.1 | General..... | 65 | +| 6.4.1.2 | Minimum requirement for BS type 1-C ..... | 66 | +| 6.4.1.3 | Minimum requirement for BS type 1-H ..... | 66 | +| 6.4.2 | Transmitter transient period ..... | 66 | +| 6.4.2.1 | General..... | 66 | +| 6.4.2.2 | Minimum requirement for BS type 1-C and BS type 1-H ..... | 67 | +| 6.4.2.3 | Void..... | 67 | +| 6.5 | Transmitted signal quality..... | 67 | +| 6.5.1 | Frequency error..... | 67 | +| 6.5.1.1 | General..... | 67 | +| 6.5.1.2 | Minimum requirement for BS type 1-C and BS type 1-H ..... | 67 | +| 6.5.2 | Modulation quality..... | 67 | +| 6.5.2.1 | General..... | 67 | +| 6.5.2.2 | Minimum Requirement for BS type 1-C and BS type 1-H ..... | 68 | +| 6.5.2.3 | EVM frame structure for measurement..... | 68 | +| 6.5.3 | Time alignment error..... | 68 | +| 6.5.3.1 | General..... | 68 | +| 6.5.3.2 | Minimum requirement for BS type 1-C and BS type 1-H ..... | 68 | +| 6.6 | Unwanted emissions..... | 69 | +| 6.6.1 | General..... | 69 | +| 6.6.2 | Occupied bandwidth..... | 70 | +| 6.6.2.1 | General..... | 70 | +| 6.6.2.2 | Minimum requirement for BS type 1-C and BS type 1-H ..... | 70 | +| 6.6.3 | Adjacent Channel Leakage Power Ratio..... | 70 | +| 6.6.3.1 | General..... | 70 | +| 6.6.3.2 | Limits and Basic limits ..... | 70 | +| 6.6.3.3 | Minimum requirement for BS type 1-C ..... | 74 | +| 6.6.3.4 | Minimum requirement for BS type 1-H ..... | 74 | +| 6.6.4 | Operating band unwanted emissions..... | 74 | +| 6.6.4.1 | General..... | 74 | +| 6.6.4.2 | Basic limits ..... | 76 | +| 6.6.4.2.1 | Basic limits for Wide Area BS (Category A)..... | 76 | +| 6.6.4.2.2 | Basic limits for Wide Area BS (Category B)..... | 77 | +| 6.6.4.2.3 | Basic limits for Medium Range BS (Category A and B)..... | 82 | +| 6.6.4.2.4 | Basic limits for Local Area BS (Category A and B)..... | 85 | +| 6.6.4.2.4A | Basic limits for Local Area and Medium Range BS for bands n46, n96 and n102 (Category A and B)..... | 87 | +| 6.6.4.2.5 | Basic limits for additional requirements..... | 90 | +| 6.6.4.3 | Minimum requirements for BS type 1-C ..... | 92 | +| 6.6.4.4 | Minimum requirements for BS type 1-H ..... | 93 | +| 6.6.5 | Transmitter spurious emissions..... | 93 | +| 6.6.5.1 | General..... | 93 | +| 6.6.5.2 | Basic limits ..... | 94 | +| 6.6.5.2.1 | General transmitter spurious emissions requirements..... | 94 | +| 6.6.5.2.2 | Protection of the BS receiver of own or different BS..... | 94 | +| 6.6.5.2.3 | Additional spurious emissions requirements..... | 95 | +| 6.6.5.2.4 | Co-location with other base stations..... | 106 | +| 6.6.5.3 | Minimum requirements for BS type 1-C ..... | 112 | +| 6.6.5.4 | Minimum requirements for BS type 1-H ..... | 112 | +| 6.7 | Transmitter intermodulation..... | 112 | +| 6.7.1 | General..... | 112 | + +| | | | +|---------|--------------------------------------------------------------------------------------|-----| +| 6.7.2 | Minimum requirements for BS type 1-C ..... | 113 | +| 6.7.2.1 | Co-location minimum requirements..... | 113 | +| 6.7.2.2 | Additional requirements..... | 113 | +| 6.7.3 | Minimum requirements for BS type 1-H ..... | 114 | +| 6.7.3.1 | Co-location minimum requirements..... | 114 | +| 6.7.3.2 | Intra-system minimum requirements..... | 115 | +| 6.7.3.3 | Additional requirements..... | 115 | +| 7 | Conducted receiver characteristics..... | 117 | +| 7.1 | General..... | 117 | +| 7.2 | Reference sensitivity level..... | 117 | +| 7.2.1 | General..... | 117 | +| 7.2.2 | Minimum requirements for BS type 1-C and BS type 1-H ..... | 117 | +| 7.3 | Dynamic range..... | 123 | +| 7.3.1 | General..... | 123 | +| 7.3.2 | Minimum requirement for BS type 1-C and BS type 1-H ..... | 123 | +| 7.4 | In-band selectivity and blocking..... | 135 | +| 7.4.1 | Adjacent Channel Selectivity (ACS)..... | 135 | +| 7.4.1.1 | General..... | 135 | +| 7.4.1.2 | Minimum requirement for BS type 1-C and BS type 1-H ..... | 135 | +| 7.4.1.3 | Void..... | 138 | +| 7.4.1.4 | Void..... | 138 | +| 7.4.2 | In-band blocking..... | 138 | +| 7.4.2.1 | General..... | 138 | +| 7.4.2.2 | Minimum requirement for BS type 1-C and BS type 1-H ..... | 138 | +| 7.4.2.3 | Void..... | 142 | +| 7.4.2.4 | Void..... | 142 | +| 7.4.2.5 | Additional narrowband blocking requirement for Band n100..... | 142 | +| 7.5 | Out-of-band blocking..... | 142 | +| 7.5.1 | General..... | 142 | +| 7.5.2 | Minimum requirement for BS type 1-C and BS type 1-H ..... | 143 | +| 7.5.3 | Co-location minimum requirements for BS type 1-C and BS type 1-H ..... | 144 | +| 7.5.4 | Void..... | 145 | +| 7.5.5 | Additional out-of-band blocking requirements for the use of RMR bands..... | 145 | +| 7.6 | Receiver spurious emissions..... | 145 | +| 7.6.1 | General..... | 145 | +| 7.6.2 | Basic limits ..... | 145 | +| 7.6.3 | Minimum requirement for BS type 1-C ..... | 146 | +| 7.6.4 | Minimum requirement for BS type 1-H ..... | 146 | +| 7.7 | Receiver intermodulation..... | 147 | +| 7.7.1 | General..... | 147 | +| 7.7.2 | Minimum requirement for BS type 1-C and BS type 1-H ..... | 147 | +| 7.7.3 | Additional narrowband intermodulation requirement for Band n100..... | 153 | +| 7.8 | In-channel selectivity..... | 153 | +| 7.8.1 | General..... | 153 | +| 7.8.2 | Minimum requirement for BS type 1-C and BS type 1-H ..... | 153 | +| 8 | Conducted performance requirements..... | 166 | +| 8.1 | General..... | 166 | +| 8.1.1 | Scope and definitions..... | 166 | +| 8.1.2 | Void..... | 166 | +| 8.2 | Performance requirements for PUSCH..... | 166 | +| 8.2.1 | Requirements for PUSCH with transform precoding disabled..... | 166 | +| 8.2.1.1 | General..... | 166 | +| 8.2.1.2 | Minimum requirements..... | 167 | +| 8.2.2 | Requirements for PUSCH with transform precoding enabled..... | 176 | +| 8.2.2.1 | General..... | 176 | +| 8.2.2.2 | Minimum requirements..... | 177 | +| 8.2.3 | Requirements for UCI multiplexed on PUSCH..... | 178 | +| 8.2.3.1 | General..... | 178 | +| 8.2.3.2 | Minimum requirements..... | 179 | +| 8.2.4 | Requirements for PUSCH for high speed train..... | 180 | + +| | | | +|-------------|--------------------------------------------------------------------------|-----| +| 8.2.4.1 | General..... | 180 | +| 8.2.4.2 | Minimum requirements..... | 181 | +| 8.2.5 | Requirements for UL timing adjustment..... | 183 | +| 8.2.5.1 | Minimum requirements for high speed train..... | 184 | +| 8.2.5.2 | Minimum requirements for normal mode..... | 185 | +| 8.2.6 | Requirements for PUSCH 0.001% BLER..... | 186 | +| 8.2.6.1 | General..... | 186 | +| 8.2.6.2 | Minimum requirements..... | 186 | +| 8.2.7 | Requirements for PUSCH repetition Type A..... | 187 | +| 8.2.7.1 | General..... | 187 | +| 8.2.7.2 | Minimum requirements..... | 188 | +| 8.2.8 | Requirements for PUSCH mapping Type B with non-slot transmission..... | 190 | +| 8.2.8.1 | General..... | 190 | +| 8.2.8.2 | Minimum requirements..... | 190 | +| 8.2.9 | Requirements of PUSCH for 2-step RA type..... | 191 | +| 8.2.9.1 | General..... | 191 | +| 8.2.9.2 | Minimum requirements..... | 192 | +| 8.2.10 | Requirements for interlaced PUSCH..... | 192 | +| 8.2.10.1 | General..... | 192 | +| 8.2.10.2 | Minimum requirements..... | 193 | +| 8.2.11 | Performance requirements for CG-UCI multiplexed on interlaced PUSCH..... | 194 | +| 8.2.11.1 | General..... | 194 | +| 8.2.11.2 | Minimum requirements..... | 195 | +| 8.2.12 | Requirements for TB processing over multi-slot PUSCH (TBoMS)..... | 196 | +| 8.2.12.1 | General..... | 196 | +| 8.2.12.2 | Minimum requirements..... | 196 | +| 8.2.13 | Requirements for PUSCH with DM-RS bundling..... | 197 | +| 8.2.13.1 | General..... | 197 | +| 8.2.13.2 | Minimum requirements..... | 198 | +| 8.3 | Performance requirements for PUCCH..... | 200 | +| 8.3.1 | DTX to ACK probability..... | 200 | +| 8.3.1.1 | General..... | 200 | +| 8.3.1.2 | Minimum requirement..... | 201 | +| 8.3.2 | Performance requirements for PUCCH format 0..... | 201 | +| 8.3.2.1 | General..... | 201 | +| 8.3.2.2 | Minimum requirements..... | 201 | +| 8.3.3 | Performance requirements for PUCCH format 1..... | 202 | +| 8.3.3.1 | NACK to ACK requirements..... | 202 | +| 8.3.3.1.1 | General..... | 202 | +| 8.3.3.1.2 | Minimum requirements..... | 202 | +| 8.3.3.2 | ACK missed detection requirements..... | 203 | +| 8.3.3.2.1 | General..... | 203 | +| 8.3.3.2.2 | Minimum requirements..... | 203 | +| 8.3.4 | Performance requirements for PUCCH format 2..... | 204 | +| 8.3.4.1 | ACK missed detection requirements..... | 204 | +| 8.3.4.1.1 | General..... | 204 | +| 8.3.4.1.2 | Minimum requirements..... | 204 | +| 8.3.4.2 | UCI BLER performance requirements..... | 205 | +| 8.3.4.2.1 | General..... | 205 | +| 8.3.4.2.2 | Minimum requirements..... | 205 | +| 8.3.5 | Performance requirements for PUCCH format 3..... | 206 | +| 8.3.5.1 | General..... | 206 | +| 8.3.5.2 | Minimum requirements..... | 206 | +| 8.3.6 | Performance requirements for PUCCH format 4..... | 207 | +| 8.3.6.1 | General..... | 207 | +| 8.3.6.2 | Minimum requirement..... | 208 | +| 8.3.7 | Performance requirements for multi-slot PUCCH..... | 209 | +| 8.3.7.1 | General..... | 209 | +| 8.3.7.2 | Performance requirements for multi-slot PUCCH format 1..... | 209 | +| 8.3.7.2.1 | NACK to ACK requirements..... | 209 | +| 8.3.7.2.1.1 | General..... | 209 | + +| | | | +|-------------|--------------------------------------------------------------------------|-----| +| 8.3.7.2.1.2 | Minimum requirements..... | 210 | +| 8.3.7.2.2 | ACK missed detection requirements..... | 210 | +| 8.3.8 | Performance requirements for interlaced PUCCH format 0..... | 210 | +| 8.3.8.1 | General..... | 210 | +| 8.3.8.2 | Minimum requirements..... | 211 | +| 8.3.9 | Performance requirements for interlaced PUCCH format 1..... | 211 | +| 8.3.9.1 | NACK to ACK requirements..... | 211 | +| 8.3.9.1.1 | General..... | 211 | +| 8.3.9.1.2 | Minimum requirements..... | 212 | +| 8.3.9.2 | ACK missed detection requirements..... | 212 | +| 8.3.9.2.1 | General..... | 212 | +| 8.3.9.2.2 | Minimum requirements..... | 212 | +| 8.3.10 | Performance requirements for interlaced PUCCH format 2..... | 213 | +| 8.3.10.1 | General..... | 213 | +| 8.3.10.2 | Minimum requirements..... | 213 | +| 8.3.11 | Performance requirements for interlaced PUCCH format 3..... | 214 | +| 8.3.11.1 | General..... | 214 | +| 8.3.11.2 | Minimum requirements..... | 214 | +| 8.3.12 | Performance requirements for PUCCH format 1 with DM-RS bundling..... | 215 | +| 8.3.12.1 | NACK to ACK requirements..... | 215 | +| 8.3.12.1.1 | General..... | 215 | +| 8.3.12.1.2 | Minimum requirements..... | 215 | +| 8.3.12.2 | ACK missed detection requirements..... | 216 | +| 8.3.12.2.1 | General..... | 216 | +| 8.3.12.2.2 | Minimum requirements..... | 216 | +| 8.3.13 | Performance requirements for PUCCH format 3 with DMRS bundling..... | 216 | +| 8.3.13.1 | General..... | 216 | +| 8.3.13.2 | Minimum requirements..... | 217 | +| 8.3.14 | Performance requirements for sub-slot repetition PUCCH format 0..... | 218 | +| 8.3.14.1 | General..... | 218 | +| 8.3.14.2 | Minimum requirements..... | 218 | +| 8.4 | Performance requirements for PRACH..... | 219 | +| 8.4.1 | PRACH False alarm probability..... | 219 | +| 8.4.1.1 | General..... | 219 | +| 8.4.1.2 | Minimum requirement..... | 219 | +| 8.4.2 | PRACH detection requirements..... | 219 | +| 8.4.2.1 | General..... | 219 | +| 8.4.2.2 | Minimum requirements for Normal Mode..... | 219 | +| 8.4.2.3 | Minimum requirements for high speed train..... | 220 | +| 8.4.2.4 | Minimum requirements for PRACH with $L_{RA}=1151$ and $L_{RA}=571$ ..... | 221 | +| 9 | Radiated transmitter characteristics..... | 223 | +| 9.1 | General..... | 223 | +| 9.2 | Radiated transmit power..... | 223 | +| 9.2.1 | General..... | 223 | +| 9.2.2 | Minimum requirement for BS type 1-H and BS type 1-O ..... | 224 | +| 9.2.3 | Minimum requirement for BS type 2-O ..... | 224 | +| 9.3 | OTA base station output power..... | 224 | +| 9.3.1 | General..... | 224 | +| 9.3.2 | Minimum requirement for BS type 1-O ..... | 225 | +| 9.3.3 | Minimum requirement for BS type 2-O ..... | 225 | +| 9.3.4 | Additional requirements (regional)..... | 225 | +| 9.4 | OTA output power dynamics..... | 225 | +| 9.4.1 | General..... | 225 | +| 9.4.2 | OTA RE power control dynamic range..... | 225 | +| 9.4.2.1 | General..... | 225 | +| 9.4.2.2 | Minimum requirement for BS type 1-O ..... | 225 | +| 9.4.3 | OTA total power dynamic range..... | 225 | +| 9.4.3.1 | General..... | 225 | +| 9.4.3.2 | Minimum requirement for BS type 1-O ..... | 226 | +| 9.4.3.3 | Minimum requirement for BS type 2-O ..... | 226 | +| 9.5 | OTA transmit ON/OFF power..... | 226 | + +| | | | +|-------------|-------------------------------------------------------------------------|-----| +| 9.5.1 | General..... | 226 | +| 9.5.2 | OTA transmitter OFF power..... | 226 | +| 9.5.2.1 | General..... | 226 | +| 9.5.2.2 | Minimum requirement for BS type 1-O ..... | 226 | +| 9.5.2.3 | Minimum requirement for BS type 2-O ..... | 227 | +| 9.5.3 | OTA transient period..... | 227 | +| 9.5.3.1 | General..... | 227 | +| 9.5.3.2 | Minimum requirement for BS type 1-O ..... | 227 | +| 9.5.3.3 | Minimum requirement for BS type 2-O ..... | 227 | +| 9.6 | OTA transmitted signal quality..... | 227 | +| 9.6.1 | OTA frequency error..... | 227 | +| 9.6.1.1 | General..... | 227 | +| 9.6.1.2 | Minimum requirement for BS type 1-O ..... | 227 | +| 9.6.1.3 | Minimum requirement for BS type 2-O ..... | 228 | +| 9.6.2 | OTA modulation quality..... | 228 | +| 9.6.2.1 | General..... | 228 | +| 9.6.2.2 | Minimum Requirement for BS type 1-O ..... | 228 | +| 9.6.2.3 | Minimum Requirement for BS type 2-O ..... | 228 | +| 9.6.2.3.1 | EVM frame structure for measurement..... | 228 | +| 9.6.3 | OTA time alignment error..... | 228 | +| 9.6.3.1 | General..... | 228 | +| 9.6.3.2 | Minimum requirement for BS type 1-O ..... | 229 | +| 9.6.3.3 | Minimum requirement for BS type 2-O ..... | 229 | +| 9.7 | OTA unwanted emissions..... | 229 | +| 9.7.1 | General..... | 229 | +| 9.7.2 | OTA occupied bandwidth..... | 230 | +| 9.7.2.1 | General..... | 230 | +| 9.7.2.2 | Minimum requirement for BS type 1-O and BS type 2-O ..... | 230 | +| 9.7.3 | OTA Adjacent Channel Leakage Power Ratio (ACLR)..... | 231 | +| 9.7.3.1 | General..... | 231 | +| 9.7.3.2 | Minimum requirement for BS type 1-O ..... | 231 | +| 9.7.3.3 | Minimum requirement for BS type 2-O ..... | 231 | +| 9.7.4 | OTA operating band unwanted emissions..... | 233 | +| 9.7.4.1 | General..... | 233 | +| 9.7.4.2 | Minimum requirement for BS type 1-O ..... | 233 | +| 9.7.4.2.1 | Additional requirements..... | 234 | +| 9.7.4.2.1.1 | Protection of DTT..... | 234 | +| 9.7.4.2.1.2 | Limits in FCC Title 47..... | 234 | +| 9.7.4.3 | Minimum requirement for BS type 2-O ..... | 234 | +| 9.7.4.3.1 | General..... | 234 | +| 9.7.4.3.2 | OTA operating band unwanted emission limits (Category A)..... | 235 | +| 9.7.4.3.3 | OTA operating band unwanted emission limits (Category B)..... | 236 | +| 9.7.4.3.4 | Additional OTA operating band unwanted emission requirements..... | 237 | +| 9.7.5 | OTA transmitter spurious emissions..... | 237 | +| 9.7.5.1 | General..... | 237 | +| 9.7.5.2 | Minimum requirement for BS type 1-O ..... | 237 | +| 9.7.5.2.1 | General..... | 237 | +| 9.7.5.2.2 | General OTA transmitter spurious emissions requirements..... | 238 | +| 9.7.5.2.3 | Protection of the BS receiver of own or different BS..... | 238 | +| 9.7.5.2.4 | Additional spurious emissions requirements..... | 238 | +| 9.7.5.2.5 | Co-location with other base stations..... | 238 | +| 9.7.5.3 | Minimum requirement for BS type 2-O ..... | 238 | +| 9.7.5.3.1 | General..... | 238 | +| 9.7.5.3.2 | General OTA transmitter spurious emissions requirements..... | 239 | +| 9.7.5.3.3 | Additional OTA transmitter spurious emissions requirements..... | 240 | +| 9.8 | OTA transmitter intermodulation..... | 240 | +| 9.8.1 | General..... | 240 | +| 9.8.2 | Minimum requirement for BS type 1-O ..... | 240 | +| 9.8.3 | Additional requirements (regional)..... | 241 | +| 10 | Radiated receiver characteristics..... | 242 | +| 10.1 | General..... | 242 | + +| | | | +|-----------|-----------------------------------------------------------------------|-----| +| 10.2 | OTA sensitivity..... | 243 | +| 10.2.1 | BS type 1-H and BS type 1-O ..... | 243 | +| 10.2.1.1 | General..... | 243 | +| 10.2.1.2 | Minimum requirement..... | 243 | +| 10.2.2 | BS type 2-O ..... | 243 | +| 10.3 | OTA reference sensitivity level..... | 244 | +| 10.3.1 | General..... | 244 | +| 10.3.2 | Minimum requirement for BS type 1-O ..... | 244 | +| 10.3.3 | Minimum requirement for BS type 2-O ..... | 246 | +| 10.4 | OTA dynamic range..... | 247 | +| 10.4.1 | General..... | 247 | +| 10.4.2 | Minimum requirement for BS type 1-O ..... | 247 | +| 10.5 | OTA in-band selectivity and blocking..... | 260 | +| 10.5.1 | OTA adjacent channel selectivity..... | 260 | +| 10.5.1.1 | General..... | 260 | +| 10.5.1.2 | Minimum requirement for BS type 1-O ..... | 260 | +| 10.5.1.3 | Minimum requirement for BS type 2-O ..... | 261 | +| 10.5.2 | OTA in-band blocking..... | 262 | +| 10.5.2.1 | General..... | 262 | +| 10.5.2.2 | Minimum requirement for BS type 1-O ..... | 262 | +| 10.5.2.3 | Minimum requirement for BS type 2-O ..... | 265 | +| 10.6 | OTA out-of-band blocking..... | 266 | +| 10.6.1 | General..... | 266 | +| 10.6.2 | Minimum requirement for BS type 1-O ..... | 266 | +| 10.6.2.1 | General minimum requirement..... | 266 | +| 10.6.2.2 | Co-location minimum requirement..... | 267 | +| 10.6.3 | Minimum requirement for BS type 2-O ..... | 267 | +| 10.6.3.1 | General minimum requirement..... | 267 | +| 10.7 | OTA receiver spurious emissions..... | 268 | +| 10.7.1 | General..... | 268 | +| 10.7.2 | Minimum requirement for BS type 1-O ..... | 268 | +| 10.7.3 | Minimum requirement for BS type 2-O ..... | 269 | +| 10.8 | OTA receiver intermodulation..... | 270 | +| 10.8.1 | General..... | 270 | +| 10.8.2 | Minimum requirement for BS type 1-O ..... | 270 | +| 10.8.3 | Minimum requirement for BS type 2-O ..... | 275 | +| 10.9 | OTA in-channel selectivity..... | 276 | +| 10.9.1 | General..... | 276 | +| 10.9.2 | Minimum requirement for BS type 1-O ..... | 276 | +| 10.9.3 | Minimum requirement for BS type 2-O ..... | 280 | +| 11 | Radiated performance requirements..... | 282 | +| 11.1 | General..... | 282 | +| 11.1.1 | Scope and definitions..... | 282 | +| 11.1.2 | OTA demodulation branches..... | 282 | +| 11.1.3 | Void..... | 283 | +| 11.2 | Performance requirements for PUSCH..... | 283 | +| 11.2.1 | Requirements for BS type 1-O ..... | 283 | +| 11.2.1.1 | Requirements for PUSCH with transform precoding disabled..... | 283 | +| 11.2.1.2 | Requirements for PUSCH with transform precoding enabled..... | 283 | +| 11.2.1.3 | Requirements for UCI multiplexed on PUSCH..... | 283 | +| 11.2.1.4 | Requirements for PUSCH for high speed train..... | 283 | +| 11.2.1.5 | Requirements for UL timing adjustment..... | 283 | +| 11.2.1.6 | Requirements for PUSCH 0.001% BLER..... | 283 | +| 11.2.1.7 | Requirements for PUSCH repetition Type A..... | 283 | +| 11.2.1.8 | Requirements for PUSCH mapping Type B with non-slot transmission..... | 283 | +| 11.2.1.9 | Requirements for PUSCH for 2-step RA type..... | 283 | +| 11.2.1.10 | Requirements for interlaced PUSCH..... | 283 | +| 11.2.1.11 | Requirements for CG-UCI multiplexed on interlaced PUSCH..... | 283 | +| 11.2.1.12 | Requirements for TB processing over multi-slot PUSCH (TBoMS)..... | 283 | +| 11.2.1.13 | Requirements for PUSCH with DM-RS bundling..... | 284 | +| 11.2.2 | Requirements for BS type 2-O ..... | 284 | + +| | | | +|--------------|-----------------------------------------------------------------------|-----| +| 11.2.2.1 | Requirements for PUSCH with transform precoding disabled..... | 284 | +| 11.2.2.1.1 | General..... | 284 | +| 11.2.2.1.2 | Minimum requirements..... | 284 | +| 11.2.2.2 | Requirements for PUSCH with transform precoding enabled..... | 289 | +| 11.2.2.2.1 | General..... | 289 | +| 11.2.2.2.2 | Minimum requirements..... | 289 | +| 11.2.2.3 | Requirements for UCI multiplexed on PUSCH..... | 290 | +| 11.2.2.3.1 | General..... | 290 | +| 11.2.2.3.2 | Minimum requirements..... | 291 | +| 11.2.2.4 | Requirements for PUSCH for 2-step RA type..... | 293 | +| 11.2.2.4.1 | General..... | 293 | +| 11.2.2.4.2 | Minimum requirements..... | 294 | +| 11.2.2.5 | Requirements for PUSCH repetition Type A..... | 294 | +| 11.2.2.5.1 | General..... | 294 | +| 11.2.2.5.2 | Minimum requirements..... | 295 | +| 11.2.2.6 | Requirements for PUSCH mapping Type B with non-slot transmission..... | 296 | +| 11.2.2.6.1 | General..... | 296 | +| 11.2.2.6.2 | Minimum requirements..... | 296 | +| 11.2.2.7 | Requirements for PUSCH for high speed train..... | 297 | +| 11.2.2.7.1 | General..... | 297 | +| 11.2.2.7.2 | Minimum requirements..... | 297 | +| 11.2.2.8 | Requirements for UL timing adjustment..... | 298 | +| 11.2.2.8.1 | General..... | 298 | +| 11.2.2.8.2 | Minimum requirements for high speed train..... | 299 | +| 11.2.2.9 | Requirements for TB processing over multi-slot PUSCH (TBoMS)..... | 300 | +| 11.2.2.9.1 | General..... | 300 | +| 11.2.2.9.2 | Minimum requirements..... | 300 | +| 11.2.2.10 | Requirements for PUSCH with DM-RS bundling..... | 301 | +| 11.2.2.10.1 | General..... | 301 | +| 11.2.2.10.2 | Minimum requirements..... | 301 | +| 11.3 | Performance requirements for PUCCH..... | 302 | +| 11.3.1 | Requirements for BS type 1-O ..... | 302 | +| 11.3.1.1 | DTX to ACK probability..... | 302 | +| 11.3.1.2 | Performance requirements for PUCCH format 0..... | 302 | +| 11.3.1.3 | Performance requirements for PUCCH format 1..... | 302 | +| 11.3.1.4 | Performance requirements for PUCCH format 2..... | 302 | +| 11.3.1.5 | Performance requirements for PUCCH format 3..... | 302 | +| 11.3.1.6 | Performance requirements for PUCCH format 4..... | 302 | +| 11.3.1.7 | Performance requirements for multi-slot PUCCH..... | 302 | +| 11.3.1.8 | Performance requirements for PUCCH format 1 with DMRS bundling..... | 302 | +| 11.3.1.9 | Performance requirements for PUCCH format 3 with DMRS bundling..... | 303 | +| 11.3.1.10 | Performance requirements for sub-slot repetition PUCCH format 0..... | 303 | +| 11.3.2 | Requirements for BS type 2-O ..... | 303 | +| 11.3.2.1 | DTX to ACK probability..... | 303 | +| 11.3.2.2 | Performance requirements for PUCCH format 0..... | 303 | +| 11.3.2.2.1 | General..... | 303 | +| 11.3.2.2.2 | Minimum requirements..... | 303 | +| 11.3.2.3 | Performance requirements for PUCCH format 1..... | 304 | +| 11.3.2.3.1 | NACK to ACK requirements..... | 304 | +| 11.3.2.3.1.1 | General..... | 304 | +| 11.3.2.3.1.2 | Minimum requirements..... | 305 | +| 11.3.2.3.2 | ACK missed detection requirements..... | 306 | +| 11.3.2.3.2.1 | General..... | 306 | +| 11.3.2.3.2.2 | Minimum requirements..... | 306 | +| 11.3.2.4 | Performance requirements for PUCCH format 2..... | 307 | +| 11.3.2.4.1 | ACK missed detection requirements..... | 307 | +| 11.3.2.4.1.1 | General..... | 307 | +| 11.3.2.4.1.2 | Minimum requirements..... | 307 | +| 11.3.2.4.2 | UCI BLER performance requirements..... | 308 | +| 11.3.2.4.2.1 | General..... | 308 | +| 11.3.2.4.2.2 | Minimum requirements..... | 308 | + +| | | | +|--------------|--------------------------------------------------------------------------|-----| +| 11.3.2.5 | Performance requirements for PUCCH format 3..... | 309 | +| 11.3.2.5.1 | General..... | 309 | +| 11.3.2.5.2 | Minimum requirements..... | 309 | +| 11.3.2.6 | Performance requirements for PUCCH format 4..... | 310 | +| 11.3.2.6.1 | General..... | 310 | +| 11.3.2.6.2 | Minimum requirements..... | 311 | +| 11.3.2.7 | Performance requirements for PUCCH format 1 with DMRS bundling..... | 312 | +| 11.3.2.7.1 | NACK to ACK requirements..... | 312 | +| 11.3.2.7.1.1 | General..... | 312 | +| 11.3.2.7.1.2 | Minimum requirements..... | 313 | +| 11.3.2.7.2 | ACK missed detection requirements..... | 313 | +| 11.3.2.7.2.1 | General..... | 313 | +| 11.3.2.7.2.2 | Minimum requirements..... | 314 | +| 11.3.2.8 | Performance requirements for PUCCH format 3 with DMRS bundling..... | 314 | +| 11.3.2.8.1 | General..... | 314 | +| 11.3.2.8.2 | Minimum requirements..... | 315 | +| 11.4 | Performance requirements for PRACH..... | 315 | +| 11.4.1 | Requirements for BS type 1-O ..... | 315 | +| 11.4.1.1 | PRACH False alarm probability..... | 315 | +| 11.4.1.2 | PRACH detection requirements..... | 315 | +| 11.4.2 | Requirements for BS type 2-O ..... | 315 | +| 11.4.2.1 | PRACH False alarm probability..... | 315 | +| 11.4.2.1.1 | General..... | 315 | +| 11.4.2.1.2 | Minimum requirement..... | 315 | +| 11.4.2.2 | PRACH detection requirements..... | 316 | +| 11.4.2.2.1 | General..... | 316 | +| 11.4.2.2.2 | Minimum requirements for Normal mode..... | 316 | +| 11.4.2.2.3 | Minimum requirements for high speed train..... | 317 | +| 11.4.2.2.4 | Minimum requirements for PRACH with $L_{RA}=1151$ and $L_{RA}=571$ ..... | 317 | + +| | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------| +| Annex A (normative): Reference measurement channels..... | 319 | +| 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)..... | 319 | +| A.2 Fixed Reference Channels for dynamic range (16QAM, R=2/3)..... | 322 | +| A.3 Fixed Reference Channels for performance requirements (QPSK, R=193/1024)..... | 324 | +| A.3A Fixed Reference Channels for performance requirements (QPSK, R=99/1024)..... | 331 | +| A.3B Fixed Reference Channels for performance requirements (QPSK, R=308/1024)..... | 333 | +| A.4 Fixed Reference Channels for performance requirements (16QAM, R=658/1024)..... | 337 | +| A.5 Fixed Reference Channels for performance requirements (64QAM, R=567/1024)..... | 342 | +| A.6 PRACH Test preambles..... | 345 | +| A.7 Fixed Reference Channels for performance requirements (16QAM, R=434/1024)..... | 346 | +| A.8 Fixed Reference Channels for performance requirements (QPSK, R=157/1024)..... | 348 | +| A.9 Fixed Reference Channels for performance requirements (256QAM, R=682.5/1024)..... | 349 | +| A.10 Fixed Reference Channels for performance requirements (64QAM, R=517/1024)..... | 350 | +| A.11 Fixed Reference Channels for performance requirements (64QAM, R=438/1024)..... | 354 | +| Annex B (normative): Error Vector Magnitude (FR1)..... | 356 | +| B.1 Reference point for measurement..... | 356 | +| B.2 Basic unit of measurement..... | 356 | +| B.3 Modified signal under test..... | 357 | +| B.4 Estimation of frequency offset..... | 357 | +| B.5 Estimation of time offset..... | 357 | +| B.5.1 General..... | 357 | +| B.5.2 Window length..... | 358 | +| B.6 Estimation of TX chain amplitude and frequency response parameters..... | 359 | +| B.7 Averaged EVM..... | 361 | +| Annex C (normative): Error Vector Magnitude (FR2)..... | 363 | +| C.1 Reference point for measurement..... | 363 | +| C.2 Basic unit of measurement..... | 363 | +| C.3 Modified signal under test..... | 364 | +| C.4 Estimation of frequency offset..... | 364 | +| C.5 Estimation of time offset..... | 364 | +| C.5.1 General..... | 364 | +| C.5.2 Window length..... | 365 | + +| | | | +|-------------------------------|-------------------------------------------------------------------------------------------|------------| +| C.6 | Estimation of TX chain amplitude and frequency response parameters..... | 366 | +| C.7 | Averaged EVM..... | 368 | +| Annex D (normative): | Characteristics of the interfering signals..... | 370 | +| Annex E: Void | | 371 | +| Annex F (normative): | Relationship between EIRP based regulatory requirements and 3GPP requirements..... | 372 | +| F.1 | General..... | 372 | +| F.2 | Relationship between EIRP based regulatory requirements and conducted requirements..... | 372 | +| F.3 | Relationship between EIRP based regulatory requirements and OTA requirements..... | 373 | +| Annex G (Normative): | Propagation conditions..... | 374 | +| G.1 | Static propagation condition..... | 374 | +| G.2 | Multi-path fading propagation conditions..... | 374 | +| G.2.1 | Delay profiles..... | 374 | +| G.2.1.1 | Delay profiles for FR1..... | 375 | +| G.2.1.2 | Delay profiles for FR2..... | 376 | +| G.2.2 | Combinations of channel model parameters..... | 378 | +| G.2.3 | MIMO Channel Correlation Matrices..... | 379 | +| G.2.3.1 | MIMO Correlation Matrices using Uniform Linear Array (ULA)..... | 379 | +| G.2.3.1.1 | Definition of MIMO Correlation Matrices..... | 379 | +| G.2.3.1.2 | MIMO Correlation Matrices at High, Medium and Low Level..... | 383 | +| G.2.3.2 | Multi-Antenna channel models using cross polarized antennas..... | 385 | +| G.2.3.2.1 | Definition of MIMO Correlation Matrices using cross polarized antennas..... | 386 | +| G.2.3.2.2 | Spatial Correlation Matrices at UE and gNB sides..... | 386 | +| G.2.3.2.2.1 | Spatial Correlation Matrices at UE side..... | 386 | +| G.2.3.2.2.2 | Spatial Correlation Matrices at gNB side..... | 387 | +| G.2.3.2.3 | MIMO Correlation Matrices using cross polarized antennas..... | 387 | +| G.3 | High speed train condition..... | 387 | +| G.4 | Moving propagation conditions..... | 392 | +| Annex H (informative): | Change history..... | 394 | + +## 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 and NB-IoT operation in NR in-band Base Station (BS). + +--- + +## 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] ITU-R Recommendation SM.329: "Unwanted emissions in the spurious domain". +- [3] Recommendation ITU-R SM.328: "Spectra and bandwidth of emissions". +- [4] 3GPP TR 25.942: "RF system scenarios". +- [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] Recommendation ITU-R M.1545: "Measurement uncertainty as it applies to test limits for the terrestrial component of International Mobile Telecommunications-2000". +- [8] "Title 47 of the Code of Federal Regulations (CFR)", Federal Communications Commission. +- [9] 3GPP TS 38.211: "NR; Physical channels and modulation". +- [10] 3GPP TS 38.213: "NR; Physical layer procedures for control". +- [11] 3GPP TS 38.331: "NR; Radio Resource Control (RRC); Protocol specification". +- [12] 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)". +- [13] 3GPP TS 36.104: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) radio transmission and reception". +- [14] 3GPP TS 37.105: "Active Antenna System (AAS) Base Station (BS) transmission and reception". +- [15] 3GPP TS 38.212: "NR; Multiplexing and channel coding". +- [16] 3GPP TR 38.901: "Study on channel model for frequencies from 0.5 to 100 GHz". +- [17] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone". +- [18] 3GPP TS 38.101-2: "NR; User Equipment (UE) radio transmission and reception; Part 2: Range 2 Standalone". +- [19] ERC Recommendation 74-01, "Unwanted emissions in the spurious domain". + +- [20] 3GPP TS 37.213: "Physical layer procedures for shared spectrum channel access". +- [21] 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)" +- [22] 3GPP TR 38.852: Introduction of 1900MHz NR band for Europe for Rail Mobile Radio (RMR) +- [23] 3GPP TR 38.853: Introduction of 900MHz NR band for Europe for Rail Mobile Radio (RMR) +- [24] FCC Report And Order And Further Notice Of Proposed Rulemaking FCC 20-51, April 2020. + +--- + +## 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]. + +**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 [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 BS *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 + +**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-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 + +**BS type 2-O:** NR base station operating at FR2 with a *requirement set* consisting only of OTA requirements defined at the RIB + +**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 + +**co-location reference antenna:** a passive antenna used as reference for base station to base station co-location 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)*. + +**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). + +**fractional bandwidth:** *fractional bandwidth* FBW is defined as + +**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 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 + +**multi-band connector:** *Antenna Connector of BS type 1-C* or *TAB connector of 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-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* + +**Multi-carrier transmission configuration:** set of one or more contiguous or non-contiguous carriers that a NR 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 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 RESENS 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 *BS 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 base station 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 BS operating in single carrier, multi-carrier, or carrier aggregation configurations that the manufacturer has declared to be available at the RIB during the *transmitter ON period* + +**rated 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 *BS types 1-H* or *BS 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 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* + +**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 BS direction setting + +**single-band connector:** *BS type 1-C antenna connector* or *BS 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*. + +**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. + +**sub-block bandwidth:** bandwidth of one *sub-block*. + +**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:** 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 *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 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 UE or BS, measured in resource block units + +**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 + +**UE transmission bandwidth configuration:** set of resource blocks located within the UE channel bandwidth which may be used for transmitting or receiving by the UE + +**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 | +| $BeW_{\theta,REFSENS}$ | Beamwidth equivalent to the OTA REFSENS RoAoA in the $\theta$ -axis in degrees. Applicable for FR1 only. | +| $BeW_{\phi,REFSENS}$ | Beamwidth equivalent to the OTA REFSENS RoAoA in the $\phi$ -axis in degrees. Applicable for FR1 only. | +| $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 Config | Transmission bandwidth configuration , where $BW_{Config} = N_{RB} \times SCS \times 12$ | +| BW Contiguous | Contiguous transmission bandwidth , i.e. BS channel bandwidth for single carrier or Aggregated BS channel bandwidth for contiguously aggregated carriers. For non-contiguous operation within a band the term is applied per sub-block . | +| BW GB,low | The minimum guard band defined in clause 5.3.3 for lowest assigned component carrier | +| BW GB,high | The minimum guard band defined in clause 5.3.3 for highest assigned component carrier | +| $\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_{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_{Global}$ | Global frequency raster granularity | +| $\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 downlink operating band edge | +| $\Delta f_{OOB}$ | Maximum offset of the out-of-band boundary from the uplink operating band edge | +| $\Delta f_{FR2\_REFSENS}$ | Offset applied to the FR2 OTA REFSENS depending on the AoA | +| $\Delta minSENS$ | Difference between conducted reference sensitivity and minSENS | +| $\Delta OTA\_REFSENS$ | Difference between conducted reference sensitivity and OTA REFSENS | +| $\Delta F_{Raster}$ | Channel raster granularity | +| $\Delta shift$ | Channel raster offset for SUL | +| 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 BS channel bandwidth | +| F FB,high | Highest supported frequency within supported operating band , for which fractional bandwidth support was declared | +| F FB,low | Lowest supported frequency within supported operating band , for which fractional bandwidth support was declared | +| F C | RF reference frequency on the channel raster, given in table 5.4.2.2-1 | +| F C,block,high | F C of the highest transmitted/received carrier in a sub-block . | +| F C,block,low | F C of the lowest transmitted/received carrier in a sub-block . | +| 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 BS Channel Bandwidth , expressed in MHz. $F_{edge,low} = F_{C,low} - F_{offset,low}$ . | +| F edge,high | The upper edge of Aggregated BS Channel Bandwidth , expressed in MHz. $F_{edge,high} = F_{C,high} + F_{offset,high}$ . | +| F edge,block,low | The lower sub-block edge , where $F_{edge,block,low} = F_{C,block,low} - F_{offset,low}$ . | +| F edge,block,high | The upper sub-block edge , where $F_{edge,block,high} = F_{C,block,high} + F_{offset,high}$ . | +| F filter | Filter centre frequency | +| F offset,high | Frequency offset from F C,high to the upper Base Station RF Bandwidth edge , or from F C,block,high to the upper sub-block edge | +| F offset,low | Frequency offset from F C,low to the lower Base Station RF Bandwidth edge , or from F C,block,low to the lower sub-block edge . | +| f _BE_offset | Separation between the edge of the last transmitted channel of the channels assigned for NR-U channel bandwidth and the centre of the measuring | +| f _offset | Separation between the channel edge frequency and the centre of the measuring | +| f _offsetmax | The offset to the frequency $\Delta f_{OBUE}$ outside the downlink operating band | +| F REF | RF reference frequency | +| F REF-Offs | Offset used for calculating F REF | +| F REF,shift | RF reference frequency for Supplementary Uplink (SUL) bands | +| 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 | +| GB Channel | Minimum guard band defined in clause 5.3.3 | +| N 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 RB | Physical resource block number | +| N RB | Transmission bandwidth configuration , expressed in resource blocks | + +| | | +|---------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $N_{\text{RB,high}}$ | Transmission bandwidth configuration for the highest assigned component carrier within a sub-block in CA | +| $N_{\text{RB,low}}$ | Transmission bandwidth configuration for the lowest assigned component carrier within a sub-block in CA | +| $N_{\text{REF}}$ | NR Absolute Radio Frequency Channel Number (NR-ARFCN) | +| $N_{\text{REF-offset}}$ | Offset used for calculating $N_{\text{REF}}$ | +| $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/n75,ind}}$ | Declared emission level for Band n50/n75; ind = a, b | +| $P_{\text{EM,n54,ind}}$ | Declared emission level for Band n54; ind = a, b, c, d, e, f | +| $P_{\text{EIRP,N}}$ | EIRP level for channel N | +| $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{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 NR BS is configured at the maximum rated carrier output TRP ( $P_{\text{rated,c,TRP}}$ ) | +| $P_{\text{rated,c,AC}}$ | The rated carrier output power per antenna connector | +| $P_{\text{rated,c,cell}}$ | The rated carrier output power per TAB connector TX min cell group | +| $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,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{rated,t,TRP}}$ | Rated total TRP output power declared per RIB | +| $P_{\text{REFSENS}}$ | Conducted Reference Sensitivity power level | +| $\text{SCS}_{\text{low}}$ | Sub-Carrier Spacing for the lowest assigned component carrier within a sub-block in CA | +| $\text{SCS}_{\text{high}}$ | Sub-Carrier Spacing for the highest assigned component carrier within a sub-block in CA | +| $\text{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 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 | +| AAS | Active Antenna System | +| ACLR | Adjacent Channel Leakage Ratio | +| ACS | Adjacent Channel Selectivity | +| AoA | Angle of Arrival | +| AWGN | Additive White Gaussian Noise | +| BS | Base Station | +| BW | Bandwidth | +| CA | Carrier Aggregation | +| CACLR | Cumulative ACLR | + +| | | +|------------|------------------------------------------------------------------------| +| CPE | Common Phase Error | +| CP-OFDM | Cyclic Prefix-OFDM | +| CW | Continuous Wave | +| DFT-s-OFDM | Discrete Fourier Transform-spread-OFDM | +| DM-RS | Demodulation Reference Signal | +| EIS | Equivalent Isotropic Sensitivity | +| EIRP | Effective Isotropic Radiated Power | +| E-UTRA | Evolved UTRA | +| EVM | Error Vector Magnitude | +| FBW | Fractional Bandwidth | +| FR | Frequency Range | +| FRC | Fixed Reference Channel | +| GSCN | Global Synchronization Channel Number | +| GSM | Global System for Mobile communications | +| HAPS | High Altitude Platform Station | +| ITU-R | Radiocommunication Sector of the International Telecommunication Union | +| ICS | In-Channel Selectivity | +| LA | Local Area | +| LNA | Low Noise Amplifier | +| MCS | Modulation and Coding Scheme | +| 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 | +| OOB | Out-of-band | +| 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 | +| QAM | Quadrature Amplitude Modulation | +| RB | Resource Block | +| RX | Receiver | +| SCS | Sub-Carrier Spacing | +| SDL | Supplementary Downlink | +| SS | Synchronization Symbol | +| SSB | Synchronization Signal Block | +| SUL | Supplementary Uplink | +| TAB | Transceiver Array Boundary | +| TAE | Time Alignment Error | +| TDL | Tapped Delay Line | +| TX | Transmitter | +| TRP | Total Radiated Power | +| UCI | Uplink Control Information | +| UEM | Unwanted Emissions Mask | +| UTRA | Universal Terrestrial Radio Access | +| WA | Wide Area | +| ZF | Zero Forcing | + +## 4 General + +### 4.1 Relationship with other core specifications + +The present document is a single-RAT specification for a BS, covering RF characteristics and minimum performance requirements. Conducted and radiated core requirements are defined for the BS architectures and BS types defined in clause 4.3. + +The applicability of each requirement is described in clause 5. + +### 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.141-1 [5] and TS 38.141-2 [6]. + +The minimum requirements given in this specification make no allowance for measurement uncertainty. The test specifications TS 38.141-1 [5] and TS 38.141-2 [6] 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 [7]. + +### 4.3 Conducted and radiated requirement reference points + +#### 4.3.1 BS type 1-C + +For *BS type 1-C*, the 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 the signal path from the BS cabinet through external devices to the antenna connector.](88a6d9692a52989caa6b208a1ba70dc0_img.jpg) + +The diagram illustrates the transmitter interface for BS type 1-C. It shows a signal path starting from the BS cabinet, passing through an External PA (if any), and then through an External device (e.g., TX filter, if any). The signal is then directed towards the antenna connector. Port A is indicated at the BS cabinet, and Port B is indicated at the far end of the external device. + +``` +graph LR; BS[BS cabinet] -- Port A --> PA[External PA (if any)]; PA --> TX[External device e.g. TX filter (if any)]; TX -- Port B --> Antenna[Towards antenna connector] +``` + +Diagram of BS type 1-C transmitter interface showing the signal path from the BS cabinet through external devices to the antenna connector. + +Figure 4.3.1-1: BS type 1-C transmitter interface + +![Figure 4.3.1-2: BS type 1-C receiver interface diagram. It shows a 'BS cabinet' connected to an 'External LNA (if any)' which is connected to an 'External device e.g. RX filter (if any)'. Port A is at the interface between the BS cabinet and the External LNA. Port B is at the interface between the External device and an antenna connector labeled 'From antenna connector'.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +Figure 4.3.1-2: BS type 1-C receiver interface diagram. It shows a 'BS cabinet' connected to an 'External LNA (if any)' which is connected to an 'External device e.g. RX filter (if any)'. Port A is at the interface between the BS cabinet and the External LNA. Port B is at the interface between the External device and an antenna connector labeled 'From antenna connector'. + +Figure 4.3.1-2: BS type 1-C receiver interface + +### 4.3.2 BS type 1-H + +For BS type 1-H, the requirements are defined for two points of reference, signified by radiated requirements and conducted requirements. + +![Figure 4.3.2-1: Radiated and conducted reference points for BS type 1-H diagram. It shows a 'Transceiver unit array (TRXUA) 1 to M' on the left, connected via multiple lines labeled #1, #2, ..., #K to a 'Composite antenna' on the right. The 'Composite antenna' contains a 'Radio Distribution Network (RDN)' and an 'Antenna Array (AA)'. A vertical dashed line labeled 'Transceiver array boundary' is at the connection points. A vertical dashed line labeled 'Radiated interface boundary' is at the outer edge of the antenna array. An arrow points to the connection points labeled 'Transceiver array boundary connector (TAB)'.](20136850feb70fd71c7d41cdae203ebb_img.jpg) + +Figure 4.3.2-1: Radiated and conducted reference points for BS type 1-H diagram. It shows a 'Transceiver unit array (TRXUA) 1 to M' on the left, connected via multiple lines labeled #1, #2, ..., #K to a 'Composite antenna' on the right. The 'Composite antenna' contains a 'Radio Distribution Network (RDN)' and an 'Antenna Array (AA)'. A vertical dashed line labeled 'Transceiver array boundary' is at the connection points. A vertical dashed line labeled 'Radiated interface boundary' is at the outer edge of the antenna array. An arrow points to the connection points labeled 'Transceiver array boundary connector (TAB)'. + +Figure 4.3.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. + +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.3 BS type 1-O and BS type 2-O + +For BS type 1-O and BS type 2-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. + +![Diagram of radiated reference points for BS type 1-O and BS type 2-O. It shows three main components: Transceiver unit array (TRXUA) 1 to P, Radio Distribution Network (RDN), and Antenna Array (AA). These components are enclosed in a dashed box. A vertical dashed line to the right of the box is labeled 'Radiated interface boundary'.](4cde160bcc69b7b6c81b648dd0e4252e_img.jpg) + +The diagram illustrates the internal components of a base station and its radiated interface. On the left, a large dashed rectangle contains the 'Transceiver unit array (TRXUA) 1 to P'. In the center, a smaller dashed rectangle contains the 'Radio Distribution Network (RDN)'. On the right, another dashed rectangle contains the 'Antenna Array (AA)'. These three rectangles are adjacent to each other. To the right of the 'Antenna Array (AA)' is a vertical dashed line labeled 'Radiated interface boundary', which represents the boundary over which the radiated characteristics are defined. + +Diagram of radiated reference points for BS type 1-O and BS type 2-O. It shows three main components: Transceiver unit array (TRXUA) 1 to P, Radio Distribution Network (RDN), and Antenna Array (AA). These components are enclosed in a dashed box. A vertical dashed line to the right of the box is labeled 'Radiated interface boundary'. + +**Figure 4.3.3-1: Radiated reference points for BS type 1-O and BS type 2-O** + +Co-location requirements are specified at the conducted interface of the *co-location reference antenna*, the *co-location reference antenna* does not form part of the BS under test but is a means to provide OTA power levels which are representative of a co-located system, further defined in clause 4.9. + +For a BS type 1-O the transceiver unit array must contain at least 8 transmitter units and at least 8 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. + +## 4.4 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. The associated deployment scenarios for each class are exactly the same for BS with and without connectors. + +For BS type 1-O and 2-O, BS classes are defined as indicated below: + +- Wide Area Base Stations are characterised by requirements derived from Macro Cell scenarios with a BS to UE minimum distance along the ground equal to 35 m. +- Medium Range Base Stations are characterised by requirements derived from Micro Cell scenarios with a BS to UE minimum distance along the ground equal to 5 m. +- Local Area Base Stations are characterised by requirements derived from Pico Cell scenarios with a BS to UE minimum distance along the ground equal to 2 m. + +For BS type 1-C and 1-H, BS classes 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. + +NOTE: Local Are Base stations are applicable also in Femto Cell scenarios. + +For BS *type 1-C, 1-H and 1-O*, HAPS BS class is defined as indicated below: + +- HAPS Base Stations are characterised by requirements derived from High Altitude Platform scenarios with a BS to ground UE minimum distance of typically around 20km. +- Unless otherwise stated, HAPS BS class would refer to Wide Area BS class, which is specified in clause 4.4. + +## 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 | Some NR operating bands may be applied regionally. | +| 6.2.1,
9.3.1 | Base station output power,
OTA base station output power: | For Band n41 and n90 operation in Japan, additional output power limits shall be applied. | +| 6.2.4,
9.3.4 | Base station output power,
OTA base station output power:
Additional requirements | These requirements may be applied regionally as additional base station output power requirements.
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.2,
9.7.2 | Occupied bandwidth,
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. | +| 6.6.3.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.2,
9.7.4.2 | Operating band unwanted emission,
OTA operating band unwanted emissions | Category A or Category B operating band unwanted emissions limits may be applied regionally.
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. | +| 6.6.4.2.5.1,
9.7.4.2.1.2 | Operating band unwanted emission,
OTA 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.2.5.2,
9.7.4.2.1.1 | Operating band unwanted emission,
OTA operating band unwanted emissions
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.3 | Operating band unwanted emissions | 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.2.1,
9.7.5.2 | Tx spurious emissions,
OTA Tx spurious emissions | Category A or Category B spurious emission limits, as defined in ITU-R Recommendation SM.329 [2], may apply regionally.
The emission limits for BS type 1-H and BS type 1-O 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.2.3,
9.7.5.3.3 | Tx spurious emissions:
additional requirements,
OTA Tx 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.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.2.1.1,
6.7.3.1.1
9.8.2 | Transmitter intermodulation,
OTA 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.2.2,
6.7.3.3 | Transmitter intermodulation | For Band n41 and n90 operation in Japan, the BS may have to comply with the additional requirements, when deployed in certain regions. | +| 6.7.2.2,
6.7.3.3,
9.8.3 | Transmitter intermodulation,
OTA 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.3 | Rx spurious emissions, | For Band n41 and n90 operation in Japan, the emission limits for BS type 1-C may apply to the sum of the emission power over all antenna connectors . | + +| Clause number | Requirement | Comments | +|----------------------------|-----------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 7.6.4,
10.7.2
10.7.3 | Rx spurious emissions,
OTA Rx spurious emissions | The emission limits for BS type 1-H and BS type 1-O specified as the basic limit + X (dB) are applicable, unless stated differently in regional regulation.
Additional limits for BS type 2-O may apply regionally. | + +## 4.6 Applicability of 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 | | | | +|--------------------------------------|-----------------|-------------|-------------|-------------| +| | BS type 1-C | BS type 1-H | BS type 1-O | BS type 2-O | +| 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 | 6.6.3 | | | +| Operating band unwanted emissions | 6.6.4 | 6.6.4 | | | +| Transmitter spurious emissions | 6.6.5 | 6.6.5 | | | +| Transmitter intermodulation | 6.7 | 6.7 | NA | NA | +| 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 | 7.6 | | | +| Receiver intermodulation | 7.7 | 7.7 | | | +| In-channel selectivity | 7.8 | 7.8 | | | +| Performance requirements | 8 | 8 | | | +| Radiated transmit power | | 9.2 | 9.2 | 9.2 | +| OTA base station output power | | | 9.3 | 9.3 | +| OTA output power dynamics | | | 9.4 | 9.4 | +| OTA transmit ON/OFF power | | | 9.5 | 9.5 | +| OTA transmitted signal quality | | | 9.6 | 9.6 | +| OTA occupied bandwidth | | | 9.7.2 | 9.7.2 | +| OTA ACLR | | NA | 9.7.3 | 9.7.3 | +| OTA out-of-band emission | | | 9.7.4 | 9.7.4 | +| OTA transmitter spurious emission | | | 9.7.5 | 9.7.5 | +| OTA transmitter intermodulation | | | 9.8 | NA | +| OTA sensitivity | | 10.2 | 10.2 | NA | +| OTA reference sensitivity level | NA | | 10.3 | 10.3 | +| OTA dynamic range | | | 10.4 | NA | +| OTA in-band selectivity and blocking | | | 10.5 | 10.5 | +| OTA out-of-band blocking | | | 10.6 | 10.6 | +| OTA receiver spurious emission | | | 10.7 | 10.7 | +| OTA receiver intermodulation | | | 10.8 | 10.8 | +| OTA in-channel selectivity | | | 10.9 | 10.9 | +| Radiated performance requirements | | | 11 | 11 | + +## 4.7 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.8 Requirements for BS capable of multi-band operation + +For *multi-band connector* or *multi-band RIB*, the RF requirements in clause 6, 7, 9 and 10 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 connector(s)*, and *multi-band RIB(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 *antenna 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 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*. + +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. + +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. + +BS type 1-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 1-O* capability of operation in multiple *operating bands*. + +For *multi-band connectors* and *multi-band RIBs* supporting the bands for TDD, the RF requirements in the present specification assume no simultaneous uplink and downlink occur between the bands. + +The RF requirements for *multi-band connectors* and *multi-band RIBs* supporting bands for both FDD and TDD are not covered by the present release of this specification. + +## 4.9 OTA co-location with other base stations + +Co-location requirements are requirements which are based on assuming the *BS type 1-O* is co-located with another BS of the same base station class, they ensure that both co-located systems can operate with minimal degradation to each other. + +Unwanted emission and out of band blocking co-location requirements are optional requirements based on declaration. TX OFF and TX IMD are mandatory requirements and have the form of a co-location requirement as it represents the worst-case scenario of all the interference cases. + +NOTE: Due to the low level of the unwanted emissions for the spurious emissions and TX OFF level co-location is the most suitable method to show conformance. + +The *co-location reference antenna* shall be a single column passive antenna which has the same vertical radiating dimension (*h*), frequency range, polarization, as the composite antenna of the *BS type 1-O* and nominal 65° horizontal half-power beamwidth (suitable for 3-sector deployment) and is placed at a distance *d* from the edge of the *BS type 1-O*, as shown in figure 4.9-1. + +![Figure 4.9-1: Illustration of BS type 1-O enclosure and co-location reference antenna. The diagram shows two views: Front View and Top View. In the Front View, a rectangular box labeled 'BS type 1-O' is on the left, with an arrow pointing to its left edge labeled 'Enclosure'. To its right is a taller rectangular box labeled 'Co-location Reference antenna'. A horizontal double-headed arrow between them is labeled 'd'. A vertical double-headed arrow on the right of the reference antenna is labeled 'h'. The label 'Front View' is to the right of the reference antenna. In the Top View, separated by a dashed line, two semi-circular shapes are shown. The left one is labeled 'Radiatingface' and the right one is also labeled 'Radiatingface'. A horizontal double-headed arrow between them is labeled 'd'. The label 'Top View' is to the right of the right radiating face.](f324fbc5d5af1e4da9cd932389f0064c_img.jpg) + +Figure 4.9-1: Illustration of BS type 1-O enclosure and co-location reference antenna. The diagram shows two views: Front View and Top View. In the Front View, a rectangular box labeled 'BS type 1-O' is on the left, with an arrow pointing to its left edge labeled 'Enclosure'. To its right is a taller rectangular box labeled 'Co-location Reference antenna'. A horizontal double-headed arrow between them is labeled 'd'. A vertical double-headed arrow on the right of the reference antenna is labeled 'h'. The label 'Front View' is to the right of the reference antenna. In the Top View, separated by a dashed line, two semi-circular shapes are shown. The left one is labeled 'Radiatingface' and the right one is also labeled 'Radiatingface'. A horizontal double-headed arrow between them is labeled 'd'. The label 'Top View' is to the right of the right radiating face. + +**Figure 4.9-1: Illustration of *BS type 1-O* enclosure and co-location reference antenna** + +Edge-to-edge separation *d* between the *BS type 1-O* and the *co-location reference antenna* shall be set to 0.1 m. + +The *BS type 1-O* and the *co-location reference antenna* shall be aligned in a common plane perpendicular to the mechanical bore-sight direction, as shown in figure 4.9-1. + +The *co-location reference antenna* and the *BS type 1-O* can have different width. + +The vertical radiating regions of the *co-location reference antenna* and the *BS type 1-O* composite antenna shall be aligned. + +For co-location requirements where the frequency range of the signal at the *co-location reference antenna* is different from the *BS type 1-O*, a *co-location reference antenna* suitable for the frequency stated in the requirement is assumed. + +OTA co-location requirements are based on the power at the conducted interface of a *co-location reference antenna*, depending on the requirement this interface is either an input or an output. For *BS type 1-O* with dual polarization the *co-location reference antenna* has two conducted interfaces each representing one polarization. + +## 5 Operating bands and channel arrangement + +### 5.1 General + +The channel arrangements presented in this clause are based on the *operating bands* and *BS channel bandwidths* defined in the present release of specifications. + +NOTE: Other *operating bands* and *BS 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 NR can operate according to the present version of the specification are identified as described in table 5.1-1. Whenever FR2 is referred, both FR2-1 and FR2-2 frequency sub-ranges shall be applied, unless otherwise stated. + +**Table 5.1-1: Definition of frequency ranges** + +| Frequency range designation | | Corresponding frequency range | +|-----------------------------|-------|-------------------------------| +| FR1 | | 410 MHz – 7125 MHz | +| FR2 | FR2-1 | 24250 MHz – 52600 MHz | +| | FR2-2 | 52600 MHz – 71000 MHz | + +### 5.2 Operating bands + +NR is designed to operate in the *operating bands* defined in table 5.2-1 and 5.2-2. + +NR operating band n1, which is defined in Table 5.2-1, can be applied for HAPS operation. + +NB-IoT is designed to operate in the NR operating bands n1, n2, n3, n5, n7, n8, n12, n13, n14, n18, n20, n25, n26, n28, n31, n41, n65, n66, n70, n71, n72, n74, n85, n90, n106 which are defined in Table 5.2-1. + +**Table 5.2-1: NR *operating bands* in FR1** + +| 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 | +| n2 | 1850 MHz – 1910 MHz | 1930 MHz – 1990 MHz | FDD | +| n3 | 1710 MHz – 1785 MHz | 1805 MHz – 1880 MHz | FDD | +| n5 | 824 MHz – 849 MHz | 869 MHz – 894 MHz | FDD | +| n7 | 2500 MHz – 2570 MHz | 2620 MHz – 2690 MHz | FDD | +| n8 | 880 MHz – 915 MHz | 925 MHz – 960 MHz | FDD | +| n12 | 699 MHz – 716 MHz | 729 MHz – 746 MHz | FDD | +| n13 | 777 MHz – 787 MHz | 746 MHz – 756 MHz | FDD | +| n14 | 788 MHz – 798 MHz | 758 MHz – 768 MHz | FDD | +| n18 | 815 MHz – 830 MHz | 860 MHz – 875 MHz | FDD | +| n20 | 832 MHz – 862 MHz | 791 MHz – 821 MHz | FDD | +| n24 7 | 1626.5 MHz – 1660.5 MHz | 1525 MHz – 1559 MHz | FDD | +| n25 | 1850 MHz – 1915 MHz | 1930 MHz – 1995 MHz | FDD | +| n26 | 814 MHz – 849 MHz | 859 MHz – 894 MHz | FDD | +| n28 | 703 MHz – 748 MHz | 758 MHz – 803 MHz | FDD | +| n29 | N/A | 717 MHz – 728 MHz | SDL | +| n30 | 2305 MHz – 2315 MHz | 2350 MHz – 2360 MHz | FDD | +| n31 | 452.5 MHz – 457.5 MHz | 462.5 MHz – 467.5 MHz | FDD | +| n34 | 2010 MHz – 2025 MHz | 2010 MHz – 2025 MHz | TDD | +| n38 | 2570 MHz – 2620 MHz | 2570 MHz – 2620 MHz | TDD | +| n39 | 1880 MHz – 1920 MHz | 1880 MHz – 1920 MHz | TDD | +| n40 | 2300 MHz – 2400 MHz | 2300 MHz – 2400 MHz | TDD | +| n41 | 2496 MHz – 2690 MHz | 2496 MHz – 2690 MHz | TDD | +| n46 | 5150 MHz – 5925 MHz | 5150 MHz – 5925 MHz | TDD(NOTE 3) | +| n48 | 3550 MHz – 3700 MHz | 3550 MHz – 3700 MHz | TDD | +| n50 | 1432 MHz – 1517 MHz | 1432 MHz – 1517 MHz | TDD | +| n51 | 1427 MHz – 1432 MHz | 1427 MHz – 1432 MHz | TDD | +| n53 | 2483.5 MHz – 2495 MHz | 2483.5 MHz – 2495 MHz | TDD | +| n54 | 1670 MHz – 1675 MHz | 1670 MHz – 1675 MHz | TDD | +| n65 | 1920 MHz – 2010 MHz | 2110 MHz – 2200 MHz | FDD | +| n66 | 1710 MHz – 1780 MHz | 2110 MHz – 2200 MHz | FDD | +| n67 | N/A | 738 MHz – 758 MHz | SDL | +| n70 | 1695 MHz – 1710 MHz | 1995 MHz – 2020 MHz | FDD | +| n71 | 663 MHz – 698 MHz | 617 MHz – 652 MHz | FDD | +| n72 | 451 MHz – 456 MHz | 461 MHz – 466 MHz | FDD | +| n74 | 1427 MHz – 1470 MHz | 1475 MHz – 1518 MHz | FDD | +| n75 | N/A | 1432 MHz – 1517 MHz | SDL | +| n76 | N/A | 1427 MHz – 1432 MHz | SDL | +| n77 | 3300 MHz – 4200 MHz | 3300 MHz – 4200 MHz | TDD | +| n78 | 3300 MHz – 3800 MHz | 3300 MHz – 3800 MHz | TDD | +| n79 | 4400 MHz – 5000 MHz | 4400 MHz – 5000 MHz | TDD | +| n80 | 1710 MHz – 1785 MHz | N/A | SUL | +| n81 | 880 MHz – 915 MHz | N/A | SUL | +| n82 | 832 MHz – 862 MHz | N/A | SUL | +| n83 | 703 MHz – 748 MHz | N/A | SUL | +| n84 | 1920 MHz – 1980 MHz | N/A | SUL | +| n85 | 698 MHz – 716 MHz | 728 MHz – 746 MHz | FDD | +| n86 | 1710 MHz – 1780 MHz | N/A | SUL | +| n89 | 824 MHz – 849 MHz | N/A | SUL | +| n90 | 2496 MHz – 2690 MHz | 2496 MHz – 2690 MHz | TDD | +| n91 | 832 MHz – 862 MHz | 1427 MHz – 1432 MHz | FDD(NOTE 2) | +| n92 | 832 MHz – 862 MHz | 1432 MHz – 1517 MHz | FDD(NOTE 2) | +| n93 | 880 MHz – 915 MHz | 1427 MHz – 1432 MHz | FDD(NOTE 2) | +| n94 | 880 MHz – 915 MHz | 1432 MHz – 1517 MHz | FDD(NOTE 2) | +| n95
(NOTE 1) | 2010 MHz – 2025 MHz | N/A | SUL | +| n96
(NOTE 4) | 5925 MHz – 7125 MHz | 5925 MHz – 7125 MHz | TDD(NOTE 3) | +| n97 5 | 2300 MHz – 2400 MHz | N/A | SUL | +| n98 5 | 1880 MHz – 1920 MHz | N/A | SUL | +| n99 6 | 1626.5 MHz – 1660.5 MHz | N/A | SUL | +| n100 | 874.4 MHz – 880 MHz | 919.4 MHz – 925 MHz | FDD | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|---------------------|------------------| +| n101 | 1900 MHz – 1910 MHz | 1900 MHz – 1910 MHz | TDD | +| n102 4 | 5925 MHz – 6425 MHz | 5925 MHz – 6425 MHz | TDD 3 | +| n104 8 | 6425 MHz – 7125 MHz | 6425 MHz – 7125 MHz | TDD | +| n105 | 663 MHz – 703 MHz | 612 MHz – 652 MHz | FDD | +| n106 | 896 MHz – 901 MHz | 935 MHz – 940 MHz | FDD | +| n109 | 703 MHz – 733 MHz | 1432 MHz – 1517 MHz | FDD (NOTE 2) | +| NOTE 1: This band is applicable in China only. | | | | +| NOTE 2: Variable duplex operation does not enable dynamic variable duplex configuration by the network, and is used such that DL and UL frequency ranges are supported independently in any valid frequency range for the band. | | | | +| NOTE 3: This band is restricted to operation with shared spectrum channel access as defined in TS 37.213 [20]. | | | | +| NOTE 4: This band is applicable only in countries/regions designating this band for shared-spectrum access use subject to country-specific conditions. | | | | +| NOTE 5: The requirements for this band are applicable only where no other NR or E-UTRA TDD operating band(s) are used within the frequency range of this band in the same geographical area. For scenarios where other NR or E-UTRA TDD operating band(s) are used within the frequency range of this band in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. | | | | +| NOTE 6: UL operation is restricted to 1627.5 – 1637.5 MHz and 1646.5 – 1656.5 MHz per FCC Order DA 20-48. | | | | +| NOTE 7: DL operation is restricted to 1526-1536 MHz frequency range. UL operation is restricted to 1627.5 – 1637.5 MHz and 1646.5 – 1656.5 MHz per FCC Order 20-51 [24] | | | | +| NOTE 8: This band is applicable only in countries/regions designating this band for IMT licensed operation subject to country-specific conditions. | | | | + +Table 5.2-2: NR operating bands in FR2 + +| NR operating band | Uplink (UL) and Downlink (DL) operating band | Duplex mode | +|-------------------|--------------------------------------------------------------------------------------------------------|-------------| +| | BS transmit/receive
UE transmit/receive
$F_{UL,low} - F_{UL,high}$
$F_{DL,low} - F_{DL,high}$ | | +| n257 | 26500 MHz – 29500 MHz | TDD | +| n258 | 24250 MHz – 27500 MHz | TDD | +| n259 | 39500 MHz – 43500 MHz | TDD | +| n260 | 37000 MHz – 40000 MHz | TDD | +| n261 | 27500 MHz – 28350 MHz | TDD | +| n262 | 47200 MHz – 48200 MHz | TDD | +| n263 | 57000 MHz – 71000 MHz | TDD | + +## 5.3 BS channel bandwidth + +### 5.3.1 General + +The *BS channel bandwidth* supports a single NR RF carrier in the uplink or downlink at the Base Station. Different UE channel bandwidths may be supported within the same spectrum for transmitting to and receiving from UEs connected to the BS. The placement of the UE channel bandwidth is flexible but can only be completely within the *BS channel bandwidth*. The BS 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 guardband 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 NR channel + +### 5.3.2 Transmission bandwidth configuration + +The *transmission bandwidth configuration* $N_{RB}$ for each *BS channel bandwidth* and subcarrier spacing is specified in table 5.3.2-1 for FR1 and table 5.3.2-2 for FR2. + +**Table 5.3.2-1: Transmission bandwidth configuration $N_{RB}$ for FR1** + +| SCS (kHz) | 3 MHz | 5 MHz | 10 MHz | 15 MHz | 20 MHz | 25 MHz | 30 MHz | 35 MHz | 40 MHz | 45 MHz | 50 MHz | 60 MHz | 70 MHz | 80 MHz | 90 MHz | 100 MHz | +|-----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------| +| | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | +| 15 | 15 | 25 | 52 | 79 | 106 | 133 | 160 | 188 | 216 | 242 | 270 | N/A | N/A | N/A | N/A | N/A | +| 30 | N/A | 11 | 24 | 38 | 51 | 65 | 78 | 92 | 106 | 119 | 133 | 162 | 189 | 217 | 245 | 273 | +| 60 | N/A | N/A | 11 | 18 | 24 | 31 | 38 | 44 | 51 | 58 | 65 | 79 | 93 | 107 | 121 | 135 | + +**Table 5.3.2-2: Transmission bandwidth configuration $N_{RB}$ for FR2-1** + +| SCS (kHz) | 50 MHz | 100 MHz | 200 MHz | 400 MHz | +|-----------|----------|----------|----------|----------| +| | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | +| 60 | 66 | 132 | 264 | N/A | +| 120 | 32 | 66 | 132 | 264 | + +**Table 5.3.2-3: Transmission bandwidth configuration $N_{RB}$ for FR2-2** + +| SCS (kHz) | 100 MHz | 400 MHz | 800 MHz | 1600 MHz | 2000 MHz | +|-----------|----------|----------|----------|----------|----------| +| | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | +| 120 | 66 | 264 | N/A | N/A | N/A | +| 480 | N/A | 66 | 124 | 248 | N/A | +| 960 | N/A | 33 | 62 | 124 | 148 | + +NOTE: All Tx and Rx requirements are defined based on *transmission bandwidth configuration* specified in table 5.3.2-1 for FR1 and table 5.3.2-2 and table 5.3.2-3 for FR2. + +The transmission bandwidth configuration for NB-IoT is specified in TS 36.104 [13] clause 5.6. + +### 5.3.3 Minimum guardband and transmission bandwidth configuration + +The minimum guardband for each *BS channel bandwidth* and SCS is specified in table 5.3.3-1 for FR1 and in table 5.3.3-2 and table 5.3.3-2a for FR2. + +**Table 5.3.3-1: Minimum guardband (kHz) (FR1)** + +| SCS (kHz) | 3 MHz | 5 MHz | 10 MHz | 15 MHz | 20 MHz | 25 MHz | 30 MHz | 35 MHz | 40 MHz | 45 MHz | 50 MHz | 60 MHz | 70 MHz | 80 MHz | 90 MHz | 100 MHz | +|-----------|-------|-------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|---------| +| | 142.5 | 242.5 | 312.5 | 382.5 | 452.5 | 522.5 | 592.5 | 572.5 | 552.5 | 712.5 | 692.5 | N/A | N/A | N/A | N/A | N/A | +| 30 | N/A | 505 | 665 | 645 | 805 | 785 | 945 | 925 | 905 | 1065 | 1045 | 825 | 965 | 925 | 885 | 845 | +| 60 | N/A | N/A | 1010 | 990 | 1330 | 1310 | 1290 | 1630 | 1610 | 1590 | 1570 | 1530 | 1490 | 1450 | 1410 | 1370 | + +**Table 5.3.3-2: Minimum guardband (kHz) (FR2-1)** + +| SCS (kHz) | 50 MHz | 100 MHz | 200 MHz | 400 MHz | +|-----------|--------|---------|---------|---------| +| 60 | 1210 | 2450 | 4930 | N/A | +| 120 | 1900 | 2420 | 4900 | 9860 | + +**Table 5.3.3-2a: Minimum guardband (kHz) (FR2-2)** + +| SCS (kHz) | 100 MHz | 400 MHz | 800 MHz | 1600 MHz | 2000 MHz | +|-----------|---------|---------|---------|----------|----------| +| 120 | 2420 | 9860 | N/A | N/A | N/A | +| 480 | N/A | 9680 | 42640 | 85520 | N/A | +| 960 | N/A | 9440 | [42400] | 85280 | 147040 | + +The minimum guardband of SCS 240 kHz SS/PBCH block for each *BS channel bandwidth* is specified in table 5.3.3-3 for FR2. + +**Table 5.3.3-3: Minimum guardband (kHz) of SCS 240 kHz SS/PBCH block (FR2)** + +| SCS (kHz) | 100 MHz | 200 MHz | 400 MHz | +|-----------|---------|---------|---------| +| 240 | 3800 | 7720 | 15560 | + +NOTE: The minimum guardband in Table 5.3.3-3 is applicable only when the SCS 240 kHz SS/PBCH block is placed adjacent to the edge of the *BS channel bandwidth* within which the SS/PBCH block is located. + +The number of RBs configured in any *BS channel bandwidth* shall ensure that the minimum guardband specified in this clause is met. + +![Diagram illustrating BS PRB utilization. A horizontal axis represents frequency (f). A central rectangular block represents the BS channel bandwidth (BW). A vertical line in the center of this block represents the carrier. Two dashed arrows point from the text 'Minimum guard band' to the gaps between the block and the carrier. Another dashed arrow points from the text 'All PRBs falling within BS channel bandwidth not covering the minimum guard band can be used' to the main body of the block.](eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg) + +The diagram shows a horizontal axis labeled 'f' representing frequency. A central rectangular block represents the 'BS channel BW'. A vertical line in the center of this block represents the carrier. Two dashed arrows point from the text 'Minimum guard band' to the gaps between the block and the carrier. Another dashed arrow points from the text 'All PRBs falling within BS channel bandwidth not covering the minimum guard band can be used' to the main body of the block. + +Diagram illustrating BS PRB utilization. A horizontal axis represents frequency (f). A central rectangular block represents the BS channel bandwidth (BW). A vertical line in the center of this block represents the carrier. Two dashed arrows point from the text 'Minimum guard band' to the gaps between the block and the carrier. Another dashed arrow points from the text 'All PRBs falling within BS channel bandwidth not covering the minimum guard band can be used' to the main body of the block. + +**Figure 5.3.3-1: BS PRB utilization** + +In the case that multiple numerologies are multiplexed in the same symbol, the minimum guardband on each side of the carrier is the guardband applied at the configured *BS channel bandwidth* for the numerology that is transmitted/received immediately adjacent to the guard band. + +For FR1, if multiple numerologies are multiplexed in the same symbol and the *BS channel bandwidth* is >50 MHz, the guardband applied adjacent to 15 kHz SCS shall be the same as the guardband defined for 30 kHz SCS for the same *BS channel bandwidth*. + +For FR2, if multiple numerologies are multiplexed in the same symbol and the *BS channel bandwidth* is >200 MHz, the guardband applied adjacent to 60 kHz SCS shall be the same as the guardband defined for 120 kHz SCS for the same *BS channel bandwidth*. + +![Diagram illustrating the guard band definition when transmitting multiple numerologies (X and Y) within a BS channel bandwidth. The diagram shows a dashed box representing the BS channel bandwidth, containing two adjacent blocks labeled 'Numerology X' and 'Numerology Y'. Arrows point from the text 'Guard band defined for numerology X when transmitted across full BS channel BW' to the left edge of the box, and from the text 'Guard band defined for numerology Y when transmitted across full BS channel BW' to the right edge of the box.](c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg) + +Diagram illustrating the guard band definition when transmitting multiple numerologies (X and Y) within a BS channel bandwidth. The diagram shows a dashed box representing the BS channel bandwidth, containing two adjacent blocks labeled 'Numerology X' and 'Numerology Y'. Arrows point from the text 'Guard band defined for numerology X when transmitted across full BS channel BW' to the left edge of the box, and from the text 'Guard band defined for numerology Y when transmitted across full BS channel BW' to the right edge of the box. + +**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. + +**Figure 5.3.3-3: Void** + +**Figure 5.3.3-4: Void** + +**Figure 5.3.3-5: Void** + +## 5.3.4 RB alignment + +For each BS channel bandwidth and each numerology, BS transmission bandwidth configuration must fulfil the minimum guardband requirement specified in clause 5.3.3. + +For each numerology, its common resource blocks are specified in clause 4.4.4.3 in [9], 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 BS by higher layer parameter carrierBandwidth defined in TS 38.331 [11] shall fall within the BS transmission bandwidth configuration. + +## 5.3.5 BS channel bandwidth per operating band + +The requirements in this specification apply to the combination of BS channel bandwidths, SCS and operating bands shown in table 5.3.5-1 for FR1 and in table 5.3.5-2 and table 5.3.5-3 for FR2. The transmission bandwidth configuration in table 5.3.2-1, table 5.3.2-2 and table 5.3.2-3 shall be supported for each of the BS channel bandwidths within the BS capability. The BS channel bandwidths are specified for both the Tx and Rx path. + +**Table 5.3.5-1: BS channel bandwidths and SCS per operating band in FR1** + +| NR Band | SCS (kHz) | BS channel bandwidth (MHz) | | | | | | | | | | | | | | | | +|---------|-----------|----------------------------|---|----|----|----|-----------------|----|----|----|----|----|----|----|----|----|-----| +| | | 3 | 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 | | | | | | +| n5 | 15 | | 5 | 10 | 15 | 20 | 25 7 | | | | | | | | | | | +| | 30 | | | 10 | 15 | 20 | 25 7 | | | | | | | | | | | +| | 60 | | | | | | | | | | | | | | | | | +| | 15 | | 5 | 10 | 15 | 20 | 25 | 30 | 35 | 40 | | 50 | | | | | | + +| NR Band | SCS (kHz) | BS channel bandwidth (MHz) | | | | | | | | | | | | | | | | +|---------|-----------|----------------------------|----------------|-----------------|----|----|-----------------|-----------------|-----------------|----|----|-----------------|-----------------|-----------------|-----------------|-----------------|------------------| +| | | 3 | 5 | 10 | 15 | 20 | 25 | 30 | 35 | 40 | 45 | 50 | 60 | 70 | 80 | 90 | 100 | +| n7 | 30 | | | 10 | 15 | 20 | 25 | 30 | 35 | 40 | | 50 | | | | | | +| | 60 | | | 10 | 15 | 20 | 25 | 30 | 35 | 40 | | 50 | | | | | | +| n8 | 15 | | 5 | 10 | 15 | 20 | 25 7 | 30 7 | 35 7 | | | | | | | | | +| | 30 | | | 10 | 15 | 20 | 25 7 | 30 7 | 35 7 | | | | | | | | | +| | 60 | | | | | | | | | | | | | | | | | +| n12 | 15 | | 5 | 10 | 15 | | | | | | | | | | | | | +| | 30 | | | 10 | 15 | | | | | | | | | | | | | +| | 60 | | | | | | | | | | | | | | | | | +| n13 | 15 | | 5 | 10 | | | | | | | | | | | | | | +| | 30 | | | 10 | | | | | | | | | | | | | | +| | 60 | | | | | | | | | | | | | | | | | +| n14 | 15 | | 5 | 10 | | | | | | | | | | | | | | +| | 30 | | | 10 | | | | | | | | | | | | | | +| | 60 | | | | | | | | | | | | | | | | | +| n18 | 15 | | 5 | 10 | 15 | | | | | | | | | | | | | +| | 30 | | | 10 | 15 | | | | | | | | | | | | | +| | 60 | | | | | | | | | | | | | | | | | +| n20 | 15 | | 5 | 10 | 15 | 20 | | | | | | | | | | | | +| | 30 | | | 10 | 15 | 20 | | | | | | | | | | | | +| | 60 | | | | | | | | | | | | | | | | | +| n24 | 15 | | 5 | 10 | | | | | | | | | | | | | | +| | 30 | | | 10 | | | | | | | | | | | | | | +| | 60 | | | 10 | | | | | | | | | | | | | | +| n25 | 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 | | | | | | | +| n26 | 15 | 3 | 5 | 10 | 15 | 20 | 25 7 | 30 7 | | | | | | | | | | +| | 30 | | | 10 | 15 | 20 | 25 7 | 30 7 | | | | | | | | | | +| n28 | 15 | 3 | 5 | 10 | 15 | 20 | 25 | 30 | | 40 | | | | | | | | +| | 30 | | | 10 | 15 | 20 | 25 | 30 | | 40 | | | | | | | | +| | 60 | | | | | | | | | | | | | | | | | +| n29 | 15 | | 5 | 10 | | | | | | | | | | | | | | +| | 30 | | | 10 | | | | | | | | | | | | | | +| | 60 | | | | | | | | | | | | | | | | | +| n30 | 15 | | 5 | 10 | | | | | | | | | | | | | | +| | 30 | | | 10 | | | | | | | | | | | | | | +| | 60 | | | | | | | | | | | | | | | | | +| n31 | 15 | 3 | 5 | | | | | | | | | | | | | | | +| | 30 | | | | | | | | | | | | | | | | | +| | 60 | | | | | | | | | | | | | | | | | +| n34 | 15 | | 5 | 10 | 15 | | | | | | | | | | | | | +| | 30 | | | 10 | 15 | | | | | | | | | | | | | +| | 60 | | | 10 | 15 | | | | | | | | | | | | | +| n38 | 15 | | 5 | 10 | 15 | 20 | 25 | 30 | | 40 | | | | | | | | +| | 30 | | | 10 | 15 | 20 | 25 | 30 | | 40 | | | | | | | | +| | 60 | | | 10 | 15 | 20 | 25 | 30 | | 40 | | | | | | | | +| n39 | 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 | | | | | | | | +| n40 | 15 | | 5 4 | 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 | +| n41 | 15 | | 5 8 | 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 | +| n46 | 15 | | | 10 6 | | 20 | | | | 40 | | | | | | | | +| | 30 | | | 10 6 | | 20 | | | | 40 | | | 60 | | 80 | | 100 | +| | 60 | | | 10 6 | | 20 | | | | 40 | | | 60 | | 80 | | 100 | +| n48 | 15 | | 5 2 | 10 | 15 | 20 | | 30 | | 40 | | 50 1 | | | | | | +| | 30 | | | 10 | 15 | 20 | | 30 | | 40 | | 50 1 | 60 1 | 70 1 | 80 1 | 90 1 | 100 1 | +| | 60 | | | 10 | 15 | 20 | | 30 | | 40 | | 50 1 | 60 1 | 70 1 | 80 1 | 90 1 | 100 1 | +| n50 | 15 | | 5 2 | 10 | 15 | 20 | | 30 | | 40 | | 50 | | | | | | +| | 30 | | | 10 | 15 | 20 | | 30 | | 40 | | 50 | 60 | | 80 | | | + +| NR Band | SCS (kHz) | BS channel bandwidth (MHz) | | | | | | | | | | | | | | | | +|---------|-----------|----------------------------|---|----|----|----|----|----|----|----|----|----|----|----|----|----|-----| +| | | 3 | 5 | 10 | 15 | 20 | 25 | 30 | 35 | 40 | 45 | 50 | 60 | 70 | 80 | 90 | 100 | +| n51 | 60 | | | 10 | 15 | 20 | | 30 | | 40 | | 50 | 60 | | 80 | | | +| | 15 | | 5 | | | | | | | | | | | | | | | +| | 30 | | | | | | | | | | | | | | | | | +| | 60 | | | | | | | | | | | | | | | | | +| n53 | 15 | | 5 | 10 | | | | | | | | | | | | | | +| | 30 | | | 10 | | | | | | | | | | | | | | +| | 60 | | | 10 | | | | | | | | | | | | | | +| n54 | 15 | | 5 | | | | | | | | | | | | | | | +| n65 | 15 | | 5 | 10 | 15 | 20 | | | | | | 50 | | | | | | +| | 30 | | | 10 | 15 | 20 | | | | | | 50 | | | | | | +| | 60 | | | 10 | 15 | 20 | | | | | | 50 | | | | | | +| 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 | | | | | | | +| n67 | 15 | | 5 | 10 | 15 | 20 | | | | | | | | | | | | +| | 30 | | | 10 | 15 | 20 | | | | | | | | | | | | +| | 60 | | | | | | | | | | | | | | | | | +| n70 | 15 | | 5 | 10 | 15 | 20 | 25 | | | | | | | | | | | +| | 30 | | | 10 | 15 | 20 | 25 | | | | | | | | | | | +| | 60 | | | 10 | 15 | 20 | 25 | | | | | | | | | | | +| n71 | 15 | | 5 | 10 | 15 | 20 | 25 | 30 | 35 | | | | | | | | | +| | 30 | | | 10 | 15 | 20 | 25 | 30 | 35 | | | | | | | | | +| | 60 | | | | | | | | | | | | | | | | | +| n72 | 15 | 3 | 5 | | | | | | | | | | | | | | | +| | 30 | | | | | | | | | | | | | | | | | +| | 60 | | | | | | | | | | | | | | | | | +| n74 | 15 | | 5 | 10 | 15 | 20 | | | | | | | | | | | | +| | 30 | | | 10 | 15 | 20 | | | | | | | | | | | | +| | 60 | | | 10 | 15 | 20 | | | | | | | | | | | | +| n75 | 15 | | 5 | 10 | 15 | 20 | 25 | 30 | | 40 | | 50 | | | | | | +| | 30 | | | 10 | 15 | 20 | 25 | 30 | | 40 | | 50 | | | | | | +| | 60 | | | 10 | 15 | 20 | 25 | 30 | | 40 | | 50 | | | | | | +| n76 | 15 | | 5 | | | | | | | | | | | | | | | +| | 30 | | | | | | | | | | | | | | | | | +| | 60 | | | | | | | | | | | | | | | | | +| n77 | 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 | +| 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 | +| n79 | 15 | | | 10 | | 20 | | 30 | | 40 | | 50 | | | | | | +| | 30 | | | 10 | | 20 | | 30 | | 40 | | 50 | 60 | 70 | 80 | 90 | 100 | +| | 60 | | | 10 | | 20 | | 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 | | | | | | | | +| n81 | 15 | | 5 | 10 | 15 | 20 | | | | | | | | | | | | +| | 30 | | | 10 | 15 | 20 | | | | | | | | | | | | +| | 60 | | | | | | | | | | | | | | | | | +| n82 | 15 | | 5 | 10 | 15 | 20 | | | | | | | | | | | | +| | 30 | | | 10 | 15 | 20 | | | | | | | | | | | | +| | 60 | | | | | | | | | | | | | | | | | +| n83 | 15 | | 5 | 10 | 15 | 20 | 25 | 30 | | 40 | | | | | | | | +| | 30 | | | 10 | 15 | 20 | 25 | 30 | | 40 | | | | | | | | +| | 60 | | | | | | | | | | | | | | | | | +| n84 | 15 | | 5 | 10 | 15 | 20 | 25 | 30 | | 40 | | 50 | | | | | | +| | 30 | | | 10 | 15 | 20 | 25 | 30 | | 40 | | 50 | | | | | | +| | 60 | | | 10 | 15 | 20 | 25 | 30 | | 40 | | 50 | | | | | | +| n85 | 15 | 3 | 5 | 10 | 15 | | | | | | | | | | | | | +| | 30 | | | 10 | 15 | | | | | | | | | | | | | +| | 60 | | | | | | | | | | | | | | | | | +| | 15 | | 5 | 10 | 15 | 20 | | | | 40 | | | | | | | | + +| NR Band | SCS (kHz) | BS channel bandwidth (MHz) | | | | | | | | | | | | | | | | +|----------------|------------------|-----------------------------------|----------|-----------------|-----------|-----------|-----------|-----------|-----------|-----------|-----------|-----------|-----------|-----------|-----------|-----------|------------| +| | | 3 | 5 | 10 | 15 | 20 | 25 | 30 | 35 | 40 | 45 | 50 | 60 | 70 | 80 | 90 | 100 | +| n86 | 30 | | | 10 | 15 | 20 | | | | 40 | | | | | | | | +| | 60 | | | 10 | 15 | 20 | | | | 40 | | | | | | | | +| n89 | 15 | | 5 | 10 | 15 | 20 | | | | | | | | | | | | +| | 30 | | | 10 | 15 | 20 | | | | | | | | | | | | +| | 60 | | | | | | | | | | | | | | | | | +| n90 | 15 | | 5 | 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 | +| n91 | 15 | | 5 | 10 3 | | | | | | | | | | | | | | +| | 30 | | | | | | | | | | | | | | | | | +| | 60 | | | | | | | | | | | | | | | | | +| n92 | 15 | | 5 | 10 | 15 | 20 | | | | | | | | | | | | +| | 30 | | | 10 | 15 | 20 | | | | | | | | | | | | +| | 60 | | | | | | | | | | | | | | | | | +| n93 | 15 | | 5 | 10 3 | | | | | | | | | | | | | | +| | 30 | | | | | | | | | | | | | | | | | +| | 60 | | | | | | | | | | | | | | | | | +| n94 | 15 | | 5 | 10 | 15 | 20 | | | | | | | | | | | | +| | 30 | | | 10 | 15 | 20 | | | | | | | | | | | | +| | 60 | | | | | | | | | | | | | | | | | +| n95 | 15 | | 5 | 10 | 15 | | | | | | | | | | | | | +| | 30 | | | 10 | 15 | | | | | | | | | | | | | + +| NR Band | SCS (kHz) | BS channel bandwidth (MHz) | | | | | | | | | | | | | | | | +|---------|-----------|----------------------------|----|----|----|----|-----------------|-----------------|-----------------|----|-----------------|----|----|----|----|----|-----| +| | | 3 | 5 | 10 | 15 | 20 | 25 | 30 | 35 | 40 | 45 | 50 | 60 | 70 | 80 | 90 | 100 | +| n96 | 60 | | | 10 | 15 | | | | | | | | | | | | | +| | 15 | | | | | 20 | | | | 40 | | | | | | | | +| | 30 | | | | | 20 | | | | 40 | | | 60 | | 80 | | 100 | +| | 60 | | | | | 20 | | | | 40 | | | 60 | | 80 | | 100 | +| n97 | 15 | | 5 | 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 | +| n98 | 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 | | | | | | | | +| n99 | 15 | | 5 | 10 | | | | | | | | | | | | | | +| | 30 | | | 10 | | | | | | | | | | | | | | +| | 60 | | | 10 | | | | | | | | | | | | | | +| n100 | 15 | 3 | 5 | | | | | | | | | | | | | | | +| | 30 | | | | | | | | | | | | | | | | | +| | 60 | | | | | | | | | | | | | | | | | +| n101 | 15 | | 5 | 10 | | | | | | | | | | | | | | +| | 30 | | | 10 | | | | | | | | | | | | | | +| | 60 | | | | | | | | | | | | | | | | | +| n102 | 15 | | | | | 20 | | | | 40 | | | | | | | | +| | 30 | | | | | 20 | | | | 40 | | | 60 | | 80 | | 100 | +| | 60 | | | | | 20 | | | | 40 | | | 60 | | 80 | | 100 | +| n104 | 15 | | | | | 20 | | 30 | | 40 | | 50 | | | | | | +| | 30 | | | | | 20 | | 30 | | 40 | | 50 | 60 | 70 | 80 | 90 | 100 | +| | 60 | | | | | 20 | | 30 | | 40 | | 50 | 60 | 70 | 80 | 90 | 100 | +| n105 | 15 | | 5 | 10 | 15 | 20 | 25 7 | 30 7 | 35 7 | | | | | | | | | +| | 30 | | | 10 | 15 | 20 | 25 7 | 30 7 | 35 7 | | | | | | | | | +| | 60 | | | | | | | | | | | | | | | | | +| n106 | 15 | 3 | | | | | | | | | | | | | | | | +| | 30 | | | | | | | | | | | | | | | | | +| | 60 | | | | | | | | | | | | | | | | | +| n109 | 15 | 5 | 10 | 15 | 20 | 25 | 30 | | 40 7 | | 50 7 | | | | | | 5 | +| | 30 | | 10 | 15 | 20 | 25 | 30 | | 40 7 | | 50 7 | | | | | | | +| | 60 | | | | | | | | | | | | | | | | | + +NOTE 1: For this bandwidth, the minimum requirements are restricted to operation when carrier is configured as a downlink SCell part of CA configuration. + +NOTE 2: For this bandwidth, the minimum requirements are restricted to operation when carrier is configured as an SCell part of DC or CA configuration. + +NOTE 3: For this bandwidth, it only applies for UL transmission. + +NOTE 4: For this bandwidth, the minimum requirements are restricted to operation when carrier is configured as an SCell part of DC or CA configuration. + +NOTE 5: Void. + +NOTE 6: This bandwidth can only be applied in certain regions where the absence of non 3GPP technologies can be guaranteed on a long term basis in this version of specification. + +NOTE 7: For this bandwidth, it only applies for DL transmission. + +NOTE 8: 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. + +**Table 5.3.5-2: BS channel bandwidths and SCS per operating band in FR2-1** + +| NR Band | SCS (kHz) | BS channel bandwidth (MHz) | | | | +|---------|-----------|----------------------------|-----|-----|-----| +| | | 50 | 100 | 200 | 400 | +| n257 | 60 | 50 | 100 | 200 | | +| | 120 | 50 | 100 | 200 | 400 | +| n258 | 60 | 50 | 100 | 200 | | +| | 120 | 50 | 100 | 200 | 400 | +| n259 | 60 | 50 | 100 | 200 | | +| | 120 | 50 | 100 | 200 | 400 | +| n260 | 60 | 50 | 100 | 200 | | +| | 120 | 50 | 100 | 200 | 400 | +| n261 | 60 | 50 | 100 | 200 | | +| | 120 | 50 | 100 | 200 | 400 | +| n262 | 60 | 50 | 100 | 200 | | +| | 120 | 50 | 100 | 200 | 400 | + +**Table 5.3.5-3: BS channel bandwidths and SCS per operating band in FR2-2** + +| NR Band | SCS (kHz) | BS channel bandwidth (MHz) | | | | | +|---------|-----------|----------------------------|-----|-----|------|------| +| | | 100 | 400 | 800 | 1600 | 2000 | +| n263 | 120 | 100 | 400 | | | | +| | 480 | | 400 | 800 | 1600 | | +| | 960 | | 400 | 800 | 1600 | 2000 | + +## 5.3A BS channel bandwidth for CA + +### 5.3A.1 Transmission bandwidth configuration for CA + +For *carrier aggregation*, the *transmission bandwidth configuration* is defined per component carrier and the requirement is specified in clause 5.3.2. + +### 5.3A.2 Minimum guardband and transmission bandwidth configuration for CA + +For intra-band contiguous *carrier aggregation*, *Aggregated BS Channel Bandwidth* and *Guard Bands* are defined as follows, see Figure 5.3A.2-1. + +![Figure 5.3A.2-1: Definition of Aggregated BS Channel Bandwidth for intra-band carrier aggregation. The diagram shows a frequency axis with three carrier blocks. The leftmost block is labeled 'Lowest Carrier Transmission Bandwidth Configuration [RB]' and contains 'Resource block' units. Its center frequency is Fc_low and its lower edge is Fedge_low. The rightmost block is labeled 'Highest Carrier Transmission Bandwidth Configuration [RB]' and also contains 'Resource block' units. Its center frequency is Fc_high and its upper edge is Fedge_high. The total bandwidth between Fedge_low and Fedge_high is labeled 'Aggregated BS Channel Bandwidth, BW_channel_CA [MHz]'. Frequency offsets Foffset_low and Foffset_high are shown between the center frequencies and the edges. Vertical dotted lines mark the 'Lower Edge' and 'Upper Edge' of the aggregated bandwidth.](be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg) + +Figure 5.3A.2-1: Definition of Aggregated BS Channel Bandwidth for intra-band carrier aggregation. The diagram shows a frequency axis with three carrier blocks. The leftmost block is labeled 'Lowest Carrier Transmission Bandwidth Configuration [RB]' and contains 'Resource block' units. Its center frequency is Fc\_low and its lower edge is Fedge\_low. The rightmost block is labeled 'Highest Carrier Transmission Bandwidth Configuration [RB]' and also contains 'Resource block' units. Its center frequency is Fc\_high and its upper edge is Fedge\_high. The total bandwidth between Fedge\_low and Fedge\_high is labeled 'Aggregated BS Channel Bandwidth, BW\_channel\_CA [MHz]'. Frequency offsets Foffset\_low and Foffset\_high are shown between the center frequencies and the edges. Vertical dotted lines mark the 'Lower Edge' and 'Upper Edge' of the aggregated bandwidth. + +**Figure 5.3A.2-1: Definition of Aggregated BS Channel Bandwidth for intra-band carrier aggregation** + +The *aggregated BS Channel Bandwidth*, $BW_{\text{Channel\_CA}}$ , is defined as + +$$BW_{\text{Channel\_CA}} = F_{\text{edge,high}} - F_{\text{edge,low}} \text{ (MHz)}$$ + +The lower bandwidth edge $F_{\text{edge,low}}$ and the upper bandwidth edge $F_{\text{edge,high}}$ of the *aggregated BS channel bandwidth* are used as frequency reference points for transmitter and receiver requirements and are defined by + +$$F_{\text{edge,low}} = F_{\text{C,low}} - F_{\text{offset,low}}$$ + +$$F_{\text{edge,high}} = F_{\text{C,high}} + F_{\text{offset,high}}$$ + +The lower and upper frequency offsets depend on the *transmission bandwidth configurations* of the lowest and highest assigned edge component carrier and are defined as + +$$F_{\text{offset,low}} = (N_{\text{RB,low}} * 12 + 1) * SCS_{\text{low}}/2 + BW_{\text{GB,low}} \text{ (MHz)}$$ + +$$F_{\text{offset,high}} = (N_{\text{RB,high}} * 12 - 1) * SCS_{\text{high}}/2 + BW_{\text{GB,high}} \text{ (MHz)}$$ + +$N_{\text{RB,low}}$ and $N_{\text{RB,high}}$ are the *transmission bandwidth configurations* according to Table 5.3.2-1 or Table 5.3.2-2 or Table 5.3.2-3 for the lowest and highest assigned component carrier, $SCS_{\text{low}}$ and $SCS_{\text{high}}$ are the sub-carrier spacing for the lowest and highest assigned component carrier respectively. $SCS_{\text{low}}$ , $SCS_{\text{high}}$ , $N_{\text{RB,low}}$ , $N_{\text{RB,high}}$ , $BW_{\text{GB,low}}$ and $BW_{\text{GB,high}}$ use the largest $\mu$ value among the subcarrier spacing configurations supported in the operating band for both of the channel bandwidths according to Table 5.3.5-1 and $BW_{\text{GB,low}}$ and $BW_{\text{GB,high}}$ are the minimum guard band for lowest and highest assigned component carrier according to Table 5.3.3-1 for the said $\mu$ value. In case there is no common $\mu$ value for both of the channel bandwidths, $\mu=1$ is used for $SCS_{\text{low}}$ , $SCS_{\text{high}}$ , $N_{\text{RB,low}}$ , $N_{\text{RB,high}}$ , $BW_{\text{GB,low}}$ and $BW_{\text{GB,high}}$ . + +For *intra-band non-contiguous carrier aggregation* sub-block bandwidth and sub-block edges are defined as follows, see figure 5.3A.2-2. + +![Figure 5.3A.2-2: Definition of sub-block bandwidth for intra-band non-contiguous spectrum. The diagram shows two sub-blocks, Sub block 1 and Sub block n, within the Base Station RF Bandwidth. Each sub-block contains multiple Resource Blocks (RBs). The sub-block bandwidth (BW_Channel,block [MHz]) is defined by the Lower Sub-block Edge and the Upper Sub-block Edge. The Lower Sub-block Edge is defined by the transmission bandwidth configuration of the lowest carrier in a sub-block [RB] (F_C,block,low) minus the F_offset_low. The Upper Sub-block Edge is defined by the transmission bandwidth configuration of the highest carrier in a sub-block [RB] (F_C,block,high) plus the F_offset_high. The diagram also shows the F_offset_low and F_offset_high offsets for each sub-block.](a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg) + +Figure 5.3A.2-2: Definition of sub-block bandwidth for intra-band non-contiguous spectrum. The diagram shows two sub-blocks, Sub block 1 and Sub block n, within the Base Station RF Bandwidth. Each sub-block contains multiple Resource Blocks (RBs). The sub-block bandwidth (BW\_Channel,block [MHz]) is defined by the Lower Sub-block Edge and the Upper Sub-block Edge. The Lower Sub-block Edge is defined by the transmission bandwidth configuration of the lowest carrier in a sub-block [RB] (F\_C,block,low) minus the F\_offset\_low. The Upper Sub-block Edge is defined by the transmission bandwidth configuration of the highest carrier in a sub-block [RB] (F\_C,block,high) plus the F\_offset\_high. The diagram also shows the F\_offset\_low and F\_offset\_high offsets for each sub-block. + +**Figure 5.3A.2-2: Definition of sub-block bandwidth for intra-band non-contiguous spectrum** + +The *lower sub-block edge* of the *sub-block bandwidth* ( $BW_{\text{Channel,block}}$ ) is defined as follows: + +$$F_{\text{edge,block,low}} = F_{\text{C,block,low}} - F_{\text{offset,low}}$$ + +The *upper sub-block edge* of the *sub-block bandwidth* is defined as follows: + +$$F_{\text{edge,block,high}} = F_{\text{C,block,high}} + F_{\text{offset,high}}$$ + +The *sub-block bandwidth*, $BW_{\text{Channel,block}}$ , is defined as follows: + +$$BW_{\text{Channel,block}} = F_{\text{edge,block,high}} - F_{\text{edge,block,low}} \text{ (MHz)}$$ + +The lower and upper frequency offsets $F_{\text{offset,block,low}}$ and $F_{\text{offset,block,high}}$ depend on the *transmission bandwidth configurations* of the lowest and highest assigned edge component carriers within a *sub-block* and are defined as + +$$F_{\text{offset,block,low}} = (N_{\text{RB,low}} * 12 + 1) * SCS_{\text{low}} / 2 + BW_{\text{GB,low}} \text{ (MHz)}$$ + +$$F_{\text{offset,block,high}} = (N_{\text{RB,high}} * 12 - 1) * SCS_{\text{high}} / 2 + BW_{\text{GB,high}} \text{ (MHz)}$$ + +where $N_{\text{RB,low}}$ and $N_{\text{RB,high}}$ are the *transmission bandwidth configurations* according to Table 5.3.2-1 or Table 5.3.2-2 for the lowest and highest assigned component carrier within a *sub-block*, respectively. $SCS_{\text{low}}$ and $SCS_{\text{high}}$ are the sub-carrier spacing for the lowest and highest assigned component carrier within a *sub-block*, respectively. $SCS_{\text{low}}$ , $SCS_{\text{high}}$ , $N_{\text{RB,low}}$ , $N_{\text{RB,high}}$ , $BW_{\text{GB,low}}$ and $BW_{\text{GB,high}}$ use the largest $\mu$ value among the subcarrier spacing configurations supported in the operating band for both of the channel bandwidths according to Table 5.3.5-1 and $BW_{\text{GB,low}}$ and $BW_{\text{GB,high}}$ are the minimum guard band for lowest and highest assigned component carrier according to Table 5.3.3-1 for the said $\mu$ value. In case there is no common $\mu$ value for both of the channel bandwidths, $\mu=1$ is used for $SCS_{\text{low}}$ , $SCS_{\text{high}}$ , $N_{\text{RB,low}}$ , $N_{\text{RB,high}}$ , $BW_{\text{GB,low}}$ and $BW_{\text{GB,high}}$ . + +The *sub-block gap size* between two consecutive *sub-blocks* $W_{\text{gap}}$ is defined as follows: + +$$W_{\text{gap}} = F_{\text{edge,block,n+1,low}} - F_{\text{edge,block,n,high}} \text{ (MHz)}$$ + +## 5.4 Channel arrangement + +### 5.4.1 Channel spacing + +#### 5.4.1.1 Channel spacing for adjacent NR carriers + +The spacing between carriers will depend on the deployment scenario, the size of the frequency block available and the *BS channel bandwidths*. The nominal channel spacing between two adjacent NR carriers is defined as following: + +- For NR FR1 *operating bands* with 100 kHz channel raster, + - Nominal Channel spacing = $(BW_{\text{Channel}(1)} + BW_{\text{Channel}(2)})/2$ +- For NR FR1 *operating bands* with 15 kHz channel raster, + - Nominal Channel spacing = $(BW_{\text{Channel}(1)} + BW_{\text{Channel}(2)})/2 + \{-5 \text{ kHz}, 0 \text{ kHz}, 5 \text{ kHz}\}$ for $\Delta F_{\text{Raster}}$ equals to 15 kHz + - Nominal Channel spacing = $(BW_{\text{Channel}(1)} + BW_{\text{Channel}(2)})/2 + \{-10 \text{ kHz}, 0 \text{ kHz}, 10 \text{ kHz}\}$ for $\Delta F_{\text{Raster}}$ equals to 30 kHz +- For NR FR2 *operating bands* with 60 kHz channel raster, + - Nominal Channel spacing = $(BW_{\text{Channel}(1)} + BW_{\text{Channel}(2)})/2 + \{-20 \text{ kHz}, 0 \text{ kHz}, 20 \text{ kHz}\}$ for $\Delta F_{\text{Raster}}$ equals to 60 kHz + - Nominal Channel spacing = $(BW_{\text{Channel}(1)} + BW_{\text{Channel}(2)})/2 + \{-40 \text{ kHz}, 0 \text{ kHz}, 40 \text{ kHz}\}$ for $\Delta F_{\text{Raster}}$ equals to 120 kHz +- For operating band n263 + - Nominal Channel spacing = $\text{ceil}((BW_{\text{Channel}(1)} + BW_{\text{Channel}(2)})/100.8) * 50.4 \text{ MHz}$ , + +where $BW_{\text{Channel}(1)}$ and $BW_{\text{Channel}(2)}$ are the *BS channel bandwidths* of the two respective NR carriers. The channel spacing can be adjusted depending on the channel raster to optimize performance in a particular deployment scenario. + +#### 5.4.1.2 Channel spacing for CA + +For intra-band contiguously aggregated carriers, the channel spacing between adjacent component carriers shall be multiple of least common multiple of channel raster and sub-carrier spacing. + +The nominal channel spacing between two adjacent aggregated NR carriers is defined as follows: + +For NR *operating bands* with 100 kHz channel raster: + +For NR *operating bands* with 15 kHz channel raster: + +with + +For NR *operating bands* with 60kHz channel raster: + +with + +For operating band n263 + +$$\text{Nominal Channel spacing} = \text{ceil}((\text{BW}_{\text{Channel}(1)} + \text{BW}_{\text{Channel}(2)})/100.8) * 50.4 \text{ MHz},$$ + +where $\text{BW}_{\text{Channel}(1)}$ and $\text{BW}_{\text{Channel}(2)}$ are the *BS channel bandwidths* of the two respective NR component carriers according to Table 5.3.2-1, 5.3.2-2 and 5.3.2-3 with values in MHz, the largest value among the subcarrier spacing configurations supported in the operating band for both of the channel bandwidths according to Table 5.3.5-1 and Table 5.3.5-2 and $\text{GB}_{\text{Channel}(i)}$ the minimum guard band for channel bandwidth $i$ according to Table 5.3.3-1, Table 5.3.3-2 and Table 5.3.3-2a for the said value, with as defined in TS 38.211 [9]. In case there is no common $\mu$ value for both of the channel bandwidths, $\mu_0=1$ is selected for NR *operating bands* with 15 kHz channel raster and $\text{GB}_{\text{Channel}(i)}$ is the minimum guard band for channel bandwidth $i$ according to Table 5.3.3-1 for $\mu=1$ with $\mu$ as defined in TS 38.211[9]. + +The channel spacing for *intra-band contiguous carrier aggregation* can be adjusted to any multiple of least common multiple of channel raster and sub-carrier spacing less than the nominal channel spacing to optimize performance in a particular deployment scenario. + +For *intra-band non-contiguous carrier aggregation*, the channel spacing between two NR component carriers in different *sub-blocks* shall be larger than the nominal channel spacing defined in this clause. + +## 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 | +| 3000 – 24250 | 15 | 3000 | 600000 | 600000 – 2016666 | +| 24250 – 100000 | 60 | 24250.08 | 2016667 | 2016667 – 3279165 | + +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}}$ . + +For SUL bands except n95, n97, n98 and for the uplink of all FDD bands defined in table 5.2-1, for TDD bands n34, n38, n39, n48, n90, and n40, + +$$F_{\text{REF,shift}} = F_{\text{REF}} + \Delta_{\text{shift}}, \text{ where } \Delta_{\text{shift}} = 0 \text{ kHz or } 7.5 \text{ kHz}$$ + +where $\Delta_{\text{shift}}$ is signalled by the network in higher layer parameter *frequencyShift7p5khz* as defined in TS 38.331 [11]. + +For bands n34, n38, n39, n48 and n40, $F_{\text{REF,shift}}$ is only applicable to uplink transmissions using a 15 kHz SCS. + +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.1A NB-IoT carrier frequency numbering + +The NB-IoT carrier frequency numbering (EARFCN) is defined in clause 5.7 of TS 36.104 [4]. + +### 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 BS. + +**Table 5.4.2.2-1: Channel Raster to Resource Element Mapping** + +| | | | +|--------------------------------|---|---| +| Resource element index | 0 | 6 | +| Physical resource block number | | | + +$k$ , and $N_{RB}$ are as defined in TS 38.211 [9]. + +### 5.4.2.3 Channel raster entries for each *operating band* + +The RF channel positions on the channel raster in each NR *operating band* are given through the applicable NR-ARFCN in table 5.4.2.3-1 for FR1 and table 5.4.2.3-2 for FR2, using the channel raster to resource element mapping in clause 5.4.2.2. + +- For NR *operating bands* with 100 kHz channel raster, $\Delta F_{\text{Raster}} = 20 \times \Delta F_{\text{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>. +- For NR *operating bands* with 15 kHz channel raster below 3 GHz, $\Delta F_{\text{Raster}} = I \times \Delta F_{\text{Global}}$ , where $I \in \{3,6\}$ . In this case, every $I^{\text{th}}$ 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 < $I$ >. +- For NR *operating bands* with 15 kHz and 60 kHz channel raster above 3 GHz, $\Delta F_{\text{Raster}} = I \times \Delta F_{\text{Global}}$ , where $I \in \{1, 2\}$ . In this case, every $I^{\text{th}}$ 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 and table 5.4.2.3-2 is given as < $I$ >. +- For frequency bands with two $\Delta F_{\text{Raster}}$ in FR1, the higher $\Delta F_{\text{Raster}}$ applies to channels using only the SCS that is equal to or larger than the higher $\Delta F_{\text{Raster}}$ and SSB SCS is equal to the higher $\Delta F_{\text{Raster}}$ . +- For frequency bands with two $\Delta F_{\text{Raster}}$ in FR2, the higher $\Delta F_{\text{Raster}}$ applies to channels using only the SCS that is equal to the higher $\Delta F_{\text{Raster}}$ and the SSB SCS that is equal to or larger than the higher $\Delta F_{\text{Raster}}$ . + +**Table 5.4.2.3-1: Applicable NR-ARFCN per *operating band* in FR1** + +| NR operating band | $\Delta F_{\text{Raster}}$ (kHz) | Uplink range of $N_{\text{REF}}$
(First – – Last) | Downlink range of $N_{\text{REF}}$
(First – – Last) | +|-------------------|----------------------------------|------------------------------------------------------------------|--------------------------------------------------------------------| +| n1 | 100 | 384000 – <20> – 396000 | 422000 – <20> – 434000 | +| n2 | 100 | 370000 – <20> – 382000 | 386000 – <20> – 398000 | +| n3 | 100 | 342000 – <20> – 357000 | 361000 – <20> – 376000 | +| n5 | 100 | 164800 – <20> – 169800 | 173800 – <20> – 178800 | +| n7 | 100 | 500000 – <20> – 514000 | 524000 – <20> – 538000 | +| n8 | 100 | 176000 – <20> – 183000 | 185000 – <20> – 192000 | +| n12 | 100 | 139800 – <20> – 143200 | 145800 – <20> – 149200 | +| n13 | 100 | 155400 – <20> – 157400 | 149200 – <20> – 151200 | +| n14 | 100 | 157600 – <20> – 159600 | 151600 – <20> – 153600 | +| n18 | 100 | 163000 – <20> – 166000 | 172000 – <20> – 175000 | +| n20 | 100 | 166400 – <20> – 172400 | 158200 – <20> – 164200 | +| n25 | 100 | 370000 – <20> – 383000 | 386000 – <20> – 399000 | +| n24 | 100 | 325300 – <20> – 332100 | 305000 – <20> – 311800 | +| n26 | 100 | 162800 – <20> – 169800 | 171800 – <20> – 178800 | +| n28 | 100 | 140600 – <20> – 149600 | 151600 – <20> – 160600 | +| | | 144608 4 | 155608 4 | +| n29 | 100 | N/A | 143400 – <20> – 145600 | +| n30 | 100 | 461000 – <20> – 463000 | 470000 – <20> – 472000 | +| n31 | 100 | 90500 – <20> – 91500 | 92500 – <20> – 93500 | +| n34 | 100 | 402000 – <20> – 405000 | 402000 – <20> – 405000 | +| n38 | 100 | 514000 – <20> – 524000 | 514000 – <20> – 524000 | +| n39 | 100 | 376000 – <20> – 384000 | 376000 – <20> – 384000 | +| n40 | 100 | 460000 – <20> – 480000 | 460000 – <20> – 480000 | +| n41 | 15 | 499200 – <3> – 537999 | 499200 – <3> – 537999 | +| | 30 | 499200 – <6> – 537996 | 499200 – <6> – 537996 | +| n46 1 | 15 | 743334 – <1> – 795000 | 743334 – <1> – 795000 | +| n48 | 15 | 636667 – <1> – 646666 | 636667 – <1> – 646666 | +| | 30 | 636668 – <2> – 646666 | 636668 – <2> – 646666 | +| n50 | 100 | 286400 – <20> – 303400 | 286400 – <20> – 303400 | +| n51 | 100 | 285400 – <20> – 286400 | 285400 – <20> – 286400 | +| n53 | 100 | 496700 – <20> – 499000 | 496700 – <20> – 499000 | +| n54 | 100 | 334000 – <20> – 335000 | 334000 – <20> – 335000 | +| n65 | 100 | 384000 – <20> – 402000 | 422000 – <20> – 440000 | +| n66 | 100 | 342000 – <20> – 356000 | 422000 – <20> – 440000 | +| n67 | 100 | N/A | 147600 – <20> – 151600 | +| n70 | 100 | 339000 – <20> – 342000 | 399000 – <20> – 404000 | +| n71 | 100 | 132600 – <20> – 139600 | 123400 – <20> – 130400 | +| n72 | 100 | 90200 – <20> – 91200 | 92200 – <20> – 93200 | +| n74 | 100 | 285400 – <20> – 294000 | 295000 – <20> – 303600 | +| n75 | 100 | N/A | 286400 – <20> – 303400 | +| n76 | 100 | N/A | 285400 – <20> – 286400 | +| n77 | 15 | 620000 – <1> – 680000 | 620000 – <1> – 680000 | +| | 30 | 620000 – <2> – 680000 | 620000 – <2> – 680000 | +| n78 | 15 | 620000 – <1> – 653333 | 620000 – <1> – 653333 | +| | 30 | 620000 – <2> – 653332 | 620000 – <2> – 653332 | +| n79 | 15 | 693334 – <1> – 733333 | 693334 – <1> – 733333 | +| | 30 | 693334 – <2> – 733332 | 693334 – <2> – 733332 | +| n80 | 100 | 342000 – <20> – 357000 | N/A | +| n81 | 100 | 176000 – <20> – 183000 | N/A | +| n82 | 100 | 166400 – <20> – 172400 | N/A | +| n83 | 100 | 140600 – <20> – 149600 | N/A | +| n84 | 100 | 384000 – <20> – 396000 | N/A | +| n85 | 100 | 139600 – <20> – 143200 | 145600 – <20> – 149200 | +| n86 | 100 | 342000 – <20> – 356000 | N/A | +| n89 | 100 | 164800 – <20> – 169800 | N/A | +| n90 | 15 | 499200 – <3> – 537999 | 499200 – <3> – 537999 | +| | 30 | 499200 – <6> – 537996 | 499200 – <6> – 537996 | +| | 100 | 499200 – <20> – 538000 | 499200 – <20> – 538000 | +| n91 | 100 | 166400 – <20> – 172400 | 285400 – <20> – 286400 | +| n92 | 100 | 166400 – <20> – 172400 | 286400 – <20> – 303400 | +| n93 | 100 | 176000 – <20> – 183000 | 285400 – <20> – 286400 | +| n94 | 100 | 176000 – <20> – 183000 | 286400 – <20> – 303400 | + +| | | | | +|-------------------|-----|------------------------|------------------------| +| n95 | 100 | 402000 – <20> – 405000 | N/A | +| n96 2 | 15 | 795000 – <1> – 875000 | 795000 – <1> – 875000 | +| n97 | 100 | 460000 – <20> – 480000 | N/A | +| n98 | 100 | 376000 – <20> – 384000 | N/A | +| n99 | 100 | 325300 – <20> – 332100 | N/A | +| n100 | 100 | 174880 – <20> – 176000 | 183880 – <20> – 185000 | +| n101 | 100 | 380000 – <20> – 382000 | 380000 – <20> – 382000 | +| n102 3 | 15 | 796334 – <1> – 828333 | 796334 – <1> – 828333 | +| n104 | 15 | 828334 – <1> – 875000 | 828334 – <1> – 875000 | +| | 30 | 828334 – <2> – 875000 | 828334 – <2> – 875000 | +| n105 | 100 | 132600 – <20> – 140600 | 122400 – <20> – 130400 | +| n106 5 | 100 | 179200 – <20> – 180200 | 187000 – <20> – 188000 | +| n109 | 100 | 140600 – <20> – 149600 | 286400 – <20> – 303400 | + +NOTE 1: Applicable NR-ARFCN for band n46 + +for 10 MHz channel bandwidth, $N_{REF} = \{782000, 788668\}$ + +for 20 MHz channel bandwidth, $N_{REF} = \{744000, 745332, 746668, 748000, 749332, 750668, 752000, 753332, 754668, 756000, 765332, 766668, 768000, 769332, 770668, 772000, 773332, 774668, 776000, 777332, 778668, 780000, 781332, 783000, 784332, 785668, 787000, 788332, 789668, 791000, 792332, 793668\}$ ; + +for 40 MHz channel bandwidth, $N_{REF} = \{744668, 746000, 748668, 751332, 754000, 755332, 766000, 767332, 770000, 772668, 775332, 778000, 780668, 783668, 786332, 787668, 790332, 793000\}$ ; + +for 60 MHz channel bandwidth, $N_{REF} = \{745332, 746668, 748000, 752000, 753332, 754668, 766668, 768000, 769332, 773332, 774668, 778668, 780000, 784332, 785668, 791000, 792332\}$ ; + +for 80 MHz channel bandwidth, $N_{REF} = \{746000, 747332, 752668, 754000, 767332, 768668, 774000, 779332, 785000, 791668\}$ + +for 100 MHz channel bandwidth, $N_{REF} = \{746668, 753332, 768000, 791000\}$ + +NOTE 2: Applicable NR-ARFCN for band n96 + +for 20 MHz channel bandwidth, $N_{REF} = \{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, $N_{REF} = \{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, $N_{REF} = \{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, $N_{REF} = \{799000, 804332, 809668, 815000, 820332, 825668, 831000, 836332, 841668, 847000, 852332, 857668, 863000, 868332\}$ + +for 100 MHz channel bandwidth, $N_{REF} = \{799668, 803668, 810332, 814332, 821000, 825000, 831668, 835668, 842332, 846332, 853000, 857000, 863668, 867668, 869000, 870332, 871668\}$ + +NOTE 3: Applicable NR-ARFCN for band n102 + +for 20 MHz channel bandwidth, $N_{REF} = \{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, $N_{REF} = \{797668, 800332, 803000, 805668, 808332, 811000, 813668, 816332, 819000, 821668, 824332, 827000\}$ + +for 60 MHz channel bandwidth, $N_{REF} = \{798332, 799668, 803668, 805000, 809000, 810332, 814332, 815668, 819668, 821000, 825000, 826332\}$ + +for 80 MHz channel bandwidth, $N_{REF} = \{799000, 804332, 809668, 815000, 820332, 825668\}$ + +for 100 MHz channel bandwidth, $N_{REF} = \{799668, 803668, 810332, 814332, 821000, 825000\}$ + +NOTE 4: This exceptional raster point is applicable only to n28 and is only applicable for 40MHz BS channel bandwidth to ensure the guardband with 30MHz UE channel bandwidth. + +NOTE 5: In the present version of the specification, only $N_{REF}$ 179800 and 187600 is applicable for 3 MHz channel bandwidth. + +**Table 5.4.2.3-2: Applicable NR-ARFCN per operating band in FR2** + +| NR operating band | $\Delta F_{\text{Raster}}$
(kHz) | Uplink and Downlink range of $N_{\text{REF}}$ | +|-------------------|-------------------------------------|-----------------------------------------------| +| | | (First – – Last) | +| n257 | 60 | 2054166 – <1> – 2104165 | +| | 120 | 2054167 – <2> – 2104165 | +| n258 | 60 | 2016667 – <1> – 2070832 | +| | 120 | 2016667 – <2> – 2070831 | +| n259 | 60 | 2270833 – <1> – 2337499 | +| | 120 | 2270833 – <2> – 2337499 | +| n260 | 60 | 2229166 – <1> – 2279165 | +| | 120 | 2229167 – <2> – 2279165 | +| n261 | 60 | 2070833 – <1> – 2084999 | +| | 120 | 2070833 – <2> – 2084999 | +| n262 | 60 | 2399166 – <1> – 2415832 | +| | 120 | 2399167 – <2> – 2415831 | +| n263 | 120 | See Table 5.4.2.3-3 | +| | 480 | | +| | 960 | | + +**Table 5.4.2.3-3: Applicable NR-ARFCN for operation in band n263** + +| Channel Bandwidth | Applicable NR-ARFCN | +|-------------------|---------------------------------------------------------------------------| +| 100 MHz | $2564083 + 1680 * N$ , $N = 0:137$ | +| 400 MHz | $2566603 + 6720 * N$ , $N = 0:33$ | +| 800 MHz | $2569963 + 6720 * N$ , $N = 0:32$ | +| 1600 MHz | $2576683 + 6720 * N$ , $N = 0:30$ | +| 2000 MHz | $2580043 + 6720 * N$ , $N = 0:29$ ,
2585083, 2655643, 2692603, 2764843 | + +For NR operating bands with 100 kHz channel raster, Enhanced channel raster is defined with $\Delta F_{\text{Raster}} = 2 \times \Delta F_{\text{Global}}$ . In this case every 2th 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-4 is given as <2>. + +**Table 5.4.2.3-4: Applicable NR-ARFCN per operating band for enhanced channel raster** + +| NR operating band | $\Delta F_{\text{Raster}}$ (kHz) | Uplink | Downlink | +|-------------------|----------------------------------|-----------------------------------------------------------|-----------------------------------------------------------| +| | | Range of $N_{\text{REF}}$
(First – – Last) | Range of $N_{\text{REF}}$
(First – – Last) | +| n1 | 10 | 384000 – <2> – 396000 | 422000 – <2> – 434000 | +| n2 | 10 | 370000 – <2> – 382000 | 386000 – <2> – 398000 | +| n3 | 10 | 342000 – <2> – 357000 | 361000 – <2> – 376000 | +| n5 | 10 | 164800 – <2> – 169800 | 173800 – <2> – 178800 | +| n7 | 10 | 500000 – <2> – 514000 | 524000 – <2> – 538000 | +| n8 | 10 | 176000 – <2> – 183000 | 185000 – <2> – 192000 | +| n12 | 10 | 139800 – <2> – 143200 | 145800 – <2> – 149200 | +| n13 | 10 | 155400 – <2> – 157400 | 149200 – <2> – 151200 | +| n14 | 10 | 157600 – <2> – 159600 | 151600 – <2> – 153600 | +| n18 | 10 | 163000 – <2> – 166000 | 172000 – <2> – 175000 | +| n20 | 10 | 166400 – <2> – 172400 | 158200 – <2> – 164200 | +| n24 | 10 | 325300 – <2> – 332100 | 305000 – <2> – 311800 | +| n25 | 10 | 370000 – <2> – 383000 | 386000 – <2> – 399000 | +| n26 | 10 | 162800 – <2> – 169800 | 171800 – <2> – 178800 | +| n28 | 10 | 140600 – <2> – 149600 | 151600 – <2> – 160600 | +| n29 | 10 | N/A | 143400 – <2> – 145600 | +| n30 | 10 | 461000 – <2> – 463000 | 470000 – <2> – 472000 | +| n34 | 10 | 402000 – <2> – 405000 | 402000 – <2> – 405000 | +| n38 | 10 | 514000 – <2> – 524000 | 514000 – <2> – 524000 | +| n39 | 10 | 376000 – <2> – 384000 | 376000 – <2> – 384000 | +| n40 | 10 | 460000 – <2> – 480000 | 460000 – <2> – 480000 | +| n50 | 10 | 286400 – <2> – 303400 | 286400 – <2> – 303400 | +| n53 | 10 | 496700 – <2> – 499000 | 496700 – <2> – 499000 | +| n54 | 10 | 334000 – <2> – 335000 | 334000 – <2> – 335000 | +| n65 | 10 | 384000 – <2> – 402000 | 422000 – <2> – 440000 | +| n66 | 10 | 342000 – <2> – 356000 | 422000 – <2> – 440000 | +| n67 | 10 | N/A | 147600 – <2> – 151600 | +| n70 | 10 | 339000 – <2> – 342000 | 399000 – <2> – 404000 | +| n71 | 10 | 132600 – <2> – 139600 | 123400 – <2> – 130400 | +| n74 | 10 | 285400 – <2> – 294000 | 295000 – <2> – 303600 | +| n75 | 10 | N/A | 286400 – <2> – 303400 | +| n76 | 10 | N/A | 285400 – <2> – 286400 | +| n80 | 10 | 342000 – <2> – 357000 | N/A | +| n81 | 10 | 176000 – <2> – 183000 | N/A | +| n82 | 10 | 166400 – <2> – 172400 | N/A | +| n83 | 10 | 140600 – <2> – 149600 | N/A | +| n84 | 10 | 384000 – <2> – 396000 | N/A | +| n85 | 10 | 139600 – <2> – 143200 | 145600 – <2> – 149200 | +| n86 | 10 | 342000 – <2> – 356000 | N/A | +| n89 | 10 | 164800 – <2> – 169800 | N/A | +| n90 | 10 | 499200 – <2> – 538000 | 499200 – <2> – 538000 | +| n91 | 10 | 166400 – <2> – 172400 | 285400 – <2> – 286400 | +| n92 | 10 | 166400 – <2> – 172400 | 286400 – <2> – 303400 | +| n93 | 10 | 176000 – <2> – 183000 | 285400 – <2> – 286400 | +| n94 | 10 | 176000 – <2> – 183000 | 286400 – <2> – 303400 | +| n95 | 10 | 402000 – <2> – 405000 | N/A | +| n97 | 10 | 460000 – <2> – 480000 | N/A | +| n98 | 10 | 376000 – <2> – 384000 | N/A | +| n99 | 10 | 325300 – <2> – 332100 | N/A | +| n100 | 10 | 174880 – <2> – 176000 | 183880 – <2> – 185000 | +| n101 | 10 | 380000 – <2> – 382000 | 380000 – <2> – 382000 | +| n105 | 10 | 132600 – <2> – 140600 | 122400 – <2> – 130400 | + +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 for above 3 MHz channel bandwidth and in table 5.4.3.1-2 for 3 MHz channel bandwidth. + +For band n100, additional parameters defining the $SS_{REF}$ and GSCN are specified in table 5.4.3.1-3. + +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 is defined separately for each band. + +The synchronization raster and the corresponding SS block do not cover all possible RF channel bandwidths and locations on Enhanced channel raster. + +**Table 5.4.3.1-1: GSCN parameters for the global frequency raster for above 3 MHz channel bandwidth** + +| Range of frequencies (MHz) | SS block frequency position $SS_{REF}$ | GSCN | Range of GSCN | +|---------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------|----------------|---------------| +| 0 – 3000 | $N * 1200 \text{ kHz} + M * 50 \text{ kHz}$ ,
$N = 1:2499$ , $M \in \{1,3,5\}$ (Note) | $3N + (M-3)/2$ | 2 – 7498 | +| 3000 – 24250 | $3000 \text{ MHz} + N * 1.44 \text{ MHz}$ ,
$N = 0:14756$ | $7499 + N$ | 7499 – 22255 | +| 24250 – 100000 | $24250.08 \text{ MHz} + N * 17.28 \text{ MHz}$ ,
$N = 0:4383$ | $22256 + N$ | 22256 – 26639 | +| NOTE: The default value for operating bands which only support SCS spaced channel raster(s) is $M=3$ . | | | | + +**Table 5.4.3.1-2: GSCN parameters for the global frequency raster for 3 MHz channel bandwidth** + +| Range of frequencies (MHz) | SS block frequency position $SS_{REF}$ | GSCN | Range of GSCN | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|------------------------|---------------| +| 0 – 1000 | $N * 600 \text{ kHz} + M * 50 \text{ kHz} + 300 \text{ kHz}$ ,
$N = 1:1665$ , $M \in \{1,3,5\}$ (Note 1) | $26638 + 3N + (M-3)/2$ | 26640 – 31634 | +| NOTE 1: Only applicable for 15 PRB transmission bandwidth configuration within 3 MHz channel bandwidth with punctured PBCH defined in TS 38.211 [9] clause 7.4.3.1. | | | | + +**Table 5.4.3.1-3: Additional GSCN parameters for the global frequency raster and for band n100** + +| SS block frequency position $SS_{REF}$ (MHz) | GSCN | Note | +|----------------------------------------------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| 920.73 | 41637 | Only applicable for 12 PRB transmission bandwidth configuration within 3 MHz channel with punctured PBCH defined in TS 38.211 [9] clause 7.4.3.1. | +| 921.45 | 41638 | Only applicable for 20 PRB DCH transmission bandwidth configuration within 5 MHz channel with unpunctured PBCH defined in TS 38.211 [9] clause 7.4.3.1. | + +### 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 [9]. + +### 5.4.3.3 Synchronization raster entries for each operating band + +For FR1 and for above 3 MHz channel bandwidth, 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 and for 3 MHz channel bandwidth, the synchronization raster for each band is given in table 5.4.3.3-4. The distance between applicable GSCN entries is given by the indicated in table 5.4.3.3-4. + +For FR2, the synchronization raster for each band is given in table 5.4.3.3-2. The distance between applicable GSCN entries is given by the indicated in table 5.4.3.3-2. + +**Table 5.4.3.3-1: Applicable SS raster entries per *operating band* (FR1) for above 3 MHz channel bandwidth** + +| NR operating band | SS Block SCS | SS Block pattern
(NOTE 1) | Range of GSCN
(First – – Last) | +|-------------------|--------------|------------------------------|-----------------------------------------------| +| n1 | 15 kHz | Case A | 5279 – <1> – 5419 | +| n2 | 15 kHz | Case A | 4829 – <1> – 4969 | +| n3 | 15 kHz | Case A | 4517 – <1> – 4693 | +| n5 | 15 kHz | Case A | 2177 – <1> – 2230 | +| | 30 kHz | Case B | 2183 – <1> – 2224 | +| n7 | 15 kHz | Case A | 6554 – <1> – 6718 | +| n8 | 15 kHz | Case A | 2318 – <1> – 2395 | +| n12 | 15 kHz | Case A | 1828 – <1> – 1858 | +| n13 | 15 kHz | Case A | 1871 – <1> – 1885 | +| n14 | 15 kHz | Case A | 1901 – <1> – 1915 | +| n18 | 15 kHz | Case A | 2156 – <1> – 2182 | +| n20 | 15 kHz | Case A | 1982 – <1> – 2047 | +| n24 | 15 kHz | Case A | 3818 – <1> – 3892 | +| | 30 kHz | Case B | 3824 – <1> – 3886 | +| n25 | 15 kHz | Case A | 4829 – <1> – 4981 | +| n26 | 15 kHz | Case A | 2153 – <1> – 2230 | +| n28 | 15 kHz | Case A | 1901 – <1> – 2002 | +| n29 | 15 kHz | Case A | 1798 – <1> – 1813 | +| n30 | 15 kHz | Case A | 5879 – <1> – 5893 | +| n31 | 15 kHz | Case A | 1161 – <1> – 1162 | +| n34 | 15 kHz | Case A | NOTE 3 | +| | 30 kHz | Case C | 5036 – <1> – 5050 | +| n38 | 15 kHz | Case A | NOTE 2 | +| | 30 kHz | Case C | 6437 – <1> – 6538 | +| n39 | 15 kHz | Case A | NOTE 4 | +| | 30 kHz | Case C | 4712 – <1> – 4789 | +| n40 | 30 kHz | Case C | 5762 – <1> – 5989 | +| n41 | 15 kHz | Case A | 6246 – <3> – 6717 | +| | 30 kHz | Case C | 6252 – <3> – 6714 | +| n46 5 | 30 kHz | Case C | 8993 – <1> – 9530 | +| n48 | 30 kHz | Case C | 7884 – <1> – 7982 | +| n50 | 30 kHz | Case C | 3590 – <1> – 3781 | +| n51 | 15 kHz | Case A | 3572 – <1> – 3574 | +| n53 | 15 kHz | Case A | 6215 – <1> – 6232 | +| | 30 kHz | Case C | 6221 – <1> – 6226 | +| n54 | 15 kHz | Case A | 4181 – <1> – 4182 | +| n65 | 15 kHz | Case A | 5279 – <1> – 5494 | +| n66 | 15 kHz | Case A | 5279 – <1> – 5494 | +| | 30 kHz | Case B | 5285 – <1> – 5488 | +| n67 | 15 kHz | Case A | 1850 – <1> – 1888 | +| n70 | 15 kHz | Case A | 4993 – <1> – 5044 | +| n71 | 15 kHz | Case A | 1547 – <1> – 1624 | +| n72 | 15 kHz | Case A | 1157 – <1> – 1159 | +| n74 | 15 kHz | Case A | 3692 – <1> – 3790 | +| n75 | 15 kHz | Case A | 3584 – <1> – 3787 | +| n76 | 15 kHz | Case A | 3572 – <1> – 3574 | +| n77 | 30 kHz | Case C | 7711 – <1> – 8329 | +| n78 | 30 kHz | Case C | 7711 – <1> – 8051 | +| n79 | 30 kHz | Case C | 8480 – <16> – 8880 7 | +| | | | 8475 – <1> – 8884 8 | +| n85 | 15 kHz | Case A | 1826 – <1> – 1858 | +| n90 | 15 kHz | Case A | 6246 – <1> – 6717 10 | +| | 15 kHz | Case A | 6245 – <1> – 6718 11 | +| | 30 kHz | Case C | 6252 – <1> – 6714 | +| n91 | 15 kHz | Case A | 3572 – <1> – 3574 | +| n92 | 15 kHz | Case A | 3584 – <1> – 3787 | +| n93 | 15 kHz | Case A | 3572 – <1> – 3574 | +| n94 | 15 kHz | Case A | 3584 – <1> – 3787 | +| n96 6 | 30 kHz | Case C | 9531 – <1> – 10363 | +| n100 | 15 kHz | Case A | 2303 – <1> – 2307, 41638 12 | +| n101 | 15 kHz | Case A | 4754 – <1> – 4768 | +| | 30 kHz | Case C | 4760 – <1> – 4764 | +| n102 9 | 30 kHz | Case C | 9531 – <1> – 9877 | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------|--------------------| +| n104 | 30 kHz | Case C | 9882 – <7> – 10358 | +| n105 | 15 kHz | Case A | 1535 – <1> – 1624 | +| n109 | 15 kHz | Case A | 3584 – <1> – 3787 | +| NOTE 1: SS Block pattern is defined in clause 4.1 in TS 38.213 [10]. | | | | +| NOTE 2: The applicable SS raster entries are GSCN = {6432, 6443, 6457, 6468, 6479, 6493, 6507, 6518, 6532, 6543} | | | | +| NOTE 3: The applicable SS raster entries are GSCN = {5032, 5043, 5054} | | | | +| NOTE 4: The applicable SS raster entries are GSCN = {4707, 4715, 4718, 4729, 4732, 4743, 4747, 4754, 4761, 4768, 4772, 4782, 4786, 4793} | | | | +| NOTE 5: The following GSCN are allowed for operation in band n46:
GSCN = {8996, 9010, 9024, 9038, 9051, 9065, 9079, 9093, 9107, 9121, 9218, 9232, 9246, 9260, 9274, 9288, 9301, 9315, 9329, 9343, 9357, 9371, 9385, 9402, 9416, 9430, 9444, 9458, 9472, 9485, 9499, 9513}. | | | | +| NOTE 6: The following GSCN are allowed for operation in band n96:
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}. | | | | +| NOTE 7: The SS raster entries apply for channel bandwidths larger than or equal to 40 MHz. | | | | +| NOTE 8: The SS raster entries apply for channel bandwidths smaller than 40 MHz. | | | | +| NOTE 9: The following GSCN are allowed for operation in band n102:
GSCN = {9535, 9548, 9562, 9576, 9590, 9603, 9617, 9631, 9645, 9659, 9673, 9687, 9701, 9714, 9728, 9742, 9756, 9770, 9784, 9798, 9812, 9826, 9840, 9853, 9867} | | | | +| NOTE 10: The SS raster entries apply for channel bandwidths larger than or equal to 10 MHz. | | | | +| NOTE 11: The SS raster entries apply for channel bandwidth equal to 5 MHz. | | | | +| NOTE 12: Only applicable for 20 PRB transmission bandwidth configuration within 5 MHz channel with unpunctured PBCH defined in TS 38.211 [9] clause 7.4.3.1. | | | | + +**Table 5.4.3.3-2: Applicable SS raster entries per operating band (FR2)** + +| NR operating band | SS Block SCS | SS Block pattern (note 1) | Range of GSCN (First – – Last) | +|-------------------|----------------------|---------------------------|--------------------------------------------| +| n257 | 120 kHz | Case D | 22388 – <1> – 22558 | +| | 240 kHz | Case E | 22390 – <2> – 22556 | +| n258 | 120 kHz | Case D | 22257 – <1> – 22443 | +| | 240 kHz | Case E | 22258 – <2> – 22442 | +| n259 | 120 kHz | Case D | 23140 – <1> – 23369 | +| | 240 kHz | Case E | 23142 – <2> – 23368 | +| n260 | 120 kHz | Case D | 22995 – <1> – 23166 | +| | 240 kHz | Case E | 22996 – <2> – 23164 | +| n261 | 120 kHz | Case D | 22446 – <1> – 22492 | +| | 240 kHz | Case E | 22446 – <2> – 22490 | +| n262 | 120 kHz | Case D | 23586 – <1> – 23641 | +| | 240 kHz | Case E | 23588 – <2> – 23640 | +| n263 | 120 kHz | Case D | Table 5.4.3.3-3 | +| | 480 kHz | Case F | | +| | 960 kHz 2 | Case G | 24162 – <6> – 24954 | + +NOTE 1: SS Block pattern is defined in section 4.1 in TS 38.213 [10]. +NOTE 2: SS Block SCS of 960 kHz is not used for initial access. + +**Table 5.4.3.3-3: Allowed GSCN for operation in band n263 for 120 kHz and 480 kHz** + +| SS Block SCS | Range of GSCN | +|--------------|---------------------------------------------------------| +| 120 kHz | $24156 + 6 * N - 3 * \text{floor}((N+5)/18)$ , N=0:137 | +| 480 kHz | $24162 + 24 * N - 12 * \text{floor}((N+4)/18)$ , N=0:33 | + +**Table 5.4.3.3-4: Applicable SS raster entries per operating band (FR1) for 3 MHz channel bandwidth** + +| NR operating band | SS Block SCS | SS Block pattern
(NOTE 1) | Range of GSCN
(First – – Last) | +|-------------------|--------------|------------------------------|--------------------------------------------------------------------| +| n26 | 15 kHz | Case A | 30937 – <1> – 31100 | +| n28 | 15 kHz | Case A | 30432 – <1> – 30644 | +| n31 | 15 kHz | Case A | 28955 – <1> – 28967 | +| n72 | 15 kHz | Case A | 28947 – <1> – 28959 | +| n85 | 15 kHz | Case A | 30282 – <1> – 30359 | +| n100 | 15 kHz | Case A | 31240 – <1> – 31242,
31244 – <1> – 31253,
41637 2 | +| n106 | 15 kHz | Case A | 31317 – <1> – 31329 | + +NOTE 1: SS Block pattern is defined in clause 4.1 in TS 38.213 [10]. + +NOTE 2: Only applicable for 12 PRB transmission bandwidth configuration within 3 MHz channel with punctured PBCH defined in TS 38.211 [9] clause 7.4.3.1. + +## 6 Conducted transmitter characteristics + +### 6.1 General + +Unless otherwise stated, the conducted transmitter characteristics are specified at the *antenna connector* for BS type 1-C and at the *TAB connector* for BS type 1-H, with a full complement of transceiver units for the configuration in normal operating conditions. + +For BS type 1-H the manufacturer shall declare the minimum number of supported geographical cells (i.e. geographical areas covered by beams). The minimum number of supported geographical cells ( $N_{\text{cells}}$ ) relates to the BS setting with the minimum amount of cell splitting supported with transmission on all *TAB connectors* supporting the *operating band*, or with minimum amount of transmitted beams. + +For BS type 1-H manufacturer shall also declare *TAB connector TX min cell groups*. Every *TAB connector* of the BS type 1-H supporting transmission in an *operating band* shall map to one *TAB connector TX min cell group* supporting the same *operating band*, where mapping of *TAB connectors* to cells/beams is implementation dependent. + +The number of *active transmitter units* that are considered when calculating the conducted TX emissions limits ( $N_{\text{TXU,counted}}$ ) for BS type 1-H is calculated as follows: + +$$N_{\text{TXU,counted}} = \min(N_{\text{TXU,active}}, \delta \times N_{\text{cells}})$$ + +$N_{\text{TXU,countedpercell}}$ is used for scaling of *basic limits* and is derived as $N_{\text{TXU,countedpercell}} = N_{\text{TXU,counted}} / N_{\text{cells}}$ + +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 and n101 and n102. + +### 6.2 Base station output power + +#### 6.2.1 General + +The BS conducted output power requirement is at *antenna connector* for BS type 1-C, or at *TAB connector* for BS type 1-H. + +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: BS type 1-C rated output power limits for BS classes** + +| BS class | $P_{\text{rated,c,AC}}$ | +|-----------------------------------------------------------------------------------------------------------------|-------------------------| +| Wide Area BS | (Note) | +| Medium Range BS | $\leq 38 \text{ dBm}$ | +| Local Area BS | $\leq 24 \text{ 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: BS type 1-H rated output power limits for BS classes** + +| BS class | $P_{\text{rated,c,sys}}$ | $P_{\text{rated,c,TABC}}$ | +|----------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------|---------------------------| +| Wide Area BS | (Note) | (Note) | +| Medium Range BS | $\leq 38 \text{ dBm} + 10\log(N_{\text{TXU,counted}})$ | $\leq 38 \text{ dBm}$ | +| Local Area BS | $\leq 24 \text{ dBm} + 10\log(N_{\text{TXU,counted}})$ | $\leq 24 \text{ 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. + +## 6.2.2 Minimum requirement for BS type 1-C + +In normal conditions, $P_{\max,c,AC}$ shall remain within +2 dB and -2 dB of the *rated carrier output power* $P_{\text{rated,c,AC}}$ , declared by the manufacturer. + +In extreme conditions, $P_{\max,c,AC}$ shall remain within +2.5 dB and -2.5 dB of the *rated carrier output power* $P_{\text{rated,c,AC}}$ , declared by the manufacturer. + +In certain regions, the minimum requirement for normal conditions may apply also for some conditions outside the range of conditions defined as normal. + +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.2.3 Minimum requirement for BS type 1-H + +In normal conditions, $P_{\max,c,TABC}$ shall remain within +2 dB and -2 dB of the *rated carrier output power* $P_{\text{rated,c,TABC}}$ for each *TAB connector* as declared by the manufacturer. + +In extreme conditions, $P_{\max,c,TABC}$ shall remain within +2.5 dB and -2.5 dB of the *rated carrier output power* $P_{\text{rated,c,TABC}}$ for each *TAB connector* as declared by the manufacturer. + +In certain regions, the minimum requirement for normal conditions may apply also for some conditions outside the range of conditions defined as normal. + +## 6.2.4 Additional requirements (regional) + +In certain regions, additional regional requirements may apply. + +For Band n41 and n90 operation in Japan, the rated output power, $P_{\text{rated,c,sys}}$ for BS type 1-H or 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}}$ of the WA BS shall not exceed $51.5 \text{ dBm/5MHz} + (f_{DL}-922.1) \times 40/3 \text{ dB}$ , with $f_{DL}$ being the centre frequency in MHz. This limit is derived from ECC Decision(20)02 [21] assuming a 17 dBi maximum antenna gain and 4 dB 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. + +NOTE: for more details on the maximum level derivation, refer to TR 38.853 [23]. + +NOTE: The additional maximum output power requirement for 3 MHz channel bandwidth will be updated in a later version, based on CEPT WG FM's feedback. + +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 [21] assuming a 18 dBi maximum antenna gain and 4 dB 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. + +NOTE: for more details on the maximum level derivation, refer to TR 38.852 [22]. + +## 6.3 Output power dynamics + +### 6.3.1 General + +The requirements in clause 6.3 apply during the *transmitter ON period*. 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 BS at maximum output power ( $P_{\max,c,AC}$ or $P_{\max,c,TABC}$ ) for a specified reference condition. + +For *BS type 1-C* this requirement shall apply at the *antenna connector* supporting transmission in the *operating band*. + +For *BS type 1-H* this requirement shall apply at each *TAB connector* supporting transmission in the *operating band*. + +#### 6.3.2.2 Minimum requirement for *BS type 1-C* and *BS type 1-H* + +RE power control dynamic range: + +**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) | 0 | 0 | +| 256QAM (PDSCH) | 0 | 0 | +| 1024QAM (PDSCH) | 0 | 0 | +| NOTE: The output power per carrier shall always be less or equal to the maximum output power of the base station. | | | + +### 6.3.3 Total power dynamic range + +#### 6.3.3.1 General + +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. + +For *BS type 1-C* this requirement shall apply at the *antenna connector* supporting transmission in the *operating band*. + +For *BS 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 BS 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. + +NOTE 2: The requirement does not apply to operation with shared spectrum channel access. + +#### 6.3.3.2 Minimum requirement for *BS type 1-C* and *BS type 1-H* + +The downlink (DL) total power dynamic range for each NR 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** + +| BS channel bandwidth (MHz) | Total power dynamic range (dB) | | | +|-----------------------------------|---------------------------------------|-------------------|-------------------| +| | 15 kHz SCS | 30 kHz SCS | 60 kHz SCS | +| 3 | 11.7 | N/A | N/A | +| 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 | +| 25 | 21.2 | 18.1 | 14.9 | +| 30 | 22 | 18.9 | 15.7 | +| 35 | 22.7 | 19.6 | 16.4 | +| 40 | 23.3 | 20.2 | 17 | +| 45 | 23.8 | 20.7 | 17.6 | +| 50 | 24.3 | 21.2 | 18.1 | +| 60 | N/A | 22 | 18.9 | +| 70 | N/A | 22.7 | 19.6 | +| 80 | N/A | 23.3 | 20.2 | +| 90 | N/A | 23.8 | 20.8 | +| 100 | N/A | 24.3 | 21.3 | + +## 6.3.4 NB-IoT RB power dynamic range for NB-IoT operation in NR in-band + +### 6.3.4.1 General + +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_{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 + +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.2-1. This power dynamic range level is only required for one NB-IoT RB. + +**Table 6.3.4.2-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 | +6 | +| 15 | Within center $77 \cdot 180\text{kHz} + 15\text{kHz}$ at each edge | +6 | +| | Other | +3 | +| 20 | Within center $102 \cdot 180\text{kHz} + 15\text{kHz}$ at each edge | +6 | +| | Other | +3 | +| 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | Within center 90% of BS channel bandwidth | +6 | +| | Other | +3 | + +## 6.4 Transmit ON/OFF power + +### 6.4.1 Transmitter OFF power + +#### 6.4.1.1 General + +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 for BS type 1-C + +For BS type 1-C, the requirements for transmitter OFF power spectral density shall be less than -85 dBm/MHz per *antenna connector*. + +#### 6.4.1.3 Minimum requirement for BS type 1-H + +For BS type 1-H, the requirements for transmitter OFF power spectral density shall be less than -85 dBm/MHz per *TAB connector*. + +### 6.4.2 Transmitter transient period + +#### 6.4.2.1 General + +*Transmitter transient period* requirements apply only to TDD operation of the BS. + +The *transmitter transient period* is the time period during which the transmitter is changing from the *transmitter OFF period* to the *transmitter ON period* or vice versa. The *transmitter transient period* is illustrated in figure 6.4.2.1-1. + +![Figure 6.4.2.1-1: Example of relations between 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: 'ON power level' and 'OFF power level'. The x-axis is divided into three main segments: 'UL transmission' (left), 'Transmitter ON period (DL transmission)' (middle), and 'GP or UL transmission' (right). The 'ON power level' segment shows a curve that rises from the 'OFF power level' to the 'ON power level' and then falls back. 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 at the beginning of the graph and one at the end.](cef8059e51ebeb728bca695b6f92dec3_img.jpg) + +Figure 6.4.2.1-1: Example of relations between 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: 'ON power level' and 'OFF power level'. The x-axis is divided into three main segments: 'UL transmission' (left), 'Transmitter ON period (DL transmission)' (middle), and 'GP or UL transmission' (right). The 'ON power level' segment shows a curve that rises from the 'OFF power level' to the 'ON power level' and then falls back. 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 at the beginning of the graph and one at the end. + +**Figure 6.4.2.1-1: Example of relations between transmitter ON period, transmitter OFF period and transmitter transient period** + +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.4.2.2 Minimum requirement for BS type 1-C and BS type 1-H 1-H + +For BS type 1-C and BS type 1-H, the *transmitter transient period* shall be shorter than the values listed in the minimum requirement table 6.4.2.2-1. + +**Table 6.4.2.2-1: Minimum requirement for the transmitter transient period for BS type 1-C and BS type 1-H** + +| Transition | Transient period length ( $\mu\text{s}$ ) | +|------------|-------------------------------------------| +| OFF to ON | 10 | +| ON to OFF | 10 | + +#### 6.4.2.3 Void + +### 6.5 Transmitted signal quality + +#### 6.5.1 Frequency error + +##### 6.5.1.1 General + +The requirements in clause 6.5.1 apply to the *transmitter ON period*. + +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. + +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.1.2 Minimum requirement for BS type 1-C and BS type 1-H + +For BS type 1-C and BS type 1-H, 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.1.2-1 observed over 1 ms. + +The frequency error requirement for NB-IoT are specified in TS 36.104 [13] clause 6.5.1. + +**Table 6.5.1.2-1: Frequency error minimum requirement** + +| BS class | Accuracy | +|-----------------|----------------| +| Wide Area BS | $\pm 0.05$ ppm | +| Medium Range BS | $\pm 0.1$ ppm | +| Local Area BS | $\pm 0.1$ ppm | + +#### 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 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 for BS type 1-C and BS type 1-H + +For BS type 1-C and 1-H, the EVM levels of each NR 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 BS type 1-C and BS type 1-H carrier** + +| Modulation scheme for PDSCH | Required EVM | +|-----------------------------|---------------------------------------------------------------------------| +| QPSK | 17.5 % | +| 16QAM | 12.5 % | +| 64QAM | 8 % | +| 256QAM | 3.5 % | +| 1024QAM | 2.5 % 1
2.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. | + +The modulation quality requirements for NB-IoT are specified in TS 36.104 [13] clause 6.5.2. + +### 6.5.2.3 EVM frame structure for measurement + +EVM shall be evaluated for each NR 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 NR, for all bandwidths, the EVM measurement shall be performed for each NR 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 + +### 6.5.3.1 General + +This requirement shall apply 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. The RF signals present at the BS transmitter *antenna connectors* or *transceiver array boundary* may experience certain timing differences in relation to each other. + +The TAE is specified for a specific set of signals/transmitter configuration/transmission mode. + +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.3.2 Minimum requirement for BS type 1-C and BS type 1-H + +For MIMO transmission, at each carrier frequency, TAE shall not exceed 65 ns. + +For *intra-band contiguous carrier aggregation*, with or without MIMO, TAE shall not exceed 260ns. + +For *intra-band non-contiguous carrier aggregation*, with or without MIMO, TAE shall not exceed 3µs. + +For *inter-band carrier aggregation*, with or without MIMO, TAE shall not exceed 3µs. + +The time alignment error requirements for NB-IoT are specified in TS 36.104 [13] clause 6.5.3. + +**Table 6.5.3.2-1: Void****Table 6.5.3.2-2: Void****Table 6.5.3.2-3: Void** + +## 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 *BS 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-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 | +| 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 | + +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* for band n46, n96 and n102** + +| 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 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 [3]. + +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 requirement for *BS type 1-C* and *BS type 1-H* + +The occupied bandwidth for each NR carrier shall be less than the *BS channel bandwidth*. For intra-band contiguous CA, the occupied bandwidth shall be less than or equal the *Aggregated BS Channel Bandwidth*. + +For NB-IoT operation in NR in-band, the occupied bandwidth for each NR carrier with NB-IoT shall be less than than the *BS 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 *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 shall apply during the *transmitter ON period*. + +### 6.6.3.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_{\text{Config}}$ ) centred on the assigned channel frequency and a filter centred on the adjacent channel frequency according to the tables below. + +For operation in paired and unpaired spectrum, the ACLR shall be higher than the value specified in table 6.6.3.2-1 in any operating band except for band n46, n96 and n102. + +**Table 6.6.3.2-1: Base station ACLR limit** + +| BS channel bandwidth of lowest/highest carrier transmitted BW_{Channel} (MHz) | BS adjacent channel centre frequency offset below the lowest or above the highest carrier centre frequency transmitted | Assumed adjacent channel carrier (informative) | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|---------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|------------------------------------------------------------------------------------|-----------------------| +| 3, 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | $BW_{Channel}$ | NR of same BW (Note 2) | Square ( $BW_{Config}$ ) | 45 dB, 38 dB (Note 4) | +| | $2 \times BW_{Channel}$ | NR of same BW (Note 2) | Square ( $BW_{Config}$ ) | 45 dB, 38 dB (Note 4) | +| | $BW_{Channel} / 2 + 2.5$ MHz | 5 MHz E-UTRA | Square (4.5 MHz) | 45 dB (Note 3) | +| | $BW_{Channel} / 2 + 7.5$ MHz | 5 MHz E-UTRA | Square (4.5 MHz) | 45 dB (Note 3) | + +NOTE 1: $BW_{Channel}$ and $BW_{Config}$ are the BS 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}$ ). +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 38 dB applies. For BS operating in other bands, ACLR requirement 45 dB applies. + +For band n46, n96 and n102, the ACLR shall be higher than the value specified in Table 6.6.3.2-1a. + +**Table 6.6.3.2-1a: Base station ACLR limit for band n46, n96 and n102** + +| BS channel bandwidth of lowest/highest NR carrier transmitted BW_{Channel} (MHz) | BS adjacent channel centre frequency offset below the lowest or above the highest carrier centre frequency transmitted | Assumed adjacent channel carrier (informative) | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|------------------------------------------------------------------------------------|-------------------| +| 10, 20, 40, 60, 80 | $BW_{Channel}$ | NR of same BW (Note 2) | Square ( $BW_{Config}$ ) | 35 dB | +| | $2 \times BW_{Channel}$ | NR of same BW (Note 2) | Square ( $BW_{Config}$ ) | 40 dB | + +NOTE 1: $BW_{Channel}$ and $BW_{Config}$ are the BS channel bandwidth and transmission bandwidth configuration of the lowest/highest NR carrier transmitted on the assigned channel frequency. +NOTE 2: With SCS that provides largest transmission bandwidth configuration ( $BW_{Config}$ ). + +The ACLR absolute *basic limit* is specified in table 6.6.3.2-2. + +**Table 6.6.3.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, the ACLR shall be higher than the value specified in Table 6.6.3.2-2a in any operating band except for band n46, n96 and n102. + +**Table 6.6.3.2-2a: Base Station ACLR limit in non-contiguous spectrum or multiple bands** + +| BS channel bandwidth of 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 | ACLR limit | +|-----------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|------------------------------------------------------------------------------------|-----------------------| +| 3, 5, 10, 15, 20 | W gap ≥ 15 (Note 3)
W gap ≥ 45 (Note 4) | 2.5 MHz | 5 MHz NR (Note 2) | Square (BW Config ) | 45 dB, 38 dB (Note 5) | +| | W gap ≥ 20 (Note 3)
W gap ≥ 50 (Note 4) | 7.5 MHz | 5 MHz NR (Note 2) | Square (BW Config ) | 45 dB, 38 dB (Note 5) | +| 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | W gap ≥ 60 (Note 4)
W gap ≥ 30 (Note 3) | 10 MHz | 20 MHz NR (Note 2) | Square (BW Config ) | 45 dB, 38 dB (Note 5) | +| | W gap ≥ 80 (Note 4)
W gap ≥ 50 (Note 3) | 30 MHz | 20 MHz NR (Note 2) | Square (BW Config ) | 45 dB, 38 dB (Note 5) | + +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 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 38 dB applies. For BS operating in other bands, ACLR requirement 45 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-2b. + +**Table 6.6.3.2-2b: Base Station ACLR limit in non-contiguous spectrum 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 | ACLR limit | +|--------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|------------------------------------------------------------------------------------|-------------------| +| 10, 20, 40, 60, 80 | W gap ≥ 60 | 10 MHz | 20 MHz NR (Note 2) | Square (BW Config ) | 35 dB | +| | 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 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.2-3 and the filters on the assigned channels are defined in table 6.6.3.2-4. + +For operation in non-contiguous spectrum or multiple bands, 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.2-3. + +The CACLR requirements in Table 6.6.3.2-3 apply to BS that supports NR, in any operating band except for band n46, n96 and n102. The CACLR requirements for band n46, n96 and n102 are in Table 6.6.3.2-3aa. + +**Table 6.6.3.2-3: Base Station CACLR limit** + +| BS channel bandwidth of 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 | +|-----------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|------------------------------------------------------------------------------------|--------------------------| +| 3, 5, 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 ) | 45 dB,
38 dB (Note 5) | +| | 10 < W gap < 20 (Note 3)
10 ≤ W gap < 50 (Note 4) | 7.5 MHz | 5 MHz NR (Note 2) | Square (BW Config ) | 45 dB,
38 dB (Note 5) | +| 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 ) | 45 dB,
38 dB (Note 5) | +| | 40 < W gap < 80 (Note 4)
40 ≤ W gap < 50 (Note 3) | 30 MHz | 20 MHz NR (Note 2) | Square (BW Config ) | 45 dB,
38 dB (Note 5) | + +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 *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 38 dB applies. For BS operating in other bands, ACLR requirement 45 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.2-3aa. + +**Table 6.6.3.2-3aa: 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 ≤ 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.2-3a. + +**Table 6.6.3.2-3a: 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.2-4: 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.3 Minimum requirement for BS type 1-C + +The ACLR (CACLR) absolute *basic limits* in table 6.6.3.2-2, 6.6.3.2-3a or the ACLR (CACLR) *limits* in table 6.6.3.2-1, 6.6.3.2-2a or 6.6.3.2-3, 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 BS type 1-C. + +### 6.6.3.4 Minimum requirement for BS type 1-H + +The ACLR (CACLR) absolute *basic limits* in table 6.6.3.2-2 + X, 6.6.3.2-3a + X (where $X = 10\log_{10}(N_{\text{TXU, counted per cell}})$ ) or the ACLR (CACLR) *limits* in table 6.6.3.2-1, 6.6.3.2-2a or 6.6.3.2-3, whichever is less stringent, shall apply for each *TAB connector TX min cell group*. + +NOTE: Conformance to the BS type 1-H ACLR requirement can be demonstrated by meeting at least one of the following criteria as determined by the manufacturer: + +- 1) The ratio of the sum of the filtered mean power measured on each *TAB connector* in the *TAB connector TX min cell group* at the assigned channel frequency to the sum of the filtered mean power measured on each *TAB connector* in the *TAB connector TX min cell group* at the adjacent channel frequency shall be greater than or equal to the ACLR *basic 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 *basic 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 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 General + +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 -3dB point of the measuring filter closest to the carrier frequency. +- $f\_offset$ is the separation between the *channel edge* frequency and the centre of the measuring filter. +- $f\_offset_{max}$ is the offset to the frequency $\Delta f_{OBUE}$ outside the downlink *operating band*, where $\Delta f_{OBUE}$ is defined in table 6.6.1-1. +- $\Delta f_{max}$ is equal to $f\_offset_{max}$ minus half of the bandwidth of the measuring filter. + +For a *multi-band connector* inside any *Inter RF Bandwidth gaps* with $W_{gap} < 2 * \Delta f_{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 clauses 6.6.4.2.1 to 6.6.4.2.4 below, where in this case: + +- $\Delta f$ is the separation between the *Base Station RF Bandwidth edge* frequency and the nominal -3 dB point of the measuring filter closest to the *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-carrier *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 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 limits* 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 clauses 6.6.4.2.1 to 6.6.4.2.4 below, where in this case: + +- $\Delta f$ is the separation between the *sub-block edge* frequency and the nominal -3 dB point of the measuring filter closest to the *sub-block edge*. +- $f\_offset$ is the separation between the *sub-block edge* frequency and the centre of the measuring filter. +- $f\_offset_{max}$ is equal to the *sub-block gap* bandwidth minus half of the bandwidth of the measuring filter. +- $\Delta f_{max}$ is equal to $f\_offset_{max}$ minus half of the bandwidth of the measuring filter. + +For Wide Area BS, the requirements of either clause 6.6.4.2.1 (Category A limits) or clause 6.6.4.2.2 (Category B limits) shall apply. + +For Medium Range BS, the requirements in clause 6.6.4.2.3 shall apply (Category A and B). + +For Local Area BS, the requirements of clause 6.6.4.2.4 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 Basic limits + +### 6.6.4.2.1 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 tables 6.6.4.2.1-1 and 6.6.4.2.1-1a. + +**Table 6.6.4.2.1-1: Wide Area BS operating band unwanted emission limits for above 3 MHz channel bandwidth (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 limits (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}$ | $- 7 \text{ dBm} - \frac{7}{5} \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -14 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -13 dBm (Note 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 -13 dBm/100 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.2.1-1a: Wide Area BS operating band unwanted emission limits for 3 MHz channel bandwidth (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 limits (Note 1, 2) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | $- 5 \text{ dBm} - \frac{10}{3} \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | -15 dBm | 100 kHz | +| $6 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $6.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -13 dBm | 100 kHz | + +NOTE 1: For a 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 6 \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 \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*. + +For BS operating in Bands n1, n2, n3, n7, n24, n25, n30, n34, n38, n39, n40, n41, n48, n50, n54, n65, n66, n70, n74, n75, n77, n78, n79, n90, n92, n94, n109, *basic limits* are specified in table 6.6.4.2.1-2: + +**Table 6.6.4.2.1-2: Wide Area BS operating band unwanted emission limits (NR bands above 1 GHz) for Category A** + +| 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 < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-7 \text{ dBm} - \frac{7}{5} \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -14 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -13 dBm (Note 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 \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.6.4.2.2 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.2.2.1 or clause 6.6.4.2.2.2 shall be applied. + +##### 6.6.4.2.2.1 Category B requirements (Option 1) + +For BS operating in Bands n5, n8, n12, n20, n26, n28, n29, n31, n67, n71, n72, n85, n105, the *basic limits* are specified in tables 6.6.4.2.2.1-1 and 6.6.4.2.2.1-1a.: + +**Table 6.6.4.2.2.1-1: Wide Area BS operating band unwanted emission limits for above 3 MHz channel bandwidth(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 limits (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}$ | $-7 \text{ dBm} - \frac{7}{5} \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -14 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -16 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 -16 dBm/100 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*, where the contribution from the far-end *sub-block* or RF Bandwidth shall be scaled according to the *measurement bandwidth* of the near-end *sub-block* or RF Bandwidth. + +NOTE 3: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.6.4.2.2.1-1a: Wide Area BS operating band unwanted emission limits for 3 MHz channel bandwidth (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 limits (Note 1, 2) | Measurement bandwidth | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | $-5 \text{ dBm} - \frac{10}{3} \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | -15 dBm | 100 kHz | +| $6 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $6.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -16 dBm | 100 kHz | +| NOTE 1: For a 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 6 \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_{\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. | | | | + +For BS operating in Bands n1, n2, n3, n7, n25, n34, n38, n39, n40, n41, n48, n50, n65, n66, n70, n75, n77, n78, n79, n90, n92, n94, n109, *basic limits* are specified in tables 6.6.4.2.2.1-2: + +**Table 6.6.4.2.2.1-2: Wide Area BS operating band unwanted emission limits (NR bands above 1 GHz) for Category B** + +| 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 < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-7 \text{ dBm} - \frac{7}{5} \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -14 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -15 dBm (Note 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_{\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 type I-C operating in Band n104, the limits are specified in tables 6.6.4.2.2.1-2a: + +**Table 6.6.4.2.2.1-2a: 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})$ | -14 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_{\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 tables 6.6.4.2.2.1-2b: + +**Table 6.6.4.2.2.1-2b: 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})$ | -14 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.2.2.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, n101. + +For a BS operating in bands n1, n3, n8, n65 or *BS type I-C* operating in bands n7, n38, n100 or n101, *basic limits* are specified in Tables 6.6.4.2.2.2-1 and 6.6.4.2.2.2-1a.: + +**Table 6.6.4.2.2.2-1: Regional Wide Area BS operating band unwanted emission limits for above 3 MHz channel bandwidth for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limits (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}$ | -14 dBm | 30 kHz | +| $0.2 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.215 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | (Note 5) | 30 kHz | +| (Note 4) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -26 dBm (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})$ | -13 dBm (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) (Note 5) | 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}$ . + +**Table 6.6.4.2.2.2-1a: Regional Wide Area BS operating band unwanted emission limits for 3 MHz channel bandwidth for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limits (Note 1, 2) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|--------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$ | | 30 kHz | +| $0.05 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ | $0.065 \text{ MHz} \leq f\_offset < 0.165 \text{ MHz}$ | | 30 kHz | +| $0.15 \text{ MHz} \leq \Delta f < 0.2 \text{ MHz}$ | $0.165 \text{ MHz} \leq f\_offset < 0.215 \text{ MHz}$ | -14 dBm | 30 kHz | +| $0.2 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.215 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | | 30 kHz | +| (Note 3) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -26 dBm | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq 6 \text{ MHz}$ | $1.5 \text{ MHz} \leq f\_offset < 6.5 \text{ MHz}$ | -13 dBm | 1 MHz | +| $6 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $6.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -15 dBm | 1 MHz | + +NOTE 1: For a 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 6 \text{ MHz}$ from both adjacent *sub-blocks* on each side of the *sub-block gap*, where the minimum requirement within *sub-block gaps* shall be -15dBm/1MHz. + +NOTE 2: For 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: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +#### 6.6.4.2.3 Basic limits for Medium Range BS (Category A and B) + +For Medium Range BS, *basic limits* are specified in tables 6.6.4.2.3-1, 6.6.4.2.3-1aa, 6.6.4.2.3-2, and 6.6.4.2.3-2aa except for Band n104. + +For the tables in this clause for *BS type 1-C* $P_{\text{rated},x} = P_{\text{rated},c,\text{AC}}$ , and for *BS type 1-H* $P_{\text{rated},x} = P_{\text{rated},c,\text{cell}} - 10 \cdot \log_{10}(N_{\text{TXU},\text{countedpercell}})$ , and for *BS type 1-O* $P_{\text{rated},x} = P_{\text{rated},c,\text{TRP}} - 9$ dB. + +**Table 6.6.4.2.3-1: Medium Range BS operating band unwanted emission limits for above 3 MHz channel bandwidth, $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 (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} - 60 \text{ dB}$ | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $\min(P_{\text{rated},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.2.3-1aa: Medium Range BS operating band unwanted emission limits for 3 MHz channel bandwidth, $31 < P_{\text{rated},c} \leq 38$ dBm** + +| 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 < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | $P_{\text{rated},c} - 59 \text{ dB}$ | 100 kHz | +| $6 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $6.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $\min(P_{\text{rated},c} - 59 \text{ dB}, -25 \text{ dBm})$ | 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 6 \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} - 59 \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*. + +For *BS type 1-C* operating in Band n104, the limits are specified in Table 6.6.4.2.3-1a and Table 6.6.4.2.3-2a. + +**Table 6.6.4.2.3-1a. 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}} - 60 \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.2.3-1b and Table 6.6.4.2.3-2b: + +**Table 6.6.4.2.3-1b. 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}} - 60 \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.2.3-2: Medium Range BS operating band unwanted emission limits for above 3 MHz channel bandwidth, $P_{\text{rated,x}} \leq 31$ dBm** + +| 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 < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -29 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -29 dBm (Note 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 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}$ . | | | | + +**Table 6.6.4.2.3-2aa: Medium Range BS operating band unwanted emission limits for 3 MHz channel bandwidth, $P_{\text{rated,c}} \leq 31$ dBm** + +| 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 < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | -28 dBm | 100 kHz | +| $6 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $6.05 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -28 dBm | 100 kHz | + +NOTE 1: For a 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 6 \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 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*. + +**Table 6.6.4.2.3-2a. Medium Range BS type 1-C operating band unwanted emission limits for band 104, $P_{\text{rated,x}} \leq 31$ 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_{\text{max}})$ | $20.05 \text{ MHz} \leq f\_offset < \min(40.05 \text{ MHz}, f\_offset_{\text{max}})$ | -29 dBm | 100 kHz | +| $40 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $40.05 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -29 dBm | 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_{\text{max}} < 40 \text{ MHz}$ . + +**Table 6.6.4.2.3-2b. Medium Range BS type 1-H operating band unwanted emission limits for band 104, $P_{\text{rated,x}} \leq 31$ 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_{\text{max}})$ | $50.05 \text{ MHz} \leq f\_offset < \min(100.05 \text{ MHz}, f\_offset_{\text{max}})$ | -29 dBm | 100 kHz | +| $100 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$ | $100.05 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | -29 dBm | 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_{\text{max}} < 100 \text{ MHz}$ . + +#### 6.6.4.2.4 Basic limits for Local Area BS (Category A and B) + +For Local Area BS, *basic limits* are specified in tables 6.6.4.2.4-1 and 6.6.4.2.4-1aa, except for n46, n96, n102 and n104. + +**Table 6.6.4.2.4-1: Local Area BS operating band unwanted emission limits for above 3 MHz channel bandwidth** + +| 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 < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -37 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -37 dBm (Note 10) | 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 -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} < 10 \text{ MHz}$ . | | | | + +**Table 6.6.4.2.4-1aa: Local Area BS operating band unwanted emission limits for 3 MHz channel bandwidth** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limits (Note 1, 2) | Measurement bandwidth | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------|--------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 3 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 3.05 \text{ MHz}$ | | 100 kHz | +| $3 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $3.05 \text{ MHz} \leq f\_offset < 6.05 \text{ MHz}$ | -35 dBm | 100 kHz | +| $6 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $6.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -35 dBm | 100 kHz | +| NOTE 1: For a 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 6 \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 -35dBm/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 | | | | + +For BS type 1-C operating in Band n104, the limits are specified in Table 6.6.4.2.4-1a. + +**Table 6.6.4.2.4-1a. 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})$ | -37 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 | 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 * \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.2.4-1b: + +**Table 6.6.4.2.4-1b. 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})$ | -37 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 | 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.2.4A Basic limits for Local Area and Medium Range BS for bands 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.2.4A-1. For Local Area and Medium Range BS operating in bands n46, n96 and n102, basic limits for 20 MHz, 40 MHz, 60 MHz, 80 MHz and 100 MHz channel bandwidth are specified in table 6.6.4.2.4A-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.2.4A-3, and for two non-transmitted channels basic limits are specified in table 6.6.4.2.4A-4, and for three non-transmitted channels basic limits are specified in table 6.6.4.2.4A-5. + +**Table 6.6.4.2.4A-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}$ | (, -40dBm) | 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})$ | (, -40dBm) | 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})$ | (, -40dBm) | 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} - 59.5 \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} - 61.5 \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} - 66.5 \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} - 59.5 \text{ dB}, -40 \text{ dBm})/100 \text{ kHz}$ . + +**Table 6.6.4.2.4A-2: Medium Range BS and Local Area BS operating band unwanted emission limits for 20 MHz, 40 MHz, 60 MHz, 80 MHz and 100 MHz channel bandwidth for bands 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}$ | $\text{ , -40dBm}$ | 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})$ | $\text{ , -40dBm}$ | 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})$ | $\text{ Max(, -40dBm)}$ | 100 kHz | +| $N \text{ MHz} \leq \Delta f < \min(8.5N \text{ MHz}, \Delta f_{\max})$ | $(N+0.05) \text{ MHz} \leq f\_offset < \min((8.5N+0.05) \text{ MHz}, f\_offset_{\max})$ | | 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, two or three non-transmitted 20 MHz channels between transmitted channels, when a NR-U channel bandwidth of 60 MHz, 80 MHz or 100 MHz have been assigned, the spectrum emission mask for non-transmitted channels specified in Table 6.6.4.2.4A-3, Table 6.6.4.2.4A-4 and Table 6.6.4.2.4A-5 applies for one, two, and three non-transmitted channels respectively. The spectrum emission mask for non-transmitted channels apply to frequencies ( $\Delta f_{\text{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.2.4A-3, Table 6.6.4.2.4A-4 and Table 6.6.4.2.4A-5 in the case of non-transmitted channels between transmitted channels. + +**Table 6.6.4.2.4A-3: Medium Range BS and Local Area BS operating band unwanted emission limits for one non-transmitted channel for 60 MHz, 80 MHz and 100 MHz channel bandwidth for bands n46, n96 and n102** + +| Frequency offset of measurement filter -3dB point, $\Delta f_{\text{BE\_offset}}$ | Frequency offset of measurement filter centre frequency, $f\_BE\_offset$ | Basic limits | Measurement bandwidth | +|-----------------------------------------------------------------------------------|--------------------------------------------------------------------------|--------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f_{\text{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_{\text{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_{\text{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_{\text{BE\_offset}} < 19.9 \text{ MHz}$ | $19.05 \text{ MHz} \leq f\_BE\_offset < 19.95 \text{ MHz}$ | | 100 kHz | + +**Table 6.6.4.2.4A-4: Medium Range BS and Local Area BS operating band unwanted emission limits for two non-transmitted channels for 80 MHz and 100 MHz channel bandwidth for bands 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 | + +**Table 6.6.4.2.4A-5: Medium Range BS and Local Area BS operating band unwanted emission limits for three non-transmitted channels for 100 MHz channel bandwidth for bands 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} < 50 \text{ MHz}$ | $10.05 \text{ MHz} \leq f\_BE\_offset < 50.05 \text{ MHz}$ | | 100 kHz | +| $50 \text{ MHz} \leq \Delta f_{BE\_offset} < 59 \text{ MHz}$ | $50.05 \text{ MHz} \leq f\_BE\_offset < 59.05 \text{ MHz}$ | | 100 kHz | +| $59 \text{ MHz} \leq \Delta f_{BE\_offset} < 59.9 \text{ MHz}$ | $59.05 \text{ MHz} \leq f\_BE\_offset < 59.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.2.4A-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: . + +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.2.5 Basic limits for additional requirements + +##### 6.6.4.2.5.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, the BS may have to comply with the applicable emission limits established by FCC Title 47 [8], when deployed in regions where those limits are applied, and under the conditions declared by the manufacturer. + +##### 6.6.4.2.5.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.2.5.2-1, a *basic limits* $P_{\text{EM,N}}$ is declared by the manufacturer. This requirement applies in the frequency range 470-790 MHz even though part of the range falls in the spurious domain. + +**Table 6.6.4.2.5.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 [13], annex F. + +##### 6.6.4.2.5.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.2.5.3-1. + +**Table 6.6.4.2.5.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.2.5.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.2.5.4-1. + +**Table 6.6.4.2.5.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} \leq \Delta f < 83.5 \text{ MHz}$ | $6.5 \text{ MHz} \leq f\_offset < 83 \text{ MHz}$ | -25 dBm | 1 MHz | +| 10 | 2400 - 2473.5 | $10 \text{ MHz} \leq \Delta f < 83.5 \text{ MHz}$ | $10.5 \text{ MHz} \leq f\_offset < 83 \text{ MHz}$ | -25 dBm | 1 MHz | +| 5 | 2477.5 - 2478.5 | $5 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $5.5 \text{ MHz}$ | -13 dBm | 1 MHz | +| 10 | 2473.5 - 2478.5 | $5 \text{ MHz} \leq \Delta f < 10 \text{ MHz}$ | $5.5 \text{ MHz} \leq f\_offset < 9.5 \text{ MHz}$ | -13 dBm | 1 MHz | +| All | 2478.5 - 2483.5 | $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.5 \text{ MHz} \leq f\_offset < 4.5 \text{ MHz}$ | -10 dBm | 1 MHz | +| 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.2.5.5 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.2.5.6 Additional operating band unwanted emissions limits for Band n24 + +In regions where FCC regulation applies, requirements for protection of GPS according to FCC Order DA 20-48 applies for operation in Band n24. The following normative requirement covers the base station, to be used together with other information about the site installation to verify compliance with the requirement in FCC Order DA 20-48. The requirement applies to BS operating in Band n24 to ensure that appropriate interference protection is provided to the 1541 – 1650 MHz band. This requirement applies to the frequency range 1541-1650 MHz, even though part of this range falls within the spurious domain. + +The level of emissions in the 1541 – 1650 MHz band, measured in measurement bandwidth according to Table 6.6.4.2.5.6-1 shall not exceed the maximum emission levels $P_{EM,B24,a}$ , $P_{EM,B24,b}$ , $P_{EM,B24,c}$ , $P_{EM,B24,d}$ , $P_{EM,B24,e}$ and $P_{EM,B24,f}$ declared by the manufacturer. + +**Table 6.6.4.2.5.6-1: Declared emissions levels for protection of the 1541-1650 MHz band** + +| Operating Band | Frequency range | Declared emission level (dBW) (Measurement bandwidth = 1 MHz) | Declared emission level (dBW) of discrete emissions of less than 700 Hz bandwidth (Measurement bandwidth = 1 kHz) | Declared emission level (dBW) of discrete emissions of less than 2 kHz bandwidth (Measurement bandwidth = 1 kHz) | +|----------------|-----------------|---------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------| +| n24 | 1541 - 1559 MHz | $P_{EM,B24,a}$ | | $P_{EM,B24,f}$ | +| | 1559 - 1610 MHz | $P_{EM,B24,b}$ | $P_{EM,B24,d}$ | | +| | 1610 - 1650 MHz | $P_{EM,B24,c}$ | $P_{EM,B24,e}$ | | + +Note: The regional requirements in FCC Order DA 20-48 are defined in terms of EIRP (effective isotropic radiated power), which is dependent on both the BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The EIRP level is calculated using: $P_{EIRP} = P_E + G_{ant}$ where $P_E$ denotes the BS unwanted emission level at the antenna connector, $G_{ant}$ equals the BS antenna gain minus feeder loss. The requirement defined above provides the characteristics of the base station needed to verify compliance with the regional requirement. + +#### 6.6.4.2.5.7 Additional operating band unwanted emissions limits for Band n100 + +In CEPT countries where ECC Decision(20)02 [21] applies, the emissions of the WA BS shall not exceed the maximum levels specified in table 6.6.4.5.7-1. + +**Table 6.6.4.2.5.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 \text{ MHz}$ | -8 dBm | 1 MHz | +| NOTE: The basic limits are derived from ECC Decision(20)02 [21] assuming a 17 dBi maximum antenna gain and 4 dB losses, and assuming one antenna connector. For more details, refer to TR 38.853 [23] | | | | + +#### 6.6.4.3 Minimum requirements for 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 clause 6.6.4.2. + +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.4 Minimum requirements for 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 clause 6.6.4.2, 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, counted per cell}})$ . + +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 General + +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-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 [2]. + +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. + +The requirements shall also apply if the BS supports NB-IoT operation in NR in-band. + +Unless otherwise stated, all requirements are measured as mean power (RMS). + +### 6.6.5.2 Basic limits + +#### 6.6.5.2.1 General transmitter spurious emissions requirements + +The *basic limits* of either table 6.6.5.2.1-1 (Category A limits) or table 6.6.5.2.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. + +**Table 6.6.5.2.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 [2], s4.1. +NOTE 2: Upper frequency as in ITU-R SM.329 [2], 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.2.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 | -30 dBm | 1 MHz | Note 1, Note 2, Note 5 | + +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: 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.2.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 spurious emission *basic limits* are provided in table 6.6.5.2.2-1. + +**Table 6.6.5.2.2-1: BS spurious emissions *basic limits* for protection of the BS receiver** + +| BS class | Frequency range | Basic limits | Measurement bandwidth | Note | +|-----------------------------------------------------------------------------|----------------------------|---------------------|-----------------------|------| +| Wide Area BS | $F_{UL,low} - F_{UL,high}$ | -96 dBm | 100 kHz | | +| Medium Range BS | $F_{UL,low} - F_{UL,high}$ | -91 dBm | 100 kHz | | +| Local Area BS | $F_{UL,low} - F_{UL,high}$ | -88 dBm | 100 kHz | | +| NOTE 1: For BS operating in band n104, the basic limit is increased by 1dB. | | | | | + +### 6.6.5.2.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.5. + +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 *basic limits* are provided in table 6.6.5.2.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.2.3 -1 apply for each supported *operating band*. + +**Table 6.6.5.2.3-1: BS spurious emissions *basic 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 limits | 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.2.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.2.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.2.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.2.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.2.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.2.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.2.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.2.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.2.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.2.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.2.2. | +| UTRA FDD Band VIII or | 925 – 960 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band n8 or n100. | + +| System type for NR to co-exist with | Frequency range for co-existence requirement | Basic limits | Measurement bandwidth | Note | +|-----------------------------------------------------|----------------------------------------------|--------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| E-UTRA Band 8 or NR Band n8 | 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.2.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.2.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.2.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 n109. | +| | 1447.9 – 1462.9 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band n50, n74, n75, n92, 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.2.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.2.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.2.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.2.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 requirement does not apply to BS operating in band n77 or n78. | +| E-UTRA Band 24 or NR Band n24 | 1525 – 1559 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band n24. | +| | 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.2.2. | +| UTRA FDD Band XXV or E-UTRA Band 25 or NR band n25 | 1930 – 1995 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band 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.2.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.2.2. | + +| System type for NR to co-exist with | Frequency range for co-existence requirement | Basic limits | Measurement bandwidth | Note | +|-----------------------------------------------------|----------------------------------------------|--------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 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.2.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.2.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.2.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.2.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.2.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. | + +| System type for NR to co-exist with | Frequency range for co-existence requirement | Basic limits | Measurement bandwidth | Note | +|---------------------------------------------------|----------------------------------------------|--------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 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 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 BS operating in Band n41, n53 or [n90]. | +| 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 is not applicable to BS 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 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.2.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.2.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.2.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.2.2. | + +| System type for NR to co-exist with | Frequency range for co-existence requirement | Basic limits | Measurement bandwidth | Note | +|-------------------------------------|----------------------------------------------|--------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 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.2.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.2.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.2.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, n74, n75, n92, n94 or n109. | +| | 1427 – 1470 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band n50, n51, n74, n75, n76, n91, n92, n93 or n94 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 or 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.2.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.2.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.2.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.2.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.2.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.
For NR BS 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 BS operating in band n12 or n85, since it is already covered by the requirement in clause 6.6.5.2.2. | +| 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.2.2. | + +| System type for NR to co-exist with | Frequency range for co-existence requirement | Basic limits | Measurement bandwidth | Note | +|-------------------------------------|----------------------------------------------|--------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 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.2.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.2.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.2.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.2.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.2.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.2.2. | +| NR band n100 | 919.4 – 925 MHz | -52 dBm | 1 MHz | This requirement does not apply to 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.2.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 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 n5 or n26.
This requirement does not apply to BS operating in n106, since it is already covered by the requirement in clause 6.6.5.2.2. | + +| System type for NR to co-exist with | Frequency range for co-existence requirement | Basic limits | Measurement bandwidth | Note | +|-------------------------------------|----------------------------------------------|--------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------| +| 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 n28, since it is already covered by the requirement in clause 6.6.5.2.2. | + +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.2.3 -1 do not apply for the $\Delta f_{\text{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.6.5.2.3 -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. + +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 NR 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 spurious emission *basic limit* for this requirement is: + +**Table 6.6.5.2.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.2.3-3: Void** + +In certain regions, the following requirement may apply to NR BS operating in Band n50 and n75 within the 1432 – 1452 MHz, and in Band n51 and Band n76. The *basic limit* is specified in Table 6.6.5.2.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.2.3-4: Additional operating band unwanted emission *basic limit* for NR BS operating in Band n50 and n75 within 1432 – 1452 MHz, and in Band n51 and n76** + +| Filter centre frequency, $F_{\text{filter}}$ | Basic limit | Measurement Bandwidth | +|----------------------------------------------|-------------|-----------------------| +| $F_{\text{filter}} = 1413.5$ MHz | -42 dBm | 27 MHz | + +In certain regions, the following requirement may apply to BS 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.6.5.2.3-5, shall be defined according to the *basic limits* $P_{EM,n50/n75,a}$ nor $P_{EM,n50/n75,b}$ declared by the manufacturer. + +**Table 6.6.5.2.3-5: Operating band n50, n74 and n75 declared emission above 1518 MHz** + +| Filter centre frequency, $F_{filter}$ | Declared basic limits (dBm) | Measurement bandwidth | +|--------------------------------------------------------------|------------------------------------|-----------------------| +| $1518.5 \text{ MHz} \leq F_{filter} \leq 1519.5 \text{ MHz}$ | $P_{EM,n50/n75,a}$ | 1 MHz | +| $1520.5 \text{ MHz} \leq F_{filter} \leq 1558.5 \text{ MHz}$ | $P_{EM,n50/n75,b}$ | 1 MHz | + +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.2.3-6: BS Spurious emissions limits for protection of 700 MHz public safety operations** + +| Operating Band | Frequency range | Basic limit | 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 BS operating in Band n30. 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-7: Additional NR BS Spurious emissions limits for Band n30** + +| Frequency range | Basic limit | 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 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 | Basic limit | Measurement Bandwidth (NOTE 1) | Note | +|--------------------------------------------|-------------|--------------------------------|---------------------------------------------------------| +| 3530 MHz – 3720 MHz | -25 dBm | 1 MHz | Applicable 10 MHz from the assigned channel edge | +| 3100 MHz – 3530 MHz
3720 MHz – 4200 MHz | -40 dBm | 1 MHz | | + +NOTE 1: 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 2: The regional requirement, included in [12], is defined in terms of EIRP, which is dependent on both the BS emissions at the *antenna connector* and the deployment (including antenna gain and feeder loss). The requirement defined above provides the characteristics of the base station needed to verify compliance with the regional requirement. The assessment of the EIRP level is described in Annex F. + +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 | Basic limit | 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.2.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. The power of any spurious emission shall not exceed: + +**Table 6.6.5.2.3-11: Additional BS spurious emissions limits for Band n77** + +| Channel bandwidth [MHz] | Frequency range [MHz] | Filter centre frequency, $F_{filter}$ [MHz] | Basic limit [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.2.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 [21] assuming a 18 dBi maximum antenna gain and 4 dB losses, and assuming one antenna connector. For more details on the maximum level derivation, refer to TR 38.852 [23] | + +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.2.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 [21] assuming a 17 dBi maximum antenna gain and 4 dB losses, and assuming one antenna connector. For more details on the maximum level derivation, refer to TR 38.853 [23]. | + +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.2.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.2.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.2.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.2.4-1 for a BS where requirements for co-location with a BS type listed in the first column apply, depending on the declared Base Station class. For a *multi-band connector*, the exclusions and conditions in the Note column of table 6.6.5.2.4-1 shall apply for each supported *operating band*. + +**Table 6.6.5.2.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 limits | | | 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 or n94 | +| UTRA FDD Band XII or E-UTRA Band 12 or NR Band n12 | 699 – 716 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band XIII or E-UTRA Band 13 or NR Band n13 | 777 – 787 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band XIV or E-UTRA Band 14 or NR Band n14 | 788 – 798 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 17 | 704 – 716 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 18 or NR Band n18 | 815 – 830 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band XX or E-UTRA Band 20 or NR Band n20 | 832 – 862 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA FDD Band XXI or E-UTRA Band 21 | 1447.9 – 1462.9 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band 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 BS 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 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 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 BS 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 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 or n94 | +| E-UTRA Band 51 or NR Band n51 | 1427 – 1432 MHz | N/A | N/A | -88 dBm | 100 kHz | This is not applicable to BS operating in Band n50, n74, n75, n76, n91, n92, n93 or n94 | +| E-UTRA Band 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 85 | 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 | NA | NA | 100 kHz | | +| NR Band n101 | 1900 – 1910 MHz | -96 dBm | NA | NA | 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.2.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 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 [4]. + +NOTE 2: Table 6.6.5.2.4-1 assumes that two *operating bands*, where the corresponding BS 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. + +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.3 Minimum requirements for 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.2. + +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.2. + +### 6.6.5.4 Minimum requirements for 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.2, 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 General + +The transmitter intermodulation requirement is a measure of the capability of the transmitter unit to inhibit the generation of signals in its non-linear elements caused by presence of the wanted signal and an interfering signal reaching the transmitter unit via the 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 intermodulation requirement. + +## 6.7.2 Minimum requirements for BS type 1-C + +### 6.7.2.1 Co-location minimum requirements + +For BS type 1-C, the wanted signal and interfering signal centre frequency is specified in table 6.7.2.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 \cdot BW_{\text{Channel}}$ (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.2.1-1. + +**Table 6.7.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, 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. | +| 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 base station are excluded from the requirement, unless the interfering signal positions fall within the frequency range of adjacent downlink operating bands in the same geographical area. In case that none of the interfering signal positions fall completely within the frequency range of the downlink operating band , TS 38.141-1 [5] provides further guidance regarding appropriate test requirements. | | +| NOTE 2: In Japan, NOTE 1 is not applied in Band n77, n78, n79. | | + +### 6.7.2.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.2.2-1. + +**Table 6.7.2.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.2.2-2. + +**Table 6.7.2.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.3 Minimum requirements for BS type 1-H + +### 6.7.3.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.3.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}}$ (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.3.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_{Channel}$ ) with 15 kHz SCS of the band defined in clause 5.3.5. | +| Interfering signal level | Rated total output power per TAB connector ( $P_{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. In case that none of the interfering signal positions fall completely within the frequency range of the downlink operating band , TS 38.141-1 [5] provides further guidance regarding appropriate test requirements. | | +| NOTE 2: In Japan, NOTE 1 is not applied in Band n77, n78, n79. | | + +### 6.7.3.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.3.2-1. + +**Table 6.7.3.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 base station manufacturer (Note 2). | +| Frequency offset between interfering signal and wanted signal | 0 MHz | +| NOTE 1: The interfering signal shall be incoherent with the wanted signal. | | +| NOTE 2: The declared interfering signal power level at each TAB connector is the sum of the co-channel leakage power coupled via the combined RDN and Antenna Array from all the other TAB connectors , but does not comprise power radiated from the Antenna Array and reflected back from the environment. The power at each of the interfering TAB connectors is $P_{rated,c,TABC}$ . | | + +### 6.7.3.3 Additional requirements + +For Band n41 and n90 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.3.3-1. + +**Table 6.7.3.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 | ± 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.3.3-2. + +**Table 6.7.3.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 | ± 2.5 MHz
± 7.5 MHz
± 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 radiated 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 TS 36.104 [13] clause 7. + +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* there is no requirement specified for band n46 and n102. + +### 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 *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 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.2.2-1 for Wide Area BS, in table 7.2.2-2 for Medium Range BS and in table 7.2.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.1 with parameters specified in table 7.2.2-2a for Medium Range BS and in table 7.2.2-3a for Local Area BS, for band n46 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.2-2b for Medium Range BS and in table 7.2.2-3b for Local Area BS, for band n96. + +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-1a for Wide Area BS, in table 7.2.2-2c for Medium Range BS and in table 7.2.2-3c for Local Area BS for band n104. + +**Table 7.2.2-1: NR Wide Area BS reference sensitivity levels** + +| BS channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel | Reference sensitivity power level, P_{REFSENS} (dBm) | +|-------------------------------------------------|----------------------------------|--------------------------------------|--------------------------------------------------------------------------| +| 3 | 15 | G-FR1-A1-7 (Note 1) | -103.6 | +| | | G-FR1-A1-21 (Note 6) | -103.6 | +| 5, 10, 15 | 15 | G-FR1-A1-1 (Note 1) | -101.7 | +| | | G-FR1-A1-10 (Note 3) | -101.7 (Note 2) | +| 10, 15 | 30 | G-FR1-A1-2 (Note 1) | -101.8 | +| 10, 15 | 60 | G-FR1-A1-3 (Note 1) | -98.9 | +| 20, 25, 30, 35, 40, 45, 50 | 15 | G-FR1-A1-4 (Note 1) | -95.3 | +| | | G-FR1-A1-11 (Note 4) | -95.3 (Note 2) | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 (Note 1) | -95.6 | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 (Note 1) | -95.7 | + +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: The requirements apply to BS that supports NB-IoT operation in NR in-band. + +NOTE 3: $P_{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_{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: Void. + +NOTE 6: $P_{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-21 mapped to the 12 NR resource blocks adjacent to the NB-IoT PRB, and for each consecutive application of a single instance of G-FR1-A1-7 mapped to disjoint frequency ranges with a width of 15 resource blocks each. + +**Table 7.2.2-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_{REFSENS} (dBm) (Note 1) | +|-------------------------------------|----------------------------------|--------------------------------------|-----------------------------------------------------------------------------------| +| 20, 30, 40, 50 | 15 | G-FR1-A1-4 (Note 1) | -94.3 | +| 20, 30, 40, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 (Note 1) | -94.6 | +| 20, 30, 40, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 (Note 1) | -94.7 | + +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*. + +**Table 7.2.2-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_{REFSENS} (dBm) | +|-------------------------------------------------|----------------------------------|-----------------------------------------------|--------------------------------------------------------------------------| +| 3 | 15 | G-FR1-A1-7 (Note 1) | -98.6 | +| | | G-FR1-A1-21 (Note 6) | -98.6 | +| 5, 10, 15 | 15 | G-FR1-A1-1 (Note 1) | -96.7 | +| | | G-FR1-A1-10 (Note 3) | -96.7 (Note 2) | +| 10, 15 | 30 | G-FR1-A1-2 (Note 1) | -96.8 | +| 10, 15 | 60 | G-FR1-A1-3 (Note 1) | -93.9 | +| 20, 25, 30, 35, 40, 45, 50 | 15 | G-FR1-A1-4 (Note 1) | -90.3 | +| | | G-FR1-A1-11 (Note 4) | -90.3 (Note 2) | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 (Note 1) | -90.6 | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 (Note 1) | -90.7 | + +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: The requirements apply to BS that supports NB-IoT operation in NR in-band. + +Note 3: $P_{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_{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. + +Note 6: $P_{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-21 mapped to the 12 NR resource blocks adjacent to the NB-IoT PRB, and for each consecutive application of a single instance of G-FR1-A1-7 mapped to disjoint frequency ranges with a width of 15 resource blocks each. + +**Table 7.2.2-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_{\text{REFSENS}} (dBm) | +|-----------------------------------|----------------------------------|--------------------------------------|---------------------------------------------------------------------------------| +| 10 | 15 | G-FR1-A1-12 (Note 2) | -103.0 | +| | 30 | G-FR1-A1-13 (Note 2) | -100.7 | +| | 60 | G-FR1-A1-3 (Note 1) | -93.9 | +| 20 | 15 | G-FR1-A1-14 (Note 2) | -100.1 | +| | 30 | G-FR1-A1-15 (Note 2) | -97.1 | +| | 60 | G-FR1-A1-6 (Note 1) | -90.7 | +| 40 | 15 | G-FR1-A1-16 (Note 2) | -97.0 | +| | 30 | G-FR1-A1-17 (Note 2) | -94.0 | +| | 60 | G-FR1-A1-6 (Note 1) | -90.7 | +| 60 | 30 | G-FR1-A1-18 (Note 2) | -92.4 | +| | 60 | G-FR1-A1-6 (Note 1) | -90.7 | +| 80 | 30 | G-FR1-A1-19 (Note 2) | -91.1 | +| | 60 | G-FR1-A1-6 (Note 1) | -90.7 | + +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.2-2. $P_{\text{REFSENS}}$ is the power level of a single instance of the reference measurement channel. This requirement shall be met for each single interlace of FRC G-FR1-A1-12 and G-FR1-A1-19, except for one instance that might overlap one other instance to cover the full *BS channel bandwidth*. + +**Table 7.2.2-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_{\text{REFSENS}} (dBm) | +|-----------------------------------|----------------------------------|--------------------------------------|---------------------------------------------------------------------------------| +| 20 | 15 | G-FR1-A1-14 (Note 2) | -99.1 | +| | 30 | G-FR1-A1-15 (Note 2) | -96.1 | +| | 60 | G-FR1-A1-6 (Note 1) | -89.7 | +| 40 | 15 | G-FR1-A1-16 (Note 2) | -96.0 | +| | 30 | G-FR1-A1-17 (Note 2) | -93.0 | +| | 60 | G-FR1-A1-6 (Note 1) | -89.7 | +| 60 | 30 | G-FR1-A1-18 (Note 2) | -91.4 | +| | 60 | G-FR1-A1-6 (Note 1) | -89.7 | +| 80 | 30 | G-FR1-A1-19 (Note 2) | -90.1 | +| | 60 | G-FR1-A1-6 (Note 1) | -89.7 | + +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.2-2. + +**Table 7.2.2-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) | -89.3 | +| 20, 30, 40, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 (Note 1) | -89.6 | +| 20, 30, 40, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 (Note 1) | -89.7 | + +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.2-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) | +|-------------------------------------------------|----------------------------------|-----------------------------------------------|---------------------------------------------------------------------------------| +| 3 | 15 | G-FR1-A1-7 (Note 1) | -95.6 | +| | | G-FR1-A1-21 (Note 6) | -95.6 | +| 5, 10, 15 | 15 | G-FR1-A1-1 (Note 1) | -93.7 | +| | | G-FR1-A1-10 (Note 3) | -93.7 (Note 2) | +| 10, 15 | 30 | G-FR1-A1-2 (Note 1) | -93.8 | +| 10, 15 | 60 | G-FR1-A1-3 (Note 1) | -90.9 | +| 20, 25, 30, 35, 40, 45, 50 | 15 | G-FR1-A1-4 (Note 1) | -87.3 | +| | | G-FR1-A1-11 (Note 4) | -87.3 (Note 2) | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 (Note 1) | -87.6 | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 (Note 1) | -87.7 | + +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. + +Note 6: $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-21 mapped to the 12 NR resource blocks adjacent to the NB-IoT PRB, and for each consecutive application of a single instance of G-FR1-A1-7 mapped to disjoint frequency ranges with a width of 15 resource blocks each. + +**Table 7.2.2-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_{REFSENS} (dBm) | +|-----------------------------------|----------------------------------|--------------------------------------|--------------------------------------------------------------------------| +| 10 | 15 | G-FR1-A1-12 (Note 2) | -100.0 | +| | 30 | G-FR1-A1-13 (Note 2) | -97.7 | +| | 60 | G-FR1-A1-3 (Note 1) | -90.9 | +| 20 | 15 | G-FR1-A1-14 (Note 2) | -97.1 | +| | 30 | G-FR1-A1-15 (Note 2) | -94.1 | +| | 60 | G-FR1-A1-6 (Note 1) | -87.7 | +| 40 | 15 | G-FR1-A1-16 (Note 2) | -94.0 | +| | 30 | G-FR1-A1-17 (Note 2) | -91.0 | +| | 60 | G-FR1-A1-6 (Note 1) | -87.7 | +| 60 | 30 | G-FR1-A1-18 (Note 2) | -89.4 | +| | 60 | G-FR1-A1-6 (Note 1) | -87.7 | +| 80 | 30 | G-FR1-A1-19 (Note 2) | -88.1 | +| | 60 | G-FR1-A1-6 (Note 1) | -87.7 | + +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.2-3. + +**Table 7.2.2-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_{REFSENS} (dBm) | +|-----------------------------------|----------------------------------|--------------------------------------|--------------------------------------------------------------------------| +| 20 | 15 | G-FR1-A1-14 (Note 2) | -96.1 | +| | 30 | G-FR1-A1-15 (Note 2) | -93.1 | +| | 60 | G-FR1-A1-6 (Note 1) | -86.7 | +| 40 | 15 | G-FR1-A1-16 (Note 2) | -93.0 | +| | 30 | G-FR1-A1-17 (Note 2) | -90.0 | +| | 60 | G-FR1-A1-6 (Note 1) | -86.7 | +| 60 | 30 | G-FR1-A1-18 (Note 2) | -88.4 | +| | 60 | G-FR1-A1-6 (Note 1) | -86.7 | +| 80 | 30 | G-FR1-A1-19 (Note 2) | -87.1 | +| | 60 | G-FR1-A1-6 (Note 1) | -86.7 | + +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.2-3. + +**Table 7.2.2-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) | -86.3 | +| 20, 30, 40, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 (Note 1) | -86.6 | +| 20, 30, 40, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 (Note 1) | -86.7 | + +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 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 *antenna connector* for BS type 1-C or *TAB connector* for BS type 1-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 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.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.2-2b for Medium Range BS and in table 7.3.2-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.2-2c for Medium Range BS and in table 7.3.2-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.2-1b for Wide Area BS, in table 7.3.2-2d for Medium Range BS and in table 7.3.2-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.104 [13] with parameters specified in table 7.3.2-1a for Wide Area BS, in table 7.3.2-2a for Medium Range BS and in table 7.3.2-3a for Local Area BS. + +**Table 7.3.2-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 | +|-----------------------------------|---------------------------------|--------------------------------------|---------------------------------------|------------------------------------------------------------------|-----------------------------------| +| 3 | 15 | G-FR1-A2-15 | -73.6 | -84.7 | AWGN | +| 5 | 15 | G-FR1-A2-1 | -70.7 | -82.5 | AWGN | +| | 30 | G-FR1-A2-2 | -71.4 | | | +| 10 | 15 | G-FR1-A2-1 | -70.7 | -79.3 | AWGN | +| | 30 | G-FR1-A2-2 | -71.4 | | | +| | 60 | G-FR1-A2-3 | -68.4 | | | +| 15 | 15 | G-FR1-A2-1 | -70.7 | -77.5 | AWGN | +| | 30 | G-FR1-A2-2 | -71.4 | | | +| | 60 | G-FR1-A2-3 | -68.4 | | | +| 20 | 15 | G-FR1-A2-4 | -64.5 | -76.2 | AWGN | +| | 30 | G-FR1-A2-5 | -64.5 | | | +| | 60 | G-FR1-A2-6 | -64.8 | | | +| 25 | 15 | G-FR1-A2-4 | -64.5 | -75.2 | AWGN | +| | 30 | G-FR1-A2-5 | -64.5 | | | +| | 60 | G-FR1-A2-6 | -64.8 | | | +| 30 | 15 | G-FR1-A2-4 | -64.5 | -74.4 | AWGN | +| | 30 | G-FR1-A2-5 | -64.5 | | | +| | 60 | G-FR1-A2-6 | -64.8 | | | +| 35 | 15 | G-FR1-A2-4 | -64.5 | -73.7 | AWGN | +| | 30 | G-FR1-A2-5 | -64.5 | | | +| | 60 | G-FR1-A2-6 | -64.8 | | | +| 40 | 15 | G-FR1-A2-4 | -64.5 | -73.1 | AWGN | +| | 30 | G-FR1-A2-5 | -64.5 | | | +| | 60 | G-FR1-A2-6 | -64.8 | | | +| 45 | 15 | G-FR1-A2-4 | -64.5 | -72.6 | AWGN | +| | 30 | G-FR1-A2-5 | -64.5 | | | +| | 60 | G-FR1-A2-6 | -64.8 | | | +| 50 | 15 | G-FR1-A2-4 | -64.5 | -72.1 | AWGN | +| | 30 | G-FR1-A2-5 | -64.5 | | | +| | 60 | G-FR1-A2-6 | -64.8 | | | +| 60 | 30 | G-FR1-A2-5 | -64.5 | -71.3 | AWGN | +| | 60 | G-FR1-A2-6 | -64.8 | | | +| 70 | 30 | G-FR1-A2-5 | -64.5 | -70.7 | AWGN | +| | 60 | G-FR1-A2-6 | -64.8 | | | +| 80 | 30 | G-FR1-A2-5 | -64.5 | -70.1 | AWGN | +| | 60 | G-FR1-A2-6 | -64.8 | | | +| 90 | 30 | G-FR1-A2-5 | -64.5 | -69.5 | AWGN | +| | 60 | G-FR1-A2-6 | -64.8 | | | +| 100 | 30 | G-FR1-A2-5 | -64.5 | -69.1 | AWGN | +| | 60 | G-FR1-A2-6 | -64.8 | | | + +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.2-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) / BW Config | Type of interfering signal | +|----------------------------|-------------------------------------------|--------------------------------|------------------------------------------------------------|----------------------------| +| 3 | FRC A15-1 in Annex A.15 in TS 36.104 [13] | -99.7 | -84.7 | AWGN | +| 5 | | | -82.5 | | +| 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 | | +| 3 | FRC A15-2 in Annex A.15 in TS 36.104 [13] | -105.6 | -84.7 | AWGN | +| 5 | | | -82.5 | | +| 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.2-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) / BW Config | Type of interfering signal | +|----------------------------|--------------------------|-------------------------------|--------------------------------|------------------------------------------------------------|----------------------------| +| 20 | 15 | G-FR1-A2-4 | -63.5 | -75.2 | AWGN | +| | 30 | G-FR1-A2-5 | -63.5 | | | +| | 60 | G-FR1-A2-6 | -63.8 | | | +| 30 | 15 | G-FR1-A2-4 | -63.5 | -73.4 | AWGN | +| | 30 | G-FR1-A2-5 | -63.5 | | | +| | 60 | G-FR1-A2-6 | -63.8 | | | +| 40 | 15 | G-FR1-A2-4 | -63.5 | -72.1 | AWGN | +| | 30 | G-FR1-A2-5 | -63.5 | | | +| | 60 | G-FR1-A2-6 | -63.8 | | | +| 50 | 15 | G-FR1-A2-4 | -63.5 | -71.1 | AWGN | +| | 30 | G-FR1-A2-5 | -63.5 | | | +| | 60 | G-FR1-A2-6 | -63.8 | | | +| 60 | 30 | G-FR1-A2-5 | -63.5 | -70.3 | AWGN | +| | 60 | G-FR1-A2-6 | -63.8 | | | +| 70 | 30 | G-FR1-A2-5 | -63.5 | -69.7 | AWGN | +| | 60 | G-FR1-A2-6 | -63.8 | | | +| 80 | 30 | G-FR1-A2-5 | -63.5 | -69.1 | AWGN | +| | 60 | G-FR1-A2-6 | -63.8 | | | +| 90 | 30 | G-FR1-A2-5 | -63.5 | -68.5 | AWGN | +| | 60 | G-FR1-A2-6 | -63.8 | | | +| 100 | 30 | G-FR1-A2-5 | -63.5 | -68.1 | AWGN | +| | 60 | G-FR1-A2-6 | -63.8 | | | + +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.2-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 | +|-----------------------------------|---------------------------------|-----------------------------------------------|---------------------------------------|------------------------------------------------------------------|-----------------------------------| +| 3 | 15 | G-FR1-A2-15 | -68.6 | -79.7 | AWGN | +| 5 | 15 | G-FR1-A2-1 | -65.7 | -77.5 | AWGN | +| | 30 | G-FR1-A2-2 | -66.4 | | | +| 10 | 15 | G-FR1-A2-1 | -65.7 | -74.3 | AWGN | +| | 30 | G-FR1-A2-2 | -66.4 | | | +| | 60 | G-FR1-A2-3 | -63.4 | | | +| 15 | 15 | G-FR1-A2-1 | -65.7 | -72.5 | AWGN | +| | 30 | G-FR1-A2-2 | -66.4 | | | +| | 60 | G-FR1-A2-3 | -63.4 | | | +| 20 | 15 | G-FR1-A2-4 | -59.5 | -71.2 | AWGN | +| | 30 | G-FR1-A2-5 | -59.5 | | | +| | 60 | G-FR1-A2-6 | -59.8 | | | +| 25 | 15 | G-FR1-A2-4 | -59.5 | -70.2 | AWGN | +| | 30 | G-FR1-A2-5 | -59.5 | | | +| | 60 | G-FR1-A2-6 | -59.8 | | | +| 30 | 15 | G-FR1-A2-4 | -59.5 | -69.4 | AWGN | +| | 30 | G-FR1-A2-5 | -59.5 | | | +| | 60 | G-FR1-A2-6 | -59.8 | | | +| 35 | 15 | G-FR1-A2-4 | -59.5 | -68.7 | AWGN | +| | 30 | G-FR1-A2-5 | -59.5 | | | +| | 60 | G-FR1-A2-6 | -59.8 | | | +| 40 | 15 | G-FR1-A2-4 | -59.5 | -68.1 | AWGN | +| | 30 | G-FR1-A2-5 | -59.5 | | | +| | 60 | G-FR1-A2-6 | -59.8 | | | +| 45 | 15 | G-FR1-A2-4 | -59.5 | -67.6 | AWGN | +| | 30 | G-FR1-A2-5 | -59.5 | | | +| | 60 | G-FR1-A2-6 | -59.8 | | | +| 50 | 15 | G-FR1-A2-4 | -59.5 | -67.1 | AWGN | +| | 30 | G-FR1-A2-5 | -59.5 | | | +| | 60 | G-FR1-A2-6 | -59.8 | | | +| 60 | 30 | G-FR1-A2-5 | -59.5 | -66.3 | AWGN | +| | 60 | G-FR1-A2-6 | -59.8 | | | +| 70 | 30 | G-FR1-A2-5 | -59.5 | -65.7 | AWGN | +| | 60 | G-FR1-A2-6 | -59.8 | | | +| 80 | 30 | G-FR1-A2-5 | -59.5 | -65.1 | AWGN | +| | 60 | G-FR1-A2-6 | -59.8 | | | +| 90 | 30 | G-FR1-A2-5 | -59.5 | -64.5 | AWGN | +| | 60 | G-FR1-A2-6 | -59.8 | | | +| 100 | 30 | G-FR1-A2-5 | -59.5 | -64.1 | AWGN | +| | 60 | G-FR1-A2-6 | -59.8 | | | + +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.2-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 | +|-----------------------------------|-------------------------------------------|---------------------------------------|------------------------------------------------------------------|-----------------------------------| +| 3 | FRC A15-1 in Annex A.15 in TS 36.104 [13] | -94.7 | -79.7 | AWGN | +| 5 | | | -77.5 | | +| 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 | | +| 3 | FRC A15-2 in Annex A.15 in TS 36.104 [13] | -100.6 | -79.7 | AWGN | +| 5 | | | -77.5 | | +| 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.2-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.8 | -74.3 | AWGN | +| | 30 | G-FR1-A2-8 (Note 2) | -70.6 | | | +| | 60 | G-FR1-A2-3 (Note 1, 3) | -63.4 | | | +| 20 | 15 | G-FR1-A2-9 (Note 2) | -69.8 | -71.2 | AWGN | +| | 30 | G-FR1-A2-10 (Note 2) | -66.8 | | | +| | 60 | G-FR1-A2-6 (Note 1, 3) | -59.8 | | | +| 40 | 15 | G-FR1-A2-11 (Note 2) | -66.7 | -68.1 | AWGN | +| | 30 | G-FR1-A2-12 (Note 2) | -63.7 | | | +| | 60 | G-FR1-A2-6 (Note 1, 3) | -59.8 | | | +| 60 | 30 | G-FR1-A2-13 (Note 2) | -61.9 | -66.3 | AWGN | +| | 60 | G-FR1-A2-6 (Note 1, 3) | -59.8 | | | +| 80 | 30 | G-FR1-A2-14 (Note 2) | -60.7 | -65.1 | AWGN | +| | 60 | G-FR1-A2-6 (Note 1, 3) | -59.8 | | | + +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.2-2. + +**Table 7.3.2-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.8 | -70.2 | AWGN | +| | 30 | G-FR1-A2-10 (Note 2) | -65.8 | | | +| | 60 | G-FR1-A2-6 (Note 1, 3) | -58.8 | | | +| 40 | 15 | G-FR1-A2-11 (Note 2) | -65.7 | -67.1 | AWGN | +| | 30 | G-FR1-A2-12 (Note 2) | -62.7 | | | +| | 60 | G-FR1-A2-6 (Note 1, 3) | -58.8 | | | +| 60 | 30 | G-FR1-A2-13 (Note 2) | -60.9 | -65.3 | AWGN | +| | 60 | G-FR1-A2-6 (Note 1, 3) | -58.8 | | | +| 80 | 30 | G-FR1-A2-14 (Note 2) | -59.7 | -64.1 | AWGN | +| | 60 | G-FR1-A2-6 (Note 1, 3) | -58.8 | | | + +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.2-2. + +**Table 7.3.2-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) / BW config | Type of interfering signal | +|----------------------------|--------------------------|----------------------------------------|--------------------------------|------------------------------------------------------------|----------------------------| +| 20 | 15 | G-FR1-A2-4 | -58.5 | -70.2 | AWGN | +| | 30 | G-FR1-A2-5 | -58.5 | | | +| | 60 | G-FR1-A2-6 | -58.8 | | | +| 30 | 15 | G-FR1-A2-4 | -58.5 | -68.4 | AWGN | +| | 30 | G-FR1-A2-5 | -58.5 | | | +| | 60 | G-FR1-A2-6 | -58.8 | | | +| 40 | 15 | G-FR1-A2-4 | -58.5 | -67.1 | AWGN | +| | 30 | G-FR1-A2-5 | -58.5 | | | +| | 60 | G-FR1-A2-6 | -58.8 | | | +| 50 | 15 | G-FR1-A2-4 | -58.5 | -66.1 | AWGN | +| | 30 | G-FR1-A2-5 | -58.5 | | | +| | 60 | G-FR1-A2-6 | -58.8 | | | +| 60 | 30 | G-FR1-A2-5 | -58.5 | -65.3 | AWGN | +| | 60 | G-FR1-A2-6 | -58.8 | | | +| 70 | 30 | G-FR1-A2-5 | -58.5 | -64.7 | AWGN | +| | 60 | G-FR1-A2-6 | -58.8 | | | +| 80 | 30 | G-FR1-A2-5 | -58.5 | -64.1 | AWGN | +| | 60 | G-FR1-A2-6 | -58.8 | | | +| 90 | 30 | G-FR1-A2-5 | -58.5 | -63.5 | AWGN | +| | 60 | G-FR1-A2-6 | -58.8 | | | +| 100 | 30 | G-FR1-A2-5 | -58.5 | -63.1 | AWGN | +| | 60 | G-FR1-A2-6 | -58.8 | | | + +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.2-3: Local Area BS dynamic range** + +| BS channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) / BWConfig | Type of interfering signal | +|-----------------------------------|---------------------------------|--------------------------------------|---------------------------------------|------------------------------------------------------------------|-----------------------------------| +| 3 | 15 | G-FR1-A2-15 | -65.6 | -76.7 | AWGN | +| 5 | 15 | G-FR1-A2-1 | -62.7 | -74.5 | AWGN | +| | 30 | G-FR1-A2-2 | -63.4 | | | +| 10 | 15 | G-FR1-A2-1 | -62.7 | -71.3 | AWGN | +| | 30 | G-FR1-A2-2 | -63.4 | | | +| | 60 | G-FR1-A2-3 | -60.4 | | | +| 15 | 15 | G-FR1-A2-1 | -62.7 | -69.5 | AWGN | +| | 30 | G-FR1-A2-2 | -63.4 | | | +| | 60 | G-FR1-A2-3 | -60.4 | | | +| 20 | 15 | G-FR1-A2-4 | -56.5 | -68.2 | AWGN | +| | 30 | G-FR1-A2-5 | -56.5 | | | +| | 60 | G-FR1-A2-6 | -56.8 | | | +| 25 | 15 | G-FR1-A2-4 | -56.5 | -67.2 | AWGN | +| | 30 | G-FR1-A2-5 | -56.5 | | | +| | 60 | G-FR1-A2-6 | -56.8 | | | +| 30 | 15 | G-FR1-A2-4 | -56.5 | -66.4 | AWGN | +| | 30 | G-FR1-A2-5 | -56.5 | | | +| | 60 | G-FR1-A2-6 | -56.8 | | | +| 35 | 15 | G-FR1-A2-4 | -56.5 | -65.7 | AWGN | +| | 30 | G-FR1-A2-5 | -56.5 | | | +| | 60 | G-FR1-A2-6 | -56.8 | | | +| 40 | 15 | G-FR1-A2-4 | -56.5 | -65.1 | AWGN | +| | 30 | G-FR1-A2-5 | -56.5 | | | +| | 60 | G-FR1-A2-6 | -56.8 | | | +| 45 | 15 | G-FR1-A2-4 | -56.5 | -64.6 | AWGN | +| | 30 | G-FR1-A2-5 | -56.5 | | | +| | 60 | G-FR1-A2-6 | -56.8 | | | +| 50 | 15 | G-FR1-A2-4 | -56.5 | -64.1 | AWGN | +| | 30 | G-FR1-A2-5 | -56.5 | | | +| | 60 | G-FR1-A2-6 | -56.8 | | | +| 60 | 30 | G-FR1-A2-5 | -56.5 | -63.3 | AWGN | +| | 60 | G-FR1-A2-6 | -56.8 | | | +| 70 | 30 | G-FR1-A2-5 | -56.5 | -62.7 | AWGN | +| | 60 | G-FR1-A2-6 | -56.8 | | | +| 80 | 30 | G-FR1-A2-5 | -56.5 | -62.1 | AWGN | +| | 60 | G-FR1-A2-6 | -56.8 | | | +| 90 | 30 | G-FR1-A2-5 | -56.5 | -61.5 | AWGN | +| | 60 | G-FR1-A2-6 | -56.8 | | | +| 100 | 30 | G-FR1-A2-5 | -56.5 | -61.1 | AWGN | +| | 60 | G-FR1-A2-6 | -56.8 | | | + +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.2-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 | +|-----------------------------------|-------------------------------------------|---------------------------------------|------------------------------------------------------------------|-----------------------------------| +| 3 | FRC A15-1 in Annex A.15 in TS 36.104 [13] | -91.7 | -76.7 | AWGN | +| 5 | | | -74.5 | | +| 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 | | +| 3 | FRC A15-2 in Annex A.15 in TS 36.104 [13] | -97.6 | -76.7 | AWGN | +| 5 | | | -74.5 | | +| 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.2-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.8 | -71.3 | AWGN | +| | 30 | G-FR1-A2-8 (Note 2) | -67.6 | | | +| | 60 | G-FR1-A2-3 (Note 1, 3) | -60.4 | | | +| 20 | 15 | G-FR1-A2-9 (Note 2) | -66.8 | -68.2 | AWGN | +| | 30 | G-FR1-A2-10 (Note 2) | -63.8 | | | +| | 60 | G-FR1-A2-6 (Note 1, 3) | -56.8 | | | +| 40 | 15 | G-FR1-A2-11 (Note 2) | -63.7 | -65.1 | AWGN | +| | 30 | G-FR1-A2-12 | -60.7 | | | +| | 60 | G-FR1-A2-6 (Note 1, 3) | -56.8 | | | +| 60 | 30 | G-FR1-A2-13 (Note 2) | -58.9 | -63.3 | AWGN | +| | 60 | G-FR1-A2-6 (Note 1, 3) | -56.8 | | | +| 80 | 30 | G-FR1-A2-14 (Note 2) | -57.7 | -62.1 | AWGN | +| | 60 | G-FR1-A2-6 (Note 1, 3) | -56.8 | | | + +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.2-3. + +**Table 7.3.2-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.8 | -67.2 | AWGN | +| | 30 | G-FR1-A2-10 (Note 2) | -62.8 | | | +| | 60 | G-FR1-A2-6 (Note 1, 3) | -55.8 | | | +| 40 | 15 | G-FR1-A2-11 (Note 2) | -62.7 | -64.1 | AWGN | +| | 30 | G-FR1-A2-12 (Note 2) | -59.7 | | | +| | 60 | G-FR1-A2-6 (Note 1, 3) | -55.8 | | | +| 60 | 30 | G-FR1-A2-13 (Note 2) | -57.9 | -62.3 | AWGN | +| | 60 | G-FR1-A2-6 (Note 1, 3) | -55.8 | | | +| 80 | 30 | G-FR1-A2-14 (Note 2) | -56.7 | -61.1 | AWGN | +| | 60 | G-FR1-A2-6 (Note 1, 3) | -55.8 | | | + +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.2-3. + +**Table 7.3.2-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) / $BW_{Config}$ | Type of interfering signal | +|----------------------------|--------------------------|-------------------------------|--------------------------------|-----------------------------------------------------|----------------------------| +| 20 | 15 | G-FR1-A2-4 | -55.5 | -67.2 | AWGN | +| | 30 | G-FR1-A2-5 | -55.5 | | | +| | 60 | G-FR1-A2-6 | -55.8 | | | +| 30 | 15 | G-FR1-A2-4 | -55.5 | -65.4 | AWGN | +| | 30 | G-FR1-A2-5 | -55.5 | | | +| | 60 | G-FR1-A2-6 | -55.8 | | | +| 40 | 15 | G-FR1-A2-4 | -55.5 | -64.1 | AWGN | +| | 30 | G-FR1-A2-5 | -55.5 | | | +| | 60 | G-FR1-A2-6 | -55.8 | | | +| 50 | 15 | G-FR1-A2-4 | -55.5 | -63.1 | AWGN | +| | 30 | G-FR1-A2-5 | -55.5 | | | +| | 60 | G-FR1-A2-6 | -55.8 | | | +| 60 | 30 | G-FR1-A2-5 | -55.5 | -62.3 | AWGN | +| | 60 | G-FR1-A2-6 | -55.8 | | | +| 70 | 30 | G-FR1-A2-5 | -55.5 | -61.7 | AWGN | +| | 60 | G-FR1-A2-6 | -55.8 | | | +| 80 | 30 | G-FR1-A2-5 | -55.5 | -61.1 | AWGN | +| | 60 | G-FR1-A2-6 | -55.8 | | | +| 90 | 30 | G-FR1-A2-5 | -55.5 | -60.5 | AWGN | +| | 60 | G-FR1-A2-6 | -55.8 | | | +| 100 | 30 | G-FR1-A2-5 | -55.5 | -60.1 | AWGN | +| | 60 | G-FR1-A2-6 | -55.8 | | | + +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 General + +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 1-C or *TAB connector* for BS type 1-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 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. + +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.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, 7.2.2-2 and 7.2.2-3 for each BS 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 D. + +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.2-1a and the frequency offset between the wanted and interfering signal in table 7.4.1.2-2a for ACS. The reference measurement channel for the wanted signal is + +identified in table 7.2.2-2a and 7.2.2-3a 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.2-1b 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 7.2.2-1a, 7.2.2-2c, 7.2.2-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.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 NB-IoT wanted signal is identified in clause 7.2.1 of TS 36.104 [13]. The characteristics of the interfering signal is further specified in annex D. + +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.2-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.2-2. The interfering signal offset is defined relative to the *Base Station RF Bandwidth* edges inside the *Inter RF Bandwidth gap*. + +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.1.2-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) | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|-----------------------------------------------------------------| +| 3 | P_{REFSENS} + 8 dB | | +| 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100
(Note 1) | $P_{REFSENS} + 6$ 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_{REFSENS}$ depends on the RAT. For NR, $P_{REFSENS}$ depends also on the BS channel bandwidth as specified in tables 7.2.2-1, 7.2.2-2, 7.2.2-3. 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 [13]. | | | + +**Table 7.4.1.2-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. | | | +| NOTE 3: Void. | | | + +**Table 7.4.1.2-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_{\text{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_{\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-1a, 7.2.2-2c, 7.2.2-3c. | | | + +**Table 7.4.1.2-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 | +|-------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------| +| 3 | $\pm 1.5075$ | 3 MHz DFT-s-OFDM NR signal
15 kHz SCS, 15 RBs | +| 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$ | | +| 30 | $\pm 9.4725$ | 20 MHz DFT-s-OFDM NR signal
15 kHz SCS, 100 RBs | +| 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.2-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 | $\pm 9.4675$ | 20 MHz DFT-s-OFDM NR signal
15 kHz SCS, 100 RBs | +| 20 | $\pm 9.4625$ | | +| 40 | $\pm 9.4675$ | | +| 60 | $\pm 9.4725$ | | +| 80 | $\pm 9.4625$ | | + +#### 7.4.1.3 Void + +#### 7.4.1.4 Void + +### 7.4.2 In-band blocking + +#### 7.4.2.1 General + +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 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, 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.2-1, 7.4.2.2-2 and 7.4.2.2-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.2 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 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.2-1, 7.4.2.2-2a and 7.4.2.2-3 for general blocking and narrowband blocking requirements. The reference measurement channel for the NB-IoT wanted signal is identified in clause 7.2.1 of TS 36.104 [13]. The characteristics of the interfering signal is further specified in annex D. + +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*. + +The in-band blocking requirement shall apply from $F_{UL,low} - \Delta f_{OOB}$ to $F_{UL,high} + \Delta f_{OOB}$ , excluding the downlink frequency range of the FDD *operating band*. The $\Delta f_{OOB}$ for *BS type 1-C* and *BS type 1-H* is defined in table 7.4.2.2-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.2-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 | + +For band n46, n96 and n102, $\Delta f_{OOB}$ is defined in table 7.4.2.2-0a. + +**Table 7.4.2.2-0a: $\Delta f_{OOB}$ offset for NR operating bands for band n46, n96 and n102** + +| 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.2-0b. + +**Table 7.4.2.2-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 tables 7.4.2.2-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 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.4.2.2-1. + +For a BS operating in *non-contiguous spectrum* within any *operating band*, the narrowband blocking requirement shall apply 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.2-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 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.2.2-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.2-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 | +|-------------------------------------------------------------------|-----------------------------------------|-----------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------| +| 3 | $P_{\text{REFSENS}} + x$ dB | Wide Area BS: -43
Medium Range BS: -38
Local Area BS: -35 | $\pm 4.5$ | 3 MHz DFT-s-OFDM NR signal
15 kHz SCS, 15 RBs | +| 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 tables 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, and 7.2.2-3c. 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 [13]. + +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.2-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. | | | | | + +**Table 7.4.2.2-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 1: $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. | | | | | + +**Table 7.4.2.2-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) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|-----------------------------------------------------------------| +| 3, 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 tables 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.2-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) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------|--------------------------------------------------------| +| 3, 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 [13].
NOTE 2: “x” is equal to 11 in case of 3 MHz channel bandwidth, equal to 8 in case of 5 MHz channel bandwidth and equal to 6 otherwise. | | | + +**Table 7.4.2.2-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 | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------| +| 3 | $\pm(255+m*180)$ ,
$m=0, 1, 2, 3, 4, 7, 10, 13$ | 3 MHz DFT-s-OFDM NR signal, 15 kHz SCS, 1 RB | +| 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.3 Void + +7.4.2.4 Void + +#### 7.4.2.5 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 and 7.4.2.5-2, the throughput shall be $\geq 95$ % of the maximum throughput of the reference measurement channel. + +**Table 7.4.2.5-1: Additional narrowband blocking requirement for RMR BS operating in n100** + +| BS channel bandwidth of the lowest carrier received (MHz) | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | +|-----------------------------------------------------------|--------------------------------|-------------------------------------| +| 3, 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. +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 [23]. + +**Table 7.4.2.5-2: Interferer frequency for additional narrowband blocking requirement for RMR BS operating in n100** + +| BS channel bandwidth of the lowest carrier received (MHz) | Interfering RB centre frequency (Note 2) | Type of interfering signal | +|-----------------------------------------------------------|---------------------------------------------------------------|----------------------------------------------| +| 3 | 874.4 MHz - (255 kHz + m*180), m=0, 1, 2, 3, 4, 7, 10, 13 | 3 MHz DFT-s-OFDM NR signal, 15 kHz SCS, 1 RB | +| 5 | 874.4 MHz - (350 kHz + m*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 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 antenna connector for BS type I-C or TAB connector for BS type I-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 for BS type 1-C and BS type 1-H + +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.2-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.2-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.2-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.2-1. + +The reference measurement channel for the wanted signal is identified in clause 7.2.2 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 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.2-1. The reference measurement channel for the NB-IoT wanted signal is identified in clause 7.2.1 of TS 36.104 [13]. + +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 BS type 1-C and BS type 1-H is defined in table 7.4.2.2-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 multi-band connector, the requirement in the out-of-band blocking frequency ranges apply for each operating band, with the exception that the in-band blocking frequency ranges of all supported operating bands according to clause 7.4.2.2 shall be excluded from the out-of-band blocking requirement. + +**Table 7.5.2-1: Out-of-band blocking performance requirement for NR** + +| Wanted Signal mean power (dBm) | Interfering Signal mean power (dBm) | Type of Interfering Signal | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|----------------------------| +| $P_{REFSENS} + 6$ dB (Note) | -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 Table 7.2.2-1, 7.2.2-2, and 7.2.2-3. For band n104, P_{REFSENS} depends on the BS channel bandwidth as specified in tables 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 [13].

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.

NOTE 3: Void

| | | + +**Table 7.5.2-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. + +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. + +### 7.5.3 Co-location minimum requirements for BS type 1-C and BS type 1-H + +This additional blocking requirement may be applied for the protection of NR BS receivers when GSM, CDMA, UTRA, E-UTRA or NR BS operating in a different frequency band are co-located with a NR BS. The requirement is applicable to all BS 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 type 1-C antenna connector or BS type 1-H TAB connector input using the parameters in table 7.5.3-1 for all the BS classes. The reference measurement channel for the wanted signal is identified in tables 7.2.2-1, 7.2.2-2 and 7.2.2-3 for each BS channel bandwidth and further specified in annex A.1. + +The 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.3-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 (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_{REFSENS} + 6\text{dB}$ (Note 1) | +16 | +8 | x (Note 2) | CW carrier | + +NOTE 1: $P_{REFSENS}$ depends on the BS channel bandwidth as specified in Table 7.2.2-1, 7.2.2-2, and 7.2.2-3. + +NOTE 2: $x = -7\text{ dBm}$ for NR BS co-located with Pico GSM850 or Pico CDMA850 + $x = -4\text{ dBm}$ for NR BS co-located with Pico DCS1800 or Pico PCS1900 + $x = -6\text{ 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_{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.4 Void + +## 7.5.5 Additional out-of-band blocking requirements for the use of RMR bands + +For the additional out-of-band blocking requirements, the interfering signal differs from the one used for the general out-of-band blocking requirement. + +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. The reference measurement channel for the wanted signal is identified in clause 7.2.2 for each *BS channel bandwidth* and further specified in annex A.1. + +The following requirement may apply to BS operating in band n101 in certain regions. + +**Table 7.5.5-1: Additional out-of-band blocking requirement for RMR BS operating in n101** + +| BS channel bandwidth of the lowest/highest carrier received (MHz) | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | Centre frequency of interfering signal (MHz) | Type of interfering signal | +|-------------------------------------------------------------------|-------------------------------------|-------------------------------------|----------------------------------------------|----------------------------| +| 5, 10 | $P_{\text{REFSENS}} + 3 \text{ dB}$ | Wide Area BS: -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. + +## 7.6 Receiver spurious emissions + +### 7.6.1 General + +The receiver spurious emissions power is the power of emissions generated or amplified in a receiver unit that appear at the *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*. 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_{\text{RXU,counted}}$ ) for *BS type 1-H* is calculated as follows: + +$$N_{\text{RXU,counted}} = \min(N_{\text{RXU,active}}, 8 \times N_{\text{cells}})$$ + +$N_{\text{RXU,countedpercell}}$ is used for scaling of *basic limits* and is derived as $N_{\text{RXU,countedpercell}} = N_{\text{RXU,counted}} / N_{\text{cells}}$ , where $N_{\text{cells}}$ is defined in clause 6.1. + +NOTE: $N_{\text{RXU,active}}$ is the number of actually active receiver units and is independent to the declaration of $N_{\text{cells}}$ . + +### 7.6.2 Basic limits + +The receiver spurious emissions *basic limits* are provided in table 7.6.2-1. + +**Table 7.6.2-1: General BS 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 5 | +| 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: 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_{\text{OBUE}}$ below the lowest frequency of the BS transmitter operating band to $\Delta f_{\text{OBUE}}$ above the highest frequency of the BS transmitter operating band may be excluded from the requirement. $\Delta f_{\text{OBUE}}$ is defined in clause 6.6.1. For multi-band connectors , the exclusion applies for all supported operating bands . | | | | +| NOTE 5: Applies for Band for which the upper frequency edge of the UL operating band is greater than 5.2 GHz. | | | | + +### 7.6.3 Minimum requirement for 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.2-1. + +For Band n41 and n90 operation in Japan, the sum of RX spurious emissions requirements over all *antenna connectors* for BS type 1-C shall not exceed *basic limits* specified in table 7.6.2-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.4 Minimum requirement for 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.2-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_{\text{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 General + +Third and higher order mixing of the two interfering RF signals can produce an interfering signal in the band of the desired channel. Intermodulation response rejection is a measure of the capability of the receiver 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 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, 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.2-1 and 7.7.2-2 for intermodulation performance in any operating band except for band n46, n96 and n102, and 7.7.2-2a for band n46, n96 and n102 and in tables 7.7.2-3, and 7.7.2-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.2-1, 7.2.2-2 and 7.2.2-3 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 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.2-1 and 7.7.2-2 for intermodulation performance and in tables 7.7.2-3, and 7.7.2-4 for narrowband intermodulation performance. The reference measurement channel for the NB-IoT wanted signal is identified in clause 7.2.1 of TS 36.104 [13]. The characteristics of the interfering signal is further specified in annex D. + +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 shall 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 shall apply 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.2-2 or 7.7.2-4. The interfering signal offset is defined relative to the *sub-block edges* inside the *sub-block gap*. + +For a *multi-band connector*, 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 *Base Station RF Bandwidth edge*. + +For a *multi-band connector*, 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.7.2-2 and 7.7.2-4. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap*. + +**Table 7.7.2-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\text{ dB}$ | -52 | See Table 7.7.2-2 | +| Medium Range BS | $P_{\text{REFSENS}} + 6\text{ dB}$ | -47 | | +| Local Area BS | $P_{\text{REFSENS}} + 6\text{ dB}$ | -44 | | +| NOTE 1: $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. 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 [13]. | | | | + +**Table 7.7.2-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.2-2a | +| Local Area BS | $P_{\text{REFSENS}} + 6$ dB | -44 | | +| NOTE 1: $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. | | | | + +**Table 7.7.2-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) | +|--------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|--------------------------------------------| +| 3 | ±4.5 | CW | +| | ±10.5 | 3 MHz DFT-s-OFDM NR signal | +| 5 | ±7.5 | CW | +| | ±17.5 | 5 MHz DFT-s-OFDM NR signal (Note 1) | +| 10 | ±7.465 | CW | +| | ±17.5 | 5 MHz DFT-s-OFDM NR signal (Note 1) | +| 15 | ±7.43 | CW | +| | ±17.5 | 5 MHz DFT-s-OFDM NR signal (Note 1) | +| 20 | ±7.395 | CW | +| | ±17.5 | 5 MHz 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 | 20 MHz DFT-s-OFDM NR signal (Note 2) | +| 35 | ±7.44 | CW | +| | ±25 | 20 MHz DFT-s-OFDM NR signal (Note 2) | +| 40 | ±7.45 | CW | +| | ±25 | 20 MHz DFT-s-OFDM NR signal (Note 2) | +| 45 | ±7.37 | CW | +| | ±25 | 20 MHz DFT-s-OFDM NR signal (Note 2) | +| 50 | ±7.35 | CW | +| | ±25 | 20 MHz DFT-s-OFDM NR signal (Note 2) | +| 60 | ±7.49 | CW | +| | ±25 | 20 MHz 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 | 20 MHz 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 | 20 MHz DFT-s-OFDM NR signal (Note 2) | + +NOTE 1: Number of RBs is 25 for 15 kHz subcarrier spacing and 10 for 30 kHz subcarrier spacing. + +NOTE 2: Number of RBs is 100 for 15 kHz subcarrier spacing, 50 for 30 kHz subcarrier spacing and 24 for 60 kHz subcarrier spacing. + +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.2-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. + +**Table 7.7.2-3: Narrowband intermodulation performance requirement in FR1** + +| BS type | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | Type of interfering signals | +|-----------------|--------------------------------------------|--------------------------------------------|------------------------------------| +| Wide Area BS | $P_{\text{REFSENS}} + 6\text{dB}$ (Note 1) | -52 | See Table 7.7.2-4 | +| Medium Range BS | $P_{\text{REFSENS}} + 6\text{dB}$ (Note 2) | -47 | | +| Local Area BS | $P_{\text{REFSENS}} + 6\text{dB}$ (Note 3) | -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 table 7.2.2-1. +For NB-IoT, $P_{\text{REFSENS}}$ depends also on the *sub-carrier spacing* as specified in tables 7.2.1-5 of TS 36.104 [13]. + +NOTE 2: $P_{\text{REFSENS}}$ depends on the RAT. +For NR, $P_{\text{REFSENS}}$ depends also on the *BS channel bandwidth* as specified in table 7.2.2-2. +For NB-IoT, $P_{\text{REFSENS}}$ depends also on the *sub-carrier spacing* as specified in tables 7.2.1-5c of TS 36.104 [13]. + +NOTE 3: $P_{\text{REFSENS}}$ depends on the RAT. +For NR, $P_{\text{REFSENS}}$ depends also on the *BS channel bandwidth* as specified in table 7.2.2-3. +For NB-IoT, $P_{\text{REFSENS}}$ depends also on the *sub-carrier spacing* as specified in tables 7.2.1-5a of TS 36.104 [13]. + +NOTE 4: For NB-IoT, the requirement shall apply only for a FRC A1-3 of TS 36.104 [13] mapped to the frequency range at the channel edge adjacent to the interfering signals. + +NOTE 5: 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 6: 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.2-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 signal | +|--------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------| +| 3 | ±360 | CW | +| | ±960 | 3 MHz DFT-s-OFDM NR signal, 1 RB (Note 1) | +| 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 | +| | ±2710 | 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.3 Additional narrowband intermodulation requirement for Band n100 + +The following requirement shall apply to BS operating in Band n100 in CEPT countries. 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* operating in Band n100, with the conditions specified in tables 7.7.3-1 and 7.7.3-2 for narrowband intermodulation performance. The reference measurement channel for the wanted signal is identified in table 7.2.2-1 and further specified in annex A.1. The characteristics of the interfering signal is further specified in annex D. + +The receiver intermodulation requirement is applicable outside the *Base Station RF Bandwidth*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges*. + +**Table 7.7.3-1: Additional narrowband intermodulation requirement for RMR BS operating in 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.3-2 | +| NOTE 1: $P_{\text{REFSENS}}$ depends also on the BS channel bandwidth as specified in clause 7.2.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 [23]. | | | + +**Table 7.7.3-2: Interfering signals for the additional narrowband intermodulation requirement for RMR BS operating in 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 | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|-------------------------------------------------------| +| 3 | -360 | CW | +| | -960 | 3 MHz DFT-s-OFDM NR signal, 15 kHz SCS, 1 RB (Note 1) | +| 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 General + +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 for BS type 1-C and BS type 1-H + +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.2-1 for Wide Area BS except for band n104, in table 7.8.2-1b for Wide Area BS for band n104, in table 7.8.2-2 for Medium Range BS except for band n46, n96, n102 and n104, in table 7.8.2-2b for Medium Range BS for band n46, in table 7.8.2-2c for Medium Range BS for band n96 and n102, in table 7.8.2-2d for Medium Range BS for band n104, in table 7.8.2-3 for Local Area BS except for band n46, n96, n102 and n104, in table 7.8.2-3b for Local Area BS for band n46, in table 7.8.2-3c for Local Area BS for band n96 and n102 and in table 7.8.2-3d for Local Area BS. The characteristics of the interfering signal is further specified in annex D. + +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.104 [13] with parameters specified in table 7.8.2-1a for Wide Area BS, in table 7.8.2-2a for Medium Range BS and in table 7.8.2-3a for Local Area BS. + +**Table 7.8.2-1: Wide Area BS in-channel selectivity** + +| BS channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | Type of interfering signal | +|-----------------------------------|---------------------------------|--------------------------------------|---------------------------------------|--------------------------------------------|-------------------------------------------| +| 3 | 15 | G-FR1-A1-20 | -102.8 | -83.6 | DFT-s-OFDM NR signal, 15 kHz SCS, 6 RBs | +| 5 | 15 | G-FR1-A1-7 | -100.6 | -81.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 10 RBs | +| 10, 15, 20, 25, 30, 35 | 15 | G-FR1-A1-1 | -98.7 | -77.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 40, 45, 50 | 15 | G-FR1-A1-4 | -92.3 | -71.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 100 RBs | +| 5 | 30 | G-FR1-A1-8 | -101.3 | -81.4 | DFT-s-OFDM NR signal, 30 kHz SCS, 5 RBs | +| 10, 15, 20, 25, 30, 35 | 30 | G-FR1-A1-2 | -98.8 | -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 | -92.6 | -71.4 | DFT-s-OFDM NR signal, 30 kHz SCS, 50 RBs | +| 10, 15, 20, 25, 30, 35 | 60 | G-FR1-A1-9 | -98.2 | -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 | -92.7 | -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. The aggregated wanted and interferer signal shall be centred in the BS channel bandwidth of the wanted signal. + +**Table 7.8.2-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 | +|-----------------------------------|-------------------------------------------|---------------------------------------|------------------------------------------------------------------|-------------------------------------------| +| 3 | FRC A14-1 in Annex A.14 in TS 36.104 [13] | -124.3 | -83.6 | DFT-s-OFDM NR signal, 15 kHz SCS, 6 RBs | +| 5 | | | -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 | +| 3 | FRC A14-2 in Annex A.14 in TS 36.104 [13] | -130.2 | -83.6 | DFT-s-OFDM NR signal, 15 kHz SCS, 6 RBs | +| 5 | | | -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.2-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 | -97.7 | -76.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 40, 50 | 15 | G-FR1-A1-4 | -91.3 | -70.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 100 RBs | +| 20, 30 | 30 | G-FR1-A1-2 | -97.8 | -77.4 | DFT-s-OFDM NR signal, 30 kHz SCS, 10 RBs | +| 40, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 | -91.6 | -70.4 | DFT-s-OFDM NR signal, 30 kHz SCS, 50 RBs | +| 20, 30 | 60 | G-FR1-A1-9 | -97.2 | -77.4 | DFT-s-OFDM NR signal, 60 kHz SCS, 5 RBs | +| 40, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 | -91.7 | -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.2-2: Medium Range BS in-channel selectivity** + +| BS channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | Type of interfering signal | +|-----------------------------------|---------------------------------|--------------------------------------|---------------------------------------|--------------------------------------------|-------------------------------------------| +| 3 | 15 | G-FR1-A1-20 | -97.8 | -78.6 | DFT-s-OFDM NR signal, 15 kHz SCS, 6 RBs | +| 5 | 15 | G-FR1-A1-7 | -95.6 | -76.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 10 RBs | +| 10, 15, 20, 25, 30, 35 | 15 | G-FR1-A1-1 | -93.7 | -72.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 40, 45, 50 | 15 | G-FR1-A1-4 | -87.3 | -66.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 100 RBs | +| 5 | 30 | G-FR1-A1-8 | -96.3 | -76.4 | DFT-s-OFDM NR signal, 30 kHz SCS, 5 RBs | +| 10, 15, 20, 25, 30, 35 | 30 | G-FR1-A1-2 | -93.8 | -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 | -87.6 | -66.4 | DFT-s-OFDM NR signal, 30 kHz SCS, 50 RBs | +| 10, 15, 20, 25, 30, 35 | 60 | G-FR1-A1-9 | -93.2 | -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 | -87.7 | -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.2-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) / BWConfig | Type of interfering signal | +|-----------------------------------|-------------------------------------------|---------------------------------------|------------------------------------------------------------------|-------------------------------------------| +| 3 | FRC A14-1 in Annex A.14 in TS 36.104 [13] | -119.3 | -78.6 | DFT-s-OFDM NR signal, 15 kHz SCS, 6 RBs | +| 5 | | | -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 | +| 3 | FRC A14-2 in Annex A.14 in TS 36.104 [13] | -125.2 | -78.6 | DFT-s-OFDM NR signal, 15 kHz SCS, 6 RBs | +| 5 | | | -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 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.2-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 | -100.0 | -79.5 | CP-OFDM NR signal, 15 kHz SCS, 10 RBs | +| | 30 | G-FR1-A1-13 | -97.7 | -77.4 | CP-OFDM NR signal, 30 kHz SCS, 10 RBs | +| | 60 | G-FR1-A1-9 | -93.2 | -73.4 | DFT-s-OFDM NR signal, 60 kHz SCS, 5 RBs | +| 20 | 15 | G-FR1-A1-14 | -97.1 | -76.4 | CP-OFDM NR signal, 15 kHz SCS, 10 RBs | +| | 30 | G-FR1-A1-15 | -94.1 | -73.4 | CP-OFDM NR signal, 30 kHz SCS, 10 RBs | +| | 60 | G-FR1-A1-9 | -93.2 | -73.4 | DFT-s-OFDM NR signal, 60 kHz SCS, 5 RBs | +| 40 | 15 | G-FR1-A1-16 | -94.0 | -73.2 | CP-OFDM NR signal, 15 kHz SCS, 20 RBs | +| | 30 | G-FR1-A1-17 | -91.0 | -70.2 | CP-OFDM NR signal, 30 kHz SCS, 10 RBs | +| | 60 | G-FR1-A1-6 | -87.7 | -66.6 | DFT-s-OFDM NR signal, 60 kHz SCS, 24 RBs | +| 60 | 30 | G-FR1-A1-18 | -89.4 | -68.4 | CP-OFDM NR signal, 30 kHz SCS, 20 RBs | +| | 60 | G-FR1-A1-6 | -87.7 | -66.6 | DFT-s-OFDM NR signal, 60 kHz SCS, 24 RBs | +| 80 | 30 | G-FR1-A1-19 | -88.1 | -67.1 | CP-OFDM NR signal, 30 kHz SCS, 20 RBs | +| | 60 | G-FR1-A1-6 | -87.7 | -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.2-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 | -96.1 | -75.4 | CP-OFDM NR signal, 15 kHz SCS, 10 RBs | +| | 30 | G-FR1-A1-15 | -93.1 | -72.4 | CP-OFDM NR signal, 30 kHz SCS, 10 RBs | +| | 60 | G-FR1-A1-9 | -92.2 | -72.4 | DFT-s-OFDM NR signal, 60 kHz SCS, 5 RBs | +| 40 | 15 | G-FR1-A1-16 | -93.0 | -72.2 | CP-OFDM NR signal, 15 kHz SCS, 20 RBs | +| | 30 | G-FR1-A1-17 | -90.0 | -69.2 | CP-OFDM NR signal, 30 kHz SCS, 10 RBs | +| | 60 | G-FR1-A1-6 | -86.7 | -65.6 | DFT-s-OFDM NR signal, 60 kHz SCS, 24 RBs | +| 60 | 30 | G-FR1-A1-18 | -88.4 | -67.4 | CP-OFDM NR signal, 30 kHz SCS, 20 RBs | +| | 60 | G-FR1-A1-6 | -86.7 | -65.6 | DFT-s-OFDM NR signal, 60 kHz SCS, 24 RBs | +| 80 | 30 | G-FR1-A1-19 | -87.1 | -66.1 | CP-OFDM NR signal, 30 kHz SCS, 20 RBs | +| | 60 | G-FR1-A1-6 | -86.7 | -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.2-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 | -92.7 | -71.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 40, 50 | 15 | G-FR1-A1-4 | -86.3 | -65.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 100 RBs | +| 20, 30 | 30 | G-FR1-A1-2 | -92.8 | -72.4 | DFT-s-OFDM NR signal, 30 kHz SCS, 10 RBs | +| 40, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 | -86.6 | -65.4 | DFT-s-OFDM NR signal, 30 kHz SCS, 50 RBs | +| 20, 30 | 60 | G-FR1-A1-9 | -92.2 | -72.4 | DFT-s-OFDM NR signal, 60 kHz SCS, 5 RBs | +| 40, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 | -86.7 | -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.2-3: Local area BS in-channel selectivity** + +| BS channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | Type of interfering signal | +|-----------------------------------|---------------------------------|--------------------------------------|---------------------------------------|--------------------------------------------|-------------------------------------------| +| 3 | 15 | G-FR1-A1-20 | -94.8 | -75.6 | DFT-s-OFDM NR signal, 15 kHz SCS, 6 RBs | +| 5 | 15 | G-FR1-A1-7 | -92.6 | -73.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 10 RBs | +| 10, 15, 20, 25, 30, 35 | 15 | G-FR1-A1-1 | -90.7 | -69.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 40, 45, 50 | 15 | G-FR1-A1-4 | -84.3 | -63.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 100 RBs | +| 5 | 30 | G-FR1-A1-8 | -93.3 | -73.4 | DFT-s-OFDM NR signal, 30 kHz SCS, 5 RBs | +| 10, 15, 20, 25, 30, 35 | 30 | G-FR1-A1-2 | -90.8 | -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 | -84.6 | -63.4 | DFT-s-OFDM NR signal, 30 kHz SCS, 50 RBs | +| 10, 15, 20, 25, 30, 35 | 60 | G-FR1-A1-9 | -90.2 | -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 | -84.7 | -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. The aggregated wanted and interferer signal shall be centred in the *BS channel bandwidth* of the wanted signal. + +**Table 7.8.2-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 | +|-----------------------------------|-------------------------------------------|---------------------------------------|------------------------------------------------------------------|-------------------------------------------| +| 3 | FRC A14-1 in Annex A.14 in TS 36.104 [13] | -116.3 | -75.6 | DFT-s-OFDM NR signal, 15 kHz SCS, 6 RBs | +| 5 | | | -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 | +| 3 | FRC A14-2 in Annex A.14 in TS 36.104 [13] | -122.2 | -75.6 | DFT-s-OFDM NR signal, 15 kHz SCS, 6 RBs | +| 5 | | | -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.2-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 | -97.0 | -76.5 | CP-OFDM NR signal, 15 kHz SCS, 10 RBs | +| | 30 | G-FR1-A1-13 | -94.7 | -74.4 | CP-OFDM NR signal, 30 kHz SCS, 10 RBs | +| | 60 | G-FR1-A1-9 | -90.2 | -70.4 | DFT-s-OFDM NR signal, 60 kHz SCS, 5 RBs | +| 20 | 15 | G-FR1-A1-14 | -94.1 | -73.4 | CP-OFDM NR signal, 15 kHz SCS, 10 RBs | +| | 30 | G-FR1-A1-15 | -91.1 | -70.4 | CP-OFDM NR signal, 30 kHz SCS, 10 RBs | +| | 60 | G-FR1-A1-9 | -90.2 | -70.4 | DFT-s-OFDM NR signal, 60 kHz SCS, 5 RBs | +| 40 | 15 | G-FR1-A1-16 | -91.0 | -70.2 | CP-OFDM NR signal, 15 kHz SCS, 20 RBs | +| | 30 | G-FR1-A1-17 | -88.0 | -67.2 | CP-OFDM NR signal, 30 kHz SCS, 10 RBs | +| | 60 | G-FR1-A1-6 | -84.7 | -63.6 | DFT-s-OFDM NR signal, 60 kHz SCS, 24 RBs | +| 60 | 30 | G-FR1-A1-18 | -86.4 | -65.4 | CP-OFDM NR signal, 30 kHz SCS, 20 RBs | +| | 60 | G-FR1-A1-6 | -84.7 | -63.6 | DFT-s-OFDM NR signal, 60 kHz SCS, 24 RBs | +| 80 | 30 | G-FR1-A1-19 | -85.1 | -64.1 | CP-OFDM NR signal, 30 kHz SCS, 20 RBs | +| | 60 | G-FR1-A1-6 | -84.7 | -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. The aggregated wanted and interferer signal shall be centred in the BS channel bandwidth of the wanted signal. + +**Table 7.8.2-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 | -93.1 | -72.4 | CP-OFDM NR signal, 15 kHz SCS, 10 RBs | +| | 30 | G-FR1-A1-15 | -90.1 | -69.4 | CP-OFDM NR signal, 30 kHz SCS, 10 RBs | +| | 60 | G-FR1-A1-9 | -89.2 | -69.4 | DFT-s-OFDM NR signal, 60 kHz SCS, 5 RBs | +| 40 | 15 | G-FR1-A1-16 | -90.0 | -69.2 | CP-OFDM NR signal, 15 kHz SCS, 20 RBs | +| | 30 | G-FR1-A1-17 | -87.0 | -66.2 | CP-OFDM NR signal, 30 kHz SCS, 10 RBs | +| | 60 | G-FR1-A1-6 | -83.7 | -62.6 | DFT-s-OFDM NR signal, 60 kHz SCS, 24 RBs | +| 60 | 30 | G-FR1-A1-18 | -85.4 | -64.4 | CP-OFDM NR signal, 30 kHz SCS, 20 RBs | +| | 60 | G-FR1-A1-6 | -83.7 | -62.6 | DFT-s-OFDM NR signal, 60 kHz SCS, 24 RBs | +| 80 | 30 | G-FR1-A1-19 | -84.1 | -63.1 | CP-OFDM NR signal, 30 kHz SCS, 20 RBs | +| | 60 | G-FR1-A1-6 | -83.7 | -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.2-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 | -89.7 | -68.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 40, 50 | 15 | G-FR1-A1-4 | -83.3 | -62.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 100 RBs | +| 20, 30 | 30 | G-FR1-A1-2 | -89.8 | -69.4 | DFT-s-OFDM NR signal, 30 kHz SCS, 10 RBs | +| 40, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 | -83.6 | -62.4 | DFT-s-OFDM NR signal, 30 kHz SCS, 50 RBs | +| 20, 30 | 60 | G-FR1-A1-9 | -89.2 | -69.4 | DFT-s-OFDM NR signal, 60 kHz SCS, 5 RBs | +| 40, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 | -83.7 | -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 requirements + +### 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 defined in annex A and the propagation conditions in annex G. The requirements only apply to those FRCs that are supported by the base station. + +Unless stated otherwise, performance requirements apply for a single carrier only. Performance requirements for a BS 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 *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 as specified in TS 38.141-1 [5]. + +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 *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 on a single *antenna connector* (for *BS type 1-C*) or on a single *TAB connector* (for *BS type 1-H*). + +#### 8.1.2 Void + +### 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 | +| 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}, {0, 1}, {0, 1, 2, 3} | +| | 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 | +| TPMI index for 2Tx two-layer or 4Tx four-layer spatial multiplexing transmission | | 0 | +| Code block group based PUSCH transmission | | Disabled | +| NOTE 1: The same requirements are applicable to FDD and TDD with different UL-DL pattern. | | | + +### 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-20 at the given SNR for 1Tx 2Tx two-layer, or 4Tx four-layer spatial multiplexing transmission. 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 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-8 | pos1 | -2.3 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-8 | pos1 | 10.1 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-8 | pos1 | 12.3 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A9-1 | pos1 | 19.1 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-8 | pos1 | -5.8 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-8 | pos1 | 6.2 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-8 | pos1 | 8.8 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A9-1 | pos1 | 15.5 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-8 | pos1 | -8.7 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-8 | pos1 | 3.0 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-8 | pos1 | 5.6 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A9-1 | pos1 | 12.4 | +| 2 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-22 | pos1 | 1.0 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-22 | pos1 | 18.2 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-22 | pos1 | -2.3 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-22 | pos1 | 11.0 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-22 | pos1 | -5.3 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-22 | pos1 | 6.8 | +| 4 | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-39 | pos1 | [1.8] | +| | | Normal | TLDC300-100 Low | 70 % | G-FR1-A7-1 | pos1 | [14.6] | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A11-1 | pos1 | [19.2] | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-39 | pos1 | [-1.5] | +| | | Normal | TLDC300-100 Low | 70 % | G-FR1-A7-1 | pos1 | [8.0] | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A11-1 | pos1 | [11.6] | + +**Table 8.2.1.2-2: Minimum 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 | -2.5 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-9 | pos1 | 10.2 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-9 | pos1 | 12.2 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A9-2 | pos1 | 19.5 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-9 | pos1 | -6.0 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-9 | pos1 | 6.3 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-9 | pos1 | 8.6 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A9-2 | pos1 | 15.9 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-9 | pos1 | -8.7 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-9 | pos1 | 3.1 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-9 | pos1 | 5.5 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A9-2 | pos1 | 12.6 | +| 2 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-23 | pos1 | 1.7 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-23 | pos1 | 18.3 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-23 | pos1 | -2.0 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-23 | pos1 | 11.2 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-23 | pos1 | -5.5 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-23 | pos1 | 6.8 | + +**Table 8.2.1.2-3: 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 | TDLB100-400 Low | 70 % | G-FR1-A3-10 | pos1 | -2.1 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-10 | pos1 | 10.0 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-10 | pos1 | 12.4 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-10 | pos1 | -5.5 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-10 | pos1 | 6.2 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-10 | pos1 | 8.6 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-10 | pos1 | -8.5 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-10 | pos1 | 3.0 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-10 | pos1 | 5.5 | +| 2 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-24 | pos1 | 2.1 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-24 | pos1 | 18.3 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-24 | pos1 | -1.8 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-24 | pos1 | 11.1 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-24 | pos1 | -5.3 | +| 4 | 4 | Normal | TDLA30-10 Low | 70 % | G-FR1-A11-2 | pos1 | [20.1] | +| | 8 | Normal | TDLA30-10 Low | 70 % | G-FR1-A11-2 | pos1 | [11.9] | + +**Table 8.2.1.2-4: 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 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-11 | pos1 | -2.3 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-11 | pos1 | 10.2 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-11 | pos1 | 12.8 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A9-3 | pos1 | 19.3 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-11 | pos1 | -5.6 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-11 | pos1 | 6.4 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-11 | pos1 | 8.6 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A9-3 | pos1 | 15.6 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-11 | pos1 | -8.6 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-11 | pos1 | 3.3 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-11 | pos1 | 5.5 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A9-3 | pos1 | 12.6 | +| 2 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-25 | pos1 | 1.3 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-25 | pos1 | 18.4 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-25 | pos1 | -2.2 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-25 | pos1 | 11.2 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-25 | pos1 | -5.2 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-25 | pos1 | 7.0 | +| 4 | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-41 | pos1 | [1.6] | +| | | Normal | TLDC300-100 Low | 70 % | G-FR1-A7-3 | pos1 | [14.9] | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A11-4 | pos1 | [19.2] | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-41 | pos1 | [-1.6] | +| | | Normal | TLDC300-100 Low | 70 % | G-FR1-A7-3 | pos1 | [8.2] | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A11-4 | pos1 | [11.6] | + +**Table 8.2.1.2-5: 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 | TDLB100-400 Low | 70 % | G-FR1-A3-12 | pos1 | -2.9 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-12 | pos1 | 10.2 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-12 | pos1 | 12.5 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-12 | pos1 | -6.0 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-12 | pos1 | 6.4 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-12 | pos1 | 8.6 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-12 | pos1 | -8.8 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-12 | pos1 | 3.2 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-12 | pos1 | 5.5 | +| 2 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-26 | pos1 | 1.3 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-26 | pos1 | 18.1 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-26 | pos1 | -2.2 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-26 | pos1 | 11.3 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-26 | pos1 | -5.3 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-26 | pos1 | 6.9 | + +**Table 8.2.1.2-6: Minimum 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 | -2.5 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-13 | pos1 | 10.0 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-13 | pos1 | 12.4 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A9-4 | pos1 | 19.9 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-13 | pos1 | -5.8 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-13 | pos1 | 6.3 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-13 | pos1 | 8.5 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A9-4 | pos1 | 16.1 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-13 | pos1 | -8.7 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-13 | pos1 | 3.1 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-13 | pos1 | 5.4 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A9-4 | pos1 | 12.6 | +| 2 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-27 | pos1 | 1.3 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-27 | pos1 | 19.5 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-27 | pos1 | -2.3 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-27 | pos1 | 11.3 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-27 | pos1 | -5.2 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-27 | pos1 | 6.9 | +| 4 | 4 | Normal | TDLA30-10 Low | 70 % | G-FR1-A11-5 | pos1 | [19.6] | +| | 8 | Normal | TDLA30-10 Low | 70 % | G-FR1-A11-5 | pos1 | [11.8] | + +**Table 8.2.1.2-7: Minimum 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.8 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-14 | pos1 | 10.2 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-14 | pos1 | 13.0 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A9-5 | pos1 | 21.1 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-14 | pos1 | -5.8 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-14 | pos1 | 6.5 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-14 | pos1 | 9.0 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A9-5 | pos1 | 16.7 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-14 | pos1 | -8.7 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-14 | pos1 | 3.2 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-14 | pos1 | 5.8 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A9-5 | pos1 | 13.1 | +| 2 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-28 | pos1 | 1.4 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-28 | pos1 | 19.2 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-28 | pos1 | -2.2 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-28 | pos1 | 11.6 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-28 | pos1 | -5.2 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-28 | pos1 | 7.1 | +| 4 | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-42 | pos1 | [2.0] | +| | | Normal | TLDC300-100 Low | 70 % | G-FR1-A7-4 | pos1 | [15.8] | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A11-6 | pos1 | [20.6] | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-42 | pos1 | [-1.4] | +| | | Normal | TLDC300-100 Low | 70 % | G-FR1-A7-4 | pos1 | [8.5] | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A11-6 | pos1 | [12.2] | + +**Table 8.2.1.2-8: 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 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-8 | pos1 | -2.3 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-8 | pos1 | 10.2 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-8 | pos1 | 12.5 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A9-1 | pos1 | 19.1 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-8 | pos1 | -5.7 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-8 | pos1 | 6.3 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-8 | pos1 | 8.9 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A9-1 | pos1 | 15.5 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-8 | pos1 | -8.7 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-8 | pos1 | 3.0 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-8 | pos1 | 5.7 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A9-1 | pos1 | 12.3 | +| 2 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-22 | pos1 | 1.5 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-22 | pos1 | 18.3 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-22 | pos1 | -2.3 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-22 | pos1 | 11.1 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-22 | pos1 | -5.4 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-22 | pos1 | 6.8 | +| 4 | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-39 | pos1 | [1.9] | +| | | Normal | TLDC300-100 Low | 70 % | G-FR1-A7-1 | pos1 | [14.7] | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A11-1 | pos1 | [19.2] | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-39 | pos1 | [-1.4] | +| | | Normal | TLDC300-100 Low | 70 % | G-FR1-A7-1 | pos1 | [8.2] | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A11-1 | pos1 | [11.6] | + +**Table 8.2.1.2-9: Minimum 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 | -2.3 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-9 | pos1 | 10.5 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-9 | pos1 | 12.6 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A9-2 | pos1 | 19.5 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-9 | pos1 | -5.7 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-9 | pos1 | 6.5 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-9 | pos1 | 8.9 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A9-2 | pos1 | 15.9 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-9 | pos1 | -9.0 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-9 | pos1 | 3.2 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-9 | pos1 | 5.8 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A9-2 | pos1 | 12.5 | +| 2 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-23 | pos1 | 2.0 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-23 | pos1 | 18.7 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-23 | pos1 | -2.3 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-23 | pos1 | 11.3 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-23 | pos1 | -5.2 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-23 | pos1 | 7.0 | + +**Table 8.2.1.2-10: 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 | TDLB100-400 Low | 70 % | G-FR1-A3-10 | pos1 | -2.1 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-10 | pos1 | 10.4 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-10 | pos1 | 12.3 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-10 | pos1 | -5.7 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-10 | pos1 | 6.3 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-10 | pos1 | 8.8 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-10 | pos1 | -8.5 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-10 | pos1 | 3.1 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-10 | pos1 | 5.7 | +| 2 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-24 | pos1 | 1.6 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-24 | pos1 | 18.1 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-24 | pos1 | -2.0 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-24 | pos1 | 11.2 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-24 | pos1 | -5.3 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-24 | pos1 | 6.9 | +| 4 | 4 | Normal | TDLA30-10 Low | 70 % | G-FR1-A11-2 | pos1 | [20.1] | +| | 8 | Normal | TDLA30-10 Low | 70 % | G-FR1-A11-2 | pos1 | [11.9] | + +**Table 8.2.1.2-11: 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 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-11 | pos1 | -2.4 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-11 | pos1 | 10.1 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-11 | pos1 | 12.5 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A9-3 | pos1 | 19.2 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-11 | pos1 | -5.7 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-11 | pos1 | 6.4 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-11 | pos1 | 8.6 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A9-3 | pos1 | 15.7 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-11 | pos1 | -8.8 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-11 | pos1 | 3.2 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-11 | pos1 | 5.6 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A9-3 | pos1 | 12.4 | +| 2 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-25 | pos1 | 1.1 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-25 | pos1 | 18.5 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-25 | pos1 | -2.5 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-25 | pos1 | 11.3 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-25 | pos1 | -5.6 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-25 | pos1 | 7.0 | +| 4 | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-41 | pos1 | [1.7] | +| | | Normal | TLDC300-100 Low | 70 % | G-FR1-A7-3 | pos1 | [15.0] | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A11-4 | pos1 | [19.2] | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-41 | pos1 | [-1.6] | +| | | Normal | TLDC300-100 Low | 70 % | G-FR1-A7-3 | pos1 | [8.3] | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A11-4 | pos1 | [1.7] | + +**Table 8.2.1.2-12: 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 | TDLB100-400 Low | 70 % | G-FR1-A3-12 | pos1 | -2.9 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-12 | pos1 | 10.1 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-12 | pos1 | 12.5 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-12 | pos1 | -6.0 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-12 | pos1 | 6.3 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-12 | pos1 | 8.6 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-12 | pos1 | -9.0 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-12 | pos1 | 3.1 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-12 | pos1 | 5.6 | +| 2 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-26 | pos1 | 1.3 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-26 | pos1 | 18.2 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-26 | pos1 | -2.3 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-26 | pos1 | 11.2 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-26 | pos1 | -5.4 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-26 | pos1 | 7.0 | + +**Table 8.2.1.2-13: Minimum 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 | -2.5 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-13 | pos1 | 10.0 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-13 | pos1 | 12.5 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A9-4 | pos1 | 19.9 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-13 | pos1 | -5.8 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-13 | pos1 | 6.2 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-13 | pos1 | 8.7 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A9-4 | pos1 | 16.0 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-13 | pos1 | -8.8 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-13 | pos1 | 3.0 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-13 | pos1 | 5.5 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A9-4 | pos1 | 12.7 | +| 2 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-27 | pos1 | 1.7 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-27 | pos1 | 18.7 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-27 | pos1 | -2.1 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-27 | pos1 | 11.2 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-27 | pos1 | -5.2 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-27 | pos1 | 6.9 | +| 4 | 4 | Normal | TDLA30-10 Low | 70 % | G-FR1-A11-5 | pos1 | [19.7] | +| | 8 | Normal | TDLA30-10 Low | 70 % | G-FR1-A11-5 | pos1 | [11.9] | + +**Table 8.2.1.2-14: Minimum 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 | -2.5 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-14 | pos1 | 10.1 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-14 | pos1 | 13.1 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A9-5 | pos1 | 21.1 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-14 | pos1 | -5.8 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-14 | pos1 | 6.3 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-14 | pos1 | 9.2 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A9-5 | pos1 | 16.9 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-14 | pos1 | -8.7 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-14 | pos1 | 3.1 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-14 | pos1 | 5.9 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A9-5 | pos1 | 13.2 | +| 2 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-28 | pos1 | 1.6 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-28 | pos1 | 19.3 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-28 | pos1 | -2.2 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-28 | pos1 | 11.6 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-28 | pos1 | -5.3 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-28 | pos1 | 7.1 | +| 4 | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-42 | pos1 | [2.1] | +| | | Normal | TLDC300-100 Low | 70 % | G-FR1-A7-4 | pos1 | [15.9] | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A11-6 | pos1 | [20.7] | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-42 | pos1 | [-1.3] | +| | | Normal | TLDC300-100 Low | 70 % | G-FR1-A7-4 | pos1 | [8.6] | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A11-6 | pos1 | [12.3] | + +**Table 8.2.1.2-15: Minimum 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 | 2.9 | + +**Table 8.2.1.2-16: Minimum 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 | 2.8 | + +**Table 8.2.1.2-17: Minimum 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 | 2.8 | + +**Table 8.2.1.2-18: Minimum 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 | 2.9 | + +**Table 8.2.1.2-19: Minimum requirements for PUSCH with 70% of maximum throughput, Type A, 50 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) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 4 | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-40 | pos1 | [2.1] | +| | | Normal | TLDC300-100 Low | 70 % | G-FR1-A7-2 | pos1 | [15.0] | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A11-3 | pos1 | [21.2] | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-40 | pos1 | [-1.3] | +| | | Normal | TLDC300-100 Low | 70 % | G-FR1-A7-2 | pos1 | [8.3] | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A11-3 | pos1 | [12.4] | + +**Table 8.2.1.2-20: Minimum requirements for PUSCH with 70% of maximum throughput, Type B 50 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) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 4 | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-40 | pos1 | [2.4] | +| | | Normal | TLDC300-100 Low | 70 % | G-FR1-A7-2 | pos1 | [15.1] | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A11-3 | pos1 | [21.2] | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-40 | pos1 | [-1.2] | +| | | Normal | TLDC300-100 Low | 70 % | G-FR1-A7-2 | pos1 | [8.3] | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A11-3 | pos1 | [12.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 | +| 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 | +| | RV sequence | +| DM-RS | DM-RS configuration type | +| | DM-RS duration | +| | Additional DM-RS position | +| | Number of DM-RS CDM group(s) without data | +| | Ratio of PUSCH EPRE to DM-RS EPRE | +| | DM-RS port(s) | +| | DM-RS sequence generation | +| Time domain resource assignment | PUSCH mapping type | +| | Start symbol | +| | Allocation length | +| Frequency domain resource assignment | RB assignment | +| | Frequency hopping | +| Code block group based PUSCH transmission | Disabled | +| NOTE 1: The same requirements are applicable to FDD and TDD with different UL-DL patterns. | | + +### 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, 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 | -2.4 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-31 | pos1 | -5.7 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-31 | pos1 | -8.5 | + +**Table 8.2.2.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 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-32 | pos1 | -2.5 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-32 | pos1 | -5.7 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-32 | pos1 | -8.4 | + +**Table 8.2.2.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 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-31 | pos1 | -2.3 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-31 | pos1 | -5.8 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-31 | pos1 | -8.6 | + +**Table 8.2.2.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 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-32 | pos1 | -2.7 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-32 | pos1 | -6.0 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-32 | pos1 | -8.8 | + +## 8.2.3 Requirements for UCI multiplexed on PUSCH + +### 8.2.3.1 General + +In the tests for UCI multiplexed on PUSCH, the UCI information only contains CSI part 1 and CSI part 2 information, and there is no HARQ-ACK information transmitted. + +The CSI part 1 block error probability (BLER) is defined as the probability of incorrectly decoding the CSI part 1 information when the CSI part 1 information is sent as follow: + +where: + +- #(false CSI part 1) denotes the number of incorrectly decoded CSI part 1 information transmitted occasions + +- #(CSI part 1) denotes the number of CSI part 1 information transmitted occasions. + +The CSI part 2 block error probability is defined as the probability of incorrectly decoding the CSI part 2 information when the CSI part 2 information is sent as follows: + +where: + +- #(false CSI part 2) denotes the number of incorrectly decoded CSI part 2 information transmitted occasions +- #(CSI part 2) denotes the number of CSI part 2 information transmitted occasions. + +The number of UCI information bit payload per slot is defined for two cases as follows: + +- 5 bits in CSI part 1, 2 bits in CSI part 2 +- 20 bits in CSI part 1, 20 bits in CSI part 2 + +The 7bits UCI 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 part2 information. + +The 40bits UCI information case is assumed random information bit selection. + +In both tests, PUSCH data, CSI part 1 and CSI part 2 information are transmitted simultaneously. + +**Table 8.2.3.1-1: Test parameters for testing UCI 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 | +| UCI | 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. | | | + +### 8.2.3.2 Minimum requirements + +The CSI part 1 block error probability shall not exceed 0.1% at the SNR in table 8.2.3.2-1 and table 8.2.3.2-2. The CSI part 2 block error probability shall not exceed 1% at the SNR given in table 8.2.3.2-3 and table 8.2.3.2-4. + +**Table 8.2.3.2-1: Minimum 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 | 5.4 | +| | 2 | Normal | TDLC300-100 Low | 40(20,20) | pos1 | G-FR1-A4-11 | 4.3 | + +**Table 8.2.3.2-2: Minimum 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 | 5.8 | +| | 2 | Normal | TDLC300-100 Low | 40(20,20) | pos1 | G-FR1-A4-11 | 4.1 | + +**Table 8.2.3.2-3: Minimum 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.2 | +| | 2 | Normal | TDLC300-100 Low | 40(20,20) | pos1 | G-FR1-A4-11 | 2.4 | + +**Table 8.2.3.2-4: Minimum 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.3 | +| | 2 | Normal | TDLC300-100 Low | 40(20,20) | pos1 | G-FR1-A4-11 | 2.6 | + +## 8.2.4 Requirements for PUSCH for high speed train + +### 8.2.4.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. The performance requirements for high speed train are optional. + +The performance requirements for PUSCH for high speed train only apply to Wide Area Base Stations and Medium Range Base Stations (subject to declaration). + +**Table: 8.2.4.1-1 Test parameters for testing high speed train 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 | 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$ | +| Time domain resource assignment | PUSCH mapping type | A | +| | 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 pattern. | | | + +## 8.2.4.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.4.2-1 to 8.2.4.2-10 at the given SNR for 1Tx. FRCs are defined in annex A. Unless stated otherwise, the MIMO correlation matrices for the gNB are defined in annex G for low correlation. + +**Table 8.2.4.2-1: Minimum 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.8 | +| | 2 | Normal | HST Scenario 1-NR350 | 70 % | G-FR1-A3-33 | pos2 | -3.7 | +| | | Normal | HST Scenario 1-NR350 | 70 % | G-FR1-A4-29 | pos2 | 8.4 | +| | | Normal | HST Scenario 3-NR350 | 70 % | G-FR1-A3-33 | pos2 | -3.6 | +| | | Normal | HST Scenario 3-NR350 | 70 % | G-FR1-A4-29 | pos2 | 8.7 | +| | 8 | Normal | HST Scenario 1-NR350 | 70 % | G-FR1-A3-33 | pos2 | -9.2 | +| | | Normal | HST Scenario 1-NR350 | 70 % | G-FR1-A4-29 | pos2 | 2.6 | + +**Table 8.2.4.2-2: Minimum 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.6 | +| | 2 | Normal | HST Scenario 1-NR350 | 70 % | G-FR1-A3-34 | pos2 | -3.7 | +| | | Normal | HST Scenario 1-NR350 | 70 % | G-FR1-A4-30 | pos2 | 8.5 | +| | | Normal | HST Scenario 3-NR350 | 70 % | G-FR1-A3-34 | pos2 | -3.5 | +| | | Normal | HST Scenario 3-NR350 | 70 % | G-FR1-A4-30 | pos2 | 8.8 | +| | 8 | Normal | HST Scenario 1-NR350 | 70 % | G-FR1-A3-34 | pos2 | -9.1 | +| | | Normal | HST Scenario 1-NR350 | 70 % | G-FR1-A4-30 | pos2 | 2.7 | + +**Table 8.2.4.2-3: Minimum 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.7 | +| | 2 | Normal | HST Scenario 1-NR500 | 70 % | G-FR1-A3-33 | pos2 | -3.9 | +| | | Normal | HST Scenario 1-NR500 | 70 % | G-FR1-A4-29 | pos2 | 8.5 | +| | | Normal | HST Scenario 3-NR500 | 70 % | G-FR1-A3-33 | pos2 | -3.6 | +| | | Normal | HST Scenario 3-NR500 | 70 % | G-FR1-A4-29 | pos2 | 9.2 | +| | 8 | Normal | HST Scenario 1-NR500 | 70 % | G-FR1-A3-33 | pos2 | -9.4 | +| | | Normal | HST Scenario 1-NR500 | 70 % | G-FR1-A4-29 | pos2 | 2.7 | + +**Table 8.2.4.2-4: Minimum 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.5 | +| | 2 | Normal | HST Scenario 1-NR500 | 70 % | G-FR1-A3-34 | pos2 | -3.9 | +| | | Normal | HST Scenario 1-NR500 | 70 % | G-FR1-A4-30 | pos2 | 8.7 | +| | | Normal | HST Scenario 3-NR500 | 70 % | G-FR1-A3-34 | pos2 | -3.4 | +| | | Normal | HST Scenario 3-NR500 | 70 % | G-FR1-A4-30 | pos2 | 10.2 | +| | 8 | Normal | HST Scenario 1-NR500 | 70 % | G-FR1-A3-34 | pos2 | -9.2 | +| | | Normal | HST Scenario 1-NR500 | 70 % | G-FR1-A4-30 | pos2 | 2.8 | + +**Table 8.2.4.2-5: Minimum 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.7 | +| | 2 | Normal | HST Scenario 1-NR350 | 70 % | G-FR1-A3-33A | pos2 | -3.7 | +| | | Normal | HST Scenario 1-NR350 | 70 % | G-FR1-A4-29A | pos2 | 8.5 | +| | | Normal | HST Scenario 3-NR350 | 70 % | G-FR1-A3-33A | pos2 | -3.6 | +| | | Normal | HST Scenario 3-NR350 | 70 % | G-FR1-A4-29A | pos2 | 8.6 | +| | 8 | Normal | HST Scenario 1-NR350 | 70 % | G-FR1-A3-33A | pos2 | -9.1 | +| | | Normal | HST Scenario 1-NR350 | 70 % | G-FR1-A4-29A | pos2 | 2.8 | + +**Table 8.2.4.2-6: Minimum 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.7 | +| | 2 | Normal | HST Scenario 1-NR350 | 70 % | G-FR1-A3-34A | pos2 | -3.6 | +| | | Normal | HST Scenario 1-NR350 | 70 % | G-FR1-A4-30A | pos2 | 8.3 | +| | | Normal | HST Scenario 3-NR350 | 70 % | G-FR1-A3-34A | pos2 | -3.6 | +| | | Normal | HST Scenario 3-NR350 | 70 % | G-FR1-A4-30A | pos2 | 8.6 | +| | 8 | Normal | HST Scenario 1-NR350 | 70 % | G-FR1-A3-34A | pos2 | -9.0 | +| | | Normal | HST Scenario 1-NR350 | 70 % | G-FR1-A4-30A | pos2 | 2.6 | + +**Table 8.2.4.2-7: Minimum 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.6 | +| | 2 | Normal | HST Scenario 1-NR500 | 70 % | G-FR1-A3-33A | pos2 | -3.6 | +| | | Normal | HST Scenario 1-NR500 | 70 % | G-FR1-A4-29A | pos2 | 8.7 | +| | | Normal | HST Scenario 3-NR500 | 70 % | G-FR1-A3-33A | pos2 | -3.5 | +| | | Normal | HST Scenario 3-NR500 | 70 % | G-FR1-A4-29A | pos2 | 8.8 | +| | 8 | Normal | HST Scenario 1-NR500 | 70 % | G-FR1-A3-33A | pos2 | -9.1 | +| | | Normal | HST Scenario 1-NR500 | 70 % | G-FR1-A4-29A | pos2 | 3.0 | + +**Table 8.2.4.2-8: Minimum 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.5 | +| | 2 | Normal | HST Scenario 1-NR500 | 70 % | G-FR1-A3-34A | pos2 | -3.6 | +| | | Normal | HST Scenario 1-NR500 | 70 % | G-FR1-A4-30A | pos2 | 8.6 | +| | | Normal | HST Scenario 3-NR500 | 70 % | G-FR1-A3-34A | pos2 | -3.4 | +| | | Normal | HST Scenario 3-NR500 | 70 % | G-FR1-A4-30A | pos2 | 8.6 | +| | 8 | Normal | HST Scenario 1-NR500 | 70 % | G-FR1-A3-34A | pos2 | -8.8 | +| | | Normal | HST Scenario 1-NR500 | 70 % | G-FR1-A4-30A | pos2 | 2.9 | + +**Table 8.2.4.2-9: Minimum requirements for PUSCH, Type A, 5 MHz channel bandwidth, 15 kHz SCS, 500km/h, multi-path fading channel requirements with 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.9 | + +**Table 8.2.4.2-10: Minimum requirements for PUSCH, Type A, 10 MHz channel bandwidth, 30 kHz SCS, 500km/h, multi-path fading channel requirements with 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 | -2.0 | + +## 8.2.5 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. 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. + +**Table 8.2.5-1 Test parameters for testing UL timing adjustment** + +| Parameter | | Value | +|--------------------------------------|----------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Transform precoding | | Disabled | +| Uplink-downlink allocation for TDD | | 15 kHz SCS:
3D1S1U, S=10D:2G:2U
30 kHz SCS:
7D1S2U, S=6D:4G:4U | +| Channel bandwidth | | 15 kHz SCS: 5MHz, 10 MHz
30 kHz SCS: 10MHz, 40 MHz | +| MCS | | 16 | +| 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 | +| | DM-RS position ( $l_0$ ) | 2 | +| | 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} | +| Time domain resource assignment | DM-RS sequence generation | $N_{ID}^0=0, n_{SCID}=0$ for moving UE
$N_{ID}^0=1, n_{SCID}=1$ for stationary UE | +| | PUSCH mapping type | Both A and 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, 25 for 10 MHz
CBW for SCS 15kHz, and 12 for 10MHz, 50
for 40 MHz CBW for SCS 30kHz | +| | Frequency hopping | Disabled | +| SRS resource allocation | Slots in which sounding RS is transmitted (Note 1) | 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 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. + +### 8.2.5.1 Minimum requirements 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.1-1 for mapping type A and table 8.2.5.1-2 for mapping type B respectively. + +**Table 8.2.5.1-1 Minimum 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.2 | +| | | | | | Scenario Z | G-FR1-A4-31A | 8.3 | +| | | | 10 | 15 | Scenario Y | G-FR1-A4-31 | 8.5 | +| | | | | | Scenario Z | G-FR1-A4-31 | 8.4 | +| | | | 10 | 30 | Scenario Y | G-FR1-A4-32A | 8.3 | +| | | | | | Scenario Z | G-FR1-A4-32A | 8.3 | +| | | | 40 | 30 | Scenario Y | G-FR1-A4-32 | 8.4 | +| | | | | | Scenario Z | G-FR1-A4-32 | 8.5 | + +**Table 8.2.5.1-2 Minimum 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.3 | +| | | | | | Scenario Z | G-FR1-A4-31A | 8.3 | +| | | | 10 | 15 | Scenario Y | G-FR1-A4-31 | 8.5 | +| | | | | | Scenario Z | G-FR1-A4-31 | 8.5 | +| | | | 10 | 30 | Scenario Y | G-FR1-A4-32A | 8.3 | +| | | | | | Scenario Z | G-FR1-A4-32A | 8.4 | +| | | | 40 | 30 | Scenario Y | G-FR1-A4-32 | 8.4 | +| | | | | | Scenario Z | G-FR1-A4-32 | 8.5 | + +## 8.2.5.2 Minimum requirements 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.2-1 for mapping type A and table 8.2.5.2-2 for mapping type B respectively. + +**Table 8.2.5.2-1 Minimum requirements for UL timing adjustment with mapping type A for normal mode** + +| 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 | 10.6 | +| | | | 10 | 15 | Scenario X | G-FR1-A4-31 | 11.2 | +| | | | 10 | 30 | Scenario X | G-FR1-A4-32A | 10.8 | +| | | | 40 | 30 | Scenario X | G-FR1-A4-32 | 12.0 | + +**Table 8.2.5.2-2 Minimum requirements for UL timing adjustment with mapping type B for normal mode** + +| 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 | 10.6 | +| | | | 10 | 15 | Scenario X | G-FR1-A4-31 | 11.3 | +| | | | 10 | 30 | Scenario X | G-FR1-A4-32A | 10.7 | +| | | | 40 | 30 | Scenario X | G-FR1-A4-32 | 12.4 | + +## 8.2.6 Requirements for PUSCH 0.001% BLER + +### 8.2.6.1 General + +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. + +**Table: 8.2.6.1-1 Test parameters for testing PUSCH 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 | +| | 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 | +| Note 1: The same requirements are applicable to FDD and TDD with different UL-DL patterns. | | | + +### 8.2.6.2 Minimum requirements + +The BLER shall be equal to or smaller than the BLER stated in tables 8.2.6.2-1 to 8.2.6.2-8 at the given SNR for 1Tx. FRCs are defined in annex A. Unless stated otherwise, the MIMO correlation matrices for the gNB are defined in annex G for low correlation. + +**Table 8.2.6.2-1: Minimum 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 (Annex G) | BLER | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|----------------------------------|--------|---------------|---------------------------|----------| +| 1 | 2 | Normal | AWGN | 0.001% | G-FR1-A3A-1 | pos1 | -5.1 | + +**Table 8.2.6.2-2: Minimum 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 (Annex G) | BLER | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|----------------------------------|--------|---------------|---------------------------|----------| +| 1 | 2 | Normal | AWGN | 0.001% | G-FR1-A3A-2 | pos1 | -5.9 | + +**Table 8.2.6.2-3: Minimum 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 (Annex G) | BLER | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|----------------------------------|--------|---------------|---------------------------|----------| +| 1 | 2 | Normal | AWGN | 0.001% | G-FR1-A3A-3 | pos1 | -5.4 | + +**Table 8.2.6.2-4: Minimum 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 (Annex G) | BLER | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|----------------------------------|--------|---------------|---------------------------|----------| +| 1 | 2 | Normal | AWGN | 0.001% | G-FR1-A3A-4 | pos1 | -6.2 | + +**Table 8.2.6.2-5: Minimum 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 (Annex G) | BLER | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|----------------------------------|--------|---------------|---------------------------|----------| +| 1 | 2 | Normal | AWGN | 0.001% | G-FR1-A3A-1 | pos1 | -5.2 | + +**Table 8.2.6.2-6: Minimum 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 (Annex G) | BLER | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|----------------------------------|--------|---------------|---------------------------|----------| +| 1 | 2 | Normal | AWGN | 0.001% | G-FR1-A3A-2 | pos1 | -5.9 | + +**Table 8.2.6.2-7: Minimum 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 (Annex G) | BLER | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|----------------------------------|--------|---------------|---------------------------|----------| +| 1 | 2 | Normal | AWGN | 0.001% | G-FR1-A3A-3 | pos1 | -5.4 | + +**Table 8.2.6.2-8: Minimum 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 (Annex G) | BLER | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|----------------------------------|--------|---------------|---------------------------|----------| +| 1 | 2 | Normal | AWGN | 0.001% | G-FR1-A3A-4 | pos1 | -6.2 | + +## 8.2.7 Requirements for PUSCH repetition Type A + +### 8.2.7.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.7.1-1 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 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. | | | +| 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. | | | + +## 8.2.7.2 Minimum requirements + +The BLER shall be equal to or smaller than the required target BLER for the FRCs stated in tables 8.2.7.2-1 to 8.2.7.2-8 at the given SNR for 1Tx. FRCs are defined in annex A. + +**Table 8.2.7.2-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 | -8.4 | +| 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.2-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 | -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.2-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.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.2-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 | -11.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.2-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 | -8.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.2-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 | -10.1 | +| 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.2-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.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.2-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 | -11.4 | +| 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 Requirements for PUSCH mapping Type B with non-slot transmission + +### 8.2.8.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 do not assume HARQ retransmissions. + +**Table: 8.2.8.1-1 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 | +| | Additional DM-RS position | Pos0 | +| | 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 | B | +| | Start symbol | 0 | +| | Allocation length | 2 | +| 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. | | | + +### 8.2.8.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.4.8-1 to 8.2.4.8-4 at the given SNR for 1Tx. FRCs are defined in annex A. Unless stated otherwise, the MIMO correlation matrices for the gNB are defined in annex G for low correlation. + +**Table 8.2.8.2-1: Minimum requirements for PUSCH with 2 symbols, Type B, 5 MHz channel bandwidth, 15 kHz SCS** + +| 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-100 | 70 % | G-FR1-A3B-1 | pos0 | 0.5 | + +**Table 8.2.8.2-2: Minimum requirements for PUSCH with 2 symbols, Type B, 10 MHz channel bandwidth, 15 kHz SCS** + +| 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-100 | 70 % | G-FR1-A3B-2 | pos0 | 0.3 | + +**Table 8.2.8.2-3: Minimum requirements for PUSCH with 2 symbols, Type B, 10 MHz channel bandwidth, 30 kHz SCS** + +| 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-100 | 70 % | G-FR1-A3B-3 | pos0 | 0.3 | + +**Table 8.2.8.2-4: Minimum requirements for PUSCH with 2 symbols, Type B, 40 MHz channel bandwidth, 30 kHz SCS** + +| 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-100 | 70 % | G-FR1-A3B-4 | pos0 | 0.0 | + +## 8.2.9 Requirements of PUSCH for 2-step RA type + +### 8.2.9.1 General + +The performance requirement of PUSCH for 2-step RA type is determined by a minimum required block error rate of MsgA received by BS at given SNR for the FRCs listed in Annex A. The performance requirements assume that the precedent preamble of MsgA is correctly detected in a 2-step RA type procedure, and no HARQ retransmissions. + +The performance requirements are applicable for wide area and medium range BS that support 2-step RA type. + +The performance requirements are not applied for a local area BS that supports 2-step RA type. + +**Table 8.2.9.1-1 Test parameters for testing 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
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:end: 15k SCS: 0:3.8
30k SCS: 0:2 | +| Test Metric | BLER: 0.01 | +| NOTE 1: A single requirement is defined that is applicable regardless of whether pos1 or pos2 is configured for the additional DM-RS position | | +| NOTE 2: 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 | | + +### 8.2.9.2 Minimum requirements + +The block error rate of MsgA for the reference measurement channel as specified in Annex A at the SNR given shall not exceed 1% in table 8.2.9.2-1 for mapping type A and table 8.2.9.2-2 for mapping type B respectively. + +**Table 8.2.9.2-1 Minimum requirements of PUSCH for 2-step RA type with mapping type A** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Mapping Type | TO cycling (start:end) [ $\mu\text{s}$ ] | Channel Bandwidth [MHz] | SCS [kHz] | Propagation conditions and correlation matrix (Annex G) | FRC (Annex A) | SNR [dB] | +|-----------------------|-----------------------|---------------|--------------|------------------------------------------|-------------------------|-----------|---------------------------------------------------------|---------------------------------|----------| +| 1 | 2 | Normal | Type A | 0:3.8 | 10 | 15 | TDLC300-100 low | G-FR1-A8-1,
or
G-FR1-A8-3 | 7.3 | +| | | | | 0:2 | 40 | 30 | TDLC300-100 low | G-FR1-A8-2,
or
G-FR1-A8-4 | 7.1 | + +**Table 8.2.9.2-2 Minimum requirements of PUSCH for 2-step RA type with mapping type B** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Mapping Type | TO cycling (start:end) [ $\mu\text{s}$ ] | Channel Bandwidth [MHz] | SCS [kHz] | Propagation conditions and correlation matrix (Annex G) | FRC (Annex A) | SNR [dB] | +|-----------------------|-----------------------|---------------|--------------|------------------------------------------|-------------------------|-----------|---------------------------------------------------------|---------------------------------|----------| +| 1 | 2 | Normal | Type B | 0:3.8 | 10 | 15 | TDLC300-100 low | G-FR1-A8-1,
or
G-FR1-A8-3 | 7.0] | +| | | | | 0:2 | 40 | 30 | TDLC300-100 low | G-FR1-A8-2,
or
G-FR1-A8-4 | 7.6 | + +## 8.2.10 Requirements for interlaced PUSCH + +### 8.2.10.1 General + +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. + +**Table 8.2.10.1-1: 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. | | | + +## 8.2.10.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.10.2-1 to 8.2.10.2-4 at the given SNR. FRCs are defined in annex A. + +**Table 8.2.10.2-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.3 | + +**Table 8.2.10.2-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.2 | + +**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.3 | + +**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.2 | + +## 8.2.11 Performance requirements for CG-UCI multiplexed on interlaced PUSCH + +### 8.2.11.1 General + +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 HARQ/ACK, CSI part 1 or CSI part 2 information transmitted. + +The number of UCI information bit payload per slot is defined as 18 bits. + +The 18 bits UCI information case is further defined with the bitmap [c0 c1 c2 c3 c4 ... c17] for CG-UCI information, where + +- [c0 c1 c2 c3] = [0 0 0 1] is mapping to the HARQ process number information, +- [c4 c5] = [0 0] is mapping to the RV sequence information. +- [c6] = [1] is mapping to the NDI information. +- [c7 c8 ... c17] = [0 0 ... 0] is the COT sharing information field. + +In the test, PUSCH data and CG-UCI are transmitted simultaneously. + +**Table 8.2.11.1-1: Test parameters for testing CG-UCI on interlaced PUSCH** + +| Parameter | | Value | +|-------------------------------------------|-------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Transform precoding | | Disabled | +| Default TDD UL-DL pattern | | 30 kHz SCS:
7D1S2U, S=6D:4G:4U

15 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 | +| | 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 | +| PT-RS | | Disabled | +| UCI | Number of information bits | 18 | +| | scaling | 1 | +| | betaOffsetCG-UCI-Index1 | 8 | +| | UCI partition for frequency hopping | Disabled | + +## 8.2.11.2 Minimum requirements + +The fraction of incorrectly decoded CG-UCI according to clause 8.2.11.1 shall be less than 1 % for the SNR listed in table 8.2.11.2-1 to 8.2.11.2-4 + +**Table 8.2.11.2-1: Minimum requirements for CG-UCI multiplexing on interlaced 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 | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|-------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLA30-10 Low | 18 | G-FR1-A5-15 | pos1 | 4.6 | + +**Table 8.2.11.2-2: Minimum requirements for CG-UCI multiplexing 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 | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|-------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLA30-10 Low | 18 | G-FR1-A5-16 | pos1 | 4.7 | + +**Table 8.2.11.2-3: Minimum requirements for CG-UCI multiplexing 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 | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|-------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLA30-10 Low | 18 | G-FR1-A5-15 | pos1 | 4.6 | + +**Table 8.2.11.2-4: Minimum requirements for CG-UCI multiplexing 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 | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|-------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLA30-10 Low | 18 | G-FR1-A5-16 | pos1 | 5.0 | + +## 8.2.12 Requirements for TB processing over multi-slot PUSCH (TBoMS) + +### 8.2.12.1 General + +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. + +**Table: 8.2.12.1-1 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. | | | + +### 8.2.12.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.12.2-1 to 8.2.12.2-4 at the given SNR. FRCs are defined in annex A. + +**Table 8.2.12.2-1: Minimum 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 | -2.3 | +| 1 | 2 | Normal | TDD | TDLB100-400 Low | 70% | G-FR1-A3-35 | pos1 | -2.5 | + +**Table 8.2.12.2-2: Minimum 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 | -2.4 | +| 1 | 2 | Normal | TDD | TDLB100-400 Low | 70% | G-FR1-A3-37 | pos1 | -2.5 | + +**Table 8.2.12.2-3: Minimum 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 | -2.1 | +| 1 | 2 | Normal | TDD | TDLB100-400 Low | 70% | G-FR1-A3-35 | pos1 | -2.5 | + +**Table 8.2.12.2-4: Minimum 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 | -2.4 | +| 1 | 2 | Normal | TDD | TDLB100-400 Low | 70% | G-FR1-A3-37 | pos1 | -2.5 | + +## 8.2.13 Requirements for PUSCH with DM-RS bundling + +### 8.2.13.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 re-transmissions. + +**Table: 8.2.13.1-1 Test parameters for testing PUSCH with DM-RS bundling** + +| Parameter | | Value | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------|------------------------------------------------------------------------------------------------| +| Transform precoding | | Disabled | +| Example UL-DL pattern [Note 1] | | 15 kHz SCS: FDD and TDD
7D1S2U, S=6D:4G:4U
30 kHz SCS: FDD and TDD
7D1S2U, S=6D:4G:4U | +| HARQ | Maximum number of HARQ transmissions | 4 | +| | RV sequence [Note 2] | 0, 0, 0, 0 for FDD
0, 3, 0, 3 for TDD | +| 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 | 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 | n8 for FDD
n2 for TDD | +| pusch-TimeDomainWindowLength | | 8 slots for FDD
2 slots for TDD | +| 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. | | | + +## 8.2.13.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.13.2-1 to 8.2.13.2-8 at the given SNR for 1Tx. FRCs are defined in annex A. + +**Table 8.2.13.2-1: Minimum requirements for PUSCH, Type A, 5 MHz channel bandwidth, 15 kHz SCS FDD** + +| 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 | -7.9 | +| | | | | | G-FR1-A3B-5 | pos1 | -9.9 | +| | 4 | Normal | TDLA30-10 Low | 70% | G-FR1-A3B-7 | pos0 | -11.8 | +| | | | | | G-FR1-A3B-5 | pos1 | -12.3 | +| | 8 | Normal | TDLA30-10 Low | 70% | G-FR1-A3B-7 | pos0 | -15.0 | +| | | | | | G-FR1-A3B-5 | pos1 | -15.6 | + +**Table 8.2.13.2-2: Minimum requirements for PUSCH, Type A, 5 MHz channel bandwidth, 15 kHz SCS TDD** + +| 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.6 | +| | | | | | G-FR1-A3B-5 | pos1 | -3.6 | +| | 4 | Normal | TDLA30-10 Low | 70% | G-FR1-A3B-7 | pos0 | -6.2 | +| | | | | | G-FR1-A3B-5 | pos1 | -6.8 | +| | 8 | Normal | TDLA30-10 Low | 70% | G-FR1-A3B-7 | pos0 | -9.4 | +| | | | | | G-FR1-A3B-5 | pos1 | -10.6 | + +**Table 8.2.13.2-3: Minimum requirements for PUSCH, Type A, 10 MHz channel bandwidth, 30 kHz SCS FDD** + +| 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 | -9.8 | +| | | | | | G-FR1-A3B-6 | pos1 | -9.5 | +| | 4 | Normal | TDLA30-10 Low | 70% | G-FR1-A3B-8 | pos0 | -13.0 | +| | | | | | G-FR1-A3B-6 | pos1 | -13.1 | +| | 8 | Normal | TDLA30-10 Low | 70% | G-FR1-A3B-8 | pos0 | -15.3 | +| | | | | | G-FR1-A3B-6 | pos1 | -15.8 | + +**Table 8.2.13.2-4: Minimum requirements for PUSCH, Type A, 10 MHz channel bandwidth, 30 kHz SCS TDD** + +| 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.9 | +| | | | | | G-FR1-A3B-6 | pos1 | -3.8 | +| | 4 | Normal | TDLA30-10 Low | 70% | G-FR1-A3B-8 | pos0 | -6.5 | +| | | | | | G-FR1-A3B-6 | pos1 | -7.0 | +| | 8 | Normal | TDLA30-10 Low | 70% | G-FR1-A3B-8 | pos0 | -9.7 | +| | | | | | G-FR1-A3B-6 | pos1 | -10.3 | + +**Table 8.2.13.2-5: Minimum requirements for PUSCH, Type B, 5 MHz channel bandwidth, 15 kHz SCS FDD** + +| 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 | -8.3 | +| | | | | | G-FR1-A3B-5 | pos1 | -9.9 | +| | 4 | Normal | TDLA30-10 Low | 70% | G-FR1-A3B-7 | pos0 | -11.8 | +| | | | | | G-FR1-A3B-5 | pos1 | -12.3 | +| | 8 | Normal | TDLA30-10 Low | 70% | G-FR1-A3B-7 | pos0 | -15.0 | +| | | | | | G-FR1-A3B-5 | pos1 | -15.6 | + +**Table 8.2.13.2-6: Minimum requirements for PUSCH, Type B, 5 MHz channel bandwidth, 15 kHz SCS TDD** + +| 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.6 | +| | | | | | G-FR1-A3B-5 | pos1 | -3.4 | +| | 4 | Normal | TDLA30-10 Low | 70% | G-FR1-A3B-7 | pos0 | -6.3 | +| | | | | | G-FR1-A3B-5 | pos1 | -6.8 | +| | 8 | Normal | TDLA30-10 Low | 70% | G-FR1-A3B-7 | pos0 | -9.4 | +| | | | | | G-FR1-A3B-5 | pos1 | -10.6 | + +**Table 8.2.13.2-7: Minimum requirements for PUSCH, Type B, 10 MHz channel bandwidth, 30 kHz SCS FDD** + +| 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 | -9.8 | +| | | | | | G-FR1-A3B-6 | pos1 | -9.5 | +| | 4 | Normal | TDLA30-10 Low | 70% | G-FR1-A3B-8 | pos0 | -13.3 | +| | | | | | G-FR1-A3B-6 | pos1 | -13.1 | +| | 8 | Normal | TDLA30-10 Low | 70% | G-FR1-A3B-8 | pos0 | -15.5 | +| | | | | | G-FR1-A3B-6 | pos1 | -15.8 | + +**Table 8.2.13.2-8: Minimum requirements for PUSCH, Type B, 10 MHz channel bandwidth, 30 kHz SCS TDD** + +| 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.8 | +| | | | | | G-FR1-A3B-6 | pos1 | -3.3 | +| | 4 | Normal | TDLA30-10 Low | 70% | G-FR1-A3B-8 | pos0 | -6.5 | +| | | | | | G-FR1-A3B-6 | pos1 | -7.0 | +| | 8 | Normal | TDLA30-10 Low | 70% | G-FR1-A3B-8 | pos0 | -9.7 | +| | | | | | G-FR1-A3B-6 | pos1 | -10.3 | + +## 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: + +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: + +## 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 | 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 | + +The transient period as specified in TS 38.101-1 [17] clause 6.3.3.1 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 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 | TDLC300-100 Low | 1 | 9.4 | 8.8 | 9.3 | +| | | | 2 | 2.8 | 3.7 | 3.3 | +| 1 | 4 | TDLC300-100 Low | 1 | 3.0 | 2.9 | 3.2 | +| | | | 2 | -1.0 | -0.5 | -0.8 | +| 1 | 8 | TDLC300-100 Low | 1 | -1.1 | -1.1 | -1.1 | +| | | | 2 | -4.1 | -3.9 | -4.0 | + +**Table 8.3.2.2-2: Minimum 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 | TDLC300-100 Low | 1 | 9.8 | 9.8 | 9.5 | 9.2 | +| | | | 2 | 4.2 | 3.6 | 3.8 | 3.5 | +| 1 | 4 | TDLC300-100 Low | 1 | 3.4 | 3.4 | 3.0 | 3.3 | +| | | | 2 | -0.3 | -0.4 | -0.5 | -0.8 | +| 1 | 8 | TDLC300-100 Low | 1 | -1.0 | -1.0 | -1.1 | -1.0 | +| | | | 2 | -3.7 | -3.8 | -4.0 | -3.9 | + +### 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-1 [17] clause 6.3.3.1 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 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.8 | -3.6 | -3.6 | +| | 4 | Normal | TDLC-300-100 Low | -8.4 | -7.6 | -8.4 | +| | 8 | Normal | TDLC-300-100 Low | -11.8 | -11.4 | -11.4 | + +**Table 8.3.3.1.2-2: Minimum requirements 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.8 | -3.3 | -3.9 | -3.5 | +| | 4 | Normal | TDLC-300-100 Low | -8.1 | -8.3 | -7.5 | -8.0 | +| | 8 | Normal | TDLC-300-100 Low | -11.5 | -11.2 | -11.6 | -11.3 | + +### 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-1 [17] clause 6.3.3.1 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 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 | -5.0 | -4.4 | -5.0 | +| | 4 | Normal | TDLC-300-100 Low | -8.6 | -8.2 | -8.5 | +| | 8 | Normal | TDLC-300-100 Low | -11.6 | -11.5 | -11.5 | + +**Table 8.3.3.2.2-2: Minimum requirements 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 | -3.9 | -4.4 | -4.4 | -4.2 | +| | 4 | Normal | TDLC-300-100 Low | -8.0 | -8.1 | -8.4 | -8.3 | +| | 8 | Normal | TDLC-300-100 Low | -11.4 | -11.4 | -11.4 | -11.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. + +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 | +| 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$ | + +#### 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 4UCI bits. + +**Table 8.3.4.1.2-1: Minimum requirements 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 | 5.8 | 5.6 | 5.9 | +| | 4 | Normal | TDLC300-100 Low | 0.4 | 0.5 | 0.3 | +| | 8 | Normal | TDLC300-100 Low | -3.5 | -3.5 | -3.5 | + +**Table 8.3.4.1.2-2: Minimum requirements 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) | | | | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|------------------------------|--------|--------|---------| +| | | | | 10 MHz | 20 MHz | 40 MHz | 100 MHz | +| 1 | 2 | Normal | TDLC300-100 Low | 5.5 | 5.6 | 5.5 | 5.7 | +| | 4 | Normal | TDLC300-100 Low | 0.3 | 0.2 | 0.3 | 0.4 | +| | 8 | Normal | TDLC300-100 Low | -3.6 | -3.6 | -3.5 | -3.3 | + +### 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 part 2. + +The transient period as specified in TS 38.101-1 [17] clause 6.3.3.1 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 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.2 | 0.8 | 1.2 | +| | 4 | Normal | TDLC300-100 Low | -3.6 | -3.2 | -3.2 | +| | 8 | Normal | TDLC300-100 Low | -6.8 | -6.7 | -6.8 | + +**Table 8.3.4.2.2-2: Minimum requirements 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) | | | | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|------------------------------|--------|--------|---------| +| | | | | 10 MHz | 20 MHz | 40 MHz | 100 MHz | +| 1 | 2 | Normal | TDLC300-100 Low | 0.5 | 1.1 | 0.4 | 0.3 | +| | 4 | Normal | TDLC300-100 Low | -3.3 | -2.9 | -3.3 | -3.4 | +| | 8 | Normal | TDLC300-100 Low | -5.8 | -5.8 | -6.7 | -5.9 | + +## 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 part 2. + +The transient period as specified in TS 38.101-1 [17] clause 6.3.3.1 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 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 | + +### 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 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.2 | 1.1 | 0.3 | +| | | | | | Additional DM-RS | -0.1 | 0.5 | -0.1 | +| | | 4 | Normal | TDLC300-100 Low | No additional DM-RS | -3.8 | -3.3 | -3.8 | +| | | | | | Additional DM-RS | -4.3 | -4.0 | -4.0 | +| | | 8 | Normal | TDLC300-100 Low | No additional DM-RS | -7.0 | -6.7 | -6.9 | +| | | | | | Additional DM-RS | -7.7 | -7.5 | -7.7 | +| | | 2 | Normal | TDLC300-100 Low | No additional DM-RS | 1.4 | 2.2 | 2.0 | +| 2 | 1 | 2 | Normal | TDLC300-100 Low | No additional DM-RS | 1.4 | 2.2 | 2.0 | +| | | 4 | Normal | TDLC300-100 Low | No additional DM-RS | -3.1 | -2.5 | -2.5 | +| | | 8 | Normal | TDLC300-100 Low | No additional DM-RS | -6.5 | -6.0 | -6.2 | + +**Table 8.3.5.2-2: Minimum requirements 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 | 0.9 | 0.6 | 0.6 | 0.9 | +| | | | | | Additional DM-RS | 0.5 | 0.3 | 0.0 | 0.1 | +| | | 4 | Normal | TDLC300-100 Low | No additional DM-RS | -3.1 | -3.4 | -3.2 | -3.5 | +| | | | | | Additional DM-RS | -3.7 | -4.1 | -4.0 | -4.2 | +| | | 8 | Normal | TDLC300-100 Low | No additional DM-RS | -6.6 | -6.7 | -6.8 | -6.8 | +| | | | | | Additional DM-RS | -7.5 | -7.6 | -7.6 | -7.7 | +| | | 2 | Normal | TDLC300-100 Low | No additional DM-RS | 1.8 | 2.0 | 2.0 | 1.5 | +| 2 | 1 | 2 | Normal | TDLC300-100 Low | No additional DM-RS | 1.8 | 2.0 | 2.0 | 1.5 | +| | | 4 | Normal | TDLC300-100 Low | No additional DM-RS | -2.9 | -3.0 | -2.4 | -3.0 | +| | | 8 | Normal | TDLC300-100 Low | No additional DM-RS | -6.4 | -6.0 | -6.4 | -6.2 | + +## 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 part 2. + +The transient period as specified in TS 38.101-1 [17] clause 6.3.3.1 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: 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 | 1.8 | 2.6 | 2.2 | +| | | | | Additional DM-RS | 1.6 | 2.4 | 1.8 | +| | 4 | Normal | TDLC300-100 Low | No additional DM-RS | -2.3 | -1.9 | -2.2 | +| | | | | Additional DM-RS | -2.9 | -2.6 | -2.7 | +| | | | | No additional DM-RS | -5.9 | -5.7 | -5.8 | +| | | | | Additional DM-RS | -6.6 | -6.4 | -6.3 | +| | 8 | Normal | TDLC300-100 Low | No additional DM-RS | -5.9 | -5.7 | -5.8 | +| | | | | Additional DM-RS | -6.6 | -6.4 | -6.3 | + +**Table 8.3.6.2-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.1 | 2.8 | 3.1 | 2.8 | +| | | | | Additional DM-RS | 2.8 | 2.3 | 3.1 | 2.2 | +| | 4 | Normal | TDLC300-100 Low | No additional DM-RS | -1.7 | -1.9 | -1.7 | -2.1 | +| | | | | Additional DM-RS | -2.0 | -2.5 | -2.5 | -2.4 | +| | | | | No additional DM-RS | -5.6 | -5.5 | -5.5 | -5.5 | +| | | | | Additional DM-RS | -6.2 | -6.1 | -6.4 | -6.2 | +| | 8 | Normal | TDLC300-100 Low | No additional DM-RS | -5.6 | -5.5 | -5.5 | -5.5 | +| | | | | Additional DM-RS | -6.2 | -6.1 | -6.4 | -6.2 | + +## 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 an NACK bit was sent on the particular bit position, where the NACK to ACK detection probability is defined as follows: + +$$\text{Prob(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. + +**Table 8.3.7.2.1.2-1: Minimum requirements for multi-slot PUCCH format 1 with 30kHz 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 | -6.3 | + +### 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. + +**Table 8.3.7.2.2.2-1: Minimum requirements for multi-slot PUCCH format 1 with 30kHz 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.6 | + +## 8.3.8 Performance requirements for interlaced PUCCH format 0 + +### 8.3.8.1 General + +The ACK missed detection probability is the probability of not detecting an ACK when an ACK was sent. + +The ACK missed detection probability performance requirement only apply to PUCCH format 0 with 1 UCI bit. The UCI information only contain ACK information. + +The 1bit UCI information is further defined with the bitmap as [1]. + +**Table 8.3.8.1-1: 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 | 0Note1 | +| NOTE 1: RBs 0,10,20,..., 100 are allocated for 15kHz SCS and RBs 0,5,10,..., 50 are allocated for 30kHz SCS | | + +### 8.3.8.2 Minimum requirements + +The ACK missed detection probability shall not exceed 1% at the SNR given in table 8.3.8.2-1 + +**Table 8.3.8.2-1: Minimum 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.8 | + +**Table 8.3.8.2-2: Minimum 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 | -2.0 | + +## 8.3.9 Performance requirements for interlaced PUCCH format 1 + +### 8.3.9.1 NACK to ACK requirements + +#### 8.3.9.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. + +The NACK to ACK detection probability performance requirement only apply to PUCCH format 1 with 2 UCI bits. The UCI information only contain ACK/NACK information. + +The 2bits UCI information is further defined with bitmap as [0 1]. + +**Table 8.3.9.1.1-1: 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 | | + +#### 8.3.9.1.2 Minimum requirements + +The NACK to ACK probability shall not exceed 0.1% at the SNR given in table 8.3.9.1.2-1. + +**Table 8.3.9.1.2-1: Minimum requirements 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.9.1.2-2: Minimum requirements 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.3 | + +### 8.3.9.2 ACK missed detection requirements + +#### 8.3.9.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.9.1.1-1 are configured. + +The ACK missed detection probability performance requirement only apply to PUCCH format 1 with 2 UCI bits. The UCI information only contain ACK/NACK information. + +The 2bits UCI information is further defined with bitmap as [0 1]. + +#### 8.3.9.2.2 Minimum requirements + +The ACK missed detection probability shall not exceed 1% at the SNR given in table 8.3.9.2.2-1. + +**Table 8.3.9.2.2-1: Minimum requirements 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 | -14.4 | + +**Table 8.3.9.2.2-2: Minimum requirements 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 | -14.1 | + +## 8.3.10 Performance requirements for interlaced PUCCH format 2 + +### 8.3.10.1 General + +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. + +**Table 8.3.10.1-1: 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 | | + +### 8.3.10.2 Minimum requirements + +The UCI block error probability shall not exceed 1% at the SNR given in table 8.3.10.2-1 and table 8.3.10.2-2 for 22 UCI bits. + +**Table 8.3.10.2-1: Minimum requirements 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 | 3.5 | + +**Table 8.3.10.2-2: Minimum requirements 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 | 3.9 | + +## 8.3.11 Performance requirements for interlaced PUCCH format 3 + +### 8.3.11.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 3 with 4 UCI bits. The UCI information only contains ACK information. + +The 4 bits UCI information case is further defined with the bitmap as [1 1 1 1]. + +**Table 8.3.11.1-1: 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 | | + +### 8.3.11.2 Minimum requirements + +The ACK missed detection probability shall not exceed 1% at the SNR given in table 8.3.11.2-1 and table 8.3.11.2-2 for 4UCI bits. + +**Table 8.3.11.2-1: Minimum requirements 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 | -6 | + +**Table 8.3.11.2-2: Minimum requirements 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 | -5.4 | + +## 8.3.12 Performance requirements for PUCCH format 1 with DM-RS bundling + +### 8.3.12.1 NACK to ACK requirements + +#### 8.3.12.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. + +The NACK to ACK detection probability performance requirement only apply to PUCCH format 1 with 2 UCI bits. The UCI information only contain ACK/NACK information. + +The 2bits UCI information is further defined with bitmap as [0 1]. + +**Table 8.3.12.1.1-1: Test Parameters** + +| Parameter | Test 1 | Test 2 | +|---------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------| +| Example TDD UL-DL pattern (Note1) | 15 kHz SCS:
7D1S2U, S=6D:4G:4U
30 kHz SCS: TDD
7D1S2U, S=6D:4G:4U | 15 kHz SCS: FDD
30 kHz SCS: FDD | +| Number of information bits | 2 | 2 | +| Number of PRBs | 1 | 1 | +| Number of symbols | 14 | 14 | +| First PRB prior to frequency hopping | 0 | 0 | +| Intra-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. | | + +#### 8.3.12.1.2 Minimum requirements + +The NACK to ACK probability shall not exceed 0.1% at the SNR given in table 8.3.12.1.2-1 and table 8.3.12.1.2-2 + +**Table 8.3.12.1.2-1: Minimum requirements for PUCCH format 1 with DMRS bundling, 15 kHz SCS, 5MHz channel bandwidth,** + +| Test number | Number of Tx antennas | Number of RX antennas | Cyclic-Prefix | Propagation conditions and correlation matrix (Annex G) | SNR (dB) | +|-------------|-----------------------|-----------------------|---------------|---------------------------------------------------------|----------| +| 1 | 1 | 2 | Normal | TDLA30-10 Low | -3.0 | +| 2 | 1 | 2 | Normal | TDLA30-10 Low | -9.1 | + +**Table 8.3.12.1.2-2: Minimum requirements for PUCCH format 1 with DMRS bundling, 30 kHz SCS, 10MHz channel bandwidth,** + +| Test number | Number of Tx antennas | Number of RX antennas | Cyclic-Prefix | Propagation conditions and correlation matrix (Annex G) | SNR (dB) | +|-------------|-----------------------|-----------------------|---------------|---------------------------------------------------------|----------| +| 1 | 1 | 2 | Normal | TDLA30-10 Low | -3.0 | +| 2 | 1 | 2 | Normal | TDLA30-10 Low | -8.7 | + +## 8.3.12.2 ACK missed detection requirements + +### 8.3.12.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.12.1.1-1 are configured. + +The ACK missed detection probability performance requirement only apply to PUCCH format 1 with 2 UCI bits. The UCI information only contain ACK/NACK information. + +The 2bits UCI information is further defined with bitmap as [0 1]. + +### 8.3.12.2.2 Minimum requirements + +The ACK missed detection probability shall not exceed 1% at the SNR given in table 8.3.12.2.2-1 and table 8.3.12.2.2-2 + +**Table 8.3.12.2.2-1: Minimum requirements for PUCCH format 1 with DMRS bundling, 15 kHz SCS, 5MHz channel bandwidth,** + +| Test number | Number of Tx antennas | Number of RX antennas | Cyclic-Prefix | Propagation conditions and correlation matrix (Annex G) | SNR (dB) | +|-------------|-----------------------|-----------------------|---------------|---------------------------------------------------------|----------| +| 1 | 1 | 2 | Normal | TDLA30-10 Low | -3.9 | +| 2 | 1 | 2 | Normal | TDLA30-10 Low | -8.9 | + +**Table 8.3.12.2.2-2: Minimum requirements for PUCCH format 1 with DMRS bundling, 30 kHz SCS, 10MHz channel bandwidth,** + +| Test number | Number of Tx antennas | Number of RX antennas | Cyclic-Prefix | Propagation conditions and correlation matrix (Annex G) | SNR (dB) | +|-------------|-----------------------|-----------------------|---------------|---------------------------------------------------------|----------| +| 1 | 1 | 2 | Normal | TDLA30-10 Low | -3.8 | +| 2 | 1 | 2 | Normal | TDLA30-10 Low | -8.5 | + +## 8.3.13 Performance requirements for PUCCH format 3 with DMRS bundling + +### 8.3.13.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 part 2. + +**Table 8.3.13.1-1: Test Parameters** + +| Parameter | Test 1 | Test 2 | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------|------------------------------------| +| Example TDD UL-DL pattern (Note1) | 15 kHz SCS:
7D1S2U, S=6D:4G:4U
30 kHz SCS: TDD
7D1S2U, S=6D:4G:4U | 15 kHz SCS: FDD
30 kHz SCS: FDD | +| Modulation order | QPSK | QPSK | +| First PRB prior to frequency hopping | 0 | 0 | +| Intra-slot frequency hopping | disabled | disabled | +| Group and sequence hopping | neither | neither | +| Hopping ID | 0 | 0 | +| 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. | | | + +### 8.3.13.2 Minimum requirements + +The UCI block error probability shall not exceed 1% at the SNR given in Table 8.3.13.2-1 and Table 8.3.13.2-2. + +**Table 8.3.13.2-1: Minimum requirements for PUCCH format 3 with DMRS bundling, 15 kHz SCS, 5MHz channel bandwidth** + +| 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.3 | +| | | | | | Additional DM-RS | -0.1 | +| 2 | 1 | 2 | Normal | TDLA30-10 Low | No additional DM-RS | -5.3 | +| | | | | | Additional DM-RS | -5.8 | + +**Table 8.3.13.2-2: Minimum requirements for PUCCH format 3 with DMRS bundling, 30 kHz SCS, 10MHz channel bandwidth** + +| 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.2 | +| | | | | | Additional DM-RS | 0.0 | +| 2 | 1 | 2 | Normal | TDLA30-10 Low | No additional DM-RS | -5.2 | + +| | | | | | | | +|--|--|--|--|--|------------------|------| +| | | | | | Additional DM-RS | -5.6 | +|--|--|--|--|--|------------------|------| + +## 8.3.14 Performance requirements for sub-slot repetition PUCCH format 0 + +### 8.3.14.1 General + +The ACK missed detection probability is the probability of not detecting an ACK when an ACK was sent. + +The ACK missed detection probability performance requirement only apply to PUCCH format 0 with 1 UCI bit. The UCI information only contain ACK information. + +The 1bit UCI information is further defined with the bitmap as [1]. + +**Table 8.3.14.1-1: 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 | + +The transient period as specified in TS 38.101-1 [17] clause 6.3.3.1 is not taken into account for performance requirement testing, where the RB hopping is symmetric to the CC centre, i.e., inter-slot frequency hopping is enabled. + +### 8.3.14.2 Minimum requirements + +The ACK missed detection probability shall not exceed 1% at the SNR given in table 8.3.14.2-1 + +**Table 8.3.14.2-1: Minimum requirements for sub-slot repetition PUCCH format 0 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 | 1.5 | + +## 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, 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 given in Table 8.4.2.1-1. + +The performance requirements for high speed train (table 8.4.23-1 to 8.4.2.3-4) are optional. + +**Table 8.4.2.1-1: Time error tolerance for AWGN, TDLC300-100 and TDLA30-10** + +| 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 and the test parameter *msg1-FrequencyStart* is set to 0. The test preambles for high speed train restricted set type A are listed in A.6-3, the test preambles for high speed train restricted set type B are listed in A.6-4, and the test preambles for high speed train short formats are listed in A.6-5. The test parameter *msg1-FrequencyStart* for high speed train is set to 0. + +The test preambles for PRACH with LRA=1151 and LRA=571 are listed in table A.6-6. + +#### 8.4.2.2 Minimum requirements for Normal Mode + +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 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.5 | +| | | TDLC300-100 Low | 400 Hz | -6.6 | +| | 4 | AWGN | 0 | -16.7 | +| | | TDLC300-100 Low | 400 Hz | -11.9 | +| | 8 | AWGN | 0 | -18.9 | +| | | TDLC300-100 Low | 400 Hz | -15.8 | + +**Table 8.4.2.2-2: PRACH missed detection 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.3 | -12.6 | -14.2 | -16.8 | -6.3 | -12.5 | +| | | TDLC300-100 Low | 400 Hz | -2.1 | -4.8 | -6.6 | -8.8 | 0.8 | -4.9 | +| | 4 | AWGN | 0 | -11.6 | -14.3 | -16.0 | -19.0 | -8.7 | -14.1 | +| | | TDLC300-100 Low | 400 Hz | -7.3 | -10.3 | -11.7 | -13.8 | -4.3 | -10.2 | +| | 8 | AWGN | 0 | -13.8 | -16.7 | -18.2 | -21.2 | -11.1 | -16.6 | +| | | TDLC300-100 Low | 400 Hz | -11.0 | -13.9 | -15.2 | -17.3 | -8.1 | -13.9 | + +**Table 8.4.2.2-3: PRACH missed detection 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 | -9.1 | -12.0 | -13.8 | -16.5 | -6.1 | -11.9 | +| | | TDLC300-100 Low | 400 Hz | -2.8 | -5.7 | -7.4 | -9.9 | 0.1 | -5.6 | +| | 4 | AWGN | 0 | -11.4 | -14.2 | -15.9 | -19.0 | -8.6 | -14.1 | +| | | TDLC300-100 Low | 400 Hz | -7.2 | -10.4 | -12.0 | -14.5 | -4.5 | -10.4 | +| | 8 | AWGN | 0 | -13.7 | -16.6 | -18.1 | -21.1 | -11.0 | -16.5 | +| | | TDLC300-100 Low | 400 Hz | -10.7 | -13.7 | -15.1 | -17.6 | -7.8 | -13.7 | + +**Table 8.4.2.2-4: Void****Table 8.4.2.2-5: Void** + +### 8.4.2.3 Minimum requirements for high speed train + +The probability of detection shall be equal to or exceed 99% for the SNR levels listed in Tables 8.4.2.3-1 to 8.4.2.3-4 + +**Table 8.4.2.3-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 | -12.0 | +| | | AWGN | 1340 Hz | -13.8 | +| | | TDLC300-100 Low | 0 Hz | -6.3 | +| | 4 | AWGN | 625 Hz | -14.5 | +| | | AWGN | 1340 Hz | -16.2 | +| | | TDLC300-100 Low | 0 Hz | -11.8 | +| | 8 | AWGN | 625 Hz | -16.5 | +| | | AWGN | 1340 Hz | -18.4 | +| | | TDLC300-100 Low | 0 Hz | -16.2 | + +**Table 8.4.2.3-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.6 | +| | | AWGN | 2334 Hz | -13.1 | +| | | TDLC300-100 Low | 0 Hz | -6.0 | +| | 4 | AWGN | 625 Hz | -14.0 | +| | | AWGN | 2334 Hz | -15.4 | +| | | TDLC300-100 Low | 0 Hz | -11.7 | +| | 8 | AWGN | 625 Hz | -16.3 | +| | | AWGN | 2334 Hz | -17.4 | +| | | TDLC300-100 Low | 0 Hz | -16.0 | + +**Table 8.4.2.3-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.3 | -14.3 | -11.1 | +| | 4 | AWGN | 1740 Hz | -13.5 | -16.7 | -13.4 | +| | 8 | AWGN | 1740 Hz | -15.6 | -18.2 | -15.5 | + +**Table 8.4.2.3-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 | -11.2 | -14.6 | -11.0 | +| | 4 | AWGN | 3334 Hz | -13.4 | -16.7 | -13.4 | +| | 8 | AWGN | 3334 Hz | -15.4 | -18.4 | -15.4 | + +#### 8.4.2.4 Minimum requirements for PRACH with $L_{RA}=1151$ and $L_{RA}=571$ + +The probability of detection shall be equal to or exceed 99% for the SNR levels listed in Tables 8.4.2.4-1 to 8.4.2.4-2. + +**Table 8.4.2.4-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 | -21.4 | -25.4 | -21.4 | +| | | TDLA30-10 Low | 400 Hz | -15.1 | -18.3 | -15.2 | + +**Table 8.4.2.4-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 | -18.4 | -22.3 | -18.4 | +| | | TDLA30-10 Low | 400 Hz | -12.1 | -15.8 | -12.1 | + +## 9 Radiated transmitter characteristics + +### 9.1 General + +Radiated transmitter characteristics requirements apply on the *BS type 1-H*, *BS type 1-O*, or *BS type 2-O* including all its functional components active and for all foreseen modes of operation of the BS unless otherwise stated. + +### 9.2 Radiated transmit power + +#### 9.2.1 General + +*BS type 1-H*, *BS type 1-O* and *BS type 2-O* are declared to support one or more beams, as per manufacturer's declarations specified in TS 38.141-2 [6]. Radiated transmit power is defined as the EIRP level for a declared beam at a specific *beam peak direction*. + +For each beam, the requirement is based on declaration of a beam identity, *reference beam direction pair*, beamwidth, *rated beam EIRP*, *OTA peak directions set*, the *beam direction pairs* at the maximum steering directions and their associated *rated beam EIRP* and beamwidth(s). + +For a declared beam and *beam direction pair*, the *rated beam EIRP* level is the maximum power that the base station is declared to radiate at the associated *beam peak direction* during the *transmitter ON period*. + +For each *beam peak direction* associated with a *beam direction pair* within the *OTA peak directions set*, a specific *rated beam EIRP* level may be claimed. Any claimed value shall be met within the accuracy requirement as described below. *Rated beam EIRP* is only required to be declared for the *beam direction pairs* subject to conformance testing as detailed in TS 38.141-2 [6]. + +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}}$ . + +For *BS type 1-O* there is no requirement specified for bands n46, n96, n100 and n101 and n102. + +#### 9.2.2 Minimum requirement for *BS type 1-H* and *BS 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. + +For *BS type 1-O* only, for each declared beam, in extreme conditions, for any specific *beam peak direction* associated with a *beam direction pair* within the *OTA peak directions set*, a manufacturer claimed EIRP level in the corresponding *beam peak direction* shall be achievable to within $\pm 2.7$ dB of the claimed value. + +Normal and extreme conditions are defined in TS 38.141-2, annex B [6]. + +In certain regions, the minimum requirement for normal conditions may apply also for some conditions outside the range of conditions defined as normal. + +### 9.2.3 Minimum requirement for *BS type 2-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 3.4$ dB of the claimed value. + +For each declared beam, in extreme conditions, for any specific *beam peak direction* associated with a *beam direction pair* within the *OTA peak directions set*, a manufacturer claimed EIRP level in the corresponding *beam peak direction* shall be achievable to within $\pm 4.5$ dB of the claimed value. + +Normal and extreme conditions are defined in TS 38.141-2, annex B [6]. + +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 base station output power + +### 9.3.1 General + +OTA BS 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*. + +The BS *rated carrier TRP output power* for *BS type 1-O* shall be within limits as specified in table 9.3.1-1. + +**Table 9.3.1-1: BS *rated carrier TRP output power* limits for *BS type 1-O*** + +| BS class | $P_{\text{rated,c,TRP}}$ | +|-----------------------------------------------------------------------------------------------|--------------------------| +| Wide Area BS | (note) | +| Medium Range BS | $\leq +47$ dBm | +| Local Area BS | $\leq +33$ dBm | +| NOTE: There is no upper limit for the $P_{\text{rated,c,TRP}}$ of the Wide Area Base Station. | | + +There is no upper limit for the *rated carrier TRP output power* of *BS type 2-O*. + +For Band n41 and n90 operation in Japan, the rated output power, $P_{\text{rated,c,TRP}}$ , declared by the manufacturer shall be equal to or less than 20 W per 10 MHz bandwidth. + +Despite the general requirements for the BS output power described in clauses 9.3.2 – 9.3.3, additional regional requirements might be applicable. + +NOTE: In certain regions, power limits corresponding to BS classes may apply for *BS type 2-O*. + +### 9.3.2 Minimum requirement for *BS type 1-O* + +In normal conditions, the *BS type 1-O maximum carrier TRP output power*, $P_{\text{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.141-1, annex B [6]. + +### 9.3.3 Minimum requirement for BS type 2-O + +In normal conditions, the *BS type 2-O maximum carrier TRP output power*, $P_{\max,c,TRP}$ measured at the RIB shall remain within $\pm 3$ 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.141-2, annex B [6]. + +### 9.3.4 Additional requirements (regional) + +*In certain regions, additional regional requirements may apply.* + +## 9.4 OTA output power dynamics + +### 9.4.1 General + +The requirements in clause 9.4 apply during the *transmitter ON period*. 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 BS 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 BS type 1-O + +The OTA RE power control dynamic range is specified the same as the conducted RE power control dynamic range requirement for *BS type 1-C* and *BS 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 BS 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 BS type 1-O + +OTA total power dynamic range minimum requirement for *BS 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 *BS type 1-C* and *BS type 1-H* in table 6.3.3.2-1. + +### 9.4.3.3 Minimum requirement for BS type 2-O + +OTA total power dynamic range minimum requirement for BS type 2-O is specified such as for each NR carrier it shall be larger than or equal to the levels specified in table 9.4.3.3-1 in FR2-1 and table 9.4.3.3-2 in FR2-2. + +**Table 9.4.3.3-1: Minimum requirement for BS type 2-O total power dynamic range in FR2-1** + +| SCS
(kHz) | OTA total power dynamic range (dB) | | | | +|--------------|------------------------------------|---------|---------|---------| +| | 50 MHz | 100 MHz | 200 MHz | 400 MHz | +| 60 | 18.1 | 21.2 | 24.2 | N/A | +| 120 | 15.0 | 18.1 | 21.2 | 24.2 | + +**Table 9.4.3.3-2: Minimum requirement for BS type 2-O total power dynamic range in FR2-2** + +| SCS
(kHz) | OTA total power dynamic range (dB) | | | | | +|--------------|------------------------------------|---------|---------|----------|----------| +| | 100 MHz | 400 MHz | 800 MHz | 1600 MHz | 2000 MHz | +| 120 | 18.1 | 24.2 | N/A | N/A | N/A | +| 480 | N/A | 18.1 | 21.2 | 24.2 | N/A | +| 960 | N/A | 15.1 | 18.1 | 21.2 | [21.9] | + +## 9.5 OTA transmit ON/OFF power + +### 9.5.1 General + +OTA transmit ON/OFF power requirements apply only to TDD operation of NR BS. + +### 9.5.2 OTA transmitter OFF power + +#### 9.5.2.1 General + +OTA transmitter OFF power is defined as the mean power measured over $70/N$ $\mu\text{s}$ filtered with a square filter of bandwidth equal to the *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 BS 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 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*. + +For BS type 1-O, the transmitter OFF power is defined as the output power at the *co-location reference antenna* conducted output(s). For BS 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*. + +#### 9.5.2.2 Minimum requirement for BS type 1-O + +The total power from all *co-location reference antenna* conducted output(s) shall be less than -106 dBm/MHz. + +#### 9.5.2.3 Minimum requirement for BS type 2-O + +The OTA transmitter OFF TRP spectral density for BS type 2-O shall be less than -36 dBm/MHz. + +## 9.5.3 OTA transient period + +### 9.5.3.1 General + +The OTA *transmitter transient period* is the time period during which the transmitter is changing from the *transmitter OFF period* to the *transmitter ON period* or vice versa. The *transmitter transient period* is illustrated in figure 6.4.2.1-1. + +This requirement shall be applied at each RIB supporting transmission in the *operating band*. + +### 9.5.3.2 Minimum requirement for BS type 1-O + +For BS type 1-O, the OTA *transmitter transient period* shall be shorter than the values listed in the minimum requirement table 9.5.3.2-1. + +**Table 9.5.3.2-1: Minimum requirement for the OTA transmitter transient period for BS type 1-O** + +| Transition | Transient period length (μs) | +|------------|------------------------------| +| OFF to ON | 10 | +| ON to OFF | 10 | + +### 9.5.3.3 Minimum requirement for BS type 2-O + +For BS type 2-O, the OTA *transmitter transient period* shall be shorter than the values listed in the minimum requirement table 9.5.3.3-1. + +**Table 9.5.3.3-1: Minimum requirement for the OTA transmitter transient period for BS type 2-O** + +| Transition | Transient period length (μs) | +|------------|------------------------------| +| OFF to ON | 3 | +| ON to OFF | 3 | + +## 9.6 OTA transmitted signal quality + +### 9.6.1 OTA frequency error + +#### 9.6.1.1 General + +The requirements in clause 9.6.1 apply to the *transmitter ON period*. + +OTA 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. + +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 BS type 1-O + +For BS type 1-O, 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.1.2-1 observed over 1 ms. + +#### 9.6.1.3 Minimum requirement for BS type 2-O + +For BS type 2-O, the modulated carrier frequency of each NR carrier configured by the BS shall be accurate to within the accuracy range given in table 9.6.1.3-1 observed over 1 ms. + +**Table 9.6.1.3-1: OTA frequency error minimum requirement** + +| BS class | Accuracy | +|-----------------|-----------------| +| Wide Area BS | ±0.05 ppm | +| Medium Range BS | ±0.1 ppm | +| Local Area BS | ±0.1 ppm | + +## 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 and Annex C for FR2. + +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 BS type 1-O + +For BS type 1-O, the EVM levels of each NR 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.2.3 Minimum Requirement for BS type 2-O + +For BS type 2-O, the EVM levels of each NR carrier for different modulation schemes on PDSCH outlined in table 9.6.2.3-1 shall be met, following the EVM frame structure described in clause 9.6.2.3.1. + +**Table 9.6.2.3-1: EVM requirements for BS type 2-O carrier** + +| Applicability | Modulation scheme for PDSCH | Required EVM (%) | +|----------------------|------------------------------------|-------------------------| +| FR2 | QPSK | 17.5 | +| FR2 | 16QAM | 12.5 | +| FR2 | 64QAM | 8 | +| FR2-1 | 256QAM | 3.5 | + +#### 9.6.2.3.1 EVM frame structure for measurement + +EVM requirements shall apply for each NR carrier over all allocated resource blocks. Different modulation schemes listed in table 9.6.2.3-1 shall be considered for rank 1. + +For NR, for all bandwidths, the EVM measurement shall be performed for each NR 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. + +## 9.6.3 OTA time alignment error + +### 9.6.3.1 General + +This requirement shall apply to frame timing in MIMO transmission, *carrier aggregation* and their combinations. + +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. + +The TAE is specified for a specific set of signals/transmitter configuration/transmission mode. + +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*. + +### 9.6.3.2 Minimum requirement for BS type 1-O + +For MIMO transmission, at each carrier frequency, OTA TAE shall not exceed 65 ns. + +For *intra-band contiguous carrier aggregation*, with or without MIMO, OTA TAE shall not exceed 260 ns. + +For *intra-band non-contiguous carrier aggregation*, with or without MIMO, OTA TAE shall not exceed 3 µs. + +For inter-band *carrier aggregation*, with or without MIMO, OTA TAE shall not exceed 3 µs. + +**Table 9.6.3.2-1: Void** + +**Table 9.6.3.2-2: Void** + +**Table 9.6.3.2-3: Void** + +### 9.6.3.3 Minimum requirement for BS type 2-O + +The minimum requirement for TAE is given in Table 9.6.3.3-4. + +**Table 9.6.3.3-1: Void** + +**Table 9.6.3.3-2: Void** + +**Table 9.6.3.3-3: Void** + +**Table 9.6.3.3-4: TAE requirements for BS type 2-O** + +| Requirement | TAE | | | +|--------------------------------------------------------------------------------------------------------|----------------------------|------------------------|------------------------| +| | 60, 120 kHz
SCS
(ns) | 480 kHz
SCS
(ns) | 960 kHz
SCS
(ns) | +| MIMO transmission | 65 | 32.5 | 32.5 | +| intra-band contiguous carrier aggregation , with or without MIMO | 130 | 32.5 | 32.5 | +| intra-band non-contiguous carrier aggregation , with or without MIMO
(Note) | 260 | N/A | N/A | +| inter-band carrier aggregation , with or without MIMO | 3000 | 3000 | 3000 | +| NOTE: intra-band non-contiguous carrier aggregation is not supported for FR2-2 in this release. | | | | + +## 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 *BS 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 *BS type 1-O* and *BS type 2-O* transmitter is specified both in terms of Adjacent Channel Leakage power Ratio (ACLR) and operating band unwanted emissions (OBUE). The OTA 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. 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 9.7.1-1 for *BS type 1-O* and *BS type 2-O* for the NR *operating bands*. + +**Table 9.7.1-1: Maximum offset $\Delta f_{\text{OBUE}}$ outside the downlink operating band** + +| BS type | Operating band characteristics (MHz) | $\Delta f_{\text{OBUE}}$ (MHz) | +|-------------|------------------------------------------------------------------------|--------------------------------| +| BS type 1-O | $F_{\text{DL,high}} - F_{\text{DL,low}} < 100$ | 10 | +| | $100 \text{ MHz} \leq F_{\text{DL,high}} - F_{\text{DL,low}} \leq 900$ | 40 | +| BS type 2-O | $F_{\text{DL,high}} - F_{\text{DL,low}} \leq 4000$ | 1500 | +| | $4000 < F_{\text{DL,high}} - F_{\text{DL,low}} \leq 14000$ | 3500 | + +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. + +For band n104, the values of $\Delta f_{\text{OBUE}}$ are defined in table 9.7.1-1a. + +**Table 9.7.1-1a: Maximum offset of OBUE outside the downlink operating band for band n104** + +| BS type | Operating band | $\Delta f_{\text{OBUE}}$ (MHz) | +|--------------------|----------------|--------------------------------| +| BS type 1-O | n104 | 100 | + +## 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 [3]. + +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. + +### 9.7.2.2 Minimum requirement for *BS type 1-O* and *BS type 2-O* + +The OTA occupied bandwidth for each NR carrier shall be less than the *BS channel bandwidth*. For intra-band contiguous CA, the OTA occupied bandwidth shall be less than or equal to the *Aggregated BS 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 during the *transmitter ON period*. + +### 9.7.3.2 Minimum requirement for BS type 1-O + +The ACLR (CACLR) absolute *basic limits* in table 6.6.3.2-2 + X, 6.6.3.2-2a + X (where X = 9 dB) or the ACLR (CACLR) *basic limit* in table 6.6.3.2-1, 6.6.3.2-2a or 6.6.3.2-3, whichever is less stringent, shall apply. + +For a RIB operating in multi-carrier or contiguous CA, the ACLR requirements in clause 6.6.3.2 shall apply to *BS channel bandwidths* of the outermost carrier for the frequency ranges defined in table 6.6.3.2-1. For a RIB operating in *non-contiguous spectrum*, the ACLR requirement in clause 6.6.3.2 shall apply in *sub-block gaps* for the frequency ranges defined in table 6.6.3.2-2a, while the CACLR requirement in clause 6.6.3.2 shall apply in *sub-block gaps* for the frequency ranges defined in table 6.6.3.2-3. + +For a *multi-band RIB*, the ACLR requirement in clause 6.6.3.2 shall apply in *Inter RF Bandwidth gaps* for the frequency ranges defined in table 6.6.3.2-2a, while the CACLR requirement in clause 6.6.3.2 shall apply in *Inter RF Bandwidth gaps* for the frequency ranges defined in table 6.6.3.2-3. + +### 9.7.3.3 Minimum requirement for BS type 2-O + +The OTA ACLR limit is specified in table 9.7.3.3-1. + +The OTA ACLR absolute limit is specified in table 9.7.3.3-2. + +The OTA ACLR (CACLR) absolute limit in table 9.7.3.3-2 or 9.7.3.3-4a or the ACLR (CACLR) limit in table 9.7.3.3-1, 9.7.3.3-3 or 9.7.3.3-4, whichever is less stringent, shall apply. + +For a RIB operating in multi-carrier or contiguous CA, the OTA ACLR requirements in table 9.7.3.3-1 shall apply to *BS 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 9.7.3.3-3 shall apply in *sub-block gaps* for the frequency ranges defined in the table, while the OTA CACLR requirement in table 9.7.3.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 9.7.3.3-4 and the filters on the assigned channels are defined in table 9.7.3.3-5. + +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 9.7.3.3-4. + +**Table 9.7.3.3-1: BS type 2-O ACLR limit** + +| BS channel bandwidth of lowest/highest 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 | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit (dB) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|------------------------------------------------------------------------------------|-------------------------------------------| +| 50, 100, 200, 400, 800, 1600, 2000 | $BW_{\text{Channel}}$ | NR of same BW (Note 2) | Square ( $BW_{\text{Config}}$ ) | 28 (Note 3)
26 (Note 4)
24 (Note 5) | +| NOTE 1: $BW_{\text{Channel}}$ and $BW_{\text{Config}}$ are the BS 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 | | | | | +| NOTE 5: Applicable to bands defined within the frequency spectrum range of 52.6 – 71 GHz. | | | | | + +**Table 9.7.3.3-2: BS type 2-O ACLR absolute limit** + +| BS class | ACLR absolute limit | +|-----------------|---------------------| +| Wide area BS | -13 dBm/MHz | +| Medium range BS | -20 dBm/MHz | +| Local area BS | -20 dBm/MHz | + +**Table 9.7.3.3-3: BS type 2-O ACLR limit in non-contiguous spectrum** + +| BS channel bandwidth of carrier transmitted adjacent to sub-block gap (MHz) | Sub-block gap size ( $W_{\text{gap}}$ ) where the limit applies (MHz) | BS adjacent channel centre frequency offset below or above the sub-block edge (inside the gap) | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|-----------------------------------------------------------------------------|-----------------------------------------------------------------------|------------------------------------------------------------------------------------------------|----------------------------------|-----------------------------------------------------------------------------|-------------| +| 50, 100 | $W_{\text{gap}} \geq 100$ (Note 5) | 25 MHz | 50 MHz NR (Note 2) | Square ( $BW_{\text{Config}}$ ) | 28 (Note 3) | +| | $W_{\text{gap}} \geq 250$ (Note 6) | | | | 26 (Note 4) | +| 200, 400 | $W_{\text{gap}} \geq 400$ (Note 6) | 100 MHz | 200 MHz NR (Note 2) | Square ( $BW_{\text{Config}}$ ) | 28 (Note 3) | +| | $W_{\text{gap}} \geq 250$ (Note 5) | | | | 26 (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 BS 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 BS channel bandwidth of the NR carrier transmitted at the other edge of the gap is 200 or 400 MHz. + +**Table 9.7.3.3-4: BS type 2-O CACLR limit in non-contiguous spectrum** + +| BS channel bandwidth of carrier transmitted adjacent to sub-block gap (MHz) | Sub-block gap size ( $W_{\text{gap}}$ ) where the limit applies (MHz) | BS adjacent channel centre frequency offset below or above the sub-block edge (inside the gap) | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | CACLR limit | +|-----------------------------------------------------------------------------|-----------------------------------------------------------------------|------------------------------------------------------------------------------------------------|----------------------------------|-----------------------------------------------------------------------------|-------------| +| 50, 100 | $50 \leq W_{\text{gap}} < 100$ (Note 5) | 25 MHz | 50 MHz NR (Note 2) | Square ( $BW_{\text{Config}}$ ) | 28 (Note 3) | +| | $50 \leq W_{\text{gap}} < 250$ (Note 6) | | | | 26 (Note 4) | +| 200, 400 | $200 \leq W_{\text{gap}} < 400$ (Note 6) | 100 MHz | 200 MHz NR (Note 2) | Square ( $BW_{\text{Config}}$ ) | 28 (Note 3) | +| | $200 \leq W_{\text{gap}} < 250$ (Note 5) | | | | 26 (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 BS 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 BS channel bandwidth of the NR carrier transmitted at the other edge of the gap is 200 or 400 MHz. + +**Table 9.7.3.3-4a: BS type 2-O CACLR absolute limit** + +| BS class | CACLR absolute limit | +|-----------------|----------------------| +| Wide area BS | -13 dBm/MHz | +| Medium range BS | -20 dBm/MHz | +| Local area BS | -20 dBm/MHz | + +**Table 9.7.3.3-5: 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 | + +## 9.7.4 OTA operating band unwanted emissions + +### 9.7.4.1 General + +The OTA limits for operating band unwanted emissions are specified as TRP per RIB unless otherwise stated. + +### 9.7.4.2 Minimum requirement for *BS type 1-O* + +Out-of-band emissions in FR1 are limited by OTA operating band unwanted emission limits. Unless otherwise stated, the operating band unwanted emission 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 9.7.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. For a *RIB* operating in multi-carrier or contiguous CA, the requirements apply to *BS channel bandwidths* of the outermost carrier for the frequency ranges defined in clause 6.6.4.1. + +For a *RIB* operating in *non-contiguous spectrum*, the requirements shall apply inside any *sub-block gap* for the frequency ranges defined in clause 6.6.4.1. + +For a *multi-band RIB*, the requirements shall apply inside any *Inter RF Bandwidth gap* for the frequency ranges defined in clause 6.6.4.1. + +The OTA operating band unwanted emission requirement for *BS type 1-O* is that for each applicable *basic limit* for *BS type 1-H* in clause 6.6.4.2, the power of any unwanted emission shall not exceed an OTA limit specified as the *basic limit* + X, where X = 9 dB. + +### 9.7.4.2.1 Additional requirements + +#### 9.7.4.2.1.1 Protection of DTT + +In certain regions the following requirement may apply for protection of DTT. For *BS type 1-O* 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 9.7.4.2.1.1-1, shall not exceed the maximum emission TRP level shown in the table. This requirement applies in the frequency range 470-790 MHz even though part of the range falls in the spurious domain. + +**Table 9.7.4.2.1.1-1: Declared emissions levels for protection of DTT** + +| Case | Measurement filter centre frequency | Condition on BS maximum aggregate TRP / 10 MHz, $P_{\text{TRP\_10MHz}}$ (NOTE) | Maximum level $P_{\text{TRP,N,MAX}}$ | Measurement bandwidth | +|---------------------------------------------------------------------------------------------|--------------------------------------|--------------------------------------------------------------------------------|--------------------------------------|-----------------------| +| A: for DTT frequencies where broadcasting is protected | $N*8 + 306$ MHz, $21 \leq N \leq 60$ | $P_{\text{TRP\_10MHz}} \geq 59$ dBm | 0 dBm | 8 MHz | +| | $N*8 + 306$ MHz, $21 \leq N \leq 60$ | $36 \leq P_{\text{TRP\_10MHz}} < 59$ dBm | $P_{\text{TRP\_10MHz}} - 59$ dBm | 8 MHz | +| | $N*8 + 306$ MHz, $21 \leq N \leq 60$ | $P_{\text{TRP\_10MHz}} < 36$ dBm | -23 dBm | 8 MHz | +| B: for DTT frequencies where broadcasting is subject to an intermediate level of protection | $N*8 + 306$ MHz, $21 \leq N \leq 60$ | $P_{\text{TRP\_10MHz}} \geq 59$ dBm | 10 dBm | 8 MHz | +| | $N*8 + 306$ MHz, $21 \leq N \leq 60$ | $36 \leq P_{\text{TRP\_10MHz}} < 59$ dBm | $P_{\text{TRP\_10MHz}} - 49$ dBm | 8 MHz | +| | $N*8 + 306$ MHz, $21 \leq N \leq 60$ | $P_{\text{TRP\_10MHz}} < 36$ dBm | -13 dBm | 8 MHz | +| C: for DTT frequencies where broadcasting is not protected | $N*8 + 306$ MHz, $21 \leq N \leq 60$ | N/A | 22 dBm | 8 MHz | + +NOTE: $P_{\text{TRP\_10MHz}}$ (dBm) is defined by $P_{\text{TRP\_10MHz}} = P_{\text{10MHz}} + G_{\text{ant}} + 9\text{dB}$ , where $G_{\text{ant}}$ is 17 dBi. + +#### 9.7.4.2.1.2 Limits in FCC Title 47 + +The BS may have to comply with the applicable emission limits established by FCC Title 47 [8], when deployed in regions where those limits are applied, and under the conditions declared by the manufacturer. + +### 9.7.4.3 Minimum requirement for BS type 2-O + +#### 9.7.4.3.1 General + +The requirements of either clause 9.7.4.3.2 (Category A limits) or clause 9.7.4.3.3 (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 (*BS type 2-O*) in clause 9.7.5.3.2. In addition, the limits in clause 9.7.4.3.4 may also apply. + +Out-of-band emissions in FR2 are limited by OTA operating band unwanted emission limits. Unless otherwise stated, the OTA operating band unwanted emission limits in FR2 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 9.7.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. 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*. + +Emissions 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_{\text{offset}}$ is the separation between the *contiguous transmission bandwidth* edge frequency and the centre of the measuring filter. +- $f_{\text{offset\_max}}$ is the offset to the frequency $\Delta f_{\text{OBUE}}$ outside the downlink *operating band*, where $\Delta f_{\text{OBUE}}$ is defined in table 9.7.1-1. +- $\Delta f_{\text{max}}$ is equal to $f_{\text{offset\_max}}$ minus half of the bandwidth of the measuring filter. + +In addition, inside any *sub-block gap* for a *RIB* operating in *non-contiguous spectrum*, emissions shall not exceed the cumulative sum of the limits specified for the adjacent *sub-blocks* on each side of the *sub-block gap*. The limit for each *sub-block* is specified in clauses 9.7.4.3.2 and 9.7.4.3.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. + +#### 9.7.4.3.2 OTA operating band unwanted emission limits (Category A) + +BS unwanted emissions shall not exceed the maximum levels specified in table 9.7.4.3.2-1, 9.7.4.3.2-2, and 9.7.4.3.2-4. + +**Table 9.7.4.3.2-1: OBUE limits applicable in the frequency range 24.25 – 33.4 GHz** + +| Frequency offset of measurement filter -3B point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | 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}(-5 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 35 \text{ dB}, -12 \text{ dBm}))$ | 1 MHz | +| $0.1 \cdot \text{BW}_{\text{contiguous}} \leq \Delta f < \Delta f_{max}$ | $0.1 \cdot \text{BW}_{\text{contiguous}} + 0.5 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | $\text{Min}(-13 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 43 \text{ dB}, -20 \text{ dBm}))$ | 1 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 . | | | | + +**Table 9.7.4.3.2-2: OBUE limits applicable in the frequency range 37 – 52.6 GHz** + +| Frequency offset of measurement filter -3B point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | 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}(-5 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 33 \text{ dB}, -12 \text{ dBm}))$ | 1 MHz | +| $0.1 \cdot \text{BW}_{\text{contiguous}} \leq \Delta f < \Delta f_{max}$ | $0.1 \cdot \text{BW}_{\text{contiguous}} + 0.5 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | $\text{Min}(-13 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 41 \text{ dB}, -20 \text{ dBm}))$ | 1 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 . | | | | + +**Table 9.7.4.3.2-3: Void** + +**Table 9.7.4.3.2-4: OBUE limits applicable in the frequency range 52.6 – 71 GHz** + +| Frequency offset of measurement filter -3B point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | 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}(-5 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 31 \text{ dB}, -12 \text{ dBm}))$ | 1 MHz | +| $0.1 \cdot \text{BW}_{\text{contiguous}} \leq \Delta f < \Delta f_{max}$ | $0.1 \cdot \text{BW}_{\text{contiguous}} + 0.5 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | $\text{Min}(-13 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 39 \text{ dB}, -20 \text{ dBm}))$ | 1 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 . | | | | + +### 9.7.4.3.3 OTA operating band unwanted emission limits (Category B) + +BS unwanted emissions shall not exceed the maximum levels specified in table 9.7.4.3.3-1, 9.7.4.3.3-2, and 9.7.4.3.3-3. + +**Table 9.7.4.3.3-1: OBUE limits applicable 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$ | 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}(-5 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 35 \text{ dB}, -12 \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, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. | | | | +| 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 9.7.4.3.3-2: OBUE limits applicable 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$ | 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}(-5 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 33 \text{ dB}, -12 \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, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. | | | | +| 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 9.7.4.3.3-3: OBUE limits applicable in the frequency range 52.6 – 71 GHz** + +| Frequency offset of measurement filter -3 dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | 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}(-5 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 31 \text{ dB}, -12 \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}} - 39 \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}} - 29 \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, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. | | | | +| 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}$ . | | | | + +#### 9.7.4.3.4 Additional OTA operating band unwanted emission requirements + +##### 9.7.4.3.4.1 Protection of Earth Exploration Satellite Service + +For BS operating in the frequency range 24.25 – 27.5 GHz, the power of unwanted emission shall not exceed the limits in table 9.7.4.3.4.1-1. + +**Table 9.7.4.3.4.1-1: OBUE limits for protection of Earth Exploration Satellite Service** + +| Frequency range | Limit | Measurement Bandwidth | +|----------------------------------------------------------------------------------|-----------------|-----------------------| +| 23.6 – 24 GHz | -3 dBm (Note 1) | 200 MHz | +| 23.6 – 24 GHz | -9 dBm (Note 2) | 200 MHz | +| NOTE 1: This limit applies to BS brought into use on or before 1 September 2027. | | | +| NOTE 2: This limit applies to BS brought into use after 1 September 2027. | | | + +### 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 BS type 1-O + +##### 9.7.5.2.1 General + +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 ITU-R recommendation SM.329 [2]. + +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. + +*BS type 1-O* requirements consists of OTA transmitter spurious emission requirements based on TRP and co-location requirements not based on TRP. + +##### 9.7.5.2.2 General OTA transmitter spurious emissions requirements + +The Tx spurious emissions requirements for *BS type 1-O* are that for each applicable *basic limit* above 30 MHz in clause 6.6.5.2.1, the TRP of any spurious emission shall not exceed an OTA limit specified as the *basic limit* + X, where X = 9 dB, unless stated differently in regional regulation. + +##### 9.7.5.2.3 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 own or a different BS of the same band being desensitised by emissions from a type 1-O BS. + +This requirement is a co-location requirement as defined in clause 4.9, the power levels are specified at the *co-location reference antenna* output. + +The total power of any spurious emission from both polarizations of the *co-location reference antenna* connector output shall not exceed the *basic limits* in clause 6.6.5.2.2 + X dB, where X = -21 dB. + +#### 9.7.5.2.4 Additional spurious emissions requirements + +These requirements may be applied for the protection of systems 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.5. + +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 Tx additional spurious emissions requirements for *BS type 1-O* are that for each applicable *basic limit* in clause 6.6.5.2.3, the TRP of any spurious emission shall not exceed an OTA limit specified as the *basic limit* + X, where X = 9 dB. + +#### 9.7.5.2.5 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 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, the power levels are specified at the *co-location reference antenna* output(s). + +The power sum of any spurious emission is specified over all supported polarizations at the output(s) of the *co-location reference antenna* and shall not exceed the *basic limits* in clause 6.6.5.2.4 + X dB, where X = -21 dB. + +For a *multi-band RIB*, the exclusions and conditions in the notes column of table 6.6.5.2.4-1 apply for each supported *operating band*. + +#### 9.7.5.3 Minimum requirement for *BS type 2-O* + +##### 9.7.5.3.1 General + +In FR2, the OTA transmitter spurious emission limits apply from 30 MHz to 2nd harmonic of the upper frequency edge of the downlink *operating band*, excluding the frequency range from $\Delta f_{\text{OBUE}}$ below the lowest frequency of the downlink *operating band*, up to $\Delta f_{\text{OBUE}}$ above the highest frequency of the downlink *operating band*, where the $\Delta f_{\text{OBUE}}$ is defined in table 9.7.1-1. + +##### 9.7.5.3.2 General OTA transmitter spurious emissions requirements + +###### 9.7.5.3.2.1 General + +The requirements of either clause 9.7.5.3.2.2 (Category A limits) or clause 9.7.5.3.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 9.7.4.3. + +###### Table 9.7.5.3.2-1: Void + +NOTE: Table 9.7.5.3.2-1 is moved to clause 9.7.5.3.2.2 as Table 9.7.5.3.2.2-1. + +#### 9.7.5.3.2.2 OTA transmitter spurious emissions (Category A) + +The power of any spurious emission shall not exceed the limits in table 9.7.5.3.2-1 + +**Table 9.7.5.3.2.2-1: BS radiated Tx spurious emission limits in FR2** + +| Frequency range | Limit | Measurement Bandwidth | Note | | +|---------------------------------------------------------------------------------------|---------|-----------------------|----------------|--| +| 30 MHz – 1 GHz | -13 dBm | 100 kHz | Note 1 | | +| 1 GHz – 2 nd harmonic of the upper frequency edge of the DL operating band | | 1 MHz | Note 1, Note 2 | | +| NOTE 1: Bandwidth as in ITU-R SM.329 [2], s4.1 | | | | | +| NOTE 2: Upper frequency as in ITU-R SM.329 [2], s2.5 table 1. | | | | | + +#### 9.7.5.3.2.3 OTA transmitter spurious emissions (Category B) + +The power of any spurious emission shall not exceed the limits in table 9.7.5.3.2.3-1. + +**Table 9.7.5.3.2.3-1: BS radiated Tx spurious emission limits in FR2 (Category B)** + +| Frequency range (Note 4) | 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 ↔ 2 nd harmonic of the upper frequency edge of the DL operating band | -20 dBm | 10 MHz | Note 2, Note 3 | +| NOTE 1: Bandwidth as in ITU-R SM.329 [2], s4.1 | | | | +| NOTE 2: Limit and bandwidth as in ERC Recommendation 74-01 [19], Annex 2. | | | | +| NOTE 3: Upper frequency as in ITU-R SM.329 [2], s2.5 table 1. | | | | +| NOTE 4: The step frequencies F step,x are defined in Table 9.7.5.3.2.3-2. | | | | + +**Table 9.7.5.3.2.3-2: Step frequencies for defining the BS radiated Tx spurious emission limits in FR2 (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 | +| n263 | 18 | 43 | 53.5 | 74.5 | 85 | 127 | +| NOTE 1: F step,x are based on ERC Recommendation 74-01 [19], Annex 2. | | | | | | | +| NOTE 2: F step,3 and F step,4 are aligned with the values for Δf OBUE in Table 9.7.1-1. | | | | | | | + +#### 9.7.5.3.3 Additional OTA transmitter spurious emissions requirements + +These requirements may be applied for the protection of systems 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.5. + +#### 9.7.5.3.3.1 Limits for protection of Earth Exploration Satellite Service + +For BS operating in the frequency range 24.25 – 27.5 GHz, the power of any spurious emissions shall not exceed the limits in Table 9.7.5.3.3.1-1. + +**Table 9.7.5.3.3.1-1: 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 BS brought into use on or before 1 September 2027. | | | | +| NOTE 2: This limit applies to BS brought into use after 1 September 2027. | | | | + +## 9.8 OTA transmitter intermodulation + +### 9.8.1 General + +The OTA transmitter intermodulation requirement is a measure of the capability of the transmitter unit to inhibit the generation of signals in its non-linear elements caused by presence of the wanted signal and an interfering signal reaching the transmitter unit via the RDN and antenna array from a co-located base station. The requirement shall apply during the *transmitter ON period* and the *transmitter transient period*. + +The requirement shall apply at each RIB supporting transmission in the *operating band*. + +The transmitter intermodulation level is the *total radiated power* of the intermodulation products when an interfering signal is injected into the *co-location reference antenna*. + +The OTA transmitter intermodulation requirement is not applicable for *BS type 2-O*. + +### 9.8.2 Minimum requirement for *BS type 1-O* + +For *BS type 1-O* the transmitter intermodulation level shall not exceed the TRP unwanted emission limits specified for OTA transmitter spurious emission in clause 9.7.5.2 (except clause 9.7.5.2.3 and clause 9.7.5.2.5), OTA operating band unwanted emissions in clause 9.7.4.2 and OTA ACLR in clause 9.7.3.2 in the presence of a wanted signal and an interfering signal, defined in table 9.8.2-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 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 *Base Station RF Bandwidth edges* of each *operating band*. In case the *inter RF Bandwidth gap* is less than $3 \cdot BW_{\text{Channel}}$ (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 9.8.2-1: Interfering and wanted signals for the OTA transmitter intermodulation requirement** + +| Parameter | Value | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------| +| Wanted signal | NR signal or multi-carrier, or multiple intra-band contiguously or non-contiguously aggregated carriers | +| Interfering signal type | NR signal the minimum BS channel bandwidth ( $BW_{Channel}$ ) with 15 kHz SCS of the band defined in clause 5.3.5 | +| Interfering signal power level | $\min(46 \text{ dBm}, P_{\text{rated,t,TRP}})$ | +| Interfering signal centre frequency offset from the lower (upper) edge of the wanted signal or edge of sub-block inside a 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 RIB 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.141-2 [6] provides further guidance regarding appropriate test requirements. | | +| NOTE 2: In Japan, NOTE 1 is not applied in Band n77, n78, n79. | | +| NOTE 3: For BS type 1-O with dual polarization, the interfering signal power shall be equally divided between the supported polarizations at the co-location reference antenna . | | + +### 9.8.3 Additional requirements (regional) + +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 TRP unwanted emission limits specified for OTA transmitter spurious emission in clause 9.7.5.2 (except clause 9.7.5.2.3 and clause 9.7.5.2.5), OTA operating band unwanted emissions in clause 9.7.4.2 and OTA ACLR in clause 9.7.3.2 in the presence of a wanted signal and an interfering signal, defined in table 9.8.3-1. + +**Table 9.8.3-1: Interfering and wanted signals for the OTA transmitter intermodulation requirement for 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 power level | $\min(46 \text{ dBm}, P_{\text{rated,t,TRP}})$ | +| Interfering signal centre frequency offset from the lower (upper) edge of the wanted signal | $\pm 2.5 \text{ MHz}$
$\pm 7.5 \text{ MHz}$
$\pm 12.5 \text{ MHz}$ | + +## 10 Radiated receiver characteristics + +### 10.1 General + +Radiated receiver characteristics are specified at RIB for *BS type 1-H*, *BS type 1-O*, or *BS type 2-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 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 radiated 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*. +- Each requirement shall be met over the RoAoA specified. + +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 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)}$$ + +For FR2 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}$$ + +## 10.2 OTA sensitivity + +### 10.2.1 BS type 1-H and BS type 1-O + +#### 10.2.1.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 *BS type 1-H* and *BS type 1-O* receiver. + +The *BS type 1-H* and *BS type 1-O* 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 BS is capable of redirecting the *receiver target* related to the OSDD then the OSDD shall include: + +- *BS 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 TS 38.141-2 [6]. +- The *receiver target reference direction*. + +NOTE 1: Some of the declared *sensitivity RoAoA* may coincide depending on the redirection capability. + +NOTE 2: In addition to the declared *sensitivity RoAoA*, several *sensitivity RoAoA* may be implicitly defined by the *receiver target redirection range* without being explicitly declared in the OSDD. + +NOTE 3: (Void) + +If the BS is not capable of redirecting the *receiver target* related to the OSDD, then the OSDD includes only: + +- The set(s) of RAT, *BS channel bandwidth* and declared minimum EIS level applicable to the *sensitivity RoAoA* in the OSDD. +- One declared active *sensitivity RoAoA*. +- The *receiver target reference direction*. + +NOTE 4: For BS without target redirection capability, the declared (fixed) *sensitivity RoAoA* is always the active *sensitivity RoAoA*. + +The OTA sensitivity EIS level declaration shall apply to each supported polarization, under the assumption of *polarization match*. + +#### 10.2.1.2 Minimum requirement + +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 *BS channel bandwidth*. + +### 10.2.2 BS type 2-O + +There is no OTA sensitivity requirement for FR2, the OTA sensitivity is the same as the OTA reference sensitivity in clause 10.3. + +## 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 BS 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: Wide Area BS reference sensitivity levels** + +| BS 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 | $-101.7 - \Delta_{OTAREFSENS}$ | +| 10, 15 | 30 | G-FR1-A1-2 | $-101.8 - \Delta_{OTAREFSENS}$ | +| 10, 15 | 60 | G-FR1-A1-3 | $-98.9 - \Delta_{OTAREFSENS}$ | +| 20, 25, 30, 35, 40, 45, 50 | 15 | G-FR1-A1-4 | $-95.3 - \Delta_{OTAREFSENS}$ | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 | $-95.6 - \Delta_{OTAREFSENS}$ | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 | $-95.7 - \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 BS channel bandwidth. + +**Table 10.3.2-1a: Wide Area BS reference sensitivity levels for n104** + +| BS channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel | Reference sensitivity power level, $P_{REFSENS}$ (dBm) (Note 6) | +|-------------------------------------|---------------------------|-------------------------------|-----------------------------------------------------------------| +| 20, 30, 40, 50 | 15 | G-FR1-A1-4 (Note 1) | $-94.3 - \Delta_{OTAREFSENS}$ | +| 20, 30, 40, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 (Note 1) | $-94.6 - \Delta_{OTAREFSENS}$ | +| 20, 30, 40, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 (Note 1) | $-94.7 - \Delta_{OTAREFSENS}$ | + +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. + +**Table 10.3.2-2: Medium Range BS reference sensitivity levels** + +| BS channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel | OTA reference sensitivity level, E_{\text{ISREFSENS}} (dBm) | +|-------------------------------------------------|----------------------------------|--------------------------------------|---------------------------------------------------------------------------------| +| 5, 10, 15 | 15 | G-FR1-A1-1 | $-96.7 - \Delta_{\text{OTAREFSENS}}$ | +| 10, 15 | 30 | G-FR1-A1-2 | $-96.8 - \Delta_{\text{OTAREFSENS}}$ | +| 10, 15 | 60 | G-FR1-A1-3 | $-93.9 - \Delta_{\text{OTAREFSENS}}$ | +| 20, 25, 30, 35, 40, 45, 50 | 15 | G-FR1-A1-4 | $-90.3 - \Delta_{\text{OTAREFSENS}}$ | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 | $-90.6 - \Delta_{\text{OTAREFSENS}}$ | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 | $-90.7 - \Delta_{\text{OTAREFSENS}}$ | + +NOTE: $E_{\text{ISREFSENS}}$ 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 10.3.2-2a: Medium Range BS reference sensitivity levels for 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) | $-89.3 - \Delta_{\text{OTAREFSENS}}$ | +| 20, 30, 40, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 (Note 1) | $-89.6 - \Delta_{\text{OTAREFSENS}}$ | +| 20, 30, 40, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 (Note 1) | $-89.7 - \Delta_{\text{OTAREFSENS}}$ | + +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 10.3.2-3: Local Area BS reference sensitivity levels** + +| BS channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel | OTA reference sensitivity level, E_{\text{ISREFSENS}} (dBm) | +|-------------------------------------------------|----------------------------------|--------------------------------------|---------------------------------------------------------------------------------| +| 5, 10, 15 | 15 | G-FR1-A1-1 | $-93.7 - \Delta_{\text{OTAREFSENS}}$ | +| 10, 15 | 30 | G-FR1-A1-2 | $-93.8 - \Delta_{\text{OTAREFSENS}}$ | +| 10, 15 | 60 | G-FR1-A1-3 | $-90.9 - \Delta_{\text{OTAREFSENS}}$ | +| 20, 25, 30, 35, 40, 45, 50 | 15 | G-FR1-A1-4 | $-87.3 - \Delta_{\text{OTAREFSENS}}$ | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 | $-87.6 - \Delta_{\text{OTAREFSENS}}$ | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 | $-87.7 - \Delta_{\text{OTAREFSENS}}$ | + +NOTE: $E_{\text{ISREFSENS}}$ 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 10.3.2-3a: Local Area BS reference sensitivity levels for 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) | $-86.3 - \Delta_{\text{OTAREFSENS}}$ | +| 20, 30, 40, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 (Note 1) | $-86.6 - \Delta_{\text{OTAREFSENS}}$ | +| 20, 30, 40, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 (Note 1) | $-86.7 - \Delta_{\text{OTAREFSENS}}$ | + +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. + +### 10.3.3 Minimum requirement for BS 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 $EIS_{\text{REFSENS}}$ level and arrives from any direction within the *OTA REFSENS RoAoA*. + +$EIS_{\text{REFSENS}}$ levels are derived from a single declared basis level $EIS_{\text{REFSENS\_50M}}$ , which is based on a reference measurement channel with 50 MHz BS channel bandwidth. $EIS_{\text{REFSENS\_50M}}$ itself is not a requirement and although it is based on a reference measurement channel with 50 MHz BS channel bandwidth it does not imply that BS has to support 50 MHz BS channel bandwidth. + +For Wide Area BS, $EIS_{\text{REFSENS\_50M}}$ is an integer value in the range -96 to -119 dBm. The specific value is declared by the vendor. + +For Medium Range BS, $EIS_{\text{REFSENS\_50M}}$ is an integer value in the range -91 to -114 dBm. The specific value is declared by the vendor. + +For Local Area BS, $EIS_{\text{REFSENS\_50M}}$ is an integer value in the range -86 to -109 dBm. The specific value is declared by the vendor. + +**Table 10.3.3-1: FR2 OTA reference sensitivity requirement** + +| Frequency Range | BS channel Bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel | OTA reference sensitivity level, $EIS_{\text{REFSENS}}$ (dBm) | +|-----------------|----------------------------|---------------------------|-------------------------------|----------------------------------------------------------------| +| FR2-1 | 50, 100, 200 | 60 | G-FR2-A1-1 | $EIS_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}}$ | +| | 50 | 120 | G-FR2-A1-2 | $EIS_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}}$ | +| | 100, 200, 400 | 120 | G-FR2-A1-3 | $EIS_{\text{REFSENS\_50M}} + 3 + \Delta_{\text{FR2\_REFSENS}}$ | +| FR2-2 | 100, 400 | 120 | G-FR2-A1-3 | $EIS_{\text{REFSENS\_50M}} + 3 + \Delta_{\text{FR2\_REFSENS}}$ | +| | 400, 800, 1600 | 480 | G-FR2-A1-6 | $EIS_{\text{REFSENS\_50M}} + 9 + \Delta_{\text{FR2\_REFSENS}}$ | +| | 400, 800, 1600, 2000 | 960 | G-FR2-A1-7 | $EIS_{\text{REFSENS\_50M}} + 9 + \Delta_{\text{FR2\_REFSENS}}$ | + +NOTE 1: $EIS_{\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 declared $EIS_{\text{REFSENS\_50M}}$ shall be within the range specified above. + +## 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 *BS 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 *BS type 1-O* + +For NR, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel. + +**Table 10.4.2-1: Wide Area BS OTA dynamic range for NR carrier** + +| 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.7-
$\Delta_{\text{OTAREFSENS}}$ | -82.5- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-2 | -71.4-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 10 | 15 | G-FR1-A2-1 | -70.7-
$\Delta_{\text{OTAREFSENS}}$ | -79.3- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-2 | -71.4-
$\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-3 | -68.4-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 15 | 15 | G-FR1-A2-1 | -70.7-
$\Delta_{\text{OTAREFSENS}}$ | -77.5- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-2 | -71.4-
$\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-3 | -68.4-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 20 | 15 | G-FR1-A2-4 | -64.5-
$\Delta_{\text{OTAREFSENS}}$ | -76.2- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -64.5-
$\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -64.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 25 | 15 | G-FR1-A2-4 | -64.5-
$\Delta_{\text{OTAREFSENS}}$ | -75.2- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -64.5-
$\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -64.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 30 | 15 | G-FR1-A2-4 | -64.5-
$\Delta_{\text{OTAREFSENS}}$ | -74.4- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -64.5-
$\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -64.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 35 | 15 | G-FR1-A2-4 | -64.5-
$\Delta_{\text{OTAREFSENS}}$ | -73.7- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -64.5-
$\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -64.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 40 | 15 | G-FR1-A2-4 | -64.5-
$\Delta_{\text{OTAREFSENS}}$ | -73.1- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -64.5-
$\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -64.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 45 | 15 | G-FR1-A2-4 | -64.5-
$\Delta_{\text{OTAREFSENS}}$ | -72.6- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -64.5-
$\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -64.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 50 | 15 | G-FR1-A2-4 | -64.5-
$\Delta_{\text{OTAREFSENS}}$ | -72.1- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -64.5-
$\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -64.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 60 | 30 | G-FR1-A2-5 | -64.5-
$\Delta_{\text{OTAREFSENS}}$ | -71.3- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -64.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 70 | 30 | G-FR1-A2-5 | -64.5-
$\Delta_{\text{OTAREFSENS}}$ | -70.7- $\Delta_{\text{OTAREFSENS}}$ | AWGN | + +| | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|------------|----------------------------------------|-------------------------------------|------| +| | 60 | G-FR1-A2-6 | -64.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 80 | 30 | G-FR1-A2-5 | -64.5-
$\Delta_{\text{OTAREFSENS}}$ | -70.1- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -64.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 90 | 30 | G-FR1-A2-5 | -64.5-
$\Delta_{\text{OTAREFSENS}}$ | -69.5- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -64.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 100 | 30 | G-FR1-A2-5 | -64.5-
$\Delta_{\text{OTAREFSENS}}$ | -69.1- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -64.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| NOTE: The wanted signal mean power is the power level of a single instance of the corresponding reference measurement channel. This requirement shall be met for each consecutive application of a single instance of the reference measurement channel mapped to disjoint frequency ranges with a width corresponding to the number of resource blocks of the reference measurement channel each, except for one instance that might overlap one other instance to cover the full BS channel bandwidth . | | | | | | + +**Table 10.4.2-1a: Wide Area BS OTA dynamic range for NR carrier of band n104** + +| BS channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) / BW Config | Type of interfering signal | +|----------------------------|--------------------------|-------------------------------|----------------------------------------|------------------------------------------------------------|----------------------------| +| 20 | 15 | G-FR1-A2-4 | -63.5-
$\Delta_{\text{OTAREFSENS}}$ | -75.2- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -63.5-
$\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -63.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 30 | 15 | G-FR1-A2-4 | -63.5-
$\Delta_{\text{OTAREFSENS}}$ | -73.4- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -63.5-
$\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -63.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 40 | 15 | G-FR1-A2-4 | -63.5-
$\Delta_{\text{OTAREFSENS}}$ | -72.1- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -63.5-
$\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -63.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 50 | 15 | G-FR1-A2-4 | -63.5-
$\Delta_{\text{OTAREFSENS}}$ | -71.1- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -63.5-
$\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -63.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 60 | 30 | G-FR1-A2-5 | -63.5-
$\Delta_{\text{OTAREFSENS}}$ | -70.3- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -63.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 70 | 30 | G-FR1-A2-5 | -63.5-
$\Delta_{\text{OTAREFSENS}}$ | -69.7- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -63.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 80 | 30 | G-FR1-A2-5 | -63.5-
$\Delta_{\text{OTAREFSENS}}$ | -69.1- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -63.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 90 | 30 | G-FR1-A2-5 | -63.5-
$\Delta_{\text{OTAREFSENS}}$ | -68.5- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -63.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 100 | 30 | G-FR1-A2-5 | -63.5-
$\Delta_{\text{OTAREFSENS}}$ | -68.1- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -63.8-
$\Delta_{\text{OTAREFSENS}}$ | | | + +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 10.4.2-2: Medium Range BS OTA dynamic range for NR carrier** + +| BS channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) / BWConfig | Type of interfering signal | +|-----------------------------------|---------------------------------|--------------------------------------|----------------------------------------|------------------------------------------------------------------|-----------------------------------| +| 5 | 15 | G-FR1-A2-1 | -65.7-
$\Delta_{\text{OTAREFSENS}}$ | -77.5- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-2 | -66.4-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 10 | 15 | G-FR1-A2-1 | -65.7-
$\Delta_{\text{OTAREFSENS}}$ | -74.3- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-2 | -66.4-
$\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-3 | -63.4-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 15 | 15 | G-FR1-A2-1 | -65.7-
$\Delta_{\text{OTAREFSENS}}$ | -72.5- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-2 | -66.4-
$\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-3 | -63.4-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 20 | 15 | G-FR1-A2-4 | -59.5-
$\Delta_{\text{OTAREFSENS}}$ | -71.2- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -59.5-
$\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -59.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 25 | 15 | G-FR1-A2-4 | -59.5-
$\Delta_{\text{OTAREFSENS}}$ | -70.2- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -59.5-
$\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -59.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 30 | 15 | G-FR1-A2-4 | -59.5-
$\Delta_{\text{OTAREFSENS}}$ | -69.4- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -59.5-
$\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -59.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 35 | 15 | G-FR1-A2-4 | -59.5-
$\Delta_{\text{OTAREFSENS}}$ | -68.7- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -59.5-
$\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -59.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 40 | 15 | G-FR1-A2-4 | -59.5-
$\Delta_{\text{OTAREFSENS}}$ | -68.1- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -59.5-
$\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -59.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 45 | 15 | G-FR1-A2-4 | -59.5-
$\Delta_{\text{OTAREFSENS}}$ | -67.6- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -59.5-
$\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -59.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 50 | 15 | G-FR1-A2-4 | -59.5-
$\Delta_{\text{OTAREFSENS}}$ | -67.1- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -59.5-
$\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -59.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 60 | 30 | G-FR1-A2-5 | -59.5-
$\Delta_{\text{OTAREFSENS}}$ | -66.3- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -59.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 70 | 30 | G-FR1-A2-5 | -59.5-
$\Delta_{\text{OTAREFSENS}}$ | -65.7- $\Delta_{\text{OTAREFSENS}}$ | AWGN | + +| | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|------------|----------------------------------------|-------------------------------------|------| +| | 60 | G-FR1-A2-6 | -59.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 80 | 30 | G-FR1-A2-5 | -59.5-
$\Delta_{\text{OTAREFSENS}}$ | -65.1- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -59.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 90 | 30 | G-FR1-A2-5 | -59.5-
$\Delta_{\text{OTAREFSENS}}$ | -64.5- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -59.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 100 | 30 | G-FR1-A2-5 | -59.5-
$\Delta_{\text{OTAREFSENS}}$ | -64.1- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -59.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| NOTE: The wanted signal mean power is the power level of a single instance of the corresponding reference measurement channel. This requirement shall be met for each consecutive application of a single instance of the reference measurement channel mapped to disjoint frequency ranges with a width corresponding to the number of resource blocks of the reference measurement channel each, except for one instance that might overlap one other instance to cover the full BS channel bandwidth . | | | | | | + +**Table 10.4.2-2a: Medium Range BS OTA dynamic range for NR carrier of band n104** + +| BS channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel (Note 2) | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) / $BW_{\text{config}}$ | Type of interfering signal | +|----------------------------|--------------------------|----------------------------------------|----------------------------------------|------------------------------------------------------------|----------------------------| +| 20 | 15 | G-FR1-A2-4 | -58.5-
$\Delta_{\text{OTAREFSENS}}$ | -70.2-
$\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -58.5-
$\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -58.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 30 | 15 | G-FR1-A2-4 | -58.5-
$\Delta_{\text{OTAREFSENS}}$ | -68.4-
$\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -58.5-
$\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -58.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 40 | 15 | G-FR1-A2-4 | -58.5-
$\Delta_{\text{OTAREFSENS}}$ | -67.1-
$\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -58.5-
$\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -58.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 50 | 15 | G-FR1-A2-4 | -58.5-
$\Delta_{\text{OTAREFSENS}}$ | -66.1-
$\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -58.5-
$\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -58.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 60 | 30 | G-FR1-A2-5 | -58.5-
$\Delta_{\text{OTAREFSENS}}$ | -65.3-
$\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -58.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 70 | 30 | G-FR1-A2-5 | -58.5-
$\Delta_{\text{OTAREFSENS}}$ | -64.7-
$\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -58.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 80 | 30 | G-FR1-A2-5 | -58.5-
$\Delta_{\text{OTAREFSENS}}$ | -64.1-
$\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -58.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 90 | 30 | G-FR1-A2-5 | -58.5-
$\Delta_{\text{OTAREFSENS}}$ | -63.5-
$\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -58.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 100 | 30 | G-FR1-A2-5 | -58.5-
$\Delta_{\text{OTAREFSENS}}$ | -63.1-
$\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -58.8-
$\Delta_{\text{OTAREFSENS}}$ | | | + +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 10.4.2-3: Local Area BS OTA dynamic range for NR carrier** + +| BS channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) / BWConfig | Type of interfering signal | +|-----------------------------------|---------------------------------|--------------------------------------|----------------------------------------|------------------------------------------------------------------|-----------------------------------| +| 5 | 15 | G-FR1-A2-1 | -62.7-
$\Delta_{\text{OTAREFSENS}}$ | -74.5- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-2 | -64.4-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 10 | 15 | G-FR1-A2-1 | -62.7-
$\Delta_{\text{OTAREFSENS}}$ | -71.3- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-2 | -64.4-
$\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-3 | -60.4-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 15 | 15 | G-FR1-A2-1 | -62.7-
$\Delta_{\text{OTAREFSENS}}$ | -69.5- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-2 | -64.4-
$\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-3 | -60.4-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 20 | 15 | G-FR1-A2-4 | -56.5-
$\Delta_{\text{OTAREFSENS}}$ | -68.2- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -56.5-
$\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -56.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 25 | 15 | G-FR1-A2-4 | -56.5-
$\Delta_{\text{OTAREFSENS}}$ | -67.2- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -56.5-
$\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -56.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 30 | 15 | G-FR1-A2-4 | -56.5-
$\Delta_{\text{OTAREFSENS}}$ | -66.4- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -56.5-
$\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -56.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 35 | 15 | G-FR1-A2-4 | -56.5-
$\Delta_{\text{OTAREFSENS}}$ | -65.7- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -56.5-
$\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -56.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 40 | 15 | G-FR1-A2-4 | -56.5-
$\Delta_{\text{OTAREFSENS}}$ | -65.1- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -56.5-
$\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -56.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 45 | 15 | G-FR1-A2-4 | -56.5-
$\Delta_{\text{OTAREFSENS}}$ | -64.6- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -56.5-
$\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -56.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 50 | 15 | G-FR1-A2-4 | -56.5-
$\Delta_{\text{OTAREFSENS}}$ | -64.1- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -56.5-
$\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -56.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 60 | 30 | G-FR1-A2-5 | -56.5-
$\Delta_{\text{OTAREFSENS}}$ | -63.3- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -56.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 70 | 30 | G-FR1-A2-5 | -56.5-
$\Delta_{\text{OTAREFSENS}}$ | -62.7- $\Delta_{\text{OTAREFSENS}}$ | AWGN | + +| | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|------------|----------------------------------------|-------------------------------------|------| +| | 60 | G-FR1-A2-6 | -56.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 80 | 30 | G-FR1-A2-5 | -56.5-
$\Delta_{\text{OTAREFSENS}}$ | -62.1- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -56.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 90 | 30 | G-FR1-A2-5 | -56.5-
$\Delta_{\text{OTAREFSENS}}$ | -61.5- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -56.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| 100 | 30 | G-FR1-A2-5 | -56.5-
$\Delta_{\text{OTAREFSENS}}$ | -61.1- $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -56.8-
$\Delta_{\text{OTAREFSENS}}$ | | | +| NOTE: The wanted signal mean power is the power level of a single instance of the corresponding reference measurement channel. This requirement shall be met for each consecutive application of a single instance of the reference measurement channel mapped to disjoint frequency ranges with a width corresponding to the number of resource blocks of the reference measurement channel each, except for one instance that might overlap one other instance to cover the full BS channel bandwidth . | | | | | | + +**Table 10.4.2-3a: Local Area BS OTA dynamic range for NR carrier of band n104** + +| BS channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) / $BW_{Config}$ | Type of interfering signal | +|----------------------------|--------------------------|-------------------------------|---------------------------------|-----------------------------------------------------|----------------------------| +| 20 | 15 | G-FR1-A2-4 | -55.5-
$\Delta_{OTAREFSENS}$ | -67.2-
$\Delta_{OTAREFSENS}$ | AWGN | +| | 30 | G-FR1-A2-5 | -55.5-
$\Delta_{OTAREFSENS}$ | | | +| | 60 | G-FR1-A2-6 | -55.8-
$\Delta_{OTAREFSENS}$ | | | +| 30 | 15 | G-FR1-A2-4 | -55.5-
$\Delta_{OTAREFSENS}$ | -65.4-
$\Delta_{OTAREFSENS}$ | AWGN | +| | 30 | G-FR1-A2-5 | -55.5-
$\Delta_{OTAREFSENS}$ | | | +| | 60 | G-FR1-A2-6 | -55.8-
$\Delta_{OTAREFSENS}$ | | | +| 40 | 15 | G-FR1-A2-4 | -55.5-
$\Delta_{OTAREFSENS}$ | -64.1-
$\Delta_{OTAREFSENS}$ | AWGN | +| | 30 | G-FR1-A2-5 | -55.5-
$\Delta_{OTAREFSENS}$ | | | +| | 60 | G-FR1-A2-6 | -55.8-
$\Delta_{OTAREFSENS}$ | | | +| 50 | 15 | G-FR1-A2-4 | -55.5-
$\Delta_{OTAREFSENS}$ | -63.1-
$\Delta_{OTAREFSENS}$ | AWGN | +| | 30 | G-FR1-A2-5 | -55.5-
$\Delta_{OTAREFSENS}$ | | | +| | 60 | G-FR1-A2-6 | -55.8-
$\Delta_{OTAREFSENS}$ | | | +| 60 | 30 | G-FR1-A2-5 | -55.5-
$\Delta_{OTAREFSENS}$ | -62.3-
$\Delta_{OTAREFSENS}$ | AWGN | +| | 60 | G-FR1-A2-6 | -55.8-
$\Delta_{OTAREFSENS}$ | | | +| 70 | 30 | G-FR1-A2-5 | -55.5-
$\Delta_{OTAREFSENS}$ | -61.7-
$\Delta_{OTAREFSENS}$ | AWGN | +| | 60 | G-FR1-A2-6 | -55.8-
$\Delta_{OTAREFSENS}$ | | | +| 80 | 30 | G-FR1-A2-5 | -55.5-
$\Delta_{OTAREFSENS}$ | -61.1-
$\Delta_{OTAREFSENS}$ | AWGN | +| | 60 | G-FR1-A2-6 | -55.8-
$\Delta_{OTAREFSENS}$ | | | +| 90 | 30 | G-FR1-A2-5 | -55.5-
$\Delta_{OTAREFSENS}$ | -60.5-
$\Delta_{OTAREFSENS}$ | AWGN | +| | 60 | G-FR1-A2-6 | -55.8-
$\Delta_{OTAREFSENS}$ | | | +| 100 | 30 | G-FR1-A2-5 | -55.5-
$\Delta_{OTAREFSENS}$ | -60.1-
$\Delta_{OTAREFSENS}$ | AWGN | +| | 60 | G-FR1-A2-6 | -55.8-
$\Delta_{OTAREFSENS}$ | | | + +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. + +## 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 BS 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 except for band n104, the OTA wanted and the interfering signal are specified in table 10.5.1.2-1 and table 10.5.1.2-2 for OTA ACS. For band n104, the OTA wanted and the interfering signal are specified in table 10.5.1.2-1a 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 characteristics of the interfering signal is further specified in annex D. + +The OTA ACS requirement is applicable outside the *Base Station RF Bandwidth* or *Radio Bandwidth*. The OTA interfering signal offset is defined relative to the *Base station RF Bandwidth edges* or *Radio Bandwidth edges*. + +For RIBs supporting operation in *non-contiguous spectrum* within any *operating band*, the 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 10.5.1.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 10.5.1.2-2. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap*. + +**Table 10.5.1.2-1: OTA ACS requirement for BS type 1-O** + +| BS 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, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 (Note 1) | $EIS_{minSENS} + 6 \text{ dB}$ | Wide Area BS: $-52 - \Delta_{minSENS}$
Medium Range BS: $-47 - \Delta_{minSENS}$
Local Area BS: $-44 - \Delta_{minSENS}$ | +| NOTE 1: The SCS for the lowest/highest carrier received is the lowest SCS supported by the BS for that bandwidth | | | +| NOTE 2: $EIS_{minSENS}$ depends on the BS channel bandwidth | | | + +**Table 10.5.1.2-1a: OTA ACS requirement for BS type 1-O for band n104** + +| BS channel bandwidth of the lowest/highest carrier received (MHz) | Wanted signal mean power (dBm) (Note 2) | Interfering signal mean power (dBm) | +|-------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------| +| 20, 30, 40, 50, 60, 70, 80, 90, 100 (Note 1) | $EIS_{minSENS} + 6 \text{ dB}$ | Wide Area BS: $-55 - \Delta_{minSENS}$
Medium Range BS: $-50 - \Delta_{minSENS}$
Local Area BS: $-47 - \Delta_{minSENS}$ | +| NOTE 1: The SCS for the lowest/highest carrier received is the lowest SCS supported by the BS for that bandwidth | | | +| NOTE 2: $EIS_{minSENS}$ depends on the BS channel bandwidth | | | + +**Table 10.5.1.2-2: OTA ACS interferer frequency offset for BS type 1-O** + +| 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 | ±2.5025 | 5 MHz DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 10 | ±2.5075 | | +| 15 | ±2.5125 | | +| 20 | ±2.5025 | | +| 25 | ±9.4675 | 20 MHz DFT-s-OFDM NR signal, 15 kHz SCS, 100 RBs | +| 30 | ±9.4725 | | +| 35 | ±9.4625 | | +| 40 | ±9.4675 | | +| 45 | ±9.4725 | | +| 50 | ±9.4625 | | +| 60 | ±9.4725 | | +| 70 | ±9.4675 | | +| 80 | ±9.4625 | | +| 90 | ±9.4725 | | +| 100 | ±9.4675 | | + +### 10.5.1.3 Minimum requirement for BS 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 10.5.1.3-1 and table 10.5.1.3-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 D. + +The OTA ACS requirement is applicable outside the *Base Station RF Bandwidth*. The OTA interfering signal offset is defined relative to the Base station *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 10.5.1.3-2. The OTA interfering signal offset is defined relative to the *sub-block edges* inside the *sub-block gap*. + +**Table 10.5.1.3-1: OTA ACS requirement for BS type 2-O** + +| Frequency Range | BS channel bandwidth of the lowest/highest carrier received (MHz) | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | +|------------------------|--------------------------------------------------------------------------|---------------------------------------|------------------------------------------------------------------------------------------------------------------------------| +| FR2-1 | 50, 100, 200, 400 | $EIS_{REFSENS} + 6$ dB (Note 3) | $EIS_{REFSENS\_50M} + 27.7 + \Delta_{FR2\_REFSENS}$ (Note 1)
$EIS_{REFSENS\_50M} + 26.7 + \Delta_{FR2\_REFSENS}$ (Note 2) | +| FR2-2 | 100, 400, 800, 1600, 2000 | $EIS_{REFSENS} + 6$ dB (Note 3) | $EIS_{REFSENS\_50M} + 28.7 + \Delta_{FR2\_REFSENS}$ (Note 4) | + +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 clause 10.3.3 +NOTE 4: Applicable to bands defined within the frequency spectrum range of 57 – 71 GHz + +**Table 10.5.1.3-2: OTA ACS interferer frequency offset for BS type 2-O** + +| Frequency Range | 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 | +|-----------------|-------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------| +| FR2-1 | 50 | ±24.29 | 50 MHz DFT-s-OFDM NR signal, 60 kHz SCS, 64 RBs | +| | 100 | ±24.31 | | +| | 200 | ±24.29 | | +| | 400 | ±24.31 | | +| FR2-2 | 100 | ±48.58 | 100 MHz DFT-s-OFDM NR signal, 120 kHz SCS, 64 RBs | +| | 400 | ±48.58 | | +| | 800 | ±48.62 | | +| | 1600 | ±48.58 | | +| | 2000 | ±48.62 | | + +## 10.5.2 OTA in-band blocking + +### 10.5.2.1 General + +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. + +### 10.5.2.2 Minimum requirement for BS 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 *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 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.2-1, table 10.5.2.2-2 and table 10.5.2.2-3 for general OTA and narrowband OTA blocking requirements. Narrowband blocking requirements are not applied for band n104. The reference measurement channel for the OTA wanted signal is identified in clause 10.3.2 and are further specified in annex A.1. The characteristics of the interfering signal is further specified in annex D. + +The OTA 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-O the OTA in-band blocking requirement shall apply in the in-band blocking frequency range, which is from $F_{UL,low} - \Delta f_{OOB}$ to $F_{UL,high} + \Delta f_{OOB}$ , excluding the downlink frequency range of the FDD *operating band*. The $\Delta f_{OOB}$ for BS type 1-O is defined in table 10.5.2.2-0 except for band n104 and 10.5.2.2-0a for band n104. + +**Table 10.5.2.2-0: $\Delta f_{OOB}$ offset for NR operating bands in FR1** + +| BS type | Operating band characteristics | $\Delta f_{OOB}$ (MHz) | +|-------------|--------------------------------------------------------|------------------------| +| BS type 1-O | $F_{UL,high} - F_{UL,low} < 100$ MHz | 20 | +| | $100$ MHz $\leq F_{UL,high} - F_{UL,low} \leq 900$ MHz | 60 | + +For band n104, $\Delta f_{\text{OOB}}$ for BS type 1-O is defined in table 10.5.2.2-0a. + +**Table 10.5.2.2-0a: $\Delta f_{\text{OOB}}$ offset for NR operating bands for band n104** + +| BS type | Operating band | $\Delta f_{\text{OOB}}$ (MHz) | +|-------------|----------------|-------------------------------| +| BS type 1-O | n104 | 100 | + +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.2-1 and 10.5.2.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 10.5.2.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 10.5.2.2-3. + +**Table 10.5.2.2-1: General OTA blocking requirement for BS type 1-O** + +| BS channel bandwidth of the lowest/highest carrier received (MHz) | Wanted signal mean power (dBm) (Note 1) | Interfering signal mean power (dBm) | Interfering signal centre frequency 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 | $EIS_{REFSENS} + x \text{ dB}$ | Wide Area BS: -43 - $\Delta_{OTAREFSENS}$
Medium Range BS: -38 - $\Delta_{OTAREFSENS}$
Local Area BS: -35 - $\Delta_{OTAREFSENS}$ | $\pm 7.5$ | 5 MHz DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| | $EIS_{minSENS} + x \text{ dB}$ | Wide Area BS: -43 - $\Delta_{minSENS}$
Medium Range BS: -38 - $\Delta_{minSENS}$
Local Area BS: -35 - $\Delta_{minSENS}$ | $\pm 7.5$ | | +| 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | $EIS_{REFSENS} + x \text{ dB}$ | Wide Area BS: -43 - $\Delta_{OTAREFSENS}$
Medium Range BS: -38 - $\Delta_{OTAREFSENS}$
Local Area BS: -35 - $\Delta_{OTAREFSENS}$ | $\pm 30$ | 20 MHz DFT-s-OFDM NR signal, 15 kHz SCS, 100 RBs | +| | $EIS_{minSENS} + x \text{ dB}$ | Wide Area BS: -43 - $\Delta_{minSENS}$
Medium Range BS: -38 - $\Delta_{minSENS}$
Local Area BS: -35 - $\Delta_{minSENS}$ | $\pm 30$ | | + +NOTE 1: 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 10.5.2.2-2: OTA narrowband blocking requirement for BS type 1-O** + +| BS channel bandwidth of the lowest/highest carrier received (MHz) | OTA Wanted signal mean power (dBm) | OTA Interfering signal mean power (dBm) | +|--------------------------------------------------------------------------|-------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------| +| 5, 10, 15, 20 | $EIS_{REFSENS} + 6 \text{ dB}$ | Wide Area BS: -49 - $\Delta_{OTAREFSENS}$
Medium Range BS: -44 - $\Delta_{OTAREFSENS}$
Local Area BS: -41 - $\Delta_{OTAREFSENS}$ | +| | $EIS_{minSENS} + 6 \text{ dB}$ | Wide Area BS: -49 - $\Delta_{minSENS}$
Medium Range BS: -44 - $\Delta_{minSENS}$
Local Area BS: -41 - $\Delta_{minSENS}$ | +| 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | $EIS_{REFSENS} + 6 \text{ dB}$ | Wide Area BS: -49 - $\Delta_{OTAREFSENS}$
Medium Range BS: -44 - $\Delta_{OTAREFSENS}$
Local Area BS: -41 - $\Delta_{OTAREFSENS}$ | +| | $EIS_{minSENS} + 6 \text{ dB}$ | Wide Area BS: -49 - $\Delta_{minSENS}$
Medium Range BS: -44 - $\Delta_{minSENS}$
Local Area BS: -41 - $\Delta_{minSENS}$ | + +NOTE 1: The SCS for the lowest/highest carrier received is the lowest SCS supported by the BS for that bandwidth. +NOTE 2: 7.5 kHz shift is not applied to the wanted signal. + +**Table 10.5.2.2-3: OTA narrowband blocking interferer frequency offsets for BS type 1-O** + +| 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 is positioned at the stated offset, the channel bandwidth of the interfering signal is located adjacently to the lower/upper Base Station RF Bandwidth edge 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. + +### 10.5.2.3 Minimum requirement for BS 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 BS type 2-O, the OTA wanted and OTA interfering signals are provided at RIB using the parameters in table 10.5.2.3-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 D. + +The OTA blocking requirements are applicable outside the *Base Station RF Bandwidth*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth* edges. + +For BS type 2-O the OTA in-band blocking requirement shall apply from $F_{UL\_low} - \Delta f_{OOB}$ to $F_{UL\_high} + \Delta f_{OOB}$ . The $\Delta f_{OOB}$ for BS type 2-O is defined in table 10.5.2.3-0. + +**Table 10.5.2.3-0: $\Delta f_{\text{OoB}}$ offset for NR operating bands in FR2** + +| BS type | Frequency Range | Operating band characteristics (MHz) | $\Delta f_{\text{OoB}}$ (MHz) | +|-------------|-----------------|--------------------------------------------------------------|-------------------------------| +| BS type 2-O | FR2-1 | $F_{\text{UL\_high}} - F_{\text{UL\_low}} \leq 4000$ | 1500 | +| | FR2-2 | $4000 < F_{\text{UL\_high}} - F_{\text{UL\_low}} \leq 14000$ | 3500 | + +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 10.5.2.3-1. The interfering signal offset is defined relative to the *sub-block* edges inside the *sub-block gap*. + +**Table 10.5.2.3-1: General OTA blocking requirement for BS type 2-O** + +| Frequency Range | BS 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 Base Station RF Bandwidth edge or sub-block edge inside a sub-block gap (MHz) | Type of OTA interfering signal | +|-----------------|-------------------------------------------------------------------|------------------------------------|-----------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------| +| FR2-1 | 50, 100, 200, 400 | $EIS_{\text{REFSENS}} + 6$ dB | $EIS_{\text{REFSENS\_50M}} + 33 + \Delta_{\text{FR2\_REFSENS}}$ | $\pm 75$ | 50 MHz DFT-s-OFDM NR signal, 60 kHz SCS, 64 RBs | +| FR2-2 | 100, 400, 800, 1600, 2000 | $EIS_{\text{REFSENS}} + 6$ dB | $EIS_{\text{REFSENS\_50M}} + 36 + \Delta_{\text{FR2\_REFSENS}}$ | $\pm 150$ | 100 MHz DFT-s-OFDM NR signal, 120 kHz SCS, 64 RBs | + +NOTE: $EIS_{\text{REFSENS}}$ and $EIS_{\text{REFSENS\_50M}}$ are given in clause 10.3.3. + +## 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 BS 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 BS 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 shall be excluded from the OTA out-of-band blocking requirement. + +For *BS 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 FDD *operating band* for BS supporting FDD. The $\Delta f_{OOB}$ for *BS type 1-O* is defined in table 10.5.2.2-0. + +**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.36 | CW carrier | +| NOTE 1: $EIS_{minSENS}$ 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 $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. | | | + +## 10.6.2.2 Co-location minimum requirement + +This additional OTA out-of-band blocking requirement may be applied for the protection of BS receivers when NR, E-UTRA BS, UTRA BS, CDMA BS or GSM/EDGE BS operating in a different frequency band are co-located with a BS. + +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 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 *BS channel bandwidth* and further specified in annex A.1. + +For *BS type 1-O* the OTA blocking requirement for co-location with BS in other frequency bands is applied for all *operating bands* for which co-location protection is provided. + +**Table 10.6.2.2-1: OTA blocking requirement for co-location with BS in other frequency bands** + +| Frequency range of interfering signal | Wanted signal mean power (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 | $EIS_{minSENS} + 6$ dB
(Note 1) | +46 | +38 | +24 | CW carrier | +| NOTE 1: $EIS_{minSENS}$ depends on the BS class and on the BS channel bandwidth , see clause 10.2.
NOTE 2: The requirement does not apply when the interfering signal falls within any of the supported uplink operating band(s) or in $\Delta f_{OOB}$ immediately outside any of the supported uplink operating band(s) . | | | | | | + +## 10.6.3 Minimum requirement for *BS type 2-O* + +### 10.6.3.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 *OTA REFSENS 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 *BS type 2-O* operating in FR2-1, the OTA out-of-band blocking requirement apply from 30 MHz to $F_{UL,low} - 1500$ MHz and from $F_{UL,high} + 1500$ MHz up to 2nd harmonic of the upper frequency edge of the *operating band*. + +For *BS type 2-O* operating in FR2-2, the OTA out-of-band blocking requirement apply from 30 MHz to $F_{UL,low} - 3500$ MHz and from $F_{UL,high} + 3500$ MHz up to 2nd harmonic of the upper frequency edge of the *operating band*. + +For OTA wanted and OTA interfering signals provided at the RIB using the parameters in table 10.6.3.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 for each *BS channel bandwidth* and further specified in annex A.1. + +**Table 10.6.3.1-1: OTA out-of-band blocking performance requirement** + +| Frequency Range | Frequency range of interfering signal (MHz) | Wanted signal mean power (dBm) | Interferer RMS field-strength (V/m) | Type of interfering signal | +|-----------------|-----------------------------------------------------------------------------------------------------------|--------------------------------|-------------------------------------|----------------------------| +| FR2-1 | 30 to 12750 | $EIS_{REFSENS} + 6$ dB | 0.36 | CW | +| | 12750 to $F_{UL,low} - 1500$ | $EIS_{REFSENS} + 6$ dB | 0.1 | CW | +| | $F_{UL,high} + 1500$ to 2 nd harmonic of the upper frequency edge of the operating band | $EIS_{REFSENS} + 6$ dB | 0.1 | CW | +| FR2-2 | 30 to 12750 | $EIS_{REFSENS} + 6$ dB | 0.36 | CW | +| | 12750 to $F_{UL,low} - 3500$ | $EIS_{REFSENS} + 6$ dB | 0.1 | CW | +| | $F_{UL,high} + 3500$ to 2 nd harmonic of the upper frequency edge of the operating band | $EIS_{REFSENS} + 6$ dB | 0.1 | CW | + +## 10.7 OTA receiver spurious emissions + +### 10.7.1 General + +The OTA RX spurious emission is the power of the emissions radiated from the antenna array from a receiver unit. + +The metric used to capture OTA receiver spurious emissions for *BS type 1-O* and *BS type 2-O* is *total radiated power* (TRP), with the requirement defined at the RIB. + +### 10.7.2 Minimum requirement for *BS type 1-O* + +For a BS operating in FDD, OTA RX spurious emissions requirement do not apply as they are superseded by the OTA TX spurious emissions requirement. This is due to the fact that TX and RX spurious emissions cannot be distinguished in OTA domain. + +For a BS operating in TDD, the OTA RX spurious emissions requirement shall apply during the *transmitter OFF period* only. + +For RX only *multi-band RIB*, the OTA RX spurious emissions requirements are subject to exclusion zones in each supported *operating band*. + +The OTA RX spurious emissions requirement for *BS type 1-O* is that for each *basic limit* specified in table 10.7.2-1, the power sum of emissions at the RIB shall not exceed limits specified as the *basic limit* + X, where X = 9 dB, unless stated differently in regional regulation. + +**Table 10.7.2-1: General BS receiver spurious emission basic limits for BS type 1-O** + +| Spurious frequency range | Basic limit (Note 4) | Measurement bandwidth | Notes | +|--------------------------------------------------------------------------------------------------|----------------------|-----------------------|------------------------| +| 30 MHz – 1 GHz | -36 dBm | 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 UL operating band in GHz | -30 dBm | 1 MHz | Note 1, Note 2, Note 3 | +| 12.75 GHz - 26 GHz | -30 dBm | 1 MHz | Note 1, Note 2, Note 6 | + +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: 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: Additional limits may apply regionally. +NOTE 5: The frequency range from $\Delta f_{\text{OBUE}}$ below the lowest frequency of the BS transmitter operating band to $\Delta f_{\text{OBUE}}$ above the highest frequency of the BS transmitter operating band may be excluded from the requirement. $\Delta f_{\text{OBUE}}$ is defined in clause 9.7.1. For multi-band R/B, the exclusion applies for all supported operating bands. +NOTE 6: Applies for Band for which the upper frequency edge of the UL operating band is greater than 5.2 GHz. + +### 10.7.3 Minimum requirement for BS type 2-O + +The OTA RX spurious emissions requirement shall apply during the transmitter OFF period only. + +For the BS type 2-O, the power of any RX spurious emission shall not exceed the limits in table 10.7.3-1. + +**10.7.3-1: Radiated Rx spurious emission limits for BS type 2-O** + +| Spurious frequency range (Note 4) | Limit (Note 5) | 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_{\text{step},1}$ | -20 dBm | 10 MHz | Note 2 | +| $F_{\text{step},1}$ ↔ $F_{\text{step},2}$ | -15 dBm | 10 MHz | Note 2 | +| $F_{\text{step},2}$ ↔ $F_{\text{step},3}$ | -10 dBm | 10 MHz | Note 2 | +| $F_{\text{step},4}$ ↔ $F_{\text{step},5}$ | -10 dBm | 10 MHz | Note 2 | +| $F_{\text{step},5}$ ↔ $F_{\text{step},6}$ | -15 dBm | 10 MHz | Note 2 | +| $F_{\text{step},6}$ ↔ 2 nd harmonic of the upper frequency edge of the UL operating band | -20 dBm | 10 MHz | Note 2, Note 3 | + +NOTE 1: Bandwidth as in ITU-R SM.329 [2], s4.1. +NOTE 2: Limit and bandwidth as in ERC Recommendation 74-01 [19], Annex 2. +NOTE 3: Upper frequency as in ITU-R SM.329 [2], s2.5 table 1. +NOTE 4: The step frequencies $F_{\text{step},x}$ are defined in table 10.7.3-2. +NOTE 5: Additional limits may apply regionally. + +**Table 10.7.3-2: Step frequencies for defining the radiated Rx spurious emission limits for BS type 2-O** + +| Operating band | $F_{\text{step},1}$ (GHz) | $F_{\text{step},2}$ (GHz) | $F_{\text{step},3}$ (GHz) | $F_{\text{step},4}$ (GHz) | $F_{\text{step},5}$ (GHz) | $F_{\text{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 | +| n262 | 37.2 | 45.2 | 45.7 | 49.7 | 50.2 | 58.2 | +| n263 | 18 | 43 | 53.5 | 74.5 | 85 | 127 | + +In addition to the requirements in Table 10.7.3-1, the requirement for protection of EESS for BS operating in frequency range 24.25 - 27.5 GHz in clause 9.7.5.3.3 may be applied. + +## 10.8 OTA receiver intermodulation + +### 10.8.1 General + +Third and higher order mixing of the two interfering RF signals can produce an interfering signal in the band of the desired channel. Intermodulation response rejection is a measure of the capability of the receiver unit to receive a wanted signal on its assigned channel frequency in the presence of two interfering signals which have a specific frequency relationship to the wanted signal. The requirement is defined as a *directional requirement* at the *RIB*. + +### 10.8.2 Minimum requirement for BS 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 a wanted signal at the assigned channel frequency and two interfering signals at the RIB with the conditions specified in tables 10.8.2-1 and 10.8.2-2 for intermodulation performance and in tables 10.8.2-3 and 10.8.2-4 for narrowband intermodulation performance. Narrowband intermodulation requirements are not applied for band n104. + +The reference measurement channel for the wanted signal is identified in table 10.3.2-1, table 10.3.2-2 and table 10.3.2-3 for each *BS channel bandwidth* and further specified in annex A.1. The characteristics of the interfering signal is further specified in annex D. + +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 60kHz and *BS channel bandwidth* $\leq 20\text{MHz}$ , for which the subcarrier spacing of the interfering signal shall be 30kHz. + +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 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 *BS channel bandwidth* of the NR interfering signal in tables 10.8.2-2 and 10.8.2-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 *Base Station 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 10.8.2-2 and 10.8.2-4. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* inside the *Inter RF Bandwidth gap*. + +**Table 10.8.2-1: General intermodulation requirement** + +| BS class | Wanted Signal mean power (dBm) | Mean power of the interfering signals (dBm) | Type of interfering signals | +|-----------------|--------------------------------|---------------------------------------------|-----------------------------| +| Wide Area BS | $EIS_{REFSENS} + 6$ dB | $-52 - \Delta_{OTAREFSENS}$ | See Table 10.8.2-2 | +| | $EIS_{minSENS} + 6$ dB | $-52 - \Delta_{minSENS}$ | | +| Medium Range BS | $EIS_{REFSENS} + 6$ dB | $-47 - \Delta_{OTAREFSENS}$ | | +| | $EIS_{minSENS} + 6$ dB | $-47 - \Delta_{minSENS}$ | | +| Local Area BS | $EIS_{REFSENS} + 6$ dB | $-44 - \Delta_{OTAREFSENS}$ | | +| | $EIS_{minSENS} + 6$ dB | $-44 - \Delta_{minSENS}$ | | + +NOTE 1: $EIS_{REFSENS}$ and $EIS_{minSENS}$ depend on the BS class and on the BS channel bandwidth, see clause 10.3 and 10.2. + +**Table 10.8.2-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 | ±7.5 | CW | +| | ±17.5 | 5 MHz DFT-s-OFDM NR signal (Note 1) | +| 10 | ±7.465 | CW | +| | ±17.5 | 5 MHz DFT-s-OFDM NR signal (Note 1) | +| 15 | ±7.43 | CW | +| | ±17.5 | 5 MHz DFT-s-OFDM NR signal (Note 1) | +| 20 | ±7.395 | CW | +| | ±17.5 | 5 MHz 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 | 20 MHz DFT-s-OFDM NR signal (Note 2) | +| 35 | ±7.44 | CW | +| | ±25 | 20 MHz DFT-s-OFDM NR signal (Note 2) | +| 40 | ±7.45 | CW | +| | ±25 | 20 MHz DFT-s-OFDM NR signal (Note 2) | +| 45 | ±7.37 | CW | +| | ±25 | 20 MHz DFT-s-OFDM NR signal (Note 2) | +| 50 | ±7.35 | CW | +| | ±25 | 20 MHz DFT-s-OFDM NR signal (Note 2) | +| 60 | ±7.49 | CW | +| | ±25 | 20 MHz 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 | 20 MHz 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 | 20 MHz DFT-s-OFDM NR signal (Note 2) | + +NOTE 1: Number of RBs is 25 for 15 kHz subcarrier spacing and 10 for 30 kHz subcarrier spacing. + +NOTE 2: Number of RBs is 100 for 15 kHz subcarrier spacing, 50 for 30 kHz subcarrier spacing and 24 for 60 kHz subcarrier spacing. + +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 10.8.2-3: Narrowband intermodulation performance requirement in FR1** + +| BS class | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | Type of interfering signals | +|-----------------|---------------------------------|-------------------------------------|-----------------------------| +| Wide Area BS | $EIS_{REFSENS} + 6$ dB (Note 1) | $-52 - \Delta_{OTAREFSENS}$ | See Table 10.8.2-4 | +| | $EIS_{minSENS} + 6$ dB (Note 1) | $-52 - \Delta_{minSENS}$ | | +| Medium Range BS | $EIS_{REFSENS} + 6$ dB (Note 1) | $-47 - \Delta_{OTAREFSENS}$ | | +| | $EIS_{minSENS} + 6$ dB (Note 1) | $-47 - \Delta_{minSENS}$ | | +| Local Area BS | $EIS_{REFSENS} + 6$ dB (Note 1) | $-44 - \Delta_{OTAREFSENS}$ | | +| | $EIS_{minSENS} + 6$ dB (Note 1) | $-44 - \Delta_{minSENS}$ | | + +NOTE 1: $EIS_{REFSENS} / EIS_{minSENS}$ depends on the BS channel bandwidth, see clause 10.3 and 10.2. + +**Table 10.8.2-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 signal | +|--------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------| +| 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 | +| | ±2710 | 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. + +### 10.8.3 Minimum requirement for BS type 2-O + +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 *OTA REFSENS RoAoA*. + +The wanted and interfering signals applies to each supported polarization, under the assumption of *polarization match*. + +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 10.8.3-1 and 10.8.3-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 *OTA REFSENS RoAoA*. The reference measurement channel for the wanted signal is identified in table 10.3.3-1 for each *BS channel bandwidth* and further specified in annex A.1. The characteristics of the interfering signal is further specified in annex D. + +The subcarrier spacing for the modulated interfering signal shall be the same as the subcarrier spacing for the wanted signal except for FR2-2 with 400MHz, 800MHz, 1600MHz and 2000MHz case. + +The receiver intermodulation requirement is applicable outside the *Base Station RF Bandwidth*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges*. + +**Table 10.8.3-1: General intermodulation requirement** + +| BS channel bandwidth of the lowest/highest carrier received (MHz) | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | Type of interfering signals | +|-----------------------------------------------------------------------------------|--------------------------------|---------------------------------------------------------------------------------------------------------------------------|-----------------------------| +| 50, 100, 200, 400, 800, 1600, 2000 | $EIS_{REFSENS} + 6$ | $EIS_{REFSENS\_50M} + 25 + \Delta_{FR2\_REFSENS}$ (Note 2),
$EIS_{REFSENS\_50M} + 28 + \Delta_{FR2\_REFSENS}$ (Note 3) | See Table 10.8.3-2 | +| NOTE 1: $EIS_{REFSENS}$ and $EIS_{REFSENS\_50M}$ are given in clause 10.3.3. | | | | +| NOTE 2: Applicable to bands defined within the frequency spectrum range of FR2-1. | | | | +| NOTE 3: Applicable to bands defined within the frequency spectrum range of FR2-2. | | | | + +**Table 10.8.3-2: Interfering signals for intermodulation requirement** + +| Frequency Range | 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 | +|-----------------|-------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|--------------------------------------| +| FR2-1 | 50 | ±7.5 | CW | +| | | ±40 | 50MHz DFT-s-OFDM NR signal (Note 1) | +| | 100 | ±6.88 | CW | +| | | ±40 | 50MHz DFT-s-OFDM NR signal (Note 1) | +| | 200 | ±5.64 | CW | +| | | ±40 | 50MHz DFT-s-OFDM NR signal (Note 1) | +| | 400 | ±6.02 | CW | +| | | ±45 | 50MHz DFT-s-OFDM NR signal (Note 1) | +| FR2-2 | 100 | ±7.5 | CW | +| | | ±65 | 100MHz DFT-s-OFDM NR signal (Note 2) | +| | 400 | ±6.28 | CW | +| | | ±70 | 100MHz DFT-s-OFDM NR signal (Note 2) | +| | 800 | [±7.3] | CW | +| | | [±105] | 100MHz DFT-s-OFDM NR signal (Note 2) | +| | 1600 | [±5.86] | CW | +| | | [±145] | 100MHz DFT-s-OFDM NR signal (Note 2) | +| | 2000 | ±7.48 | CW | +| | | ±210 | 100MHz DFT-s-OFDM NR signal (Note 2) | + +NOTE 1: Number of RBs is 64 for the 60 kHz subcarrier spacing, 32 for the 120 kHz subcarrier spacing + +NOTE 2: Number of RBs is 64 with 120 kHz subcarrier spacing. + +## 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 BS 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 BS 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 Wide Area BS, in table 10.9.2-2 for Medium Range BS and in table 10.9.2-3 for Local Area BS except in operating band n104. +- In table 10.9.2-1a for Wide Area BS, in table 10.9.2-2a for Medium Range BS and in table 10.9.2-3a for Local Area BS in operating band n104. + +The characteristics of the interfering signal is further specified in annex D. + +**Table 10.9.2-1: Wide Area BS in-channel selectivity** + +| BS channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | Type of interfering signal | +|-----------------------------------|---------------------------------|--------------------------------------|---------------------------------------|--------------------------------------------|-------------------------------------------| +| 5 | 15 | G-FR1-A1-7 | $-100.6 - \Delta_{\min\text{SENS}}$ | $-81.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 10 RBs | +| 10, 15, 20, 25, 30, 35 | 15 | G-FR1-A1-1 | $-98.7 - \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 | $-92.3 - \Delta_{\min\text{SENS}}$ | $-71.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 100 RBs | +| 5 | 30 | G-FR1-A1-8 | $-101.3 - \Delta_{\min\text{SENS}}$ | $-81.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 5 RBs | +| 10, 15, 20, 25, 30, 35 | 30 | G-FR1-A1-2 | $-98.8 - \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 | $-92.6 - \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 | $-98.2 - \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 | $-92.7 - \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 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 10.9.2-1a: 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 | $-97.7 - \Delta_{\min\text{SENS}}$ | $-76.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 40, 50 | 15 | G-FR1-A1-4 | $-91.3 - \Delta_{\min\text{SENS}}$ | $-70.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 100 RBs | +| 20, 30 | 30 | G-FR1-A1-2 | $-97.8 - \Delta_{\min\text{SENS}}$ | $-77.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 10 RBs | +| 40, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 | $-91.6 - \Delta_{\min\text{SENS}}$ | $-70.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 50 RBs | +| 20, 30 | 60 | G-FR1-A1-9 | $-97.2 - \Delta_{\min\text{SENS}}$ | $-77.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 60 kHz SCS, 5 RBs | +| 40, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 | $-91.7 - \Delta_{\min\text{SENS}}$ | $-70.6 - \Delta_{\min\text{SENS}}$ | 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 10.9.2-2: Medium Range BS in-channel selectivity** + +| BS channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | Type of interfering signal | +|---------------------------------|--------------------------|-------------------------------|------------------------------------|-------------------------------------|-------------------------------------------| +| 5 | 15 | G-FR1-A1-7 | $-95.6 - \Delta_{\min\text{SENS}}$ | $-76.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 10 RBs | +| 10, 15, 20, 25, 30, 35 | 15 | G-FR1-A1-1 | $-93.7 - \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 | $-87.3 - \Delta_{\min\text{SENS}}$ | $-66.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 100 RBs | +| 5 | 30 | G-FR1-A1-8 | $-96.3 - \Delta_{\min\text{SENS}}$ | $-76.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 5 RBs | +| 10, 15, 20, 25, 30, 35 | 30 | G-FR1-A1-2 | $-93.8 - \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 | $-87.6 - \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 | $-93.2 - \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 | $-87.7 - \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 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 10.9.2-2a: 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 | $-92.7 - \Delta_{\min\text{SENS}}$ | $-71.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 40, 50 | 15 | G-FR1-A1-4 | $-86.3 - \Delta_{\min\text{SENS}}$ | $-65.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 100 RBs | +| 20, 30 | 30 | G-FR1-A1-2 | $-92.8 - \Delta_{\min\text{SENS}}$ | $-72.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 10 RBs | +| 40, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 | $-86.6 - \Delta_{\min\text{SENS}}$ | $-65.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 50 RBs | +| 20, 30 | 60 | G-FR1-A1-9 | $-92.2 - \Delta_{\min\text{SENS}}$ | $-72.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 60 kHz SCS, 5 RBs | +| 40, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 | $-86.7 - \Delta_{\min\text{SENS}}$ | $-65.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 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 10.9.2-3: Local area BS in-channel selectivity** + +| BS channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | Type of interfering signal | +|---------------------------------|--------------------------|-------------------------------|------------------------------------|-------------------------------------|-------------------------------------------| +| 5 | 15 | G-FR1-A1-7 | $-92.6 - \Delta_{\min\text{SENS}}$ | $-73.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 10 RBs | +| 10, 15, 20, 25, 30, 35 | 15 | G-FR1-A1-1 | $-90.7 - \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 | $-84.3 - \Delta_{\min\text{SENS}}$ | $-63.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 100 RBs | +| 5 | 30 | G-FR1-A1-8 | $-93.3 - \Delta_{\min\text{SENS}}$ | $-73.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 5 RBs | +| 10, 15, 20, 25, 30, 35 | 30 | G-FR1-A1-2 | $-90.8 - \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 | $-84.6 - \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 | $-90.2 - \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 | $-84.7 - \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 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 10.9.2-3a: 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 | $-89.7 - \Delta_{\min\text{SENS}}$ | $-68.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 40, 50 | 15 | G-FR1-A1-4 | $-83.3 - \Delta_{\min\text{SENS}}$ | $-62.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 100 RBs | +| 20, 30 | 30 | G-FR1-A1-2 | $-89.8 - \Delta_{\min\text{SENS}}$ | $-69.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 10 RBs | +| 40, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 | $-83.6 - \Delta_{\min\text{SENS}}$ | $-62.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 50 RBs | +| 20, 30 | 60 | G-FR1-A1-9 | $-89.2 - \Delta_{\min\text{SENS}}$ | $-69.4 - \Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 60 kHz SCS, 5 RBs | +| 40, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 | $-83.7 - \Delta_{\min\text{SENS}}$ | $-62.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 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. + +### 10.9.3 Minimum requirement for BS type 2-O + +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 *OTA REFSSENS RoAoA*. + +The wanted and interfering signals applies to each supported polarization, under the assumption of *polarization match*. + +For *BS 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 10.9.3-1. The characteristics of the interfering signal is further specified in annex D. + +**Table 10.9.3-1: OTA in-channel selectivity requirement for *BS type 2-O*** + +| Frequency Range | BS channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel | Wanted signal mean power (dBm) (Note 2) | Interfering signal mean power (dBm) (Note 2) | Type of interfering signal | +|-----------------|----------------------------|--------------------------|-------------------------------|---------------------------------------------------|---------------------------------------------------|------------------------------------------| +| FR2-1 | 50 | 60 | G-FR2-A1-4 | $EIS_{REFSENS\_50M} + \Delta_{FR2\_REFSENS}$ | $EIS_{REFSENS\_50M} + 10 + \Delta_{FR2\_REFSENS}$ | DFT-s-OFDM NR signal, 60 kHz SCS, 32 RB | +| | 100,200 | 60 | G-FR2-A1-1 | $EIS_{REFSENS\_50M} + 3 + \Delta_{FR2\_REFSENS}$ | $EIS_{REFSENS\_50M} + 13 + \Delta_{FR2\_REFSENS}$ | DFT-s-OFDM NR signal, 60 kHz SCS, 64 RB | +| | 50 | 120 | G-FR2-A1-5 | $EIS_{REFSENS\_50M} + \Delta_{FR2\_REFSENS}$ | $EIS_{REFSENS\_50M} + 10 + \Delta_{FR2\_REFSENS}$ | DFT-s-OFDM NR signal, 120 kHz SCS, 16 RB | +| | 100,200,400 | 120 | G-FR2-A1-2 | $EIS_{REFSENS\_50M} + 3 + \Delta_{FR2\_REFSENS}$ | $EIS_{REFSENS\_50M} + 13 + \Delta_{FR2\_REFSENS}$ | DFT-s-OFDM NR signal, 120 kHz SCS, 32 RB | +| FR2-2 | 100,400 | 120 | G-FR2-A1-2 | $EIS_{REFSENS\_50M} + 3 + \Delta_{FR2\_REFSENS}$ | $EIS_{REFSENS\_50M} + 13 + \Delta_{FR2\_REFSENS}$ | DFT-s-OFDM NR signal, 120 kHz SCS, 32 RB | +| | 400 | 480 | G-FR2-A1-8 | $EIS_{REFSENS\_50M} + 9 + \Delta_{FR2\_REFSENS}$ | $EIS_{REFSENS\_50M} + 19 + \Delta_{FR2\_REFSENS}$ | DFT-s-OFDM NR signal, 480 kHz SCS, 32 RB | +| | 800, 1600 | 480 | G-FR2-A1-6 | $EIS_{REFSENS\_50M} + 12 + \Delta_{FR2\_REFSENS}$ | $EIS_{REFSENS\_50M} + 22 + \Delta_{FR2\_REFSENS}$ | DFT-s-OFDM NR signal, 480 kHz SCS, 54 RB | +| | 400 | 960 | G-FR2-A1-9 | $EIS_{REFSENS\_50M} + 9 + \Delta_{FR2\_REFSENS}$ | $EIS_{REFSENS\_50M} + 19 + \Delta_{FR2\_REFSENS}$ | DFT-s-OFDM NR signal, 960 kHz SCS, 16 RB | +| | 800, 1600, 2000 | 960 | G-FR2-A1-7 | $EIS_{REFSENS\_50M} + 12 + \Delta_{FR2\_REFSENS}$ | $EIS_{REFSENS\_50M} + 22 + \Delta_{FR2\_REFSENS}$ | DFT-s-OFDM NR signal, 960 kHz SCS, 27 RB | + +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. + +NOTE 2: $EIS_{REFSENS\_50M}$ is defined in clause 10.3.3. + +**Table 10.9.3-2: (Void)** + +**Table 10.9.3-3: (Void)** + +## 11 Radiated performance requirements + +### 11.1 General + +#### 11.1.1 Scope and definitions + +Radiated performance requirements specify the ability of the *BS type 1-O* or *BS 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 defined in annex A and the propagation conditions in annex G. The requirements only apply to those FRCs that are supported by the BS. + +The radiated performance requirements for *BS type 1-O* and for the *BS type 2-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 BS, with the required SNR applied separately per polarization. + +NOTE 1: The BS can support more than 2 *demodulation branches*, however OTA conformance testing can only be performed for 1 or 2 *demodulation branches*. + +Unless stated otherwise, radiated performance requirements apply for a single carrier only. Radiated performance requirements for a BS supporting CA are defined in terms of single carrier requirements. + +For *BS 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 2: *BS 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. + +In tests performed with signal generators a synchronization signal may be provided from the BS to the signal generator, to enable correct timing of the wanted signal. + +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 energy in a slot on a RIB. + +N is the noise energy 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 *BS type 1-O*, or the *BS 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 *BS type 1-O*, or the *BS 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). + +### 11.1.3 Void + +## 11.2 Performance requirements for PUSCH + +### 11.2.1 Requirements for *BS type 1-O* + +#### 11.2.1.1 Requirements for PUSCH with transform precoding disabled + +Apply the requirements defined in clause 8.2.1 for 2Rx. + +#### 11.2.1.2 Requirements for PUSCH with transform precoding enabled + +Apply the requirements defined in clause 8.2.2 for 2Rx. + +#### 11.2.1.3 Requirements for UCI multiplexed on PUSCH + +Apply the requirements defined in clause 8.2.3 for 2Rx. + +#### 11.2.1.4 Requirements for PUSCH for high speed train + +Apply the requirements defined in clause 8.2.4 for 2Rx. + +#### 11.2.1.5 Requirements for UL timing adjustment + +Apply the requirements defined in clause 8.2.5 for 2Rx. + +#### 11.2.1.6 Requirements for PUSCH 0.001% BLER + +Apply the requirements defined in clause 8.2.6 for 2Rx. + +#### 11.2.1.7 Requirements for PUSCH repetition Type A + +Apply the requirements defined in clause 8.2.7 for 2Rx. + +#### 11.2.1.8 Requirements for PUSCH mapping Type B with non-slot transmission + +Apply the requirements defined in clause 8.2.8 for 2Rx. + +#### 11.2.1.9 Requirements for PUSCH for 2-step RA type + +Apply the requirements defined in clause 8.2.9 for 2Rx. + +#### 11.2.1.10 Requirements for interlaced PUSCH + +Apply the requirements defined in clause 8.2.10 for 2Rx. + +#### 11.2.1.11 Requirements for CG-UCI multiplexed on interlaced PUSCH + +Apply the requirements defined in clause 8.2.11 for 2Rx. + +#### 11.2.1.12 Requirements for TB processing over multi-slot PUSCH (TBoMS) + +Apply the requirements defined in clause 8.2.12 for 2Rx. + +### 11.2.1.13 Requirements for PUSCH with DM-RS bundling + +Apply the requirements for 2Rx defined in clause 8.2.13 for 2Rx. + +## 11.2.2 Requirements for BS type 2-O + +### 11.2.2.1 Requirements for PUSCH with transform precoding disabled + +#### 11.2.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 11.2.2.1.1-1: Test parameters for testing PUSCH** + +| Parameter | | Value | +|-----------------------------------------------------------------------------------|-------------------------------------------|--------------------------------------------------------------------------------------------------| +| Transform precoding | | Disabled | +| Default TDD UL-DL pattern (Note 1) | | 60 kHz and 120kHz SCS:
3D1S1U, S=10D:2G:2U
480kHz SCS:14D2S4U,
S1=12D:2G0U, S2=0D:6G:8U | +| 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 symbols | 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, n_{SCID}=0$ | +| Time domain resource | PUSCH mapping type | B | +| | Start symbol index | 0 | +| | Allocation length | 10 | +| Frequency domain resource | 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 | +| PT-RS configuration | Frequency density ( $K_{PT-RS}$ ) | 2, Disabled | +| | Time density ( $L_{PT-RS}$ ) | 1, Disabled | +| NOTE 1: The same requirements are applicable to TDD with different UL-DL patterns | | | + +#### 11.2.2.1.2 Minimum requirements + +The throughput shall be equal to or larger than the fraction of maximum throughput stated in the tables 11.2.2.1.2-1 to 11.2.2.1.2-10 at the given SNR for 1Tx and for 2Tx two-layer spatial multiplexing transmission. + +**Table 11.2.2.1.2-1: Minimum requirements for PUSCH with 70% of maximum throughput, 50 MHz channel bandwidth, 60 kHz SCS in FR2-1** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | PT-RS | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|-------|----------| +| 1 | 2 | Normal | TDLA30-300 Low | 70 % | G-FR2-A3-1 | pos0 | No | -2.0 | +| | | | | | G-FR2-A3-13 | pos1 | No | -2.2 | +| | | Normal | TDLA30-300 Low | 70 % | G-FR2-A4-1 | pos0 | Yes | 12.0 | +| | | | | | | | No | 11.5 | +| | | | | | G-FR2-A4-11 | pos1 | Yes | 10.7 | +| | | | | | | | No | 10.7 | +| | | Normal | TDLA30-75 Low | 70 % | G-FR2-A5-1 | pos0 | Yes | 13.7 | +| | | | | | | | No | 13.1 | +| | | | | | G-FR2-A5-6 | pos1 | Yes | 13.4 | +| | | | | | | | No | 12.9 | +| 2 | | Normal | TDLA30-300 Low | 70 % | G-FR2-A3-6 | pos0 | No | 1.5 | +| | | | | | G-FR2-A3-18 | pos1 | No | 1.2 | +| | | Normal | TDLA30-300 Low | 70 % | G-FR2-A7-1 | pos0 | Yes | 15.2 | +| | | | | | | | No | 14.3 | +| | | | | | G-FR2-A7-6 | pos1 | Yes | 13.8 | +| | | | | | | | No | 13.0 | + +**Table 11.2.2.1.2-2: Minimum requirements for PUSCH with 70% of maximum throughput, 100 MHz channel bandwidth, 60 kHz SCS in FR2-1** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | PT-RS | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|-------|----------| +| 1 | 2 | Normal | TDLA30-300 Low | 70 % | G-FR2-A3-2 | pos0 | No | -2.1 | +| | | | | | G-FR2-A3-14 | pos1 | No | -2.4 | +| | | | TDLA30-300 Low | 70 % | G-FR2-A4-2 | pos0 | Yes | 12.2 | +| | | | | | | | No | 11.2 | +| | | | | | G-FR2-A4-12 | pos1 | Yes | 11.2 | +| | | | | | | | No | 10.6 | +| | | | TDLA30-75 Low | 70 % | G-FR2-A5-2 | pos0 | Yes | 14.2 | +| | | | | | | | No | 13.3 | +| | | | | | G-FR2-A5-7 | pos1 | Yes | 13.7 | +| | | | | | | | No | 13.1 | +| 2 | | | TDLA30-300 Low | 70 % | G-FR2-A3-7 | pos0 | No | 1.5 | +| | | | | | G-FR2-A3-19 | pos1 | No | 1.2 | +| | | | TDLA30-300 Low | 70 % | G-FR2-A7-2 | pos0 | Yes | 16.0 | +| | | | | | | | No | 14.9 | +| | | | | | G-FR2-A7-7 | pos1 | Yes | 13.8 | +| | | | | | | | No | 13.1 | + +**Table 11.2.2.1.2-3: Minimum requirements for PUSCH with 70% of maximum throughput, 50 MHz channel bandwidth, 120 kHz SCS in FR2-1** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | PT-RS | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|-------|----------| +| 1 | 2 | Normal | TDLA30-300 Low | 70 % | G-FR2-A3-3 | pos0 | No | -1.8 | +| | | | | | G-FR2-A3-15 | pos1 | No | -2.1 | +| | | Normal | TDLA30-300 Low | 70 % | G-FR2-A4-3 | pos0 | Yes | 11.6 | +| | | | | | | | No | 10.9 | +| | | | | | G-FR2-A4-13 | pos1 | Yes | 10.9 | +| | | | | | | | No | 10.5 | +| | | Normal | TDLA30-75 Low | 70 % | G-FR2-A5-3 | pos0 | Yes | 13.7 | +| | | | | | | | No | 13.1 | +| | | | | | G-FR2-A5-8 | pos1 | Yes | 13.2 | +| | | | | | | | No | 13.0 | +| 2 | 2 | Normal | TDLA30-300 Low | 70 % | G-FR2-A3-8 | pos0 | No | 1.4 | +| | | | | | G-FR2-A3-20 | pos1 | No | 1.3 | +| | | Normal | TDLA30-300 Low | 70 % | G-FR2-A7-3 | pos0 | Yes | 14.2 | +| | | | | | | | No | 13.6 | +| | | | | | G-FR2-A7-8 | pos1 | Yes | 13.9 | +| | | | | | | | No | 13.1 | + +**Table 11.2.2.1.2-4: Minimum requirements for PUSCH with 70% of maximum throughput, 100 MHz channel bandwidth, 120 kHz SCS in FR2-1** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | PT-RS | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|-------|----------| +| 1 | 2 | Normal | TDLA30-300 Low | 70 % | G-FR2-A3-4 | pos0 | No | -2.4 | +| | | | | | G-FR2-A3-16 | pos1 | No | -2.5 | +| | | Normal | TDLA30-300 Low | 70 % | G-FR2-A4-4 | pos0 | Yes | 11.9 | +| | | | | | | | No | 10.5 | +| | | | | | G-FR2-A4-14 | pos1 | Yes | 11.1 | +| | | | | | | | No | 10.5 | +| | | Normal | TDLA30-75 Low | 70 % | G-FR2-A5-4 | pos0 | Yes | 13.5 | +| | | | | | | | No | 12.9 | +| | | | | | G-FR2-A5-9 | pos1 | Yes | 13.4 | +| | | | | | | | No | 12.8 | +| 2 | 2 | Normal | TDLA30-300 Low | 70 % | G-FR2-A3-9 | pos0 | No | 1.4 | +| | | | | | G-FR21-A3-21 | pos1 | No | 1.2 | +| | | Normal | TDLA30-300 Low | 70 % | G-FR2-A7-4 | pos0 | Yes | 13.9 | +| | | | | | | | No | 13.2 | +| | | | | | G-FR2-A7-9 | pos1 | Yes | 13.5 | +| | | | | | | | No | 12.9 | + +**Table 11.2.2.1.2-5: Minimum requirements for PUSCH with 70% of maximum throughput, 200 MHz channel bandwidth, 120 kHz SCS in FR2-1** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | PT-RS | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|-------|----------| +| 1 | 2 | Normal | TDLA30-300 Low | 70 % | G-FR2-A3-5 | pos0 | No | -2.1 | +| | | | | | G-FR2-A3-17 | pos1 | No | -2.4 | +| | | Normal | TDLA30-300 Low | 70 % | G-FR2-A4-5 | pos0 | Yes | 11.3 | +| | | | | | | | No | 10.9 | +| | | | | | G-FR2-A4-15 | pos1 | Yes | 11.2 | +| | | | | | | | No | 10.7 | +| | | Normal | TDLA30-75 Low | 70 % | G-FR2-A5-5 | pos0 | Yes | 14.1 | +| | | | | | | | No | 13.4 | +| | | | | | G-FR2-A5-10 | pos1 | Yes | 13.7 | +| | | | | | | | No | 13.3 | +| 2 | 2 | Normal | TDLA30-300 Low | 70 % | G-FR2-A3-10 | pos0 | No | 1.4 | +| | | | | | G-FR2-A3-22 | pos1 | No | 1.1 | +| | | Normal | TDLA30-300 Low | 70 % | G-FR2-A7-5 | pos0 | Yes | 14.0 | +| | | | | | | | No | 13.3 | +| | | | | | G-FR2-A7-10 | pos1 | Yes | 13.6 | +| | | | | | | | No | 13.0 | + +**Table 11.2.2.1.2-6: Minimum requirements for PUSCH with 30% of maximum throughput, 50 MHz channel bandwidth, 60 kHz SCS in FR2-1** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | PT-RS | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|-------|----------| +| 1 | 2 | Normal | TDLA30-300 Low | 30 % | G-FR2-A4-1 | pos0 | Yes | 4.0 | +| | | | | | | | No | 3.5 | +| | | | | | G-FR2-A4-11 | pos1 | Yes | 3.7 | +| | | | | | | | No | 3.1 | + +**Table 11.2.2.1.2-7: Minimum requirements for PUSCH with 30% of maximum throughput, 50 MHz channel bandwidth, 120 kHz SCS in FR2-1** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | PT-RS | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|-------|----------| +| 1 | 2 | Normal | TDLA30-300 Low | 30 % | G-FR2-A4-3 | pos0 | Yes | 4.0 | +| | | | | | | | No | 3.6 | +| | | | | | G-FR2-A4-13 | pos1 | Yes | 3.7 | +| | | | | | | | No | 3.2 | + +**Table 11.2.2.1.2-8: Test requirements for PUSCH with 70% of maximum throughput, 100 MHz Channel Bandwidth, 120 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | PT-RS | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|-------|----------| +| 1 | 2 | Normal | TDLA30-650 | 70 % | G-FR2-A3B-1 | pos1 | No | -0.2 | +| | | Normal | TDLA30-650 | 70 % | G-FR2-A4-21 | pos1 | Yes | 11.2 | +| | | Normal | TDLD30-200 | 70 % | G-FR2-A5-11 | pos1 | Yes | 12.5 | +| 2 | | Normal | TDLA30-650 | 70 % | G-FR2-A3B-6 | pos1 | No | 3.9 | +| | | Normal | TDLA30-650 | 70 % | G-FR2-A7-11 | pos1 | Yes | 13.6 | + +**Table 11.2.2.1.2-9: Test requirements for PUSCH with 70% of maximum throughput, 400 MHz Channel Bandwidth, 120 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | PT-RS | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|-------|----------| +| 1 | 2 | Normal | TDLA10-650 | 70 % | G-FR2-A3B-2 | pos1 | No | -0.2 | +| | | Normal | TDLA10-650 | 70 % | G-FR2-A4-22 | pos1 | Yes | 11.2 | +| | | Normal | TDLD10-200 | 70 % | G-FR2-A5-12 | pos1 | Yes | 12.6 | +| 2 | | Normal | TDLA10-650 | 70 % | G-FR2-A3B-7 | pos1 | No | 4 | +| | | Normal | TDLA10-650 | 70 % | G-FR2-A7-12 | pos1 | Yes | 14 | + +**Table 11.2.2.1.2-10: Test requirements for PUSCH with 70% of maximum throughput, 400 MHz Channel Bandwidth, 480 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | PT-RS | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|-------|----------| +| 1 | 2 | Normal | TDLA10-650 | 70 % | G-FR2-A3B-3 | pos1 | No | -0.5 | +| | | Normal | TDLA10-650 | 70 % | G-FR2-A4-23 | pos1 | Yes | 10.8 | +| | | Normal | TDLD10-200 | 70 % | G-FR2-A5-13 | pos1 | Yes | 12.8 | +| 2 | | Normal | TDLA10-650 | 70 % | G-FR2-A3B-8 | pos1 | No | 3.5 | +| | | Normal | TDLA10-650 | 70 % | G-FR2-A7-13 | pos1 | Yes | 13.8 | + +## 11.2.2.2 Requirements for PUSCH with transform precoding enabled + +### 11.2.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 11.2.2.2.1-1: Test parameters for testing PUSCH** + +| Parameter | | Value | +|------------------------------------------------------------------------------------|-------------------------------------------|--------------------------------------------------------------------------------------------------| +| Transform precoding | | Enabled | +| Default TDD UL-DL pattern (Note 1) | | 60 kHz and 120kHz SCS:
3D1S1U, S=10D:2G:2U
480kHz SCS:14D2S4U, S1=12D:2G0U,
S2=0D:6G:8U | +| 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 | 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 | B | +| | Start symbol | 0 | +| | Allocation length | 10 | +| Frequency domain resource assignment | RB assignment | FR2-1: 30 PRBs in the middle of the test bandwidth
FR2-2: Full applicable test bandwidth | +| | Frequency hopping | Disabled | +| Code block group based PUSCH transmission | | Disabled | +| PT-RS | | Not configured | +| NOTE 1: The same requirements are applicable to TDD with different UL-DL patterns. | | | + +### 11.2.2.2.2 Minimum requirements + +The throughput shall be equal to or larger than the fraction of maximum throughput stated in the tables 11.2.2.2.2-1 to 11.2.2.2.2-4 at the given SNR. + +**Table 11.2.2.2.2-1: Minimum requirements for PUSCH with 70% of maximum throughput, Type B, 50 MHz Channel Bandwidth, 60 kHz SCS in FR2-1** + +| Number of TX antennas | Number of demodulation branches | 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-300 Low | 70 % | G-FR2-A3-11 | pos0 | -1.8 | +| | | | | | G-FR2-A3-23 | pos1 | -1.9 | + +**Table 11.2.2.2.2-2: Minimum requirements for PUSCH with 70% of maximum throughput, Type B, 50 MHz Channel Bandwidth, 120 kHz SCS in FR2-1** + +| Number of TX antennas | Number of demodulation branches | 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-300 Low | 70 % | G-FR2-A3-12 | pos0 | -1.8 | +| | | | | | G-FR2-A3-24 | pos1 | -1.9 | + +**Table 11.2.2.2.2-3: Minimum requirements for PUSCH with 70% of maximum throughput, Type B, 100 MHz Channel Bandwidth, 120 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | 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-650 | 70 % | G-FR2-A3B-4 | pos1 | 0.1 | + +**Table 11.2.2.2.2-4: Minimum requirements for PUSCH with 70% of maximum throughput, Type B, 400 MHz Channel Bandwidth, 480 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | 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 | TDLA10-650 | 70 % | G-FR2-A3B-5 | pos1 | 0.2 | + +## 11.2.2.3 Requirements for UCI multiplexed on PUSCH + +### 11.2.2.3.1 General + +In the tests for UCI multiplexed on PUSCH, the UCI information only contains CSI part 1 and CSI part 2 information, and there is no HARQ-ACK information transmitted. + +The CSI part 1 block error probability (BLER) is defined as the probability of incorrectly decoding the CSI part 1 information when the CSI part 1 information is sent as follows: + +where: + +- #(false CSI part 1) denotes the number of incorrectly decoded CSI part 1 information transmitted occasions +- #(CSI part 1) denotes the number of CSI part 1 information transmitted occasions. + +The CSI part 2 block error probability is defined as the probability of incorrectly decoding the CSI part 2 information when the CSI part 2 information is sent as follows: + +where: + +- #(false CSI part 2) denotes the number of incorrectly decoded CSI part 2 information transmitted occasions +- #(CSI part 2) denotes the number of CSI part 2 information transmitted occasions. + +The number of UCI information bit payload per slot is defined for two cases as follows: + +- 5 bits in CSI part 1, 2 bits in CSI part 2 +- 20 bits in CSI part 1, 20 bits in CSI part 2 + +The 7bits UCI 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 40bits UCI information case is assumed random information bits selection. + +In both tests, PUSCH data, CSI part 1 and CSI part 2 information are transmitted simultaneously. + +**Table 11.2.2.3.1-1: Test parameters for testing UCI multiplexed on PUSCH** + +| Parameter | | Value | | +|------------------------------------------------------------------------------------|------------------------------------------------------------------|-------------------------------------|---------| +| Transform precoding | | Disabled | | +| Default TDD UL-DL pattern (Note 1) | | 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 | 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 | B | | +| | Start symbol | 0 | | +| | Allocation length | 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 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 TDD with different UL-DL patterns. | | | | + +### 11.2.2.3.2 Minimum requirements + +The CSI part 1 block error probability shall not exceed 0.1% at the SNR given in table 11.2.2.3.2-1 and table 11.2.2.3.2-2. The CSI part 2 block error probability shall not exceed 1% at the SNR given in table 11.2.2.3.2-3 and table 11.2.2.3.2-4. + +**Table 11.2.2.3.2-1: Minimum 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 | 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 | TDLA30-300 Low | 7(5,2) | pos0 | G-FR2-A4-3 | 7.2 | +| | 2 | Normal | TDLA30-300 Low | 40(20,20) | pos0 | G-FR2-A4-3 | 5.8 | +| | 2 | Normal | TDLA30-300 Low | 7(5,2) | pos1 | G-FR2-A4-13 | 7.8 | +| | 2 | Normal | TDLA30-300 Low | 40(20,20) | pos1 | G-FR2-A4-13 | 5.9 | + +**Table 11.2.2.3.2-2: Minimum requirements for UCI multiplexed on PUSCH, Type B, Without PTRS, CSI part 1, 50 MHz Channel Bandwidth, 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | 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 | TDLA30-300 LOW | 7(5,2) | pos0 | G-FR2-A4-3 | 7.1 | +| | 2 | Normal | TDLA30-300 LOW | 40(20,20) | pos0 | G-FR2-A4-3 | 5.8 | +| | 2 | Normal | TDLA30-300 LOW | 7(5,2) | pos1 | G-FR2-A4-13 | 7.3 | +| | 2 | Normal | TDLA30-300 LOW | 40(20,20) | pos1 | G-FR2-A4-13 | 5.5 | + +**Table 11.2.2.3.2-3: Minimum requirements for UCI multiplexed on PUSCH, Type B, with PTRS, CSI part 2, 50 MHz Channel Bandwidth, 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | 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 | TDLA30-300 Low | 7(5,2) | pos0 | G-FR2-A4-3 | 1.1 | +| | 2 | Normal | TDLA30-300 Low | 40(20,20) | pos0 | G-FR2-A4-3 | 4.0 | +| | 2 | Normal | TDLA30-300 Low | 7(5,2) | pos1 | G-FR2-A4-13 | 1.3 | +| | 2 | Normal | TDLA30-300 Low | 40(20,20) | pos1 | G-FR2-A4-13 | 4.0 | + +**Table 11.2.2.3.2-3: Minimum requirements for UCI multiplexed on PUSCH, Type B, with PTRS, CSI part 2, 50 MHz Channel Bandwidth, 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | 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 | TDLA30-300 Low | 7(5,2) | pos0 | G-FR2-A4-3 | 1.1 | +| | 2 | Normal | TDLA30-300 Low | 40(20,20) | pos0 | G-FR2-A4-3 | 4.0 | +| | 2 | Normal | TDLA30-300 Low | 7(5,2) | pos1 | G-FR2-A4-13 | 1.3 | +| | 2 | Normal | TDLA30-300 Low | 40(20,20) | pos1 | G-FR2-A4-13 | 4.0 | + +**Table 11.2.2.3.2-4: Minimum requirements for UCI multiplexed on PUSCH, Type B, Without PTRS, CSI part 2, 50 MHz Channel Bandwidth, 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | 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 | TDLA30-300 Low | 7(5,2) | pos0 | G-FR2-A4-3 | 1.1 | +| | 2 | Normal | TDLA30-300 Low | 40(20,20) | pos0 | G-FR2-A4-3 | 3.9 | +| | 2 | Normal | TDLA30-300 Low | 7(5,2) | pos1 | G-FR2-A4-13 | 1.2 | +| | 2 | Normal | TDLA30-300 Low | 40(20,20) | pos1 | G-FR2-A4-13 | 3.7 | + +## 11.2.2.4 Requirements for PUSCH for 2-step RA type + +### 11.2.2.4.1 General + +The performance requirement of PUSCH for 2-step RA type is determined by a minimum required block error rate of MsgA for a given SNR for the FRCs listed in annex A. The performance requirements assume that the precedent preamble of MsgA is correctly detected in a 2-step RA type procedure and no HARQ retransmissions. + +The performance requirements are applicable for wide area and medium range BS that support 2-step RA type. The performance requirements are not applied for a local area BS that supports 2-step RA type. + +**Table 11.2.2.4.1-1: Test parameters for testing PUSCH for 2-step RA type** + +| Parameter | Value | +|----------------------|--------------------------------------------| +| Transform precoding | Disabled | +| Channel bandwidth | 60 kHz SCS: 50 MHz
120 kHz SCS: 100 MHz | +| MCS | 2 | +| DM-RS | DM-RS configuration type | +| | 1 | +| | DM-RS duration | +| | single-symbol DM-RS | +| | Additional DM-RS symbols | +| | pos1 | +| | Number of DM-RS CDM group(s) without data | +| Time domain resource | Ratio of PUSCH EPRE to DM-RS EPRE | +| | -3 dB | +| | DM-RS port(s) | +| | {0} | +| | DM-RS sequence generation | +| | $N_{ID}=0, n_{SCID}=0$ | +| | PUSCH mapping type | +| | B | +| | Start symbol | +| | 0 | +| | Allocation length | +| | 10 | + +| | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------|----------| +| Frequency domain resource | RB assignment | 2 PRB | +| | Starting PRB index | 0 | +| | Frequency hopping | Disabled | +| Time Offset (TO) | 60 kHz SCS: 0 to 0.6
120kHz SCS: 0 to 0.5 | | +| Note1: The power ratio between preamble and msgA is assumed to be sufficient to achieve 100% preamble detection. The SNR for the requirement is defined on the msgA PUSCH. | | | + +### 11.2.2.4.2 Minimum requirements + +The block error rate of MsgA shall be equal to or smaller than 1% at the given SNR. + +**Table 11.2.2.4.2-1 Minimum requirements of PUSCH for 2-step RA type with mapping type B** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Channel Bandwidth [MHz] | SCS [kHz] | Propagation conditions and correlation matrix (Annex G) | FRC (Annex A) | SNR [dB] | +|-----------------------|-----------------------|---------------|-------------------------|-----------|---------------------------------------------------------|---------------|----------| +| 1 | 2 | Normal | 50 | 60 | TDLA30-300 low | G-FR2-A3-25 | 8. 7 | +| | | | 100 | 120 | TDLA30-300 low | G-FR2-A3-26 | 8. 3 | + +### 11.2.2.5 Requirements for PUSCH repetition Type A + +#### 11.2.2.5.1 General + +The performance requirement of PUSCH is determined by a maximum block error rate (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 retransmissions. + +**Table 11.2.2.5.1-1: Test parameters for testing PUSCH repetition Type A** + +| Parameter | Value | +|-------------------------------------------|--------------------------------------------| +| Transform precoding | Disabled | +| Default TDD UL-DL pattern (Note 1) | 60 kHz and 120kHz SCS: 3D1S1U, S=10D:2G:2U | +| HARQ | Maximum number of HARQ transmissions | +| | 4 | +| DM-RS | RV sequence | +| | 0, 3, 0, 3 | +| | DM-RS configuration type | +| | 1 | +| | DM-RS duration | +| | single-symbol DM-RS | +| | Additional DM-RS symbols | +| Time domain resource | Number of DM-RS CDM group(s) without data | +| | 2 | +| | Ratio of PUSCH EPRE to DM-RS EPRE | +| | -3 dB | +| Frequency domain resource | DM-RS port(s) | +| | 0 | +| | DM-RS sequence generation | +| | $N_{ID}=0, n_{SCID}=0$ | +| Code block group based PUSCH transmission | PUSCH mapping type | +| | B | +| | Start symbol index | +| | 0 | +| PT-RS configuration | Allocation length | +| | 10 | +| PT-RS configuration | PUSCH aggregation factor (Note 2) | +| | n8 | +| PT-RS configuration | RB assignment | +| | Full applicable test bandwidth | +| PT-RS configuration | Frequency hopping | +| | Disabled | +| PT-RS configuration | Frequency density ( $K_{PT-RS}$ ) | +| | Disabled | +| PT-RS configuration | Time density ( $L_{PT-RS}$ ) | +| | Disabled | + +NOTE 1: The effective RV sequence is {0,2,3,1} with slot aggregation +NOTE 2: 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 + +### 11.2.2.5.2 Minimum requirements + +The BLER shall be equal to or smaller than the required target BLER for the FRCs stated in tables 11.2.2.5.2-1 to 11.2.2.5.2-4 at the given SNR for 1Tx. FRCs are defined in annex A. Unless stated otherwise, the MIMO correlation matrices for the gNB are defined in annex G for low correlation. + +**Table 11.2.2.5.2-1: Minimum requirements for PUSCH, TypeB, 50 MHz channel bandwidth, 60 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Target BLER | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|-------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLA30-300 | 1% (Note1) | G-FR2-A3A-5 | Pos1 | -11.9 | + +NOTE 1: BLER is defined as residual BLER, i.e. ratio of incorrectly received transport blocks/sent transport blocks, independently of the number of HARQ transmission(s) for each transport block + +**Table 11.2.2.5.2-2: Minimum requirements for PUSCH, TypeB, 100 MHz channel bandwidth, 60 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Target BLER | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|-------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLA30-300 | 1% (Note1) | G-FR2-A3A-6 | Pos1 | -12.2 | + +NOTE 1: BLER is defined as residual BLER, i.e. ratio of incorrectly received transport blocks/sent transport blocks, independently of the number of HARQ transmission(s) for each transport block + +**Table 11.2.2.5.2-3: Minimum requirements for PUSCH, TypeB, 50 MHz channel bandwidth, 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Target BLER | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|-------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLA30-300 | 1% (Note1) | G-FR2-A3A-7 | Pos1 | -11.2 | + +NOTE 1: BLER is defined as residual BLER, i.e. ratio of incorrectly received transport blocks/sent transport blocks, independently of the number of HARQ transmission(s) for each transport block + +**Table 11.2.2.5.2-4: Minimum requirements for PUSCH, TypeB, 100 MHz channel bandwidth, 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Target BLER | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|-------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLA30-300 | 1% (Note1) | G-FR2-A3A-8 | Pos1 | -11.7 | + +NOTE 1: BLER is defined as residual BLER, i.e. ratio of incorrectly received transport blocks/sent transport blocks, independently of the number of HARQ transmission(s) for each transport block + +## 11.2.2.6 Requirements for PUSCH mapping Type B with non-slot transmission + +### 11.2.2.6.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 do not assume HARQ retransmissions. + +**Table 11.2.2.6.1-1: Test parameters for testing PUSCH mapping Type B with non-slot transmission** + +| Parameter | | Value | +|-----------------------------------------------------------------------------------|-------------------------------------------|-----------------------------------------------| +| Transform precoding | | Disabled | +| Default TDD UL-DL pattern (Note 1) | | 60 kHz and 120kHz 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 symbols | Pos0 | +| | 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, n_{SCID}=0$ | +| Time domain resource | PUSCH mapping type | B | +| | Start symbol index | 0 | +| | Allocation length | 4 | +| Frequency domain resource | RB assignment | Full applicable test bandwidth | +| | Frequency hopping | Disabled | +| Code block group based PUSCH transmission | | Disabled | +| PT-RS configuration | Frequency density ( $K_{PT-RS}$ ) | Disabled | +| | Time density ( $L_{PT-RS}$ ) | Disabled | +| NOTE 1: The same requirements are applicable to TDD with different UL-DL patterns | | | + +### 11.2.2.6.2 Minimum requirements + +The throughput shall be equal to or larger than the fraction of maximum throughput for the FRCs stated in tables 11.2.2.6.2-1 to 11.2.2.6.2-4 at the given SNR for 1Tx. FRCs are defined in an annex A. Unless stated otherwise, the MIMO correlation matrices for the gNB are defined in annex G for low correlation. + +**Table 11.2.2.6.2-1: Minimum requirements for PUSCH, Type B, 50 MHz channel bandwidth, 60 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | 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-300 | 70% | G-FR2-A3A-1 | Pos0 | -4.4 | + +**Table 11.2.2.6.2-2: Minimum requirements for PUSCH, Type B, 100 MHz channel bandwidth, 60 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | 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-300 | 70% | G-FR2-A3A-2 | Pos0 | -5.0 | + +**Table 11.2.2.6.2-3: Minimum requirements for PUSCH, Type B, 50 MHz channel bandwidth, 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | 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-300 | 70% | G-FR2-A3A-3 | Pos0 | -4.1 | + +**Table 11.2.2.6.2-4: Minimum requirements for PUSCH, Type B, 100 MHz channel bandwidth, 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | 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-300 | 70% | G-FR2-A3A-4 | Pos0 | -5.1 | + +## 11.2.2.7 Requirements for PUSCH for high speed train + +### 11.2.2.7.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. The performance requirements for high speed train are optional and only applicable for FR2-1 below 30GHz. + +The performance requirements for PUSCH high speed train apply to Wide Area Base Stations and Medium Range Base Stations (subject to declaration). + +**Table 11.2.2.7.1-1: Test parameters for testing high speed train** + +| Parameter | Value | +|-----------------------------------------------------------------------------------|--------------------------------------------------| +| Transform precoding | Disabled | +| Default TDD UL-DL pattern (Note 1) | 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 symbols Pos0 or Pos1 or 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, n_{SCID}=0$ | +| Time domain resource | PUSCH mapping type B | +| | Start symbol index 0 | +| | Allocation length 10 | +| Frequency domain resource | RB assignment Full applicable test bandwidth | +| | Frequency hopping Disabled | +| Code block group based PUSCH transmission | Disabled | +| PT-RS configuration | Frequency density ( $K_{PT-RS}$ ) 2 | +| | Time density ( $L_{PT-RS}$ ) 1 | +| NOTE 1: The same requirements are applicable to TDD with different UL-DL patterns | | + +### 11.2.2.7.2 Minimum requirements + +The throughput shall be equal to or larger than the fraction of maximum throughput for the FRCs stated in tables 11.2.2.7.2-1 to 11.2.2.7.2-4 at the given SNR for 1Tx. FRCs are defined in an annex A. Unless stated otherwise, the MIMO correlation matrices for the gNB are defined in annex G for low correlation. + +**Table 11.2.2.7.2-1: Minimum requirements for PUSCH, Type B, 50 MHz channel bandwidth, 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | 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 | Scenario 4-BI-NR350, FR2 | 70% | G-FR2-A10-1 | pos0 | 12.9 | +| 1 | 2 | Normal | Scenario 4-BI-NR350, FR2 | 70% | G-FR2-A10-3,
G-FR2-A10-5 | pos1, pos2 | 12.5 | + +**Table 11.2.2.7.2-2: Minimum requirements for PUSCH, Type B, 200 MHz channel bandwidth, 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | 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 | Scenario 4-BI-NR350, FR2 | 70% | G-FR2-A10-2 | pos0 | 12.8 | +| 1 | 2 | Normal | Scenario 4-BI-NR350, FR2 | 70% | G-FR2-A10-4,
G-FR2-A10-6 | pos1, pos2 | 12.3 | + +## 11.2.2.8 Requirements for UL timing adjustment + +### 11.2.2.8.1 General + +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. The performance requirements for UL timing adjustment scenario Y defined in Annex G.4 are optional and only applicable for FR2-1 below 30GHz. + +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 Tables A.10-4, A.10-5, and A.10-6 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, Doppler shift is not taken into account. + +**Table 11.2.2.8.1-1 Test parameters for testing UL timing adjustment** + +| Parameter | | Value | +|--------------------------------------|----------------------------------------------------|--------------------------------------------------------------------------------------------------------| +| Transform precoding | | Disabled | +| Uplink-downlink allocation for TDD | | 120 kHz SCS:
3D1S1U, S=10D:2G:2U | +| Channel bandwidth | | 120 kHz SCS: 50MHz, 200 MHz | +| 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 | +| | DM-RS position ( $l_0$ ) | 2 | +| | Additional DM-RS position | pos0, pos1, 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} | +| Time domain resource assignment | DM-RS sequence generation | $N_{ID}^0=0, n_{SCID}=0$ for moving UE
$N_{ID}^0=1, n_{SCID}=1$ for stationary UE | +| | PUSCH mapping type | B | +| | Allocation length | 10 | +| Frequency domain resource assignment | RB assignment | 50 MHz CBW/120kHz SCS: 16 RB for each UE
200MHz CBW/120kHz SCS: 66 RB for each UE | +| | Starting PRB index | Moving UE: 0
Stationary UE: 16 for 50MHz CBW, 66 for 200MHz CBW for SCS 120kHz | +| | Frequency hopping | Disabled | +| SRS resource allocation | Slots in which sounding RS is transmitted (Note 1) | For TDD:
- last symbol in slot #3 in radio frames for 120KHz | +| | SRS resource allocation | 120 kHz SCS:
- $C_{SRS} = 9, B_{SRS} = 0$ , for 32 RB
- $C_{SRS} = 33, B_{SRS} = 0$ , for 132 RB | + +NOTE 1. The transmission of SRS is optional. And the transmission comb and SRS periodic are configured as $K_{TC} = 2$ , and $T_{SRS} = 80$ respectively. + +### 11.2.2.8.2 Minimum requirements 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 11.2.2.8.2-1 for mapping type B. + +Annex A for the moving UE at the SNR given in table 11.2.2.8.2-1 for mapping type B. + +**Table 11.2.2.8.2-1 Minimum 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 | 50 | 120 | Scenario Y | G-FR2-A10-7 | 9.1 | +| | | | | | Scenario Y | G-FR2-A10-9, G-FR2-A10-11 | 8.8 | +| | | | 200 | 120 | Scenario Y | G-FR2-A10-8 | 9.0 | +| | | | | | Scenario Y | G-FR2-A10-10, G-FR2-A10-12 | 8.9 | + +### 11.2.2.9 Requirements for TB processing over multi-slot PUSCH (TBoMS) + +#### 11.2.2.9.1 General + +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. + +**Table 11.2.2.9.1-1: Test parameters for testing PUSCH TBoMS** + +| Parameter | | Value | +|-----------------------------------------------------------------------------------|-------------------------------------------|-----------------------------------------------| +| Transform precoding | | Disabled | +| Default TDD UL-DL pattern (Note 1) | | 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 | +| | 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 | 10 | +| | Number of slots allocated for TBoMS PUSCH | 2 | +| | 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 | +| PT-RS configuration | Frequency density ( $K_{PT-RS}$ ) | Disabled | +| | Time density ( $L_{PT-RS}$ ) | Disabled | +| Note 1: The same requirements are applicable to TDD with different UL-DL pattern. | | | + +#### 11.2.2.9.2 Minimum requirements + +The throughput shall be equal to or larger than the fraction of maximum throughput for the FRCs stated in tables 11.2.2.9.2-1 to 11.2.2.9.2-2 at the given SNR. FRCs are defined in annex A. + +**Table 11.2.2.9.2-1: Minimum requirements for PUSCH TBoMS, Type B, 50 MHz channel bandwidth, 60 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 | TDD | TDLA30-300 Low | 70% | G-FR2-A3-27 | pos1 | -2.6 | + +**Table 11.2.2.9.2-2: Minimum requirements for PUSCH TBoMS, Type B, 50 MHz channel bandwidth, 120 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 | TDD | TDLA30-300 Low | 70% | G-FR2-A3-28 | pos1 | -2.4 | + +## 11.2.2.10 Requirements for PUSCH with DM-RS bundling + +### 11.2.2.10.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 11.2.2.10.1-1: Test parameters for testing PUSCH with DM-RS bundling** + +| Parameter | | Value | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------|----------------------------------------------------------| +| Transform precoding | | Disabled | +| Example TDD UL-DL pattern (Note 1) | | 60 kHz and 120kHz SCS:
DDSUU or DSUUU,
S=10D:2G:2U | +| 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 symbols | 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, n_{SCID}=0$ | +| Time domain resource | PUSCH mapping type | B | +| | Start symbol index | 0 | +| | Allocation length | 14 | +| | PUSCH aggregation factor | n2 | +| pusch-TimeDomainWindowLength | | 2 slots | +| Frequency domain resource | RB assignment | Full applicable test bandwidth | +| | Frequency hopping | Disabled | +| Code block group based PUSCH transmission | | Disabled | +| PT-RS configuration | Frequency density ( $K_{PT-RS}$ ) | Disabled | +| | Time density ( $L_{PT-RS}$ ) | 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. | | | + +### 11.2.2.10.2 Minimum requirements + +The throughput shall be equal to or larger than the fraction of maximum throughput stated in the tables 11.2.2.10.2-1 and 11.2.2.10.2-2 at the given SNR for 1Tx. FRCs are defined in annex A. Unless stated otherwise, the MIMO correlation matrices for the gNB are defined in annex G for low correlation. + +**Table 11.2.2.10.2-1: Minimum requirements for PUSCH, TypeB, 50 MHz channel bandwidth, 60 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | 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-75 | 70% | G-FR2-A3B-1 | pos1 | -3.9 | + +**Table 11.2.2.10.2-2: Minimum requirements for PUSCH, TypeB, 50 MHz channel bandwidth, 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | 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-75 | 70% | G-FR2-A3B-2 | pos1 | -3.5 | + +## 11.3 Performance requirements for PUCCH + +### 11.3.1 Requirements for BS 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 2 Rx. + +#### 11.3.1.3 Performance requirements for PUCCH format 1 + +Apply the requirements defined in sub-clause 8.3.3 for 2Rx. + +#### 11.3.1.4 Performance requirements for PUCCH format 2 + +Apply the requirements defined in clause 8.3.4 for 2Rx. + +#### 11.3.1.5 Performance requirements for PUCCH format 3 + +Apply the requirements defined in clause 8.3.5 for 2Rx. + +#### 11.3.1.6 Performance requirements for PUCCH format 4 + +Apply the requirements defined in clause 8.3.6 for 2Rx. + +#### 11.3.1.7 Performance requirements for multi-slot PUCCH + +Apply the requirements defined in clause 8.3.7 for 2Rx. + +#### 11.3.1.8 Performance requirements for PUCCH format 1 with DMRS bundling + +Apply the requirements defined in clause 8.3.12 for 2Rx. + +### 11.3.1.9 Performance requirements for PUCCH format 3 with DMRS bundling + +Apply the requirements defined in clause 8.3.13 for 2Rx. + +### 11.3.1.10 Performance requirements for sub-slot repetition PUCCH format 0 + +Apply the requirements defined in clause 8.3.14 for 2Rx. + +## 11.3.2 Requirements for BS type 2-O + +### 11.3.2.1 DTX to ACK probability + +Apply the requirements defined in clause 8.3.1. + +### 11.3.2.2 Performance requirements for PUCCH format 0. + +#### 11.3.2.2.1 General + +The ACK missed detection probability is the probability of not detecting an ACK when an ACK was sent. + +**Table 11.3.2.2.1-1: Test Parameters** + +| Parameter | Test | +|--------------------------------------|-------------------------------------------------| +| Number of UCI information bits | 1 | +| Number of PRBs | FR2-1: 1.
FR2-2: 1,16 | +| 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 | + +The transient period as specified in TS 38.101-1 [17] clause 6.3.3.1 and TS 38.101-2 [18] clause 6.3.3.1 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. + +#### 11.3.2.2.2 Minimum requirements + +The ACK missed detection probability shall not exceed 1% at the SNR given in table 11.3.2.2.2-1 to 11.3.2.2.2-4. + +**Table 11.3.2.2.2-1: Minimum requirements for PUCCH format 0 and 60 kHz SCS in FR2-1** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex G) | Number of OFDM symbols | Channel bandwidth / SNR (dB) | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------|------------------------------|---------| +| | | | | 50 MHz | 100 MHz | +| 1 | 2 | TDLA30-300 Low | 1 | 9.3 | 9.0 | +| | | | 2 | 4.2 | 4.0 | + +**Table 11.3.2.2.2-2: Minimum requirements for PUCCH format 0 and 120 kHz SCS in FR2-1** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex G) | Number of OFDM symbols | Channel bandwidth / SNR (dB) | | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------|------------------------------|---------|---------| +| | | | | 50 MHz | 100 MHz | 200 MHz | +| 1 | 2 | TDLA30-300 Low | 1 | 9.5 | 9.2 | 9.7 | +| | | | 2 | 4.1 | 3.8 | 4.0 | + +**Table 11.3.2.2.2-3: Minimum requirements for PUCCH format 0 and 120 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex G) | Number of OFDM symbols | Number of PRBs | Channel bandwidth / SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------|----------------|------------------------------| +| | | | | | 100 MHz | +| 1 | 2 | TDLA30-650 Low | 1 | 1 | 9.6 | +| | | | 2 | 16 | -5.8 | + +**Table 11.3.2.2.2-4: Minimum requirements for PUCCH format 0 and 480 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex G) | Number of OFDM symbols | Number of PRBs | Channel bandwidth / SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------|----------------|------------------------------| +| | | | | | 400 MHz | +| 1 | 2 | TDLA10-650 Low | 1 | 1 | 9.6 | +| | | | 2 | 16 | -4.8 | + +### 11.3.2.3 Performance requirements for PUCCH format 1. + +#### 11.3.2.3.1 NACK to ACK requirements + +##### 11.3.2.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 11.3.2.3.1.1-1: Test Parameters** + +| Parameter | Test | +|---------------------------------------------------------|----------------------------------------| +| Number of information bits | 2 | +| Number of PRBs | FR2-1:1
FR2-2:1,16 | +| 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-1 [17] and TS 38.101-2 [18] clause 6.3.3.1 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. + +#### 11.3.2.3.1.2 Minimum requirements + +The NACK to ACK probability shall not exceed 0.1% at the SNR given in Table 11.3.2.3.1.2-1 and Table 11.3.2.3.1.2-4. + +**Table 11.3.2.3.1.2-1: Minimum requirements for PUCCH format 1 with 60 kHz SCS in FR2-1** + +| Number of TX antennas | Number of Demodulation Branches | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | Channel bandwidth / SNR (dB) | | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------------------------------|---------| +| | | | | 50 MHz | 100 MHz | +| 1 | 2 | Normal | TDLA30-300 Low | -1.2 | -4.2 | + +**Table 11.3.2.3.1.2-2: Minimum requirements for PUCCH format 1 with 120 kHz SCS in FR2-1** + +| Number of TX antennas | Number of Demodulation Branches | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | Channel bandwidth / SNR (dB) | | | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------------------------------|---------|---------| +| | | | | 50 MHz | 100 MHz | 200 MHz | +| 1 | 2 | Normal | TDLA30-300 Low | -3.9 | -3.9 | -3.0 | + +**Table 11.3.2.3.1.2-3: Minimum requirements for PUCCH format 1 and 120 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | Number of RBs | Channel bandwidth / SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|---------------|------------------------------| +| | | | | | 100 MHz | +| 1 | 2 | Normal | TDLA30-650 Low | 1 | -2.7 | +| | | | | 16 | -13.1 | + +**Table 11.3.2.3.1.2-4: Minimum requirements for PUCCH format 1 and 480 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | Number of RBs | Channel bandwidth / SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|---------------|------------------------------| +| | | | | | 400 MHz | +| 1 | 2 | Normal | TDLA10-650 Low | 1 | -2.9 | +| | | | | 16 | -13.8 | + +### 11.3.2.3.2 ACK missed detection requirements + +#### 11.3.2.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 11.3.2.3.1.1-1 are configured. + +The transient period as specified in TS 38.101-1 [17] and TS 38.101-2 [18] clause 6.3.3.1 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. + +#### 11.3.2.3.2.2 Minimum requirements + +The ACK missed detection probability shall not exceed 1% at the SNR given in Table 11.3.2.3.2.2-1 to Table 11.3.2.3.2.4. + +**Table 11.3.2.3.2.2-1: Minimum requirements for PUCCH format 1 with 60 kHz SCS in FR2-1** + +| Number of TX antennas | Number of Demodulation Branches | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | Channel bandwidth / SNR (dB) | | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------------------------------|---------| +| | | | | 50 MHz | 100 MHz | +| 1 | 2 | Normal | TDLA30-300 Low | -3.9 | -4.2 | + +**Table 11.3.2.3.2.2-2: Minimum requirements for PUCCH format 1 with 120 kHz SCS in FR2-1** + +| Number of TX antennas | Number of Demodulation Branches | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | Channel bandwidth / SNR (dB) | | | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------------------------------|---------|---------| +| | | | | 50 MHz | 100 MHz | 200 MHz | +| 1 | 2 | Normal | TDLA30-300 Low | -4.7 | -4.6 | -4.6 | + +**Table 11.3.2.3.2.2-3: Minimum requirements for PUCCH format 1 and 120 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | Number of RBs | Channel bandwidth / SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|---------------|------------------------------| +| | | | | | 100 MHz | +| 1 | 2 | Normal | TDLA30-650 Low | 1 | -4.1 | +| | | | | 16 | -14.8 | + +**Table 11.3.2.3.2.2-4: Minimum requirements for PUCCH format 1 and 480 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | Number of RBs | Channel bandwidth / SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|---------------|------------------------------| +| | | | | | 400 MHz | +| 1 | 2 | Normal | TDLA10-650 Low | 1 | -4.2 | +| | | | | 16 | -14.4 | + +### 11.3.2.4 Performance requirements for PUCCH format 2 + +#### 11.3.2.4.1 ACK missed detection requirements + +##### 11.3.2.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 11.3.2.4.1.1-1: Test Parameters** + +| Parameter | Value | +|------------------------------------|--------------| +| Modulation order | QSPK | +| 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$ | + +##### 11.3.2.4.1.2 Minimum requirements + +The ACK missed detection probability shall not exceed 1% at the SNR given in table 11.3.2.4.1.2-1 to 11.3.2.4.1.2-4 for 4UCI bits. + +**Table 11.3.2.4.1.2-1: Minimum requirements for PUCCH format 2 with 60 kHz SCS in FR2-1** + +| Number of TX antennas | Number of Demodulation Branches | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | Channel bandwidth / SNR (dB) | | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------------------------------|---------| +| | | | | 50 MHz | 100 MHz | +| 1 | 2 | Normal | TDLA30-300 Low | 6.7 | 7.2 | + +**Table 11.3.2.4.1.2-2: Minimum requirements for PUCCH format 2 with 120 kHz SCS in FR2-1** + +| Number of TX antennas | Number of Demodulation Branches | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | Channel bandwidth / SNR (dB) | | | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------------------------------|---------|---------| +| | | | | 50 MHz | 100 MHz | 200 MHz | +| 1 | 2 | Normal | TDLA30-300 Low | 6.6 | 6.3 | 6.6 | + +**Table 11.3.2.4.1.2-3: Minimum requirements for PUCCH format 2 and 120 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | Channel bandwidth / SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------------------------------| +| | | | | 100 MHz | +| 1 | 2 | Normal | TDLA30-650 Low | 5.4 | + +**Table 11.3.2.4.1.2-4: Minimum requirements for PUCCH format 2 and 480 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | Channel bandwidth / SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------------------------------| +| | | | | 400 MHz | +| 1 | 2 | Normal | TDLA10-650 Low | 5.4 | + +#### 11.3.2.4.2 UCI BLER performance requirements + +##### 11.3.2.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 part 2. + +The transient period as specified in TS 38.101-1 [17] and TS 38.101-2 [18] clause 6.3.3.1 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 performance only applies to the PUCCH format 2 with 22 UCI bits. + +**Table 11.3.2.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$ | + +##### 11.3.2.4.2.2 Minimum requirements + +The UCI block error probability shall not exceed 1% at the SNR given in table 11.3.2.4.2.2-1 to 11.3.2.4.2.2-4 for 22 UCI bits. + +**Table 11.3.2.4.2.2-1: Minimum requirements for PUCCH format 2 with 60 kHz SCS in FR2-1** + +| Number of TX antennas | Number of Demodulation Branches | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | Channel bandwidth / SNR (dB) | | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------------------------------|---------| +| | | | | 50 MHz | 100 MHz | +| 1 | 2 | Normal | TDLA30-300 Low | 2.6 | 1.1 | + +**Table 11.3.2.4.2.2-2: Minimum requirements for PUCCH format 2 with 120 kHz SCS in FR2-1** + +| Number of TX antennas | Number of Demodulation Branches | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | Channel bandwidth / SNR (dB) | | | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------------------------------|---------|---------| +| | | | | 50 MHz | 100 MHz | 200 MHz | +| 1 | 2 | Normal | TDLA30-300 Low | 1.2 | 1.2 | 1.1 | + +**Table 11.3.2.4.2.2-3: Minimum requirements for PUCCH format 2 and 120 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | Channel bandwidth / SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------------------------------| +| | | | | 100 MHz | +| 1 | 2 | Normal | TDLA30-650 Low | 2.1 | + +**Table 11.3.2.4.2.2-4: Minimum requirements for PUCCH format 2 and 480 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | Channel bandwidth / SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------------------------------| +| | | | | 400 MHz | +| 1 | 2 | Normal | TDLA10-650 Low | 2.6 | + +### 11.3.2.5 Performance requirements for PUCCH format 3 + +#### 11.3.2.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 part 2. + +The transient period as specified in TS 38.101-2 [18] clause 6.3.3.1 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. + +**Table 11.3.2.5.1-1: 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 | + +#### 11.3.2.5.2 Minimum requirements + +The UCI block error probability shall not exceed 1% at the SNR given in Table 11.3.2.5.2-1 to 11.3.2.5.2-4. + +**Table 11.3.2.5.2-1: Required SNR for PUCCH format 3 with 60kHz SCS in FR2-1** + +| Test Number | Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | Additional DM-RS configuration | Channel Bandwidth / SNR (dB) | | +|-------------|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|------------------------------|---------| +| | | | | | | 50 MHz | 100 MHz | +| 1 | 1 | 2 | Normal | TDLA30-300 Low | No additional DM-RS | 1.6 | 0.7 | +| | | | | | Additional DM-RS | 1.3 | 0.9 | +| 2 | 1 | 2 | Normal | TDLA30-300 Low | No additional DM-RS | 3.0 | 2.4 | + +**Table 11.3.2.5.2-2: Required SNR for PUCCH format 3 with 120kHz SCS in FR2-1** + +| Test Number | Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | Additional DM-RS configuration | Channel Bandwidth / SNR (dB) | | | +|-------------|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|------------------------------|---------|---------| +| | | | | | | 50 MHz | 100 MHz | 200 MHz | +| 1 | 1 | 2 | Normal | TDLA30-300 Low | No additional DM-RS | 1.4 | 0.7 | 0.7 | +| | | | | | Additional DM-RS | 1.3 | 1.4 | 0.9 | +| 2 | 1 | 2 | Normal | TDLA30-300 Low | No additional DM-RS | 1.1 | 2.9 | 1.4 | + +**Table 11.3.2.5.2-3: Minimum requirements for PUCCH format 3 and 120 kHz SCS in FR2-2** + +| Test Number | Number of TX antennas | Number of Demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | Additional DM-RS configuration | Channel bandwidth / SNR (dB) | +|-------------|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|------------------------------| +| | | | | | | 100 | +| 1 | 1 | 2 | Normal | TDLA30-650 Low | No additional DM-RS | 0.6 | +| | | | | | Additional DM-RS | 0.7 | +| 2 | 1 | 2 | Normal | TDLA30-650 Low | No additional DM-RS | 1.8 | + +**Table 11.3.2.5.2-4: Minimum requirements for PUCCH format 3 and 480 kHz SCS in FR2-2** + +| Test Number | Number of TX antennas | Number of Demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | Additional DM-RS configuration | Channel bandwidth / SNR (dB) | +|-------------|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|------------------------------| +| | | | | | | 400 | +| 1 | 1 | 2 | Normal | TDLA10-650 Low | No additional DM-RS | 0.5 | +| | | | | | Additional DM-RS | 0.5 | +| 2 | 1 | 2 | Normal | TDLA10-650 Low | No additional DM-RS | 2 | + +## 11.3.2.6 Performance requirements for PUCCH format 4 + +### 11.3.2.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 part 2. + +The transient period as specified in TS 38.101-2 [18] clause 6.3.3.1 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. + +**Table 11.3.2.6.1-1: Test parameters** + +| Parameter | Value | +|---------------------------------------------------|--------------------------------------------------------| +| Modulation order | QPSK | +| First PRB prior to frequency hopping/starting PRB | 0 | +| Number of PRBs | For tests with FR2-1 : 1.
For tests 2 with FR2-2:16 | +| 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 | + +### 11.3.2.6.2 Minimum requirements + +The UCI block error probability shall not exceed 1% at the SNR given in Table 11.3.2.6.2-1 to 11.3.2.6.2-4. + +**Table 11.3.2.6.2-1: Required SNR for PUCCH format 4 with 60 kHz SCS in FR2-1** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | Additional DM-RS configuration | Channel Bandwidth / SNR (dB) | | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|------------------------------|---------| +| | | | | | 50 MHz | 100 MHz | +| 1 | 2 | Normal | TDLA30-300 Low | No additional DM-RS | 3.0 | 2.7 | +| | | | | Additional DM-RS | 3.1 | 3.5 | + +**Table 11.3.2.6.2-2: Required SNR for PUCCH format 4 with 120 kHz SCS in FR2-1** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | Additional DM-RS configuration | Channel Bandwidth / SNR (dB) | | | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|------------------------------|---------|---------| +| | | | | | 50 MHz | 100 MHz | 200 MHz | +| 1 | 2 | Normal | TDLA30-300 Low | No additional DM-RS | 2.8 | 2.8 | 3.5 | +| | | | | Additional DM-RS | 3.6 | 3.8 | 3.2 | + +**Table 11.3.2.6.2-3: Minimum requirements for PUCCH format 4 and 120 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Number of PRBs | Additional DM-RS configuration | Channel bandwidth / SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|----------------|--------------------------------|------------------------------| +| | | | | | | 100 MHz | +| 1 | 2 | Normal | TDLA30-650 Low | 1 | No additional DM-RS | 3.0 | +| | | | | | Additional DM-RS | 3.0 | +| 1 | 2 | Normal | TDLA30-650 Low | 16 | No additional DM-RS | -9.0 | +| | | | | | Additional DM-RS | -8.9 | + +**Table 11.3.2.6.2-4: Minimum requirements for PUCCH format 4 and 480 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Number of PRBs | Additional DM-RS configuration | Channel bandwidth / SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|----------------|--------------------------------|------------------------------| +| | | | | | | 400 MHz | +| 1 | 2 | Normal | TDLA10-650 Low | 1 | No additional DM-RS | 3.6 | +| | | | | | Additional DM-RS | [-3.4] | +| 1 | 2 | Normal | TDLA10-650 Low | 16 | No additional DM-RS | -9.1 | +| | | | | | Additional DM-RS | [-9.0] | + +### 11.3.2.7 Performance requirements for PUCCH format 1 with DMRS bundling + +#### 11.3.2.7.1 NACK to ACK requirements + +##### 11.3.2.7.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(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. + +The NACK to ACK detection probability performance requirement only apply to PUCCH format 1 with 2 UCI bits. The UCI information only contain ACK/NACK information. + +The 2bits UCI information is further defined with bitmap as [0 1]. + +**Table 11.3.2.7.1.1-1: Test Parameters** + +| Parameter | Test | +|------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Example TDD UL-DL pattern (Note1) | 60 kHz SCS:
DDSUU, S=10D:2G:2U
or DSUUU
120 kHz SCS:
DDSUU,
S=10D:2G:2U, DSUUU
or DSUUU | +| 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 | +| 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 | +| PUCCH-TimeDomainWindowLength | 2 | +| 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. | + +#### 11.3.2.7.1.2 Minimum requirements + +The NACK to ACK probability shall not exceed 0.1% at the SNR given in table 11.3.2.7.1.2-1 and table 11.3.2.7.1.2-2 + +**Table 11.3.2.7.1.2-1: Minimum requirements for PUCCH format 1 with DMRS bundling, 60 kHz SCS, 50MHz channel bandwidth** + +| Number of Tx antennas | Number of demodulation branches | Cyclic-Prefix | Propagation conditions and correlation matrix (Annex G) | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|----------| +| 1 | 2 | Normal | TDLA30-75 Low | -3.3 | + +**Table 11.3.2.7.1.2-2: Minimum requirements for PUCCH format 1 with DMRS bundling, 120 kHz SCS, 50MHz channel bandwidth** + +| Number of Tx antennas | Number of demodulation branches | Cyclic-Prefix | Propagation conditions and correlation matrix (Annex G) | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|----------| +| 1 | 2 | Normal | TDLA30-75 Low | -3.2 | + +#### 11.3.2.7.2 ACK missed detection requirements + +##### 11.3.2.7.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 11.3.2.7.2.1-1 are configured. + +The ACK missed detection probability performance requirement only apply to PUCCH format 1 with 2 UCI bits. The UCI information only contain ACK/NACK information. + +The 2bits UCI information is further defined with bitmap as [0 1]. + +#### 11.3.2.7.2.2 Minimum requirements + +The ACK missed detection probability shall not exceed 1% at the SNR given in table 11.3.2.7.2.2-1 to table 11.3.2.7.2.2-2 + +**Table 11.3.2.7.2.2-1: Minimum requirements for PUCCH format 1 with JCE, 60 kHz SCS, 50MHz channel bandwidth** + +| Test Number | Number of Tx antennas | Number of demodulation branches | Cyclic-Prefix | Propagation conditions and correlation matrix (Annex G) | SNR (dB) | +|-------------|-----------------------|---------------------------------|---------------|---------------------------------------------------------|----------| +| 1 | 1 | 2 | Normal | TDLA30-75 Low | -4.8 | + +**Table 11.3.2.7.2.2-1: Minimum requirements for PUCCH format 1 with JCE, 120 kHz SCS, 100MHz channel bandwidth** + +| Test Number | Number of Tx antennas | Number of demodulation branches | Cyclic-Prefix | Propagation conditions and correlation matrix (Annex G) | SNR (dB) | +|-------------|-----------------------|---------------------------------|---------------|---------------------------------------------------------|----------| +| 1 | 1 | 2 | Normal | TDLA30-75 Low | -4.9 | + +#### 11.3.2.8 Performance requirements for PUCCH format 3 with DMRS bundling + +##### 11.3.2.8.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 part 2. + +**Table 11.3.2.8.1-1: Test Parameters** + +| Parameter | Test | +|--------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Example TDD UL-DL pattern (Note 1) | 60 kHz SCS:
DDSUU, S=10D:2G:2U or DSUUU
120 kHz SCS:
DDSUU, S=10D:2G:2U or DSUUU | +| Modulation order | QPSK | +| First PRB prior to frequency hopping | 0 | +| Intra-slot frequency hopping | disabled | +| 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 | +| Number of slots for PUCCH repetition | 2 | +| PUCCH-TimeDomainWindowLength | 2 | +| 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. | + +### 11.3.2.8.2 Minimum requirements + +The UCI block error probability shall not exceed 1% at the SNR given in Table 11.3.2.8.2-1 and Table 11.3.2.8.2-2. + +**Table 11.3.2.8.2-1: Minimum requirements for PUCCH format 3 with JCE, 60 kHz SCS, 50MHz channel bandwidth** + +| Test Number | Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | Additional DM-RS configuration | Channel bandwidth / SNR (dB) | +|-------------|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|------------------------------| +| | | | | | | 50 MHz | +| 1 | 1 | 2 | Normal | TDLA30-75 Low | No additional DM-RS | 0.1 | +| | | | | | Additional DM-RS | -0.2 | + +**Table 11.3.2.8.2-2: Minimum requirements for PUCCH format 3 with JCE, 120 kHz SCS, 50MHz channel bandwidth** + +| Test Number | Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | Additional DM-RS configuration | Channel bandwidth / SNR (dB) | +|-------------|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|------------------------------| +| | | | | | | 50 MHz | +| 1 | 1 | 2 | Normal | TDLA30-75 Low | No additional DM-RS | 0.7 | +| | | | | | Additional DM-RS | -0.1 | + +## 11.4 Performance requirements for PRACH + +### 11.4.1 Requirements for BS type 1-O + +#### 11.4.1.1 PRACH False alarm probability + +Apply the requirements defined in clause 8.4.1 for 2Rx. + +#### 11.4.1.2 PRACH detection requirements + +Apply the requirements defined in clause 8.4.2 for 2Rx. + +### 11.4.2 Requirements for BS type 2-O + +#### 11.4.2.1 PRACH False alarm probability + +##### 11.4.2.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. + +##### 11.4.2.1.2 Minimum requirement + +The false alarm probability shall be less than or equal to 0.1%. + +## 11.4.2.2 PRACH detection requirements + +### 11.4.2.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 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 given in Table 11.4.2.2-1. + +The performance requirements for high speed train (table 11.4.2.2.3-1) are optional and only applicable for FR2-1 below 30GHz. + +**Table 11.4.2.2-1: Time error tolerance for AWGN, TDLA30-300, and TDLA10-650** + +| PRACH preamble | PRACH SCS (kHz) | Time error tolerance | | | +|------------------------|-----------------|----------------------|------------|------------| +| | | AWGN | TDLA30-300 | TDLA10-650 | +| A1, A2, A3, B4, C0, C2 | 60 | 0.13 us | 0.28 us | N/A | +| | 120 | 0.07 us | 0.22 us | N/A | +| | 480 | 18 ns | N/A | 68 ns | + +The test preambles for normal mode are listed in table A.6-2 and the test parameter *msg1-FrequencyStart* is set to 0. The test preambles for high speed train short formats are listed in table A.6-7 and the test parameter *msg1-FrequencyStart* for high speed train is set to 0. + +### 11.4.2.2.2 Minimum requirements for Normal mode + +The probability of detection shall be equal to or exceed 99% for the SNR levels listed in Tables 11.4.2.2.2-1 to 11.4.2.2.2-4. + +**Table 11.4.2.2.2-1: PRACH missed detection requirements for Normal Mode, 60 kHz SCS in FR2-1** + +| Number of TX antennas | Number of demodulation branches | 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.9 | -11.9 | -13.5 | -15.8 | -6.0 | -11.8 | +| | | TDLA30-300 Low | 4000 Hz | -1.6 | -3.8 | -4.8 | -6.9 | 1.1 | -3.9 | + +**Table 11.4.2.2.2-2: PRACH missed detection requirements for Normal Mode, 120 kHz SCS in FR2-1** + +| Number of TX antennas | Number of demodulation branches | 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.7 | -11.5 | -13.3 | -15.8 | -5.8 | -11.4 | +| | | TDLA30-300 Low | 4000 Hz | -1.7 | -4.4 | -5.8 | -7.5 | 1.2 | -4.2 | + +**Table 11.4.2.2.2-3: PRACH missed detection test requirements for Normal Mode, 120 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex G) | Frequency offset | SNR (dB) | | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------|-----------------|-----------------|-----------------| +| | | | | Burst format A2 | Burst format B4 | Burst format C2 | +| 1 | 2 | AWGN | 0 | -11.8 | -16 | -11.8 | +| | | TDLA30-650 Low | 7100 Hz | -4.3 | -7.3 | -4.2 | + +**Table 11.4.2.2.22-4: PRACH missed detection test requirements for Normal Mode, 480 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex G) | Frequency offset | SNR (dB) | | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------|-----------------|-----------------|-----------------| +| | | | | Burst format A2 | Burst format B4 | Burst format C2 | +| 1 | 2 | AWGN | 0 | -11.7 | -15.9 | -11.8 | +| | | TDLA10-650 Low | 7100 Hz | -4.5 | -9.3 | -4.5 | + +#### 11.4.2.2.3 Minimum requirements for high speed train + +The probability of detection shall be equal to or exceed 99% for the SNR levels listed in Table 11.4.2.2.3-1. + +**Table 11.4.2.2.3-1: PRACH missed detection requirements for high speed train, 120 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Propagation conditions (Annex G) | Frequency offset | SNR (dB) | +|-----------------------|-----------------------|----------------------------------|------------------|-----------------| +| | | | | Burst format C2 | +| 1 | 2 | AWGN | 19444 Hz | -10.4 | + +#### 11.4.2.2.4 Minimum requirements for PRACH with $L_{RA}=1151$ and $L_{RA}=571$ + +The probability of detection shall be equal to or exceed 99% for the SNR levels listed in Tables 11.4.2.2.4-1 to 11.4.2.2.4-3. + +**Table 11.4.2.2.4-1: Missed detection requirements for PRACH with $L_{RA}=571$ , 120 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | 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.9 | -22.1 | -17.9 | +| | | TDLA30-650 Low | 7100 Hz | -10.9 | -13.8 | -10.7 | + +**Table 11.4.2.2.4-2: Missed detection requirements for PRACH with $L_{RA}=1151$ , 120 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | 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.9 | -25.0 | -20.8 | +| | | TDLA10-650 | 7100 Hz | -14.0 | -16.9 | -14.0 | + +**Table 11.4.2.2.4-3: Missed detection requirements for PRACH with $L_{RA}=571$ , 480 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | 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.9 | -22.0 | -17.9 | +| | | TDLA10-650 | 7100 Hz | -11.1 | -15.0 | -11.1 | + +--- + +## 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, in-channel selectivity, OTA sensitivity, OTA reference sensitivity level, OTA ACS, OTA in-band blocking, OTA out-of-band blocking, OTA receiver intermodulation and OTA in-channel selectivity. The parameters for the band n46, n96 and n102 reference measurement channels are specified in table A.1-1a and A.1-1b for reference sensitivity level, ACS, in-band blocking, out-of-band blocking, receiver intermodulation, in-channel selectivity. + +The parameters for the reference measurement channels are specified in table A.1-2 for FR2 OTA reference sensitivity level, OTA ACS, OTA in-band blocking, OTA out-of-band blocking, OTA receiver intermodulation and OTA in-channel selectivity. + +Reference measurement channels G-FR2-A1-1 to G-FR2-A1-5 are used for FR2-1 requirements. Reference measurement channels G-FR2-A1-2, G-FR2-A1-3, G-FR2-A1-6 to G-FR2-A1-9 are used for FR2-2 requirements. + +**Table A.1-1: FRC parameters for FR1 reference sensitivity level, ACS, in-band blocking, out-of-band blocking, receiver intermodulation, in-channel selectivity, OTA sensitivity, OTA reference sensitivity level, OTA ACS, OTA in-band blocking, OTA out-of-band blocking, OTA receiver intermodulation and OTA 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 | G-FR1-A1-20 | G-FR1-A1-21 | +|-------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|-------------|-------------|-------------|-------------| +| Subcarrier spacing (kHz) | 15 | 30 | 60 | 15 | 30 | 60 | 15 | 30 | 60 | 15 | 15 | 15 | 15 | +| Allocated resource blocks | 25 | 11 | 11 | 106 | 51 | 24 | 15 | 6 | 6 | 24 | 105 | 9 | 12 | +| CP-OFDM Symbols per slot (Note 1) | 12 | 12 | 12 | 12 | 12 | 12 | 12 | 12 | 12 | 12 | 12 | 12 | 12 | +| Modulation | QPSK | QPSK | 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 | 1/3 | 1/3 | +| Payload size (bits) | 2152 | 984 | 984 | 9224 | 4352 | 2088 | 1320 | 528 | 528 | [2088] | [8968] | 808 | 1032 | +| Transport block CRC (bits) | 16 | 16 | 16 | 24 | 24 | 16 | 16 | 16 | 16 | 16 | 24 | 16 | 16 | +| Code block CRC size (bits) | - | - | - | 24 | - | - | - | - | - | - | 24 | - | - | +| Number of code blocks - C | 1 | 1 | 1 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | 1 | +| Code block size including CRC (bits) (Note 3) | 2168 | 1000 | 1000 | 4648 | 4376 | 2104 | 1336 | 544 | 544 | [2104] | [4520] | 824 | 1048 | +| Total number of bits per slot | 7200 | 3168 | 3168 | 30528 | 14688 | 6912 | 4320 | 1728 | 1728 | [6912] | [30240] | 2592 | 3456 | +| Total symbols per slot | 3600 | 1584 | 1584 | 15264 | 7344 | 3456 | 2160 | 864 | 864 | [3456] | [15120] | 1296 | 1728 | +| NOTE 1: UL-DMRS-config-type = 1 with UL-DMRS-max-len = 1, UL-DMRS-add-pos = 1 with = 2, = 11 as per table 6.4.1.1.3-3 of TS 38.211 [9]. | | | | | | | | | | | | | | +| 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 [15]. | | | | | | | | | | | | | | + +**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 *l* = 2, *l* = 11 as per table 6.4.1.1.3-3 of TS 38.211 [9]. + +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 [15]. + +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}. + +**Table A.1-2: FRC parameters for FR2 OTA reference sensitivity level, OTA ACS, OTA in-band blocking, OTA out-of-band blocking, OTA receiver intermodulation and OTA in-channel selectivity** + +| Reference channel | G-FR2-A1-1 | G-FR2-A1-2 | G-FR2-A1-3 | G-FR2-A1-4 | G-FR2-A1-5 | G-FR2-A1-6 | G-FR2-A1-7 | G-FR2-A1-8 | G-FR2-A1-9 | +|-----------------------------------------------|------------|------------|------------|------------|------------|------------|------------|------------|------------| +| Subcarrier spacing (kHz) | 60 | 120 | 120 | 60 | 120 | 480 | 960 | 480 | 960 | +| Allocated resource blocks | 66 | 32 | 66 | 33 | 16 | 66 | 33 | 33 | 17 | +| 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) | 5632 | 2792 | 5632 | 2856 | 1416 | 5632 | 2856 | 2856 | 1480 | +| Transport block CRC (bits) | 24 | 16 | 24 | 16 | 16 | 24 | 16 | 16 | 16 | +| Code block CRC size (bits) | - | - | - | - | - | - | - | - | - | +| Number of code blocks - C | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| Code block size including CRC (bits) (Note 3) | 5656 | 2808 | 5656 | 2872 | 1432 | 5656 | 2872 | 2872 | 1496 | +| Total number of bits per slot | 19008 | 9216 | 19008 | 9504 | 4608 | 19008 | 9504 | 9504 | 4896 | +| Total symbols per slot | 9504 | 4608 | 9504 | 4752 | 2304 | 9504 | 4752 | 4752 | 2448 | + +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 [9]. + +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 sub-clause 5.2.2 of TS 38.212 [15]. + +## 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. 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 and OTA 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 | G-FR1-A2-15 | +|-----------------------------------------------|------------|------------|------------|------------|------------|------------|-------------| +| Subcarrier spacing (kHz) | 15 | 30 | 60 | 15 | 30 | 60 | 15 | +| Allocated resource blocks | 25 | 11 | 11 | 106 | 51 | 24 | 15 | +| 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) | 2/3 | 2/3 | 2/3 | 2/3 | 2/3 | 2/3 | 2/3 | +| Payload size (bits) | 9224 | 4032 | 4032 | 38936 | 18960 | 8968 | 5504 | +| Transport block CRC (bits) | 24 | 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 | 1 | +| Code block size including CRC (bits) (Note 3) | 4648 | 4056 | 4056 | 7816 | 6352 | 4520 | 5528 | +| Total number of bits per slot | 14400 | 6336 | 6336 | 61056 | 29376 | 13824 | 8640 | +| Total symbols per slot | 3600 | 1584 | 1584 | 15264 | 7344 | 3456 | 2160 | + +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 [9]. + +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 [15]. + +**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 $l_0 = 2$ , $l = 11$ as per table 6.4.1.1.3-3 of TS 38.211 [9]. + +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 [15]. + +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. +- FRC parameters are specified in table A.3-16 for FR1 PUSCH with transform precoding disabled, *Additional DM-RS position = pos1* and 4 transmission layers. + +The parameters for the reference measurement channels are specified in table A.3-14 for FR1 PUSCH performance requirements for TB processing over multi-slot PUSCH: + +- FRC parameters are specified in table A.3-14 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.3-7 to table A.3-12 for FR2 PUSCH performance requirements: + +- FRC parameters are specified in table A.3-7 for FR2 PUSCH with transform precoding disabled, *Additional DM-RS position = pos0* and 1 transmission layer. +- FRC parameters are specified in table A.3-8 for FR2 PUSCH with transform precoding disabled, *Additional DM-RS position = pos0* and 2 transmission layers. +- FRC parameters are specified in table A.3-9 for FR2 PUSCH with transform precoding enabled, *Additional DM-RS position = pos0* and 1 transmission layer. +- FRC parameters are specified in table A.3-10 for FR2 PUSCH with transform precoding disabled, *Additional DM-RS position = pos1* and 1 transmission layer. +- FRC parameters are specified in table A.3-11 for FR2 PUSCH with transform precoding disabled, *Additional DM-RS position = pos1* and 2 transmission layers. +- FRC parameters are specified in table A.3-12 for FR2 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-13 for FR2 PUSCH performance requirements for 2-step RA type: + +- FRC parameters are specified in table A.3-13 for FR2 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.3-15 for FR2 PUSCH performance requirements for TBoMS: + +- FRC parameters are specified in table A.3-15 for FR2 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*, *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 [9]. + +NOTE 2: Code block size including CRC (bits) equals to *K'* in clause 5.2.2 of TS 38.212 [15]. + +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 *l0= 2* or *3* for PUSCH mapping type A, 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 [15]. + +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 [9]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [15]. + +**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 [9]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [15]. + +**Table A.3-7: FRC parameters for FR2 PUSCH performance requirements, transform precoding disabled, *Additional DM-RS position = pos0* and 1 transmission layer (QPSK, R=193/1024)** + +| Reference channel | G-FR2-A3-1 | G-FR2-A3-2 | G-FR2-A3-3 | G-FR2-A3-4 | G-FR2-A3-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 (Note 2) | 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 *l0 = 0* as per Table 6.4.1.1.3-3 of TS 38.211 [9]. + +NOTE 2: Code block size including CRC (bits) equals to *K'* in sub-clause 5.2.2 of TS 38.212 [15]. + +**Table A.3-8: FRC parameters for FR2 PUSCH performance requirements, transform precoding disabled, *Additional DM-RS position = pos0* and 2 transmission layers (QPSK, R=193/1024)** + +| Reference channel | G-FR2-A3-6 | G-FR2-A3-7 | G-FR2-A3-8 | G-FR2-A3-9 | G-FR2-A3-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 (Note 2) | 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 *l0 = 0* as per Table 6.4.1.1.3-3 of TS 38.211 [9]. + +NOTE 2: Code block size including CRC (bits) equals to *K'* in sub-clause 5.2.2 of TS 38.212 [15]. + +**Table A.3-9: FRC parameters for FR2 PUSCH performance requirements, transform precoding enabled, *Additional DM-RS position = pos0* and 1 transmission layer (QPSK, R=193/1024)** + +| Reference channel | G-FR2-A3-11 | G-FR2-A3-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 (Note 2) | 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 *l0 = 0* as per Table 6.4.1.1.3-3 of TS 38.211 [9]. + +NOTE 2: Code block size including CRC (bits) equals to *K'* in sub-clause 5.2.2 of TS 38.212 [15]. + +**Table A.3-10: FRC parameters for FR2 PUSCH performance requirements, transform precoding disabled, *Additional DM-RS position = pos1* and 1 transmission layer (QPSK, R=193/1024)** + +| Reference channel | G-FR2-A3-13 | G-FR2-A3-14 | G-FR2-A3-15 | G-FR2-A3-16 | G-FR2-A3-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 (Note 2) | 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 *l0 = 0* and *l = 8* as per Table 6.4.1.1.3-3 of TS 38.211 [9]. + +NOTE 2: Code block size including CRC (bits) equals to *K'* in sub-clause 5.2.2 of TS 38.212 [15]. + +**Table A.3-11: FRC parameters for FR2 PUSCH performance requirements, transform precoding disabled, *Additional DM-RS position = pos1* and 2 transmission layers (QPSK, R=193/1024)** + +| Reference channel | G-FR2-A3-18 | G-FR2-A3-19 | G-FR2-A3-20 | G-FR2-A3-21 | G-FR2-A3-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 (Note 2) | 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 *l0 = 0* and *l = 8* as per Table 6.4.1.1.3-3 of TS 38.211 [9]. + +NOTE 2: Code block size including CRC (bits) equals to *K'* in sub-clause 5.2.2 of TS 38.212 [15]. + +**Table A.3-12: FRC parameters for FR2 PUSCH performance requirements, transform precoding enabled, Additional DM-RS position = pos1 and 1 transmission layer (QPSK, R=193/1024)** + +| Reference channel | G-FR2-A3-23 | G-FR2-A3-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 (Note 2) | 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 [9]. | | | +| NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [15]. | | | + +**Table A.3-13: FRC parameters for FR2 PUSCH performance requirements, transform precoding disabled, Additional DM-RS position = pos1 and 1 transmission layer (QPSK, R=193/1024)** + +| Reference channel | G-FR2-A3-25 | G-FR2-A3-26 | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------| +| Subcarrier spacing [kHz] | 60 | 120 | +| Allocated resource blocks | 2 | 2 | +| CP-OFDM Symbols per slot (Note 1) | 8 | 8 | +| Modulation | QPSK | QPSK | +| Code rate (Note 2) | 193/1024 | 193/1024 | +| Payload size (bits) | 72 | 72 | +| Transport block CRC (bits) | 16 | 16 | +| Code block CRC size (bits) | 0 | 0 | +| Number of code blocks - C | 1 | 1 | +| Code block size including CRC (bits) (Note 2) | 88 | 88 | +| Total number of bits per slot | 384 | 384 | +| Total number of symbols per slot | 192 | 192 | +| 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 = 2$ as per Table 6.4.1.1.3-3 of TS 38.211 [9]. | | | +| NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [15]. | | | + +**Table A.3-14: 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 with $l_0 = 2$ as per Table 6.4.1.1.3-3 of TS 38.211 [9]. | | | | | +| NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [15]. | | | | | + +**Table A.3-16: FRC parameters for FR1 PUSCH performance requirements, transform precoding disabled, additional DM-RS position = pos1 and 4 transmission layers (QPSK, R=193/1024)** + +| Reference channel | G-FR1-A3-39 | G-FR1-A3-40 | G-FR1-A3-41 | G-FR1-A3-42 | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------|-------------|-------------| +| Subcarrier spacing [kHz] | 15 | 15 | 30 | 30 | +| Allocated resource blocks | 25 | 270 | 24 | 273 | +| 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) | 5384 | 58472 | 5256 | 59496 | +| Transport block CRC (bits) | 24 | 24 | 24 | 24 | +| Code block CRC size (bits) | 24 | 24 | 24 | 24 | +| Number of code blocks - C | 2 | 16 | 2 | 16 | +| Code block size including CRC (bits) (Note 2) | 2728 | 3680 | 2664 | 3744 | +| Total number of bits per slot | 28800 | 311040 | 27648 | 314496 | +| Total symbols per slot | 14400 | 155520 | 13824 | 157248 | +| 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 [9]. | | | | | +| NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [15]. | | | | | + +**Table A.3-15: FRC parameters for FR2 PUSCH performance requirements, transform precoding disabled, Additional DM-RS position = pos1 and 1 transmission layer (QPSK, R=193/1024)** + +| Reference channel | G-FR2-A3-27 | G-FR2-A3-28 | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------| +| Number of TBoMS slots | 2 | 2 | +| Subcarrier spacing [kHz] | 60 | 120 | +| Allocated resource blocks per slot | 5 | 5 | +| Data bearing CP-OFDM Symbols per slot (Note 1) | 8 | 8 | +| Modulation | QPSK | QPSK | +| Code rate (Note 2) | 193/1024 | 193/1024 | +| Payload size (bits) | 368 | 368 | +| 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) | 384 | 384 | +| Total number of bits over all TBoMS slots | 1920 | 1920 | +| Total resource elements over all TBoMS slots | 960 | 960 | +| 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 , l0 = 0 and l = 8 for PUSCH mapping type B as per table 6.4.1.1.3-3 of TS 38.211 [9]. | | | +| NOTE 2: Code block size including CRC (bits) equals to K' in sub-clause 5.2.2 of TS 38.212 [15]. | | | + +## 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. + +The parameters for the reference measurement channels are specified in table A.3A-2 to A.3A-3 for FR2 PUSCH performance requirements: + +- FRC parameters are specified in table A.3A-2 for FR2 PUSCH with transform precoding disabled, additional DM-RS position = pos0 and 1 transmission layer. +- FRC parameters are specified in table A.3A-3 for FR2 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 | +| Data bearing 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 resource elements 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 [9]. | | | | | +| NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [15]. | | | | | + +**Table A.3A-2: FRC parameters for FR2 PUSCH performance requirements, transform precoding disabled, additional DM-RS position = pos0 and 1 transmission layer (QPSK, R=99/1024)** + +| Reference channel | G-FR2-A3A-1 | G-FR2-A3A-2 | G-FR2-A3A-3 | G-FR2-A3A-4 | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------|-------------|-------------| +| Subcarrier spacing [kHz] | 60 | 60 | 120 | 120 | +| Allocated resource blocks | 66 | 132 | 32 | 66 | +| Data bearing CP-OFDM Symbols per slot (Note 1) | 3 | 3 | 3 | 3 | +| Modulation | QPSK | QPSK | QPSK | QPSK | +| Code rate (Note 2) | 99/1024 | 99/1024 | 99/1024 | 99/1024 | +| Payload size (bits) | 456 | 928 | 224 | 456 | +| 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) | 472 | 944 | 240 | 472 | +| Total number of bits per slot | 4752 | 9504 | 2304 | 4752 | +| Total symbols per slot | 2376 | 4752 | 1152 | 2376 | +| 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 [9]. | | | | | +| NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [15]. | | | | | + +**Table A.3A-3: FRC parameters for FR2 PUSCH performance requirements, transform precoding disabled, additional DM-RS position = pos1 and 1 transmission layer (QPSK, R=99/1024)** + +| Reference channel | G-FR2-A3A-5 | G-FR2-A3A-6 | G-FR2-A3A-7 | G-FR2-A3A-8 | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------|-------------|-------------| +| Subcarrier spacing [kHz] | 60 | 60 | 120 | 120 | +| Allocated resource blocks | 66 | 132 | 32 | 66 | +| Data bearing CP-OFDM Symbols per slot (Note 1) | 8 | 8 | 8 | 8 | +| Modulation | QPSK | QPSK | QPSK | QPSK | +| Code rate (Note 2) | 99/1024 | 99/1024 | 99/1024 | 99/1024 | +| Payload size (bits) | 1224 | 2472 | 608 | 1224 | +| 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) | 1240 | 2488 | 624 | 1240 | +| Total number of bits per slot | 12672 | 25344 | 6144 | 12672 | +| Total symbols per slot | 6336 | 12672 | 3072 | 6336 | +| 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= 0 and l = 8 as per table 6.4.1.1.3-3 of TS 38.211 [9]. | | | | | +| NOTE 2: Code block size including CRC (bits) equals to K' in clause 5.2.2 of TS 38.212 [15]. | | | | | + +## A.3B Fixed Reference Channels for performance requirements (QPSK, R=308/1024) + +The parameters for the reference measurement channel are 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. + +The parameters for the reference measurement channel are specified in table A.3B-4 for FR2-1 PUSCH performance requirements with DM-RS bundling: + +- FRC parameters are specified in table A.3B-4 for FR2-1 PUSCH with transform precoding disabled, additional DM-RS position = pos1 and 1 transmission layer. + +The parameters for the reference measurement channel are specified in table A.3B-5 to table A.3B-7 for FR2-2 PUSCH performance requirements: + +- FRC parameters are specified in table A.3B-5 for FR2-2 PUSCH with transform precoding disabled, *Additional DM-RS position = pos1* and 1 transmission layer. +- FRC parameters are specified in table A.3B-6 for FR2-2 PUSCH with transform precoding enabled, *Additional DM-RS position = pos1* and 1 transmission layer. +- FRC parameters are specified in table A.3B-7 for FR2-2 PUSCH with transform precoding disabled, *Additional DM-RS position = pos1* and 2 transmission layers. + +**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 | +| Data bearing 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 resource elements 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$ for PUSCH mapping type B as per table 6.4.1.1.3-3 of TS 38.211 [9]. | | | | | +| NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [15]. | | | | | + +**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 [9]. | | | +| 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 $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 [9]. | | | +| 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-4: FRC parameters for FR2-1 PUSCH performance requirements, transform precoding disabled, *Additional DM-RS position = pos1* and 1 transmission layer (QPSK, R=308/1024)** + +| Reference channel | G-FR2-A3B-1 | G-FR2-A3B-2 | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------| +| Subcarrier spacing [kHz] | 60 | 120 | +| Allocated resource blocks | 66 | 32 | +| CP-OFDM Symbols per slot (Note 1) | 12 | 12 | +| Modulation | QPSK | QPSK | +| Code rate (Note 2) | 308/1024 | 308/1024 | +| Payload size (bits) | 5632 | 2792 | +| Transport block CRC (bits) | 24 | 16 | +| Code block CRC size (bits) | - | - | +| Number of code blocks - C | 1 | 1 | +| Code block size including CRC (bits) (Note 2) | 5656 | 2808 | +| Total number of bits per slot | 19008 | 9216 | +| Total resource elements per slot | 9504 | 4608 | +| 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 = 10$ as per Table 6.4.1.1.3-3 of TS 38.211 [9]. | | | +| 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-5: FRC parameters for FR2-2 PUSCH performance requirements, transform precoding disabled, *Additional DM-RS position = pos1* and 1 transmission layer (QPSK, R=308/1024)** + +| Reference channel | G-FR2-A3B-3 | G-FR2-A3B-4 | G-FR2-A3B-5 | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------|-------------| +| Subcarrier spacing [kHz] | 120 | 120 | 480 | +| Allocated resource blocks | 66 | 264 | 66 | +| CP-OFDM Symbols per slot (Note 1) | 8 | 8 | 8 | +| Modulation | QPSK | QPSK | QPSK | +| Code rate (Note 2) | 308/1024 | 308/1024 | 308/1024 | +| Payload size (bits) | 3824 | 15112 | 3824 | +| Transport block CRC (bits) | 16 | 24 | 16 | +| Code block CRC size (bits) | - | 24 | - | +| Number of code blocks - C | 1 | 2 | 1 | +| Code block size including CRC (bits) (Note 2) | 3840 | 7592 | 3840 | +| Total number of bits per slot without PT-RS | 12672 | 50688 | 12672 | +| Total symbols per slot without PT-RS | 6336 | 25344 | 6336 | +| 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 l0 = 0 and l = 8 as per Table 6.4.1.1.3-3 of TS 38.211 [9]. | | | | +| NOTE 2: Code block size including CRC (bits) equals to K' in sub-clause 5.2.2 of TS 38.212 [15]. | | | | +| NOTE 3: The calculation of the “Total number of bits per slot” and “Total symbols per slot” fields include the REs taken up by CSI part 1 and CSI part 2, if present. | | | | + +**Table A.3B-6: FRC parameters for FR2-2 PUSCH performance requirements, transform precoding enabled, *Additional DM-RS position = pos1* and 1 transmission layer (QPSK, R=308/1024)** + +| Reference channel | G-FR2-A3B-6 | G-FR2-A3B-7 | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------| +| Subcarrier spacing [kHz] | 120 | 480 | +| Allocated resource blocks | 64 | 64 | +| DFT-s-OFDM Symbols per slot (Note 1) | 8 | 8 | +| Modulation | QPSK | QPSK | +| Code rate (Note 2) | 308/1024 | 308/1024 | +| Payload size (bits) | 3624 | 3624 | +| 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) | 3640 | 3640 | +| Total number of bits per slot without PT-RS | 12288 | 12288 | +| Total symbols per slot without PT-RS | 6144 | 6144 | +| 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 l0 = 0 and l = 8 as per Table 6.4.1.1.3-3 of TS 38.211 [9]. | | | +| NOTE 2: Code block size including CRC (bits) equals to K' in sub-clause 5.2.2 of TS 38.212 [15]. | | | +| NOTE 3: The calculation of the “Total number of bits per slot” and “Total symbols per slot” fields include the REs taken up by CSI part 1 and CSI part 2, if present. | | | + +**Table A.3B-7: FRC parameters for FR2-2 PUSCH performance requirements, transform precoding disabled, *Additional DM-RS position = pos1* and 2 transmission layers (QPSK, R=308/1024)** + +| Reference channel | G-FR2-A3B-8 | G-FR2-A3B-9 | G-FR2-A3B-10 | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------|--------------| +| Subcarrier spacing [kHz] | 120 | 120 | 480 | +| Allocated resource blocks | 66 | 264 | 66 | +| CP-OFDM Symbols per slot (Note 1) | 8 | 8 | 8 | +| Modulation | QPSK | QPSK | QPSK | +| Code rate (Note 2) | 308/1024 | 308/1024 | 308/1024 | +| Payload size (bits) | 7552 | 30728 | 7552 | +| Transport block CRC (bits) | 24 | 24 | 24 | +| Code block CRC size (bits) | - | 24 | - | +| Number of code blocks - C | 1 | 4 | 1 | +| Code block size including CRC (bits) (Note 2) | 7576 | 7712 | 7576 | +| Total number of bits per slot without PT-RS | 25344 | 101376 | 25344 | +| Total symbols per slot without PT-RS | 12672 | 50688 | 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 l0 = 0 and l = 8 as per Table 6.4.1.1.3-3 of TS 38.211 [9]. | | | | +| NOTE 2: Code block size including CRC (bits) equals to K' in sub-clause 5.2.2 of TS 38.212 [15]. | | | | +| NOTE 3: The calculation of the “Total number of bits per slot” and “Total symbols per slot” fields include the REs taken up by CSI part 1 and CSI part 2, if present. | | | | + +## 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, table A.4-2B 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 = pos 2 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 layer +- 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. + +The parameters for the reference measurement channels are specified in table A.4-5 to table A.4-8 for FR2-1 PUSCH performance requirements: + +- FRC parameters are specified in table A.4-5 for FR2-1 PUSCH with transform precoding disabled, *Additional DM-RS position = pos0* and 1 transmission layer. +- FRC parameters are specified in table A.4-6 for FR2-1 PUSCH with transform precoding disabled, *Additional DM-RS position = pos0* and 2 transmission layers. +- FRC parameters are specified in table A.4-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.4-8 for FR2-1 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.4-7A for FR2-2 PUSCH performance requirements: + +- FRC parameters are specified in table A.4-7A for FR2-2 PUSCH with transform precoding disabled, *Additional DM-RS position = pos1* and 1 transmission layer. + +**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
(Note 3) | 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_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 [9]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [15]. + +NOTE 3: The calculation of the “Total number of bits per slot” and “Total symbols per slot” fields include the REs taken up by CSI part 1 and CSI part 2, if present. + +**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 [9]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [15]. + +**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 [9]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [15]. + +**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_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 [9]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [15]. + +**Table A.4-5: 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 | G-FR2-A4-1 | G-FR2-A4-2 | G-FR2-A4-3
(Note 3) | G-FR2-A4-4 | G-FR2-A4-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 (Note 2) | 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 without PT-RS | 28512 | 57024 | 13824 | 28512 | 57024 | +| Total number of bits per slot with PT-RS (Note 4) | 27324 | 54648 | 13248 | 27324 | 54648 | +| Total symbols per slot without PT-RS | 7128 | 14256 | 3456 | 7128 | 14256 | +| Total symbols per slot with PT-RS (Note 4) | 6831 | 13662 | 3312 | 6831 | 13662 | + +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 [9]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [15]. + +NOTE 3: The calculation of the “Total number of bits per slot” and “Total symbols per slot” fields include the REs taken up by CSI part 1 and CSI part 2, if present. + +NOTE 4: PT-RS configuration $K_{PT-RS} = 2$ , $L_{PT-RS} = 1$ . + +**Table A.4-6: 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 | G-FR2-A4-6 | G-FR2-A4-7 | G-FR2-A4-8 | G-FR2-A4-9 | G-FR2-A4-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 (Note 2) | 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 without PT-RS | 57024 | 114048 | 27648 | 57024 | 114048 | +| Total number of bits per slot with PT-RS (Note 3) | 54648 | 109296 | 26496 | 54648 | 109296 | +| Total symbols per slot without PT-RS | 14256 | 28512 | 6912 | 14256 | 28512 | +| Total symbols per slot with PT-RS (Note 3) | 13662 | 27324 | 6624 | 13662 | 27324 | + +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 [9]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [15]. + +NOTE 3: PT-RS configuration $K_{PT-RS} = 2$ , $L_{PT-RS} = 1$ . + +**Table A.4-7: 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 | G-FR2-A4-11 | G-FR2-A4-12 | G-FR2-A4-13
(Note 3) | G-FR2-A4-14 | G-FR2-A4-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 (Note 2) | 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 without PT-RS | 25344 | 50688 | 12288 | 25344 | 50688 | +| Total number of bits per slot with PT-RS (Note 4) | 24288 | 48576 | 11776 | 24288 | 48576 | +| Total symbols per slot without PT-RS | 6336 | 12672 | 3072 | 6336 | 12672 | +| Total symbols per slot with PT-RS (Note 4) | 6072 | 12144 | 2944 | 6072 | 12144 | + +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 [9]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [15]. + +NOTE 3: The calculation of the “Total number of bits per slot” and “Total symbols per slot” fields include the REs taken up by CSI part 1 and CSI part 2, if present. + +NOTE 4: PT-RS configuration $K_{PT-RS} = 2$ , $L_{PT-RS} = 1$ . + +**Table A.4-7A: FRC parameters for FR2-2 PUSCH performance requirements, transform precoding disabled, Additional DM-RS position = pos1 and 1 transmission layer (16QAM, R=658/1024)** + +| Reference channel | G-FR2-A4-21 | G-FR2-A4-22 | G-FR2-A4-23 | +|---------------------------------------------------|-------------|-------------|-------------| +| Subcarrier spacing [kHz] | 120 | 120 | 480 | +| Allocated resource blocks | 66 | 264 | 66 | +| CP-OFDM Symbols per slot (Note 1) | 8 | 8 | 8 | +| Modulation | 16QAM | 16QAM | 16QAM | +| Code rate (Note 2) | 658/1024 | 658/1024 | 658/1024 | +| Payload size (bits) | 16392 | 65576 | 16392 | +| Transport block CRC (bits) | 24 | 24 | 24 | +| Code block CRC size (bits) | 24 | 24 | 24 | +| Number of code blocks - C | 2 | 8 | 2 | +| Code block size including CRC (bits) (Note 2) | 8232 | 8224 | 8232 | +| Total number of bits per slot without PT-RS | 25344 | 101376 | 25344 | +| Total number of bits per slot with PT-RS (Note 4) | 24288 | 97152 | 24288 | +| Total symbols per slot without PT-RS | 6336 | 25344 | 6336 | +| Total symbols per slot with PT-RS (Note 4) | 6072 | 24288 | 6072 | + +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 [9]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [15]. + +NOTE 3: The calculation of the “Total number of bits per slot” and “Total symbols per slot” fields include the REs taken up by CSI part 1 and CSI part 2, if present. + +NOTE 4: PT-RS configuration $K_{PT-RS} = 2$ , $L_{PT-RS} = 1$ . + +**Table A.4-8: 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 | G-FR2-A4-16 | G-FR2-A4-17 | G-FR2-A4-18 | G-FR2-A4-19 | G-FR2-A4-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 (Note 2) | 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 without PT-RS | 50688 | 101376 | 24576 | 50688 | 101376 | +| Total number of bits per slot with PT-RS (Note 3) | 48576 | 97152 | 23552 | 48576 | 97152 | +| Total symbols per slot without PT-RS | 12672 | 25344 | 6144 | 12672 | 25344 | +| Total symbols per slot with PT-RS (Note 3) | 12144 | 24288 | 5888 | 12144 | 24288 | + +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 [9]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [15]. + +NOTE 3: PT-RS configuration $K_{PT-RS} = 2$ , $L_{PT-RS} = 1$ . + +**Table A.4-8A: Void** + +## 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-5 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-5 for FR1 interlaced 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.5-3 to table A.5-4 for FR2-1 PUSCH performance requirements: + +- FRC parameters are specified in table A.5-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.5-4 for FR2-1 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.5-4A for FR2-2 PUSCH performance requirements: + +- FRC parameters are specified in table A.5-4A for FR2-2 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_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 [9]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [15]. + +**Table A.5-3: 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 | G-FR2-A5-1 | G-FR2-A5-2 | G-FR2-A5-3 | G-FR2-A5-4 | G-FR2-A5-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 (Note 2) | 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 without PT-RS | 42768 | 85536 | 20736 | 42768 | 85536 | +| Total number of bits per slot with PT-RS (Note 3) | 40986 | 81972 | 19872 | 40986 | 81972 | +| Total symbols per slot without PT-RS | 7128 | 14256 | 3456 | 7128 | 14256 | +| Total symbols per slot with PT-RS (Note 3) | 6831 | 13662 | 3312 | 6831 | 13662 | + +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 [9]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [15]. + +NOTE 3: PT-RS configuration $K_{PT-RS} = 2$ , $L_{PT-RS} = 1$ . + +**Table A.5-4: 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 | G-FR2-A5-6 | G-FR2-A5-7 | G-FR2-A5-8 | G-FR2-A5-9 | G-FR2-A5-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 (Note 2) | 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 without PT-RS | 38016 | 76032 | 18432 | 38016 | 76032 | +| Total number of bits per slot with PT-RS (Note 3) | 36432 | 72864 | 17664 | 36432 | 72864 | +| Total symbols per slot without PT-RS | 6336 | 12672 | 3072 | 6336 | 12672 | +| Total symbols per slot with PT-RS (Note 3) | 6072 | 12144 | 2944 | 6072 | 12144 | + +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 [9]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [15]. + +NOTE 3: PT-RS configuration $K_{PT-RS} = 2$ , $L_{PT-RS} = 1$ . + +**Table A.5-4A: FRC parameters for FR2-2 PUSCH performance requirements, transform precoding disabled, Additional DM-RS position = pos1 and 1 transmission layer (64QAM, R=567/1024)** + +| Reference channel | G-FR2-A5-11 | G-FR2-A5-12 | G-FR2-A5-13 | +|---------------------------------------------------|-------------|-------------|-------------| +| Subcarrier spacing [kHz] | 120 | 120 | 480 | +| Allocated resource blocks | 66 | 66 | 66 | +| CP-OFDM Symbols per slot (Note 1) | 8 | 8 | 8 | +| Modulation | 64QAM | 64QAM | 64QAM | +| Code rate (Note 2) | 567/1024 | 567/1024 | 567/1024 | +| Payload size (bits) | 21000 | 83976 | 21000 | +| Transport block CRC (bits) | 24 | 24 | 24 | +| Code block CRC size (bits) | 24 | 24 | 24 | +| Number of code blocks - C | 3 | 10 | 3 | +| Code block size including CRC (bits) (Note 2) | 7032 | 8424 | 7032 | +| Total number of bits per slot without PT-RS | 38016 | 152064 | 38016 | +| Total number of bits per slot with PT-RS (Note 3) | 36432 | 145728 | 36432 | +| Total symbols per slot without PT-RS | 6336 | 25344 | 6336 | +| Total symbols per slot with PT-RS (Note 3) | 6072 | 24288 | 6072 | + +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 [9]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [15]. + +NOTE 3: PT-RS configuration $K_{PT-RS} = 2$ , $L_{PT-RS} = 1$ . + +**Table A.5-5: 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 [9]. | | | +| NOTE 2: Code block size including CRC (bits) equals to K' in clause 5.2.2 of TS 38.212 [15]. | | | +| 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: 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 | + +**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 in FR1** + +| 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 | + +**Table A.6-7: Test preambles for high speed train short formats in FR2** + +| Burst format | SCS (kHz) | Ncs | Logical sequence index | v | +|--------------|-----------|-----|------------------------|---| +| C2 | 120 | 0 | 0 | 0 | + +**Table A.6-8: Test preambles for PRACH with $L_{RA}=139$ , $L_{RA}=571$ and $L_{RA}=1151$ for 120 kHz and 480 kHz SCS** + +| Burst format | SCS (kHz) | $L_{RA}$ | Ncs | Logical sequence index | v | +|--------------|-----------|----------|-----|------------------------|---| +| A2
B4, C2 | 120 | 571 | 285 | 0 | 0 | +| | 120 | 1151 | 575 | 0 | 0 | +| | 480 | 139 | 69 | 0 | 0 | +| | 480 | 571 | 285 | 0 | 0 | + +## A.7 Fixed Reference Channels for performance requirements (16QAM, $R=434/1024$ ) + +The parameters for the reference measurement channels are specified in table A.7-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.7-2 for FR2-1 PUSCH performance requirements 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.7-3 for FR2-2 PUSCH performance requirements 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.7-4 for FR1 PUSCH performance requirements with transform precoding disabled, additional DM-RS position = pos1 and 4 transmission layers. + +**Table A.7-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 | G-FR2-A7-1 | G-FR2-A7-2 | G-FR2-A7-3 | G-FR2-A7-4 | G-FR2-A7-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 (Note 2) | 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 without PT-RS | 57024 | 114048 | 27648 | 57024 | 114048 | +| Total number of bits per slot with PT-RS (Note 3) | 54648 | 109296 | 26496 | 54648 | 109296 | +| Total symbols per slot without PT-RS | 14256 | 28512 | 6912 | 14256 | 28512 | +| Total symbols per slot with PT-RS (Note 3) | 13662 | 27324 | 6624 | 13662 | 27324 | + +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 [9]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [15]. + +NOTE 3: PT-RS configuration $K_{PT-RS} = 2$ , $L_{PT-RS} = 1$ . + +**Table A.7-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 | G-FR2-A7-6 | G-FR2-A7-7 | G-FR2-A7-8 | G-FR2-A7-9 | G-FR2-A7-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 (Note 2) | 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 without PT-RS | 50688 | 101376 | 24576 | 50688 | 101376 | +| Total number of bits per slot with PT-RS (Note 3) | 48576 | 97152 | 23552 | 48576 | 97152 | +| Total symbols per slot without PT-RS | 12672 | 25344 | 6144 | 12672 | 25344 | +| Total symbols per slot with PT-RS (Note 3) | 12144 | 24288 | 5888 | 12144 | 24288 | + +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 [9]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [15]. + +NOTE 3: PT-RS configuration $K_{PT-RS} = 2$ , $L_{PT-RS} = 1$ . + +**Table A.7-3: FRC parameters for FR2-2 PUSCH performance requirements, transform precoding disabled, Additional DM-RS position = pos1 and 2 transmission layers (16QAM, R=434/1024)** + +| Reference channel | G-FR2-A7-11 | G-FR2-A7-12 | G-FR2-A7-13 | +|---------------------------------------------------|-------------|-------------|-------------| +| Subcarrier spacing [kHz] | 120 | 120 | 480 | +| Allocated resource blocks | 66 | 264 | 66 | +| CP-OFDM Symbols per slot (Note 1) | 8 | 8 | 8 | +| Modulation | 16QAM | 16QAM | 16QAM | +| Code rate (Note 2) | 434/1024 | 434/1024 | 434/1024 | +| Payload size (bits) | 21504 | 86040 | 21504 | +| Transport block CRC (bits) | 24 | 24 | 24 | +| Code block CRC size (bits) | 24 | 24 | 24 | +| Number of code blocks - C | 3 | 11 | 3 | +| Code block size including CRC (bits) (Note 2) | 7200 | 7848 | 7200 | +| Total number of bits per slot without PT-RS | 50688 | 202752 | 50688 | +| Total number of bits per slot with PT-RS (Note 4) | 48576 | 194304 | 48576 | +| Total symbols per slot without PT-RS | 12672 | 50688 | 12672 | +| Total symbols per slot with PT-RS (Note 4) | 12144 | 48576 | 12144 | + +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 [9]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [15]. + +NOTE 3: The calculation of the "Total number of bits per slot" and "Total symbols per slot" fields include the REs taken up by CSI part 1 and CSI part 2, if present. + +NOTE 4: PT-RS configuration $K_{PT-RS} = 2$ , $L_{PT-RS} = 1$ . + +**Table A.7-4: FRC parameters for FR1 PUSCH performance requirements, transform precoding disabled, Additional DM-RS position = pos1 and 4 transmission layers (16QAM, R=434/1024)** + +| Reference channel | G-FR1-A7-1 | G-FR1-A7-2 | G-FR1-A7-3 | G-FR1-A7-4 | +|-----------------------------------------------|------------|------------|------------|------------| +| Subcarrier spacing [kHz] | 15 | 15 | 30 | 30 | +| Allocated resource blocks | 25 | 270 | 24 | 273 | +| CP-OFDM Symbols per slot (Note 1) | 12 | 12 | 12 | 12 | +| Modulation | 16 QAM | 16 QAM | 16 QAM | 16 QAM | +| Code rate (Note 2) | 434/1024 | 434/1024 | 434/1024 | 434/1024 | +| Payload size (bits) | 24576 | 262376 | 23568 | 270576 | +| Transport block CRC (bits) | 24 | 24 | 24 | 24 | +| Code block CRC size (bits) | 24 | 24 | 24 | 24 | +| Number of code blocks - C | 3 | 32 | 3 | 33 | +| Code block size including CRC (bits) (Note 2) | 8224 | 8224 | 7888 | 8224 | +| Total number of bits per slot | 57600 | 622080 | 55296 | 628992 | +| Total symbols per slot | 14400 | 155520 | 13824 | 157248 | + +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 [9]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [15]. + +## A.8 Fixed Reference Channels for performance requirements (QPSK, R=157/1024) + +Note: Different FRC numbers are assigned in TS 38.141-1 [5] for the FRCs in this annex. + +The parameters for the reference measurement channels are specified in table A.8-1 and A.8-2 for FR1 PUSCH performance requirements for 2-step RA type with Additional DM-RS position equals to pos2 and pos1 respectively. + +**Table A.8-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-A8-1 | G-FR1-A8-2 | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------| +| Subcarrier spacing [kHz] | 15 | 30 | +| Allocated resource blocks | 2 | 2 | +| 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) | 0 | 0 | +| 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 symbols 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 with l0= 2 as per Table 6.4.1.1.3-3 of TS 38.211 [9]. | | | +| NOTE 2: Code block size including CRC (bits) equals to K' in clause 5.2.2 of TS 38.212 [15]. | | | + +**Table A.8-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-A8-3 | G-FR1-A8-4 | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------| +| Subcarrier spacing [kHz] | 15 | 30 | +| Allocated resource blocks | 2 | 2 | +| 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) | 0 | 0 | +| 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 symbols 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 with l0= 2 as per Table 6.4.1.1.3-3 of TS 38.211 [9]. | | | +| NOTE 2: Code block size including CRC (bits) equals to K' in clause 5.2.2 of TS 38.212 [15]. | | | + +## A.9 Fixed Reference Channels for performance requirements (256QAM, R=682.5/1024) + +Note: Different FRC numbers are assigned in TS 38.141-1 [5] for the FRCs in this annex. + +The parameters for the reference measurement channels are specified in table A.9-1 for FR1 PUSCH performance requirements: + +- FRC parameters are specified in table A.9-1 for FR1 PUSCH with transform precoding disabled, *Additional DM-RS position = pos1* and 1 transmission layer. + +**Table A.9-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-A9-1 | G-FR1-A9-2 | G-FR1-A9-3 | G-FR1-A9-4 | G-FR1-A9-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/1024 | 682/1024 | 682/1024 | 682/1024 | 682/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, $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 [15]. + +## A.10 Fixed Reference Channels for performance requirements (64QAM, R=517/1024) + +The parameters for the reference measurement channels are specified in table A.10-1, A.10-2 and A.10-3 for FR2 PUSCH performance requirements: + +- FRC parameters are specified in table A.10-1 for FR2 PUSCH with transform precoding disabled, *Additional DM-RS position = pos0* and 1 transmission layer. +- FRC parameters are specified in table A.10-2 for FR2 PUSCH with transform precoding disabled, *Additional DM-RS position = pos1* and 1 transmission layer. +- FRC parameters are specified in table A.10-3 for FR2 PUSCH with transform precoding disabled, *Additional DM-RS position = pos2* and 1 transmission layer. + +The parameters for the reference measurement channels are specified in table A.10-4, table A.10-5 and table A.10-6 for FR2 PUSCH UL timing adjustment performance requirements: + +- FRC parameters are specified in table A.10-4 for FR2 UL timing adjustment requirements, PUSCH with transform precoding disabled, *Additional DM-RS position = pos0* and 1 transmission layer. +- FRC parameters are specified in table A.10-5 for FR2 UL timing adjustment requirements, PUSCH with transform precoding disabled, *DM-RS position = pos1* and 1 transmission layer. +- FRC parameters are specified in table A.10-6 for FR2 UL timing adjustment requirements, PUSCH with transform precoding disabled, *Additional Additional DM-RS position = pos2* and 1 transmission layer. + +**Table A.10-1: FRC parameters for FR2 PUSCH performance requirements, transform precoding disabled, Additional DM-RS position = pos0 and 1 transmission layer (64QAM, R=517/1024)** + +| Reference channel | G-FR2-A10-1 | G-FR2-A10-2 | +|------------------------------------------------------|-------------|-------------| +| Subcarrier spacing [kHz] | 120 | 120 | +| Allocated resource blocks | 32 | 132 | +| Data bearing CP-OFDM Symbols per slot (Note 1) | 9 | 9 | +| Modulation | 64QAM | 64QAM | +| Code rate (Note 2) | 517/1024 | 517/1024 | +| Payload size (bits) | 10504 | 43032 | +| Transport block CRC (bits) | 24 | 24 | +| Code block CRC size (bits) | 24 | 24 | +| Number of code blocks - C | 2 | 6 | +| Code block size including CRC (bits) (Note 2) | 5288 | 7200 | +| Total number of bits per slot without PT-RS | 20736 | 85536 | +| Total number of bits per slot with PT-RS (Note 3) | 19872 | 81972 | +| Total resource elements per slot without PT-RS | 3456 | 14256 | +| Total resource elements per slot with PT-RS (Note 3) | 3312 | 13662 | + +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 [9]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [15]. + +NOTE 3: PT-RS configuration $K_{PT-RS} = 2$ , $L_{PT-RS} = 1$ . + +**Table A.10-2: FRC parameters for FR2 PUSCH performance requirements, transform precoding disabled, Additional DM-RS position = pos1 and 1 transmission layer (64QAM, R=517/1024)** + +| Reference channel | G-FR2-A10-3 | G-FR2-A10-4 | +|------------------------------------------------------|-------------|-------------| +| Subcarrier spacing [kHz] | 120 | 120 | +| Allocated resource blocks | 32 | 132 | +| Data bearing CP-OFDM Symbols per slot (Note 1) | 8 | 8 | +| Modulation | 64QAM | 64QAM | +| Code rate (Note 2) | 517/1024 | 517/1024 | +| Payload size (bits) | 9224 | 37896 | +| Transport block CRC (bits) | 24 | 24 | +| Code block CRC size (bits) | 24 | 24 | +| Number of code blocks - C | 2 | 5 | +| Code block size including CRC (bits) (Note 2) | 4648 | 7608 | +| Total number of bits per slot without PT-RS | 18432 | 76032 | +| Total number of bits per slot with PT-RS (Note 3) | 17664 | 72864 | +| Total resource elements per slot without PT-RS | 3072 | 12672 | +| Total resource elements per slot with PT-RS (Note 3) | 2944 | 12144 | + +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 [9]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [15]. + +NOTE 3: PT-RS configuration $K_{PT-RS} = 2$ , $L_{PT-RS} = 1$ . + +**Table A.10-3: FRC parameters for FR2 PUSCH performance requirements, transform precoding disabled, Additional DM-RS position = pos2 and 1 transmission layer (64QAM, R=517/1024)** + +| Reference channel | G-FR2-A10-5 | G-FR2-A10-6 | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------| +| Subcarrier spacing [kHz] | 120 | 120 | +| Allocated resource blocks | 32 | 132 | +| Data bearing CP-OFDM Symbols per slot (Note 1) | 7 | 7 | +| Modulation | 64QAM | 64QAM | +| Code rate (Note 2) | 517/1024 | 517/1024 | +| Payload size (bits) | 8064 | 33816 | +| Transport block CRC (bits) | 24 | 24 | +| Code block CRC size (bits) | - | 24 | +| Number of code blocks - C | 1 | 5 | +| Code block size including CRC (bits) (Note 2) | 8088 | 6792 | +| Total number of bits per slot without PT-RS | 16128 | 66528 | +| Total number of bits per slot with PT-RS (Note 3) | 15456 | 63756 | +| Total resource elements per slot without PT-RS | 2688 | 11088 | +| Total resource elements per slot with PT-RS (Note 3) | 2576 | 10626 | +| 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 with $l_0 = 0$ and $l = 4, 8$ as per Table 6.4.1.1.3-3 of TS 38.211 [9]. | | | +| NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [15]. | | | +| NOTE 3: PT-RS configuration $K_{PT-RS} = 2$ , $L_{PT-RS} = 1$ . | | | + +**Table A.10-4: FRC parameters for FR2 UL timing adjustment requirements, PUSCH with transform precoding disabled, Additional DM-RS position = pos0 and 1 transmission layer (64QAM, R=517/1024)** + +| Reference channel | G-FR2-A10-7 | G-FR2-A10-8 | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------| +| Subcarrier spacing [kHz] | 120 | 120 | +| Allocated resource blocks | 16 | 66 | +| Data bearing CP-OFDM Symbols per slot (Note 1) | 9 | 9 | +| Modulation | 64QAM | 64QAM | +| Code rate (Note 2) | 517/1024 | 517/1024 | +| Payload size (bits) | 5248 | 21504 | +| Transport block CRC (bits) | 24 | 24 | +| Code block CRC size (bits) | - | 24 | +| Number of code blocks - C | 1 | 3 | +| Code block size including CRC (bits) (Note 2) | 5272 | 7200 | +| Total number of bits per slot without PT-RS | 10368 | 42768 | +| Total number of bits per slot with PT-RS (Note 3) | 9936 | 40986 | +| Total resource elements per slot without PT-RS | 1728 | 7128 | +| Total resource elements per slot with PT-RS (Note 3) | 1656 | 6831 | +| 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 [9]. | | | +| NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [15]. | | | +| NOTE 3: PT-RS configuration $K_{PT-RS} = 2$ , $L_{PT-RS} = 1$ . | | | + +**Table A.10-5: FRC parameters for FR2 UL timing adjustment requirements, PUSCH with transform precoding disabled, Additional DM-RS position = pos1 and 1 transmission layer (64QAM, R=517/1024)** + +| Reference channel | G-FR2-A10-9 | G-FR2-A10-10 | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|--------------| +| Subcarrier spacing [kHz] | 120 | 120 | +| Allocated resource blocks | 16 | 66 | +| Data bearing CP-OFDM Symbols per slot (Note 1) | 8 | 8 | +| Modulation | 64QAM | 64QAM | +| Code rate (Note 2) | 517/1024 | 517/1024 | +| Payload size (bits) | 4608 | 18960 | +| Transport block CRC (bits) | 24 | 24 | +| Code block CRC size (bits) | - | 24 | +| Number of code blocks - C | 1 | 3 | +| Code block size including CRC (bits) (Note 2) | 4632 | 6352 | +| Total number of bits per slot without PT-RS | 9216 | 38016 | +| Total number of bits per slot with PT-RS (Note 3) | 8832 | 36432 | +| Total resource elements per slot without PT-RS | 1536 | 6336 | +| Total resource elements per slot with PT-RS (Note 3) | 1472 | 6072 | +| 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 [9]. | | | +| NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [15]. | | | +| NOTE 3: PT-RS configuration $K_{PT-RS} = 2$ , $L_{PT-RS} = 1$ . | | | + +**Table A.10-6: FRC parameters for FR2 UL timing adjustment requirements, PUSCH with transform precoding disabled, Additional DM-RS position = pos2 and 1 transmission layer (64QAM, R=517/1024)** + +| Reference channel | G-FR2-A10-11 | G-FR2-A10-12 | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|--------------| +| Subcarrier spacing [kHz] | 120 | 120 | +| Allocated resource blocks | 16 | 66 | +| Data bearing CP-OFDM Symbols per slot (Note 1) | 7 | 7 | +| Modulation | 64QAM | 64QAM | +| Code rate (Note 2) | 517/1024 | 517/1024 | +| Payload size (bits) | 4032 | 16896 | +| Transport block CRC (bits) | 24 | 24 | +| Code block CRC size (bits) | - | 24 | +| Number of code blocks - C | 1 | 3 | +| Code block size including CRC (bits) (Note 2) | 4056 | 5664 | +| Total number of bits per slot without PT-RS | 8064 | 33264 | +| Total number of bits per slot with PT-RS (Note 3) | 7728 | 31878 | +| Total resource elements per slot without PT-RS | 1344 | 5544 | +| Total resource elements per slot with PT-RS (Note 3) | 1288 | 5313 | +| 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 with $l_0 = 0$ and $l = 4, 8$ as per Table 6.4.1.1.3-3 of TS 38.211 [9]. | | | +| NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [15]. | | | +| NOTE 3: PT-RS configuration $K_{PT-RS} = 2$ , $L_{PT-RS} = 1$ . | | | + +## A.11 Fixed Reference Channels for performance requirements (64QAM, R=438/1024) + +The parameters for the reference measurement channels are specified in table A.11-1 for FR1 PUSCH performance requirements: + +- FRC parameters are specified in table A.11-1 for FR1 PUSCH with transform precoding disabled, *Additional DM-RS position = pos1* and 4 transmission layers. + +**Table A.11-1: FRC parameters for FR1 PUSCH performance requirements, transform precoding disabled, *Additional DM-RS position = pos1* and 4 transmission layers (64QAM, R=438/1024)** + +| Reference channel | G-FR1-A11-1 | G-FR1-A11-2 | G-FR1-A11-3 | G-FR1-A11-4 | G-FR1-A11-5 | G-FR1-A11-6 | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------|-------------|-------------|-------------|-------------| +| Subcarrier spacing [kHz] | 15 | 15 | 15 | 30 | 30 | 30 | +| Allocated resource blocks | 25 | 106 | 270 | 24 | 106 | 273 | +| CP-OFDM Symbols per slot (Note 1) | 12 | 12 | 12 | 12 | 12 | 12 | +| Modulation | 64 QAM | 64 QAM | 64 QAM | 64 QAM | 64 QAM | 64 QAM | +| Code rate (Note 2) | 438/1024 | 438/1024 | 438/1024 | 438/1024 | 438/1024 | 438/1024 | +| Payload size (bits) | 36896 | 155776 | 401640 | 35856 | 155776 | 401640 | +| Transport block CRC (bits) | 24 | 24 | 24 | 24 | 24 | 24 | +| Code block CRC size (bits) | 24 | 24 | 24 | 24 | 24 | 24 | +| Number of code blocks - C | 5 | 19 | 48 | 5 | 19 | 48 | +| Code block size including CRC (bits) (Note 2) | 7408 | 8224 | 8392 | 7200 | 8224 | 8392 | +| Total number of bits per slot | 86400 | 366336 | 933120 | 82944 | 366336 | 943488 | +| Total symbols per slot | 14400 | 61056 | 155520 | 13824 | 61056 | 157248 | +| 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 [9]. | | | | | | | +| NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [15]. | | | | | | | + +## 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. A block diagram showing the receiver processing chain: BS TX -> Remove CP -> FFT -> Per-subcarrier Amplitude/phase correction -> Symbol detection/decoding. A box labeled 'Pre-/post FFT time / frequency synchronization' has dotted arrows pointing to 'Remove CP', 'FFT', and 'Per-subcarrier Amplitude/phase correction'. A dashed arrow points from a box labeled 'Reference point for EVM measurement' to the input of the 'Symbol detection/decoding' block, indicating the measurement point is after the per-subcarrier correction.](fe7ce38208f739f617c272d8238c7bfa_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] -.-> Symbol_detection + +``` + +Figure B.1-1: Reference point for EVM measurement. A block diagram showing the receiver processing chain: BS TX -> Remove CP -> FFT -> Per-subcarrier Amplitude/phase correction -> Symbol detection/decoding. A box labeled 'Pre-/post FFT time / frequency synchronization' has dotted arrows pointing to 'Remove CP', 'FFT', and 'Per-subcarrier Amplitude/phase correction'. A dashed arrow points from a box labeled 'Reference point for EVM measurement' to the input of the 'Symbol detection/decoding' block, indicating the measurement point is after the per-subcarrier correction. + +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 subcarriers in the frequency domain: + +where + +$T$ is the set of symbols with the considered modulation scheme being active within the slot, + +$\mathcal{K}_t$ is the set of subcarriers within the subcarriers with the considered modulation scheme being active in symbol $t$ , + +$\tilde{s}_{t,k}$ is the ideal signal reconstructed by the measurement equipment in accordance with relevant Tx models, + +$\hat{s}_{t,k}$ 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: + +where + +is the time domain samples of the signal under test. + +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. + +is the RF frequency offset. + +is the phase response of the TX chain. + +is the amplitude response of the TX chain. + +--- + +## B.4 Estimation of frequency offset + +The observation period for determining the frequency offset shall be 1 slot. + +--- + +## B.5 Estimation of time offset + +### B.5.1 General + +The observation period for determining the sample timing difference shall be 1 slot. + +In the following $T$ 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. + +$T$ 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 $T$ are determined: + +and + +where $T = \frac{W}{2}$ if $W$ is odd and $T = \frac{W}{2} - 1$ if $W$ 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) (%) | +|-------------------------|----------|---------------------------------------------------|----------------------------|--------------------------------------------------------------------------| +| 3 | 256 | 18 | 8 | 44.4 | +| 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 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 | +| 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 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 | +| 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. + +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 | +| 25 | 512 | 128 | 110 | 85.9 | +| 30 | 768 | 192 | 164 | 85.9 | +| 35 | 768 | 192 | 164 | 85.9 | +| 40 | 1024 | 256 | 220 | 85.9 | +| 45 | 1024 | 256 | 220 | 85.9 | +| 50 | 1024 | 256 | 220 | 85.9 | +| 60 | 1536 | 384 | 340 | 88.6 | +| 70 | 1536 | 384 | 340 | 88.7 | +| 80 | 2048 | 512 | 454 | 88.7 | +| 90 | 2048 | 512 | 454 | 88.7 | +| 100 | 2048 | 512 | 454 | 88.7 | + +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 for each reference signal subcarrier $f$ . + +- 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. +- 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 moving averaging at the channel edge and for limited reference subcarriers respectively. Diagram A shows a curve representing the moving average window size, which increases from 1 at the first subcarrier to 19 at the 10th subcarrier and remains constant until the channel edge. Diagram B shows a similar curve but with a reduced window size of 5 subcarriers for averaging, starting from the second subcarrier.](89065ed508d3657c36172356d9ecedb4_img.jpg) + +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 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 + +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 moving averaging at the channel edge and for limited reference subcarriers respectively. Diagram A shows a curve representing the moving average window size, which increases from 1 at the first subcarrier to 19 at the 10th subcarrier and remains constant until the channel edge. Diagram B shows a similar curve but with a reduced window size of 5 subcarriers for averaging, starting from the second subcarrier. + +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 $\lfloor \frac{N_{slots}}{10} \rfloor$ slots where $N_{slots}$ is the number of slots in a 10 ms measurement interval. + +For FDD the averaging in the time domain equals the 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: + +For TDD, let $N_{dl}$ be the number of slots with downlink symbols within a 10 ms measurement interval, the averaging in the time domain can be calculated from 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). +- 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 $\Delta\tilde{t}_l$ and $\overline{EVM}_{frame,h}$ is calculated using $\Delta\tilde{t}_h$ ( $l$ and $h$ , low and high; where low is the timing $\Delta\tilde{t}_l$ and high is the timing $\Delta\tilde{t}_h$ ). +- In order to unite at least $N_{dl}$ slots, consider the minimum integer number of 10 ms measurement intervals, where $N_{dl}$ is determined by. + $N_{dl} = 10$ for 15 kHz SCS, $N_{dl} = 20$ for 30 kHz SCS and $N_{dl} = 40$ for 60 kHz SCS normal CP. +- Unite by RMS. + +## Annex C (normative): Error Vector Magnitude (FR2) + +### C.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 C.1-1 below. + +![Figure C.1-1: Reference point for EVM measurement. A block diagram showing the signal flow from BS TX through Remove CP, FFT, Per-subcarrier Amplitude/phase and CPE correction, and Symbol detection/decoding. A 'Pre-/post FFT time / frequency synchronization' block is shown above the main path, with dashed arrows pointing to the Remove CP, FFT, and Per-subcarrier correction blocks. A dashed arrow from a 'Reference point for EVM measurement' block points to the output of the Per-subcarrier correction block.](d7a98a717edbc26ca1508aaab7a566f4_img.jpg) + +``` + +graph LR + BS_TX[BS TX] --> Remove_CP[Remove CP] + Remove_CP --> FFT[FFT] + FFT --> Per_subcarrier[Per-subcarrier Amplitude/phase and CPE correction] + Per_subcarrier --> Symbol_detection[Symbol detection/decoding] + Pre_post_fft[Pre-/post FFT time / frequency synchronization] -.-> Remove_CP + Pre_post_fft -.-> FFT + Pre_post_fft -.-> Per_subcarrier + Ref_point[Reference point for EVM measurement] -.-> Per_subcarrier + +``` + +Figure C.1-1: Reference point for EVM measurement. A block diagram showing the signal flow from BS TX through Remove CP, FFT, Per-subcarrier Amplitude/phase and CPE correction, and Symbol detection/decoding. A 'Pre-/post FFT time / frequency synchronization' block is shown above the main path, with dashed arrows pointing to the Remove CP, FFT, and Per-subcarrier correction blocks. A dashed arrow from a 'Reference point for EVM measurement' block points to the output of the Per-subcarrier correction block. + +Figure C.1-1: Reference point for EVM measurement + +### C.2 Basic unit of measurement + +The basic unit of EVM measurement is defined over one slot in the time domain and subcarriers in the frequency domain: + +where + +is the set of symbols with the considered modulation scheme being active within the slot, + +is the set of subcarriers within the subcarriers with the considered modulation scheme being active in symbol $t$ , + +is the ideal signal reconstructed by the measurement equipment in accordance with relevant Tx models, + +is the modified signal under test defined in C.3. + +NOTE: Although the basic unit of measurement is one slot, the equalizer is calculated over 10 ms measurement intervals 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. + +### C.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: + +where + +is the time domain samples of the signal under test. + +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 C.7. + +is the RF frequency offset. + +is the phase response of the TX chain. + +is the amplitude response of the TX chain. + +## C.4 Estimation of frequency offset + +The observation period for determining the frequency offset shall be 1 slot. + +## C.5 Estimation of time offset + +### C.5.1 General + +The observation period for determining the sample timing difference shall be 1 slot. + +In the following $n$ represents the middle sample of the EVM window of length $W$ (defined in C.5.2) or the last sample of the first window half if $W$ is even. + +$n$ 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 the 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 $n$ are determined: + +and + +where if $W$ is odd and $n$ if is even. + +When the cyclic prefix length varies from symbol to symbol then $n$ shall be further restricted to the subset of symbols with the considered modulation scheme being active and with the considered cyclic prefix length type. + +### C.5.2 Window length + +Table C.5.2-1, Table C.5.2-2, Table C.5.2-2a and Table C.5.2-2b specify the EVM window length ( $W$ ) for normal CP for FR2. + +**Table C.5.2-1: EVM window length for normal CP, FR2, 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) (%) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|--------------------------|-----------------------|--------------------------------------------| +| 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 C.5.2-2: EVM window length for normal CP, FR2, 120 kHz SCS** + +| Channel bandwidth (MHz) | FFT size | CP 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 1: 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. + +**Table C.5.2-2a: EVM window length for normal CP, FR2-2, 480 kHz SCS** + +| Channel bandwidth (MHz) | FFT size | CP length in FFT samples | EVM window length W | Ratio of W to total CP length (Note) (%) | +|-------------------------|----------|--------------------------|---------------------|------------------------------------------| +| 400 | 1024 | 72 | [36] | [50] | +| 800 | 2048 | 144 | [72] | [50] | +| 1600 | 4096 | 288 | [144] | [50] | + +NOTE 1: 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. + +**Table C.5.2-2b: EVM window length for normal CP, FR2-2, 960 kHz SCS** + +| Channel bandwidth (MHz) | FFT size | CP length in FFT samples | EVM window length W | Ratio of W to total CP length (Note) (%) | +|-------------------------|----------|--------------------------|---------------------|------------------------------------------| +| 400 | 512 | 36 | [18] | [50] | +| 800 | 1024 | 72 | [36] | [50] | +| 1600 | 2048 | 144 | [72] | [50] | +| 2000 | [2048] | [144] | [72] | [50] | + +NOTE 1: 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. + +Table C.5.2-3 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 C.5.2-3: EVM window length for extended CP, FR2, 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) (%) | +|-------------------------|----------|--------------------------|---------------------|------------------------------------------| +| 50 | 1024 | 256 | 220 | 85.9 | +| 100 | 2048 | 512 | 440 | 85.9 | +| 200 | 4096 | 1024 | 880 | 85.9 | + +NOTE: These percentages are informative. + +## C.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 intervals. 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: + +- nominal demodulation reference signals 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. + +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). + +Where $N$ is the number of reference signal time-domain locations $t_i$ from 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 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 C.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. 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, $\mathcal{S}$ is the set of subcarriers where PT-RS are mapped, where $\mathcal{O}$ is the set of OFDM symbols where PT-RS are mapped while $\hat{h}$ and $h$ 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 $\hat{h}$ to remove influence of the CPE, and obtain estimate of the complex coefficient's phase + +(t) + +![Figure C.6-1: Reference subcarrier smoothing in the frequency domain. The figure contains 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 stays constant. Diagram B shows the process for a 1RB allocation with a reduced window size of 5 subcarriers.](832ff030ba600d7d805d1e3dcc534373_img.jpg) + +Figure C.6-1 consists of two diagrams, A and B, illustrating reference subcarrier smoothing in the frequency domain. + +**Diagram A: Moving averaging at channel edge** + +This diagram shows a series of vertical bars representing reference subcarriers. The first bar is labeled "The first reference subcarrier is not averaged". The second bar is labeled "The second reference subcarrier is the average of the first three subcarriers". A curve starts at the first bar and rises, eventually plateauing. An arrow points to the plateau with the text: "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". Another arrow points to the rising part of the curve with the text: "The subsequent 7 subcarriers are averaged over 5, 7 .. 17 subcarriers". The x-axis is labeled "Reference subcarriers" with a right-pointing arrow. + +**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** + +This diagram shows a group of five vertical bars. The first three bars are labeled "The first, second and third reference subcarriers are the average of the five subcarriers on left". The last three bars are labeled "The first, second and third reference subcarriers are the average of the five subcarriers on right". The bars are connected by a horizontal line at the top. The x-axis is labeled "Reference subcarriers" with a right-pointing arrow. + +**Text to the right of Diagram B:** + +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 C.6-1: Reference subcarrier smoothing in the frequency domain. The figure contains 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 stays constant. Diagram B shows the process for a 1RB allocation with a reduced window size of 5 subcarriers. + +Figure C.6-1: Reference subcarrier smoothing in the frequency domain + +## C.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_{\text{slots}}$ slots where $N_{\text{slots}}$ is the number of slots in a 10 ms measurement interval. + +For TDD, let $N_{\text{slots}}$ be the number of slots with downlink symbols within a 10 ms measurement interval, the averaging in the time domain can be calculated from $N_{\text{slots}}$ slots of different 10 ms measurement intervals and should have a minimum of $N_{\text{slots}}$ slots averaging length where $N_{\text{slots}}$ is the number of slots in a 10 ms measurement interval. + +- $\text{EVM}_{\text{avg}}$ is derived by: Square the EVM results in each 10 ms measurement intervals. Sum the squares, divide the sum by the number of EVM relevant locations, square-root the quotient (RMS). + +- Where $N_{RB}$ is the number of resource blocks with the considered modulation scheme in slot $i$ . +- The $\sigma_{\text{RMS}}$ is calculated, using the maximum of $\sigma_{\text{RMS}}$ at the window $W$ extremities. Thus $\sigma_{\text{RMS}}$ is calculated using $\sigma_{\text{RMS}}$ and $\sigma_{\text{RMS}}$ is calculated using $(l$ and $h$ , low and high; where low is the timing $l$ and high is the timing $h$ ). +- In order to unite at least $N$ slots, consider the minimum integer number of 10 ms measurement intervals, where $N$ is determined by: + - and $N$ for 60 kHz SCS and $N$ for 120 kHz SCS. +- Unite by RMS. + +--- + +## Annex D (normative): Characteristics of the interfering signals + +The interfering signal shall be a PUSCH 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 TS38.211 [9]. Mapping of PUSCH modulation to receiver requirement are specified in table D-1. + +**Table D-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 E: Void + +--- + +## Annex F (normative): Relationship between EIRP based regulatory requirements and 3GPP requirements + +--- + +### F.1 General + +This annex applies to FR1 *BS type 1-C*, *BS type 1-H* and *BS type 1-O*. + +Some regional requirements are defined per effective isotropic radiated power (EIRP), which is a combination of the transmitted power (or in some cases spectral density) and the effective antenna gain which is a site-specific condition. Such requirements may be applied per antenna, per cell, or per base station. It shall be noted that the definition of BS or cell may differ between regulations. + +The regulations are based on the assumption on *BS type 1-C* conducted requirements and a passive antenna and must be interpreted for active antenna systems that have active beamforming. This annex describes how the power per connector and sum power over *TAB connectors* can be related to such requirements. + +Where the regulator prescribes a method for EIRP calculation, that method supersedes the proposed assessment in this annex. + +--- + +### F.2 Relationship between EIRP based regulatory requirements and conducted requirements + +When 3GPP specifications mandate manufacturer declarations of the (conducted) output power or power spectral density per connector for the base station under the reference conditions stated as a way to accommodate the referred regional requirements without putting requirements on the local site conditions. + +For the case when the base station manufacturer maximum output power or unwanted emission declarations apply per connector, the maximum EIRP can be estimated using the following formulas: + +EIRP per antenna (applicable for *BS type 1-C*): $P_{\text{EIRP}} = P_{\text{Tx}} + G_{\text{Ant}}$ + +EIRP per cell or per BS (applicable for *BS type 1-H*): $P_{\text{EIRPcell}} = 10 \cdot \log \left( \sum 10^{P_{\text{EIRPn}}/10} \right)$ + +In case the EIRP requirement is set per polarization, the summation shall be made per polarization. + +- " $P_{\text{EIRP}}$ " is the resulting effective isotropic radiated power (or radiated power spectral density) resulting from the power (or power spectral density) declared by the manufacturer in dBm (or dBm/measurement BW). +- " $P_{\text{Tx}}$ " is the conducted power or power spectral density declared by the manufacturer in dBm (or dBm/measurement BW). +- " $G_{\text{Ant}}$ " is the effective antenna gain, calculated as the antenna gain (dBi) minus the loss of the site infrastructure connecting the BS antenna connector with the antenna (dB) for the applied frequency. The antenna nominal gain is only applicable within a certain frequency range. For *BS type 1-H*, $G_{\text{Ant}}$ shall be an assumption on the gain of a passive antenna system in order to provide a total power emissions level comparable to the level obtained when a *BS type 1-C* is connected to a passive antenna. A typical example of a passive antenna gain, as used for *BS type 1-O*, is 17 dBi. +- "n" is the index number of the co-located antennas illuminating the same cell. $P_{\text{EIRPn}}$ is the $P_{\text{EIRP}}$ of the *n*th antenna. +- "Cell" is in this annex used in the sense that it is the limited geographical area covered by the carrier transmitted from one site. + +## F.3 Relationship between EIRP based regulatory requirements and OTA requirements + +The regulations set an EIRP limit considering a passive antenna BS. Although the gain of passive antennas may vary somewhat, the variation is in the order of a few dBs. The gain variation of a *BS type 1-O* may be much larger. However, *BS type 1-O* unwanted emissions requirements are defined as TRP, since TRP impacts co-existence properties. + +In order to relate the EIRP values in the specifications to TRP, a fixed assumption has been made on the gain of a typical passive BS antenna. + +Thus, the maximum TRP can be estimated using the following formulas: + +$$\text{TRP limit per antenna: } P_{\text{TRP, antenna}} = P_{\text{EIRP}} - G_{\text{Ant}}$$ + +$$\text{TRP limit per cell or per BS: } P_{\text{TRP}} = P_{\text{TRP, antenna}} + 9 \text{ dB}$$ + +It is noted that the *BS type 1-O* architecture assumes that a BS subject to OTA requirements will have at least 8 antennas. + +In case the TRP requirement is set per polarization, the summation shall be made per polarization. + +- " $P_{\text{EIRP}}$ " is the effective isotropic radiated power (or radiated power spectral density) set in the regulation (assuming a passive BS antenna) in dBm (or dBm/measurement BW). +- " $G_{\text{Ant}}$ " is the effective antenna gain, the antenna gain (dBi) is a fixed reference value of 17 dBi. Directivity value should be used in above equations, however with all antenna losses are assumed zero then we can use effective antenna gain. + +--- + +## Annex 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, FR2(24.25 GHz – 71 GHz). + +#### G.2.1 Delay profiles + +The delay profiles are simplified from the TR 38.901 [16] 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, G.2.1.2 and G.2.1.3 can be used as such. + +Step 1: Use the original TDL model from TR 38.901 [16]. + +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 [16]. + +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, G.2.1.1-4, G.2.1.2-2, G.2.1.2-3, G.2.1.2-4 and G.2.1.2-5 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 table G.2.1.1-1 and the tapped delay line models are specified in tables G.2.1.1-2 ~ 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 | Rayleigh | +| 3 | 15 | -5.1 | Rayleigh | +| 4 | 20 | -5.1 | Rayleigh | +| 5 | 25 | -9.6 | Rayleigh | +| 6 | 50 | -8.2 | Rayleigh | +| 7 | 65 | -13.1 | Rayleigh | +| 8 | 75 | -11.5 | Rayleigh | +| 9 | 105 | -11.0 | Rayleigh | +| 10 | 135 | -16.2 | Rayleigh | +| 11 | 150 | -16.6 | Rayleigh | +| 12 | 290 | -26.2 | Rayleigh | + +**Table G.2.1.1-3: TDLB100 (DS = 100 ns)** + +| Tap # | Delay (ns) | Power (dB) | Fading distribution | +|-------|------------|------------|---------------------| +| 1 | 0 | 0 | Rayleigh | +| 2 | 10 | -2.2 | Rayleigh | +| 3 | 20 | -0.6 | Rayleigh | +| 4 | 30 | -0.6 | Rayleigh | +| 5 | 35 | -0.3 | Rayleigh | +| 6 | 45 | -1.2 | Rayleigh | +| 7 | 55 | -5.9 | Rayleigh | +| 8 | 120 | -2.2 | Rayleigh | +| 9 | 170 | -0.8 | Rayleigh | +| 10 | 245 | -6.3 | Rayleigh | +| 11 | 330 | -7.5 | Rayleigh | +| 12 | 480 | -7.1 | Rayleigh | + +**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 | Rayleigh | +| 3 | 70 | -7.7 | Rayleigh | +| 4 | 190 | -2.5 | Rayleigh | +| 5 | 195 | -2.4 | Rayleigh | +| 6 | 200 | -9.9 | Rayleigh | +| 7 | 240 | -8.0 | Rayleigh | +| 8 | 325 | -6.6 | Rayleigh | +| 9 | 520 | -7.1 | Rayleigh | +| 10 | 1045 | -13.0 | Rayleigh | +| 11 | 1510 | -14.2 | Rayleigh | +| 12 | 2595 | -16.0 | Rayleigh | + +## G.2.1.2 Delay profiles for FR2 + +The delay profiles for FR2 are specified in table G.2.1.2-1 and the tapped delay line models are specified in table G.2.1.2-2 - G.2.1.2-5.. + +**Table G.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 | +| TDLA10 | 16 | 10 ns | 96 ns | 2 ns | +| TDLD10 | 10 | 10 ns | 126 ns | 2 ns | +| TDLD30 | 10 | 30 ns | 375 ns | 5 ns | + +**Table G.2.1.2-2: TDLA30 (DS = 30 ns)** + +| Tap # | Delay (ns) | Power (dB) | Fading distribution | +|-------|------------|------------|---------------------| +| 1 | 0 | -15.5 | Rayleigh | +| 2 | 10 | 0 | Rayleigh | +| 3 | 15 | -5.1 | Rayleigh | +| 4 | 20 | -5.1 | Rayleigh | +| 5 | 25 | -9.6 | Rayleigh | +| 6 | 50 | -8.2 | Rayleigh | +| 7 | 65 | -13.1 | Rayleigh | +| 8 | 75 | -11.5 | Rayleigh | +| 9 | 105 | -11.0 | Rayleigh | +| 10 | 135 | -16.2 | Rayleigh | +| 11 | 150 | -16.6 | Rayleigh | +| 12 | 290 | -26.2 | Rayleigh | + +**Table G.2.1.2-3: TDLA10 (DS = 10 ns)** + +| Tap # | Delay (ns) | Power (dB) | Fading distribution | +|-------|------------|------------|---------------------| +| 1 | 0 | -16.1 | Rayleigh | +| 2 | 4 | 0 | | +| 3 | 6 | -4 | | +| 4 | 8 | -10.2 | | +| 5 | 16 | -18.6 | | +| 6 | 18 | -9.3 | | +| 7 | 22 | -13.7 | | +| 8 | 24 | -17.9 | | +| 9 | 26 | -13.5 | | +| 10 | 30 | -14 | | +| 11 | 40 | -15.4 | | +| 12 | 44 | -18.9 | | +| 13 | 46 | -21.0 | | +| 14 | 48 | -21.6 | | +| 15 | 50 | -19.3 | | +| 16 | 96 | -25.9 | | + +**Table G.2.1.2-4: TLDL10 (DS = 10 ns)** + +| Tap # | Delay (ns) | Power (dB) | Fading distribution | +|-----------------------------------------------|------------|------------|---------------------| +| 1 | 0 | -15.5 | LOS
Rayleigh | +| | 0 | 0 | | +| 2 | 6 | -5.1 | | +| 3 | 14 | -5.1 | | +| 4 | 18 | -9.6 | | +| 5 | 26 | -8.2 | | +| 6 | 40 | -13.1 | | +| 7 | 80 | -11.5 | | +| 8 | 94 | -11.0 | | +| 9 | 98 | -16.2 | | +| 10 | 126 | -16.6 | | +| Note 1: Tap #1 follows a Ricean distribution. | | | | + +**Table G.2.1.2-5: TDLD30 (DS = 30 ns)** + +| Tap # | Delay (ns) | Power (dB) | Fading distribution | +|-----------------------------------------------|------------|------------|---------------------| +| 1 | 0 | -0.2 | LOS
Rayleigh | +| | 0 | -12.4 | | +| 2 | 20 | -21 | | +| 3 | 40 | -16.7 | | +| 4 | 55 | -18.3 | | +| 5 | 80 | -21.9 | | +| 6 | 120 | -27.8 | | +| 7 | 240 | -23.6 | | +| 8 | 285 | -24.8 | | +| 9 | 290 | -30.0 | | +| 10 | 375 | -27.6 | | +| Note 1: Tap #1 follows a Rician distribution. | | | | + +## 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 and G.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 (24.25 GHz – 71 GHz), respectively. + +**Table G.2.2-1: Channel model parameters for FR1** + +| Combination name | Tapped delay line 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 | + +**Table G.2.2-2: Channel model parameters for FR2** + +| Combination name | Tapped delay line model | Maximum Doppler frequency | +|------------------|-------------------------|---------------------------| +| TDLA30-75 | TDLA30 | 75 Hz | +| TDLA30-300 | TDLA30 | 300 Hz | +| TDLA10-650 | TDLA10 | 650 Hz | +| TDLA30-650 | TDLA30 | 650 Hz | +| TDLD10-200 | TDLD10 | 200 Hz | +| TDLD30-200 | TDLD30 | 200 Hz | + +## G.2.3 MIMO Channel Correlation Matrices + +The MIMO channel correlation matrices defined in 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 (ULA) + +The MIMO channel correlation matrices defined in 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** + +| | One antenna | Two antennas | Four antennas | Eight antennas | +|----------------------------|---------------|----------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| gNode B Correlation | $R_{gNB} = 1$ | $R_{gNB} = \begin{pmatrix} 1 & \alpha \\ \alpha^* & 1 \end{pmatrix}$ | $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}$ | $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 | | | | + +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{pmatrix} 1 & \alpha \\ \alpha^* & 1 \end{pmatrix}$ | +| 1x4 case | $R_{spat} = 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}$ | +| 1x8 case | $R_{spat} = 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}$ | +| 2x2 case | $R_{spat} = R_{UE} \otimes R_{gNB} = \begin{bmatrix} 1 & \beta \\ \beta^* & 1 \end{bmatrix} \otimes \begin{bmatrix} 1 & \alpha \\ \alpha^* & 1 \end{bmatrix} = \begin{bmatrix} 1 & \alpha & \beta & \beta\alpha \\ \alpha^* & 1 & \beta\alpha^* & \beta \\ \beta^* & \beta^*\alpha & 1 & \alpha \\ \beta^*\alpha^* & \beta^* & \alpha^* & 1 \end{bmatrix}$ | +| 2x4 case | $R_{spat} = R_{UE} \otimes R_{gNB} = \begin{bmatrix} 1 & \beta \\ \beta^* & 1 \end{bmatrix} \otimes \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}$ | +| 2x8 case | $R_{spat} = R_{UE} \otimes R_{gNB} = \begin{bmatrix} 1 & \beta \\ \beta^* & 1 \end{bmatrix} \otimes \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}$ | + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 4x4 case | $R_{spat} = R_{UE} \otimes R_{gNB} = \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} \otimes \begin{bmatrix} 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{bmatrix}$ | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +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: + +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 | | +| 2x2 case | | +| 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 | | + +**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 | | +| 2x8 case | | +| 4x4 case | | + +In Table G.2.3.1.2-4, $I$ is a 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 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 +- $(\bullet)^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, \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 \bullet \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$ . + +For 4-antenna transmitter using two pairs of cross-polarized antenna elements, + +$$R_{UE} = \begin{pmatrix} 1 & \beta \\ \beta^* & 1 \end{pmatrix}$$ + +### 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} = 1$ . + +For 4-antenna receiver using two pairs of cross-polarized antenna elements, + +$$R_{gNB} = \begin{pmatrix} 1 & \alpha \\ \alpha^* & 1 \end{pmatrix}$$ + +For 8-antenna receiver using four pairs of cross-polarized antenna elements, + +$$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}$$ + +### 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} = I_8$ | +| 2x8 case | $R_{low} = I_{16}$ | + +In Table G.2.3.2.3-2, $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 +- Scenario 4-BI-NR350, FR2: Open space + +The high speed train conditions for the test of the baseband performance are three 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 all three scenarios is given by: + +$$(G.3.1)$$ + +where $f_D$ is the Doppler shift and $f_{max}$ is the maximum Doppler frequency. + +For Scenario 1 and Scenario 3, 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. + +For Scenario 4, the cosine of angle $\theta$ is given by: + +$$(G.3.5)$$ + +$$(G.3.6)$$ + +$$(G.3.7)$$ + +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, G.3-4 and G.3-9 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, for band n77 for the 30kHz SCS, and for band n257 for the 120kHz 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 basestation 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 | Scenario 4-BI-NR350, FR2 | +| | 700 m | 300 m | 700 m | +| | 150 m | 2 m | 150 m | +| | 350 km/h | 350 km/h | 350 km/h | +| | 1340 Hz for 15kHz SCS
2334 Hz for 30kHz SCS | 1340 Hz for 15kHz SCS
2334 Hz for 30kHz SCS | 19444 Hz for 120kHz 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 | +| | 700 m | 300 m | +| | 150 m | 2 m | +| | 500 km/h | 500 km/h | +| | 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, periodic sinusoidal-like wave oscillating between approximately -1200 Hz and 1200 Hz over a 50-second time period.](0362d269cf8a825d1c65a468fcc88808_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 is a smooth, periodic wave that starts at approximately 1200 Hz at 0 seconds, decreases to a minimum of about -1200 Hz at 10 seconds, increases to a maximum of about 1200 Hz at 20 seconds, decreases again to about -1200 Hz at 30 seconds, increases to about 1200 Hz at 40 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, periodic sinusoidal-like wave oscillating between approximately -1200 Hz and 1200 Hz over a 50-second time 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 time period.](2efdbbefdd5a8f462a7866e28b50a556_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 curve is a square wave that starts at approximately 1200 Hz at 0 seconds, drops to about -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 time 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, periodic sinusoidal-like wave oscillating between approximately -2000 Hz and 2000 Hz over a 50-second time period.](9e0e01c6247122e4aeb20232ecdfe5b3_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 is a smooth, periodic wave that starts at approximately 2000 Hz at 0 seconds, decreases to a minimum of about -2000 Hz at 10 seconds, increases to a maximum of about 2000 Hz at 20 seconds, decreases again to about -2000 Hz at 30 seconds, increases to about 2000 Hz at 40 seconds, and finally decreases to about -2000 Hz at 50 seconds. + +Graph of Doppler shift (Hz) vs Time (sec) for scenario 1-NR350 (30 kHz SCS). The plot shows a smooth, periodic sinusoidal-like wave oscillating between approximately -2000 Hz and 2000 Hz over a 50-second time 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.](c26110a289eb2c41e31c197c6ccff035_img.jpg) + +This graph shows 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, drops to -2500 Hz at 2 seconds, returns to 2500 Hz at 4 seconds, drops to -2500 Hz at 6 seconds, and continues this pattern. The period of the square wave is approximately 4 seconds. + +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 sinusoidal wave oscillating between approximately 1500 Hz and -1500 Hz over a 50-second time period.](67ba9da7d9adb5f60447e65bf4bb74fa_img.jpg) + +This graph shows 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 sinusoidal wave that starts at approximately 1500 Hz, crosses zero at 5 seconds, reaches a minimum of -1500 Hz at 10 seconds, crosses zero at 15 seconds, reaches a maximum of 1500 Hz at 20 seconds, and continues this pattern. The period of the sinusoidal wave is approximately 20 seconds. + +Figure G.3-5: Doppler shift trajectory for scenario 1-NR500 (15 kHz SCS). The graph shows a sinusoidal 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.](acfcaa452beafc856ac576f670a1f2c4_img.jpg) + +This graph shows 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, drops to -1800 Hz at 2 seconds, returns to 1800 Hz at 4 seconds, drops to -1800 Hz at 6 seconds, and continues this pattern. The period of the square wave is approximately 4 seconds. + +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) + +![Graph of Doppler shift (Hz) vs Time (sec) for scenario 1-NR500 (30 kHz SCS). The plot shows a smooth sinusoidal wave oscillating between approximately -3000 Hz and 3000 Hz over a 50-second time period.](818603aa875f7827229dc7ba1faee7a8_img.jpg) + +This graph shows the Doppler shift trajectory for scenario 1-NR500 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 plot features a smooth, periodic sinusoidal wave that 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 for five full cycles over the 50-second duration. + +Graph of Doppler shift (Hz) vs Time (sec) for scenario 1-NR500 (30 kHz SCS). The plot shows a smooth sinusoidal wave oscillating between approximately -3000 Hz and 3000 Hz over a 50-second time period. + +Figure G.3-7: Doppler shift trajectory for scenario 1-NR500 (30 kHz SCS) + +![Graph of Doppler shift (Hz) vs Time (sec) for scenario 3-NR500 (30 kHz SCS). The plot shows a square wave oscillating between approximately -3000 Hz and 3000 Hz over a 50-second time period.](7a5f8628e9bf1ad30b7257ce3785e17c_img.jpg) + +This graph shows the Doppler shift trajectory for scenario 3-NR500 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 plot features a square wave that starts at 3000 Hz at 0 seconds, drops to -3000 Hz at approximately 2.5 seconds, returns to 3000 Hz at 5 seconds, and continues this pattern for ten full cycles over the 50-second duration. + +Graph of Doppler shift (Hz) vs Time (sec) for scenario 3-NR500 (30 kHz SCS). The plot shows a square wave oscillating between approximately -3000 Hz and 3000 Hz over a 50-second time period. + +Figure G.3-8: Doppler shift trajectory for scenario 3-NR500 (30 kHz SCS) + +![Figure G.3-9: Doppler shift trajectory for scenario 4-BI-NR350, FR2 (120 kHz SCS). The graph shows a periodic sawtooth-like pattern of Doppler shift (Hz) over time (sec). The y-axis ranges from -20000 to 20000 Hz, and the x-axis ranges from 0 to 50 seconds. The pattern consists of approximately 8 cycles, with each cycle showing a sharp drop from a positive value to a negative value, followed by a gradual increase back towards the positive value.](e6b7edf0d92a0843cc21e4ef707c50e5_img.jpg) + +Figure G.3-9: Doppler shift trajectory for scenario 4-BI-NR350, FR2 (120 kHz SCS). The graph shows a periodic sawtooth-like pattern of Doppler shift (Hz) over time (sec). The y-axis ranges from -20000 to 20000 Hz, and the x-axis ranges from 0 to 50 seconds. The pattern consists of approximately 8 cycles, with each cycle showing a sharp drop from a positive value to a negative value, followed by a gradual increase back towards the positive value. + +Figure G.3-9: Doppler shift trajectory for scenario 4-BI-NR350, FR2 (120 kHz SCS) + +## G.4 Moving propagation conditions + +Figure G.4-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 (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, $\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 G.4-1. + +![Figure G.4-1: Moving propagation conditions diagram. It shows a horizontal timeline with a reference point 'Ref' at time t0 and a first tap 'P1' at time t1. The time difference between t0 and t1 is labeled as Δτ. There are also dashed vertical lines representing other taps at later times.](178b298b89a3deeb2d1a8790b64379cc_img.jpg) + +Figure G.4-1: Moving propagation conditions diagram. It shows a horizontal timeline with a reference point 'Ref' at time t0 and a first tap 'P1' at time t1. The time difference between t0 and t1 is labeled as Δτ. 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}$
120 kHz: 1.25 $\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}$
120 kHz: 1.04 $\text{s}^{-1}$ | 15 kHz: 0.18 $\text{s}^{-1}$
30 kHz: 0.36 $\text{s}^{-1}$ | + +NOTE 1: Doppler shift is not taken into account in UL TA scenario Y and Z. + +--- + +## Annex H (informative): Change history + +| Change history | | | | | | | | +|----------------|---------------|------------|----|-----|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-05 | RAN4#83 | R4-1704619 | | | | Specification skeleton | 0.0.1 | +| 2017-05 | RAN4#83 | R4-1705332 | | | | Specification skeleton (revised) | 0.0.2 | +| 2017-05 | RAN4#83 | R4-1706228 | | | | Specification skeleton (revised) | 0.0.3 | +| 2017-07 | RAN4-NR AH #2 | R4-1706983 | | | | Agreed Text Proposal in RAN4 NR AH #2:
R4-1706955 , "TP to TS 38.104: BS classification for NR BS" | 0.1.0 | +| 2018-08 | RAN4#84 | R4-1709212 | | | | Agreed Text Proposal in RAN4 #84:
R4-1708872 , "TP to TS 38.104 BS transmitter transient period" | 0.2.0 | +| 2018-10 | RAN4#84 bis | R4-1711970 | | | | Agreed Text Proposal in RAN4 #84bis:
R4-1710199 , "TP for TS 38.104: out of band blocking (10.4)"
R4-1710587 , "TP for TS 38.104: Relationship with other core specifications (4.1)"
R4-1710588 , "TP for TS 38.104: Relationship between minimum requirements and test requirements (4.2)"
R4-1710589 , "TP for TS 38.104: Regional requirements (4.5)"
R4-1710591 , "TP for TS 38.104: Conducted transmitter characteristics (general) (6.1)"
R4-1710593 , "TP for TS 38.104: Operating band unwanted emissions (conducted) (6.6.4)"
R4-1710594 , "TP for TS 38.104: Conducted receiver characteristics (General) (7.1)"
R4-1710595 , "TP for TS 38.104: Radiated transmitter characteristics (General) (9.1)"
R4-1710598 , "TP for TS 38.104: Radiated receiver characteristics (General) (10.1)"
R4-1711325 , "TP to TS38.104: OTA Output power dynamics (9.4)"
R4-1711363 , "TP to TS 38.104 - Occupied bandwidth (6.6.2)"
R4-1711745 , "TP to TS 38.104 - Conducted and radiated requirement reference points (4.3)"
R4-1711746 , "TP for TS 38.104: Adding applicability table to clause 4.6"
R4-1711747 , "TP for TS 38.104: Operating bands and channel arrangements. (5)"
R4-1711748 , "TP to TS38.104: conducted NR BS output power (6.2)"
R4-1711750 , "TP for TS 38.104: Transmit ON/OFF power (6.4)"
R4-1711753 , "TP for TS 38.104: Time alignment error requirements (6.5)"
R4-1711754 , "TP for TS 38.104: Unwanted emissions, General (Conducted) (6.6.1)"
R4-1711755 , "TP to TS 38.104: Occupied bandwidth for FR1 and FR2 NR BS (9.7)"
R4-1711756 , "TP to TS 38.104: Transmitter spurious emissions (conducted) (6.6.5)"
R4-1711757 , "TP for TS 38.104: Conducted BS transmitter intermodulation for FR1 (section 6.7)"
R4-1711758 , "TP to TS 38.104: Reference Sensitivity (conducted) (7.2)"
R4-1711759 , "TP to TS 38.104: NR BS conducted ACLR requirement in FR1 (6.6.3)"
R4-1711760 , "TP to TS38.104: conducted NR BS receiver spurious emissions (7.6)"
R4-1711761 , "TP to TS38.104: Radiated NR BS transmit power; FR1 (9.2)"
R4-1711762 , "TP to TS38.104: OTA base station output power, FR1 (9.3)"
R4-1711763 , "TP for TS 38.104: OTA Transmit ON/OFF power (9.5)"
R4-1711764 , "TP to TS 38.104 - OTA ACLR"
R4-1711765 , "TP for TS 38.104: OTA Operating band unwanted emissions and Spectrum emissions mask (9.7.4)"
R4-1711766 , "TP for TS 38.104: OTA Spurious emission (9.7.5)"
R4-1711767 , "TP for TS 38.104: Adding specification text for OTA TX IMD requirement in clause 9.8"
R4-1711768 , "TP to TS 38.104: OTA Sensitivity (10.2)"
R4-1711771 , "TP to TS38.104: OTA receiver spurious emissions, FR1 (10.7)"
R4-1711772 , "TP to TS 38.104: Receiver Intermodulation (10.8)"
R4-1711811 , "TP to TS 38.104: NR BS conducted in-band selectivity and blocking requirements in FR1 (7.4)"
R4-1711950 , "TP to TS 38.104: Modulation Quality Skeleton (6.5)" | 0.3.0 | + +| | | | | | | | | +|--|--|--|--|--|--|----------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| | | | | | | R4-1711951 , "TP to TS38.104: frequency error for FR1 NR BS (6.5&9.6)"
R4-1711952 , "TP to TS 38.104: OTA reference sensitivity (10.3)" | | +|--|--|--|--|--|--|----------------------------------------------------------------------------------------------------------------------------------------------------------|--| + +| | | | | | | | | +|---------|-------------|------------|--|--|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2017-11 | RAN4#84 bis | R4-1711971 | | | | Alignment of structure, terminology, and definitions between clauses. | 0.4.0 | +| 2017-12 | RAN4#85 | R4-1714544 | | | | Agreed Text Proposal in RAN4 #85:
R4-1712614 , "TP to TS 38.104 - OTA sensitivity (10.2)"
R4-1712648 , "TP to TS 38.104: corrections for the applicability of "BS type" and "requirement set" definitions"
R4-1712964 , "TP for TS 38.104: out of band blocking (7.5)"
R4-1713631 , "TP to 38.104 on introduction of n71"
R4-1713632 , "TP to 38.104, clause 4.7 (Requirements for contiguous and non-contiguous spectrum)"
R4-1713633 , "TP to 38.104, clause 4.8 (Requirements for BS capable of multi-band operation)"
R4-1713634 , "TP to 38.104, clause 6.6.4.2.6 (basic limits for additional requirements for operating band unwanted emissions)"
R4-1714116 , "TP to TS 38.104: Revision of the TRP definition"
R4-1714117 , "TP to TS 38.104: Radiated NR BS transmit power; 2-O (9.2.3)"
R4-1714121 , "TP to TS 38.104: OTA Output power dynamics (9.4)"
R4-1714125 , "TP to TS 38.104 v0.4.0: OTA TDD Off power"
R4-1714127 , "TP for TS 38.104: OTA frequency error (9.6.1)"
R4-1714129 , "TP to TS 38.104: NR BS conducted CACLR requirements in FR1 (6.6.3)"
R4-1714134 , "TP to TS 38.104v0.4.0: Absolute levels for FR2 ACLR absolute levels for NR BS"
R4-1714136 , "TP for TS 38.104: Update of OTA TX IM requirement for sub-clause 4.9 and sub-clause 9.8"
R4-1714141 , "TP to TS 38.104: Reference Sensitivity (conducted) (7.2)"
R4-1714142 , "TP to TS 38.104: NR BS FRCs for receiver requirements"
R4-1714150 , "TP to TS 38.104 - OTA out of band blocking FR1 (10.6)"
R4-1714306 , "TP for TS 38.104: Adding of TRP in terminology in clause 3"
R4-1714307 , "TP to TS 38.104 - Conducted and radiated requirement reference points (4.3)"
R4-1714308 , "TP for TS 38.104: Base station classes (4.4)"
R4-1714310 , "TP to TS 38.104: Directional and TRP requirements identification (directional vs. TRP)"
R4-1714312 , "TP for TS 38.104: Update of applicability table in sub-clause 4.6"
R4-1714313 , "TP to TS 38.104: Operating bands (5.1-5.3)"
R4-1714315 , "TP to TS38.104: frequency error for NR BS (6.5&9.6)"
R4-1714316 , "TP for TS 38.104: Adding text for clause 6.5.2 Modulation quality"
R4-1714317 , "TP to TS 38.104: Dynamic Range for FR1 (conducted)"
R4-1714318 , "TP to TS38.104: ICS requirement (7.8&10.9)"
R4-1714319 , "TP for TS 38.104: Adding text for clause 9.6.4 Modulation quality"
R4-1714320 , "TP for TS 38.104: OTA Spurious emission (9.7.5)"
R4-1714321 , "TP for TS 38.104: OTA Dynamic range (10.4)"
R4-1714390 , "TP to TS 38.104: FR2 RX IM OTA, 10.8.3"
R4-1714428 , "TP to TS 38.104 v0.4.0: Time alignment for CA"
R4-1714430 , "TP to TS 38.104: Transmitter spurious emissions (conducted) (6.6.5)"
R4-1714432 , "TP to TS 38.104: Output Power Dynamics for FR1 (conducted)"
R4-1714433 , "TP to TS 38.104: OTA Rx spurious emissions for BS type O 2 (10.7.3)"
R4-1714435 , "TP to TS 38.104: FR2 REFSENS"
R4-1714437 , "TP for TS 38.104: Conducted Adjacent Channel Leakage Power Ratio (ACLR) (6.6.3)"
R4-1714439 , "TP for TS 38.104: Receiver spurious emission (7.6)"
R4-1714476 , "TP to TR 38.104: Channel arrangement (5.4)"
R4-1714493 , "TP for TS 38.104: Operating band unwanted emissions (6.6.4)"
R4-1714515 , "TP for TS 38.104: OTA Out-of-band emissions (9.7.4)"
R4-1714517 , "TP to TS 38.104: OTA base station output power, 2-O (9.3.3)"
R4-1714518 , "TP to TS 38.104: ACS and blocking update"
R4-1714520 , "Draft TP to TS 38.104: OTA In-band selectivity and blocking (10.5)"
R4-1714525 , "TP to TS 38.104: FR1 RX IM conducted 7.7"
R4-1714526 , "TP to TS 38.104: FR1 RX IM OTA 10.8.2" | 0.5.0 | +| 2017-12 | RAN#78 | RP-172268 | | | | Presented to TSG RAN for approval. | 1.0.0 | +| 2017-12 | RAN#78 | | | | | Approved by plenary – Rel-15 spec under change control | 15.0.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2018-03 | RAN#79 | RP-180264 | 0004 | | F | TS 38.104 Combined updates (NSA) from RAN4 #86 and AH-1801 | 15.1.0 | +| 2018-06 | RAN#80 | RP-181076 | 0005 | | F | TS 38.104 Combined updates (NSA) from RAN4 #86bis and RAN4 #87 | 15.2.0 | +| 2018-09 | RAN#81 | RP-181896 | 0008 | | F | TS 38.104 Combined updates from RAN4 #88 | 15.3.0 | +| 2018-12 | RAN#82 | RP-182837 | 0016 | 1 | F | CR to TS 38.104 on Combined updates from RAN4 #88bis and #89 (including 7.5 kHz carrier shift in UL for remaining bands) | 15.4.0 | +| 2018-12 | RAN#82 | RP-182362 | 0017 | | B | CR to 38.104 on Combined CRs for BS Demodulation performance | 15.4.0 | +| 2019-03 | RAN#83 | RP-190403 | 0019 | | F |

CR to TS 38.104 on Combined updates from RAN4 #90

This document combines the proposed changes in the following Draft CRs from RAN4 #90:

  • - R4-1900284, "Draft CR on NR PUCCH format2 performance requirements for TS 38.104"
  • - R4-1900763, "Draft CR to TS 38.104: Update of performance requirement numbers for DFT-s-OFDM based PUSCH"
  • - R4-1900876, "Draft CR to TS 38.104: On RX spurious emissions requirement"
  • - R4-1900968, "Draft CR for 38.104: Performance requirements for NR PUCCH format 1"
  • - R4-1901329, "Draft CR to 38.104: Annex C.6 correction"
  • - R4-1901330, "Draft CR to 38.104: Abbreviations addition"
  • - R4-1901387, "Draft CR to TS 38.104 BS demodulation PUCCH format 0 requirements"
  • - R4-1901474, "Draft CR to TS 38.104: Corrections on transmitter co-existence and co-location requirements"
  • - R4-1901483, "Draft CR to TS 38.104: Corrections on general intermodulation requirement"
  • - R4-1902239, "Draft CR to TS 38.104: Addition of missing EIRP/EIS definitions in terminology in clause 3.1"
  • - R4-1902241, "Draft CR to 38.104; clarification of BS power limits"
  • - R4-1902245, "Draft CR to 38.104: Correction to FR2 OTA Interfering signal mean power units"
  • - R4-1902246, "Draft CR to 38.104; Correction to definition of OTA reference sensitivity"
  • - R4-1902260, "draft CR to TS 38.104 - update emissions scaling"
  • - R4-1902338, "Draft CR: Update on FR1 range extension for TS38.104"
  • - R4-1902389, "draftCR for 38.104 on PUSCH requirements with CP-OFDM and FR1"
  • - R4-1902394, "Draft CR to TS 38.104 – PUSCH requirements with CP-OFDM for FR2"
  • - R4-1902396, "CR: Updates to PUCCH formats 3 and 4 performance requirements in TS 38.104"
  • - R4-1902444, "Draft CR to TS 38.104: Editorial CR for BS demodulation requirements"
  • - R4-1902561, "Draft CR for updating PRACH performance requirements in TS38.104"
  • - R4-1902571, "Corrections to 38.104 Delay profile calculation"
  • - R4-1902642, "Draft CR to TS 38.104: Correction on multi-band operation related requirements"
| 15.5.0 | +| 2019-06 | RAN#84 | RP-191240 | 0029 | | F |

CR to TS 38.104 Combined updates from RAN4 #90bis and RAN4#91

From RAN4 #90bis:

  • - R4-1903105, "Draft CR to TS 38.104: Corrections on terminologies and editorial errors"
  • - R4-1903319, "Draft CR to TS 38.104: removal of unused definition: "minimum EIRP level under extreme condition""
  • - R4-1903320, "Draft CR to TS 38.104: OSDD information correction"
  • - R4-1903457, "Draft CR to TS 38.104: Removal of FFS for FR2 TDD OFF power level requirement in clause 9.5"
  • - R4-1903499, "Draft CR to 38.104: Correction to unwanted emissions mask for bands n7 and n38"
  • - R4-1903836, "Draft CR to TS 38.104: Correction on description on multi-band operation in section 4.8"
  • - R4-1904024, "Draft CR to TS 38.104 Applicability rules for BS demodulation"
  • - R4-1904234, "draftCR: Correlation matrix for 8Rx in TS 38.104"
  • - R4-1904723, "Draft CR to TS 38.104: Update of performance requirements for DFT-s-OFDM based PUSCH"
  • - R4-1904726, "draftCR for 38.104 on PUSCH requirements with CP-OFDM and FR1"
  • - R4-1904729, "Draft CR on PRACH performance requirements in TS38.104"
  • - R4-1904734, "Draft CR on TS 38.104 Performance requirement"
| 15.6.0 | + +| | | | | | | | +|--|--|--|--|--|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | | | |

for PUCCH format 1"

  • - R4-1904735, "Draft CR on NR PUCCH format2 performance requirements for TS 38.104"
  • - R4-1904739, "Draft CR to TS 38.104 BS demodulation PUCCH format 0 requirements"
  • - R4-1904745, "draftCR: Updates to PUCCH formats 3 and 4 performance requirements in TS 38.104"
  • - R4-1904799, "Draft CR to TS 38.104: FRC update for PUSCH FR1 mapping type B and FR2 DMRS 1+1"
  • - R4-1904816, "Draft CR : Clarification on step 5 and step 6 for delay profiles calculation (38.104)"
  • - R4-1904842, "Draft CR to TS 38.104 BS demodulation CP-OFDM PUSCH FR2 requirements"
  • - R4-1905126, "draft CR to 38.104 for TAE requirements"
  • - R4-1905139, "draft CR to TS 38.104 on EVM measurement (Annex B and C)"
  • - R4-1905140, "Draft CR: editorial correction on FR1 spurious emission requirement in TS38.104"
  • - R4-1905143, "Draft CR for TS 38.104: Addition of NOTE for transmitter intermodulation requirements in certain regions"
  • - R4-1905144, "Draft CR to TS 38.104: FRC reference corrections for the Rx requirements"
  • - R4-1905145, "Draft CR to TS 38.104: Clarification on application of interfering signal offsets for ACS, blocking and intermodulation requirements"
  • - R4-1905148, "Draft CR to TS 38.104: Corrections on out-of-band blocking requirement"

From RAN4 #91:

  • - R4-1906002, "Draft CR to 38.104: Subclause 6.7 and 9.8 transmitter intermodulation – correction of interfering signal type"
  • - R4-1906096, "Draft CR to 38.104: Correction of frequency range for OTA spurious emissions"
  • - R4-1906311, "Draft CR to 38.104: Correction on FRC (Annex A)"
  • - R4-1906346, "Removal of n65 in Rel-15 38.104"
  • - R4-1906915, "Draft CR to TS 38.104: Clarification on application of interfering signal offsets for OTA ACS, blocking and intermodulation requirements"
  • - R4-1906918, "Draft CR to TS 38.104: Clarification on type of interfering signal for ACS, in-band blocking and ICS requirements"
  • - R4-1907110, "Draft CR to TS 38.104: correction of the fundamental frequency limit of 2.55GHz for the spurious emissions"
  • - R4-1907246, "Draft CR to TS 38.104: Update of performance requirements for DFT-s-OFDM based PUSCH"
  • - R4-1907249, "Draft CR to TS 38.104: Correction on the terminology in PUSCH FRC tables"
  • - R4-1907252, "Draft CR to TS38.104: Updates of PRACH performance requirements"
  • - R4-1907255, "Draft CR on NR PUCCH format2 performance requirements for TS 38.104"
  • - R4-1907258, "Draft CR on NR UCI on PUSCH performance requirements for TS 38.104"
  • - R4-1907261, "draftCR: Updates to PUCCH formats 3 and 4 performance requirements in TS 38.104"
  • - R4-1907266, "Draft CR on TS 38.104 Performance requirement for PUCCH format 1"
  • - R4-1907267, "Draft CR on TS 38.104 Performance requirement for multi-slot PUCCH format 1"
  • - R4-1907272, "Draft CR to TS 38.104 BS demodulation PUCCH format 0 requirements"
  • - R4-1907275, "Draft CR to TS 38.104 BS demodulation CP-OFDM PUSCH FR2 requirements"
  • - R4-1907277, "draftCR for 38.104 on PUSCH requirements with CP-OFDM and FR1"
  • - R4-1907629, "Draft CR to 38.104: Term “reference signal” replacing by term “ideal signal” in EVM context"
  • - R4-1907634, "Draft CR to 38.104: corrections to the EVM annex"
  • - R4-1907659, "Draft CR to TS 38.104 on Spurious emission Category B in FR2"
  • - R4-1907661, "Draft CR to 38.104 Definition of contiguous transmission bandwidth"
  • - R4-1907662, "Draft CR to 38.104: BS TAE requirements"
  • - R4-1907664, "Draft CR to 38.104: Clarification of interferer RB frequency for narrowband blocking"
  • - R4-1907672, "Draft CR for TS 38.104: Correction on EVM"
  • - R4-1907689, "Correction to CA carrier spacing"
| +|--|--|--|--|--|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | | | | | +|---------|--------|-----------|------|---|---|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2019-06 | RAN#84 | RP-191252 | 0024 | 1 | B | CR to TS38.104 to introducing spectrum sharing on band n41 | 16.0.0 | +| 2019-06 | RAN#84 | RP-191242 | 0025 | | B | Introduction of band n14 - CR to TS 38.104 | 16.0.0 | +| 2019-06 | RAN#84 | RP-191246 | 0026 | | B | Introduction of band n30 - CR to TS 38.104 | 16.0.0 | +| 2019-06 | RAN#84 | RP-191244 | 0028 | | B | introduce n18 into TS38.104 | 16.0.0 | +| 2019-06 | RAN#84 | RP-191250 | 0030 | 1 | B | n65 introduction to 38.104 | 16.0.0 | +| 2019-06 | RAN#84 | RP-191251 | 0031 | | B | Addition channel bandwidth of 30MHz for n50 in TS 38.104 | 16.0.0 | +| 2019-06 | RAN#84 | RP-191248 | 0032 | | B | CR to 38.104: Introduction of n48 | 16.0.0 | +| 2019-09 | RAN#85 | RP-192049 | 0034 | | A | CR to T 38.104: Implementation of endorsed draft CRs from RAN4#92 (Rel-16)
(Mirrors changes in R4-1908440 for Rel-15 TS 38.104)
- R4-1907940, "Draft CR to TS 38.104: Correction on the terminology in FRC tables in A.1 and A.2"
- R4-1908307, "Draft CR to TS 38.104: Clarification on application of OTA receiver requirements for BS supporting polarization"
- R4-1908387, "Draft CR for TS38.104: editorial correction for reference measurement channel"
- R4-1908619, "Draft CR to TS38.104: Correction on interferer frequency offset values for ACS"
- R4-1908629, "Draft CR to TS38.104: Corrections on EVM window length (Annex B.5.2, C.5.2)"
- R4-1908774, "DraftCR to 38.104: Editorial Corrections to redundant units in clause 10.8.3"
- R4-1908805, "Draft CR to 38.104: Limits in FCC title 47 for OTA operating band unwanted emissions (9.7)"
- R4-1909270, "Draft CR to TS 38.104: Receiver spurious emissions frequency correction"
- R4-1909309, "DraftCR to TS 38.104: text corrections, Rel-15"
- R4-1909310, "DraftCR to 38.104: correction of TAB connectors mapping to TAB connector TX min cell group, Rel-15"
- R4-1909416, "draft CR 38.104 - correct reference to annex F"
- R4-1910066, "Draft CR to TS 38.104: Update of performance requirements for DFT-s-OFDM based PUSCH"
- R4-1910069, "Draft CR on NR PUCCH format2 performance requirements for TS 38.104"
- R4-1910072, "Draft CR on NR UCI on PUSCH performance requirements for TS 38.104"
- R4-1910075, "draftCR for 38.104 on PUSCH requirements with CP-OFDM and FR1"
- R4-1910078, "Draft CR to TS38.104: Updates to NR PRACH performance requirements"
- R4-1910081, "Draft CR to TS 38.104 BS demodulation PUCCH format 0 requirements"
- R4-1910084, "Draft CR to TS 38.104 BS demodulation CP-OFDM PUSCH FR2 requirements"
- R4-1910088, "Draft CR for 38.104: Performance requirements for NR PUCCH format 1"
- R4-1910089, "Draft CR for 38.104: Performance requirements for NR multi-slot PUCCH"
- R4-1910094, "draftCR: Updates to PUCCH formats 3 and 4 performance requirements in TS 38.104"
- R4-1910431, "Corrections to EVM calculations in 38.141-1 annex B"
- R4-1910462, "Draft CR to 38.104: Correction on regional requirements (4.5)"
- R4-1910493, "Draft CR to TS 38.104 correction to Annex C.7"
- R4-1910606, "Draft CR for TS 38.104: Channel spacing for adjacent NR carriers" | 16.1.0 | +| 2019-09 | RAN#85 | RP-192032 | 0035 | 1 | B | CR to introduce 30MHz bandwidth of n41 to TS 38.104 | 16.1.0 | +| 2019-09 | RAN#85 | RP-192029 | 0036 | | B | CR on Introduction and Protection of SUL band n89 into TS 38.104 | 16.1.0 | +| 2019-09 | RAN#85 | RP-192031 | 0037 | | B | CR for TS 38.104: adding wider channel bandwidths in Band n7 | 16.1.0 | +| 2019-09 | RAN#85 | RP-192034 | 0039 | | B | n29 introduction to 38.104 | 16.1.0 | +| 2019-12 | RAN#86 | RP-192999 | 0049 | 1 | A | CR to TS 38.104: Update of performance requirements for DFT-s-OFDM based PUSCH (Rel-16) | 16.2.0 | +| 2019-12 | RAN#86 | RP-193013 | 0050 | 1 | B | Introduction of 2010-2025MHz SUL band into Rel-16 TS 38.104 | 16.2.0 | +| 2019-12 | RAN#86 | RP-193034 | 0055 | | A | Sync raster to SSB resource element mapping | 16.2.0 | +| 2019-12 | RAN#86 | RP-192999 | 0057 | | A | CR on correction of NR PUCCH format2 performance requirements (Rel-16) for TS 38.104 | 16.2.0 | +| 2019-12 | RAN#86 | RP-192999 | 0059 | 1 | A | CR on correction of NR UCI on PUSCH performance requirements (Rel-16) for TS 38.104 | 16.2.0 | +| 2019-12 | RAN#86 | RP-192999 | 0061 | | A | CR on correction on FRC table for FR1 PUSCH performance requirements (Rel-16) for TS 38.104 | 16.2.0 | +| 2019-12 | RAN#86 | RP-192999 | 0063 | 1 | A | CR for 38.104 on PUSCH requirements with CP-OFDM and FR1 | 16.2.0 | +| 2019-12 | RAN#86 | RP-193034 | 0065 | | A | CR for TS38.104: Corrections on channel bandwidth for band n34 | 16.2.0 | +| 2019-12 | RAN#86 | RP-193035 | 0067 | | A | CR to TS38.104: Editorial corrections | 16.2.0 | +| 2019-12 | RAN#86 | RP-193035 | 0070 | 1 | A | CR to 38.104 on Editorial corrections (Rel-16) | 16.2.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|----------------------------------------------------------------------------------------------------------------------|--------| +| 2019-12 | RAN#86 | RP-193034 | 0074 | | A | CR to 38.104 on Receiver spurious emission requirements | 16.2.0 | +| 2019-12 | RAN#86 | RP-193021 | 0075 | 1 | F | CR to remove square brackets for n90 in TS38.104 | 16.2.0 | +| 2019-12 | RAN#86 | RP-192999 | 0077 | | A | Updates to PRACH requirements in TS 38.104 for Rel-16 | 16.2.0 | +| 2019-12 | RAN#86 | RP-193034 | 0081 | | A | CR to TS 38.104: Correction on interference level of receiver dynamic range requirement | 16.2.0 | +| 2019-12 | RAN#86 | RP-193034 | 0083 | | A | CR to TS 38.104: Finalization of interfering RB centre frequency offsets in receiver narrowband blocking requirement | 16.2.0 | +| 2019-12 | RAN#86 | RP-193034 | 0085 | | A | CR to TR 38.104: Correction of table reference of interfering signal for ACS requirement | 16.2.0 | +| 2019-12 | RAN#86 | RP-193034 | 0087 | | A | CR to TS 38.104: Correction on interfering signal frequency offsets for receiver intermodulation requirements | 16.2.0 | +| 2019-12 | RAN#86 | RP-193034 | 0089 | | A | CR to TS 38.104 on corrections to channel raster entries for NR band (Rel-16) | 16.2.0 | +| 2019-12 | RAN#86 | RP-193035 | 0097 | | A | CR to TS38.104: further updates on the abbreviations (section 3.3)-R16 | 16.2.0 | +| 2019-12 | RAN#86 | RP-193023 | 0098 | 1 | B | CR to TS 38.104 - NB-IoT introduction | 16.2.0 | +| 2019-12 | RAN#86 | RP-192999 | 0100 | | F | CR to TS 38.104 BS demodulation PUCCH format 0 requirements | 16.2.0 | +| 2019-12 | RAN#86 | RP-192999 | 0102 | 1 | F | CR to TS 38.104 BS demodulation CP-OFDM PUSCH FR2 requirements | 16.2.0 | +| 2019-12 | RAN#86 | RP-193017 | 0103 | | B | CR to 38.104 - Band n75 - wider CBW | 16.2.0 | +| 2019-12 | RAN#86 | RP-193018 | 0105 | | B | CR for TS 38.104: adding wider channel bandwidths in Band n77/n78 | 16.2.0 | +| 2019-12 | RAN#86 | RP-193016 | 0106 | | B | CR for TS 38.104: Addition channel bandwidth of 40MHz for n38 | 16.2.0 | +| 2019-12 | RAN#86 | RP-193035 | 0108 | | A | CR to 38.104: Correction on FR2 Category B OBUE mask | 16.2.0 | +| 2019-12 | RAN#86 | RP-193002 | 0110 | | A | CR Frame averaging for EVM Annex B and C in TS 38.104 | 16.2.0 | +| 2019-12 | RAN#86 | RP-193035 | 0112 | | A | CR to TS 38.104: OTA TAE correction, Rel-16 | 16.2.0 | +| 2019-12 | RAN#86 | RP-193035 | 0114 | | A | CR to TS 38.104: MR BS class terminology correction, Rel-16 | 16.2.0 | +| 2019-12 | RAN#86 | RP-192999 | 0116 | 1 | F | CR: Updates for PUCCH formats 3 and 4 performance requirements in TS 38.104 (Rel-16) | 16.2.0 | +| 2019-12 | RAN#86 | RP-193035 | 0118 | | A | Correction of limit for TX spurious BS type 1-H | 16.2.0 | +| 2019-12 | RAN#86 | RP-192999 | 0119 | | A | CR for 38.104: Performance requirements for NR PUCCH format 1 | 16.2.0 | +| 2019-12 | RAN#86 | RP-192999 | 0120 | | A | CR for 38.104: Performance requirements for NR multi-slot PUCCH | 16.2.0 | +| 2019-12 | RAN#86 | RP-193035 | 0122 | | A | CR to TS 38.104: Editorial corrections | 16.2.0 | +| 2019-12 | RAN#86 | RP-193035 | 0124 | | A | CR to TS 38.104: Clarification for the number of interfering signals | 16.2.0 | +| 2020-03 | RAN#87 | RP-200381 | 0126 | | B | Introduction of n26 | 16.3.0 | +| 2020-03 | RAN#87 | RP-200382 | 0127 | 1 | B | Introduction of n53 | 16.3.0 | +| 2020-03 | RAN#87 | RP-200384 | 0131 | | B | Introducing new channel bandwidth for band n28 | 16.3.0 | +| 2020-03 | RAN#87 | RP-200410 | 0132 | | F | CR to TS 38.104: Corrections on NB-IoT operation in NR channel bandwidth | 16.3.0 | +| 2020-03 | RAN#87 | RP-200398 | 0134 | 1 | A | CR to TS 38.104: Corrections on rated carrier output power symbols | 16.3.0 | +| 2020-03 | RAN#87 | RP-200379 | 0136 | 1 | C | CR for 38.104: new FRC tables for FR2 PUSCH 2T2R MCS12 | 16.3.0 | +| 2020-03 | RAN#87 | RP-200407 | 0137 | 2 | B | CR for 38.104: introduction of UL timing adjustment | 16.3.0 | +| 2020-03 | RAN#87 | RP-200407 | 0138 | 2 | B | CR for 38.104: Appendix for UL timing adjustment | 16.3.0 | +| 2020-03 | RAN#87 | RP-200386 | 0139 | | B | CR for TS 38.104: adding wider channel bandwidths for n66 | 16.3.0 | +| 2020-03 | RAN#87 | RP-200398 | 0142 | | A | CR to TS 38.104: Regional requirements | 16.3.0 | +| 2020-03 | RAN#87 | RP-200392 | 0143 | | F | Maintenance on the BS BW for n92 and n94 | 16.3.0 | +| 2020-03 | RAN#87 | RP-200398 | 0145 | | A | IntraSlot frequency hopping applicability in the one OFDM symbol test case | 16.3.0 | +| 2020-03 | RAN#87 | RP-200383 | 0146 | 1 | B | CR to 38.104 Band n1 - wider CBW - Additional Channel BW | 16.3.0 | +| 2020-03 | RAN#87 | RP-200385 | 0148 | | B | CR to 38.104 Band n38 - wider CBW - Additional Channel BW | 16.3.0 | +| 2020-03 | RAN#87 | RP-200398 | 0149 | | A | CR to TS 38.104 editorial correction R16 catA | 16.3.0 | +| 2020-03 | RAN#87 | RP-200407 | 0156 | 1 | B | CR for TS 38.104: Introduction of PRACH demodulation requirements for NR HST | 16.3.0 | +| 2020-03 | RAN#87 | RP-200407 | 0157 | 2 | B | CR for 38.104: HST PUSCH demodulation requirements introduction | 16.3.0 | +| 2020-03 | RAN#87 | RP-200407 | 0158 | 2 | B | CR for 38.104: HST PUSCH demodulation Annex including both FRC and channel model | 16.3.0 | +| 2020-03 | RAN#87 | RP-200379 | 0159 | 1 | C | CR for 38.104: Performance requirements for FR2 PUSCH 2T2R 16QAM | 16.3.0 | +| 2020-06 | RAN#88 | RP-200986 | 0164 | | A | CR for 38.104: Performance requirements clarification of PUSCH BS Type O-2 PT-RS configuration for MCS 2 | 16.4.0 | +| 2020-06 | RAN#88 | RP-201043 | 0167 | | F | CR for 38.104: Performance requirements for FR2 PUSCH 2T2R 16QAM | 16.4.0 | +| 2020-06 | RAN#88 | RP-200986 | 0176 | | A | CR to TS 38.104: Correction to out-of-band blocking requirements in subclause 7.5 and subclause 10.6 | 16.4.0 | +| 2020-06 | RAN#88 | RP-200986 | 0178 | | A | CR to TS 38.104: Correction on the CA nominal channel spacing | 16.4.0 | +| 2020-06 | RAN#88 | RP-200986 | 0180 | | A | 30k SSB SCS for n50 | 16.4.0 | +| 2020-06 | RAN#88 | RP-200986 | 0182 | | A | Addition of 30k SSB SCS for Band n38 | 16.4.0 | +| 2020-06 | RAN#88 | RP-200972 | 0185 | | B | CR to TS 38.104: Introduction of FR2 DL 256QAM | 16.4.0 | +| 2020-06 | RAN#88 | RP-200977 | 0190 | | B | CR for TS 38.104: adding 50 MHz CBW for n1 | 16.4.0 | +| 2020-06 | RAN#88 | RP-200986 | 0195 | | A | CR to 38.104: Adding missing clause on Radiated Performance requirements for multi-slot PUCCH (11.3.1) | 16.4.0 | +| 2020-06 | RAN#88 | RP-200980 | 0198 | | B | CR to TS 38.104 - Add 40 MHz CBW in band n3 | 16.4.0 | +| 2020-06 | RAN#88 | RP-200982 | 0199 | | B | CR to TS 38.104 - Add 50 MHz CBW in band n65 | 16.4.0 | + +| | | | | | | | | +|---------|---------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------|--------| +| 2020-06 | RAN#88 | RP-200986 | 0209 | | A | CR to 38.104 on Receiver spurious emissions exclusion band (Rel-16) | 16.4.0 | +| 2020-06 | RAN#88 | RP-200986 | 0211 | | A | CR to 38.104 on EESS protection for bands n257 and n258 (Rel-16) | 16.4.0 | +| 2020-06 | RAN#88 | RP-200986 | 0213 | | A | TS38.104 draft CR on 30KHz SSB SCS for n40 (Rel-16) | 16.4.0 | +| 2020-06 | RAN#88 | RP-200986 | 0207 | 1 | A | CR to 38.104 on Removal of brackets and TBD (Rel-16) | 16.4.0 | +| 2020-06 | RAN#88 | RP-200975 | 0165 | 1 | B | CR for 38.104: HST PUSCH demodulation requirements | 16.4.0 | +| 2020-06 | RAN#88 | RP-200975 | 0166 | 1 | B | CR for 38.104: HST PUSCH demodulation FRC and channel model annexes | 16.4.0 | +| 2020-06 | RAN#88 | RP-200975 | 0186 | 1 | F | CR for 38.104 Introduction of PRACH demodulation requirements for NR HST | 16.4.0 | +| 2020-06 | RAN#88 | RP-200975 | 0187 | 1 | B | CR for 38.104: Performance requirements for UL timing adjustment | 16.4.0 | +| 2020-06 | RAN#88 | RP-201043 | 0168 | 1 | B | CR for TS 38.104: Introduce PUSCH performance requirements at 30% throughput test point | 16.4.0 | +| 2020-06 | RAN#88 | RP-200986 | 0172 | 1 | F | UCI multiplexed on PUSCH requirement | 16.4.0 | +| 2020-06 | RAN#88 | RP-200978 | 0205 | 1 | B | CR to 38.104 for Introduction of band n259 | 16.4.0 | +| 2020-09 | RAN#89 | RP-201497 | 0218 | 1 | B | CR for 38.104: HST PUSCH demodulation requirements | 16.5.0 | +| 2020-09 | RAN#89 | RP-201497 | 0219 | 1 | B | CR for 38.104: HST PUSCH demodulation FRC and channel model annexes | 16.5.0 | +| 2020-09 | RAN#89 | RP-201502 | 0220 | 1 | B | Introduction of LTE/NR spectrum sharing in band 48/n48 frequency range | 16.5.0 | +| 2020-09 | RAN#89 | RP-201512 | 0222 | | A | CR to TS 38.104: Correction of co-location requirement in subclause 7.5.3 | 16.5.0 | +| 2020-09 | RAN#89 | RP-201512 | 0224 | | A | CR to TS38.104: Add 30k SSB SCS for Band n34 and n39 | 16.5.0 | +| 2020-09 | RAN#89 | RP-201512 | 0227 | 1 | A | CR to TS 38.104: OTA receiver spurious requirements for EESS protection (rel-16) | 16.5.0 | +| 2020-09 | RAN#89 | RP-201499 | 0228 | | F | CR for 38.104: Performance requirements for UL timing adjustment | 16.5.0 | +| 2020-09 | RAN#89 | RP-201507 | 0229 | | F | Correction to NB-IoT Bands with n26 | 16.5.0 | +| 2020-09 | RAN#89 | RP-201512 | 0233 | 1 | A | CR to 38.104: Annex B and C clarification on equalisation calculation (B.6, C.6) | 16.5.0 | +| 2020-09 | RAN#89 | RP-202101 | 0238 | 1 | C | 7.5 kHz UL shift for LTE/NR spectrum sharing in Band 38/n38 | 16.5.0 | +| 2020-09 | RAN#89 | RP-202113 | 0239 | 1 | B | CR to TS 38.104: Introduction of NR-U into BS core specification | 16.5.0 | +| 2020-12 | RAN#90 | RP-202422 | 0242 | 1 | F | CR for 38.104: HST PUSCH demodulation requirements | 16.6.0 | +| 2020-12 | RAN#90 | RP-202416 | 0243 | 1 | B | CR for 38.104: Ultra high reliability BS demodulation requirements | 16.6.0 | +| 2020-12 | RAN#90 | RP-202416 | 0244 | 1 | B | CR for 38.104: Low latency BS demodulation requirements | 16.6.0 | +| 2020-12 | RAN#90 | RP-202415 | 0245 | 2 | B | CR to TS 38.104 BS demodulation requirements for 2-step RACH | 16.6.0 | +| 2020-12 | RAN#90 | RP-202414 | 0247 | 1 | F | CR to TS 38.104 with NR-U remaining open issues updates | 16.6.0 | +| 2020-12 | RAN#90 | RP-202415 | 0248 | 1 | B | CR on BS demodulation requirements for 2-step RACH for FR2 | 16.6.0 | +| 2020-12 | RAN#90 | RP-202416 | 0249 | 1 | B | CR to TS 38.104: Addition of BS performance requirements for URLLC PUSCH repetition Type A | 16.6.0 | +| 2020-12 | RAN#90 | RP-202422 | 0250 | 1 | B | CR for 38.104: Introduction of performance requirements for NR HST PRACH under fading channel | 16.6.0 | +| 2020-12 | RAN#90 | RP-202423 | 0257 | 1 | F | Adding FRC table description in Annex in TS38.104 v16.5.0 | 16.6.0 | +| 2020-12 | RAN#90 | RP-202488 | 0261 | | A | CR to 38.104 on Category B OTA spurious emissions for and n257 | 16.6.0 | +| 2020-12 | RAN#90 | RP-202451 | 0240 | | B | Introduction of 1880-1920MHz SUL band into Rel-17 TS 38.104 | 17.0.0 | +| 2020-12 | RAN#90 | RP-202452 | 0241 | | B | Introduction of 2300-2400MHz SUL band into Rel-17 TS 38.104 | 17.0.0 | +| 2020-12 | RAN#90 | RP-202448 | 0253 | | B | CR to TS 38.104: introduction of NR band n13 | 17.0.0 | +| 2020-12 | RAN#90 | RP-202453 | 0258 | 1 | B | Big CR to 38.104 - Additional Channel BW | 17.0.0 | +| 2020-12 | RAN#90 | RP-202456 | 0214 | 3 | B | LTE/NR spectrum sharing in Band 40/n40 | 17.0.0 | +| 2021-03 | RAN#91e | RP-210096 | 0262 | 2 | B | CR for TS 38.104 Introduction of SUL for UL of NR band n24 | 17.1.0 | +| 2021-03 | RAN#91e | RP-210078 | 0264 | | A | CR for 38.104: HST PUSCH demodulation requirements | 17.1.0 | +| 2021-03 | RAN#91e | RP-210068 | 0266 | | A | CR for 38.104: Low latency FR1 BS demodulation requirements | 17.1.0 | +| 2021-03 | RAN#91e | RP-210068 | 0268 | | A | CR for 38.104: Ultra high reliability BS demodulation requirements | 17.1.0 | +| 2021-03 | RAN#91e | RP-210068 | 0270 | | A | CR on PUSCH repetition type A and PUSCH mapping type B radiated performance requirement for TS 38.104 | 17.1.0 | +| 2021-03 | RAN#91e | RP-210117 | 0273 | | A | CR to TS 38.104: Additions of regional requirements for n41 and n90 in Japan, Rel-17 | 17.1.0 | +| 2021-03 | RAN#91e | RP-210073 | 0275 | | A | CR on correction 2-step RACH performance requirements for FR2 in 38.104 (Rel-17) | 17.1.0 | +| 2021-03 | RAN#91e | RP-210078 | 0277 | | A | CR for 38.104: Cleanup for performance requirements of NR HST PRACH under | 17.1.0 | +| 2021-03 | RAN#91e | RP-210068 | 0279 | | A | CR to TS 38.104: Correction of BS performance requirements for URLLC PUSCH repetition Type A | 17.1.0 | +| 2021-03 | RAN#91e | RP-210084 | 0282 | | A | CR to TS 38.104: system parameters maintenance for NR-U | 17.1.0 | +| 2021-03 | RAN#91e | RP-210084 | 0284 | | A | CR to TS 38.104: corrections of NR-U BS Tx requirements | 17.1.0 | +| 2021-03 | RAN#91e | RP-210084 | 0286 | | A | CR to TS 38.104: corrections of NR-U BS Rx requirements | 17.1.0 | +| 2021-03 | RAN#91e | RP-210117 | 0289 | | A | CR to TS 38.104: EESS protection requirement correction | 17.1.0 | +| 2021-03 | RAN#91e | RP-210189 | 0291 | | B | Big CR to 38.104 - Additional Channel BW | 17.1.0 | +| 2021-03 | RAN#91e | RP-210117 | 0294 | | A | CR to TS38.104: Correction on the Aggregated Channel Bandwidth | 17.1.0 | +| 2021-03 | RAN#91e | RP-210097 | 0295 | | B | CR to 38.104: Introduction of n24 | 17.1.0 | +| 2021-03 | RAN#91e | RP-210084 | 0297 | | A | CR to TS 38.104 corrections to NR-U BS RF Tx requirements | 17.1.0 | + +| | | | | | | | | +|---------|----------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2021-03 | RAN#91e | RP-210084 | 0299 | | A | CR to TS 38.104 corrections to NR-U BS RF Rx requirements | 17.1.0 | +| 2021-06 | RAN#92 | RP-211117 | 0305 | | A | Correction of the channel raster of n259 for TS 38.104 | 17.2.0 | +| 2021-06 | RAN#92 | RP-211095 | 0307 | | A | CR to TS 38.104: Corrections on frequency offset symbols for spectrum emission mask for non-transmitted channels | 17.2.0 | +| 2021-06 | RAN#92 | RP-211079 | 0310 | | F | CR to TS 38.104 on BS channel bandwidth per operating band | 17.2.0 | +| 2021-06 | RAN#92 | RP-211105 | 0314 | | A | CR on correction of PUSCH repetition type A and PUSCH mapping type B radiated performance requirements for TS 38.104 | 17.2.0 | +| 2021-06 | RAN#92 | RP-211121 | 0318 | 1 | B | CR to TS 38.104: Introduction of band n262 | 17.2.0 | +| 2021-06 | RAN#92 | RP-211115 | 0319 | | B | Big CR to TS 38.104: Adding channel BW support in existing NR bands | 17.2.0 | +| 2021-06 | RAN#92 | RP-211116 | 0320 | 1 | B | CR to TS 38.104: Introduction of band n67 | 17.2.0 | +| 2021-06 | RAN#92 | RP-211116 | 0321 | 1 | B | CR to TS 38.104: Introduction of band n85 | 17.2.0 | +| 2021-06 | RAN#92 | RP-211095 | 0323 | | A | CR to 38.104 with correction of NR-U 60 MHz and 80 MHz channels | 17.2.0 | +| 2021-06 | RAN#92 | RP-211094 | 0325 | | A | Big CR for NR-U BS demodulation requirements in TS 38.104 (Rel-17) | 17.2.0 | +| 2021-06 | RAN#92 | RP-211108 | 0329 | | A | CR for 38.104: HST PUSCH demodulation requirements and spec maintenance | 17.2.0 | +| 2021-06 | RAN#92 | RP-211108 | 0331 | | A | CR for 38.104: Low latency and ultra-low BLER FR1 BS demodulation requirements | 17.2.0 | +| 2021-06 | RAN#92 | RP-211090 | 0333 | | A | CR to 38.104: In-band blocking for multi-band Base Stations | 17.2.0 | +| 2021-09 | RAN#93 | RP-211907 | 0343 | | B | Big CR to TS 38.104: Adding channel BW support in existing NR bands | 17.3.0 | +| 2021-09 | RAN#93 | RP-211909 | 0341 | | B | CR for TS 38.104: introduction of channel bandwidths 35MHz and 45MHz
NOTE The CR is not implemented | 17.3.0 | +| 2021-09 | RAN#93 | RP-211910 | 0348 | | B | Introduction of the UL 7.5kHz shift for NR TDD band n34 and n39 in 38.104 R17 | 17.3.0 | +| 2021-09 | RAN#93 | RP-211926 | 0351 | | F | Big CR for TS 38.104 Maintenance Demod part (Rel-17, CAT F) | 17.3.0 | +| 2021-09 | RAN#93 | RP-211926 | 0354 | | A | Big CR for TS 38.104 Maintenance RF part (Rel-17, CAT A) | 17.3.0 | +| 2021-12 | RAN#94 | RP-212835 | 0356 | | B | Big CR to TS 38.104: Adding channel BW support in existing NR bands | 17.4.0 | +| 2021-12 | RAN#94 | RP-212836 | 0357 | | F | CR to TS 38.104 - Fix to band n85 introduction | 17.4.0 | +| 2021-12 | RAN#94 | RP-212825 | 0355 | 2 | B | CR for TS 38.104: 1024QAM | 17.4.0 | +| 2021-12 | RAN#94 | RP-212824 | 0360 | | F | Big CR for TS 38.104 Maintenance RF part (Rel-17, CAT F) | 17.4.0 | +| 2021-12 | RAN#94 | RP-212850 | 0362 | | F | Big CR for TS 38.104 Maintenance Demod part (Rel-17, CAT F) | 17.4.0 | +| 2021-12 | RAN#94 | RP-213147 | 0363 | | B | CR for TS 38.104: introduction of channel bandwidths 35MHz and 45MHz
NOTE The CR is a resubmission of CR R4-2114918 of RP-211909 | 17.4.0 | +| 2022-03 | RAN#95-e | RP-220377 | 0364 | 1 | B | CR for TS 38.104: capturing HAPS requirements | 17.5.0 | +| 2022-03 | RAN#95-e | RP-220347 | 0365 | 1 | B | CR to TS38.104 on introduction of upper 700MHz A block | 17.5.0 | +| 2022-03 | RAN#95-e | RP-220357 | 0369 | 1 | B | CR for 38.104 to introduce n102 | 17.5.0 | +| 2022-03 | RAN#95-e | RP-220361 | 0372 | | B | BigCR for TS38.104: Introduction of conformance testing requirements for FR1 PUSCH 256QAM | 17.5.0 | +| 2022-03 | RAN#95-e | RP-220334 | 0374 | | F | Big CR for TS 38.104 Maintenance RF part (Rel-17, CAT F) | 17.5.0 | +| 2022-03 | RAN#95-e | RP-220334 | 0376 | | A | Big CR for TS 38.104 Maintenance Demod part (Rel-17, CAT A) | 17.5.0 | +| 2022-03 | RAN#95-e | RP-220376 | 0378 | | B | Big CR to 38.104: RMR 1900MHz band n101 introduction | 17.5.0 | +| 2022-06 | RAN#96 | RP-221680 | 0379 | | B | Big CR on FR2 HST BS demodulation requirement for TS 38.104 | 17.6.0 | +| 2022-06 | RAN#96 | RP-221684 | 0380 | 1 | B | CR to TS 38.104 - Tx requirements: RMR 900MHz band introduction | 17.6.0 | +| 2022-06 | RAN#96 | RP-221671 | 0381 | | B | Big CR to TS 38.104: Adding channel BW support in existing NR bands | 17.6.0 | +| 2022-06 | RAN#96 | RP-221684 | 0382 | 1 | B | CR to 38.104 on introduction of n100 (system parameters) | 17.6.0 | +| 2022-06 | RAN#96 | RP-221673 | 0383 | 1 | B | CR to TS38.104 the introduction of 6425-7125MHz | 17.6.0 | +| 2022-06 | RAN#96 | RP-221676 | 0384 | | B | Big CR to 38.104 for Rel-17 NR extension up to 71 GHz introduction | 17.6.0 | +| 2022-06 | RAN#96 | RP-221684 | 0385 | | B | CR to TS 38.104: RMR900 Rx requirements for band n100, Rel-17 | 17.6.0 | +| 2022-06 | RAN#96 | RP-221676 | 0386 | | B | Big CR on extending NR to 71GHz for TS 38.104 | 17.6.0 | +| 2022-06 | RAN#96 | RP-221655 | 0389 | | F | Big CR for TS 38.104 Maintenance RF part (Rel-17, CAT F) | 17.6.0 | +| 2022-06 | RAN#96 | RP-221659 | 0391 | | A | Big CR for TS 38.104 Maintenance Demod part (Rel-17, CAT A) | 17.6.0 | +| 2022-09 | RAN#97 | RP-222038 | 0394 | 1 | F | CR to 38.104 on n100 corrections | 17.7.0 | +| 2022-09 | RAN#97 | RP-222041 | 0395 | | F | Big CR on FR2 HST BS demodulation requirement for TS 38.104 | 17.7.0 | +| 2022-09 | RAN#97 | RP-222050 | 0401 | 1 | B | CR for 38.104: Add 5 MHz channel BW for n41 | 17.7.0 | +| 2022-09 | RAN#97 | RP-222026 | 0404 | | F | Big CR for TS 38.104 Maintenance RF part (Rel-17, CAT F) | 17.7.0 | +| 2022-09 | RAN#97 | RP-222026 | 0407 | | F | Big CR for TS 38.104 Maintenance Demod part (Rel-17, CAT F) | 17.7.0 | +| 2022-09 | RAN#97 | RP-222051 | 0408 | | F | Big CR to 38.104 for Rel-17 NR extension up to 71 GHz maintenance (Rel-17, CAT F) | 17.7.0 | +| 2022-09 | RAN#97 | RP-222051 | 0410 | | B | Big CR of TS38.104 on system parameter updates for FR2-2 | 17.7.0 | +| 2022-12 | RAN#98-e | RP-223307 | 0411 | | F | CR to TS 38.104 on reference to FRCs | 17.8.0 | +| 2022-12 | RAN#98-e | RP-223307 | 0412 | | F | CR to TS 38.104: Correction of guardband for FR2-2 in sub-clause 5.3.3 | 17.8.0 | + +| | | | | | | | | +|---------|----------|-----------|------|---|---|----------------------------------------------------------------------------------------------------|--------| +| 2022-12 | RAN#98-e | RP-223300 | 0413 | | B | Big CR for coverage enhancement performance requirements for TS38.104 | 17.8.0 | +| 2022-12 | RAN#98-e | RP-223308 | 0414 | 1 | B | Corrections for 100MHz CBW inclusion for n46 n96 and n102 | 17.8.0 | +| 2022-12 | RAN#98-e | RP-223309 | 0415 | | F | CR to TS 38.104 on tables for BS channel bandwidths | 17.8.0 | +| 2022-12 | RAN#98-e | RP-223297 | 0419 | | F | CR for TS38.104 correction on normal PUSCH requirements (Rel-17) | 17.8.0 | +| 2022-12 | RAN#98-e | RP-223309 | 0424 | 2 | F | CR to 38.104: Spurious emission requirements, Rel-17 | 17.8.0 | +| 2022-12 | RAN#98-e | RP-223302 | 0426 | | B | Big CR for TS 38.104 Demodulation requirements for Enhanced IIOT and URLLC support (Rel-17, CAT B) | 17.8.0 | +| 2022-12 | RAN#98-e | RP-223298 | 0429 | | F | CR for 38.104: define home class as one kind of LA BS | 17.8.0 | +| 2022-12 | RAN#98-e | RP-223524 | 0432 | 1 | A | CR on R17 TS 38.104 to add channel raster exception for band n28 [n28_BS40MHz_raster] | 17.8.0 | + +| Change history | | | | | | | | +|----------------|----------|-----------|------|-----|-----|-------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-12 | RAN#98-e | RP-223315 | 0428 | | B | CR to 38.104 on introduction of Band 54 | 18.0.0 | +| 2022-12 | RAN#98-e | RP-223319 | 0433 | | B | CR to TS38.104 the introduction of APT600MHz | 18.0.0 | +| 2023-03 | RAN#99 | RP-230513 | 0435 | | A | Correction of coverage enhancement BS demodulation requirement in 38.104 (R18 A) | 18.1.0 | +| 2023-03 | RAN#99 | RP-230514 | 0437 | | A | CR to TS 38.104 on table references for OTA operating band unwanted emission limits | 18.1.0 | +| 2023-03 | RAN#99 | RP-230510 | 0439 | | A | Big CR to 38.104: demodulation requirements introduction for FR2-2 | 18.1.0 | +| 2023-03 | RAN#99 | RP-230515 | 0441 | | A | CR for TS 38.104 Demodulation requirements for Enhanced IIOT and URLLC support (Rel-18, CAT A) | 18.1.0 | +| 2023-03 | RAN#99 | RP-230535 | 0446 | 1 | B | CR to 38.104 on introduction of Band n54 | 18.1.0 | +| 2023-03 | RAN#99 | RP-230506 | 0449 | | A | CR to 38.104: FRC number corrections (Rel-18) | 18.1.0 | +| 2023-03 | RAN#99 | RP-230559 | 0450 | | B | Big CR to TS 38.104: Adding channel BW support in existing NR bands | 18.1.0 | +| 2023-03 | RAN#99 | RP-230513 | 0452 | | A | CR to 38.104: BS Conformance, OBUE correction for 6G licensed band | 18.1.0 | +| 2023-03 | RAN#99 | RP-230514 | 0460 | | A | CR to TS 38.104: NR-ARFCN table reference correction for band n263, Rel-18 | 18.1.0 | +| 2023-03 | RAN#99 | RP-230514 | 0464 | | A | CR to 38.104: Correction on Rx intermodulation requirements for FR2-2 (Rel-18) | 18.1.0 | +| 2023-06 | RAN#100 | RP-231347 | 0466 | | A | Draft CR 38.104: PUSCH requirements for FR2-2 | 18.2.0 | +| 2023-06 | RAN#100 | RP-231347 | 0468 | | A | CR to TS 38.104 on corrections of table references for extending current NR operation to 71GHz | 18.2.0 | +| 2023-06 | RAN#100 | RP-231348 | 0470 | | A | CR to TS 38.104 on corrections and clarifications of operating band unwanted emission limits for band n104 | 18.2.0 | +| 2023-06 | RAN#100 | RP-231348 | 0472 | | A | CR for TR 38.104, 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 | 0477 | | A | CR for TS38.104 FRC tables for FR2-2 PUSCH demodulation_Rel-18 | 18.2.0 | +| 2023-06 | RAN#100 | RP-231350 | 0479 | 1 | A | CR for TS38.104 on FRC table for PUSCH TBoMS_Rel-18 | 18.2.0 | +| 2023-06 | RAN#100 | RP-231352 | 0482 | 1 | A | CR for TS 38.104: Operating band unwanted emissions for Single RAT BS supporting multi-band operation | 18.2.0 | +| 2023-06 | RAN#100 | RP-231339 | 0485 | | A | CR to TS 38.104 - Maintenance related to bands n100 and n101 | 18.2.0 | +| 2023-06 | RAN#100 | RP-231352 | 0488 | | A | CR on 38.104: Updates to FRC of PUSCH requirements(Rel-18) | 18.2.0 | +| 2023-06 | RAN#100 | RP-231342 | 0490 | | A | CR on 38.104: Updates to the test setup for the PF0 requirements with sub-slot repetition(Rel-18) | 18.2.0 | +| 2023-06 | RAN#100 | RP-231362 | 0491 | | B | CR to 38.104 on introduction of Band 106 | 18.2.0 | +| 2023-06 | RAN#100 | RP-231356 | 0496 | | A | CR to 38.104: Correction to ACLR and CACLR requirement | 18.2.0 | +| 2023-06 | RAN#100 | RP-231343 | 0497 | | B | Addition of 30 KHz SCS for Sync Raster for Band n53 | 18.2.0 | +| 2023-12 | RAN#102 | RP-233342 | 0521 | | A | [NR_unlic] CR for 38.104: Removal of applicability rule (Rel-18, Cat A) | 18.3.0 | +| 2023-12 | RAN#102 | RP-233340 | 0524 | | A | [NR_RF_FR1-Core] CR to TS 38.141-1 on correction of transmitter spurious emissions for protection of Band n20 | 18.3.0 | +| 2023-12 | RAN#102 | RP-233366 | 0525 | | B | CR to TS 38.104 on introduction NR bands n31 and n72 | 18.3.0 | +| 2023-12 | RAN#102 | RP-233363 | 0528 | | F | CR to TS 38.104 on clarification of applicable SS raster entries for 3 MHz channel bandwidth | 18.3.0 | +| 2023-12 | RAN#102 | RP-233363 | 0537 | | B | Big CR for 38.104 on 4Tx PUSCH demodulation requirements | 18.3.0 | +| 2023-12 | RAN#102 | RP-233370 | 0538 | | B | Big CR to TS 38.104: Adding channel BW support in existing NR bands | 18.3.0 | +| 2023-12 | RAN#102 | RP-233363 | 0542 | | F | CR to TS 38.104 on support of NB-IoT operation in NR in-band for 3 MHz channel bandwidth | 18.3.0 | +| 2023-12 | RAN#102 | RP-233366 | 0547 | | B | CR to TS 38.104 on Introduction of Band n106 | 18.3.0 | +| 2023-12 | RAN#102 | RP-233371 | 0549 | | F | Adding 20MHz channel raster points for 5925-5945MHz in the full 6GHz band | 18.3.0 | +| 2023-12 | RAN#102 | RP-233364 | 0543 | 1 | B | CR for TS 38.104 on adding RF requirements for ATG BS | 18.3.0 | +| 2023-12 | RAN#102 | RP-233363 | 0526 | 1 | F | [NR_FR1_less than_5MHz_BW-Core] CR for Tx intermodulation core requirements in certain region | 18.3.0 | +| 2023-12 | RAN#102 | RP-233366 | 0544 | 1 | B | CR to TS38.104: Introduction of n109 | 18.3.0 | +| 2023-12 | RAN#102 | RP-233365 | 0536 | 1 | B | CR to TS38.104: Introduction of an enhanced channel raster | 18.3.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38141-2/026465adb7b73fef0f5e56a6541850a6_img.jpg b/marked/Rel-18/38_series/38141-2/026465adb7b73fef0f5e56a6541850a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9733a469902092903e405f1d388c12657819975f --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/026465adb7b73fef0f5e56a6541850a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e40da0b75919fbb31146eab723016d331626dfdaaf9f19a6a6a503e788d611b0 +size 4729 diff --git a/marked/Rel-18/38_series/38141-2/02ae5fd93ac89537e28a7ff747361ecc_img.jpg b/marked/Rel-18/38_series/38141-2/02ae5fd93ac89537e28a7ff747361ecc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..efe54ae9327547c9cd017d50c5e89a3c84ac2370 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/02ae5fd93ac89537e28a7ff747361ecc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68c1c3adb1ccdaf7f582d64f9559c112b125139afe18e4c78fb32435b6cc6cee +size 37439 diff --git a/marked/Rel-18/38_series/38141-2/032a41557f10f862ab4bf7a1b20cbfd7_img.jpg b/marked/Rel-18/38_series/38141-2/032a41557f10f862ab4bf7a1b20cbfd7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42700a2f451efe6cc192b59cedbd71b660ca3acc --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/032a41557f10f862ab4bf7a1b20cbfd7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8559e9058730a42469abdd1c744af196efe55516366b4e1c5bc8cf92a1ed5aef +size 48125 diff --git a/marked/Rel-18/38_series/38141-2/061137657bf1fb2669843fe20861b2ec_img.jpg b/marked/Rel-18/38_series/38141-2/061137657bf1fb2669843fe20861b2ec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9676059e2154b6d3c31ed9a15dd45d020cbdb095 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/061137657bf1fb2669843fe20861b2ec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce0f4cf650af52baab6f9bea727388029ebb09f0a487b4f20f6817069e9690c6 +size 40109 diff --git a/marked/Rel-18/38_series/38141-2/07203f762dabc167b043a1c4bdc1493c_img.jpg b/marked/Rel-18/38_series/38141-2/07203f762dabc167b043a1c4bdc1493c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56d5e33d85be20e377ad4a7668dfca2664287e46 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/07203f762dabc167b043a1c4bdc1493c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:55b1cce7475ddf362f6526f0b3f5103938c2a34bb3a7710b0d8cc42b25c11383 +size 77806 diff --git a/marked/Rel-18/38_series/38141-2/0dae8b268a9af5498a783511f7993d8c_img.jpg b/marked/Rel-18/38_series/38141-2/0dae8b268a9af5498a783511f7993d8c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eabbd48f17dd1b474ecae8b85d11831cabe748f8 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/0dae8b268a9af5498a783511f7993d8c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:06b2be333cf754a253c0f0698f04f5e364ae144c09001b52e34c2e084f476f1a +size 71589 diff --git a/marked/Rel-18/38_series/38141-2/1459b35539dc68bda6750123e67497be_img.jpg b/marked/Rel-18/38_series/38141-2/1459b35539dc68bda6750123e67497be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..03cddf6d1487285bf2ee1b1241759ea8e55cc17a --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/1459b35539dc68bda6750123e67497be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67c8794bbdc472f9a3facef5fa79bece0704d58ab3f5023e507751920a071805 +size 75943 diff --git a/marked/Rel-18/38_series/38141-2/15c6aea1b21929dc379fb3b7cf100d8c_img.jpg b/marked/Rel-18/38_series/38141-2/15c6aea1b21929dc379fb3b7cf100d8c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b567817c57eb4cdb94b4670b46505c88e1fb38ba --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/15c6aea1b21929dc379fb3b7cf100d8c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba30b984b75f19eaa284f1718f3f03911c40146e940acb10c4adb93b692e97ab +size 73896 diff --git a/marked/Rel-18/38_series/38141-2/1bee321e63e7ca14df7e4a8f2f386ce5_img.jpg b/marked/Rel-18/38_series/38141-2/1bee321e63e7ca14df7e4a8f2f386ce5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cea14671325144090f9835509aa4d765548b89af --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/1bee321e63e7ca14df7e4a8f2f386ce5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e02f2283d807cc9dfc4c714f47d8cb371dd18908ddb286cbabfc155a995a0179 +size 5549 diff --git a/marked/Rel-18/38_series/38141-2/286afeddc8f076c168e16822fa62ba81_img.jpg b/marked/Rel-18/38_series/38141-2/286afeddc8f076c168e16822fa62ba81_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1be3276dfbe01b6b843f01ee9557e2d9e07e661e --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/286afeddc8f076c168e16822fa62ba81_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa1c8b48932db55b0886ae49cd560eaab7c509067aaacc2fe2841d7e2f578d26 +size 25298 diff --git a/marked/Rel-18/38_series/38141-2/2889c0ef51f720bd7c31921af28f4658_img.jpg b/marked/Rel-18/38_series/38141-2/2889c0ef51f720bd7c31921af28f4658_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..96fa71cccb08b546b34364b3dd50dbd2bb01cf90 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/2889c0ef51f720bd7c31921af28f4658_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7d7ddc1942c44754a1a55aa12b929d00e2685d76e9625c6dd7c4859943a0a2d5 +size 38058 diff --git a/marked/Rel-18/38_series/38141-2/2a687a9dad17eb1f0512bb384fa2fdc8_img.jpg b/marked/Rel-18/38_series/38141-2/2a687a9dad17eb1f0512bb384fa2fdc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f9ba2cbb4e8b282dc5db9ebade8d0b0531a4bfb --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/2a687a9dad17eb1f0512bb384fa2fdc8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:881bda8d3dc44e7af395a57dc977a9b8293badc4bd3d70a3c35739b975d2d587 +size 75006 diff --git a/marked/Rel-18/38_series/38141-2/2f05c618a0dd9a0242a6b12ac9aee748_img.jpg b/marked/Rel-18/38_series/38141-2/2f05c618a0dd9a0242a6b12ac9aee748_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..950979972de3ca936c400a8ebc08f7ee7f1bd965 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/2f05c618a0dd9a0242a6b12ac9aee748_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bdf399ef82a45f20e8bf12d3ebe0a831109a9c13c12186a0d49c42919165dd15 +size 4736 diff --git a/marked/Rel-18/38_series/38141-2/3e719a8e608ad16194d4878e2d4fe35b_img.jpg b/marked/Rel-18/38_series/38141-2/3e719a8e608ad16194d4878e2d4fe35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c02acea9581789cf79d68544d60d80cfd800352 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/3e719a8e608ad16194d4878e2d4fe35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:948db0f521643c7264761ed6ed327c4caa8d9d7f9137e65ca84bef379bf1dcee +size 5197 diff --git a/marked/Rel-18/38_series/38141-2/4347f3937d22aee5e65e238303e4e4ee_img.jpg b/marked/Rel-18/38_series/38141-2/4347f3937d22aee5e65e238303e4e4ee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2efc6003d49387cb436d2b865e7acff8f27b62b0 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/4347f3937d22aee5e65e238303e4e4ee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58bc4ca32f4c97be8805da686e61a97165969ad768562170c6eb9e63d10e114f +size 34745 diff --git a/marked/Rel-18/38_series/38141-2/4599d7b27f6bd8041758d322232455d0_img.jpg b/marked/Rel-18/38_series/38141-2/4599d7b27f6bd8041758d322232455d0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d27393c76b74da1255c113d70873c3c58666ae87 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/4599d7b27f6bd8041758d322232455d0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d262d8db3845128b69b0b67eb349fe3ec5ebcc6d59ef91b6206acd610d41a09 +size 4831 diff --git a/marked/Rel-18/38_series/38141-2/4e4a4519e08d677bc4a0dab3dc816f05_img.jpg b/marked/Rel-18/38_series/38141-2/4e4a4519e08d677bc4a0dab3dc816f05_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f40205c5e3520bcf61bc0bb01ced9562b6978c4d --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/4e4a4519e08d677bc4a0dab3dc816f05_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bff82eb8340891bf20062c4eb3288908acce7e9f375d657df1b878edbe27a17e +size 29724 diff --git a/marked/Rel-18/38_series/38141-2/4ea8d6ad6a6469a3a90ebf2d424f7d07_img.jpg b/marked/Rel-18/38_series/38141-2/4ea8d6ad6a6469a3a90ebf2d424f7d07_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b961693ed4fea8ddd783fd48a14e5f3efde2eea --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/4ea8d6ad6a6469a3a90ebf2d424f7d07_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7edf02e371bde1ff5a079ea35d280f0dfb70888dccabf0e4d15b682ded31a1da +size 41891 diff --git a/marked/Rel-18/38_series/38141-2/4ff00a489baaa34a0c01070de1d613db_img.jpg b/marked/Rel-18/38_series/38141-2/4ff00a489baaa34a0c01070de1d613db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f5a9121f5712120e91afa43772d35023ca53605e --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/4ff00a489baaa34a0c01070de1d613db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1b28c7445e21fd463be32eee3b68e151e419608190751d402a83b14009f9b38c +size 46443 diff --git a/marked/Rel-18/38_series/38141-2/5387e60d72dd1cdc4eacd4a37499e9db_img.jpg b/marked/Rel-18/38_series/38141-2/5387e60d72dd1cdc4eacd4a37499e9db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c5db6af7fbfe0c1891ac2db60ed7cacf1ed957b0 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/5387e60d72dd1cdc4eacd4a37499e9db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7885d14bea576018f1fa20099a50d0adc3a9a69db478ce687ec080bcdff323fc +size 81720 diff --git a/marked/Rel-18/38_series/38141-2/53c60f255aa58c330efd23c77dfdc762_img.jpg b/marked/Rel-18/38_series/38141-2/53c60f255aa58c330efd23c77dfdc762_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..010b6f3214c4388ef86fd42c45218335521bd756 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/53c60f255aa58c330efd23c77dfdc762_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c563555b6160a3f03b95b0596f846dccb3c211fc49a1a285fd98ef8110838ed1 +size 18427 diff --git a/marked/Rel-18/38_series/38141-2/54f3455c3fc6038d4a5baa771a3b6e0e_img.jpg b/marked/Rel-18/38_series/38141-2/54f3455c3fc6038d4a5baa771a3b6e0e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b6c449708e47596f8b5c778b2f1067e1e90e9f5 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/54f3455c3fc6038d4a5baa771a3b6e0e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b597c104dc18442cd8d98b016b6e14394b035d085602cd9b1617a8be92b00cd3 +size 39283 diff --git a/marked/Rel-18/38_series/38141-2/55184b561250bd2191d0f64fd4948673_img.jpg b/marked/Rel-18/38_series/38141-2/55184b561250bd2191d0f64fd4948673_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dac854d88158e0c911038af9c0bc12ecb4ee85c4 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/55184b561250bd2191d0f64fd4948673_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:171a289f803905bb61524c91fa46259bbcb583010a34ad63d64f3cfe207fb9f0 +size 38877 diff --git a/marked/Rel-18/38_series/38141-2/56d829bcd0079ac2e963ee6df7bf540e_img.jpg b/marked/Rel-18/38_series/38141-2/56d829bcd0079ac2e963ee6df7bf540e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b5bfcab288c93182df1f0ce0d1062fc1318bab34 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/56d829bcd0079ac2e963ee6df7bf540e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b5405e5bc856edfc2a34a2e1ae73e2d37e10886624219a049417a8209358863 +size 42912 diff --git a/marked/Rel-18/38_series/38141-2/5dcbbe47fca438acf7d505a856fd40a7_img.jpg b/marked/Rel-18/38_series/38141-2/5dcbbe47fca438acf7d505a856fd40a7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8bb38d739546705d02d799e214ba1f5e94e3acd --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/5dcbbe47fca438acf7d505a856fd40a7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82f1f39b0af88574b3d70e91c2e25e1b1d5a946844ec64837ba967a1c633a369 +size 68430 diff --git a/marked/Rel-18/38_series/38141-2/5e9af8986a5845504f251d3079da8078_img.jpg b/marked/Rel-18/38_series/38141-2/5e9af8986a5845504f251d3079da8078_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..49dc143121f5eac430b13c3c738095952f06b94d --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/5e9af8986a5845504f251d3079da8078_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7bc8cd7a026173fe490b0ef38ae6638d3d62e4eaf01494252dd3be16f3cd9851 +size 58660 diff --git a/marked/Rel-18/38_series/38141-2/5ef9a81e819cc94dc0c6517896f31c6f_img.jpg b/marked/Rel-18/38_series/38141-2/5ef9a81e819cc94dc0c6517896f31c6f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9543392731da15b885bb4f2497777ab6678f925a --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/5ef9a81e819cc94dc0c6517896f31c6f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c019f9c9fc3a574ca2270438ceaa4974f47976e1fc535064463f8dd3fda43c27 +size 66377 diff --git a/marked/Rel-18/38_series/38141-2/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38141-2/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa013172c80164e90a83c65ece72e33d3166cd46 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24ceaf33a3a5a53608ed941b74a424f43981eb282981407a59f60bdddf5aaef2 +size 7462 diff --git a/marked/Rel-18/38_series/38141-2/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38141-2/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cbf24fe647685f58c364376b4b859e2db4b2cd17 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb095ae7f68f6e70bedfa3a43872e361c8a70f0f3abcde0a1ebddb7520e95eb1 +size 5529 diff --git a/marked/Rel-18/38_series/38141-2/700d7b9748b3f21b6381998882dd61ea_img.jpg b/marked/Rel-18/38_series/38141-2/700d7b9748b3f21b6381998882dd61ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d2ed9bc420d0d712f83db22c1e8ae55c764804fe --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/700d7b9748b3f21b6381998882dd61ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4f31be38ab3ebc8a87dd9a513b5e31e92763fa4a4257b029d15201c9f21763b +size 22748 diff --git a/marked/Rel-18/38_series/38141-2/701d39c5ca98f4045e3e0db67c9a267a_img.jpg b/marked/Rel-18/38_series/38141-2/701d39c5ca98f4045e3e0db67c9a267a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d8f1670de00e6aeaa566a202a948c8688d7beafc --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/701d39c5ca98f4045e3e0db67c9a267a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5e31280a6c381fd428377d442458b410192bc22b9107d13980fddfa06e8a428 +size 69260 diff --git a/marked/Rel-18/38_series/38141-2/76fd6b70a4c042241b32568c536a4704_img.jpg b/marked/Rel-18/38_series/38141-2/76fd6b70a4c042241b32568c536a4704_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..969ff5c70c737f5a72d79c148834a68451c77cc8 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/76fd6b70a4c042241b32568c536a4704_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:145d45861a0b71cc5a000267f3f5a62d40f7d0b3fd8a62c685b1ec0c7d7c50a9 +size 42694 diff --git a/marked/Rel-18/38_series/38141-2/794f5ecb17da881f300b5dbcae23d88f_img.jpg b/marked/Rel-18/38_series/38141-2/794f5ecb17da881f300b5dbcae23d88f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c58f67b40e02b17fdcc69751e88f0848aee6d520 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/794f5ecb17da881f300b5dbcae23d88f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2fba55149d868b5e06332f98ebc30e40531b217dc6585a9ed704cc10e6fe5ed0 +size 67955 diff --git a/marked/Rel-18/38_series/38141-2/7bcbec1a44e47d72995323f51516b314_img.jpg b/marked/Rel-18/38_series/38141-2/7bcbec1a44e47d72995323f51516b314_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ba1a86816f9b10d851f106e04ec352a27b9f8c8 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/7bcbec1a44e47d72995323f51516b314_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d6457daf923cab566924330dc18d22eee5084f2365f93aa53fef48c4968557c +size 14798 diff --git a/marked/Rel-18/38_series/38141-2/8269648391c59363ea61243864a2adf7_img.jpg b/marked/Rel-18/38_series/38141-2/8269648391c59363ea61243864a2adf7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a4524174e166921c5eb013eadb8a100195ae6a0 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/8269648391c59363ea61243864a2adf7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0611bec761d82a2de933ba70debb9cfa02fded175f3280959c546b139cc740b5 +size 41191 diff --git a/marked/Rel-18/38_series/38141-2/8c5fc2c0636cfe6e574227dbf490fd4b_img.jpg b/marked/Rel-18/38_series/38141-2/8c5fc2c0636cfe6e574227dbf490fd4b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b343eb3a29a089384a7fdc79a1cf40c443027a9 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/8c5fc2c0636cfe6e574227dbf490fd4b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:444fdeb3fadd425149db616082ca80334e9095122b1b58de96597cd867954453 +size 20851 diff --git a/marked/Rel-18/38_series/38141-2/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg b/marked/Rel-18/38_series/38141-2/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5d90c185557c2bde1f0d3341145e9a9f3deb0e97 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7007bd24811b646c1f6e39dd241a1366b44f98e65931838f484c96653d528a1b +size 46547 diff --git a/marked/Rel-18/38_series/38141-2/97fd0793c8041e1c0e6413aa3d9364c4_img.jpg b/marked/Rel-18/38_series/38141-2/97fd0793c8041e1c0e6413aa3d9364c4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..03d068571c03ba050068aaa2b9e3b77f48cfeea0 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/97fd0793c8041e1c0e6413aa3d9364c4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b181544a36c76cdab538cd8b4cdfb3221559dc5cdc5c4cfadffd9b471e15dbf6 +size 46701 diff --git a/marked/Rel-18/38_series/38141-2/9a14684f8ae1345c6efea6f5994c730c_img.jpg b/marked/Rel-18/38_series/38141-2/9a14684f8ae1345c6efea6f5994c730c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c0868171e8ea73b8a9135745b441a62fce92f877 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/9a14684f8ae1345c6efea6f5994c730c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:30ab30d9809ad6147ccf0b126223f1ef52967b4ab8f734972ddeec1096100c8c +size 59441 diff --git a/marked/Rel-18/38_series/38141-2/9c575767fe4409cdd2898df6f70139f5_img.jpg b/marked/Rel-18/38_series/38141-2/9c575767fe4409cdd2898df6f70139f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c4d5be7eca4f073ee52eac624906e214f22412f3 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/9c575767fe4409cdd2898df6f70139f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:574b71690d14ab4b36ed7672850a1d4234a57627e7987bf7d98b47d21ca09a91 +size 53645 diff --git a/marked/Rel-18/38_series/38141-2/9e33e281350dad2ba558efa5407770de_img.jpg b/marked/Rel-18/38_series/38141-2/9e33e281350dad2ba558efa5407770de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..30eedef106354990f40ff676c2f2ec321ab2a0e7 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/9e33e281350dad2ba558efa5407770de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:78e9f895e9c00478233004ee85fffb75b30a67cc4c2782e0dc17cb18f463190c +size 81989 diff --git a/marked/Rel-18/38_series/38141-2/a50bb96f2021602f9ef99fc8e5bb9915_img.jpg b/marked/Rel-18/38_series/38141-2/a50bb96f2021602f9ef99fc8e5bb9915_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c51360e360ae3562491ee7805fd2b8fce7bda3d5 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/a50bb96f2021602f9ef99fc8e5bb9915_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:210d3c5aff769500ac52ac0b42dec0cbfa5d14c63a0c885b1d4a1db05e9f6bd2 +size 5187 diff --git a/marked/Rel-18/38_series/38141-2/a7c4c4e8cc0302c649dc4e9476d97372_img.jpg b/marked/Rel-18/38_series/38141-2/a7c4c4e8cc0302c649dc4e9476d97372_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..daead9389c95d5ce4dbd8eda9021ebe6b04bf077 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/a7c4c4e8cc0302c649dc4e9476d97372_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5f967d39cbc1de20c264649685d4212bc521114a36091ad79f85bbeb7687796a +size 4908 diff --git a/marked/Rel-18/38_series/38141-2/ab5f5ba41a1f485b0d132c14fdf23bc0_img.jpg b/marked/Rel-18/38_series/38141-2/ab5f5ba41a1f485b0d132c14fdf23bc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3759e82e4a5abd319b3d316710c120d444b394d9 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/ab5f5ba41a1f485b0d132c14fdf23bc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:870cf8b402595ae475a5e6443d2830417ead94c42bfc4d511fc1b3acec5547a5 +size 39088 diff --git a/marked/Rel-18/38_series/38141-2/b5f2a411da1c592432185a9a34e95c38_img.jpg b/marked/Rel-18/38_series/38141-2/b5f2a411da1c592432185a9a34e95c38_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3955e43f7bfce2d44ca15948edbfd8943e0c64ed --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/b5f2a411da1c592432185a9a34e95c38_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:660dfc55987f0ec75a67e0f3013325070411a4127965798e92e761262d70f08c +size 138861 diff --git a/marked/Rel-18/38_series/38141-2/b6c180eec8419c3f2a80bb59d1b71faf_img.jpg b/marked/Rel-18/38_series/38141-2/b6c180eec8419c3f2a80bb59d1b71faf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f49be26095782a14b16fc88f79576ed488da793 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/b6c180eec8419c3f2a80bb59d1b71faf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a03549ebb4ae32c282c50b83915f2c748abfa080541790f71cebd54f1a73fe15 +size 36750 diff --git a/marked/Rel-18/38_series/38141-2/b81e457e59b65ecf9be46c05a8e4b7c9_img.jpg b/marked/Rel-18/38_series/38141-2/b81e457e59b65ecf9be46c05a8e4b7c9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..30266a4b20ce1a598fd4f439fa2955f304bd2768 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/b81e457e59b65ecf9be46c05a8e4b7c9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:28f514655a4dc61ab02ff6c1c1e05c921863edb39aff6a1f2e7477e7f5bebe9e +size 68502 diff --git a/marked/Rel-18/38_series/38141-2/bd0102d6e3d91c70d57762f2c33904bf_img.jpg b/marked/Rel-18/38_series/38141-2/bd0102d6e3d91c70d57762f2c33904bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..54680c574b46ce444f0d3694ca5ba89e07efb8c2 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/bd0102d6e3d91c70d57762f2c33904bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:309dcd18703f98677e85c7fa42e188a776552dca782b75bb00631cd09f5deba9 +size 4852 diff --git a/marked/Rel-18/38_series/38141-2/c31fc33e1a6e262737615e382de3624e_img.jpg b/marked/Rel-18/38_series/38141-2/c31fc33e1a6e262737615e382de3624e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b9c78c9f1c8098a712bb58fce5d458b4d723419 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/c31fc33e1a6e262737615e382de3624e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:01e3e33807364c4f8f16bb7d97d7e352b9965e44842b1bb80a67c6bc7adaa2fa +size 27864 diff --git a/marked/Rel-18/38_series/38141-2/cfd4ab4dd7c8508bc31765b288283a14_img.jpg b/marked/Rel-18/38_series/38141-2/cfd4ab4dd7c8508bc31765b288283a14_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f75e3a24c3dae031a79a40821d44b73e552ea9cb --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/cfd4ab4dd7c8508bc31765b288283a14_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:76a38f69db349e44d6ce87c95cc9b036c8201ac60a70559d26a06b535adf8520 +size 52362 diff --git a/marked/Rel-18/38_series/38141-2/d461c6341beba90844ef785469cd757f_img.jpg b/marked/Rel-18/38_series/38141-2/d461c6341beba90844ef785469cd757f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a68723b448efab7beb0bb30d9620c606c9d35867 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/d461c6341beba90844ef785469cd757f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1c8f0850059030c564435bd9c6eeb2c4d1fdab6a1eb53e6d1d01a8ae534c4902 +size 61352 diff --git a/marked/Rel-18/38_series/38141-2/d74ed29ed2b7aca01173043c14d46cab_img.jpg b/marked/Rel-18/38_series/38141-2/d74ed29ed2b7aca01173043c14d46cab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..35dddc92aeaac624fcb20794ec32440d3f721230 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/d74ed29ed2b7aca01173043c14d46cab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b1fe539fe3a352f2936ea4a9f225036b88168087491147a05d83c86107f51015 +size 33281 diff --git a/marked/Rel-18/38_series/38141-2/d88324d357512f1306e8cdac68f80fd3_img.jpg b/marked/Rel-18/38_series/38141-2/d88324d357512f1306e8cdac68f80fd3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f0cd6ead802ad06e8de7b5fa2e157d547b35380 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/d88324d357512f1306e8cdac68f80fd3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:27d09c302a31336266d70941351aed7a1282fad53a8ac669c1222a750f5ca28b +size 86491 diff --git a/marked/Rel-18/38_series/38141-2/dd3bdc670c443b40676e413a4367b9da_img.jpg b/marked/Rel-18/38_series/38141-2/dd3bdc670c443b40676e413a4367b9da_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20b7e70645dc7d3dbb5d563ad34fffae574b32c2 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/dd3bdc670c443b40676e413a4367b9da_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:156ca08168da9491ec60463b12275a677806712df0563fc5f4dc6ba4f7718ecc +size 72439 diff --git a/marked/Rel-18/38_series/38141-2/e05122559f56af5699789b7118d8fe87_img.jpg b/marked/Rel-18/38_series/38141-2/e05122559f56af5699789b7118d8fe87_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1916f8dd678180f1d68f5d73eb11ee2060f4453a --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/e05122559f56af5699789b7118d8fe87_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e360b88030b62aff7f89a17a53f348b393c22e5c0f6d22350faeacd8272d960c +size 62288 diff --git a/marked/Rel-18/38_series/38141-2/e4f6dfe8642c4656d6cd3626216c9d55_img.jpg b/marked/Rel-18/38_series/38141-2/e4f6dfe8642c4656d6cd3626216c9d55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0293bc717ee413aa3143aba20599b1f6a1bf5a68 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/e4f6dfe8642c4656d6cd3626216c9d55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:673e29ff50609e232740a9aa01fc69e187b5c5585659e9378aa62b8e496e6f96 +size 43392 diff --git a/marked/Rel-18/38_series/38141-2/e76fde14f7de3365b3c30570652890e6_img.jpg b/marked/Rel-18/38_series/38141-2/e76fde14f7de3365b3c30570652890e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa249bfb1547c9b2a26afb2bac87f10a366a1ffb --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/e76fde14f7de3365b3c30570652890e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04f630117d358ebafc45ff99d3173178016f375c9803c67ef0e475edab70a2da +size 41796 diff --git a/marked/Rel-18/38_series/38141-2/e8ceb2500b8a99cd4d677554b974a3f4_img.jpg b/marked/Rel-18/38_series/38141-2/e8ceb2500b8a99cd4d677554b974a3f4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e44fc43980f810b0e45ebf4d56853c9b84a7ad09 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/e8ceb2500b8a99cd4d677554b974a3f4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68efd116da82856513d21841b34c5a3d80806c1803dd81ca0ddc863a8c5b9c35 +size 4655 diff --git a/marked/Rel-18/38_series/38141-2/e97277b95d25bb9cfe8581800948ddeb_img.jpg b/marked/Rel-18/38_series/38141-2/e97277b95d25bb9cfe8581800948ddeb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d845a30991ced048a2a34602cf34e607d21aa979 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/e97277b95d25bb9cfe8581800948ddeb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:92d74c1e682a9a5c220592325418995d0310646f9f461279650cb0747a164df5 +size 9495 diff --git a/marked/Rel-18/38_series/38141-2/ec9101c0a733cc6b8240c5ade9a04754_img.jpg b/marked/Rel-18/38_series/38141-2/ec9101c0a733cc6b8240c5ade9a04754_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0624d54042cad642460b52f9a7f14ac26916b42 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/ec9101c0a733cc6b8240c5ade9a04754_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:074c9ce264b2c71618262eb3b3e6e1138085d97e035de36738db2ad20c3ed056 +size 19288 diff --git a/marked/Rel-18/38_series/38141-2/ee70b385addc0cd03ee26d51d63c97cf_img.jpg b/marked/Rel-18/38_series/38141-2/ee70b385addc0cd03ee26d51d63c97cf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd13a3e50d381bf35eb27b265428b6da8db9f4d8 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/ee70b385addc0cd03ee26d51d63c97cf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7fe0c6f925b2cc6334031ccbce54dd0f72972aac26984cbc318cb36af6ffba5 +size 26096 diff --git a/marked/Rel-18/38_series/38141-2/ef8af6989f67e7a666533db9b903dfcf_img.jpg b/marked/Rel-18/38_series/38141-2/ef8af6989f67e7a666533db9b903dfcf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aad73240c73b6903f7e7292e83d9f024a49822fb --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/ef8af6989f67e7a666533db9b903dfcf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af06b3af33626dfe3abaf273c6178bd99562bcf829f63b5ffd6834cf8b18b068 +size 82750 diff --git a/marked/Rel-18/38_series/38141-2/f1091147d93cee4dfa88498610e395a7_img.jpg b/marked/Rel-18/38_series/38141-2/f1091147d93cee4dfa88498610e395a7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ab1b0e6f8dd86215852db5483f5890dcc00b27d --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/f1091147d93cee4dfa88498610e395a7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a5fb0721449403c155b70bd47ab3f7dad861cf82bb5e0c5015a85caac4dfb2d +size 36708 diff --git a/marked/Rel-18/38_series/38141-2/f146bedbc65611bb7e7515e9e6965755_img.jpg b/marked/Rel-18/38_series/38141-2/f146bedbc65611bb7e7515e9e6965755_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d53255eb3f630dac7a839f7e82f2c388c342a46d --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/f146bedbc65611bb7e7515e9e6965755_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:781eb3f7a2ad19cb91d2df675d0dfd56fb7fc22d061f042f1c248fdee407ec51 +size 14437 diff --git a/marked/Rel-18/38_series/38141-2/f8d7f8ccdb986d4a88d3c5f0a29f838a_img.jpg b/marked/Rel-18/38_series/38141-2/f8d7f8ccdb986d4a88d3c5f0a29f838a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0236703ae7e04d22f350ccabc08e32fa1372450e --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/f8d7f8ccdb986d4a88d3c5f0a29f838a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9546e6557cfc47508fa2327dea705be355ccecbb98c070216cb2ac5a6169c536 +size 28554 diff --git a/marked/Rel-18/38_series/38141-2/raw.md b/marked/Rel-18/38_series/38141-2/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e2358650cb532439628e0137a903c36b5c572b36 --- /dev/null +++ b/marked/Rel-18/38_series/38141-2/raw.md @@ -0,0 +1,15762 @@ + + +# 3GPP TS 38.141-2 V18.4.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Base Station (BS) conformance testing Part 2: Radiated conformance testing (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' in black with a green wave-like graphic above the 'G', and the word 'ADVANCED' in smaller black letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. The 'G' has a red signal-like 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. + +## **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..... | 17 | +| 1 Scope..... | 19 | +| 2 References..... | 19 | +| 3 Definitions, symbols and abbreviations..... | 21 | +| 3.1 Definitions..... | 21 | +| 3.2 Symbols..... | 24 | +| 3.3 Abbreviations..... | 26 | +| 4 General radiated test conditions and declarations..... | 28 | +| 4.1 Measurement uncertainties and test requirements..... | 28 | +| 4.1.1 General..... | 28 | +| 4.1.2 Acceptable uncertainty of OTA Test System..... | 30 | +| 4.1.2.1 General..... | 30 | +| 4.1.2.2 Measurement of transmitter..... | 31 | +| 4.1.2.3 Measurement of receiver..... | 33 | +| 4.1.2.4 Measurement of performance requirement..... | 37 | +| 4.1.3 Interpretation of measurement results..... | 38 | +| 4.2 Radiated requirement reference points..... | 38 | +| 4.3 Base station classes..... | 40 | +| 4.4 Regional requirements..... | 40 | +| 4.5 BS configurations..... | 41 | +| 4.5.1 Transmit configurations..... | 41 | +| 4.5.2 Receive configurations..... | 42 | +| 4.5.3 Power supply options..... | 43 | +| 4.5.4 BS with integrated Iuant BS modem..... | 44 | +| 4.6 Manufacturer's declarations..... | 44 | +| 4.7 Test configurations..... | 54 | +| 4.7.1 General..... | 54 | +| 4.7.2 Test signal configurations..... | 55 | +| 4.7.2.1 Test signal used to build Test Configurations..... | 55 | +| 4.7.2.2 NRTC1: Contiguous spectrum operation..... | 55 | +| 4.7.2.2.1 NRTC1 generation..... | 55 | +| 4.7.2.2.2 NRTC1 power allocation..... | 55 | +| 4.7.2.3 NRTC2: Contiguous CA occupied bandwidth..... | 56 | +| 4.7.2.3.1 NRTC2 generation..... | 56 | +| 4.7.2.3.2 NRTC2 power allocation..... | 56 | +| 4.7.2.4 NRTC3: Non-contiguous spectrum operation..... | 56 | +| 4.7.2.4.1 NRTC3 generation..... | 57 | +| 4.7.2.4.2 NRTC3 power allocation..... | 57 | +| 4.7.2.5 NRTC4: Multi-band test configuration for full carrier allocation..... | 57 | +| 4.7.2.5.1 NRTC4 generation..... | 57 | +| 4.7.2.5.2 NRTC4 power allocation..... | 58 | +| 4.7.2.6 NRTC5: Multi-band test configuration with high PSD per carrier..... | 58 | +| 4.7.2.6.1 NRTC5 generation..... | 58 | +| 4.7.2.6.2 NRTC5 power allocation..... | 58 | +| 4.8 Applicability of requirements..... | 59 | +| 4.8.1 Requirement set applicability..... | 59 | +| 4.8.2 Applicability of test configurations for single-band RIB ..... | 59 | +| 4.8.3 Applicability of test configurations for multi-band RIB ..... | 60 | +| 4.8.4 Additional conformance..... | 61 | +| 4.9 RF channels and test models..... | 62 | +| 4.9.1 RF channels..... | 62 | +| 4.9.2 Test models..... | 63 | +| 4.9.2.1 General..... | 63 | +| 4.9.2.2 NR FR2 test models..... | 63 | +| 4.9.2.2.1 NR FR2 test model 1.1 (NR-FR2-TM1.1)..... | 64 | + +| | | | +|------------|------------------------------------------------------------------|----| +| 4.9.2.2.2 | NR FR2 test model 2 (NR-FR2-TM2)..... | 65 | +| 4.9.2.2.2a | NR FR2 test model 2a (NR-FR2-TM2a)..... | 65 | +| 4.9.2.2.3 | NR FR2 test model 3.1 (NR-FR2-TM3.1)..... | 66 | +| 4.9.2.2.4 | NR FR2 test model 3.1a (NR-FR2-TM3.1a)..... | 66 | +| 4.9.2.3 | Data content of physical channels and signals for NR-FR2-TM..... | 66 | +| 4.9.2.3.1 | PDCCH..... | 67 | +| 4.9.2.3.2 | PDSCH..... | 67 | +| 4.10 | Requirements for contiguous and non-contiguous spectrum..... | 68 | +| 4.11 | Requirements for BS capable of multi-band operation..... | 68 | +| 4.12 | Co-location requirements..... | 69 | +| 4.12.1 | General..... | 69 | +| 4.12.2 | Co-location test antenna..... | 69 | +| 4.12.2.1 | General..... | 69 | +| 4.12.2.2 | Co-location test antenna characteristics..... | 69 | +| 4.12.2.3 | Co-location test antenna alignment..... | 70 | +| 4.13 | Format and interpretation of tests..... | 71 | +| 4.14 | Reference coordinate system..... | 72 | +| 5 | Operating bands and channel arrangement..... | 74 | +| 6 | Radiated transmitter characteristics..... | 75 | +| 6.1 | General..... | 75 | +| 6.2 | Radiated transmit power..... | 75 | +| 6.2.1 | Definition and applicability..... | 75 | +| 6.2.2 | Minimum requirement..... | 76 | +| 6.2.3 | Test purpose..... | 76 | +| 6.2.4 | Method of test..... | 76 | +| 6.2.4.1 | Initial conditions..... | 76 | +| 6.2.4.2 | Procedure..... | 76 | +| 6.2.5 | Test requirement..... | 77 | +| 6.3 | OTA base station output power..... | 77 | +| 6.3.1 | Definition and applicability..... | 77 | +| 6.3.2 | Minimum requirement..... | 78 | +| 6.3.3 | Test purpose..... | 78 | +| 6.3.4 | Method of test..... | 78 | +| 6.3.4.1 | Initial conditions..... | 78 | +| 6.3.4.2 | Procedure..... | 78 | +| 6.3.5 | Test requirement..... | 79 | +| 6.3.5.1 | BS type 1-O ..... | 79 | +| 6.3.5.2 | BS type 2-O ..... | 79 | +| 6.4 | OTA output power dynamics..... | 79 | +| 6.4.1 | General..... | 79 | +| 6.4.2 | OTA RE power control dynamic range..... | 79 | +| 6.4.2.1 | Definition and applicability..... | 79 | +| 6.4.2.2 | Minimum requirement..... | 80 | +| 6.4.2.3 | Method of test..... | 80 | +| 6.4.3 | OTA total power dynamic range..... | 80 | +| 6.4.3.1 | Definition and applicability..... | 80 | +| 6.4.3.2 | Minimum requirement..... | 80 | +| 6.4.3.3 | Test purpose..... | 80 | +| 6.4.3.4 | Method of test..... | 80 | +| 6.4.3.4.1 | Initial conditions..... | 80 | +| 6.4.3.4.2 | Procedure..... | 80 | +| 6.4.3.5 | Test requirement..... | 81 | +| 6.4.3.5.1 | BS type 1-O ..... | 81 | +| 6.4.3.5.2 | BS type 2-O ..... | 82 | +| 6.5 | OTA transmit ON/OFF power..... | 82 | +| 6.5.1 | OTA transmitter OFF power..... | 82 | +| 6.5.1.1 | Definition and applicability..... | 82 | +| 6.5.1.2 | Minimum requirement..... | 83 | +| 6.5.1.3 | Test purpose..... | 83 | +| 6.5.1.4 | Method of test..... | 83 | + +| | | | +|-----------|------------------------------------------------------|-----| +| 6.5.1.5 | Test requirements..... | 83 | +| 6.5.2 | OTA transmitter transient period..... | 83 | +| 6.5.2.1 | Definition and applicability..... | 83 | +| 6.5.2.2 | Minimum requirement..... | 84 | +| 6.5.2.3 | Test purpose..... | 84 | +| 6.5.2.4 | Method of test..... | 84 | +| 6.5.2.4.1 | Initial conditions..... | 84 | +| 6.5.2.4.2 | Procedure..... | 85 | +| 6.5.2.5 | Test requirements..... | 86 | +| 6.5.2.5.1 | BS type 1-O ..... | 86 | +| 6.5.2.5.2 | BS type 2-O ..... | 86 | +| 6.6 | OTA transmitted signal quality..... | 86 | +| 6.6.1 | General..... | 86 | +| 6.6.2 | OTA frequency error..... | 86 | +| 6.6.2.1 | Definition and applicability..... | 86 | +| 6.6.2.2 | Minimum Requirement..... | 86 | +| 6.6.2.3 | Test purpose..... | 87 | +| 6.6.2.4 | Method of test..... | 87 | +| 6.6.2.4.1 | Initial conditions..... | 87 | +| 6.6.2.5 | Test Requirements..... | 87 | +| 6.6.3 | OTA modulation quality..... | 87 | +| 6.6.3.1 | Definition and applicability..... | 87 | +| 6.6.3.2 | Minimum Requirement..... | 87 | +| 6.6.3.3 | Test purpose..... | 87 | +| 6.6.3.4 | Method of test..... | 87 | +| 6.6.3.4.1 | Initial conditions..... | 87 | +| 6.6.3.4.2 | Procedure..... | 88 | +| 6.6.3.5 | Test requirements..... | 89 | +| 6.6.3.5.1 | BS type 1-O ..... | 89 | +| 6.6.3.5.2 | BS type 2-O ..... | 91 | +| 6.6.4 | OTA time alignment error..... | 93 | +| 6.6.4.1 | Definition and applicability..... | 93 | +| 6.6.4.2 | Minimum requirement..... | 93 | +| 6.6.4.3 | Test purpose..... | 93 | +| 6.6.4.4 | Method of test..... | 93 | +| 6.6.4.4.1 | Initial conditions..... | 93 | +| 6.6.4.4.2 | Procedure..... | 93 | +| 6.6.4.5 | Test Requirement..... | 94 | +| 6.6.4.5.1 | BS type 1-O ..... | 94 | +| 6.6.4.5.2 | BS type 2-O ..... | 94 | +| 6.7 | OTA unwanted emissions..... | 95 | +| 6.7.1 | General..... | 95 | +| 6.7.2 | OTA occupied bandwidth..... | 95 | +| 6.7.2.1 | Definition and applicability..... | 95 | +| 6.7.2.2 | Minimum requirement..... | 96 | +| 6.7.2.3 | Test purpose..... | 96 | +| 6.7.2.4 | Method of test..... | 96 | +| 6.7.2.4.1 | Initial conditions..... | 96 | +| 6.7.2.4.2 | Procedure..... | 96 | +| 6.7.2.5 | Test requirement..... | 98 | +| 6.7.2.5.1 | BS type 1-O ..... | 98 | +| 6.7.2.5.2 | BS type 2-O ..... | 98 | +| 6.7.3 | OTA Adjacent Channel Leakage Power Ratio (ACLR)..... | 98 | +| 6.7.3.1 | Definition and applicability..... | 98 | +| 6.7.3.2 | Minimum requirement..... | 98 | +| 6.7.3.3 | Test purpose..... | 98 | +| 6.7.3.4 | Method of test..... | 98 | +| 6.7.3.4.1 | Initial conditions..... | 98 | +| 6.7.3.4.2 | Procedure..... | 99 | +| 6.7.3.5 | Test requirements..... | 100 | +| 6.7.3.5.1 | BS type 1-O ..... | 100 | + +| | | | +|-----------|-----------------------------------------------------------------------|-----| +| 6.7.3.5.2 | BS type 2-O ..... | 102 | +| 6.7.4 | OTA operating band unwanted emissions..... | 105 | +| 6.7.4.1 | Definition and applicability..... | 105 | +| 6.7.4.2 | Minimum requirement..... | 105 | +| 6.7.4.3 | Test purpose..... | 105 | +| 6.7.4.4 | Method of test..... | 105 | +| 6.7.4.4.1 | Initial conditions..... | 105 | +| 6.7.4.4.2 | Procedure..... | 106 | +| 6.7.4.5 | Test requirements..... | 106 | +| 6.7.4.5.1 | BS type 1-O ..... | 106 | +| 6.7.4.5.2 | BS type 2-O ..... | 120 | +| 6.7.5 | OTA transmitter spurious emissions..... | 123 | +| 6.7.5.1 | General..... | 123 | +| 6.7.5.2 | General OTA transmitter spurious emissions requirements..... | 124 | +| 6.7.5.2.1 | Definition and applicability..... | 124 | +| 6.7.5.2.2 | Minimum requirement..... | 124 | +| 6.7.5.2.3 | Test purpose..... | 124 | +| 6.7.5.2.4 | Method of test..... | 124 | +| 6.7.5.2.5 | Test requirement..... | 125 | +| 6.7.5.3 | Protection of the BS receiver of own or different BS..... | 127 | +| 6.7.5.3.1 | Definition and applicability..... | 127 | +| 6.7.5.3.2 | Minimum requirements..... | 127 | +| 6.7.5.3.3 | Test purpose..... | 128 | +| 6.7.5.3.4 | Method of test..... | 128 | +| 6.7.5.3.5 | Test requirements..... | 129 | +| 6.7.5.4 | Additional spurious emissions requirements..... | 129 | +| 6.7.5.4.1 | Definition and applicability..... | 129 | +| 6.7.5.4.2 | Minimum Requirement..... | 129 | +| 6.7.5.4.3 | Test purpose..... | 129 | +| 6.7.5.4.4 | Method of test..... | 130 | +| 6.7.5.4.5 | Test requirement..... | 131 | +| 6.7.5.5 | Co-location requirements..... | 141 | +| 6.7.5.5.1 | Definition and applicability..... | 141 | +| 6.7.5.5.2 | Minimum requirements..... | 142 | +| 6.7.5.5.3 | Test purpose..... | 142 | +| 6.7.5.5.4 | Method of test..... | 142 | +| 6.7.5.5.5 | Test requirements..... | 143 | +| 6.8 | OTA transmitter intermodulation..... | 148 | +| 6.8.1 | Definition and applicability..... | 148 | +| 6.8.2 | Minimum requirement..... | 148 | +| 6.8.3 | Test purpose..... | 148 | +| 6.8.4 | Method of test..... | 149 | +| 6.8.4.1 | Initial conditions..... | 149 | +| 6.8.4.2 | Procedure..... | 149 | +| 6.8.5 | Test requirements..... | 150 | +| 6.8.5.1 | Requirement for BS type 1-O..... | 150 | +| 6.8.5.2 | Additional requirements (regional)..... | 151 | +| 7.1 | General..... | 152 | +| 7.2 | OTA sensitivity..... | 153 | +| 7.2.1 | Definition and applicability..... | 153 | +| 7.2.2 | Minimum requirement..... | 153 | +| 7.2.3 | Test Purpose..... | 153 | +| 7.2.4 | Method of test..... | 153 | +| 7.2.4.1 | Initial conditions..... | 153 | +| 7.2.4.2 | Procedure..... | 154 | +| 7.2.5 | Test requirements..... | 154 | +| 7.2.5.1 | General..... | 154 | +| 7.2.5.2 | Test requirements for BS type 1-H and BS type 1-O ..... | 154 | +| 7.2.5.3 | Test requirements for BS type 2-O ..... | 155 | +| 7.3 | OTA reference sensitivity level..... | 156 | +| 7.3.1 | Definition and applicability..... | 156 | + +| | | | +|-----------|------------------------------------------------------------|-----| +| 7.3.2 | Minimum requirement..... | 156 | +| 7.3.3 | Test Purpose..... | 156 | +| 7.3.4 | Method of test..... | 156 | +| 7.3.4.1 | Initial conditions..... | 156 | +| 7.3.4.2 | Procedure..... | 156 | +| 7.3.5 | Test requirements..... | 157 | +| 7.3.5.1 | General..... | 157 | +| 7.3.5.2 | Test requirements for BS type 1-O ..... | 157 | +| 7.3.5.3 | Test requirements for BS type 2-O ..... | 158 | +| 7.4 | OTA dynamic range..... | 160 | +| 7.4.1 | Definition and applicability..... | 160 | +| 7.4.2 | Minimum requirement..... | 160 | +| 7.4.3 | Test purpose..... | 160 | +| 7.4.4 | Method of test..... | 160 | +| 7.4.4.1 | Initial conditions..... | 160 | +| 7.4.4.2 | Procedure..... | 160 | +| 7.4.5 | Test requirement..... | 161 | +| 7.4.5.1 | General..... | 161 | +| 7.4.5.2 | Test requirements for BS type 1-O ..... | 161 | +| 7.5 | OTA in-band selectivity and blocking..... | 174 | +| 7.5.1 | OTA adjacent channel selectivity..... | 174 | +| 7.5.1.1 | Definition and applicability..... | 174 | +| 7.5.1.2 | Minimum requirement..... | 174 | +| 7.5.1.3 | Test purpose..... | 174 | +| 7.5.1.4 | Method of test..... | 174 | +| 7.5.1.4.1 | Initial conditions..... | 174 | +| 7.5.1.4.2 | Procedure..... | 174 | +| 7.5.1.5 | Test requirement..... | 175 | +| 7.5.1.5.1 | General..... | 175 | +| 7.5.1.5.2 | Test requirements for BS type 1-O ..... | 175 | +| 7.5.1.5.3 | Test requirements for BS type 2-O ..... | 176 | +| 7.5.2 | OTA in-band blocking..... | 177 | +| 7.5.2.1 | Definition and applicability..... | 177 | +| 7.5.2.2 | Minimum requirement..... | 177 | +| 7.5.2.3 | Test purpose..... | 177 | +| 7.5.2.4 | Method of test..... | 177 | +| 7.5.2.4.1 | Initial conditions..... | 177 | +| 7.5.2.4.2 | Procedure..... | 178 | +| 7.5.2.5 | Test requirement..... | 179 | +| 7.5.2.5.1 | General..... | 179 | +| 7.5.2.5.2 | Test requirements for BS type 1-O ..... | 179 | +| 7.5.2.5.3 | Test requirements for BS type 2-O ..... | 182 | +| 7.6 | OTA out-of-band blocking..... | 183 | +| 7.6.1 | Definition and applicability..... | 183 | +| 7.6.2 | Minimum requirement..... | 183 | +| 7.6.3 | Test purpose..... | 183 | +| 7.6.4 | Method of test..... | 184 | +| 7.6.4.1 | Initial conditions..... | 184 | +| 7.6.4.2 | Procedure..... | 184 | +| 7.6.4.2.1 | BS type 1-O procedure for out-of-band blocking..... | 184 | +| 7.6.4.2.2 | BS type 1-O procedure for co-location blocking..... | 185 | +| 7.6.4.2.3 | BS type 2-O procedure for out-of-band blocking..... | 185 | +| 7.6.5 | Test requirements..... | 186 | +| 7.6.5.1 | Requirement for BS type 1-O ..... | 186 | +| 7.6.5.1.1 | General..... | 186 | +| 7.6.5.1.2 | Co-location requirement..... | 187 | +| 7.6.5.2 | Requirement for BS type 2-O ..... | 187 | +| 7.6.5.2.1 | General requirement..... | 187 | +| 7.7 | OTA receiver spurious emissions..... | 188 | +| 7.7.1 | Definition and applicability..... | 188 | +| 7.7.2 | Minimum requirement..... | 188 | + +| | | | +|-----------|----------------------------------------------------------------------------------------------|-----| +| 7.7.3 | Test purpose..... | 189 | +| 7.7.4 | Method of test..... | 189 | +| 7.7.4.1 | Initial conditions..... | 189 | +| 7.7.4.2 | Procedure..... | 189 | +| 7.7.5 | Test requirement..... | 190 | +| 7.7.5.1 | Test requirement for BS type 1-O ..... | 190 | +| 7.7.5.2 | Test requirement for BS type 2-O ..... | 191 | +| 7.8 | OTA receiver intermodulation..... | 192 | +| 7.8.1 | Definition and applicability..... | 192 | +| 7.8.2 | Minimum requirement..... | 192 | +| 7.8.3 | Test purpose..... | 192 | +| 7.8.4 | Method of test..... | 192 | +| 7.8.4.1 | Initial conditions..... | 192 | +| 7.8.4.2 | Procedure..... | 193 | +| 7.8.5 | Test requirement..... | 193 | +| 7.8.5.1 | BS type 1-O ..... | 193 | +| 7.8.5.2 | BS type 2-O ..... | 199 | +| 7.9 | OTA in-channel selectivity..... | 200 | +| 7.9.1 | Definition and applicability..... | 200 | +| 7.9.2 | Minimum requirement..... | 200 | +| 7.9.3 | Test purpose..... | 201 | +| 7.9.4 | Method of test..... | 201 | +| 7.9.4.1 | Initial conditions..... | 201 | +| 7.9.4.2 | Procedure..... | 201 | +| 7.9.5 | Test requirement..... | 202 | +| 7.9.5.1 | BS type 1-O ..... | 202 | +| 7.9.5.2 | BS type 2-O ..... | 207 | +| 8 | Radiated performance requirements..... | 209 | +| 8.1 | General..... | 209 | +| 8.1.0 | Scope and definitions..... | 209 | +| 8.1.1 | OTA demodulation branches..... | 209 | +| 8.1.2 | Applicability rule..... | 210 | +| 8.1.2.0 | General..... | 210 | +| 8.1.2.1 | Applicability of PUSCH performance requirements..... | 210 | +| 8.1.2.1.1 | Applicability of requirements for different subcarrier spacings..... | 210 | +| 8.1.2.1.2 | Applicability of requirements for different channel bandwidths..... | 210 | +| 8.1.2.1.3 | Applicability of requirements for different configurations..... | 210 | +| 8.1.2.1.4 | Applicability of requirements for uplink carrier aggregation..... | 210 | +| 8.1.2.1.5 | Applicability of requirements for TDD with different UL-DL patterns..... | 210 | +| 8.1.2.1.6 | Applicability of UL timing adjustment requirements for different scenarios..... | 211 | +| 8.1.2.1.7 | Applicability of 2-step RA type requirements for different subcarrier spacings..... | 211 | +| 8.1.2.1.8 | Applicability of PUSCH with 0.001% BLER requirements..... | 211 | +| 8.1.2.1.9 | Applicability of PUSCH repetition type A requirements..... | 211 | +| 8.1.2.2 | Applicability of PUCCH performance requirements..... | 211 | +| 8.1.2.2.1 | Applicability of requirements for different formats..... | 211 | +| 8.1.2.2.2 | Applicability of requirements for different subcarrier spacings..... | 211 | +| 8.1.2.2.3 | Applicability of requirements for different channel bandwidths..... | 211 | +| 8.1.2.2.4 | Applicability of requirements for different configurations..... | 211 | +| 8.1.2.2.5 | Applicability of requirements for multi-slot PUCCH..... | 212 | +| 8.1.2.2.6 | Applicability of requirements for PUCCH sub-slot based repetition..... | 212 | +| 8.1.2.3 | Applicability of PRACH performance requirements..... | 212 | +| 8.1.2.3.1 | Applicability of requirements for different formats..... | 212 | +| 8.1.2.3.2 | Applicability of requirements for different subcarrier spacings..... | 212 | +| 8.1.2.3.3 | Applicability of requirements for different channel bandwidths..... | 212 | +| 8.1.2.3.4 | Applicability of requirements for different restricted set types of long PRACH format 0..... | 212 | +| 8.1.2.4 | Applicability of PUSCH for high speed train performance requirements..... | 212 | +| 8.1.2.4.1 | Applicability of requirements for different speeds..... | 212 | +| 8.1.2.4.2 | Applicability of requirements for ITIR..... | 212 | +| 8.1.2.4.3 | Applicability of requirements for different channel bandwidths..... | 213 | +| 8.1.2.4.4 | Applicability of requirements for different DM-RS configurations..... | 213 | +| 8.1.2.5 | Applicability of interlaced PUSCH performance requirements..... | 213 | + +| | | | +|------------|-----------------------------------------------------------------------------------------------|-----| +| 8.1.2.5.1 | General applicability of interlaced PUSCH performance requirements..... | 213 | +| 8.1.2.5.2 | Applicability of requirements for different subcarrier spacings..... | 213 | +| 8.1.2.5.3 | Applicability of requirements for different channel bandwidths..... | 213 | +| 8.1.2.5.4 | Applicability of requirements for different configurations..... | 213 | +| 8.1.2.5.5 | Applicability of CG-UCI multiplexed on PUSCH requirements..... | 213 | +| 8.1.2.6 | Applicability of interlaced PUCCH performance requirements..... | 214 | +| 8.1.2.6.1 | General applicability of interlaced PUCCH performance requirements..... | 214 | +| 8.1.2.6.2 | Applicability of requirements for different formats..... | 214 | +| 8.1.2.6.3 | Applicability of requirements for different subcarrier spacings..... | 214 | +| 8.1.2.6.4 | Applicability of requirements for different channel bandwidths..... | 214 | +| 8.1.2.7 | Applicability of performance requirements for PRACH with $L_{RA}=1151$ and $L_{RA}=571$ ..... | 214 | +| 8.1.2.7.1 | Applicability of requirements for different formats..... | 214 | +| 8.1.2.7.2 | Applicability of requirements for different subcarrier spacings..... | 214 | +| 8.1.2.7.3 | Applicability of requirements for different channel bandwidths..... | 214 | +| 8.1.2.8 | Applicability of performance requirements for PUSCH with TB over Multi-Slots..... | 214 | +| 8.1.2.8.1 | Applicability of requirements for different UL-DL patterns..... | 214 | +| 8.1.2.9 | Applicability of performance requirements for PUSCH with DM-RS bundling..... | 215 | +| 8.1.2.9.1 | Applicability of requirements for TDD different subcarrier spacings..... | 215 | +| 8.1.2.9.2 | Applicability of requirements for TDD with different UL-DL patterns..... | 215 | +| 8.1.2.9.3 | Applicability of requirements for different receiver antenna connectors..... | 215 | +| 8.1.2.10 | Applicability of performance requirements for PUCCH with DM-RS bundling..... | 215 | +| 8.1.2.10.1 | Applicability of requirements for TDD different subcarrier spacings..... | 215 | +| 8.1.2.10.2 | Applicability of requirements for TDD with different UL-DL patterns..... | 215 | +| 8.2 | OTA performance requirements for PUSCH..... | 215 | +| 8.2.1 | Performance requirements for PUSCH with transform precoding disabled..... | 215 | +| 8.2.1.1 | Definition and applicability..... | 215 | +| 8.2.1.2 | Minimum Requirement..... | 215 | +| 8.2.1.3 | Test purpose..... | 216 | +| 8.2.1.4 | Method of test..... | 216 | +| 8.2.1.4.1 | Initial conditions..... | 216 | +| 8.2.1.4.2 | Procedure..... | 216 | +| 8.2.1.5 | Test Requirement..... | 218 | +| 8.2.1.5.1 | Test requirement for BS type 1-O ..... | 218 | +| 8.2.1.5.2 | Test requirement for BS type 2-O ..... | 223 | +| 8.2.2 | Performance requirements for PUSCH with transform precoding enabled..... | 227 | +| 8.2.2.1 | Definition and applicability..... | 227 | +| 8.2.2.2 | Minimum Requirement..... | 227 | +| 8.2.2.3 | Test Purpose..... | 227 | +| 8.2.2.4 | Method of test..... | 227 | +| 8.2.2.4.1 | Initial Conditions..... | 227 | +| 8.2.2.4.2 | Procedure..... | 227 | +| 8.2.2.5 | Test Requirement..... | 229 | +| 8.2.2.5.1 | Test requirement for BS type 1-O ..... | 229 | +| 8.2.2.5.2 | Test requirement for BS type 2-O ..... | 230 | +| 8.2.3 | Performance requirements for UCI multiplexed on PUSCH..... | 231 | +| 8.2.3.1 | Definition and applicability..... | 231 | +| 8.2.3.2 | Minimum Requirement..... | 231 | +| 8.2.3.3 | Test purpose..... | 232 | +| 8.2.3.4 | Method of test..... | 232 | +| 8.2.3.4.1 | Initial conditions..... | 232 | +| 8.2.3.4.2 | Procedure..... | 232 | +| 8.2.3.5 | Test Requirement..... | 234 | +| 8.2.3.5.1 | Test requirement for BS type 1-O ..... | 234 | +| 8.2.3.5.2 | Test requirement for BS type 2-O ..... | 235 | +| 8.2.4 | Performance requirements for PUSCH for high speed train..... | 236 | +| 8.2.4.1 | Definition and applicability..... | 236 | +| 8.2.4.2 | Minimum Requirement..... | 236 | +| 8.2.4.3 | Test Purpose..... | 236 | +| 8.2.4.4 | Method of test..... | 236 | +| 8.2.4.4.1 | Initial Conditions..... | 236 | +| 8.2.4.4.2 | Procedure..... | 237 | + +| | | | +|------------|--------------------------------------------------------------------------|-----| +| 8.2.4.5 | Test Requirement for BS Type 1-O ..... | 239 | +| 8.2.4.6 | Test Requirement for BS Type 2-O ..... | 241 | +| 8.2.5 | Performance requirements for UL timing adjustment..... | 241 | +| 8.2.5.1 | Definition and applicability..... | 241 | +| 8.2.5.2 | Minimum Requirement..... | 242 | +| 8.2.5.3 | Test Purpose..... | 242 | +| 8.2.5.4 | Method of test..... | 242 | +| 8.2.5.4.1 | Initial Conditions..... | 242 | +| 8.2.5.4.2 | Procedure..... | 242 | +| 8.2.5.5 | Test Requirement for High Speed Train for BS type 1-O ..... | 245 | +| 8.2.5.5a | Test Requirement for High Speed Train for BS type 2-O ..... | 246 | +| 8.2.5.6 | Test Requirement for Normal Mode..... | 246 | +| 8.2.6 | Performance requirements for PUSCH with 0.001% BLER..... | 246 | +| 8.2.6.1 | Definition and applicability..... | 246 | +| 8.2.6.2 | Minimum Requirement..... | 247 | +| 8.2.6.3 | Test Purpose..... | 247 | +| 8.2.6.4 | Method of test..... | 247 | +| 8.2.6.4.1 | Initial Conditions..... | 247 | +| 8.2.6.4.2 | Procedure..... | 247 | +| 8.2.6.5 | Test requirement..... | 248 | +| 8.2.6.5.1 | Test requirement for BS type 1-O ..... | 248 | +| 8.2.7 | Performance requirements for PUSCH repetition Type A..... | 250 | +| 8.2.7.1 | Definition and applicability..... | 250 | +| 8.2.7.2 | Minimum Requirement..... | 250 | +| 8.2.7.3 | Test purpose..... | 250 | +| 8.2.7.4 | Method of test..... | 250 | +| 8.2.7.4.1 | Initial conditions..... | 250 | +| 8.2.7.4.2 | Procedure..... | 250 | +| 8.2.7.5 | Test Requirement..... | 252 | +| 8.2.7.5.1 | Test requirement for BS type 1-O ..... | 252 | +| 8.2.7.5.2 | Test requirement for BS type 2-O ..... | 254 | +| 8.2.8.1 | Definition and applicability..... | 254 | +| 8.2.8.2 | Minimum Requirement..... | 255 | +| 8.2.8.3 | Test purpose..... | 255 | +| 8.2.8.4 | Method of test..... | 255 | +| 8.2.8.4.1 | Initial conditions..... | 255 | +| 8.2.8.4.2 | Procedure..... | 255 | +| 8.2.8.5 | Test Requirement..... | 257 | +| 8.2.8.5.1 | Test requirement for BS type 1-O ..... | 257 | +| 8.2.8.5.2 | Test requirement for BS type 2-O ..... | 258 | +| 8.2.9 | Performance requirements for MsgA PUSCH..... | 259 | +| 8.2.9.1 | Definition and applicability..... | 259 | +| 8.2.9.2 | Minimum Requirement..... | 259 | +| 8.2.9.3 | Test Purpose..... | 259 | +| 8.2.9.4 | Method of test..... | 259 | +| 8.2.9.4.1 | Initial Conditions..... | 259 | +| 8.2.9.4.2 | Procedure..... | 259 | +| 8.2.9.5 | Test Requirement..... | 262 | +| 8.2.9.5.1 | Test Requirement for BS type 1-O ..... | 262 | +| 8.2.9.5.2 | Test Requirement for BS type 2-O ..... | 263 | +| 8.2.10 | Requirements for interlaced PUSCH..... | 264 | +| 8.2.10.1 | Definition and applicability..... | 264 | +| 8.2.10.2 | Minimum Requirement..... | 264 | +| 8.2.10.3 | Test Purpose..... | 264 | +| 8.2.10.4 | Method of test..... | 264 | +| 8.2.10.4.1 | Initial Conditions..... | 264 | +| 8.2.10.4.2 | Procedure..... | 265 | +| 8.2.10.5 | Test Requirement..... | 266 | +| 8.2.10.5.1 | Test requirement for BS type 1-O ..... | 266 | +| 8.2.11 | Performance requirements for CG-UCI multiplexed on interlaced PUSCH..... | 267 | +| 8.2.11.1 | Definition and applicability..... | 267 | + +| | | | +|------------|-------------------------------------------------------------------------------|-----| +| 8.2.11.2 | Minimum Requirement..... | 267 | +| 8.2.11.3 | Test purpose..... | 267 | +| 8.2.11.4 | Method of test..... | 267 | +| 8.2.11.4.1 | Initial conditions..... | 267 | +| 8.2.11.4.2 | Procedure..... | 267 | +| 8.2.11.5 | Test Requirement..... | 269 | +| 8.2.11.5.1 | Test requirement for BS type 1-O ..... | 269 | +| 8.2.12 | Performance requirements for TB processing over multi-slot PUSCH (TBoMS)..... | 269 | +| 8.2.12.1 | Definition and applicability..... | 269 | +| 8.2.12.2 | Minimum Requirement..... | 269 | +| 8.2.12.3 | Test Purpose..... | 270 | +| 8.2.12.4 | Method of test..... | 270 | +| 8.2.12.4.1 | Initial Conditions..... | 270 | +| 8.2.12.4.2 | Procedure..... | 270 | +| 8.2.12.5 | Test Requirement..... | 272 | +| 8.2.12.5.1 | Test requirement for BS type 1-O ..... | 272 | +| 8.2.12.5.2 | Test requirement for BS type 2-O ..... | 273 | +| 8.2.13 | Performance requirements for PUSCH with DMRS bundling..... | 273 | +| 8.2.13.1 | Definition and applicability..... | 273 | +| 8.2.13.2 | Minimum Requirement..... | 274 | +| 8.2.13.3 | Test Purpose..... | 274 | +| 8.2.13.4 | Method of test..... | 274 | +| 8.2.13.4.1 | Initial Conditions..... | 274 | +| 8.2.13.4.2 | Procedure..... | 274 | +| 8.2.13.5 | Test Requirement..... | 276 | +| 8.2.13.5.1 | Test requirement for BS type 1-O ..... | 276 | +| 8.2.13.5.2 | Test requirement for BS type 2-O ..... | 278 | +| 8.3 | OTA performance requirements for PUCCH..... | 279 | +| 8.3.1 | Performance requirements for PUCCH format 0..... | 279 | +| 8.3.1.1 | Definition and applicability..... | 279 | +| 8.3.1.2 | Minimum Requirement..... | 279 | +| 8.3.1.3 | Test purpose..... | 279 | +| 8.3.1.4 | Method of test..... | 279 | +| 8.3.1.4.1 | Initial conditions..... | 279 | +| 8.3.1.4.2 | Procedure..... | 279 | +| 8.3.1.5 | Test Requirement..... | 281 | +| 8.3.1.5.1 | Test requirement for BS type 1-O ..... | 281 | +| 8.3.1.5.2 | Test requirement for BS type 2-O ..... | 282 | +| 8.3.2 | Performance requirements for PUCCH format 1..... | 282 | +| 8.3.2.1 | NACK to ACK detection..... | 282 | +| 8.3.2.1.1 | Definition and applicability..... | 282 | +| 8.3.2.1.2 | Minimum Requirement..... | 283 | +| 8.3.2.1.3 | Test purpose..... | 283 | +| 8.3.2.1.4 | Method of test..... | 283 | +| 8.3.2.1.5 | Test Requirement..... | 285 | +| 8.3.2.2 | ACK missed detection..... | 286 | +| 8.3.2.2.1 | Definition and applicability..... | 286 | +| 8.3.2.2.2 | Minimum Requirement..... | 287 | +| 8.3.2.2.3 | Test purpose..... | 287 | +| 8.3.2.2.4 | Method of test..... | 287 | +| 8.3.2.2.5 | Test Requirement..... | 289 | +| 8.3.3 | Performance requirements for PUCCH format 2..... | 290 | +| 8.3.3.1 | ACK missed detection performance requirements..... | 290 | +| 8.3.3.1.1 | Definition and applicability..... | 290 | +| 8.3.3.1.2 | Minimum Requirement..... | 290 | +| 8.3.3.1.3 | Test Purpose..... | 290 | +| 8.3.3.1.4 | Method of test..... | 290 | +| 8.3.3.1.5 | Test requirement..... | 292 | +| 8.3.3.2 | UCI BLER performance requirements..... | 293 | +| 8.3.3.2.1 | Definition and applicability..... | 293 | +| 8.3.3.2.2 | Minimum Requirement..... | 294 | + +| | | | +|-----------|-------------------------------------------------------------|-----| +| 8.3.3.2.3 | Test Purpose..... | 294 | +| 8.3.3.2.4 | Method of test..... | 294 | +| 8.3.3.2.5 | Test requirement..... | 295 | +| 8.3.4 | Performance requirements for PUCCH format 3..... | 296 | +| 8.3.4.1 | Definition and applicability..... | 296 | +| 8.3.4.2 | Minimum requirement..... | 297 | +| 8.3.4.3 | Test purpose..... | 297 | +| 8.3.4.4 | Method of test..... | 297 | +| 8.3.4.4.1 | Initial conditions..... | 297 | +| 8.3.4.4.2 | Procedure..... | 297 | +| 8.3.4.5 | Test requirement..... | 298 | +| 8.3.4.5.1 | Test requirement for BS type 1-O ..... | 298 | +| 8.3.4.5.2 | Test requirement for BS type 2-O ..... | 299 | +| 8.3.5 | Performance requirements for PUCCH format 4..... | 300 | +| 8.3.5.1 | Definition and applicability..... | 300 | +| 8.3.5.2 | Minimum requirement..... | 300 | +| 8.3.5.3 | Test purpose..... | 300 | +| 8.3.5.4 | Method of test..... | 300 | +| 8.3.5.4.1 | Initial conditions..... | 300 | +| 8.3.5.4.2 | Procedure..... | 300 | +| 8.3.5.5 | Test requirement..... | 302 | +| 8.3.5.5.1 | Test requirement for BS type 1-O ..... | 302 | +| 8.3.5.5.2 | Test requirement for BS type 2-O ..... | 302 | +| 8.3.6 | Performance requirements for multi-slot PUCCH format..... | 303 | +| 8.3.6.1 | Performance requirements for multi-slot PUCCH format 1..... | 303 | +| 8.3.6.1.1 | NACK to ACK detection..... | 303 | +| 8.3.6.1.2 | ACK missed detection..... | 305 | +| 8.3.7 | Performance requirements for interlaced PUCCH format 0..... | 307 | +| 8.3.7.1 | Definition and applicability..... | 307 | +| 8.3.7.2 | Minimum Requirement..... | 308 | +| 8.3.7.3 | Test purpose..... | 308 | +| 8.3.7.4 | Method of test..... | 308 | +| 8.3.7.4.1 | Initial conditions..... | 308 | +| 8.3.7.4.2 | Procedure..... | 308 | +| 8.3.7.5 | Test Requirement..... | 309 | +| 8.3.7.5.1 | Test requirement for BS type 1-O ..... | 309 | +| 8.3.8 | Performance requirements for interlaced PUCCH format 1..... | 309 | +| 8.3.8.1 | NACK to ACK detection..... | 309 | +| 8.3.8.1.1 | Definition and applicability..... | 309 | +| 8.3.8.1.2 | Minimum Requirement..... | 310 | +| 8.3.8.1.3 | Test purpose..... | 310 | +| 8.3.8.1.4 | Method of test..... | 310 | +| 8.3.8.1.5 | Test Requirement..... | 311 | +| 8.3.8.2 | ACK missed detection..... | 311 | +| 8.3.8.2.1 | Definition and applicability..... | 311 | +| 8.3.8.2.2 | Minimum Requirement..... | 312 | +| 8.3.8.2.3 | Test purpose..... | 312 | +| 8.3.8.2.4 | Method of test..... | 312 | +| 8.3.8.2.5 | Test Requirement..... | 313 | +| 8.3.9 | Performance requirements for interlaced PUCCH format 2..... | 314 | +| 8.3.9.1 | Definition and applicability..... | 314 | +| 8.3.9.2 | Minimum Requirement..... | 314 | +| 8.3.9.3 | Test Purpose..... | 314 | +| 8.3.9.4 | Method of test..... | 314 | +| 8.3.9.4.1 | Initial conditions..... | 314 | +| 8.3.9.4.2 | Procedure..... | 314 | +| 8.3.9.5 | Test requirement..... | 315 | +| 8.3.10 | Performance requirements for interlaced PUCCH format 3..... | 316 | +| 8.3.10.1 | Definition and applicability..... | 316 | +| 8.3.10.2 | Minimum Requirement..... | 316 | +| 8.3.10.3 | Test Purpose..... | 316 | + +| | | | +|--------------|----------------------------------------------------------------------------|-----| +| 8.3.10.4 | Method of test..... | 316 | +| 8.3.10.4.1 | Initial conditions..... | 316 | +| 8.3.10.4.2 | Procedure..... | 316 | +| 8.3.10.5 | Test requirement..... | 317 | +| 8.3.11 | Performance requirements for PUCCH sub-slot based repetition format 0..... | 318 | +| 8.3.11.1 | Definition and applicability..... | 318 | +| 8.3.11.2 | Minimum Requirement..... | 318 | +| 8.3.11.3 | Test purpose..... | 318 | +| 8.3.11.4 | Method of test..... | 319 | +| 8.3.11.4.1 | Initial conditions..... | 319 | +| 8.3.11.4.2 | Procedure..... | 319 | +| 8.3.11.5 | Test Requirement..... | 320 | +| 8.3.11.5.1 | Test requirement for BS type 1-O ..... | 320 | +| 8.3.12 | Performance requirements PUCCH format 1 with DM-RS bundling..... | 320 | +| 8.3.12.1 | NACK to ACK detection..... | 320 | +| 8.3.12.1.1 | Definition and applicability..... | 320 | +| 8.3.12.1.2 | Minimum Requirement..... | 321 | +| 8.3.12.1.3 | Test purpose..... | 321 | +| 8.3.12.1.4 | Method of test..... | 321 | +| 8.3.12.1.4.1 | Initial conditions..... | 321 | +| 8.3.12.1.4.2 | Procedure..... | 321 | +| 8.3.12.1.5 | Test Requirement..... | 322 | +| 8.3.12.1.5.1 | Test Requirement for BS type 1-O ..... | 322 | +| 8.3.12.1.5.2 | Test Requirement for BS type 2-O ..... | 323 | +| 8.3.12.2 | ACK missed detection..... | 323 | +| 8.3.12.2.1 | Definition and applicability..... | 323 | +| 8.3.12.2.2 | Minimum Requirement..... | 324 | +| 8.3.12.2.3 | Test purpose..... | 324 | +| 8.3.12.2.4 | Method of test..... | 324 | +| 8.3.12.2.4.1 | Initial conditions..... | 324 | +| 8.3.12.2.4.2 | Procedure..... | 324 | +| 8.3.12.2.5 | Test Requirement..... | 326 | +| 8.3.12.2.5.1 | Test Requirement for BS type 1-O ..... | 326 | +| 8.3.12.2.5.2 | Test Requirement for BS type 2-O ..... | 326 | +| 8.3.13 | Performance requirements for PUCCH format 3 with DM-RS bundling..... | 327 | +| 8.3.13.1 | Definition and applicability..... | 327 | +| 8.3.13.2 | Minimum requirement..... | 327 | +| 8.3.13.3 | Test purpose..... | 327 | +| 8.3.13.4 | Method of test..... | 327 | +| 8.3.13.4.1 | Initial conditions..... | 327 | +| 8.3.13.4.2 | Procedure..... | 327 | +| 8.3.13.5 | Test requirement..... | 329 | +| 8.3.13.5.1 | Test Requirement for BS type 1-O ..... | 329 | +| 8.3.13.5.2 | Test Requirement for BS type 2-O ..... | 329 | +| 8.4 | OTA performance requirements for PRACH..... | 330 | +| 8.4.1 | PRACH false alarm probability and missed detection..... | 330 | +| 8.4.1.1 | Definition and applicability..... | 330 | +| 8.4.1.2 | Minimum requirement..... | 330 | +| 8.4.1.3 | Test purpose..... | 330 | +| 8.4.1.4 | Method of test..... | 330 | +| 8.4.1.4.1 | Initial conditions..... | 330 | +| 8.4.1.4.2 | Procedure..... | 331 | +| 8.4.1.5 | Test requirement for Normal Mode..... | 333 | +| 8.4.1.5.1 | Test requirement for BS type 1-O ..... | 333 | +| 8.4.1.5.2 | Test requirement for BS type 2-O ..... | 334 | +| 8.4.1.6 | Test requirement for high speed train..... | 335 | +| 8.4.1.6.1 | Test requirement for BS type 1-O ..... | 335 | +| 8.4.1.6.2 | Test requirement for BS type 2-O ..... | 336 | +| 8.4.1.7 | Test requirement for PRACH with $L_{RA}=1151$ and $L_{RA}=571$ ..... | 336 | +| 8.4.1.7.1 | Test requirement for BS type 1-O ..... | 336 | +| 8.4.1.7.2 | Test requirement for BS type 2-O ..... | 336 | + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------| +| Annex A (normative): Reference measurement channels..... | 337 | +| A.1 Fixed Reference Channels for OTA sensitivity, OTA reference sensitivity level, OTA ACS, OTA in-band blocking, OTA out-of-band blocking, OTA receiver intermodulation and OTA in-channel selectivity (QPSK, R=1/3)..... | 337 | +| A.2 Fixed Reference Channels for OTA dynamic range (16QAM, R=2/3)..... | 340 | +| A.3 Fixed Reference Channels for performance requirements (QPSK, R=193/1024)..... | 340 | +| A.3A Fixed Reference Channels for performance requirements (QPSK, R=99/1024)..... | 348 | +| A.3B Fixed Reference Channels for performance requirements (QPSK, R=308/1024)..... | 350 | +| A.4 Fixed Reference Channels for performance requirements (16QAM, R=658/1024)..... | 354 | +| A.5 Fixed Reference Channels for performance requirements (64QAM, R=567/1024)..... | 359 | +| A.6 PRACH Test preambles..... | 362 | +| A.7 Fixed Reference Channels for performance requirements (16QAM, R=434/1024)..... | 363 | +| A.8 Fixed Reference Channels for performance requirements (QPSK, R=157/1024)..... | 365 | +| A.9 Fixed Reference Channels for performance requirements (256QAM, R=682.5/1024)..... | 366 | +| A.10 Fixed Reference Channels for performance requirements (64QAM, R=517/1024)..... | 367 | +| A.11 Fixed Reference Channels for performance requirements (64QAM, R=438/1024)..... | 370 | +| Annex B (normative): Environmental requirements for the BS equipment..... | 371 | +| B.1 General..... | 371 | +| B.2 Normal test environment..... | 371 | +| B.3 Extreme test environment..... | 371 | +| B.3.1 Extreme temperature..... | 371 | +| B.4 Vibration..... | 372 | +| B.5 Power supply..... | 372 | +| B.6 Measurement of test environments..... | 372 | +| B.7 OTA extreme test methods..... | 373 | +| B.7.1 Direct far field method..... | 373 | +| B.7.2 Relative method..... | 373 | +| Annex C (informative): Test tolerances and derivation of test requirements..... | 375 | +| C.1 Measurement of transmitter..... | 376 | +| C.2 Measurement of receiver..... | 382 | +| C.3 Measurement of performance requirements..... | 383 | +| Annex D (normative): Calibration..... | 386 | +| Annex E (informative): OTA measurement system set-up..... | 387 | +| E.1 Transmitter..... | 387 | +| E.1.1 Radiated transmit power, OTA output power dynamics, OTA transmitted signal quality, OTA occupied bandwidth, and OTA transmit ON/OFF power ( BS type 2-O )..... | 387 | +| E.1.2 OTA base station output power, OTA ACLR, OTA operating band unwanted emissions..... | 388 | +| E.1.3 OTA spurious emissions..... | 388 | +| E.1.4 OTA co-location emissions, OTA transmit ON/OFF power ( BS type 1-O )..... | 389 | + +| | | | +|-------------------------------|------------------------------------------------------------------------------------------|------------| +| E.1.5 | OTA transmitter intermodulation..... | 390 | +| E.2 | Receiver..... | 391 | +| E.2.1 | OTA sensitivity and OTA reference sensitivity level..... | 391 | +| E.2.2 | OTA dynamic range..... | 391 | +| E.2.3 | OTA adjacent channel selectivity, general OTA blocking, and OTA narrowband blocking..... | 392 | +| E.2.4 | OTA blocking..... | 393 | +| E.2.4.1 | General OTA out-of-band blocking..... | 393 | +| E.2.4.2 | OTA co-location blocking..... | 393 | +| E.2.5 | OTA receiver spurious emissions..... | 394 | +| E.2.6 | OTA receiver intermodulation..... | 394 | +| E.2.7 | OTA in-channel selectivity..... | 395 | +| E.3 | Performance requirements..... | 395 | +| Annex F (normative): | Void | 396 | +| Annex G (informative): | Transmitter spatial emissions declaration..... | 397 | +| G.1 | General..... | 397 | +| G.2 | Declarations..... | 398 | +| Annex H (normative): | Characteristics of the interfering signals..... | 399 | +| Annex I (normative): | TRP measurement procedures..... | 400 | +| I.1 | General..... | 400 | +| I.2 | Spherical equal angle grid..... | 400 | +| I.2.1 | General..... | 400 | +| I.2.2 | Reference angular step criteria..... | 400 | +| I.3 | Spherical equal area grid..... | 402 | +| I.4 | Spherical Fibonacci grid..... | 403 | +| I.5 | Orthogonal cut grid..... | 403 | +| I.5.1 | General..... | 403 | +| I.5.2 | Operating band unwanted emissions..... | 404 | +| I.5.3 | Spurious unwanted emissions..... | 404 | +| I.6 | Wave vector space grid..... | 405 | +| I.7 | Void..... | 405 | +| I.8 | Void..... | 405 | +| I.9 | Full sphere with sparse sampling..... | 405 | +| I.10 | Beam-based directions..... | 406 | +| I.11 | Peak method..... | 406 | +| I.12 | Equal sector with peak average..... | 406 | +| I.13 | Pre-scan..... | 407 | +| Annex J (normative): | Propagation conditions..... | 408 | +| J.1 | Static propagation condition..... | 408 | +| J.2 | Multi-path fading propagation conditions..... | 408 | +| J.2.1 | Delay profiles..... | 408 | +| J.2.1.1 | Delay profiles for FR1..... | 409 | + +| | | | +|-------------------------------|---------------------------------------------------------------------------------|------------| +| J.2.1.2 | Delay profiles for FR2..... | 410 | +| J.2.2 | Combinations of channel model parameters..... | 411 | +| J.2.3 | MIMO channel correlation matrices..... | 411 | +| J.2.3.1 | MIMO correlation matrices using Uniform Linear Array..... | 411 | +| J.2.3.1.1 | Definition of MIMO correlation matrices..... | 411 | +| J.2.3.1.2 | MIMO correlation matrices at high, medium and low level..... | 413 | +| J.2.3.2 | Multi-antenna channel models using cross polarized antennas..... | 415 | +| J.2.3.2.1 | Definition of MIMO correlation matrices using cross polarized antennas..... | 415 | +| J.2.3.2.2 | Spatial correlation matrices at UE and gNB sides..... | 416 | +| J.2.3.2.2.1 | Spatial correlation matrices at UE side..... | 416 | +| J.2.3.2.2.2 | Spatial correlation matrices at gNB side..... | 416 | +| J.2.3.2.3 | MIMO correlation matrices using cross polarized antennas..... | 416 | +| J.3 | High speed train condition..... | 417 | +| J.4 | Moving propagation conditions..... | 422 | +| Annex K (informative): | Measuring noise close to noise-floor..... | 424 | +| Annex L (normative): | In-channel TX tests..... | 425 | +| L.1 | General..... | 425 | +| L.2 | Basic principles..... | 425 | +| L.2.1 | Output signal of the TX under test..... | 425 | +| L.2.2 | Ideal signal..... | 425 | +| L.2.3 | Measurement results..... | 426 | +| L.2.4 | Measurement points..... | 426 | +| L.3 | Pre-FFT minimization process..... | 428 | +| L.4 | Timing of the FFT window..... | 428 | +| L.5 | Resource element TX power..... | 429 | +| L.6 | Post-FFT equalisation..... | 430 | +| L.7 | EVM..... | 432 | +| L.7.0 | General..... | 432 | +| L.7.1 | Averaged EVM (FDD)..... | 432 | +| L.7.2 | Averaged EVM (TDD) for FR1 and FR2-1..... | 433 | +| L.7.3 | Averaged EVM (TDD) for FR2-2..... | 433 | +| Annex M (normative): | General rules for statistical testing..... | 434 | +| M.1 | Testing methodology of PUSCH performance requirements with 0.001% BLER..... | 434 | +| M.1.1 | General..... | 434 | +| M.1.2 | Numerical definition of the pass-fail limits for testing PUSCH 0.001% BLER..... | 435 | +| M.1.3 | Theory to derive the early pass/fail limits in M.1.2 (informative)..... | 436 | +| M.1.3.1 | Numerical definition of the pass-fail limits for testing PUSCH 0.001% BLER..... | 436 | +| M.1.3.2 | Simulation to derive the pass-fail limits for testing PUSCH 0.001% BLER..... | 436 | +| Annex N (informative): | Change history..... | 438 | + +## 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 Base Station (BS) *type 1-H*, *BS type 1-O* and *BS type 2-O*. These have been derived from, and are consistent with the radiated requirements for *BS type 1-H*, *BS type 1-O* and *BS type 2-O* in BS specification defined in TS 38.104 [2]. + +A *BS type 1-C* only has conducted requirements so it does not require compliance to this specification. + +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-1 [3]. + +*BS type 1-O* and *BS type 2-O* have only radiated requirements so they require compliance to this specification 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-1: "NR, Base Station (BS) conformance testing, Part 1: Conducted conformance testing" +- [4] Recommendation ITU-R 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] Void +- [7] 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" +- [8] 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" +- [9] IEC 60 721: "Classification of environmental conditions" +- [10] IEC 60 068-2-1 (2007): "Environmental testing - Part 2: Tests. Tests A: Cold" +- [11] IEC 60 068-2-2: (2007): "Environmental testing - Part 2: Tests. Tests B: Dry heat" +- [12] IEC 60 068-2-6: (2007): "Environmental testing - Part 2: Tests - Test Fc: Vibration (sinusoidal)" +- [13] Recommendation ITU-R M.328: "Spectra and bandwidth of emissions" +- [14] FCC publication number 662911: "Emissions Testing of Transmitters with Multiple Outputs in the Same Band" +- [15] 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)" + +- [16] Void +- [17] Void +- [18] 3GPP TS 36.104: "E-UTRA; Base Station (BS) radio transmission and reception" +- [19] 3GPP TS 38.212: "NR; Multiplexing and channel coding" +- [20] 3GPP TS 38.211: "NR; Physical channels and modulation" +- [21] 3GPP TS 38.214: "NR; Physical layer procedures for data" +- [22] 3GPP TS 38.331: "NR; Radio Resource Control (RRC) protocol specification" +- [23] 3GPP TR 38.901: "Study on channel model for frequencies from 0.5 to 100 GHz" +- [24] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone" +- [25] 3GPP TS 38.101-2: "NR; User Equipment (UE) radio transmission and reception; Part 2: Range 2 Standalone" +- [26] ERC Recommendation 74-01: "Unwanted emissions in the spurious domain" +- [27] 3GPP TR 25.942: "RF system scenarios". +- [28] ITU-T Recommendation O.150, "Equipment for the measurement of digital and analogue/digital parameters" +- [29] 3GPP TR 37.941: "Radio Frequency (RF) conformance testing background for radiated Base Station (BS) requirements" +- [30] 3GPP TS 37.145-2: "Active Antenna System (AAS) Base Station (BS) conformance testing; Part 2: radiated 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*. + +**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 1: In single carrier operation, the *Base Station RF Bandwidth* is equal to the channel bandwidth. + +**Base Station RF Bandwidth edge:** frequency of one of the edges of the *Base Station RF Bandwidth*. + +**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. + +**beam:** beam (of the antenna) is the main lobe of the radiation pattern of an *antenna array*. + +NOTE 2: For certain BS *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. + +**BS channel bandwidth:** RF bandwidth supporting a single NR RF carrier with the transmission bandwidth configured in the uplink or downlink. + +NOTE 3: The *BS channel bandwidth* is measured in MHz and is used as a reference for transmitter and receiver RF requirements. + +NOTE 4: 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 receiver:** composite receiver function of a BS receiving in an *operating band*. + +**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. + +**BS type 2-O:** NR base station operating at FR2 with a requirement set consisting only of OTA requirements defined at the RIB. + +**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. + +**co-location reference antenna:** a passive antenna used as reference for base station to base station co-location 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)*. + +**demodulation branch:** single input of the *BS receiver* to the demodulation algorithms. + +**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 *FR1 OTA REFSENS RoAoA* or *FR2 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 5: Isotropic directivity is equal in all directions (0 dBi). + +**equivalent isotropic sensitivity:** sensitivity for an isotropic directivity device equivalent to the sensitivity of the discussed device exposed to an incoming wave from a defined AoA. + +NOTE 6: The sensitivity is the minimum received power level at which specific requirement is met. + +NOTE 7: Isotropic directivity is equal in all directions (0 dBi). + +**fractional bandwidth:** fractional bandwidth FBW is defined in percent as . + +**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 8: Carriers aggregated in each band can be contiguous or non-contiguous. + +**intra-band contiguous carrier aggregation:** *contiguous carriers* aggregated in the same operating band. + +**intra-band non-contiguous carrier aggregation:** non-contiguous carriers aggregated in the same operating band. + +**Inter-band gap:** The frequency gap between two supported consecutive operating bands. + +**Inter RF Bandwidth gap:** frequency gap between two consecutive Base Station RF Bandwidths that are placed within two supported *operating bands*. + +**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 9: It is used as a frequency reference point for both transmitter and receiver requirements. + +**maximum carrier TRP:** mean power level measured per RIB during the *transmitter ON period* for a specific carrier in a specified reference condition and corresponding to the declared *rated carrier TRP* ( $P_{\text{rated,c,TRP}}$ ). + +**maximum transmitter TRP:** mean power level measured per RIB during the *transmitter ON period* in a specified reference condition and corresponding to the declared *rated transmitter TRP* ( $P_{\text{rated,t,TRP}}$ ). + +**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 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. + +**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. + +**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 10: The operating band(s) for a BS is declared by the manufacturer according to the designations in TS 38.104 [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 11: 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 RESENS RoAoA:** Is the RoAoA determined by the contour defined by the points at which the achieved EIS is 3dB higher than the achieved EIS in the reference direction assuming that for any AoA, the receiver gain is optimized for that AoA. + +NOTE 12: This contour will be related to the average element/sub-array radiation pattern 3dB beam width. + +**OTA sensitivity directions declaration:** set of manufacturer declarations comprising at least one set of declared minimum EIS values (with *BS channel bandwidth*), and related directions over which the EIS applies. + +NOTE 13: 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 14: 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 base station is declared to radiate at the associated *beam peak direction* during the *transmitter ON period*. + +**rated carrier TRP:** mean power level declared by the manufacturer per carrier, for BS operating in single carrier, multi-carrier, or carrier aggregation configurations that the manufacturer has declared to be available at the RIB during the *transmitter ON period*. + +**rated transmitter TRP:** mean power level declared by the manufacturer, 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 *BS types 1-H*, *BS type 1-O* and *BS types 2-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 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*. + +**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 BS direction setting. + +**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. + +**sub-block:** one contiguous allocated block of spectrum for transmission and reception by the same base station. + +NOTE 15: 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:** 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. + +**total radiated power:** the total power radiated by the antenna. + +NOTE 16: 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. + +**total RF bandwidth:** maximum sum of Base Station RF Bandwidths in all supported *operating bands*. + +**transceiver array boundary:** conducted interface between the transceiver unit array and the composite antenna. + +**transmission bandwidth:** RF Bandwidth of an instantaneous transmission from a UE or BS, measured in resource block units. + +**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 17: 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 | +| $\text{BeW}_\theta$ | The beam width in $\theta$ | +| $\text{BeW}_\phi$ | The beam width in $\phi$ | +| $\text{BeW}_{\theta, \text{REFSENS}}$ | The beamwidth equivalent to the OTA REFSENS RoAoA in the $\theta$ -axis in degrees, applicable for FR1 only | + +| | | +|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $BeW_{\phi,REFSENS}$ | The beamwidth equivalent to the OTA REFSENS RoAoA in the $\phi$ -axis in degrees, applicable for FR1 only | +| $BW_{Channel}$ | BS channel bandwidth | +| $BW_{Channel\_CA}$ | Aggregated BS channel bandwidth , expressed in MHz. $BW_{Channel\_CA} = F_{edge\_high} - F_{edge\_low}$ | +| $BW_{Config}$ | Transmission bandwidth configuration, expressed in MHz, where $BW_{Config} = N_{RB} \times SCS \times 12$ | +| $BW_{Contiguous}$ | Contiguous transmission bandwidth, i.e. BS channel bandwidth for single carrier or aggregated BS channel bandwidth for contiguously aggregated carriers. For non-contiguous operation within a band the term is applied per sub-block. | +| $BW_{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_{max}$ | $f\_offset_{max}$ minus half of the bandwidth of the measuring filter | +| $\Delta F_{Global}$ | Global frequency raster granularity | +| $\Delta f_{OBUE}$ | Maximum offset of the operating band unwanted emissions mask from the downlink operating band edge | +| $\Delta_{FR2\_REFSENS}$ | Offset applied to the FR2 OTA REFSENS depending on the AoA | +| $\Delta f_{OOB}$ | Maximum offset of the out-of-band boundary from the uplink operating band edge | +| $\Delta_{minSENS}$ | Difference between conducted reference sensitivity and $EIS_{minSENS}$ | +| $\Delta_{OTA\_REFSENS}$ | Difference between conducted reference sensitivity and OTA REFSENS | +| $\Delta F_{Raster}$ | Channel raster granularity | +| $\Delta_{sample}$ | The difference between the nominal and extreme power measurements during extreme EIRP testing, $P_{max,sample,nom} - P_{max,sample,ext}$ | +| $\Delta_{SUL}$ | Channel raster offset for SUL | +| $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 BS channel bandwidth | +| $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_C$ | RF reference frequency on the channel raster | +| $F_{C,block,high}$ | $F_C$ of the highest transmitted/received carrier in a sub-block | +| $F_{C,block,low}$ | $F_C$ of the lowest transmitted/received carrier in a sub-block | +| $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_{edge\_low}$ | The lower edge of Aggregated BS channel bandwidth , expressed in MHz. $F_{edge\_low} = F_{C\_low} - F_{offset\_low}$ | +| $F_{edge\_high}$ | The upper edge of Aggregated BS channel bandwidth , expressed in MHz. $F_{edge\_high} = F_{C\_high} + F_{offset\_high}$ | +| $F_{edge,block,low}$ | The lower sub-block edge, where $F_{edge,block,low} = F_{C,block,low} - F_{offset\_low}$ | +| $F_{edge,block,high}$ | The upper sub-block edge, where $F_{edge,block,high} = F_{C,block,high} + F_{offset\_high}$ | +| $F_{offset\_high}$ | Frequency offset from $F_{C\_high}$ to the upper Base Station RF Bandwidth edge , or from $F_{C,block,high}$ to the upper sub-block edge | +| $F_{offset\_low}$ | Frequency offset from $F_{C\_low}$ to the lower Base Station RF Bandwidth edge , or from $F_{C,block,low}$ to the lower sub-block edge | +| $f\_offset$ | Separation between the channel edge frequency and the centre of the measuring filter | +| $f\_offset_{max}$ | The offset to the frequency $\Delta f_{OBUE}$ outside the downlink operating band | +| $F_{REF}$ | RF reference frequency | +| $F_{REF,SUL}$ | RF reference frequency for Supplementary Uplink (SUL) bands | +| $F_{step,X}$ | Frequency steps for the OTA transmitter spurious emissions (Category B) | +| $F_{DL\_low}$ | The lowest frequency of the downlink operating band | +| $F_{DL\_high}$ | The highest frequency of the downlink operating band | +| $F_{UL\_low}$ | The lowest frequency of the uplink operating band | +| $F_{UL\_high}$ | The highest frequency of the uplink operating band | +| $I_{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_{cells}$ | The declared number corresponding to the minimum number of cells that can be transmitted by an BS type I-H in a particular operating band | +| $N_{RB}$ | Transmission bandwidth configuration, expressed in resource blocks | +| $N_{REF}$ | NR Absolute Radio Frequency Channel Number (NR-ARFCN) | + +| | | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $N_{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 | +| $P_{EM,n50,ind}$ | Declared emission level for Band n50 in the band 1518-1559 MHz; ind = a, b | +| $P_{max,c,EIRP}$ | The maximum carrier EIRP when the BS is configured at the maximum rated carrier TRP ( $P_{rated,c,TRP}$ ) | +| $P_{max,c,EIRP, extreme}$ | The maximum carrier EIRP when the BS is configured at the maximum rated carrier TRP ( $P_{rated,c,TRP}$ ) under extreme conditions, either measured directly or calculated | +| $P_{max,c,TRP}$ | Maximum carrier TRP measured at the RIB(s), and corresponding to the declared rated carrier TRP ( $P_{rated,c,TRP}$ ) | +| $P_{max,sample,nom}$ | The measured sample power in extreme conditionals chamber when the BS is configured at the rated carrier TRP ( $P_{rated,c,TRP}$ ), under nominal conditions | +| $P_{max,sample,ext}$ | The measured sample power in extreme conditionals chamber when the BS is configured at the rated carrier TRP ( $P_{rated,c,TRP}$ ), under extreme conditions | +| $P_{rated,c,EIRP}$ | The rated carrier EIRP when the BS is configured at the rated carrier TRP ( $P_{rated,c,TRP}$ ) | +| $P_{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_{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_{rated,c,TRP}$ | Rated carrier TRP declared per RIB | +| $P_{rated,t,TRP}$ | Rated transmitter TRP declared per RIB | +| $P_{REFSENS}$ | Conducted reference Sensitivity power level | +| $SS_{REF}$ | SS block reference frequency position | +| $TRP_{Estimate}$ | Numerically approximated TRP | +| $TT_{OTA}$ | Test tolerance for OTA requirements | +| $W_{gap}$ | Sub-block gap or Inter RF Bandwidth gap size | +| $\theta$ | The angle in the reference coordinate system between the projection of the x/y plane and the radiation vector defined between $-90^\circ$ and $90^\circ$ . $0^\circ$ represents the y/z plane. The angle is aligned with the down-tilt angle | +| $\phi$ | The angle in the reference coordinate system between the x-axis and the projection of the radiation vector onto the x/y plane defined between $-180^\circ$ and $180^\circ$ | + +### 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 | +| ACLR | Adjacent Channel Leakage Ratio | +| ACS | Adjacent Channel Selectivity | +| AoA | Angle of Arrival | +| AWGN | Additive White Gaussian Noise | +| BS | Base Station | +| BW | Bandwidth | +| CA | Carrier Aggregation | +| CACLR | Cumulative ACLR | +| CATR | Compact Antenna Test Range | +| CPE | Common Phase Error | +| CP-OFDM | Cyclic Prefix-OFDM | +| CLTA | Co-Location Test Antenna | +| CW | Continuous Wave | +| DFT-s-OFDM | Discrete Fourier Transform-spread-OFDM | +| DM-RS | Demodulation Reference Signal | +| EUT | Equipment Under Test | +| EIRP | Equivalent Isotropic Radiated Power | +| EIS | Equivalent Isotropic Sensitivity | +| FBW | Fractional Bandwidth | +| FR | Frequency Range | +| GSCN | Global Synchronization Channel Number | +| ICS | In-Channel Selectivity | + +| | | +|----------|------------------------------------------------------------------------| +| ITU-R | Radiocommunication Sector of the International Telecommunication Union | +| LA | Local Area | +| LNA | Low Noise Amplifier | +| MR | Medium Range | +| NR | New Radio | +| NR-ARFCN | NR Absolute Radio Frequency Channel Number | +| OBUE | Operating Band Unwanted Emissions | +| OCC | Orthogonal Covering Code | +| OSDD | OTA Sensitivity Directions Declaration | +| OTA | Over The Air | +| PT-RS | Phase Tracking Reference Signal | +| PWS | Plane Wave Synthesizer | +| RB | Resource Block | +| RDN | Radio Distribution Network | +| REFSENS | Reference Sensitivity | +| RIB | Radiated Interface Boundary | +| RMS | Root Mean Square (value) | +| RS | Reference Signal | +| RV | Redundancy Version | +| RX | Receiver | +| RoAoA | Range of Angles of Arrival | +| SCS | Sub-Carrier Spacing | +| SSB | Synchronization Signal Block | +| TAB | Transceiver Array Boundary | +| TAE | Time Alignment Error | +| TDD | Time Division Duplex | +| TDL | Tapped Delay Line | +| TRP | Total Radiated Power | +| TT | Test Tolerance | +| UCI | Uplink Control Information | +| ZF | Zero Forcing | + +--- + +## 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.141-2 (the present document), i.e. to all radiated tests defined in FR1 for *BS type 1-H*, *BS type 1-O* and radiated tests defined in FR2 for *BS type 2-O*. 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]. 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 BS 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 | +| | Protection of the BS receiver of own or different BS | Co-location | See clause 4.12 | See clause 4.12 | +| | 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 [29]. + +#### 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 [29]. + +**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:
±1.1 dB, $f \leq 3$ GHz
±1.3 dB, $3$ GHz $< f \leq 7.125$ GHz
±1.8 dB for band n96
Extreme condition:
±2.5 dB, $f \leq 3$ GHz
±2.6 dB, $3$ GHz $< f \leq 7.125$ GHz | +| 6.3 OTA base station output power | ±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 7.125$ GHz | +| 6.4.2 OTA RE power control dynamic range | N/A | +| 6.4.3 OTA total power dynamic range | ±0.4 dB | +| 6.5.1 OTA transmitter OFF power | ±3.4 dB, $f \leq 3.0$ GHz
±3.6 dB, $3.0$ GHz $< f \leq 7.125$ GHz(NOTE 1) | +| 6.5.2 OTA transmitter transient period | N/A | +| 6.6.2 OTA frequency error | ±12 Hz | +| 6.6.3 OTA modulation quality | ±1 % | +| 6.6.4 OTA time alignment error | ±25 ns | +| 6.7.2 OTA occupied bandwidth | ±100 kHz, $BW_{\text{Channel}}$ 5 MHz, 10 MHz
±300 kHz, $BW_{\text{Channel}}$ 15 MHz, 20 MHz, 25 MHz, 30 MHz, 35 MHz, 40 MHz, 45 MHz, 50 MHz
±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
±1 dB, $BW \leq 20$ MHz
±1 dB, $BW > 20$ MHz

$3.0$ GHz $< f \leq 7.125$ GHz
±1.2 dB, $BW \leq 20$ MHz
±1.2 dB, $BW > 20$ MHz

Absolute power ±2.2 dB, $f \leq 3.0$ GHz
Absolute power ±2.7 dB, $3.0$ GHz $< f \leq 4.2$ GHz
Absolute power ±2.7 dB, $4.2$ GHz $< f \leq 7.125$ GHz | +| 6.7.4 OTA operating band unwanted emissions | Absolute power ±1.8 dB, $f \leq 3.0$ GHz
Absolute power ±2 dB, $3.0$ GHz $< f \leq 4.2$ GHz
Absolute power ±2 dB, $4.2$ GHz $< f \leq 6.0$ GHz | +| 6.7.5.2 OTA transmitter spurious emissions, mandatory requirements | ±2.3 dB, $30$ MHz $< f \leq 6$ GHz
±4.2 dB, $6$ GHz $< f \leq 26$ GHz | +| 6.7.5.3 OTA transmitter spurious emissions, protection of BS receiver | ±3.1 dB, $f \leq 3$ GHz
±3.3 dB, $3$ GHz $< f \leq 4.2$ GHz
±3.4, $4.2$ GHz $< f \leq 7.125$ GHz(NOTE 1) | +| 6.7.5.4 OTA transmitter spurious emissions, additional spurious emissions requirements | ±2.6 dB, $f \leq 3$ GHz
±3.0, $3$ GHz $< f \leq 4.2$ GHz
±3.5, $4.2$ GHz $< f \leq 6$ GHz | +| 6.7.5.5 OTA transmitter spurious emissions, co-location | ±3.1 dB, $f \leq 3$ GHz
±3.3 dB, $3$ GHz $< f \leq 4.2$ GHz
±3.4, $4.2$ GHz $< f \leq 7.125$ 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.
±3.2 dB, $f \leq 3.0$ GHz
±3.4 dB, $3.0$ GHz $< f \leq 4.2$ GHz
±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 [29] 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 OTA transmitter tests** + +| Clause | Maximum OTA Test System uncertainty | +|---------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 6.2 Radiated transmit power | Normal condition:
$\pm 1.7$ dB (24.25 – 29.5 GHz)
$\pm 2.0$ dB (37 – 43.5 GHz)
$\pm 2.2$ dB (43.5 GHz < $f \leq 48.2$ GHz)
$\pm 3.0$ dB (52.6 GHz $\leq f \leq 71$ GHz)
Extreme condition:
$\pm 3.1$ dB (24.25 – 29.5 GHz)
$\pm 3.3$ dB (37 – 43.5 GHz)
$\pm 3.5$ dB (43.5 GHz < $f \leq 48.2$ GHz)
$\pm 3.9$ dB (52.6 GHz $\leq f \leq 71$ 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.6$ dB (43.5 GHz < $f \leq 48.2$ GHz)
$\pm 3.2$ dB (52.6 GHz $\leq f \leq 71$ GHz) | +| 6.4.2 OTA RE power control dynamic range | N/A | +| 6.4.3 OTA total power dynamic range | $\pm 0.4$ dB | +| 6.5.1 OTA transmitter OFF power | $\pm 2.9$ dB (24.25 – 29.5 GHz)
$\pm 3.3$ dB (37 – 43.5 GHz)
$\pm 3.6$ dB (43.5 GHz < $f \leq 48.2$ GHz)
$\pm 5.6$ dB (52.6 GHz $\leq f \leq 71$ GHz) | +| 6.5.2 OTA transmitter transient period | N/A | +| 6.6.2 OTA frequency error | $\pm 12$ Hz | +| 6.6.3 OTA modulation quality | 1% | +| 6.6.4 OTA time alignment error | $\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)
$\pm 2.8$ dB (43.5 GHz < $f \leq 48.2$ GHz)
$\pm 4.6$ dB (52.6 GHz $\leq f \leq 71$ GHz)

Absolute ACLR:
$\pm 2.7$ dB (24.25 – 29.5 GHz)
$\pm 2.7$ dB (37 – 43.5 GHz)
$\pm 2.9$ dB (43.5 GHz < $f \leq 48.2$ GHz)
$\pm 4.7$ dB (52.6 GHz $\leq f \leq 71$ 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 (43.5 GHz < $f \leq 48.2$ GHz)
$\pm 4.7$ dB (52.6 GHz $\leq f \leq 71$ 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 5.3$ dB, 60 GHz < $f \leq 110$ GHz
$\pm 5.9$ dB, 110 GHz < $f \leq 142$ 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 5.3$ dB, 60 GHz < $f \leq 110$ GHz
$\pm 5.9$ dB, 110 GHz < $f \leq 142$ 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 [29]. + +**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\text{ GHz} < f \leq 4.2$ GHz
$\pm 1.6$ dB, $4.2\text{ GHz} < f \leq 6.0$ GHz
$\pm 1.9$ dB, $6.0\text{ GHz} < f \leq 7.125$ GHz
$\pm 1.9$ dB for band n96 | +| 7.3 OTA reference sensitivity level | $\pm 1.3$ dB, $f \leq 3.0$ GHz
$\pm 1.4$ dB, $3.0\text{ GHz} < f \leq 4.2$ GHz
$\pm 1.6$ dB, $4.2\text{ GHz} < f \leq 6.0$ GHz
$\pm 1.9$ dB, $6.0\text{ GHz} < f \leq 7.125$ 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\text{ GHz} < f \leq 4.2$ GHz
$\pm 2.4$ dB, $4.2\text{ GHz} < f \leq 6.0$ GHz
$\pm 2.8$ dB, $6.0\text{ GHz} < f \leq 7.125$ GHz | +| 7.5.2 In-band blocking (General) | $\pm 1.9$ dB, $f \leq 3.0$ GHz
$\pm 2.2$ dB, $3.0\text{ GHz} < f \leq 4.2$ GHz
$\pm 2.5$ dB, $4.2\text{ GHz} < f \leq 6.0$ GHz
$\pm 2.9$ dB, $6.0\text{ GHz} < f \leq 7.125$ GHz | +| 7.5.2 In-band blocking (Narrowband) | $\pm 1.7$ dB, $f \leq 3.0$ GHz
$\pm 2.1$ dB, $3.0\text{ GHz} < f \leq 4.2$ GHz
$\pm 2.4$ dB, $4.2\text{ 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\text{ GHz} < f_{\text{interferer}} \leq 6.0$ GHz
$\pm 3.5$ dB, $6.0\text{ GHz} < f_{\text{interferer}} \leq 12.75$ GHz

$3\text{ 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\text{ GHz} < f_{\text{interferer}} \leq 6.0$ GHz
$\pm 3.6$ dB, $6.0\text{ GHz} < f_{\text{interferer}} \leq 12.75$ GHz

$4.2\text{ GHz} < f_{\text{wanted}} \leq 7.125$ GHz:
$\pm 2.2$ dB, $f_{\text{interferer}} \leq 3.0$ GHz
$\pm 2.3$ dB, $3.0\text{ GHz} < f_{\text{interferer}} \leq 6.0$ GHz
$\pm 3.6$ dB, $6.0\text{ 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\text{ GHz} < f_{\text{interferer}} \leq 4.2$ GHz
$\pm 3.7$ dB, $4.2\text{ GHz} < f_{\text{interferer}} \leq 6.0$ GHz

$3\text{ 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\text{ GHz} < f_{\text{interferer}} \leq 4.2$ GHz
$\pm 3.7$ dB, $4.2\text{ GHz} < f_{\text{interferer}} \leq 6.0$ GHz

$4.2\text{ 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\text{ GHz} < f_{\text{interferer}} \leq 4.2$ GHz
$\pm 3.8$ dB, $4.2\text{ GHz} < f_{\text{interferer}} \leq 6.0$ GHz

$6.0\text{ GHz} < f \leq 7.125$ GHz:
$\pm 3.6$ dB, $f_{\text{interferer}} \leq 3.0$ GHz
$\pm 3.8$ dB, $3.0\text{ GHz} < f_{\text{interferer}} \leq 4.2$ GHz
$\pm 3.9$ dB, $4.2\text{ GHz} < f_{\text{interferer}} \leq 6.0$ GHz | +| 7.7 OTA receiver spurious emissions | $\pm 2.5$ dB, $30\text{ MHz} \leq f \leq 6.0$ GHz
$\pm 4.2$ dB, $6.0\text{ 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\text{ GHz} < f \leq 4.2$ GHz
$\pm 3.2$ dB, $4.2\text{ GHz} < f \leq 6.0$ GHz
$\pm 3.5$ dB, $6.0\text{ GHz} < f \leq 7.125$ GHz | +| 7.9 OTA in-channel selectivity | $\pm 1.7$ dB, $f \leq 3.0$ GHz
$\pm 2.1$ dB, $3.0\text{ GHz} < f \leq 4.2$ GHz
$\pm 2.4$ dB, $4.2\text{ GHz} < f \leq 6.0$ GHz
$\pm 2.8$ dB, $6.0\text{ GHz} < f \leq 7.125$ 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 [29], 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 OTA receiver tests** + +| Clause | Maximum OTA Test System uncertainty | +|----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 7.3 OTA reference sensitivity level | $\pm 2.4$ dB, $24.25$ GHz $< f \leq 29.5$ GHz
$\pm 2.4$ dB, $37$ GHz $< f \leq 43.5$ GHz
$\pm 3.5$ dB, $43.5$ GHz $< f \leq 48.2$ GHz
$\pm 3.0$ dB, $52.6$ GHz $\leq f \leq 71$ GHz | +| 7.5.1 OTA adjacent channel selectivity | $\pm 3.4$ dB, $24.25$ GHz $< f \leq 29.5$ GHz
$\pm 3.4$ dB, $37$ GHz $< f \leq 43.5$ GHz
$\pm 5.1$ dB, $43.5$ GHz $< f \leq 48.2$ GHz
$\pm 4.0$ dB, $52.6$ GHz $\leq f \leq 71$ GHz | +| 7.5.2 In-band blocking (General) | $\pm 3.4$ dB, $24.25$ GHz $< f \leq 29.5$ GHz
$\pm 3.4$ dB, $37$ GHz $< f \leq 43.5$ GHz
$\pm 5.1$ dB, $43.5$ GHz $< f \leq 48.2$ GHz
$\pm 4.0$ dB, $52.6$ GHz $\leq f \leq 71$ GHz | +| 7.6 OTA out-of-band blocking | $\pm 3.6$ dB, $24.25$ GHz $< f \leq 43.5$ GHz
$\pm 4.5$ dB, $43.5$ GHz $< f \leq 48.2$ GHz
$\pm 4.0$ dB, $52.6$ GHz $\leq f \leq 142$ GHz | +| 7.7 OTA receiver spurious emissions | $\pm 2.5$ 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 5.3$ dB, $60$ GHz $< f \leq 110$ GHz
$\pm 5.9$ dB, $110$ GHz $< f \leq 142$ GHz | +| 7.8 OTA receiver intermodulation | $\pm 3.9$ dB, $24.25$ GHz $< f \leq 29.5$ GHz
$\pm 3.9$ dB, $37$ GHz $< f \leq 43.5$ GHz
$\pm 5.4$ dB, $43.5$ GHz $< f \leq 48.2$ GHz
$\pm 4.5$ dB, $52.6$ GHz $\leq f \leq 71$ GHz | +| 7.9 OTA in-channel selectivity | $\pm 3.4$ dB, $24.25$ GHz $< f \leq 29.5$ GHz
$\pm 3.4$ dB, $37$ GHz $< f \leq 43.5$ GHz
$\pm 5.1$ dB, $43.5$ GHz $< f \leq 48.2$ GHz
$\pm 4.0$ dB, $52.6$ GHz $\leq f \leq 71$ GHz | +| 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 OTA Test System uncertainty for FR1 OTA performance requirements** + +| Clause | Maximum OTA Test System uncertainty | Derivation of OTA Test System uncertainty | +|---------------------------------------------------------------------------------------------------|-------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 8 PUSCH, PUCCH, PRACH with single antenna port and fading channel | $\pm 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:
$\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$ dB
Fading profile power uncertainty $\pm 0.5$ dB | +| 8 PUSCH, PRACH with single antenna port and AWGN | $\pm 0.3$ dB | Signal-to-noise ratio uncertainty $\pm 0.3$ dB | +| 8 PUSCH with two antenna port and fading channel | $\pm 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:
$\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$ dB
Fading profile power uncertainty $\pm 0.7$ dB for MIMO | +| NOTE: Test system uncertainty values are applicable for normal condition unless otherwise stated. | | | + +**Table 4.1.2.4-2: Maximum OTA Test System uncertainty for FR2 OTA performance requirements** + +| Clause | Maximum OTA Test System uncertainty | Derivation of OTA Test System uncertainty | +|-------------------------------------------------------------------|-------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 8 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 PRACH with single antenna port and AWGN | ± 0.3 dB | Signal-to-noise ratio uncertainty ±0.3 dB | +| 8 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 | + +NOTE: Test system uncertainty values are applicable for normal condition unless otherwise stated. + +### 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 [4]. + +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 this specification. + +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 *BS type 1-H*, *BS type 1-O* and *BS 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 *BS 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 *BS type 1-H* are tested in the far field (Fraunhofer) region. + +General architecture and reference points of *BS type 1-H*, *BS type 1-O* and *BS type 2-O* are presented on the following figures 4.2-1 – 4.2-2. + +![Figure 4.2-1: General architecture of BS type 1-H. The diagram shows a 'Transceiver unit array (TRXUA) 1 to M' on the left, separated by a dashed line labeled 'Transceiver array boundary'. To the right of this boundary are 'K' connectors, labeled #1, #2, ..., #K, which are part of the 'Composite antenna'. An arrow points to one of these connectors, labeled 'Transceiver array boundary connector (TAB)'. The 'Composite antenna' is further divided by a dashed line labeled 'Radiated interface boundary (RIB)' into two sub-components: 'Radio Distribution Network (RDN)' and 'Antenna Array (AA)'.](4ff00a489baaa34a0c01070de1d613db_img.jpg) + +Figure 4.2-1: General architecture of BS type 1-H. The diagram shows a 'Transceiver unit array (TRXUA) 1 to M' on the left, separated by a dashed line labeled 'Transceiver array boundary'. To the right of this boundary are 'K' connectors, labeled #1, #2, ..., #K, which are part of the 'Composite antenna'. An arrow points to one of these connectors, labeled 'Transceiver array boundary connector (TAB)'. The 'Composite antenna' is further divided by a dashed line labeled 'Radiated interface boundary (RIB)' into two sub-components: 'Radio Distribution Network (RDN)' and 'Antenna Array (AA)'. + +**Figure 4.2-1: General architecture of *BS type 1-H*** + +This specification details only radiated test requirements and hence only requires the radiated reference points. + +![Figure 4.2-2: General architecture of BS type 1-O and BS type 2-O. The diagram shows a 'Transceiver unit array (TRXUA) 1 to P' on the left. To its right is a dashed line representing the 'Radiated interface boundary (RIB)'. Further right is a dashed box labeled 'Composite antenna', which contains two sub-components: 'Radio Distribution Network (RDN)' and 'Antenna Array (AA)'.](f1091147d93cee4dfa88498610e395a7_img.jpg) + +Figure 4.2-2: General architecture of BS type 1-O and BS type 2-O. The diagram shows a 'Transceiver unit array (TRXUA) 1 to P' on the left. To its right is a dashed line representing the 'Radiated interface boundary (RIB)'. Further right is a dashed box labeled 'Composite antenna', which contains two sub-components: 'Radio Distribution Network (RDN)' and 'Antenna Array (AA)'. + +**Figure 4.2-2: General architecture of *BS type 1-O* and *BS 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 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. The associated deployment scenarios and definitions of BS classes are exactly the same for BS with and without connectors. + +BS classes for *BS type 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. + +BS classes for *BS type 1-O* and *BS type 2-O* are defined as indicated below: + +- Wide Area Base Stations are characterised by requirements derived from Macro Cell scenarios with a BS to UE minimum distance along the ground equal to 35 m. +- Medium Range Base Stations are characterised by requirements derived from Micro Cell scenarios with a BS to UE minimum distance along the ground equal to 5 m. +- Local Area Base Stations are characterised by requirements derived from Pico Cell scenarios with a BS to UE minimum distance along the ground equal to 2 m. + +The manufacturer shall declare the intended class of the BS under test. + +## 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 | Operating bands | Some NR operating bands may be applied regionally. | +| 6.3.1 | OTA base station output power | Additional output power limits may be applied regionally. | +| 6.7.2 | OTA occupied bandwidth | The requirement may be applied regionally. There may also be regional requirements to declare the occupied bandwidth according to the definition in present specification. | +| 6.7.4 | OTA operating band unwanted emissions | Category A or Category B operating band unwanted emission limits may be applied regionally. | +| 6.7.4.5.1.6.1 | OTA operating band unwanted emissions Limits in FCC Title 47 | The BS may have to comply with the applicable emission limits established by FCC Title 47, when deployed in regions where those limits are applied, and under the conditions declared by the manufacturer. | +| 6.7.4.5.1.6.2 | OTA operating band unwanted emissions 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.7.4.5.1.6.3 | 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.7.5.2 | General OTA 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-O specified as the basic limit + X (dB) are applicable, unless stated differently in regional regulation. | +| 6.7.5.4 | Additional OTA transmitter spurious emissions | These requirements may be applied for the protection of system operating in frequency ranges other than the BS operating band. | +| 6.8.5.1 | OTA 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.8.5.2 | Additional OTA 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.7.5 | OTA receiver spurious emissions | The emission limits for BS type 1-O specified as the basic limit + X (dB) are applicable, unless stated differently in regional regulation. Additional limits for BS type 2-O may apply regionally. | + +## 4.5 BS 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 radiated interface boundary for an NR BS.](9252ccfbbe9e34cb108f0060f2b563f1_img.jpg) + +This diagram illustrates the transmitter test interfaces for an NR BS. The NR BS is shown as a dashed box containing three main components: a 'Transceiver unit array' on the left, a 'Radio Distribution Network (RDN)' in the center, and an 'Antenna Array (AA)' on the right. The RDN and AA are grouped together as a 'Composite antenna'. A dashed line labeled 'Radiated interface boundary' is positioned to the right of the antenna array. A large arrow points from the antenna array, across the boundary, to a 'Measurement equipment' block which is connected to an antenna symbol. + +Diagram of transmitter test interfaces showing the radiated interface boundary for an NR BS. + +**Figure 4.5.1-1: Transmitter test interfaces** + +![Diagram of transmitter test interfaces for co-location concept, showing top and front views.](e05122559f56af5699789b7118d8fe87_img.jpg) + +This diagram shows the transmitter test interfaces for the co-location concept. It is divided into two parts. The top part, labeled 'Top view', shows a 'Measurement equipment' block connected to a 'Co-location reference antenna' (a dashed rectangle). An arrow points from the bottom part of the diagram up to this reference antenna. The bottom part shows the NR BS (dashed box) with its internal components: 'Transceiver unit array', 'Radio Distribution Network (RDN)', and 'Antenna Array (AA)' (grouped as 'Composite antenna'). A large arrow points from the antenna array to a 'Test antenna' (antenna symbol) which is connected to a 'Measurement equipment' block. + +Diagram of transmitter test interfaces for co-location concept, showing top and front views. + +**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 interfaces for a standard NR BS. The NR BS is shown as a dashed box containing a 'Transceiver unit array' and a 'Composite antenna'. The 'Composite antenna' is further divided into 'Radio Distribution Network (RDN)' and 'Antenna Array (AA)'. To the right, a 'Measurement equipment' block is connected to an antenna, with a large arrow pointing towards the 'Antenna Array (AA)' of the composite antenna.](8269648391c59363ea61243864a2adf7_img.jpg) + +Diagram of receiver test interfaces for a standard NR BS. The NR BS is shown as a dashed box containing a 'Transceiver unit array' and a 'Composite antenna'. The 'Composite antenna' is further divided into 'Radio Distribution Network (RDN)' and 'Antenna Array (AA)'. To the right, a 'Measurement equipment' block is connected to an antenna, with a large arrow pointing towards the 'Antenna Array (AA)' of the composite antenna. + +**Figure 4.5.2-1: Receiver test interfaces** + +![Diagram of receiver test interfaces for the co-location concept. At the top, a 'Top view' shows 'Measurement equipment' connected to a 'Co-location reference antenna'. A large downward arrow leads to a diagram of the NR BS, which contains a 'Transceiver unit array' and a 'Composite antenna' (divided into 'RDN' and 'AA'). To the right of the AA, a 'Test antenna' connected to 'Measurement equipment' has a large arrow pointing towards it.](9a14684f8ae1345c6efea6f5994c730c_img.jpg) + +Top view + +Diagram of receiver test interfaces for the co-location concept. At the top, a 'Top view' shows 'Measurement equipment' connected to a 'Co-location reference antenna'. A large downward arrow leads to a diagram of the NR BS, which contains a 'Transceiver unit array' and a 'Composite antenna' (divided into 'RDN' and 'AA'). To the right of the AA, a 'Test antenna' connected to 'Measurement equipment' has a large arrow pointing towards it. + +**Figure 4.5.2-2: Receiver test interfaces for co-location concept** + +### 4.5.3 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. + +#### 4.5.4 BS with integrated Iuant BS modem + +Unless otherwise stated, for the tests in the present document, the integrated Iuant BS modem shall be switched OFF. + +### 4.6 Manufacturer's declarations + +The following BS manufacturer's declarations listed in table 4.6-1, when applicable to the BS under test, are required to be provided by the manufacturer for radiated requirements testing for *BS type 1-H*, *BS type 1-O* and *BS type 2-O*. + +For the *BS type 1-H* declarations required for the conducted requirements testing, refer to TS 38.141-1 [3], clause 4.6. + +**Table 4.6-1 Manufacturers declarations for BS type 1-H, BS type 1-O and BS type 2-O radiated test requirements** + +| Declaration identifier | Declaration | Description | Applicability (Note 1) | | | +|------------------------|-------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------|-------------| +| | | | BS type 1-H (Note 2) | BS type 1-O | BS type 2-O | +| D.1 | Coordinate system reference point | Location of coordinated system reference point in reference to an identifiable physical feature of the BS enclosure. | x | x | x | +| D.2 | Coordinate system orientation | Orientation of the coordinate system in reference to an identifiable physical feature of the BS 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 BS is intended to produce shall be considered, including beams that during operation may be identified by any kind of cell or UE specific reference signals, with the exception of any type of beam that is created from a group of transmitters that are not all phase synchronised.

(Note 3)

| x | x | x | +| D.4 | Operating bands and frequency ranges |

List of NR operating band(s) supported by the BS and if applicable, frequency range(s) within the operating band(s) that the BS can operate in. Supported bands declared for every beam (D.3).

(Note 4)

| c | x | x | +| D.5 | BS requirements set | Declaration of one of the NR base station requirement's set as defined for BS type 1-H, BS type 1-O, or BS type 2-O. | c | x | x | +| D.6 | BS class | Declared as Wide Area BS, Medium Range BS, or Local Area BS. | c | x | x | +| D.7 | BS channel band width and SCS support | BS 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 | + +| Declaration identifier | Declaration | Description | Applicability
(Note 1) | | | +|------------------------|-------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|---|-----| +| | | | | | | +| D.10 | OTA peak directions set maximum steering direction(s) |

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

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

The maximum steering direction(s) may coincide with the reference beam centre direction. Declared for every beam (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, 20)

| 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 | +| 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 BS 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 Base Station RF Bandwidth |

Maximum Base Station RF Bandwidth in the operating band, declared for each supported operating band (D.4). (Note 15)

| c | x | x | + +| Declaration identifier | Declaration | Description | Applicability
(Note 1) | | | +|------------------------|------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|-----|-----| +| | | | c | x | n/a | +| 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 BS 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 BS channel bandwidth and SCS | The BS 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 | +| 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 ( $EIS_{REFSENS\_50M}$ ) | The $EIS_{REFSENS\_50M}$ level applicable in the OTA REFSSENS RoAoA, (used as a basis for the derivation of the FR2 $EIS_{REFSENS}$ for other channel bandwidths supported by BS). (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 | +| 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 | + +| Declaration identifier | Declaration | Description | Applicability
(Note 1) | | | +|------------------------|----------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|---|-----| +| | | | | | | +| 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 BS power, $P_{\text{rated,c,TRP}}$ | $P_{\text{rated,c,TRP}}$ is declared as TRP OTA power per carrier, declared per supported operating band. (Note 12, 14, 18, 20) | n/a | x | x | +| D.38 | Rated transmitter TRP, $P_{\text{rated,t,TRP}}$ | Rated total radiated output power. Declared per supported operating band . (Note 12, 14, 18, 20) | 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 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]. | c | x | x | +| D.41 | 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.7.4 apply. (Note 16, Note 19) | c | x | x | +| D.42 | 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 operating band are deployed. | c | x | x | +| D.43 | 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 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 | BS capability to operate with a single carrier (only) or multiple carriers. Declared per supported operating band, per RIB. (Note 17) | 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 | + +| Declaration identifier | Declaration | Description | Applicability
(Note 1) | | | +|------------------------|-------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|-----|-----| +| | | | c | x | n/a | +| 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 a BS 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 is 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). | 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 BS. | c | x | n/a | +| D.53 | OTA REFSENS RoAoA | Range of angles of arrival associated with the OTA REFSENS. | n/a | x | x | +| D.54 | OTA REFSENS receiver target reference direction | Reference direction inside the OTA REFSENS RoAoA (D.53). | n/a | x | x | +| D.55 | OTA REFSENS conformance test directions | The following four OTA REFSENS conformance test directions shall be declared:
1) The direction determined by the maximum $\phi$ value achievable inside the OTA REFSENS RoAoA, while $\theta$ value being the closest possible to the OTA REFSENS receiver target reference direction.
2) The direction determined by the minimum $\phi$ value achievable inside the OTA REFSENS RoAoA, while $\theta$ value being the closest possible to the OTA REFSENS receiver target reference direction.
3) The direction determined by the maximum $\theta$ value achievable inside the OTA REFSENS RoAoA, while $\phi$ value being the closest possible to the OTA REFSENS receiver target reference direction.
4) The direction determined by the minimum $\theta$ value achievable inside the OTA REFSENS RoAoA, while $\phi$ value being the closest possible to the OTA REFSENS 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).
(Note 12, 13, 14, 15, 18, 20) | 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).
(Note 12, 13, 14, 15, 18, 20) | 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.100 | PUSCH mapping type | Declaration of the supported PUSCH mapping type for FR1 as specified in TS 38.211 [20], i.e., type A, type B or both. | c | x | n/a | +| D.101 | PUSCH additional DM-RS positions | Declaration of the supported additional DM-RS position(s) for FR2, i.e., pos0, pos1, or both. | n/a | n/a | x | +| D.102 | PUCCH format | Declaration of the supported PUCCH format(s) as specified in TS 38.211 [20], i.e., format 0, format 1, format 2, format 3, format 4. | c | x | x | +| D.103 | PRACH format and SCS | Declaration of the supported PRACH format(s) as specified in TS 38.211 [20], 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 [20], i.e.:
  • - For BS type 1-O: 15 kHz, 30 kHz or both.
  • - For BS type 2-O: 60 kHz, 120 kHz or both.
| c | 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. | c | 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. | c | x | x | +| D.106 | PUSCH PT-RS | 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 | 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 | + +| Declaration identifier | Declaration | Description | Applicability
(Note 1) | | | +|------------------------|------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|-----|-----| +| | | | c | x | x | +| D.109 | High speed train | Declaration of high speed train scenario support, i.e. HST support or no HST support | c | x | x | +| D.110 | 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.109. | c | x | n/a | +| D.111 | 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.109. | c | x | x | +| D.112 | Interlaced formats | Declaration of support of interlaced PUSCH and PUCCH formats, i.e. interlaced format support or no interlaced format support. | c | x | n/a | +| D.113 | 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. | c | x | n/a | +| D.114 | CG-UCI | Declaration of support of GC-UCI multiplexed on PUSCH as specified in TS 38.211 [17]. | c | x | n/a | +| D.115 | 2-step RA | Declaration of support of 2-step RA type. | c | x | x | +| D.116 | PUSCH 256QAM | Declaration of PUSCH 256QAM support | c | x | n/a | +| D.117 | Additional DM-RS for FR2 high speed train | Declaration of supported additional DM-RS position(s) for FR2 high speed train scenario for PUSCH and UL timing adjustment, i.e., pos0, pos1, pos2, or any combination | n/a | n/a | x | +| D.118 | PUCCH sub-slot based repetition formats | Declaration of PUCCH sub-slot based repetition formats. | c | x | n/a | +| D.119 | PUSCH TB over multi-slots | BS support TBoMS over physical consecutive UL slots | c | x | x | +| D.120 | PUSCH TB over multi-slots | BS support TBoMS over physical non-consecutive UL slots | c | x | x | +| D.121 | 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. {15 kHz, 30 kHz, 60 kHz 120 kHz} | c | x | x | +| D.122 | 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 | c | x | x | +| D.123 | MCS index table 3 | Declaration of support MCS index table 3 as specified in TS 38.214 [18]. | c | x | n/a | +| D.124 | PUSCH repetition type A | Declaration of support PUSCH repetition type A | c | x | x | + +| Declaration identifier | Declaration | Description | Applicability (Note 1) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------|------------------------| +| NOTE 1: Manufacturer declarations applicable per BS requirement set were marked as "x". Manufacturer declarations not applicable per BS requirement set were marked as "n/a". | | | | +| NOTE 2: For BS type 1-H, the only radiated declarations are related to EIRP and EIS requirements. For BS type 1-H declarations required for the conducted requirements testing, refer to TS 38.141-1 [3]. For declarations marked as 'c', related conducted declarations in TS 38.141-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 BS type 1-H or BS 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 BS has to support 50 MHz channel bandwidth. | | | | +| NOTE 8: Not applicable for BS 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 a BS 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 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 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: If BS is declared to support Band n20 (D.4), 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 17: In case of BS type 1-H, this declaration applies per TAB connector. | | | | +| NOTE 18: If a BS 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: If BS is declared to support Band n24 (D.4), 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 20: 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 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 *BS channel bandwidth* and subcarrier spacing used to build NR 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 NR TCs for BS type 1-H and BS type 1-O** + +| Operating band characteristics | | $F_{DL\_high} - F_{DL\_low} < 100$ MHz | $F_{DL\_high} - F_{DL\_low} \geq 100$ MHz | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|-------------------------------------------------------------------------|-------------------------------------------| +| TC signal characteristics | $BW_{channel}$ | 5 MHz (Note) | 20 MHz (Note) | +| | Subcarrier spacing | Smallest supported subcarrier spacing declared per operating band (D.7) | | +| NOTE: If this BS channel bandwidth is not supported, the narrowest supported BS channel bandwidth declared per operating band (D.7) shall be used. | | | | + +**Table 4.7.2.1-2: Signal to be used to build NR TCs for BS type 2-O** + +| Operating band characteristics | | $F_{DL\_high} - F_{DL\_low} \leq 3250$ MHz | $3250 < F_{DL\_high} - F_{DL\_low} \leq 14000$ MHz | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|-------------------------------------------------------------------------|----------------------------------------------------|--|--| +| TC signal characteristics | $BW_{channel}$ | 100 MHz (Note 1, Note 2) | 400 MHz (Note 1, Note 2, Note 3) | | | +| | Subcarrier spacing | Smallest supported subcarrier spacing declared per operating band (D.7) | | | | +| NOTE 1: BS vendor can decide to test with 50 MHz BS channel bandwidth and smallest supported SCS declared per operating band (D.7) instead of 100 MHz BS channel bandwidth in certain regions, where spectrum allocation and regulation require testing with 50 MHz. | | | | | | +| NOTE 2: If this BS channel bandwidth is not supported, the narrowest supported BS channel bandwidth declared per operating band (D.7) shall be used. | | | | | | +| NOTE 3: For FR2-2 only NRTC1 and NRTC2 are applicable. | | | | | | + +### 4.7.2.2 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.2.2.1 NRTC1 generation + +NRTC1 shall be constructed on a per band basis using the following method: + +- The *Base Station RF Bandwidth* of each supported operating band shall be the declared maximum radiated *Base Station RF Bandwidth* for contiguous operation (D.17). +- Select the carrier to be tested according to 4.7.2.1 and place it adjacent to the lower *Base Station RF Bandwidth edge*. Place same signal adjacent to the upper *Base Station RF Bandwidth edge*. +- For transmitter tests, select as many carriers (according to 4.7.2.1) that the beam supports within a band and that fit in the rest of the declared maximum *Base Station RF Bandwidth*. Place the carriers adjacent to each other starting from the upper *Base Station RF Bandwidth edge*. The nominal carrier spacing defined in TS 38.104 [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 NRTC1 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 NRTC2: Contiguous CA occupied bandwidth + +NRTC2 in this clause is used to test CA occupied bandwidth. + +##### 4.7.2.3.1 NRTC2 generation + +NRTC2 shall be constructed on a per band basis using the following method: + +- Of all component carrier combinations supported by the beam, those which have smallest or largest sum of channel bandwidths of component carrier, shall be tested. Of all component carrier combinations which have smallest or largest sum of channel bandwidth of component carriers supported by the BS, only one combination having largest sum and one combination having smallest sum shall be tested irrespective of the number of component carriers. +- Of all component carrier combinations which have same sum of channel 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 *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 declared per *operating band* (D.7) 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 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.104 [2] clause 5.4.1 shall apply. + +##### 4.7.2.3.2 NRTC2 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 NRTC3: Non-contiguous spectrum operation + +The purpose of NRTC3 is to test NR multicarrier non-contiguous aspects. + +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.2.4.1 NRTC3 generation + +NRTC3 is constructed on a per band basis using the following method: + +- The *Base Station RF Bandwidth* of each supported operating band shall be the declared maximum radiated *Base Station RF Bandwidth* for non-contiguous operation (D.17). The *Base Station RF Bandwidth* consists of one sub-block gap and two sub-blocks located at the edges of the declared maximum radiated *Base Station RF Bandwidth* for non-contiguous operation (D.17). +- Select the carrier to be tested according to 4.7.2.1. Place it adjacent to the upper *Base Station RF Bandwidth edge* and another similar carrier adjacent to the lower *Base Station RF Bandwidth edge*. +- 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 plus two times the *channel bandwidth* used in the previous step and the beam supports at least 4 carriers, place a NR carrier of this *channel bandwidth* 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.2.4.2 NRTC3 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 NRTC4: Multi-band test configuration for full carrier allocation + +The purpose of NRTC4 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 NRTC4 generation + +NRTC4 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 *Base Station RF Bandwidth* of each supported operating band shall be the declared maximum radiated *Base Station 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 *Base Station RF Bandwidth*, if possible. +- The allocated *Base Station RF Bandwidth* of the outermost bands shall be located at the outermost edges of the declared maximum radiated *Radio Bandwidth* (D.18). +- 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 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 *base station RF bandwidths* of each of the supported operating bands is greater than the declared *total RF bandwidth* $BW_{\text{tot}}$ (D.19) of transmitter and receiver for the declared band combinations of the BS, then repeat the steps above for test configurations where the *Base Station RF Bandwidth* of one of the operating band shall be reduced so that the declared *total RF bandwidth* is not exceeded and vice versa. + +- If the sum of the maximum number of supported 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 NRTC4 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 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 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.2.6.1 NRTC5 generation + +NRTC5 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 *Base Station RF Bandwidth* of each supported operating band shall be the declared maximum radiated *Base Station 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 NRTC3, where the declared parameters for multi-band operation shall apply. Narrowest supported *BS 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 *base station RF bandwidths* of each of the supported *operating bands* is greater than the declared *total RF bandwidth* $BW_{\text{tot}}$ (D.19) of transmitter and receiver for the declared band combinations of the BS, then repeat the steps above for test configurations where the *Base Station RF Bandwidth* of one of the *operating band* shall be reduced so that the declared *total RF bandwidth* $BW_{\text{tot}}$ of the *operating band* with multi-band dependencies (D.18) is not exceeded and vice versa. + +##### 4.7.2.6.2 NRTC5 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 BS 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** + +| Requirement | Requirement set | | | +|--------------------------------------|-----------------|-------------|-------------| +| | BS type 1-H | BS type 1-O | BS type 2-O | +| Radiated transmit power | 6.2 | 6.2 | 6.2 | +| OTA base station output power | NA | 6.3 | 6.3 | +| OTA output power dynamics | | 6.4 | 6.4 | +| OTA transmit ON/OFF power | | 6.5 | 6.5 | +| OTA transmitted signal quality | | 6.6 | 6.6 | +| OTA occupied bandwidth | | 6.7.2 | 6.7.2 | +| OTA ACLR | | 6.7.3 | 6.7.3 | +| OTA out-of-band emission | | 6.7.4 | 6.7.4 | +| OTA transmitter spurious emission | | 6.7.5 | 6.7.5 | +| OTA transmitter intermodulation | | 6.8 | NA | +| OTA sensitivity | 7.2 | 7.2 | NA | +| OTA reference sensitivity level | NA | 7.3 | 7.3 | +| OTA dynamic range | | 7.4 | NA | +| OTA in-band selectivity and blocking | | 7.5 | 7.5 | +| OTA out-of-band blocking | | 7.6 | 7.6 | +| OTA receiver spurious emission | | 7.7 | 7.7 | +| OTA receiver intermodulation | | 7.8 | 7.8 | +| OTA in-channel selectivity | | 7.9 | 7.9 | +| Radiated performance requirements | | 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 a BS 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. + +Unless otherwise stated, single carrier configuration (SC) tests shall be performed using signal with narrowest supported *BS 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*** + +| BS test case | Contiguous spectrum capable BS | C and NC capable BS with identical parameters | C and NC capable BS with different parameters | +|--------------------------------------------------------|------------------------------------|-----------------------------------------------|-----------------------------------------------| +| Radiated transmit power | NRTC1 | NRTC1 | NRTC1, NRTC3 | +| OTA base station maximum output power | NRTC1 | NRTC1 | NRTC1, NRTC3 | +| OTA RE Power control dynamic range | 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 for NR TDD BS) | NRTC1 | NRTC1 | NRTC1, NRTC3 | +| OTA frequency error | Tested with Error Vector Magnitude | Tested with Error Vector Magnitude | Tested with Error Vector Magnitude | +| OTA error Vector Magnitude | NRTC1 | NRTC1 | NRTC1, NRTC3 | +| OTA time alignment error | NRTC1 | NRTC1 | NRTC1, NRTC3 | +| OTA Occupied bandwidth | SC, NRTC2 (Note 1) | SC, NRTC2 (Note 1) | SC, NRTC2 (Note 1) | +| OTA ACLR | NRTC1 | NRTC1, NRTC3 | NRTC1, NRTC3 | +| OTA CACLR | - | NRTC3 | NRTC3 | +| OTA operating band unwanted emissions | NRTC1, SC (Note 2) | NRTC1, NRTC3, SC (Note 2) | NRTC1, NRTC3, SC (Note 2) | +| OTA transmitter spurious emissions | NRTC1 | NRTC3 | NRTC1, NRTC3 | +| OTA transmitter intermodulation | NRTC1 | NRTC1, NRTC3 | NRTC1, NRTC3 | +| OTA sensitivity | SC | SC | SC | +| OTA reference sensitivity level | SC | SC | SC | +| OTA dynamic range | SC | SC | SC | +| OTA adjacent channel selectivity | NRTC1 | NRTC3 | NRTC1, NRTC3 | +| In-band blocking | NRTC1 | NRTC3 | NRTC1, NRTC3 | +| OTA out-of-band blocking | NRTC1 | NRTC3 | NRTC1, NRTC3 | +| OTA receiver spurious emissions | NRTC1 | NRTC3 | NRTC1, NRTC3 | +| OTA receiver intermodulation | NRTC1 | NRTC3 | NRTC1, NRTC3 | +| OTA 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 subcarrier spacing. + +#### 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. + +Unless otherwise stated, single carrier configuration (SC) tests shall be performed using signal with narrowest supported BS 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 BS type 2-O. + +**Table 4.8.3-1: Test configuration for a *multi-band RIB*** + +| BS test case | Test configuration | +|--------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------| +| Radiated transmit power | NRTC1/3 (Note 1), NRTC4 | +| OTA base station maximum output power | NRTC1/3 (Note 1), NRTC4 | +| OTA RE power control dynamic range | Tested with Error Vector Magnitude | +| OTA total power dynamic range | SC | +| OTA transmit ON/OFF power (only applied for NR TDD BS) | NRTC4 | +| OTA frequency error | Tested with Error Vector Magnitude | +| OTA Error Vector Magnitude | NRTC1/3 (Note 1), NRTC4 | +| OTA time alignment error | NRTC1/3 (Note 1), NRTC5 (Note 2) | +| OTA occupied bandwidth | SC, NRTC2 (Note 3) | +| OTA ACLR | NRTC1/3 (Note 1), NRTC5 (Note 4) | +| OTA CACLR | NRTC3 (Note 1), NRTC5 (Note 4) | +| OTA operating band unwanted emissions | NRTC1/3 (Note 1), NRTC5, SC (Note 5) | +| OTA transmitter spurious emissions | NRTC1/3 (Note 1), NRTC5 | +| OTA transmitter intermodulation | NRTC1/3 (Note 1) | +| OTA sensitivity | SC | +| OTA reference sensitivity level | SC | +| OTA dynamic range | SC | +| OTA adjacent channel selectivity | NRTC5 | +| In-band blocking | NRTC5 | +| OTA out-of-band blocking | NRTC5 | +| OTA receiver spurious emissions | NRTC1/3 (Note 1), NRTC5 | +| OTA receiver intermodulation | NRTC5 | +| OTA in-channel selectivity | 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: | OBUE SC shall be tested using the widest supported channel bandwidth and the highest supported sub-carrier spacing. | + +#### 4.8.4 Additional conformance + +For a *BS type 1-H* additionally conforming to TS 37.145-2 [30], conformance to some of the RF requirements in the present document can be demonstrated through the corresponding requirements in TS 37.145-2 [30] as listed in Table 4.8.4-1. + +**Table 4.8.4-1: Alternative RF test requirements for a BS additionally conforming to TS 37.145-2 [30] for *BS type 1-H*** + +| RF requirement | Clause in the present document | Alternative clause in TS 37.145-2 [30] | +|-------------------------|---------------------------------------|-----------------------------------------------| +| Radiated transmit power | 6.2.5 | 6.2.5 | +| OTA sensitivity | 7.2.5.2 | 7.2.5.5 | + +For a *BS type 1-O* additionally conforming to TS 37.145-2 [30], conformance to some of the RF requirements in the present document can be demonstrated through the corresponding requirements in TS 37.145-2 [30] as listed in Table 4.8.4-2. + +**Table 4.8.4-2: Alternative RF test requirements for a BS additionally conforming to TS 37.145-2 [30] for BS type 1-O** + +| RF requirement | Clause in the present document | Alternative clause in TS 37.145-2 [30] | +|---------------------------------------|--------------------------------------------|--------------------------------------------| +| Radiated transmit power | 6.2.5 | 6.2.5 | +| OTA base station output power | 6.3.5.1 | 6.3.2.5 | +| OTA transmit ON/OFF power | 6.5 | 6.5 | +| OTA Unwanted emissions | | | +| OTA transmitter spurious emission | 6.7.5.2.5, 6.7.5.3.5, 6.7.5.4.5, 6.7.5.5.5 | 6.7.6.2.5, 6.7.6.3.5, 6.7.6.4.5, 6.7.6.5.5 | +| OTA Operating band unwanted emissions | 6.7.4.5.1 | 6.7.5.5 (except for 6.7.5.5.5) | +| OTA Transmitter intermodulation | 6.8.5 | 6.8.5.1 | +| OTA sensitivity | 7.2.5.2 | 7.2.5.5 | +| OTA reference sensitivity level | 7.3.5.2 | 7.3.5.4 | +| OTA Narrowband blocking | 7.5.2.5.2 | 7.5.5.1.2 | +| OTA Blocking | 7.5.2.5.2 | 7.5.5.1.1 | +| OTA Out-of-band blocking | 7.6.5.1.1 | 7.6.2.5.1 | +| Co-location with other base stations | 7.6.5.1.2 | 7.6.3.5.1 | +| OTA Receiver spurious emissions | 7.7.5.1 | 7.7.5 | +| OTA Intermodulation | 7.8.5.1 | 7.8.5.1.1 | +| OTA Narrowband intermodulation | 7.8.5.1 | 7.8.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 BRFBW (bottom), MRFBW (middle) and TRFBW (top). + +Unless otherwise stated, the test shall be performed at BRFBW, MRFBW and TRFBW defined as following: + +- BRFBW: maximum *Base Station RF Bandwidth* located at the bottom of the supported frequency range in the operating band. +- MRFBW: maximum *Base Station RF Bandwidth* located in the middle of the supported frequency range in the operating band. +- TRFBW: maximum *Base Station RF Bandwidth* located at the top of the supported frequency range in the operating band. + +For a BS capable of multi-band operation and capable of dual-band operation, unless otherwise stated, the test shall be performed at BRFBW\_TRFBW and B'RFBW\_TRFBW defined as following: + +- BRFBW\_TRFBW: the *Base Station RF Bandwidths* located at the bottom of the supported frequency range in the lower operating band and at the highest possible simultaneous frequency position, within the maximum *Radio Bandwidth*, in the upper operating band. +- B'RFBW\_TRFBW: the *Base Station RF Bandwidths* located at the top of the supported frequency range in the upper operating band and at the lowest possible simultaneous frequency position, within the maximum *Radio Bandwidth*, in the lower operating band. + +NOTE: $B_{\text{RFBW\_T\_RFBW}} = B'_{\text{RFBW\_T\_RFBW}} = B_{\text{RFBW\_T\_RFBW}}$ when the declared maximum *Radio Bandwidth* (see clause 4.6) spans both operating bands. $B_{\text{RFBW\_T\_RFBW}}$ means the *Base Station RF Bandwidths* are located at the bottom of the supported frequency range in the lower operating band and at the top of the supported frequency range in the upper operating band. + +Occupied bandwidth test in this TS are 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. + +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 NR test models needed for *BS type 2-O*. Note the NR FR1 test models described in TS 38.141-1 [3] are also applicable for *BS type 1-O* conformance testing. + +### 4.9.2.2 NR FR2 test models + +The set-up of physical channels for transmitter tests shall be according to one of the NR test models (NR- 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: + +- For FR2-1, duration is 2 radio frames for TDD (20 ms). For FR2-2, duration is twice of 80 slots in time length (160 slots time length). +- 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 table 5.3.2-2 and table 5.3.2-3 in TS 38.104 [2]. +- Normal CP +- Virtual resource blocks of localized type + +For NR FR2 TDD, 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 [22]. + +**Table 4.9.2.2-1: Configurations of TDD for BS type 2-O test models** + +| Field name | Value | | | | +|----------------------------------------------------|-------|------|------|------| +| referenceSubcarrierSpacing (kHz) | 60 | 120 | 480 | 960 | +| Periodicity (ms) for dl-UL-TransmissionPeriodicity | 1.25 | 1.25 | 1.25 | 1.25 | +| nrofDownlinkSlots | 3 | 7 | 29 | 59 | +| nrofDownlinkSymbols | 10 | 6 | 10 | 6 | +| nrofUplinkSlots | 1 | 2 | 9 | 18 | +| nrofUplinkSymbols | 2 | 4 | 2 | 4 | + +Common physical channel parameters for all FR2 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 FR2 test models are described in clauses 4.9.2.2.1 to 4.9.2.2.3. + +**Table 4.9.2.2-2: Common physical channel parameters for BS type 2-O PDCCH** + +| 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 BS type 2-O PDSCH** + +| 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) | 0 | +| dmrs-Type for comb pattern | Configuration type 1 | +| maxLength | 1 | +| Ratio of PDSCH 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.2-4: Common physical channel parameters for PDSCH by RNTI for BS type 2-O test models** + +| Parameter | Value | +|-----------------------------------|-------| +| 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 NR FR2 test model 1.1 (NR-FR2-TM1.1) + +This model shall be used for tests on: + +- Radiated transmit power +- BS output power +- Transmit ON/OFF power +- TAE +- 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.2. Specific physical channel parameters for NR-FR2-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-FR2-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 NR FR2 test model 2 (NR-FR2-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 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-FR2-TM2 are defined in table 4.9.2.2.2-1 for 64QAM. For 16QAM and QPSK, specific physical channel parameters for NR-FR2-TM2 are defined in table 4.9.2.2.2-1 with 64QAM PDSCH PRB replaced with selected modulation order PDSCH PRB according to the corresponding test procedure. + +**Table 4.9.2.2.2-1: Specific physical channel parameters of NR-FR2-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.2a NR FR2 test model 2a (NR-FR2-TM2a) + +This model shall be used for tests on: + +- Total power dynamic range (lower OFDM symbol power limit 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. Specific physical channel parameters for NR-FR2-TM2a are defined in table 4.9.2.2.2-1 with all 64QAM PDSCH PRBs replaced by 256QAM PDSCH PRBs. + +#### 4.9.2.2.3 NR FR2 test model 3.1 (NR-FR2-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 PRBs allocated) +- Transmitted signal quality + - Frequency error + - EVM for 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. Specific physical channel parameters for NR-FR2-TM3.1 are defined in table 4.9.2.2.1-1 with all QPSK PDSCH PRBs replaced with selected modulation order PDSCH PRBs according to the corresponding test procedure. + +#### 4.9.2.2.4 NR FR2 test model 3.1a (NR-FR2-TM3.1a) + +This model shall be used for tests on: + +- Output power dynamics + - Total power dynamic range (upper OFDM symbol power limit 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. Specific physical channel parameters for NR-FR2-TM3.1a shall be defined in table 4.9.2.2.1-1 with all QPSK PDSCH PRBs replaced by 256QAM. + +#### 4.9.2.3 Data content of physical channels and signals for NR-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 [20], 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 [20] use the following additional parameters: + +- for the lowest configured carrier, for the 2nd lowest configured carrier, ... for the nth configured carrier +- Antenna ports starting with 2000 for PDCCH +- $q = 0$ (single code word) +- For NR-FR2-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 + +#### 4.9.2.3.1 PDCCH + +- + +- PDCCH modulation to be QPSK as described in TS 38.211 [20], 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-FR2-TM definitions in clause 4.4.9.2.2. +- Generate this amount of bits from the output of the PN23 sequence generator [28]. For FR2-1, 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 FR2-2, the PN sequence generator is initialized with a starting seed of "all ones" in the first allocated slot of each 80 slots time period of test model length, identical payload data sequence repeated in following 80 slot. The PN sequence is continuous over the slot boundaries. +- 1 CCE shall be according to TS 38.211 [20], clause 7.3.2. PDCCH using non-interleaved CCE-to-REG mapping. PDCCH occupies the first two 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 [20], clause 7.3.2.3. +- in DM-RS sequence generation in TS 38.211 [20], clause 7.4.1.3. +- in scrambling sequence generation in TS 38.211 [20], clause 7.3.2.3. +- Perform mapping to REs according to TS 38.211 [20], 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 [28]. For FR2-1, the PN sequence generator is initialized with a starting seed of "all ones" in the first allocated slot of each frame. For FR2-2, the PN sequence generator is initialized with a starting seed of "all ones" in the first allocated slot of each 80 slots time period of test model length, identical payload data sequence repeated in following 80 slot. 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 (). +- NR-FR2-TMs utilize 1 or 2 user PDSCH transmissions distinguished by . For each NR-FR2-TM, PRBs are mapped to user () as follows: + +**Table 4.9.2.3.2-1: Mapping of PRBs to $n_{\text{RNTI}}$ for NR-FR2-TM** + +| Test model | $n_{\text{RNTI}}$ | Number of users | +|---------------|-------------------------------------------------------|-----------------| +| NR-FR2-TM1.1 | 2 for PRBs located in PRB#0-2
0 for remaining PRBs | 2 | +| NR-FR2-TM2 | 2 for all PRBs | 1 | +| NR-FR2-TM2a | 2 for all PRBs | 1 | +| NR-FR2-TM3.1 | 2 for PRBs located in PRB#0-2
0 for remaining PRBs | 2 | +| NR-FR2-TM3.1a | 2 for PRBs located in PRB#0-2
0 for remaining PRBs | 2 | + +- Perform user specific scrambling according to TS 38.211 [20], clause 7.3.1.1. +- +- Perform modulation of the scrambled bits with the modulation scheme defined for each user according to TS 38.211 [20], clause 7.3.1.2. +- Perform mapping of the complex-valued symbols to layer according to TS 38.211 [20], clause 7.3.1.3. Complex-valued modulation symbols for codeword shall be mapped onto the layers , where is equal to 1. +- Perform PDSCH mapping type A according to TS 38.211 [20]. +- PDSCH resource allocation according to TS 38.214 [21] as following; + - NR-FR2-TM1.1, NR-FR2-TM3.1, NR-FR2-TM3.1a: type 1 for PDSCH with $n_{\text{RNTI}} = 0$ , $n_{\text{RNTI}} = 2$ + +- NR-FR2-TM2, NR-FR2-TM2a: type 1 for PDSCH with $n_{\text{RNTI}} = 2$ +- DM-RS sequence generation according to TS 38.211 [20], clause 7.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 [20], clause 7.4.1.1.2 with parameters listed in table 4.9.2.2-3. +- For NR-FR2-TM PT-RS sequence generation according to TS 38.211 [20], clause 7.4.1.2.1, with parameters listed in table 4.9.2.2-3. +- For NR-FR2-TM PT-RS mapping according to TS 38.211 [20], clause 7.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 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 RIB*, the radiated test requirements in clause 6 and 7 apply separately to each supported *operating band*, unless otherwise stated. For some radiated test requirements, it is explicitly stated that specific additions or exclusions to the test requirement apply at *multi-band RIB(s)* as detailed in the requirement clause. + +*BS type 1-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 1-O* capability of operation in multiple *operating bands*. + +For *multi-band RIBs* supporting the bands for TDD, the radiated test requirements in the present specification assume no simultaneous uplink and downlink occur between the bands. + +NOTE: The radiated test requirements for *multi-band RIBs* supporting bands for both FDD and TDD are not covered by the present release of this specification. + +## 4.12 Co-location requirements + +### 4.12.1 General + +Co-location requirements are requirements which are based on assuming the *BS type 1-O* is co-located with another BS of the same base station class. They ensure that both co-located systems can operate with minimal degradation to each other. + +The co-location requirements in table 4.12.1-1 rely on a *co-location reference antenna* used to mimic a base station to base station 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 BS receiver of own or different BS | Measure emission | Optional based on declaration | +| | OTA spurious emission: Co-location with other base stations | | | +| 6.8 | OTA transmitter intermodulation | Inject the interferer signal | Mandatory | +| 7.6.3 | OTA out-of-band blocking: Co-location with other base stations | 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.104 [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 *BS type 1-O* implemented with a planar antenna array. The method for testing BS with other antenna array implementations is not covered by the present release of this specification. + +**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\%$ | Test object vertical radiating length $\pm 30\%$ (Note 2) | +| Horizontal beam width | $65^\circ \pm 10^\circ$ | $65^\circ \pm 10^\circ$ | +| Vertical beam width | N/A | The half-power vertical beam width of the CLTA equals the narrowest declared (D.3) vertical beamwidth $\pm 3^\circ$ (Note 2) | +| Polarization (Note 3) | Match (Note4) | Match to in-band (Note 4) | +| Conducted interface return loss | $> 10$ dB | $> 10$ dB | +| NOTE 1: If a multi-column or multi-band antenna is used the column closest to the NR BS shall be selected while other columns are terminated during testing. | | | +| NOTE 2: The vertical radiating dimension definition shall be used instead of the vertical beam width definition when the test chamber dimensions limit the use of vertical beam width definition. Otherwise the vertical beam width definition shall be used. | | | +| NOTE 3: For BS type 1-O with dual polarization the CLTA has two conducted interfaces each representing one polarization. | | | +| NOTE 4: Matched to the polarization of EUT antenna. | | | + +#### 4.12.2.3 Co-location test antenna alignment + +The alignment between the NR BS 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 BS 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 BS and CLTA. The diagram shows three views: Horizontal View, Vertical View, and Side View. In the Horizontal View, the NR BS type 1-O is a large rectangle with an 'X' inside, and the CLTA is a smaller rectangle with an 'X' inside. A horizontal dashed line connects their centers. A vertical dashed line connects the bottom of the NR BS to the bottom of the CLTA. A horizontal double-headed arrow labeled 'd' indicates the distance between the vertical center lines. In the Vertical View, the NR BS is a rectangle, and the CLTA is a smaller rectangle. A vertical dashed line connects the bottom of the NR BS to the bottom of the CLTA. Arrows point down from the bottom of each rectangle to the text 'Mechanical bore-sight direction'. In the Side View, the NR BS is a rectangle with a dashed line inside, and the CLTA is a smaller rectangle. The text 'Back side' is to the left of the NR BS, and 'Front side' is to the right of the CLTA.](5e9af8986a5845504f251d3079da8078_img.jpg) + +Figure 4.12.2.3-1: Alignment of NR BS and CLTA. The diagram shows three views: Horizontal View, Vertical View, and Side View. In the Horizontal View, the NR BS type 1-O is a large rectangle with an 'X' inside, and the CLTA is a smaller rectangle with an 'X' inside. A horizontal dashed line connects their centers. A vertical dashed line connects the bottom of the NR BS to the bottom of the CLTA. A horizontal double-headed arrow labeled 'd' indicates the distance between the vertical center lines. In the Vertical View, the NR BS is a rectangle, and the CLTA is a smaller rectangle. A vertical dashed line connects the bottom of the NR BS to the bottom of the CLTA. Arrows point down from the bottom of each rectangle to the text 'Mechanical bore-sight direction'. In the Side View, the NR BS is a rectangle with a dashed line inside, and the CLTA is a smaller rectangle. The text 'Back side' is to the left of the NR BS, and 'Front side' is to the right of the CLTA. + +**Figure 4.12.2.3-1: Alignment of NR BS and CLTA** + +## 4.13 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. The OTA Test System is assumed to be correctly calibrated as part of the initial conditions. Calibration is not explicitly mentioned. + +#### X.4.2y.2 Procedure + +This clause describes the steps necessary to perform the test and provides further details of the test definition like 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.14 Reference coordinate system + +Radiated requirements are stated in terms of electromagnetic characteristics (e.g. EIRP and EIS) at certain angles with respect to the base station. To be able to declare radiated characteristics part of radiated requirements a reference coordinate system is required. The reference coordinate system is should be associated to an identifiable physical feature on the base station enclosure. The location of the origin and the orientation of the reference coordinate system are for the base station manufacturer to declare. + +The reference coordinate system is created of a Cartesian coordinate system with rectangular axis (x, y, z) and spherical angles ( $\theta$ , $\phi$ ) as showed in figure 4.14-1. + +![Figure 4.14-1: Reference coordinate system. A 3D Cartesian 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 vector is shown originating from the origin. The angle theta (θ) is measured from the positive z-axis down to the vector. The angle phi (φ) is measured in the xy-plane from the positive y-axis to the projection of the vector onto the plane.](8c5fc2c0636cfe6e574227dbf490fd4b_img.jpg) + +Figure 4.14-1: Reference coordinate system. A 3D Cartesian 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 vector is shown originating from the origin. The angle theta (θ) is measured from the positive z-axis down to the vector. The angle phi (φ) is measured in the xy-plane from the positive y-axis to the projection of the vector onto the plane. + +Figure 4.14-1: Reference coordinate system + +$\phi$ is the angle in the x/y plane, between the x-axis and the projection of the radiating vector onto the x/y plane and is defined between $-180^\circ$ and $+180^\circ$ , inclusive. $\theta$ is the angle between the projection of the vector in the x/y plane and the radiating vector and is defined between $-90^\circ$ and $+90^\circ$ , inclusive. Note that $\theta$ is defined as positive along the down-tilt angle. + +--- + +## 5 Operating bands and channel arrangement + +For the NR 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 radiated testing purposes in this specification, FR1 and FR2 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. BS 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 + +Radiated transmit power is defined as the EIRP level for a declared beam at a specific *beam peak direction*. + +For each declared beam, the requirement is based on declarations captured in clause 4.6 for a beam identifier (D.3), *reference beam direction pair* (D.8), *rated beam EIRP* (D.11) at the beam's reference direction pair, *OTA peak directions set* (D.9), the *beam direction pairs* at the maximum steering directions (D.10) and their associated *rated beam EIRP* and *beamwidth(s)* for reference *beam direction pair* and maximum steering directions (D.12). + +For a declared beam identifier and *beam direction pair*, the *rated beam EIRP* level is the maximum power that the BS is declared to radiate at the associated *beam peak direction* during the *transmitter ON period*. + +For each *beam peak direction* associated with a *beam direction pair* within the *OTA peak directions set*, a specific *rated beam EIRP* level may be claimed. Any claimed value shall be met within the accuracy requirement as described below. *Rated beam EIRP* is only required to be declared for the *beam direction pairs* subject to conformance testing as detailed in clause 6.2.4.1. + +NOTE 1: The *OTA peak directions set* for a beam is the complete continuous or discrete set of all *beam direction* for which the EIRP accuracy is intended to be achieved for the beam. + +NOTE 2: A beam direction pair consists of a beam centre direction and an associated beam peak direction. + +NOTE 3: A declared EIRP value is a value provided by the manufacturer for verification according to the conformance specification declaration requirements, whereas a claimed EIRP value is provided by the manufacturer to the equipment user for normal operation of the equipment and is not subject to formal conformance testing. + +For *operating bands* where the supported *fractional bandwidth* (FBW) is larger than 6%, two rated carrier EIRP may be declared by manufacturer: + +- $P_{\text{rated,c,FBWlow}}$ for lower supported frequency range, and +- $P_{\text{rated,c,FBWhigh}}$ for higher supported frequency range. + +For frequencies in between $F_{\text{FBWlow}}$ and $F_{\text{FBWhigh}}$ the rated carrier EIRP is: + +- $P_{\text{rated,c,FBWlow}}$ , for the carrier whose carrier frequency is within frequency range $F_{\text{FBWlow}} \leq f < (F_{\text{FBWlow}} + F_{\text{FBWhigh}}) / 2$ , +- $P_{\text{rated,c,FBWhigh}}$ , for the carrier whose carrier frequency is within frequency range $(F_{\text{FBWlow}} + F_{\text{FBWhigh}}) / 2 \leq f \leq F_{\text{FBWhigh}}$ . + +Radiated transmit power is directional requirement applicable to BS type 1-H, BS type 1-O and BS type 2-O. + +For BS Type 1-H, 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 BS type 1-H there is no requirement specified for band n46, n100, n101 and n102. + +For BS type 1-O there is no requirement specified for bands n46, n96, n100, n101 and n102. + +## 6.2.2 Minimum requirement + +Radiated transmit power minimum requirement for *BS type 1-H* and *BS type 1-O* is defined in TS 38.104 [2], clause 9.2.2. + +Radiated transmit power minimum requirement for *BS type 2-O* is defined in TS 38.104 [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 *BS type 1-H*, *BS type 1-O* and *BS type 2-O*. + +## 6.2.4 Method of test + +### 6.2.4.1 Initial conditions + +Test environments: + +- Normal, see annex B.2. +- Extreme (*BS type 1-O* and *BS type 2-O* only), 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}}$ 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 peak directions set reference beam direction pair (D.8), and +- OTA peak directions set maximum steering directions (D.10). + +Beams to be tested: + +- The *beam* with the highest *rated beam EIRP* (D.11), or +- The beams with highest rated beam EIRP, $Prated,c,FBWlow$ (D.57) and $Prated,c,FBWhigh$ (D.58), if these are provided. + +Under extreme test environment, for the *BS type 1-O* and *BS type 2-O* 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. Direction to be tested is only at *OTA peak directions set reference beam direction pair* (D.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 normal test environment conditions in OTA domain, the test procedure is as follows: + +- 1) Place the BS at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (D.2) of the BS with the test system. +- 3) Orient the positioner (and BS) in order that the direction to be tested aligns with the test antenna. + +- 4) Configure the *beam peak direction* of the BS according to the declared *beam direction pair*. +- 5) Set the BS 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 BS 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. + +- 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 BS 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 + +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, relative to the manufacturer's declared rated beam EIRP (D.11) value: + +**Table 6.2.5-1: Test requirement for radiated transmit power** + +| | Normal test environment | Extreme test environment | +|-------------|------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------| +| BS type 1-H | $f \leq 3 \text{ GHz}: \pm 3.3 \text{ dB}$ | N/A | +| | $3 \text{ GHz} < f \leq 7.125 \text{ GHz}: \pm 3.5 \text{ dB}$
For band n96: $\pm 4.0 \text{ dB}$ | | +| BS type 1-O | $f \leq 3 \text{ GHz}: \pm 3.3 \text{ dB}$ | $f \leq 3 \text{ GHz}: \pm 5.2 \text{ dB}$ | +| | $3 \text{ GHz} < f \leq 7.125 \text{ GHz}: \pm 3.5 \text{ dB}$ | $3 \text{ GHz} < f \leq 4.2 \text{ GHz}: \pm 5.3 \text{ dB}$ | +| | | $4.2 \text{ GHz} < f \leq 7.125 \text{ GHz}: \pm 5.3 \text{ dB}$ | +| BS type 2-O | $24.15 \text{ GHz} < f \leq 29.5 \text{ GHz}: \pm 5.1 \text{ dB}$ | $24.15 \text{ GHz} < f \leq 29.5 \text{ GHz}: \pm 7.6 \text{ dB}$ | +| | $37 \text{ GHz} < f \leq 43.5 \text{ GHz}: \pm 5.4 \text{ dB}$ | $37 \text{ GHz} < f \leq 43.5 \text{ GHz}: \pm 7.8 \text{ dB}$ | +| | $43.5 \text{ GHz} < f \leq 48.2 \text{ GHz}: \pm 5.6 \text{ dB}$ | $43.5 \text{ GHz} < f \leq 48.2 \text{ GHz}: \pm 8.0 \text{ dB}$ | +| | $52.6 \text{ GHz} < f \leq 71 \text{ GHz}: \pm 6.4 \text{ dB}$ | $52.6 \text{ GHz} < f \leq 71 \text{ GHz}: \pm 8.4 \text{ dB}$ | + +## 6.3 OTA base station output power + +### 6.3.1 Definition and applicability + +OTA BS output power is declared as rated carrier TRP, with the output power accuracy requirement defined at the RIB during the *transmitter ON period*. + +The BS *rated carrier TRP* for BS type 1-O shall be within limits as specified in table 6.3.1-1. + +**Table 6.3.1-1: BS rated carrier TRP limits for BS type 1-O** + +| BS class | $P_{\text{rated,c,TRP}}$ | +|-----------------------------------------------------------------------------------------------|--------------------------| +| Wide Area BS | (note) | +| Medium Range BS | $\leq +47 \text{ dBm}$ | +| Local Area BS | $\leq +33 \text{ dBm}$ | +| NOTE: There is no upper limit for the $P_{\text{rated,c,TRP}}$ of the Wide Area Base Station. | | + +For Band n41 and n90 operation in Japan, the rated output power, $P_{\text{rated,c,TRP}}$ , declared by the manufacturer shall be equal to or less than 20 W per 10 MHz bandwidth. + +There is no upper limit for the *rated carrier TRP* of BS type 2-O. + +Despite the general requirements for the BS output power described in TS 38.104 [2] clauses 9.3.2 – 9.3.3, additional regional requirements might be applicable. + +NOTE: In certain regions, power limits corresponding to BS classes may apply for *BS type 2-O*. + +### 6.3.2 Minimum requirement + +The minimum requirement for *BS type 1-O* is in TS 38.104 [2], clause 9.3.2. + +The minimum requirement for *BS type 2-O* is in TS 38.104 [2], clause 9.3.3. + +### 6.3.3 Test purpose + +The test purpose is to verify the accuracy of the *maximum carrier TRP* ( $P_{\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. + +*Base Station RF Bandwidth* positions to be tested for multi-carrier and/or CA: + +- $B_{RFBW}$ , $M_{RFBW}$ and $T_{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. + +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). + +#### 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. When calibrated and operated within the guidance of 3GPP TR 37.941 [29] the measurement methods are applicable and selected depending on availability at the test facility. + +- 1) Place the BS at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (D.2) of the BS with the test system. +- 3) Configure the BS such that the beam peak direction(s) applied during the power measurement step 6 are consistent with the grid and measurement approach for the TRP test. +- 4) Set the BS 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 BS 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. + +- 5) Orient the positioner (and BS) in order that the direction to be tested aligns with the test antenna such that measurements to determine TRP can be performed (see annex 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 $EIRP = EIRP_{p1} + EIRP_{p2}$ . + +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 BS 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 7.125$ GHz. + +### 6.3.5.2 BS 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. +- within +5.6 dB and -5.6 dB of the manufacturer's declared *rated carrier TRP* $P_{\text{rated,c,TRP}}$ for carrier frequency $43.5$ GHz $< f \leq 48.2$ GHz. +- within +6.2 dB and -6.2 dB of the manufacturer's declared *rated carrier TRP* $P_{\text{rated,c,TRP}}$ for carrier frequency $52.6$ GHz $\leq f \leq 71$ GHz. + +## 6.4 OTA output power dynamics + +### 6.4.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.2 OTA RE power control dynamic range + +#### 6.4.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 BS 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.2.2 Minimum requirement + +The minimum requirement for *BS type 1-O* is in TS 38.104 [2], clause 9.4.2.2. + +#### 6.4.2.3 Method of test + +No specific test or test requirements are defined for RE power control dynamic range. The Error Vector Magnitude test, as described in clause 6.6 provides sufficient test coverage for this requirement. + +### 6.4.3 OTA total power dynamic range + +#### 6.4.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 BS 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.3.2 Minimum requirement + +The minimum requirement for *BS type 1-O* is in TS 38.104 [2], clause 9.4.3.2. + +The minimum requirement for *BS type 2-O* is in TS 38.104 [2], clause 9.4.3.3. + +#### 6.4.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.3.4 Method of test + +##### 6.4.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\theta$ , 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.3.4.2 Procedure + +- 1) Place the BS at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (D.2) of the BS with the test system. +- 3) Orient the positioner (and BS) in order that the direction to be tested aligns with the test antenna. +- 4) Configure the beam peak direction of the BS according to the declared beam direction pair. +- 5) For *BS 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: + - NR-FR1-TM3.1b if 1024QAM is supported by BS without power back off, or + +- NR-FR1-TM3.1a in TS 38.141-1 [3] clause 4.9.2.2.6 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 in TS 38.141-1 [3] clause 4.9.2.2.5 if 1024QAM and 256QAM are both not supported by BS without power back off. For *BS 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: + - NR-FR2-TM3.1a if 256QAM is supported by BS without power back off, or + - NR-FR2-TM3.1 if 256QAM is supported by BS with power back off, or 256QAM is not supported by BS; with 64QAM signals if 64QAM is supported by BS without power back off, or; + - NR-FR2-TM3.1 with highest modulation order supported without power back off if 64QAM is not supported by BS, or; + - NR-FR2-TM3.1 with highest modulation order supported without power back off if 64QAM is supported by BS 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 *BS 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: +- NR-FR1-TM2b if 1024QAM is supported by BS, or + - NR-FR1-TM2a in TS 38.141-1 [3] clause 4.9.2.2.4 if 1024QAM is not supported by BS and 256QAM is supported by BS; or + - NR-FR1-TM2 in TS 38.141-1 [3] clause 4.9.2.2.3 if 1024QAM and 256QAM is not supported by BS; +- For *BS 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: +- NR-FR2-TM2a if 256QAM is supported by BS, or; + - NR-FR2-TM2 with highest modulation order supported if 256QAM is not supported by BS; +- 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.3.5 Test requirement + +#### 6.4.3.5.1 BS 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.3.5.1-1. + +**Table 6.4.3.5.1-1: Total power dynamic range** + +| BS channel bandwidth (MHz) | Total power dynamic range (dB) | | | +|----------------------------|--------------------------------|------------|------------| +| | 15 kHz SCS | 30 kHz SCS | 60 kHz SCS | +| 5 | 13.5 | 10 | N/A | +| 10 | 16.7 | 13.4 | 10 | +| 15 | 18.5 | 15.3 | 12.1 | +| 20 | 19.8 | 16.6 | 13.4 | +| 25 | 20.8 | 17.7 | 14.5 | +| 30 | 21.6 | 18.5 | 15.3 | +| 35 | 22.7 | 19.6 | 16.4 | +| 40 | 22.9 | 19.8 | 16.6 | +| 45 | 23.8 | 20.7 | 17.6 | +| 50 | 23.9 | 20.8 | 17.7 | +| 60 | N/A | 21.6 | 18.5 | +| 70 | N/A | 22.3 | 19.2 | +| 80 | N/A | 22.9 | 19.8 | +| 90 | N/A | 23.4 | 20.4 | +| 100 | N/A | 23.9 | 20.9 | + +NOTE: 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.3.5.2 BS type 2-O + +OTA total power dynamic range minimum requirement for *BS 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.4.3.5.2-1 in FR2-1 and table 6.4.3.5.2-2 in FR2-2. + +**Table 6.4.3.5.2-1: Minimum requirement for BS type 2-O total power dynamic range in FR2-1** + +| 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 | + +**Table 6.4.3.5.2-2: Minimum requirement for BS type 2-O total power dynamic range in FR2-2** + +| SCS (kHz) | OTA total power dynamic range (dB) | | | | | +|-----------|------------------------------------|---------|---------|----------|----------| +| | 100 MHz | 400 MHz | 800 MHz | 1600 MHz | 2000 MHz | +| 120 | 17.7 | 23.8 | N/A | N/A | N/A | +| 480 | N/A | 17.7 | 20.8 | 23.8 | N/A | +| 960 | N/A | 14.7 | 17.7 | 20.8 | [21.5] | + +NOTE: Additional test requirements for the EVM at the lower limit of the dynamic range are defined in clause 6.6. + +## 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 requirements apply only to TDD operation of NR BS. + +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 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 BS supporting intra-band contiguous CA, the transmitter OFF power is defined as the mean power measured over $70/N \mu\text{s}$ filtered with a square filter of bandwidth equal to the *aggregated BS channel bandwidth* $BW_{\text{Channel\_CA}}$ centred on $(F_{\text{edge\_high}} + F_{\text{edge\_low}})/2$ during the *transmitter OFF period*. $N = SCS/15$ , where SCS is the smallest supported Sub Carrier Spacing in kHz in the *aggregated BS channel bandwidth*. + +For *BS type 1-O*, the transmitter OFF power is defined as the output power at the *co-location test antenna* conducted output(s). For *BS type 2-O* the transmitter OFF power is defined as TRP. + +For *multi-band RIBs* or *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 *BS type 1-O* is in TS 38.104 [2], clause 9.5.2.2. + +The minimum requirement for *BS type 2-O* is in TS 38.104 [2], clause 9.5.2.3. + +### 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* requirements apply only to TDD operation of BS. + +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. 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 curve starts at the OFF power level, rises sharply during the 'Transmitter transient period', reaches the ON power level, and then falls back to the OFF power level during another 'Transmitter transient period'. The time between the start and end of the ON power level is the 'Transmitter ON period (DL transmission)'. The time before the first transient period is the 'Transmitter OFF period'. The time after the second transient period is also labeled 'Transmitter OFF period'. The graph also shows 'UL transmission' before the ON period and 'GP or UL transmission' after the ON period.](d461c6341beba90844ef785469cd757f_img.jpg) + +Figure 6.5.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: 'ON power level' and 'OFF power level'. The curve starts at the OFF power level, rises sharply during the 'Transmitter transient period', reaches the ON power level, and then falls back to the OFF power level during another 'Transmitter transient period'. The time between the start and end of the ON power level is the 'Transmitter ON period (DL transmission)'. The time before the first transient period is the 'Transmitter OFF period'. The time after the second transient period is also labeled 'Transmitter OFF period'. The graph also shows 'UL transmission' before the ON period and 'GP or UL transmission' after 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 *BS 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 *BS 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 *BS type 1-O* is in TS 38.104 [2], clause 9.5.3.2. + +The minimum requirement for *BS type 2-O* is in TS 38.104 [2], clause 9.5.3.3. + +## 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 *BS type 1-O* is specified as co-location requirement. For general description of co-location requirements, refer to clause 4.12. +- The requirement for *BS 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 BS at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (D.2) of the BS with the test system. + +##### 6.5.2.4.2.2 BS type 1-O + +- 3) Set the BS in the direction of the declared beam peak direction of the beam direction pair, for the beam to be tested. +- 4) Place the *co-location test antenna* as specified in clause 4.12. +- 5) Configure the beam peak direction of the BS according to the declared beam direction pair. +- 6) Set the BS 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 a BS 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 BS 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 BS 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 BS 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 BS 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 BS type 2-O + +- 3) Set the BS in the direction of the declared beam peak direction of the *beam direction pair*, for the beam to be tested. +- 4) Set the BS to transmit according to the applicable test configuration in clause 4.8 using the corresponding test model NR-FR2-TM1.1 and set of physical channels in clause 4.9.2. + +For a BS 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 NR-FR2-TM1.1 and set of physical channels in clause 4.9.2 on all carriers 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 NR BS 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 NR BS 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 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 + $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 BS channel bandwidth*. + +## 6.5.2.5 Test requirements + +### 6.5.2.5.1 BS type 1-O + +The mean power spectral density measured according to clause 6.5.2.4.2 shall be less than -102.6 dBm/MHz for carrier frequency $f \leq 3.0 \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 7.125 \text{ GHz}$ . + +For *multi-band RIB*, the requirement is only applicable during the transmitter OFF period in all supported operating bands. + +### 6.5.2.5.2 BS 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. + +The measured mean EIRP spectral density according to clause 6.5.2.4.2 shall be less than $-32.4 + P_{\text{rated,c,EIRP}} - P_{\text{rated,c,TRP}}$ dBm/MHz for carrier frequency $43.5 \text{ GHz} < f \leq 48.2 \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 $-30.4 + P_{\text{rated,c,EIRP}} - P_{\text{rated,c,TRP}}$ dBm/MHz for carrier frequency $52.6 \text{ GHz} \leq f \leq 71 \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. + +## 6.6 OTA transmitted signal quality + +### 6.6.1 General + +Unless otherwise stated, the requirements in clause 6.6 apply during the *transmitter ON period*. + +### 6.6.2 OTA frequency error + +#### 6.6.2.1 Definition and applicability + +OTA frequency error is the measure of the difference between the actual BS 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. + +#### 6.6.2.2 Minimum Requirement + +The minimum requirement for *BS type 1-O* is in TS 38.104 [2], clause 9.6.1.2. + +The minimum requirement for *BS type 2-O* is in TS 38.104 [2], clause 9.6.1.3. + +### 6.6.2.3 Test purpose + +The test purpose is to verify that OTA frequency error is within the limit specified by the minimum requirement. + +### 6.6.2.4 Method of test + +Requirement is tested together with OTA modulation quality test, as described in clause 6.6.3. + +#### 6.6.2.4.1 Initial conditions + +Directions to be tested: OTA coverage range reference direction (D.35). + +### 6.6.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.6.2.5-1 observed over 1 ms. + +**Table 6.6.2.5-1: OTA frequency error test requirement for BS type 1-O and BS type 2-O** + +| 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})$ | + +## 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 *BS type 1-O*, is in TS 38.104 [2], clause 9.6.2.2. + +The minimum requirement for *BS type 2-O*, is in TS 38.104 [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. + +*Base station 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 + +- 1) Place the BS at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (D.2) of the BS with the test system. +- 3) Orient the positioner (and BS) in order that the direction to be tested aligns with the test antenna. +- 4) Configure the beamforming settings of the BS according to the direction to be tested. +- 5) Set the BS 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 BS type 1-O declared to be capable of single carrier operation only, set the BS to transmit a signal according to: + +- 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 related output power if 1024QAM is supported by BS with power back off, and NR-FR1-TM3.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 256 QAM is supported by BS without power back off, or + - NR-FR1-TM3.1a if 256QAM is supported by BS with power back off and 1024QAM is not supported, at manufacturer's declared rated output power ( $P_{\text{rated,c,EIRP}}$ ) 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 BS type 1-O declared to be capable of multi-carrier and/or CA operation, set the BS 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: + +- 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-TM3.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-TM3.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 if 256QAM is supported by BS with power back off, at manufacturer's declared rated output power ( $P_{\text{rated,c,EIRP}}$ ) 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 *BS type 2-O* declared to be capable of single carrier operation only, set the BS 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: + +- NR-FR2-TM3.1a with 256QAM signal if 256QAM is supported by BS without power back off, or +- NR-FR2-TM3.1a at manufacturer's declared rated output power if 256QAM is supported by BS with power back off, and NR-FR2-TM3.1 with highest modulation order supported without power back off, or +- NR-FR2-TM3.1 with 64QAM signal if 64QAM is supported by BS without power back off, or +- NR-FR2-TM 3.1 with highest modulation order without power back off if 64QAM is not supported by BS, or +- if 64 QAM is supported by BS with power back off, NR-FR2-TM 3.1 with 64QAM at manufacturer's declared rated output power ( $P_{\text{rated,c,EIRP}}$ ) and NR-FR2-TM3.1 with highest modulation order supported at maximum power. + +For *BS type 2-O* declared to be capable of multi-carrier and/or CA operation, set the BS to transmit according to: + +- NR-FR2-TM3.1a with 256QAM signal if 256QAM is supported by BS without power back off, or +- NR-FR2-TM3.1a at manufacturer's declared rated output power if 256QAM is supported by BS with power back off, and NR-FR2-TM3.1 at maximum power, or +- NR-FR2-TM3.1 with 64QAM signal if 64QAM is supported by BS without power back off, or +- NR-FR2-TM3.1 with highest modulation order supported without power back off if 64QAM is not supported by BS, or +- if 64QAM is supported by BS with power back off, NR-FR2-TM3.1 with 64QAM signal at manufacturer's declared rated output power ( $P_{\text{rated,c,EIRP}}$ ) and NR-FR2-TM3.1 with highest supported modulation order at maximum power + +For NR-FR1-TM 3.1a and NR-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 NR-FR1-TM2 if 256QAM and 1024 QAM is not supported by *BS type 1-O* or for NR-FR1-TM2a if 256QAM is supported by *BS type 1-O* and 1024 QAM 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 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 NR-FR2-TM2 if 256QAM is not supported by *BS type 2-O* or for NR-FR2-TM2a if 256QAM is supported by *BS type 2-O*. For NR-FR2-TM2 and NR-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 *BS type 1-O* + +For *BS type 1-O*, the EVM of each NR carrier for different modulation schemes on PDSCH shall be less than the limits in table 6.6.3.5.1-1. + +**Table 6.6.3.5.1-1: EVM requirements for BS type 1-O** + +| 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.6.3.5.1-1 shall be considered for rank 1. + +For NR, 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.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 BS 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) (%) | +|-------------------------|----------|--------------------------------------------------------------|----------------------------|--------------------------------------------------------------------------| +| 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.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) (%) | +|-------------------------|----------|------------------------------------------------------|----------------------------|------------------------------------------------------------------| +| 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.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 BS type 2-O + +For BS type 2-O, the EVM of each NR carrier for different modulation schemes on PDSCH shall be less than the limits in table 6.6.3.5.2-1 for FR2-1 and table 6.6.3.5.2-1a for FR2-2. + +**Table 6.6.3.5.2-1: EVM requirements for BS type 2-O for FR2-1** + +| Modulation scheme for PDSCH | Required EVM (%) | +|-----------------------------|------------------| +| QPSK | 18.5 | +| 16QAM | 13.5 | +| 64QAM | 9 | +| 256QAM | 4.5 | + +**Table 6.6.3.5.2-1a: EVM requirements for BS type 2-O for FR2-2** + +| Modulation scheme for PDSCH | Required EVM (%) | +|-----------------------------|------------------| +| QPSK | [18.5] | +| 16QAM | [13.5] | +| 64QAM | [9.0] | + +EVM requirements shall apply for each NR carrier over all allocated resource blocks and downlink slots. PT-RS should be configured for localized setting for every fourth symbol for every second RB. Different modulation schemes listed in table 6.6.3.5.2-1 and table 6.6.3.5.2-1a shall be considered for rank 1. + +For FR2-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. + +For FR2-2, for all bandwidths, the EVM measurement shall be performed for each NR carrier over all allocated resource blocks and downlink slots within 80 slots measurement periods. The boundaries of the EVM measurement periods need not be aligned with radio frame boundaries. + +Table 6.6.3.5.2-2, 6.6.3.5.2-3, 6.6.3.5.2-4, and 6.6.3.5.2-5 below specify the EVM window length ( $W$ ) for normal CP for BS 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, 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. | | | | | + +**Table 6.6.3.5.2-4: EVM window length for normal CP, FR2-2, 480 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) (%) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|-------------------------------------|----------------------------|-------------------------------------------------| +| 400 | 1024 | 72 | 36 | 50 | +| 800 | 2048 | 144 | 72 | 50 | +| 1600 | 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 16. Symbol 0 of slot 0 and slot 16 may have a longer CP and therefore a lower percentage. | | | | | + +**Table 6.6.3.5.2-5: EVM window length for normal CP, FR2-2, 960 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) (%) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|-------------------------------------|----------------------------|-------------------------------------------------| +| 400 | 512 | 36 | 18 | 50 | +| 800 | 1024 | 72 | 36 | 50 | +| 1600 | 2048 | 144 | 72 | 50 | +| 2000 | 2048 | 144 | 72 | 50 | +| NOTE: These percentages are informative and apply to all OFDM symbols within subframe except for symbol 0 of slot 0 and slot 32. Symbol 0 of slot 0 and slot 32 may have a longer CP and therefore a lower percentage. | | | | | + +## 6.6.4 OTA time alignment error + +### 6.6.4.1 Definition and applicability + +This requirement shall apply to frame timing in MIMO transmission, carrier aggregation and their combinations. + +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 *BS type 1-O* is in TS 38.104 [2], clause 9.6.3.2. + +The minimum requirement for *BS type 2-O* is in TS 38.104 [2], clause 9.6.3.3. + +#### 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. + +*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}}$ and $B'_{\text{RFBW\_T}}$ 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 BS polarisations such that it receives half the power from each polarisation. + +##### 6.6.4.4.2 Procedure + +- 1) Place the BS at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (D.2) of the BS with the test system. +- 3) Orient the positioner (and BS) in order that the direction to be tested aligns with the test antenna. +- 4) Configure the beamforming settings of the BS according to the direction of the testing. +- 5) Set the *BS type 1-O* to transmit NR-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 *BS type 2-O* to transmit NR-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 NR-FR1-TM1.1 and NR-FR2-TM 1.1 (using DMRS ports $p = 1000$ and $1001$ with CDM). + +For a BS declared to be capable of single carrier operation only, set the BS 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 BS supports intra band contiguous or non-contiguous Carrier Aggregation set the BS to transmit using the applicable test configuration and corresponding power setting specified in clauses 4.7.2 and 4.8. + +If the BS supports inter band carrier aggregation set the BS 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 *BS type 1-O* declared to be capable of multi-carrier operation, set the BS 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 *BS type 2-O* declared to be capable of multi-carrier operation, set the BS 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 *BS 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 *BS type 2-O* + +The minimum requirement for TAE is given in Table 6.6.4.5.2-1. + +**Table 6.6.4.5.2-1: TAE requirements for *BS type 2-O*** + +| Requirement | TAE | | | +|--------------------------------------------------------------------------------------------------------|----------------------------|------------------------|------------------------| +| | 60, 120 kHz
SCS
(ns) | 480 kHz
SCS
(ns) | 960 kHz
SCS
(ns) | +| MIMO transmission | 90 | 57.5 | 57.5 | +| intra-band contiguous carrier aggregation, with or without MIMO | 155 | 57.5 | 57.5 | +| intra-band non-contiguous carrier aggregation, with or without MIMO
(Note) | 285 | N/A | N/A | +| inter-band carrier aggregation, with or without MIMO | 3025 | 3025 | 3025 | +| NOTE: Intra-band non-contiguous carrier aggregation is not supported for FR2-2 in this release. | | | | + +## 6.7 OTA unwanted emissions + +### 6.7.1 General + +OTA unwanted emissions consist of so-called out-of-band emissions and spurious emissions according to ITU definitions ITU-R SM.329 [5]. In ITU terminology, out of band emissions are unwanted emissions immediately outside the *BS 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 *BS type 1-O* and *BS type 2-O* transmitter is specified both in terms of Adjacent Channel Leakage power Ratio (ACLR) and operating band unwanted emissions (OBUE). The OTA Operating band unwanted emissions define all unwanted emissions in each supported downlink operating band plus the frequency ranges $\Delta f_{OBUE}$ above and $\Delta f_{OBUE}$ below each band. 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_{OBUE}$ . The value of $\Delta f_{OBUE}$ is defined in table 6.7.1-1 for *BS type 1-O* and *BS type 2-O* for the NR operating bands. + +**Table 6.7.1-1: Maximum offset $\Delta f_{\text{OBUE}}$ outside the downlink operating band** + +| BS type | Operating band characteristics | $\Delta f_{\text{OBUE}}$ (MHz) | +|-------------|------------------------------------------------------------------------------------|--------------------------------| +| BS 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 | +| | n104 | 100 | +| BS type 2-O | $F_{\text{DL,high}} - F_{\text{DL,low}} \leq 4000 \text{ MHz}$ | 1500 | +| | $4000 < F_{\text{DL,high}} - F_{\text{DL,low}} \leq 14000 \text{ MHz}$ | 3500 | + +The OTA 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 OTA 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 applies during the *transmitter ON period* for a single transmitted carrier. The minimum requirement below may be applied regionally. There may also be regional requirements to declare the OTA occupied bandwidth according to the definition in the present clause. + +The OTA occupied bandwidth is defined as a *directional requirement* and shall be met in the manufacturer's declared *OTA coverage range* at the RIB. + +### 6.7.2.2 Minimum requirement + +The minimum requirement for *BS type 1-O* and *BS type 2-O* is in TS 38.104 [2], clause 9.7.2.2. + +### 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 BS channel bandwidth* positions to be tested for contiguous carrier aggregation: $M_{\text{BW Channel CA}}$ ; see clause 4.9.1. + +For a BS 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 NR-FR1-TM1.1 for *BS type 1-O* or NR-FR2-TM1.1 for *BS type 2-O* in clause 4.9.2 at manufacturers declared rated carrier EIRP ( $P_{\text{rated,c,EIRP}}$ , D.11). + +For a BS declared to be capable of contiguous carrier aggregation operation, set the base station to transmit according to NR-FR1-TM1.1 for *BS type 1-O* or NR-FR2-TM1.1 for *BS 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. + +#### 6.7.2.4.2 Procedure + +- 1) Place the BS at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (D.2) of the BS with the test system. +- 3) Orient the positioner (and BS) in order that the direction to be tested aligns with the test antenna.. +- 4) Configure the beam peak direction of the BS according to the declared beam direction pair. +- 5) Set the BS 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, table 6.7.2.4.2-2, and table 6.7.2.4.2-3. The selected resolution bandwidth (RBW) filter of the analyser shall be 30 kHz or less. + +NOTE: The detection mode of the spectrum analyzer will not have any effect on the result if the statistical properties of the out-of-OBW power are the same as those of the inside-OBW power. Both are expected to have the Rayleigh distribution of the amplitude of Gaussian noise. In any case where the statistics are not the same, though, the detection mode is power responding. There are at least two ways to be power responding. The spectrum analyser can be set to "sample" detection, with its video bandwidth setting at least three times its RBW setting. Or the analyser may be set to respond to the average of the power (root-mean-square of the voltage) across the measurement cell. + +**Table 6.7.2.4.2-1: Span and number of measurement points for OBW measurements for FR1** + +| Bandwidth | BS channel bandwidth
$BW_{Channel}$ (MHz) | | | | | Aggregated BS
channel bandwidth
$BW_{Channel\_CA}$ (MHz) | +|--------------------------------------|----------------------------------------------|-----|-----|-----|------|---------------------------------------------------------------------| +| | 5 | 10 | 15 | 20 | > 20 | > 20 | +| Span (MHz) | 10 | 20 | 30 | 40 | | $2 \times BW_{Channel\_CA}$ | +| Minimum number of measurement points | 400 | 400 | 400 | 400 | | $\left\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-1** + +| Bandwidth | BS channel bandwidth
$BW_{Channel}$ (MHz) | | | | Aggregated BS
channel bandwidth
$BW_{Channel\_CA}$ (MHz) | +|--------------------------------------|----------------------------------------------|-----|-----|-----|----------------------------------------------------------------| +| | 50 | 100 | 200 | 400 | > 50 | +| Span (MHz) | | | | | $2 \times BW_{Channel\_CA}$ | +| Minimum number of measurement points | | | | | | + +**Table 6.7.2.4.2-3: Span and number of measurement points for OBW measurements for FR2-2** + +| Bandwidth | BS channel bandwidth
$BW_{Channel}$ (MHz) | | | | | Aggregated BS channel bandwidth
$BW_{Channel\_CA}$ (MHz) | | +|--------------------------------------|----------------------------------------------|-----|-----|------|------|-------------------------------------------------------------|-------| +| | 100 | 400 | 800 | 1600 | 2000 | $\leq 400$ | > 400 | +| Span (MHz) | | | | | | | | +| Minimum number of measurement points | | | | | | | | + +- 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 BS type 1-O + +The OTA occupied bandwidth for each NR carrier shall be less than the channel bandwidth as defined in TS 38.104 [2], table 5.3.5-1. 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.7.2.5.2 BS type 2-O + +The OTA occupied bandwidth for each NR carrier shall be less than the channel bandwidth as defined in TS 38.104 [2], table 5.3.5-2. 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.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. + +For both *BS type 1-O* and *BS type 2-O*, for a *RIB* operating in multi-carrier or contiguous CA, the OTA ACLR requirements in clause 6.7.3.2 apply to *BS channel bandwidths* of the outermost carrier. + +For *BS type 1-O*, for a *RIB* operating in non-contiguous spectrum, the OTA ACLR requirements in clause 6.7.3.2 shall apply inside sub-block gaps for the frequency ranges defined in table 6.7.3.5.1-2a, while the CACLR requirement in clause 6.7.3.2 shall apply in *sub block gaps* for the frequency ranges defined in table 6.7.3.5.1-3. In addition, for a *multi-band RIB*, the ACLR requirement in clause 6.7.3.2 shall apply in *Inter RF Bandwidth gaps* for the frequency ranges defined in table 6.7.3.5.1-2a, while the CACLR requirement in clause 6.7.3.2 shall apply in *Inter RF Bandwidth gaps* for the frequency ranges defined in table 6.7.3.5.1-3. + +For *BS type 2-O*, for a *RIB* operating in non-contiguous spectrum, the OTA ACLR requirements in clause 6.7.3.2 shall apply inside any sub-block gap for the frequency ranges defined in table 6.7.3.5.2-3, while the CACLR requirement in clause 6.6.3.2 shall apply in *sub block gaps* for the frequency ranges defined in table 6.7.3.5.2-3. + +The requirement shall be applied per RIB during the *transmitter ON period*. + +### 6.7.3.2 Minimum requirement + +The minimum requirement for *BS type 1-O* is in TS 38.104 [2], clause 9.7.3.2. + +The minimum requirement for *BS type 2-O* is in TS 38.104 [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. + +*Base Station 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: As the requirement is TRP the beam pattern(s) may be set up to optimise the TRP measurement procedure (see annex I). + +#### 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. When calibrated and operated within the guidance of 3GPP TR 37.941 [29] the measurement methods are applicable and selected depending on availability at the test facility. + +- 1) Place the BS at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (D.2) of the BS with the test system. +- 3) The measurement devices characteristics shall be: + +measurement filter bandwidth: defined in clause 6.7.3.5. + +detection mode: true RMS voltage or true power averaging. + +The emission power should be averaged over an appropriate time duration to ensure the measurement is within the measurement uncertainty in Table 4.1.2.2-1 for FR1 and Table 4.1.2.2-2 for FR2. + +- 4) For single carrier operation, set the BS 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 BS 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. + +- 5) Orient the positioner (and BS) in order that the direction to be tested aligns with the test antenna such that measurements to determine TRP can be performed (see annex 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 $\text{TRP}_{\text{Estimate}}$ (see annex I). +- 8) Calculate $\text{TRP}_{\text{Estimate}}$ 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 *BS type 1-O* or table 6.7.3.5.2-1 for *BS 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 NR- FR1-TM1.2 defined in clause 4.9.2 in TS 38.141-1 [3] for *BS type 1-O*. + +In addition, for *multi-band RIB*, the following steps shall apply: + +- 13) For *BS 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 *BS type 1-O* + +For the OTA ACLR requirement either the OTA ACLR limits in tables 6.7.3.5.1-1/2a 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-3 or the OTA CACLR absolute limits in table 6.7.3.5.1-3a 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-3 and the filters on the assigned channels are defined in table 6.7.3.5.1-4. + +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: BS type 1-O ACLR limit** + +| BS channel bandwidth of lowest/highest NR carrier transmitted BW_{Channel} (MHz) | BS adjacent channel centre frequency offset below the lowest or above the highest carrier centre frequency transmitted | Assumed adjacent channel carrier (informative) | Filter on the adjacent channel frequency and corresponding filter bandwidth | OTA ACLR limit (0 – 3 GHz) | OTA ACLR limit (3 – 6 GHz) | OTA ACLR limit (6.0 – 7.125 GHz) | +|------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|------------------------------------------------------------------------------------|-----------------------------------|-----------------------------------|-----------------------------------------| +| 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | $BW_{Channel}$ | NR of same BW (Note 2) | Square ( $BW_{Config}$ ) | 44 dB | 43.8 dB | 36.8 dB | +| | $2 \times BW_{Channel}$ | NR of same BW (Note 2) | Square ( $BW_{Config}$ ) | 44 dB | 43.8 dB | 36.8 dB | +| | $BW_{Channel}/2 + 2.5$ MHz | 5 MHz E-UTRA | Square (4.5 MHz) | 44 dB (Note 3) | 43.8 dB (Note 3) | NA | +| | $BW_{Channel}/2 + 7.5$ MHz | 5 MHz E-UTRA | Square (4.5 MHz) | 44 dB (Note 3) | 43.8 dB (Note 3) | NA | + +NOTE 1: $BW_{Channel}$ and $BW_{Config}$ are the BS channel bandwidth and transmission bandwidth configuration of the lowest/highest NR carrier transmitted on the assigned channel frequency. + +NOTE 2: With SCS that provides largest transmission bandwidth configuration ( $BW_{Config}$ ). + +NOTE 3: The requirements are applicable when the band is also defined for E-UTRA or UTRA. + +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: BS type 1-O ACLR absolute limit** + +| BS category / BS class | OTA ACLR absolute limit | +|-------------------------------|--------------------------------| +| Category A Wide Area BS | -4 dBm/MHz | +| Category B Wide Area BS | -6 dBm/MHz | +| Medium Range BS | -16 dBm/MHz | +| Local Area BS | -23 dBm/MHz | + +NOTE 1: The test requirement is derived from the basic limit a scaling factor of 9 dB and any applicable TT. + +NOTE 2: Void + +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-2a. + +**Table 6.7.3.5.1-2a: BS type 1-O ACLR limit in non-contiguous spectrum or multiple bands** + +| 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 | OTA ACLR limit (0-3GHz) | OTA ACLR limit (3-6GHz) | OTA ACLR limit (6.0 – 7.125 GHz) | +|--------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|------------------------------------------------------------------------------------|--------------------------------|--------------------------------|-----------------------------------------| +| 5, 10, 15, 20 | W gap ≥ 15 (Note 3)
W gap ≥ 45 (Note 4) | 2.5 MHz | 5 MHz NR (Note 2) | Square (BW Config ) | 44 dB | 43.8 dB | 36.8 dB | +| | W gap ≥ 20 (Note 3)
W gap ≥ 50 (Note 4) | 7.5 MHz | 5 MHz NR (Note 2) | Square (BW Config ) | 44 dB | 43.8 dB | 36.8 dB | +| 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | W gap ≥ 60 (Note 4)
W gap ≥ 30 (Note 3) | 10 MHz | 20 MHz NR (Note 2) | Square (BW Config ) | 44 dB | 43.8 dB | 36.8 dB | +| | W gap ≥ 80 (Note 4)
W gap ≥ 50 (Note 3) | 30 MHz | 20 MHz NR (Note 2) | Square (BW Config ) | 44 dB | 43.8 dB | 36.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 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. + +The OTA CACLR measurement result shall not less than the OTA CACLR limit specified in table 6.7.3.5.1-3. + +**Table 6.7.3.5.1-3: BS type 1-O CACLR limit** + +| 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 | OTA CACLR limit (0-3 GHz) | OTA CACLR limit (3-6 GHz) | OTA CACLR limit (6.0 – 7.125 GHz) | +|--------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|------------------------------------------------------------------------------------|----------------------------------|----------------------------------|------------------------------------------| +| 5, 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 | 36.8dB | +| | 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 | 36.8dB | +| 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 | 36.8dB | +| | 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 | 36.8dB | + +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 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. + +The absolute total power measurement shall not exceed the OTA CACLR absolute limit specified in table 6.7.3.5.1-3a. + +**Table 6.7.3.5.1-3a: BS type 1-O CACLR absolute limit** + +| BS category / BS class | OTA CACLR absolute limit | +|-------------------------------|---------------------------------| +| Category A Wide Area BS | -4 dBm/MHz | +| Category B Wide Area BS | -6 dBm/MHz | +| Medium Range BS | -16 dBm/MHz | +| Local Area BS | -23 dBm/MHz | + +NOTE 1: The test requirement is derived from the basic limit a scaling factor of 9 dB and any applicable TT. +NOTE 2: Void + +**Table 6.7.3.5.1-4: 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 BS type 2-O + +For the OTA ACLR requirement either the OTA ACLR limits in tables 6.7.3.5.2-1/3 or the OTA ACLR absolute limits in table 6.7.3.5.2-2 shall apply, whichever is less stringent. The OTA CACLR limits in table 6.7.3.5.2-4 or the OTA CACLR absolute limits in table 6.7.3.5.2-4a shall apply, whichever is less stringent. + +The CACLR in a sub-block 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, and +- b) 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-5. + +The OTA ACLR measurement result shall not be less than the OTA ACLR limit specified in table 6.7.3.5.2-1. + +**Table 6.7.3.5.2-1: BS type 2-O ACLR limit** + +| BS channel bandwidth of lowest/highest NR carrier transmitted BW_{Channel} (MHz) | BS adjacent channel centre frequency offset below the lowest or above the highest carrier centre frequency transmitted | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | OTA ACLR limit (dB) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|------------------------------------------------------------------------------------|------------------------------------------------------------------| +| 50, 100, 200, 400, 800, 1600, 2000 | $BW_{Channel}$ | NR of same BW (Note 2) | Square ( $BW_{Config}$ ) | 25.7 (Note 3)
23.4 (Note 4)
23.2 (Note 5)
19.4 (Note 6) | +| NOTE 1: $BW_{Channel}$ and $BW_{Config}$ are the BS channel bandwidth and transmission bandwidth configuration of the lowest/highest NR carrier transmitted on the assigned channel frequency.
NOTE 2: With SCS that provides largest transmission bandwidth configuration ( $BW_{Config}$ ).
NOTE 3: 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 – 43.5 GHz.
NOTE 5: Applicable to bands defined within the frequency spectrum range of 43.5 – 48.2 GHz.
NOTE 6: Applicable to bands defined within the frequency spectrum range of 52.6 – 71 GHz. | | | | | + +The absolute total power measurement shall not exceed the OTA ACLR absolute limit specified in table 6.7.3.5.2-2 + +**Table 6.7.3.5.2-2: BS type 2-O ACLR absolute limit** + +| BS class | ACLR absolute limit (Note 1) | ACLR absolute limit (Note 2) | ACLR absolute limit (Note 3) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|-------------------------------------|-------------------------------------| +| Wide area BS | -10.3 dBm/MHz | -10.1 dBm/MHz | -8.3 dBm/MHz | +| Medium range BS | -17.3 dBm/MHz | -17.1 dBm/MHz | -15.3 dBm/MHz | +| Local area BS | -17.3 dBm/MHz | -17.1 dBm/MHz | -15.3 dBm/MHz | +| NOTE 1: Applicable to bands defined within the frequency spectrum range of 24.25 – 43.5 GHz
NOTE 2: Applicable to bands defined within the frequency spectrum range of 43.5 – 48.2 GHz.
NOTE 3: Applicable to bands defined within the frequency spectrum range of 52.6 – 71 GHz. | | | | + +For operation in non-contiguous spectrum, the OTA ACLR measurement result shall not be less than the OTA ACLR limit specified in table 6.7.3.5.2-3. + +**Table 6.7.3.5.2-3: BS type 2-O ACLR limit in non-contiguous spectrum** + +| BS channel bandwidth of NR carrier transmitted adjacent to sub-block gap (MHz) | Sub-block gap size (Wgap) where the limit applies (MHz) | BS adjacent channel centre frequency offset below or above the sub-block edge (inside the gap) | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | OTA ACLR limit (MHz) | +|---------------------------------------------------------------------------------------|---------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------|-----------------------------------------|------------------------------------------------------------------------------------|-------------------------------------------------| +| 50, 100 | W gap ≥ 100 (Note 5)
W gap ≥ 250 (Note 6) | 25 MHz | 50 MHz NR (Note 2) | Square (BW Config ) | 25.7 (Note 3)
23.4 (Note 4)
23.2 (Note 7) | +| 200, 400 | W gap ≥ 400 (Note 6)
W gap ≥ 250 (Note 5) | 100 MHz | 200 MHz NR (Note 2) | Square (BW Config ) | 25.7 (Note 3)
23.4 (Note 4)
23.2 (Note 7) | + +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 to bands defined within the frequency spectrum range of 24.24 – 33.4 GHz. +NOTE 4: Applicable to bands defined within the frequency spectrum range of 37 – 43.5 GHz. +NOTE 5: Applicable in case the BS 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 BS channel bandwidth of the NR carrier transmitted at the other edge of the gap is 200 or 400 MHz. +NOTE 7: Applicable to bands defined within the frequency spectrum range of 43.5 – 48.2 GHz. + +For operation in non-contiguous spectrum, the CACLR for carriers located on either side of the sub-block gap shall be less than the value specified in table 6.7.3.5.2-4. + +**Table 6.7.3.5.2-4: BS type 2-O CACLR limit in non-contiguous spectrum** + +| BS channel bandwidth of NR carrier transmitted adjacent to sub-block gap (MHz) | Sub-block gap size (Wgap) where the limit applies (MHz) | BS adjacent channel centre frequency offset below or above the sub-block edge (inside the gap) | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | OTA CACLR limit (dB) | +|---------------------------------------------------------------------------------------|--------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------|-----------------------------------------|------------------------------------------------------------------------------------|-------------------------------------------------| +| 50, 100 | 50 ≤ W gap < 100 (Note 5)
50 ≤ W gap < 250 (Note 6) | 25 MHz | 50 MHz NR (Note 2) | Square (BW Config ) | 25.7 (Note 3)
23.4 (Note 4)
23.2 (Note 7) | +| 200, 400 | 200 ≤ W gap < 400 (Note 6)
200 ≤ W gap < 250 (Note 5) | 100 MHz | 200 MHz NR (Note 2) | Square (BW Config ) | 25.7 (Note 3)
23.4 (Note 4)
23.2 (Note 7) | + +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 to bands defined within the frequency spectrum range of 24.24 – 33.4 GHz. +NOTE 4: Applicable to bands defined within the frequency spectrum range of 37 – 43.5 GHz. +NOTE 5: Applicable in case the BS 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 BS channel bandwidth of the NR carrier transmitted at the other edge of the gap is 200 or 400 MHz. +NOTE 7: Applicable to bands defined within the frequency spectrum range of 43.5 – 48.2 GHz. + +The absolute total power measurement shall not exceed the OTA CACLR absolute limit specified in table 6.7.3.5.2-4a. + +**Table 6.7.3.5.2-4a: BS type 2-O CACLR absolute limit** + +| BS class | CACLR absolute limit (Note 1) | ACLR absolute limit (Note 2) | +|-----------------|-------------------------------|------------------------------| +| Wide area BS | -10.3 dBm/MHz | -10.1 dBm/MHz | +| Medium range BS | -17.3 dBm/MHz | -17.1 dBm/MHz | +| Local area BS | -17.3 dBm/MHz | -17.1 dBm/MHz | + +NOTE 1: Applicable to bands defined within the frequency spectrum range of 24.25 – 43.5 GHz +NOTE 2: Applicable to bands defined within the frequency spectrum range of 43.5 – 48.2 GHz + +**Table 6.7.3.5.2-5: 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. + +For *BS type 1-O*, for a *RIB* operating in multi-carrier or contiguous CA, the requirements apply to *BS 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. + +For *BS type 2-O*, for a *RIB* operating in multi-carrier or contiguous CA, the requirements apply to the frequencies 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 *BS type 1-O* is defined in TS 38.104 [2], clause 9.7.4.2. + +The minimum requirement for *BS type 2-O* is defined in TS 38.104 [2], clause 9.7.4.3. + +### 6.7.4.3 Test purpose + +This test measures the emissions of the BS, close to the assigned channel bandwidth of the wanted signal, while the BS 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. + +*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. + +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). + +#### 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. When calibrated and operated within the guidance of 3GPP TR 37.941 [29] the measurement methods are applicable and selected depending on availability at the test facility. + +- 1) Place the BS at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (D.2) of the BS 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. + +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 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 for FR1 and Table 4.1.2.2-2 for FR2. + +- 4) For single carrier operation, set the BS 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 BS declared to be capable of multi-carrier and/or CA operation, use the applicable test signal configuration and corresponding power setting specified in clause 4.7.2 and 4.8 using the corresponding test model(s) in clause 4.9.2 on all carriers configured. + +- 5) Orient the positioner (and BS) in order that the direction to be tested aligns with the test antenna such that measurements to determine TRP can be performed (see annex 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 $TRP_{\text{Estimate}}$ (see annex I). +- 8) Calculate $TRP_{\text{Estimate}}$ using the measurements made in step 6. +- 9) For *BS 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 BS 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_{\max}$ is equal to $f\_offset_{\max}$ minus half of the bandwidth of the measuring filter. + +For a *multi-band RIB* inside any *Inter RF Bandwidth gaps* with $W_{\text{gap}} < 2 * \Delta f_{\text{OBUE}}$ , emissions shall not exceed the cumulative sum of the test requirements specified at the *Base Station RF Bandwidth edges* on each side of the *Inter RF Bandwidth gap*. The test requirement for *Base Station RF Bandwidth edge* is specified in 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 *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 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_{\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 limit of the band where there are carriers transmitted, as defined in the tables of the present clause, shall apply across both downlink bands. +- In other cases, the operating band unwanted emission limit of the band where there are carriers transmitted, as defined in the tables of the present clause for the largest frequency offset ( $\Delta f_{\max}$ ), shall apply from $\Delta f_{\text{OBUE}}$ MHz below the lowest frequency, up to $\Delta f_{\text{OBUE}}$ MHz above the highest frequency of the supported downlink operating band without any carrier transmitted. + +For a multicarrier *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 BS (Category A) + +For a *RIB* operating in Bands n5, n8, n12, n13, n14, n26, n28, n29, n71, n85, n106, emissions shall not exceed the maximum levels specified in table 6.7.4.5.1.1-1. + +**Table 6.7.4.5.1.1-1: Wide Area BS operating band unwanted emission limits +(NR bands $\leq 1$ GHz) for Category A** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (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 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 -4 dBm/100 kHz. + +NOTE 2: For a *multi-band RIB* 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}$ . + +NOTE 4: The test requirement is derived from the basic limit a scaling factor of 9 dB and any applicable TT. + +NOTE 5: Void + +For a RIB operating in Bands n1, n2, n3, n7, n25, n30, n34, n38, n39, n40, n41, n50, n54, n65, n66, n70, n74, n75, n77, n78, n79, n109 emissions shall not exceed the maximum levels specified in tables 6.7.4.5.1.1-2 to 6.7.4.5.1.1-4: + +**Table 6.7.4.5.1.1-2: Wide Area BS operating band unwanted emission limits +(1 GHz $<$ NR bands $\leq 3$ GHz) for Category A** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (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}$ | -4 dBm (Note 3) | 1 MHz | + +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 -4 dBm/1 MHz. + +NOTE 2: For a *multi-band RIB* 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}$ . + +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.5.1.1-3: Wide Area BS *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 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 -4 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. | | | | +| NOTE 5: Void | | | | + +**Table 6.7.4.5.1.1-4: Wide Area BS *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 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 -4 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. | | | | +| NOTE 5: Void | | | | + +#### 6.7.4.5.1.2 Wide Area BS Category B (Option 1) + +For Category B operating band unwanted emissions, there are two options for the limits that may be applied regionally. option 1 is as follows. + +For a *RIB* operating in Bands n5, n8, n12, n20, n26, n28, n29, n67, n71, n85, emissions shall not exceed the maximum levels specified in table 6.7.4.5.1.2-1: + +**Table 6.7.4.5.1.2-1: Wide Area BS operating band unwanted emission limits +(NR bands $\leq 1$ GHz) for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (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}$ | -7 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 -7 dBm/ 100 kHz. | | | | +| NOTE 2: For a multi-band RIB 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}$ . | | | | +| NOTE 4: The test requirement is derived from the basic limit a scaling factor of 9 dB and any applicable TT. | | | | +| NOTE 5: Void | | | | + +For a *RIB* operating in Bands n1, n2, n3, n7, n25, n34, n38, n39, n40, n41, n50, n65, n66, n70, n75, n77, n78, n79, n104, n109 emissions shall not exceed the maximum levels specified in tables 6.7.4.5.1.2-2 to 6.7.4.5.1.2-5: + +**Table 6.7.4.5.1.2-2: Wide Area BS operating band unwanted emission limits +( $1 \text{ GHz} < \text{NR bands} \leq 3 \text{ GHz}$ ) for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (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 (Note 3) | 1 MHz | +| 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 -6 dBm/1 MHz. | | | | +| NOTE 2: For a multi-band RIB 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}$ . | | | | +| 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.5.1.2-3: Wide Area BS operating band unwanted emission limits +(3 GHz < NR bands ≤ 4.2 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 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 -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. | | | | +| NOTE 5: Void | | | | + +**Table 6.7.4.5.1.2-4: Wide Area BS 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 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 -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. | | | | +| NOTE 5: Void | | | | + +**Table 6.7.4.5.1.2-5: Wide Area BS operating band unwanted emission limits +(6 GHz < NR bands ≤ 7.125 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, 5) | Measurement bandwidth | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------|----------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 50 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 50.05 \text{ MHz}$ | | 100 kHz | +| (Note 4) | | | | +| $50 \text{ MHz} \leq \Delta f \leq \min(100 \text{ MHz}, \Delta f_{max})$ | $50.05 \text{ MHz} \leq f\_offset < \min(100.05 \text{ MHz}, f\_offset_{max})$ | -3 dBm | 100 kHz | +| $100 \text{ MHz} \leq \Delta f \leq \Delta f_{max}$ | $100.5 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | - 6 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 100 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the minimum requirement within sub-block gaps shall be -6 dBm/1MHz. | | | | +| NOTE 2: For a multi-band connector with Inter RF Bandwidth gap $< 2 * \Delta f_{OBU E}$ 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} < 100 \text{ MHz}$ . | | | | +| NOTE 4: This frequency range ensures that the range of values of $f\_offset$ is continuous. | | | | +| NOTE 5: The test requirement is derived from the basic limit a scaling factor of 9 dB and any applicable TT. | | | | + +#### 6.7.4.5.1.3 Wide Area BS Category B (Option 2) + +The limits in this clause are intended for Europe and may be applied regionally for a *RIB* operating in bands n1, n3, n8. + +For a *RIB* operating in bands n1, n3, n8, n65 emissions shall not exceed the maximum levels specified in table 6.7.4.5.1.3-1: + +**Table 6.7.4.5.1.3-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, 5) | Measurement bandwidth | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------|----------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.2 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.215 \text{ MHz}$ | -3.2 dBm | 30 kHz | +| $0.2 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.215 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | | 30 kHz | +| (Note 4) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -15.2 dBm | 30 kHz | +| $1 \text{ MHz} \leq \Delta f \leq \min(10 \text{ MHz}, \Delta f_{max})$ | $1.5 \text{ MHz} \leq f\_offset < \min(10.5 \text{ MHz}, f\_offset_{max})$ | -2.2 dBm | 1 MHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | - 6 dBm (Note 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 -6 dBm/1MHz. | | | | +| NOTE 2: For a multi-band connector with Inter RF Bandwidth gap $< 2 * \Delta f_{OBU E}$ 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: The test requirement is derived from the basic limit a scaling factor of 9 dB and any applicable TT. | | | | +| NOTE 6: Void | | | | + +#### 6.7.4.5.1.4 Medium Range BS (Category A and Category B) + +For Medium Range BS class in NR bands $\leq 3$ GHz, emissions shall not exceed the maximum levels specified in tables 6.7.4.5.1.4-1 and 6.7.4.5.1.4-4. + +For Medium Range BS class in 3GHz $<$ NR bands $\leq 4.2$ GHz, emissions shall not exceed the maximum levels specified in tables 6.7.4.5.1.4-2 and 6.7.4.5.1.4-5. + +For Medium Range BS class in 4.2GHz $<$ NR bands $\leq 6$ GHz, emissions shall not exceed the maximum levels specified in tables 6.7.4.5.1.4-3 and 6.7.4.5.1.4-6. + +For Medium Range BS class in 6.0 GHz $<$ NR bands $\leq 7.125$ GHz, emissions shall not exceed the maximum levels specified in tables 6.7.4.5.1.4-3a and 6.7.4.5.1.4-7. + +**Table 6.7.4.5.1.4-1: Medium Range BS operating band unwanted emission limits, $40 < P_{\text{rated,c,TRP}} \leq 47$ 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}$ | | 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 \text{ dB}$ | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $\min(P_{\text{rated,c,TRP}} - 60 \text{ dB}, -16 \text{ dBm})$
(Note 3) | 100 kHz | + +NOTE 1: For a BS supporting non-contiguous spectrum operation within any *operating band* the emission limits within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the emission limits within sub-block gaps shall be $\min(P_{\text{rated,c,TRP}} - 60 \text{ dB}, -16 \text{ dBm})/100 \text{ KHz}$ . + +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. + +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.5.1.4-2: Medium Range BS operating band unwanted emission limits, $40 < P_{\text{rated,c,TRP}} \leq 47$ 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}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | $P_{\text{rated,c,TRP}} - 58 \text{ dB}$ | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $\min(P_{\text{rated,c,TRP}} - 60 \text{ dB}, -16 \text{ dBm})$
(Note 3) | 100 kHz | + +NOTE 1: For a BS supporting non-contiguous spectrum operation within any *operating band* the emission limits within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the emission limits within sub-block gaps shall be $\min(P_{\text{rated,c,TRP}} - 60 \text{ dB}, -16 \text{ dBm})/100 \text{ KHz}$ . + +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. + +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.5.1.4-3: Medium Range BS operating band unwanted emission limits, $40 < P_{\text{rated,c,TRP}} \leq 47$ 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}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | $P_{\text{rated,c,TRP}} - 58 \text{ dB}$ | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $\min(P_{\text{rated,c,TRP}} - 60 \text{ dB}, -16 \text{ dBm})$
(Note 3) | 100 kHz | + +NOTE 1: For a BS supporting non-contiguous spectrum operation within any *operating band* the emission limits within sub-block gaps is calculated as a cumulative sum of contributions from adjacent sub blocks on each side of the sub block gap. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub blocks on each side of the sub-block gap, where the emission limits within sub-block gaps shall be $\min(P_{\text{rated,c,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. + +NOTE 5: Void + +**Table 6.7.4.5.1.4-3a: Medium Range BS operating band unwanted emission limits, $40 < P_{\text{rated,c,TRP}} \leq 47$ dBm (for 6.0 GHz < NR bands $\leq 7.125$ 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 < 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 \text{ dB}$ | 100 kHz | +| $100 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $100.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $\min(P_{\text{rated,x}} - 60 \text{ dB}, -16 \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 $\min(P_{\text{rated,x}} - 60 \text{ dB}, -16 \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}$ . + +NOTE 4: The test requirement is derived from the basic limit applying a scaling factor of 9 dB and any applicable TT. + +**Table 6.7.4.5.1.4-4: Medium Range BS operating band unwanted emission limits, $P_{\text{rated,c,TRP}} \leq 40$ 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}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -18.2 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -20 dBm (Note 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 -20 dBm/100 KHz. + +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. + +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.5.1.4-5: Medium Range BS operating band unwanted emission limits, $P_{\text{rated,c,TRP}} \leq 40$ 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}$ | | 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 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 -20 dBm/100 KHz. + +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. + +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.5.1.4-6: Medium Range BS operating band unwanted emission limits, $P_{\text{rated,c,TRP}} \leq 40$ 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}$ | | 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 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 -20 dBm/100 KHz. + +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. + +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.5.1.4-7: Medium Range BS operating band unwanted emission limits, $P_{\text{rated,c,TRP}} \leq 40$ dBm +(for 6.0 GHz < NR bands $\leq$ 7.125 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 < 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})$ | -18 dBm | 100 kHz | +| $100 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $100.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -20 dBm | 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 -20 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} < 100 \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.5.1.5 Local Area BS (Category A and Category B) + +For Local Area BS class in NR bands $\leq 3 \text{ GHz}$ , emissions shall not exceed the maximum levels specified in table 6.7.4.5.1.5-1. + +For Local Area BS class 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.5.1.5-2. + +For Local Area BS class 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.5.1.5-3. + +For Local Area BS class in $6.0 \text{ GHz} < \text{NR bands} \leq 7.125 \text{ GHz}$ , emissions shall not exceed the maximum levels specified in tables 6.7.4.5.1.5-4. + +**Table 6.7.4.5.1.5-1: Local Area BS 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}$ | | 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 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 -28 dBm/100 KHz. + +NOTE 2: For a *multi-band RIB* 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}$ . + +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.5.1.5-2: Local Area BS 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}$ | | 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 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 -28 dBm/100 KHz. + +NOTE 2: For a *multi-band RIB* 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}$ . + +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.5.1.5-3: Local Area BS operating band unwanted emission limits ( $4.2 \text{ GHz} < \text{NR bands} \leq 6 \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}$ | | 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 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 -28 dBm/100 KHz. + +NOTE 2: For a *multi-band RIB* 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}$ . + +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.5.1.5-4: Local Area BS operating band unwanted emission limits (for 6.0 GHz < NR bands $\leq$ 7.125 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 < 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})$ | -26 dBm | 100 kHz | +| $100 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $100.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -28 dBm | 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 -28 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} < 100 \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.5.1.6 Additional requirements + +## 6.7.4.5.1.6.1 Limits in FCC Title 47 + +In addition to the requirements in tables 6.7.4.5.1.1-1 to 6.7.4.5.1.5-3, the BS 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.5.1.6.2 Protection of DTT + +In certain regions the following requirement may apply for protection of DTT. For *BS type 1-O* 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.7.4.5.1.6.2-1, shall not exceed the maximum emission TRP level shown in the table. This requirement applies in the frequency range 470-790 MHz even though part of the range falls in the spurious domain. + +**Table 6.7.4.5.1.6.2-1: Declared emissions levels for protection of DTT** + +| Case | Measurement filter centre frequency | Condition on BS maximum aggregate EIRP / 10 MHz, $P_{\text{EIRP\_10MHz}}$ (NOTE) | Maximum level $P_{\text{EIRP,N,MAX}}$ | Measurement bandwidth | +|---------------------------------------------------------------------------------------------|-----------------------------------------------|----------------------------------------------------------------------------------|-------------------------------------------|-----------------------| +| A: for DTT frequencies where broadcasting is protected | $N*8 + 306 \text{ MHz}$ , $21 \leq N \leq 60$ | $P_{\text{EIRP\_10MHz}} \geq 59 \text{ dBm}$ | 0 dBm | 8 MHz | +| | $N*8 + 306 \text{ MHz}$ , $21 \leq N \leq 60$ | $36 \leq P_{\text{EIRP\_10MHz}} < 59 \text{ dBm}$ | $P_{\text{EIRP\_10MHz}} - 59 \text{ dBm}$ | 8 MHz | +| | $N*8 + 306 \text{ MHz}$ , $21 \leq N \leq 60$ | $P_{\text{EIRP\_10MHz}} < 36 \text{ dBm}$ | -23 dBm | 8 MHz | +| B: for DTT frequencies where broadcasting is subject to an intermediate level of protection | $N*8 + 306 \text{ MHz}$ , $21 \leq N \leq 60$ | $P_{\text{EIRP\_10MHz}} \geq 59 \text{ dBm}$ | 10 dBm | 8 MHz | +| | $N*8 + 306 \text{ MHz}$ , $21 \leq N \leq 60$ | $36 \leq P_{\text{EIRP\_10MHz}} < 59 \text{ dBm}$ | $P_{\text{EIRP\_10MHz}} - 49 \text{ dBm}$ | 8 MHz | +| | $N*8 + 306 \text{ MHz}$ , $21 \leq N \leq 60$ | $P_{\text{EIRP\_10MHz}} < 36 \text{ dBm}$ | -13 dBm | 8 MHz | +| C: for DTT frequencies where broadcasting is not protected | $N*8 + 306 \text{ MHz}$ , $21 \leq N \leq 60$ | N.A. | 22 dBm | 8 MHz | + +NOTE: $P_{\text{EIRP\_10MHz}}$ (dBm) is defined by $P_{\text{EIRP\_10MHz}} = P_{10 \text{ MHz}} + G_{\text{ant}} + 9 \text{ dB}$ , where $G_{\text{ant}}$ is 17 dBi. + +#### 6.7.4.5.1.6.3 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-O* operating in Band n24 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.7.4.5.1.6.3-1 shall not exceed the maximum emission TRP limits indicated in the table. This requirement applies in the frequency range 1541-1650 MHz even though part of the range falls in the spurious domain. + +**Table 6.7.4.5.1.6.3-1: Emissions levels for protection of GPS** + +| Operating Band | Frequency range (MHz) | Emission level (dBW)
(Measurement bandwidth = 1 MHz) | Emission level (dBW)
of discrete emissions
of less than 700 Hz
bandwidth
(Measurement
bandwidth = 1 kHz) | Emission level (dBW) of
discrete emissions of
less than 2 kHz
bandwidth
(Measurement
bandwidth = 1 kHz) | +|----------------|-----------------------|---------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------| +| n24 | 1541 - 1559 | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | +| | 1559 - 1610 | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | | +| | 1610 - 1650 | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | | + +Note: The regional requirements 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). $P_{\text{EIRP}}$ values in table 6.7.4.5.1.6.3-1 are the effective isotropic power (or radiated power spectral density) set in the FCC Order DA 20-48 for the specified frequency ranges and bandwidths. + +#### 6.7.4.5.1.6.4 Additional limits for BS operating in Bands n50, n51, n74, n75, n76 + +For BS operating in bands n50, n51, n74, n75 and n76 additional emission limits that might be applicable in the OBUE frequency domain are specified in clause 6.7.5.4.5. + +### 6.7.4.5.2 BS type 2-O + +#### 6.7.4.5.2.1 General + +The requirements of either clause 6.7.4.5.2.2 (Category A limits) or clause 6.7.4.5.2.3 (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 (*BS 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_{\text{offset}}$ is the separation between the *contiguous transmission bandwidth* edge frequency and the centre of the measuring filter. +- $f_{\text{offsetmax}}$ is the offset to the frequency $\Delta f_{\text{OBUE}}$ outside the downlink *operating band*, 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. + +**Table 6.7.4.5.2-1: Void****Table 6.7.4.5.2-2: Void** + +#### 6.7.4.5.2.2 OTA operating band unwanted emission limits (Category A) + +The power of unwanted emission shall not exceed the limits in table 6.7.4.5.2.2-1, 6.7.4.5.2.2-2 or 6.7.4.5.2.2-3. + +**Table 6.7.4.5.2.2-1: OBUE limits applicable 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 * BW_{contiguous}$ | $0.5 \text{ MHz} \leq f\_offset < 0.1 * BW_{contiguous} + 0.5 \text{ MHz}$ | $\text{Min}(-2.3 \text{ dBm}, \text{Max}(P_{rated,t,TRP} - 32.3 \text{ dB}, -9.3 \text{ dBm}))$ | 1 MHz | +| $0.1 * BW_{contiguous} \leq \Delta f < \Delta f_{max}$ | $0.1 * BW_{contiguous} + 0.5 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | $\text{Min}(-13 \text{ dBm}, \text{Max}(P_{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.5.2.2-2: OBUE limits applicable in the frequency range 37– 43.5 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 * BW_{contiguous}$ | $0.5 \text{ MHz} \leq f\_offset < 0.1 * BW_{contiguous} + 0.5 \text{ MHz}$ | $\text{Min}(-2.3 \text{ dBm}, \text{Max}(P_{rated,t,TRP} - 30.3 \text{ dB}, -9.3 \text{ dBm}))$ | 1 MHz | +| $0.1 * BW_{contiguous} \leq \Delta f < \Delta f_{max}$ | $0.1 * BW_{contiguous} + 0.5 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | $\text{Min}(-13 \text{ dBm}, \text{Max}(P_{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.5.2.2-3: OBUE limits applicable in the frequency range 43.5– 48.2 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 * BW_{contiguous}$ | $0.5 \text{ MHz} \leq f\_offset < 0.1 * BW_{contiguous} + 0.5 \text{ MHz}$ | $\text{Min}(-2.1 \text{ dBm}, \text{Max}(P_{rated,t,TRP} - 30.1 \text{ dB}, -9.1 \text{ dBm}))$ | 1 MHz | +| $0.1 * BW_{contiguous} \leq \Delta f < \Delta f_{max}$ | $0.1 * BW_{contiguous} + 0.5 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | $\text{Min}(-13 \text{ dBm}, \text{Max}(P_{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.5.2.2-4: OBUE limits applicable in the frequency range 52.6 – 71 GHz** + +| Frequency offset of measurement filter -3B point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | 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}(-0.3 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 26.3 \text{ dB}, -7.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}} - 39 \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.5.2.3 OTA operating band unwanted emission limits (Category B) + +The power of unwanted emission shall not exceed the limits in table 6.7.4.5.2.3-1, 6.7.4.5.2.3-2 or 6.7.4.5.2.3-3. + +**Table 6.7.4.5.2.3-1: OBUE limits applicable 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*, where the contribution from the far-end *sub-block* shall be scaled according to the measurement bandwidth of the near-end *sub-block*. +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.5.2.3-2: OBUE limits applicable in the frequency range 37 – 43.5 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*, where the contribution from the far-end *sub-block* shall be scaled according to the measurement bandwidth of the near-end *sub-block*. +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.5.2.3-3: OBUE limits applicable in the frequency range 43.5 – 48.2 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}} - 30.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}} - 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, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. + +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.5.2.3-4: OBUE limits applicable in the frequency range 52.6 – 71 GHz** + +| Frequency offset of measurement filter -3 dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | 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}(-0.3 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 26.3 \text{ dB}, -7.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}} - 39 \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}} - 29 \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, where the contribution from the far-end sub-block shall be scaled according to the measurement bandwidth of the near-end sub-block. + +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.5.2.4 Additional OTA operating band unwanted emission limits + +##### 6.7.4.5.2.4.1 Protection of Earth Exploration Satellite Service + +For BS 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.5.2.4.1-1. + +**Table 6.7.4.5.2.4.1-1: BS radiated limits for protection of EESS** + +| 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 BS brought into use on or before 1 September 2027. + +NOTE 2: This limit applies to BS brought into use after 1 September 2027. + +## 6.7.5 OTA transmitter spurious emissions + +### 6.7.5.1 General + +Unless otherwise stated, all requirements are measured as mean power. + +The OTA transmitter spurious emissions limits are specified as TRP per RIB, unless otherwise stated. + +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 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 downlink *operating band*, as specified in ITU-R recommendation SM.329 [5]. + +For *multi-band RIB* each supported *operating band* and the $\Delta f_{\text{OBUE}}$ MHz around each band are excluded from the OTA transmitter spurious emissions requirements. + +Additional limits in clause 6.7.5.4.5 may apply closer than $\Delta f_{\text{OBUE}}$ from the edges of *downlink operating band*. + +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. + +*BS type 1-O* requirements consists of OTA transmitter spurious emission requirements based on TRP and co-location requirements not based on TRP. + +The OTA transmitter spurious emission limits for FR2 shall apply from 30 MHz to 2nd harmonic of the upper frequency edge of the downlink *operating band*, 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 clause 6.7.1. + +## 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 *BS type 1-O* is specified in TS 38.104 [2], clause 9.7.5.2.2. + +The minimum requirement for *BS type 2-O* is specified in TS 38.104 [2], clause 9.7.5.3.2. + +### 6.7.5.2.3 Test purpose + +The test purpose is to verify if the radiated spurious emissions from the BS 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_{\text{DL\_low}} - \Delta f_{\text{OBUE}}$ + - T when testing from $F_{\text{DL\_high}} + \Delta f_{\text{OBUE}}$ to 12.75 GHz (or to 5th harmonic) +- For FR2: + - B when testing from 30 MHz to $F_{\text{DL\_low}} - \Delta f_{\text{OBUE}}$ + - T when testing from $F_{\text{DL\_high}} + \Delta f_{\text{OBUE}}$ 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_{\text{RFBW}}$ when testing from 30 MHz to $F_{\text{DL\_low}} - \Delta f_{\text{OBUE}}$ + - $T_{\text{RFBW}}$ when testing from $F_{\text{DL\_high}} + \Delta f_{\text{OBUE}}$ to 12.75 GHz (or 5th harmonic) +- For FR2: + - $B_{\text{RFBW}}$ when testing from 30 MHz to $F_{\text{DL\_low}} - \Delta f_{\text{OBUE}}$ + - $T_{\text{RFBW}}$ when testing from $F_{\text{DL\_high}} + \Delta f_{\text{OBUE}}$ to 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_{\text{RFBW\_T'RFBW}}$ when testing from 30 MHz to $F_{\text{DL\_Blow\_low}} - \Delta f_{\text{OBUE}}$ + - $B'_{\text{RFBW\_T'RFBW}}$ when testing from $F_{\text{DL\_Bhigh\_high}} + \Delta f_{\text{OBUE}}$ to 12.75 GHz (or to 5th harmonic) + - $B_{\text{RFBW\_T'RFBW}}$ and $B'_{\text{RFBW\_T'RFBW}}$ when testing from $F_{\text{DL\_Blow\_high}} + \Delta f_{\text{OBUE}}$ to $F_{\text{DL\_Bhigh\_low}} - \Delta f_{\text{OBUE}}$ + +Directions to be tested: As the requirement is TRP the beam pattern(s) may be set up to optimise the TRP measurement procedure (see annex I). + +#### 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. When calibrated and operated within the guidance of 3GPP TR 37.941 [29] the measurement methods are applicable and selected depending on availability at the test facility. + +- 1) Place the BS at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (D.2) of the BS 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. + - 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 for FR1 and Table 4.1.2.2-2 for FR2. +- 5) Set the BS 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. NR-FR1-TM1.1 for *BS type 1-O* and NR-FR2-TM1.1 for *BS 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. +- 6) Orient the positioner (and BS) in order that the direction to be tested aligns with the test antenna such that measurements to determine TRP can be performed (see annex 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 *BS 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 *BS type 1-O* + +For a BS 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 OTA BS transmitter spurious emission limits for *BS type 1-O*, 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 | +| 12.75 GHz - 26 GHz | -13 + X dBm | 1 MHz | Note 1, Note 2, Note 6, Note 7 | +| 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: Void.
NOTE 5: Void.
NOTE 6: X = 9 dB, unless stated differently in regional regulation.
NOTE 7: Applies for Band for which the upper frequency edge of the DL operating band is greater than 5.2 GHz. | | | | + +For a BS 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 OTA BS transmitter spurious emission limits for *BS type 1-O*, 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 | -30 + X dBm | 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 | +| 12.75 GHz - 26 GHz | -30 + X dBm | 1 MHz | Note 1, Note 2, Note 5, 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 DL operating band is greater than 2.55 GHz and less than or equal to 5.2 GHz.
NOTE 4: Void.
NOTE 5: X = 9 dB, unless stated differently in regional regulation.
NOTE 6: Applies for Band for which the upper frequency edge of the DL operating band is greater than 5.2 GHz. | | | | + +#### 6.7.5.2.5.2 Test requirement for BS 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. + +**Table 6.7.5.2.5.2-1: Void** + +NOTE: Table 6.7.5.2.5.2-1 is moved to clause 6.7.5.2.5.2.2 as table 6.7.5.2.5.2.2-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-1. + +**Table 6.7.5.2.5.2.2-1: General OTA BS transmitter spurious emission limits for BS type 2-O** + +| 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 [5], s4.1. +NOTE 2: Upper frequency as in ITU-R SM.329 [5], 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: BS radiated Tx spurious emission limits in FR2 (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(2nd 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 [5], s4.1 +NOTE 2: Limit and bandwidth as in ERC Recommendation 74-01 [26], annex 2. +NOTE 3: Upper frequency as in ITU-R SM.329 [5], 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 BS radiated Tx spurious emission limits in FR2 (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 [26], 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 Protection of the BS receiver of own or different BS + +#### 6.7.5.3.1 Definition and applicability + +This requirement shall be applied for NR FDD operation in order to prevent the receivers of own or a different BS of the same band being desensitised by emissions from a *BS type 1-O*. + +This requirement is a co-location requirement as defined in clause 4.9, in TS 38.104 [2], the power levels are specified at the CLTA output. + +#### 6.7.5.3.2 Minimum requirements + +The minimum requirement for *BS type 1-O* is defined in TS 38.104 [2], clause 9.7.5.2. + +#### 6.7.5.3.3 Test purpose + +For OTA co-location spurious emission, the test purpose is to verify that the emission is within the specified requirement limits at the CLTA conducted output(s). + +#### 6.7.5.3.4 Method of test + +##### 6.7.5.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. + +*Base Station 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 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.3.4.2 Procedure + +- 1) Select and place the NR BS 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 NR BS as depicted in annex E.1.3. +- 4) The test antenna shall be dual (or single) polarized with the same frequency range as the NR BS 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 analyzer) characteristics shall be: + +- Detection mode: True RMS. + +The emission power should be averaged over an appropriate time duration to ensure the measurement is within the measurement uncertainty in Table 4.1.2.2-1. + +8) Set the *BS type 1-O* to transmit: + +- Set the NR BS 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 NR BS declared to be capable of multi-carrier and/or 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 clause 4.7.2 and 4.8. + +9) Measure the emission at the specified frequencies with specified measurement bandwidth. + +NOTE: An alternative measurement method to be used for measuring the OTA emission is described in annex K. + +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.3.5 Test requirements + +#### 6.7.5.3.5.1 Test requirement for *BS type 1-O* + +This requirement shall be applied for NR FDD operation in order to prevent the receivers of own or a different BS of the same band being desensitised by emissions from a *BS type 1-O*. + +This requirement is a co-location requirement as defined in clause 4.9, in TS 38.104 [2], the power levels are specified at the CLTA output. + +The total power of any spurious emission from both polarizations of the CLTA connector output shall not exceed the limits in table 6.7.5.3.5.1-1. + +**Table 6.7.5.3.5.1-1: BS type 1-O OTA spurious emissions limits for protection of the BS receiver** + +| BS class | Frequency range | Maximum Level for bands below 3GHz | Maximum Level for bands between 3 and 4.2GHz | Maximum Level for bands between 4.2 and 7.125 GHz | Measurement bandwidth | +|-----------------|------------------------------|------------------------------------|----------------------------------------------|---------------------------------------------------|-----------------------| +| Wide Area BS | $F_{UL\_low} - F_{UL\_high}$ | -113.9 dBm | -113.7 dBm | -113.6 dBm | 100 kHz | +| Medium Range BS | | -108.9 dBm | -108.7 dBm | -108.6 dBm | | +| Local Area BS | | -105.9 dBm | -105.7 dBm | -105.6 dBm | | + +### 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 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.). + +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 *BS type 1-O* is specified in TS 38.104 [2], clause 9.7.5.2.4. + +The minimum requirement for *BS type 2-O* is specified in TS 38.104 [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 BS 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}$ + - 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 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}$ + - $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 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}$ + - $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 requirements are TRP the beam pattern(s) may be set up to optimise the TRP measurement procedure (see annex I). + +#### 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. When calibrated and operated within the guidance of 3GPP TR 37.941 [29] the measurement methods are applicable and selected depending on availability at the test facility. + +- 1) Place the BS at the positioner. + +- 2) Align the manufacturer declared coordinate system orientation (D.2) of the BS 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. + - 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 for FR1 and Table 4.1.2.2-2 for FR2. +- 5) Set the BS 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 (NR-FR1-TM1.1 for *BS type 1-O* and NR-FR2-TM1.1 for *BS 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 NR-FR1-TM1.1 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. +- 6) Orient the positioner (and BS) in order that the direction to be tested aligns with the test antenna such that measurements to determine TRP can be performed (see annex 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 *BS 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 BS where requirements for co-existence with the system listed in the first column apply. For a *multi-band RIB*, the exclusions and conditions in the Note column of table 6.7.5.4.5-1 apply for each supported *operating band*. + +**Table 6.7.5.4.5-1: BS spurious emissions test 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 | Test limit | Measurement bandwidth | Notes | +|---------------------------------------------------------------|----------------------------------------------|------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GSM900 | 921 – 960 MHz | -45.4 dBm | 100 kHz | This requirement does not apply to BS operating in band n8. | +| | 876 – 915 MHz | -49.4 dBm | 100 kHz | For the frequency range 880-915 MHz, this requirement does not apply to BS operating in band n8, since it is already covered by the requirement in clause 6.7.5.3. | +| DCS1800 | 1805 – 1880 MHz | -35.4 dBm | 100 kHz | This requirement does not apply to BS operating in band n3. | +| | 1710 – 1785 MHz | -49.4 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.7.5.3. | +| PCS1900 | 1930 – 1990 MHz | -35.4 dBm | 100 kHz | This requirement does not apply to BS operating in band n2, n25 or band n70. | +| | 1850 – 1910 MHz | -49.4 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.7.5.3. | +| GSM850 or CDMA850 | 869 – 894 MHz | -45.4 dBm | 100 kHz | This requirement does not apply to BS operating in band n5 or n26. | +| | 824 – 849 MHz | -49.4 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.7.5.3. | +| UTRA FDD Band I or E-UTRA Band 1 or NR Band n1 | 2110 – 2170 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band n1 or n65. | +| | 1920 – 1980 MHz | -37.4 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.7.5.3. | +| UTRA FDD Band II or E-UTRA Band 2 or NR Band n2 | 1930 – 1990 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band n2 or n70. | +| | 1850 – 1910 MHz | -37.4 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.7.5.3. | +| UTRA FDD Band III or E-UTRA Band 3 or NR Band n3 | 1805 – 1880 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band n3. | +| | 1710 – 1785 MHz | -37.4 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.7.5.3. | +| UTRA FDD Band IV or E-UTRA Band 4 | 2110 – 2155 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band n66. | +| | 1710 – 1755 MHz | -37.4 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.7.5.3. | +| UTRA FDD Band V or E-UTRA Band 5 or NR Band n5 | 869 – 894 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band n5 or n26. | +| | 824 – 849 MHz | -37.4 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.7.5.3. | +| UTRA FDD Band VI, XIX or E-UTRA Band 6, 18, 19 or NR Band n18 | 860 – 890 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band n18. | +| | 815 – 830 MHz | -37.4 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.7.5.3. | +| | 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 | This requirement does not apply to BS operating in band n7. | +| | 2500 – 2570 MHz | -37.4 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.7.5.3. | +| UTRA FDD Band VIII or E-UTRA Band 8 or NR Band n8 | 925 – 960 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band n8. | +| | 880 – 915 MHz | -37.4 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.7.5.3. | + +| System type for NR to co-exist with | Frequency range for co-existence requirement | Test limit | Measurement bandwidth | Notes | +|-----------------------------------------------------|----------------------------------------------|------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UTRA FDD Band IX or E-UTRA Band 9 | 1844.9 – 1879.9 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band n3. | +| | 1749.9 – 1784.9 MHz | -37.4 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.7.5.3. | +| UTRA FDD Band X or E-UTRA Band 10 | 2110 – 2170 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band n66 | +| | 1710 – 1770 MHz | -37.4 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.7.5.3. | +| UTRA FDD Band XI or XXI or E-UTRA Band 11 or 21 | 1475.9 – 1510.9 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band n50, n74, n75 or n109. | +| | 1427.9 – 1447.9 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band n50, n51, n74, n75, n76 or n109. | +| | 1447.9 – 1462.9 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band n50, n74, n75 or n109. | +| UTRA FDD Band XII or E-UTRA Band 12 or NR Band n12 | 729 – 746 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band n12 or n85. | +| | 699 – 716 MHz | -37.4 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.7.5.3.
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 | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band n13. | +| | 777 – 787 MHz | -37.4 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.7.5.3. | +| UTRA FDD Band XIV or E-UTRA Band 14 or NR Band n14 | 758 – 768 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band n14. | +| | 788 – 798 MHz | -37.4 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.7.5.3. | +| E-UTRA Band 17 | 734 – 746 MHz | -40.4 dBm | 1 MHz | | +| | 704 – 716 MHz | -37.4 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 | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band n20 or n28. | +| | 832 – 862 MHz | -37.4 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.7.5.3. | +| UTRA FDD Band XXII or E-UTRA Band 22 | 3510 – 3590 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in Band n77 or n78. | +| | 3410 – 3490 MHz | -37 dBm | 1 MHz | This requirement does not apply to BS operating in Band n77 or n78. | +| E-UTRA Band 24 or NR Band n24 | 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 | This requirement does not apply to BS operating in band n2, n25 or n70. | +| | 1850 – 1915 MHz | -37.4 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.7.5.3. For BS operating in Band n2, it applies for 1910 MHz to 1915 MHz, while the rest is covered in clause 6.7.5.3. | +| UTRA FDD Band XXVI or | 859 – 894 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band n5 or n26. | + +| System type for NR to co-exist with | Frequency range for co-existence requirement | Test limit | Measurement bandwidth | Notes | +|---------------------------------------------------|----------------------------------------------|------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| E-UTRA Band 26 or NR Band n26 | 814 – 849 MHz | -37.4 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.7.5.3. For BS operating in Band n5, it applies for 814 MHz to 824 MHz, while the rest is covered in clause 6.7.5.3. | +| E-UTRA Band 27 | 852 – 869 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band n5. | +| | 807 – 824 MHz | -37.4 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 | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band n20, n67 or n28. | +| | 703 – 748 MHz | -37.4 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.7.5.3. 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 | -40.4 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 | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band n30. | +| | 2305 – 2315 MHz | -37.4 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.7.5.3. | +| E-UTRA Band 31 or NR Band n31 | 462.5 -467.5 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band n31 or n72. | +| | 452.5 -457.5 MHz | -37.4 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.7.5.3. This requirement does not apply to BS operating in band n72. | +| UTRA FDD band XXXII or E-UTRA band 32 | 1452 – 1496 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band n50, n74, n75 or n109. | +| 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 | This requirement does not apply to BS operating in Band n34. | +| 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 | 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 | -40.4 dBm | 1 MHz | | +| UTRA TDD Band d) or E-UTRA Band 38 or NR Band n38 | 2570 – 2620 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band n38. | + +| System type for NR to co-exist with | Frequency range for co-existence requirement | Test limit | Measurement bandwidth | Notes | +|---------------------------------------------------|----------------------------------------------|------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UTRA TDD Band f) or E-UTRA Band 39 or NR band n39 | 1880 – 1920MHz | -40.4 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 | -40.4 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 | -40.4 dBm | 1 MHz | This is not applicable to BS operating in Band n41. | +| E-UTRA Band 42 | 3400 – 3600 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in Band n77 or n78. | +| E-UTRA Band 43 | 3600 – 3800 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in Band n77 or n78. | +| E-UTRA Band 44 | 703 – 803 MHz | -40.4 dBm | 1 MHz | This is not applicable to BS operating in Band n28. | +| 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 | 3550 – 3700 MHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in Band n77 or n78. | +| E-UTRA Band 50 or NR Band n50 | 1432 – 1517 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band n50, n51, n74, n75, n76 or n109. | +| E-UTRA Band 51 or NR Band n51 | 1427 – 1432 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band n50, n51, n75, n76 or n109. | +| E-UTRA Band 53 or NR Band n53 | 2483.5 - 2495 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band n41 or n90. | +| E-UTRA Band 54 or NR Band n54 | 1670 - 1675 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band n54 | +| E-UTRA Band 65 or NR Band n65 | 2110 – 2200 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band n1 or n65. | +| | 1920 – 2010 MHz | -37.4 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.7.5.3.
This requirement does not apply to BS operating in band n65, since it is already covered by the requirement in clause 6.7.5.3. | +| E-UTRA Band 66 or NR Band n66 | 2110 – 2200 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band n66. | +| | 1710 – 1780 MHz | -37.4 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.7.5.3. | +| E-UTRA Band 67 or NR Band n67 | 738 – 758 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band n28 or n67. | +| E-UTRA Band 68 | 753 -783 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band n28. | +| | 698-728 MHz | -37.4 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.7.5.3. | +| E-UTRA Band 69 | 2570 – 2620 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band n38. | + +| System type for NR to co-exist with | Frequency range for co-existence requirement | Test limit | Measurement bandwidth | Notes | +|-------------------------------------|----------------------------------------------|------------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| E-UTRA Band 70 or NR Band n70 | 1995 – 2020 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band n2, n25 or n70 | +| | 1695 – 1710 MHz | -37.4 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.7.5.3. | +| E-UTRA Band 71 or NR Band n71 | 617 – 652 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band n71 or n105 | +| | 663 – 698 MHz | -37.4 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.7.5.3. | +| E-UTRA Band 72 or NR Band n72 | 461 – 466 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band n31 or n72. | +| | 451 – 456 MHz | -37.4 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.7.5.3. This requirement does not apply to BS operating in band n31. | +| E-UTRA Band 74 or NR Band n74 | 1475 – 1518 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band n50, n74, n75 or n109. | +| | 1427 – 1470 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band n50, n51, n74, n75, n76 or n109. | +| E-UTRA Band 75 or NR Band n75 | 1432 – 1517 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band n50, n51, n74, n75, n76 or n109. | +| E-UTRA Band 76 or NR Band n76 | 1427 – 1432 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band n50, n51, n75, n76 or n109. | +| NR Band n77 | 3.3 – 4.2 GHz | -40 dBm | 1 MHz | This requirement does not apply to BS operating in Band n77 or n78 | +| NR Band n78 | 3.3 – 3.8 GHz | -40 dBm | 1 MHz | This requirement does not apply to BS 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 BS operating in Band n79 | +| NR Band n80 | 1710 – 1785 MHz | -37.4 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.7.5.3. | +| NR Band n81 | 880 – 915 MHz | -37.4 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.7.5.3. | +| NR Band n82 | 832 – 862 MHz | -37.4 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.7.5.3. | +| NR Band n83 | 703 – 748 MHz | -37.4 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.7.5.3. | +| NR Band n84 | 1920 – 1980 MHz | -37.4 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.7.5.3. | +| E-UTRA Band 85 or NR Band n85 | 728 – 746 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band n12 or n85. | +| | 698 – 716 MHz | -37.4 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.7.5.3. 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 | -37.4 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.7.5.3. | +| NR Band n89 | 824 – 849 MHz | -37.4 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.7.5.3. | +| NR Band n91 | 1427 – 1432 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band n50, n51, n75, n76 or n109. | + +| System type for NR to co-exist with | Frequency range for co-existence requirement | Test limit | Measurement bandwidth | Notes | +|-------------------------------------|----------------------------------------------|------------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 832 – 862 MHz | -37.4 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.7.5.3. | +| NR Band n92 | 1432 – 1517 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band n50, n51, n74, n75, n76 or n109. | +| | 832 – 862 MHz | -37.4 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.7.5.3. | +| NR Band n93 | 1427 – 1432 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band n50, n51, n75, n76 or n109. | +| | 880 – 915 MHz | -37.4 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.7.5.3. | +| NR Band n94 | 1432 – 1517 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band n50, n51, n74, n75, n76 or n109. | +| | 880 – 915 MHz | -37.4 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.7.5.3. | +| NR Band n95 | 2010 – 2025 MHz | -40.4 dBm | 1 MHz | | +| NR Band n96 | 5925 – 7125 MHz | -39.5 dBm | 1 MHz | This requirement does not apply to BS operating in Band n104. | +| NR Band n97 | 2300 – 2400MHz | -40.4 dBm | 1 MHz | NR Band n97 | +| NR Band n98 | 1880 – 1920MHz | -40.4 dBm | 1 MHz | | +| NR Band n99 | 1626.5 – 1660.5 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band n24, since it is already covered by the requirement in clause 6.7.5.3. | +| NR Band n100 | 919.4 – 925 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band n8. | +| | 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 | This requirement does not apply to BS operating in Band n104. | +| 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 | This requirement does not apply to BS operating in Band n104 | +| NR Band n105 | 612 – 652 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in band n71 or n105 | +| | 663 – 703 MHz | -37.4 dBm | 1 MHz | This requirement does not apply to BS operating in band n105, since it is already covered by the requirement in clause 6.7.5.3. | +| E-UTRA Band 106 or NR Band n106 | 935 - 940 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band n106 | +| | 896 – 901 MHz | -37.4 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.7.5.3.
This requirement does not apply to BS operating in Band n5 or n26. | +| NR Band n109 | 1432 – 1517 MHz | -40.4 dBm | 1 MHz | This requirement does not apply to BS operating in Band n50, n51, n74, n75 or n76. | +| | 703 – 733 MHz | -37.4 dBm | 1 MHz1 MHz | This requirement does not apply to BS operating in band n28, since it is already covered by the requirement in clause 6.7.5.3. | + +- 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 6.7.5.4.5-1 do 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.7.5.4.5-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 NR 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.7.1. + +The power of any spurious emission shall not exceed: + +**Table 6.7.5.4.5-2: BS spurious emissions test limits for BS for co-existence with PHS** + +| Frequency range | Test limit | Measurement bandwidth | Note | +|---------------------|------------|-----------------------|-------------------------------------------------------------------------------| +| 1884.5 – 1915.7 MHz | -32 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 BS operating in Band n50 and n75 within 1432-1452 MHz, and in Band n51 and Band n76. Emissions shall not exceed the test level specified in table 6.7.5.4.5-3. 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.7.5.4.5-3: Additional emission test limit for BS operating in Band n50 and n75 within 1432-1452 MHz, and in Band n51 and n76** + +| Filter centre frequency, $F_{\text{filter}}$ | Test limit (dBm) | Measurement bandwidth | +|----------------------------------------------|------------------|-----------------------| +| $F_{\text{filter}} = 1413.5$ MHz | -42 | 27 MHz | + +In certain regions, the following requirement may apply to BS 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 as EIRP, on centre frequencies $F_{\text{filter}}$ with filter bandwidth according to table 6.7.5.4.5-4, shall not exceed the EIRP limit. + +**Table 6.7.5.4.5-4: Operating band n50, n74 and n75 emission test limits above 1518 MHz** + +| Filter centre frequency, $F_{\text{filter}}$ | EIRP limit (dBm) | Measurement bandwidth | +|-------------------------------------------------------|------------------|-----------------------| +| $1518.5$ MHz $\leq F_{\text{filter}} \leq 1519.5$ MHz | -0.8 | 1 MHz | +| $1520.5$ MHz $\leq F_{\text{filter}} \leq 1558.5$ MHz | -30 | 1 MHz | + +In certain regions, the following requirement shall be applied to BS operating in Band 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.7.5.4.5-5: BS Spurious emissions limits for protection of 700 MHz public safety operations** + +| Operating Band | Frequency range | Maximum Level | Measurement Bandwidth | +|----------------|-----------------|---------------|-----------------------| +| n13 | 763 - 775 MHz | -37 dBm | 6.25 kHz | +| n13 | 793 - 805 MHz | -37 dBm | 6.25 kHz | +| n14 | 769 – 775 MHz | -37 dBm | 6.25 kHz | +| n14 | 799 – 805 MHz | -37 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.7.5.4.5-6: Additional NR BS Spurious emissions limits for Band n30** + +| Frequency range | Basic limit | Measurement bandwidth | +|-------------------|-------------|-----------------------| +| 2200 – 2345 MHz | -33.4 dBm | 1 MHz | +| 2362.5 – 2365 MHz | -13.4 dBm | | +| 2365 – 2367.5 MHz | -28.4 dBm | | +| 2367.5 – 2370 MHz | -30.4 dBm | | +| 2370 – 2395 MHz | -33.4 dBm | | + +NOTE: The regional requirement, included in ECC/DEC/(17)06 [15], is defined in terms of EIRP, which is dependent on both the BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The requirement defined above provides the characteristics of the base station needed to verify compliance with the regional requirement. The assessment of the EIRP level is described in TS 38.104 [2] annex E. + +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 TRP of any spurious emission shall not exceed: + +**Table 6.7.5.4.5-7: BS OTA Spurious emissions limits for protection of 800 MHz public safety operations** + +| Operating Band | Frequency range | Maximum Level | Measurement Bandwidth | Note | +|----------------|-----------------|---------------|-----------------------|--------------------------------------------------------| +| n26 | 851 - 859 MHz | -4 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.7.5.4.5-8: Additional BS Spurious emissions limits for Band n41 and n90** + +| Frequency range | Test limit | Measurement Bandwidth | +|-----------------------------------------------------------------------------|------------|-----------------------| +| 2505 MHz – 2535 MHz | -33 dBm | 1 MHz | +| NOTE: This requirement applies for carriers allocated within 2545-2645 MHz. | | | + +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.7.5.4.5-9 shall not exceed the maximum TRP limits indicated in the table. + +**Table 6.7.5.4.5-9: 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_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | +| | 1559 - 1610 MHz | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | | +| | 1610 - 1650 MHz | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | $P_{\text{EIRP}} - 17 \text{ dBi} + 9 \text{ dB}$ | | + +Note: The regional requirements in attachment to the FCC reference document, 0007135419, are defined in terms of EIRP (effective isotropic radiated power), which is dependent on both the BS emissions at the antenna connector and the deployment (including antenna gain and feeder loss). + +#### 6.7.5.4.5.2 Test requirement for BS type 2-O + +For BS operating in the frequency range 24.25 – 27.5 GHz, the power of any spurious emissions shall not exceed the limits in Table 6.7.5.4.5.2-1. + +**Table 6.7.5.4.5.2-1: BS spurious emissions test 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 BS brought into use on or before 1 September 2027. | | | | +| NOTE 2: This limit applies to BS brought into use after 1 September 2027. | | | | + +### 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 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 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.104 [2], the power levels are specified at the CLTA output. + +#### 6.7.5.5.2 Minimum requirements + +The minimum requirement for *BS type 1-O* is defined in TS 38.104 [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. + +*Base Station 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 NR BS 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 NR BS as depicted in annex E.1.3. +- 4) The test antenna shall be dual (or single) polarized with the same frequency range as the NR BS 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 analyzer) characteristics shall be: + - Detection mode: True RMS. + +The emission power should be averaged over an appropriate time duration to ensure the measurement is within the measurement uncertainty in Table 4.1.2.2-1. + +- 8) Set the *BS type 1-O* to transmit: + - Set the NR BS 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 NR BS declared to be capable of multi-carrier and/or CA operation, set the BS 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. + +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 *BS type 1-O* + +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 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.104 [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: BS type 1-O OTA spurious emissions limits for BS co-located with another BS** + +| Type of co-located BS | Frequency range for co-location requirement | Test limit | | | Measurement bandwidth | Note | +|-----------------------------------------------------|---------------------------------------------|------------|------------|------------|-----------------------|------------------------------------------------------------------| +| | | WA BS | MR BS | LA BS | | | +| 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 | | +| UTRA FDD Band VI, XIX or E-UTRA Band 6, 19 | 830 – 845 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band VII or E-UTRA Band 7 or NR Band n7 | 2500 – 2570 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band VIII or E-UTRA Band 8 or NR Band n8 | 880 – 915 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band IX or E-UTRA Band 9 | 1749.9 – 1784.9 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band X or E-UTRA Band 10 | 1710 – 1770 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band XI or E-UTRA Band 11 | 1427.9 – 1447.9 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band n50 , n75 or n109 | +| UTRA FDD Band XII or E-UTRA Band 12 | 699 – 716 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band XIII or E-UTRA Band 13 or NR Band n13 | 777 – 787 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band XIV or E-UTRA Band 14 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 | 815 – 830 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band XX or E-UTRA Band 20 or NR Band n20 | 832 – 862 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band XXI or E-UTRA Band 21 | 1447.9 – 1462.9 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band n50, n75 or n109 | +| UTRA FDD Band XXII or E-UTRA Band 22 | 3410 – 3490 MHz | -113.7 dBm | -108.7 dBm | -105.7 dBm | 100 kHz | This is not applicable to BS operating in Band n77 or n78 | + +| | | | | | | | +|-----------------------------------------------------|---------------------|------------|------------|------------|---------|-----------------------------------------------------------------| +| E-UTRA Band 24 or NR Band n24 | 1626.5 – 1660.5 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band XXV or E-UTRA Band 25 | 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 | 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 | | +| UTRA TDD Band b) or E-UTRA Band 36 | 1930 – 1990 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band n2 | +| 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 | This is not applicable to BS operating in Band n38. | +| UTRA TDD Band f) or E-UTRA Band 39 | 1880 – 1920 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA TDD Band e) or E-UTRA Band 40 | 2300 – 2400MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 41 or NR Band n41 | 2496 – 2690 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band n41 | +| E-UTRA Band 42 | 3400 – 3600 MHz | -113.7 dBm | -108.7 dBm | -105.7 dBm | 100 kHz | This is not applicable to BS operating in Band n77 or n78 | +| E-UTRA Band 43 | 3600 – 3800 MHz | -113.7 dBm | -108.7 dBm | -105.7 dBm | 100 kHz | This is not applicable to BS operating in Band n77 or n78 | +| E-UTRA Band 44 | 703 – 803 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band n28 | +| 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 | 3550 – 3700 MHz | -113.7 dBm | -108.7 dBm | -105.7 dBm | 100 kHz | This is not applicable to BS 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 | This is not applicable to BS operating in Band n74, n75 or n109 | + +| | | | | | | | +|-------------------------------|---------------------|------------|------------|------------|---------|----------------------------------------------------------------------| +| E-UTRA Band 51 or NR Band n51 | 1427 – 1432 MHz | N/A | N/A | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band n50, n75, n76 or n109 | +| E-UTRA Band 53 or NR Band n53 | 2483.5 – 2495 MHz | N/A | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band n41 or n90 | +| E-UTRA Band 54 or NR Band n54 | 1670 – 1675 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band n54 | +| 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 | | +| E-UTRA Band 74 or NR Band n74 | 1427 – 1470 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to BS operating in Band n50 | +| NR Band n77 | 3.3 – 4.2 GHz | -113.7 dBm | -108.7 dBm | -105.7 dBm | 100 kHz | This is not applicable to BS 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 BS 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 | | +| 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 n95 | 2010 – 2025 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| NR Band 96 | 5925 – 7125 | N/A | -107.6 dBm | -104.6 dBm | 100 kHz | | +| NR Band n97 | 2300 – 2400 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| NR Band n98 | 1880 – 1920 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| NR Band n99 | 1626.5 – 1660.5 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| NR band n100 | 874.4 – 880 MHz | -113.9 dBm | NA | NA | 100 kHz | | + +| | | | | | | | +|---------------------------------|-----------------|------------|------------|------------|----------------|-----------------------------------------------------| +| NR band n101 | 1900 - 1910 MHz | -113.9 dBm | NA | NA | 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 | This is not applicable to BS operating in Band n104 | +| 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 kHz100 kHz | | + +NOTE 1: As defined in the scope for spurious emissions in this clause, the co-location requirements in table 6.7.5.5.5.1-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 table 5.2-1 in TS 38.104 [2]). The current state-of-the-art technology does not allow a single generic solution for co-location with other system on adjacent frequencies for 30 dB BS-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [27]. + +NOTE 2: Table 6.7.5.5.5.1-1 assumes that two *operating bands*, where the corresponding BS transmit and receive frequency ranges in table 5.2-1 in TS 38.104 [2] would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-location requirements may apply that are not covered by the 3GPP specifications. + +NOTE 3: Co-located TDD base stations that are synchronized and using the same or adjacent *operating band* can transmit without special co-locations requirements. For unsynchronized base stations, special co-location requirements may apply that are not covered by the 3GPP specifications. + +## 6.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 *BS 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 *BS type 1-O* operation is defined in TS 38.104 [2], clause 9.8.2. + +The OTA transmitter intermodulation requirement is not applicable for *BS 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. + +*Base Station 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. + +### 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 NR BS and the emission frequencies. +- 4) Several test antennas are required to cover both the NR BS 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 NR BS 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 analyzer) characteristics shall be: + +- Detection mode: True RMS. + +The emission power should be averaged over an appropriate time duration to ensure the measurement is within the measurement uncertainty in Table 4.1.2.2-1. + +- 9) Set the BS *type I-O* to transmit: + - Set the NR BS 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 NR BS declared to be capable of multi-carrier and/or CA operation, set the BS 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. +- 10) Generate the interfering signal using test model as defined in clause 4.9.2, at a centre frequency offset according to the conditions in table 9.8.2-1 in TS 38.104 [2], but exclude interfering frequencies that are outside of the allocated downlink operating band or interfering frequencies that are not completely within the sub-block gap or within the *Inter RF Bandwidth gap*. + +- 11) Connect the interfering signal to the CLTA input interfaces, equally dividing the power among supported polarizations. Adjust the interfering signal level at the CLTA conducted input(s) as defined in table 6.8.5.1-1. +- 12) If the interfering 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 interfering 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 defined in table 6.8.5.1-1. +- 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 BS 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 *Base Station RF Bandwidth edges*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges* or *Radio Bandwidth edges*. + +For RIBs supporting operation in *non-contiguous spectrum*, the requirement is also applicable inside a *sub-block gap* for interfering signal offsets where the interfering signal falls completely within the *sub-block gap*. The interfering signal offset is defined relative to the *sub-block edges*. + +For RIBs supporting operation in multiple *operating bands*, 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 * 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.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 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 power level | $\min(46 \text{ dBm}, P_{\text{rated,t,TRP}})$ | +| Interfering signal centre frequency offset from the lower (upper) edge of the wanted signal or edge of sub-block inside a 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. | | +| NOTE 3: For BS type 1-O supporting dual polarization, the interfering signal power shall be equally divided between supported polarizations at the CLTA interfaces. | | + +## 6.8.5.2 Additional requirements (regional) + +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 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.2-1. + +**Table 6.8.5.2-1: Interfering and wanted signals for the OTA transmitter intermodulation requirement for 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 power level | $\min(46 \text{ dBm}, P_{\text{rated,t,TRP}})$ | +| Interfering signal centre frequency offset from the lower (upper) edge of the wanted signal | $\pm 2.5 \text{ MHz}$
$\pm 7.5 \text{ MHz}$
$\pm 12.5 \text{ MHz}$ | + +## 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. BS 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 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 radiated 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*. + +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*. + +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) 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)}$$ + +For FR2 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}$$ + +For *BS type 1-H* there is no requirement specified for band n46, n100, n101 and n102. + +For *BS type 1-O* there is no requirement specified for bands n46, n96, n100, n101 and n102. + +## 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 *BS type 1-H* and *BS type 1-O receiver*. + +The *BS type 1-H* and *BS 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 BS is capable of redirecting the *receiver target* related to the OSDD then the OSDD shall include: + +- *BS 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 BS is not capable of redirecting the *receiver target* related to the OSDD, then the OSDD includes only: + +- *BS 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 + +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 TS 38.104 [2] clause 7.2.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 *BS channel bandwidth*. + +### 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) Configure the beam peak direction for the transmitter according to the declared reference beam direction pair for the appropriate beam identifier. +- 6) For FDD operation, set the BS to transmit beam(s) of the same operational band as the OSDD being tested according to the appropriate test configuration in clauses 4.7 and 4.8. +- 7) Start the signal generator for the wanted signal to transmit: + - The test signal as specified in clause 7.2.5. +- 8) 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. +- 9) Measure the throughput according to annex A.1 for each supported polarization. +- 10) 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 BS type 1-H and BS type 1-O + +For each measured carrier, the throughput measured in step 9 of clause 7.2.4.2 shall be $\geq 95$ % of the maximum throughput of the reference measurement channel as specified in annex A.1 with parameters specified in table 7.2.5.2-1. + +**Table 7.2.5.2-1: EIS levels** + +| BS 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 | $6.0$ GHz $< f \leq 7.125$ GHz | +| 5, 10, 15 | 15 | G-FR1-A1-1 | Declared minimum EIS
+ 1.3 | Declared minimum EIS
+ 1.4 | Declared minimum EIS
+ 1.6 | Declared minimum EIS
+ 1.9 | +| 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 BS channel bandwidth. + +**Table 7.2.5-2: Void****Table 7.2.5-3: EIS levels for band n96 for BS Type 1-H** + +| BS channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel | OTA sensitivity level, EIS (dBm) | +|----------------------------|---------------------------|-------------------------------|----------------------------------| +| 20 | 15 | G-FR1-A1-14 (Note 2) | Declared minimum EIS
+ 1.9 | +| | 30 | G-FR1-A1-15 (Note 2) | | +| | 60 | G-FR1-A1-6 (Note 1) | | +| 40 | 15 | G-FR1-A1-16 (Note 2) | | +| | 30 | G-FR1-A1-17 (Note 2) | | +| | 60 | G-FR1-A1-6 (Note 1) | | +| 60 | 30 | G-FR1-A1-18 (Note 2) | | +| | 60 | G-FR1-A1-6 (Note 1) | | +| 80 | 30 | G-FR1-A1-19 (Note 2) | | +| | 60 | G-FR1-A1-6 (Note 1) | | + +NOTE 1: 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 BS channel bandwidth. + +NOTE 2: EIS 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. + +### 7.2.5.3 Test requirements for BS type 2-O + +There is no OTA sensitivity requirement for FR2, the OTA sensitivity is the same as the OTA reference sensitivity in clause 7.3. + +## 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 *BS type 1-O* the minimum requirement is in TS 38.104 [2], clause 10.3.2. + +For *BS type 2-O* the minimum requirement is in TS 38.104 [2], clause 10.3.3. + +### 7.3.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_{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 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) Configure the beam peak direction for the transmitter according to the declared reference beam direction pair for the appropriate beam identifier. +- 6) For FDD operation, set the BS to transmit beam(s) of the same operational band as the *OTA REFSENS RoAoA* being tested according to the appropriate test configuration in clauses 4.7 and 4.8. +- 7) Start the signal generator for the wanted signal to transmit: + - The test signal as specified in clause 7.3.5. + +- 8) 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. +- 9) Measure the throughput according to annex A.1 for each supported polarization. +- 10) Repeat steps 3 to 9 for all OTA REFSENS conformance test directions of the BS (D.55), and supported polarizations. + +For multi-band capable FR1 BS and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carriers activated in the other band. + +## 7.3.5 Test 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 Test requirements for BS type 1-O + +For each measured carrier, the throughput measured in step 9 of clause 7.3.4.2 shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel as specified in annex A.1 with parameters specified in tables 7.3.5.2-1 to 7.3.5.2-3. + +**Table 7.3.5.2-1: Wide Area BS EISREFSENS levels** + +| BS 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 | $6.0$ GHz $< f \leq 7.125$ GHz | +| 5, 10, 15 | 15 | G-FR1-A1-1 | -100.4 –
$\Delta_{\text{OTAREFSENS}}$ | -100.3 –
$\Delta_{\text{OTAREFSENS}}$ | -100.1 –
$\Delta_{\text{OTAREFSENS}}$ | NA | +| 10, 15 | 30 | G-FR1-A1-2 | -100.5 –
$\Delta_{\text{OTAREFSENS}}$ | -100.4 –
$\Delta_{\text{OTAREFSENS}}$ | -100.2 –
$\Delta_{\text{OTAREFSENS}}$ | NA | +| 10, 15 | 60 | G-FR1-A1-3 | -97.6 –
$\Delta_{\text{OTAREFSENS}}$ | -97.5 –
$\Delta_{\text{OTAREFSENS}}$ | -97.3 –
$\Delta_{\text{OTAREFSENS}}$ | NA | +| 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}}$ | -92.4 –
$\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}}$ | -92.7 –
$\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}}$ | -92.8 –
$\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 BS channel bandwidth. + +**Table 7.3.5.2-2: Medium Range BS EISREFSENS levels** + +| BS channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel (annex A.1) | EIS REFSENS (dBm) | | | | +|-------------------------------------------------|---------------------------|-------------------------------------------|------------------------------------|------------------------------------|------------------------------------|------------------------------------| +| | | | f ≤ 3.0 GHz | 3.0 GHz < f ≤ 4.2 GHz | 4.2 GHz < f ≤ 6.0 GHz | 6.0 GHz < f ≤ 7.125 GHz | +| 5, 10, 15 | 15 | G-FR1-A1-1 | -95.4 –
Δ OTAREFSENS | -95.3 –
Δ OTAREFSENS | -95.1 –
Δ OTAREFSENS | NA | +| 10, 15 | 30 | G-FR1-A1-2 | -95.5 –
Δ OTAREFSENS | -95.4 –
Δ OTAREFSENS | -95.2 –
Δ OTAREFSENS | NA | +| 10, 15 | 60 | G-FR1-A1-3 | -92.6 –
Δ OTAREFSENS | -92.5 –
Δ OTAREFSENS | -92.3 –
Δ OTAREFSENS | NA | +| 20, 25, 30, 35, 40, 45, 50 | 15 | G-FR1-A1-4 | -89 –
Δ OTAREFSENS | -88.9 –
Δ OTAREFSENS | -88.7 –
Δ OTAREFSENS | -87.4 –
Δ OTAREFSENS | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 | -89.3 –
Δ OTAREFSENS | -89.2 –
Δ OTAREFSENS | -89 – Δ OTAREFSENS | -87.7 –
Δ OTAREFSENS | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 | -89.4 –
Δ OTAREFSENS | -89.3 –
Δ OTAREFSENS | -89.1 –
Δ OTAREFSENS | -87.8 –
Δ 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 BS channel bandwidth. + +**Table 7.3.5.2-3: Local Area BS EISREFSENS levels** + +| BS channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel (annex A.1) | OTA reference sensitivity level, EIS REFSENS (dBm) | | | | +|-------------------------------------------------|---------------------------|-------------------------------------------|---------------------------------------------------------------|------------------------------------|------------------------------------|------------------------------------| +| | | | f ≤ 3.0 GHz | 3.0 GHz < f ≤ 4.2 GHz | 4.2 GHz < f ≤ 6.0 GHz | 6.0 GHz < f ≤ 7.125 GHz | +| 5, 10, 15 | 15 | G-FR1-A1-1 | -92.4 –
Δ OTAREFSENS | -92.3 –
Δ OTAREFSENS | -92.1 –
Δ OTAREFSENS | NA | +| 10, 15 | 30 | G-FR1-A1-2 | -92.5 –
Δ OTAREFSENS | -92.4 –
Δ OTAREFSENS | -92.2 –
Δ OTAREFSENS | NA | +| 10, 15 | 60 | G-FR1-A1-3 | -89.6 –
Δ OTAREFSENS | -89.5 –
Δ OTAREFSENS | -89.3 –
Δ OTAREFSENS | NA | +| 20, 25, 30, 35, 40, 45, 50 | 15 | G-FR1-A1-4 | -86 –
Δ OTAREFSENS | -85.9 –
Δ OTAREFSENS | -85.7 –
Δ OTAREFSENS | -84.4 –
Δ OTAREFSENS | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 | -86.3 –
Δ OTAREFSENS | -86.2 –
Δ OTAREFSENS | -86 – Δ OTAREFSENS | -84.7 –
Δ OTAREFSENS | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 | -86.4 –
Δ OTAREFSENS | -86.3 –
Δ OTAREFSENS | -86.1 –
Δ OTAREFSENS | -84.8 –
Δ 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 BS channel bandwidth. + +### 7.3.5.3 Test requirements for BS type 2-O + +The throughput shall be ≥ 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 BS channel bandwidth. EISREFSENS\_50M itself is not a requirement and although it is based on a reference measurement channel with 50 MHz BS channel bandwidth it does not imply that BS has to support 50 MHz BS channel bandwidth. + +For Wide Area BS, $EIS_{REFSENS\_50M}$ is an integer value in the range -96 to -119 dBm. The specific value is declared by the vendor. + +For Medium Range BS, $EIS_{REFSENS\_50M}$ is an integer value in the range -91 to -114 dBm. The specific value is declared by the vendor. + +For Local Area BS, $EIS_{REFSENS\_50M}$ is an integer value in the range -86 to -109 dBm. The specific value is declared by the vendor. + +**Table 7.3.5.3-1: FR2-1 OTA reference sensitivity requirement applicable in the frequency range 24.25 – 43.5 GHz** + +| BS 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_{FR2\_REFSENS}$ | +| 50 | 120 | G-FR2-A1-2 | $EIS_{REFSENS\_50M} + 2.4 + \Delta_{FR2\_REFSENS}$ | +| 100, 200, 400 | 120 | G-FR2-A1-3 | $EIS_{REFSENS\_50M} + 3 + 2.4 + \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 BS channel bandwidth. + +NOTE 2: The declared $EIS_{REFSENS\_50M}$ shall be within the range specified in table 10.3.3-2. + +**Table 7.3.5.3-2: FR2-1 OTA reference sensitivity requirement applicable in the frequency range 43.5 – 48.2 GHz** + +| BS 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} + 3.5 + \Delta_{FR2\_REFSENS}$ | +| 50 | 120 | G-FR2-A1-2 | $EIS_{REFSENS\_50M} + 3.5 + \Delta_{FR2\_REFSENS}$ | +| 100, 200, 400 | 120 | G-FR2-A1-3 | $EIS_{REFSENS\_50M} + 3 + 3.5 + \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 BS channel bandwidth. + +NOTE 2: The declared $EIS_{REFSENS\_50M}$ shall be within the range specified in table 10.3.3-2. + +**Table 7.3.5.3-3 FR2-2 OTA reference sensitivity requirement applicable in the frequency range 52.6 – 71 GHz** + +| BS channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel (annex A.1) | OTA reference sensitivity level, $EIS_{REFSENS}$ (dBm) | +|----------------------------|---------------------------|-------------------------------------------|--------------------------------------------------------| +| 100,400 | 120 | G-FR2-A1-3 | $EIS_{REFSENS\_50M} + 3 + 3.0 + \Delta_{FR2\_REFSENS}$ | +| 400, 800, 1600 | 480 | G-FR2-A1-6 | $EIS_{REFSENS\_50M} + 9 + 3.0 + \Delta_{FR2\_REFSENS}$ | +| 400, 800, 1600, 2000 | 960 | G-FR2-A1-7 | $EIS_{REFSENS\_50M} + 9 + 3.0 + \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 BS channel bandwidth. + +NOTE 2: The declared $EIS_{REFSENS\_50M}$ shall be within the range specified in table 10.3.3-2. + +## 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 BS 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 BS type I-O, the minimum requirement is in TS 38.104 [2], clause 10.4.2. + +### 7.4.3 Test purpose + +The test purpose is to verify that at the BS 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 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.2. +- 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) Configure the beam peak direction for the transmitter according to the declared reference beam direction pair for the appropriate beam identifier. +- 6) For FDD operation, set the BS to transmit beam(s) of the same operational band as the *OTA REFSENS RoAoA* being tested according to the appropriate test configuration in clauses 4.7 and 4.8. +- 7) Set the test signal mean power so that the calibrated radiated power at the BS 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. +- 8) 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 BS 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-3a. + +**Table 7.4.5.2-1: Wide Area BS dynamic range for $f \leq 6.0$ GHz** + +| BS 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 | +|----------------------------|--------------------------|-------------------------------------------|--------------------------------|-------------------------------|-------------------------------|-----------------------------------------------------|----------------------------| +| | | | $f \leq 3.0$ GHz | $3.0$ GHz $< f \leq 4.2$ GHz | $4.2$ GHz $< f \leq 6.0$ GHz | | | +| 5 | 15 | G-FR1-A2-1 | -70.4 – $\Delta_{OTAREFSENS}$ | -70.4 – $\Delta_{OTAREFSENS}$ | -70.4 – $\Delta_{OTAREFSENS}$ | -82.5 – $\Delta_{OTAREFSENS}$ | AWGN | +| | 30 | G-FR1-A2-2 | -71.1 – $\Delta_{OTAREFSENS}$ | -71.1 – $\Delta_{OTAREFSENS}$ | -71.1 – $\Delta_{OTAREFSENS}$ | | | +| 10 | 15 | G-FR1-A2-1 | -70.4 – $\Delta_{OTAREFSENS}$ | -70.4 – $\Delta_{OTAREFSENS}$ | -70.4 – $\Delta_{OTAREFSENS}$ | -79.3 – $\Delta_{OTAREFSENS}$ | AWGN | +| | 30 | G-FR1-A2-2 | -71.1 – $\Delta_{OTAREFSENS}$ | -71.1 – $\Delta_{OTAREFSENS}$ | -71.1 – $\Delta_{OTAREFSENS}$ | | | +| | 60 | G-FR1-A2-3 | -68.1 – $\Delta_{OTAREFSENS}$ | -68.1 – $\Delta_{OTAREFSENS}$ | -68.1 – $\Delta_{OTAREFSENS}$ | | | +| 15 | 15 | G-FR1-A2-1 | -70.4 – $\Delta_{OTAREFSENS}$ | -70.4 – $\Delta_{OTAREFSENS}$ | -70.4 – $\Delta_{OTAREFSENS}$ | -77.5 – $\Delta_{OTAREFSENS}$ | AWGN | +| | 30 | G-FR1-A2-2 | -71.1 – $\Delta_{OTAREFSENS}$ | -71.1 – $\Delta_{OTAREFSENS}$ | -71.1 – $\Delta_{OTAREFSENS}$ | | | +| | 60 | G-FR1-A2-3 | -68.1 – $\Delta_{OTAREFSENS}$ | -68.1 – $\Delta_{OTAREFSENS}$ | -68.1 – $\Delta_{OTAREFSENS}$ | | | +| 20 | 15 | G-FR1-A2-4 | -64.2 – $\Delta_{OTAREFSENS}$ | -64.2 – $\Delta_{OTAREFSENS}$ | -64.2 – $\Delta_{OTAREFSENS}$ | -76.2 – $\Delta_{OTAREFSENS}$ | AWGN | +| | 30 | G-FR1-A2-5 | -64.2 – $\Delta_{OTAREFSENS}$ | -64.2 – $\Delta_{OTAREFSENS}$ | -64.2 – $\Delta_{OTAREFSENS}$ | | | +| | 60 | G-FR1-A2-6 | -64.5 – $\Delta_{OTAREFSENS}$ | -64.5 – $\Delta_{OTAREFSENS}$ | -64.5 – $\Delta_{OTAREFSENS}$ | | | +| 25 | 15 | G-FR1-A2-4 | -64.2 – $\Delta_{OTAREFSENS}$ | -64.2 – $\Delta_{OTAREFSENS}$ | -64.2 – $\Delta_{OTAREFSENS}$ | -75.2 – $\Delta_{OTAREFSENS}$ | AWGN | +| | 30 | G-FR1-A2-5 | -64.2 – $\Delta_{OTAREFSENS}$ | -64.2 – $\Delta_{OTAREFSENS}$ | -64.2 – $\Delta_{OTAREFSENS}$ | | | +| | 60 | G-FR1-A2-6 | -64.5 – $\Delta_{OTAREFSENS}$ | -64.5 – $\Delta_{OTAREFSENS}$ | -64.5 – $\Delta_{OTAREFSENS}$ | | | +| 30 | 15 | G-FR1-A2-4 | -64.2 – $\Delta_{OTAREFSENS}$ | -64.2 – $\Delta_{OTAREFSENS}$ | -64.2 – $\Delta_{OTAREFSENS}$ | -74.4 – $\Delta_{OTAREFSENS}$ | AWGN | +| | 30 | G-FR1-A2-5 | -64.2 – $\Delta_{OTAREFSENS}$ | -64.2 – $\Delta_{OTAREFSENS}$ | -64.2 – $\Delta_{OTAREFSENS}$ | | | +| | 60 | G-FR1-A2-6 | -64.5 – $\Delta_{OTAREFSENS}$ | -64.5 – $\Delta_{OTAREFSENS}$ | -64.5 – $\Delta_{OTAREFSENS}$ | | | +| 35 | 15 | G-FR1-A2-4 | -64.2 – $\Delta_{OTAREFSENS}$ | -64.2 – $\Delta_{OTAREFSENS}$ | -64.2 – $\Delta_{OTAREFSENS}$ | -73.7 – $\Delta_{OTAREFSENS}$ | AWGN | +| | 30 | G-FR1-A2-5 | -64.2 – $\Delta_{OTAREFSENS}$ | -64.2 – $\Delta_{OTAREFSENS}$ | -64.2 – $\Delta_{OTAREFSENS}$ | | | +| | 60 | G-FR1-A2-6 | -64.5 – $\Delta_{OTAREFSENS}$ | -64.5 – $\Delta_{OTAREFSENS}$ | -64.5 – $\Delta_{OTAREFSENS}$ | | | +| 40 | 15 | G-FR1-A2-4 | -64.2 – $\Delta_{OTAREFSENS}$ | -64.2 – $\Delta_{OTAREFSENS}$ | -64.2 – $\Delta_{OTAREFSENS}$ | -73.1 – $\Delta_{OTAREFSENS}$ | AWGN | +| | 30 | G-FR1-A2-5 | -64.2 – $\Delta_{OTAREFSENS}$ | -64.2 – $\Delta_{OTAREFSENS}$ | -64.2 – $\Delta_{OTAREFSENS}$ | | | +| | 60 | G-FR1-A2-6 | -64.5 – $\Delta_{OTAREFSENS}$ | -64.5 – $\Delta_{OTAREFSENS}$ | -64.5 – $\Delta_{OTAREFSENS}$ | | | +| 45 | 15 | G-FR1-A2-4 | -64.2 – $\Delta_{OTAREFSENS}$ | -64.2 – $\Delta_{OTAREFSENS}$ | -64.2 – $\Delta_{OTAREFSENS}$ | -72.6 – $\Delta_{OTAREFSENS}$ | AWGN | +| | 30 | G-FR1-A2-5 | -64.2 – $\Delta_{OTAREFSENS}$ | -64.2 – $\Delta_{OTAREFSENS}$ | -64.2 – $\Delta_{OTAREFSENS}$ | | | +| | 60 | G-FR1-A2-6 | -64.5 – $\Delta_{OTAREFSENS}$ | -64.5 – $\Delta_{OTAREFSENS}$ | -64.5 – $\Delta_{OTAREFSENS}$ | | | +| 50 | 15 | G-FR1-A2-4 | -64.2 – $\Delta_{OTAREFSENS}$ | -64.2 – $\Delta_{OTAREFSENS}$ | -64.2 – $\Delta_{OTAREFSENS}$ | -72.1 – $\Delta_{OTAREFSENS}$ | AWGN | +| | 30 | G-FR1-A2-5 | -64.2 – $\Delta_{OTAREFSENS}$ | -64.2 – $\Delta_{OTAREFSENS}$ | -64.2 – $\Delta_{OTAREFSENS}$ | | | +| | 60 | G-FR1-A2-6 | -64.5 – $\Delta_{OTAREFSENS}$ | -64.5 – $\Delta_{OTAREFSENS}$ | -64.5 – $\Delta_{OTAREFSENS}$ | | | +| 60 | 30 | G-FR1-A2-5 | -64.2 – $\Delta_{OTAREFSENS}$ | -64.2 – $\Delta_{OTAREFSENS}$ | -64.2 – $\Delta_{OTAREFSENS}$ | -71.3 – $\Delta_{OTAREFSENS}$ | AWGN | +| | 60 | G-FR1-A2-6 | -64.5 – $\Delta_{OTAREFSENS}$ | -64.5 – $\Delta_{OTAREFSENS}$ | -64.5 – $\Delta_{OTAREFSENS}$ | | | + +| | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|------------|-----------------------------------------|-----------------------------------------|-----------------------------------------|-----------------------------------------|------| +| 70 | 30 | G-FR1-A2-5 | -64.2 –
$\Delta_{\text{OTAREFSENS}}$ | -64.2 –
$\Delta_{\text{OTAREFSENS}}$ | -64.2 –
$\Delta_{\text{OTAREFSENS}}$ | -70.7 –
$\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -64.5 –
$\Delta_{\text{OTAREFSENS}}$ | -64.5 –
$\Delta_{\text{OTAREFSENS}}$ | -64.5 –
$\Delta_{\text{OTAREFSENS}}$ | | | +| 80 | 30 | G-FR1-A2-5 | -64.2 –
$\Delta_{\text{OTAREFSENS}}$ | -64.2 –
$\Delta_{\text{OTAREFSENS}}$ | -64.2 –
$\Delta_{\text{OTAREFSENS}}$ | -70.1 –
$\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -64.5 –
$\Delta_{\text{OTAREFSENS}}$ | -64.5 –
$\Delta_{\text{OTAREFSENS}}$ | -64.5 –
$\Delta_{\text{OTAREFSENS}}$ | | | +| 90 | 30 | G-FR1-A2-5 | -64.2 –
$\Delta_{\text{OTAREFSENS}}$ | -64.2 –
$\Delta_{\text{OTAREFSENS}}$ | -64.2 –
$\Delta_{\text{OTAREFSENS}}$ | -69.5 –
$\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -64.5 –
$\Delta_{\text{OTAREFSENS}}$ | -64.5 –
$\Delta_{\text{OTAREFSENS}}$ | -64.5 –
$\Delta_{\text{OTAREFSENS}}$ | | | +| 100 | 30 | G-FR1-A2-5 | -64.2 –
$\Delta_{\text{OTAREFSENS}}$ | -64.2 –
$\Delta_{\text{OTAREFSENS}}$ | -64.2 –
$\Delta_{\text{OTAREFSENS}}$ | -69.1 –
$\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -64.5 –
$\Delta_{\text{OTAREFSENS}}$ | -64.5 –
$\Delta_{\text{OTAREFSENS}}$ | -64.5 –
$\Delta_{\text{OTAREFSENS}}$ | | | +| NOTE: The wanted signal mean power is the power level of a single instance of the corresponding reference measurement channel. This requirement shall be met for each consecutive application of a single instance of the reference measurement channel mapped to disjoint frequency ranges with a width corresponding to the number of resource blocks of the reference measurement channel each, except for one instance that might overlap one other instance to cover the full BS channel bandwidth . | | | | | | | | + +**Table 7.4.5.2-1a: Wide Area BS dynamic range for $6.0 < f \leq 7.125$ GHz** + +| BS 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 | +|----------------------------|--------------------------|-------------------------------------------|--------------------------------------|------------------------------------------------------------|----------------------------| +| 20 | 15 | G-FR1-A2-4 | -63.2 – $\Delta_{\text{OTAREFSENS}}$ | -75.2 – $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -63.2 – $\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -63.5 – $\Delta_{\text{OTAREFSENS}}$ | | | +| 30 | 15 | G-FR1-A2-4 | -63.2 – $\Delta_{\text{OTAREFSENS}}$ | -73.4 – $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -63.2 – $\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -63.5 – $\Delta_{\text{OTAREFSENS}}$ | | | +| 40 | 15 | G-FR1-A2-4 | -63.2 – $\Delta_{\text{OTAREFSENS}}$ | -72.1 – $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -63.2 – $\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -63.5 – $\Delta_{\text{OTAREFSENS}}$ | | | +| 50 | 15 | G-FR1-A2-4 | -63.2 – $\Delta_{\text{OTAREFSENS}}$ | -71.1 – $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -63.2 – $\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -63.5 – $\Delta_{\text{OTAREFSENS}}$ | | | +| 60 | 30 | G-FR1-A2-5 | -63.2 – $\Delta_{\text{OTAREFSENS}}$ | -70.3 – $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -63.5 – $\Delta_{\text{OTAREFSENS}}$ | | | +| 70 | 30 | G-FR1-A2-5 | -63.2 – $\Delta_{\text{OTAREFSENS}}$ | -69.7 – $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -63.5 – $\Delta_{\text{OTAREFSENS}}$ | | | +| 80 | 30 | G-FR1-A2-5 | -63.2 – $\Delta_{\text{OTAREFSENS}}$ | -69.1 – $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -63.5 – $\Delta_{\text{OTAREFSENS}}$ | | | +| 90 | 30 | G-FR1-A2-5 | -63.2 – $\Delta_{\text{OTAREFSENS}}$ | -68.5 – $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -63.5 – $\Delta_{\text{OTAREFSENS}}$ | | | +| 100 | 30 | G-FR1-A2-5 | -63.2 – $\Delta_{\text{OTAREFSENS}}$ | -68.1 – $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -63.5 – $\Delta_{\text{OTAREFSENS}}$ | | | + +NOTE: The wanted signal mean power is the power level of a single instance of the corresponding reference measurement channel. This requirement shall be met for each consecutive application of a single instance of the reference measurement channel mapped to disjoint frequency ranges with a width corresponding to the number of resource blocks of the reference measurement channel each, except for one instance that might overlap one other instance to cover the full BS channel bandwidth. + +**Table 7.4.5.2-2: Medium Range BS dynamic range for $f \leq 6.0$ GHz** + +| BS 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 | +|----------------------------|--------------------------|-------------------------------------------|---------------------------------|---------------------------------|---------------------------------|------------------------------------------------------------|----------------------------| +| | | | f ≤ 3.0 GHz | 3.0 GHz < f ≤ 4.2 GHz | 4.2 GHz < f ≤ 6.0 GHz | | | +| 5 | 15 | G-FR1-A2-1 | -65.4 – Δ OTAREFSENS | -65.4 – Δ OTAREFSENS | -65.4 – Δ OTAREFSENS | -77.5 – Δ OTAREFSENS | AWGN | +| | 30 | G-FR1-A2-2 | -66.1 – Δ OTAREFSENS | -66.1 – Δ OTAREFSENS | -66.1 – Δ OTAREFSENS | | | +| 10 | 15 | G-FR1-A2-1 | -65.4 – Δ OTAREFSENS | -65.4 – Δ OTAREFSENS | -65.4 – Δ OTAREFSENS | -74.3 – Δ OTAREFSENS | AWGN | +| | 30 | G-FR1-A2-2 | -66.1 – Δ OTAREFSENS | -66.1 – Δ OTAREFSENS | -66.1 – Δ OTAREFSENS | | | +| | 60 | G-FR1-A2-3 | -63.1 – Δ OTAREFSENS | -63.1 – Δ OTAREFSENS | -63.1 – Δ OTAREFSENS | | | +| 15 | 15 | G-FR1-A2-1 | -65.4 – Δ OTAREFSENS | -65.4 – Δ OTAREFSENS | -65.4 – Δ OTAREFSENS | -72.5 – Δ OTAREFSENS | AWGN | +| | 30 | G-FR1-A2-2 | -66.1 – Δ OTAREFSENS | -66.1 – Δ OTAREFSENS | -66.1 – Δ OTAREFSENS | | | +| | 60 | G-FR1-A2-3 | -63.1 – Δ OTAREFSENS | -63.1 – Δ OTAREFSENS | -63.1 – Δ OTAREFSENS | | | +| 20 | 15 | G-FR1-A2-4 | -59.2 – Δ OTAREFSENS | -59.2 – Δ OTAREFSENS | -59.2 – Δ OTAREFSENS | -71.2 – Δ OTAREFSENS | AWGN | +| | 30 | G-FR1-A2-5 | -59.2 – Δ OTAREFSENS | -59.2 – Δ OTAREFSENS | -59.2 – Δ OTAREFSENS | | | +| | 60 | G-FR1-A2-6 | -59.5 – Δ OTAREFSENS | -59.5 – Δ OTAREFSENS | -59.5 – Δ OTAREFSENS | | | +| 25 | 15 | G-FR1-A2-4 | -59.2 – Δ OTAREFSENS | -59.2 – Δ OTAREFSENS | -59.2 – Δ OTAREFSENS | -70.2 – Δ OTAREFSENS | AWGN | +| | 30 | G-FR1-A2-5 | -59.2 – Δ OTAREFSENS | -59.2 – Δ OTAREFSENS | -59.2 – Δ OTAREFSENS | | | +| | 60 | G-FR1-A2-6 | -59.5 – Δ OTAREFSENS | -59.5 – Δ OTAREFSENS | -59.5 – Δ OTAREFSENS | | | +| 30 | 15 | G-FR1-A2-4 | -59.2 – Δ OTAREFSENS | -59.2 – Δ OTAREFSENS | -59.2 – Δ OTAREFSENS | -69.4 – Δ OTAREFSENS | AWGN | +| | 30 | G-FR1-A2-5 | -59.2 – Δ OTAREFSENS | -59.2 – Δ OTAREFSENS | -59.2 – Δ OTAREFSENS | | | +| | 60 | G-FR1-A2-6 | -59.5 – Δ OTAREFSENS | -59.5 – Δ OTAREFSENS | -59.5 – Δ OTAREFSENS | | | +| 35 | 15 | G-FR1-A2-4 | -59.2 – Δ OTAREFSENS | -59.2 – Δ OTAREFSENS | -59.2 – Δ OTAREFSENS | -68.7 – Δ OTAREFSENS | AWGN | +| | 30 | G-FR1-A2-5 | -59.2 – Δ OTAREFSENS | -59.2 – Δ OTAREFSENS | -59.2 – Δ OTAREFSENS | | | +| | 60 | G-FR1-A2-6 | -59.5 – Δ OTAREFSENS | -59.5 – Δ OTAREFSENS | -59.5 – Δ OTAREFSENS | | | +| 40 | 15 | G-FR1-A2-4 | -59.2 – Δ OTAREFSENS | -59.2 – Δ OTAREFSENS | -59.2 – Δ OTAREFSENS | -68.1 – Δ OTAREFSENS | AWGN | +| | 30 | G-FR1-A2-5 | -59.2 – Δ OTAREFSENS | -59.2 – Δ OTAREFSENS | -59.2 – Δ OTAREFSENS | | | +| | 60 | G-FR1-A2-6 | -59.5 – Δ OTAREFSENS | -59.5 – Δ OTAREFSENS | -59.5 – Δ OTAREFSENS | | | +| 45 | 15 | G-FR1-A2-4 | -59.2 – Δ OTAREFSENS | -59.2 – Δ OTAREFSENS | -59.2 – Δ OTAREFSENS | -67.6 – Δ OTAREFSENS | AWGN | +| | 30 | G-FR1-A2-5 | -59.2 – Δ OTAREFSENS | -59.2 – Δ OTAREFSENS | -59.2 – Δ OTAREFSENS | | | +| | 60 | G-FR1-A2-6 | -59.5 – Δ OTAREFSENS | -59.5 – Δ OTAREFSENS | -59.5 – Δ OTAREFSENS | | | +| 50 | 15 | G-FR1-A2-4 | -59.2 – Δ OTAREFSENS | -59.2 – Δ OTAREFSENS | -59.2 – Δ OTAREFSENS | -67.1 – Δ OTAREFSENS | AWGN | +| | 30 | G-FR1-A2-5 | -59.2 – Δ OTAREFSENS | -59.2 – Δ OTAREFSENS | -59.2 – Δ OTAREFSENS | | | +| | 60 | G-FR1-A2-6 | -59.5 – Δ OTAREFSENS | -59.5 – Δ OTAREFSENS | -59.5 – Δ OTAREFSENS | | | +| 60 | 30 | G-FR1-A2-5 | -59.2 – Δ OTAREFSENS | -59.2 – Δ OTAREFSENS | -59.2 – Δ OTAREFSENS | -66.3 – Δ OTAREFSENS | AWGN | +| | 60 | G-FR1-A2-6 | -59.5 – Δ OTAREFSENS | -59.5 – Δ OTAREFSENS | -59.5 – Δ OTAREFSENS | | | + +| | | | | | | | | +|-----|----|------------|-----------------------------------------|-----------------------------------------|-----------------------------------------|-----------------------------------------|------| +| 70 | 30 | G-FR1-A2-5 | -59.2 –
$\Delta_{\text{OTAREFSENS}}$ | -59.2 –
$\Delta_{\text{OTAREFSENS}}$ | -59.2 –
$\Delta_{\text{OTAREFSENS}}$ | -65.7 –
$\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -59.5 –
$\Delta_{\text{OTAREFSENS}}$ | -59.5 –
$\Delta_{\text{OTAREFSENS}}$ | -59.5 –
$\Delta_{\text{OTAREFSENS}}$ | | | +| 80 | 30 | G-FR1-A2-5 | -59.2 –
$\Delta_{\text{OTAREFSENS}}$ | -59.2 –
$\Delta_{\text{OTAREFSENS}}$ | -59.2 –
$\Delta_{\text{OTAREFSENS}}$ | -65.1 –
$\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -59.5 –
$\Delta_{\text{OTAREFSENS}}$ | -59.5 –
$\Delta_{\text{OTAREFSENS}}$ | -59.5 –
$\Delta_{\text{OTAREFSENS}}$ | | | +| 90 | 30 | G-FR1-A2-5 | -59.2 –
$\Delta_{\text{OTAREFSENS}}$ | -59.2 –
$\Delta_{\text{OTAREFSENS}}$ | -59.2 –
$\Delta_{\text{OTAREFSENS}}$ | -64.5 –
$\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -59.5 –
$\Delta_{\text{OTAREFSENS}}$ | -59.5 –
$\Delta_{\text{OTAREFSENS}}$ | -59.5 –
$\Delta_{\text{OTAREFSENS}}$ | | | +| 100 | 30 | G-FR1-A2-5 | -59.2 –
$\Delta_{\text{OTAREFSENS}}$ | -59.2 –
$\Delta_{\text{OTAREFSENS}}$ | -59.2 –
$\Delta_{\text{OTAREFSENS}}$ | -64.1 –
$\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -59.5 –
$\Delta_{\text{OTAREFSENS}}$ | -59.5 –
$\Delta_{\text{OTAREFSENS}}$ | -59.5 –
$\Delta_{\text{OTAREFSENS}}$ | | | + +NOTE: The wanted signal mean power is the power level of a single instance of the corresponding reference measurement channel. This requirement shall be met for each consecutive application of a single instance of the reference measurement channel mapped to disjoint frequency ranges with a width corresponding to the number of resource blocks of the reference measurement channel each, except for one instance that might overlap one other instance to cover the full BS channel bandwidth. + +**Table 7.4.5.2-2a: Medium Range BS dynamic range for $6.0 < f \leq 7.125$ GHz** + +| BS 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 | +|----------------------------|--------------------------|-------------------------------------------|--------------------------------------|------------------------------------------------------------|----------------------------| +| 20 | 15 | G-FR1-A2-4 | -58.2 – $\Delta_{\text{OTAREFSENS}}$ | -70.2 – $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -58.2 – $\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -58.5 – $\Delta_{\text{OTAREFSENS}}$ | | | +| 30 | 15 | G-FR1-A2-4 | -58.2 – $\Delta_{\text{OTAREFSENS}}$ | -68.4 – $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -58.2 – $\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -58.5 – $\Delta_{\text{OTAREFSENS}}$ | | | +| 40 | 15 | G-FR1-A2-4 | -58.2 – $\Delta_{\text{OTAREFSENS}}$ | -67.1 – $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -58.2 – $\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -58.5 – $\Delta_{\text{OTAREFSENS}}$ | | | +| 50 | 15 | G-FR1-A2-4 | -58.2 – $\Delta_{\text{OTAREFSENS}}$ | -66.1 – $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -58.2 – $\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -58.5 – $\Delta_{\text{OTAREFSENS}}$ | | | +| 60 | 30 | G-FR1-A2-5 | -58.2 – $\Delta_{\text{OTAREFSENS}}$ | -65.3 – $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -58.5 – $\Delta_{\text{OTAREFSENS}}$ | | | +| 70 | 30 | G-FR1-A2-5 | -58.2 – $\Delta_{\text{OTAREFSENS}}$ | -64.7 – $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -58.5 – $\Delta_{\text{OTAREFSENS}}$ | | | +| 80 | 30 | G-FR1-A2-5 | -58.2 – $\Delta_{\text{OTAREFSENS}}$ | -64.1 – $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -58.5 – $\Delta_{\text{OTAREFSENS}}$ | | | +| 90 | 30 | G-FR1-A2-5 | -58.2 – $\Delta_{\text{OTAREFSENS}}$ | -63.5 – $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -58.5 – $\Delta_{\text{OTAREFSENS}}$ | | | +| 100 | 30 | G-FR1-A2-5 | -58.2 – $\Delta_{\text{OTAREFSENS}}$ | -63.1 – $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -58.5 – $\Delta_{\text{OTAREFSENS}}$ | | | + +NOTE: The wanted signal mean power is the power level of a single instance of the corresponding reference measurement channel. This requirement shall be met for each consecutive application of a single instance of the reference measurement channel mapped to disjoint frequency ranges with a width corresponding to the number of resource blocks of the reference measurement channel each, except for one instance that might overlap one other instance to cover the full BS channel bandwidth. + +**Table 7.4.5.2-3: Local Area BS dynamic range for $f \leq 6.0$ GHz** + +| BS 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 | +|----------------------------|--------------------------|-------------------------------------------|---------------------------------|---------------------------------|---------------------------------|------------------------------------------------------------|----------------------------| +| | | | f ≤ 3.0 GHz | 3.0 GHz < f ≤ 4.2 GHz | 4.2 GHz < f ≤ 6.0 GHz | | | +| 5 | 15 | G-FR1-A2-1 | -62.4 – Δ OTAREFSENS | -62.4 – Δ OTAREFSENS | -62.4 – Δ OTAREFSENS | -74.5 – Δ OTAREFSENS | AWGN | +| | 30 | G-FR1-A2-2 | -64.1 – Δ OTAREFSENS | -64.1 – Δ OTAREFSENS | -64.1 – Δ OTAREFSENS | | | +| 10 | 15 | G-FR1-A2-1 | -62.4 – Δ OTAREFSENS | -62.4 – Δ OTAREFSENS | -62.4 – Δ OTAREFSENS | -71.3 – Δ OTAREFSENS | AWGN | +| | 30 | G-FR1-A2-2 | -64.1 – Δ OTAREFSENS | -64.1 – Δ OTAREFSENS | -64.1 – Δ OTAREFSENS | | | +| | 60 | G-FR1-A2-3 | -60.1 – Δ OTAREFSENS | -60.1 – Δ OTAREFSENS | -60.1 – Δ OTAREFSENS | | | +| 15 | 15 | G-FR1-A2-1 | -62.4 – Δ OTAREFSENS | -62.4 – Δ OTAREFSENS | -62.4 – Δ OTAREFSENS | -69.5 – Δ OTAREFSENS | AWGN | +| | 30 | G-FR1-A2-2 | -64.1 – Δ OTAREFSENS | -64.1 – Δ OTAREFSENS | -64.1 – Δ OTAREFSENS | | | +| | 60 | G-FR1-A2-3 | -60.1 – Δ OTAREFSENS | -60.1 – Δ OTAREFSENS | -60.1 – Δ OTAREFSENS | | | +| 20 | 15 | G-FR1-A2-4 | -56.2 – Δ OTAREFSENS | -56.2 – Δ OTAREFSENS | -56.2 – Δ OTAREFSENS | -68.2 – Δ OTAREFSENS | AWGN | +| | 30 | G-FR1-A2-5 | -56.2 – Δ OTAREFSENS | -56.2 – Δ OTAREFSENS | -56.2 – Δ OTAREFSENS | | | +| | 60 | G-FR1-A2-6 | -56.5 – Δ OTAREFSENS | -56.5 – Δ OTAREFSENS | -56.5 – Δ OTAREFSENS | | | +| 25 | 15 | G-FR1-A2-4 | -56.2 – Δ OTAREFSENS | -56.2 – Δ OTAREFSENS | -56.2 – Δ OTAREFSENS | -67.2 – Δ OTAREFSENS | AWGN | +| | 30 | G-FR1-A2-5 | -56.2 – Δ OTAREFSENS | -56.2 – Δ OTAREFSENS | -56.2 – Δ OTAREFSENS | | | +| | 60 | G-FR1-A2-6 | -56.5 – Δ OTAREFSENS | -56.5 – Δ OTAREFSENS | -56.5 – Δ OTAREFSENS | | | +| 30 | 15 | G-FR1-A2-4 | -56.2 – Δ OTAREFSENS | -56.2 – Δ OTAREFSENS | -56.2 – Δ OTAREFSENS | -66.4 – Δ OTAREFSENS | AWGN | +| | 30 | G-FR1-A2-5 | -56.2 – Δ OTAREFSENS | -56.2 – Δ OTAREFSENS | -56.2 – Δ OTAREFSENS | | | +| | 60 | G-FR1-A2-6 | -56.5 – Δ OTAREFSENS | -56.5 – Δ OTAREFSENS | -56.5 – Δ OTAREFSENS | | | +| 35 | 15 | G-FR1-A2-4 | -56.2 – Δ OTAREFSENS | -56.2 – Δ OTAREFSENS | -56.2 – Δ OTAREFSENS | -65.7 – Δ OTAREFSENS | AWGN | +| | 30 | G-FR1-A2-5 | -56.2 – Δ OTAREFSENS | -56.2 – Δ OTAREFSENS | -56.2 – Δ OTAREFSENS | | | +| | 60 | G-FR1-A2-6 | -56.5 – Δ OTAREFSENS | -56.5 – Δ OTAREFSENS | -56.5 – Δ OTAREFSENS | | | +| 40 | 15 | G-FR1-A2-4 | -56.2 – Δ OTAREFSENS | -56.2 – Δ OTAREFSENS | -56.2 – Δ OTAREFSENS | -65.1 – Δ OTAREFSENS | AWGN | +| | 30 | G-FR1-A2-5 | -56.2 – Δ OTAREFSENS | -56.2 – Δ OTAREFSENS | -56.2 – Δ OTAREFSENS | | | +| | 60 | G-FR1-A2-6 | -56.5 – Δ OTAREFSENS | -56.5 – Δ OTAREFSENS | -56.5 – Δ OTAREFSENS | | | +| 45 | 15 | G-FR1-A2-4 | -56.2 – Δ OTAREFSENS | -56.2 – Δ OTAREFSENS | -56.2 – Δ OTAREFSENS | -64.6 – Δ OTAREFSENS | AWGN | +| | 30 | G-FR1-A2-5 | -56.2 – Δ OTAREFSENS | -56.2 – Δ OTAREFSENS | -56.2 – Δ OTAREFSENS | | | +| | 60 | G-FR1-A2-6 | -56.5 – Δ OTAREFSENS | -56.5 – Δ OTAREFSENS | -56.5 – Δ OTAREFSENS | | | +| 50 | 15 | G-FR1-A2-4 | -56.2 – Δ OTAREFSENS | -56.2 – Δ OTAREFSENS | -56.2 – Δ OTAREFSENS | -64.1 – Δ OTAREFSENS | AWGN | +| | 30 | G-FR1-A2-5 | -56.2 – Δ OTAREFSENS | -56.2 – Δ OTAREFSENS | -56.2 – Δ OTAREFSENS | | | +| | 60 | G-FR1-A2-6 | -56.5 – Δ OTAREFSENS | -56.5 – Δ OTAREFSENS | -56.5 – Δ OTAREFSENS | | | +| 60 | 30 | G-FR1-A2-5 | -56.2 – Δ OTAREFSENS | -56.2 – Δ OTAREFSENS | -56.2 – Δ OTAREFSENS | -63.3 – Δ OTAREFSENS | AWGN | +| | 60 | G-FR1-A2-6 | -56.5 – Δ OTAREFSENS | -56.5 – Δ OTAREFSENS | -56.5 – Δ OTAREFSENS | | | + +| | | | | | | | | +|-----|----|------------|-----------------------------------------|-----------------------------------------|-----------------------------------------|-----------------------------------------|------| +| 70 | 30 | G-FR1-A2-5 | -56.2 –
$\Delta_{\text{OTAREFSENS}}$ | -56.2 –
$\Delta_{\text{OTAREFSENS}}$ | -56.2 –
$\Delta_{\text{OTAREFSENS}}$ | -62.7 –
$\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -56.5 –
$\Delta_{\text{OTAREFSENS}}$ | -56.5 –
$\Delta_{\text{OTAREFSENS}}$ | -56.5 –
$\Delta_{\text{OTAREFSENS}}$ | | | +| 80 | 30 | G-FR1-A2-5 | -56.2 –
$\Delta_{\text{OTAREFSENS}}$ | -56.2 –
$\Delta_{\text{OTAREFSENS}}$ | -56.2 –
$\Delta_{\text{OTAREFSENS}}$ | -62.1 –
$\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -56.5 –
$\Delta_{\text{OTAREFSENS}}$ | -56.5 –
$\Delta_{\text{OTAREFSENS}}$ | -56.5 –
$\Delta_{\text{OTAREFSENS}}$ | | | +| 90 | 30 | G-FR1-A2-5 | -56.2 –
$\Delta_{\text{OTAREFSENS}}$ | -56.2 –
$\Delta_{\text{OTAREFSENS}}$ | -56.2 –
$\Delta_{\text{OTAREFSENS}}$ | -61.5 –
$\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -56.5 –
$\Delta_{\text{OTAREFSENS}}$ | -56.5 –
$\Delta_{\text{OTAREFSENS}}$ | -56.5 –
$\Delta_{\text{OTAREFSENS}}$ | | | +| 100 | 30 | G-FR1-A2-5 | -56.2 –
$\Delta_{\text{OTAREFSENS}}$ | -56.2 –
$\Delta_{\text{OTAREFSENS}}$ | -56.2 –
$\Delta_{\text{OTAREFSENS}}$ | -61.1 –
$\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -56.5 –
$\Delta_{\text{OTAREFSENS}}$ | -56.5 –
$\Delta_{\text{OTAREFSENS}}$ | -56.5 –
$\Delta_{\text{OTAREFSENS}}$ | | | + +NOTE: The wanted signal mean power is the power level of a single instance of the corresponding reference measurement channel. This requirement shall be met for each consecutive application of a single instance of the reference measurement channel mapped to disjoint frequency ranges with a width corresponding to the number of resource blocks of the reference measurement channel each, except for one instance that might overlap one other instance to cover the full BS channel bandwidth. + +**Table 7.4.5.2-3a: Local Area BS dynamic range for $6.0 < f \leq 7.125$ GHz** + +| BS 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 | +|----------------------------|--------------------------|-------------------------------------------|--------------------------------------|------------------------------------------------------------|----------------------------| +| 20 | 15 | G-FR1-A2-4 | -55.2 – $\Delta_{\text{OTAREFSENS}}$ | -67.2 – $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -55.2 – $\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -55.5 – $\Delta_{\text{OTAREFSENS}}$ | | | +| 30 | 15 | G-FR1-A2-4 | -55.2 – $\Delta_{\text{OTAREFSENS}}$ | -65.4 – $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -55.2 – $\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -55.5 – $\Delta_{\text{OTAREFSENS}}$ | | | +| 40 | 15 | G-FR1-A2-4 | -55.2 – $\Delta_{\text{OTAREFSENS}}$ | -64.1 – $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -55.2 – $\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -55.5 – $\Delta_{\text{OTAREFSENS}}$ | | | +| 50 | 15 | G-FR1-A2-4 | -55.2 – $\Delta_{\text{OTAREFSENS}}$ | -63.1 – $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -55.2 – $\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -55.5 – $\Delta_{\text{OTAREFSENS}}$ | | | +| 60 | 30 | G-FR1-A2-5 | -55.2 – $\Delta_{\text{OTAREFSENS}}$ | -62.3 – $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -55.5 – $\Delta_{\text{OTAREFSENS}}$ | | | +| 70 | 30 | G-FR1-A2-5 | -55.2 – $\Delta_{\text{OTAREFSENS}}$ | -61.7 – $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -55.5 – $\Delta_{\text{OTAREFSENS}}$ | | | +| 80 | 30 | G-FR1-A2-5 | -55.2 – $\Delta_{\text{OTAREFSENS}}$ | -61.1 – $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -55.5 – $\Delta_{\text{OTAREFSENS}}$ | | | +| 90 | 30 | G-FR1-A2-5 | -55.2 – $\Delta_{\text{OTAREFSENS}}$ | -60.5 – $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -55.5 – $\Delta_{\text{OTAREFSENS}}$ | | | +| 100 | 30 | G-FR1-A2-5 | -55.2 – $\Delta_{\text{OTAREFSENS}}$ | -60.1 – $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | -55.5 – $\Delta_{\text{OTAREFSENS}}$ | | | + +NOTE: The wanted signal mean power is the power level of a single instance of the corresponding reference measurement channel. This requirement shall be met for each consecutive application of a single instance of the reference measurement channel mapped to disjoint frequency ranges with a width corresponding to the number of resource blocks of the reference measurement channel each, except for one instance that might overlap one other instance to cover the full BS channel bandwidth. + +## 7.5 OTA 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 *BS type 1-O*, the minimum requirement is in TS 38.104 [2], clause 10.5.1.2. + +For *BS type 2-O*, the minimum requirement is in TS 38.104 [2], clause 10.5.1.3. + +#### 7.5.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.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. + +*Base Station 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}}^{\text{RFBW}}$ and $B'_{\text{RFBW\_T}}^{\text{RFBW}}$ in multi-band operation, see clause 4.9.1. + +Directions to be tested: + +- For BS type 1-O, receiver target reference direction (D.31), +- For BS type 2-O, OTA REFSENS receiver target reference direction (D.54). + +##### 7.5.1.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.3. +- 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) Align the BS 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) For FDD operation, set the BS to transmit beam(s) of the same operational band as the OSDD or *OTA REFSENS RoAoA* being tested according to the appropriate test configuration in clauses 4.7 and 4.8. + +- 7) Set the test signal mean power so that the calibrated radiated power at the BS 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.5.1.4.1-1 for *BS type 1-O* and table 7.5.1.4.2-1 for *BS type 2-O*. + - b) 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.4.1-1 for *BS type 1-O* and table 7.5.1.4.2-1 for *BS type 2-O*. +- 8) 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 clause 4.1. + +### 7.5.1.5.2 Test requirements for *BS 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, 7.5.1.5.2-1a 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 TS 38.104 [2] annex D. + +The OTA ACS requirement is applicable outside the Base Station RF Bandwidth or Radio Bandwidth. The OTA interfering signal offset is defined relative to the Base station RF Bandwidth edges or Radio Bandwidth edges. + +For RIBs supporting operation in *non-contiguous spectrum* within any operating band, the 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 Base Station RF Bandwidth edges inside the Inter RF Bandwidth gap. + +**Table 7.5.1.5.2-1: OTA ACS requirement for *BS type 1-O* for $f \leq 6.0$ GHz** + +| BS 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$ GHz $< f \leq 4.2$ GHz | $4.2$ GHz $< f \leq 6.0$ GHz | | | | | +| 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 (Note 1) | $EIS_{minSENS} + 6$ dB | | | Wide Area BS: -52 – $\Delta_{minSENS}$
Medium Range BS: -47 – $\Delta_{minSENS}$
Local Area BS: -44 – $\Delta_{minSENS}$ | | | | +| NOTE 1: The SCS for the lowest/highest carrier received is the lowest SCS supported by the BS for that bandwidth. | | | | | | | | +| NOTE 2: $EIS_{minSENS}$ depends on the BS channel bandwidth as specified in TS 38.104 [2], clause 10.2.1. | | | | | | | | + +**Table 7.5.1.5.2-1a: OTA ACS requirement for BS type 1-O for band 6.0 GHz < f ≤ 7.125 GHz** + +| BS channel bandwidth of the lowest/highest carrier received (MHz) | Wanted signal mean power (dBm) (Note 2) | Interfering signal mean power (dBm) | +|--------------------------------------------------------------------------|------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------| +| 20, 30, 40, 50, 60, 70, 80, 90, 100 (Note 1) | $EIS_{minSENS} + 6$ dB | Wide Area BS: $-55 - \Delta_{minSENS}$
Medium Range BS: $-50 - \Delta_{minSENS}$
Local Area BS: $-47 - \Delta_{minSENS}$ | + +NOTE 1: The SCS for the lowest/highest carrier received is the lowest SCS supported by the BS for that bandwidth. + +NOTE 2: $EIS_{minSENS}$ depends on the BS channel bandwidth as specified in TS 38.104 [2], clause 10.2.1. + +**Table 7.5.1.5.2-2: OTA ACS interferer frequency offset for BS type 1-O** + +| 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$ | | +| 30 | $\pm 9.4725$ | 20 MHz DFT-s-OFDM NR signal, 15 kHz SCS, 100 RBs | +| 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 BS 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 TS 38.104 [2] annex D. + +The OTA ACS requirement is applicable outside the Base Station RF Bandwidth. The OTA interfering signal offset is defined relative to the Base station 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 BS type 2-O** + +| Frequency range | BS channel bandwidth of the lowest/highest carrier received (MHz) | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | +|-----------------|-------------------------------------------------------------------|---------------------------------|------------------------------------------------------------------------------------------------------------------------------| +| FR2-1 | 50, 100, 200, 400 | $EIS_{REFSENS} + 6$ dB (Note 3) | $EIS_{REFSENS\_50M} + 27.7 + \Delta_{FR2\_REFSENS}$ (Note 1) | +| FR2-2 | 100, 400, 800, 1600, 2000 | | $EIS_{REFSENS\_50M} + 26.7 + \Delta_{FR2\_REFSENS}$ (Note 2)
$EIS_{REFSENS\_50M} + 28.7 + \Delta_{FR2\_REFSENS}$ (Note 4) | + +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 specified in TS 38.104 [2], clause 10.3.3. +NOTE 4: Applicable to bands defined within the frequency spectrum range of 52.6 – 71 GHz. + +**Table 7.5.1.5.3-2: OTA ACS interferer frequency offset for BS type 2-O** + +| Frequency range | 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 | +|-----------------|-------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------| +| FR2-1 | 50 | $\pm 24.29$ | 50 MHz DFT-s-OFDM NR signal, 60 kHz SCS, 64 RBs | +| | 100 | $\pm 24.31$ | | +| | 200 | $\pm 24.29$ | | +| | 400 | $\pm 24.31$ | | +| FR2-2 | 100 | $\pm 48.58$ | 100 MHz DFT-s-OFDM NR signal, 120 kHz SCS, 64 RBs | +| | 400 | $\pm 48.58$ | | +| | 800 | $\pm 48.62$ | | +| | 1600 | $\pm 48.58$ | | +| | 2000 | $\pm 48.62$ | | + +## 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 BS type 1-O, the minimum requirement is in TS 38.104 [2], clause 10.5.2.2. + +For BS type 2-O, the minimum requirement is in TS 38.104 [2], clause 10.5.2.3. + +### 7.5.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.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. + +*Base Station 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}}$ and $B'_{\text{RFBW\_T}}$ in multi-band operation, see clause 4.9.1. + +Directions to be tested: + +For BS type 1-O: + +- receiver target reference direction for the minSENS OSDD (D.31), +- OTA REFSENS conformance test directions (D.55), + +For BS 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 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.3. +- 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) Align the BS 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) For FDD operation, set the BS to transmit beam(s) of the same operational band as the OSDD or *OTA REFSENS RoAoA* being tested according to the appropriate test configuration in clauses 4.7 and 4.8. +- 7) Set the test signal mean power so that the calibrated radiated power at the BS Antenna Array coordinate system reference point is as follows: + +For general OTA blocking: + +- a) Set the signal generator for the wanted signal to transmit as specified in table 7.5.2.5.2-1 for *BS type 1-O* and table 7.5.2.5.3-1 for *BS type 2-O*. +- b) 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 for *BS type 1-O* and table 7.5.2.5.3-1 for *BS type 2-O*. The interfering signal shall be swept with a step size of 1 MHz for *BS type 1-O* or as indicated in Table 7.5.2.4.2-1 for *BS type 2-O* starting from the minimum offset to the channel edges of the wanted signals. + +**Table 7.5.2.4.2-1: FR2 Interferer signal step size** + +| Minimum supported BS channel bandwidth (MHz) | Measurement step size (MHz) | +|----------------------------------------------|-----------------------------| +| 50 | 15 | +| 100 | 30 | +| 200 | 60 | +| 400 | 60 | + +For OTA narrowband blocking: + +- a) Set the signal generator for the wanted signal to transmit as specified in table 7.5.2.5.2-2 for *BS type 1-O*. + +- b) 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 for *BS type 1-O*. 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. +- 8) 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. +- 9) 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 clause 4.1. + +### 7.5.2.5.2 Test requirements for *BS 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. Narrowband blocking requirements shall not be applied for band n104. 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 TS 38.104 [2] annex D. + +The OTA 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-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_{OOB}$ to $F_{UL\_high} + \Delta f_{OOB}$ , excluding the downlink frequency range of the FDD *operating band*, where the $\Delta f_{OOB}$ for *BS type 1-O* is defined in table 7.5.2.5.2-0. + +**Table 7.5.2.5.2-0: $\Delta f_{OOB}$ offset for NR operating bands in FR1** + +| BS type | Operating band characteristics | $\Delta f_{OOB}$ (MHz) | +|-------------|----------------------------------------------------------|------------------------| +| BS type 1-O | $F_{UL\_high} - F_{UL\_low} < 100$ MHz | 20 | +| | $100$ MHz $\leq F_{UL\_high} - F_{UL\_low} \leq 900$ MHz | 60 | +| | n104 | 100 | + +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 BS type 1-O** + +| 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 | +|-------------------------------------------------------------------|-----------------------------------------|------------------------------|--------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------| +| | $f \leq 3.0$ GHz | $3.0$ GHz $< f \leq 4.2$ GHz | $4.2$ GHz $< f \leq 7.125$ GHz | | | | +| 5, 10, 15, 20 | $EIS_{REFSENS} + x$ dB (NOTE 2, NOTE 4) | | | Wide Area BS: -43 - $\Delta_{OTAREFSENS}$
Medium Range BS: -38 - $\Delta_{OTAREFSENS}$
Local Area BS: -35 - $\Delta_{OTAREFSENS}$ (NOTE 2) | $\pm 7.5$ | 5 MHz DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| | $EIS_{minSENS} + x$ dB (NOTE 3, NOTE 4) | | | Wide Area BS: -43 - $\Delta_{minSENS}$
Medium Range BS: -38 - $\Delta_{minSENS}$
Local Area BS: -35 - $\Delta_{minSENS}$ (NOTE 3) | | | +| 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | $EIS_{REFSENS} + x$ dB (NOTE 2, NOTE 4) | | | Wide Area BS: -43 - $\Delta_{OTAREFSENS}$
Medium Range BS: -38 - $\Delta_{OTAREFSENS}$
Local Area BS: -35 - $\Delta_{OTAREFSENS}$ (NOTE 2) | $\pm 30$ | 20 MHz DFT-s-OFDM NR signal, 15 kHz SCS, 100 RBs | +| | $EIS_{minSENS} + x$ dB (NOTE 3, NOTE 4) | | | Wide Area BS: -43 - $\Delta_{minSENS}$
Medium Range BS: -38 - $\Delta_{minSENS}$
Local Area BS: -35 - $\Delta_{minSENS}$ (NOTE 3) | | | + +NOTE 1: $EIS_{REFSENS}$ and $EIS_{minSENS}$ depends on the BS channel bandwidth as specified in TS 38.104 [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. + +NOTE 4: 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.5.2.5.2-2: OTA narrowband blocking requirement for BS type 1-O** + +| BS channel bandwidth of the lowest/highest carrier received (MHz) | OTA Wanted signal mean power (dBm) | | | OTA Interfering signal mean power (dBm) | +|--------------------------------------------------------------------------|-------------------------------------------|---------------------------------|---------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| | f ≤ 3.0 GHz | 3.0 GHz < f ≤ 4.2 GHz | 4.2 GHz < f ≤ 6.0 GHz | | +| 5, 10, 15, 20 | EIS REFSENS + 6 dB (NOTE 3) | | | Wide Area BS: -49 - Δ OTAREFSENS
Medium Range BS: -44 - Δ OTAREFSENS
Local Area BS: -41 - Δ OTAREFSENS | +| | EIS minSENS + 6 dB (NOTE 4) | | | Wide Area BS: -49 - Δ minSENS
Medium Range BS: -44 - Δ minSENS
Local Area BS: -41 - Δ minSENS | +| 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | EIS REFSENS + 6 dB (NOTE 3) | | | Wide Area BS: -49 - Δ OTAREFSENS
Medium Range BS: -44 - Δ OTAREFSENS
Local Area BS: -41 - Δ OTAREFSENS | +| | EIS minSENS + 6 dB (NOTE 4) | | | Wide Area BS: -49 - Δ minSENS
Medium Range BS: -44 - Δ minSENS
Local Area BS: -41 - Δ minSENS | + +NOTE 1: The SCS for the lowest/highest carrier received is the lowest SCS supported by the BS for that bandwidth. + +NOTE 2: EISREFSENS and EISminSENS depends on the *BS channel bandwidth* as specified in TS 38.104 [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 BS type 1-O** + +| 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 is positioned at the stated offset, the channel bandwidth of the interfering signal is located adjacently to the lower/upper Base Station RF Bandwidth edge. + +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 BS 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 BS 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 TS 38.104 [2] annex D. + +The OTA blocking requirements are applicable outside the *Base Station RF Bandwidth*. The interfering signal offset is defined relative to the *Base Station RF Bandwidth edges*. + +For BS 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 BS 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** + +| BS type | Frequency range | Operating band characteristics (MHz) | $\Delta f_{\text{OOB}}$ (MHz) | +|-------------|-----------------|--------------------------------------------------------------|-------------------------------| +| BS type 2-O | FR2-1 | $F_{\text{UL\_high}} - F_{\text{UL\_low}} \leq 4000$ | 1500 | +| | FR2-2 | $4000 < F_{\text{UL\_high}} - F_{\text{UL\_low}} \leq 14000$ | 3500 | + +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 BS type 2-O** + +| Frequency range | BS 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 Base Station RF Bandwidth edge or sub-block edge inside a sub-block gap (MHz) | Type of OTA interfering signal | +|-----------------|-------------------------------------------------------------------|------------------------------------|--------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------| +| FR2-1 | 50, 100, 200, 400 | $EIS_{\text{REFSENS}} + 6$ dB | $EIS_{\text{REFSENS\_50M}} + 33 + \Delta_{\text{FR2\_REFSENS}}$ dB | $\pm 75$ | 50 MHz DFT-s-OFDM NR signal, 60 kHz SCS, 64 RBs | +| FR2-2 | 100, 400, 800, 1600, 2000 | | $EIS_{\text{REFSENS\_50M}} + 36 + \Delta_{\text{FR2\_REFSENS}}$ dB | $\pm 150$ | 100 MHz DFT-s-OFDM NR signal, 120 kHz SCS, 64 RBs | + +NOTE: $EIS_{\text{REFSENS}}$ and $EIS_{\text{REFSENS\_50M}}$ are given in TS 38.104 [2], clause 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 + +The minimum requirement for *BS type 1-O* is defined in TS 38.104 [2], clause 10.6.2. + +The minimum requirement for *BS type 2-O* is defined in TS 38.104 [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. + +*Base Station 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}}^{\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}}$ , blocking testing above the highest operating band may be omitted. +- For $B'_{\text{RFBW\_T}}^{\text{RFBW}}$ , blocking testing below the lowest operating band may be omitted. + +Directions to be tested: + +- For *BS type 1-O*, receiver target reference direction (D.31). +- For *BS type 2-O*, OTA REFSENS receiver target reference direction (D.54). + +### 7.6.4.2 Procedure + +#### 7.6.4.2.1 *BS type 1-O* procedure for out-of-band blocking + +- 1) Place BS and the test antenna(s) according to annex E.2.4.1. +- 2) Align the BS 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 *BS* and the blocking frequencies. If the test antenna does not cover both the wanted and interfering signal frequencies, separate test antennas for the wanted and interfering signal are required. +- 5) The OTA blocking interferer is injected into the test antenna, with the blocking interferer producing specified interferer field strength level for each supported polarization. The interferer shall be *polarization matched* in-band and the polarization maintained for out-of-band frequencies. +- 6) 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. +- 7) For FDD operation, configure the beam peak direction for the transmitter units associated with the RIB under test according to the declared reference beam direction pair for the appropriate beam identifier with the carrier set-up and power allocation according to the applicable test configuration(s) (see clause 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. +- 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. 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. +- 9) 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. +- 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. +- 11) Repeat for all supported polarizations. + +In addition, for *multi-band RIB*, the following steps shall apply: + +- 12) 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 *BS type 1-O* procedure for co-location blocking + +- 1) Place NR BS 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 BS 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 BS 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. +- 8) For FDD operation, configure the beam peak direction for the transmitter units associated with the RIB under test according to the declared reference beam direction pair for the appropriate beam identifier with the carrier set-up and power allocation according to the applicable test configuration(s) (see clause 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. +- 9) 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. +- 10) 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). +- 11) 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: + +- 12) 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 *BS type 2-O* procedure for out-of-band blocking + +- 1) Place BS and the test antenna(s) according to annex E.2.4.1. +- 2) Align the BS 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 *BS* and the blocking frequencies. If the test antenna does not cover both the wanted and interfering signal frequencies, separate test antennas for the wanted and interfering signal are required. +- 5) The OTA blocking interferer is injected into the test antenna, with the blocking interferer producing specified interferer field strength level for each supported polarization. The interferer shall be *polarization matched* in-band and the polarization maintained for out-of-band frequencies. +- 6) 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. + +- 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 and table 7.6.4.2.3-2. +- 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 for FR2-1** + +| Frequency range (MHz) | Minimum supported BS 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 | + +**Table 7.6.4.2.3-2: Interferer signal step size for FR2-2** + +| Frequency range (MHz) | Minimum supported BS channel bandwidth (MHz) | Measurement step size (MHz) | +|-----------------------|----------------------------------------------|-----------------------------| +| 30 to 6000 | 100, 400, 800, 1600, 2000 | 1 | +| 6000 to 142000 | 100 | 30 | +| | 400 | 60 | +| | 800 | 240 | +| | 1600 | 240 | +| | 2000 | 240 | + +- 10) Repeat for all supported polarizations. + +## 7.6.5 Test requirements + +### 7.6.5.1 Requirement for BS 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 [2] for each BS 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 [2] shall be excluded from the OTA out-of-band blocking requirement. + +For BS type 1-O the OTA out-of-band blocking requirement apply from $30\text{ MHz}$ to $F_{UL\_low} - \Delta f_{OOB}$ and from $F_{UL\_high} + \Delta f_{OOB}$ up to $12750\text{ MHz}$ , including the downlink frequency range of the FDD operating band for BS supporting FDD. The $\Delta f_{OOB}$ for BS 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 [2], 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 BS receivers when NR, E-UTRA BS, UTRA BS, CDMA BS or GSM/EDGE BS operating in a different frequency band are co-located with a BS. + +The interferer power level is specified at the CLTA conducted input(s) as the signal power per supported polarization. + +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 clause 10.3.2 in TS 38.104 [2] for each *BS channel bandwidth* and further specified in annex A.1. + +For *BS type 1-O* the OTA blocking requirement for co-location with BS 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 in other frequency bands** + +| Frequency range of interfering signal | Wanted signal mean power (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 | EIS minSENS + 6 dB
(Note 1) | +46 | +38 | +24 | CW carrier | + +NOTE 1: EISminSENS depends on the BS class and on the *BS channel bandwidth* as specified in TS 38.104 [2], clause 10.2.1. +NOTE 2: The requirement does not apply when the interfering signal falls within any of the supported uplink operating band(s) or in $\Delta f_{OOB}$ immediately outside any of the supported uplink operating band(s). +NOTE 3: The specified interferer signal power level is applied to all supported CLTA input ports.. + +### 7.6.5.2 Requirement for *BS 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 and table 7.6.5.2.1-2, 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.104 [2] for each *BS channel bandwidth* and further specified in annex A.1. + +For *BS type 2-O* within FR2-1 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 *BS type 2-O* is defined in table 7.5.2.5.3-0. + +For *BS type 2-O* within FR2-2 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 [142] GHz. The $\Delta f_{OOB}$ for *BS 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 for FR2-1** + +| 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^{nd}$ harmonic of the upper frequency edge of the operating band, 60000) | | 0.1 | | +| NOTE: $EIS_{REFSENS}$ is given in TS 38.104 [2], clause 10.3.3. | | | | + +**Table 7.6.5.2.1-2: OTA out-of-band blocking performance requirement for FR2-2** + +| 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 $2^{nd}$ harmonic of the upper frequency edge of the operating band | | 0.1 | | +| NOTE: $EIS_{REFSENS}$ is given in TS 38.104 [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 ITU-R recommendation SM.329 [5]. + +For *multi-band RIB* the above exclusion applies for each supported *operating band*. + +The OTA receiver spurious emission limits for FR2 shall apply from 30 MHz to $2^{nd}$ 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 BS operating in FDD, OTA RX spurious emissions requirement do not apply as they are superseded by the OTA TX spurious emissions requirement. This is due to the fact that TX and RX spurious emissions cannot be distinguished in OTA domain. + +For a BS 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 *BS type 1-O* and *BS type 2-O* is total radiated power (TRP), with the requirement defined at the RIB. + +### 7.7.2 Minimum requirement + +The minimum requirement for *BS type 1-O* is specified in TS 38.104 [2], clause 10.7.2. + +The minimum requirement for *BS type 2-O* is specified in TS 38.104 [2], clause 10.7.3. + +### 7.7.3 Test purpose + +The test purpose is to verify if the receiver radiated spurious emissions from the BS 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) for FR2-1 + - T when testing from $F_{DL\_high} + \Delta f_{OBUE}$ to 2nd harmonic (or to 142 GHz) for FR2-2 + +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) for FR2-1 + - $T_{RFBW}$ when testing from $F_{DL\_high} + \Delta f_{OBUE}$ to 2nd harmonic (or to 142 GHz) for FR2-2 + +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). + +#### 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. When calibrated and operated within the guidance of 3GPP TR 37.941 [29] the measurement methods are applicable and selected depending on availability at the test facility. + +- 1) Place the BS at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (D.2) of the BS 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. + - 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 for FR1 and Table 4.1.2.3-2 for FR2. +- 5) Set the TDD BS to receive only. +- 6) Orient the positioner (and BS) in order that the direction to be tested aligns with the test antenna such that measurements to determine TRP can be performed (see annex 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 *BS 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 *BS 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 BS receiver spurious emission limits for BS 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 | +| 12.75 GHz - 26 GHz | -30 + X dBm | 1 MHz | Note 1, Note 2, Note 6, Note 9 | +| 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.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.
NOTE 9: Applies for Band for which the upper frequency edge of the UL operating band is greater than 5.2 GHz. | | | | + +## 7.7.5.2 Test requirement for BS 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 BS 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 [2], s4.1.
NOTE 2: Limit and bandwidth as in ERC Recommendation 74-01 [19], Annex 2.
NOTE 3: Upper frequency as in ITU-R SM.329 [2], s2.5 table 1.
NOTE 4: The step frequencies $F_{step,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 BS 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 | +| n262 | 37.2 | 45.2 | 45.7 | 49.7 | 50.2 | 58.2 | +| n263 | 18 | 43 | 53.5 | 74.5 | 85 | 127 | + +In addition, the following requirement may be applied for protection of EESS for BS 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 BS brought into use on or before 1 September 2027. NOTE 2: This limit applies to BS 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 requirement for *BS type 1-O* is in TS 38.104 [2], clause 10.8.2. + +The minimum requirement for *BS type 2-O* is in TS 38.104 [2], clause 10.8.3. + +### 7.8.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.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. + +*Base Station 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}}$ and $B'_{\text{RFBW\_T}}$ for multi-band operation, see clause 4.9.1. + +Directions to be tested: + +- OTA REFSENS receiver target reference direction (D.54). +- In addition, for *BS type 1-O*, receiver target reference direction (D.31). + +## 7.8.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.6. +- 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) Align the BS to that the wanted signal and interferer signal is *polarization matched* with the test antenna(s). +- 5) Configure the beam peak direction of the BS according to declared reference beam direction pair for the appropriate beam identifier. +- 6) For FDD operation, set the BS to transmit the beam(s) of the same operational band as the *OTA REFSENS RoAoA* or OSDD being tested according to the appropriate test configuration in clauses 4.7 and 4.8. +- 7) Set the test signal mean power so the calibrated radiated power at the BS Antenna Array coordinate system reference point is as specified as follows: + - a) Set the signal generator for the wanted signal to transmit as specified in table 7.8.5.1-1 (for general intermodulation) or 7.8.5.1-3 (for narrowband intermodulation) for *BS type 1-O*, or table 7.8.5.2-1 (for general intermodulation) for *BS type 2-O*. + - b) Set the signal generator for the interfering signal at the same frequency as the wanted signal to transmit as specified in table 7.8.5.1-1 (for general intermodulation) or 7.8.5.1-3 (for narrowband intermodulation) for *BS type 1-O*, or table 7.8.5.2-1 (for general intermodulation) for *BS type 2-O*. +- 8) Set the signal generator for the interfering signal to transmit at the frequency offset and as specified in table 7.8.5.1-2 (for general intermodulation) or 7.8.5.1-4 (for narrowband intermodulation) for *BS type 1-O*, or table 7.8.5.2-2 (for general intermodulation) for *BS type 2-O*. +- 9) 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. +- 10) Repeat for all the specified measurement directions and supported polarizations. + +In addition, for *multi-band RIB(s)*, the following steps shall apply: + +- 11) For *multi-band RIBs* and single band tests, repeat the steps above per involved band where single band test configurations and test models shall apply with no carrier activated in the other band. + +## 7.8.5 Test requirement + +### 7.8.5.1 *BS 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_{\text{REFSENS}}$ : 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 $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.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. Narrowband intermodulation requirements shall not be applied for band n104. + +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 *BS 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 *BS 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 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 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 *BS 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 Base Station 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 Base Station RF Bandwidth edges inside the Inter RF Bandwidth gap. + +**Table 7.8.5.1-1: General intermodulation requirement** + +| BS class | Wanted Signal mean power (dBm) | Mean power of interfering signals (dBm) | Type of interfering signal | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|-----------------------------------------|----------------------------| +| Wide Area BS | $EIS_{REFSENS} + 6$ dB | $-52 - \Delta_{OTAREFSENS}$ | See table 7.8.5.1-2 | +| | $EIS_{minSENS} + 6$ dB | $-52 - \Delta_{minSENS}$ | | +| Medium Range BS | $EIS_{REFSENS} + 6$ dB | $-47 - \Delta_{OTAREFSENS}$ | | +| | $EIS_{minSENS} + 6$ dB | $-47 - \Delta_{minSENS}$ | | +| Local Area BS | $EIS_{REFSENS} + 6$ dB | $-44 - \Delta_{OTAREFSENS}$ | | +| | $EIS_{minSENS} + 6$ dB | $-44 - \Delta_{minSENS}$ | | +| NOTE: $EIS_{REFSENS}$ and $EIS_{minSENS}$ depend on the BS class and on the BS channel bandwidth as specified in TS 38.104 [2], clause 10.3.2 and 10.2.1. | | | | + +**Table 7.8.5.1-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 | ±7.5 | CW | +| | ±17.5 | 5MHz DFT-s-OFDM NR signal (Note 1) | +| 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 | 20 MHz 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 | 20 MHz 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 *Base Station RF Bandwidth* edge. + +**Table 7.8.5.1-3: Narrowband intermodulation performance requirement in FR1** + +| BS class | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | Type of interfering signal | +|-----------------|-------------------------------------------|-------------------------------------|----------------------------| +| Wide Area BS | EIS REFSENS + 6 dB
(Note 1) | -52 - Δ OTAREFSENS | See table 7.8.5.1-4 | +| | EIS minSENS + 6 dB
(Note 1) | -52 - Δ minSENS | | +| Medium Range BS | EIS REFSENS + 6 dB
(Note 1) | -47 - Δ OTAREFSENS | | +| | EIS minSENS + 6 dB
(Note 1) | -47 - Δ minSENS | | +| Local Area BS | EIS REFSENS + 6 dB
(Note 1) | -44 - Δ OTAREFSENS | | +| | EIS minSENS + 6 dB
(Note 1) | -44 - Δ minSENS | | + +NOTE: EISREFSENS and EISminSENS depends on the BS channel bandwidth as specified in TS 38.104 [2], clause 10.3.2 and 10.2.1. + +**Table 7.8.5.1-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 signal | +|--------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------| +| 5 | ±360 | CW | +| | ±1420 | 5MHz DFT-s-OFDM NR signal, 1 RB (NOTE 1) | +| 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 | 20 MHz 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 | 20 MHz 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 BS channel bandwidth of the interfering signal is located adjacently to the lower/upper 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.5.2 BS 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 OTA REFSENS RoAoA*. The reference measurement channel for the wanted signal is identified in table 7.3.5.3-1 for each *BS 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 FR2-2 with 400 MHz, 800 MHz, 1600 MHz and 2000 MHz case. + +The receiver intermodulation requirement is applicable outside the Base Station RF Bandwidth. The interfering signal offset is defined relative to the Base Station RF Bandwidth edges. + +**Table 7.8.5.2-1: General intermodulation requirement** + +| BS 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, 800, 1600, 2000 | $EIS_{REFSENS\_50M} + 25 + \Delta_{FR2\_REFSENS}$ dB (Note 2),
$EIS_{REFSENS\_50M} + 28 + \Delta_{FR2\_REFSENS}$ (Note 3) | $EIS_{REFSENS} + 6\text{dB}$ | See table 7.8.5.2-2 | +| NOTE 1: $EIS_{REFSENS}$ and $EIS_{REFSENS\_50M}$ are given in TS 38.104 [2], clause 10.3.3. | | | | +| NOTE 2: Applicable to bands defined within the frequency spectrum range of FR2-1. | | | | +| NOTE 3: Applicable to bands defined within the frequency spectrum range of FR2-2. | | | | + +**Table 7.8.5.2-2: Interfering signals for intermodulation requirement** + +| Frequency range | BS channel bandwidth of the lowest/highest carrier received (MHz) | Interfering signal centre frequency offset from the Base Station RF Bandwidth edge (MHz) | Type of interfering signal | +|-----------------|-------------------------------------------------------------------|------------------------------------------------------------------------------------------|--------------------------------------| +| FR2-1 | 50 | ±7.5 | CW | +| | | ±40 | 50MHz DFT-s-OFDM NR signal (Note 1) | +| | 100 | ±6.88 | CW | +| | | ±40 | 50MHz DFT-s-OFDM NR signal (Note 1) | +| | 200 | ±5.64 | CW | +| | | ±40 | 50MHz DFT-s-OFDM NR signal (Note 1) | +| | 400 | ±6.02 | CW | +| | | ±45 | 50MHz DFT-s-OFDM NR signal (Note 1) | +| FR2-2 | 100 | ±7.5 | CW | +| | | ±65 | 100MHz DFT-s-OFDM NR signal (Note 2) | +| | 400 | ±6.28 | CW | +| | | ±70 | 100MHz DFT-s-OFDM NR signal (Note 2) | +| | 800 | [±7.3] | CW | +| | | [±105] | 100MHz DFT-s-OFDM NR signal (Note 2) | +| | 1600 | [±5.86] | CW | +| | | [±145] | 100MHz DFT-s-OFDM NR signal (Note 2) | +| | 2000 | ±7.48 | CW | +| | | ±210 | 100MHz DFT-s-OFDM NR signal (Note 2) | + +NOTE 1: For the 60 kHz subcarrier spacing, the number of RB is 64. For the 120 kHz subcarrier spacing, the number of RB is 32. + +NOTE 2: Number of RBs is 64 with 120 kHz subcarrier spacing. + +## 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.141-1 [3] and shall be time aligned with the wanted signal. + +### 7.9.2 Minimum requirement + +The minimum requirement for BS type 1-O is in TS 38.104 [2], clause 10.9.2. + +The minimum requirement for BS type 2-O is in TS 38.104 [2], clause 10.9.3. + +### 7.9.3 Test purpose + +The purpose of this test is to verify the BS 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 BS type 1-O, receiver target reference direction (D.31), +- For BS type 2-O, OTA REFSENS receiver target reference direction (D.54). + +#### 7.9.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.7. +- 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) Align the BS 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) For FDD operation, set the BS to transmit beam(s) of the same operational band as the *OTA REFSENS RoAoA* or OSDD being tested according to the appropriate test configuration in clauses 4.7 and 4.8. +- 7) Set the test signal mean power so the calibrated radiated power at the BS Antenna Array coordinate system reference point is as specified as follows: + - a) Adjust the signal generator for the wanted signal as specified in: + +For BS type 1-O, table 7.9.5.1-1 for BS of Wide Area BS class, in table 7.9.5.1-2 for BS of Local Area BS class and in table 7.9.5.1-3 for BS of Medium Range BS class on one side of the $F_c$ . + +For BS type 2-O, tables 7.9.5.2-1, 7.9.5.2-2 and 7.9.5.2-3 on one side of the $F_c$ . + - b) Adjust the signal generator for the interfering signal as specified in: + +For BS type 1-O, table 7.9.5.1-1 for BS of Wide Area BS class, in table 7.9.5.1-2 for BS of Local Area BS class and in table 7.9.5.1-3 for BS of Medium Range BS class at opposite side of the $F_c$ and adjacent to the wanted signal. + +For BS type 2-O, tables 7.9.5.2-1, 7.9.5.2-2 and 7.9.5.2-3 at opposite side of the $F_c$ and adjacent to the wanted signal. +- 8) Measure throughput according to annex A.1 for each supported polarization. +- 9) 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. +- 10) Repeat for all the specified measurement directions and supported polarizations. + +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. + +## 7.9.5 Test requirement + +### 7.9.5.1 BS 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 *BS 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 tables 7.9.5.1-1 and 7.9.5.1-1a for Wide Area BS, in tables 7.9.5.1-2 and 7.9.5.1-2a for Medium Range BS and in tables 7.9.5.1-3 and 7.9.5.1-3a for Local Area BS. + +**Table 7.9.5.1-1: Wide Area BS in-channel selectivity for $f \leq 6$ GHz** + +| BS 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 | | | +| 5 | 15 | G-FR1-A1-7 | -98.9-
$\Delta_{minSENS}$ | -98.5-
$\Delta_{minSENS}$ | -98.2-
$\Delta_{minSENS}$ | -81.4 -
$\Delta_{minSENS}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 10 RBs | +| 10, 15, 20, 25, 30, 35 | 15 | G-FR1-A1-1 | -97-
$\Delta_{minSENS}$ | -96.6-
$\Delta_{minSENS}$ | -96.3-
$\Delta_{minSENS}$ | -77.4 -
$\Delta_{minSENS}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 40, 45, 50 | 15 | G-FR1-A1-4 | -90.6-
$\Delta_{minSENS}$ | -90.2-
$\Delta_{minSENS}$ | -89.9-
$\Delta_{minSENS}$ | -71.4 -
$\Delta_{minSENS}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 100 RBs | +| 5 | 30 | G-FR1-A1-8 | -99.6-
$\Delta_{minSENS}$ | -99.2-
$\Delta_{minSENS}$ | -98.9-
$\Delta_{minSENS}$ | -81.4 -
$\Delta_{minSENS}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 5 RBs | +| 10, 15, 20, 25, 30, 35 | 30 | G-FR1-A1-2 | -97.1-
$\Delta_{minSENS}$ | -96.7-
$\Delta_{minSENS}$ | -96.4-
$\Delta_{minSENS}$ | -78.4 -
$\Delta_{minSENS}$ | 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_{minSENS}$ | -90.5-
$\Delta_{minSENS}$ | -90.2-
$\Delta_{minSENS}$ | -71.4 -
$\Delta_{minSENS}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 50 RBs | +| 10, 15, 20, 25, 30, 35 | 60 | G-FR1-A1-9 | -96.5-
$\Delta_{minSENS}$ | -96.1-
$\Delta_{minSENS}$ | -95.8-
$\Delta_{minSENS}$ | -78.4 -
$\Delta_{minSENS}$ | 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_{minSENS}$ | -90.6-
$\Delta_{minSENS}$ | -90.3-
$\Delta_{minSENS}$ | -71.6 -
$\Delta_{minSENS}$ | 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.9.5.1-1a: Wide Area BS in-channel selectivity for $6 < f \leq 7.125$ GHz** + +| BS 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 | +|-----------------------------|--------------------------|-------------------------------------------|--------------------------------------|---------------------------------------|-------------------------------------------| +| 20, 30 | 15 | G-FR1-A1-1 | -94.9
$-\Delta_{\min\text{SENS}}$ | -76.4 -
$\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 40, 50 | 15 | G-FR1-A1-4 | -88.5
$-\Delta_{\min\text{SENS}}$ | -70.4 -
$\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 100 RBs | +| 20, 30 | 30 | G-FR1-A1-2 | -95.0
$-\Delta_{\min\text{SENS}}$ | -77.4 -
$\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 10 RBs | +| 40, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 | -88.8
$-\Delta_{\min\text{SENS}}$ | -70.4 -
$\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 50 RBs | +| 20, 30 | 60 | G-FR1-A1-9 | -94.4
$-\Delta_{\min\text{SENS}}$ | -77.4 -
$\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 60 kHz SCS, 5 RBs | +| 40, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 | -88.9
$-\Delta_{\min\text{SENS}}$ | -70.6 -
$\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 60 kHz SCS, 24 RBs | + +**Table 7.9.5.1-2: Medium Range BS in-channel selectivity for $f \leq 6.0$ GHz** + +| BS 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 | | | +| 5 | 15 | G-FR1-A1-7 | -93.9-
$\Delta_{\min\text{SENS}}$ | -93.5-
$\Delta_{\min\text{SENS}}$ | -93.2-
$\Delta_{\min\text{SENS}}$ | -76.4 -
$\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 10 RBs | +| 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 | +| 5 | 30 | G-FR1-A1-8 | -94.6-
$\Delta_{\min\text{SENS}}$ | -94.2-
$\Delta_{\min\text{SENS}}$ | -93.9-
$\Delta_{\min\text{SENS}}$ | -76.4 -
$\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 5 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 *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.9.5.1-2a: Medium Range BS in-channel selectivity for $6.0 < f \leq 7.125$ GHz** + +| BS 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 | +|-----------------------------|--------------------------|-------------------------------------------|--------------------------------------|---------------------------------------|-------------------------------------------| +| 20, 30 | 15 | G-FR1-A1-1 | -89.9
$-\Delta_{\min\text{SENS}}$ | -71.4 -
$\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 40, 50 | 15 | G-FR1-A1-4 | -83.5
$-\Delta_{\min\text{SENS}}$ | -65.4 -
$\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 100 RBs | +| 20, 30 | 30 | G-FR1-A1-2 | -90.0
$-\Delta_{\min\text{SENS}}$ | -72.4 -
$\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 10 RBs | +| 40, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 | -83.8
$-\Delta_{\min\text{SENS}}$ | -65.4 -
$\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 50 RBs | +| 20, 30 | 60 | G-FR1-A1-9 | -89.4
$-\Delta_{\min\text{SENS}}$ | -72.4 -
$\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 60 kHz SCS, 5 RBs | +| 40, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 | -83.9
$-\Delta_{\min\text{SENS}}$ | -65.6 -
$\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 60 kHz SCS, 24 RBs | + +**Table 7.9.5.1-3: Local area BS in-channel selectivity for $f \leq 6.0$ GHz** + +| BS 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 | | | +| 5 | 15 | G-FR1-A1-7 | -90.9-
$\Delta_{\min\text{SENS}}$ | -90.5-
$\Delta_{\min\text{SENS}}$ | -90.2-
$\Delta_{\min\text{SENS}}$ | -73.4 -
$\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 10 RBs | +| 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 | +| 5 | 30 | G-FR1-A1-8 | -91.6-
$\Delta_{\min\text{SENS}}$ | -91.2-
$\Delta_{\min\text{SENS}}$ | -90.9-
$\Delta_{\min\text{SENS}}$ | -73.4 -
$\Delta_{\min\text{SENS}}$ | DFT-s- NR signal, 30 kHz SCS, 5 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 *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.9.5.1-3a: Local area BS in-channel selectivity for $6.0 < f \leq 7.125$ GHz** + +| BS 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 | +|-----------------------------|--------------------------|-------------------------------------------|--------------------------------------|---------------------------------------|-------------------------------------------| +| 20, 30 | 15 | G-FR1-A1-1 | -86.9
$-\Delta_{\min\text{SENS}}$ | -68.4 -
$\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 40, 50 | 15 | G-FR1-A1-4 | -80.5
$-\Delta_{\min\text{SENS}}$ | -62.4 -
$\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 100 RBs | +| 20, 30 | 30 | G-FR1-A1-2 | -87.0
$-\Delta_{\min\text{SENS}}$ | -69.4 -
$\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 10 RBs | +| 40, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 | -80.8
$-\Delta_{\min\text{SENS}}$ | -62.4 -
$\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 50 RBs | +| 20, 30 | 60 | G-FR1-A1-9 | -86.4
$-\Delta_{\min\text{SENS}}$ | -69.4 -
$\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 60 kHz SCS, 5 RBs | +| 40, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 | -80.9
$-\Delta_{\min\text{SENS}}$ | -62.6 -
$\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 60 kHz SCS, 24 RBs | + +### 7.9.5.2 BS type 2-O + +For BS 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 tables 7.9.5.2-1, 7.9.5.2-2 and 7.9.5.2-3. + +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 BS type 2-O applicable in the frequency range 24.25 – 43.5 GHz** + +| BS 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 | $\text{EIS}_{\text{REFSENS\_50M}} + 3.4 + \Delta_{\text{FR2\_REFSENS}}$ | $\text{EIS}_{\text{REFSENS\_50M}} + 10 + \Delta_{\text{FR2\_REFSENS}}$ | DFT-s-OFDM NR signal, 60 kHz SCS, 32 RBs | +| 100, 200 | 60 | G-FR2-A1-1 | $\text{EIS}_{\text{REFSENS\_50M}} + 6.4 + \Delta_{\text{FR2\_REFSENS}}$ | $\text{EIS}_{\text{REFSENS\_50M}} + 13 + \Delta_{\text{FR2\_REFSENS}}$ | DFT-s-OFDM NR signal, 60 kHz SCS, 64 RBs | +| 50 | 120 | G-FR2-A1-5 | $\text{EIS}_{\text{REFSENS\_50M}} + 3.4 + \Delta_{\text{FR2\_REFSENS}}$ | $\text{EIS}_{\text{REFSENS\_50M}} + 10 + \Delta_{\text{FR2\_REFSENS}}$ | DFT-s-OFDM NR signal, 120 kHz SCS, 16 RBs | +| 100, 200, 400 | 120 | G-FR2-A1-2 | $\text{EIS}_{\text{REFSENS\_50M}} + 6.4 + \Delta_{\text{FR2\_REFSENS}}$ | $\text{EIS}_{\text{REFSENS\_50M}} + 13 + \Delta_{\text{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 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 2: $\text{EIS}_{\text{REFSENS\_50M}}$ is defined in TS38.104 [2], clause 7.3.3. + +**Table 7.9.5.2-2: OTA in-channel selectivity requirement for BS type 2-O applicable in the frequency range 43.5 – 48.2 GHz** + +| BS 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} + 5.1 + \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} + 8.1 + \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} + 5.1 + \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} + 8.1 + \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 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 interfering signal shall be centred in the BS channel bandwidth of the wanted signal. + +NOTE 2: $EIS_{REFSENS\_50M}$ is defined in TS38.104 [2], clause 7.3.3. + +**Table 7.9.5.2-3: OTA in-channel selectivity requirement for BS type 2-O applicable in the frequency range 52.6 – 71 GHz** + +| BS channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel | Wanted signal mean power (dBm) (Note 2) | Interfering signal mean power (dBm) (Note 2) | Type of interfering signal | +|----------------------------|--------------------------|-------------------------------|---------------------------------------------------------|---------------------------------------------------|------------------------------------------| +| 100, 400 | 120 | G-FR2-A1-2 | $EIS_{REFSENS\_50M} + 3 + 4.0 + \Delta_{FR2\_REFSENS}$ | $EIS_{REFSENS\_50M} + 13 + \Delta_{FR2\_REFSENS}$ | DFT-s-OFDM NR signal, 120 kHz SCS, 32 RB | +| 400 | 480 | G-FR2-A1-8 | $EIS_{REFSENS\_50M} + 9 + 4.0 + \Delta_{FR2\_REFSENS}$ | $EIS_{REFSENS\_50M} + 19 + \Delta_{FR2\_REFSENS}$ | DFT-s-OFDM NR signal, 480 kHz SCS, 32 RB | +| 800, 1600 | 480 | G-FR2-A1-6 | $EIS_{REFSENS\_50M} + 12 + 4.0 + \Delta_{FR2\_REFSENS}$ | $EIS_{REFSENS\_50M} + 22 + \Delta_{FR2\_REFSENS}$ | DFT-s-OFDM NR signal, 480 kHz SCS, 54 RB | +| 400 | 960 | G-FR2-A1-9 | $EIS_{REFSENS\_50M} + 9 + 4.0 + \Delta_{FR2\_REFSENS}$ | $EIS_{REFSENS\_50M} + 19 + \Delta_{FR2\_REFSENS}$ | DFT-s-OFDM NR signal, 960 kHz SCS, 16 RB | +| 800, 1600, 2000 | 960 | G-FR2-A1-7 | $EIS_{REFSENS\_50M} + 12 + 4.0 + \Delta_{FR2\_REFSENS}$ | $EIS_{REFSENS\_50M} + 22 + \Delta_{FR2\_REFSENS}$ | DFT-s-OFDM NR signal, 960 kHz SCS, 27 RB | + +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 in TS 38.104 [2]. The aggregated wanted and interferer signal shall be centred in the BS channel bandwidth of the wanted signal. + +NOTE 2: $EIS_{REFSENS\_50M}$ is defined in TS 38.104 [2], clause 7.3.3. + +## 8 Radiated performance requirements + +### 8.1 General + +#### 8.1.0 Scope and definitions + +Radiated performance requirements specify the ability of the *BS type 1-O* or *BS 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.104 [2] annex A and annex J, respectively. The requirements only apply to those FRCs that are supported by the BS. + +The radiated performance requirements for *BS type 1-O* and for the *BS type 2-O* are limited to two OTA *demodulations branches* as described in clause 8.1.1. Conformance requirements can only be tested for 1 or 2 *demodulation branches* depending on the number of polarizations supported by the BS, with the required SNR applied separately per polarization. + +NOTE 1: BS can support more than 2 *demodulation branches*, however OTA conformance testing can only be performed for 1 or 2 *demodulation branches*. + +Unless stated otherwise, radiated performance requirements apply for a single carrier only. Radiated performance requirements for a BS supporting CA are defined in terms of single carrier requirements. + +For *BS 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 2: *BS 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. + +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 RIB. + +N is the noise energy in a bandwidth corresponding to the transmission bandwidth over the same duration where signal energy exists. + +#### 8.1.1 OTA demodulation branches + +Radiated performance requirements are only specified for up to 2 *demodulation branches*. + +If the *BS type 1-O*, or the *BS 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 *BS type 1-O*, or the *BS 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.2 Applicability rule + +### 8.1.2.0 General + +Unless otherwise stated, for a BS declared to support more than 2 demodulation branches (for *BS type 1-O* and *BS 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.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.7 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.7 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.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.2.1.3 Applicability of requirements for different configurations + +Unless otherwise stated, for *BS 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 *BS 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 *BS 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 *BS type 2-O*, PUSCH requirement tests with transform precoding enabled shall be done for without PT-RS. + +#### 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.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.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, for *BS type 1-O*, 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. + +Unless otherwise stated, for *BS type 2-O*, the tests for UL timing adjustment for scenario Y shall apply only if high speed train is declared to be supported (see D.109 in table 4.6-1). + +#### 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 only for a BS declaring support of 2-step RA type (see D.115 in table 4.6-1) for one (freely selected) subcarrier spacing declared to be supported (see D.7 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.123 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.123 and D.124 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.7 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.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.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.107 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.118 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.111 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.7 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.111 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 type 1-O that declares to support 500 km/h (see D.110 in table 4.6-1) and passes the tests for 500 km/h, can also consider the tests for 350 km/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 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.4.3 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.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.2.4.4 Applicability of requirements for different DM-RS configurations + +Unless otherwise stated, for *BS type 2-O*, FR2 HST PUSCH requirement test shall apply only for the additional DM-RS position declared to be supported (see D.117 in table 4.6-1). If more than one DM-RS configuration is declared to be supported, the test shall be done for the minimum number of DM-RS supported. + +### 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.112 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.7 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 15 KHz and 30 KHz SCS are declared to be supported, the tests shall be done for 30 KHz SCS (see D.7 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.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 defined for 20 MHz channel bandwidth. For 15 KHz subcarrier spacing, the tested RB's are uniformly spaced over the channel bandwidth at RB index {110, 120, ..., 210}. For 30 KHz 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.114 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.112 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.7 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.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 defined for 20 MHz channel bandwidth. For 15 KHz 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 30 KHz 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.113] 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 15 KHz and 30 KHz SCS are declared to be supported, the tests shall be done for 30 KHz SCS (see D.113 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 declared to be supported (see D.7 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.119 and D.120 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 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.121 and D.122 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-O*) (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 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.121 and D.122 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 OTA 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 + +For *BS type 1-O*, the minimum requirement is in TS 38.104 [2], clause 11.2.1.1. + +For *BS type 2-O*, the minimum requirement is in TS 38.104 [2], clause 11.2.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_{\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.1.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.3. +- 2) Align the manufacturer declared coordinate system orientation of the BS with the test system. +- 3) Set the BS 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 the corresponding UL reference measurement channel defined in annex A, and according to additional test parameters listed in table 8.2.1.4.2-1. + +**Table 8.2.1.4.2-1: Test parameters for testing PUSCH** + +| Parameter | | BS type 1-O | BS type 2-O | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------|-------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------| +| 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 | 60 kHz and 120 kHz SCS:
3D1S1U, S=10D:2G:2U
480 kHz
SCS:14D2S4U,S1=12D:2G
0U,S2=0D:6G:8U | +| 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 1: The same requirements are applicable to FDD and TDD with different UL-DL patterns for BS type 1-O, and the same requirements are applicable to TDD with different UL-DL patterns for BS 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 BS receiver is as specified in clause 8.2.1.5.1 and 8.2.1.5.2 for *BS type 1-O* and *BS 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.2.1.4.2-2. + +**Table 8.2.1.4.2-2: AWGN power level at the BS input** + +| BS type | Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|-------------------------|---------------------------|-------------------------|---------------------------------------------------------------------------------------------------------| +| BS type 1-O
(Note 4) | 15 | 5 | $-86.5 - \Delta_{\text{OTAREFSENS}}$ dBm / 4.5 MHz | +| | | 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 | +| BS type 2-O
(Note 5) | 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}$ | +| | | 400 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 24 \text{ dBm} / 380.16 \text{ MHz}$ | +| | 480 | 400 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 24 \text{ dBm} / 380.16 \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. + +NOTE 4: 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. + +NOTE 5: The AWGN power level contains an AWGN offset of 15dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 15dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. + +- 8) For reference channels applicable to the BS, measure the throughput. + +## 8.2.1.5 Test Requirement + +### 8.2.1.5.1 Test requirement for BS type 1-O + +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-1 to table 8.2.1.5.1-18 for 1Tx and for 2Tx two layer spatial multiplexing transmission. + +**Table 8.2.1.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 | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | 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-A9-1 | pos1 | 19.7 | +| 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 | + +**Table 8.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 | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | 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-A9-2 | pos1 | 20.1 | +| 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 | + +**Table 8.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 | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | 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 | +| 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 | + +**Table 8.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 | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | 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-A9-3 | pos1 | 19.9 | +| 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 | + +**Table 8.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 | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | 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 | +| 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 | + +**Table 8.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 | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | 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-A9-4 | pos1 | 20.5 | +| 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 | + +**Table 8.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 | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | 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-A9-5 | pos1 | 21.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 | + +**Table 8.2.1.5.1-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 demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | 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-A9-1 | pos1 | 19.7 | +| 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 | + +**Table 8.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 | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | 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-A9-2 | pos1 | 20.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 | + +**Table 8.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 | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | 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 | +| 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 | + +**Table 8.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 | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | 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-A9-3 | pos1 | 19.8 | +| 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 | + +**Table 8.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 | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | 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 | +| 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 | + +**Table 8.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 | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | 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-A9-4 | pos1 | 20.5 | +| 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 | + +**Table 8.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 | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | 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-A9-5 | pos1 | 21.7 | +| 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 | + +**Table 8.2.1.5.1-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 demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (Annex J) | 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.1-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 demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (Annex J) | 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.1-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 demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (Annex J) | 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.1-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 demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (Annex J) | 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 | + +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.2.1.5.2 Test requirement for BS type 2-O + +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.2-1 to 8.2.1.5.2-10. + +**Table 8.2.1.5.2-1: Test requirements for PUSCH with 70% of maximum throughput, 50 MHz Channel Bandwidth, 60 kHz SCS in FR2-1** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | PT-RS | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|-------|----------| +| 1 | 2 | Normal | TDLA30-300 Low | 70 % | G-FR2-A3-1 | pos0 | No | -1.4 | +| | | | | | G-FR2-A3-13 | pos1 | No | -1.6 | +| | | Normal | TDLA30-300 Low | 70 % | G-FR2-A4-1 | pos0 | Yes | 12.6 | +| | | | | | | | No | 12.1 | +| | | | | | G-FR2-A4-11 | pos1 | Yes | 11.3 | +| | | | | | | | No | 11.3 | +| | | Normal | TDLA30-75 Low | 70 % | G-FR2-A5-1 | pos0 | Yes | 14.3 | +| | | | | | | | No | 13.7 | +| | | | | | G-FR2-A5-6 | pos1 | Yes | 14.0 | +| | | | | | | | No | 13.5 | +| 2 | | Normal | TDLA30-300 Low | 70 % | G-FR2-A3-6 | pos0 | No | 2.3 | +| | | | | | G-FR2-A3-18 | pos1 | No | 2.0 | +| | | Normal | TDLA30-300 Low | 70 % | G-FR2-A7-1 | pos0 | Yes | 16.0 | +| | | | | | | | No | 15.1 | +| | | | | | G-FR2-A7-6 | pos1 | Yes | 14.6 | +| | | | | | | | No | 13.8 | + +**Table 8.2.1.5.2-2: Test requirements for PUSCH with 70% of maximum throughput, 100 MHz Channel Bandwidth, 60 kHz SCS in FR2-1** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | PT-RS | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|-------|----------| +| 1 | 2 | Normal | TDLA30-300 Low | 70 % | G-FR2-A3-2 | pos0 | No | -1.5 | +| | | | | | G-FR2-A3-14 | pos1 | No | -1.8 | +| | | Normal | TDLA30-300 Low | 70 % | G-FR2-A4-2 | pos0 | Yes | 12.8 | +| | | | | | | | No | 11.8 | +| | | | | | G-FR2-A4-12 | pos1 | Yes | 11.8 | +| | | | | | | | No | 11.2 | +| | | Normal | TDLA30-75 Low | 70 % | G-FR2-A5-2 | pos0 | Yes | 14.8 | +| | | | | | | | No | 13.9 | +| | | | | | G-FR2-A5-7 | pos1 | Yes | 14.3 | +| | | | | | | | No | 13.7 | +| 2 | | Normal | TDLA30-300 Low | 70 % | G-FR2-A3-7 | pos0 | No | 2.3 | +| | | | | | G-FR2-A3-19 | pos1 | No | 2.0 | +| | | Normal | TDLA30-300 Low | 70 % | G-FR2-A7-2 | pos0 | Yes | 16.8 | +| | | | | | | | No | 15.7 | +| | | | | | G-FR2-A7-7 | pos1 | Yes | 14.6 | +| | | | | | | | No | 13.9 | + +**Table 8.2.1.5.2-3: Test requirements for PUSCH with 70% of maximum throughput, 50 MHz Channel Bandwidth, 120 kHz SCS in FR2-1** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | PT-RS | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|-------|----------| +| 1 | 2 | Normal | TDLA30-300 Low | 70 % | G-FR2-A3-3 | pos0 | No | -1.2 | +| | | | | | G-FR2-A3-15 | pos1 | No | -1.5 | +| | | Normal | TDLA30-300 Low | 70 % | G-FR2-A4-3 | pos0 | Yes | 12.2 | +| | | | | | | | No | 11.5 | +| | | | | | G-FR2-A4-13 | pos1 | Yes | 11.5 | +| | | | | | | | No | 11.1 | +| | | Normal | TDLA30-75 Low | 70 % | G-FR2-A5-3 | pos0 | Yes | 14.3 | +| | | | | | | | No | 13.7 | +| | | | | | G-FR2-A5-8 | pos1 | Yes | 13.8 | +| | | | | | | | No | 13.6 | +| 2 | | Normal | TDLA30-300 Low | 70 % | G-FR2-A3-8 | pos0 | No | 2.2 | +| | | | | | G-FR2-A3-20 | pos1 | No | 2.1 | +| | | Normal | TDLA30-300 Low | 70 % | G-FR2-A7-3 | pos0 | Yes | 15.0 | +| | | | | | | | No | 14.4 | +| | | | | | G-FR2-A7-8 | Pos1 | Yes | 14.7 | +| | | | | | | | No | 13.9 | + +**Table 8.2.1.5.2-4: Test requirements for PUSCH with 70% of maximum throughput, 100 MHz Channel Bandwidth, 120 kHz SCS in FR2-1** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | PT-RS | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|-------|----------| +| 1 | 2 | Normal | TDLA30-300 Low | 70 % | G-FR2-A3-4 | pos0 | No | -1.8 | +| | | | | | G-FR2-A3-16 | pos1 | No | -1.9 | +| | | Normal | TDLA30-300 Low | 70 % | G-FR2-A4-4 | pos0 | Yes | 12.5 | +| | | | | | | | No | 11.1 | +| | | | | | G-FR2-A4-14 | pos1 | Yes | 11.7 | +| | | | | | | | No | 11.1 | +| | | Normal | TDLA30-75 Low | 70 % | G-FR2-A5-4 | pos0 | Yes | 14.1 | +| | | | | | | | No | 13.5 | +| | | | | | G-FR2-A5-9 | pos1 | Yes | 14.0 | +| | | | | | | | No | 13.4 | +| 2 | | Normal | TDLA30-300 Low | 70 % | G-FR2-A3-9 | pos0 | No | 2.2 | +| | | | | | G-FR2-A3-21 | pos1 | No | 2.0 | +| | | Normal | TDLA30-300 Low | 70 % | G-FR2-A7-4 | pos0 | Yes | 14.7 | +| | | | | | | | No | 14.0 | +| | | | | | G-FR2-A7-9 | pos1 | Yes | 14.3 | +| | | | | | | | No | 13.7 | + +**Table 8.2.1.5.2-5: Test requirements for PUSCH with 70% of maximum throughput, 200 MHz Channel Bandwidth, 120 kHz SCS in FR2-1** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | PT-RS | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|-------|----------| +| 1 | 2 | Normal | TDLA30-300 Low | 70 % | G-FR2-A3-5 | pos0 | No | -1.5 | +| | | | | | G-FR2-A3-17 | pos1 | No | -1.8 | +| | | Normal | TDLA30-300 Low | 70 % | G-FR2-A4-5 | pos0 | Yes | 11.9 | +| | | | | | | | No | 11.5 | +| | | | | | G-FR2-A4-15 | pos1 | Yes | 11.8 | +| | | | | | | | No | 11.3 | +| | | Normal | TDLA30-75 Low | 70 % | G-FR2-A5-5 | pos0 | Yes | 14.7 | +| | | | | | | | No | 14.0 | +| | | | | | G-FR2-A5-10 | pos1 | Yes | 14.3 | +| | | | | | | | No | 13.9 | +| 2 | | Normal | TDLA30-300 Low | 70 % | G-FR2-A3-10 | pos0 | No | 2.2 | +| | | | | | G-FR2-A3-22 | pos1 | No | 1.9 | +| | | Normal | TDLA30-300 Low | 70 % | G-FR2-A7-5 | pos0 | Yes | 14.8 | +| | | | | | | | No | 14.1 | +| | | | | | G-FR2-A7-10 | pos1 | Yes | 14.4 | +| | | | | | | | No | 13.8 | + +**Table 8.2.1.5.2-6: Test requirements for PUSCH with 30% of maximum throughput, 50 MHz channel bandwidth, 60 kHz SCS in FR2-1** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | PT-RS | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|-------|----------| +| 1 | 2 | Normal | TDLA30-300 Low | 30 % | G-FR2-A4-1 | pos0 | Yes | 4.6 | +| | | | | | | | No | 4.1 | +| | | | | | G-FR2-A4-11 | pos1 | Yes | 4.3 | +| | | | | | | | No | 3.7 | + +**Table 8.2.1.5.2-7: Test requirements for PUSCH with 30% of maximum throughput, 50 MHz channel bandwidth, 120 kHz SCS in FR2-1** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | PT-RS | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|-------|----------| +| 1 | 2 | Normal | TDLA30-300 Low | 30 % | G-FR2-A4-3 | pos0 | Yes | 4.6 | +| | | | | | | | No | 4.2 | +| | | | | | G-FR2-A4-13 | pos1 | Yes | 4.3 | +| | | | | | | | No | 3.8 | + +**Table 8.2.1.5.2-8: Test requirements for PUSCH with 70% of maximum throughput, 100 MHz Channel Bandwidth, 120 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | PT-RS | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|-------|----------| +| 1 | 2 | Normal | TDLA30-650 | 70 % | G-FR2-A3B-1 | pos1 | No | 0.4 | +| | | Normal | TDLA30-650 | 70 % | G-FR2-A4-21 | pos1 | Yes | 11.8 | +| | | Normal | TDLD30-200 | 70 % | G-FR2-A5-11 | pos1 | Yes | 13.1 | +| | | Normal | TDLA30-650 | 70 % | G-FR2-A3B-6 | pos1 | No | 4.5 | +| | | Normal | TDLA30-650 | 70 % | G-FR2-A7-11 | pos1 | Yes | 14.2 | + +**Table 8.2.1.5.2-9: Test requirements for PUSCH with 70% of maximum throughput, 400 MHz Channel Bandwidth, 120 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | PT-RS | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|-------|----------| +| 1 | 2 | Normal | TDLA10-650 | 70 % | G-FR2-A3B-2 | pos1 | No | 0.4 | +| | | Normal | TDLA10-650 | 70 % | G-FR2-A4-22 | pos1 | Yes | 11.8 | +| | | Normal | TDLD10-200 | 70 % | G-FR2-A5-12 | pos1 | Yes | 13.2 | +| | | Normal | TDLA10-650 | 70 % | G-FR2-A3B-7 | pos1 | No | 4.6 | +| | | Normal | TDLA10-650 | 70 % | G-FR2-A7-12 | pos1 | Yes | 14.6 | + +**Table 8.2.1.5.2-10: Test requirements for PUSCH with 70% of maximum throughput, 400 MHz Channel Bandwidth, 480 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | PT-RS | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|-------|----------| +| 1 | 2 | Normal | TDLA10-650 | 70 % | G-FR2-A3B-3 | pos1 | No | 0.1 | +| | | Normal | TDLA10-650 | 70 % | G-FR2-A4-23 | pos1 | Yes | 11.4 | +| | | Normal | TDLD10-200 | 70 % | G-FR2-A5-13 | pos1 | Yes | 13.4 | +| 2 | | Normal | TDLA10-650 | 70 % | G-FR2-A3B-8 | pos1 | No | 4.0 | +| | | Normal | TDLA10-650 | 70 % | G-FR2-A7-13 | pos1 | Yes | 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.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 + +For BS type 1-O, the minimum requirement is in TS 38.104 [2], clause 11.2.1.2. + +For BS type 2-O, the minimum requirement is in TS 38.104 [2], clause 11.2.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 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.2.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.3. +- 2) Align the manufacturer declared coordinate system orientation of the BS with the test system. + +- 3) Set the BS 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 the corresponding UL reference measurement channel defined in annex A, and according to additional test parameters listed in table 8.2.2.4.2-1. + +**Table 8.2.2.4.2-1: Test parameters for testing PUSCH** + +| Parameter | | BS type 1-O | BS type 2-O | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------|--------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------| +| 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 | 60 kHz and 120 kHz SCS:
3D1S1U, S=10D:2G:2U
480 kHz
SCS:14D2S4U,S1=12D:2G
0U,S2=0D:6G:8U | +| 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 | 0 | +| | Allocation length | 14 | 10 | +| 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 1: The same requirements are applicable to FDD and TDD with different UL-DL patterns for BS type 1-O, and the same requirements are applicable to TDD with different UL-DL patterns for BS 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 BS receiver is as specified in clause 8.2.2.5.1 and 8.2.2.5.2 for *BS type 1-O* and *BS 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.2.2.4.2-2. + +**Table 8.2.2.4.2-2: AWGN power level at the BS input** + +| BS type | Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|-----------------------------|---------------------------|-------------------------|---------------------------------------------------------------------------------------------------------| +| BS type 1-O (Note 4) | 15 | 5 | $-86.5 - \Delta_{\text{OTAREFSENS}}$ dBm / 4.5 MHz | +| | 30 | 10 | $-83.6 - \Delta_{\text{OTAREFSENS}}$ dBm / 8.64 MHz | +| BS type 2-O (Note 5) | 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}$ | +| | | 100 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 24 \text{ dBm} / 380.16 \text{ MHz}$ | +| | 480 | 400 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 24 \text{ dBm} / 380.16 \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. + +NOTE 4: 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. + +NOTE 5: The AWGN power level contains an AWGN offset of 15dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 15dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. + +8) For reference channels applicable to the BS, measure the throughput. + +## 8.2.2.5 Test Requirement + +### 8.2.2.5.1 Test requirement for *BS type 1-O* + +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-1 to table 8.2.2.5.1-4. + +**Table 8.2.2.5.1-1: Test requirements for PUSCH with 70% of maximum throughput, Type A, 5 MHz channel bandwidth, 15 kHz SCS in FR2-1** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | 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 | + +**Table 8.2.2.5.1-2: Test requirements for PUSCH with 70% of maximum throughput, Type A, 10 MHz channel bandwidth, 30 kHz SCS in FR2-1** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | 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 | + +**Table 8.2.2.5.1-3: Test requirements for PUSCH with 70% of maximum throughput, Type B, 5 MHz channel bandwidth, 15 kHz SCS in FR2-1** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | 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 | + +**Table 8.2.2.5.1-4: Test requirements for PUSCH with 70% of maximum throughput, Type B, 10 MHz channel bandwidth, 30 kHz SCS in FR2-1** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | 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 | + +#### 8.2.2.5.2 Test requirement for BS type 2-O + +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.2-1 to table 8.2.2.5.2-2. + +**Table 8.2.2.5.2-1: Test requirements for PUSCH with 70% of maximum throughput, Type B, 50 MHz channel bandwidth, 60 kHz SCS in FR2-1** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLA30-300 Low | 70 % | G-FR2-A3-11 | Pos0 | -1.2 | +| | | | | | G-FR2-A3-23 | pos1 | -1.3 | + +**Table 8.2.2.5.2-2: Test requirements for PUSCH with 70% of maximum throughput, Type B, 50 MHz channel bandwidth, 120 kHz SCS in FR2-1** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLA30-300 Low | 70 % | G-FR2-A3-12 | Pos0 | -1.2 | +| | | | | | G-FR2-A3-24 | pos1 | -1.3 | + +**Table 8.2.2.5.2-3: Test requirements for PUSCH with 70% of maximum throughput, Type B, 100 MHz channel bandwidth, 120 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLA30-650 Low | 70 % | G-FR2-A3B-4 | pos1 | 0.7 | + +**Table 8.2.2.5.2-4: Test requirements for PUSCH with 70% of maximum throughput, Type B, 400 MHz channel bandwidth, 480 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLA10-650 Low | 70 % | G-FR2-A3B-5 | pos1 | 0.8 | + +## 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 Requirement + +For BS type 1-O, the minimum requirement is in TS 38.104 [2] clause 11.2.1.3. + +For BS type 2-O, the minimum requirement is in TS 38.104 [2] clause 11.2.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 + +Direction to be tested: OTA REFSSENS *receiver target reference direction* (see D.54 in table 4.6-1). + +#### 8.2.3.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.3. +- 2) Align the manufacturer declared coordinate system orientation of the BS with the test system. +- 3) Set the BS 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 to the corresponding UL reference measurement channel defined in annex A, and according to additional test parameters listed in table 8.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.2.3.4.2-1 Test parameters for testing UCI multiplexed on PUSCH** + +| Parameter | | BS type 1-O | BS type 2-O | +|-------------------------------------------|-----------------------------------------------------------|--------------------------------------|----------------------------------------| +| Transform precoding | | Disabled | | +| Default TDD UL-DL pattern (Note 1) | | 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 | {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 for BS type 1-O, and the same requirements are applicable to TDD with different UL-DL patterns for BS 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 BS receiver is as specified in clause 8.2.3.5.1 and 8.2.3.5.2 for BS type 1-O and BS 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.2.3.4.2-2. + +**Table 8.2.3.4.2-2: AWGN power level at the BS input** + +| BS type | Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|----------------------|---------------------------|-------------------------|--------------------------------------------------------------------------------------------------------| +| BS type 1-O (Note 4) | 30 | 10 | $-83.6 - \Delta_{\text{OTAREFSENS}}$ dBm / 8.64 MHz | +| BS type 2-O (Note 5) | 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 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: $\text{EIS}_{\text{REFSENS\_50M}}$ as declared in D.28 in table 4.6-1. + +NOTE 4: 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. + +NOTE 5: The AWGN power level contains an AWGN offset of 15dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 15dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. + +- 8) 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 transmitted, the number of incorrectly decoded CSI part 2 information transmitted during UCI multiplexed on PUSCH transmission. + +## 8.2.3.5 Test Requirement + +### 8.2.3.5.1 Test requirement for BS type 1-O + +The fraction of incorrectly decoded UCI with CSI part 1 according to clause 8.2.3.4.2 shall be less than 0.1 % for the SNR listed in table 8.2.3.5.1-1 and table 8.2.3.5.1-2. The fraction of incorrectly decoded UCI with CSI part 2 according to clause 8.2.3.4.2 shall be less than 1 % for the SNR listed in table 8.2.3.5.1-3 and table 8.2.3.5.1-4. + +**Table 8.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 | Cyclic Prefix | 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 | 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.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 | Cyclic Prefix | 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 | 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.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 | Cyclic Prefix | 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 | 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.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 | Cyclic Prefix | 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 | 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.3.5.2 Test requirement for BS type 2-O + +The fraction of incorrectly decoded UCI with CSI part 1 measured according to clause 8.2.3.4.2 shall be less than 0.1 % for the SNR listed in table 8.2.3.5.2-1 and table 8.2.3.5.2-2. The fraction of incorrectly decoded UCI with CSI part 2 measured according to clause 8.2.3.4.2 shall be less than 1 % for the SNR listed in table 8.2.3.5.2-3 and table 8.2.3.5.2-4. + +**Table 8.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 | Cyclic Prefix | 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 | Normal | TDLA30-300 Low | 7 (5, 2) | pos0 | G-FR2-A4-3 | 7.8 | +| | 2 | Normal | TDLA30-300 Low | 40 (20,20) | pos0 | G-FR2-A4-3 | 6.4 | +| | 2 | Normal | TDLA30-300 Low | 7 (5, 2) | pos1 | G-FR2-A4-13 | 8.4 | +| | 2 | Normal | TDLA30-300 Low | 40 (20,20) | pos1 | G-FR2-A4-13 | 6.5 | + +**Table 8.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 | Cyclic Prefix | 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 | Normal | TDLA30-300 Low | 7 (5, 2) | pos0 | G-FR2-A4-3 | 7.7 | +| | 2 | Normal | TDLA30-300 Low | 40 (20,20) | pos0 | G-FR2-A4-3 | 6.4 | +| | 2 | Normal | TDLA30-300 Low | 7 (5, 2) | pos1 | G-FR2-A4-13 | 7.9 | +| | 2 | Normal | TDLA30-300 Low | 40 (20,20) | pos1 | G-FR2-A4-13 | 6.1 | + +**Table 8.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 | Cyclic Prefix | 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 | Normal | TDLA30-300 Low | 7 (5, 2) | pos0 | G-FR2-A4-3 | 1.7 | +| | 2 | Normal | TDLA30-300 Low | 40 (20,20) | pos0 | G-FR2-A4-3 | 4.6 | +| | 2 | Normal | TDLA30-300 Low | 7 (5, 2) | pos1 | G-FR2-A4-13 | 1.9 | +| | 2 | Normal | TDLA30-300 Low | 40 (20,20) | pos1 | G-FR2-A4-13 | 4.6 | + +**Table 8.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 | Cyclic Prefix | 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 | Normal | TDLA30-300 Low | 7 (5, 2) | pos0 | G-FR2-A4-3 | 1.7 | +| | 2 | Normal | TDLA30-300 Low | 40 (20,20) | pos0 | G-FR2-A4-3 | 4.5 | +| | 2 | Normal | TDLA30-300 Low | 7 (5, 2) | pos1 | G-FR2-A4-13 | 1.8 | +| | 2 | Normal | TDLA30-300 Low | 40 (20,20) | pos1 | G-FR2-A4-13 | 4.3 | + +## 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 and only apply for FR2-1 below 30GHz. + +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 + +For BS type 1-O, the minimum requirement is in TS 38.104 [2] clause 11.2.1.4. + +For BS type 2-O, the minimum requirement is in TS 38.104 [2] clause 11.2.2.7. + +### 8.2.4.3 Test Purpose + +The test shall verify the receiver's ability to achieve throughput under high speed train and multipath fading propagation 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; 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.4.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.3. +- 2) Align the manufacturer declared coordinate system orientation of the BS with the test system. +- 3) Set the BS 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 the corresponding UL reference measurement channel defined in annex A, and according to additional test parameters listed in table 8.2.4.4.2-1 for BS type 1-O or table 8.2.4.4.2-1A for BS type 2-O. + +**Table 8.2.4.4.2-1: Test parameters for testing PUSCH under HST conditions (BS type 1-O)** + +| 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 | +| | First DM-RS position | pos 2 or pos 3
(NOTE 2) | +| | 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$ | +| Time domain resource assignment | PUSCH mapping type | A | +| | 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 pattern. | | | +| Note 2: Either pos2 or pos3 may be selected for conformance testing. | | | + +**Table 8.2.4.4.2-1A: Test parameters for testing PUSCH under HST conditions (BS type 2-O)** + +| Parameter | | Value | +|-------------------------------------------|-------------------------------------------|-------------------------------------| +| Transform precoding | | Disabled | +| Default TDD UL-DL pattern (NOTE 1) | | 120 KHz 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 symbols | pos0, pos1, pos2
(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(s) | {0} | +| | DM-RS sequence generation | NID=0, nSCID =0 | +| Time domain resource | PUSCH mapping type | B | +| | Start symbol index | 0 | +| | Allocation length | 10 | +| Frequency domain resource | RB assignment | Full applicable test bandwidth | +| | Frequency hopping | Disabled | +| Code block group based PUSCH transmission | | Disabled | +| PT-RS configuration | Frequency density (KPT-RS) | 2 | +| | Time density (LPT-RS) | 1 | + +NOTE 1: The same requirements are applicable to TDD with different UL-DL patterns + +NOTE 2: Either pos0, pos1 or pos2 may be selected for conformance testing. + +The channel emulators shall be configured according to the corresponding channel model defined in annex J. Unless stated otherwise, the MIMO correlation matrices for the gNB are defined in annex J for low correlation. + +- Adjust the test signal mean power so the calibrated radiated SNR value at the BS receiver is as specified in clause 8.2.4.5 (BS type 1-O) or clause 8.2.4.6 (BS type 2-O) 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.2.4.4.2-2. + +**Table 8.2.4.4.2-2: AWGN power level at the BS input** + +| BS type | Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|--------------|---------------------------|-------------------------|---------------------------------------------------------------------------------------------------------| +| 1-O (NOTE 2) | 15 | 5 | $-86.5 - \Delta_{\text{OTAREFSENS}}$ dBm / 4.5MHz | +| | | 10 | $-83.3 - \Delta_{\text{OTAREFSENS}}$ dBm / 9.36 MHz | +| | 30 | 10 | $-83.6 - \Delta_{\text{OTAREFSENS}}$ dBm / 8.64MHz | +| | | 40 | $-77.2 - \Delta_{\text{OTAREFSENS}}$ dBm / 38.16 MHz | +| 2-O (NOTE 3) | 120 | 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: 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 + +NOTE 3: The AWGN power level contains an AWGN offset of 15dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 15dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. + +- For reference channels applicable to the BS, measure the throughput. + +### 8.2.4.5 Test Requirement for BS Type 1-O + +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 J for low correlation. + +**Table 8.2.4.5-1: Test requirements for PUSCH, Type A, 10 MHz channel bandwidth, 15 kHz SCS, 350 km/h** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions (Annex J) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------|----------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 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 | + +**Table 8.2.4.5-2: Test requirements for PUSCH, Type A, 40 MHz channel bandwidth, 30 kHz SCS, 350 km/h** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions (Annex J) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------|----------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 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 | + +**Table 8.2.4.5-3: Test requirements for PUSCH, Type A, 10 MHz channel bandwidth, 15 kHz SCS, 500 km/h** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions (Annex J) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------|----------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 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 | + +**Table 8.2.4.5-4: Test requirements for PUSCH, Type A, 40 MHz channel bandwidth, 30 kHz SCS, 500 km/h** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions (Annex J) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------|----------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 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 | + +**Table 8.2.4.5-5: Test requirements for PUSCH, Type A, 5 MHz channel bandwidth, 15 kHz SCS, 350 km/h** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions (Annex J) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------|----------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 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 | + +**Table 8.2.4.5-6: Test requirements for PUSCH, Type A, 10 MHz channel bandwidth, 30 kHz SCS, 350 km/h** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions (Annex J) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------|----------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 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 | + +**Table 8.2.4.5-7: Test requirements for PUSCH, Type A, 5 MHz channel bandwidth, 15 kHz SCS, 500 km/h** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions (Annex J) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------|----------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 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 | + +**Table 8.2.4.5-8: Test requirements for PUSCH, Type A, 10 MHz channel bandwidth, 30 kHz SCS, 500 km/h** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions (Annex J) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------|----------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 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 | + +**Table 8.2.4.5-9: Test requirements for PUSCH, Type A, 5 MHz channel bandwidth, 15 kHz SCS, multi-path fading channel** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions (Annex J) | Frequency offset (Hz) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------|----------------------------------|-----------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLC300-600 | 0 | 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** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions (Annex J) | Frequency offset (Hz) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------|----------------------------------|-----------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLC300-1200 | 0 | 70 % | G-FR1-A3-34A | pos2 | -1.4 | + +## 8.2.4.6 Test Requirement for BS Type 2-O + +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.6-1 to 8.2.4.6-2. Unless stated otherwise, the MIMO correlation matrices for the gNB are defined in annex J for low correlation. + +**Table 8.2.4.6-1: Test requirements for PUSCH, Type B, 50 MHz channel bandwidth, 120 kHz SCS, 350 km/h** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions (Annex J) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------|----------------------------------|--------------------------------|-----------------------------|---------------------------|----------| +| 1 | 2 | Normal | Scenario 4-BI-NR350, FR2 | 70 % | G-FR2-A10-1 | pos0 | 13.5 | +| | | Normal | Scenario 4-BI-NR350, FR2 | 70 % | G-FR2-A10-3,
G-FR2-A10-5 | pos1,
pos2 | 13.1 | + +**Table 8.2.4.6-2: Test requirements for PUSCH, Type B, 200 MHz channel bandwidth, 120 kHz SCS, 350 km/h** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions (Annex J) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------|----------------------------------|--------------------------------|-----------------------------|---------------------------|----------| +| 1 | 2 | Normal | Scenario 4-BI-NR350, FR2 | 70 % | G-FR2-A10-2 | pos0 | 13.4 | +| | | Normal | Scenario 4-BI-NR350, FR2 | 70 % | G-FR2-A10-4,
G-FR2-A10-6 | pos1,
pos2 | 12.9 | + +## 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 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 J.4 are optional. The performance requirements for UL timing adjustment scenario Y in FR2 apply only to FR2-1 below 30GHz. + +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 Tables A.4-2B, A.10-4, A.10-5, and A.10-6 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 12.2.1.5 and 12.2.2. 8. + +### 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: $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.5.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.3. +- 2) Align the manufacturer declared coordinate system orientation of the BS with the test system. +- 3) Set the BS 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 the corresponding UL reference measurement channel defined in annex A, and according to additional test parameters listed in table 8.2.5.4.2-1 and table 8.2.5.4.2-1a. + +**Table 8.2.5.4.2-1 Test parameters for testing UL timing adjustment for BS type 1-O** + +| Parameter | | Value | +|--------------------------------------|----------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Transform precoding | | Disabled | +| Uplink-downlink allocation for TDD | | 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 | {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/15 KHz: 12 RB for each UE
10MHz CBW/15 KHz SCS: 25 RB for each UE
10MHz CBW/30 KHz: 12 RB for each UE
40MHz CBW/30 KHz SCS: 50 RB for each UE | +| | Starting PRB index | Moving UE: 0
Stationary UE: 12 for 5MHz CBW/15 KHz SCS, 25 for 10 MHz CBW/15 KHz SCS, 12 for 10MHz CBW/30 KHz SCS and 50 for 40 MHz CBW/30 KHz SCS | +| | Frequency hopping | Disabled | +| SRS resource allocation | Slots in which sounding RS is transmitted (Note 1) | For FDD: slot #1 in radio frames
For TDD:
- last symbol in slot #3 in radio frames for 15 KHz
- last symbol in slot #7 in radio frames for 30 KHz | +| | 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 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. + +**Table 8.2.5.4.2-1a Test parameters for testing UL timing adjustment for BS type 2-O** + +| Parameter | | Value | +|--------------------------------------|----------------------------------------------------|--------------------------------------------------------------------------------------------------------| +| Transform precoding | | Disabled | +| Uplink-downlink allocation for TDD | | 120 kHz SCS:
3D1S1U, S=10D:2G:2U | +| Channel bandwidth | | 120 kHz SCS: 50MHz, 200 MHz | +| 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 | +| | DM-RS position ( $l_0$ ) | 2 | +| | Additional DM-RS position | pos0, pos1, 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} | +| Time domain resource assignment | DM-RS sequence generation | $N_{ID}^0=0, n_{SCID}=0$ for moving UE
$N_{ID}^0=1, n_{SCID}=1$ for stationary UE | +| | PUSCH mapping type | B | +| | Allocation length | 10 | +| Frequency domain resource assignment | RB assignment | 50 MHz CBW/120 KHz SCS: 16 RB for each UE
200MHz CBW/120 KHz SCS: 66 RB for each UE | +| | Starting PRB index | Moving UE: 0
Stationary UE: 16 for 50MHz CBW, 66 for 200MHz CBW for SCS 120 KHz | +| | Frequency hopping | Disabled | +| SRS resource allocation | Slots in which sounding RS is transmitted (Note 1) | For TDD:
- last symbol in slot #3 in radio frames for 120 KHz | +| | SRS resource allocation | 120 kHz SCS:
- $C_{SRS} = 9, B_{SRS} = 0$ , for 32 RB
- $C_{SRS} = 33, B_{SRS} = 0$ , for 132 RB | + +NOTE 1. The transmission of SRS is optional. And the transmission comb and SRS periodic are configured as $K_{TC} = 2$ , and $T_{SRS} = 80$ respectively. + +The multipath fading emulators shall be configured according to the corresponding channel model defined in annex J. Unless stated otherwise, the MIMO correlation matrices for the gNB are defined in annex J for low correlation. + +- Adjust the test signal mean power so the calibrated radiated SNR value at the BS receiver is as specified in clause 8.2.5.5 for high speed train and clause 8.2.5.6 for normal mode 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.2.5.4.2-2. + +**Table 8.2.5.4.2-2: AWGN power level at the BS input** + +| BS type | Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|--------------|---------------------------|-------------------------|-------------------------------------------------------------------------------------------------------| +| 1-O (NOTE 2) | 15 | 5 | $-86.5\text{dBm} - \Delta_{\text{OTAREFSENS}}\text{ dBm} / 4.5\text{MHz}$ | +| | | 10 | $-83.3 - \Delta_{\text{OTAREFSENS}}\text{ dBm} / 9.36\text{ MHz}$ | +| | 30 | 10 | $-83.6\text{ dBm} - \Delta_{\text{OTAREFSENS}}\text{ dBm} / 8.64\text{MHz}$ | +| | | 40 | $-77.2 - \Delta_{\text{OTAREFSENS}}\text{ dBm} / 38.16\text{ MHz}$ | +| 2-O (NOTE 3) | 120 | 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: 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. + +NOTE 3: The AWGN power level contains an AWGN offset of 15dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 15dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. + +8) For reference channels applicable to the BS, measure the throughput. + +### 8.2.5.5 Test Requirement for High Speed Train for BS type 1-O + +The throughput shall be $\geq 70\%$ of the maximum throughput of the reference measurement channel as specified in annex A measured for the moving UE according to clause 8.2.5.4.2 shall not be below the limits for the SNR levels specified 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 demodulation branches | Cyclic prefix | Channel Bandwidth [MHz] | SCS [kHz] | Moving propagation conditions and correlation matrix (Annex J) | 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 demodulation branches | Cyclic prefix | Channel Bandwidth [MHz] | SCS [kHz] | Moving propagation conditions and correlation matrix (Annex J) | 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.5a Test Requirement for High Speed Train for BS type 2-O + +The throughput shall be $\geq 70\%$ of the maximum throughput of the reference measurement channel as specified in annex A measured for the moving UE according to clause 8.2.5.4.2 shall not be below the limits for the SNR levels specified in table 8.2.5.5a-1 for mapping type B. + +**Table 8.2.5.5a-1 Minimum requirements for UL timing adjustment with mapping type B for high speed train** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Channel Bandwidth [MHz] | SCS [kHz] | Moving propagation conditions and correlation matrix (Annex J) | FRC (Annex A) | SNR [dB] | +|-----------------------|---------------------------------|---------------|-------------------------|-----------|----------------------------------------------------------------|----------------------------|----------| +| 1 | 2 | Normal | 50 | 120 | Scenario Y | G-FR2-A10-7 | 9.7 | +| | | | | | Scenario Y | G-FR2-A10-9, G-FR2-A10-11 | 9.4 | +| | | | 200 | 120 | Scenario Y | G-FR2-A10-8 | 9.6 | +| | | | | | Scenario Y | G-FR2-A10-10, G-FR2-A20-12 | 9.5 | + +### 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 measured for the moving UE according to clause 8.2.5.4.2 shall not be below the limits for the SNR levels specified 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 for normal mode** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Channel Bandwidth [MHz] | SCS [kHz] | Moving propagation conditions and correlation matrix (Annex J) | 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 for normal mode** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Channel Bandwidth [MHz] | SCS [kHz] | Moving propagation conditions and correlation matrix (Annex J) | 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. + +### 8.2.6.2 Minimum Requirement + +For BS type 1-O, the minimum requirement is in TS 38.104 [2], clause 11.2.1.6. + +For BS type 2-O, no requirement and no test are defined. + +### 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: 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.6.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.3. +- 2) Align the manufacturer declared coordinate system orientation of the BS with the test system. +- 3) Set the BS 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 the corresponding UL reference measurement channel defined in annex A, and according to additional test parameters listed in table 8.2.5.4.2-1. + +**Table 8.2.6.4.2-1: 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
RV sequence | +| DM-RS | DM-RS configuration type
DM-RS duration
Additional DM-RS position
Number of DM-RS CDM group(s) without data
Ratio of PUSCH EPRE to DM-RS EPRE
DM-RS port(s)
DM-RS sequence generation | +| Time domain resource assignment | PUSCH mapping type
Start symbol
Allocation length | +| Frequency domain resource assignment | RB assignment
Frequency hopping | +| Code block group based PUSCH transmission | Disabled | +| Note 1: The same requirements are applicable to FDD and TDD with different UL-DL patterns. | | + +No multipath fading channel is included in the test. + +- 7) Adjust the test signal mean power so the calibrated radiated SNR value at the BS receiver is as specified in clause 8.2.6.5 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.2.6.4.2-2. + +**Table 8.2.6.4.2-2: AWGN power level at the BS input** + +| BS type | Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|--------------|---------------------------|-------------------------|------------------------------------------------------| +| 1-O (NOTE 2) | 15 | 10 | $-83.3 - \Delta_{\text{OTAREFSENS}}$ dBm / 9.36 MHz | +| | 30 | 40 | $-77.2 - \Delta_{\text{OTAREFSENS}}$ dBm / 38.16 MHz | + +NOTE 1: $\Delta_{\text{OTAREFSENS}}$ as declared in D.53 in table 4.6-1 and clause 7.1. +NOTE 2: 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. + +- 8) For reference channels applicable to the BS, measure the BLER. BLER is evaluated based on the test methodology described in Annex I. + +## 8.2.6.5 Test requirement + +### 8.2.6.5.1 Test requirement for BS type 1-O + +The throughput measured 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-1 to table 8.2.6.5.1-8 for 0.001% BLER if declared to be supported. + +**Table 8.2.6.5.1-1: Test requirements for PUSCH with 0.001% BLER, Type A, 5 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | 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.1-2: Test requirements for PUSCH with 0.001% BLER, Type A, 10 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | 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.1-3: Test requirements for PUSCH with 0.001% BLER, Type A, 10 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | 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.1-4: Test requirements for PUSCH with 0.001% BLER, Type A, 40 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | 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.1-5: Test requirements for PUSCH with 0.001% BLER, Type B, 5 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | 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.1-6: Test requirements for PUSCH with 0.001% BLER, Type B, 10 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | 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.1-7: Test requirements for PUSCH with 0.001% BLER, Type B, 10 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | 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.1-8: Test requirements for PUSCH with 0.001% BLER, Type B, 40 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | 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 | + +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.2.7 Performance requirements for PUSCH repetition Type A + +### 8.2.7.1 Definition and applicability + +The performance requirement of PUSCH repetition Type A is determined by block error probability (BLER). The performance is measured by the required SNR at block error probability of PUSCH data not exceeding 1 %. 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 + +For BS type 1-O, the minimum requirement is in TS 38.104 [2], clause 11.2.1.7. + +For BS type 2-O, the minimum requirement is in TS 38.104 [2], clause 11.2.2.7. + +### 8.2.7.3 Test purpose + +The test shall verify the receiver's ability to achieve target block error probability of 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. + +Direction to be tested: OTA REFSENS *receiver target reference direction* (see D.54 in table 4.6-1). + +#### 8.2.7.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.3. +- 2) Align the manufacturer declared coordinate system orientation of the BS with the test system. +- 3) Set the BS 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 the corresponding UL reference measurement channel defined in annex A, and according to additional test parameters listed in table 8.2.7.4.2-1. + +**Table 8.2.7.4.2-1: Test parameters for testing PUSCH repetition Type A** + +| Parameter | | BS type 1-O | BS type 2-O | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------|---------------------------------------------------------------------------|------------------------------------------------| +| 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 | 60 kHz and 120 kHz SCS:
3D1S1U, S=10D:2G:2U | +| 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(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 | +| | PUSCH aggregation factor | 15 KHz SCS: n2 for FDD and n8 for TDD
30 KHz SCS: n2 (Note 3) (Note 5) | n8 (Note 4) | +| Frequency domain resource assignment | RB assignment | Full applicable test bandwidth | | +| | Frequency hopping | Disabled | | +| Code block group based PUSCH transmission | | Disabled | Disabled | +| PTRS configuration | Frequency density ( $K_{PT-RS}$ ) | N.A. | Disabled | +| | Time density ( $L_{PT-RS}$ ) | N.A. | Disabled | +| Note 1: The same requirements are applicable to TDD with different UL-DL patterns and different aggregation factor configurations under assumption that two effective transmissions of the transport block are generated for BS type 2-O.
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.
Note 4: 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.
Note 5: PUSCH aggregation factor for 15 KHz SCS: The requirements for PUSCH with aggregation for 15 KHz can be tested either by configuring n8 and the DDDSU TDD pattern or by configuring FDD with aggregation level n2. | | | | + +- 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 BS receiver is as specified in clause 8.2.7.5.1 and clause 8.2.7.5.2 for *BS type 1-O* and *BS 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.2.7.4.2-2. + +**Table 8.2.7.4.2-2: AWGN power level at the BS input** + +| BS type | Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|-------------------------|---------------------------|-------------------------|--------------------------------------------------------------------------------------------------------| +| BS type 1-O
(Note 4) | 15 | 5 | $-86.5 - \Delta_{\text{OTAREFSENS}}$ dBm / 4.5 MHz | +| | | 10 | $-83.3 - \Delta_{\text{OTAREFSENS}}$ dBm / 9.36 MHz | +| | 30 | 10 | $-83.6 - \Delta_{\text{OTAREFSENS}}$ dBm / 8.64 MHz | +| | | 40 | $-77.2 - \Delta_{\text{OTAREFSENS}}$ dBm / 38.16 MHz | +| BS type 2-O
(Note 5) | 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}$ | + +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. + +NOTE 4: 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. + +NOTE 5: The AWGN power level contains an AWGN offset of 15dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 15dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. + +8) For reference channels applicable to the BS, measure the throughput. + +## 8.2.7.5 Test Requirement + +### 8.2.7.5.1 Test requirement for BS type 1-O + +The block error probability (BLER) measured according to clause 8.2.7.4.2 shall not exceed 1% for the SNR levels specified in table 8.2.7.5.1-1 to table 8.2.7.5.1-8 for ITx. + +**Table 8.2.7.5.1-1: Test requirements for PUSCH, Type A, 5 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | 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.1-2: Test requirements for PUSCH, Type A, 10 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | 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.1-3: Test requirements for PUSCH, Type A, 10 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | 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.1-4: Test requirements for PUSCH, Type A, 40 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | 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.1-5: Test requirements for PUSCH, Type B, 5 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | 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.1-6: Test requirements for PUSCH, Type B, 10 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | 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.1-7: Test requirements for PUSCH, Type B, 10 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | 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: Calculate the target BLER after all HARQ transmission(s) for one TB. | | | | | | | | + +**Table 8.2.7.5.1-8: Test requirements for PUSCH, Type B, 40 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | 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: Calculate the target BLER after all HARQ transmission(s) for one TB. | | | | | | | | + +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.2.7.5.2 Test requirement for BS type 2-O + +The block error probability (BLER) measured according to clause 8.2.7.4.2 shall not exceed 1% for the SNR levels specified in table 8.2.7.5.2-1 to 8.2.7.5.2-7. + +**Table 8.2.7.5.2-1: Test requirements for PUSCH with 1% BLER, 50 MHz Channel Bandwidth, 60 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | BLER | FRC (annex A) | Additional DM-RS position | PT-RS | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------|---------------|---------------------------|-------|----------| +| 1 | 2 | Normal | TDLA30-300 Low | 1 % | G-FR2-A3A-5 | pos1 | No | -11.3 | + +**Table 8.2.7.5.2-2: Test requirements for PUSCH with 1% BLER, 100 MHz Channel Bandwidth, 60 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | BLER | FRC (annex A) | Additional DM-RS position | PT-RS | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------|---------------|---------------------------|-------|----------| +| 1 | 2 | Normal | TDLA30-300 Low | 1 % | G-FR2-A3A-6 | pos1 | No | -11.6 | + +**Table 8.2.7.5.2-3: Test requirements for PUSCH with 1% BLER, 50 MHz Channel Bandwidth, 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | BLER | FRC (annex A) | Additional DM-RS position | PT-RS | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------|---------------|---------------------------|-------|----------| +| 1 | 2 | Normal | TDLA30-300 Low | 1 % | G-FR2-A3A-7 | pos1 | No | -10.6 | + +**Table 8.2.7.5.2-4: Test requirements for PUSCH with 1% BLER, 100 MHz Channel Bandwidth, 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | BLER | FRC (annex A) | Additional DM-RS position | PT-RS | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------|---------------|---------------------------|-------|----------| +| 1 | 2 | Normal | TDLA30-300 Low | 1 % | G-FR2-A3A-8 | pos1 | No | -11.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.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 with non-slot transmission 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 + +For BS type 1-O, the minimum requirement is in TS 38.104 [2], clause 11.2.1.8. + +For BS type 2-O, the minimum requirement is in TS 38.104 [2], clause 11.2.2.5. + +### 8.2.8.3 Test purpose + +The test shall verify the receiver's ability to achieve throughput under scenarios with non-slot PUSCH Type B transmission 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. + +Direction to be tested: OTA REFSENS *receiver target reference direction* (see D.54 in table 4.6-1). + +#### 8.2.8.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.3. +- 2) Align the manufacturer declared coordinate system orientation of the BS with the test system. +- 3) Set the BS 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 the corresponding UL reference measurement channel defined in annex A, and according to additional test parameters listed in table 8.2.8.4.2-1. + +**Table 8.2.8.4.2-1: Test parameters for testing PUSCH** + +| Parameter | | BS type 1-O | BS type 2-O | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------|-------------------------------------------------------------------------|------------------------------------------------| +| 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 | 60 kHz and 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 | pos0 | pos0 | +| | 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 | B | B | +| | Start symbol | 0 | 0 | +| | Allocation length | 2 | 4 | +| 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. | Disabled | +| | Time density ( $L_{PT-RS}$ ) | N.A. | Disabled | +| Note 1: The same requirements are applicable to FDD and TDD with different UL-DL patterns for BS type 1-O, and the same requirements are applicable to TDD with different UL-DL patterns for BS 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 BS receiver is as specified in clause 8.2.8.5.1 and 8.2.8.5.2 for *BS type 1-O* and *BS 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.2.8.4.2-2. + +**Table 8.2.8.4.2-2: AWGN power level at the BS input** + +| BS type | Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|-------------------------|---------------------------|-------------------------|--------------------------------------------------------------------------------------------------------| +| BS type 1-O
(Note 4) | 15 | 5 | $-86.5 - \Delta_{\text{OTAREFSENS}}$ dBm / 4.5 MHz | +| | | 10 | $-83.3 - \Delta_{\text{OTAREFSENS}}$ dBm / 9.36 MHz | +| | 30 | 10 | $-83.6 - \Delta_{\text{OTAREFSENS}}$ dBm / 8.64 MHz | +| | | 40 | $-77.2 - \Delta_{\text{OTAREFSENS}}$ dBm / 38.16 MHz | +| BS type 2-O
(Note 5) | 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}$ | + +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. + +NOTE 4: 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. + +NOTE 5: The AWGN power level contains an AWGN offset of 15dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 15dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. + +8) For reference channels applicable to the BS, measure the throughput. + +## 8.2.8.5 Test Requirement + +### 8.2.8.5.1 Test requirement for BS type 1-O + +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-1 to table 8.2.8.5.1-4 for ITx. + +**Table 8.2.8.5.1-1: Test requirements for PUSCH, Type B, 5 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLC300-100 Low | 70% | G-FR1-A3B-1 | pos0 | 1.1 | + +**Table 8.2.8.5.1-2: Test requirements for PUSCH, Type B, 10 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLC300-100 Low | 70% | G-FR1-A3B-2 | pos0 | 0.9 | + +**Table 8.2.8.5.1-3: Test requirements for PUSCH, Type B, 10 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLC300-100 Low | 70% | G-FR1-A3B-3 | pos0 | 0.9 | + +**Table 8.2.8.5.1-4: Test requirements for PUSCH, Type B, 40 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLC300-100 Low | 70% | G-FR1-A3B-4 | pos0 | 0.6 | + +NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +#### 8.2.8.5.2 Test requirement for BS type 2-O + +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.2-1 to 8.2.8.5.2-4 for 1Tx. + +**Table 8.2.8.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 | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | PT-RS | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|-------|----------| +| 1 | 2 | Normal | TDLA30-300 Low | 70 % | G-FR2-A3A-1 | pos0 | No | -3.8 | + +**Table 8.2.8.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 | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | PT-RS | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|-------|----------| +| 1 | 2 | Normal | TDLA30-300 Low | 70 % | G-FR2-A3A-2 | pos0 | No | -4.4 | + +**Table 8.2.8.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 | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | PT-RS | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|-------|----------| +| 1 | 2 | Normal | TDLA30-300 Low | 70 % | G-FR2-A3A-3 | pos0 | No | -3.5 | + +**Table 8.2.8.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 | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | PT-RS | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|-------|----------| +| 1 | 2 | Normal | TDLA30-300 Low | 70 % | G-FR2-A3A-4 | pos0 | No | -4.5 | + +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.2.9 Performance requirements for MsgA PUSCH + +### 8.2.9.1 Definition and applicability + +The performance requirement of MsgA PUSCH is determined by a maximum allowed block error rate of Msg A received by BS at given SNR for FRCs listed in annex A. The performance requirements assume that the precedent preamble of MsgA is correctly detection. 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 + +For *BS type 1-O*, the minimum requirement is in TS 38.104 [2] clause 11.2.1.9. + +For *BS type 2-O*, the minimum requirement is in TS 38.104 [2] clause 11.2.1.4. + +### 8.2.9.3 Test Purpose + +The test shall verify the receiver's ability to detect MsgA PUSCH under multipath fading propagation conditions 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_{\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.9.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.3. +- 2) Align the manufacturer declared coordinate system orientation of the BS with the test system. +- 3) Set the BS 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 the corresponding UL reference measurement channel defined in annex A, and according to additional test parameters listed in table 8.2.9.4.2-1. + +**Table 8.2.9.4.2-1: Test parameters for testing MsgA PUSCH for 2-step RA type** + +| Parameter | | BS type 1-O | BS type 2-O | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------|-------------------------------------------------------------------------|-------------------------------------------------|--|--| +| Preamble format | | Free choice | | | | +| Transform precoding | | Disable | | | | +| Power offset between preamble and MsgA(Note 1) | | Free choice | | | | +| Default TDD UL-DL pattern(Note 2) | | 15 kHz SCS:
3D1S1U, S=10D:2G:2U
30 kHz SCS:
7D1S2U, S=6D:4G:4U | 60 kHz and 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 | Pos 1 or Pos 2 (Note 3) | 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 | 0 | | | +| | Allocation length | 14 | 10 | | | +| Frequency domain resource assignment | RB assignment | 2 | 2 | | | +| | Starting PRB index | 0 | 0 | | | +| | Frequency hopping | Disabled | | | | +| Code block group based PUSCH transmission | | Disabled | | | | +| PT-RS | | Not configured | | | | +| Timing offset (TO) Cycling (us) | | 15 kHz SCS: 0:0.2:3.8
30 kHz SCS: 0:0.1:2 | 60 kHz SCS: 0:0.1:0.6
120 kHz SCS: 0:0.1:0.5 | | | +| | | | | | | +| NOTE1: The power ratio between preamble and msgA is set to be sufficient to achieve 100% preamble detection. The SNR for the requirement is defined on the msgA PUSCH | | | | | | +| NOTE 2: The same requirements are applicable to FDD and TDD with different UL-DL patterns | | | | | | +| NOTE 3: 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. | | | | | | + +- 6) The channel emulators shall be configured according to the corresponding channel model defined in annex J. Unless stated otherwise, the MIMO correlation matrices for the gNB are defined in annex J.2.3 for low correlation. +- 7) Adjust the test signal mean power so the calibrated radiated SNR value at the BS receiver is as specified in clause 8.2.9.5.1 and 8.2.9.5.2 for BS type 1-O and BS 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.2.9.4.2-2. + +**Table 8.2.9.4.2-2: AWGN power level at the BS input** + +| BS type | Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|-------------------------|---------------------------|-------------------------|--------------------------------------------------------------------------------------------------------| +| BS type 1-O
(Note 4) | 15 | 10 | $-83.3 - \Delta_{\text{OTAREFSENS}}$ dBm / 9.36 MHz | +| | 30 | 40 | $-77.2 - \Delta_{\text{OTAREFSENS}}$ dBm / 38.16 MHz | +| BS type 2-O
(Note 5) | 60 | 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}$ | + +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. + +NOTE 4: 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. + +NOTE 5: The AWGN power level contains an AWGN offset of 15dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 15dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. + +- 8) The test signal generator sends a MsgA including a preamble and PUSCH signal and the receiver tries to detect the MsgA signal contents. The MsgA signal is sent with timing offset as described below. The following statistics are collected: the number of incorrectly decoded MsgA PUSCH transmitted during the MsgA signal transmission. + +The timing offset base value for MsgA signal with 15 kHz SCS is set to 0. This offset is increased within the loop, by adding in each step a value of 0.2 us for *BS type 1-O* with 15 kHz SCS, until the end of the tested range, which is 3.8 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. + +![Figure 8.2.9.4.2-1: Timing offset scheme for MsgA transmission for BS type 1-O with 15 kHz SCS. The diagram shows a horizontal timeline with 19 vertical tick marks representing transmission attempts. The first tick mark is labeled '0 us'. Subsequent tick marks are labeled from '0.2 us' to '3.8 us' in increments of 0.2 us. A curved arrow originates from the '0 us' label and points to the final '3.8 us' label, indicating the sequence of offsets used during testing.](ab5f5ba41a1f485b0d132c14fdf23bc0_img.jpg) + +Figure 8.2.9.4.2-1: Timing offset scheme for MsgA transmission for BS type 1-O with 15 kHz SCS. The diagram shows a horizontal timeline with 19 vertical tick marks representing transmission attempts. The first tick mark is labeled '0 us'. Subsequent tick marks are labeled from '0.2 us' to '3.8 us' in increments of 0.2 us. A curved arrow originates from the '0 us' label and points to the final '3.8 us' label, indicating the sequence of offsets used during testing. + +**Figure 8.2.9.4.2-1: Timing offset scheme for MsgA transmission for BS type 1-O with 15 kHz SCS** + +The timing offset base value for MsgA signal with 30 kHz SCS is set to 0. This offset is increased within the loop, by adding in each step a value of 0.1 us for *BS type 1-O* with 30 kHz SCS, until the end of the tested range, 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-2. + +![Figure 8.2.9.4.2-2: Timing offset scheme for MsgA transmission for BS type 1-O with 30 kHz SCS. The diagram shows a sequence of 20 time slots, each 0.1 us wide, starting from 0 us and ending at 2.0 us. Arrows indicate the timing offset for each slot, increasing by 0.1 us in each step.](061137657bf1fb2669843fe20861b2ec_img.jpg) + +The diagram illustrates the timing offset scheme for MsgA transmission for BS type 1-O with 30 kHz SCS. It shows a sequence of 20 time slots, each 0.1 us wide, starting from 0 us and ending at 2.0 us. Arrows indicate the timing offset for each slot, increasing by 0.1 us in each step. + +Figure 8.2.9.4.2-2: Timing offset scheme for MsgA transmission for BS type 1-O with 30 kHz SCS. The diagram shows a sequence of 20 time slots, each 0.1 us wide, starting from 0 us and ending at 2.0 us. Arrows indicate the timing offset for each slot, increasing by 0.1 us in each step. + +**Figure 8.2.9.4.2-2: Timing offset scheme for MsgA transmission for BS type 1-O with 30 kHz SCS** + +The timing offset base value for MsgA signal with 60 kHz is set to 0. This offset is increased within the loop, by adding in each step a value of 0.1 us for *BS type 2-O* with 60 kHz SCS, until the end of the tested range, which is 0.6 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-3. + +![Figure 8.2.9.4.2-3: Timing offset scheme for MsgA transmission for BS type 2-O with 60 kHz SCS. The diagram shows a sequence of 6 time slots, each 0.1 us wide, starting from 0 us and ending at 0.6 us. Arrows indicate the timing offset for each slot, increasing by 0.1 us in each step.](ee70b385addc0cd03ee26d51d63c97cf_img.jpg) + +The diagram illustrates the timing offset scheme for MsgA transmission for BS type 2-O with 60 kHz SCS. It shows a sequence of 6 time slots, each 0.1 us wide, starting from 0 us and ending at 0.6 us. Arrows indicate the timing offset for each slot, increasing by 0.1 us in each step. + +Figure 8.2.9.4.2-3: Timing offset scheme for MsgA transmission for BS type 2-O with 60 kHz SCS. The diagram shows a sequence of 6 time slots, each 0.1 us wide, starting from 0 us and ending at 0.6 us. Arrows indicate the timing offset for each slot, increasing by 0.1 us in each step. + +**Figure 8.2.9.4.2-3: Timing offset scheme for MsgA transmission for BS type 2-O with 60 kHz SCS** + +The timing offset base value for MsgA signal with 120 kHz is set to 0. This offset is increased within the loop, by adding in each step a value of 0.1 us for *BS type 2-O* with 120 kHz SCS, until the end of the tested range, which is 0.5 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-4. + +![Figure 8.2.9.4.2-4: Timing offset scheme for MsgA transmission for BS type 2-O with 120 kHz SCS. The diagram shows a sequence of 5 time slots, each 0.1 us wide, starting from 0 us and ending at 0.5 us. Arrows indicate the timing offset for each slot, increasing by 0.1 us in each step.](286afeddc8f076c168e16822fa62ba81_img.jpg) + +The diagram illustrates the timing offset scheme for MsgA transmission for BS type 2-O with 120 kHz SCS. It shows a sequence of 5 time slots, each 0.1 us wide, starting from 0 us and ending at 0.5 us. Arrows indicate the timing offset for each slot, increasing by 0.1 us in each step. + +Figure 8.2.9.4.2-4: Timing offset scheme for MsgA transmission for BS type 2-O with 120 kHz SCS. The diagram shows a sequence of 5 time slots, each 0.1 us wide, starting from 0 us and ending at 0.5 us. Arrows indicate the timing offset for each slot, increasing by 0.1 us in each step. + +**Figure 8.2.9.4.2-4: Timing offset scheme for MsgA transmission for BS type 2-O with 120 kHz SCS** + +## 8.2.9.5 Test Requirement + +### 8.2.9.5.1 Test Requirement for *BS type 1-O* + +The block error rate of MsgA PUSCH for the reference measurement channel as specified in Annex A at the SNR given in table 8.2.9.5.1-1 to table 8.2.9.5.1-4 shall not exceed 1%. + +**Table 8.2.9.5.1-1: Test requirements for MsgA PUSCH for 2-step RA type, Type A, 15 kHz SCS** + +| Number of TX antennas | Number of RX demodulation branches | Cyclic prefix | Propagation conditions (Annex J) | BLER | FRC (Annex A) | Time offset (Note 1) | SNR (dB) | +|-----------------------|------------------------------------|---------------|----------------------------------|------|---------------------------|----------------------|----------| +| 1 | 2 | Normal | TDLC300-100 | 1% | G-FR1-A8-1, or G-FR1-A8-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.1-2: Test requirements for MsgA PUSCH for 2-step RA type, Type A, 30 kHz SCS** + +| Number of TX antennas | Number of RX demodulation branches | Cyclic prefix | Propagation conditions (Annex J) | BLER | FRC (Annex A) | Time offset (Note 1) | SNR (dB) | +|-----------------------|------------------------------------|---------------|----------------------------------|------|---------------------------|----------------------|----------| +| 1 | 2 | Normal | TDLC300-100 | 1% | G-FR1-A8-2, or G-FR1-A8-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.1-3: Test requirements for MsgA PUSCH for 2-step RA type, Type B, 15 kHz SCS** + +| Number of TX antennas | Number of RX demodulation branches | Cyclic prefix | Propagation conditions (Annex J) | BLER | FRC (Annex A) | Time offset (Note 1) | SNR (dB) | +|-----------------------|------------------------------------|---------------|----------------------------------|------|---------------------------|----------------------|----------| +| 1 | 2 | Normal | TDLC300-100 | 1% | G-FR1-A8-1, or G-FR1-A8-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.1-4: Test requirements for MsgA PUSCH for 2-step RA type, Type B, 30 kHz SCS** + +| Number of TX antennas | Number of RX demodulation branches | Cyclic prefix | Propagation conditions (Annex J) | BLER | FRC (Annex A) | Time offset (Note 1) | SNR (dB) | +|-----------------------|------------------------------------|---------------|----------------------------------|------|---------------------------|----------------------|----------| +| 1 | 2 | Normal | TDLC300-100 | 1% | G-FR1-A8-2, or G-FR1-A8-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.9.5.2 Test Requirement for BS type 2-O + +The block error rate of MsgA PUSCH for the reference measurement channel as specified in Annex A at the SNR given in table 8.2.9.5.2-1 to table 8.2.9.5.2-2 shall not exceed 1%. + +**Table 8.2.9.5.2-1: Test requirements for MsgA PUSCH for 2-step RA type, Type B, 60 kHz SCS** + +| Number of TX antennas | Number of RX demodulation branches | Cyclic prefix | Propagation conditions (Annex J) | BLER | FRC (Annex A) | Time offset (Note 1) | SNR (dB) | +|-----------------------|------------------------------------|---------------|----------------------------------|------|---------------|----------------------|----------| +| 1 | 2 | Normal | TDLA30-300 | 1% | G-FR2-A3-25 | 0, 0.1, 0.6 | 9.3 | + +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-2: Test requirements for MsgA PUSCH for 2-step RA type, Type B, 120 kHz SCS** + +| Number of TX antennas | Number of RX demodulation branches | Cyclic prefix | Propagation conditions (Annex J) | BLER | FRC (Annex A) | Time offset (Note 1) | SNR (dB) | +|-----------------------|------------------------------------|---------------|----------------------------------|------|---------------|----------------------|----------| +| 1 | 2 | Normal | TDLA30-300 | 1% | G-FR2-A3-26 | 0, 0.1, 0.5 | 8.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. + +## 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 + +For BS type 1-O, the minimum requirement is in TS 38.104 [2], clause 11.2.1.1. + +For BS type 2-O, no requirement and no test are defined. + +### 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. + +Direction to be tested: OTA REFSSENS *receiver target reference direction* (see D.54 in table 4.6-1). + +#### 8.2.10.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.3. +- 2) Align the manufacturer declared coordinate system orientation of the BS with the test system. +- 3) Set the BS 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 the corresponding UL reference measurement channel defined in annex A, and according to additional test parameters listed in table 8.2.10.4.2-1. + +**Table 8.2.10.4.2-1: Test parameters for testing PUSCH** + +| Parameter | | Value | +|--------------------------------------------------------------------------------------------|-------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| BS type | | BS type 1-O | +| 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 15 KHz and first interlace with RBs 0,5,10,...,50 are allocated for tests with 30 KHz. | +| | 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. | | | + +- 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 BS receiver is as specified in clause 8.2.10.5.1, 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.2.10.4.2-2. + +**Table 8.2.10.4.2-2: AWGN power level at the BS input** + +| BS type | Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------|---------------------------|-------------------------|-----------------------------------------------| +| 1-O | 15 | 20 | $-80.2 - \Delta_{OTAREFSENS}$ dBm / 19.08 MHz | +| | 30 | 20 | $-80.4 - \Delta_{OTAREFSENS}$ dBm / 18.36 MHz | + +NOTE 1: $\Delta_{OTAREFSENS}$ as declared in D.53 in table 4.6-1 and clause 7.1. + +NOTE 2: 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. + +## 8.2.10.5 Test Requirement + +### 8.2.10.5.1 Test requirement for BS type 1-O + +The throughput measured according to clause 8.2.10.4.2 shall not be below the limits for the SNR levels specified in table 8.2.10.5-1. + +**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 demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (Annex J) | 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 demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (Annex J) | 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.5-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 demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (Annex J) | 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-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 demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (Annex J) | 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 | + +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.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 HARQ/ACK, CSI part 1 or CSI part 2 information transmitted. + +The number of UCI information bit payload per slot is defined as 18 bits. + +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 Requirement + +The minimum requirement is in TS 38.104 [2] clause 11.2.1.11. + +### 8.2.11.3 Test purpose + +The test shall verify the receiver's ability to detect UCI with 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 + +Direction to be tested: OTA REFSENS *receiver target reference direction* (see D.54 in table 4.6-1). + +#### 8.2.11.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.3. +- 2) Align the manufacturer declared coordinate system orientation of the BS with the test system. +- 3) Set the BS 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 to the corresponding UL reference measurement channel defined in annex A, and according to additional test parameters listed in table 8.2.11.4.2-1. The UCI information bit payload per slot is equal to 18 bits. + +**Table: 8.2.11.4.2-1 Test parameters for testing CG-UCI multiplexed on interlaced PUSCH** + +| Parameter | | Value | +|-------------------------------------------|-------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Transform precoding | | Disabled | +| Default TDD UL-DL pattern | | 30 kHz SCS:
7D1S2U, S=6D:4G:4U

15 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 | +| | 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 15 KHz and first interlace with RBs 0,5,10,...50 are allocated for tests with 30 KHz. | +| | Frequency hopping | Disabled | +| Code block group based PUSCH transmission | | Disabled | +| PT-RS | | Disabled | +| UCI | Number of information bits | 18 | +| | scaling | 1 | +| | betaOffsetCG-UCI-Index1 | 8 | +| | UCI partition for frequency hopping | Disabled | + +- 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 BS receiver is as specified in clause 8.2.11.5.1 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.2.11.4.2-2. + +**Table 8.2.11.4.2-2: AWGN power level at the BS input** + +| BS type | Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|--------------------------------------------------------------------------------|---------------------------|-------------------------|-----------------------------------------------| +| BS type 1-O | 15 | 20 | $-80.2 - \Delta_{OTAREFSENS}$ dBm / 19.08 MHz | +| BS type 1-O | 30 | 20 | $-80.4 - \Delta_{OTAREFSENS}$ dBm / 18.36 MHz | +| NOTE: $\Delta_{OTAREFSENS}$ as declared in D.53 in table 4.6-1 and clause 7.1. | | | | + +- 8) The signal generators send a test pattern where CG-UCI information can be multiplexed on interlaced PUSCH. The following statistics are kept: the number of incorrectly decoded CG-UCI information transmitted during UCI multiplexed on interlaced PUSCH transmission. + +## 8.2.11.5 Test Requirement + +### 8.2.11.5.1 Test requirement for BS type 1-O + +The fraction of incorrectly decoded CG-UCI according to clause 8.2.11.4.2 shall be less than 1 % for the SNR listed in table 8.2.11.5.1-1 to table 8.2.11.5.1-4. + +**Table 8.2.11.5.1-1: Test requirements for CG-UCI multiplexed on interlaced PUSCH, Type A, 20 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (Annex J) | 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.1-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 demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (Annex J) | 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.1-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 demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (Annex J) | 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.1-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 demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (Annex J) | 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 + +For BS type 1-O, the minimum requirement is in TS 38.104 [2], clause 11.2.1.12. + +For BS type 2-O, the minimum requirement is in TS 38.104 [2], clause 11.2.2.9. + +### 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_{\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.12.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.3. +- 2) Align the manufacturer declared coordinate system orientation of the BS with the test system. +- 3) Set the BS 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 the corresponding UL reference measurement channel defined in annex A, and according to additional test parameters listed in table 8.2.12.4.2-1. + +**Table: 8.2.12.4.2-1 Test parameters for testing PUSCH TBoMS** + +| Parameter | | BS type 1-O | BS type 2-O | +|-------------------------------------------|-------------------------------------------|-------------------------------------------------------------------------|------------------------------------------------| +| Transform precoding | | Disabled | Disabled | +| Default TDD UL-DL pattern (Note 1) | | 15 kHz SCS:
3D1S1U, S=10D:2G:2U
30 kHz SCS:
7D1S2U, S=6D:4G:4U | 60 kHz and 120 kHz SCS:
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 | +| | Additional DM-RS position | pos1 | pos1 | +| | Number of DM-RS CDM group(s) without data | 2 | 2 | +| | Ratio of PUSCH EPRE to DM-RS EPRE | -3 dB | -3 dB | +| | DM-RS port | 0 | 0 | +| | DM-RS sequence generation | $N_{ID}^0=0, n_{SCID}=0$ | $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 | +| | Number of slots allocated for TBoMS PUSCH | 8 for FDD
2 for TDD | 2 | +| | Number of repetitions of a single TBoMS | 1 | 1 | +| Frequency domain resource assignment | RB assignment | 5 RBs in the middle of the test bandwidth | 5RBs in the middle of the test bandwidth | +| | Frequency hopping | Disabled | Disabled | +| Code block group based PUSCH transmission | | Disabled | Disabled | +| PT-RS configuration | Frequency density ( $K_{PT-RS}$ ) | N.A. | Disabled | +| | Time density ( $L_{PT-RS}$ ) | N.A. | Disabled | + +Note 1: The same requirements are applicable to TDD with different UL-DL pattern. + +- 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 BS receiver is as specified in clause 8.2.12.5.1 and clause 8.2.12.5.2 for BS type 1-O and BS 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.2.12.4.2-2. + +**Table 8.2.12.4.2-2: AWGN power level at the BS input** + +| BS type | Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|----------------------|---------------------------|-------------------------|-------------------------------------------------------------------| +| BS type 1-O (Note 4) | 15 | 5 | $-86.5 - \Delta_{OTAREFSENS}$ dBm / 4.5 MHz | +| | 30 | 10 | $-83.6 - \Delta_{OTAREFSENS}$ dBm / 8.64 MHz | +| BS type 2-O (Note 5) | 60 | 50 | $EIS_{REFSENS\_50M} + \Delta_{FR2\_REFSENS} + 15$ dBm / 47.52 MHz | +| | 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 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: $EIS_{REFSENS\_50M}$ as declared in D.28 in table 4.6-1. + +NOTE 4: 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. + +NOTE 5: The AWGN power level contains an AWGN offset of 15dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 15dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. + +- 8) For reference channels applicable to the BS, measure the throughput. + +## 8.2.12.5 Test Requirement + +### 8.2.12.5.1 Test requirement for BS type 1-O + +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-1 to 8.2.12.5.1-4. + +**Table 8.2.12.5.1-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 J) | 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.1-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 J) | 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.1-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 J) | 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.1-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 J) | 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 | + +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.2.12.5.2 Test requirement for BS type 2-O + +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.2-1 to 8.2.12.5.2-2. + +**Table 8.2.12.5.2-1: Minimum requirements for PUSCH TBoMS, Type B, 50 MHz channel bandwidth, 60 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Duplex | Propagation conditions and correlation matrix (Annex J) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|--------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDD | TDLA30-300 Low | 70% | G-FR2-A3-27 | pos1 | -2.0 | + +**Table 8.2.12.5.2-2: Minimum requirements for PUSCH TBoMS, Type B, 50 MHz channel bandwidth, 120 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Duplex | Propagation conditions and correlation matrix (Annex J) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|--------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDD | TDLA30-300 Low | 70% | G-FR2-A3-28 | pos1 | -1.8 | + +### 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.8. + +#### 8.2.13.2 Minimum Requirement + +For BS type 1-O, the minimum requirement is in TS 38.104 [2], clause 11.2.1.13. + +For BS type 2-O, the minimum requirement is in TS 38.104 [2], clause 11.2.2.10. + +#### 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_{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.13.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.3. +- 2) Align the manufacturer declared coordinate system orientation of the BS with the test system. +- 3) Set the BS 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 the corresponding UL reference measurement channel defined in annex A, and according to additional test parameters listed in table 8.2.13.4.2-1. + +**Table 8.2.13.4.2-1: Test parameters for testing PUSCH with DMRS bundling** + +| Parameter | | BS type 1-O | BS type 2-O | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------|------------------------------------------|------------------------------------------| +| Transform precoding | | Disabled | | +| Example TDD UL-DL pattern (Note 1) | | 7D1S2U, S=6D:4G:4U | DDSUU, S=10D:2G:2U or DSUUU, S=10D:2G:2U | +| HARQ | Maximum number of HARQ transmissions | 4 | | +| | RV sequence (Note 2) | 0, 3, 0, 3 for TDD
0, 0, 0, 0 for FDD | 0, 3, 0, 3 | +| DM-RS | DM-RS configuration type | 1 | | +| | DM-RS duration | single-symbol DM-RS | | +| | Additional DM-RS position | pos0, pos1 | 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 | B | +| | Start symbol | 0 | | +| | Allocation length | 14 | | +| | PUSCH aggregation factor | 8 slots for FDD
2 slots for TDD | | +| Frequency domain resource assignment | RB assignment | Full applicable test bandwidth | | +| | Frequency hopping | Disabled | | +| Configured time domain window (cTDW) length | | 2 for TDD
8 for FDD | 2 | +| Code block group based PUSCH transmission | | Disabled | Disabled | +| PTRS configuration | Frequency density ( $K_{PT-RS}$ ) | N.A. | Disabled | +| | Time density ( $L_{PT-RS}$ ) | N.A. | 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 | | | | + +- 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 BS receiver is as specified in clause 8.2.13.5.1 and clause 8.2.13.5.2 for BS type 1-O and BS 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.2.13.4.2-2. + +**Table 8.2.13.4.2-2: AWGN power level at the BS input** + +| BS type | Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|----------------------|---------------------------|-------------------------|--------------------------------------------------------------------------------------------------------| +| BS type 1-O (Note 4) | 15 | 5 | $-86.5 - \Delta_{\text{OTAREFSENS}}$ dBm / 4.5 MHz | +| | 30 | 10 | $-83.6 - \Delta_{\text{OTAREFSENS}}$ dBm / 8.64 MHz | +| BS type 2-O (Note 5) | 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. + +NOTE 4: 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. + +NOTE 5: The AWGN power level contains an AWGN offset of 15dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 15dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. + +- 8) For reference channels applicable to the BS, measure the throughput. + +## 8.2.13.5 Test Requirement + +### 8.2.13.5.1 Test requirement for BS type 1-O + +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-1 to table 8.2.13.5.1-8. + +**Table 8.2.13.5.1-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 demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | 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.1-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 demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | 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.1-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 demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | 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.1-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 demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | 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.1 | + +**Table 8.2.13.5.1-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 demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | 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.1-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 demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | 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.1-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 demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | 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.1-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 demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | 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.2.13.5.2 Test requirement for BS type 2-O + +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.2-1 and table 8.2.13.5.2-2. + +**Table 8.2.13.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 | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLA30-75 Low | 70 % | G-FR2-A3B-1 | pos1 | -3.3 | + +**Table 8.2.13.5.2-2: Test requirements for PUSCH with 70% of maximum throughput, 50 MHz channel bandwidth, 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Cyclic prefix | Propagation conditions and correlation matrix (annex J) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLA30-75 Low | 70 % | G-FR2-A3B-2 | pos1 | -2.9 | + +## 8.3 OTA 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 [24] clause 6.3.3.1 and TS 38.101-2 [25] 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 + +For *BS type 1-O*, the minimum requirements are in TS 38.104 [2] clause 11.3.1.1 and 11.3.1.2. + +For *BS type 2-O*, the minimum requirements are in TS 38.104 [2] clause 11.3.2.1 and 11.3.2.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. + +Direction to be tested: OTA REFSENS *receiver target reference direction* (see D.54 in table 4.6-1). + +##### 8.3.1.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.3. +- 2) Align the manufacturer declared coordinate system orientation of the BS with the test system. + +- 3) Set the BS 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 [20] and according to additional test parameters listed in table 8.3.1.4.2-1. + +**Table 8.3.1.4.2-1: Test parameters** + +| Parameter | BS type 1-O | BS type 2-O | +|--------------------------------------|----------------------------------------------|----------------------------------------------| +| number of UCI information bits | 1 | 1 | +| Number of PRBs | 1 | FR2-1: 1
FR2-2: 1, 16 | +| 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 | + +- 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 BS receiver is as specified in clause 8.3.1.5.1 and 8.3.1.5.2 for *BS type 1-O* and *BS 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 quoted in table 8.3.1.4.2-2. + +**Table 8.3.1.4.2-2: AWGN power level at the BS input****Table 8.3.1.4.2-2: AWGN power level at the BS input** + +| BS type | Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|----------------------|---------------------------|-------------------------|-----------------------------------------------------------------------------------------| +| BS type 1-O (Note 4) | 15 | 5 | $-83.5 - \Delta_{\text{OTAREFSENS}}$ dBm / 4.5 MHz | +| | | 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 | +| | | 100 | $-70.1 - \Delta_{\text{OTAREFSENS}}$ dBm / 98.28 MHz | +| BS type 2-O (Note 5) | 60 | 50 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 15$ dBm / 47.52 MHz | +| | | 100 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 18$ dBm / 95.04 MHz | +| | 120 | 50 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 15$ dBm / 46.08 MHz | +| | | 100 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 18$ dBm / 95.04 MHz | +| | | 200 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 21$ dBm / 190.08 MHz | +| | | 400 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 24$ dBm / 380.16 MHz | +| | 480 | 400 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 24$ dBm / 380.16 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. + +NOTE 4: 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. + +NOTE 5: The AWGN power level contains an AWGN offset of 15dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 15dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. + +- 8) 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 rectangular boxes labeled 'ACK' in a horizontal sequence, followed by three dots '...' indicating a repeating pattern.](2f05c618a0dd9a0242a6b12ac9aee748_img.jpg) + +Figure 8.3.1.4.2-1: Test signal pattern for single user PUCCH format 0 demodulation tests. The diagram shows three rectangular boxes labeled 'ACK' in a horizontal sequence, followed by three dots '...' indicating a repeating pattern. + +**Figure 8.3.1.4.2-1: Test signal pattern for single user PUCCH format 0 demodulation tests** + +## 8.3.1.5 Test Requirement + +### 8.3.1.5.1 Test requirement for BS 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.3.1.5.1-1 and in table 8.3.1.5.1-2. + +**Table 8.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) | | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------|------------------------------|--------|--------| +| | | | | 5 MHz | 10 MHz | 20 MHz | +| 1 | 2 | TDLC300-100 Low | 1 | 10.0 | 9.4 | 9.9 | +| | | | 2 | 3.4 | 4.3 | 3.9 | + +**Table 8.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.3.1.5.2 Test requirement for BS 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.3.1.5.2-1 to table 8.3.1.5.2-4. + +**Table 8.3.1.5.2-1: Test requirements for PUCCH format 0 and 60 kHz SCS in FR2-1** + +| 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.3.1.5.2-2: Test requirements for PUCCH format 0 and 120 kHz SCS in FR2-1** + +| 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 | + +**Table 8.3.1.5.2-3: Test requirements for PUCCH format 0 and 120 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | Number of OFDM symbols | Number of PRB | Channel bandwidth / SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------|---------------|------------------------------| +| | | | | | 100 MHz | +| 1 | 2 | TDLA30-650 Low | 1 | 1 | 10.2 | +| | | | 2 | 16 | -5.2 | + +**Table 8.3.1.5.2-4: Test requirements for PUCCH format 0 and 480 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | Number of OFDM symbols | Number of PRB | Channel bandwidth / SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------|---------------|------------------------------| +| | | | | | 400 MHz | +| 1 | 2 | TDLA10-650 Low | 1 | 1 | 10.3 | +| | | | 2 | 16 | -4.0 | + +## 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 [24] and TS 38.101-2 [25] 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 + +For BS type 1-O, the minimum requirement is in TS 38.104 [2], clause 11.3.1.3. + +For BS type 2-O, the minimum requirement is in TS 38.104 [2], clause 11.3.2.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 + +Direction to be tested: OTA REFSENS receiver target reference direction (see D.54 in table 4.6-1). + +##### 8.3.2.1.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.3. +- 2) Align the manufacturer declared coordinate system orientation of the BS with the test system. +- 3) Set the BS 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 [20], and according to additional test parameters listed in table 8.3.2.1.4.2-1. + +**Table 8.3.2.1.4.2-1: Test parameters** + +| Parameter | Test | +|---------------------------------------------------------|-------------------------------------------| +| Number of information bits | 2 | +| Number of PRBs | FR1 and FR2-1: 1
FR2-2: 1, 16 | +| 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 | + +- 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 BS receiver is as specified in clause 8.3.2.1.5.1 and 8.3.2.1.5.2 for BS type 1-O and BS 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.3.2.1.4.2-2. + +**Table 8.3.2.1.4.2-2: AWGN power level at the BS input** + +| BS type | Subcarrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|-------------------------|--------------------------|-------------------------|-----------------------------------------------------------------------------------------| +| BS type 1-O
(Note 4) | 15 kHz | 5 | $-83.5 - \Delta_{\text{OTAREFSENS}}$ dBm / 4.5 MHz | +| | | 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 | +| BS type 2-O
(Note 5) | 60 kHz | 50 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 15$ dBm / 47.52 MHz | +| | | 100 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 18$ dBm / 95.04 MHz | +| | 120 kHz | 50 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 15$ dBm / 46.08 MHz | +| | | 100 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 18$ dBm / 95.04 MHz | +| | | 200 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 21$ dBm / 190.08 MHz | +| | | 400 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 24$ dBm / 380.16 MHz | +| | 480 kHz | 400 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 24$ dBm / 380.16 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. + +NOTE 4: 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. + +NOTE 5: The AWGN power level contains an AWGN offset of 15dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 15dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. + +- 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.3.2.1.5 Test Requirement + +#### 8.3.2.1.5.1 Test Requirement for BS 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.3.2.1.5.1-1 and table 8.3.2.1.5.1-2. + +**Table 8.3.2.1.5.1-1: Required SNR for PUCCH format 1 with 15 kHz SCS** + +| Number of TX antennas | Number of Demodulation Branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Channel bandwidth / SNR (dB) | | | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------------------------------|--------|--------| +| | | | | 5 MHz | 10 MHz | 20 MHz | +| 1 | 2 | Normal | TDLC300-100 Low | -3.2 | -3.0 | -3.0 | + +**Table 8.3.2.1.5.1-2: Required SNR for PUCCH format 1 with 30 kHz SCS** + +| Number of TX antennas | Number of Demodulation Branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Channel bandwidth / SNR (dB) | | | | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------------------------------|--------|--------|---------| +| | | | | 10 MHz | 20 MHz | 40 MHz | 100 MHz | +| 1 | 2 | Normal | TDLC300-100 Low | -2.2 | -2.7 | -3.3 | -2.9 | + +#### 8.3.2.1.5.2 Test Requirement for BS 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.3.2.1.5.2-1 to table 8.3.2.1.5.2-4. + +**Table 8.3.2.1.5.2-1: Required SNR for PUCCH format 1 with 60 kHz SCS in FR2-1** + +| Number of TX antennas | Number of Demodulation Branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Channel bandwidth / SNR (dB) | | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------------------------------|---------| +| | | | | 50 MHz | 100 MHz | +| 1 | 2 | Normal | TDLA30-300 Low | -0.6 | -3.6 | + +**Table 8.3.2.1.5.2-2: Required SNR for PUCCH format 1 with 120 kHz SCS in FR2-1** + +| Number of TX antennas | Number of Demodulation Branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Channel bandwidth / SNR (dB) | | | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------------------------------|---------|---------| +| | | | | 50 MHz | 100 MHz | 200 MHz | +| 1 | 2 | Normal | TDLA30-300 Low | -3.3 | -3.3 | -2.4 | + +**Table 8.3.2.1.5.2-3: Required SNR for PUCCH format 1 and 120 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Number of PRB | Channel bandwidth / SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|---------------|------------------------------| +| | | | | | 100 MHz | +| 1 | 2 | Normal | TDLA30-650 Low | 1 | -3.5 | +| | | | | 16 | -14.2 | + +**Table 8.3.2.1.5.2-4: Required SNR for PUCCH format 1 and 480 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Number of PRB | Channel bandwidth / SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|---------------|------------------------------| +| | | | | | 400 MHz | +| 1 | 2 | Normal | TDLA10-650 Low | 1 | -3.6 | +| | | | | 16 | -13.8 | + +### 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 [24] and TS 38.101-2 [25] 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 + +For BS type 1-O, the minimum requirement is in TS 38.104 [2], clause 11.3.1.3. + +For BS type 2-O, the minimum requirement is in TS 38.104 [2], clause 11.3.2.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: 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.3.2.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.3. +- 2) Align the manufacturer declared coordinate system orientation of the BS with the test system. +- 3) Set the BS 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 [20], and according to additional test parameters listed in table 8.3.2.2.4.2-1. + +**Table 8.3.2.2.4.2-1: Test Parameters** + +| Parameter | Value | +|------------------------------------------------------------|-------------------------------------------| +| Number of information bits | 2 | +| Number of PRBs | FR1 and FR2-1: 1
FR2-2: 1, 16 | +| 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 | + +- 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 BS receiver is as specified in clause 8.3.2.2.5.1 and 8.3.2.2.5.2 for BS type 1-O and BS 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.3.2.2.4.2-2. + +**Table 8.3.2.2.4.2-2: AWGN power level at the BS input** + +| BS type | Subcarrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|-------------------------|--------------------------|-------------------------|-----------------------------------------------------------------------------------------| +| BS type 1-O
(Note 4) | 15 kHz | 5 | $-83.5 - \Delta_{\text{OTAREFSENS}}$ dBm / 4.5 MHz | +| | | 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 | +| BS type 2-O
(Note 5) | 60 kHz | 50 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 15$ dBm / 47.52 MHz | +| | | 100 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 18$ dBm / 95.04 MHz | +| | 120 kHz | 50 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 15$ dBm / 46.08 MHz | +| | | 100 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 18$ dBm / 95.04 MHz | +| | | 200 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 21$ dBm / 47.52 MHz | +| | | 400 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 24$ dBm / 380.16 MHz | +| | 480 kHz | 400 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 24$ dBm / 380.16 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. + +NOTE 4: 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. + +NOTE 5: The AWGN power level contains an AWGN offset of 15dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 15dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. + +- 8) 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 + +#### 8.3.2.2.5.1 Test Requirement for BS 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.3.2.2.5-1 and table 8.3.2.2.5-2. + +**Table 8.3.2.2.5.1-1: Required SNR for PUCCH format 1 with 15 kHz SCS** + +| Number of TX antennas | Number of Demodulation Branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Channel bandwidth / SNR (dB) | | | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------------------------------|--------|--------| +| | | | | 5 MHz | 10 MHz | 20 MHz | +| 1 | 2 | Normal | TDLC300-100 Low | -4.4 | -3.8 | -4.4 | + +**Table 8.3.2.2.5.1-2: Required SNR for PUCCH format 1 with 30 kHz SCS** + +| Number of TX antennas | Number of Demodulation Branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | 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 | + +#### 8.3.2.2.5.2 Test Requirement for BS 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.3.2.2.5.2-1 to table 8.3.2.2.5.2-4. + +**Table 8.3.2.2.5.2-1: Required SNR for PUCCH format 1 with 60 kHz SCS in FR2-1** + +| Number of TX antennas | Number of Demodulation Branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Channel bandwidth / SNR (dB) | | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------------------------------|---------| +| | | | | 50 MHz | 100 MHz | +| 1 | 2 | Normal | TDLA30-300 Low | -3.3 | -3.6 | + +**Table 8.3.2.2.5.2-2: Required SNR for PUCCH format 1 with 120 kHz SCS in FR2-1** + +| Number of TX antennas | Number of Demodulation Branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Channel bandwidth / SNR (dB) | | | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------------------------------|---------|---------| +| | | | | 50 MHz | 100 MHz | 200 MHz | +| 1 | 2 | Normal | TDLA30-300 Low | -4.1 | -4.0 | -4.0 | + +**Table 8.3.2.2.5.2-3: Required SNR for PUCCH format 1 and 120 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Number of PRB | Channel bandwidth / SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|---------------|------------------------------| +| | | | | | 100 MHz | +| 1 | 2 | Normal | TDLA30-650 Low | 1 | -2.1 | +| | | | | 16 | -12.5 | + +**Table 8.3.2.2.5.2-4: Required SNR for PUCCH format 1 and 480 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Number of PRB | Channel bandwidth / SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|---------------|------------------------------| +| | | | | | 400 MHz | +| 1 | 2 | Normal | TDLA10-650 Low | 1 | -2.3 | +| | | | | 16 | -13.2 | + +### 8.3.3 Performance requirements for PUCCH format 2 + +#### 8.3.3.1 ACK missed detection performance requirements + +##### 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 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 BS is based on the test applicability rules defined in clause 8.1.2. + +#### 8.3.3.1.2 Minimum Requirement + +For *BS type 1-O*, the minimum requirement is in TS 38.104 [2] clause 11.3.1.4. + +For *BS type 2-O*, the minimum requirement is in TS 38.104 [2] clause 11.3.2.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 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.3.3.1.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.3. +- 2) Align the manufacturer declared coordinate system orientation of the BS with the test system. +- 3) Set the BS 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 one polarization of the test antenna(s). +- 5) The characteristics of the wanted signal shall be configured according to TS 38.211 [20], and according to additional test parameters listed in table 8.3.3.1.4.2-1. + +**Table 8.3.3.1.4.2-1: Test parameters** + +| Parameter | Value | +|------------------------------------|--------------| +| 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$ | + +- 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 BS receiver is as specified in clause 8.3.3.1.5.1 and 8.3.3.1.5.2 for *BS type 1-O* and *BS 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.3.3.1.4.2-2. + +**Table 8.3.3.1.4.2-2: AWGN power level at the BS input** + +| BS type | Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|-------------------------|---------------------------|-------------------------|---------------------------------------------------------------------------------------------------------| +| BS type 1-O
(Note 4) | 15 kHz | 5 | $-83.5 - \Delta_{\text{OTAREFSENS}}$ dBm / 4.5 MHz | +| | | 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 | +| BS type 2-O
(Note 5) | 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}$ | +| | 120 kHz | 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}$ | +| | | 400 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 24 \text{ dBm} / 380.16 \text{ MHz}$ | +| | 480 kHz | 400 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 24 \text{ dBm} / 380.16 \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 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: $\text{EIS}_{\text{REFSENS\_50M}}$ as declared in D.28 in table 4.6-1. +NOTE 4: 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. +NOTE 5: The AWGN power level contains an AWGN offset of 15dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 15dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. + +- 8) The signal generator sends a test pattern with pattern outlined in figure 8.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.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.](4599d7b27f6bd8041758d322232455d0_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', representing detected ACK bits. To the right of the third box are three dots, indicating a continuation of the pattern. + +**Figure 8.3.3.1.4.2-1: Test signal pattern for PUCCH format 2 demodulation tests** + +### 8.3.3.1.5 Test requirement + +#### 8.3.3.1.5.1 Requirements for BS 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.3.3.1.5.1-1 and table 8.3.3.1.5.1-2. + +**Table 8.3.3.1.5.1-1: Required SNR for PUCCH format 2 with 15 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Channel bandwidth / SNR (dB) | | | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------------------------------|--------|--------| +| | | | | 5 MHz | 10 MHz | 20 MHz | +| 1 | 2 | Normal | TDLC300-100 Low | 6.4 | 6.2 | 6.5 | + +**Table 8.3.3.1.5.1-2: Required SNR for PUCCH format 2 with 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Channel bandwidth/ SNR (dB) | | | | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|-----------------------------|--------|-------|--------| +| | | | | 10MHz | 20 MHz | 40MHz | 100MHz | +| 1 | 2 | Normal | TDLC300-100 Low | 6.1 | 6.2 | 6.1 | 6.3 | + +## 8.3.3.1.5.2 + +## Requirements for BS 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.3.3.1.5.2-1 to table 8.3.3.1.5.2-4. + +**Table 8.3.3.1.5.2-1: Required SNR for PUCCH format 2 with 60 kHz SCS in FR2-1** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Channel bandwidth / SNR (dB) | | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------------------------------|---------| +| | | | | 50 MHz | 100 MHz | +| 1 | 2 | Normal | TDLA30-300 Low | 7.3 | 7.8 | + +**Table 8.3.3.1.5.2-2: Required SNR for PUCCH format 2 with 120 kHz SCS in FR2-1** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Channel bandwidth / SNR (dB) | | | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------------------------------|---------|---------| +| | | | | 50 MHz | 100 MHz | 200 MHz | +| 1 | 2 | Normal | TDLA30-300 Low | 7.2 | 6.9 | 7.2 | + +**Table 8.3.3.1.5.2-3: Required SNR for PUCCH format 2 and 120 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Channel bandwidth / SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------------------------------| +| | | | | 100 MHz | +| 1 | 2 | Normal | TDLA30-650 Low | 6 | + +**Table 8.3.3.1.5.2-4: Required SNR for PUCCH format 2 and 480 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Channel bandwidth / SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------------------------------| +| | | | | 400 MHz | +| 1 | 2 | Normal | TDLA10-650 Low | 6 | + +### 8.3.3.2 UCI BLER performance requirements + +#### 8.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 BS is based on the test applicability rules defined in clause 8.1.2. + +The transient period as specified in TS 38.101-1 [24] and TS 38.101-2 [25] 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 + +For *BS type 1-O*, the minimum requirement is in TS 38.104 [2] clause 11.3.1.4. + +For *BS type 2-O*, the minimum requirement is in TS 38.104 [2] clause 11.3.2.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 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.3.3.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.3. +- 2) Align the manufacturer declared coordinate system orientation of the BS with the test system. +- 3) Set the BS 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 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 [20], and according to additional test parameters listed in table 8.3.3.2.4.2-1. + +**Table 8.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$ | + +- 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 BS receiver is as specified in clause 8.3.3.2.5.1 and 8.3.3.2.5.2 for BS type 1-O and BS 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.3.3.2.4.2-2. + +**Table 8.3.3.2.4.2-2: AWGN power level at the BS input** + +| BS type | Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|----------------------|---------------------------|-------------------------|---------------------------------------------------------------------------------------------------------| +| BS type 1-O (Note 4) | 15 kHz | 5 | $-83.5 - \Delta_{\text{OTAREFSENS}}$ dBm / 4.5 MHz | +| | | 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 | +| BS type 2-O (Note 5) | 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}$ | +| | 120 kHz | 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}$ | +| | | 400 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 24 \text{ dBm} / 380.16 \text{ MHz}$ | +| | 480 kHz | 400 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 24 \text{ dBm} / 380.16 \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 declared in clause 7.1. + +NOTE 3: $\text{EIS}_{\text{REFSENS\_50M}}$ as declared in D.28 in table 4.6-1. + +NOTE 4: 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. + +NOTE 5: The AWGN power level contains an AWGN offset of 15dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 15dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. + +- 8) 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, indicating a repeating pattern.](026465adb7b73fef0f5e56a6541850a6_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, 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 requirement + +#### 8.3.3.2.5.1 Requirements for BS type 1-O + +The fraction of incorrectly decoded UCI is shall be less than 1% for the SNR listed in table 8.3.3.2.5.1-1 and table 8.3.3.2.5.1-2. + +**Table 8.3.3.2.5.1-1: Required SNR for PUCCH format 2 with 15 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Channel bandwidth / SNR (dB) | | | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------------------------------|--------|--------| +| | | | | 5 MHz | 10 MHz | 20 MHz | +| 1 | 2 | Normal | TDLC300-100 Low | 0.8 | 1.4 | 1.8 | + +**Table 8.3.3.2.5.1-2: Required SNR for PUCCH format 2 with 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Channel bandwidth/ SNR (dB) | | | | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|-----------------------------|--------|-------|--------| +| | | | | 10MHz | 20 MHz | 40MHz | 100MHz | +| 1 | 2 | Normal | TDLC300-100 Low | 1.1 | 1.7 | 1.0 | 0.9 | + +### 8.3.3.2.5.2 Requirements for BS type 2-O + +The fraction of incorrectly decoded UCI shall be less than 1% for the SNR listed in table 8.3.3.2.5.2-1 to table 8.3.3.2.5.2-4. + +**Table 8.3.3.2.5.2-1: Required SNR for PUCCH format 2 with 60 kHz SCS in FR2-1** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Channel bandwidth / SNR (dB) | | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------------------------------|---------| +| | | | | 50 MHz | 100 MHz | +| 1 | 2 | Normal | TDLA30-300 Low | 3.2 | 1.7 | + +**Table 8.3.3.2.5.2-2: Required SNR for PUCCH format 2 with 120 kHz SCS in FR2-1** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Channel bandwidth / SNR (dB) | | | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------------------------------|---------|---------| +| | | | | 50 MHz | 100 MHz | 200 MHz | +| 1 | 2 | Normal | TDLA30-300 Low | 1.8 | 1.8 | 1.7 | + +**Table 8.3.3.2.5.2-3: Required SNR for PUCCH format 2 and 120 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Channel bandwidth / SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------------------------------| +| | | | | 100 MHz | +| 1 | 2 | Normal | TDLA30-650 Low | 2.7 | + +**Table 8.3.3.2.5.2-4: Required SNR for PUCCH format 2 and 480 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Channel bandwidth / SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------------------------------| +| | | | | 400 MHz | +| 1 | 2 | Normal | TDLA10-650 Low | 3.2 | + +## 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 [24] clause 6.3.3.1 and TS 38.101-2 [25] 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 + +For *BS type 1-O*, the minimum requirement is in TS 38.104 [2], clause 11.3.1.5. + +For *BS type 2-O*, the minimum requirement is in TS 38.104 [2], clause 11.3.2.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 + +Direction to be tested: + +- OTA REFSENS *receiver target reference direction* (see D.54 in table 4.6-1). + +##### 8.3.4.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.3. +- 2) Align the manufacturer declared coordinate system orientation of the BS with the test system. +- 3) Set the BS 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 [20], and according to additional test parameters listed in table 8.3.4.4.2-1. + +**Table 8.3.4.4.2-1: 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 | + +- 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 BS receiver is as specified in clause 8.3.4.5.1 and 8.3.4.5.2 for *BS type 1-O* and *BS type 2-O* respectively, and 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.3.4.4.2-2. + +**Table 8.3.4.4.2-2: AWGN power level at the BS input** + +| BS type | Subcarrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|-------------------------|--------------------------|-------------------------|-----------------------------------------------------------------------------------------| +| BS type 1-O
(Note 4) | 15 | 5 | $-83.5 - \Delta_{\text{OTAREFSENS}}$ dBm / 4.5MHz | +| | | 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 | +| BS type 2-O
(Note 5) | 60 | 50 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 15$ dBm / 47.52MHz | +| | | 100 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 18$ dBm / 95.04 MHz | +| | 120 | 50 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 15$ dBm / 46.08 MHz | +| | | 100 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 18$ dBm / 95.04 MHz | +| | | 200 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 21$ dBm / 190.08 MHz | +| | | 400 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 24$ dBm / 380.16 MHz | +| | 480 | 400 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 24$ dBm / 380.16 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 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. + +NOTE 4: 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. + +NOTE 5: The AWGN power level contains an AWGN offset of 15dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 15dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. + +## 8.3.4.5 Test requirement + +### 8.3.4.5.1 Test requirement for *BS type 1-O* + +The fraction of incorrectly decoded UCI is shall be less than 1% for the SNR listed in table 8.3.4.5.1-1 and table 8.3.4.5.1-2. + +**Table 8.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 | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | 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 | +| 2 | 1 | 2 | Normal | TDLC300-100 Low | No additional DM-RS | 2.0 | 2.8 | 2.6 | + +**Table 8.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 | Cyclic Prefix | 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 | 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 | +| 2 | 1 | 2 | Normal | TDLC300-100 Low | No additional DM-RS | 2.4 | 2.6 | 2.6 | 2.1 | + +### 8.3.4.5.2 Test requirement for BS type 2-O + +The fraction of incorrectly decoded UCI is shall be less than 1% for the SNR listed in table 8.3.4.5.2-1 to table 8.3.4.5.2-4. + +**Table 8.3.4.5.2-1: Required SNR for PUCCH format 3 with 60 kHz SCS in FR2-1** + +| Test Number | Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Additional DM-RS configuration | Channel bandwidth / SNR (dB) | | +|-------------|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|------------------------------|---------| +| | | | | | | 50 MHz | 100 MHz | +| 1 | 1 | 2 | Normal | TDLA30-300 Low | No additional DM-RS | 2.2 | 1.3 | +| | | | | | Additional DM-RS | 1.9 | 1.5 | +| 2 | 1 | 2 | Normal | TDLA30-300 Low | No additional DM-RS | 3.6 | 3.0 | + +**Table 8.3.4.5.2-2: Required SNR for PUCCH format 3 with 120 kHz SCS in FR2-1** + +| Test Number | Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Additional DM-RS configuration | Channel bandwidth / SNR (dB) | | | +|-------------|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|------------------------------|---------|---------| +| | | | | | | 50 MHz | 100 MHz | 200 MHz | +| 1 | 1 | 2 | Normal | 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 | Normal | TDLA30-300 Low | No additional DM-RS | 1.7 | 3.5 | 2.0 | + +**Table 8.3.4.5.2-3: Required SNR for PUCCH format 3 with 120 kHz SCS in FR2-2** + +| Test Number | Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Additional DM-RS configuration | Channel bandwidth / SNR (dB) | +|-------------|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|------------------------------| +| | | | | | | 100 MHz | +| 1 | 1 | 2 | Normal | TDLA30-650 Low | No additional DM-RS | 1.2 | +| | | | | | Additional DM-RS | 1.3 | +| 2 | 1 | 2 | Normal | TDLA30-650 Low | No additional DM-RS | 2.4 | + +**Table 8.3.4.5.2-4: Required SNR for PUCCH format 3 with 480 kHz SCS in FR2-2** + +| Test Number | Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Additional DM-RS configuration | Channel bandwidth / SNR (dB) | +|-------------|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|------------------------------| +| | | | | | | 400 MHz | +| 1 | 1 | 2 | Normal | TDLA10-650 Low | No additional DM-RS | 1 | +| | | | | | Additional DM-RS | 1.1 | +| 2 | 1 | 2 | Normal | TDLA10-650 Low | No additional DM-RS | 2.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 [24] and TS 38.101-2 [25] 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 + +For BS type 1-O, the minimum requirement is in TS 38.104 [2], clause 11.3.1.6. + +For BS type 2-O, the minimum requirement is in TS 38.104 [2], clause 11.3.2.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 + +Direction to be tested: + +- OTA REFSENS *receiver target reference direction* (see D.54 in table 4.6-1). + +#### 8.3.5.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.3. +- 2) Align the manufacturer declared coordinate system orientation of the BS with the test system. +- 3) Set the BS 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 [20], and according to additional test parameters listed in table 8.3.5.4.2-1. + +**Table 8.3.5.4.2-1: Test parameters** + +| Parameter | Value | +|--------------------------------------|-------------------------------------------------| +| Modulation order | QPSK | +| First PRB prior to frequency hopping | 0 | +| Number of PRBs | FR1 and FR2-1: 1
FR2-2: 1, 16 | +| 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 BS receiver is as specified in clause 8.3.5.5.1 and 8.3.5.5.2 for *BS type 1-O* and *BS 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.3.5.4.2-2. + +**Table 8.3.5.4.2-2: AWGN power level at the BS input** + +| BS type | Subcarrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|-------------|--------------------------|-------------------------|-----------------------------------------------------------------------------------------| +| BS type 1-O | 15 | 5 | $-83.5 - \Delta_{\text{OTAREFSENS}}$ dBm / 4.5MHz | +| | | 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 | +| BS type 2-O | 60 | 50 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 15$ dBm / 47.52 MHz | +| | | 100 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 18$ dBm / 95.04 MHz | +| | 120 | 50 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 15$ dBm / 46.08 MHz | +| | | 100 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 18$ dBm / 95.04 MHz | +| | | 200 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 21$ dBm / 190.08 MHz | +| | | 400 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 24$ dBm / 380.16 MHz | +| | | | | +| | 480 | 400 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 24$ dBm / 380.16 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 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.3.5.5 Test requirement + +#### 8.3.5.5.1 Test requirement for BS type 1-O + +The fraction of incorrectly decoded UCI is shall be less than 1% for the SNR listed in table 8.3.5.5.1-1 and table 8.3.5.5.1-2. + +**Table 8.3.5.5.1-1: Required SNR for PUCCH format 4 with 15 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | 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 | + +**Table 8.3.5.5.1-2: Required SNR for PUCCH format 4 with 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | 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 | 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 | + +### 8.3.5.5.2 Test requirement for BS type 2-O + +The fraction of incorrectly decoded UCI is shall be less than 1% for the SNR listed in table 8.3.5.5.2-1 to table 8.3.5.5.2-4. + +**Table 8.3.5.5.2-1: Required SNR for PUCCH format 4 with 60 kHz SCS in FR2-1** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Additional DM-RS configuration | Channel bandwidth / SNR (dB) | | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|------------------------------|---------| +| | | | | | 50 MHz | 100 MHz | +| 1 | 2 | Normal | TDLA30-300 Low | No additional DM-RS | 3.6 | 3.3 | +| | | | | Additional DM-RS | 3.7 | 4.1 | + +**Table 8.3.5.5.2-2: Required SNR for PUCCH format 4 with 120 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Additional DM-RS configuration | Channel bandwidth / SNR (dB) | | | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|------------------------------|---------|---------| +| | | | | | 50 MHz | 100 MHz | 200 MHz | +| 1 | 2 | Normal | TDLA30-300 Low | No additional DM-RS | 3.4 | 3.4 | 4.1 | +| | | | | Additional DM-RS | 4.2 | 4.4 | 3.8 | + +**Table 8.3.5.5.2-3: Required SNR for PUCCH format 4 with 120 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Number of PRBs | Additional DM-RS configuration | Channel bandwidth / SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|----------------|--------------------------------|------------------------------| +| | | | | | | 100 MHz | +| 1 | 2 | Normal | TDLA30-650 Low | 1 | No additional DM-RS | 3.6 | +| | | | | | Additional DM-RS | 3.6 | +| 1 | 2 | Normal | TDLA30-650 Low | 16 | No additional DM-RS | -8.4 | +| | | | | | Additional DM-RS | -8.3 | + +**Table 8.3.5.5.2-4: Required SNR for PUCCH format 4 with 480 kHz SCS in FR2-2** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Number of PRBs | Additional DM-RS configuration | Channel bandwidth / SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|----------------|--------------------------------|------------------------------| +| | | | | | | 400 MHz | +| 1 | 2 | Normal | TDLA10-650 Low | 1 | No additional DM-RS | 4.2 | +| | | | | | Additional DM-RS | 4 | +| 1 | 2 | Normal | TDLA10-650 Low | 16 | No additional DM-RS | -8.5 | +| | | | | | Additional DM-RS | -8.4 | + +## 8.3.6 Performance requirements for multi-slot PUCCH format + +### 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 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 BS is based on the test applicability rules defined in clause 8.1.2.2. + +##### 8.3.6.1.1.2 Minimum Requirement + +For BS *type I-O*, the minimum requirement is in TS 38.104 [2], clause 11.3.1.7. + +##### 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 + +Direction to be tested: OTA REFSENS *receiver target reference direction* (D.54). + +###### 8.3.6.1.1.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.3. +- 2) Align the manufacturer declared coordinate system orientation of the BS with the test system. +- 3) Set the BS 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 [20], and according to additional test parameters listed in table 8.3.6.1.1.4.2-1. + +**Table 8.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 | + +- 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 BS receiver is as specified in clause 8.3.6.1.1.5.1 for *BS type 1-O*, 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.3.6.1.1.4.2-2 + +**Table 8.3.6.1.1.4.2-2: AWGN power level at the BS input** + +| BS type | Subcarrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|-------------------------|--------------------------|-------------------------|------------------------------------------------------| +| BS type 1-O
(Note 4) | 15 kHz | 5 | $-83.5 - \Delta_{\text{OTAREFSENS}}$ dBm / 4.5 MHz | +| | | 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 1: $\Delta_{\text{OTAREFSENS}}$ as declared in D.53 in table 4.6-1 and clause 7.1. + +NOTE 2: Void. NOTE3: Void. + +NOTE 4: 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.. + +- 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.3.6.1.1.5 Test Requirement + +##### 8.3.6.1.1.5.1 Test Requirement for *BS 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.3.6.1.1.5.1-1. + +**Table 8.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 | Cyclic Prefix | Propagation conditions and correlation matrix (Annex J) | Channel bandwidth (MHz) / SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|------------------------------------| +| | | | | 40 MHz | +| 1 | 2 | Normal | TDLC-300-100 Low | -5.7 | + +#### 8.3.6.1.1.5.2 Void + +### 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 + +For *BS type I-O*, the minimum requirement is in TS 38.104 [2], clause 11.3.1.7. + +#### 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 (SC): M; see clause 4.9.1 + +Direction to be tested: OTA REFSENS *receiver target reference direction* (D.54). + +##### 8.3.6.1.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.3. +- 2) Align the manufacturer declared coordinate system orientation of the BS with the test system. +- 3) Set the BS 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 [20], and according to additional test parameters listed in table 8.3.6.1.2.4.2-1. + +**Table 8.3.6.1.2.4.2-1: Test Parameters for multi-slot PUCCH format 1** + +| Parameter | Value | +|---------------------------------------------------------|----------------------------------------| +| 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 | + +- 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 BS receiver is as specified in clause 8.3.6.1.2.5.1 for *BS type 1-O*, 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.3.6.1.2.4.2-2. + +**Table 8.3.6.1.2.4.2-2: AWGN power level at the BS input** + +| BS type | Subcarrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|-------------|--------------------------|-------------------------|------------------------------------------------------| +| BS type 1-O | 15 kHz | 5 | $-83.5 - \Delta_{\text{OTAREFSENS}}$ dBm / 4.5 MHz | +| | | 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 1: $\Delta_{\text{OTAREFSENS}}$ as declared in D.53 in table 4.6-1 and clause 7.1. +NOTE 2: Void. +NOTE 3: Void. + +- 8) The signal generator sends a test pattern with the pattern outlined in figure 8.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.3.6.1.2.4.2-1: Test signal pattern for PUCCH format 1 demodulation tests. The diagram shows a sequence of three 'ACK' boxes separated by idle periods, followed by an ellipsis indicating more repetitions.](a50bb96f2021602f9ef99fc8e5bb9915_img.jpg) + +Figure 8.3.6.1.2.4.2-1: Test signal pattern for PUCCH format 1 demodulation tests. The diagram shows a sequence of three 'ACK' boxes separated by idle periods, followed by an ellipsis indicating more repetitions. + +**Figure 8.3.6.1.2.4.2-1: Test signal pattern for PUCCH format 1 demodulation tests** + +8.3.6.1.2.5 Test Requirement + +8.3.6.1.2.5.1 Test Requirement for BS 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.3.6.1.2.5.1-1. + +**Table 8.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 | Cyclic Prefix | Propagation conditions and correlation matrix (Annex J) | Channel bandwidth (MHz) / SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|------------------------------------| +| | | | | 40 MHz | +| 1 | 2 | Normal | TDLC-300-100 Low | -7.0 | + +8.3.6.1.2.5.2 Void + +## 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 contains 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 + +For *BS type 1-O*, the minimum requirements are in TS 38.104 [2] clause 11.3.1.8 and 11.3.1.9. + +### 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. + +Direction to be tested: OTA REFSENS *receiver target reference direction* (see D.54 in table 4.6-1). + +#### 8.3.7.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.3. +- 2) Align the manufacturer declared coordinate system orientation of the BS with the test system. +- 3) Set the BS 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 [20] and according to additional test parameters listed in table 8.3.7.4.2-1. + +**Table 8.3.7.4.2-1: 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 15 KHz SCS and RBs 0, 5, 10, ..., 50 are allocated for 30 KHz SCS. | | + +- 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 BS receiver is as specified in clause 8.3.7.5.1 for *BS type 1-O*, 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 quoted in table 8.3.7.4.2-2. + +**Table 8.3.7.4.2-2: AWGN power level at the BS input** + +| BS type | Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|-------------------------|------------------------------------------------------| +| BS type 1-O (NOTE 2) | 15 | 20 | $-77.2 - \Delta_{\text{OTAREFSENS}}$ dBm / 19.08 MHz | +| | 30 | 20 | $-77.4 - \Delta_{\text{OTAREFSENS}}$ dBm / 18.36 MHz | +| NOTE 1: $\Delta_{\text{OTAREFSENS}}$ as declared in D.53 in table 4.6-1 and clause 7.1. | | | | +| NOTE 2: 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. | | | | + +- 8) 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 three rectangular boxes, each containing the text 'ACK', representing detected ACK signals. To the right of the third box are three dots (ellipsis), indicating a continuation of the pattern.](1bee321e63e7ca14df7e4a8f2f386ce5_img.jpg) + +Figure 8.3.7.4.2-1: Test signal pattern for single user interlaced PUCCH format 0 demodulation tests. The diagram shows three rectangular boxes, each containing the text 'ACK', representing detected ACK signals. To the right of the third box are three dots (ellipsis), indicating a continuation of the 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 + +### 8.3.7.5.1 Test requirement for *BS 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.3.7.5.1-1. + +**Table 8.3.7.5.1-1: Test requirements for interlaced PUCCH format 0 with 15 kHz SCS, 20 MHz channel bandwidth** + +| Number of Tx antennas | Number of RX antennas | Propagation conditions and correlation matrix (Annex J) | Number of OFDM symbols | SNR (dB) | +|-----------------------|-----------------------|---------------------------------------------------------|------------------------|----------| +| 1 | 2 | TDLA30-10 Low | 1 | -2.2 | + +**Table 8.3.7.5.1-2: Test requirements for interlaced PUCCH format 0 with 30 kHz SCS, 20.MHz channel bandwidth** + +| Number of Tx antennas | Number of RX antennas | Propagation conditions and correlation matrix (Annex J) | 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 + +For BS type 1-O, the minimum requirement is in TS 38.104 [2], clause 11.3.1.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 + +Direction to be tested: OTA REFSENS receiver target reference direction (see D.54 in table 4.6-1). + +##### 8.3.8.1.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.3. +- 2) Align the manufacturer declared coordinate system orientation of the BS with the test system. +- 3) Set the BS 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 [20], and according to additional test parameters listed in table 8.3.8.1.4.2-1. + +**Table 8.3.8.1.4.2-1: 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 15 KHz SCS and RBs 0, 5, 10, ..., 50 are allocated for 30 KHz SCS. | | + +- 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 BS receiver is as specified in clause 8.3.8.1.5.1 for BS type 1-O, 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.3.8.1.4.2-2. + +**Table 8.3.8.1.4.2-2: AWGN power level at the BS input** + +| BS type | Subcarrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|-------------------------|------------------------------------------------------| +| BS type 1-O
(NOTE 2) | 15 | 20 | $-77.2 - \Delta_{\text{OTAREFSENS}}$ dBm / 19.08 MHz | +| | 30 | 20 | $-77.4 - \Delta_{\text{OTAREFSENS}}$ dBm / 18.36 MHz | +| NOTE 1: $\Delta_{\text{OTAREFSENS}}$ as declared in D.53 in table 4.6-1 and clause 7.1. | | | | +| NOTE 2: 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. | | | | + +- 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.3.8.1.5 Test Requirement + +#### 8.3.8.1.5.1 Test Requirement for BS 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.3.8.1.5.1-1. + +**Table 8.3.8.1.5.1-1: Required SNR for interlaced PUCCH format 1 with 15 kHz SCS, 20 MHz channel bandwidth** + +| Number of Tx antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (Annex J) | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|----------| +| 1 | 2 | Normal | TDLA30-10 Low | -13.2 | + +**Table 8.3.8.1.5.1-2: Required SNR for interlaced PUCCH format 1 with 30 kHz SCS, 20 MHz channel bandwidth** + +| Number of Tx antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (Annex J) | 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 + +For BS type 1-O, the minimum requirement is in TS 38.104 [2], clause 11.3.1.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: 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.3.8.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.3. +- 2) Align the manufacturer declared coordinate system orientation of the BS with the test system. +- 3) Set the BS 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 [20], and according to additional test parameters listed in table 8.3.8.2.4.2-1. + +**Table 8.3.8.2.4.2-1: 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 15 KHz SCS and
RBs 0, 5, 10, ..., 50 are allocated for 30 KHz SCS. | | + +- 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 BS receiver is as specified in clause 8.3.8.2.5.1 for BS type 1-O, 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.3.8.2.4.2-2. + +**Table 8.3.8.2.4.2-2: AWGN power level at the BS input** + +| BS type | Subcarrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|-------------------------|------------------------------------------------------| +| BS type 1-O
(NOTE 2) | 15 | 20 | $-77.2 - \Delta_{\text{OTAREFSENS}}$ dBm / 19.08 MHz | +| | 30 | 20 | $-77.4 - \Delta_{\text{OTAREFSENS}}$ dBm / 18.36 MHz | +| NOTE 1: $\Delta_{\text{OTAREFSENS}}$ as declared in D.53 in table 4.6-1 and clause 7.1. | | | | +| NOTE 2: 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. | | | | + +- 8) 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 + +#### 8.3.8.2.5.1 Test Requirement for BS 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.3.8.2.5-1. + +**Table 8.3.8.2.5.1-1: Required SNR for interlaced PUCCH format 1 with 15 kHz SCS, 20 MHz channel bandwidth** + +| Number of Tx antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (Annex J) | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|----------| +| 1 | 2 | Normal | TDLA30-10 Low | -13.8 | + +**Table 8.3.8.2.5.1-2: Required SNR for interlaced PUCCH format 1 with 30 kHz SCS, 20 MHz channel bandwidth** + +| Number of Tx antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (Annex J) | 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. + +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. + +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 + +For BS type 1-O, the minimum requirement is in TS 38.104 [2] clause 11.3.1.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 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.3.9.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.3. +- 2) Align the manufacturer declared coordinate system orientation of the BS with the test system. +- 3) Set the BS 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 one polarization of the test antenna(s). +- 5) The characteristics of the wanted signal shall be configured according to TS 38.211 [20], and according to additional test parameters listed in table 8.3.9.4.2-1. + +**Table 8.3.9.4.2-1: 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 15 KHz SCS and RBs 0, 5, 10,...,50 are allocated for 30 KHz SCS | | + +- 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 BS receiver is as specified in clause 8.3.9.5 for *BS type 1-O*, 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.3.9.4.2-2. + +**Table 8.3.9.4.2-2: AWGN power level at the BS input** + +| BS type | Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|-------------------------|-----------------------------------------------| +| BS type 1-O | 15 kHz | 20 | $-77.2 - \Delta_{OTAREFSENS}$ dBm / 19.08 MHz | +| BS type 1-O | 30 kHz | 20 | $-77.4 - \Delta_{OTAREFSENS}$ dBm / 18.36 MHz | +| NOTE 1: $\Delta_{OTAREFSENS}$ as declared in D.53 in table 4.6-1 and clause 7.1. | | | | +| NOTE 2: 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. | | | | + +- 8) The signal generator sends a test pattern with 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', representing the signal pattern. To the right of the third box are three dots, indicating the pattern continues.](a7c4c4e8cc0302c649dc4e9476d97372_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', representing the signal pattern. To the right of the third box are three dots, indicating the pattern continues. + +**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 demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (Annex J) | 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 demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (Annex J) | 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 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. + +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 + +For BS type I-O, the minimum requirement is in TS 38.104 [2] clause 11.3.1.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 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.3.10.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.3. +- 2) Align the manufacturer declared coordinate system orientation of the BS with the test system. +- 3) Set the BS 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 one polarization of the test antenna(s). +- 5) The characteristics of the wanted signal shall be configured according to TS 38.211 [20], and according to additional test parameters listed in table 8.3.10.4.2-1. + +**Table 8.3.10.4.2-1: 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 15 KHz SCS and RBs 0,5,10,...,45 are allocated for 30 KHz SCS | | + +- 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 BS receiver is as specified in clause 8.3.10.5 for *BS type 1-O*, 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.3.10.4.2-2. + +**Table 8.3.10.4.2-2: AWGN power level at the BS input** + +| BS type | Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|-------------------------|------------------------------------------------------| +| BS type 1-O | 15 kHz | 20 | $-77.2 - \Delta_{\text{OTAREFSENS}}$ dBm / 19.08 MHz | +| BS type 1-O | 30 kHz | 20 | $-77.4 - \Delta_{\text{OTAREFSENS}}$ dBm / 18.36 MHz | +| NOTE 1: $\Delta_{\text{OTAREFSENS}}$ as declared in D.53 in table 4.6-1 and clause 7.1. | | | | +| NOTE 2: 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. | | | | + +- 8) The signal generator sends a test pattern with pattern outlined in figure 8.3.10.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.3.10.4.2-1: Test signal pattern for interlaced PUCCH format 3 demodulation tests. The diagram shows three boxes labeled 'ACK' followed by three dots, representing a sequence of ACK signals.](bd0102d6e3d91c70d57762f2c33904bf_img.jpg) + +Figure 8.3.10.4.2-1: Test signal pattern for interlaced PUCCH format 3 demodulation tests. The diagram shows three boxes labeled 'ACK' followed by three dots, representing a sequence of ACK signals. + +**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-1 and table 8.3.10.5.1-2. + +**Table 8.3.10.5.1-1: Required SNR for interlaced PUCCH format 3 with 15 kHz SCS, 20 MHz channel bandwidth** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (Annex J) | AdditionalDM-RS configuration | SNR(dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|-------------------------------|---------| +| 1 | 2 | Normal | TDLA30-10 Low | No additional DM-RS | -5.4 | + +**Table 8.3.10.5.1-2: Required SNR for interlaced PUCCH format 3 with 30 kHz SCS, 20 MHz channel bandwidth** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (Annex J) | 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 PUCCH sub-slot based repetition 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 probability performance requirement only apply to PUCCH format 0 with 1 UCI bit. The UCI information only contain ACK information. + +The 1bit UCI information is further defined with the bitmap as [1]. + +The transient period as specified in TS 38.101-1 [24] clause 6.3.3.1 and TS 38.101-2 [25] 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.11.2 Minimum Requirement + +For *BS type 1-O*, the minimum requirements are in TS 38.104 [2] clause 11.3.1.10. + +### 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. + +Direction to be tested: OTA REFSENS *receiver target reference direction* (see D.54 in table 4.6-1). + +#### 8.3.11.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.3. +- 2) Align the manufacturer declared coordinate system orientation of the BS with the test system. +- 3) Set the BS 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 [20] and according to additional test parameters listed in table 8.3.11.4.2-1. + +**Table 8.3.11.4.2-1: Test parameters** + +| Parameter | Test | +|--------------------------------------------------------------------|-------------------------------------------------| +| Number of UCI information bits | 1 | +| Number of PRBs | 1 | +| Number of PUCCH symbols
( nrofSymobls ) | 2 | +| Number of PUCCH sub-slot based 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 | + +- 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 BS receiver is as specified in clause 8.3.11.5.1 for *BS type 1-O*, 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 quoted in table 8.3.11.4.2-2. + +**Table 8.3.11.4.2-2: AWGN power level at the BS input** + +| BS type | Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|----------------------|---------------------------|-------------------------|-----------------------------------------------------| +| BS type 1-O (Note 2) | 30 | 10 | $-80.6 - \Delta_{\text{OTAREFSENS}}$ dBm / 8.64 MHz | + +NOTE 1: $\Delta_{\text{OTAREFSENS}}$ as declared in D.53 in table 4.6-1 and clause 7.1. +NOTE 2: 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. + +- 8) 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 detected ACK signals. To the right of the third box are three dots, indicating a sequence of such ACK signals.](3e719a8e608ad16194d4878e2d4fe35b_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 detected ACK signals. To the right of the third box are three dots, indicating a sequence of such ACK signals. + +**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 + +### 8.3.11.5.1 Test requirement for BS 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.3.11.5.1-1. + +**Table 8.3.11.5.1-1: Test requirements for PUCCH sub-slot repetition format 0 and 30 kHz SCS, 10 MHz channel bandwidth** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | 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 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.12.1.2 Minimum Requirement + +For BS type 1-O, the minimum requirement is in TS 38.104 [2], clause 11.3.1.8. + +For BS type 2-O, the minimum requirement is in TS 38.104 [2], clause 11.3.2.7. + +### 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. + +Direction to be tested: OTA REFSENS receiver target reference direction (see D.54 in table 4.6-1). + +#### 8.3.12.1.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.3. +- 2) Align the manufacturer declared coordinate system orientation of the BS with the test system. +- 3) Set the BS 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 [20], and according to additional test parameters listed in table 8.3.12.1.4.2-1. + +**Table 8.3.12.1.4.2-1: 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
60/120 kHz SCS: DDSUU, S=10D:2G:2U or
DSUUU, S=10D:2G:2U | | +| 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. | | + +- 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 BS receiver is as specified in clause 8.3.12.1.5.1 and 8.3.12.1.5.2 for BS type 1-O and BS 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.3.12.1.4.2-2 + +**Table 8.3.12.1.4.2-2: AWGN power level at the BS input** + +| BS type | Subcarrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|-------------------------|--------------------------|-------------------------|--------------------------------------------------------------------------------------------------------| +| BS type 1-O
(Note 4) | 15 kHz | 5 | $-83.5 - \Delta_{\text{OTAREFSENS}}$ dBm / 4.5 MHz | +| | 30 kHz | 10 | $-80.6 - \Delta_{\text{OTAREFSENS}}$ dBm / 8.64 MHz | +| BS type 2-O
(Note 5) | 60 kHz | 50 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 15 \text{ dBm} / 47.52 \text{ MHz}$ | +| | 120 kHz | 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. + +NOTE 4: 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. + +NOTE 5: The AWGN power level contains an AWGN offset of 15dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 15dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. + +- 8) The signal generator sends random codewords 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 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.1.5 Test Requirement + +#### 8.3.12.1.5.1 Test Requirement for BS 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.3.12.1.5.1-1 and table 8.3.12.1.5.1-2. + +**Table 8.3.12.1.5.1-1: Minimum requirements for PUCCH format 1 with DM-RS bundling with 15 kHz SCS** + +| Test Number | Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Channel bandwidth / SNR (dB) | +|-------------|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------------------------------| +| | | | | | 5 MHz | +| 1 | 1 | 2 | Normal | TDLA30-10 | -2.4 | +| 2 | 1 | 2 | Normal | TDLA30-10 | -8.5 | + +**Table 8.3.12.1.5.1-2: Minimum requirements for PUCCH format 1 with DM-RS bundling with 30 kHz SCS** + +| Test Number | Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Channel bandwidth / SNR (dB) | +|-------------|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------------------------------| +| | | | | | 10 MHz | +| 1 | 1 | 2 | Normal | TDLA30-10 | -2.4 | +| 2 | 1 | 2 | Normal | TDLA30-10 | -8.1 | + +#### 8.3.12.1.5.2 Test Requirement for BS 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.3.12.1.5.2-1 and table 8.3.12.1.5.2-2. + +**Table 8.3.12.1.5.2-1: Minimum requirements for PUCCH format 1 with DM-RS bundling with 60 kHz SCS** + +| Test Number | Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex G) | Channel bandwidth / SNR (dB) | +|-------------|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------------------------------| +| | | | | | 50 MHz | +| 1 | 1 | 2 | Normal | TDLA30-10 | -2.7 | + +**Table 8.3.12.1.5.2-2: Minimum requirements for PUCCH format 1 with DM-RS bundling with 120 kHz SCS** + +| Test Number | Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex G) | Channel bandwidth / SNR (dB) | +|-------------|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------------------------------| +| | | | | | 50 MHz | +| 1 | 1 | 2 | Normal | TDLA30-75 | -2.6 | + +### 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. + +Which specific test(s) are applicable to BS is based on the test applicability rules defined in clause 8.1.2. + +#### 8.3.12.2.2 Minimum Requirement + +For BS type 1-O, the minimum requirement is in TS 38.104 [2], clause 11.3.1.8. + +For BS type 2-O, the minimum requirement is in TS 38.104 [2], clause 11.3.2.7. + +#### 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. + +Direction to be tested: OTA REFSENS receiver target reference direction (see D.54 in table 4.6-1). + +##### 8.3.12.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.3. +- 2) Align the manufacturer declared coordinate system orientation of the BS with the test system. +- 3) Set the BS 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 [20], and according to additional test parameters listed in table 8.3.12.2.4.2-1. + +**Table 8.3.12.2.4.2-1: 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
60/120 kHz SCS: DDSUU, S=10D:2G:2U or
DSUUU, S=10D:2G:2U | | +| 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. | | + +- 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 BS receiver is as specified in clause 8.3.12.2.5-1 and 8.3.12.2.5-2 for BS type 1-O and BS 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.3.12.2.4.2-2. + +**Table 8.3.12.2.4.2-2: AWGN power level at the BS input** + +| BS type | Subcarrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|-------------------------|--------------------------|-------------------------|--------------------------------------------------------------------------------------------------------| +| BS type 1-O
(Note 4) | 15 kHz | 5 | $-83.5 - \Delta_{\text{OTAREFSENS}}$ dBm / 4.5 MHz | +| | 30 kHz | 10 | $-80.6 - \Delta_{\text{OTAREFSENS}}$ dBm / 8.64 MHz | +| BS type 2-O
(Note 5) | 60 kHz | 50 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 15 \text{ dBm} / 47.52 \text{ MHz}$ | +| | 120 kHz | 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. + +NOTE 4: 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. + +NOTE 5: The AWGN power level contains an AWGN offset of 15dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 15dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. + +- 8) 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 + +#### 8.3.12.2.5.1 Test Requirement for BS 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.3.12.2.5.1-1 and table 8.3.12.2.5.1-2. + +**Table 8.3.12.2.5.1-1: Minimum requirements for PUCCH format 1 with DM-RS bundling with 15 kHz SCS** + +| Test Number | Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | 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.1-2: Minimum requirements for PUCCH format 1 with DM-RS bundling with 30 kHz SCS** + +| Test Number | Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Channel bandwidth / SNR (dB) | +|-------------|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------------------------------| +| | | | | | 10 MHz | +| 1 | 1 | 2 | Normal | TDLA30-10 | -3.2 | +| 2 | 1 | 2 | Normal | TDLA30-10 | -7.9 | + +#### 8.3.12.2.5.2 Test Requirement for BS 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 table 8.3.12.2.5.2-1 and table 8.3.12.2.5.2-2. + +**Table 8.3.12.2.5.2-1: Minimum requirements for PUCCH format 1 with DM-RS bundling with 60 kHz SCS** + +| Test Number | Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Channel bandwidth / SNR (dB) | +|-------------|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------------------------------| +| | | | | | 50 MHz | +| 1 | 1 | 2 | Normal | TDLA30-10 | -4.2 | + +**Table 8.3.12.2.5.2-2: Minimum requirements for PUCCH format 1 with DM-RS bundling with 120 kHz SCS** + +| Test Number | Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Channel bandwidth / SNR (dB) | +|-------------|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------------------------------| +| | | | | | 50 MHz | +| 1 | 1 | 2 | Normal | TDLA30-75 | -4.3 | + +### 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.2. + +### 8.3.13.2 Minimum requirement + +For BS type 1-O, the minimum requirement is in TS 38.104 [2], clause 11.3.1.9. + +For BS type 2-O, the minimum requirement is in TS 38.104 [2], clause 11.3.2.10. + +### 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 + +Direction to be tested: OTA REFSENS *receiver target reference direction* (see D.54 in table.4.6-1). + +#### 8.3.13.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.3. +- 2) Align the manufacturer declared coordinate system orientation of the BS with the test system. +- 3) Set the BS 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 one polarization of the test antenna(s). +- 5) The characteristics of the wanted signal shall be configured according to TS 38.211 [20], and according to additional test parameters listed in table 8.3.13.4.2-1. + +**Table 8.3.13.4.2-1: 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
60/120 kHz SCS: DDSUU, S=10D:2G:2U or
DSUUU, S=10D:2G:2U | | +| 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 | +| 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. | | + +- 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 BS receiver is as specified in clause 8.3.13.5.1 and 8.3.13.5.2 for *BS type 1-O* and *BS type 2-O* respectively, and 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.3.13.4.2-2. + +**Table 8.3.13.4.2-2: AWGN power level at the BS input** + +| BS type | Subcarrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|-------------------------|--------------------------|-------------------------|--------------------------------------------------------------------------------------------------------| +| BS type 1-O
(Note 4) | 15 kHz | 5 | $-83.5 - \Delta_{\text{OTAREFSENS}}$ dBm / 4.5 MHz | +| | 30 kHz | 10 | $-80.6 - \Delta_{\text{OTAREFSENS}}$ dBm / 8.64 MHz | +| BS type 2-O
(Note 5) | 60 kHz | 50 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 15 \text{ dBm} / 47.52 \text{ MHz}$ | +| | 120 kHz | 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. +NOTE 4: 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. +NOTE 5: The AWGN power level contains an AWGN offset of 15dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 15dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. + +- 8) 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.13.5 Test requirement + +#### 8.3.13.5.1 Test Requirement for BS 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.3.13.5.1-1 and table 8.3.13.5.1-2. + +**Table 8.3.13.5.1-1: Required SNR for PUCCH format 3 with 15 kHz SCS** + +| Test Number | Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | 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.1-2: Required SNR for PUCCH format 3 with 30 kHz SCS** + +| Test Number | Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | 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.3.13.5.2 Test Requirement for BS 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 table 8.3.13.5.2-1 and table 8.3.13.5.2-2. + +**Table 8.3.13.5.2-1: Required SNR for PUCCH format 3 with 60 kHz SCS** + +| Test Number | Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Additional DM-RS configuration | Channel bandwidth / SNR (dB) | +|-------------|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|------------------------------| +| | | | | | | 50 MHz | +| 1 | 1 | 2 | Normal | TDLA30-75 Low | No Additional DM-RS | 0.7 | +| 2 | 1 | 2 | Normal | TDLA30-75 Low | Additional DM-RS | 0.4 | + +**Table 8.3.13.5.2-2: Required SNR for PUCCH format 3 with 120 kHz SCS** + +| Test Number | Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (annex J) | Additional DM-RS configuration | Channel bandwidth / SNR (dB) | +|-------------|-----------------------|---------------------------------|---------------|---------------------------------------------------------|--------------------------------|------------------------------| +| | | | | | | 50 MHz | +| 1 | 1 | 2 | Normal | TDLA30-75 Low | No Additional DM-RS | 1.3 | +| 2 | 1 | 2 | Normal | TDLA30-75 Low | Additional DM-RS | 0.5 | + +## 8.4 OTA 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, TDLC300-100, TDLA30-10, TDLA30-300, TDLA30-650, and TDLA10-650, 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, TDLC300-100, TDLA30-10, TDLA30-300, TDLA30-650 and TDLA10-650** + +| PRACH
preamble | PRACH
SCS
(kHz) | Time error tolerance | | | | | | +|---------------------------|-----------------------|----------------------|-------------|-----------|------------|------------|------------| +| | | AWGN | TDLC300-100 | TDLA30-10 | TDLA30-300 | TDLA30-650 | TDLA10-650 | +| 0 | 1.25 | 1.04 us | 2.55 us | N/A | N/A | N/A | N/A | +| A1, A2, A3,
B4, C0, C2 | 15 | 0.52 us | 2.03 us | 0.67 us | N/A | N/A | N/A | +| | 30 | 0.26 us | 1.77 us | 0.41 us | N/A | N/A | N/A | +| | 60 (FR2) | 0.13 us | N/A | N/A | 0.28 us | N/A | N/A | +| | 120 | 0.07 us | N/A | N/A | 0.22 us | 0.22 us | N/A | +| | 480 | 18 ns | N/A | N/A | N/A | N/A | 68 ns | + +The test preambles for normal mode are listed in table A.6-1 and A.6-2. 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. + +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-1 to 8.4.1.6.1-4 and table 8.4.1.6.2-1) are optional, and only applicable for FR2-1 below 30 GHz. The test preambles for PRACH with $L_{RA}=1151$ and $L_{RA}=571$ are listed in table A.6-6. + +#### 8.4.1.2 Minimum requirement + +For BS type 1-O, the minimum requirement is in TS 38.104 [2] clause 11.4.1.1 and 11.4.1.2. + +For BS type 2-O, the minimum requirement is in TS 38.104 [2] clause 11.4.2.1 and 11.4.2.2. + +#### 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 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.4.1.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.3. +- 2) Align the manufacturer declared coordinate system orientation of the BS with the test system. +- 3) Set the BS 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 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.4.1.4.2-1. + +**Table 8.4.1.4.2-1: AWGN power level at the BS input** + +| BS type | Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|----------------------|---------------------------|-------------------------|---------------------------------------------------------------------------------------------------------| +| BS type 1-O (Note 4) | 15 | 5 | $-83.5 - \Delta_{\text{OTAREFSENS}}$ dBm / 4.5MHz | +| | | 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 | +| BS type 2-O (Note 5) | 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}$ | +| | | 400 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 24 \text{ dBm} / 380.16 \text{ MHz}$ | +| | 480 | 400 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 24 \text{ dBm} / 380.16 \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. + +NOTE 4: 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. + +NOTE 5: The AWGN power level contains an AWGN offset of 15dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 15dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. + +- 8) Adjust the frequency offset of the test signal according to table 8.4.1.5.1-1 or 8.4.1.5.1-2 or 8.4.1.5.1-3 or 8.4.1.6.1-1 or 8.4.1.6.1-2 or 8.4.1.6.1-3 or 8.4.1.6.1-4 or 8.4.1.5.2-1 or 8.4.1.5.2-2 or 8.4.1.5.2-3 or 8.4.1.5.2-4 or 8.4.1.5.2-5 or 8.4.1.7.1-1 or 8.4.1.7.1-2 or 8.4.1.6.2-1 or 8.4.1.7.x-1 or 8.4.1.7.x-2 or 8.4.1.7.x-3. +- 9) Adjust the equipment so that the SNR specified in table 8.4.1.5.1-1 or 8.4.1.5.1-2 or 8.4.1.5.1-3 or 8.4.1.6.1-1 or 8.4.1.6.1-2 or 8.4.1.6.1-3 or 8.4.1.6.1-4 or 8.4.1.5.2-1 or 8.4.1.5.2-2 or 8.4.1.5.2-3 or 8.4.1.5.2-4 or 8.4.1.5.2-5 or 8.4.1.7.1-1 or 8.4.1.7.1-2 or 8.4.1.6.2-1 or 8.4.1.7.x-1 or 8.4.1.7.x-2 or 8.4.1.7.x-3 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.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 repeating pattern.](e8ceb2500b8a99cd4d677554b974a3f4_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 repeating pattern. + +**Figure 8.4.1.4.2-1: PRACH preamble test pattern** + +Unless otherwise stated, the timing offset base value for PRACH preamble format 0 is set to 50% of $N_{\text{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 Ncs. The timing offset scheme for PRACH preamble format 0 is presented in Figure 8.4.1.4.2-2. + +![Figure 8.4.1.4.2-2: Timing offset scheme for PRACH preamble format 0. The diagram shows a horizontal timeline with 10 equal segments. A curved arrow at the top points from the start of the first segment to the start of the tenth segment. Vertical lines with downward-pointing arrows mark the boundaries between segments, starting from the second segment.](ec9101c0a733cc6b8240c5ade9a04754_img.jpg) + +Figure 8.4.1.4.2-2: Timing offset scheme for PRACH preamble format 0. The diagram shows a horizontal timeline with 10 equal segments. A curved arrow at the top points from the start of the first segment to the start of the tenth segment. Vertical lines with downward-pointing arrows mark the boundaries between segments, starting from the second segment. + +**Figure 8.4.1.4.2-2: Timing offset scheme for PRACH preamble format 0** + +Unless otherwise stated, 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.4.1.4.2-3 for 15 kHz, 30 kHz, 60 kHz, and 120 kHz SCS. + +![Figure 8.4.1.4.2-3: Timing offset scheme for PRACH preamble format A1, A2, A3, B4, C0 and C2 using 15 kHz, 30 kHz, 60 kHz, and 120 kHz SCS. The diagram shows a horizontal timeline with 10 equal segments. A curved arrow at the top points from the start of the first segment to the start of the tenth segment. Vertical lines with downward-pointing arrows mark the boundaries between segments, starting from the second segment.](53c60f255aa58c330efd23c77dfdc762_img.jpg) + +Figure 8.4.1.4.2-3: Timing offset scheme for PRACH preamble format A1, A2, A3, B4, C0 and C2 using 15 kHz, 30 kHz, 60 kHz, and 120 kHz SCS. The diagram shows a horizontal timeline with 10 equal segments. A curved arrow at the top points from the start of the first segment to the start of the tenth segment. Vertical lines with downward-pointing arrows mark the boundaries between segments, starting from the second segment. + +**Figure 8.4.1.4.2-3: Timing offset scheme for PRACH preamble format A1, A2, A3, B4, C0 and C2 using 15 kHz, 30 kHz, 60 kHz, and 120 kHz SCS** + +For test requirement specified in Table 8.4.1.6.2-1, the timing offset base value for PRACH preamble format C2 is set to 0. This offset is increased within the loop, by adding in each step a value of 0.48us, until the end of the tested range, which is 4.8us. Then the loop is being reset and the timing offset is set again to 0. The timing offset scheme for PRACH preamble format C2 is presented in Figure 8.4.1.4.2-4. + +![Figure 8.4.1.4.2-4: Timing offset scheme for PRACH preamble format C2. The diagram shows a horizontal timeline with 10 segments. Above the timeline, the start of each segment is labeled with a timing offset value: 0us, 0.48us, 0.96us, 1.44us, 1.92us, 2.4us, 2.88us, 3.36us, 3.84us, 4.32us, and 4.8us. A curved arrow at the top points from the start of the first segment to the start of the tenth segment. Vertical lines with downward-pointing arrows mark the boundaries between segments, starting from the second segment.](4e4a4519e08d677bc4a0dab3dc816f05_img.jpg) + +Figure 8.4.1.4.2-4: Timing offset scheme for PRACH preamble format C2. The diagram shows a horizontal timeline with 10 segments. Above the timeline, the start of each segment is labeled with a timing offset value: 0us, 0.48us, 0.96us, 1.44us, 1.92us, 2.4us, 2.88us, 3.36us, 3.84us, 4.32us, and 4.8us. A curved arrow at the top points from the start of the first segment to the start of the tenth segment. Vertical lines with downward-pointing arrows mark the boundaries between segments, starting from the second segment. + +**Figure 8.4.1.4.2-4: Timing offset scheme for PRACH preamble format C2** + +For test requirements with 480 kHz SCS, the timing offset base value for PRACH preamble format A2, B4, 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.4us. Then the loop is being reset and the timing offset is set again to 0. The timing offset scheme for PRACH preamble format A2, B4, and C2 is presented in Figure 8.4.1.4.2-5. + +![Timing offset scheme diagram for PRACH preamble format A2, B4, and C2 using 480 kHz SCS. The diagram shows a horizontal timeline with four tick marks labeled 0us, 0.1us, 0.2us, 0.3us, and 0.4us. Above the timeline, a semi-circular arc connects the 0us and 0.4us marks. Below the timeline, four inverted semi-circular arcs are drawn, each starting at one of the tick marks (0us, 0.1us, 0.2us, 0.3us) and ending at the next tick mark.](e97277b95d25bb9cfe8581800948ddeb_img.jpg) + +Timing offset scheme diagram for PRACH preamble format A2, B4, and C2 using 480 kHz SCS. The diagram shows a horizontal timeline with four tick marks labeled 0us, 0.1us, 0.2us, 0.3us, and 0.4us. Above the timeline, a semi-circular arc connects the 0us and 0.4us marks. Below the timeline, four inverted semi-circular arcs are drawn, each starting at one of the tick marks (0us, 0.1us, 0.2us, 0.3us) and ending at the next tick mark. + +**Figure 8.4.1.4.2-5: Timing offset scheme for PRACH preamble format A2, B4, and C2 using 480 kHz SCS** + +#### 8.4.1.5 Test requirement for Normal Mode + +##### 8.4.1.5.1 Test requirement for BS type 1-O + +Pfa shall not exceed 0.1%. Pd shall not be below 99% for the SNRs in tables 8.4.1.5.1-1 to 8.4.1.5.1-3. + +**Table 8.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.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.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 | + +Table 8.4.1.5.1-4: Void + +Table 8.4.1.5.1-5: Void + +## 8.4.1.5.2 Test requirement for BS type 2-O + +Pfa shall not exceed 0.1%. Pd shall not be below 99% for the SNRs in tables 8.4.1.5.2-1 to 8.4.1.5.2-4. + +Table 8.4.1.5.2-1: PRACH missed detection test requirements for Normal Mode, 60 kHz SCS in FR2-1 + +| 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.4.1.5.2-2: PRACH missed detection test requirements for Normal Mode, 120 kHz SCS in FR2-1 + +| 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 | + +Table 8.4.1.5.2-3: PRACH missed detection test requirements for Normal Mode, 120 kHz SCS in FR2-2 + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex J) | Frequency offset | SNR (dB) | | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------|-----------------|-----------------|-----------------| +| | | | | Burst format A2 | Burst format B4 | Burst format C2 | +| 1 | 2 | AWGN | 0 | -11.5 | -15.7 | -11.5 | +| | | TDLA30-650 Low | 7100 | -3.4 | -6.7 | -3.6 | + +Table 8.4.1.5.2-4: PRACH missed detection test requirements for Normal Mode, 480 kHz SCS in FR2-2 + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex J) | Frequency offset | SNR (dB) | | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------|-----------------|-----------------|-----------------| +| | | | | Burst format A2 | Burst format B4 | Burst format C2 | +| 1 | 2 | AWGN | 0 | -11.4 | -15.6 | -11.5 | +| | | TDLA10-650 Low | 7100 | -3.9 | -8.7 | -3.9 | + +#### 8.4.1.6 Test requirement for high speed train + +##### 8.4.1.6.1 Test requirement for BS type 1-O + +Pfa shall not exceed 0.1%. Pd shall not be below 99% for the SNRs in tables 8.4.1.6.1-1 to 8.4.1.6.1-4. + +**Table 8.4.1.6.1-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 demodulation branches | Propagation conditions and correlation matrix (annex J) | 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 | + +**Table 8.4.1.6.1-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 demodulation branches | Propagation conditions and correlation matrix (annex J) | 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 | + +**Table 8.4.1.6.1-3: PRACH missed detection requirements for high speed train, 15 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex J) | Frequency offset | SNR (dB) | | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------|-----------------|-----------------|-----------------| +| | | | | Burst format A2 | Burst format B4 | Burst format C2 | +| 1 | 2 | AWGN | 1740 Hz | -11.0 | -14.0 | -10.8 | + +**Table 8.4.1.6.1-4: PRACH missed detection requirements for high speed train, 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex J) | Frequency offset | SNR (dB) | | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------|-----------------|-----------------|-----------------| +| | | | | Burst format A2 | Burst format B4 | Burst format C2 | +| 1 | 2 | AWGN | 3334 Hz | -10.9 | -14.3 | -10.7 | + +##### 8.4.1.6.2 Test requirement for BS type 2-O + +Pfa shall not exceed 0.1%. Pd shall not be below 99% for the SNRs in Table 8.4.1.6.2-1. + +**Table 8.4.1.6.2-1: PRACH missed detection requirements for high speed train, 120 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Propagation conditions (Annex J) | Frequency offset | SNR (dB) | +|-----------------------|-----------------------|----------------------------------|------------------|-----------------| +| | | | | Burst format C2 | +| 1 | 2 | AWGN | 19444 Hz | -9.8 | + +#### 8.4.1.7 Test requirement for PRACH with $L_{RA}=1151$ and $L_{RA}=571$ + +##### 8.4.1.7.1 Test requirement for BS type 1-O + +Pfa shall not exceed 0.1%. Pd shall not be below 99% for the SNRs in tables 8.4.1.7.1-1 to 8.4.1.7.1-2. + +**Table 8.4.1.7.1-1: Missed detection requirements for PRACH with $L_{RA}=1151$ , 15 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex J) | 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.1-2: Missed detection requirements for PRACH with $L_{RA}=571$ , 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex J) | 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 | + +#### 8.4.1.7.2 Test requirement for BS type 2-O + +Pfa shall not exceed 0.1%. Pd shall not be below 99% for the SNRs in tables 8.4.1.7.2-1 to 8.4.1.7.2-3. + +**Table 8.4.1.7.2-1: Missed detection requirements for PRACH with $L_{RA}=571$ , 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex J) | Frequency offset | SNR (dB) | | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------|-----------------|-----------------|-----------------| +| | | | | Burst format A2 | Burst format B4 | Burst format C2 | +| 1 | 2 | AWGN | 0 | -17.6 | -21.8 | -17.6 | +| | | TDLA30-650 Low | 7100 | -10.3 | -13.2 | -10.1 | + +**Table 8.4.1.7.2-2: Missed detection requirements for PRACH with $L_{RA}=1151$ , 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex J) | Frequency offset | SNR (dB) | | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------|-----------------|-----------------|-----------------| +| | | | | Burst format A2 | Burst format B4 | Burst format C2 | +| 1 | 2 | AWGN | 0 | -20.6 | -24.7 | -20.5 | +| | | TDLA30-650 Low | 7100 | -13.4 | -16.3 | -13.4 | + +**Table 8.4.1.7.2-3: Missed detection requirements for PRACH with $L_{RA}=571$ , 480 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex J) | Frequency offset | SNR (dB) | | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------|-----------------|-----------------|-----------------| +| | | | | Burst format A2 | Burst format B4 | Burst format C2 | +| 1 | 2 | AWGN | 0 | -17.6 | -21.7 | -17.6 | +| | | TDLA10-650 Low | 7100 | -10.5 | -14.4 | -10.5 | + +--- + +## Annex A (normative): Reference measurement channels + +### A.1 Fixed Reference Channels for OTA sensitivity, OTA reference sensitivity level, OTA ACS, OTA in-band blocking, OTA out-of-band blocking, OTA receiver intermodulation and OTA in-channel selectivity (QPSK, $R=1/3$ ) + +The parameters for the reference measurement channels are specified in table A.1-1 for FR1 OTA sensitivity, OTA reference sensitivity level, OTA ACS, OTA in-band blocking, OTA out-of-band blocking, OTA receiver intermodulation and OTA in-channel selectivity. + +The parameters for the reference measurement channels are specified in table A.1-2 for FR2 OTA reference sensitivity level, OTA ACS, OTA in-band blocking, OTA out-of-band blocking, OTA receiver intermodulation and OTA in-channel selectivity. + +**Table A.1-1: FRC parameters for FR1 OTA sensitivity, OTA reference sensitivity level, OTA ACS, OTA in-band blocking, OTA out-of-band blocking, OTA receiver intermodulation and OTA 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 | +|-----------------------------------------------|------------|------------|------------|------------|------------|------------|------------|------------|------------| +| 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: 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 [20]. + +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 [19], clause 5.2.2. + +**Table A.1-1a: FRC parameters for band n96 OTA sensitivity, for BS Type 1-H** + +| 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 *l* = 2, *l* = 11 as per table 6.4.1.1.3-3 of TS 38.211 [20]. + +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^1$ in sub-clause 5.2.2 of TS 38.212 [19]. + +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}. + +**Table A.1-2: FRC parameters for FR2 OTA reference sensitivity level, OTA ACS, OTA in-band blocking, OTA out-of-band blocking, OTA receiver intermodulation and OTA in-channel selectivity** + +| Reference channel | G-FR2-A1-1 | G-FR2-A1-2 | G-FR2-A1-3 | G-FR2-A1-4 | G-FR2-A1-5 | +|-----------------------------------------------|------------|------------|------------|------------|------------| +| Subcarrier spacing (kHz) | 60 | 120 | 120 | 60 | 120 | +| Allocated resource blocks | 66 | 32 | 66 | 33 | 16 | +| CP-OFDM Symbols per slot (Note 1) | 12 | 12 | 12 | 12 | 12 | +| Modulation | QPSK | QPSK | QPSK | QPSK | QPSK | +| Code rate (Note 2) | 1/3 | 1/3 | 1/3 | 1/3 | 1/3 | +| Payload size (bits) | 5632 | 2792 | 5632 | 2856 | 1416 | +| Transport block CRC (bits) | 24 | 16 | 24 | 16 | 16 | +| Code block CRC size (bits) | - | - | - | - | - | +| Number of code blocks - C | 1 | 1 | 1 | 1 | 1 | +| Code block size including CRC (bits) (Note 3) | 5656 | 2808 | 5656 | 2872 | 1432 | +| Total number of bits per slot | 19008 | 9216 | 19008 | 9504 | 4608 | +| Total symbols per slot | 9504 | 4608 | 9504 | 4752 | 2304 | + +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 [20]. + +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 [19], clause 5.2.2. + +## A.2 Fixed Reference Channels for OTA dynamic range (16QAM, R=2/3) + +The parameters for the reference measurement channels are specified in table A.2-1 for FR1 OTA dynamic range. + +**Table A.2-1: FRC parameters for FR1 OTA 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 [20]. + +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 [19], clause 5.2.2. + +## 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-14 for FR1 PUSCH performance requirements for TBoMS: + +- FRC parameters are specified in table A.3-14 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.3-7 to table A.3-12 for FR2 PUSCH performance requirements: + +- FRC parameters are specified in table A.3-7 for FR2 PUSCH with transform precoding disabled, additional DM-RS position = pos0 and 1 transmission layer. +- FRC parameters are specified in table A.3-8 for FR2 PUSCH with transform precoding disabled, additional DM-RS position = pos0 and 2 transmission layer. +- FRC parameters are specified in table A.3-9 for FR2 PUSCH with transform precoding enabled, additional DM-RS position = pos0 and 1 transmission layer. +- FRC parameters are specified in table A.3-10 for FR2 PUSCH with transform precoding disabled, additional DM-RS position = pos1 and 1 transmission layer. +- FRC parameters are specified in table A.3-11 for FR2 PUSCH with transform precoding disabled, additional DM-RS position = pos1 and 2 transmission layer. +- FRC parameters are specified in table A.3-12 for FR2 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-13 for FR2 PUSCH performance requirements for 2-step RA type: + +- FRC parameters are specified in table A.3-13 for FR2 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.3-15 for FR2 PUSCH performance requirements for TBoMS: + +- FRC parameters are specified in table A.3-15 for FR2 PUSCH with transform precoding disabled, *Additional DM-RS position = pos1* and 1 transmission layer. + +Note: The FRC table A.3-16 defined in TS38.104 [2] and TS38.141-1 [3] is not used in this specification. + +**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_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 clause 5.2.2 of TS 38.212 [19]. + +**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 [20]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [19]. + +**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 [20]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [19]. + +**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 [20]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [19]. + +**Table A.3-7: FRC parameters for FR2 PUSCH performance requirements, transform precoding disabled, additional DM-RS position = pos0 and 1 transmission layer (QPSK, R=193/1024)** + +| Reference channel | G-FR2-A3-1 | G-FR2-A3-2 | G-FR2-A3-3 | G-FR2-A3-4 | G-FR2-A3-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 (Note 2) | 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 [20]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [19]. + +**Table A.3-8: FRC parameters for FR2 PUSCH performance requirements, transform precoding disabled, additional DM-RS position = pos0 and 2 transmission layers (QPSK, R=193/1024)** + +| Reference channel | G-FR2-A3-6 | G-FR2-A3-7 | G-FR2-A3-8 | G-FR2-A3-9 | G-FR2-A3-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 (Note 2) | 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 [20]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [19]. + +**Table A.3-9: FRC parameters for FR2 PUSCH performance requirements, transform precoding enabled, additional DM-RS position = pos0 and 1 transmission layer (QPSK, R=193/1024)** + +| Reference channel | G-FR2-A3-11 | G-FR2-A3-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 (Note 2) | 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 [20]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [19]. + +**Table A.3-10: FRC parameters for FR2 PUSCH performance requirements, transform precoding disabled, additional DM-RS position = pos1 and 1 transmission layer (QPSK, R=193/1024)** + +| Reference channel | G-FR2-A3-13 | G-FR2-A3-14 | G-FR2-A3-15 | G-FR2-A3-16 | G-FR2-A3-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 (Note 2) | 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 [20]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [19]. + +**Table A.3-11: FRC parameters for FR2 PUSCH performance requirements, transform precoding disabled, additional DM-RS position = pos1 and 2 transmission layers (QPSK, R=193/1024)** + +| Reference channel | G-FR2-A3-18 | G-FR2-A3-19 | G-FR2-A3-20 | G-FR2-A3-21 | G-FR2-A3-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 (Note 2) | 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 [20]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [19]. + +**Table A.3-12: FRC parameters for FR2 PUSCH performance requirements, transform precoding enabled, additional DM-RS position = pos1 and 1 transmission layer (QPSK, R=193/1024)** + +| Reference channel | G-FR2-A3-23 | G-FR2-A3-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 (Note 2) | 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 [20]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [19]. + +**Table A.3-13: FRC parameters for FR2 PUSCH performance requirements, transform precoding disabled, additional DM-RS position = pos1 and 1 transmission layer (QPSK, R=193/1024)** + +| Reference channel | G-FR2-A3-25 | G-FR2-A3-26 | +|-----------------------------------------------|-------------|-------------| +| Subcarrier spacing (kHz) | 60 | 120 | +| Allocated resource blocks | 2 | 2 | +| CP-OFDM Symbols per slot (Note 1) | 8 | 8 | +| Modulation | QPSK | QPSK | +| Code rate (Note 2) | 193/1024 | 193/1024 | +| Payload size (bits) | 72 | 72 | +| Transport block CRC (bits) | 16 | 16 | +| Code block CRC size (bits) | 0 | 0 | +| Number of code blocks - C | 1 | 1 | +| Code block size including CRC (bits) (Note 2) | 88 | 88 | +| Total number of bits per slot | 384 | 384 | +| Total symbols per slot | 192 | 192 | + +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 = 2$ and $l = 10$ 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 clause 5.2.2 of TS 38.212 [19]. + +**Table A.3-14: 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 [20]. | | | | | +| NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [19]. | | | | | + +**Table A.3-15: FRC parameters for FR2 PUSCH performance requirements, transform precoding disabled, Additional DM-RS position = pos1 and 1 transmission layer (QPSK, R=193/1024)** + +| Reference channel | G-FR2-A3-27 | G-FR2-A3-28 | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------| +| Number of TBoMS slots | 2 | 2 | +| Subcarrier spacing [kHz] | 60 | 120 | +| Allocated resource blocks per slot | 5 | 5 | +| Data bearing CP-OFDM Symbols per slot (Note 1) | 8 | 8 | +| Modulation | QPSK | QPSK | +| Code rate (Note 2) | 193/1024 | 193/1024 | +| Payload size (bits) | 368 | 368 | +| 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) | 384 | 384 | +| Total number of bits over all TBoMS slots | 1920 | 1920 | +| Total resource elements over all TBoMS slots | 960 | 960 | +| 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 = 0$ and $l = 8$ 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 [19]. | | | + +## A.3A Fixed Reference Channels for performance requirements (QPSK, R=99/1024) + +The parameters for the reference measurement channels 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. + +The parameters for the reference measurement channels are specified in table A.3A-2 to A.3A-3 for FR2 PUSCH performance requirements: + +- FRC parameters are specified in table A.3A-2 for FR2 PUSCH with transform precoding disabled, additional DM-RS position = pos0 and 1 transmission layer. +- FRC parameters are specified in table A.3A-3 for FR2 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 [20]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [19]. + +**Table A.3A-2: FRC parameters for FR2 PUSCH performance requirements, transform precoding disabled, additional DM-RS position = pos0 and 1 transmission layer (QPSK, R=99/1024)** + +| Reference channel | G-FR2-A3A-1 | G-FR2-A3A-2 | G-FR2-A3A-3 | G-FR2-A3A-4 | +|------------------------------------------------|-------------|-------------|-------------|-------------| +| Subcarrier spacing [kHz] | 60 | 60 | 120 | 120 | +| Allocated resource blocks | 66 | 132 | 32 | 66 | +| Data bearing CP-OFDM Symbols per slot (Note 1) | 3 | 3 | 3 | 3 | +| Modulation | QPSK | QPSK | QPSK | QPSK | +| Code rate (Note 2) | 99/1024 | 99/1024 | 99/1024 | 99/1024 | +| Payload size (bits) | 456 | 928 | 224 | 456 | +| 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) | 472 | 944 | 240 | 472 | +| Total number of bits per slot | 4752 | 9504 | 2304 | 4752 | +| Total symbols per slot | 2376 | 4752 | 1152 | 2376 | + +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 [20]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in subclause 5.2.2 of TS 38.212 [19]. + +**Table A.3A-3: FRC parameters for FR2 PUSCH performance requirements, transform precoding disabled, additional DM-RS position = pos1 and 1 transmission layer (QPSK, R=99/1024)** + +| Reference channel | G-FR2-A3A-5 | G-FR2-A3A-6 | G-FR2-A3A-7 | G-FR2-A3A-8 | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------|-------------|-------------| +| Subcarrier spacing [kHz] | 60 | 60 | 120 | 120 | +| Allocated resource blocks | 66 | 132 | 32 | 66 | +| Data bearing CP-OFDM Symbols per slot (Note 1) | 8 | 8 | 8 | 8 | +| Modulation | QPSK | QPSK | QPSK | QPSK | +| Code rate (Note 2) | 99/1024 | 99/1024 | 99/1024 | 99/1024 | +| Payload size (bits) | 1224 | 2472 | 608 | 1224 | +| 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) | 1240 | 2488 | 624 | 1240 | +| Total number of bits per slot | 12672 | 25344 | 6144 | 12672 | +| Total symbols per slot | 6336 | 12672 | 3072 | 6336 | +| 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 = 0$ and $l = 8$ 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 subclause 5.2.2 of TS 38.212 [19]. | | | | | + +## A.3B Fixed Reference Channels for performance requirements (QPSK, R=308/1024) + +The parameters for the reference measurement channels are 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, no additional DM-RS 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. + +The parameters for the reference measurement channel are specified in table A.3B-4 for FR2 PUSCH performance requirements with DM-RS bundling: + +- FRC parameters are specified in table A.3B-4 for FR2 PUSCH with transform precoding disabled, additional DM-RS position = pos1 and 1 transmission layer. + +The parameters for the reference measurement channel are specified in table A.3B-5 to table A.3B-7 for FR2-2 PUSCH performance requirements: + +- FRC parameters are specified in table A.3B-5 for FR2-2 PUSCH with transform precoding disabled, *Additional DM-RS position = pos1* and 1 transmission layer. +- FRC parameters are specified in table A.3B-6 for FR2-2 PUSCH with transform precoding enabled, *Additional DM-RS position = pos1* and 1 transmission layer. +- FRC parameters are specified in table A.3B-7 for FR2-2 PUSCH with transform precoding disabled, *Additional DM-RS position = pos1* and 2 transmission layers. + +**Table A.3B-1: FRC parameters for FR1 PUSCH performance requirements, transform precoding disabled, no additional DM-RS 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 [20]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [19]. + +**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 [9]. + +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 $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 [9]. | | | +| 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-4: FRC parameters for FR2 PUSCH performance requirements, transform precoding disabled, *Additional DM-RS position = pos1* and 1 transmission layer (QPSK, R=308/1024)** + +| Reference channel | G-FR2-A3B-1 | G-FR2-A3B-2 | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------| +| Subcarrier spacing [kHz] | 60 | 120 | +| Allocated resource blocks | 66 | 32 | +| CP-OFDM Symbols per slot (Note 1) | 12 | 12 | +| Modulation | QPSK | QPSK | +| Code rate (Note 2) | 308/1024 | 308/1024 | +| Payload size (bits) | 5632 | 2792 | +| Transport block CRC (bits) | 24 | 16 | +| Code block CRC size (bits) | - | - | +| Number of code blocks - C | 1 | 1 | +| Code block size including CRC (bits) (Note 2) | 5656 | 2808 | +| Total number of bits per slot | 19008 | 9216 | +| Total resource elements per slot | 9504 | 4608 | +| 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 = 10$ as per Table 6.4.1.1.3-3 of TS 38.211 [9]. | | | +| 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-5: FRC parameters for FR2-2 PUSCH performance requirements, transform precoding disabled, *Additional DM-RS position = pos1* and 1 transmission layer (QPSK, R=308/1024)** + +| Reference channel | G-FR2-A3B-3 | G-FR2-A3B-4 | G-FR2-A3B-5 | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------|-------------| +| Subcarrier spacing [kHz] | 120 | 120 | 480 | +| Allocated resource blocks | 66 | 264 | 66 | +| CP-OFDM Symbols per slot (Note 1) | 8 | 8 | 8 | +| Modulation | QPSK | QPSK | QPSK | +| Code rate (Note 2) | 308/1024 | 308/1024 | 308/1024 | +| Payload size (bits) | 3824 | 15112 | 3824 | +| Transport block CRC (bits) | 16 | 24 | 16 | +| Code block CRC size (bits) | - | 24 | - | +| Number of code blocks - C | 1 | 2 | 1 | +| Code block size including CRC (bits) (Note 2) | 3840 | 7592 | 3840 | +| Total number of bits per slot without PT-RS | 12672 | 50688 | 12672 | +| Total symbols per slot without PT-RS | 6336 | 25344 | 6336 | +| 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 [9]. | | | | +| NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [15]. | | | | +| NOTE 3: The calculation of the “Total number of bits per slot” and “Total symbols per slot” fields include the REs taken up by CSI part 1 and CSI part 2, if present. | | | | + +**Table A.3B-6: FRC parameters for FR2-2 PUSCH performance requirements, transform precoding enabled, *Additional DM-RS position = pos1* and 1 transmission layer (QPSK, R=308/1024)** + +| Reference channel | G-FR2-A3B-6 | G-FR2-A3B-7 | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------| +| Subcarrier spacing [kHz] | 120 | 480 | +| Allocated resource blocks | 64 | 64 | +| DFT-s-OFDM Symbols per slot (Note 1) | 8 | 8 | +| Modulation | QPSK | QPSK | +| Code rate (Note 2) | 308/1024 | 308/1024 | +| Payload size (bits) | 3624 | 3624 | +| 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) | 3640 | 3640 | +| Total number of bits per slot without PT-RS | 12288 | 12288 | +| Total symbols per slot without PT-RS | 6144 | 6144 | +| 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 [9]. | | | +| NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [15]. | | | +| NOTE 3: The calculation of the “Total number of bits per slot” and “Total symbols per slot” fields include the REs taken up by CSI part 1 and CSI part 2, if present. | | | + +**Table A.3B-7: FRC parameters for FR2-2 PUSCH performance requirements, transform precoding disabled, Additional DM-RS position = pos1 and 2 transmission layers (QPSK, R=308/1024)** + +| Reference channel | G-FR2-A3B-8 | G-FR2-A3B-9 | G-FR2-A3B-10 | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------|--------------| +| Subcarrier spacing [kHz] | 120 | 120 | 480 | +| Allocated resource blocks | 66 | 264 | 66 | +| CP-OFDM Symbols per slot (Note 1) | 8 | 8 | 8 | +| Modulation | QPSK | QPSK | QPSK | +| Code rate (Note 2) | 308/1024 | 308/1024 | 308/1024 | +| Payload size (bits) | 7552 | 30728 | 7552 | +| Transport block CRC (bits) | 24 | 24 | 24 | +| Code block CRC size (bits) | - | 24 | - | +| Number of code blocks - C | 1 | 4 | 1 | +| Code block size including CRC (bits) (Note 2) | 7576 | 7712 | 7576 | +| Total number of bits per slot without PT-RS | 25344 | 101376 | 25344 | +| Total symbols per slot without PT-RS | 12672 | 50688 | 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 [9]. | | | | +| NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [15]. | | | | +| NOTE 3: The calculation of the "Total number of bits per slot" and "Total symbols per slot" fields include the REs taken up by CSI part 1 and CSI part 2, if present. | | | | + +## 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, table A.4-2B 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 = pos 2 and 1 transmission layer. +- FRC parameters are specified in table A.4-2B for FR1 UL timing adjustment, PUSCH with transform precoding disabled, additional DM-RS position = pos2 and 1 transmission layer. +- 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. + +The parameters for the reference measurement channels are specified in table A.4-5 to table A.4-8 for FR2-1 PUSCH performance requirements: + +- FRC parameters are specified in table A.4-5 for FR2-1 PUSCH with transform precoding disabled, additional DM-RS position = pos0 and 1 transmission layer. +- FRC parameters are specified in table A.4-6 for FR2-1 PUSCH with transform precoding disabled, additional DM-RS position = pos0 and 2 transmission layers. +- FRC parameters are specified in table A.4-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.4-8 for FR2-1 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.4-7A for FR2-2 PUSCH performance requirements: + +- FRC parameters are specified in table A.4-7A for FR2-2 PUSCH with transform precoding disabled, additional DM-RS position = pos1 and 1 transmission layer. + +**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
(Note 3) | 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_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 clause 5.2.2 of TS 38.212 [19]. + +NOTE 3: The calculation of the "Total number of bits per slot" and "Total symbols per slot" fields include the REs taken up by CSI part 1 and CSI part 2, if present. + +**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 [20]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [19]. + +**Table A.4-2B: FRC parameters for FR1 UL timing adjustment, PUSCH with 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 | +| 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) | 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 data bearing resource elements 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, and $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 clause 5.2.2 of TS 38.212 [19]. + +**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_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 clause 5.2.2 of TS 38.212 [19]. + +**Table A.4-5: 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 | G-FR2-A4-1 | G-FR2-A4-2 | G-FR2-A4-3 (Note 3) | G-FR2-A4-4 | G-FR2-A4-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 (Note 2) | 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 without PT-RS | 28512 | 57024 | 13824 | 28512 | 57024 | +| Total number of bits per slot with PT-RS (Note 4) | 27324 | 54648 | 13248 | 27324 | 54648 | +| Total symbols per slot without PT-RS | 7128 | 14256 | 3456 | 7128 | 14256 | +| Total symbols per slot with PT-RS (Note 4) | 6831 | 13662 | 3312 | 6831 | 13662 | + +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 [20]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [15]. + +NOTE 3: The calculation of the “Total number of bits per slot” and “Total symbols per slot” fields include the REs taken up by CSI part 1 and CSI part 2, if present. + +NOTE 4: PT-RS configuration $K_{PT-RS} = 2$ , $L_{PT-RS} = 1$ . + +**Table A.4-6: 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 | G-FR2-A4-6 | G-FR2-A4-7 | G-FR2-A4-8 | G-FR2-A4-9 | G-FR2-A4-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 (Note 2) | 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 without PT-RS | 57024 | 114048 | 27648 | 57024 | 114048 | +| Total number of bits per slot with PT-RS (Note 3) | 54648 | 109296 | 26496 | 54648 | 109296 | +| Total symbols per slot without PT-RS | 14256 | 28512 | 6912 | 14256 | 28512 | +| Total symbols per slot with PT-RS (Note 3) | 13662 | 27324 | 6624 | 13662 | 27324 | + +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 [20]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [15]. + +NOTE 3: PT-RS configuration $K_{PT-RS} = 2$ , $L_{PT-RS} = 1$ . + +**Table A.4-7: 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 | G-FR2-A4-11 | G-FR2-A4-12 | G-FR2-A4-13 | G-FR2-A4-14 | G-FR2-A4-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 (Note 2) | 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 without PT-RS | 25344 | 50688 | 12288 | 25344 | 50688 | +| Total number of bits per slot with PT-RS (Note 4) | 24288 | 48576 | 11776 | 24288 | 48576 | +| Total symbols per slot without PT-RS | 6336 | 12672 | 3072 | 6336 | 12672 | +| Total symbols per slot with PT-RS (Note 4) | 6072 | 12144 | 2944 | 6072 | 12144 | + +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 [20]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [19]. + +NOTE 3: The calculation of the “Total number of bits per slot” and “Total symbols per slot” fields include the REs taken up by CSI part 1 and CSI part 2, if present. + +NOTE 4: PT-RS configuration $K_{PT-RS} = 2$ , $L_{PT-RS} = 1$ . + +**Table A.4-7A: FRC parameters for FR2-2 PUSCH performance requirements, transform precoding disabled, Additional DM-RS position = pos1 and 1 transmission layer (16QAM, R=658/1024)** + +| Reference channel | G-FR2-A4-21 | G-FR2-A4-22 | G-FR2-A4-23 | +|---------------------------------------------------|-------------|-------------|-------------| +| Subcarrier spacing [kHz] | 120 | 120 | 480 | +| Allocated resource blocks | 66 | 264 | 66 | +| CP-OFDM Symbols per slot (Note 1) | 8 | 8 | 8 | +| Modulation | 16QAM | 16QAM | 16QAM | +| Code rate (Note 2) | 658/1024 | 658/1024 | 658/1024 | +| Payload size (bits) | 16392 | 65576 | 16392 | +| Transport block CRC (bits) | 24 | 24 | 24 | +| Code block CRC size (bits) | 24 | 24 | 24 | +| Number of code blocks - C | 2 | 8 | 2 | +| Code block size including CRC (bits) (Note 2) | 8232 | 8224 | 8232 | +| Total number of bits per slot without PT-RS | 25344 | 101376 | 25344 | +| Total number of bits per slot with PT-RS (Note 4) | 24288 | 97152 | 24288 | +| Total symbols per slot without PT-RS | 6336 | 25344 | 6336 | +| Total symbols per slot with PT-RS (Note 4) | 6072 | 24288 | 6072 | + +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 [9]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [15]. + +NOTE 3: The calculation of the “Total number of bits per slot” and “Total symbols per slot” fields include the REs taken up by CSI part 1 and CSI part 2, if present. + +NOTE 4: PT-RS configuration $K_{PT-RS} = 2$ , $L_{PT-RS} = 1$ . + +**Table A.4-8: 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 | G-FR2-A4-16 | G-FR2-A4-17 | G-FR2-A4-18 | G-FR2-A4-19 | G-FR2-A4-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 (Note 2) | 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 without PT-RS | 50688 | 101376 | 24576 | 50688 | 101376 | +| Total number of bits per slot with PT-RS (Note 3) | 48576 | 97152 | 23552 | 48576 | 97152 | +| Total symbols per slot without PT-RS | 12672 | 25344 | 6144 | 12672 | 25344 | +| Total symbols per slot with PT-RS (Note 3) | 12144 | 24288 | 5888 | 12144 | 24288 | + +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 [20]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [19]. + +NOTE 3: PT-RS configuration $K_{PT-RS} = 2$ , $L_{PT-RS} = 1$ . + +**Table A.4-8A: Void** + +## 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 for FR1 PUSCH performance requirements 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.5-3 to table A.5-4 for FR2-1 PUSCH performance requirements: + +- FRC parameters are specified in table A.5-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.5-4 for FR2-1 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.5-4A and table A.5-7 for FR2-2 PUSCH performance requirements: + +- FRC parameters are specified in table A.5-4A for FR2-2 PUSCH with transform precoding disabled, additional DM-RS position = pos1 and 1 transmission layer. +- FRC parameters are specified in table A.5-7 for FR2-2 PUSCH with transform precoding disabled, *Additional DM-RS position = pos1* and 2 transmission layers. + +**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_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 clause 5.2.2 of TS 38.212 [19]. + +**Table A.5-3: 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 | G-FR2-A5-1 | G-FR2-A5-2 | G-FR2-A5-3 | G-FR2-A5-4 | G-FR2-A5-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 (Note 2) | 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 without PT-RS | 42768 | 85536 | 20736 | 42768 | 85536 | +| Total number of bits per slot with PT-RS (Note 3) | 40986 | 81972 | 19872 | 40986 | 81972 | +| Total symbols per slot without PT-RS | 7128 | 14256 | 3456 | 7128 | 14256 | +| Total symbols per slot with PT-RS (Note 3) | 6831 | 13662 | 3312 | 6831 | 13662 | + +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 [20]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [19]. + +NOTE 3: PT-RS configuration $K_{PT-RS} = 2$ , $L_{PT-RS} = 1$ . + +**Table A.5-4: 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 | G-FR2-A5-6 | G-FR2-A5-7 | G-FR2-A5-8 | G-FR2-A5-9 | G-FR2-A5-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 (Note 2) | 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 without PT-RS | 38016 | 76032 | 18432 | 38016 | 76032 | +| Total number of bits per slot with PT-RS (Note 3) | 36432 | 72864 | 17664 | 36432 | 72864 | +| Total symbols per slot without PT-RS | 6336 | 12672 | 3072 | 6336 | 12672 | +| Total symbols per slot with PT-RS (Note 3) | 6072 | 12144 | 2944 | 6072 | 12144 | + +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 [20]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [19]. + +NOTE 3: PT-RS configuration $K_{PT-RS} = 2$ , $L_{PT-RS} = 1$ . + +**Table A.5-4A: FRC parameters for FR2-2 PUSCH performance requirements, transform precoding disabled, Additional DM-RS position = pos1 and 1 transmission layer (64QAM, R=567/1024)** + +| Reference channel | G-FR2-A5-11 | G-FR2-A5-12 | G-FR2-A5-13 | +|---------------------------------------------------|-------------|-------------|-------------| +| Subcarrier spacing [kHz] | 120 | 120 | 480 | +| Allocated resource blocks | 66 | 66 | 66 | +| CP-OFDM Symbols per slot (Note 1) | 8 | 8 | 8 | +| Modulation | 64QAM | 64QAM | 64QAM | +| Code rate (Note 2) | 567/1024 | 567/1024 | 567/1024 | +| Payload size (bits) | 21000 | 83976 | 21000 | +| Transport block CRC (bits) | 24 | 24 | 24 | +| Code block CRC size (bits) | 24 | 24 | 24 | +| Number of code blocks - C | 3 | 10 | 3 | +| Code block size including CRC (bits) (Note 2) | 7032 | 8424 | 7032 | +| Total number of bits per slot without PT-RS | 38016 | 152064 | 38016 | +| Total number of bits per slot with PT-RS (Note 3) | 36432 | 145728 | 36432 | +| Total symbols per slot without PT-RS | 6336 | 25344 | 6336 | +| Total symbols per slot with PT-RS (Note 3) | 6072 | 24288 | 6072 | + +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 [9]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [15]. + +NOTE 3: PT-RS configuration $K_{PT-RS} = 2$ , $L_{PT-RS} = 1$ . + +**Table A.5-5: 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 , $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 clause 5.2.2 of TS 38.212 [19]. | | | +| 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 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 | + +**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 in FR1** + +| 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 | + +**Table A.6-7: Test preambles for high speed train short formats in FR2** + +| Burst format | SCS (kHz) | Ncs | Logical sequence index | v | +|--------------|-----------|-----|------------------------|---| +| C2 | 120 | 0 | 0 | 0 | + +**Table A.6-8 Test preambles for PRACH with $L_{RA}=139$ , $L_{RA}=571$ and $L_{RA}=1151$ for 120 KHz and 480 KHz SCS** + +| Burst format | SCS (kHz) | $L_{RA}$ | Ncs | Logical sequence index | v | +|--------------|-----------|----------|-----|------------------------|---| +| A2, B4, C2 | 120 | 571 | 285 | 0 | 0 | +| | 120 | 1151 | 575 | 0 | 0 | +| | 480 | 139 | 69 | 0 | 0 | +| | 480 | 571 | 285 | 0 | 0 | + +## A.7 Fixed Reference Channels for performance requirements (16QAM, $R=434/1024$ ) + +The parameters for the reference measurement channels are specified in table A.7-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.7-2 for FR2-1 PUSCH performance requirements 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.7-3 for FR2-2 PUSCH performance requirements with transform precoding disabled, additional DM-RS position = pos1 and 2 transmission layers. + +Note: The FRC table A.7-4 defined in TS38.104 [2] is not used in this specification. + +**Table A.7-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 | G-FR2-A7-1 | G-FR2-A7-2 | G-FR2-A7-3 | G-FR2-A7-4 | G-FR2-A7-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 (Note 2) | 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 without PT-RS | 57024 | 114048 | 27648 | 57024 | 114048 | +| Total number of bits per slot with PT-RS (Note 3) | 54648 | 109296 | 26496 | 54648 | 109296 | +| Total symbols per slot without PT-RS | 14256 | 28512 | 6912 | 14256 | 28512 | +| Total symbols per slot with PT-RS (Note 3) | 13662 | 27324 | 6624 | 13662 | 27324 | + +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 [20]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [19]. + +NOTE 3: PT-RS configuration $K_{PT-RS} = 2$ , $L_{PT-RS} = 1$ . + +**Table A.7-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 | G-FR2-A7-6 | G-FR2-A7-7 | G-FR2-A7-8 | G-FR2-A7-9 | G-FR2-A7-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 (Note 2) | 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 without PT-RS | 50688 | 101376 | 24576 | 50688 | 101376 | +| Total number of bits per slot with PT-RS (Note 3) | 48576 | 97152 | 23552 | 48576 | 97152 | +| Total symbols per slot without PT-RS | 12672 | 25344 | 6144 | 12672 | 25344 | +| Total symbols per slot with PT-RS (Note 3) | 12144 | 24288 | 5888 | 12144 | 24288 | + +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 [20]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [19]. + +NOTE 3: PT-RS configuration $K_{PT-RS} = 2$ , $L_{PT-RS} = 1$ . + +**Table A.7-3: FRC parameters for FR2-2 PUSCH performance requirements, transform precoding disabled, Additional DM-RS position = pos1 and 2 transmission layers (16QAM, R=434/1024)** + +| Reference channel | G-FR2-A7-11 | G-FR2-A7-12 | G-FR2-A7-13 | +|---------------------------------------------------|-------------|-------------|-------------| +| Subcarrier spacing [kHz] | 120 | 120 | 480 | +| Allocated resource blocks | 66 | 264 | 66 | +| CP-OFDM Symbols per slot (Note 1) | 8 | 8 | 8 | +| Modulation | 16QAM | 16QAM | 16QAM | +| Code rate (Note 2) | 434/1024 | 434/1024 | 434/1024 | +| Payload size (bits) | 21504 | 86040 | 21504 | +| Transport block CRC (bits) | 24 | 24 | 24 | +| Code block CRC size (bits) | 24 | 24 | 24 | +| Number of code blocks - C | 3 | 11 | 3 | +| Code block size including CRC (bits) (Note 2) | 7200 | 7848 | 7200 | +| Total number of bits per slot without PT-RS | 50688 | 202752 | 50688 | +| Total number of bits per slot with PT-RS (Note 4) | 48576 | 194304 | 48576 | +| Total symbols per slot without PT-RS | 12672 | 50688 | 12672 | +| Total symbols per slot with PT-RS (Note 4) | 12144 | 48576 | 12144 | + +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 [9]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [15]. + +NOTE 3: The calculation of the “Total number of bits per slot” and “Total symbols per slot” fields include the REs taken up by CSI part 1 and CSI part 2, if present. + +NOTE 4: PT-RS configuration $K_{PT-RS} = 2$ , $L_{PT-RS} = 1$ . + +## A.8 Fixed Reference Channels for performance requirements (QPSK, R=157/1024) + +Note: Different FRC numbers are assigned in TS 38.141-1 [3] for the FRCs in this annex. + +The parameters for the reference measurement channels are specified in table A.8-1 and A.8-2 for FR1 PUSCH performance requirements for 2-step RA type with Additional DM-RS position equals to pos2 and pos1 respectively. + +**Table A.8-1: 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-A8-1 | G-FR1-A8-2 | +|-----------------------------------------------|------------|------------| +| Subcarrier spacing [kHz] | 15 | 30 | +| Allocated resource blocks | 2 | 2 | +| 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) | 0 | 0 | +| 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 symbols 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 with $l_0 = 2$ 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 clause 5.2.2 of TS 38.212 [19]. + +**Table A.8-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-A8-3 | G-FR1-A8-4 | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------| +| Subcarrier spacing [kHz] | 15 | 30 | +| Allocated resource blocks | 2 | 2 | +| 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) | 0 | 0 | +| 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 symbols 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 with l0 = 2 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 clause 5.2.2 of TS 38.212 [19]. | | | + +## A.9 Fixed Reference Channels for performance requirements (256QAM, R=682.5/1024) + +Note: Different FRC numbers are assigned in TS 38.141-1 [3] for the FRCs in this annex. + +The parameters for the reference measurement channels are specified in table A.9-1 for FR1 PUSCH performance requirements: + +- FRC parameters are specified in table A.9-1 for FR1 PUSCH with transform precoding disabled, *Additional DM-RS position = pos1* and 1 transmission layer. + +**Table A.9-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-A9-1 | G-FR1-A9-2 | G-FR1-A9-3 | G-FR1-A9-4 | G-FR1-A9-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 [5]. | | | | | | +| NOTE 2: Code block size including CRC (bits) equals to K' in clause 5.2.2 of TS 38.212 [15]. | | | | | | + +## A.10 Fixed Reference Channels for performance requirements (64QAM, R=517/1024) + +The parameters for the reference measurement channels are specified in table A.10-1, A.10-2 and A.10-3 for FR2 PUSCH performance requirements: + +- FRC parameters are specified in table A.10-1 for FR2 PUSCH with transform precoding disabled, *Additional DM-RS position = pos0* and 1 transmission layer. +- FRC parameters are specified in table A.10-2 for FR2 PUSCH with transform precoding disabled, *Additional DM-RS position = pos1* and 1 transmission layer. +- FRC parameters are specified in table A.10-3 for FR2 PUSCH with transform precoding disabled, *Additional DM-RS position = pos2* and 1 transmission layer. + +The parameters for the reference measurement channels are specified in table A.10-4, table A.10-5 and table A.10-6 for FR2 PUSCH UL timing adjustment performance requirements: + +- FRC parameters are specified in table A.10-4 for FR2 UL timing adjustment requirements, PUSCH with transform precoding disabled, *Additional DM-RS position = pos0* and 1 transmission layer. +- FRC parameters are specified in table A.10-5 for FR2 UL timing adjustment requirements, PUSCH with transform precoding disabled, *Additional DM-RS position = pos1* and 1 transmission layer. +- FRC parameters are specified in table A.10-6 for FR2 UL timing adjustment requirements, PUSCH with transform precoding disabled, *Additional DM-RS position = pos2* and 1 transmission layer. + +**Table A.10-1: FRC parameters for FR2 PUSCH performance requirements, transform precoding disabled, Additional DM-RS position = pos0 and 1 transmission layer (64QAM, R=517/1024)** + +| Reference channel | G-FR2-A10-1 | G-FR2-A10-2 | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------| +| Subcarrier spacing [kHz] | 120 | 120 | +| Allocated resource blocks | 32 | 132 | +| Data bearing CP-OFDM Symbols per slot (Note 1) | 9 | 9 | +| Modulation | 64QAM | 64QAM | +| Code rate (Note 2) | 517/1024 | 517/1024 | +| Payload size (bits) | 10504 | 43032 | +| Transport block CRC (bits) | 24 | 24 | +| Code block CRC size (bits) | 24 | 24 | +| Number of code blocks - C | 2 | 6 | +| Code block size including CRC (bits) (Note 2) | 5288 | 7200 | +| Total number of bits per slot without PT-RS | 20736 | 85536 | +| Total number of bits per slot with PT-RS (Note 3) | 19872 | 81972 | +| Total resource elements per slot without PT-RS | 3456 | 14256 | +| Total resource elements per slot with PT-RS (Note 3) | 3312 | 13662 | +| 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 [9]. | | | +| NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [15]. | | | +| NOTE 3: PT-RS configuration $K_{PT-RS} = 2$ , $L_{PT-RS} = 1$ . | | | + +**Table A.10-2: FRC parameters for FR2 PUSCH performance requirements, transform precoding disabled, Additional DM-RS position = pos1 and 1 transmission layer (64QAM, R=517/1024)** + +| Reference channel | G-FR2-A10-3 | G-FR2-A10-4 | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------| +| Subcarrier spacing [kHz] | 120 | 120 | +| Allocated resource blocks | 32 | 132 | +| Data bearing CP-OFDM Symbols per slot (Note 1) | 8 | 8 | +| Modulation | 64QAM | 64QAM | +| Code rate (Note 2) | 517/1024 | 517/1024 | +| Payload size (bits) | 9224 | 37896 | +| Transport block CRC (bits) | 24 | 24 | +| Code block CRC size (bits) | 24 | 24 | +| Number of code blocks - C | 2 | 5 | +| Code block size including CRC (bits) (Note 2) | 4648 | 7608 | +| Total number of bits per slot without PT-RS | 18432 | 76032 | +| Total number of bits per slot with PT-RS (Note 3) | 17664 | 72864 | +| Total resource elements per slot without PT-RS | 3072 | 12672 | +| Total resource elements per slot with PT-RS (Note 3) | 2944 | 12144 | +| 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 [9]. | | | +| NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [15]. | | | +| NOTE 3: PT-RS configuration $K_{PT-RS} = 2$ , $L_{PT-RS} = 1$ . | | | + +**Table A.10-3: FRC parameters for FR2 PUSCH performance requirements, transform precoding disabled, Additional DM-RS position = pos2 and 1 transmission layer (64QAM, R=517/1024)** + +| Reference channel | G-FR2-A10-5 | G-FR2-A10-6 | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------| +| Subcarrier spacing [kHz] | 120 | 120 | +| Allocated resource blocks | 32 | 132 | +| Data bearing CP-OFDM Symbols per slot (Note 1) | 7 | 7 | +| Modulation | 64QAM | 64QAM | +| Code rate (Note 2) | 517/1024 | 517/1024 | +| Payload size (bits) | 8064 | 33816 | +| Transport block CRC (bits) | 24 | 24 | +| Code block CRC size (bits) | | 24 | +| Number of code blocks - C | 1 | 5 | +| Code block size including CRC (bits) (Note 2) | 8088 | 6792 | +| Total number of bits per slot without PT-RS | 16128 | 66528 | +| Total number of bits per slot with PT-RS (Note 3) | 15456 | 63756 | +| Total resource elements per slot without PT-RS | 2688 | 11088 | +| Total resource elements per slot with PT-RS (Note 3) | 2576 | 10626 | +| 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 with $l_0 = 0$ and $l = 4, 8$ as per Table 6.4.1.1.3-3 of TS 38.211 [9]. | | | +| NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [15]. | | | +| NOTE 3: PT-RS configuration $K_{PT-RS} = 2$ , $L_{PT-RS} = 1$ . | | | + +**Table A.10-4: FRC parameters for FR2 UL timing adjustment requirements, PUSCH with transform precoding disabled, Additional DM-RS position = pos0 and 1 transmission layer (64QAM, R=517/1024)** + +| Reference channel | G-FR2-A10-7 | G-FR2-A10-8 | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------| +| Subcarrier spacing [kHz] | 120 | 120 | +| Allocated resource blocks | 16 | 66 | +| Data bearing CP-OFDM Symbols per slot (Note 1) | 9 | 9 | +| Modulation | 64QAM | 64QAM | +| Code rate (Note 2) | 517/1024 | 517/1024 | +| Payload size (bits) | 5248 | 21504 | +| Transport block CRC (bits) | 24 | 24 | +| Code block CRC size (bits) | - | 24 | +| Number of code blocks - C | 1 | 3 | +| Code block size including CRC (bits) (Note 2) | 5272 | 7200 | +| Total number of bits per slot without PT-RS | 10368 | 42768 | +| Total number of bits per slot with PT-RS (Note 3) | 9936 | 40986 | +| Total resource elements per slot without PT-RS | 1728 | 7128 | +| Total resource elements per slot with PT-RS (Note 3) | 1656 | 6831 | +| 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 [9]. | | | +| NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [15]. | | | +| NOTE 3: PT-RS configuration $K_{PT-RS} = 2$ , $L_{PT-RS} = 1$ . | | | + +**Table A.10-5: FRC parameters for FR2 UL timing adjustment requirements, PUSCH with transform precoding disabled, Additional DM-RS position = pos1 and 1 transmission layer (64QAM, R=517/1024)** + +| Reference channel | G-FR2-A10-9 | G-FR2-A10-10 | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|--------------| +| Subcarrier spacing [kHz] | 120 | 120 | +| Allocated resource blocks | 16 | 66 | +| Data bearing CP-OFDM Symbols per slot (Note 1) | 8 | 8 | +| Modulation | 64QAM | 64QAM | +| Code rate (Note 2) | 517/1024 | 517/1024 | +| Payload size (bits) | 4608 | 18960 | +| Transport block CRC (bits) | 24 | 24 | +| Code block CRC size (bits) | - | 24 | +| Number of code blocks - C | 1 | 3 | +| Code block size including CRC (bits) (Note 2) | 4632 | 6352 | +| Total number of bits per slot without PT-RS | 9216 | 38016 | +| Total number of bits per slot with PT-RS (Note 3) | 8832 | 36432 | +| Total resource elements per slot without PT-RS | 1536 | 6336 | +| Total resource elements per slot with PT-RS (Note 3) | 1472 | 6072 | +| 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 [9]. | | | +| NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [15]. | | | +| NOTE 3: PT-RS configuration $K_{PT-RS} = 2$ , $L_{PT-RS} = 1$ . | | | + +**Table A.10-6: FRC parameters for FR2 UL timing adjustment requirements, PUSCH with transform precoding disabled, Additional DM-RS position = pos2 and 1 transmission layer (64QAM, R=517/1024)** + +| Reference channel | G-FR2-A10-11 | G-FR2-A10-12 | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|--------------| +| Subcarrier spacing [kHz] | 120 | 120 | +| Allocated resource blocks | 16 | 66 | +| Data bearing CP-OFDM Symbols per slot (Note 1) | 7 | 7 | +| Modulation | 64QAM | 64QAM | +| Code rate (Note 2) | 517/1024 | 517/1024 | +| Payload size (bits) | 4032 | 16896 | +| Transport block CRC (bits) | 24 | 24 | +| Code block CRC size (bits) | - | 24 | +| Number of code blocks - C | 1 | 3 | +| Code block size including CRC (bits) (Note 2) | 4056 | 5664 | +| Total number of bits per slot without PT-RS | 8064 | 33264 | +| Total number of bits per slot with PT-RS (Note 3) | 7728 | 31878 | +| Total resource elements per slot without PT-RS | 1344 | 5544 | +| Total resource elements per slot with PT-RS (Note 3) | 1288 | 5313 | +| 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 with $l_0 = 0$ and $l = 4, 8$ as per Table 6.4.1.1.3-3 of TS 38.211 [9]. | | | +| NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [15]. | | | +| NOTE 3: PT-RS configuration $K_{PT-RS} = 2$ , $L_{PT-RS} = 1$ . | | | + +## A.11 Fixed Reference Channels for performance requirements (64QAM, R=438/1024) + +Fixed Reference Channels for performance requirements (64QAM, R=438/1024) are 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. + +For OTA requirements where it is not possible to environmentally control the entire calibrated OTA chamber either localised control of the BS 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 D.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 [7]; +- 2) The equipment class for the equipment under test, as defined in the IEC 60 721-3-4 [8]; +- 3) The equipment that does not comply with the mentioned classes, the relevant classes from IEC 60 721 [9] 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 [10]. + +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 [11]. + +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 [12]. 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 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. + +## B.7 OTA extreme test methods + +### B.7.1 Direct far field method + +The BS 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 RF-transparent boundary. Inside, a 'Radome like enclosure' contains an 'NR BS' (Network Radio Base Station). A 'Temperature control system' is connected to this enclosure. A 'Test system Calibrated point' is marked on the NR BS. A 'declared coordinate reference point and orientation' is indicated with axes θ and φ. A 'Test antenna' is positioned outside the enclosure, connected to 'Measurement equipment'.](15c6aea1b21929dc379fb3b7cf100d8c_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 RF-transparent boundary. Inside, a 'Radome like enclosure' contains an 'NR BS' (Network Radio Base Station). A 'Temperature control system' is connected to this enclosure. A 'Test system Calibrated point' is marked on the NR BS. A 'declared coordinate reference point and orientation' is indicated with axes θ and φ. A 'Test antenna' is positioned outside the enclosure, connected to 'Measurement equipment'. + +**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 BS under test is placed inside a small (compared to a far field chamber) anechoic chamber which is both RF a screened and suitable for environmental conditioning. The RF conditions inside the chamber are absorptive and capable of dissipating the power of the BS when radiating. A sample antenna or RF probe are placed in a location which gives a sample of the main beam EIRP but does not have to accurately measure the EIRP directly, instead the near-field response is measured. For this method test components are exposed to the full temperature range for example the test antenna/probe, cables, absorbers etc. may change as a function of temperature. + +Using the relative method it is also necessary to measure the EIRP under nominal conditions using an appropriately calibrated far field (or near filed) test range to obtain $P_{\text{max,c,EIRP}}$ . + +![Diagram of the measurement setup for extreme conditions for EIRP accuracy using the difference method. A central box labeled 'NR BS' is inside a 'Small shield anechoic and environmental chamber' (represented by a thick border with zigzag lines). A 'Temperature control system' box is connected to the left side of the chamber. A 'Test antenna/Probe' is positioned inside the chamber, pointing towards the 'NR BS'. The 'Test antenna/Probe' is connected to 'Measurement equipment' on the right.](56d829bcd0079ac2e963ee6df7bf540e_img.jpg) + +Diagram of the measurement setup for extreme conditions for EIRP accuracy using the difference method. A central box labeled 'NR BS' is inside a 'Small shield anechoic and environmental chamber' (represented by a thick border with zigzag lines). A 'Temperature control system' box is connected to the left side of the chamber. A 'Test antenna/Probe' is positioned inside the chamber, pointing towards the 'NR BS'. The 'Test antenna/Probe' is connected to 'Measurement equipment' on the 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_{\text{max,c,EIRP}}$ ) made in the appropriate far field or near field chamber and compared against the extreme requirement. As follows: + +$$P_{\text{max,c,EIRP, extreme}} = P_{\text{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 $\text{EIRP} = \text{EIRP}_{\text{p1}} + \text{EIRP}_{\text{p2}}$ . + +--- + +## Annex C (informative): Test tolerances and derivation of test requirements + +The test requirements explicitly defined in this specification have been calculated by relaxing the minimum requirements of the core specification TS 38.104 [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.104 [2] | Test Tolerance (TT OTA ) | Test requirement in the present document | +|------------------------------------------------------------------------|--------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------| +| 6.2 Radiated transmit power | See TS 38.104 [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 7.125$ 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 7.125$ GHz | Formula:
Upper limit + TT, Lower limit – TT | +| 6.3 OTA base station output power | See TS 38.104 [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 7.125$ GHz | Formula:
Upper limit + TT, Lower limit – TT | +| 6.4 OTA output power dynamics | See TS 38.104 [2], clause 9.4 | 0.4 dB | Formula:
Total power dynamic range – TT | +| 6.5.1 OTA transmitter OFF power | See TS 38.104 [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 7.125$ GHz | Formula:
Minimum Requirement + TT | +| 6.6.2 OTA frequency Error | See TS 38.104 [2], clause 9.6.1 | 12 Hz | Formula:
Frequency Error limit + TT | +| 6.6.3 OTA Modulation quality (EVM) | See TS 38.104 [2], clause 9.6.2 | 1% | Formula:
EVM limit + TT | +| 6.6.4 OTA time alignment error | See TS 38.104 [2], clause 9.6.3 | 25 ns | | +| 6.7.2 OTA occupied bandwidth | See TS 38.104 [2], clause 9.7.2 | 0 Hz | Formula:
Minimum Requirement + TT | +| 6.7.3 OTA Adjacent Channel Leakage Power Ratio (ACLR) | See TS 38.104 [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 7.125$ GHz

Absolute:
0 dB | Formula:
Relative limit - TT
Absolute limit + TT | +| 6.7.4 OTA operating band unwanted emissions | See TS 38.104 [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 7.125$ GHz

Offsets $\geq 10$ MHz: 0 dB

Additional limits for bands n50, n51, n74, n75, n76: 0 dB | Formula:
Minimum Requirement + TT | +| 6.7.5.2 General transmitter spurious emissions requirements Category A | See TS 38.104 [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.104 [2], clause 9.7.5.2.2 | 0 dB | Formula:
Minimum Requirement + TT | +| 6.7.5.3 Protection of the BS receiver of own or different BS | See TS 38.104 [2], clause 9.7.5.2.3 | 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 7.125$ GHz | Formula:
Minimum Requirement + TT | + +| | | | | +|------------------------------------------------------------------------------|-------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------| +| 6.7.5.4 Additional spurious emissions requirements | See TS 38.104 [2], clause 9.7.5.2.4 |

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 7.125 GHz

For co-existence with PHS:
0 dB

Additional limits for bands n50, n51, n74, n75, n76: 0 dB

| Formula:
Minimum Requirement + TT | +| 6.7.5.5 Co-location with other base stations | See TS 38.104 [2], clause 9.7.5.2.5 |

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 7.125 GHz

| Formula:
Minimum Requirement + TT | +| 6.8 OTA transmitter intermodulation | See TS 38.104 [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 OTA transmitter tests)** + +| Test | Minimum requirement in TS 38.104 [2] | Test Tolerance (TT OTA ) | Test requirement in the present document | +|------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------| +| 6.2 Radiated transmit power | Normal conditions:
1.7 dB, 24.25GHz < f ≤ 29.5GHz
2.0 dB, 37GHz < f ≤ 43.5GHz
2.2 dB, 43.5GHz < f ≤ 48.2GHz
[3.0] dB, 52.6GHz ≤ f ≤ 71GHz

Extreme conditions:
3.1 dB, 24.25GHz < f ≤ 29.5GHz
3.3 dB, 37GHz < f ≤ 43.5GHz
3.5 dB, 43.5GHz < f ≤ 48.2GHz
[3.9] dB, 52.6GHz ≤ f ≤ 71GHz | Normal conditions:
1.7 dB, 24.25GHz < f ≤ 29.5GHz
2.0 dB, 37GHz < f ≤ 43.5GHz
2.2 dB, 43.5GHz < f ≤ 48.2GHz
3.0 dB, 52.6GHz ≤ f ≤ 71GHz

Extreme conditions:
3.1 dB, 24.25GHz < f ≤ 29.5GHz
3.3 dB, 37GHz < f ≤ 43.5GHz
3.5 dB, 43.5GHz < f ≤ 48.2GHz
3.9 dB, 52.6GHz ≤ f ≤ 71GHz | Formula:
Upper limit + TT, Lower limit – TT | +| 6.3 OTA base station output power | 2.1 dB, 24.25GHz < f ≤ 29.5GHz
2.4 dB, 37GHz < f ≤ 43.5GHz
2.6 dB, 43.5GHz < f ≤ 48.2GHz
[4.7] dB, 52.6GHz ≤ f ≤ 71GHz | 2.1 dB, 24.25GHz < f ≤ 29.5GHz
2.4 dB, 37GHz < f ≤ 43.5GHz
2.6 dB, 43.5GHz < f ≤ 48.2GHz
3.2 dB, 52.6GHz ≤ f ≤ 71GHz | Formula:
Upper limit + TT, Lower limit – TT | +| 6.4 OTA output power dynamics | 0.4 dB | 0.4 dB | Formula:
Total power dynamic range – TT | +| 6.5.1 OTA transmitter OFF power | 2.9 dB, 24.25GHz < f ≤ 29.5GHz
3.3 dB, 37GHz < f ≤ 43.5GHz
3.6 dB, 43.5GHz < f ≤ 48.2GHz
[5.6] dB, 52.6GHz ≤ f ≤ 71GHz | 2.9 dB, 24.25GHz < f ≤ 29.5GHz
3.3 dB, 37GHz < f ≤ 43.5GHz
3.6 dB, 43.5GHz < f ≤ 48.2GHz
5.6 dB, 52.6GHz ≤ f ≤ 71GHz | Formula:
Minimum Requirement + TT | +| 6.6.2 OTA frequency Error | 12 Hz | 12 Hz | Formula:
Frequency Error limit + TT | +| 6.6.3 OTA Modulation quality (EVM) | 1 %
[1] %, 52.6GHz ≤ f ≤ 71GHz | 1 % | Formula:
EVM limit + TT | +| 6.6.4 OTA time alignment error | 25 ns | 25 ns | | +| 6.7.2 OTA occupied bandwidth | 0 Hz | 0 Hz | Formula:
Minimum Requirement + TT | + +| | | | | +|------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------| +| 6.7.3 OTA Adjacent Channel Leakage Power Ratio (ACLR) | Relative:
2.3 dB, 24.25GHz < f ≤ 29.5GHz
2.6 dB, 37GHz < f ≤ 43.5GHz
2.8 dB, 43.5GHz < f ≤ 48.2GHz
[5.2] dB, 52.6GHz ≤ f ≤ 71GHz

Absolute:
2.7 dB, 24.25GHz < f ≤ 29.5GHz
2.7 dB, 37GHz < f ≤ 43.5GHz
2.9 dB, 43.5GHz < f ≤ 48.2GHz
[5.3] dB, 52.6GHz ≤ f ≤ 71GHz | Relative:
2.3 dB, 24.25GHz < f ≤ 29.5GHz
2.6 dB, 37GHz < f ≤ 43.5GHz
2.8 dB, 43.5GHz < f ≤ 48.2GHz
4.6 dB, 52.6GHz ≤ f ≤ 71GHz

Absolute:
2.7 dB, 24.25GHz < f ≤ 29.5GHz
2.7 dB, 37GHz < f ≤ 43.5GHz
2.9 dB, 43.5GHz < f ≤ 48.2GHz
4.7 dB, 52.6GHz ≤ f ≤ 71GHz | Formula:
Relative limit - TT
Absolute limit + TT | +| 6.7.4 OTA operating band unwanted emissions | 0 MHz ≤ Δf < 0.1*BW contiguous
2.7 dB, 24.25GHz < f ≤ 29.5GHz
2.7 dB, 37GHz < f ≤ 43.5GHz
2.9 dB, 43.5GHz < f ≤ 48.2GHz
[5.3] dB, 52.6GHz ≤ f ≤ 71GHz

0.1*BW contiguous ≤ Δf < Δf max
0 dB

For co-existence with Earth Exploration Satellite Service 0 dB | 0 MHz ≤ Δf < 0.1*BW contiguous
2.7 dB, 24.25GHz < f ≤ 29.5GHz
2.7 dB, 37GHz < f ≤ 43.5GHz
2.9 dB, 43.5GHz < f ≤ 48.2GHz
4.7 dB, 52.6GHz ≤ f ≤ 71GHz

0.1*BW contiguous ≤ Δf < Δf max
0 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 | 0 dB | 0 dB | Formula:
Minimum Requirement + TT | +| 6.7.5.2 General transmitter spurious emissions requirements Category B | 0 dB | 0 dB | Formula:
Minimum Requirement + TT | +| 6.7.5.4 OTA transmitter spurious emissions, additional requirements | For co-existence with Earth Exploration Satellite Service 0 dB | 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.104 [2] | Test Tolerance (TT OTA ) | Test requirement in the present document | +|--------------------------------------------|--------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------| +| 7.2 OTA sensitivity | See TS 38.104 [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
1.9 dB, $6.0$ GHz $< f \leq 7.125$ GHz | Formula:
Declared Minimum EIS + TT | +| 7.3 OTA reference sensitivity level | See TS 38.104 [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
1.9 dB, $6.0$ GHz $< f \leq 7.125$ GHz | Formula:
$EIS_{REFSENS} + TT$ | +| 7.4 OTA dynamic range | See TS 38.104 [2], clause 10.4 | 0.3 dB, $f \leq 7.125$ GHz | Formula:
Wanted signal power + TT

Interferer signal power unchanged. | +| 7.5.1 OTA adjacent channel selectivity | See TS 38.104 [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.104 [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.104 [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.104 [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.104 [2], clause 10.6 | 0 dB | Formula:
Wanted signal power unchanged

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

Interferer signal power unchanged | +| 7.9 OTA in-channel selectivity | See TS 38.104 [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
2.8 dB, $6.0$ GHz $< f \leq 7.125$ 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 OTA receiver tests)** + +| Test | Minimum requirement in TS 38.104 [2] | Test Tolerance (TT OTA ) | Test requirement in the present document | +|----------------------------------------|--------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------| +| 7.3 OTA reference sensitivity level | See TS 38.104 [2], clause 10.3 | 2.4 dB, 24.25 GHz < f ≤ 33.4 GHz
2.4 dB, 37 GHz < f ≤ 43.5 GHz
3.5 dB, 43.5 GHz < f ≤ 48.2 GHz
3.0 dB, 52.6GHz ≤ f ≤ 71GHz | Formula:
EIS REFSENS + TT | +| 7.5.1 OTA adjacent channel selectivity | See TS 38.104 [2], clause 10.5.1 | 0 dB | Formula:
Wanted signal power + TT

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

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

Interferer signal power unchanged. | +| 7.9 OTA in-channel selectivity | See TS 38.104 [2], clause 10.9 | 3.4 dB, 24.25 GHz < f ≤ 33.4 GHz
3.4 dB, 37 GHz < f ≤ 43.5 GHz
5.1 dB, 43.5 GHz < f ≤ 48.2 GHz
4.0 dB, 52.6GHz ≤ f ≤ 71GHz | 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 + +**Table C.3-1: Derivation of test requirements (FR1 OTA performance tests)** + +| Test | Minimum Requirement in TS 38.104 [2] | Test Tolerance (TT OTA ) | Test requirement in the present document | +|----------------------------------------------------------------------------|--------------------------------------|-------------------------------------|-----------------------------------------------------------| +| 8.2.1 Performance requirements for PUSCH with transform precoding disabled | See clause 11.2.1.1 | 0.6 dB | Formula: SNR + TT OTA
T-put limit unchanged | +| 8.2.2 Performance requirements for PUSCH with transform precoding enabled | See clause 11.2.1.2 | 0.6 dB | Formula: SNR + TT OTA
T-put limit unchanged | +| 8.2.3 Performance requirements for UCI multiplexed on PUSCH | See clause 11.2.1.3 | 0.6 dB | Formula: SNR + TT OTA
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.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 | See clause 11.2.1.7 | 0.6 dB | Formula: SNR + TT OTA
BLER limit unchanged | +| 8.2.8 Performance requirements for PUSCH mapping type B with non-slot transmission | See clause 11.2.1.8 | 0.6 dB | Formula: SNR + TT OTA
T-put limit unchanged | +| 8.2.12 Performance requirements for PUSCH TB over Multi-Slots | See clause 11.2.1.12 | 0.6 dB | Formula: SNR + TT OTA
T-put limit unchanged | +| 8.2.13 Performance requirements for PUSCH with DM-RS bundling | See clause 11.2.1.13 | 0.6 dB | Formula: SNR + TT OTA
T-put limit unchanged | +| 8.3.1 Performance requirements for PUCCH format 0 | See clause 11.3.1.2 | 0.6 dB | Formula: SNR + TT OTA
False ACK limit unchanged
Correct ACK limit unchanged | +| 8.3.2 Performance requirements for PUCCH format 1 | See clause 11.3.1.3 | 0.6 dB | Formula: SNR + TT OTA
False ACK limit unchanged
False NACK limit unchanged
Correct ACK limit unchanged | +| 8.3.3 Performance requirements for PUCCH format 2 | See clause 11.3.1.4 | 0.6 dB | Formula: SNR + TT OTA
False ACK limit unchanged
Correct ACK limit unchanged
UCI BLER limit unchanged | +| 8.3.4 Performance requirements for PUCCH format 3 | See clause 11.3.1.5 | 0.6 dB | Formula: SNR + TT OTA
UCI BLER limit unchanged | +| 8.3.5 Performance requirements for PUCCH format 4 | See clause 11.3.1.6 | 0.6 dB | Formula: SNR + TT OTA
UCI BLER limit unchanged | +| 8.3.6 Performance requirements for multi-slot PUCCH | See clause 11.3.1.7 | 0.6 dB | Formula: SNR + TT OTA
False ACK limit unchanged
False NACK limit unchanged
Correct ACK limit unchanged | +| 8.3.11 Performance requirements for PUCCH sub-slot based repetition format 0 | See clause 11.3.1.10 | 0.6dB | Formula: SNR + TT OTA
False ACK limit unchanged
Correct ACK limit unchanged | +| 8.3.12 Performance requirements for PUCCH format 1 with DM-RS bundling | See clause 11.3.1.8 | 0.6 dB | Formula: SNR + TT OTA
False ACK limit unchanged
False NACK limit unchanged
Correct ACK limit unchanged | +| 8.3.13 Performance requirements for PUCCH format 3 with DM-RS bundling | See clause 11.3.1.9 | 0.6 dB | Formula: SNR + TT OTA
UCI BLER limit unchanged | +| 8.4.1 PRACH false alarm probability and missed detection | See clause 11.4.1 | 0.6 dB for fading cases
0.3 dB for AWGN cases | Formula: SNR + TT OTA
PRACH False detection limit unchanged
PRACH detection limit unchanged | +| 8.4.2 Performance requirements for PRACH for high speed train | 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 | +| 8.2.5 Performance requirements for UL timing adjustment | See clause 11.2.1.5 | 0.3 dB for AWGN cases | Formula: SNR + TT OTA
T-put limit unchanged | +| NOTE: TT values are applicable for normal condition unless otherwise stated. | | | | + +**Table C.3-2: Derivation of test requirements (FR2 OTA performance tests)** + +| Test | Minimum requirement in TS 38.104 [2] | Test Tolerance (TTOTA) | Test requirement in the present document | +|------------------------------------------------------------------------------------|---------------------------------------------|--------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------| +| 8.2.1 Performance requirements for PUSCH with transform precoding disabled | See clause 11.2.2.1 | 0.6 dB | Formula: SNR + TT OTA
T-put limit unchanged | +| 8.2.2 Performance requirements for PUSCH with transform precoding enabled | See clause 11.2.2.2 | 0.6 dB | Formula: SNR + TT OTA
T-put limit unchanged | +| 8.2.3 Performance requirements for UCI multiplexed on PUSCH | See clause 11.2.2.3 | 0.6 dB | Formula: SNR + TT OTA
BLER limit unchanged | +| 8.2.7 Performance requirements for PUSCH repetition Type A | See clause 11.2.2.4 | 0.6 dB | Formula: SNR + TT OTA
BLER limit unchanged | +| 8.2.8 Performance requirements for PUSCH mapping Type B with non-slot transmission | See clause 11.2.2.5 | 0.6 dB | Formula: SNR + TT OTA
T-put limit unchanged | +| 8.2.12 Performance requirements for PUSCH TB over Multi-Slots | See clause 11.2.2.9 | 0.6 dB | Formula: SNR + TT OTA
T-put limit unchanged | +| 8.2.13 Performance requirements for PUSCH with DM-RS bundling | See clause 11.2.2.10 | 0.6 dB | Formula: SNR + TT OTA
T-put limit unchanged | +| 8.3.1 Performance requirements for PUCCH format 0 | See clause 11.3.2.2 | 0.6 dB | Formula: SNR + TT OTA
False ACK limit unchanged
Correct ACK limit unchanged | +| 8.3.2 Performance requirements for PUCCH format 1 | See clause 11.3.2.3 | 0.6 dB | Formula: SNR + TT OTA
False ACK limit unchanged
False NACK limit unchanged
Correct ACK limit unchanged | +| 8.3.3 Performance requirements for PUCCH format 2 | See clause 11.3.2.4 | 0.6 dB | Formula: SNR + TT OTA
False ACK limit unchanged
Correct ACK limit unchanged
UCI BLER limit unchanged | +| 8.3.4 Performance requirements for PUCCH format 3 | See clause 11.3.2.5 | 0.6 dB | Formula: SNR + TT OTA
UCI BLER limit unchanged | +| 8.3.5 Performance requirements for PUCCH format 4 | See clause 11.3.2.6 | 0.6 dB | Formula: SNR + TT OTA
UCI BLER limit unchanged | +| 8.3.12 Performance requirements for PUCCH format 1 with DM-RS bundling | See clause 11.3.2.7 | 0.6 dB | Formula: SNR + TT OTA
False ACK limit unchanged
False NACK limit unchanged
Correct ACK limit unchanged | +| 8.3.13 Performance requirements for PUCCH format 3 with DM-RS bundling | See clause 11.3.2.8 | 0.6 dB | Formula: SNR + TT OTA
UCI BLER limit unchanged | +| 8.4.1 PRACH false alarm probability and missed detection | See clause 11.4.2 | 0.6 dB for fading cases
0.3 dB for AWGN cases | Formula: SNR + TT OTA
PRACH False detection limit unchanged
PRACH detection limit unchanged | + +NOTE: TT values are applicable for normal condition unless otherwise stated. + +--- + +## Annex D (normative): Calibration + +OTA test requirements specific and OTA measurement chamber specific calibration (and measurement) procedures were captured in TR 37.941 [29] 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 [29] for FR1 are assumed to be also applicable to *BS type 1-H* and *BS type 1-O* for the FR1 frequency range (i.e. up to 6 GHz), as well as for *BS type 2-O* for the FR2 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 (*BS 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 (BS type 2-O).](5ef9a81e819cc94dc0c6517896f31c6f_img.jpg) + +The diagram illustrates the measurement setup within a 'Test system enclosure' lined with sawtooth-shaped electromagnetic wave absorbers. Inside, an 'NR BS' (New Radio Base Station) is positioned on the left. A 'Calibrated point' is marked on a vertical dashed line above the BS. A 'declared coordinate reference point and orientation' is indicated by a dot at the center of the BS, with a vertical dashed line passing through it. Two angles, $\theta$ and $\phi$ , are shown originating from this reference point. On the right side of the enclosure, a 'Test antenna' is mounted on a stand, pointing towards the BS. This antenna is connected to 'Measurement equipment' located outside the enclosure on the right. + +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 (BS 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 (*BS 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, PWS, etc.). + +## E.1.2 OTA base station output power, OTA ACLR, OTA operating band unwanted emissions + +![Figure E.1.2-1: Measurement set up for OTA base station output power, OTA ACLR, OTA operating band unwanted emissions. The diagram shows a test system enclosure with a jagged border. Inside, an NR BS is mounted on a positioner, which is a circular platform. A 'Test system Calibrated point' is marked on the NR BS. A 'declared coordinate reference point and orientation' is indicated by a dashed line. The NR BS is connected to a 'Positioner'. A 'Test antenna' is positioned outside the enclosure, connected to a 'Measurement receiver'.](794f5ecb17da881f300b5dbcae23d88f_img.jpg) + +The diagram illustrates the measurement setup for OTA base station output power, OTA ACLR, and OTA operating band unwanted emissions. It features a test system enclosure with a jagged border. Inside, an NR BS is mounted on a positioner, which is a circular platform. A 'Test system Calibrated point' is marked on the NR BS. A 'declared coordinate reference point and orientation' is indicated by a dashed line. The NR BS is connected to a 'Positioner'. A 'Test antenna' is positioned outside the enclosure, connected to a 'Measurement receiver'. + +Figure E.1.2-1: Measurement set up for OTA base station output power, OTA ACLR, OTA operating band unwanted emissions. The diagram shows a test system enclosure with a jagged border. Inside, an NR BS is mounted on a positioner, which is a circular platform. A 'Test system Calibrated point' is marked on the NR BS. A 'declared coordinate reference point and orientation' is indicated by a dashed line. The NR BS is connected to a 'Positioner'. A 'Test antenna' is positioned outside the enclosure, connected to a 'Measurement receiver'. + +**Figure E.1.2-1: Measurement set up for OTA base station 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, PWS, etc.). + +## E.1.3 OTA spurious emissions + +![Figure E.1.3-1: Measurement set up for OTA spurious emissions. The diagram shows a test system enclosure with a jagged border. Inside, an NR BS is mounted on a positioner, which is a circular platform. A 'Test system Calibrated point' is marked on the NR BS. A 'declared coordinate reference point and orientation' is indicated by a dashed line. The NR BS is connected to a 'Positioner'. A 'Test antenna' is positioned outside the enclosure, connected to a 'Measurement receiver'.](b81e457e59b65ecf9be46c05a8e4b7c9_img.jpg) + +The diagram illustrates the measurement setup for OTA spurious emissions. It features a test system enclosure with a jagged border. Inside, an NR BS is mounted on a positioner, which is a circular platform. A 'Test system Calibrated point' is marked on the NR BS. A 'declared coordinate reference point and orientation' is indicated by a dashed line. The NR BS is connected to a 'Positioner'. A 'Test antenna' is positioned outside the enclosure, connected to a 'Measurement receiver'. + +Figure E.1.3-1: Measurement set up for OTA spurious emissions. The diagram shows a test system enclosure with a jagged border. Inside, an NR BS is mounted on a positioner, which is a circular platform. A 'Test system Calibrated point' is marked on the NR BS. A 'declared coordinate reference point and orientation' is indicated by a dashed line. The NR BS is connected to a 'Positioner'. A 'Test antenna' is positioned outside the enclosure, connected to a 'Measurement receiver'. + +**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 (BS type 1-O) + +![Figure E.1.4-1: Measurement set up for OTA co-location emissions, OTA transmit ON/OFF power (BS type 1-O).](ef8af6989f67e7a666533db9b903dfcf_img.jpg) + +The diagram illustrates the measurement setup for OTA co-location emissions. It features a circular 'Test system enclosure' lined with sawtooth-shaped electromagnetic wave absorbers. Inside the enclosure, an 'NR BS' (New Radio Base Station) is mounted on a 'Positioner' that allows for rotation. A 'Calibrated point' is marked on the NR BS, and a 'declared coordinate reference point and orientation' is indicated. A 'Co-Location Test Antenna' is positioned near the NR BS. A 'Test antenna' is located outside the enclosure, connected to a 'Measurement receiver'. A red line connects the NR BS to a 'Switch, limiter or filter', which is then connected to a 'Measurement Device'. + +Figure E.1.4-1: Measurement set up for OTA co-location emissions, OTA transmit ON/OFF power (BS type 1-O). + +**Figure E.1.4-1: Measurement set up for OTA co-location emissions, OTA transmit ON/OFF power (BS 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, PWS (NOTE), etc.). + +NOTE: The maximum rated Power Density (PD) per section of the PWS area (e.g. dBm/cm2) might be restricted depending on the implementation. This Power Density at a specific reference plane can be calculated for each transmitter as a function of the total radiated power, the test distance and the radiation pattern of the transmitter. + +## E.1.5 OTA transmitter intermodulation + +![Diagram of the measurement setup for OTA transmitter intermodulation. A test system enclosure with sawtooth walls contains a 'Test system Calibrated point' and a 'declared coordinate reference point and orientation'. A 'Test antenna' is connected to a 'Measurement receiver'. A 'Co-Location Test Antenna' is connected to a 'Signal Generator for the interfering signal'. A 'Positioner' and 'NR BS' are also shown within the enclosure.](5387e60d72dd1cdc4eacd4a37499e9db_img.jpg) + +The diagram illustrates the measurement setup for OTA transmitter intermodulation. It features a 'Test system enclosure' with sawtooth walls. Inside, a 'Test system Calibrated point' and a 'declared coordinate reference point and orientation' are marked. A 'Test antenna' is connected to a 'Measurement receiver'. A 'Co-Location Test Antenna' is connected to a 'Signal Generator for the interfering signal'. A 'Positioner' and 'NR BS' are also shown within the enclosure. The 'Test system Calibrated point' is connected to the 'declared coordinate reference point and orientation' by a dashed line. The 'Test antenna' is connected to the 'Measurement receiver' by a solid line. The 'Co-Location Test Antenna' is connected to the 'Signal Generator for the interfering signal' by a solid line. The 'Positioner' and 'NR BS' are connected to the 'Test system Calibrated point' by a dashed line. The 'Test system Calibrated point' is connected to the 'declared coordinate reference point and orientation' by a dashed line. The 'Test antenna' is connected to the 'Measurement receiver' by a solid line. The 'Co-Location Test Antenna' is connected to the 'Signal Generator for the interfering signal' by a solid line. The 'Positioner' and 'NR BS' are connected to the 'Test system Calibrated point' by a dashed line. + +Diagram of the measurement setup for OTA transmitter intermodulation. A test system enclosure with sawtooth walls contains a 'Test system Calibrated point' and a 'declared coordinate reference point and orientation'. A 'Test antenna' is connected to a 'Measurement receiver'. A 'Co-Location Test Antenna' is connected to a 'Signal Generator for the interfering signal'. A 'Positioner' and 'NR BS' are also shown within the enclosure. + +**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, PWS (NOTE), 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. + +**NOTE:** The maximum rated Power Density (PD) per section of the PWS area (e.g. dBm/cm2) might be restricted depending on the implementation. This Power Density at a specific reference plane can be calculated for each transmitter as a function of the total radiated power, the test distance and the radiation pattern of the transmitter. + +## 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](0dae8b268a9af5498a783511f7993d8c_img.jpg) + +The diagram illustrates the measurement setup for OTA sensitivity and OTA reference sensitivity level. It shows a test system enclosure with a jagged border. Inside, on the left, a 'Signal generator for the wanted signal' is connected to a 'Test antenna'. A label 'Test antenna polarisation can be adjusted' points to this antenna. On the right, an 'NR BS' (Next Generation NodeBase Station) is shown. A 'Test system Calibrated point' is marked on the NR BS. A coordinate system is defined with a 'declared coordinate reference point and orientation' at the origin (0). The angles $\theta$ and $\varphi$ are indicated. The entire setup is enclosed in a 'Test system enclosure'. + +Figure E.2.1-1: Measurement set up for OTA sensitivity and OTA reference sensitivity level + +**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, PWS, etc.). + +### E.2.2 OTA dynamic range + +![Figure E.2.2-1: Measurement set up for OTA dynamic range](1459b35539dc68bda6750123e67497be_img.jpg) + +The diagram illustrates the measurement setup for OTA dynamic range. It shows a test system enclosure with a jagged border. On the left, two signal generators are shown: 'Signal Generator for the wanted signal' connected to 'ATT1' and 'Signal Generator for the AWGN interfering signal' connected to 'ATT2'. Both ATT1 and ATT2 are connected to a 'Hybrid'. The output of the Hybrid is connected to a 'Test antenna'. A label 'Test antenna polarisation can be adjusted' points to this antenna. On the right, an 'NR BS' (Next Generation NodeBase Station) is shown. A 'Test system Calibrated point' is marked on the NR BS. A coordinate system is defined with a 'declared coordinate reference point and orientation' at the origin (0). The angles $\theta$ and $\varphi$ are indicated. The entire setup is enclosed in a 'Test system enclosure'. + +Figure E.2.2-1: Measurement set up for OTA dynamic range + +**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, PWS, 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 antenna is positioned at a declared coordinate reference point and orientation. The Test system has a Calibrated point. The Test system enclosure contains an NR BS. The Test antenna is at an angle θ from the vertical axis and an angle φ from the horizontal axis.](dd3bdc670c443b40676e413a4367b9da_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 antenna is positioned at a declared coordinate reference point and orientation. The Test system has a Calibrated point. The Test system enclosure contains an NR BS. The Test antenna is at an angle θ from the vertical axis and an angle φ from the horizontal axis. + +**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, PWS, etc.). + +![Figure E.2.3-2: Measurement set up for general OTA 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 Termination. The Termination is connected to a Test antenna inside a Test system enclosure. The Test antenna's polarization can be adjusted. The Test antenna is positioned at a declared coordinate reference point and orientation. The Test system has a Calibrated point. The Test system enclosure contains an NR BS. The Test antenna is at an angle θ from the vertical axis and an angle φ from the horizontal axis.](701d39c5ca98f4045e3e0db67c9a267a_img.jpg) + +Figure E.2.3-2: Measurement set up for general OTA 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 Termination. The Termination is connected to a Test antenna inside a Test system enclosure. The Test antenna's polarization can be adjusted. The Test antenna is positioned at a declared coordinate reference point and orientation. The Test system has a Calibrated point. The Test system enclosure contains an NR BS. The Test antenna is at an angle θ from the vertical axis and an angle φ from the horizontal axis. + +**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, PWS, etc.). + +## E.2.4 OTA blocking + +### E.2.4.1 General OTA out-of-band blocking + +![Diagram of measurement setup for general OTA out-of-band blocking. It shows a test system enclosure with two signal generators (wanted and interfering) connected to test antennas (in band and out of band) on the left. On the right, an NR BS is positioned at a calibrated point with a coordinate reference point and orientation (theta, phi).](9e33e281350dad2ba558efa5407770de_img.jpg) + +The diagram illustrates the measurement setup for general OTA out-of-band blocking. It features a rectangular test system enclosure with jagged edges representing the walls. Inside, on the left, are two signal generators: 'Signal Generator for the wanted signal' and 'Signal Generator for the interfering signal'. These are connected to two test antennas: 'Test antenna (in band)' and 'Test antenna (out of band)'. A label 'Test antenna polarisation can be adjusted' points to these antennas. On the right side of the enclosure is an 'NR BS' (New Radio Base Station) represented by a square box. A 'Test system Calibrated point' is marked with a dashed vertical line. A 'declared coordinate reference point and orientation' is indicated by a dot at the center of the NR BS, with angles $\theta$ and $\phi$ shown. The entire setup is labeled 'Test system enclosure' at the bottom right. + +Diagram of measurement setup for general OTA out-of-band blocking. It shows a test system enclosure with two signal generators (wanted and interfering) connected to test antennas (in band and out of band) on the left. On the right, an NR BS is positioned at a calibrated point with a coordinate reference point and orientation (theta, phi). + +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, PWS, etc.). + +### E.2.4.2 OTA co-location blocking + +![Diagram of measurement setup for OTA co-location blocking. It shows a test system enclosure with a wanted signal generator and test antenna on the left, and an NR BS with a co-location test antenna on the right. An interfering signal generator is connected to an amplifier outside the enclosure, with its output entering the enclosure to interfere with the co-location test antenna.](d88324d357512f1306e8cdac68f80fd3_img.jpg) + +The diagram illustrates the measurement setup for OTA co-location blocking. It shows a rectangular test system enclosure. Inside, on the left, a 'Signal Generator for the wanted signal' is connected to a 'Test antenna (in band)', with a label 'Test antenna polarisation can be adjusted'. On the right, an 'NR BS' is shown with a 'Co-Location Test Antenna' inside it. A 'Test system Calibrated point' is marked with a dashed vertical line, and a 'declared coordinate reference point and orientation' is indicated by a dot at the center of the NR BS with angles $\theta$ and $\phi$ . Outside the enclosure at the bottom, a 'Signal Generator for the interfering signal' is connected to an amplifier. The output of this amplifier enters the enclosure through a red line, pointing towards the 'Co-Location Test Antenna'. The entire setup is labeled 'Test system enclosure' at the bottom right. + +Diagram of measurement setup for OTA co-location blocking. It shows a test system enclosure with a wanted signal generator and test antenna on the left, and an NR BS with a co-location test antenna on the right. An interfering signal generator is connected to an amplifier outside the enclosure, with its output entering the enclosure to interfere with the co-location test antenna. + +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, PWS (NOTE), etc.). For testing blocking far out-of-band several CLTAs might be needed. + +NOTE: The maximum rated Power Density (PD) per section of the PWS area (e.g. dBm/cm2) might be restricted depending on the implementation. This Power Density at a specific reference plane can be calculated for each transmitter as a function of the total radiated power, the test distance and the radiation pattern of the transmitter. + +## E.2.5 OTA receiver spurious emissions + +![Figure E.2.5-1: Measurement set up for OTA receiver spurious emissions. The diagram shows a test system enclosure with anechoic chamber walls. Inside, a 'Test system Calibrated point' is marked on a 'Positioner' which holds an 'NR BS' (Non-Reference Base Station). A 'declared coordinate reference point and orientation' is indicated. A 'Test antenna' is positioned outside the enclosure, connected to a 'Measurement receiver'. The diagram also shows the angular coordinates theta and phi for the test antenna's orientation.](5dcbbe47fca438acf7d505a856fd40a7_img.jpg) + +Figure E.2.5-1: Measurement set up for OTA receiver spurious emissions. The diagram shows a test system enclosure with anechoic chamber walls. Inside, a 'Test system Calibrated point' is marked on a 'Positioner' which holds an 'NR BS' (Non-Reference Base Station). A 'declared coordinate reference point and orientation' is indicated. A 'Test antenna' is positioned outside the enclosure, connected to a 'Measurement receiver'. The diagram also shows the angular coordinates theta and phi for the test antenna's orientation. + +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 + +![Figure E.2.6-1: Measurement set up for OTA receiver intermodulation. The diagram shows three signal generators on the left: 'Signal Generator for the wanted signal', 'Signal Generator for the CW interfering signal', and 'Signal Generator for the modulated interfering signal'. Each is connected to an attenuator (ATT1, ATT2, ATT3) and then to a hybrid combiner. The output of the hybrid is connected to a 'Test antenna' inside a test system enclosure. The test antenna's polarization can be adjusted. Inside the enclosure, there is an 'NR BS' (Non-Reference Base Station) on a 'Positioner' at a 'Test system Calibrated point'. A 'declared coordinate reference point and orientation' is also shown. The diagram includes angular coordinates theta and phi.](2a687a9dad17eb1f0512bb384fa2fdc8_img.jpg) + +Figure E.2.6-1: Measurement set up for OTA receiver intermodulation. The diagram shows three signal generators on the left: 'Signal Generator for the wanted signal', 'Signal Generator for the CW interfering signal', and 'Signal Generator for the modulated interfering signal'. Each is connected to an attenuator (ATT1, ATT2, ATT3) and then to a hybrid combiner. The output of the hybrid is connected to a 'Test antenna' inside a test system enclosure. The test antenna's polarization can be adjusted. Inside the enclosure, there is an 'NR BS' (Non-Reference Base Station) on a 'Positioner' at a 'Test system Calibrated point'. A 'declared coordinate reference point and orientation' is also shown. The diagram includes angular coordinates theta and phi. + +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, PWS, etc.). + +## E.2.7 OTA in-channel selectivity + +![Measurement set up for OTA in-channel selectivity diagram](07203f762dabc167b043a1c4bdc1493c_img.jpg) + +This diagram illustrates the measurement setup for OTA in-channel selectivity. On the left, a 'Signal Generator for the wanted signal and the interfering signal' is connected to a 'Hybrid' component. The output of the hybrid is connected to a 'Test antenna'. A label indicates that the 'Test antenna polarisation can be adjusted'. The test antenna is positioned inside a 'Test system enclosure' lined with electromagnetic wave absorbers. Inside the enclosure, there is a 'Test system Calibrated point' and an 'NR BS' (Next Generation Base Station). The NR BS is shown with a coordinate system where $\theta$ represents the elevation angle and $\phi$ represents the azimuth angle, with the origin at the 'declared coordinate reference point and orientation'. + +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, PWS, etc.). + +## E.3 Performance requirements + +![Measurement set up for single TX, single demodulation branch radiated performance requirements diagram](54f3455c3fc6038d4a5baa771a3b6e0e_img.jpg) + +This diagram illustrates the measurement setup for single TX, single demodulation branch radiated performance requirements. It shows two signal paths entering a 'Hybrid' component. The first path consists of a 'Signal generator for the AWGN signal' followed by an attenuator 'ATT1'. The second path consists of a 'Signal generator for the wanted signal' followed by a 'Fading channel emulator #1' and an attenuator 'ATT2'. The output of the hybrid is connected to a Power Amplifier ('PA'). The PA is connected to a 'Test antenna' inside a 'Test system enclosure' lined with electromagnetic wave absorbers. Inside the enclosure, there is an 'NR BS' (Next Generation Base Station) with a coordinate system where $\theta$ represents the elevation angle and $\phi$ represents the azimuth angle, with the origin at the 'NR BS declared coordinate reference point and orientation'. + +Measurement set up for single TX, single demodulation branch radiated performance requirements diagram + +Figure E.3-1: Measurement set up for single TX, single demodulation branch radiated performance requirements + +![Figure E.3-2: Measurement set up for single TX, dual polarization radiated performance requirements. The diagram shows a signal generator for the first AWGN signal connected to ATT1, and a signal generator for the wanted signal connected to Fading channel emulator #1 and Fading channel emulator #2. These are connected to ATT2 and ATT3 respectively. Both ATT2 and ATT3 are connected to Hybrid 2. ATT1 is connected to Hybrid 1. Hybrid 1 is connected to PA 1, and Hybrid 2 is connected to PA 2. Both PA 1 and PA 2 are connected to a Test system enclosure. Inside the enclosure, there are two test antennas labeled 'Test antenna polarization A' and 'Test antenna polarization B'. An NR BS is shown with a coordinate system (theta, phi) and a label 'NR BS declared coordinate reference point and orientation'.](9c575767fe4409cdd2898df6f70139f5_img.jpg) + +Figure E.3-2: Measurement set up for single TX, dual polarization radiated performance requirements. The diagram shows a signal generator for the first AWGN signal connected to ATT1, and a signal generator for the wanted signal connected to Fading channel emulator #1 and Fading channel emulator #2. These are connected to ATT2 and ATT3 respectively. Both ATT2 and ATT3 are connected to Hybrid 2. ATT1 is connected to Hybrid 1. Hybrid 1 is connected to PA 1, and Hybrid 2 is connected to PA 2. Both PA 1 and PA 2 are connected to a Test system enclosure. Inside the enclosure, there are two test antennas labeled 'Test antenna polarization A' and 'Test antenna polarization B'. An NR BS is shown with a coordinate system (theta, phi) and a label 'NR BS declared coordinate reference point and orientation'. + +Figure E.3-2: Measurement set up for single TX, dual polarization radiated performance requirements + +![Figure E.3-3: Measurement set up for dual TX, dual polarization radiated performance requirements. The diagram shows two signal generators for the wanted signal, labeled Tx1 and Tx2. Tx1 is connected to Fading channel emulator #1 and Fading channel emulator #2. Tx2 is connected to Fading channel emulator #3 and Fading channel emulator #4. Fading channel emulator #1 and #2 are connected to Hybrid 1. Fading channel emulator #3 and #4 are connected to Hybrid 2. Hybrid 1 is connected to ATT1 and ATT2. Hybrid 2 is connected to ATT3 and ATT4. ATT1 and ATT2 are connected to Hybrid 3. ATT3 and ATT4 are connected to Hybrid 4. Hybrid 3 is connected to PA 1, and Hybrid 4 is connected to PA 2. Both PA 1 and PA 2 are connected to a Test system enclosure. Inside the enclosure, there are two test antennas labeled 'Test antenna polarization A' and 'Test antenna polarization B'. An NR BS is shown with a coordinate system (theta, phi) and a label 'NR BS declared coordinate reference point and orientation'.](032a41557f10f862ab4bf7a1b20cbfd7_img.jpg) + +Figure E.3-3: Measurement set up for dual TX, dual polarization radiated performance requirements. The diagram shows two signal generators for the wanted signal, labeled Tx1 and Tx2. Tx1 is connected to Fading channel emulator #1 and Fading channel emulator #2. Tx2 is connected to Fading channel emulator #3 and Fading channel emulator #4. Fading channel emulator #1 and #2 are connected to Hybrid 1. Fading channel emulator #3 and #4 are connected to Hybrid 2. Hybrid 1 is connected to ATT1 and ATT2. Hybrid 2 is connected to ATT3 and ATT4. ATT1 and ATT2 are connected to Hybrid 3. ATT3 and ATT4 are connected to Hybrid 4. Hybrid 3 is connected to PA 1, and Hybrid 4 is connected to PA 2. Both PA 1 and PA 2 are connected to a Test system enclosure. Inside the enclosure, there are two test antennas labeled 'Test antenna polarization A' and 'Test antenna polarization B'. An NR BS is shown with a coordinate system (theta, phi) and a label 'NR BS declared coordinate reference point and orientation'. + +Figure E.3-3: Measurement set up for dual TX, dual polarization radiated performance requirements + +![Figure E.3-4: Measurement set up for UL timing adjustment, single TX, dual polarization radiated performance requirements. The diagram shows a signal generator for the first AWGN signal connected to ATT1, and a signal generator for the wanted signal connected to Fading channel emulator #1. These are connected to Hybrid 1. Hybrid 1 is connected to ATT2 and ATT3. ATT2 is connected to Hybrid 2, and ATT3 is connected to Hybrid 3. Hybrid 2 is connected to PA 1, and Hybrid 3 is connected to PA 2. Both PA 1 and PA 2 are connected to a Test system enclosure. Inside the enclosure, there are two test antennas labeled 'Test antenna polarization A' and 'Test antenna polarization B'. An NR BS is shown with a coordinate system (theta, phi) and a label 'NR BS declared coordinate reference point and orientation'.](7bcbec1a44e47d72995323f51516b314_img.jpg) + +Figure E.3-4: Measurement set up for UL timing adjustment, single TX, dual polarization radiated performance requirements. The diagram shows a signal generator for the first AWGN signal connected to ATT1, and a signal generator for the wanted signal connected to Fading channel emulator #1. These are connected to Hybrid 1. Hybrid 1 is connected to ATT2 and ATT3. ATT2 is connected to Hybrid 2, and ATT3 is connected to Hybrid 3. Hybrid 2 is connected to PA 1, and Hybrid 3 is connected to PA 2. Both PA 1 and PA 2 are connected to a Test system enclosure. Inside the enclosure, there are two test antennas labeled 'Test antenna polarization A' and 'Test antenna polarization B'. An NR BS is shown with a coordinate system (theta, phi) and a label 'NR BS declared coordinate reference point and orientation'. + +Figure E.3-4: Measurement set up for UL timing adjustment, single TX, dual polarization radiated performance requirements + +The OTA chambers shown in figures E.3-1, E.3-2, E.3-3 and E.3-4 are intended to be generic and can be replaced with any suitable OTA chamber (e.g. far field anechoic chamber, CATR, etc.). The PA(s) depicted in figures E.3-1, E.3-2, E.3-3 and E.3-4 is optional. Fading channel emulators are included when needed according to the requirement description. + +NOTE: The HARQ Feedback (only for PUSCH) could be done as an RF feedback or as a digital feedback. The HARQ Feedback should be error free. + +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 2D plane with a vertical axis labeled θ and a horizontal axis labeled φ. A dashed ellipse represents the 'OTA peak directions set', with five red 'X' marks inside it. The area outside the ellipse is labeled 'Out of cell directions set'. The bottom part is a power level graph with a horizontal axis labeled φ. It shows a red curve representing 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)'.](e76fde14f7de3365b3c30570652890e6_img.jpg) + +The figure illustrates the spatial emission characteristics of a transmitter. The top part, titled 'Directions diagram', shows a 2D coordinate system with a vertical axis labeled $\theta$ and a horizontal axis labeled $\varphi$ . A dashed ellipse represents the 'OTA peak directions set', which is the region where the transmitter is intended to emit. Inside this ellipse, there are five red 'X' marks. The area outside the ellipse is labeled 'Out of cell directions set'. The bottom part is a power level graph with a horizontal axis labeled $\varphi$ . It shows a red curve representing 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 2D plane with a vertical axis labeled θ and a horizontal axis labeled φ. A dashed ellipse represents the 'OTA peak directions set', with five red 'X' marks inside it. The area outside the ellipse is labeled 'Out of cell directions set'. The bottom part is a power level graph with a horizontal axis labeled φ. It shows a red curve representing 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 | +|------------------------|---------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| +| DE.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. | +| DE.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 (D.8, D.10) | +| DE.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 (D.8, D.10) | +| DE.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 (D.8, D.10). | +| 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 (D.8, D.10) | + +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 + +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 [20]. Mapping of PUSCH modulation to receiver requirement are specified in table H-1. + +**Table H-1: Modulation of the interfering signal** + +| Receiver requirement | Modulation | +|-----------------------------------------------------------|------------| +| OTA in-channel selectivity | 16QAM | +| OTA adjacent channel selectivity and narrow-band blocking | QPSK | +| General OTA blocking | QPSK | +| OTA receiver intermodulation | QPSK | + +# Annex I (normative): TRP measurement procedures + +## I.1 General + +The annex describes various procedures for BS OTA TRP measurements. These procedures can provide either an accurate or an over-estimate of TRP values. The procedures for an accurate estimate can be applied to all TRP requirements. However, if a TRP requirement does not need accurate TRP estimate then the procedures for over-estimate of TRP may be used in order to have a reasonable OTA test time. Pre-scan does not provide an accurate TRP estimate or over-estimate of TRP. Pre-scan is a fast but coarse method that is used to identify the spurious emission frequencies with emission power as described in annex I.13. A sequential measurement is then made at the emission frequencies, to assess the TRP as described in annex I.2 to annex I.9. + +When making TRP measurements the alignment between EUT and measurement antenna is important to achieve expected measurement uncertainty: + +1. The measurement antenna needs to be aligned tangential to the measurement surface forming a sphere around the EUT, in order to correctly measure the TRP properly. +2. Test methods described in clauses I.5.1, I.5.2, I.10, I.11 and I.12 require angular alignment between the selected measurement grid and EUT radiation pattern in order to measure peak values in the main beams. Angular misalignment can lead to differences in the actual and measured angular positions of the intended maximum EIRP. +3. Test methods described in clause I.5.3, I.6 and I.9 are designed to be independent of rotations of the angular grid, and hence angular alignment between the measurement grid and EUT is not needed. + +## I.2 Spherical equal angle grid + +### I.2.1 General + +$TRP_{\text{Estimate}}$ is defined as + +when EIRP measurements is used or as + +when power density measurements are used, and $d$ is the test distance. $N$ and $M$ are the number of samples in the $\theta$ and $\phi$ angles. Each $(\theta_i, \phi_j)$ is a sampling point. The sampling angular intervals for $\theta$ and $\phi$ angles are $\Delta\theta$ and $\Delta\phi$ . The sampling intervals and are described in I.2.2. + +### I.2.2 Reference angular step criteria + +The reference angular steps $\Delta\theta$ and $\Delta\phi$ in degrees are defined as: + +The upper limit for these reference angular steps of $\Delta\theta$ ensures a low Summation Error (SE) when $d$ is large compared to the EUT dimensions. + +$D_{\text{cyl}}$ and $D$ are calculated as: + +, + +The definition of $d$ , $w$ and $h$ is shown in figure I.2.2-1. The radiation source can be EUT antenna array or the whole of EUT. + +![Figure I.2.2-1: Dimensions of a radiation source: depth (d), width (w) and height (h). The diagram shows a 3D coordinate system with x, y, and z axes. A rectangular prism representing the radiation source is positioned at the origin. The height of the prism along the z-axis is labeled h, the width along the x-axis is labeled w, and the depth along the y-axis is labeled d. A red vector labeled P points from the origin to a point on the surface of the prism. The angle between the z-axis and the vector P is labeled theta. The angle between the x-axis and the projection of the vector P onto the xy-plane is labeled phi. Dashed lines indicate the projection of the vector P onto the xy-plane and the z-axis.](700d7b9748b3f21b6381998882dd61ea_img.jpg) + +Figure I.2.2-1: Dimensions of a radiation source: depth (d), width (w) and height (h). The diagram shows a 3D coordinate system with x, y, and z axes. A rectangular prism representing the radiation source is positioned at the origin. The height of the prism along the z-axis is labeled h, the width along the x-axis is labeled w, and the depth along the y-axis is labeled d. A red vector labeled P points from the origin to a point on the surface of the prism. The angle between the z-axis and the vector P is labeled theta. The angle between the x-axis and the projection of the vector P onto the xy-plane is labeled phi. Dashed lines indicate the projection of the vector P onto the xy-plane and the z-axis. + +**Figure I.2.2-1: Dimensions of a radiation source: depth (d), width (w) and height (h)** + +Optionally, in the case of Uniform Linear Array (ULA), when $d$ is negligible ( $d \approx 0$ ) and the EUT is mounted along the yz plane as shown in figure I.2.2-2, the reference angular steps, in degrees, can be determined by + +Where $D_y$ is the length of radiating parts of EUT along y-axis, $D_z$ is the length of radiating parts of EUT along the z-axis and $\lambda$ is wavelength for the measured frequency. + +![Figure I.2.2-2: Spherical coordinate system for OTA conformance testing of EUT. The diagram shows a sphere centered at the origin of a 3D Cartesian coordinate system with x, y, and z axes. A point on the sphere is defined by its radial distance K (labeled as Kz and Ky in the diagram), its polar angle theta (θ) measured from the positive z-axis, and its azimuthal angle phi (φ) measured from the positive x-axis in the xy-plane. A small grey rectangular block representing the EUT is positioned at the center of the sphere.](f8d7f8ccdb986d4a88d3c5f0a29f838a_img.jpg) + +Figure I.2.2-2: Spherical coordinate system for OTA conformance testing of EUT. The diagram shows a sphere centered at the origin of a 3D Cartesian coordinate system with x, y, and z axes. A point on the sphere is defined by its radial distance K (labeled as Kz and Ky in the diagram), its polar angle theta (θ) measured from the positive z-axis, and its azimuthal angle phi (φ) measured from the positive x-axis in the xy-plane. A small grey rectangular block representing the EUT is positioned at the center of the sphere. + +**Figure I.2.2-2: Spherical coordinate for OTA conformance testing of EUT** + +Where due to practical reasons such as time constraints or turn-table precision, measurement with the reference steps is not practical, sparser grids can be used. Use of sparse grids can lead to errors in TRP assessment. In order to characterize these errors, the SF (sparsity factor) of the grid is defined as + +Where $\Delta\theta$ and $\Delta\phi$ are the actual angular steps used in the measurement. + +Alternatively, when EUT radiating dimensions are not known, for each frequency within the *downlink operating band* including $\Delta f_{\text{OBUE}}$ , the reference angular steps can be specified in terms of the *beamwidth* of the wanted signal as + +where $\lambda_0$ is the wavelength of the wanted signal, and $\text{BeW}_\phi$ and $\text{BeW}_\theta$ are the *beamwidth* of the wanted signal in the $\phi$ -axis and $\theta$ -axis, respectively. + +$\text{BeW}_\phi$ and $\text{BeW}_\theta$ may be set to *beamwidth* declared for the OTA BS radiated transmit power requirement provided the same *beam* is applied to test in-band TRP requirements. + +NOTE: *Beamwidth* is approximately equal to half the first-null beam width. + +## I.3 Spherical equal area grid + +$\text{TRP}_{\text{Estimate}}$ is defined as + +N is the total number of samples and specified as + +The sampling intervals $\Delta\theta$ and $\Delta\phi$ are described in annex I.2.2. Each $(\theta, \phi)$ is a sampling point. + +## 1.4 Spherical Fibonacci grid + +$TRP_{Estimate}$ is defined as + +$N$ is the total number of samples and specified as + +The sampling intervals $\Delta\theta$ and $\Delta\phi$ are described in annex I.2.2. Each $(\theta, \phi)$ is a sampling point, where $\theta$ and $\phi$ , in degrees, are defined as: + +## 1.5 Orthogonal cut grid + +### 1.5.1 General + +Here, at least two cuts (default) shall be used, an optional third cut can be used. The alignment of the cuts must be along the symmetry planes of the antenna array. No alignment is required for spurious emissions. + +When alignment is required: + +- 1) The first mandatory cut is a horizontal cut passing through the peak direction of the main beam. +- 2) The second mandatory is a vertical cut passing through the peak direction of the main beam. Using the data from these two mandatory cuts, a conditional pattern multiplication can be used. +- 3) The third optional cut is a vertical cut orthogonal to the first and the second cut. + +When alignment is not required, the cuts can be aligned arbitrarily. + +Once the number and the orientation of the cuts are decided, the total EIRP is measured on the orthogonal cuts and the TRP is then calculated as follows: First the contributions from each cut is calculated as + +where $P$ is the number of sampling points in the cut. The final contribution for all cuts is calculated as + +where $N$ is the number of cuts. Note that when orthogonal cuts are measured, the interclause points are measured multiple times and the repeated values can be removed from the samples before averaging. + +When two cuts measurements are used, a conditional pattern multiplication can be applied. The following are the conditions for applying pattern multiplication: + +- i. The vertical cut (and the main beam) is in the $\theta$ -plane +- ii. The frequency of the emission is within the downlink operating band. +- iii. The bandwidth of the emission is the same as the bandwidth of the in-band modulated signal +- iv. The emission appears/disappears when the Tx power is turned on/off. +- v. The antenna arrays of the EUT + - 1) Have rectangular grids of antenna element positions + - 2) Have symmetry planes that are vertical and horizontal. + +### 3) Have parallel antenna planes + +The antenna array is here assumed to be placed in the $yz$ -plane. The pattern multiplication is performed in $uv$ -coordinates and the data in the two cuts are denoted $\phi$ at $u = 0$ and a vertical cut with data $\phi$ at $v = 0$ . The data is split in two parts corresponding to the forward and backward hemispheres. The $uv$ -coordinates are the projections of the angular directions onto the antenna plane, here the $yz$ -plane. Using the spherical coordinates as depicted in figure I.2.2-1 the $u$ and $v$ coordinates are defined as: + +Note that only the data on the cuts are measured. + +Calculate power density/EIRP values outside the two cardinal cuts as + +The pattern multiplication is applied separately for the forward (fwd) and backward (bwd) hemisphere. The TRP is then calculated as + +NOTE: The numerical singularity at $\phi = 0$ must be treated with care, e.g. by change of variables. + +## I.5.2 Operating band unwanted emissions + +The procedure is as follows: + +- 1) Follow steps described in annex I.5.1 for the first two mandatory cuts and calculate the $TRP_{Estimate}$ . +- 2) Compare the $TRP_{Estimate}$ to the limit. +- 3) If the $TRP_{Estimate}$ is above the limit, perform the measurement on an additional third cut and repeat steps 1 to 2. + +## I.5.3 Spurious unwanted emissions + +The procedure is as follows: + +- 1) Follow steps described in annex I.5.1 for two cuts and calculate the preliminary $TRP_{Estimate}$ . +- 2) Add the appropriate correction factor $\Delta TRP$ according to table I.5.3-1 to ensure overestimation with 95% confidence. +- 3) Compare the corrected $TRP_{Estimate}$ (including $\Delta TRP$ ) to the limit. +- 4) If the corrected $TRP_{Estimate}$ is above the limit, perform the measurement on an additional third cut and repeat steps 1 to 3. + +**Table I.5.3-1: The correction factor for two or three cuts dense sampling** + +| | Three cuts | Two cuts | +|-------------------------------------|------------|----------| +| Correction factor $\Delta TRP$ (dB) | 2.0 | 2.5 | + +## I.6 Wave vector space grid + +If EUT is mounted along the $yz$ plane as shown in figure I.2.2-1, the reference step in wave vector space can be determined by + +where $D_y$ is the length of radiating parts of EUT along y-axis, $D_z$ is the length of radiating parts of EUT along the z-axis. + +According to the relationship between the normalized wave vector and spherical coordinate, the wave vector can be represented as following: + +The total radiated power (TRP) in the wave vector space is determined by: + +For spurious Tx or Rx emissions and where due to practical reasons such as time constraints or turn-table precision, measurement with the reference steps is not practical, sparser grids can be used. Use of sparse grids can lead to errors in TRP assessment. In order to characterize these errors, the SF (sparsity factor) of the grid is defined as + +Where $\Delta\theta$ and $\Delta\phi$ are the actual steps used in the wave vector space in the measurement and the upper bound of their value is $1/12$ , corresponding to 15 degree steps close to boresight. + +## I.7 Void + +## I.8 Void + +## I.9 Full sphere with sparse sampling + +The procedure is as follows: + +- 1) Set the angular grid: + - a. Non-harmonic frequencies: choose the angular steps $\Delta\theta$ and $\Delta\phi$ smaller than or equal to 15 degrees. Calculate the sparsity factor (SF) as + +and the correction factor as: + +where $\Delta\theta_{ref}$ corresponds to 15 degrees angular step. If the sparsity factor is smaller than 1, the correction factor $\Delta\text{TRP}$ is 0 dB. + +Harmonic frequencies with fixed beam test signal: choose the angular steps smaller than or equal to the reference angular steps $\Delta\theta_{ref}$ and $\Delta\phi_{ref}$ . Correction factor $\Delta\text{TRP}$ is 0 dB. + +Harmonic frequencies with beam sweeping test signal: set the angular steps to 15 degrees. Correction factor is $\Delta\text{TRP}$ 0 dB. + +- 2) Apply a suitable numerical integration to calculate the preliminary $\text{TRP}_{\text{Estimate}}$ . +- 3) Add the appropriate correction factor $\Delta\text{TRP}$ according to step 1 to ensure an overestimation with 95 % confidence. +- 4) Compare the corrected $\text{TRP}_{\text{Estimate}}$ (including $\Delta\text{TRP}$ ) with the limit. If the corrected $\text{TRP}_{\text{Estimate}}$ is above the limit, choose a smaller angular step and repeat steps 2-4. If the sparsity factor is less than one, no significant improvement of accuracy is expected. + +## I.10 Beam-based directions + +Beam-based direction can be used in the base station *operating band* only if the directivity of the radiation pattern of the emissions being measured is known. $TRP_{Estimate}$ is defined as + +, where $EIRP_{max}$ is the maximum EIRP in the beam peak direction within a particular beam direction pair and $D$ is the directivity of the EUT. + +## I.11 Peak method + +The peak method can be used when frequencies with unwanted peak emissions are identified during pre-scan. The method does not provide an estimate of TRP. + +For each peak emission frequency identified during pre-scan, measure peak EIRP or power density as follows: + +- 1) Move EUT and test antenna to the same position where the peak emission is recorded during the pre-scan. +- 2) Move the EUT around the position and test antenna orientation to find the final peak EIRP or power density. +- 3) The measured peak power density or EIRP shall be used to demonstrate conformance. + +NOTE: Peak EIRP is the linear sum of two orthogonal polarized components. + +## I.12 Equal sector with peak average + +Equal sector with peak average can be performed on frequencies with unwanted peak emission, which are considered by the peak method for further measurements. + +The spherical angle $\Omega$ is divided into $K$ equal sectors. If the largest dimension of EUT is less than 60 cm, then each sector is a half quadrant of $45^\circ$ . + +For each peak emission frequency, measure peak EIRP of beams belonging to different sectors of the sphere as follows: + +- 1) Move EUT and test antenna to the same position where the emission peak is recorded during the pre-scan. +- 2) Move EUT around the position and test antenna orientation to find the final peak EIRP. +- 3) Repeat Steps 1 to 2 until all sectors are covered. +- 4) Calculate $TRP_{Estimate}$ as + +, where $EIRP_k$ is the peak EIRP in the $k$ th sector. + +NOTE: Peak EIRP is the linear sum of two orthogonal polarized components. + +## I.13 Pre-scan + +Pre-scan is used to identify frequencies with unwanted emission power levels above a certain threshold. The pre-scan does not provide an estimate of TRP. An emission frequency identified by a pre-scan may be further investigated by any of the TRP measurement methods in this annex. + +The procedure for pre-scan is as follows: + +- 1) Scan the entire surface around EUT. +- 2) Rotate test antenna to cover all possible polarizations of emissions to detect maximum emissions. +- 3) Record the list of frequencies and corresponding unwanted emission power levels, EUT spatial positions, and test antenna polarization for which the maximum emission levels occur. + +- 4) Emissions which 20 dB or more below the specified limit shall not require further measurements. + +## 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.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), FR2-1 (24.25 – 52.6 GHz) and FR2-2 (52.6 – 71 GHz). + +#### J.2.1 Delay profiles + +The delay profiles are simplified from the TR 38.901 [23] 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 [23]. + +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 [23]. + +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 J.2.1.1-1 and the tapped delay line models are specified in tables J.2.1.1-2 ~ 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 + +The delay profiles for FR2 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 | +| TDLC300-600 | TDLC300 | 600 Hz | +| TDLC300-1200 | TDLC300 | 1200 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 gNB and UE and for the antenna configuration using cross polarized antennas. + +### J.2.3.1 MIMO correlation matrices using Uniform Linear Array + +The MIMO channel correlation matrices defined in J.2.3.1 apply for the antenna configuration using uniform linear array (ULA) at both gNB and UE. + +#### J.2.3.1.1 Definition of MIMO correlation matrices + +Table J.2.3.1.1-1 defines the correlation matrix for the gNB. + +**Table J.2.3.1.1-1: gNB correlation matrix** + +| | | +|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| One antenna |

gNB 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 UE: + +**Table J.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 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 gNB and UE 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^{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{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^{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}$ | +| 4x4 case | $R_{spat} = R_{UE} \otimes R_{gNB} = \begin{pmatrix} 1 & \beta^{1/3} & \beta^{4/3} & \beta \\ \beta^{1/3*} & 1 & \beta^{1/3} & \beta^{4/3} \\ \beta^{4/3*} & \beta^{1/3*} & 1 & \beta^{1/3} \\ \beta^* & \beta^{4/3*} & \beta^{1/3*} & 1 \end{pmatrix} \otimes \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}$ | + +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}$ . + +### 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 table 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 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 J.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 J.2.3.1.2-2: MIMO correlation matrices for high correlation** + +| | | +|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1x2 case | $R_{high} = \begin{bmatrix} 1 & 0.9 \\ 0.9 & 1 \end{bmatrix}$ | +| 2x2 case | $R_{high} = \begin{bmatrix} 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{bmatrix}$ | +| 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{bmatrix} 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{bmatrix}$ | +| 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 UE and gNB sides + +#### J.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, + +#### J.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} = 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 | | | +|------------------------------------------------------------------------------------------------------------|---|---| +| ✓ | ☞ | ■ | +| 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.3 High speed train condition + +The applicable models for high speed train conditions are as follows: + +- Scenario 1-NR350 / Scenario 1-NR500: Open space +- Scenario 3-NR350 / Scenario 3-NR500: Tunnel +- Scenario 4-BI-NR350, FR2: Open space + +The high speed train conditions for the test of the baseband performance are three non-fading propagation channels. The Doppler shift varies with time as described below. For BS with Rx diversity, the Doppler shift time variation is the same for each antenna at each time instant. + +For all three scenarios, the Doppler shift is given by: + +$$(J.3.1)$$ + +where $f_d$ is the Doppler shift and $f_{max}$ is the maximum Doppler frequency. + +For Scenario 1 and Scenario 3, the cosine of angle is given by: + +$$(J.3.2)$$ + +$$(J.3.3)$$ + +$$(J.3.4)$$ + +where $d_0$ is the initial distance in metres of the train from BS, and $h$ is the perpendicular distance in metres from the BS to the railway track, $v$ is the velocity of the train in m/s, $t$ is time in seconds. + +For Scenario 4, the cosine of angle is given by: + +$$(J.3.5)$$ + +$$(J.3.6)$$ + +$$(J.3.7)$$ + +where $d_0$ is the initial distance of the train from BS, and $h$ 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 J.3-1 and J.3-2. The resulting time varying Doppler shift is shown in Figure J.3-1, J.3-2, J.3-3, J.3-4, and J.3-9 for 350 km/h scenarios, and in Figure J.3-5, J.3-6, J.3-7 and J.3-8 for 500 km/h scenarios. For 350 km/h scenarios, the Doppler shift was derived such that it corresponds to a velocity of around 350 km/h for band n1 for the 15 KHz SCS, for band n77 for the 30 KHz SCS, and for band n257 for the 120 KHz SCS. + +For 500 km/h scenarios, the Doppler shift was derived such that it corresponds to a velocity of around 500 km/h for band n3 for the 15 KHz SCS, and for band n77 for the 30 KHz 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 J.3-1: Parameters for high speed train conditions for UE velocity 350 km/h** + +| Parameter | Value | | | +|-----------|--------------------------------------------------|--------------------------------------------------|--------------------------| +| | Scenario 1-NR350 | Scenario 3-NR350 | Scenario 4-BI-NR350, FR2 | +| | 700 m | 300 m | 700 m | +| | 150 m | 2 m | 150 m | +| | 350 km/h | 350 km/h | 350 km/h | +| | 1340 Hz for 15 KHz SCS
2334 Hz for 30 KHz SCS | 1340 Hz for 15 KHz SCS
2334 Hz for 30 KHz SCS | 19444 Hz for 120 KHz SCS | + +**Table J.3-2: Parameters for high speed train conditions for UE velocity 500 km/h** + +| Parameter | Value | | +|-----------|--------------------------------------------------|--------------------------------------------------| +| | Scenario 1-NR500 | Scenario 3-NR500 | +| | 700 m | 300 m | +| | 150 m | 2 m | +| | 500 km/h | 500 km/h | +| | 1740 Hz for 15 KHz SCS
3334 Hz for 30 KHz SCS | 1740 Hz for 15 KHz SCS
3334 Hz for 30 KHz SCS | + +![Figure J.3-1: Doppler shift trajectory for scenario 1-NR350 (15 kHz SCS). The graph shows a periodic oscillation of 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 curve starts at approximately 1200 Hz at 0 seconds, decreases to a minimum of about -1200 Hz at 10 seconds, increases to a maximum of about 1200 Hz at 20 seconds, decreases again to a minimum of about -1200 Hz at 30 seconds, increases to a maximum of about 1200 Hz at 40 seconds, and finally decreases to about -1200 Hz at 50 seconds.](4347f3937d22aee5e65e238303e4e4ee_img.jpg) + +Figure J.3-1: Doppler shift trajectory for scenario 1-NR350 (15 kHz SCS). The graph shows a periodic oscillation of 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 curve starts at approximately 1200 Hz at 0 seconds, decreases to a minimum of about -1200 Hz at 10 seconds, increases to a maximum of about 1200 Hz at 20 seconds, decreases again to a minimum of about -1200 Hz at 30 seconds, increases to a maximum of about 1200 Hz at 40 seconds, and finally decreases to about -1200 Hz at 50 seconds. + +**Figure J.3-1: Doppler shift trajectory for scenario 1-NR350 (15 kHz SCS)** + +![Figure J.3-2: Doppler shift trajectory for scenario 3-NR350 (15 kHz SCS). The graph shows a square wave oscillating between approximately 1500 Hz and -1500 Hz over a 50-second time period.](2889c0ef51f720bd7c31921af28f4658_img.jpg) + +This graph shows the Doppler shift trajectory for scenario 3-NR350 with 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 1500 Hz, drops to -1500 Hz at 2.5 seconds, returns to 1500 Hz at 5 seconds, drops to -1500 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 J.3-2: Doppler shift trajectory for scenario 3-NR350 (15 kHz SCS). The graph shows a square wave oscillating between approximately 1500 Hz and -1500 Hz over a 50-second time period. + +Figure J.3-2: Doppler shift trajectory for scenario 3-NR350 (15 kHz SCS) + +![Figure J.3-3: Doppler shift trajectory for scenario 1-NR350 (30 kHz SCS). The graph shows a sinusoidal wave oscillating between approximately 2000 Hz and -2000 Hz over a 50-second time period.](b6c180eec8419c3f2a80bb59d1b71faf_img.jpg) + +This graph shows the Doppler shift trajectory for scenario 1-NR350 with 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 sinusoidal wave that starts at approximately 2000 Hz, crosses zero at 6.25 seconds, reaches a minimum of -2000 Hz at 12.5 seconds, crosses zero at 18.75 seconds, reaches a maximum of 2000 Hz at 25 seconds, crosses zero at 31.25 seconds, reaches a minimum of -2000 Hz at 37.5 seconds, crosses zero at 43.75 seconds, and ends at -2000 Hz at 50 seconds, completing approximately 2.5 cycles. + +Figure J.3-3: Doppler shift trajectory for scenario 1-NR350 (30 kHz SCS). The graph shows a sinusoidal wave oscillating between approximately 2000 Hz and -2000 Hz over a 50-second time period. + +Figure J.3-3: Doppler shift trajectory for scenario 1-NR350 (30 kHz SCS) + +![Figure J.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.](4ea8d6ad6a6469a3a90ebf2d424f7d07_img.jpg) + +This graph shows the Doppler shift trajectory for scenario 3-NR350 with 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, drops to -2500 Hz at 2.5 seconds, returns to 2500 Hz at 5 seconds, drops 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 J.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 J.3-4: Doppler shift trajectory for scenario 3-NR350 (30 kHz SCS) + +![Figure J.3-5: Doppler shift trajectory for scenario 1-NR500 (15 kHz SCS). The graph shows a sinusoidal Doppler shift over 50 seconds, with peaks around 1500 Hz and troughs around -1500 Hz.](55184b561250bd2191d0f64fd4948673_img.jpg) + +This graph shows the Doppler shift (Hz) over a 50-second time period for scenario 1-NR500 with 15 kHz SCS. The y-axis ranges from -3000 to 3000 Hz with major grid lines every 1000 Hz. The x-axis ranges from 0 to 50 seconds with major grid lines every 10 seconds. The curve is a smooth sinusoidal wave starting at 0 seconds with a positive shift of approximately 1500 Hz. It reaches a minimum of about -1500 Hz at 5 seconds, a maximum of about 1500 Hz at 10 seconds, and continues this pattern for five full cycles, ending at approximately 1500 Hz at 50 seconds. + +Figure J.3-5: Doppler shift trajectory for scenario 1-NR500 (15 kHz SCS). The graph shows a sinusoidal Doppler shift over 50 seconds, with peaks around 1500 Hz and troughs around -1500 Hz. + +Figure J.3-5: Doppler shift trajectory for scenario 1-NR500 (15 kHz SCS) + +![Figure J.3-6: Doppler shift trajectory for scenario 3-NR500 (15 kHz SCS). The graph shows a square wave Doppler shift over 50 seconds, alternating between approximately 1500 Hz and -1500 Hz.](76fd6b70a4c042241b32568c536a4704_img.jpg) + +This graph shows the Doppler shift (Hz) over a 50-second time period for scenario 3-NR500 with 15 kHz SCS. The y-axis ranges from -3000 to 3000 Hz with major grid lines every 1000 Hz. The x-axis ranges from 0 to 50 seconds with major grid lines every 10 seconds. The curve is a square wave starting at 0 seconds with a positive shift of approximately 1500 Hz. It alternates between 1500 Hz and -1500 Hz every 2.5 seconds, completing 20 full cycles by 50 seconds, ending at -1500 Hz. + +Figure J.3-6: Doppler shift trajectory for scenario 3-NR500 (15 kHz SCS). The graph shows a square wave Doppler shift over 50 seconds, alternating between approximately 1500 Hz and -1500 Hz. + +Figure J.3-6: Doppler shift trajectory for scenario 3-NR500 (15 kHz SCS) + +![Figure J.3-7: Doppler shift trajectory for scenario 1-NR500 (30 kHz SCS). The graph shows a sinusoidal Doppler shift over 50 seconds, with peaks around 3000 Hz and troughs around -3000 Hz.](e4f6dfe8642c4656d6cd3626216c9d55_img.jpg) + +This graph shows the Doppler shift (Hz) over a 50-second time period for scenario 1-NR500 with 30 kHz SCS. The y-axis ranges from -3000 to 3000 Hz with major grid lines every 1000 Hz. The x-axis ranges from 0 to 50 seconds with major grid lines every 10 seconds. The curve is a smooth sinusoidal wave starting at 0 seconds with a positive shift of approximately 3000 Hz. It reaches a minimum of about -3000 Hz at 5 seconds, a maximum of about 3000 Hz at 10 seconds, and continues this pattern for five full cycles, ending at approximately 3000 Hz at 50 seconds. + +Figure J.3-7: Doppler shift trajectory for scenario 1-NR500 (30 kHz SCS). The graph shows a sinusoidal Doppler shift over 50 seconds, with peaks around 3000 Hz and troughs around -3000 Hz. + +Figure J.3-7: Doppler shift trajectory for scenario 1-NR500 (30 kHz SCS) + +![Figure J.3-8: Doppler shift trajectory for scenario 3-NR500 (30 kHz SCS). The graph shows a periodic square wave pattern. The y-axis is 'Doppler Shift (Hz)' ranging from -3000 to 3000. The x-axis is 'Time (sec)' ranging from 0 to 50. The signal alternates between approximately 3000 Hz and -3000 Hz in a square wave fashion, with a period of about 2.5 seconds.](cfd4ab4dd7c8508bc31765b288283a14_img.jpg) + +Figure J.3-8: Doppler shift trajectory for scenario 3-NR500 (30 kHz SCS). The graph shows a periodic square wave pattern. The y-axis is 'Doppler Shift (Hz)' ranging from -3000 to 3000. The x-axis is 'Time (sec)' ranging from 0 to 50. The signal alternates between approximately 3000 Hz and -3000 Hz in a square wave fashion, with a period of about 2.5 seconds. + +Figure J.3-8: Doppler shift trajectory for scenario 3-NR500 (30 kHz SCS) + +![Figure J.3-9: Doppler shift trajectory for scenario 4-BI-NR350, FR2 (120 kHz SCS). The graph shows a periodic square wave pattern. The y-axis is 'Doppler Shift (Hz)' ranging from -20000 to 20000. The x-axis is 'Time (sec)' ranging from 0 to 50. The signal alternates between approximately 18000 Hz and -18000 Hz in a square wave fashion, with a period of about 2.5 seconds.](97fd0793c8041e1c0e6413aa3d9364c4_img.jpg) + +Figure J.3-9: Doppler shift trajectory for scenario 4-BI-NR350, FR2 (120 kHz SCS). The graph shows a periodic square wave pattern. The y-axis is 'Doppler Shift (Hz)' ranging from -20000 to 20000. The x-axis is 'Time (sec)' ranging from 0 to 50. The signal alternates between approximately 18000 Hz and -18000 Hz in a square wave fashion, with a period of about 2.5 seconds. + +Figure J.3-9: Doppler shift trajectory for scenario 4-BI-NR350, FR2 (120 kHz SCS) + +## J.4 Moving propagation conditions + +Figure J.4-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 (J.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 15 KHz SCS, $\Delta\tau - (T_A - 31) \times 16 \times 32 T_c$ for 30 KHz SCS and $\Delta\tau - (T_A - 31) \times 16 \times 8 T_c$ for 120 KHz SCS. The relative timing among all taps is fixed. The parameters for the moving propagation conditions are shown in Table J.4-1. + +![Diagram illustrating moving propagation conditions. A horizontal axis represents time. A solid vertical arrow labeled 'Ref' is at time t0. A dashed vertical arrow labeled 'P1' is at time t1. The time difference between t0 and t1 is labeled Δτ. There are additional dashed vertical arrows at later times, with the last one having a horizontal dashed line leading to it.](f146bedbc65611bb7e7515e9e6965755_img.jpg) + +Diagram illustrating moving propagation conditions. A horizontal axis represents time. A solid vertical arrow labeled 'Ref' is at time t0. A dashed vertical arrow labeled 'P1' is at time t1. The time difference between t0 and t1 is labeled Δτ. There are additional dashed vertical arrows at later times, with the last one having a horizontal dashed line leading to it. + +Figure J.4-1: Moving propagation conditions + +(J.4-1) + +Table J.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 μs
30 kHz: 5 μs | 15 kHz: 10 μs
30 kHz: 5 μs
120 kHz: 1.25 μs | 15 kHz: 10 μs
30 kHz: 5 μs | +|

Image: Doppler shift icon

$\dot{\tau}$ | 15 kHz: 0.04 s -1
30 kHz: 0.08 s -1 | 15 kHz: 0.13 s -1
30 kHz: 0.26 s -1
120 kHz: 1.04 s -1 | 15 kHz: 0.18 s -1
30 kHz: 0.36 s -1 | + +NOTE: Doppler shift is not taken into account in UL TA scenario Y and scenario Z. + +## 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 towards (3, 0).](c31fc33e1a6e262737615e382de3624e_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 towards (3, 0). + +**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 + +### L.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. + +--- + +### L.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. + +#### L.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.141-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, table 6.6.3.5.2-3 for 120 kHz SCS, table 6.6.3.5.2-4 for 480 kHz SCS and table 6.6.3.5.2-5 for 960 kHz SCS. In the time domain it comprises at least 10 ms for FR1 and FR2-1 and at least 80 slots for FR2-2. 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. + +#### L.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 L.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 L.2.1 in the time domain. + +## L.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. + +## L.2.4 Measurement points + +The resource element TX power is measured after the FFT box as described in figure L.2.4-1 for FR1 and in figure L.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 L.2.4-1 and for FR2 in figure L.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.141-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* and the cyclic prefix length is determined from table 6.6.3.5.2-2 for 60 kHz SCS, table 6.6.3.5.2-3 for 120 kHz SCS, table 6.6.3.5.2-4 for 480 kHz SCS and table 6.6.3.5.2-5 for 960 kHz SCS. + +In one subframe, there are two symbols with the length of the cyclic prefix larger than the values listed in TS 38.141-1 [3] tables 6.5.3.5-2, 6.5.3.5-3 and 6.5.3.5-4 for FR1 and tables 6.6.3.5.2-2, table 6.6.3.5.2-3, table 6.6.3.5.2-4 and table 6.6.3.5.2-5 for FR2. Table L.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 L.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 + \frac{FFT\ size}{128}$ | +| 30 | | 2 | (symbol 0, slot 0)
(symbol 0, slot 1) | $CP\ length + \frac{FFT\ size}{64}$ | +| 60 | | 4 | (symbol 0, slot 0)
(symbol 0, slot 2) | $CP\ length + \frac{FFT\ size}{32}$ | +| 60 | FR2-1 | 4 | (symbol 0, slot 0)
(symbol 0, slot 2) | $CP\ length + \frac{FFT\ size}{32}$ | +| 120 | | 8 | (symbol 0, slot 0)
(symbol 0, slot 4) | $CP\ length + \frac{FFT\ size}{16}$ | +| 120 | FR2-2 | 8 | (symbol 0, slot 0)
(symbol 0, slot 4) | $CP\ length + \frac{FFT\ size}{16}$ | +| 480 | | 32 | (symbol 0, slot 0)
(symbol 0, slot 16) | $CP\ length + \frac{FFT\ size}{4}$ | +| 960 | | 64 | (symbol 0, slot 0)
(symbol 0, slot 32) | $CP\ length + \frac{FFT\ size}{2}$ | + +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 reference point for FR1 EVM measurements. The flow is: BS 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' block is connected to the 'Per-subcarrier Amplitude/phase correction' block.](02ae5fd93ac89537e28a7ff747361ecc_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] + Pre_post[Pre-/post FFT time / frequency synchronization] -.-> Remove_CP + Pre_post -.-> FFT + Pre_post -.-> Per_subcarrier + Ref[EVM measurement reference point] -.-> Per_subcarrier + +``` + +Block diagram showing the reference point for FR1 EVM measurements. The flow is: BS 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' block is connected to the 'Per-subcarrier Amplitude/phase correction' block. + +**Figure L.2.4-1: Reference point for FR1 EVM measurements** + +![Figure L.2.4-2: Reference point for FR2 EVM measurements. The diagram shows a signal flow from BS TX to Remove CP, then to FFT, then to Per-subcarrier Amplitude/phase and CPE 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 and CPE correction blocks. A box labeled 'Reference point for EVM measurement' has a dashed arrow pointing to the Per-subcarrier Amplitude/phase and CPE correction block.](d74ed29ed2b7aca01173043c14d46cab_img.jpg) + +``` + +graph LR + BS_TX[BS TX] --> Remove_CP[Remove CP] + Remove_CP --> FFT[FFT] + FFT --> Per_subcarrier[Per-subcarrier Amplitude/phase and CPE 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 L.2.4-2: Reference point for FR2 EVM measurements. The diagram shows a signal flow from BS TX to Remove CP, then to FFT, then to Per-subcarrier Amplitude/phase and CPE 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 and CPE correction blocks. A box labeled 'Reference point for EVM measurement' has a dashed arrow pointing to the Per-subcarrier Amplitude/phase and CPE correction block. + +Figure L.2.4-2: Reference point for FR2 EVM measurements + +## L.3 Pre-FFT minimization process + +Sample timing, carrier frequency in are varied in order to minimise the difference between $\hat{s}_i$ and $s_i$ , after the amplitude ratio of $\hat{s}_i$ and $s_i$ has been scaled. Best fit (minimum difference) is achieved when the RMS difference value between $\hat{s}_i$ and $s_i$ 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 $\hat{s}_i$ . + +## L.4 Timing of the FFT window + +The FFT window length is $FFT\ size$ samples per OFDM symbol. For FDD, there are $N_{slots}$ FFTs performed where $N_{slots}$ is the number of slots in a 10 ms measurement interval, and the number of symbols in a slot for normal CP is 14. For TDD, the number of FFTs performed is the number of downlink symbols in the measurement interval. + +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. 832 FFTs (i.e. 3,407,872 samples) cover less than the acquired number of samples (i.e. 3,651,584 samples in 10 ms). There are 816 symbols with 4384 samples and 16 symbols with 4640 samples. + +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}$ , + +- , and +- . + +The value of EVM window length $W$ is obtained from the transmission bandwidth and TS 38.141-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, table 6.6.3.5.2-3 for 120 kHz SCS, table 6.6.3.5.2-4 for 480 kHz SCS and table 6.6.3.5.2-5 for 960 kHz SCS for FR2. + +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 $\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.141-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, table 6.6.3.5.2-3 for 120 kHz SCS, table 6.6.3.5.2-4 for 480 kHz SCS and table 6.6.3.5.2-5 for 960 kHz SCS for FR2, and the longer CP length is obtained from table L.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. + +## L.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 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 for FR1 and FR2-1, in an 80 slots measurement interval for FR2-2 and is computed according to the values in table 4.9.2.2-1. + +For the example used in the annex, $N = 10$ and $N = 80$ . + +## L.6 Post-FFT equalisation + +Perform FFTs on $s$ , one for each OFDM symbol within 10 ms for FR1 and FR2-1, and 80 slots measurement interval for FR2-2 measurement interval with the FFT window timing to produce an array of samples, 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$ . The result is an array of samples, 1120 in the time axis by 4096 in the frequency axis. + +The equalizer coefficients $\hat{h}$ and $\hat{a}$ are determined as follows: + +1. Calculate the complex ratios (amplitude and phase) of the post-FFT acquired signal $\hat{s}$ and the post-FFT ideal signal $s$ , for each demodulation reference signal, over 10 ms measurement interval for FR1 and FR2-1, and 80 slots measurement interval for FR2-2. 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 for FR1 and FR2-1, and 80 slots measurement interval for FR2-2. 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{s}/s$ by adding multiples of $2 * \pi$ when absolute phase jumps between consecutive time instances are greater then 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 $\hat{s}$ for each demodulation reference signal subcarrier $f$ . + +3. The equalizer coefficients for amplitude and phase $\hat{h}$ and $\hat{a}$ 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 L.6-1. +4. Perform linear interpolation from the equalizer coefficients $\hat{h}$ and $\hat{a}$ to compute coefficients $\hat{h}$ , for each subcarrier. + +![Figure L.6-1: Reference subcarrier smoothing in the frequency domain. The figure contains 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 1RB allocation with a reduced window size of 5 subcarriers.](b5f2a411da1c592432185a9a34e95c38_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 L.6-1: Reference subcarrier smoothing in the frequency domain. The figure contains 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 1RB allocation with a reduced window size of 5 subcarriers. + +**Figure L.6-1: Reference subcarrier smoothing in the frequency domain** + +- a) In case of FR2 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)$$ + +## L.7 EVM + +### L.7.0 General + +For EVM create two sets of $s$ , according to the timing $t$ and $k$ , using the equalizer coefficients from L.6. + +The equivalent ideal samples are calculated from (annex L.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, +- $k$ 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 for FR1 and FR2-1, and over the entire 80 slots measurement interval for FR2-2 to reduce the impact of noise in the reference signals. + +### L.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}$ downlink slots where $N_{slots}$ 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_{RB}$ is the number of resource blocks with the considered modulation scheme in subframe $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_{low}$ is calculated using $s$ in the expressions above and $EVM_{high}$ is calculated using $s$ in the calculation where ( $l$ and $h$ , low and high; where low is the timing $t$ and high is the timing $t$ ). + +Thus: + +The resulting $EVM_{avg}$ is compared against the limit. + +### L.7.2 Averaged EVM (TDD) for FR1 and FR2-1 + +Let $N_{slots}$ 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}$ slots of different 10 ms measurement intervals and should have a minimum of $N_{slots}$ slots averaging length where $N_{slots}$ is the number of slots in a 10 ms measurement interval. + +$EVM_{avg}$ 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 $\Delta f$ is calculated, using the maximum of $\Delta f$ at the window $W$ extremities. Thus $\Delta f$ is calculated using $\Delta f_{low}$ and $\Delta f_{high}$ using ( $l$ and $h$ , low and high; where low is the timing $l$ and high is the timing $h$ ). + +In order to unite at least 10 slots, consider the minimum integer number of 10 ms measurement intervals, where $N$ is determined by + +And for FR1, $N = 1$ for 15 kHz SCS, $N = 2$ for 30 kHz SCS and $N = 4$ for 60 kHz SCS normal CP. For FR2, $N = 1$ for 60 kHz SCS and $N = 2$ for 120 kHz SCS. + +Unite by RMS. + +The resulting $\Delta f$ is compared against the limit. + +### L.7.3 Averaged EVM (TDD) for FR2-2 + +Let $N$ be the number of slots with downlink symbols within a 80 slots measurement interval. For TDD, the averaging in the time domain can be calculated from $N$ slots of different measurement intervals and should have a minimum of 80 slots averaging length for FR2-2. + +$EVM_{RMS}$ is derived by: Square the EVM results in each one 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 $\Delta f$ is calculated, using the maximum of $\Delta f$ at the window $W$ extremities. Thus $\Delta f$ is calculated using $\Delta f_{low}$ and $\Delta f_{high}$ using ( $l$ and $h$ , low and high; where low is the timing $l$ and high is the timing $h$ ). + +In order to unite at least 80 slots, consider the minimum integer number of 80 slots measurement intervals, where $N$ is determined by + +Unite by RMS. + +The resulting $\Delta f$ is compared against the limit. + +--- + +## Annex M (normative): General rules for statistical testing + +### M.1 Testing methodology of PUSCH performance requirements with 0.001% BLER + +#### M.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 M.1.1-1. If $n_s$ is greater than the $n_{sp}$ value in M.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 M.1.3.1. The minimum testing time is defined by the possible decision coordinates detailed in clause M.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). + +## M.1.2 Numerical definition of the pass-fail limits for testing PUSCH 0.001% BLER + +**Table M.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 M.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 EUT passes after 1074532 samples. The maximum test time is 52171625 samples. A EUT passes, if the maximum number of samples is reached and it did not fail before. + +## M.1.3 Theory to derive the early pass/fail limits in M.1.2 (informative) + +### M.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. + +### M.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 ( $n_e, n_s$ ), as captured in clause M.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 EUT 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 EUTs 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 EUTs 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 EUTs decrease during the simulation, as the decided EUTs leave the population. That number decreases with an approximately exponential characteristics. After 642 bad results all EUTs 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 N (informative): Change history + +| Change history | | | | | | | | +|----------------|--------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|-----|-----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-11 | RAN4#84bis | R4-1711983 | - | - | - | TS skeleton | 0.0.1 | +| 2018-04 | RAN4#86bis | R4-1805875,
R4-1805876,
R4-1804931,
R4-1805877,
R4-1805386,
R4-1805916,
R4-1805915,
R4-1805878 | - | - | - | Implementation of TPs agreed during RAN4#86bis, on top of the agreed R4-1803913:
- R4-1805875 TP for TS 38.141-2: Addition of applicability table in clause 4.7.2
- R4-1805876 TP for TS 38.141-2: Addition of co-location reference antenna description to clause 4.13
- R4-1804931 TP to TS 38.141-2: clauses 1-3
- R4-1805877 TP to TS 38.141-2: clauses 4, 5
- R4-1805386 TP to TS 38.141-2: clause 6
- R4-1805916 TP to TS 38.141-2: clause 7
- R4-1805915 TP to TS 38.141-2: NR BS OTA sensitivity conformance test (7.2)
- R4-1805878 TP to TS 38.141-2: NR BS OTA REFSSENS conformance test (7.3) | 0.1.0 | +| 2018-06 | RAN4#87 | R4-1714157,
R4-1806599,
R4-1807591,
R4-1807747,
R4-1808325,
R4-1808329,
R4-1808331,
R4-1808332,
R4-1808333,
R4-1808334,
R4-1808336,
R4-1808337,
R4-1808483,
R4-1808487 | - | - | - | Implementation of TPs agreed during RAN4#87, on top of R4-1807255:
- R4-1714157 TP to TS 38.141-2 - annex with spatial declarations definitions
- R4-1806599 TP to TS 38.141-2: NR BS OTA dynamic range conformance test (7.4)
- R4-1807591 TP to TS 38.141-2 - update to Rx general clause (7.1)
- R4-1807747 TP to TS 38.141-2: Annexes
- R4-1808325 TP to TS 38.141-2: Improvement of RIB interface in Figures 4.2-1, 4.2-2 and 4.2-3, in clause 4.2
- R4-1808329 TP to TS 38.141-2: NR BS OTA in-band selectivity and blocking conformance test (7.5)
- R4-1808331 TP to TS 38.141-2: Definitions, symbols and abbreviations (Clauses 3)
- R4-1808332 TP to TS 38.141-2: NR BS OTA occupied bandwidth (6.7.2)
- R4-1808333 TP to TR 38.141-2: Clarifications on OTA sensitivity requirement (7.2.1, 7.3.1)
- R4-1808334 TP to TS 38.141-2 - OTA base station output power (6.3)
- R4-1808336 TP to TS 38.141-2 - OTA in-band receiver intermodulation (7.8)
- R4-1808337 TP to TS 38.141-2 - OTA in-channel selectivity (7.9)
- R4-1808483 TP to TS 38.141-2: multi-band operation
- R4-1808487 TP to TS 38.141-2 - OTA output power dynamics (6.4) | 0.2.0 | +| 2018-07 | RAN4-AH-1807 | R4-1808823
R4-1808874
R4-1809109
R4-1809465
R4-1809485
R4-1809486
R4-1809487
R4-1809488
R4-1809489 | - | - | - | Implementation of TPs approved during RAN4-AH-1807, on top of R4-1809266 (TS 38.141-2, v0.2.0):
- R4-1808823 TP to TS 38.141-2: Applicability of requirements (Clauses 4.7)
- R4-1808874 TP to TS 38.141-2: Introduction of the transmit, receive and co-location configurations, in clause 4.5
- R4-1809109 TP to TS 38.141-2 - Annex D, TX and RX Test setup
- R4-1809465 TP to TS 38.141-2 - 4.8.2 Test signal Configurations
- R4-1809485 TP to TS 38.141-2: NR BS acceptable uncertainty of OTA Test System (4.1.2)
- R4-1809486 TP to TS 38.141-2: NR BS derivation of test requirement (Annex C)
- R4-1809487 TP to TS 38.141-2: Correction of RX procedures
- R4-1809488 TP to TS 38.141-2: Correction of TX directional power related requirements | 0.3.0 | + +| | | | | | | | | +|--|--|------------|--|--|--|-----------------------------------------------------------------------------------------------------------|--| +| | | R4-1809490 | | | | - R4-1809489 TP to TS 38.141-2 – OTA unwanted emissions – General (6.7.1) | | +| | | R4-1809491 | | | | - R4-1809490 TP to TS 38.141-2: NR BS OTA occupied bandwidth (6.7.2) | | +| | | R4-1809493 | | | | - R4-1809491 TP to TS 38.141-2 – OTA ACLR (6.7.3) | | +| | | R4-1809494 | | | | - R4-1809493 TP to TS 38.141-2 Annex XX - measuring extreme conditions | | +| | | R4-1809495 | | | | - R4-1809494 TP to TS 38.141-2 Test requirement for Radiated transmit power | | +| | | R4-1809496 | | | | - R4-1809495 TP to TS 38.141-2 Transmitter spurious emissions (6.7.5) | | +| | | R4-1809497 | | | | - R4-1809496 TP to TS 38.141-2: Adding requirement text for OTA Tx IMD in clause 6.8 and Annex E1.7 | | +| | | R4-1809499 | | | | - R4-1809497 TP to TS 38.141-2 Receiver spurious emissions (7.7) | | +| | | R4-1809501 | | | | - R4-1809499 TP to TS 38.141-2: OTA frequency error (6.6.2) | | +| | | R4-1809516 | | | | - R4-1809501 TP to TS 38.141-2: OTA time alignment error (6.6.4) | | +| | | R4-1809561 | | | | - R4-1809516 TP to TR 38.141-2: NR BS OTA manufacturers declarations for radiated test requirements (4.6) | | +| | | R4-1809562 | | | | - R4-1809561 TP to TS 38.141-2: OTA modulation quality (6.6.3) | | +| | | | | | | - R4-1809562 TP to TS 38.141-2 – OTA operating band unwanted emissions (6.7.4) | | + +| | | | | | | | | +|---------|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------| +| 2018-08 | RAN4#88 | R4-1810818,
R4-1810822,
R4-1810823,
R4-1811150,
R4-1811538,
R4-1811592,
R4-1811618,
R4-1811621,
R4-1811626,
R4-1811742,
R4-1811743,
R4-1811745,
R4-1811746,
R4-1811747,
R4-1811748,
R4-1811749,
R4-1811750,
R4-1811751,
R4-1811752,
R4-1811754,
R4-1811760,
R4-1811766,
R4-1811767,
R4-1811848,
R4-1811879,
R4-1811886,
R4-1811887 | - | - | - | Implementation of TPs approved during RAN4#88, on top of R4-1810576 (TS 38.141-2, v0.3.0):
- R4-1810818 TP to TS 38.141-2: Operating bands and channel arrangement (5)
- R4-1810822 TP to TS 38.141-2: initial conditions for FR2 Rx spur test (7.7)
- R4-1810823 TP to TS 38.141-2: FRC annex (A)
- R4-1811150 TP: Add parameters band n50 in TS 38.141-2
- R4-1811538 TP for introduction of band n74 for TS38.141-2
- R4-1811592 TP to TS38.141-2: OTA operating band unwanted emissions requirements (6.7.4)
- R4-1811618 Correction on general clause for 38.141-2
- R4-1811621 TP to TS 38.141-2 Clause 4.8.2.1 Test signal used to build Test Configurations
- R4-1811626 TP to TS 38.141-2: Clause 6.1 NR Test Models
- R4-1811742 TP to TS38.141-2: Regional requirements (4.4)
- R4-1811743 TP to TS 38.141-2: Remaining issues and corrections for Radiated Tx power (EIRP) (6.2)
- R4-1811745 TP to TS 38.141-2: Corrections and improvements to the OTA Tx spurious emissions test (6.7.5)
- R4-1811746 TP to TS 38.141-2: Calibration annex (D)
- R4-1811747 TP to TS 38.141-2: Improvements of co-location requirement description in clause 4.12
- R4-1811748 TP to TS 38.141-2: NR BS OTA occupied bandwidth (6.7.2)
- R4-1811749 TP to TS 38.141-2: Adding requirement text for OTA co-location spurious emission in clause 6.7.5 and Annex E1.3
- R4-1811750 TP to TS 38.141-2 on MU and TT for Rx requirements for FR1 and FR2
- R4-1811751 TP to TS 38.141-2 on MU and TT for transmission in-band TRP emission and directional requirements or FR2 and FR1
- R4-1811752 TP to TS38.141-2 on MU and TT for extreme EIRP for FR1 and FR2
- R4-1811754 TP to TS 38.141-2: Improvement of requirement text for OTA TX IMD in clause 6.8 and Annex E.1.5
- R4-1811760 TP to TS 38.141-2: test tolerance table (Annex C)
- R4-1811766 TP to TS 38.141-2: wideband operation corrections and FBW declarations (4.6)
- R4-1811767 TP to TS 38.141-2: OTA declarations cleanup (4.6)
- R4-1811848 TP to TS 38.141-2: Adding requirement text for OTA out-of-band blocking in clause 7.6 and Annex E2.4.1 and E2.4.2
- R4-1811879 TP to TS 38.141-2 – Overview of radiated Tx and Rx requirements (4.13)
- R4-1811886 TP to TS 38.141-2: OBUE correction
- R4-1811887 TP to TS 38.141-2 on OTA Tx ON/OFF power requirements | 0.4.0 | +| 2018-09 | RAN#81 | RP-181664 | - | - | - | Presented to TSG RAN for information. | 1.0.0 | +| 2018-11 | RAN4#8bis | R4-1812584,
R4-1812666,
R4-1812683,
R4-1813300,
R4-1813301,
R4-1813310,
R4- | - | - | - | Implementation of TPs approved during RAN4#88bis, on top of RP-181664 (TS 38.141-1, v1.0.0):
- R4-1812584 TP to TS 38.141-2: Correction on NOTE for wanted signal mean power for NR BS RX requirements
- R4-1812666 TP to TS 38.141-2: Correction of directions for OTA requirements
- R4-1812683 TP to TS 38.141-2: Clarification Note on non-zero Test Tolerance
- R4-1813300 TP to TS 38.141-2: correction of the OSDD definition for single RAT NR BS specification
- R4-1813301 TP to TS 38.141-2: alignment with TS 38.104 modifications after RAN4#88
- R4-1813310 TP to TS 38.141-2: structure alignments with | 1.1.0 | + +| | | | | | | | | +|--|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| | | 1813532,
R4-
1813754,
R4-
1813877,
R4-
1813881,
R4-
1813883,
R4-
1813896,
R4-
1813899,
R4-
1813900,
R4-
1813901,
R4-
1813902,
R4-
1813903,
R4-
1813907,
R4-
1813908,
R4-
1813911,
R4-
1813912,
R4-
1813913,
R4-
1813914,
R4-
1813915,
R4-
1813993,
R4-
1814074,
R4-
1814078,
R4-
1814080,
R4-
1814120,
R4-
1814193,
R4-
1814250,
R4-
1814251,
R4-
1814253,
R4-
1814254 | | | | TS 38.141-1
- R4-1813532 TP to TS 38.141-2: Corrections to Modulation quality test in Clause 6.6.3
- R4-1813754 TP to TS 38.141-2: Radiated performance requirements (8)
- R4-1813877 TP for TS38.141-2: RF channel for BS OTA conformance test
- R4-1813881 TP to TS 38.141-2: Clause 4.9.2.3 Data content of PHY channels
- R4-1813883 TP to TS 38.141-2: FR2 test model(Clause 4.9.3)
- R4-1813896 TP to TS 38.141-2: Addition of MU for OTA performance requirements for FR1
- R4-1813899 TP to TS 38.141-2: alignment of directions to be tested for OTA requirements
- R4-1813900 TP to TS 38.141-2 on CLTA definition
- R4-1813901 TP to TS 38.141-2 on MU and TT corrections for FR1 and FR2
- R4-1813902 TP to TS 38.141-2 on Rx requirement corrections for FR1 and FR2
- R4-1813903 TP to 38.141-2: Clause 4.6 - correction for manufacturer declaration
- R4-1813907 TP to TS 38.141-2: frequency range for the inband blocking requirement for FR2
- R4-1813908 TP to TS 38.141-2 – adding TRP measurement grids to the annex
- R4-1813911 TP to TS 38.141-2: Update for NR BS occupied bandwidth requirement (6.7.2)
- R4-1813912 TP to 38.141-2: Corrections to OTA co-location spurious emission (6.7.5 and E.1.3)
- R4-1813913 TP to 38.141-2: Corrections to OTA transmitter intermodulation in clause 6.8 and Annex E.1.5
- R4-1813914 TP to TS 38.141-2: Correction of the RX intermodulation interferer
- R4-1813915 TP to TS 38.141-2: In-channel selectivity (7.9)
- R4-1813993 TP to TS 38.141-2: Radiated performance requirements for CP-OFDM based PUSCH
- R4-1814074 TP to TS 38.141-2: Corrections on OTA transmit ON/OFF power
- R4-1814078 TP to TS38.141-2: OTA CACLR absolute limits (6.7.3)
- R4-1814080 TP to TS 38.141-2: OTA declarations numbering and cross-referencing
- R4-1814120 TP to TS 38.141-2: Correction on the FRCs in Annex A1 and A2
- R4-1814193 TP to TS38.141-2: OTA UEM(Clause 6.7.4)
- R4-1814250 TP to TS 38.141-2: operating bands applicable for spurious emissions testing above 12.75 GHz
- R4-1814251 TP to TS 38.141-2: correction for the narrowest supported CHBW and SCS
- R4-1814253 TP to TS 38.141-2: Improvement of out-of-band blocking requirement in clause 7.6
- R4-1814254 TP to TS 38.141-2 on CLTA related MU | | +|--|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| + +| | | | | | | | | +|---------|---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------| +| 2018-11 | RAN4#89 | R4-1816288
R4-1814444
R4-1814504
R4-1814622
R4-1815005
R4-1815268
R4-1815304
R4-1815305
R4-1815330
R4-1815375
R4-1815381
R4-1815686
R4-1815689
R4-1815963
R4-1816277
R4-1816290
R4-1816291
R4-1816292
R4-1816293
R4-1816294
R4-1816295
R4-1816296
R4-1816297
R4-1816298
R4-1816300
R4-1816305
R4-1816306
R4-1816309
R4-1816312
R4-1816313
R4-1816315
R4-1816317
R4-1816318
R4-1816319 | - | - | - | Implementation of TPs approved during RAN4#89, on top of R4-1815277 (TS 38.141-1, v1.1.0):
R4-1816288 TP to TS 38.141-2: general cleanup
R4-1814444 TP to TS 38.141-2: FRC definitions for PUSCH and test parameters for PRACH
R4-1814504 TP to TS38.141-2: Removal of the multi-band test for BS type 2-O
R4-1814622 TP to TS 38.141-2 on Characteristics of the interfering signals
R4-1815005 TP to 38.141-2: MU clarifications
R4-1815268 TP to TS 38.141-2 on General radiated receiver characteristics
R4-1815304 TP to TS 38.141-2: Alignment of test procedure for OTA out-of-band blocking in clause 7.6
R4-1815305 TP to TS 38.141-2: Improvement of test specification text with respect to directions for OTA out-of-band blocking in clause 7.6
R4-1815330 TP to TS 38.141-2: Correction to FBW definition in clause 3.1
R4-1815375 TP to TS 38.141-2: Interpretation of measurement results and the Shared Risk principle
R4-1815381 TP to 38.141-2: OTA demodulation alignment with TS38.104 (8.1)
R4-1815686 TP to 38.141-2: alignment of OTA requirement names
R4-1815689 TP to 38.141-2: OTA out-of-band blocking co-location requirement (7.6)
R4-1815963 TP to TS 38.141-2: corrections of notes in declarations table (4.6)
R4-1816277 TP to TS 38.141-2: remaining annexes
R4-1816290 TP to TS 38.141-2 on manufacturer declarations for NR radiated requirements testing
R4-1816291 TP to TS 38.141-2: narrowest beam selection for OTA testing
R4-1816292 TP to 38.141-2: Radiated transmit power testing extreme environment conditions (6.2)
R4-1816293 TP to TS38.141-2: Radiated transmit power requirement with wideband operation (6.2)
R4-1816294 TP to TS38.141-2: OTA total power dynamic range(Clause 6.4.3)
R4-1816295 TP to TS 38.141-2: OTA transmitter OFF power (Clause 6.5.1)
R4-1816296 TP to TS38.141-2: OTA ACLR, UEM and spurious emission (Clause 6.7.3)
R4-1816297 TP to TS 38.141-2: additional spurious emissions requirement corrections (6.7.5.4.5.1)
R4-1816298 TP to TS 38.141-2: Correction to RX receiver test directions
R4-1816300 TP to TS 38.141-2 – adding further details on reference steps to the annex
R4-1816305 TP to TS 38.141-2 - polarization wording improvements for OTA sensitivity and reference sensitivity
R4-1816306 TP to TS 38.141-2_Corrections on transmitter intermodulation (clause 3.2 and 6.8)
R4-1816309 TP to TS 38.141-2 - update FR2 extreme MU and TT
R4-1816312 TP to TS 38.141-2: Addition of calibration procedure for extreme temperature testing in Annex B.7
R4-1816313 TP to TS 38.141-2: Test distance for blocking interferer signal in clause 7.6
R4-1816315 TP to 38.141-2: Corrections to co-location requirements
R4-1816317 TP to 38.141-2 Corrections to TRP grids formula in Annex I and adding reference in Clause 6.5
R4-1816318 Operating band orthogonal cuts measurement
R4-1816319 TP to TS 38.141-2 Correction on declaration
R4-1816350 TP for introducing propagation conditions in TS 38.141-2 | 1.2.0 | +|---------|---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------| + +| | | | | | | | | +|--|--|------------|--|--|--|---------------------------------------------------------------------------------------------------------------------------------------|--| +| | | R4-1816350 | | | | R4-1816353 TP to TS 38.141-2: Radiated test requirements for DFT-s-OFDM based PUSCH | | +| | | R4-1816353 | | | | R4-1816356 TP for TS 38.141-2 on NR PUCCH format2 radiated performance requirements | | +| | | R4-1816356 | | | | R4-1816359 TP to TS38.141-2: Performance requirements for PRACH | | +| | | R4-1816359 | | | | R4-1816361 TP for TS38.141-2: PUCCH format 1 OTA conformance test | | +| | | R4-1816361 | | | | R4-1816362 TP to TS 38.141-2: Radiated test requirements for CP-OFDM based PUSCH in FR1 | | +| | | R4-1816362 | | | | R4-1816371 TP to 38.141-2 – PUSCH requirements with CP-OFDM for FR2 | | +| | | R4-1816371 | | | | R4-1816446 TP to TS 38.141-2: Cleanup to OTA requirements text | | +| | | R4-1816446 | | | | R4-1816484 TP to TS 38.141-2: Improvement of specification text related to injection of interferer power for OTA TX IMD in clause 6.8 | | +| | | R4-1816484 | | | | R4-1816485 TP on 38.141-2: Deletion of test procedure on OFF power and transient period for FR2 | | +| | | R4-1816485 | | | | R4-1816593 TP to TS 38.141-2: PUCCH format 0 requirement testing | | +| | | R4-1816593 | | | | R4-1816720 TP for introducing PUCCH format 3 and 4 radiated conformance requirements for OTA test in 38.141-2 | | +| | | R4-1816720 | | | | R4-1816726 TP to TS 38.141-2: FR2 test model(Clause 4.9.2) | | +| | | R4-1816726 | | | | R4-1816732 TP to TS 38.141-2: OTA transmitted signal quality (Clause 6.6) | | +| | | R4-1816732 | | | | R4-1816735 TP to TS 38.141-2: Clause 4.9.2.3 Data content for PHY channels | | +| | | R4-1816735 | | | | R4-1816740 TP to TS 38.141-2: Correction to FR2 OTA REFESENS requirement | | +| | | R4-1816740 | | | | | | + +| | | | | | | | | +|---------|--------|-----------|------|--|---|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2018-12 | RAN#82 | RP-182584 | | | | 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-2

Implementation of the following draft CRs, which were Endorsed during RAN4#90, on top of v15.0.0:
R4-1900286 Draft CR on NR PUCCH format2 radiated performance requirements for TS 38.141-2
R4-1900629 Draft CR to TS 38.141-2_Clean up the test requirements for some Rx requirements
R4-1900739 Draft CR to TS 38.141-2:OTA dynamic range test requirement (7.4.5)
R4-1900742 Draft CR to TS 38.141-2:Correction on OTA total power dynamic range requirement (6.4.3)
R4-1900765 Draft CR to TS 38.141-2: Update of test requirement numbers for DFT-s-OFDM based PUSCH
R4-1900830 Draft CR to TR 38.141-02: Correction to manufacturer declaration in clause 4.6
R4-1900877 Draft CR to TS 38.141-2: On RX spurious emissions requirement
R4-1900970 Draft CR for 38.141-2: Radiated test requirements for NR PUCCH format 1
R4-1901009 Draft CR to 38.141-2: Addition of coordinates system definition
R4-1901325 Draft CR to 38.141-2: Correction to clause 6.4.3 OTA total power dynamic range - correction
R4-1901332 Draft CR to 38.141-2: Updates for Abbreviations clause
R4-1901372 CR to TS 38.141-2: Clause 3.2 Missing Beam width Symbol Definition
R4-1901389 Draft CR to TS 38.141-2 BS demodulation PUCCH format 0 requirements
R4-1901476 Draft CR to TS 38.141-2 Corrections on transmitter co-existence and co-location requirements
R4-1901486 Draft CR to TS 38.141-2: Corrections on OTA in-band blocking requirements
R4-1901538 TS 38.141-2: Editorial corrections
R4-1901743 DraftCR to TS 38.141-2: addition of the Iuant BS modem clause
R4-1902261 draft CR to TS 38.141-2 - update emissions scaling
R4-1902274 Draft CR to TS 38.141-2: Addition of missing EIRP/EIS terminology in Clause 3
R4-1902275 Draft CR to 38.141-2; Correction to definition of OTA reference sensitivity
R4-1902276 Draft CR to TS 38.141-2:Overview of radiated Tx requirements (4.1.1)
R4-1902277 Draft CR to TS 38.141-2: Corrections on Measurement uncertainties and test requirements
R4-1902278 CR to TS 38.141-2: Adding clause 4.8 reference to test procedures
R4-1902279 Draft CR to TS 38.141-2_Correction on test procedures for single-carrier and multi-carrier operation for Tx requirements
R4-1902281 Draft CR to 38.141-2: Cleanup of RX procedures
R4-1902282 Draft CR to TS 38.141-2:Test tolerance for radiated transmit power (C.1)
R4-1902283 Draft CR to TS 38.141-2_Correction on multi-band operation related requirements
R4-1902285 Correction of FR2 RoAoA declaration
R4-1902287 Draft CR to 38.141-2; clarification of BS power limits
R4-1902289 Draft CR to TR 38.141-2: Editorial clean-up of TRP measurement clause in Annex I
R4-1902291 Draft CR to 38.141-2: Addition of measurement system setup for radiated performance requirements | 15.1.0 | + +| | | | | | | | | +|--|--|--|--|--|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| | | | | | | R4-1902293 Draft CR for TS 38.141-2: Correction on TM applicability
R4-1902295 Corrections to 38.141-2 clause 4.9.2 base conformation test models
R4-1902319 Draft CR to TS38.141-2 Tx OFF and transient measurement procedure
R4-1902343 CR to TS 38.141-2: FR frequency limit corrections
R4-1902385 Draft CR to TS 38.141-2: Applicability rule for BS radiated demodulation test
R4-1902391 draftCR for TS 38.141-2: Radiated test requirements for CP-OFDM based PUSCH in FR1
R4-1902395 Draft CR to 38.141-2 – PUSCH requirements with CP-OFDM for FR2
R4-1902398 draftCR: Updates to PUCCH format 3 and 4 radiated conformance testing in TS 38.141-2
R4-1902401 Draft CR for updating PRACH performance requirements in TS38.141-2
R4-1902446 Draft CR to TS 38.141-2: Editorial CR for BS radiated demodulation test
R4-1902573 Corrections to 38.141-2 Delay profile calculation
R4-1902647 CR to TS 38.141-2: NR TM Multicarrier Configuration | | +|--|--|--|--|--|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| + +| | | | | | | | | +|---------|--------|-----------|------|--|---|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2019-06 | RAN#84 | RP-191240 | 0005 | | B |

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

Implementation of Draft CRs into the merged Draft CR based on the endorsed tdocs during RAN4#90bis, on top of TS 38.141-2, v15.1.0:
R4-1903326 Draft CR to TS 38.141-2: cleanup
R4-1903331 Draft CR to TS 38.141-2: performance measure correction for the Rx requirements
R4-1903459 Draft CR to TS 38.141-2: Correction to TX requirements with respect to total EIRP in clause 6.2.4.2, clause 6.3.4.2 and Annex B.7.1
R4-1903490 Draft CR to 38.141-2: Addition of measurement uncertainty for FR2 performance requirements
R4-1903615 Draft CR to 38.141-2_Correction on OTA BS output power requirements (6.3)
R4-1903616 Draft CR to 38.141-2: Correction on OTA occupied bandwidth requirements (6.7.2)
R4-1903617 Draft CR to 38.141-2: Correction on OTA transmitter spurious emissions requirements (6.7.5)
R4-1904207 Editorial corrections to TS 38.141-2
R4-1904236 draftCR: Correlation matrix for 8Rx in TS 38.141-2
R4-1904722 Draft CR to TS 38.141-2: Update of applicability rule for BS radiated demodulation test
R4-1904725 Draft CR to TS 38.141-2: Update of radiated test requirements for DFT-s-OFDM based PUSCH
R4-1904728 draftCR for TS 38.141-2: Radiated test requirements for CP-OFDM based PUSCH in FR1
R4-1904731 Draft CR on PRACH performance requirements in TS38.141-2
R4-1904733 Draft CR on TS 38.141-2 Radiated test requirements for PUCCH format 1
R4-1904737 Draft CR on NR PUCCH format2 radiated performance requirements for TS 38.141-2
R4-1904738 Draft CR to TS 38.141-2 Adding required vendor declaration items for BS demodulation
R4-1904741 Draft CR to TS 38.141-2 BS demodulation PUCCH format 0 requirements
R4-1904744 draftCR: Measurement system set-up and TT in TS 38.141-2
R4-1904747 draftCR: Updates to PUCCH format 3 and 4 radiated conformance testing in TS 38.141-2
R4-1904803 Draft CR to TS 38.141-2: FRC update for PUSCH FR1 mapping type B and FR2 DMRS 1+1
R4-1904818 Draft CR: Clarification on step 5 and step 6 for delay profiles calculation (38.141-2)
R4-1904843 Draft CR to TS 38.141-2 BS demodulation CP-OFDM PUSCH FR2 requirements
R4-1905112 Draft CR to TS 38.141-2:Overview of radiated Tx requirements (4.1.1)
R4-1905118 Corrections to TS38.141-2 clause 6.6.3.5 EVM measurement
R4-1905119 draft CR to TS38.141-2 on clause 4.9.2.3 header
R4-1905122 draft CR to TS38.141-2 on test model(Clause 4.9.2)
R4-1905125 draft CR to 38.141-2 for TAE requirements
R4-1905129 draft CR to TS38.141-2 on FR2 OFF power test procedure
R4-1905130 draft CR to TS38.141-2 on TT and MU tables for FR2 OFF power
R4-1905142 Draft CR: editorial correction on FR1 spurious emission requirement in TS38.141-2
R4-1905147 Draft CR to TS 38.141-2: Clarification on application of interfering signal offsets for ACS, blocking and intermodulation requirements
R4-1905150 Draft CR to TS 38.141-2: Corrections on out-

| 15.2.0 | +|---------|--------|-----------|------|--|---|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| + +| | | | | | | | +|--|--|--|--|--|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | | | |

of-band blocking requirement
R4-1905175 Draft CR to TS 38.141-2: FRC reference corrections for the Rx requirements
R4-1905177 Draft CR to TS 38.141-2: consideration of supported frequency range of the operating band
R4-1905183 Draft CR for TS 38.141-2: Improvements of figures in Annex E
R4-1905184 Draft CR to TS 38.141-2: Correction on manufacturer's declarations related to multi-band operation(clause 4.6)
R4-1905185 Draft CR for TS 38.141-2: Addition of NOTE for transmitter intermodulation requirements in certain regions
R4-1905200 Draft CR to TS 38.141-2: Addition of RC test method for spurious emission in clause 6.7 and 7.7
R4-1902647 CR to TS 38.141-2: NR TM Multicarrier Configuration

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-1905216:
R4-1905410 DraftCR to TS 38.141-2 Editorial Corrections
R4-1905536 draftCR to TS 38.141-2 OTA RX spurious emission (clause 7.7)
R4-1905901 draft CR to TS 38.141-2 - corrections to test set up diagrams
R4-1906004 Draft CR to 38.141-2: 6.8 OTA transmitter intermodulation – correction of interfering signal type
R4-1906120 Draft CR to TS 38.141-2 Correction on multi-band test configurations
R4-1906313 Draft CR to 38.141-2: Correction on FRC (Annex A)
R4-1906783 Draft CR to TS38.141-2 on FR2 MU tables correction on frequency range (4.1.2.2, 4.1.2.3)
R4-1906920 Draft CR to TS 38.141-2: Clarification on type of interfering signal for ACS, in-band blocking and ICS requirements
R4-1906968 Draft CR to TS 38.141-2: adding further details to spherical Fibonacci grids (I.4)
R4-1907112 Draft CR to TS 38.141-2: correction of the fundamental frequency limit of 2.55GHz for the spurious emissions
R4-1907245 Draft CR to TS 38.141-2: Update of applicability rule for BS radiated demodulation test
R4-1907248 Draft CR to TS 38.141-2: Update of radiated test requirements for DFT-s-OFDM based PUSCH
R4-1907251 Draft CR to TS 38.141-2: Correction on the terminology in PUSCH FRC tables
R4-1907254 Draft CR to TS38.141-2: Updates of PRACH performance requirements
R4-1907257 Draft CR on NR PUCCH format2 radiated performance requirements for TS 38.141-2
R4-1907260 Draft CR on NR UCI on PUSCH radiated performance requirements for TS 38.141-2
R4-1907263 draftCR: Updates to PUCCH format 3 and 4 radiated conformance testing in TS 38.141-2
R4-1907265 Draft CR on TS 38.141-2 Radiated test requirements for PUCCH format 1
R4-1907271 Draft CR to TS 38.141-2 Manufacturer declaration for BS demodulation
R4-1907274 Draft CR to TS 38.141-2 BS demodulation PUCCH format 0 requirements
R4-1907276 Draft CR to TS 38.141-2 BS demodulation CP-OFDM PUSCH FR2 requirements
R4-1907279 draftCR for TS 38.141-2: Radiated test requirements for CP-OFDM based PUSCH in FR1
R4-1907631 Draft CR to 38.141-2: Term "reference signal" replacing by term "ideal signal" in EVM context

| +|--|--|--|--|--|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | | | | | +|--|--|--|--|--|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| | | | | | | R4-1907633 Draft CR to 38.141-2: corrections to the Annex F structure
R4-1907637 Draft CR to TS38.141-2 on target resource block clarification for EVM measurement (4.9.2.2, 4.9.2.3, 6.6.3.5)
R4-1907639 Draft CR to TS38.141-2: Correction on test model
R4-1907642 Draft CR to TS38.141-2 on TT and MU tables for FR2 Tx OFF power measurement (4.1.2.2, C.1)
R4-1907660 Draft CR to TS 38.141-2 on Spurious emission Category B in FR2
R4-1907663 Draft CR to 38.141-2: BS TAE requirements
R4-1907666 Draft CR to 38.141-2: Clarification of interferer RB frequency for narrowband blocking
R4-1907670 Draft CR to TS 38.141-2: Corrections to Annex I (TRP)
R4-1907671 Draft CR to TS 38.141-2: Correction on usage of terms TRP and EIRP
R4-1907677 Draft CR to 38.141-2: Correction on OTA measurement setup (Annex E)
R4-1907678 Draft CR to TS 38.141-2: Added description of symbol TRP Estimate
R4-1907682 Draft CR to 38.141-2: Correction on procedure for general OTA transmitter spurious emissions requirements (6.7.5)
R4-1907683 Draft CR to 38.141-2: Correction on OTA transmitter spurious emissions co-location requirements (6.7.5)
R4-1907684 Draft CR to 38.141-2 Definition of contiguous transmission bandwidth
R4-1907847 Draft CR to TS 38.141-02: Test model (clause 4.9.2)
R4-1907851 Draft CR to TS 38.141-2: Editorial cleanup of OTA transmit ON/OFF power in clause 6.5
R4-1907853 Draft CR to TS 38.141-2: Clarification om beam identifier declaration in clause 4.6 | | +|--|--|--|--|--|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-----------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2019-06 | RAN#84 | RP-191242 | 0002 | | B | Introduction of band n14 - CR to TS 38.141-2 | 16.0.0 | +| 2019-06 | RAN#84 | RP-191246 | 0003 | | B | Introduction of band n30 - CR to TS 38.141-2 | 16.0.0 | +| 2019-06 | RAN#84 | RP-191250 | 0004 | 1 | B | n65 introduction to 38.141-2 | 16.0.0 | +| 2019-09 | RAN#85 | RP-192029 | 0006 | 1 | F | CR on Protection of SUL bands to TS 38.141-2 | 16.1.0 | +| 2019-09 | RAN#85 | RP-192034 | 0007 | 1 | B | n29 introduction to 38.141-2 | 16.1.0 | +| 2019-09 | RAN#85 | RP-192022 | 0009 | | A | CR to TS 38.141-2: Implementation of endorsed draft CRs from RAN4#92 (Rel-16)
- Mirrors changes in R4-1910361 for Rel-15 TS 38.141-2 | 16.1.0 | +| 2019-12 | RAN#86 | RP-193001 | 0011 | 1 | A | CR to TS 38.141-2: Further update of applicability rule for BS radiated demodulation test (Rel-16) | 16.2.0 | +| 2019-12 | RAN#86 | RP-193001 | 0013 | 1 | A | CR to TS 38.141-2: Update of radiated test requirements for DFT-s-OFDM based PUSCH (Rel-16) | 16.2.0 | +| 2019-12 | RAN#86 | RP-193013 | 0014 | | B | Introduction of 2010-2025MHz SUL band into Rel-16 TS 38.141-2 | 16.2.0 | +| 2019-12 | RAN#86 | RP-193003 | 0018 | 1 | A | CR on correction of NR PUCCH format2 radiated performance requirements (Rel-16) for TS 38.141-2 | 16.2.0 | +| 2019-12 | RAN#86 | RP-193003 | 0020 | 1 | A | CR on correction of NR UCI on PUSCH radiated performance requirements (Rel-16) for TS 38.141-2 | 16.2.0 | +| 2019-12 | RAN#86 | RP-193001 | 0022 | | A | CR on correction on FRC table for FR1 PUSCH radiated performance requirements (Rel-16) for TS 38.141-2 | 16.2.0 | +| 2019-12 | RAN#86 | RP-193003 | 0024 | 1 | A | CR for 38.141-2: Radiated test requirements for CP-OFDM based PUSCH in FR1 | 16.2.0 | +| 2019-12 | RAN#86 | RP-192989 | 0027 | | A | CR to 38.141-2 on Receiver spurious emission requirements | 16.2.0 | +| 2019-12 | RAN#86 | RP-192989 | 0031 | | A | CR to TS 38.141-2: Correction on interference level of receiver dynamic range requirement | 16.2.0 | +| 2019-12 | RAN#86 | RP-192989 | 0033 | | A | CR to TS 38.141-2: Correction on interfering signal frequency offsets for receiver intermodulation requirements | 16.2.0 | +| 2019-12 | RAN#86 | RP-192989 | 0035 | | A | CR to TS 38.141-2: Clarification of conformance testing for same beams | 16.2.0 | +| 2019-12 | RAN#86 | RP-193001 | 0036 | | A | Updates to PRACH OTA tests in TS 38.141-2 for Rel-16 | 16.2.0 | +| 2019-12 | RAN#86 | RP-192989 | 0045 | | A | CR to TS 38.141-2 some clean up of clause 6.3.5 and 6.4.1 | 16.2.0 | +| 2019-12 | RAN#86 | RP-192989 | 0048 | | A | CR to TS38.141-2: further updates on the abbreviations (clause 3.3)-R16 | 16.2.0 | +| 2019-12 | RAN#86 | RP-192989 | 0050 | | A | CR to 38.141-2 additional updates on clarification for NR TM1.1 | 16.2.0 | +| 2019-12 | RAN#86 | RP-192990 | 0054 | | A | CR to 38.141-2: Annex L.5 Resource element TX power | 16.2.0 | +| 2019-12 | RAN#86 | RP-193001 | 0056 | | A | CR to TS 38.141-2 BS demodulation PUCCH format 0 requirements | 16.2.0 | +| 2019-12 | RAN#86 | RP-193001 | 0058 | | A | CR to TS 38.141-2 BS demodulation CP-OFDM PUSCH FR2 requirements | 16.2.0 | +| 2019-12 | RAN#86 | RP-192990 | 0060 | | A | CR to TS 38.141-2: Additional information about alignment needed for TRP measurements in Annex I | 16.2.0 | +| 2019-12 | RAN#86 | RP-192990 | 0065 | | A | CR to 38.141-2: Correction on FR2 Category B OBUE mask | 16.2.0 | +| 2019-12 | RAN#86 | RP-192990 | 0067 | | A | CR Corrections to EVM 38.141-2 Annex L.7 | 16.2.0 | +| 2019-12 | RAN#86 | RP-192990 | 0069 | | A | CR Corrections to EVM 38.141-2 Annex L.4 | 16.2.0 | +| 2019-12 | RAN#86 | RP-192990 | 0071 | | A | CR to TS 38.141-2: correction of the multipath fading reference for BS demodulation requirements, Rel-16 | 16.2.0 | +| 2019-12 | RAN#86 | RP-192990 | 0075 | | A | CR to TS 38.141-2: Additional Tx spur for FR2 - removal, Rel-16 | 16.2.0 | +| 2019-12 | RAN#86 | RP-192990 | 0077 | | A | CR to TS 38.141-2: Calibration procedure for radiated FR2 measurements, Rel-16 | 16.2.0 | +| 2019-12 | RAN#86 | RP-193001 | 0079 | | A | CR: Removal of the square brackets for uncertainty and TT for OTA tests in 38.141-2 (Rel-16) | 16.2.0 | +| 2019-12 | RAN#86 | RP-193001 | 0081 | | A | CR: Updates to manufacture's declarations for demodulation requirements in TS 38.141-2 (Rel-16) | 16.2.0 | +| 2019-12 | RAN#86 | RP-193001 | 0083 | | A | CR: Updates for PUCCH format 3 and 4 radiated conformance testing in TS 38.141-2 (Rel-16) | 16.2.0 | +| 2019-12 | RAN#86 | RP-192990 | 0085 | 1 | A | Corrections of references in measurement uncertainty table | 16.2.0 | +| 2019-12 | RAN#86 | RP-192990 | 0089 | | A | Editorial corrections | 16.2.0 | +| 2019-12 | RAN#86 | RP-192990 | 0091 | | A | Removal of FFS and brackets in RF requirements | 16.2.0 | +| 2019-12 | RAN#86 | RP-193003 | 0094 | | A | CR for TS 38.141-2 Radiated test requirements for NR PUCCH format 1 | 16.2.0 | +| 2019-12 | RAN#86 | RP-193003 | 0095 | | A | CR for TS 38.141-2 Radiated test requirements for NR multi-slot PUCCH | 16.2.0 | +| 2019-12 | RAN#86 | RP-192989 | 0097 | | A | CR to TS 38.141-2: Update to Table C.1-2 FR2 OTA transmitter tests | 16.2.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|--------------------------------------------------------------------------------------------------------------------------------|--------| +| 2019-12 | RAN#86 | RP-192989 | 0098 | | A | CR to 38.141-2: OTA ACLR (6.7.3) | 16.2.0 | +| 2019-12 | RAN#86 | RP-192989 | 0099 | | A | CR to 38.141-2: OTA receiver intermodulation procedure (7.8) | 16.2.0 | +| 2019-12 | RAN#86 | RP-192989 | 0100 | | A | CR to 38.141-2: OTA transmitter spurious emissions (6.7) | 16.2.0 | +| 2019-12 | RAN#86 | RP-192989 | 0101 | | A | CR to 38.141-2: OTA receiver spurious emissions (7.7) | 16.2.0 | +| 2020-03 | RAN#87 | RP-200403 | 0104 | | A | CR on correction of NR UCI on PUSCH radiated performance requirements for TS 38.141-2 | 16.3.0 | +| 2020-03 | RAN#87 | RP-200403 | 0109 | 1 | A | CR to TS 38.141-2: Corrections on rated carrier output power symbols and clarifications on procedure for reverberation chamber | 16.3.0 | +| 2020-03 | RAN#87 | RP-200403 | 0111 | | A | CR to TS 38.141-2: Corrections on generation of test configurations | 16.3.0 | +| 2020-03 | RAN#87 | RP-200403 | 0118 | | A | CR to TS 38.141-2: Regional requirements | 16.3.0 | +| 2020-03 | RAN#87 | RP-200403 | 0120 | | A | IntraSlot frequency hopping applicability in the one OFDM symbol test case | 16.3.0 | +| 2020-03 | RAN#87 | RP-200403 | 0128 | | A | CR to 38.141-2 updates for OSTP calculations | 16.3.0 | +| 2020-03 | RAN#87 | RP-200403 | 0130 | | A | CR to 38.141-2 updates for reference to annex F and OFDM symbol TX power | 16.3.0 | +| 2020-03 | RAN#87 | RP-200446 | 0143 | | A | CR to TS 38.141-2: Random data content for NR BS Test Models | 16.3.0 | +| 2020-03 | RAN#87 | RP-200381 | 0105 | | B | Introduction of n26 | 16.3.0 | +| 2020-03 | RAN#87 | RP-200382 | 0106 | 1 | B | Introduction of n53 | 16.3.0 | +| 2020-03 | RAN#87 | RP-200379 | 0116 | 1 | C | CR for 38.141-2: new FRC tables for FR2 PUSCH 2T2R MCS12 | 16.3.0 | +| 2020-03 | RAN#87 | RP-200407 | 0121 | 1 | B | Introducing of conformance tests for 350 km/h HST | 16.3.0 | +| 2020-03 | RAN#87 | RP-200407 | 0122 | 1 | B | Introduction of HST 350 km/h FRCs and channel model | 16.3.0 | +| 2020-03 | RAN#87 | RP-200379 | 0132 | 1 | C | CR for 38.141-2: Radiated test requirements for FR2 PUSCH 2T2R 16QAM | 16.3.0 | +| 2020-03 | RAN#87 | RP-200403 | 0138 | 1 | F | Corrections on receiver intermodulation | 16.3.0 | +| 2020-06 | RAN#88 | RP-200986 | 0145 | | A | CR for 38.141-2: Radiated test requirements clarification of PUSCH BS Type O-2 PT-RS configuration for MCS 2 | 16.4.0 | +| 2020-06 | RAN#88 | RP-201043 | 0146 | | F | CR for 38.141-2: Radiated test requirements for FR2 PUSCH 2T2R 16QAM | 16.4.0 | +| 2020-06 | RAN#88 | RP-200986 | 0148 | | A | CR to TS 38.141-2: Correction on frequency offset symbols in test configurations | 16.4.0 | +| 2020-06 | RAN#88 | RP-200986 | 0150 | | A | CR to TS 38.141-2: Correction on test procedure of OTA in-channel selectivity | 16.4.0 | +| 2020-06 | RAN#88 | RP-200986 | 0158 | | A | CR 38.141-2 Rel16 4.9.2.3 corrections for random data generation | 16.4.0 | +| 2020-06 | RAN#88 | RP-200986 | 0162 | | A | CR to TS 38.141-2: Correction to out-of-band blocking requirement in clause 7.6 | 16.4.0 | +| 2020-06 | RAN#88 | RP-200972 | 0165 | | B | CR to TS 38.141-2: Introduction of FR2 DL 256QAM | 16.4.0 | +| 2020-06 | RAN#88 | RP-200986 | 0168 | | A | CR to TS 38.141-2: MU and TT value tables | 16.4.0 | +| 2020-06 | RAN#88 | RP-200986 | 0170 | | A | CR to TS 38.141-2: OTA receiver intermodulation interference signal type | 16.4.0 | +| 2020-06 | RAN#88 | RP-200986 | 0174 | | A | NR FR2 test models for 16QAM | 16.4.0 | +| 2020-06 | RAN#88 | RP-200986 | 0179 | | A | CR to TS 38.141-2: Corrections for the extreme environment testing, Rel-16 | 16.4.0 | +| 2020-06 | RAN#88 | RP-201005 | 0181 | | A | CR to TS 38.141-2: internal TR references corrections (wrt. TR 37.941 for OTA BS testing), Rel-16 | 16.4.0 | +| 2020-06 | RAN#88 | RP-200986 | 0183 | | A | CR to 38.141-2: Correction on required SNR value for multi-slot PUCCH testing (8.3.6) (C.3) | 16.4.0 | +| 2020-06 | RAN#88 | RP-200986 | 0185 | | A | CR to TS 38.141-2 - Manufacturer declaration clarifications | 16.4.0 | +| 2020-06 | RAN#88 | RP-200978 | 0190 | | B | CR to 38.141-2 for Introduction of band n259 | 16.4.0 | +| 2020-06 | RAN#88 | RP-200986 | 0192 | | A | CR to TS 38.141-2: Adding spherical angle definitions to 3.2 | 16.4.0 | +| 2020-06 | RAN#88 | RP-200986 | 0194 | | A | CR to TS 38.141-2: Correcting the reference angular step equations (Annex I.2.2) | 16.4.0 | +| 2020-06 | RAN#88 | RP-200986 | 0198 | | A | CR to 38.141-2 on EESS protection for bands n257 and n258 (Rel-16) | 16.4.0 | +| 2020-06 | RAN#88 | RP-200975 | 0159 | 1 | B | Introduction of conformance tests for 350kph and 500kph HST | 16.4.0 | +| 2020-06 | RAN#88 | RP-200975 | 0160 | 1 | B | HST PUSCH demodulation FRC and channel condition annex | 16.4.0 | +| 2020-06 | RAN#88 | RP-200975 | 0166 | 1 | F | CR for 38.141-2 Introduction of PRACH radiated conformance testing for NR HST | 16.4.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-----------------------------------------------------------------------------------------------------------------|--------| +| 2020-06 | RAN#88 | RP-200975 | 0152 | 1 | B | CR for TS 38.141-2: introduction of NR PUSCH UL timing adjustment | 16.4.0 | +| 2020-06 | RAN#88 | RP-200975 | 0153 | 1 | B | CR for TS 38.141-2: appendix for NR PUSCH UL timing adjustment | 16.4.0 | +| 2020-06 | RAN#88 | RP-201043 | 0151 | 1 | B | CR for TS 38.141-2: Introduce PUSCH performance requirements at 30% throughput test point | 16.4.0 | +| 2020-06 | RAN#88 | RP-200975 | 0154 | 2 | B | CR for TS 38.141-2, Introduction of high speed support declaration for NR HST | 16.4.0 | +| 2020-09 | RAN#89 | RP-201497 | 0203 | | B | CR for TS 38.141-2: Introduction of NR PUSCH UL timing adjustment performance requirement for scenario Z | 16.5.0 | +| 2020-09 | RAN#89 | RP-201497 | 0205 | | F | CR for TS 38.141-2: Add maximum test system uncertainty for NR HST PUSCH with single port and AWGN | 16.5.0 | +| 2020-09 | RAN#89 | RP-201497 | 0206 | 1 | B | CR for TS 38.141-2, Introduction of high speed support declaration for NR HST | 16.5.0 | +| 2020-09 | RAN#89 | RP-201512 | 0210 | | A | Clarification CR on NR-FR2-TM3.1 | 16.5.0 | +| 2020-09 | RAN#89 | RP-201512 | 0212 | | A | CR for TS 38.141-2: NR FR2 test model 2 | 16.5.0 | +| 2020-09 | RAN#89 | RP-201512 | 0214 | 1 | A | CR to TS 38.141-2: Additional requirements for EESS protection (rel-16) | 16.5.0 | +| 2020-09 | RAN#89 | RP-201512 | 0216 | | A | Increase of step size for FR2 in-band blocking conformance test | 16.5.0 | +| 2020-09 | RAN#89 | RP-201497 | 0218 | 1 | F | CR for TS 38.141-2: Introduction of test tolerance for NR HST PRACH | 16.5.0 | +| 2020-09 | RAN#89 | RP-201512 | 0220 | 1 | A | CR to 38.141-2: Annex L clarification on equalisation calculation (L.6) | 16.5.0 | +| 2020-12 | RAN#90 | RP-202422 | 0228 | 1 | F | CR for 38.141-2: Introduction of NR PUSCH UL timing adjustment performance requirement for scenario X | 16.6.0 | +| 2020-12 | RAN#90 | RP-202489 | 0230 | | A | CR for 38.141-2: Add error-free feedback in demodulation requirement test setup | 16.6.0 | +| 2020-12 | RAN#90 | RP-202415 | 0231 | 1 | B | CR to TS 38.141-2: BS demodulation requirements for 2-step RACH (Annex) | 16.6.0 | +| 2020-12 | RAN#90 | RP-202416 | 0234 | 1 | B | Introduction of URLLC 0.001% BLER requirement | 16.6.0 | +| 2020-12 | RAN#90 | RP-202416 | 0235 | 1 | B | CR for 38.141-2: URLLC testing methodology appendix | 16.6.0 | +| 2020-12 | RAN#90 | RP-202416 | 0239 | 1 | B | CR to TS 38.141-2: Addition of BS conformance testing for FR2 URLLC PUSCH repetition Type A | 16.6.0 | +| 2020-12 | RAN#90 | RP-202416 | 0240 | 1 | B | CR to TS 38.141-2: FRC for FR1 URLLC BS performance requirements | 16.6.0 | +| 2020-12 | RAN#90 | RP-202422 | 0245 | 1 | B | Additional test cases and FRC tables for HST PUSCH | 16.6.0 | +| 2020-12 | RAN#90 | RP-202416 | 0246 | 1 | B | CR on FR2 requirements for PUSCH mapping Type B with low number of symbols | 16.6.0 | +| 2020-12 | RAN#90 | RP-202437 | 0251 | | F | CR to 38.141-2: Correction to test system uncertainty | 16.6.0 | +| 2020-12 | RAN#90 | RP-202489 | 0255 | | A | CR to 38.141-2 on Category B OTA spurious emissions for Band n257 | 16.6.0 | +| 2020-12 | RAN#90 | RP-202422 | 0256 | 1 | B | CR for 38.141-2 Introduction of conformance testing for NR HST PRACH under fading channel | 16.6.0 | +| 2020-12 | RAN#90 | RP-202509 | 0257 | | F | CR to 38.141-2: Annex C correction on frequency range of FR2 TT table (C.2) | 16.6.0 | +| 2020-12 | RAN#90 | RP-202415 | 0258 | | B | CR on MsgA PUSCH radiated performance requirement for TS 38.141-2 | 16.6.0 | +| 2020-12 | RAN#90 | RP-202451 | 0223 | | B | Introduction of 1880-1920MHz SUL band into Rel-17 TS 38.141-2 | 17.0.0 | +| 2020-12 | RAN#90 | RP-202452 | 0225 | | B | Introduction of 2300-2400MHz SUL band into Rel-17 TS 38.141-2 | 17.0.0 | +| 2020-12 | RAN#90 | RP-202448 | 0241 | | B | CR to TS 38.141-2: introduction of NR band n13 | 17.0.0 | +| 2021-03 | RAN#91 | RP-210097 | 0259 | | B | CR for 38.141-2 introduction of NR band n24 | 17.1.0 | +| 2021-03 | RAN#91 | RP-210096 | 0260 | | B | CR to 38.141-2 on introducing new SUL band n99 | 17.1.0 | +| 2021-03 | RAN#91 | RP-210116 | 0265 | | A | CR for TS 38.142-2: Correction on definition for the out-of-band CLTA (Rel-17) | 17.1.0 | +| 2021-03 | RAN#91 | RP-210116 | 0268 | | A | CR for 38.141-2: BS demodulation different channel bandwidths applicability rules | 17.1.0 | +| 2021-03 | RAN#91 | RP-210068 | 0270 | | A | CR on FRC for URLLC BS radiated performance requirement for TS 38.141-2 | 17.1.0 | +| 2021-03 | RAN#91 | RP-210073 | 0272 | | A | CR on MsgA PUSCH radiated performance requirement for TS 38.141-2 | 17.1.0 | +| 2021-03 | RAN#91 | RP-210078 | 0274 | 1 | A | Finalize SNR values for HST PUSCH | 17.1.0 | +| 2021-03 | RAN#91 | RP-210068 | 0276 | | A | CR for TS 38.141-2: Updates of performance requirements of PUSCH repetition type A and PUSCH mapping type B for | 17.1.0 | + +| | | | | | | | | +|--|--|--|--|--|--|---------------|--| +| | | | | | | URLLC for FR1 | | +|--|--|--|--|--|--|---------------|--| + +| | | | | | | | | +|---------|--------|-----------|------|---|---|------------------------------------------------------------------------------------------------------|--------| +| 2021-03 | RAN#91 | RP-210116 | 0279 | | A | CR to TS 38.141-2: Additions of regional requirements for n41 and n90 in Japan, Rel-17 | 17.1.0 | +| 2021-03 | RAN#91 | RP-210068 | 0281 | | A | CR on FR2 requirements for PUSCH mapping Type B with low number of symbols (Rel-17) | 17.1.0 | +| 2021-03 | RAN#91 | RP-210073 | 0283 | | A | CR on update applicability rule for 2-step RACH in 38.141-2 (Rel-17) | 17.1.0 | +| 2021-03 | RAN#91 | RP-210078 | 0285 | | A | CR for 38.141-2 Cleanup of conformance testing for NR HST PRACH under fading channel (Rel-17) | 17.1.0 | +| 2021-03 | RAN#91 | RP-210068 | 0287 | | A | CR to TS38.141-2 Correction of BS conformance testing for FR2 URLLC PUSCH repetition Type A (Rel-17) | 17.1.0 | +| 2021-03 | RAN#91 | RP-210116 | 0295 | | A | CR to TS 38.141-2 clarification on PN23 sequence generation | 17.1.0 | +| 2021-03 | RAN#91 | RP-210116 | 0298 | | A | CR to TS 38.141-2: EESS protection requirement correction | 17.1.0 | +| 2021-03 | RAN#91 | RP-210116 | 0301 | | A | CR to TS 38.141-2: Receiver requirement corrections | 17.1.0 | +| 2021-03 | RAN#91 | RP-210068 | 0303 | | A | CR to TS 38.141-2 Update of 0.001% BLER test requirements | 17.1.0 | +| 2021-03 | RAN#91 | RP-210116 | 0314 | | A | CR for 38.141-2: BS demodulation synchronization in test setup | 17.1.0 | +| 2021-06 | RAN#92 | RP-211104 | 0318 | | A | CR for TS 38.141-2: Introduction of NR PUSCH UL TA performance requirement(Rel-17) | 17.2.0 | +| 2021-06 | RAN#92 | RP-211094 | 0320 | | A | Big CR for NR-U BS radiated conformance testing in TS 38.141-2 | 17.2.0 | +| 2021-06 | RAN#92 | RP-211105 | 0322 | | A | CR for TS38.141-2 remove SNR brackets for HST PUSCH demodulation (catA) | 17.2.0 | +| 2021-06 | RAN#92 | RP-211105 | 0326 | | A | CR for TS 38.141-2 Updates of performance requirements of PUSCH repetition type A for URLLC | 17.2.0 | +| 2021-06 | RAN#92 | RP-211116 | 0327 | 1 | B | CR to TS 38.141-2: Introduction of band n67 | 17.2.0 | +| 2021-06 | RAN#92 | RP-211116 | 0328 | 1 | B | CR to TS 38.141-2: Introduction of band n85 | 17.2.0 | +| 2021-06 | RAN#92 | RP-211108 | 0336 | | A | CR for 38.141-2: HST demodulation specification maintenance | 17.2.0 | +| 2021-06 | RAN#92 | RP-211109 | 0338 | | A | CR for 38.141-2: Demodulation performance enhancement specification maintenance | 17.2.0 | +| 2021-06 | RAN#92 | RP-211094 | 0345 | | A | TS 38.141-2: Introduction of NR-U co-existence requirements | 17.2.0 | +| 2021-06 | RAN#92 | RP-211089 | 0348 | | A | TS 38.141-2: Correction of additional spurious emission limits for bands 50, 51, 75, 76 | 17.2.0 | +| 2021-06 | RAN#92 | RP-211090 | 0351 | | A | CR to 38.141-2: removal of outstanding TBDs, Rel-17 | 17.2.0 | +| 2021-06 | RAN#92 | RP-211090 | 0354 | | A | CR to 38.141-2: In-band blocking for multi-band Base Stations | 17.2.0 | +| 2021-06 | RAN#92 | RP-211091 | 0355 | | A | CR to 38.141-2: BS conformance test, FR2 Rx OOB test MU value correction (4.1.2.3) | 17.2.0 | +| 2021-06 | RAN#92 | RP-211082 | 0359 | | A | CR to TS 38.141-2: Receiver IMD requirement corrections | 17.2.0 | +| 2021-06 | RAN#92 | RP-211083 | 0362 | | A | CR for 38.141-2: Add AWGN Offset notes to FR1 and FR2 demod noise levels | 17.2.0 | +| 2021-09 | RAN#93 | RP-211909 | 0365 | | B | CR to TS 38.141-2: Introduction of 35MHz and 45MHz | 17.3.0 | +| 2021-09 | RAN#93 | RP-211898 | 0368 | | B | CR to 38.141-2: Introduction of n262 | 17.3.0 | +| 2021-09 | RAN#93 | RP-211926 | 0371 | | A | Big CR for TS 38.141-2 Maintenance RF part (Rel-17, CAT A) | 17.3.0 | +| 2021-09 | RAN#93 | RP-211926 | 0374 | | A | Big CR for TS 38.141-2 Maintenance Demod part (Rel-17, CAT A) | 17.3.0 | +| 2021-12 | RAN#94 | RP-212850 | 0376 | | A | Big CR for TS 38.141-2 Maintenance Demod part (Rel-17, CAT A) | 17.4.0 | +| 2021-12 | RAN#94 | RP-212856 | 0379 | | A | Big CR for TS 38.141-2 Maintenance RF part (Rel-17, CAT A) | 17.4.0 | +| 2022-03 | RAN#95 | RP-220347 | 0384 | 1 | B | CR to TS 38.141-2: implementation of LTE_upper_700MHz_A band 103 | 17.5.0 | +| 2022-03 | RAN#95 | RP-220357 | 0385 | | B | CR to TS 38.141-2 the introduction of EU unlicensed band n102 | 17.5.0 | +| 2022-03 | RAN#95 | RP-220361 | 0386 | | B | Big CR for TS38.141-2 FR1 PUSCH 256QAM | 17.5.0 | +| 2022-03 | RAN#95 | RP-220337 | 0389 | | A | Big CR for TS 38.141-2 Maintenance RF part (Rel-17, CAT A) | 17.5.0 | +| 2022-03 | RAN#95 | RP-220337 | 0392 | | A | Big CR for TS 38.141-2 Maintenance Demod part (Rel-17, CAT A) | 17.5.0 | +| 2022-03 | RAN#95 | RP-220376 | 0393 | | B | CR to TS 38.141-2: RMR 1900MHz band n101 introduction | 17.5.0 | +| 2022-06 | RAN#96 | RP-221660 | 0398 | 1 | F | CR to 38.141-2: BS FR2 OBUE Cat B requirement table note | 17.6.0 | + +| | | | | | | | | +|---------|----------|-----------|------|---|---|----------------------------------------------------------------------------------------------------------------------|--------| +| | | | | | | clarification (6.7.4.5.2) | | +| 2022-06 | RAN#96 | RP-221684 | 0400 | | B | CR to TS 38.141-2: RMR 900MHz band introduction | 17.6.0 | +| 2022-06 | RAN#96 | RP-221680 | 0403 | | B | Big CR to TS 38.141-2 on HST FR2 BS Demodulation Performance Requirements | 17.6.0 | +| 2022-06 | RAN#96 | RP-221660 | 0406 | | F | Big CR for TS 38.141-2 Maintenance RF part (Rel-17, CAT F) | 17.6.0 | +| 2022-09 | RAN#97 | RP-222037 | 0407 | 1 | B | CR to TS 38.141-2 - Introduction of licensed 6GHz band n104 | 17.7.0 | +| 2022-09 | RAN#97 | RP-222034 | 0408 | 1 | B | CR to TS 38.141-2: Introduction of 1024 QAM in FR1 | 17.7.0 | +| 2022-09 | RAN#97 | RP-222041 | 0419 | | F | Big CR on FR2 HST BS demodulation requirement for TS 38.141-2 | 17.7.0 | +| 2022-09 | RAN#97 | RP-222026 | 0422 | | F | Big CR for TS 38.141-2 Maintenance RF part (Rel-17, CAT F)
NOTE: This CR is partially implemented for NR band n46 | 17.7.0 | +| 2022-09 | RAN#97 | RP-222026 | 0425 | | F | Big CR for TS 38.141-2 Maintenance Demod part (Rel-17, CAT F) | 17.7.0 | +| 2022-12 | RAN#98-e | RP-223309 | 0427 | 1 | F | CR to 38.141-2: Spurious emission requirements, Rel-17 | 17.8.0 | +| 2022-12 | RAN#98-e | RP-223302 | 0429 | | B | Big CR for TS 38.141-2 Demodulation requirements for Enhanced IIOT and URLLC support | 17.8.0 | +| 2022-12 | RAN#98-e | RP-223293 | 0432 | | A | CR to 38.141-2: Additional BS conformance to other standards | 17.8.0 | +| 2022-12 | RAN#98-e | RP-223300 | 0433 | | B | Big CR for coverage enhancement performance requirements for TS38.141-2 | 17.8.0 | + +| Change history | | | | | | | | +|----------------|----------|-----------|------|-----|-----|------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-12 | RAN#98-e | RP-223315 | 0435 | - | B | CR to 38.141-2 on introduction of Band 54 | 18.0.0 | +| 2022-12 | RAN#98-e | RP-223319 | 0436 | - | B | CR to 38.141-2 on introduction of Band n105 | 18.0.0 | +| 2023-03 | RAN#99 | RP-230513 | 0438 | | A | Correction of coverage enhancement BS demodulation requirement in 38.141-2 (R18 A) | 18.1.0 | +| 2023-03 | RAN#99 | RP-230510 | 0440 | | A | Big CR to 38.141-2: demodulation requirements introduction for FR2-2 | 18.1.0 | +| 2023-03 | RAN#99 | RP-230505 | 0444 | | A | CR for TS 38.141-2, Correction on transmitter spatial emissions declaration in Annex G | 18.1.0 | +| 2023-03 | RAN#99 | RP-230505 | 0448 | | A | Update to PUSCH performance test cases | 18.1.0 | +| 2023-03 | RAN#99 | RP-230535 | 0449 | 1 | B | CR to 38.141-2 on introduction of Band n54 | 18.1.0 | +| 2023-03 | RAN#99 | RP-230506 | 0452 | | A | CR to 38.141-2: FRC number corrections (Rel-18) | 18.1.0 | +| 2023-03 | RAN#99 | RP-230513 | 0454 | | A | CR to 38.141-2: NOTE for n104 in BS co-existence table | 18.1.0 | +| 2023-03 | RAN#99 | RP-230513 | 0456 | | A | CR to 38.141-2: BS Conformance, OBUE correction for 6G licensed band | 18.1.0 | +| 2023-03 | RAN#99 | RP-230513 | 0458 | | A | CR to 38.141-2: BS Conformance, removal of [] for 47GHz Rx test | 18.1.0 | +| 2023-03 | RAN#99 | RP-230514 | 0463 | | A | CR to 38.141-2: MU values for OBW requirements (Rel-18) | 18.1.0 | +| 2023-03 | RAN#99 | RP-230513 | 0474 | | A | Correction CR on PUCCH JCE requirements for TS 38.141-2 | 18.1.0 | +| 2023-03 | RAN#99 | RP-230515 | 0475 | | A | Correction CR on PUCCH performance requirements for IIOT and URLLC for TS 38.141-2 | 18.1.0 | +| 2023-03 | RAN#99 | RP-230515 | 0476 | | A | Update to HST Model FR2 requirements | 18.1.0 | +| 2023-03 | RAN#99 | RP-230510 | 0478 | | A | Big CR to TS 38.141-2: FR2-2 BS RF test requirements introduction, Rel-18 | 18.1.0 | +| 2023-06 | RAN#100 | RP-231347 | 0480 | | A | Draft CR 38.141-2: PUCCH requirements for FR2-2 | 18.2.0 | +| 2023-06 | RAN#100 | RP-231347 | 0482 | | A | CR to TS 38.141-2 on completion of measurement uncertainties for extending current NR operation to 71GHz | 18.2.0 | +| 2023-06 | RAN#100 | RP-231354 | 0485 | | A | CR for TS 38.141-2 UL TA Demod requirements relative TPUT addition (NR_HST, Rel-18, CAT A) | 18.2.0 | +| 2023-06 | RAN#100 | RP-231354 | 0487 | | A | CR for TS 38.141-2 UL TA Demod requirements relative TPUT addition (NR_HST_FR2, Rel-18, CAT A) | 18.2.0 | +| 2023-06 | RAN#100 | RP-231347 | 0489 | | A | CR for TS38.141-2 FRC tables for FR2-2 PUSCH demodulation, Rel-18 | 18.2.0 | +| 2023-06 | RAN#100 | RP-231350 | 0491 | 1 | A | CR for TS38.141-2 on FRC table for PUSCH TBoMS, Rel-18 | 18.2.0 | +| 2023-06 | RAN#100 | RP-231339 | 0495 | | A | CR to TS 38.141-2 - Maintenance related to bands n100 and n101 | 18.2.0 | +| 2023-06 | RAN#100 | RP-231352 | 0498 | | A | CR on 38.141-2: Updates to FRC of PUSCH requirements(Rel-18) | 18.2.0 | +| 2023-06 | RAN#100 | RP-231347 | 0500 | | A | CR on 38.141-2: Updates to FR2-2 PUSCH requirements(Rel-18) | 18.2.0 | +| 2023-06 | RAN#100 | RP-231347 | 0502 | | A | CR to 38.141-2: 71 GHz Extension BS conformance test Test Model clarification | 18.2.0 | +| 2023-06 | RAN#100 | RP-231362 | 0505 | | B | CR to 38.141-2 on introduction of Band 106 | 18.2.0 | +| 2023-06 | RAN#100 | RP-231358 | 0509 | | A | CR to 38.141-2: Correction to ACLR and CACLR requirement | 18.2.0 | +| 2023-09 | RAN#101 | RP-232505 | 0546 | - | A | TS 38.141-2: Corrections | 18.3.0 | +| 2023-09 | RAN#101 | RP-232490 | 0542 | 1 | A | [NR_ext_to_71GHz-Perf] CR to TS 38.141-2: propagation conditions annex J reference corrections, Rel-18 | 18.3.0 | +| 2023-09 | RAN#101 | RP-232490 | 0539 | - | A | [NR_FR1_35MHz_45MHz_BW-Core] CR to 38.141-2: Correction on EVM window length table R18 | 18.3.0 | +| 2023-09 | RAN#101 | RP-232488 | 0532 | - | A | Update to Test Case 8.2.13 (FDD case, PUSCH Aggregation Factor 8), Rel18, 38.141-2 | 18.3.0 | +| 2023-09 | RAN#101 | RP-232492 | 0530 | - | A | CR for TS38.141-2 add declaration and applicability rule for URLLC requirements | 18.3.0 | +| 2023-09 | RAN#101 | RP-232490 | 0525 | 1 | A | CR to TS 38.141-2 on completion of measurement uncertainties for extending current NR operation to 71GHz | 18.3.0 | +| 2023-12 | RAN#102 | RP-233366 | 0551 | | B | CR to TS 38.141-2 on introduction NR bands n31 and n72 | 18.4.0 | +| 2023-12 | RAN#102 | RP-233345 | 0557 | | A | [NR_ext_to_71GHz-Perf] CR to 38.141-2: 71 GHz Extension BS performance test PRACH offset correction R18 | 18.4.0 | +| 2023-12 | RAN#102 | RP-233366 | 0561 | | B | CR to 38.141-2 on introduction of Band 106 | 18.4.0 | +| 2023-12 | RAN#102 | RP-233363 | 0552 | 1 | F | [NR_FR1_lessthan_5MHz_BW-Core] CR for OTA Tx intermodulation requirements in certain region | 18.4.0 | +| 2023-12 | RAN#102 | RP-233363 | 0563 | | B | Big CR for TS 38.141-2 on 4Tx demodulation requirements | 18.4.0 | +| 2023-12 | RAN#102 | RP-233339 | 0550 | 1 | A | [NR_n18-Perf] CR to TS 38.141-2 on correction of transmitter spurious emissions for protection of Band n18 | 18.4.0 | +| 2023-12 | RAN#102 | RP-233366 | 0553 | 1 | B | CR to TS38.141-2 Introduction of n109 | 18.4.0 | + diff --git a/marked/Rel-18/38_series/38161/072320147c6e0a97ea1854ac62ddfe17_img.jpg b/marked/Rel-18/38_series/38161/072320147c6e0a97ea1854ac62ddfe17_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f184c7bc499a01b35de34b0cc267746f3239750 --- /dev/null +++ b/marked/Rel-18/38_series/38161/072320147c6e0a97ea1854ac62ddfe17_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a7d3525bdbd0037a8938c665fc62a36e4f4ac977de4388f8e9d5b7dbd352f60 +size 50591 diff --git a/marked/Rel-18/38_series/38161/0ba96c8121e21d5b3cdd48e3e19546fd_img.jpg b/marked/Rel-18/38_series/38161/0ba96c8121e21d5b3cdd48e3e19546fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e6a54e8bce22466d6bba405c5810f1da07d6835 --- /dev/null +++ b/marked/Rel-18/38_series/38161/0ba96c8121e21d5b3cdd48e3e19546fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a9f57ff0a6cf06209b68a0af51f91bea6ecfc0adb43d39b3ec1553e6b3d8fee +size 20245 diff --git a/marked/Rel-18/38_series/38161/0e15b493e5acc6fa1d411bea5cae7164_img.jpg b/marked/Rel-18/38_series/38161/0e15b493e5acc6fa1d411bea5cae7164_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d2619779fda583c575b038e8bba826bced76997 --- /dev/null +++ b/marked/Rel-18/38_series/38161/0e15b493e5acc6fa1d411bea5cae7164_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bb4e51c9249465e5cfc7bded14357a4eb4f40d3eb0a79346b3a9efb25b6fdcf9 +size 24460 diff --git a/marked/Rel-18/38_series/38161/1a71c1fcfe031ac87d6458c6b5062bf1_img.jpg b/marked/Rel-18/38_series/38161/1a71c1fcfe031ac87d6458c6b5062bf1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0154045ca807fed39a36aa60f7a0745d99913aea --- /dev/null +++ b/marked/Rel-18/38_series/38161/1a71c1fcfe031ac87d6458c6b5062bf1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a70a7956681c96eee73218d824853c34a2a91c1018f84749b9270f33c09c0ac +size 14158 diff --git a/marked/Rel-18/38_series/38161/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-18/38_series/38161/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ee9a380942b3ce0f848f6f44571772af341b32e --- /dev/null +++ b/marked/Rel-18/38_series/38161/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:33e8ded3588f7ba2da0c16ebc1576882515fb462e5067e5fb44171b9d0a630a0 +size 172199 diff --git a/marked/Rel-18/38_series/38161/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-18/38_series/38161/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da376b4ea71c216b61121f6bff20f212afcb747a --- /dev/null +++ b/marked/Rel-18/38_series/38161/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a12dd2f372bc4cca408ecf512d96de5745ed2b10c6afcf46de399f02320fe80 +size 28505 diff --git a/marked/Rel-18/38_series/38161/39ca823ef41ba00da416ecc099940770_img.jpg b/marked/Rel-18/38_series/38161/39ca823ef41ba00da416ecc099940770_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7dd648552537bbac23548f0e80b1fd6368fc8ed5 --- /dev/null +++ b/marked/Rel-18/38_series/38161/39ca823ef41ba00da416ecc099940770_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f7dfd95286263a094a72f05db837d65be936e59bd882695762a05c931a19985 +size 13018 diff --git a/marked/Rel-18/38_series/38161/4ba0c02941829d6ece2e065f08a4e575_img.jpg b/marked/Rel-18/38_series/38161/4ba0c02941829d6ece2e065f08a4e575_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00138f6dcef0391b3a9c60e84f2670aae7c0507d --- /dev/null +++ b/marked/Rel-18/38_series/38161/4ba0c02941829d6ece2e065f08a4e575_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:12a97f94063f3df452283b7556fd093312f3cb71ddaf796a1a73375cb18ce90d +size 9095 diff --git a/marked/Rel-18/38_series/38161/4ece98b7109616bdd7b02d2da1d5cdb8_img.jpg b/marked/Rel-18/38_series/38161/4ece98b7109616bdd7b02d2da1d5cdb8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..06c9c9fc6ac18ce99bba4e2766e59f2921bad8f7 --- /dev/null +++ b/marked/Rel-18/38_series/38161/4ece98b7109616bdd7b02d2da1d5cdb8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:63f868e2b073143213e54e7d546dba7364c986cb8ac4d45130d4310c267143f5 +size 14158 diff --git a/marked/Rel-18/38_series/38161/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38161/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52c6f136a54cb9c6bddbbe9ddafb95d3873256d0 --- /dev/null +++ b/marked/Rel-18/38_series/38161/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/38161/62051fc7741291f88d17b08447d20455_img.jpg b/marked/Rel-18/38_series/38161/62051fc7741291f88d17b08447d20455_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dfd579c5ca57766b68b627ae9403302f4eed3c29 --- /dev/null +++ b/marked/Rel-18/38_series/38161/62051fc7741291f88d17b08447d20455_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9c8a06de9c2cf7fdb4c6888f1d9de5f594ccd97a056521cba07beabdb5b28f7 +size 9647 diff --git a/marked/Rel-18/38_series/38161/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38161/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..49bcd70dc2731bb08fe266516be2a54150925f73 --- /dev/null +++ b/marked/Rel-18/38_series/38161/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e5eb2d3f7487c9ca08e82820abb12cecef805c01e17f9600610fbb4e2c01173 +size 5673 diff --git a/marked/Rel-18/38_series/38161/69350f1ebebf4e4b2d5644dfc6671d7c_img.jpg b/marked/Rel-18/38_series/38161/69350f1ebebf4e4b2d5644dfc6671d7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e3e8b064aa8c1ecfb927b2d149ea9868a0aa677 --- /dev/null +++ b/marked/Rel-18/38_series/38161/69350f1ebebf4e4b2d5644dfc6671d7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed21086c707d48664e2be92630ed3a5d572177dd30228f96be7efc9457d02a01 +size 22056 diff --git a/marked/Rel-18/38_series/38161/9ac4f77294db49ed5489461c24bb01bf_img.jpg b/marked/Rel-18/38_series/38161/9ac4f77294db49ed5489461c24bb01bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8022bd456cbf4992443ff7f3dd78f6554e840600 --- /dev/null +++ b/marked/Rel-18/38_series/38161/9ac4f77294db49ed5489461c24bb01bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a458f2150418f7aace2b7eb3eacbaddcc1a97491e16831e23975422fd09f244 +size 14877 diff --git a/marked/Rel-18/38_series/38161/9b686adccf125267a013fa25721231a3_img.jpg b/marked/Rel-18/38_series/38161/9b686adccf125267a013fa25721231a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f69c28a73427d032a48823ffb76980870affb3a --- /dev/null +++ b/marked/Rel-18/38_series/38161/9b686adccf125267a013fa25721231a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f3184d2ff92c941731d7a30f43a0b97ee40fbd661f6dbc2d1343fbfabafe9cd8 +size 27913 diff --git a/marked/Rel-18/38_series/38161/c925eb337128296a214c69e40455be77_img.jpg b/marked/Rel-18/38_series/38161/c925eb337128296a214c69e40455be77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad391aa07a2548f1e922ee584e9dd6c8fcf8c081 --- /dev/null +++ b/marked/Rel-18/38_series/38161/c925eb337128296a214c69e40455be77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58df88247046831f12d0c2f8c771c9cf4067c1f1eb1d27e45ef6fe0a2d0e948f +size 23877 diff --git a/marked/Rel-18/38_series/38161/ceb48bd7cc8cbb0fa401b366532bbdb0_img.jpg b/marked/Rel-18/38_series/38161/ceb48bd7cc8cbb0fa401b366532bbdb0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e5bb31ef2973f50b7fc0a9f77d5783e09cbdad0 --- /dev/null +++ b/marked/Rel-18/38_series/38161/ceb48bd7cc8cbb0fa401b366532bbdb0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:377a5ebea5d8dac57e6f9d89c053cfd43da3b301c74cc3e745c91bf300bce66b +size 33876 diff --git a/marked/Rel-18/38_series/38161/d778f25f203fa5a385e9f6458f655763_img.jpg b/marked/Rel-18/38_series/38161/d778f25f203fa5a385e9f6458f655763_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8044a6513ab6fb78ae42c1c62de07f80541e4b88 --- /dev/null +++ b/marked/Rel-18/38_series/38161/d778f25f203fa5a385e9f6458f655763_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a29dfa4f65a42543c16611eda926e7b334af0523249500af47d3f2ca474f232a +size 9968 diff --git a/marked/Rel-18/38_series/38161/raw.md b/marked/Rel-18/38_series/38161/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a97bbc41739e1df349aeb2cf3fe57134a4a43443 --- /dev/null +++ b/marked/Rel-18/38_series/38161/raw.md @@ -0,0 +1,1702 @@ + + +# 3GPP TS 38.161 V18.0.0 (2023-12) + +*Technical Specification* + +**3rd Generation Partnership Project; +Technical Specification Group Radio Access Network; +NR; +User Equipment (UE) TRP (Total Radiated Power) and TRS +(Total Radiated Sensitivity) requirements; +Range 1 Standalone and Range 1 Interworking operation with +other radios +(Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' underneath. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +# **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +# --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|---------------------------------------------------------------------------|-----------| +| Foreword ..... | 7 | +| 1 Scope..... | 9 | +| 2 References..... | 9 | +| 3 Definitions of terms, symbols and abbreviations..... | 10 | +| 3.1 Terms..... | 10 | +| 3.2 Symbols..... | 10 | +| 3.3 Abbreviations ..... | 10 | +| 4 General..... | 11 | +| 4.1 Relationship between minimum requirements and test requirements..... | 11 | +| 4.2 Applicability of minimum requirements ..... | 11 | +| 4.2.1 General ..... | 11 | +| 4.2.1.1 UE mechanical modes ..... | 11 | +| 4.3 Applicability rules for testing of FR1 SA and NSA UEs..... | 11 | +| 4.4 Applicability rules for testing of power class capability of UEs..... | 11 | +| 5 Frequency bands ..... | 12 | +| 5.1 General ..... | 12 | +| 5.2 Operating bands..... | 12 | +| 5.2.1 FR1 Standalone Operating bands ..... | 12 | +| 5.2.2 FR1 EN-DC band combinations ..... | 13 | +| 5.3 Test parameters for each band..... | 15 | +| 6 FR1 TRP requirements..... | 21 | +| 6.1 General ..... | 21 | +| 6.2 Minimum requirement..... | 21 | +| 6.2.1 Minimum requirement for handheld UE ..... | 21 | +| 6.2.1.1 Hand phantom browsing mode ..... | 22 | +| 6.2.1.1.1 NR FR1 ..... | 22 | +| 6.2.1.1.2 NR FR1 in EN-DC mode ..... | 22 | +| 6.2.1.2 Beside the head and hand phantom talk mode..... | 23 | +| 6.2.1.2.1 NR FR1 ..... | 23 | +| 6.2.1.2.2 NR FR1 in EN-DC mode ..... | 23 | +| 7 FR1 TRS requirements..... | 24 | +| 7.1 General ..... | 24 | +| 7.2 Minimum requirement..... | 24 | +| 7.2.1 Minimum requirement for handheld UE ..... | 24 | +| 7.2.1.1 Hand phantom browsing mode ..... | 24 | +| 7.2.1.1.1 NR FR1 ..... | 24 | +| 7.2.1.1.2 NR FR1 in EN-DC mode ..... | 25 | +| 7.2.1.2 Beside the head and hand phantom position..... | 25 | +| 7.2.1.2.1 NR FR1 ..... | 25 | +| 7.2.1.2.2 NR FR1 in EN-DC mode ..... | 25 | +| Annex A (normative): Test methodology ..... | 27 | +| A.1 General..... | 27 | +| A.2 UE configuration..... | 27 | +| A.2.1 General ..... | 27 | +| A.2.2 UE configuration for TRP test ..... | 27 | +| A.2.3 UE configuration for TRS test ..... | 27 | +| A.3 Test system of Anechoic Chamber method ..... | 28 | +| A.3.1 System setup..... | 28 | +| A.3.2 Calibration procedure..... | 28 | +| A.3.3 Test procedure ..... | 29 | + +| | | | +|-----------------------------------------------------------------------|---------------------------------------------------------------|-----------| +| A.3.3.1 | General ..... | 29 | +| A.3.3.2 | TRP Test procedure..... | 29 | +| A.3.3.3 | TRS Test procedure..... | 30 | +| A.3.4 | Minimum Range Length ..... | 30 | +| A.3.5 | Definition of TRP and TRS for AC ..... | 32 | +| A.3.5.1 | Total Radiated Power (TRP) ..... | 32 | +| A.3.5.2 | Total Radiated Sensitivity (TRS) ..... | 32 | +| A.4 | Preliminary example MU budget..... | 34 | +| Annex B (normative): Phantoms definition and Positioning ..... | | 45 | +| B.1 | General ..... | 45 | +| B.2 | Phantom Definition ..... | 45 | +| B.2.1 | Head Phantom ..... | 45 | +| B.2.2 | PDA Grip Hand Phantom..... | 45 | +| B.2.3 | Wide Grip Hand Phantom ..... | 45 | +| B.2.4 | Forearm Phantom ..... | 46 | +| B.3 | UE positioning guidelines..... | 46 | +| B.3.1 | Hand phantom only (Browsing mode)..... | 46 | +| B.3.1.1 | Wide Grip Hand ..... | 47 | +| B.3.1.2 | PDA Grip Hand ..... | 47 | +| B.3.2 | Head and Hand phantom (Talk Mode)..... | 49 | +| B.3.2.1 | General ..... | 49 | +| B.3.2.2 | Wide Grip Hand and Head ..... | 50 | +| B.3.2.1 | PDA Grip Hand and Head..... | 50 | +| B.3.3 | Forearm phantom (Wrist-worn Mode)..... | 50 | +| B.3.2.1 | General ..... | 50 | +| B.3.2.2 | Forearm phantom positioning in the chamber..... | 50 | +| B.3.2.3 | Wrist-Worn RedCap Device mounted on the Forearm Phantom ..... | 51 | +| Annex C (normative): Environmental requirements..... | | 53 | +| C.1 | General..... | 53 | +| C.2 | Environmental..... | 53 | +| C.2.1 | Temperature ..... | 53 | +| C.2.2 | Voltage ..... | 53 | +| Annex D (informative): Change history..... | | 54 | + +# 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 TRP (Total Radiated Power) and TRS (Total Radiated Sensitivity) requirements for NR UEs operating on Range 1 Standalone and Range 1 Interworking operation with other radios. + +# --- 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.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". +- [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 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". +- [9] 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: +- [10] CTIA Certification™: "CTIA Certification Test Plan for Wireless Device Over-the-Air Performance, CTIA 01.72: Near-Field Phantoms", 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: + +| | | +|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $TRP_{average}$ | The average measured total radiated power of low, mid and high channel. When hand phantom is involved, the average is performed with low, mid and high channel from both hand left and hand right. | +| $TRS_{average}$ | The average measured total radiated sensitivity of low, mid and high channel. When hand phantom is involved, the average is performed with low, mid and high channel from both hand left and hand right. | + +## 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 Relationship between minimum requirements and test requirements + +The Minimum Requirements given in this specification make no allowance for measurement uncertainty. The test specification in RAN5 will define final test tolerances for FR1 TRP TRS. The test tolerances are used to relax the minimum requirements in this specification to create test requirements. + +## 4.2 Applicability of minimum requirements + +### 4.2.1 General + +The minimum requirements apply only to the corresponding primary mechanical mode of UE in the environmental conditions specified in Annex C.4.2.2. + +### 4.2.1 UE mechanical modes + +The mechanical modes of a device under test (DUT) are declared by the manufacturer. A DUT shall have at least one mechanical mode. If only one mode is supported, then this is defined as the primary. 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 Applicability rules for testing of FR1 SA and NSA UEs + +The applicability and test coverage rules for Non-Standalone (NSA) only capable devices shall include the following: + +- For each NR band supported by the device, test the UE in EN-DC mode using any one example configuration containing that NR band or configuration declaration decision tree as per recommended TRP/TRS test procedures in this specification. + +The applicability and test coverage rules for Standalone (SA) and NSA (EN-DC) capable devices shall include the following: + +- For each NR band in a device, test the UE in Standalone Mode as per the TRP/TRS test procedures in this specification. +- This shall also fulfil coverage for all EN-DC FR1 minimum performance requirements for that NR band and need not be retested in EN-DC mode. + +## 4.4 Applicability rules for testing of power class capability of UEs + +The applicability and test coverage rules for PC2 and PC3 UEs shall include the following: + +- For UEs that support PC2 in a given band: verify the requirement only with PC2 configuration +- For UEs that only support PC3 in a given band: verify the requirement with PC3 configuration + +NOTE 1: The test procedure and requirements in this version of the specification apply only for handheld UEs based on 1 Tx configuration and are not applicable to UEs under TxD and UL MIMO configurations. + +# 5 Frequency bands + +## 5.1 General + +The requirements defined in this specification for NR apply to the frequency bands defined in Clause 5.2. + +## 5.2 Operating bands + +### 5.2.1 FR1 Standalone Operating bands + +The requirements defined in this specification for FR1 standalone apply to the operating bands defined in Table 5.2.1-1. + +**Table 5.2.1-1 NR operating bands in FR1 standalone** + +| 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 | +| n2 | 1850 MHz – 1910 MHz | 1930 MHz – 1990 MHz | FDD | +| n3 | 1710 MHz – 1785 MHz | 1805 MHz – 1880 MHz | FDD | +| n5 | 824 MHz – 849 MHz | 869 MHz – 894 MHz | FDD | +| n7 | 2500 MHz – 2570 MHz | 2620 MHz – 2690 MHz | FDD | +| n8 | 880 MHz – 915 MHz | 925 MHz – 960 MHz | FDD | +| n12 | 699 MHz – 716 MHz | 729 MHz – 746 MHz | FDD | +| n14 | 788 MHz – 798 MHz | 758 MHz – 768 MHz | FDD | +| n20 | 832 MHz – 862 MHz | 791 MHz – 821 MHz | FDD | +| n25 | 1850 MHz – 1915 MHz | 1930 MHz – 1995 MHz | FDD | +| n26 | 814 MHz – 849 MHz | 859 MHz – 894 MHz | FDD | +| n28 | 703 MHz – 748 MHz | 758 MHz – 803 MHz | FDD | +| n30 | 2305 MHz – 2315 MHz | 2350 MHz – 2360 MHz | FDD | +| n34 | 2010 MHz – 2025 MHz | 2010 MHz – 2025 MHz | TDD | +| n38 | 2570 MHz – 2620 MHz | 2570 MHz – 2620 MHz | TDD | +| n39 | 1880 MHz – 1920 MHz | 1880 MHz – 1920 MHz | TDD | +| n40 | 2300 MHz – 2400 MHz | 2300 MHz – 2400 MHz | TDD | +| n41 | 2496 MHz – 2690 MHz | 2496 MHz – 2690 MHz | TDD | +| n48 | 3550 MHz – 3700 MHz | 3550 MHz – 3700 MHz | TDD | +| n50 | 1432 MHz – 1517 MHz | 1432 MHz – 1517 MHz | TDD 1 | +| n51 | 1427 MHz – 1432 MHz | 1427 MHz – 1432 MHz | TDD | +| n53 | 2483.5 MHz – 2495 MHz | 2483.5 MHz – 2495 MHz | TDD | +| n65 | 1920 MHz – 2010 MHz | 2110 MHz – 2200 MHz | FDD 4 | +| n66 | 1710 MHz – 1780 MHz | 2110 MHz – 2200 MHz | FDD | +| n70 | 1695 MHz – 1710 MHz | 1995 MHz – 2020 MHz | FDD | +| n71 | 663 MHz – 698 MHz | 617 MHz – 652 MHz | FDD | +| n74 | 1427 MHz – 1470 MHz | 1475 MHz – 1518 MHz | FDD | +| n75 | N/A | 1432 MHz – 1517 MHz | SDL | +| n76 | N/A | 1427 MHz – 1432 MHz | SDL | +| n77 12 | 3300 MHz – 4200 MHz | 3300 MHz – 4200 MHz | TDD | +| n78 | 3300 MHz – 3800 MHz | 3300 MHz – 3800 MHz | TDD | +| n79 | 4400 MHz – 5000 MHz | 4400 MHz – 5000 MHz | TDD | +| n80 | 1710 MHz – 1785 MHz | N/A | SUL | +| n81 | 880 MHz – 915 MHz | N/A | SUL | +| n82 | 832 MHz – 862 MHz | N/A | SUL | +| n83 | 703 MHz – 748 MHz | N/A | SUL | +| n84 | 1920 MHz – 1980 MHz | N/A | SUL | +| n86 | 1710 MHz – 1780 MHz | N/A | SUL | +| n95 | 2010 MHz – 2025 MHz | N/A | SUL | + +Other operating bands may be considered in future releases. + +### 5.2.2 FR1 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 5.2.2-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 [8], Clause 5.3 and 5.4 (Measurement frequencies for E-UTRA FDD and TDD). | | +| Note 2: | As per Table 5.3-1 and Table 5.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. The process starts with a loop for each NR band. It checks if the UE supports the band, if requirements were met in SA mode, and if an example EN-DC band combination exists. If not, it proceeds to select a candidate combination by picking the NR band and then finding the closest supported LTE band. It then checks if the configuration meets criteria or if more band combinations are possible.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +``` + +graph TD + Start([1. For each NR band that has TRP/TRS requirements specified in TS38.161:]) --> D1{Does the UE support the band?} + D1 -- No --> N1([Continue to the next band]) + D1 -- Yes --> D2{Has the requirement been fulfilled by testing the UE in SA mode?} + D2 -- Yes --> N2([Requirement need not be retested in EN-DC mode; continue to the next band]) + D2 -- No --> D3{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?} + D3 -- Yes --> S2([2. Configure the UE according to the example band combination and perform the test in EN-DC mode]) + D3 -- No --> S3([3. Select an EN-DC band combination candidate as follows:]) + S3 --> S4[For the NR carrier: select the NR band under test from step #1] + S4 --> S5[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] + S5 --> D4{Does the resulting EN-DC configuration fulfill the criteria defined in TS38.161, Clause 5.2.2?} + D4 -- Yes --> S6([5. Configure the UE according to the chosen band combination and perform the test in EN-DC mode]) + D4 -- No --> D5{Does the UE support more LTE bands in combination with the selected NR band?} + D5 -- Yes --> S7[Select the next-closest LTE band] + S7 --> S5 + D5 -- No --> S8([4. Configure the UE according to any band combination which includes the selected NR band and which is self-declared by the OEM]) + +``` + +Flowchart for selecting EN-DC band combination for TRP/TRS testing. The process starts with a loop for each NR band. It checks if the UE supports the band, if requirements were met in SA mode, and if an example EN-DC band combination exists. If not, it proceeds to select a candidate combination by picking the NR band and then finding the closest supported LTE band. It then checks if the configuration meets criteria or if more band combinations are possible. + +Figure 5.2.2-1: Decision tree to select the EN-DC band combination for TRP/TRS testing + +## 5.3 Test parameters for each band + +The detailed testing parameters for each band is defined in Table 5.3-1 and Table 5.3-2. + +**Table 5.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 | | Low | 509202 | 2546.01 | 509202 | 2546.01 | 135@67 | N/A | + +| | | | | | | | | | | | +|-----|---------------|----|-----------------|------|--------|---------|--------|---------|--------|-----| +| | | | DFT-s-OFDM QPSK | Mid | 518598 | 2592.99 | 518598 | 2592.99 | | | +| | | | | High | 528000 | 2640 | 528000 | 2640 | | | +| n48 | 20 | 15 | DFT-s-OFDM QPSK | Low | 637334 | 3560.01 | 637334 | 3560.01 | 50@25 | N/A | +| | | | | Mid | 641666 | 3624.99 | 641666 | 3624.99 | | | +| | | | | 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 5.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 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 509202 | 2546.01 | 509202 | 2546.01 | 270@0 | 273@0 | +| | | | | | Mid | 518598 | 2592.99 | 518598 | 2592.99 | | | +| | | | | | 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 | | | Low | 288400 | 1442 | 288400 | 1442 | 100@0 | 106@0 | + +| | | | | | | | | | | | | +|------------|----------------|----|--------------|-----------------|------|--------|---------|--------|---------|-------|-------| +| | | | CP-OFDM QPSK | DFT-s-OFDM QPSK | 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 5.3-3 and Table 5.3-4. + +**Table 5.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 | | Low | 177500 | 887.5 | 186500 | 932.5 | 36@18 | N/A | + +| | | | | | | | | | | | +|-----|----|----|-----------------|------|--------|----------|--------|----------|-------|-----| +| | | | DFT-s-OFDM QPSK | 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 | 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 | 15 | 15 | DFT-s-OFDM QPSK | Low | 620500 | 3307.5 | 620500 | 3307.5 | 36@18 | N/A | +| | | | | Mid | 650000 | 3750 | 650000 | 3750 | | | +| | | | | High | 679500 | 4192.5 | 679500 | 4192.5 | | | +| n78 | 15 | 15 | DFT-s-OFDM | Low | 620500 | 3307.5 | 620500 | 3307.5 | 36@18 | N/A | +| | | | | Mid | 636666 | 3549.99 | 636666 | 3549.99 | | | + +| | | | | | | | | | | | +|-----|----|----|------------|------|--------|----------|--------|----------|-------|-----| +| n79 | 20 | 15 | QPSK | High | 652832 | 3792.48 | 652832 | 3792.48 | 50@25 | N/A | +| | | | DFT-s-OFDM | Low | 694000 | 4410 | 694000 | 4410 | | | +| | | | QPSK | Mid | 713333 | 4699.995 | 713333 | 4699.995 | | | +| | | | | High | 732667 | 4990.005 | 732667 | 4990.005 | | | + +Table 5.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 on (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 | | | Low | 500700 | 2503.5 | 500700 | 2503.5 | 75@0 | 79@0 | + +| | | | | | | | | | | | | +|-----|----|----|--------------|-----------------|------|--------|----------|--------|----------|-------|-------| +| | | | CP-OFDM QPSK | DFT-s-OFDM QPSK | 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 | | | + +# 6 FR1 TRP requirements + +## 6.1 General + +The TRP requirements specified in Clause 6 apply to handheld UE with TAS off and power back-off functions disabled. + +The TRP requirements defined in Clause 6.2 should be verified based on the detailed test parameters in Table 5.3-1. + +## 6.2 Minimum requirement + +### 6.2.1 Minimum requirement for handheld UE + +The average measured total radiated power (TRP) of low, mid and high channel for handheld UE shall be higher than the average TRP requirement specified in subclauses 6.2.1.1 and 6.2.1.2. The averaging shall be done in linear scale for the TRP results of both right and left side of the phantom head in case of beside the head and hand phantom positions. For the hand phantom browsing mode position the averaging shall be done in linear scale for the TRP results of both right and left hand phantom measurements. + +$$TRP_{average} = 10 \log \left[ \frac{10^{P_{left\_tow}/10} + 10^{P_{left\_mid}/10} + 10^{P_{left\_high}/10} + 10^{P_{right\_tow}/10} + 10^{P_{right\_mid}/10} + 10^{P_{right\_high}/10}}{6} \right]$$ + +For UEs which do not support NR FR1 in stand-alone mode, EN-DC mode requirements apply. SA and EN-DC test case applicability is defined in Clause 4.3, and test case applicability based on power class capability is defined in Clause 4.4. The relevant test methodology is defined in Annexes A and B of this specification. + +#### 6.2.1.1 Hand phantom browsing mode + +Hand phantom browsing mode positions are defined in Clause B.3.1. + +##### 6.2.1.1.1 NR FR1 + +Handheld UE TRP minimum performance requirement for NR FR1 bands in the hand phantom browsing position and the primary mechanical mode are defined in Tables 6.2.1.1.1-1 and 6.2.1.1.1-2. + +**Table 6.2.1.1.1-1: Handheld PC3 UE TRP minimum performance requirement for NR FR1 bands in the hand phantom browsing position and the primary mechanical mode** + +| NR Band | Bandwidth (MHz) | Usage Scenario | Power Class 3 | | +|---------|-----------------|----------------|-------------------|-----------------| +| | | | Average TRP (dBm) | | +| | | | UE width ≤ 72mm | UE width > 72mm | +| n28 | 20 | HL and HR | | | +| n41 | 100 | HL and HR | | | +| n78 | 100 | HL and HR | | | +| n79 | 100 | HL and HR | | | + +**Table 6.2.1.1.2: Handheld PC2 UE TRP minimum performance requirement for NR FR1 bands in the hand phantom browsing position and the primary mechanical mode** + +| NR Band | Bandwidth (MHz) | Usage Scenario | Power Class 2 | | +|---------|-----------------|----------------|-------------------|-----------------| +| | | | Average TRP (dBm) | | +| | | | UE width ≤ 72mm | UE width > 72mm | +| n28 | 20 | HL and HR | | | +| n41 | 100 | HL and HR | | 12.5 | +| n78 | 100 | HL and HR | | 13 | +| n79 | 100 | HL and HR | | | + +##### 6.2.1.1.2 NR FR1 in EN-DC mode + +Handheld UE TRP minimum performance requirement for NR FR1 bands (in EN-DC mode) in the hand phantom browsing position and the primary mechanical mode are defined in Tables 6.2.1.1.2-1 and 6.2.1.1.2-2. + +**Table 6.2.1.1.2-1: Handheld PC3 UE TRP minimum performance requirement for NR FR1 bands (in EN-DC mode) in the hand phantom browsing position and the primary mechanical mode** + +| NR Band | Bandwidth (MHz) | Usage Scenario | Power Class 3 | | +|---------|-----------------|----------------|-------------------|-----------------| +| | | | Average TRP (dBm) | | +| | | | UE width ≤ 72mm | UE width > 72mm | +| n28 | 20 | HL and HR | | | +| n41 | 100 | HL and HR | | | +| n78 | 100 | HL and HR | | | +| n79 | 100 | HL and HR | | | + +**Table 6.2.1.1.2-2: Handheld PC2 UE TRP minimum performance requirement for NR FR1 bands (in EN-DC mode) in the hand phantom browsing position and the primary mechanical mode** + +| NR Band | Bandwidth (MHz) | Usage Scenario | Power Class 2 | | +|---------|-----------------|----------------|-------------------|-----------------| +| | | | Average TRP (dBm) | | +| | | | UE width ≤ 72mm | UE width > 72mm | +| n28 | 20 | HL and HR | | | +| n41 | 100 | HL and HR | | | +| n78 | 100 | HL and HR | | | +| n79 | 100 | HL and HR | | | + +#### 6.2.1.2 Beside the head and hand phantom talk mode + +Beside the head and hand phantom mode positions are defined in Clause B.3.2 of this specification. + +##### 6.2.1.2.1 NR FR1 + +Handheld UE TRP minimum performance requirement for NR FR1 bands in the beside head and hand phantom talk position and the primary mechanical mode are defined in Tables 6.2.1.2.1-1 and 6.2.1.2.1-2. + +**Table 6.2.1.2.1-1: Handheld PC3 UE TRP minimum performance requirement for NR FR1 bands in the beside head and hand phantom talk position and the primary mechanical mode** + +| NR Band | Bandwidth (MHz) | Usage Scenario | Power Class 3 | | +|---------|-----------------|----------------|-------------------|-----------------| +| | | | Average TRP (dBm) | | +| | | | UE width ≤ 72mm | UE width > 72mm | +| n28 | 20 | BHHL and BHHR | | | +| n41 | 100 | BHHL and BHHR | | | +| n78 | 100 | BHHL and BHHR | | | +| n79 | 100 | BHHL and BHHR | | | + +**Table 6.2.1.2.1-2: Handheld PC2 UE TRP minimum performance requirement for NR FR1 bands in the beside head and hand phantom talk position and the primary mechanical mode** + +| NR Band | Bandwidth (MHz) | Usage Scenario | Power Class 2 | | +|---------|-----------------|----------------|-------------------|-----------------| +| | | | Average TRP (dBm) | | +| | | | UE width ≤ 72mm | UE width > 72mm | +| n28 | 20 | BHHL and BHHR | | | +| n41 | 100 | BHHL and BHHR | | | +| n78 | 100 | BHHL and BHHR | | | +| n79 | 100 | BHHL and BHHR | | | + +##### 6.2.1.2.2 NR FR1 in EN-DC mode + +Handheld UE TRP minimum performance requirement for NR FR1 bands (in EN-DC mode) in the beside head and hand phantom talk position and the primary mechanical mode are defined in Tables 6.2.1.2.2-1 and 6.2.1.2.2-2. + +**Table 6.2.1.2.2-1: Handheld PC3 UE TRP minimum performance requirement for NR FR1 bands (in EN-DC mode) in the beside head and hand phantom talk position and the primary mechanical mode** + +| NR Band | Bandwidth (MHz) | Usage Scenario | Power Class 3 | | +|---------|-----------------|----------------|-------------------|-----------------| +| | | | Average TRP (dBm) | | +| | | | UE width ≤ 72mm | UE width > 72mm | +| n28 | 20 | BHHL and BHHR | | | +| n41 | 100 | BHHL and BHHR | | | +| n78 | 100 | BHHL and BHHR | | | +| n79 | 100 | BHHL and BHHR | | | + +**Table 6.2.1.2.2-2: Handheld PC2 UE TRP minimum performance requirement for NR FR1 bands (in EN-DC mode) in the beside head and hand phantom talk position and the primary mechanical mode** + +| NR Band | Bandwidth (MHz) | Usage Scenario | Power Class 2 | | +|---------|-----------------|----------------|-------------------|-----------------| +| | | | Average TRP (dBm) | | +| | | | UE width ≤ 72mm | UE width > 72mm | +| n28 | 20 | BHHL and BHHR | | | +| n41 | 100 | BHHL and BHHR | | | +| n78 | 100 | BHHL and BHHR | | | +| n79 | 100 | BHHL and BHHR | | | + +# 7 FR1 TRS requirements + +## 7.1 General + +The TRS requirements specified in Clause 7 apply to handheld UE configured with maximum number of Rx antennas supported for each band, which is specified in TS 38.101-1 Clause 7.3 [3]. + +The TRS requirements defined in Clause 7.2 should be verified based on the detailed test parameters in Table 5.3-2. + +## 7.2 Minimum requirement + +### 7.2.1 Minimum requirement for handheld UE + +The average measured total radiated sensitivity (TRS) of low, mid and high channel for handheld UE shall be lower than the average TRS requirement specified in subclauses 7.2.1.1 and 7.2.1.2. The averaging shall be done in linear scale for the TRS results of both right and left side of the phantom head in case of beside the head and hand phantom positions. For the hand phantom browsing mode position the averaging shall be done in linear scale for the TRP results of both right and left hand phantom measurements. + +$$TRS_{average} = 10 \log \left[ 6 / \left( \frac{1}{10^{\frac{P_{left\_low}}{10}}} + \frac{1}{10^{\frac{P_{left\_mid}}{10}}} + \frac{1}{10^{\frac{P_{left\_high}}{10}}} + \frac{1}{10^{\frac{P_{right\_low}}{10}}} + \frac{1}{10^{\frac{P_{right\_mid}}{10}}} + \frac{1}{10^{\frac{P_{right\_high}}{10}}} \right) \right]$$ + +For UEs which do not support NR FR1 in stand-alone mode, EN-DC mode requirements apply. SA and EN-DC test case applicability is defined in Clause 4.3, and test case applicability based on power class capability is defined in Clause 4.4. The relevant test methodology is defined in Annexes A and B of this specification. + +#### 7.2.1.1 Hand phantom browsing mode + +Hand phantom browsing mode positions are defined in Clause B.3.1. + +##### 7.2.1.1.1 NR FR1 + +Handheld UE TRS minimum performance requirement for NR FR1 bands in the hand phantom browsing position and the primary mechanical mode are defined in Tables 7.2.1.1.1-1 and 7.2.1.1.1-2. + +**Table 7.2.1.1.1-1: Handheld PC3 and PC2 UE TRS minimum performance requirement for NR FR1 bands in the hand phantom browsing position and the primary mechanical mode** + +| NR Band | Bandwidth (MHz) | Usage Scenario | Power Class 3 and Power Class 2 | | +|---------|-----------------|----------------|---------------------------------|-----------------| +| | | | Average TRS (dBm) | | +| | | | UE width ≤ 72mm | UE width > 72mm | +| n28 | 20 | HL and HR | | | +| n41 | 100 | HL and HR | | -80 | +| n78 | 100 | HL and HR | | -81.2 | +| n79 | 100 | HL and HR | | | + +##### 7.2.1.1.2 NR FR1 in EN-DC mode + +Handheld UE TRS minimum performance requirement for NR FR1 bands (in EN-DC mode) in the hand phantom browsing position and the primary mechanical mode are defined in Tables 6.2.1.1.2-1 and 6.2.1.1.2-2. + +**Table 7.2.1.1.2-1: Handheld PC3 and PC2 UE TRS minimum performance requirement for NR FR1 bands (in EN-DC mode) in the hand phantom browsing position and the primary mechanical mode** + +| NR Band | Bandwidth (MHz) | Usage Scenario | Power Class 3 and Power Class 2 | | +|---------|-----------------|----------------|---------------------------------|-----------------| +| | | | Average TRS (dBm) | | +| | | | UE width ≤ 72mm | UE width > 72mm | +| n28 | 20 | HL and HR | | | +| n41 | 100 | HL and HR | | | +| n78 | 100 | HL and HR | | | +| n79 | 100 | HL and HR | | | + +#### 7.2.1.2 Beside the head and hand phantom position + +Beside the head and hand phantom mode positions are defined in Clause B.3.2. + +##### 7.2.1.2.1 NR FR1 + +Handheld UE TRP minimum performance requirement for NR FR1 bands in the beside head and hand phantom position and the primary mechanical mode are defined in Tables 7.2.1.2.1-1 and 7.2.1.2.1-2. + +**Table 7.2.1.2.1-1: Handheld PC3 and PC2 UE TRS minimum performance requirement for NR FR1 bands in the beside head and hand phantom position and the primary mechanical mode** + +| NR Band | Bandwidth (MHz) | Usage Scenario | Power Class 3 and Power Class 2 | | +|---------|-----------------|----------------|---------------------------------|-----------------| +| | | | Average TRS (dBm) | | +| | | | UE width ≤ 72mm | UE width > 72mm | +| n28 | 20 | BHHL and BHHR | | | +| n41 | 100 | BHHL and BHHR | | | +| n78 | 100 | BHHL and BHHR | | | +| n79 | 100 | BHHL and BHHR | | | + +##### 7.2.1.2.2 NR FR1 in EN-DC mode + +Handheld UE TRS minimum performance requirement for NR FR1 bands (in EN-DC mode) in the beside head and hand phantom position and the primary mechanical mode are defined in Tables 6.2.1.2.2-1 and 6.2.1.2.2-2. + +**Table 7.2.1.2.2-1: Handheld PC3 and PC2 UE TRS minimum performance requirement for NR FR1 bands (in EN-DC mode) in the beside head and hand phantom position and the primary mechanical mode** + +| NR Band | Bandwidth (MHz) | Usage Scenario | Power Class 3 and Power Class 2 | | +|---------|-----------------|----------------|---------------------------------|-------------------| +| | | | Average TRS (dBm) | | +| | | | UE width $\leq$ 72mm | UE width $>$ 72mm | +| n28 | 20 | BHHL and BHHR | | | +| n41 | 100 | BHHL and BHHR | | | +| n78 | 100 | BHHL and BHHR | | | +| n79 | 100 | BHHL and BHHR | | | + +# --- Annex A (normative): Test methodology --- + +## A.1 General + +TRP TRS minimum requirement specified in Clause 6 and Clause 7 should be measured with Anechoic Chamber method. + +## --- A.2 UE configuration + +### A.2.1 General + +For FR1 TRP and TRS 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 TRP and TRS test. + +### A.2.2 UE configuration for TRP test + +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 5 Table 5.3-1. + +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 [7] as applicable. The measurement should be carried out based on the detailed test parameters for each band, as defined in Clause 5 Table 5.3-1. 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. + +### A.2.3 UE configuration for TRS test + +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. + +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 5 Table 5.3-2. + +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 [7], as applicable. The measurement should be carried out based on the detailed test parameters for each band, as defined in Clause 5 Table 5.3-2. 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. + +## A.3 Test system of Anechoic Chamber method + +### A.3.1 System setup + +For FR1 TRP TRS testing, both Single-antenna and multiple-antennas anechoic chambers can be applied. In Figure A.3.1-1, an example TRP TRS test system with combined axes system is presented. + +![Figure A.3.1-1: Example of a FR1 TRP TRS OTA test system with combined axis. The diagram shows a Device Under Test (DUT) mounted on a rotating turntable inside an anechoic chamber. A test antenna is positioned to receive signals from the DUT. The DUT is connected to a 'Link' box, which is connected to a 'Test Equipment (e.g. Communication Tester)'. The test antenna is connected to a 'Switch Unit', which is also connected to the 'Test Equipment'. A coordinate reference point (A) is marked on the DUT, an antenna connector (B) is shown on the test antenna, and a test equipment connector (C) is shown on the test equipment.](9b686adccf125267a013fa25721231a3_img.jpg) + +Figure A.3.1-1: Example of a FR1 TRP TRS OTA test system with combined axis. The diagram shows a Device Under Test (DUT) mounted on a rotating turntable inside an anechoic chamber. A test antenna is positioned to receive signals from the DUT. The DUT is connected to a 'Link' box, which is connected to a 'Test Equipment (e.g. Communication Tester)'. The test antenna is connected to a 'Switch Unit', which is also connected to the 'Test Equipment'. A coordinate reference point (A) is marked on the DUT, an antenna connector (B) is shown on the test antenna, and a test equipment connector (C) is shown on the test equipment. + +Figure A.3.1-1: Example of a FR1 TRP TRS OTA test system with combined axis + +In Figure A.3.1-2, an example TRP TRS test system with distributed axes system is presented. + +![Figure A.3.1-2: Example of a FR1 TRP TRS OTA test system with distributed axis. The diagram shows a DUT mounted on a rotating turntable inside an anechoic chamber. A 'Test Antenna' is positioned to receive signals from the DUT, and a 'Link Antenna' is positioned to transmit signals to the DUT. The DUT is connected to a 'Link' box, which is connected to a 'Test Equipment (e.g. Communication Tester)'. The 'Test Antenna' is connected to a 'Switch Unit', which is also connected to the 'Test Equipment'. The 'Link Antenna' is also connected to the 'Test Equipment'. A coordinate reference point (A) is marked on the DUT, an antenna connector (B) is shown on the test antenna, and a test equipment connector (C) is shown on the test equipment.](ceb48bd7cc8cbb0fa401b366532bbdb0_img.jpg) + +Figure A.3.1-2: Example of a FR1 TRP TRS OTA test system with distributed axis. The diagram shows a DUT mounted on a rotating turntable inside an anechoic chamber. A 'Test Antenna' is positioned to receive signals from the DUT, and a 'Link Antenna' is positioned to transmit signals to the DUT. The DUT is connected to a 'Link' box, which is connected to a 'Test Equipment (e.g. Communication Tester)'. The 'Test Antenna' is connected to a 'Switch Unit', which is also connected to the 'Test Equipment'. The 'Link Antenna' is also connected to the 'Test Equipment'. A coordinate reference point (A) is marked on the DUT, an antenna connector (B) is shown on the test antenna, and a test equipment connector (C) is shown on the test equipment. + +Figure A.3.1-2: Example of a FR1 TRP TRS OTA test system with distributed axis + +### A.3.2 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 A.3.2-1: Example FR1 TRP TRS calibration setup. The diagram shows a calibration setup inside a shielded enclosure. A reference antenna (B) is connected to a Network Analyzer (C) via a cable (D). A measurement antenna (A) is connected to a Switch Unit (E) via a cable (D). The Network Analyzer is connected to the Switch Unit. The legend identifies: A: Coordinate reference point; B: Antenna connector; C: Network Analyzer connector; D: Reference antenna connector; E: Network analyzer connector.](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +Figure A.3.2-1: Example FR1 TRP TRS calibration setup. The diagram shows a calibration setup inside a shielded enclosure. A reference antenna (B) is connected to a Network Analyzer (C) via a cable (D). A measurement antenna (A) is connected to a Switch Unit (E) via a cable (D). The Network Analyzer is connected to the Switch Unit. The legend identifies: A: Coordinate reference point; B: Antenna connector; C: Network Analyzer connector; D: Reference antenna connector; E: Network analyzer connector. + +**Figure A.3.2-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 A.2.2-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. + +### A.3.3 Test procedure + +#### A.3.3.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. + +#### A.3.3.2 TRP Test procedure + +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, e.g., 15 degrees or 30 degrees, in both theta ( $\theta$ ) and phi ( $\phi$ ) axes for TRP measurement. 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 A.3.5.1. + +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 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 A.3.5.1. + +This TRP test procedure is common to both SA and EN-DC measurements. The detailed UE configurations for TRP test in SA and EN-DC mode are specified in Clause A.2. + +#### A.3.3.3 TRS Test procedure + +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, e.g., 30 degrees or 45 degree 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. + +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 and integration approaches outlined in Clause A.3.5.2. + +This TRS test procedure is common to both SA and EN-DC measurements. The detailed UE configurations for TRS test in SA and EN-DC mode are specified in Clause A.2. + +### A.3.4 Minimum Range Length + +This sub-section specifies the minimum range lengths for Anechoic-Chamber-based 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 A.3.4-1. + +![Figure A.3.4-1: Illustration of range length definition. The diagram shows a central shaded circle labeled 'Quiet Zone with 30cm diameter'. A larger dashed circle is centered on the shaded circle. An arrow labeled 'Range Length' points from the center of the shaded circle to the outer dashed circle. Another arrow points from the text 'Quiet Zone with 30cm diameter' to the inner shaded circle.](39ca823ef41ba00da416ecc099940770_img.jpg) + +Figure A.3.4-1: Illustration of range length definition. The diagram shows a central shaded circle labeled 'Quiet Zone with 30cm diameter'. A larger dashed circle is centered on the shaded circle. An arrow labeled 'Range Length' points from the center of the shaded circle to the outer dashed circle. Another arrow points from the text 'Quiet Zone with 30cm diameter' to the inner shaded circle. + +**Figure A.3.4-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 A.3.4-1 shall be considered the minimum range length for NR FR1 TRP-TRS OTA systems with 30cm quiet zone size. + +**Table A.3.4-1: Minimum Range Length for NR FR1 TRP-TRS OTA systems with 30cm quiet zone size.** + +| $F$ [GHz] | $D_{rad}$ [m] | $R_{QZ}+2D_{rad}^2/\lambda$ | $3D = 6R_{QZ}$ | $R_{QZ}+2\lambda$ | $\max(R_{QZ}+2\lambda, 3D, R_{QZ}+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 | + +### A.3.5 Definition of TRP and TRS for AC + +#### A.3.5.1 Total Radiated Power (TRP) + +This definition is used to calculate the Total Radiated Power (TRP) value. For Anechoic Chamber method, TRP 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$$ + +Where the effective isotropic radiated power (EIRP) is defined as + +$$EIRP(\theta, \phi) = P_T G_T(\theta, \phi)$$ + +Where $P_T G_T$ is the product of the power delivered to the antenna and the antenna's power gain, and $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$$ + +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)$$ + +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]$$ + +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 A.3.5.1-1. + +**Table A.3.5.1-1: Applicability for TRP measurement grids** + +| Frequency Range | Quadrature | $\Delta\theta=\Delta\phi [^\circ]$ | N | M | Min. Number of Grid Points | +|-----------------|-----------------|------------------------------------|----|----|----------------------------| +| FR1 | $\sin(\theta)$ | 15 | 12 | 24 | 266 | +| | | 30 | 6 | 12 | 62 | +| | Clenshaw-Curtis | 15 | 12 | 24 | 266 | +| | | 30 | 6 | 12 | 62 | + +#### A.3.5.2 Total Radiated Sensitivity (TRS) + +This definition is used to calculate the Total Radiated Sensitivity (TRS) value. For Anechoic Chamber method, the TRS with 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}$$ + +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, and $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}$$ + +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)}$$ + +Where the value of $W(\theta_n)$ can be calculated as follows (same equation as TRP): + +$$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]$$ + +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 TRS quadratures, frequency ranges, and measurement grids is tabulated in Table A.3.5.2-1. + +**Table A.3.5.2-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 | +| | Clenshaw-Curtis | 45 | 4 | 8 | 26 | +| > 3GHz | $\sin(\theta)$ | 30 | 6 | 12 | 62 | +| | Clenshaw-Curtis | 30 | 6 | 12 | 62 | +| | Clenshaw-Curtis | 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$ ) + +## A.4 Preliminary example MU budget + +### A.4.1 General + +### A.4.2 Test system of Anechoic Chamber method + +The uncertainty contributions related to TRP are described in Annex B in [2]. The preliminary example uncertainty budget for TRP test case using Anechoic Chamber test system is presented in Table A.4.2-1 for Browsing mode and Table A.4.2-2 for Talk mode, respectively. + +**Table A.4.2-1 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 | c i | 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.11 | Actual | 1 | 1 | 0.00 | 0.11 | +| 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.89] | +| Expanded uncertainty [dB] (Confidence interval of 95 %) | | | | | | | | [1.64] | [1.75] | +| 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.75] | + +**Table A.4.2-2 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 $> 3\text{dB}$ | 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.6\text{m}$ ,
$\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 Table B.2.12-1 | 0 | 0.11 | Actual | 1 | 1 | 0.00 | 0.11 | +| 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.87] | [1.97] | +| 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.87] | [1.97] | + +The uncertainty contributions related to TRS are described in Annex B in [2]. A preliminary example uncertainty budget TRS test cases using Anechoic Chamber test system is presented in Table A.4.2-3 for Browsing mode and Table A.4.2-4 for Talk mode, respectively. + +**Table A.4.2-3: 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 $> 3\text{dB}$ | 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.16] | [1.16] | Normal | 2 | 1 | [0.58] | [0.58] | +| 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.04 | 0.25 | Actual | 1 | 1 | 0.04 | 0.25 | +| 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.00] | [1.06] | +| Expanded uncertainty [dB] (Confidence interval of 95 %) | | | | | | | | [1.97] | [2.08] | +| 22 | Systematic Error related to TRP grids | mean error | 0 | 0 | Actual | 1 | 1 | 0.00 | 0.08 | +| Total Expanded uncertainty [dB] (Confidence interval of 95 %) | | | | | | | | [1.97] | [2.16] | + +**Table A.4.2-4: 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 $> 3\text{dB}$ | 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.16] | [1.16] | Normal | 2 | 1 | [0.58] | [0.58] | +| 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), Data Mode Fixture | 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.04 | 0.25 | Actual | 1 | 1 | 0.04 | 0.25 | +| 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.11] | [1.16] | +| Expanded uncertainty [dB] (Confidence interval of 95 %) | | | | | | | | [2.17] | [2.27] | +| 22 | Systematic Error related to TRP grids | mean error | 0 | 0 | Actual | 1 | 1 | 0.00 | 0.08 | +| Total Expanded uncertainty [dB] (Confidence interval of 95 %) | | | | | | | | [2.17] | [2.35] | + +# Annex B (normative): Phantoms definition and Positioning + +## B.1 General + +This Clause defines the phantom definition and positioning guidance for TRP TRS requirement measurement. + +## B.2 Phantom Definition + +### B.2.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 [8]. For TRP TRS test, the IEEE SAM head model has been extended to the neck region, which is specified in CTIA Certification OTA Test Plan 01.72 [10]. + +The Head phantom defined in CTIA Certification OTA Test Plan 01.72, section 2.1 [10], is used for FR1 TRP TRS requirement testing. + +![Figure B.2.1-1: Three views of a head phantom. The left view shows the front of the head, which is blue with a white vertical stripe down the center. The middle view shows the head in profile, facing left, with a white vertical stripe on the side. The right view shows the back of the head, which is blue with a white vertical stripe down the center. The head is mounted on a yellow base.](c925eb337128296a214c69e40455be77_img.jpg) + +Figure B.2.1-1: Three views of a head phantom. The left view shows the front of the head, which is blue with a white vertical stripe down the center. The middle view shows the head in profile, facing left, with a white vertical stripe on the side. The right view shows the back of the head, which is blue with a white vertical stripe down the center. The head is mounted on a yellow base. + +**Figure B.2.1-1 Head Phantom (© 2001 – 2022 CTIA Certification. Reproduced with permission.), +defined in the CTIA Certification OTA Test Plan** + +### B.2.2 PDA Grip Hand Phantom + +The PDA Grip Hand described in TS 37.544 Annex A.2.2 [8], which is identical to that defined in CTIA Certification OTA Test Plan 01.72, section 2.2.12 [10], is adopted for TRP TRS testing for the UE with width $\geq 56\text{mm}$ and $\leq 72\text{mm}$ . + +### B.2.3 Wide Grip Hand Phantom + +The Wide Grip hand defined in CTIA Certification OTA Test Plan 01.72, section 2.2.13 [10], is used for FR1 TRP TRS testing for UE with width $> 72\text{mm}$ and $\leq 92\text{mm}$ . + +![Figure B.2.3-1: Two grey, anatomical hand phantoms, one left and one right, shown from a palm-up perspective. They are designed for testing mobile devices in a wide grip.](0e15b493e5acc6fa1d411bea5cae7164_img.jpg) + +Figure B.2.3-1: Two grey, anatomical hand phantoms, one left and one right, shown from a palm-up perspective. They are designed for testing mobile devices in a wide grip. + +Figure B.2.3-1 Wide Grip hand (© 2001 – 2022 CTIA Certification. Reproduced with permission.), defined in the CTIA Certification OTA Test Plan + +### B.2.4 Forearm Phantom + +The Forearm phantom defined in CTIA Certification OTA Test Plan 01.72 section 2.3 [10], is used for FR1 TRP TRS testing for wrist-worn RedCap UE in this technical report. + +![Figure B.2.4-1: A grey forearm phantom with a cylindrical top section and a conical bottom section. It has a vertical scale on its side. Labels indicate: 'Cylindrical Section (100 mm)' for the top part, 'Conical Section (215 mm)' for the bottom part, 'Target Test Position' pointing to a green circle, 'Cylindrical Perimeter: 144.0 mm' at the top, 'Test Position Perimeter: 162.7 mm' at the green circle, and 'Base Perimeter: 224.5 mm' at the bottom.](69350f1ebebf4e4b2d5644dfc6671d7c_img.jpg) + +Figure B.2.4-1: A grey forearm phantom with a cylindrical top section and a conical bottom section. It has a vertical scale on its side. Labels indicate: 'Cylindrical Section (100 mm)' for the top part, 'Conical Section (215 mm)' for the bottom part, 'Target Test Position' pointing to a green circle, 'Cylindrical Perimeter: 144.0 mm' at the top, 'Test Position Perimeter: 162.7 mm' at the green circle, and 'Base Perimeter: 224.5 mm' at the bottom. + +Figure B.2.4-1: Forearm Phantom with Target Test Position (© 2001 – 2022 CTIA Certification. Reproduced with permission.), defined in the CTIA Certification OTA Test Plan + +## B.3 UE positioning guidelines + +### B.3.1 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 Clause B.3.1. 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. The DUT should be set as + +primary mechanical mode for browsing mode scenario, which is declared by manufacturer if the UE support multiple mechanical modes. Then, 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}$ + +Note: the width is the UE width under primary mechanical mode for Browsing mode scenario. + +#### B.3.1.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 [9], is used for FR1 TRP TRS testing for UE with width $>72\text{mm}$ and $\leq 92\text{mm}$ . + +![Figure B.3.1.1-1: Positioning guidance for Wide Grip Hand. The image shows two views of a hand phantom holding a device (DUT). The left view shows the DUT (a light blue rectangular block) being held by the fingers and thumb. The right view shows the DUT (a dark blue rectangular block) being held by the fingers and thumb. Blue arrows point to the contact surfaces between the fingers and the DUT, labeled 'contact surfaces'.](072320147c6e0a97ea1854ac62ddfe17_img.jpg) + +Figure B.3.1.1-1: Positioning guidance for Wide Grip Hand. The image shows two views of a hand phantom holding a device (DUT). The left view shows the DUT (a light blue rectangular block) being held by the fingers and thumb. The right view shows the DUT (a dark blue rectangular block) being held by the fingers and thumb. Blue arrows point to the contact surfaces between the fingers and the DUT, labeled 'contact surfaces'. + +**Figure B.3.1.1-1: Positioning guidance for Wide Grip Hand (© 2001 – 2022 CTIA Certification. Reproduced with permission.), defined in the CTIA Certification OTA Test Plan** + +#### B.3.1.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. + +![A right-handed PDA Grip hand phantom holding a device with a spacer. The spacer is labeled 'side wall' with a right arrow and 'bottom wall' with a down arrow.](d778f25f203fa5a385e9f6458f655763_img.jpg) + +A 3D rendering of a right-handed hand phantom holding a rectangular device. A white spacer is positioned between the device and the hand. The spacer has two labels: 'side wall' with a right-pointing arrow on its top edge, and 'bottom wall' with a downward-pointing arrow on its bottom edge. + +A right-handed PDA Grip hand phantom holding a device with a spacer. The spacer is labeled 'side wall' with a right arrow and 'bottom wall' with a down arrow. + +**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. + +### B.3.2 Head and Hand phantom (Talk Mode) + +#### B.3.2.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 Clause B.2. + +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. The DUT should be set as primary mechanical mode for talk mode scenario, which is declared by manufacturer if the UE support multiple mechanical modes. 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}$ + +Note: the width is the UE width under primary mechanical mode for talk mode scenario. + +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 Clause B.3.1. + +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 B.3.2.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 B.3.2.1-1) at the line RE-LE. Then, position the DUT beside the phantom so that the vertical line (see Figure B.3.2.1-3) is parallel to the reference plane in Figure B.3.2.1-2 and is aligned with the line M-RE on the reference plane (see Figure B.3.2.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 B.3.2.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 at the center of the mouth. The reference plane is a horizontal line passing through RE and LE, and a vertical line passing through M.](9ac4f77294db49ed5489461c24bb01bf_img.jpg) + +Figure B.3.2.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 at the center of the mouth. The reference plane is a horizontal line passing through RE and LE, and a vertical line passing through M. + +Figure B.3.2.1-1: Reference plane on head phantom, front view + +![Figure B.3.2.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 at the mouth. The reference plane is a vertical line passing through RE and M.](62051fc7741291f88d17b08447d20455_img.jpg) + +Figure B.3.2.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 at the mouth. The reference plane is a vertical line passing through RE and M. + +Figure B.3.2.1-2: Reference plane on head phantom, side view + +![Diagram of a mobile handset showing reference lines. A vertical dashed line passes through the center of the handset, labeled 'Vertical line' at the top. A horizontal dashed line passes through the top edge, labeled 'Horizontal line' on the left. The top edge is labeled 'ear piece'. The bottom edge is divided into two equal parts, each labeled 'Half' with a double-headed arrow.](4ece98b7109616bdd7b02d2da1d5cdb8_img.jpg) + +Diagram of a mobile handset showing reference lines. A vertical dashed line passes through the center of the handset, labeled 'Vertical line' at the top. A horizontal dashed line passes through the top edge, labeled 'Horizontal line' on the left. The top edge is labeled 'ear piece'. The bottom edge is divided into two equal parts, each labeled 'Half' with a double-headed arrow. + +**Figure B.3.2.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 B.3.1, 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. + +#### B.3.2.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 Clause B.3.1.1. + +#### B.3.2.1 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 Clause B.3.1.2. + +### B.3.3 Forearm phantom (Wrist-worn Mode) + +#### B.3.2.1 General + +The positioning specified in this clause is used for the test cases for Wrist-worn Mode using Forearm Phantom. The characteristics of the Forearm phantom is specified in Clause B.2.4. + +Talk mode is used to simulate user cases where the DUT is placed in Forearm phantom. The DUT should be set as primary mechanical mode for browsing mode scenario, which is declared by manufacturer if the UE support multiple mechanical modes. + +#### B.3.2.2 Forearm phantom positioning in the chamber + +The Forearm Phantom shall be mounted in the chamber coordinate system as shown in Figure B.3.2.2-1. + +![Figure B.3.2.2-1: Positioning guidance for Forearm Phantom in the chamber. The image shows a dark grey forearm phantom with a wrist-worn device mounted on it. A coordinate system is overlaid: the Z-axis is a blue vertical arrow pointing up from the top of the phantom, the X-axis is a red arrow pointing left from the device, and the Y-axis is a green arrow pointing right from the device. The device has a small display showing '10:15'.](4ba0c02941829d6ece2e065f08a4e575_img.jpg) + +Figure B.3.2.2-1: Positioning guidance for Forearm Phantom in the chamber. The image shows a dark grey forearm phantom with a wrist-worn device mounted on it. A coordinate system is overlaid: the Z-axis is a blue vertical arrow pointing up from the top of the phantom, the X-axis is a red arrow pointing left from the device, and the Y-axis is a green arrow pointing right from the device. The device has a small display showing '10:15'. + +**Figure B.3.2.2-1: Positioning guidance for Forearm Phantom in the chamber (© 2001 – 2022 CTIA Certification. Reproduced with permission.), defined in the CTIA Certification OTA Test Plan** + +#### B.3.2.3 Wrist-Worn RedCap Device mounted on the Forearm Phantom + +This clause defines the positioning guideline for wrist-worn RedCap devices. + +The positioning guideline defined in CTIA Certification OTA Test Plan 01.71, section 2.3 [9], is used for FR1 TRP TRS testing for wrist-worn RedCap devices in this technical specification. + +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, as shown in B.3.2.3-1. 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 B.3.2.3-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 a top-down perspective with a red vertical line labeled 'Plane J' and a green horizontal line labeled 'Plane B' passing through the device. The right view shows a side perspective with a blue horizontal line labeled 'Plane K' and 'Plane A' passing through the device. A yellow arrow points to the intersection of the device and the phantom, labeled 'Intersection at Face of Phantom'.](0ba96c8121e21d5b3cdd48e3e19546fd_img.jpg) + +Figure B.3.2.3-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 a top-down perspective with a red vertical line labeled 'Plane J' and a green horizontal line labeled 'Plane B' passing through the device. The right view shows a side perspective with a blue horizontal line labeled 'Plane K' and 'Plane A' passing through the device. A yellow arrow points to the intersection of the device and the phantom, labeled 'Intersection at Face of Phantom'. + +**Figure B.3.2.3-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 B.3.2.3-2. + +![Two forearm phantoms showing the left and right positioning for a wrist-worn device. Each phantom has a vertical scale and a digital watch strapped to it.](1a71c1fcfe031ac87d6458c6b5062bf1_img.jpg) + +The image shows two dark grey forearm phantoms standing vertically. Each phantom has a vertical scale marked with small horizontal lines. A digital wrist-worn device with a black face and a dark strap is attached to the middle of each phantom. The left phantom shows the device at a position marked '10:15' on its scale, and the right phantom shows it at a position marked '10:20'. + +Two forearm phantoms showing the left and right positioning for a wrist-worn device. Each phantom has a vertical scale and a digital watch strapped to it. + +**Figure B.3.2.3-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** + +# --- Annex C (normative): Environmental requirements --- + +## C.1 General + +This normative annex specifies the environmental requirements of the UE. Within these limits the requirements of the present documents shall be fulfilled. + +--- + +## C.2 Environmental + +The requirements in this clause apply to all types of UE(s). + +### C.2.1 Temperature + +All the test cases defined in this technical specification should be measured in room temperature e.g. 25°C. + +### C.2.2 Voltage + +All 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 (informative): Change history + +| Change history | | | | | | | | +|----------------|----------------|------------|------|-----|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2021-11 | RAN4#101-e | R4-2120687 | | | | Initial Skeleton | 0.0.1 | +| 2022-01 | RAN4#101-bis-e | R4-2200971 | | | | R4-2200974 TP to TS 38.161 on requirement applicability | 0.1.0 | +| 2022-03 | RAN4#102-e | R4-2204952 | | | | R4-2205174 TP to 38.161 on general aspects
R4-2207315 Text proposal on environmental requirements for 38.161
R4-2207323 TP to 38.161 on TRP aspects
R4-2207316 TP to TS 38.161 on frequency bands
R4-2207322 TP to TS 38.161 on Annex A: Test methodology | 0.2.0 | +| 2022-05 | RAN4#103-e | R4-2208626 | | | | R4-2208481 TP to TS 38.161 on primary mechanical mode
R4-2210939 TP to 38.161 on EN-DC and PC2 test case applicability rules
R4-2210940 TP to 38.161 on TRP aspects
R4-2210942 TP to TS 38.161 on test method
R4-2210944 TP to TS 38.161 on Phantoms | 0.3.0 | +| 2022-08 | RAN4#104-e | R4-2212810 | | | | R4-2214795 TP to TS 38.161 on general aspects
R4-2214796 TP to TS 38.161 on TRP TRS requirements | 0.4.0 | +| 2022-09 | RAN#97-e | RP-222321 | | | | For one-step approval in RAN Plenary | 1.0.0 | +| 2022-09 | RAN#97-e | RP-222608 | | | | Editorial update from Rapporteur | 1.1.0 | +| 2022-09 | RAN#97-e | | | | | Under change control | 17.0.0 | +| 2022-12 | RAN#98-e | RP-223310 | 0001 | | F | CR to TS 38.161 on test parameters | 17.1.0 | +| 2023-03 | RAN#99 | RP-230514 | 0002 | | F | CR to TS 38.161 on clarification of test parameters | 17.2.0 | +| 2023-06 | RAN#100 | RP-231343 | 0003 | 1 | F | CR to TS 38.161 on EN-DC decision tree | 17.3.0 | +| 2023-06 | RAN#100 | RP-231343 | 0004 | 1 | F | CR to TS 38.161 on measurement grids and editorial correction | 17.3.0 | +| 2023-12 | RAN#102 | RP-233365 | 0007 | | B | CR to TS 38.161 on New test configurations for Rel-18 TRP TRS | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38174/01855a115275f85d385c12fe6aa4c4ae_img.jpg b/marked/Rel-18/38_series/38174/01855a115275f85d385c12fe6aa4c4ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e17bc1dccebaa620a64d6b6c661dc462b810790 --- /dev/null +++ b/marked/Rel-18/38_series/38174/01855a115275f85d385c12fe6aa4c4ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24f3e9c2e40b427f2c4f404c2f4771f62cd7a97dd95e6feccd379bdb6d71b3de +size 30117 diff --git a/marked/Rel-18/38_series/38174/17f63ca1463dd3a235a7bea317eceba2_img.jpg b/marked/Rel-18/38_series/38174/17f63ca1463dd3a235a7bea317eceba2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc4fe76c10fa4f8855f79ef9e218ab797615b84f --- /dev/null +++ b/marked/Rel-18/38_series/38174/17f63ca1463dd3a235a7bea317eceba2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f1be6e9e6fdb7128fc24a31f3ddd29d11dae51fd2dc3c98ea9f194d0c0ac067 +size 35301 diff --git a/marked/Rel-18/38_series/38174/21976e2036dc7868558281681258568b_img.jpg b/marked/Rel-18/38_series/38174/21976e2036dc7868558281681258568b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b7e5ca5ba66f0f99aded780a52f1a65cb015d2df --- /dev/null +++ b/marked/Rel-18/38_series/38174/21976e2036dc7868558281681258568b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa4046290cc7b010ff0d12a17c97ebb1205c34dc1e1c2fc4f444635af12ed9bd +size 33133 diff --git a/marked/Rel-18/38_series/38174/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-18/38_series/38174/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..268892457dcf1dd10c18d4332021662035f98ad2 --- /dev/null +++ b/marked/Rel-18/38_series/38174/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:10fbf9d9b06bb5970518949fd788cec0bdd39f3461fc974e1ed40f21d5947311 +size 31487 diff --git a/marked/Rel-18/38_series/38174/4f3e31cc28990010782bfee837129791_img.jpg b/marked/Rel-18/38_series/38174/4f3e31cc28990010782bfee837129791_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a5fdd2054c53cbc84ee5420a0dd7cdbc9a714cc --- /dev/null +++ b/marked/Rel-18/38_series/38174/4f3e31cc28990010782bfee837129791_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d7e8457f777ecb1977d7f1691bd7359c979125ceb03f8a4e18f254f77a0573b +size 20809 diff --git a/marked/Rel-18/38_series/38174/507613acfd7f6ef6af724a2005f24024_img.jpg b/marked/Rel-18/38_series/38174/507613acfd7f6ef6af724a2005f24024_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bad51b6354c9bd4842603d7b866325d103557b25 --- /dev/null +++ b/marked/Rel-18/38_series/38174/507613acfd7f6ef6af724a2005f24024_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:154d44f2184b81d690e77c2aa15622c6bab010c0c8d1269db1ebd814e3093ab6 +size 35060 diff --git a/marked/Rel-18/38_series/38174/50af5a2f950373ea84d0298d4c7ae25d_img.jpg b/marked/Rel-18/38_series/38174/50af5a2f950373ea84d0298d4c7ae25d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac3258d4a655aaf22c2b7a71fe7f6f48f5ce1e92 --- /dev/null +++ b/marked/Rel-18/38_series/38174/50af5a2f950373ea84d0298d4c7ae25d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9d58f59e2739a87b5fcced6087693affdd177c9d53f549b374e449f4d996536 +size 65104 diff --git a/marked/Rel-18/38_series/38174/53aea0bced847238f29b804b3d23744f_img.jpg b/marked/Rel-18/38_series/38174/53aea0bced847238f29b804b3d23744f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e384e72a98503d7c39d2defdc18e51e9fa227634 --- /dev/null +++ b/marked/Rel-18/38_series/38174/53aea0bced847238f29b804b3d23744f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e89724246dc596aa901c9ba5cdc1bd194c7efb7efcf0bc73ce0f68bbfee937d +size 28358 diff --git a/marked/Rel-18/38_series/38174/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38174/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f939ba2c8b3d24abdff772a2caf235d5ec9f06d5 --- /dev/null +++ b/marked/Rel-18/38_series/38174/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f336d8ab4c596f6b12ab1a49571a6ccdd50c8514a7f00c0aea24a3973944a140 +size 8330 diff --git a/marked/Rel-18/38_series/38174/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38174/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b8b055955004342ecb17137baee74452a48b3f2 --- /dev/null +++ b/marked/Rel-18/38_series/38174/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd58b710e5ba93c97d0a94f9cf320a36e7b780bb37711df02f7c4f97cabdadc1 +size 5386 diff --git a/marked/Rel-18/38_series/38174/69f94bbb66c1b9e3368795d3abb1e5d0_img.jpg b/marked/Rel-18/38_series/38174/69f94bbb66c1b9e3368795d3abb1e5d0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..250a965448ba0f66f96d2302054b9aaf52d58db4 --- /dev/null +++ b/marked/Rel-18/38_series/38174/69f94bbb66c1b9e3368795d3abb1e5d0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:84e228b3481386a0024b04df113ae8a0e4bf891b3ebec94da3b867bf99a2bb1e +size 35591 diff --git a/marked/Rel-18/38_series/38174/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-18/38_series/38174/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f4f23ed672fea7b06eebc60cc83c48b7b0af3224 --- /dev/null +++ b/marked/Rel-18/38_series/38174/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a24c8ff02575bc3885b84cec6e98f6356da3a798660d02e10fa99000c4fc76e +size 49163 diff --git a/marked/Rel-18/38_series/38174/759c7d62402f0b4651ddce292be5bdef_img.jpg b/marked/Rel-18/38_series/38174/759c7d62402f0b4651ddce292be5bdef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8aa181462648524f9a8d30942884dc4e56303507 --- /dev/null +++ b/marked/Rel-18/38_series/38174/759c7d62402f0b4651ddce292be5bdef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e61d480981e7a1f4e7209b090201878ca14516abcec7ed05647423c0da6b85cb +size 44390 diff --git a/marked/Rel-18/38_series/38174/827cac884f0a6425ff8e36c32a793859_img.jpg b/marked/Rel-18/38_series/38174/827cac884f0a6425ff8e36c32a793859_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6bfc5534b78ff136e1ee5b9d947efda35b9462d7 --- /dev/null +++ b/marked/Rel-18/38_series/38174/827cac884f0a6425ff8e36c32a793859_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:873b860ebf8f7336f892a4784ab55e16e499951f40352207af54f50644443385 +size 32009 diff --git a/marked/Rel-18/38_series/38174/90c8c7dc147b20e66be4dbbf3dd636a6_img.jpg b/marked/Rel-18/38_series/38174/90c8c7dc147b20e66be4dbbf3dd636a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..327bb549e16cdb96326191ef299b29cfca791c99 --- /dev/null +++ b/marked/Rel-18/38_series/38174/90c8c7dc147b20e66be4dbbf3dd636a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5596661f6ed537191d55385a11355c7a96607e60b8c9d580407d65b8c6e67f9d +size 30168 diff --git a/marked/Rel-18/38_series/38174/a8e0f16a3f8bdfbd54d8d18cbdaab339_img.jpg b/marked/Rel-18/38_series/38174/a8e0f16a3f8bdfbd54d8d18cbdaab339_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef662283cff307b9c8b420283fa4bcf04c8174b8 --- /dev/null +++ b/marked/Rel-18/38_series/38174/a8e0f16a3f8bdfbd54d8d18cbdaab339_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb9d73767c314cbcda4b6f87336edae00fe2dee452b29f10823975bc913752a3 +size 30101 diff --git a/marked/Rel-18/38_series/38174/be69dd6f7ffed68b2738a5dd34ad4fd2_img.jpg b/marked/Rel-18/38_series/38174/be69dd6f7ffed68b2738a5dd34ad4fd2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53ff5b2dca503f3a4f5fa175a988f626a9f89b2a --- /dev/null +++ b/marked/Rel-18/38_series/38174/be69dd6f7ffed68b2738a5dd34ad4fd2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dbd71ac67db472632a4da0c9103c42bc99b48083c64a01f924f500d3495dcd59 +size 28873 diff --git a/marked/Rel-18/38_series/38174/c78844717bf077b0701f90f5e2935dea_img.jpg b/marked/Rel-18/38_series/38174/c78844717bf077b0701f90f5e2935dea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bb9a5867631503256e8e78cd4fc6763f22e2c9cd --- /dev/null +++ b/marked/Rel-18/38_series/38174/c78844717bf077b0701f90f5e2935dea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d370d04c40e109b43d241b4ba1c9265ab69257191b90a694d5c9d3fd273ef5a +size 37751 diff --git a/marked/Rel-18/38_series/38174/ca2740c55eeb32272b09a48cdfb7ee4d_img.jpg b/marked/Rel-18/38_series/38174/ca2740c55eeb32272b09a48cdfb7ee4d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b2a780496d2b8591514c85b8dce45b5dacf7ab5 --- /dev/null +++ b/marked/Rel-18/38_series/38174/ca2740c55eeb32272b09a48cdfb7ee4d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cfcb1bb049656afea38f7bb75f7f80a08d0861f331605ec03137f4cad62a1f19 +size 33166 diff --git a/marked/Rel-18/38_series/38174/e4a32ec6d1b56eec38fd6f6313f83b06_img.jpg b/marked/Rel-18/38_series/38174/e4a32ec6d1b56eec38fd6f6313f83b06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f1a33755581355494aeffe476ce22ef00980c45 --- /dev/null +++ b/marked/Rel-18/38_series/38174/e4a32ec6d1b56eec38fd6f6313f83b06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2fc2906395f7ea3924bd1b4405b78fffce3266b66496058a9828dbc5e46c157 +size 28264 diff --git a/marked/Rel-18/38_series/38174/raw.md b/marked/Rel-18/38_series/38174/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..15df848e749e080b5b0ca21ab90abde129b91cd6 --- /dev/null +++ b/marked/Rel-18/38_series/38174/raw.md @@ -0,0 +1,13824 @@ + + +# 3GPP TS 38.174 V18.3.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Integrated access and backhaul 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 text to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. The 'G' has a red signal wave icon below it. + +3GPP logo + +A GLOBAL INITIATIVE + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. +The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. +This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. +Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|---------------------------------------------------------------------------------------|----| +| Foreword..... | 27 | +| 1 Scope..... | 29 | +| 2 References..... | 29 | +| 3 Definitions, symbols and abbreviations..... | 30 | +| 3.1 Definitions..... | 30 | +| 3.2 Symbols..... | 35 | +| 3.3 Abbreviations..... | 36 | +| 4 General..... | 38 | +| 4.1 Relationship with other core specifications..... | 38 | +| 4.2 Relationship between minimum requirements and test requirements..... | 38 | +| 4.3 Conducted and radiated requirement reference points..... | 39 | +| 4.3.2 IAB type 1-H..... | 39 | +| 4.3.3 IAB type 1-O and IAB type 2-O..... | 39 | +| 4.4 IAB classes..... | 40 | +| 4.4.1 IAB-DU classes..... | 40 | +| 4.4.2 IAB-MT classes..... | 40 | +| 4.5 Regional requirements..... | 41 | +| 4.6 Applicability of requirements..... | 41 | +| 4.7 Applicability of RRM requirements in this specification..... | 43 | +| 4.7.1 Applicability of signalling characteristics related RRM requirements..... | 43 | +| 4.8 Requirements for contiguous and non-contiguous spectrum..... | 44 | +| 4.9 Requirements for IAB-DU and IAB-MT capable of multi-band operation..... | 44 | +| 4.10 OTA co-location with other base stations..... | 45 | +| 4.11 Requirements for IAB-DU and IAB-MT capable of simultaneous operation..... | 46 | +| 4.12 Specification suffix information..... | 47 | +| 5 Operating bands and channel arrangement..... | 47 | +| 5.1 General..... | 47 | +| 5.2 Operating bands..... | 47 | +| 5.3 Channel bandwidth..... | 48 | +| 5.3.1 General..... | 48 | +| 5.3.2 Transmission bandwidth configuration..... | 48 | +| 5.3.3 Minimum guardband and transmission bandwidth configuration..... | 49 | +| 5.3.4 RB alignment..... | 49 | +| 5.3.5 IAB-DU and IAB-MT channel bandwidth per operating band..... | 49 | +| 5.3A IAB-DU and IAB-MT channel bandwidth for CA..... | 49 | +| 5.4 Channel arrangement..... | 49 | +| 5.4.1 Channel spacing..... | 49 | +| 5.4.2 Channel raster..... | 49 | +| 5.4.2.1 NR-ARFCN and channel raster..... | 49 | +| 5.4.2.2 Channel raster to resource element mapping..... | 49 | +| 5.4.2.3 Channel raster entries for each operating band ..... | 50 | +| 5.4.3 Synchronization raster..... | 50 | +| 5.4.3.1 Synchronization raster and numbering..... | 50 | +| 5.4.3.2 Synchronization raster to synchronization block resource element mapping..... | 50 | +| 5.4.3.3 Synchronization raster entries for each operating band..... | 50 | +| 6 Conducted transmitter characteristics..... | 50 | +| 6.1 General..... | 50 | +| 6.2 IAB output power..... | 51 | +| 6.2.1 General..... | 51 | +| 6.2.1B Output power for mIAB-MT..... | 51 | +| 6.3.2.1.2B Minimum requirement for mIAB-MT type 1-H ..... | 51 | +| 6.2.2 Minimum requirement for IAB type 1-H..... | 51 | +| 6.2.3 Additional requirements (regional)..... | 51 | +| 6.3 Output power dynamics..... | 51 | +| 6.3.1 IAB-DU Output Power Dynamics..... | 51 | + +| | | | +|-------------|-----------------------------------------------------------------------------------------|----| +| 6.3.1.1 | General..... | 51 | +| 6.3.1.2 | RE power control dynamic range..... | 52 | +| 6.3.1.2.1 | General..... | 52 | +| 6.3.1.2.2 | Minimum requirement for IAB-DU type 1-H ..... | 52 | +| 6.3.1.3 | Total power dynamic range..... | 52 | +| 6.3.1.3.1 | General..... | 52 | +| 6.3.1.3.2 | Minimum requirement for IAB-DU type 1-H ..... | 52 | +| 6.3.2 | IAB-MT Output Power Dynamics..... | 52 | +| 6.3.2.1 | Total power dynamic range..... | 52 | +| 6.3.2.1.1 | General..... | 52 | +| 6.3.2.1.2 | Minimum requirement for IAB-MT type 1-H ..... | 52 | +| 6.3.3 | Power control..... | 52 | +| 6.3.3.1 | Relative power tolerance for local area IAB-MT type 1-H..... | 52 | +| 6.3.3.1B | Relative power tolerance for mIAB-MT type 1-H..... | 53 | +| 6.3.3.2 | Aggregate power tolerance for local area IAB-MT type 1-H..... | 53 | +| 6.4 | Transmit ON/OFF power..... | 53 | +| 6.4.1 | Transmitter OFF power..... | 53 | +| 6.4.1.1 | General..... | 53 | +| 6.4.1.3 | Minimum requirement for IAB-DU type 1-H ..... | 54 | +| 6.4.1.4 | Minimum requirement for IAB-MT type 1-H ..... | 54 | +| 6.4.2 | Transmitter transient period..... | 54 | +| 6.4.2.1 | General..... | 54 | +| 6.4.2.2 | Minimum requirement for IAB-DU type 1-H ..... | 55 | +| 6.4.2.3 | Minimum requirement for IAB-MT type 1-H ..... | 55 | +| 6.5 | Transmitted signal quality..... | 55 | +| 6.5.1 | Frequency error..... | 55 | +| 6.5.1.1 | IAB-DU frequency error..... | 55 | +| 6.5.1.2 | IAB-MT frequency error..... | 55 | +| 6.5.2 | Modulation quality..... | 55 | +| 6.5.2.1 | IAB-DU modulation quality..... | 55 | +| 6.5.2.2 | IAB-MT modulation quality..... | 55 | +| 6.5.2.2.1 | General..... | 55 | +| 6.5.2.2.2 | Minimum requirements for IAB-MT type 1-H ..... | 55 | +| 6.5.2.2.3 | EVM frame structure for measurement..... | 56 | +| 6.5.3 | Time alignment error..... | 56 | +| 6.5.3.1 | IAB-DU time alignment error..... | 56 | +| 6.5.4 | Timing error between IAB-DU and IAB-MT of the same IAB-Node..... | 56 | +| 6.6 | Unwanted emissions..... | 56 | +| 6.6.1 | General..... | 56 | +| 6.6.2 | Occupied bandwidth..... | 57 | +| 6.6.2.1 | General..... | 57 | +| 6.6.2.2 | Minimum requirement for IAB-DU type 1-H ..... | 57 | +| 6.6.2.3 | Minimum requirement for IAB-MT type 1-H ..... | 57 | +| 6.6.3 | Adjacent Channel Leakage Power Ratio..... | 57 | +| 6.6.3.1 | General..... | 57 | +| 6.6.3.2 | Limits and Basic limits ..... | 57 | +| 6.6.3.3 | Minimum requirement for IAB-DU type 1-H and IAB-MT type 1-H ..... | 60 | +| 6.6.4 | Operating band unwanted emissions..... | 61 | +| 6.6.4.1 | General..... | 61 | +| 6.6.4.2 | Basic limits ..... | 63 | +| 6.6.4.2.1 | Basic limits for Wide Area IAB-DU and Wide Area IAB-MT (Category A)..... | 63 | +| 6.6.4.2.2 | Basic limits for Wide Area IAB-DU and Wide Area IAB-MT (Category B)..... | 63 | +| 6.6.4.2.2.1 | Category B requirements..... | 63 | +| 6.6.4.2.3 | Basic limits for Medium Range IAB-DU (Category A and B)..... | 64 | +| 6.6.4.2.4 | Basic limits for Local Area IAB-DU and Local Area IAB-MT (Category A and B)..... | 65 | +| 6.6.4.2.5 | Basic limits for additional requirements..... | 65 | +| 6.6.4.2.5.1 | Limits in FCC Title 47..... | 65 | +| 6.6.4.3 | Minimum requirements for IAB-DU type 1-H and IAB-MT type 1-H ..... | 65 | +| 6.6.5 | Transmitter spurious emissions..... | 66 | +| 6.6.5.1 | General..... | 66 | +| 6.6.5.2 | Basic limits..... | 66 | + +| | | | +|----------------------------|----------------------------------------------------------------------------------|----| +| 6.6.5.2.1 | General transmitter spurious emissions requirements..... | 66 | +| 6.6.5.2.2 | Additional spurious emissions requirements..... | 67 | +| 6.6.5.2.3 | Co-location with base stations and IAB-Nodes..... | 73 | +| 6.6.5.3 | Minimum requirements for IAB-DU and IAB-MT type 1-H ..... | 78 | +| 6.7 | Transmitter intermodulation..... | 78 | +| 6.7.1 | General..... | 78 | +| 6.7.2 | Minimum requirements for IAB-DU type 1-H and IAB-MT type 1-H ..... | 79 | +| 6.7.2.1 | Co-location minimum requirements..... | 79 | +| 6.7.2.2 | Intra-system minimum requirements..... | 79 | +| 7 | Conducted receiver characteristics..... | 80 | +| 7.1 | General..... | 80 | +| 7.2 | Reference sensitivity level..... | 80 | +| 7.2.1 | IAB-DU reference sensitivity level..... | 80 | +| 7.2.1.1 | General..... | 80 | +| 7.2.1.2 | Minimum requirements for IAB-DU type 1-H ..... | 81 | +| 7.2.2 | IAB-MT reference sensitivity level..... | 81 | +| Table 7.2.2-2: Void | | 81 | +| 7.2.2.1 | General..... | 81 | +| 7.2.2.2 | Minimum requirements for IAB-MT type 1-H ..... | 81 | +| 7.3 | Dynamic range..... | 82 | +| 7.3.1 | IAB-DU dynamic range..... | 82 | +| 7.3.1.1 | General..... | 82 | +| 7.3.1.2 | Minimum requirement for IAB-DU type 1-H ..... | 82 | +| 7.4 | In-band selectivity and blocking..... | 82 | +| 7.4.1 | Adjacent Channel Selectivity (ACS)..... | 82 | +| 7.4.1.1 | General..... | 82 | +| 7.4.1.2 | Minimum requirement for IAB-DU type 1-H ..... | 83 | +| 7.4.1.3 | Minimum requirement for IAB-MT type 1-H ..... | 83 | +| 7.4.2 | In-band blocking..... | 84 | +| 7.4.2.1 | General..... | 84 | +| 7.4.2.2 | Minimum requirement for IAB-DU type 1-H ..... | 84 | +| 7.4.2.3 | Minimum requirement for IAB-MT type 1-H ..... | 84 | +| 7.5 | Out-of-band blocking..... | 86 | +| 7.5.1 | General..... | 86 | +| 7.5.2 | Void..... | 86 | +| 7.5.3 | Minimum requirement for IAB-DU type 1-H ..... | 86 | +| 7.5.4 | Co-location minimum requirements for IAB-DU type 1-H ..... | 86 | +| 7.5.5 | Minimum requirement for IAB-MT type 1-H ..... | 87 | +| 7.5.6 | Co-location minimum requirements for IAB-MT type 1-H ..... | 87 | +| 7.6 | Receiver spurious emissions..... | 88 | +| 7.6.1 | General..... | 88 | +| 7.6.2 | IAB-DU receiver spurious emissions..... | 88 | +| 7.6.2.1 | Basic limits..... | 88 | +| 7.6.2.2 | Minimum requirement for IAB-DU type 1-H ..... | 89 | +| 7.6.3 | IAB-MT receiver spurious emissions..... | 89 | +| 7.6.3.1 | Basic limits..... | 89 | +| 7.6.3.2 | Minimum requirement for IAB-MT type 1-H ..... | 90 | +| 7.7 | Receiver intermodulation..... | 90 | +| 7.7.1 | General..... | 90 | +| 7.7.2 | Minimum requirement for IAB-DU type 1-H ..... | 90 | +| 7.7.3 | Minimum requirement for IAB-MT type 1-H ..... | 91 | +| 7.8 | In-channel selectivity..... | 91 | +| 7.8.1 | General..... | 91 | +| 7.8.2 | Minimum requirement for IAB-DU type 1-H ..... | 91 | +| 8 | Conducted performance requirements..... | 91 | +| 8.1 | IAB-DU performance requirements..... | 91 | +| 8.1.1 | General..... | 91 | +| 8.1.2 | Performance requirements for PUSCH..... | 92 | +| 8.1.2.1 | Requirements for PUSCH with transform precoding disabled..... | 92 | +| 8.1.2.1.1 | General..... | 92 | + +| | | | +|-----------|--------------------------------------------------------------|-----| +| 8.1.2.1. | Minimum requirements..... | 92 | +| 8.1.2.2 | Requirements for PUSCH with transform precoding enabled..... | 99 | +| 8.1.2.2.1 | General..... | 99 | +| 8.1.2.2.2 | Minimum requirements..... | 100 | +| 8.1.2.3 | Requirements for UCI multiplexed on PUSCH..... | 101 | +| 8.1.2.3.1 | General..... | 101 | +| 8.1.2.3.2 | Minimum requirements..... | 102 | +| 8.1.3 | Performance requirements for PUCCH..... | 103 | +| 8.1.3.1 | DTX to ACK probability..... | 103 | +| 8.1.3.1.1 | General..... | 103 | +| 8.1.3.1.2 | Minimum requirement..... | 103 | +| 8.1.3.2 | Performance requirements for PUCCH format 0..... | 103 | +| 8.1.3.2.1 | General..... | 103 | +| 8.1.3.2.2 | Minimum requirement..... | 104 | +| 8.1.3.3 | Performance requirements for PUCCH format 1..... | 104 | +| 8.1.3.3.1 | NACK to ACK requirements..... | 104 | +| 8.1.3.3.2 | ACK missed detection requirements..... | 106 | +| 8.1.3.4 | Performance requirements for PUCCH format 2..... | 107 | +| 8.1.3.4.1 | NACK to ACK requirements..... | 107 | +| 8.1.3.4.2 | UCI BLER performance requirements..... | 108 | +| 8.1.3.5 | Performance requirements for PUCCH format 3..... | 108 | +| 8.1.3.5.1 | General..... | 108 | +| 8.1.3.5.2 | Minimum requirements..... | 109 | +| 8.1.3.6 | Performance requirements for PUCCH format 4..... | 110 | +| 8.1.3.6.1 | General..... | 110 | +| 8.1.3.6.2 | Minimum requirement..... | 110 | +| 8.1.3.7 | Performance requirements for multi-slot PUCCH..... | 111 | +| 8.1.3.7.1 | General..... | 111 | +| 8.1.3.7.2 | Performance requirements for multi-slot PUCCH format 1..... | 111 | +| 8.1.4 | Performance requirements for PRACH..... | 112 | +| 8.1.4.1 | PRACH false alarm probability..... | 112 | +| 8.1.4.1.1 | General..... | 112 | +| 8.1.4.1.2 | Minimum requirement..... | 113 | +| 8.1.4.2 | PRACH detection requirements..... | 113 | +| 8.1.4.2.1 | General..... | 113 | +| 8.1.4.2.2 | Minimum requirements for normal mode..... | 113 | +| 8.2 | IAB-MT requirements..... | 114 | +| 8.2.1 | General..... | 114 | +| 8.2.2 | Demodulation performance requirements..... | 114 | +| 8.2.2.1 | Performance requirements for PDSCH..... | 114 | +| 8.2.2.1.1 | General..... | 114 | +| 8.2.2.1.2 | Minimum requirements..... | 115 | +| 8.2.2.2 | Performance requirements for PDCCH..... | 116 | +| 8.2.2.2.1 | General..... | 116 | +| 8.2.2.2.2 | Minimum requirements..... | 116 | +| 8.2.3 | CSI reporting requirements..... | 116 | +| 8.2.3.1 | General..... | 116 | +| 8.2.3.1.1 | Common test parameters..... | 116 | +| 8.2.3.2 | Reporting of Channel Quality Indicator (CQI)..... | 118 | +| 8.2.3.2.1 | General..... | 118 | +| 8.2.3.2.2 | Minimum requirements..... | 118 | +| 8.2.3.3 | Reporting of Precoding Matrix Indicator (PMI)..... | 119 | +| 8.2.3.3.1 | General..... | 119 | +| 8.2.3.3.2 | Minimum requirements..... | 121 | +| 8.2.3.4 | Reporting of Rank Indicator (RI)..... | 121 | +| 8.2.3.4.1 | General..... | 121 | +| 8.2.3.4.2 | Minimum requirements..... | 122 | +| 9 | Radiated transmitter characteristics..... | 123 | +| 9.1 | General..... | 123 | +| 9.2 | Radiated transmit power..... | 123 | +| 9.2.1 | General..... | 123 | + +| | | | +|------------|----------------------------------------------------------------------------------------------------|-----| +| 9.2.2 | Minimum requirement for IAB-DU type 1-H, IAB-DU type 1-O, IAB-MT type 1-H and IAB-MT type 1-O..... | 124 | +| 9.2.3 | Minimum requirement for IAB-DU type 2-O and IAB-MT type 2-O..... | 124 | +| 9.2.4 | Configured radiated output power..... | 124 | +| 9.2.4.1 | IAB-MT configured output power for IAB-MT type 1-H, 1-O and 2-O..... | 124 | +| 9.3 | OTA IAB output power..... | 124 | +| 9.3.1 | General..... | 124 | +| 9.3.1B | Output power for mIAB-MT..... | 125 | +| 9.3.2 | Minimum requirement for IAB-DU type 1-O and IAB-MT type 1-O..... | 125 | +| 9.3.3 | Minimum requirement for IAB type 2-O..... | 125 | +| 9.4 | OTA output power dynamics..... | 125 | +| 9.4.1 | IAB-DU OTA Output Power Dynamics..... | 125 | +| 9.4.1.1 | General..... | 125 | +| 9.4.1.2 | OTA RE power control dynamic range..... | 126 | +| 9.4.1.2.1 | General..... | 126 | +| 9.4.1.2.2 | Minimum requirement for IAB-DU type 1-O ..... | 126 | +| 9.4.1.3 | OTA total power dynamic range..... | 126 | +| 9.4.1.3.1 | General..... | 126 | +| 9.4.1.3.2 | Minimum requirement for IAB-DU type 1-O ..... | 126 | +| 9.4.1.3.3 | Minimum requirement for IAB-DU type 2-O ..... | 126 | +| 9.4.2 | IAB-MT OTA Output Power Dynamics..... | 126 | +| 9.4.2.1 | OTA total power dynamic range..... | 126 | +| 9.4.2.1.1 | General..... | 126 | +| 9.4.2.1.2 | Minimum requirement for IAB-MT type 1-O..... | 126 | +| 9.4.2.1.2B | Minimum requirement for mIAB-MT type 1-O..... | 126 | +| 9.4.2.1.3 | Minimum requirement for IAB-MT type 2-O..... | 127 | +| 9.4.2.1.3B | Minimum requirement for mIAB-MT type 2-O..... | 127 | +| 9.4.3 | Power control..... | 127 | +| 9.4.3.1 | Power control for local area IAB-MT type 1-O..... | 127 | +| 9.4.3.1.1 | Relative EIRP tolerance for local area IAB-MT type 1-O..... | 127 | +| 9.4.3.1.1B | Relative EIRP tolerance for mIAB-MT type 1-O..... | 127 | +| 9.4.3.1.2 | Aggregate EIRP tolerance for local area IAB-MT type 1-O..... | 128 | +| 9.4.3.2 | Power control for local area IAB-MT type 2-O..... | 128 | +| 9.4.3.2.1 | Relative EIRP tolerance for local area IAB-MT type 2-O..... | 128 | +| 9.4.3.2.1B | Relative EIRP tolerance for mIAB-MT type 2-O..... | 128 | +| 9.4.3.2.2 | Aggregate EIRP tolerance for local area IAB-MT type 2-O..... | 129 | +| 9.5 | OTA transmit ON/OFF power..... | 129 | +| 9.5.1 | General..... | 129 | +| 9.5.2 | OTA transmitter OFF power..... | 129 | +| 9.5.2.1 | General..... | 129 | +| 9.5.2.2 | Minimum requirement for IAB-DU type 1-O..... | 129 | +| 9.5.2.3 | Minimum requirement for IAB-DU type 2-O..... | 129 | +| 9.5.2.4 | Minimum requirement for IAB-MT type 1-O..... | 130 | +| 9.5.2.5 | Minimum requirement for IAB-MT type 2-O..... | 130 | +| 9.5.3 | OTA transient period..... | 130 | +| 9.5.3.1 | General..... | 130 | +| 9.5.3.2 | Minimum requirement for IAB-DU type 1-O..... | 130 | +| 9.5.3.3 | Minimum requirement for IAB-DU type 2-O..... | 130 | +| 9.5.3.4 | Minimum requirement for IAB-MT type 1-O..... | 130 | +| 9.5.3.5 | Minimum requirement for IAB-MT type 2-O..... | 130 | +| 9.6 | OTA transmitted signal quality..... | 130 | +| 9.6.1 | OTA frequency error..... | 130 | +| 9.6.1.1 | IAB-DU OTA frequency error..... | 130 | +| 9.6.1.2 | IAB-MT OTA frequency error..... | 130 | +| 9.6.1.2.1 | General..... | 130 | +| 9.6.1.2.2 | Minimum requirement for IAB-MT type 1-O..... | 130 | +| 9.6.1.2.3 | Minimum requirement for IAB-MT type 2-O..... | 130 | +| 9.6.2 | OTA modulation quality..... | 131 | +| 9.6.2.1 | IAB-DU OTA modulation quality..... | 131 | +| 9.6.2.2 | IAB-MT OTA modulation quality..... | 131 | +| 9.6.2.2.1 | General..... | 131 | + +| | | | +|-------------|-------------------------------------------------------------------------------------------|-----| +| 9.6.2.2.2 | Minimum requirement for IAB-MT type 1-O..... | 131 | +| 9.6.2.2.3 | Minimum requirement for IAB-MT type 2-O..... | 131 | +| 9.6.2.2.4 | EVM frame structure for measurement..... | 131 | +| 9.6.3 | OTA time alignment error..... | 131 | +| 9.6.3.1 | IAB-DU OTA time alignment error..... | 131 | +| 9.6.4 | Timing error between IAB-DU and IAB-MT of the same IAB-Node..... | 132 | +| 9.7 | OTA unwanted emissions..... | 132 | +| 9.7.1 | General..... | 132 | +| 9.7.2 | OTA occupied bandwidth..... | 132 | +| 9.7.2.1 | General..... | 132 | +| 9.7.2.2 | Minimum requirement for IAB-DU type 1-O and IAB-DU type 2-O ..... | 133 | +| 9.7.2.3 | Minimum requirement for IAB-MT type 1-O and IAB-MT type 2-O ..... | 133 | +| 9.7.3 | OTA Adjacent Channel Leakage Power Ratio (ACLR)..... | 133 | +| 9.7.3.1 | General..... | 133 | +| 9.7.3.2 | Minimum requirement for IAB-DU type 1-O and IAB-MT type 1-O ..... | 133 | +| 9.7.3.3 | Minimum requirement for IAB-DU type 2-O and Wide Area IAB-MT type 2-O ..... | 133 | +| 9.7.3.4 | Minimum requirement for Local Area IAB-MT type 2-O ..... | 135 | +| 9.7.4 | OTA operating band unwanted emissions..... | 137 | +| 9.7.4.1 | General..... | 137 | +| 9.7.4.2 | Minimum requirement for IAB-DU type 1-O ..... | 137 | +| 9.7.4.3 | Minimum requirement for IAB-MT type 1-O ..... | 138 | +| 9.7.4.4 | Additional requirements..... | 138 | +| 9.7.4.4.1 | Limits in FCC Title 47..... | 138 | +| 9.7.4.5 | Minimum requirement for IAB-DU type 2-O and IAB-MT type 2-O ..... | 138 | +| 9.7.4.5.1 | General..... | 138 | +| 9.7.4.5.2 | OTA operating band unwanted emission limits (Category A)..... | 139 | +| 9.7.4.5.3 | OTA operating band unwanted emission limits (Category B)..... | 140 | +| 9.7.4.5.4 | Additional OTA operating band unwanted emission requirements..... | 140 | +| 9.7.5 | OTA transmitter spurious emissions..... | 140 | +| 9.7.5.1 | General..... | 140 | +| 9.7.5.2 | Minimum requirement for IAB-DU type 1-O and IAB-MT type 1-O ..... | 141 | +| 9.7.5.2.1 | General..... | 141 | +| 9.7.5.2.2 | General OTA transmitter spurious emissions requirements..... | 141 | +| 9.7.5.2.3 | Additional spurious emissions requirements..... | 141 | +| 9.7.5.2.4 | Co-location with other base stations and IAB-Nodes..... | 141 | +| 9.7.5.3 | Minimum requirement for IAB-DU type 2-O and IAB-MT type 2-O ..... | 142 | +| 9.7.5.3.1 | General..... | 142 | +| 9.7.5.3.2 | General OTA transmitter spurious emissions requirements..... | 142 | +| 9.7.5.3.2.1 | General..... | 142 | +| 9.7.5.3.2.2 | OTA transmitter spurious emissions (Category A)..... | 142 | +| 9.7.5.3.2.3 | OTA transmitter spurious emissions (Category B)..... | 142 | +| 9.7.5.3.3 | Additional OTA transmitter spurious emissions requirements..... | 143 | +| 9.7.5.3.3.1 | Limits for protection of Earth Exploration Satellite Service..... | 143 | +| 9.8 | OTA transmitter intermodulation..... | 143 | +| 9.8.1 | General..... | 143 | +| 9.8.2 | Minimum requirement for IAB-DU type 1-O and IAB-MT type 1-O ..... | 144 | +| 10 | Radiated receiver characteristics..... | 144 | +| 10.1 | General..... | 144 | +| 10.2 | OTA sensitivity..... | 145 | +| 10.2.1 | IAB-DU OTA sensitivity..... | 145 | +| 10.2.1.1 | IAB-DU type 1-H and IAB-DU type 1-O..... | 145 | +| 10.2.1.2 | IAB-DU type 2-O..... | 145 | +| 10.2.2 | IAB-MT OTA sensitivity..... | 146 | +| 10.2.2.1 | IAB-MT type 1-H and IAB-MT type 1-O..... | 146 | +| 10.2.2.1.1 | General..... | 146 | +| 10.2.2.1.2 | Minimum requirement..... | 146 | +| 10.2.2.2 | IAB-MT type 2-O..... | 146 | +| 10.3 | OTA reference sensitivity level..... | 146 | +| 10.3.1 | General..... | 146 | +| 10.3.2 | IAB-DU OTA reference sensitivity level..... | 147 | +| 10.3.2.1 | Minimum requirement for IAB-DU type 1-O ..... | 147 | + +| | | | +|------------|------------------------------------------------------------------------------|-----| +| 10.3.2.2 | Minimum requirement for IAB-DU type 2-O ..... | 147 | +| 10.3.3 | IAB-MT OTA reference sensitivity level..... | 147 | +| 10.3.3.1 | General..... | 147 | +| 10.3.3.2 | Minimum requirement for IAB-MT type 1-O ..... | 147 | +| 10.3.3.3 | Minimum requirement for IAB-MT type 2-O ..... | 148 | +| 10.4 | OTA Dynamic range..... | 149 | +| 10.4.1 | IAB-DU OTA dynamic range..... | 149 | +| 10.4.1.1 | General..... | 149 | +| 10.4.1.2 | Minimum requirement for IAB-DU type 1-O ..... | 149 | +| 10.5 | OTA in-band selectivity and blocking..... | 149 | +| 10.5.1 | OTA adjacent channel selectivity..... | 149 | +| 10.5.1.1 | General..... | 149 | +| 10.5.1.2 | Minimum requirement for IAB-DU type 1-O ..... | 149 | +| 10.5.1.3 | Minimum requirement for IAB-DU type 2-O ..... | 150 | +| 10.5.1.4 | Minimum requirement for IAB-MT type 2-O ..... | 150 | +| 10.5.1.5 | Minimum requirement for IAB-MT type 1-O ..... | 150 | +| 10.5.2 | OTA in-band blocking..... | 151 | +| 10.6 | OTA out-of-band blocking..... | 155 | +| 10.6.1 | General..... | 155 | +| 10.6.2 | Minimum requirement for IAB-MT type 1-O and IAB-DU type 1-O..... | 155 | +| 10.6.3 | Minimum requirement for IAB-MT type 2-O and IAB-DU type 2-O..... | 156 | +| 10.6.4 | Co-location minimum requirement for IAB-MT type 1-O and IAB-DU type 1-O..... | 157 | +| 10.7 | OTA receiver spurious emissions..... | 157 | +| 10.7.1 | General..... | 157 | +| 10.7.2 | IAB-DU OTA receiver spurious emissions..... | 158 | +| 10.7.2.1 | Minimum requirement for IAB-DU type 1-O..... | 158 | +| 10.7.2.2 | Minimum requirement for IAB-DU type 2-O..... | 158 | +| 10.7.3 | IAB-MT OTA receiver spurious emissions..... | 158 | +| 10.7.3.1 | Minimum requirement for IAB-MT type 1-O..... | 158 | +| 10.7.3.2 | Minimum requirement for IAB-MT type 2-O..... | 158 | +| 10.8 | OTA receiver intermodulation..... | 159 | +| 10.8.1 | General..... | 159 | +| 10.8.2 | Minimum requirement for IAB-DU type 1-O ..... | 159 | +| 10.8.3 | Minimum requirement for IAB-DU type 2-O ..... | 159 | +| 10.8.4 | Minimum requirement for IAB-MT type 1-O ..... | 160 | +| 10.9 | OTA in-channel selectivity..... | 160 | +| 10.9.1 | General..... | 160 | +| 10.9.2 | Minimum requirement for IAB-DU type 1-O ..... | 160 | +| 10.9.3 | Minimum requirement for IAB-DU type 2-O ..... | 160 | +| 11 | Radiated performance requirements..... | 161 | +| 11.1 | IAB-DU performance requirements..... | 161 | +| 11.1.1 | General..... | 161 | +| 11.1.2 | OTA demodulation branches..... | 161 | +| 11.1.2 | Performance requirements for PUSCH..... | 162 | +| 11.1.2.1 | Performance requirements for IAB type 1-O ..... | 162 | +| 11.1.2.1.1 | Performance requirements for PUSCH with transform precoding disabled..... | 162 | +| 11.1.2.1.2 | Performance requirements for PUSCH with transform precoding enabled..... | 162 | +| 11.1.2.1.3 | Performance requirements for UCI multiplexed on PUSCH..... | 162 | +| 11.1.2.2 | Performance requirements for IAB type 2-O..... | 162 | +| 11.1.2.2.1 | Performance requirements for PUSCH with transform precoding disabled..... | 162 | +| 11.1.2.2.2 | Performance requirements for PUSCH with transform precoding enabled..... | 165 | +| 11.1.2.2.3 | Performance requirements for UCI multiplexed on PUSCH..... | 166 | +| 11.1.3 | Performance requirements for PUCCH..... | 168 | +| 11.1.3.1 | Performance requirements for IAB type 1-O ..... | 168 | +| 11.1.3.1.1 | DTX to ACK probability..... | 168 | +| 11.1.3.1.2 | Performance requirements for PUCCH format 0..... | 168 | +| 11.1.3.1.3 | Performance requirements for PUCCH format 1..... | 168 | +| 11.1.3.1.4 | Performance requirements for PUCCH format 2..... | 168 | +| 11.1.3.1.5 | Performance requirements for PUCCH format 3..... | 168 | +| 11.1.3.1.6 | Performance requirements for PUCCH format 4..... | 168 | +| 11.1.3.1.7 | Performance requirements for multi-slot PUCCH..... | 169 | + +| | | | +|--------------|--------------------------------------------------------|-----| +| 11.1.3.2 | Performance requirements for IAB type 2-O ..... | 169 | +| 11.1.3.2.1 | DTX to ACK probability..... | 169 | +| 11.1.3.2.2 | Performance requirements for PUCCH format 0..... | 169 | +| 11.1.3.2.3 | Performance requirements for PUCCH format 1..... | 170 | +| 11.1.3.2.4 | Performance requirements for PUCCH format 2..... | 171 | +| 11.1.3.2.5 | Performance requirements for PUCCH format 3..... | 173 | +| 11.1.3.2.6 | Performance requirements for PUCCH format 4..... | 174 | +| 11.1.4 | Performance requirements for PRACH..... | 174 | +| 11.1.4.1 | Performance requirements for IAB type 1-O ..... | 174 | +| 11.1.4.1.1 | PRACH False alarm probability..... | 174 | +| 11.1.4.1.2 | PRACH detection requirements..... | 174 | +| 11.1.4.2 | Performance requirements for IAB type 2-O ..... | 175 | +| 11.1.4.2.1 | PRACH false alarm probability..... | 175 | +| 11.1.4.2.2 | PRACH missed detection requirements..... | 175 | +| 11.2 | IAB-MT performance requirements..... | 176 | +| 11.2.1 | General..... | 176 | +| 11.2.2 | OTA demodulation branches..... | 176 | +| 11.2.2 | Demodulation performance requirements..... | 176 | +| 11.2.2.1 | Performance requirements for IAB type 1-O..... | 176 | +| 11.2.2.1.1 | Performance requirements for PDSCH..... | 176 | +| 11.2.2.1.2 | Performance requirements for PDCCH..... | 178 | +| 11.2.2.2 | Performance requirements for IAB type 2-O..... | 179 | +| 11.2.2.2.1 | Performance requirements for PDSCH..... | 179 | +| 11.2.2.2.2 | Performance requirements for PDCCH..... | 180 | +| 11.2.3 | CSI reporting requirements..... | 181 | +| 11.2.3.1 | Performance requirements for IAB type 1-O..... | 181 | +| 11.2.3.1.1 | Reporting of Channel Quality Indicator (CQI)..... | 181 | +| 11.2.3.1.2 | Reporting of Precoding Matrix Indicator (PMI)..... | 181 | +| 11.2.3.1.3 | Reporting of Rank Indicator (RI)..... | 181 | +| 11.2.3.2 | Performance requirements for IAB type 2-O..... | 182 | +| 11.2.3.2.1 | General..... | 182 | +| 11.2.3.2.2 | Reporting of Channel Quality Indicator (CQI)..... | 183 | +| 11.2.3.2.3 | Reporting of Precoding Matrix Indicator (PMI)..... | 185 | +| 11.2.3.2.4 | Reporting of Rank Indicator (RI)..... | 187 | +| 12 | Radio Resource Management requirements..... | 189 | +| 12.1 | RRC_CONNECTED state mobility for IAB-MTs..... | 189 | +| 12.1.1 | RRC Connection Mobility Control..... | 189 | +| 12.1.1.1 | SA: RRC Re-establishment..... | 189 | +| 12.1.1.1.1 | Introduction..... | 189 | +| 12.1.1.1.2 | Requirements..... | 189 | +| 12.1.1.1.2.1 | IAB MT Re-establishment delay requirement..... | 189 | +| 12.1.1.1B | SA: RRC Re-establishment for mIAB-MT..... | 191 | +| 12.1.1.1B.1 | Introduction..... | 191 | +| 12.1.1.1B.2 | Requirements..... | 191 | +| 12.1.1.2 | Random access..... | 192 | +| 12.1.1.3 | SA: RRC Connection Release with Redirection..... | 192 | +| 12.1.1.3.1 | Introduction..... | 192 | +| 12.1.1.3.2 | Requirements..... | 192 | +| 12.1.1.3.2.1 | RRC connection release with redirection to NR..... | 192 | +| 12.1.2 | Void..... | 193 | +| 12.1.2B | Handover for mIAB-MT..... | 193 | +| 12.1.2B.1 | Introduction..... | 193 | +| 12.1.2B.2 | NR FR1 - NR FR1 Intra-frequency Handover..... | 193 | +| 12.1.2B.2.1 | Handover delay..... | 193 | +| 12.1.2B.2.2 | Interruption time..... | 193 | +| 12.1.2B.3 | NR FR2-1 - NR FR2-1 Intra-frequency Handover..... | 194 | +| 12.1.2B.3.1 | Handover delay..... | 194 | +| 12.1.2B.3.2 | Interruption time..... | 194 | +| 12.2 | Timing..... | 195 | +| 12.2.1 | IAB-MT transmit timing..... | 195 | +| 12.2.1.1 | Introduction..... | 195 | + +| | | | +|-------------|------------------------------------------------------------------------|-----| +| 12.2.1.2 | Requirements..... | 195 | +| 12.2.1.2.1 | Gradual timing adjustment..... | 196 | +| 12.2.3 | IAB-MT timing advance..... | 197 | +| 12.2.3.1 | Timing Advance adjustment delay..... | 197 | +| 12.2.3.2 | Timing Advance adjustment accuracy..... | 197 | +| 12.2.4 | Cell phase synchronization accuracy..... | 197 | +| 12.2.4.1 | Introduction..... | 197 | +| 12.2.4.2 | Requirements..... | 197 | +| 12.3 | Signalling Characteristics for IAB MTs..... | 197 | +| 12.3.1 | Radio Link Monitoring..... | 197 | +| 12.3.1.1 | Introduction..... | 197 | +| 12.3.1.2 | Requirements for SSB based radio link monitoring..... | 197 | +| 12.3.1.2.1 | Introduction..... | 197 | +| 12.3.1.2.2 | Minimum requirement..... | 198 | +| 12.3.1.2.3 | Measurement restrictions for SSB based RLM..... | 199 | +| 12.3.1.3 | Requirements for CSI-RS based radio link monitoring..... | 199 | +| 12.3.1.3.1 | Introduction..... | 199 | +| 12.3.1.3.2 | Minimum requirement..... | 200 | +| 12.3.1.3.3 | Measurement restrictions for CSI-RS based RLM..... | 201 | +| 12.3.1.4 | Minimum requirement for IAB-MT turning off the transmitter..... | 201 | +| 12.3.1.5 | Minimum requirement for L1 indication..... | 201 | +| 12.3.1.6 | Scheduling availability of IAB-MT during radio link monitoring..... | 201 | +| 12.3.2 | Link Recovery Procedure..... | 201 | +| 12.3.2.1 | Introduction..... | 201 | +| 12.3.2.2 | Requirements for SSB based beam failure detection..... | 202 | +| 12.3.2.2.1 | Introduction..... | 202 | +| 12.3.2.2.2 | Minimum requirement..... | 202 | +| 12.3.2.2.3 | Measurement restriction for SSB based beam failure detection..... | 202 | +| 12.3.2.3 | Requirements for CSI-RS based beam failure detection..... | 202 | +| 12.3.2.3.1 | Introduction..... | 202 | +| 12.3.2.3.2 | Minimum requirement..... | 203 | +| 12.3.2.3.3 | Measurement restrictions for CSI-RS based beam failure detection..... | 204 | +| 12.3.2.4 | Minimum requirement for L1 indication..... | 204 | +| 12.3.2.5 | Requirements for SSB based candidate beam detection..... | 204 | +| 12.3.2.5.1 | Introduction..... | 204 | +| 12.3.2.5.2 | Minimum requirement..... | 204 | +| 12.3.2.5.3 | Measurement restriction for SSB based candidate beam detection..... | 205 | +| 12.3.2.6 | Requirements for CSI-RS based candidate beam detection..... | 205 | +| 12.3.2.6.1 | Introduction..... | 205 | +| 12.3.2.6.2 | Minimum requirement..... | 205 | +| 12.3.2.6.3 | Measurement restriction for CSI-RS based candidate beam detection..... | 206 | +| 12.3.2.7 | Scheduling availability of IAB-MT during beam failure detection..... | 206 | +| 12.3.2.8 | Scheduling availability of IAB-MT during candidate beam detection..... | 206 | +| 12.3B | Signalling Characteristics for mIAB MTs..... | 206 | +| 12.3B.1 | Radio Link Monitoring..... | 206 | +| 12.3B.1.1 | Introduction..... | 206 | +| 12.3B.1.2 | Requirements for SSB based radio link monitoring..... | 206 | +| 12.3B.1.2.1 | Introduction..... | 206 | +| 12.3B.1.2.2 | Minimum requirement..... | 207 | +| 12.3B.1.2.3 | Measurement restrictions for SSB based RLM..... | 208 | +| 12.3B.1.3 | Requirements for CSI-RS based radio link monitoring..... | 208 | +| 12.3B.1.3.1 | Introduction..... | 208 | +| 12.3B.1.3.2 | Minimum requirement..... | 209 | +| 12.3B.1.3.3 | Measurement restrictions for CSI-RS based RLM..... | 210 | +| 12.3B.1.4 | Minimum requirement for mIAB-MT turning off the transmitter..... | 210 | +| 12.3B.1.5 | Minimum requirement for L1 indication..... | 211 | +| 12.3B.1.6 | Scheduling availability of mIAB-MT during radio link monitoring..... | 211 | +| 12.3B.2 | Link Recovery Procedure..... | 211 | +| 12.3B.2.1 | Introduction..... | 211 | +| 12.3B.2.2 | Requirements for SSB based beam failure detection..... | 211 | +| 12.3B.2.2.1 | Introduction..... | 211 | + +| | | | +|-------------|-------------------------------------------------------------------------|-----| +| 12.3B.2.2.2 | Minimum requirement..... | 211 | +| 12.3B.2.2.3 | Measurement restriction for SSB based beam failure detection..... | 212 | +| 12.3B.2.3 | Requirements for CSI-RS based beam failure detection..... | 212 | +| 12.3B.2.3.1 | Introduction..... | 212 | +| 12.3B.2.3.2 | Minimum requirement..... | 212 | +| 12.3B.2.3.3 | Measurement restrictions for CSI-RS based beam failure detection..... | 213 | +| 12.3B.2.4 | Minimum requirement for L1 indication..... | 213 | +| 12.3B.2.5 | Requirements for SSB based candidate beam detection..... | 214 | +| 12.3B.2.5.1 | Introduction..... | 214 | +| 12.3B.2.5.2 | Minimum requirement..... | 214 | +| 12.3B.2.5.3 | Measurement restriction for SSB based candidate beam detection..... | 215 | +| 12.3B.2.6 | Requirements for CSI-RS based candidate beam detection..... | 215 | +| 12.3B.2.6.1 | Introduction..... | 215 | +| 12.3B.2.6.2 | Minimum requirement..... | 215 | +| 12.3B.2.6.3 | Measurement restriction for CSI-RS based candidate beam detection..... | 216 | +| 12.3B.2.7 | Scheduling availability of mIAB-MT during beam failure detection..... | 216 | +| 12.3B.2.8 | Scheduling availability of mIAB-MT during candidate beam detection..... | 216 | +| 12.3B.3 | Active TCI state switching delay..... | 216 | +| 12.3B.3.1 | Introduction..... | 216 | +| 12.3B.3.2 | Known conditions for TCI state..... | 216 | +| 12.3B.3.3 | MAC-CE based TCI state switch delay..... | 217 | +| 12.3B.3.4 | DCI based TCI state switch delay..... | 218 | +| 12.3B.3.5 | RRC based TCI state switch delay..... | 218 | +| 12.3B.3.6 | Active TCI state list update delay..... | 218 | +| 12.4 | Void..... | 219 | +| 12.4B | Measurement Procedure for mIAB-MT..... | 219 | +| 12.4B.1 | General measurement requirement..... | 219 | +| 12.4B.1.1 | Introduction..... | 219 | +| 12.4B.2 | NR intra-frequency measurements..... | 219 | +| 12.4B.2.1 | Introduction..... | 219 | +| 12.4B.2.2 | Requirements applicability..... | 219 | +| 12.4B.2.3 | Number of cells and number of SSB..... | 219 | +| 12.4B.2.3.1 | Requirements for FR1..... | 219 | +| 12.4B.2.3.2 | Requirements for FR2-1..... | 220 | +| 12.4B.2.4 | Measurement Reporting Requirements..... | 220 | +| 12.4B.2.4.1 | Periodic Reporting..... | 220 | +| 12.4B.2.4.2 | Event-triggered Periodic Reporting..... | 220 | +| 12.4B.2.4.3 | Event Triggered Reporting..... | 220 | +| 12.4B.2.5 | Intrafrequency measurements without measurement gaps..... | 221 | +| 12.4B.2.5.1 | Intrafrequency cell identification..... | 221 | +| 12.4B.2.5.2 | Measurement period..... | 222 | +| 12.4B.3 | L1-RSRP measurements for Reporting..... | 222 | +| 12.4B.3.1 | Introduction..... | 222 | +| 12.4B.3.2 | Requirements applicability..... | 223 | +| 12.4B.3.3 | Measurement Reporting Requirements..... | 223 | +| 12.4B.3.3.1 | Periodic Reporting..... | 223 | +| 12.4B.3.3.2 | Semi-Persistent Reporting..... | 223 | +| 12.4B.3.3.3 | Aperiodic Reporting..... | 224 | +| 12.4B.3.4 | L1-RSRP measurement requirements..... | 224 | +| 12.4B.3.4.1 | SSB based L1-RSRP Reporting..... | 224 | +| 12.4B.3.4.2 | CSI-RS based L1-RSRP Reporting..... | 225 | + +**Annex A (normative): IAB-MT Reference measurement channels.....227** + +| | | | +|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| A.1 | Fixed Reference Channels for reference sensitivity level, ACS, in-band blocking, out-of-band blocking and receiver intermodulation (QPSK, R=1/3)..... | 227 | +| A.2 | IAB-DU Fixed Reference Channels..... | 227 | +| A.2.1 | Fixed Reference Channels for PUSCH performance requirements (QPSK, R=193/1024)..... | 227 | +| A.2.2 | Fixed Reference Channels for PUSCH performance requirements (16QAM, R=434/1024)..... | 232 | +| A.2.3 | Fixed Reference Channels for PUSCH performance requirements (16QAM, R=658/1024)..... | 233 | +| A.2.4 | Fixed Reference Channels for PUSCH performance requirements (64QAM, R=567/1024)..... | 236 | +| A.2.5 | PRACH Test preambles..... | 238 | + +| | | | +|-----------------------------|------------------------------------------------------------------------------------------------|------------| +| A.3 | IAB-MT Fixed Reference Channels..... | 238 | +| A.3.1 | Fixed Reference Channels for PDSCH performance requirements (16QAM)..... | 238 | +| A.3.2 | Fixed Reference Channels for PDSCH performance requirements (64QAM)..... | 239 | +| A.3.3 | Fixed Reference Channels for PDSCH performance requirements (256QAM)..... | 240 | +| A.3.4 | Fixed Reference Channels for PDCCH performance requirements..... | 241 | +| A.3.5 | Fixed Reference Channels for CSI reporting performance..... | 242 | +| Annex B (normative): | IAB-DU Error Vector Magnitude (FR1)..... | 244 | +| Annex C (normative): | IAB-DU Error Vector Magnitude (FR2-1)..... | 244 | +| Annex D (normative): | IAB-MT Error Vector Magnitude (FR1)..... | 244 | +| D.0 | General..... | 244 | +| D.1 | Reference point for measurement..... | 244 | +| D.2 | Basic unit of measurement..... | 244 | +| D.3 | Modified signal under test..... | 245 | +| D.4 | Estimation of frequency offset..... | 245 | +| D.5 | Estimation of time offset..... | 245 | +| D.6 | Estimation of TX chain amplitude and frequency response parameters..... | 245 | +| D.7 | Averaged EVM..... | 245 | +| Annex E (normative): | IAB-MT Error Vector Magnitude (FR2)..... | 246 | +| E.0 | General..... | 246 | +| E.1 | Reference point for measurement..... | 246 | +| E.2 | Basic unit of measurement..... | 246 | +| E.3 | Modified signal under test..... | 246 | +| E.4 | Estimation of frequency offset..... | 246 | +| E.5 | Estimation of time offset..... | 246 | +| E.6 | Estimation of TX chain amplitude and frequency response parameters..... | 246 | +| E.7 | Averaged EVM..... | 246 | +| Annex F (normative): | 247 | | +| F.1 | Characteristics of the interfering signals for IAB-DU..... | 247 | +| F.2 | Characteristics of the interfering signals for IAB-MT..... | 247 | +| Annex G (normative): | IAB-MT RRM Testing..... | 247 | +| G.1 | IAB-MT RRM test configurations..... | 249 | +| G.1.1 | Reference measurement channels..... | 249 | +| G.1.1.1 | PDSCH..... | 249 | +| G.1.1.1.1 | TDD..... | 249 | +| G.1.1.2 | CORESET for RMSI scheduling..... | 252 | +| G.1.1.2.1 | TDD..... | 252 | +| G.1.1.3 | CORESET for RMC scheduling..... | 255 | +| G.1.1.3.1 | TDD..... | 255 | +| G.1.2 | OFDMA channel noise generator (OCNG)..... | 256 | +| G.1.2.1 | Generic OFDMA Channel Noise Generator (OCNG)..... | 256 | +| G.1.2.1.1 | OCNG pattern 1: Generic OCNG pattern for all unused REs..... | 256 | +| G.1.2.1.2 | OCNG pattern 2: Generic OCNG pattern for all unused REs for 2AoA setup..... | 257 | +| G.1.2.1.3 | OCNG pattern 3: Generic OCNG pattern for unused REs in the same bandwidth as PDSCH
RMC..... | 257 | +| G.1.2.1.4 | OCNG pattern 4: Generic OCNG pattern for all unused REs outside SSB slot(s)..... | 258 | +| G.1.3 | Antenna configurations..... | 258 | +| G.1.3.1 | Antenna configurations for FR1..... | 258 | +| G.1.3.1.1 | Antenna connection for 4 Rx capable IAB-MT..... | 258 | +| G.1.3.2 | Antenna configurations for FR2-1..... | 259 | +| G.1.4 | BWP configurations..... | 259 | +| G.1.4.1 | Introduction..... | 259 | +| G.1.4.2 | Downlink BWP configurations..... | 260 | +| G.1.4.2.1 | Initial BWP..... | 260 | + +| | | | +|------------|--------------------------------------------------------------------------------------------------------------|-----| +| G.1.4.2.2 | Dedicated BWP..... | 260 | +| G.1.4.3 | Uplink BWP configurations..... | 260 | +| G.1.4.3.1 | Initial BWP..... | 260 | +| G.1.4.3.2 | Dedicated BWP..... | 261 | +| G.1.5 | SSB Configurations..... | 261 | +| G.1.5.1 | SSB Configurations for FR1..... | 261 | +| G.1.5.1.1 | SSB pattern 1 in FR1: SSB allocation for SSB SCS=15 kHz..... | 261 | +| G.1.5.1.2 | SSB pattern 2 in FR1: SSB allocation for SSB SCS=30 kHz..... | 261 | +| G.1.5.1.3 | SSB pattern 3 in FR1: SSB allocation for SSB SCS=15 kHz..... | 262 | +| G.1.5.1.4 | SSB pattern 4 in FR1: SSB allocation for SSB SCS=30 kHz..... | 262 | +| G.1.5.1.5 | SSB pattern 5 in FR1: SSB allocation for SSB SCS=15 kHz starting from odd SFN..... | 262 | +| G.1.5.1.6 | SSB pattern 6 in FR1: SSB allocation for SSB SCS=30 kHz starting from odd SFN..... | 263 | +| G.1.5.2 | SSB Configurations for FR2-1..... | 263 | +| G.1.5.2.1 | SSB pattern 1 in FR2-1: SSB allocation for SSB SCS=120 kHz..... | 263 | +| G.1.5.2.2 | SSB pattern 2 in FR2: SSB allocation for SSB SCS=240 kHz..... | 263 | +| G.1.5.2.3 | SSB pattern 3 in FR2-1: SSB allocation for SSB SCS=120 kHz..... | 264 | +| G.1.5.2.4 | SSB pattern 4 in FR2-1: SSB allocation for SSB SCS=240 kHz..... | 264 | +| G.1.5.2.5 | SSB pattern 5 in FR2-1: SSB allocation for SSB SCS=120 kHz..... | 264 | +| G.1.5.2.6 | SSB pattern 6 in FR2-1: SSB allocation for SSB SCS=240 kHz..... | 265 | +| G.1.5.2.7 | SSB pattern 7 in FR2-1: SSB allocation for SSB SCS=120 kHz..... | 265 | +| G.1.5.2.8 | SSB pattern 8 in FR2-1: SSB allocation for SSB SCS=240 kHz..... | 265 | +| G.1.6 | SMTC Configurations..... | 266 | +| G.1.6.1 | SMTC pattern 1: SMTC period = 20 ms with SMTC duration = 1 ms..... | 266 | +| G.1.6.2 | SMTC pattern 2: SMTC period = 20 ms with SMTC duration = 5 ms..... | 266 | +| G.1.6.3 | SMTC pattern 3: SMTC period = 160 ms with SMTC duration = 1 ms..... | 266 | +| G.1.6.4 | SMTC pattern 4: SMTC period = 20 ms with SMTC duration = 1 ms..... | 266 | +| G.1.6.5 | SMTC pattern 5: SMTC period = 20 ms with SMTC duration = 5 ms..... | 266 | +| G.1.7 | CSI-RS configurations..... | 267 | +| G.1.7.1 | TDD..... | 267 | +| G.1.8 | Angle of Arrival (AoA) for FR2-1 RRM test cases..... | 269 | +| G.1.8.1 | Setup 1: Single AoA..... | 269 | +| G.1.8.2 | Setup 2: 2 AoAs..... | 269 | +| G.1.9 | TCI State Configuration..... | 270 | +| G.1.9.1 | Introduction..... | 270 | +| G.1.9.2 | TCI states..... | 270 | +| G.1.10 | Configurations of CSI-RS for tracking..... | 270 | +| G.1.10.1 | Configuration of CSI-RS for tracking for FR1..... | 270 | +| G.1.10.1.2 | TDD..... | 270 | +| G.1.10.2 | Configuration of CSI-RS for tracking for FR2-1..... | 271 | +| G.1.10.2.1 | TDD..... | 271 | +| G.2 | IAB-MT RRM test cases..... | 272 | +| G.2.1 | RRC_CONNECTED state mobility for IAB-MTs..... | 272 | +| G.2.1.1 | RRC Connection Mobility Control..... | 272 | +| G.2.1.1.1 | RRC Re-establishment..... | 272 | +| G.2.1.1.2 | RRC Connection Release with Redirection..... | 283 | +| G.2.2 | Timing..... | 288 | +| G.2.2.1 | Transmit timing..... | 288 | +| G.2.2.1.1 | NR IAB-MT Transmit Timing Test for FR1..... | 288 | +| G.2.2.1.2 | NR IAB-MT Transmit Timing Test for FR2-1..... | 291 | +| G.2.3 | Signalling Characteristics for IAB MTs..... | 294 | +| G.2.3.1 | Radio link Monitoring..... | 294 | +| G.2.3.1.1 | Radio Link Monitoring Out-of-sync Test for FR1 PCell configured with SSB-based RLM RS in non-DRX mode..... | 294 | +| G.2.3.1.2 | Radio Link Monitoring In-sync Test for FR1 PCell configured with SSB-based RLM RS in non-DRX mode..... | 297 | +| G.2.3.1.3 | Radio Link Monitoring Out-of-sync Test for FR2-1 PCell configured with SSB-based RLM RS in non-DRX mode..... | 301 | +| G.2.3.1.4 | Radio Link Monitoring In-sync Test for FR2-1 PCell configured with SSB-based RLM RS in non-DRX mode..... | 304 | +| G.2.3.1.5 | Radio Link Monitoring Out-of-sync Test for FR1 PCell configured with CSI-RS-based RLM in non-DRX mode..... | 308 | + +| | | | +|-----------|----------------------------------------------------------------------------------------------------------------------------|-----| +| G.2.3.1.6 | Radio Link Monitoring In-sync Test for FR1 PCell configured with CSI-RS-based RLM in non-DRX mode..... | 311 | +| G.2.3.1.7 | Radio Link Monitoring Out-of-sync Test for FR2-1 PCell configured with CSI-RS-based RLM in non-DRX mode..... | 314 | +| G.2.3.1.8 | Radio Link Monitoring In-sync Test for FR2-1 PCell configured with CSI-RS-based RLM in non-DRX mode..... | 317 | +| G.2.3.2 | Beam Failure Detection and Link Recovery Procedure..... | 320 | +| G.2.3.2.1 | Beam Failure Detection and Link Recovery Test for FR1 PCell configured with SSB-based BFD and LR..... | 320 | +| G.2.3.2.2 | Beam Failure Detection and Link Recovery Test for FR2-1 PCell configured with SSB-based BFD and LR..... | 324 | +| G.2.3.2.3 | Beam Failure Detection and Link Recovery Test for FR1 PCell configured with CSI-RS-based BFD and LR..... | 330 | +| G.2.3.2.4 | Beam Failure Detection and Link Recovery Test for FR2-1 PCell configured with CSI-RS-based BFD and LR in non-DRX mode..... | 334 | + +**Annex H (normative): Conditions for IAB-MT RRM requirements applicability for operating bands.....339** + +| | | | +|---------|--------------------------------------------------------------------------------------------------|-----| +| H.1 | Conditions for RRC_CONNECTED state mobility for IAB-MT..... | 339 | +| H.1.1 | Introduction..... | 339 | +| H.1.1.1 | Conditions for Measurements on NR Intra-frequency Cells for RRC Connection Re-establishment..... | 340 | +| H.1.1.2 | Conditions for Measurements on NR Inter-frequency Cells for RRC Connection Re-establishment..... | 341 | +| H.1.1.3 | Conditions for Measurements on NR Cells for RRC Connection Release with Redirection..... | 342 | + +**Annex I (normative): Propagation conditions.....343** + +| | | | +|-----------|-----------------------------------------------------------------------------|-----| +| I.1 | Static propagation condition..... | 343 | +| I.1.1 | IAB-MT receiver with 2RX..... | 343 | +| I.2 | Multi-path fading propagation conditions..... | 344 | +| I.2.1 | General..... | 344 | +| I.2.2 | Delay profiles..... | 344 | +| I.2.2.1 | General..... | 344 | +| I.2.2.2 | Delay profiles for FR1..... | 345 | +| I.2.3 | Combinations of channel model parameters..... | 346 | +| I.2.4 | MIMO channel correlation matrices..... | 347 | +| I.2.4.1 | General..... | 347 | +| I.2.4.2 | MIMO correlation matrices using Uniform Linear Array..... | 347 | +| I.2.4.2.1 | General..... | 347 | +| I.2.4.2.2 | Definition of MIMO correlation matrices..... | 347 | +| I.2.4.2.3 | MIMO correlation matrices at high, medium and low level..... | 348 | +| I.2.4.3 | Multi-antenna channel models using cross polarized antennas..... | 350 | +| I.2.4.3.1 | General..... | 350 | +| I.2.4.3.2 | Definition of MIMO correlation matrices using cross polarized antennas..... | 351 | +| I.2.4.3.3 | Spatial correlation matrices at IAB-MT/UE and IAB-DU/gNB sides..... | 351 | +| I.2.4.3.4 | MIMO correlation matrices using cross polarized antennas..... | 352 | +| I.2.4.3.5 | Beam steering approach..... | 352 | +| I.3 | Physical signals, channels mapping and precoding..... | 354 | +| I.3.1 | General..... | 354 | + +**Annex J (informative): Change history.....356** + +--- + +## 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, certain modal verbs have the following meanings: + +**shall** indicates a mandatory requirement to do something + +**shall not** indicates an interdiction (prohibition) to do something + +NOTE 1: The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +NOTE 2: The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +**should** indicates a recommendation to do something + +**should not** indicates a recommendation not to do something + +**may** indicates permission to do something + +**need not** indicates permission not to do something + +NOTE 3: The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +**can** indicates that something is possible + +**cannot** indicates that something is impossible + +NOTE 4: The constructions "can" and "cannot" shall not to be used as substitutes for "may" and "need not". + +**will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document + +**will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document + +**might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +NOTE 5: The constructions "is" and "is not" do not indicate requirements. + +# 1 Scope + +The present document establishes the minimum RF characteristics, minimum radio resource management (RRM) requirements, RRM test cases and minimum performance requirements of NR Integrated access and backhaul (IAB). + +# 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.101-1: "NR User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone" +- [4] 3GPP TS 38.101-2: "NR User Equipment (UE) radio transmission and reception: Part 2: Range 2 Standalone" +- [5] 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 " +- [6] 3GPP TS 38.133: "NR: Requirements for support of radio resource management" +- [7] 3GPP TS 38.300: "NR; Overall description; Stage-2". +- [8] 3GPP TS 38.211: "NR; Physical channels and modulation". +- [9] 3GPP TS 38.212 "NR; Multiplexing and channel coding". +- [10] 3GPP TS 38.213: "NR; Physical layer procedures for control". +- [11] 3GPP TS 38.214: "NR; Physical layer procedures for data". +- [12] 3GPP TS 38.215: "NR; Physical layer measurements". +- [13] 3GPP TS 38.304: "NR; User Equipment (UE) procedures in idle mode". +- [14] 3GPP TS 38.321: "NR; Medium Access Control (MAC) protocol specification". +- [15] 3GPP TS 38.331: "NR; Radio Resource Control (RRC); Protocol specification". +- [16] ITU-R Recommendation SM.329: "Unwanted emissions in the spurious domain". +- [17] ERC Recommendation 74-01, "Unwanted emissions in the spurious domain". +- [18] ITU-R Recommendation M.1545: "Measurement uncertainty as it applies to test limits for the terrestrial component of International Mobile Telecommunications – 2000" +- [19] Recommendation ITU-R SM.328: "Spectra and bandwidth of emissions". +- [20] "Title 47 of the Code of Federal Regulations (CFR)", Federal Communications Commission. + +- [21] 3GPP TS 38.141-2: "NR; Base Station (BS) conformance testing; Part 2: Radiated conformance testing". +- [22] 3GPP TS 38.141-1: "NR; Base Station (BS) conformance testing; Part 1: Conducted conformance testing". +- [23] 3GPP TS 38.521-1: "NR; User Equipment (UE) conformance specification; Radio transmission and reception; Part 1: Range 1 Standalone". +- [24] 3GPP TS 38.521-2: "NR; User Equipment (UE) conformance specification; Radio transmission and reception; Part 2: Range 2 Standalone". +- [25] 3GPP TS 38.176-1: "NR; Integrated Access and Backhaul (IAB) conformance testing; Part 1: Conducted conformance testing". +- [26] 3GPP TS 38.176-2: "NR; Integrated Access and Backhaul (IAB) conformance testing; Part 2: Radiated conformance testing". +- [27] 3GPP TR 38.901: "Study on channel model for frequencies from 0.5 to 100 GHz" +- [28] 3GPP TR 38.101-4: " NR; User Equipment (UE) radio transmission and reception; Part 4: Performance requirements" +- [29] 3GPP TS 38.300: "NR; NR and NG-RAN Overall description; Stage-2". + +--- + +## 3 Definitions, symbols and abbreviations + +### 3.1 Definitions + +For the purposes of the present document, the terms 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. + +**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 + +**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-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 + +**BS type 2-O:** NR base station operating at FR2 with a *requirement set* consisting only of OTA requirements defined at the RIB + +**Channel edge:** lowest or highest frequency of the NR carrier, separated by the *IAB-MT channel bandwidth* or *IAB-DU 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 IAB-DU or IAB-MT aggregates carriers with a specific set of technical requirements + +**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 + +**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 UE bandwidth parts that are smaller than or equal to the *IAB transmission bandwidth configuration*, in any part of the *IAB transmission bandwidth configuration*. + +**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-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 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 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-MT RF Bandwidth edge:** frequency of one of the edges of the *IAB-MT RF Bandwidth*. + +**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 + +**Mobile IAB-node:** Mobile IAB-node as defined in TS 38.300 [29] + +**Mobile IAB-DU:** IAB-DU function on the mobile IAB-node as defined in TS 38.300 [29] + +**Mobile IAB-MT:** IAB-MT function on the mobile IAB-node as defined in TS 38.300 [29] +**Mobile IAB type 1-H:** Mobile IAB-MT operating at FR1 with a *requirement set* consisting of conducted requirements defined at individual *TAB connectors* and OTA requirements defined at RIB + +**Mobile IAB-MT type 1-O:** Mobile IAB-MT operating at FR1 with a *requirement set* consisting only of OTA requirements defined at the RIB + +**Mobile IAB-MT type 2-O:** Mobile IAB-MT operating at FR2 with a *requirement set* consisting only of OTA requirements defined at the RIB + +**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 REFSSENS 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, 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 *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 | +| $BeW_{\theta,REFSENS}$ | Beamwidth equivalent to the OTA REFSENS RoAoA in the $\theta$ -axis in degrees. Applicable for FR1 only. | +| $BeW_{\phi,REFSENS}$ | Beamwidth equivalent to the OTA REFSENS RoAoA in the $\phi$ -axis in degrees. Applicable for FR1 only. | +| $BW_{Channel}$ | BS channel bandwidth | +| $BW_{Channel\_CA}$ | Aggregated BS Channel Bandwidth , expressed in MHz. $BW_{Channel\_CA} = F_{edge,high} - F_{edge,low}$ . | +| $BW_{Config}$ | Transmission bandwidth configuration , where $BW_{Config} = N_{RB} \times SCS \times 12$ | +| $BW_{Contiguous}$ | Contiguous transmission bandwidth , i.e. BS channel bandwidth for single carrier or Aggregated BS channel bandwidth for contiguously aggregated carriers. For non-contiguous operation within a band the term is applied per sub-block . | +| $\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_{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 downlink operating band edge | +| $\Delta f_{OOB}$ | Maximum offset of the out-of-band boundary from the uplink operating band edge | +| $\Delta f_{FR2\_REFSENS}$ | Offset applied to the FR2 OTA REFSENS depending on the AoA | +| $\Delta f_{minSENS}$ | Difference between conducted reference sensitivity and minSENS | +| $\Delta f_{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 BS channel bandwidth | +| $\hat{E}_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 TAB connector or RIB | +| $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 BS Channel Bandwidth , expressed in MHz. $F_{edge,low} = F_{C,low} - F_{offset,low}$ . | +| $F_{edge,high}$ | The upper edge of Aggregated BS 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\_offset_{max}$ | The offset to the frequency $\Delta 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_{Io}$ | The total received power density, including signal and interference, as measured at the IAB-MT TAB connector or RIB. | +| $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 TAB connector or RIB. | +| $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 TAB connector or RIB | + +| | | +|---------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 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 TAB connector or RIB | +| $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{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 | +| | Timing offset between uplink and downlink radio frames at the UE / IAB-MT, as defined in clause 4.2.3 in TS 38.213 | +| $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{CMAX},f,c}$ | The configured maximum output power for carrier f of serving cell c in each slot | +| $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 NR BS 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 | +| $\text{SSB\_RP}$ | Received (linear) average power of the resource elements that carry SSB signals and channels, measured at the IAB-MT TAB connector or RIB | +| $T_c$ | Basic time unit, defined in clause 4.1 of TS 38.211 [8] | +| $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 | +| mIAB | Mobile IAB | +| 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 IAB-MT TAB connector or RIB. | +| 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 + +### 4.1 Relationship with other core specifications + +The present document is a single-RAT specification for an IAB-DU and IAB-MT, covering RF characteristics and minimum performance requirements and RRM requirements for the IAB-MT. Conducted and radiated core requirements are defined for the IAB node architectures and IAB node types defined in subclause 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.176-1 [25] and TS 38.176-2 [26]. + +The minimum requirements given in this specification make no allowance for measurement uncertainty. The test specifications TS 38.176-1 [25] and TS 38.176-2 [26] 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 [18]. + +### 4.3 Conducted and radiated requirement reference points + +### 4.3.2 IAB type 1-H + +For *IAB type 1-H*, the requirements are defined for two points of reference, signified by radiated requirements and conducted requirements. + +![Diagram of radiated and conducted reference points for IAB type 1-H. It shows a Transceiver unit array (TRXUA) on the left, connected via multiple lines (labeled #1, #2, ..., #K) to a Composite antenna on the right. The Composite antenna contains a Radio Distribution Network (RDN) and an Antenna Array (AA). A vertical dashed line labeled 'Transceiver array boundary' is positioned between the TRXUA and the Composite antenna. A vertical dashed line labeled 'Radiated interface boundary' is positioned to the right of the Composite antenna. An arrow points to one of the connection points on the Transceiver array boundary, labeled 'Transceiver array boundary connector (TAB)'.](759c7d62402f0b4651ddce292be5bdef_img.jpg) + +Diagram of radiated and conducted reference points for IAB type 1-H. It shows a Transceiver unit array (TRXUA) on the left, connected via multiple lines (labeled #1, #2, ..., #K) to a Composite antenna on the right. The Composite antenna contains a Radio Distribution Network (RDN) and an Antenna Array (AA). A vertical dashed line labeled 'Transceiver array boundary' is positioned between the TRXUA and the Composite antenna. A vertical dashed line labeled 'Radiated interface boundary' is positioned to the right of the Composite antenna. An arrow points to one of the connection points on the Transceiver array boundary, labeled 'Transceiver array boundary connector (TAB)'. + +**Figure 4.3.2-1: Radiated and conducted reference points for IAB 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. + +Conducted characteristics are defined at individual or groups of *TAB connectors* at the *transceiver array boundary*, which is the conducted interface between the transceiver unit array and the composite antenna. + +The transceiver unit array is part of the composite transceiver functionality generating modulated transmit signal structures and performing receiver combining and demodulation. + +The transceiver unit array contains an implementation specific number of transmitter units and an implementation specific number of receiver units. Transmitter units and receiver units may be combined into transceiver units. The transmitter/receiver units have the ability to transmit/receive parallel independent modulated symbol streams. + +The composite antenna contains a radio distribution network (RDN) and an antenna array. The RDN is a linear passive network which distributes the RF power generated by the transceiver unit array to the antenna array, and/or distributes the radio signals collected by the antenna array to the transceiver unit array, in an implementation specific way. + +How a conducted requirement is applied to the *transceiver array boundary* is detailed in the respective requirement subclause. + +### 4.3.3 IAB type 1-O and IAB type 2-O + +For *IAB type 1-O* and *IAB type 2-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. + +![Diagram of radiated reference points for IAB type 1-O and IAB type 2-O. It shows three main components enclosed in dashed boxes: 'Transceiver unit array (TRXUA) 1 to P', 'Radio Distribution Network (RDN)', and 'Antenna Array (AA)'. These components are grouped together by a larger dashed box. To the right of the Antenna Array is a vertical dashed line labeled 'Radiated interface boundary'.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +Diagram of radiated reference points for IAB type 1-O and IAB type 2-O. It shows three main components enclosed in dashed boxes: 'Transceiver unit array (TRXUA) 1 to P', 'Radio Distribution Network (RDN)', and 'Antenna Array (AA)'. These components are grouped together by a larger dashed box. To the right of the Antenna Array is a vertical dashed line labeled 'Radiated interface boundary'. + +**Figure 4.3.3-1: Radiated reference points for IAB type 1-O and IAB type 2-O** + +For an *IAB-DU type 1-O* the transceiver unit array must contain at least 8 transmitter units and at least 8 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. + +## 4.4 IAB classes + +### 4.4.1 IAB-DU classes + +The requirements in this specification 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. + +For IAB *type 1-H*, 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 coupling loss equal to 70 dB. +- Medium Range IAB-DU are characterised by requirements derived from Micro Cell scenarios with a BS to UE minimum coupling loss equals to 53 dB. +- Local Area IAB-DU are characterised by requirements derived from Pico Cell scenarios with a BS to UE minimum coupling loss equal to 45 dB. + +### 4.4.2 IAB-MT classes + +The requirements in this specification apply to Wide Area IAB-MT and Local Area IAB-MT classes unless otherwise stated. + +For IAB *type 1-H*, 1-O, and 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.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 | 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. | +| 6.6.2,
9.7.2 | Occupied bandwidth,
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. | +| 6.6.4.2,
9.7.4.2
9.7.4.3 | Operating band unwanted emission,
OTA operating band unwanted emissions | Category A or Category B operating band unwanted emissions limits may be applied regionally. | +| 6.6.4.2.5.1,
9.7.4.4.1 | Operating band unwanted emission,
OTA operating band unwanted emissions:
Limits in FCC Title 47 | 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. | +| 6.6.5.2.1,
9.7.5.2.2
9.7.5.3.2 | Tx spurious emissions,
OTA Tx spurious emissions | Category A or Category B spurious emission limits, as defined in ITU-R Recommendation SM.329 [2], may apply regionally.
The emission limits for IAB type 1-H and IAB type 1-O specified as the basic limit + X (dB) are applicable, unless stated differently in regional regulation. | +| 6.6.5.2.2,
9.7.5.2.3
9.7.5.3.3 | Tx spurious emissions:
additional requirements,
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 . | +| 6.7.2.1,
9.8.2 | Transmitter intermodulation,
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. | +| 7.6.2,
7.6.3
10.7.2
10.7.3 | Rx spurious emissions,
OTA Rx spurious emissions | The emission limits for IAB type 1-H and IAB type 1-O specified as the basic limit + X (dB) are applicable, unless stated differently in regional regulation. | + +## 4.6 Applicability of requirements + +In table 4.6-1, the requirement applicability for each *requirement set* of IAB-DUs is defined. In table 4.6-2, the requirement applicability for each *requirement set* of IAB-MTs 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 for IAB-DUs** + +| Requirement | IAB-DU type 1-H | IAB-DU type 1-O | IAB-DU type 2-O | +|--------------------------------------|-------------------------------|-------------------------------|-------------------------------| +| Output power | 6.2 | NA | NA | +| Output power dynamics | 6.3 | | | +| Transmit ON/OFF power | 6.4 | | | +| Transmitted signal quality | 6.5 | | | +| Occupied bandwidth | 6.6.2 | | | +| ACLR | 6.6.3 | | | +| Operating band unwanted emissions | 6.6.4 | | | +| Transmitter spurious emissions | 6.6.5 | | | +| Transmitter intermodulation | 6.7 | | | +| Reference sensitivity level | 7.2 | | | +| Dynamic range | 7.3 | | | +| In-band selectivity and blocking | 7.4 | | | +| Out-of-band blocking | 7.5 | | | +| Receiver spurious emissions | 7.6 | | | +| Receiver intermodulation | 7.7 | | | +| In-channel selectivity | 7.8 | | | +| Performance requirements | 8 | | | +| Radiated transmit power | 9.2 | 9.2 | 9.2 | +| OTA Output power | NA | 9.3 | 9.3 | +| OTA output power dynamics | | 9.4 | 9.4 | +| OTA transmit ON/OFF power | | 9.5 | 9.5 | +| OTA transmitted signal quality | | 9.6 | 9.6 | +| OTA occupied bandwidth | | 9.7.2 | 9.7.2 | +| OTA ACLR | | 9.7.3 | 9.7.3 | +| OTA out-of-band emission | | 9.7.4 | 9.7.4 | +| OTA transmitter spurious emission | | 9.7.5 | 9.7.5 | +| OTA transmitter intermodulation | | 9.8 | NA | +| OTA sensitivity | 10.2 | 10.2 | NA | +| OTA reference sensitivity level | NA | 10.3 | 10.3 | +| OTA dynamic range | | 10.4 | NA | +| OTA in-band selectivity and blocking | | 10.5 | 10.5 | +| OTA out-of-band blocking | | 10.6 | 10.6 | +| OTA receiver spurious emission | | 10.7 | 10.7 | +| OTA receiver intermodulation | | 10.8 | 10.8 | +| OTA in-channel selectivity | | 10.9 | 10.9 | +| Radiated performance requirements | | 11 | 11 | + +**Table 4.6-2: Requirement set applicability for IAB-MTs** + +| Requirement | IAB-MT type 1-
H | IAB-MT type 1-
O | IAB-MT type 2-
O | +|--------------------------------------|---------------------|---------------------|---------------------| +| Output power | 6.2 | NA | NA | +| Output power dynamics | 6.3 | | | +| Transmit ON/OFF power | 6.4 | | | +| Transmitted signal quality | 6.5 | | | +| Occupied bandwidth | 6.6.2 | | | +| ACLR | 6.6.3 | | | +| Operating band unwanted emissions | 6.6.4 | | | +| Transmitter spurious emissions | 6.6.5 | | | +| Transmitter intermodulation | 6.7 | | | +| Reference sensitivity level | 7.2 | | | +| Dynamic range | NA | | | +| In-band selectivity and blocking | 7.4 | | | +| Out-of-band blocking | 7.5 | | | +| Receiver spurious emissions | 7.6 | | | +| Receiver intermodulation | 7.7 | | | +| In-channel selectivity | NA | | | +| Performance requirements | 8 | | | +| Radiated transmit power | 9.2 | 9.2 | 9.2 | +| OTA Output power | NA | 9.3 | 9.3 | +| OTA output power dynamics | | 9.4 | 9.4 | +| OTA transmit ON/OFF power | | 9.5 | 9.5 | +| OTA transmitted signal quality | | 9.6 | 9.6 | +| OTA occupied bandwidth | | 9.7.2 | 9.7.2 | +| OTA ACLR | | 9.7.3 | 9.7.3 | +| OTA out-of-band emission | | 9.7.4 | 9.7.4 | +| OTA transmitter spurious emission | | 9.7.5 | 9.7.5 | +| OTA transmitter intermodulation | | 9.8 | NA | +| OTA sensitivity | 10.2 | 10.2 | NA | +| OTA reference sensitivity level | NA | 10.3 | 10.3 | +| OTA dynamic range | | NA | NA | +| OTA in-band selectivity and blocking | | 10.5 | 10.5 | +| OTA out-of-band blocking | | 10.6 | 10.6 | +| OTA receiver spurious emission | | 10.7 | 10.7 | +| OTA receiver intermodulation | | 10.8 | NA | +| OTA in-channel selectivity | | NA | NA | +| Radiated performance requirements | | 11 | 11 | + +## 4.7 Applicability of RRM requirements in this specification + +### 4.7.1 Applicability of signalling characteristics related RRM requirements + +The RRM requirements on the signalling characteristics for IAB MTs specified in section 12.3 shall apply only for the local area IAB class defined in section 4.4. + +### 4.7.2 Applicability of RRM requirements in non-DRX + +All the RRM requirements for IAB MT specified in section 12 shall apply when no DRX is used. The IAB-MT shall assume that no DRX is used provided the following conditions are met: + +- DRX parameters are not configured or +- DRX parameters are configured and + - drx-InactivityTimer is running or + +- drx-RetransmissionTimerDL is running or +- drx-RetransmissionTimerUL is running or +- ra-ContentionResolutionTimer is running or +- a Scheduling Request sent on PUCCH is pending or +- a PDCCH indicating a new transmission addressed to the C-RNTI of the MAC entity has not been received after successful reception of a Random Access Response for the preamble not selected by the MAC entity + +## 4.8 Requirements for contiguous and non-contiguous spectrum + +A spectrum allocation where an IAB-DU or IAB-MT operates can either be contiguous or non-contiguous. Unless otherwise stated, the requirements in the present specification apply for IAB-DU and IAB-MT configured for both *contiguous spectrum* operation and *non-contiguous spectrum* operation. + +For IAB-DU or IAB-MT 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* and *IAB-MT RF Bandwidth edges* and the *sub-block edges* respectively. + +## 4.9 Requirements for IAB-DU and IAB-MT capable of multi-band operation + +For *multi-band connector* or *multi-band RIB*, the RF requirements in clause 6, 7, 9 and 10 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 connector(s)*, and *multi-band RIB(s)* as detailed in the requirement clause. For *IAB-DU* or *IAB-MT* 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 *TAB connectors* for *IAB-DU* or *IAB-MT 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 IAB-DU or IAB-MT 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 *IAB-DU* or *IAB-MT* are applicable. Single-band requirements are tested separately at the *connector* configured for single-band operation, with all other *antenna connectors* terminated. + +A *IAB-DU* or *IAB-MT 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 *IAB-DU type 1-H* capability of operation in multiple *operating bands*. + +Unless otherwise stated all requirements specified for an *operating band* apply only to the set of *TAB connectors* supporting that *operating band*. + +In 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*. + +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. + +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. + +*IAB-DU* or *IAB-MT type 1-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-DU* or *IAB-MT type 1-O* capability of operation in multiple *operating bands*. + +For *multi-band connectors* and *multi-band RIBs* supporting the bands for TDD, the RF requirements in the present specification assume no simultaneous uplink and downlink occur between the bands. + +## 4.10 OTA co-location with other base stations + +Co-location requirements are requirements which are based on assuming the *IAB-DU* or *IAB-MT 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. + +Unwanted emission and out of band blocking co-location requirements are optional requirements based on declaration. TX OFF and TX IMD are mandatory requirements and have the form of a co-location requirement as it represents the worst-case scenario of all the interference cases. + +NOTE: Due to the low level of the unwanted emissions for the spurious emissions and TX OFF level co-location is the most suitable method to show conformance. + +The *co-location reference antenna* shall be a single column passive antenna which has the same vertical radiating dimension ( $h$ ), frequency range, polarization, as the composite antenna of the *IAB-DU* or *IAB-MT type 1-O* and nominal $65^\circ$ horizontal half-power beamwidth (suitable for 3-sector deployment) and is placed at a distance $d$ from the edge of the *IAB-DU* or *IAB-MT type 1-O*, as shown in figure 4.10-1. + +![Figure 4.10-1: Illustration of IAB-DU and IAB-MT type 1-O enclosure and co-location reference antenna. The diagram shows two views: Front View and Top View. In the Front View, an 'Enclosure' (labeled IAB-DU or IAB-MT type 1-O) and a 'Co-location Reference antenna' are shown as vertical rectangles. The distance between their inner edges is labeled 'd'. The height of the reference antenna is labeled 'h'. In the Top View, the 'Radiating face' of the enclosure and the 'Radiating face' of the reference antenna are shown as semi-circular shapes. The distance between their flat edges is labeled 'd'. A dashed horizontal line separates the two views.](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +Figure 4.10-1: Illustration of IAB-DU and IAB-MT type 1-O enclosure and co-location reference antenna. The diagram shows two views: Front View and Top View. In the Front View, an 'Enclosure' (labeled IAB-DU or IAB-MT type 1-O) and a 'Co-location Reference antenna' are shown as vertical rectangles. The distance between their inner edges is labeled 'd'. The height of the reference antenna is labeled 'h'. In the Top View, the 'Radiating face' of the enclosure and the 'Radiating face' of the reference antenna are shown as semi-circular shapes. The distance between their flat edges is labeled 'd'. A dashed horizontal line separates the two views. + +**Figure 4.10-1: Illustration of IAB-DU and IAB-MT type 1-O enclosure and co-location reference antenna** + +Edge-to-edge separation $d$ between the *IAB-DU or IAB-MT type 1-O* and the *co-location reference antenna* shall be set to 0.1 m. + +The *IAB-DU or IAB-MT type 1-O* and the *co-location reference antenna* shall be aligned in a common plane perpendicular to the mechanical bore-sight direction, as shown in figure 4.10-1. + +The *co-location reference antenna* and the *IAB-DU or IAB-MT type 1-O* can have different width. + +The vertical radiating regions of the *co-location reference antenna* and the *IAB-DU or IAB-MT type 1-O* composite antenna shall be aligned. + +For co-location requirements where the frequency range of the signal at the *co-location reference antenna* is different from the *IAB-DU or IAB-MT type 1-O*, a *co-location reference antenna* suitable for the frequency stated in the requirement is assumed. + +OTA co-location requirements are based on the power at the conducted interface of a *co-location reference antenna*, depending on the requirement this interface is either an input or an output. For *IAB-DU or IAB-MT type 1-O* with dual polarization the *co-location reference antenna* has two conducted interfaces each representing one polarization. + +## 4.11 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, the requirements in the present specification apply for IAB-MT and IAB-DU of IAB-node configured as *IAB Simultaneous Operation*. + +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 different declarations for verification on Modulation quality and ACLR according to the conformance specification declaration 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. + +## 4.12 Specification suffix information + +Unless stated otherwise, the suffix shown in Table 4.12-1 is used for indicating the clause for mobile-IAB node. + +**Table 4.12-1: Definition of suffixes** + +| Clause suffix | Variant | +|---------------|-----------------| +| B | Mobile IAB-node | + +An IAB-node which supports the mobile feature needs to meet both the general requirements of local area IAB-MT and the additional requirement applicable to the additional clause (suffixes B) in clauses 5, 6, 7,8,9,10,11 and 12. Where there is a difference in requirement between the general requirements and the additional clause requirements (suffixes B) in clauses 5, 6, 7,8,9,10,11 and 12, the tighter requirements are applicable unless stated otherwise in the additional clause. + +# 5 Operating bands and channel arrangement + +## 5.1 General + +The channel arrangements presented in this clause are based on the *operating bands* and *IAB-DU or IAB-MT channel bandwidths* defined in the present release of specifications. + +NOTE: Other *operating bands* and *IAB-DU or IAB-MT 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 NR 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 | +| FR2 | FR2-1 | 24250 MHz – 52600 MHz | +| | FR2-2 | 52600 MHz – 71000 MHz | + +## 5.2 Operating bands + +NR IAB is designed to operate in the *operating bands* in FR1 defined in table 5.2-1 and operating bands in FR2-1 defined in 38.104 [2]. + +**Table 5.2-1 NR IAB operating bands in FR1** + +| 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 | +|-------------------|--------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|-------------| +| n41 | 2496 MHz – 2690 MHz | 2496 MHz – 2690 MHz | TDD | +| n77 | 3300 MHz – 4200 MHz | 3300 MHz – 4200 MHz | TDD | +| n78 | 3300 MHz – 3800 MHz | 3300 MHz – 3800 MHz | TDD | +| n79 | 4400 MHz – 5000 MHz | 4400 MHz – 5000 MHz | TDD | + +## 5.3 Channel bandwidth + +### 5.3.1 General + +The IAB-DU channel bandwidth supports a single NR RF carrier in the uplink or downlink at the IAB node. Different UE or IAB-MT channel bandwidths may be supported within the same spectrum for transmitting to and receiving from UEs or IAB-MT connected to the IAB-DU. The placement of the UE or IAB-MT channel bandwidth is flexible but can only be completely within the IAB-DU channel bandwidth. The IAB-DU shall be able to transmit to and/or receive from one or more UE or IAB-MT 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 IAB-MT channel bandwidth supports a single NR RF carrier in the uplink or downlink at the IAB-MT. From a BS or IAB-DU perspective, different IAB-MT channel bandwidths may be supported within the same spectrum for transmitting to and receiving from UEs or IAB-MT connected to the IAB-DU. Transmission of multiple carriers to the same IAB-MT (CA) or multiple carriers to different UEs or IAB-MT within the IAB-DU channel bandwidth can be supported. + +From a IAB-MT perspective, the IAB-MT is configured with one or more BWP / carriers, each with its own IAB-MT channel bandwidth. The IAB-MT does not need to be aware of the BS or IAB-DU channel bandwidth or how the BS or IAB-DU allocates bandwidth to different UEs or IAB-MT. + +The placement of the IAB-MT channel bandwidth for each IAB-MT carrier is flexible but can only be completely within the IAB-donor or IAB-DU channel bandwidth. + +The relationship between the IAB-DU or IAB-MT channel bandwidth, the guardband 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 NR channel** + +### 5.3.2 Transmission bandwidth configuration + +For IAB-DU, the transmission bandwidth configuration is the same as specified for BS in TS 38.104 [2], subclause 5.3.2. + +For IAB-MT, the transmission bandwidth configuration is the same as specified for UE in TS 38.101-1 [3] for FR1 in subclause 5.3.2 and in TS 38.101-2 [4] for FR2-1 in subclause 5.3.2. + +### 5.3.3 Minimum guardband and transmission bandwidth configuration + +For IAB-DU, the minimum guardband and transmission bandwidth configuration is the same as specified for BS in TS38.104 [2], subclause 5.3.3. + +For IAB-MT, the minimum guardband and transmission bandwidth configuration is the same as specified for UE in TS38.101-1 [3] for FR1 and in TS 38.101-2 [4] for FR2-1 in subclause 5.3.3. + +### 5.3.4 RB alignment + +For each *IAB-DU channel bandwidth* and each numerology, *IAB-DU transmission bandwidth configuration* must fulfil the minimum guardband requirement specified in clause 5.3.3. + +For IAB-DU, for each numerology, its common resource blocks are specified in clause 4.4.4.3 in [7], 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 IAB-DU, for each numerology, all *UE and IAB-MT transmission bandwidth configurations* indicated to UEs or IAB-MT served by the IAB-DU by higher layer parameter *carrierBandwidth* defined in TS 38.331 [15] shall fall within the *IAB-DU transmission bandwidth configuration*. + +For IAB-MT, the RB alignment is the same as specified for UE in TS38.101-1 [3] for FR1 in subclause 5.3.4 and in TS 38.101-2 [4] for FR2-1 in subclause 5.3.4. + +### 5.3.5 IAB-DU and IAB-MT channel bandwidth per operating band + +For IAB-DU, the channel bandwidth for NR bands for FR1 in Table 5.2.1 and for NR bands for FR2-1 defined in TS38.104 [2] is the same as specified for BS in TS38.104 [2], subclause 5.3.5. + +For IAB-MT, the channel bandwidth for NR bands for FR1 in Table 5.2-1 is the same as specified for UE in TS38.101-1[3] in subclause 5.3.5 and for NR bands for FR2-1 defined in TS38.104[2] is the same as specified for UE in TS38.101-2[4] in subclause 5.3.5. + +## 5.3A IAB-DU and IAB-MT channel bandwidth for CA + +The IAB-DU and IAB-MT channel bandwidth for CA is the same as specified for BS in TS38.104[2], subclause 5.3A. + +## 5.4 Channel arrangement + +### 5.4.1 Channel spacing + +For IAB-DU, the channel spacing is the same as specified for BS in TS38.104 [2], subclause 5.4.1. + +For IAB-MT, the channel spacing is the same as specified for UE in TS38.101-1 [3] for FR1 in subclause 5.4.1 and in TS38.101-2 [4] for FR2-1 in subclause 5.4.1. + +### 5.4.2 Channel raster + +#### 5.4.2.1 NR-ARFCN and channel raster + +For IAB-DU, the NR-ARFCN and channel raster is the same as specified for BS in TS38.104 [2], subclause 5.4.2.1. + +For IAB-MT, the NR-ARFCN and channel raster is the same as specified for UE in TS38.101-1 [3] for FR1 in subclause 5.4.2.1 and in TS38.101-2 [4] for FR2-1 in subclause 5.4.2.1. + +#### 5.4.2.2 Channel raster to resource element mapping + +For IAB-DU, the Channel raster to resource element mapping is the same as specified for BS in TS38.104 [2], subclause 5.4.2.2. + +For IAB-MT, the Channel raster to resource element mapping is the same as specified for UE in TS38.101-1 [3] for FR1 in subclause 5.4.2.2 and in TS38.101-2 [4] for FR2-1 in subclause 5.4.2.2. + +#### 5.4.2.3 Channel raster entries for each *operating band* + +For IAB-DU, the channel raster entries for NR bands for FR1 in Table 5.2-1 and NR bands for FR2-1 defined in TS38.104 [2] are the same as specified for BS in TS38.104 [2], subclause 5.4.2.3. + +For IAB-MT, the channel raster entries for NR bands for FR1 in Table 5.2-1 are the same as specified for UE in TS38.101-1 [3] in subclause 5.4.2.3 and for NR bands for FR2-1 defined in TS38.104 [2] are the same as specified for UE in TS38.101-2 [4] in subclause 5.4.2.3. + +### 5.4.3 Synchronization raster + +#### 5.4.3.1 Synchronization raster and numbering + +For IAB-DU, the synchronization raster and numbering are the same as specified for BS in TS38.104 [2], subclause 5.4.3.1. + +For IAB-MT, the synchronization raster and numbering are the same as specified for UE in TS38.101-1 [3] for FR1 in subclause 5.4.3.1 and in TS38.101-2 [4] for FR2-1 in subclause 5.4.3.1. + +#### 5.4.3.2 Synchronization raster to synchronization block resource element mapping + +For IAB-DU, the synchronization raster to synchronization block resource element mapping is the same as specified for BS in TS38.104 [2], subclause 5.4.3.2. + +For IAB-MT, the synchronization raster to synchronization block resource element mapping is the same as specified for UE in TS38.101-1 [3] for FR1 in subclause 5.4.3.2 and in TS38.101-2 [4] for FR2-1 in subclause 5.4.3.2. + +#### 5.4.3.3 Synchronization raster entries for each operating band + +For IAB-DU, the synchronization raster entries for NR bands for FR1 in Table 5.2-1 and for NR bands for FR2-1 defined in TS38.104 [2] are the same as specified for BS in TS38.104 [2], subclause 5.4.3.3. + +For IAB-MT, the synchronization raster entries for NR bands for FR1 in Table 5.2-1 are the same as specified for UE in TS38.101-1 [3] in subclause 5.4.3.3 and for NR bands for FR2-1 defined in TS38.104 [2] are the same as specified for UE in TS38.101-2 [4] in subclause 5.4.3.3. + +## 6 Conducted transmitter characteristics + +### 6.1 General + +Unless otherwise stated, the conducted transmitter characteristics are specified at the *TAB connector* for *IAB-DU* and *IAB-MT type 1-H*, with a full complement of transceiver units for the configuration in normal operating conditions. + +For *IAB-DU* and *IAB-MT type 1-H* the manufacturer shall declare the minimum number of supported geographical cells (i.e. geographical areas covered by beams). The declaration is done separately for IAB-DU and IAB-MT. The minimum number of supported geographical cells ( $N_{\text{cells}}$ ) relates to the setting with the minimum amount of cell splitting supported with transmission on all *TAB connectors* supporting the *operating band*, or with minimum amount of transmitted beams. + +For *IAB-DU* and *IAB-MT type 1-H* manufacturer shall also declare *TAB connector TX min cell groups*. The declaration is done separately for IAB-DU and IAB-MT. Every *TAB connector* of the *IAB-DU type 1-H* and *IAB-MT type 1-H* supporting transmission in an *operating band* shall map to one *TAB connector TX min cell group* supporting the same *operating band*, where mapping of *TAB connectors* to cells/beams is implementation dependent. + +The number of *active transmitter units* that are considered when calculating the conducted TX emissions limits ( $N_{\text{TXU,counted}}$ ) for *IAB-DU* and *IAB-MT type 1-H* is calculated as follows: + +$$N_{\text{TXU,counted}} = \min(N_{\text{TXU,active}}, 8 \times N_{\text{cells}})$$ + +$N_{\text{TXU,countedpercell}}$ is used for scaling of *basic limits* and is derived as $N_{\text{TXU,countedpercell}} = N_{\text{TXU,counted}} / N_{\text{cells}}$ + +NOTE: $N_{\text{TXU,active}}$ depends on the actual number of *active transmitter units* and is independent to the declaration of $N_{\text{cells}}$ . + +### 6.2 IAB output power + +#### 6.2.1 General + +The IAB type 1-H conducted output power requirement is at *TAB connector* for *IAB type 1-H*. + +The *rated carrier output power* of the *IAB type 1-H* shall be as specified in table 6.2.1-1 for *IAB-DU type 1-H* and in table 6.2.1-2 for *IAB-MT type 1-H*. + +**Table 6.2.1-1: IAB-DU type 1-H rated output power limits for IAB-DU classes** + +| IAB-DU class | $P_{\text{rated,c,sys}}$ | $P_{\text{rated,c,TABC}}$ | +|----------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------|---------------------------| +| Wide Area IAB-DU | (Note) | (Note) | +| Medium Range IAB-DU | $\leq 38 \text{ dBm} + 10\log(N_{\text{TXU,counted}})$ | $\leq 38 \text{ dBm}$ | +| Local Area IAB-DU | $\leq 24 \text{ dBm} + 10\log(N_{\text{TXU,counted}})$ | $\leq 24 \text{ dBm}$ | +| NOTE: There is no upper limit for the $P_{\text{rated,c,sys}}$ or $P_{\text{rated,c,TABC}}$ of the Wide Area IAB-DU. | | | + +**Table 6.2.1-2: IAB-MT type 1-H rated output power limits for IAB-MT classes** + +| IAB-MT class | $P_{\text{rated,c,sys}}$ | $P_{\text{rated,c,TABC}}$ | +|----------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------|---------------------------| +| Wide Area IAB-MT | (Note) | (Note) | +| Local Area IAB-MT | $\leq 24 \text{ dBm} + 10\log(N_{\text{TXU,counted}})$ | $\leq 24 \text{ dBm}$ | +| NOTE: There is no upper limit for the $P_{\text{rated,c,sys}}$ or $P_{\text{rated,c,TABC}}$ of the Wide area IAB-MT. | | | + +## 6.2.1B Output power for mIAB-MT + +The output power requirements in clause 6.2.1 for Local area IAB-MT apply for mIAB-MT. + +### 6.3.2.1.2B Minimum requirement for mIAB-MT type 1-H + +For a mIAB-MT the total power dynamic range for each NR carrier shall be larger than or equal to $73 - 10\log_{10}(\text{BW}_{\text{Channel}}/20)$ dB where $\text{BW}_{\text{Channel}}$ is the mIAB-MT configured channel bandwidth. + +## 6.2.2 Minimum requirement for IAB type 1-H + +In normal conditions, $P_{\text{max,c,TABC}}$ shall remain within +2 dB and -2 dB of the *rated carrier output power* $P_{\text{rated,c,TABC}}$ for each *TAB connector* as declared by the manufacturer. + +In extreme conditions, $P_{\text{max,c,TABC}}$ shall remain within +2.5 dB and -2.5 dB of the *rated carrier output power* $P_{\text{rated,c,TABC}}$ for each *TAB connector* as declared by the manufacturer. + +In certain regions, the minimum requirement for normal conditions may apply also for some conditions outside the range of conditions defined as normal. + +## 6.2.3 Additional requirements (regional) + +In certain regions, additional regional requirements may apply. + +# 6.3 Output power dynamics + +## 6.3.1 IAB-DU Output Power Dynamics + +### 6.3.1.1 General + +The requirements in clause 6.3 apply during the *transmitter ON period*. 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.1.2 RE power control dynamic range + +#### 6.3.1.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 IAB-DU at maximum output power ( $P_{\text{max,c,TABC}}$ ) for a specified reference condition. + +For *IAB-DU type 1-H* this requirement shall apply at each *TAB connector* supporting transmission in the *operating band*. + +#### 6.3.1.2.2 Minimum requirement for IAB-DU type 1-H + +The RE power control dynamic range is specified the same as the conducted RE power control dynamic range requirement for BS type 1-H in TS 38.104 [2], subclause 6.3.2.2. + +#### 6.3.1.3 Total power dynamic range + +##### 6.3.1.3.1 General + +The IAB-DU 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 IAB-DU type 1-H this requirement shall apply at each *TAB connector* supporting transmission in the *operating band*. + +NOTE: The upper limit of the dynamic range is the OFDM symbol power for a BS 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.1.3.2 Minimum requirement for IAB-DU type 1-H + +The total power dynamic range is specified the same as the total power dynamic range requirement for BS type 1-H in TS 38.104 [2], subclause 6.3.3.2, where references to *BS channel bandwidth* apply to *IAB-DU channel bandwidth*. + +### 6.3.2 IAB-MT Output Power Dynamics + +#### 6.3.2.1 Total power dynamic range + +##### 6.3.2.1.1 General + +The IAB-MT 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 included as part of the dynamic range. + +##### 6.3.2.1.2 Minimum requirement for IAB-MT type 1-H + +For a wide area IAB-MT the total power dynamic range for each NR carrier shall be larger than or equal to 5 dB. + +For a local area IAB-MT the total power dynamic range for each NR carrier shall be larger than or equal to 10 dB. + +### 6.3.3 Power control + +#### 6.3.3.1 Relative power tolerance for local area IAB-MT type 1-H + +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. + +The minimum requirements specified for each *TAB-connector* in Table 6.3.3.1-1 apply only when the output power is within the limits set by declared maximum output power and specified dynamic range. + +2 exceptions are allowed for each of two test patterns. The test patterns are a monotonically increasing power sweep and a monotonically decreasing power sweep. For those exceptions, the power tolerance limit is a maximum of [ $\pm 6.0$ dB] in Table 6.3.3.1-1. + +**Table 6.3.3.1-1: Relative power tolerance** + +| Power step $\Delta P$ (Up or down) (dB) | Power tolerance (dB) | +|-----------------------------------------|----------------------| +| $\Delta P < 2$ | $[\pm 2.5]$ | +| $2 \leq \Delta P < 3$ | $[\pm 3.5]$ | +| $3 \leq \Delta P < 4$ | $[\pm 4.5]$ | +| $4 \leq \Delta P < 10$ | $[\pm 5.5]$ | + +### 6.3.3.1B Relative power tolerance for mIAB-MT type 1-H + +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. + +The minimum requirements specified for each *TAB-connector* in Table 6.3.3.1B-1 apply only when the output power is within the limits set by declared maximum output power and specified dynamic range. + +2 exceptions are allowed for each of two test patterns. The test patterns are a monotonically increasing power sweep and a monotonically decreasing power sweep. For those exceptions, the power tolerance limit is a maximum of $[\pm 6.0 \text{ dB}]$ in Table 6.3.3.1B-1. + +**Table 6.3.3.1B-1: Relative power tolerance** + +| Power step $\Delta P$ (Up or down) (dB) | Power tolerance (dB) | +|-----------------------------------------|----------------------| +| $\Delta P < 2$ | $[\pm 2.5]$ | +| $2 \leq \Delta P < 3$ | $[\pm 3.5]$ | +| $3 \leq \Delta P < 4$ | $[\pm 4.5]$ | +| $4 \leq \Delta P < 10$ | $[\pm 5.5]$ | +| $10 \leq \Delta P < 15$ | $[\pm 6]$ | +| $15 \leq \Delta P$ | $[\pm 6.5]$ | + +### 6.3.3.2 Aggregate power tolerance for local area IAB-MT type 1-H + +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 [10] kept constant. + +The minimum requirements specified for each *TAB-connector* in Table 6.3.3.2-1 apply only when the output power is within the limits set by declared maximum output power and specified dynamic range. + +**Table 6.3.3.2-1: Aggregate power tolerance** + +| TPC command | UL channel | Aggregate power tolerance within [21 ms] | +|-------------|------------|------------------------------------------| +| 0 dB | PUCCH | $[\pm 2.5 \text{ dB}]$ | +| 0 dB | PUSCH | $[\pm 3.5 \text{ dB}]$ | + +## 6.4 Transmit ON/OFF power + +### 6.4.1 Transmitter OFF power + +#### 6.4.1.1 General + +Transmit OFF power requirements apply to TDD operation of IAB-DU and TDD operation of IAB-MT. + +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 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-DU and IAB-MT, 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 IAB 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 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 (IAB-MT) Channel Bandwidth*. + +#### 6.4.1.3 Minimum requirement for IAB-DU type 1-H + +The BS requirements specified in 6.4.1.3 in TS 38.104 [2] apply to *IAB-DU type 1-H*. + +#### 6.4.1.4 Minimum requirement for IAB-MT type 1-H + +The BS requirements specified in 6.4.1.3 in TS 38.104 [2] apply to *IAB-MT type 1-H*. + +### 6.4.2 Transmitter transient period + +#### 6.4.2.1 General + +Transmitter transient period requirements apply to TDD operation of IAB-DU and TDD operation of IAB-MT. + +The transmitter transient period is the time period during which the transmitter is changing from the transmitter OFF period to the transmitter ON period or vice versa. The transmitter transient period is illustrated in figure 6.4.2.1-1 for IAB-DU and IAB-MT. + +![Figure 6.4.2.1-1: Example of relations between transmitter ON period, transmitter OFF period and transmitter transient period for IAB-DU and IAB-MT. 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' (shaded area on the left), 'Transmitter ON period (DL/UL transmission)' (middle), and 'GP or UL/DL transmission' (shaded area on the right). The 'Transmitter transient period' is indicated by two double-headed arrows: one between the 'Transmitter OFF period' (left) and the start of the ON period, and another between the end of the ON period and the start of the next 'Transmitter OFF period' (right). The power curve shows a smooth transition between the ON and OFF levels during these transient periods.](50af5a2f950373ea84d0298d4c7ae25d_img.jpg) + +Figure 6.4.2.1-1: Example of relations between transmitter ON period, transmitter OFF period and transmitter transient period for IAB-DU and IAB-MT. 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' (shaded area on the left), 'Transmitter ON period (DL/UL transmission)' (middle), and 'GP or UL/DL transmission' (shaded area on the right). The 'Transmitter transient period' is indicated by two double-headed arrows: one between the 'Transmitter OFF period' (left) and the start of the ON period, and another between the end of the ON period and the start of the next 'Transmitter OFF period' (right). The power curve shows a smooth transition between the ON and OFF levels during these transient periods. + +**Figure 6.4.2.1-1: Example of relations between transmitter ON period, transmitter OFF period and transmitter transient period for IAB-DU and IAB-MT** + +For IAB-DU type 1-H and IAB-MT type 1-H, this requirement shall be applied at each TAB connector supporting transmission in the operating band. + +#### 6.4.2.2 Minimum requirement for IAB-DU type 1-H + +The BS requirements specified in clause 6.4.2.2 in TS 38.104 [2] apply to *IAB-DU type 1-H*. + +#### 6.4.2.3 Minimum requirement for IAB-MT type 1-H + +The BS requirements specified in clause 6.4.2.2 in TS 38.104 [2] apply to *IAB-MT type 1-H*. + +## 6.5 Transmitted signal quality + +### 6.5.1 Frequency error + +#### 6.5.1.1 IAB-DU frequency error + +The requirements in clause 6.5.1 for BS type 1-H in TS 38.104 [2] apply to IAB-DU type 1-H. + +#### 6.5.1.2 IAB-MT frequency error + +The IAB-MT basic measurement interval of modulated carrier frequency is 1 UL slot. The mean value of basic measurements of IAB-MT modulated carrier frequency shall be accurate to within $\pm 0.1$ PPM observed over a period of 1 ms of cumulated measurement intervals compared to the carrier frequency received from the parent node. + +### 6.5.2 Modulation quality + +#### 6.5.2.1 IAB-DU modulation quality + +The requirements in clause 6.5.2 for BS type 1-H in TS 38.104 [2] apply to IAB-DU type 1-H. + +NOTE: When the indicated IAB-MT transmission timing mode is set to 'Case6' as specified in 3GPP TS 38.213 [10], the power imbalance for simultaneous transmission between IAB-DU and IAB-MT under which the system can be operated is declared by manufacturer. + +#### 6.5.2.2 IAB-MT modulation quality + +##### 6.5.2.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 D. + +For IAB-MT type 1-H this requirement shall be applied at each TAB connector supporting transmission in the operating band. + +##### 6.5.2.2.2 Minimum requirements for IAB-MT type 1-H + +For *IAB-MT type 1-H*, the EVM levels of each NR carrier for different modulation schemes outlined in table 6.5.2.2.2-1 shall be met using the frame structure described in clause 6.5.2.2.3. + +**Table 6.5.2.2.2-1: Requirements for Error Vector Magnitude** + +| Parameter | Unit | Average EVM Level | +|-----------|------|-------------------| +| QPSK | % | 17.5 | +| 16 QAM | % | 12.5 | +| 64 QAM | % | 8 | +| 256 QAM | % | 3.5 | + +NOTE: When the indicated IAB-MT transmission timing mode is set to 'Case6' as specified in 3GPP TS 38.213 [10], the power imbalance for simultaneous transmission between IAB-DU and IAB-MT under which the system can be operated is declared by manufacturer. + +##### 6.5.2.2.3 EVM frame structure for measurement + +EVM shall be evaluated for each NR carrier over all allocated resource blocks and uplink subframes for IAB-MT. Different modulation schemes listed in Table 6.5.2.2.2-1 shall be considered for rank 1. + +For NR, for all bandwidths, the EVM measurement shall be performed for each NR carrier over all allocated resource blocks and uplink 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 + +#### 6.5.3.1 IAB-DU time alignment error + +The requirements in clause 6.5.3 for BS type 1-H in TS 38.104 [2] apply to IAB-DU type 1-H. + +### 6.5.4 Timing error between IAB-DU and IAB-MT of the same IAB-Node + +When the indicated IAB-MT transmission timing mode is set to 'Case6' as specified in 3GPP TS 38.213 [10] and IAB-DU and IAB-MT of the same IAB-Node are transmitting simultaneously, the timing error between transmission timing of IAB-DU and IAB-MT shall not exceed 3 $\mu$ s. + +## 6.6 Unwanted emissions + +### 6.6.1 General + +Unwanted emissions consist of out-of-band emissions and spurious emissions according to ITU definitions [16]. In ITU terminology, out of band emissions are unwanted emissions immediately outside the channel bandwidth resulting from the modulation process and non-linearity in the transmitter but excluding spurious emissions. Spurious emissions are emissions which are caused by unwanted transmitter effects such as harmonics emission, parasitic emission, intermodulation products and frequency conversion products, but exclude out of band emissions. + +The out-of-band emissions requirement for the IAB-DU and IAB-MT 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* of IAB-DU and uplink *operating band* of IAB-MT, 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 tables 6.6.1-1 and 6.6.1-2 for the NR *operating bands*. + +**Table 6.6.1-1: Maximum offset of OBUE outside the downlink *operating band* of IAB-DU** + +| IAB-DU type | Operating band characteristics | $\Delta f_{\text{OBUE}}$ (MHz) | +|-----------------|----------------------------------------------------------------------|--------------------------------| +| IAB-DU type 1-H | $F_{\text{DL,high}} - F_{\text{DL,low}} < 100$ MHz | 10 | +| | $100$ MHz $\leq F_{\text{DL,high}} - F_{\text{DL,low}} \leq 900$ MHz | 40 | + +**Table 6.6.1-2: Maximum offset of OBUE outside the uplink *operating band* of IAB-MT** + +| IAB-MT type | Operating band characteristics | $\Delta f_{\text{OBUE}}$ (MHz) | +|-----------------|----------------------------------------------------------------------|--------------------------------| +| IAB-MT type 1-H | $F_{\text{UL,high}} - F_{\text{UL,low}} < 100$ MHz | 10 | +| | $100$ MHz $\leq F_{\text{UL,high}} - F_{\text{UL,low}} \leq 900$ MHz | 40 | + +For IAB-DU type 1-H and IAB-MT type 1-H the unwanted emission requirements are applied per the *TAB connector TX min cell groups* for all the supported configurations. 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 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 [19]. + +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 *IAB-DU type 1-H* and *IAB-MT 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 *IAB-DU type 1-H* + +The occupied bandwidth for each NR carrier shall be less than the *IAB-DU channel bandwidth*. For intra-band contiguous CA, the occupied bandwidth shall be less than or equal the *Aggregated IAB-DU Channel Bandwidth*. + +### 6.6.2.3 Minimum requirement for *IAB-MT type 1-H* + +The occupied bandwidth for each NR carrier shall be less than the *IAB-MT channel bandwidth*. For intra-band contiguous CA, the occupied bandwidth shall be less than or equal the *Aggregated IAB-MT 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 *IAB-DU RF Bandwidth*, *IAB-MT RF Bandwidth* or *Radio Bandwidth* whatever the type of transmitter considered (single carrier or multi-carrier) and for all transmission modes foreseen by the manufacturer's specification. + +For an *IAB-Node* operating in *non-contiguous spectrum*, the ACLR requirement in clause 6.6.3.2 shall apply in *sub-block gaps* for the frequency ranges defined in table 6.6.3.2-3, while the CACLR requirement in clause 6.6.3.2 shall apply in *sub-block gaps* for the frequency ranges defined in table 6.6.3.2-4. + +For a *multi-band connector*, the ACLR requirement in clause 6.6.3.2 shall apply in *Inter RF Bandwidth gaps* for the frequency ranges defined in table 6.6.3.2-3, while the CACLR requirement in clause 6.6.3.2 shall apply in *Inter RF Bandwidth gaps* for the frequency ranges defined in table 6.6.3.2-4. + +The requirement shall apply during the *transmitter ON period*. + +NOTE: When the indicated IAB-MT transmission timing mode is set to 'Case6' as specified in 3GPP TS 38.213 [10], the power imbalance for simultaneous transmission between IAB-DU and IAB-MT under which the system can be operated is declared by manufacturer. + +### 6.6.3.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_{\text{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. + +**Table 6.6.3.2-1: *IAB-DU type 1-H* and *IAB-MT type 1-H* 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 (informative) | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|-------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|------------------------------------------------------------------------------------|-------------------| +| 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}}$ ) | 45 dB | +| | $2 \times BW_{\text{Channel}}$ | NR of same BW (Note 2) | Square ( $BW_{\text{Config}}$ ) | 45 dB | + +| | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|--------------|------------------|-------------------| +| | $BW_{Channel}/2 + 2.5$ MHz | 5 MHz E-UTRA | Square (4.5 MHz) | 45 dB
(Note 3) | +| | $BW_{Channel}/2 + 7.5$ MHz | 5 MHz E-UTRA | Square (4.5 MHz) | 45 dB
(Note 3) | +| NOTE 1: $BW_{Channel}$ and $BW_{Config}$ are the 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_{Config}$ ).
NOTE 3: The requirements are applicable when the band is also defined for E-UTRA or UTRA. | | | | | + +The ACLR absolute *basic limit* is specified in table 6.6.3.2-2. + +**Table 6.6.3.2-2: IAB-DU type 1-H and IAB-MT type 1-H ACLR absolute basic limit** + +| IAB-DU and IAB-MT category / class | ACLR absolute basic limit | +|-------------------------------------------------------------|----------------------------------| +| Category A Wide Area IAB-DU and Category A Wide Area IAB-MT | -13 dBm/MHz | +| Category B Wide Area IAB-DU and Category B Wide Area IAB-MT | -15 dBm/MHz | +| Medium Range IAB-DU | -25 dBm/MHz | +| Local Area IAB-DU and Local Area IAB-MT | -32 dBm/MHz | + +For operation in non-contiguous spectrum or multiple bands, the ACLR shall be higher than the value specified in Table 6.6.3.2-3. + +**Table 6.6.3.2-3: IAB-DU type 1-H and IAB-MT type 1-H ACLR limit in non-contiguous spectrum or multiple bands** + +| IAB-DU and IAB-MT channel bandwidth of lowest/highest 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 IAB-DU or IAB-MT RF Bandwidth edge (inside the gap) | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|-----------------------------------------------------------------------------|------------| +| 10, 15, 20 | $W_{gap} \geq 15$ (Note 3)
$W_{gap} \geq 45$ (Note 4) | 2.5 MHz | 5 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 45 dB | +| | $W_{gap} \geq 20$ (Note 3)
$W_{gap} \geq 50$ (Note 4) | 7.5 MHz | 5 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 45 dB | +| 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | $W_{gap} \geq 60$ (Note 4)
$W_{gap} \geq 30$ (Note 3) | 10 MHz | 20 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 45 dB | +| | $W_{gap} \geq 80$ (Note 4)
$W_{gap} \geq 50$ (Note 3) | 30 MHz | 20 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 45 dB | +| NOTE 1: $BW_{Config}$ is the transmission bandwidth configuration of the assumed adjacent channel carrier.
NOTE 2: With SCS that provides largest transmission bandwidth configuration ( $BW_{Config}$ ).
NOTE 3: Applicable in case the IAB-DU or IAB-MT 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-DU or IAB-MT 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 Cumulative Adjacent Channel Leakage power Ratio (CACLR) in a *sub-block gap* or the *Inter RF Bandwidth gap* is the ratio of: + +- a) the sum of the filtered mean power centred on the assigned channel frequencies for the two carriers adjacent to each side of the *sub-block gap* or the *Inter RF Bandwidth gap*, and +- b) the filtered mean power centred on a frequency channel adjacent to one of the respective *sub-block edges*, *IAB-MT RF Bandwidth edges* or *IAB-DU RF Bandwidth edges*. + +The assumed filter for the adjacent channel frequency is defined in table 6.6.3.2-4 and the filters on the assigned channels are defined in table 6.6.3.2-6. + +For operation in *non-contiguous spectrum* or multiple bands, 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.2-4. + +**Table 6.6.3.2-4: IAB-DU type 1-H and IAB-MT type 1-H CACLR limit** + +| IAB-DU and IAB-MT channel bandwidth of lowest/highest carrier transmitted $BW_{\text{channel}}$ (MHz) | Sub-block or Inter RF Bandwidth 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 or IAB-DU or IAB-MT RF Bandwidth edge (inside the gap) | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | CACLR limit | +|-------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|-----------------------------------------------------------------------------|-------------| +| 10, 15, 20 | $5 \leq W_{\text{gap}} < 15$ (Note 3)
$5 \leq W_{\text{gap}} < 45$ (Note 4) | 2.5 MHz | 5 MHz NR (Note 2) | Square ( $BW_{\text{Config}}$ ) | 45 dB | +| | $10 < W_{\text{gap}} < 20$ (Note 3)
$10 \leq W_{\text{gap}} < 50$ (Note 4) | 7.5 MHz | 5 MHz NR (Note 2) | Square ( $BW_{\text{Config}}$ ) | 45 dB | +| 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | $20 \leq W_{\text{gap}} < 60$ (Note 4)
$20 \leq W_{\text{gap}} < 30$ (Note 3) | 10 MHz | 20 MHz NR (Note 2) | Square ( $BW_{\text{Config}}$ ) | 45 dB | +| | $40 < W_{\text{gap}} < 80$ (Note 4)
$40 \leq W_{\text{gap}} < 50$ (Note 3) | 30 MHz | 20 MHz NR (Note 2) | Square ( $BW_{\text{Config}}$ ) | 45 dB | + +NOTE 1: $BW_{\text{Config}}$ is the transmission bandwidth configuration of the assumed adjacent channel carrier. + +NOTE 2: With SCS that provides largest transmission bandwidth configuration ( $BW_{\text{Config}}$ ). + +NOTE 3: Applicable in case the *IAB-DU* or *IAB-MT 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-DU* or *IAB-MT 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 CACLR absolute *basic limit* is specified in table 6.6.3.2-5. + +**Table 6.6.3.2-5: IAB-DU type 1-H and IAB-MT type 1-H CACLR absolute basic limit** + +| IAB-DU and IAB-MT category / class | CACLR absolute basic limit | +|-------------------------------------------------------------|-----------------------------------| +| Category A Wide Area IAB-DU and Category A Wide Area IAB-MT | -13 dBm/MHz | +| Category B Wide Area IAB-DU and Category B Wide Area IAB-MT | -15 dBm/MHz | +| Medium Range IAB-DU | -25 dBm/MHz | +| Local Area IAB-DU and Local Area IAB-MT | -32 dBm/MHz | + +**Table 6.6.3.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.3 Minimum requirement for IAB-DU type 1-H and IAB-MT type 1-H + +The ACLR (CACLR) absolute *basic limits* in table 6.6.3.2-2 + X, 6.6.3.2-5 + X (where $X = 10\log_{10}(N_{\text{TXU, countedpercell}})$ ) or the ACLR (CACLR) *limits* in table 6.6.3.2-1, 6.6.3.2-3 or 6.6.3.2-4, whichever is less stringent, shall apply for each *TAB connector TX min cell group*. + +NOTE: Conformance to the *IAB-DU type 1-H* and *IAB-MT type 1-H* ACLR requirements 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 *basic limit*. 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 *basic limit* 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 *IAB-DU type 1-H* or *IAB-MT type 1-H* is applied, the conformance can be demonstrated by meeting at least one of the following criteria as determined by the manufacturer: + +- 1) The sum of the filtered mean power measured on each *TAB connector* in the *TAB connector TX min cell group* at the adjacent channel frequency shall be less than or equal to the ACLR (CACLR) absolute *basic limit* + X. 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* 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 General + +Unless otherwise stated, the operating band unwanted emission (OBUE) limits for IAB-DU 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*. + +Unless otherwise stated, the operating band unwanted emission (OBUE) limits for IAB-MT in FR1 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.6.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 IAB-DU and IAB-MT operating in *non-contiguous spectrum*, the requirements apply inside any *sub-block gap*. In addition, for a IAB-MT or IAB-DU 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 -3dB point of the measuring filter closest to the carrier frequency. +- $f\_offset$ is the separation between the *channel edge* frequency and the centre of the measuring filter. +- $f\_offset_{max}$ is the offset to the frequency $\Delta f_{OBUE}$ outside the downlink *operating band* of IAB-DU and uplink *operating band* of IAB-MT, where $\Delta f_{OBUE}$ is defined in tables 6.6.1-1 and 6.6.1-2. +- $\Delta f_{max}$ is equal to $f\_offset_{max}$ minus half of the bandwidth of the measuring filter. + +For a *multi-band connector* inside any *Inter RF Bandwidth gaps* with $W_{gap} < 2 * \Delta f_{OBUE}$ , a combined *basic limit* shall be applied which is the cumulative sum of the *basic limits* specified at the *IAB-DU and IAB-MT RF Bandwidth edges* on each side of the *Inter RF Bandwidth gap*. The *basic limit* for *IAB-DU and IAB-MT RF Bandwidth edge* is specified in clauses 6.6.4.2.1 to 6.6.4.2.4 below, where in this case: + +- $\Delta f$ is the separation between the *IAB-DU or IAB-MT RF Bandwidth edge* frequency and the nominal -3 dB point of the measuring filter closest to the *IAB-DU or IAB-MT RF Bandwidth edge*. +- $f\_offset$ is the separation from the *IAB-DU or IAB-MT RF Bandwidth edge* frequency to 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* of IAB-DU, 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 *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 limits* 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 *multi-band connector* of IAB-MT, 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 *basic limit* 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_{OBUE}$ , $f\_offset_{max}$ shall be the offset to the frequency $\Delta f_{OBUE}$ MHz outside the outermost edges of the two supported uplink *operating bands* and the operating band unwanted emission *basic limits* 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 *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 uplink *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 clauses 6.6.4.2.1 to 6.6.4.2.4 below, where in this case: + +- $\Delta f$ is the separation between the *sub-block* edge frequency and the nominal -3 dB point of the measuring filter closest to the *sub-block* edge. +- $f\_offset$ is the separation between the *sub-block* edge frequency and the centre of the measuring filter. +- $f\_offset_{max}$ is equal to the *sub-block gap* bandwidth minus half of the bandwidth of the measuring filter. +- $\Delta f_{max}$ is equal to $f\_offset_{max}$ minus half of the bandwidth of the measuring filter. + +For Wide Area IAB-DU and Wide Area IAB-MT, the requirements of either clause 6.6.4.2.1 (Category A limits) or clause 6.6.4.2.2 (Category B limits) shall apply. + +For Medium Range IAB-DU, the requirements in clause 6.6.4.2.3 shall apply (Category A and B). + +For Local Area IAB-DU and Local Area IAB-MT, the requirements of clause 6.6.4.2.4 shall apply (Category A and B). + +The application of either Category A or Category B *basic limits* shall be the same as for Transmitter spurious emissions in clause 6.6.5. + +## 6.6.4.2 Basic limits + +### 6.6.4.2.1 Basic limits for Wide Area IAB-DU and Wide Area IAB-MT (Category A) + +For operating in Bands n41, n77, n78, n79, *basic limits* are specified in table 6.6.4.2.1-1: + +**Table 6.6.4.2.1-1: Wide Area IAB-DU and Wide Area IAB-MT operating band unwanted emission limits (NR bands above 1 GHz) for Category A** + +| 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 < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-7 \text{ dBm} - \frac{7}{5} \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{max})$ | -14 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | -13 dBm (Note 3) | 1MHz | + +NOTE 1: For an IAB-DU and IAB-MT 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_{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.2.2 Basic limits for Wide Area IAB-DU and Wide Area IAB-MT (Category B) + +For Category B Operating band unwanted emissions, the *basic limits* in clause 6.6.4.2.2.1 shall be applied. + +#### 6.6.4.2.2.1 Category B requirements + +For IAB-DU and IAB-MT operating in Bands n41, n77, n78, n79 *basic limits* are specified in tables 6.6.4.2.2.1-1: + +**Table 6.6.4.2.2.1-1: Wide Area IAB-DU and IAB-MT 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 limits (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}$ | $-7 \text{ dBm} - \frac{7}{5} \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.05 \right) \text{ dB}$ | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -14 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -15 dBm (Note 3) | 1MHz | +| NOTE 1: For an IAB-DU and IAB-MT 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.6.4.2.3 Basic limits for Medium Range IAB-DU (Category A and B) + +For Medium Range IAB-DU, *basic limits* are specified in table 6.6.4.2.3-1 and table 6.6.4.2.3-2. + +For the tables in this clause for *IAB-DU type 1-H* $P_{\text{rated},x} = P_{\text{rated},c,\text{cell}} - 10 \cdot \log_{10}(N_{\text{TXU},\text{countedpercell}})$ , and *IAB-DU type 1-O* $P_{\text{rated},x} = P_{\text{rated},c,\text{TRP}} - 9 \text{ dB}$ . + +**Table 6.6.4.2.3-1: Medium Range IAB-DU operating band unwanted emission limits, $31 < P_{\text{rated},x} \leq 38 \text{ dBm}$** + +| 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 < 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} - 60 \text{ dB}$ | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.5 \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 an IAB-DU 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},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.2.3-2: Medium Range IAB-DU operating band unwanted emission limits, $P_{\text{rated,x}} \leq 31$ dBm** + +| 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 < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -29 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -29 dBm (Note 3) | 100 kHz | + +NOTE 1: For an IAB-DU supporting *non-contiguous spectrum* operation within any *operating band* the emission limits within *sub-block gaps* is calculated as a cumulative sum of contributions from adjacent *sub-blocks* on each side of the *sub-block gap*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent *sub-blocks* on each side of the *sub-block gap*, where the emission limits within *sub-block gaps* shall be -29dBm/100kHz. + +NOTE 2: For a *multi-band connector* with *Inter RF Bandwidth gap* $< 2 \cdot \Delta f_{\text{OBUE}}$ the emission limits within the *Inter RF Bandwidth gaps* is calculated as a cumulative sum of contributions from adjacent *sub-blocks* or RF Bandwidth on each side of the *Inter RF Bandwidth gap*. + +NOTE 3: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +#### 6.6.4.2.4 Basic limits for Local Area IAB-DU and Local Area IAB-MT (Category A and B) + +For Local Area IAB-DU and Local Area IAB-MT, *basic limits* are specified in table 6.6.4.2.4-1. + +**Table 6.6.4.2.4-1: Local Area IAB-DU and Local Area IAB-MT operating band unwanted emission limits** + +| 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 < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | -37 dBm | 100 kHz | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -37 dBm (Note 10) | 100 kHz | + +NOTE 1: For an IAB-DU and IAB-MT 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.6.4.2.5 Basic limits for additional requirements + +##### 6.6.4.2.5.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, the IAB-DU and IAB-MT may have to comply with the applicable emission limits established by FCC Title 47 [20], when deployed in regions where those limits are applied, and under the conditions declared by the manufacturer. + +#### 6.6.4.3 Minimum requirements for IAB-DU type 1-H and IAB-MT type 1-H + +The operating band unwanted emissions requirements for *IAB-DU type 1-H* and *IAB-MT type 1-H* are that for each *TAB connector TX min cell group* and each applicable *basic limit* in clause 6.6.4.2, 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}})$ . + +NOTE: Conformance to the *IAB-DU type 1-H* and *IAB-MT type 1-H* operating band unwanted emission requirement can be demonstrated by meeting at least one of the following criteria as determined by the manufacturer: + +- 1) The sum of the emissions power measured on each *TAB connector* in the *TAB connector TX min cell group* shall be less than or equal to the 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 *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 General + +For IAB-DU, 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-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 [16]. + +For IAB-MT, 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 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 6.6.1-2. For some *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 ITU-R recommendation SM.329 [16]. + +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). + +### 6.6.5.2 Basic limits + +#### 6.6.5.2.1 General transmitter spurious emissions requirements + +The *basic limits* of either table 6.6.5.2.1-1 (Category A limits) or table 6.6.5.2.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. + +**Table 6.6.5.2.1-1: General IAB-DU and IAB-MT 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 | + +NOTE 1: *Measurement bandwidths* as in ITU-R SM.329 [16], s4.1. +NOTE 2: Upper frequency as in ITU-R SM.329 [16], s2.5 table 1. +NOTE 3: For IAB-DU, 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 IAB-MT, 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: This spurious frequency range applies only to *IAB-DU type 1-H* and *IAB-MT type 1-H*. + +**Table 6.6.5.2.1-2: General IAB-DU and IAB-MT 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 | + +NOTE 1: *Measurement bandwidths* as in ITU-R SM.329 [16], s4.1. +NOTE 2: Upper frequency as in ITU-R SM.329 [16], s2.5 table 1. +NOTE 3: For IAB-DU, 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 IAB-MT, 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: This spurious frequency range applies only to *IAB-DU type 1-H* and *IAB-MT type 1-H*. + +#### 6.6.5.2.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 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.5. + +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 *basic limits* are provided in table 6.6.5.2.2-1 where requirements for co-existence with the system listed in the first column apply for IAB-MT and IAB-DU. For a *multi-band connector*, the exclusions and conditions in the Note column of table 6.6.5.2.2-1 apply for each supported *operating band*. + +**Table 6.6.5.2.2-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 | Basic limits | Measurement bandwidth | Note | +|---------------------------------------------------------------|-----------------------------------------------------|---------------------|------------------------------|-------------| +| GSM900 | 921 – 960 MHz | -57 dBm | 100 kHz | | +| | 876 – 915 MHz | -61 dBm | 100 kHz | | +| DCS1800 | 1805 – 1880 MHz | -47 dBm | 100 kHz | | +| | 1710 – 1785 MHz | -61 dBm | 100 kHz | | +| PCS1900 | 1930 – 1990 MHz | -47 dBm | 100 kHz | | +| | 1850 – 1910 MHz | -61 dBm | 100 kHz | | +| GSM850 or CDMA850 | 869 – 894 MHz | -57 dBm | 100 kHz | | +| | 824 – 849 MHz | -61 dBm | 100 kHz | | +| UTRA FDD Band I or E-UTRA Band 1 or NR Band n1 | 2110 – 2170 MHz | -52 dBm | 1 MHz | | +| | 1920 – 1980 MHz | -49 dBm | 1 MHz | | +| UTRA FDD Band II or E-UTRA Band 2 or NR Band n2 | 1930 – 1990 MHz | -52 dBm | 1 MHz | | +| | 1850 – 1910 MHz | -49 dBm | 1 MHz | | +| UTRA FDD Band III or E-UTRA Band 3 or NR Band n3 | 1805 – 1880 MHz | -52 dBm | 1 MHz | | +| | 1710 – 1785 MHz | -49 dBm | 1 MHz | | +| UTRA FDD Band IV or E-UTRA Band 4 | 2110 – 2155 MHz | -52 dBm | 1 MHz | | +| | 1710 – 1755 MHz | -49 dBm | 1 MHz | | +| UTRA FDD Band V or E-UTRA Band 5 or NR Band n5 | 869 – 894 MHz | -52 dBm | 1 MHz | | +| | 824 – 849 MHz | -49 dBm | 1 MHz | | +| UTRA FDD Band VI, XIX or E-UTRA Band 6, 18, 19 or NR Band n18 | 860 – 890 MHz | -52 dBm | 1 MHz | | +| | 815 – 830 MHz | -49 dBm | 1 MHz | | +| | 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 | | +| | 2500 – 2570 MHz | -49 dBm | 1 MHz | | +| UTRA FDD Band VIII or E-UTRA Band 8 or NR Band n8 | 925 – 960 MHz | -52 dBm | 1 MHz | | +| | 880 – 915 MHz | -49 dBm | 1 MHz | | +| UTRA FDD Band IX or E-UTRA Band 9 | 1844.9 – 1879.9 MHz | -52 dBm | 1 MHz | | +| | 1749.9 – 1784.9 MHz | -49 dBm | 1 MHz | | +| UTRA FDD Band X or E-UTRA Band 10 | 2110 – 2170 MHz | -52 dBm | 1 MHz | | +| | 1710 – 1770 MHz | -49 dBm | 1 MHz | | + +| | | | | | +|-----------------------------------------------------|---------------------|---------|-------|------------------------------------------------------------------------------------| +| UTRA FDD Band XI or XXI or E-UTRA Band 11 or 21 | 1475.9 – 1510.9 MHz | -52 dBm | 1 MHz | | +| | 1427.9 – 1447.9 MHz | -49 dBm | 1 MHz | | +| | 1447.9 – 1462.9 MHz | -49 dBm | 1 MHz | | +| UTRA FDD Band XII or E-UTRA Band 12 or NR Band n12 | 729 – 746 MHz | -52 dBm | 1 MHz | | +| | 699 – 716 MHz | -49 dBm | 1 MHz | | +| UTRA FDD Band XIII or E-UTRA Band 13 | 746 – 756 MHz | -52 dBm | 1 MHz | | +| | 777 – 787 MHz | -49 dBm | 1 MHz | | +| UTRA FDD Band XIV or E-UTRA Band 14 or NR band n14 | 758 – 768 MHz | -52 dBm | 1 MHz | | +| | 788 – 798 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 17 | 734 – 746 MHz | -52 dBm | 1 MHz | | +| | 704 – 716 MHz | -49 dBm | 1 MHz | | +| UTRA FDD Band XX or E-UTRA Band 20 or NR Band n20 | 791 – 821 MHz | -52 dBm | 1 MHz | | +| | 832 – 862 MHz | -49 dBm | 1 MHz | | +| UTRA FDD Band XXII or E-UTRA Band 22 | 3510 – 3590 MHz | -52 dBm | 1 MHz | This requirement does not apply to IAB-DU and IAB-MT operating in band n77 or n78. | +| | 3410 – 3490 MHz | -49 dBm | 1 MHz | This requirement does not apply to IAB-DU and IAB-MT operating in band n77 or n78. | +| E-UTRA Band 24 | 1525 – 1559 MHz | -52 dBm | 1 MHz | | +| | 1626.5 – 1660.5 MHz | -49 dBm | 1 MHz | | +| UTRA FDD Band XXV or E-UTRA Band 25 or NR band n25 | 1930 – 1995 MHz | -52 dBm | 1 MHz | | +| | 1850 – 1915 MHz | -49 dBm | 1 MHz | | +| UTRA FDD Band XXVI or E-UTRA Band 26 or NR Band n26 | 859 – 894 MHz | -52 dBm | 1 MHz | | +| | 814 – 849 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 27 | 852 – 869 MHz | -52 dBm | 1 MHz | | +| | 807 – 824 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 28 or NR Band n28 | 758 – 803 MHz | -52 dBm | 1 MHz | | +| | 703 – 748 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 29 or NR Band n29 | 717 – 728 MHz | -52 dBm | 1 MHz | | + +| | | | | | +|---------------------------------------------------|-------------------|---------|-------|---------------------------------------------------------------------------| +| E-UTRA Band 30 or NR Band n30 | 2350 – 2360 MHz | -52 dBm | 1 MHz | | +| | 2305 – 2315 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 31 or NR Band n31 | 462.5 – 467.5 MHz | -52 dBm | 1 MHz | | +| | 452.5 – 457.5 MHz | -49 dBm | 1 MHz | | +| UTRA FDD band XXXII or E-UTRA band 32 | 1452 – 1496 MHz | -52 dBm | 1 MHz | | +| 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 | | +| 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 | | +| 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 | | +| UTRA TDD Band f) or E-UTRA Band 39 or NR band n39 | 1880 – 1920MHz | -52 dBm | 1 MHz | | +| UTRA TDD Band e) or E-UTRA Band 40 or NR Band n40 | 2300 – 2400MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 41 or NR Band n41, n90 | 2496 – 2690 MHz | -52 dBm | 1 MHz | This is not applicable IAB-DU and IAB-MT operating in Band n41. | +| E-UTRA Band 42 | 3400 – 3600 MHz | -52 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 | -52 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 | -52 dBm | 1 MHz | | +| 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 | | +| 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 IAB-DU and IAB-MT operating in Band n77 or n78. | +| E-UTRA Band 50 or NR band n50 | 1432 – 1517 MHz | -52 dBm | 1 MHz | | + +| | | | | | +|-------------------------------|-------------------|---------|-------|-----------------------------------------------------------------------------------| +| E-UTRA Band 51 or NR Band n51 | 1427 – 1432 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 53 or NR Band n53 | 2483.5 - 2495 MHz | -52 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 | -52 dBm | 1 MHz | | +| E-UTRA Band 65 or NR Band n65 | 2110 – 2200 MHz | -52 dBm | 1 MHz | | +| | 1920 – 2010 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 66 or NR Band n66 | 2110 – 2200 MHz | -52 dBm | 1 MHz | | +| | 1710 – 1780 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 67 or NR Band n67 | 738 – 758 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 68 | 753 -783 MHz | -52 dBm | 1 MHz | | +| | 698-728 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 69 | 2570 – 2620 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 70 or NR Band n70 | 1995 – 2020 MHz | -52 dBm | 1 MHz | | +| | 1695 – 1710 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 71 or NR Band n71 | 617 – 652 MHz | -52 dBm | 1 MHz | | +| | 663 – 698 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 72 or NR Band n72 | 461 – 466 MHz | -52 dBm | 1 MHz | | +| | 451 – 456 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 74 or NR Band n74 | 1475 – 1518 MHz | -52 dBm | 1 MHz | | +| | 1427 – 1470 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 75 or NR Band n75 | 1432 – 1517 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 76 or NR Band n76 | 1427 – 1432 MHz | -52 dBm | 1 MHz | | +| NR Band n77 | 3.3 – 4.2 GHz | -52 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 | -52 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 | -52 dBm | 1 MHz | This requirement does not apply to IAB-DU and IAB-MT operating in Band n79 | +| NR Band n80 | 1710 – 1785 MHz | -49 dBm | 1 MHz | | +| NR Band n81 | 880 – 915 MHz | -49 dBm | 1 MHz | | +| NR Band n82 | 832 – 862 MHz | -49 dBm | 1 MHz | | +| NR Band n83 | 703 – 748 MHz | -49 dBm | 1 MHz | | +| NR Band n84 | 1920 – 1980 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 85 or NR Band n85 | 728 – 746 MHz | -52 dBm | 1 MHz | | +| | 698 – 716 MHz | -49 dBm | 1 MHz | | +| NR Band n86 | 1710 – 1780 MHz | -49 dBm | 1 MHz | | +| NR Band n89 | 824 – 849 MHz | -49 dBm | 1 MHz | | +| NR Band n91 | 1427 – 1432 MHz | -52 dBm | 1 MHz | | +| | 832 – 862 MHz | -49 dBm | 1 MHz | | +| NR Band n92 | 1432 – 1517 MHz | -52 dBm | 1 MHz | | + +| | | | | | +|---------------------------------|---------------------|---------|-------|--| +| | 832 – 862 MHz | -49 dBm | 1 MHz | | +| NR Band n93 | 1427 – 1432 MHz | -52 dBm | 1 MHz | | +| | 880 – 915 MHz | -49 dBm | 1 MHz | | +| NR Band n94 | 1432 – 1517 MHz | -52 dBm | 1 MHz | | +| | 880 – 915 MHz | -49 dBm | 1 MHz | | +| NR Band n95 | 2010 – 2025 MHz | -52 dBm | 1 MHz | | +| NR Band n96 | 5925 – 7125 MHz | -52 dBm | 1 MHz | | +| NR Band n97 | 2300 – 2400 MHz | -52 dBm | 1 MHz | | +| NR Band n98 | 1880 – 1920 MHz | -52 dBm | 1 MHz | | +| NR Band n99 | 1626.5 – 1660.5 MHz | -49 dBm | 1 MHz | | +| NR Band n100 | 919.4 – 925 MHz | -52 dBm | 1 MHz | | +| | 874.4 – 880 MHz | -49 dBm | 1 MHz | | +| NR Band n101 | 1900 – 1910 MHz | -52 dBm | 1 MHz | | +| NR Band n102 | 5925 – 6425 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 103 | 757 – 758 MHz | -52 dBm | 1 MHz | | +| | 787 – 788 MHz | -49 dBm | 1 MHz | | +| NR band n104 | 6425 – 7125 MHz | -52 dBm | 1 MHz | | +| NR Band n105 | 612 – 652 MHz | -52 dBm | 1 MHz | | +| | 663 – 703 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 106 or NR Band n106 | 935 – 940 MHz | -52 dBm | 1 MHz | | +| NR Band n109 | 896 – 901 MHz | -49 dBm | 1 MHz | | +| | 1432 – 1517 MHz | -52 dBm | 1 MHz | | +| | 703 – 733 MHz | -49 dBm | 1 MHz | | + +NOTE 1: As defined in the scope for spurious emissions in this clause the co-existence requirements in table 6.6.5.2.2-1 do not apply for the $\Delta f_{\text{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.6.5.2.2-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.6.5.2.3 Co-location with base stations and IAB-Nodes + +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. + +The *basic limits* are in table 6.6.5.2.3-1 for an IAB-DU and IAB-MT. Requirements for co-location with a system listed in the first column apply, depending on the declared IAB-DU and IAB-MT class. For a *multi-band connector*, the exclusions and conditions in the Note column of table 6.6.5.2.3-1 shall apply for each supported *operating band*. + +**Table 6.6.5.2.3-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 | Basic 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 | -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 | | +| 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 | 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 | | +| 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 IAB-DU and IAB-MT operating in Band n77 or n78 | +| E-UTRA Band 23 | 2000 – 2020 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | + +| | | | | | | | +|-----------------------------------------------------|---------------------|---------|---------|---------|---------|--------------------------------------------------------------------------| +| E-UTRA Band 24 | 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 | | +| 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 | | +| 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 | | +| UTRA TDD Band f) or E-UTRA Band 39 or NR band n39 | 1880 – 1920MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA TDD Band e) or E-UTRA Band 40 or NR Band n40 | 2300 – 2400MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| 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 IAB-DU and IAB-MT operating in Band n41 | +| E-UTRA Band 42 | 3400 – 3600 MHz | -96 dBm | -91 dBm | -88 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 | -96 dBm | -91 dBm | -88 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 | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| 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 | | +| E-UTRA Band 48 or NR Band n48 | 3550 – 3700 MHz | -96 dBm | -91 dBm | -88 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 | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 51 or NR Band n51 | 1427 – 1432 MHz | N/A | N/A | -88 dBm | 100 kHz | | + +| | | | | | | | +|-------------------------------|-------------------|---------|---------|---------|---------|--------------------------------------------------------------------------| +| 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 IAB-DU and IAB-MT operating in Band n41 | +| E-UTRA Band 54 or NR Band n54 | 1670 – 1675 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 65 or NR Band n65 | 1920 – 2010 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| 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 | | +| NR Band n77 | 3.3 – 4.2 GHz | -96 dBm | -91 dBm | -88 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 | -96 dBm | -91 dBm | -88 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 | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to IAB-DU and IAB-MT operating in Band n79 | +| 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 – 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 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 | | +| 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.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 [4]. + +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.6.5.3 Minimum requirements for IAB-DU and IAB-MT type 1-H + +The Tx spurious emissions requirements for *IAB-DU type 1-H* and *IAB-MT type 1-H* are that for each *TAB connector TX min cell group* and each applicable *basic limit* in clause 6.6.5.2, the power summation of 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 *IAB-DU type 1-H* and *IAB-MT 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 *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 General + +The transmitter intermodulation requirement is a measure of the capability of the transmitter unit to inhibit the generation of signals in its non-linear elements caused by presence of the wanted signal and an interfering signal reaching the transmitter unit via the antenna, RDN and antenna array. The requirement shall apply during the *transmitter ON period* and the *transmitter transient period*. + +For *IAB 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 *IAB 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 or IAB. +- 2) Intra-system transmitter intermodulation in which the interfering signal is from other transmitter units within the *IAB type 1-H*. + +For *IAB 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 intermodulation requirement. + +## 6.7.2 Minimum requirements for *IAB-DU type 1-H* and *IAB-MT type 1-H* + +### 6.7.2.1 Co-location minimum requirements + +The transmitter intermodulation level shall not exceed the unwanted emission limits in clauses 7.6 in the presence of an NR interfering signal according to table 6.7. 2.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 *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 *IAB RF Bandwidth edges* of each *operating band*. In case the *inter RF Bandwidth gap* is less than $3 \cdot BW_{\text{Channel}}$ (where $BW_{\text{Channel}}$ is the minimal *IAB-DU channel bandwidth* or *IAB-MT 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. 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 IAB channel bandwidth ( $BW_{\text{Channel}}$ ) with 15 kHz SCS of the band defined in clause 5.3.5. | +| 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.2.2 Intra-system minimum requirements + +The transmitter intermodulation level shall not exceed the unwanted emission limits in clauses 6.6 in the presence of an NR interfering signal according to table 6.7. 2.2-1. + +**Table 6.7.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 IAB channel bandwidth and SCS as the wanted signal (Note 1). | +| Interfering signal level | Power level declared by the IAB manufacturer (Note 2). | +| Frequency offset between interfering signal and wanted signal | 0 MHz | +| NOTE 1: | The interfering signal shall be incoherent with the wanted signal. | +| NOTE 2: | The declared interfering signal power level at each TAB connector is the sum of the co-channel leakage power coupled via the combined RDN and Antenna Array from all the other TAB connectors , but does not comprise power radiated from the Antenna Array and reflected back from the environment. The power at each of the interfering TAB connectors is $P_{\text{rated,c,TABC}}$ . | + +## 7 Conducted receiver characteristics + +### 7.1 General + +Conducted receiver characteristics are specified at *TAB connector* for IAB 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 receive period. +- Requirements shall be met for any transmitter setting. +- Throughput requirements defined for the conducted receiver characteristics do not assume HARQ retransmissions. +- When IAB-DU or IAB-MT 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-DU and IAB-MT in TDD operation are configured to TX OFF power during *receive period*. + +## 7.2 Reference sensitivity level + +### 7.2.1 IAB-DU reference sensitivity level + +#### 7.2.1.1 General + +The reference sensitivity power level $P_{\text{REFSENS}}$ is the minimum mean power received at the *TAB connector* for IAB-DU type 1-H at which a throughput requirement shall be met for a specified reference measurement channel. + +### 7.2.1.2 Minimum requirements for IAB-DU type 1-H + +The wide area IAB-DU reference sensitivity level is specified the same as the wide area BS reference sensitivity level requirement for BS type 1-H in TS 38.104 [2], subclause 7.2.2, where references to BS channel bandwidth apply to IAB-DU channel bandwidth. + +The medium range IAB-DU reference sensitivity level is specified the same as the medium range BS reference sensitivity level requirement for BS type 1-H in TS 38.104 [2], subclause 7.2.2, where references to BS channel bandwidth apply to IAB-DU channel bandwidth. + +The local area IAB-DU reference sensitivity level is specified the same as the local area BS reference sensitivity level requirement for BS type 1-H in TS 38.104 [2], subclause 7.2.2, where references to BS channel bandwidth apply to IAB-DU channel bandwidth. + +Referenced requirements applying to NB IoT are not applicable to the IAB-DU + +## 7.2.2 IAB-MT reference sensitivity level + +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 for Wide Area IAB-MT and in table 7.2.2-2 for Local Area IAB-MT. + +**Table 7.2.2-1: Void** + +**Table 7.2.2-2: Void** + +### 7.2.2.1 General + +The reference sensitivity power level $P_{\text{REFSENS}}$ is the minimum mean power received at the TAB connector for IAB-MT type 1-H at which a throughput requirement shall be met for a specified reference measurement channel. + +### 7.2.2.2 Minimum requirements for IAB-MT 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.2-1 for Wide Area IAB-MT and in table 7.2.2.2-2 for Local Area IAB-MT. + +**Table 7.2.2.2-1: Wide Area IAB-MT reference sensitivity levels** + +| IAB-MT channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel | Reference sensitivity power level, $P_{\text{REFSENS}}$ (dBm) | +|-------------------------------------------------|---------------------------|-------------------------------|---------------------------------------------------------------| +| 10, 15 | 30 | G-FR1-A1-22 (Note 1) | -102.0 | +| 10, 15 | 60 | G-FR1-A1-23 (Note 1) | -99.0 | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-25 (Note 1) | -95.4 | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-26 (Note 1) | -95.6 | + +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 IAB-MT channel bandwidth. + +**Table 7.2.2.2-2: Local Area IAB-MT reference sensitivity levels** + +| IAB-MT channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel | Reference sensitivity power level, P_{\text{REFSENS}} (dBm) | +|-------------------------------------------------|----------------------------------|--------------------------------------|---------------------------------------------------------------------------------| +| 10, 15 | 30 | G-FR1-A1-22 (Note 1) | -94.0 | +| 10, 15 | 60 | G-FR1-A1-23 (Note 1) | -91.0 | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-25 (Note 1) | -87.4 | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-26 (Note 1) | -87.6 | + +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 IAB-MT channel bandwidth. + +## 7.3 Dynamic range + +### 7.3.1 IAB-DU dynamic range + +#### 7.3.1.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 *IAB-DU type 1-H* inside the received *IAB-DU 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.1.2 Minimum requirement for *IAB-DU type 1-H* + +The wide area IAB-DU dynamic range is specified the same as the wide area BS dynamic requirement for BS *type 1-H* in TS 38.104 [2], subclause 7.3.2, where references to *BS channel bandwidth* apply to *IAB-DU channel bandwidth*. + +The medium range IAB-DU dynamic range is specified the same as the medium range BS dynamic range requirement for BS *type 1-H* in TS 38.104 [2], subclause 7.3.2, where references to *BS channel bandwidth* apply to *IAB-DU channel bandwidth*. + +The local area IAB-DU dynamic range is specified the same as the local area BS dynamic range requirement for BS *type 1-H* in TS 38.104 [2], subclause 7.3.2, where references to *BS channel bandwidth* apply to *IAB-DU channel bandwidth*. + +Referenced requirements applying to NB IoT are not applicable to the IAB-DU + +## 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 the *TAB connector* for *IAB-MT type 1-H* or *IAB-DU type 1-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 for *IAB-DU type 1-H* + +Minimum requirement is the same as specified for BS type 1-H in TS38.104[2], subclause 7.4.1.2. + +#### 7.4.1.3 Minimum requirement for *IAB-MT type 1-H* + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel. + +For IAB-MT, the wanted and the interfering signal coupled to the *IAB-MT type 1-H TAB connector* are specified in table 7.4.1.3-1 and the frequency offset between the wanted and interfering signal in table 7.4.1.3-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 *IAB-MT channel bandwidth* and further specified in annex A.1. The characteristics of the interfering signal is further specified in annex F. + +The ACS requirement is applicable 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 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.3-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.3-2. The interfering signal offset is defined relative to the *IAB-MT RF Bandwidth* edges inside the *Inter RF Bandwidth gap*. + +Minimum conducted requirement is defined at the *TAB connector* for *IAB-MT type 1-H*. + +**Table 7.4.1.3-1: ACS requirement for IAB-MT** + +| IAB-MT channel bandwidth of the lowest/highest carrier received (MHz) | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | +|-----------------------------------------------------------------------------------------------------------------------|---------------------------------------|-------------------------------------------------| +| 10, 15, 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100
(Note 1) | $P_{\text{REFSENS}} + 6 \text{ dB}$ | Wide Area IAB-MT: -52
Local Area IAB-MT: -44 | +| NOTE 1: The SCS for the lowest/highest carrier received is the lowest SCS supported by the IAB-MT for that bandwidth. | | | + +**Table 7.4.1.3-2: IAB-MT ACS interferer frequency offset values** + +| 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.4.2 In-band blocking + +### 7.4.2.1 General + +The in-band blocking characteristics is a measure of the receiver's ability to receive a wanted signal at its assigned channel at the *TAB connector* for *IAB-DU type 1-H* and *IAB-MT 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 for IAB-DU type 1-H + +Minimum requirement is the same as specified for BS type 1-H in TS38.104[2], subclause 7.4.2.2. + +### 7.4.2.3 Minimum requirement for IAB-MT 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 *IAB-MT type 1-H TAB connector* using the parameters in tables 7.4.2.3-1, 7.4.2.3-2 and 7.4.2.3-3 for general blocking and narrowband blocking requirements. The reference measurement channel for the wanted signal is identified in clause 7.2.2 for each *IAB-MT channel bandwidth* and further specified in annex A.1. The characteristics of the interfering signal is further specified in annex F. + +The 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*. + +The 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 *wide area IAB-MT type 1-H* is defined in table 7.4.2.3-0. + +Minimum conducted requirement is defined at the *TAB connector* for *IAB-MT type 1-H*. + +**Table 7.4.2.3-0: $\Delta f_{OOB}$ offset for NR operating bands** + +| IAB-MT type | Operating band characteristics | $\Delta f_{OOB}$ (MHz) | +|------------------------|--------------------------------------------------------|------------------------| +| IAB-MT type 1-H | $F_{DL,high} - F_{DL,low} < 100$ MHz | 20 | +| | $100$ MHz $\leq F_{DL,high} - F_{DL,low} \leq 900$ MHz | 60 | + +For an IAB-MT 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 tables 7.4.2.3-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 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.4.2.3-1. + +For an IAB-MT operating in *non-contiguous spectrum* within any *operating band*, the narrowband blocking requirement shall apply 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.3-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 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.2.3-3. The interfering signal offset is defined relative to the *IAB-MT RF Bandwidth* edges inside the *Inter RF Bandwidth gap*. + +**Table 7.4.2.3-1: IAB-MT general blocking requirement** + +| 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 | $P_{\text{REFSENS}} + 6$ dB | Wide Area IAB-MT: -43
Local Area IAB-MT: -35 | $\pm 7.5$ | 5 MHz CP-OFDM NR signal
15 kHz SCS, 25 RBs | +| 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | $P_{\text{REFSENS}} + 6$ dB | Wide Area IAB-MT: -43
Local Area IAB-MT: -35 | $\pm 30$ | 20 MHz CP-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 IAB-MT channel bandwidth as specified in tables 7.2.2-1, 7.2.2-2. | | | | | + +**Table 7.4.2.3-2: IAB-MT narrowband blocking requirement** + +| IAB-MT channel bandwidth of the lowest/highest carrier received (MHz) | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------|-------------------------------------------------| +| 10, 15, 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 (Note 1) | $P_{\text{REFSENS}} + 6$ dB | Wide Area IAB-MT: -49
Local Area IAB-MT: -41 | +| NOTE 1: The SCS for the lowest/highest carrier received is the lowest SCS supported by the IAB-MT for that IAB-MT channel bandwidth
NOTE 2: $P_{\text{REFSENS}}$ depends on the IAB-MT channel bandwidth as specified in tables 7.2.2-1 and 7.2.2-2.
NOTE 3: 7.5 kHz shift is not applied to the wanted signal. | | | + +**Table 7.4.2.3-3: IAB-MT narrowband blocking interferer frequency offsets** + +| 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 | +|-----------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------| +| | | 5 MHz CP-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 CP-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 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 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 IAB-DU type 1-H and IAB-MT 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 Void + +### 7.5.3 Minimum requirement for IAB-DU type 1-H + +Minimum requirement is the same as specified for BS type 1-H in TS 38.104 [2], subclause 7.5.2. + +### 7.5.4 Co-location minimum requirements for IAB-DU type 1-H + +Minimum requirement is the same as specified for BS type 1-H in TS 38.104 [2], subclause 7.5.3. + +## 7.5.5 Minimum requirement for IAB-MT 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 *IAB-Node type 1-H TAB connector* using the parameters in table 7.5.5-2. The reference measurement channel for the wanted signal is identified in subclause 7.2.1 and subclause 7.2.2 for each *IAB-Node channel bandwidth* and further specified in annex A.1. + +The out-of-band blocking requirement apply from 1 MHz to $F_{DL,low} - \Delta f_{OOB}$ and from $F_{DL,high} + \Delta f_{OOB}$ up to 12750 MHz. The $\Delta f_{OOB}$ for *IAB-MT type 1-H* is defined in table 7.5.5-1. + +**Table 7.5.5-1: $\Delta f_{OOB}$ offset for NR operating bands** + +| IAB-MT type | Operating band characteristics | \Delta f_{OOB} (MHz) | +|--------------------|--------------------------------------------------------|------------------------------------------| +| type 1-H | $F_{DL,high} - F_{DL,low} < 100$ MHz | 20 | +| | $100$ MHz $\leq F_{DL,high} - F_{DL,low} \leq 900$ MHz | 60 | + +Minimum conducted requirement is defined and at the *TAB connector* for *IAB-MT type 1-H*. + +For a *multi-band connector*, the requirement in the out-of-band blocking frequency ranges apply for each *operating band*, with the exception that the in-band blocking frequency ranges of all supported *operating bands* according to clause 7.4.2.2 shall be excluded from the out-of-band blocking requirement. + +**Table 7.5.5-2: Out-of-band blocking performance requirement for NR** + +| Wanted Signal mean power (dBm) | Interfering Signal mean power (dBm) | Type of Interfering Signal | +|----------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------|-----------------------------------| +| $P_{REFSENS} + 6$ dB (Note) | -15 | CW carrier | +| NOTE 1: For NR, $P_{REFSENS}$ depends also on the IAB-MT channel bandwidth as specified in subclause 7.2.1 and subclause 7.2.2. | | | + +## 7.5.6 Co-location minimum requirements for IAB-MT type 1-H + +This additional blocking requirement may be applied for the protection of IAB-MT receivers when GSM, CDMA, UTRA, E-UTRA, NR BS or IAB-Node operating in a different frequency band are co-located with an IAB Node. The requirement is applicable to all *IAB-MT channel bandwidths* supported by the IAB Node. + +The requirements in this clause assume a 30 dB coupling loss between interfering transmitter and IAB Node 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 *IAB type 1-H TAB connector* input using the parameters in table 7.5.6-1 for all the IAB Node classes. The reference measurement channel for the wanted signal is identified in subclause 7.2.1 and subclause 7.2.2 for each *IAB-MT channel bandwidth* and further specified in annex A.1. + +The blocking requirement for co-location with BS or IAB-Node in other bands is applied for all *operating bands* for which co-location protection is provided. + +Minimum conducted requirement is defined at the *TAB connector* for *IAB-MT type 1-H*. + +**Table 7.5.6-1: Blocking performance requirement for the IAB Node** + +| Frequency range of interfering signal | Wanted signal mean power (dBm) | Interfering signal mean power for WA IAB Node (dBm) | Interfering signal mean power for LA IAB Node (dBm) | Type of interfering signal | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------|-----------------------------------------------------|-----------------------------------------------------|----------------------------| +| Frequency range of co-located downlink operating band | $P_{\text{REFSENS}} + 6\text{dB}$ (Note 1) | +16 | $x$ (Note 2) | CW carrier | +| NOTE 1: $P_{\text{REFSENS}}$ depends on the IAB-MT channel bandwidth as specified in subclause 7.2.1 and subclause 7.2.2.
NOTE 2: $x = -7\text{ dBm}$ for IAB-MT co-located with Pico GSM850 or Pico CDMA850
$x = -4\text{ dBm}$ for IAB-MT co-located with Pico DCS1800 or Pico PCS1900
$x = -6\text{ dBm}$ for IAB-MT 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 downlink operating band(s) or in $\Delta f_{\text{OOB}}$ immediately outside any of the supported downlink operating band(s) . | | | | | + +## 7.6 Receiver spurious emissions + +### 7.6.1 General + +The receiver spurious emissions power is the power of emissions generated or amplified in a receiver unit that appear at the *TAB connector* (for IAB-DU type 1-H and IAB-MT type 1-H). The requirements apply to all IAB-DU and IAB-MT with separate RX and TX *TAB connectors*. + +For *TAB connectors* supporting both RX and TX in TDD, the requirements apply during the *transmitter OFF period*. + +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 IAB-DU type 1-H and IAB-MT type 1-H manufacturer shall declare *TAB connector RX min cell groups*. The declaration is done separately for IAB-DU and IAB-MT. Every *TAB connector* of IAB-DU type 1-H and IAB-MT 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_{\text{RXU,counted}}$ ) for IAB-DU type 1-H and IAB-MT type 1-H is calculated as follows: + +$$N_{\text{RXU,counted}} = \min(N_{\text{RXU,active}}, 8 \times N_{\text{cells}})$$ + +$N_{\text{RXU,countedpercell}}$ is used for scaling of *basic limits* and is derived as $N_{\text{RXU,countedpercell}} = N_{\text{RXU,counted}} / N_{\text{cells}}$ , where $N_{\text{cells}}$ is defined in clause 6.1. + +NOTE: $N_{\text{RXU,active}}$ is the number of actually active receiver units and is independent to the declaration of $N_{\text{cells}}$ . + +### 7.6.2 IAB-DU receiver spurious emissions + +#### 7.6.2.1 Basic limits + +The receiver spurious emissions *basic limits* are provided in table 7.6.2.1-1. + +**Table 7.6.2.1-1: General IAB-DU 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 | + +NOTE 1: Measurement bandwidths as in ITU-R SM.329 [16], s4.1. +NOTE 2: Upper frequency as in ITU-R SM.329 [16], 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.6.1]. For multi-band connectors, the exclusion applies for all supported operating bands. + +## 7.6.2.2 Minimum requirement for IAB-DU type 1-H + +The RX spurious emissions requirements for IAB-DU type 1-H are that for each applicable basic limit specified in table 7.6.2.1-1 for each TAB connector RX min cell group, the power sum of emissions at 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 IAB-DU 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 IAB-DU 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 IAB-DU limit as defined above for the respective frequency span, scaled by $-10\log_{10}(n)$ , where $n$ is the number of TAB connectors in the TAB connector RX min cell group. + +## 7.6.3 IAB-MT receiver spurious emissions + +### 7.6.3.1 Basic limits + +The IAB-MT receiver spurious emissions basic limits are provided in table 7.6.3.1-1. + +**Table 7.6.3.1-1: General IAB-MT 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 DL operating band in GHz | -47 dBm | 1 MHz | Note 1, Note 2, Note 3 | + +NOTE 1: Measurement bandwidths as in ITU-R SM.329 [16], s4.1. +NOTE 2: Upper frequency as in ITU-R SM.329 [16], 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: The frequency range from $\Delta f_{\text{OBUE}}$ below the lowest frequency of the IAB-MT transmitter operating band to $\Delta f_{\text{OBUE}}$ above the highest frequency of the IAB-MT transmitter operating band may be excluded from the requirement. $\Delta f_{\text{OBUE}}$ is defined in clause [6.6.1]. For multi-band connectors, the exclusion applies for all supported operating bands. + +### 7.6.3.2 Minimum requirement for IAB-MT type 1-H + +The RX spurious emissions requirements for IAB-MT type 1-H are that for each applicable basic limit specified in table 7.6.3.1-1 for each TAB connector RX min cell group, the power sum of emissions at respective TAB connectors shall not exceed the IAB-MT limits specified as the basic limits + X, where $X = 10\log_{10}(N_{\text{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 IAB-MT. + +NOTE: Conformance to the IAB-MT 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 IAB-MT 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 IAB-MT limit as defined above for the respective frequency span, scaled by $-10\log_{10}(n)$ , where $n$ is the number of TAB connectors in the TAB connector RX min cell group. + +## 7.7 Receiver intermodulation + +### 7.7.1 General + +Third and higher order mixing of the two interfering RF signals can produce an interfering signal in the band of the desired channel. Intermodulation response rejection is a measure of the capability of the receiver to receive a wanted signal on its assigned channel frequency at TAB connector for IAB-DU type 1-H [and IAB-MT 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 for IAB-DU type 1-H + +The Wide Area IAB-DU receiver intermodulation requirement is specified the same as the Wide Area receiver intermodulation requirement for BS type 1-H in TS 38.104[2], subclause 7.7.2, where references to BS channel bandwidth apply to IAB-DU channel bandwidth. + +The Medium Range IAB-DU receiver intermodulation requirement is specified the same as the Medium Range BS receiver intermodulation requirement for BS type 1-H in TS 38.104[2], subclause 7.7.2, where references to BS channel bandwidth apply to IAB-DU channel bandwidth. + +The Local Area IAB-DU receiver intermodulation requirement is specified the same as the Local Area BS receiver intermodulation requirement for BS *type 1-H* in TS 38.104[2], subclause 7.7.2, where references to *BS channel bandwidth* apply to *IAB-DU channel bandwidth*. + +Referenced requirements applying to NB-IoT are not applicable to the IAB-DU + +### 7.7.3 Minimum requirement for *IAB-MT type 1-H* + +The Wide Area IAB-MT receiver intermodulation requirement is specified the same as the Wide Area receiver intermodulation requirement for BS *type 1-H* in TS 38.104[2], subclause 7.7.2, where references to *BS channel bandwidth* apply to *IAB-MT channel bandwidth*. + +The Local Area IAB-MT receiver intermodulation requirement is specified the same as the Local Area BS receiver intermodulation requirement for BS *type 1-H* in TS 38.104[2], subclause 7.7.2, where references to *BS channel bandwidth* apply to *IAB-MT channel bandwidth*. + +Interfering signal for IAB-MT *type 1-H* should be CP-OFDM + +## 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 *TAB connector* for *IAB-DU 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 for *IAB-DU type 1-H* + +The wide area IAB-DU receiver in-channel selectivity requirement is specified the same as the wide area receiver in-channel selectivity requirement for BS *type 1-H* in TS 38.104[2], subclause 7.8.2, where references to *BS channel bandwidth* apply to *IAB-DU channel bandwidth*. + +The medium range IAB-DU receiver in-channel selectivity requirement is specified the same as the medium range BS receiver in-channel selectivity requirement for BS *type 1-H* in TS 38.104[2], subclause 7.8.2, where references to *BS channel bandwidth* apply to *IAB-DU channel bandwidth*. + +The local area IAB-DU receiver in-channel selectivity requirement is specified the same as the local area BS receiver in-channel selectivity requirement for BS *type 1-H* in TS 38.104[2], subclause 7.8.2, where references to *BS channel bandwidth* apply to *IAB-DU channel bandwidth*. + +Referenced requirements applying to NB-IoT are not applicable to the IAB-DU + +--- + +## 8 Conducted performance requirements + +### 8.1 IAB-DU performance requirements + +#### 8.1.1 General + +Conducted performance requirements specify the ability of the IAB type 1-H to correctly demodulate signals in various conditions and configurations. Conducted performance requirements are specified at the TAB connector(s). + +Conducted performance requirements for the IAB-DU are specified for the fixed reference channels defined in annex A and the propagation conditions in annex I. The requirements only apply to those FRCs that are supported by the IAB-DU. + +Unless stated otherwise, performance requirements apply for a single carrier only. Performance requirements for an IAB-DU supporting carrier aggregation are defined in terms of single carrier requirements. + +The SNR used in this clause is specified based on a single carrier and defined as: + +$$\text{SNR} = S / N$$ + +Where: + +S is the total signal energy in the slot on a single TAB connector. + +N is the noise energy in a bandwidth corresponding to the transmission bandwidth over the duration of a slot on a single TAB connector. + +## 8.1.2 Performance requirements for PUSCH + +### 8.1.2.1 Requirements for PUSCH with transform precoding disabled + +#### 8.1.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.1.2.1.1-1: 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 | +| Cyclic prefix | | Normal | +| 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}, {0, 1} | +| | 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 | +| TPMI index for 2Tx two-layer spatial multiplexing transmission | | 0 | +| Code block group based PUSCH transmission | | Disabled | +| NOTE 1: The same requirements are applicable to different UL-DL patterns. | | | + +#### 8.1.2.1. Minimum requirements + +The throughput shall be equal to or larger than 70% of the maximum throughput for the FRCs stated in tables 8.1.2.1.2-1 to 8.1.2.1.2-14 at the given SNR for 1Tx or for 2Tx two-layer spatial multiplexing transmission. FRCs are defined in annex A. + +**Table 8.1.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 Demodulation Branches | Propagation conditions and correlation matrix (Annex I) | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|---------------|---------------------------|----------| +| 1 | 2 | TDLB100-400 Low | D-FR1-A.2.1-1 | pos1 | -2.3 | +| | | TDLC300-100 Low | D-FR1-A.2.3-1 | pos1 | 10.1 | +| | | TDLA30-10 Low | D-FR1-A.2.4-1 | pos1 | 12.3 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-1 | pos1 | -5.8 | +| | | TDLC300-100 Low | D-FR1-A.2.3-1 | pos1 | 6.2 | +| | | TDLA30-10 Low | D-FR1-A.2.4-1 | pos1 | 8.8 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-1 | pos1 | -8.7 | +| | | TDLC300-100 Low | D-FR1-A.2.3-1 | pos1 | 3.0 | +| | | TDLA30-10 Low | D-FR1-A.2.4-1 | pos1 | 5.6 | +| 2 | 2 | TDLB100-400 Low | D-FR1-A.2.1-8 | pos1 | 1.0 | +| | | TDLC300-100 Low | D-FR1-A.2.3-8 | pos1 | 18.2 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-8 | pos1 | -2.3 | +| | | TDLC300-100 Low | D-FR1-A.2.3-8 | pos1 | 11.0 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-8 | pos1 | -5.3 | +| | | TDLC300-100 Low | D-FR1-A.2.3-8 | pos1 | 6.8 | + +**Table 8.1.2.1.2-2: Minimum 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 I) | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|---------------|---------------------------|----------| +| 1 | 2 | TDLB100-400 Low | D-FR1-A.2.1-2 | pos1 | -2.5 | +| | | TDLC300-100 Low | D-FR1-A.2.3-2 | pos1 | 10.2 | +| | | TDLA30-10 Low | D-FR1-A.2.4-2 | pos1 | 12.2 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-2 | pos1 | -6.0 | +| | | TDLC300-100 Low | D-FR1-A.2.3-2 | pos1 | 6.3 | +| | | TDLA30-10 Low | D-FR1-A.2.4-2 | pos1 | 8.6 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-2 | pos1 | -8.7 | +| | | TDLC300-100 Low | D-FR1-A.2.3-2 | pos1 | 3.1 | +| | | TDLA30-10 Low | D-FR1-A.2.4-2 | pos1 | 5.5 | +| 2 | 2 | TDLB100-400 Low | D-FR1-A.2.1-9 | pos1 | 1.7 | +| | | TDLC300-100 Low | D-FR1-A.2.3-9 | pos1 | 18.3 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-9 | pos1 | -2.0 | +| | | TDLC300-100 Low | D-FR1-A.2.3-9 | pos1 | 11.2 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-9 | pos1 | -5.5 | +| | | TDLC300-100 Low | D-FR1-A.2.3-9 | pos1 | 6.8 | + +**Table 8.1.2.1.2-3: Minimum 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 I) | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|----------| +| 1 | 2 | TDLB100-400 Low | D-FR1-A.2.1-3 | pos1 | -2.1 | +| | | TDLC300-100 Low | D-FR1-A.2.3-3 | pos1 | 10.0 | +| | | TDLA30-10 Low | D-FR1-A.2.4-3 | pos1 | 12.4 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-3 | pos1 | -5.5 | +| | | TDLC300-100 Low | D-FR1-A.2.3-3 | pos1 | 6.2 | +| | | TDLA30-10 Low | D-FR1-A.2.4-3 | pos1 | 8.6 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-3 | pos1 | -8.5 | +| | | TDLC300-100 Low | D-FR1-A.2.3-3 | pos1 | 3.0 | +| | | TDLA30-10 Low | D-FR1-A.2.4-3 | pos1 | 5.5 | +| 2 | 2 | TDLB100-400 Low | D-FR1-A.2.1-10 | pos1 | 2.1 | +| | | TDLC300-100 Low | D-FR1-A.2.3-10 | pos1 | 18.3 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-10 | pos1 | -1.8 | +| | | TDLC300-100 Low | D-FR1-A.2.3-10 | pos1 | 11.1 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-10 | pos1 | -5.3 | +| | | TDLC300-100 Low | D-FR1-A.2.3-10 | pos1 | 6.9 | + +**Table 8.1.2.1.2-4: Minimum 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 I) | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|----------| +| 1 | 2 | TDLB100-400 Low | D-FR1-A.2.1-4 | pos1 | -2.3 | +| | | TDLC300-100 Low | D-FR1-A.2.3-4 | pos1 | 10.2 | +| | | TDLA30-10 Low | D-FR1-A.2.4-4 | pos1 | 12.8 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-4 | pos1 | -5.6 | +| | | TDLC300-100 Low | D-FR1-A.2.3-4 | pos1 | 6.4 | +| | | TDLA30-10 Low | D-FR1-A.2.4-4 | pos1 | 8.6 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-4 | pos1 | -8.6 | +| | | TDLC300-100 Low | D-FR1-A.2.3-4 | pos1 | 3.3 | +| | | TDLA30-10 Low | D-FR1-A.2.4-4 | pos1 | 5.5 | +| 2 | 2 | TDLB100-400 Low | D-FR1-A.2.1-11 | pos1 | 1.3 | +| | | TDLC300-100 Low | D-FR1-A.2.3-11 | pos1 | 18.4 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-11 | pos1 | -2.2 | +| | | TDLC300-100 Low | D-FR1-A.2.3-11 | pos1 | 11.2 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-11 | pos1 | -5.2 | +| | | TDLC300-100 Low | D-FR1-A.2.3-11 | pos1 | 7.0 | + +**Table 8.1.2.1.2-5: Minimum 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 I) | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|----------| +| 1 | 2 | TDLB100-400 Low | D-FR1-A.2.1-5 | pos1 | -2.9 | +| | | TDLC300-100 Low | D-FR1-A.2.3-5 | pos1 | 10.2 | +| | | TDLA30-10 Low | D-FR1-A.2.4-5 | pos1 | 12.5 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-5 | pos1 | -6.0 | +| | | TDLC300-100 Low | D-FR1-A.2.3-5 | pos1 | 6.4 | +| | | TDLA30-10 Low | D-FR1-A.2.4-5 | pos1 | 8.6 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-5 | pos1 | -8.8 | +| | | TDLC300-100 Low | D-FR1-A.2.3-5 | pos1 | 3.2 | +| | | TDLA30-10 Low | D-FR1-A.2.4-5 | pos1 | 5.5 | +| 2 | 2 | TDLB100-400 Low | D-FR1-A.2.1-12 | pos1 | 1.3 | +| | | TDLC300-100 Low | D-FR1-A.2.3-12 | pos1 | 18.1 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-12 | pos1 | -2.2 | +| | | TDLC300-100 Low | D-FR1-A.2.3-12 | pos1 | 11.3 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-12 | pos1 | -5.3 | +| | | TDLC300-100 Low | D-FR1-A.2.3-12 | pos1 | 6.9 | + +**Table 8.1.2.1.2-6: Minimum 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 I) | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|----------| +| 1 | 2 | TDLB100-400 Low | D-FR1-A.2.1-6 | pos1 | -2.5 | +| | | TDLC300-100 Low | D-FR1-A.2.3-6 | pos1 | 10.0 | +| | | TDLA30-10 Low | D-FR1-A.2.4-6 | pos1 | 12.4 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-6 | pos1 | -5.8 | +| | | TDLC300-100 Low | D-FR1-A.2.3-6 | pos1 | 6.3 | +| | | TDLA30-10 Low | D-FR1-A.2.4-6 | pos1 | 8.5 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-6 | pos1 | -8.7 | +| | | TDLC300-100 Low | D-FR1-A.2.3-6 | pos1 | 3.1 | +| | | TDLA30-10 Low | D-FR1-A.2.4-6 | pos1 | 5.4 | +| 2 | 2 | TDLB100-400 Low | D-FR1-A.2.1-13 | pos1 | 1.3 | +| | | TDLC300-100 Low | D-FR1-A.2.3-13 | pos1 | 19.5 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-13 | pos1 | -2.3 | +| | | TDLC300-100 Low | D-FR1-A.2.3-13 | pos1 | 11.3 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-13 | pos1 | -5.2 | +| | | TDLC300-100 Low | D-FR1-A.2.3-13 | pos1 | 6.9 | + +**Table 8.1.2.1.2-7: Minimum 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 I) | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|----------| +| 1 | 2 | TDLB100-400 Low | D-FR1-A.2.1-7 | pos1 | -2.8 | +| | | TDLC300-100 Low | D-FR1-A.2.3-7 | pos1 | 10.2 | +| | | TDLA30-10 Low | D-FR1-A.2.4-7 | pos1 | 13.0 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-7 | pos1 | -5.8 | +| | | TDLC300-100 Low | D-FR1-A.2.3-7 | pos1 | 6.5 | +| | | TDLA30-10 Low | D-FR1-A.2.4-7 | pos1 | 9.0 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-7 | pos1 | -8.7 | +| | | TDLC300-100 Low | D-FR1-A.2.3-7 | pos1 | 3.2 | +| | | TDLA30-10 Low | D-FR1-A.2.4-7 | pos1 | 5.8 | +| 2 | 2 | TDLB100-400 Low | D-FR1-A.2.1-14 | pos1 | 1.4 | +| | | TDLC300-100 Low | D-FR1-A.2.3-14 | pos1 | 19.2 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-14 | pos1 | -2.2 | +| | | TDLC300-100 Low | D-FR1-A.2.3-14 | pos1 | 11.6 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-14 | pos1 | -5.2 | +| | | TDLC300-100 Low | D-FR1-A.2.3-14 | pos1 | 7.1 | + +**Table 8.1.2.1.2-8: Minimum 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 I) | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|---------------|---------------------------|----------| +| 1 | 2 | TDLB100-400 Low | D-FR1-A.2.1-1 | pos1 | -2.3 | +| | | TDLC300-100 Low | D-FR1-A.2.3-1 | pos1 | 10.2 | +| | | TDLA30-10 Low | D-FR1-A.2.4-1 | pos1 | 12.5 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-1 | pos1 | -5.7 | +| | | TDLC300-100 Low | D-FR1-A.2.3-1 | pos1 | 6.3 | +| | | TDLA30-10 Low | D-FR1-A.2.4-1 | pos1 | 8.9 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-1 | pos1 | -8.7 | +| | | TDLC300-100 Low | D-FR1-A.2.3-1 | pos1 | 3.0 | +| | | TDLA30-10 Low | D-FR1-A.2.4-1 | pos1 | 5.7 | +| 2 | 2 | TDLB100-400 Low | D-FR1-A.2.1-8 | pos1 | 1.5 | +| | | TDLC300-100 Low | D-FR1-A.2.3-8 | pos1 | 18.3 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-8 | pos1 | -2.3 | +| | | TDLC300-100 Low | D-FR1-A.2.3-8 | pos1 | 11.1 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-8 | pos1 | -5.4 | +| | | TDLC300-100 Low | D-FR1-A.2.3-8 | pos1 | 6.8 | + +**Table 8.1.2.1.2-9: Minimum 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 I) | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|---------------|---------------------------|----------| +| 1 | 2 | TDLB100-400 Low | D-FR1-A.2.1-2 | pos1 | -2.3 | +| | | TDLC300-100 Low | D-FR1-A.2.3-2 | pos1 | 10.5 | +| | | TDLA30-10 Low | D-FR1-A.2.4-2 | pos1 | 12.6 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-2 | pos1 | -5.7 | +| | | TDLC300-100 Low | D-FR1-A.2.3-2 | pos1 | 6.5 | +| | | TDLA30-10 Low | D-FR1-A.2.4-2 | pos1 | 8.9 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-2 | pos1 | -9.0 | +| | | TDLC300-100 Low | D-FR1-A.2.3-2 | pos1 | 3.2 | +| | | TDLA30-10 Low | D-FR1-A.2.4-2 | pos1 | 5.8 | +| 2 | 2 | TDLB100-400 Low | D-FR1-A.2.1-9 | pos1 | 2.0 | +| | | TDLC300-100 Low | D-FR1-A.2.3-9 | pos1 | 18.7 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-9 | pos1 | -2.3 | +| | | TDLC300-100 Low | D-FR1-A.2.3-9 | pos1 | 11.3 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-9 | pos1 | -5.2 | +| | | TDLC300-100 Low | D-FR1-A.2.3-9 | pos1 | 7.0 | + +**Table 8.1.2.1.2-10: Minimum 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 I) | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|----------| +| 1 | 2 | TDLB100-400 Low | D-FR1-A.2.1-3 | pos1 | -2.1 | +| | | TDLC300-100 Low | D-FR1-A.2.3-3 | pos1 | 10.4 | +| | | TDLA30-10 Low | D-FR1-A.2.4-3 | pos1 | 12.3 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-3 | pos1 | -5.7 | +| | | TDLC300-100 Low | D-FR1-A.2.3-3 | pos1 | 6.3 | +| | | TDLA30-10 Low | D-FR1-A.2.4-3 | pos1 | 8.8 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-3 | pos1 | -8.5 | +| | | TDLC300-100 Low | D-FR1-A.2.3-3 | pos1 | 3.1 | +| | | TDLA30-10 Low | D-FR1-A.2.4-3 | pos1 | 5.7 | +| 2 | 2 | TDLB100-400 Low | D-FR1-A.2.1-10 | pos1 | 1.6 | +| | | TDLC300-100 Low | D-FR1-A.2.3-10 | pos1 | 18.1 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-10 | pos1 | -2.0 | +| | | TDLC300-100 Low | D-FR1-A.2.3-10 | pos1 | 11.2 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-10 | pos1 | -5.3 | +| | | TDLC300-100 Low | D-FR1-A.2.3-10 | pos1 | 6.9 | + +**Table 8.1.2.1.2-11: Minimum 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 I) | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|----------| +| 1 | 2 | TDLB100-400 Low | D-FR1-A.2.1-4 | pos1 | -2.4 | +| | | TDLC300-100 Low | D-FR1-A.2.3-4 | pos1 | 10.1 | +| | | TDLA30-10 Low | D-FR1-A.2.4-4 | pos1 | 12.5 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-4 | pos1 | -5.7 | +| | | TDLC300-100 Low | D-FR1-A.2.3-4 | pos1 | 6.4 | +| | | TDLA30-10 Low | D-FR1-A.2.4-4 | pos1 | 8.6 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-4 | pos1 | -8.8 | +| | | TDLC300-100 Low | D-FR1-A.2.3-4 | pos1 | 3.2 | +| | | TDLA30-10 Low | D-FR1-A.2.4-4 | pos1 | 5.6 | +| 2 | 2 | TDLB100-400 Low | D-FR1-A.2.1-11 | pos1 | 1.1 | +| | | TDLC300-100 Low | D-FR1-A.2.3-11 | pos1 | 18.5 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-11 | pos1 | -2.5 | +| | | TDLC300-100 Low | D-FR1-A.2.3-11 | pos1 | 11.3 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-11 | pos1 | -5.6 | +| | | TDLC300-100 Low | D-FR1-A.2.3-11 | pos1 | 7.0 | + +**Table 8.1.2.1.2-12: Minimum 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 I) | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|----------| +| 1 | 2 | TDLB100-400 Low | D-FR1-A.2.1-5 | pos1 | -2.9 | +| | | TDLC300-100 Low | D-FR1-A.2.3-5 | pos1 | 10.1 | +| | | TDLA30-10 Low | D-FR1-A.2.4-5 | pos1 | 12.5 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-5 | pos1 | -6.0 | +| | | TDLC300-100 Low | D-FR1-A.2.3-5 | pos1 | 6.3 | +| | | TDLA30-10 Low | D-FR1-A.2.4-5 | pos1 | 8.6 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-5 | pos1 | -9.0 | +| | | TDLC300-100 Low | D-FR1-A.2.3-5 | pos1 | 3.1 | +| | | TDLA30-10 Low | D-FR1-A.2.4-5 | pos1 | 5.6 | +| 2 | 2 | TDLB100-400 Low | D-FR1-A.2.1-12 | pos1 | 1.3 | +| | | TDLC300-100 Low | D-FR1-A.2.3-12 | pos1 | 18.2 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-12 | pos1 | -2.3 | +| | | TDLC300-100 Low | D-FR1-A.2.3-12 | pos1 | 11.2 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-12 | pos1 | -5.4 | +| | | TDLC300-100 Low | D-FR1-A.2.3-12 | pos1 | 7.0 | + +**Table 8.1.2.1.2-13: Minimum 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 I) | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|----------| +| 1 | 2 | TDLB100-400 Low | D-FR1-A.2.1-6 | pos1 | -2.5 | +| | | TDLC300-100 Low | D-FR1-A.2.3-6 | pos1 | 10.0 | +| | | TDLA30-10 Low | D-FR1-A.2.4-6 | pos1 | 12.5 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-6 | pos1 | -5.8 | +| | | TDLC300-100 Low | D-FR1-A.2.3-6 | pos1 | 6.2 | +| | | TDLA30-10 Low | D-FR1-A.2.4-6 | pos1 | 8.7 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-6 | pos1 | -8.8 | +| | | TDLC300-100 Low | D-FR1-A.2.3-6 | pos1 | 3.0 | +| | | TDLA30-10 Low | D-FR1-A.2.4-6 | pos1 | 5.5 | +| 2 | 2 | TDLB100-400 Low | D-FR1-A.2.1-13 | pos1 | 1.7 | +| | | TDLC300-100 Low | D-FR1-A.2.3-13 | pos1 | 18.7 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-13 | pos1 | -2.1 | +| | | TDLC300-100 Low | D-FR1-A.2.3-13 | pos1 | 11.2 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-13 | pos1 | -5.2 | +| | | TDLC300-100 Low | D-FR1-A.2.3-13 | pos1 | 6.9 | + +**Table 8.1.2.1.2-14: Minimum 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 I) | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|----------| +| 1 | 2 | TDLB100-400 Low | D-FR1-A.2.1-7 | pos1 | -2.5 | +| | | TDLC300-100 Low | D-FR1-A.2.3-7 | pos1 | 10.1 | +| | | TDLA30-10 Low | D-FR1-A.2.4-7 | pos1 | 13.1 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-7 | pos1 | -5.8 | +| | | TDLC300-100 Low | D-FR1-A.2.3-7 | pos1 | 6.3 | +| | | TDLA30-10 Low | D-FR1-A.2.4-7 | pos1 | 9.2 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-7 | pos1 | -8.7 | +| | | TDLC300-100 Low | D-FR1-A.2.3-7 | pos1 | 3.1 | +| | | TDLA30-10 Low | D-FR1-A.2.4-7 | pos1 | 5.9 | +| 2 | 2 | TDLB100-400 Low | D-FR1-A.2.1-14 | pos1 | 1.6 | +| | | TDLC300-100 Low | D-FR1-A.2.3-14 | pos1 | 19.3 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-14 | pos1 | -2.2 | +| | | TDLC300-100 Low | D-FR1-A.2.3-14 | pos1 | 11.6 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-14 | pos1 | -5.3 | +| | | TDLC300-100 Low | D-FR1-A.2.3-14 | pos1 | 7.1 | + +## 8.1.2.2 Requirements for PUSCH with transform precoding enabled + +### 8.1.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.1.2.2.1-1: Test parameters for testing PUSCH** + +| Parameter | | Value | +|---------------------------------------------------------------------------|-------------------------------------------|--------------------------------------------------------------------------------------------------------------------| +| Transform precoding | | Enabled | +| Cyclic Prefix | | Normal | +| 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 different UL-DL patterns. | | | + +#### 8.1.2.2.2 Minimum requirements + +The throughput shall be equal to or larger than 70% of the maximum throughput for the FRCs stated in tables 8.1.2.2.2-1 to 8.1.2.2.2-4 at the given SNR. FRCs are defined in annex A. + +**Table 8.1.2.2.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 Demodulation Branches | Propagation conditions and correlation matrix (Annex I) | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|----------| +| 1 | 2 | TDLB100-400 Low | D-FR1-A.2.1-15 | pos1 | -2.4 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-15 | pos1 | -5.7 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-15 | pos1 | -8.5 | + +**Table 8.1.2.2.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 Demodulation Branches | Propagation conditions and correlation matrix (Annex I) | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|----------| +| 1 | 2 | TDLB100-400 Low | D-FR1-A.2.1-16 | pos1 | -2.5 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-16 | pos1 | -5.7 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-16 | pos1 | -8.4 | + +**Table 8.1.2.2.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 Demodulation Branches | Propagation conditions and correlation matrix (Annex I) | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|----------| +| 1 | 2 | TDLB100-400 Low | D-FR1-A.2.1-15 | pos1 | -2.3 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-15 | pos1 | -5.8 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-15 | pos1 | -8.6 | + +**Table 8.1.2.2.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 Demodulation Branches | Propagation conditions and correlation matrix (Annex I) | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|----------| +| 1 | 2 | TDLB100-400 Low | D-FR1-A.2.1-16 | pos1 | -2.7 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-16 | pos1 | -6.0 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-16 | pos1 | -8.8 | + +### 8.1.2.3 Requirements for UCI multiplexed on PUSCH + +#### 8.1.2.3.1 General + +In the tests for UCI multiplexed on PUSCH, the UCI information only contains CSI part 1 and CSI part 2 information, and there is no HACK/ACK information transmitted. + +The CSI part 1 block error probability (BLER) is defined as the probability of incorrectly decoding the CSI part 1 information when the CSI part 1 information is sent as follow: + +where: + +- #(false CSI part 1) denotes the number of incorrectly decoded CSI part 1 information transmitted occasions +- #(CSI part 1) denotes the number of CSI part 1 information transmitted occasions. + +The CSI part 2 block error probability is defined as the probability of incorrectly decoding the CSI part 2 information when the CSI part 2 information is sent as follows: + +where: + +- #(false CSI part 2) denotes the number of incorrectly decoded CSI part 2 information transmitted occasions +- #(CSI part 2) denotes the number of CSI part 2 information transmitted occasions. + +The number of UCI information bit payload per slot is defined for two cases as follows: + +- 5 bits in CSI part 1, 2 bits in CSI part 2 +- 20 bits in CSI part 1, 20 bits in CSI part 2 + +The 7bits UCI 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 part2 information. + +The 40bits UCI information case is assumed random information bit selection. + +In both tests, PUSCH data, CSI part 1 and CSI part 2 information are transmitted simultaneously. + +**Table 8.1.2.3.1-1: Test parameters for testing UCI on PUSCH** + +| Parameter | | Value | +|-------------------------------------------|-------------------------------------------------------------|-----------------------------------| +| Transform precoding | | Disabled | +| Default TDD UL-DL pattern (Note 1) | | 30 kHz SCS:
7D1S2U, S=6D:4G:4U | +| Cyclic Prefix | | Normal | +| 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 | +| UCI | 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 different UL-DL patterns. + +### 8.1.2.3.2 Minimum requirements + +The CSI part 1 block error probability shall not exceed 0.1% at the SNR in table 8.1.2.3.2-1 and table 8.1.2.3.2-2. The CSI part 2 block error probability shall not exceed 1% at the SNR given in table 8.1.2.3.2-3 and table 8.1.2.3.2-4. + +**Table 8.1.2.3.2-1: Minimum 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 I) | 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 | 5.4 | +| | 2 | TDLC300-100 Low | 40(20,20) | pos1 | D-FR1-A.2.3-4 | 4.3 | + +**Table 8.1.2.3.2-2: Minimum requirements for UCI multiplexed on PUSCH, Type B, CSI part 1, 10 MHz Channel Bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of Demodulation Branches | Propagation conditions and correlation matrix (Annex I) | 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 | 5.8 | +| | 2 | TDLC300-100 Low | 40(20,20) | pos1 | D-FR1-A.2.3-4 | 4.1 | + +**Table 8.1.2.3.2-3: Minimum requirements for UCI multiplexed on PUSCH, Type A, CSI part 2, 10 MHz Channel Bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of Demodulation Branches | Propagation conditions and correlation matrix (Annex I) | 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.2 | +| | 2 | TDLC300-100 Low | 40(20,20) | pos1 | D-FR1-A.2.3-4 | 2.4 | + +**Table 8.1.2.3.2-4: Minimum requirements for UCI multiplexed on PUSCH, Type B, CSI part 2, 10 MHz Channel Bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of Demodulation Branches | Propagation conditions and correlation matrix (Annex I) | 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.3 | +| | 2 | TDLC300-100 Low | 40(20,20) | pos1 | D-FR1-A.2.3-4 | 2.6 | + +### 8.1.3 Performance requirements for PUCCH + +#### 8.1.3.1 DTX to ACK probability + +##### 8.1.3.1.1 General + +The DTX to ACK probability, i.e. the probability that ACK is detected when nothing was sent: + +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.1.3.1.2 Minimum requirement + +The DTX to ACK probability shall not exceed 1% for all PUCCH formats carrying ACK/NACK bits: + +#### 8.1.3.2 Performance requirements for PUCCH format 0 + +##### 8.1.3.2.1 General + +The ACK missed detection probability is the probability of not detecting an ACK when an ACK was sent. + +**Table 8.1.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 | 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 | + +[The transient period as specified in TS 38.101-1 [3] clause 6.3.3.1 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.1.3.2.2 Minimum requirement + +The ACK missed detection probability shall not exceed 1% at the SNR given in table 8.1.3.2.2-1 and in table 8.1.3.2.2-2. + +**Table 8.1.3.2.2-1: Minimum requirements for PUCCH format 0 and 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Propagation conditions and correlation matrix (Annex I) | Number of OFDM symbols | Channel bandwidth / SNR (dB) | | | +|-----------------------|-----------------------|---------------------------------------------------------|------------------------|------------------------------|--------|--------| +| | | | | 5 MHz | 10 MHz | 20 MHz | +| 1 | 2 | TDLC300-100 Low | 1 | 9.4 | 8.8 | 9.3 | +| | | | 2 | 2.8 | 3.7 | 3.3 | +| 1 | 4 | TDLC300-100 Low | 1 | 3.0 | 2.9 | 3.2 | +| | | | 2 | -1.0 | -0.5 | -0.8 | +| 1 | 8 | TDLC300-100 Low | 1 | -1.1 | -1.1 | -1.1 | +| | | | 2 | -4.1 | -3.9 | -4.0 | + +**Table 8.1.3.2.2-2: Minimum requirements for PUCCH format 0 and 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Propagation conditions and correlation matrix (Annex I) | Number of OFDM symbols | Channel bandwidth / SNR (dB) | | | | +|-----------------------|-----------------------|---------------------------------------------------------|------------------------|------------------------------|--------|--------|---------| +| | | | | 10 MHz | 20 MHz | 40 MHz | 100 MHz | +| 1 | 2 | TDLC300-100 Low | 1 | 9.8 | 9.8 | 9.5 | 9.2 | +| | | | 2 | 4.2 | 3.6 | 3.8 | 3.5 | +| 1 | 4 | TDLC300-100 Low | 1 | 3.4 | 3.4 | 3.0 | 3.3 | +| | | | 2 | -0.3 | -0.4 | -0.5 | -0.8 | +| 1 | 8 | TDLC300-100 Low | 1 | -1.0 | -1.0 | -1.1 | -1.0 | +| | | | 2 | -3.7 | -3.8 | -4.0 | -3.9 | + +#### 8.1.3.3 Performance requirements for PUCCH format 1 + +##### 8.1.3.3.1 NACK to ACK requirements + +###### 8.1.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(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.1.3.3.1.1-1: Test Parameters** + +| Parameter | Test | +|------------------------------------------------------------|-------------------------------------------| +| Cyclic prefix | Normal | +| 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-1 [3] clause 6.3.3.1 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.1.3.3.1.2 Minimum requirements + +The NACK to ACK probability shall not exceed 0.1% at the SNR given in table 8.1.3.3.1.2-1 and table 8.1.3.3.1.2-2. + +**Table 8.1.3.3.1.2-1: Minimum requirements for PUCCH format 1 with 15 kHz SCS** + +| Number of TX antennas | Number of Demodulation Branches | Propagation conditions and correlation matrix (Annex I) | Channel bandwidth / SNR (dB) | | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------------|--------|--------| +| | | | 5 MHz | 10 MHz | 20 MHz | +| 1 | 2 | TDLC-300-100 Low | -3.8 | -3.6 | -3.6 | +| | 4 | TDLC-300-100 Low | -8.4 | -7.6 | -8.4 | +| | 8 | TDLC-300-100 Low | -11.8 | -11.4 | -11.4 | + +**Table 8.1.3.3.1.2-2: Minimum requirements for PUCCH format 1 with 30 kHz SCS** + +| Number of TX antennas | Number of Demodulation Branches | Propagation conditions and correlation matrix (Annex I) | Channel bandwidth / SNR (dB) | | | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------------|--------|--------|---------| +| | | | 10 MHz | 20 MHz | 40 MHz | 100 MHz | +| 1 | 2 | TDLC-300-100 Low | -2.8 | -3.3 | -3.9 | -3.5 | +| | 4 | TDLC-300-100 Low | -8.1 | -8.3 | -7.5 | -8.0 | +| | 8 | TDLC-300-100 Low | -11.5 | -11.2 | -11.6 | -11.3 | + +### 8.1.3.3.2 ACK missed detection requirements + +#### 8.1.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-1 [3] clause 6.3.3.1 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.1.3.3.2.2 Minimum requirements + +The ACK missed detection probability shall not exceed 1% at the SNR given in table 8.1.3.3.2.2-1 and in table 8.1.3.3.2.2-2. + +**Table 8.1.3.3.2.2-1: Minimum requirements for PUCCH format 1 with 15 kHz SCS** + +| Number of TX antennas | Number of Demodulation Branches | Propagation conditions and correlation matrix (Annex I) | Channel bandwidth / SNR (dB) | | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------------|--------|--------| +| | | | 5 MHz | 10 MHz | 20 MHz | +| 1 | 2 | TDLC-300-100 Low | -5.0 | -4.4 | -5.0 | +| | 4 | TDLC-300-100 Low | -8.6 | -8.2 | -8.5 | +| | 8 | TDLC-300-100 Low | -11.6 | -11.5 | -11.5 | + +**Table 8.1.3.3.2.2-2: Minimum requirements for PUCCH format 1 with 30 kHz SCS** + +| Number of TX antennas | Number of Demodulation Branches | Propagation conditions and correlation matrix (Annex I) | Channel bandwidth / SNR (dB) | | | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------------|--------|--------|---------| +| | | | 10 MHz | 20 MHz | 40 MHz | 100 MHz | +| 1 | 2 | TDLC-300-100 Low | -3.9 | -4.4 | -4.4 | -4.2 | +| | 4 | TDLC-300-100 Low | -8.0 | -8.1 | -8.4 | -8.3 | +| | 8 | TDLC-300-100 Low | -11.4 | -11.4 | -11.4 | -11.4 | + +### 8.1.3.4 Performance requirements for PUCCH format 2 + +#### 8.1.3.4.1 NACK to ACK requirements + +##### 8.1.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.1.3.4.1.1-1: Test Parameters** + +| Parameter | Value | +|--------------------------------------|----------------------------------------------| +| Cyclic Prefix | Normal | +| Modulation order | QSPK | +| 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$ | + +[The transient period as specified in TS 38.101-1 [3] 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.4.1.2 Minimum requirements + +The ACK missed detection probability shall not exceed 1% at the SNR given in table 8.1.3.4.1.2-1 and table 8.1.3.4.1.2-2 for 4UCI bits. + +**Table 8.1.3.4.1.2-1: Minimum requirements for PUCCH format 2 with 15 kHz SCS** + +| Number of TX antennas | Number of Demodulation Branches | Propagation conditions and correlation matrix (Annex I) | Channel bandwidth / SNR (dB) | | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------------|--------|--------| +| | | | 5 MHz | 10 MHz | 20 MHz | +| 1 | 2 | TDLC300-100 Low | 5.8 | 5.6 | 5.9 | +| | 4 | TDLC300-100 Low | 0.4 | 0.5 | 0.3 | +| | 8 | TDLC300-100 Low | -3.5 | -3.5 | -3.5 | + +**Table 8.1.3.4.1.2-2: Minimum requirements for PUCCH format 2 with 30 kHz SCS** + +| Number of TX antennas | Number of Demodulation Branches | Propagation conditions and correlation matrix (Annex I) | Channel bandwidth / SNR (dB) | | | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------------|--------|--------|---------| +| | | | 10 MHz | 20 MHz | 40 MHz | 100 MHz | +| 1 | 2 | TDLC300-100 Low | 5.5 | 5.6 | 5.5 | 5.7 | +| | 4 | TDLC300-100 Low | 0.3 | 0.2 | 0.3 | 0.4 | +| | 8 | TDLC300-100 Low | -3.6 | -3.6 | -3.5 | -3.3 | + +#### 8.1.3.4.2 UCI BLER performance requirements + +##### 8.1.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 part 2. + +[The transient period as specified in TS 38.101-1 [3] clause 6.3.3.1 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.1.3.4.2.1-1: Test Parameters** + +| Parameter | Value | +|--------------------------------------|----------------------------------------------| +| Cyclic Prefix | Normal | +| Modulation order | QSPK | +| First PRB prior to frequency hopping | 0 | +| Intra-slot frequency hopping | enabled | +| Frist 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.1.3.4.2.2 Minimum requirement + +The UCI block error probability shall not exceed 1% at the SNR given in table 8.2.3.4.2.2-1 and table 8.1.3.4.2.2-2 for 22 UCI bits. + +**Table 8.1.3.4.2.2-1: Minimum requirements for PUCCH format 2 with 15 kHz SCS** + +| Number of TX antennas | Number of Demodulation Branches | Channel bandwidth / SNR (dB) | | | +|-----------------------|---------------------------------|------------------------------|--------|--------| +| | | 5 MHz | 10 MHz | 20 MHz | +| 1 | 2 | 0.2 | 0.8 | 1.2 | +| | 4 | -3.6 | -3.2 | -3.2 | +| | 8 | -6.8 | -6.7 | -6.8 | + +**Table 8.1.3.4.2.2-2: Minimum requirements for PUCCH format 2 with 30 kHz SCS** + +| Number of TX antennas | Number of Demodulation Branches | Cyclic Prefix | Propagation conditions and correlation matrix (Annex I) | Channel bandwidth / SNR (dB) | | | | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|------------------------------|--------|--------|---------| +| | | | | 10 MHz | 20 MHz | 40 MHz | 100 MHz | +| 1 | 2 | Normal | TDLC300-100 Low | 0.5 | 1.1 | 0.4 | 0.3 | +| | 4 | Normal | TDLC300-100 Low | -3.3 | -2.9 | -3.3 | -3.4 | +| | 8 | Normal | TDLC300-100 Low | -5.8 | -5.8 | -6.7 | -5.9 | + +#### 8.1.3.5 Performance requirements for PUCCH format 3 + +##### 8.1.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 part 2. + +[The transient period as specified in TS 38.101-1 [3] clause 6.3.3.1 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.1.3.5.1-1: Test Parameters** + +| Parameter | Test 1 | Test 2 | +|--------------------------------------|----------------------------------------------|--------| +| Cyclic Prefix | Normal | | +| 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 | + +#### 8.1.3.5.2 Minimum requirements + +The UCI block error probability shall not exceed 1% at the SNR given in Table 8.2.3.5.2-1 and Table 8.2.3.5.2-2. + +**Table 8.2.3.5.2-1: Minimum requirements for PUCCH format 3 with 15 kHz SCS** + +| Test Number | Number of TX antennas | Number of Demodulation Branches | Additional DM-RS configuration | Channel bandwidth / SNR (dB) | | | +|-------------|-----------------------|---------------------------------|--------------------------------|------------------------------|--------|--------| +| | | | | 5 MHz | 10 MHz | 20 MHz | +| 1 | 1 | 2 | No additional DM-RS | 0.2 | 1.1 | 0.3 | +| | | | Additional DM-RS | -0.1 | 0.5 | -0.1 | +| | | 4 | No additional DM-RS | -3.8 | -3.3 | -3.8 | +| | | | Additional DM-RS | -4.3 | -4.0 | -4.0 | +| | | 8 | No additional DM-RS | -7.0 | -6.7 | -6.9 | +| | | | Additional DM-RS | -7.7 | -7.5 | -7.7 | +| 2 | 1 | 2 | No additional DM-RS | 1.4 | 2.2 | 2.0 | +| | | 4 | No additional DM-RS | -3.1 | -2.5 | -2.5 | +| | | 8 | No additional DM-RS | -6.5 | -6.0 | -6.2 | + +**Table 8.1.3.5.2-2: Minimum requirements for PUCCH format 3 with 30 kHz SCS** + +| Test Number | Number of TX antennas | Number of Demodulation Branches | Cyclic Prefix | Propagation conditions and correlation matrix (Annex I) | 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 | 0.9 | 0.6 | 0.6 | 0.9 | +| | | | | | Additional DM-RS | 0.5 | 0.3 | 0.0 | 0.1 | +| | | 4 | Normal | TDLC300-100 Low | No additional DM-RS | -3.1 | -3.4 | -3.2 | -3.5 | +| | | | | | Additional DM-RS | -3.7 | -4.1 | -4.0 | -4.2 | +| | | 8 | Normal | TDLC300-100 Low | No additional DM-RS | -6.6 | -6.7 | -6.8 | -6.8 | +| | | | | | Additional DM-RS | -7.5 | -7.6 | -7.6 | -7.7 | +| | | 2 | Normal | TDLC300-100 Low | No additional DM-RS | 1.8 | 2.0 | 2.0 | 1.5 | +| 2 | 1 | 4 | Normal | TDLC300-100 Low | No additional DM-RS | -2.9 | -3.0 | -2.4 | -3.0 | +| | | 8 | Normal | TDLC300-100 Low | No additional DM-RS | -6.4 | -6.0 | -6.4 | -6.2 | + +### 8.1.3.6 Performance requirements for PUCCH format 4 + +#### 8.1.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 part 2. + +[The transient period as specified in TS 38.101-1 [3] clause 6.3.3.1 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.1.3.6.1-1: Test parameters** + +| Parameter | Value | +|--------------------------------------|----------------------------------------------| +| Cyclic Prefix | Normal | +| 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.1.3.6.2 Minimum requirement + +The UCI block error probability shall not exceed 1% at the SNR given in Table 8.2.3.6.2-1 and Table 8.2.3.6.2-2. + +**Table 8.1.3.6.2-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 I) | Additional DM-RS configuration | Channel bandwidth / SNR (dB) | | | +|-----------------------|---------------------------------|---------------------------------------------------------|--------------------------------|------------------------------|--------|--------| +| | | | | 5 MHz | 10 MHz | 20 MHz | +| 1 | 2 | TDLC300-100 Low | No additional DM-RS | 1.8 | 2.6 | 2.2 | +| | | | Additional DM-RS | 1.6 | 2.4 | 1.8 | +| | 4 | TDLC300-100 Low | No additional DM-RS | -2.3 | -1.9 | -2.2 | +| | | | Additional DM-RS | -2.9 | -2.6 | -2.7 | +| | | | No additional DM-RS | -5.9 | -5.7 | -5.8 | +| | | | Additional DM-RS | -6.6 | -6.4 | -6.3 | + +**Table 8.1.3.6.2-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 I) | 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.1 | 2.8 | 3.1 | 2.8 | +| | | | Additional DM-RS | 2.8 | 2.3 | 3.1 | 2.2 | +| | 4 | TDLC300-100 Low | No additional DM-RS | -1.7 | -1.9 | -1.7 | -2.1 | +| | | | Additional DM-RS | -2.0 | -2.5 | -2.5 | -2.4 | +| | | | No additional DM-RS | -5.6 | -5.5 | -5.5 | -5.5 | +| | | | Additional DM-RS | -6.2 | -6.1 | -6.4 | -6.2 | + +### 8.1.3.7 Performance requirements for multi-slot PUCCH + +#### 8.1.3.7.1 General + +#### 8.1.3.7.2 Performance requirements for multi-slot PUCCH format 1 + +##### 8.1.3.7.2.1 ACK to NACK requirements + +###### 8.1.3.7.2.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(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.1.3.7.2.1.1-1: Test Parameters for multi-slot PUCCH format 1** + +| Parameter | Test | +|---------------------------------------------------|-------------------------------------------| +| Cyclic Prefix | Normal | +| 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.1.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.2.3.7.2.1.2-1. + +**Table 8.1.3.7.2.1.2-1: Minimum requirements for multi-slot PUCCH format 1 with 30kHz SCS** + +| Number of TX antennas | Number of RX antennas | Propagation conditions and correlation matrix (Annex I) | Channel bandwidth / SNR (dB) | +|-----------------------|-----------------------|---------------------------------------------------------|------------------------------| +| | | | 40 MHz | +| 1 | 2 | TDLC-300-100 Low | -6.3 | + +#### 8.1.3.7.2.2 ACK missed detection requirements + +##### 8.1.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.2.3.7.2.1.1-1 are configured. + +##### 8.1.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.2.3.7.2.2.2-1. + +**Table 8.1.3.7.2.2.2-1: Minimum requirements for multi-slot PUCCH format 1 with 30kHz SCS** + +| Number of TX antennas | Number of RX antennas | Propagation conditions and correlation matrix (Annex I) | Channel bandwidth / SNR (dB) | +|-----------------------|-----------------------|---------------------------------------------------------|------------------------------| +| | | | 40 MHz | +| 1 | 2 | TDLC-300-100 Low | -7.6 | + +### 8.1.4 Performance requirements for PRACH + +#### 8.1.4.1 PRACH false alarm probability + +##### 8.1.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.1.4.1.2 Minimum requirement + +The false alarm probability shall be less than or equal to 0.1%. + +### 8.1.4.2 PRACH detection requirements + +#### 8.1.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. 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.1.4.2.1-1. + +**Table 8.1.4.2.1-1: Time error tolerance** + +| PRACH preamble | PRACH SCS (kHz) | Time error tolerance | +|------------------------|-----------------|----------------------| +| 0 | 1.25 | 2.55 us | +| A1, A2, A3, B4, C0, C2 | 15 | 2.03 us | +| | 30 | 1.77 us | + +The test preambles for normal mode are listed in table A.2.5-1 and the test parameter *msg1-FrequencyStart* is set to 0. + +#### 8.1.4.2.2 Minimum requirements for normal mode + +The probability of detection shall be equal to or exceed 99% for the SNR levels listed in Tables 8.1.4.2.2-1 to 8.1.4.2.2-3. + +**Table 8.1.4.2.2-1: PRACH missed detection requirements for Normal Mode, 1.25 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Propagation conditions and correlation matrix (Annex I) | Frequency offset | SNR (dB) | +|-----------------------|-----------------------|---------------------------------------------------------|------------------|----------------| +| | | | | Burst format 0 | +| 1 | 2 | TDLC300-100 Low | 400 Hz | -6.6 | +| | 4 | TDLC300-100 Low | 400 Hz | -11.9 | +| | 8 | TDLC300-100 Low | 400 Hz | -15.8 | + +**Table 8.1.4.2.2-2: PRACH missed detection requirements for Normal Mode, 15 kHz SCS** + +| Number of TX antennas | Number of Demodulation Branches | Propagation conditions and correlation matrix (Annex I) | Frequency offset | SNR (dB) | | | | | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| | | | | Burst format A1 | Burst format A2 | Burst format A3 | Burst format B4 | Burst format C0 | Burst format C2 | +| 1 | 2 | TDLC300-100 Low | 400 Hz | -2.1 | -4.8 | -6.6 | -8.8 | 0.8 | -4.9 | +| | 4 | TDLC300-100 Low | 400 Hz | -7.3 | -10.3 | -11.7 | -13.8 | -4.3 | -10.2 | +| | 8 | TDLC300-100 Low | 400 Hz | -11.0 | -13.9 | -15.2 | -17.3 | -8.1 | -13.9 | + +**Table 8.1.4.2.2-3: PRACH missed detection requirements for Normal Mode, 30 kHz SCS** + +| Number of TX antennas | Number of Demodulation Branches | Propagation conditions and correlation matrix (Annex I) | Frequency offset | SNR (dB) | | | | | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| | | | | Burst format A1 | Burst format A2 | Burst format A3 | Burst format B4 | Burst format C0 | Burst format C2 | +| 1 | 2 | TDLC300-100 Low | 400 Hz | -2.8 | -5.7 | -7.4 | -9.9 | 0.1 | -5.6 | +| | 4 | TDLC300-100 Low | 400 Hz | -7.2 | -10.4 | -12.0 | -14.5 | -4.5 | -10.4 | +| | 8 | TDLC300-100 Low | 400 Hz | -10.7 | -13.7 | -15.1 | -17.6 | -7.8 | -13.7 | + +## 8.2 IAB-MT requirements + +### 8.2.1 General + +Conducted performance requirements specify the ability of the *IAB-MT type 1-H* to correctly demodulate signals in various conditions and configurations. Conducted performance requirements are specified at the *TAB connector(s)* (for *IAB-MT type 1-H*). + +Conducted performance requirements for the IAB-MT are specified for the fixed reference channels defined in annex A and the propagation conditions in annex I. The requirements only apply to those FRCs that are supported by the IAB-MT. + +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 Performance requirements for PDSCH + +##### 8.2.2.1.1 General + +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 retransmissions. + +**Table: 8.2.2.1.1-1 Test parameters for testing PDSCH** + +| Parameter | Value | +|------------------------------------|----------------------------------------------------------------| +| Cyclic prefix | Normal | +| Default TDD UL-DL pattern (Note 1) | 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 | +| | DM-RS position ( l0 ) | +| | 2 | +| | Additional DM-RS position | +| | 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 | + +| | | | +|------------------------------------------------------------------------------------|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 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 | +| | DM-RS sequence generation | $N_{ID}^0=0$ | +| Time domain resource assignment | PDSCH mapping type | A | +| | Start symbol | 2 | +| | Allocation length | 12 | +| Frequency domain resource assignment | RB assignment | Full applicable test bandwidth | +| PT-RS configuration | | Not configured | +| PRB bundling size | | 2 | +| VRB-to-PRB mapping type | | Not interleaved | +| PDSCH & PDSCH DMRS Precoding configuration | | Single Panel Type I, Random precoder selection updated per slot, with equal probability of each applicable $i_1, i_2$ combination, and with PRB bundling granularity | +| Note 1: The same requirements are applicable to TDD with different UL-DL patterns. | | | + +#### 8.2.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.2.1.2-1 to 8.2.2.1.2-4 at the given SNR with the test parameters stated in Table 8.2.2.1.1-1. + +**Table 8.2.2.1.2-1: Minimum requirements for PDSCH Type A with Rank 1** + +| Test number | FRC (Annex A) | Bandwidth (MHz) / Subcarrier spacing (kHz) | Propagation conditions (Annex I) | Antenna configuration | Fraction of maximum throughput (%) | SNR (dB) | +|-------------|---------------|--------------------------------------------|----------------------------------|-----------------------|------------------------------------|----------| +| 1-1 | M-FR1-A.3.3-1 | 40/30 | TDLA30-10 | 2x4, ULA Low | 70 | 21.6 | +| 1-2 | M-FR1-A.3.1-1 | 40/30 | TDLA30-10 | 2x4, ULA Low | 30 | -1.1 | + +**Table 8.2.2.1.2-2: Minimum requirements for PDSCH Type A with Rank 2** + +| Test number | FRC (Annex A) | Bandwidth (MHz) / Subcarrier spacing (kHz) | Propagation conditions (Annex I) | Antenna configuration | Fraction of maximum throughput (%) | SNR (dB) | +|-------------|---------------|--------------------------------------------|----------------------------------|-----------------------|------------------------------------|----------| +| 2-1 | M-FR1-A.3.2-1 | 40/30 | TDLA30-10 | 2x4, ULA Low | 70 | 13.6 | + +**Table 8.2.2.1.2-3: Minimum requirements for PDSCH Type A with Rank 3** + +| Test number | FRC (Annex A) | Bandwidth (MHz) / Subcarrier spacing (kHz) | Propagation conditions (Annex I) | Antenna configuration | Fraction of maximum throughput (%) | SNR (dB) | +|-------------|---------------|--------------------------------------------|----------------------------------|-----------------------|------------------------------------|----------| +| 3-1 | M-FR1-A.3.1-2 | 40/30 | TDLA30-10 | 4x4, ULA Low | 70 | 11.4 | + +**Table 8.2.2.1.2-4: Minimum requirements for PDSCH Type A with Rank 4** + +| Test number | FRC (Annex A) | Bandwidth (MHz) / Subcarrier spacing (kHz) | Propagation conditions (Annex I) | Antenna configuration | Fraction of maximum throughput (%) | SNR (dB) | +|-------------|---------------|--------------------------------------------|----------------------------------|-----------------------|------------------------------------|----------| +| 4-1 | M-FR1-A.3.1-3 | 40/30 | TDLA30-10 | 4x4, ULA Low | 70 | 15.4 | + +## 8.2.2.2 Performance requirements for PDCCH + +### 8.2.2.2.1 General + +The receiver characteristics of the PDCCH are determined by the probability of miss-detection of the Downlink Scheduling Grant (Pm-dsg). + +**Table: 8.2.2.2.1-1 Test parameters for testing PDCCH** + +| Parameter | Value | +|-------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Cyclic prefix | Normal | +| Default TDD UL-DL pattern (Note 1) | 7D1S2U, S=6D:4G:4U | +| DM-RS sequence generation | $N_{ID}=0$ | +| Frequency domain resource allocation for CORESET | Start from RB = 0 with contiguous RB allocation | +| CCE to REG mapping type | Interleaved | +| Interleaver size | 3 | +| REG bundle size | 2 for test with 1Tx
6 for test with 2Tx | +| Shift Index | 0 | +| Slots for PDCCH monitoring | Each slot | +| Number of PDCCH candidates for the tested aggregation level | 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 | + +Note 1: The same requirements are applicable to TDD with different UL-DL patterns. + +### 8.2.2.2.2 Minimum requirements + +The Pm-dsg shall be equal to or smaller than 1%, for the cases stated in Table 8.2.2.2.2-1 at the given SNR with the test parameters stated in Table 8.2.2.2.1-1. + +**Table 8.2.2.2.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 I) | Antenna configuration | Pm-dsg (%) | SNR (dB) | +|-------------|--------------------------------------------|------------|------------------|-------------------|---------------|----------------------------------|-----------------------|------------|----------| +| 1 | 40/30 | 102 | 1 | 2 | M-FR1-A.3.4-1 | TDLA30-10 | 1x4, ULA Low | 1 | 2.1 | +| 2 | 40/30 | 102 | 1 | 4 | M-FR1-A.3.4-2 | TDLA30-10 | 1x4, ULA Low | 1 | 0.7 | +| 3 | 40/30 | 90 | 1 | 8 | M-FR1-A.3.4-3 | TDLA30-10 | 2x4, ULA Low | 1 | -4.1 | + +## 8.2.3 CSI reporting requirements + +### 8.2.3.1 General + +This clause includes conducted requirements for the reporting of channel state information (CSI). + +#### 8.2.3.1.1 Common test parameters + +Parameters specified in Table 8.2.3.1-1 are applied for all test cases in clause 8.2.3 unless otherwise stated. + +**Table 8.2.3.1-1: Test parameters for CSI test cases** + +| Parameter | | Unit | Value | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|------|-------------------------------------------------------------------------------------------------------------------------------| +| PDSCH transmission scheme | | | Transmission scheme 1 | +| Duplex mode | | | TDD | +| Actual carrier configuration | Offset between Point A and the lowest usable subcarrier on this carrier (Note 2) | RBs | 0 | +| | Subcarrier spacing | kHz | 30 | +| DL BWP configuration #1 | Cyclic prefix | | Normal | +| | RB offset | RBs | 0 | +| | Number of contiguous PRB | PRBs | Maximum transmission bandwidth configuration as specified in clause 5.3.2 for tested channel bandwidth and subcarrier spacing | +| Active DL BWP index | | | 1 | +| Cross carrier scheduling | | | Not configured | +| PDSCH configuration | Mapping type | | Type A | +| | $k_0$ | | 0 | +| | Starting symbol (S) | | 2 | +| | Length (L) | | 12 | +| | PDSCH aggregation factor | | 1 | +| | PRB bundling type | | Static | +| | PRB bundling size | | 2 | +| | Resource allocation type | | type 0 | +| | VRB-to-PRB mapping type | | Non-interleaved | +| PDSCH DMRS configuration | VRB-to-PRB mapping interleaver bundle size | | N/A | +| | DMRS Type | | Type 1 | +| | Number of additional DMRS | | 1 | +| | Maximum number of OFDM symbols for DL front loaded DMRS | | 1 | +| | DMRS ports indexes | | {1000} for Rank1
{1000, 1001} for Rank2
{1000, 1001, 1002} for Rank3
{1000, 1001, 1002, 1003} for Rank4 | +| PTRS configuration | Number of PDSCH DMRS CDM group(s) without data | | 2 | +| | Frequency density ( $K_{PT-RS}$ ) | | N/A | +| NZP CSI-RS for CSI acquisition | Time density ( $L_{PT-RS}$ ) | | N/A | +| | Frequency Occupation | | Start PRB 0
Number of PRB = BWP size | +| Redundancy version coding sequence | | | {0,2,3,1} | +| Physical signals, channels mapping and precoding | | | As specified in Annex I.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 [3] for tested channel bandwidth and subcarrier spacing. | | | | + +### 8.2.3.2 Reporting of Channel Quality Indicator (CQI) + +#### 8.2.3.2.1 General + +The reporting accuracy of the channel quality indicator (CQI) under frequency non-selective conditions is determined by the reporting variance and the BLER performance using the transport format indicated by the reported CQI median. The purpose is to verify that the reported CQI values are in accordance with the CQI definition given in TS 38.214 [11]. 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. + +**Table 8.2.3.2.1-1: Test parameters for testing CQI reporting** + +| Parameter | Unit | Test 1 | Test 2 | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------|--------|-------------------------| +| Bandwidth | MHz | | 40 | +| Subcarrier spacing | kHz | | 30 | +| Default TDD UL-DL pattern (Note 1) | | | 7D1S2U,
S=6D:4G:4U | +| SNR | dB | 5 | 6 11 12 | +| Propagation channel | | | AWGN | +| Antenna configuration | | | 2x4 | +| Beamforming Model | | | As specified in Annex I | +| 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 | | | 11111111 | +| 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 | +| Maximum number of HARQ transmission | | | 1 | +| Measurement channel | | | M-FR1-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 [28] are left up to test implementation, if transmitted or needed. | | | | + +#### 8.2.3.2.2 Minimum requirements + +For the parameters specified in Table 8.2.3.2.1-1, and using the downlink physical channels specified in Annex A, 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.3 Reporting of Precoding Matrix Indicator (PMI) + +#### 8.2.3.3.1 General + +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_{follow1, follow2}$ is 90 % of the maximum throughput obtained at $SNR_{follow1, follow2}$ using the precoders configured according to the IAB-MT reports, and $t_{rnd1, rnd2}$ is the throughput measured at $SNR_{follow1, follow2}$ with random precoding. + +**Table 8.2.3.3.1-1: Test parameters for testing PMI reporting** + +| Parameter | Unit | Test 1 | Test 2 | +|-------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|----------------------------------| +| Bandwidth | MHz | 40 | | +| Subcarrier spacing | kHz | 30 | | +| TDD DL-UL configuration (Note 1) | | 7D1S2U, S=6D:4G:4U | | +| Propagation channel | | TDLA30-5 | | +| Antenna configuration | | High XP 4 x 4
(N1,N2) = (2,1) | High XP 8 x 4
(N1,N2) = (4,1) | +| Beamforming Model | | As specified in Annex I.3.1 | | +| NZP CSI-RS for CSI acquisition | CSI-RS resource Type | Periodic | | +| | Number of CSI-RS ports (X) | 4 | 8 | +| | CDM Type | FD-CDM2 | CDM4 (FD2, TD2) | +| | Density (ρ) | 1 | | +| | First subcarrier index in the PRB used for CSI-RS ( $k_0, k_1$ ) | Row 4, (0,-) | Row 8, (4,6) | +| | First OFDM symbol in the PRB used for CSI-RS ( $l_0, l_1$ ) | (13,-) | (5,-) | +| | NZP CSI-RS-timeConfig periodicity and offset | slot | 10/1 | +| ReportConfigType | | Periodic | | +| CQI-table | | Table 1 | | +| reportQuantity | | cri-RI-PMI-CQI | | +| cqi-FormatIndicator | | Wideband | | +| pmi-FormatIndicator | | Wideband | | +| Sub-band Size | RB | 16 | | +| csi-ReportingBand | | 1111111 | | +| CSI-Report interval and offset | slot | Not configured | | +| CSI-Report periodicity and offset | | 10/9 | | +| Codebook configuration | Codebook Type | typeI-SinglePanel | | +| | Codebook Mode | 1 | | +| | (CodebookConfig-N1, CodebookConfig-N2) | (2,1) | (4,1) | +| | (CodebookConfig-O1, CodebookConfig-O2) | (4,1) | | +| | CodebookSubsetRestriction | 11111111 | 0x FFFF | +| | RI Restriction | 00000001 | 00000010 | +| CQI/RI/PMI delay | ms | 5.5 | 6.5 | +| Maximum number of HARQ transmission | | 4 | | +| Measurement channel | | M-FR1-A.3.5-5 | M-FR1-A.3.5-6 | +| 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 granularity) with equal probability of each applicable $i_1, i_2$ 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) for test 1 and not later than slot#(n-6) for test 2, this reported PMI cannot be applied at the gNB downlink before slot#(n+4) for test 1 and before slot#(n+6) for test 2. | | | +| Note 4: | Randomization of the principle beam direction shall be used as specified in I.2.4.3.5. | | | +| Note 5: | SSB, TRS, CSI-RS, and/or other unspecified test parameters with respect to TS 38.101-4 [28] are left up to test implementation, if transmitted or needed. | | | + +### 8.2.3.3.2 Minimum requirements + +For the parameters specified in Table 8.2.3.2.1-1 and using the downlink physical channels specified in Annex A, the minimum requirements are specified in Table 8.2.3.2.2-1: + +**Table 8.2.3.2.2-1: Minimum requirement for PMI reporting** + +| Parameter | Test 1 | Test 2 | +|-----------|--------|--------| +| $\gamma'$ | 1.3 | 1.5 | + +### 8.2.3.4 Reporting of Rank Indicator (RI) + +#### 8.2.3.4.1 General + +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. + +**Table 8.2.3.4.1-1: Test parameters for testing RI reporting** + +| Parameter | Unit | Test 1 | Test 2 | Test 3 | Test 4 | | | | +|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------|----------------------------------------------------|----------------------------------------------------|------------------------------------------------------|--|--|--| +| Bandwidth | MHz | 40 | | | | | | | +| Subcarrier spacing | kHz | 30 | | | | | | | +| Default TDD UL-DL pattern (Note 1) | | 7D1S2U, S=6D:4G:4U | | | | | | | +| SNR | dB | -2 | 16 | 16 | 22 | | | | +| Propagation channel | | TDLA30-5 | | | | | | | +| Antenna configuration | | ULA Low 2x4 | ULA Low 2x4 | ULA High 2x4 | ULA Low 4x4 | | | | +| Beamforming Model | | As defined in Annex I.3.1 | | | | | | | +| NZP CSI-RS for CSI acquisition | CSI-RS resource Type | | Periodic | | | | | | +| | Number of CSI-RS ports (X) | 2 | 2 | 2 | 4 | | | | +| | CDM Type | | FD-CDM2 | | | | | | +| | Density (p) | | 1 | | | | | | +| | First subcarrier index in the PRB used for CSI-RS ( $k_0, k_1$ ) | Row 3 (6,-) | Row 3 (6,-) | Row 3 (6,-) | Row 4 (0,-) | | | | +| | First OFDM symbol in the PRB used for CSI-RS ( $l_0, l_1$ ) | | (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 | | 11111111 | | | | | | | +| CSI-Report periodicity and offset | slot | 10/9 | | | | | | | +| Codebook configuration | Codebook Type | | typeI-SinglePanel | | | | | | +| | Codebook Mode | | 1 | | | | | | +| | (CodebookConfig-N1, CodebookConfig-N2) | N/A | N/A | N/A | (2,1) | | | | +| | CodebookSubsetRestriction | 010000 for fixed rank 2, 010011 for following rank | 000011 for fixed rank 1, 010011 for following rank | 000011 for fixed rank 1, 010011 for following rank | 11111111 | | | | +| | RI Restriction | N/A | N/A | N/A | 00000010 for fixed Rank 2 and 00001111 for follow RI | | | | +| CQI/RI/PMI delay | ms | 9.5 | | | | | | | +| Maximum number of HARQ transmission | | 1 | | | | | | | +| RI Configuration | | Fixed RI = 2 and follow RI | Fixed RI = 1 and follow RI | Fixed RI = 1 and follow RI | Fixed RI = 2 and follow RI | | | | +| 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 [28] are left up to test implementation, if transmitted or needed. | | | | | | | | +| Note 3: | Measurements channels are specified in Table A.3.5-1. M-FR1-A.3.5-1 is used for Rank 1 case. M-FR1-A.3.5-2 is used for Rank 2 case. M-FR1-A.3.5-3 is used for Rank 3 case. M-FR1-A.3.5-4 is used for Rank 4 case. | | | | | | | | + +#### 8.2.3.4.2 Minimum requirements + +The minimum performance requirement in Table 8.2.3.4.2-1 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.3.1-1 and using the downlink physical channels specified in Annex A, the minimum requirements are specified in Table 8.2.3.4.2-1. + +**Table 8.2.3.4.2-1: Minimum requirement for RI reporting** + +| | Test 1 | Test 2 | Test 3 | Test 4 | +|-------|--------|--------|--------|--------| +| $J_1$ | N/A | 1.05 | 0.9 | N/A | +| $J_2$ | 0.9 | N/A | N/A | 0.9 | + +## 9 Radiated transmitter characteristics + +### 9.1 General + +Radiated transmitter characteristics requirements apply on the *IAB-DU* and *IAB-MT type 1-H*, *IAB-DU* and *IAB-MT type 1-O*, or *IAB-DU* and *IAB-MT type 2-O* including all its functional components active and for all foreseen modes of operation unless otherwise stated. + +For *IAB-MT type 1-O* manufacturer shall also declare $N_{TXU,active}$ . $N_{TXU,active}$ active transmitter units supporting the same *operating band* is implementation dependent. + +The number of *active transmitter units* that are considered when calculating the radiated TX emissions limits ( $N_{TXU,counted}$ ) for *IAB-MT type 1-O* is calculated as follows: + +$$N_{TXU,counted} = \min(N_{TXU,active}, 8)$$ + +$N_{TXU,countedpercell}$ is used for scaling of *basic limits* and is derived as $N_{TXU,countedpercell} = N_{TXU,counted}$ + +NOTE: $N_{TXU,active}$ depends on the actual number of *active transmitter units*. + +### 9.2 Radiated transmit power + +#### 9.2.1 General + +*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 base station is declared to radiate at the associated *beam peak direction* during the *transmitter ON period*. + +For each *beam peak direction* associated with a *beam direction pair* within the *OTA peak directions set*, a specific *rated beam EIRP* level may be claimed. Any claimed value shall be met within the accuracy requirement as described below. *Rated beam EIRP* is only required to be declared for the *beam direction pairs* subject to conformance testing. + +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}}$ . + +## 9.2.2 Minimum requirement for IAB-DU type 1-H, IAB-DU type 1-O, IAB-MT type 1-H and IAB-MT 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. + +For IAB type 1-O only, for each declared beam, in extreme conditions, for any specific *beam peak direction* associated with a *beam direction pair* within the *OTA peak directions set*, a manufacturer claimed EIRP level in the corresponding *beam peak direction* shall be achievable to within $\pm 2.7$ dB of the claimed value. + +Normal and extreme conditions are defined in TS 38.141-2 [21], annex B. + +In certain regions, the minimum requirement for normal conditions may apply also for some conditions outside the range of conditions defined as normal. + +## 9.2.3 Minimum requirement for IAB-DU type 2-O and IAB-MT type 2-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 3.4$ dB of the claimed value. + +For each declared beam, in extreme conditions, for any specific *beam peak direction* associated with a *beam direction pair* within the *OTA peak directions set*, a manufacturer claimed EIRP level in the corresponding *beam peak direction* shall be achievable to within $\pm 4.5$ dB of the claimed value. + +Normal and extreme conditions are defined in TS 38.141-2 [21], annex B. + +In certain regions, the minimum requirement for normal conditions may apply also for some conditions outside the range of conditions defined as normal. + +## 9.2.4 Configured radiated output power + +### 9.2.4.1 IAB-MT configured output power for IAB-MT type 1-H, 1-O and 2-O + +The configured maximum output power $P_{\text{CMAX,fc}}$ is set in each slot according to the following equation: + +$$P_{\text{CMAX,fc}} = P_{\text{Rated,c,EIRP}}$$ + +where $P_{\text{Rated,c,EIRP}}$ is declared by manufacturer. + +## 9.3 OTA IAB output power + +### 9.3.1 General + +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 9.3.1-1 for IAB-DU type 1-O and in table 9.3.1-2 for IAB-MT type 1-O. + +**Table 9.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 9.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 9.3.2 – 9.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. + +## 9.3.1B Output power for mIAB-MT + +Only Local Area IAB-MT type 1-O and type 2-O requirements are applied for mIAB-MT type 1-O and type 2-O. + +## 9.3.2 Minimum requirement for IAB-DU type 1-O and IAB-MT type 1-O + +In normal conditions, the IAB type 1-O *maximum carrier TRP output power*, $P_{\text{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.141-1 [22], annex B. + +## 9.3.3 Minimum requirement for IAB type 2-O + +In normal conditions, the IAB type 2-O *maximum carrier TRP output power*, $P_{\text{max,c,TRP}}$ measured at the RIB shall remain within $\pm 3$ 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.141-2 [21], annex B. + +## 9.4 OTA output power dynamics + +### 9.4.1 IAB-DU OTA Output Power Dynamics + +#### 9.4.1.1 General + +The requirements in clause 9.4 apply during the *transmitter ON period*. 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.1.2 OTA RE power control dynamic range + +#### 9.4.1.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 BS 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.1.2.2 Minimum requirement for IAB-DU type 1-O + +The OTA RE power control dynamic range is specified the same as the conducted RE power control dynamic range requirement for BS *type 1-H* in TS 38.104x[2], subclause 6.3.2.2. + +### 9.4.1.3 OTA total power dynamic range + +#### 9.4.1.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 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 symbol carries PDSCH and not contain RS or SSB. + +#### 9.4.1.3.2 Minimum requirement for IAB-DU type 1-O + +The OTA total power dynamic range is specified the same as the total power dynamic range requirement for BS *type 1-H* in TS 38.104x[2], subclause 6.3.3.2, where references to *BS channel bandwidth* apply to *IAB-DU channel bandwidth*. + +#### 9.4.1.3.3 Minimum requirement for IAB-DU type 2-O + +The OTA total power dynamic range is specified the same as the OTA total power dynamic range requirement for BS *type 2-O* in TS 38.104x[2], subclause 9.4.3.3. + +## 9.4.2 IAB-MT OTA Output Power Dynamics + +### 9.4.2.1 OTA total power dynamic range + +#### 9.4.2.1.1 General + +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*. + +#### 9.4.2.1.2 Minimum requirement for IAB-MT type 1-O + +For a wide area IAB-MT the total power dynamic range for each NR carrier shall be larger than or equal to 5 dB. + +For a local area IAB-MT the total power dynamic range for each NR carrier shall be larger than or equal to 10 dB. + +#### 9.4.2.1.2B Minimum requirement for mIAB-MT type 1-O + +For a mIAB-MT the total power dynamic range for each NR carrier shall be larger than or equal to 45 dB. + +#### 9.4.2.1.3 Minimum requirement for IAB-MT type 2-O + +For a wide area IAB-MT the total power dynamic range for each NR carrier shall be larger than or equal to 5 dB. + +For a local area IAB-MT the total power dynamic range for each NR carrier shall be larger than or equal to 10 dB. + +#### 9.4.2.1.3B Minimum requirement for mIAB-MT type 2-O + +For a mIAB-MT the total power dynamic range for each NR carrier shall be larger than or equal to 30 dB. + +### 9.4.3 Power control + +#### 9.4.3.1 Power control for local area IAB-MT type 1-O + +##### 9.4.3.1.1 Relative EIRP tolerance for local area IAB-MT type 1-O + +The relative EIRP tolerance is the ability of the transmitter to set its radiated 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 20 ms. + +The minimum requirements specified in Table 9.4.3.1.1-1 apply only when the output power is within the limits set by declared maximum output power and specified dynamic range. + +2 exceptions are allowed for each of two test patterns. The test patterns are a monotonically increasing power sweep and a monotonically decreasing power sweep. For those exceptions, the power tolerance limit is a maximum of $\pm 11.0$ dB in Table 9.4.3.1.1-1. + +**Table 9.4.3.1.1-1: Relative EIRP tolerance for local area IAB-MT type 1-O** + +| Power step $\Delta P$ (Up or down) (dB) | EIRP tolerance (dB) | +|-----------------------------------------|---------------------| +| $\Delta P < 2$ | $\pm 2.5$ | +| $2 \leq \Delta P < 3$ | $\pm 3.5$ | +| $3 \leq \Delta P < 4$ | $\pm 4.5$ | +| $4 \leq \Delta P < 10$ | $\pm 5.5$ | + +##### 9.4.3.1.1B Relative EIRP tolerance for mIAB-MT type 1-O + +The relative EIRP tolerance is the ability of the transmitter to set its radiated 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 20 ms. + +The minimum requirements specified in Table 9.4.3.1.1B-1 apply only when the output power is within the limits set by declared maximum output power and specified dynamic range. + +2 exceptions are allowed for each of two test patterns. The test patterns are a monotonically increasing power sweep and a monotonically decreasing power sweep. For those exceptions, the power tolerance limit is a maximum of $\pm 11.0$ dB in Table 9.4.3.1.1B-1. + +**Table 9.4.3.1.1B-1: Relative EIRP tolerance for mIAB-MT type 1-O** + +| Power step $\Delta P$ (Up or down) (dB) | EIRP tolerance (dB) | +|-----------------------------------------|---------------------| +| $\Delta P < 2$ | $\pm 2.5$ | +| $2 \leq \Delta P < 3$ | $\pm 3.5$ | +| $3 \leq \Delta P < 4$ | $\pm 4.5$ | +| $4 \leq \Delta P < 10$ | $\pm 5.5$ | +| $10 \leq \Delta P < 15$ | $\pm 6$ | +| $15 \leq \Delta P$ | $\pm 6.5$ | + +#### 9.4.3.1.2 Aggregate EIRP tolerance for local area IAB-MT type 1-O + +The aggregate EIRP control tolerance is the ability of the transmitter to maintain its EIRP in a sub-frame (1 ms) during non-contiguous transmissions within [21ms] in response to 0 dB TPC commands with respect to the first UE transmission and all other power control parameters as specified in 3GPP TS 38.213 [10] kept constant. + +The minimum requirements specified in Table 9.4.3.1.2-1 apply only when the output power is within the limits set by declared maximum output power and specified dynamic range. + +**Table 9.4.3.1.2-1: Aggregate power tolerance for local area IAB-MT type 1-O** + +| TPC command | UL channel | Aggregate EIRP tolerance within [21 ms] | +|-------------|------------|-----------------------------------------| +| 0 dB | PUCCH | [ $\pm 2.5$ dB] | +| 0 dB | PUSCH | [ $\pm 3.5$ dB] | + +#### 9.4.3.2 Power control for local area IAB-MT type 2-O + +##### 9.4.3.2.1 Relative EIRP tolerance for local area IAB-MT type 2-O + +The relative EIRP tolerance is the ability of the transmitter to set its radiated 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 20 ms. + +The minimum requirements specified in Table 9.4.3.1.1-1 apply only when the output power is within the limits set by declared maximum output power and specified dynamic range. + +2 exceptions are allowed for each of two test patterns. The test patterns are a monotonically increasing power sweep and a monotonically decreasing power sweep. For those exceptions, the power tolerance limit is a maximum of [ $\pm 11.0$ dB] in Table 9.4.3.1.1-1. + +**Table 9.4.3.2.1-1: Relative EIRP tolerance for local area IAB-MT type 2-O** + +| Power step $\Delta P$ (Up or down) (dB) | EIRP tolerance (dB) | +|-----------------------------------------|---------------------| +| $\Delta P < 2$ | [ $\pm 3.0$ ] | +| $2 \leq \Delta P < 3$ | [ $\pm 4.0$ ] | +| $3 \leq \Delta P < 4$ | [ $\pm 5.0$ ] | +| $4 \leq \Delta P < 10$ | [ $\pm 6.0$ ] | + +##### 9.4.3.2.1B Relative EIRP tolerance for mIAB-MT type 2-O + +The relative EIRP tolerance is the ability of the transmitter to set its radiated 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 20 ms. + +The minimum requirements specified in Table 9.4.3.1.1B-1 apply only when the output power is within the limits set by declared maximum output power and specified dynamic range. + +2 exceptions are allowed for each of two test patterns. The test patterns are a monotonically increasing power sweep and a monotonically decreasing power sweep. For those exceptions, the power tolerance limit is a maximum of [ $\pm 11.0$ dB] in Table 9.4.3.1.1B-1. + +**Table 9.4.3.2.1B-1: Relative EIRP tolerance for mIAB-MT type 2-O** + +| Power step $\Delta P$ (Up or down) (dB) | EIRP tolerance (dB) | +|-----------------------------------------|---------------------| +| $\Delta P < 2$ | $[\pm 3.0]$ | +| $2 \leq \Delta P < 3$ | $[\pm 4.0]$ | +| $3 \leq \Delta P < 4$ | $[\pm 5.0]$ | +| $4 \leq \Delta P < 10$ | $[\pm 6.0]$ | +| $10 \leq \Delta P < 15$ | $[\pm 6]$ | +| $15 \leq \Delta P$ | $[\pm 6.5]$ | + +#### 9.4.3.2.2 Aggregate EIRP tolerance for local area IAB-MT type 2-O + +The aggregate EIRP control tolerance is the ability of the transmitter to maintain its EIRP in a sub-frame (1 ms) during non-contiguous transmissions within [21ms] in response to 0 dB TPC commands with respect to the first UE transmission and all other power control parameters as specified in 3GPP TS 38.213 [10] kept constant. + +The minimum requirements specified in Table 9.4.3.1.2-1 apply only when the output power is within the limits set by declared maximum output power and specified dynamic range. + +**Table 9.4.3.2.2-1: Aggregate power tolerance for local area IAB-MT type 2-O** + +| TPC command | UL channel | Aggregate EIRP tolerance within [21 ms] | +|-------------|------------|-----------------------------------------| +| 0 dB | PUCCH | $[\pm 3.5 \text{ dB}]$ | +| 0 dB | PUSCH | $[\pm 3.5 \text{ dB}]$ | + +### 9.5 OTA transmit ON/OFF power + +#### 9.5.1 General + +OTA transmit ON/OFF power requirements apply to TDD operation of IAB-DU and TDD operation of IAB-MT. + +#### 9.5.2 OTA transmitter OFF power + +##### 9.5.2.1 General + +OTA transmitter OFF power is defined as the mean power measured over $70/N \mu\text{s}$ filtered with a square filter of bandwidth equal to the *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 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 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*. + +##### 9.5.2.2 Minimum requirement for IAB-DU type 1-O + +The BS requirements specified in 9.5.2.2 in TS 38.104 [2] apply to *IAB-DU type 1-O*. + +##### 9.5.2.3 Minimum requirement for IAB-DU type 2-O + +The BS requirements specified in 9.5.2.3 in TS 38.104 [2] apply to *IAB-DU type 2-O*. + +#### 9.5.2.4 Minimum requirement for IAB-MT type 1-O + +The BS requirements specified in 9.5.2.2 in TS 38.104 [2] apply to *IAB-MT type 1-O*. + +#### 9.5.2.5 Minimum requirement for IAB-MT type 2-O + +The BS requirements specified in 9.5.2.3 in TS 38.104 [2] apply to *IAB-DU type 2-O*. + +### 9.5.3 OTA transient period + +#### 9.5.3.1 General + +The OTA *transmitter transient period* is the time period during which the transmitter is changing from the *transmitter OFF period* to the *transmitter ON period* or vice versa. The *transmitter transient period* is illustrated in figure 6.4.2.1-1 for IAB-DU and IAB-MT. + +This requirement shall be applied at each RIB supporting transmission in the *operating band*. + +#### 9.5.3.2 Minimum requirement for IAB-DU type 1-O + +The BS requirements specified in 9.5.3.2 in TS 38.104 [2] apply to *IAB-DU type 1-O*. + +#### 9.5.3.3 Minimum requirement for IAB-DU type 2-O + +The BS requirements specified in 9.5.3.3 in TS 38.104 [2] apply to *IAB-DU type 2-O*. + +#### 9.5.3.4 Minimum requirement for IAB-MT type 1-O + +The BS requirements specified in 9.5.3.2 in TS 38.104 [2] apply to *IAB-MT type 1-O*. + +#### 9.5.3.5 Minimum requirement for IAB-MT type 2-O + +The BS requirements specified in 9.5.3.3 in TS 38.104 [2] apply to *IAB-MT type 2-O*. + +### 9.6 OTA transmitted signal quality + +#### 9.6.1 OTA frequency error + +##### 9.6.1.1 IAB-DU OTA frequency error + +The requirements in clause 9.6.1 for BS type 1-O and type 2-O in TS 38.104 [2] apply to IAB-DU type 1-O and type 2-O respectively. + +##### 9.6.1.2 IAB-MT OTA frequency error + +###### 9.6.1.2.1 General + +The requirements in subclause 9.6.1.2 apply to the *transmitter ON period*. 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.2 Minimum requirement for IAB-MT type 1-O + +The IAB-MT basic measurement interval of modulated carrier frequency is 1 UL slot. The mean value of basic measurements of IAB-MT modulated carrier frequency shall be accurate to within $\pm 0.1$ PPM observed over a period of 1 msec of cumulated measurement intervals compared to the carrier frequency received from the parent node. + +###### 9.6.1.2.3 Minimum requirement for IAB-MT type 2-O + +The IAB-MT basic measurement interval of modulated carrier frequency is 1 UL slot. The mean value of basic measurements of IAB-MT modulated carrier frequency shall be accurate to within $\pm 0.1$ PPM observed over a period of 1 msec of cumulated measurement intervals compared to the carrier frequency received from the parent node. + +## 9.6.2 OTA modulation quality + +### 9.6.2.1 IAB-DU OTA modulation quality + +The requirements in clause 9.6.2 for BS type 1-O and type 2-O in TS 38.104 [2] apply to IAB-DU type 1-O and type 2-O respectively. + +NOTE: When the indicated IAB-MT transmission timing mode is set to 'Case6' as specified in 3GPP TS 38.213 [10], the power imbalance for simultaneous transmission between IAB-DU and IAB-MT under which the system can be operated is declared by manufacturer. + +### 9.6.2.2 IAB-MT OTA modulation quality + +#### 9.6.2.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 D for FR1 and Annex E for FR2-1. + +OTA modulation quality requirement is defined as a *directional requirement* at the RIB and shall be met within the *OTA coverage range*. + +NOTE: When the indicated IAB-MT transmission timing mode is set to 'Case6' as specified in 3GPP TS 38.213 [10], the power imbalance for simultaneous transmission between IAB-DU and IAB-MT under which the system can be operated is declared by manufacturer. + +#### 9.6.2.2.2 Minimum requirement for IAB-MT type 1-O + +For IAB-MT type 1-O, the EVM levels of each NR carrier for different modulation schemes outlined in table 6.5.2.2.2-1 shall be met. Requirements shall be the same as clause 6.5.2.2.2. + +#### 9.6.2.2.3 Minimum requirement for IAB-MT type 2-O + +For IAB-MT type 2-O, the EVM levels of each NR carrier for different modulation schemes outlined in table 9.6.2.2.3-1 shall be met , following the EVM frame structure described in clause 9.6.2.2.4. + +**Table 9.6.2.2.3-1: Minimum requirements for error vector magnitude** + +| Parameter | Unit | Average EVM level | +|-----------|------|-------------------| +| QPSK | % | 17.5 | +| 16 QAM | % | 12.5 | +| 64 QAM | % | 8.0 | + +#### 9.6.2.2.4 EVM frame structure for measurement + +EVM shall be evaluated for each NR carrier over all allocated resource blocks and uplink subframes. Different modulation schemes listed in table 9.6.2.2.3-1 shall be considered for rank 1. + +For NR, for all bandwidths, the EVM measurement shall be performed for each NR carrier over all allocated resource blocks and uplink subframes within 10 ms measurement periods. The boundaries of the EVM measurement periods need not be aligned with radio frame boundaries. + +## 9.6.3 OTA time alignment error + +### 9.6.3.1 IAB-DU OTA time alignment error + +The requirements in clause 9.6.3 for BS type 1-O and type 2-O in TS 38.104 [2] apply to IAB-DU type 1-O and type 2-O respectively. + +## 9.6.4 Timing error between IAB-DU and IAB-MT of the same IAB-Node + +When the indicated IAB-MT transmission timing mode is set to 'Case6' as specified in 3GPP TS 38.213 [10] and IAB-DU and IAB-MT of the same IAB-Node are transmitting simultaneously, the timing error between transmission timing of IAB-DU and IAB-MT shall not exceed 3 $\mu$ s. + +## 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 [16]. In ITU terminology, out of band emissions are unwanted emissions immediately outside the *channel bandwidth* resulting from the modulation process and non-linearity in the transmitter but excluding spurious emissions. Spurious emissions are emissions which are caused by unwanted transmitter effects such as harmonics emission, parasitic emission, intermodulation products and frequency conversion products, but exclude out of band emissions. + +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 9.7.1-1 *IAB-DU type 1-O* and *type 2-O* and in table 9.7.1-2 *IAB-MT type 1-O* and *type 2-O* for NR *operating bands*. + +**Table 9.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$ MHz | 10 | +| | $100$ MHz $\leq F_{\text{DL,high}} - F_{\text{DL,low}} \leq 900$ MHz | 40 | +| IAB-DU type 2-O | $F_{\text{DL,high}} - F_{\text{DL,low}} \leq 4000$ MHz | 1500 | + +**Table 9.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$ MHz | 10 | +| | $100$ MHz $\leq F_{\text{UL,high}} - F_{\text{UL,low}} \leq 900$ MHz | 40 | +| IAB-MT type 2-O | $F_{\text{UL,high}} - F_{\text{UL,low}} \leq 4000$ 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. + +## 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 [3]. + +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. + +### 9.7.2.2 Minimum requirement for *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*. + +### 9.7.2.3 Minimum requirement for *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*. + +## 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 during the *transmitter ON period*. + +NOTE: When the indicated IAB-MT transmission timing mode is set to 'Case6' as specified in 3GPP TS 38.213 [10], the power imbalance for simultaneous transmission between IAB-DU and IAB-MT under which the system can be operated is declared by manufacturer. + +### 9.7.3.2 Minimum requirement for *IAB-DU type 1-O* and *IAB-MT type 1-O* + +The ACLR (CACLR) absolute *basic limits* in table 6.6.3.2-2 + X, 6.6.3.2-5 + X (where and X = 9 dB for IAB-DU and X = $10\log_{10}(N_{TXU,countedpercell})$ for IAB-MT) or the ACLR (CACLR) *basic limit* in table 6.6.3.2-1, 6.6.3.2-3 or 6.6.3.2-4, whichever is less stringent, shall apply. + +For a *RIB* operating in multi-carrier or contiguous CA, the ACLR requirements in clause 6.6.3.2 shall apply to *IAB-DU* and *IAB-MT channel bandwidths* of the outermost carrier for the frequency ranges defined in table 6.6.3.2-1. For a RIB operating in *non-contiguous spectrum*, the ACLR requirement in clause 6.6.3.2 shall apply in *sub-block gaps* for the frequency ranges defined in table 6.6.3.2-3, while the CACLR requirement in clause 6.6.3.2 shall apply in *sub-block gaps* for the frequency ranges defined in table 6.6.3.2-4. + +For a *multi-band RIB*, the ACLR requirement in clause 6.6.3.2 shall apply in *Inter RF Bandwidth gaps* for the frequency ranges defined in table 6.6.3.2-3, while the CACLR requirement in clause 6.6.3.2 shall apply in *Inter RF Bandwidth gaps* for the frequency ranges defined in table 6.6.3.2-4. + +### 9.7.3.3 Minimum requirement for *IAB-DU type 2-O* and *Wide Area IAB-MT type 2-O* + +The OTA ACLR limit is specified in table 9.7.3.3-1. + +The OTA ACLR absolute limit is specified in table 9.7.3.3-2. + +The OTA ACLR (CACLR) absolute limit in table 9.7.3.3-2 or 9.7.3.3-5 or the ACLR (CACLR) limit in table 9.7.3.3-1, 9.7.3.3-3 or 9.7.3.3-4, whichever is less stringent, shall apply. + +For a *RIB* operating in multi-carrier or contiguous CA, the OTA ACLR requirements in table 9.7.3.3-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 9.7.3.3-3 shall apply in *sub-block gaps* for the frequency ranges defined in the table, while the OTA CACLR requirement in table 9.7.3.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 9.7.3.3-4 and the filters on the assigned channels are defined in table 9.7.3.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 9.7.3.3-4. + +**Table 9.7.3.3-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 BWChannel (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 Channel | NR of same BW (Note 2) | Square (BW Config ) | 28 (Note 3)
26 (Note 4) | + +NOTE 1: BWChannel and BWConfig 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 (BWConfig). +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 9.7.3.3-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 and Wide area IAB-MT | -13 dBm/MHz | +| Medium range IAB-DU | -20 dBm/MHz | +| Local area IAB-DU | -20 dBm/MHz | + +**Table 9.7.3.3-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 (Wgap) 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 | +|----------------------------------------------------------------------------------------|---------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------|-----------------------------------------|------------------------------------------------------------------------------------|----------------------------| +| 50, 100 | W gap ≥ 100 (Note 5)
W gap ≥ 250 (Note 6) | 25 MHz | 50 MHz NR (Note 2) | Square (BW Config ) | 28 (Note 3)
26 (Note 4) | +| 200, 400 | W gap ≥ 400 (Note 6)
W gap ≥ 250 (Note 5) | 100 MHz | 200 MHz NR (Note 2) | Square (BW Config ) | 28 (Note 3)
26 (Note 4) | + +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 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 9.7.3.3-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 | +|----------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------|-----------------------------------------|------------------------------------------------------------------------------------|----------------------------| +| 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}}$ ) | 28 (Note 3)
26 (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}}$ ) | 28 (Note 3)
26 (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 9.7.3.3-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 and Wide area IAB-MT | -13 dBm/MHz | +| Medium range IAB-DU | -20 dBm/MHz | +| Local area IAB-DU | -20 dBm/MHz | + +**Table 9.7.3.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 | + +### 9.7.3.4 Minimum requirement for Local Area IAB-MT type 2-O + +The OTA ACLR limit is specified in table 9.7.3.4-1. + +The OTA ACLR absolute limit is specified in table 9.7.3.4-2. + +The OTA ACLR (CACLR) absolute limit in table 9.7.3.4-2 or 9.7.3.4-5 or the ACLR (CACLR) limit in table 9.7.3.4-1, 9.7.3.4-3 or 9.7.3.4-4, whichever is less stringent, shall apply. + +Requirements specified for Local Area IAB-DU type 2-O in clause 9.7.3.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 9.7.3.4-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 9.7.3.4-3 shall apply in sub-block gaps for the frequency ranges defined in the table, while the OTA CACLR requirement in table 9.7.3.4-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 + +- b) 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 9.7.3.4-4 and the filters on the assigned channels are defined in table 9.7.3.4-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 9.7.3.4-4. + +**Table 9.7.3.4-1: Local Area IAB-MT type 2-O ACLR limit** + +| IAB-MT channel bandwidth of lowest/highest carrier transmitted BWChannel (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 Channel | NR of same BW (Note 2) | Square (BW Config ) | 24 (Note 3) | + +NOTE 1: BWChannel and BWConfig 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* (BWConfig). +NOTE 3: Applicable to bands defined within the frequency spectrum range of 24.25 – 33.4 GHz and 37 – 52.6 GHz + +**Table 9.7.3.3-2: Local Area IAB-MT type 2-O ACLR absolute limit** + +| IAB-MT class | ACLR absolute limit | +|---------------------|----------------------------| +| Local area IAB-MT | -20 dBm/MHz | + +**Table 9.7.3.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 (Wgap) 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 gap ≥ 100 (Note 4)
W gap ≥ 250 (Note 5) | 25 MHz | 50 MHz NR (Note 2) | Square (BW Config ) | 24 (Note 3) | +| 200, 400 | W gap ≥ 400 (Note 5)
W gap ≥ 250 (Note 4) | 100 MHz | 200 MHz NR (Note 2) | Square (BW Config ) | 24 (Note 3) | + +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 to bands defined within the frequency spectrum range of 24.25 – 33.4 GHz and 37 – 52.6 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 9.7.3.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}}$ ) | 24 (Note 3) | +| 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}}$ ) | 24 (Note 3) | + +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 9.7.3.3-5: Local Area IAB-MT type 2-O CACLR absolute limit** + +| IAB-MT class | CACLR absolute limit | +|---------------------|-----------------------------| +| Local area IAB-MT | -20 dBm/MHz | + +**Table 9.7.3.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 | + +## 9.7.4 OTA operating band unwanted emissions + +### 9.7.4.1 General + +The OTA limits for operating band unwanted emissions are specified as TRP per RIB unless otherwise stated. + +### 9.7.4.2 Minimum requirement for IAB-DU type 1-O + +Out-of-band emissions in FR1 are limited by OTA operating band unwanted emission limits. Unless otherwise stated, the operating band unwanted emission 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 9.7.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. For a *RIB* operating in multi-carrier or contiguous CA, the requirements apply to *IAB-DU channel bandwidths* of the outermost carrier for the frequency ranges defined in clause 6.6.4.1. + +For a *RIB* operating in *non-contiguous spectrum*, the requirements shall apply inside any *sub-block gap* for the frequency ranges defined in clause 6.6.4.1. + +For a *multi-band RIB*, the requirements shall apply inside any *Inter RF Bandwidth gap* for the frequency ranges defined in clause 6.6.4.1. + +The OTA operating band unwanted emission requirement for *IAB-DU type 1-O* is that for each applicable *basic limit* in clause 6.6.4.2, the power of any unwanted emission shall not exceed an OTA limit specified as the *basic limit* + X, where X = 9 dB. + +### 9.7.4.3 Minimum requirement for *IAB-MT type 1-O* + +Out-of-band emissions in FR1 are limited by OTA operating band unwanted emission limits. Unless otherwise stated, the operating band unwanted emission limits in FR1 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 9.7.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. For a *RIB* operating in multi-carrier or contiguous CA, the requirements apply to *IAB-MT channel bandwidths* of the outermost carrier for the frequency ranges defined in clause 6.6.4.1. + +For a *RIB* operating in *non-contiguous spectrum*, the requirements shall apply inside any *sub-block gap* for the frequency ranges defined in clause 6.6.4.1. + +For a *multi-band RIB*, the requirements shall apply inside any *Inter RF Bandwidth gap* for the frequency ranges defined in clause 6.6.4.1. + +The OTA operating band unwanted emission requirement for *IAB-MT type 1-O* is that for each applicable *basic limit* in clause 6.6.4.2, the power of any unwanted emission shall not exceed an OTA limit specified as the *basic limit* + X, where $X = 10 \log_{10}(N_{\text{TXU, counted per cell}})$ dB. + +### 9.7.4.4 Additional requirements + +#### 9.7.4.4.1 Limits in FCC Title 47 + +The IAB-DU and IAB-MT may have to comply with the applicable emission limits established by FCC Title 47 [20], when deployed in regions where those limits are applied, and under the conditions declared by the manufacturer. + +### 9.7.4.5 Minimum requirement for *IAB-DU type 2-O* and *IAB-MT type 2-O* + +#### 9.7.4.5.1 General + +The requirements of either clause 9.7.4.5.2 (Category A limits) or clause 9.7.4.5.3 (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-DU and IAB-MT type 2-O*) in clause 9.7.6.3.2. In addition, the limits in clause 9.7.4.5.4 may also apply. + +Out-of-band emissions in FR2-1 are limited by OTA operating band unwanted emission limits. + +For IAB-DU type 2-O, unless otherwise stated, the OTA operating band unwanted emission limits in FR2-1 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*. + +For IAB-MT type 2-O, unless otherwise stated, the OTA operating band unwanted emission limits in FR2-1 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 9.7.1-1 and 9.7.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. 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*. + +Emissions 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_{\text{offset}}$ is the separation between the *contiguous transmission bandwidth* edge frequency and the centre of the measuring filter. +- $f_{\text{offsetmax}}$ is the offset to the frequency $\Delta f_{\text{OBUE}}$ outside the downlink *operating band*, where $\Delta f_{\text{OBUE}}$ is defined in table 9.7.1-1. + +- $\Delta f_{\max}$ is equal to $f\_offset_{\max}$ minus half of the bandwidth of the measuring filter. + +In addition, inside any *sub-block gap* for a *RIB* operating in *non-contiguous spectrum*, emissions shall not exceed the cumulative sum of the limits specified for the adjacent *sub-blocks* on each side of the *sub-block gap*. The limit for each *sub-block* is specified in clauses 9.7.4.5.2 and 9.7.4.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. + +#### 9.7.4.5.2 OTA operating band unwanted emission limits (Category A) + +IAB-DU and IAB-MT unwanted emissions shall not exceed the maximum levels specified in table 9.7.4.3.2-1 and 9.7.4.3.2-2. + +**Table 9.7.4.5.2-1: OBUE limits applicable in the frequency range 24.25 – 33.4 GHz** + +| Frequency offset of measurement filter -3B point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | 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}(-5 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 35 \text{ dB}, -12 \text{ dBm}))$ | 1 MHz | +| $0.1 \cdot \text{BW}_{\text{contiguous}} \leq \Delta f < \Delta f_{\max}$ | $0.1 \cdot \text{BW}_{\text{contiguous}} + 0.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $\text{Min}(-13 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 43 \text{ dB}, -20 \text{ dBm}))$ | 1 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 . | | | | + +**Table 9.7.4.5.2-2: OBUE limits applicable in the frequency range 37 – 52.6 GHz** + +| Frequency offset of measurement filter -3B point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | 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}(-5 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 33 \text{ dB}, -12 \text{ dBm}))$ | 1 MHz | +| $0.1 \cdot \text{BW}_{\text{contiguous}} \leq \Delta f < \Delta f_{\max}$ | $0.1 \cdot \text{BW}_{\text{contiguous}} + 0.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $\text{Min}(-13 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 41 \text{ dB}, -20 \text{ dBm}))$ | 1 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 . | | | | + +### 9.7.4.5.3 OTA operating band unwanted emission limits (Category B) + +IAB-DU and IAB-MT unwanted emissions shall not exceed the maximum levels specified in table 9.7.4.5.3-1 or 9.7.4.5.3-2. + +**Table 9.7.4.5.3-1: OBUE limits applicable 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$ | 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}(-5 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 35 \text{ dB}, -12 \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 9.7.4.5.3-2: OBUE limits applicable 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$ | 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}(-5 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 33 \text{ dB}, -12 \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}$ . + +### 9.7.4.5.4 Additional OTA operating band unwanted emission requirements + +#### 9.7.4.5.4.1 Protection of Earth Exploration Satellite Service + +For IAB-DU and IAB-MT operating in the frequency range 24.25 – 27.5 GHz, the power of unwanted emission shall not exceed the limits in table 9.7.4.5.4.1-1. + +**Table 9.7.4.5.4.1-1: OBUE limits for protection of Earth Exploration Satellite Service** + +| Frequency range | Limit | Measurement Bandwidth | +|-----------------|-----------------|-----------------------| +| 23.6 – 24 GHz | -3 dBm (Note 1) | 200 MHz | +| 23.6 – 24 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 and enters into force from January 1, 2021. +NOTE 2: This limit applies to IAB-DU and IAB-MT brought into use after 1 September 2027. + +## 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 IAB-DU type 1-O and IAB-MT type 1-O + +### 9.7.5.2.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 ITU-R recommendation SM.329 [16]. + +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 ITU-R recommendation SM.329 [16]. + +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. + +### 9.7.5.2.2 General OTA transmitter spurious emissions requirements + +The Tx spurious emissions requirements for *IAB-DU type 1-O* are that for each applicable *basic limit* above 30 MHz in clause 6.6.5.2.1, the TRP of any spurious emission shall not exceed an OTA limit specified as the *basic limit* + X, where X = 9 dB, unless stated differently in regional regulation. + +The Tx spurious emissions requirements for *IAB-MT type 1-O* are that for each applicable *basic limit* above 30 MHz in clause 6.6.5.2.1, the TRP of any spurious emission shall not exceed an OTA limit specified as the *basic limit* + X, where $X = 10 \log_{10}(N_{\text{TXU, counted per cell}})$ dB, unless stated differently in regional regulation. + +### 9.7.5.2.3 Additional spurious emissions requirements + +These requirements may be applied for the protection of systems operating in frequency ranges other than IAB-DU downlink *operating band* or IAB-MT uplink *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.5. + +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 Tx additional spurious emissions requirements for *IAB-DU type 1-O* and *IAB-MT type 1-O* are that for each applicable *basic limit* in clause 6.6.5.2.2, the TRP of any spurious emission shall not exceed an OTA limit specified as the *basic limit* + X, where X = 9 dB for IAB-DU and $X = 10 \log_{10}(N_{\text{TXU, counted per cell}})$ dB for IAB-MT. + +### 9.7.5.2.4 Co-location with other base stations and IAB-Nodes + +These requirements may be applied for the protection of other receivers when GSM900, DCS1800, PCS1900, GSM850, CDMA850, UTRA FDD, UTRA TDD, E-UTRA, NR BS, IAB-DU and/or IAB-MT are co-located with an IAB-Node. + +The requirements assume co-location with 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, the power levels are specified at the *co-location reference antenna* output(s). + +The power sum of any spurious emission is specified over all supported polarizations at the output(s) of the *co-location reference antenna* and shall not exceed the *basic limits* in clause 6.6.5.2.3 + X dB, where X = -21 dB for IAB-DU and X = -30 + 10log10(NTXU,countedpercell) dB for IAB-MT. + +For a *multi-band RIB*, the exclusions and conditions in the notes column of table 6.6.5.2.3-1 apply for each supported *operating band*. + +### 9.7.5.3 Minimum requirement for IAB-DU type 2-O and IAB-MT type 2-O + +#### 9.7.5.3.1 General + +For IAB-DU type 2-O, the OTA transmitter spurious emission limits apply from 30 MHz to 2nd harmonic of the upper frequency edge of the downlink *operating band*, excluding the frequency range from $\Delta f_{\text{OBUE}}$ below the lowest frequency of the downlink *operating band*, up to $\Delta f_{\text{OBUE}}$ above the highest frequency of the downlink *operating band*, where the $\Delta f_{\text{OBUE}}$ is defined in table 9.7.1-1. + +For IAB-MT type 2-O, the OTA transmitter spurious emission limits apply from 30 MHz to 2nd harmonic of the upper frequency edge of the downlink *operating band*, excluding the frequency range from $\Delta f_{\text{OBUE}}$ below the lowest frequency of the uplink *operating band*, up to $\Delta f_{\text{OBUE}}$ above the highest frequency of the uplink *operating band*, where the $\Delta f_{\text{OBUE}}$ is defined in table 9.7.1-2. + +#### 9.7.5.3.2 General OTA transmitter spurious emissions requirements + +##### 9.7.5.3.2.1 General + +The requirements of either clause 9.7.5.3.2.2 (Category A limits) or clause 9.7.5.3.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 9.7.4. + +##### 9.7.5.3.2.2 OTA transmitter spurious emissions (Category A) + +The power of any spurious emission shall not exceed the limits in table 9.7.5.3.2-1 + +**Table 9.7.5.3.2.2-1: IAB-DU and IAB-MT radiated Tx spurious emission limits in FR2-1** + +| Frequency range | Limit | Measurement Bandwidth | Note | +|----------------------------------------------------------------------------------------------|---------|-----------------------|----------------| +| 30 MHz – 1 GHz | -13 dBm | 100 kHz | Note 1 | +| 1 GHz – 2 nd harmonic of the upper frequency edge of the DL operating band | | 1 MHz | Note 1, Note 2 | +| NOTE 1: Bandwidth as in ITU-R SM.329 [16], s4.1 | | | | +| NOTE 2: Upper frequency as in ITU-R SM.329 [16], s2.5 table 1. | | | | + +##### 9.7.5.3.2.3 OTA transmitter spurious emissions (Category B) + +The power of any spurious emission shall not exceed the limits in table 9.7.5.3.2.3-1. + +**Table 9.7.5.3.2.3-1: IAB-DU and IAB-MT radiated Tx spurious emission limits in FR2-1 (Category B)** + +| Frequency range
(Note 4) | Limit | 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_{\text{step},1}$ | -20 dBm | 10 MHz | Note 2 | +| $F_{\text{step},1} \leftrightarrow F_{\text{step},2}$ | -15 dBm | 10 MHz | Note 2 | +| $F_{\text{step},2} \leftrightarrow F_{\text{step},3}$ | -10 dBm | 10 MHz | Note 2 | +| $F_{\text{step},4} \leftrightarrow F_{\text{step},5}$ | -10 dBm | 10 MHz | Note 2 | +| $F_{\text{step},5} \leftrightarrow F_{\text{step},6}$ | -15 dBm | 10 MHz | Note 2 | +| $F_{\text{step},6} \leftrightarrow$ 2 nd harmonic of
the upper frequency edge
of the DL operating band | -20 dBm | 10 MHz | Note 2, Note 3 | + +NOTE 1: Bandwidth as in ITU-R SM.329 [16], s4.1 +NOTE 2: Limit and bandwidth as in ERC Recommendation 74-01 [19], Annex 2. +NOTE 3: Upper frequency as in ITU-R SM.329 [16], s2.5 table 1. +NOTE 4: The step frequencies $F_{\text{step},x}$ are defined in Table 9.7.5.3.2.3-2. + +**Table 9.7.5.3.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_{\text{step},1}$
(GHz) | $F_{\text{step},2}$
(GHz) | $F_{\text{step},3}$
(GHz)
(Note 2) | $F_{\text{step},4}$
(GHz)
(Note 2) | $F_{\text{step},5}$
(GHz) | $F_{\text{step},6}$
(GHz) | +|----------------|------------------------------|------------------------------|------------------------------------------|------------------------------------------|------------------------------|------------------------------| +| n258 | 18 | 21 | 22.75 | 29 | 30.75 | 40.5 | +| n259 | 23.5 | 35.5 | 38 | 45 | 47.5 | 59.5 | + +NOTE 1: $F_{\text{step},x}$ are based on ERC Recommendation 74-01 [19], Annex 2. +NOTE 2: $F_{\text{step},3}$ and $F_{\text{step},4}$ are aligned with the values for $\Delta f_{\text{OBUE}}$ in Table 9.7.1-1 and Table 9.7.1-2. + +### 9.7.5.3.3 Additional OTA transmitter spurious emissions requirements + +These requirements may be applied for the protection of systems operating in frequency ranges other than the IAB-Node. 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.5. + +#### 9.7.5.3.3.1 Limits for protection of Earth Exploration Satellite Service + +For IAB-DU and IAB-MT operating in the frequency range 24.25 – 27.5 GHz, the power of any spurious emissions shall not exceed the limits in Table 9.7.5.3.3.1-1. + +**Table 9.7.5.3.3.1-1: 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-DU and IAB-MT brought into use on or before 1 September 2027 and enters into force from January 1, 2021. +NOTE 2: This limit applies to IAB-DU and IAB-MT brought into use after 1 September 2027. + +## 9.8 OTA transmitter intermodulation + +### 9.8.1 General + +The OTA transmitter intermodulation requirement is a measure of the capability of the transmitter unit to inhibit the generation of signals in its non-linear elements caused by presence of the wanted signal and an interfering signal reaching the transmitter unit via the RDN and antenna array from a co-located base station or IAB. The requirement applies during the *transmitter ON period* and the *transmitter transient period*. + +The requirement shall apply at each RIB supporting transmission in the *operating band*. + +The transmitter intermodulation level is the *total radiated power* of the intermodulation products when an interfering signal is injected into the *co-location reference antenna*. + +The OTA transmitter intermodulation requirement is not applicable for *IAB type 2-O*. + +## 9.8.2 Minimum requirement for *IAB-DU type 1-O* and *IAB-MT type 1-O* + +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 9.7.5.2 (except clause 9.7.5.2.3), OTA operating band unwanted emissions in clauses 9.7.4.2 and 9.7.4.3, and OTA ACLR in clause 9.7.3.2 in the presence of a wanted signal and an interfering signal, defined in table 9.8.2-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 \cdot BW_{\text{Channel}}$ (where $BW_{\text{Channel}}$ is the minimal *IAB-DU Channel Bandwidth* or *IAB-MT 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 9.8. 2-1: Interfering and wanted signals for the OTA transmitter intermodulation requirement** + +| Parameter | Value | +|--------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Wanted signal | NR signal 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}}$ ) with or IAB-MT Channel Bandwidth ( $BW_{\text{Channel}}$ ) 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 RIB 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 polarizations at the *co-location reference antenna*. + +# 10 Radiated receiver characteristics + +## 10.1 General + +Radiated receiver characteristics are specified at RIB for *IAB type 1-H*, *IAB type 1-O*, or *IAB type 2-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 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*. +- Each requirement shall be met over the RoAoA specified. + +NOTE 2: In normal operating condition the IAB in TDD operation is configured to TX OFF power during *receive period*. + +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)}$$ + +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}$$ + +## 10.2 OTA sensitivity + +### 10.2.1 IAB-DU OTA sensitivity + +#### 10.2.1.1 IAB-DU type 1-H and IAB-DU type 1-O + +The OTA sensitivity requirement is a *directional requirement* based upon the declaration of one or more *OTA sensitivity directions declaration* (OSDD), related to a *IAB-DU type 1-H* and *IAB-DU type 1-O* receiver. + +The IAB-DU reference sensitivity level is specified the same as the BS reference sensitivity level requirement for BS in TS 38.104 [2], subclause 10.2.1, where references to *BS channel bandwidth* apply to *IAB-DU channel bandwidth*. + +#### 10.2.1.2 IAB-DU type 2-O + +There is no OTA sensitivity requirement for FR2-1, the OTA sensitivity is the same as the OTA reference sensitivity in clause 10.3. + +### 10.2.2 IAB-MT OTA sensitivity + +#### 10.2.2.1 IAB-MT type 1-H and IAB-MT type 1-O + +##### 10.2.2.1.1 General + +The OTA sensitivity requirement is a *directional requirement* based upon the declaration of one or more *OTA sensitivity directions declaration* (OSDD), related to a *IAB-MT type 1-H* and *IAB-MT type 1-O* receiver. + +The *IAB-MT type 1-H* and *IAB-MT type 1-O* may optionally be capable of redirecting/changing the *receiver target* by means of adjusting IAB-MT settings resulting in multiple *sensitivity RoAoA*. The *sensitivity RoAoA* resulting from the current IAB-MT settings is the active *sensitivity RoAoA*. + +If the IAB-MT is capable of redirecting the *receiver target* related to the OSDD then the OSDD shall include: + +- *IAB-MT 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 IAB-MT. +- Five declared *sensitivity RoAoA* comprising the conformance testing directions as detailed in TS 38.141-2 [21]. +- 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-MT is not capable of redirecting the *receiver target* related to the OSDD, then the OSDD includes only: + +- The set(s) of RAT, *IAB-MT channel bandwidth* and declared minimum EIS level applicable to the *sensitivity RoAoA* in the OSDD. +- One declared active *sensitivity RoAoA*. +- The *receiver target reference direction*. + +NOTE 4: For IAB-MT 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.1.2 Minimum requirement + +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.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 *IAB-MT channel bandwidth*. + +#### 10.2.2.2 IAB-MT type 2-O + +There is no OTA sensitivity requirement for FR2-1, the OTA sensitivity is the same as the OTA reference sensitivity in clause 10.3. + +### 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 IAB-DU OTA reference sensitivity level + +### 10.3.2.1 Minimum requirement for IAB-DU type 1-O + +The wide area IAB-DU reference sensitivity level is specified the same as the wide area BS reference sensitivity level requirement for BS in TS 38.104[2], subclause 10.3.2, where references to *BS channel bandwidth* apply to *IAB-DU channel bandwidth*. + +The medium range IAB-DU reference sensitivity level is specified the same as the medium range BS reference sensitivity level requirement for BS in TS 38.104[2], subclause 10.3.2, where references to *BS channel bandwidth* apply to *IAB-DU channel bandwidth*. + +The local area IAB-DU reference sensitivity level is specified the same as the local area BS reference sensitivity level requirement for BS in TS 38.104[2], subclause 10.3.2, where references to *BS channel bandwidth* apply to *IAB-DU channel bandwidth*. + +### 10.3.2.2 Minimum requirement for IAB-DU type 2-O + +The wide area IAB-DU reference sensitivity level is specified the same as the wide area BS reference sensitivity level requirement for BS in TS 38.104[2], subclause 10.3.3, where references to *BS channel bandwidth* apply to *IAB-DU channel bandwidth*. + +The medium range IAB-DU reference sensitivity level is specified the same as the medium range BS reference sensitivity level requirement for BS in TS 38.104[2], subclause 10.3.3, where references to *BS channel bandwidth* apply to *IAB-DU channel bandwidth*. + +The local area IAB-DU reference sensitivity level is specified the same as the local area BS reference sensitivity level requirement for BS in TS 38.104[2], subclause 10.3.3, where references to *BS channel bandwidth* apply to *IAB-DU channel bandwidth*. + +## 10.3.3 IAB-MT OTA reference sensitivity level + +### 10.3.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. + +### 10.3.3.2 Minimum requirement for IAB-MT 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.3.2-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) | +|-------------------------------------------------|----------------------------------|--------------------------------------|--------------------------------------------------------------------------| +| 10, 15 | 30 | G-FR1-A1-22 | $-102.0 - \Delta_{OTAREFSENS}$ | +| 10, 15 | 60 | G-FR1-A1-23 | $-99.0 - \Delta_{OTAREFSENS}$ | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-25 | $-95.4 - \Delta_{OTAREFSENS}$ | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-26 | $-95.6 - \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 *IAB-MT channel bandwidth*. + +**Table 10.3.3.2-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, EISREFSENS (dBm) | +|-------------------------------------------------|----------------------------------|--------------------------------------|---------------------------------------------------------------------| +| 10, 15 | 30 | G-FR1-A1-22 | -94.0 - Δ OTAREFSENS | +| 10, 15 | 60 | G-FR1-A1-23 | -91.0 - Δ OTAREFSENS | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-25 | -87.4 - Δ OTAREFSENS | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-26 | -87.6 - Δ 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*. + +### 10.3.3.3 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, EISREFSENS\_50M is an integer value in the range -86 to -114 dBm. The specific value is declared by the vendor. + +**Table 10.3.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, EISREFSENS (dBm) | +|---------------------------------------|----------------------------------|--------------------------------------|---------------------------------------------------------------------| +| 50, 100, 200 | 60 | G-FR2-A1-21 | EIS REFSENS_50M + Δ FR2_REFSENS | +| 50 | 120 | G-FR2-A1-22 | EIS REFSENS_50M + Δ FR2_REFSENS | +| 100, 200, 400 | 120 | G-FR2-A1-23 | EIS REFSENS_50M + 3 + Δ 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-MT channel bandwidth*. + +NOTE 2: The declared EISREFSENS\_50M shall be within the range specified above. + +## 10.4 OTA Dynamic range + +### 10.4.1 IAB-DU OTA dynamic range + +#### 10.4.1.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 [*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*. + +#### 10.4.1.2 Minimum requirement for *IAB-DU type 1-O* + +The wide area IAB-DU dynamic range is specified the same as the wide area BS dynamic requirement for BS *type 1-O* in TS 38.104[2], subclause 10.4.2, where references to *BS channel bandwidth* apply to *IAB-DU channel bandwidth*. + +The medium range IAB-DU dynamic range is specified the same as the medium range BS dynamic range requirement for BS *type 1-O* in TS 38.104[2], subclause 10.4.2, where references to *BS channel bandwidth* apply to *IAB-DU channel bandwidth*. + +The local area IAB-DU dynamic range is specified the same as the local area BS dynamic range requirement for BS *type 1-O* in TS 38.104[2], subclause 10.4.2, where references to *BS channel bandwidth* apply to *IAB-DU 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 *IAB-DU type 1-O* + +Minimum requirement is the same as specified for BS type 1-O in TS38.104[2], subclause 10.5.1.2. + +##### 10.5.1.3 Minimum requirement for *IAB-DU type 2-O* + +Minimum requirement is the same as specified for BS type 2-O in TS38.104[2], subclause 10.5.1.3. + +##### 10.5.1.4 Minimum requirement 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-1, the OTA wanted and the interfering signal are specified in table 10.5.1.4-1 and table 10.5.1.4-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 F. + +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 10.5.1.4-2. The OTA interfering signal offset is defined relative to the sub-block edges inside the sub-block gap. + +**Table 10.5.1.4-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 [ 10.3.3] | | | + +**Table 10.5.1.4-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 | | + +### 10.5.1.5 Minimum requirement 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 $\geq 95\%$ of the maximum throughput of the reference measurement channel. + +For FR1, the OTA wanted and the interfering signal are specified in table 10.5.1.5-1, table 10.5.1.5-2 and table 10.5.1.5-3 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 F. + +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 10.5.1.5-2 and table 10.5.1.5-3. 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 10.5.1.5-2 and table 10.5.1.5-3. The interfering signal offset is defined relative to the *IAB-MT RF Bandwidth edges* inside the *Inter RF Bandwidth gap*. + +**Table 10.5.1.5-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) | $EI_{S_{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: $EI_{S_{minSENS}}$ depends on the IAB-MT channel bandwidth | | | + +**Table 10.5.1.5-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$ | | + +## 10.5.2 OTA in-band blocking + +### 10.5.2.1 General + +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. + +### 10.5.2.2 Minimum requirement for IAB-DU type 1-O + +Minimum requirement is the same as specified for BS type 1-O in TS38.104[2], subclause 10.5.2.2. + +### 10.5.2.3 Minimum requirement for IAB DU type 2-O + +Minimum requirement is the same as specified for BS type 2-O in TS38.104[2], subclause 10.5.2.3. + +### 10.5.2.4 Minimum requirement for IAB-MT of 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 REFSSENS 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 10.5.2.4-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 F. + +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 10.5.2.4-0. + +**Table 10.5.2.4-0: $\Delta f_{OOB}$ offset for NR operating bands for Wide Area IAB-MT in FR2-1** + +| 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 10.5.2.4-1. The interfering signal offset is defined relative to the sub-block edges inside the sub-block gap. + +**Table 10.5.2.4-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 | $EIS_{REFSENS} + 6$ dB | $EIS_{REFSENS\_50M} + 33 + \Delta f_{FR2\_REFSENS}$ | $\pm 75$ | 50 MHz CP-OFDM NR signal, 60 kHz SCS, 64 RBs | +| NOTE: $EIS_{REFSENS}$ and $EIS_{REFSENS\_50M}$ are given in subclause [ 10.3.3]. | | | | | + +## 10.5.2.5 Minimum requirement for *IAB-MT of 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 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 F. + +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_{DL,low} - \Delta f_{OOB}$ to $F_{DL,high} + \Delta f_{OOB}$ . The $\Delta f_{OOB}$ for *wide area IAB-MT type 1-O* is defined in table 10.5.2.5-0. + +**Table 10.5.2.5-0: $\Delta f_{OOB}$ offset for NR operating bands in FR1** + +| IAB-MT type | Operating band characteristics | $\Delta f_{OOB}$ (MHz) | +|------------------------|--------------------------------------------------------|------------------------| +| IAB-MT type 1-O | $F_{DL,high} - F_{DL,low} < 100$ MHz | 20 | +| | $100$ MHz $\leq F_{DL,high} - F_{DL,low} \leq 900$ 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.5-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 10.5.2.5-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 10.5.2.5-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 10.5.2.5-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 | +|------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------| +| | | 5 MHz CP-OFDM NR signal, 15 kHz SCS, 1 RB | +| 10 | ±(355 + m*180),
m=0, 1, 2, 3, 4, 9, 14, 19, 24 | | +| 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, 99 | | +| 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. + +## 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 IAB-MT type 1-O and 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 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-2, 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 and subclause 10.3.3 for each *IAB-Node channel bandwidth*. + +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 table 10.6.2-1 shall be excluded from the OTA out-of-band blocking requirement. + +For 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 FR1 OTA out-of-band blocking requirement is defined in table 10.6.2-1. + +**Table 10.6.2-1: $\Delta f_{OOB}$** + +| Operating band characteristics | $\Delta f_{OOB}$ (MHz) | +|--------------------------------------------------------|------------------------| +| $F_{UL,high} - F_{UL,low} < 100$ MHz | 20 | +| $100$ MHz $\leq F_{UL,high} - F_{UL,low} \leq 900$ MHz | 60 | + +**Table 10.6.2-2: 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 | CW | +| NOTE 1: $EIS_{minSENS}$ depends on the channel bandwidth as specified in clause 9.2.
NOTE 2: The RMS field-strength level in V/m is related to the interferer EIRP level at a distance described as $r$ , where EIRP is in W and $r$ is in m; for example, 0.36 V/m is equivalent to 36 dBm at fixed distance of 30 m. | | | + +### 10.6.3 Minimum requirement for IAB-MT type 2-O and IAB-DU type 2-O + +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 *OTA REFSENS 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 *IAB type 2-O* the OTA out-of-band blocking requirement apply from 30 MHz to $F_{UL,low} - 1500$ MHz and from $F_{UL,high} + 1500$ MHz up to 2nd harmonic of the upper frequency edge of the *operating band*. + +For OTA wanted and OTA interfering signals provided at the RIB using the parameters in table 10.6.3-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 subclause 10.3.2 and subclause 10.3.3 for each *IAB Node channel bandwidth*. + +**Table 10.6.3-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 | +| 12750 to F UL,low – 1500 | EIS REFSENS + 6 dB | 0.1 | CW | +| F UL,high + 1500 to 2 nd harmonic of the upper frequency edge of the operating band | EIS REFSENS + 6 dB | 0.1 | CW | + +## 10.6.4 Co-location minimum requirement for IAB-MT type 1-O and IAB-DU type 1-O + +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 10.6.4-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 for each *IAB channel bandwidth* and further specified in annex A.1. The characteristics of the interfering signal is further specified in annex F. + +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 10.6.4-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 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 | 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 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_{\text{foob}}$ immediately outside any of the supported downlink *operating band(s)*. + +## 10.7 OTA receiver spurious emissions + +### 10.7.1 General + +The OTA RX spurious emission is the power of the emissions radiated from the antenna array from a receiver unit. + +The metric used to capture OTA receiver spurious emissions for IAB-MT and IAB-DU for *IAB type 1-O* and *IAB type 2-O* is *total radiated power (TRP)*, with the requirement defined at the RIB. + +For *IAB-MT type 1-O* manufacturer shall declare $N_{\text{RXU,active}}$ . $N_{\text{RXU,active}}$ active receiver units supporting the same *operating band* is implementation dependent. + +The number of active receiver units that are considered when calculating the radiated RX spurious emission limits ( $N_{\text{RXU,counted}}$ ) for *IAB-MT type 1-O* is calculated as follows: + +$$N_{RXU,counted} = \min(N_{RXU,active}, 8)$$ + +$N_{RXU,countedpercell}$ is used for scaling of *basic limits* and is derived as $N_{RXU,countedpercell} = N_{RXU,counted}$ . + +NOTE: $N_{RXU,active}$ is the number of actually active receiver units. + +## 10.7.2 IAB-DU OTA receiver spurious emissions + +### 10.7.2.1 Minimum requirement for IAB-DU type 1-O + +Minimum requirement is the same as specified for BS type 1-O in TS 38.104[2], subclause 10.7.2. + +### 10.7.2.2 Minimum requirement for IAB-DU type 2-O + +Minimum requirement is the same as specified for BS type 2-O in TS 38.104[2], subclause 10.7.3. + +## 10.7.3 IAB-MT OTA receiver spurious emissions + +### 10.7.3.1 Minimum requirement for IAB-MT type 1-O + +For an IAB-MT operating in TDD, the OTA RX spurious emissions requirement shall apply during the *transmitter OFF period* only. + +For RX only *multi-band RIB*, the OTA RX spurious emissions requirements are subject to exclusion zones in each supported *operating band*. + +The OTA RX spurious emissions requirement for *IAB-MT type 1-O* is that for each *basic limit* specified in table 10.7.3.1-1, the power sum of emissions at the RIB shall not exceed limits specified as the *basic limit* + X, where $X = 10\log_{10}(N_{RXU,countedpercell})$ dB, unless stated differently in regional regulation. + +**Table 10.7.3.1-1: General receiver spurious emission basic limits for IAB-MT type 1-O** + +| Spurious frequency range | Basic limit (Note 4) | Measurement bandwidth | Notes | +|--------------------------------------------------------------------------------------------------|----------------------|-----------------------|------------------------| +| 30 MHz – 1 GHz | -36 dBm | 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 [16], s4.1. +NOTE 2: Upper frequency as in ITU-R SM.329 [16], 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: Additional limits may apply regionally. + +### 10.7.3.2 Minimum requirement for IAB-MT type 2-O + +The OTA RX spurious emissions requirement shall apply during the *transmitter OFF period* only. + +For the Wide Area *IAB-MT type 2-O*, the power of any RX spurious emission shall not exceed the limits in table 10.7.3.2-1. + +### 10.7.3.2-1: Radiated Rx spurious emission limits for IAB-MT 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_{\text{step},1}$ | -20 dBm | 10 MHz | Note 2 | +| $F_{\text{step},1} \leftrightarrow F_{\text{step},2}$ | -15 dBm | 10 MHz | Note 2 | +| $F_{\text{step},2} \leftrightarrow F_{\text{step},3}$ | -10 dBm | 10 MHz | Note 2 | +| $F_{\text{step},4} \leftrightarrow F_{\text{step},5}$ | -10 dBm | 10 MHz | Note 2 | +| $F_{\text{step},5} \leftrightarrow F_{\text{step},6}$ | -15 dBm | 10 MHz | Note 2 | +| $F_{\text{step},6} \leftrightarrow$ 2 nd harmonic of the upper frequency edge of the DL operating band | -20 dBm | 10 MHz | Note 2, Note 3 | + +NOTE 1: Bandwidth as in ITU-R SM.329 [16], s4.1. +NOTE 2: Limit and bandwidth as in ERC Recommendation 74-01 [17], Annex 2. +NOTE 3: Upper frequency as in ITU-R SM.329 [16], s2.5 table 1. +NOTE 4: The step frequencies $F_{\text{step},x}$ are defined in table 10.7.3.2-2. +NOTE 5: Additional limits may apply regionally. + +**Table 10.7.3.2-2: Step frequencies for defining the radiated Rx spurious emission limits for IAB-MT type 2-O** + +| Operating band | $F_{\text{step},1}$ (GHz) | $F_{\text{step},2}$ (GHz) | $F_{\text{step},3}$ (GHz) | $F_{\text{step},4}$ (GHz) | $F_{\text{step},5}$ (GHz) | $F_{\text{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 | + +## 10.8 OTA receiver intermodulation + +### 10.8.1 General + +Third and higher order mixing of the two interfering RF signals can produce an interfering signal in the band of the desired channel. Intermodulation response rejection is a measure of the capability of the receiver unit to receive a wanted signal on its assigned channel frequency in the presence of two interfering signals which have a specific frequency relationship to the wanted signal. The requirement is defined as a directional requirement at the RIB. + +### 10.8.2 Minimum requirement for IAB-DU type 1-O + +The Wide Area IAB-DU receiver intermodulation requirement is specified the same as the Wide Area receiver intermodulation requirement for BS type 1-O in TS 38.104 [2], subclause 10.8.2, where references to *BS channel bandwidth* apply to *IAB-DU channel bandwidth*. + +The Medium Range IAB-DU receiver intermodulation requirement is specified the same as the Medium Range BS receiver intermodulation requirement for BS type 1-O in TS 38.104 [2], subclause 10.8.2, where references to *BS channel bandwidth* apply to *IAB-DU channel bandwidth*. + +The Local Area IAB-DU receiver intermodulation requirement is specified the same as the Local Area BS receiver intermodulation requirement for BS type 1-O in TS 38.104 [2], subclause 10.8.2, where references to *BS channel bandwidth* apply to *IAB-DU channel bandwidth*. + +### 10.8.3 Minimum requirement for IAB-DU type 2-O + +The Wide Area IAB-DU receiver intermodulation requirement is specified the same as the Wide Area receiver intermodulation requirement for BS type 2-O in TS 38.104 [2], subclause 10.8.3, where references to *BS channel bandwidth* apply to *IAB-DU channel bandwidth*. + +The Medium Range IAB-DU receiver intermodulation requirement is specified the same as the Medium Range BS receiver intermodulation requirement for BS *type 2-O* in TS 38.104 [2], subclause 10.8.3, where references to *BS channel bandwidth* apply to *IAB-DU channel bandwidth*. + +The Local Area IAB-DU receiver intermodulation requirement is specified the same as the Local Area BS receiver intermodulation requirement for BS *type 2-O* in TS 38.104 [2], subclause 10.8.3, where references to *BS channel bandwidth* apply to *IAB-DU channel bandwidth*. + +## 10.8.4 Minimum requirement for *IAB-MT type 1-O* + +The Wide Area IAB-MT receiver intermodulation requirement is specified the same as the Wide Area receiver intermodulation requirement for BS *type 1-O* in TS 38.104 [2], subclause 10.8.2, where references to *BS channel bandwidth* apply to *IAB-MT channel bandwidth*. + +The Local Area IAB-MT receiver intermodulation requirement is specified the same as the Local Area BS receiver intermodulation requirement for BS *type 1-O* in TS 38.104 [2], subclause 10.8.2, where references to *BS channel bandwidth* apply to *IAB-MT channel bandwidth*. + +Interfering signal for IAB-MT *type 1-O* should be CP-OFDM. + +# 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 *IAB-DU type 1-O* + +The wide area IAB-DU receiver in-channel selectivity requirement is specified the same as the wide area receiver in-channel selectivity requirement for BS *type 1-O* in TS 38.104[2], subclause 10.9.2, where references to *BS channel bandwidth* apply to *IAB-DU channel bandwidth*. + +The medium range IAB-DU receiver in-channel selectivity requirement is specified the same as the medium range BS receiver in-channel selectivity requirement for BS *type 1-O* in TS 38.104[2], subclause 10.9.2, where references to *BS channel bandwidth* apply to *IAB-DU channel bandwidth*. + +The local area IAB-DU receiver in-channel selectivity requirement is specified the same as the local area BS receiver in-channel selectivity requirement for BS *type 1-O* in TS 38.104[2], subclause 10.9.2, where references to *BS channel bandwidth* apply to *IAB-DU channel bandwidth*. + +## 10.9.3 Minimum requirement for *IAB-DU type 2-O* + +The wide area IAB-DU receiver in-channel selectivity requirement is specified the same as the wide area receiver in-channel selectivity requirement for BS *type 2-O* in TS 38.104[2], subclause 10.9.3, where references to *BS channel bandwidth* apply to *IAB-DU channel bandwidth*. + +The medium range IAB-DU receiver in-channel selectivity requirement is specified the same as the medium range BS receiver in-channel selectivity requirement for BS *type 2-O* in TS 38.104[2], subclause 10.9.3, where references to *BS channel bandwidth* apply to *IAB-DU channel bandwidth*. + +The local area IAB-DU receiver in-channel selectivity requirement is specified the same as the local area BS receiver in-channel selectivity requirement for BS *type 2-O* in TS 38.104[2], subclause 10.9.3, where references to *BS channel bandwidth* apply to *IAB-DU channel bandwidth*. + +## 11 Radiated performance requirements + +### 11.1 IAB-DU performance requirements + +#### 11.1.1 General + +Radiated performance requirements specify the ability of the *IAB-DU type 1-O* or *IAB-DU 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 IAB-DU are specified for the fixed reference channels defined in annex A and the propagation conditions in annex I. The requirements only apply to those FRCs that are supported by the IAB-DU. + +The radiated performance requirements for *IAB-DU type 1-O* and for *IAB-DU type 2-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 IAB-DU, with the required SNR applied separately per polarization. + +NOTE 1: The 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. + +In tests performed with signal generators a synchronization signal may be provided from the IAB-DU 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 energy in a slot on a RIB. + +N is the noise energy in a bandwidth corresponding to the *transmission bandwidth* over the duration of a slot on a RIB. + +#### 11.1.2 OTA demodulation branches + +Radiated performance requirements are only specified for up to 2 *demodulation branches*. + +If the *IAB-DU type 1-O*, or the *IAB-DU 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-DU type 1-O*, or the *IAB-DU 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). + +## 11.1.2 Performance requirements for PUSCH + +### 11.1.2.1 Performance requirements for IAB type 1-O + +#### 11.1.2.1.1 Performance requirements for PUSCH with transform precoding disabled + +Apply the requirements defined in clause 8.1.2.1 for 2Rx. + +#### 11.1.2.1.2 Performance requirements for PUSCH with transform precoding enabled + +Apply the requirements defined in clause 8.1.2.2 for 2Rx. + +#### 11.1.2.1.3 Performance requirements for UCI multiplexed on PUSCH + +Apply the requirements defined in clause 8.1.2.3 for 2Rx. + +### 11.1.2.2 Performance requirements for IAB type 2-O + +#### 11.1.2.2.1 Performance requirements for PUSCH with transform precoding disabled + +##### 11.1.2.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 the maximum throughput for the FRCs listed in annex A. The performance requirements assume HARQ retransmissions. + +**Table 11.1.2.2.1.1-1: Test parameters for PUSCH testing** + +| Parameter | | Value | +|------------------------------------------------------------------------------------|-------------------------------------------|-----------------------------------------------| +| Transform precoding | | Disabled | +| Default TDD UL-DL pattern (Note 1) | | 60 kHz and 120kHz SCS:
3D1S1U, S=10D:2G:2U | +| Cyclic prefix | | Normal | +| 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 symbols | 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, n_{SCID}=0$ | +| Time domain resource | PUSCH mapping type | B | +| | Start symbol index | 0 | +| | Allocation length | 10 | +| Frequency domain resource | 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 | +| PT-RS configuration | Frequency density ( $K_{PT-RS}$ ) | 2, Disabled | +| | Time density ( $L_{PT-RS}$ ) | 1, Disabled | +| Note 1: The same requirements are applicable to TDD with different UL-DL patterns. | | | + +#### 11.1.2.2.1.2 Minimum requirements + +The throughput shall be equal to or larger than the 70% of maximum throughput stated in the tables 11.1.2.2.1.2-1 to 11.1.2.2.1.2-5 at the given SNR for 1Tx and for 2Tx two-layer spatial multiplexing transmission. + +**Table 11.1.2.2.1.2-1: Minimum requirements for PUSCH, 50 MHz channel bandwidth, 60 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex I) | FRC (Annex A) | Additional DM-RS position | PT-RS | SNR (dB) | | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|-------|----------|--| +| 1 | 2 | TDLA30-300 Low | D-FR2-A.2.1-1 | pos0 | No | -2.0 | | +| | | | D-FR2-A.2.1-13 | pos1 | No | -2.2 | | +| | | | D-FR2-A.2.3-1 | pos0 | Yes | 12.0 | | +| | | | | | No | 11.5 | | +| | | | D-FR2-A.2.3-11 | pos1 | Yes | 10.7 | | +| | | | | | No | 10.7 | | +| | | TDLA30-75 Low | D-FR2-A.2.4-1 | pos0 | Yes | 13.7 | | +| | | | | | No | 13.1 | | +| | | | D-FR2-A.2.4-6 | pos1 | Yes | 13.4 | | +| | | | | | No | 12.9 | | +| 2 | | TDLA30-300 Low | D-FR2-A.2.1-6 | pos0 | No | 1.5 | | +| | | | D-FR2-A.2.1-18 | pos1 | No | 1.2 | | +| | | | D-FR2-A.2.2-1 | pos0 | Yes | 15.2 | | +| | | | | | No | 14.3 | | +| | | TDLA30-300 Low | D-FR2-A.2.2-6 | pos1 | Yes | 13.8 | | +| | | | | | No | 13.0 | | + +**Table 11.1.2.2.1.2-2: Minimum requirements for PUSCH, 100 MHz channel bandwidth, 60 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex I) | FRC (Annex A) | Additional DM-RS position | PT-RS | SNR (dB) | | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|-------|----------|--| +| 1 | 2 | TDLA30-300 Low | D-FR2-A.2.1-2 | pos0 | No | -2.1 | | +| | | | D-FR2-A.2.1-14 | pos1 | No | -2.4 | | +| | | | D-FR2-A.2.3-2 | pos0 | Yes | 12.2 | | +| | | | | | No | 11.2 | | +| | | | D-FR2-A.2.3-12 | pos1 | Yes | 11.2 | | +| | | | | | No | 10.6 | | +| | | TDLA30-75 Low | D-FR2-A.2.4-2 | pos0 | Yes | 14.2 | | +| | | | | | No | 13.3 | | +| | | | D-FR2-A.2.4-7 | pos1 | Yes | 13.7 | | +| | | | | | No | 13.1 | | +| 2 | | TDLA30-300 Low | D-FR2-A.2.1-7 | pos0 | No | 1.5 | | +| | | | D-FR2-A.2.1-19 | pos1 | No | 1.2 | | +| | | | D-FR2-A.2.2-2 | pos0 | Yes | 16.0 | | +| | | | | | No | 14.9 | | +| | | TDLA30-300 Low | D-FR2-A.2.2-7 | pos1 | Yes | 13.8 | | +| | | | | | No | 13.1 | | + +**Table 11.1.2.2.1.2-3: Minimum requirements for PUSCH, 50 MHz channel bandwidth, 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex I) | 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.8 | +| | | | D-FR2-A.2.1-15 | pos1 | No | -2.1 | +| | | | D-FR2-A.2.3-3 | pos0 | Yes | 11.6 | +| | | | | | No | 10.9 | +| | | | D-FR2-A.2.3-13 | pos1 | Yes | 10.9 | +| | | | | | No | 10.5 | + +| | | | | | | | +|---|--|----------------|----------------|------|-----|------| +| 2 | | TDLA30-75 Low | D-FR2-A.2.4-3 | pos0 | Yes | 13.7 | +| | | | | | No | 13.1 | +| | | | D-FR2-A.2.4-8 | pos1 | Yes | 13.2 | +| | | | | | No | 13.0 | +| | | TDLA30-300 Low | D-FR2-A.2.1-8 | pos0 | No | 1.4 | +| | | | D-FR2-A.2.1-20 | pos1 | No | 1.3 | +| | | | D-FR2-A.2.2-3 | pos0 | Yes | 14.2 | +| | | | | | No | 13.6 | +| | | | D-FR2-A.2.2-8 | pos1 | Yes | 13.9 | + +Table 11.1.2.2.1.2-4: Minimum requirements for PUSCH, 100 MHz channel bandwidth, 120 kHz SCS + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex I) | FRC (Annex A) | Additional DM-RS position | PT-RS | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|-------|----------| +| 1 | 2 | TDLA30-300 Low | D-FR2-A.2.1-4 | pos0 | No | -2.4 | +| | | | D-FR2-A.2.1-16 | pos1 | No | -2.5 | +| | | | D-FR2-A.2.3-4 | pos0 | Yes | 11.9 | +| | | | | | No | 10.5 | +| | | | D-FR2-A.2.3-14 | pos1 | Yes | 11.1 | +| | | | | | No | 10.5 | +| | | TDLA30-75 Low | D-FR2-A.2.4-4 | pos0 | Yes | 13.5 | +| | | | | | No | 12.9 | +| | | | D-FR2-A.2.4-9 | pos1 | Yes | 13.4 | +| | | | | | No | 12.8 | +| 2 | | TDLA30-300 Low | D-FR2-A.2.1-9 | pos0 | No | 1.4 | +| | | | D-FR2-A.2.1-21 | pos1 | No | 1.2 | +| | | | D-FR2-A.2.2-4 | pos0 | Yes | 13.9 | +| | | | | | No | 13.2 | +| | | | D-FR2-A.2.2-9 | pos1 | Yes | 13.5 | + +Table 11.1.2.2.1.2-5: Minimum requirements for PUSCH, 200 MHz channel bandwidth, 120 kHz SCS + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex I) | FRC (Annex A) | Additional DM-RS position | PT-RS | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|-------|----------| +| 1 | 2 | TDLA30-300 Low | D-FR2-A.2.1-5 | pos0 | No | -2.1 | +| | | | D-FR2-A.2.1-17 | pos1 | No | -2.4 | +| | | | D-FR2-A.2.3-5 | pos0 | Yes | 11.3 | +| | | | | | No | 10.9 | +| | | | D-FR2-A.2.3-15 | pos1 | Yes | 11.2 | +| | | | | | No | 10.7 | +| | | TDLA30-75 Low | D-FR2-A.2.4-5 | pos0 | Yes | 14.1 | +| | | | | | No | 13.4 | +| | | | D-FR2-A.2.4-10 | pos1 | Yes | 13.7 | +| | | | | | No | 13.3 | +| 2 | | TDLA30-300 Low | D-FR2-A.2.1-10 | pos0 | No | 1.4 | +| | | | D-FR2-A.2.1-22 | pos1 | No | 1.1 | +| | | | D-FR2-A.2.2-5 | pos0 | Yes | 14.0 | +| | | | | | No | 13.3 | +| | | | D-FR2-A.2.2-10 | pos1 | Yes | 13.6 | + +### 11.1.2.2.2 Performance requirements for PUSCH with transform precoding enabled + +#### 11.1.2.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 the maximum throughput for the FRCs listed in Annex A. The performance requirements assume HARQ retransmissions. + +**Table 11.1.2.2.2.1-1: Test parameters for PUSCH testing** + +| Parameter | | Value | +|------------------------------------------------------------------------------------|-------------------------------------------|----------------------------------------------------------------| +| Transform precoding | | Enabled | +| Default TDD UL-DL pattern (Note 1) | | 60 kHz and 120kHz SCS:
3D1S1U, S=10D:2G:2U | +| Cyclic prefix | | Normal | +| 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 | 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 | B | +| | Start symbol | 0 | +| | Allocation length | 10 | +| Frequency domain resource assignment | RB assignment | 30 PRBs in the middle of the test bandwidth | +| | Frequency hopping | Disabled | +| Code block group based PUSCH transmission | | Disabled | +| PT-RS | | Not configured | +| Note 1: The same requirements are applicable to TDD with different UL-DL patterns. | | | + +#### 11.1.2.2.2.2 Minimum requirements + +The throughput shall be equal to or larger than the 70% of maximum throughput stated in the tables 11.1.2.2.2.2-1 to 11.1.2.2.2.2-2 at the given SNR. + +**Table 11.1.2.2.2.2-1: Minimum requirements for PUSCH, Type B, 50 MHz Channel Bandwidth, 60 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex I) | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|----------| +| 1 | 2 | TDLA30-300 Low | D-FR2-A.2.1-11 | pos0 | -1.8 | +| | | | D-FR2-A.2.1-23 | pos1 | -1.9 | + +**Table 11.1.2.2.2.2-2: Minimum requirements for PUSCH, Type B, 50 MHz Channel Bandwidth, 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex I) | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|----------| +| 1 | 2 | TDLA30-300 Low | D-FR2-A.2.1-12 | pos0 | -1.8 | +| | | | D-FR2-A.2.1-24 | pos1 | -1.9 | + +### 11.1.2.2.3 Performance requirements for UCI multiplexed on PUSCH + +#### 11.1.2.2.3.1 General + +In the tests for UCI multiplexed on PUSCH the UCI information only contains CSI part 1 and CSI part 2 information and there is no HARQ-ACK information transmitted. + +The CSI part 1 block error probability is defined as the probability of incorrectly decoded the CSI part 1 information when the CSI part 1 information is sent as follow: + +where: + +- #(false CSI part 1) denotes the number of incorrectly decoded CSI part 1 information transmitted occasions +- #(CSI part 1) denotes the number of CSI part 1 information transmitted occasions. + +The CSI part 2 block error probability (BLER) is defined as the probability of incorrectly decoded the CSI part 2 information when the CSI part 2 information is sent as follows: + +where: + +- #(false CSI part 2) denotes the number of incorrectly decoded CSI part 2 information transmitted occasions +- #(CSI part 2) denotes the number of CSI part 2 information transmitted occasions. + +The number of UCI information bit payload per slot is defined for two cases as follows: + +- 5 bits in CSI part 1, 2 bits in CSI part 2 +- 20 bits in CSI part 1, 20 bits in CSI part 2 + +The 7bits UCI 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 40bits UCI information case is assumed random information bit selection. + +In both tests, PUSCH data, CSI part 1 and CSI part 2 information are transmitted simultaneously. + +**Table 11.1.2.2.3.1-1: Test parameters for UCI multiplexed on PUSCH testing** + +| Parameter | | Value | | +|------------------------------------------------------------------------------------|------------------------------------------------------------------|-------------------------------------|---------| +| Transform precoding | | Disabled | | +| Default TDD UL-DL pattern (Note 1) | | 120 kHz SCS:
3D1S1U, S=10D:2G:2U | | +| Cyclic prefix | | Normal | | +| 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 | 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 | B | | +| | Start symbol | 0 | | +| | Allocation length | 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 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 TDD with different UL-DL patterns. | | | | + +### 11.1.2.2.3.2 Minimum requirements + +The CSI part 1 block error probability shall not exceed 0.1% at the SNR given in table 11.1.2.2.3.2-1 and table 11.1.2.2.3.2-2. The CSI part 2 block error probability shall not exceed 1% at the SNR given in table 11.1.2.2.3.2-3 and table 11.1.2.2.3.2-4. + +**Table 11.1.2.2.3.2-1: Minimum 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 I) | 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.2 | +| | 2 | TDLA30-300 Low | 40(20,20) | pos0 | D-FR2-A.2.3-3 | 5.8 | +| | 2 | TDLA30-300 Low | 7(5,2) | pos1 | D-FR2-A.2.3-13 | 7.8 | +| | 2 | TDLA30-300 Low | 40(20,20) | pos1 | D-FR2-A.2.3-13 | 5.9 | + +**Table 11.1.2.2.3.2-2: Minimum requirements for UCI multiplexed on PUSCH, Type B, Without PTRS, CSI part 1, 50 MHz Channel Bandwidth, 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex I) | 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.1 | +| | 2 | TDLA30-300 Low | 40(20,20) | pos0 | D-FR2-A.2.3-3 | 5.8 | +| | 2 | TDLA30-300 Low | 7(5,2) | pos1 | D-FR2-A.2.3-13 | 7.3 | +| | 2 | TDLA30-300 Low | 40(20,20) | pos1 | D-FR2-A.2.3-13 | 5.5 | + +**Table 11.1.2.2.3.2-3: Minimum requirements for UCI multiplexed on PUSCH, Type B, With PTRS, CSI part 2, 50 MHz Channel Bandwidth, 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex I) | 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.1 | +| | 2 | TDLA30-300 Low | 40(20,20) | pos0 | D-FR2-A.2.3-3 | 4.0 | +| | 2 | TDLA30-300 Low | 7(5,2) | pos1 | D-FR2-A.2.3-13 | 1.3 | +| | 2 | TDLA30-300 Low | 40(20,20) | pos1 | D-FR2-A.2.3-13 | 4.0 | + +**Table 11.1.2.2.3.2-4: Minimum requirements for UCI multiplexed on PUSCH, Type B, Without PTRS, CSI part 2, 50 MHz Channel Bandwidth, 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex I) | 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.1 | +| | 2 | TDLA30-300 Low | 40(20,20) | pos0 | D-FR2-A.2.3-3 | 3.9 | +| | 2 | TDLA30-300 Low | 7(5,2) | pos1 | D-FR2-A.2.3-13 | 1.2 | +| | 2 | TDLA30-300 Low | 40(20,20) | pos1 | D-FR2-A.2.3-13 | 3.7 | + +## 11.1.3 Performance requirements for PUCCH + +### 11.1.3.1 Performance requirements for IAB type 1-O + +#### 11.1.3.1.1 DTX to ACK probability + +Apply the requirements defined in clause 8.1.3.1 + +#### 11.1.3.1.2 Performance requirements for PUCCH format 0 + +Apply the requirements defined in clause 8.1.3.2 for 2 Rx. + +#### 11.1.3.1.3 Performance requirements for PUCCH format 1 + +Apply the requirements defined in clause 8.1.3.3 for 2Rx. + +#### 11.1.3.1.4 Performance requirements for PUCCH format 2 + +Apply the requirements defined in clause 8.1.3.4 for 2Rx. + +#### 11.1.3.1.5 Performance requirements for PUCCH format 3 + +Apply the requirements defined in clause 8.1.3.5 for 2Rx. + +#### 11.1.3.1.6 Performance requirements for PUCCH format 4 + +Apply the requirements defined in clause 8.1.3.6 for 2Rx. + +#### 11.1.3.1.7 Performance requirements for multi-slot PUCCH + +Apply the requirements defined in clause 8.1.3.7 for 2Rx. + +#### 11.1.3.2 Performance requirements for *IAB type 2-O* + +##### 11.1.3.2.1 DTX to ACK probability + +Apply the requirements defined in clause 8.1.3.1. + +##### 11.1.3.2.2 Performance requirements for PUCCH format 0 + +###### 11.1.3.2.2.1 General + +The ACK missed detection probability is the probability of not detecting an ACK when an ACK was sent. + +**Table 11.1.3.2.2.1-1: Test parameters for PUCCH format 0 testing** + +| Parameter | Value | +|--------------------------------------|----------------------------------------------| +| Cyclic prefix | Normal | +| 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 | + +The transient period as specified in TS 38.101-1 [3] clause 6.3.3.1 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. + +###### 11.1.3.2.2.2 Minimum requirements + +The ACK missed detection probability shall not exceed 1% at the SNR given in table 11.1.3.2.2.2-1 and in table 11.1.3.2.2.2-2. + +**Table 11.1.3.2.2.2-1: Minimum requirements for PUCCH format 0 and 60 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex I) | Number of OFDM symbols | Channel bandwidth / SNR (dB) | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------|------------------------------|---------| +| | | | | 50 MHz | 100 MHz | +| 1 | 2 | TDLA30-300 Low | 1 | 9.3 | 9.0 | +| | | | 2 | 4.2 | 4.0 | + +**Table 11.1.3.2.2.2-2: Minimum requirements for PUCCH format 0 and 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex I) | Number of OFDM symbols | Channel bandwidth / SNR (dB) | | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------|------------------------------|---------|---------| +| | | | | 50 MHz | 100 MHz | 200 MHz | +| 1 | 2 | TDLA30-300 Low | 1 | 9.5 | 9.2 | 9.7 | +| | | | 2 | 4.1 | 3.8 | 4.0 | + +### 11.1.3.2.3 Performance requirements for PUCCH format 1 + +#### 11.1.3.2.3.1 NACK to ACK requirements + +##### 11.1.3.2.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 11.1.3.2.3.1.1-1: Test Parameters for PUCCH format 1 testing** + +| Parameter | Test | +|------------------------------------------------|----------------------------------------| +| Cyclic prefix | Normal | +| 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-1 [3] and TS 38.101-2 [4] clause 6.3.3.1 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. + +##### 11.1.3.2.3.1.2 Minimum requirements + +The NACK to ACK probability shall not exceed 0.1% at the SNR given in Table 11.1.3.2.3.1.2-1 and Table 11.1.3.2.3.1.2-2. + +**Table 11.1.3.2.3.1.2-1: Minimum requirements for PUCCH format 1 with 60 kHz SCS** + +| Number of TX antennas | Number of Demodulation Branches | Propagation conditions and correlation matrix (Annex I) | Channel bandwidth / SNR (dB) | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------------|---------| +| | | | 50 MHz | 100 MHz | +| 1 | 2 | TDLA30-300 Low | -1.2 | -4.2 | + +**Table 11.1.3.2.3.1.2-2: Minimum requirements for PUCCH format 1 with 120 kHz SCS** + +| Number of TX antennas | Number of Demodulation Branches | Propagation conditions and correlation matrix (Annex I) | Channel bandwidth / SNR (dB) | | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------------|---------|---------| +| | | | 50 MHz | 100 MHz | 200 MHz | +| 1 | 2 | TDLA30-300 Low | -3.9 | -3.9 | -3.0 | + +## 11.1.3.2.3.2 ACK missed detection requirements + +## 11.1.3.2.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 11.1.3.2.3.1.1-1 are configured. + +The transient period as specified in TS 38.101-1 [3] clause 6.3.3.1 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. + +## 11.1.3.2.3.2.2 Minimum requirements + +The ACK missed detection probability shall not exceed 1% at the SNR given in Table 11.1.3.2.3.2.2-1 and in Table 11.1.3.2.3.2.2-2. + +**Table 11.1.3.2.3.2.2-1: Minimum requirements for PUCCH format 1 with 60 kHz SCS** + +| Number of TX antennas | Number of Demodulation Branches | Propagation conditions and correlation matrix (Annex I) | Channel bandwidth / SNR (dB) | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------------|---------| +| | | | 50 MHz | 100 MHz | +| 1 | 2 | TDLA30-300 Low | -3.9 | -4.2 | + +**Table 11.1.3.2.3.2.2-2: Minimum requirements for PUCCH format 1 with 120 kHz SCS** + +| Number of TX antennas | Number of Demodulation Branches | Propagation conditions and correlation matrix (Annex I) | Channel bandwidth / SNR (dB) | | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------------|---------|---------| +| | | | 50 MHz | 100 MHz | 200 MHz | +| 1 | 2 | TDLA30-300 Low | -4.7 | -4.6 | -4.6 | + +## 11.1.3.2.4 Performance requirements for PUCCH format 2 + +## 11.1.3.2.4.1 ACK missed detection requirements + +## 11.1.3.2.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 11.1.3.2.4.1.1-1: Test Parameters for PUCCH format 2 testing** + +| Parameter | Value | +|--------------------------------------|----------------------------------------------| +| Cyclic prefix | Normal | +| Modulation order | QSPK | +| 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$ | + +The transient period as specified in TS 38.101-1 [3] 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. + +The ACK missed detection probability shall not exceed 1% at the SNR given in table 11.1.3.2.4.1.2-1 and table 11.1.3.2.4.1.2-2 for 4 UCI bits. + +**Table 11.1.3.2.4.1.2-1: Minimum requirements for PUCCH format 2 with 60 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex I) | Channel bandwidth / SNR (dB) | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------------|---------| +| | | | 50 MHz | 100 MHz | +| 1 | 2 | TDLA30-300 Low | 6.7 | 7.2 | + +**Table 11.1.3.2.4.1.2-2: Minimum requirements for PUCCH format 2 with 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex I) | Channel bandwidth / SNR (dB) | | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------------|---------|---------| +| | | | 50 MHz | 100 MHz | 200 MHz | +| 1 | 2 | TDLA30-300 Low | 6.6 | 6.3 | 6.6 | + +#### 11.1.3.2.4.2 UCI BLER performance requirements + +##### 11.1.3.2.4.2.1 General + +The UCI block error probability (BLER) is defined as the probability of incorrectly decoded 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 [3] clause 6.3.3.1 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 performance only applies to the PUCCH format 2 with 22 UCI bits. + +**Table 11.1.3.2.4.2.1-1: Test Parameters for UCI BLER testing** + +| Parameter | Value | +|--------------------------------------|--------------------------------------------| +| Cyclic prefix | Normal | +| 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 | NID0=0 | + +##### 11.1.3.2.4.2.2 Minimum requirements + +The UCI block error probability shall not exceed 1% at the SNR given in table 11.1.3.2.4.2.2-1 and table 11.1.3.2.4.2.2-2 for 22 UCI bits. + +**Table 11.1.3.2.4.2.2-1: Minimum requirements for PUCCH format 2 with 60 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex I) | Channel bandwidth / SNR (dB) | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------------|---------| +| | | | 50 MHz | 100 MHz | +| 1 | 2 | TDLA30-300 Low | 2.6 | 1.1 | + +**Table 11.1.3.2.4.2.2-2: Minimum requirements for PUCCH format 2 with 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex I) | Channel bandwidth / SNR (dB) | | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------------|---------|---------| +| | | | 50 MHz | 100 MHz | 200 MHz | +| 1 | 2 | TDLA30-300 Low | 1.2 | 1.2 | 1.1 | + +### 11.1.3.2.5 Performance requirements for PUCCH format 3 + +#### 11.1.3.2.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 part 2. + +The transient period as specified in TS 38.101-2 [4] clause 6.3.3.1 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. + +**Table 11.1.3.2.5.1-1: Test parameters for PUCCH format 3 testing** + +| Parameter | Test 1 | Test 2 | +|--------------------------------------|----------------------------------------------|--------| +| Cyclic prefix | Normal | | +| 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 | + +#### 11.1.3.2.5.2 Minimum requirements + +The UCI block error probability shall not exceed 1% at the SNR given in Table 11.1.3.2.5.2-1 and Table 11.1.3.2.5.2-2. + +**Table 11.1.3.2.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 I) | Additional DM-RS configuration | Channel Bandwidth / SNR (dB) | | +|-------------|-----------------------|---------------------------------|---------------------------------------------------------|--------------------------------|------------------------------|---------| +| | | | | | 50 MHz | 100 MHz | +| 1 | 1 | 2 | TDLA30-300 Low | No additional DM-RS | 1.6 | 0.7 | +| | | | | Additional DM-RS | 1.3 | 0.9 | +| 2 | 1 | 2 | TDLA30-300 Low | No additional DM-RS | 3.0 | 2.4 | + +**Table 11.1.3.2.5.2-2: Required SNR for PUCCH format 3 with 120kHz SCS** + +| Test Number | Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex I) | Additional DM-RS configuration | Channel Bandwidth / SNR (dB) | | | +|-------------|-----------------------|---------------------------------|---------------------------------------------------------|--------------------------------|------------------------------|---------|---------| +| | | | | | 50 MHz | 100 MHz | 200 MHz | +| 1 | 1 | 2 | TDLA30-300 Low | No additional DM-RS | 1.4 | 0.7 | 0.7 | +| | | | | Additional DM-RS | 1.3 | 1.4 | 0.9 | +| 2 | 1 | 2 | TDLA30-300 Low | No additional DM-RS | 1.1 | 2.9 | 1.4 | + +### 11.1.3.2.6 Performance requirements for PUCCH format 4 + +#### 11.1.3.2.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 decoded 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 [3] clause 6.3.3.1 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. + +**Table 11.1.3.2.6.1-1: Test parameters for PUCCH format 4 testing** + +| Parameter | Value | +|-------------------------------------------------|----------------------------------------------| +| Cyclic prefix | Normal | +| Modulation | QPSK | +| First PRB prior to frequency hoppingstartingPRB | 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 | + +#### 11.1.3.2.6.2 Minimum requirements + +The UCI block error probability shall not exceed 1% at the SNR given in Table 11.1.3.2.6.2-1 and Table 11.1.3.2.6.2-2. + +**Table 11.1.3.2.6.2-1: Minimum requirements for PUCCH format 4 with 60 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex I) | Additional DM-RS configuration | Channel Bandwidth / SNR (dB) | | +|-----------------------|---------------------------------|---------------------------------------------------------|--------------------------------|------------------------------|---------| +| | | | | 50 MHz | 100 MHz | +| 1 | 2 | TDLA30-300 Low | No additional DM-RS | 3.0 | 2.7 | +| | | | Additional DM-RS | 3.1 | 3.5 | + +**Table 11.1.3.2.6.2-2: Minimum requirements for PUCCH format 4 with 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex I) | Additional DM-RS configuration | Channel Bandwidth / SNR (dB) | | | +|-----------------------|---------------------------------|---------------------------------------------------------|--------------------------------|------------------------------|---------|--------| +| | | | | 50 MHz | 100 MHz | 200MHz | +| 1 | 2 | TDLA30-300 Low | No additional DM-RS | 2.8 | 2.8 | 3.5 | +| | | | Additional DM-RS | 3.6 | 3.8 | 3.2 | + +### 11.1.4 Performance requirements for PRACH + +#### 11.1.4.1 Performance requirements for IAB type 1-O + +##### 11.1.4.1.1 PRACH False alarm probability + +Apply the requirements defined in clause 8.1.4.1 for 2Rx. + +##### 11.1.4.1.2 PRACH detection requirements + +Apply the requirements defined in clause 8.1.4.2 for 2Rx. + +### 11.1.4.2 Performance requirements for IAB type 2-O + +#### 11.1.4.2.1 PRACH false alarm probability + +##### 11.1.4.2.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. + +##### 11.1.4.2.1.2 Minimum requirement + +The false alarm probability shall be less than or equal to 0.1%. + +#### 11.1.4.2.2 PRACH missed detection requirements + +##### 11.1.4.2.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 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 given in Table 11.1.4.2.2.1-1. + +**Table 11.1.4.2.2.1-1: Time error tolerance for AWGN and TDLA30-300** + +| PRACH preamble | PRACH SCS (kHz) | Time error tolerance | | +|------------------------|-----------------|----------------------|------------| +| | | AWGN | TDLA30-300 | +| A1, A2, A3, B4, C0, C2 | 60 | 0.13 us | 0.28 us | +| | 120 | 0.07 us | 0.22 us | + +The test preambles for normal mode are listed in table A.2.5-2 and the test parameter *msg1-FrequencyStart* is set to 0. + +##### 11.1.4.2.2.2 Minimum requirements + +The probability of detection shall be equal to or exceed 99% for the SNR levels listed in Tables 11.1.4.2.2.2-1 to 11.1.4.2.2.2-2. + +**Table 11.1.4.2.2.2-1: PRACH missed detection requirements for Normal Mode, 60 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex I) | 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.9 | -11.9 | -13.5 | -15.8 | -6.0 | -11.8 | +| | | TDLA30-300 Low | 4000 Hz | -1.6 | -3.8 | -4.8 | -6.9 | 1.1 | -3.9 | + +**Table 11.1.4.2.2.2-2: PRACH missed detection requirements for Normal Mode, 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex I) | 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.7 | -11.5 | -13.3 | -15.8 | -5.8 | -11.4 | +| | | TDLA30-300 Low | 4000 Hz | -1.7 | -4.4 | -5.8 | -7.5 | 1.2 | -4.2 | + +## 11.2 IAB-MT performance requirements + +### 11.2.1 General + +Radiated performance requirements specify the ability of the *IAB-MT type 1-O* or the *IAB-MT 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 IAB-MT are specified for the fixed reference channels defined in annex A and the propagation conditions in annex I. The requirements only apply to those FRCs that are supported by the IAB-MT. + +The radiated performance requirements for the *IAB-MT type 1-O* and for the *IAB-MT type 2-O* are limited to two OTA *demodulation branches* as described in clause 11.2.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 1: The IAB-MT 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. + +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 energy in a slot on a RIB. + +N is the noise energy in a bandwidth corresponding to the *transmission bandwidth* over the duration of a slot on a RIB + +Radiated performance requirements are only specified for up to 2 *demodulation branches*. + +### 11.2.2 OTA demodulation branches + +If the *IAB-MT type 1-O*, or the *IAB-MT 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-MT type 1-O*, or the *IAB-MT 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). + +## 11.2.2 Demodulation performance requirements + +### 11.2.2.1 Performance requirements for IAB type 1-O + +#### 11.2.2.1.1 Performance requirements for PDSCH + +##### 11.2.2.1.1.1 General + +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 retransmissions. + +**Table: 11.2.2.1.1.1-1 Test parameters for PDSCH testing** + +| Parameter | | Value | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Cyclic prefix | | Normal | +| Default TDD UL-DL pattern (Note 1) | | 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 | +| | DM-RS position ( $l_0$ ) | 2 | +| | Additional DM-RS position | 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 | +| | 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 | +| | DM-RS sequence generation | $N_{ID}^0=0$ | +| Time domain resource assignment | PDSCH mapping type | A | +| | Start symbol | 2 | +| | Allocation length | 12 | +| Frequency domain resource assignment | RB assignment | Full applicable test bandwidth | +| PT-RS configuration | | Not configured | +| PRB bundling size | | 2 | +| VRB-to-PRB mapping type | | Not interleaved | +| PDSCH & PDSCH DMRS Precoding configuration | | Single Panel Type I, Random precoder selection updated per slot, with equal probability of each applicable $i_1, i_2$ combination, and with PRB bundling granularity | +| Note 1: The same requirements are applicable to TDD with different UL-DL patterns. | | | +| Note 2: SSB, TRS, CSI-RS, and/or other unspecified test parameters with respect to TS 38.101-4 [28] are left up to test implementation, if transmitted or needed. | | | + +#### 11.2.2.1.1.2 Minimum requirements + +The throughput shall be equal to or larger than the fraction of maximum throughput for the FRCs stated in tables 11.2.2.1.1.2-1 and 11.2.2.1.1.2-2 at the given SNR with the test parameters stated in Table 11.2.2.1.1.1-1. + +**Table 11.2.2.1.1.2-1: Minimum requirements for PDSCH with Rank 1, 40 MHz Channel Bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex I) | FRC (Annex A) | Fraction of maximum throughput (%) | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|---------------|------------------------------------|----------| +| 2 | 2 | TDLA30-10, ULA Low | M-FR1-A.3.3-1 | 70 | 25.3 | +| | | TDLA30-10, ULA Low | M-FR1-A.3.1-1 | 30 | 2.2 | + +**Table 11.2.2.1.1.2-2: Minimum requirements for PDSCH with Rank 2, 40 MHz Channel Bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex I) | FRC (Annex A) | Fraction of maximum throughput (%) | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|---------------|------------------------------------|----------| +| 2 | 2 | TDLA30-10, ULA Low | M-FR1-A.3.2-1 | 70 | 19.8 | + +### 11.2.2.1.1.2 Performance requirements for PDCCH + +#### 11.2.2.1.1.2.1 General + +The receiver characteristics of the PDCCH are determined by the probability of miss-detection of the Downlink Scheduling Grant (Pm-dsg). + +**Table: 11.2.2.1.1.2.1-1 Test parameters for PDCCH testing** + +| Parameter | Value | +|-------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Cyclic prefix | Normal | +| Default TDD UL-DL pattern (Note 1) | 7D1S2U, S=6D:4G:4U | +| DM-RS sequence generation | $N_{ID}=0$ | +| Frequency domain resource allocation for CORESET | Start from RB = 0 with contiguous RB allocation | +| CCE to REG mapping type | Interleaved | +| Interleaver size | 3 | +| REG bundle size | 6 for test with aggregation level 8
2 for others | +| Shift Index | 0 | +| Slots for PDCCH monitoring | Each slot | +| Number of PDCCH candidates for the tested aggregation level | 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 | + +Note 1: The same requirements are applicable to TDD with different UL-DL patterns. +Note 2: SSB, TRS, CSI-RS, and/or other unspecified test parameters with respect to TS 38.101-4 [28] are left up to test implementation, if transmitted or needed. + +#### 11.2.2.1.1.2.2 Minimum requirements + +The Pm-dsg shall be equal to or smaller than 1%, for the cases stated in Table 11.2.2.1.1.2.2-1 at the given SNR with the test parameters stated in Table 11.2.2.1.1.2.1-1. + +**Table 11.2.2.1.1.2.2-1: Minimum requirements for PDCCH, 40 MHz Channel Bandwidth, 30 kHz SCS** + +| Antenna configuration | CORESET RB | CORESET duration | Aggregation level | FRC (Annex A) | Propagation conditions and correlation matrix (Annex I) | Pm-dsg (%) | SNR (dB) | +|-----------------------|------------|------------------|-------------------|---------------|---------------------------------------------------------|------------|----------| +| 1x2 | 102 | 1 | 2 | M-FR1-A.3.4-1 | TDLA30-10, Low | 1 | 7.0 | +| 1x2 | 102 | 1 | 4 | M-FR1-A.3.4-1 | TDLA30-10, Low | 1 | 4.9 | +| 2x2 | 90 | 1 | 8 | M-FR1-A.3.4-1 | TDLA30-10, Low | 1 | -0.7 | + +### 11.2.2.2 Performance requirements for IAB type 2-O + +#### 11.2.2.2.1 Performance requirements for PDSCH + +##### 11.2.2.2.1.1 General + +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 retransmissions. + +**Table: 11.2.2.2.1.1-1 Test parameters for PDSCH testing** + +| Parameter | Value | +|--------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Cyclic prefix | Normal | +| Default TDD UL-DL pattern (Note 1) | 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 | +| | DM-RS position ( $l_0$ ) 2 | +| | Additional DM-RS position pos1 | +| | Number of DM-RS CDM group(s) without data 1 | +| | DM-RS port(s) {1000} for Rank 1 tests
{1000-1001} for Rank 2 tests | +| | DM-RS sequence generation $N_{ID}^0=0$ | +| Time domain resource assignment | PDSCH mapping type A | +| | Start symbol 1 | +| | Allocation length 13 | +| Frequency domain resource assignment | RB assignment Full applicable test bandwidth | +| PT-RS configuration | Frequency density ( $K_{PT-RS}$ ) 2 | +| | Time density ( $L_{PT-RS}$ ) 1 | +| PRB bundling size | 2 | +| VRB-to-PRB mapping type | Not interleaved | +| PDSCH & PDSCH DMRS Precoding configuration | Single Panel Type I, Random precoder selection updated per slot, with equal probability of each applicable $i_1, i_2$ combination, and with PRB bundling granularity | + +Note 1: The same requirements are applicable to TDD with different UL-DL patterns. +Note 2: SSB, TRS, CSI-RS, and/or other unspecified test parameters with respect to TS 38.101-4 [28] are left up to test implementation, if transmitted or needed. + +#### 11.2.2.2.1.2 Minimum requirements + +The throughput shall be equal to or larger than the fraction of maximum throughput for the FRCs stated in table 11.2.2.2.1.2-1, 11.2.2.2.1.2-2 and 11.2.2.2.1.2-3 at the given SNR with the test parameters stated in Table 11.2.2.2.1.1-1. + +**Table 11.2.2.2.1.2-1: Minimum requirements for PDSCH with Rank 1, 100 MHz Channel Bandwidth, 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex I) | FRC (Annex A) | Fraction of maximum throughput (%) | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|---------------|------------------------------------|----------| +| 2 | 2 | TDLA30-75, ULA Low | M-FR2-A.3.1-2 | 30 | 2.3 | +| 2 | 2 | TDLA30-75, ULA Low | M-FR2-A.3.2-1 | 70 | 11.7 | + +**Table 11.2.2.2.1.2-2: Minimum requirements for PDSCH with Rank 2, 50 MHz Channel Bandwidth, 60 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex I) | FRC (Annex A) | Fraction of maximum throughput (%) | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|---------------|------------------------------------|----------| +| 2 | 2 | TDLA30-75, ULA Low | M-FR2-A.3.1-1 | 70 | 14.3 | + +**Table 11.2.2.2.1.2-3: Minimum requirements for PDSCH with Rank 2, 100 MHz Channel Bandwidth, 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex I) | FRC (Annex A) | Fraction of maximum throughput (%) | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|---------------|------------------------------------|----------| +| 2 | 2 | TDLA30-75, ULA Low | M-FR2-A.3.1-3 | 70 | 14.2 | +| 2 | 2 | TDLA30-75, ULA Low | M-FR2-A.3.2-2 | 70 | 18.6 | + +## 11.2.2.2.2 Performance requirements for PDCCH + +### 11.2.2.2.2.1 General + +The receiver characteristics of the PDCCH are determined by the probability of miss-detection of the Downlink Scheduling Grant (Pm-dsg). + +**Table: 11.2.2.2.2.1-1 Test parameters for testing PDCCH** + +| Parameter | Value | +|-------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Cyclic prefix | Normal | +| Default TDD UL-DL pattern (Note 1) | 3D1S1U, S=10D:2G:2U | +| DM-RS sequence generation | NID=0 | +| Frequency domain resource allocation for CORESET | Start from RB = 0 with contiguous RB allocation | +| CCE to REG mapping type | Interleaved | +| Interleaver size | 2 for test with Aggregation level 4
3 for others | +| REG bundle size | 6 for test with Aggregation level 4
2 for others | +| Shift Index | 0 | +| Slots for PDCCH monitoring | Each slot | +| Number of PDCCH candidates for the tested aggregation level | 1 | +| PDCCH Precoding configuration | Single Panel Type I, Random precoder selection updated per slot, with equal probability of each applicable i1, i2 combination with REG bundling granularity for number of Tx larger than 1 | + +Note 1: The same requirements are applicable to TDD with different UL-DL patterns. +Note 2: SSB, TRS, CSI-RS, and/or other unspecified test parameters with respect to TS 38.101-4 [28] are left up to test implementation, if transmitted or needed + +### 11.2.2.2.2.2 Minimum requirements + +The Pm-dsg shall be equal to or smaller than 1%, for the cases stated in Table 11.2.2.2.2.2-1 at the given SNR with the test parameters stated in Table 11.2.2.2.2.1-1. + +**Table 11.2.2.2.2.2-1: Minimum requirements for PDCCH, 100 MHz Channel Bandwidth, 120 kHz SCS** + +| Antenna configuration | CORESET RB | CORESET duration | Aggregation level | FRC (Annex A) | Propagation conditions and correlation matrix (Annex I) | Pm-dsg (%) | SNR (dB) | +|-----------------------|------------|------------------|-------------------|---------------|---------------------------------------------------------|------------|----------| +| 1x2 | 60 | 1 | 2 | M-FR2-A.3.4-1 | TDLA30-75, ULA Low | 1 | 6.4 | +| 1x2 | 60 | 1 | 4 | M-FR2-A.3.4-2 | TDLA30-75, ULA Low | 1 | 2.9 | +| 2x2 | 60 | 1 | 8 | M-FR2-A.3.4-3 | TDLA30-75, ULA Low | 1 | 0.1 | + +## 11.2.3 CSI reporting requirements + +### 11.2.3.1 Performance requirements for IAB type 1-O + +#### 11.2.3.1.1 Reporting of Channel Quality Indicator (CQI) + +Apply the requirements defined in clause 8.2.3.2 for 2Rx. + +#### 11.2.3.1.2 Reporting of Precoding Matrix Indicator (PMI) + +Apply the requirements defined in clause 8.2.3.3 for 2Rx. + +#### 11.2.3.1.3 Reporting of Rank Indicator (RI) + +Apply the requirements defined in clause 8.2.3.4 for 2Rx. + +### 11.2.3.2 Performance requirements for IAB type 2-O + +#### 11.2.3.2.1 General + +This clause includes radiated requirements for the reporting of channel state information (CSI). + +##### 11.2.3.2.1.1 Void + +Void + +##### 11.2.3.2.1.2 Common test parameters + +Parameters specified in Table 11.2.3.2.1.2-1 are applied for all test cases in this clause unless otherwise stated. + +**Table 11.2.3.2.1.2-1: Test parameters for CSI test cases** + +| Parameter | Unit | Value | +|--------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| PDSCH transmission scheme | | Transmission scheme 1 | +| Duplex Mode | | TDD | +| PTRS epre-Ratio | | 0 | +| Actual carrier configuration | Offset between Point A and the lowest usable subcarrier on this carrier (Note 3) | RBs 0 | +| | Subcarrier spacing | kHz 120 | +| DL BWP configuration #1 | Cyclic prefix | Normal | +| | RB offset | RBs 0 | +| | Number of contiguous PRB | PRBs Maximum transmission bandwidth configuration as specified in clause 5.3.2 of TS 38.101-2 [4] for tested channel bandwidth and subcarrier spacing | +| | Active DL BWP index | 1 | +| PDSCH configuration | Mapping type | Type A | +| | k0 | 0 | +| | Starting symbol (S) | 2 | +| | Length (L) | 12 | +| | PDSCH aggregation factor | 1 | +| | PRB bundling type | Static | +| | PRB bundling size | 2 | +| | Resource allocation type | Type 0 | +| | RBG size | Config2 | +| | VRB-to-PRB mapping type | Non-interleaved | +| PDSCH DMRS configuration | VRB-to-PRB mapping interleaver bundle size | N/A | +| | DMRS Type | Type 1 | +| | Number of additional DMRS | 1 | +| | DMRS ports indexes | {1000} for Rank1
{1000,1001} for Rank2 | +| | Maximum number of OFDM symbols for DL front loaded DMRS | 1 | +| PTRS configuration | Number of PDSCH DMRS CDM group(s) without data | 2 | +| | Frequency density ( KPT-RS ) | 2 | +| | Time density ( LPT-RS ) | 1 | +| NZP CSI-RS for CSI acquisition | Resource Element Offset | 2 | +| Redundancy version coding sequence | Frequency Occupation | Start PRB 0
Number of PRB = BWP size | +| Physical signals, channels mapping and precoding | | {0,2,3,1} | +| Note 1: | PDSCH is scheduled only on full DL slots without CSI-RS resource and TRS allocated. | | +| Note 2: | Point A coincides with minimum guard band as specified in Table 5.3.3-1 from TS 38.101-2 [4] for tested channel bandwidth and subcarrier spacing. | | + +## 11.2.3.2.2 Reporting of Channel Quality Indicator (CQI) + +### 11.2.3.2.2.1 General + +The reporting accuracy of the channel quality indicator (CQI) under frequency non-selective conditions is determined by the reporting variance and the BLER performance using the transport format indicated by the reported CQI median. + +The purpose is to verify that the reported CQI values are in accordance with the CQI definition given in TS 38.214 [11]. 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. + +**Table 11.2.3.2.2.1-1: Test parameters** + +| Parameter | Unit | Test 1 | Test 2 | | | +|-------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|---------|--|--| +| Bandwidth | MHz | 100 | | | | +| Subcarrier spacing | kHz | 120 | | | | +| Duplex Mode | | TDD | | | | +| Default TDD UL-DL pattern (Note 1) | | 3D1S1U | | | | +| Special Slot Configuration | | 10D+2G+2U | | | | +| SNR BB | dB | 8 | 9 14 15 | | | +| Propagation channel | | AWGN | | | | +| Antenna configuration | | 2×2 with static channel specified in Annex I.1 | | | | +| Beamforming Model | | As specified in Annex I.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 (ρ) | 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 | | | | +| cqi-FormatIndicator | | Wideband | | | | +| pmi-FormatIndicator | | Wideband | | | | +| Sub-band Size | RB | 8 | | | | +| csi-ReportingBand | | 11111111 | | | | +| CSI-Report periodicity and offset | slot | 5/4 | | | | +| 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 | 1.75 | | | | +| Maximum number of HARQ transmission | | 1 | | | | +| Measurement channel | | M-FR2-A.3.5-2 | | | | +| 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 [28] 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). | | | | | + +#### 11.2.3.2.2.2 Minimum requirements + +For the parameters specified in Table 11.2.3.2.1.1-1, and using the downlink physical channels specified in Annex A, the minimum requirements are specified by the following: + +- The reported CQI value according to the reference channel shall be in the range of ±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. + +### 11.2.3.2.3 Reporting of Precoding Matrix Indicator (PMI) + +#### 11.2.3.2.3.1 General + +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 reports 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 and applied to the PDSCH. A fixed transport format (FRC) is configured for all requirements. + +The requirements for transmission mode 1 with 2TX and higher layer parameter *codebookType* set to 'typeI-SinglePanel' are specified in terms of the ratio + +$$\gamma = \frac{t_{ue}}{t_{rnd}}$$ + +In the definition of $\gamma$ , for 2TX PMI requirements, $t_{ue}$ is 90 % of the maximum throughput obtained at $SNR_{ue}$ using the precoders configured according to the IAB-MT reports, and $t_{rnd}$ is the throughput measured at $SNR_{ue}$ with random precoding. + +**Table 11.2.3.2.3.1-1: Test parameters** + +| Parameter | Unit | Test 1 | +|-------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------| +| Bandwidth | MHz | 100 | +| Subcarrier spacing | kHz | 120 | +| Default TDD UL-DL pattern (Note 1) | | 3D1S1U | +| Special Slot Configuration | | 10D+2G+2U | +| Propagation channel | | TDLA30-35 | +| Antenna configuration | | 2 x 2 ULA Low | +| Beamforming Model | | As specified in Annex I.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 (ρ) | 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, l_1$ ) | (13,-) | +| | CSI-RS interval and offset | slot 5/1 | +| ReportConfigType | | Periodic | +| CQI-table | | Table 1 | +| reportQuantity | | cri-RI-PMI-CQI | +| cqi-FormatIndicator | | Wideband | +| pmi-FormatIndicator | | Wideband | +| Sub-band Size | RB | 8 | +| csi-ReportingBand | | 111111111 | +| CSI-Report interval and offset | slot | 5/4 | +| Codebook configuration | Codebook Type | typeI-SinglePanel | +| | Codebook Mode | 1 | +| | (CodebookConfig-N1, CodebookConfig-N2) | N/A | +| | CodebookSubsetRestriction | 001111 | +| | RI Restriction | N/A | +| CQI/RI/PMI delay | ms | 1.75 | +| Maximum number of HARQ transmission | | 4 | +| Measurement channel | | M-FR2-A.3.5-3 | +| Note 1: | The same requirements are applicable for TDD with different UL-DL pattern. | | +| Note 2: | For random precoder selection, the precoder shall be updated in each slot (0.125 ms granularity). | | +| 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). | | +| Note 4: | Randomization of the principle beam direction shall be used as specified in Annex I.2.3.2.3. | | +| Note 5: | SSB, TRS, CSI-RS and/or other unspecified test parameters with respect to TS 38.101-4 [28] are left up to test implementation, if transmitted or needed | | + +#### 11.2.3.2.3.2 Minimum requirements + +For the parameters specified in Table 11.2.3.2.3.1-1, and using the downlink physical channels specified in Annex A, the minimum requirements are specified in Table 11.2.3.2.3.2-1. + +**Table 11.2.3.2.3.2-1: Minimum requirement** + +| Parameter | Test 1 | +|-----------|--------| +| $\gamma'$ | 1.05 | + +#### 11.2.3.2.4 Reporting of Rank Indicator (RI) + +##### 11.2.3.2.4.1 General + +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. + +The minimum performance requirement in Table 11.2.3.2.4.2-1 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$ ; + +**Table 11.2.3.2.4.1-1: Test parameters** + +| Parameter | Unit | Test 1 | Test 2 | Test 3 | +|-------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------|----------------------------------------------------|----------------------------------------------------| +| Bandwidth | MHz | 100 | 100 | 100 | +| Subcarrier spacing | kHz | 120 | 120 | 120 | +| Duplex Mode | | TDD | TDD | TDD | +| Default TDD UL-DL pattern (Note 1) | | 3D1S1U | 3D1S1U | 3D1S1U | +| Special Slot Configuration | | 10D+2G+2U | 10D+2G+2U | 10D+2G+2U | +| SNR | dB | 0 | 16 | 16 | +| Propagation channel | | TDLA30-35 | TDLA30-35 | TDLA30-35 | +| Antenna configuration | | ULA Low 2x2 | ULA Low 2x2 | XP High 2x2 | +| Beamforming Model | | As defined in Annex I.3.1 | As defined in Annex I.3.1 | As defined in Annex I.3.1 | +| NZP CSI-RS for CSI acquisition | CSI-RS resource Type | Periodic | Periodic | Periodic | +| | Number of CSI-RS ports ( $X$ ) | 2 | 2 | 2 | +| | CDM Type | FD-CDM2 | FD-CDM2 | FD-CDM2 | +| | Density ( $\rho$ ) | 1 | 1 | 1 | +| | First subcarrier index in the PRB used for CSI-RS ( $k_0, k_1$ ) | Row 3 (6,-) | Row 3 (6,-) | Row 3 (6,-) | +| | First OFDM symbol in the PRB used for CSI-RS ( $l_0, l_1$ ) | (13,-) | (13,-) | (13,-) | +| | NZP CSI-RS-timeConfig interval and offset | slot | 5/1 | 5/1 | +| ReportConfigType | | Periodic | Periodic | Periodic | +| CQI-table | | Table 1 | Table 1 | Table 1 | +| reportQuantity | | cri-RI-PMI-CQI | cri-RI-PMI-CQI | cri-RI-PMI-CQI | +| cqi-FormatIndicator | | Wideband | Wideband | Wideband | +| pmi-FormatIndicator | | Wideband | Wideband | Wideband | +| Sub-band Size | RB | 8 | 8 | 8 | +| csi-ReportingBand | | 111111111 | 111111111 | 111111111 | +| CSI-Report interval and offset | slot | 5/4 | 5/4 | 5/4 | +| Codebook configuration | Codebook Type | typeI-SinglePanel | typeI-SinglePanel | typeI-SinglePanel | +| | Codebook Mode | 1 | 1 | 1 | +| | (CodebookConfig-N1, CodebookConfig-N2) | N/A | N/A | N/A | +| | CodebookSubsetRestriction | 010000 for fixed rank 2, 010011 for following rank | 000011 for fixed rank 1, 010011 for following rank | 000011 for fixed rank 1, 010011 for following rank | +| | RI Restriction | N/A | N/A | N/A | +| CQI/RI/PMI delay | ms | 1.75 | 1.75 | 1.75 | +| Maximum number of HARQ transmission | | 1 | 1 | 1 | +| RI Configuration | | Fixed RI = 2 and follow RI | Fixed RI = 1 and follow RI | 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 [28] are left up to test implementation, if transmitted or needed. | | | | +| Note 3: | Measurements channels are specified in Table A.3.5-2. M-FR2-A.3.5-1 is used for Rank 1 case. M-FR2-A.3.5-2 is used for Rank 2 case. | | | | +| Note 4: | 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). | | | | + +#### 11.2.3.2.4.2 Minimum requirements + +For the parameters specified in Table 11.2.3.2.4.1-1, and using the downlink physical channels specified in Annex A, the minimum requirements are specified in Table 11.2.3.2.4.2-1. + +**Table 11.2.3.2.4.2-1: Minimum requirement** + +| | Test 1 | Test 2 | Test 3 | +|-------|--------|--------|--------| +| $J_1$ | N/A | 1.05 | 1.05 | +| $J_2$ | 1.0 | N/A | N/A | + +## 12 Radio Resource Management requirements + +### 12.1 RRC\_CONNECTED state mobility for IAB-MTs + +#### 12.1.1 RRC Connection Mobility Control + +##### 12.1.1.1 SA: RRC Re-establishment + +###### 12.1.1.1.1 Introduction + +This clause contains requirements on the IAB-MT regarding RRC connection re-establishment procedure. RRC connection re-establishment is initiated when an IAB-MT in RRC\_CONNECTED state loses RRC connection due to any of failure cases, including radio link failure, handover failure, and RRC connection reconfiguration failure. The RRC connection re-establishment procedure is specified in clause 5.3.7 of TS 38.331 [15]. + +The requirements in this clause are applicable for RRC connection re-establishment to NR cell. + +###### 12.1.1.1.2 Requirements + +In RRC\_CONNECTED state the IAB-MT shall be capable of sending *RRCREestablishmentRequest* message within $T_{re-establish\_delay}$ seconds from the moment it detects a loss in RRC connection. The total RRC connection delay ( $T_{re-establish\_delay}$ ) shall be less than: + +$T_{UL\_grant}$ : It is the time required to acquire and process uplink grant from the target PCell. The uplink grant is required to transmit *RRCREestablishmentRequest* message. + +The IAB-MT re-establishment delay ( $T_{IAB-MT\_re-establish\_delay}$ ) is specified in clause 12.1.1.1.2.1. + +###### 12.1.1.1.2.1 IAB MT Re-establishment delay requirement + +The IAB-MT re-establishment delay ( $T_{IAB-MT\_re-establish\_delay}$ ) is the time between the moments when any of the conditions requiring RRC re-establishment as defined in clause 5.3.7 in TS 38.331 [15] is detected by the IAB-MT and when the IAB-MT sends PRACH to the target PCell. The IAB-MT re-establishment delay ( $T_{IAB-MT\_re-establish\_delay}$ ) requirement shall be less than: + +The intra-frequency target NR cell shall be considered detectable if each relevant SSB can satisfy that: + +- the conditions of SSB\_RP and SSB Ês/Iot according to Annex H.1.1.1 for a corresponding IAB-MT class and IAB type are fulfilled. + +The inter-frequency target NR cell shall be considered detectable when for each relevant SSB: + +- the conditions of SSB\_RP and SSB Ês/Iot according to Annex H.1.1.2 for a corresponding IAB-MT class and IAB type are fulfilled. + +$T_{identify\_intra\_NR}$ : It is the time to identify the target intra-frequency NR cell and it depends on whether the target NR cell is known cell or unknown cell and on the frequency range (FR) of the target NR cell. If the IAB-MT is not configured with intra-frequency NR carrier for RRC re-establishment then $T_{identify\_intra\_NR}=0$ ; otherwise $T_{identify\_intra\_NR}$ shall not exceed the values defined in Table 12.1.1.1.2.1-1. + +$T_{\text{identify\_inter\_NR},i}$ : It is the time to identify the target inter-frequency NR cell on inter-frequency carrier $i$ configured for RRC re-establishment and it depends on whether the target NR cell is known cell or unknown cell and on the frequency range (FR) of the target NR cell. $T_{\text{identify\_inter\_NR},i}$ shall not exceed the values defined in Table 12.1.1.2.1-2. + +$T_{\text{SMTC}}$ : It is the periodicity of the SMTC occasion configured for the intra-frequency carrier. If the IAB-MT has been provided with higher layer signaling of *smtc2* [15] and is not capable of 4 SMTC configurations per frequency [15], then $T_{\text{SMTC}}$ follows *smtc1* or *smtc2* according to the physical cell ID of the target cell. If the IAB-MT has been provided with higher layer signaling of *smtcj*, where $1 \leq j \leq 4$ [15] and is also capable of 4 SMTC configurations per frequency [15], then $T_{\text{SMTC}}$ follows *smtcj* according to the physical cell ID of the target cell. + +$T_{\text{SMTC},i}$ : It is the periodicity of the SMTC occasion configured for the inter-frequency carrier $i$ . If the IAB-MT is not capable of 4 SMTC configurations per frequency [15], then the requirements shall apply provided that the IAB-MT is configured with only one SMTC configuration for each inter-frequency carrier $i$ according to the physical cell ID of the target cell. If the IAB-MT has been provided with higher layer signaling of *smtcj*, where $1 \leq j \leq 4$ [15] and is also capable of 4 SMTC configurations per frequency [15], then $T_{\text{SMTC}}$ follows *smtcj* configured for the inter-frequency carrier $i$ according to the physical cell ID of the target cell. If the IAB-MT is not provided with SMTC configuration then the IAB-MT may assume that the target SSB periodicity is no larger than 160 ms. + +$T_{\text{SI-NR}}$ : It is the time required for receiving all the relevant system information according to the reception procedure and the RRC procedure delay of system information blocks defined in TS 38.331 [15] for the target NR cell. + +$T_{\text{PRACH}}$ : It is the delay uncertainty in acquiring the first available PRACH occasion in the target NR cell. $T_{\text{PRACH}}$ can be up to the summation of SSB to PRACH occasion association period and 10 ms. SSB to PRACH occasion associated period is defined in clause 14 of TS 38.213 [10]. + +$N_{\text{freq}}$ : It is the total number of NR frequencies to be monitored for RRC re-establishment; $N_{\text{freq}} = 1$ if the target intra-frequency NR cell is known, else $N_{\text{freq}} = 2$ and $T_{\text{identify\_intra\_NR}} = 0$ if the target inter-frequency NR cell is known. + +There is no requirement if the target cell does not contain the IAB-MT context or if the SSB transmission periodicity is larger than 160 ms. + +In the requirement defined in the below tables, the target FR1 cell is known if it has been meeting the relevant cell identification requirement during the last 5 seconds otherwise it is unknown. + +**Table 12.1.1.2.1-1: Time to identify target NR cell for RRC connection re-establishment to NR intra-frequency cell** + +| Serving cell SSB $\bar{E}_s/\text{lot}$ (dB) | Frequency range (FR) of target NR cell | $T_{\text{identify\_intra\_NR}}$ [ms] | | +|----------------------------------------------|----------------------------------------|--------------------------------------------|---------------------------------------------| +| | | Known NR cell | Unknown NR cell | +| $\geq -8$ | FR1 | MAX (1600 ms, $5 \times T_{\text{SMTC}}$ ) | MAX (6400 ms, $10 \times T_{\text{SMTC}}$ ) | +| $\geq -8$ | FR2-1 | N/A | MAX (8000 ms, $80 \times T_{\text{SMTC}}$ ) | +| $< -8$ | FR1 | N/A | 6400 Note1 | +| $< -8$ | FR2-1 | N/A | 28160 Note1 | + +Note 1: The IAB-MT is not required to successfully identify a cell on any NR frequency layer when $T_{\text{SMTC}} > 160$ ms and serving cell SSB $\bar{E}_s/\text{lot} < -8$ dB. + +**Table 12.1.1.2.1-2: Time to identify target NR cell for RRC connection re-establishment to NR inter-frequency cell** + +| Serving cell SSB $\bar{E}_s/\text{lot}$ (dB) | Frequency range (FR) of target NR cell | $T_{\text{identify\_inter\_NR},i}$ [ms] | | +|----------------------------------------------|----------------------------------------|----------------------------------------------|------------------------------------------------| +| | | Known NR cell | Unknown NR cell | +| $\geq -8$ | FR1 | MAX (1600 ms, $6 \times T_{\text{SMTC},i}$ ) | MAX (6400 ms, $13 \times T_{\text{SMTC},i}$ ) | +| $\geq -8$ | FR2-1 | N/A | MAX (8000 ms, $104 \times T_{\text{SMTC},i}$ ) | +| $< -8$ | FR1 | N/A | 6400 Note1 | +| $< -8$ | FR2-1 | N/A | 32000 Note1 | + +Note 1: The IAB-MT is not required to successfully identify a cell on any NR frequency layer when $T_{\text{SMTC},i} > 160$ ms and serving cell SSB $\bar{E}_s/\text{lot} < -8$ dB. + +## 12.1.1.1B SA: RRC Re-establishment for mIAB-MT + +### 12.1.1.1B.1 Introduction + +This clause contains requirements on the mobile IAB-MT (mIAB-MT) regarding RRC connection re-establishment procedure. RRC connection re-establishment is initiated when a mIAB-MT in RRC\_CONNECTED state loses RRC connection due to any of failure cases, including radio link failure, handover failure, and RRC connection reconfiguration failure. The RRC connection re-establishment procedure is specified in clause 5.3.7 of TS 38.331 [15]. + +The requirements in this clause are applicable for RRC connection re-establishment to NR cell. + +### 12.1.1.1B.2 Requirements + +In RRC\_CONNECTED state the mIAB-MT shall be capable of sending *RRCReestablishmentRequest* message within $T_{\text{re-establish\_delay}}$ seconds from the moment it detects a loss in RRC connection. The total RRC connection delay ( $T_{\text{re-establish\_delay}}$ ) shall be less than: + +$T_{\text{UL\_grant}}$ : It is the time required to acquire and process uplink grant from the target PCell. The uplink grant is required to transmit *RRCReestablishmentRequest* message. + +The mIAB-MT re-establishment delay ( $T_{\text{mIAB-MT\_re-establish\_delay}}$ ) is specified in clause 12.1.1.1B.2.1. + +#### 12.1.1.1B.2.1 mIAB-MT Re-establishment delay requirement + +The mIAB-MT re-establishment delay ( $T_{\text{mIAB-MT\_re-establish\_delay}}$ ) is the time between the moments when any of the conditions requiring RRC re-establishment as defined in clause 5.3.7 in TS 38.331 [15] is detected by the mIAB-MT and when the mIAB-MT sends PRACH to the target PCell. The mIAB-MT re-establishment delay ( $T_{\text{mIAB-MT\_re-establish\_delay}}$ ) requirement shall be less than: + +The intra-frequency target NR cell shall be considered detectable if each relevant SSB can satisfy that: + +- the conditions of SSB\_RP and SSB Ês/Iot according to Annex TBD for the mIAB-MT class and IAB type are fulfilled. + +$T_{\text{identify\_intra\_NR}}$ : It is the time to identify the target intra-frequency NR cell and it depends on whether the target NR cell is known cell or unknown cell and on the FR of the target NR cell. $T_{\text{identify\_intra\_NR}}$ shall not exceed the values defined in Table 12.1.1.1B.2.1-1. + +$T_{\text{SMTC}}$ : It is the periodicity of the SMTC occasion configured for the intra-frequency carrier. If the IAB-MT has been provided with higher layer signaling of *smtc2* [15] and is not capable of 4 SMTC configurations per frequency [15], then $T_{\text{SMTC}}$ follows *smtc1* or *smtc2* according to the physical cell ID of the target cell. If the IAB-MT has been provided with higher layer signaling of *smtcj*, where $1 \leq j \leq 4$ [15] and is also capable of 4 SMTC configurations per frequency [15], then $T_{\text{SMTC}}$ follows *smtcj* according to the physical cell ID of the target cell. + +$T_{\text{SI-NR}}$ : It is the time required for receiving all the relevant system information according to the reception procedure and the RRC procedure delay of system information blocks defined in TS 38.331 [15] for the target NR cell. + +$T_{\text{PRACH}}$ : It is the delay uncertainty in acquiring the first available PRACH occasion in the target NR cell. $T_{\text{PRACH}}$ can be up to the summation of SSB to PRACH occasion association period and 10 ms. SSB to PRACH occasion associated period is defined in the table 8.1-1 of TS 38.213 [10]. + +There is no requirement if the target cell does not contain the mIAB-MT context. + +In the requirement defined in the below tables, the target FR1 cell is known if it has been meeting the relevant cell identification requirement during the last 5 seconds otherwise it is unknown. + +**Table 12.1.1.1B.2-1: Time to identify target NR cell for RRC connection re-establishment to NR intra-frequency cell** + +| Serving cell
SSB Ês/lot (dB) | FR of target NR
cell | $T_{\text{identify\_intra\_NR}}$ [ms] | | +|---------------------------------|-------------------------|-------------------------------------------|---------------------------------------------| +| | | Known NR cell | Unknown NR cell | +| $\geq -8$ | FR1 | MAX (200 ms, $5 \times T_{\text{SMTC}}$ ) | MAX (800 ms, $10 \times T_{\text{SMTC}}$ ) | +| $\geq -8$ | FR2-1 | N/A | MAX (1000 ms, $80 \times T_{\text{SMTC}}$ ) | +| $< -8$ | FR1 | N/A | 800 Note1 | +| $< -8$ | FR2-1 | N/A | 3520 Note1 | + +Note 1: The mIAB-MT is not required to successfully identify a cell on any NR frequency layer when $T_{\text{SMTC}} > 20$ ms and serving cell SSB Ês/lot $< -8$ dB. + +### 12.1.1.2 Random access + +The requirements in clause 6.2.2 in TS 38.133 [6] apply for IAB-MT. + +### 12.1.1.3 SA: RRC Connection Release with Redirection + +#### 12.1.1.3.1 Introduction + +This clause contains requirements on the IAB-MT regarding RRC connection release with redirection procedure. RRC connection release with redirection is initiated by the *RRRelease* message with redirection to NR from NR specified in TS 38.331 [15]. The RRC connection release with redirection procedure is specified in clause 5.3.8 of TS 38.331 [15]. + +#### 12.1.1.3.2 Requirements + +##### 12.1.1.3.2.1 RRC connection release with redirection to NR + +The IAB-MT shall be capable of performing the RRC connection release with redirection to the target NR cell within $T_{\text{connection\_release\_redirect\_NR}}$ . + +The time delay ( $T_{\text{connection\_release\_redirect\_NR}}$ ) is the time between the end of the last slot containing the RRC command, “*RRRelease*” (TS 38.331 [15]) on the NR PDSCH and the time the IAB-MT starts to send random access to the target NR cell. The time delay ( $T_{\text{connection\_release\_redirect\_NR}}$ ) shall be less than: + +$$T_{\text{connection\_release\_redirect\_NR}} = T_{\text{RR\_procedure\_delay}} + T_{\text{identify\_NR}} + T_{\text{SI\_NR}} + T_{\text{RACH}}$$ + +The target NR cell shall be considered detectable when for each relevant SSB, the side conditions should be met that, + +- the conditions of SSB\_RP and SSB Ês/lot according to Annex H.1.1.3 for a corresponding IAB-MT class and IAB type are fulfilled. + +$T_{\text{RR\_procedure\_delay}}$ : It is the RRC procedure delay for processing the received message “*RRRelease*” as defined in clause 6.2.2 of TS 38.331 [15]. + +$T_{\text{identify\_NR}}$ : It is the time to identify the target NR cell and depends on the frequency range (FR) of the target NR cell. It is defined in Table 12.1.1.3.2-1. Note that $T_{\text{identify\_NR}} = T_{\text{PSS/SSS-synch}} + T_{\text{meas}}$ , in which $T_{\text{PSS/SSS-synch}}$ is the cell search time and $T_{\text{meas}}$ is the measurement time due to cell selection criteria evaluation. + +$T_{\text{SI\_NR}}$ : It is the time required for acquiring all the relevant system information of the target NR cell. This time depends upon whether the IAB-MT is provided with the relevant system information of the target NR cell or not by the old NR cell before the RRC connection is released. + +$T_{\text{RACH}}$ : It is the delay uncertainty in acquiring the first available PRACH occasion in the target NR cell. $T_{\text{RACH}}$ can be up to the summation of SSB to PRACH occasion association period and 10 ms. SSB to PRACH occasion associated period is defined in clause 14 of TS 38.213 [10]. + +$T_s$ is the SMTC periodicity of the target NR cell if the IAB-MT has been provided with an SMTC configuration for the target cell in the redirection command, otherwise $T_s$ is the SMTC periodicity configured in the *measObjectNR* having the same SSB frequency and subcarrier spacing configured for the RRC connection release with redirection. If the IAB-MT is not capable of 4 SMTC configurations per frequency [15], then the requirements shall apply provided that the IAB-MT is configured with only one SMTC configuration on carrier configured for RRC connection release with redirection. If the IAB-MT has been provided with higher layer signaling of *smtcj*, where $1 \leq j \leq 4$ [15] and is also capable of 4 SMTC configurations per frequency [15], then $T_{\text{smtc}}$ follows *smtcj* according to the physical cell ID of the + +target cell. If the IAB-MT is not provided with SMTC configuration or measurement object for the frequency which is also configured for the RRC connection release with redirection then the requirement in this clause is applied with $T_{rs} = 160$ ms if the SSB transmission periodicity is not larger than 160 ms. + +- There is no requirement if the SSB transmission periodicity is larger than 160ms. + +**Table 12.1.1.3.2-1: Time to identify target NR cell for RRC connection release with redirection to NR** + +| Frequency range (FR) of target NR cell | $T_{identify-NR}$ | +|----------------------------------------|---------------------------------------------| +| FR1 | MAX (5440 ms, $11 \times T_{rs}$ ) | +| FR2-1 | MAX (7040 ms, $8 \times 11 \times T_{rs}$ ) | + +## 12.1.2 Void + +### 12.1.2B Handover for mIAB-MT + +#### 12.1.2B.1 Introduction + +The purpose of NR handover is to change the NR PCell to another NR cell. The requirements in this clause are applicable to the mIAB-MT in SA NR. + +#### 12.1.2B.2 NR FR1 - NR FR1 Intra-frequency Handover + +The requirements in this clause are applicable to intra-frequency handover of the mIAB-MT from NR FR1 cell to NR FR1 cell. + +##### 12.1.2B.2.1 Handover delay + +When the mobile IAB-MT (mIAB-MT) receives a RRC message implying handover the mIAB-MT shall be ready to start the transmission of the new uplink PRACH channel within $D_{handover}$ msec from the end of the last TTI containing the RRC command. + +Where: + +$D_{handover}$ equals the applicable RRC procedure delay defined in clause 12 in TS 38.331 [15] plus the interruption time stated in clause 12.1.2B.2.2. + +##### 12.1.2B.2.2 Interruption time + +The interruption time is the time between end of the last TTI containing the RRC command on the old PDSCH and the time the mIAB-MT starts transmission of the new PRACH, excluding the RRC procedure delay. + +When intra-frequency or inter-frequency handover is commanded, the interruption time shall be less than $T^{interrupt}$ : + +$$T_{interrupt} = T_{search} + T_{IU} + T_{processing} + T_{\Delta} + T_{margin} \text{ ms}$$ + +Where: + +$T_{search}$ is the time required to search the target cell when the target cell is not already known when the handover command is received by the mIAB-MT. If the target cell is known, then $T_{search} = 0$ ms. If the target cell is an unknown intra-frequency cell and the target cell $E_s/I_{ot} \geq -2$ dB, then $T_{search} = T_{rs}$ ms. Regardless of whether DRX is in use by the mIAB-MT, $T_{search}$ shall still be based on non-DRX target cell search time defined in clause TBD. + +$T_{\Delta}$ is time for fine time tracking and acquiring full timing information of the target cell. $T_{\Delta} = T_{rs}$ for both known and unknown target cell. + +$T_{processing}$ is time for mIAB-MT processing. $T_{processing}$ can be up to 20ms. + +$T_{margin}$ is time for SSB post-processing. $T_{margin}$ can be up to 2ms. + +$T_{IU}$ is the interruption uncertainty in acquiring the first available PRACH occasion in the new cell. $T_{IU}$ can be up to the summation of SSB to PRACH occasion association period and 10 ms. SSB to PRACH occasion associated period is defined in the table 8.1-1 of TS 38.213 [10]. + +$T_{rs}$ is the SMTC periodicity of the target NR cell if the mIAB-MT has been provided with an SMTC configuration for the target cell in the handover command, otherwise $T_{rs}$ is the SMTC configured in the *measObjectNR* having the same SSB frequency and subcarrier spacing. If the mIAB-MT is not provided with an SMTC configuration or measurement object on this frequency, the requirement in this clause is applied with $T_{rs}=5\text{ms}$ assuming the SSB transmission periodicity is 5ms. There is no requirement if the SSB transmission periodicity is not 5ms. If the mIAB-MT has been provided with higher layer in TS 38.331 [15] signaling of *smtc2* prior to the handover command and is not capable of 4 SMTC configurations per frequency [15], then $T_{rs}$ follows *smtc1* or *smtc2* according to the physical cell ID of the target cell. If the IAB-MT has been provided with higher layer signaling of *smtcj* (where $1 \leq j \leq 4$ [15]) prior to the handover command and is also capable of 4 SMTC configurations per frequency [15], then $T_{SMTC}$ follows *smtcj* according to the physical cell ID of the target cell. + +In the interruption requirement a cell is known if it has been meeting the relevant cell identification requirement during the last 5 seconds otherwise it is unknown. Relevant cell identification requirements are described in Clause TBD for intra-frequency handover. + +### 12.1.2B.3 NR FR2-1 - NR FR2-1 Intra-frequency Handover + +The requirements in this clause are applicable to intra-frequency handover of the mIAB-MT from NR FR2-1 cell to NR FR2-1 cell. + +#### 12.1.2B.3.1 Handover delay + +When the mIAB-MT receives a RRC message implying handover the mIAB-MT shall be ready to start the transmission of the new uplink PRACH channel within $D_{\text{handover}}$ ms from the end of the last TTI containing the RRC command. + +Where: + +$D_{\text{handover}}$ equals the applicable RRC procedure delay defined in clause 12 in TS 38.331 [15] plus the interruption time stated in clause 12.1.2B.3.2. + +#### 12.1.2B.3.2 Interruption time + +The interruption time is the time between end of the last TTI containing the RRC command on the old PDSCH and the time the mIAB-MT starts transmission of the new PRACH, excluding the RRC procedure delay. + +When intra-frequency or inter-frequency handover is commanded, the interruption time shall be less than $T^{\text{interrupt}}$ : + +$$T^{\text{interrupt}} = T_{\text{search}} + T_{IU} + T_{\text{processing}} + T_{\Delta} + T_{\text{margin}} \text{ ms}$$ + +Where: + +$T_{\text{search}}$ is the time required to search the target cell when the handover command is received by the mIAB-MT. If the target cell is a known cell, then $T_{\text{search}} = 0 \text{ ms}$ . If the target cell is an unknown intra-frequency cell and the target cell $E_s/I_{ot} \geq -2 \text{ dB}$ , then $T_{\text{search}} = N * T_{rs} \text{ ms}$ . $N=8$ when the target cell is in FR2-1. Regardless of whether DRX is in use by the mIAB-MT, $T_{\text{search}}$ shall still be based on non-DRX target cell search times. + +$T_{\text{processing}}$ is time for mIAB-MT processing. $T_{\text{processing}}$ can be up to 20ms. + +$T_{\text{margin}}$ is time for SSB post-processing. $T_{\text{margin}}$ can be up to 2ms. + +$T_{\Delta}$ is time for fine time tracking and acquiring full timing information of the target cell. $T_{\Delta} = T_{rs}$ for both known and unknown target cell. + +$T_{IU}$ is the interruption uncertainty in acquiring the first available PRACH occasion in the new cell. $T_{IU}$ can be up to the summation of SSB to PRACH occasion association period and 10 ms. SSB to PRACH occasion associated period is defined in the table 8.1-1 of TS 38.213 [10]. + +$T_{rs}$ is the SMTC periodicity of the target NR cell if the mIAB-MT has been provided with an SMTC configuration for the target cell in the handover command, otherwise $T_{rs}$ is the SMTC configured in the *measObjectNR* having the same SSB frequency and subcarrier spacing. If the mIAB-MT is not provided SMTC + +configuration or measurement object on this frequency, the requirement in this clause is applied with $T_{rs}=5\text{ms}$ assuming the SSB transmission periodicity is 5ms. There is no requirement if the SSB transmission periodicity is not 5ms. If the mIAB-MT has been provided with higher layer in TS 38.331 [15] signaling of *smtc2* prior to the handover command and is not capable of 4 SMTC configurations per frequency [15], then $T_{rs}$ follows *smtc1* or *smtc2* according to the physical cell ID of the target cell. If the IAB-MT has been provided with higher layer signaling of *smtcj* (where $1 \leq j \leq 4$ [15]) prior to the handover command and is also capable of 4 SMTC configurations per frequency [15], then $T_{SMTC}$ follows *smtcj* according to the physical cell ID of the target cell. + +In FR2-1, the target cell is known if it has been meeting the following conditions: + +- During the last 5 seconds before the reception of the handover command: + - the mIAB-MT has sent a valid measurement report for the target cell and + - One of the SSBs measured from the NR target cell being configured remains detectable according to the cell identification conditions specified in clause TBD for intra-frequency cell, + - One of the SSBs measured from the target cell also remains detectable during the handover delay according to the cell identification conditions specified in clause TBD for intra-frequency cell. + +otherwise it is unknown. + +## 12.2 Timing + +### 12.2.1 IAB-MT transmit timing + +#### 12.2.1.1 Introduction + +The IAB-MT shall have capability to follow the frame timing change of the reference cell in connected state. The uplink frame transmission takes place before the reception of the first detected path (in time) of the corresponding downlink frame from the reference cell. IAB-MT belonging to local area IAB-MT class as defined in clause 4.4.2 and also capable of carrier aggregation shall use the SpCell as the reference cell for deriving the IAB-MT transmit timing for cells in the PTAG. IAB-MT initial transmit timing accuracy, gradual timing adjustment requirements are defined in the following requirements. The requirements apply when the indicated IAB-MT transmission timing mode is set to 'Case 1' specified in clause 14 of TS 38.213 [10]. + +#### 12.2.1.2 Requirements + +The IAB-MT initial transmission timing error shall be less than or equal to $\pm T_c$ where the timing error limit value $T_c$ is specified in Table 12.2.1.2-1. This requirement applies for PUCCH, PUSCH and SRS or it is the PRACH transmission. + +The IAB-MT shall meet the $T_c$ requirement for an initial transmission provided that at least one SSB is available at the IAB-MT during the last 160 ms. The reference point for the IAB-MT initial transmit timing control requirement shall be the downlink timing of the reference cell minus $(N_{TA} + N_{TA\ offset}) \times T_c$ . The downlink timing is defined as the time when the first path (in time) of the corresponding downlink frame used by the IAB-MT to determine downlink timing is received from the reference cell at the IAB-MT antenna. $N_{TA}$ for PRACH is defined as 0. + +$(N_{TA} + N_{TA\ offset}) \times T_c$ (in $T_c$ units) for other channels is the difference between IAB-MT transmission timing and the downlink timing immediately after when the last timing advance in clause 12.2.2 was applied. $N_{TA}$ for other channels is not changed until next timing advance is received. The value of $N_{TA\ offset}$ depends on the duplex mode of the cell in which the uplink transmission takes place and the frequency range (FR). $N_{TA\ offset}$ is defined in Table 12.2.1.2-2. + +**Table 12.2.1.2-1: $T_e$ Timing Error Limit** + +| Frequency Range | SCS of SSB signals ( kHz) | SCS of uplink signals ( kHz) | $T_e$ | +|-----------------------------------------------------------------|---------------------------|------------------------------|--------------------------| +| 1 | 15 | 15 | $12 \cdot 64 \cdot T_c$ | +| | | 30 | $10 \cdot 64 \cdot T_c$ | +| | | 60 | $10 \cdot 64 \cdot T_c$ | +| | 30 | 15 | $8 \cdot 64 \cdot T_c$ | +| | | 30 | $8 \cdot 64 \cdot T_c$ | +| | | 60 | $7 \cdot 64 \cdot T_c$ | +| FR2-1 | 120 | 60 | $3.5 \cdot 64 \cdot T_c$ | +| | | 120 | $3.5 \cdot 64 \cdot T_c$ | +| | 240 | 60 | $3 \cdot 64 \cdot T_c$ | +| | | 120 | $3 \cdot 64 \cdot T_c$ | +| Note 1: $T_c$ is the basic timing unit defined in TS 38.211 [8] | | | | + +**Table 12.2.1.2-2: The Value of $N_{TA\ offset}$** + +| Frequency range and band of cell used for uplink transmission | $N_{TA\ offset}$ (Unit: $T_c$ ) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| FR1 TDD band without LTE-NR coexistence case | 25600 (Note 1) | +| FR1 TDD band with LTE-NR coexistence case | 39936 (Note 1) | +| FR2-1 | 13792 | +| Note 1: The IAB-MT identifies $N_{TA\ offset}$ based on the information n-TimingAdvanceOffset as specified in TS 38.331 [15]. If IAB-MT is not provided with the information n-TimingAdvanceOffset, the default value of $N_{TA\ offset}$ is set as 25600 for FR1 band. | | + +When it is the transmission for PUCCH, PUSCH and SRS transmission, the IAB-MT shall be capable of changing the transmission timing according to the received downlink frame of the reference cell except when the timing advance in clause 12.2.3 is applied. + +#### 12.2.1.2.1 Gradual timing adjustment + +When the transmission timing error between the IAB-MT and the reference timing exceeds $\pm T_e$ then the IAB-MT is required to adjust its timing to within $\pm T_e$ . The reference timing shall be $(N_{TA} + N_{TA\ offset}) \times T_c$ before the downlink timing of the reference cell. All adjustments made to the IAB-MT uplink timing shall follow these rules: + +- 1) The maximum amount of the magnitude of the timing change in one adjustment shall be $T_q$ . +- 2) The minimum aggregate adjustment rate shall be $T_p$ per second. +- 3) The maximum aggregate adjustment rate shall be $T_q$ per 200 ms. + +where the maximum autonomous time adjustment step $T_q$ and the aggregate adjustment rate $T_p$ are specified in Table 12.2.1.2.1-1. + +**Table 12.2.1.2.1-1: $T_q$ Maximum Autonomous Time Adjustment Step and $T_p$ Minimum Aggregate Adjustment rate** + +| Frequency Range | SCS of uplink signals (kHz) | $T_q$ | $T_p$ | +|---------------------------------------------------------------|-----------------------------|--------------------------|--------------------------| +| 1 | 15 | $5.5 \cdot 64 \cdot T_c$ | $5.5 \cdot 64 \cdot T_c$ | +| | 30 | $5.5 \cdot 64 \cdot T_c$ | $5.5 \cdot 64 \cdot T_c$ | +| | 60 | $5.5 \cdot 64 \cdot T_c$ | $5.5 \cdot 64 \cdot T_c$ | +| 2 | 60 | $2.5 \cdot 64 \cdot T_c$ | $2.5 \cdot 64 \cdot T_c$ | +| | 120 | $2.5 \cdot 64 \cdot T_c$ | $2.5 \cdot 64 \cdot T_c$ | +| NOTE: $T_c$ is the basic timing unit defined in TS 38.211 [8] | | | | + +## 12.2.2 Void + +## 12.2.3 IAB-MT timing advance + +### 12.2.3.1 Timing Advance adjustment delay + +The IAB-MT shall adjust the timing of its uplink transmission timing at time slot $n+k+1$ for a timing advance command received in time slot $n$ , and the value of $k$ is defined in clause 4.2 in TS 38.213 [10]. The requirements in this clause apply for IAB-MT, for 'Case 1' transmission timing mode specified in clause 14 of TS 38.213 [10]. + +### 12.2.3.2 Timing Advance adjustment accuracy + +The IAB-MT shall adjust the timing of its transmissions with a relative accuracy better than or equal to the IAB-MT Timing Advance adjustment accuracy requirement in Table 12.2.3-1, to the signalled timing advance value compared to the timing of preceding uplink transmission. The timing advance command step is defined in TS 38.213 [10]. + +**Table 12.2.3.2-1: UE Timing Advance adjustment accuracy** + +| UL Sub Carrier Spacing(kHz) | 15 | 30 | 60 | 120 | +|---------------------------------------|---------------|---------------|---------------|--------------| +| UE Timing Advance adjustment accuracy | $\pm 256 T_c$ | $\pm 256 T_c$ | $\pm 128 T_c$ | $\pm 32 T_c$ | + +## 12.2.4 Cell phase synchronization accuracy + +### 12.2.4.1 Introduction + +Cell phase synchronization accuracy for TDD is defined as the maximum absolute deviation in frame start timing between any pair of cells on the same frequency that have overlapping coverage areas. + +### 12.2.4.2 Requirements + +The cell phase synchronization accuracy measured at IAB DU TAB connectors or RIBs shall be better than $3 \mu\text{s}$ . + +## 12.3 Signalling Characteristics for IAB MTs + +### 12.3.1 Radio Link Monitoring + +#### 12.3.1.1 Introduction + +The UE requirements in sub-clause 8.1.1 [6] apply for IAB-MT. + +#### 12.3.1.2 Requirements for SSB based radio link monitoring + +##### 12.3.1.2.1 Introduction + +The requirements in this clause apply for each SSB based RLM-RS resource configured for PCell, provided that the SSB configured for RLM is actually transmitted within IAB-MT active DL BWP during the entire evaluation period specified in clause 12.3.1.2.2. + +**Table 12.3.1.2.1-1: PDCCH transmission parameters for out-of-sync evaluation** + +| Attribute | Value for BLER Configuration #0 | +|------------------------------------------------------------------|---------------------------------| +| DCI format | 1-0 | +| Number of control OFDM symbols | 2 | +| Aggregation level (CCE) | 8 | +| Ratio of hypothetical PDCCH RE energy to average SSS RE energy | 4dB | +| Ratio of hypothetical PDCCH DMRS energy to average SSS RE energy | 4dB | +| Bandwidth (PRBs) | 24 | +| Sub-carrier spacing (kHz) | SCS of the active DL BWP | +| DMRS precoder granularity | REG bundle size | +| REG bundle size | 6 | +| CP length | Normal | +| Mapping from REG to CCE | Distributed | + +**Table 12.3.1.2.1-2: PDCCH transmission parameters for in-sync evaluation** + +| Attribute | Value for BLER Configuration #0 | +|------------------------------------------------------------------|---------------------------------| +| DCI payload size | 1-0 | +| Number of control OFDM symbols | 2 | +| Aggregation level (CCE) | 4 | +| Ratio of hypothetical PDCCH RE energy to average SSS RE energy | 0dB | +| Ratio of hypothetical PDCCH DMRS energy to average SSS RE energy | 0dB | +| Bandwidth (PRBs) | 24 | +| Sub-carrier spacing (kHz) | SCS of the active DL BWP | +| DMRS precoder granularity | REG bundle size | +| REG bundle size | 6 | +| CP length | Normal | +| Mapping from REG to CCE | Distributed | + +### 12.3.1.2.2 Minimum requirement + +IAB-MT shall be able to evaluate whether the downlink radio link quality on the configured RLM-RS resource estimated over the last $T_{\text{Evaluate\_out\_SSB}}$ [ms] period becomes worse than the threshold $Q_{\text{out\_SSB}}$ within $T_{\text{Evaluate\_out\_SSB}}$ [ms] evaluation period. + +IAB-MT shall be able to evaluate whether the downlink radio link quality on the configured RLM-RS resource estimated over the last $T_{\text{Evaluate\_in\_SSB}}$ [ms] period becomes better than the threshold $Q_{\text{in\_SSB}}$ within $T_{\text{Evaluate\_in\_SSB}}$ [ms] evaluation period. + +$T_{\text{Evaluate\_out\_SSB}}$ and $T_{\text{Evaluate\_in\_SSB}}$ are defined in Table 12.3.1.2.2-1 for FR1 with scaling factor $K_1 = 5$ . + +$T_{\text{Evaluate\_out\_SSB}}$ and $T_{\text{Evaluate\_in\_SSB}}$ are defined in Table 12.3.1.2.2-2 for FR2-1 with scaling factor $N=8$ and $K_2 = 3$ . + +For FR1, + +- $P = 1$ + +For FR2-1, + +- $P=1$ , when the RLM-RS resource is not overlapped with SMTC occasion. +- , when the RLM-RS resource is partially overlapped with SMTC occasion ( $T_{\text{SSB}} < T_{\text{SMTCperiod}}$ ). +- $P = 3$ , when RLM-RS resource is fully overlapped with SMTC period ( $T_{\text{SSB}} = T_{\text{SMTCperiod}}$ ). + +If the IAB-MT is not capable of 4 SMTC configurations per frequency [15], and is provided with higher layer signaling of smtcj, where $1 \leq j \leq 2$ [15], then $T_{\text{SMTCperiod}}$ follows smtcjmax where jmax is the maximum value of all j for which smtcj has been configured. + +If the IAB-MT is capable of 4 SMTC configurations per frequency [15], and is provided with higher layer signaling of smtcj, where $1 \leq j \leq 4$ [15], then $T_{\text{SMTCperiod}}$ follows smtcjmax where jmax is the maximum value of all j for which smtcj has been configured. + +Longer evaluation period would be expected if the combination of RLM-RS resource and SMTC occasion configurations does not meet previous conditions. + +**Table 12.3.1.2.2-1: Evaluation period $T_{\text{Evaluate\_out\_SSB}}$ and $T_{\text{Evaluate\_in\_SSB}}$ for FR1** + +| Configuration | $T_{\text{Evaluate\_out\_SSB}}$ (ms) | $T_{\text{Evaluate\_in\_SSB}}$ (ms) | +|--------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------| +| no DRX | $\text{Max}(200 \times K_1, \text{Ceil}(10 \times P \times K_1) \times T_{\text{ssb}})$ | $\text{Max}(100 \times K_1, \text{Ceil}(5 \times P \times K_1) \times T_{\text{ssb}})$ | +| NOTE: $T_{\text{ssb}}$ is the periodicity of the SSB configured for RLM. | | | + +**Table 12.3.1.2.2-2: Evaluation period $T_{\text{Evaluate\_out\_SSB}}$ and $T_{\text{Evaluate\_in\_SSB}}$ for FR2-1** + +| Configuration | $T_{\text{Evaluate\_out\_SSB}}$ (ms) | $T_{\text{Evaluate\_in\_SSB}}$ (ms) | +|--------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------| +| no DRX | $\text{Max}(200 \times K_2, \text{Ceil}(10 \times P \times N \times K_2) \times T_{\text{ssb}})$ | $\text{Max}(100 \times K_2, \text{Ceil}(5 \times P \times N \times K_2) \times T_{\text{ssb}})$ | +| NOTE: $T_{\text{ssb}}$ is the periodicity of the SSB configured for RLM. | | | + +### 12.3.1.2.3 Measurement restrictions for SSB based RLM + +The UE requirements in sub-clause 8.1.2.3 [6] apply for IAB-MT. + +### 12.3.1.3 Requirements for CSI-RS based radio link monitoring + +#### 12.3.1.3.1 Introduction + +The requirements in this clause apply for each CSI-RS based RLM-RS resource configured for PCell, provided that the CSI-RS configured for RLM is actually transmitted within IAB-MT active DL BWP during the entire evaluation period specified in clause 12.3.1.3.2. IAB-MT is not expected to perform radio link monitoring measurements on the CSI-RS configured as RLM-RS if the CSI-RS is not in the active TCI state of any CORESET configured in the IAB-MT active BWP. + +**Table 12.3.1.3.1-1: PDCCH transmission parameters for out-of-sync evaluation** + +| Attribute | Value for BLER Configuration #0 | +|---------------------------------------------------------------------|---------------------------------| +| DCI format | 1-0 | +| Number of control OFDM symbols | 2 | +| Aggregation level (CCE) | 8 | +| Ratio of hypothetical PDCCH RE energy to average CSI-RS RE energy | 4dB | +| Ratio of hypothetical PDCCH DMRS energy to average CSI-RS RE energy | 4dB | +| Bandwidth (PRBs) | 48 | +| Sub-carrier spacing (kHz) | SCS of the active DL BWP | +| DMRS precoder granularity | REG bundle size | +| REG bundle size | 6 | +| CP length | Normal | +| Mapping from REG to CCE | Distributed | + +**Table 12.3.1.3.1-2: PDCCH transmission parameters for in-sync evaluation** + +| Attribute | Value for BLER Configuration #0 | +|---------------------------------------------------------------------|---------------------------------| +| DCI payload size | 1-0 | +| Number of control OFDM symbols | 2 | +| Aggregation level (CCE) | 4 | +| Ratio of hypothetical PDCCH RE energy to average CSI-RS RE energy | 0dB | +| Ratio of hypothetical PDCCH DMRS energy to average CSI-RS RE energy | 0dB | +| Bandwidth (PRBs) | 48 | +| Sub-carrier spacing (kHz) | SCS of the active DL BWP | +| DMRS precoder granularity | REG bundle size | +| REG bundle size | 6 | +| CP length | Normal | +| Mapping from REG to CCE | Distributed | + +### 12.3.1.3.2 Minimum requirement + +IAB-MT shall be able to evaluate whether the downlink radio link quality on the configured RLM-RS resource estimated over the last $T_{\text{Evaluate\_out\_CSI-RS}}$ [ms] period becomes worse than the threshold $Q_{\text{out\_CSI-RS}}$ within $T_{\text{Evaluate\_out\_CSI-RS}}$ [ms] evaluation period. + +IAB-MT shall be able to evaluate whether the downlink radio link quality on the configured RLM-RS resource estimated over the last $T_{\text{Evaluate\_in\_CSI-RS}}$ [ms] period becomes better than the threshold $Q_{\text{in\_CSI-RS}}$ within $T_{\text{Evaluate\_in\_CSI-RS}}$ [ms] evaluation period. + +- $T_{\text{Evaluate\_out\_CSI-RS}}$ and $T_{\text{Evaluate\_in\_CSI-RS}}$ are defined in Table 12.3.1.3.2-1 for FR1 with scaling factor $K_1 = 5$ . +- $T_{\text{Evaluate\_out\_CSI-RS}}$ and $T_{\text{Evaluate\_in\_CSI-RS}}$ are defined in Table 12.3.1.3.2-2 for FR2-1 with scaling factor $K_2 = 3$ . + +The requirements of $T_{\text{Evaluate\_out\_CSI-RS}}$ and $T_{\text{Evaluate\_in\_CSI-RS}}$ apply provided that the CSI-RS for RLM is not in a resource set configured with repetition ON. The requirements do not apply when the CSI-RS resource in the active TCI state of CORESET is the same CSI-RS resource for RLM and the TCI state information of the CSI-RS resource is not given, wherein the TCI state information means QCL Type-D to SSB for L1-RSRP or CSI-RS with repetition ON. + +For FR1, + +- $P=1$ . + +For FR2-1, + +- $P=1$ , when the RLM-RS resource is not overlapped with SMTC occasion. +- $P=2$ , when the RLM-RS resource is partially overlapped with SMTC occasion ( $T_{\text{CSI-RS}} < T_{\text{SMTCperiod}}$ ). +- $P = 3$ , when the RLM-RS resource is fully overlapped with SMTC occasion ( $T_{\text{CSI-RS}} = T_{\text{SMTCperiod}}$ ). + +If the IAB-MT is not capable of 4 SMTC configurations per frequency [15], and is provided with higher layer signaling of smtcj, where $1 \leq j \leq 2$ [15], then $T_{\text{SMTCperiod}}$ follows smtcjmax where jmax is the maximum value of all j for which smtcj has been configured. + +If the IAB-MT is capable of 4 SMTC configurations per frequency [15], and is provided with higher layer signaling of smtcj, where $1 \leq j \leq 4$ [15], then $T_{\text{SMTCperiod}}$ follows smtcjmax where jmax is the maximum value of all j for which smtcj has been configured. + +NOTE: The overlap between CSI-RS for RLM and SMTC means that CSI-RS based RLM is within the SMTC window duration. + +Longer evaluation period would be expected if the combination of RLM-RS resource and SMTC occasion configurations does not meet previous conditions. + +The values of $M_{\text{out}}$ and $M_{\text{in}}$ used in Table 12.3.1.3.2-1 and Table 12.3.1.3.2-2 are defined as: + +- $M_{\text{out}} = 20$ and $M_{\text{in}} = 10$ , if the CSI-RS resource configured for RLM is transmitted with higher layer CSI-RS parameter *density* [8, clause 7.4.1] set to 3 and over the bandwidth $\geq 24$ PRBs. + +**Table 12.3.1.3.2-1: Evaluation period $T_{\text{Evaluate\_out\_CSI-RS}}$ and $T_{\text{Evaluate\_in\_CSI-RS}}$ for FR1** + +| Configuration | $T_{\text{Evaluate\_out\_CSI-RS}}$ (ms) | $T_{\text{Evaluate\_in\_CSI-RS}}$ (ms) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------| +| no DRX | $\text{Max}(200 \times K_1, \text{Ceil}(M_{\text{out}} \times P \times K_1) \times T_{\text{CSI-RS}})$ | $\text{Max}(100 \times K_1, \text{Ceil}(M_{\text{in}} \times P \times K_1) \times T_{\text{CSI-RS}})$ | +| NOTE: $T_{\text{CSI-RS}}$ is the periodicity of the CSI-RS resource configured for RLM. The requirements in this table apply for $T_{\text{CSI-RS}}$ equal to 5 ms, 10ms, 20 ms or 40 ms. | | | + +**Table 12.3.1.3.2-2: Evaluation period $T_{\text{Evaluate\_out\_CSI-RS}}$ and $T_{\text{Evaluate\_in\_CSI-RS}}$ for FR2-1** + +| Configuration | $T_{\text{Evaluate\_out\_CSI-RS}}$ (ms) | $T_{\text{Evaluate\_in\_CSI-RS}}$ (ms) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------| +| no DRX | $\text{Max}(200 \times K_2, \text{Ceil}(M_{\text{out}} \times P \times K_2) \times T_{\text{CSI-RS}})$ | $\text{Max}(100 \times K_2, \text{Ceil}(M_{\text{in}} \times P \times K_2) \times T_{\text{CSI-RS}})$ | +| NOTE: $T_{\text{CSI-RS}}$ is the periodicity of the CSI-RS resource configured for RLM. The requirements in this table apply for $T_{\text{CSI-RS}}$ equal to 5 ms, 10 ms, 20 ms or 40 ms. | | | + +### 12.3.1.3.3 Measurement restrictions for CSI-RS based RLM + +The UE requirements in sub-clause 8.1.3.3 [6] apply for IAB-MT. + +### 12.3.1.4 Minimum requirement for IAB-MT turning off the transmitter + +The UE requirements in sub-clause 8.1.5 [6] apply for IAB-MT. + +### 12.3.1.5 Minimum requirement for L1 indication + +When the downlink radio link quality on all the configured RLM-RS resources is worse than $Q_{\text{out}}$ , layer 1 of the IAB-MT shall send an out-of-sync indication for the cell to the higher layers. A layer 3 filter shall be applied to the out-of-sync indications as specified in TS 38.331 [15]. + +When the downlink radio link quality on at least one of the configured RLM-RS resources is better than $Q_{\text{in}}$ , layer 1 of the IAB-MT shall send an in-sync indication for the cell to the higher layers. A layer 3 filter shall be applied to the in-sync indications as specified in TS 38.331 [15]. + +The out-of-sync and in-sync evaluations for the configured RLM-RS resources shall be performed as specified in clause 5 [10]. Two successive indications from layer 1 shall be separated by at least $T_{\text{Indication\_interval}}$ . + +$T_{\text{Indication\_interval}}$ is $\max(10\text{ms}, T_{\text{RLM-RS,M}})$ , where $T_{\text{RLM-RS,M}}$ is the shortest periodicity of all configured RLM-RS resources for the monitored cell, which corresponds to $T_{\text{SSB}}$ specified in clause 12.3.1.2 if the RLM-RS resource is SSB, or $T_{\text{CSI-RS}}$ specified in clause 12.3.1.3 if the RLM-RS resource is CSI-RS. + +### 12.3.1.6 Scheduling availability of IAB-MT during radio link monitoring + +The UE requirements in sub-clause 8.1.7 [6] apply for IAB-MT. + +## 12.3.2 Link Recovery Procedure + +### 12.3.2.1 Introduction + +The UE requirements in sub-clause 8.5.1 [6] apply for IAB-MT. + +### 12.3.2.2 Requirements for SSB based beam failure detection + +#### 12.3.2.2.1 Introduction + +The UE requirements in sub-clause 8.5.2.1 [6] apply for IAB-MT. + +### 12.3.2.2.2 Minimum requirement + +IAB-MT shall be able to evaluate whether the downlink radio link quality on the configured SSB resource in set estimated over the last $T_{\text{Evaluate\_BFD\_SSB}}$ ms period becomes worse than the threshold $Q_{\text{out\_LR\_SSB}}$ within $T_{\text{Evaluate\_BFD\_SSB}}$ ms period. + +The value of $T_{\text{Evaluate\_BFD\_SSB}}$ is defined in Table 12.3.2.2.2-1 for FR1. + +The value of $T_{\text{Evaluate\_BFD\_SSB}}$ is defined in Table 12.3.2.2.2-2 for FR2 with scaling factor $N=8$ . + +For FR1, + +- $P=1$ . + +For FR2, + +- $P=1$ , when the BFD-RS resource is not overlapped with SMTC occasion. +- $P=2$ , when the BFD-RS resource is partially overlapped with SMTC occasion ( $T_{\text{SSB}} < T_{\text{SMTCperiod}}$ ). +- $P=3$ , when the BFD-RS resource is fully overlapped with SMTC period ( $T_{\text{SSB}} = T_{\text{SMTCperiod}}$ ). + +If the IAB-MT is not capable of 4 SMTC configurations per frequency [15], and is provided with higher layer signaling of smtcj, where $1 \leq j \leq 2$ [15], then $T_{\text{SMTCperiod}}$ follows smtcjmax where jmax is the maximum value of all j for which smtcj has been configured. + +If the IAB-MT is capable of 4 SMTC configurations per frequency [15], and is provided with higher layer signaling of smtcj, where $1 \leq j \leq 4$ [15], then $T_{\text{SMTCperiod}}$ follows smtcjmax where jmax is the maximum value of all j for which smtcj has been configured. + +Longer evaluation period would be expected if the combination of BFD-RS resource and SMTC occasion does not meet previous conditions. + +**Table 12.3.2.2.2-1: Evaluation period $T_{\text{Evaluate\_BFD\_SSB}}$ for FR1** + +| Configuration | $T_{\text{Evaluate\_BFD\_SSB}}$ (ms) | +|---------------------------------------------------------------------------|--------------------------------------------------------| +| no DRX | Max(50, Ceil( $5 \times P$ ) $\times T_{\text{SSB}}$ ) | +| Note: $T_{\text{SSB}}$ is the periodicity of SSB in the set $\bar{q}_0$ . | | + +**Table 12.3.2.2.2-2: Evaluation period $T_{\text{Evaluate\_BFD\_SSB}}$ for FR2** + +| Configuration | $T_{\text{Evaluate\_BFD\_SSB}}$ (ms) | +|---------------------------------------------------------------------------|-----------------------------------------------------------------| +| no DRX | Max(50, Ceil( $5 \times P \times N$ ) $\times T_{\text{SSB}}$ ) | +| Note: $T_{\text{SSB}}$ is the periodicity of SSB in the set $\bar{q}_0$ . | | + +### 12.3.2.2.3 Measurement restriction for SSB based beam failure detection + +The UE requirements in sub-clause 8.5.2.3 [6] apply for IAB-MT. + +### 12.3.2.3 Requirements for CSI-RS based beam failure detection + +#### 12.3.2.3.1 Introduction + +The UE requirements in sub-clause 8.5.3.1 [6] apply for IAB-MT. + +#### 12.3.2.3.2 Minimum requirement + +IAB-MT shall be able to evaluate whether the downlink radio link quality on the CSI-RS resource in set estimated over the last $T_{\text{Evaluate\_BFD\_CSI-RS}}$ ms period becomes worse than the threshold $Q_{\text{out\_LR\_CSI-RS}}$ within $T_{\text{Evaluate\_BFD\_CSI-RS}}$ ms period. + +The value of $T_{\text{Evaluate\_BFD\_CSI-RS}}$ is defined in Table 12.3.2.3.2-1 for FR1. + +The value of $T_{\text{Evaluate\_BFD\_CSI-RS}}$ is defined in Table 12.3.2.3.2-2 for FR2-1 with $N=1$ . + +The requirements of $T_{\text{Evaluate\_BFD\_CSI-RS}}$ apply provided that the CSI-RS for BFD is not in a resource set configured with repetition ON. The requirements shall not apply when the CSI-RS resource in the active TCI state of CORESET is the same CSI-RS resource for BFD and the TCI state information of the CSI-RS resource is not given, wherein the TCI state information means QCL Type-D to SSB for L1-RSRP or CSI-RS with repetition ON. + +For FR1, + +- $P = 1$ . + +For FR2-1, + +- $P = 1$ , when the BFD-RS resource is not overlapped with SMTC occasion. +- $P = P_{\text{sharing factor}}$ , when the BFD-RS resource is partially overlapped with SMTC occasion ( $T_{\text{CSI-RS}} < T_{\text{SMTCperiod}}$ ). +- $P = P_{\text{sharing factor}}$ , when BFD-RS resource is fully overlapped with SMTC occasion ( $T_{\text{CSI-RS}} = T_{\text{SMTCperiod}}$ ). +- $P_{\text{sharing factor}} = 3$ . + +If the IAB-MT is not capable of 4 SMTC configurations per frequency [15], and is provided with higher layer signaling of smtcj, where $1 \leq j \leq 2$ [15], then $T_{\text{SMTCperiod}}$ follows smtcjmax where jmax is the maximum value of all j for which smtcj has been configured. + +If the IAB-MT is capable of 4 SMTC configurations per frequency [15], and is provided with higher layer signaling of smtcj, where $1 \leq j \leq 4$ [15], then $T_{\text{SMTCperiod}}$ follows smtcjmax where jmax is the maximum value of all j for which smtcj has been configured. + +NOTE: The overlap between CSI-RS for BFD and SMTC means that CSI-RS for BFD is within the SMTC window duration. + +Longer evaluation period would be expected if the combination of the BFD-RS resource and SMTC occasion configurations does not meet previous conditions. + +The values of $M_{\text{BFD}}$ used in Table 12.3.2.3.2-1 and Table 12.3.2.3.2-2 are defined as + +- $M_{\text{BFD}} = 10$ , if the CSI-RS resource(s) in set $\bar{q}_0$ used for BFD is transmitted with Density = 3 and over the bandwidth $\geq 24$ PRBs. + +**Table 12.3.2.3.2-1: Evaluation period $T_{\text{Evaluate\_BFD\_CSI-RS}}$ for FR1** + +| Configuration | $T_{\text{Evaluate\_BFD\_CSI-RS}}$ (ms) | +|---------------|------------------------------------------------------------------------------------| +| no DRX | $\text{Max}(50, [M_{\text{BFD}} \times P] \times T_{\text{CSI-RS}})$ | +| Note: | $T_{\text{CSI-RS}}$ is the periodicity of CSI-RS resource in the set $\bar{q}_0$ . | + +**Table 12.3.2.3.2-2: Evaluation period $T_{\text{Evaluate\_BFD\_CSI-RS}}$ for FR2-1** + +| Configuration | $T_{\text{Evaluate\_BFD\_CSI-RS}}$ (ms) | +|---------------|------------------------------------------------------------------------------------| +| no DRX | $\text{Max}(50, [M_{\text{BFD}} \times P \times N] \times T_{\text{CSI-RS}})$ | +| Note: | $T_{\text{CSI-RS}}$ is the periodicity of CSI-RS resource in the set $\bar{q}_0$ . | + +### 12.3.2.3.3 Measurement restrictions for CSI-RS based beam failure detection + +The UE requirements in sub-clause 8.5.3.3 [6] apply for IAB-MT. + +### 12.3.2.4 Minimum requirement for L1 indication + +When the radio link quality on all the RS resources in set is worse than $Q_{\text{out\_LR}}$ , layer 1 of the IAB-MT shall send a beam failure instance indication to the higher layers. A layer 3 filter may be applied to the beam failure instance indications as specified in TS 38.331 [15]. + +The beam failure instance evaluation for the RS resources in set shall be performed as specified in clause 6 in TS 38.213 [10]. Two successive indications from layer 1 shall be separated by at least $T_{\text{Indication\_interval\_BFD}}$ . + +$T_{\text{Indication\_interval\_BFD}}$ is $\max(2\text{ms}, T_{\text{SSB-RS,M}})$ or $\max(2\text{ms}, T_{\text{CSI-RS,M}})$ , where $T_{\text{SSB-RS,M}}$ and $T_{\text{CSI-RS,M}}$ is the shortest periodicity of all RS resources in set for the accessed cell, corresponding to either the shortest periodicity of the SSB in the set or CSI-RS resource in the set. + +### 12.3.2.5 Requirements for SSB based candidate beam detection + +#### 12.3.2.5.1 Introduction + +The requirements in this clause apply for each SSB resource in the set $\bar{q}_1$ configured for a serving cell, provided that the SSBs configured for candidate beam detection are actually transmitted within IAB-MT active DL BWP during the entire evaluation period specified in clause 12.3.2.5.2. + +#### 12.3.2.5.2 Minimum requirement + +Upon request the IAB-MT shall be able to evaluate whether the L1-RSRP measured on the configured SSB resource in set $\bar{q}_1$ estimated over the last $T_{\text{Evaluate\_CBD\_SSB}}$ ms period becomes better than the threshold $Q_{\text{in\_LR}}$ provided SSB\_RP and SSB Ês/Iot are according to Annex Table in B.2.4.1 [6] for a corresponding band. + +The IAB-MT shall monitor the configured SSB resources using the evaluation period in table 12.3.2.5.2-1 and 12.3.2.5.2-2 which is applicable to the non-DRX mode only. + +The value of $T_{\text{Evaluate\_CBD\_SSB}}$ is defined in Table 12.3.2.5.2-1 for FR1. + +The value of $T_{\text{Evaluate\_CBD\_SSB}}$ is defined in Table 12.3.2.5.2-2 for FR2-1 with scaling factor $N=8$ . + +Where, + +For FR1, + +- $P = 1$ . + +For FR2-1, + +- $P=1$ , when the candidate beam detection RS resource is not overlapped with SMTC occasion. +- $P=2$ , when candidate beam detection RS is partially overlapped with SMTC occasion ( $T_{\text{SSB}} < T_{\text{SMTCperiod}}$ ). +- $P = 3$ , when candidate beam detection RS is fully overlapped with SMTC period ( $T_{\text{SSB}} = T_{\text{SMTCperiod}}$ ). + +If the IAB-MT is not capable of 4 SMTC configurations per frequency [15], and is provided with higher layer signaling of smtcj, where $1 \leq j \leq 2$ [15], then $T_{\text{SMTCperiod}}$ follows smtcjmax where jmax is the maximum value of all j for which smtcj has been configured. + +If the IAB-MT is capable of 4 SMTC configurations per frequency [15], and is provided with higher layer signaling of smtcj, where $1 \leq j \leq 4$ [15], then $T_{\text{SMTCperiod}}$ follows smtcjmax where jmax is the maximum value of all j for which smtcj has been configured. + +Longer evaluation period would be expected if the combination of CBD-RS resource and SMTC occasion configurations does not meet previous conditions. + +**Table 12.3.2.5.2-1: Evaluation period $T_{\text{Evaluate\_CBD\_SSB}}$ for FR1** + +| Configuration | $T_{\text{Evaluate\_CBD\_SSB}}$ (ms) | +|---------------------------------------------------------------------------|-------------------------------------------------| +| non-DRX | $\text{Ceil}(3 \times P) \times T_{\text{SSB}}$ | +| Note: $T_{\text{SSB}}$ is the periodicity of SSB in the set $\bar{q}_1$ . | | + +**Table 12.3.2.5.2-2: Evaluation period $T_{\text{Evaluate\_CBD\_SSB}}$ for FR2-1** + +| Configuration | $T_{\text{Evaluate\_CBD\_SSB}}$ (ms) | +|---------------------------------------------------------------------------|----------------------------------------------------------| +| non-DRX | $\text{Ceil}(3 \times P \times N) \times T_{\text{SSB}}$ | +| Note: $T_{\text{SSB}}$ is the periodicity of SSB in the set $\bar{q}_1$ . | | + +### 12.3.2.5.3 Measurement restriction for SSB based candidate beam detection + +The UE requirements in sub-clause 8.5.5.3 [6] apply for IAB-MT. + +### 12.3.2.6 Requirements for CSI-RS based candidate beam detection + +#### 12.3.2.6.1 Introduction + +The requirements in this clause apply for each CSI-RS resource in the set $\bar{q}_1$ configured for a serving cell, provided that the CSI-RS resources configured for candidate beam detection are actually transmitted within IAB MT active DL BWP during the entire evaluation period specified in clause 12.3.2.6.2. + +#### 12.3.2.6.2 Minimum requirement + +Upon request the IAB-MT shall be able to evaluate whether the L1-RSRP measured on the configured CSI-RS resource in set $\bar{q}_1$ estimated over the last $T_{\text{Evaluate\_CBD\_CSI-RS}}$ [ms] period becomes better than the threshold $Q_{\text{in\_LR}}$ within $T_{\text{Evaluate\_CBD\_CSI-RS}}$ [ms] period provided CSI-RS Ês/Iot is according to Annex Table in B.2.4.2 [6] for a corresponding band. + +The IAB-MT shall monitor the configured CSI-RS resources using the evaluation period in table 12.3.2.6.2-1 and 12.3.2.6.2-2 which is applicable to the non-DRX mode only. + +The value of $T_{\text{Evaluate\_CBD\_CSI-RS}}$ is defined in Table 12.3.2.6.2-1 for FR1. + +The value of $T_{\text{Evaluate\_CBD\_CSI-RS}}$ is defined in Table 12.3.2.6.2-2 for FR2 with scaling factor $N=8$ . + +For FR1, + +- $P = 1$ . + +For FR2-1, + +- $P = 1$ , when candidate beam detection RS is not overlapped with SMTC occasion. +- $P = 2$ , when candidate beam detection RS is partially overlapped with SMTC occasion ( $T_{\text{CSI-RS}} < T_{\text{SMTCperiod}}$ ). +- $P = 3$ , when candidate beam detection RS is fully overlapped with SMTC occasion ( $T_{\text{CSI-RS}} = T_{\text{SMTCperiod}}$ ). + +If the IAB-MT is not capable of 4 SMTC configurations per frequency [15], and is provided with higher layer signaling of smtcj, where $1 \leq j \leq 2$ [15], then $T_{\text{SMTCperiod}}$ follows smtcjmax where jmax is the maximum value of all j for which smtcj has been configured. + +If the IAB-MT is capable of 4 SMTC configurations per frequency [15], and is provided with higher layer signaling of smtcj, where $1 \leq j \leq 4$ [15], then $T_{\text{SMTCperiod}}$ follows smtcjmax where jmax is the maximum value of all j for which smtcj has been configured. + +Longer evaluation period would be expected if the CSI-RS is on the same OFDM symbols with RLM, BFD, BM-RS, or other CBD-RS, according to the measurement restrictions defined in clause 12.3.2.6.3. + +The values of $M_{\text{CBD}}$ used in Table 12.3.2.6.2-1 and Table 12.3.2.6.2-2 are defined as + +- $M_{\text{CBD}} = 3$ , if the CSI-RS resource configured in the set $\bar{q}_1$ is transmitted with Density = 3 and over the bandwidth $\geq 24$ PRBs. + +**Table 12.3.2.6.2-1: Evaluation period $T_{\text{Evaluate\_CBD\_CSI-RS}}$ for FR1** + +| Configuration | $T_{\text{Evaluate\_CBD\_CSI-RS}}$ (ms) | +|------------------------------------------------------------------------------------------|------------------------------------------------------------------------| +| non-DRX | Max(25, Ceil( $M_{\text{CBD}} \times P$ ) $\times T_{\text{CSI-RS}}$ ) | +| Note: $T_{\text{CSI-RS}}$ is the periodicity of CSI-RS resource in the set $\bar{q}_1$ . | | + +**Table 12.3.2.6.2-2: Evaluation period $T_{\text{Evaluate\_CBD\_CSI-RS}}$ for FR2-1** + +| Configuration | $T_{\text{Evaluate\_CBD\_CSI-RS}}$ (ms) | +|------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------| +| non-DRX | $\text{Max}(25, \text{Ceil}(M_{\text{CBD}} \times P \times N) \times T_{\text{CSI-RS}})$ | +| Note: $T_{\text{CSI-RS}}$ is the periodicity of CSI-RS resource in the set $\bar{q}_1$ . | | + +### 12.3.2.6.3 Measurement restriction for CSI-RS based candidate beam detection + +The UE requirements in sub-clause 8.5.6.3 [6] apply for IAB-MT. + +### 12.3.2.7 Scheduling availability of IAB-MT during beam failure detection + +The UE requirements in sub-clause 8.5.7 [6] apply for IAB-MT. + +### 12.3.2.8 Scheduling availability of IAB-MT during candidate beam detection + +The UE requirements in sub-clause 8.5.8 [6] apply for IAB-MT. + +## 12.3B Signalling Characteristics for mIAB MTs + +### 12.3B.1 Radio Link Monitoring + +#### 12.3B.1.1 Introduction + +The UE requirements in sub-clause 8.1.1 [6] apply for mIAB-MT. + +#### 12.3B.1.2 Requirements for SSB based radio link monitoring + +##### 12.3B.1.2.1 Introduction + +The requirements in this clause apply for each SSB based RLM-RS resource configured for PCell or PSCell, provided that the SSB configured for RLM is actually transmitted within mIAB-MT active DL BWP during the entire evaluation period specified in clause 12.3B.1.2.2. + +**Table 12.3B.1.2.1-1: PDCCH transmission parameters for out-of-sync evaluation** + +| Attribute | Value for BLER Configuration #0 | +|------------------------------------------------------------------|---------------------------------| +| DCI format | 1-0 | +| Number of control OFDM symbols | 2 | +| Aggregation level (CCE) | 8 | +| Ratio of hypothetical PDCCH RE energy to average SSS RE energy | 4dB | +| Ratio of hypothetical PDCCH DMRS energy to average SSS RE energy | 4dB | +| Bandwidth (PRBs) | 24 | +| Sub-carrier spacing (kHz) | SCS of the active DL BWP | +| DMRS precoder granularity | REG bundle size | +| REG bundle size | 6 | +| CP length | Normal | +| Mapping from REG to CCE | Distributed | + +**Table 12.3B.1.2.1-2: PDCCH transmission parameters for in-sync evaluation** + +| Attribute | Value for BLER Configuration #0 | +|------------------------------------------------------------------|---------------------------------| +| DCI payload size | 1-0 | +| Number of control OFDM symbols | 2 | +| Aggregation level (CCE) | 4 | +| Ratio of hypothetical PDCCH RE energy to average SSS RE energy | 0dB | +| Ratio of hypothetical PDCCH DMRS energy to average SSS RE energy | 0dB | +| Bandwidth (PRBs) | 24 | +| Sub-carrier spacing (kHz) | SCS of the active DL BWP | +| DMRS precoder granularity | REG bundle size | +| REG bundle size | 6 | +| CP length | Normal | +| Mapping from REG to CCE | Distributed | + +### 12.3B.1.2.2 Minimum requirement + +mIAB-MT shall be able to evaluate whether the downlink radio link quality on the configured RLM-RS resource estimated over the last $T_{\text{Evaluate\_out\_SSB}}$ [ms] period becomes worse than the threshold $Q_{\text{out\_SSB}}$ within $T_{\text{Evaluate\_out\_SSB}}$ [ms] evaluation period. + +mIAB-MT shall be able to evaluate whether the downlink radio link quality on the configured RLM-RS resource estimated over the last $T_{\text{Evaluate\_in\_SSB}}$ [ms] period becomes better than the threshold $Q_{\text{in\_SSB}}$ within $T_{\text{Evaluate\_in\_SSB}}$ [ms] evaluation period. + +$T_{\text{Evaluate\_out\_SSB}}$ and $T_{\text{Evaluate\_in\_SSB}}$ are defined in Table 12.3B.1.2.2-1 for FR1. + +$T_{\text{Evaluate\_out\_SSB}}$ and $T_{\text{Evaluate\_in\_SSB}}$ are defined in Table 12.3B.1.2.2-2 for FR2-1-1 with scaling factor $N=8$ . + +For FR1, + +- $P = 1$ + +For FR2-1-1, + +- $P=1$ , when the RLM-RS resource is not overlapped with SMTC occasion. +- $P=1$ , when the RLM-RS resource is fully overlapped with SMTC occasion and the RLM-RS resource is: + - not overlapped with the SSB symbols indicated by *SSB-ToMeasure* and 1 data symbol before each consecutive SSB symbols indicated by *SSB-ToMeasure* and 1 data symbol after each consecutive SSB symbols indicated by *SSB-ToMeasure*, given that *SSB-ToMeasure* is configured, where the *SSB-ToMeasure* is the union set of *SSB-ToMeasure* from all the configured measurement objects merged on the same serving carrier, and, + - not overlapped by the RSSI symbols indicated by *ss-RSSI-Measurement* and 1 data symbol before each RSSI symbol indicated by *ss-RSSI-Measurement* and 1 data symbol after each RSSI symbol indicated by *ss-RSSI-Measurement*, given that *ss-RSSI-Measurement* is configured. +- , when the RLM-RS resource is partially overlapped with SMTC occasion ( $T_{\text{SSB}} < T_{\text{SMTCperiod}}$ ). +- $P = 3$ , otherwise. + +If the mIAB-MT is not capable of 4 SMTC configurations per frequency [15], and is provided with higher layer signaling of *smtcj*, where $1 \leq j \leq 2$ [15], then $T_{\text{SMTCperiod}}$ follows *smtcj*max where $j_{\text{max}}$ is the maximum value of all $j$ for which *smtcj* has been configured. + +If the mIAB-MT is capable of 4 SMTC configurations per frequency [15], and is provided with higher layer signaling of *smtcj*, where $1 \leq j \leq 4$ [15], then $T_{\text{SMTCperiod}}$ follows *smtcj*max where $j_{\text{max}}$ is the maximum value of all $j$ for which *smtcj* has been configured. + +Longer evaluation period would be expected if the combination of RLM-RS resource and SMTC occasion configurations does not meet previous conditions. + +**Table 12.3B.1.2.2-1: Evaluation period $T_{\text{Evaluate\_out\_SSB}}$ and $T_{\text{Evaluate\_in\_SSB}}$ for FR1** + +| Configuration | $T_{\text{Evaluate\_out\_SSB}}$ (ms) | $T_{\text{Evaluate\_in\_SSB}}$ (ms) | +|--------------------------------------------------------------------------|-------------------------------------------------------------------|------------------------------------------------------------------| +| no DRX | $\text{Max}(200, \text{Ceil}(10 \times P) \times T_{\text{SSB}})$ | $\text{Max}(100, \text{Ceil}(5 \times P) \times T_{\text{SSB}})$ | +| NOTE: $T_{\text{SSB}}$ is the periodicity of the SSB configured for RLM. | | | + +**Table 12.3B.1.2.2-2: Evaluation period $T_{\text{Evaluate\_out\_SSB}}$ and $T_{\text{Evaluate\_in\_SSB}}$ for FR2-1-1** + +| Configuration | $T_{\text{Evaluate\_out\_SSB}}$ (ms) | $T_{\text{Evaluate\_in\_SSB}}$ (ms) | +|--------------------------------------------------------------------------|----------------------------------------------------------------------------|---------------------------------------------------------------------------| +| no DRX | $\text{Max}(200, \text{Ceil}(10 \times P \times N) \times T_{\text{SSB}})$ | $\text{Max}(100, \text{Ceil}(5 \times P \times N) \times T_{\text{SSB}})$ | +| NOTE: $T_{\text{SSB}}$ is the periodicity of the SSB configured for RLM. | | | + +### 12.3B.1.2.3 Measurement restrictions for SSB based RLM + +The UE requirements in sub-clause 8.1.2.3 [6] apply for mIAB-MT. + +## 12.3B.1.3 Requirements for CSI-RS based radio link monitoring + +### 12.3B.1.3.1 Introduction + +The requirements in this clause apply for each CSI-RS based RLM-RS resource configured for PCell or PSCell, provided that the CSI-RS configured for RLM is actually transmitted within mIAB-MT active DL BWP during the entire evaluation period specified in clause 12.3B.1.3.2. mIAB-MT is not expected to perform radio link monitoring measurements on the CSI-RS configured as RLM-RS if the CSI-RS is not in the active TCI state of any CORESET configured in the mIAB-MT active BWP. + +**Table 12.3B.1.3.1-1: PDCCH transmission parameters for out-of-sync evaluation** + +| Attribute | Value for BLER Configuration #0 | +|---------------------------------------------------------------------|---------------------------------| +| DCI format | 1-0 | +| Number of control OFDM symbols | 2 | +| Aggregation level (CCE) | 8 | +| Ratio of hypothetical PDCCH RE energy to average CSI-RS RE energy | 4dB | +| Ratio of hypothetical PDCCH DMRS energy to average CSI-RS RE energy | 4dB | +| Bandwidth (PRBs) | 48 | +| Sub-carrier spacing (kHz) | SCS of the active DL BWP | +| DMRS precoder granularity | REG bundle size | +| REG bundle size | 6 | +| CP length | Normal | +| Mapping from REG to CCE | Distributed | + +**Table 12.3B.1.3.1-2: PDCCH transmission parameters for in-sync evaluation** + +| Attribute | Value for BLER Configuration #0 | +|---------------------------------------------------------------------|---------------------------------| +| DCI payload size | 1-0 | +| Number of control OFDM symbols | 2 | +| Aggregation level (CCE) | 4 | +| Ratio of hypothetical PDCCH RE energy to average CSI-RS RE energy | 0dB | +| Ratio of hypothetical PDCCH DMRS energy to average CSI-RS RE energy | 0dB | +| Bandwidth (PRBs) | 48 | +| Sub-carrier spacing (kHz) | SCS of the active DL BWP | +| DMRS precoder granularity | REG bundle size | +| REG bundle size | 6 | +| CP length | Normal | +| Mapping from REG to CCE | Distributed | + +### 12.3B.1.3.2 Minimum requirement + +mIAB-MT shall be able to evaluate whether the downlink radio link quality on the configured RLM-RS resource estimated over the last $T_{\text{Evaluate\_out\_CSI-RS}}$ [ms] period becomes worse than the threshold $Q_{\text{out\_CSI-RS}}$ within $T_{\text{Evaluate\_out\_CSI-RS}}$ [ms] evaluation period. + +mIAB-MT shall be able to evaluate whether the downlink radio link quality on the configured RLM-RS resource estimated over the last $T_{\text{Evaluate\_in\_CSI-RS}}$ [ms] period becomes better than the threshold $Q_{\text{in\_CSI-RS}}$ within $T_{\text{Evaluate\_in\_CSI-RS}}$ [ms] evaluation period. + +- $T_{\text{Evaluate\_out\_CSI-RS}}$ and $T_{\text{Evaluate\_in\_CSI-RS}}$ are defined in Table 12.3B.1.3.2-1 for FR1. +- $T_{\text{Evaluate\_out\_CSI-RS}}$ and $T_{\text{Evaluate\_in\_CSI-RS}}$ are defined in Table 12.3B.1.3.2-2 for FR2-1-1. + +The requirements of $T_{\text{Evaluate\_out\_CSI-RS}}$ and $T_{\text{Evaluate\_in\_CSI-RS}}$ apply provided that the CSI-RS for RLM is not in a resource set configured with repetition ON. The requirements do not apply when the CSI-RS resource in the active TCI state of CORESET is the same CSI-RS resource for RLM and the TCI state information of the CSI-RS resource is not given, wherein the TCI state information means QCL Type-D to SSB for L1-RSRP or CSI-RS with repetition ON. + +For FR1, + +- $P=1$ . + +For FR2-1-1, + +- $P=1$ , when the RLM-RS resource is not overlapped with SMTC occasion. +- $P=1$ , when the RLM-RS resource is fully overlapped with SMTC occasion and the RLM-RS resource is. + - not overlapped with the SSB symbols indicated by *SSB-ToMeasure* and 1 data symbol before each consecutive SSB symbols indicated by *SSB-ToMeasure* and 1 data symbol after each consecutive SSB symbols indicated by *SSB-ToMeasure*, given that *SSB-ToMeasure* is configured, where the *SSB-ToMeasure* is the union set of *SSB-ToMeasure* from all the configured measurement objects merged on the same serving carrier, and + - not overlapped by the RSSI symbols indicated by *ss-RSSI-Measurement* and 1 data symbol before each RSSI symbol indicated by *ss-RSSI-Measurement* and 1 data symbol after each RSSI symbol indicated by *ss-RSSI-Measurement*, given that *ss-RSSI-Measurement* is configured. +- , when the RLM-RS resource is partially overlapped with SMTC occasion ( $T_{\text{CSI-RS}} < T_{\text{SMTCperiod}}$ ). +- $P = 3$ , otherwise. + +If the mIAB-MT is not capable of 4 SMTC configurations per frequency [15], and is provided with higher layer signaling of smtcj, where $1 \leq j \leq 2$ [15], then $T_{\text{SMTCperiod}}$ follows smtcjmax where jmax is the maximum value of all j for which smtcj has been configured. + +If the mIAB-MT is capable of 4 SMTC configurations per frequency [15], and is provided with higher layer signaling of smtcj, where $1 \leq j \leq 4$ [15], then $T_{\text{SMTCperiod}}$ follows smtcjmax where jmax is the maximum value of all j for which smtcj has been configured. + +NOTE: The overlap between CSI-RS for RLM and SMTC means that CSI-RS based RLM is within the SMTC window duration. + +Longer evaluation period would be expected if the combination of RLM-RS resource and SMTC occasion configurations does not meet previous conditions. + +The values of $M_{\text{out}}$ and $M_{\text{in}}$ used in Table 12.3B.1.3.2-1 and Table 12.3B.1.3.2-2 are defined as: + +- $M_{\text{out}} = 20$ and $M_{\text{in}} = 10$ , if the CSI-RS resource configured for RLM is transmitted with higher layer CSI-RS parameter *density* [8, clause 7.4.1] set to 3 and over the bandwidth $\geq 24$ PRBs. + +**Table 12.3B.1.3.2-1: Evaluation period $T_{\text{Evaluate\_out\_CSI-RS}}$ and $T_{\text{Evaluate\_in\_CSI-RS}}$ for FR1** + +| Configuration | $T_{\text{Evaluate\_out\_CSI-RS}}$ (ms) | $T_{\text{Evaluate\_in\_CSI-RS}}$ (ms) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|---------------------------------------------------------------------------------| +| no DRX | $\text{Max}(200, \text{Ceil}(M_{\text{out}} \times P) \times T_{\text{CSI-RS}})$ | $\text{Max}(100, \text{Ceil}(M_{\text{in}} \times P) \times T_{\text{CSI-RS}})$ | +| NOTE: $T_{\text{CSI-RS}}$ is the periodicity of the CSI-RS resource configured for RLM. The requirements in this table apply for $T_{\text{CSI-RS}}$ equal to 5 ms, 10ms, 20 ms or 40 ms. | | | + +**Table 12.3B.1.3.2-2: Evaluation period $T_{\text{Evaluate\_out\_CSI-RS}}$ and $T_{\text{Evaluate\_in\_CSI-RS}}$ for FR2-1** + +| Configuration | $T_{\text{Evaluate\_out\_CSI-RS}}$ (ms) | $T_{\text{Evaluate\_in\_CSI-RS}}$ (ms) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|---------------------------------------------------------------------------------| +| no DRX | $\text{Max}(200, \text{Ceil}(M_{\text{out}} \times P) \times T_{\text{CSI-RS}})$ | $\text{Max}(100, \text{Ceil}(M_{\text{in}} \times P) \times T_{\text{CSI-RS}})$ | +| NOTE: $T_{\text{CSI-RS}}$ is the periodicity of the CSI-RS resource configured for RLM. The requirements in this table apply for $T_{\text{CSI-RS}}$ equal to 5 ms, 10 ms, 20 ms or 40 ms. | | | + +### 12.3B.1.3.3 Measurement restrictions for CSI-RS based RLM + +The UE requirements in sub-clause 8.1.3.3 [6] apply for mIAB-MT. + +### 12.3B.1.4 Minimum requirement for mIAB-MT turning off the transmitter + +The UE requirements in sub-clause 8.1.5 [6] apply for mIAB-MT. + +### 12.3B.1.5 Minimum requirement for L1 indication + +When the downlink radio link quality on all the configured RLM-RS resources is worse than $Q_{\text{out}}$ , layer 1 of the mIAB-MT shall send an out-of-sync indication for the cell to the higher layers. A layer 3 filter shall be applied to the out-of-sync indications as specified in TS 38.331 [15]. + +When the downlink radio link quality on at least one of the configured RLM-RS resources is better than $Q_{\text{in}}$ , layer 1 of the mIAB-MT shall send an in-sync indication for the cell to the higher layers. A layer 3 filter shall be applied to the in-sync indications as specified in TS 38.331 [15]. + +The out-of-sync and in-sync evaluations for the configured RLM-RS resources shall be performed as specified in clause 5 [10]. Two successive indications from layer 1 shall be separated by at least $T_{\text{Indication\_interval}}$ . + +$T_{\text{Indication\_interval}}$ is $\max(10\text{ms}, T_{\text{RLM-RS,M}})$ , where $T_{\text{RLM-RS,M}}$ is the shortest periodicity of all configured RLM-RS resources for the monitored cell, which corresponds to $T_{\text{SSB}}$ specified in clause 12.3B.1.2 if the RLM-RS resource is SSB, or $T_{\text{CSI-RS}}$ specified in clause 12.3B.1.3 if the RLM-RS resource is CSI-RS. + +### 12.3B.1.6 Scheduling availability of mIAB-MT during radio link monitoring + +The UE requirements in sub-clause 8.1.7 [6] apply for mIAB-MT. + +## 12.3B.2 Link Recovery Procedure + +### 12.3B.2.1 Introduction + +The UE requirements in sub-clause 8.5.1 [6] apply for mIAB-MT. + +### 12.3B.2.2 Requirements for SSB based beam failure detection + +#### 12.3B.2.2.1 Introduction + +The UE requirements in sub-clause 8.5.2.1 [6] apply for mIAB-MT. + +#### 12.3B.2.2.2 Minimum requirement + +mIAB-MT shall be able to evaluate whether the downlink radio link quality on the configured SSB resource in set estimated over the last $T_{\text{Evaluate\_BFD\_SSB}}$ ms period becomes worse than the threshold $Q_{\text{out\_LR\_SSB}}$ within $T_{\text{Evaluate\_BFD\_SSB}}$ ms period. + +The value of $T_{\text{Evaluate\_BFD\_SSB}}$ is defined in Table 12.3B.2.2.2-1 for FR1. + +The value of $T_{\text{Evaluate\_BFD\_SSB}}$ is defined in Table 12.3B.2.2.2-2 for FR2-1 with scaling factor $N=8$ . + +For FR1, + +- $P=1$ . + +For FR2-1, + +- $P=1$ , when the BFD-RS resource is not overlapped with SMTC occasion. +- $P=1$ , when the RLM-RS resource is fully overlapped with SMTC occasion and the RLM-RS resource is: + - not overlapped with the SSB symbols indicated by *SSB-ToMeasure* and 1 data symbol before each consecutive SSB symbols indicated by *SSB-ToMeasure* and 1 data symbol after each consecutive SSB symbols indicated by *SSB-ToMeasure*, given that *SSB-ToMeasure* is configured, where the *SSB-ToMeasure* is the union set of *SSB-ToMeasure* from all the configured measurement objects merged on the same serving carrier, and, + - not overlapped by the RSSI symbols indicated by *ss-RSSI-Measurement* and 1 data symbol before each RSSI symbol indicated by *ss-RSSI-Measurement* and 1 data symbol after each RSSI symbol indicated by *ss-RSSI-Measurement*, given that *ss-RSSI-Measurement* is configured. +- , when the BFD-RS resource is partially overlapped with SMTC occasion ( $T_{\text{SSB}} < T_{\text{SMTCperiod}}$ ). +- $P = 3$ , otherwise. + +If the mIAB-MT is not capable of 4 SMTC configurations per frequency [15], and is provided with higher layer signaling of $\text{smtcj}$ , where $1 \leq j \leq 2$ [15], then $T_{\text{SMTCperiod}}$ follows $\text{smtcj}_{\text{max}}$ where $j_{\text{max}}$ is the maximum value of all $j$ for which $\text{smtcj}$ has been configured. + +If the mIAB-MT is capable of 4 SMTC configurations per frequency [15], and is provided with higher layer signaling of $\text{smtcj}$ , where $1 \leq j \leq 4$ [15], then $T_{\text{SMTCperiod}}$ follows $\text{smtcj}_{\text{max}}$ where $j_{\text{max}}$ is the maximum value of all $j$ for which $\text{smtcj}$ has been configured. + +Longer evaluation period would be expected if the combination of BFD-RS resource and SMTC occasion does not meet previous conditions. + +**Table 12.3B.2.2.2-1: Evaluation period $T_{\text{Evaluate\_BFD\_SSB}}$ for FR1** + +| Configuration | $T_{\text{Evaluate\_BFD\_SSB}}$ (ms) | +|---------------|---------------------------------------------------------------------| +| no DRX | $\text{Max}(50, \text{Ceil}(5 \times P) \times T_{\text{SSB}})$ | +| Note: | $T_{\text{SSB}}$ is the periodicity of SSB in the set $\bar{q}_0$ . | + +**Table 12.3B.2.2.2-2: Evaluation period $T_{\text{Evaluate\_BFD\_SSB}}$ for FR2-1** + +| Configuration | $T_{\text{Evaluate\_BFD\_SSB}}$ (ms) | +|---------------------------------------------------------------------------|--------------------------------------------------------------------------| +| no DRX | $\text{Max}(50, \text{Ceil}(5 \times P \times N) \times T_{\text{SSB}})$ | +| Note: $T_{\text{SSB}}$ is the periodicity of SSB in the set $\bar{q}_0$ . | | + +### 12.3B.2.2.3 Measurement restriction for SSB based beam failure detection + +The UE requirements in sub-clause 8.5.2.3 [6] apply for mIAB-MT. + +### 12.3B.2.3 Requirements for CSI-RS based beam failure detection + +#### 12.3B.2.3.1 Introduction + +The UE requirements in sub-clause 8.5.3.1 [6] apply for mIAB-MT. + +#### 12.3B.2.3.2 Minimum requirement + +mIAB-MT shall be able to evaluate whether the downlink radio link quality on the CSI-RS resource in set estimated over the last $T_{\text{Evaluate\_BFD\_CSI-RS}}$ ms period becomes worse than the threshold $Q_{\text{out\_LR\_CSI-RS}}$ within $T_{\text{Evaluate\_BFD\_CSI-RS}}$ ms period. + +The value of $T_{\text{Evaluate\_BFD\_CSI-RS}}$ is defined in Table 12.3B.2.3.2-1 for FR1. + +The value of $T_{\text{Evaluate\_BFD\_CSI-RS}}$ is defined in Table 12.3B.2.3.2-2 for FR2-1 with $N=1$ . + +The requirements of $T_{\text{Evaluate\_BFD\_CSI-RS}}$ apply provided that the CSI-RS for BFD is not in a resource set configured with repetition ON. The requirements shall not apply when the CSI-RS resource in the active TCI state of CORESET is the same CSI-RS resource for BFD and the TCI state information of the CSI-RS resource is not given, wherein the TCI state information means QCL Type-D to SSB for L1-RSRP or CSI-RS with repetition ON. + +For FR1, + +- $P = 1$ . + +For FR2-1, + +- $P = 1$ , when the BFD-RS resource is not overlapped with SMTC occasion. +- $P=1$ , when the RLM-RS resource is fully overlapped with SMTC occasion and the RLM-RS resource is: + - not overlapped with the SSB symbols indicated by *SSB-ToMeasure* and 1 data symbol before each consecutive SSB symbols indicated by *SSB-ToMeasure* and 1 data symbol after each consecutive SSB symbols indicated by *SSB-ToMeasure*, given that *SSB-ToMeasure* is configured, where the *SSB-ToMeasure* is the union set of *SSB-ToMeasure* from all the configured measurement objects merged on the same serving carrier, and, + - not overlapped by the RSSI symbols indicated by *ss-RSSI-Measurement* and 1 data symbol before each RSSI symbol indicated by *ss-RSSI-Measurement* and 1 data symbol after each RSSI symbol indicated by *ss-RSSI-Measurement*, given that *ss-RSSI-Measurement* is configured. +- , when the BFD-RS resource is partially overlapped with SMTC occasion ( $T_{\text{CSI-RS}} < T_{\text{SMTCperiod}}$ ). +- $P = P_{\text{sharing factor}}$ , when BFD-RS resource is fully overlapped with SMTC occasion ( $T_{\text{CSI-RS}} = T_{\text{SMTCperiod}}$ ). +- $P_{\text{sharing factor}} = 3$ otherwise. + +If the mIAB-MT is not capable of 4 SMTC configurations per frequency [15], and is provided with higher layer signaling of *smtcj*, where $1 \leq j \leq 2$ [15], then $T_{\text{SMTCperiod}}$ follows *smtcjmax* where *jmax* is the maximum value of all *j* for which *smtcj* has been configured. + +If the mIAB-MT is capable of 4 SMTC configurations per frequency [15], and is provided with higher layer signaling of *smtcj*, where $1 \leq j \leq 4$ [15], then $T_{\text{SMTCperiod}}$ follows *smtcjmax* where *jmax* is the maximum value of all *j* for which *smtcj* has been configured. + +NOTE: The overlap between CSI-RS for BFD and SMTC means that CSI-RS for BFD is within the SMTC window duration. + +Longer evaluation period would be expected if the combination of the BFD-RS resource and SMTC occasion configurations does not meet previous conditions. + +The values of $M_{\text{BFD}}$ used in Table 12.3B.2.3.2-1 and Table 12.3B.2.3.2-2 are defined as + +- $M_{\text{BFD}} = 10$ , if the CSI-RS resource(s) in set $\bar{q}_0$ used for BFD is transmitted with Density = 3. + +**Table 12.3B.2.3.2-1: Evaluation period $T_{\text{Evaluate\_BFD\_CSI-RS}}$ for FR1** + +| Configuration | $T_{\text{Evaluate\_BFD\_CSI-RS}}$ (ms) | +|------------------------------------------------------------------------------------------|----------------------------------------------------------------------| +| no DRX | $\text{Max}(50, [M_{\text{BFD}} \times P] \times T_{\text{CSI-RS}})$ | +| Note: $T_{\text{CSI-RS}}$ is the periodicity of CSI-RS resource in the set $\bar{q}_0$ . | | + +**Table 12.3B.2.3.2-2: Evaluation period $T_{\text{Evaluate\_BFD\_CSI-RS}}$ for FR2-1** + +| Configuration | $T_{\text{Evaluate\_BFD\_CSI-RS}}$ (ms) | +|------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------| +| no DRX | $\text{Max}(50, [M_{\text{BFD}} \times P \times N] \times T_{\text{CSI-RS}})$ | +| Note: $T_{\text{CSI-RS}}$ is the periodicity of CSI-RS resource in the set $\bar{q}_0$ . | | + +### 12.3B.2.3.3 Measurement restrictions for CSI-RS based beam failure detection + +The UE requirements in sub-clause 8.5.3.3 [6] apply for mIAB-MT. + +### 12.3B.2.4 Minimum requirement for L1 indication + +When the radio link quality on all the RS resources in set $\bar{q}_0$ is worse than $Q_{\text{out\_LR}}$ , layer 1 of the mIAB-MT shall send a beam failure instance indication to the higher layers. A layer 3 filter may be applied to the beam failure instance indications as specified in TS 38.331 [15]. + +The beam failure instance evaluation for the RS resources in set $\bar{q}_0$ shall be performed as specified in clause 6 in TS 38.213 [10]. Two successive indications from layer 1 shall be separated by at least $T_{\text{Indication\_interval\_BFD}}$ . + +$T_{\text{Indication\_interval\_BFD}}$ is $\max(2\text{ms}, T_{\text{SSB-RS,M}})$ or $\max(2\text{ms}, T_{\text{CSI-RS,M}})$ , where $T_{\text{SSB-RS,M}}$ and $T_{\text{CSI-RS,M}}$ is the shortest periodicity of all RS resources in set $\bar{q}_0$ for the accessed cell, corresponding to either the shortest periodicity of the SSB in the set $\bar{q}_0$ or CSI-RS resource in the set $\bar{q}_0$ . + +### 12.3B.2.5 Requirements for SSB based candidate beam detection + +#### 12.3B.2.5.1 Introduction + +The requirements in this clause apply for each SSB resource in the set $\bar{q}_1$ configured for a serving cell, provided that the SSBs configured for candidate beam detection are actually transmitted within mIAB-MT active DL BWP during the entire evaluation period specified in clause 12.3B.2.5.2. + +#### 12.3B.2.5.2 Minimum requirement + +Upon request the mIAB-MT shall be able to evaluate whether the L1-RSRP measured on the configured SSB resource in set $\bar{q}_1$ estimated over the last $T_{\text{Evaluate\_CBD\_SSB}}$ ms period becomes better than the threshold $Q_{\text{in\_LR}}$ provided SSB\_RP and SSB Ês/Iot are according to Annex Table in B.2.4.1 [6] for a corresponding band. + +The mIAB-MT shall monitor the configured SSB resources using the evaluation period in table 12.3B.2.5.2-1 and 12.3B.2.5.2-2 which is applicable to the non-DRX mode only. + +The value of $T_{\text{Evaluate\_CBD\_SSB}}$ is defined in Table 12.3B.2.5.2-1 for FR1. + +The value of $T_{\text{Evaluate\_CBD\_SSB}}$ is defined in Table 12.3B.2.5.2-2 for FR2-1 with scaling factor $N=8$ . + +Where, + +For FR1,, + +- $P = 1$ . + +For FR2-1, + +- $P=1$ , when the candidate beam detection RS resource is not overlapped with SMTC occasion. +- $P=1$ , when the RLM-RS resource is fully overlapped with SMTC occasion and the RLM-RS resource is: + - not overlapped with the SSB symbols indicated by *SSB-ToMeasure* and 1 data symbol before each consecutive SSB symbols indicated by *SSB-ToMeasure* and 1 data symbol after each consecutive SSB symbols indicated by *SSB-ToMeasure*, given that *SSB-ToMeasure* is configured, where the *SSB-ToMeasure* is the union set of *SSB-ToMeasure* from all the configured measurement objects merged on the same serving carrier, and, + - not overlapped by the RSSI symbols indicated by *ss-RSSI-Measurement* and 1 data symbol before each RSSI symbol indicated by *ss-RSSI-Measurement* and 1 data symbol after each RSSI symbol indicated by *ss-RSSI-Measurement*, given that *ss-RSSI-Measurement* is configured. +- , when candidate beam detection RS is partially overlapped with SMTC occasion ( $T_{\text{SSB}} < T_{\text{SMTCperiod}}$ ). +- $P = 3$ , otherwise. + +If the mIAB-MT is not capable of 4 SMTC configurations per frequency [15], and is provided with higher layer signaling of *smtcj*, where $1 \leq j \leq 2$ [15], then $T_{\text{SMTCperiod}}$ follows $\text{smtcj}_{\text{jmax}}$ where $j_{\text{max}}$ is the maximum value of all $j$ for which *smtcj* has been configured. + +If the mIAB-MT is capable of 4 SMTC configurations per frequency [15], and is provided with higher layer signaling of *smtcj*, where $1 \leq j \leq 4$ [15], then $T_{\text{SMTCperiod}}$ follows $\text{smtcj}_{\text{jmax}}$ where $j_{\text{max}}$ is the maximum value of all $j$ for which *smtcj* has been configured. + +Longer evaluation period would be expected if the combination of CBD-RS resource and SMTC occasion configurations does not meet previous conditions. + +**Table 12.3B.2.5.2-1: Evaluation period $T_{\text{Evaluate\_CBD\_SSB}}$ for FR1** + +| Configuration | $T_{\text{Evaluate\_CBD\_SSB}}$ (ms) | +|---------------------------------------------------------------------------|-------------------------------------------------| +| non-DRX | $\text{Ceil}(3 \times P) \times T_{\text{SSB}}$ | +| Note: $T_{\text{SSB}}$ is the periodicity of SSB in the set $\bar{q}_1$ . | | + +**Table 12.3B.2.5.2-2: Evaluation period $T_{\text{Evaluate\_CBD\_SSB}}$ for FR2-1** + +| Configuration | $T_{\text{Evaluate\_CBD\_SSB}}$ (ms) | +|---------------------------------------------------------------------------|----------------------------------------------------------| +| non-DRX | $\text{Ceil}(3 \times P \times N) \times T_{\text{SSB}}$ | +| Note: $T_{\text{SSB}}$ is the periodicity of SSB in the set $\bar{q}_1$ . | | + +### 12.3B.2.5.3 Measurement restriction for SSB based candidate beam detection + +The UE requirements in sub-clause 8.5.5.3 [6] apply for mIAB-MT. + +### 12.3B.2.6 Requirements for CSI-RS based candidate beam detection + +#### 12.3B.2.6.1 Introduction + +The requirements in this clause apply for each CSI-RS resource in the set $\bar{q}_1$ configured for a serving cell, provided that the CSI-RS resources configured for candidate beam detection are actually transmitted within IAB MT active DL BWP during the entire evaluation period specified in clause 12.3B.2.6.2. + +### 12.3B.2.6.2 Minimum requirement + +Upon request the mIAB-MT shall be able to evaluate whether the L1-RSRP measured on the configured CSI-RS resource in set $\bar{q}_1$ estimated over the last $T_{\text{Evaluate\_CBD\_CSI-RS}}$ [ms] period becomes better than the threshold $Q_{\text{in\_LR}}$ within $T_{\text{Evaluate\_CBD\_CSI-RS}}$ [ms] period provided CSI-RS Ês/Iot is according to Annex Table in B.2.4.2 [6] for a corresponding band. + +The mIAB-MT shall monitor the configured CSI-RS resources using the evaluation period in table 12.3B.2.6.2-1 and 12.3B.2.6.2-2 which is applicable to the non-DRX mode only. + +The value of $T_{\text{Evaluate\_CBD\_CSI-RS}}$ is defined in Table 12.3B.2.6.2-1 for FR1. + +The value of $T_{\text{Evaluate\_CBD\_CSI-RS}}$ is defined in Table 12.3B.2.6.2-2 for FR2-1 with scaling factor $N=8$ . + +For FR1, + +- $P = 1$ . + +For FR2-1, + +- $P = 1$ , when candidate beam detection RS is not overlapped with SMTC occasion. +- $P=1$ , when the RLM-RS resource is fully overlapped with SMTC occasion and the RLM-RS resource is. + - not overlapped with the SSB symbols indicated by *SSB-ToMeasure* and 1 data symbol before each consecutive SSB symbols indicated by *SSB-ToMeasure* and 1 data symbol after each consecutive SSB symbols indicated by *SSB-ToMeasure*, given that *SSB-ToMeasure* is configured, where the *SSB-ToMeasure* is the union set of *SSB-ToMeasure* from all the configured measurement objects merged on the same serving carrier, and, + - not overlapped by the RSSI symbols indicated by *ss-RSSI-Measurement* and 1 data symbol before each RSSI symbol indicated by *ss-RSSI-Measurement* and 1 data symbol after each RSSI symbol indicated by *ss-RSSI-Measurement*, given that *ss-RSSI-Measurement* is configured. +- , when candidate beam detection RS is partially overlapped with SMTC occasion ( $T_{\text{CSI-RS}} < T_{\text{SMTCperiod}}$ ). +- $P = 3$ , otherwise. + +If the mIAB-MT is not capable of 4 SMTC configurations per frequency [15], and is provided with higher layer signaling of *smtcj*, where $1 \leq j \leq 2$ [15], then $T_{\text{SMTCperiod}}$ follows *smtcj*max where $j_{\text{max}}$ is the maximum value of all $j$ for which *smtcj* has been configured. + +If the mIAB-MT is capable of 4 SMTC configurations per frequency [15], and is provided with higher layer signaling of *smtcj*, where $1 \leq j \leq 4$ [15], then $T_{\text{SMTCperiod}}$ follows *smtcj*max where $j_{\text{max}}$ is the maximum value of all $j$ for which *smtcj* has been configured. + +Longer evaluation period would be expected if the CSI-RS is on the same OFDM symbols with RLM, BFD, BM-RS, or other CBD-RS, according to the measurement restrictions defined in clause 12.3B.2.6.3. + +The values of $M_{\text{CBD}}$ used in Table 12.3B.2.6.2-1 and Table 12.3B.2.6.2-2 are defined as + +- $M_{\text{CBD}} = 3$ , if the CSI-RS resource configured in the set $\bar{q}_1$ is transmitted with Density = 3. + +**Table 12.3B.2.6.2-1: Evaluation period $T_{\text{Evaluate\_CBD\_CSI-RS}}$ for FR1** + +| Configuration | $T_{\text{Evaluate\_CBD\_CSI-RS}}$ (ms) | +|------------------------------------------------------------------------------------------|------------------------------------------------------------------------| +| non-DRX | Max(25, Ceil( $M_{\text{CBD}} \times P$ ) $\times T_{\text{CSI-RS}}$ ) | +| Note: $T_{\text{CSI-RS}}$ is the periodicity of CSI-RS resource in the set $\bar{q}_1$ . | | + +**Table 12.3B.2.6.2-2: Evaluation period $T_{\text{Evaluate\_CBD\_CSI-RS}}$ for FR2-1** + +| Configuration | $T_{\text{Evaluate\_CBD\_CSI-RS}}$ (ms) | +|------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------| +| non-DRX | $\text{Max}(25, \text{Ceil}(M_{\text{CBD}} \times P \times N) \times T_{\text{CSI-RS}})$ | +| Note: $T_{\text{CSI-RS}}$ is the periodicity of CSI-RS resource in the set $\bar{q}_i$ . | | + +### 12.3B.2.6.3 Measurement restriction for CSI-RS based candidate beam detection + +The UE requirements in sub-clause 8.5.6.3 [6] apply for mIAB-MT. + +### 12.3B.2.7 Scheduling availability of mIAB-MT during beam failure detection + +The UE requirements in sub-clause 8.5.7 [6] apply for mIAB-MT. + +### 12.3B.2.8 Scheduling availability of mIAB-MT during candidate beam detection + +The UE requirements in sub-clause 8.5.8 [6] apply for mIAB-MT. + +## 12.3B.3 Active TCI state switching delay + +### 12.3B.3.1 Introduction + +The requirements in this clause apply for an mIAB-MT configured with one or more TCI state configurations on serving cell. mIAB-MT shall complete the switch of active TCI state within the delay defined in this clause. + +### 12.3B.3.2 Known conditions for TCI state + +The TCI state is known if the following conditions are met: + +- During the period from the last transmission of the RS resource used for the L1-RSRP measurement reporting for the target TCI state to the completion of active TCI state switch, where the RS resource for L1-RSRP measurement is the RS in target TCI state or QCLed to the target TCI state +- TCI state switch command is received within 1280 ms upon the last transmission of the RS resource for beam reporting or measurement +- The mIAB-MT has sent at least 1 L1-RSRP report for the target TCI state before the TCI state switch command +- The TCI state remains detectable during the TCI state switching period +- The SSB associated with the TCI state remain detectable during the TCI switching period + - SNR of the TCI state $\geq -3\text{dB}$ + +Otherwise, the TCI state is unknown. + +### 12.3B.3.3 MAC-CE based TCI state switch delay + +If the target TCI state is known, upon receiving PDSCH carrying MAC-CE activation command in slot $n$ , mIAB-MT shall be able to receive PDCCH with target TCI state of the serving cell on which TCI state switch occurs at the first slot that is after slot $n + T_{\text{HARQ}} + TO_k * (T_{\text{first-SSB}} + T_{\text{SSB-proc}}) / \text{NR slot length}$ . The mIAB-MT shall be able to receive PDCCH with the old TCI state until slot $n + T_{\text{HARQ}} + TO_k$ . Where $T_{\text{HARQ}}$ is the timing between DL data transmission and acknowledgement as specified in TS 38.213 [3]; + +- $T_{\text{first-SSB}}$ is time to first SSB transmission after MAC CE command is decoded by the mIAB-MT; The SSB shall be the QCL-TypeA or QCL-TypeC to target TCI state +- $T_{\text{SSB-proc}} = 2 \text{ ms}$ ; +- $TO_k = 1$ if target TCI state is not in the active TCI state list for PDSCH, 0 otherwise. + +If the target TCI state is unknown, upon receiving PDSCH carrying MAC-CE activation command in slot $n$ , mIAB-MT shall be able to receive PDCCH with target TCI state of the serving cell on which TCI state switch occurs at the first slot that is after slot $n + T_{\text{HARQ}} + T_{\text{L1-RSRP}} + TO_{\text{uk}} * (T_{\text{first-SSB}} + T_{\text{SSB-proc}}) / NR \text{ slot length}$ . The mIAB-MT shall be able to receive PDCCH with the old TCI state until slot $n + T_{\text{HARQ}} +$ . + +Where + +- $T_{\text{L1-RSRP}} = 0$ in FR1 or when the TCI state switching not involving QCL-TypeD in FR2. Otherwise, +- $T_{\text{L1-RSRP}}$ is the time for Rx beam refinement in FR2, defined as +- $T_{\text{L1-RSRP\_Measurement\_Period\_SSB}}$ for SSB as specified in clause TBD, + - with the assumption of $M=1$ + - with $T_{\text{Report}} = 0$ +- $T_{\text{L1-RSRP\_Measurement\_Period\_CSI-RS}}$ for CSI-RS as specified in clause TBD + - configured with higher layer parameter *repetition* set to ON + - with the assumption of $M=1$ for periodic CSI-RS + - for aperiodic CSI-RS if number of resources in resource set at least equal to *MaxNumberRxBeam* + - with $T_{\text{Report}} = 0$ +- $TO_{\text{uk}} = 1$ for CSI-RS based L1-RSRP measurement, and 0 for SSB based L1-RSRP measurement when TCI state switching involves QCL-TypeD +- $TO_{\text{uk}} = 1$ when TCI state switching involves other QCL types only +- $T_{\text{first-SSB}}$ is time to first SSB transmission after L1-RSRP measurement when TCI state switching involves QCL-TypeD; +- $T_{\text{first-SSB}}$ is time to first SSB transmission after MAC CE command is decoded by the mIAB-MT for other QCL types; +- The SSB shall be the QCL-TypeA or QCL-TypeC to target TCI state + +### 12.3B.3.4 DCI based TCI state switch delay + +If the target TCI state is known, when a mIAB-MT is configured with the higher layer parameter *tci-PresentInDCI* which is set as 'enabled' for the CORESET scheduling PDSCH at slot $n$ , mIAB-MT shall be able to receive PDSCH with target TCI state of the serving cell on which TCI state switch occurs at the first slot that is after slot $n + \text{timeDurationForQCL}$ , where, *timeDurationForQCL* is the time required by the mIAB-MT to perform PDCCH reception and applying spatial QCL information received in DCI for PDSCH processing as described in TS 38.214 [26], the value mIAB-MT of *timeDurationForQCL* is defined in TS 38.331 [2]. + +The known condition for TCI state defined in clause 12.3B.3.2 is applied. + +### 12.3B.3.5 RRC based TCI state switch delay + +If the target TCI state is known, mIAB-MT shall be able to receive PDCCH with target TCI state of the serving cell on which TCI state switch occurs at the first slot that is after slot $n + (T_{\text{RRC\_processing}} + TO_{\text{k}} * (T_{\text{first-SSB}} + T_{\text{SSB-proc}})) / NR \text{ slot length}$ . The mIAB-MT is not required to receive PDCCH/PDSCH/CSI-RS or transmit PUCCH/PUSCH until the end of switching period. + +Where + +- Slot $n$ is the last slot overlapping with the PDSCH carrying RRC activation command. +- $T_{\text{RRC\_processing}}$ is the RRC processing delay defined in Clause 12 of TS 38.331 [2]. +- $T_{\text{first-SSB}}$ is time to first SSB transmission after RRC processing by the mIAB-MT; The SSB shall be the QCL-TypeA or QCL-TypeC to target TCI state. + +- $T_{\text{SSB-proc}}$ and $TO_k$ are defined in clause 12.3.B.3.3. + +If the target TCI state is unknown, mIAB-MT shall be able to receive PDCCH with target TCI state of the serving cell on which TCI state switch occurs at the first slot that is after slot $n + (T_{\text{RRC\_processing}} + T_{\text{L1-RSRP}} + TO_{\text{uk}} * (T_{\text{first-SSB}} + T_{\text{SSB-proc}})) / \text{NR slot length}$ . The mIAB-MT is not required to receive PDCCH/PDSCH/CSI-RS or transmit PUCCH/PUSCH until the end of switching period. + +Where + +- Slot $n$ is the last slot overlapping with the PDSCH carrying RRC activation command. +- $T_{\text{RRC\_processing}}$ is the RRC processing delay defined in Clause 12 of TS 38.331 [2]. +- $T_{\text{first-SSB}}$ is time to first SSB transmission after L1-RSRP measurement when TCI state switching involves QCL-TypeD; +- $T_{\text{first-SSB}}$ is time to first SSB transmission after RRC processing time at the mIAB-MT for other QCL types; + - The SSB shall be the QCL-TypeA or QCL-TypeC to target TCI state +- $T_{\text{L1-RSRP}}$ , $TO_{\text{uk}}$ and $T_{\text{SSB-proc}}$ are defined in clause 12.3.B.3.3. + +The requirements for RRC based TCI state switch delay apply when only 1 TCI state is configured in RRC TCI state list. When a longer switching delay is allowed. Where is the time between DL data transmission and acknowledgement as specified in TS 38.213 [3]. + +### 12.3.B.3.6 Active TCI state list update delay + +If the target TCI state is known, upon receiving PDSCH carrying MAC-CE active TCI state list update at slot $n$ , mIAB-MT shall be able to receive PDCCH to schedule PDSCH with the new target TCI state at the first slot that is after $n + T_{\text{HARQ}} + TO_k * (T_{\text{first-SSB}} + T_{\text{SSB-proc}}) / \text{NR slot length}$ . Where $T_{\text{HARQ}}$ , $T_{\text{first-SSB}}$ , $T_{\text{SSB-proc}}$ and $TO_k$ are defined in clause 12.3.X.3. + +## 12.4 Void + +### 12.4B Measurement Procedure for mIAB-MT + +#### 12.4B.1 General measurement requirement + +##### 12.4B.1.1 Introduction + +This clause contains general requirements on the mIAB-MT regarding measurement reporting in RRC\_CONNECTED state. The requirements are split in intra-frequency and L1-RSRP measurements requirements. The measurement quantities are defined in TS38.215 [x], the measurement model is defined in TS38.300 [x], TS37.340 [x] and measurement accuracies are specified in clause TBA. Control of measurement reporting is specified in TS 38.331 [x]. + +#### 12.4B.2 NR intra-frequency measurements + +##### 12.4B.2.1 Introduction + +A measurement is defined as a SSB based intra-frequency measurement provided the centre frequency of the SSB of the serving cell indicated for measurement and the centre frequency of the SSB of the neighbour cell are the same, and the subcarrier spacing of the two SSBs are also the same. + +The mIAB-MT shall be able to identify new intra-frequency cells and perform SS-RSRP, SS-RSRQ, and SS-SINR measurements of identified intra-frequency cells if carrier frequency information is provided by PCell, even if no explicit neighbour list with physical layer cell identities is provided. + +For intra-frequency connected mode measurements, up to two measurement window periodicities may be configured. A single measurement window offset and measurement duration are configured per intra-frequency measurement object. + +## 12.4B.2.2 Requirements applicability + +The requirements in clause 12.4B.2 apply, provided: + +- The cell being identified or measured is detectable. + +An intra-frequency cell shall be considered detectable when for each relevant SSB: + +- SS-RSRP related side conditions given in clauses TBA and TBA for FR1 and FR2-1, respectively, for a corresponding Band, +- SS-RSRQ related side conditions given in clauses TBA and TBA for FR1 and FR2-1, respectively, for a corresponding Band, +- SS-SINR related side conditions given in clauses TBA and TBA for FR1 and FR2-1, respectively, for a corresponding Band, +- SSB\_RP and SSB Ês/Iot according to Annex TBA for a corresponding Band. + +## 12.4B.2.3 Number of cells and number of SSB + +### 12.4B.2.3.1 Requirements for FR1 + +For each intra-frequency layer, during each layer 1 measurement period, the mIAB-MT shall be capable of performing SS-RSRP, SS-RSRQ, and SS-SINR measurements for at least: + +- 8 identified cells, and +- 14 SSBs with different SSB index and/or PCI on the intra-frequency layer, where the number of SSBs in the serving cell is not smaller than the number of configured RLM-RS SSB resources. + +### 12.4B.2.3.2 Requirements for FR2-1 + +For one single intra-frequency layer in a band, during each layer 1 measurement period, the mIAB-MT shall be capable of performing SS-RSRP, SS-RSRQ, and SS-SINR measurements for at least: + +- 6 identified cells, and +- 24 SSBs with different SSB index and/or PCI, + +where this single intra-frequency layer shall be PCC when mIAB-MT is configured with SA NR operation mode with PCC in the band. + +The mIAB-MT shall also be capable of performing SS-RSRP, SS-RSRQ, and SS-SINR measurements for at least 2 SSBs on serving cell for each of the other intra-frequency layer(s) in the same band. + +## 12.4B.2.4 Measurement Reporting Requirements + +### 12.4B.2.4.1 Periodic Reporting + +Reported RSRP, RSRQ, and RS-SINR measurements contained in periodic measurement reports shall meet the requirements in clauses TBA (RSRP for FR1), TBA (RSRP for FR2-1), TBA (RSRQ for FR1), TBA (RSRQ for FR2-1), TBA (RS-SINR for FR1) and TBA (RS-SINR for FR2-1). + +### 12.4B.2.4.2 Event-triggered Periodic Reporting + +Reported RSRP, RSRQ, and RS-SINR measurements contained in event-triggered periodic measurement reports shall meet the requirements in clauses TBA (RSRP for FR1), TBA (RSRP for FR2), TBA (RSRQ for FR1), TBA (RSRQ for FR2-1), TBA (RS-SINR for FR1) and TBA (RS-SINR for FR2-1). + +The first report in event triggered periodic measurement reporting shall meet the requirements specified in clause 12.4B.2.4.3. + +### 12.4B.2.4.3 Event Triggered Reporting + +Reported RSRP, RSRQ, and RS-SINR measurements contained in event triggered measurement reports shall meet the requirements in clauses TBA (RSRP for FR1), TBA (RSRP for FR2-1), TBA (RSRQ for FR1), TBA (RSRQ for FR2-1), TBA (RS-SINR for FR1) and TBA (RS-SINR for FR2-1). + +The mIAB-MT shall not send any event triggered measurement reports as long as no reporting criteria is fulfilled. + +The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the point when the mIAB-MT starts to transmit the measurement report over the air interface. This requirement assumes that the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty is: $2 \times \text{TTI}_{\text{DCCH}}$ . This measurement reporting delay excludes a delay which caused by no UL resources being available for mIAB-MT to send the measurement report on. + +The event triggered measurement reporting delay, measured without L3 filtering shall be less than $T_{\text{identify\_intra\_with\_index}}$ or $T_{\text{identify\_intra\_without\_index}}$ defined in clause 12.4B.2.5.1. When L3 filtering is used an additional delay can be expected. + +A cell is detectable only if at least one SSBs measured from the Cell being configured remains detectable during the time period $T_{\text{identify\_intra\_without\_index}}$ or $T_{\text{identify\_intra\_with\_index}}$ as defined in clause 12.4B.2.5.1. If a cell which has been detectable at least for the time period $T_{\text{identify\_intra\_without\_index}}$ or $T_{\text{identify\_intra\_with\_index}}$ defined in clause 12.4B.2.5.1 becomes undetectable for a period $\leq 5$ seconds and then the cell becomes detectable again with the same spatial reception parameter and triggers an event, the event triggered measurement reporting delay shall be less than $T_{\text{SSB\_measurement\_period\_intra}}$ provided the timing to that cell has not changed more than $\pm 3200/T_c$ and L3 filtering has not been used, where $\mu$ is the SCS configuration as defined in clause 4.2 of TS 38.211 [x]. When L3 filtering is used, an additional delay can be expected. + +### 12.4B.2.5 Intrafrequency measurements without measurement gaps + +#### 12.4B.2.5.1 Intrafrequency cell identification + +The mIAB-MT shall be able to identify a new detectable intra-frequency cell within $T_{\text{identify\_intra\_without\_index}}$ if the mIAB-MT is not indicated to report SSB based RRM measurement result with the associated SSB index (*reportQuantityRsIndexes* or *maxNrofRSIndexesToReport* is not configured), or the mIAB-MT is indicated that the neighbour cell is synchronous with the serving cell (*deriveSSB-IndexFromCell* is enabled). Otherwise mIAB-MT shall be able to identify a new detectable intra frequency cell within $T_{\text{identify\_intra\_with\_index}}$ . The mIAB-MT shall be able to identify a new detectable intra frequency SS block of an already detected cell within $T_{\text{identify\_intra\_without\_index}}$ . It is assumed that *deriveSSB-IndexFromCell* is always enabled for FR1 TDD and FR2-1 with SCS smaller or equal to 240 kHz. + +$$T_{\text{identify\_intra\_without\_index}} = (T_{\text{PSS/SSS\_sync\_intra}} + T_{\text{SSB\_measurement\_period\_intra}}) \text{ ms}$$ + +$$T_{\text{identify\_intra\_with\_index}} = (T_{\text{PSS/SSS\_sync\_intra}} + T_{\text{SSB\_measurement\_period\_intra}} + T_{\text{SSB\_time\_index\_intra}}) \text{ ms}$$ + +Where: + +$T_{\text{PSS/SSS\_sync\_intra}}$ : it is the time period used in PSS/SSS detection given in table 12.4B.2.5.1-1, 12.4B.2.5.1-2 + +$T_{\text{SSB\_time\_index\_intra}}$ : it is the time period used to acquire the index of the SSB being measured given in table 12.4B.2.5.1-3. + +$T_{\text{SSB\_measurement\_period\_intra}}$ : equal to a measurement period of SSB based measurement given in table 12.4B.2.5.2-1, table 12.4B.2.5.2-2. + +if the high layer in TS 38.331 [x] signalling of *smtc2* is configured, the assumed periodicity of intra-frequency SMTC occasions corresponds to the value of higher layer parameter *smtc2*; Otherwise the assumed periodicity of intra-frequency SMTC occasions corresponds to the value of higher layer parameter *smtc1*. + +$M_{\text{pss/sss\_sync\_w/o\_gaps}}$ : For a mIAB-MT supporting FR2-1 TBA, $M_{\text{pss/sss\_sync\_w/o\_gaps}} = \text{TBA}$ . For a mIAB-MT supporting FR2-1 power class TBA, $M_{\text{pss/sss\_sync\_w/o\_gaps}} = \text{TBA}$ . + +$M_{\text{meas\_period\_w/o\_gaps}}$ : For a mIAB-MT supporting FR2-1 power class TBA, $M_{\text{meas\_period\_w/o\_gaps}} = \text{TBA}$ . For a mIAB-MT supporting FR2-1 power class TBA, $M_{\text{meas\_period\_w/o\_gaps}} = \text{TBA}$ . + +For FR2-1, + +$K_{\text{layer1\_measurement}}=1$ , + +- if all of the reference signals configured for RLM, BFD, CBD or L1-RSRP for beam reporting on any FR2-1 serving frequency in the same band are not fully overlapped by intra-frequency SMTC occasions, or +- if all of the reference signal configured for RLM, BFD, CBD or L1-RSRP for beam reporting on any FR2-1 serving frequency in the same band and fully-overlapped by intra-frequency SMTC occasions are not overlapped with any of the SSB symbols and the RSSI symbols, and 1 symbol before each consecutive SSB symbols and the RSSI symbols, and 1 symbol after each consecutive SSB symbols and the RSSI symbols, given that *SSB-ToMeasure* and *SS-RSSI-Measurement* are configured, where SSB symbols are indicated by the union set of *SSB-ToMeasure* from all the configured measurement objects on the same serving carrier which can be merged. and RSSI symbols are indicated by *SS-RSSI-Measurement*; + +$K_{\text{layer1\_measurement}}=1.5$ , otherwise. + +If the above-mentioned reference signal configured for L1-RSRP measurement is aperiodic CSI-RS resource, longer cell identification delay would be expected. + +**Table 12.4B.2.5.1-1: Time period for PSS/SSS detection, (Frequency range FR1)** + +| DRX cycle | $T_{\text{PSS/SSS\_sync\_intra}}$ | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------| +| No DRX | $\max(600\text{ms}, 5 \times \text{SMTC period})^{\text{Note 1}}$ | +| NOTE 1: If different SMTC periodicities are configured for different cells, the SMTC period in the requirement is the one used by the cell being identified | | + +**Table 12.4B.2.5.1-2: Time period for PSS/SSS detection, (Frequency range FR2-1)** + +| DRX cycle | $T_{\text{PSS/SSS\_sync\_intra}}$ | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------| +| No DRX | $\max(600\text{ms}, \text{ceil}(M_{\text{pss/sss\_sync\_w/o\_gaps}} \times K_{\text{layer1\_measurement}}) \times \text{SMTC period})^{\text{Note 1}}$ | +| NOTE 1: If different SMTC periodicities are configured for different cells, the SMTC period in the requirement is the one used by the cell being identified | | + +**Table 12.4B.2.5.1-3: Time period for time index detection (FR1)** + +| DRX cycle | $T_{\text{SSB\_time\_index\_intra}}$ | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------| +| No DRX | $\max(120\text{ms}, 3 \times \text{SMTC period})^{\text{Note 1}}$ | +| NOTE 1: If different SMTC periodicities are configured for different cells, the SMTC period in the requirement is the one used by the cell being identified | | + +## 12.4B.2.5.2 Measurement period + +The measurement period for intra-frequency measurements without gaps is as shown in table 12.4B.2.5.2-1, 12.4B.2.5.2-2. + +For FR2-1, a longer measurement period is allowed, if aperiodic CSI-RS resource is measured for L1-RSRP measurement on any FR2-1 serving frequency in the same band and overlapped with any of the SSB symbols and the RSSI symbols, and 1 symbol before each consecutive SSB symbols and the RSSI symbols, and 1 symbol after each consecutive SSB symbols and the RSSI symbols. If *SSB-ToMeasure* or *SS-RSSI-Measurement* is configured, the SSB symbols are indicated by the union set of *SSB-ToMeasure* from all the configured measurement objects on the same band which can be merged and the RSSI symbols are indicated by *SS-RSSI-Measurement*. + +**Table 12.4B.2.5.2-1: Measurement period for intra-frequency measurements without gaps (FR1)** + +| DRX cycle | $T_{\text{SSB\_measurement\_period\_intra}}$ | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------| +| No DRX | $\max(200\text{ms}, 5 \times \text{SMTC period})^{\text{Note 1}}$ | +| NOTE 1: If different SMTC periodicities are configured for different cells, the SMTC period in the requirement is the one used by the cell being identified | | + +**Table 12.4B.2.5.2-2: Measurement period for intra-frequency measurements without gaps (FR2-1)** + +| DRX cycle | $T_{\text{SSB\_measurement\_period\_intra}}$ | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| No DRX | $\max(400\text{ms}, \text{ceil}(\frac{M_{\text{meas\_period\_w/o\_gaps}} \times K_{\text{layer1\_measurement}}}{\text{SMTC period}})^{\text{Note 1}}) \times \text{SMTC period}$ | +| NOTE 1: If different SMTC periodicities are configured for different cells, the SMTC period in the requirement is the one used by the cell being identified | | + +## 12.4B.3 L1-RSRP measurements for Reporting + +### 12.4B.3.1 Introduction + +When configured by the network, the mIAB-MT shall be able to perform L1-RSRP measurements of configured CSI-RS, SSB or CSI-RS and SSB resources for L1-RSRP. The measurements shall be performed for a serving cell, on the resources configured for L1-RSRP measurements within the active BWP. + +The mIAB-MT shall be able to measure all CSI-RS resources and/or SSB resources of the *nzp-CSI-RS-ResourceSet* and/or *csi-SSB-ResourceSet* within the *CSI-ResourceConfig* settings configured for L1-RSRP for the active BWP, provided that the number of resources, including the number of SSB resources of the cell with PCI different from serving cell configured for L1-RSRP measurements in TBA, does not exceed the mIAB-MT capability indicated by *beamManagementSSB-CSI-RS*. + +The mIAB-MT shall report the measurement quantity (*reportQuantity*) and send periodic, semi-persistent or aperiodic reports, according to the *reportConfigType* according to the CSI reporting configuration(s) (*CSI-ReportConfig*) for the active BWP. + +### 12.4B.3.2 Requirements applicability + +The requirements in clause 12.4B.3 apply, provided: + +- The CSI-RS or SSB or CSI-RS and SSB resources configured for L1-RSRP measurements are measurable. + +An SSB resource configured for L1-RSRP shall be considered measurable when for each relevant SSB the following conditions are met: + +- L1-RSRP related side conditions given in clauses TBA and TBA for FR1 and FR2-1, respectively, for a corresponding band, +- SSB\_RP and SSB Ês/Iot according to TBA for a corresponding band. + +A CSI-RS resource configured for L1-RSRP shall be considered measurable when for each relevant CSI-RS the following conditions are met: + +- L1-RSRP related side conditions given in clauses TBA and TBA for FR1 and FR2-1, respectively, for a corresponding band, +- CSI-RS\_RP and CSI-RS Ês/Iot according to TBA for a corresponding band. + +A CSI-RS and SSB resource configured for L1-RSRP shall be considered measurable when the measurable resource conditions are met for both CSI-RS resource and SSB resource. + +Requirements are defined for periodic, semi-persistent and aperiodic resources. + +### 12.4B.3.3 Measurement Reporting Requirements + +The mIAB-MT shall send L1-RSRP reports only for report configurations configured for the active BWP. + +The mIAB-MT shall report the L1-RSRP value as a 7-bit value in the range [-140, -44] dBm with 1dB step size according to clause TBA for FR1 and TBA for FR2-1 if *nrofReportedRS* is configured to one. If *nrofReportedRS* is configured to be larger than one, or if *groupBasedBeamReporting* is enabled, the mIAB-MT shall use differential L1-RSRP based reporting as defined in clause TBA for FR1 and TBA for FR2-1. The differential L1-RSRP is quantized to + +a 4-bit value with 2dB step size. The mapping between the reported L1-RSRP value and the measured quantity is described in TBA. + +#### 12.4B.3.3.1 Periodic Reporting + +Reported L1-RSRP measurements contained in periodic L1-RSRP measurement reports shall meet the requirements in clauses TBA for FR1 and TBA for FR2-1, respectively. + +The mIAB-MT shall only send periodic L1-RSRP measurement reports for an active BWP. + +The mIAB-MT shall transmit the periodic L1-RSRP reporting on PUCCH over the air interface according to the periodicity defined in clause 5.2.1.4 in TS 38.214 [x]. + +#### 12.4B.3.3.2 Semi-Persistent Reporting + +Reported L1-RSRP measurements contained in a Semi-Persistent L1-RSRP measurement report shall meet the requirements in clauses TBA for FR1 and TBA for FR2-1, respectively. This requirement applies for semi-persistent L1-RSRP reports send on PUSCH or PUCCH. + +The mIAB-MT shall only send semi-persistent L1-RSRP measurement reports on PUSCH, if a DCI request has been received. + +The mIAB-MT shall only send semi-persistent L1-RSRP measurement reports on PUCCH, if an activation command [x] has been received. + +The mIAB-MT shall transmit the semi-persistent L1-RSRP reporting on PUSCH or PUCCH over the air interface according to the periodicity defined in clause 5.2.1.4 in TS 38.214 [x]. + +#### 12.4B.3.3.3 Aperiodic Reporting + +Reported L1-RSRP measurements contained in aperiodic triggered, aperiodic triggered periodic and aperiodic triggered semi-persistent L1-RSRP reports shall meet the requirements in clauses TBA for FR1 and TBA for FR2-1, respectively. + +The mIAB-MT shall only send aperiodic L1-RSRP measurement reports, if a DCI trigger has been received. + +After the mIAB-MT receives CSI request in DCI, the mIAB-MT shall transmit the aperiodic L1-RSRP reporting on PUSCH over the air interface at the time specified according to clause 6.1.2.1 in TS 38.214 [x]. + +### 12.4B.3.4 L1-RSRP measurement requirements + +#### 12.4B.3.4.1 SSB based L1-RSRP Reporting + +The mIAB-MT shall be capable of performing L1-RSRP measurements based on the configured SSB resource for L1-RSRP computation, and the mIAB-MT physical layer shall be capable of reporting L1-RSRP measured over the measurement period of $T_{L1-RSRP\_Measurement\_Period\_SSB}$ . + +The value of $T_{L1-RSRP\_Measurement\_Period\_SSB}$ is defined in Table 12.4B.3.4.1-1 for FR1. The value of $T_{L1-RSRP\_Measurement\_Period\_SSB}$ is defined in Table 12.4B.3.4.1-2 for FR2-1, where + +- $M=1$ if higher layer parameter *timeRestrictionForChannelMeasurement* is configured, and $M=3$ otherwise +- $N= 8$ in Table 12.4B.3.4.1-2. + +For FR2-1, + +$P_l =$ + +- $P$ is $P_{L1\_sharing} * P_{sharing\ factor}$ + +Where: + +- $T_{SSB} = \text{ssb-periodicityServingCell}$ of the serving cell +- $T_{SMTCperiod} = \text{the configured SMTC period}$ +- $P_{sharing\ factor} = 1$ , if + +- not overlapped with the SSB symbols indicated by *SSB-ToMeasure* and 1 data symbol before each consecutive SSB symbols indicated by *SSB-ToMeasure* and 1 data symbol after each consecutive SSB symbols indicated by *SSB-ToMeasure*, given that *SSB-ToMeasure* is configured, where the *SSB-ToMeasure* is the union set of *SSB-ToMeasure* from all the configured measurement objects merged on the same serving carrier, and, +- not overlapped by the RSSI symbols indicated by *ss-RSSI-Measurement* and 1 data symbol before each RSSI symbol indicated by *ss-RSSI-Measurement* and 1 data symbol after each RSSI symbol indicated by *ss-RSSI-Measurement*, given that *ss-RSSI-Measurement* is configured. +- $P_{\text{sharing factor}} = 3$ , otherwise. + +If the high layer in TS 38.331 [x] signaling of *smtc2* is configured, $T_{\text{SMTCperiod}}$ corresponds to the value of higher layer parameter *smtc2*; Otherwise $T_{\text{SMTCperiod}}$ corresponds to the value of higher layer parameter *smtc1*. $T_{\text{SMTCperiod}}$ is the shortest SMTC period among all CCs in the same FR2-1 band, provided the SMTC offset of all CCs in FR2-1 have the same offset. + +**Table 12.4B.3.4.1-1: Measurement period $T_{\text{L1-RSRP\_Measurement\_Period\_SSB}}$ for FR1** + +| Configuration | $T_{\text{L1-RSRP\_Measurement\_Period\_SSB}}$ (ms) | +|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| non-DRX | $\max(T_{\text{Report}}, M * T_{\text{SSB}})$ | +| Note 1: | $T_{\text{SSB}}$ = ssb-periodicityServingCell is the periodicity of the SSB-Index configured for L1-RSRP measurement. $T_{\text{DRX}}$ is the DRX cycle length. $T_{\text{Report}}$ is configured periodicity for reporting. | + +**Table 12.4B.3.4.1-2: Measurement period $T_{\text{L1-RSRP\_Measurement\_Period\_SSB}}$ for FR2-1** + +| Configuration | $T_{\text{L1-RSRP\_Measurement\_Period\_SSB}}$ (ms) | +|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| non-DRX | $\max(T_{\text{Report}}, \text{ceil}(M * P * N) * T_{\text{SSB}})$ | +| Note: | $T_{\text{SSB}}$ = ssb-periodicityServingCell is the periodicity of the SSB-Index configured for L1-RSRP measurement. $T_{\text{DRX}}$ is the DRX cycle length. $T_{\text{Report}}$ is configured periodicity for reporting. | + +#### 12.4B.3.4.2 CSI-RS based L1-RSRP Reporting + +The mIAB-MT shall be capable of performing L1-RSRP measurements based on the configured CSI-RS resource for L1-RSRP computation, and the mIAB-MT physical layer shall be capable of reporting L1-RSRP measured over the measurement period of $T_{\text{L1-RSRP\_Measurement\_Period\_CSI-RS}}$ . + +The value of $T_{\text{L1-RSRP\_Measurement\_Period\_CSI-RS}}$ is defined in Table 12.4B.3.4.2-1 for FR1 and in Table 12.4B.3.4.2-2 for FR2-1, where + +- For periodic and semi-persistent CSI-RS resources, $M=1$ if higher layer parameter *timeRestrictionForChannelMeasurement* is configured, and $M=3$ otherwise +- For aperiodic CSI-RS resources $M=1$ +- For periodic CSI-RS resources in a resource set configured with higher layer parameter *repetition* set to OFF, $N=1$ . The requirements apply if *qcl-InfoPeriodicCSI-RS* is configured for all the resources in the resource set and for each resource one RS has QCL-TypeD with + - SSB for L1-RSRP measurement, or + - another CSI-RS in resource set configured with repetition ON. +- For periodic CSI-RS resources in a resource set configured with higher layer parameter *repetition* set to ON, $N=\text{ceil}(\text{maxNumberRxBeam} / N_{\text{res\_per\_set}})$ , where $N_{\text{res\_per\_set}}$ is number of resources in the resource set. The requirements apply provided *qcl-InfoPeriodicCSI-RS* is configured with QCL-TypeD for all resources in the resource set. +- For semi-persistent CSI-RS resources in a resource set configured with higher layer parameter *repetition* set to OFF, $N=1$ . The requirements apply provided TCI state is provided for all resources in the resource set in the MAC CE activating the resource set and for each resource one RS has QCL-TypeD with + +- SSB for L1-RSRP measurement, or +- another CSI-RS in resource set configured with repetition ON. +- For semi-persistent CSI-RS resources in a resource set configured with higher layer parameter *repetition* set to ON, $N = \text{ceil}(\text{maxNumberRxBBeam} / N_{\text{res\_per\_set}})$ , where $N_{\text{res\_per\_set}}$ is number of resources in the resource set. The requirements apply provided TCI state is provided with QCL-TypeD for all resources in the resource set in the MAC CE activating the resource set. +- For aperiodic CSI-RS resources in a resource set configured with higher layer parameter *repetition* set to OFF, $N = 1$ . The requirements apply provided *qcl-info* is configured for all resources in the resource set and for each resource one RS has QCL-TypeD with + - SSB for L1-RSRP measurement, or + - another CSI-RS in resource set configured with repetition ON. +- For aperiodic CSI-RS resources in a resource set configured with higher layer parameter *repetition* set to ON, $N = 1$ . mIAB-MT is not required to meet the accuracy requirements in clause [10.1.19.2] and [10.1.20.2] if number of resources in the resource set is smaller than *maxNumberRxBBeam*. The requirements apply provided *qcl-info* is configured with QCL-TypeD for all resources in the resource set. + +For a mIAB-MT not supporting *concurrentMeasGap-r17* or when concurrent gaps are not configured, + +For FR2-1, + +- $P = 1$ , when CSI-RS is not overlapped with SMTC occasion. +- $P = 2$ , when CSI-RS is partially overlapped with SMTC occasion ( $T_{\text{CSI-RS}} < T_{\text{SMTCperiod}}$ ). +- $P = P_{\text{sharing factor}}$ , when CSI-RS is fully overlapped with SMTC occasion ( $T_{\text{CSI-RS}} = T_{\text{SMTCperiod}}$ ). +- $P = 1$ , for aperiodic CSI-RS + +Where: + +- $P_{\text{sharing factor}} = 1$ , if + - not overlapped with the SSB symbols indicated by *SSB-ToMeasure* and 1 data symbol before each consecutive SSB symbols indicated by *SSB-ToMeasure* and 1 data symbol after each consecutive SSB symbols indicated by *SSB-ToMeasure*, given that *SSB-ToMeasure* is configured, where the *SSB-ToMeasure* is the union set of *SSB-ToMeasure* from all the configured measurement objects merged on the same serving carrier, and, + - not overlapped by the RSSI symbols indicated by *ss-RSSI-Measurement* and 1 data symbol before each RSSI symbol indicated by *ss-RSSI-Measurement* and 1 data symbol after each RSSI symbol indicated by *ss-RSSI-Measurement*, given that *ss-RSSI-Measurement* is configured. +- $P_{\text{sharing factor}} = 3$ , otherwise. + +$T_{\text{SMTCperiod}}$ = the configured SMTC period. + +$T_{\text{CSI-RS}}$ = the periodicity of CSI-RS configured for L1-RSRP measurement + +**Table 12.4B.3.4.2-1: Measurement period $T_{\text{L1-RSRP\_Measurement\_Period\_CSI-RS}}$ for FR1** + +| Configuration | $T_{\text{L1-RSRP\_Measurement\_Period\_CSI-RS}}$ (ms) | +|---------------|---------------------------------------------------------------------------------------------------------------------------------------| +| non-DRX | $\max(T_{\text{Report}}, M * T_{\text{CSI-RS}})$ | +| Note 1: | $T_{\text{CSI-RS}}$ is the periodicity of CSI-RS configured for L1-RSRP measurement. | +| Note 2: | the requirements are applicable provided that the CSI-RS resource configured for L1-RSRP measurement is transmitted with Density = 3. | + +**Table 12.4B.3.4.2-2: Measurement period $T_{L1-RSRP\_Measurement\_Period\_CSI-RS}$ for FR2-1** + +| Configuration | $T_{L1-RSRP\_Measurement\_Period\_CSI-RS}$ (ms) | +|---------------|---------------------------------------------------------------------------------------------------------------------------------------| +| non-DRX | $\max(T_{Report}, \text{ceil}(M*P*N)*T_{CSI-RS})$ | +| Note 1: | $T_{CSI-RS}$ is the periodicity of CSI-RS configured for L1-RSRP measurement. | +| Note 2: | the requirements are applicable provided that the CSI-RS resource configured for L1-RSRP measurement is transmitted with Density = 3. | + +## Annex A (normative): IAB-MT Reference measurement channels + +### A.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-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 for FR2-1 OTA reference sensitivity level, OTA ACS, OTA in-band blocking, and OTA out-of-band blocking. + +**Table A1-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 | +| NOTE 1: DL-DMRS-config-type = 1 with DL-DMRS-max-len = 1, DL-DMRS-add-pos = pos2 with $l_0 = 2$ , $l = 6$ and 9 as per Table 7.4.1.1.2-3 of TS 38.211 [3]. | | | | | +| NOTE 2: MCS index 4 and target coding rate = 308/1024 are adopted to calculate payload size for receiver sensitivity | | | | | + +**Table A1-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 | +| 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 [3]. | | | | +| 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 to table A.2.1-3 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-4 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 [8]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [9]. + +**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 [8]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [9]. + +**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 [8]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [9]. + +**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 *l0 = 0* as per Table 6.4.1.1.3-3 of TS 38.211 [8]. + +NOTE 2: Code block size including CRC (bits) equals to *K'* in sub-clause 5.2.2 of TS 38.212 [9]. + +**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 *l0 = 0* as per Table 6.4.1.1.3-3 of TS 38.211 [8]. + +NOTE 2: Code block size including CRC (bits) equals to *K'* in sub-clause 5.2.2 of TS 38.212 [9]. + +**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 *l0 = 0* as per Table 6.4.1.1.3-3 of TS 38.211 [8]. + +NOTE 2: Code block size including CRC (bits) equals to *K'* in sub-clause 5.2.2 of TS 38.212 [9]. + +**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 [8]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [9]. + +**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 [8]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [9]. + +**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 [8]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [9]. + +## 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 [8]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [9]. + +**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 [8]. | | | | | | +| NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [9]. | | | | | | + +### 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.2.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 [8]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [9]. + +**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 [8]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [9]. + +**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 *l0 = 0* as per Table 6.4.1.1.3-3 of TS 38.211 [8]. + +NOTE 2: Code block size including CRC (bits) equals to *K'* in sub-clause 5.2.2 of TS 38.212 [9]. + +**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 *l0 = 0* as per Table 6.4.1.1.3-3 of TS 38.211 [8]. + +NOTE 2: Code block size including CRC (bits) equals to *K'* in sub-clause 5.2.2 of TS 38.212 [9]. + +**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 *l0* = 0 and *l* = 8 as per Table 6.4.1.1.3-3 of TS 38.211 [8]. + +NOTE 2: Code block size including CRC (bits) equals to *K'* in sub-clause 5.2.2 of TS 38.212 [9]. + +**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 *l0* = 0 and *l* = 8 as per Table 6.4.1.1.3-3 of TS 38.211 [8]. + +NOTE 2: Code block size including CRC (bits) equals to *K'* in sub-clause 5.2.2 of TS 38.212 [9]. + +## 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 [8]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [9]. + +**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 | G-FR2-A.2.4-1 | G-FR2-A.2.4-2 | G-FR2-A.2.4-3 | G-FR2-A.2.4-4 | G-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 [8]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [9]. + +**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 | G-FR2-A.2.4-6 | G-FR2-A.2.4-7 | G-FR2-A.2.4-8 | G-FR2-A.2.4-9 | G-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 [8]. | | | | | | +| NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [9]. | | | | | | + +## 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: FRC parameters for FR1 PDSCH performance requirements, 1-4 transmission layers, 16QAM** + +| Parameter | Unit | Value | | | +|-------------------------------------|------|---------------|---------------|---------------| +| | | M-FR1-A.3.1-1 | M-FR1-A.3.1-2 | M-FR1-A.3.1-3 | +| Reference channel | | | | | +| Channel bandwidth | MHz | 40 | 40 | 40 | +| Subcarrier spacing | kHz | 30 | 30 | 30 | +| Allocated resource blocks | PRBs | 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 | | 0.48 | 0.48 | 0.48 | +| 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 | | 26632 | 73776 | 98376 | +| Transport block CRC per Slot | | 24 | 24 | 24 | +| Number of Code Blocks per Slot | | 4 | 9 | 12 | +| Binary Channel Bits Per Slot | | 55968 | 152640 | 203520 | + +**Table A.3.1-2: FRC parameters for FR2-1 PDSCH performance requirements, 1-2 transmission layers, 16QAM** + +| Parameter | Unit | Value | | | +|-------------------------------------|------|---------------|---------------|---------------| +| | | M-FR2-A.3.1-1 | M-FR2-A.3.1-2 | M-FR2-A.3.1-3 | +| Reference channel | | | | | +| Channel bandwidth | MHz | 50 | 100 | 100 | +| Subcarrier spacing | kHz | 60 | 120 | 120 | +| Allocated resource blocks | PRBs | 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 | | 0.48 | 0.48 | 0.48 | +| Number of MIMO layers | | 2 | 1 | 2 | +| Number of DMRS REs | | 12 | 12 | 12 | +| Overhead for TBS determination | | 6 | 6 | 6 | +| Information Bit Payload per Slot | | 34816 | 17424 | 34816 | +| Transport block CRC per Slot | | 24 | 24 | 24 | +| Number of Code Blocks per Slot | | 5 | 3 | 5 | +| Binary Channel Bits Per Slot | | 73128 | 36564 | 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: FRC parameters for FR1 PDSCH performance requirements, 2 transmission layers, 64QAM** + +| Parameter | Unit | Value | +|-------------------------------------|------|---------------| +| Reference channel | | M-FR1-A.3.2-1 | +| Channel bandwidth | MHz | 40 | +| Subcarrier spacing | kHz | 30 | +| Allocated resource blocks | PRBs | 106 | +| Number of consecutive PDSCH symbols | | 12 | +| MCS table | | 64QAM | +| MCS index | | 19 | +| Modulation | | 64QAM | +| Target Coding Rate | | 0.51 | +| Number of MIMO layers | | 2 | +| Number of DMRS REs | | 12 | +| Overhead for TBS determination | | 0 | +| Information Bit Payload per Slot | | 83976 | +| Transport block CRC per Slot | | 24 | +| Number of Code Blocks per Slot | | 10 | +| Binary Channel Bits Per Slot | | 167904 | + +**Table A.3.2-2: FRC parameters for FR2-1 PDSCH performance requirements, 1-2 transmission layers, 64QAM** + +| Parameter | Unit | Value | | +|-------------------------------------|------|---------------|---------------| +| 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 | PRBs | 66 | 66 | +| Number of consecutive PDSCH symbols | | 13 | 13 | +| MCS table | | 64QAM | 64QAM | +| MCS index | | 18 | 17 | +| Modulation | | 64QAM | 64QAM | +| Target Coding Rate | | 0.46 | 0.43 | +| Number of MIMO layers | | 1 | 2 | +| Number of DMRS REs | | 12 | 12 | +| Overhead for TBS determination | | 6 | 6 | +| Information Bit Payload per Slot | | 25104 | 47112 | +| Transport block CRC per Slot | | 24 | 24 | +| Number of Code Blocks per Slot | | 3 | 6 | +| Binary Channel Bits Per Slot | | 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: FRC parameters for FR1 PDSCH performance requirements, 1 transmission layer, 256QAM** + +| Parameter | Unit | Value | +|-------------------------------------|------|---------------| +| Reference channel | | M-FR1-A.3.3-1 | +| Channel bandwidth | MHz | 40 | +| Subcarrier spacing | kHz | 30 | +| Allocated resource blocks | PRBs | 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 | | 92200 | +| Transport block CRC per Slot | | 24 | +| Number of Code Blocks per Slot | | 11 | +| Binary Channel Bits Per Slot | | 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: FR1 PDCCH Reference Channels** + +| Parameter | Unit | Value | | | +|-------------------------------------|------|---------------|---------------|---------------| +| 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: FR2-1 PDCCH Reference Channels** + +| Parameter | Unit | Value | | | +|-------------------------------------|------|---------------|---------------|---------------| +| | | M-FR2-A.3.4-1 | M-FR2-A.3.4-2 | M-FR2-A.3.4-3 | +| Reference channel | | | | | +| 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 performance + +This clause defines the DL signal applicable to the reporting of channel status information. + +Tables in this clause specifies the mapping of CQI index to Information Bit payload, which complies with the CQI definition specified in clause 5.2.2.1 of TS 38.214 [11] and with MCS definition specified in clause 5.1.3 of TS 38.214 [11]. + +**Table A.3.5-1: Fixed Reference Channels for FR1 CSI 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 | | 57376 | 114776 | 172176 | 229576 | +| 11 | 5.1152 | 19 | 256QAM | 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 FR2-1 CSI 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-3: PDSCH Reference Channel for FR1 PMI reporting requirements** + +| Parameter | Unit | Value | | +|-------------------------------------|------|---------------|---------------| +| 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 | PRBs | 106 | 106 | +| Number of consecutive PDSCH symbols | | 12 | 12 | +| MCS table | | 64QAM | 64QAM | +| MCS index | | 13 | 13 | +| Modulation | | 16QAM | 16QAM | +| Target Coding Rate | | 0.48 | 0.48 | +| Number of MIMO layers | | 1 | 2 | +| Number of DMRS REs (Note 3) | | 24 | 24 | +| Overhead for TBS determination | | 0 | 0 | +| Information Bit Payload per Slot | Bits | 24576 | 49176 | +| For Slot i = 20 | | | | +| Transport block CRC per Slot | Bits | 24 | 24 | +| Number of Code Blocks per Slot | CBs | 3 | 6 | +| Binary Channel Bits Per Slot | Bits | 50880 | 101760 | + +**Table A.3.5-4: PDSCH Reference Channel for FR2-1 PMI reporting requirements** + +| Parameter | Unit | Value | +|-------------------------------------|------|---------------| +| Reference channel | | M-FR2-A.3.5-3 | +| Channel bandwidth | MHz | 100 | +| Subcarrier spacing | kHz | 120 | +| Allocated resource blocks | PRBs | 66 | +| Number of consecutive PDSCH symbols | | 12 | +| MCS table | | 64QAM | +| MCS index | | 13 | +| Modulation | | 16QAM | +| Target Coding Rate | | 0.48 | +| Number of MIMO layers | | 1 | +| Number of DMRS REs (Note 3) | | 24 | +| Overhead for TBS determination | | 6 | +| Information Bit Payload per Slot | | 14344 | +| Transport block CRC per Slot | | 24 | +| Number of Code Blocks per Slot | | 2 | +| Binary Channel Bits Per Slot | | 30360 | + +--- + +## Annex B (normative): IAB-DU Error Vector Magnitude (FR1) + +The Annex B in TS 38.104 [2] applies to FR1 IAB-DU. + +--- + +## Annex C (normative): IAB-DU Error Vector Magnitude (FR2-1) + +The Annex C in TS 38.104 [2] applies to FR2-1 IAB-DU. + +--- + +## Annex D (normative): IAB-MT Error Vector Magnitude (FR1) + +### D.0 General + +FR1 IAB-MT EVM can be determined by the process according to + +1) Annex E in TS 38.521-1 [23]. Only CP-OFDM waveform of PUSCH is measured for IAB-MT. + +Or + +2) Annex D.1 to Annex D.7. + +### D.1 Reference point for measurement + +The Annex B.1 in TS 38.104 [2] applies to FR1 IAB-MT. + +### D.2 Basic unit of measurement + +The Annex B.2 in TS 38.104 [2] applies to FR1 IAB-MT. + +## D.3 Modified signal under test + +The Annex B.3 in TS 38.104 [2] applies to FR1 IAB-MT. + +## D.4 Estimation of frequency offset + +The Annex B.4 in TS 38.104 [2] applies to FR1 IAB-MT. + +## D.5 Estimation of time offset + +The Annex B.5 in TS 38.104 [2] applies to FR1 IAB-MT. + +## D.6 Estimation of TX chain amplitude and frequency response parameters + +The Annex B.6 in TS 38.104 [2] applies to FR1 IAB-MT. + +## D.7 Averaged EVM + +EVM is averaged over all allocated uplink resource blocks with the considered modulation scheme in the frequency domain, and a minimum of $N_{\text{slots}}$ slots where $N_{\text{slots}}$ is the number of slots in a 10 ms measurement interval. + +For TDD, let $N_{\text{slots}}$ be the number of slots with uplink symbols within a 10 ms measurement interval, the averaging in the time domain can be calculated from $N_{\text{slots}}$ slots of different 10 ms measurement intervals and should have a minimum of $N_{\text{slots}}$ slots averaging length where $N_{\text{slots}}$ is the number of slots in a 10 ms measurement interval. + +- $\text{EVM}_{\text{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_{\text{RB}}$ is the number of resource blocks with the considered modulation scheme in slot $i$ . +- The $\text{EVM}_{\text{RMS}}$ is calculated, using the maximum of $\text{EVM}_{\text{RMS}}$ at the window $W$ extremities. Thus $\text{EVM}_{\text{RMS}}$ is calculated using $\text{EVM}_{\text{RMS}}$ and $\text{EVM}_{\text{RMS}}$ calculated using $(l$ and $h)$ , low and high; where low is the timing $t_{\text{low}}$ and high is the timing $t_{\text{high}}$ ). +- In order to unite at least $N_{\text{slots}}$ slots, consider the minimum integer number of 10 ms measurement intervals, where $N_{\text{slots}}$ is determined by. + +and $N_{\text{slots}}$ for 15 kHz SCS, $N_{\text{slots}}$ for 30 kHz SCS and $N_{\text{slots}}$ for 60 kHz SCS normal CP. + +- Unite by RMS. + +--- + +## Annex E (normative): IAB-MT Error Vector Magnitude (FR2) + +### E.0 General + +FR2-1 IAB-MT EVM can be determined by the process according to + +- 1) Annex E in TS 38.521-2 [24]. Only CP-OFDM waveform of PUSCH is measured for IAB-MT. + +Or + +2) Annex E.1 to Annex E.7. + +## E.1 Reference point for measurement + +The Annex C.1 in TS 38.104 [2] applies to FR2-1 IAB-MT. + +## E.2 Basic unit of measurement + +The Annex C.2 in TS 38.104 [2] applies to FR2-1 IAB-MT. + +## E.3 Modified signal under test + +The Annex C.3 in TS 38.104 [2] applies to FR2-1 IAB-MT. + +## E.4 Estimation of frequency offset + +The Annex C.4 in TS 38.104 [2] applies to FR2-1 IAB-MT. + +## E.5 Estimation of time offset + +The Annex C.5 in TS 38.104 [2] applies to FR2-1 IAB-MT. + +## E.6 Estimation of TX chain amplitude and frequency response parameters + +The Annex C.6 in TS 38.104 [2] applies to FR2-1 IAB-MT. + +## E.7 Averaged EVM + +EVM is averaged over all allocated uplink resource blocks with the considered modulation scheme in the frequency domain, and a minimum of $N_{\text{slots}}$ slots where $N_{\text{slots}}$ is the number of slots in a 10 ms measurement interval. + +For TDD, let $N_{\text{slots}}$ be the number of slots with uplink symbols within a 10 ms measurement interval, the averaging in the time domain can be calculated from $N_{\text{slots}}$ slots of different 10 ms measurement intervals and should have a minimum of $N_{\text{slots}}$ slots averaging length where $N_{\text{slots}}$ is the number of slots in a 10 ms measurement interval. + +- $\text{EVM}_{\text{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_{\text{RB}}$ is the number of resource blocks with the considered modulation scheme in slot $i$ . +- The $\text{EVM}_{i,j}$ is calculated, using the maximum of $\text{EVM}_{i,j,k}$ at the window $W$ extremities. Thus $\text{EVM}_{i,j}$ is calculated using $\text{EVM}_{i,j,k}$ and $\text{EVM}_{i,j,k-1}$ ( $l$ and $h$ , low and high; where low is the timing $k$ and high is the timing $k-1$ ). +- In order to unite at least $N_{\text{slots}}$ slots, consider the minimum integer number of 10 ms measurement intervals, where $N_{\text{intervals}}$ is determined by: + - and $N_{\text{slots}}$ for 60 kHz SCS and $N_{\text{slots}}$ for 120 kHz SCS. +- Unite by RMS. + +## Annex F (normative): + +### F.1 Characteristics of the interfering signals for IAB-DU + +The Annex D in in TS 38.104 [2] apply to FR1 IAB-DU. + +### F.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 TS38.211 [8]. Mapping of PDSCH modulation to receiver requirement are specified in table F-1.* + +**Table F-1: Modulation of the interfering signal** + +| Receiver requirement | Modulation | +|-------------------------------------------------------|------------| +| Adjacent channel selectivity and narrow-band blocking | QPSK | +| General blocking | QPSK | +| Receiver intermodulation | QPSK | + +## Annex G (normative): IAB-MT RRM Testing + +The test cases defined in this Annex are to verify the minimum requirements defined in clause 12. The conducted tests are performed for IAB type 1-H, and the over the air (OTA) tests are performed for IAB type 2-O, where the conducted and radiated reference points and the IAB type are defined in clause 4.3. For the test cases for IAB-MT, the DU part is disabled during the testing. The test cases apply for Local-area IAB-MT classes, where the IAB-MT classes are defined in clause 4.4. + +The test configurations and procedures are defined in following clauses and in each test cases. The test requirements are derived using the corresponding configuration parameters as example. The actual IAB-MT RRM test can be conducted by any set of configuration parameters which are left to implementations and manufacturer declarations and the corresponding test requirements shall be based on the actual configuration parameters used in the test. For example, TDD pattern and related configurations shall be configurable and left for implementation and declaration including: + +- DL/UL scheduling related configuration +- PRACH configuration +- SRS configuration +- SSB configuration +- CSI-RS configuration +- BWP configuration +- SMTC configuration +- TCI state configuration +- Antenna configuration +- AoA configuration + +## G.1 IAB-MT RRM test configurations + +### G.1.1 Reference measurement channels + +#### G.1.1.1 PDSCH + +##### G.1.1.1.1 TDD + +**Table G.1.1.1.1-1: PDSCH Reference Measurement Channels for SCS=15kHz** + +| Parameter | Unit | Value | | | | | | | +|-------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|--|--|--|--|--|--| +| Reference channel | | SR.1.1
TDD | | | | | | | +| Channel bandwidth | MHz | 10 | | | | | | | +| Number of transmitter antennas | | 1 | | | | | | | +| Allocated resource blocks for PDSCH Note 1 | | 24 | | | | | | | +| Allocated slots per Radio Frame | | | | | | | | | +| Radio frame containing SSB | slots | Note 5 | | | | | | | +| Radio frame not containing SSB | slots | 4 | | | | | | | +| MCS table | | 64QAM | | | | | | | +| MCS index | | 4 | | | | | | | +| Modulation | | QPSK | | | | | | | +| Target Coding Rate | | 1/3 | | | | | | | +| Number of control symbols | | 2 | | | | | | | +| PDSCH mapping type | | Type A | | | | | | | +| Information Bit Payload | | | | | | | | | +| For slots with RMSI Note 2 | bits | 1608 | | | | | | | +| For slots without RMSI | bits | 1864 | | | | | | | +| Number of Code Blocks per slot | | 1 | | | | | | | +| Binary Channel Bits Per slot | | | | | | | | | +| For slots with RMSI Note 2, Note 4 | bits | 5184 | | | | | | | +| For slots without RMSI Note 6 | bits | 6048 | | | | | | | +| Note 1: | Allocated outside the SMTC duration in time and in resource blocks which do not overlap with the resource blocks allocated for SS/PBCH block. | | | | | | | | +| Note 2: | PDSCH is scheduled on the slots with RMSI. | | | | | | | | +| Note 3: | If necessary the information bit payload size can be adjusted to facilitate the test implementation. The payload sizes are defined in TS 38.213 [3]. | | | | | | | | +| Note 4: | Derived based on the PDSCH DMRS assumption: dmrs-TypeA-Position=2, dmrs-Type=1, dmrs-AdditionalPositions=2, maxLength=1, Antenna port index: 1000, and Number of PDSCH DMRS CDM group(s) without data: 2. | | | | | | | | +| Note 5: | PDSCH is not scheduled in slots containing SSB according to the SSB configuration used in the test. SSB configurations are defined in clause G.1.5. | | | | | | | | +| Note 6: | Derived based on the PDSCH DMRS assumption: dmrs-TypeA-Position=2, dmrs-Type=1, dmrs-AdditionalPositions=2, maxLength=1, Antenna port index: 1000, and Number of PDSCH DMRS CDM group(s) without data: 1. | | | | | | | | + +**Table G.1.1.1.1-2: PDSCH Reference Measurement Channels for SCS=30kHz** + +| Parameter | Unit | Value | | | | | | | +|-------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|--|--|--|--|--|--| +| Reference channel | | SR.2.1
TDD | | | | | | | +| Channel bandwidth | MHz | 40 | | | | | | | +| Number of transmitter antennas | | 1 | | | | | | | +| Allocated resource blocks for PDSCH Note 1 | | 24 | | | | | | | +| Allocated slots per Radio Frame | | | | | | | | | +| Radio frame containing SSB | slots | Note 5 | | | | | | | +| Radio frame not containing SSB | slots | 10 | | | | | | | +| MCS table | | 64QAM | | | | | | | +| MCS index | | 4 | | | | | | | +| Modulation | | QPSK | | | | | | | +| Target Coding Rate | | 1/3 | | | | | | | +| Number of control symbols | | 2 | | | | | | | +| PDSCH mapping type | | Type A | | | | | | | +| Information Bit Payload | | | | | | | | | +| For slots with RMSI Note 2 | bits | 1608 | | | | | | | +| For slots without RMSI | bits | 1864 | | | | | | | +| Number of Code Blocks per slot | | 1 | | | | | | | +| Binary Channel Bits Per slot | | | | | | | | | +| For slots with RMSI Note 2, Note 4 | bits | 5184 | | | | | | | +| For slots without RMSI Note 6 | bits | 6048 | | | | | | | +| Note 1: | Allocated outside the SMTC duration in time and in resource blocks which do not overlap with the resource blocks allocated for SS/PBCH block. | | | | | | | | +| Note 2: | PDSCH is scheduled on the slots with RMSI. | | | | | | | | +| Note 3: | If necessary the information bit payload size can be adjusted to facilitate the test implementation. The payload sizes are defined in TS 38.213 [3]. | | | | | | | | +| Note 4: | Derived based on the PDSCH DMRS assumption: dmrs-TypeA-Position=2, dmrs-Type=1, dmrs-AdditionalPositions=2, maxLength=1, Antenna port index: 1000, and Number of PDSCH DMRS CDM group(s) without data: 2. | | | | | | | | +| Note 5: | PDSCH is not scheduled in slots containing SSB according to the SSB configuration used in the test. SSB configurations are defined in clause G.1.5. | | | | | | | | +| Note 6: | Derived based on the PDSCH DMRS assumption: dmrs-TypeA-Position=2, dmrs-Type=1, dmrs-AdditionalPositions=2, maxLength=1, Antenna port index: 1000, and Number of PDSCH DMRS CDM group(s) without data: 1. | | | | | | | | + +**Table G.1.1.1.1-3: PDSCH Reference Measurement Channels for SCS=120kHz** + +| Parameter | Unit | Value | | | | | | | +|-------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|--|--|--|--|--|--| +| Reference channel | | SR.3.1
TDD | | | | | | | +| Channel bandwidth | MHz | 100 | | | | | | | +| Number of transmitter antennas | | 1 | | | | | | | +| Allocated resource blocks for PDSCH Note 1 | | 24 | | | | | | | +| Allocated slots per Radio Frame | | | | | | | | | +| Radio frame containing SSB | slots | Note 5 | | | | | | | +| Radio frame not containing SSB | slots | 48 | | | | | | | +| MCS table | | 64QAM | | | | | | | +| MCS index | | 4 | | | | | | | +| Modulation | | QPSK | | | | | | | +| Target Coding Rate | | 1/3 | | | | | | | +| Number of control symbols | | 2 | | | | | | | +| PDSCH mapping type | | Type A | | | | | | | +| Information Bit Payload | | | | | | | | | +| For slots with RMSI Note 2 | bits | 1608 | | | | | | | +| For slots without RMSI | bits | 1864 | | | | | | | +| Number of Code Blocks per slot | | 1 | | | | | | | +| Binary Channel Bits Per slot | | | | | | | | | +| For slots with RMSI Note 2, Note 4 | bits | 5184 | | | | | | | +| For slots without RMSI Note 6 | bits | 6048 | | | | | | | +| Note 1: | Allocated outside the SMTC duration in time and in resource blocks which do not overlap with the resource blocks allocated for SS/PBCH block | | | | | | | | +| Note 2: | PDSCH is scheduled on the slots with RMSI. | | | | | | | | +| Note 3: | If necessary the information bit payload size can be adjusted to facilitate the test implementation. The payload sizes are defined in TS 38.213 [3]. | | | | | | | | +| Note 4: | Derived based on the PDSCH DMRS assumption: dmrs-TypeA-Position=2, dmrs-Type=1, dmrs-AdditionalPositions=2, maxLength=1, Antenna port index: 1000, and Number of PDSCH DMRS CDM group(s) without data: 2. | | | | | | | | +| Note 5: | PDSCH is not scheduled in slots containing SSB according to the SSB configuration used in the test. SSB configurations are defined in clause G.1.5. | | | | | | | | +| Note 6: | Derived based on the PDSCH DMRS assumption: dmrs-TypeA-Position=2, dmrs-Type=1, dmrs-AdditionalPositions=2, maxLength=1, Antenna port index: 1000, and Number of PDSCH DMRS CDM group(s) without data: 1. | | | | | | | | + +## G.1.1.2 CORESET for RMSI scheduling + +### G.1.1.2.1 TDD + +**Table G.1.1.2.1-1: RMSI CORESET Reference Channel for TDD with SCS=15KHz** + +| Parameter | Unit | Value | | | | | | | +|--------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|--|--|--|--|--|--| +| Reference channel | | CR.1.1
TDD | | | | | | | +| Channel bandwidth | MHz | 10 | | | | | | | +| Subcarrier spacing | kHz | 15 | | | | | | | +| Allocated resource blocks for RMSI CORESET Note 7 | | 24 | | | | | | | +| SSB and RMSI CORESET multiplexing configuration Note 7 | | Pattern 1 | | | | | | | +| Offset between SSB and RMSI CORESET Note 3, 7 | RB | 0 (Note 8) | | | | | | | +| Configuration of PDCCH monitoring occasions for RMSI CORESET Note 4 | | Index 4 | | | | | | | +| Number of transmitter antennas | | 1 | | | | | | | +| Duration of RMSI CORESET Note 7 | symbols | 2 | | | | | | | +| DCI Format Note 1 | | Note 2 | | | | | | | +| Aggregation level | CCE | 8 | | | | | | | +| DMRS precoder granularity | | 6 | | | | | | | +| REG bundle size | | 6 | | | | | | | +| Mapping from REG to CCE | | Distributed | | | | | | | +| Cell ID | | Note 5 | | | | | | | +| Payload (without CRC) | bits | Note 6 | | | | | | | +| Note 1: | DCI formats are defined in TS 38.212. | | | | | | | | +| Note 2: | DCI format shall depend upon the test configuration. | | | | | | | | +| Note 3: | The offset is defined with respect to the subcarrier spacing of the CORESET from the smallest RB index of RMSI CORESET to the smallest RB index of the common RB overlapping with the first RB of the SS/PBCH block. | | | | | | | | +| Note 4: | The configuration of PDCCH monitoring occasions for RMSI CORESET is defined in Table 13-11 in TS 38.213 [3]. | | | | | | | | +| Note 5: | Cell ID shall depend upon the test configuration. | | | | | | | | +| Note 6: | Payload size shall depend upon the test configuration. | | | | | | | | +| Note 7: | The configuration of set of resource blocks and slot symbols of control resource set for Type0-PDCCH search space corresponds to index 0 in Table 13-1 in TS 38.213 [3]. | | | | | | | | +| Note 8: | Other values can be used to align with GSCN [13] as long as SSB does not overlap the RMC. | | | | | | | | + +**Table G.1.1.2.1-2: RMSI CORESET Reference Channel for TDD with SCS=30KHz** + +| Parameter | Unit | Value | | | | | | | +|--------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|--|--|--|--|--|--| +| Reference channel | | CR.2.1
TDD | | | | | | | +| Channel bandwidth | MHz | 40 | | | | | | | +| Subcarrier spacing | kHz | 30 | | | | | | | +| Allocated resource blocks for RMSI CORESET Note 7 | | 24 | | | | | | | +| SSB and RMSI CORESET multiplexing configuration Note 7 | | Pattern 1 | | | | | | | +| Offset between SSB and RMSI CORESET Note 3, 7 | RB | 0 (Note 8) | | | | | | | +| Configuration of PDCCH monitoring occasions for RMSI CORESET Note 4 | | Index 4 | | | | | | | +| Number of transmitter antennas | | 1 | | | | | | | +| Duration of RMSI CORESET Note 7 | symbols | 2 | | | | | | | +| DCI Format Note 1 | | Note 2 | | | | | | | +| Aggregation level | CCE | 8 | | | | | | | +| DMRS precoder granularity | | 6 | | | | | | | +| REG bundle size | | 6 | | | | | | | +| Mapping from REG to CCE | | Distributed | | | | | | | +| Cell ID | | Note 5 | | | | | | | +| Payload (without CRC) | bits | Note 6 | | | | | | | +| Note 1: | DCI formats are defined in TS 38.212. | | | | | | | | +| Note 2: | DCI format shall depend upon the test configuration. | | | | | | | | +| Note 3: | The offset is defined with respect to the subcarrier spacing of the CORESET from the smallest RB index of RMSI CORESET to the smallest RB index of the common RB overlapping with the first RB of the SS/PBCH block. | | | | | | | | +| Note 4: | The configuration of PDCCH monitoring occasions for RMSI CORESET is defined in Table 13-11 in TS 38.213 [3]. | | | | | | | | +| Note 5: | Cell ID shall depend upon the test configuration. | | | | | | | | +| Note 6: | Payload size shall depend upon the test configuration. | | | | | | | | +| Note 7: | The configuration of set of resource blocks and slot symbols of control resource set for Type0-PDCCH search space corresponds to index 0 in Table 13-6 in TS 38.213 [3]. | | | | | | | | +| Note 8: | Other values can be used to align with GSCN [13] as long as SSB does not overlap the RMC. | | | | | | | | + +**Table G.1.1.2.1-3: RMSI CORESET Reference Channel for TDD with SCS=120KHz** + +| Parameter | Unit | Value | | | | | | | +|--------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|--|--|--|--|--|--| +| Reference channel | | CR.3.1
TDD | | | | | | | +| Channel bandwidth | MHz | 100 | | | | | | | +| Subcarrier spacing | kHz | 120 | | | | | | | +| Allocated resource blocks for RMSI CORESET Note 7 | | 24 | | | | | | | +| SSB and RMSI CORESET multiplexing configuration Note 7 | | Pattern 1 | | | | | | | +| Offset between SSB and RMSI CORESET Note 3, 7 | RB | 0 (Note 8) | | | | | | | +| Configuration of PDCCH monitoring occasions for RMSI CORESET Note 4 | | Index 4 | | | | | | | +| Number of transmitter antennas | | 1 | | | | | | | +| Duration of RMSI CORESET Note 7 | symbols | 2 | | | | | | | +| DCI Format Note 1 | | Note 2 | | | | | | | +| Aggregation level | CCE | 8 | | | | | | | +| DMRS precoder granularity | | 6 | | | | | | | +| REG bundle size | | 6 | | | | | | | +| Mapping from REG to CCE | | Distributed | | | | | | | +| Cell ID | | Note 5 | | | | | | | +| Payload (without CRC) | bits | Note 6 | | | | | | | +| Note 1: | DCI formats are defined in TS 38.212. | | | | | | | | +| Note 2: | DCI format shall depend upon the test configuration. | | | | | | | | +| Note 3: | The offset is defined with respect to the subcarrier spacing of the CORESET from the smallest RB index of RMSI CORESET to the smallest RB index of the common RB overlapping with the first RB of the SS/PBCH block. | | | | | | | | +| Note 4: | The configuration of PDCCH monitoring occasions for RMSI CORESET is defined in Table 13-12 in TS 38.213 [3]. | | | | | | | | +| Note 5: | Cell ID shall depend upon the test configuration. | | | | | | | | +| Note 6: | Payload size shall depend upon the test configuration. | | | | | | | | +| Note 7: | The configuration of set of resource blocks and slot symbols of control resource set for Type0-PDCCH search space corresponds to index 0 in Table 13-8 in TS 38.213 [3]. | | | | | | | | +| Note 8: | Other values can be used to align with GSCN [13] as long as SSB does not overlap the RMC. | | | | | | | | + +### G.1.1.3 CORESET for RMC scheduling + +#### G.1.1.3.1 TDD + +**Table G.1.1.3.1-1: Control Channel RMC for TDD with SCS=15KHz** + +| Parameter | Unit | Value | | | | | | | +|---------------------------------------------------------|---------|-------------------------|-------------------------|--|--|--|--|--| +| Reference channel | | CCR.1.1
TDD | CCR.1.2
TDD | | | | | | +| Subcarrier spacing | kHz | 15 | 15 | | | | | | +| Allocated resource blocks for CORESET Note 3 | | 24 | 18 | | | | | | +| Number of transmitter antennas | | 1 | 1 | | | | | | +| Duration of CORESET | symbols | 2 | 2 | | | | | | +| REG bundle size | | 6 | 6 | | | | | | +| DMRS precoder granularity | | Same as REG bundle size | Same as REG bundle size | | | | | | +| CCE to REG mapping | | Interleaved | Interleaved | | | | | | +| Interleave n_shift | | 0 | 0 | | | | | | +| Interleave size | | 2 | 2 | | | | | | +| Beamforming Pre-Coder | | N/A | N/A | | | | | | +| Aggregation level | CCE | 8 | 4 | | | | | | +| DCI formats | | Note 1 | Note 1 | | | | | | +| Payload size (without CRC) | bits | Note 2 | Note 2 | | | | | | + +Note 1: DCI format shall depend upon the test configuration. + +Note 2: Payload size shall depend upon the test configuration + +Note 3: Allocated in the resource blocks where the associated RMC is scheduled. + +**Table G.1.1.3.1-2: Control Channel RMC for TDD with SCS=30KHz** + +| Parameter | Unit | Value | | | | | | | +|---------------------------------------------------------|---------|-------------------------|--|--|--|--|--|--| +| Reference channel | | CCR.2.1
TDD | | | | | | | +| Subcarrier spacing | kHz | 30 | | | | | | | +| Allocated resource blocks for CORESET Note 3 | | 24 | | | | | | | +| Number of transmitter antennas | | 1 | | | | | | | +| Duration of CORESET | symbols | 2 | | | | | | | +| REG bundle size | | 6 | | | | | | | +| DMRS precoder granularity | | Same as REG bundle size | | | | | | | +| CCE to REG mapping | | Interleaved | | | | | | | +| Interleave n_shift | | 0 | | | | | | | +| Interleave size | | 2 | | | | | | | +| Beamforming Pre-Coder | | N/A | | | | | | | +| Aggregation level | CCE | 8 | | | | | | | +| DCI formats | | Note 1 | | | | | | | +| Payload size (without CRC) | bits | Note 2 | | | | | | | + +Note 1: DCI format shall depend upon the test configuration. + +Note 2: Payload size shall depend upon the test configuration. + +Note 3: Allocated in the same resource blocks where the associated RMC is scheduled. + +**Table G.1.1.3.1-3: Control Channel RMC for TDD with SCS=120KHz** + +| Parameter | Unit | Value | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----------------------------------|----------------------------------|----------------------------------|--|--|--|--| +| Reference channel | | CCR.3.1
TDD | CCR.3.2
TDD | CCR.3.3
TDD | | | | | +| Subcarrier spacing | kHz | 120 | 120 | 120 | | | | | +| Allocated resource blocks for CORESET Note 3 | | 24 | 24 | 24 | | | | | +| Number of transmitter antennas | | 1 | 1 | 1 | | | | | +| monitoringSlotPeriodicityAndOffset | | sl160
0 | sl160
0 | sl160
80 | | | | | +| monitoringSymbolsWithinSlot | | 1100000
0000000 | 0011000
0000000 | 1100000
0000000 | | | | | +| Duration of CORESET | slot | 1 | 1 | 1 | | | | | +| REG bundle size | | 6 | 6 | 6 | | | | | +| DMRS precoder granularity | | Same as
REG
bundle
size | Same as
REG
bundle
size | Same as
REG
bundle
size | | | | | +| CCE to REG mapping | | Interleaved | Interleaved | Interleaved | | | | | +| Interleave n_shift | | 0 | 0 | 0 | | | | | +| Interleave size | | 2 | 2 | 2 | | | | | +| Beamforming Pre-Coder | | N/A | N/A | N/A | | | | | +| Aggregation level | CCE | 8 | 8 | 8 | | | | | +| DCI formats | | Note 1 | Note 1 | Note 1 | | | | | +| Payload size (without CRC) | bits | Note 2 | Note 2 | Note 2 | | | | | +| Note 1: DCI format shall depend upon the test configuration.
Note 2: Payload size shall depend upon the test configuration.
Note 3: Allocated in the same resource blocks where the associated PDSCH RMC is scheduled. | | | | | | | | | + +## G.1.2 OFDMA channel noise generator (OCNG) + +### G.1.2.1 Generic OFDMA Channel Noise Generator (OCNG) + +The OCNG pattern is used in a test for modelling allocations of unused resources in the channel bandwidth to virtual IAB-MTs (which are not under test). The OCNG pattern comprises PDCCH and PDSCH transmissions to the virtual IAB-MTs. + +#### G.1.2.1.1 OCNG pattern 1: Generic OCNG pattern for all unused REs + +**Table G.1.2.1.1-1: OP.1: Generic OCNG pattern for all unused REs** + +| OCNG Parameters | Control Region | Data Region | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|------------------------------------------------| +| Resource allocation | Unused REs (Note 1) | Unused REs (Note 2) | +| Channel | PDCCH | PDSCH | +| Contents | Virtual IAB-MT IDs | Uncorrelated pseudo random QPSK modulated data | +| Antenna transmission scheme | Same as used in PDCCH RMC | Same as used in PDSCH RMC | +| Subcarrier spacing | Same as used in PDCCH RMC | Same as used in PDSCH RMC | +| Aggregation level | Same as used in PDCCH RMC | N/A | +| Code rate | Same as used in PDCCH RMC | Same as used in PDSCH RMC | +| Transmit Power | Same as used in PDCCH RMC | Same as used in PDSCH RMC | +| CP length | Same as used in PDCCH RMC | Same as used in PDSCH RMC | +| Note 1: REs not used in the active CORESETs where PDCCH is scheduled for the IAB-MT under test.
Note 2: REs not allocated to any physical channels, CORESET, SSB or any other reference signal within the channel bandwidth of the cell. | | | + +### G.1.2.1.2 OCNG pattern 2: Generic OCNG pattern for all unused REs for 2AoA setup + +**Table G.1.2.1.2-1: OP.2: Generic OCNG pattern for all unused REs for 2AoA setup** + +| OCNG Parameters | Control Region | Data Region | +|-----------------------------|--------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------| +| Probe | Transmitting the serving beam | | +| Resource allocation | Unused REs (Note 1) in the symbols where SSB/CSI-RS are not transmitted from both the serving beam probe and non-serving beam probe. | Unused REs (Note 2) in the symbols where SSB/CSI-RS are not transmitted from both the serving beam probe and non-serving beam probe. | +| Channel | PDCCH | PDSCH | +| Contents | Virtual IAB-MT IDs | Uncorrelated pseudo random QPSK modulated data | +| Antenna transmission scheme | Same as used in PDCCH RMC | Same as used in PDSCH RMC | +| Subcarrier spacing | Same as used in PDCCH RMC | Same as used in PDSCH RMC | +| Aggregation level | Same as used in PDCCH RMC | N/A | +| Code rate | Same as used in PDCCH RMC | Same as used in PDSCH RMC | +| Transmit Power | Same as used in PDCCH RMC | Same as used in PDSCH RMC | +| CP length | Same as used in PDCCH RMC | Same as used in PDSCH RMC | +| Note 1: | REs not used in the active CORESETs where PDCCH is scheduled for the IAB-MT under test. | | +| Note 2: | REs not allocated to any physical channels, CORESET, SSB or any other reference signal within the channel bandwidth of the cell. | | +| Note 3: | No OCNG is transmitted from the probe transmitting non-serving beam. | | + +### G.1.2.1.3 OCNG pattern 3: Generic OCNG pattern for unused REs in the same bandwidth as PDSCH RMC + +**Table G.1.2.1.3-1: OP.3: Generic OCNG pattern for unused REs in the same BW as RMC** + +| OCNG Parameters | Control Region | Data Region | +|-----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------| +| Resource allocation | Unused REs (Note 1) | Unused REs (Note 2) | +| Channel | PDCCH | PDSCH | +| Contents | Virtual IAB-MT IDs | Uncorrelated pseudo random QPSK modulated data | +| Antenna transmission scheme | Same as used in PDCCH RMC | Same as used in PDSCH RMC | +| Subcarrier spacing | Same as used in PDCCH RMC | Same as used in PDSCH RMC | +| Aggregation level | Same as used in PDCCH RMC | N/A | +| Code rate | Same as used in PDCCH RMC | Same as used in PDSCH RMC | +| Transmit Power | Same as used in PDCCH RMC | Same as used in PDSCH RMC | +| CP length | Same as used in PDCCH RMC | Same as used in PDSCH RMC | +| Note 1: | REs not used in the active CORESETs where PDCCH is scheduled for the IAB-MT under test. REs for OCNG shall not be allocated outside the allocated bandwidth of the PDSCH RMC of the serving cell. | | +| Note 2: | REs not allocated to any physical channels, CORESET, SSB or any other reference signal within the allocated bandwidth of the PDSCH RMC of the serving cell. REs for OCNG shall not be allocated outside the allocated bandwidth of the PDSCH RMC of the serving cell. | | + +#### G.1.2.1.4 OCNG pattern 4: Generic OCNG pattern for all unused REs outside SSB slot(s) + +**Table G.1.2.1.4-1: OP.4: Generic OCNG pattern for all unused REs outside SSB slot(s)** + +| OCNG Parameters | Control Region | Data Region | +|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------| +| Resource allocation | Unused REs (Note 1) | Unused REs (Note 2) | +| Channel | PDCCH | PDSCH | +| Contents | Virtual IAB-MT IDs | Uncorrelated pseudo random QPSK modulated data | +| Antenna transmission scheme | Same as used in PDCCH RMC | Same as used in PDSCH RMC | +| Subcarrier spacing | Same as used in PDCCH RMC | Same as used in PDSCH RMC | +| Aggregation level | Same as used in PDCCH RMC | N/A | +| Code rate | Same as used in PDCCH RMC | Same as used in PDSCH RMC | +| Transmit Power | Same as used in PDCCH RMC | Same as used in PDSCH RMC | +| CP length | Same as used in PDCCH RMC | Same as used in PDSCH RMC | +| Note 1: | REs not used in the active CORESETs where PDCCH is scheduled for the IAB-MT under test. REs for OCNG shall not be allocated in the slot(s) containing SSB of the respective cell. | | +| Note 2: | REs not allocated to any physical channels, CORESET, SSB or any other reference signal within the channel bandwidth of the cell. REs for OCNG shall not be allocated in the slot(s) containing SSB of the respective cell. | | + +### G.1.3 Antenna configurations + +#### G.1.3.1 Antenna configurations for FR1 + +Unless otherwise specified, NR TDD cells in all RRM Test cases in AWGN propagation condition are configured with Antenna Configuration [1x2]. + +##### G.1.3.1.1 Antenna connection for 4 Rx capable IAB-MT + +###### G.1.3.1.1.1 Introduction + +All tests for FR1 are specified for IAB-MTs supporting 2RX. In this clause, the antenna connection method for applying 2RX tests to IAB-MTs supporting 4RX antenna ports is specified. No tests are currently specified for FR1 which are applicable only to 4RX antenna ports, so 4RX capable IAB-MTs are always tested by reusing tests which were originally specified for 2RX IAB-MTs. + +###### G.1.3.1.1.2 Principle of testing + +###### G.1.3.1.1.2.1 Single carrier tests + +For 4RX capable IAB-MTs supporting at least one 2RX band, the, all single carrier tests specified for FR1 except those in G.2.3 shall be tested on any band where 2RX is supported with the antenna connection specified in clause G.1.3.1.1.2.2. + +For 4RX capable IAB-MT which do not support any 2RX band, all tests specified for FR1 shall be tested using the antenna connection specified in clause G.1.3.1.1.2.3. For radio link monitoring tests, the SNR levels are modified according to table G.1.3.1.1.2.1-1 and table G.1.3.1.1.2.1-2. For beam failure detection and link recovery tests, the SNR levels are modified according to table G.1.3.1.1.2.1-3. + +**Table G.1.3.1.1.2.1-1: Modified parameters for RLM out of sync testing with 4 RX antenna connection** + +| Test case | SNR during T3 (dB) | | | | +|-----------|--------------------|--------|--------|--------| +| | Test 1 | Test 2 | Test 3 | Test 4 | +| G.2.3.1.1 | -18 | N/A | N/A | N/A | +| G.2.3.1.3 | -18 | N/A | N/A | N/A | +| G.2.3.1.5 | -18 | N/A | N/A | N/A | +| G.2.3.1.7 | -18 | N/A | N/A | N/A | + +**Table G.1.3.1.1.2.1-2: Modified parameters for RLM in sync single carrier testing with 4 RX antenna connection** + +| Test case | SNR during T3 (dB) | | SNR during T4 (dB) | | +|-----------|--------------------|--------|--------------------|--------| +| | Test 1 | Test 2 | Test 1 | Test 2 | +| G.2.3.1.2 | -18 | N/A | -8 | N/A | +| G.2.3.1.4 | -18 | N/A | -8 | N/A | +| G.2.3.1.6 | -18 | N/A | -8 | N/A | +| G.2.3.1.8 | -18 | N/A | -8 | N/A | + +**Table G.1.3.1.1.2.1-3: Modified parameters for Beam Failure Detection and Link Recovery testing with 4 RX antenna connection** + +| Test case | SNR for RS in set $q_0$ during T3, T4 and T5 (dB) | +|-----------|---------------------------------------------------| +| | Test 1 | +| G.2.3.2.1 | -15 | +| G.2.3.2.2 | -15 | +| G.2.3.2.3 | -15 | +| G.2.3.2.4 | -15 | + +#### G.1.3.1.1.2.2 Antenna connection for bands where 2RX is supported + +For bands where 2RX is supported, it is left to declaration and AP configuration to decide which 2 of the 4 Rx ports are connected with data source from tester. The remaining 2 Rx ports shall be connected with zero input. No test parameters or requirements are modified. + +#### G.1.3.1.1.2.3 Antenna connection for bands where 4RX is supported + +For bands where 4RX is supported, all 4 RX antennas are connected with data source from tester. The Tester provide independent noise and fading (low correlation) for each antenna port. Except for the modifications to radio link monitoring thresholds described in clauses G.1.3.1.1.2.1 and G.1.3.1.1.2.2, no test parameters or requirements are modified. + +### G.1.3.2 Antenna configurations for FR2-1 + +Unless otherwise specified, the default Downlink Antenna Configuration for NR FR2-1 cells is 1x2. + +In case of Downlink Antenna Configuration 2x2 for NR FR2-1 cells, unless otherwise specified, the downlink signal is transmitted over the two polarizations (V and H) of the dual polarized antenna of the test equipment. + +## G.1.4 BWP configurations + +### G.1.4.1 Introduction + +This clause provides the typical BWP configurations used for RRM test cases defined in Annex G. For downlink BWP, both initial BWP and dedicated BWP configurations are specified in clause G.1.4.2 and for uplink BWP, both initial BWP and dedicated BWP configurations are specified in clause G.1.4.3. + +## G.1.4.2 Downlink BWP configurations + +### G.1.4.2.1 Initial BWP + +**Table G.1.4.2.1-1: Downlink BWP patterns for initial BWP configuration** + +| BWP Parameters | Unit | Values | | | +|--------------------|------|-----------------------------------------|--------------------------------------------------------|--| +| Reference BWP | | DLBWP.0.1 | DLBWP.0.2 | | +| Starting PRB index | | 0 | RB a Note 1 | | +| Bandwidth | RB | Same as RF channel defined in each test | same as RMSI CORESET (CORESET #0) defined in each test | | + +Note 1: RBa is the lowest PRB index to guarantee the BWP including SSB PRB index (RBJ, RBJ+1, ..., RBJ+19) which is defined in Clause G.1.5. + +### G.1.4.2.2 Dedicated BWP + +**Table G.1.4.2.2-1: Downlink BWP patterns for dedicated BWP configuration** + +| BWP Parameters | Unit | Values | | | +|--------------------|------|-----------------------------------------|-------------------------------------------------------------------|-------------------------------------------------------------------| +| Reference BWP | | DLBWP.1.1 | DLBWP.1.2 | DLBWP.1.3 | +| Starting PRB index | | 0 | RB b Note 1 | RB a Note 2 | +| Bandwidth | RB | Same as RF channel defined in each test | 25 for SCS = 15KHz,
51 for SCS = 30KHz,
32 for SCS = 120KHz | 25 for SCS = 15KHz,
51 for SCS = 30KHz,
32 for SCS = 120KHz | + +Note 1: RBb is the lowest PRB index to guarantee the BWP not fully overlapped with SSB PRB index (RBJ, RBJ+1, ..., RBJ+19) which is defined in Clause G.1.5. +Note 2: RBa is the lowest PRB index to guarantee the BWP including SSB PRB index (RBJ, RBJ+1, ..., RBJ+19) which is defined in Clause G.1.5. + +## G.1.4.3 Uplink BWP configurations + +### G.1.4.3.1 Initial BWP + +**Table G.1.4.3.1-1: Uplink BWP patterns for initial BWP configuration** + +| BWP Parameters | Unit | Values | | | +|--------------------|------|-----------------------------------------|--------------------------------------------------------|--| +| Reference BWP | | ULBWP.0.1 | ULBWP.0.2 | | +| Starting PRB index | | 0 | RB a Note 1 | | +| Bandwidth | RB | Same as RF channel defined in each test | same as RMSI CORESET (CORESET #0) defined in each test | | + +Note 1: RBa is same as RBa for DLBWP.0.2 as defined in Table G.1.4.2.1-1. + +### G.1.4.3.2 Dedicated BWP + +**Table G.1.4.3.2-1: Uplink BWP patterns for dedicated BWP configuration** + +| BWP Parameters | Unit | Values | | | +|--------------------|------|-----------------------------------------|-------------------------------------------------------------------|-------------------------------------------------------------------| +| Reference BWP | | ULBWP.1.1 | ULBWP.1.2 | ULBWP.1.3 | +| Starting PRB index | | 0 | RB b Note 1 | RB a Note 2 | +| Bandwidth | RB | Same as RF channel defined in each test | 25 for SCS = 15KHz,
51 for SCS = 30KHz,
32 for SCS = 120KHz | 25 for SCS = 15KHz,
51 for SCS = 30KHz,
32 for SCS = 120KHz | + +Note 1: RBb is same as RBb for DLBWP.1.2 as defined in Table G.1.4.2.2-1. +Note 2: RBa is same as RBa for DLBWP.1.3 as defined in Table G.1.4.2.2-1. + +## G.1.5 SSB Configurations + +### G.1.5.1 SSB Configurations for FR1 + +#### G.1.5.1.1 SSB pattern 1 in FR1: SSB allocation for SSB SCS=15 kHz + +**Table G.1.5.1.1-1: SSB.1 FR1: SSB Pattern 1 for SSB SCS=15 kHz in 10 MHz channel** + +| SSB Parameters | Values | +|-------------------------------------------------|------------------------------------------------------------------------------------| +| SSB SCS | 15 kHz | +| SSB periodicity (T SSB ) | 20 ms | +| Number of SSBs per SS-burst | 1 | +| SS/PBCH block index | 0 | +| Symbol numbers containing SSB Note 2 | 2-5 | +| Slot numbers containing SSB Note 2 | 0 | +| SFN containing SSB | SFN mod
(max(T SSB , 10ms)/10ms) = 0 | +| RB numbers containing SSB within channel BW | (RB j , RB j+1 , ..., RB j+19 ) Note 1 | + +Note 1: RBs containing SSB can be configured in any frequency location within the cell bandwidth according to the allowed synchronization raster defined in clause 5.4.3 +Note 2: These values have been derived from other parameters for information purposes (as per TS 38.213 [3]). They are not settable parameters themselves. + +#### G.1.5.1.2 SSB pattern 2 in FR1: SSB allocation for SSB SCS=30 kHz + +**Table G.1.5.1.2-1: SSB.2 FR1: SSB Pattern 2 for SSB SCS=30 kHz** + +| SSB Parameters | Values | +|-------------------------------------------------|------------------------------------------------------------------------------------| +| SSB SCS | 30 kHz | +| SSB periodicity (T SSB ) | 20 ms | +| Number of SSBs per SS-burst | 1 | +| SS/PBCH block index | 0 | +| Symbol numbers containing SSB Note 3 | 4-7 or 2-5 Note 2 | +| Slot numbers containing SSB Note 3 | 0 | +| SFN containing SSB | SFN mod
(max(T SSB , 10ms)/10ms) = 0 | +| RB numbers containing SSB within channel BW | (RB j , RB j+1 , ..., RB j+19 ) Note 1 | + +Note 1: RBs containing SSB can be configured in any frequency location within the cell bandwidth according to the allowed synchronization raster defined in clause 5.4.3 +Note 2: Symbols 4-7 is chosen, if the SSB pattern Case B should be used for the current band as define in clause 5.4.3; Otherwise, symbol 2-5 is chosen. +Note 3: These values have been derived from other parameters for information purposes (as per TS 38.213 [3]). They are not settable parameters themselves + +## G.1.5.1.3 SSB pattern 3 in FR1: SSB allocation for SSB SCS=15 kHz + +Table G.1.5.1.3-1: SSB.3 FR1: SSB Pattern 3 for SSB SCS=15 kHz + +| SSB Parameters | Values | | +|-------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|------| +| SSB SCS | 15 kHz | | +| SSB periodicity ( $T_{\text{SSB}}$ ) | 20 ms | | +| Number of SSBs per SS-burst | 2 | | +| SS/PBCH block index | 0 | 1 | +| Symbol numbers containing SSB Note 2 | 2-5 | 8-11 | +| Slot numbers containing SSB Note 2 | 0 | 0 | +| SFN containing SSB | SFN mod $(\max(T_{\text{SSB}}, 10\text{ms})/10\text{ms}) = 0$ | | +| RB numbers containing SSB within channel BW | $(\text{RB}_j, \text{RB}_{j+1}, \dots, \text{RB}_{j+19})^{\text{Note 1}}$ | | +| Note 1: | RBs containing SSB can be configured in any frequency location within the cell bandwidth according to the allowed synchronization raster defined in clause 5.4.3 | | +| Note 2: | These values have been derived from other parameters for information purposes (as per TS 38.213 [3]). They are not settable parameters themselves. | | + +## G.1.5.1.4 SSB pattern 4 in FR1: SSB allocation for SSB SCS=30 kHz + +Table G.1.5.1.4-1: SSB.4 FR1: SSB Pattern 4 for SSB SCS=30 kHz + +| SSB Parameters | Values | | +|-------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|------| +| SSB SCS | 30 kHz | | +| SSB periodicity ( $T_{\text{SSB}}$ ) | 20 ms | | +| Number of SSBs per SS-burst | 2 | | +| SS/PBCH block index | 0 | 1 | +| Symbol numbers containing SSB Note 3 | 4-7 or 2-5 Note 2 | 8-11 | +| Slot numbers containing SSB Note 3 | 0 | 0 | +| SFN containing SSB | SFN mod $(\max(T_{\text{SSB}}, 10\text{ms})/10\text{ms}) = 0$ | | +| RB numbers containing SSB within channel BW | $(\text{RB}_j, \text{RB}_{j+1}, \dots, \text{RB}_{j+19})^{\text{Note 1}}$ | | +| Note 1: | RBs containing SSB can be configured in any frequency location within the cell bandwidth according to the allowed synchronization raster defined in clause 5.4.3. | | +| Note 2: | Symbols 4-7 is chosen, if the SSB pattern Case B should be used for the current band as defined in clause 5.4.3; Otherwise, symbol 2-5 is chosen. | | +| Note 3: | These values have been derived from other parameters for information purposes (as per TS 38.213 [3]). They are not settable parameters themselves. | | + +## G.1.5.1.5 SSB pattern 5 in FR1: SSB allocation for SSB SCS=15 kHz starting from odd SFN + +Table G.1.5.1.5-1: SSB.5 FR1: SSB Pattern 5 for SSB SCS=15 kHz + +| SSB Parameters | Values | | +|-------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| SSB SCS | 15 kHz | | +| SSB periodicity ( $T_{\text{SSB}}$ ) | 20 ms | | +| Number of SSBs per SS-burst | 1 | | +| SS/PBCH block index | 0 | | +| Symbol numbers containing SSB Note 2 | 2-5 | | +| Slot numbers containing SSB Note 2 | 0 | | +| SFN containing SSB | SFN mod $(\max(T_{\text{SSB}}, 10\text{ms})/10\text{ms}) = 1$ | | +| RB numbers containing SSB within channel BW | $(\text{RB}_j, \text{RB}_{j+1}, \dots, \text{RB}_{j+19})^{\text{Note 1}}$ | | +| Note 1: | RBs containing SSB can be configured in any frequency location within the cell bandwidth according to the allowed synchronization raster defined in clause 5.4.3. | | +| Note 2: | These values have been derived from other parameters for information purposes (as per TS 38.213 [3]). They are not settable parameters themselves. | | + +G.1.5.1.6 SSB pattern 6 in FR1: SSB allocation for SSB SCS=30 kHz starting from odd SFN + +**Table G.1.5.1.6-1: SSB.6 FR1: SSB Pattern 6 for SSB SCS=30 kHz** + +| SSB Parameters | Values | +|-------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SSB SCS | 30 kHz | +| SSB periodicity ( $T_{\text{SSB}}$ ) | 20 ms | +| Number of SSBs per SS-burst | 1 | +| SS/PBCH block index | 0 | +| Symbol numbers containing SSB Note 3 | 4-7 or 2-5 Note 2 | +| Slot numbers containing SSB Note 3 | 0 | +| SFN containing SSB | $\text{SFN mod } (\max(T_{\text{SSB}}, 10\text{ms})/10\text{ms}) = 1$ | +| RB numbers containing SSB within channel BW | $(\text{RB}_j, \text{RB}_{j+1}, \dots, \text{RB}_{j+19})^{\text{Note 1}}$ | +| Note 1: | RBs containing SSB can be configured in any frequency location within the cell bandwidth according to the allowed synchronization raster defined in clause 5.4.3 | +| Note 2: | Symbols 4-7 is chosen, if the SSB pattern Case B should be used for the current band as defined in clause 5.4.3; Otherwise, symbol 2-5 is chosen. | +| Note 3: | These values have been derived from other parameters for information purposes (as per TS 38.213 [3]). They are not settable parameters themselves. | + +G.1.5.2 SSB Configurations for FR2-1 + +G.1.5.2.1 SSB pattern 1 in FR2-1: SSB allocation for SSB SCS=120 kHz + +**Table G.1.5.2.1-1: SSB.1 FR2-1: SSB Pattern 1 for SSB SCS = 120 kHz with 2 SSBs per SS-burst** + +| SSB Parameters | Values | | +|--------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|------| +| SSB SCS | 120 kHz | | +| SSB periodicity ( $T_{\text{SSB}}$ ) | 20 ms | | +| Number of SSBs per SS-burst | 2 | | +| SS/PBCH block index | 0 | 1 | +| Symbol numbers containing SSBs Note 2 | 4-7 | 8-11 | +| Slot numbers containing SSB Note 2 | 0 | 0 | +| SFN containing SSB | $\text{SFN mod } (\max(T_{\text{SSB}}, 10\text{ms})/10\text{ms}) = 0$ | | +| RB numbers containing SSBs within channel BW | $(\text{RB}_j, \text{RB}_{j+1}, \dots, \text{RB}_{j+19})^{\text{Note 1}}$ | | +| Note 1: | RBs containing SSB can be configured in any frequency location within the cell bandwidth according to the allowed synchronization raster defined in clause 5.4.3. | | +| Note 2: | These values have been derived from other parameters for information purposes (as per TS 38.213 [3]). They are not settable parameters themselves. | | + +G.1.5.2.2 SSB pattern 2 in FR2: SSB allocation for SSB SCS=240 kHz + +**Table G.1.5.2.2-1: SSB.2 FR2-1: SSB Pattern 2 for SSB SCS = 240 kHz with 2 SSBs per SS-burst** + +| SSB Parameters | Values | | +|--------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------| +| SSB SCS | 240 kHz | | +| SSB periodicity ( $T_{\text{SSB}}$ ) | 20 ms | | +| Number of SSBs per SS-burst | 2 | | +| SS/PBCH block index | 0 | 1 | +| Symbol numbers containing SSBs Note 2 | 8-11 | 12-13, 0-1 | +| Slot numbers containing SSB Note 2 | 0 | 0, 1 | +| SFN containing SSB | $\text{SFN mod } (\max(T_{\text{SSB}}, 10\text{ms})/10\text{ms}) = 0$ | | +| RB numbers containing SSBs within channel BW | $(\text{RB}_j, \text{RB}_{j+1}, \dots, \text{RB}_{j+39})^{\text{Note 1}}$ | | +| Note 1: | RBs containing SSB can be configured in any frequency location within the cell bandwidth according to the allowed synchronization raster defined in clause 5.4.3. | | +| Note 2: | These values have been derived from other parameters for information purposes (as per TS 38.213 [3]). They are not settable parameters themselves. | | + +## G.1.5.2.3 SSB pattern 3 in FR2-1: SSB allocation for SSB SCS=120 kHz + +Table G.1.5.2.3-1: SSB.3 FR2-1: SSB Pattern 3 for SSB SCS = 120 kHz with 1 SSB per SS-burst + +| SSB Parameters | Values | +|--------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SSB SCS | 120 kHz | +| SSB periodicity ( $T_{\text{SSB}}$ ) | 20 ms | +| Number of SSBs per SS-burst | 1 | +| SS/PBCH block index | 0 | +| Symbol numbers containing SSBs Note 2 | 4-7 | +| Slot numbers containing SSB Note 2 | 0 | +| SFN containing SSB | SFN mod
$(\max(T_{\text{SSB}}, 10\text{ms})/10\text{ms}) = 0$ | +| RB numbers containing SSBs within channel BW | $(\text{RB}_J, \text{RB}_{J+1}, \dots, \text{RB}_{J+19})^{\text{Note 1}}$ | +| Note 1: | RBs containing SSB can be configured in any frequency location within the cell bandwidth according to the allowed synchronization raster defined in clause 5.4.3. | +| Note 2: | These values have been derived from other parameters for information purposes (as per TS 38.213 [3]). They are not settable parameters themselves. | + +## G.1.5.2.4 SSB pattern 4 in FR2-1: SSB allocation for SSB SCS=240 kHz + +Table G.1.5.2.4-1: SSB.4 FR2-1: SSB Pattern 4 for SSB SCS = 240 kHz with 1 SSB per SS-burst + +| SSB Parameters | Values | +|--------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SSB SCS | 240 kHz | +| SSB periodicity ( $T_{\text{SSB}}$ ) | 20 ms | +| Number of SSBs per SS-burst | 1 | +| SS/PBCH block index | 0 | +| Symbol numbers containing SSBs Note 2 | 8-11 | +| Slot numbers containing SSB Note 2 | 0 | +| SFN containing SSB | SFN mod
$(\max(T_{\text{SSB}}, 10\text{ms})/10\text{ms}) = 0$ | +| RB numbers containing SSBs within channel BW | $(\text{RB}_J, \text{RB}_{J+1}, \dots, \text{RB}_{J+39})^{\text{Note 1}}$ | +| Note 1: | RBs containing SSB can be configured in any frequency location within the cell bandwidth according to the allowed synchronization raster defined in clause 5.4.3. | +| Note 2: | These values have been derived from other parameters for information purposes (as per TS 38.213 [3]). They are not settable parameters themselves. | + +## G.1.5.2.5 SSB pattern 5 in FR2-1: SSB allocation for SSB SCS=120 kHz + +Table G.1.5.2.5-1: SSB.5 FR2-1: SSB Pattern 5 for SSB SCS = 120 kHz with 2 SSBs per SS-burst + +| SSB Parameters | Values | | +|--------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| SSB SCS | 120 kHz | | +| SSB periodicity ( $T_{\text{SSB}}$ ) | 20 ms | | +| Number of SSBs per SS-burst | 2 | | +| SS/PBCH block index | 2 | 3 | +| Symbol numbers containing SSBs Note 2 | 2-5 | 6-9 | +| Slot numbers containing SSB Note 2 | 1 | 1 | +| SFN containing SSB | SFN mod
$(\max(T_{\text{SSB}}, 10\text{ms})/10\text{ms}) = 0$ | | +| RB numbers containing SSBs within channel BW | $(\text{RB}_J, \text{RB}_{J+1}, \dots, \text{RB}_{J+19})^{\text{Note 1}}$ | | +| Note 1: | RBs containing SSB can be configured in any frequency location within the cell bandwidth according to the allowed synchronization raster defined in clause 5.4.3. | | +| Note 2: | These values have been derived from other parameters for information purposes (as per TS 38.213 [3]). They are not settable parameters themselves. | | + +## G.1.5.2.6 SSB pattern 6 in FR2-1: SSB allocation for SSB SCS=240 kHz + +Table G.1.5.2.6-1: SSB.6 FR2-1: SSB Pattern 6 for SSB SCS = 240 kHz with 2 SSBs per SS-burst + +| SSB Parameters | Values | | +|--------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| SSB SCS | 240 kHz | | +| SSB periodicity ( $T_{\text{SSB}}$ ) | 20 ms | | +| Number of SSBs per SS-burst | 2 | | +| SS/PBCH block index | 2 | 3 | +| Symbol numbers containing SSBs Note 2 | 2-5 | 6-9 | +| Slot numbers containing SSB Note 2 | 1 | 1 | +| SFN containing SSB | SFN mod $(\max(T_{\text{SSB}}, 10\text{ms})/10\text{ms}) = 0$ | | +| RB numbers containing SSBs within channel BW | $(\text{RB}_J, \text{RB}_{J+1}, \dots, \text{RB}_{J+39})^{\text{Note 1}}$ | | +| Note 1: | RBs containing SSB can be configured in any frequency location within the cell bandwidth according to the allowed synchronization raster defined in clause 5.4.3. | | +| Note 2: | These values have been derived from other parameters for information purposes (as per TS 38.213 [3]). They are not settable parameters themselves. | | + +## G.1.5.2.7 SSB pattern 7 in FR2-1: SSB allocation for SSB SCS=120 kHz + +Table G.1.5.2.7-1: SSB.7 FR2-1: SSB Pattern 7 for SSB SCS = 120 kHz with 1 SSB per SS-burst + +| SSB Parameters | Values | | +|--------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| SSB SCS | 120 kHz | | +| SSB periodicity ( $T_{\text{SSB}}$ ) | 20 ms | | +| Number of SSBs per SS-burst | 1 | | +| SS/PBCH block index | 1 | | +| Symbol numbers containing SSBs Note 2 | 8-11 | | +| Slot numbers containing SSB Note 2 | 0 | | +| SFN containing SSB | SFN mod $(\max(T_{\text{SSB}}, 10\text{ms})/10\text{ms}) = 0$ | | +| RB numbers containing SSBs within channel BW | $(\text{RB}_J, \text{RB}_{J+1}, \dots, \text{RB}_{J+19})^{\text{Note 1}}$ | | +| Note 1: | RBs containing SSB can be configured in any frequency location within the cell bandwidth according to the allowed synchronization raster defined in clause 5.4.3. | | +| Note 2: | These values have been derived from other parameters for information purposes (as per TS 38.213 [3]). They are not settable parameters themselves. | | + +## G.1.5.2.8 SSB pattern 8 in FR2-1: SSB allocation for SSB SCS=240 kHz + +Table G.1.5.2.8-1: SSB.8 FR2-1: SSB Pattern 8 for SSB SCS = 240 kHz with 1 SSB per SS-burst + +| SSB Parameters | Values | | +|--------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| SSB SCS | 240 kHz | | +| SSB periodicity ( $T_{\text{SSB}}$ ) | 20 ms | | +| Number of SSBs per SS-burst | 1 | | +| SS/PBCH block index | 1 | | +| Symbol numbers containing SSBs Note 2 | 12-13 | 0-1 | +| Slot numbers containing SSB Note 2 | 0 | 1 | +| SFN containing SSB | SFN mod $(\max(T_{\text{SSB}}, 10\text{ms})/10\text{ms}) = 0$ | | +| RB numbers containing SSBs within channel BW | $(\text{RB}_J, \text{RB}_{J+1}, \dots, \text{RB}_{J+39})^{\text{Note 1}}$ | | +| Note 1: | RBs containing SSB can be configured in any frequency location within the cell bandwidth according to the allowed synchronization raster defined in clause 5.4.3. | | +| Note 2: | These values have been derived from other parameters for information purposes (as per TS 38.213 [3]). They are not settable parameters themselves. | | + +## G.1.6 SMTC Configurations + +### G.1.6.1 SMTC pattern 1: SMTC period = 20 ms with SMTC duration = 1 ms + +**Table G.1.6.1-1: SMTC.1: SMTC Pattern 1 for SMTC period = 20 ms and duration = 1 ms** + +| SMTC Parameters | Values | +|------------------|--------| +| SMTC periodicity | 20 ms | +| SMTC offset | 0 ms | +| SMTC duration | 1 ms | + +### G.1.6.2 SMTC pattern 2: SMTC period = 20 ms with SMTC duration = 5 ms + +**Table G.1.6.2-1: SMTC.2: SMTC Pattern 2 for SMTC period = 20 ms and duration = 5 ms** + +| SMTC Parameters | Values | +|------------------|--------| +| SMTC periodicity | 20 ms | +| SMTC offset | 0 ms | +| SMTC duration | 5 ms | + +### G.1.6.3 SMTC pattern 3: SMTC period = 160 ms with SMTC duration = 1 ms + +**Table G.1.6.3-1: SMTC.3: SMTC Pattern 3 for SMTC period = 20 ms and duration = 5 ms** + +| SMTC Parameters | Values | +|------------------|--------| +| SMTC periodicity | 160 ms | +| SMTC offset | 0 ms | +| SMTC duration | 1 ms | + +### G.1.6.4 SMTC pattern 4: SMTC period = 20 ms with SMTC duration = 1 ms + +**Table G.1.6.4-1: SMTC.4: SMTC Pattern 4 for SMTC period = 20 ms and duration = 1 ms** + +| SMTC Parameters | Values | +|------------------|--------| +| SMTC periodicity | 20 ms | +| SMTC offset | 10 ms | +| SMTC duration | 1 ms | + +### G.1.6.5 SMTC pattern 5: SMTC period = 20 ms with SMTC duration = 5 ms + +**Table G.1.6.4-1: SMTC.5: SMTC Pattern 5 for SMTC period = 20 ms and duration = 5 ms** + +| SMTC Parameters | Values | +|------------------|--------| +| SMTC periodicity | 20 ms | +| SMTC offset | 10 ms | +| SMTC duration | 5 ms | + +## G.1.7 CSI-RS configurations + +### G.1.7.1 TDD + +**Table G.1.7.1-1: CSI-RS Reference Measurement Channels for SCS=15kHz** + +| | CSI-RS.1.1 TDD | CSI-RS.1.2 TDD | CSI-RS.1.3 TDD | CSI-RS.1.4 TDD | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|------------------------------------------|------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Resource Type | periodic | periodic | aperiodic | aperiodic | +| Resource Set Config | | | | | +| nzp-CSI-ResourceSetId | 0 | 0 | 0 | 0 | +| repetition | n.a. | off | off | on | +| aperiodicTriggeringOffset | n.a. | n.a. | 0 | 0 | +| trs-Info | n.a. | n.a. | n.a. | n.a. | +| Resource Config | | | | | +| nzp-CSI-RS-ResourceId | 0 for resource #0 | 10 for resource #0
11 for resource #1 | 20 for resource #0
21 for resource #1 | 0 for resource #0
1 for resource #1
2 for resource #2
3 for resource #3
4 for resource #4
5 for resource #5
6 for resource #6
7 for resource #7 | +| powerControlOffset | 0 | 0 | 0 | 0 | +| powerControlOffsetSS | db0 | db0 | db0 | db0 | +| scramblingID | 0 | 0 | 0 | 0 | +| Period (slots) | slot5 | slot10 | n.a. | n.a. | +| qcl-InfoPeriodicCSI-RS | TCI.State.0 | TCI.State.0
TCI.State.1 | n.a. | n.a. | +| frequencyDomainAllocation | 000001 | 000001 | 000001 | 000001 | +| nrofPorts | 2 | 1 | 1 | 1 | +| firstOFDMSymbolInTimeDomain | 4 for resource #0 | 6 for resource #0
10 for resource #1 | 6 for resource #0
10 for resource #1 | 0 for resource #0
1 for resource #1
2 for resource #2
3 for resource #3
4 for resource #4
5 for resource #5
6 for resource #6
7 for resource #7 | +| cdm-Type | FD-CDM2 | noCDM | noCDM | noCDM | +| density | 1 | 3 | 3 | 3 | +| startingRB | 0 | 0 | 0 | 0 | +| nrofRBs | 276 (Note 1) | 276 (Note 1) | 276 (Note 1) | 276 (Note 1) | +| Note 1: If the configured value of PRBs is larger than the width of the corresponding BWP relevant for the test case, the Test Equipment shall implement CSI-RS only in the width of that BWP. | | | | | + +**Table G.1.7.1-2: CSI-RS Reference Measurement Channels for SCS=30kHz** + +| | CSI-RS.2.1 TDD | CSI-RS.2.2 TDD | CSI-RS.2.3 TDD | CSI-RS.2.4 TDD | +|-----------------------------|-----------------------|-----------------------|-----------------------|-----------------------| +| Resource Type | periodic | periodic | aperiodic | aperiodic | +| Resource Set Config | | | | | +| nzp-CSI-ResourceSetId | 0 | 0 | 0 | 0 | +| repetition | n.a. | off | off | on | +| aperiodicTriggeringOffset | n.a. | n.a. | 0 | 0 | +| trs-Info | n.a. | n.a. | n.a. | n.a. | +| Resource Config | | | | | +| nzp-CSI-RS-ResourceId | 0 for resource #0 | 10 for resource #0 | 20 for resource #0 | 0 for resource #0 | +| | | | | 1 for resource #1 | +| | | | | 2 for resource #2 | +| | | | | 3 for resource #3 | +| | | 11 for resource #1 | 21 for resource #1 | 4 for resource #4 | +| | | | | 5 for resource #5 | +| | | | | 6 for resource #6 | +| | | | | 7 for resource #7 | +| powerControlOffset | 0 | 0 | 0 | 0 | +| powerControlOffsetSS | db0 | db0 | db0 | db0 | +| scramblingID | 0 | 0 | 0 | 0 | +| Period (slots) | slot10 | slot20 | n.a. | n.a. | +| qcl-InfoPeriodicCSI-RS | TCI.State.0 | TCI.State.0 | n.a. | n.a. | +| | | TCI.State.1 | | | +| frequencyDomainAllocation | 000001 | 000001 | 000001 | 000001 | +| nrofPorts | 2 | 1 | 1 | 1 | +| firstOFDMSymbolInTimeDomain | 4 for resource #0 | 6 for resource #0 | 6 for resource #0 | 0 for resource #0 | +| | | | | 1 for resource #1 | +| | | | | 2 for resource #2 | +| | | | | 3 for resource #3 | +| | | 10 for resource #1 | 10 for resource #1 | 4 for resource #4 | +| | | | | 5 for resource #5 | +| | | | | 6 for resource #6 | +| | | | | 7 for resource #7 | +| cdm-Type | FD-CDM2 | noCDM | noCDM | noCDM | +| density | 1 | 3 | 3 | 3 | +| startingRB | 0 | 0 | 0 | 0 | +| nrofRBs | 276 (Note 1) | 276 (Note 1) | 276 (Note 1) | 276 (Note 1) | + +Note 1: If the configured value of PRBs is larger than the width of the corresponding BWP relevant for the test case, the Test Equipment shall implement CSI-RS only in the width of that BWP. + +**Table G.1.7.1-3: CSI-RS Reference Measurement Channels for SCS=120kHz** + +| | CSI-RS.3.1 TDD | CSI-RS.3.2 TDD | CSI-RS.3.3 TDD | CSI-RS.3.4 TDD | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------|-----------------------|-----------------------| +| Resource Type | periodic | periodic | aperiodic | aperiodic | +| Resource Set Config | | | | | +| nzp-CSI-ResourceSetId | 0 | 0 | 0 | 0 | +| repetition | n.a. | off | off | on | +| aperiodicTriggeringOffset | n.a. | n.a. | 4 | 4 | +| trs-Info | n.a. | n.a. | n.a. | n.a. | +| Resource Config | | | | | +| nzp-CSI-RS-ResourceId | 0 for resource #0 | 10 for resource #0 | 20 for resource #0 | 0 for resource #0 | +| | | | | 1 for resource #1 | +| | | 11 for resource #1 | 21 for resource #1 | 2 for resource #2 | +| | | | | 3 for resource #3 | +| | | | | 4 for resource #4 | +| | | | | 5 for resource #5 | +| | | | | 6 for resource #6 | +| | | | | 7 for resource #7 | +| powerControlOffset | 0 | 0 | 0 | 0 | +| powerControlOffsetSS | db0 | db0 | db0 | db0 | +| scramblingID | 0 | 0 | 0 | 0 | +| Period (slots) | slot40 | slot80 | n.a. | n.a. | +| qcl-InfoPeriodicCSI-RS | TCI.State.0 | TCI.State.0 | n.a. | n.a. | +| | | TCI.State.1 | | | +| frequencyDomainAllocation | 000001 | 000001 | 000001 | 000001 | +| nrofPorts | 1 | 1 | 1 | 1 | +| firstOFDMSymbolInTimeDomain | 4 for resource #0 | 6 for resource #0 | 6 for resource #0 | 0 for resource #0 | +| | | | | 1 for resource #1 | +| | | 10 for resource #1 | 10 for resource #1 | 2 for resource #2 | +| | | | | 3 for resource #3 | +| | | | | 4 for resource #4 | +| | | | | 5 for resource #5 | +| | | | | 6 for resource #6 | +| | | | | 7 for resource #7 | +| cdm-Type | FD-CDM2 | noCDM | noCDM | noCDM | +| density | 1 | 3 | 3 | 3 | +| startingRB | 0 | 0 | 0 | 0 | +| nrofRBs | 276 (Note 1) | 276 (Note 1) | 276 (Note 1) | 276 (Note 1) | +| Note 1: If the configured value of PRBs is larger than the width of the corresponding BWP relevant for the test case, the Test Equipment shall implement CSI-RS only in the width of that BWP. | | | | | + +## G.1.8 Angle of Arrival (AoA) for FR2-1 RRM test cases + +This clause specifies the AoA setups for FR2 RRM test cases. The applicable AoA setup is defined in each test case. + +### G.1.8.1 Setup 1: Single AoA + +There is only one active probe in the test. The DL signals, and noise if applicable, transmitted from the probe, are aligned to AoA based upon the declaration. + +### G.1.8.2 Setup 2: 2 AoAs + +There are 2 active probes in the test. The DL signals, and noise if applicable, transmitted from the two active probes, align to AoAs based upon the declaration. + +## G.1.9 TCI State Configuration + +### G.1.9.1 Introduction + +This clause provides the configurations for TCI states towards either SSB or CSI-RS. The TCI states defined in this clause are configured in each test when applicable to indicate that certain DL signals are QCL'ed with the referenceSignal configured in the TCI states. + +### G.1.9.2 TCI states + +**Table G.1.9.2-1: TCI States** + +| Parameter | TCI.State.0 | TCI.State.1 | TCI.State.2 | TCI.State.3 | +|----------------------------|-------------|-------------|----------------------------------------------------|----------------------------------------------------| +| tci-StateId | Id0 | Id1 | Id2 | Id3 | +| qcl-Type1 | typeC | typeC | typeA | typeA | +| qcl-Type2 Note1 | typeD | typeD | typeD | typeD | +| referenceSignal | SSB0 | SSB1 | Resource #4 in TRS resource set 1 Note3 | Resource #4 in TRS resource set 2 Note3 | + +Note 1: qcl-Type2 of typeD only where applicable. For RRM test cases, this will be only in FR2-1 +Note 2: referenceSignal configurations towards which the TCI states are configured are defined in a test-specific manner. +Note 3: Reference TRS resource sets are defined in G.1.10, and the applicable TRS resource set(s) are specified in each test case. When a single TRS resource set is configured in a test case, it is considered as resource set 1. + +## G.1.10 Configurations of CSI-RS for tracking + +### G.1.10.1 Configuration of CSI-RS for tracking for FR1 + +#### G.1.10.1.2 TDD + +**Table G.1.10.1.2-1: CSI-RS for tracking for SCS=15kHz** + +| Parameter | Unit | Value | +|---------------------------------------------------|----------------------------------------------------------------------------------------|--------------------------------------------------------------------------------| +| Reference channel | | TRS.1.1 TDD | +| Bandwidth | | BW of Active BWP Note 1 | +| SCS | kHz | 15 | +| First subcarrier index in the PRB used for CSI-RS | | $k_0=0$ for CSI-RS resource 1,2,3,4 | +| First OFDM symbol in the slot used for CSI-RS | | $l_0 = 5$ for CSI-RS resource 1 and 3
$l_0 = 9$ for CSI-RS resource 2 and 4 | +| Number of CSI-RS ports (X) | | 1 for CSI-RS resource 1,2,3,4 | +| CDM Type | | 'No CDM' for CSI-RS resource 1,2,3,4 | +| Density (p) | | 3 for CSI-RS resource 1,2,3,4 | +| CSI-RS periodicity | slots | 20 for CSI-RS resource 1,2,3,4 | +| EPRE ratio to SSS | dB | $-3$ Note 2 | +| TCI state | | TCI.State.0 | +| Note: | BW of TRS is configured same as the BW size of IAB-MT active BWP in the RRM test cases | | + +**Table G.1.10.1.2-2: CSI-RS for tracking for SCS=30kHz** + +| Parameter | Unit | Value | +|---------------------------------------------------|----------------------------------------------------------------------------------------|--------------------------------------------------------------------------------| +| Reference channel | | TRS.1.2 TDD | +| Bandwidth | | BW of Active BWP Note 1 | +| SCS | kHz | 30 | +| First subcarrier index in the PRB used for CSI-RS | | $k_0=0$ for CSI-RS resource 1,2,3,4 | +| First OFDM symbol in the slot used for CSI-RS | | $l_0 = 5$ for CSI-RS resource 1 and 3
$l_0 = 9$ for CSI-RS resource 2 and 4 | +| Number of CSI-RS ports (X) | | 1 for CSI-RS resource 1,2,3,4 | +| CDM Type | | 'No CDM' for CSI-RS resource 1,2,3,4 | +| Density (p) | | 3 for CSI-RS resource 1,2,3,4 | +| CSI-RS periodicity | slots | 40 for CSI-RS resource 1,2,3,4 | +| EPRE ratio to SSS | dB | -3 Note 2 | +| TCI state | | TCI.State.0 | +| Note 1: | BW of TRS is configured same as the BW size of IAB-MT active BWP in the RRM test cases | | +| Note 2: | Unless otherwise specified in the test case | | + +## G.1.10.2 Configuration of CSI-RS for tracking for FR2-1 + +### G.1.10.2.1 TDD + +**Table G.1.10.2.1-1: CSI-RS for tracking for SCS=120kHz Set 1** + +| Parameter | Unit | Value | +|---------------------------------------------------|-----------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------| +| Reference channel | | TRS.2.1 TDD | +| Bandwidth | | BW of Active BWP Note 1,3 | +| SCS | kHz | 120 | +| First subcarrier index in the PRB used for CSI-RS | | $k_0=0$ for CSI-RS resource 1,2,3,4 | +| First OFDM symbol in the slot used for CSI-RS | | $l_0 = 1$ for CSI-RS resource 1 and 3
$l_0 = 5$ for CSI-RS resource 2 and 4 | +| Number of CSI-RS ports (X) | | 1 for CSI-RS resource 1,2,3,4 | +| CDM Type | | 'No CDM' for CSI-RS resource 1,2,3,4 | +| Density (p) | | 3 for CSI-RS resource 1,2,3,4 | +| CSI-RS periodicity | slots | 80 for CSI-RS resource 1,2,3,4 | +| EPRE ratio to SSS | dB | -3 Note 2 | +| TCI state | | TCI.State.0 | +| Note 1: | BW of TRS is configured same as the BW size of IAB-MT active BWP in the RRM test cases | | +| Note 2: | Unless otherwise specified in the test case | | +| Note 3: | If active BWP is larger than 52RBs, BW of TRS is configured as 52RBs. Otherwise, same as active BWP size. | | + +**Table G.1.10.2.1-2: CSI-RS for tracking for SCS=120kHz Set 2** + +| Parameter | Unit | Value | +|---------------------------------------------------|-----------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------| +| Reference channel | | TRS.2.2 TDD | +| Bandwidth | | BW of Active BWP Note 1,3 | +| SCS | kHz | 120 | +| First subcarrier index in the PRB used for CSI-RS | | $k_0=0$ for CSI-RS resource 1,2,3,4 | +| First OFDM symbol in the slot used for CSI-RS | | $l_0 = 2$ for CSI-RS resource 1 and 3
$l_0 = 6$ for CSI-RS resource 2 and 4 | +| Number of CSI-RS ports (X) | | 1 for CSI-RS resource 1,2,3,4 | +| CDM Type | | 'No CDM' for CSI-RS resource 1,2,3,4 | +| Density (p) | | 3 for CSI-RS resource 1,2,3,4 | +| CSI-RS periodicity | slots | 80 for CSI-RS resource 1,2,3,4 | +| EPRE ratio to SSS | dB | -3 Note 2 | +| TCI state | | TCI.State.1 | +| Note 1: | BW of TRS is configured same as the BW size of IAB-MT active BWP in the RRM test cases | | +| Note 2: | Unless otherwise specified in the test case | | +| Note 3: | If active BWP is larger than 52RBs, BW of TRS is configured as 52RBs. Otherwise, same as active BWP size. | | + +## G.2 IAB-MT RRM test cases + +### G.2.1 RRC\_CONNECTED state mobility for IAB-MTs + +#### G.2.1.1 RRC Connection Mobility Control + +##### G.2.1.1.1 RRC Re-establishment + +###### G.2.1.1.1.1 Inter-frequency RRC Re-establishment in FR1 for LA IAB-MT + +###### G.2.1.1.1.1.1 Test Purpose and Environment + +The purpose is to verify that the NR inter-frequency RRC re-establishment delay in FR1 to an unknown target cell is within the specified limits. These tests will verify the requirements in clause 12.1.1.1. This test case is applicable only for local area IAB-MT and for IAB type 1-H. + +The test parameters are given in table G.2.1.1.1.1.1-1, table G.2.1.1.1.1.1-2 and table G.2.1.1.1.1.1-3 below. The test consists of 3 successive time periods, with time duration of T1, T2 and T3 respectively. At the start of time period T2, cell 1, which is the active cell, becomes inactive. The time period T3 starts after the occurrence of the radio link failure. During T1, the IAB-MT shall be configured with the carrier frequency of cell 2 (with RF Channel Number #2) to ensure that the IAB-MT has the context of the carrier frequency of cell 2 by the end of T1. + +**Table G.2.1.1.1.1.1-1: Supported test configurations** + +| Configuration | Description of serving cell | Description of target cell | +|---------------------------------------------------------------------------------------------|---------------------------------------------------|---------------------------------------------------| +| 1 | 15 kHz SSB SCS, 10 MHz bandwidth, TDD duplex mode | 15 kHz SSB SCS, 10 MHz bandwidth, TDD duplex mode | +| 2 | 30 kHz SSB SCS, 40 MHz bandwidth, TDD duplex mode | 30 kHz SSB SCS, 40 MHz bandwidth, TDD duplex mode | +| Note: The IAB-MT is only required to be tested in one of the supported test configurations. | | | + +**Table G.2.1.1.1.1.1-2: General test parameters for NR inter-frequency RRC Re-establishment test case in FR1** + +| Parameter | | Unit | Test configuration | Value | Comment | +|----------------------------|-----------------|------|--------------------|---------------------------|---------------------------------------------------------------| +| Initial condition | Active cell | | 1, 2 | Cell1 | | +| | Neighbour cells | | 1, 2 | Cell2 | | +| Final condition | Active cell | | 1, 2 | Cell2 | | +| RF Channel Number | | | 1, 2 | 1, 2 | | +| Time offset between cells | | | 1, 2 | 3 µs | Synchronous cells | +| N310 | | - | 1, 2 | 1 | Maximum consecutive out-of-sync indications from lower layers | +| N311 | | - | 1, 2 | 1 | Minimum consecutive in-sync indications from lower layers | +| T310 | | ms | 1, 2 | 0 | Radio link failure timer; T310 is disabled | +| T311 | | ms | 1, 2 | 30000 | RRC re-establishment timer | +| Access Barring Information | | - | 1, 2 | Not Sent | No additional delays in random access procedure. | +| SSB configuration | | | 1 | SSB.1 FR1 | | +| | | | 2 | SSB.2 FR1 | | +| SMTC configuration | | | 1 | SMTC pattern 1 | | +| | | | 2 | SMTC pattern 1 | | +| DRX cycle length | | s | 1, 2 | OFF | | +| PRACH configuration | | | 1, 2 | FR1 PRACH configuration 1 | TBD | +| T1 | | s | 1, 2 | 20 | | +| T2 | | ms | 1, 2 | 1000 | Time for the IAB-MT to detect RLF | +| T3 | | s | 1, 2 | 20 | | + +**Table G.2.1.1.1.1-3: Cell specific test parameters for NR inter-frequency RRC Re-establishment test case in FR1** + +| Parameter | Unit | Test configuration | Cell 1 | | | Cell 2 | | | | | | | | | +|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|---------------------|-----------|-----------|---------------------|-----------|-----------|--|--|--|--|--|--| +| | | | T1 | T2 | T3 | T1 | T2 | T3 | | | | | | | +| RF Channel Number | | 1, 2 | 1 | | | 2 | | | | | | | | | +| TDD configuration | | 1 | TDDConf.1.1 | | | TDDConf.1.1 | | | | | | | | | +| | | 2 | TDDConf.2.1 | | | TDDConf.2.1 | | | | | | | | | +| PDSCH RMC configuration | | 1 | SR.1.1 FDD | | | N/A | | | | | | | | | +| | | 2 | SR.1.1 TDD | | | | | | | | | | | | +| RMSI CORESET RMC configuration | | 1 | CR.1.1 TDD | | | CR.1.1 TDD | | | | | | | | | +| | | 2 | CR.2.1 TDD | | | CR.2.1 TDD | | | | | | | | | +| Dedicated CORESET RMC configuration | | 1 | CCR.1.1 TDD | | | CCR.1.1 TDD | | | | | | | | | +| | | 2 | CCR.2.1 TDD | | | CCR.2.1 TDD | | | | | | | | | +| OCNG Pattern | | 1, 2 | OP.1 defined in TBD | | | OP.1 defined in TBD | | | | | | | | | +| TRS configuration | | 1 | TRS.1.1 TDD | | | N/A | | | | | | | | | +| | | 2 | TRS.1.2 TDD | | | | | | | | | | | | +| Initial DL BWP configuration | | 1, 2 | DLBWP.0 | | | DLBWP.0 | | | | | | | | | +| Initial UL BWP configuration | | 1, 2 | ULBWP.0 | | | ULBWP.0 | | | | | | | | | +| Active DL BWP configuration | | 1, 2 | DLBWP.1.1 | N/A | N/A | N/A | N/A | DLBWP.1.1 | | | | | | | +| Active UL BWP configuration | | 1, 2 | ULBWP.1.1 | N/A | N/A | N/A | N/A | ULBWP.1.1 | | | | | | | +| RLM-RS | | 1, 2 | SSB | | | SSB | | | | | | | | | +| Note2 | dB | 1, 2 | 4 | -infinity | -infinity | -infinity | -infinity | 7 | | | | | | | +| | dBm/SCS | 1 | -98 | | | | | | | | | | | | +| Note2 | dBm/15 kHz | 2 | -95 | | | | | | | | | | | | +| | dB | 1, 2 | 4 | -infinity | -infinity | -infinity | -infinity | 7 | | | | | | | +| SS-RSRP Note3 | dBm/SCS | 1 | -94 | -infinity | -infinity | -infinity | -infinity | -91 | | | | | | | +| | dBm/SCS | 2 | -91 | -infinity | -infinity | -infinity | -infinity | -88 | | | | | | | +| Io | dBm/9.36 MHz | 1 | -64.59 | -70.05 | -70.05 | -70.05 | -70.05 | -62.26 | | | | | | | +| | dBm/38.16 MHz | 2 | -58.50 | -63.94 | -63.94 | -63.94 | -63.94 | -56.15 | | | | | | | +| Propagation Condition | | 1, 2 | AWGN | | | | | | | | | | | | +| Note 1: | OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral density is achieved for all OFDM symbols. | | | | | | | | | | | | | | +| Note 2: | Interference from other cells and noise sources not specified in the test is assumed to be constant over subcarriers and time and shall be modelled as AWGN of appropriate power for to be fulfilled. | | | | | | | | | | | | | | +| Note 3: | SS-RSRP levels have been derived from other parameters for information purposes. They are not settable parameters themselves. | | | | | | | | | | | | | | + +**G.2.1.1.1.1.2 Test Requirements** + +The RRC re-establishment delay is defined as the time from the start of time period T3, to the moment when the IAB-MT starts to send PRACH preambles to cell 2 for sending the *RRCREestablishmentRequest* message to cell 2. + +The RRC re-establishment delay to an unknown NR inter frequency cell shall be less than 14.5 s. + +The rate of correct RRC re-establishments observed during repeated tests shall be at least 90%. + +NOTE: The RRC re-establishment delay in the test is derived from the following expression: + +Where: + +$T_{UL\_grant}$ = It is the time required to acquire and process uplink grant from the target cell. The PRACH reception is used as a trigger for the completion of the test; hence $T_{UL\_grant}$ is not used. + +$N_{\text{freq}} = 2$ + +$T_{\text{identify\_intra\_NR}} = 6400 \text{ ms}$ + +$T_{\text{identify\_inter\_NR}} = 6400 \text{ ms}$ + +$T_{\text{SI}} = 1280 \text{ ms}$ ; it is the time required for receiving all the relevant system information as defined in TS 38.331 for the target inter-frequency NR cell. + +$T_{\text{PRACH}} = 15 \text{ ms}$ ; it is the additional delay caused by the random access procedure. + +This gives a total of 14495 ms, allow 14.5 s in the test case. + +#### G.2.1.1.1.2 Intra-frequency RRC Re-establishment in FR1 without serving cell timing for LA IAB-MT + +##### G.2.1.1.1.2.1 Test Purpose and Environment + +The purpose is to verify that the NR intra-frequency RRC re-establishment delay in FR1 without serving cell timing is within the specified limits. These tests will verify the requirements in clause 12.1.1.1. This test case is applicable only for local area IAB-MT and for IAB type 1-H. + +The test parameters are given in table G.2.1.1.1.2.1-1, table G.2.1.1.1.2.1-2 and table G.2.1.1.1.2.1-3 below. The test consists of 3 successive time periods, with time duration of T1, T2 and T3 respectively. At the start of time period T2, cell 1, which is the active cell, is deactivated. The time period T3 starts after the occurrence of the radio link failure. + +**Table G.2.1.1.1.2.1-1: Supported test configurations** + +| Configuration | Description | +|---------------|---------------------------------------------------------------------------------------| +| 1 | 15 kHz SSB SCS, 10 MHz bandwidth, TDD duplex mode | +| 2 | 30 kHz SSB SCS, 40 MHz bandwidth, TDD duplex mode | +| Note: | The IAB-MT is only required to be tested in one of the supported test configurations. | + +**Table G.2.1.1.1.2.1-2: General test parameters for NR intra-frequency RRC Re-establishment test case in FR1** + +| Parameter | | Unit | Test configuration | Value | Comment | +|----------------------------|-----------------|------|--------------------|---------------------------|----------------------------------------------------------------------| +| Initial condition | Active cell | | 1, 2 | Cell1 | | +| | Neighbour cells | | 1, 2 | Cell2 | | +| Final condition | Active cell | | 1, 2 | Cell2 | | +| RF Channel Number | | | 1, 2 | 1, 2 | | +| Time offset between cells | | | 1, 2 | 3 $\mu$ s | Synchronous cells | +| N310 | | - | 1, 2 | 1 | Maximum consecutive out-of-sync indications from lower layers | +| N311 | | - | 1, 2 | 1 | Minimum consecutive in-sync indications from lower layers | +| T310 | | ms | 1, 2 | 6000 | Radio link failure timer configured by RLF-TimersAndConstants | +| T311 | | ms | 1, 2 | 15000 | RRC re-establishment timer | +| Access Barring Information | | - | 1, 2 | Not Sent | No additional delays in random access procedure. | +| SSB configuration | | | 1 | SSB.1 FR1 | | +| | | | 2 | SSB.2 FR1 | | +| SMTC configuration | | | 1 | SMTC pattern 1 | | +| | | | 2 | SMTC pattern 1 | | +| DRX cycle length | | s | 1, 2 | OFF | | +| PRACH configuration | | | 1, 2 | FR1 PRACH configuration 1 | TBD | +| T1 | | s | 1, 2 | 10 | | +| T2 | | s | 1, 2 | 7 | Time for the IAB-MT to detect RLF | +| T3 | | s | 1, 2 | 10 | | + +**Table G.2.1.1.1.2.1-3: Cell specific test parameters for NR intra-frequency RRC Re-establishment test case in FR1** + +| Parameter | Unit | Test configuration | Cell 1 | | | Cell 2 | | | +|-------------------------------------|--------------|--------------------|---------------------|-----------|-----------|---------------------|-----------|--------| +| | | | T1 | T2 | T3 | T1 | T2 | T3 | +| TDD configuration | | 1 | TDDConf.1.1 | | | TDDConf.1.1 | | | +| | | 2 | TDDConf.2.1 | | | TDDConf.2.1 | | | +| PDSCH RMC configuration | | 1 | SR.1.1 TDD | | | N/A | | | +| | | 2 | SR.2.1 TDD | | | | | | +| RMSI CORESET RMC configuration | | 1 | CR.1.1 TDD | | | CR.1.1 TDD | | | +| | | 2 | CR.2.1 TDD | | | CR.2.1 TDD | | | +| Dedicated CORESET RMC configuration | | 1 | CCR.1.1 TDD | | | CCR.1.1 TDD | | | +| | | 2 | CCR.2.1 TDD | | | CCR.2.1 TDD | | | +| OCNG Pattern | | 1, 2 | OP.1 defined in TBD | | | OP.1 defined in TBD | | | +| Initial DL BWP configuration | | 1, 2 | DLBWP.0.1 | | | DLBWP.0.1 | | | +| Initial UL BWP configuration | | 1, 2 | ULBWP.0.1 | | | ULBWP.0.1 | | | +| RLM-RS | | 1, 2 | SSB | | | SSB | | | +| | dB | 1, 2 | 4 | -infinity | -infinity | -infinity | -infinity | 4 | +| Note2 | dBm/SCS | 1 | -98 | | | | | | +| | | 2 | -95 | | | | | | +| Note2 | dBm/15 kHz | 1, 2 | -98 | | | | | | +| | dB | 1, 2 | 4 | -infinity | -infinity | -infinity | -infinity | 4 | +| SS-RSRP Note3 | dBm/SCS | 1 | -94 | -infinity | -infinity | -infinity | -infinity | -94 | +| | | 2 | -91 | -infinity | -infinity | -infinity | -infinity | -91 | +| Io | dBm/9.36 MHz | 1 | -64.59 | -infinity | -infinity | -infinity | -infinity | -64.59 | +| | dBm/9.36 MHz | 2 | -58.50 | -infinity | -infinity | -infinity | -infinity | -58.50 | +| Propagation Condition | | 1, 2 | AWGN | | | | | | + +Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral density is achieved for all OFDM symbols. +Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over subcarriers and time and shall be modelled as AWGN of appropriate power for to be fulfilled. +Note 3: SS-RSRP levels have been derived from other parameters for information purposes. They are not settable parameters themselves. + +**G.2.1.1.1.2.2 Test Requirements** + +The RRC re-establishment delay is defined as the time from the start of time period T3, to the moment when the IAB-MT starts to send PRACH preambles to cell 2 for sending the *RRCREestablishmentRequest* message to cell 2. + +The RRC re-establishment delay to an unknown NR intra frequency cell without serving cell timing shall be less than 8.1 s. + +The rate of correct RRC re-establishments observed during repeated tests shall be at least 90%. + +NOTE: The RRC re-establishment delay in the test is derived from the following expression: + +Where: + +$T_{UL\_grant}$ = It is the time required to acquire and process uplink grant from the target cell. The PRACH reception is used as a trigger for the completion of the test; hence $T_{UL\_grant}$ is not used. + +$$N_{freq} = 1$$ + +$$T_{identify\_intra\_NR} = 6400 \text{ ms}$$ + +$T_{SI} = 1280$ ms; it is the time required for receiving all the relevant system information as defined in TS 38.331 [2] for the target intra-frequency NR cell. + +$T_{PRACH} = 15$ ms; it is the additional delay caused by the random access procedure. + +This gives a total of 8095 ms, allow 8.1 s in the test case. + +#### G.2.1.1.1.3 Inter-frequency RRC Re-establishment in FR2-1 for LA IAB-MT + +##### G.2.1.1.1.3.1 Test Purpose and Environment + +The purpose is to verify that the NR inter-frequency RRC re-establishment delay in FR2-1 without known target cell is within the specified limits. These tests will verify the requirements in clause 12.1.1.1. This test case is applicable only for local area IAB-MT and for IAB type 2-O. + +The test parameters are given in table G.2.1.1.1.3.1-1, table G.2.1.1.1.3.1-2 and table G.2.1.1.1.3.1-3 below. The test consists of 3 successive time periods, with time duration of T1, T2 and T3 respectively. At the start of time period T2, cell 1, which is the active cell, becomes inactive. The time period T3 starts after the occurrence of the radio link failure. During T1, the IAB-MT shall be configured with the carrier frequency of cell 2 (with RF Channel Number #2) to ensure that the IAB-MT has the context of the carrier frequency of cell 2 by the end of T1. + +**Table G.2.1.1.1.3.1-1: Supported test configurations** + +| Configuration | Description | +|---------------|--------------------------------------------------------| +| 1 | NR 120 kHz SSB SCS, 100 MHz bandwidth, TDD duplex mode | + +**Table G.2.1.1.1.3.1-2: General test parameters for NR inter-frequency RRC Re-establishment test case in FR2-1** + +| Parameter | Unit | Test configuration | Value | Comment | +|----------------------------|-----------------|--------------------|-----------------------------|---------------------------------------------------------------| +| Initial condition | Active cell | 1 | Cell1 | | +| | Neighbour cells | 1 | Cell2 | | +| Final condition | Active cell | 1 | Cell2 | | +| RF Channel Number | | 1 | 1, 2 | | +| Time offset between cells | | 1 | 3 $\mu$ s | Synchronous cells | +| N310 | - | 1 | 1 | Maximum consecutive out-of-sync indications from lower layers | +| N311 | - | 1 | 1 | Minimum consecutive in-sync indications from lower layers | +| T310 | ms | 1 | 0 | Radio link failure timer; T310 is disabled | +| T311 | ms | 1 | 30000 | RRC re-establishment timer | +| Access Barring Information | - | 1 | Not Sent | No additional delays in random access procedure. | +| SSB configuration | | 1 | SSB.1 FR2-1 | | +| | | 1 | SMTC pattern 1 | | +| DRX cycle length | s | 1 | OFF | | +| PRACH configuration | | 1 | FR2-1 PRACH configuration 1 | Table TBD | +| T1 | s | 1 | 10 | | +| T2 | ms | 1 | 4800 | Time for the IAB-MT to detect RLF | +| T3 | s | 1 | 20 | | + +**Table G.2.1.1.1.3.1-3: Cell specific test parameters for NR inter-frequency RRC Re-establishment test case in FR2-1** + +| Parameter | Unit | Test configuration | Cell 1 | | | Cell 2 | | | | | | | | | +|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|----------------------------------------|-----------|-----------|---------------------|-----------|--------|--|--|--|--|--|--| +| | | | T1 | T2 | T3 | T1 | T2 | T3 | | | | | | | +| AoA setup | | 1 | Setup 2 as specified in clause G.1.8.2 | | | | | | | | | | | | +| TDD configuration | | 1 | TDDConf.3.1 | | | TDDConf.3.1 | | | | | | | | | +| PDSCH RMC configuration | | 1 | SR.3.1 TDD | | | N/A | | | | | | | | | +| RMSI CORESET RMC configuration | | 1 | CR.3.1 TDD | | | CR.3.1 TDD | | | | | | | | | +| Dedicated CORESET RMC configuration | | 1 | CCR.3.1 TDD | | | CCR.3.1 TDD | | | | | | | | | +| TRS configuration | | 1 | TRS.2.1 TDD | | | N/A | | | | | | | | | +| PDSCH/PDCCH TCI state | | 1 | TCI.State.2 | | | N/A | | | | | | | | | +| OCNG Pattern | | 1 | OP.1 defined in TBD | | | OP.1 defined in TBD | | | | | | | | | +| Initial DL BWP configuration | | 1 | DLBWP.0.1 | | | DLBWP.0.1 | | | | | | | | | +| Initial UL BWP configuration | | 1 | ULBWP.0.1 | | | ULBWP.0.1 | | | | | | | | | +| RLM-RS | | 1 | SSB | | | SSB | | | | | | | | | +| Note2 | dB | 1 | 5 | -infinity | -infinity | -infinity | -infinity | 8 | | | | | | | +| Note2 | dBm/15 kHz | 1 | -98 | | | | | | | | | | | | +| Note2 | dBm/SCS | 1 | -89 | | | | | | | | | | | | +| | dB | 1 | 5 | -infinity | -infinity | -infinity | -infinity | 8 | | | | | | | +| SS-RSRP Note3 | dBm/SCS | 1 | -84 | -infinity | -infinity | -infinity | -infinity | -81 | | | | | | | +| Io | dBm/95.04 MHz | 1 | -53.82 | -infinity | -infinity | -infinity | -infinity | -51.37 | | | | | | | +| Propagation Condition | | 1 | AWGN | | | | | | | | | | | | +| Note 1: | OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral density is achieved for all OFDM symbols. | | | | | | | | | | | | | | +| Note 2: | Interference from other cells and noise sources not specified in the test is assumed to be constant over subcarriers and time and shall be modelled as AWGN of appropriate power for to be fulfilled. | | | | | | | | | | | | | | +| Note 3: | SS-RSRP levels have been derived from other parameters for information purposes. They are not settable parameters themselves. | | | | | | | | | | | | | | +| Note 4: | Void | | | | | | | | | | | | | | + +**G.2.1.1.1.3.2 Test Requirements** + +The RRC re-establishment delay is defined as the time from the start of time period T3, to the moment when the IAB-MT starts to send PRACH preambles to cell 2 for sending the *RRCREestablishmentRequest* message to cell 2. + +The RRC re-establishment delay to an unknown NR inter frequency cell shall be less than 18 s. + +The rate of correct RRC re-establishments observed during repeated tests shall be at least 90%. + +NOTE: The RRC re-establishment delay in the test is derived from the following expression: + +Where: + +$T_{UL\_grant}$ = It is the time required to acquire and process uplink grant from the target cell. The PRACH reception is used as a trigger for the completion of the test; hence $T_{UL\_grant}$ is not used. + +$$N_{freq} = 2$$ + +$$T_{identify\_intra\_NR} = 8000 \text{ ms}$$ + +$$T_{identify\_inter\_NR} = 8000 \text{ ms}$$ + +$T_{SI} = 1280$ ms; it is the time required for receiving all the relevant system information as defined in TS 38.331 for the target inter-frequency NR cell. + +$T_{PRACH} = 15$ ms; it is the additional delay caused by the random access procedure. + +This gives a total of 17695 ms, allow 18 s in the test case. + +G.2.1.1.1.4 Intra-frequency RRC Re-establishment in FR2-1 without serving cell timing for LA IAB-MT + +G.2.1.1.1.4.1 Test Purpose and Environment + +The purpose is to verify that the NR intra-frequency RRC re-establishment delay in FR2-1 without serving cell timing is within the specified limits. These tests will verify the requirements in clause 12.1.1.1. This test case is applicable only for local area IAB-MT and for IAB type 2-O. + +The test parameters are given in table G.2.1.1.1.4.1-1, table G.2.1.1.1.4.1-2 and table G.2.1.1.1.4.1-3 below. The test consists of 3 successive time periods, with time duration of T1, T2 and T3 respectively. At the start of time period T2, cell 1, which is the active cell, is deactivated. The time period T3 starts after the occurrence of the radio link failure. + +**Table G.2.1.1.1.4.1-1: Supported test configurations** + +| Configuration | Description | +|---------------|-----------------------------------------------------| +| 1 | 120 kHz SSB SCS, 100 MHz bandwidth, TDD duplex mode | + +**Table G.2.1.1.1.4.1-2: General test parameters for NR intra-frequency RRC Re-establishment test case in FR2-1** + +| Parameter | Unit | Test configuration | Value | Comment | +|----------------------------|-----------------|--------------------|-----------------------------|----------------------------------------------------------------------| +| Initial condition | Active cell | 1 | Cell1 | | +| | Neighbour cells | 1 | Cell2 | | +| Final condition | Active cell | 1 | Cell2 | | +| RF Channel Number | | 1 | 1 | | +| Time offset between cells | | 1 | 3 $\mu$ s | Synchronous cells | +| N310 | - | 1 | 1 | Maximum consecutive out-of-sync indications from lower layers | +| N311 | - | 1 | 1 | Minimum consecutive in-sync indications from lower layers | +| T310 | ms | 1 | 6000 | Radio link failure timer configured by RLF-TimersAndConstants | +| T311 | ms | 1 | 30000 | RRC re-establishment timer | +| Access Barring Information | - | 1 | Not Sent | No additional delays in random access procedure. | +| SSB configuration | | 1 | SSB.1 FR2-1 | | +| SMTC configuration | | 1 | SMTC pattern 1 | | +| DRX cycle length | s | 1 | OFF | | +| PRACH configuration | | 1 | FR2-1 PRACH configuration 1 | Table TBD | +| T1 | s | 1 | 10 | | +| T2 | s | 1 | 10800 | Time for the IAB-MT to detect RLF | +| T3 | s | 1 | 30 | | + +**Table G.2.1.1.1.4.1-3: Cell specific test parameters for NR intra-frequency RRC Re-establishment test case in FR2-1** + +| Parameter | Unit | Test configuration | Cell 1 | | | Cell 2 | | | | | | | | | +|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|----------------------------------------|-----------|-----------|------------------------|-----------|--------|--|--|--|--|--|--| +| | | | T1 | T2 | T3 | T1 | T2 | T3 | | | | | | | +| AoA setup | | 1 | Setup 2 as specified in clause G.1.8.2 | | | | | | | | | | | | +| TDD configuration | | 1 | TDDConf.3.1 | | | TDDConf.3.1 | | | | | | | | | +| | | 1 | SR.3.1 TDD | | | N/A | | | | | | | | | +| RMSI CORESET RMC configuration | | 1 | CR.3.1 FDD | | | CR.3.1 FDD | | | | | | | | | +| Dedicated CORESET RMC configuration | | 1 | CCR.3.1 FDD | | | CCR.3.1 FDD | | | | | | | | | +| TRS configuration | | 1 | TRS.2.1 TDD | | | N/A | | | | | | | | | +| TCI state | | 1 | CSI-RS.Config.0 | | | N/A | | | | | | | | | +| OCNG Pattern | | 1 | OP.1 defined in TBD | | | OP.1 defined in TBD | | | | | | | | | +| Initial DL BWP configuration | | 1 | DLBWP.0.1 | | | DLBWP.0.1 | | | | | | | | | +| Initial UL BWP configuration | | 1 | ULBWP.0.1 | | | ULBWP.0.1 | | | | | | | | | +| RLM-RS | | 1 | SSB | | | SSB | | | | | | | | | +| AoA setup | | 1 | Setup 1 defined in TBD | | | Setup 1 defined in TBD | | | | | | | | | +| | dB | 1 | 5 | -infinity | -infinity | -infinity | -infinity | 5 | | | | | | | +| Note2 | dBm/SCS | 1 | -98 | | | | | | | | | | | | +| Note2 | dBm/15 kHz | 1 | -89 | | | | | | | | | | | | +| | dB | 1 | 5 | -infinity | -infinity | -infinity | -infinity | 5 | | | | | | | +| SS-RSRP Note3 | dBm/SCS | 1 | -93 | -infinity | -infinity | -infinity | -infinity | -93 | | | | | | | +| Io | dBm/95.04 MHz | 1 | -62.82 | -infinity | -infinity | -infinity | -infinity | -62.82 | | | | | | | +| Propagation Condition | | 1 | AWGN | | | | | | | | | | | | +| Note 1: | OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral density is achieved for all OFDM symbols. | | | | | | | | | | | | | | +| Note 2: | Interference from other cells and noise sources not specified in the test is assumed to be constant over subcarriers and time and shall be modelled as AWGN of appropriate power for to be fulfilled. | | | | | | | | | | | | | | +| Note 3: | SS-RSRP levels have been derived from other parameters for information purposes. They are not settable parameters themselves. | | | | | | | | | | | | | | +| Note 4: | Void | | | | | | | | | | | | | | + +**G.2.1.1.1.4.2 Test Requirements** + +The RRC re-establishment delay is defined as the time from the start of time period T3, to the moment when the IAB-MT starts to send PRACH preambles to cell 2 for sending the *RRCReestablishmentRequest* message to cell 2. + +The RRC re-establishment delay to an unknown NR intra frequency cell without serving cell timing shall be less than 30 s. + +The rate of correct RRC re-establishments observed during repeated tests shall be at least 90%. + +NOTE: The RRC re-establishment delay in the test is derived from the following expression: + +Where: + +$T_{UL\_grant}$ = It is the time required to acquire and process uplink grant from the target cell. The PRACH reception is used as a trigger for the completion of the test; hence $T_{UL\_grant}$ is not used. + +$$N_{freq} = 1$$ + +$$T_{identify\_intra\_NR} = 28160 \text{ ms}$$ + +$T_{SI} = 1280 \text{ ms}$ ; it is the time required for receiving all the relevant system information as defined in TS 38.331 [2] for the target intra-frequency NR cell. + +$T_{PRACH} = 15$ ms; it is the additional delay caused by the random access procedure. + +This gives a total of 29855 ms, allow 30 s in the test case. + +#### G.2.1.1.2 RRC Connection Release with Redirection + +##### G.2.1.1.2.1 Redirection from NR in FR1 to NR in FR1 + +###### G.2.1.1.2.1.1 Test Purpose and Environment + +This test is to verify RRC connection release with redirection from NR to NR requirements specified in clause 12.1.1.3. + +###### G.2.1.1.2.1.2 Test Parameters + +Supported test configurations are shown in table G.2.1.1.2.1.2-1. The time delay is tested by using the parameters in table G.2.1.1.2.1.2-2, and G.2.1.1.2.1.2-3. + +The test consists of two successive time periods, with time duration of T1, and T2 respectively. The *RRCRelease* message shall be sent to the IAB-MT during period T1 and the start of T2 is the instant when the last TTI containing the RRC message is sent to the IAB-MT. Prior to time duration T2, the IAB-MT shall not have any timing information of Cell 2. Cell 2 is powered up at the beginning of the T2. + +**Table G.2.1.1.2.1.2-1: Redirection from NR to NR test configurations** + +| Config | Description | +|----------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------| +| 1 | Source cell: NR 15 kHz SSB SCS, TDD duplex mode
Target cell: NR 15 kHz SSB SCS, TDD duplex mode | +| 2 | Source cell: NR 30 kHz SSB SCS, TDD duplex mode
Target cell: NR 30 kHz SSB SCS, TDD duplex mode | +| Note 1: The IAB-MT is only required to be tested in one of the supported test configurations | | + +**Table G.2.1.1.2.1.2-2: General test parameters for Redirection from NR to NR test case** + +| Parameter | Unit | Value | Comment | +|----------------------------|-------------------|-----------|--------------------------------------------------| +| Initial conditions | Active cell | Cell 1 | | +| | Neighbouring cell | Cell 2 | | +| Final condition | Active cell | Cell 2 | | +| Filter coefficient | | 0 | L3 filtering is not used | +| Access Barring Information | - | Not Sent | No additional delays in random access procedure. | +| Time offset between cells | | 3 $\mu$ s | Synchronous cells | +| T1 | s | 5 | | +| T2 | s | 8 | | + +**Table G.2.1.1.2.1.2-3: Cell specific test parameters for Redirection from NR to NR test case** + +| Parameter | | Unit | Cell 1 | | Cell 2 | | | | | | | | | +|------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|----------------|-------|-----------|-------|--|--|--|--|--|--|--| +| | | | T1 | T2 | T1 | T2 | | | | | | | | +| NR RF Channel Number | | | 1 | | 2 | | | | | | | | | +| BWP BW | Config 1 | MHz | DLBWP.1.1 | | | | | | | | | | | +| | Config 2 | | DLBWP.1.1 | | | | | | | | | | | +| DRx Cycle | | ms | Not Applicable | | | | | | | | | | | +| PDSCH Reference measurement channel | Config 1 | | SR.1.1 TDD | | | | | | | | | | | +| | Config 2 | | SR 2.1 TDD | | | | | | | | | | | +| CORESET Reference Channel | Config 1 | | CR.1.1 TDD | | | | | | | | | | | +| | Config 2 | | CR 2.1 TDD | | | | | | | | | | | +| OCNG Patterns | | | OCNG pattern 1 | | | | | | | | | | | +| SSB configuration | Config 1 | | SSB.1 FR1 | | | | | | | | | | | +| | Config 2 | | SSB.2 FR1 | | | | | | | | | | | +| SMTC configuration | Config 1 | | SMTC.1 FR1 | | | | | | | | | | | +| | Config 2 | | SMTC.2 FR1 | | | | | | | | | | | +| PDSCH/PDCCH subcarrier spacing | Config 1 | kHz | 15 kHz | | | | | | | | | | | +| | Config 2 | | 30 kHz | | | | | | | | | | | +| PUCCH/PUSCH subcarrier spacing | Config 1 | kHz | 15 kHz | | | | | | | | | | | +| | Config 2 | | 30 kHz | | | | | | | | | | | +| BWP configuration | Initial DL BWP | | DLBWP.0.1 | | | | | | | | | | | +| | Dedicated DL BWP | | DLBWP.1.1 | | | | | | | | | | | +| | Initial UL BWP | | ULBWP.0.1 | | | | | | | | | | | +| | Dedicated UL BWP | | ULBWP.1.1 | | | | | | | | | | | +| EPRE ratio of PSS to SSS | | dB | 0 | | | | | | | | | | | +| EPRE ratio of PBCH DMRS to SSS | | | | | | | | | | | | | | +| EPRE ratio of PBCH to PBCH DMRS | | | | | | | | | | | | | | +| EPRE ratio of PDCCH DMRS to SSS | | | | | | | | | | | | | | +| EPRE ratio of PDCCH to PDCCH DMRS | | | | | | | | | | | | | | +| EPRE ratio of PDSCH DMRS to SSS | | | | | | | | | | | | | | +| EPRE ratio of PDSCH to PDSCH | | | | | | | | | | | | | | +| EPRE ratio of OCNG DMRS to SSS (Note 1) | | | | | | | | | | | | | | +| EPRE ratio of OCNG to OCNG DMRS (Note 1) | | | | | | | | | | | | | | +| Note2 | | dBm/15kHz | -98 | | | | | | | | | | | +| Note2 | Config 1 | dBm/SCS | -98 | | | | | | | | | | | +| | Config 2 | | -95 | | | | | | | | | | | +| | | dB | 4 | 4 | -infinity | 4 | | | | | | | | +| | | dB | 4 | 4 | -infinity | 4 | | | | | | | | +| I 0 Note3 | Config 1 | dBm/BW | Note3 | Note3 | Note3 | Note3 | | | | | | | | +| | Config 2 | dBm/BW | Note3 | Note3 | Note3 | Note3 | | | | | | | | +| Propagation condition | | - | AWGN | | | | | | | | | | | +| Note 1: | OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral density is achieved for all OFDM symbols. | | | | | | | | | | | | | +| Note 2: | Interference from other cells and noise sources not specified in the test is assumed to be constant over subcarriers and time and shall be modelled as AWGN of appropriate power for to be fulfilled. | | | | | | | | | | | | | +| Note 3: | I 0 levels have been derived from other parameters for information purposes. They are not settable parameters themselves. | | | | | | | | | | | | | + +#### G.2.1.1.2.1.3 Test Requirements + +The IAB-MT shall start to transmit the PRACH to Cell 2 less than 7480 ms from the beginning of time period T2. The rate of correct RRC connection release redirection to NR observed during repeated tests shall be at least 90%. + +NOTE: The redirection delay can be expressed as: + +$$T_{\text{connection\_release\_redirect\_NR}} = T_{\text{RRC\_procedure\_delay}} + T_{\text{identify-NR}} + T_{\text{SI-NR}} + T_{\text{RACH}},$$ + +where: + +$T_{\text{RRC\_procedure\_delay}} = 110$ ms in the test. + +$T_{\text{identify-NR}} = 5440$ ms in the test. + +$T_{\text{SI-NR}} = 1280$ ms, it is the time required for receiving all the relevant system information. + +$T_{\text{RACH}} = 650$ ms in the test. + +This gives a total of 7480 ms. + +#### G.2.1.1.2.2 Redirection from NR in FR2-1 to NR in FR2-1 + +##### G.2.1.1.2.2.1 Test Purpose and Environment + +This test is to verify RRC connection release with redirection from NR to NR requirements specified in clause 12.1.1.3. + +##### G.2.1.1.2.2.2 Test Parameters + +Supported test configurations are shown in table G.2.1.1.2.2.2-1. The time delay is tested by using the parameters in table G.2.1.1.2.2.2-2, and G.2.1.1.2.2.2-3. + +The test consists of two successive time periods, with time duration of T1, and T2 respectively. The *RRCRelease* message shall be sent to the IAB-MT during period T1 and the start of T2 is the instant when the last TTI containing the RRC message is sent to the IAB-MT. Prior to time duration T2, the IAB-MT shall not have any timing information of Cell 2. Cell 2 is powered up at the beginning of the T2. + +**Table G.2.1.1.2.2.2-1: Redirection from NR to NR test configurations** + +| Config | Description | +|--------|------------------------------------------------------------------------------------------------------| +| 1 | Source cell: NR 120 kHz SSB SCS, TDD duplex mode
Target cell: NR 120 kHz SSB SCS, TDD duplex mode | + +**Table G.2.1.1.2.2.2-2: General test parameters for Redirection from NR to NR test case** + +| Parameter | Unit | Value | Comment | +|----------------------------|-------------------|-----------|--------------------------------------------------| +| Initial conditions | Active cell | Cell 1 | | +| | Neighbouring cell | Cell 2 | | +| Final condition | Active cell | Cell 2 | | +| Filter coefficient | | 0 | L3 filtering is not used | +| Access Barring Information | - | Not Sent | No additional delays in random access procedure. | +| Time offset between cells | | 3 $\mu$ s | Synchronous cells | +| T1 | s | 5 | | +| T2 | s | 10 | | + +**Table G.2.1.1.2.2.2-3: Cell specific test parameters for Redirection from NR to NR test case** + +| Parameter | Unit | Cell 1 | | Cell 2 | | | | | | +|-------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|-------|-----------|-------|--|--|--|--| +| | | T1 | T2 | T1 | T2 | | | | | +| AoA setup | | 1 AoA as defined in G.1.8 | | | | | | | | +| NR RF Channel Number | | 1 | | 2 | | | | | | +| Duplex mode | | TDD | | | | | | | | +| BWP BW | MHz | DLBWP.1.1 | | | | | | | | +| DRx Cycle | ms | Not Applicable | | | | | | | | +| PDSCH Reference measurement channel | | SR3.1 TDD | | | | | | | | +| CORESET Reference Channel | | CR3.1 TDD | | | | | | | | +| OCNG Patterns | | OCNG pattern 1 | | | | | | | | +| SMTC configuration Note 6 | | SMTC.1 FR2-1 | | | | | | | | +| PDSCH/PDCCH subcarrier spacing | kHz | 120 kHz | | | | | | | | +| PUCCH/PUSCH subcarrier spacing | kHz | 120 kHz | | | | | | | | +| TRS configuration | | TRS.2.1 TDD | | | | | | | | +| TCI configuration Note 6 | | CSI-RS.Config.0 | | | | | | | | +| BWP configuration | Initial DL BWP | DLBWP.0.1 | | | | | | | | +| | Dedicated DL BWP | DLBWP.1.1 | | | | | | | | +| | Initial UL BWP | ULBWP.0.1 | | | | | | | | +| | Dedicated UL BWP | ULBWP.1.1 | | | | | | | | +| EPRE ratio of PSS to SSS | dB | 0 | | 0 | | | | | | +| EPRE ratio of PBCH DMRS to SSS | | | | | | | | | | +| EPRE ratio of PBCH to PBCH DMRS | | | | | | | | | | +| EPRE ratio of PDCCH DMRS to SSS | | | | | | | | | | +| EPRE ratio of PDCCH to PDCCH DMRS | | | | | | | | | | +| EPRE ratio of PDSCH DMRS to SSS | | | | | | | | | | +| EPRE ratio of PDSCH to PDSCH | | | | | | | | | | +| EPRE ratio of OCNG DMRS to SSS( Note 1 ) | | | | | | | | | | +| EPRE ratio of OCNG to OCNG DMRS ( Note 1 ) | | | | | | | | | | +| Note2 | dBm/15kHz | -104.7 | | -104.7 | | | | | | +| Note2 | Config 1 | dBm/SCS | -95.7 | | -95.7 | | | | | +| | Config 2 | | -95.7 | | -95.7 | | | | | +| | dB | 5 | 5 | -Infinity | 5 | | | | | +| | dB | 5 | 5 | -Infinity | 5 | | | | | +| Io Note3 | Config 1 | dBm/BW | Note3 | Note3 | Note3 | | | | | +| | Config 2 | dBm/BW | Note3 | Note3 | Note3 | | | | | +| Propagation condition | - | AWGN | | | | | | | | +| Note 1: | OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral density is achieved for all OFDM symbols. | | | | | | | | | +| Note 2: | Interference from other cells and noise sources not specified in the test is assumed to be constant over subcarriers and time and shall be modelled as AWGN of appropriate power for to be fulfilled. | | | | | | | | | +| Note 3: | Io levels have been derived from other parameters for information purposes. They are not settable parameters themselves. | | | | | | | | | +| Note 4: | Equivalent power received by an antenna with 0 dBi gain at the centre of the quiet zone | | | | | | | | | +| Note 5: | As observed with 0 dBi gain antenna at the centre of the quiet zone | | | | | | | | | + +**G.2.1.1.2.2.3 Test Requirements** + +The IAB-MT shall start to transmit the PRACH to Cell 2 less than 9080 ms from the beginning of time period T2. + +The rate of correct RRC connection release redirection to NR observed during repeated tests shall be at least 90%. + +NOTE: The redirection delay can be expressed as: + +$$T_{\text{connection\_release\_redirect\_NR}} = T_{\text{RRC\_procedure\_delay}} + T_{\text{identify-NR}} + T_{\text{SI-NR}} + T_{\text{RACH}},$$ + +where: + +$T_{\text{RR\_procedure\_delay}} = 110$ ms in the test. + +$T_{\text{identify-NR}} = 7040$ ms in the test. + +$T_{\text{SI-NR}} = 1280$ ms, it is the time required for receiving all the relevant system information. + +$T_{\text{RACH}} = 650$ ms in the test. + +This gives a total of 9080 ms. + +## G.2.2 Timing + +### G.2.2.1 Transmit timing + +#### G.2.2.1.1 NR IAB-MT Transmit Timing Test for FR1 + +##### G.2.2.1.1.1 Test Purpose and environment + +The purpose of this test is to verify that the IAB-MT can follow frame timing change of the connected gNodeb and that the IAB-MT initial transmit timing accuracy, maximum amount of timing change in one adjustment, minimum and maximum adjustment rate are within the specified limits. This test will verify the requirements in clause 12.2.1.2. Local area IAB-MT type 1-H shall be tested with this test. + +Supported test configurations are shown in Table G.2.2.1.1.1-1. + +**Table G.2.2.1.1.1-1: Supported test configurations for FR1 PCell** + +| Configuration | Description | +|---------------|--------------------------------------------------------------------------------------| +| 1 | NR TDD, SSB SCS 15 kHz, data SCS 15 kHz, BW 10 MHz | +| 2 | NR TDD, SSB SCS 30 kHz, data SCS 30 kHz, BW 40 MHz | +| Note: | The IAB-MT is only required to be tested in one of the supported test configurations | + +For this test a single NR cell (Cell 1) is used. Table G.2.2.1.1.1-2 defines the parameters to be configured and strength of the transmitted signals. The transmit timing is verified by the IAB-MT transmitting SRS using the configuration defined in Table G.2.2.1.1.1-3. + +**Table G.2.2.1.1.1-2: Cell Specific Test Parameters for UL Transmit Timing test** + +| Parameter | Unit | Config | Test1 | +|------------------------------------------|-------------|--------|-----------------------------| +| SSB ARFCN | | 1,2,3 | 1 | +| TDD configuration | | 1 | TDDConf.1.1 | +| | | 2 | TDDConf.1.2 | +| BW channel | MHz | 1 | 10: N RB,c = 52 | +| | | 2 | 10: N RB,c = 52 | +| | | 3 | 40: N RB,c = 106 | +| Initial BWP Configuration | | 1,2,3 | DLBWP.0.1
ULBWP.0.1 | +| Dedicated BWP Configuration | | 1,2,3 | DLBWP.1.1
ULBWP.1.1 | +| DRX Cycle | ms | | N/A | +| PDSCH Reference measurement channel | | 1 | SR.1.1 TDD | +| | | 2 | SR.2.1 TDD | +| RMSI CORESET Reference Channel | | 1 | CR.1.1 TDD | +| | | 2 | CR.2.1 TDD | +| Dedicated CORESET Reference Channel | | 1 | CCR.1.1 TDD | +| | | 2 | CCR.2.1 TDD | +| OCNG Patterns | | 1,2,3 | OP.1 | +| SSB configuration | | 1,2 | SSB.1 FR1 | +| | | 3 | SSB.2 FR1 | +| SMTC Configuration | | 1,2 | SMTC.1 | +| | | 3 | SMTC.2 | +| TRS configuration | | 1 | TRS.1.1 TDD | +| | | 2 | TRS.1.2 TDD | +| EPRE ratio of PSS to SSS | dB | 1,2,3 | 0 | +| EPRE ratio of PBCH DMRS to SSS | | | | +| EPRE ratio of PBCH to PBCH DMRS | | | | +| EPRE ratio of PDCCH DMRS to SSS | | | | +| EPRE ratio of PDCCH to PDCCH DMRS | | | | +| EPRE ratio of PDSCH DMRS to SSS | | | | +| EPRE ratio of PDSCH to PDSCH | | | | +| EPRE ratio of OCNG DMRS to SSS (Note 1) | | | | +| EPRE ratio of OCNG to OCNG DMRS (Note 1) | | | | +| Note2 | dBm/15 kHz | 1,2,3 | -98 | +| Note2 | dBm/SCS | 1,2 | -98 | +| | | 3 | -95 | +| | | 1,2,3 | 3 | +| | | 1,2,3 | 3 | +| SS-RSRP Note3 | dBm/SCS | 1,2 | -95 | +| | | 3 | -92 | +| I o Note3 | dBm/9.36MHz | 1,2 | -65.2 | +| | dBm/38.1MHz | 3 | -59.2 | +| Propagation condition | | 1,2,3 | AWGN | +| SRS Config | | 1,2 | SRSCConf.1 Note5 | +| | | 3 | SRSCConf.1 Note5 | + +| | | +|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Note 1: | OCNG shall be used such that the resources in Cell 1 are fully allocated and a constant total transmitted power spectral density is achieved for all OFDM symbols. | +| Note 2: | Interference from other cells and noise sources not specified in the test is assumed to be constant over subcarriers and time and shall be modelled as AWGN of appropriate power for to be fulfilled. | +| Note 3: | SS-RSRP and Io levels have been derived from other parameters for information purposes. They are not settable parameters themselves. | +| Note 4: | SS-RSRP minimum requirements are specified assuming independent interference and noise at each receiver antenna port. | +| Note 5: | SRS configs are given in Table G.2.2.1.1.1-3 | + +**Table G.2.2.1.1.1-3: SRS Configuration for Timing Accuracy Test** + +| | Field | SRSConf.1 | Comments | +|-----------------|----------------------------------|--------------------------------------------------------------|--------------------| +| SRS-ResourceSet | srs-ResourceSetId | 0 | | +| | srs-ResourceIdList | 0 | | +| | resourceType | Periodic | | +| | Usage | Codebook | | +| SRS-Resource | SRS-ResourceId | 0 | | +| | nrofSRS-Ports | Port1 | | +| | transmissionComb | n2 | | +| | combOffset-n2 | 0 | | +| | cyclicShift-n2 | 0 | | +| | resourceMapping startPosition | 0 | | +| | resourceMapping nrofSymbols | n1 | | +| | resourceMapping repetitionFactor | n1 | | +| | freqDomainPosition | 0 | | +| | freqDomainShift | 0 | | +| | freqHopping c-SRS | 14 for test configuration 1,2
25 for test configuration 3 | Matches $N_{RB,c}$ | +| | freqHopping b-SRS | 0 | | +| | freqHopping b-hop | 0 | | +| | groupOrSequenceHopping | Neither | | +| | resourceType | Periodic | | +| | periodicityAndOffset-p | sl1, 0 | | +| | sequenceId | 0 | Any 10 bit number | + +#### G.2.2.1.1.2 Test requirements + +The test sequence shall be carried out in RRC\_CONNECTED for every test case. + +Following will be the test sequence for this test + +- 1) Setup NR PCell according to parameters given in Table G.2.2.1.1.1-1. +- 2) After connection set up with the cell, the test equipment will verify that the timing of the NR cell is within $(N_{TA} + N_{TA\_offset}) \times T_c \pm T_e$ of the first path (in time) of DL SSB used by the IAB-MT to determine downlink timing is received from the reference cell at the IAB-MT antenna. + - a. The $N_{TA\_offset}$ value (in $T_c$ units) is 25600 + - b. The $T_e$ values depend on the DL and UL SCS for which the test is being run and are given in Table 12.2.1.2-1 +- 3) The test system shall adjust the timing of the DL path by values given in Table G.2.2.1.1.2-1 + +**Table G.2.2.1.1.2-1: Adjustment Value for DL Timing** + +| SCS of SSB signals (KHz) | Adjustment Value | +|--------------------------|--------------------| +| | Test1 | +| 15 | $+64 \cdot 64 T_c$ | +| 30 | $+32 \cdot 64 T_c$ | + +- 4) The test system shall verify that the adjustment step size and the adjustment rate shall be according to requirements specified in clause 12.2.1.2 Table 12.2.1.2.1-1 until the IAB-MT transmit timing offset is within $(N_{TA} + N_{TA\_offset}) \times T_c \pm T_e$ respective to the first path (in time) of DL SSB used by the IAB-MT to determine downlink timing is received from the reference cell at the IAB-MT antenna. +- 5) The test system shall verify that the IAB-MT transmit timing offset stays within $(N_{TA} + N_{TA\_offset}) \times T_c \pm T_e$ of the first path (in time) of DL SSB used by the IAB-MT to determine downlink timing is received from the reference cell at the IAB-MT antenna. + +## G.2.2.1.2 NR IAB-MT Transmit Timing Test for FR2-1 + +### G.2.2.1.2.1 Test Purpose and environment + +The purpose of this test is to verify that the IAB-MT can follow frame timing change of the connected gNodeb and that the IAB-MT initial transmit timing accuracy, maximum amount of timing change in one adjustment, minimum and maximum adjustment rate are within the specified limits. This test will verify the requirements in clause 12.2.1.2. Local area IAB-MT type 2-O shall be tested with this test. + +Supported test configurations are shown in Table G.2.2.1.2.1-1. + +**Table G.2.2.1.2.1-1: Supported test configurations for FR2-1 PCell** + +| Configuration | Description | +|---------------|-------------------------------------------------------| +| 1 | NR TDD, SSB SCS 240 kHz, data SCS 120 kHz, BW 100 MHz | + +For this test a single NR cell is used. Tables G.2.2.1.2.1-2 and Tables G.2.2.1.2.1-2A define the parameters to be configured and strength of the transmitted signals. The transmit timing is verified by the IAB-MT transmitting SRS using the configuration defined in Table G.2.2.1.2.1-3. + +**Table G.2.2.1.2.1-2: Cell Specific Test Parameters for UL Transmit Timing test** + +| Parameter | Unit | Config | Test1 | Test2 | +|------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|-----------------------------|----------------------------| +| SSB ARFCN | | 1 | Freq1 | Freq1 | +| BW channel | MHz | 1 | 100: N RB,c = 66 | | +| Initial BWP Configuration | | 1 | DLBWP.0.1
ULBWP.0.1 | | +| Dedicated BWP Configuration | | 1 | DLBWP.1.1
ULBWP.1.1 | | +| TRS Configuration | | 1 | TRS.2.1 TDD | | +| TCI State | | 1 | CSI-RS.Config.0 | | +| DRx Cycle | ms | | N/A | | +| PDSCH Reference measurement channel | | 1 | SR.3.1 TDD | | +| RMSI CORESET Reference Channel | | 1 | CR.3.1 TDD | | +| Dedicated CORESET Reference Channel | | 1 | CCR.3.1 TDD | | +| OCNG Patterns | | 1 | OP.1 | | +| SSB Configuration | | 1 | SSB.4 FR2-1 | | +| SMTC Configuration | | 1 | SMTC.1 | | +| EPRE ratio of PSS to SSS | dB | 1 | 0 | 0 | +| EPRE ratio of PBCH DMRS to SSS | | | | | +| EPRE ratio of PBCH to PBCH DMRS | | | | | +| EPRE ratio of PDCCH DMRS to SSS | | | | | +| EPRE ratio of PDCCH to PDCCH DMRS | | | | | +| EPRE ratio of PDSCH DMRS to SSS | | | | | +| EPRE ratio of PDSCH to PDSCH | | | | | +| EPRE ratio of OCNG DMRS to SSS (Note 1) | | | | | +| EPRE ratio of OCNG to OCNG DMRS (Note 1) | | | | | +| Propagation condition | | 1 | AWGN | | +| SRS Config | | 1 | SRSConf.1 Note5 | SRSConf.2 Note5 | +| Note 1: | OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral density is achieved for all OFDM symbols. | | | | +| Note 2: | Interference from other cells and noise sources not specified in the test is assumed to be constant over subcarriers and time and shall be modelled as AWGN of appropriate power for to be fulfilled. | | | | +| Note 3: | SS-RSRP and Io levels have been derived from other parameters for information purposes. They are not settable parameters themselves. | | | | +| Note 4: | SS-RSRP minimum requirements are specified assuming independent interference and noise at each receiver antenna port. | | | | +| Note 5: | SRS configs are given in Table G.2.2.1.2.1-3 | | | | + +**Table G.2.2.1.2.1-2A: OTA related test parameters** + +| Parameter | Unit | Test 1 | Test 2 | +|---------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------| +| Angle of arrival configuration | Setup 1 according to clause G.1.8 | | | +| Note 1 | dBm/15kHz Note4 | | -112 | +| Note 1 | dBm/SCS Note3 | | -103 | +| | dB | | 4 | +| SS-RSRP Note2 | dBm/SCS Note4 | | -99 | +| | dB | | 4 | +| I o Note2 | dBm/95.04 MHz Note4 | | -68.5 | +| Note 1: | Interference from other cells and noise sources not specified in the test is assumed to be constant over subcarriers and time and shall be modelled as AWGN of appropriate power for to be fulfilled. | | | +| Note 2: | SS-RSRP and I o levels have been derived from other parameters for information purposes. They are not settable parameters themselves. | | | +| Note 3: | SS-RSRP minimum requirements are specified assuming independent interference and noise at each receiver antenna port. | | | +| Note 4: | Equivalent power received by an antenna with 0dBi gain at the centre of the quiet zone | | | +| Note 5: | As observed with 0dBi gain antenna at the centre of the quiet zone | | | + +**Table G.2.2.1.2.1-3: SRS Configuration for Timing Accuracy Test** + +| | Field | SRSConf.1 | SRSConf.2 | Comments | +|-----------------|----------------------------------|-----------|-----------|---------------------------| +| SRS-ResourceSet | srs-ResourceSetId | 0 | 0 | | +| | srs-ResourceIdList | 0 | 0 | | +| | resourceType | Periodic | Periodic | | +| | Usage | Codebook | Codebook | | +| SRS-Resource | SRS-ResourceId | 0 | 0 | | +| | nrofSRS-Ports | Port1 | Port1 | | +| | transmissionComb | n2 | n2 | | +| | combOffset-n2 | 0 | 0 | | +| | cyclicShift-n2 | 0 | 0 | | +| | resourceMapping startPosition | 0 | 0 | | +| | resourceMapping nrofSymbols | n1 | n1 | | +| | resourceMapping repetitionFactor | n1 | n1 | | +| | freqDomainPosition | 0 | 0 | | +| | freqDomainShift | 0 | 0 | | +| | freqHopping c-SRS | 17 | 17 | Matches N RB,c | +| | freqHopping b-SRS | 0 | 0 | | +| | freqHopping b-hop | 0 | 0 | | +| | groupOrSequenceHopping | Neither | Neither | | +| | resourceType | Periodic | Periodic | | +| | periodicityAndOffset-p | sl1, 0 | sl2560, 4 | | +| | sequenceId | 0 | 0 | Any 10 bit number | + +#### G.2.2.1.2.2 Test requirements + +The test sequence shall be carried out in RRC\_CONNECTED for every test case. + +Following will be the test sequence for this test: + +- 1) Setup NR PCell according to parameters given in Table G.2.2.1.2.1-1. +- 2) After connection set up with the cell, the test equipment will verify that the timing of the NR cell is within $(N_{TA} + N_{TA\_offset}) \times T_c \pm T_e$ of the first path (in time) of DL SSB used by the IAB-MT to determine downlink timing is received from the reference cell at the IAB-MT antenna. + +- a. The $N_{TA}$ offset value (in $T_c$ units) is 13792 +- b. The $T_c$ values depend on the DL and UL SCS for which the test is being run and are given in Table 12.2.1.2-1 +- 3) The test system shall adjust the timing of the DL path by values given in Table G.2.2.1.2.2-1 + +**Table G.2.2.1.2.2-1: Adjustment Value for DL Timing** + +| SCS of SSB signals (kHz) | Adjustment Value | | +|--------------------------|-------------------|-------------------| +| | Test1 | Test2 | +| 240 | $+8 \cdot 64 T_c$ | $+4 \cdot 64 T_c$ | + +- 4) The test system shall verify that the adjustment step size and the adjustment rate shall be according to requirements specified in clause 12.2.1.2 Table 12.2.1.2.1-1 until the IAB-MT transmit timing offset is within $(N_{TA} + N_{TA\_offset}) \times T_c \pm T_c$ respective to the first path (in time) of DL SSB used by the IAB-MT to determine downlink timing is received from the reference cell at the IAB-MT antenna. +- 5) The test system shall verify that the IAB-MT transmit timing offset stays within $(N_{TA} + N_{TA\_offset}) \times T_c \pm T_c$ of the first path (in time) of DL SSB used by the IAB-MT to determine downlink timing is received from the reference cell at the IAB-MT antenna. + +## G.2.3 Signalling Characteristics for IAB MTs + +### G.2.3.1 Radio link Monitoring + +#### G.2.3.1.1 Radio Link Monitoring Out-of-sync Test for FR1 PCell configured with SSB-based RLM RS in non-DRX mode + +##### G.2.3.1.1.1 Test Purpose and Environment + +The purpose of this test is to verify that the IAB-MT properly detects the out of sync and in sync for the purpose of monitoring downlink radio link quality of the PCell. This test will partly verify the FR1 radio link monitoring requirements in clause 12.3.1. + +In the test, IAB-MT is configured to perform RLM on SSB, with *detectionResource* included in *RadioLinkMonitoringRS* set to SSB#0 and SSB#1, and *purpose* set to 'rlf'. Supported test configurations are shown in table G.2.3.1.1.1-1. The test parameters are given in Tables G.2.3.1.1-2 and G.2.3.1.1.1-3 below. There is one cell (Cell 1), which is the active NR cell, in the test. The test consists of three successive time periods, with time duration of T1, T2 and T3 respectively. Figure G.2.3.1.1.1-1 shows the variation of the downlink SNR in the active cell to emulate out-of-sync and in-sync states. Prior to the start of the time duration T1, the IAB-MT shall be fully synchronized to Cell 1. The IAB-MT shall be configured for periodic CSI reporting with a reporting periodicity of 5 ms. + +**Table G.2.3.1.1.1-1: Supported test configurations for FR1 PCell** + +| Configuration | Description | +|---------------|----------------------------------------------------------------------------------------| +| 1 | TDD, SSB SCS 15 kHz, data SCS 15 kHz, BW 10 MHz | +| 2 | TDD, SSB SCS 30 kHz, data SCS 30 kHz, BW 40 MHz | +| Note: | The IAB-MT is only required to pass in one of the supported test configurations in FR1 | + +**Table G.2.3.1.1.1-2: General test parameters for FR1 out-of-sync testing in non-DRX mode** + +| Parameter | | Unit | Value | +|----------------------------------------------|------------------------------------------------------------------|------|-----------------------------| +| | | | Test 1 | +| Active PCell | | | Cell 1 | +| RF Channel Number | | | 1 | +| Duplex mode | Config 1,2 | | TDD | +| BW channel | Config 1 | MHz | 10: N RB,c = 52 | +| | Config 2 | | 40: N RB,c = 106 | +| DL initial BWP configuration | Config 1, 2 | | DLBWP.0.1 | +| DL dedicated BWP configuration | Config 1, 2 | | DLBWP.1.1 | +| UL initial BWP configuration | Config 1, 2 | | ULBWP.0.1 | +| UL dedicated BWP configuration | Config 1, 2 | | ULBWP.1.1 | +| TDD Configuration | Config 1 | | TDDConf.1.1 | +| | Config 2 | | TDDConf.2.1 | +| CORESET Reference Channel | Config 1 | | CR.1.1 TDD | +| | Config 2 | | CR.2.1 TDD | +| SSB Configuration | Config 1 | | SSB.1 FR1 | +| | Config 2 | | SSB.2 FR1 | +| SMTC Configuration | Config 1 | | SMTC.1 | +| | Config 2 | | SMTC.1 | +| PDSCH/PDCCH subcarrier spacing | Config 1 | | 15 kHz | +| | Config 2 | | 30 kHz | +| PRACH Configuration | Config 1 | | TBD | +| | Config 2 | | TBD | +| SSB index assigned as RLM RS | | | 0 | +| OCNG parameters | | | OP.1 | +| CP length | | | Normal | +| Correlation Matrix and Antenna Configuration | | | 2x2 Low | +| Out of sync transmission parameters | DCI format | | 1-0 | +| | Number of Control OFDM symbols | | 2 | +| | Aggregation level | CCE | 8 | +| | Ratio of hypothetical PDCCH RE energy to average SSS RE energy | dB | 4 | +| | Ratio of hypothetical PDCCH DMRS energy to average SSS RE energy | dB | 4 | +| | DMRS precoder granularity | | REG bundle size | +| | REG bundle size | | 6 | +| DRX | | | OFF | +| Layer 3 filtering | | | Enabled | +| T310 timer | | ms | 0 | +| T311 timer | | ms | 1000 | +| N310 | | | 1 | +| N311 | | | 1 | +| CSI-RS configuration for CSI reporting | Config 1 | | CSI-RS.1.1 TDD | +| | Config 2 | | CSI-RS.2.1 TDD | +| CSI-RS for tracking | Config 1 | | TRS.1.1 TDD | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|---|-------------| +| | Config 2 | | TRS.1.2 TDD | +| T1 | | s | 0.2 | +| T2 | | s | 1.08 | +| T3 | | s | 1.08 | +| D1 | | s | 1.04 | +| Note 1: All configurations are assigned to the IAB-MT prior to the start of time period T1.
Note 2: IAB-MT-specific PDCCH is not transmitted after T1 starts. | | | | + +**Table G.2.3.1.1.1-3: Cell specific test parameters for FR1 (Cell 1) for out-of-sync radio link monitoring tests in non-DRX mode** + +| Parameter | Unit | Test 1 | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|-------------------|-------|-----|--|--|--| +| | | T1 | T2 | T3 | | | | +| EPRE ratio of PDCCH DMRS to SSS | dB | | 4 | | | | | +| EPRE ratio of PDCCH to PDCCH DMRS | dB | | 0 | | | | | +| EPRE ratio of PBCH DMRS to SSS | dB | | 0 | | | | | +| EPRE ratio of PBCH to PBCH DMRS | dB | | | | | | | +| EPRE ratio of PSS to SSS | dB | | | | | | | +| EPRE ratio of PDSCH DMRS to SSS | dB | | | | | | | +| EPRE ratio of PDSCH to PDSCH DMRS | dB | | | | | | | +| EPRE ratio of OCNG DMRS to SSS | dB | | | | | | | +| EPRE ratio of OCNG to OCNG DMRS | dB | | | | | | | +| SNR on RLM-RS | Config 1 | 1 | -7 | -15 | | | | +| | Config 2 | 1 | -7 | -15 | | | | +| | Config 3 | 1 | -7 | -15 | | | | +| SNR on other channels and signals | Config 1, 2, 3 | | 1 | | | | | +| | Config 1 | | dBm/- | -98 | | | | +| | Config 2 | | SCS | -95 | | | | +| Propagation condition | | TDL-C 300ns 100Hz | | | | | | +| Note 1: OCNG shall be used such that the resources in Cell 1 are fully allocated and a constant total transmitted power spectral density is achieved for all OFDM symbols. | | | | | | | | +| Note 2: The signal contains PDCCH for IAB-MTs other than the device under test as part of OCNG. | | | | | | | | +| Note 3: SNR levels correspond to the signal to noise ratio over the SSS REs. | | | | | | | | +| Note 4: The SNR in time periods T1, T2 and T3 is denoted as SNR1, SNR2 and SNR3 respectively in Figure G.2.3.1.1.1-1. | | | | | | | | +| Note 5: The SNR values are specified for testing an IAB-MT which supports 2RX on at least one band. For testing of an IAB-MT which supports 4RX on all bands, the SNR during T3 is defined in clause G.1.3 | | | | | | | | + +![Figure G.2.3.1.1.1-1: SNR variation for out-of-sync testing. The diagram shows SNR levels (SNR1, SNR2, SNR3) over time, divided into periods T1, T2, and T3. SNR1 is the highest level, SNR2 is intermediate, and SNR3 is the lowest. Thresholds Qin and Qout are indicated by dashed lines. A timeline at the bottom shows intervals A, B, C, and D1 within the T3 period.](4f3e31cc28990010782bfee837129791_img.jpg) + +The figure illustrates the SNR variation for out-of-sync testing. The vertical axis represents the SNR level, with three distinct levels: SNR1 (highest), SNR2 (middle), and SNR3 (lowest). Horizontal dashed lines represent the quality thresholds Qin and Qout. The horizontal axis represents time, divided into three main periods: T1, T2, and T3. During T1, the SNR is at level SNR1. At the start of T2, it drops to SNR2. At the start of T3, it drops further to SNR3. Within the T3 period, there are sub-intervals labeled A, B, C, and D1, with D1 being a shorter duration within C. + +Figure G.2.3.1.1.1-1: SNR variation for out-of-sync testing. The diagram shows SNR levels (SNR1, SNR2, SNR3) over time, divided into periods T1, T2, and T3. SNR1 is the highest level, SNR2 is intermediate, and SNR3 is the lowest. Thresholds Qin and Qout are indicated by dashed lines. A timeline at the bottom shows intervals A, B, C, and D1 within the T3 period. + +**Figure G.2.3.1.1.1-1: SNR variation for out-of-sync testing** + +#### G.2.3.1.1.2 Test Requirements + +The IAB-MT behaviour in each test during time durations T1, T2 and T3 shall be as follows: + +During the period from time point A to time point B the IAB-MT shall transmit uplink signal at least in all uplink slots configured for CSI transmission according to the configured periodic CSI reporting. + +The IAB-MT shall stop transmitting uplink signal no later than time point C (D1 second after the start of the time duration T3). + +The rate of correct events observed during repeated tests shall be at least 90%. + +#### G.2.3.1.2 Radio Link Monitoring In-sync Test for FR1 PCell configured with SSB-based RLM RS in non-DRX mode + +##### G.2.3.1.2.1 Test Purpose and Environment + +The purpose of this test is to verify that the IAB-MT properly detects the out of sync and in sync for the purpose of monitoring downlink radio link quality of the PCell. This test will partly verify the FR1 radio link monitoring requirements in clause 12.3.1. + +In the test, IAB-MT is configured to perform RLM on SSB, with *detectionResource* included in *RadioLinkMonitoringRS* set to SSB#0 and SSB#1, and *purpose* set to ‘*rlf*’. Supported test configurations are shown in table G.2.3.1.2.1-1. The test parameters are given in Tables G.2.3.1.2.1-2, and G.2.3.1.2.1-3 below. There is one cell (Cell 1), which is the active cell, in the test. The test consists of five successive time periods, with time duration of T1, T2, T3, T4 and T5 respectively. Figure G.2.3.1.2.1-1 shows the variation of the downlink SNR in the active cell to emulate out-of-sync and in-sync states. Prior to the start of the time duration T1, the IAB-MT shall be fully synchronized to Cell 1. Prior to the start of the time duration T1, the IAB-MT shall be fully synchronized to Cell 1. The IAB-MT shall be configured for periodic CSI reporting with a reporting periodicity of 5 ms. + +**Table G.2.3.1.2.1-1: Supported test configurations for FR1 PCell** + +| Configuration | Description | +|---------------|----------------------------------------------------------------------------------------| +| 1 | TDD, SSB SCS 15 kHz, data SCS 15 kHz, BW 10 MHz | +| 2 | TDD, SSB SCS 30 kHz, data SCS 30 kHz, BW 40 MHz | +| Note: | The IAB-MT is only required to pass in one of the supported test configurations in FR1 | + +**Table G.2.3.1.2.1-2: General test parameters for FR1 in-sync testing in non-DRX mode** + +| Parameter | | Unit | Value | +|----------------------------------------------|------------------------------------------------------------------|------|-----------------------------| +| | | | Test 1 | +| Active PCell | | | Cell 1 | +| RF Channel Number | | | 1 | +| Duplex mode | Config 1, 2 | | TDD | +| BW channel | Config 1 | MHz | 10: N RB,c = 52 | +| | Config 2 | | 40: N RB,c = 106 | +| DL initial BWP configuration | Config 1, 2 | | DLBWP.0.1 | +| DL dedicated BWP configuration | Config 1, 2 | | DLBWP.1.1 | +| UL initial BWP configuration | Config 1, 2 | | ULBWP.0.1 | +| UL dedicated BWP configuration | Config 1, 2 | | ULBWP.1.1 | +| TDD Configuration | Config 1 | | TDDConf.1.1 | +| | Config 2 | | TDDConf.2.1 | +| CORESET Reference Channel | Config 1 | | CR.1.1 TDD | +| | Config 2 | | CR.2.1 TDD | +| SSB Configuration | Config 1 | | SSB.1 FR1 | +| | Config 2 | | SSB.2 FR1 | +| SMTC Configuration | Config 1,2 | | SMTC.1 | +| PDSCH/PDCCH subcarrier spacing | Config 1 | | 15 kHz | +| | Config 2 | | 30 kHz | +| PRACH Configuration | Config 1 | | TBD | +| | Config 2 | | TBD | +| SSB index assigned as RLM RS | | | 0 | +| OCNG parameters | | | OP.1 | +| CP length | | | Normal | +| Correlation Matrix and Antenna Configuration | | | 2x2 Low | +| In sync transmission parameters | DCI format | | 1-0 | +| | Number of Control OFDM symbols | | 2 | +| | Aggregation level | CCE | 4 | +| | Ratio of hypothetical PDCCH RE energy to average SSS RE energy | dB | 0 | +| | Ratio of hypothetical PDCCH DMRS energy to average SSS RE energy | dB | 0 | +| | DMRS precoder granularity | | REG bundle size | +| | REG bundle size | | 6 | +| Out of sync | DCI format | | 1-0 | + +| | | | | +|---------------------------------------------------------------------------------------------|------------------------------------------------------------------|-----|-----------------| +| transmission parameters | Number of Control OFDM symbols | | 2 | +| | Aggregation level | CCE | 8 | +| | Ratio of hypothetical PDCCH RE energy to average SSS RE energy | dB | 4 | +| | Ratio of hypothetical PDCCH DMRS energy to average SSS RE energy | dB | 4 | +| | DMRS precoder granularity | | REG bundle size | +| | REG bundle size | | 6 | +| DRX | | | OFF | +| Layer 3 filtering | | | Enabled | +| T310 timer | | ms | 1000 | +| T311 timer | | ms | 1000 | +| N310 | | | 1 | +| N311 | | | 1 | +| CSI-RS configuration for CSI reporting | Config 1 | | CSI-RS.1.1 TDD | +| | Config 2 | | CSI-RS.2.1 TDD | +| CSI-RS for tracking | Config 1 | | TRS.1.1 TDD | +| | Config 2 | | TRS.1.2 TDD | +| T1 | | s | 0.2 | +| T2 | | s | 0.2 | +| T3 | | s | 1.04 | +| T4 | | s | 0.2 | +| T5 | | s | 2.02 | +| D1 | | s | 1.98 | +| Note 1: All configurations are assigned to the IAB-MT prior to the start of time period T1. | | | | +| Note 2: IAB-MT-specific PDCCH is not transmitted after T1 starts. | | | | + +**Table G.2.3.1.2.1-3: Cell specific test parameters for FR1 (Cell 1) for in-sync radio link monitoring tests in non-DRX mode** + +| Parameter | Unit | Test 1 | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|-------------------|----|-----|------|----| +| | | T1 | T2 | T3 | T4 | T5 | +| EPRE ratio of PDCCH DMRS to SSS | dB | | | 4 | | | +| EPRE ratio of PDCCH to PDCCH DMRS | dB | | | 0 | | | +| EPRE ratio of PBCH DMRS to SSS | dB | | | 0 | | | +| EPRE ratio of PBCH to PBCH DMRS | dB | | | | | | +| EPRE ratio of PSS to SSS | dB | | | | | | +| EPRE ratio of PDSCH DMRS to SSS | dB | | | | | | +| EPRE ratio of PDSCH to PDSCH DMRS | dB | | | | | | +| EPRE ratio of OCNG DMRS to SSS | dB | | | | | | +| EPRE ratio of OCNG to OCNG DMRS | dB | | | | | | +| SNR on RLM-RS | Config 1 | 1 | -7 | -15 | -4.5 | 1 | +| | Config 2 | 1 | -7 | -15 | -4.5 | 1 | +| | Config 3 | 1 | -7 | -15 | -4.5 | 1 | +| SNR on other channels and signals | Config 1, 2, 3 | 1 | | | | | +| | Config 1 | dBm/-98 | | | | | +| | Config 2 | SCS/-95 | | | | | +| Propagation condition | | TDL-C 300ns 100Hz | | | | | +|

Note 1: OCNG shall be used such that the resources in Cell 1 are fully allocated and a constant total transmitted power spectral density is achieved for all OFDM symbols.

Note 2: The signal contains PDCCH for IAB-MTs other than the device under test as part of OCNG.

Note 3: SNR levels correspond to the signal to noise ratio over the SSS REs.

Note 4: The SNR in time periods T1, T2, T3, T4 and T5 is denoted as SNR1, SNR2, SNR3, SNR4 and SNR5 respectively in Figure G.2.3.1.2.1-1.

Note 5: The SNR values are specified for testing an IAB-MT which supports 2RX on at least one band. For testing of an IAB-MT which supports 4RX on all bands, the SNR during T3 and T4 is modified as specified in clause G.1.3.

| | | | | | | + +![Figure G.2.3.1.2.1-1: SNR variation for in-sync testing. The diagram shows SNR levels (SNR1 to SNR5) over time, divided into periods T1 to T5. It also indicates signal levels Qin and Qout, and a distance D1 between points E and F.](827cac884f0a6425ff8e36c32a793859_img.jpg) + +The figure illustrates the SNR variation for in-sync testing. The vertical axis represents the SNR level, with horizontal dashed lines indicating the signal levels *Qin* and *Qout*. The horizontal axis represents time, divided into five periods: T1, T2, T3, T4, and T5. The SNR levels are defined as follows: + + +- SNR1: The SNR level during time period T1. +- SNR2: The SNR level during time period T2. +- SNR3: The SNR level during time period T3. +- SNR4: The SNR level during time period T4. +- SNR5: The SNR level during time period T5. + + The diagram also shows a distance *D1* between points E and F on the time axis. The SNR levels are indicated by step-like lines: SNR1 is at the *Qin* level; SNR2 is below *Qout*; SNR3 is at the *Qout* level; SNR4 is between *Qout* and *Qin*; and SNR5 is at the *Qin* level. + +Figure G.2.3.1.2.1-1: SNR variation for in-sync testing. The diagram shows SNR levels (SNR1 to SNR5) over time, divided into periods T1 to T5. It also indicates signal levels Qin and Qout, and a distance D1 between points E and F. + +**Figure G.2.3.1.2.1-1: SNR variation for in-sync testing** + +**G.2.3.1.2.2 Test Requirements** + +The IAB-MT behaviour in each test during time durations T1, T2, T3, T4 and T5 shall be as follows: + +During the period from time point A to time point F (D1 second after the start of time duration T5) the IAB-MT shall transmit uplink signal at least in all uplink slots configured for CSI transmission according to the configured periodic CSI reporting. + +The rate of correct events observed during repeated tests shall be at least 90%. + +#### G.2.3.1.3 Radio Link Monitoring Out-of-sync Test for FR2-1 PCell configured with SSB-based RLM RS in non-DRX mode + +##### G.2.3.1.3.1 Test Purpose and Environment + +The purpose of this test is to verify that the IAB-MT properly detects the out of sync and in sync for the purpose of monitoring downlink radio link quality of the PCell. This test will partly verify the FR2-1 radio link monitoring requirements in clause 12.3.1. + +In the test, IAB-MT is configured to perform RLM on SSB, with *detectionResource* included in *RadioLinkMonitoringRS* set to SSB#0 and SSB#1, and *purpose* set to ‘*rlf*’. Supported test configurations are shown in table G.2.3.1.3.1-1. The test parameters are given in Tables G.2.3.1.3.1-2 and G.2.3.1.3.1-3 below. There is one cell (Cell 1), which is the active NR cell, in the test. The test consists of three successive time periods, with time duration of T1, T2 and T3 respectively. Figure G.2.3.1.3.1-1 shows the variation of the downlink SNR in the active cell to emulate out-of-sync and in-sync states, and Figure G.2.3.1.3.1-2 shows the Time multiplexed downlink transmissions from each Angle of Arrival. Prior to the start of the time duration T1, the IAB-MT shall be fully synchronized to Cell 1. The IAB-MT shall be configured for periodic CSI reporting with a reporting periodicity of 5 ms. + +**Table G.2.3.1.3.1-1: Supported test configurations for FR2-1 PCell** + +| Configuration | Description | +|---------------|---------------------------------------------------| +| 1 | TDD, SSB SCS 120 KHz, data SCS 120KHz, BW 100 MHz | + +**Table G.2.3.1.3.1-2: General test parameters for FR2-1 out-of-sync testing in non-DRX mode** + +| Parameter | | Unit | Value | +|---------------------------------------------------------------------------------------------|------------------------------------------------------------------|------|-----------------------------| +| | | | Test 1 | +| Active PCell | | | Cell 1 | +| RF Channel Number | | | 1 | +| Duplex mode | Config 1 | | TDD | +| BW channel | Config 1 | | 100: N RB,c = 66 | +| DL initial BWP configuration | Config 1 | | DLBWP.0.1 | +| DL dedicated BWP configuration | Config 1 | | DLBWP.1.1 | +| UL initial BWP configuration | Config 1 | | ULBWP.0.1 | +| UL dedicated BWP configuration | Config 1 | | ULBWP.1.1 | +| TDD Configuration | Config 1 | | TDDConf.3.1 | +| CORESET Reference Channel | Config 1 | | CR.3.1 TDD | +| SSB Configuration | Config 1 | | SSB.1 FR2 | +| SMTC Configuration | Config 1 | | SMTC.1 | +| PDSCH/PDCCH subcarrier spacing | Config 1 | | 120 KHz | +| PRACH Configuration | Config 1 | | TBD | +| SSB index assigned as RLM RS | Config 1 | | 0,1 | +| OCNG parameters | | | OP.2 | +| CP length | | | Normal | +| Out of sync transmission parameters | DCI format | | 1-0 | +| | Number of Control OFDM symbols | | 2 | +| | Aggregation level | CCE | 8 | +| | Ratio of hypothetical PDCCH RE energy to average SSS RE energy | dB | 4 | +| | Ratio of hypothetical PDCCH DMRS energy to average SSS RE energy | dB | 4 | +| | DMRS precoder granularity | | REG bundle size | +| | REG bundle size | | 6 | +| DRX | | | OFF | +| Layer 3 filtering | | | Enabled | +| T310 timer | | ms | 0 | +| T311 timer | | ms | 1000 | +| N310 | | | 1 | +| N311 | | | 1 | +| CSI-RS for CSI reporting | Config 1 | | CSI-RS.3.1 TDD | +| TCI states for PDCCH/PDSCH | | | TCI.State.2 | +| CSI-RS for tracking | Config 1 | | TRS.2.1 TDD | +| T1 | | s | 0.2 | +| T2 | | s | 4.88 | +| T3 | | s | 4.88 | +| D1 | | s | 4.84 | +| Note 1: All configurations are assigned to the IAB-MT prior to the start of time period T1. | | | | +| Note 2: IAB-MT-specific PDCCH is not transmitted after T1 starts. | | | | + +**Table G.2.3.1.3.1-3: OTA related cell specific test parameters for FR2-1 (Cell 1) for out-of-sync radio link monitoring tests in non-DRX mode** + +| Parameter | Unit | Test 1 | | | | | | +|-----------|------|----------------------------------------|----|----|-------------|----|----| +| | | T1 | T2 | T3 | T1 | T2 | T3 | +| AoA setup | | Setup 2 as specified in clause G.1.8.2 | | | | | | +| | | AoA1 | | | AoA2 | | | + +| | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|---------------------------------|---------------------|----------------------|-----------------|---------------------|-----|--|--|--| +| EPRE ratio of PDCCH DMRS to SSS | dB | 4 | | | Not sent | | | | | | +| EPRE ratio of PDCCH to PDCCH DMRS | dB | | | | | | | | | | +| EPRE ratio of PBCH DMRS to SSS | dB | | | | | | | | | | +| EPRE ratio of PBCH to PBCH DMRS | dB | | | | | | | | | | +| EPRE ratio of PSS to SSS | dB | 0 | | | | | | | | | +| EPRE ratio of PDSCH DMRS to SSS | dB | | | | | | | | | | +| EPRE ratio of PDSCH to PDSCH DMRS | dB | | | | | | | | | | +| EPRE ratio of OCN G DMRS to SSS | dB | | | | | | | | | | +| EPRE ratio of OCN G to OCN G DMRS | dB | | | | | | | | | | +| ssb-Index 0 SNR | Config 1 | dB | $2^{\text{Note 6}}$ | $-6^{\text{Note 6}}$ | -15 | | | | | | +| ssb-Index 1 SNR | Config 1 | | Not sent | | | $2^{\text{Note 6}}$ | -15 | | | | +| SNR on other channels and signals | Config 1 | dB | $2^{\text{Note 6}}$ | | | N/A | | | | | +| | Config 1 | dBm/15kHz | -92.1 | | | -92.1 | | | | | +| Time multiplexing of the downlink transmissions from each AoA | | Defined in Figure G.2.3.1.3.1-2 | | | | | | | | | +| Propagation condition | | TDL-A 30ns 75Hz | | | TDL-A 30ns 75Hz | | | | | | +| Note 1: OCN G shall be used such that the resources in Cell 1 are fully allocated and a constant total transmitted power spectral density is achieved for all OFDM symbols.
Note 2: The signal contains PDCCH for IAB-MTs other than the device under test as part of OCN G.
Note 3: SNR levels correspond to the signal to noise ratio over the SSS REs.
Note 4: The SNR values are specified for testing an IAB-MT which supports 2RX on at least one band. For testing of an IAB-MT which supports 4RX on all bands, the SNR during T3 is defined in clause G.1.3.
Note 5: Void
Note 6: This value allows up to 1dB degradation from applied SNR to IAB-MT baseband. | | | | | | | | | | | + +![Graph showing SNR variation over time for out-of-sync testing. The y-axis is SNR level with markers SNR1, SNR2, and SNR3. The x-axis is time with markers A, B, C and intervals T1, T2, T3. SNR1 is constant at level Q_in. SNR2 starts at SNR1, drops at point A to level Q_out, and drops to SNR3 at point B. SNR3 is constant from point B onwards. Yellow arrows indicate 'SSB index 0 SNR level' (from B to C) and 'SSB index 1 SNR level' (from C onwards). A double-headed arrow labeled D1 is between B and C.](90c8c7dc147b20e66be4dbbf3dd636a6_img.jpg) + +Graph showing SNR variation over time for out-of-sync testing. The y-axis is SNR level with markers SNR1, SNR2, and SNR3. The x-axis is time with markers A, B, C and intervals T1, T2, T3. SNR1 is constant at level Q\_in. SNR2 starts at SNR1, drops at point A to level Q\_out, and drops to SNR3 at point B. SNR3 is constant from point B onwards. Yellow arrows indicate 'SSB index 0 SNR level' (from B to C) and 'SSB index 1 SNR level' (from C onwards). A double-headed arrow labeled D1 is between B and C. + +Figure G.2.3.1.3.1-1: SNR variation for out-of-sync testing + +![Figure G.2.3.1.3.1-2: Time multiplexed downlink transmissions. The diagram shows two rows of time slots. The top row has 8 red slots, with the first slot containing a green sub-slot and the last slot containing a purple sub-slot. The bottom row has 8 white slots, with the first slot containing a green sub-slot and the last slot containing a purple sub-slot. Below the rows is a legend with six colored squares: grey, red, green, purple, blue, and white. Arrows indicate time intervals T1, T2, and T3.](ca2740c55eeb32272b09a48cdfb7ee4d_img.jpg) + +Figure G.2.3.1.3.1-2: Time multiplexed downlink transmissions. The diagram shows two rows of time slots. The top row has 8 red slots, with the first slot containing a green sub-slot and the last slot containing a purple sub-slot. The bottom row has 8 white slots, with the first slot containing a green sub-slot and the last slot containing a purple sub-slot. Below the rows is a legend with six colored squares: grey, red, green, purple, blue, and white. Arrows indicate time intervals T1, T2, and T3. + +**Figure G.2.3.1.3.1-2: Time multiplexed downlink transmissions** + +#### G.2.3.1.3.2 Test Requirements + +The IAB-MT behavior in each test during time durations T1, T2 and T3 shall be as follows: + +During the period from time point A to time point B the IAB-MT shall transmit uplink signal at least in all uplink slots configured for CSI transmission according to the configured periodic CSI reporting. + +The IAB-MT shall stop transmitting uplink signal no later than time point C (D1 second after the start of the time duration T3). + +The rate of correct events observed during repeated tests shall be at least 90%. + +#### G.2.3.1.4 Radio Link Monitoring In-sync Test for FR2-1 PCell configured with SSB-based RLM RS in non-DRX mode + +##### G.2.3.1.4.1 Test Purpose and Environment + +The purpose of this test is to verify that the IAB-MT properly detects the out of sync and in sync for the purpose of monitoring downlink radio link quality of the PCell. This test will partly verify the FR2-1 radio link monitoring requirements in clause 12.3.1. + +In the test, IAB-MT is configured to perform RLM on SSB, with *detectionResource* included in *RadioLinkMonitoringRS* set to SSB#0 and SSB#1, and *purpose* set to ‘*rlf*’. Supported test configurations are shown in table G.2.3.1.4.1-1. The test parameters are given in Tables G.2.3.1.4.1-2, and G.2.3.1.4.1-3 below. There is one cell (Cell 1), which is the active cell, in the test. The test consists of five successive time periods, with time duration of T1, T2, T3, T4 and T5 respectively. Figure G.2.3.1.4.1-1 shows the variation of the downlink SNR in the active cell to emulate out-of-sync and in-sync states, and Figure G.2.3.1.4.1-2 shows the Time multiplexed downlink transmissions from each Angle of Arrival. Prior to the start of the time duration T1, the IAB-MT shall be fully synchronized to Cell 1. Prior to the start of the time duration T1, the IAB-MT shall be fully synchronized to Cell 1. The IAB-MT shall be configured for periodic CSI reporting with a reporting periodicity of 5 ms. + +**Table G.2.3.1.4.1-1: Supported test configurations for FR2-1 PCell** + +| Configuration | Description | +|---------------|---------------------------------------------------| +| 1 | TDD, SSB SCS 120 KHz, data SCS 120KHz, BW 100 MHz | + +**Table G.2.3.1.4.1-2: General test parameters for FR2-1 in-sync testing in non-DRX mode** + +| Parameter | | Unit | Value | +|---------------------------------------------------------------------------------------------|------------------------------------------------------------------|------|-----------------------------| +| | | | Test 1 | +| Active PCell | | | Cell 1 | +| RF Channel Number | | | 1 | +| Duplex mode | Config 1 | | TDD | +| BW channel | Config 1 | | 100: N RB,c = 66 | +| DL initial BWP configuration | Config 1 | | DLBWP.0.1 | +| DL dedicated BWP configuration | Config 1 | | DLBWP.1.1 | +| UL initial BWP configuration | Config 1 | | ULBWP.0.1 | +| UL dedicated BWP configuration | Config 1 | | ULBWP.1.1 | +| TDD Configuration | Config 1 | | TDDConf.3.1 | +| CORESET Reference Channel | Config 1 | | CR.3.1 TDD | +| SSB Configuration | Config 1 | | SSB.1 FR2-1 | +| SMTC Configuration | Config 1 | | SMTC.3 | +| PDSCH/PDCCH subcarrier spacing | Config 1 | | 120 KHz | +| PRACH Configuration | Config 1 | | TBD | +| SSB index assigned as RLM RS | Config 1 | | 0,1 | +| OCNG parameters | | | OP.2 | +| CP length | | | Normal | +| In sync transmission parameters | DCI format | | 1-0 | +| | Number of Control OFDM symbols | | 2 | +| | Aggregation level | CCE | 4 | +| | Ratio of hypothetical PDCCH RE energy to average SSS RE energy | dB | 0 | +| | Ratio of hypothetical PDCCH DMRS energy to average SSS RE energy | dB | 0 | +| | DMRS precoder granularity | | REG bundle size | +| | REG bundle size | | 6 | +| Out of sync transmission parameters | DCI format | | 1-0 | +| | Number of Control OFDM symbols | | 2 | +| | Aggregation level | CCE | 8 | +| | Ratio of hypothetical PDCCH RE energy to average SSS RE energy | dB | 4 | +| | Ratio of hypothetical PDCCH DMRS energy to average SSS RE energy | dB | 4 | +| | DMRS precoder granularity | | REG bundle size | +| | REG bundle size | | 6 | +| DRX | | | OFF | +| Layer 3 filtering | | | Enabled | +| T310 timer | | ms | 4000 | +| T311 timer | | ms | 1000 | +| N310 | | | 1 | +| N311 | | | 1 | +| CSI-RS for CSI reporting | Config 1 | | CSI-RS.3.1 TDD | +| TCI states for PDCCH/PDSCH | | | TCI.State.2 | +| CSI-RS for tracking | Config 1 | | TRS.2.1 TDD | +| T1 | | s | 0.2 | +| T2 | | s | 0.2 | +| T3 | | s | 4.84 | +| T4 | | s | 0.2 | +| T5 | | s | 7.84 | +| D1 | | s | 7.8 | +| Note 1: All configurations are assigned to the IAB-MT prior to the start of time period T1. | | | | +| Note 2: IAB-MT-specific PDCCH is not transmitted after T1 starts. | | | | + +**Table G.2.3.1.4.1-3: OTA related cell specific test parameters for FR2-1 (Cell 1) for in-sync radio link monitoring tests in non-DRX mode** + +| Parameter | Unit | Test 1 | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|---------------------|----------------------|-----|------|---------------------|----|---------------------|-----|-----|--|--|--|--|--|--|--|--|--|--|--|--|--| +| | | T1 | T2 | T3 | T4 | T5 | T1 | T2 | T3 | T4 | T5 | | | | | | | | | | | | | | +| AoA setup | | Setup 2 as specified in clause G.1.8.2 | | | | | | | | | | | | | | | | | | | | | | | +| | | AoA1 | | | | | AoA2 | | | | | | | | | | | | | | | | | | +| EPRE ratio of PDCCH DMRS to SSS | dB | 4 | | | | | | | | | | | | | | | | | | | | | | | +| EPRE ratio of PDCCH to PDCCH DMRS | dB | Not sent | | | | | | | | | | | | | | | | | | | | | | | +| EPRE ratio of PBCH DMRS to SSS | dB | | | | | | | | | | | | | | | | | | | | | | | | +| EPRE ratio of PBCH to PBCH DMRS | dB | | | | | | | | | | | | | | | | | | | | | | | | +| EPRE ratio of PSS to SSS | dB | | | | | | | | | | | | | | | | | | | | | | | | +| EPRE ratio of PDSCH DMRS to SSS | dB | | | | | | | | | | | | | | | | | | | | | | | | +| EPRE ratio of PDSCH to PDSCH DMRS | dB | | | | | | | | | | | | | | | | | | | | | | | | +| EPRE ratio of OCNG DMRS to SSS | dB | | | | | | | | | | | | | | | | | | | | | | | | +| EPRE ratio of OCNG to OCNG DMRS | dB | | | | | | | | | | | | | | | | | | | | | | | | +| ssb-Index 0 SNR | Config 1 | dB | $2^{\text{Note 6}}$ | $-6^{\text{Note 6}}$ | -15 | -4.5 | $2^{\text{Note 6}}$ | | | | | | | | | | | | | | | | | | +| ssb-Index 1 SNR | Config 1 | | Not sent | | | | | | $2^{\text{Note 6}}$ | -15 | -15 | | | | | | | | | | | | | | +| SNR on other channels and signals | Config 1 | dB | $2^{\text{Note 6}}$ | | | | | | N/A | | | | | | | | | | | | | | | | +| | Config 1 | dBm/15kHz | -92.1 | | | | | | -92.1 | | | | | | | | | | | | | | | | +| Time multiplexing of the downlink transmissions from each AoA | | Defined in Figure G.2.3.1.4.1-2 | | | | | | | | | | | | | | | | | | | | | | | +| Propagation condition | | TDL-A 30ns 75Hz | | | | | TDL-A 30ns 75Hz | | | | | | | | | | | | | | | | | | +| Note 1: | OCNG shall be used such that the resources in Cell 1 are fully allocated and a constant total transmitted power spectral density is achieved for all OFDM symbols. | | | | | | | | | | | | | | | | | | | | | | | | +| Note 2: | The signal contains PDCCH for IAB-MTs other than the device under test as part of OCNG. | | | | | | | | | | | | | | | | | | | | | | | | +| Note 3: | SNR levels correspond to the signal to noise ratio over the SSS REs. | | | | | | | | | | | | | | | | | | | | | | | | +| Note 4: | The SNR values are specified for testing an IAB-MT which supports 2RX on at least one band. For testing of an IAB-MT which supports 4RX on all bands, the SNR during T3 is defined in clause G.1.3. | | | | | | | | | | | | | | | | | | | | | | | | +| Note 5: | Void. | | | | | | | | | | | | | | | | | | | | | | | | +| Note 6: | This value allows up to 1dB degradation from applied SNR to IAB-MT baseband | | | | | | | | | | | | | | | | | | | | | | | | + +![Figure G.2.3.1.4.1-1: SNR variation for in-sync testing. A graph showing SNR level (SNR1, SNR5, SNR4, SNR2, SNR3) over time intervals T1, T2, T3, T4, T5. The graph shows two step-like curves: 'SSB index 0 SNR level' (yellow) and 'SSB index 1 SNR level' (black). Thresholds Q_in and Q_out are indicated. Time points A, B, C, D, E, F are marked on the x-axis, with D1 indicating a duration from E to F.](69f94bbb66c1b9e3368795d3abb1e5d0_img.jpg) + +Figure G.2.3.1.4.1-1: SNR variation for in-sync testing. A graph showing SNR level (SNR1, SNR5, SNR4, SNR2, SNR3) over time intervals T1, T2, T3, T4, T5. The graph shows two step-like curves: 'SSB index 0 SNR level' (yellow) and 'SSB index 1 SNR level' (black). Thresholds Q\_in and Q\_out are indicated. Time points A, B, C, D, E, F are marked on the x-axis, with D1 indicating a duration from E to F. + +Figure G.2.3.1.4.1-1: SNR variation for in-sync testing + +![Figure G.2.3.1.4.1-2: Time multiplexed downlink transmissions. Two diagrams showing time slots with various colored blocks representing different transmission types. A legend at the bottom identifies the colors: Gray (PDCCH), Red (PDSCH), Green (CSI-RS), Purple (PUCCH), Blue (PUSCH), and White (Unused capacity).](c78844717bf077b0701f90f5e2935dea_img.jpg) + +Figure G.2.3.1.4.1-2: Time multiplexed downlink transmissions. Two diagrams showing time slots with various colored blocks representing different transmission types. A legend at the bottom identifies the colors: Gray (PDCCH), Red (PDSCH), Green (CSI-RS), Purple (PUCCH), Blue (PUSCH), and White (Unused capacity). + +Figure G.2.3.1.4.1-2: Time multiplexed downlink transmissions + +G.2.3.1.4.2 Test Requirements + +The IAB-MT behaviour in each test during time durations T1, T2, T3, T4 and T5 shall be as follows: + +During the period from time point A to time point F (D1 second after the start of time duration T5) the IAB-MT shall transmit uplink signal at least in all uplink slots configured for CSI transmission according to the configured periodic CSI reporting. + +The rate of correct events observed during repeated tests shall be at least 90%. + +### G.2.3.1.5 Radio Link Monitoring Out-of-sync Test for FR1 PCell configured with CSI-RS-based RLM in non-DRX mode + +#### G.2.3.1.5.1 Test Purpose and Environment + +The purpose of this test is to verify that the IAB-MT properly detects the out of sync for the purpose of monitoring downlink CSI-RS based radio link quality of the PCell. This test will partly verify the FR1 PCell CSI-RS Out-of-sync radio link monitoring requirements in clause 12.3.1.3. This test case is applicable only for local area IAB-MT and for IAB type 1-H. + +The test parameters are given in Tables G.2.3.1.5.1-1, G.2.3.1.5.1-2 and G.2.3.1.5.1-3 below. There is one cell, cell 1 which is the PCell, in the test. The test consists of three successive time periods, with time duration of T1, T2 and T3 respectively. Figure G.2.3.1.5.1-1 shows the variation of the downlink SNR in the PCell to emulate out-of-sync and in-sync states. Prior to the start of the time duration T1, the IAB-MT shall be fully synchronized to cell 1. The IAB-MT shall be configured for periodic CSI reporting with a reporting periodicity defined in CSI-RS configuration. In the test, SSB0 is configured as the BFD-RS. + +**Table G.2.3.1.5.1-1: Supported test configurations for FR1 PCell** + +| Configuration | Description | +|---------------|----------------------------------------------------------------------------------------| +| 1 | TDD duplex mode, 15 kHz SSB SCS, 10 MHz bandwidth | +| 2 | TDD duplex mode, 30 kHz SSB SCS, 40 MHz bandwidth | +| Note: | The IAB-MT is only required to pass in one of the supported test configurations in FR1 | + +**Table G.2.3.1.5.1-2: General test parameters for FR1 PCell for CSI-RS out-of-sync testing in non-DRX** + +| Parameter | | Unit | IAB-MT | +|-------------------------------------------------------------------|---------------------------------------------------------------------|------|----------------------------| +| | | | Test 1 | +| Active PCell | | | Cell 1 | +| RF Channel Number | | | 1 | +| Duplex mode | Config 1, 2 | | TDD | +| TDD Configuration | Config 1 | | TDDConf.1.1 | +| | Config 2 | | TDDConf.2.1 | +| DL initial BWP configuration | Config 1, 2 | | DLBWP.0.1 | +| DL dedicated BWP configuration | Config 1, 2 | | DLBWP.1.1 | +| UL initial BWP configuration | Config 1, 2 | | ULBWP.0.1 | +| UL dedicated BWP configuration | Config 1, 2 | | ULBWP.1.1 | +| CORESET Reference Channel | Config 1 | | CR.1.1 TDD | +| | Config 2 | | CR.2.1 TDD | +| SSB Configuration | Config 1 | | SSB.1 FR1 | +| | Config 2 | | SSB.2 FR1 | +| SMTC Configuration | Config 1 | | SMTC.1 | +| | Config 2 | | SMTC.1 | +| PDSCH/PDCCH subcarrier spacing | Config 1 | | 15 kHz | +| | Config 2 | | 30 kHz | +| TRS configuration | Config 1 | | TRS.1.1 TDD | +| | Config 2 | | TRS.1.2 TDD | +| CSI-RS for RLM | Config 1 | | Resource #4 in TRS.1.1 TDD | +| | Config 2 | | Resource #4 in TRS.1.2 TDD | +| TCI configuration for PDCCH/PDSCH | | | TCI.State.2 | +| OCNG parameters | | | OP.1 | +| CP length | | | Normal | +| Correlation Matrix and Antenna Configuration | | | 2x2 Low | +| Out of sync transmission parameters | DCI format | | 1-0 | +| | Number of Control OFDM symbols | | 2 | +| | Aggregation level | CCE | 8 | +| | Ratio of hypothetical PDCCH RE energy to average CSI-RS RE energy | dB | 4 | +| | Ratio of hypothetical PDCCH DMRS energy to average CSI-RS RE energy | dB | 4 | +| | DMRS precoder granularity | | REG bundle size | +| | REG bundle size | | 6 | +| Layer 3 filtering | | | Enabled | +| T310 timer | | ms | 0 | +| T311 timer | | ms | 1000 | +| N310 | | | 1 | +| N311 | | | 1 | +| CSI-RS configuration for CSI reporting | Config 1 | | CSI-RS.1.1 TDD | +| | Config 2 | | CSI-RS.2.1 TDD | +| T1 | | s | 0.2 | +| T2 | | s | 48 | +| T3 | | s | 0.48 | +| D1 | | s | 0.44 | +| Note 1: IAB-MT-specific PDCCH is not transmitted after T1 starts. | | | | + +**Table G.2.3.1.5.1-3: Cell specific test parameters for FR1 for CSI-RS out-of-sync radio link monitoring in non-DRX** + +| Parameter | Unit | Test 1 | | | | | | +|-----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-----|-----|--|--|--| +| | | T1 | T2 | T3 | | | | +| PDCCH_beta | dB | | 4 | | | | | +| PDCCH_DMRS_beta | dB | | 4 | | | | | +| PBCH_beta | dB | | 0 | | | | | +| PSS_beta | dB | | | | | | | +| SSS_beta | dB | | | | | | | +| PDSCH_beta | dB | | | | | | | +| OCNG_beta | dB | | | | | | | +| SNR on RLM-RS | Config 1, 2 | 1 | -7 | -15 | | | | +| SNR on other channels and signals | Config 1, 2 | | 1 | | | | | +| | Config 1, 2 | | -98 | | | | | +| Propagation condition | | TDL-C 300ns 100Hz | | | | | | +| Note 1: | OCNG shall be used such that the resources in Cell 1 are fully allocated and a constant total transmitted power spectral density is achieved for all OFDM symbols. | | | | | | | +| Note 2: | The uplink resources for CSI reporting are assigned to the IAB-MT prior to the start of time period T1. | | | | | | | +| Note 3: | NZP CSI-RS resource set configuration for CSI reporting are assigned to the IAB-MT prior to the start of time period T1. | | | | | | | +| Note 4: | The timers and layer 3 filtering related parameters are configured prior to the start of time period T1. | | | | | | | +| Note 5: | The signal contains PDCCH for IAB-MTs other than the device under test as part of OCNG. | | | | | | | +| Note 6: | SNR levels correspond to the signal to noise ratio over the SSS REs. | | | | | | | +| Note 7: | The SNR in time periods T1, T2 and T3 is denoted as SNR1, SNR2 and SNR3 respectively in figure G.2.3.1.5.1-1. | | | | | | | +| Note 8: | The SNR IAB-MTs are specified for testing a IAB-MT which supports 2RX on at least one band. For testing of IAB-MT which supports 4RX on all bands, the SNR during T3 is specified in clause G.1.3.1.1. | | | | | | | + +![Figure G.2.3.1.5.1-1: SNR variation for CSI-RS out-of-sync testing. The diagram shows a step-like SNR level over time. The y-axis is labeled 'SNR level' and has markers for 'SNR 1', 'SNR 2', and 'SNR 3'. The x-axis represents time, divided into three periods: T1, T2, and T3. The SNR starts at SNR 1 during T1, drops to SNR 2 during T2, and drops further to SNR 3 during T3. A horizontal line labeled 'Cell 1 SNR level' is shown. Two dashed horizontal lines represent thresholds 'Qin' and 'Qout'. Time points A, B, and C are marked on the x-axis. A double-headed arrow between B and C is labeled 'D1 ms'.](507613acfd7f6ef6af724a2005f24024_img.jpg) + +Figure G.2.3.1.5.1-1: SNR variation for CSI-RS out-of-sync testing. The diagram shows a step-like SNR level over time. The y-axis is labeled 'SNR level' and has markers for 'SNR 1', 'SNR 2', and 'SNR 3'. The x-axis represents time, divided into three periods: T1, T2, and T3. The SNR starts at SNR 1 during T1, drops to SNR 2 during T2, and drops further to SNR 3 during T3. A horizontal line labeled 'Cell 1 SNR level' is shown. Two dashed horizontal lines represent thresholds 'Qin' and 'Qout'. Time points A, B, and C are marked on the x-axis. A double-headed arrow between B and C is labeled 'D1 ms'. + +**Figure G.2.3.1.5.1-1: SNR variation for CSI-RS out-of-sync testing****G.2.3.1.5.2 Test Requirements** + +The IAB-MT behaviour during time durations T1, T2, and T3 shall be as follows: + +During time durations T1, T2 and T3, the IAB-MT shall transmit uplink signal at least in all subframes configured for CSI transmission on Cell 1. + +During the period from time point A to time point B the IAB-MT shall transmit uplink signal in Cell 1 at least in all uplink slots configured for CSI transmission according to the configured periodic CSI reporting for Cell 1. + +The IAB-MT shall stop transmitting uplink signal in Cell 1 no later than time point C ( $D_1$ ms after the start of the time duration T3) on the PCell. + +The rate of correct events observed during repeated tests shall be at least 90%. + +### G.2.3.1.6 Radio Link Monitoring In-sync Test for FR1 PCell configured with CSI-RS-based RLM in non-DRX mode + +#### G.2.3.1.6.1 Test Purpose and Environment + +The purpose of this test is to verify that the IAB-MT properly detects the in sync for the purpose of monitoring downlink CSI-RS based radio link quality of the PCell. This test will partly verify the FR1 PCell CSI-RS In-sync radio link monitoring requirements in clause 12.3.1.3. This test case is applicable only for local area IAB-MT and for IAB type 1-H. + +The test parameters are given in Tables G.2.3.1.6.1-1, G.2.3.1.6.1-2, and G.2.3.1.6.1-3 below. There is one cells, cell 1 which is the PCell, in the test. The test consists of five successive time periods, with time duration of T1, T2, T3, T4 and T5 respectively. Figure G.2.3.1.6.1-1 shows the variation of the downlink SNR in the PCell to emulate out-of-sync and in-sync states. Prior to the start of the time duration T1, the IAB-MT shall be fully synchronized to cell 1. The IAB-MT shall be configured for periodic CSI reporting with a reporting periodicity defined in CSI-RS configuration. In the test, SSB0 is configured as the BFD-RS. + +**Table G.2.3.1.6.1-1: Supported test configurations for FR1 PCell** + +| Configuration | Description | +|---------------|----------------------------------------------------------------------------------------| +| 1 | TDD duplex mode, 15 kHz SSB SCS, 10 MHz bandwidth | +| 2 | TDD duplex mode, 30kHz SSB SCS, 40 MHz bandwidth | +| Note: | The IAB-MT is only required to pass in one of the supported test configurations in FR1 | + +**Table G.2.3.1.6.1-2: General test parameters for FR1 PCell for CSI-RS in-sync testing in non-DRX** + +| Parameter | | Unit | IAB-MT | +|----------------------------------------------|---------------------------------------------------------------------|------|----------------------------| +| | | | Test 1 | +| Active PCell | | | Cell 1 | +| RF Channel Number | | | 1 | +| Duplex mode | Config 1, 2 | | TDD | +| TDD Configuration | Config 1 | | TDDConf.1.1 | +| | Config 2 | | TDDConf.2.1 | +| DL initial BWP configuration | Config 1, 2 | | DLBWP.0.1 | +| DL dedicated BWP configuration | Config 1, 2 | | DLBWP.1.1 | +| UL initial BWP configuration | Config 1, 2 | | ULBWP.0.1 | +| UL dedicated BWP configuration | Config 1, 2 | | ULBWP.1.1 | +| CORESET Reference Channel | Config 1 | | CR.1.1 TDD | +| | Config 2 | | CR.2.1 TDD | +| SSB Configuration | Config 1 | | SSB.1 FR1 | +| | Config 2 | | SSB.2 FR1 | +| SMTC Configuration | Config 1, 2 | | SMTC.1 | +| PDSCH/PDCCH subcarrier spacing | Config 1 | | 15 kHz | +| | Config 2 | | 30 kHz | +| TRS configuration | Config 1 | | TRS.1.1 TDD | +| | Config 2 | | TRS.1.2 TDD | +| CSI-RS for RLM | Config 1 | | Resource #4 in TRS.1.1 TDD | +| | Config 2 | | Resource #4 in TRS.1.2 TDD | +| TCI configuration for PDCCH/PDSCH | | | TCI.State.2 | +| OCNG parameters | | | OP.1 | +| CP length | | | Normal | +| Correlation Matrix and Antenna Configuration | | | 2x2 Low | +| Out of sync transmission parameters | DCI format | | 1-0 | +| | Number of Control OFDM symbols | | 2 | +| | Aggregation level | CCE | 8 | +| | Ratio of hypothetical PDCCH RE energy to average CSI-RS RE energy | dB | 4 | +| | Ratio of hypothetical PDCCH DMRS energy to average CSI-RS RE energy | dB | 4 | +| | DMRS precoder granularity | | REG bundle size | +| | REG bundle size | | 6 | +| In sync transmission parameters | DCI format | | 1-0 | +| | Number of Control OFDM symbols | | 2 | +| | Aggregation level | CCE | 4 | +| | Ratio of hypothetical PDCCH RE energy to average CSI-RS RE energy | dB | 0 | +| | Ratio of hypothetical PDCCH DMRS energy to average CSI-RS RE energy | dB | 0 | +| | DMRS precoder granularity | | REG bundle size | +| | REG bundle size | | 6 | +| Layer 3 filtering | | | Enabled | +| T310 timer | | ms | 1000 | +| T311 timer | | ms | 1000 | +| N310 | | | 1 | +| N311 | | | 1 | +| CSI-RS configuration for CSI | Config 1 | | CSI-RS.1.1 TDD | + +| | | | | +|-------------------------------------------------------------------|----------|---|----------------| +| reporting | Config 2 | | CSI-RS.2.1 TDD | +| T1 | | s | 0.2 | +| T2 | | s | 0.2 | +| T3 | | s | 0.44 | +| T4 | | s | 0.2 | +| T5 | | s | 0.88 | +| T6 | | s | 0.84 | +| Note 1: IAB-MT-specific PDCCH is not transmitted after T1 starts. | | | | + +**Table G.2.3.1.6.1-3: Cell specific test parameters for FR1 for CSI-RS in-sync radio link monitoring in non-DRX** + +| Parameter | Unit | Test 1 | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------------|----|-----|------|----|--|--|--|--|--| +| | | T1 | T2 | T3 | T4 | T5 | | | | | | +| PDCCH_beta | dB | | | 4 | | | | | | | | +| PDCCH_DMRS_beta | dB | | | 4 | | | | | | | | +| PBCH_beta | dB | | | 0 | | | | | | | | +| PSS_beta | dB | | | | | | | | | | | +| SSS_beta | dB | | | | | | | | | | | +| PDSCH_beta | dB | | | | | | | | | | | +| OCNG_beta | dB | | | | | | | | | | | +| SNR on RLM-RS | Config 1, 2 | 1 | -7 | -15 | -4.5 | 1 | | | | | | +| SNR on other channels and signals | Config 1, 2 | | | 1 | | | | | | | | +| | Config 1, 2 | | | -98 | | | | | | | | +| Propagation condition | | TDL-C 300ns 100Hz | | | | | | | | | | +| Note 1: OCNG shall be used such that the resources in Cell 1 are fully allocated and a constant total transmitted power spectral density is achieved for all OFDM symbols. | | | | | | | | | | | | +| Note 2: The uplink resources for CSI reporting are assigned to the IAB-MT prior to the start of time period T1. | | | | | | | | | | | | +| Note 3: NZP CSI-RS resource set configuration for CSI reporting are assigned to the IAB-MT prior to the start of time period T1. | | | | | | | | | | | | +| Note 4: The timers and layer 3 filtering related parameters are configured prior to the start of time period T1. | | | | | | | | | | | | +| Note 5: The signal contains PDCCH for IAB-MTs other than the device under test as part of OCNG. | | | | | | | | | | | | +| Note 6: SNR levels correspond to the signal to noise ratio over the SSS REs. | | | | | | | | | | | | +| Note 7: The SNR in time periods T1, T2, T3, T4 and T5 is denoted as SNR1, SNR2, SNR3, SNR4 and SNR5 respectively in figure G.2.3.1.6.1-1. | | | | | | | | | | | | +| Note 8: The SNR IAB-MTs are specified for testing a IAB-MT which supports 2RX on at least one band. For testing of IAB-MT which supports 4RX on all bands, the SNR during T3 is specified in clause G.1.3.1.1. | | | | | | | | | | | | + +![Figure G.2.3.1.6.1-1: SNR variation for CSI-RS in-sync testing. The diagram shows SNR levels (SNR1 to SNR5) over time, divided into periods T1 through T5. A horizontal axis marks time points A, B, C, D, E, and F. SNR1 is the highest level, starting at A. SNR2 is lower than SNR1, starting at B. SNR3 is the lowest level, starting at C. SNR4 is higher than SNR3, starting at D. SNR5 is the highest level, starting at E. The diagram also shows two horizontal dashed lines labeled Qin and Qout. A double-headed arrow labeled T6 indicates the duration between E and F.](01855a115275f85d385c12fe6aa4c4ae_img.jpg) + +Figure G.2.3.1.6.1-1: SNR variation for CSI-RS in-sync testing. The diagram shows SNR levels (SNR1 to SNR5) over time, divided into periods T1 through T5. A horizontal axis marks time points A, B, C, D, E, and F. SNR1 is the highest level, starting at A. SNR2 is lower than SNR1, starting at B. SNR3 is the lowest level, starting at C. SNR4 is higher than SNR3, starting at D. SNR5 is the highest level, starting at E. The diagram also shows two horizontal dashed lines labeled Qin and Qout. A double-headed arrow labeled T6 indicates the duration between E and F. + +**Figure G.2.3.1.6.1-1: SNR variation for CSI-RS in-sync testing** + +**G.2.3.1.6.2 Test Requirements** + +The IAB-MT behaviour in each test during time durations T1, T2, T3, T4 and T5 shall be as follows: + +During the period from time point A to time point F (T6 second after the start of time duration T5) the IAB-MT shall transmit uplink signal at least in all uplink slots configured for CSI transmission according to the configured periodic CSI reporting on the PCell. + +The rate of correct events observed during repeated tests shall be at least 90%. + +#### G.2.3.1.7 Radio Link Monitoring Out-of-sync Test for FR2-1 PCell configured with CSI-RS-based RLM in non-DRX mode + +##### G.2.3.1.7.1 Test Purpose and Environment + +The purpose of this test is to verify that the IAB-MT properly detects the out of sync for the purpose of monitoring downlink CSI-RS based radio link quality of the PCell. This test will partly verify the FR2-1 PCell CSI-RS Out-of-sync radio link monitoring requirements in clause 12.3.1.3. This test case is applicable only for local area IAB-MT and for IAB type 2-0. + +The test parameters are given in Tables G.2.3.1.7.1-1, G.2.3.1.7.1-2 and G.2.3.1.7.1-3 below. There is one cell, cell 1 which is the PCell, in the test. The test consists of three successive time periods, with time duration of T1, T2 and T3 respectively. Figure G.2.3.1.7.1-1 shows the variation of the downlink SNR in the PCell to emulate out-of-sync and in-sync states. Prior to the start of the time duration T1, the IAB-MT shall be fully synchronized to cell 1. The IAB-MT shall be configured for periodic CSI reporting with a reporting periodicity of 10 ms. In the test, SSB0 and SSB1 are configured as BFD-RS. + +**Table G.2.3.1.7.1-1: Supported test configurations for FR2-1 PCell** + +| Configuration | Description | +|---------------|-----------------------------------------------------| +| 1 | TDD duplex mode, 120 kHz SSB SCS, 100 MHz bandwidth | + +**Table G.2.3.1.7.1-2: General test parameters for FR2-1 PCell for CSI-RS out-of-sync testing in non-DRX** + +| Parameter | | Unit | IAB-MT | +|-------------------------------------------------------------------|---------------------------------------------------------------------|------|----------------------------------------------------------| +| | | | Test 1 | +| Active PCell | | | Cell 1 | +| RF Channel Number | | | 1 | +| Duplex mode | Config 1 | | TDD | +| TDD Configuration | Config 1 | | TDDConf.3.1 | +| DL initial BWP configuration | Config 1 | | DLBWP.0.1 | +| DL dedicated BWP configuration | Config 1 | | DLBWP.1.1 | +| UL initial BWP configuration | Config 1 | | ULBWP.0.1 | +| UL dedicated BWP configuration | Config 1 | | ULBWP.1.1 | +| CORESET Reference Channel | Config 1 | | CCR.3.1 TDD
CCR.3.3 TDD | +| SSB Configuration | Config 1 | | SSB.1 FR2-1 | +| SMTC Configuration | Config 1 | | SMTC.1 | +| PDSCH/PDCCH subcarrier spacing | Config 1 | | 120 KHz | +| CSI-RS for RLM | Config 1 | | Resource #4 in TRS.2.1 TDD
Resource #4 in TRS.2.2 TDD | +| TRS configuration | | | TRS.2.1 TDD
TRS.2.2 TDD | +| TCI configuration for PDCCH#1/PDSCH | | | TCI.State.2 | +| TCI configuration for PDCCH#2 | | | TCI.State.3 | +| OCNG parameters | | | OP.1 | +| CP length | | | Normal | +| Out of sync transmission parameters | DCI format | | 1-0 | +| | Number of Control OFDM symbols | | 2 | +| | Aggregation level | CCE | 8 | +| | Ratio of hypothetical PDCCH RE energy to average CSI-RS RE energy | dB | 4 | +| | Ratio of hypothetical PDCCH DMRS energy to average CSI-RS RE energy | dB | 4 | +| | DMRS precoder granularity | | REG bundle size | +| | REG bundle size | | 6 | +| | | | | +| Layer 3 filtering | | | Enabled | +| T310 timer | | ms | 0 | +| T311 timer | | ms | 1000 | +| N310 | | | 1 | +| N311 | | | 1 | +| CSI-RS for CSI reporting | Config 1 | | CSI-RS.3.1 TDD | +| T1 | | s | 0.2 | +| T2 | | s | 0.35 | +| T3 | | s | 0.35 | +| D1 | | s | 0.31 | +| Note 1: IAB-MT-specific PDCCH is not transmitted after T1 starts. | | | | + +**Table G.2.3.1.7.1-3: Cell specific test parameters for FR2-1 for CSI-RS out-of-sync radio link monitoring in non-DRX** + +| Parameter | Unit | Test 1 | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|--------------------------------------|---------------------|----------------------|-------------------|---------------------|-----|--|--|--|--|--|--|--|--| +| | | T1 | T2 | T3 | T1 | T2 | T3 | | | | | | | | | +| AoA setup | | AoA setup as defined in clause G.1.8 | | | | | | | | | | | | | | +| | | AoA1 | | | AoA2 | | | | | | | | | | | +| Assumption for IAB-MT beams Note 8 | | Rough | | | Rough | | | | | | | | | | | +| PDCCH_beta | dB | 4 | | | Not sent | | | | | | | | | | | +| PDCCH_DMRS_beta | dB | | | | | | | | | | | | | | | +| PBCH_beta | dB | | | | | | | | | | | | | | | +| PSS_beta | dB | | | | | | | | | | | | | | | +| SSS_beta | dB | | | | | | | | | | | | | | | +| PDSCH_beta | dB | | | | | | | | | | | | | | | +| OCNG_beta | dB | | | | | | | | | | | | | | | +| SNR on RLM-RS1 | Config 1 | dB | 2 Note 9 | -6 Note 9 | -15 | | | | | | | | | | | +| SNR on RLM-RS2 | Config 1 | | Not sent | | | 2 Note 9 | -14 | | | | | | | | | +| SNR on other channels and signals | Config 1 | dB | 2 Note 9 | | | N/A | | | | | | | | | | +| | Config 1 | dBm/15kHz | -92.1 | | | -92.1 | | | | | | | | | | +| Propagation condition | | TDL-C 300ns 100Hz | | | TDL-C 300ns 100Hz | | | | | | | | | | | +| Note 1: OCNG shall be used such that the resources in Cell 1 are fully allocated and a constant total transmitted power spectral density is achieved for all OFDM symbols. | | | | | | | | | | | | | | | | +| Note 2: The uplink resources for CSI reporting are assigned to the IAB-MT prior to the start of time period T1. | | | | | | | | | | | | | | | | +| Note 3: NZP CSI-RS resource set configuration for CSI reporting are assigned to the IAB-MT prior to the start of time period T1. | | | | | | | | | | | | | | | | +| Note 4: The timers and layer 3 filtering related parameters are configured prior to the start of time period T1. | | | | | | | | | | | | | | | | +| Note 5: The signal contains PDCCH for IAB-MTs other than the device under test as part of OCNG. | | | | | | | | | | | | | | | | +| Note 6: SNR levels correspond to the signal to noise ratio over the SSS REs. | | | | | | | | | | | | | | | | +| Note 7: The SNR in time periods T1, T2 and T3 is denoted as SNR1, SNR2 and SNR3 respectively in figure G.2.3.1.7.1-1. | | | | | | | | | | | | | | | | +| Note 8: Information about types of IAB-MT beam does not limit IAB-MT implementation or test system implementation. | | | | | | | | | | | | | | | | +| Note 9: This IAB-MT allows up to 1dB degradation from applied SNR to IAB-MT baseband | | | | | | | | | | | | | | | | + +![Figure G.2.3.1.7.1-1: SNR variation for CSI-RS out-of-sync testing. The graph shows SNR levels (SNR1, SNR2, SNR3) over time periods T1, T2, and T3. SNR1 is constant at a high level. SNR2 starts at SNR1, drops at point A, and drops again at point B. SNR3 starts at SNR1, drops at point A, and remains constant at a lower level than SNR2. The graph also shows Qin, Qout, RLM-RS1 SNR level, RLM-RS2 SNR level, and time intervals D1, T1, T2, and T3.](53aea0bced847238f29b804b3d23744f_img.jpg) + +The figure is a line graph showing SNR variation over time. The y-axis represents SNR levels with markers for SNR1, SNR2, and SNR3. The x-axis represents time, divided into three periods: T1, T2, and T3, by vertical lines at points A, B, and C. + + +- SNR1 (black line) is constant at the highest level throughout all periods. +- SNR2 (red line) starts at SNR1, drops to a middle level at point A, and drops again to a lower level at point B. +- SNR3 (green line) starts at SNR1, drops to the same lower level as SNR2 at point A, and remains constant through point C. +- Horizontal dashed lines indicate 'Qin' (above SNR1) and 'Qout' (between SNR2 and SNR3). +- Labels 'RLM-RS1 SNR level' and 'RLM-RS2 SNR level' point to the SNR3 and SNR2 lines respectively. +- Time intervals T1, T2, and T3 are marked at the bottom. D1 is the duration from B to C. + +Figure G.2.3.1.7.1-1: SNR variation for CSI-RS out-of-sync testing. The graph shows SNR levels (SNR1, SNR2, SNR3) over time periods T1, T2, and T3. SNR1 is constant at a high level. SNR2 starts at SNR1, drops at point A, and drops again at point B. SNR3 starts at SNR1, drops at point A, and remains constant at a lower level than SNR2. The graph also shows Qin, Qout, RLM-RS1 SNR level, RLM-RS2 SNR level, and time intervals D1, T1, T2, and T3. + +**Figure G.2.3.1.7.1-1: SNR variation for CSI-RS out-of-sync testing** + +**G.2.3.1.7.2 Test Requirements** + +The IAB-MT behaviour during time durations T1, T2, and T3 shall be as follows: + +During time durations T1, T2 and T3, the IAB-MT shall transmit uplink signal at least in all subframes configured for CSI transmission on Cell 1. + +During the period from time point A to time point B the IAB-MT shall transmit uplink signal in Cell 1 at least in all uplink slots configured for CSI transmission according to the configured periodic CSI reporting for Cell 1. + +The IAB-MT shall stop transmitting uplink signal in Cell 1 no later than time point C ( $D_1$ second after the start of the time duration T3) on the PCell. + +The rate of correct events observed during repeated tests shall be at least 90%. + +#### G.2.3.1.8 Radio Link Monitoring In-sync Test for FR2-1 PCell configured with CSI-RS-based RLM in non-DRX mode + +##### G.2.3.1.8.1 Test Purpose and Environment + +The purpose of this test is to verify that the IAB-MT properly detects the in sync for the purpose of monitoring downlink CSI-RS based radio link quality of the PCell. This test will partly verify the FR2 PCell CSI-RS In-sync radio link monitoring requirements in clause 12.3.1.3. This test case is applicable only for local area IAB-MT and for IAB type 2-O. + +The test parameters are given in Tables G.2.3.1.8.1-1, G.2.3.1.8.1-2 and G.2.3.1.8.1-3 below. There is one cells, cell 1 which is the PCell, in the test. The test consists of five successive time periods, with time duration of T1, T2, T3, T4 and T5 respectively. Figure G.2.3.1.8.1-1 shows the variation of the downlink SNR in the PCell to emulate out-of-sync and in-sync states. Prior to the start of the time duration T1, the IAB-MT shall be fully synchronized to cell 1. The IAB-MT shall be configured for periodic CSI reporting with a reporting periodicity of 10 ms. In the test, SSB0 and SSB1 are configured as BFD-RS. + +**Table G.2.3.1.8.1-1: Supported test configurations for FR2-1 PCell** + +| Configuration | Description | +|---------------|-----------------------------------------------------| +| 1 | TDD duplex mode, 120 kHz SSB SCS, 100 MHz bandwidth | + +**Table G.2.3.1.8.1-2: General test parameters for FR2-1 PCell for CSI-RS in-sync testing in non-DRX** + +| Parameter | | Unit | IAB-MT | +|-------------------------------------------------------------------|---------------------------------------------------------------------|------|----------------------------| +| Active PCell | | | Test 1 | +| RF Channel Number | | | Cell 1 | +| Duplex mode | Config 1 | | 1 | +| TDD Configuration | Config 1 | | TDD | +| DL initial BWP configuration | Config 1 | | TDDConf.3.1 | +| DL dedicated BWP configuration | Config 1 | | DLBWP.0.1 | +| UL initial BWP configuration | Config 1 | | DLBWP.1.1 | +| UL dedicated BWP configuration | Config 1 | | ULBWP.0.1 | +| CORESET Reference Channel | Config 1 | | ULBWP.1.1 | +| SSB Configuration | Config 1 | | CCR.3.1 TDD | +| SMTC Configuration | Config 1 | | CCR.3.3 TDD | +| PDSCH/PDCCH subcarrier spacing | Config 1 | | SSB.1 FR2-1 | +| CSI-RS for RLM | Config 1 | | SMTC.1 | +| TRS configuration | | | 120 KHz | +| TCI configuration for PDCCH#1/PDSCH | | | Resource #4 in TRS.2.1 TDD | +| TCI configuration for PDCCH#2 | | | Resource #4 in TRS.2.2 TDD | +| OCNG parameters | | | TRS.2.1 TDD | +| CP length | | | TRS.2.2 TDD | +| Out of sync transmission parameters | DCI format | | TCI.State.2 | +| | Number of Control OFDM symbols | | TCI.State.3 | +| | Aggregation level | CCE | OP.1 | +| | Ratio of hypothetical PDCCH RE energy to average CSI-RS RE energy | dB | Normal | +| | Ratio of hypothetical PDCCH DMRS energy to average CSI-RS RE energy | dB | 1-0 | +| | DMRS precoder granularity | | 2 | +| | REG bundle size | | 8 | +| In sync transmission parameters | DCI format | | 4 | +| | Number of Control OFDM symbols | | 1-0 | +| | Aggregation level | CCE | 2 | +| | Ratio of hypothetical PDCCH RE energy to average CSI-RS RE energy | dB | 4 | +| | Ratio of hypothetical PDCCH DMRS energy to average CSI-RS RE energy | dB | 0 | +| | DMRS precoder granularity | | 0 | +| | REG bundle size | | REG bundle size | +| Layer 3 filtering | | | 6 | +| T310 timer | | ms | Enabled | +| T311 timer | | ms | 1000 | +| N310 | | | 1000 | +| N311 | | | 1 | +| CSI-RS for CSI reporting | Config 1 | | 1 | +| T1 | | s | CSI-RS.3.1 TDD | +| T2 | | s | 0.2 | +| T3 | | s | 0.2 | +| T4 | | s | 0.24 | +| T5 | | s | 0.2 | +| D1 | | s | 0.88 | +| Note 1: IAB-MT-specific PDCCH is not transmitted after T1 starts. | | | 0.84 | + +**Table G.2.3.1.8.1-3: Cell specific test parameters for FR2-1 for CSI-RS in-sync radio link monitoring in non-DRX** + +| Parameter | Unit | Test 1 | | | | | | | | | | | | | | | +|-----------------------------------------------|----------|--------------------------------------|----------------------|-----|------|---------------------|----------------------|-----|-----|-----|-----|--|--|--|--|--| +| | | T1 | T2 | T3 | T4 | T5 | T1 | T2 | T3 | T4 | T5 | | | | | | +| AoA setup | | AoA setup as defined in clause G.1.8 | | | | | | | | | | | | | | | +| Assumption for IAB-MT beams Note 8 | | AoA1
Rough | | | | | AoA2
Rough | | | | | | | | | | +| PDCCH_beta | dB | 4 | | | | | Not sent | | | | | | | | | | +| PDCCH_DMRS_beta | dB | 4 | | | | | | | | | | | | | | | +| PBCH_beta | dB | 0 | | | | | | | | | | | | | | | +| PSS_beta | dB | | | | | | | | | | | | | | | | +| SSS_beta | dB | | | | | | | | | | | | | | | | +| PDSCH_beta | dB | | | | | | | | | | | | | | | | +| OCNG_beta | dB | | | | | | | | | | | | | | | | +| SNR on RLM-RS1 | Config 1 | 2 Note 9 | -6 Note 9 | -15 | -4.5 | 2 Note 9 | | | | | | | | | | | +| SNR on RLM-RS2 | Config 1 | Not sent | | | | | 2 Note 9 | -14 | -15 | -15 | -14 | | | | | | +| SNR on other channels and signals | Config 1 | 2 Note 10 | | | | | N/A | | | | | | | | | | +| | Config 1 | -92.1 | | | | | -92.1 | | | | | | | | | | +| Propagation condition | | TDL-C 300ns 100Hz | | | | | TDL-C 300ns 100Hz | | | | | | | | | | + +Note 1: OCNG shall be used such that the resources in Cell 1 are fully allocated and a constant total transmitted power spectral density is achieved for all OFDM symbols. +Note 2: The uplink resources for CSI reporting are assigned to the IAB-MT prior to the start of time period T1. +Note 3: NZP CSI-RS resource set configuration for CSI reporting are assigned to the IAB-MT prior to the start of time period T1. +Note 4: The timers and layer 3 filtering related parameters are configured prior to the start of time period T1. +Note 5: The signal contains PDCCH for IAB-MTs other than the device under test as part of OCNG. +Note 6: SNR levels correspond to the signal to noise ratio over the SSS REs. +Note 7: The SNR in time periods T1, T2, T3, T4 and T5 is denoted as SNR1, SNR2, SNR3, SNR4 and SNR5 respectively in figure G.2.3.1.8.1-1. +Note 8: Information about types of IAB-MT beam does not limit IAB-MT implementation or test system implementation. +Note 9: This IAB-MT allows up to 1dB degradation from applied SNR to IAB-MT baseband. + +![Figure G.2.3.1.8.1-1: SNR variation for CSI-RS in-sync testing. The graph shows SNR levels (SNR1/5, SNR4, SNR2, SNR3) over time intervals T1, T2, T3, T4, and T5. The RLM-RS1 SNR level (red line) starts at SNR1/5 in T1, drops to SNR2 in T2, drops to SNR3 in T3, rises to SNR4 in T4, and rises to SNR1/5 in T5. The RLM-RS2 SNR level (green line) starts at SNR1/5 in T1, drops to SNR3 in T2, stays at SNR3 in T3, rises to SNR2 in T4, and rises to SNR1/5 in T5. Thresholds Qin and Qout are indicated by horizontal dashed lines. Time points A, B, C, D, E, F are marked on the x-axis, with D1 being the duration from the start of T5 to point F.](21976e2036dc7868558281681258568b_img.jpg) + +Figure G.2.3.1.8.1-1: SNR variation for CSI-RS in-sync testing. The graph shows SNR levels (SNR1/5, SNR4, SNR2, SNR3) over time intervals T1, T2, T3, T4, and T5. The RLM-RS1 SNR level (red line) starts at SNR1/5 in T1, drops to SNR2 in T2, drops to SNR3 in T3, rises to SNR4 in T4, and rises to SNR1/5 in T5. The RLM-RS2 SNR level (green line) starts at SNR1/5 in T1, drops to SNR3 in T2, stays at SNR3 in T3, rises to SNR2 in T4, and rises to SNR1/5 in T5. Thresholds Qin and Qout are indicated by horizontal dashed lines. Time points A, B, C, D, E, F are marked on the x-axis, with D1 being the duration from the start of T5 to point F. + +**Figure G.2.3.1.8.1-1: SNR variation for CSI-RS in-sync testing** + +**G.2.3.1.8.2 Test Requirements** + +The IAB-MT behaviour in each test during time durations T1, T2, T3, T4 and T5 shall be as follows: + +During the period from time point A to time point F (D1 second after the start of time duration T5) the IAB-MT shall transmit uplink signal at least in all uplink slots configured for CSI transmission according to the configured periodic CSI reporting on the PCell. + +The rate of correct events observed during repeated tests shall be at least 90%. + +## G.2.3.2 Beam Failure Detection and Link Recovery Procedure + +### G.2.3.2.1 Beam Failure Detection and Link Recovery Test for FR1 PCell configured with SSB-based BFD and LR + +#### G.2.3.2.1.1 Test Purpose and Environment + +The purpose of this test is to verify that the IAB-MT properly detects SSB-based beam failure in the set $q_0$ configured for a serving cell and that the IAB-MT performs correct SSB-based link recovery based on beam candidate set $q_1$ . The purpose is to test the downlink monitoring for beam failure detection within the IAB-MT's active DL BWP, during the evaluation period, and link recovery. This test will partly verify the SSB based beam failure detection and link recovery for an FR1 serving cell requirements in clause 12.3.2. + +The test parameters are given in Tables G.2.3.2.1.1-1, G.2.3.2.1.1-2 and G.2.3.2.1.1-3 below. There is one cell, cell 1 which is the active cell, in the test. The test consists of five successive time periods, with time duration of T1, T2, T3, T4 and T5 respectively. Figure G.2.3.2.1.1-1 shows the variation of the downlink SNR of the SSB in set $q_0$ in the active cell to emulate SSB based beam failure. Figure G.2.3.2.1.1-1 additionally shows the variation of the downlink L1-RSRP of the SSB in set $q_1$ of the candidate beam used for link recovery. Prior to the start of the time duration T1, the IAB-MT shall be fully synchronized to cell 1. The IAB-MT shall be configured for periodic CSI reporting with a reporting periodicity of 2 ms. The IAB-MT is configured to perform inter-frequency measurements using GP ID #0 (40ms) in test 1. + +**Table G.2.3.2.1.1-1: Supported test configurations for FR1 PCell** + +| Configuration | Description | +|---------------|----------------------------------------------------------------------------------------| +| 1 | TDD duplex mode, 15 kHz SSB SCS, 10 MHz bandwidth | +| 2 | TDD duplex mode, 30 kHz SSB SCS, 40 MHz bandwidth | +| Note: | The IAB-MT is only required to pass in one of the supported test configurations in FR1 | + +**Table G.2.3.2.1.1-2: General test parameters for FR1 PCell for SSB-based beam failure detection and link recovery testing** + +| Parameter | | Unit | Value | Comment | +|----------------------------------------------|-------------|------|-----------------|---------| +| | | | Test 1 | | +| Active PCell | | | Cell 1 | | +| RF Channel Number | | | 1 | | +| Duplex mode | Config 1, 2 | | TDD | | +| BWchannel | Config 1 | MHz | 10: NRB,c = 52 | | +| | Config 2 | | 40: NRB,c = 106 | | +| DL initial BWP configuration | Config 1, 2 | | DLBWP.0.1 | | +| DL dedicated BWP configuration | Config 1, 2 | | DLBWP.1.1 | | +| UL initial BWP configuration | Config 1, 2 | | ULBWP.0.1 | | +| UL dedicated BWP configuration | Config 1, 2 | | ULBWP.1.1 | | +| CORESET Reference Channel | Config 1 | | CR.1.1 TDD | | +| | Config 2 | | CR.2.1 TDD | | +| SSB Configuration | Config 1 | | SSB.3 FR1 | | +| | Config 2 | | SSB.4 FR1 | | +| SMTC Configuration | Config 1 | | SMTC.1 | | +| | Config 2 | | SMTC.1 | | +| PDSCH/PDCCH subcarrier spacing | Config 1 | | 15 KHz | | +| | Config 2 | | 30 KHz | | +| PRACH Configuration | Config 1 | | Table G.X | | +| | Config 2 | | Table G.X | | +| SSB Index assigned as BFD RS ( $q_0$ ) | | | 0 | | +| SSB Index assigned as CBD RS ( $q_1$ ) | | | 1 | | +| OCNG parameters | | | OP.1 | | +| CP length | | | Normal | | +| Correlation Matrix and Antenna Configuration | | | 2x2 Low | | +| Beam failure | DCI format | | 1-0 | | + +| | | | | | +|---------------------------------------------------------------------------------------------|---------------------------------------------------------------------|-----------------|-----------------|-----------------------------------------------------------------------------------------| +| detection transmission parameters | Number of Control OFDM symbols | | 2 | | +| | Aggregation level | CCE | 8 | | +| | Ratio of hypothetical PDCCH RE energy to average CSI-RS RE energy | dB | 0 | | +| | Ratio of hypothetical PDCCH DMRS energy to average CSI-RS RE energy | dB | 0 | | +| | DMRS precoder granularity | | REG bundle size | | +| | REG bundle size | | 6 | | +| rlmInSyncOutOfSyncThreshold | | | absent | When the field is absent, the IAB-MT applies the value 0. (Table 8.1.1-1 of TS 38.133). | +| rsrp-ThresholdSSB | Config 1 | dBm/
SCS kHz | -98 | Threshold used for $Q_{in\_LR\_SSB}$ | +| | Config 2 | | -95 | | +| powerControlOffsetSS | | | db0 | Used for deriving rsrp-ThresholdCSI-RS | +| beamFailureInstanceMaxCount | | | n1 | see clause 5.17 of TS 38.321 [14] | +| beamFailureDetectionTimer | | | pbfd4 | see clause 5.17 of TS 38.321 [14] | +| CSI-RS configuration for CSI reporting | Config 1 | | CSI-RS.1.1 TDD | | +| | Config 2 | | CSI-RS.2.1 TDD | | +| CSI-RS for tracking | Config 1 | | TRS.1.1 TDD | | +| | Config 2 | | TRS.1.2 TDD | | +| SSB Index assigned as RLM RS | | 0, 1 | | | +| T310 Timer | ms | 1000 | | | +| N310 | | 2 | | | +| T1 | | s | 0.2 | During this time the the IAB-MT shall be fully synchronized to cell 1 | +| T2 | | s | 0.37 | | +| T3 | | s | 0.24 | | +| T4 | | s | 0 | | +| T5 | | s | 0.17 | | +| D1 | | s | 0.13 | | +| Note 1: All configurations are assigned to the IAB-MT prior to the start of time period T1. | | | | | +| Note 2: IAB-MT-specific PDCCH is not transmitted after T1 starts. | | | | | + +**Table G.2.3.2.1.1-3: Cell specific test parameters for FR1 PCell for SSB-based beam failure detection and link recovery testing** + +| Parameter | Unit | Test 1 | | | | | | | | | | | | | | +|-----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------|------|-----|-----|--|--|--|--|--|--|--|--|--| +| | | T1 | T2 | T3 | T4 | T5 | | | | | | | | | | +| EPRE ratio of PDCCH DMRS to SSS | dB | | | 0 | | | | | | | | | | | | +| EPRE ratio of PDCCH to PDCCH DMRS | dB | | | | | | | | | | | | | | | +| EPRE ratio of PBCH DMRS to SSS | dB | | | | | | | | | | | | | | | +| EPRE ratio of PBCH to PBCH DMRS | dB | | | | | | | | | | | | | | | +| EPRE ratio of PSS to SSS | dB | | | | | | | | | | | | | | | +| EPRE ratio of PDSCH DMRS to SSS | dB | | | | | | | | | | | | | | | +| EPRE ratio of PDSCH to PDSCH DMRS | dB | | | | | | | | | | | | | | | +| EPRE ratio of OCNG DMRS to SSS | dB | | | | | | | | | | | | | | | +| EPRE ratio of OCNG to OCNG DMRS | dB | | | | | | | | | | | | | | | +| SNR_SSB of set $q_0$ | Config 1 | dB | 5 | -3 | -12 | -12 | | | | | | | | | | +| | Config 2 | dB | 5 | -3 | -12 | -12 | | | | | | | | | | +| SNR_SSB of set $q_1$ | Config 1 | dB | -10 | -10 | 10 | 10 | | | | | | | | | | +| | Config 2 | dB | -10 | -10 | 10 | 10 | | | | | | | | | | +| SSB_RP of set $q_1$ | Config 1 | dBm/SCS kHz | -108 | -108 | -88 | -88 | | | | | | | | | | +| | Config 2 | dBm/SCS kHz | -105 | -105 | -85 | -85 | | | | | | | | | | +| | Config 1 | dBm/15 kHz | -98 | | | | | | | | | | | | | +| | Config 2 | dBm/15 kHz | -98 | | | | | | | | | | | | | +| Propagation condition | | TDL-C 300ns 100Hz | | | | | | | | | | | | | | +| Note 1: | OCNG shall be used such that the resources in Cell 1 are fully allocated and a constant total transmitted power spectral density is achieved for all OFDM symbols. | | | | | | | | | | | | | | | +| Note 2: | The uplink resources for CSI reporting are assigned to the IAB-MT prior to the start of time period T1. | | | | | | | | | | | | | | | +| Note 3: | NZP CSI-RS resource set configuration for CSI reporting are assigned to the IAB-MT prior to the start of time period T1. | | | | | | | | | | | | | | | +| Note 4: | Void. | | | | | | | | | | | | | | | +| Note 5: | The timers and layer 3 filtering related parameters are configured prior to the start of time period T1. | | | | | | | | | | | | | | | +| Note 6: | The signal contains PDCCH for IAB-MTs other than the device under test as part of OCNG. | | | | | | | | | | | | | | | +| Note 7: | SNR levels correspond to the signal to noise ratio over the SSS REs. | | | | | | | | | | | | | | | +| Note 8: | The SNR in time periods T1, T2, T3, T4 and T5 is denoted as SNR1, SNR2 and SNR3 respectively in figure G.2.3.2.1.1-1. | | | | | | | | | | | | | | | +| Note 9: | The SNR values are specified for testing a IAB-MT which supports 2RX on at least one band. For testing of a IAB-MT which supports 4RX on all bands, the SNR during T3 is modified as specified in clause G.1.3. | | | | | | | | | | | | | | | + +![Figure G.2.3.2.1.1-1: SNR and L1-RSRP variation SSB for SSB-based beam failure detection and link recovery testing. The graph shows SNR levels (SNR1, SNR2, SNR3) and L1-RSRP level over time, divided into periods T1 to T5. Key thresholds shown are rsrp-ThresholdSSB and Q_out_LR_SSB. Points A through F mark transitions between SNR levels.](be69dd6f7ffed68b2738a5dd34ad4fd2_img.jpg) + +The figure illustrates the variation of SNR and L1-RSRP levels over time for SSB-based beam failure detection and link recovery testing. The time axis is divided into five periods: T1, T2, T3, T4, and T5. + +During T1, the SNR level is SNR1, corresponding to SSB $q_0$ . + +At point A (start of T2), the SNR level drops to SNR2. + +At point B (start of T3), the SNR level drops further to SNR3. + +Simultaneously at point B, the L1-RSRP level jumps to a higher level corresponding to SSB $q_1$ . + +The L1-RSRP level remains constant at the $q_1$ level through point F. + +Two horizontal dashed lines represent thresholds: 'rsrp-ThresholdSSB' and ' $Q_{out\_LR\_SSB}$ '. + +Point C is on the SNR3 level during T3. + +Point D is on the time axis between T3 and T4. + +Point E is on the time axis between T4 and T5. + +Point F is at the end of the timeline shown. + +A duration 'D1' is indicated between points E and F. + +Figure G.2.3.2.1.1-1: SNR and L1-RSRP variation SSB for SSB-based beam failure detection and link recovery testing. The graph shows SNR levels (SNR1, SNR2, SNR3) and L1-RSRP level over time, divided into periods T1 to T5. Key thresholds shown are rsrp-ThresholdSSB and Q\_out\_LR\_SSB. Points A through F mark transitions between SNR levels. + +**Figure G.2.3.2.1.1-1: SNR and L1-RSRP variation SSB for SSB-based beam failure detection and link recovery testing** + +#### G.2.3.2.1.2 Test Requirements + +The IAB-MT behaviour during time durations T1, T2, T3, T4 and T5 shall be as follows: + +During the time duration T1 and T2, the IAB-MT shall transmit uplink signal at least in all subframes configured for CSI transmission on Cell 1. + +During the period from time point A to time point B the IAB-MT shall transmit uplink signal in Cell 1 in all uplink slots configured for CSI transmission according to the configured periodic CSI reporting for Cell 1. + +During T3 the IAB-MT shall detect beam failure and initiate link recovery. During T4 and T5 the IAB-MT measures and evaluate beam candidate from beam candidate set $q_1$ . + +No later than time point F occurring no later than $D1 = 120+10$ ms after the start of T5, the IAB-MT shall transmit preamble on a beam associated with the candidate beam set $q_1$ . The IAB-MT shall not transmit preamble on a beam associated with the candidate beam set $q_1$ earlier than time point B. + +Test is concluded once the test equipment has received the initial preamble transmission from the IAB-MT. The rate of correct events observed during repeated tests shall be at least 90%. + +#### G.2.3.2.2 Beam Failure Detection and Link Recovery Test for FR2-1 PCell configured with SSB-based BFD and LR + +##### G.2.3.2.2.1 Test Purpose and Environment + +The purpose of this test is to verify that the IAB-MT properly detects SSB-based beam failure in the set $q_0$ configured for a serving cell and that the IAB-MT performs correct SSB-based link recovery based on beam candidate set $q_1$ . The purpose is to test the downlink monitoring for beam failure detection within the IAB-MT active DL BWP, during the evaluation period, and link recovery, when no DRX is used. This test will partly verify the SSB based beam failure detection and link recovery for an FR2-1 serving cell requirements in clause 12.3.2.2. + +The test parameters are given in Tables G.2.3.2.2.1-1, G.2.3.2.2.1-2 and G.2.3.2.2.1-3 below. There is one cell, cell 1 which is the active cell, in the test. The test consists of five successive time periods, with time duration of T1, T2, T3, T4 and T5 respectively. Figure G.2.3.2.X.1-1 shows the variation of the downlink SNR of the SSB in set $q_0$ in the active cell to emulate SSB based beam failure. Figure G.2.3.2.2.1-1 additionally shows the variation of the downlink L1-RSRP of the SSB in set $q_1$ of the candidate beam used for link recovery. Prior to the start of the time duration T1, the IAB-MT shall be fully synchronized to cell 1. The IAB-MT shall be configured for periodic CSI reporting with a reporting periodicity of 2 ms. In the test, DRX configuration is not enabled. + +**Table G.2.3.2.2.1-1: Supported test configurations for FR2-1 PCell** + +| Configuration | Description | +|---------------|------------------------------------------------------------------------------------------| +| 1 | TDD duplex mode, 120 kHz SSB SCS, 100 MHz bandwidth | +| 2 | TDD duplex mode, 240 kHz SSB SCS, 100 MHz bandwidth | +| Note: | The IAB-MT is only required to pass in one of the supported test configurations in FR2-1 | + +**Table G.2.3.2.2.1-2: General test parameters for FR2-1 PCell for SSB-based beam failure detection and link recovery testing** + +| Parameter | | Unit | Value | Comment | +|------------------------------------------------|---------------------------------------------------------------------|------|-----------------------------|--------------------------------------------------------------------------------| +| | | | Test 1 | | +| Active PCell | | | Cell 1 | | +| RF Channel Number | | | 1 | | +| Duplex mode | Config 1, 2 | | TDD | | +| BW channel | Config 1, 2 | | 100: N RB,c = 66 | | +| DL initial BWP configuration | Config 1, 2 | | DLBWP.0.1 | | +| DL dedicated BWP configuration | Config 1, 2 | | DLBWP.1.1 | | +| UL initial BWP configuration | Config 1, 2 | | ULBWP.0.1 | | +| UL dedicated BWP configuration | Config 1, 2 | | ULBWP.1.1 | | +| CORESET Reference Channel | Config 1, 2 | | CR. 3.1 TDD | | +| SSB Configuration | Config 1 | | SSB.1 FR2-1 | | +| | Config 2 | | SSB.2 FR2-1 | | +| SMTC Configuration | Config 1, 2 | | SMTC.3 | | +| PDSCH/PDCCH subcarrier spacing | Config 1, 2 | | 120 KHz | | +| SSB index assigned as BFD RS (q 0 ) | | | 0 | | +| SSB index assigned as CBD RS (q 1 ) | | | 1 | | +| OCNG parameters | | | OP.1 | | +| CP length | | | Normal | | +| Beam failure detection transmission parameters | DCI format | | 1-0 | | +| | Number of Control OFDM symbols | | 2 | | +| | Aggregation level | CCE | 8 | | +| | Ratio of hypothetical PDCCH RE energy to average CSI-RS RE energy | dB | 0 | | +| | Ratio of hypothetical PDCCH DMRS energy to average CSI-RS RE energy | dB | 0 | | +| | DMRS precoder granularity | | REG bundle size | | +| | REG bundle size | | 6 | | +| DRX | | | OFF | | +| rlmlnSyncOutOfSyncThreshold | | | absent | When the field is absent, the IAB-MT applies the value 0. (Table 8.1.1-1 in TS | + +| | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------|----------------|-----------------------------------------------------------------------| +| | | | | 38.133 [6]). | +| rsrp-ThresholdSSB | Config 1 | dBm/SSB SCS | -94.5 | Threshold used for $Q_{in\_LR\_SSB}$ | +| | Config 2 | | -91.5 | | +| powerControlOffsetSS | | | db0 | Used for deriving rsrp-ThresholdCSI-RS | +| beamFailureInstanceMaxCount | | | n1 | see clause 5.17 of TS 38.321 [7] | +| beamFailureDetectionTimer | | | pbfd4 | see clause 5.17 of TS 38.321 [7] | +| CSI-RS configuration for CSI reporting | Config 1, 2 | | CSI-RS.3.1 TDD | | +| TCI states | | | TCI.State.0 | | +| CSI-RS for tracking | Config 1, 2 | | TRS.2.1 TDD | | +| SSB index assigned as RLM RS | | | 0, 1 | | +| T310 Timer | | ms | 1000 | | +| N310 | | | 2 | | +| T1 | | s | 1 | During this time the the IAB-MT shall be fully synchronized to cell 1 | +| T2 | | s | 2.61 | | +| T3 | | s | 1.64 | | +| T4 | | s | 0 | | +| T5 | | s | 1.01 | | +| D1 | | s | 0.97 | | +| Note 1: All configurations are assigned to the IAB-MT prior to the start of time period T1.
Note 2: IAB-MT-specific PDCCH is not transmitted after T1 starts. | | | | | + +*Editor's note: An additional RS for RLM, different from BFD-RS at constant high SNR shall be configured as part of the test configuration.* + +**Table G.2.3.2.2.1-3: Cell specific test parameters for FR2-1 PCell for SSB-based beam failure detection and link recovery testing** + +| Parameter | Unit | Test 1 | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|---------------------------|--------|-------|-------|-------|--|--|--|--|--| +| | | T1 | T2 | T3 | T4 | T5 | | | | | | +| AoA setup | | Setup 1 defined in G.1.18 | | | | | | | | | | +| EPRE ratio of PDCCH DMRS to SSS | dB | 0 | | | | | | | | | | +| EPRE ratio of PDCCH to PDCCH DMRS | dB | | | | | | | | | | | +| EPRE ratio of PBCH DMRS to SSS | dB | | | | | | | | | | | +| EPRE ratio of PBCH to PBCH DMRS | dB | | | | | | | | | | | +| EPRE ratio of PSS to SSS | dB | | | | | | | | | | | +| EPRE ratio of PDSCH DMRS to SSS | dB | | | | | | | | | | | +| EPRE ratio of PDSCH to PDSCH DMRS | dB | | | | | | | | | | | +| EPRE ratio of OCNG DMRS to SSS | dB | | | | | | | | | | | +| EPRE ratio of OCNG to OCNG DMRS | dB | | | | | | | | | | | +| SNR_SSB of set $q_0$ | Config 1 | 5 | -3 | -12 | -12 | -12 | | | | | | +| | Config 2 | 5 | -3 | -12 | -12 | -12 | | | | | | +| SNR_SSB of set $q_1$ | Config 1 | 0.2 | 0.2 | 20.2 | 20.2 | 20.2 | | | | | | +| | Config 2 | 0.2 | 0.2 | 20.2 | 20.2 | 20.2 | | | | | | +| SSB_RP of set $q_1$ | Config 1 | -104.5 | -104.5 | -84.5 | -84.5 | -84.5 | | | | | | +| | Config 2 | -101.5 | -101.5 | -81.5 | -81.5 | -81.5 | | | | | | +| | Config 1 | -104.7 | | | | | | | | | | +| | Config 2 | -104.7 | | | | | | | | | | +| Propagation condition | | TDL-A 30ns 75Hz | | | | | | | | | | +| Note 1: OCNG shall be used such that the resources in Cell 1 are fully allocated and a constant total transmitted power spectral density is achieved for all OFDM symbols. | | | | | | | | | | | | +| Note 2: The uplink resources for CSI reporting are assigned to the IAB-MT prior to the start of time period T1. | | | | | | | | | | | | +| Note 3: NZP CSI-RS resource set configuration for CSI reporting are assigned to the IAB-MT prior to the start of time period T1. | | | | | | | | | | | | +| Note 4: Void | | | | | | | | | | | | +| Note 5: The timers and layer 3 filtering related parameters are configured prior to the start of time period T1. | | | | | | | | | | | | +| Note 6: The signal contains PDCCH for IAB-MTs other than the device under test as part of OCNG. | | | | | | | | | | | | +| Note 7: SNR levels correspond to the signal to noise ratio over the SSS REs. | | | | | | | | | | | | +| Note 8: The SNR in time periods T1, T2, T3, T4 and T5 is denoted as SNR1, SNR2 and SNR3 respectively in figure G.2.3.2.2.X.1-1. | | | | | | | | | | | | +| Note 9: The SNR values are specified for testing an IAB-MT which supports 2RX on at least one band. For testing of an IAB-MT which supports 4RX on all bands, the SNR during T3 is modified as specified in clause G.1.3. 1 | | | | | | | | | | | | + +![Figure G.2.3.2.2.1-1: SNR and L1-RSRP variation SSB for SSB-based beam failure detection and link recovery testing in non-DRX mode. The graph shows SNR level and L1-RSRP level over time, divided into periods T1 through T5. Key thresholds include rsrp-ThresholdSSB and Q_out_LR_SSB. Points A through F mark specific time intervals, with D1 indicating a duration between E and F.](a8e0f16a3f8bdfbd54d8d18cbdaab339_img.jpg) + +The figure illustrates the variation of SNR and L1-RSRP levels over time for SSB-based beam failure detection and link recovery testing. The vertical axis represents the signal level, with labels for SNR level, L1-RSRP level, SSB $q_0$ , SSB $q_1$ , rsrp-ThresholdSSB, and $Q_{out\_LR\_SSB}$ . The horizontal axis represents time, divided into five periods: T1, T2, T3, T4, and T5. Key time points are marked as A, B, C, D, E, and F. A duration D1 is indicated between points E and F. The SNR level is shown as a blue line, and the L1-RSRP level as a yellow line. The SNR level starts at SNR1 in T1, drops to SNR2 in T2, and then to SNR3 in T3. The L1-RSRP level starts at SSB $q_0$ in T1, drops to SSB $q_1$ in T2, and remains constant in T3, T4, and T5. + +Figure G.2.3.2.2.1-1: SNR and L1-RSRP variation SSB for SSB-based beam failure detection and link recovery testing in non-DRX mode. The graph shows SNR level and L1-RSRP level over time, divided into periods T1 through T5. Key thresholds include rsrp-ThresholdSSB and Q\_out\_LR\_SSB. Points A through F mark specific time intervals, with D1 indicating a duration between E and F. + +**Figure G.2.3.2.2.1-1: SNR and L1-RSRP variation SSB for SSB-based beam failure detection and link recovery testing in non-DRX mode** + +#### G.2.3.2.2.2 Test Requirements + +The IAB-MT behaviour during time durations T1, T2, T3, T4 and T5 shall be as follows: + +During the time duration T1 and T2, the IAB-MT shall transmit uplink signal at least in all subframes configured for CSI transmission on Cell 1. + +During the period from time point A to time point B the IAB-MT shall transmit uplink signal in Cell 1 in all uplink slots configured for CSI transmission according to the configured periodic CSI reporting for Cell 1. + +During T3 the IAB-MT shall detect beam failure and initiate link recovery. During T4 and T5 the IAB-MT measures and evaluate beam candidate from beam candidate set $q_1$ . + +No later than time point F occurring no later than $D1 = 560+650$ ms after the start of T5, the IAB-MT shall transmit preamble on a beam associated with the candidate beam set $q_1$ . The IAB-MT shall not transmit preamble on a beam associated with the candidate beam set $q_1$ earlier than time point B. + +Test is concluded once the test equipment has received the initial preamble transmission from the IAB-MT. The rate of correct events observed during repeated tests shall be at least 90%. + +#### G.2.3.2.3 Beam Failure Detection and Link Recovery Test for FR1 PCell configured with CSI-RS-based BFD and LR + +##### G.2.3.2.3.1 Test Purpose and Environment + +The purpose of this test is to verify that the IAB-MT properly detects CSI-RS-based beam failure in the set $q_0$ configured for a serving cell and that the IAB-MT performs correct CSI-RS-based link recovery based on beam candidate set $q_1$ . The purpose is to test the downlink monitoring for beam failure detection within the IAB-MT's active DL BWP, during the evaluation period, and link recovery. This test will partly verify the CSI-RS based beam failure detection and link recovery for an FR1 serving cell requirements in clause 12.3.2. + +The test parameters are given in Tables G.2.3.2.3.1-1, G.2.3.2.3.1-2 and G.2.3.2.3.1-3 below. There is one cell, cell 1 which is the active cell, in the test. The test consists of five successive time periods, with time duration of T1, T2, T3, T4 and T5 respectively. Figure G.2.3.2.3.1-1 shows the variation of the downlink SNR of the CSI-RS in set $q_0$ in the active cell to emulate CSI-RS based beam failure. Figure G.2.3.2.3.1-1 additionally shows the variation of the downlink L1-RSRP of the CSI-RS in set $q_1$ of the candidate beam used for link recovery. Prior to the start of the time duration T1, the IAB-MT shall be fully synchronized to cell 1. The IAB-MT shall be configured for periodic CSI reporting with a reporting periodicity of [2] ms. + +**Table G.2.3.2.3.1-1: Supported test configurations for FR1 PCell** + +| Configuration | Description | +|---------------|----------------------------------------------------------------------------------------| +| 1 | TDD duplex mode, 15 kHz SSB SCS, 10 MHz bandwidth | +| 2 | TDD duplex mode, 30 kHz SSB SCS, 40 MHz bandwidth | +| Note: | The IAB-MT is only required to pass in one of the supported test configurations in FR1 | + +**Table G.2.3.2.3.1-2: General test parameters for FR1 PCell for CSI-RS-based beam failure detection and link recovery testing** + +| Parameter | | Unit | Value | Comment | +|-------------------------------------------------------------------|---------------------------------------------------------------------|--------------------|-----------------|-----------------------------------------------------------------------------------------| +| | | | Test 1 | | +| Active PCell | | | Cell 1 | | +| RF Channel Number | | | 1 | | +| Duplex mode | | | TDD | | +| CORESET | Config 1 | | CR.1.1 TDD | | +| Reference Channel | Config 2 | | CR.2.1 TDD | | +| SSB | Config 1 | | SSB.1 FR1 | | +| Configuration | Config 2 | | SSB.2 FR1 | | +| SMT | Config 1 | | SMT.1 | G.1.6 | +| Configuration | Config 2 | | SMT.1 | | +| PDSCH/PDCCH | Config 1 | | 15 KHz | | +| subcarrier spacing | Config 2 | | 30 KHz | | +| csi-RS-Index assigned as beam failure detection RS in set $q_0$ | | | 0 | | +| OCNG parameters | | | OP.1 | G.1.2.1 | +| CP length | | | Normal | | +| Correlation Matrix and Antenna Configuration | | | 2x2 Low | | +| Beam failure detection transmission parameters | DCI format | | 1-0 | | +| | Number of Control OFDM symbols | | 2 | | +| | Aggregation level | CCE | 8 | | +| | Ratio of hypothetical PDCCH RE energy to average CSI-RS RE energy | dB | 0 | | +| | Ratio of hypothetical PDCCH DMRS energy to average CSI-RS RE energy | dB | 0 | | +| | DMRS precoder granularity | | REG bundle size | | +| | REG bundle size | | 6 | | +| csi-RS-Index assigned as candidate beam detection RS in set $q_1$ | | | 1 | N | +| rlmlnSyncOutOfSyncThreshold | | | absent | When the field is absent, the IAB-MT applies the value 0. (Table 8.1.1-1 of TS 38.133). | +| rsrp-ThresholdSSB | Config 1 | dBm/
SCS
kHz | -98 | Threshold used for $Q_{in\_LR\_SSB}$ | +| | Config 2 | | -95 | | +| powerControlOffsetSS | | | db0 | Used for deriving rsrp-ThresholdCSI-RS | +| beamFailureInstanceMaxCount | | | n1 | see clause 5.17 of TS 38.321 [14] | +| beamFailureDetectionTimer | | | pbfd4 | see clause 5.17 of TS 38.321 [14] | +| CSI-RS configuration for $q_0$ and $q_1$ | Config 1 | | CSI-RS.1.2 TDD | | + +| | | | | | +|-------------------------------------------------------------------|----------|----|----------------|-----------------------------------------------------------------------| +| CSI-RS configuration for CSI reporting | Config 2 | | CSI-RS.2.2 TDD | | +| | Config 1 | | CSI-RS.1.1 TDD | | +| | Config 2 | | CSI-RS.2.1 TDD | | +| TRS configuration | Config 1 | | TRS.1.1 TDD | | +| | Config 2 | | TRS.1.2 TDD | | +| CSI-RS-Index assigned as RLM RS | Config 1 | | CSI-RS.1.2 TDD | | +| | Config 2 | | CSI-RS.2.2 TDD | | +| T310 Timer | | ms | 1000 | | +| N310 | | | 2 | | +| T1 | | s | 0.2 | During this time the the IAB-MT shall be fully synchronized to cell 1 | +| T2 | | s | 0.18 | | +| T3 | | s | 0.14 | | +| T4 | | s | 0 | | +| T5 | | s | 0.08 | | +| D1 | | s | 0.04 | | +| Note 1: IAB-MT-specific PDCCH is not transmitted after T1 starts. | | | | | + +**Table G.2.3.2.3.1-3: Cell specific test parameters for FR1 PCell for CSI-RS-based beam failure detection and link recovery testing** + +| Parameter | Unit | Test 1 | | | | | | | | | | +|-----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------|------|-----|-----|--|--|--|--|--| +| | | T1 | T2 | T3 | T4 | T5 | | | | | | +| EPRE ratio of PDCCH DMRS to SSS | dB | | | 0 | | | | | | | | +| EPRE ratio of PDCCH to PDCCH DMRS | dB | | | | | | | | | | | +| EPRE ratio of PBCH DMRS to SSS | dB | | | | | | | | | | | +| EPRE ratio of PBCH to PBCH DMRS | dB | | | | | | | | | | | +| EPRE ratio of PSS to SSS | dB | | | | | | | | | | | +| EPRE ratio of PDSCH DMRS to SSS | dB | | | | | | | | | | | +| EPRE ratio of PDSCH to PDSCH DMRS | dB | | | | | | | | | | | +| EPRE ratio of OCNG DMRS to SSS | dB | | | | | | | | | | | +| EPRE ratio of OCNG to OCNG DMRS | dB | | | | | | | | | | | +| SNR_CSI-RS of set $q_0$ | Config 1 | dB | 5 | -3 | -12 | -12 | | | | | | +| | Config 2 | dB | 5 | -3 | -12 | -12 | | | | | | +| SNR_CSI-RS of set $q_1$ | Config 1 | dB | -10 | -10 | 10 | 10 | | | | | | +| | Config 2 | dB | -10 | -10 | 10 | 10 | | | | | | +| CSI-RS_RP of set $q_1$ | Config 1 | dBm/SCS kHz | -108 | -108 | -88 | -88 | | | | | | +| | Config 2 | dBm/SCS kHz | -105 | -105 | -85 | -85 | | | | | | +| | Config 1 | dBm/15 KHz | | | -98 | | | | | | | +| | Config 2 | dBm/15 KHz | | | -98 | | | | | | | +| Propagation condition | | TDL-C 300ns 100Hz | | | | | | | | | | +| Note 1: | OCNG shall be used such that the resources in Cell 1 are fully allocated and a constant total transmitted power spectral density is achieved for all OFDM symbols. | | | | | | | | | | | +| Note 2: | The uplink resources for CSI reporting are assigned to the IAB-MT prior to the start of time period T1. | | | | | | | | | | | +| Note 3: | NZP CSI-RS resource set configuration for CSI reporting are assigned to the IAB-MT prior to the start of time period T1. | | | | | | | | | | | +| Note 4: | Void | | | | | | | | | | | +| Note 5: | The timers and layer 3 filtering related parameters are configured prior to the start of time period T1. | | | | | | | | | | | +| Note 6: | The signal contains PDCCH for IAB-MTs other than the device under test as part of OCNG. | | | | | | | | | | | +| Note 7: | SNR levels correspond to the signal to noise ratio over the REs carrying CSI-RS. | | | | | | | | | | | +| Note 8: | The SNR in time periods T1, T2, T3, T4 and T5 is denoted as SNR1, SNR2 and SNR3 respectively in figure G.2.3.2.2.1-1. | | | | | | | | | | | +| Note 9: | The SNR values are specified for testing a IAB-MT which supports 2RX on at least one band. For testing of a IAB-MT which supports 4RX on all bands, the SNR during T3 is modified as specified in clause G.1.3. | | | | | | | | | | | + +![Figure G.2.3.2.3.1-1: SNR and L1-RSRP variation for CSI-RS-based beam failure detection and link recovery testing. The graph shows SNR levels (SNR1, SNR2, SNR3) and L1-RSRP level (CSI-RS q1) over time. The x-axis is divided into time periods T1, T2, T3, T4, and T5, with markers A, B, C, D, E, and F. A horizontal dashed line represents the rsrp-ThresholdCSI-RS, and another horizontal dashed line represents the Q_out_LR_CSI-RS threshold. The L1-RSRP level starts at a high value (SNR1) and drops to a lower value (SNR2) at point B, then drops further to SNR3 at point C. The SNR levels remain constant throughout the time periods shown.](e4a32ec6d1b56eec38fd6f6313f83b06_img.jpg) + +Figure G.2.3.2.3.1-1: SNR and L1-RSRP variation for CSI-RS-based beam failure detection and link recovery testing. The graph shows SNR levels (SNR1, SNR2, SNR3) and L1-RSRP level (CSI-RS q1) over time. The x-axis is divided into time periods T1, T2, T3, T4, and T5, with markers A, B, C, D, E, and F. A horizontal dashed line represents the rsrp-ThresholdCSI-RS, and another horizontal dashed line represents the Q\_out\_LR\_CSI-RS threshold. The L1-RSRP level starts at a high value (SNR1) and drops to a lower value (SNR2) at point B, then drops further to SNR3 at point C. The SNR levels remain constant throughout the time periods shown. + +**Figure G.2.3.2.3.1-1: SNR and L1-RSRP variation for CSI-RS-based beam failure detection and link recovery testing** + +### G.2.3.2.3.2 Test Requirements + +The IAB-MT behaviour during time durations T1, T2, T3, T4 and T5 shall be as follows: + +During the time duration T1 and T2, the IAB-MT shall transmit uplink signal at least in all subframes configured for CSI transmission on Cell 1. + +During the period from time point A to time point B the IAB-MT shall transmit uplink signal in Cell 1 in all uplink slots configured for CSI transmission according to the configured periodic CSI reporting for Cell 1. + +During T3 the shall detect beam failure and initiat link recovery. During T4 and T5 the IAB-MT measures and evaluate beam candidate from beam candidate set $q_1$ . + +No later than time point F occurring no later than $D1 = 30+10$ ms after the start of T5, the IAB-MT shall transmit preamble on a beam associated with the candidate beam set $q_1$ . The IAB-MT shall not transmit preamble on a beam associated with the candidate beam set $q_1$ earlier than time point B. + +Test is concluded once the test equipment has received the initial preamble transmission from the IAB-MT. The rate of correct events observed during repeated tests shall be at least 90%. + +### G.2.3.2.4 Beam Failure Detection and Link Recovery Test for FR2-1 PCell configured with CSI-RS-based BFD and LR in non-DRX mode + +#### G.2.3.2.4.1 Test Purpose and Environment + +The purpose of this test is to verify that the IAB-MT properly detects CSI-RS-based beam failure in the set $q_0$ configured for a serving cell and that the IAB-MT performs correct CSI-RS-based link recovery based on beam candidate set $q_1$ . The purpose is to test the downlink monitoring for beam failure detection within the IAB-MT's active DL BWP, during the evaluation period, and link recovery, when no DRX is used. This test will partly verify the CSI-RS based beam failure detection and link recovery for an FR2-1 serving cell requirements in clause 12.3.2. + +The test parameters are given in Tables G.2.3.2.4.1-1, G.2.3.2.4.1-2, and G.2.3.2.4.1-3 below. There is one cell, cell 1 which is the active cell, in the test. The test consists of five successive time periods, with time duration of T1, T2, T3, T4 and T5 respectively. Figure G.2.3.2.4.1-1 shows the variation of the downlink SNR of the CSI-RS in set $q_0$ in the active cell to emulate CSI-RS based beam failure. Figure G.2.3.2.4.1-1 additionally shows the variation of the downlink L1-RSRP of the CSI-RS in set $q_1$ of the candidate beam used for link recovery. Prior to the start of the time duration T1, the IAB-MT shall be fully synchronized to cell 1. The IAB-MT shall be configured for periodic CSI reporting with a reporting periodicity of [2] ms. In the test, DRX configuration is not enabled. + +**Table G.2.3.2.4.1-1: Supported test configurations for FR2-1 PCell** + +| Configuration | Description | +|---------------|-----------------------------------------------------| +| 1 | TDD duplex mode, 120 kHz SSB SCS, 100 MHz bandwidth | + +**Table G.2.3.2.4.1-2: General test parameters for FR2-1 PCell for CSI-RS based beam failure detection and link recovery testing in non-DRX mode** + +| Parameter | | Unit | Value | Comment | +|-----------------------------------------------------------------|------------|------|-------------|----------| +| | | | Test 1 | | +| Active PCell | | | Cell 1 | | +| RF Channel Number | | | 1 | | +| Duplex mode | Config 1 | | TDD | | +| TDD Configuration | Config 1 | | TBD | | +| CORESET Reference Channel | Config 1 | | CR.3.1 TDD | G.1.1.2 | +| SSB Configuration | Config 1 | | SSB.3 FR2-1 | G.1.5 | +| SMTC Configuration | Config 1 | | SMTC.3 | G.1.6 | +| PDSCH/PDCCH subcarrier spacing | Config 1 | | 120KHz | | +| csi-RS-Index assigned as beam failure detection RS in set $q_0$ | | | 0 | | +| TRS configuration | | | TRS.2.1 TDD | G.1.10.2 | +| TCI configuration | | | TBD | | +| OCNG parameters | | | OP.1 | G.1.2.1 | +| CP length | | | Normal | | +| Beam failure | DCI format | | 1-0 | | + +| | | | | | +|-------------------------------------------------------------------|---------------------------------------------------------------------|-------------|-----------------|---------------------------------------------------------------------------------------------| +| detection transmission parameters | Number of Control OFDM symbols | | 2 | | +| | Aggregation level | CCE | 8 | | +| | Ratio of hypothetical PDCCH RE energy to average CSI-RS RE energy | dB | 0 | | +| | Ratio of hypothetical PDCCH DMRS energy to average CSI-RS RE energy | dB | 0 | | +| | DMRS precoder granularity | | REG bundle size | | +| | REG bundle size | | 6 | | +| DRX | | | OFF | | +| csi-RS-Index assigned as candidate beam detection RS in set $q_1$ | | | 1 | | +| rlmInSyncOutOfSyncThreshold | | | absent | When the field is absent, the IAB-MT applies the value 0. (Table 8.1.1-1 in TS 38.133 [6]). | +| rsrp-ThresholdSSB | | dBm/SCS kHz | -94.5 | Threshold used for $Q_{in\_LR\_SSB}$ | +| powerControlOffsetSS | | | db0 | Used for deriving rsrp-ThresholdCSI-RS | +| beamFailureInstanceMaxCount | | | n1 | see clause 5.17 of TS 38.321 [14] | +| beamFailureDetectionTimer | | | pbfd4 | see clause 5.17 of TS 38.321 [14] | +| CSI-RS configuration for $q_0$ and $q_1$ | Config 1 | | CSI-RS.3.2 TDD | G.1.7.1 | +| CSI-RS configuration for CSI reporting | Config 1 | | CSI-RS.3.1 TDD | G.1.7.1 | +| csi-RS-Index assigned as RLM RS | | | 0, 1 | G.1.7.1 | +| T310 Timer | | ms | 1000 | | +| N310 | | | 2 | | +| T1 | | s | 0.2 | During this time the the IAB-MT shall be fully synchronized to cell 1 | +| T2 | | s | 0.18 | | +| T3 | | s | 0.14 | | +| T4 | | s | 0 | | +| T5 | | s | 0.08 | | +| D1 | | s | 0.04 | | +| Note 1: IAB-MT-specific PDCCH is not transmitted after T1 starts. | | | | | + +**Table G.2.3.2.4.1-3: Cell specific test parameters for FR2-1 PCell for CSI-RS based beam failure detection and link recovery testing in non-DRX mode** + +| Parameter | Unit | Test 1 | | | | | | | | | | | | | | +|-----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------|--------|-------|-------|--|--|--|--|--|--|--|--|--| +| | | T1 | T2 | T3 | T4 | T5 | | | | | | | | | | +| AoA setup | | Setup 1 defined in G.1.8 | | | | | | | | | | | | | | +| EPRE ratio of PDCCH DMRS to SSS | dB | 0 | | | | | | | | | | | | | | +| EPRE ratio of PDCCH to PDCCH DMRS | dB | | | | | | | | | | | | | | | +| EPRE ratio of PBCH DMRS to SSS | dB | | | | | | | | | | | | | | | +| EPRE ratio of PBCH to PBCH DMRS | dB | | | | | | | | | | | | | | | +| EPRE ratio of PSS to SSS | dB | | | | | | | | | | | | | | | +| EPRE ratio of PDSCH DMRS to SSS | dB | | | | | | | | | | | | | | | +| EPRE ratio of PDSCH to PDSCH DMRS | dB | | | | | | | | | | | | | | | +| EPRE ratio of OCNQ DMRS to SSS | dB | | | | | | | | | | | | | | | +| EPRE ratio of OCNQ to OCNQ DMRS | dB | | | | | | | | | | | | | | | +| SNR_CSI-RS of set $q_0$ | Config 1 | dB | 5 | -3 | -12 | -12 | | | | | | | | | | +| SNR_CSI-RS of set $q_1$ | Config 1 | dB | 0.2 | 0.2 | 20.2 | 20.2 | | | | | | | | | | +| CSI-RS_RP of set $q_1$ | Config 1 | dBm/SCS kHz | -104.5 | -104.5 | -84.5 | -84.5 | | | | | | | | | | +| | Config 1 | dBm/15 KHz | -104.7 | | | | | | | | | | | | | +| Propagation condition | | TDL-A 30ns 75Hz | | | | | | | | | | | | | | +| Note 1: | OCNQ shall be used such that the resources in Cell 1 are fully allocated and a constant total transmitted power spectral density is achieved for all OFDM symbols. | | | | | | | | | | | | | | | +| Note 2: | The uplink resources for CSI reporting are assigned to the IAB-MT prior to the start of time period T1. | | | | | | | | | | | | | | | +| Note 3: | NZP CSI-RS resource set configuration for CSI reporting are assigned to the IAB-MT prior to the start of time period T1. | | | | | | | | | | | | | | | +| Note 4: | Void | | | | | | | | | | | | | | | +| Note 5: | The timers and layer 3 filtering related parameters are configured prior to the start of time period T1. | | | | | | | | | | | | | | | +| Note 6: | The signal contains PDCCH for UEs other than the device under test as part of OCNQ. | | | | | | | | | | | | | | | +| Note 7: | SNR levels correspond to the signal to noise ratio over the REs carrying CSI-RS. | | | | | | | | | | | | | | | +| Note 8: | The SNR in time periods T1, T2, T3, T4 and T5 is denoted as SNR1, SNR2 and SNR3 respectively in figure G.2.3.2.x.1-1. | | | | | | | | | | | | | | | +| Note 9: | The SNR values are specified for testing an IAB-MT which supports 2RX on at least one band. For testing of an IAB-MT which supports 4RX on all bands, the SNR during T3 is modified as specified in clause G.1.3.2. | | | | | | | | | | | | | | | + +![Figure G.2.3.2.4.1-1: SNR and L1-RSRP variation for CSI-RS based beam failure detection and link recovery testing in non-DRX mode. The graph shows SNR levels (SNR1, SNR2, SNR3) and L1-RSRP level (CSI-RS q1) over time. The x-axis is divided into time periods T1, T2, T3, T4, and T5, with markers A, B, C, D, E, and F. A horizontal dashed line represents the rsrp-ThresholdCSI-RS, and another dashed line represents the Q_out_LR_CSI-RS threshold. The SNR levels fluctuate between these thresholds across the time periods.](17f63ca1463dd3a235a7bea317eceba2_img.jpg) + +Figure G.2.3.2.4.1-1: SNR and L1-RSRP variation for CSI-RS based beam failure detection and link recovery testing in non-DRX mode. The graph shows SNR levels (SNR1, SNR2, SNR3) and L1-RSRP level (CSI-RS q1) over time. The x-axis is divided into time periods T1, T2, T3, T4, and T5, with markers A, B, C, D, E, and F. A horizontal dashed line represents the rsrp-ThresholdCSI-RS, and another dashed line represents the Q\_out\_LR\_CSI-RS threshold. The SNR levels fluctuate between these thresholds across the time periods. + +**Figure G.2.3.2.4.1-1: SNR and L1-RSRP variation for CSI-RS based beam failure detection and link recovery testing in non-DRX mode****G.2.3.2.4.2 Test Requirements** + +The IAB-MT behaviour during time durations T1, T2, T3, T4 and T5 shall be as follows: + +During the time duration T1 and T2, the IAB-MT shall transmit uplink signal at least in all subframes configured for CSI transmission on Cell 1. + +During the period from time point A to time point B the IAB-MT shall transmit uplink signal in Cell 1 in all uplink slots configured for CSI transmission according to the configured periodic CSI reporting for Cell 1. + +During T3 the shall detect beam failure and initiat link recovery. During T4 and T5 the IAB-MT measures and evaluate beam candidate from beam candidate set $q_1$ . + +No later than time point F occurring no later than $D1 = 30 + 10$ ms after the start of T5, the IAB-MT shall transmit preamble on a beam associated with the candidate beam set $q_1$ . The IAB-MT shall not transmit preamble on a beam associated with the candidate beam set $q_1$ earlier than time point B. + +Test is concluded once the test equipment has received the initial preamble transmission from the IAB-MT. The rate of correct events observed during repeated tests shall be at least 90%. + +--- + +## Annex H (normative): Conditions for IAB-MT RRM requirements applicability for operating bands + +### H.1 Conditions for RRC\_CONNECTED state mobility for IAB-MT + +#### H.1.1 Introduction + +In Annex H.1, the following conditions are specified: + +- IAB-MT conditions which shall apply for IAB-MT RRC Connection Re-establishment requirements for NR intra-frequency cells in clause 12.1.1.1 and +- IAB-MT conditions which shall apply for IAB-MT RRC Connection Re-establishment requirements for NR inter-frequency cells in clause 12.1.1.1 and +- IAB-MT conditions which shall apply for IAB-MT RRC Connection Release with Redirection requirements for NR cells in clause 12.1.1.3. + +##### H.1.1.1 Conditions for Measurements on NR Intra-frequency Cells for RRC Connection Re-establishment + +This clause defines the following conditions in terms of SSB\_RP and SSB $\hat{E}_s/Iot$ for measurements on NR intra-frequency cells for RRC connection re-establishment: + +- The conditions are defined in Table H.1.1.1-1 for FR1 NR cells for Wide Area IAB-MT and IAB Type 1-H. +- The conditions are defined in Table H.1.1.1-2 for FR1 NR cells for Local Area IAB-MT and IAB Type 1-H. +- The conditions are defined in Table H.1.1.1-3 for FR1 NR cells for Wide Area IAB-MT and IAB Type 1-O. +- The conditions are defined in Table H.1.1.1-4 for FR1 NR cells for Local Area IAB-MT and IAB Type 1-O. +- The conditions are defined in Table H.1.1.1-5 for FR2-1 NR cells for Local Area and Wide Atea IAB-MT and IAB Type 2-O. + +**Table H.1.1.1-1: Conditions for RRC connection re-establishment for intra-frequency cell for Wide Area IAB-MT and IAB Type 1-H** + +| IAB-MT channel bandwidth (MHz) | SSB sub-carrier spacing (kHz) | Side conditions | | +|-----------------------------------------|-------------------------------|---------------------------------|--------------------------------------------------------------| +| | | SSB $\hat{E}_s/\text{lot}$ (dB) | Minimum SSB_RP (dBm) | +| 10, 15 | 30 | -6 | $-107 - 10 \cdot \text{Log}_{10}(N_{\text{PRB}} \cdot 12)$ | +| 20, 25, 30, 40, 50, 60, 70, 80, 90, 100 | 30 | -6 | $-101.4 - 10 \cdot \text{Log}_{10}(N_{\text{PRB}} \cdot 12)$ | + +NOTE 1: $N_{\text{PRB}}$ is the number of PRBs within the IAB-IMT channel bandwidth defined in section 5.3.2. + +**Table H.1.1.1-2: Conditions for RRC connection re-establishment for intra-frequency cell for Local Area IAB-MT and IAB Type 1-H** + +| IAB-MT channel bandwidth (MHz) | SSB sub-carrier spacing (kHz) | Side conditions | | +|-----------------------------------------|-------------------------------|---------------------------------|-------------------------------------------------------------| +| | | SSB $\hat{E}_s/\text{lot}$ (dB) | Minimum SSB_RP (dBm) | +| 10, 15 | 30 | -6 | $-99 - 10 \cdot \text{Log}_{10}(N_{\text{PRB}} \cdot 12)$ | +| 20, 25, 30, 40, 50, 60, 70, 80, 90, 100 | 30 | -6 | $-92.5 - 10 \cdot \text{Log}_{10}(N_{\text{PRB}} \cdot 12)$ | + +NOTE 1: $N_{\text{PRB}}$ is the number of PRBs within the IAB-IMT channel bandwidth defined in section 5.3.2. + +**Table H.1.1.1-3: Conditions for RRC connection re-establishment for intra-frequency cell for Wide Area IAB-MT and IAB Type 1-O** + +| IAB-MT channel bandwidth (MHz) | SSB sub-carrier spacing (kHz) | Side conditions | | +|-----------------------------------------|-------------------------------|---------------------------------|-------------------------------------------------------------------------------------------| +| | | SSB $\hat{E}_s/\text{lot}$ (dB) | Minimum SSB_RP (dBm) | +| 10, 15 | 30 | -6 | $-107 - 10 \cdot \text{Log}_{10}(N_{\text{PRB}} \cdot 12) - \Delta_{\text{OTAREFSENS}}$ | +| 20, 25, 30, 40, 50, 60, 70, 80, 90, 100 | 30 | -6 | $-101.4 - 10 \cdot \text{Log}_{10}(N_{\text{PRB}} \cdot 12) - \Delta_{\text{OTAREFSENS}}$ | + +NOTE 1: $N_{\text{PRB}}$ is the number of PRBs within the IAB-IMT channel bandwidth defined in section 5.3.2. + +**Table H.1.1.1-4: Conditions for RRC connection re-establishment for intra-frequency cell for Local Area IAB-MT and IAB Type 1-O** + +| IAB-MT channel bandwidth (MHz) | SSB sub-carrier spacing (kHz) | Side conditions | | +|-----------------------------------------|-------------------------------|---------------------------------|------------------------------------------------------------------------------------------| +| | | SSB $\hat{E}_s/\text{lot}$ (dB) | Minimum SSB_RP (dBm) | +| 10, 15 | 30 | -6 | $-99 - 10 \cdot \text{Log}_{10}(N_{\text{PRB}} \cdot 12) - \Delta_{\text{OTAREFSENS}}$ | +| 20, 25, 30, 40, 50, 60, 70, 80, 90, 100 | 30 | -6 | $-92.5 - 10 \cdot \text{Log}_{10}(N_{\text{PRB}} \cdot 12) - \Delta_{\text{OTAREFSENS}}$ | + +NOTE 1: $N_{\text{PRB}}$ is the number of PRBs within the IAB-IMT channel bandwidth defined in section 5.3.2. + +**Table H.1.1.1-5: Conditions for RRC connection re-establishment for intra-frequency cell for Local Area IAB-MT and IAB Type 2-O** + +| IAB-MT channel bandwidth (MHz) | SSB sub-carrier spacing (kHz) | Side conditions | | +|--------------------------------|-------------------------------|---------------------------------|---------------------------------------------------------------------------------------------------------------------------| +| | | SSB $\hat{E}_s/\text{lot}$ (dB) | Minimum SSB_RP (dBm) | +| 50 | 120 | -6 | $\text{EIS}_{\text{REFSENS\_50M}} - 10 \cdot \text{Log}_{10}(N_{\text{PRB}} \cdot 12) + \Delta_{\text{FR2\_REFSENS}} - 5$ | +| 100, 200, 400 | 120 | -6 | $\text{EIS}_{\text{REFSENS\_50M}} - 10 \cdot \text{Log}_{10}(N_{\text{PRB}} \cdot 12) - 2 + \Delta_{\text{FR2\_REFSENS}}$ | + +NOTE 1: $N_{\text{PRB}}$ is the number of PRBs within the IAB-IMT channel bandwidth defined in section 5.3.2. + +NOTE 2: $\text{EIS}_{\text{REFSENS\_50M}}$ for wide area IAB-MT and local area IAB-MT is defined in section 10.3.3.3. + +## H.1.1.2 Conditions for Measurements on NR Inter-frequency Cells for RRC Connection Re-establishment + +This clause defines the following conditions in terms of SSB\_RP and SSB $\hat{E}_s/\text{lot}$ for measurements on NR inter-frequency cells for RRC connection re-establishment: + +- The conditions are defined in Table H.1.1.2-1 for FR1 NR cells for Wide Area IAB-MT and IAB Type 1-H. + +- The conditions are defined in Table H.1.1.2-2 for FR1 NR cells for Local Area IAB-MT and IAB Type 1-H. +- The conditions are defined in Table H.1.1.2-3 for FR1 NR cells for Wide Area IAB-MT and IAB Type 1-O. +- The conditions are defined in Table H.1.1.2-4 for FR1 NR cells for Local Area IAB-MT and IAB Type 1-O. +- The conditions are defined in Table H.1.1.2-5 for FR2-1 NR cells for Local Area and Wide Area IAB-MT and IAB Type 2-O. + +**Table H.1.1.2-1: Conditions for RRC connection re-establishment for inter-frequency cell for Wide Area IAB-MT and IAB Type 1-H** + +| IAB-MT channel bandwidth (MHz) | SSB sub-carrier spacing (kHz) | Side conditions | | +|-----------------------------------------|-------------------------------|---------------------------------|-------------------------------------------------------------| +| | | SSB $\bar{E}_s/\text{lot}$ (dB) | Minimum SSB_RP (dBm) | +| 10, 15 | 30 | -4 | $-105 - 10 \cdot \text{Log}_{10}(N_{\text{PRB}} \cdot 12)$ | +| 20, 25, 30, 40, 50, 60, 70, 80, 90, 100 | 30 | -4 | $-99.4 - 10 \cdot \text{Log}_{10}(N_{\text{PRB}} \cdot 12)$ | + +NOTE 1: $N_{\text{PRB}}$ is the number of PRBs within the IAB-MT channel bandwidth defined in section 5.3.2. + +**Table H.1.1.2-2: Conditions for RRC connection re-establishment for inter-frequency cell for Local Area IAB-MT and IAB Type 1-H** + +| IAB-MT channel bandwidth (MHz) | SSB sub-carrier spacing (kHz) | Side conditions | | +|-----------------------------------------|-------------------------------|---------------------------------|-------------------------------------------------------------| +| | | SSB $\bar{E}_s/\text{lot}$ (dB) | Minimum SSB_RP (dBm) | +| 10, 15 | 30 | -4 | $-97 - 10 \cdot \text{Log}_{10}(N_{\text{PRB}} \cdot 12)$ | +| 20, 25, 30, 40, 50, 60, 70, 80, 90, 100 | 30 | -4 | $-90.5 - 10 \cdot \text{Log}_{10}(N_{\text{PRB}} \cdot 12)$ | + +NOTE 1: $N_{\text{PRB}}$ is the number of PRBs within the IAB-MT channel bandwidth defined in section 5.3.2. + +**Table H.1.1.2-3: Conditions for RRC connection re-establishment for inter-frequency cell for Wide Area IAB-MT and IAB Type 1-O** + +| IAB-MT channel bandwidth (MHz) | SSB sub-carrier spacing (kHz) | Side conditions | | +|-----------------------------------------|-------------------------------|---------------------------------|------------------------------------------------------------------------------------------| +| | | SSB $\bar{E}_s/\text{lot}$ (dB) | Minimum SSB_RP (dBm) | +| 10, 15 | 30 | -4 | $-105 - 10 \cdot \text{Log}_{10}(N_{\text{PRB}} \cdot 12) - \Delta_{\text{OTAREFSENS}}$ | +| 20, 25, 30, 40, 50, 60, 70, 80, 90, 100 | 30 | -4 | $-99.4 - 10 \cdot \text{Log}_{10}(N_{\text{PRB}} \cdot 12) - \Delta_{\text{OTAREFSENS}}$ | + +NOTE 1: $N_{\text{PRB}}$ is the number of PRBs within the IAB-MT channel bandwidth defined in section 5.3.2. + +**Table H.1.1.2-4: Conditions for RRC connection re-establishment for inter-frequency cell for Local Area IAB-MT and IAB Type 1-O** + +| IAB-MT channel bandwidth (MHz) | SSB sub-carrier spacing (kHz) | Side conditions | | +|-----------------------------------------|-------------------------------|---------------------------------|------------------------------------------------------------------------------------------| +| | | SSB $\bar{E}_s/\text{lot}$ (dB) | Minimum SSB_RP (dBm) | +| 10, 15 | 30 | -4 | $-97 - 10 \cdot \text{Log}_{10}(N_{\text{PRB}} \cdot 12) - \Delta_{\text{OTAREFSENS}}$ | +| 20, 25, 30, 40, 50, 60, 70, 80, 90, 100 | 30 | -4 | $-90.5 - 10 \cdot \text{Log}_{10}(N_{\text{PRB}} \cdot 12) - \Delta_{\text{OTAREFSENS}}$ | + +NOTE 1: $N_{\text{PRB}}$ is the number of PRBs within the IAB-MT channel bandwidth defined in section 5.3.2. + +**Table H.1.1.2-5: Conditions for RRC connection re-establishment for inter-frequency cell for Local Area IAB-MT and IAB Type 2-O** + +| IAB-MT channel | SSB sub-carrier | Side conditions | +|----------------|-----------------|-----------------| +|----------------|-----------------|-----------------| + +| bandwidth (MHz) | spacing (kHz) | SSB Ês/lot (dB) | Minimum SSB_RP (dBm) | +|-----------------|---------------|-----------------|-----------------------------------------------------------------------------------------------| +| 50 | 120 | -4 | $EI_{SREFSENS\_50M} - 10 \cdot \text{Log}_{10}(N_{PRB} \cdot 12) + \Delta_{FR2\_REFSENS} - 3$ | +| 100, 200, 400 | 120 | -4 | $EI_{SREFSENS\_50M} - 10 \cdot \text{Log}_{10}(N_{PRB} \cdot 12) + \Delta_{FR2\_REFSENS}$ | + +NOTE 1: $N_{PRB}$ is the number of PRBs within the IAB-IMT channel bandwidth defined in section 5.3.2. +NOTE 2: $EI_{SREFSENS\_50M}$ for wide area IAB-MT and local area IAB-MT is defined in section 10.3.3.3. + +### H.1.1.3 Conditions for Measurements on NR Cells for RRC Connection Release with Redirection + +This clause defines the following conditions in terms of SSB\_RP and SSB Ês/lot for measurements on NR cells for RRC connection release with redirection: + +- The conditions are defined in Table H.1.1.3-1 for FR1 NR cells for Wide Area IAB-MT and IAB Type 1-H. +- The conditions are defined in Table H.1.1.3-2 for FR1 NR cells for Local Area IAB-MT and IAB Type 1-H. +- The conditions are defined in Table H.1.1.3-3 for FR1 NR cells for Wide Area IAB-MT and IAB Type 1-O. +- The conditions are defined in Table H.1.1.3-4 for FR1 NR cells for Local Area IAB-MT and IAB Type 1-O. +- The conditions are defined in Table H.1.1.3-5 for FR2-1 NR cells for Local Area and Wide Atea IAB-MT and IAB Type 2-O. + +**Table H.1.1.3-1: Conditions for RRC connection release with redirection for NR cell for Wide Area IAB-MT and IAB Type 1-H** + +| IAB-MT channel bandwidth (MHz) | SSB sub-carrier spacing (kHz) | Side conditions | | +|-----------------------------------------|-------------------------------|-----------------|------------------------------------------------------| +| | | SSB Ês/lot (dB) | Minimum SSB_RP (dBm) | +| 10, 15 | 30 | -4 | $-105 - 10 \cdot \text{Log}_{10}(N_{PRB} \cdot 12)$ | +| 20, 25, 30, 40, 50, 60, 70, 80, 90, 100 | 30 | -4 | $-99.4 - 10 \cdot \text{Log}_{10}(N_{PRB} \cdot 12)$ | + +NOTE 1: $N_{PRB}$ is the number of PRBs within the IAB-IMT channel bandwidth defined in section 5.3.2. + +**Table H.1.1.3-2: Conditions for RRC connection release with redirection for NR cell for Local Area IAB-MT and IAB Type 1-H** + +| IAB-MT channel bandwidth (MHz) | SSB sub-carrier spacing (kHz) | Side conditions | | +|-----------------------------------------|-------------------------------|-----------------|------------------------------------------------------| +| | | SSB Ês/lot (dB) | Minimum SSB_RP (dBm) | +| 10, 15 | 30 | -4 | $-97 - 10 \cdot \text{Log}_{10}(N_{PRB} \cdot 12)$ | +| 20, 25, 30, 40, 50, 60, 70, 80, 90, 100 | 30 | -4 | $-90.5 - 10 \cdot \text{Log}_{10}(N_{PRB} \cdot 12)$ | + +NOTE 1: $N_{PRB}$ is the number of PRBs within the IAB-IMT channel bandwidth defined in section 5.3.2. + +**Table H.1.1.3-3: Conditions for RRC connection release with redirection for NR cell for Wide Area IAB-MT and IAB Type 1-O** + +| IAB-MT channel bandwidth (MHz) | SSB sub-carrier spacing (kHz) | Side conditions | | +|-----------------------------------------|-------------------------------|-----------------|----------------------------------------------------------------------------| +| | | SSB Ês/lot (dB) | Minimum SSB_RP (dBm) | +| 10, 15 | 30 | -4 | $-105 - 10 \cdot \text{Log}_{10}(N_{PRB} \cdot 12) - \Delta_{OTAREFSENS}$ | +| 20, 25, 30, 40, 50, 60, 70, 80, 90, 100 | 30 | -4 | $-99.4 - 10 \cdot \text{Log}_{10}(N_{PRB} \cdot 12) - \Delta_{OTAREFSENS}$ | + +NOTE 1: $N_{PRB}$ is the number of PRBs within the IAB-IMT channel bandwidth defined in section 5.3.2. + +**Table H.1.1.3-4: Conditions for RRC connection release with redirection for NR cell for Local Area IAB-MT and IAB Type 1-O** + +| IAB-MT channel bandwidth (MHz) | SSB sub-carrier spacing (kHz) | Side conditions | | +|-----------------------------------------|-------------------------------|---------------------------------|------------------------------------------------------------------------------------------| +| | | SSB $\hat{E}_s/\text{lot}$ (dB) | Minimum SSB_RP (dBm) | +| 10, 15 | 30 | -4 | $-97 - 10 \cdot \text{Log}_{10}(N_{\text{PRB}} \cdot 12) - \Delta_{\text{OTAREFSENS}}$ | +| 20, 25, 30, 40, 50, 60, 70, 80, 90, 100 | 30 | -4 | $-90.5 - 10 \cdot \text{Log}_{10}(N_{\text{PRB}} \cdot 12) - \Delta_{\text{OTAREFSENS}}$ | + +NOTE 1: $N_{\text{PRB}}$ is the number of PRBs within the IAB-IMT channel bandwidth defined in section 5.3.2.**Table H.1.1.3-5: Conditions for RRC connection release with redirection for NR cell for Local Area IAB-MT and IAB Type 2-O** + +| IAB-MT channel bandwidth (MHz) | SSB sub-carrier spacing (kHz) | Side conditions | | +|--------------------------------|-------------------------------|---------------------------------|---------------------------------------------------------------------------------------------------------------------------| +| | | SSB $\hat{E}_s/\text{lot}$ (dB) | Minimum SSB_RP (dBm) | +| 50 | 120 | -4 | $\text{EIS}_{\text{REFSENS\_50M}} - 10 \cdot \text{Log}_{10}(N_{\text{PRB}} \cdot 12) + \Delta_{\text{FR2\_REFSENS}} - 3$ | +| 100, 200, 400 | 120 | -4 | $\text{EIS}_{\text{REFSENS\_50M}} - 10 \cdot \text{Log}_{10}(N_{\text{PRB}} \cdot 12) + \Delta_{\text{FR2\_REFSENS}}$ | + +NOTE 1: $N_{\text{PRB}}$ is the number of PRBs within the IAB-IMT channel bandwidth defined in section 5.3.2.NOTE 2: $\text{EIS}_{\text{REFSENS\_50M}}$ for wide area IAB-MT and local area IAB-MT is defined in section 10.3.3.3. + +## Annex I (normative): Propagation conditions + +### I.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. + +#### I.1.1 IAB-MT receiver with 2RX + +For 1 port transmission the channel matrix is defined in the frequency domain by: + +$$\mathbf{H} = \begin{bmatrix} 1 \\ 1 \end{bmatrix}$$ + +For 2 port transmission the channel matrix is defined in the frequency domain by: + +$$\mathbf{H} = \begin{bmatrix} 1 & j \\ 1 & -j \end{bmatrix}$$ + +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}$$ + +## I.2 Multi-path fading propagation conditions + +### I.2.1 General + +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-1 (24.25 GHz – 52.6 GHz). + +### I.2.2 Delay profiles + +#### I.2.2.1 General + +The delay profiles are simplified from the TR 38.901 [27] 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 I.2.2.1 can be used as such. + +- Step 1: Use the original TDL model from TR 38.901 [27]. +- 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 [27]. +- 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 $\rightarrow$ 15 ns, 10 ns & 25 ns $\rightarrow$ 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 $\rightarrow$ -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 I.2.2.2-2, I.2.2.2-3, and I.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. + +## I.2.2.2 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 I.2.2.2-1 and the tapped delay line models are specified in tables I.2.2.2-2 ~ table I.2.2.2-4. + +**Table I.2.2.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 | +| TDLB100 | 12 | 100 ns | 480 ns | 5 ns | +| TDLC300 | 12 | 300 ns | 2595 ns | 5 ns | + +**Table I.2.2.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 | | + +**Table I.2.2.2-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 I.2.2.2-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 | | + +## I.2.3 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 I.2.3-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 I.2.3-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 | + +## I.2.4 MIMO channel correlation matrices + +### I.2.4.1 General + +The MIMO channel correlation matrices defined in annex I.2.4 apply for the antenna configuration using uniform linear arrays at both IAB-DU/gNB and IAB-MT/UE and for the antenna configuration using cross polarized antennas. + +### I.2.4.2 MIMO correlation matrices using Uniform Linear Array + +#### I.2.4.2.1 General + +The MIMO channel correlation matrices defined in annex I.2.4.2 apply for the antenna configuration using uniform linear array (ULA) at both IAB-DU/gNB and IAB-MT/UE. + +#### I.2.4.2.2 Definition of MIMO correlation matrices + +Table I.2.4.2.2-1 defines the correlation matrix for the IAB-DU or gNB. + +**Table I.2.4.2.2-1: IAB-DU or gNB correlation matrix** + +| IAB-DU or 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}$ | + +NOTE: The matrix applies to the IAB-DU for IAB-DU requirements and gNB for IAB-MT requirements. + +Table I.2.4.2.2-2 defines the correlation matrix for the IAB-MT or UE: + +**Table I.2.4.2.2-2: IAB-MT or UE correlation matrix** + +| | One antenna | Two antennas | Four antennas | +|-------------------------|--------------|-------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IAB-MT / 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}$ | + +NOTE: The matrix applies to the UE for IAB-DU requirements and IAB-MT for IAB-MT requirements. + +Table I.2.4.2.2-3 defines the channel spatial correlation matrix $R_{spat}$ . The parameters, $\alpha$ and $\beta$ in table I.2.4.2.2-3 defines the spatial correlation between the antennas at the IAB-DU/gNB and IAB-MT/UE respectively. + +**Table I.2.4.2.2-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}$ | +| NOTE 1: $R_{gNB}$ refers to an IAB-DU for IAB-DU requirements or a gNB for IAB-MT requirements.
NOTE 2: $R_{UE}$ refers to an UE for IAB-DU requirements or and IAB-MT for IAB-MT requirements | | + +For cases with more antennas at either IAB-DU/gNB or IAB-MT/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}$ . + +**I.2.4.2.3 MIMO correlation matrices at high, medium and low level** + +The $\alpha$ and $\beta$ for different correlation types are given in table I.2.4.2.3-1. + +**Table I.2.4.2.3-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 I.2.4.2.3-2, I.2.4.2.3-3 and I.2.4.2.3-4 as below. + +The values in table I.2.4.2.3-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 I.2.4.2.3-3 to insure the correlation matrix is positive semi-definite after round-off to 4 digit precision with a = 0.00012. + +**Table I.2.4.2.3-2: MIMO correlation matrices for high correlation** + +| | | +|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1x2 case | | +| 2x2 case | $R_{high} = \begin{pmatrix} 1 & 0.9 \\ 0.9 & 1 \end{pmatrix}$ $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 I.2.4.2.3-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 I.2.4.2.3-4: MIMO correlation matrices for low correlation** + +| | | +|----------|--| +| 1x2 case | | +| 1x4 case | | +| 1x8 case | | +| 2x2 case | | +| 2x4 case | | +| 2x4 case | | +| 4x4 case | | + +In table I.2.4.12.3-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. + +### I.2.4.3 Multi-antenna channel models using cross polarized antennas + +#### I.2.4.3.1 General + +The MIMO channel correlation matrices defined in annex I.2.4.3 apply to two cases as presented below: + +- One TX antenna and multiple RX antennas case, with cross polarized antennas used at IAB-DU/gNB +- Multiple TX antennas and multiple RX antennas case, with cross polarized antennas used at IAB-MT/UE + +The cross-polarized antenna elements with +/-45 degrees polarization slant angles are deployed at IAB. For one TX antenna case, antenna element with +90 degree polarization slant angle is deployed at IAB-MT/UE. For multiple TX antennas case, cross-polarized antenna elements with +90/0 degrees polarization slant angles are deployed at IAB-MT/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. + +#### I.2.4.3.2 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 (IAB-DU requirements) or IAB-MT (IAB-MT requirements) with same polarization, +- $R_{gNB}$ is the spatial correlation matrix at the IAB-DU (IAB-DU requirements) or gNB (IAB-MT requirements) with same polarization, +- $\Gamma_{UL}$ is a polarization correlation matrix, +- $P_{UL}$ is a permutation matrix, and +- $(\cdot)^T$ denotes transpose. + +Table I.2.4.3.2-1 defines the polarization correlation matrix. + +**Table I.2.4.3.2-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 + +$$\mathbf{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 I.2.4.3. + +**I.2.4.3.3 Spatial correlation matrices at IAB-MT/UE and IAB-DU/gNB sides** + +**I.2.4.3.3.1 Spatial correlation matrices at IAB-MT/UE side** + +In this subclause, $R_{UE}$ refers to a UE for IAB-DU requirements or an IAB-MT for IAB-MT requirements. + +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{bmatrix} 1 & \beta \\ \beta^* & 1 \end{bmatrix}$$ + +For 4-antenna transmitter using two pairs of cross-polarized antenna elements, + +**I.2.4.3.3.2 Spatial correlation matrices at IAB-DU/gNB side** + +In this subclause, $R_{gNB}$ refers to an IAB-DU for IAB-DU requirements or a gNB for IAB-MT requirements. + +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{bmatrix} 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{bmatrix}$$ + +For 8-antenna receiver using four pairs of cross-polarized antenna elements, + +**I.2.4.3.4 MIMO correlation matrices using cross polarized antennas** + +The values for parameters $\alpha$ , $\beta$ and $\gamma$ for low spatial correlation are given in table I.2.4.3.4-1. + +**Table I.2.4.3.4-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 IAB-DU/gNB side.
NOTE 2: Value of $\beta$ applies when more than one pair of cross-polarized antenna elements at IAB-MT/UE side. | | | + +The correlation matrices for low spatial correlation are defined in table I.2.4.3.4-2 as below. + +**Table I.2.4.3.4-2: MIMO correlation matrices for low spatial correlation** + +| | | +|----------|-----------------------------| +| 1x8 case | $R_{low} = \mathbf{I}_8$ | +| 2x8 case | $R_{low} = \mathbf{I}_{16}$ | + +In table I.2.4.3.4-2, $\mathbf{I}_d$ is a $d \times d$ identity matrix. + +### I.2.4.3.5 Beam steering approach + +For the 2D cross-polarized antenna array at gNB, given the channel spatial correlation matrix in I.2.4.3.2, I.2.4.3.3 and I.2.4.3.4, 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_{t1}$ is the number of antenna elements in first dimension with same polarization, +- $N_{t2}$ 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 1 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 I.2.4.3.5-1, and k is the linear increment of 2# 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 I.2.4.3.5-1: The step of phase variation** + +| Variation Step | Value (rad/ms) | +|----------------|-------------------------| +| | $1.2566 \times 10^{-3}$ | + +## I.3 Physical signals, channels mapping and precoding + +### I.3.1 General + +Unless otherwise stated, the transmission on antenna port(s) is defined by using a precoder matrix of size , where is the number of physical transmit antenna elements configured per test , is the number of ports for a reference signal or physical channel configured per test, and is the first port for that reference signal or physical channel as defined in clauses 7.3 and 7.4 in TS 38.211 [8]. This precoder takes as an input a block of signals for antenna port(s) , , with being the number of modulation symbols per antenna port including the reference signal symbols, and generates a block of signals 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: + +For Clause 8.2.3 and 11.2.3, the transmission of PDCCH and PDCCH DMRS on antenna port is defined by using a precoder matrix of size 2x1. This precoder takes as an input a block of signals for antenna port(s) , and generates a block of signals 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: + +The precoder matrix is specific to the test case configuration. is defined in Clause 5.2.2.2 of TS 38.214 [11]. + +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 with (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 are mapped to the physical antenna index where is the number of NZP CSI-RS ports configured per test. + + + +--- + +## Annex J (informative): Change history + +| Change history | | | | | | | | +|----------------|-----------|------------|------|-----|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 09/2019 | RAN4#92 | R4-1910404 | | | | Initial TS skeleton | 0.0.1 | +| 06/2020 | RAN4#95-e | R4-2007467 | | | | Update of IAB TS with agreed TP in RAN4#95-e:
R4-2007991 TP to TS 38.174 v0.0.1: Adding references related to IAB
R4-2008769 TP to TS 38.174: system parameter
R4-2006275 TP to TS 38.174: IAB-DU Transmitted signal quality
R4-2008778 TP to TS 38.174: Transmit ON/OFF power
R4-2008788 TP to TS 38.174: IAB RX IM requirement (section 7.7 and 10.8)
R4-2008791 TP to TS 38.174: IAB ICS requirement (section 7.8 and 10.9)
R4-2008795 TP to TS 38.174: OTA ACS
R4-2008796 TP to TS 38.174: OTA RX spurious
R4-2008798 TP to TS 38.174: OTA Inband blocking
R4-2008799 TP to TS 38.174: Conducted RX spurious
R4-2008800 TP to TS 38.174 -IAB-DU RX sensitivity
R4-2008801 TP to TS 38.174 -IAB-DU Rx dynamic range
R4-2009063 TP to TS 38.174 -IAB-DU TX dynamic range
R4-2008596 TP to 38174 RRM IAB TS
R4-2008597 TP to TS 38.174 v0.0.1: Updates to RRC re-establishment requirements for IAB MT
R4-2008598 TP to TS 38.174 v0.0.1: Updates to RRC re-direction requirements for IAB MT
R4-2008599 TP to TS 38174 Transmit Timing requirements for IAB-MT
R4-2008600 TP for IAB RLM
R4-2008601 TP to TS 38.174 v0.0.1: Beam Candidate Detection Requirements for IAB MT
R4-2008611 TP to TS 38.174 on BFD requirements of IAB-MTs | 0.1.0 | +| 09/2020 | Ran4#96-e | R4-2012566 | | | | Update of IAB TS with agreed TPs in RAN4#96-e
R4-2012108: Removing editor's notes and replacing TBD with appropriate numbers
R4-2012234: RLM requirements for IAB MTs
R4-2012614: IAB-MT classes, applicability of requirements, requirements for contiguous and non-contiguous spectrum
R4-2012618: Output power dynamics, Radiated transmit power, OTA output power
R4-2012620: IAB Output power, Radiated transmit power
R4-2012621: Output power dynamics, OTA output power dynamics
R4-2012622: Appendices, frequency error, modulation quality, OTA frequency error, OTA modulation quality
R4-2012624: Unwanted emissions, OTA unwanted emissions
R4-2012626: Transmitter intermodulation, OTA transmitter intermodulation
R4-2012628: Reference sensitivity level, dynamic range, OTA sensitivity, OTA dynamic range, fixed reference channels for reference sensitivity
R4-2012631: In-band selectivity and blocking, out-of-band blocking, OTA out-of-band blocking
R4-2012633: Receiver intermodulation, OTA receiver intermodulation
R4-2012760: IAB-MT receiver spurious emissions, OTA IAB-MT receiver spurious emissions | 0.2.0 | +| 2020-09 | RAN#89 | RP-01909 | | | | Draft version for information purposes to the RAN Plenary | 1.0.0 | +| 2020-09 | RAN#89 | RP-01979 | | | | Minor editorial corrections | 1.0.1 | +| 2020-09 | RAN#89 | RP-01979 | | | | Approved by plenary – Rel-16 spec under change control | 16.0.0 | +| 2020-12 | RAN#90 | RP-202504 | 0006 | | F | Correction CR on TS38.174 | 16.1.0 | +| 2021-03 | RAN#91 | RP-210170 | 0011 | | F | Big CR to TR 38.174 – correction to clause 6 | 16.2.0 | +| 2021-06 | RAN#92 | RP-211101 | 0015 | | F | CR on maintenance on sharing factor of RLM and link recovery for IAB-MT | 16.3.0 | +| 2021-06 | RAN#92 | RP-211101 | 0016 | 1 | B | Big CR on IAB-MT demodulation in TS 38.174 | 16.3.0 | +| 2021-06 | RAN#92 | RP-211101 | 0018 | 1 | B | Big CR: IAB-MT RRM test cases in 38.174 | 16.3.0 | +| 2021-06 | RAN#92 | RP-211101 | 0020 | | F | Big CR for update Core part of TS 38.174 | 16.3.0 | +| 2021-09 | RAN#93 | RP-211892 | 0021 | | F | Big CR for TS 38.174 Maintenance (Rel-16, CAT F) | 16.4.0 | +| 2021-12 | RAN#94 | RP-212851 | 0022 | | F | Big CR for TS 38.174 Maintenance (Rel-16, CAT F) | 16.5.0 | +| 2022-03 | RAN#95 | RP-220374 | 0024 | | B | Big CR to TS38.174 for Rel-17 IAB enhancement | 17.0.0 | +| 2022-03 | RAN#95 | RP-220334 | 0026 | | F | Big CR for TS 38.174 Maintenance (Rel-16, CAT F) | 16.6.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 | 0027 | | B | Introducing 6GHz licensed operation into 38.174 | 17.1.0 | +| 2022-06 | RAN#96 | RP-221665 | 0033 | 1 | F | Big CR for TS 38.174 Maintenance (Rel-17, CAT F) | 17.1.0 | +| 2022-06 | RAN#96 | RP-221665 | 0035 | | A | Big CR on TS 38.174 Maintenance (Rel-17) | 17.1.0 | +| 2022-12 | RAN#98-e | RP-223310 | 0038 | 1 | F | CR on case-6 timing for eIAB_RF | 17.2.0 | +| 2023-03 | RAN#99 | RP-230515 | 0042 | | F | Correction to IAB-MT timing reference point in TS 38.174 | 17.3.0 | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|----------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2023-03 | RAN#99 | RP-230533 | 0041 | | B | CR to TS 38.174: Addition of band n105 | 18.0.0 | +| 2023-03 | RAN#99 | RP-230535 | 0040 | 1 | B | CR to 38.174 on introduction of Band n54 | 18.0.0 | +| 2023-06 | RAN#100 | RP-231353 | 0045 | | A | CR for TS 38.174, Correction on OTA IAB output power etc. | 18.1.0 | +| 2023-06 | RAN#100 | RP-231353 | 0048 | | A | CR on maintenance for IAB R18 | 18.1.0 | +| 2023-06 | RAN#100 | RP-231353 | 0051 | | A | Clean up for IAB demodulation requirements in TS 38.174 (Rel-18) | 18.1.0 | +| 2023-06 | RAN#100 | RP-231353 | 0053 | | A | CR to TS 38.174 Maintenance of IAB for supported BW R18 | 18.1.0 | +| 2023-09 | RAN#101 | RP-232491 | 0056 | | A | [NR_IAB_enh-Core] CR to TS 38.174: Addition of missing bands for IAB co-existence and co-location requirements | 18.2.0 | +| 2023-09 | RAN#101 | RP-232491 | 0059 | | A | CR for TS 38.174, Correction on scaling factor for IAB-MT type 1-O | 18.2.0 | +| 2023-09 | RAN#101 | RP-232491 | 0062 | | A | [NR_IAB-Core] CR on maintenance of RRM requirements for IAB R18 | 18.2.0 | +| 2023-09 | RAN#101 | RP-232491 | 0067 | | A | CR to correct FR2 range in IAB specification | 18.2.0 | +| 2023-09 | RAN#101 | RP-232491 | 0069 | | A | Correction to applicable FR2 range for IAB-MT RRM core requirements | 18.2.0 | +| 2023-09 | RAN#101 | RP-232491 | 0072 | | A | [NR_IAB-Perf] CR on NR IAB performance requirements (TS38.174, Rel-18) | 18.2.0 | +| 2023-12 | RAN#102 | RP-233366 | 0074 | | B | CR to TS38.174: introduction of NR bands n31 and n72 | 18.3.0 | +| 2023-12 | RAN#102 | RP-233366 | 0075 | | B | CR to TS38.174: introduction of band n106 | 18.3.0 | +| 2023-12 | RAN#102 | RP-233373 | 0077 | | B | Big CR to TS 38.174 on RF core requirements for NR Mobile IAB | 18.3.0 | +| 2023-12 | RAN#102 | RP-233347 | 0079 | | F | CR to TS 38.174 with correction of co-existence and co-location requirements | 18.3.0 | +| 2023-12 | RAN#102 | RP-233366 | 0084 | | B | CR to 38.174 on introduction of Band n109 | 18.3.0 | +| 2023-12 | RAN#102 | RP-233347 | 0087 | | A | CR to update FR2 range in IAB specification | 18.3.0 | +| 2023-12 | RAN#102 | RP-233347 | 0092 | | A | [NR_IAB_enh] Correction to IAB-MT TA adjustment accuracy requirements | 18.3.0 | +| 2023-12 | RAN#102 | RP-233347 | 0094 | | A | [NR_IAB_enh] Correction to applicable FR2 range in IAB-MT RRM performance requirements | 18.3.0 | +| 2023-12 | RAN#102 | RP-233373 | 0095 | | B | Big CR to TS 38.174 on RRM core requirements for NR Mobile IAB | 18.3.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38175/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-18/38_series/38175/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21c4528a47393f07ab3178ed3eb3f26b5f2d5abd --- /dev/null +++ b/marked/Rel-18/38_series/38175/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:798eb1b8ddf827ee0aeb7a4004f71a849e22e88198986cbc356654ec63b9d037 +size 27925 diff --git a/marked/Rel-18/38_series/38175/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38175/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c12a83ba872a7983a6d0b8d53336d62852b98811 --- /dev/null +++ b/marked/Rel-18/38_series/38175/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b670e9caf3b1e6ca508c2c08aeeacc3c5090c045ac1241c8d7c62ec56a078b40 +size 9408 diff --git a/marked/Rel-18/38_series/38175/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38175/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6641cd6f75926b154cabba70eb5852a42fd3a12d --- /dev/null +++ b/marked/Rel-18/38_series/38175/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a22388208a3abcda452ceb579b616870c8e47599685ef195bbc1e66a5106c3cd +size 5215 diff --git a/marked/Rel-18/38_series/38175/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-18/38_series/38175/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7f8fe69077171c12bfce57a0656300081c2a2b58 --- /dev/null +++ b/marked/Rel-18/38_series/38175/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:80016881d5733aacd61307f6b92c67f035a2a39183f5b4ebfd47e3d3ab4461d8 +size 56985 diff --git a/marked/Rel-18/38_series/38175/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-18/38_series/38175/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..96c8d9ae2fd80b9fbdf8be4c0727acb2de26b3aa --- /dev/null +++ b/marked/Rel-18/38_series/38175/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b04b85eab21788839112523ae4afc6fa3a929720fea130b6768018197c2994f +size 24943 diff --git a/marked/Rel-18/38_series/38175/dbe553cf16dd14073b89a8263a428664_img.jpg b/marked/Rel-18/38_series/38175/dbe553cf16dd14073b89a8263a428664_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f38b32d8f4e98db6844df4d68da2e640a705a24 --- /dev/null +++ b/marked/Rel-18/38_series/38175/dbe553cf16dd14073b89a8263a428664_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:730d89a56c739fe6b8aa6648d7ca54321856ad5be88a0df5294ac49f9d605559 +size 22101 diff --git a/marked/Rel-18/38_series/38175/raw.md b/marked/Rel-18/38_series/38175/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..17d9fc0900dec57e04003ba6c98ddfbace678d8b --- /dev/null +++ b/marked/Rel-18/38_series/38175/raw.md @@ -0,0 +1,1119 @@ + + +# 3GPP TS 38.175 V18.1.0 (2024-06) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Integrated access and backhaul ElectroMagnetic Compatibility (EMC) (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller text to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles – Sophia Antipolis +Valbonne – FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|--------------------------------------------------------------------------------|----| +| Foreword ..... | 7 | +| 1 Scope..... | 8 | +| 2 References..... | 8 | +| 3 Definitions, symbols and abbreviations ..... | 10 | +| 3.1 Definitions..... | 10 | +| 3.2 Symbols..... | 11 | +| 3.3 Abbreviations ..... | 12 | +| 4 Test conditions ..... | 12 | +| 4.1 General ..... | 12 | +| 4.2 Arrangements for establishing a communication link..... | 13 | +| 4.3 Narrow band responses on receivers..... | 13 | +| 4.4 Exclusion bands..... | 14 | +| 4.4.1 Transmitter exclusion band ..... | 14 | +| 4.4.2 Receiver exclusion band..... | 14 | +| 4.5 IAB test configurations ..... | 15 | +| 5 Performance assessment ..... | 16 | +| 5.1 General ..... | 16 | +| 5.2 Assessment of throughput of IAB-DU..... | 16 | +| 5.3 Assessment of throughput of IAB-MT..... | 16 | +| 5.4 Ancillary equipment..... | 17 | +| 6 Performance criteria..... | 17 | +| 6.1 Performance criteria for continuous phenomena for IAB..... | 17 | +| 6.2 Performance criteria for transient phenomena for IAB..... | 18 | +| 6.3 Performance criteria for continuous phenomena for Ancillary equipment..... | 18 | +| 6.4 Performance criteria for transient phenomena for Ancillary equipment..... | 18 | +| 7 Applicability overview..... | 18 | +| 7.0 General ..... | 18 | +| 7.1 Emission..... | 19 | +| 7.2 Immunity ..... | 19 | +| 8 Emission..... | 20 | +| 8.1 Test configurations..... | 20 | +| 8.2 Radiated emission ..... | 20 | +| 8.2.1 Radiated emission, IAB..... | 20 | +| 8.2.1.1 Definition ..... | 20 | +| 8.2.1.2 Test method..... | 20 | +| 8.2.1.3 Limits ..... | 21 | +| 8.2.1.4 Interpretation of the measurement results..... | 22 | +| 8.2.2 Radiated emission, ancillary equipment..... | 23 | +| 8.2.2.1 Definition ..... | 23 | +| 8.2.2.2 Test method..... | 23 | +| 8.2.2.3 Limits ..... | 23 | +| 8.3 Conducted emission DC power input/output port..... | 23 | +| 8.3.1 Definition..... | 23 | +| 8.3.2 Test method ..... | 23 | +| 8.3.3 Limits..... | 24 | +| 8.4 Conducted emissions, AC mains power input/output port..... | 24 | +| 8.4.1 Definition..... | 24 | +| 8.4.2 Test method ..... | 24 | +| 8.4.3 Limits..... | 24 | +| 8.5 Conducted emissions, telecommunication port..... | 24 | +| 8.5.1 Definition..... | 24 | +| 8.5.2 Test method ..... | 25 | + +| | | | +|---------------------------------------------------|------------------------------------------------------------------------------------|-----------| +| 8.5.3 | Limits..... | 25 | +| 8.6 | Harmonic Current emissions (AC mains input port) ..... | 25 | +| 8.7 | Voltage fluctuations and flicker (AC mains input port)..... | 25 | +| 9 | Immunity..... | 25 | +| 9.1 | Test configurations..... | 25 | +| 9.2 | RF electromagnetic field (80 MHz – 6000 MHz)..... | 26 | +| 9.2.1 | Definition..... | 26 | +| 9.2.2 | Test method and level..... | 26 | +| 9.2.3 | Performance criteria ..... | 28 | +| 9.3 | Electrostatic discharge..... | 28 | +| 9.3.1 | Definition..... | 28 | +| 9.3.2 | Test method and level..... | 29 | +| 9.3.3 | Performance criteria ..... | 29 | +| 9.4 | Fast transients common mode..... | 29 | +| 9.4.1 | Definition..... | 29 | +| 9.4.2 | Test method and level..... | 29 | +| 9.4.3 | Performance criteria ..... | 29 | +| 9.5 | RF common mode (0.15 MHz – 80 MHz)..... | 30 | +| 9.5.1 | Definition..... | 30 | +| 9.5.2 | Test method and level..... | 30 | +| 9.5.3 | Performance criteria ..... | 30 | +| 9.6 | Voltage dips and interruptions ..... | 30 | +| 9.6.1 | Definition..... | 31 | +| 9.6.2 | Test method and level..... | 31 | +| 9.6.3 | Performance criteria ..... | 31 | +| 9.7 | Surges, common and differential mode..... | 31 | +| 9.7.1 | Definition..... | 31 | +| 9.7.2 | Test method and level..... | 31 | +| 9.7.2.1 | Test method for telecommunication ports directly connected to outdoor cables ..... | 32 | +| 9.7.2.2 | Test method for telecommunication ports connected to indoor cables..... | 32 | +| 9.7.2.3 | Test method for AC power ports ..... | 32 | +| 9.7.3 | Performance criteria ..... | 32 | +| Annex A (informative): Change history..... | | 32 | + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- Y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions “shall” and “shall not” are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions “must” and “must not” are not used as substitutes for “shall” and “shall not”. Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- Should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction “may not” is ambiguous and is not used in normative elements. The unambiguous constructions “might not” or “shall not” are used instead, depending upon the meaning intended. + +- Can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions “can” and “cannot” are not substitutes for “may” and “need not”. + +- Will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions “is” and “is not” do not indicate requirements. + +# --- 1 Scope + +The present document covers the assessment for NR Integrated access and backhaul (IAB) node and associated ancillary equipment in respect of Electromagnetic Compatibility (EMC). + +The present document specifies the applicable test conditions, performance assessment and performance criteria for NR Integrated access and backhaul (IAB) node and associated ancillary equipment. + +Technical requirements related to the antenna and TAB connectors are not included in the present document. These are found in the relevant product standards [2, 24, 25]. + +The environment classification used in the present document refers to the residential, commercial and light industrial environment classification used in IEC 61000-6-1 [4], IEC 61000-6-3 [5] and IEC 61000-6-8 [26]. + +The EMC requirements have been selected to ensure an adequate level of compatibility for apparatus at residential, commercial and light industrial environments. The levels, however, do not cover extreme cases which may occur in any location but with low probability of occurrence. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: “Vocabulary for 3GPP Specifications” +- [2] 3GPP TS 38.174: “NR; Integrated access and backhaul radio transmission and reception”. +- [3] 3GPP TR 38.809: “NR; Background for Integrated access and backhaul radio transmission and reception”. +- [4] IEC 61000-6-1: “Electromagnetic compatibility (EMC) – Part 6-1: Generic standards – Immunity for residential, commercial and light-industrial environments”. +- [5] IEC 61000-6-3: “Electromagnetic compatibility (EMC) – Part 6-3: Generic standards – Emission standard for equipment in residential environments”. +- [6] CISPR 32: “Electromagnetic compatibility of multimedia equipment – Emission requirements”. +- [7] IEC 60050-161: “International Electrotechnical Vocabulary (IEV) – Part 161: Electromagnetic compatibility”. + +- [8] IEC 61000-3-2: "Electromagnetic compatibility (EMC) – Part 3-2: Limits – Limits for harmonic current emissions (equipment input current $\leq 16$ A per phase)". +- [9] IEC 61000-3-12: "Electromagnetic compatibility (EMC) – Part 3-12: Limits – Limits for harmonic currents produced by equipment connected to public low-voltage system with input current $>16$ A and $\leq 75$ A per phase". +- [10] IEC 61000-3-3: "Electromagnetic compatibility (EMC) – Part 3-3: Limits – Limitation of voltage changes, voltage fluctuations and flicker in low-voltage supply systems, for equipment with rated current $\leq 16$ A per phase and not subject to conditional connection". +- [11] IEC 61000-3-11: "Electromagnetic compatibility (EMC) – Part 3-11: Limits – Limitation of voltage changes, voltage fluctuations and flicker in low-voltage supply systems - Equipment with rated current $\leq 75$ A and subject to conditional connections". +- [12] IEC 61000-4-2: "Electromagnetic compatibility (EMC) – Part 4-2: Testing and measurement techniques – Electrostatic discharge immunity test". +- [13] IEC 61000-4-3: "Electromagnetic compatibility (EMC) – Part 4-3: Testing and measurement techniques – Radiated, radio-frequency, electromagnetic field immunity test". +- [14] IEC 61000-4-4: "Electromagnetic compatibility (EMC) – Part 4-4: Testing and measurement techniques – Electrical fast transient/burst immunity test". +- [15] IEC 61000-4-5: "Electromagnetic compatibility (EMC) – Part 4-5: Testing and measurement techniques – Surge immunity test". +- [16] IEC 61000-4-6: "Electromagnetic compatibility (EMC) – Part 4-6: Testing and measurement techniques – Immunity to conducted disturbances, induced by radio frequency fields". +- [17] IEC 61000-4-11: "Electromagnetic compatibility (EMC) – Part 4-11: Testing and measurement techniques – Voltage dips, short interruptions and voltage variations immunity tests". +- [18] IEC 61000-4-21: "Electromagnetic compatibility (EMC) – Part 4-21: Testing and measurement techniques – Reverberation chamber test methods". +- [19] ETSI EN 301 489-1: "ElectroMagnetic Compatibility (EMC) standard for radio equipment and services; Part 1: Common technical requirements; Harmonised Standard covering the essential requirements of article 3.1(b) of Directive 2014/53/EU and the essential requirements of article 6 of Directive 2014/30/EU". +- [20] Recommendation ITU-R SM.329: "Unwanted emissions in the spurious domain". +- [21] Recommendation ITU-R SM.1539: "Variation of the boundary between the out-of-band and spurious domains required for the application of Recommendations ITU-R SM.1541 and ITU-R SM.329". +- [22] 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception". +- [23] CISPR 16-1-4: 2019-01: "Specification for radio disturbance and immunity measuring apparatus and methods – Part 1-4: Radio disturbance and immunity measuring apparatus – Antennas and test sites for radiated disturbance measurements". +- [24] 3GPP TS 38.176-1: "NR; Integrated access and backhaul (IAB) conformance testing; Part 1: Conducted conformance testing". +- [25] 3GPP TS 38.176-2: "NR; Integrated Access and Backhaul (IAB) conformance testing; Part 2: Radiated conformance testing; ". +- [26] IEC 61000-6-8: "Electromagnetic compatibility (EMC) – Part 6-8: Generic standards – Emission standard for professional equipment in commercial and light-industrial locations". +- [27] 3GPP TS 38.300: "NR; NR and NG-RAN Overall description; Stage-2". + +# 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] 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]. + +**Channel bandwidth:** the RF bandwidth supporting a single NR RF carrier with the transmission bandwidth configured in the uplink or downlink of a cell. The *channel bandwidth* is measured in MHz and is used as a reference for transmitter and receiver RF requirements. + +**Continuous phenomena:** electromagnetic disturbance, the effects of which on a particular device or equipment cannot be resolved into a succession of distinct effects (IEC 60050-161 [7]). + +**Enclosure port:** physical boundary of the equipment through which electromagnetic fields may radiate or impinge. + +NOTE: In the case of *integral antenna* equipment, this port is inseparable from the antenna port. + +**Exclusion band:** frequency range(s) not subject to test or assessment. + +**IAB-node:** RAN node that supports wireless access to UEs and wirelessly backhauls the access traffic. + +**IAB type 1-H:** IAB-MT and IAB-DU operating at FR1 with a requirement set holding requirements defined at the respective TAB and OTA requirements defined at the respective RIB + +**IAB type 1-O:** IAB-MT and IAB-DU operating at FR1 with a requirement set consisting only of OTA requirements defined at the respective RIB. + +**IAB type 2-O:** IAB-MT and IAB-DU operating at FR2 with a requirement set consisting only of OTA requirements defined at the respective RIB + +**integral antenna:** antenna designed for permanent connection to the equipment and considered part of the enclosure port. + +NOTE: An *integral antenna* may be fitted internally or externally. + +**Mobile IAB-node:** Mobile IAB-node as defined in TS 38.300 [27] + +**Mobile IAB-DU:** IAB-DU function on the mobile IAB-node as defined in TS 38.300 [27] + +**Mobile IAB-MT:** IAB-MT function on the mobile IAB-node as defined in TS 38.300 [27] + +**Mobile IAB type 1-H:** Mobile IAB-MT operating at FR1 with a *requirement set* consisting of conducted requirements defined at individual *TAB connectors* and OTA requirements defined at RIB + +**Mobile IAB-MT type 1-O:** Mobile IAB-MT operating at FR1 with a *requirement set* consisting only of OTA requirements defined at the RIB + +**Mobile IAB-MT type 2-O:** Mobile IAB-MT operating at FR2 with a *requirement set* consisting only of OTA requirements defined at the RIB + +**Operating band:** frequency range in which NR operates (paired or unpaired), that is defined with a specific set of technical requirements. + +**Port:** particular interface of EUT used for EMC requirements testing purposes. + +NOTE: Any connection point on EUT intended for connection of cables to or from EUT during the EMC testing is considered as a port. + +EXAMPLE 1: Examples of ports for *IAB type 1-H* are as presented in figure 3.1-1: + +![Diagram of IAB type 1-H apparatus ports](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +A diagram showing an 'Apparatus' represented by a rectangle inside a larger 'Enclosure' rectangle. On the left side of the enclosure, there are three ports: 'AC power port', 'DC power port', and 'Earth port'. On the right side, there are three ports: 'Antenna port', 'Signal/control port', and 'Telecommunication port'. The 'Enclosure Port' label is positioned above the enclosure rectangle. + +Diagram of IAB type 1-H apparatus ports + +**Figure 3.1-1: Examples of ports for IAB type 1-H** + +EXAMPLE 2: Examples of ports for *IAB type 1-O* and *IAB type 2-O* (i.e. with no *antenna ports*) are as presented in figure 3.1-2: + +![Diagram of IAB type 1-O and 2-O apparatus ports](dbe553cf16dd14073b89a8263a428664_img.jpg) + +A diagram showing an 'Apparatus' represented by a rectangle inside a larger 'Enclosure' rectangle. On the left side of the enclosure, there are three ports: 'AC power port', 'DC power port', and 'Earth port'. On the right side, there are two ports: 'Signal/control port' and 'Telecommunication port'. The 'Enclosure' label is positioned above the enclosure rectangle. This diagram is similar to Figure 3.1-1 but lacks the 'Antenna port'. + +Diagram of IAB type 1-O and 2-O apparatus ports + +**Figure 3.1-2: Examples of ports for IAB type 1-O and IAB type 2-O** + +**receiver exclusion band:** band of frequencies over which no tests of radiated immunity of a receiver are made, and expressed relative to the IAB receive band. + +**Signal port:** port intended for the interconnection of components of an EUT, or between an EUT and associated equipment and used in accordance with relevant functional specifications (for example for the maximum length of cable connected to it). + +**Spatial exclusion zone:** range of angles where no tests of radiated immunity are made for *IAB type 1-O* or *IAB type 2-O* (i.e. half sphere around the EUT’s radiating direction). + +**Throughput:** number of payload bits successfully received per second for a reference measurement channel in a specified reference condition. + +**Telecommunication port:** ports which are intended to be connected to telecommunication networks (e.g. public switched telecommunication networks, integrated services digital networks), local area networks (e.g. Ethernet, Token Ring) and similar networks. + +NOTE: *Telecommunication port* is called “wired network port” in CISPR 32 [6] and ETSI EN 301 489-1 [19]. + +**Transient phenomena:** pertaining to or designating a phenomena or a quantity which varies between two consecutive steady states during a time interval short compared with the time-scale of interest (IEC 60050-161 [7]). + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|--------------------------|------------------------------------------------------------------------------------------------------------------| +| $BW_{\text{Channel}}$ | Channel bandwidth | +| $\Delta f_{\text{OBUE}}$ | Maximum offset of the operating band unwanted emissions mask from the downlink operating band edge | +| $F_{\text{DL,low}}$ | The lowest frequency of the downlink operating band | + +| | | +|----------------------|-------------------------------------------------------------| +| F DL,high | The highest frequency of the downlink operating band | +| F UL,low | The lowest frequency of the uplink operating band | +| F UL,high | The highest frequency of the uplink operating band | + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|----------|-------------------------------------------------| +| AC | Alternating Current | +| AMN | Artificial Mains Network | +| BC | Band Category | +| BH | Backhaul | +| CA | Carrier Aggregation | +| CDN | Coupling/Decoupling Network | +| CS | Capability Set | +| DC | Direct Current | +| EIRP | Equivalent Isotropic Radiated Power | +| EMC | Electromagnetic Compatibility | +| e.r.p. | Effective Radiated Power | +| ESD | Electrostatic Discharge | +| EUT | Equipment Under Test | +| FR | Frequency Range | +| FRC | Fixed Reference Channel | +| IAB | Integrated Access and Backhaul | +| mIAB | Mobile IAB | +| NC | Non Contiguous | +| NG | Next Generation | +| NGC | Next Generation Core | +| NR | New Radio | +| NR-ARFCN | NR Absolute Radio Frequency Channel Number | +| NRTC | NR Test Configuration | +| NTC | Test Configuration for Non-contiguous operation | +| RAT | Radio Access Technology | +| RF | Radio Frequency | +| RIB | Radiated Interface Boundary | +| rms | root mean square | +| SC | Single Carrier | +| TC | Test Configuration | + +# --- 4 Test conditions + +## 4.1 General + +Requirements throughout the EMC specifications are in some cases defined separately for different frequency ranges (FR). The frequency ranges FR1 and FR2 are defined in clause 5.1 of TS 38.174 [2]. NR IAB is designed to operate in FR1 and FR2-1. + +The equipment shall be tested in normal test environment defined in the corresponding IAB conformance testing specification TS 38.176-1 [24] and TS 38.176-2 [25]. The test conditions shall be recorded in the test report. + +For IAB Node capable of multi-band operation, the requirements in the present document apply for each supported *operating band* unless otherwise stated. *Operating bands* shall be activated according to the test configuration in subclause 4.5. Tests shall be performed relating to each type of port and all *operating bands* shall be assessed during the tests. + +The manufacturer shall declare the supported *operating band(s)* according to the list of NR IAB *operating bands* defined in TS 38.174 [2]. + +NOTE 1: NR IAB *operating bands* for IAB *type 1-H*, are declared by the manufacturer according to the declarations specified in TS 38.176-1 [24], table 4.6-1 and TS 38.176-2 [25], table 4.6-1. + +NOTE 2: NR IAB *operating bands* for IAB *type 1-O* and IAB *type 2-O*, are declared by the manufacturer according to the declarations specified in TS 38.176-2 [25], table 4.6-1. + +## 4.2 Arrangements for establishing a communication link + +The wanted RF input signal nominal frequency shall be selected by setting the NR Absolute Radio Frequency Channel Number (NR-ARFCN) to an appropriate number. + +A communication link shall be set up with a suitable test system capable of evaluating the required performance criteria (hereafter called “the test system”) at the radio interface and *telecommunication port/ports* (the NG interface). The test system shall be located outside of the test environment. + +When the EUT is required to be in the transmit/receive mode, the following conditions shall be met: + +- For the IAB *type 1-H* testing, the EUT shall be commanded to operate at rated transmit power; +- For the IAB *type 1-O* and IAB *type 2-O* testing, the EUT transmit power shall be configured as stated in clause 8.1 for emission test and clause 9.1 for immunity test accordingly, +- Adequate measures shall be taken to avoid the effect of the unwanted signal on the measuring equipment; +- The wanted input signal level shall be set to a level where the performance is not limited by the receiver noise floor or strong signal effects. + +NOTE: 15 dB above the conducted reference sensitivity level has been used as an example of wanted input signal level in legacy 3GPP EMC specifications for establishing a communication link. + +For immunity tests clause 4.3 shall apply and the conditions shall be as follows. + +## 4.3 Narrow band responses on receivers + +Responses on receivers or duplex transceivers occurring during the immunity test at discrete frequencies which are narrow band responses (spurious responses), are identified by the following method: + +- if during an immunity test the quantity being monitored goes outside the specified tolerances (clause 6), it is necessary to establish whether the deviation is due to a narrow band response or to a wide band (EMC) phenomenon. Therefore, the test shall be repeated with the unwanted signal frequency increased, and then decreased by $2 \times \text{BW}_{\text{Channel}}$ MHz, where $\text{BW}_{\text{Channel}}$ is the channel bandwidth as defined in TS 38.174 [2], clause 5.3; +- if the deviation disappears in either one or both of the above MHz offset cases, then the response is considered as a narrow band response; +- if the deviation does not disappear, this may be due to the fact that the offset has made the frequency of the unwanted signal correspond to the frequency of another narrow band response. Under these circumstances the procedure is repeated with the increase and decrease of the frequency of the unwanted signal set to $2.5 \times \text{BW}_{\text{Channel}}$ MHz; +- if the deviation does not disappear with the increased and/or decreased frequency, the phenomenon is considered wide band and therefore an EMC problem and the equipment fails the test. + +For immunity test narrow band responses are disregarded. + +## 4.4 Exclusion bands + +### 4.4.1 Transmitter exclusion band + +The *transmitter exclusion band* for IAB is the frequency range over which no tests of radiated immunity of a transmitter are made. As the IAB node may operate its access and backhaul link in different NR IAB *operating band*, the *transmitter exclusion band* for IAB applies separately for the access and backhaul link. The *transmitter exclusion band* applies to IAB type 1-O. + +The *transmitter exclusion band* is defined as: + +$$F_{DL,low} - \Delta f_{OBUE} < f < F_{DL,high} + \Delta f_{OBUE}$$ + +Where: + +- Values of $F_{DL,low}$ and $F_{DL,high}$ , $F_{UL,low}$ and $F_{UL,high}$ are defined for each NR IAB *operating band* in TS 38.174 [2], clause 5.2. +- The value of $\Delta f_{OBUE}$ is derived considering the width of the NR IAB *operating band*, and is defined as in table 4.4.1-1 and table 4.4.1-2. + +**Table 4.4.1-1: $\Delta f_{OBUE}$ offset value for NR IAB-DU** + +| IAB-DU type | Operating band characteristics | $\Delta f_{OBUE}$ (MHz) | +|-----------------|--------------------------------------------------------|-------------------------| +| IAB-DU type 1-O | $F_{DL,high} - F_{DL,low} < 100$ MHz | 10 | +| | $100$ MHz $\leq F_{DL,high} - F_{DL,low} \leq 900$ MHz | 40 | + +**Table 4.4.1-2: $\Delta f_{OBUE}$ offset value for NR IAB-MT** + +| IAB-MT type | Operating band characteristics | $\Delta f_{OBUE}$ (MHz) | +|-----------------|--------------------------------------------------------|-------------------------| +| IAB-MT type 1-O | $F_{UL,high} - F_{UL,low} < 100$ MHz | 10 | +| | $100$ MHz $\leq F_{UL,high} - F_{UL,low} \leq 900$ MHz | 40 | + +For IAB node capable of multi-band operation, the total transmitter exclusion band is a combination of the exclusion bands for each operating band supported by IAB node. + +NOTE: As the radiated immunity testing is defined in the frequency range 80 MHz to 6 GHz, there is no *transmitter exclusion band* defined for IAB type 2-O. + +### 4.4.2 Receiver exclusion band + +The *receiver exclusion band* for IAB is the frequency range over which no tests of radiated immunity of a receiver are made. As the IAB node may operate its access and backhaul link in different NR IAB *operating band*, the *receiver exclusion band* for IAB applies separately for the access and backhaul link. The *receiver exclusion band* applies to IAB type 1-O. + +The *receiver exclusion band* is defined as: + +$$F_{UL,low} - \Delta f_{RX} < f < F_{UL,high} + \Delta f_{RX}$$ + +Where: + +- Values of $F_{UL,low}$ and $F_{UL,high}$ are defined for each NR IAB *operating band* in TS 38.174 [2], clause 5.2. +- The value of $\Delta f_{RX}$ is derived considering the width of the NR IAB *operating band*, and is defined as in table 4.4.2-1. Value of the $\Delta f_{RX}$ also depends on the RI test setup, i.e. whether or not the *spatial exclusion zone* (as described in subclause 9.2.2) is considered during the RI test. + +**Table 4.4.1-1: $\Delta f_{Rx}$ offset values for IAB** + +| IAB type | IAB operating band characteristics | RI test setup | $\Delta f_{Rx}$ (MHz) | +|--------------|--------------------------------------------------------|------------------------|-----------------------| +| IAB type 1-O | $F_{UL,high} - F_{UL,low} < 100$ MHz | With exclusion zone | 20 | +| | | Without exclusion zone | 60 | +| | $100$ MHz $\leq F_{UL,high} - F_{UL,low} \leq 900$ MHz | With exclusion zone | 60 | +| | | Without exclusion zone | 200 | + +NOTE: As the radiated immunity testing is defined in the frequency range 80 MHz to 6 GHz, there is no *receiver exclusion band* defined for IAB type 2-O. + +## 4.5 IAB test configurations + +The present clause defines the IAB test configurations that shall be used for demonstrating conformance. A single IAB carrier shall be used for testing of single-carrier capable IAB. + +Single carrier configuration (SC) tests shall be performed using signal with narrowest supported IAB channel bandwidth with the smallest supported subcarrier spacing declared per operating band in TS 38.176-1 [24] clause 4.6, and TS 38.176-2 [25] clause 4.6. + +For other IAB node, the test configurations in table 4.5-1 and table 4.5-2 shall be used. The IAB test configurations (IABTCx) are defined in TS 38.176-1 [24], clause 4.7 for IAB type 1-H and in TS 38.176-2 [25], clause 4.7 for IAB type 1-O and IAB type 2-O. + +**Table 4.5-1: Test configurations for IAB type 1-H** + +| IAB test case | IAB capable of multi-carrier and/or CA in a single band | | | IAB capable of multi-band operation | | +|----------------|---------------------------------------------------------|------------------------------------------------|------------------------------------------------|-------------------------------------|---------------------------------------| +| | Contiguous spectrum capable IAB | C and NC capable IAB with identical parameters | C and NC capable IAB with different parameters | Common connector | Separate connectors | +| Emission tests | IABTC1 | IABTC3 | IABTC1, IABTC3 | IABTC1/3 (Note 1), IABTC5 | IABTC1/3 (Note 1, 2), IABTC5 (Note 2) | +| Immunity tests | IABTC1 | IABTC3 | IABTC1, IABTC3 | IABTC5 | IABTC1/3 (Note 1), IABTC5 (Note 3) | + +NOTE 1: IABTC1 and/or IABTC3 shall be applied in each supported operating band. +NOTE 2: For single-band operation test, other TAB connector(s) is (are) terminated. +NOTE 3: IABTC5 is only applicable for multi-band receiver. + +**Table 4.5-2: Test configurations for IAB type 1-O** + +| IAB test case | single-band RIB | | | multi-band RIB | +|----------------|---------------------------------|------------------------------------------------|------------------------------------------------|---------------------------| +| | Contiguous spectrum capable IAB | C and NC capable IAB with identical parameters | C and NC capable IAB with different parameters | | +| Emission tests | IABTC1 | IABTC3 | IABTC1, IABTC3 | IABTC1/3 (Note 1), IABTC5 | +| Immunity tests | IABTC1 | IABTC3 | IABTC1, IABTC3 | IABTC5 | + +NOTE 1: IABTC1 and/or IABTC3 shall be applied in each supported operating band. + +Table 4.5-3: Test configurations for IAB type 2-O + +| IAB test case | single-band RIB | | | +|----------------|---------------------------------|------------------------------------------------|------------------------------------------------| +| | Contiguous spectrum capable IAB | C and NC capable IAB with identical parameters | C and NC capable IAB with different parameters | +| Emission tests | IABTC1 | IABTC3 | IABTC1, IABTC3 | +| Immunity tests | IABTC1 | IABTC3 | IABTC1, IABTC3 | + +# 5 Performance assessment + +## 5.1 General + +The following information shall be recorded in or annexed to the test report: + +- the primary functions of the radio equipment to be tested during and after the EMC testing; +- the intended functions of the radio equipment which shall be in accordance with the documentation accompanying the equipment; +- the method to be used to verify that a communications link is established and maintained; +- the user-control functions and stored data that are required for normal operation and the method to be used to assess whether these have been lost after EMC stress; +- the *ancillary equipment* to be combined with the radio equipment for testing (where applicable); +- the information about *ancillary equipment* intended to be used with the radio equipment; +- information about the common and/or band-specific active RF components and other hardware blocks for a communication link in IAB node capable of multi-band operation; +- an exhaustive list of ports (and RIBs), classified as either power or signal/control. Power ports shall further be classified as AC or DC power. + +Performance assessment of a IAB Node with multiple enclosures may be done separately for the IAB Node part with the Radio digital unit and the Radio unit respectively, according to the manufacturer's choice. + +A communication link used by more than one operating band, shall be assessed on all operating bands. Communication link(s) and/or radio performance parameters for the operating bands can during the test be assessed simultaneously or separately for each band, depending on the test environment capability. + +## 5.2 Assessment of throughput of IAB-DU + +For downlink assessment of the IAB-DU, a communication link shall be established between the transmitter (via port for the IAB type 1-H, or via RIB for the IAB type 1-O and IAB type 2-O) and the test equipment. Test equipment shall meet the requirements for the throughput assessment defined in TS38.176-1[24] and TS38.176-2[25] for the bearer used in the immunity tests. The level of the signal supplied to the equipment should be within the range for which the assessment of throughput is not impaired. Power control shall be OFF during the immunity testing. + +For uplink assessment of the IAB-DU, the value of the throughput at the output of the receiver shall be monitored at NG interface by using suitable test equipment. + +## 5.3 Assessment of throughput of IAB-MT + +The test arrangement and signals, given in clause 4, apply to IAB-MT. The assessment of equipment performance shall be based on data transfer according to the criteria in clause 6. + +## 5.4 Ancillary equipment + +At the manufacturer's discretion the test may be performed on the ancillary equipment separately or on a representative configuration of the combination of radio and ancillary equipment. In each case EUT is tested against all applicable immunity and emission clauses of the present document and in each case, compliance enables the ancillary equipment to be used with different radio equipment. + +# 6 Performance criteria + +## 6.1 Performance criteria for continuous phenomena for IAB + +The test should, where possible, be performed using a bearer with the characteristics of data rate and throughput defined in table 6.1-1 and table 6.1-2. If the test is not performed using one of these bearers (for example, none of them are supported by the IAB node), the characteristics of the bearer used shall be recorded in the test report. + +The throughput in table 6.1-1 and table 6.1-2 is stated relative to the maximum throughput of the FRC. + +The IAB node uplink and downlink paths shall each meet the performance criteria defined in table 6.1-1 and table 6.1-2 during the test. If the uplink and downlink paths are evaluated as a one loop then the criteria is two times the throughput reduction shown in table 6.1-1 and table 6.1-2 (i.e. throughput > 90 % instead of throughput > 95 %). After each test case IAB node shall operate as intended with no loss of user control function, stored data and the communication link to both UE and donor test equipments shall be maintained. + +**Table 6.1-1: FR1 performance criteria for continuous phenomena for IAB** + +| NR channel bandwidth (MHz) as defined in TS 38.174 section 5.3.2 [2] for IAB-MT and TS 38.104 section 5.3.2-1 [22] for IAB-DU | Sub-carrier spacing (kHz) | Bearer information data rate for IAB-MT | Bearer information data rate for IAB-DU | Performance criteria (Note 1, Note 2) | +|-------------------------------------------------------------------------------------------------------------------------------|---------------------------|-------------------------------------------|-------------------------------------------|------------------------------------------| +| 10, 15 | 30 | G-FR1-A1-22 in annex A.1 in TS 38.174 [2] | G-FR1-A1-2 in annex A.1 in TS 38.104 [22] | Throughput > 95 %,
no loss of service | +| 10, 15 | 60 | G-FR1-A1-23 in annex A.1 in TS 38.174 [2] | G-FR1-A1-3 in annex A.1 in TS 38.104 [22] | | +| 20 to 100 | 30 | G-FR1-A1-25 in annex A.1 in TS 38.174 [2] | G-FR1-A1-5 in annex A.1 in TS 38.104 [22] | | +| 20 to 100 | 60 | G-FR1-A1-26 in annex A.1 in TS 38.174 [2] | G-FR1-A1-6 in annex A.1 in TS 38.104 [22] | | + +NOTE 1: The performance criteria, throughput > 95 %, no loss of service, applies also if a bearer with another characteristics is used in the test. + +NOTE 2: The performance criteria, throughput > 90 %, no loss of service, applies instead if the uplink and downlink paths are evaluated as a one loop. + +**Table 6.1-2: FR2-1 performance criteria for continuous phenomena for IAB** + +| NR channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Bearer information data rate for IAB-MT | Bearer information data rate for IAB-DU | Performance criteria (Note 1, Note 2) | +|----------------------------|---------------------------|-------------------------------------------|-------------------------------------------|------------------------------------------| +| 50, 100, 200 | 60 | G-FR2-A1-21 in annex A.1 in TS 38.174 [2] | G-FR2-A1-1 in annex A.1 in TS 38.104 [22] | Throughput > 95 %,
no loss of service | +| 50 | 120 | G-FR2-A1-22 in annex A.1 in TS 38.174 [2] | G-FR2-A1-2 in annex A.1 in TS 38.104 [22] | | +| 100, 200, 400 | 120 | G-FR2-A1-23 in annex A.1 in TS 38.174 [2] | G-FR2-A1-3 in annex A.1 in TS 38.104 [22] | | + +NOTE 1: The performance criteria, throughput > 95 %, no loss of service, applies also if a bearer with another characteristics is used in the test. + +NOTE 2: The performance criteria, throughput > 90 %, no loss of service, applies instead if the uplink and downlink paths are evaluated as a one loop. + +## 6.2 Performance criteria for transient phenomena for IAB + +At the conclusion of the total test (comprising the series of individual exposures to transient phenomena) the IAB node shall operate as intended with no user noticeable loss of control functions or stored data. At the conclusion of each exposure the IAB node shall operate with no user noticeable loss of the communication link to both UE and donor test equipments. + +The channel bandwidth, sub-carrier spacing and bearer information data rate should be chosen based on manufacturer's declaration and defined according to table 6.1-1 and table 6.1-2. + +## 6.3 Performance criteria for continuous phenomena for Ancillary equipment + +The apparatus shall continue to operate as intended during and after the test. No degradation of performance or loss of function is allowed below the performance level specified by the manufacturer, when the apparatus is used as intended. The performance level may be replaced by a permissible performance loss. If the minimum performance level or the permissible performance loss is not specified by the manufacturer, either of these may be derived from the product description and documentation and what the user may reasonably expect from the apparatus if used as intended. + +## 6.4 Performance criteria for transient phenomena for Ancillary equipment + +The apparatus shall continue to operate as intended after the test. No degradation of performance or loss of function is allowed below the performance level specified by the manufacturer, when the apparatus is used as intended. The performance level may be replaced by a permissible performance loss. During the test, degradation of performance is however allowed. If the minimum performance level or the permissible performance loss is not specified by the manufacturer, either of these may be derived from the product description and documentation and what the user may reasonably expect from the apparatus if used as intended. + +# --- 7 Applicability overview + +## 7.0 General + +Throughout this specification, whenever the IAB requirement is referred, its applicability shall be considered as applicable to the IAB node as a whole (i.e. IAB-MT and IAB-DU), irrespective of its implementation. Performance assessment of an IAB node with multiple enclosures may be done separately for each of them, according to the manufacturer's choice. + +## 7.1 Emission + +Table 7.1-1: Emission requirements applicability + +| Phenomenon | Application | Equipment test requirement | | Reference clause in the present document | Reference standard | +|----------------------------------|-----------------------------------------|--------------------------------------|---------------------|------------------------------------------|-------------------------------------------| +| | | IAB | Ancillary equipment | | | +| Radiated emission | IAB enclosure (Note 1) | applicable for IAB type 1-H (Note 2) | not applicable | 8.2.1 | ITU-R SM.329 [20] | +| Radiated emission | Enclosure of ancillary equipment | not applicable | applicable | 8.2.2 | CISPR 32 [6] | +| Conducted emission | DC power input/output port | applicable | applicable | 8.3 | CISPR 32 [6] | +| Conducted emission | AC mains input/output port | applicable | applicable | 8.4 | CISPR 32 [6] | +| Conducted emission | Telecommunication port | applicable | applicable | 8.5 | CISPR 32 [6] | +| Harmonic current emissions | AC mains input port | applicable | applicable | 8.6 | IEC 61000-3-2 [8] or IEC 61000-3-12 [9] | +| Voltage fluctuations and flicker | AC mains input port | applicable | applicable | 8.7 | IEC 61000-3-3 [10] or IEC 61000-3-11 [11] | + +NOTE 1: Radiated emission measurement of an IAB node with multiple enclosures may be done separately for each of them, according to the manufacturer's choice. + +NOTE 2: Radiated emission requirements for IAB type 1-O, IAB type 2-O, mIAB-MT type 1-O and mIAB type 2-O are described in clause 8.2.1. + +## 7.2 Immunity + +Table 7.2-1: Immunity requirements applicability + +| Phenomenon | Application | Equipment test requirement | | Reference clause in the present document | Reference standard | +|------------------------------------------|---------------------------------------------------------------------------|----------------------------|---------------------|------------------------------------------|---------------------| +| | | IAB equipment | Ancillary equipment | | | +| RF electromagnetic field (80 – 6000 MHz) | Enclosure | applicable | applicable | 9.2 | IEC 61000-4-3 [13] | +| Electrostatic discharge | Enclosure | applicable | applicable | 9.3 | IEC 61000-4-2 [12] | +| Fast transients common mode | Signal, telecommunications and control ports, DC and AC power input ports | applicable | applicable | 9.4 | IEC 61000-4-4 [14] | +| RF common mode 0.15 – 80 MHz | Signal, telecommunications and control ports, DC and AC power input ports | applicable | applicable | 9.5 | IEC 61000-4-6 [16] | +| Voltage dips and interruptions | AC mains power input ports | applicable | applicable | 9.6 | IEC 61000-4-11 [17] | +| Surges, common and differential mode | AC power input ports and telecommunications port | applicable | applicable | 9.7 | IEC 61000-4-5 [15] | + +# 8 Emission + +## 8.1 Test configurations + +This clause defines the configurations for emission tests as follows: + +- The equipment shall be tested under normal test conditions as specified in the functional standards; +- The test configuration shall be as close to normal intended use as possible; +- If the equipment is part of a system, or can be connected to ancillary equipment, then it shall be acceptable to test the equipment while connected to the minimum configuration of *ancillary equipment* necessary to exercise the ports; +- If the equipment has a large number of ports, then a sufficient number shall be selected to simulate actual operation conditions and to ensure that all the different types of termination are tested; +- The test conditions, test configuration and mode of operation shall be recorded in the test report; +- Ports which in normal operation are connected shall be connected to an *ancillary equipment* or to a representative piece of cable correctly terminated to simulate the input/output characteristics of the *ancillary equipment*; in case of *IAB type 1-H*, *antenna ports* shall be correctly terminated; +- For *IAB type 1-O* and *IAB type 2-O* without *antenna ports* but intentionally radiating through the *antenna array*, the equipment shall be placed in a test setup suitable for the radiated power; +- Ports which are not connected to cables during normal operation, e.g. service connectors, programming connectors, temporary connectors etc. shall not be connected to any cables for the purpose of EMC testing. Where cables have to be connected to these ports, or interconnecting cables have to be extended in length in order to exercise the EUT, precautions shall be taken to ensure that the evaluation of the EUT is not affected by the addition or extension of these cables; +- The test arrangements for transmitter and receiver clauses of the transceiver are described separately for the sake of clarity. However, where possible the test of the transmitter clause and receiver clause of the EUT may be carried out simultaneously to reduce test time. + +## 8.2 Radiated emission + +### 8.2.1 Radiated emission, IAB + +This test is applicable to *IAB type 1-H*. This test shall be performed on a representative configuration of IAB node. + +For *IAB type 1-O* and *IAB type 2-O*, the radiated emission is covered by radiated spurious emission requirement in TS 38.174 [2], conforming to the test requirement in TS 38.174[2]. + +#### 8.2.1.1 Definition + +This test assesses the ability of IAB node to limit unwanted emission from the *enclosure port*. + +#### 8.2.1.2 Test method + +- a) A test site fulfilling the requirements of ITU-R SM.329 [20] shall be used. The IAB node shall be placed on a non-conducting support and shall be operated from a power source via a RF filter to avoid radiation from the power leads. One of the following two alternative measurement methods shall be used: + +- 1) Field strength method measurement + +The test method shall be in accordance with CISPR 32 [6]. The field strength measurements shall be performed on a test site that is validated according to the methods and requirements of CISPR 16-1-4 [23]. + +Unless otherwise stated, measurements are conducted at 3 m or 10 m on an open area test site (OATS) or semi anechoic chamber (SAC) for frequencies up to 1 GHz, or at 3 m on a free space open area test site (FSOATS) or fully-anechoic room (FAR) for frequencies above 1 GHz. Unless otherwise stated, all measurements are done with RMS detector and with the -3 dB bandwidth of the measuring filter equal to the reference bandwidth in table 8.2.1.3-1. + +NOTE 1: Test site validation methods for radiated emissions tests are defined in CISPR 16-1-4 [23], clause 6 and 7. Examples of test site validation methods are listed below: + +- 30 – 1000 MHz frequency range: Normalized Site Attenuation (NSA), Reference Site Method (RSM). +- 1 – 18 GHz frequency range: $S_{VSWR}$ standard test procedure, $S_{VSWR}$ reciprocal test procedure. + +##### 2) Substitution method measurement (also called a substitution method) + +Mean power of any spurious components shall be detected by the test antenna and measuring receiver (e.g. a spectrum analyser). At each frequency at which a component is detected, the IAB node shall be rotated and the height of the test antenna adjusted to obtain maximum response, and the effective radiated power (e.r.p.) of that component determined by a substitution measurement. The measurement shall be repeated with the test antenna in the orthogonal polarization plane. + +NOTE: Effective radiated power (e.r.p.) refers to the radiation of a half wave tuned dipole instead of an isotropic antenna. There is a constant difference of 2.15 dB between e.i.r.p. and e.r.p., as defined in ITU-R SM.329 annex 1 [20]. + +$$\text{e.r.p. (dBm)} = \text{e.i.r.p. (dBm)} - 2.15$$ + +- b) The IAB node shall transmit with maximum power declared by the manufacturer with all transmitters active. Set the base station to transmit a signal as stated in subclause 4.5. +- c) For IAB-DU the received power shall be measured over the frequency range from 30 MHz to $F_{DL,low} - \Delta f_{OBUE}$ and from $F_{DL,high} + \Delta f_{OBUE}$ up to 12750 MHz. The video bandwidth shall be approximately three times the resolution bandwidth. If this video bandwidth is not available on the measuring receiver, it shall be the maximum available and at least 1 MHz. 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 [20]. Unless otherwise stated, all measurements are done as mean power (RMS). +- D) For IAB-MT the received power shall be measured over the frequency range from 30 MHz to $F_{UL,low} - \Delta f_{OBUE}$ and from $F_{UL,high} + \Delta f_{OBUE}$ up to 12750 MHz. The video bandwidth shall be approximately three times the resolution bandwidth. If this video bandwidth is not available on the measuring receiver, it shall be the maximum available and at least 1 MHz. For some *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 ITU-R recommendation SM.329 [20]. Unless otherwise stated, all measurements are done as mean power (RMS). + +#### 8.2.1.3 Limits + +The frequency boundary and reference bandwidths for the detailed transitions of the limits between the requirements for out of band emissions and spurious emissions are based on ITU-R Recommendations SM.329 [20] and SM.1539 [21]. The IAB type I-H shall meet the limits below: + +**Table 8.2.1.3-1: Limits for radiated emissions from IAB type 1-H** + +| Frequency Range | e.r.p.
(dBm) | Field strength
at 3 m
(dBμV/m)
(NOTE 4) | Field strength
at 10 m
(dBμV/m)
(NOTE 4) | Reference
bandwidth | NOTE | +|-------------------------------------------------------------------------------------------------------|-----------------|--------------------------------------------------|---------------------------------------------------|------------------------|------| +| 30 MHz ≤ f < 1000 MHz | -36 | 65.4 (NOTE 5) | 54.9 (NOTE 5) | 100 kHz | | +| 1 GHz ≤ f < 12.75 GHz | -30 | 67.4 | Not applicable | 1 MHz | | +| 12.75 GHz ≤ f < 5 th harmonic of the upper frequency edge of the DL operating band in GHz | -30 | 67.4 | Not applicable | 1 MHz | 1 | +| F DL,low – Δf OBUE < f < F DL,high + Δf OBUE (for IAB-DU) | Not defined | Not defined | Not defined | Not defined | 2,3 | +| F UL,low – Δf OBUE < f < F UL,high + Δf OBUE (for IAB-MT) | | | | | | + +NOTE 1: For IAB-DU, 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 IAB-MT, 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 2: For IAB node capable of multi-band operation, the frequency ranges relating to the RF bandwidths of all supported *operating bands* apply. + +NOTE 3: ΔfOBUE is defined in clause 6.6.1 of TS 38.174 [2]. + +NOTE 4: The field strength measurements shall be conducted on OATS or SAC for frequencies up to 1 GHz, or on FSOATS or FAR for frequencies above 1 GHz. + +NOTE 5: Limits for radiated emissions are translated from the e.r.p. limit of -36 dBm into the field strength limit of 61.4 dBμV/m (at 3m) or 50.9 dBμV/m (at 10m), and increased by the site gain value of 4 dB. The value of the site gain is based on ITU-R Recommendations SM.329 [20]. + +#### 8.2.1.4 Interpretation of the measurement results + +The interpretation of the results recorded in a test report for the radiated emission measurements described in the present document shall be as follows: + +- the measured value related to the corresponding limit will be used to decide whether an equipment meets the requirements of the present document; +- the value of the measurement uncertainty for the measurement of each parameter shall be included in the test report; +- the recorded value of the measurement uncertainty shall be, for each measurement, equal to or lower than the values in table 8.2.1.4-1 for IAB node. + +Table 8.2.1.4-1 specifies the maximum measurement uncertainty of the test system. The test system shall enable the equipment under test to be measured with an uncertainty not exceeding the specified values. All tolerances and uncertainties are absolute values, and are valid for a confidence level of 95 %, unless otherwise stated. + +A confidence level of 95 % is the measurement uncertainty tolerance interval for a specific measurement that contains 95% of the performance of a population of test equipment. + +**Table 8.2.1.4-1: Maximum measurement uncertainty (IAB node)** + +| Parameter | Uncertainty for EUT dimension ≤ 1 m | Uncertainty for EUT dimension > 1 m | +|--------------------------------------------------------|-------------------------------------|-------------------------------------| +| Effective radiated RF power between 30 MHz to 180 MHz | ±6 dB | ±6 dB | +| Effective radiated RF power between 180 MHz to 4 GHz | ±4 dB | ±6 dB | +| Effective radiated RF power between 4 GHz to 12,75 GHz | ±6 dB | ±9 dB (NOTE) | +| Field strength between 30 MHz to 12,75 GHz | ±6 dB | ±6 dB | + +NOTE: This value may be reduced to ±6 dB when further information on the potential radiation characteristic of the EUT is available. + +NOTE: If the test system for a test is known to have a measurement uncertainty greater than that specified in table 8.2.1.4-1, this equipment can still be used, provided that an adjustment is made follows: + +Any additional uncertainty in the test system over and above that specified in table 8.2.1.4-1 is used to tighten the test requirements – making the test harder to pass. + +This procedure will ensure that a test system not compliant with table 8.2.1.4-1 does not increase the probability of passing an EUT that would otherwise have failed a test if a test system compliant with table 8.2.1.4-1 had been used. + +### 8.2.2 Radiated emission, ancillary equipment + +This test is only applicable to *ancillary equipment* not incorporated in the radio equipment and intended to be measured on a stand-alone basis, as declared by the manufacturer. This test shall be performed on a representative configuration of the *ancillary equipment*. + +This test is not applicable for *ancillary equipment* incorporated in the radio equipment, or for *ancillary equipment* intended to be measured in combination with the radio equipment. In these cases, the requirements of the relevant product standard for the effective use of the radio spectrum shall apply. + +#### 8.2.2.1 Definition + +This test assesses the ability of *ancillary equipment* to limit unwanted emission from the *enclosure port*. + +#### 8.2.2.2 Test method + +The test method shall be in accordance with CISPR 32[6]. + +#### 8.2.2.3 Limits + +The *ancillary equipment* shall meet the limits according to CISPR 32[6] table A.4 and table A.5. + +For the referred limit values, the following shall apply: + +Where the limits value varies over a given frequency range, it changes linearly with respect to the logarithm of the frequency. + +Where there is a step in the relevant limit, the lower value shall be applied at the transition frequency. + +Alternatively, for *ancillary equipment* intended to be used in telecommunication centres only, the class A limits given in CISPR 32 [6], annex A, table A.2 and table A.3 may be used. + +## 8.3 Conducted emission DC power input/output port + +If the DC power cable of the radio equipment is intended to be less than 3 m in length, and intended only for direct connection to a dedicated AC to DC power supply, then the measurement shall be performed only on the AC power input of that power supply as specified in clause 8.4. + +This test shall be performed on a representative configuration of the radio equipment, the associated *ancillary equipment*, or representative configuration of the combination of radio and *ancillary equipment*. + +### 8.3.1 Definition + +This test assesses the ability of radio equipment and *ancillary equipment* to limit internal noise from the DC power input/output ports. + +### 8.3.2 Test method + +The test method shall be in accordance with CISPR 32 [6] and the Artificial Mains Network (AMN) shall be connected to a DC power source. + +In the case of DC output ports, the ports shall be connected via an AMN to a load drawing the rated current of the source. + +A measuring receiver shall be connected to each AMN measurement port in turn and the conducted emission recorded. + +The equipment shall be installed with a ground plane as defined in CISPR 32 [6]. The reference earth point of the AMN shall be connected to the reference ground plane with a conductor as short as possible. + +### 8.3.3 Limits + +The equipment shall meet the limits according to CISPR 32 [6] table A.9, which are defined for average detector receiver and for quasi-peak detector receiver. If the average limit is met when using a quasi-peak detector, the equipment shall be deemed to meet both limits and measurement with the average detector receiver is not necessary. + +Where there is a step in the referred limit values, the lower value shall be applied at the transition frequency. + +## 8.4 Conducted emissions, AC mains power input/output port + +This test is applicable to equipment powered by the AC mains. + +This test is not applicable to AC output ports which are connected directly (or via a circuit breaker) to the AC power port of the EUT. + +This test shall be performed on a representative configuration of the radio equipment, the associated *ancillary equipment*, or representative configuration of the combination of radio and *ancillary equipment*. + +### 8.4.1 Definition + +This test assesses the ability of radio equipment and *ancillary equipment* to limit internal noise from the AC mains power input/output ports. + +### 8.4.2 Test method + +The test method shall be in accordance with CISPR 32 [6]. + +### 8.4.3 Limits + +The equipment shall meet the limits according to CISPR 32 [6] table A.10, which are defined for the average detector receiver and for quasi-peak detector receiver. If the average limit is met when using a quasi-peak detector, the equipment shall be deemed to meet both limits and measurement with the average detector receiver is not necessary. + +For the referred limit values following shall apply: + +Where the limits value varies over a given frequency range, it changes linearly with respect to the logarithm of the frequency. + +Where there is a step in the relevant limit, the lower value shall be applied at the transition frequency. + +Alternatively, for equipment intended to be used in telecommunication centres the limits given in CISPR 32 [6] table A.9 shall be used. + +## 8.5 Conducted emissions, telecommunication port + +This test is applicable for radio equipment and/or *ancillary equipment* for fixed use which have *telecommunication ports*. + +This test shall be performed on a representative configuration of radio equipment, the associated *ancillary equipment*, or a representative configuration of the combination of radio and *ancillary equipment*. + +### 8.5.1 Definition + +This test assesses the EUT unwanted emission present at the *telecommunication ports*. + +### 8.5.2 Test method + +The test method shall be in accordance with CISPR 32 [6]. + +### 8.5.3 Limits + +The *telecommunication ports* shall meet the limits according to CISPR 32 [6] table A.12. + +For the referred limit values, following shall apply: + +Where the limits value varies over a given frequency range, it changes linearly with respect to the logarithm of the frequency. + +Where there is a step in the relevant limit, the lower value shall be applied at the transition frequency. + +Alternatively, for equipment intended to be used in telecommunication centres only, the limits given in CISPR 32 [6] table A.11 may be used. + +## 8.6 Harmonic Current emissions (AC mains input port) + +The requirements of IEC 61000-3-2 [8] for harmonic current emission apply for equipment covered by the scope of the present document. For equipment with an input current of greater than 16A per phase, IEC 61000-3-12 [9] applies. + +## 8.7 Voltage fluctuations and flicker (AC mains input port) + +The requirements of IEC 61000-3-3 [10] for voltage fluctuations and flicker apply for equipment covered by the scope of the present document. For equipment with an input current of greater than 16 A per phase, IEC 61000-3-11 [11] applies. + +# --- 9 Immunity + +## 9.1 Test configurations + +This clause defines the configurations for immunity tests as follows: + +- the equipment shall be tested under normal test conditions as specified in the functional standards; +- during the test, the RF output power may be reduced to a power level sufficient for establishing and maintaining the required communication link; +- the test configuration shall be as close to normal intended use as possible; +- if the equipment is part of a system, or can be connected to *ancillary equipment*, then it shall be acceptable to test the equipment while connected to the minimum configuration of *ancillary equipment* necessary to exercise the ports; +- if the equipment has a large number of ports, then a sufficient number shall be selected to simulate actual operation conditions and to ensure that all the different types of termination are tested; +- the test conditions, test configuration and mode of operation shall be recorded in the test report; +- ports which in normal operation are connected shall be connected to an *ancillary equipment* or to a representative piece of cable correctly terminated to simulate the input/output characteristics of the *ancillary equipment*. In case of IAB type 1-H, *antenna ports* shall be correctly terminated; +- ports which are not connected to cables during normal operation, e.g. service connectors, programming connectors, temporary connectors etc. shall not be connected to any cables for the purpose of EMC testing. Where cables have to be connected to these ports, or interconnecting cables have to be extended in length in + +order to exercise the EUT, precautions shall be taken to ensure that the evaluation of the EUT is not affected by the addition or extension of these cables; + +- immunity tests on the entire IAB Node shall be performed by establishing communication links at the radio interface (e.g. with the mobile simulator) and the NG interface (e.g. with an NGC simulator) and evaluating the throughput; +- immunity tests shall be performed on both the uplink and downlink paths. The tests shall also include both the radio interface and the NG interface. Throughput evaluation may be carried out at either interface, where appropriate, and the measurements for the uplink and downlink paths may be carried out as a single path looped at either the radio interface or NG interface. In case of looping is used care have to be taken that the throughput information doesn't change due to looping; +- for IAB node capable of multi-band operation, communication links shall be established in such a way that all *operating band(s)* are activated during the test according to the applicable test configurations in clause 4.5. Performance assessment may be done separately for each *operating band*. + +## 9.2 RF electromagnetic field (80 MHz – 6000 MHz) + +The test shall be performed on a representative configuration of the equipment, the associated ancillary equipment, or representative configuration of the combination of radio and ancillary equipment. + +### 9.2.1 Definition + +This test assesses the ability of radio equipment and *ancillary equipment* to operate as intended in the presence of a radio frequency electromagnetic field disturbance at the enclosure. + +### 9.2.2 Test method and level + +The test method shall be in accordance with IEC 61000-4-3 [13], which specifies test methodology based on anechoic chamber. The use of reverberation chamber test method according to IEC 61000-4-21 [18], clause 6.1 and Annex D as alternative method is allowed. + +The following requirements shall apply: + +- The test level shall be 3 V/m amplitude modulated to a depth of 80 % by a sinusoidal audio signal of 1 kHz; +- The stepped frequency increments shall be 1 % of the momentary frequency; +- The test shall be performed over the frequency range 80 MHz - 6000 MHz; with the exception of the exclusion band for receivers (see clause 4.4); +- Responses in stand-alone receivers or receivers which are part of transceivers occurring at discrete frequencies which are narrow band responses, shall be disregarded, see clause 4.3; +- The frequencies selected during the test shall be recorded in the test report. +- For the test method in accordance with IEC 61000-4-3[13], the *spatial exclusion zone* can be chosen to protect the IAB node receiver(s). For the frequency range above 690 MHz (according to ETSI EN 301 489-50 [28]), the EMC RF electromagnetic field immunity requirement with a level of 10 V/m applies on the non-radiating faces of the *IAB type 1-O*, or *IAB type 2-O*, as depicted on figures 9.2.2-1. + +NOTE: Depending on the IAB implementation, application of the spatial exclusion to all radiating faces of the IAB may not allow proper execution of the RI testing. In such cases as depicted on figures 9.2.2-2, to protect the IAB node receiver(s), exclusion bands shall be considered, as in table 4.4.1-1. + +![Diagram illustrating the spatial exclusion zone for an IAB radiating face. It shows the EUT, RI testing directions, and the EUT radiating direction.](26d664119ad25250780f554633444e54_img.jpg) + +The diagram illustrates a spatial exclusion zone for an IAB radiating face. A central vertical dashed rectangle is labeled "Spatial exclusion zone". To the left of this zone, a semi-circular shape represents the "EUT radiating face", with the label "EUT" inside it. A horizontal arrow points from the EUT towards the right, labeled "EUT radiating direction". Three other arrows, all labeled "RI testing direction", point towards the EUT from the top, bottom, and left. The top and bottom arrows are vertical, while the left arrow is horizontal. + +Diagram illustrating the spatial exclusion zone for an IAB radiating face. It shows the EUT, RI testing directions, and the EUT radiating direction. + +Figure 9.2.2-1: Example of the spatial exclusion application in case of a single instance of the IAB radiating face (horizontal plane depicted) + +![Diagram illustrating the spatial exclusion application for a 3-panel IAB node. The diagram shows three IAB arrays (IAB array #1, IAB array #2, IAB array #3) arranged in a horizontal plane. IAB array #1 is on the right, IAB array #2 is on the bottom-left, and IAB array #3 is on the top-left. A dashed rectangle labeled 'Spatial Exclusion Zone' is positioned to the right of IAB array #1. Red arrows indicate the 'Radiating face' for each array: IAB array #1 points right towards '90° Front Side', IAB array #2 points down towards '180° Right Side', and IAB array #3 points up towards '0° Left Side'. A red arrow on the left points towards '270° Back Side'. The diagram also includes labels for 'Radiating face' and 'Radiating face' for the arrays.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +Diagram illustrating the spatial exclusion application for a 3-panel IAB node. The diagram shows three IAB arrays (IAB array #1, IAB array #2, IAB array #3) arranged in a horizontal plane. IAB array #1 is on the right, IAB array #2 is on the bottom-left, and IAB array #3 is on the top-left. A dashed rectangle labeled 'Spatial Exclusion Zone' is positioned to the right of IAB array #1. Red arrows indicate the 'Radiating face' for each array: IAB array #1 points right towards '90° Front Side', IAB array #2 points down towards '180° Right Side', and IAB array #3 points up towards '0° Left Side'. A red arrow on the left points towards '270° Back Side'. The diagram also includes labels for 'Radiating face' and 'Radiating face' for the arrays. + +Figure 9.2.2-2: Example of the spatial exclusion application in case of a 3-panel IAB node (horizontal plane depicted) – proper execution of the RI test may not be feasible + +### 9.2.3 Performance criteria + +#### IAB node: + +The performance criteria of clause 6.1 shall apply. + +#### Ancillary equipment: + +The performance criteria of clause 6.3 shall apply. + +## 9.3 Electrostatic discharge + +The test shall be performed on a representative configuration of the radio equipment, the associated *ancillary equipment*, or representative configuration of the combination of radio and *ancillary equipment*. + +### 9.3.1 Definition + +This test assesses the ability of radio equipment and *ancillary equipment* to operate as intended in the event of an electrostatic discharge. + +### 9.3.2 Test method and level + +The test method shall be in accordance with IEC 61000-4-2 [12]: + +- for contact discharge, the equipment shall pass at $\pm 4$ kV; +- for air discharge shall pass at $\pm 8$ kV; +- electrostatic discharge shall be applied to all exposed surfaces of the EUT except where the user documentation specially indicates a requirement for appropriate protective measures. + +NOTE: Ensure that the EUT is fully discharged between each ESD exposure. + +### 9.3.3 Performance criteria + +#### IAB node: + +The performance criteria of clause 6.2 shall apply. + +#### Ancillary equipment: + +The performance criteria of clause 6.4 shall apply. + +## 9.4 Fast transients common mode + +The test shall be performed on AC mains power input ports. + +This test shall be performed on *signal ports*, *telecommunication ports*, *control ports* and DC power input/output ports if the cables may be longer than 3 m. + +Where this test is not carried out on a port or any other ports because the manufacturer declares that it is not intended to be used with cables longer than 3 m, a list of ports which were not tested for this reason shall be included in the test report. + +This test shall be performed on a representative configuration of the equipment, the associated *ancillary equipment*, or representative configuration of the combination of radio and *ancillary equipment*. + +### 9.4.1 Definition + +This test assesses the ability of radio equipment and *ancillary equipment* to operate as intended in the event of fast transients present on one of the input/output ports. + +### 9.4.2 Test method and level + +The test method shall be in accordance with IEC 61000-4-4 [14]: + +- The test level for *signal ports*, *telecommunication ports* and *control ports* shall be 0.5 kV open circuit voltage as given in IEC 61000-4-4 [14]; +- The test level for DC power input/output ports shall be 0.5 kV open circuit voltage as given in IEC 61000-4-4 [14]; +- The test level for AC mains power input ports shall be 1 kV open circuit voltage as given in IEC 61000-4-4 [14]. + +For AC and DC power input ports the transients shall be applied (in parallel) to all the conductors in the cable with reference to the cabinet reference earth (true common mode) and the source impedance shall be 50 $\Omega$ . + +### 9.4.3 Performance criteria + +#### IAB node: + +The performance criteria of clause 6.2 shall apply. + +#### **Ancillary equipment:** + +The performance criteria of clause 6.4 shall apply. + +## 9.5 RF common mode (0.15 MHz – 80 MHz) + +The test shall be performed on AC mains power input/output ports. + +This test shall be performed on *signal ports*, telecommunication *ports*, control and DC power input/output ports, which may have cables longer than 3 m. + +Where this test is not carried out on a port or any other ports because the manufacturer declares that it is not intended to be used with cables longer than stated above, a list of ports which were not tested shall be included in the test report. + +This test shall be performed on a representative configuration of the equipment, the associated *ancillary equipment*, or representative configuration of the combination of radio and *ancillary equipment*. + +NOTE: This test can also be performed using the clamp injection method, where appropriate, see IEC 61000-4-6 [16]. + +### 9.5.1 Definition + +This test assesses the ability of radio equipment and *ancillary equipment* to operate as intended in the presence of a radio frequency electromagnetic disturbance. + +### 9.5.2 Test method and level + +The test method shall be in accordance with IEC 61000-4-6 [16]: + +- The test signal shall be amplitude modulated to a depth of 80 % by a sinusoidal audio signal of 1 kHz; +- The stepped frequency increments shall be 50 kHz in the frequency range 150 kHz to 5 MHz and 1% frequency increment of the momentary frequency in the frequency range 5 MHz to 80 MHz; +- The test level shall be severity level 2 as given in IEC 61000-4-6 [16] corresponding to 3 V rms, at a transfer impedance of 150 Ω; +- The test shall be performed over the frequency range 150 kHz – 80 MHz; +- The injection method to be used shall be selected according to the basic standard IEC 61000-4-6 [16]; +- Responses of stand-alone receivers or receivers which are part of transceivers occurring at discrete frequencies which are narrow band responses, shall be disregarded, see clause 4.3; +- The frequencies of the immunity test signal selected and used during the test shall be recorded in the test report. + +### 9.5.3 Performance criteria + +#### **IAB node:** + +The performance criteria of clause 6.1 shall apply. + +#### **Ancillary equipment:** + +The performance criteria of clause 6.3 shall apply. + +## 9.6 Voltage dips and interruptions + +The tests shall be performed on AC mains power input ports. + +These tests shall be performed on a representative configuration of the equipment, the associated *ancillary equipment*, or representative configuration of the combination of radio and *ancillary equipment*. + +### 9.6.1 Definition + +These tests assess the ability of radio equipment and *ancillary equipment* to operate as intended in the event of voltage dips and interruptions present on the AC mains power input ports. + +### 9.6.2 Test method and level + +The test method shall be in accordance with IEC 61000-4-11 [17], where the test levels shall be: + +- Voltage dip: 0 % residual voltage for 0.5 cycle; +- Voltage dip: 0 % residual voltage for 1 cycle; +- Voltage dip: 70 % residual voltage for 25/30 cycles (at 50/60 Hz); +- Voltage interruption: 0 % residual voltage for 250/300 cycles (at 50/60 Hz). + +### 9.6.3 Performance criteria + +For a 0 % residual voltage dip test, the performance criteria for transient phenomena shall be applied: + +- Criteria 6.2 for IAB node +- Criteria 6.4 for *ancillary equipment* + +For a 70% residual voltage dip test and for voltage interruption test, the following applies: + +1. In the case where the equipment is fitted with or connected to a battery back-up, the following performance criteria shall be applied: + - Criteria 6.2 for IAB node + - Criteria 6.4 for *ancillary equipment* +2. In the case where the equipment is powered solely from the AC mains supply (without the use of a parallel battery back-up) volatile user data may have been lost and if applicable the communication link need not to be maintained and lost functions should be recoverable by user or operator: + - No unintentional responses shall occur at the end of the test, when the voltage is restored to nominal + - In the event of loss of communications link or in the event of loss of user data, this fact shall be recorded in the test report + +## 9.7 Surges, common and differential mode + +The tests shall be performed on AC mains power input ports. + +This test shall be additionally performed on *telecommunication ports*. + +These tests shall be performed on a representative configuration of the equipment, the associated *ancillary equipment*, or representative configuration of the combination of radio and *ancillary equipment*. + +### 9.7.1 Definition + +These tests assess the ability of radio equipment and *ancillary equipment* to operate as intended in the event of surges being present at the AC mains power input ports and *telecommunication ports*. + +### 9.7.2 Test method and level + +The test method shall be in accordance with IEC 61000-4-5 [15]. + +The requirements and evaluation of test results given in clause 9.7.2.1 (*telecommunication ports*, outdoor cables), clause 9.7.2.2 (*telecommunication ports*, indoor cables) and clause 9.7.2.3 (AC power ports) shall apply, but no test shall be required where normal functioning cannot be achieved, because of the impact of the CDN on the EUT. + +#### 9.7.2.1 Test method for telecommunication ports directly connected to outdoor cables + +The test level for *telecommunications ports*, intended to be directly connected to the telecommunications network via outdoor cables, shall be 1 kV line to ground as given in IEC 61000-4-5 [15]. In this case the total output impedance of the surge generator shall be in accordance with the basic standard IEC 61000-4-5 [15]. + +The test generator shall provide the 1.2/50 $\mu\text{s}$ pulse as defined in IEC 61000-4-5 [15]. + +#### 9.7.2.2 Test method for telecommunication ports connected to indoor cables + +The test level for telecommunication *ports*, intended to be connected to indoor cables (longer than 10 m) shall be 0.5 kV line to ground. In this case the total output impedance of the surge generator shall be in accordance with the basic standard IEC 61000-4-5 [15]. + +The test generator shall provide the 1.2/50 $\mu\text{s}$ pulse as defined in IEC 61000-4-5 [15]. + +#### 9.7.2.3 Test method for AC power ports + +The test level for AC power input *ports* shall be 2 kV line to ground, and 1 kV line to line, with the output impedance of the surge generator as given in IEC 61000-4-5 [15]. + +In telecommunication centres 1 kV line to ground and 0.5 kV line to line shall be used. + +The test generator shall provide the 1.2/50 $\mu\text{s}$ pulse as defined in IEC 61000-4-5 [15]. + +### 9.7.3 Performance criteria + +#### IAB node: + +The performance criteria of clause 6.2 shall apply. + +#### Ancillary equipment: + +The performance criteria of clause 6.4 shall apply. \ No newline at end of file diff --git a/marked/Rel-18/38_series/38176-1/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-18/38_series/38176-1/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b8711582e98b44c4e2c79d6a41537961713fcad7 --- /dev/null +++ b/marked/Rel-18/38_series/38176-1/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b1def8e0d7b22be8cd891b2c1d3614241d55442eea90989cf371349fa2e0102 +size 32323 diff --git a/marked/Rel-18/38_series/38176-1/18b87e4ce7ef441f5620b8d6539a2939_img.jpg b/marked/Rel-18/38_series/38176-1/18b87e4ce7ef441f5620b8d6539a2939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8fd1f28cb77f62952797cc2783fd9f4304a838c1 --- /dev/null +++ b/marked/Rel-18/38_series/38176-1/18b87e4ce7ef441f5620b8d6539a2939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cae451733682deaf9f942c77382f577cc28befebf1dcfbb3baa8770e9703b83e +size 6155 diff --git a/marked/Rel-18/38_series/38176-1/1fd763be1b7a05b52e554f0583617642_img.jpg b/marked/Rel-18/38_series/38176-1/1fd763be1b7a05b52e554f0583617642_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..65c749e1275123b552f91f162524559a84b77f6a --- /dev/null +++ b/marked/Rel-18/38_series/38176-1/1fd763be1b7a05b52e554f0583617642_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad51279afd8fd16e2d303c3016fe18c46b8e2e691181511684a8eb51714d8170 +size 20143 diff --git a/marked/Rel-18/38_series/38176-1/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-18/38_series/38176-1/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d50845d066ed49ac2151ec4bd25ba7d2a9ee68bf --- /dev/null +++ b/marked/Rel-18/38_series/38176-1/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d333cf719ff148ff8d95ac838b17947ed816f0feb489f47c51057b57d8cd58a +size 43900 diff --git a/marked/Rel-18/38_series/38176-1/3054e46608784063609e8c7a253fcd24_img.jpg b/marked/Rel-18/38_series/38176-1/3054e46608784063609e8c7a253fcd24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45a5d76c38e67be227875ea46f0aac719efe147d --- /dev/null +++ b/marked/Rel-18/38_series/38176-1/3054e46608784063609e8c7a253fcd24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a610b1cc24e50fdf941a05bffab7c4c5efdd6d7b784c756d34111df8dac0d04e +size 33529 diff --git a/marked/Rel-18/38_series/38176-1/3334c914bdd313ced24f692366028a6d_img.jpg b/marked/Rel-18/38_series/38176-1/3334c914bdd313ced24f692366028a6d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b9c3f081cc98e23a8df418ce4c2852038f4632d --- /dev/null +++ b/marked/Rel-18/38_series/38176-1/3334c914bdd313ced24f692366028a6d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e945851a99f5066b67117b68ff6bae734b4c927d93fc946208af32614f71734 +size 51735 diff --git a/marked/Rel-18/38_series/38176-1/351243fd59cdae993f191da9ebb48016_img.jpg b/marked/Rel-18/38_series/38176-1/351243fd59cdae993f191da9ebb48016_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ec32fe5338a8c2a6ea16364bf9e50212b9287a7 --- /dev/null +++ b/marked/Rel-18/38_series/38176-1/351243fd59cdae993f191da9ebb48016_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e85b9026a509f81ef4226d94903a5ac790dc84240693dea22c7e27c6063edbb4 +size 40096 diff --git a/marked/Rel-18/38_series/38176-1/3d6d0738981fdd03d003cc653bdfdaae_img.jpg b/marked/Rel-18/38_series/38176-1/3d6d0738981fdd03d003cc653bdfdaae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..273b94f71aabbe00b7b1abcd3e67dae76cf45cb0 --- /dev/null +++ b/marked/Rel-18/38_series/38176-1/3d6d0738981fdd03d003cc653bdfdaae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:76d2d3d63cb1817d6bf3aa374e280cb0cef5ca735d224d5213a604f1d5db17a0 +size 37262 diff --git a/marked/Rel-18/38_series/38176-1/3e0674a68142b10eac3384d2acd6c136_img.jpg b/marked/Rel-18/38_series/38176-1/3e0674a68142b10eac3384d2acd6c136_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0a45efad41d1fa8fe7666f488d25c514e70c5527 --- /dev/null +++ b/marked/Rel-18/38_series/38176-1/3e0674a68142b10eac3384d2acd6c136_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:739ef84f6aa29728899cd01736fcf311a42ad4ba8cd4ab29709d5ed857201aaa +size 46666 diff --git a/marked/Rel-18/38_series/38176-1/41bc9383c0d6e910a69e23d465ae5607_img.jpg b/marked/Rel-18/38_series/38176-1/41bc9383c0d6e910a69e23d465ae5607_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b16e97e941d1bb9cc65001a2313347c1d5b80e7 --- /dev/null +++ b/marked/Rel-18/38_series/38176-1/41bc9383c0d6e910a69e23d465ae5607_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98f8dc457a29c24d4a93cadf0675b5840c8dfc2010b7ad117d93d123bad0021b +size 73671 diff --git a/marked/Rel-18/38_series/38176-1/49035d3c3a8a3e4936b78ae634359aab_img.jpg b/marked/Rel-18/38_series/38176-1/49035d3c3a8a3e4936b78ae634359aab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..87c997c61352914aa559a9217d01f696a629171b --- /dev/null +++ b/marked/Rel-18/38_series/38176-1/49035d3c3a8a3e4936b78ae634359aab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c862eb6f4c0c8fd1dd1beff5faa50be87eb2af563c7451609916d349004943ef +size 33173 diff --git a/marked/Rel-18/38_series/38176-1/51b71ddd044e4e2f9db8fb8dc08a560b_img.jpg b/marked/Rel-18/38_series/38176-1/51b71ddd044e4e2f9db8fb8dc08a560b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a609eeeb5d9427ee76b9f66101bb29c3cbe6633 --- /dev/null +++ b/marked/Rel-18/38_series/38176-1/51b71ddd044e4e2f9db8fb8dc08a560b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:307d544745634535140ab1aa6629c5dd7c5da8335ff9bd23549c98f5bc1ab892 +size 141239 diff --git a/marked/Rel-18/38_series/38176-1/5766537cfe2f332b335d51cd00e40b46_img.jpg b/marked/Rel-18/38_series/38176-1/5766537cfe2f332b335d51cd00e40b46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e67c4f3ea23a16bcd9d0b70f0b7e9d127468c390 --- /dev/null +++ b/marked/Rel-18/38_series/38176-1/5766537cfe2f332b335d51cd00e40b46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aecb03f65737e40c22f522dae18bc24d25f150534141d79669033be05bcfe2c7 +size 52322 diff --git a/marked/Rel-18/38_series/38176-1/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38176-1/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8bfa19a3924bea77884784716fed1fab2bd789ec --- /dev/null +++ b/marked/Rel-18/38_series/38176-1/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/38176-1/6424fc1c7a7c26364a135780c1e479f9_img.jpg b/marked/Rel-18/38_series/38176-1/6424fc1c7a7c26364a135780c1e479f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..79e340a1384653e3b2bfaddaa397fa388c984019 --- /dev/null +++ b/marked/Rel-18/38_series/38176-1/6424fc1c7a7c26364a135780c1e479f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9019b79deb2478514bc4e5ee8ca671741cf7638e765cfa106e6ec062330bd2e7 +size 5820 diff --git a/marked/Rel-18/38_series/38176-1/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38176-1/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..25bf39b5f02b52970526a94656848a88bc1da6c0 --- /dev/null +++ b/marked/Rel-18/38_series/38176-1/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9a3b0f14e900ceb5f09d1a21957704bd1c465d73771a3b732202d06203ff6d7 +size 5495 diff --git a/marked/Rel-18/38_series/38176-1/6bd66a9f24bf7442862b8f3ab580297e_img.jpg b/marked/Rel-18/38_series/38176-1/6bd66a9f24bf7442862b8f3ab580297e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a48534a55c8edcd277fdc0e66fcfd6dea5a2ba03 --- /dev/null +++ b/marked/Rel-18/38_series/38176-1/6bd66a9f24bf7442862b8f3ab580297e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca8403669a70510fcd60b50f84836a6ffb8eaf48964c2658db0395064a2cefaa +size 38230 diff --git a/marked/Rel-18/38_series/38176-1/768662ed52466041c8f43e005b48f501_img.jpg b/marked/Rel-18/38_series/38176-1/768662ed52466041c8f43e005b48f501_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c21464525a553ee1f126fe0b824877429ea116db --- /dev/null +++ b/marked/Rel-18/38_series/38176-1/768662ed52466041c8f43e005b48f501_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4bbd25be474ae69c6969ff323d7e08283c6768348ef54c32d9ed2d47a91f1a35 +size 58053 diff --git a/marked/Rel-18/38_series/38176-1/851584a7a34f04e13a0ae8dc57f1a7be_img.jpg b/marked/Rel-18/38_series/38176-1/851584a7a34f04e13a0ae8dc57f1a7be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40020abd633cfcc93f006ca8bab238deb5d3ccae --- /dev/null +++ b/marked/Rel-18/38_series/38176-1/851584a7a34f04e13a0ae8dc57f1a7be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:78635b9633f52dc6690a6e311f143ed5062f88bb68020e464b9f0b4e08df13f9 +size 5218 diff --git a/marked/Rel-18/38_series/38176-1/889982a45a70fa2e605a553842ce8952_img.jpg b/marked/Rel-18/38_series/38176-1/889982a45a70fa2e605a553842ce8952_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..415c1dd9bee5065dabe13267ab1ffaa22644f2d9 --- /dev/null +++ b/marked/Rel-18/38_series/38176-1/889982a45a70fa2e605a553842ce8952_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3eae12714daef2cedf13469c6a0fc20451f448ac5d82334160e9b94e2a44da60 +size 5549 diff --git a/marked/Rel-18/38_series/38176-1/89a9571da272e76616860592f8960874_img.jpg b/marked/Rel-18/38_series/38176-1/89a9571da272e76616860592f8960874_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e9adaf38a62bc17fc91dda2b369a1570a208a27 --- /dev/null +++ b/marked/Rel-18/38_series/38176-1/89a9571da272e76616860592f8960874_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:154d39bd62d8f5eddb43eb8d5ca057f8d19b52673764b3dee25d62acc8b1cef4 +size 32281 diff --git a/marked/Rel-18/38_series/38176-1/8bdf315853992d21f389da554f3a8215_img.jpg b/marked/Rel-18/38_series/38176-1/8bdf315853992d21f389da554f3a8215_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c544603197d330c0479079643ce5ebe17cf392fe --- /dev/null +++ b/marked/Rel-18/38_series/38176-1/8bdf315853992d21f389da554f3a8215_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04ce9beda656363e7f6e327995e378d71f7193d29a58899d1b1017fde82e1a3f +size 6184 diff --git a/marked/Rel-18/38_series/38176-1/91d148dff4c40942811f006b6e8f8168_img.jpg b/marked/Rel-18/38_series/38176-1/91d148dff4c40942811f006b6e8f8168_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c5d5a3a29069a8b1cb050b2b18e9a1f8dc3a7133 --- /dev/null +++ b/marked/Rel-18/38_series/38176-1/91d148dff4c40942811f006b6e8f8168_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02887ec835358e95538155f2b33074ba4435652269e39972a342f6829b2b4125 +size 44861 diff --git a/marked/Rel-18/38_series/38176-1/a0bf1e4e2765bf05e8009f39007df772_img.jpg b/marked/Rel-18/38_series/38176-1/a0bf1e4e2765bf05e8009f39007df772_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..46f5a13edc5789dfd0b9606c63bdd5c185152ae0 --- /dev/null +++ b/marked/Rel-18/38_series/38176-1/a0bf1e4e2765bf05e8009f39007df772_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a5e727b3b85b19d758f7a8c42c8b29bf5c70555237cb8df17488f76c22a466b +size 41520 diff --git a/marked/Rel-18/38_series/38176-1/b4022f9f3b9a3b30ade5c100052cb16a_img.jpg b/marked/Rel-18/38_series/38176-1/b4022f9f3b9a3b30ade5c100052cb16a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a13c313e1e5959a0792cd6c1b2f17c1890ea9d87 --- /dev/null +++ b/marked/Rel-18/38_series/38176-1/b4022f9f3b9a3b30ade5c100052cb16a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ac1b28b7efc7f1f45585e7e2c3d6637be988f86b8faea994fa238af150f1bc41 +size 40097 diff --git a/marked/Rel-18/38_series/38176-1/c139aa372176ff96d02d462be232c810_img.jpg b/marked/Rel-18/38_series/38176-1/c139aa372176ff96d02d462be232c810_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4aff0c8f532ae05ecd2651b3d49ee8e78a95f82f --- /dev/null +++ b/marked/Rel-18/38_series/38176-1/c139aa372176ff96d02d462be232c810_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0912642da27fffde92c0a2300f5d1bd8a60b4772adbc54442af79999aba34682 +size 56674 diff --git a/marked/Rel-18/38_series/38176-1/c24f22afc8106a8f9b76c759a1db6891_img.jpg b/marked/Rel-18/38_series/38176-1/c24f22afc8106a8f9b76c759a1db6891_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b095fc50d1b5875d1ae82be8abcef883fed78493 --- /dev/null +++ b/marked/Rel-18/38_series/38176-1/c24f22afc8106a8f9b76c759a1db6891_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a48d9684989648a46b3fecadfd6d733938c013ca80c51eb1382719eeb2b92398 +size 80205 diff --git a/marked/Rel-18/38_series/38176-1/cdb980c2fe504f3132b907d4de707c7f_img.jpg b/marked/Rel-18/38_series/38176-1/cdb980c2fe504f3132b907d4de707c7f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b777639459ae11047de97860e44310d63a66929 --- /dev/null +++ b/marked/Rel-18/38_series/38176-1/cdb980c2fe504f3132b907d4de707c7f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e91e35ef2f10e16bb26d0f5c4b41d1e43a12c8fcf1d4fb6024600b37055baa0 +size 46424 diff --git a/marked/Rel-18/38_series/38176-1/d0dd433695a01d364ac98f846f68bc8f_img.jpg b/marked/Rel-18/38_series/38176-1/d0dd433695a01d364ac98f846f68bc8f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9b147b674c970d2553997930b318f081ae97c29 --- /dev/null +++ b/marked/Rel-18/38_series/38176-1/d0dd433695a01d364ac98f846f68bc8f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:060b0d38bb70596e3e5c1c360dea05e3f5c6b0d8118c8655b6e2f7194ffa9759 +size 18451 diff --git a/marked/Rel-18/38_series/38176-1/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg b/marked/Rel-18/38_series/38176-1/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc6fc72cc5828fc9a1b3a3ad8217024786beab8a --- /dev/null +++ b/marked/Rel-18/38_series/38176-1/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dbaca81c51efdd1061a5d551c6b685feb5b3e5aaee88c4e6e45640d5e69e898a +size 33203 diff --git a/marked/Rel-18/38_series/38176-1/e0113695dbf148bf5ec34354e544414b_img.jpg b/marked/Rel-18/38_series/38176-1/e0113695dbf148bf5ec34354e544414b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..beb9a11483dfc46a6b40649f3fbc74f1a63fa6f0 --- /dev/null +++ b/marked/Rel-18/38_series/38176-1/e0113695dbf148bf5ec34354e544414b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8098c8aaf2e410d17a89204c80b92102919649351d65c0df7ec6270a10fb5e4e +size 56485 diff --git a/marked/Rel-18/38_series/38176-1/e27f0c293be4088211306b9fc673178b_img.jpg b/marked/Rel-18/38_series/38176-1/e27f0c293be4088211306b9fc673178b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56cb0df081fe9bee23bad908e7bcf8896ca285ba --- /dev/null +++ b/marked/Rel-18/38_series/38176-1/e27f0c293be4088211306b9fc673178b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc7654f2f5af433ac2c28ebc6355b1d83ee3428a3095eb575a1dedf0ea21deff +size 73252 diff --git a/marked/Rel-18/38_series/38176-1/e86d625d503436075806fd06df985443_img.jpg b/marked/Rel-18/38_series/38176-1/e86d625d503436075806fd06df985443_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98f4b9c26f29baf933bbb17693e9e35f29b5d381 --- /dev/null +++ b/marked/Rel-18/38_series/38176-1/e86d625d503436075806fd06df985443_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82ce47aa47902cbf4e81986867cdf402574cec9a688ba96225ff64212a6be63e +size 38508 diff --git a/marked/Rel-18/38_series/38176-1/f3c73e8e478b8b2d9f6a96a970040556_img.jpg b/marked/Rel-18/38_series/38176-1/f3c73e8e478b8b2d9f6a96a970040556_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..863222797367408febd0230e4b3f0fcc3dcfc716 --- /dev/null +++ b/marked/Rel-18/38_series/38176-1/f3c73e8e478b8b2d9f6a96a970040556_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c907898971ccadc3b212407194ddfa64dfd8e93f8379823ef7d46927fe380cfc +size 5520 diff --git a/marked/Rel-18/38_series/38176-1/fdd39709ead076a03c9920362efa1a00_img.jpg b/marked/Rel-18/38_series/38176-1/fdd39709ead076a03c9920362efa1a00_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ec7e8cb01169e33fd9dec4d8a7db7eb6decef97 --- /dev/null +++ b/marked/Rel-18/38_series/38176-1/fdd39709ead076a03c9920362efa1a00_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b320368a27ff67b1efb0fa65ce8f9a1093cd73e482cc36beb4216d0e140eff45 +size 32634 diff --git a/marked/Rel-18/38_series/38176-1/raw.md b/marked/Rel-18/38_series/38176-1/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..00e9181a94f86f2b0c7f913f66324df2052e97f1 --- /dev/null +++ b/marked/Rel-18/38_series/38176-1/raw.md @@ -0,0 +1,8762 @@ + + +# 3GPP TS 38.176-1 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 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 bold, stylized font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' underneath. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +# **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +# --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|------------------------------------------------------------------------------|----| +| Foreword..... | 22 | +| 1 Scope..... | 24 | +| 2 References..... | 24 | +| 3 Definitions of terms, symbols and abbreviations..... | 25 | +| 3.1 Terms..... | 25 | +| 3.2 Symbols..... | 28 | +| 3.3 Abbreviations..... | 29 | +| 4 General conducted test conditions and declarations..... | 30 | +| 4.1 Measurement uncertainties and test requirements..... | 30 | +| 4.1.1 General..... | 30 | +| 4.1.2 Acceptable uncertainty of Test System..... | 30 | +| 4.1.2.1 General..... | 30 | +| 4.1.2.2 Measurement of transmitter..... | 31 | +| 4.1.2.3 Measurement of receiver..... | 32 | +| 4.1.2.4 Measurement of performance requirements..... | 35 | +| 4.1.3 Interpretation of measurement results..... | 37 | +| 4.2 Conducted requirement reference points..... | 37 | +| 4.2.1 IAB type 1-H ..... | 37 | +| 4.3 IAB classes..... | 38 | +| 4.3.1 IAB-DU class ..... | 38 | +| 4.3.2 IAB-MT class ..... | 39 | +| 4.4 Regional requirements..... | 39 | +| 4.5 IAB configurations..... | 39 | +| 4.5.1 IAB type 1-H ..... | 39 | +| 4.5.1.1 Transmit configurations..... | 39 | +| 4.5.1.2 Receive configurations..... | 40 | +| 4.5.1.3 Power supply options..... | 40 | +| 4.5.2 IAB with integrated Iuant BS modem..... | 41 | +| 4.6 Manufacturer declarations..... | 41 | +| 4.7 Test configurations..... | 46 | +| 4.7.1 General..... | 46 | +| 4.7.2 Test signal used to build Test Configurations..... | 46 | +| 4.7.3 IABTC1: Contiguous spectrum operation..... | 46 | +| 4.7.3.1 General..... | 46 | +| 4.7.3.2 IABTC1 generation..... | 46 | +| 4.7.3.3 IABTC1 power allocation..... | 47 | +| 4.7.4 IABTC2: Contiguous CA occupied bandwidth..... | 47 | +| 4.7.4.1 General..... | 47 | +| 4.7.4.2 IABTC2 generation..... | 47 | +| 4.7.4.3 IABTC2 power allocation..... | 48 | +| 4.7.5 IABTC3: Non-contiguous spectrum operation..... | 48 | +| 4.7.5.1 General..... | 48 | +| 4.7.5.2 IABTC3 generation..... | 48 | +| 4.7.5.3 IABTC3 power allocation..... | 48 | +| 4.7.6 IABTC4: Multi-band test configuration for full carrier allocation..... | 48 | +| 4.7.6.1 General..... | 48 | +| 4.7.6.2 IABTC4 generation..... | 48 | +| 4.7.6.3 IABTC4 power allocation..... | 49 | +| 4.7.7 IABTC5: Multi-band test configuration with high PSD per carrier..... | 49 | +| 4.7.7.1 General..... | 49 | +| 4.7.7.2 IABTC5 generation..... | 49 | +| 4.7.7.3 IABTC5 power allocation..... | 50 | +| 4.8 Applicability of requirements..... | 50 | +| 4.8.1 General..... | 50 | +| 4.8.2 Requirement set applicability..... | 50 | + +| | | | +|-------------|---------------------------------------------------------------------------|----| +| 4.8.3 | Applicability of test configurations for single-band operation..... | 50 | +| 4.8.4 | Applicability of test configurations for multi-band operation..... | 53 | +| 4.9 | RF channels and test models..... | 54 | +| 4.9.1 | RF channels..... | 54 | +| 4.9.2 | Test models..... | 55 | +| 4.9.2.1 | General..... | 55 | +| 4.9.2.2 | FR1 test models for IAB-DU..... | 55 | +| 4.9.2.3 | FR1 test models for IAB-MT..... | 56 | +| 4.9.2.3.1 | General..... | 56 | +| 4.9.2.3.2 | FR1 test model 1.1 (IAB-MT-FR1-TM1.1)..... | 57 | +| 4.9.2.3.3 | FR1 test model 2 (IAB-MT-FR1-TM2)..... | 57 | +| 4.9.2.3.3a | FR1 test model 2a (IAB-MT-FR1-TM2a)..... | 57 | +| 4.9.2.3.4 | FR1 test model 3.1 (IAB-MT-FR1-TM3.1)..... | 58 | +| 4.9.2.3.5 | FR1 test model 3.1a (IAB-MT-FR1-TM3.1a)..... | 58 | +| 4.9.2.4 | Data content of Physical channels and Signals for IAB-MT-FR1-TM..... | 58 | +| 4.9.2.4.1 | General..... | 58 | +| 4.9.2.4.2 | PUSCH..... | 59 | +| 4.10 | Requirements for contiguous and non-contiguous spectrum..... | 59 | +| 4.11 | Requirements for IAB capable of multi-band operation..... | 59 | +| 4.12 | Format and interpretation of tests..... | 60 | +| 4.13 | Test efficiency optimization..... | 61 | +| 4.14 | Requirements for IAB-DU and IAB-MT capable of simultaneous operation..... | 63 | +| 5 | Operating bands and channel arrangement..... | 64 | +| 6 | Conducted transmitter characteristics (IAB-DU and IAB-MT)..... | 64 | +| 6.1 | General..... | 64 | +| 6.2 | IAB output power..... | 64 | +| 6.2.1 | General..... | 64 | +| 6.2.2 | Minimum requirement..... | 65 | +| 6.2.3 | Test purpose..... | 65 | +| 6.2.4 | Method of test..... | 65 | +| 6.2.4.1 | Initial conditions..... | 65 | +| 6.2.4.2 | Procedure..... | 65 | +| 6.2.5 | Test requirement..... | 66 | +| 6.3 | Output power dynamics..... | 66 | +| 6.3.1 | IAB-DU Output Power Dynamics..... | 66 | +| 6.3.1.1 | General..... | 66 | +| 6.3.1.2 | RE power control dynamic range..... | 66 | +| 6.3.1.2.1 | Definition and applicability..... | 66 | +| 6.3.1.2.2 | Minimum requirement..... | 66 | +| 6.3.1.2.3 | Test purpose..... | 67 | +| 6.3.1.3 | Total power dynamic range..... | 67 | +| 6.3.1.3.1 | Definition and applicability..... | 67 | +| 6.3.1.3.2 | Minimum requirement..... | 67 | +| 6.3.1.3.3 | Test purpose..... | 67 | +| 6.3.1.3.4 | Method of test..... | 67 | +| 6.3.1.3.4.1 | Initial conditions..... | 67 | +| 6.3.1.3.4.2 | Procedure..... | 67 | +| 6.3.1.3.5 | Test requirements..... | 68 | +| 6.3.2 | IAB-MT Output Power Dynamics..... | 68 | +| 6.3.2.1 | Total power dynamic range..... | 68 | +| 6.3.2.1.1 | Definition and applicability..... | 68 | +| 6.3.2.1.2 | Minimum requirement..... | 68 | +| 6.3.2.1.3 | Test purpose..... | 68 | +| 6.3.2.1.4 | Method of test..... | 69 | +| 6.3.2.1.4.1 | Initial conditions..... | 69 | +| 6.3.2.1.4.2 | Procedure..... | 69 | +| 6.3.2.1.5 | Test requirements..... | 69 | +| 6.3.2.2 | Relative power tolerance for local area IAB-MT..... | 69 | +| 6.3.2.2.1 | Definition and applicability..... | 69 | +| 6.3.2.2.2 | Minimum requirement..... | 69 | + +| | | | +|-----------|------------------------------------------------------|----| +| 6.3.2.2.3 | Test purpose..... | 70 | +| 6.3.2.3 | Aggregate power tolerance for local area IAB-MT..... | 70 | +| 6.3.2.3.1 | Definition and applicability..... | 70 | +| 6.3.2.3.2 | Minimum requirement..... | 70 | +| 6.3.2.3.3 | Test purpose..... | 70 | +| 6.4 | Transmit ON/OFF power..... | 70 | +| 6.4.1 | Transmitter OFF power..... | 70 | +| 6.4.1.1 | Definition and applicability..... | 70 | +| 6.4.1.2 | Minimum requirement..... | 70 | +| 6.4.1.3 | Test purpose..... | 70 | +| 6.4.1.4 | Method of test..... | 70 | +| 6.4.1.5 | Test requirements..... | 71 | +| 6.4.2 | Transmitter transient period..... | 71 | +| 6.4.2.1 | Definition and applicability..... | 71 | +| 6.4.2.2 | Minimum requirement..... | 71 | +| 6.4.2.3 | Test purpose..... | 71 | +| 6.4.2.4 | Method of test..... | 72 | +| 6.4.2.4.1 | Initial conditions..... | 72 | +| 6.4.2.4.2 | Procedure..... | 72 | +| 6.4.2.5 | Test requirements..... | 72 | +| 6.5 | Transmitted signal quality..... | 73 | +| 6.5.1 | General..... | 73 | +| 6.5.2 | Frequency error..... | 73 | +| 6.5.2.1 | IAB-DU frequency error..... | 73 | +| 6.5.2.1.1 | Definition and applicability..... | 73 | +| 6.5.2.1.2 | Minimum Requirement..... | 73 | +| 6.5.2.1.3 | Test purpose..... | 73 | +| 6.5.2.1.4 | Method of test..... | 73 | +| 6.5.2.1.5 | Test Requirements..... | 73 | +| 6.5.2.2 | IAB-MT frequency error..... | 74 | +| 6.5.2.2.1 | Definition and applicability..... | 74 | +| 6.5.2.2.2 | Minimum Requirement..... | 74 | +| 6.5.2.2.3 | Test purpose..... | 74 | +| 6.5.2.2.4 | Method of test..... | 74 | +| 6.5.2.2.5 | Test Requirements..... | 74 | +| 6.5.3 | Modulation quality..... | 74 | +| 6.5.3.1 | Definition and applicability..... | 74 | +| 6.5.3.2 | Minimum Requirement..... | 74 | +| 6.5.3.3 | Test purpose..... | 74 | +| 6.5.3.4 | Method of test..... | 75 | +| 6.5.3.4.1 | Initial conditions..... | 75 | +| 6.5.3.4.2 | Procedure for IAB-DU..... | 75 | +| 6.5.3.4.3 | Procedure for IAB-MT..... | 76 | +| 6.5.3.5 | Test requirements..... | 76 | +| 6.5.4 | Time alignment error..... | 78 | +| 6.5.4.1 | Definition and applicability..... | 78 | +| 6.5.4.2 | Minimum requirement..... | 78 | +| 6.5.4.3 | Test purpose..... | 78 | +| 6.5.4.4 | Method of test..... | 78 | +| 6.5.4.4.1 | Initial conditions..... | 78 | +| 6.5.4.4.2 | Procedure..... | 78 | +| 6.5.4.5 | Test requirement..... | 79 | +| 6.5.5 | Timing error between IAB-DU and IAB-MT..... | 79 | +| 6.5.5.1 | Definition and applicability..... | 79 | +| 6.5.5.2 | Minimum requirement..... | 79 | +| 6.5.5.3 | Test purpose..... | 79 | +| 6.5.5.4 | Method of test..... | 79 | +| 6.5.5.4.1 | Initial conditions..... | 79 | +| 6.5.5.4.2 | Procedure..... | 80 | +| 6.5.5.5 | Test requirement..... | 80 | +| 6.6 | Unwanted emissions..... | 80 | + +| | | | +|-------------|-----------------------------------------------------------------------------------------|-----| +| 6.6.1 | General..... | 80 | +| 6.6.2 | Occupied bandwidth..... | 81 | +| 6.6.2.1 | General..... | 81 | +| 6.6.2.2 | Minimum Requirements..... | 81 | +| 6.6.2.3 | Test purpose..... | 81 | +| 6.6.2.4 | Method of test..... | 81 | +| 6.6.2.4.1 | Initial conditions..... | 81 | +| 6.6.2.4.2 | Procedure..... | 82 | +| 6.6.2.5 | Test requirements..... | 82 | +| 6.6.3 | Adjacent Channel Leakage Power Ratio..... | 83 | +| 6.6.3.1 | General..... | 83 | +| 6.6.3.2 | Minimum requirement..... | 83 | +| 6.6.3.3 | Test purpose..... | 83 | +| 6.6.3.4 | Method of test..... | 83 | +| 6.6.3.4.1 | Initial conditions..... | 83 | +| 6.6.3.4.2 | Procedure..... | 83 | +| 6.6.3.5 | Test requirements..... | 84 | +| 6.6.3.5.1 | General requirements..... | 84 | +| 6.6.3.5.2 | Limits and basic limits ..... | 84 | +| 6.6.3.5.3 | IAB type 1-H ..... | 87 | +| 6.6.4 | Operating band unwanted emissions..... | 88 | +| 6.6.4.1 | Definition and applicability..... | 88 | +| 6.6.4.2 | Minimum requirement..... | 90 | +| 6.6.4.3 | Test purpose..... | 90 | +| 6.6.4.4 | Method of test..... | 90 | +| 6.6.4.4.1 | Initial conditions..... | 90 | +| 6.6.4.4.2 | Procedure..... | 90 | +| 6.6.4.5 | Test requirements..... | 91 | +| 6.6.4.5.1 | General requirements..... | 91 | +| 6.6.4.5.2 | Basic limits for Wide Area IAB-DU and IAB-MT (Category A)..... | 91 | +| 6.6.4.5.3 | Basic limits for Wide Area IAB-DU and Wide Area IAB-MT (Category B)..... | 92 | +| 6.6.4.5.3.1 | General..... | 92 | +| 6.6.4.5.3.2 | Category B requirements..... | 92 | +| 6.6.4.5.4 | Basic limits for Medium Range IAB-DU (Category A and B)..... | 93 | +| 6.6.4.5.5 | Basic limits for Local Area IAB-DU and Local Area IAB-MT (Category A and B)..... | 95 | +| 6.6.4.5.5 | Basic limits for additional requirements..... | 96 | +| 6.6.4.5.5.1 | Limits in FCC Title 47..... | 96 | +| 6.6.4.5.6 | IAB type 1-H ..... | 96 | +| 6.6.5 | Transmitter spurious emissions..... | 96 | +| 6.6.5.1 | Definition and applicability..... | 96 | +| 6.6.5.2 | Minimum requirement..... | 97 | +| 6.6.5.3 | Test purpose..... | 97 | +| 6.6.5.4 | Method of test..... | 97 | +| 6.6.5.4.1 | Initial conditions..... | 97 | +| 6.6.5.4.2 | Procedure..... | 97 | +| 6.6.5.5 | Test requirements..... | 98 | +| 6.6.5.5.1 | Basic limits..... | 98 | +| 6.6.5.5.1.1 | Tx spurious emissions..... | 98 | +| 6.6.5.5.2 | Additional spurious emissions requirements..... | 99 | +| 6.6.5.5.3 | Co-location with base stations and IAB-nodes..... | 104 | +| 6.6.5.6 | IAB type 1-H ..... | 108 | +| 6.7 | Transmitter intermodulation..... | 108 | +| 6.7.1 | Definition and applicability..... | 108 | +| 6.7.2 | Minimum requirement..... | 108 | +| 6.7.3 | Test purpose..... | 108 | +| 6.7.4 | Method of test..... | 109 | +| 6.7.4.1 | Initial conditions..... | 109 | +| 6.7.4.2 | Procedure..... | 109 | +| 6.7.5 | Test requirements..... | 110 | +| 6.7.5.1 | IAB type 1-H ..... | 110 | +| 6.7.5.1.1 | Co-location minimum requirements..... | 110 | + +| | | | +|-----------|-------------------------------------------------------------|-----| +| 6.7.5.1.2 | Intra-system minimum requirements..... | 111 | +| 6.7.5.1.3 | Additional requirements..... | 111 | +| 7 | Conducted receiver characteristics (IAB-DU and IAB-MT)..... | 111 | +| 7.1 | General..... | 111 | +| 7.2 | Reference sensitivity level..... | 111 | +| 7.2.1 | Definition and applicability..... | 111 | +| 7.2.2 | Minimum requirement..... | 111 | +| 7.2.3 | Test purpose..... | 112 | +| 7.2.4 | Method of test..... | 112 | +| 7.2.4.1 | Initial conditions..... | 112 | +| 7.2.4.2 | Procedure..... | 112 | +| 7.2.5 | Test requirements..... | 112 | +| 7.2.5.1 | Test requirements for IAB-DU ..... | 112 | +| 7.2.5.2 | Test requirements for IAB-MT ..... | 114 | +| 7.3 | Dynamic range..... | 115 | +| 7.3.1 | Definition and applicability..... | 115 | +| 7.3.2 | Minimum requirement..... | 115 | +| 7.3.3 | Test purpose..... | 115 | +| 7.3.4 | Method of test..... | 115 | +| 7.3.4.1 | Initial conditions..... | 115 | +| 7.3.4.2 | Procedure..... | 115 | +| 7.3.5 | Test requirements..... | 116 | +| 7.4 | In-band selectivity and blocking..... | 119 | +| 7.4.1 | Adjacent Channel Selectivity (ACS)..... | 119 | +| 7.4.1.1 | Definition and applicability..... | 119 | +| 7.4.1.2 | Minimum requirement..... | 120 | +| 7.4.1.3 | Test purpose..... | 120 | +| 7.4.1.4 | Method of test..... | 120 | +| 7.4.1.4.1 | Initial conditions..... | 120 | +| 7.4.1.4.2 | Procedure..... | 120 | +| 7.4.1.5 | Test requirements..... | 120 | +| 7.4.1.5.1 | Test requirements for IAB-DU..... | 120 | +| 7.4.1.5.2 | Test requirements for IAB-MT..... | 121 | +| 7.4.2 | In-band blocking..... | 123 | +| 7.4.2.1 | Definition and applicability..... | 123 | +| 7.4.2.2 | Minimum requirement..... | 123 | +| 7.4.2.3 | Test purpose..... | 123 | +| 7.4.2.4 | Method of test..... | 123 | +| 7.4.2.4.1 | Initial conditions..... | 123 | +| 7.4.2.4.2 | Procedure for general blocking..... | 123 | +| 7.4.2.4.3 | Procedure for narrowband blocking..... | 124 | +| 7.4.2.5 | Test requirements..... | 124 | +| 7.4.2.5.1 | Test requirements for IAB-DU..... | 124 | +| 7.4.2.5.2 | Test requirements for IAB-MT..... | 126 | +| 7.5 | Out-of-band blocking..... | 128 | +| 7.5.1 | Definition and applicability..... | 128 | +| 7.5.2 | Minimum requirement..... | 128 | +| 7.5.3 | Test purpose..... | 129 | +| 7.5.4 | Method of test..... | 129 | +| 7.5.4.1 | Initial conditions..... | 129 | +| 7.5.4.2 | Procedure..... | 129 | +| 7.5.5 | Test requirements..... | 130 | +| 7.5.5.1 | General requirements for IAB-DU..... | 130 | +| 7.5.5.2 | Co-location requirements for IAB-DU..... | 130 | +| 7.5.5.3 | General requirements for IAB-MT..... | 131 | +| 7.5.5.4 | Co-location requirements for IAB-MT..... | 131 | +| 7.6 | Receiver spurious emissions..... | 132 | +| 7.6.1 | Definition and applicability..... | 132 | +| 7.6.2 | Minimum requirement..... | 132 | +| 7.6.3 | Test purpose..... | 133 | +| 7.6.4 | Method of test..... | 133 | + +| | | | +|-----------|---------------------------------------------------------------------------|-----| +| 7.6.4.1 | Initial conditions..... | 133 | +| 7.6.4.2 | Procedure..... | 133 | +| 7.6.5 | Test requirements..... | 133 | +| 7.6.5.1 | Basic limits for IAB-DU..... | 133 | +| 7.6.5.2 | Test requirement for IAB-DU..... | 134 | +| 7.6.5.3 | Basic limits for IAB-MT..... | 134 | +| 7.6.5.4 | Test requirement for IAB-MT..... | 135 | +| 7.7 | Receiver intermodulation..... | 135 | +| 7.7.1 | Definition and applicability..... | 135 | +| 7.7.2 | Minimum requirement..... | 135 | +| 7.7.3 | Test purpose..... | 136 | +| 7.7.4 | Method of test..... | 136 | +| 7.7.4.1 | Initial conditions..... | 136 | +| 7.7.4.2 | Procedure..... | 136 | +| 7.7.5 | Test requirements..... | 136 | +| 7.7.5.1 | IAB-DU ..... | 136 | +| 7.7.5.2 | IAB-MT ..... | 140 | +| 7.8 | In-channel selectivity..... | 142 | +| 7.8.1 | Definition and applicability..... | 142 | +| 7.8.2 | Minimum requirement..... | 143 | +| 7.8.3 | Test purpose..... | 143 | +| 7.8.4 | Method of test..... | 143 | +| 7.8.4.1 | Initial conditions..... | 143 | +| 7.8.4.2 | Procedure..... | 143 | +| 7.8.5 | Test requirements..... | 143 | +| 7.8.5.1 | IAB-DU ..... | 143 | +| 8 | Conducted performance requirements..... | 145 | +| 8.1 | IAB-DU performance requirements..... | 145 | +| 8.1.1 | General..... | 145 | +| 8.1.1.1 | Scope and definitions..... | 145 | +| 8.1.1.2 | Applicability rule..... | 146 | +| 8.1.1.2.1 | General..... | 146 | +| 8.1.1.2.2 | Applicability of PUSCH performance requirements..... | 146 | +| 8.1.1.2.3 | Applicability of PUCCH performance requirements..... | 147 | +| 8.1.1.2.4 | Applicability of PRACH performance requirements..... | 147 | +| 8.1.2 | Performance requirements for PUSCH..... | 148 | +| 8.1.2.1 | Performance requirements for PUSCH with transform precoding disabled..... | 148 | +| 8.1.2.1.1 | Definition and applicability..... | 148 | +| 8.1.2.1.2 | Minimum requirement..... | 148 | +| 8.1.2.1.3 | Test purpose..... | 148 | +| 8.1.2.1.4 | Method of test..... | 148 | +| 8.1.2.1.5 | Test requirement..... | 149 | +| 8.1.2.2 | Performance requirements for PUSCH with transform precoding enabled..... | 155 | +| 8.1.2.2.1 | Definition and applicability..... | 155 | +| 8.1.2.2.2 | Minimum requirement..... | 155 | +| 8.1.2.2.3 | Test purpose..... | 156 | +| 8.1.2.2.4 | Method of test..... | 156 | +| 8.1.2.2.5 | Test requirement..... | 157 | +| 8.1.2.3 | Performance requirements for UCI multiplexed on PUSCH..... | 158 | +| 8.1.2.3.1 | Definition and applicability..... | 158 | +| 8.1.2.3.2 | Minimum requirement..... | 158 | +| 8.1.2.3.3 | Test purpose..... | 158 | +| 8.1.2.3.4 | Method of test..... | 158 | +| 8.1.2.3.5 | Test requirement..... | 159 | +| 8.1.3 | Performance requirements for PUCCH..... | 160 | +| 8.1.3.1 | Performance requirements for PUCCH format 0..... | 160 | +| 8.1.3.1.1 | Definition and applicability..... | 160 | +| 8.1.3.1.2 | Minimum requirement..... | 161 | +| 8.1.3.1.3 | Test purpose..... | 161 | +| 8.1.3.1.4 | Method of test..... | 161 | +| 8.1.3.1.5 | Test requirement..... | 162 | + +| | | | +|-------------|--------------------------------------------------------------------------|-----| +| 8.1.3.2 | Performance requirements for PUCCH format 1..... | 162 | +| 8.1.3.2.1 | NACK to ACK detection..... | 162 | +| 8.1.3.2.2 | ACK missed detection..... | 164 | +| 8.1.3.3 | Performance requirements for PUCCH format 2..... | 167 | +| 8.1.3.3.1 | ACK missed detection..... | 167 | +| 8.1.3.3.2 | UCI BLER performance requirements..... | 168 | +| 8.1.3.4 | Performance requirements for PUCCH format 3..... | 170 | +| 8.1.3.4.1 | Definition and applicability..... | 170 | +| 8.1.3.4.2 | Minimum requirement..... | 170 | +| 8.1.3.4.3 | Test purpose..... | 170 | +| 8.1.3.4.4 | Method of test..... | 171 | +| 8.1.3.4.5 | Test requirement..... | 172 | +| 8.1.3.5 | Performance requirements for PUCCH format 4..... | 172 | +| 8.1.3.5.1 | Definition and applicability..... | 172 | +| 8.1.3.5.2 | Minimum requirement..... | 173 | +| 8.1.3.5.3 | Test purpose..... | 173 | +| 8.1.3.5.4 | Method of test..... | 173 | +| 8.1.3.5.5 | Test requirement..... | 174 | +| 8.1.3.6 | Performance requirements for multi-slot PUCCH..... | 175 | +| 8.1.3.6.1 | Performance requirements for multi-slot PUCCH format 1..... | 175 | +| 8.1.4 | Performance requirements for PRACH..... | 178 | +| 8.1.4.1 | PRACH false alarm probability and missed detection requirements..... | 178 | +| 8.1.4.1.1 | Definition and applicability..... | 178 | +| 8.1.4.1.2 | Minimum requirement..... | 179 | +| 8.1.4.1.3 | Test purpose..... | 179 | +| 8.1.4.1.4 | Method of test..... | 179 | +| 8.1.4.1.5 | Test requirement..... | 180 | +| 8.2 | IAB-MT Performance requirements..... | 181 | +| 8.2.1 | General..... | 181 | +| 8.2.1.1 | Scope and definitions..... | 181 | +| 8.2.2 | Demodulation performance requirements..... | 182 | +| 8.2.2.1 | General..... | 182 | +| 8.2.2.1.1 | Applicability of requirements..... | 182 | +| 8.2.2.2 | Performance requirements for PDSCH..... | 183 | +| 8.2.2.2.1 | Definition and applicability..... | 183 | +| 8.2.2.2.2 | Minimum requirement..... | 183 | +| 8.2.2.2.3 | Test purpose..... | 183 | +| 8.2.2.2.4 | Method of test..... | 183 | +| 8.2.2.2.5 | Test requirement..... | 185 | +| 8.2.2.3 | Performance requirements for PDCCH..... | 185 | +| 8.2.2.3.1 | Definition and applicability..... | 185 | +| 8.2.2.3.2 | Minimum requirement..... | 185 | +| 8.2.2.3.3 | Test purpose..... | 186 | +| 8.2.2.3.4 | Method of test..... | 186 | +| 8.2.2.3.5 | Test requirement..... | 186 | +| 8.2.3 | CSI reporting requirements..... | 187 | +| 8.2.3.1 | General..... | 187 | +| 8.2.3.1.1 | Applicability rule for IAB-MT..... | 187 | +| 8.2.3.1.1.1 | General..... | 187 | +| 8.2.3.1.1.2 | Applicability of requirements for different subcarrier spacings..... | 187 | +| 8.2.3.1.1.3 | Applicability of requirements for TDD with different UL-DL patterns..... | 187 | +| 8.2.3.1.1.4 | Applicability of requirements for IAB-MT features..... | 187 | +| 8.2.3.1.2 | Common test parameters..... | 187 | +| 8.2.3.2 | Reporting Channel Quality Indicator (CQI)..... | 188 | +| 8.2.3.2.1 | Definition and applicability..... | 188 | +| 8.2.3.2.2 | Minimum requirement..... | 189 | +| 8.2.3.2.3 | Test purpose..... | 189 | +| 8.2.3.2.4 | Method of test..... | 189 | +| 8.2.3.2.5 | Test requirement..... | 190 | +| 8.2.3.3 | Reporting of Precoding Matrix Indicator (PMI)..... | 190 | +| 8.2.3.3.1 | Definition and applicability..... | 190 | + +| | | | +|-----------|---------------------------------------|-----| +| 8.2.3.3.2 | Minimum requirement..... | 191 | +| 8.2.3.3.3 | Test purpose..... | 191 | +| 8.2.3.3.4 | Method of test..... | 191 | +| 8.2.3.3.5 | Test requirement..... | 192 | +| 8.2.3.4 | Reporting of Rank Indicator (RI)..... | 193 | +| 8.2.3.4.1 | General..... | 193 | +| 8.2.3.4.2 | Minimum requirements..... | 193 | +| 8.2.3.4.3 | Test purpose..... | 193 | +| 8.2.3.4.4 | Method of test..... | 193 | +| 8.2.3.4.5 | Test requirement..... | 194 | + +**Annex A (normative): Reference measurement channels..... 196** + +| | | | +|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| A.1 | IAB-DU and IAB-MT Reference measurement channels..... | 196 | +| A.1.1 | IAB-DU Reference measurement channels..... | 196 | +| A.1.2 | IAB-MT Reference measurement channels..... | 196 | +| 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)..... | 196 | +| A.2 | IAB-DU Fixed Reference Channels..... | 196 | +| A.2.1 | Fixed Reference Channels for PUSCH performance requirements (QPSK, R = 193/1024)..... | 196 | +| A.2.2 | Fixed Reference Channels for PUSCH performance requirements (16QAM, R=434/1024)..... | 198 | +| A.2.3 | Fixed Reference Channels for PUSCH performance requirements (16QAM, R = 658/1024)..... | 198 | +| A.2.4 | Fixed Reference Channels for PUSCH performance requirements (64QAM, R = 567/1024)..... | 199 | +| A.2.5 | PRACH test preambles..... | 200 | +| A.3 | IAB-MT Fixed Reference Channels..... | 200 | +| A.3.1 | Fixed Reference Channels for PDSCH performance requirements (16QAM)..... | 200 | +| A.3.2 | Fixed Reference Channels for PDSCH performance requirements (64QAM)..... | 201 | +| A.3.3 | Fixed Reference Channels for PDSCH performance requirements (256QAM)..... | 201 | +| A.3.4 | Fixed Reference Channels for PDCCH performance requirements..... | 202 | +| A.3.5 | Fixed Reference Channels for CSI reporting performance requirements..... | 202 | + +**Annex B (normative): Environmental requirements for the IAB equipment..... 204** + +| | | | +|-------|---------------------------------------|-----| +| B.1 | General..... | 204 | +| B.2 | Normal test environment..... | 204 | +| B.3 | Extreme test environment..... | 204 | +| B.3.1 | General..... | 204 | +| B.3.2 | Extreme temperature..... | 204 | +| B.4 | Vibration..... | 205 | +| B.5 | Power supply..... | 205 | +| B.6 | Measurement of test environments..... | 205 | + +**Annex C (informative): Test tolerances and derivation of test requirements..... 207** + +| | | | +|-------|----------------------------------------------|-----| +| C.1 | Measurement of transmitter..... | 207 | +| C.2 | Measurement of receiver..... | 209 | +| C.3 | Measurement of performance requirements..... | 210 | +| C.3.1 | List IAB-DU TTs..... | 210 | +| C.3.2 | List IAB-MT TTs..... | 210 | + +**Annex D (informative): Measurement system set-up..... 211** + +| | | | +|-------|-----------------------------------------------------------------------------------------------------------------------------------|-----| +| D.1 | IAB type 1-H transmitter..... | 211 | +| D.1.1 | IAB output power, output power dynamics, transmitter ON/OFF power, frequency error, EVM, unwanted emissions for IAB type 1-H..... | 211 | + +| | | | +|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|------------| +| D.1.2 | Transmitter intermodulation for IAB type 1-H..... | 212 | +| D.1.3 | Transmitter spurious emissions for IAB type 1-H..... | 213 | +| D.1.4 | Time alignment error for IAB-DU ..... | 214 | +| D.2 | IAB type 1-H receiver..... | 215 | +| D.2.1 | Reference sensitivity level for IAB type 1-H..... | 215 | +| D.2.2 | Receiver dynamic range for IAB type 1-H..... | 215 | +| D.2.3 | Receiver adjacent channel selectivity and narrowband blocking for IAB type 1-H..... | 216 | +| D.2.4 | Receiver spurious emissions..... | 216 | +| D.2.5 | Receiver In-channel selectivity for IAB type 1-H..... | 218 | +| D.2.6 | Receiver intermodulation for IAB type 1-H..... | 218 | +| D.3 | IAB type 1-H performance requirements..... | 219 | +| D.3.1 | Performance requirements for PUSCH and PUCCH on single antenna port in multipath fading conditions..... | 219 | +| D.3.2 | Performance requirements for PUSCH, PDSCH, PDCCH transmission and PMI/RI reporting on two antenna ports in multipath fading conditions..... | 220 | +| D.3.3 | Performance requirements for PUSCH, PRACH transmission and CQI reporting in static conditions..... | 221 | +| Annex E (normative): | Characteristics of interfering signals..... | 222 | +| E.1 | Characteristics of the interfering signals for IAB-DU..... | 222 | +| E.2 | Characteristics of the interfering signals for IAB-MT..... | 222 | +| Annex F (normative): | Propagation conditions..... | 223 | +| F.1 | Static propagation condition..... | 223 | +| F.1.1 | IAB-MT receiver with 2RX..... | 223 | +| F.2 | Multi-path fading propagation conditions..... | 223 | +| F.2.1 | General..... | 223 | +| F.2.2 | Delay profiles..... | 223 | +| F.2.2.1 | General..... | 223 | +| F.2.2.2 | Delay profiles for FR1..... | 225 | +| F.2.3 | Combinations of channel model parameters..... | 226 | +| F.2.4 | MIMO channel correlation matrices..... | 226 | +| F.2.4.1 | General..... | 226 | +| F.2.4.2 | MIMO correlation matrices using Uniform Linear Array..... | 226 | +| F.2.4.2.1 | General..... | 226 | +| F.2.4.2.2 | Definition of MIMO correlation matrices..... | 226 | +| F.2.4.2.3 | MIMO correlation matrices at high, medium and low level..... | 228 | +| F.2.4.3 | Multi-antenna channel models using cross polarized antennas..... | 230 | +| F.2.4.3.1 | General..... | 230 | +| F.2.4.3.2 | Definition of MIMO correlation matrices using cross polarized antennas..... | 230 | +| F.2.4.3.3 | Spatial correlation matrices at UE/IAB-MT and IAB-DU/gNB sides..... | 231 | +| F.2.4.3.3.1 | Spatial correlation matrices at IAB-MT/UE side..... | 231 | +| F.2.4.3.3.2 | Spatial correlation matrices at IAB-DU/gNB side..... | 231 | +| F.2.4.3.4 | MIMO correlation matrices using cross polarized antennas..... | 231 | +| F.2.4.3.5 | Beam steering approach..... | 232 | +| Annex G (normative): | In-channel TX tests for IAB-DU..... | 234 | +| Annex H (normative): | In-channel TX tests for IAB-MT..... | 235 | +| H.0 | Applicability..... | 235 | +| H.1 | General..... | 235 | +| H.2 | Basic principles..... | 235 | +| H.2.1 | Output signal of the TX under test..... | 235 | +| H.2.2 | Ideal signal..... | 235 | +| H.2.3 | Measurement results..... | 236 | + +| | | | +|---------------------------------------------------|-----------------------------------|------------| +| H.2.4 | Measurement points..... | 236 | +| H.3 | Pre-FFT minimization process..... | 237 | +| H.4 | Timing of the FFT window..... | 237 | +| H.5 | Resource element TX power..... | 238 | +| H.6 | Post-FFT equalisation..... | 239 | +| H.7 | EVM..... | 240 | +| H.7.0 | General..... | 240 | +| H.7.1 | Averaged EVM (TDD)..... | 241 | +| Annex I (informative): Change history..... | | 242 | + +## Foreword + +This clause is mandatory; do not alter the text in any way other than to choose between "Specification" and "Report". + +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 Integrated access and backhaul (IAB). + +The present document specifies the Radio Frequency (RF) test methods and conformance requirements for NR Integrated access and backhaul (IAB) type 1-H. These have been derived from, and are consistent with the conducted requirements for NR Integrated access and backhaul (IAB) type 1-H in NR Integrated access and backhaul specification defined in TS 38.174 [2]. + +An *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-2 [3]. + +*IAB type 1-O* and *IAB type 2-O* have only radiated requirements so they require compliance to TS 38.176-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.174: "NR Integrated access and backhaul radio transmission and reception". +- [3] 3GPP TS 38.176-2: " NR; Integrated Access and Backhaul (IAB) conformance testing; Part 2: Radiated conformance testing". +- [4] Recommendation ITU-R M.1545: "Measurement uncertainty as it applies to test limits for the terrestrial component of International Mobile Telecommunications-2000". +- [5] Recommendation ITU-R SM.329: "Unwanted emissions in the spurious domain". +- [6] Recommendation ITU-R SM.328: "Spectra and bandwidth of emissions". +- [7] "Title 47 of the Code of Federal Regulations (CFR)", Federal Communications Commission. +- [8] 3GPP TR 25.942: "RF system scenarios" +- [9] 3GPP TS 38.211: "NR; Physical channels and modulation" +- [10] 3GPP TS 38.212: "NR; Multiplexing and channel coding" +- [11] 3GPP TS 38.104: "NR Base Station (BS) radio transmission and reception" +- [12] 3GPP TS 38.213: "NR; Physical layer procedures for control". +- [13] 3GPP TS 38.141-1: "NR; Base Station (BS) conformance testing; Part 1: Conducted conformance testing". +- [14] 3GPP TS 38.331: "NR; Radio Resource Control (RRC); Protocol specification". +- [15] Recommendation ITU-T O.150, "Equipment for the measurement of digital and analogue/digital parameters" + +- [16] 3GPP TS 38.521-1: "NR; User Equipment (UE) conformance specification; Radio transmission and reception; Part 1: Range 1 Standalone". +- [17] 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" +- [18] 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" +- [19] IEC 60 721: "Classification of environmental conditions" +- [20] IEC 60 068-2-1 (2007): "Environmental testing - Part 2: Tests. Tests A: Cold" +- [21] IEC 60 068-2-2: (2007): "Environmental testing - Part 2: Tests. Tests B: Dry heat" +- [22] IEC 60 068-2-6: (2007): "Environmental testing - Part 2: Tests - Test Fc: Vibration (sinusoidal)" +- [23] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone" +- [24] 3GPP TS 38.214: "NR; Physical layer procedures for data" +- [25] 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 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]. + +**aggregated IAB channel bandwidth:** the RF bandwidth in which a IAB-DU and/or IAB-MT transmits and receives multiple contiguously aggregated carriers. The *aggregated IAB channel bandwidth* is measured in MHz + +**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* + +**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 + +**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. + +**Channel edge:** lowest or highest frequency of the NR carrier, separated by the *IAB-MT channel bandwidth* or *IAB-DU 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 IAB-DU or IAB-MT aggregates carriers with a specific set of technical requirements + +**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)*. + +**fractional bandwidth:** *fractional bandwidth* FBW is defined as + +**highest carrier:** The carrier with the highest carrier frequency transmitted/received in a specified frequency band. + +**IAB-donor:** gNB that provides network access to UEs via a network of backhaul and access links. + +**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 UE bandwidth parts that are smaller than or equal to the *IAB transmission bandwidth configuration*, in any part of the *IAB transmission bandwidth configuration*. + +**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 + +**measurement bandwidth:** RF bandwidth in which an emission level is specified + +**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 + +**Parent node:** IAB-MT's next hop neighbour node; the parent node can be IAB-node or IAB-donor. + +**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 requirement sets as defined for *IAB type 1-H*, *IAB type 1-O*, and *IAB type 2-O* + +**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 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 + +**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 | +| $BW_{\text{Channel}}$ | IAB-DU channel bandwidth or IAB-MT channel bandwidth | +| $BW_{\text{Channel\_CA}}$ | aggregated IAB channel bandwidth , expressed in MHz. $BW_{\text{Channel\_CA}} = F_{\text{edge\_high}} - F_{\text{edge\_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{max}}$ | $f_{\text{offset\_max}}$ minus half of the bandwidth of the measuring filter | +| $\Delta f_{\text{OBUE}}$ | Maximum offset of the operating band unwanted emissions mask from the downlink operating band edge | +| $\Delta f_{\text{OOB}}$ | Maximum offset of the out-of-band boundary from the uplink operating band edge | +| $F_{\text{C}}$ | 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 IAB 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 IAB channel bandwidth , expressed in MHz. $F_{\text{edge\_high}} = F_{\text{C\_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{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 | +| $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 IAB type 1-H in a particular operating band | +| $N_{\text{RB}}$ | Transmission bandwidth configuration, expressed in resource blocks | +| $N_{\text{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_{\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{max,c,TABC}}$ | The maximum carrier output power per TAB 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,TABC}}$ | The rated total output power declared at TAB connector | + +| | | +|----------------------|----------------------------------------------| +| P REFSENS | Conducted Reference Sensitivity power level | +| W 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]. + +| | | +|------------|------------------------------------------------------------------------| +| 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 | +| GSM | Global System for Mobile communications | +| ITU-R | Radiocommunication Sector of the International Telecommunication Union | +| IAB | Integrated Access and Backhaul | +| IAB-DU | IAB Distribution Unit | +| IAB-MT | IAB Mobile Termination | +| ICS | In-Channel Selectivity | +| LA | Local Area | +| 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 | +| 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 | +| TX | Transmitter | +| TT | Test Tolerance | +| UCI | Uplink Control Information | +| WA | Wide Area | +| 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 the present document, i.e. to all conducted tests defined for FR1. 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] 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 *IAB type 1-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 IAB output power | ±0.7 dB, $f \leq 3$ GHz
±1.0 dB, $3$ GHz $< f \leq 6$ GHz (Note) | | +| 6.3.1 IAB-DU Output power dynamics | ± 0.4 dB | | +| 6.3.2 IAB-MT Output power dynamics | ±0.7 dB, $BW \leq 40$ MHz
±1.0 dB, $40$ MHz $< f \leq 100$ MHz | | +| 6.4.1 Transmit OFF power | ±2.0 dB, $f \leq 3$ GHz
±2.5 dB, $3$ GHz $< f \leq 6$ GHz (Note) | | +| 6.4.2 Transmitter transient period | N/A | | +| 6.5.2.1 IAB-DU Frequency error | ± 12 Hz | | +| 6.5.2.2 IAB-MT Frequency error | ±15 Hz, $f \leq 3.0$ GHz
±36 Hz, $f > 3.0$ GHz | | +| 6.5.3 EVM | ± 1% | | +| 6.5.4 Time alignment error | ± 25 ns | | +| 6.6.5 Timing error between IAB-DU and IAB-MT | ± 25 ns | | +| 6.6.2 Occupied bandwidth | 10 MHz IAB Channel BW: ±100 kHz
15 MHz, 20 MHz, 25 MHz, 30 MHz, 40 MHz, 50 MHz IAB Channel BW: ±300 kHz
60 MHz, 70 MHz, 80 MHz, 90 MHz, 100 MHz IAB 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 6$ GHz (Note)

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 6$ GHz (Note) | | +| 6.6.4 Operating band unwanted emissions | ±1.5 dB, $f \leq 3$ GHz
±1.8 dB, $3$ GHz $< f \leq 6$ GHz (Note) | | +| 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, 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 6$ 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 6$ GHz | | +| 6.6.5.2.3 Transmitter spurious emissions, Co-location | ±3.0 dB | | +| 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.

±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$ GHz $< f \leq 6$ GHz apply for IAB 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 | | +| 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) |

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

f \leq 6 GHz
Impact of interferer leakage 0.4 dB

| + +| | | | +|------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 7.4.2 In-band blocking (General blocking) | ±1.6 dB, $f \leq 3$ GHz
±2.0 dB, $3$ GHz $< f \leq 4.2$ GHz
±2.2 dB, $4.2$ GHz $< f \leq 6$ GHz (NOTE 2) | | +| 7.4.2 In-band blocking (Narrow band blocking) | ±1.4 dB, $f \leq 3$ GHz
±1.8 dB, $3$ GHz $< f \leq 4.2$ GHz
±2.1 dB, $4.2$ GHz $< f \leq 6$ GHz (NOTE 2) | | +| 7.5.5.1, 7.5.5.3 Out-of-band blocking (General requirements) | $f_{wanted} \leq 3$ GHz
$1$ MHz $< f_{interferer} \leq 3$ GHz: ±1.3 dB
$3.0$ GHz $< f_{interferer} \leq 4.2$ GHz: ±1.5 dB
$4.2$ GHz $< f_{interferer} \leq 12.75$ GHz: ±3.2 dB

$3$ GHz $< f_{wanted} \leq 4.2$ GHz:
$1$ MHz $< f_{interferer} \leq 3$ GHz: ±1.5 dB
$3.0$ GHz $< f_{interferer} \leq 4.2$ GHz: ±1.7 dB
$4.2$ GHz $< f_{interferer} \leq 12.75$ GHz: ±3.3 dB

$4.2$ GHz $< f_{wanted} \leq 6.0$ GHz:
$1$ MHz $< f_{interferer} \leq 3$ GHz: ±1.7 dB
$3.0$ GHz $< f_{interferer} \leq 4.2$ GHz: ±1.8 dB
$4.2$ GHz $< f_{interferer} \leq 12.75$ GHz: ±3.3 dB | Overall system uncertainty comprises three quantities:

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

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

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

Out of band blocking, using CW interferer:
Wanted signal level:
±0.7 dB up to 3 GHz
±1.0 dB up to 4.2 GHz
±1.22 dB up to 6 GHz

Interferer signal level:
±1.0 dB up to 3 GHz
±1.2 dB up to 4.2 GHz
±3.0 dB up to 12.75 GHz
Impact of interferer Broadband noise 0.1 dB | +| 7.5.5.2, 7.5.5.4 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 | Co-location blocking, using CW interferer:
$f \leq 3.0$ GHz
Wanted signal level ± 0.7 dB
$3.0$ GHz $< f \leq 4.2$ GHz
Wanted signal level ± 1.0 dB
$4.2$ GHz $< f \leq 6.0$ GHz
Wanted signal level ± 1.22 dB

$f \leq 6.0$ GHz
Interferer signal level:
± 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: ±2.0 dB
$4$ GHz $< f \leq 19$ GHz: ±4.0 dB
$19$ GHz $< f \leq 26$ GHz: ±4.5 dB | | +| 7.7 Receiver intermodulation | ±1.8 dB, $f \leq 3.0$ GHz
±2.4 dB, $3.0$ GHz $< f \leq 4.2$ GHz
±3.0 dB, $4.2$ GHz $< f \leq 6.0$ GHz (NOTE 2) | Overall system uncertainty comprises four quantities:

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

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

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

Test System uncertainty = $\sqrt{(2 \times}$ | + +| | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | $(CW\_level\_error)^2 + (mod\_interferer\_level\_error)^2 + (wanted\_signal\_level\_error)^2] + 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
$f \leq 6$ GHz
Impact of interferer ACLR 0.4 dB | +| 7.8 In-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) | | +| 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$ GHz $< f \leq 6$ GHz apply for IAB 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.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. 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 $\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 | + +### 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 IAB type 1-H + +*IAB type 1-H* requirements are defined for two points of reference, signified by radiated requirements and conducted requirements. + +![Diagram of Radiated and conducted reference points for IAB type 1-H. The diagram shows a Transceiver unit array (TRXUA) with multiple units (#1, #2, ..., #K) connected to a Transceiver array boundary connector (TAB). The TAB is connected to a Composite antenna, which contains a Radio Distribution Network (RDN) and an Antenna Array (AA). The Radiated interface boundary (RIB) is shown as a dashed line to the right of the Composite antenna.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +The diagram illustrates the internal structure of an IAB type 1-H node. On the left, a dashed box labeled 'Transceiver unit array (TRXUA) 1 to M' contains multiple transceiver units labeled #1, #2, ..., #K. Each unit is connected to a vertical line representing the 'Transceiver array boundary'. At the bottom of this boundary, a connector labeled 'Transceiver array boundary connector (TAB)' is shown. To the right of the TAB, another dashed box labeled 'Composite antenna' contains two sub-components: 'Radio Distribution Network (RDN)' and 'Antenna Array (AA)'. A vertical dashed line to the right of the antenna array is labeled 'Radiated interface boundary (RIB)'. + +Diagram of Radiated and conducted reference points for IAB type 1-H. The diagram shows a Transceiver unit array (TRXUA) with multiple units (#1, #2, ..., #K) connected to a Transceiver array boundary connector (TAB). The TAB is connected to a Composite antenna, which contains a Radio Distribution Network (RDN) and an Antenna Array (AA). The Radiated interface boundary (RIB) is shown as a dashed line to the right of the Composite antenna. + +**Figure 4.2.1-1: Radiated and conducted reference points for IAB 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.176-2 [3] and are out of scope of the present document. + +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 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. For *IAB type 1-H*, 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 coupling loss equal to 70 dB. +- Medium Range IAB-DU are characterised by requirements derived from Micro Cell scenarios with a BS to UE minimum coupling loss equals to 53 dB. +- Local Area IAB-DU are characterised by requirements derived from Pico Cell scenarios with a BS to UE minimum coupling loss equal to 45 dB. + +### 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-H*, 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 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.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. | +| 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.4.2 | Operating band unwanted emission | Category A or Category B operating band unwanted emissions limits may be applied regionally. | +| 6.6.4.2.5.1 | Operating band unwanted emission | 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. | +| 6.6.5.2.1, | Tx spurious emissions, | Category A or Category B spurious emission limits, as defined in Recommendation ITU-R SM.329 [5], may apply regionally.
The emission limits for IAB type 1-H specified as the basic limit + X (dB) are applicable, unless stated differently in regional regulation. | +| 6.6.5.2.2, | Tx spurious emissions:
additional requirements,
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 . | +| 6.7.2.1 | 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. | +| 7.6.2,
7.6.3 | Rx spurious emissions, | The emission limits for IAB type 1-H specified as the basic limit + X (dB) are applicable, unless stated differently in regional regulation. | + +## 4.5 IAB configurations + +### 4.5.1 IAB type 1-H + +#### 4.5.1.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. + +![Figure 4.5.1.1-1: Transmitter test ports diagram](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +The diagram illustrates the transmitter test ports for a transceiver unit array. A dashed box on the left represents the 'transceiver unit array'. A vertical dashed line to its right marks the 'transceiver array boundary'. At this boundary, there are multiple ports labeled #1, #2, ..., #K. Port #1 is connected to a 'Measurement Equipment' block. Port #2 is connected to a 'Load' block. Port #K is also connected to a 'Load' block. An arrow points to the boundary line with the label 'Transceiver array boundary connector TAB(n)'. + +Figure 4.5.1.1-1: Transmitter test ports diagram + +**Figure 4.5.1.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.1.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. + +![Figure 4.5.1.2-1: Receiver test ports diagram](dc1f232cfd39be5c20b21374ad4c04c0_img.jpg) + +The diagram illustrates the receiver test ports for a transceiver unit array. A dashed box on the left represents the 'transceiver unit array'. A vertical dashed line to its right marks the 'transceiver array boundary'. At this boundary, there are multiple ports labeled #1, #2, ..., #K. Port #1 is connected to a 'Measurement Equipment' block, with an arrow pointing from the equipment to the port. Port #2 is connected to a 'Load' block. Port #K is also connected to a 'Load' block. An arrow points to the boundary line with the label 'Transceiver array boundary connector TAB(n)'. + +Figure 4.5.1.2-1: Receiver test ports diagram + +**Figure 4.5.1.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 units(s) disabled or their *TAB connector(s)* being terminated. + +#### 4.5.1.3 Power supply options + +If the *IAB 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.2 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. 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 *IAB type 1-H* declarations listed in table 4.6-1, when applicable to the IAB-DU or IAB-MT under test, are required to be provided by the manufacturer for the conducted requirements testing of the *IAB type 1-H*. Declarations may be provided independently for IAB-MT and IAB-DU. + +For the *IAB type 1-H* declarations required for the radiated requirements testing, refer to TS 38.176-2 [3]. + +**Table 4.6-1 Manufacturer declarations for IAB-type 1-H conducted test requirements** + +| Declaration identifier | Declaration | Description | Applicability | | +|------------------------|---------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-----------------| +| | | | IAB-DU type 1-H | IAB-MT type 1-H | +| D.1 | IAB requirements set | Declaration of one of the IAB requirement's set as defined for IAB type 1-H . | x | x | +| D.2 | IAB class | IAB class of the IAB, declared as Wide Area IAB, Medium Range IAB, or Local Area IAB. | 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 IAB-DU or IAB-MT and if applicable, frequency range(s) within the operating band(s) that the IAB can operate in. Declarations shall be made per TAB connector for IAB type 1-H . | x | x | +| D.4 | 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]. | x | x | +| D.5 | Additional operating band unwanted emissions | The manufacturer shall declare whether the IAB-DU or IAB-MT under test is intended to operate in geographic areas where the additional operating band unwanted emission limits defined in clause 6.6.4.5 apply. | x | x | +| D.6 | Co-existence with other systems | The manufacturer shall declare whether the IAB-DU or IAB-MT 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 IAB | The manufacturer shall declare whether the IAB-DU or IAB-MT under test is intended to operate co-located with IAB 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 | | | +| D.11 | Maximum IAB RF Bandwidth | Maximum IAB RF Bandwidth in the operating band for single-band operation. Declared per supported operating band, per TAB connector for IAB type 1-H . (Note 2) | x | x | + +| Declaration identifier | Declaration | Description | Applicability | | +|------------------------|---------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-----------------| +| | | | IAB-DU type 1-H | IAB-MT type 1-H | +| D.12 | Maximum IAB RF Bandwidth for multi-band operation | Maximum IAB RF Bandwidth for multi-band operation. Declared per supported operating band, per TAB connector for IAB 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 TAB connector for IAB 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 TAB connector for IAB 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 TAB connector for IAB type 1-H. | x | x | + +| Declaration identifier | Declaration | Description | Applicability | | +|------------------------|-----------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-----------------| +| | | | IAB-DU type 1-H | IAB-MT type 1-H | +| 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 TAB connector for IAB 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.38) 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_{\text{rated,c,AC}}$ , or $P_{\text{rated,c,TABC}}$ ) | Conducted rated carrier output power, per single band connector or multi-band connector . Declared per supported operating band , per TAB connector for IAB type 1-H. (Note 1, 2) | x | x | +| D.22 | Rated total output power ( $P_{\text{rated,t,AC}}$ , or $P_{\text{rated,t,TABC}}$ ) | Conducted total rated output power. Declared per supported operating band , per TAB connector for IAB type 1-H. For multi-band connectors declared for each supported operating band in each supported band combination. (Note 1, 2) | x | x | +| D.23 | 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) | x | x | +| D.24 | $N_{\text{cells}}$ | Number corresponding to the minimum number of cells that can be transmitted by a IAB in a particular operating band with transmission on all TAB connectors supporting the operating band . | x | x | +| D.25 | Maximum supported power difference between carriers | Maximum supported power difference between carriers. Declared per supported operating band , per TAB connector for IAB type 1-H. (Note 3). | 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 IAB. Declared per TAB connector for IAB type 1-H. | x | x | +| D.28 | void | void | | | +| 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 | x | +| D.30 | Intra-system interfering signal level | The interfering signal level in dBm. Declared per supported operating band , per TAB connector for IAB type 1-H covered by D.29. | x | x | + +| Declaration identifier | Declaration | Description | Applicability | | +|------------------------|--------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-----------------| +| | | | IAB-DU type 1-H | IAB-MT type 1-H | +| 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 TAB connector of IAB type 1-H , which have been declared equivalent. Equivalent connectors imply that the TAB connector of IAB 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 TAB connector of IAB type 1-H are identical and the transmitter unit and/or receiver unit driving the TAB connector of IAB 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 IAB 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 | 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 IAB 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 | x | +| D.35 | void | void | | | +| 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 | 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 TAB connector for IAB type 1-H . | x | x | + +| Declaration identifier | Declaration | Description | Applicability | | +|------------------------|---------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-----------------| +| | | | IAB-DU type 1-H | IAB-MT type 1-H | +| 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 or TAB connector for IAB type 1-H.. | x | x | +| D.41 | void | void | | | +| D.42 | void | void | | | +| D.43 | void | void | | | +| D.IAB-1 | Same RF implementation. | Declaration whether IAB-MT and IAB-DU have same RF implementation. | x | x | +| D.IAB-2 | IAB simultaneous operation | Declare support of IAB simultaneous operation, simultaneous transmission, or simultaneous reception or both. | x | x | +| D.IAB-3 | 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 | x | x | +| D.100 | PUSCH mapping type | Declaration of the supported PUSCH mapping type as specified in TS 38.211 [9], i.e., type A, type B or both. | x | | +| D.101 | PUSCH additional DM-RS positions | Declaration of the supported additional DM-RS position(s), i.e., pos0, pos1 or both. | x | | +| D.102 | PUCCH format | Declaration of the supported PUCCH format(s) as specified in TS 38.211 [9], i.e., format 0, format 1, format 2, format 3, format 4. | x | | +| D.103 | PRACH format and SCS | Declaration of the supported PRACH format(s) as specified in TS 38.211 [9], 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 [9], i.e., 15 kHz, 30 kHz or both. | 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 | | +| 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 | | +| D.106 | PUCCH multi-slot | Declaration of multi-slot PUCCH support. | 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 | | +| D.108 | Modulation order | Declaration of the supported modulation order, i.e. QPSK, 16QAM, 64QAM | x | | +| D.109 | DFT-s-OFDM | Declaration of the supported DFT-s-OFDM, i.e. supported or not supported. | x | | +| D.200 | 256QAM for PDSCH for FR1 | Declaration of the supported 256QAM modulation scheme for PDSCH for FR1, i.e. supported or not supported. | | x | +| 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. | | x | +| D.202 | Maximum number of PDSCH MIMO layers | Declaration of the the maximum number of spatial multiplexing layer(s) supported by the IAB-MT for DL reception, i.e. 2, 4, 8 or not supported. | | x | + +| Declaration identifier | Declaration | Description | Applicability | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------|-----------------|-----------------|--|--| +| | | | IAB-DU type 1-H | IAB-MT type 1-H | | | +| NOTE 1: If an IAB-DU or IAB-MT 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 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: The power difference is declared at highest rated output power. | | | | | | | +| NOTE 4: 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 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 IAB Test Configurations shall be selected according to table 4.7.2-1. + +**Table 4.7.2-1: Signal to be used to build IAB TCs** + +| Operating Band characteristics | | $F_{DL\_high} - F_{DL\_low} < 100$ MHz | $F_{DL\_high} - F_{DL\_low} \geq 100$ MHz | +|--------------------------------------------------------------------------------------------------------------|-----------------------|----------------------------------------|-------------------------------------------| +| TC signal characteristics | BW channel | 10 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 IABTC1: Contiguous spectrum operation + +#### 4.7.3.1 General + +The purpose of test configuration IABTC1 is to test all IAB 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.3.2 IABTC1 generation + +IABTC1 shall be constructed on a per band basis using the following method: + +- Declared maximum IAB RF Bandwidth supported for contiguous spectrum operation (D.11) shall be used; + +- For IAB not supporting simultaneous transmission between IAB-DU and IAB-MT, select the IAB carrier to be tested according to 4.7.2 and place it adjacent to the lower IAB RF Bandwidth edge. Place same signals adjacent to the upper 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 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 IAB RF Bandwidth edge. +- For transmitter tests, select as many IAB carriers (according to 4.7.2) that the IAB supports within an *operating band* and fit in the rest of the declared maximum IAB RF Bandwidth (D.11). Place the carriers adjacent to each other starting from the upper IAB RF Bandwidth edge. The nominal channel spacing defined in TS 38.174 [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 IAB and are transmitted using the same *TAB connector*. All configured component carriers are transmitted simultaneously in the tests where the transmitter should be ON. + +#### 4.7.3.3 IABTC1 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) for IAB according to the manufacturer's declaration in clause 4.6. + +### 4.7.4 IABTC2: Contiguous CA occupied bandwidth + +#### 4.7.4.1 General + +IABTC2 in this clause is used to test CA occupied bandwidth. + +#### 4.7.4.2 IABTC2 generation + +The CA specific test configuration should be constructed on a per band basis using the following method: + +- All component carrier combinations supported by the IAB, which have different sum of channel bandwidth of component carrier, shall be tested. For all component carrier combinations which have the same sum of channel bandwidth of component carriers, only one of the component carrier combinations shall be tested. +- Of all component carrier combinations which have same sum of channel bandwidth of component carrier, select those with the narrowest carrier with the smallest supported subcarrier spacing 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 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 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.174 [2], clause 5.4.1 shall apply. + +#### 4.7.4.3 IABTC2 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 IAB according to the manufacturer's declaration in clause 4.6. + +#### 4.7.5 IABTC3: Non-contiguous spectrum operation + +##### 4.7.5.1 General + +The purpose of IABTC3 is to test all IAB requirements excluding CA occupied bandwidth. + +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.5.2 IABTC3 generation + +IABTC3 is constructed on a per band basis using the following method: + +- For IAB not supporting simultaneous transmission between IAB-DU and IAB-MT, select the IAB carrier to be tested according to clause 4.7.2. Place it adjacent to the upper IAB RF Bandwidth edge and another carrier (as described in clause 4.7.2) 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 and place it adjacent to the already placed IAB UL carrier at the upper IAB RF Bandwidth edge. Place the same IAB DL carrier adjacent to the already placed IAB UL carrier at the lower IAB RF Bandwidth edge. +- 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 IAB 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.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.5.3 IABTC3 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) for IAB according to the manufacturer's declaration in clause 4.6. + +#### 4.7.6 IABTC4: Multi-band test configuration for full carrier allocation + +##### 4.7.6.1 General + +The purpose of IABTC4 is to test multi-band operation aspects considering maximum supported number of carriers. + +##### 4.7.6.2 IABTC4 generation + +IABTC4 is based on re-using the previously specified test configurations (IABTC1, IABTC2 and IABTC3) applicable per band involved in multi-band operation. It is constructed using the following method: + +- The IAB RF Bandwidth of each supported operating band shall be the declared maximum IAB 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 IAB RF Bandwidths edges, if possible. + +- The allocated IAB 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 IABTC1, 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 IAB RF Bandwidths of each supported *operating bands* is larger than the declared *Total RF Bandwidth* BWtot (D.13) of transmitter and receiver for the declared band combinations of the IAB, repeat the steps above for test configurations where the IAB 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.3 IABTC4 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 (Prated,t,AC or Prated,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 IABTC5: Multi-band test configuration with high PSD per carrier + +##### 4.7.7.1 General + +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.7.2 IABTC5 generation + +IABTC5 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 IAB RF Bandwidth of each supported *operating band* shall be the declared maximum IAB RF Bandwidth in multi-band operation (D.12). +- The allocated IAB 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 IAB RF Bandwidths edges for middle band(s) if any. Additional carriers shall next be placed at the IAB 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 IABTC3, 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 IAB RF Bandwidths for middle band(s) if any. + +- If the sum of the maximum IAB RF Bandwidth of each supported operating bands is larger than the declared *Total RF Bandwidth* $BW_{tot}$ (D.13) of transmitter and receiver for the declared band combinations of the IAB, repeat the steps above for test configurations where the IAB RF Bandwidth of one of the operating band shall be reduced so that the *Total RF Bandwidth* $BW_{tot}$ of transmitter and receiver is not exceeded and vice versa. + +#### 4.7.7.3 IABTC5 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_{rated,t,AC}$ or $P_{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.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 of IAB-DU and IAB-MT 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.2-1: Requirement set applicability for IAB-DUs and IAB-MTs** + +| Requirement | IAB-DU Requirement set | IAB-MT Requirement set | +|-----------------------------------|------------------------|------------------------| +| 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 | 6.6.3 | +| Operating band unwanted emissions | 6.6.4 | 6.6.4 | +| Transmitter spurious emissions | 6.6.5 | 6.6.5 | +| Transmitter intermodulation | 6.7.5 | 6.7.5 | +| Reference sensitivity level | 7.2 | 7.2 | +| Dynamic range | 7.3 | NA | +| In-band selectivity and blocking | 7.4 | 7.4 | +| Out-of-band blocking | 7.5 | 7.5 | +| Receiver spurious emissions | 7.6 | 7.6 | +| Receiver intermodulation | 7.7 | 7.7 | +| In-channel selectivity | 7.8 | NA | +| 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 an IAB node capable of single carrier, multi-carrier and/or CA operation in both contiguous and non-contiguous spectrum in single band. + +For an IAB node declared to be capable of single carrier operation only (D.16), a single carrier (SC) shall be used for testing. + +For an IAB node 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 an IAB node 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 an IAB node 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 an IAB node declared to support IAB simultaneous operation (D.IAB-2) 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-2 shall be used for testing of simultaneous operation. + +For an IAB node declared to support IAB simultaneous operation (D.IAB-2) 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 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-2 shall be used for testing of simultaneous operation. + +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 IAB capable of multi-carrier and/or CA in a single band** + +| IAB test case | Contiguous spectrum capable IAB | C and NC capable IAB with identical parameters | C and NC capable IAB with different parameters | +|---------------------------------------------------------|----------------------------------------|-------------------------------------------------------|-------------------------------------------------------| +| Output power | IABTC1 | IABTC1 | IABTC1, IABTC3 | +| 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 | +| Total power dynamic range | SC | SC | SC | +| Transmit ON/OFF power (only applied to NR TDD IAB) | IABTC1 | IABTC1 | IABTC1, IABTC3 | +| Frequency error | Tested with Error Vector Magnitude | Tested with Error Vector Magnitude | Tested with Error Vector Magnitude | +| Error Vector Magnitude | IABTC1 | IABTC1 | IABTC1, IABTC3 | +| Time alignment error (only applied to IAB-DU) | IABTC1 | IABTC1 | IABTC1, IABTC3 | +| Occupied bandwidth | SC, IABTC2 (Note 1) | SC, IABTC2 (Note 1) | SC, IABTC2 (Note 1) | +| Adjacent Channel Leakage power Ratio (ACLR) | IABTC1 | IABTC3 | IABTC1, IABTC3 | +| Cumulative ACLR requirement in non-contiguous spectrum | - | IABTC3 | IABTC3 | +| Operating band unwanted emissions | IABTC1, SC (Note 2) | IABTC1, IABTC3, SC (Note 2) | IABTC1, IABTC3, SC (Note 2) | +| Transmitter spurious emissions | IABTC1 | IABTC3 | IABTC1, IABTC3 | +| Transmitter intermodulation | IABTC1 | IABTC1, IABTC3 | IABTC1, IABTC3 | +| Reference sensitivity level | SC | SC | SC | +| Dynamic range | SC | SC | SC | +| Adjacent Channel Selectivity (ACS) | IABTC1 | IABTC3 | IABTC1, IABTC3 | +| In-band blocking | IABTC1 | IABTC3 | IABTC1, IABTC3 | +| Out-of-band blocking | IABTC1 | IABTC3 | IABTC1, IABTC3 | +| Receiver spurious emissions | IABTC1 | IABTC3 | IABTC1, IABTC3 | +| Receiver intermodulation | IABTC1 | IABTC3 | IABTC1, IABTC3 | +| 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 sub-carrier spacing. + +**Table 4.8.3-2: Test configurations for a IAB capable of simultaneous operation in a single band** + +| IAB test case | Contiguous spectrum capable IAB | C and NC capable IAB with identical parameters | C and NC capable IAB with different parameters | +|--------------------------------------------------------|----------------------------------------|-------------------------------------------------------|-------------------------------------------------------| +| Output power | IABTC1 | IABTC1 | IABTC1, IABTC3 | +| Transmit ON/OFF power (only applied to NR TDD IAB) | IABTC1 | IABTC1 | IABTC1, IABTC3 | +| Frequency error | Tested with Error Vector Magnitude | Tested with Error Vector Magnitude | Tested with Error Vector Magnitude | +| Error Vector Magnitude | IABTC1 | IABTC1 | IABTC1, IABTC3 | +| Time alignment error between IAB-DU and IAB-MT | IABTC1 | IABTC1 | IABTC1, IABTC3 | +| Adjacent Channel Leakage power Ratio (ACLR) | IABTC1 | IABTC3 | IABTC1, IABTC3 | +| Cumulative ACLR requirement in non-contiguous spectrum | - | IABTC3 | IABTC3 | +| Operating band unwanted emissions | IABTC1 (Note 2) | IABTC1, IABTC3 (Note 2) | IABTC1, IABTC3 (Note 2) | +| Transmitter spurious emissions | IABTC1 | IABTC3 | IABTC1, IABTC3 | +| Transmitter intermodulation | IABTC1 | IABTC1, IABTC3 | IABTC1, IABTC3 | +| Adjacent Channel Selectivity (ACS) | IABTC1 | IABTC3 | IABTC1, IABTC3 | +| In-band blocking | IABTC1 | IABTC3 | IABTC1, IABTC3 | +| Out-of-band blocking | IABTC1 | IABTC3 | IABTC1, IABTC3 | +| Receiver spurious emissions | IABTC1 | IABTC3 | IABTC1, IABTC3 | +| Receiver intermodulation | IABTC1 | IABTC3 | IABTC1, IABTC3 | + +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 sub-carrier spacing. + +**Table 4.8.4-2: Test configuration for a IAB capable of simultaneous operation in multi-band operation** + +| IAB test case | Test configuration | | +|---------------------------------------------------------|----------------------------------------|------------------------------------------| +| | Common connector | Separate connectors | +| Output power | IABTC1/3 (Note 1), IABTC4 | IABTC1/3 (Note 1), IABTC4 | +| RE Power control dynamic range (only applied to IAB-DU) | Tested with Error Vector Magnitude | Tested with Error Vector Magnitude | +| Transmit ON/OFF power (only applied to NR TDD IAB) | IABTC4 | IABTC4 | +| Frequency error | Tested with Error Vector Magnitude | Tested with Error Vector Magnitude | +| Error Vector Magnitude | IABTC1/3 (Note 1), IABTC4 | IABTC1/3 (Note 1), IABTC4 | +| Time alignment error between IAB-DU and IAB-MT | IABTC1/3 (Note 1), IABTC5 (Note 2) | IABTC1/3 (Note 1), IABTC5 (Note 2) | +| Adjacent Channel Leakage power Ratio (ACLR) | IABTC1/3 (Note 1), IABTC5 (Note 4) | IABTC1/3 (Note 1, 5), IABTC5 (Note 4, 5) | +| Cumulative ACLR requirement in non-contiguous spectrum | IABTC3 (Note 1), IABTC5 (Note 4) | IABTC3 (Note 1, 5) | +| Operating band unwanted emissions | IABTC1/3 (Note 1), IABTC5, SC (Note 7) | IABTC1/3 (Note 1, 5), IABTC5 (Note 5) | +| Transmitter spurious emissions | IABTC1/3 (Note 1), IABTC5 | IABTC1/3 (Note 1, 5), IABTC5 (Note 5) | +| Transmitter intermodulation | IABTC1/3 (Note 1) | IABTC1/3 (Note 1, 5) | +| Adjacent Channel Selectivity (ACS) | IABTC5 | IABTC1/3 (Note 1), IABTC5 (Note 6) | +| In-band blocking | IABTC5 | IABTC1/3 (Note 1), IABTC5 (Note 6) | +| Out-of-band blocking | IABTC5 | IABTC1/3 (Note 1), IABTC5 (Note 6) | +| Receiver spurious emissions | IABTC1/3 (Note 1), IABTC5 | IABTC1/3 (Note 1, 5), IABTC5 (Note 5) | +| Receiver intermodulation | IABTC5 | IABTC1/3 (Note 1), IABTC5 (Note 6) | + +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: Void. +NOTE 4: IABTC5 may be applied for Inter RF Bandwidth gap only. +NOTE 5: For single-band operation test, other TAB connector(s) is (are) terminated. +NOTE 6: IABTC5 is only applicable for multi-band receiver. + +#### 4.8.4 Applicability of test configurations for multi-band operation + +For an IAB node 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. + +For an IAB node declared to be capable of IAB simultaneous operation of multi-band operation, the test configuration in table 4.8.4-2 and/or table 4.8.3-2 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-2 shall be used. In the case where multiple bands are mapped on common *single-band connector*, the test configuration in table 4.8.3-2 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-2 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 IAB capable of multi-band operation** + +| IAB test case | Test configuration | | +|---------------------------------------------------------|----------------------------------------|----------------------------------------------------| +| | Common connector | Separate connectors | +| Output power | IABTC1/3 (Note 1), IABTC4 | IABTC1/3 (Note 1), IABTC4 | +| RE Power control dynamic range (only applied to IAB-DU) | Tested with Error Vector Magnitude | Tested with Error Vector Magnitude | +| Total power dynamic range | SC | SC | +| Transmit ON/OFF power (only applied to NR TDD IAB) | IABTC4 | IABTC4 | +| Frequency error | Tested with Error Vector Magnitude | Tested with Error Vector Magnitude | +| Error Vector Magnitude | IABTC1/3 (Note 1), IABTC4 | IABTC1/3 (Note 1), IABTC4 | +| Time alignment error (only applied to IAB-DU) | IABTC1/3 (Note 1), IABTC5 (Note 2) | IABTC1/3 (Note 1), IABTC5 (Note 2) | +| Occupied bandwidth | SC, IABTC2 (Note 3) | SC, IABTC2 (Note 3) | +| Adjacent Channel Leakage power Ratio (ACLR) | IABTC1/3 (Note 1), IABTC5 (Note 4) | IABTC1/3 (Note 1, 5), IABTC5 (Note 4, 5) | +| Cumulative ACLR requirement in non-contiguous spectrum | IABTC3 (Note 1), IABTC5 (Note 4) | IABTC3 (Note 1, 5) | +| Operating band unwanted emissions | IABTC1/3 (Note 1), IABTC5, SC (Note 7) | IABTC1/3 (Note 1, 5), IABTC5 (Note 5), SC (Note 7) | +| Transmitter spurious emissions | IABTC1/3 (Note 1), IABTC5 | IABTC1/3 (Note 1, 5), IABTC5 (Note 5) | +| Transmitter intermodulation | IABTC1/3 (Note 1) | IABTC1/3 (Note 1, 5) | +| Reference sensitivity level | SC | SC | +| Dynamic range | SC | SC | +| Adjacent Channel Selectivity (ACS) | IABTC5 | IABTC1/3 (Note 1), IABTC5 (Note 6) | +| In-band blocking | IABTC5 | IABTC1/3 (Note 1), IABTC5 (Note 6) | +| Out-of-band blocking | IABTC5 | IABTC1/3 (Note 1), IABTC5 (Note 6) | +| Receiver spurious emissions | IABTC1/3 (Note 1), IABTC5 | IABTC1/3 (Note 1, 5), IABTC5 (Note 5) | +| Receiver intermodulation | IABTC5 | IABTC1/3 (Note 1), IABTC5 (Note 6) | +| In-channel selectivity (only applied to IAB-DU) | SC | 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: For single-band operation test, other TAB connector(s) is (are) terminated. +NOTE 6: IABTC5 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. + +## 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 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 this TS 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_{RFBW}$ (bottom), $M_{RFBW}$ (middle) and $T_{RFBW}$ (top). + +Unless otherwise stated, the test shall be performed at $B_{RFBW}$ , $M_{RFBW}$ and $T_{RFBW}$ defined as following: + +- $B_{RFBW}$ : maximum IAB RF Bandwidth located at the bottom of the supported frequency range in the operating band. +- $M_{RFBW}$ : maximum IAB RF Bandwidth located in the middle of the supported frequency range in the operating band. +- $T_{RFBW}$ : maximum IAB 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 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_{BW\ Channel\ CA}(\text{bottom})$ , $M_{BW\ Channel\ CA}(\text{middle})$ and $T_{BW\ Channel\ CA}(\text{top})$ for contiguous spectrum operation. + +Unless otherwise stated, the test for contiguous spectrum operation shall be performed at $B_{BW\ Channel\ CA}$ , $M_{BW\ Channel\ CA}$ and $T_{BW\ Channel\ CA}$ defined as following: + +- $B_{BW\ Channel\ CA}$ : *aggregated IAB channel bandwidth* located at the bottom of the supported frequency range in each operating band; +- $M_{BW\ Channel\ CA}$ : *aggregated IAB channel bandwidth* located close in the middle of the supported frequency range in each operating band; +- $T_{BW\ Channel\ CA}$ : *aggregated IAB channel bandwidth* located at the top of the supported frequency range in each operating band. + +For IAB capable of multi-band operation, unless otherwise stated, the test shall be performed at $B_{RFBW\_T'_{RFBW}}$ and $B'_{RFBW\_T_{RFBW}}$ defined as following: + +- $B_{RFBW\_T'_{RFBW}}$ : the *IAB 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'_{RFBW\_T_{RFBW}}$ : the *IAB 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_{RFBW\_T'_{RFBW}} = B'_{RFBW\_T_{RFBW}} = B_{RFBW\_T_{RFBW}}$ when the declared Maximum Radio Bandwidth spans all operating bands. $B_{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. + +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 FR1 test models needed for *IAB type I-H*. Note that the NR FR1 test models are also applicable to *IAB type I-O* conformance testing in TS 38.176-2 [3]. + +### 4.9.2.2 FR1 test models for IAB-DU + +FR1 test model in clause 4.9.2.2 in TS 38.141-1[13] applies to IAB-DU as below: + +NR-FR1-TM1.1 applies to IAB-DU-FR1-TM1.1 + +NR-FR1-TM1.2 applies to IAB-DU-FR1-TM1.2 + +NR-FR1-TM2 applies to IAB-DU-FR1-TM2 + +NR-FR1-TM2a applies to IAB-DU-FR1-TM2a + +NR-FR1-TM3.1 applies to IAB-DU-FR1-TM3.1 + +NR-FR1-TM3.1a applies to IAB-DU-FR1-TM3.1a + +NR-FR1-TM3.2 applies to IAB-DU-FR1-TM3.2 + +NR-FR1-TM3.3 applies to IAB-DU-FR1-TM3.3 + +Testing models applying to NB-IoT operation in clause 4.9.2.2 in TS 38.141-1[13] are not applicable to IAB-DU. + +#### 4.9.2.3 FR1 test models for IAB-MT + +##### 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 (IAB-MT-FR1-TM) below. A reference to the applicable test model is made within each test. + +The following general parameters are used by all IAB-MT 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 clause 5.3.2 in TS 38.174[2]. +- Normal CP +- Virtual resource blocks of localized type + +IAB-MT test models are derived based on the uplink/downlink configuration as shown in the table 4.9.2.3.1-1 using information element *TDD-UL-DL-ConfigCommon* as defined in TS 38.331 [14]. + +**Table 4.9.2.3.1-1: Configurations of TDD for IAB 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 | + +Common physical channel parameters for all IAB-MT 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 IAB-MT 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 IAB type 1-H 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 IAB type 1-H test models** + +| Parameter | Value | +|-----------|-------| +| | PUSCH | + +#### 4.9.2.3.2 FR1 test model 1.1 (IAB-MT-FR1-TM1.1) + +This model shall be used for tests on: + +- IAB output power +- Transmit ON/OFF power +- 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.3.1. Specific physical channel parameters for IAB-MT-FR1-TM1.1 are defined in table 4.9.2.3.2-1. + +**Table 4.9.2.3.2-1: Specific physical channel parameters of IAB-MT-FR1-TM1.1** + +| Parameter | Value | +|------------------|----------| +| # of PRBs PUSCH | $N_{RB}$ | +| Modulation PUSCH | QPSK | + +#### 4.9.2.3.3 FR1 test model 2 (IAB-MT-FR1-TM2) + +This model shall be used for tests on: + +- Total power dynamic range (at lower PSD TX power limit at min power) +- Transmitted signal quality + - EVM of single 64QAM PRB allocation (at lower PSD TX power limit at min power) + - Frequency error (at min power) + +Common physical channel parameters are defined in clause 4.9.2.3.1. Specific physical channel parameters for IAB-MT-FR1-TM2 are defined in table 4.9.2.3.3-1. + +**Table 4.9.2.3.3-1: Specific physical channel parameters of IAB-MT-FR1-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.3a FR1 test model 2a (IAB-MT-FR1-TM2a) + +This model shall be used for tests on: + +- 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.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 (IAB-MT-FR1-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.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 (IAB-MT-FR1-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.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 IAB-MT-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 [9], 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 [9] use the following additional parameters: + +- $n_{ID}$ , Physical layer cell identity $n_{ID} = 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 [15]. 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 [9], clause 6.3.1.1. +- Perform modulation of the scrambled bits with the modulation scheme defined for each user according to TS 38.211 [9], clause 6.3.1.2 +- +- Perform mapping of the complex-valued symbols to layer according to TS 38.211 [9], clause 6.3.1.3. +- Perform PUSCH mapping according to TS 38.211 [9] using parameters listed in table 4.9.2.3-2. +- DM-RS sequence generation according to TS 38.211 [9], 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. +- +- +- DM-RS mapping according to TS 38.211 [9], 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 an IAB-DU or IAB-MT operates can either be contiguous or non-contiguous. Unless otherwise stated, the requirements in the present specification apply for IAB-DU and IAB-MT configured for both *contiguous spectrum* operation and *non-contiguous spectrum* operation. + +For IAB-DU or IAB-MT operation in *non-contiguous spectrum*, some requirements apply both at the *IAB RF Bandwidth edges* and inside the *sub-block gaps*. For each such requirement, it is stated how the limits apply relative to the *IAB RF Bandwidth edges* and the *sub-block edges* respectively. + +## 4.11 Requirements for IAB 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 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 *IAB-DU* or *IAB-MT* 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 *TAB connectors* for *IAB 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 IAB-DU or IAB-MT 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 *IAB-DU* or *IAB-MT* are applicable. Single-band requirements are tested separately at the *connector* configured for single-band operation, with all other *TAB connectors* terminated. + +An *IAB 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 *IAB type 1-H* capability of operation in multiple *operating bands*. + +Unless otherwise stated all requirements specified for an *operating band* apply only to the set of *TAB connectors* supporting that *operating band*. + +In 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 the present document. + +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 the present document. + +## 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. + +### **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* it is required that the DUT selection between requirements follows following rules: + +- Out of maximum output transmit power, modulation quality and ACLR, operating band unwanted emissions and transmitter general spurious emissions, IAB-DU and IAB-MT are required to be the DUT at least once, +- Out of reference sensitivity, receiver spurious emissions, 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 may be larger than for the IAB-DU. In cases where the test efficiency optimization is applicable 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 | | +|------------------------|--------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|-----------------|-----------------| +| | | | IAB-DU type 1-H | IAB-MT type 1-H | +| D.2 | IAB class | Medium range IAB-DU can apply test efficiency optimization with wide area IAB-MT in case other declarations in this table are the same. | x | x | +| D.3 | Operating bands and frequency ranges | | x | x | +| D.8 | Single band connector or multi-band connector | | x | x | +| D.11 | Maximum IAB RF Bandwidth | | x | x | +| D.13 | Total RF bandwidth (BW tot ) | | x | x | +| D.14 | NR supported channel bandwidths and SCS | | x | x | +| D.17 | Maximum number of supported carriers per operating band in single band operation | | x | x | +| D.18 | Maximum number of supported carriers per operating band in multi-band operation | | x | x | +| D.19 | Total maximum number of supported carriers in multi-band operation | | x | x | +| D.20 | Other band combination multi-band restrictions | | x | x | +| D.21 | Rated carrier output power (P rated,c,AC , or P rated,c,TABC ) | | x | x | +| D.22 | Rated total output power (P rated,t,AC , or P rated,t,TABC ) | | x | x | + +**Table 4.13-2: Test requirement applicability for TX requirements** + +| Tx requirement | | Test efficiency optimization applicable | Test requirement applicability (Note 1) | +|-----------------------------------------|--------------------------------------|-----------------------------------------|-----------------------------------------| +| Maximum output power | | Yes | | +| Output power dynamics (only for IAB-DU) | | No | (Note 2) | +| Output power dynamics (only for IAB-MT) | | No | (Note 2) | +| Transmitter OFF power | | Yes | | +| Transient period | | Yes | | +| IAB-DU Frequency Error | | No | (Note 2) | +| IAB-MT Frequency Error | | No | (Note 2) | +| Modulation quality | | Yes | | +| Time alignment error (only for IAB-DU) | | No | (Note 2) | +| Occupied bandwidth | | Yes | | +| ACLR | | Yes | | +| Operating band unwanted emission | | Yes | | +| Transmitter spurious emission | General requirement | | | +| | Additional spurious emissions | | | +| | Co-location with other base stations | | | +| OTA transmitter intermodulation | | Yes | | + +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. + +**Table 4.13-3: Test requirement applicability for receiver requirements** + +| Rx requirement | | Test efficiency optimization applicable | Test requirement applicability (Note 1) | +|------------------------------------------|-------------------------|-----------------------------------------|-----------------------------------------| +| Reference sensitivity | | Yes | | +| Dynamic range (only for IAB-DU) | | No | (Note 2) | +| Adjacent channel selectivity | | Yes | IAB-MT | +| In-band blocking | | Yes | IAB-MT | +| Out-of-band blocking | General requirement | | IAB-MT | +| | Co-location requirement | | | +| Receiver spurious emissions | | Yes | | +| Receiver intermodulation | | Yes | IAB-MT | +| 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 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-3) 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 conducted testing purposes in the present document, only FR1 operating bands are considered. + +## 6 Conducted transmitter characteristics (IAB-DU and IAB-MT) + +### 6.1 General + +General test conditions for conducted 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 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.3, if representative *TAB connectors* are used then per connector criteria (i.e. option 2) shall be applied. + +For *IAB-DU* and *IAB-MT* the manufacturer shall declare the minimum number of supported geographical cells (i.e. geographical areas). The declaration is done separately for IAB-DU and IAB-MT. The minimum number of supported geographical cells ( $N_{\text{cells}}$ , D.24) relates to the setting with the minimum amount of cell splitting supported with transmission on all *TAB connectors* supporting the *operating band*. + +For *IAB-DU* and *IAB-MT* manufacturer shall also declare *TAB connector TX min cell groups* (D.34). The declaration is done separately for IAB-DU and IAB-MT. Every *TAB connector* of the *IAB type 1-H* supporting transmission in an *operating band* shall map to one *TAB connector TX min cell group* supporting the same *operating band*, where mapping of *TAB connectors* to cells/beams is implementation dependent. + +The number of *active transmitter units* that are considered when calculating the conducted TX emissions limits ( $N_{\text{TXU,counted}}$ ) for *IAB-DU* and *IAB-MT* is calculated as follows: + +$$N_{\text{TXU,counted}} = \min(N_{\text{TXU,active}}, 8 \times N_{\text{cells}})$$ + +$N_{\text{TXU,countedpercell}}$ is used for scaling of *basic limits* and is derived as $N_{\text{TXU,countedpercell}} = N_{\text{TXU,counted}} / N_{\text{cells}}$ + +NOTE: $N_{\text{TXU,active}}$ depends on the actual number of *active transmitter units* and is independent to the declaration of $N_{\text{cells}}$ . + +### 6.2 IAB output power + +#### 6.2.1 General + +The IAB type 1-H conducted output power requirement is at *TAB connector* for *IAB type 1-H*. + +The *rated carrier output power* of the *IAB type 1-H* shall be as specified in table 6.2.1-1 for *IAB-DU* and in table 6.2.1-2 for *IAB-MT*. + +**Table 6.2.1-1: IAB type 1-H rated output power limits for IAB-DU classes** + +| IAB-DU class | $P_{\text{rated,c,sys}}$ | $P_{\text{rated,c,TABC}}$ | +|----------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------|---------------------------| +| Wide Area IAB-DU | (Note) | (Note) | +| Medium Range IAB-DU | $\leq 38 \text{ dBm} + 10\log(N_{\text{TXU,counted}})$ | $\leq 38 \text{ dBm}$ | +| Local Area IAB-DU | $\leq 24 \text{ dBm} + 10\log(N_{\text{TXU,counted}})$ | $\leq 24 \text{ dBm}$ | +| NOTE: There is no upper limit for the $P_{\text{rated,c,sys}}$ or $P_{\text{rated,c,TABC}}$ of the Wide Area IAB-DU. | | | + +**Table 6.2.1-2: IAB type 1-H rated output power limits for IAB-MT classes** + +| IAB-MT class | $P_{\text{rated,c,sys}}$ | $P_{\text{rated,c,TABC}}$ | +|----------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------|---------------------------| +| Wide Area IAB-MT | (Note) | (Note) | +| Local Area IAB-MT | $\leq 24 \text{ dBm} + 10\log(N_{\text{TXU,counted}})$ | $\leq 24 \text{ dBm}$ | +| NOTE: There is no upper limit for the $P_{\text{rated,c,sys}}$ or $P_{\text{rated,c,TABC}}$ of the Wide area IAB-MT. | | | + +## 6.2.2 Minimum requirement + +The minimum requirement *IAB type 1-H* applies per *single-band connector*, or per *multi-band connector* supporting transmission in the *operating band*. + +The minimum requirement for *IAB-DU* is defined in TS 38.174 [2], clause 6.2.2. + +The minimum requirement for *IAB-MT* is defined in TS 38.174 [2], clause 6.2.2. + +## 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 + +*IAB 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 *IAB 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. If IAB simultaneous transmission is declared to be supported (see D.IAB-2 in table 4.6-1), when IAB-MT and IAB-DU are transmitting simultaneously, the measurement may be pretested on one connector at a time or may be tested in parallel as shown in annex D.1.1. Whichever method is used the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested. + +- 1) Connect 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 *IAB type 1-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,TABC}}$ for *IAB 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. + +- 3) Measure the *maximum carrier output power* ( $P_{\text{max,c,TABC}}$ for *IAB type 1-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,TABC}}$ for *IAB type 1-H* (D.21): + +**Table 6.2.5-1: Test requirement for conducted IAB-DU and IAB-MT output power** + +| | Normal test environment | Extreme test environment | +|---------------------------------|----------------------------------------------------------------|----------------------------------------------------------------| +| IAB-DU,
IAB-MT | $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 6.0 \text{ GHz}: \pm 3.0 \text{ dB}$ | $3.0 \text{ GHz} < f \leq 6.0 \text{ GHz}: \pm 3.5 \text{ dB}$ | + +## 6.3 Output power dynamics + +### 6.3.1 IAB-DU Output Power Dynamics + +#### 6.3.1.1 General + +The requirements in clause 6.3.1 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.1.2 RE power control dynamic range + +##### 6.3.1.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 an IAB-DU at *maximum carrier output power* ( $P_{\text{max,c,TABC}}$ or $P_{\text{max,c,AC}}$ ) for a specified reference condition. + +For *IAB type 1-H* this requirement shall apply at each *TAB connector* supporting transmission in the *operating band*. + +##### 6.3.1.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 *IAB type 1-H* is defined in TS 38.174 [2], clause 6.3.1.2. + +##### 6.3.1.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.3 provides sufficient test coverage for this requirement. + +#### 6.3.1.3 Total power dynamic range + +##### 6.3.1.3.1 Definition and applicability + +The IAB-DU 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 *IAB type 1-H* this requirement shall apply at each *TAB connector* supporting transmission in the *operating band*. + +NOTE: The upper limit of the dynamic range is the OFDM symbol power for an IAB-DU 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 PDCCH, RS or SSB. + +#### 6.3.1.3.2 Minimum requirement + +The minimum requirement applies per *single-band connector*, or per *multi-band connector*. + +The minimum requirement for *IAB-DU* is in TS 38.174 [2], clause 6.3.1.3. + +#### 6.3.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.3.1.3.4 Method of test + +##### 6.3.1.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 *IAB type 1-H*. + +##### 6.3.1.3.4.2 Procedure + +For *IAB 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. 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 *IAB 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 $P_{\text{rated,c,TABC}}$ for *IAB type 1-H* (D.21). +- 3) For *IAB-DU type 1-H*, set the IAB-DU to transmit a signal according to: + - IAB-DU-FR1-TM3.1a if 256QAM is supported without power back off, or + - IAB-DU-FR1-TM3.1 if 256QAM is supported with power back off, or + - IAB-DU-FR1-TM3.1 if 256QAM is not supported by IAB-DU. +- 4) Measure the OFDM symbol TX power (OSTP) as defined in the annex H. +- 5) For *IAB-DU type 1-H*, set to transmit a signal according to: + - IAB-DU-FR1-TM2a if 256QAM is supported, or + - IAB-DU-FR1-TM2 if 256QAM is 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.1.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.1.3.5-1. + +**Table 6.3.1.3.5-1: IAB-DU total power dynamic range** + +| NR 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 | 23.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 EVM at the lower limit of the dynamic range are defined in clause 6.5.3. + +## 6.3.2 IAB-MT Output Power Dynamics + +### 6.3.2.1 Total power dynamic range + +#### 6.3.2.1.1 Definition and applicability + +The IAB-MT 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 included as part of the dynamic range. + +#### 6.3.2.1.2 Minimum requirement + +The IAB-MT total power dynamic range is defined in TS 38.174 [2], clause 6.3.2.1.2. + +#### 6.3.2.1.3 Test purpose + +The test purpose is to verify that the IAB-MT total power dynamic range is within the limits specified by the minimum requirement. + +#### 6.3.2.1.4 Method of test + +##### 6.3.2.1.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 *IAB type I-H*. + +##### 6.3.2.1.4.2 Procedure + +For *IAB 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.1.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 *IAB 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 $P_{\text{rated,c,TABC}}$ for *IAB type 1-H* (D.21). +- 3) Set the IAB-MT to transmit a signal according to IAB-MT-FR1-TM3.1 +- 4) Measure the power over 1ms +- 5) Set to transmit a signal according to IAB-MT-FR1-TM2. +- 6) Measure the power over 1ms + +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.2.1.5 Test requirements + +The $\Delta P$ between the power measured in step 4 and step 6 of clause 6.3.2.1.4.2 shall be: + +**Table 6.3.2.1.5-1: IAB-MT 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.3.2.2 Relative power tolerance for local area IAB-MT + +#### 6.3.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.3.2.2.2 Minimum requirement + +The IAB-MT total power dynamic range is defined in TS 38.174 [2], clause 6.3.3.1 + +#### 6.3.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.3.2.1 provides sufficient test coverage for this requirement. + +### 6.3.2.3 Aggregate power tolerance for local area IAB-MT + +#### 6.3.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 [12] kept constant. + +#### 6.3.2.3.2 Minimum requirement + +The IAB-MT Aggregate power tolerance is defined in TS 38.174 [2], clause 6.3.3.2 + +### 6.3.2.3.3 Test purpose + +No specific test or test requirements are defined for IAB-MT Aggregate power tolerance. + +## 6.4 Transmit ON/OFF power + +### 6.4.1 Transmitter OFF power + +#### 6.4.1.1 Definition and applicability + +Transmit OFF power requirements apply to TDD operation of IAB-DU and TDD operation of IAB-MT. + +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 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 type 1-H*, 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 *IAB type 1-H* 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 IAB 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 channel bandwidth*. + +#### 6.4.1.2 Minimum requirement + +The minimum requirement for *IAB type 1-H*: + +For *IAB-DU* is in TS 38.174 [2], clause 6.4.1.3. + +For *IAB-MT* is in TS 38.174 [2], clause 6.4.1.4. + +#### 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 to TDD operation of IAB-DU and TDD operation of IAB-MT. + +The transmitter transient period is the time period during which the transmitter is changing from the transmitter OFF period to the transmitter ON period or vice versa. The transmitter transient period is illustrated in figure 6.4.2.1-1 for IAB-DU and IAB-MT. + +![Figure 6.4.2.1-1: Example of relations between transmitter ON period, transmitter OFF period and transmitter transient period for IAB-DU and IAB-MT. 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 curve shows a transition from a low power level to the ON power level, then a period of high power, and then a transition back to the low power level. The high power period is labeled 'Transmitter ON period (DL/UL transmission)'. The transition periods are labeled 'Transmitter transient period'. The periods before and after the ON period are labeled 'Transmitter OFF period'. The x-axis also has labels for 'UL/DL transmission' and 'GP or UL/DL transmission'.](e0113695dbf148bf5ec34354e544414b_img.jpg) + +Figure 6.4.2.1-1: Example of relations between transmitter ON period, transmitter OFF period and transmitter transient period for IAB-DU and IAB-MT. 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 curve shows a transition from a low power level to the ON power level, then a period of high power, and then a transition back to the low power level. The high power period is labeled 'Transmitter ON period (DL/UL transmission)'. The transition periods are labeled 'Transmitter transient period'. The periods before and after the ON period are labeled 'Transmitter OFF period'. The x-axis also has labels for 'UL/DL transmission' and 'GP or UL/DL transmission'. + +**Figure 6.4.2.1-1: Example of relations between transmitter ON period, transmitter OFF period and transmitter transient period for IAB-DU and IAB-MT** + +For IAB type 1-H, this requirement shall be applied at each TAB connector supporting transmission in the operating band. + +## 6.4.2.2 Minimum requirement + +The minimum requirement for *IAB type 1-H*: + +For *IAB-DU* is in TS 38.174 [2], clause 6.4.2.2. + +For *IAB-MT* is in TS 38.174 [2], clause 6.4.2.3. + +## 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: + +- MRFBW 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.4.2.4.2 Procedure + +The minimum requirement is applied to all *TAB connectors*, they may be tested one at a time or multiple *TAB connectors* may be tested in parallel as shown in annex D.1.1 for *IAB type 1-H*. If IAB simultaneous transmission is declared to be supported (see D.IAB-2 in table 4.6-1), connector(s) for IAB-MT and IAB-DU may be tested one at a time or *TAB connectors* may be tested in parallel as shown in Annex D.1.1 for *IAB type 1-H*. Whichever method is used the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested. + +- 1) Connect *TAB connector* to measurement equipment as shown in annex D.1.1 for *IAB type 1-H*. All *TAB connectors* not under test shall be terminated. + +As a general rule, the resolution bandwidth of the measuring equipment should be equal to the measurement bandwidth. However, to improve measurement accuracy, sensitivity, efficiency and avoiding e.g. carrier leakage, the resolution bandwidth may be smaller than the measurement bandwidth. When the resolution bandwidth is smaller than the measurement bandwidth, the result should be integrated over the measurement bandwidth in order to obtain the equivalent noise bandwidth of the measurement bandwidth. + +- 2) For single carrier set the *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 TAB connector* ( $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 *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 a *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 IAB 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 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 6.0 \text{ GHz}$ . + +For *multi-band connector*, 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 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 IAB-DU frequency error + +##### 6.5.2.1.1 Definition and applicability + +For IAB-DU, 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. + +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 *IAB type 1-H* this requirement shall be applied at each *TAB connector* supporting transmission in the *operating band*. + +##### 6.5.2.1.2 Minimum Requirement + +For IAB-DU, the minimum requirement is in TS 38.174 [2], clause 6.5.1.1. + +##### 6.5.2.1.3 Test purpose + +The test purpose is to verify that frequency error is within the limit specified by the minimum requirement. + +##### 6.5.2.1.4 Method of test + +Requirement is tested together with modulation quality test, as described in clause 6.5.3. + +##### 6.5.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.5.2.1.5-1 observed over 1 ms. + +**Table 6.5.2.1.5-1: Frequency error test requirement for IAB-DU** + +| 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.5.2.2 IAB-MT frequency error + +##### 6.5.2.2.1 Definition and applicability + +For IAB-MT, 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 type 1-H* this requirement shall be applied at each *TAB connector* supporting transmission in the *operating band*. + +#### 6.5.2.2.2 Minimum Requirement + +For IAB-MT, the minimum requirement is in TS 38.174 [2], clause 6.5.1.2. + +#### 6.5.2.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.2.4 Method of test + +Requirement is tested together with modulation quality test, as described in clause 6.5.3. + +#### 6.5.2.2.5 Test Requirements + +For IAB-MT, 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.5.2.2.5-1: Frequency error test requirement for IAB-MT** + +| IAB-MT frequency range | Accuracy | +|------------------------|--------------------------------------| +| $f \leq 3.0\text{GHz}$ | $\pm(0.1\text{ ppm} + 15\text{ Hz})$ | +| $f > 3.0\text{GHz}$ | $\pm(0.1\text{ ppm} + 36\text{ Hz})$ | + +### 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 IAB type I-H this requirement shall be applied at each TAB connector supporting transmission in the operating band. + +#### 6.5.3.2 Minimum Requirement + +For IAB-DU, the minimum requirement is in TS 38.174 [2], clause 6.5.2.1. + +For IAB-MT, the minimum requirement is in TS 38.174 [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'_{\text{RFBW}}}}$ and $B'_{\text{RFBW\_T'_{\text{RFBW}}}}$ in multi-band operation, see clause 4.9.1. + +#### 6.5.3.4.2 Procedure for IAB-DU + +For IAB-DU, the minimum requirement is applied to all *TAB connectors*, they may be tested one at a time or multiple *TAB connectors* may be tested in parallel as shown in annex D.1.1 for *IAB type 1-H*. Whichever method is used the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested. + +1) For a *TAB connector* declared to be capable of single carrier operation only (D.16), set the *TAB connector* under test 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, or +- IAB-DU-FR1-TM3.1a at manufacturer's declared rated output power if 256QAM is supported by IAB-DU with power back off, 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 a *TAB connector* declared to be capable of multi-carrier and/or CA operation (D.15-D.16), set 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: + +- IAB-DU-FR1-TM 3.1a if 256QAM is supported by IAB-DU without power back off, or +- IAB-DU-FR1-TM3.1a at manufacturer's declared rated output power if 256QAM is supported by IAB node with power back off, 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-FR1-TM3.1a, 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 IAB-DU-FR1-TM2 if 256QAM is not supported by IAB-DU or for IAB-DU-FR1-TM2a if 256QAM is supported by IAB-DU. For IAB-DU-FR1-TM2 and IAB-DU-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.5.3.4.3 Procedure for IAB-MT + +For IAB-MT, the minimum requirement is applied to all *TAB connectors*, they may be tested one at a time or multiple *TAB connectors* may be tested in parallel as shown in annex D.1.1 for *IAB type 1-H*. Whichever method is used the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested. + +1) For a *TAB connector* declared to be capable of single carrier operation only (D.16), set the *TAB connector* under test to transmit a signal according to the applicable test configuration in clause 4.8 using the corresponding test models: + +- IAB-MT-FR1-TM3.1a if 256QAM is supported by IAB-MT without power back off, or +- IAB-MT-FR1-TM3.1a at manufacturer's declared rated output power if 256QAM is supported by IAB-MT with power back off, and IAB-MT-FR1-TM3.1 at maximum power, or +- IAB-MT-FR1-TM3.1 with highest modulation order supported by IAB-MT. + +For a *TAB connector* declared to be capable of multi-carrier and/or CA operation (D.15-D.16), set 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: + +- IAB-MT-FR1-TM3.1a if 256QAM is supported by IAB-MT without power back off, or +- IAB-MT-FR1-TM3.1a at manufacturer's declared rated output power if 256QAM is supported by IAB-MT with power back off, 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-FR1-TM3.1a, 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 IAB-MT-FR1-TM2 if 256QAM is not supported by IAB-MT or for IAB-MT-FR1-TM2a if 256QAM is supported by IAB-MT. For IAB-MT-FR1-TM2 and IAB-MT-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.5.3.5 Test requirements + +The EVM of each NR carrier for different modulation schemes on PDSCH or PUSCH shall be less than the limits in table 6.5.3.5-1a. + +**Table 6.5.3.5-1: EVM requirements for IAB type 1-H** + +| 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.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 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. + +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 *IAB 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) | +|-------------------------|----------|--------------------------------------------------------------|----------------------------|--------------------------------------------------------------------------| +| 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) | +|-------------------------|----------|------------------------------------------------------|----------------------------|------------------------------------------------------------------| +| 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. + +## 6.5.4 Time alignment error + +### 6.5.4.1 Definition and applicability + +For IAB-DU, this requirement applies 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 at the IAB-DU transmitter *TAB connectors* are not perfectly aligned in time and may experience certain timing differences in relation to each other. + +For *IAB type I-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 *IAB-DU* are in TS 38.174 [2], clause 6.5.3.1. + +#### 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}}$ and $B'_{\text{RFBW\_T}}$ in multi-band operation, see clause 4.9.1. + +##### 6.5.4.4.2 Procedure + +For *IAB 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 *IAB type 1-H*: Connect two representative *TAB connectors* one from separate TAE group (D.31) to the measurement equipment according to annex D.1.4. Terminate any unused *TAB connector(s)*. + +2) Set the connectors under test to transmit IAB-DU-FR1-TM1.1 or any DL signal using MIMO transmission or carrier aggregation. + +NOTE: For MIMO transmission, different ports may be configured in IAB-DU-FR1-TM1.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 or non-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 IAB-DU 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 IAB-DU 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. + +### 6.5.5 Timing error between IAB-DU and IAB-MT + +#### 6.5.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.5.5.2 Minimum requirement + +The minimum requirements for *IAB-DU* and *IAB-MT* are in TS 38.174 [2], clause 6.5.4. + +#### 6.5.5.3 Test purpose + +To verify that the timing error between IAB-DU and IAB-MT simultaneous transmission is within the limit specified by the minimum requirement. + +#### 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. + +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}}$ and $B'_{\text{RFBW\_T}}$ in multi-band operation, see clause 4.9.1. + +##### 6.5.5.4.2 Procedure + +Compliance is to be demonstrated between all pairs of *single-band connectors and/or multi-band connectors*. + +1) Conducted measurement setup: + +- For *IAB type 1-H*: Connect two representative *TAB connectors* one from IAB-DU and one from IAB-MT to the measurement equipment. Terminate any unused *TAB connector(s)*. + +2) Set the connectors under test to transmit IAB-DU-FR1-TM1.1 or IAB-MT-FR1-TM1.1, respectively. + +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). + +For a connector declared to be capable of multi-carrier operation (D.15), 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 and 4.8 using the corresponding test model in clause 4.9.2 on all carriers configured. + +4) Measure the timing error between DM-RS symbols on the IAB-DU and IAB-MT connectors. Note that the possible difference in DM-RS symbol position and slot number shall be compensated for in the measured timing error. + +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.5.5 Test requirement + +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 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 IAB-DU and IAB-MT 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* of IAB-DU and uplink *operating band* of IAB-MT, 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 tables 6.6.1-1 and 6.6.1-2 for the NR *operating bands*. + +**Table 6.6.1-1: Maximum offset of OBUE outside the downlink *operating band* of IAB-DU** + +| IAB-DU type | Operating band characteristics | $\Delta f_{\text{OBUE}}$ (MHz) | +|---------------------|------------------------------------------------------------------------------------|--------------------------------| +| IAB 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 | + +**Table 6.6.1-2: Maximum offset of OBUE outside the uplink *operating band* of IAB-MT** + +| IAB-MT type | Operating band characteristics | $\Delta f_{\text{OBUE}}$ (MHz) | +|---------------------|------------------------------------------------------------------------------------|--------------------------------| +| IAB type 1-H | $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 | + +For *IAB type 1-H* the unwanted emission requirements are applied per the *TAB connector TX min cell groups* for all the supported configurations. 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 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 [6]. + +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 *IAB 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 *IAB type 1-H* is in TS 38.174 [2] clause 6.6.2. + +### 6.6.2.3 Test purpose + +The test purpose is to verify that the emission at the *TAB connector* does not occupy an excessive bandwidth for the service to be provided and is, therefore, not likely to create interference to other users of the spectrum beyond undue limits. + +### 6.6.2.4 Method of test + +#### 6.6.2.4.1 Initial conditions + +Test environment: Normal; see annex B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1. + +*Aggregated IAB channel bandwidth* positions to be tested for contiguous carrier aggregation: $M_{\text{BW Channel CA}}$ ; see clause 4.9.1. + +- 1) Connect the measurement device to *TAB connector* as shown in annex D.1.1 for *IAB type 1-H*. +- 2) For a IAB 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 IAB-DU-FR1-TM1.1 for *IAB-DU type 1-H* or IAB-MT-FR1-TM1.1 for *IAB-MT type 1-H* at manufacturer's declared rated output power ( $P_{\text{rated,c,TABC}}$ , D.21). + +For an IAB declared to be capable of contiguous CA operation, set the IAB to transmit according to IAB-DU-FR1-TM1.1 for *IAB-DU type 1-H* or IAB-MT-FR1-TM1.1 for *IAB-MT type 1-H* on all carriers configured using the applicable test configuration and corresponding power setting specified in clauses 4.7.4 and 4.8. + +For an IAB declared to be capable of simultaneous transmission(see D.IAB-2 in table 4.6-1), set the IAB to simultaneously transmit according to IAB-DU-FR1-TM1.1 for *IAB-DU type 1-H* and IAB-MT-FR1-TM1.1 for *IAB-MT type 1-H* using the applicable test configuration and corresponding power setting specified in clauses 4.7.4 and 4.8. + +#### 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 | IAB-DU channel bandwidth or IAB-MT channel bandwidth
BWChannel (MHz) | | | | Aggregated IAB channel bandwidth BWChannel_CA (MHz) | | | | +|--------------------------------------|--------------------------------------------------------------------------------------------------|-----|-----|-----------------------------------------------------------------|------------------------------------------------------------------------------|--|--|---------------------------------------------------------------------| +| | 10 | 15 | 20 | > 20 | > 20 | | | | +| Span (MHz) | 20 | 30 | 40 | | | | | $2 \times BW_{Channel\_CA}$ | +| Minimum number of measurement points | 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 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 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 IAB, the following step shall apply: + +- 6) For multi-band capable IAB 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.174 [2], table 5.3.5-1. For contiguous CA, the occupied bandwidth shall be less than or equal to the *aggregated IAB channel bandwidth* as defined in TS 38.174 [2], clause 5.3A. + +## 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 *IAB-DU RF Bandwidth*, *IAB-MT RF Bandwidth* or *Radio Bandwidth* whatever the type of transmitter considered (single carrier or multi-carrier) and for all transmission modes foreseen by the manufacturer's specification. + +For an IAB- node operating in *non-contiguous spectrum*, the ACLR requirement in clause 6.6.3.2 shall apply in *sub-block gaps* for the frequency ranges defined in table 6.6.3.2-3, while the CACLR requirement in clause 6.6.3.2 shall apply in *sub-block gaps* for the frequency ranges defined in table 6.6.3.2-4. + +For a *multi-band connector*, the ACLR requirement in clause 6.6.3.2 shall apply in *Inter RF Bandwidth gaps* for the frequency ranges defined in table 6.6.3.2-3, while the CACLR requirement in clause 6.6.3.2 shall apply in *Inter RF Bandwidth gaps* for the frequency ranges defined in table 6.6.3.2-4. + +The requirement shall apply 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 *IAB type 1-H* is defined in TS 38.174 [2], clause 6.6.3. + +### 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. + +*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. + +#### 6.6.3.4.2 Procedure + +For *IAB 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. If simultaneous transmission is declared to be supported (see D.IAB-2 in table 4.6-1), when IAB-MT and IAB-DU are transmitting simultaneously, the measurement may be tested on one connector at a time or may be tested in parallel as shown in annex D.1.1. Whichever method is used the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested. + +- 1) Connect the *single-band connector* or *multi-band connector* under test to measurement equipment as shown in annex D.1.1 for *IAB 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. + +- 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 IAB-DU-FR1-TM1.1 or IAB-MT-FR1-TM1.1 in clause 4.9.2 at *rated carrier output power* $P_{\text{rated,c,TABC}}$ for IAB 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. + +- 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 IAB-DU-FR1-TM1.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, the ACLR shall be higher than the value specified in table 6.6.3.5.2-1. + +**Table 6.6.3.5.2-1: IAB type 1-H ACLR limit** + +| IAB-DU channel bandwidth and IAB-MT channel bandwidth of lowest/highest carrier transmitted BW_{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 (informative) | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|------------------------------------------------------------------------------------|-------------------| +| 10, 15, 20 | $BW_{Channel}$ | NR of same BW (Note 2) | Square ( $BW_{Config}$ ) | 44.2 | +| | $2 \times BW_{Channel}$ | NR of same BW (Note 2) | Square ( $BW_{Config}$ ) | 44.2 | +| | $BW_{Channel}/2 + 2.5$ MHz | 5 MHz E-UTRA | Square (4.5 MHz) | 44.2 (Note 3) | +| | $BW_{Channel}/2 + 7.5$ MHz | 5 MHz E-UTRA | Square (4.5 MHz) | 44.2 (Note 3) | +| 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | $BW_{Channel}$ | NR of same BW (Note 2) | Square ( $BW_{Config}$ ) | 43.8 dB | +| | $2 \times BW_{Channel}$ | NR of same BW (Note 2) | Square ( $BW_{Config}$ ) | 43.8 dB | +| | $BW_{Channel}/2 + 2.5$ MHz | 5 MHz E-UTRA | Square (4.5 MHz) | 43.8 dB (Note 3) | +| | $BW_{Channel}/2 + 7.5$ MHz | 5 MHz E-UTRA | Square (4.5 MHz) | 43.8 dB (Note 3) | + +NOTE 1: $BW_{Channel}$ and $BW_{Config}$ are the *IAB-DU channel bandwidth 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_{Config}$ ). + +NOTE 3: The requirements are applicable when the band is also defined for E-UTRA or UTRA. + +The ACLR absolute *basic limit* is specified in table 6.6.3.5.2-2. + +**Table 6.6.3.5.2-2: IAB type 1-H ACLR absolute basic limit** + +| IAB-DU and IAB-MT category / class | ACLR absolute basic limit | +|-------------------------------------------------------------|----------------------------------| +| Category A Wide Area IAB-DU and Category A Wide Area IAB-MT | -13 dBm/MHz | +| Category B Wide Area IAB-DU and Category B Wide Area IAB-MT | -15 dBm/MHz | +| Medium Range IAB-DU | -25 dBm/MHz | +| Local Area IAB-DU and Local Area IAB-MT | -32 dBm/MHz | + +For operation in non-contiguous spectrum or multiple bands, the ACLR shall be higher than the value specified in Table 6.6.3.5.2-3. + +**Table 6.6.3.5.2-3: IAB type 1-H ACLR limit in non-contiguous spectrum or multiple bands** + +| IAB-DU channel bandwidth and IAB-MT channel bandwidth of lowest/highest 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 IAB RF Bandwidth edge (inside the gap) | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|-------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|----------------------------------|-----------------------------------------------------------------------------|------------| +| 10, 15, 20 | W gap ≥ 15 (Note 3)
W gap ≥ 45 (Note 4) | 2.5 MHz | 5 MHz NR (Note 2) | Square (BW Config ) | 44.2 dB | +| | W gap ≥ 20 (Note 3)
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 | W gap ≥ 60 (Note 4)
W gap ≥ 30 (Note 3) | 10 MHz | 20 MHz NR (Note 2) | Square (BW Config ) | 43.8 dB | +| | W gap ≥ 80 (Note 4)
W gap ≥ 50 (Note 3) | 30 MHz | 20 MHz NR (Note 2) | Square (BW Config ) | 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-DU channel bandwidth or IAB-MT 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-DU channel bandwidth or IAB-MT 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 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 *IAB RF Bandwidth edges*. + +The assumed filter for the adjacent channel frequency is defined in table 6.6.3.2-4 and the filters on the assigned channels are defined in table 6.6.3.2-6. + +For operation in *non-contiguous spectrum* or multiple bands, 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.2-4. + +**Table 6.6.3.5.2-4: IAB type 1-H CACLR limit** + +| IAB-DU channel bandwidth and IAB-MT channel bandwidth of lowest/highest 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 IAB RF Bandwidth edge (inside the gap) | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | CACLR limit | +|-------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|------------------------------------------------------------------------------------|--------------------| +| 10, 15, 20 | 5 ≤ W gap < 15 (Note 3) | 2.5 MHz | 5 MHz NR (Note 2) | Square (BW Config ) | 44.2 dB | +| | 5 ≤ W gap < 45 (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 | 10 < W gap < 20 (Note 3)
10 ≤ W gap < 50 (Note 4) | 10 MHz | 20 MHz NR (Note 2) | Square (BW Config ) | 43.8 dB | +| | 20 ≤ W gap < 60 (Note 4)
20 ≤ W gap < 30 (Note 3) | 30 MHz | 20 MHz NR (Note 2) | Square (BW Config ) | 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-DU channel bandwidth or IAB-MT 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-DU channel bandwidth or IAB-MT 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 CACLR absolute *basic limit* is specified in table 6.6.3.2-5. + +**Table 6.6.3.2-5: IAB type 1-H CACLR absolute basic limit** + +| IAB-DU and IAB-MT category / class | CACLR absolute basic limit | +|-------------------------------------------------------------|-----------------------------------| +| Category A Wide Area IAB-DU and Category A Wide Area IAB-MT | -13 dBm/MHz | +| Category B Wide Area IAB-DU and Category B Wide Area IAB-MT | -15 dBm/MHz | +| Medium Range IAB-DU | -25 dBm/MHz | +| Local Area IAB-DU and Local Area IAB-MT | -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 IAB type 1-H + +The ACLR absolute *basic limits* in table 6.6.3.5.2-2+ X (where X = 10log10(NTXU,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 = 10log10(NTXU,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 *IAB 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 IAB-MT or IAB-DU. 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 IAB-MT or IAB-DU 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 *IAB 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 IAB-MT or IAB-DU. 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 IAB-MT or IAB-DU 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 for IAB-DU 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*. + +Unless otherwise stated, the operating band unwanted emission (OBUE) limits for IAB-MT in FR1 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.6.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 IAB-DU and IAB-MT operating in *non-contiguous spectrum*, the requirements apply inside any *sub-block gap*. In addition, for a IAB-MT or IAB-DU 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 -3dB point of the measuring filter closest to the carrier frequency. +- $f_{\text{offset}}$ is the separation between the *channel edge* frequency and the centre of the measuring filter. +- $f_{\text{offset,max}}$ is the offset to the frequency $\Delta f_{\text{OBUE}}$ outside the downlink *operating band* of IAB-DU and uplink *operating band* of IAB-MT, where $\Delta f_{\text{OBUE}}$ is defined in tables 6.6.1-1 and 6.6.1-2. +- $\Delta f_{\text{max}}$ is equal to $f_{\text{offset,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 *IAB RF Bandwidth edges* on each side of the + +*Inter RF Bandwidth gap.* The *basic limit* for *IAB RF Bandwidth edge* is specified in clauses 6.6.4.2.1 to 6.6.4.2.4 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 from the *IAB RF Bandwidth edge* frequency to 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* of IAB-DU, 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 *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 limits* 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 *multi-band connector* of IAB-MT, 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 *basic limit* 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_{OBUE}$ , $f\_offset_{max}$ shall be the offset to the frequency $\Delta f_{OBUE}$ MHz outside the outermost edges of the two supported uplink *operating bands* and the operating band unwanted emission *basic limits* 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 *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 uplink *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 clauses 6.6.4.2.1 to 6.6.4.2.4 below, where in this case: + +- $\Delta f$ is the separation between the *sub-block edge* frequency and the nominal -3 dB point of the measuring filter closest to the *sub-block edge*. +- $f\_offset$ is the separation between the *sub-block edge* frequency and the centre of the measuring filter. +- $f\_offset_{max}$ is equal to the *sub-block gap* bandwidth minus half of the bandwidth of the measuring filter. +- $\Delta f_{max}$ is equal to $f\_offset_{max}$ minus half of the bandwidth of the measuring filter. + +For Wide Area IAB-DU and Wide Area IAB-MT, the requirements of either clause 6.6.4.2.1 (Category A limits) or clause 6.6.4.2.2 (Category B limits) shall apply. + +For Medium Range IAB-DU, the requirements in clause 6.6.4.2.3 shall apply (Category A and B). + +For Local Area IAB-DU and Local Area IAB-MT, the requirements of clause 6.6.4.2.4 shall apply (Category A and B). + +The application of either Category A or Category B *basic limits* shall be the same as for Transmitter spurious emissions 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 *IAB type 1-H* are defined in TS 38.174 [2], clause 6.6.4.2. + +#### 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. + +*IAB 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 *IAB 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. If simultaneous transmission is declared to be supported (see D.IAB-2 in table 4.6-1), when IAB-MT and IAB-DU are transmitting simultaneously, the measurement may be tested on one connector at a time or may be tested in parallel as shown in annex D.1.1. Whichever method is used the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested. + +- 1) Connect the *single-band connector* or *multi-band connector* under test to measurement equipment as shown in annex D.1.1 for *IAB 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. +- 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,TABC}}$ (D.21). Channel set-up shall be according to IAB-DU-FR1-TM1.1 or IAB-MT-FR1-TM1.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) 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 IAB-DU-FR1-TM1.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 IAB-DU and IAB-MT (Category A) + +For IAB-DU and IAB-MT operating in Bands n41 *basic limits* are specified in table 6.6.4.2.1-1: + +**Table 6.6.4.2.1-1: Wide Area IAB-DU and Wide Area IAB-MT 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 limits (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 an IAB-DU and IAB-MT 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 IAB-DU and IAB-MT operating in Bands n77, n78 and n79 *basic limits* are specified in table 6.6.4.2.1-2: + +**Table 6.6.4.2.1-2: Wide Area IAB-DU and Wide Area IAB-MT 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 an IAB-DU and IAB-MT 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 IAB-DU and Wide Area IAB-MT (Category B) + +##### 6.6.4.5.3.1 General + +For Category B Operating band unwanted emissions, the *basic limits* in clause 6.6.4.5.3.2 shall be applied. + +##### 6.6.4.5.3.2 Category B requirements + +For IAB-DU and IAB-MT operating in Bands n41 *basic limits* are specified in table 6.6.4.5.3.2-1: + +**Table 6.6.4.5.3.2-1: Wide Area IAB-DU and IAB-MT 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 limits (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) | 1 MHz | + +NOTE 1: For an IAB-DU and IAB-MT 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_{\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 IAB-DU and IAB-MT operating in Bands n77, n78 and n79 *basic limits* are specified in table 6.6.4.5.3.2-2: + +**Table 6.6.4.5.3.2-2: Wide Area IAB-DU and Wide Area IAB-MT 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 an IAB-DU and IAB-MT 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_{\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.4 Basic limits for Medium Range IAB-DU (Category A and B) + +For Medium Range IAB-DU, *basic limits* are specified in table 6.6.4.5.4-1 to table 6.6.4.5.4-4. + +For the tables in this clause for *IAB type I-H* $P_{\text{rated,x}} = P_{\text{rated,c,cell}} - 10 * \log_{10}(N_{\text{TXU,countedpercell}})$ , + +**Table 6.6.4.5.4-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$ | Basic limits (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}$ | $\text{Min}(P_{\text{rated,x}} - 60 \text{ dB}, -25 \text{ dBm})$ (Note 3) | 100 kHz | + +NOTE 1: For an IAB-DU 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,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-2: 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$ | Basic limits (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 an IAB-DU 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}$ . + +**Table 6.6.4.5.4-3: Medium Range IAB-DU operating band unwanted emission limits, $31 < P_{\text{rated,x}} \leq 38$ dBm (NR bands $> 3$ GHz)** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limit (Note 1, 2) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|----------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | | 100 kHz | +| $5 \text{ MHz} \leq \Delta f < \min(10 \text{ MHz}, \Delta f_{\max})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\max})$ | $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 an IAB-DU 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}$ . + +**Table 6.6.4.5.4-4: Medium Range IAB-DU 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 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 an IAB-DU 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.6.4.5.5 Basic limits for 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 \text{ GHz}$ , *basic limits* are specified in table 6.6.4.5.4-1. + +For Local Area IAB-DU and Local Area IAB-MT in NR bands $\leq 3 \text{ GHz}$ , *basic limits* are specified in table 6.6.4.5.4-2. + +**Table 6.6.4.5.4-1: Local Area IAB-DU and Local Area IAB-MT 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 limits (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 an IAB-DU and IAB-MT 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 * \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: Local Area IAB-DU and Local Area IAB-MT 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$ | 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 an IAB-DU and IAB-MT 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 * \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.6.4.5.5 Basic limits for additional requirements + +##### 6.6.4.5.5.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, the IAB-DU and IAB-MT may have to comply with the applicable emission limits established by FCC Title 47 [7], when deployed in regions where those limits are applied, and under the conditions declared by the manufacturer. + +##### 6.6.4.5.6 IAB type 1-H + +The operating band unwanted emissions requirements for *IAB type 1-H* are that for each *TAB connector TX min cell group* and each applicable *basic limit* in clause 6.6.4.2, 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, counted per cell}})$ . + +NOTE: Conformance to the *IAB type 1-H* operating band unwanted emission requirement can be demonstrated by meeting at least one of the following criteria as determined by the manufacturer: + +- 1) The sum of the emissions power measured on each *TAB connector* in the *TAB connector TX min cell group* shall be less than or equal to the 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 *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 + +For IAB-DU, 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-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 Recommendation ITU-R SM.329 [5]. + +For IAB-MT, 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 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 6.6.1-2. For some *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 [5]. + +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). + +#### 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 *IAB type 1-H* are defined in TS 38.174 [2], clause 6.6.5. + +#### 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}}$ for IAB-DU or $F_{\text{UL\_low}} - \Delta f_{\text{OBUE}}$ for IAB-MT +- T when testing the spurious emissions above $F_{\text{DL\_high}} + \Delta f_{\text{OBUE}}$ for IAB-DU or $F_{\text{UL\_high}} + \Delta f_{\text{OBUE}}$ for IAB-MT; see clause 4.9.1. + +*IAB 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}}$ for IAB-DU or $F_{\text{UL\_low}} - \Delta f_{\text{OBUE}}$ for IAB-MT; $T_{\text{RFBW}}$ when testing the spurious frequencies above $F_{\text{DL\_high}} + \Delta f_{\text{OBUE}}$ for IAB-DU or $F_{\text{UL\_high}} + \Delta f_{\text{OBUE}}$ for IAB-MT 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}}$ for IAB-DU or $F_{\text{UL\_low}} - \Delta f_{\text{OBUE}}$ for IAB-MT of the lowest operating band; $B'_{\text{RFBW\_T}}$ when testing the spurious frequencies above $F_{\text{DL\_high}} + \Delta f_{\text{OBUE}}$ for IAB-DU or $F_{\text{UL\_high}} + \Delta f_{\text{OBUE}}$ for IAB-MT of the highest operating band in multi-band operation, see clause 4.9.1. + +##### 6.6.5.4.2 Procedure + +For *IAB 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.13.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. 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. +- 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 IAB-DU-FR1-TM1.1 or IAB-MT-FR1-TM1.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. + +- 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 *basic 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. + +**Table 6.6.5.5.1.1-1: General IAB-DU and IAB-MT 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 | + +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: For IAB-DU, 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 IAB-MT, 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: This spurious frequency range applies only to *IAB type 1-H*. + +**Table 6.6.5.5.1.1-2: General IAB-DU and IAB-MT 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 | + +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: For IAB-DU, 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 IAB-MT, 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: This spurious frequency range applies only to IAB type 1-H. + +#### 6.6.5.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 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.5. + +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 *basic limits* are provided in table 6.6.5.5.2-1 where requirements for co-existence with the system listed in the first column apply for IAB-MT and IAB-DU. For a *multi-band connector*, the exclusions and conditions in the Note column of table 6.6.5.5.2-1 apply for each supported *operating band*. + +**Table 6.6.5.5.2-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 | Basic limits | Measurement bandwidth | Note | +|-------------------------------------------------|----------------------------------------------|--------------|-----------------------|------| +| GSM900 | 921 – 960 MHz | -57 dBm | 100 kHz | | +| | 876 – 915 MHz | -61 dBm | 100 kHz | | +| DCS1800 | 1805 – 1880 MHz | -47 dBm | 100 kHz | | +| | 1710 – 1785 MHz | -61 dBm | 100 kHz | | +| PCS1900 | 1930 – 1990 MHz | -47 dBm | 100 kHz | | +| | 1850 – 1910 MHz | -61 dBm | 100 kHz | | +| GSM850 or CDMA850 | 869 – 894 MHz | -57 dBm | 100 kHz | | +| | 824 – 849 MHz | -61 dBm | 100 kHz | | +| UTRA FDD | 2110 – 2170 MHz | -52 dBm | 1 MHz | | +| Band I or E-UTRA Band 1 or NR Band n1 | 1920 – 1980 MHz | -49 dBm | 1 MHz | | +| UTRA FDD Band II or E-UTRA Band 2 or NR Band n2 | 1930 – 1990 MHz | -52 dBm | 1 MHz | | +| | 1850 – 1910 MHz | -49 dBm | 1 MHz | | +| UTRA FDD | 1805 – 1880 MHz | -52 dBm | 1 MHz | | + +| System type to co-exist with | Frequency range for co-existence requirement | Basic limits | Measurement bandwidth | Note | +|---------------------------------------------------------------|-----------------------------------------------------|---------------------|------------------------------|-------------| +| Band III or E-UTRA Band 3 or NR Band n3 | 1710 – 1785 MHz | -49 dBm | 1 MHz | | +| UTRA FDD Band IV or E-UTRA Band 4 | 2110 – 2155 MHz | -52 dBm | 1 MHz | | +| | 1710 – 1755 MHz | -49 dBm | 1 MHz | | +| UTRA FDD Band V or E-UTRA Band 5 or NR Band n5 | 869 – 894 MHz | -52 dBm | 1 MHz | | +| | 824 – 849 MHz | -49 dBm | 1 MHz | | +| UTRA FDD Band VI, XIX or E-UTRA Band 6, 18, 19 or NR Band n18 | 860 – 890 MHz | -52 dBm | 1 MHz | | +| | 815 – 830 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 | | +| | 2500 – 2570 MHz | -49 dBm | 1 MHz | | +| UTRA FDD Band VIII or E-UTRA Band 8 or NR Band n8 | 925 – 960 MHz | -52 dBm | 1 MHz | | +| | 880 – 915 MHz | -49 dBm | 1 MHz | | +| UTRA FDD Band IX or E-UTRA Band 9 | 1844.9 – 1879.9 MHz | -52 dBm | 1 MHz | | +| | 1749.9 – 1784.9 MHz | -49 dBm | 1 MHz | | +| UTRA FDD Band X or E-UTRA Band 10 | 2110 – 2170 MHz | -52 dBm | 1 MHz | | +| | 1710 – 1770 MHz | -49 dBm | 1 MHz | | +| UTRA FDD Band XI or XXI or E-UTRA Band 11 or 21 | 1475.9 – 1510.9 MHz | -52 dBm | 1 MHz | | +| | 1427.9 – 1447.9 MHz | -49 dBm | 1 MHz | | +| | 1447.9 – 1462.9 MHz | -49 dBm | 1 MHz | | +| UTRA FDD Band XII or E-UTRA Band 12 or NR Band n12 | 729 – 746 MHz | -52 dBm | 1 MHz | | +| | 699 – 716 MHz | -49 dBm | 1 MHz | | +| UTRA FDD Band XIII or E-UTRA Band 13 | 746 – 756 MHz | -52 dBm | 1 MHz | | +| | 777 – 787 MHz | -49 dBm | 1 MHz | | + +| System type to co-exist with | Frequency range for co-existence requirement | Basic limits | Measurement bandwidth | Note | +|-----------------------------------------------------|-----------------------------------------------------|---------------------|------------------------------|------------------------------------------------------------------------------------| +| UTRA FDD Band XIV or E-UTRA Band 14 or NR band n14 | 758 – 768 MHz | -52 dBm | 1 MHz | | +| | 788 – 798 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 17 | 734 – 746 MHz | -52 dBm | 1 MHz | | +| | 704 – 716 MHz | -49 dBm | 1 MHz | | +| UTRA FDD Band XX or E-UTRA Band 20 or NR Band n20 | 791 – 821 MHz | -52 dBm | 1 MHz | | +| | 832 – 862 MHz | -49 dBm | 1 MHz | | +| UTRA FDD Band XXII or E-UTRA Band 22 | 3510 – 3590 MHz | -52 dBm | 1 MHz | This requirement does not apply to IAB-DU and IAB-MT operating in band n77 or n78. | +| | 3410 – 3490 MHz | -49 dBm | 1 MHz | This requirement does not apply to IAB-DU and IAB-MT operating in band n77 or n78. | +| E-UTRA Band 24 | 1525 – 1559 MHz | -52 dBm | 1 MHz | | +| | 1626.5 – 1660.5 MHz | -49 dBm | 1 MHz | | +| UTRA FDD Band XXV or E-UTRA Band 25 or NR band n25 | 1930 – 1995 MHz | -52 dBm | 1 MHz | | +| | 1850 – 1915 MHz | -49 dBm | 1 MHz | | +| UTRA FDD Band XXVI or E-UTRA Band 26 or NR Band n26 | 859 – 894 MHz | -52 dBm | 1 MHz | | +| | 814 – 849 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 27 | 852 – 869 MHz | -52 dBm | 1 MHz | | +| | 807 – 824 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 28 or NR Band n28 | 758 – 803 MHz | -52 dBm | 1 MHz | | +| | 703 – 748 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 29 or NR Band n29 | 717 – 728 MHz | -52 dBm | 1 MHz | | +| | | | | | +| E-UTRA Band 30 or NR Band n30 | 2350 – 2360 MHz | -52 dBm | 1 MHz | | +| | 2305 – 2315 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 31 or NR Band n31 | 462.5 – 467.5 MHz | -52 dBm | 1 MHz | | +| | 452.5 – 457.5 MHz | -49 dBm | 1 MHz | | +| UTRA FDD band XXXII or E-UTRA band 32 | 1452 – 1496 MHz | -52 dBm | 1 MHz | | +| UTRA TDD Band a) or E-UTRA Band 33 | 1900 – 1920 MHz | -52 dBm | 1 MHz | | + +| System type to co-exist with | Frequency range for co-existence requirement | Basic limits | Measurement bandwidth | Note | +|---------------------------------------------------|-----------------------------------------------------|---------------------|------------------------------|---------------------------------------------------------------------------| +| UTRA TDD Band a) or E-UTRA Band 34 or NR band n34 | 2010 – 2025 MHz | -52 dBm | 1 MHz | | +| 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 | | +| 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 | | +| UTRA TDD Band f) or E-UTRA Band 39 or NR band n39 | 1880 – 1920 MHz | -52 dBm | 1 MHz | | +| UTRA TDD Band e) or E-UTRA Band 40 or NR Band n40 | 2300 – 2400 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 41 or NR Band n41, n90 | 2496 – 2690 MHz | -52 dBm | 1 MHz | This is not applicable IAB-DU and IAB-MT operating in Band n41. | +| E-UTRA Band 42 | 3400 – 3600 MHz | -52 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 | -52 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 | -52 dBm | 1 MHz | | +| 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 | | +| 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 IAB-DU and IAB-MT operating in Band n77 or n78. | +| E-UTRA Band 50 or NR band n50 | 1432 – 1517 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 51 or NR Band n51 | 1427 – 1432 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 53 or NR Band n53 | 2483.5 - 2495 MHz | -52 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 | -52 dBm | 1 MHz | | + +| System type to co-exist with | Frequency range for co-existence requirement | Basic limits | Measurement bandwidth | Note | +|-------------------------------------|-----------------------------------------------------|---------------------|------------------------------|-----------------------------------------------------------------------------------| +| E-UTRA Band 65 or NR Band n65 | 2110 – 2200 MHz | -52 dBm | 1 MHz | | +| | 1920 – 2010 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 66 or NR Band n66 | 2110 – 2200 MHz | -52 dBm | 1 MHz | | +| | 1710 – 1780 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 67 or NR Band n67 | 738 – 758 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 68 | 753 - 783 MHz | -52 dBm | 1 MHz | | +| | 698-728 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 69 | 2570 – 2620 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 70 or NR Band n70 | 1995 – 2020 MHz | -52 dBm | 1 MHz | | +| | 1695 – 1710 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 71 or NR Band n71 | 617 – 652 MHz | -52 dBm | 1 MHz | | +| | 663 – 698 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 72 or NR Band n72 | 461 – 466 MHz | -52 dBm | 1 MHz | | +| | 451 – 456 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 74 or NR Band n74 | 1475 – 1518 MHz | -52 dBm | 1 MHz | | +| | 1427 – 1470 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 75 or NR Band n75 | 1432 – 1517 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 76 or NR Band n76 | 1427 – 1432 MHz | -52 dBm | 1 MHz | | +| NR Band n77 | 3.3 – 4.2 GHz | -52 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 | -52 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 | -52 dBm | 1 MHz | This requirement does not apply to IAB-DU and IAB-MT operating in Band n79 | +| NR Band n80 | 1710 – 1785 MHz | -49 dBm | 1 MHz | | +| NR Band n81 | 880 – 915 MHz | -49 dBm | 1 MHz | | +| NR Band n82 | 832 – 862 MHz | -49 dBm | 1 MHz | | +| NR Band n83 | 703 – 748 MHz | -49 dBm | 1 MHz | | +| NR Band n84 | 1920 – 1980 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 85 or NR Band n85 | 728 – 746 MHz | -52 dBm | 1 MHz | | +| | 698 – 716 MHz | -49 dBm | 1 MHz | | +| NR Band n86 | 1710 – 1780 MHz | -49 dBm | 1 MHz | | +| NR Band n89 | 824 – 849 MHz | -49 dBm | 1 MHz | | +| NR Band n91 | 1427 – 1432 MHz | -52 dBm | 1 MHz | | +| | 832 – 862 MHz | -49 dBm | 1 MHz | | +| NR Band n92 | 1432 – 1517 MHz | -52 dBm | 1 MHz | | +| | 832 – 862 MHz | -49 dBm | 1 MHz | | +| NR Band n93 | 1427 – 1432 MHz | -52 dBm | 1 MHz | | +| | 880 – 915 MHz | -49 dBm | 1 MHz | | +| NR Band n94 | 1432 – 1517 MHz | -52 dBm | 1 MHz | | +| | 880 – 915 MHz | -49 dBm | 1 MHz | | +| NR Band n95 | 2010 – 2025 MHz | -52 dBm | 1 MHz | | + +| System type to co-exist with | Frequency range for co-existence requirement | Basic limits | Measurement bandwidth | Note | +|---------------------------------|----------------------------------------------|--------------|-----------------------|------| +| NR Band n96 | 5925 – 7125 MHz | -52 dBm | 1 MHz | | +| NR Band n97 | 2300 – 2400 MHz | -52 dBm | 1 MHz | | +| NR Band n98 | 1880 – 1920 MHz | -52 dBm | 1 MHz | | +| NR Band n99 | 1626.5 – 1660.5 MHz | -49 dBm | 1 MHz | | +| NR Band n100 | 919.4 – 925 MHz | -52 dBm | 1 MHz | | +| | 874.4 – 880 MHz | -49 dBm | 1 MHz | | +| NR Band n101 | 1900 – 1910 MHz | -52 dBm | 1 MHz | | +| NR Band n102 | 5925 – 6425 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 103 | 757 – 758 MHz | -52 dBm | 1 MHz | | +| | 787 – 788 MHz | -49 dBm | 1 MHz | | +| NR Band n104 | 6425 – 7125 MHz | -52 dBm | 1 MHz | | +| NR Band n105 | 612 – 652 MHz | -52 dBm | 1 MHz | | +| | 663 – 703 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 106 or NR Band n106 | 935 – 940 MHz | -52 dBm | 1 MHz | | +| | 896 – 901 MHz | -49 dBm | 1 MHz | | +| NR Band n109 | 1432 – 1517 MHz | -52 dBm | 1 MHz | | +| | 703 – 733 MHz | -49 dBm | 1 MHz | | + +NOTE 1: As defined in the scope for spurious emissions in this clause the co-existence requirements in table 6.6.5.2.2-1 do not apply for the $\Delta f_{\text{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.6.5.2.2-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.6.5.5.3 Co-location with base stations and IAB-nodes + +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. + +The *basic limits* are in table 6.6.5.2.3-1 for an IAB-DU and IAB-MT. Requirements for co-location with a system listed in the first column apply, depending on the declared IAB-DU and IAB-MT class. For a *multi-band connector*, the exclusions and conditions in the Note column of table 6.6.5.2.3-1 shall apply for each supported *operating band*. + +**Table 6.6.5.5.3-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 | Basic 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 | -98 dBm | -91 dBm | -70 dBm | 100 kHz | | +| DCS1800 | 1710 – 1785 MHz | -98 dBm | -91 dBm | -80 dBm | 100 kHz | | + +| Co-located system | Frequency range for co-location requirement | Basic limits | | | Measurement bandwidth | Note | +|-----------------------------------------------------|---------------------------------------------|-------------------------|-----------|-------------------------|-----------------------|--------------------------------------------------------------------------| +| | | WA IAB-DU and WA IAB-MT | MR IAB-DU | LA IAB-DU and LA IAB-MT | | | +| 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 | | +| 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 | 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 | | +| 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 IAB-DU and IAB-MT operating in Band n77 or n78 | +| E-UTRA Band 23 | 2000 – 2020 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 24 | 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 | | + +| Co-located system | Frequency range for co-location requirement | Basic limits | | | Measurement bandwidth | Note | +|---------------------------------------------------|---------------------------------------------|-------------------------|-----------|-------------------------|-----------------------|--------------------------------------------------------------------------| +| | | WA IAB-DU and WA IAB-MT | MR IAB-DU | LA IAB-DU and LA IAB-MT | | | +| 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 | | +| 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 | | +| 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 | | +| UTRA TDD Band f) or E-UTRA Band 39 or NR band n39 | 1880 – 1920MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| UTRA TDD Band e) or E-UTRA Band 40 or NR Band n40 | 2300 – 2400MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| 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 IAB-DU and IAB-MT operating in Band n41 | +| E-UTRA Band 42 | 3400 – 3600 MHz | -96 dBm | -91 dBm | -88 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 | -96 dBm | -91 dBm | -88 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 | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| 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 | | +| E-UTRA Band 48 or NR Band n48 | 3550 – 3700 MHz | -96 dBm | -91 dBm | -88 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 | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 51 or NR Band n51 | 1427 – 1432 MHz | N/A | N/A | -88 dBm | 100 kHz | | +| 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 IAB-DU and IAB-MT operating in Band n41 | +| E-UTRA Band 54 or NR Band n54 | 1670 – 1675 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 65 or NR Band n65 | 1920 – 2010 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | + +| Co-located system | Frequency range for co-location requirement | Basic limits | | | Measurement bandwidth | Note | +|---------------------------------|---------------------------------------------|-------------------------|-----------|-------------------------|-----------------------|--------------------------------------------------------------------------| +| | | WA IAB-DU and WA IAB-MT | MR IAB-DU | LA IAB-DU and LA IAB-MT | | | +| 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 | | +| NR Band n77 | 3.3 – 4.2 GHz | -96 dBm | -91 dBm | -88 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 | -96 dBm | -91 dBm | -88 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 | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to IAB-DU and IAB-MT operating in Band n79 | +| 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 85 | 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 – 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 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 | | +| 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.2.3-1 do not apply for the frequency range extending $\Delta f_{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 [8]. + +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.6.5.6 IAB type 1-H + +The Tx spurious emissions requirements for *IAB type 1-H* are that for each *TAB connector TX min cell group* and each applicable *basic limit* in clause 6.6.5.2, the power summation of 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, counted per cell}})$ , unless stated differently in regional regulation. + +NOTE: Conformance to the *IAB 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 *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 *IAB 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 *IAB 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 *IAB type 1-H*. + +For *IAB 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 *IAB type 1-H* is defined in TS 38.174 [2], clause 6.7.2. + +### 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. + +*IAB 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. + +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. + +### 6.7.4.2 Procedure + +For *IAB 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.2. If IAB simultaneous transmission is declared to be supported (see D.IAB-2 in table 4.6-1), connector(s) for IAB-MT and IAB-DU may be tested one at a time or may be tested in parallel as shown in annex D.1.2. 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 *IAB type 1-H*. All connectors not under test shall be terminated. +- 2) The measurement device characteristics shall be: + - Detection mode: True RMS. +- 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,TABc}}$ for *IAB type 1-H* (D.21). Channel set-up shall be according to IAB-DU-FR1-TM 1.1 for IAB-DU and IAB-MT-FR1-TM1.1 for IAB-MT. + +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 IAB-DU and IAB-MT. + +- 4) For IAB 1-H, generate the interfering signal according to IAB-DU-FR1-TM1.1 for IAB-DU and IAB-MT-FR1-TM1.1 for IAB-MT, 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 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 *IAB 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 *IAB 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 IAB type 1-H + +#### 6.7.5.1.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.1.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 *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 *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-DU channel bandwidth* and *IAB-MT 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.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 | +| 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 | 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.1.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.1.2-1. + +**Table 6.7.5.1.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 IAB-DU channel bandwidth or IAB-MT channel bandwidth and SCS as the wanted signal (Note 1). | +| Interfering signal level | Power level declared by the IAB manufacturer (Note 2). | +| Frequency offset between interfering signal and wanted signal | 0 MHz | +| NOTE 1: The interfering signal shall be incoherent with the wanted signal. | | +| NOTE 2: The declared interfering signal power level at each TAB connector is the sum of the co-channel leakage power coupled via the combined RDN and Antenna Array from all the other TAB connectors , but does not comprise power radiated from the Antenna Array and reflected back from the environment. The power at each of the interfering TAB connectors is $P_{\text{rated,c,TABC}}$ . | | + +### 6.7.5.1.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.1.3-1. + +**Table 6.7.5.1.3-1 Interfering and wanted signals for the additional transmitter intermodulation requirement for Band n41** + +| 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. | | + +## 7 Conducted receiver characteristics (IAB-DU and IAB-MT) + +### 7.1 General + +### 7.2 Reference sensitivity level + +#### 7.2.1 Definition and applicability + +The reference sensitivity power level $P_{\text{REFSENS}}$ is the minimum mean power received at the *TAB connector* for *IAB 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 *IAB type 1-H*: + +For *IAB-DU* is in TS 38.174 [2], clause 7.2.1. + +For *IAB-MT* is in TS 38.174 [2], clause 7.2.2. + +## 7.2.3 Test purpose + +To verify that for each *IAB 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. + +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. +- 2) Start the signal generator for the wanted signal to transmit the Fixed Reference Channels for reference sensitivity in clause 7.2.5 and according to annex A.1. +- 3) Set the signal generator for the wanted signal power as specified in clause 7.2.5. +- 4) Measure the throughput according to annex A.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.2.5 Test requirements + +### 7.2.5.1 Test requirements for *IAB-DU* + +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-1 for Wide Area IAB-DU, in table 7.2.5.1-2 for Medium Range IAB-DU and in table 7.2.5.1-3 for Local Area IAB-DU. + +**Table 7.2.5.1-1: NR Wide Area IAB-DU reference sensitivity levels** + +| IAB-DU channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel | Reference sensitivity power level, PREFSENS (dBm) | | | +|-------------------------------------------------|----------------------------------|--------------------------------------|---------------------------------------------------------------------|---------------------------------|---------------------------------| +| | | | f ≤ 3.0 GHz | 3.0 GHz < f ≤ 4.2 GHz | 4.2 GHz < f ≤ 6.0 GHz | +| 10, 15 | 15 | G-FR1-A1-1 (Note 1) | -101 | -100.7 | -100.5 | +| 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 | +| 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: *PREFSENS* is the power level of a single instance of the reference measurement channel. This requirement shall be met for each consecutive application of a single instance of the reference measurement channel mapped to disjoint frequency ranges with a width corresponding to the number of resource blocks of the reference measurement channel each, except for one instance that might overlap one other instance to cover the full *IAB-DU channel bandwidth*. + +**Table 7.2.5.1-2: NR Medium Range IAB-DU reference sensitivity levels** + +| IAB-DU channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel | Reference sensitivity power level, PREFSENS (dBm) | | | +|-------------------------------------------------|----------------------------------|--------------------------------------|---------------------------------------------------------------------|---------------------------------|---------------------------------| +| | | | f ≤ 3.0 GHz | 3.0 GHz < f ≤ 4.2 GHz | 4.2 GHz < f ≤ 6.0 GHz | +| 10, 15 | 15 | G-FR1-A1-1 (Note 1) | -96 | -95.7 | -95.5 | +| 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 | +| 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: *PREFSENS* is the power level of a single instance of the reference measurement channel. This requirement shall be met for each consecutive application of a single instance of the reference measurement channel mapped to disjoint frequency ranges with a width corresponding to the number of resource blocks of the reference measurement channel each, except for one instance that might overlap one other instance to cover the full *IAB-DU channel bandwidth*. + +**Table 7.2.5.1-3: NR Local Area IAB-DU reference sensitivity levels** + +| IAB-DU channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel | Reference sensitivity power level, PREFSENS (dBm) | | | +|-------------------------------------------------|----------------------------------|--------------------------------------|---------------------------------------------------------------------|---------------------------------|---------------------------------| +| | | | f ≤ 3.0 GHz | 3.0 GHz < f ≤ 4.2 GHz | 4.2 GHz < f ≤ 6.0 GHz | +| 10, 15 | 15 | G-FR1-A1-1 (Note 1) | -93 | -92.7 | -92.5 | +| 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 | +| 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: *PREFSENS* is the power level of a single instance of the reference measurement channel. This requirement shall be met for each consecutive application of a single instance of the reference measurement channel mapped to disjoint frequency ranges with a width corresponding to the number of resource blocks of the reference measurement channel each, except for one instance that might overlap one other instance to cover the full *IAB-DU channel bandwidth*. + +### 7.2.5.2 Test requirements for *IAB-MT* + +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.2-1 for Wide Area IAB-MT and in table 7.2.5.2-2 for Local Area IAB-MT. + +**Table 7.2.5.2-1: Wide Area IAB-MT reference sensitivity levels** + +| IAB-MT channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel | Reference sensitivity power level, PREFSENS (dBm) | | | +|-------------------------------------------------|----------------------------------|--------------------------------------|---------------------------------------------------------------------|---------------------------------|---------------------------------| +| | | | f ≤ 3.0 GHz | 3.0 GHz < f ≤ 4.2 GHz | 4.2 GHz < f ≤ 6.0 GHz | +| 10, 15 | 30 | G-FR1-A1-22 (Note 1) | -101.3 | -101 | -100.8 | +| 10, 15 | 60 | G-FR1-A1-23 (Note 1) | -98.3 | -98 | -97.8 | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-25 (Note 1) | -94.7 | -94.4 | -94.2 | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-26 (Note 1) | -94.9 | -94.6 | -94.4 | + +NOTE 1: *PREFSENS* is the power level of a single instance of the reference measurement channel. This requirement shall be met for each consecutive application of a single instance of the reference measurement channel mapped to disjoint frequency ranges with a width corresponding to the number of resource blocks of the reference measurement channel each, except for one instance that might overlap one other instance to cover the full *IAB-MT channel bandwidth*. + +**Table 7.2.5.2-2: Local Area IAB-MT reference sensitivity levels** + +| IAB-MT 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 | +| 10, 15 | 30 | G-FR1-A1-22 (Note 1) | -93.3 | -93 | -92.8 | +| 10, 15 | 60 | G-FR1-A1-23 (Note 1) | -90.3 | -90 | -89.8 | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-25 (Note 1) | -86.7 | -86.4 | -86.2 | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-26 (Note 1) | -86.9 | -86.6 | -86.4 | + +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 IAB-MT 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 *TAB connector* for IAB-DU inside the received IAB-DU 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 IAB type 1-H for IAB-DU is in TS 38.174 [2], clause 7.3.1. + +### 7.3.3 Test purpose + +To verify that the IAB type 1-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. + +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 . + +- 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 IAB class. +- 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 IAB class. +- 4) Measure the throughput according to annex A.2. + +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 IAB-DU, in table 7.3.2-2 for Medium Range IAB-DU and in table 7.3.2-3 for Local Area IAB-DU. + +**Table 7.3.5-1: Wide Area IAB-DU dynamic range** + +| IAB-DU 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-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 *IAB-DU channel bandwidth*. + +**Table 7.3.5-2: Medium Range IAB-DU dynamic range** + +| IAB-DU 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-1 | -65.4 | -74.3 | AWGN | +| | 30 | G-FR1-A2-2 | -66.1 | | | +| | 60 | G-FR1-A2-3 | -63.1 | | | +| 15 | 15 | G-FR1-A2-1 | -65.4 | -72.5 | AWGN | +| | 30 | G-FR1-A2-2 | -66.1 | | | +| | 60 | G-FR1-A2-3 | -63.1 | | | +| 20 | 15 | G-FR1-A2-4 | -59.2 | -71.2 | AWGN | +| | 30 | G-FR1-A2-5 | -59.2 | | | +| | 60 | G-FR1-A2-6 | -59.5 | | | +| 25 | 15 | G-FR1-A2-4 | -59.2 | -70.2 | AWGN | +| | 30 | G-FR1-A2-5 | -59.2 | | | +| | 60 | G-FR1-A2-6 | -59.5 | | | +| 30 | 15 | G-FR1-A2-4 | -59.2 | -69.4 | AWGN | +| | 30 | G-FR1-A2-5 | -59.2 | | | +| | 60 | G-FR1-A2-6 | -59.5 | | | +| 35 | 15 | G-FR1-A2-4 | -59.2 | -68.7 | AWGN | +| | 30 | G-FR1-A2-5 | -59.2 | | | +| | 60 | G-FR1-A2-6 | -59.5 | | | +| 40 | 15 | G-FR1-A2-4 | -59.2 | -68.1 | AWGN | +| | 30 | G-FR1-A2-5 | -59.2 | | | +| | 60 | G-FR1-A2-6 | -59.5 | | | +| 45 | 15 | G-FR1-A2-4 | -59.2 | -67.6 | AWGN | +| | 30 | G-FR1-A2-5 | -59.2 | | | +| | 60 | G-FR1-A2-6 | -59.5 | | | +| 50 | 15 | G-FR1-A2-4 | -59.2 | -67.1 | AWGN | +| | 30 | G-FR1-A2-5 | 59.8 | | | +| | 60 | G-FR1-A2-6 | -59.5 | | | +| 60 | 30 | G-FR1-A2-5 | -59.2 | -66.3 | AWGN | +| | 60 | G-FR1-A2-6 | -59.5 | | | +| 70 | 30 | G-FR1-A2-5 | -59.2 | -65.7 | AWGN | +| | 60 | G-FR1-A2-6 | -59.5 | | | +| 80 | 30 | G-FR1-A2-5 | -59.2 | -65.1 | AWGN | +| | 60 | G-FR1-A2-6 | -59.5 | | | +| 90 | 30 | G-FR1-A2-5 | -59.2 | -64.5 | AWGN | +| | 60 | G-FR1-A2-6 | -59.5 | | | +| 100 | 30 | G-FR1-A2-5 | -59.2 | -64.1 | AWGN | +| | 60 | G-FR1-A2-6 | -59.5 | | | + +NOTE: The wanted signal mean power is the power level of a single instance of the corresponding reference measurement channel. This requirement shall be met for each consecutive application of a single instance of the reference measurement channel mapped to disjoint frequency ranges with a width corresponding to the number of resource blocks of the reference measurement channel each, except for one instance that might overlap one other instance to cover the full *IAB-DU channel bandwidth*. + +**Table 7.3.5-3: Local Area IAB-DU dynamic range** + +| IAB-DU 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-1 | -62.4 | -71.3 | AWGN | +| | 30 | G-FR1-A2-2 | -63.1 | | | +| | 60 | G-FR1-A2-3 | -60.1 | | | +| 15 | 15 | G-FR1-A2-1 | -62.4 | -69.5 | AWGN | +| | 30 | G-FR1-A2-2 | -63.1 | | | +| | 60 | G-FR1-A2-3 | -60.1 | | | +| 20 | 15 | G-FR1-A2-4 | -56.2 | -68.2 | AWGN | +| | 30 | G-FR1-A2-5 | -56.2 | | | +| | 60 | G-FR1-A2-6 | -56.5 | | | +| 25 | 15 | G-FR1-A2-4 | -56.2 | -67.2 | AWGN | +| | 30 | G-FR1-A2-5 | -56.2 | | | +| | 60 | G-FR1-A2-6 | -56.5 | | | +| 30 | 15 | G-FR1-A2-4 | -56.2 | -66.4 | AWGN | +| | 30 | G-FR1-A2-5 | -56.2 | | | +| | 60 | G-FR1-A2-6 | -56.5 | | | +| 35 | 15 | G-FR1-A2-4 | -56.2 | -65.7 | AWGN | +| | 30 | G-FR1-A2-5 | -56.2 | | | +| | 60 | G-FR1-A2-6 | -56.5 | | | +| 40 | 15 | G-FR1-A2-4 | -56.2 | -65.1 | AWGN | +| | 30 | G-FR1-A2-5 | -56.2 | | | +| | 60 | G-FR1-A2-6 | -56.5 | | | +| 45 | 15 | G-FR1-A2-4 | -56.2 | -64.6 | AWGN | +| | 30 | G-FR1-A2-5 | -56.2 | | | +| | 60 | G-FR1-A2-6 | -56.5 | | | +| 50 | 15 | G-FR1-A2-4 | -56.2 | -64.1 | AWGN | +| | 30 | G-FR1-A2-5 | -56.2 | | | +| | 60 | G-FR1-A2-6 | -56.5 | | | +| 60 | 30 | G-FR1-A2-5 | -56.2 | -63.3 | AWGN | +| | 60 | G-FR1-A2-6 | -56.5 | | | +| 70 | 30 | G-FR1-A2-5 | -56.2 | -62.7 | AWGN | +| | 60 | G-FR1-A2-6 | -56.5 | | | +| 80 | 30 | G-FR1-A2-5 | -56.2 | -62.1 | AWGN | +| | 60 | G-FR1-A2-6 | -56.5 | | | +| 90 | 30 | G-FR1-A2-5 | -56.2 | -61.5 | AWGN | +| | 60 | G-FR1-A2-6 | -56.5 | | | +| 100 | 30 | G-FR1-A2-5 | -56.2 | -61.1 | AWGN | +| | 60 | G-FR1-A2-6 | -56.5 | | | + +NOTE: The wanted signal mean power is the power level of a single instance of the corresponding reference measurement channel. This requirement shall be met for each consecutive application of a single instance of the reference measurement channel mapped to disjoint frequency ranges with a width corresponding to the number of resource blocks of the reference measurement channel each, except for one instance that might overlap one other instance to cover the full *IAB-DU 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 *TAB connector* for *IAB type 1-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 *IAB type 1-H*: + +For *IAB-DU* are in TS 38.174 [2], clause 7.4.1.2. + +For *IAB-MT* are in TS 38.174 [2], clause 7.4.1.3. + +#### 7.4.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.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. + +*IAB 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'}}$ and $B'_{\text{RFBW\_T}}$ 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 *IAB 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 *IAB type 1-H*. +- 2) For IAB-DU, set the signal generator for the wanted signal to transmit as specified in table 7.4.1.5.1-1. + +For IAB-MT, set the signal generator for the wanted signal to transmit as specified in table 7.4.1.5.2-1. + +For simultaneous operation tests, set the signal generator for the wanted signal of IAB-DU to transmit as specified in table 7.4.1.5.1-1 and for the wanted signal of IAB-MT to transmit in table 7.4.1.5.2-1. + +- 3) For IAB-DU, set the signal generator for the interfering signal to transmit at the frequency offset and as specified in table 7.4.1.5.1-1 and 7.4.1.5.1-2. For IAB-MT, set the signal generator for the interfering signal to transmit at the frequency offset and as specified in table 7.4.1.5.2-1 and 7.4.1.5.2-2. + +For simultaneous operation tests, set the signal generator for the interfering signal to transmit at the frequency offset and as specified in table 7.4.1.5.2-1 and 7.4.1.5.2-2. + +- 4) Measure the throughput according to annex A.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.4.1.5 Test requirements + +##### 7.4.1.5.1 Test requirements for IAB-DU + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel. + +For IAB, the wanted and the interfering signal coupled to the *IAB type 1-H TAB connector* are specified in table 7.4.1.5.1-1 and the frequency offset between the wanted and interfering signal in table 7.4.1.5.1-2 for ACS. The reference measurement channel for the wanted signal is identified in table 7.2.5.1-1, 7.2.5.1-2 and 7.2.5.1-3 for each channel bandwidth and further specified in annex A.1. The characteristics of the interfering signal is further specified in annex F. + +The ACS requirement is applicable 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 a IAB 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.1-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.1-2. The interfering signal offset is defined relative to the *IAB RF Bandwidth edges* inside the Inter RF Bandwidth gap + +Conducted requirement is defined at the *TAB connector* for *IAB type 1-H*. + +**Table 7.4.1.5.1-1: IAB ACS requirement** + +| IAB-DU channel bandwidth of the lowest/highest carrier received (MHz) | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------|-----------------------------------------------------------------------------| +| 10, 15, 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 (Note 1) | $P_{\text{REFSENS}} + 6$ dB | Wide Area IAB-DU: -52
Medium Range IAB-DU: -47
Local Area IAB-DU: -44 | +| NOTE 1: The SCS for the lowest/highest carrier received is the lowest SCS supported by the IAB for that bandwidth. | | | +| NOTE 2: $P_{\text{REFSENS}}$ depends on the RAT. For NR, $P_{\text{REFSENS}}$ depends also on the IAB-DU channel bandwidth as specified in TS 38.174 [2], table 7.2.2-1, 7.2.2-2 and 7.2.2-3. | | | + +**Table 7.4.1.5.1-2: IAB ACS interferer frequency offset values** + +| IAB-DU channel bandwidth of the lowest/highest carrier received (MHz) | 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 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.4.1.5.2 Test requirements for IAB-MT + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel. + +For IAB-MT, the wanted and the interfering signal coupled to the *IAB type 1-H TAB connector* are specified in table 7.4.1.5.1-1 and the frequency offset between the wanted and interfering signal in table 7.4.1.5.2-2 for ACS. The reference measurement channel for the wanted signal is identified in table 7.2.5.2-1 and 7.2.5.2-2 for each *IAB-MT channel bandwidth* and further specified in annex A.1. The characteristics of the interfering signal is further specified in annex F. + +The ACS requirement is applicable 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 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-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-2. The interfering signal offset is defined relative to the *IAB-MT RF Bandwidth* edges inside the *Inter RF Bandwidth gap*. + +Minimum conducted requirement is defined at the *TAB connector* for *IAB type 1-H*. + +**Table 7.4.1.5.2-1: ACS requirement for IAB-MT** + +| IAB-MT channel bandwidth of the lowest/highest carrier received (MHz) | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | +|-----------------------------------------------------------------------------------------------------------------------|---------------------------------------|-------------------------------------------------| +| 10, 15, 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 (Note 1) | $P_{\text{REFSENS}} + 6$ dB | Wide Area IAB-MT: -52
Local Area IAB-MT: -44 | +| NOTE 1: The SCS for the lowest/highest carrier received is the lowest SCS supported by the IAB-MT for that bandwidth. | | | + +**Table 7.4.1.5.2-2: IAB-MT ACS interferer frequency offset values** + +| 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$ | | +| 30 | $\pm 9.4725$ | 20 MHz CP-OFDM NR signal
15 kHz SCS, 100 RBs | +| 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.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 *TAB connector* for *IAB 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 requirement for *IAB type 1-H*: + +For *IAB-DU* are in TS 38.174 [2], clause 7.4.2.2. + +For *IAB-MT* are in TS 38.174 [2], clause 7.4.2.3. + +### 7.4.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.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 + +*IAB 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'RFBW}}$ and $B'_{\text{RFBW\_T'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.4.2.4.2 Procedure for general blocking + +The minimum requirement is applied to all connectors under test. + +For *IAB 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 *IAB type 1-H*. +- 2) For IAB-DU, set the signal generator for the wanted signal to transmit as specified in table 7.4.2.5.1-1. + +For IAB-MT, set the signal generator for the wanted signal to transmit as specified in table 7.4.2.5.2-1. + +For simultaneous operation tests, set the signal generator for the wanted signal of IAB-DU to transmit as specified in table 7.4.2.5.1-1 and for the wanted signal of IAB-MT to transmit in table 7.4.2.5.2-1. 3) For IAB-DU, set the signal generator for the interfering signal to transmit at the frequency offset and as specified in table 7.4.2.5.1-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-1. + +For IAB-MT, set the signal generator for the interfering signal to transmit at the frequency offset and as specified in table 7.4.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 as specified in table 7.4.2.5.2-1. + +For simultaneous operation tests, set the signal generator for the interfering signal to transmit at the frequency offset and as specified in table 7.4.2.5.2-1. + +- 4) Measure the throughput according to annex A.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.4.2.4.3 Procedure for narrowband blocking + +The minimum requirement is applied to all connectors under test. + +For *IAB 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 *IAB type 1-H*. +- 2) For IAB-DU, set the signal generator for the wanted signal to transmit as specified in table 7.4.2.5.1-2. + +For IAB-MT, set the signal generator for the wanted signal to transmit as specified in table 7.4.2.5.2-2. + +For simultaneous operation tests, set the signal generator for the wanted signal of IAB-DU to transmit as specified in table 7.4.2.5.1-2 and for the wanted signal of IAB-MT to transmit in table 7.4.2.5.2-2.3) For IAB-DU, set the signal generator for the interfering signal to transmit at the frequency offset and as specified in table 7.4.2.5.1-2 and 7.4.2.5.1-3. 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.1-3. + +For IAB-MT, set the signal generator for the interfering signal to transmit at the frequency offset and as specified in table 7.4.2.5.2-2 and 7.4.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.4.2.5.2-3. + +For simultaneous operation tests, set the signal generator for the interfering signal to transmit at the frequency offset and as specified in table 7.4.2.5.2-2 and 7.4.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.4.2.5.2-3.4) Measure the throughput according to annex A.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.4.2.5 Test requirements + +##### 7.4.2.5.1 Test requirements for IAB-DU + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel, with a wanted and an interfering signal coupled to *IAB type 1-H TAB connector* using the parameters in tables 7.4.2.5.1-1, 7.4.2.5.1-2 and 7.4.2.5.1-3 for general blocking and narrowband blocking requirements. The reference measurement channel for the wanted signal is identified in clause 7.2.5.1 for each channel bandwidth and further specified in annex A.1. The characteristics of the interfering signal is further specified in annex E. + +The 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 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 *IAB type 1-H* is defined in table 7.4.2.5.1-0. + +Minimum conducted requirement is defined at the *TAB connector* for *IAB type 1-H*. + +**Table 7.4.2.5.1-0: $\Delta f_{\text{OOB}}$ offset for NR operating bands** + +| IAB-DU type | Operating band characteristics | $\Delta f_{\text{OOB}}$ (MHz) | +|---------------------|------------------------------------------------------------------------|-------------------------------| +| IAB type 1-H | $F_{\text{UL\_high}} - F_{\text{UL\_low}} < 100$ MHz | 20 | +| | $100$ MHz $\leq F_{\text{UL\_high}} - F_{\text{UL\_low}} \leq 900$ MHz | 60 | +| | $100$ MHz $\leq F_{\text{UL\_high}} - F_{\text{UL\_low}} \leq 900$ MHz | 60 | + +For a IAB 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-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-1. + +For a IAB 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.1-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.1-3. The interfering signal offset is defined relative to the *IAB RF Bandwidth edges* inside the *Inter RF Bandwidth gap*. + +**Table 7.4.2.5.1-1: IAB general blocking requirement** + +| 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-DU RF Bandwidth edge or sub-block edge inside a sub-block gap (MHz) | Type of interfering signal | +|-----------------------------------------------------------------------|--------------------------------|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------| +| 10, 15, 20 | $P_{\text{REFSENS}} + 6$ dB | Wide Area IAB-DU: -43
Medium Range IAB-DU: -38
Local Area IAB-DU: -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}} + 6$ dB | Wide Area IAB-DU: -43
Medium Range IAB-DU: -38
Local Area IAB-DU: -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 *IAB-DU channel bandwidth* as specified in TS 38.174 [2], table 7.2.2-1, 7.2.2-2 and 7.2.2-3. + +**Table 7.4.2.5.2-2: IAB-DU narrowband blocking requirement** + +| IAB-DU channel bandwidth of the lowest/highest carrier received (MHz) | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | +|-----------------------------------------------------------------------|--------------------------------|-----------------------------------------------------------------------------| +| 10, 15, 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100
(Note 1) | $P_{\text{REFSENS}} + 6$ dB | Wide Area IAB-DU: -49
Medium Range IAB-DU: -44
Local Area IAB-DU: -41 | + +NOTE 1: The SCS for the lowest/highest carrier received is the lowest SCS supported by the IAB-DU for that *IAB-DU channel bandwidth* + +NOTE 2: $P_{\text{REFSENS}}$ depends on the *IAB-DU channel bandwidth* as specified in TS 38.174 [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.1-3: IAB-DU narrowband blocking interferer frequency offsets** + +| IAB-DU channel bandwidth of the lowest/highest carrier received (MHz) | Interfering RB centre frequency offset to the lower/upper IAB-DU 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 positioned at the stated offset, the *channel bandwidth* of the interfering signal is located adjacently to the lower/upper *IAB-DU 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.2 Test requirements for IAB-MT + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel, with a wanted and an interfering signal coupled to *IAB type 1-H TAB connector* using the parameters in tables 7.4.2.5.2-1, 7.4.2.5.2-2 and 7.4.2.5.2-3 for general blocking and narrowband blocking requirements. The reference measurement channel for the wanted signal is identified in clause 7.2.2 for each *IAB-MT channel bandwidth* and further specified in annex A.1. The characteristics of the interfering signal is further specified in annex E. + +The 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*. + +The 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 *wide area IAB-MT* is defined in table 7.4.2.5.2-0. + +Minimum conducted requirement is defined at the *TAB connector* for *IAB-MT*. + +**Table 7.4.2.5.2-0: $\Delta f_{\text{OOB}}$ offset for NR operating bands** + +| IAB-MT type | Operating band characteristics | $\Delta f_{\text{OOB}}$ (MHz) | +|--------------|----------------------------------------------------------------------|-------------------------------| +| IAB type 1-H | $F_{\text{DL,high}} - F_{\text{DL,low}} < 100$ MHz | 20 | +| | $100$ MHz $\leq F_{\text{DL,high}} - F_{\text{DL,low}} \leq 900$ MHz | 60 | + +For an IAB-MT 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.2-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 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 Table 7.4.2.5.2-1. + +For an IAB-MT operating in *non-contiguous spectrum* within any *operating band*, the narrowband blocking requirement shall apply 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.2-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 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.2.5.2-3. The interfering signal offset is defined relative to the *IAB-MT RF Bandwidth* edges inside the *Inter RF Bandwidth gap*. + +**Table 7.4.2.5.2-1: IAB-MT general blocking requirement** + +| 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 | $P_{\text{REFSENS}} + 6$ dB | Wide Area IAB-MT: -43
Local Area IAB-MT: -35 | $\pm 7.5$ | 5 MHz CP-OFDM NR signal
15 kHz SCS, 25 RBs | +| 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | $P_{\text{REFSENS}} + 6$ dB | Wide Area IAB-MT: -43
Local Area IAB-MT: -35 | $\pm 30$ | 20 MHz CP-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 IAB-MT *channel bandwidth* as specified in tables 7.2.2-1, 7.2.2-2. + +**Table 7.4.2.5.2-2: IAB-MT narrowband blocking requirement** + +| IAB-MT channel bandwidth of the lowest/highest carrier received (MHz) | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | +|---------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|-------------------------------------------------| +| 10, 15, 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 (Note 1) | $P_{\text{REFSENS}} + 6$ dB | Wide Area IAB-MT: -49
Local Area IAB-MT: -41 | +| NOTE 1: The SCS for the lowest/highest carrier received is the lowest SCS supported by the IAB-MT for that IAB-MT channel bandwidth | | | +| NOTE 2: $P_{\text{REFSENS}}$ depends on the IAB-MT channel bandwidth as specified in tables 7.2.2-1 and 7.2.2-2. | | | +| NOTE 3: 7.5 kHz shift is not applied to the wanted signal. | | | + +**Table 7.4.2.5.2-3: IAB-MT narrowband blocking interferer frequency offsets** + +| 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 | $\pm(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 | $\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 CP-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 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 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 *TAB connector* for *IAB 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 requirement for *IAB type 1-H*: + +For *IAB-DU* are defined in TS 38.174 [2], clause 7.5.3. + +For *IAB-MT* are defined in TS 38.174 [2], clause 7.5.5. + +Co-location minimum requirements for *IAB type 1-H*: + +For *IAB-DU* are defined in TS 38.174 [2], clause 7.5.4. + +For *IAB-MT* are defined in TS 38.174 [2], clause 7.5.6. + +### 7.5.3 Test purpose + +To verify the ability of the receiver to receive a wanted signal at its assigned channel at the *TAB connector* for *IAB 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.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 + +*IAB 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'}}$ and $B'_{\text{RFBW\_T'}}$ 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 *IAB 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 *IAB type 1-H*. +- 2) For IAB-DU, 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. + +For IAB-MT, set the signal generator for the wanted signal as defined in clause 7.5.5 to transmit as specified in table 7.5.5.3-2 and 7.5.5.4-1. + +For simultaneous operation tests, set the signal generator for the wanted signal of IAB-DU to transmit as specified in table 7.5.5.1-1 and 7.5.5.2-1 and for the wanted signal of IAB-MT to transmit in table 7.5.5.3-2 and 7.5.5.4-1.3) + +For IAB-DU, 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 than 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. + +For IAB-MT, set the Signal generator for the interfering signal to transmit at the frequency offset and as specified in table 7.5.5.3-2 and 7.5.5.4-1. The CW interfering signal shall be swept with a step size of 1 MHz over than 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. + +For simultaneous operation tests, set the signal generator for the interfering signal to transmit at the frequency offset and as specified in table 7.5.5.3-2 and 7.5.5.4-1. The CW interfering signal shall be swept with a step size of 1 MHz over than 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. + +- 4) Measure the throughput according to annex A.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.5.5 Test requirements + +### 7.5.5.1 General requirements for IAB-DU + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel, with a wanted and an interfering signal coupled to *IAB 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 *IAB 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. The $\Delta f_{OOB}$ for *IAB type 1-H* is defined in table 7.4.2.5.1-0. + +Minimum conducted requirement is defined at the *TAB connector* for *IAB type 1-H*. + +For a IAB 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 *IAB-DU channel bandwidth* as specified in TS 38.174 [2], tables 7.2.2-1, 7.2.2-2 and 7.2.2-3. + +### 7.5.5.2 Co-location requirements for IAB-DU + +This additional blocking requirement may be applied for the protection of NR IAB receivers when GSM, CDMA, UTRA, E-UTRA BS or NR IAB operating in a different frequency band are co-located with a NR IAB. The requirement is applicable to all channel bandwidths supported by the NR IAB. + +The requirements in this clause assume a 30 dB coupling loss between interfering transmitter and NR IAB receiver and are based on co-location with base stations or IAB 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 IAB antenna input using the parameters in table 7.5.5.2-1 for all the IAB 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 *IAB type 1-H* blocking requirement for co-location with IAB in other bands is applied for all operating bands for which co-location protection is provided. + +Minimum conducted requirement is defined at the *TAB connector* for *IAB type 1-H*. + +**Table 7.5.5.2-1: Blocking performance requirement for NR IAB when co-located with BS/IAB in other frequency bands.** + +| Frequency range of interfering signal | Wanted signal mean power for WA IAB-DU (dBm) | Interfering signal mean power for WA IAB-DU (dBm) | Interfering signal mean power for MR IAB-DU (dBm) | Interfering signal mean power for LA IAB-DU (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 *IAB-DU channel bandwidth* as specified in TS 38.174 [2], tables 7.2.2-1, 7.2.2-2 and 7.2.2-3. + +NOTE 2: x = -7 dBm for NR IAB co-located with Pico GSM850 or Pico CDMA850 +x = -4 dBm for NR IAB co-located with Pico DCS1800 or Pico PCS1900 +x = -6 dBm for NR IAB 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). + +### 7.5.5.3 General requirements for IAB-MT + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel, with a wanted and an interfering signal coupled to *IAB type 1-H TAB connector* using the parameters in table 7.5.5.3-2. The reference measurement channel for the wanted signal is identified in subclause 7.2.1 and subclause 7.2.2 for each *IAB-MT channel bandwidth* and further specified in annex A.1. + +The out-of-band blocking requirement apply from 1 MHz to $F_{\text{DL,low}} - \Delta f_{\text{OOB}}$ and from $F_{\text{DL,high}} + \Delta f_{\text{OOB}}$ up to 12750 MHz. The $\Delta f_{\text{OOB}}$ for *IAB-MT* is defined in table 7.5.5.3-1. + +**Table 7.5.5.3-1: $\Delta f_{\text{OOB}}$ offset for NR operating bands** + +| IAB-MT type | Operating band characteristics | $\Delta f_{\text{OOB}}$ (MHz) | +|---------------------|----------------------------------------------------------------------------------|-------------------------------| +| IAB type 1-H | $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 | + +Minimum conducted requirement is defined and at the *TAB connector* for *IAB-MT type 1-H*. + +For a *multi-band connector*, the requirement in the out-of-band blocking frequency ranges apply for each *operating band*, with the exception that the in-band blocking frequency ranges of all supported *operating bands* according to clause 7.4.2.2 shall be excluded from the out-of-band blocking requirement. + +**Table 7.5.5.3-2: Out-of-band blocking performance requirement for NR** + +| Wanted Signal mean power (dBm) | Interfering Signal mean power (dBm) | Type of Interfering Signal | +|-------------------------------------------|-------------------------------------|----------------------------| +| $P_{\text{REFSENS}} + 6\text{ dB}$ (Note) | -15 | CW carrier | + +NOTE 1: For NR, $P_{\text{REFSENS}}$ depends also on the *IAB-MT channel bandwidth* as specified in subclause 7.2.1 and subclause 7.2.2. + +### 7.5.5.4 Co-location requirements for IAB-MT + +This additional blocking requirement may be applied for the protection of IAB-MT receivers when GSM, CDMA, UTRA, E-UTRA, NR BS or IAB-node operating in a different frequency band are co-located with an IAB-node. The requirement is applicable to all *IAB-MT channel bandwidths* supported by the IAB-node. + +The requirements in this clause assume a 30 dB coupling loss between interfering transmitter and IAB-node 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 *IAB type 1-H TAB connector* input using the parameters in table 7.5.5.4-1 for all the IAB classes. The reference measurement channel for the wanted signal is identified in subclause 7.2.1 and subclause 7.2.2 for each *IAB-MT channel bandwidth* and further specified in annex A.1. + +The blocking requirement for co-location with BS or IAB-node in other bands is applied for all *operating bands* for which co-location protection is provided. + +Minimum conducted requirement is defined at the *TAB connector* for *IAB type 1-H*. + +**Table 7.5.5.4-1: Blocking performance requirement for the IAB node** + +| Frequency range of interfering signal | Wanted signal mean power (dBm) | Interfering signal mean power for WA IAB node (dBm) | Interfering signal mean power for LA IAB node (dBm) | Type of interfering signal | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------|-----------------------------------------------------|-----------------------------------------------------|----------------------------| +| Frequency range of co-located downlink operating band | $P_{\text{REFSENS}} + 6\text{dB}$ (Note 1) | +16 | x (Note 2) | CW carrier | +| NOTE 1: $P_{\text{REFSENS}}$ depends on the IAB-MT channel bandwidth as specified in subclause 7.2.1 and subclause 7.2.2. | | | | | +| NOTE 2: x = -7 dBm for IAB-MT co-located with Pico GSM850 or Pico CDMA850
x = -4 dBm for IAB-MT co-located with Pico DCS1800 or Pico PCS1900
x = -6 dBm for IAB-MT 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 downlink operating band(s) or in $\Delta f_{\text{OOB}}$ immediately outside any of the supported downlink operating band(s) . | | | | | + +## 7.6 Receiver spurious emissions + +### 7.6.1 Definition and applicability + +The receiver spurious emissions power is the power of emissions generated or amplified in a receiver unit that appear at the *TAB connector* (for *IAB type 1-H*). The requirements apply to all IAB-DU and IAB-MT with separate RX and TX *TAB connectors*. + +For *TAB connectors* supporting both RX and TX in TDD, the requirements apply during the *transmitter OFF period*. + +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 *IAB type 1-H* manufacturer shall declare *TAB connector RX min cell groups*. The declaration is done separately for IAB-DU and IAB-MT. Every *TAB connector* of *IAB 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_{\text{RXU,counted}}$ ) for IAB type 1-H is calculated as follows: + +$$N_{\text{RXU,counted}} = \min(N_{\text{RXU,active}}, \delta \times N_{\text{cells}})$$ + +$N_{\text{RXU,countedpercell}}$ is used for scaling of *basic limits* and is derived as $N_{\text{RXU,countedpercell}} = N_{\text{RXU,counted}} / N_{\text{cells}}$ , where $N_{\text{cells}}$ is defined in clause 6.1. + +NOTE: $N_{\text{RXU,active}}$ is the number of actually active receiver units and is independent to the declaration of $N_{\text{cells}}$ . + +### 7.6.2 Minimum requirement + +The minimum requirement for *IAB type 1-H*: + +For *IAB-DU* are in TS 38.174 [2], clause 7.6.2. + +For *IAB-MT* are in TS 38.174 [2], clause 7.6.3. + +## 7.6.3 Test purpose + +The test purpose is to verify the ability of the IAB 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. + +*IAB RF Bandwidth* positions to be tested for multi-carrier: + +- $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. + +### 7.6.4.2 Procedure + +The minimum requirement is applied to all connectors under test, + +For *IAB 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.2.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.4 for *IAB type 1-H*. +- 2) For TDD connectors capable of transmit and receive ensure the transmitter is OFF. For *IAB type 1-H* supporting simultaneous reception of IAB-DU and IAB-MT (D.IAB-2), both IAB-DU and IAB-MT shall be configured to simultaneously receive only during the test. +- 3) For IAB-DU, set the measurement equipment parameters as specified in table 7.6.5.1-1. +For IAB-MT, set the measurement equipment parameters as specified in table 7.6.5.3-1. +- 4) For IAB-DU, measure the spurious emissions over each frequency range described in table 7.6.5.1-1. +For IAB-MT, measure the spurious emissions over each frequency range described in table 7.6.5.3-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 for IAB-DU + +The receiver spurious emissions limits are provided in table 7.6.5.1-1. + +**Table 7.6.5.1-1: General 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 | + +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: 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.6.1. For *multi-band connectors*, the exclusion applies for all supported *operating bands*. +NOTE 5: Void + +### 7.6.5.2 Test requirement for IAB-DU + +The RX spurious emissions requirements for *IAB 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 IAB 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 IAB-DU. + +NOTE: Conformance to the IAB-DU 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 IAB-DU 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 IAB-DU limit as defined above for the respective frequency span, scaled by $-10\log_{10}(n)$ , where *n* is the number of *TAB connectors* in the *TAB connector RX min cell group*. + +### 7.6.5.3 Basic limits for IAB-MT + +The IAB-MT receiver spurious emissions *basic limits* are provided in table 7.6.5.3-1. + +**Table 7.6.5.3-1: General IAB-MT 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 DL operating band in GHz | -47 dBm | 1 MHz | Note 1, Note 2, Note 3 | + +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: 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: The frequency range from $\Delta f_{\text{OBUE}}$ below the lowest frequency of the IAB-MT transmitter *operating band* to $\Delta f_{\text{OBUE}}$ above the highest frequency of the IAB-MT transmitter *operating band* may be excluded from the requirement. $\Delta f_{\text{OBUE}}$ is defined in clause [6.6.1]. For *multi-band connectors*, the exclusion applies for all supported *operating bands*. + +## 7.6.5.4 Test requirement for IAB-MT + +The RX spurious emissions requirements for *IAB type 1-H* are that for each applicable *basic limit* specified in table 7.6.5.3-1 for each *TAB connector RX min cell group*, the power sum of emissions at respective *TAB connectors* shall not exceed the IAB-MT limits specified as the *basic limits* + X, where $X = 10\log_{10}(N_{\text{RXU, counted per cell}})$ , 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 IAB-MT. + +NOTE: Conformance to the IAB-MT 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 IAB-MT 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 IAB-MT 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 *TAB connector* for *IAB 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 requirement for *IAB type 1-H*: + +For *IAB-DU* are in TS 38.174 [2], clause 7.7.2. + +For *IAB-MT* are in TS 38.174 [2], clause 7.7.3. + +### 7.7.3 Test purpose + +The test purpose is to verify the ability of the IAB node 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 + +*IAB 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 *IAB type 1-H* the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested; see clause 7.1. If IAB simultaneous reception is declared to be supported (see D.IAB-2 in table 4.6-1), connector(s) for IAB-MT and IAB-DU may be tested one at a time or may be tested in parallel as shown in annex D.2.6. + +- 1) Connect the connector under test to measurement equipment as shown in annex D.2.6 for *IAB type 1-H*. All connectors not under test shall be terminated. +- 2) Set the signal generator for the wanted signal to transmit as specified in table 7.7.5.1-1 and 7.7.5.1-3 for IAB-DU and table 7.7.5.2-1 and 7.7.5.2-3 for IAB-MT. +- 3) Set the signal generator for the interfering signal to transmit at the frequency offset and as specified in table 7.7.5.1-2 and 7.7.5.1-4 for IAB-DU and table 7.7.5.2-2 and 7.7.5.2-4 for IAB-MT. +- 4) Measure the throughput according to annex A.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.7.5 Test requirements + +#### 7.7.5.1 IAB-DU + +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 *IAB type 1-H TAB connector*, with the conditions specified in tables 7.7.5.1-1 and 7.7.5.1-2 for intermodulation performance and in tables 7.7.5.1-3, and 7.7.5.1-4 for narrowband intermodulation performance. The reference measurement channel for the wanted signal is identified in tables 7.2.5.1-1 to 7.2.5.1-3 for each channel bandwidth and further specified in annex A.1. 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 *IAB-DU 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 *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 an IAB-DU 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.1-2 or 7.7.5.1-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 *IAB-DU 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.1-2 and 7.7.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.7.5.1-1: General intermodulation requirement** + +| IAB-DU type | Wanted Signal mean power (dBm) | Mean power of interfering signals (dBm) | Type of interfering signals | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|-----------------------------------------|-----------------------------| +| Wide Area | $P_{\text{REFSENS}} + 6\text{ dB}$ | -52 | See table 7.7.5.1-2 | +| Medium Range | $P_{\text{REFSENS}} + 6\text{ dB}$ | -47 | | +| Local Area | $P_{\text{REFSENS}} + 6\text{ dB}$ | -44 | | +| NOTE: $P_{\text{REFSENS}}$ depends on the RAT and the IAB class. For NR, $P_{\text{REFSENS}}$ depends also on the IAB-DU channel bandwidth as specified in TS 38.174 [2], clause 7.2.1.2. | | | | + +**Table 7.7.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 | 5 MHz DFT-s-OFDM NR signal, (Note 1) | +| 15 | ±7.43 | CW | +| | ±17.5 | 5 MHz DFT-s-OFDM NR signal, (Note 1) | +| 20 | ±7.395 | CW | +| | ±17.5 | 5 MHz 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 | 20 MHz DFT-s-OFDM NR signal, (Note 2) | +| 35 | ±7.44 | CW | +| | ±25 | 20 MHz DFT-s-OFDM NR signal, (Note 2) | +| 40 | ±7.45 | CW | +| | ±25 | 20 MHz DFT-s-OFDM NR signal, (Note 2) | +| 45 | ±7.37 | CW | +| | ±25 | 20 MHz DFT-s-OFDM NR signal, (Note 2) | +| 50 | ±7.35 | CW | +| | ±25 | 20 MHz DFT-s-OFDM NR signal, (Note 2) | +| 60 | ±7.49 | CW | +| | ±25 | 20 MHz 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 | 20 MHz 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 | 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 *IAB-DU RF Bandwidth edge*. + +**Table 7.7.5.1-3: Narrowband intermodulation performance requirement in FR1** + +| IAB-DU type | Wanted signal mean power (dBm) (Note 1) | Mean power of interfering signals (dBm) | Type of interfering signal | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|------------------------------------------------|-----------------------------------| +| Wide Area | $P_{\text{REFSENS}} + 6$ dB | -52 | See table 7.7.5.1-4 | +| Medium Range | $P_{\text{REFSENS}} + 6$ dB | -47 | | +| Local Area | $P_{\text{REFSENS}} + 6$ dB | -44 | | +| NOTE: $P_{\text{REFSENS}}$ depends on the RAT. For NR, $P_{\text{REFSENS}}$ depends also on the IAB-DU channel bandwidth as specified in TS 38.174 [2], clause 7.2.1.2. | | | | + +**Table 7.7.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 signals | +|------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------| +| 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 | +| | ±2710 | 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 *IAB-DU channel bandwidth* of the interfering signal is located adjacently to the lower/upper *IAB-DU 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.2 IAB-MT + +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 *IAB type 1-H TAB connector*, with the conditions specified in tables 7.7.5.2-1 and 7.7.5.2-2 for intermodulation performance and in tables 7.7.5.2-3, and 7.7.5.2-4 for narrowband intermodulation performance. The reference measurement channel for the wanted signal is identified in tables 7.2.5.2-1 to 7.2.5.2-2 for each channel bandwidth and further specified in annex A.1. 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 *IAB-MT 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 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 an IAB-MT 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-2 or 7.7.5.2-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 *IAB-MT 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-2 and 7.7.5.2-4. The interfering signal offset is defined relative to the *IAB-MT RF Bandwidth edges* inside the *Inter RF Bandwidth gap*. + +**Table 7.7.5.2-1: General intermodulation requirement** + +| IAB-MT type | Wanted Signal mean power (dBm) | Mean power of interfering signals (dBm) | Type of interfering signals | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|-----------------------------------------|-----------------------------| +| Wide Area | $P_{\text{REFSENS}} + 6\text{ dB}$ | -52 | See table 7.7.5.2-2 | +| Local Area | $P_{\text{REFSENS}} + 6\text{ dB}$ | -44 | | +| NOTE: $P_{\text{REFSENS}}$ depends on the RAT and the IAB class. For NR, $P_{\text{REFSENS}}$ depends also on the IAB-MT channel bandwidth as specified in TS 38.174 [2], clause 7.2.2.2. | | | | + +**Table 7.7.5.2-2: Interfering signals for intermodulation requirement** + +| 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 (MHz) | Type of interfering signal (Note 3) | +|------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------|--------------------------------------------| +| 10 | $\pm 7.465$ | CW | +| | $\pm 17.5$ | 5 MHz CP-OFDM NR signal, (Note 1) | +| 15 | $\pm 7.43$ | CW | +| | $\pm 17.5$ | 5 MHz CP-OFDM NR signal, (Note 1) | +| 20 | $\pm 7.395$ | CW | +| | $\pm 17.5$ | 5 MHz CP-OFDM NR signal, (Note 1) | +| 25 | $\pm 7.465$ | CW | +| | $\pm 25$ | 20 MHz CP-OFDM NR signal, (Note 2) | +| 30 | $\pm 7.43$ | CW | +| | $\pm 25$ | 20 MHz CP-OFDM NR signal, (Note 2) | +| 35 | $\pm 7.44$ | CW | +| | $\pm 25$ | 20 MHz CP-OFDM NR signal, (Note 2) | +| 40 | $\pm 7.45$ | CW | +| | $\pm 25$ | 20 MHz CP-OFDM NR signal, (Note 2) | +| 45 | $\pm 7.37$ | CW | +| | $\pm 25$ | 20 MHz CP-OFDM NR signal, (Note 2) | +| 50 | $\pm 7.35$ | CW | +| | $\pm 25$ | 20 MHz CP-OFDM NR signal, (Note 2) | +| 60 | $\pm 7.49$ | CW | +| | $\pm 25$ | 20 MHz CP-OFDM NR signal, (Note 2) | +| 70 | $\pm 7.42$ | CW | +| | $\pm 25$ | 20 MHz CP-OFDM NR signal, (Note 2) | +| 80 | $\pm 7.44$ | CW | +| | $\pm 25$ | 20 MHz CP-OFDM NR signal, (Note 2) | +| 90 | $\pm 7.46$ | CW | +| | $\pm 25$ | 20 MHz CP-OFDM NR signal, (Note 2) | +| 100 | $\pm 7.48$ | CW | +| | $\pm 25$ | 20 MHz 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.7.5.2-3: Narrowband intermodulation performance requirement in FR1** + +| IAB-MT type | Wanted signal mean power (dBm) (Note 1) | Mean power of interfering signals (dBm) | Type of interfering signal | +|--------------------|------------------------------------------------|------------------------------------------------|-----------------------------------| +| Wide Area | $P_{\text{REFSENS}} + 6$ dB | -52 | See table 7.7.5.2-4 | +| Local Area | $P_{\text{REFSENS}} + 6$ dB | -44 | | + +NOTE: $P_{\text{REFSENS}}$ depends on the RAT. For NR, $P_{\text{REFSENS}}$ depends also on the *IAB-MT channel bandwidth* as specified in TS 38.174 [2], clause 7.2.2.2. + +**Table 7.7.5.2-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 signals | +|------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------| +| 10 | ±370 | CW | +| | ±1960 | 5 MHz CP-OFDM NR signal, 1 RB (Note 1) | +| 15 (Note 2) | ±380 | CW | +| | ±1960 | 5 MHz CP-OFDM NR signal, 1 RB (Note 1) | +| 20 (Note 2) | ±390 | CW | +| | ±2320 | 5 MHz CP-OFDM NR signal, 1 RB (Note 1) | +| 25 (Note 2) | ±325 | CW | +| | ±2350 | 20 MHz CP-OFDM NR signal, 1 RB (Note 1) | +| 30 (Note 2) | ±335 | CW | +| | ±2350 | 20 MHz CP-OFDM NR signal, 1 RB (Note 1) | +| 35 (Note 2) | ±345 | CW | +| | ±2710 | 20 MHz CP-OFDM NR signal, 1 RB (Note 1) | +| 40 (Note 2) | ±355 | CW | +| | ±2710 | 20 MHz CP-OFDM NR signal, 1 RB (Note 1) | +| 45 (Note 2) | ±365 | CW | +| | ±2710 | 20 MHz CP-OFDM NR signal, 1 RB (Note 1) | +| 50 (Note 2) | ±375 | CW | +| | ±2710 | 20 MHz CP-OFDM NR signal, 1 RB (Note 1) | +| 60 (Note 2) | ±395 | CW | +| | ±2710 | 20 MHz CP-OFDM NR signal, 1 RB (Note 1) | +| 70 (Note 2) | ±415 | CW | +| | ±2710 | 20 MHz CP-OFDM NR signal, 1 RB (Note 1) | +| 80 (Note 2) | ±435 | CW | +| | ±2710 | 20 MHz CP-OFDM NR signal, 1 RB (Note 1) | +| 90 (Note 2) | ±365 | CW | +| | ±2530 | 20 MHz CP-OFDM NR signal, 1 RB (Note 1) | +| 100 (Note 2) | ±385 | CW | +| | ±2530 | 20 MHz 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* 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.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 *TAB connector* for *IAB-DU* 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 *IAB type 1-H* for *IAB-DU* are in TS 38.174 [2], clause 7.8.2. + +## 7.8.3 Test purpose + +The purpose of this test is to verify the IAB-DU 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 *IAB 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 in sub-clause 7.8.5. +- 2) Set the signal generator for the interfering signal to transmit at the frequency offset and as specified in sub-clause 7.8.5. +- 3) Measure the throughput according to annex A.1. + +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 + +### 7.8.5.1 IAB-DU + +For *IAB-DU*, 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-1 for Wide Area IAB-DU, in table 7.8.5.1-2 for Medium Range IAB-DU and in table 7.8.5.1-3 for Local Area IAB-DU. The characteristics of the interfering signal is further specified in annex E. + +**Table 7.8.5.1-1: Wide Area IAB-DU in-channel selectivity** + +| IAB-DU 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 | | | +| 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 | +| 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 *IAB-DU channel bandwidth* of the wanted signal according to the clause 5.4.2.2 in TS 38.174 [2]. The aggregated wanted and interferer signal shall be centred in the *IAB-DU channel bandwidth* of the wanted signal. + +**Table 7.8.5.1-2: Medium Range IAB-DU in-channel selectivity** + +| IAB-DU 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 | | | +| 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 | +| 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 *IAB-DU channel bandwidth* of the wanted signal according to the clause 5.4.2.2 in TS 38.174 [2]. The aggregated wanted and interferer signal shall be centred in the *IAB-DU channel bandwidth* of the wanted signal. + +**Table 7.8.5.1-3: Local area IAB-DU in-channel selectivity** + +| IAB-DU 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 | | | +| 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 | +| 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 *IAB-DU channel bandwidth* of the wanted signal according to the clause 5.4.2.2 in TS 38.174 [2]. The aggregated wanted and interferer signal shall be centred in the *IAB-DU channel bandwidth* of the wanted signal. + +## 8 Conducted performance requirements + +### 8.1 IAB-DU performance requirements + +#### 8.1.1 General + +##### 8.1.1.1 Scope and definitions + +Conducted performance requirements specify the ability of the *IAB type 1-H* to correctly demodulate signals in various conditions and configurations. Conducted performance requirements are specified at the *TAB connector(s)*. + +Conducted performance requirements for the IAB-DU are specified for the fixed reference channels and the propagation conditions defined in TS 38.174 [2] annex A and annex F, respectively. The requirements only apply to those FRCs that are supported by the IAB-DU. + +Unless stated otherwise, performance requirements apply for a single carrier only. 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: + +$$\text{SNR} = S / N$$ + +Where: + +$S$ is the total signal energy in a slot on a single *TAB connector*. + +N is the noise energy in a bandwidth corresponding to the transmission bandwidth over the duration of a slot. + +### 8.1.1.2 Applicability rule + +#### 8.1.1.2.1 General + +Unless otherwise stated, for a IAB-DU supporting more than 8 *TAB connectors* (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 IAB-DU supporting different numbers of *TAB connectors* (see D.37 in table 4.6-1), the 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.1.2.2 Applicability of PUSCH performance requirements + +##### 8.1.1.2.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.14 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.2.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.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 centred in this widest supported channel bandwidth. + +##### 8.1.1.2.2.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.1.2.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.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.1.2.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.2.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.109 in table 4.6-1). + +### 8.1.1.2.3 Applicability of PUCCH performance requirements + +#### 8.1.1.2.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.2.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.14 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.2.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.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 PRIAB-DU shall then be centred in this widest supported channel bandwidth. + +#### 8.1.1.2.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.2.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.106 in table 4.6-1). + +### 8.1.1.2.4 Applicability of PRACH performance requirements + +#### 8.1.1.2.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.2.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.2.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.14 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.2.2. + +#### 8.1.2.1.2 Minimum requirement + +The minimum requirement is in TS 38.174 [2] clause 8.1.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_{BW\ Channel\ CA}$ ; see clause 4.9.1. + +##### 8.1.2.1.4.2 Test procedure + +- 1) Connect the IAB-DU tester generating the wanted signal, multipath fading simulators and AWGN generators to all IAB-DU *TAB connectors* for diversity reception via a combining network as shown in annex D. 3. +- 2) Adjust the AWGN generator, according to the channel bandwidth, defined in table 8.1.2.1.4.2-1. + +**Table 8.1.2.1.4.2-1: AWGN power level at the IAB-DU input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|-------------------------|----------------------| +| 15 kHz | 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 | + +- 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 | +| Cyclic prefix | Normal | +| 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
RV sequence | +| DM-RS | 1
single-symbol DM-RS
pos1
2
-3 dB
{0}, {0, 1}
$N_{ID}^0=0, n_{SCID}=0$ | +| Time domain resource assignment | PUSCH mapping type
Start symbol
Allocation length | +| Frequency domain resource assignment | Full applicable test bandwidth
Disabled | +| TPMI index for 2Tx two layer spatial multiplexing transmission | 0 | +| Code block group based PUSCH transmission | Disabled | + +NOTE 1: The same requirements are applicable with different UL-DL patterns. + +- 4) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex F. +- 5) Adjust the equipment so that required SNR specified in table 8.1.2.1.5-1 to 8.1.2.1.5-14 is achieved at the IAB-DU input. +- 6) For each of the reference channels in table 8.1.2.1.5-1 to 8.1.2.1.5-14 applicable for the base station, measure the throughput. + +#### 8.1.2.1.5 Test requirement + +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 to 8.1.2.1.5-14. + +**Table 8.1.2.1.5-1: Void** + +**Table 8.1.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 | Propagation conditions and correlation matrix (annex F) | 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 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-2 | pos1 | -5.4 | +| | | TDLC300-100 Low | D-FR1-A.2.3-2 | pos1 | 6.9 | +| | | TDLA30-10 Low | D-FR1-A.2.4-2 | pos1 | 9.2 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-2 | pos1 | -8.1 | +| | | TDLC300-100 Low | D-FR1-A.2.3-2 | pos1 | 3.7 | +| | | TDLA30-10 Low | D-FR1-A.2.4-2 | pos1 | 6.1 | +| 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 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-9 | pos1 | -1.2 | +| | | TDLC300-100 Low | D-FR1-A.2.3-9 | pos1 | 12.0 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-9 | pos1 | -4.7 | +| | | TDLC300-100 Low | D-FR1-A.2.3-9 | pos1 | 7.6 | + +**Table 8.1.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 | Propagation conditions and correlation matrix (annex F) | 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 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-3 | pos1 | -4.9 | +| | | TDLC300-100 Low | D-FR1-A.2.3-3 | pos1 | 6.8 | +| | | TDLA30-10 Low | D-FR1-A.2.4-3 | pos1 | 9.2 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-3 | pos1 | -7.9 | +| | | TDLC300-100 Low | D-FR1-A.2.3-3 | pos1 | 3.6 | +| | | TDLA30-10 Low | D-FR1-A.2.4-3 | pos1 | 6.1 | +| 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 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-10 | pos1 | -1.0 | +| | | TDLC300-100 Low | D-FR1-A.2.3-10 | pos1 | 11.9 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-10 | pos1 | -4.5 | +| | | TDLC300-100 Low | D-FR1-A.2.3-10 | pos1 | 7.7 | + +**Table 8.1.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 | Propagation conditions and correlation matrix (annex F) | 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 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-4 | pos1 | -5.0 | +| | | TDLC300-100 Low | D-FR1-A.2.3-4 | pos1 | 7.0 | +| | | TDLA30-10 Low | D-FR1-A.2.4-4 | pos1 | 9.2 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-4 | pos1 | -8.0 | +| | | TDLC300-100 Low | D-FR1-A.2.3-4 | pos1 | 3.9 | +| | | TDLA30-10 Low | D-FR1-A.2.4-4 | pos1 | 6.1 | +| 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 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-11 | pos1 | -1.4 | +| | | TDLC300-100 Low | D-FR1-A.2.3-11 | pos1 | 12.0 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-11 | pos1 | -4.4 | +| | | TDLC300-100 Low | D-FR1-A.2.3-11 | pos1 | 7.8 | + +**Table 8.1.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 | Propagation conditions and correlation matrix (annex F) | 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 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-5 | pos1 | -5.4 | +| | | TDLC300-100 Low | D-FR1-A.2.3-5 | pos1 | 7.0 | +| | | TDLA30-10 Low | D-FR1-A.2.4-5 | pos1 | 9.2 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-5 | pos1 | -8.2 | +| | | TDLC300-100 Low | D-FR1-A.2.3-5 | pos1 | 3.8 | +| | | TDLA30-10 Low | D-FR1-A.2.4-5 | pos1 | 6.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 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-12 | pos1 | -1.4 | +| | | TDLC300-100 Low | D-FR1-A.2.3-12 | pos1 | 12.1 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-12 | pos1 | -4.5 | +| | | TDLC300-100 Low | D-FR1-A.2.3-12 | pos1 | 7.7 | + +**Table 8.1.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 | Propagation conditions and correlation matrix (annex F) | 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 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-6 | pos1 | -5.2 | +| | | TDLC300-100 Low | D-FR1-A.2.3-6 | pos1 | 6.9 | +| | | TDLA30-10 Low | D-FR1-A.2.4-6 | pos1 | 9.1 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-6 | pos1 | -8.1 | +| | | TDLC300-100 Low | D-FR1-A.2.3-6 | pos1 | 3.7 | +| | | TDLA30-10 Low | D-FR1-A.2.4-6 | pos1 | 6.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 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-13 | pos1 | -1.5 | +| | | TDLC300-100 Low | D-FR1-A.2.3-13 | pos1 | 12.1 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-13 | pos1 | -4.4 | +| | | TDLC300-100 Low | D-FR1-A.2.3-13 | pos1 | 7.7 | + +**Table 8.1.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 | Propagation conditions and correlation matrix (annex F) | 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 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-7 | pos1 | -5.2 | +| | | TDLC300-100 Low | D-FR1-A.2.3-7 | pos1 | 7.1 | +| | | TDLA30-10 Low | D-FR1-A.2.4-7 | pos1 | 9.6 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-7 | pos1 | -8.1 | +| | | TDLC300-100 Low | D-FR1-A.2.3-7 | pos1 | 3.8 | +| | | TDLA30-10 Low | D-FR1-A.2.4-7 | pos1 | 6.4 | +| 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 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-14 | pos1 | -1.4 | +| | | TDLC300-100 Low | D-FR1-A.2.3-14 | pos1 | 12.4 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-14 | pos1 | -4.4 | +| | | TDLC300-100 Low | D-FR1-A.2.3-14 | pos1 | 7.9 | + +**Table 8.1.2.1.5-8: Void** + +**Table 8.1.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 | Propagation conditions and correlation matrix (annex F) | 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 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-2 | pos1 | -5.1 | +| | | TDLC300-100 Low | D-FR1-A.2.3-2 | pos1 | 7.1 | +| | | TDLA30-10 Low | D-FR1-A.2.4-2 | pos1 | 9.5 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-2 | pos1 | -8.4 | +| | | TDLC300-100 Low | D-FR1-A.2.3-2 | pos1 | 3.8 | +| | | TDLA30-10 Low | D-FR1-A.2.4-2 | pos1 | 6.4 | +| 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 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-9 | pos1 | -1.5 | +| | | TDLC300-100 Low | D-FR1-A.2.3-9 | pos1 | 12.1 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-9 | pos1 | -4.4 | +| | | TDLC300-100 Low | D-FR1-A.2.3-9 | pos1 | 7.8 | + +**Table 8.1.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 | Propagation conditions and correlation matrix (annex F) | 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 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-3 | pos1 | -5.1 | +| | | TDLC300-100 Low | D-FR1-A.2.3-3 | pos1 | 6.9 | +| | | TDLA30-10 Low | D-FR1-A.2.4-3 | pos1 | 9.4 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-3 | pos1 | -7.9 | +| | | TDLC300-100 Low | D-FR1-A.2.3-3 | pos1 | 3.7 | +| | | TDLA30-10 Low | D-FR1-A.2.4-3 | pos1 | 6.3 | +| 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 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-10 | pos1 | -1.2 | +| | | TDLC300-100 Low | D-FR1-A.2.3-10 | pos1 | 12.0 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-10 | pos1 | -4.5 | +| | | TDLC300-100 Low | D-FR1-A.2.3-10 | pos1 | 7.7 | + +**Table 8.1.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 | Propagation conditions and correlation matrix (annex F) | 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 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-4 | pos1 | -5.1 | +| | | TDLC300-100 Low | D-FR1-A.2.3-4 | pos1 | 7.0 | +| | | TDLA30-10 Low | D-FR1-A.2.4-4 | pos1 | 9.2 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-4 | pos1 | -8.2 | +| | | TDLC300-100 Low | D-FR1-A.2.3-4 | pos1 | 3.8 | +| | | TDLA30-10 Low | D-FR1-A.2.4-4 | pos1 | 6.2 | +| 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 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-11 | pos1 | -1.7 | +| | | TDLC300-100 Low | D-FR1-A.2.3-11 | pos1 | 12.1 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-11 | pos1 | -4.8 | +| | | TDLC300-100 Low | D-FR1-A.2.3-11 | pos1 | 7.8 | + +**Table 8.1.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 | Propagation conditions and correlation matrix (annex F) | 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 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-5 | pos1 | -5.4 | +| | | TDLC300-100 Low | D-FR1-A.2.3-5 | pos1 | 6.9 | +| | | TDLA30-10 Low | D-FR1-A.2.4-5 | pos1 | 9.2 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-5 | pos1 | -8.4 | +| | | TDLC300-100 Low | D-FR1-A.2.3-5 | pos1 | 3.7 | +| | | TDLA30-10 Low | D-FR1-A.2.4-5 | pos1 | 6.2 | +| 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 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-12 | pos1 | -1.5 | +| | | TDLC300-100 Low | D-FR1-A.2.3-12 | pos1 | 12.0 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-12 | pos1 | -4.6 | +| | | TDLC300-100 Low | D-FR1-A.2.2-12 | pos1 | 7.8 | + +**Table 8.1.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 | Propagation conditions and correlation matrix (annex F) | 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 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-6 | pos1 | -5.2 | +| | | TDLC300-100 Low | D-FR1-A.2.3-6 | pos1 | 6.8 | +| | | TDLA30-10 Low | D-FR1-A.2.4-6 | pos1 | 9.3 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-6 | pos1 | -8.2 | +| | | TDLC300-100 Low | D-FR1-A.2.3-6 | pos1 | 3.6 | +| | | TDLA30-10 Low | D-FR1-A.2.4-6 | pos1 | 6.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 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-13 | pos1 | -1.3 | +| | | TDLC300-100 Low | D-FR1-A.2.3-13 | pos1 | 12.0 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-13 | pos1 | -4.4 | +| | | TDLC300-100 Low | D-FR1-A.2.3-13 | pos1 | 7.7 | + +**Table 8.1.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 | Propagation conditions and correlation matrix (annex F) | 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 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-7 | pos1 | -5.2 | +| | | TDLC300-100 Low | D-FR1-A.2.3-7 | pos1 | 6.9 | +| | | TDLA30-10 Low | D-FR1-A.2.4-7 | pos1 | 9.8 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-7 | pos1 | -8.1 | +| | | TDLC300-100 Low | D-FR1-A.2.3-7 | pos1 | 3.7 | +| | | TDLA30-10 Low | D-FR1-A.2.4-7 | pos1 | 6.5 | +| 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 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-14 | pos1 | -1.4 | +| | | TDLC300-100 Low | D-FR1-A.2.3-14 | pos1 | 12.4 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-14 | pos1 | -4.5 | +| | | TDLC300-100 Low | D-FR1-A.2.3-14 | pos1 | 7.9 | + +## 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.2.2. + +### 8.1.2.2.2 Minimum requirement + +The minimum requirement is in TS 38.174 [2], clause 8.1.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 annex B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1. + +#### 8.1.2.2.4.2 Test procedure + +- 1) Connect the IAB-DU tester generating the wanted signal, multipath fading simulators and AWGN generators to all IAB-DU *TAB connectors* for diversity reception via a combining network as shown in annex D. 3. +- 2) Adjust the AWGN generator, according to the SCS and channel bandwidth, defined in table 8.1.2.2.4.2-1. + +**Table 8.1.2.2.4.2-1: AWGN power level at the IAB-DU 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 | + +- 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.1.2.2.4.2-2. + +**Table 8.1.2.2.4.2-2: Test parameters for testing PUSCH** + +| Parameter | Value | +|---------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Transform precoding | Enabled | +| Cyclic prefix | Normal | +| 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
RV sequence | +| DM-RS | DM-RS configuration type
DM-RS duration
Additional DM-RS position
Number of DM-RS CDM group(s) without data
Ratio of PUSCH EPRE to DM-RS EPRE
DM-RS port(s)
DM-RS sequence generation | +| Time domain resource assignment | PUSCH mapping type
Start symbol
Allocation length | +| Frequency domain resource assignment | RB assignment
Frequency hopping | +| Code block group based PUSCH transmission | Disabled | +| NOTE 1: The same requirements are applicable to different UL-DL patterns. | | + +- 4) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex F. + +- 5) Adjust the equipment so that required SNR specified in table 8.1.2.2.5-1 to 8.1.2.2.5-4 is achieved at the IAB-DU input. +- 6) For each of the reference channels in table 8.1.2.2.5-1 to 8.1.2.2.5-4 applicable for the base station, measure the throughput. + +#### 8.1.2.2.5 Test requirement + +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 to 8.1.2.2.5-4. + +**Table 8.1.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 | Propagation conditions and correlation matrix (annex F) | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------------------------------------------------|----------------|---------------------------|----------| +| 1 | 2 | TDLB100-400 Low | D-FR1-A.2.1-15 | pos1 | -1.8 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-15 | pos1 | -5.1 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-15 | pos1 | -7.9 | + +**Table 8.1.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 | Propagation conditions and correlation matrix (annex F) | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------------------------------------------------|----------------|---------------------------|----------| +| 1 | 2 | TDLB100-400 Low | D-FR1-A.2.1-16 | pos1 | -1.9 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-16 | pos1 | -5.1 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-16 | pos1 | -7.8 | + +**Table 8.1.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 | Propagation conditions and correlation matrix (annex F) | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------------------------------------------------|----------------|---------------------------|----------| +| 1 | 2 | TDLB100-400 Low | D-FR1-A.2.1-15 | pos1 | -1.7 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-15 | pos1 | -5.2 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-15 | pos1 | -8.0 | + +**Table 8.1.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 | Propagation conditions and correlation matrix (annex F) | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------------------------------------------------|----------------|---------------------------|----------| +| 1 | 2 | TDLB100-400 Low | D-FR1-A.2.1-16 | pos1 | -2.1 | +| | 4 | TDLB100-400 Low | D-FR1-A.2.1-16 | pos1 | -5.4 | +| | 8 | TDLB100-400 Low | D-FR1-A.2.1-16 | pos1 | -8.2 | + +### 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 HARQ/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 IAB-DU is based on the test applicability rule defined in clause 8.1.1.2.2. + +#### 8.1.2.3.2 Minimum requirement + +The minimum requirements are in TS 38.174 [2] clause 8.1.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. + +##### 8.1.2.3.4.2 Test procedure + +- 1) Connect the IAB-DU tester generating the wanted signal, multipath fading simulators and AWGN generators to all IAB-DU *TAB connectors* for diversity reception via a combining network as shown in annex D. 3. +- 2) Adjust the AWGN generator, according to combination of SCS and channel bandwidth defined in table 8.1.2.3.4.2-1. + +**Table 8.2.3.4.2-1: AWGN power level at the IAB-DU input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|-------------------------|----------------------| +| 30 | 10 | -80.6 dBm / 8.64 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 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.1.2.3.4.2-2: Test parameters for testing UCI multiplexed on PUSCH** + +| Parameter | Value | +|-------------------------------------------|---------------------------------------------------------------------------| +| Transform precoding | Disabled | +| Cyclic prefix | Normal | +| Default TDD UL-DL pattern (Note 1) | 30 kHz SCS:
7D1S2U, S=6D:4G:4U | +| HARQ | Maximum number of HARQ transmissions | +| | RV sequence | +| DM-RS | DM-RS configuration type | +| | DM-RS duration | +| | Additional DM-RS position | +| | Number of DM-RS CDM group(s) without data | +| | Ratio of PUSCH EPRE to DM-RS EPRE | +| | DM-RS port(s) | +| | DM-RS sequence generation | +| Time domain resource assignment | PUSCH mapping type | +| | Start symbol | +| | Allocation length | +| Frequency domain resource assignment | RB assignment | +| | Frequency hopping | +| Code block group based PUSCH transmission | Disabled | +| UCI | Number of CSI part 1 and CSI part 2 information bit payload | +| | scaling | +| | betaOffsetACK-Index1 | +| | betaOffsetCSI-Part1-Index1 and betaOffsetCSI-Part1-Index2 | +| | betaOffsetCSI-Part2-Index1 and betaOffsetCSI-Part2-Index2 | +| | UCI partition for frequency hopping | +| | NOTE 1: The same requirements are applicable to different UL-DL patterns. | + +- 4) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex F. +- 5) Adjust the equipment so that required SNR specified in table 8.1.2.3.5-1 to 8.1.2.3.5-4 is achieved at the IAB-DU input during the UCI multiplexed on PUSCH transmissions. +- 6) The tester 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.1.2.3.5 Test requirement + +The fractional of incorrectly decoded UCI with CSI part 1 according to clause 8.1.2.3.4.2 shall be less than 0.1 % for SNR listed in table 8.1.2.3.5-1 and table 8.1.2.3.5-2. The fractional of incorrectly decoded UCI with CSI part 2 according to clause 8.1.2.3.4.2 shall be less than 1 % for SNR listed in table 8.1.2.3.5-3 and table 8.1.2.3.5-4. + +**Table 8.1.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 | Propagation conditions and correlation matrix (Annex F) | 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-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 | Propagation conditions and correlation matrix (Annex F) | 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-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 | Propagation conditions and correlation matrix (Annex F) | 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-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 | Propagation conditions and correlation matrix (Annex F) | 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.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 [23] clause 6.3.3.1 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. + +Which specific test(s) are applicable to IAB-DU is based on the test applicability rules defined in clause 8.1.1.2.3. + +#### 8.1.3.1.2 Minimum requirement + +The minimum requirements are in TS 38.174 [2] clause 8.1.3.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. + +##### 8.1.3.1.4.2 Test procedure + +- 1) Connect the IAB-DU tester generating the wanted signal, multipath fading simulators and AWGN generators to all IAB-DU *TAB connectors* for diversity reception via a combining network as shown in annex D. 3. +- 2) Adjust the AWGN generator, according to the channel bandwidth and sub-carrier spacing defined in table 8.1.3.1.4.2-1. + +**Table 8.1.3.1.4.2-1: AWGN power level at the IAB-DU input** + +| Subcarrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|--------------------------|-------------------------|-----------------------| +| 15 | 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 | + +- 3) The characteristics of the wanted signal shall be configured according to TS 38.211 [9] and the specific test parameters are configured as mentioned in table 8.1.3.1.4.2-2: + +**Table 8.1.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.1.3.1.5-1 or table 8.1.3.1.5-2 is achieved at the IAB-DU input during the ACK transmissions. +- 6) The tester 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', arranged horizontally. To the right of the third box are three dots, indicating a repeating pattern.](f3c73e8e478b8b2d9f6a96a970040556_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', arranged horizontally. To the right of the third box are three dots, indicating a repeating 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 + +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 and in table 8.1.3.1.5-2. + +**Table 8.1.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 F) | 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 | + +| Number of TX antennas | Number of RX antennas | Propagation conditions and correlation matrix (annex F) | Number of OFDM symbols | Channel bandwidth / SNR (dB) | | +|-----------------------|-----------------------|---------------------------------------------------------|------------------------|------------------------------|--------| +| | | | | 10 MHz | 20 MHz | +| 1 | 2 | TDLC-300-100 Low | 1 | 9.4 | 9.9 | +| | | | 2 | 4.3 | 3.9 | +| 1 | 4 | TDLC-300-100 Low | 1 | 3.5 | 3.8 | +| | | | 2 | 0.1 | -0.2 | +| 1 | 8 | TDLC-300-100 Low | 1 | -0.5 | -0.5 | +| | | | 2 | -3.3 | -3.4 | + +**Table 8.1.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 F) | 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.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 [23] clause 6.3.3.1 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. + +Which specific test(s) are applicable to IAB-DU is based on the test applicability rules defined in clause 8.1.1.2.3. + +#### 8.1.3.2.1.2 Minimum requirement + +The minimum requirement is in TS 38.174 [2] clause 8.1.3.3.1 + +#### 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. + +##### 8.1.3.2.1.4.2 Test procedure + +- 1) Connect the IAB-DU tester generating the wanted signal, multipath fading simulators and AWGN generators to all IAB-DU *TAB connectors* for diversity reception via a combining network as shown in annex D. 3. +- 2) Adjust the AWGN generator, according to the combinations of SCS and channel bandwidth defined in table 8.1.3.2.1.4.2-1. + +**Table 8.1.3.2.1.4.2-1: AWGN power level at the IAB-DU input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|-------------------------|-----------------------| +| 15 kHz | 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 | + +- 3) The characteristics of the wanted signal shall be configured according to TS 38.211 [9], and the specific test parameters are configured as below: + +**Table 8.1.3.2.1.4.2-2: Test parameters** + +| Parameter | Values | +|---------------------------------------------------------|---------------------------------------| +| Cyclic prefix | Normal | +| 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 F. +- 5) Adjusting the equipment so that the SNR specified in table 8.1.3.2.1.5-1 and table 8.1.3.2.1.5-2 is achieved at the IAB-DU 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.1.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.1.3.2.1.5-1 and table 8.1.3.2.1.5-2. + +**Table 8.1.3.2.1.5-1: Required SNR for PUCCH format 1 with 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Propagation conditions and correlation matrix (annex F) | Channel bandwidth / SNR (dB) | | +|-----------------------|-----------------------|---------------------------------------------------------|------------------------------|--------| +| | | | 10 MHz | 20 MHz | +| 1 | 2 | TDLC-300-100 Low | -3.0 | -3.0 | +| | 4 | TDLC-300-100 Low | -7.0 | -7.8 | +| | 8 | TDLC-300-100 Low | -10.8 | -10.8 | + +**Table 8.1.3.2.1.5-2: Required SNR for PUCCH format 1 with 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Propagation conditions and correlation matrix (annex F) | Channel bandwidth / SNR (dB) | | | | +|-----------------------|-----------------------|---------------------------------------------------------|------------------------------|--------|--------|---------| +| | | | 10 MHz | 20 MHz | 40 MHz | 100 MHz | +| 1 | 2 | TDLC-300-100 Low | -2.2 | -2.7 | -3.3 | -2.9 | +| | 4 | TDLC-300-100 Low | -7.5 | -7.7 | -6.9 | -7.4 | +| | 8 | TDLC-300-100 Low | -10.9 | -10.6 | -10.1 | -10.7 | + +#### 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 [23] clause 6.3.3.1 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. + +Which specific test(s) are applicable to IAB-DU is based on the test applicability rules defined in clause 8.1.1.2.3. + +#### 8.1.3.2.2.2 Minimum requirement + +The minimum requirement is in TS 38.174 [2] clause 8.1.3.3.2 + +#### 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 (SC): M; see clause 4.9.1. + +##### 8.1.3.2.2.4.2 Test procedure + +- 1) Connect the IAB-DU tester generating the wanted signal, multipath fading simulators and AWGN generators to all IAB-DU *TAB connectors* for diversity reception via a combining network as shown in annex D. 3. +- 2) Adjust the AWGN generator, according to the combinations of SCS and channel bandwidth defined in table 8.1.3.2.2.4.2-1. + +**Table 8.1.3.2.2.4.2-1: AWGN power level at the IAB-DU input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|-------------------------|-----------------------| +| 15 kHz | 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 | + +- 3) The characteristics of the wanted signal shall be configured according to TS 38.211 [9], and the specific test parameters are configured as below: + +**Table 8.3.2.2.4.2-2: Test parameters** + +| Parameter | Values | +|---------------------------------------------------------|----------------------------------------| +| Cyclic prefix | Normal | +| 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 F. +- 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 IAB-DU input during the transmissions. +- 6) 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 + +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 Required SNR for PUCCH format 1 with 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Propagation conditions and correlation matrix (annex F) | Channel bandwidth / SNR (dB) | | +|-----------------------|-----------------------|---------------------------------------------------------|------------------------------|--------| +| | | | 10 MHz | 20 MHz | +| 1 | 2 | TDLC300-100 Low | -3.8 | -4.4 | +| | 4 | TDLC300-100 Low | -7.6 | -7.9 | +| | 8 | TDLC300-100 Low | -10.9 | -10.9 | + +**Table 8.1.3.2.2.5-2 Required SNR for PUCCH format 1 with 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Propagation conditions and correlation matrix (annex F) | 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 | +| | 4 | TDLC300-100 Low | -7.4 | -7.5 | -7.8 | -7.7 | +| | 8 | TDLC300-100 Low | -10.8 | -10.8 | -10.8 | -10.8 | + +### 8.1.3.3 Performance requirements for PUCCH format 2 + +#### 8.1.3.3.1 ACK missed detection + +##### 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. 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.2.3. + +The transient period as specified in TS 38.101-1 [23] clause 6.3.3.1 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.1.3.3.1.2 Minimum requirement + +The minimum requirements are in TS 38.174 [2] clause 8.1.3.4.1 + +##### 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 annex B.2. + +RF channels to be tested for single carrier; M; see clause 4.9.1. + +###### 8.1.3.3.1.4.2 Test procedure + +- 1) Connect the IAB-DU tester generating the wanted signal, multipath fading simulators and AWGN generators to all IAB-DU *TAB connectors* for diversity reception via a combining network as shown in annex D. 3. +- 2) Adjust the AWGN generator, according to the channel bandwidth defined in table 8.1.3.3.1.4.2-1. + +**Table 8.1.3.3.1.4.2-1: AWGN power level at the IAB-DU input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|-------------------------|-----------------------| +| 15 | 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 | + +- 3) The characteristics of the wanted signal shall be configured according to TS 38.211 [9], and the specific test parameters are configured as blow: + +**Table 8.3.3.1.4.2-2: Test parameters** + +| Parameter | Values | +|--------------------------------------|----------------------------------------------| +| Cyclic prefix | Normal | +| 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$ | + +- 4) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex F. +- 5) Adjust the equipment so that the SNR specified in table 8.1.3.3.1.5-1 and table 8.1.3.3.1.5-2 is achieved at the IAB-DU input during the UCI transmissions. +- 6) The tester sends a test pattern with the pattern outlined in figure 8.1.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.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', arranged horizontally. To the right of the third box are three dots, indicating a repeating pattern.](6424fc1c7a7c26364a135780c1e479f9_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', arranged horizontally. To the right of the third box are three dots, indicating a repeating 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 + +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 and table 8.1.3.3.1.5-2. + +**Table 8.1.3.3.1.5-1: Required SNR for PUCCH format 2 with 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Propagation conditions and correlation matrix (annex F) | Channel bandwidth / SNR (dB) | | +|-----------------------|-----------------------|---------------------------------------------------------|------------------------------|--------| +| | | | 10 MHz | 20 MHz | +| 1 | 2 | TDLC300-100 Low | 6.2 | 6.5 | +| | 4 | TDLC300-100 Low | 1.1 | 0.9 | +| | 8 | TDLC300-100 Low | -2.9 | -2.9 | + +**Table 8.1.3.3.1.5-2: Required SNR for PUCCH format 2 with 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Propagation conditions and correlation matrix (annex F) | Channel bandwidth / SNR (dB) | | | | +|-----------------------|-----------------------|---------------------------------------------------------|------------------------------|-------|-------|--------| +| | | | 10MHz | 20MHz | 40MHz | 100MHz | +| 1 | 2 | TDLC300-100 Low | 6.1 | 6.2 | 6.1 | 6.3 | +| | 4 | TDLC300-100 Low | 0.9 | 0.8 | 0.9 | 1.0 | +| | 8 | TDLC300-100 Low | -3.0 | -3.0 | -2.9 | -2.7 | + +#### 8.1.3.3.2 UCI BLER performance requirements + +##### 8.1.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 IAB-DU is based on the test applicability rules defined in clause 8.1.1.2.3. + +The transient period as specified in TS 38.101-1 [23] clause 6.3.3.1 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.1.3.3.2.2 Minimum requirement + +The minimum requirement is TS 38.174 [2] clause 8.1.3.4.2 + +#### 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 annex B.2. + +RF channels to be tested for single carrier; M; see clause 4.9.1 + +##### 8.1.3.3.2.4.2 Test procedure + +- 1) Connect the IAB-DU tester generating the wanted signal, multipath fading simulators and AWGN generators to all IAB-DU *TAB connectors* for diversity reception via a combining network as shown in annex D. 3. +- 2) Adjust the AWGN generator, according to the channel bandwidth defined in table 8.1.3.3.2.4.2-1. + +**Table 8.1.3.3.2.4.2-1: AWGN power level at the IAB-DU input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|-------------------------|-----------------------| +| 15 | 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 | + +- 3) The characteristics of the wanted signal shall be configured according to TS 38.211 [9], and the specific test parameters are configured as blow: + +**Table 8.1.3.3.2.4.2-2: Test parameters** + +| Parameter | Values | +|--------------------------------------|----------------------------------------------| +| Cyclic prefix | Normal | +| 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 F. + +- 5) Adjust the equipment so that the SNR specified in table 8.1.3.3.2.5-1 or table 8.1.3.3.2.5-2 is achieved at the IAB-DU input during the UCI transmissions. +- 6) 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, indicating a repeating pattern.](18b87e4ce7ef441f5620b8d6539a2939_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, indicating a repeating pattern. + +**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** + +The fraction of incorrectly decoded UCI shall be less than 1% for the SNR listed in table 8.1.3.3.2.5-1 and table 8.1.3.3.2.5-2. + +**Table 8.1.3.3.2.5-1: Required SNR for PUCCH format 2 with 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Propagation conditions and correlation matrix (annex F) | Channel bandwidth / SNR (dB) | | +|-----------------------|-----------------------|---------------------------------------------------------|------------------------------|--------| +| | | | 10 MHz | 20 MHz | +| 1 | 2 | TDLC300-100 Low | 1.4 | 1.8 | +| | 4 | TDLC300-100 Low | -2.6 | -2.6 | +| | 8 | TDLC300-100 Low | -6.1 | -6.2 | + +**Table 8.1.3.3.2.5-2: Required SNR for PUCCH format 2 with 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Propagation conditions and correlation matrix (annex F) | Channel bandwidth / SNR (dB) | | | | +|-----------------------|-----------------------|---------------------------------------------------------|------------------------------|-------|-------|--------| +| | | | 10MHz | 20MHz | 40MHz | 100MHz | +| 1 | 2 | TDLC300-100 Low | 1.1 | 1.7 | 1.0 | 0.9 | +| | 4 | TDLC300-100 Low | -2.7 | -2.3 | -2.7 | -2.8 | +| | 8 | TDLC300-100 Low | -5.2 | -5.2 | -6.1 | -5.3 | + +**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 [23] clause 6.3.3.1 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. + +Which specific test(s) are applicable to IAB-DU is based on the test applicability rules defined in clause 8.1.2.2.3. + +**8.1.3.4.2 Minimum requirement** + +The minimum requirement is in TS 38.174 [2] clause 8.1.3.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 + +##### 8.1.3.4.4.2 Test procedure + +- 1) Connect the IAB-DU tester generating the wanted signal, multipath fading simulators and AWGN generators to all IAB-DU *TAB connectors* for diversity reception via a combining network as shown in annex D.6. +- 2) Adjust the AWGN generator, according to the subcarrier spacing and channel bandwidth defined in table 8.1.3.4.4.2-1. + +**Table 8.1.3.4.4.2-1: AWGN power level at the IAB-DU input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|-------------------------|-----------------------| +| 15 | 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 | + +- 3) The characteristics of the wanted signal shall be configured according to TS 38.211 [9]. The specific test parameters are configured as below: + +**Table 8.1.3.4.4.2-2: Test parameters** + +| Parameter | Test 1 | Test 2 | +|--------------------------------------|----------------------------------------------|--------| +| Cyclic prefix | Normal | | +| 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 F. +- 5) Adjust the equipment so that the SNR specified in table 8.1.3.4.5-1 or table 8.1.3.4.5-2 is achieved at the IAB-DU input during the UCI transmissions. +- 6) The tester sends a test pattern with the pattern outlined in figure 8.1.3.4.4.2-1. The following statistics are kept: the number of incorrectly decoded UCI. + +![Figure 8.1.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', representing UCI transmissions. To the right of the third box is an ellipsis '...', indicating a sequence of transmissions.](889982a45a70fa2e605a553842ce8952_img.jpg) + +Figure 8.1.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', representing UCI transmissions. To the right of the third box is an ellipsis '...', indicating a sequence of transmissions. + +**Figure 8.1.3.4.4.2-1: Test signal pattern for PUCCH format 3 demodulation tests** + +#### 8.1.3.4.5 Test requirement + +The fraction of incorrectly decoded UCI is shall be less than 1% for the SNR listed in table 8.1.3.4.5-1 and table 8.1.3.4.5-2. + +**Table 8.1.3.4.5-1: Required SNR for PUCCH format 3 with 15 kHz SCS** + +| Test Number | Number of TX antennas | Number of RX antennas | Propagation conditions and correlation matrix (annex F) | 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 | +| | | 4 | TDLC300-100 Low | No additional DM-RS | -2.7 | -3.2 | +| | | | | Additional DM-RS | -3.4 | -3.4 | +| | | 8 | TDLC300-100 Low | No additional DM-RS | -6.1 | -6.3 | +| | | | | Additional DM-RS | -6.9 | -7.1 | +| | | 2 | TDLC300-100 Low | No additional DM-RS | 2.8 | 2.6 | +| 2 | 2 | 4 | TDLC300-100 Low | No additional DM-RS | -1.9 | -1.9 | +| | | 8 | TDLC300-100 Low | No additional DM-RS | -5.4 | -5.6 | + +**Table 8.1.3.4.5-2: Required SNR for PUCCH format 3 with 30 kHz SCS** + +| Test Number | Number of TX antennas | Number of RX antennas | Propagation conditions and correlation matrix (annex F) | 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 | +| | | 4 | 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 | 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 | TDLC300-100 Low | No additional DM-RS | 2.4 | 2.6 | 2.6 | 2.1 | +| 2 | 1 | 4 | TDLC300-100 Low | No additional DM-RS | -2.3 | -2.4 | -1.8 | -2.4 | +| | | 8 | TDLC300-100 Low | No additional DM-RS | -5.8 | -5.4 | -5.8 | -5.6 | + +#### 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 [23] clause 6.3.3.1 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. + +Which specific test(s) are applicable to IAB-DU is based on the test applicability rules defined in clause 8.1.1.2.3. + +#### 8.1.3.5.2 Minimum requirement + +The minimum requirement is in TS 38.104 [11] clause 8.1.3.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 + +##### 8.1.3.5.4.2 Test procedure + +- 1) Connect the IAB-DU tester generating the wanted signal, multipath fading simulators and AWGN generators to all IAB-DU *TAB connectors* for diversity reception via a combining network as shown in annex D. 3.. +- 2) Adjust the AWGN generator, according to the subcarrier spacing and channel bandwidth defined in table 8.1.3.5.4.2-1. + +**Table 8.1.3.5.4.2-1: AWGN power level at the IAB-DU input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|-------------------------|-----------------------| +| 15 | 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 | + +- 3) The characteristics of the wanted signal shall be configured according to TS 38.211 [9]. The test parameters are configured as below: + +**Table 8.1.3.5.4.2-2: Test parameters** + +| Parameter | Values | +|--------------------------------------|----------------------------------------------| +| Cyclic prefix | Normal | +| 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 F. +- 5) Adjust the equipment so that the SNR specified in table 8.1.3.5.5-1 or table 8.1.3.5.5-2 is achieved at the IAB-DU input during the UCI transmissions. +- 6) The tester sends a test pattern with the pattern outlined in figure 8.1.3.5.4.2-1. The following statistics are kept: the number of incorrectly decoded UCI. + +![Figure 8.1.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 (ellipsis), indicating a repeating pattern.](8bdf315853992d21f389da554f3a8215_img.jpg) + +Figure 8.1.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 (ellipsis), indicating a repeating pattern. + +**Figure 8.1.3.5.4.2-1: Test signal pattern for PUCCH format 4 demodulation tests** + +#### 8.1.3.5.5 Test requirement + +The fraction of incorrectly decoded UCI is shall be less than 1% for the SNR listed in table 8.1.3.5.5-1 and table 8.1.3.5.5-2. + +**Table 8.1.3.5.5-1: Required SNR for PUCCH format 4 with 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Propagation conditions and correlation matrix (annex F) | 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 | +| | 4 | TDLC300-100 Low | No additional DM-RS | -1.3 | -1.6 | +| | | | Additional DM-RS | -2.0 | -2.1 | +| | 8 | TDLC300-100 Low | No additional DM-RS | -5.1 | -5.2 | +| | | | Additional DM-RS | -5.8 | -5.7 | + +**Table 8.1.3.5.5-2: Required SNR for PUCCH format 4 with 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Propagation conditions and correlation matrix (annex F) | 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 | +| | 4 | 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 | 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.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 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 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.2.3. + +###### 8.1.3.6.1.1.2 Minimum requirement + +The minimum requirement is in TS 38.174 [2] clause 8.1.3.7.2.1. + +###### 8.1.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.1.3.6.1.1.4 Method of test + +###### 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. + +###### 8.1.3.6.1.1.4.2 Test procedure + +- 1) Connect the IAB-DU tester generating the wanted signal, multipath fading simulators and AWGN generators to all IAB-DU *TAB connectors* for diversity reception via a combining network as shown in annex D. 3. +- 2) Adjust the AWGN generator, according to the combinations of SCS and channel bandwidth defined in Table 8.1.3.6.1.1.4.2-1. + +**Table 8.1.3.6.1.1.4.2-1: AWGN power level at the IAB-DU input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|-------------------------|-----------------------| +| 15 | 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 | + +- 3) The characteristics of the wanted signal shall be configured according to TS 38.211 [9], and the specific test parameters are configured as below: + +**Table 8.1.3.6.1.1.4.2-2: Test parameters for multi-slot PUCCH format 1** + +| Parameter | Test | +|---------------------------------------------------------|----------------------------------------| +| Cyclic prefix | Normal | +| 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 F. +- 5) Adjusting the equipment so that the SNR specified in table 8.1.3.6.1.1.5-1 is achieved at the IAB-DU input during the transmissions. +- 6) 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 + +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. + +**Table 8.1.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 | Propagation conditions and correlation matrix (annex F) | Channel bandwidth / SNR (dB) | +|-----------------------|-----------------------|---------------------------------------------------------|------------------------------| +| | | | 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 + +The minimum requirement is in TS 38.174 [2] clause 8.1.3.7.2.2. + +#### 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: M; see clause 4.9.1. + +##### 8.1.3.6.1.2.4.2 Test procedure + +- 1) Connect the IAB-DU tester generating the wanted signal, multipath fading simulators and AWGN generators to all IAB-DU *TAB connectors* for diversity reception via a combining network as shown in annex D. 3. +- 2) Adjust the AWGN generator, according to the combinations of SCS and channel bandwidth defined in table 8.1.3.6.1.2.4.2-1. + +**Table 8.1.3.6.1.2.4.2-1: AWGN power level at the IAB-DU input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|-------------------------|-----------------------| +| 15 | 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 | + +- 3) The characteristics of the wanted signal shall be configured according to TS 38.211 [9], and the specific test parameters are configured as below: + +**Table 8.1.3.6.1.2.4.2-2: Test parameters for multi-slot PUCCH format 1** + +| Parameter | Test | +|---------------------------------------------------------|----------------------------------------| +| Cyclic prefix | Normal | +| 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 F. +- 5) Adjusting the equipment so that the SNR specified in table 8.1.3.6.1.2.5-1 is achieved at the IAB-DU input during the transmissions. +- 6) 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.6.1.1.4.2 for NACK to ACK detection. Both statistics are measured in the same testing. + +#### 8.1.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.1.3.6.1.2.5-1. + +**Table 8.1.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 | Propagation conditions and correlation matrix (annex F) | Channel bandwidth / 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 requirements + +##### 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 and TDLC300-100, 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 and TDLC300-100** + +| PRACH preamble | PRACH SCS (kHz) | Time error tolerance | | +|------------------------|-----------------|----------------------|-------------| +| | | AWGN | TDLC300-100 | +| 0 | 1.25 | 1.04 us | 2.55 us | +| A1, A2, A3, B4, C0, C2 | 15 | 0.52 us | 2.03 us | +| | 30 | 0.26 us | 1.77 us | + +The test preambles for normal mode are listed in A.2.5-1. + +Which specific test(s) are applicable to IAB-DU is based on the test applicability rules defined in clause 8.1.1.2.4. + +##### 8.1.4.1.2 Minimum requirement + +The minimum requirement is in TS 38.174 [2] clause 8.1.4.1 and 8.1.4.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 annex B.2. + +RF channels to be tested: for single carrier: M; see clause 4.9.1. + +##### 8.1.4.1.4.2 Test procedure + +- 1) Connect the IAB-DU tester generating the wanted signal, multipath fading simulators and AWGN generators to all IAB-DU *TAB connectors* for diversity reception via a combining network as shown in annex D. 3. +- 2) Adjust the AWGN generator, according to the SCS and channel bandwidth. + +**Table 8.1.4.1.4.2-1: AWGN power level at the IAB-DU input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|-------------------------|----------------------| +| 15 | 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 | + +- 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 F. +- 5) Adjust the frequency offset of the test signal according to table 8.1.4.1.5-1 or 8.1.4.1.5-2 or 8.1.4.1.5-3 or 8.1.4.1.6-1 or 8.1.4.1.6-2 or 8.1.4.1.6-3 or 8.1.4.1.6-4. +- 6) Adjust the equipment so that the SNR specified in table 8.1.4.1.5-1 or 8.1.4.1.5-2 or 8.1.4.1.5-3 or 8.1.4.1.6-1 or 8.1.4.1.6-2 or 8.1.4.1.6-3 or 8.1.4.1.6-4 is achieved at the IAB-DU 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.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. + +![Figure 8.1.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.](851584a7a34f04e13a0ae8dc57f1a7be_img.jpg) + +Figure 8.1.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.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 $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.1.4.1.4.2-2. + +![Timing offset scheme for PRACH preamble format 0 diagram](1fd763be1b7a05b52e554f0583617642_img.jpg) + +A diagram illustrating the timing offset scheme for PRACH preamble format 0. It shows a horizontal timeline divided into 10 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 tenth segment, indicating a loop or reset mechanism. + +Timing offset scheme for PRACH preamble format 0 diagram + +**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.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.1.4.1.4.2-3. + +![Timing offset scheme for PRACH preamble format A1 A2, A3, B4, C0 and C2 diagram](d0dd433695a01d364ac98f846f68bc8f_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 10 segments, downward-pointing arcs with arrowheads, 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.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** + +Pfa shall not exceed 0.1%. Pd shall not be below 99% for the SNRs in tables 8.1.4.1.5-1 to 8.1.4.1.5-3. + +**Table 8.1.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 F) | 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.1.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 F) | 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.1.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 F) | 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 | + +## 8.2 IAB-MT Performance requirements + +### 8.2.1 General + +#### 8.2.1.1 Scope and definitions + +Conducted performance requirements specify the ability of the IAB-MT to correctly demodulate signals in various conditions and configurations. Conducted performance requirements are specified at the TAB connector(s). + +Conducted performance requirements for the IAB-MT are specified for the fixed reference channels and the propagation conditions defined in TS 38.174 [2] annex A and annex F, respectively. The requirements only apply to those FRCs that are supported by the IAB-MT. + +Unless stated otherwise, performance requirements apply for a single carrier only. Performance requirements for an IAB-MT supporting CA are defined in terms of single carrier requirements. + +The SNR used in this clause is specified based on a single carrier and defined as: + +$$\text{SNR} = S / N$$ + +Where: + +S is the total signal energy in a slot on a single *TAB connector*. + +N is the noise energy in a bandwidth corresponding to the transmission bandwidth over the duration of a slot. + +## 8.2.2 Demodulation performance requirements + +### 8.2.2.1 General + +#### 8.2.2.1.1 Applicability of requirements + +##### 8.2.2.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.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, the PDSCH 256QAM tests (Test 1-1 of Clause 8.2.2.2.5) shall apply only if 256QAM for PDSCH for FR1 is declared to be supported (see D.200 in table 4.6-1, *pdsch-256QAM-FR1*). + +Unless otherwise stated, the PDSCH tests (Tests 4, 5 of clause 8.2.2.2.5) 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, the PDSCH tests (Tests 3, 4, 5 of clause 8.2.2.2.5) 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, *maxConfigNumberPortsAcrossNZP-CSI-RS-PerCC*). + +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. + +#### 8.2.2.2.2 Minimum requirement + +The minimum requirement is in TS 38.174 [2] clause 8.2.2.1.2. + +#### 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_i$ ; 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.2.2.4.2 Procedure + +- 1) Connect the IAB tester generating the wanted signal, multipath fading simulators and AWGN generators to all IAB-MT *TAB connectors* for diversity reception via a combining network as shown in annex D.6. +- 2) Adjust the AWGN generator and adjust the AWGN power level to -77.2 dBm / 38.16MHz. +- 3) The characteristics of the wanted signal shall be configured according to the corresponding DL reference measurement channel defined in annex A and the test parameters in table 8.2.2.2.4.2-1. + +**Table 8.2.2.2.4.2-1: Test parameters for testing PDSCH** + +| Parameter | Unit | Value | +|-----------------------------------------------------------|----------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Duplex mode | | TDD | +| Active BWP index | | 1 | +| Default TDD UL-DL pattern (Note 1) | | 7D1S2U, S=6D:4G:4U | +| PDSCH transmission scheme | | Transmission scheme 1 | +| Carrier configuration | Offset between Point A and the lowest usable subcarrier on this carrier (Note 1) | RBs 0 | +| | Subcarrier spacing | kHz 30 | +| DL BWP configuration #1 | Cyclic prefix | Normal | +| | RB offset | RBs 0 | +| | Number of contiguous PRB | PRBs 106 | +| PDSCH DMRS configuration | Antenna ports indexes | {1000} for Rank 1 tests
{1000, 1001} for Rank 2 tests
{1000-1002} for Rank 3 tests
{1000-1003} for Rank 4 tests | +| | Position of the first DMRS for PDSCH mapping type A | 2 | +| | Number of PDSCH DMRS CDM group(s) without data | 1 for Rank 1 and Rank 2 tests
2 for Rank 3 and Rank 4 tests | +| | DMRS Type | Type 1 | +| | Number of additional DMRS | 1 | +| | Maximum number of OFDM symbols for DL front loaded DMRS | 1 | +| | | | +| PDSCH configuration | Mapping type | Type A | +| | k0 | 0 | +| | Starting symbol (S) | 2 | +| | Length (L) | Specific to each Reference channel | +| | PDSCH aggregation factor | 1 | +| | PRB bundling type | Static | +| | PRB bundling size | 2 | +| | Resource allocation type | Type 0 | +| | RBG size | Config2 | +| | VRB-to-PRB mapping type | Non-interleaved | +| | VRB-to-PRB mapping interleaver bundle size | N/A | +| PT-RS configuration | | PT-RS is not configured | +| Maximum number of code block groups for ACK/NACK feedback | | 1 | +| Maximum number of HARQ transmission | | 4 | +| HARQ ACK/NACK bundling | | Multiplexed | +| Redundancy version coding sequence | | {0,2,3,1} | +| PDSCH & PDSCH DMRS Precoding configuration | | Single Panel Type I, Random precoder selection updated per slot, with equal probability of each applicable $i_1, i_2$ combination, and with PRB bundling granularity | + +NOTE 1: The same requirements are applicable to TDD with different UL-DL patterns. + +NOTE 2: Point A coincides with minimum guard band as specified in TS 38.174 [2] for tested channel bandwidth and subcarrier spacing. + +- 4) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex F. +- 5) Adjust the equipment so that required SNR specified in tables 8.2.2.2.5.1-1, 8.2.2.2.5.1-2, 8.2.2.2.5.1-3 or 8.2.2.2.5.2-1-4 (as applicable) is achieved at the IAB-MT input. +- 6) For each of the reference channels in tables 8.2.2.2.5.1-1, 8.2.2.2.5.1-2, 8.2.2.2.5.1-3 or 8.2.2.2.5.2-1-4 applicable for the IAB-MT, measure the throughput. + +### 8.2.2.2.5 Test requirement + +The throughput measured according to clause 8.2.2.2.4.2 shall not be below the limits for the SNR levels specified in table 8.2.2.2.5-1, 8.2.2.2.5-2, 8.2.2.2.5-3 and 8.2.2.2.5-4. + +**Table 8.2.2.2.5-1: Minimum performance for Rank 1** + +| Test num. | Reference channel | Bandwidth (MHz) / Subcarrier spacing (kHz) | Modulation format and code rate | Propagation condition | Correlation matrix and antenna configuration | Reference value | | +|-----------|-------------------|--------------------------------------------|---------------------------------|-----------------------|----------------------------------------------|------------------------------------|----------| +| | | | | | | Fraction of maximum throughput (%) | SNR (dB) | +| 1 | M-FR1-A.3.3-1 | 40 / 30 | 256QAM, 0.82 | TDLA30-10 | 2x4, ULA Low | 70 | 22.5] | +| 2 | M-FR1-A.3.1-1 | 40 / 30 | 16QAM, 0.48 | TDLA30-10 | 2x4, ULA Low | 30 | -0.1 | + +**Table 8.2.2.2.5-2: Minimum performance for Rank 2** + +| Test num. | Reference channel | Bandwidth (MHz) / Subcarrier spacing (kHz) | Modulation format and code rate | Propagation condition | Correlation matrix and antenna configuration | Reference value | | +|-----------|-------------------|--------------------------------------------|---------------------------------|-----------------------|----------------------------------------------|------------------------------------|----------| +| | | | | | | Fraction of maximum throughput (%) | SNR (dB) | +| 3 | M-FR1-A.3.2-1 | 40 / 30 | 64QAM, 0.50 | TDLA30-10 | 2x4, ULA Low | 70 | 14.6 | + +**Table 8.2.2.2.5-3: Minimum performance for Rank 3** + +| Test num. | Reference channel | Bandwidth (MHz) / Subcarrier spacing (kHz) | Modulation format and code rate | Propagation condition | Correlation matrix and antenna configuration | Reference value | | +|-----------|-------------------|--------------------------------------------|---------------------------------|-----------------------|----------------------------------------------|------------------------------------|----------| +| | | | | | | Fraction of maximum throughput (%) | SNR (dB) | +| 4 | M-FR1-A.3.1-3 | 40 / 30 | 16QAM, 0.48 | TDLA30-10 | 4x4, ULA Low | 70 | 12.4 | + +**Table 8.2.2.2.5-4: Minimum performance for Rank 4** + +| Test num. | Reference channel | Bandwidth (MHz) / Subcarrier spacing (kHz) | Modulation format and code rate | Propagation condition | Correlation matrix and antenna configuration | Reference value | | +|-----------|-------------------|--------------------------------------------|---------------------------------|-----------------------|----------------------------------------------|------------------------------------|----------| +| | | | | | | Fraction of maximum throughput (%) | SNR (dB) | +| 5 | M-FR1-A.3.1-4 | 40 / 30 | 16QAM, 0.48 | TDLA30-10 | 4x4, ULA Low | 70 | 16.4 | + +### 8.2.2.3 Performance requirements for PDCCH + +#### 8.2.2.3.1 Definition and applicability + +The performance requirement of PDCCH is determined by a maximum allowed missed detection rate for a given SNR. The required missed detection rate is expressed for the FRCs listed in annex A. + +#### 8.2.2.3.2 Minimum requirement + +The minimum requirement is in TS 38.174 [2] clause 8.2.2.2. + +### 8.2.2.3.3 Test purpose + +The test shall verify the receiver's ability to achieve missed detection rate 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_i$ ; see clause 4.9.1. + +RF channels to be tested for carrier aggregation: $M_{BW\ Channel\ CA}$ ; see clause 4.9.1. + +#### 8.2.2.3.4.2 Procedure + +- 1) Connect the IAB tester generating the wanted signal, multipath fading simulators and AWGN generators to all IAB-MT *TAB connectors* for diversity reception via a combining network as shown in annex D.6. +- 2) Adjust the AWGN generator and adjust the AWGN power level to -77.2 dBm / 38.16MHz. +- 3) The characteristics of the wanted signal shall be configured according to the corresponding DL reference measurement channel defined in annex A and the test parameters in table 8.2.2.3.4.2-1. + +**Table 8.2.2.3.4.2-1: Test parameters for testing PDCCH** + +| Parameter | Unit | 1 Tx Antenna | 2 Tx Antenna | +|-------------------------|------|--------------|--------------| +| CCE to REG mapping type | | interleaved | interleaved | +| Interleaver size | | | 3 | +| REG bundle size | | 2 | 6 | +| Shift Index | | | 0 | + +- 4) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex F. +- 5) Adjust the equipment so that required SNR specified in tables 8.2.2.3.5.1-1, 8.2.2.3.5.2-2, 8.2.2.3.6.1-3, 8.2.2.3.6.2-4 (as applicable) is achieved at the IAB-MT input. +- 6) For each of the reference channels in table 8.2.2.3.5.1-1, 8.2.2.3.5.2-2, 8.2.2.3.6.1-3, 8.2.2.3.6.2-4 applicable for the IAB-MT, measure the missed detection. + +### 8.2.2.3.5 Test requirement + +For the parameters specified in Table 8.2.2.3.4.2.1-1, the average probability of a missed downlink scheduling grant ( $Pm-dsg$ ) shall be below the specified value in Table 8.2.2.3.5-1. + +**Table 8.2.2.3.5-1: Minimum performance for PDCCH** + +| Test number | Bandwidth (MHz) | CORESET RB | CORESET duration | Aggregation level | Reference Channel | Propagation Condition | Antenna configuration and correlation Matrix | Reference value | | +|-------------|-----------------|------------|------------------|-------------------|-------------------|-----------------------|----------------------------------------------|-----------------|----------| +| | | | | | | | | Pm-dsg (%) | SNR (dB) | +| 1 | 40 | 102 | 1 | 2 | M-FR1-A.3.4-1 | TDLA30-10 | 1x4 Low | 1 | 2.1 | +| 2 | 40 | 102 | 1 | 4 | M-FR1-A.3.4-2 | TDLA30-10 | 1x4 Low | 1 | -0.9 | +| 3 | 40 | 90 | 1 | 8 | M-FR1-A.3.4-3 | TDLA30-10 | 2x4 Low | 1 | -4.3 | + +## 8.2.3 CSI reporting requirements + +### 8.2.3.1 General + +#### 8.2.3.1.1 Applicability rule for IAB-MT + +##### 8.2.3.1.1.1 General + +Unless otherwise stated, for an IAB-MT declared to support more than 4 *TAB connectors* (for *IAB type 1-H*), the performance requirement tests for 4 RX antennas shall apply, and the specific connectors used for testing is up to IAB-MT implementation. + +Testing of performance requirements for RI and PMI reporting is optional. + +##### 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.14 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 requirements for IAB-MT features + +Unless otherwise stated, for *IAB type 1-H*, the CSI reporting tests 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-H*, the CSI reporting 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*). + +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 | +|------------------------------------|----------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------| +| PDSCH transmission scheme | | Transmission scheme 1 | +| Duplex mode | | TDD | +| PTRS epre-Ratio | | N/A | +| Actual carrier configuration | Offset between Point A and the lowest usable subcarrier on this carrier (Note 3) | RBs 0 | +| | Subcarrier spacing | kHz 30 | +| DL BWP configuration #1 | Cyclic prefix | Normal | +| | RB offset | RBs 0 | +| | Number of contiguous PRB | PRBs 106 | +| Active DL BWP index | | 1 | +| PDSCH configuration | Mapping type | Type A | +| | k0 | 0 | +| | Starting symbol (S) | 2 | +| | Length (L) | 12 | +| | PDSCH aggregation factor | 1 | +| | PRB bundling type | Static | +| | PRB bundling size | 2 | +| | Resource allocation type | Type 0 | +| | VRB-to-PRB mapping type | Non-interleaved | +| | VRB-to-PRB mapping interleaver bundle size | N/A | +| PDSCH DMRS configuration | DMRS Type | Type 1 | +| | Number of additional DMRS | 1 | +| | Maximum number of OFDM symbols for DL front loaded DMRS | 1 | +| | DMRS ports indexes | {1000} for Rank1
{1000, 1001} for Rank2
{1000, 1001, 1002} for Rank3
{1000, 1001, 1002, 1003} for Rank4 | +| | Number of PDSCH DMRS CDM group(s) without data | 2 | +| PTRS configuration | Frequency density ( $K_{PT-RS}$ ) | N/A | +| | Time density ( $L_{PT-RS}$ ) | N/A | +| | Resource Element Offset | N/A | +| NZP CSI-RS for CSI acquisition | Frequency Occupation | Start PRB 0
Number of PRB = BWP size | +| Redundancy version coding sequence | | {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 [23] for tested channel bandwidth and subcarrier spacing. + +## 8.2.3.2 Reporting Channel Quality Indicator (CQI) + +### 8.2.3.2.1 Definition and applicability + +The reporting accuracy of the channel quality indicator (CQI) under frequency non-selective conditions is determined by the reporting variance and the BLER performance using the transport format indicated by the reported CQI median. The purpose is to verify that the reported CQI values are in accordance with the CQI definition given in TS 38.214 [24]. 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. + +Which specific test(s) are applicable to IAB-MT is based on the test applicability rules defined in clause 8.2.1.2. + +#### 8.2.3.2.2 Minimum requirement + +The minimum requirement is in TS 38.174 [2] clause 8.2.3.1. + +#### 8.2.3.2.3 Test purpose + +The test shall verify the receiver's ability to report CQI values accordance with the CQI definition given in TS 38.214 [24]. + +#### 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. + +##### 8.2.3.2.4.2 Test procedure + +- 1) Connect the IAB-MT tester generating the wanted signal and AWGN generators to all IAB-MT *TAB* connectors for diversity reception via a combining network as shown in annex D.5 and D.6. +- 2) Adjust the AWGN generator, according to the channel bandwidth, defined in table 8.2.3.2.4.2-1. + +**Table 8.2.3.2.4.2-1: AWGN power level at the IAB-MT input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|-------------------------|----------------------| +| 30 kHz | 40 | -77.2 dBm / 38.16MHz | + +- 3) The characteristics of the wanted signal shall be configured according to the corresponding DL reference measurement channel defined in annex A and the test parameters in table 8.2.3.2.4.2-2. + +**Table 8.2.3.2.4.2-2: Test parameters for testing CQI reporting** + +| Parameter | Unit | Test 1 | Test 2 | +|-------------------------------------|------------------------------------------------------------------|---------------------------|-------------------| +| Bandwidth | MHz | | 40 | +| Subcarrier spacing | kHz | | 30 | +| Default TDD UL-DL pattern (Note 1) | | 7D1S2U, S=6D:4G:4U | | +| SNR | dB | 5 6 11 12 | | +| Propagation channel | | AWGN | | +| Antenna configuration | | 2x4 | | +| Beamforming Model | | As specified in Annex J.3 | | +| NZP CSI-RS for CSI acquisition | CSI-RS resource Type | | Periodic | +| | Number of CSI-RS ports ( $X$ ) | | 2 | +| | CDM Type | | FD-CDM2 | +| | Density ( $\rho$ ) | | 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 | +| | CodebookSubsetRestriction | | 010000 | +| | RI Restriction | | N/A | +| CQI/RI/PMI delay | ms | 9.5 | | +| Maximum number of HARQ transmission | | 1 | | +| Measurement channel | | M-FR1-A.3.5-2 | | + +NOTE 1: The same requirements are applicable for TDD with different UL-DL pattern. + +- 4) Adjust the equipment so that required SNR specified in table 8.2.3.2.4.2-2 is achieved at the IAB-MT input. +- 5) For each test specified in table 8.2.3.2.4.2-2 applicable for the IAB-MT, measure the median CQI and the BLER at median CQI and (median CQI+1 or median CQI-1) as per clause 8.2.3.2.5. + +### 8.2.3.2.5 Test requirement + +For the parameters specified in Table 8.2.3.2.4.2-2, and using the downlink physical channels specified in Annex A, the test requirements are specified by the following: + +- a) 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. +- b) 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.3 Reporting of Precoding Matrix Indicator (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 $y$ , for 4TX and 8TX PMI requirements, $t_{follow1, follow2}$ is 90 % of the maximum throughput obtained at $SNR_{follow1, follow2}$ using the precoders configured according to the IAB-MT reports, and $t_{rnd1, rnd2}$ is the throughput measured at $SNR_{follow1, follow2}$ with random precoding. + +#### 8.2.3.3.2 Minimum requirement + +The minimum requirement is in TS 38.174 [2] clause 8.2.3.2. + +#### 8.2.3.3.3 Test purpose + +The test shall verify the receiver's ability to achieve throughput gain under multipath fading propagation conditions using reporting PMI comparing to using random PMI. + +#### 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. + +##### 8.2.3.3.4.2 Test procedure + +- 1) Connect the IAB-MT tester generating the wanted signal and AWGN generators to all IAB-MT *TAB* connectors for diversity reception via a combining network as shown in annex D.5 and D.6. +- 2) Adjust the AWGN generator, according to the channel bandwidth, defined in table 8.2.3.3.4.2-1. + +**Table 8.2.3.3.4.2-1: AWGN power level at the IAB-MT input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|-------------------------|----------------------| +| 30 kHz | 40 | -77.2 dBm / 38.16MHz | + +- 3) The characteristics of the wanted signal shall be configured according to the corresponding DL reference measurement channel defined in annex A and the test parameters in table 8.2.3.3.4.2-2. + +**Table 8.2.3.3.4.2-2: Test parameters for testing PMI reporting** + +| Parameter | Unit | Test 1 | Test 2 | +|-------------------------------------|------------------------------------------------------------------|----------------------------------|----------------------------------| +| Bandwidth | MHz | 40 | 40 | +| Subcarrier spacing | kHz | 30 | 30 | +| Default TDD UL-DL pattern (Note 1) | | 7D1S2U,
S=6D:4G:4U | 7D1S2U,
S=6D:4G:4U | +| Propagation channel | | TDLA30-5 | TDLA30-5 | +| Antenna configuration | | High XP 4 x 4
(N1,N2) = (2,1) | High XP 8 x 4
(N1,N2) = (4,1) | +| Beamforming Model | | As specified in
Annex J.3 | As specified in
Annex J.3 | +| NZP CSI-RS for CSI acquisition | CSI-RS resource Type | Periodic | Periodic | +| | Number of CSI-RS ports (X) | 4 | 8 | +| | CDM Type | FD-CDM2 | CDM4 (FD2, TD2) | +| | Density (ρ) | 1 | 1 | +| | First subcarrier index in the PRB used for CSI-RS ( $k_0, k_1$ ) | Row 4, (0,-) | Row 8, (4,6) | +| | First OFDM symbol in the PRB used for CSI-RS ( $l_0, l_1$ ) | (13,-) | (5,-) | +| | NZP CSI-RS-timeConfig periodicity and offset | slot 10/1 | slot 10/1 | +| ReportConfigType | | Periodic | Periodic | +| CQI-table | | Table 1 | Table 1 | +| reportQuantity | | cri-RI-PMI-CQI | cri-RI-PMI-CQI | +| cqi-FormatIndicator | | Wideband | Wideband | +| pmi-FormatIndicator | | Wideband | Wideband | +| Sub-band Size | RB | 16 | 16 | +| csi-ReportingBand | | 1111111 | 1111111 | +| CSI-Report periodicity and offset | slot | 10/9 | 10/9 | +| Codebook configuration | Codebook Type | typeI-SinglePanel | typeI-SinglePanel | +| | Codebook Mode | 1 | 1 | +| | (CodebookConfig-N1,CodebookConfig-N2) | (2,1) | (4,1) | +| | (CodebookConfig-O1,CodebookConfig-O2) | (4,1) | (4,1) | +| | CodebookSubsetRestriction | 1111111 | 0x FFFF | +| | RI Restriction | 00000001 | 00000010 | +| CQI/RI/PMI delay | ms | 5.5 | 6.5 | +| Maximum number of HARQ transmission | | 4 | 4 | +| Measurement channel | | M-FR1-A.3.5-5 | M-FR1-A.3.5-6 | + +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 granularity) with equal probability of each applicable $i_1, i_2$ 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)$ for Test 1 or slot# $(n-6)$ for Test 2, this reported PMI cannot be applied at the gNB downlink before slot# $(n+4)$ for Test 1 or slot# $(n+6)$ for Test 2 respectively. + +NOTE 4: Randomization of the principle beam direction shall be used as specified in Annex F.2.4.2.4. + +- 4) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex F. +- 5) Adjust the equipment so that required SNR specified in clause 8.2.3.3.1 is achieved at the IAB-MT input. +- 6) For each test specified in table 8.2.3.3.4.2-2 applicable for the IAB-MT, calculate $\gamma$ . + +### 8.2.3.3.5 Test requirement + +For the parameters specified in Table 8.2.3.3.4.2-2, and using the downlink physical channels specified in Annex A, the test requirements are specified in Table 8.2.3.3.5-1. + +**Table 8.2.3.3.5-1 Test requirements for PMI reporting** + +| Parameter | Test 1 | Test 2 | +|-----------|--------|--------| +| $\gamma$ | 1.29 | 1.49 | + +## 8.2.3.4 Reporting of Rank Indicator (RI) + +### 8.2.3.4.1 General + +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 requirements + +The minimum requirement is in TS 38.174 [2] clause 8.2.3.3. + +### 8.2.3.4.3 Test purpose + +The test shall verify the receiver's ability to report rank indicator accurately represents the channel rank. + +### 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. + +#### 8.2.3.4.4.2 Test procedure + +- 1) Connect the IAB-MT tester generating the wanted signal and AWGN generators to all IAB-MT *TAB* connectors for diversity reception via a combining network as shown in annex D.5 and D.6. +- 2) Adjust the AWGN generator, according to the channel bandwidth, defined in table 8.2.3.4.4.2-1. + +**Table 8.2.3.4.4.2-1: AWGN power level at the IAB-MT input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|-------------------------|----------------------| +| 30 kHz | 40 | -77.2 dBm / 38.16MHz | + +- 3) The characteristics of the wanted signal shall be configured according to the corresponding DL reference measurement channel defined in annex A and the test parameters in table 8.2.3.4.4.2-2. + +**Table 8.2.3.4.4.2-2: Test parameters for testing RI reporting** + +| Parameter | Unit | Test 1 | Test 2 | Test 3 | Test 4 | +|-------------------------------------|------------------------------------------------------------|----------------------------------------------------|----------------------------------------------------|----------------------------------------------------|------------------------------------------------------| +| Bandwidth | MHz | 40 | 40 | 40 | 40 | +| Subcarrier spacing | kHz | 30 | 30 | 30 | 30 | +| Default TDD UL-DL pattern (Note 1) | | 7D1S2U,
S=6D:4G:4U | 7D1S2U,
S=6D:4G:4U | 7D1S2U,
S=6D:4G:4U | 7D1S2U,
S=6D:4G:4U | +| SNR | | -2 | 16 | 16 | 22 | +| Propagation channel | | TDLA30-5 | TDLA30-5 | TDLA30-5 | TDLA30-5 | +| Antenna configuration | | ULA Low 2x4 | ULA Low 2x4 | ULA High 2x4 | ULA Low 4x4 | +| Beamforming Model | | As specified in Annex J.3 | As specified in Annex J.3 | As specified in Annex J.3 | As specified in Annex J.3 | +| NZP CSI-RS for CSI acquisition | CSI-RS resource Type | Periodic | Periodic | Periodic | Periodic | +| | Number of CSI-RS ports (X) | 2 | 2 | 2 | 4 | +| | CDM Type | FD-CDM2 | FD-CDM2 | FD-CDM2 | FD-CDM2 | +| | Density (p) | 1 | 1 | 1 | 1 | +| | First subcarrier index in the PRB used for CSI-RS (k0, k1) | Row 3 (6,-) | Row 3 (6,-) | Row 3 (6,-) | Row 4 (0,-) | +| | First OFDM symbol in the PRB used for CSI-RS (l0, l1) | (13,-) | (13,-) | (13,-) | (13,-) | +| | NZP CSI-RS-timeConfig periodicity and offset | slot 10/1 | slot 10/1 | slot 10/1 | slot 10/1 | +| ReportConfigType | | Periodic | Periodic | Periodic | Periodic | +| CQI-table | | Table 2 | Table 2 | Table 2 | Table 2 | +| reportQuantity | | cri-RI-PMI-CQI | cri-RI-PMI-CQI | cri-RI-PMI-CQI | cri-RI-PMI-CQI | +| cqi-FormatIndicator | | Wideband | Wideband | Wideband | Wideband | +| pmi-FormatIndicator | | Wideband | Wideband | Wideband | Wideband | +| Sub-band Size | RB | 16 | 16 | 16 | 16 | +| csi-ReportingBand | | 11111111 | 11111111 | 11111111 | 11111111 | +| CSI-Report periodicity and offset | slot | 10/9 | 10/9 | 10/9 | 10/9 | +| Codebook configuration | Codebook Type | typeI-SinglePanel | typeI-SinglePanel | typeI-SinglePanel | typeI-SinglePanel | +| | Codebook Mode | 1 | 1 | 1 | 1 | +| | (CodebookConfig-N1, CodebookConfig-N2) | N/A | N/A | N/A | (2,1) | +| | CodebookSubsetRestriction | 010000 for fixed rank 2, 010011 for following rank | 000011 for fixed rank 1, 010011 for following rank | 000011 for fixed rank 1, 010011 for following rank | 11111111 | +| | RI Restriction | N/A | N/A | N/A | 00000010 for fixed Rank 2 and 00001111 for follow RI | +| CQI/RI/PMI delay | ms | 9.5 | 9.5 | 9.5 | 9.5 | +| Maximum number of HARQ transmission | | 1 | 1 | 1 | 1 | +| RI Configuration | | Fixed RI = 2 and follow RI | Fixed RI = 1 and follow RI | Fixed RI = 1 and follow RI | Fixed RI = 2 and follow RI | + +NOTE 1: The same requirements are applicable for TDD with different UL-DL pattern. +NOTE 2: Measurements channels are specified in Table A.3.5-1. M-FR1-A.3.5-1 is used for Rank 1 case. M-FR1-A.3.5-2 is used for Rank 2 case. M-FR1-A.3.5-3 is used for Rank 3 case. M-FR1-A.3.5-4 is used for Rank 4 case. + +- 4) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex F. +- 5) Adjust the equipment so that required SNR specified in Table 8.2.3.4.4.2-2 is achieved at the IAB-MT input. +- 6) For each test specified in table 8.2.3.4.4.2-2 applicable for the IAB-MT, calculate $\gamma$ . + +#### 8.2.3.4.5 Test requirement + +The test requirement for RI reporting is defined as + +- a) 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$ ; +- b) 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-2 and using the downlink physical channels specified in Annex A, the test requirements are specified in Table 8.2.3.4.5-1. + +**Table 8.2.3.4.5-1 Test requirements for RI reporting** + +| | Test 1 | Test 2 | Test 3 | Test 4 | +|------------|---------------|---------------|---------------|---------------| +| $\gamma_1$ | N/A | 1.05 | 0.9 | N/A | +| $\gamma_2$ | 0.9 | N/A | N/A | 0.9 | + +## 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-1 [13] applies to FR1 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. + +**Table A.1.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 [9]. + +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 $K$ in sub-clause 5.2.2 of TS 38.212 [10]. + +### 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. + +**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 [9]. + +Note 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [10]. + +**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 [9]. + +Note 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [10]. + +**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 [9]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [10]. + +## A.2.2 Fixed Reference Channels for PUSCH performance requirements (16QAM, R=434/1024) + +## 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. + +**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 [9]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [10]. + +**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 [9]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [10]. + +## 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. + +**Table A.2.3-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 [9]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [10]. + +## 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 | + +## 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 + +**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 | M-FR1-A.3.1-4 | M-FR1-A.3.1-5 | +|-----------------------------------------|---------------|---------------|---------------|---------------|---------------| +| Channel bandwidth (MHz) | 40 | 40 | 40 | 40 | 40 | +| Subcarrier spacing (kHz) | 30 | 30 | 30 | 30 | 30 | +| Allocated resource blocks | 106 | 106 | 106 | 106 | 106 | +| Number of consecutive PDSCH symbols | 12 | 12 | 12 | 12 | 12 | +| MCS table | 64QAM | 64QAM | 64QAM | 64QAM | 64QAM | +| MCS index | 13 | 13 | 13 | 13 | 13 | +| Modulation | 16QAM | 16QAM | 16QAM | 16QAM | 16QAM | +| Target Coding Rate | 490/1024 | 490/1024 | 490/1024 | 490/1024 | 490/1024 | +| Number of MIMO layers | 1 | 3 | 4 | 1 | 2 | +| Number of DMRS REs | 12 | 24 | 24 | 24 | 24 | +| Overhead for TBS determination | 0 | 0 | 0 | 0 | 0 | +| Information Bit Payload per Slot (bits) | 26632 | 73776 | 98376 | 24576 | 49176 | +| Transport block CRC per Slot (bits) | 24 | 24 | 24 | 24 | 24 | +| Number of Code Blocks per Slot | 4 | 9 | 12 | 3 | 6 | +| Binary Channel Bits Per Slot (bits) | 55968 | 152640 | 203520 | 50880 | 101760 | + +### 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. + +**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 | + +### 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.5-1 for FR1 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 | + +### A.3.5 Fixed Reference Channels for CSI reporting performance requirements + +This clause defines the DL signal applicable to the reporting of channel state information + +Tables A.3.5-1 specifies the mapping of CQI index to Information Bit payload, which complies with the CQI definition specified in clause 5.2.2.1 of TS 38.214 [24] and with MCS definition specified in clause 5.1.3 of TS 38.214 [24]. + +The parameters for the reference measurement channels are specified in table A.3.5-2 for FR1 PMI reporting performance requirements + +**Table A.3.5-1: Fixed Reference Channels for CSI reporting** + +| Reference channel | | | | M-FR1-A.2.5-1 | M-FR1-A.2.5-2 | M-FR1-A.2.5-3 | M-FR1-A.2.5-4 | +|-------------------------------------------|---------------------|-----------|------------|---------------|---------------|---------------|---------------| +| MCS table | | | | 256QAM | | | | +| 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 | | | | | +| 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** + +| 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 | + +--- + +## Annex B (normative): Environmental requirements for the IAB equipment + +### B.1 General + +For each test in the present document, the environmental conditions under which the IAB 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 + +#### 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 [17]. +- 2) The equipment class for the equipment under test, as defined in the IEC 60 721-3-4 [18]. +- 3) The equipment that does not comply with the mentioned classes, the relevant classes from IEC 60 721 [19] 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 [20]. + +**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 [21]. + +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 [22]. 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 [20] Test Ab/Ad and IEC 60 068-2-2 [21] 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 [20] Test Ab/Ad and IEC 60 068-2-2 [21] 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. + + + +--- + +## 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.174 [2] | Test Tolerance (TT) | Test requirement in the present document | +|--------------------------------------------------------------------------|--------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------| +| 6.2 IAB output power | See TS 38.174 [2], clause 6.2 | Normal and extreme conditions:
0.7 dB, $f \leq 3.0$ GHz
1.0 dB, $3.0$ GHz $< f \leq 6$ GHz (Note 1) | Formula:
Upper limit + TT, Lower limit - TT | +| 6.3.1 IAB-DU Output power dynamics | See TS 38.174 [2], clause 6.3.1 | 0.4 dB | Formula:
Total power dynamic range – TT (dB) | +| 6.3.2 IAB-MT Total power dynamic range | See TS 38.174 [2], clause 6.3.2 | $\pm 0.7$ dB, $BW \leq 40$ MHz
$\pm 1.0$ dB, $40$ MHz $< f \leq 100$ MHz | Formula:
Total power dynamic range – TT (dB) | +| 6.4.1 Transmitter OFF power | See TS 38.174 [2], clause 6.4.1 | 2.0 dB, $f \leq 3.0$ GHz
2.5 dB, $3.0$ GHz $< f \leq 6$ GHz (Note 1) | Formula:
Minimum Requirement + TT | +| 6.4.2 Transient period | See TS 38.174 [2], clause 6.4.2 | N/A | | +| 6.5.2.1 IAB-DU Frequency error | See TS 38.174 [2], clause 6.5.1.1 | 12 Hz | Formula:
Frequency Error limit + TT | +| 6.5.2.2 IAB-MT Frequency error | See TS 38.174 [2], clause 6.5.1.2 | $\pm 15$ Hz, $f \leq 3.0$ GHz
$\pm 36$ Hz, $f > 3.0$ GHz | Formula:
Frequency Error limit + TT | +| 6.5.4 Modulation quality (EVM) | See TS 38.174 [2], clause 6.5.2 | 1% | Formula:
EVM limit + TT | +| 6.5.4 Time alignment error | See TS 38.174 [2], clause 6.5.3.1 | 25ns | Formula:
Time alignment error limit + TT + TT | +| 6.6.2 Occupied bandwidth | See TS 38.174 [2], clause 6.6.2 | 0 Hz | Formula:
Minimum Requirement + TT | +| 6.6.3 Adjacent Channel Leakage Power Ratio (ACLR) | See TS 38.174 [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.174 [2], clause 6.6.4 | Offsets $< 10$ MHz
1.5 dB, $f \leq 3.0$ GHz
1.8 dB, $3.0$ GHz $< f \leq 6$ GHz (Note 1)

Offsets $\geq 10$ MHz
0dB | Formula:
Minimum Requirement + TT | +| 6.6.5.5.1 General transmitter spurious emissions requirements Category A | See TS 38.174 [2], clause 6.6.5.2.1 | 0dB | Formula:
Minimum Requirement + TT | +| 6.6.5.5.1 General transmitter spurious emissions requirements Category B | See TS 38.174 [2], clause 6.6.5.2.1 | 0dB | Formula:
Minimum Requirement + TT | +| 6.6.5.5.2 Additional spurious emissions requirements | See TS 38.174 [2], clause 6.6.5.2.2 | 0dB | Formula:
Minimum Requirement + TT | +| 6.6.5.5.3 Co-location with other base stations | See TS 38.174 [2], clause 6.6.5.2.3 | 0dB | Formula:
Minimum Requirement + TT | +| 6.7 Transmitter intermodulation | See TS 38.174 [2], clause 6.7 | 0dB | Formula: Ratio + TT | + +NOTE 1: TT values for $4.2$ GHz $< f \leq 6.0$ GHz apply for IAB 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.174 [2] | Test Tolerance (TT) | Test requirement in the present document | +|--------------------------------------|--------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------| +| 7.2 Reference sensitivity level | See TS 38.174 [2], clause 7.2 | Normal and extreme conditions:
0.7 dB, $f \leq 3.0$ GHz
1.0 dB, $3.0$ GHz $< f \leq 4.2$ GHz
1.2 dB, $4.2$ GHz $< f \leq 6.0$ GHz | Formula: Reference sensitivity power level + TT | +| 7.3 Dynamic range | See TS 38.174 [2], clause 7.3 | 0.3 dB | Formula: Wanted signal power + TT | +| 7.4 In-band selectivity and blocking | See TS 38.174 [2], clause 7.4 | 0dB | Formula: Wanted signal power + TT | +| 7.5 Out-of-band blocking | See TS 38.174 [2], clause 7.5 | 0dB | Formula: Wanted signal power + TT | +| 7.6 Receiver spurious emissions | See TS 38.174 [2], clause 7.6 | 0dB | Formula:
Minimum Requirement + TT | +| 7.7 Receiver intermodulation | See TS 38.174 [2], clause 7.7 | 0dB | Formula: Wanted signal power + TT | +| 7.8 In-channel selectivity | See TS 38.174 [2], clause 7.8 | 1.4 dB, $f \leq 3.0$ GHz
1.8 dB, $3.0$ GHz $< f \leq 4.2$ GHz
2.1 dB, $4.2$ GHz $< f \leq 6.0$ GHz | Formula: Wanted signal power + TT | + +NOTE: TT values are applicable for normal condition unless otherwise stated. + +## C.3 Measurement of performance requirements + +### C.3.1 List IAB-DU TTs + +Table C.3-1: Derivation of Test Requirements (Performance tests) + +| Test | Minimum Requirement in TS 38.174 [2] | Test Tolerance (TT) | Test requirement in the present document | +|----------------------------------------------------------------------|--------------------------------------|----------------------------------------------|-------------------------------------------------------------------------------------------------------------| +| 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 | +| Performance requirements for PUSCH with transform precoding enabled | SNRs as specified | 0.6 dB | Formula: SNR + TT
T-put limit unchanged | +| Performance requirements for UCI multiplexed on PUSCH | SNRs as specified | 0.6 dB | Formula: SNR + TT
BLER limit unchanged | +| Performance requirements for PUCCH format 0 | SNRs as specified | 0.6 dB | Formula: SNR + TT
False ACK limit unchanged
Correct ACK limit unchanged | +| 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 | +| 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 | +| Performance requirements for PUCCH format 3 | SNRs as specified | 0.6 dB | Formula: SNR + TT
UCI BLER limit unchanged | +| Performance requirements for PUCCH format 4 | SNRs as specified | 0.6 dB | Formula: SNR + TT
UCI BLER limit unchanged | +| 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 | +| PRACH false alarm probability and missed detection | SNRs as specified | 0.3 dB | Formula: SNR + TT
PRACH false detection limit unchanged
PRACH detection limit unchanged | + +### C.3.2 List IAB-MT TTs + +Table C.3-2: Derivation of Test Requirements (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 | [1dB] | Formula: SNR + TT
T-put limit unchanged | +| Performance requirements for PDCCH | SNRs as specified | [0.9 dB] for 1TX
[1dB] for 2TX | Formula: SNR + TT
T-put limit unchanged | +| Performance requirements for CSI reporting | SNRs as specified | No test tolerances applied | SNR limit unchanged | + +## Annex D (informative): Measurement system set-up + +### D.1 IAB type 1-H transmitter + +#### D.1.1 IAB output power, output power dynamics, transmitter ON/OFF power, frequency error, EVM, unwanted emissions for IAB type 1-H + +*TAB connectors* may be connected to the measurement equipment singularly and tested one at a time (figure D.1.1-1), or may be tested simultaneously in groups (figure D.1.1-2) where the group size may range from two to all the *TAB connectors* which are subject to particular transmitter test in this test setup. + +In all cases the measurement is per *TAB connector* but the measurement may be done in parallel. + +![Diagram of the measurement system set-up for IAB type 1-H output power, output power dynamics, transmitter ON/OFF power, frequency error, EVM, unwanted emissions for a single TAB connector.](fdd39709ead076a03c9920362efa1a00_img.jpg) + +The diagram illustrates the measurement system set-up for a single *TAB connector*. On the left, a dashed box labeled 'Transceiver unit array' contains multiple transceivers. A vertical dashed line labeled 'Transceiver array boundary' separates the unit array from the external measurement environment. To the right of this boundary, several connectors are shown, 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'. An arrow points to connector #K with the label 'Transceiver array boundary connector TAB(n)'. + +Diagram of the measurement system set-up for IAB type 1-H output power, output power dynamics, transmitter ON/OFF power, frequency error, EVM, unwanted emissions for a single TAB connector. + +**Figure D.1.1-1: Measuring system set-up for IAB type 1-H output power, output power dynamics, transmitter ON/OFF power, frequency error, EVM, unwanted emissions for a single *TAB connector*** + +![Diagram of measuring system set-up for IAB type 1-H output power, output power dynamics, transmitter ON/OFF power, frequency error, EVM, unwanted emissions for multiple TAB connectors.](3054e46608784063609e8c7a253fcd24_img.jpg) + +The diagram shows a 'transceiver unit array' (dashed box) on the left. A vertical dashed line labeled 'transceiver array boundary' separates it from the 'Measurement Equipment' (solid box) on the right. Multiple horizontal lines connect the array to the equipment, labeled #1, #2, ..., #K. 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)'. + +Diagram of measuring system set-up for IAB type 1-H output power, output power dynamics, transmitter ON/OFF power, frequency error, EVM, unwanted emissions for multiple TAB connectors. + +**Figure D.1.1-2: Measuring system set-up for IAB type 1-H output power, output power dynamics, transmitter ON/OFF power, frequency error, EVM, unwanted emissions for multiple TAB connectors** + +### D.1.2 Transmitter intermodulation for IAB type 1-H + +![Diagram of measuring system set-up for IAB type 1-H transmitter intermodulation.](3e0674a68142b10eac3384d2acd6c136_img.jpg) + +The diagram shows a 'Transceiver Array Boundary (TAB)' (dashed box) on the left. Inside, multiple horizontal lines represent TAB connectors, labeled #1, ..., #n, ..., #NTABC. Connectors #1 and #NTABC are connected to 'Load' blocks. Connector #n is labeled 'TAB connector under test'. From connector #n, a 'Wanted signal' arrow points right to a circulator (circular symbol with a clockwise arrow). An 'Interferring signal' arrow points from a 'Test signal' block (via an 'Att' (attenuator) block) into the same circulator. The circulator's output points to a 'Spectrum analyser' block. + +Diagram of measuring system set-up for IAB type 1-H transmitter intermodulation. + +**Figure D.1.2-1: Measuring system set-up for IAB type 1-H transmitter intermodulation** + +![Diagram of measuring system set-up for IAB type 1-H transmitter intermodulation for IAB simultaneous operation. It shows a Transceiver Array Boundary (TAB) with multiple connectors (#1, #n, #m, #NTABC). Connectors #1 and #NTABC are terminated with 'Load'. Connector #n is connected to a circulator that outputs a 'Wanted signal' to a 'Spectrum analyser' and receives an 'Interferring signal' from a 'Test signal' source via an 'Att' (attenuator). Connector #m is connected to another circulator that outputs a 'Wanted signal' to a 'Spectrum analyser' and receives an 'Interferring signal' from a 'Test signal' source via an 'Att' (attenuator). The 'TAB connector under test' is indicated between connectors #n and #m.](e27f0c293be4088211306b9fc673178b_img.jpg) + +Diagram of measuring system set-up for IAB type 1-H transmitter intermodulation for IAB simultaneous operation. It shows a Transceiver Array Boundary (TAB) with multiple connectors (#1, #n, #m, #NTABC). Connectors #1 and #NTABC are terminated with 'Load'. Connector #n is connected to a circulator that outputs a 'Wanted signal' to a 'Spectrum analyser' and receives an 'Interferring signal' from a 'Test signal' source via an 'Att' (attenuator). Connector #m is connected to another circulator that outputs a 'Wanted signal' to a 'Spectrum analyser' and receives an 'Interferring signal' from a 'Test signal' source via an 'Att' (attenuator). The 'TAB connector under test' is indicated between connectors #n and #m. + +Figure D.1.2-2: Measuring system set-up for IAB type 1-H transmitter intermodulation for IAB simultaneous operation + +### D.1.3 Transmitter spurious emissions for IAB type 1-H + +*TAB connectors* may be connected to the measurement equipment singularly and tested one at a time (figure D.1.3-1), or may be tested simultaneously in groups (figure D.1.3-2) where the group size may range from two to all the *TAB connectors* which are subject to transmitter spurious emissions test. + +In all cases the measurement is per *TAB connector* but the measurement may be done in parallel. + +![Diagram of measuring system set-up for transmitter spurious emissions for a single TAB connector. It shows a Transceiver unit array with multiple connectors (#1, #2, #K) at the Transceiver array boundary. Connector #1 is connected to a 'TX notch' which is then connected to 'Measurement equipment'. Connectors #2 and #K are terminated with 'Load'. The diagram is labeled 'Transceiver array boundary' at the top and 'Transceiver unit array' at the bottom. An arrow points to connector #K with the label 'Transceiver array boundary connector TAB(n)'.](6bd66a9f24bf7442862b8f3ab580297e_img.jpg) + +Diagram of measuring system set-up for transmitter spurious emissions for a single TAB connector. It shows a Transceiver unit array with multiple connectors (#1, #2, #K) at the Transceiver array boundary. Connector #1 is connected to a 'TX notch' which is then connected to 'Measurement equipment'. Connectors #2 and #K are terminated with 'Load'. The diagram is labeled 'Transceiver array boundary' at the top and 'Transceiver unit array' at the bottom. An arrow points to connector #K with the label 'Transceiver array boundary connector TAB(n)'. + +Figure D.1.3-1: Measuring system set-up for transmitter spurious emissions for a single *TAB connector* + +![Diagram of measuring system set-up for transmitter spurious emissions for multiple TAB connectors in parallel test.](351243fd59cdae993f191da9ebb48016_img.jpg) + +This diagram illustrates the measuring system set-up for transmitter spurious emissions. On the left, a dashed box labeled 'Transceiver unit array' contains multiple connectors labeled #1, #2, ..., #K. A vertical dashed line labeled 'Transceiver array boundary' passes through these connectors. An arrow labeled 'Transceiver array boundary connector TAB(n)' points to connector #K. Each connector is connected to a block labeled 'TX notch', which in turn connects to a large block labeled 'Measurement equipment'. + +Diagram of measuring system set-up for transmitter spurious emissions for multiple TAB connectors in parallel test. + +Figure D.1.3-2: Measuring system set-up for transmitter spurious emissions for multiple *TAB connectors* in parallel test + +### D.1.4 Time alignment error for *IAB-DU* + +![Diagram of measuring system set-up for IAB-DU test of time alignment error.](a0bf1e4e2765bf05e8009f39007df772_img.jpg) + +This diagram illustrates the measuring system set-up for IAB-DU test of time alignment error. On the left, a dashed box labeled 'Transceiver unit array' contains multiple connectors labeled #1, #2, #3, ..., #K. A vertical dashed line labeled 'Transceiver array boundary' passes through these connectors. An arrow labeled 'Transceiver array boundary connector TAB(n)' points to connector #K. Connectors #1 and #2 are connected to a block labeled 'Measurement equipment: Timing difference measurement'. Connectors #3 and #K are connected to blocks labeled 'Load'. + +Diagram of measuring system set-up for IAB-DU test of time alignment error. + +Figure D.1.4-1: Measuring system set-up for *IAB-DU* test of time alignment error + +## D.2 IAB type 1-H receiver + +### D.2.1 Reference sensitivity level for IAB type 1-H + +![Diagram of measuring system set-up for IAB type 1-H reference sensitivity level test. It shows a transceiver unit array connected to a transceiver array boundary via connectors #1, #2, and #K. Connector #1 is connected to a signal generator for the wanted signal. Connectors #2 and #K are connected to loads. The boundary is labeled 'transceiver array boundary' and the connectors are labeled 'Transceiver array boundary connector TAB(n)'.](49035d3c3a8a3e4936b78ae634359aab_img.jpg) + +The diagram illustrates the test setup for reference sensitivity. On the left, a dashed box represents the 'transceiver unit array'. A vertical dashed line marks the 'transceiver array boundary'. At this boundary, there are multiple connectors labeled #1, #2, ..., #K. Connector #1 is connected to a 'Signal generator for the wanted signal'. 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)'. + +Diagram of measuring system set-up for IAB type 1-H reference sensitivity level test. It shows a transceiver unit array connected to a transceiver array boundary via connectors #1, #2, and #K. Connector #1 is connected to a signal generator for the wanted signal. Connectors #2 and #K are connected to loads. The boundary is labeled 'transceiver array boundary' and the connectors are labeled 'Transceiver array boundary connector TAB(n)'. + +Figure D.2.1-1: Measuring system set-up for IAB type 1-H reference sensitivity level test + +### D.2.2 Receiver dynamic range for IAB type 1-H + +![Diagram of measuring system set-up for IAB type 1-H dynamic range test. It shows a transceiver unit array connected to a transceiver array boundary via connectors #1, #2, and #K. Connector #1 is connected to a Hybrid, which is then connected to two signal generators: one for the wanted signal and one for the AWGN interfering signal. Connectors #2 and #K are connected to loads. The boundary is labeled 'transceiver array boundary' and the connectors are labeled 'Transceiver array boundary connector TAB(n)'.](b4022f9f3b9a3b30ade5c100052cb16a_img.jpg) + +This diagram shows the setup for a dynamic range test. Similar to the previous diagram, a 'transceiver unit array' is on the left, separated by a 'transceiver array boundary' (dashed line) with connectors #1, #2, ..., #K. Connector #1 connects to a 'Hybrid' block. The Hybrid has two outputs: one connected to a 'Signal generator for the wanted signal' and another to a 'Signal generator for the AWGN interfering signal'. 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)'. + +Diagram of measuring system set-up for IAB type 1-H dynamic range test. It shows a transceiver unit array connected to a transceiver array boundary via connectors #1, #2, and #K. Connector #1 is connected to a Hybrid, which is then connected to two signal generators: one for the wanted signal and one for the AWGN interfering signal. Connectors #2 and #K are connected to loads. The boundary is labeled 'transceiver array boundary' and the connectors are labeled 'Transceiver array boundary connector TAB(n)'. + +Figure D.2.2-1: Measuring system set-up for IAB type 1-H dynamic range test + +## D.2.3 Receiver adjacent channel selectivity and narrowband blocking for IAB type 1-H + +![Figure D.2.3-1: Measuring system set-up for IAB type 1-H adjacent channel selectivity and narrowband blocking test. The diagram shows a 'transceiver unit array' (dashed box) connected to a 'transceiver array boundary' (dashed vertical line). At the 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 connected to a 'Load' block. The 'Hybrid' block is connected to two 'ATT' (Attenuator) blocks, labeled ATT1 and ATT2. ATT1 is connected to a 'Signal generator for the wanted signal'. ATT2 is connected to a 'Signal generator for the interfering signal'. An arrow points to the boundary line with the label 'Transceiver array boundary connector TAB(n)'.](91d148dff4c40942811f006b6e8f8168_img.jpg) + +Figure D.2.3-1: Measuring system set-up for IAB type 1-H adjacent channel selectivity and narrowband blocking test. The diagram shows a 'transceiver unit array' (dashed box) connected to a 'transceiver array boundary' (dashed vertical line). At the 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 connected to a 'Load' block. The 'Hybrid' block is connected to two 'ATT' (Attenuator) blocks, labeled ATT1 and ATT2. ATT1 is connected to a 'Signal generator for the wanted signal'. ATT2 is connected to a 'Signal generator for the interfering signal'. An arrow points to the boundary line with the label 'Transceiver array boundary connector TAB(n)'. + +**Figure D.2.3-1: Measuring system set-up for IAB type 1-H adjacent channel selectivity and narrowband blocking test** + +![Figure D.2.3-2: Measuring system set-up for IAB type 1-H adjacent channel selectivity and narrowband blocking test. This diagram is similar to Figure D.2.3-1 but shows a different configuration. At the 'transceiver array boundary', connector #1 is connected to a 'Hybrid' block, which is then connected to ATT1 (wanted signal) and ATT2 (interfering signal). Connector #2 is connected to another 'Hybrid' block, which is connected to ATT1 (wanted signal) and ATT2 (interfering signal). Connector #K is connected to a 'Load' block. The 'transceiver unit array' (dashed box) is on the left. An arrow points to the boundary line with the label 'Transceiver array boundary connector TAB(n)'.](768662ed52466041c8f43e005b48f501_img.jpg) + +Figure D.2.3-2: Measuring system set-up for IAB type 1-H adjacent channel selectivity and narrowband blocking test. This diagram is similar to Figure D.2.3-1 but shows a different configuration. At the 'transceiver array boundary', connector #1 is connected to a 'Hybrid' block, which is then connected to ATT1 (wanted signal) and ATT2 (interfering signal). Connector #2 is connected to another 'Hybrid' block, which is connected to ATT1 (wanted signal) and ATT2 (interfering signal). Connector #K is connected to a 'Load' block. The 'transceiver unit array' (dashed box) is on the left. An arrow points to the boundary line with the label 'Transceiver array boundary connector TAB(n)'. + +**Figure D.2.3-2: Measuring system set-up for IAB type 1-H adjacent channel selectivity and narrowband blocking test** + +## D.2.4 Receiver spurious emissions + +*TAB connector(s)* may be connected to the measurement equipment singularly and tested one at a time (figure D.2.2-1), or may be tested simultaneously in groups (figure D.2.2-2) where the group size may range from 2 to all the *TAB connectors*. + +In all cases the measurement is per *TAB connector* but the measurement may be done in parallel. + +![Diagram of measuring system set-up for IAB type 1-H receiver spurious emissions for a single TAB connector.](3d6d0738981fdd03d003cc653bdfdaae_img.jpg) + +This diagram illustrates the measuring system set-up for IAB type 1-H receiver spurious emissions for a single TAB connector. On the left, a dashed box labeled 'transceiver unit array' contains multiple transceiver units. A vertical dashed line labeled 'transceiver array boundary' separates this array from the external measurement equipment. At this boundary, there are several connectors labeled #1, #2, ..., #K. Connector #1 is connected to a block labeled 'TX notch', which is then connected to a 'Measurement receiver'. Connectors #2 and #K are each connected to a block labeled 'Load'. An arrow points to the boundary line with the label 'Transceiver array boundary connector TAB(n)'. + +Diagram of measuring system set-up for IAB type 1-H receiver spurious emissions for a single TAB connector. + +**Figure D.2.4-1: Measuring system set-up for IAB type 1-H receiver spurious emissions for a single TAB connector** + +![Diagram of measuring system set-up for IAB type 1-H receiver spurious emissions for multiple TAB connectors.](e86d625d503436075806fd06df985443_img.jpg) + +This diagram illustrates the measuring system set-up for IAB type 1-H receiver spurious emissions for multiple TAB connectors. Similar to the previous diagram, a dashed box on the left represents the 'transceiver unit array', separated by a 'transceiver array boundary' (vertical dashed line). At this boundary, connectors #1, #2, ..., #K are shown. Each connector is connected to a block labeled 'TX'. All 'TX' blocks are connected to a single, larger 'Measurement receiver(s)' block on the right. An arrow points to the boundary line with the label 'Transceiver array boundary connector TAB(n)'. + +Diagram of measuring system set-up for IAB type 1-H receiver spurious emissions for multiple TAB connectors. + +**Figure D.2.4-2: Measuring system set-up for IAB type 1-H receiver spurious emissions for multiple TAB connectors** + +## D.2.5 Receiver In-channel selectivity for IAB type 1-H + +![Diagram of measuring system set-up for IAB type 1-H in-channel selectivity test. It shows a transceiver unit array connected to a transceiver array boundary. At the boundary, port #1 is connected to a Hybrid, port #2 to a Load, and port #K to a Load. The Hybrid is connected to a signal generator for the wanted signal and interfering signal.](89a9571da272e76616860592f8960874_img.jpg) + +The diagram illustrates the test setup for in-channel selectivity. On the left, a dashed box labeled 'transceiver unit array' contains multiple ports. A vertical dashed line labeled 'transceiver array boundary' separates the unit array from the external test equipment. Port #1 is connected to a 'Hybrid' component. Port #2 and port #K are connected to 'Load' components. The 'Hybrid' component is connected to a 'Signal generator for the wanted signal and interfering signal'. + +Diagram of measuring system set-up for IAB type 1-H in-channel selectivity test. It shows a transceiver unit array connected to a transceiver array boundary. At the boundary, port #1 is connected to a Hybrid, port #2 to a Load, and port #K to a Load. The Hybrid is connected to a signal generator for the wanted signal and interfering signal. + +Figure D.2.5-1: Measuring system set-up for IAB type 1-H in-channel selectivity test + +## D.2.6 Receiver intermodulation for IAB type 1-H + +![Diagram of measuring system set-up for IAB type 1-H receiver intermodulation test. It shows a transceiver unit array connected to a transceiver array boundary. At the boundary, port #1 is connected to a Hybrid, port #2 to a Load, and port #K to a Load. The Hybrid is connected to ATT1 (wanted signal), and another Hybrid is connected to ATT2 (CW interfering signal) and ATT3 (NR interfering signal).](5766537cfe2f332b335d51cd00e40b46_img.jpg) + +The diagram illustrates the test setup for receiver intermodulation. On the left, a dashed box labeled 'transceiver unit array' contains multiple ports. A vertical dashed line labeled 'transceiver array boundary' separates the unit array from the external test equipment. Port #1 is connected to a 'Hybrid' component. Port #2 and port #K are connected to 'Load' components. The 'Hybrid' component is connected to 'ATT1' (Signal generator for the wanted signal). Another 'Hybrid' component is connected to 'ATT2' (Signal generator for the CW interfering signal) and 'ATT3' (Signal generator for the NR interfering signal). The second 'Hybrid' component is also connected to the first 'Hybrid' component. A label 'Transceiver array boundary connector TAB(n)' points to the boundary line. + +Diagram of measuring system set-up for IAB type 1-H receiver intermodulation test. It shows a transceiver unit array connected to a transceiver array boundary. At the boundary, port #1 is connected to a Hybrid, port #2 to a Load, and port #K to a Load. The Hybrid is connected to ATT1 (wanted signal), and another Hybrid is connected to ATT2 (CW interfering signal) and ATT3 (NR interfering signal). + +Figure D.2.6-1: Measuring system set-up for IAB type 1-H receiver intermodulation test + +![Figure D.2.6-2: Measuring system set-up for IAB type 1-H receiver intermodulation test for IAB Simultaneous Operation. The diagram shows a 'transceiver unit array' on the left, enclosed in a dashed box. A vertical dashed line labeled 'transceiver array boundary' separates it from the test equipment. At this boundary, there are 'Transceiver array boundary connector TAB(n)' points. Port #1 connects to a 'Hybrid' block, which is then connected to 'ATT1' and a 'Signal generator for the wanted signal'. Port #2 connects to a 'Load' block. There are vertical ellipsis dots between port #2 and port K-1. Port K-1 connects to a 'Load' block. Port K connects to a 'Hybrid' block. This 'Hybrid' block is connected to 'ATTn' and a 'Signal generator for the wanted signal', and also to another 'Hybrid' block. This second 'Hybrid' block is connected to 'ATTn+1' and a 'Signal generator for the CW interfering signal', and also to a third 'Hybrid' block. The third 'Hybrid' block is connected to 'ATTn+2' and a 'Signal generator for the NR interfering signal'.](c24f22afc8106a8f9b76c759a1db6891_img.jpg) + +Figure D.2.6-2: Measuring system set-up for IAB type 1-H receiver intermodulation test for IAB Simultaneous Operation. The diagram shows a 'transceiver unit array' on the left, enclosed in a dashed box. A vertical dashed line labeled 'transceiver array boundary' separates it from the test equipment. At this boundary, there are 'Transceiver array boundary connector TAB(n)' points. Port #1 connects to a 'Hybrid' block, which is then connected to 'ATT1' and a 'Signal generator for the wanted signal'. Port #2 connects to a 'Load' block. There are vertical ellipsis dots between port #2 and port K-1. Port K-1 connects to a 'Load' block. Port K connects to a 'Hybrid' block. This 'Hybrid' block is connected to 'ATTn' and a 'Signal generator for the wanted signal', and also to another 'Hybrid' block. This second 'Hybrid' block is connected to 'ATTn+1' and a 'Signal generator for the CW interfering signal', and also to a third 'Hybrid' block. The third 'Hybrid' block is connected to 'ATTn+2' and a 'Signal generator for the NR interfering signal'. + +**Figure D.2.6-2: Measuring system set-up for IAB type 1-H receiver intermodulation test for IAB Simultaneous Operation** + +### D.3 IAB type 1-H performance requirements + +#### D.3.1 Performance requirements for PUSCH and PUCCH on single antenna port in multipath fading conditions + +![Figure D.3.1-1: Functional set-up for performance requirements for PUSCH and PUCCH for IAB with Rx diversity (2 Rx case shown). The diagram shows a 'transceiver unit array' on the left, enclosed in a dashed box. A vertical dashed line labeled 'transceiver array boundary' separates it from the test equipment. At this boundary, there are 'Transceiver array boundary connector TAB(n)' points. Port #1 connects to a directional coupler (triangle symbol). The output of this coupler goes to a 'Channel Simulator' and an 'AWGN Generator'. Port #2 connects to another directional coupler. The output of this coupler goes to another 'Channel Simulator' and another 'AWGN Generator'. There are vertical ellipsis dots between port #2 and port #K. Port #K connects to a 'Load' block. The outputs of the 'Channel Simulators' and 'AWGN Generators' are combined at a second directional coupler, which then connects to an 'IAB tester'. A line labeled 'HARQ feedback (only for PUSCH)' goes from the 'IAB tester' back to the 'transceiver unit array'.](3334c914bdd313ced24f692366028a6d_img.jpg) + +Figure D.3.1-1: Functional set-up for performance requirements for PUSCH and PUCCH for IAB with Rx diversity (2 Rx case shown). The diagram shows a 'transceiver unit array' on the left, enclosed in a dashed box. A vertical dashed line labeled 'transceiver array boundary' separates it from the test equipment. At this boundary, there are 'Transceiver array boundary connector TAB(n)' points. Port #1 connects to a directional coupler (triangle symbol). The output of this coupler goes to a 'Channel Simulator' and an 'AWGN Generator'. Port #2 connects to another directional coupler. The output of this coupler goes to another 'Channel Simulator' and another 'AWGN Generator'. There are vertical ellipsis dots between port #2 and port #K. Port #K connects to a 'Load' block. The outputs of the 'Channel Simulators' and 'AWGN Generators' are combined at a second directional coupler, which then connects to an 'IAB tester'. A line labeled 'HARQ feedback (only for PUSCH)' goes from the 'IAB tester' back to the 'transceiver unit array'. + +**Figure D.3.1-1: Functional set-up for performance requirements for PUSCH and PUCCH for IAB with Rx diversity (2 Rx case shown)** + +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. + +### D.3.2 Performance requirements for PUSCH, PDSCH, PDCCH transmission and PMI/RI reporting on two antenna ports in multipath fading conditions + +![Functional set-up for performance requirements for PUSCH, PDSCH and PDCCH transmission on two antenna ports in multipath fading conditions (2 Rx case shown).](41bc9383c0d6e910a69e23d465ae5607_img.jpg) + +The diagram illustrates the functional set-up for performance requirements. On the left, a dashed box labeled 'transceiver unit array' contains multiple ports labeled #1, #2, ..., #K. A vertical dashed line labeled 'transceiver array boundary' separates this array from the external test equipment. At each port (#1, #2, ..., #K), a signal path goes through a circulator. Port #1 connects to a 'Channel Simulator', which then connects to an 'IAB tester' via 'Tx 1'. Port #2 connects to another 'Channel Simulator', which connects to the 'IAB tester' via 'Tx 2'. Port #K connects to a 'Load'. Below the channel simulators, there are two 'AWGN Generator' blocks. A 'feedback' line connects the 'IAB tester' back to the 'transceiver unit array'. At the bottom, a dashed box labeled 'Synchronization source (if used see NOTE 2)' provides a synchronization signal to the 'IAB tester' and the 'AWGN Generators'. + +Functional set-up for performance requirements for PUSCH, PDSCH and PDCCH transmission on two antenna ports in multipath fading conditions (2 Rx case shown). + +**Figure D.3.2-1: Functional set-up for performance requirements for PUSCH, PDSCH and PDCCH transmission on two antenna ports in multipath fading conditions (2 Rx case shown)** + +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. + +### D.3.3 Performance requirements for PUSCH, PRACH transmission and CQI reporting in static conditions + +![Functional set-up for performance requirements for PUSCH and PRACH in static conditions for IAB-DU with Rx diversity (2 Rx case shown).](c139aa372176ff96d02d462be232c810_img.jpg) + +The diagram illustrates the functional set-up for performance requirements. On the left, a dashed box labeled 'transceiver unit array' contains multiple transceiver units. A vertical dashed line labeled 'transceiver array boundary' separates this array from the external test equipment. At this boundary, there are connectors labeled #1, #2, ..., #K. Connector #1 is connected to a directional coupler, which is then connected to an 'AWGN Generator'. Connector #2 is also connected to a directional coupler, which is connected to another 'AWGN Generator'. Connector #K is connected to a 'Load'. Below the boundary, an arrow points to one of the connectors, labeled 'Transceiver array boundary connector TAB(n)'. To the right of the boundary, the outputs of the directional couplers are combined and connected to an 'IAB tester'. At the bottom, a dashed box labeled 'Synchronization source (if used see NOTE 1)' is connected to both the 'IAB tester' and the 'transceiver unit array' via dashed lines. + +Functional set-up for performance requirements for PUSCH and PRACH in static conditions for IAB-DU with Rx diversity (2 Rx case shown). + +**Figure D.3.3-1: Functional set-up for performance requirements for PUSCH and PRACH in static conditions for IAB-DU with Rx diversity (2 Rx case shown)** + +NOTE 1: 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 2: It is left up to implementation how L1/L2 is configured for testing. + +--- + +## Annex E (normative): Characteristics of interfering signals + +### E.1 Characteristics of the interfering signals for IAB-DU + +The Annex D in TS 38.104 [11] apply to FR1 IAB-DU. + +--- + +### E.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 TS38.211 [9]. 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 F (normative): Propagation conditions + +### F.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. + +#### F.1.1 IAB-MT receiver with 2RX + +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}$$ + +### F.2 Multi-path fading propagation conditions + +#### F.2.1 General + +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-1 (24.25 GHz – 52.6 GHz). + +## F.2.2 Delay profiles + +### F.2.2.1 General + +The delay profiles are simplified from the TR 38.901 [25] 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 F.2.2.1 can be used as such. + +- Step 1: Use the original TDL model from TR 38.901 [25]. +- 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 [25]. +- 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 F.2.2.2-2, F.2.2.2-3, and F.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. + +## F.2.2.2 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 F.2.2.2-1 and the tapped delay line models are specified in tables F.2.2.2-2 ~ table F.2.2.2-4. + +**Table F.2.2.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 | +| TDLB100 | 12 | 100 ns | 480 ns | 5 ns | +| TDLC300 | 12 | 300 ns | 2595 ns | 5 ns | + +**Table F.2.2.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 | | + +**Table F.2.2.2-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 F.2.2.2-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 | | + +## F.2.3 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 F.2.3-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 F.2.3-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 | + +## F.2.4 MIMO channel correlation matrices + +### F.2.4.1 General + +The MIMO channel correlation matrices defined in annex F.2.4 apply for the antenna configuration using uniform linear arrays at both IAB and UE and for the antenna configuration using cross polarized antennas. + +### F.2.4.2 MIMO correlation matrices using Uniform Linear Array + +#### F.2.4.2.1 General + +The MIMO channel correlation matrices defined in annex F.2.4.2 apply for the antenna configuration using uniform linear array (ULA) at both IAB and UE. + +#### F.2.4.2.2 Definition of MIMO correlation matrices + +Table F.2.4.2.2-1 defines the correlation matrix for the IAB. + +**Table F.2.4.2.2-1: IAB-DU or gNB correlation matrix** + +| IAB-DU or 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}$ | + +NOTE: The matrix applies to the IAB-DU for IAB-DU requirements and gNB for IAB-MT requirements. + +Table F.2.4.2.2-2 defines the correlation matrix for the UE: + +**Table F.2.4.2.2-2: IAB-MT or UE correlation matrix** + +| | One antenna | Two antennas | Four antennas | +|-------------------------|--------------------|-------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IAB-MT / 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}$ | + +NOTE: The matrix applies to the UE for IAB-DU requirements and IAB-MT for IAB-MT requirements. + +Table F.2.4.2.2-3 defines the channel spatial correlation matrix $R_{spat}$ . The parameters, $\alpha$ and $\beta$ in table F.2.4.2.2-3 defines the spatial correlation between the antennas at the IAB and UE respectively. + +**Table F.2.4.2.2-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{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}$ | +| 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{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}$ | + +NOTE 1: $R_{gNB}$ refers to an IAB-DU for IAB-DU requirements or a gNB for IAB-MT requirements. +NOTE 2: $R_{UE}$ refers to an UE for IAB-DU requirements or and IAB-MT for IAB-MT requirements + +For cases with more antennas at either IAB or gNB/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}$ . + +### F.2.4.2.3 MIMO correlation matrices at high, medium and low level + +The $\alpha$ and $\beta$ for different correlation types are given in table F.2.4.2.3-1. + +**Table F.2.4.2.3-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 F.2.4.2.3-2, F.2.4.2.3-3 and F.2.4.2.3-4 as below. + +The values in table F.2.4.2.3-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 F.2.4.2.3-3 to insure the correlation matrix is positive semi-definite after round-off to 4 digit precision with $a = 0.00012$ . + +**Table F.2.4.2.3-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.8894 & 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 F.2.4.2.3-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.9884 \\ 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 F.2.4.2.3-4: MIMO correlation matrices for low correlation** + +| | | +|----------|--| +| 1x2 case | | +| 1x4 case | | +| 1x8 case | | +| 2x2 case | | +| 2x4 case | | +| 2x4 case | | +| 4x4 case | | + +In table F.2.4.12.3-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. + +## F.2.4.3 Multi-antenna channel models using cross polarized antennas + +### F.2.4.3.1 General + +The MIMO channel correlation matrices defined in annex F.2.4.3 apply to two cases as presented below: + +- One TX antenna and multiple RX antennas case, with cross polarized antennas used at IAB +- Multiple TX antennas and multiple RX antennas case, with cross polarized antennas used at both UE and IAB + +The cross-polarized antenna elements with +/-45 degrees polarization slant angles are deployed at IAB. 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. + +### F.2.4.3.2 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 (IAB-DU requirements) or IAB-MT (IAB-MT requirements) with same polarization, +- $R_{gNB}$ is the spatial correlation matrix at the IAB-DU (IAB-DU requirements) or gNB (IAB-MT requirements) with same polarization, +- $\Gamma_{UL}$ is a polarization correlation matrix, +- $P_{UL}$ is a permutation matrix, and +- $(\bullet)^T$ denotes transpose. + +Table F.2.4.3.2-1 defines the polarization correlation matrix. + +**Table F.2.4.3.2-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 + +$$\mathbf{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 F.2.4.3. + +### F.2.4.3.3 Spatial correlation matrices at UE/IAB-MT and IAB-DU/gNB sides + +#### F.2.4.3.3.1 Spatial correlation matrices at IAB-MT/UE side + +In this subclause, $R_{UE}$ refers to a UE for IAB-DU requirements or an IAB-MT for IAB-MT requirements. + +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, + +#### F.2.4.3.3.2 Spatial correlation matrices at IAB-DU/gNB side + +In this subclause, $R_{gNB}$ refers to an IAB-DU for IAB-DU requirements or a gNB for IAB-MT requirements. + +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/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}$$ + +For 8-antenna receiver using four pairs of cross-polarized antenna elements, + +#### F.2.4.3.4 MIMO correlation matrices using cross polarized antennas + +The values for parameters $\alpha$ , $\beta$ and $\gamma$ for low spatial correlation are given in table F.2.4.3.4-1. + +**Table F.2.4.3.4-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 F.2.4.3.4-2 as below. + +**Table F.2.4.3.4-2: MIMO correlation matrices for low spatial correlation** + +| | | +|----------|-----------------------------| +| 1x8 case | $R_{low} = \mathbf{I}_8$ | +| 2x8 case | $R_{low} = \mathbf{I}_{16}$ | + +In table F.2.4.3.4-2, $\mathbf{I}_d$ is a $d \times d$ identity matrix. + +### F.2.4.3.5 Beam steering approach + +For the 2D cross-polarized antenna array at gNB, given the channel spatial correlation matrix in F.2.4.3.2, F.2.4.3.3 and F.2.4.3.4, 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_1$ is the number of antenna elements in first dimension with same polarization, +- $N_2$ 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 $n$ stands for first dimension and second dimension respectively. + +- $\phi_{n,k}$ controls the phase variation in first dimension and second dimension respectively, and the phase for k-th subframe is denoted by $\phi_{n,k}$ , where $\phi_{n,0}$ is the random start value with the uniform distribution, i.e., $\phi_{n,0} \sim U[0, 2\pi)$ , $\Delta\phi$ is the step of phase variation, which is defined in Table F.2.4.3.5-1, and k is the linear increment of $2^u$ for every slot throughout the simulation, the index $n$ stands for first dimension and second dimension respectively. +- $\mathbf{W}$ is the precoding matrix for $N_t$ transmission antennas, +- $\mathbf{y}$ is the received signal, $\mathbf{x}$ is the transmitted signal, and $\mathbf{n}$ is AWGN. +- $\Delta f$ corresponds to subcarrier spacing configuration, + +For the 1D cross-polarized antenna array at gNB, the corresponding random channel matrix $\mathbf{H}$ can be calculated by letting $N_2=1$ , i.e., + +**Table F.2.4.3.5-1: The step of phase variation** + +| Variation Step | Value (rad/ms) | +|----------------|-------------------------| +| | $1.2566 \times 10^{-3}$ | + +--- + +## Annex G (normative): In-channel TX tests for IAB-DU + +The Annex H in TS 38.141-1 [13] applies to FR1 IAB-DU. + +--- + +## Annex H (normative): In-channel TX tests for IAB-MT + +### H.0 Applicability + +FR1 IAB-MT EVM can be determined by the process according to following alternatives: + +Alternative 1: Annex E in TS 38.521-1 [16]. Only CP-OFDM waveform of PUSCH is measured for IAB-MT or + +Alternative 2: from Annex H.1 to Annex H.7. + +--- + +### 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 TDD 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 $s_{ideal}$ 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 IAB-MT TX to Remove CP, then to FFT, then to Per-subcarrier Amplitude/phase correction, and finally to 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' block is connected to the Per-subcarrier Amplitude/phase correction block.](cdb980c2fe504f3132b907d4de707c7f_img.jpg) + +``` + +graph LR + TX[IAB-MT TX] --> CP[Remove CP] + CP --> FFT[FFT] + FFT --> APC[Per-subcarrier Amplitude/phase correction] + APC --> SD[Symbol detection/decoding] + Sync[Pre-/post FFT time / frequency synchronization] -.-> CP + Sync -.-> FFT + Sync -.-> APC + Ref[Reference point for EVM measurement] -.-> APC + +``` + +Figure H.2.4-1: Reference point for FR1 EVM measurements. The diagram shows a signal flow from IAB-MT TX to Remove CP, then to FFT, then to Per-subcarrier Amplitude/phase correction, and finally to 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' block is connected 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 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 . + +## H.4 Timing of the FFT window + +The FFT window length is *FFT size* samples per OFDM symbol. + +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 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 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 $t_{ideal}$ and $t_{measured}$ : + +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_{ideal}$ , 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_{ideal}$ is a Dirac peak and that the correlation between the ideal signal $t_{ideal}$ 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 $t_{center}$ is determined according to the cyclic prefix length of the OFDM symbols. For normal CP, there are two values for $t_{center}$ in a 1 ms period: + +- $t_{center} = \text{length of cyclic prefix} / 2$ , +- $t_{center} = \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_{center} = 144$ within the CP of length 288 for OFDM symbols 1 to 13 of a slot, +- $t_{center} = 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 $t_{measured}$ with the FFT window timing $t_{center}$ . The result is called $P_{RE}$ . 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 PUSCH and not containing PUCCH, SRS or PRACH within a slot. + +From the acquired samples, values for each OSTP can be obtained and averaged where for TDD, $N_{slot}$ is the number of slots with uplink 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_{slot} = 1$ . + +## H.6 Post-FFT equalisation + +Perform FFTs on $y$ , one for each OFDM symbol within 10 ms measurement interval with the FFT window timing to produce an array of samples, $y_t$ in the time axis $t$ by *FFT size* in the frequency axis $f$ . + +For the example in the annex, 280 FFTs are performed on $y$ . The result is an array of samples, 280 in the time axis by 4096 in the frequency axis. + +The equalizer coefficients $\hat{h}$ and $\hat{\phi}$ 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 $\phi$ 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 $y$ for each demodulation reference signal subcarrier $f$ . + +3. The equalizer coefficients for amplitude and phase $\hat{h}$ and $\hat{\phi}$ 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}$ and $\hat{\phi}$ to compute coefficients, $\hat{h}_f$ and $\hat{\phi}_f$ , for each subcarrier. + +![Figure H.6-1: Reference subcarrier smoothing in the frequency domain. The figure consists of two parts, A and B, illustrating moving averaging of reference subcarriers. Part A shows the process at the channel edge, where the window size increases from 1 to 19 and then decreases back to 1. Part B shows the process for a smaller number of available reference subcarriers (5) within a set of contiguously allocated RBs.](51b71ddd044e4e2f9db8fb8dc08a560b_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 parts, A and B, illustrating moving averaging of reference subcarriers. Part A shows the process at the channel edge, where the window size increases from 1 to 19 and then decreases back to 1. Part B shows the process for a smaller number of available reference subcarriers (5) within a set of contiguously allocated RBs. + +Figure H.6-1: Reference subcarrier smoothing in the frequency domain + +## H.7 EVM + +### H.7.0 General + +For EVM create two sets of , according to the timing and , using the equalizer coefficients from H.6. + +The equivalent ideal samples are calculated from (annex H.2.2) and are called . + +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, +- $\mathcal{S}$ is the set of subcarriers within the resource blocks with the considered modulation scheme being active in symbol $t$ , +- $\tilde{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 (TDD) + +EVM is averaged over all allocated uplink resource blocks with the considered modulation scheme in the frequency domain, and a minimum of $N_{\text{slots}}$ slots where $N_{\text{slots}}$ is the number of slots in a 10 ms measurement interval. + +For TDD, let $N_{\text{slots}}$ be the number of slots with uplink symbols within a 10 ms measurement interval, the averaging in the time domain can be calculated from $N_{\text{slots}}$ slots of different 10 ms measurement intervals and should have a minimum of $N_{\text{slots}}$ slots averaging length where $N_{\text{slots}}$ is the number of slots in a 10 ms measurement interval. + +- $\text{EVM}_{\text{avg}}$ 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_{\text{RB}}$ is the number of resource blocks with the considered modulation scheme in slot $i$ . + - The $\text{EVM}_{i,j}$ is calculated, using the maximum of $\text{EVM}_{i,j}$ at the window $W$ extremities. Thus $\text{EVM}_{i,j}$ is calculated using $\text{EVM}_{i,j,l}$ and $\text{EVM}_{i,j,h}$ (l and h, low and high; where low is the timing $t_{\text{low}}$ and and high is the timing $t_{\text{high}}$ ). + - In order to unite at least $N_{\text{slots}}$ slots, consider the minimum integer number of 10 ms measurement intervals, where $N_{\text{slots}}$ is determined by. +- and $N_{\text{slots}}$ for 15 kHz SCS, $N_{\text{slots}}$ for 30 kHz SCS and $N_{\text{slots}}$ for 60 kHz SCS normal CP. +- Unite by RMS. + +## Annex I (informative): Change history + +| Change history | | | | | | | | +|----------------|---------------|------------|------|-----|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 04/2021 | RAN4#9 8bis-e | R4-2106058 | | | | IAB conducted conformance specification skeleton | 0.0.1 | +| 05/2021 | RAN4#9 9-e | R4-2111397 | | | | Update of IAB conducted conformance TS with agreed TP in RAN4#98bis-e:
R4-2106050 TP for Annex E for conducted IAB test specification
R4-2106054 TP to TS38.176-1 on subclause 4.10 -5
R4-2106131 TP to TS 38.176-1 -Clause 4.1
R4-2106059 TP to TS 38.176-1 - Annex D
R4-2106056 TP to TS 38.xxx-1: Section 4.2~4.5
R4-2106062 TP for TS 38.176-1: Transmit ON/OFF power
R4-2106064 TP to TS 38.176-1: Output power and Unwanted emission
R4-2106065 TP to TS 38.xxx-1: TX IMD requirements
R4-2106066 TP to TS 38.176-1 Annex A for IAB conducted test specification
R4-2106069 TP to TS 38.176-1 - Sensitivity, clause 7.2
R4-2106070 TP to TS 38.176-1 - Rx dynamic range, clause 7.3
R4-2106071 TP for IBB, OBB and RX spurious of conducted receiver test
R4-2106067 TP to TS 38.xxx-1: RX IMD requirements
R4-2106068 TP to TS 38.xxx-1: RX ICS requirements
R4-2106072 TP to TS 38.176-1 Clause 4.6 Declarations for IAB conducted test specification | 0.1.0 | +| 05/2021 | RAN4#9 9-e | R4-2108095 | | | | Update of IAB conducted conformance TS with agreed TP in RAN4#99-e:
R4-2111399 TP to TS 38.176-1 -Clean up
R4-2108565 TP to TS 38.176-1 on test efficiency clause 4.13
R4-2108569 TP for TS 38.176-1: Test configurations and applicability of requirements
R4-2108567 TP to TS 38.176-1: IAB Common test issue on test model-Conducted
R4-2108571 TP for TS 38.176-1: Annex B and C
R4-2108573 TP to TS 38.176-1 -Clause 4.1
R4-2111397 TS 38.176-1 -Updated TS 37.176-1
R4-2111399 TP to TS 38.176-1 -Clean up
R4-2108710 TP for TS 38.176-1: Transmitted signal quality
R4-2108087 TP to TS 38.176-1 - OTA Tx dynamic range, clause 6.3
R4-2111177 TP for IBB, OBB and RX spurious of conducted receiver test
R4-2111405 TP to TS 38.176-1 - Sensitivity, clause 7.2
R4-2108576 TP to TS 38.176-1 Clause 4.6 Declarations for IAB conducted test specification
R4-2108577 TP to TS 38.176-1: Annex G and H: In-channel TX test | 0.2.0 | +| 06/2021 | RAN#92-e | RP-211342 | | | | Presented to TSG RAN for approval.
(Including RF and Demod parts:
R4-2108095 Big TP to TS 38.176-1 on RF part
R4-2109211 Big TP to TS 38.176-1: IAB demodulation performance requirement) | 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-1 Maintenance (Rel-16, CAT F) | 16.1.0 | +| 2021-12 | RAN#94 | RP-212851 | 0003 | | F | Big CR for TS 38.176-1 Maintenance (Rel-16, CAT F) | 16.2.0 | +| 2022-03 | RAN#95 | RP-220334 | 0004 | | F | Big CR for TS 38.176-1 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 | 0005 | | B | CR to TR 38.176-1 on introduction of 6GHz licensed band | 17.1.0 | +| 2022-06 | RAN#96 | RP-221665 | 0007 | | F | Big CR for TS 38.176-1 Maintenance (Rel-17, CAT F) | 17.1.0 | +| 2022-09 | RAN#97 | RP-222049 | 0011 | | B | Big CR for TS 38.176-1 (Rel-17, CAT B) | 17.2.0 | +| 2022-12 | RAN#98-e | RP-223310 | 0012 | | F | CR on eIAB performance -general requirement -38.176-1 | 17.3.0 | +| 2023-03 | RAN#99 | RP-230515 | 0014 | | A | CR to TS 38.176-1 with corrections to test models acronyms | 17.4.0 | +| 2023-03 | RAN#99 | RP-230515 | 0015 | | F | CR to TS 38.176-1 with bracket removal for measurement uncertainties for timing error between IAB-DU and IAB-MT | 17.4.0 | +| 2023-03 | RAN#99 | RP-230515 | 0019 | | A | CR to TS 38.176-1 Maintenance for IAB-MT performance requirement R17 | 17.4.0 | + +| Change history | | | | | | | | +|-----------------------|----------------|-------------|-----------|------------|------------|-----------------------------------------------------------------------------------------------------------------------|--------------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2023-03 | RAN#99 | RP-230535 | 0016 | | B | CR to 38.176-1 on introduction of Band n54 | 18.0.0 | +| 2023-03 | RAN#99 | RP-230533 | 0017 | | B | CR to TS 37.176-1: Introduction of NR band n105 | 18.0.0 | +| 2023-06 | RAN#100 | RP-231353 | 0021 | | A | CR to TS 38.176-1: 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-1 (Rel-18) | 18.1.0 | +| 2023-06 | RAN#100 | RP-231353 | 0026 | | A | CR to TS 38.176-1 Maintenance of IAB for supported BW R18 | 18.1.0 | +| 2023-09 | RAN#101 | RP-232491 | 0030 | | A | [NR_IAB-Perf] CR on NR IAB performance requirements (TS38.176-1, Rel-18) | 18.2.0 | +| 2023-12 | RAN#102 | RP-233366 | 0031 | | B | CR to TS38.176-1: introduction of NR bands n31 and n72 | 18.3.0 | +| 2023-12 | RAN#102 | RP-233366 | 0032 | | B | CR to TS38.176-1: the introduction of band n106 | 18.3.0 | +| 2023-12 | RAN#102 | RP-233371 | 0033 | | F | [NR_600MHz_APT-Perf] CR to TS38.176-1: Addition of missing band n105 for IAB coexistence and co-location requirements | 18.3.0 | +| 2023-12 | RAN#102 | RP-233338 | 0035 | | A | [NR_IAB-Perf] CR for 38.176-1: Removal of Square Brackets in IAB-MT Performance Requirements (Rel-18, Cat A) | 18.3.0 | +| 2023-12 | RAN#102 | RP-233347 | 0036 | | F | CR to TS 38.176-1 with correction of co-existence and co-location requirements | 18.3.0 | +| 2023-12 | RAN#102 | RP-233366 | 0038 | | B | CR to 38.176-1 on introduction of Band n109 | 18.3.0 | +| 2023-12 | RAN#102 | RP-233347 | 0040 | | 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/38181/037f0f683efaa7f7d98458c351d3ce6b_img.jpg b/marked/Rel-18/38_series/38181/037f0f683efaa7f7d98458c351d3ce6b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6dec4e67f066322086f27309aa2173cb38eb99ac --- /dev/null +++ b/marked/Rel-18/38_series/38181/037f0f683efaa7f7d98458c351d3ce6b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b317f667dc7e55b7aa68db8d346103a10c916f6648829ec51375790ca59eeaf +size 92300 diff --git a/marked/Rel-18/38_series/38181/079326de347e985e278d2674647d17dc_img.jpg b/marked/Rel-18/38_series/38181/079326de347e985e278d2674647d17dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..950b3c500cb59f3a73e29416d75bad8f63173ce2 --- /dev/null +++ b/marked/Rel-18/38_series/38181/079326de347e985e278d2674647d17dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5196f888049fcadf338d54f3354f4019263073ae55a26862ac4d0a5d0f874ebf +size 5913 diff --git a/marked/Rel-18/38_series/38181/0b8f0df92a831a94cdac664d8b05f0ec_img.jpg b/marked/Rel-18/38_series/38181/0b8f0df92a831a94cdac664d8b05f0ec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fce33a6949280207140f3f0f9aca8f2c522054fb --- /dev/null +++ b/marked/Rel-18/38_series/38181/0b8f0df92a831a94cdac664d8b05f0ec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c47a9032eb157d558bcae5aad78d1b5e67c1bfd7b3005b2cd08dc9f7de7ebe57 +size 36932 diff --git a/marked/Rel-18/38_series/38181/223792b3652794024244c277cc46394b_img.jpg b/marked/Rel-18/38_series/38181/223792b3652794024244c277cc46394b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c334df4f49ae6145828fff88ac0eecbe9cdaaec --- /dev/null +++ b/marked/Rel-18/38_series/38181/223792b3652794024244c277cc46394b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee28614ee418eee2fd04f9a684dc922072af36fc7bed1d369d7af6691a731b04 +size 4842 diff --git a/marked/Rel-18/38_series/38181/235956431f37eb6f426ad00290e52a08_img.jpg b/marked/Rel-18/38_series/38181/235956431f37eb6f426ad00290e52a08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b764d8eb385b2fb0c9b0dc71f051b3fd637bb65a --- /dev/null +++ b/marked/Rel-18/38_series/38181/235956431f37eb6f426ad00290e52a08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fbb38eff2da8e39d1f4cc2c2723ca38f430c1a4ff55673bd6b6a583f61c6ffb3 +size 39772 diff --git a/marked/Rel-18/38_series/38181/29178b001cb4c04e0c5ab60662ce5d80_img.jpg b/marked/Rel-18/38_series/38181/29178b001cb4c04e0c5ab60662ce5d80_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7e041432b319c4253235023c550f9001c1e43be --- /dev/null +++ b/marked/Rel-18/38_series/38181/29178b001cb4c04e0c5ab60662ce5d80_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24cfede629141e6e5f86089203b0dfa4e920e19b01db0c95df5afd4ad7ca0c29 +size 37391 diff --git a/marked/Rel-18/38_series/38181/2957154f4dc666a6cafb7b4d2d882910_img.jpg b/marked/Rel-18/38_series/38181/2957154f4dc666a6cafb7b4d2d882910_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..436491f215a896bf4d85b891a7618e0b63948cec --- /dev/null +++ b/marked/Rel-18/38_series/38181/2957154f4dc666a6cafb7b4d2d882910_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:536535cf981d73b9986edbf686559b9885da60f88964fdbe6fe69a85f5384d4a +size 5450 diff --git a/marked/Rel-18/38_series/38181/313826501fcb4294a5d337702ea35f2d_img.jpg b/marked/Rel-18/38_series/38181/313826501fcb4294a5d337702ea35f2d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a981c0ece5024e6c560219d2509cccddf15efda4 --- /dev/null +++ b/marked/Rel-18/38_series/38181/313826501fcb4294a5d337702ea35f2d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:163354dc4677fe7b57709ce21e0a6d30976232d10f69daf0607dd012fad8a6b9 +size 33713 diff --git a/marked/Rel-18/38_series/38181/345a37f4d6b16c98368c8144e67313d0_img.jpg b/marked/Rel-18/38_series/38181/345a37f4d6b16c98368c8144e67313d0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ce8359f58d19da834cc1ea77d2ad6c93bc0496a --- /dev/null +++ b/marked/Rel-18/38_series/38181/345a37f4d6b16c98368c8144e67313d0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0bd089a4a08d6dbad91929d714e8924a1e29ad1cb6db7fd59da5a488a0d8e050 +size 13500 diff --git a/marked/Rel-18/38_series/38181/3893e26cb0b95e076fdc8953d2db0072_img.jpg b/marked/Rel-18/38_series/38181/3893e26cb0b95e076fdc8953d2db0072_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a559fd47e083cdf89c2afdb652f1fc21b3d4e59 --- /dev/null +++ b/marked/Rel-18/38_series/38181/3893e26cb0b95e076fdc8953d2db0072_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fce30ce3fe59211c5a90970ee684d2c6c2f351a9eb4fb560de50c67d2fb58d43 +size 49740 diff --git a/marked/Rel-18/38_series/38181/39fbaf75053c08ab3bb2cbff5ad6ec67_img.jpg b/marked/Rel-18/38_series/38181/39fbaf75053c08ab3bb2cbff5ad6ec67_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..547218223eb1f92d821bfaa431821691d1666042 --- /dev/null +++ b/marked/Rel-18/38_series/38181/39fbaf75053c08ab3bb2cbff5ad6ec67_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:110baf0fc33033abc50c27e696cf1b75d4be4795eb263620f834b31306c0d528 +size 33317 diff --git a/marked/Rel-18/38_series/38181/46d9e0876283f18b63c5b7ac7b63bd41_img.jpg b/marked/Rel-18/38_series/38181/46d9e0876283f18b63c5b7ac7b63bd41_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..677106d890d558e55ebb2b1b632bac30edbcca03 --- /dev/null +++ b/marked/Rel-18/38_series/38181/46d9e0876283f18b63c5b7ac7b63bd41_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b872ddc969cef35858e0012e7e17b1ef6b41f222f36d277a0ff8d623b632d3a +size 22391 diff --git a/marked/Rel-18/38_series/38181/51501a01b2c29ac95e126882508f8831_img.jpg b/marked/Rel-18/38_series/38181/51501a01b2c29ac95e126882508f8831_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98b0a5cbbde65063af8d275eb430faba9e2da9b5 --- /dev/null +++ b/marked/Rel-18/38_series/38181/51501a01b2c29ac95e126882508f8831_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:99d0f3e4161f1e7d7792ddbaa6eede6f93287dd5ffd9c8b2163d7911c29f2e54 +size 4908 diff --git a/marked/Rel-18/38_series/38181/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38181/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1db461d4c07ca3ab6af40337c6a646f752d58caf --- /dev/null +++ b/marked/Rel-18/38_series/38181/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8a30178a146c953ab98612742816f96263d174a54881c630b33336fcdedc1d3 +size 10302 diff --git a/marked/Rel-18/38_series/38181/6116b1a533010c170fc526ec513ba0b8_img.jpg b/marked/Rel-18/38_series/38181/6116b1a533010c170fc526ec513ba0b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d058167ba0469546e5a791b329266c2324915e83 --- /dev/null +++ b/marked/Rel-18/38_series/38181/6116b1a533010c170fc526ec513ba0b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1830906d6748afdb643e32631003059c888dff28de93e9482b03a8ddf0943d1c +size 5084 diff --git a/marked/Rel-18/38_series/38181/61d000f6a2a1ff2f0da0b51fb732fafb_img.jpg b/marked/Rel-18/38_series/38181/61d000f6a2a1ff2f0da0b51fb732fafb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d69ba0fdd007ca0c26869069d65c4728edf97f46 --- /dev/null +++ b/marked/Rel-18/38_series/38181/61d000f6a2a1ff2f0da0b51fb732fafb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b172d7617c9047a52b5caf2ce61a6369389159330a245a0c1b5f0e170cf6d524 +size 5484 diff --git a/marked/Rel-18/38_series/38181/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38181/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..142ae31946e859b92ad99571107b6cf1447afc1c --- /dev/null +++ b/marked/Rel-18/38_series/38181/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7077c2e76a6b60dff72a8a53eefb3cc1261d45f90f649d801b98d5f4649d3b8f +size 5490 diff --git a/marked/Rel-18/38_series/38181/6cdb31bed6791fa0bd3fbc1e583b07ed_img.jpg b/marked/Rel-18/38_series/38181/6cdb31bed6791fa0bd3fbc1e583b07ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..54e6551fd827904f44f830d1216f61f33fed793c --- /dev/null +++ b/marked/Rel-18/38_series/38181/6cdb31bed6791fa0bd3fbc1e583b07ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:637e1ce7cd53c8d59f8864025884ee25c360bfb8774b4ef37b14316c54abe52e +size 44845 diff --git a/marked/Rel-18/38_series/38181/7478250c3f9a732a15bbd7d500d1c8f1_img.jpg b/marked/Rel-18/38_series/38181/7478250c3f9a732a15bbd7d500d1c8f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2753a395021f007c28d94201e55e8e1b0b04299e --- /dev/null +++ b/marked/Rel-18/38_series/38181/7478250c3f9a732a15bbd7d500d1c8f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3752f22a5321205ad3d0928971b33b107b93940268ab50f37935ebeef7d138be +size 40687 diff --git a/marked/Rel-18/38_series/38181/7b49a5e2da4a559dce8c167c9203ad8e_img.jpg b/marked/Rel-18/38_series/38181/7b49a5e2da4a559dce8c167c9203ad8e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..924053793dd523172a994d4fff30e4361dc91b2c --- /dev/null +++ b/marked/Rel-18/38_series/38181/7b49a5e2da4a559dce8c167c9203ad8e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68d9682f649d6f43bcf2066b0d4ea85afdbf435a47f969b1e747b3ffc912ae28 +size 18699 diff --git a/marked/Rel-18/38_series/38181/7c19fc92dc74a74ec346d46bc39a3946_img.jpg b/marked/Rel-18/38_series/38181/7c19fc92dc74a74ec346d46bc39a3946_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a80fe56c3c2558227e62538274be4a9de237bf4 --- /dev/null +++ b/marked/Rel-18/38_series/38181/7c19fc92dc74a74ec346d46bc39a3946_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29624e5bc79855fe0abd6108fceddaaa5a6caea421f6bb839669de6c0c1092e9 +size 46627 diff --git a/marked/Rel-18/38_series/38181/7d2d1d3870cd224c4430d19334557716_img.jpg b/marked/Rel-18/38_series/38181/7d2d1d3870cd224c4430d19334557716_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..682194c8ad92b40c6b430d464931ef5e26b44815 --- /dev/null +++ b/marked/Rel-18/38_series/38181/7d2d1d3870cd224c4430d19334557716_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e06c6d4e7e73f1e537526556dae4571b97126226824b4d5142745eeed3adab9 +size 43144 diff --git a/marked/Rel-18/38_series/38181/80ec3bf791fd8eb41f73a420c2122529_img.jpg b/marked/Rel-18/38_series/38181/80ec3bf791fd8eb41f73a420c2122529_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..becbb048f512f6ea2f6805b2b9674fd89e5172f2 --- /dev/null +++ b/marked/Rel-18/38_series/38181/80ec3bf791fd8eb41f73a420c2122529_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9a3008197cdc5ba2d96e463e0a643acb0c3ae0d9d6fde3ba6cf622e232382c7 +size 41505 diff --git a/marked/Rel-18/38_series/38181/84e5b251aa38db522f76f5cc3afcb853_img.jpg b/marked/Rel-18/38_series/38181/84e5b251aa38db522f76f5cc3afcb853_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c89994c2598bccd2886942e06e2fe43f30934d0a --- /dev/null +++ b/marked/Rel-18/38_series/38181/84e5b251aa38db522f76f5cc3afcb853_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:63d6f38a1182234cf40a360f79e5c9df47e52074a7325744f6ebfbe448714c74 +size 47263 diff --git a/marked/Rel-18/38_series/38181/8512afe2a50a7087c8b77a68dd354994_img.jpg b/marked/Rel-18/38_series/38181/8512afe2a50a7087c8b77a68dd354994_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f268c5013a5e42e0975730cc89be9571611d78b --- /dev/null +++ b/marked/Rel-18/38_series/38181/8512afe2a50a7087c8b77a68dd354994_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:509c27f6f91deb669ec4d910199406c64f2c953abf7b5535e8a8a77359663e5d +size 98195 diff --git a/marked/Rel-18/38_series/38181/88f5a639e0e8bae43a30c7ebe33752e5_img.jpg b/marked/Rel-18/38_series/38181/88f5a639e0e8bae43a30c7ebe33752e5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ba04de77454ab8205195af0f8196690f8eb2646 --- /dev/null +++ b/marked/Rel-18/38_series/38181/88f5a639e0e8bae43a30c7ebe33752e5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a1988e9eb8a213f8842b3fb327a4ffc98bb8073059cdd31938e8dd3e230592b0 +size 107165 diff --git a/marked/Rel-18/38_series/38181/91e400bc8bab58306b4d18432e94c9de_img.jpg b/marked/Rel-18/38_series/38181/91e400bc8bab58306b4d18432e94c9de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a23f59197a3633d44cdb346c75b8d95e353a8718 --- /dev/null +++ b/marked/Rel-18/38_series/38181/91e400bc8bab58306b4d18432e94c9de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f7f987be6092567fe38ead6bc8a2415de5d53f2b5281c9c8a22b0a2babc8b66d +size 5537 diff --git a/marked/Rel-18/38_series/38181/98e54d5540b2efe3e24af3cf936bc4ea_img.jpg b/marked/Rel-18/38_series/38181/98e54d5540b2efe3e24af3cf936bc4ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..938f5f8cc4a539ab2fdc05e05ac2c3a70f0086eb --- /dev/null +++ b/marked/Rel-18/38_series/38181/98e54d5540b2efe3e24af3cf936bc4ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d86c3cfb138f92941db7895ca403fb35e920f79927b9f1365a57fe77707af0a2 +size 31944 diff --git a/marked/Rel-18/38_series/38181/9af97997b7d3fbca90b8ddba0ea39c6c_img.jpg b/marked/Rel-18/38_series/38181/9af97997b7d3fbca90b8ddba0ea39c6c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1ea30c7e4f7eb16d06713b9f09d51fa3fb8b352 --- /dev/null +++ b/marked/Rel-18/38_series/38181/9af97997b7d3fbca90b8ddba0ea39c6c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c4a0176744b354c39278dcd68ccc5e9af8a6d523e7501b6cd09aa93fd1b73dd +size 32279 diff --git a/marked/Rel-18/38_series/38181/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg b/marked/Rel-18/38_series/38181/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51cb6683e383d5c979bda4e1fd4a1cdfdbcad1d0 --- /dev/null +++ b/marked/Rel-18/38_series/38181/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49e13601ea8de651bf5106724dd18423c33fe4dca21b53a0836e92387e20a9d7 +size 46556 diff --git a/marked/Rel-18/38_series/38181/a0eb8d30ac11ba97b2733c187b89ff22_img.jpg b/marked/Rel-18/38_series/38181/a0eb8d30ac11ba97b2733c187b89ff22_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..111aeaa51160dad4b1467531f1ff243c8fb83d04 --- /dev/null +++ b/marked/Rel-18/38_series/38181/a0eb8d30ac11ba97b2733c187b89ff22_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a1e0301fffbab64f4cdcad39b29a4f8a92a725a72f639d1ab4bad63c745bb583 +size 18999 diff --git a/marked/Rel-18/38_series/38181/aa2c37b4b3f732603f944bbda641b722_img.jpg b/marked/Rel-18/38_series/38181/aa2c37b4b3f732603f944bbda641b722_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..586c0022a38f4110180a568e31edb9ce1d0d91e3 --- /dev/null +++ b/marked/Rel-18/38_series/38181/aa2c37b4b3f732603f944bbda641b722_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:662ff08df9ef7f86547c62badd455a10bfc9a4de386c93c4f3e911750edd370c +size 32723 diff --git a/marked/Rel-18/38_series/38181/bbd1d8687d2e06af9f71954d66034838_img.jpg b/marked/Rel-18/38_series/38181/bbd1d8687d2e06af9f71954d66034838_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef827ffe8721404ef74744ee1e7d5a7873090186 --- /dev/null +++ b/marked/Rel-18/38_series/38181/bbd1d8687d2e06af9f71954d66034838_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98d51f92ef96adbc574b7509ac1fa98995ea159edaf38017a814f402788a41a8 +size 100755 diff --git a/marked/Rel-18/38_series/38181/bd7d36eb91fa35077ac820550097bac2_img.jpg b/marked/Rel-18/38_series/38181/bd7d36eb91fa35077ac820550097bac2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..046cee7b7bcc3e05f8f40828bd825dbe86c6afff --- /dev/null +++ b/marked/Rel-18/38_series/38181/bd7d36eb91fa35077ac820550097bac2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:269121b43f460ae8c302177cd53f01e28adcb82864cd2e19b522d906299ab1ba +size 4677 diff --git a/marked/Rel-18/38_series/38181/be2dee4acf57ae6f4e3a015e28bcfb61_img.jpg b/marked/Rel-18/38_series/38181/be2dee4acf57ae6f4e3a015e28bcfb61_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cb692b16f535f927178f62a8688795e4a96bcf16 --- /dev/null +++ b/marked/Rel-18/38_series/38181/be2dee4acf57ae6f4e3a015e28bcfb61_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5f20e3836f41e8772e1122af2192b5938620f05636dca23b9b442f07bfb79b22 +size 41941 diff --git a/marked/Rel-18/38_series/38181/bf15a4a25f6e71dea348cde412f1df55_img.jpg b/marked/Rel-18/38_series/38181/bf15a4a25f6e71dea348cde412f1df55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f8c14f617dd16a3ebabcf7b77ef40209e0b4982 --- /dev/null +++ b/marked/Rel-18/38_series/38181/bf15a4a25f6e71dea348cde412f1df55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e86949736635436480eb806b87b9a9fec8c191350259d9b57004fcff68dfbf93 +size 140186 diff --git a/marked/Rel-18/38_series/38181/c28a32402d58c11a48dfffe91182e745_img.jpg b/marked/Rel-18/38_series/38181/c28a32402d58c11a48dfffe91182e745_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..05a3aabee168dde8b3172676ff2ebe18bfb834d1 --- /dev/null +++ b/marked/Rel-18/38_series/38181/c28a32402d58c11a48dfffe91182e745_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:644360084f0c0c91908c675d69080594779df5f125eeecb0a33ff8e5c687c058 +size 42715 diff --git a/marked/Rel-18/38_series/38181/c5d9ee57705b6598bd43f9c075fec3c7_img.jpg b/marked/Rel-18/38_series/38181/c5d9ee57705b6598bd43f9c075fec3c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d518ec551f1e305682e92db43912e35f64816f95 --- /dev/null +++ b/marked/Rel-18/38_series/38181/c5d9ee57705b6598bd43f9c075fec3c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a9433524f0641cdb1312e8233d01c8a2dc1cfc91cb555556e5c535d459a9278 +size 5082 diff --git a/marked/Rel-18/38_series/38181/ca5dc5fde2061d0ca2051ef7840fc842_img.jpg b/marked/Rel-18/38_series/38181/ca5dc5fde2061d0ca2051ef7840fc842_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..683ae17f5fa3757df717f5a165290da3ea20c27c --- /dev/null +++ b/marked/Rel-18/38_series/38181/ca5dc5fde2061d0ca2051ef7840fc842_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4cfd3a82cfc6934d3d62ab0efe64315afa7398ba2d59300895660648ac52e45 +size 32538 diff --git a/marked/Rel-18/38_series/38181/d4735388eddeb40049070f8ab30921be_img.jpg b/marked/Rel-18/38_series/38181/d4735388eddeb40049070f8ab30921be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..76873db61f51ef9687cdd2395c14a43586bf062b --- /dev/null +++ b/marked/Rel-18/38_series/38181/d4735388eddeb40049070f8ab30921be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:43f6be6bd94374a3a51bf3460ae51b5369f5c1cd688df9f3530f2d36d3d5ab56 +size 32531 diff --git a/marked/Rel-18/38_series/38181/d77263a08ee7c05fd8a0edf5b071b865_img.jpg b/marked/Rel-18/38_series/38181/d77263a08ee7c05fd8a0edf5b071b865_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea6e24f2f1ab303308a4d951bcd1cfd780ed5bc1 --- /dev/null +++ b/marked/Rel-18/38_series/38181/d77263a08ee7c05fd8a0edf5b071b865_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:234b48ad2dc2604750c4a18fd9d34abed35268861fd349b5cc6fb10b7c7ccd3c +size 36277 diff --git a/marked/Rel-18/38_series/38181/dcc3de7b5b2ad8fbacf8f3c7b5b08aa3_img.jpg b/marked/Rel-18/38_series/38181/dcc3de7b5b2ad8fbacf8f3c7b5b08aa3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f18b34ebccc028e4779e6002f06d4d211e15c87 --- /dev/null +++ b/marked/Rel-18/38_series/38181/dcc3de7b5b2ad8fbacf8f3c7b5b08aa3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:45ab4d45d689765ace3fa62312731fe836acb40629163d7301d7f325c58d8f51 +size 5690 diff --git a/marked/Rel-18/38_series/38181/dcff3b4c32053e26f2c807df3c11b55b_img.jpg b/marked/Rel-18/38_series/38181/dcff3b4c32053e26f2c807df3c11b55b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab384c513ed2eeb40851a61c6f874cac17f6336e --- /dev/null +++ b/marked/Rel-18/38_series/38181/dcff3b4c32053e26f2c807df3c11b55b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cdce2625995c988b4ccbde9077196659718436f19272d6e29da0850cf027883b +size 50681 diff --git a/marked/Rel-18/38_series/38181/e034b0863f1ccdc3e0b3d0e2f449be66_img.jpg b/marked/Rel-18/38_series/38181/e034b0863f1ccdc3e0b3d0e2f449be66_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac1e85592d4a21919fb448dc88fdb391ec892de2 --- /dev/null +++ b/marked/Rel-18/38_series/38181/e034b0863f1ccdc3e0b3d0e2f449be66_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5247f972ae236c1a4471323b06052485a7492adb27c0180aa808d729e8d45184 +size 4846 diff --git a/marked/Rel-18/38_series/38181/f087d3f5d298b3b1634d13ff17879e41_img.jpg b/marked/Rel-18/38_series/38181/f087d3f5d298b3b1634d13ff17879e41_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f097cefcf8a2f8700545beba8b3e110bab7717e --- /dev/null +++ b/marked/Rel-18/38_series/38181/f087d3f5d298b3b1634d13ff17879e41_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2350e13e1212fcfc9d358c5383d1e01ff74bb9c93a32e2ec6aa909a183e8d55b +size 20244 diff --git a/marked/Rel-18/38_series/38181/f26e237ac9b5c1b2cbbb849964f978f0_img.jpg b/marked/Rel-18/38_series/38181/f26e237ac9b5c1b2cbbb849964f978f0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b7ad1eb54f7e858073aca58311b3dba4f4d4f020 --- /dev/null +++ b/marked/Rel-18/38_series/38181/f26e237ac9b5c1b2cbbb849964f978f0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96ce31d3cd4d7adc862da2f248140bc0dc75740cb77b622a08f960ea075957ad +size 18453 diff --git a/marked/Rel-18/38_series/38181/ff3a3d26b4b40920cf1377205fb08445_img.jpg b/marked/Rel-18/38_series/38181/ff3a3d26b4b40920cf1377205fb08445_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..17c2d8f43c9aa48d8da6031ce2921204115cb9c5 --- /dev/null +++ b/marked/Rel-18/38_series/38181/ff3a3d26b4b40920cf1377205fb08445_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d8d3548efc8cc60924272de993236b2f7e872f828e70b47be0dfb2bd53c147a +size 46926 diff --git a/marked/Rel-18/38_series/38181/raw.md b/marked/Rel-18/38_series/38181/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..9aa04894803038a6baf2822ff3f4e1404a1513e0 --- /dev/null +++ b/marked/Rel-18/38_series/38181/raw.md @@ -0,0 +1,8266 @@ + + +# 3GPP TS 38.181 V18.0.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Satellite Access Node (SAN) 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. At the bottom, the text 'A GLOBAL INITIATIVE' is written in a smaller, spaced-out 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..... | 27 | +| 1 Scope..... | 29 | +| 2 References..... | 29 | +| 3 Definitions of terms, symbols and abbreviations..... | 30 | +| 3.1 Terms..... | 30 | +| 3.2 Symbols..... | 33 | +| 3.3 Abbreviations..... | 34 | +| 4 General test conditions and declarations..... | 35 | +| 4.1 Measurement uncertainties and test requirements..... | 35 | +| 4.1.1 General..... | 35 | +| 4.1.2 Acceptable uncertainty of Test System..... | 36 | +| 4.1.2.1 General..... | 36 | +| 4.1.2.2 Measurement of transmitter..... | 37 | +| 4.1.2.3 Measurement of receiver..... | 38 | +| 4.1.2.4 Measurement of performance requirements..... | 40 | +| 4.1.3 Interpretation of measurement results..... | 40 | +| 4.2 Requirement reference points..... | 41 | +| 4.2.1 SAN type 1-H..... | 41 | +| 4.2.2 SAN type 1-O..... | 42 | +| 4.3 Satellite Access Node classes..... | 42 | +| 4.4 Regional requirements..... | 42 | +| 4.5 SAN configurations..... | 43 | +| 4.5.1 SAN type 1-H transmit configurations..... | 43 | +| 4.5.2 SAN type 1-H receive configurations..... | 43 | +| 4.5.3 SAN type 1-O transmit configurations..... | 44 | +| 4.5.4 SAN type 1-O receive configurations..... | 44 | +| 4.5.5 Power supply options..... | 44 | +| 4.6 Manufacturer declarations..... | 45 | +| 4.7 Test configurations..... | 52 | +| 4.7.1 General..... | 52 | +| 4.7.2 Test signal used to build Test Configurations..... | 52 | +| 4.7.3 NRTC1: Contiguous spectrum operation..... | 53 | +| 4.7.3.1 NRTC1 generation..... | 53 | +| 4.7.3.2 NRTC1 power allocation..... | 53 | +| 4.8 Applicability of requirements..... | 53 | +| 4.8.1 General..... | 53 | +| 4.8.2 Requirement set applicability..... | 53 | +| 4.8.3 Applicability of test configurations for single-band operation..... | 54 | +| 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-SAN-FR1-TM1.1)..... | 57 | +| 4.9.2.2.2 FR1 test model 1.2 (NR-SAN-FR1-TM1.2)..... | 58 | +| 4.9.2.2.3 FR1 test model 2 (NR-SAN-FR1-TM2)..... | 58 | +| 4.9.2.2.4 FR1 test model 3.1 (NR-SAN-FR1-TM3.1)..... | 59 | +| 4.9.2.2.5 FR1 test model 3.2 (NR-SAN-FR1-TM3.2)..... | 59 | +| 4.9.2.2.6 FR1 test model 3.3 (NR-SAN-FR1-TM3.3)..... | 60 | +| 4.9.2.3 Data content of Physical channels and Signals for NR-SAN-FR1-TM..... | 61 | +| 4.9.2.3.1 PDCCH..... | 61 | +| 4.9.2.3.2 PDSCH..... | 61 | +| 4.10 Void..... | 62 | +| 4.11 Reference coordinate system..... | 62 | +| 4.12 Format and interpretation of tests..... | 63 | + +| | | | +|-----------|--------------------------------------------------|----| +| 5 | Operating bands and channel arrangement..... | 64 | +| 6 | Conducted transmitter characteristics..... | 64 | +| 6.1 | General..... | 64 | +| 6.1.1 | SAN type 1-H..... | 64 | +| 6.2 | Satellite Access Node output power..... | 64 | +| 6.2.1 | Definition and applicability..... | 64 | +| 6.2.2 | Minimum requirement..... | 65 | +| 6.2.3 | Test purpose..... | 65 | +| 6.2.4 | Method of test..... | 65 | +| 6.2.4.1 | Initial conditions..... | 65 | +| 6.2.4.2 | Procedure..... | 65 | +| 6.2.5 | Test requirement..... | 66 | +| 6.3 | Output power dynamics..... | 66 | +| 6.3.1 | General..... | 66 | +| 6.3.2 | RE power control dynamic range..... | 66 | +| 6.3.2.1 | Definition and applicability..... | 66 | +| 6.3.2.2 | Minimum requirement..... | 66 | +| 6.3.2.3 | Test purpose..... | 66 | +| 6.3.3 | Total power dynamic range..... | 66 | +| 6.3.3.1 | Definition and applicability..... | 66 | +| 6.3.3.2 | Minimum requirement..... | 66 | +| 6.3.3.3 | Test purpose..... | 67 | +| 6.3.3.4 | Method of test..... | 67 | +| 6.3.3.4.1 | Initial conditions..... | 67 | +| 6.3.3.4.2 | Procedure..... | 67 | +| 6.3.3.5 | Test requirements..... | 67 | +| 6.4 | Transmit ON/OFF power..... | 68 | +| 6.5 | Transmitted signal quality..... | 68 | +| 6.5.1 | General..... | 68 | +| 6.5.2 | Frequency error..... | 68 | +| 6.5.2.1 | Definition and applicability..... | 68 | +| 6.5.2.2 | Minimum Requirement..... | 68 | +| 6.5.2.3 | Test purpose..... | 68 | +| 6.5.2.4 | Method of test..... | 68 | +| 6.5.2.5 | Test Requirements..... | 68 | +| 6.5.3 | Modulation quality..... | 69 | +| 6.5.3.1 | Definition and applicability..... | 69 | +| 6.5.3.2 | Minimum Requirement..... | 69 | +| 6.5.3.3 | Test purpose..... | 69 | +| 6.5.3.4 | Method of test..... | 69 | +| 6.5.3.4.1 | Initial conditions..... | 69 | +| 6.5.3.4.2 | Procedure..... | 69 | +| 6.5.3.5 | Test requirements..... | 70 | +| 6.6 | Unwanted emissions..... | 71 | +| 6.6.1 | General..... | 71 | +| 6.6.2 | Occupied bandwidth..... | 71 | +| 6.6.2.1 | Definition and applicability..... | 71 | +| 6.6.2.2 | Minimum requirements..... | 71 | +| 6.6.2.3 | Test purpose..... | 71 | +| 6.6.2.4 | Method of test..... | 71 | +| 6.6.2.4.1 | Initial conditions..... | 71 | +| 6.6.2.4.2 | Procedure..... | 72 | +| 6.6.2.5 | Test requirements..... | 72 | +| 6.6.3 | Adjacent Channel Leakage Power Ratio (ACLR)..... | 72 | +| 6.6.3.1 | Definition and applicability..... | 72 | +| 6.6.3.2 | Minimum requirement..... | 72 | +| 6.6.3.3 | Test purpose..... | 73 | +| 6.6.3.4 | Method of test..... | 73 | +| 6.6.3.4.1 | Initial conditions..... | 73 | +| 6.6.3.4.2 | Procedure..... | 73 | +| 6.6.3.5 | Test requirements..... | 73 | + +| | | | +|-----------|-----------------------------------------|----| +| 6.6.3.5.1 | General requirements..... | 73 | +| 6.6.3.5.2 | Limits..... | 73 | +| 6.6.4 | Out-of-band emissions..... | 74 | +| 6.6.4.1 | Definition and applicability..... | 74 | +| 6.6.4.2 | Minimum requirement..... | 74 | +| 6.6.4.3 | Test purpose..... | 75 | +| 6.6.4.4 | Method of test..... | 75 | +| 6.6.4.4.1 | Initial conditions..... | 75 | +| 6.6.4.4.2 | Procedure..... | 75 | +| 6.6.4.5 | Test requirements..... | 75 | +| 6.6.5 | Transmitter spurious emissions..... | 76 | +| 6.6.5.1 | Definition and applicability..... | 76 | +| 6.6.5.2 | Minimum requirement..... | 76 | +| 6.6.5.3 | Test purpose..... | 76 | +| 6.6.5.4 | Method of test..... | 76 | +| 6.6.5.4.1 | Initial conditions..... | 76 | +| 6.6.5.4.2 | Procedure..... | 77 | +| 6.6.5.5 | Test requirements..... | 77 | +| 6.6.5.5.1 | Basic limits..... | 77 | +| 6.7 | Transmitter intermodulation..... | 78 | +| 7 | Conducted receiver characteristics..... | 78 | +| 7.1 | General..... | 78 | +| 7.2 | Reference sensitivity level..... | 78 | +| 7.2.1 | Definition and applicability..... | 78 | +| 7.2.2 | Minimum requirement..... | 78 | +| 7.2.3 | Test purpose..... | 78 | +| 7.2.4 | Method of test..... | 78 | +| 7.2.4.1 | Initial conditions..... | 78 | +| 7.2.4.2 | Procedure..... | 79 | +| 7.2.5 | Test requirements..... | 79 | +| 7.3 | Dynamic range..... | 80 | +| 7.3.1 | Definition and applicability..... | 80 | +| 7.3.2 | Minimum requirement..... | 80 | +| 7.3.3 | Test purpose..... | 80 | +| 7.3.4 | Method of test..... | 80 | +| 7.3.4.1 | Initial conditions..... | 80 | +| 7.3.4.2 | Procedure..... | 80 | +| 7.3.5 | Test requirements..... | 80 | +| 7.4 | In-band sensitivity and blocking..... | 81 | +| 7.4.1 | Adjacent Channel Selectivity (ACS)..... | 81 | +| 7.4.1.1 | Definition and applicability..... | 81 | +| 7.4.1.2 | Minimum requirement..... | 81 | +| 7.4.1.3 | Test purpose..... | 81 | +| 7.4.1.4 | Method of test..... | 81 | +| 7.4.1.4.1 | Initial conditions..... | 81 | +| 7.4.1.4.2 | Procedure..... | 81 | +| 7.4.1.5 | Test requirements..... | 82 | +| 7.4.2 | In-band blocking..... | 82 | +| 7.5 | Out-of-band blocking..... | 83 | +| 7.5.1 | Definition and applicability..... | 83 | +| 7.5.2 | Minimum requirement..... | 83 | +| 7.5.3 | Test purpose..... | 83 | +| 7.5.4 | Method of test..... | 83 | +| 7.5.4.1 | Initial conditions..... | 83 | +| 7.5.4.2 | Procedure..... | 83 | +| 7.5.5 | Test requirements..... | 83 | +| 7.6 | Receiver spurious emission..... | 84 | +| 7.7 | Receiver intermodulation..... | 84 | +| 7.8 | In-channel selectivity..... | 84 | +| 7.8.1 | Definition and applicability..... | 84 | +| 7.8.2 | Minimum requirement..... | 84 | + +| | | | +|-----------|---------------------------------------------------------------------------|----| +| 7.8.3 | Test purpose..... | 84 | +| 7.8.4 | Method of test..... | 84 | +| 7.8.4.1 | Initial conditions..... | 84 | +| 7.8.4.2 | Procedure..... | 84 | +| 7.8.5 | Test requirements..... | 85 | +| 8 | Conducted performance characteristics..... | 86 | +| 8.1 | General..... | 86 | +| 8.1.1 | Scope and definitions..... | 86 | +| 8.1.2 | Applicability rule..... | 87 | +| 8.1.2.1 | General..... | 87 | +| 8.1.2.2 | Applicability of PUSCH performance requirements..... | 87 | +| 8.1.2.2.1 | Applicability of requirements for different subcarrier spacings..... | 87 | +| 8.1.2.2.2 | Applicability of requirements for different channel bandwidths..... | 87 | +| 8.1.2.2.3 | Applicability of requirements for different configurations..... | 87 | +| 8.1.2.3 | Applicability of PUCCH performance requirements..... | 87 | +| 8.1.2.3.1 | Applicability of requirements for different formats..... | 87 | +| 8.1.2.3.2 | Applicability of requirements for different subcarrier spacings..... | 87 | +| 8.1.2.3.3 | Applicability of requirements for different channel bandwidths..... | 87 | +| 8.1.2.3.4 | Applicability of requirements for different configurations..... | 87 | +| 8.1.2.3.5 | Applicability of requirements for multi-slot PUCCH..... | 88 | +| 8.1.2.4 | Applicability of PRACH performance requirements..... | 88 | +| 8.1.2.4.1 | Applicability of requirements for different formats..... | 88 | +| 8.1.2.4.2 | Applicability of requirements for different subcarrier spacings..... | 88 | +| 8.1.2.4.3 | Applicability of requirements for different channel bandwidths..... | 88 | +| 8.2 | Performance requirements for PUSCH..... | 88 | +| 8.2.1 | Performance requirements for PUSCH with transform precoding disabled..... | 88 | +| 8.2.1.1 | Definition and applicability..... | 88 | +| 8.2.1.2 | Minimum Requirement..... | 88 | +| 8.2.1.3 | Test Purpose..... | 88 | +| 8.2.1.4 | Method of test..... | 88 | +| 8.2.1.4.1 | Initial Conditions..... | 88 | +| 8.2.1.4.2 | Procedure..... | 89 | +| 8.2.1.5 | Test Requirement..... | 89 | +| 8.2.2 | Performance requirements for PUSCH with transform precoding enabled..... | 90 | +| 8.2.2.1 | Definition and applicability..... | 90 | +| 8.2.2.2 | Minimum Requirement..... | 91 | +| 8.2.2.3 | Test Purpose..... | 91 | +| 8.2.2.4 | Method of test..... | 91 | +| 8.2.2.4.1 | Initial Conditions..... | 91 | +| 8.2.2.4.2 | Procedure..... | 91 | +| 8.2.2.5 | Test Requirement..... | 92 | +| 8.2.3 | Performance requirements for UL timing adjustment..... | 93 | +| 8.2.3.1 | Definition and applicability..... | 93 | +| 8.2.3.2 | Minimum Requirement..... | 93 | +| 8.2.3.3 | Test Purpose..... | 93 | +| 8.2.3.4 | Method of test..... | 94 | +| 8.2.3.4.1 | Initial Conditions..... | 94 | +| 8.2.3.4.2 | Procedure..... | 94 | +| 8.2.3.5 | Test Requirement for Normal Mode..... | 95 | +| 8.2.4 | Performance requirements for PUSCH repetition Type A..... | 96 | +| 8.2.4.1 | Definition and applicability..... | 96 | +| 8.2.4.2 | Minimum Requirement..... | 96 | +| 8.2.4.3 | Test Purpose..... | 96 | +| 8.2.4.4 | Method of test..... | 96 | +| 8.2.4.4.1 | Initial Conditions..... | 96 | +| 8.2.4.4.2 | Procedure..... | 96 | +| 8.2.4.5 | Test Requirement..... | 97 | +| 8.3 | Performance requirements for PUCCH..... | 98 | +| 8.3.1 | Performance requirements for PUCCH format 0..... | 98 | +| 8.3.1.1 | Definition and applicability..... | 98 | +| 8.3.1.2 | Minimum Requirement..... | 98 | + +| | | | +|-------------|-------------------------------------------------------------|-----| +| 8.3.1.3 | Test purpose..... | 98 | +| 8.3.1.4 | Method of test..... | 98 | +| 8.3.1.4.1 | Initial conditions..... | 98 | +| 8.3.1.4.2 | Procedure..... | 98 | +| 8.3.1.5 | Test Requirement..... | 99 | +| 8.3.2 | Performance requirements for PUCCH format 1..... | 100 | +| 8.3.2.1 | NACK to ACK detection..... | 100 | +| 8.3.2.1.1 | Definition and applicability..... | 100 | +| 8.3.2.1.2 | Minimum Requirement..... | 100 | +| 8.3.2.1.3 | Test purpose..... | 100 | +| 8.3.2.1.4 | Method of test..... | 100 | +| 8.3.2.1.4.1 | Initial Conditions..... | 100 | +| 8.3.2.1.4.2 | Procedure..... | 100 | +| 8.3.2.1.5 | Test Requirement..... | 101 | +| 8.3.2.2 | ACK missed detection..... | 102 | +| 8.3.2.2.1 | Definition and applicability..... | 102 | +| 8.3.2.2.2 | Minimum Requirement..... | 102 | +| 8.3.2.2.3 | Test purpose..... | 102 | +| 8.3.2.2.4 | Method of test..... | 102 | +| 8.3.2.2.4.1 | Initial Conditions..... | 102 | +| 8.3.2.2.4.2 | Procedure..... | 102 | +| 8.3.2.2.5 | Test Requirement..... | 103 | +| 8.3.3 | Performance requirements for PUCCH format 2..... | 103 | +| 8.3.3.1 | ACK missed detection..... | 103 | +| 8.3.3.1.1 | Definition and applicability..... | 103 | +| 8.3.3.1.2 | Minimum requirements..... | 104 | +| 8.3.3.1.3 | Test purpose..... | 104 | +| 8.3.3.1.4 | Method of test..... | 104 | +| 8.3.3.1.4.1 | Initial Condition..... | 104 | +| 8.3.3.1.4.2 | Procedure..... | 104 | +| 8.3.3.1.5 | Test requirements..... | 105 | +| 8.3.3.2 | UCI BLER performance requirements..... | 105 | +| 8.3.3.2.1 | Definition and applicability..... | 105 | +| 8.3.3.2.2 | Minimum Requirement..... | 105 | +| 8.3.3.2.3 | Test purpose..... | 105 | +| 8.3.3.2.4 | Method of test..... | 105 | +| 8.3.3.2.4.1 | Initial Condition..... | 105 | +| 8.3.3.2.4.2 | Procedure..... | 106 | +| 8.3.3.2.5 | Test requirements..... | 106 | +| 8.3.4 | Performance requirements for PUCCH format 3..... | 107 | +| 8.3.4.1 | Definition and applicability..... | 107 | +| 8.3.4.2 | Minimum requirement..... | 107 | +| 8.3.4.3 | Test purpose..... | 107 | +| 8.3.4.4 | Method of test..... | 107 | +| 8.3.4.4.1 | Initial conditions..... | 107 | +| 8.3.4.4.2 | Procedure..... | 107 | +| 8.3.4.5 | Test requirement..... | 108 | +| 8.3.5 | Performance requirements for PUCCH format 4..... | 109 | +| 8.3.5.1 | Definition and applicability..... | 109 | +| 8.3.5.2 | Minimum requirement..... | 109 | +| 8.3.5.3 | Test purpose..... | 109 | +| 8.3.5.4 | Method of test..... | 109 | +| 8.3.5.4.1 | Initial conditions..... | 109 | +| 8.3.5.4.2 | Procedure..... | 109 | +| 8.3.5.5 | Test requirement..... | 110 | +| 8.3.6 | Performance requirements for multi-slot PUCCH..... | 111 | +| 8.3.6.1 | Performance requirements for multi-slot PUCCH format 1..... | 111 | +| 8.3.6.1.1 | NACK to ACK detection..... | 111 | +| 8.3.6.1.1.1 | Definition and applicability..... | 111 | +| 8.3.6.1.1.2 | Minimum Requirement..... | 111 | +| 8.3.6.1.1.3 | Test purpose..... | 111 | + +| | | | +|---------------|---------------------------------------------------------|-----| +| 8.3.6.1.1.4 | Method of test..... | 111 | +| 8.3.6.1.1.4.1 | Initial conditions..... | 111 | +| 8.3.6.1.1.4.2 | Procedure..... | 111 | +| 8.3.6.1.1.5 | Test Requirement..... | 112 | +| 8.3.6.1.2 | ACK missed detection..... | 112 | +| 8.3.6.1.2.1 | Definition and applicability..... | 112 | +| 8.3.6.1.2.2 | Minimum Requirement..... | 113 | +| 8.3.6.1.2.3 | Test purpose..... | 113 | +| 8.3.6.1.2.4 | Method of test..... | 113 | +| 8.3.6.1.2.4.1 | Initial conditions..... | 113 | +| 8.3.6.1.2.4.2 | Procedure..... | 113 | +| 8.3.6.1.2.5 | Test Requirement..... | 114 | +| 8.4 | Performance requirements for PRACH..... | 115 | +| 8.4.1 | PRACH false alarm probability and missed detection..... | 115 | +| 8.4.1.1 | Definition and applicability..... | 115 | +| 8.4.1.2 | Minimum requirement..... | 115 | +| 8.4.1.3 | Test purpose..... | 115 | +| 8.4.1.4 | Method of test..... | 115 | +| 8.4.1.4.1 | Initial conditions..... | 115 | +| 8.4.1.4.2 | Procedure..... | 115 | +| 8.4.1.5 | Test requirement for Normal Mode..... | 117 | +| 9 | Radiated transmitter characteristics..... | 118 | +| 9.1 | General..... | 118 | +| 9.2 | Radiated transmit power..... | 118 | +| 9.2.1 | Definition and applicability..... | 118 | +| 9.2.2 | Minimum requirement..... | 118 | +| 9.2.3 | Test purpose..... | 118 | +| 9.2.4 | Method of test..... | 118 | +| 9.2.4.1 | Initial conditions..... | 118 | +| 9.2.4.2 | Procedure..... | 119 | +| 9.2.5 | Test requirement..... | 119 | +| 9.3 | OTA SAN output power..... | 119 | +| 9.3.1 | Definition and applicability..... | 119 | +| 9.3.2 | Minimum requirement..... | 119 | +| 9.3.3 | Test purpose..... | 119 | +| 9.3.4 | Method of test..... | 120 | +| 9.3.4.1 | Initial conditions..... | 120 | +| 9.3.4.2 | Procedure..... | 120 | +| 9.3.5 | Test requirement..... | 120 | +| 9.4 | OTA output power dynamics..... | 120 | +| 9.4.1 | General..... | 120 | +| 9.4.2 | OTA RE power control dynamic range..... | 121 | +| 9.4.2.1 | Definition and applicability..... | 121 | +| 9.4.2.2 | Minimum requirement..... | 121 | +| 9.4.2.3 | Method of test..... | 121 | +| 9.4.3 | OTA total power dynamic range..... | 121 | +| 9.4.3.1 | Definition and applicability..... | 121 | +| 9.4.3.2 | Minimum requirement..... | 121 | +| 9.4.3.3 | Test purpose..... | 121 | +| 9.4.3.4 | Method of test..... | 121 | +| 9.4.3.4.1 | Initial conditions..... | 121 | +| 9.4.3.4.2 | Procedure..... | 122 | +| 9.4.3.5 | Test requirement..... | 122 | +| 9.4.3.5.1 | SAN type 1-O ..... | 122 | +| 9.5 | OTA transmit ON/OFF power..... | 123 | +| 9.6 | OTA transmitted signal quality..... | 123 | +| 9.6.1 | General..... | 123 | +| 9.6.2 | OTA frequency error..... | 123 | +| 9.6.2.1 | Definition and applicability..... | 123 | +| 9.6.2.2 | Minimum Requirement..... | 123 | +| 9.6.2.3 | Test purpose..... | 123 | + +| | | | +|-------------|--------------------------------------------------------------|-----| +| 9.6.2.4 | Method of test..... | 123 | +| 9.6.2.4.1 | Initial conditions..... | 123 | +| 9.6.2.5 | Test Requirements..... | 123 | +| 9.6.3 | OTA modulation quality..... | 123 | +| 9.6.3.1 | Definition and applicability..... | 123 | +| 9.6.3.2 | Minimum Requirement..... | 124 | +| 9.6.3.3 | Test purpose..... | 124 | +| 9.6.3.4 | Method of test..... | 124 | +| 9.6.3.4.1 | Initial conditions..... | 124 | +| 9.6.3.4.2 | Procedure..... | 124 | +| 9.6.3.5 | Test requirements..... | 125 | +| 9.6.3.5.1 | SAN type 1-O ..... | 125 | +| 9.7 | OTA unwanted emissions..... | 126 | +| 9.7.1 | General..... | 126 | +| 9.7.2 | OTA occupied bandwidth..... | 126 | +| 9.7.2.1 | General..... | 126 | +| 9.7.2.2 | Minimum requirement..... | 126 | +| 9.7.2.3 | Test purpose..... | 127 | +| 9.7.2.4 | Method of test..... | 127 | +| 9.7.2.4.1 | Initial conditions..... | 127 | +| 9.7.2.4.2 | Procedure..... | 127 | +| 9.7.2.5 | Test requirement..... | 128 | +| 9.7.3 | OTA Adjacent Channel Leakage Power Ratio (ACLR)..... | 128 | +| 9.7.3.1 | Definition and applicability..... | 128 | +| 9.7.3.2 | Minimum requirement..... | 128 | +| 9.7.3.3 | Test purpose..... | 128 | +| 9.7.3.4 | Method of test..... | 128 | +| 9.7.3.4.1 | Initial conditions..... | 128 | +| 9.7.3.4.2 | Procedure..... | 128 | +| 9.7.3.5 | Test requirements..... | 129 | +| 9.7.4 | OTA out-of-band emissions..... | 130 | +| 9.7.4.1 | Definition and applicability..... | 130 | +| 9.7.4.2 | Minimum requirement..... | 130 | +| 9.7.4.3 | Test purpose..... | 130 | +| 9.7.4.4 | Method of test..... | 130 | +| 9.7.4.4.1 | Initial conditions..... | 130 | +| 9.7.4.4.2 | Procedure..... | 130 | +| 9.7.4.5 | Test requirements..... | 131 | +| 9.7.5 | OTA transmitter spurious emissions..... | 131 | +| 9.7.5.1 | General..... | 131 | +| 9.7.5.2 | General OTA transmitter spurious emissions requirements..... | 132 | +| 9.7.5.2.1 | Definition and applicability..... | 132 | +| 9.7.5.2.2 | Minimum requirement..... | 132 | +| 9.7.5.2.3 | Test purpose..... | 132 | +| 9.7.5.2.4 | Method of test..... | 132 | +| 9.7.5.2.4.1 | Initial conditions..... | 132 | +| 9.7.5.2.4.2 | Procedure..... | 132 | +| 9.7.5.2.5 | Test requirement..... | 133 | +| 9.7.5.2.5.1 | Test requirement for SAN type 1-O..... | 133 | +| 9.8 | OTA transmitter intermodulation..... | 133 | +| 10 | Radiated receiver characteristic..... | 133 | +| 10.1 | General..... | 133 | +| 10.2 | OTA sensitivity..... | 134 | +| 10.2.1 | Definition and applicability..... | 134 | +| 10.2.2 | Minimum requirement..... | 135 | +| 10.2.3 | Test Purpose..... | 135 | +| 10.2.4 | Method of test..... | 135 | +| 10.2.4.1 | Initial conditions..... | 135 | +| 10.2.4.2 | Procedure..... | 135 | +| 10.2.5 | Test requirements..... | 136 | +| 10.2.5.1 | General..... | 136 | + +| | | | +|------------|-------------------------------------------------------------------------|-----| +| 10.2.5.2 | Test requirements for SAN type 1-H and SAN type 1-O ..... | 136 | +| 10.3 | OTA reference sensitivity level..... | 136 | +| 10.3.1 | Definition and applicability..... | 136 | +| 10.3.2 | Minimum requirement..... | 136 | +| 10.3.3 | Test Purpose..... | 136 | +| 10.3.4 | Method of test..... | 137 | +| 10.3.4.1 | Initial conditions..... | 137 | +| 10.3.4.2 | Procedure..... | 137 | +| 10.3.5 | Test requirements..... | 137 | +| 10.3.5.1 | General..... | 137 | +| 10.3.5.2 | Test requirements for SAN type 1-O ..... | 137 | +| 10.4 | OTA dynamic range..... | 138 | +| 10.4.1 | Definition and applicability..... | 138 | +| 10.4.2 | Minimum requirement..... | 138 | +| 10.4.3 | Test purpose..... | 138 | +| 10.4.4 | Method of test..... | 139 | +| 10.4.4.1 | Initial conditions..... | 139 | +| 10.4.4.2 | Procedure..... | 139 | +| 10.4.5 | Test requirement..... | 139 | +| 10.4.5.1 | General..... | 139 | +| 10.4.5.2 | Test requirements for SAN type 1-O ..... | 139 | +| 10.5 | OTA in-band selectivity and blocking..... | 140 | +| 10.5.1 | OTA adjacent channel selectivity..... | 140 | +| 10.5.1.1 | Definition and applicability..... | 140 | +| 10.5.1.2 | Minimum requirement..... | 140 | +| 10.5.1.3 | Test purpose..... | 140 | +| 10.5.1.4 | Method of test..... | 140 | +| 10.5.1.4.1 | Initial conditions..... | 140 | +| 10.5.1.4.2 | Procedure..... | 141 | +| 10.5.1.5 | Test requirement..... | 141 | +| 10.5.1.5.1 | General..... | 141 | +| 10.5.1.5.2 | Test requirements for SAN type 1-O ..... | 141 | +| 10.5.2 | OTA in-band blocking..... | 142 | +| 10.6 | OTA out-of-band blocking..... | 142 | +| 10.6.1 | Definition and applicability..... | 142 | +| 10.6.2 | Minimum requirement..... | 142 | +| 10.6.3 | Test purpose..... | 142 | +| 10.6.4 | Method of test..... | 142 | +| 10.6.4.1 | Initial conditions..... | 142 | +| 10.6.4.2 | Procedure..... | 143 | +| 10.6.5 | Test requirements..... | 143 | +| 10.7 | OTA receiver spurious emissions..... | 144 | +| 10.8 | OTA receiver intermodulation..... | 144 | +| 10.9 | OTA in-channel selectivity..... | 144 | +| 10.9.1 | Definition and applicability..... | 144 | +| 10.9.2 | Minimum requirement..... | 144 | +| 10.9.3 | Test purpose..... | 144 | +| 10.9.4 | Method of test..... | 144 | +| 10.9.4.1 | Initial conditions..... | 144 | +| 10.9.4.2 | Procedure..... | 145 | +| 10.9.5 | Test requirement..... | 145 | +| 10.9.5.1 | SAN type 1-O ..... | 145 | +| 11 | Radiated performance requirements..... | 146 | +| 11.1 | General..... | 146 | +| 11.1.1 | Scope and definitions..... | 146 | +| 11.1.2 | OTA demodulation branches..... | 147 | +| 11.1.3 | Applicability rule..... | 147 | +| 11.1.3.1 | General..... | 147 | +| 11.1.3.2 | Applicability of PUSCH performance requirements..... | 147 | +| 11.1.3.2.1 | Applicability of requirements for different subcarrier spacings..... | 147 | +| 11.1.3.2.2 | Applicability of requirements for different channel bandwidths..... | 148 | + +| | | | +|--------------|---------------------------------------------------------------------------|-----| +| 11.1.3.2.3 | Applicability of requirements for different configurations..... | 148 | +| 11.1.3.3 | Applicability of PUCCH performance requirements..... | 148 | +| 11.1.3.3.1 | Applicability of requirements for different formats..... | 148 | +| 11.1.3.3.2 | Applicability of requirements for different subcarrier spacings..... | 148 | +| 11.1.3.3.3 | Applicability of requirements for different channel bandwidths..... | 148 | +| 11.1.3.3.4 | Applicability of requirements for different configurations..... | 148 | +| 11.1.3.3.5 | Applicability of requirements for multi-slot PUCCH..... | 148 | +| 11.1.3.4 | Applicability of PRACH performance requirements..... | 149 | +| 11.1.3.4.1 | Applicability of requirements for different formats..... | 149 | +| 11.1.3.4.2 | Applicability of requirements for different subcarrier spacings..... | 149 | +| 11.1.3.4.3 | Applicability of requirements for different channel bandwidths..... | 149 | +| 11.2 | OTA performance requirements for PUSCH..... | 149 | +| 11.2.1 | Performance requirements for PUSCH with transform precoding disabled..... | 149 | +| 11.2.1.1 | Definition and applicability..... | 149 | +| 11.2.1.2 | Minimum Requirement..... | 149 | +| 11.2.1.3 | Test Purpose..... | 149 | +| 11.2.1.4 | Method of test..... | 149 | +| 11.2.1.4.1 | Initial Conditions..... | 149 | +| 11.2.1.4.2 | Procedure..... | 149 | +| 11.2.1.5 | Test Requirement..... | 150 | +| 11.2.2 | Performance requirements for PUSCH with transform precoding enabled..... | 152 | +| 11.2.2.1 | Definition and applicability..... | 152 | +| 11.2.2.2 | Minimum Requirement..... | 152 | +| 11.2.2.3 | Test Purpose..... | 152 | +| 11.2.2.4 | Method of test..... | 152 | +| 11.2.2.4.1 | Initial Conditions..... | 152 | +| 11.2.2.4.2 | Procedure..... | 152 | +| 11.2.2.5 | Test Requirement..... | 153 | +| 11.2.3 | Performance requirements for UL timing adjustment..... | 155 | +| 11.2.3.1 | Definition and applicability..... | 155 | +| 11.2.3.2 | Minimum Requirement..... | 155 | +| 11.2.3.3 | Test Purpose..... | 155 | +| 11.2.3.4 | Method of test..... | 155 | +| 11.2.3.4.1 | Initial Conditions..... | 155 | +| 11.2.3.4.2 | Procedure..... | 155 | +| 11.2.3.5 | Test Requirement..... | 156 | +| 11.2.4 | Performance requirements for PUSCH repetition Type A..... | 157 | +| 11.2.4.1 | Definition and applicability..... | 157 | +| 11.2.4.2 | Minimum Requirement..... | 158 | +| 11.2.4.3 | Test Purpose..... | 158 | +| 11.2.4.4 | Method of test..... | 158 | +| 11.2.4.4.1 | Initial Conditions..... | 158 | +| 11.2.4.4.2 | Procedure..... | 158 | +| 11.2.4.5 | Test Requirement..... | 159 | +| 11.3 | OTA performance requirements for PUCCH..... | 160 | +| 11.3.1 | Performance requirements for PUCCH format 0..... | 160 | +| 11.3.1.1 | Definition and applicability..... | 160 | +| 11.3.1.2 | Minimum Requirement..... | 160 | +| 11.3.1.3 | Test purpose..... | 160 | +| 11.3.1.4 | Method of test..... | 161 | +| 11.3.1.4.1 | Initial conditions..... | 161 | +| 11.3.1.4.2 | Procedure..... | 161 | +| 11.3.1.5 | Test Requirement..... | 162 | +| 11.3.1.5.1 | Test requirement for SAN type 1-O ..... | 162 | +| 11.3.2 | Performance requirements for PUCCH format 1..... | 162 | +| 11.3.2.1 | NACK to ACK detection..... | 162 | +| 11.3.2.1.1 | Definition and applicability..... | 162 | +| 11.3.2.1.2 | Minimum Requirement..... | 162 | +| 11.3.2.1.3 | Test purpose..... | 163 | +| 11.3.2.1.4 | Method of test..... | 163 | +| 11.3.2.1.4.1 | Initial Conditions..... | 163 | + +| | | | +|----------------|-------------------------------------------------------------|-----| +| 11.3.2.1.4.2 | Procedure..... | 163 | +| 11.3.2.1.5 | Test Requirement..... | 164 | +| 11.3.2.2 | ACK missed detection..... | 164 | +| 11.3.2.2.1 | Definition and applicability..... | 164 | +| 11.3.2.2.2 | Minimum Requirement..... | 165 | +| 11.3.2.2.3 | Test purpose..... | 165 | +| 11.3.2.2.4 | Method of test..... | 165 | +| 11.3.2.2.4.1 | Initial Conditions..... | 165 | +| 11.3.2.2.4.2 | Procedure..... | 165 | +| 11.3.2.2.5 | Test Requirement..... | 166 | +| 11.3.3 | Performance requirements for PUCCH format 2..... | 166 | +| 11.3.3.1 | ACK missed detection performance requirements..... | 166 | +| 11.3.3.1.1 | Definition and applicability..... | 166 | +| 11.3.3.1.2 | Minimum Requirement..... | 167 | +| 11.3.3.1.3 | Test Purpose..... | 167 | +| 11.3.3.1.4 | Method of test..... | 167 | +| 11.3.3.1.4.1 | Initial conditions..... | 167 | +| 11.3.3.1.4.2 | Procedure..... | 167 | +| 11.3.3.1.5 | Test requirement..... | 168 | +| 11.3.3.2 | UCI BLER performance requirements..... | 168 | +| 11.3.3.2.1 | Definition and applicability..... | 168 | +| 11.3.3.2.2 | Minimum Requirement..... | 168 | +| 11.3.3.2.3 | Test Purpose..... | 169 | +| 11.3.3.2.4 | Method of test..... | 169 | +| 11.3.3.2.4.1 | Initial conditions..... | 169 | +| 11.3.3.2.4.2 | Procedure..... | 169 | +| 11.3.3.2.5 | Test requirement..... | 170 | +| 11.3.4 | Performance requirements for PUCCH format 3..... | 170 | +| 11.3.4.1 | Definition and applicability..... | 170 | +| 11.3.4.2 | Minimum requirement..... | 170 | +| 11.3.4.3 | Test purpose..... | 170 | +| 11.3.4.4 | Method of test..... | 170 | +| 11.3.4.4.1 | Initial conditions..... | 170 | +| 11.3.4.4.2 | Procedure..... | 171 | +| 11.3.4.5 | Test requirement..... | 172 | +| 11.3.4.5.1 | Test requirement for SAN type 1-O ..... | 172 | +| 11.3.5 | Performance requirements for PUCCH format 4..... | 172 | +| 11.3.5.1 | Definition and applicability..... | 172 | +| 11.3.5.2 | Minimum requirement..... | 172 | +| 11.3.5.3 | Test purpose..... | 172 | +| 11.3.5.4 | Method of test..... | 172 | +| 11.3.5.4.1 | Initial conditions..... | 172 | +| 11.3.5.4.2 | Procedure..... | 173 | +| 11.3.5.5 | Test requirement..... | 173 | +| 11.3.5.5.1 | Test requirement for SAN type 1-O ..... | 173 | +| 11.3.6 | Performance requirements for multi-slot PUCCH format..... | 174 | +| 11.3.6.1 | Performance requirements for multi-slot PUCCH format 1..... | 174 | +| 11.3.6.1.1 | NACK to ACK detection..... | 174 | +| 11.3.6.1.1.1 | Definition and applicability..... | 174 | +| 11.3.6.1.1.2 | Minimum Requirement..... | 174 | +| 11.3.6.1.1.3 | Test purpose..... | 174 | +| 11.3.6.1.1.4 | Method of test..... | 174 | +| 11.3.6.1.1.4.1 | Initial conditions..... | 174 | +| 11.3.6.1.1.4.2 | Procedure..... | 175 | +| 11.3.6.1.1.5 | Test Requirement..... | 175 | +| 11.3.6.1.2 | ACK missed detection..... | 176 | +| 11.3.6.1.2.1 | Definition and applicability..... | 176 | +| 11.3.6.1.2.2 | Minimum Requirement..... | 176 | +| 11.3.6.1.2.3 | Test purpose..... | 176 | +| 11.3.6.1.2.4 | Method of test..... | 176 | +| 11.3.6.1.2.4.1 | Initial Conditions..... | 176 | + +| | | | +|----------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------|------------| +| 11.3.6.1.2.4.2 | Procedure..... | 176 | +| 11.3.6.1.2.5 | Test Requirement..... | 177 | +| 11.4 | OTA performance requirements for PRACH..... | 178 | +| 11.4.1 | PRACH false alarm probability and missed detection..... | 178 | +| 11.4.1.1 | Definition and applicability..... | 178 | +| 11.4.1.2 | Minimum requirement..... | 178 | +| 11.4.1.3 | Test purpose..... | 179 | +| 11.4.1.4 | Method of test..... | 179 | +| 11.4.1.4.1 | Initial conditions..... | 179 | +| 11.4.1.4.2 | Procedure..... | 179 | +| 11.4.1.5 | Test requirement..... | 180 | +| Annex A (normative): Reference measurement channel..... | | 181 | +| A.1 | Fixed Reference Channels for RF Rx requirement (QPSK, R=1/3)..... | 181 | +| A.2 | Fixed Reference Channels for dynamic range (16QAM, R=2/3)..... | 182 | +| A.3 | Fixed Reference Channels for performance requirements (QPSK, R=308/1024)..... | 183 | +| A.4 | PRACH test preambles..... | 185 | +| Annex B (informative): Environmental requirements for the SAN equipment..... | | 185 | +| B.1 | General..... | 185 | +| B.2 | Normal test environment..... | 185 | +| B.2.1 | Normal test environment for SPRF..... | 185 | +| B.2.2 | Normal test environment for SAN terrestrial equipment..... | 186 | +| B.3 | Extreme test environment..... | 186 | +| B.3.1 | Extreme test environment for SPRF..... | 186 | +| B.3.2 | Extreme test environment for SAN terrestrial equipment..... | 186 | +| B.3.3 | Extreme temperature..... | 187 | +| B.3.4 | Extreme power supply..... | 187 | +| B.4 | Vibration..... | 187 | +| B.5 | Measurement of test environment..... | 188 | +| Annex C (informative): Test tolerances and derivation of test requirements..... | | 188 | +| C.1 | Measurement of transmitter..... | 189 | +| C.2 | Measurement of receiver..... | 190 | +| C.3 | Measurement of performance requirements..... | 191 | +| Annex D (informative): Measurement system set-up..... | | 192 | +| D.1 | SAN type 1-H transmitter..... | 192 | +| D.1.1 | SAN output power, output power dynamics, frequency error, EVM, unwanted emissions for SAN type 1-H..... | 192 | +| D.1.2 | Transmitter intermodulation for SAN type 1-H..... | 193 | +| D.1.3 | Transmitter spurious emissions for SAN type 1-H..... | 193 | +| D.1.4 | Time alignment error for SAN type 1-H ..... | 194 | +| D.2 | SAN type 1-H receiver..... | 195 | +| D.2.1 | Reference sensitivity level for SAN type 1-H..... | 195 | +| D.2.2 | Receiver dynamic range for SAN type 1-H..... | 195 | +| D.2.3 | Receiver adjacent channel selectivity and narrowband blocking for SAN type 1-H..... | 196 | +| D.2.4 | Receiver spurious emissions..... | 196 | +| D.2.5 | Receiver In-channel selectivity for SAN type 1-H..... | 196 | +| D.2.6 | Receiver intermodulation for SAN type 1-H..... | 196 | + +| | | | +|-------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|------------| +| D.3 | SAN type 1-H and type 1-O transmitter..... | 197 | +| D.3.1 | Radiated transmit power, output power, output power dynamics, transmitted signal quality, OTA unwanted emissions, OTA transmitter spurious emissions..... | 197 | +| D.4 | SAN type 1-H and type 1-O receiver..... | 197 | +| D.4.1 | OTA sensitivity and OTA reference sensitivity level..... | 198 | +| D.4.2 | OTA dynamic range, OTA adjacent channel selectivity..... | 198 | +| D.4.3 | OTA out-of-band blocking..... | 199 | +| D.5 | Void..... | 199 | +| D.6 | SAN type 1-H performance requirements..... | 200 | +| D.6.1 | Performance requirements for PUSCH, single user PUCCH, PRACH on single antenna port in multipath fading conditions..... | 200 | +| D.6.2 | Performance requirements for PUSCH and PRACH in static conditions..... | 201 | +| D.6.3 | Performance requirements for UL timing adjustment..... | 202 | +| D.7 | SAN type 1-O performance requirements..... | 202 | +| Annex E (normative): | Characteristic of interfering signal..... | 203 | +| Annex F (normative): | Void 204 | | +| Annex G (normative): | Propagation conditions..... | 204 | +| G.1 | Static propagation condition..... | 204 | +| G.2 | Multi-path fading propagation conditions..... | 204 | +| G.2.1 | Delay profiles..... | 204 | +| G.2.1.1 | Delay profiles for FR1..... | 205 | +| G.2.2 | Combinations of channel model parameters..... | 205 | +| G.2.3 | MIMO channel correlation matrices..... | 205 | +| G.2.3.1 | MIMO correlation matrices using Uniform Linear Array..... | 206 | +| G.2.3.1.1 | Definition of MIMO correlation matrices..... | 206 | +| G.2.3.1.2 | MIMO correlation matrices at high, medium and low level..... | 206 | +| G.3 | Moving propagation conditions..... | 207 | +| Annex H (normative): | In-channel Tx test..... | 208 | +| H.1 | General..... | 208 | +| H.2 | Basic principles..... | 208 | +| H.2.1 | Output signal of the TX under test..... | 208 | +| H.2.2 | Ideal signal..... | 209 | +| H.2.3 | Measurement results..... | 209 | +| H.2.4 | Measurement points..... | 209 | +| H.3 | Pre-FFT minimization process..... | 210 | +| H.4 | Timing of the FFT window..... | 211 | +| H.5 | Resource element TX power..... | 212 | +| H.6 | Post-FFT equalisation..... | 212 | +| H.7 | EVM..... | 213 | +| H.7.0 | General..... | 213 | +| H.7.1 | Averaged EVM (FDD)..... | 214 | +| Annex I (informative): | Change history..... | 215 | + +## 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 Satellite Access Node (SAN) type 1-H and type 1-O. These have been derived from and are consistent with the conducted requirements for SAN type 1-H and radiated requirement for SAN type 1-H and type 1-O in NR SAN specification defined in TS 38.108 [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.108: "Satellite Access Node radio transmission and reception" +- [3] ITU-R Recommendation M.1545, "Measurement uncertainty as it applies to test limits for the terrestrial component of International Mobile Telecommunications-2000" +- [4] ITU-R Recommendation SM.329: "Unwanted emissions in the spurious domain" +- [5] ITU-R Recommendation SM.328: "Spectra and bandwidth of emissions" +- [6] ITU-R Recommendation SM.1541-6: "Unwanted emissions in the out-of-band domain". +- [7] 3GPP TS 38.212: "NR; Multiplexing and channel coding" +- [8] 3GPP TS 38.211: "NR; Physical channels and modulation" +- [9] 3GPP TS 38.214: "NR; Physical layer procedures for data" +- [10] ITU-T Recommendation O.150, "Equipment for the measurement of digital and analogue/digital parameters" +- [11] 3GPP TR 38.901: "Study on channel model for frequencies from 0.5 to 100 GHz" +- [12] 3GPP TS 38.101-5: "NR; User Equipment (UE) radio transmission and reception; Part 5: Satellite access Radio Frequency (RF) and performance requirements" +- [13] 3GPP TR 37.941: "Radio Frequency (RF) conformance testing background for radiated Base Station (BS) requirements" +- [14] IEC 60 068-2-1 (2007): "Environmental testing - Part 2: Tests. Tests A: Cold" +- [15] IEC 60 068-2-2: (2007): "Environmental testing - Part 2: Tests. Tests B: Dry heat" +- [16] IEC 60 068-2-6: (2007): "Environmental testing - Part 2: Tests - Test Fc: Vibration (sinusoidal)" +- [17] 3GPP TR 38.811: "Study on New Radio (NR) to support non-terrestrial networks (Release 15)" +- [18] 3GPP TS 38.141-2: "NR; Base Station (BS) conformance testing Part 2: Radiated conformance testing" + +- [19] IEC 60721-3-3: "Classification of environmental conditions –Part 3-3: Classification of groups of environmental parameters and their severities – Stationary use at weatherprotected locations" +- [20] IEC 60721-3-4: "Classification of environmental conditions - Part 3-4: Classification of groups of environmental parameters and their severities - Stationary use at non-weatherprotected locations" +- [21] IEC 60721-1: "Classification of environmental conditions Part 1: Environmental parameters and their severities" + +--- + +## 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]. + +**basic limit:** emissions limit relating to the power supplied by a single transmitter to a single antenna transmission line in ITU-R SM.329 [4] 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*. + +**demodulation branch:** single input of the *SAN receiver* to the demodulation algorithms. + +**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). + +**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 receiver:** composite receiver function of a SAN receiving in an *operating band*. + +**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 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 (SAN):** 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 encompasses 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. | +| $BeW_{\theta}$ | The beam width in $\theta$ | +| $BeW_{\phi}$ | The beam width in $\phi$ | +| $BeW_{\theta,REFSENS}$ | Beamwidth equivalent to the OTA REFSENS RoAoA in the $\theta$ -axis in degrees. Applicable for FR1 only. | +| $BeW_{\phi,REFSENS}$ | Beamwidth equivalent to the OTA REFSENS RoAoA in the $\phi$ -axis in degrees. Applicable for FR1 only. | +| $BW_{Config}$ | Transmission bandwidth configuration , where $BW_{Config} = N_{RB} \times SCS \times 12$ . | +| $BW_{Contiguous}$ | Contiguous transmission bandwidth , i.e. SAN channel bandwidth for single carrier. | +| $BW_{GB,low}$ | The minimum guard band defined in clause 5.3.3 for lowest assigned component carrier. | +| $BW_{GB,high}$ | The minimum guard band defined in clause 5.3.3 for highest assigned component carrier. | +| $BW_{SAN}$ | The SAN transponder bandwidth | +| $BW_{SAN,RF}$ | SAN RF channel bandwidth in MHz | +| $\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_{Global}$ | Global frequency raster granularity. | +| $\Delta f_{max}$ | $f\_offset_{max}$ minus half of the bandwidth of the measuring filter. | +| $\Delta f_{OOB}$ | Maximum offset of the out-of-band boundary from the uplink operating band edge. | +| $\Delta_{minSENS}$ | Difference between conducted reference sensitivity and minSENS. | +| $\Delta_{OTAREFSENS}$ | Difference between conducted reference sensitivity and OTA REFSENS. | +| $\Delta F_{Raster}$ | Channel raster granularity. | +| $EIS_{minSENS}$ | The EIS declared for the minSENS RoAoA . | +| $EIS_{REFSENS}$ | OTA REFSENS EIS value. | +| $F_C$ | RF reference frequency on the channel raster, given in table 5.4.2.2-1. | +| $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_{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 . | +| $GB_{\text{Channel}}$ | Minimum guard band defined in clause 5.3.3. | +| $N_{\text{RB}}$ | Physical resource block number. | +| $N_{\text{REF}}$ | Transmission bandwidth configuration , expressed in resource blocks. | +| $N_{\text{REF-Offs}}$ | NR Absolute Radio Frequency Channel Number (NR-ARFCN). | +| $P_{\text{EIRP,N}}$ | Offset used for calculating $N_{\text{REF}}$ scaling per cell, as calculated in clause 6.1. | +| $P_{\text{max,c,TABC}}$ | EIRP level for channel N. | +| $P_{\text{max,c,TRP}}$ | The maximum carrier output power per TAB connector . | +| $P_{\text{max,c,EIRP}}$ | 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{rated,c,sys}}$ | 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,GEO}}$ | $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,LEO}}$ | 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,TABC}}$ | 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,GEO}}$ | $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,LEO}}$ | The rated carrier output power per TAB connector of the SAN GEO class. | +| $P_{\text{rated,c,TRP}}$ | The rated carrier output power per TAB connector of the SAN LEO class. | +| $P_{\text{rated,t,TABC}}$ | Rated carrier TRP output power declared per RIB. | +| $P_{\text{rated,t,TRP}}$ | The rated total output power declared at TAB connector . | +| $P_{\text{rated,t,sys}}$ | Rated total TRP output power declared per RIB. | +| $P_{\text{REFSENS}}$ | The sum of $P_{\text{rated,t,TABC}}$ for all TAB connectors . | +| $SAN_{\text{Channel}}$ | Conducted Reference Sensitivity power level. | +| $SS_{\text{REF}}$ | SAN channel bandwidth . | +| $TRP_{\text{Estimate}}$ | SS block reference frequency position. | +| $TT_{\text{OTA}}$ | Numerically approximated TRP | +| $\theta$ | Test tolerance for OTA requirements | +| $\phi$ | The angle in the reference coordinate system between the projection of the x/y plane and the radiation vector defined between -90° and 90°. 0° represents the y/z plane. The angle is aligned with the down-tilt angle | +| | The angle in the reference coordinate system between the x-axis and the projection of the radiation vector onto the x/y plane defined between -180° and 180° | + +### 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 | Active Antenna System | +| ACLR | Adjacent Channel Leakage Ratio | +| ACS | Adjacent Channel Selectivity | +| AoA | Angle of Arrival | +| AWGN | Additive White Gaussian Noise | +| BW | Bandwidth | +| CA | Carrier Aggregation | +| CATR | Compact Antenna Test Range | +| 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 | + +| | | +|----------|--------------------------------------------| +| EUT | Equipment Under Test | +| EVM | Error Vector Magnitude | +| FDD | Frequency Division Duplex | +| 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 | +| RF | Radio Frequency | +| RX | Receiver | +| SAN | Satellite Access Node | +| SCS | Sub-Carrier Spacing | +| SSB | Synchronization Signal Block | +| TAB | Transceiver Array Boundary | +| TRP | Total Radiated Power | +| TT | Test Tolerance | +| TX | Transmitter | + +## 4 General test conditions and declarations + +### 4.1 Measurement uncertainties and test requirements + +#### 4.1.1 General + +The requirements of this clause apply to all applicable tests in TS 38.181(the present document), i.e. to all conducted tests defined in FR1 for *SAN type 1-H* and radiated tests defined in FR1 for *SAN type 1-H* and *SAN type 1-O*. The frequency range FR1 is defined in clause 5.1 of TS 38.108 [2]. + +The minimum requirements are given in TS 38.108 [2]. Test Tolerances for the conducted test requirements (TT) and test Tolerances for the radiated test requirements (TTOTA) explicitly stated in the present document are given in annex C of the present document. + +The test tolerances for the radiated test requirements (TTOTA) for SAN were reused from TR 37.941 [13]. Reuse of TR 37.941 [x] TTOTA values for SAN LEO radiated conformance testing is subject to the following conditions: + +- EUT suitability to fit OTA chambers considered in TR 37.941 [13], and +- Environmental test conditions assumed for BS testing in TR 37.941 [13]. + +Reuse of TR 37.941 [13] TTOTA values for SAN GEO radiated conformance testing may not be justified for some products due to too large SAN GEO antenna array dimensions, and required OTA RF chamber size. + +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 radiated 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 | | +| Radiated transmit power | Directional | OTA peak directions set | 5 | +| OTA Satellite Access Node output power | TRP | N/A | See TS 38.141-2 [18], annex I | +| OTA output power dynamics | Directional | OTA peak directions set | 1 | +| OTA modulation quality | Directional | OTA coverage range | 5 | +| OTA frequency error | Directional | OTA coverage range | 1 | +| OTA occupied bandwidth | Directional | OTA coverage range | 1 | +| OTA ACLR | TRP | N/A | See TS 38.141-2 [18], annex I | +| OTA out-of-band emissions | TRP | N/A | See TS 38.141-2 [18], annex I | +| OTA transmitter spurious emission | General requirement | TRP | N/A | +| | | | See TS 38.141-2 [18], annex I | +| NOTE: Directional requirement does not imply one compliance direction only. The directional requirement applies to a single direction at a time. | | | | + +**Table 4.1.1-2: Overview of radiated Rx requirements** + +| Rx requirement | Classification | Applicability levels | Coverage range | Number of conformance directions | +|--------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|----------------------|--------------------|----------------------------------| +| | | FR1 | FR1 | | +| OTA sensitivity | Directional | Minimum EIS | OSDD | 5 | +| OTA reference sensitivity level | Directional | OTA REFSSENS | OTA REFSSENS RoAoA | 5 | +| OTA Dynamic range | Directional | OTA REFSSENS | OTA REFSSENS RoAoA | 1 | +| OTA adjacent channel selectivity | Directional | minSENS | minSENS RoAoA | 1 | +| OTA out-of-band blocking | General requirement | Directional | minSENS | minSENS RoAoA | +| | | Directional | minSENS | minSENS RoAoA | +| OTA in-channel selectivity | Directional | minSENS | minSENS RoAoA | 1 | +| NOTE: Directional requirement does not imply one compliance direction only. The directional requirement applies to a single direction at a time. | | | | | + +## 4.1.2 Acceptable uncertainty of Test System + +### 4.1.2.1 General + +The maximum acceptable uncertainty of the Conducted Test System and OTA Test System are 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 conducted 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 EUT and the Test System. + +For details on measurement uncertainty budget calculation, measurement methodology description (including calibration and measurement stage for each test range), MU budget format and its contributions, refer to TR 37.941 [13], where MU analyses for the BS radiated testing were captured. The maximum OTA Test System uncertainty for FR1 OTA transmitter and receiver tests in tables 4.1.2.2-2 and 4.1.2.3-2 were reused from BS MU budgets in TR 37.941 [13]. Reuse of TR 37.941 [13] MU values for SAN LEO radiated conformance testing is subject to the following conditions: + +- EUT suitability to fit OTA chambers considered in TR 37.941 [13], and +- Environmental test conditions assumed for BS testing in TR 37.941 [13]. + +Reuse of TR 37.941 [13] $TT_{OTA}$ values for SAN GEO radiated conformance testing may not be justified for some products due to too large SAN GEO antenna array dimensions, and required OTA RF chamber size. + +#### 4.1.2.2 Measurement of transmitter + +The maximum conducted Test System uncertainty for conducted transmitter tests minimum requirements is given in table 4.1.2.2-1. And the maximum OTA Test System uncertainty for OTA transmitter tests minimum requirements is given in table 4.1.2.2-2. + +**Table 4.1.2.2-1: Maximum Test System uncertainty for conducted transmitter tests** + +| Clause | Maximum Test System Uncertainty | Derivation of Test System Uncertainty | +|------------------------------------------------------------------------|---------------------------------------------------------------------------------------------|---------------------------------------| +| 6.2 SAN output power | $\pm 0.7$ dB, $f \leq 3$ GHz | | +| 6.3 Output power dynamics | $\pm 0.4$ dB | | +| 6.5.2 Frequency error | $\pm 12$ Hz | | +| 6.5.3 EVM | $\pm 1\%$ | | +| 6.6.2 Occupied bandwidth | 5 MHz, 10 MHz SAN Channel BW: $\pm 100$ kHz
15 MHz, 20 MHz SAN Channel BW: $\pm 300$ kHz | | +| 6.6.3 Adjacent Channel Leakage power Ratio (ACLR) | ACLR
$BW \leq 20$ MHz: $\pm 0.8$ dB | | +| 6.6.4 Out-of-band emissions | $\pm 1.5$ dB, $f \leq 3$ GHz | | +| 6.6.5.5.1.1 Transmitter spurious emissions, Mandatory Requirements | 9 kHz $< f \leq 4$ GHz: $\pm 2.0$ dB
4 GHz $< f \leq 15$ GHz: $\pm 4.0$ dB | | +| 6.6.5.5.1.2 Transmitter spurious emissions, Protection of SAN receiver | $\pm 3.0$ dB | | + +**Table 4.1.2.2-2: Maximum OTA Test System uncertainty for FR1 OTA transmitter tests** + +| Clause | Maximum OTA Test System uncertainty | +|--------------------------------------------------------------------|---------------------------------------------------------------------------------------------| +| 9.2 Radiated transmit power | Normal condition:
$[\pm 1.1]$ dB, $f \leq 3$ GHz | +| 9.3 OTA base station output power | $[\pm 1.4]$ dB, $f \leq 3.0$ GHz | +| 9.4.3 OTA total power dynamic range | $[\pm 0.4]$ dB | +| 9.6.2 OTA frequency error | $[\pm 12]$ Hz | +| 9.6.3 OTA modulation quality | $[\pm 1 \%]$ | +| 9.7.2 OTA occupied bandwidth | $[\pm 100]$ kHz, BWChannel 5 MHz, 10 MHz
$[\pm 300]$ kHz, BWChannel 15 MHz, 20 MHz | +| 9.7.3 OTA ACLR | $f \leq 3.0$ GHz
$[\pm 1]$ dB, $BW \leq 20$ MHz | +| 9.7.4 OTA out-of-band emissions | Absolute power $[\pm 1.8]$ dB, $f \leq 3.0$ GHz | +| 9.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 15$ GHz | +| NOTE: | Test system uncertainty values are applicable for normal condition unless otherwise stated. | + +#### 4.1.2.3 Measurement of receiver + +The maximum conducted Test System uncertainty for conducted receiver tests minimum requirements are given in table 4.1.2.3-1, and the maximum OTA Test System uncertainty for OTA receiver tests minimum requirements are given in table 4.1.2.3-2. + +**Table 4.1.2.3-1: Maximum Test System Uncertainty for conducted 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 | | +| 7.3 Dynamic range | $\pm 0.3$ dB | | +| 7.4.1 Adjacent channel selectivity | $\pm 1.4$ dB, $f \leq 3$ GHz |

Overall system uncertainty comprises three quantities:

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

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

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

f \leq 3 GHz
Wanted signal level \pm 0.7 dB
Interferer signal level \pm 0.7 dB

f \leq 6 GHz
Impact of interferer leakage 0.4 dB

| +| 7.5.5.1 Out-of-band blocking | $f_{\text{wanted}} \leq 3$ GHz
$1\text{MHz} < f_{\text{interferer}} \leq 3$ GHz: $\pm 1.3$ dB
$3$ GHz $< f_{\text{interferer}} \leq 4.2$ GHz: $\pm 1.5$ dB
$4.2\text{GHz} < f_{\text{interferer}} \leq 12.75$ GHz: $\pm 3.2$ dB |

Overall system uncertainty comprises three quantities:

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

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

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

Out of band blocking, using CW interferer:
Wanted signal level:
\pm 0.7 dB up to 3 GHz

Interferer signal level:
\pm 1.0 dB up to 3 GHz
Impact of interferer Broadband noise 0.1 dB

| +| 7.8 In-channel selectivity | $\pm 1.4$ dB, $f \leq 3$ GHz | | +| NOTE: 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. | | | + +**Table 4.1.2.3-2: Maximum OTA Test System uncertainty for FR1 OTA receiver tests** + +| Clause | Maximum OTA Test System uncertainty | +|---------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 10.2 OTA sensitivity | [ $\pm 1.3$ ] dB, $f \leq 3$ GHz | +| 10.3 OTA reference sensitivity level | [ $\pm 1.3$ ] dB, $f \leq 3$ GHz | +| 10.4 OTA dynamic range | [ $\pm 0.3$ ] dB | +| 10.5.1 OTA adjacent channel selectivity | [ $\pm 1.7$ ] dB, $f \leq 3$ GHz | +| 10.6 OTA out-of-band blocking | $f_{wanted} \leq 3$ GHz:
[ $\pm 2.0$ ] dB, $f_{interferer} \leq 3$ GHz
[ $\pm 2.1$ ] dB, $3$ GHz $< f_{interferer} \leq 6$ GHz
[ $\pm 3.5$ ] dB, $6$ GHz $< f_{interferer} \leq 12.75$ GHz | +| 10.9 OTA in-channel selectivity | [ $\pm 1.7$ ] dB, $f \leq 3$ GHz | +| NOTE: Test system uncertainty values are applicable for normal condition unless otherwise stated. | | + +#### 4.1.2.4 Measurement of performance requirements + +**Table 4.1.2.4-1: Maximum Test System Uncertainty for FR1 conducted 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$ 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{(\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.5$ dB | +| 8 PRACH with single antenna port 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 radiated performance requirements** + +| Clause | Maximum Test System Uncertainty | Derivation of Test System Uncertainty | +|--------------------------------------------------------------------|---------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 11 PUSCH, PUCCH, PRACH with single antenna port and fading channel | $\pm 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{(\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.5$ dB | +| 11 PRACH with single antenna port and AWGN | $\pm 0.3$ dB | Signal-to-noise ratio uncertainty $\pm 0.3$ dB | + +#### 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 [3]. + +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 Requirement reference points + +### 4.2.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 showing radiated and conducted reference points.](84e5b251aa38db522f76f5cc3afcb853_img.jpg) + +The diagram illustrates the architecture of a Satellite Access Node (SAN) for type 1-H. It shows a flow from left to right: 'Non-NTN infrastructure gNB functions' connected to a 'Gateway', which is connected via a 'Feeder link' to the 'NTN Payload RF'. The 'NTN Payload RF' is enclosed in a dashed box and contains a 'Transceiver unit array (TRXUA) 1 to M', a 'Radio Distribution Network (RDN)', and an 'Antenna Array (AA)'. The 'Transceiver unit array' is connected to the 'RDN', which is connected to the 'Antenna Array'. The 'Antenna Array' is part of a 'Composite antenna'. Two reference points are indicated: '#1', '#2', and '#K' are located at the 'Transceiver array boundary' (the interface between the TRXUA and the RDN), and a 'TAB connector' is located at the 'Radiated interface boundary' (the interface between the RDN and the Antenna Array). + +Diagram of Satellite Access Node (SAN) architecture showing radiated and conducted reference points. + +**Figure 4.2.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.2.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.2.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 an 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 encloses these three sub-components, and a vertical dashed line to the right of the AA is labeled 'Radiated interface boundary'.](7d2d1d3870cd224c4430d19334557716_img.jpg) + +Figure 4.2.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 an 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 encloses these three sub-components, and a vertical dashed line to the right of the AA is labeled 'Radiated interface boundary'. + +**Figure 4.2.2-1: Radiated reference points for SAN type 1-O** + +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. + +## 4.3 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 currently defined in Table 4.3-1. + +**Table 4.3-1 SAN classes** + +| SAN Class | Satellite constellation | +|-----------|-----------------------------------------------| +| GEO class | GEO satellite | +| LEO class | LEO 600 km satellite
LEO 1200 km satellite | + +## 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 | Satellite operating bands may be applied regionally. | +| 6.6.4,
9.7.4 | Out-of-band emissions,
OTA out-of-band emissions | For n255 operation in US, Limits in FCC Title 47 apply. | +| 6.6.5,
9.7.5 | Tx spurious emissions,
OTA Tx spurious emissions | For n255 operation in US, Limits in FCC Title 47 apply. | + +## 4.5 SAN configurations + +### 4.5.1 SAN type 1-H 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 SAN type 1-H transmit configurations showing a transceiver unit array connected to measurement equipment and loads at the transceiver array boundary.](98e54d5540b2efe3e24af3cf936bc4ea_img.jpg) + +The diagram illustrates the transmit configuration for SAN type 1-H. 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. 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 ellipses between #2 and #K indicate additional connectors. + +Diagram of SAN type 1-H transmit configurations showing a transceiver unit array connected to measurement equipment and loads at the transceiver array boundary. + +**Figure 4.5.1-1: SAN type 1-H 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 SAN type 1-H 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 SAN type 1-H receive configurations showing measurement equipment and loads connected to the transceiver unit array at the transceiver array boundary.](ca5dc5fde2061d0ca2051ef7840fc842_img.jpg) + +The diagram illustrates the receive configuration for SAN type 1-H. It is similar to the transmit diagram but with different connections. The 'transceiver unit array' is on the left, and the 'transceiver array boundary' is a vertical dashed line. Connectors #1, #2, ..., #K are on this boundary. Connector #1 is connected to a box labeled 'Measurement Equipment', with an arrow pointing from the equipment to the connector. Connectors #2 and #K are each connected to a box labeled 'Load'. Vertical ellipses between #2 and #K indicate additional connectors. An arrow points to connector #K with the label 'Transceiver array boundary connector TAB(n)'. + +Diagram of SAN type 1-H receive configurations showing measurement equipment and loads connected to the transceiver unit array at the transceiver array boundary. + +**Figure 4.5.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.3 SAN type 1-O transmit configurations + +Unless otherwise stated, the radiated transmitter characteristics in clause 9 are specified at RIB, with a full complement of transceiver units for the configuration in normal operating conditions. + +![Diagram of SAN type 1-O transmitter test interfaces showing the internal components of an NR BS and its connection to measurement equipment.](a05e675f8651ae7ccea1d0d68691d1a9_img.jpg) + +The diagram illustrates the internal structure of an NR BS and its connection to measurement equipment for transmit testing. The NR BS is shown as a dashed box containing three main components: a 'Transceiver unit array' on the left, a 'Radio Distribution Network (RDN)' in the center, and an 'Antenna Array (AA)' on the right. The RDN and AA are grouped together as a 'Composite antenna'. A dashed line labeled 'Radiated interface boundary' is positioned to the right of the AA. A large arrow points from the AA, across the boundary, to a 'Measurement equipment' block which is connected to an antenna symbol. + +Diagram of SAN type 1-O transmitter test interfaces showing the internal components of an NR BS and its connection to measurement equipment. + +Figure 4.5.3-1: SAN type 1-O transmitter test interfaces + +### 4.5.4 SAN type 1-O receive configurations + +Unless otherwise stated, the radiated receiver characteristics in clause 10 are specified at RIB, with a full complement of transceiver units for the configuration in normal operating conditions. + +![Diagram of SAN type 1-O receiver test interfaces showing the internal components of an NR BS and its connection to measurement equipment.](80ec3bf791fd8eb41f73a420c2122529_img.jpg) + +The diagram illustrates the internal structure of an NR BS and its connection to measurement equipment for receive testing. The NR BS is shown as a dashed box containing three main components: a 'Transceiver unit array' on the left, a 'Radio Distribution Network (RDN)' in the center, and an 'Antenna Array (AA)' on the right. The RDN and AA are grouped together as a 'Composite antenna'. A large arrow points from a 'Measurement equipment' block (connected to an antenna symbol) on the right, into the AA. The RIB (Radiated Interface Boundary) is implied by the context of the section. + +Diagram of SAN type 1-O receiver test interfaces showing the internal components of an NR BS and its connection to measurement equipment. + +Figure 4.5.4-1: SAN type 1-O receiver test interfaces + +### 4.5.5 Power supply options + +[If the SAN 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.6 Manufacturer declarations + +The following SAN declarations listed in table 4.6-1, when applicable to the SAN under test, are required to be provided by the manufacturer for the conducted requirements testing of the *SAN type 1-H*, and radiated requirements testing of *SAN type 1-H* and *SAN type 1-O*. + +**Table 4.6-1 Manufacturers declarations for *SAN type 1-H* conducted test requirements, and for *SAN type 1-H* and *SAN type 1-O* radiated test requirements** + +| Declaration identifier | Declaration | Description | Applicability (Note 1) | | +|------------------------|-------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------| +| | | | SAN type 1-H (Note 2) | SAN type 1-O | +| D.1 | Coordinate system reference point | Location of coordinated system reference point in reference to an identifiable physical feature of the SAN enclosure. | x | x | +| D.2 | Coordinate system orientation | Orientation of the coordinate system in reference to an identifiable physical feature of the SAN enclosure. | 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 SAN 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 | +| D.4 | Operating bands and frequency ranges |

List of NR operating band(s) supported by the SAN and if applicable, frequency range(s) within the operating band(s) that the SAN can operate in.

Supported bands declared for every beam for SAN type 1-O (D.3), or every TAB connector for SAN type 1-H.

(Note 4)

| c | x | +| D.5 | SAN requirements set | Declaration of one of the NR satellite access node requirement's set as defined for SAN type 1-H, or SAN type 1-O. | c | x | +| D.6 | SAN class | Declared as GEO SAN, or LEO SAN. | c | x | +| D.7 | SAN channel band width and SCS support | SAN supported SCS and channel bandwidth per supported SCS. Declared for each beam for SAN type 1-O (D.3) or each TAB connector for SAN type 1-H, and each operating band (D.4). | c | 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 | +| D.9 | OTA peak directions set | The OTA peak directions set for each beam. Declared for every beam (D.3). | x | x | + +| Declaration identifier | Declaration | Description | Applicability
(Note 1) | | +|------------------------|-------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|---| +| 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 | +| D.11 | Rated beam EIRP ( $P_{\text{rated,c,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 11) | 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 | +| 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 | +| 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 | +| D.15 | Number of carriers at maximum TRP | The number of carriers per operating band the SAN is capable of generating at maximum TRP declared for every beam (D.3). | n/a | x | +| D.16 | Maximum Satellite Access Node RF Bandwidth | Maximum Satellite Access Node RF Bandwidth in the operating band , declared for each supported operating band for each beam for SAN type 1-O, or for each TAB connector for SAN type 1-H (D.4).
(Note 10) | c | x | +| D.17 | Total RF bandwidth ( $BW_{\text{tot}}$ ) | Total RF bandwidth $BW_{\text{tot}}$ of transmitter and receiver, declared per the band combinations (D.42). | c | x | + +| Declaration identifier | Declaration | Description | Applicability (Note 1) | | +|------------------------|------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---| +| | | | | | +| D.18 | Contiguous spectrum operation support | Ability of SAN to support contiguous frequency distribution of carriers when operating multi-carrier in an operating band.
Declared for each single-band RIB for SAN type 1-O or each single-band connector for SAN type 1-H, for each operating band . | c | x | +| D.19 | OSDD identifier | A unique identifier for the OSDD. | x | x | +| D.20 | OSDD operating band support | Operating band supported by the OSDD, declared for every OSDD (D.19).
(Note 5) | x | x | +| D.21 | OTA sensitivity supported SAN channel bandwidth and SCS | The SAN supported SCS and channel bandwidth per supported SCS by each OSDD. | x | x | +| D.22 | Redirection of receiver target support | Ability to redirect the receiver target related to the OSDD. | x | x | +| D.23 | 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.19).
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 | +| D.24 | Receiver target reference direction
Sensitivity Range of Angle of Arrival | The sensitivity RoAoA associated with the receiver target reference direction (D.26) for each OSDD. | x | x | +| D.25 | 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. | x | x | +| D.26 | Receiver target reference direction | For each OSDD an associated direction inside the receiver target redirection range (D.25).
(Note 7) | x | x | +| D.27 | Conformance test directions sensitivity RoAoA | For each OSDD that includes a receiver target redirection range, four sensitivity RoAoA comprising the conformance test directions (D.28). | x | x | + +| Declaration identifier | Declaration | Description | Applicability
(Note 1) | | +|------------------------|----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|---| +| | | | | | +| D.28 | 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 | +| D.29 | OTA coverage range | Declared as a single range of directions within which selected TX OTA requirements are intended to be met.
(Note 8) | x | x | +| D.30 | OTA coverage range reference direction | The direction describing the reference direction of the OTA converge range (D.29).
(Note 9) | x | x | + +| Declaration identifier | Declaration | Description | Applicability (Note 1) | | +|------------------------|----------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----| +| D.31 | 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 | +| D.32 | The rated carrier OTA SAN power, $P_{\text{rated,c,TRP}}$ | $P_{\text{rated,c,TRP}}$ is declared as TRP OTA power per carrier, declared per supported operating band. (Note 11) | n/a | x | +| D.33 | Rated transmitter TRP, $P_{\text{rated,t,TRP}}$ | Rated total radiated output power. Declared per supported operating band . (Note 11) | n/a | x | +| D.34 | Rated carrier output power ( $P_{\text{rated,c,TABC}}$ ) | Conducted rated carrier output power, per single band connector . Declared per supported operating band , per TAB connector for SAN type 1-H . (Note 11) | c | n/a | +| D.35 | Rated total output power ( $P_{\text{rated,t,TABC}}$ ) | Conducted total rated output power. Declared per supported operating band , per TAB connector for SAN type 1-H . (Note 11) | c | n/a | +| D.36 | Single band connector | List of single-band connector for the supported operating bands (D.4). | c | n/a | +| D.37 | Equivalent connectors | List of TAB connector of SAN type 1-H , which have been declared equivalent. Equivalent connectors imply that the TAB connector of SAN 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 TAB connector of SAN type 1-H are identical and the transmitter unit and/or receiver unit driving TAB connector of SAN type 1-H are of identical design. | c | n/a | +| D.38 | Single-band RIB | List of single-band RIB for the supported operating bands (D.4). | n/a | x | +| D.39 | Single or multiple carrier | SAN capability to operate with a single carrier (only) or multiple carriers. Declared per supported operating band , per RIB for SAN type 1-O or per TAB connector for SAN type 1-H . | c | x | +| D.40 | Maximum number of supported carriers per operating band | Maximum number of supported carriers. Declared per supported operating band , per RIB for SAN type 1-O or per TAB connector for SAN type 1-H . (Note 10) | c | x | +| D.41 | Maximum supported power difference between carriers | Maximum supported power difference between carriers in each supported operating band . Declared per operating band (D.4), per RIB for SAN type 1-O or per TAB connector for SAN type 1-H . | c | x | +| D.42 | Operating band combination support | List of operating bands combinations supported by single-band RIB(s) of SAN type 1-O , or single-band connector(s) of SAN type 1-H . | c | x | + +| Declaration identifier | Declaration | Description | Applicability (Note 1) | | +|------------------------|--------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----| +| D.43 | OTA REFSENS RoAoA | Range of angles of arrival associated with the OTA REFSENS. | n/a | x | +| D.44 | OTA REFSENS receiver target reference direction | Reference direction inside the OTA REFSENS RoAoA (D.43). | n/a | x | +| D.45 | OTA REFSENS conformance test directions | The following four OTA REFSENS conformance test directions shall be declared:
1) The direction determined by the maximum $\phi$ value achievable inside the OTA REFSENS RoAoA, while $\theta$ value being the closest possible to the OTA REFSENS receiver target reference direction.
2) The direction determined by the minimum $\phi$ value achievable inside the OTA REFSENS RoAoA, while $\theta$ value being the closest possible to the OTA REFSENS receiver target reference direction.
3) The direction determined by the maximum $\theta$ value achievable inside the OTA REFSENS RoAoA, while $\phi$ value being the closest possible to the OTA REFSENS receiver target reference direction.
4) The direction determined by the minimum $\theta$ value achievable inside the OTA REFSENS RoAoA, while $\phi$ value being the closest possible to the OTA REFSENS receiver target reference direction. | n/a | x | +| D.46 | 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 | +| D.47 | 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. | c | n/a | +| D.48 | 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. | c | n/a | +| D.49 | $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. | c | n/a | +| D.50 | $P_{\text{rated,c,TABC,GEO}}$ | The rated carrier output power per TAB connector of the SAN GEO class. | c | n/a | +| D.51 | $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. | c | n/a | +| D.52 | $P_{\text{rated,c,TABC,LEO}}$ | The rated carrier output power per TAB connector of the SAN LEO class. | c | n/a | +| D.100 | PUSCH mapping type | Declaration of the supported PUSCH mapping type as specified in TS 38.211 [8], i.e., type A, type B or both. | c | x | +| D.101 | PUCCH format | Declaration of the supported PUCCH format(s) as specified in TS 38.211 [8], i.e., format 0, format 1, format 2, format 3, format 4. | c | x | + +| Declaration identifier | Declaration | Description | Applicability (Note 1) | | +|------------------------|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---| +| | | | c | x | +| D.102 | PRACH format and SCS | Declaration of the supported PRACH format(s) as specified in TS 38.211 [8], i.e., format: 0, 2, B4, C2.
Declaration of the supported SCS(s) per supported PRACH format with short sequence, as specified in TS 38.211 [8], i.e., 15 kHz, 30 kHz or both. | | | +| D.103 | 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. | c | x | +| D.104 | 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. | c | x | +| D.105 | PUCCH multi-slot | Declaration of multi-slot PUCCH support. | c | x | + +NOTE 1: Manufacturer declarations applicable per SAN *requirement set* were marked as "x" or "c". +Manufacturer declarations not applicable per SAN *requirement set* were marked as "n/a". + +NOTE 2: For SAN *type 1-H*, the only radiated declarations are related to EIRP and EIS requirements. For declarations marked as 'c', related conducted declarations apply, and for declarations marked as 'x', related radiated declarations apply. + +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, or single-band TAB connectors. + +NOTE 5: As each identified OSDD has a declared minimum EIS value (D.23), multiple operating band can only be declared if they have the same minimum EIS declaration. + +NOTE 6: If the SAN *type 1-H* or SAN *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: For an OSDD without receiver target redirection range, this is a direction inside the sensitivity RoAoA. + +NOTE 8: *OTA coverage range* is used for conformance testing of such TX OTA requirements as occupied bandwidth, frequency error or EVM. + +NOTE 9: The *OTA coverage reference* direction may be the same as the Reference beam direction pair (D.8) but does not have to be. + +NOTE 10: Parameters for 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 11: If a SAN is capable of 64QAM 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. + +## 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. + +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 for SAN type 1-H and SAN type 1-O** + +| Operating Band characteristics | | $F_{DL\_high} - F_{DL\_low} < 100 \text{ MHz}$ | +|--------------------------------------------------------------------------------------------------------------|--------------------|------------------------------------------------| +| TC signal characteristics | $BW_{channel}$ | 5 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 SAN 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 *SAN RF Bandwidth* supported for contiguous spectrum operation (D.16) shall be used; +- Select the carrier to be tested according to 4.7.2 and place it adjacent to the lower SAN RF Bandwidth edge. Place same signal adjacent to the upper SAN RF Bandwidth edge. +- For transmitter tests, select as many carriers (according to 4.7.2) that the SAN supports within an *operating band* and fit in the rest of the declared maximum *SAN RF Bandwidth* (D.16). Place the carriers adjacent to each other starting from the upper *SAN RF Bandwidth* edge. The nominal channel spacing defined in TS 38.108 [2], clause 5.4.1 shall apply. + +All configured component carriers are transmitted simultaneously in the tests where the transmitter should be ON. + +#### 4.7.3.2 NRTC1 power allocation + +For conducted test: + +Set the power spectral density of each carrier to the same level so that the sum of the carrier powers equals the rated total output power ( $P_{\text{rated,t,TABC}}$ , D.35) according to the manufacturer's declaration in clause 4.6. + +For OTA test: + +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.33). + +## 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. Requirements not included in a *requirement set* is marked not applicable (NA). + +**Table 4.8.2-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 | + +#### 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 SAN capable of single carrier, multi-carrier operation in contiguous spectrum in single band. + +For a SAN declared to be capable of single carrier operation only (D.39), a single carrier (SC) shall be used for testing. + +For conducted test, for a SAN declared to support multi-carrier operation in contiguous spectrum within a single band (D.39) with *single band connector*, the test configurations in the second column of table 4.8.3-1 shall be used for testing. + +For OTA test, for a SAN declared to support multi-carrier operation in contiguous spectrum within a single band (D.39) with *single band RIB*, the test configurations in the second column of 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 channel bandwidth and the smallest supported sub-carrier spacing. + +**Table 4.8.3-1: Test configurations for a *single-band connector*** + +| SAN test case | Contiguous spectrum capable SAN | +|-----------------------------------------------------------------------------------------------------------------------------|----------------------------------------| +| Base station output power | NRTC1 | +| RE Power control dynamic range | Tested with Error Vector Magnitude | +| Total power dynamic range | SC | +| Frequency error | Tested with Error Vector Magnitude | +| Error Vector Magnitude | NRTC1 | +| Occupied bandwidth | SC | +| Adjacent Channel Leakage power Ratio (ACLR) | NRTC1 | +| Out-of-band emissions | NRTC1, SC (Note 1) | +| Transmitter spurious emissions | NRTC1 | +| Reference sensitivity level | SC | +| Dynamic range | SC | +| Adjacent Channel Selectivity (ACS) | NRTC1 | +| Out-of-band blocking | NRTC1 | +| In-channel selectivity | SC | +| Note 1: OOBE SC shall be tested using the widest supported channel bandwidth and the highest supported sub-carrier spacing. | | + +**Table 4.8.3-2: Test configurations for a *single-band RIB*** + +| SAN test case | Contiguous spectrum capable SAN | +|----------------------------------------------------------------------------------------------------------------------------|----------------------------------------| +| Radiated transmit power | NRTC1 | +| OTA base station maximum output power | NRTC1 | +| OTA RE Power control dynamic range | Tested with Error Vector Magnitude | +| OTA total power dynamic range | SC | +| OTA frequency error | Tested with Error Vector Magnitude | +| OTA error Vector Magnitude | NRTC1 | +| OTA Occupied bandwidth | SC | +| OTA ACLR | NRTC1 | +| OTA out-of-band emissions | NRTC1, SC (Note 1) | +| OTA transmitter spurious emissions | NRTC1 | +| OTA sensitivity | SC | +| OTA reference sensitivity level | SC | +| OTA dynamic range | SC | +| OTA adjacent channel selectivity | NRTC1 | +| OTA out-of-band blocking | NRTC1 | +| OTA in-channel selectivity | SC | +| Note 1: OOBE SC shall be tested using the widest supported channel bandwidth and the highest supported subcarrier spacing. | | + +## 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 SAN. 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 SAN RF Bandwidth located at the bottom, middle and top of the supported frequency range in the operating band. These are denoted as BRFBW (bottom), MRFBW (middle) and TRFBW (top). + +Unless otherwise stated, the test shall be performed at BRFBW, MRFBW and TRFBW defined as following: + +- $B_{\text{RFBW}}$ : maximum SAN RF Bandwidth located at the bottom of the supported frequency range in the operating band. +- $M_{\text{RFBW}}$ : maximum SAN RF Bandwidth located in the middle of the supported frequency range in the operating band. +- $T_{\text{RFBW}}$ : maximum SAN RF Bandwidth located at the top of the supported frequency range in the 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 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 SAN FR1 test models needed for *SAN type 1-H* and *SAN type 1-O*. + +### 4.9.2.2 FR1 test models + +The set-up of physical channels for transmitter tests shall be according to one of the NR SAN FR1 test models (NR-SAN-FR1-TM) below. A reference to the applicable test model is made within each test. + +The following general parameters are used by all NR SAN test models: + +- Duration is 1 radio frame (10 ms) for FDD +- The slots are numbered 0 to $10 \times 2^\mu - 1$ where $\mu$ is the numerology corresponding to the subcarrier spacing (15kHz, 30kHz, and 60kHz) +- $N_{\text{RB}}$ is the maximum transmission bandwidth configuration seen in table 5.3.2-1 in TS 38.108 [2]. +- Normal CP +- Virtual resource blocks of localized type + +Common physical channel parameters for all NR SAN FR1 test models are specified in the following tables: table 4.9.2.2-1 for PDCCH, table 4.9.2.2-2 and table 4.9.2.2-3 for PDSCH. Specific physical channel parameters for NR SAN FR1 test models are described in clauses 4.9.2.2.1 to 4.9.2.2.6. + +**Table 4.9.2.2-1: Common physical channel parameters for PDCCH for *SAN type 1-H* and *SAN type 1-O* 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_{\text{RB}} - 3$ | +| Ratio of PDCCH EPRE to DM-RS EPRE | 0 dB | +| Boosting level of control channel | 0 dB | + +**Table 4.9.2.2-2: Common physical channel parameters for PDSCH for SAN type 1-H and SAN type 1-O 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-3: Common physical channel parameters for PDSCH by RNTI for SAN type 1-H and SAN type 1-O 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-SAN-FR1-TM1.1)** + +This model shall be used for tests on: + +- SAN output power +- Unwanted emissions + - Occupied bandwidth + - ACLR + - Operating band unwanted emissions + - Transmitter spurious emissions + +Common physical channel parameters are defined in clause 4.9.2.2. Specific physical channel parameters for NR-SAN-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-SAN-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-SAN-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-SAN-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-SAN-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 [9], 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-SAN-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-SAN-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-SAN-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 3.1 (NR-SAN-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 $x$ and $y$ + +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.5 FR1 test model 3.2 (NR-SAN-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-SAN-FR1-TM3.2 are defined in table 4.9.2.2.5-1. + +**Table 4.9.2.2.5-1: Specific physical channel parameters of NR-SAN-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 | $P$ , where $P$ is determined from table 5.1.2.2.1-1 from TS 38.214 [9], configuration 1 column using $x$ as the size of the bandwidth part and $y$ | +| Locations of 16QAM RBGs which are deboosted | and if $y = 1, 3, \dots$ , | +| 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 $y$ for which EVM is not measured | QPSK | + +#### 4.9.2.2.6 FR1 test model 3.3 (NR-SAN-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-SAN-FR1-TM3.3 are defined in table 4.9.2.2.6-1. + +**Table 4.9.2.2.6-1: Specific physical channel parameters of NR-SAN-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 [9], 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.3 Data content of Physical channels and Signals for NR-SAN-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 [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: + +- for the lowest configured carrier, for the 2nd lowest configured carrier, ..., for the nth configured carrier +- Antenna ports starting with 2000 for PDCCH +- $q = 0$ (single code word) +- Rank 1, single layer +- Antenna port starting with 1000 for PDSCH + +##### 4.9.2.3.1 PDCCH + +- +- PDCCH modulation to be QPSK as described in TS 38.211 [8], 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-SAN-FR1-TM definitions in clause 4.9.2.2 +- Generate this amount of bits from the output of the PN23 sequence generator [10]. 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 [8], 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 [8], clause 7.3.2.3 +- in DM-RS sequence generation in TS 38.211 [8], clause 7.4.1.3 + +- in scrambling sequence generation in TS 38.211 [8], clause 7.3.2.3 +- Perform mapping to REs according to TS 38.211 [8], 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 [10]. 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 TMs with multi-users, the PN sequence can be generated per user ( $n_{\text{RNTI}}$ ). +- NR-SAN-FR1-TMs utilize 1, 2 or 3 user PDSCH transmissions distinguished by . For each NR-SAN-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-SAN-FR1-TM** + +| Test model | $n_{\text{RNTI}}$ | Number of users | +|------------------|-----------------------------------------------------------------------------------------------------------------------------|-----------------| +| NR-SAN-FR1-TM1.1 | 2 for PRBs located in PRB#0-2
0 for remaining PRBs | 2 | +| NR-SAN-FR1-TM1.2 | 0 for boosted PRBs
1 for de-boosted PRBs
2 for PRBs located in PRB#0-2 | 3 | +| NR-SAN-FR1-TM2 | 2 for all PRBs | 1 | +| NR-SAN-FR1-TM3.1 | 2 for PRBs located in PRB#0-2
0 for remaining PRBs | 2 | +| NR-SAN-FR1-TM3.2 | 0 for QPSK PRBs
1 for 16QAM PRBs
2 for PRBs located in PRB#0-2 | 3 | +| NR-SAN-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 [8], clause 7.3.1.1. +- Perform modulation of the scrambled bits with the modulation scheme defined for each user according to TS 38.211 [8], clause 7.3.1.1 +- +- Perform mapping of the complex-valued symbols to layer according to TS 38.211 [8], clause 7.3.1.3. Complex-valued modulation symbols for codeword shall be mapped onto the layers , where is equal to number of layers. +- Perform PDSCH mapping according to TS 38.211 [8] using parameters listed in table 4.9.2.2-2. +- PDSCH resource allocation according to TS 38.214 [9] as following; + - NR-SAN-FR1-TM1.1, NR-SAN-FR1-TM3.1: type 1 for PDSCH with $n_{\text{RNTI}} = 0$ and $n_{\text{RNTI}} = 2$ , + - NR-SAN-FR1-TM1.2, NR-SAN-FR1-TM3.2, NR-SAN-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-SAN-FR1-TM2: type 1 for PDSCH with $n_{\text{RNTI}} = 2$ . +- DM-RS sequence generation according to TS 38.211 [8], 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-2. +- +- +- DM-RS mapping according to TS 38.211 [8], clause 7.4.1.1.2 using parameters listed in table 4.9.2.2-2. + +## 4.10 Void + +## 4.11 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 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.11-1. + +![Figure 4.11-1: Reference coordinate system. A 3D Cartesian coordinate system with x, y, and z axes. A vector is shown originating from the origin. The angle phi (φ) is measured in the x/y plane from the x-axis to the projection of the vector. The angle theta (θ) is measured from the projection of the vector in the x/y plane to the vector itself, with the positive direction being downwards (down-tilt).](46d9e0876283f18b63c5b7ac7b63bd41_img.jpg) + +Figure 4.11-1: Reference coordinate system. A 3D Cartesian coordinate system with x, y, and z axes. A vector is shown originating from the origin. The angle phi (φ) is measured in the x/y plane from the x-axis to the projection of the vector. The angle theta (θ) is measured from the projection of the vector in the x/y plane to the vector itself, with the positive direction being downwards (down-tilt). + +**Figure 4.11-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.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.2 First test method** + +##### **X.4.2.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.2.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.2a 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 operating bands specification, their channel bandwidth configurations, channel spacing and raster, as well as synchronization raster specification, refer to TS 38.108 [2], clause 5 and its relevant clauses. + +--- + +## **6 Conducted transmitter characteristics** + +### **6.1 General** + +#### **6.1.1 SAN type 1-H** + +General test conditions for conducted transmitter tests are given in clause 4, including interpretation of measurement results and configurations for testing. SAN configurations for the tests are defined in clause 4.5. + +If a number of *single-band connectors* have been declared equivalent (D.37), only a representative one is necessary to be tested to demonstrate conformance. + +## 6.2 Satellite Access Node output power + +### 6.2.1 Definition and applicability + +The conducted SAN output power requirements are specified at *single-band connector*. + +The *rated carrier output power* of the *SAN type 1-H* shall be as specified in table 6.2.1-1. + +**Table 6.2.1-1: SAN type 1-H rated output power limits for SAN classes** + +| SAN class | P_{\text{rated,c,sys}} (NOTE) | P_{\text{rated,c,TABC}} (NOTE) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------|----------------------------------------------------| +| SAN GEO | $P_{\text{rated,c,sys,GEO}}$ | $P_{\text{rated,c,TABC,GEO}}$ | +| SAN LEO | $P_{\text{rated,c,sys,LEO}}$ | $P_{\text{rated,c,TABC,LEO}}$ | +| NOTE: $P_{\text{rated,c,sys}}$ or $P_{\text{rated,c,TABC}}$ of SAN shall be based on manufacturer declaration and comply with regulation requirement. | | | + +The output power limit for the respective SAN classes in table 6.2.1-1 shall be compared to the rated output power and the declared SAN class. It is not subject to testing. + +### 6.2.2 Minimum requirement + +The minimum requirement applies per *single-band connector* supporting transmission in the *operating band*. + +The minimum requirement for *SAN type 1-H* is defined in TS 38.108 [2], clause 6.2.2. + +### 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 conditions. + +### 6.2.4 Method of test + +#### 6.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 + +*SAN RF Bandwidth* positions to be tested for multi-carrier: + +- $B_{\text{RFBW}}$ , $M_{\text{RFBW}}$ and $T_{\text{RFBW}}$ for *single-band connector(s)*, see clause 4.9.1. + +#### 6.2.4.2 Procedure + +For *SAN 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. 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)* under test as shown in annex D.1.1 for *SAN type 1-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,TABC}}$ for *SAN type 1-H* (D.34). + +For a connector under test declared to be capable of multi-carrier (D.39) 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_{\max,c,TABC}$ for *SAN type 1-H*) for each carrier at each connector under test. + +## 6.2.5 Test requirement + +For each *single-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 test environments, relative to the manufacturer's declared $P_{\text{rated,c,TABC}}$ for *SAN type 1-H* (D.34): + +**Table 6.2.5-1: Test requirement for conducted SAN output power** + +| SAN type | Normal test environment | +|---------------------|------------------------------| +| SAN type 1-H | $f \leq 3$ GHz: $\pm 2.7$ dB | + +## 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 SAN at *maximum carrier output power* ( $P_{\max,c,TABC}$ ) for a specified reference condition. + +#### 6.3.2.2 Minimum requirement + +The minimum requirement applies per *single-band connector* in the *operating band*. + +The minimum requirement for *SAN type 1-H* is defined in TS 38.108 [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 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. + +NOTE: The upper limit of the total power dynamic range is the OFDM symbol TX power (OSTP) for a SAN 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. + +#### 6.3.3.2 Minimum requirement + +The minimum requirement applies per *single-band connector*. + +The minimum requirement for *SAN type 1-H* is in TS 38.108 [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.3 for *SAN type 1-H*. + +#### 6.3.3.4.2 Procedure + +For *SAN 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. 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 *SAN 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,TABC}}$ for *SAN type 1-H* (D.34). +- 3) For *SAN type 1-H*, set the SAN to transmit a signal according to: + - NR-SAN-FR1-TM3.1 if 64QAM is supported by SAN without power back off, or + - NR-SAN-FR1-TM3.1 with all 64QAM PDSCH PRBs replaced by 16QAM PDSCH PRBs if 64QAM is supported by SAN with power back off, or + - NR-SAN-FR1-TM3.1 with all 64QAM PDSCH PRBs replaced by 16QAM PDSCH PRBs if 64QAM is not supported by SAN but 16QAM is supported by SAN, or + - NR-SAN-FR1-TM3.1 with all 64QAM PDSCH PRBs replaced by QPSK PDSCH PRBs if 64QAM and 16QAM are both not supported by SAN. +- 4) Measure the OFDM symbol TX power (OSTP) as defined in the annex H. +- 5) For *SAN type 1-H*, set the SAN to transmit a signal according to: + - NR-SAN-FR1-TM2 if 64QAM is supported by SAN, or + - NR-SAN-FR1-TM2 with all 64QAM PDSCH PRBs replaced by 16QAM PDSCH PRBs if 64QAM is not supported by SAN and 16QAM is supported; + - NR-SAN-FR1-TM2 with all 64QAM PDSCH PRBs replaced by QPSK PDSCH PRBs if 64QAM and 16QAM are both not supported; +- 6) Measure the OFDM symbol TX power (OSTP) as defined in the annex H. + +### 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: SAN total power dynamic range** + +| SAN 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 | + +NOTE: Additional test requirements for the EVM at the lower limit of the dynamic range are defined in clause 6.5.4. + +## 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 General + +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 SAN 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 *SAN type I-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.108 [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 SAN shall be accurate to within 0.05 ppm + 12 Hz (tolerance) observed over 1 ms. + +## 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 *SAN 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.108 [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: + +- $B_{RFBW}$ , $M_{RFBW}$ and $T_{RFBW}$ in single-band operation, see clause 4.9.1. + +#### 6.5.3.4.2 Procedure + +The minimum requirement is applied to all *TAB connectors*, they may be tested one at a time or multiple *TAB connectors* may be tested in parallel as shown in annex D.1.1 for *SAN type 1-H*. Whichever method is used the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested. + +- 1) For a *TAB connector* declared to be capable of single carrier operation only (D.39), set 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-SAN-FR1-TM3.1 if 64QAM is supported by SAN without power back off, or + - NR-SAN-FR1-TM3.1 at manufacturer's declared rated output power if 64QAM is supported by SAN with power back off, and NR-SAN-FR1-TM3.2 at maximum power, or + - NR-SAN-FR1-TM3.2 if highest modulation order supported by SAN is 16QAM, or + - NR-SAN-FR1-TM3.3 if highest modulation order supported by SAN is QPSK. + +For *TAB connector* declared to be capable of multi-carrier operation, set 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-SAN-FR1-TM3.1 if 64QAM is supported by SAN without power back off, or +- NR-SAN-FR1-TM3.1 at manufacturer's declared rated output power if 64QAM is supported by SAN with power back off, and NR-SAN-FR1-TM3.2 at maximum power, or +- NR-SAN-FR1-TM3.2 if highest modulation order supported by SAN is 16QAM, or + +- NR-SAN-FR1-TM3.3 if highest modulation order supported by SAN is QPSK. + +For NR-SAN-FR1-TM3.1, power back-off shall be applied if it is declared. + +- 2) Measure the EVM and frequency error as defined in annex H. + +### 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 SAN type 1-H carrier** + +| Modulation scheme for PDSCH | Required EVM | +|----------------------------------------------|--------------| +| QPSK | 18.5 % | +| 16QAM | 13.5 % | +| 64QAM (NOTE) | 9 % | +| NOTE: EVM requirement for 64QAM is optional. | | + +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 SAN 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 | 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 6.5.3.5-3 EVM window length for normal CP for NR, 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 6.5.3.5-4 EVM window length for normal CP for NR, 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. + +## 6.6 Unwanted emissions + +### 6.6.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 *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 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 [5]. + +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 requirements + +The minimum requirement for *SAN type 1-H* is defined in TS 38.108 [2] clause 6.6.2. + +#### 6.6.2.3 Test purpose + +The test purpose is to verify that the emission at the *TAB connector* does not occupy an excessive bandwidth for the service to be provided and is, therefore, not likely to create interference to other users of the spectrum beyond undue limits. + +## 6.6.2.4 Method of test + +### 6.6.2.4.1 Initial conditions + +Test environment: Normal; see annex B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1. + +- 1) Connect the measurement device to the *TAB connector* as shown in annex D.1.1 for *SAN type 1-H*. +- 2) For a SAN declared to be capable of single carrier operation (D.39), start transmission according to the applicable test configuration in clause 4.8 using the corresponding test model NR-SAN-FR1-TM1.1 at manufacturer's declared *rated carrier output power per TAB connector* ( $P_{\text{rated,c,TABC}}$ , D.34). + +### 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 | SAN channel bandwidth
$BW_{\text{Channel}}$ (MHz) | | | | +|--------------------------------------|------------------------------------------------------|-----|-----|-----| +| | 5 | 10 | 15 | 20 | +| Span (MHz) | 10 | 20 | 30 | 40 | +| Minimum number of measurement points | 400 | 400 | 400 | 400 | + +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, $P_0$ , (in power units, not decibel units) of all the measurement cells in the measurement span. Compute $P_1$ , the power outside the occupied bandwidth on each side. $P_1$ is half of the total power outside the bandwidth. $P_1$ is half of $(100 \% - (\text{occupied percentage}))$ of $P_0$ . For the occupied percentage of 99 %, $P_1$ is 0.005 times $P_0$ . +- 3) Determine the lowest frequency, $f_1$ , for which the sum of all power in the measurement cells from the beginning of the span to $f_1$ exceeds $P_1$ . +- 4) Determine the highest frequency, $f_2$ , for which the sum of all power in the measurement cells from $f_2$ to the end of the span exceeds $P_1$ . +- 5) Compute the occupied bandwidth as $f_2 - f_1$ . + +### 6.6.2.5 Test requirements + +The occupied bandwidth for each carrier shall be less than the channel bandwidth as defined in TS 38.108 [2], table 5.3.5-1 for *SAN type 1-H*. + +## 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 Satellite Access Node RF Bandwidth or Radio Bandwidth whatever the type of transmitter considered (e.g. single carrier or multi-carrier) and for all transmission modes foreseen by the manufacturer's specification. + +### 6.6.3.2 Minimum requirement + +The minimum requirement applies per *single-band connector* supporting transmission in the *operating band*. + +The minimum requirement for *SAN type 1-H* is defined in TS 38.108 [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. + +*Satellite Access Node 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. + +#### 6.6.3.4.2 Procedure + +For *SAN 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 *SAN 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 *SAN 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. + +- 2) For a connectors declared to be capable of single carrier operation only (D.39), set the representative connectors under test to transmit according to the applicable test configuration in clause 4.8 using the corresponding test models NR-SAN-FR1-TM 1.1 in clause 4.9.2 at *rated carrier output power* $P_{\text{rated,c,TABC}}$ for *SAN type 1-H* (D.34). + +For a connector under test declared to be capable of multi-carrier 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 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) Repeat the test with the channel set-up according to NR-SAN-FR1-TM 1.2 in clause 4.9.2. + +### 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 + +The ACLR is defined with a square filter of bandwidth equal to the transmission bandwidth configuration of the transmitted signal ( $BW_{\text{Config}}$ ) centred on the assigned channel frequency and a filter centred on the adjacent channel frequency according to the tables below. + +The ACLR shall be higher than the value specified in Table 6.6.3.5.2-1/2. + +**Table 6.6.3.5.2-1: SAN ACLR limit for GEO class** + +| SAN channel bandwidth of lowest/highest carrier transmitted $BW_{\text{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 | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|-----------------------------------------------------------------------------|------------| +| 5, 10, 15, 20 | $BW_{\text{Channel}}$ | NR of same BW (NOTE 2) | Square ( $BW_{\text{Config}}$ ) (NOTE 1) | 13.2 | +| | $2 \times BW_{\text{Channel}}$ | NR of same BW (NOTE 2) | Square ( $BW_{\text{Config}}$ ) (NOTE 1) | 13.2 | +| NOTE 1: $BW_{\text{Channel}}$ and $BW_{\text{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_{\text{Config}}$ ). | | | | | + +**Table 6.6.3.5.2-2: SAN ACLR limit for LEO class** + +| SAN channel bandwidth of lowest/highest carrier transmitted $BW_{\text{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 | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|-----------------------------------------------------------------------------|------------| +| 5, 10, 15, 20 | $BW_{\text{Channel}}$ | NR of same BW (NOTE 2) | Square ( $BW_{\text{Config}}$ ) (NOTE 1) | 23.2 | +| | $2 \times BW_{\text{Channel}}$ | NR of same BW (NOTE 2) | Square ( $BW_{\text{Config}}$ ) (NOTE 1) | 23.2 | +| NOTE 1: $BW_{\text{Channel}}$ and $BW_{\text{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_{\text{Config}}$ ). | | | | | + +## 6.6.4 Out-of-band emissions + +### 6.6.4.1 Definition and applicability + +Unless otherwise stated, the out-of-band emission (OOBE) limits for SAN in FR1 are defined from $BW_{\text{SAN}}$ channel edge up to frequencies separated from the $BW_{\text{SAN}}$ channel edge by 200% of the *necessary bandwidth*, where the *necessary bandwidth* is $BW_{\text{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_{\text{SAN}}$ *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. +- $\alpha$ is the SAN class parameter in dB identified to characterize different SAN classes. + +#### 6.6.4.2 Minimum requirement + +The minimum requirement applies per *single-band connector* supporting transmission in the *operating band*. + +The minimum requirement for *SAN type 1-H* is defined in TS 38.108 [2], clause 6.6.4.2. + +#### 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. + +*SAN 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. + +##### 6.6.4.4.2 Procedure + +For *SAN 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. 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* 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. + +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 manufacturer's declared *rated carrier output power per TAB connector* ( $P_{\text{rated,c,TABC}}$ , D.34). Channel set-up shall be according to NR-SAN-FR1-TM 1.1. + +For a connector under test declared to be capable of multi-carrier 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) Step the centre frequency of the measurement filter in contiguous steps and measure the emission within the specified frequency ranges with the specified measurement bandwidth. +- 4) Repeat the test for the remaining test cases, with the channel set-up according to NR-SAN-FR1-TM 1.2. + +#### 6.6.4.5 Test requirements + +For SAN operating in Bands n256, n255, n254, the out-of-band emissions (OOBE) requirements for GEO and LEO classes are defined as described in table 6.6.4.5-1, in line with Annex 5 of ITU recommendation SM.1541-6 [6]. + +**Table 6.6.4.5-1: SAN LEO and GEO out-of-band emission 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 \text{BW}_{\text{SAN}}$ | $0.002 \text{ MHz} \leq f\_offset < 2 \times \text{BW}_{\text{SAN}} + 0.002 \text{ MHz}$ | | 4 kHz | + +NOTE 1: $\text{BW}_{\text{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 [6], Annex 5 OoB domain emission limits for space services. +NOTE 4: =0 dB for GEO class and =3 dB for LEO class. + +## 6.6.5 Transmitter spurious emissions + +### 6.6.5.1 Definition and applicability + +The transmitter spurious emission limits shall apply from 30 MHz to 11 GHz, excluding the *SAN transponder bandwidth* $\text{BW}_{\text{SAN}}$ and the frequency range where the out-of-band emissions apply. + +The lower limit and upper limit are as per ITU-R recommendation SM.329, Table 1: For systems operating within 600 MHz and 5.2 GHz, the lower limit is 30 MHz and the upper limit is the 5th harmonic of the higher frequency. + +The lower limit of 30 MHz can be replaced as per ITU-R SM.329-12: 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 wavelength, do not require spurious domain emission measurements below 0.7 times the waveguide cut-off frequency. + +The requirements shall apply whatever the type of transmitter considered (e.g. single carrier or multi-carrier). It applies for all transmission modes foreseen by the manufacturer's specification. + +The requirements shall apply to SAN that support NR. + +Unless otherwise stated, all requirements are measured as mean power (RMS). + +### 6.6.5.2 Minimum requirement + +The minimum requirement applies per *single-band connector* supporting transmission in the *operating band*. + +The minimum requirement for *SAN type 1-H* is defined in Table 6.6.5.5.1.1-1. + +### 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 the lower frequency edge of the *SAN transponder bandwidth* minus 2 times $\text{BW}_{\text{SAN}}$ , +- T when testing the spurious emissions above the upper frequency edge of the *SAN transponder bandwidth* plus 2 times $\text{BW}_{\text{SAN}}$ ; see clause 4.9.1. + +*SAN RF Bandwidth* positions to be tested for multi-carrier: + +- $B_{RFBW}$ when testing the spurious frequencies below the lower frequency edge of the *SAN transponder bandwidth* minus 2 times $BW_{SAN}$ ; $T_{RFBW}$ when testing the spurious frequencies above the upper frequency edge of the *SAN transponder bandwidth* plus 2 times $BW_{SAN}$ in single-band operation; see clause 4.9.1. + +#### 6.6.5.4.2 Procedure + +For *SAN 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. 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* under test to measurement equipment as shown in annex D.1.1 for *SAN type 1-H*. All connectors not under test shall be terminated with a matched load. +- 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.39), 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,TABC}}$ , D.34). Channel set-up shall be according to NR-FR1-TM 1.1. + +For a connector under test declared to be capable of multi-carrier operation (D.39) 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. + +- 4) Measure the emission at the specified frequencies with specified measurement bandwidth. + +#### 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 Table 6.6.5.5.1.1-1 shall apply. + +**Table 6.6.5.5.1.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 [4], s4.1. | | | | | | | +| NOTE 2: Upper frequency as in ITU-R SM.329 [4], 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 [4], 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.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, and the positive offsets of the interfering signal apply relative to the upper *SAN RF Bandwidth* edge. + +NOTE: In normal operating condition the SAN is configured to transmit and receive at the same time. + +For *SAN type 1-H* if a number of *TAB connectors* have been declared equivalent (D.37), only a representative one is necessary to demonstrate conformance. + +### 7.2 Reference sensitivity level + +#### 7.2.1 Definition and applicability + +The reference sensitivity power level $P_{\text{REFSENS}}$ is the minimum mean power received at the *TAB connector* for *SAN 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 *SAN type 1-H* is in TS 38.108 [2], clause 7.2.2. + +#### 7.2.3 Test purpose + +To verify that for the *SAN type 1-H* receiver 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. + +RF channels to be tested for single carrier: B, M and T; see clause 4.9.1. + +##### 7.2.4.2 Procedure + +The minimum requirement is applied to all connectors under test. + +For *SAN 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 *SAN type 1-H*. +- 2) Set the SAN 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 *SAN type 1-H* set the *TAB connector* to the manufacturers declared *rated carrier output power* ( $P_{\text{rated,c,TABC}}$ , D.34). +- 3) Start the signal generator for the wanted signal to transmit the Fixed Reference Channels for reference sensitivity according to annex A.1. +- 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. + +## 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 and 7.2.5-2 for *SAN type 1-H* in all operating band in FR1. + +**Table 7.2.5-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 | -98.6 | +| 10, 15 | 30 | G-FR1-A1-2 | -98.7 | +| 10, 15 | 60 | G-FR1-A1-3 | -95.8 | +| 20 | 15 | G-FR1-A1-4 | -92.2 | +| 20 | 30 | G-FR1-A1-5 | -92.5 | +| 20 | 60 | G-FR1-A1-6 | -92.6 | + +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.5-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 | -101.7 | +| 10, 15 | 30 | G-FR1-A1-2 | -101.8 | +| 10, 15 | 60 | G-FR1-A1-3 | -98.9 | +| 20 | 15 | G-FR1-A1-4 | -95.3 | +| 20 | 30 | G-FR1-A1-5 | -95.6 | +| 20 | 60 | G-FR1-A1-6 | -95.7 | + +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 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 *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 requirement + +The minimum requirement for *SAN type 1-H* is in TS 38.108 [2], clause 7.3.2. + +### 7.3.3 Test purpose + +To verify that the each *SAN type 1-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 *SAN 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.2 for *SAN type 1-H*. +- 2) Set the signal generator for the wanted signal to transmit as specified in table 7.3.5-1 according to the appropriate SAN class. +- 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 according to the appropriate SAN class. +- 4) Measure the throughput according to annex A.2. + +### 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.5-1 for SAN LEO class. + +**Table 7.3.5-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) / BWConfig | Type of interfering signal | +|------------------------------------|---------------------------------|--------------------------------------|---------------------------------------|------------------------------------------------------------------|-----------------------------------| +| 5 | 15 | G-FR1-A2-1 | -76.1 | -88.2 | AWGN | +| | 30 | G-FR1-A2-2 | -76.8 | | | +| 10 | 15 | G-FR1-A2-1 | -76.1 | -85.0 | AWGN | +| | 30 | G-FR1-A2-2 | -76.8 | | | +| | 60 | G-FR1-A2-3 | -73.8 | | | +| 15 | 15 | G-FR1-A2-1 | -76.1 | -83.2 | AWGN | +| | 30 | G-FR1-A2-2 | -76.8 | | | +| | 60 | G-FR1-A2-3 | -73.8 | | | +| 20 | 15 | G-FR1-A2-4 | -69.9 | -81.9 | AWGN | +| | 30 | G-FR1-A2-5 | -69.9 | | | +| | 60 | G-FR1-A2-6 | -70.2 | | | + +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 sensitivity 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 *TAB connector* for *SAN type 1-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 *SAN type 1-H* is in TS 38.108 [2], clause 7.4.1.2. + +#### 7.4.1.3 Test purpose + +The test purpose is to verify the ability of the SAN 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. + +*SAN RF Bandwidth* positions to be tested for multi-carrier (MC): + +- $M_{\text{RFBW}}$ for *single-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 *SAN 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 *SAN type 1-H*. +- 2) For FDD operation, set the SAN to transmit: + - For single carrier operation set the connector under test to transmit at manufacturers declared *rated carrier output power* ( $P_{\text{rated,c,TABC}}$ , D.34). + - For a connector under test declared to be capable of multi-carrier operation (D.39) 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. + +### 7.4.1.5 Test requirements + +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.5-1 and the frequency offset between the wanted and interfering signal in table 7.4.1.5-2 for ACS. The characteristics of the interfering signal is further specified in annex E. + +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. + +Conducted requirement is defined at the *TAB connector* for *SAN type 1-H*. + +**Table 7.4.1.5-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_{\text{REFSENS}} + 6$ dB
(NOTE 2) | GEO SAN class: -57
LEO SAN 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_{\text{REFSENS}}$ depends on the SAN channel bandwidth as specified in table 7.2.2-1 and 7.2.2-2 in TS 38.108 [2]. | | | + +**Table 7.4.1.5-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 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 *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 requirement + +The minimum requirements for *BS type 1-H* are defined in TS 38.108 [2], clause 7.5.2. + +### 7.5.3 Test purpose + +To verify that for each *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. + +*SAN RF bandwidth* positions to be tested for multi-carrier (MC): $M_{RFBW}$ for *single-band connector(s)*, see clause 4.9.1. + +#### 7.5.4.2 Procedure + +The minimum requirement is applied to all *TAB connectors* under test. For *SAN 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. +- 2) For FDD operation, set the SAN 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. +- 4) Set the signal generator for the interfering signal to transmit at the frequency offset and as specified in table 7.5.5-1. The CW interfering signal shall be swept with a step size of 1 MHz over the range 1 MHz to $(F_{UL\_low} - \Delta f_{OOB})$ MHz and $(F_{UL\_high} + \Delta f_{OOB})$ MHz to 12750 MHz. +- 5) Measure the throughput according to annex A.1. + +### 7.5.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 *SAN type 1-H TAB connector* using the parameters in table 7.5.5-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.5-2. + +Minimum conducted requirement is defined at the *TAB connector* for *SAN type 1-H*. + +**Table 7.5.5-1: Out-of-band blocking requirement for NR** + +| Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | Type of interfering signal | +|-----------------------------------------------------------------------------------|-------------------------------------|----------------------------| +| $P_{\text{REFSENS}} + 6$ dB
(NOTE) | -44 | CW carrier | +| NOTE: For SAN, $P_{\text{REFSENS}}$ depends on the SAN channel bandwidth . | | | + +**Table 7.5.5-2: $\Delta f_{\text{OoB}}$ offset for NR operating bands** + +| SAN type | Operating band characteristics | $\Delta f_{\text{OoB}}$ (MHz) | +|---------------------|----------------------------------------------------|-------------------------------| +| SAN type 1-H | $F_{\text{UL,high}} - F_{\text{UL,low}} < 100$ MHz | 20 | + +## 7.6 Receiver spurious emission + +The requirement is not applicable in this version of the specification. *TAB connectors* shall always support both TX and RX. + +## 7.7 Receiver intermodulation + +The requirement is not applicable in this version of the specification. + +## 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 *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 requirement + +The minimum requirements for *SAN type 1-H* are in TS 38.108 [2], clause 7.8.2. + +### 7.8.3 Test purpose + +The purpose of this test is to verify the SAN 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 *SAN 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-2. +- 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-2. +- 3) Measure the throughput according to annex A.1. + +## 7.8.5 Test 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.8.5-1 for SAN GEO class, in table 7.8.5-2 for SAN LEO class. The characteristics of the interfering signal is further specified in annex E. + +**Table 7.8.5-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 | -96.8 | -92.0 | DFT-s-OFDM NR signal, 15 kHz SCS, 10 RBs | +| 10,15,20 | 15 | G-FR1-A1-1 | -94.9 | -88.1 | DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 5 | 30 | G-FR1-A1-8 | -97.5 | -92.0 | DFT-s-OFDM NR signal, 30 kHz SCS, 5 RBs | +| 10,15,20 | 30 | G-FR1-A1-2 | -95 | -89.0 | DFT-s-OFDM NR signal, 30 kHz SCS, 10 RBs | +| 10,15,20 | 60 | G-FR1-A1-9 | -94.4 | -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.5-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 | -99.9 | -83.1 | DFT-s-OFDM NR signal, 15 kHz SCS, 10 RBs | +| 10,15,20 | 15 | G-FR1-A1-1 | -98 | -79.2 | DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 5 | 30 | G-FR1-A1-8 | -100.6 | -83.1 | DFT-s-OFDM NR signal, 30 kHz SCS, 5 RBs | +| 10,15,20 | 30 | G-FR1-A1-2 | -98.1 | -80.1 | DFT-s-OFDM NR signal, 30 kHz SCS, 10 RBs | +| 10,15,20 | 60 | G-FR1-A1-9 | -97.5 | -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 characteristics + +### 8.1 General + +#### 8.1.1 Scope and definitions + +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 TS 38.108 [2] 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. + +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 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.1.2 Applicability rule + +##### 8.1.2.1 General + +Unless otherwise stated, for a SAN supporting different numbers of *TAB connectors* (for *SAN type 1-H*) (see D.48 in table 4.6-1), the tests with low MIMO correlation level shall apply only for the highest number of supported connectors, and the specific connectors used for testing are based on manufacturer declaration. If performance requirement is not specified for the highest number of supported connectors, the tests shall be done by using performance requirement for the closest number of connectors lower than this highest number of supported connectors. + +##### 8.1.2.2 Applicability of PUSCH performance requirements + +###### 8.1.2.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). + +###### 8.1.2.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 SAN 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.2.2.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. + +#### 8.1.2.3 Applicability of PUCCH performance requirements + +##### 8.1.2.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.101 in table 4.6-1). + +##### 8.1.2.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). + +##### 8.1.2.3.3 Applicability of requirements for different channel bandwidths + +For each subcarrier spacing declared to be supported by the SAN, the test requirements for a specific channel bandwidth shall apply only if the SAN 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.2.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.103 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.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. + +##### 8.1.2.3.5 Applicability of requirements for multi-slot PUCCH + +Unless otherwise stated, multi-slot PUCCH requirement tests shall apply only if the SAN supports it (see D.105 in table 4.6-1). + +#### 8.1.2.4 Applicability of PRACH performance requirements + +##### 8.1.2.4.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.102 in table 4.6-1). + +#### 8.1.2.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.102 in table 4.6-1). + +#### 8.1.2.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.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 SAN is based on the test applicability rules defined in clause 8.1.2. + +#### 8.2.1.2 Minimum Requirement + +The minimum requirement is in TS 38.108 [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. + +##### 8.2.1.4.2 Procedure + +- 1) Connect the SAN tester generating the wanted signal, multipath fading simulators and AWGN generators to all SAN TAB connectors for diversity reception via a combining network as shown in annex D.6 for SAN *type 1-H*. +- 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 SAN 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.1.4.2-2. + +**Table 8.2.1.4.2-2: 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(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 | + +- 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-4 is achieved at the SAN input. +- 6) For each of the reference channels in table 8.2.1.5-1 to 8.2.1.5-4 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-4. + +**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 | 1 | Normal | NTN-TDLA100-200 Low | 70% | G-FR1-A3-1 | pos1 | 3.8 | +| | | Normal | NTN-TDLC5-200 Low | 70% | G-FR1-A3-1 | pos1 | 2.2 | +| | 2 | Normal | NTN-TDLA100-200 Low | 70% | G-FR1-A3-1 | pos1 | -0.1 | +| | | Normal | NTN-TDLC5-200 Low | 70% | G-FR1-A3-1 | pos1 | -0.6 | + +**Table 8.2.1.5-2: 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 | 1 | Normal | NTN-TDLA100-200 Low | 70% | G-FR1-A3-1 | pos1 | 3.9 | +| | | Normal | NTN-TDLC5-200 Low | 70% | G-FR1-A3-1 | pos1 | 2.2 | +| | 2 | Normal | NTN-TDLA100-200 Low | 70% | G-FR1-A3-1 | pos1 | 0.0 | +| | | Normal | NTN-TDLC5-200 Low | 70% | G-FR1-A3-1 | pos1 | -0.6 | + +**Table 8.2.1.5-3: 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 | 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 | 2.0 | +| | 2 | Normal | NTN-TDLA100-200 Low | 70% | G-FR1-A3-3 | pos1 | -0.4 | +| | | Normal | NTN-TDLC5-200 Low | 70% | G-FR1-A3-3 | pos1 | -0.8 | + +**Table 8.2.1.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 | 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.9 | +| | 2 | Normal | NTN-TDLA100-200 Low | 70% | G-FR1-A3-3 | pos1 | -0.4 | +| | | Normal | NTN-TDLC5-200 Low | 70% | G-FR1-A3-3 | pos1 | -0.8 | + +## 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 SAN 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.108 [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 SAN tester generating the wanted signal, multipath fading simulators and AWGN generators to all SAN TAB connectors for diversity reception via a combining network as shown in annex D.6 for SAN *type 1-H*. +- 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 SAN 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 | +| 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 | + +- 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 SAN 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 | 1 | Normal | NTN-TDLA100-200 Low | 70% | G-FR1-A3-5 | pos1 | 4.3 | +| | | Normal | NTN-TDLC5-200 Low | 70% | G-FR1-A3-5 | pos1 | 2.2 | +| | 2 | Normal | NTN-TDLA100-200 Low | 70% | G-FR1-A3-5 | pos1 | 0.1 | +| | | Normal | NTN-TDLC5-200 Low | 70% | G-FR1-A3-5 | pos1 | -0.6 | + +**Table 8.2.2.5-2: 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 | 1 | Normal | NTN-TDLA100-200 Low | 70% | G-FR1-A3-5 | pos1 | 4.3 | +| | | Normal | NTN-TDLC5-200 Low | 70% | G-FR1-A3-5 | pos1 | 2.2 | +| | 2 | Normal | NTN-TDLA100-200 Low | 70% | G-FR1-A3-5 | pos1 | 0.1 | +| | | Normal | NTN-TDLC5-200 Low | 70% | G-FR1-A3-5 | pos1 | -0.6 | + +**Table 8.2.2.5-3: 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 | 1 | Normal | NTN-TDLA100-200 Low | 70% | G-FR1-A3-6 | pos1 | 4.1 | +| | | Normal | NTN-TDLC5-200 Low | 70% | G-FR1-A3-6 | pos1 | 1.9 | +| | 2 | Normal | NTN-TDLA100-200 Low | 70% | G-FR1-A3-6 | pos1 | -0.1 | +| | | Normal | NTN-TDLC5-200 Low | 70% | G-FR1-A3-6 | pos1 | -0.8 | + +**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 | 1 | Normal | NTN-TDLA100-200 Low | 70% | G-FR1-A3-6 | pos1 | 4.1 | +| | | Normal | NTN-TDLC5-200 Low | 70% | G-FR1-A3-6 | pos1 | 1.9 | +| | 2 | Normal | NTN-TDLA100-200 Low | 70% | G-FR1-A3-6 | pos1 | -0.1 | +| | | Normal | NTN-TDLC5-200 Low | 70% | G-FR1-A3-6 | pos1 | -0.8 | + +## 8.2.3 Performance requirements for UL timing adjustment + +### 8.2.3.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. + +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. + +Which specific test(s) are applicable to SAN is based on the test applicability rules defined in clause 8.1.2. + +### 8.2.3.2 Minimum Requirement + +The minimum requirement is in TS 38.108 [2] clause 8.2.3. + +### 8.2.3.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.3.4 Method of test + +#### 8.2.3.4.1 Initial Conditions + +Test environment: Normal, see Annex B.2. + +RF channels to be tested: M; see clause 4.9.1. + +#### 8.2.3.4.2 Procedure + +- 1) Connect the SAN tester generating the wanted signal, multipath fading simulators and AWGN generators to all SAN TAB connectors for diversity reception via a combining network as shown in annex D.6 for SAN *type 1-H*. +- 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 SAN 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 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.3.4.2-2. + +**Table 8.2.3.4.2-2 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(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/30kHz SCS:
12 RB for each UE | +| | Starting PRB index | Moving UE: 0
Stationary UE: 12 for 5MHz CBW/15kHz SCS,
12 for 10MHz CBW/30kHz SCS | +| | Frequency hopping | Disabled | +| SRS resource allocation | Slots in which sounding RS is transmitted (Note2) | For FDD: slot #1 in radio frames | +| | SRS resource allocation | 15 kHz SCS:
$C_{SRS}=5, B_{SRS}=0$ , for 20 RB
30 kHz SCS:
$C_{SRS}=5, B_{SRS}=0$ , for 20 RB | +| NOTE 2: The transmission of SRS is optional. And the transmission comb and SRS periodic 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.3. +- 5) Adjust the equipment so that required SNR specified in Table 8.2.3.5-1 to Table 8.2.3.5-2 is achieved at the SAN input for normal mode. +- 6) For each of the reference channels in Table 8.2.3.5-1 to Table 8.2.3.5-2 applicable for the base station, measure the throughput for normal mode. + +### 8.2.3.5 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.3.5-1 for mapping type A and table 8.2.3.5-2 for mapping type B respectively. + +**Table 8.2.3.5-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 | 1 | Normal | 5 | 15 | Scenario X | G-FR1-A3-2 | 4.7 | +| | | | 10 | 30 | Scenario X | G-FR1-A3-4 | 4.2 | +| | 2 | Normal | 5 | 15 | Scenario X | G-FR1-A3-2 | 0.3 | +| | | | 10 | 30 | Scenario X | G-FR1-A3-4 | 0.1 | + +**Table 8.2.3.5-2: Test requirements for UL timing adjustment with mapping type B** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Channel Bandwidth h [MHz] | SCS [kHz] | Moving propagation conditions and correlation matrix (Annex G) | FRC (Annex A) | SNR [dB] | +|-----------------------|-----------------------|---------------|---------------------------|-----------|----------------------------------------------------------------|---------------|----------| +| 1 | 1 | Normal | 5 | 15 | Scenario X | G-FR1-A3-2 | 4.8 | +| | | | 10 | 30 | Scenario X | G-FR1-A3-4 | 4.2 | +| | 2 | Normal | 5 | 15 | Scenario X | G-FR1-A3-2 | 0.3 | +| | | | 10 | 30 | Scenario X | G-FR1-A3-4 | 0.2 | + +## 8.2.4 Performance requirements for PUSCH repetition Type A + +### 8.2.4.1 Definition and applicability + +The performance requirement of PUSCH with slot aggregation factor configured is determined by a minimum required throughput measured 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 SAN is based on the test applicability rules defined in clause 8.1.2. + +### 8.2.4.2 Minimum Requirement + +The minimum requirement is in TS 38.108 [2] clause 8.2.4. + +### 8.2.4.3 Test Purpose + +The test shall verify the receiver's ability to achieve throughput measured with PUSCH repetition Type A under multipath fading propagation 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 for single carrier: M; see clause 4.9.1. + +#### 8.2.4.4.2 Procedure + +- 1) Connect the SAN tester generating the wanted signal, multipath fading simulators and AWGN generators to all SAN TAB connectors for diversity reception via a combining network as shown in annex D.6 for *SAN type 1-H*. +- 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 SAN 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.4.4.2-2. + +**Table 8.2.4.4.2-2: Test parameters for testing PUSCH repetition Type A** + +| Parameter | | Value | +|--------------------------------------------------------------------------|-------------------------------------------|--------------------------------| +| Transform precoding | | Disabled | +| HARQ | Maximum number of HARQ transmissions | 4 | +| | RV sequence | 0, 3, 0, 3 [Note 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 | +| | 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. | | | + +- 4) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G.2. +- 5) Adjust the equipment so that required SNR specified in table 8.2.4.5-1 to 8.2.4.5-4 is achieved at the SAN input. +- 6) For each of the reference channels in table 8.2.4.5-1 to 8.2.4.5-4 applicable for the base station, measure the throughput. + +## 8.2.4.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.4.5-1 to 8.2.4.5-4. + +**Table 8.2.4.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) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 70% | G-FR1-A3A-1 | pos1 | -4.5 | +| | 2 | Normal | NTN-TDLA100-200 Low | 70% | G-FR1-A3A-1 | pos1 | -7.9 | + +**Table 8.2.4.5-2: 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) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 70% | G-FR1-A3A-1 | pos1 | -4.5 | +| | 2 | Normal | NTN-TDLA100-200 Low | 70% | G-FR1-A3A-1 | pos1 | -7.9 | + +**Table 8.2.4.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) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 70% | G-FR1-A3A-2 | pos1 | -4.5 | +| | 2 | Normal | NTN-TDLA100-200 Low | 70% | G-FR1-A3A-2 | pos1 | -7.9 | + +**Table 8.2.4.5-4: 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) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 70% | G-FR1-A3A-2 | pos1 | -4.5 | +| | 2 | Normal | NTN-TDLA100-200 Low | 70% | G-FR1-A3A-2 | pos1 | -7.9 | + +## 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-5 [12] 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. + +Which specific test(s) are applicable to SAN 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.108 [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 for single carrier: M, see clause 4.9.1. + +### 8.3.1.4.2 Procedure + +- 1) Connect the SAN tester generating the wanted signal, multipath fading simulators and AWGN generators to all SAN TAB connectors for diversity reception via a combining network as shown in annex D.6 for *SAN type 1-H*. +- 2) Adjust the AWGN generator, according to the subcarrier spacing and channel bandwidth defined in table 8.3.1.4.2-1. + +**Table 8.3.1.4.2-1: AWGN power level at the SAN input** + +| Subcarrier 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 [8] 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 for PUCCH format 0** + +| 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 | The largest PRB index – (Number of PRBs – 1) | +| Group and sequence hopping | neither | +| Hopping ID | 0 | +| Initial cyclic shift | 0 | +| First symbol | 12 | +| Number of OFDM symbols | 2 | + +- 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.1.5-1 and table 8.3.1.5-2 is achieved at the SAN 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 rectangular boxes, each containing the text 'ACK', spaced horizontally. To the right of the third box are three dots (ellipsis), indicating a repeating pattern.](91e400bc8bab58306b4d18432e94c9de_img.jpg) + +Figure 8.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', spaced horizontally. To the right of the third box are three dots (ellipsis), indicating a repeating pattern. + +**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, 5 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Propagation conditions and correlation matrix (annex G) | SNR (dB) | +|-----------------------|-----------------------|---------------------------------------------------------|----------| +| 1 | 1 | NTN-TDLA100-200 Low | 9.5 | +| | 2 | NTN-TDLA100-200 Low | 3.9 | + +**Table 8.3.1.5-2: Test requirements for PUCCH format 0, 10 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Propagation conditions and correlation matrix (annex G) | SNR (dB) | +|-----------------------|-----------------------|---------------------------------------------------------|----------| +| 1 | 1 | NTN-TDLA100-200 Low | 11.7 | +| | 2 | NTN-TDLA100-200 Low | 5.4 | + +## 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-5 [12] 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. + +Which specific test(s) are applicable to SAN 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.108 [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 SAN tester generating the wanted signal, multipath fading simulators and AWGN generators to all SAN TAB connectors for diversity reception via a combining network as shown in annex D.6 for *SAN type 1-H*. +- 2) Adjust the AWGN generator, according to the subcarrier spacing 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 SAN input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| 15 kHz | 5 | -83.5 dBm / 4.5 MHz | +| 30 kHz | 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 [8], and the specific test parameters are configured as mentioned in table 8.3.2.1.4.2-2: + +**Table 8.3.2.1.4.2-2: Test parameters for 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 | 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 SAN 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: Test requirements for PUCCH format 1, 5 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (annex G) | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|----------| +| 1 | 1 | Normal | NTN-TDL100-200 Low | 2.8 | +| | 2 | Normal | NTN-TDL100-200 Low | -3.5 | + +**Table 8.3.2.1.5-2: Test requirements for PUCCH format 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) | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 3.6 | +| | 2 | Normal | NTN-TDLA100-200 Low | -2.9 | + +### 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-5 [12] 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. + +Which specific test(s) are applicable to SAN 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.108 [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: M, see clause 4.9.1. + +##### 8.3.2.2.4.2 Procedure + +- 1) Connect the SAN tester generating the wanted signal, multipath fading simulators and AWGN generators to all SAN TAB connectors for diversity reception via a combining network as shown in annex D.6 for *SAN type 1-H*. +- 2) Adjust the AWGN generator, according to the subcarrier spacing 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 SAN input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| 15 kHz | 5 | -83.5 dBm / 4.5 MHz | +| 30 kHz | 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 [8], and the specific test parameters are configured as mentioned in table 8.3.2.2.4.2-2: + +**Table 8.3.2.2.4.2-2: Test parameters for 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 | 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 SAN 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. + +### 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: Test requirements for PUCCH format 1, 5 MHz channel bandwidth, 15 kHz SCS** + +| 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 | 2.1 | +| | 2 | Normal | NTN-TDLA100-200 Low | -4.0 | + +**Table 8.3.2.2.5-2: Test requirements for PUCCH format 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) | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 3.7 | +| | 2 | Normal | NTN-TDLA100-200 Low | -2.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 SAN 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.108 [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 SAN tester generating the wanted signal, multipath fading simulators and AWGN generators to all SAN TAB connectors for diversity reception via a combining network as shown in annex D.6 for *SAN type 1-H*. +- 2) Adjust the AWGN generator, according to the subcarrier spacing and 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 SAN 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 [8], and the specific test parameters are configured as mentioned in table 8.3.3.1.4.2-2: + +**Table 8.3.3.1.4.2-2: Test parameters for PUCCH format 2** + +| Parameter | Value | +|--------------------------------------|--------------| +| Modulation order | QSPK | +| First PRB prior to frequency hopping | 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 SAN 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 a sequence of three rectangular boxes, each containing the text 'ACK', followed by three dots (ellipsis) to the right, indicating a repeating pattern of ACK signals over time.](6116b1a533010c170fc526ec513ba0b8_img.jpg) + +Figure 8.3.3.1.4.2-1: Test signal pattern for PUCCH format 2 demodulation tests. The diagram shows a sequence of three rectangular boxes, each containing the text 'ACK', followed by three dots (ellipsis) to the right, indicating a repeating pattern of ACK signals over time. + +**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: Test requirements for PUCCH format 2, 5 MHz channel bandwidth, 15 kHz SCS** + +| 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 | 15.2 | +| | 2 | Normal | NTN-TDLA100-200 Low | 5.3 | + +**Table 8.3.3.1.5-2: Test requirements for PUCCH format 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) | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 12.6 | +| | 2 | Normal | NTN-TDLA100-200 Low | 5.0 | + +### 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 1 and CSI part 2. + +The transient period as specified in TS 38.101-5 [12] 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 SAN is based on the test applicability rules defined in clause 8.1.2. + +#### 8.3.3.2.2 Minimum Requirement + +The minimum requirement is TS 38.108 [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 SAN tester generating the wanted signal, multipath fading simulators and AWGN generators to all SAN TAB connectors for diversity reception via a combining network as shown in annex D.6 for *SAN type 1-H*. +- 2) Adjust the AWGN generator, according to the subcarrier spacing and 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 SAN 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 [8], and the specific test parameters are configured as mentioned in table 8.3.3.2.4.2-2: + +**Table 8.3.3.2.4.2-2: Test parameters for PUCCH format 2** + +| 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$ | + +- 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 and table 8.3.3.2.5-2 is achieved at the SAN 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, indicating a sequence of such boxes.](079326de347e985e278d2674647d17dc_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, indicating a sequence of such boxes. + +**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: Test requirements for PUCCH format 2, 5 MHz channel bandwidth, 15 kHz SCS** + +| 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 | 6.9 | +| | 2 | Normal | NTN-TDLA100-200 Low | 1.4 | + +**Table 8.3.3.2.5-2: Test requirements for PUCCH format 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) | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 7.0 | +| | 2 | Normal | NTN-TDLA100-200 Low | 1.1 | + +## 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 1 and CSI part 2. + +The transient period as specified in TS 38.101-5 [12] 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. + +Which specific test(s) are applicable to SAN is based on the test applicability rules defined in clause 8.1.2. + +#### 8.3.4.2 Minimum requirement + +The minimum requirement is in TS 38.108 [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 SAN tester generating the wanted signal, multipath fading simulators and AWGN generators to all SAN TAB connectors for diversity reception via a combining network as shown in annex D.6 for *SAN type 1-H*. +- 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 SAN 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 [8]. The specific test parameters are configured as mentioned in table 8.3.4.4.2-2: + +**Table 8.3.4.4.2-2: Test parameters for PUCCH format 3** + +| 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) | +| 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 | + +- 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 and table 8.3.4.5-2 is achieved at the SAN 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 are three dots, indicating a sequence of such boxes.](61d000f6a2a1ff2f0da0b51fb732fafb_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 are three dots, indicating a sequence of such boxes. + +**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: Test requirements for PUCCH format 3, 5 MHz channel bandwidth, 15 kHz SCS** + +| 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 | 7.2 | +| | | | | Additional DM-RS | 7.0 | +| | 2 | Normal | NTN-TDLA100-200 Low | No additional DM-RS | 0.9 | +| | | | | Additional DM-RS | 0.6 | + +**Table 8.3.4.5-2: Test requirements for PUCCH format 3, 10 MHz channel bandwidth, 30 kHz SCS** + +| 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.8 | +| | | | | Additional DM-RS | 9.2 | +| | 2 | Normal | NTN-TDLA100-200 Low | No additional DM-RS | 2.2 | +| | | | | Additional DM-RS | 1.9 | + +## 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 1 and CSI part 2. + +The transient period as specified in TS 38.101-5 [12] 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. + +Which specific test(s) are applicable to SAN is based on the test applicability rules defined in clause 8.1.2. + +### 8.3.5.2 Minimum requirement + +The minimum requirement is in TS 38.108 [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 SAN tester generating the wanted signal, multipath fading simulators and AWGN generators to all SAN TAB connectors for diversity reception via a combining network as shown in annex D.6 for *SAN type 1-H*. +- 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 SAN 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 [8]. The test parameters are configured as mentioned in table 8.3.5.4.2-2: + +**Table 8.3.5.4.2-2: Test parameters for PUCCH format 4** + +| 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 | + +- 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 and table 8.3.5.5-2 is achieved at the SAN 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', representing the transmission of UCI information. These boxes are arranged horizontally with ellipses '...' to the right, indicating a sequence of transmissions over time.](dcc3de7b5b2ad8fbacf8f3c7b5b08aa3_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', representing the transmission of UCI information. These boxes are arranged horizontally with ellipses '...' to the right, indicating a sequence of transmissions over time. + +**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: Test requirements for PUCCH format 4, 5 MHz channel bandwidth, 15 kHz SCS** + +| 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.5 | +| | | | | Additional DM-RS | 9.2 | +| | 2 | Normal | NTN-TDLA100-200 Low | No additional DM-RS | 3.1 | +| | | | | Additional DM-RS | 2.8 | + +**Table 8.3.5.5-2: Test requirements for PUCCH format 4, 10 MHz channel bandwidth, 30 kHz SCS** + +| 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 | 11.1 | +| | | | | Additional DM-RS | 11.1 | +| | 2 | Normal | NTN-TDLA100-200 Low | No additional DM-RS | 4.1 | +| | | | | Additional DM-RS | 3.9 | + +## 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 SAN is based on the test applicability rules defined in clause 8.1.2. + +##### 8.3.6.1.1.2 Minimum Requirement + +The minimum requirement is in TS 38.108 [2] clause 8.3.7. + +##### 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 SAN tester generating the wanted signal, multipath fading simulators and AWGN generators to all SAN TAB connectors for diversity reception via a combining network as shown in annex D.6 for *SAN type 1-H*. +- 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 SAN 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 [8], and the specific test parameters are configured as mentioned in table 8.3.6.1.1.4.2-2: + +**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 and table 8.3.6.1.1.5-2 is achieved at the SAN 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 and table 8.3.6.1.1.5-2. + +**Table 8.3.6.1.1.5-1: Test requirements for multi-slot PUCCH format 1, 5 MHz channel bandwidth, 15 kHz SCS** + +| 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 | -6.0 | + +**Table 8.3.6.1.1.5-2: Test requirements for multi-slot PUCCH format 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) | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 1.8 | +| | 2 | Normal | NTN-TDLA100-200 Low | -5.0 | + +### 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. + +Which specific test(s) are applicable to SAN is based on the test applicability rules defined in clause 8.1.2. + +#### 8.3.6.1.2.2 Minimum Requirement + +The minimum requirement is in TS 38.108 [2] clause 8.3.7. + +#### 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 SAN tester generating the wanted signal, multipath fading simulators and AWGN generators to all SAN TAB connectors for diversity reception via a combining network as shown in annex D.6 for *SAN 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 SAN 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 [8], and the specific test parameters are configured as mentioned in table 8.3.6.1.2.4.2-2: + +**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.6.1.2.5-1 and table 8.3.6.1.2.5-2 is achieved at the SAN 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 and table 8.3.6.1.2.5-2. + +**Table 8.3.6.1.2.5-1: Test requirements for multi-slot PUCCH format 1, 5 MHz channel bandwidth, 15 kHz SCS** + +| 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.3 | +| | 2 | Normal | NTN-TDLA100-200 Low | -7.4 | + +**Table 8.3.6.1.2.5-2: Test requirements for multi-slot PUCCH format 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) | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | -0.6 | +| | 2 | Normal | NTN-TDLA100-200 Low | -7.0 | + +## 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 (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 and NTN-TDLA100-200, 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 NTN-TDLA100-200** + +| PRACH preamble | PRACH SCS (kHz) | Time error tolerance | | +|----------------|-----------------|----------------------|-----------------| +| | | AWGN | NTN-TDLA100-200 | +| 0, 2 | 1.25 | 1.04 us | 1.33 us | +| B4, C2 | 15 | 0.52 us | 0.81 us | +| | 30 | 0.26 us | 0.55 us | + +The test preambles for normal mode are listed in table A.4-1. + +Which specific test(s) are applicable to SAN is based on the test applicability rules defined in clause 8.1.2. + +#### 8.4.1.2 Minimum requirement + +The minimum requirement is in TS 38.108 [2] clause 8.4.1.2. + +#### 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 SAN TAB connectors for diversity reception via a combining network as shown in D.6 for *SAN type 1-H*. +- 2) Adjust the AWGN generator, according to the SCS and channel bandwidth. + +**Table 8.4.1.4.2-1: AWGN power level at the SAN input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|-------------------------|---------------------| +| 15 | 5 | -83.5 dBm / 4.5MHz | +| 30 | 10 | -80.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 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. +- 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 is achieved at the SAN 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 labeled 'Preamble' separated by a gap, followed by three dots indicating a repeating sequence.](2957154f4dc666a6cafb7b4d2d882910_img.jpg) + +Figure 8.4.1.4.2-1: PRACH preamble test pattern. The diagram shows two rectangular boxes labeled 'Preamble' separated by a gap, followed by three dots indicating a repeating sequence. + +**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 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 and format 2 is presented in figure 8.4.1.4.2-2. + +![Figure 8.4.1.4.2-2: Timing offset scheme for PRACH preamble format 0 and format 2. The diagram shows a horizontal timeline with 10 vertical tick marks. A large curved arrow at the top points from the first tick to the last. Below the timeline, a series of 9 smaller curved arrows connect each tick mark to the next, indicating a sequential timing offset increase.](f087d3f5d298b3b1634d13ff17879e41_img.jpg) + +Figure 8.4.1.4.2-2: Timing offset scheme for PRACH preamble format 0 and format 2. The diagram shows a horizontal timeline with 10 vertical tick marks. A large curved arrow at the top points from the first tick to the last. Below the timeline, a series of 9 smaller curved arrows connect each tick mark to the next, indicating a sequential timing offset increase. + +**Figure 8.4.1.4.2-2: Timing offset scheme for PRACH preamble format 0 and format 2** + +The timing offset base value for PRACH preamble format B4 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 B4 and C2 is presented in figure 8.4.1.4.2-3. + +![Figure 8.4.1.4.2-3: Timing offset scheme for PRACH preamble format B4 and C2. The diagram shows a horizontal timeline with eight vertical tick marks. Above the timeline, a long curved arrow points from the first tick mark to the eighth. Below the timeline, seven curved arrows point from the first to the second, second to third, third to fourth, fourth to fifth, fifth to sixth, sixth to seventh, and seventh to eighth tick marks, indicating the timing offset between consecutive preambles.](a0eb8d30ac11ba97b2733c187b89ff22_img.jpg) + +Figure 8.4.1.4.2-3: Timing offset scheme for PRACH preamble format B4 and C2. The diagram shows a horizontal timeline with eight vertical tick marks. Above the timeline, a long curved arrow points from the first tick mark to the eighth. Below the timeline, seven curved arrows point from the first to the second, second to third, third to fourth, fourth to fifth, fifth to sixth, sixth to seventh, and seventh to eighth tick marks, indicating the timing offset between consecutive preambles. + +Figure 8.4.1.4.2-3: Timing offset scheme for PRACH preamble format B4 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) | Time error tolerance | Frequency offset | SNR (dB) | | +|-----------------------|-----------------------|---------------------------------------------------------|----------------------|------------------|----------------|----------------| +| | | | | | Burst format 0 | Burst format 2 | +| 1 | 1 | AWGN | 1.04 us | 0 | -11.7 | -17.1 | +| | | NTN-TDLA100-200 Low | 1.33 us | 200 Hz | 1.3 | -9.1 | +| | 2 | AWGN | 1.04 us | 0 | -14.2 | -19.5 | +| | | NTN-TDLA100-200 Low | 1.33 us | 200 Hz | -6.2 | -14.3 | + +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) | Time error tolerance | Frequency offset | SNR (dB) | | +|-----------------------|-----------------------|---------------------------------------------------------|----------------------|------------------|-----------------|-----------------| +| | | | | | Burst format B4 | Burst format C2 | +| 1 | 1 | AWGN | 0.52 us | 0 | -14.3 | -8.9 | +| | | NTN-TDLA100-200 Low | 0.81 us | 200 Hz | -2.1 | 2.5 | +| | 2 | AWGN | 0.52 us | 0 | -16.5 | -12.2 | +| | | NTN-TDLA100-200 Low | 0.81 us | 200 Hz | -8.4 | -4.2 | + +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) | Time error tolerance | Frequency offset | SNR (dB) | | +|-----------------------|-----------------------|---------------------------------------------------------|----------------------|------------------|-----------------|-----------------| +| | | | | | Burst format B4 | Burst format C2 | +| 1 | 1 | AWGN | 0.52 us | 0 | -14.1 | -8.9 | +| | | NTN-TDLA100-200 Low | 0.81 us | 200 Hz | -3.7 | 0.7 | +| | 2 | AWGN | 0.52 us | 0 | -16.2 | -11.6 | +| | | NTN-TDLA100-200 Low | 0.81 us | 200 Hz | -9.4 | -5.2 | + +## 9 Radiated transmitter characteristics + +### 9.1 General + +General test conditions for transmitter tests are given in clause 4, including interpretation of measurement results and configurations for testing. SAN 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. + +### 9.2 Radiated transmit power + +#### 9.2.1 Definition and applicability + +Radiated transmit power is defined as the EIRP level for a declared beam at a specific *beam peak direction*. + +For each declared beam, the requirement is based on declarations given in clause 4.6 for a beam identifier (D.3), *reference beam direction pair* (D.8), *rated beam EIRP* (D.11) at the beam's reference direction pair, *OTA peak directions set* (D.9), the *beam direction pairs* at the maximum steering directions (D.10) and their associated *rated beam EIRP* and *beam width(s)* for reference *beam direction pair* and maximum steering directions (D.12). + +For a declared beam identifier 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*. + +For each *beam peak direction* associated with a *beam direction pair* within the *OTA peak directions set*, a specific *rated beam EIRP* level may be claimed. Any claimed value shall be met within the accuracy requirement as described below. *Rated beam EIRP* is only required to be declared for the *beam direction pairs* subject to conformance testing as detailed in clause 9.2.4.1. + +NOTE 1: The *OTA peak directions set* for a beam is the complete continuous or discrete set of all *beam direction* for which the EIRP requirement is achieved for the beam. + +NOTE 2: A beam direction pair consists of a beam centre direction and an associated beam peak direction. + +Radiated transmit power is directional requirement applicable to SAN type 1-H and SAN type 1-O. + +#### 9.2.2 Minimum requirement + +Radiated transmit power minimum requirement for *SAN type 1-H* and *SAN type 1-O* is defined in TS 38.108 [2], clause 9.2.2. + +#### 9.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 *SAN type 1-H* and *SAN type 1-O*. + +#### 9.2.4 Method of test + +##### 9.2.4.1 Initial conditions + +Test environment: Test to be performed on environment as declared by the manufacturer. + +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: A representative number of beams shall be chosen to demonstrate the SAN conformance to radiated power requirements. + +#### 9.2.4.2 Procedure + +The test procedure is as follows: + +- 1) Place the satellite on the positioner. +- 2) Align the manufacturer declared coordinate system orientation (D.2) of the satellite with the test system. +- 3) Orient the positioner and satellite in order that the direction to be tested aligns with the test antenna. +- 4) Configure the *beam peak direction* of the satellite according to the declared *beam direction pair*. +- 5) Set the SAN 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 SAN declared to be capable of multi-carrier 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. + +- 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 SAN 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. + +#### 9.2.5 Test requirement + +For each declared conformance *beam direction pair*, the EIRP measurement results in clause 9.2.4.2 shall remain within the values provided in table 9.2.5-1, relative to the manufacturer's declared rated beam EIRP (D.11) value: + +**Table 9.2.5-1: Test requirement for radiated transmit power** + +| | Normal test environment | +|----------------------------|--------------------------------------------| +| SAN type 1-H, SAN type 1-O | $f \leq 3 \text{ GHz}: \pm 3.3 \text{ dB}$ | + +### 9.3 OTA SAN output power + +#### 9.3.1 Definition and applicability + +OTA SAN output power is declared as rated carrier TRP. + +#### 9.3.2 Minimum requirement + +The minimum requirement for *SAN type 1-O* is specified in TS 38.108, clause 9.2. + +#### 9.3.3 Test purpose + +The test purpose is to measure the *maximum carrier TRP* ( $P_{\max,c,TRP}$ ) across the frequency range for all *RIBs*. + +### 9.3.4 Method of test + +#### 9.3.4.1 Initial conditions + +Test environment: Test to be performed on environment as declared by the manufacturer. + +RF channels to be tested for single carrier: B, M, T; see clause 4.9.1. + +*SAN 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. + +Beams to be tested: + +As the requirement is TRP the beam pattern(s) may be set up to optimise the TRP measurement procedure as long as the required TRP level is achieved. + +#### 9.3.4.2 Procedure + +The following procedure for measuring TRP is based on the directional power measurements. + +- 1) Place the satellite on the positioner. +- 2) Align the manufacturer declared coordinate system orientation (D.2) of the satellite with the test system. +- 3) Configure the satellite 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 SAN 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 SAN declared to be capable of multi-carrier 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. +- 5) Orient the positioner and satellite in order that the direction to be tested aligns with the test antenna such that measurements to determine TRP can be performed. +- 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{EIRP}_{\text{p1}} + \text{EIRP}_{\text{p2}}$ . +- 7) Repeat step 6-7 for all directions in the appropriated TRP measurement grid needed for full TRP estimation +- 8) Calculate TRP using the EIRP measurements. + +For 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. + +### 9.3.5 Test requirement + +The final TRP measurement result in clause 9.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; + +## 9.4 OTA output power dynamics + +### 9.4.1 General + +The requirements in clause 9.4 apply during the *transmitter ON period*. Transmit signal quality (as specified in clause 9.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. + +## 9.4.2 OTA RE power control dynamic range + +### 9.4.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 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 + +The minimum requirement for *SAN type 1-O* is in TS 38.108 [2], clause 9.4.2.2. + +### 9.4.2.3 Method of test + +No specific test or test requirements are defined for RE power control dynamic range. The Error Vector Magnitude test, as described in clause 9.6 provides sufficient test coverage for this requirement. + +## 9.4.3 OTA total power dynamic range + +### 9.4.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 BS 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. + +### 9.4.3.2 Minimum requirement + +The minimum requirement for *SAN type 1-O* is in TS 38.108 [2], clause 9.4.3.2. + +### 9.4.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. + +### 9.4.3.4 Method of test + +#### 9.4.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\theta$ , 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). + +#### 9.4.3.4.2 Procedure + +- 1) Place the SAN at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (D.2) of the SAN with the test system. +- 3) Orient the positioner (and SAN) in order that the direction to be tested aligns with the test antenna. +- 4) Configure the beam peak direction of the SAN according to the declared beam direction pair. +- 5) For *SAN type 1-O*, set the SAN to transmit a signal according to the applicable test configuration in clause 4.8 using the corresponding test models: + - NR-SAN-FR1-TM3.1 if 64QAM is supported by SAN without power back off, or + - NR-SAN-FR1-TM3.1 with all 64QAM PDSCH PRBs replaced by 16QAM PDSCH PRBs if 64QAM is supported by SAN with power back off, or + - NR-SAN-FR1-TM3.1 with all 64QAM PDSCH PRBs replaced by 16QAM PDSCH PRBs if 64QAM is not supported by SAN but 16QAM is supported by SAN, or + - NR-SAN-FR1-TM3.1 with all 64QAM PDSCH PRBs replaced by QPSK PDSCH PRBs if 16QAM is not supported by SAN. +- 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 *SAN type 1-O*, set the SAN to transmit a signal according to the applicable test configuration in clause 4.8 using the corresponding test models: + - NR-SAN-FR1-TM2 if 64QAM is supported by SAN, or + - NR-SAN-FR1-TM2 with all 64QAM PDSCH PRBs replaced by 16QAM PDSCH PRBs if 64QAM is not supported by SAN and 16QAM is supported; + - NR-SAN-FR1-TM2 with all 64QAM PDSCH PRBs replaced by QPSK PDSCH PRBs if 64QAM and 16QAM are both not supported; +- 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. + +#### 9.4.3.5 Test requirement + +##### 9.4.3.5.1 SAN 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.3.5.1-1. + +**Table 9.4.3.5.1-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.5 | 10 | N/A | +| 10 | 16.7 | 13.4 | 10 | +| 15 | 18.5 | 15.3 | 12.1 | +| 20 | 19.8 | 16.6 | 13.4 | + +NOTE: Additional test requirements for the Error Vector Magnitude (EVM) at the lower limit of the dynamic range are defined in clause 6.6. + +## 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 General + +The requirements in clause 9.6 apply during the *transmitter ON period*. + +### 9.6.2 OTA frequency error + +#### 9.6.2.1 Definition and applicability + +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.2.2 Minimum Requirement + +The minimum requirement for *SAN type 1-O* is in TS 38.108 [2], clause 9.6.1.2. + +#### 9.6.2.3 Test purpose + +The test purpose is to verify that OTA frequency error is within the limit specified by the minimum requirement. + +#### 9.6.2.4 Method of test + +Requirement is tested together with OTA modulation quality test, as described in clause 9.6.3. + +##### 9.6.2.4.1 Initial conditions + +Directions to be tested: OTA coverage range reference direction (D.30). + +#### 9.6.2.5 Test Requirements + +The modulated carrier frequency of each NR carrier configured by the SAN shall be accurate to within 0.05 ppm + 12 Hz (tolerance) observed over 1 ms. + +## 9.6.3 OTA modulation quality + +### 9.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*. + +### 9.6.3.2 Minimum Requirement + +The minimum requirement for *SAN type 1-O*, is in TS 38.108 [2], clause 9.6.2.2. + +### 9.6.3.3 Test purpose + +The test purpose is to verify that OTA modulation quality is within the limit specified by the minimum requirement. + +### 9.6.3.4 Method of test + +#### 9.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. + +*SAN RF bandwidth* positions to be tested for multi-carrier: + +- $B_{\text{RFBW}}$ and $T_{\text{RFBW}}$ in single-band operation, see clause 4.9.1; + +Directions to be tested: + +- The OTA coverage range reference direction (D.30). +- The OTA coverage range maximum directions (D.31). + +Polarizations to be tested: For dual polarized systems the requirement shall be tested and met for both polarizations. + +#### 9.6.3.4.2 Procedure + +- 1) Place the SAN at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (D.2) of the SAN with the test system. +- 3) Orient the positioner (and SAN) in order that the direction to be tested aligns with the test antenna. +- 4) Configure the beamforming settings of the SAN according to the direction to be tested. +- 5) Set the SAN 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 *SAN type 1-O* declared to be capable of single carrier operation only, set the SAN to transmit a signal according to: + +- NR-SAN-FR1-TM3.1 if 64QAM is supported by SAN without power back off, or +- NR-SAN-FR1-TM3.1 at manufacturer's declared rated output power if 64QAM is supported by SAN with power back off, and NR-SAN-FR1-TM3.2 at maximum power, or +- NR-SAN-FR1-TM3.2 if highest modulation order supported by SAN is 16QAM, or +- NR-SAN-FR1-TM3.3 if highest modulation order supported by SAN is QPSK. + +For *SAN type 1-O* declared to be capable of multi-carrier operation, set the SAN 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: + +- NR-SAN-FR1-TM3.1 if 64QAM is supported by SAN without power back off, or +- NR-SAN-FR1-TM3.1 at manufacturer's declared rated output power if 64QAM is supported by SAN with power back off, and NR-SAN-FR1-TM3.2 at maximum power, or +- NR-SAN-FR1-TM3.2 if highest modulation order supported by SAN is 16QAM, or + +- NR-SAN-FR1-TM3.3 if highest modulation order supported by SAN is QPSK. + +For NR-SAN-FR1-TM3.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 H. + +### 9.6.3.5 Test requirements + +#### 9.6.3.5.1 SAN type 1-O + +For *SAN type 1-O*, the EVM of each NR carrier for different modulation schemes on PDSCH shall be less than the limits in table 9.6.3.5.1-1. + +**Table 9.6.3.5.1-1: EVM requirements for *SAN type 1-O*** + +| Modulation scheme for PDSCH | Required EVM | +|----------------------------------------------|--------------| +| QPSK | 18.5 % | +| 16QAM | 13.5 % | +| 64QAM (NOTE) | 9 % | +| NOTE: EVM requirement for 64QAM is optional. | | + +EVM shall be evaluated for each NR carrier over all allocated resource blocks and downlink slots. Different modulation schemes listed in table 9.6.3.5.1-1 shall be considered for rank 1. + +For NR, 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 9.6.3.5.1-2, 9.6.3.5.1-3, 9.6.3.5.1-4 below specify the EVM window length (*W*) for normal CP for *SAN type 1-O*. + +**Table 9.6.3.5.1-2: 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 9.6.3.5.1-3: 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 9.6.3.5.1-4: EVM window length for normal CP for NR, 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. | | | | + +## 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 [4]. 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 I-O* is specified both in terms of Adjacent Channel Leakage power Ratio (ACLR) and out-of-band emissions (OOBE). + +**Table 9.7.1-1: Void** + +The unwanted emission requirements are applied per cell for all the configurations. Requirements for OTA unwanted emissions are captured using TRP, or *directional requirements* as described per requirement. + +For the OTA TRP measurement procedures, refer to TS 38.141-2 [18], annex I. + +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 [5]. + +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 + +The minimum requirement for *SAN type I-O* is defined in TS 38.108 [2], clause 9.7.2.2. + +#### 9.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. + +### 9.7.2.4 Method of test + +#### 9.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.30). + +Beams to be tested: Declared beam with the highest intended EIRP for the narrowest intended beam corresponding to the smallest $BeW\theta$ , or for the narrowest intended beam corresponding to the smallest $BeW\phi$ (D.3, D.11). + +For SAN 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 NR-SAN-FR1-TM1.1 for *SAN type 1-O* in clause 4.9.2 at manufacturers declared rated carrier EIRP ( $P_{\text{rated,c,EIRP}}$ , D.11). + +#### 9.7.2.4.2 Procedure + +- 1) Place the SAN at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (D.2) of the SAN with the test system. +- 3) Orient the positioner (and SAN) in order that the direction to be tested aligns with the test antenna. +- 4) Configure the beam peak direction of the SAN according to the declared beam direction pair. +- 5) Set the SAN 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 9.7.2.4.2-1. The selected resolution bandwidth (RBW) filter of the analyser shall be 30 kHz or less. + +NOTE: The detection mode of the spectrum analyzer will not have any effect on the result if the statistical properties of the out-of-OBW power are the same as those of the inside-OBW power. Both are expected to have the Rayleigh distribution of the amplitude of Gaussian noise. In any case where the statistics are not the same, though, the detection mode is power responding. There are at least two ways to be power responding. The spectrum analyser can be set to "sample" detection, with its video bandwidth setting at least three times its RBW setting. Or the analyser may be set to respond to the average of the power (root-mean-square of the voltage) across the measurement cell. + +**Table 9.7.2.4.2-1: Span and number of measurement points for OBW measurements for FR1** + +| Bandwidth | SAN channel bandwidth
$BW_{\text{Channel}}$ (MHz) | | | | +|--------------------------------------|------------------------------------------------------|-----|-----|-----| +| | 5 | 10 | 15 | 20 | +| Span (MHz) | 10 | 20 | 30 | 40 | +| Minimum number of measurement points | 400 | 400 | 400 | 400 | + +- 7) Compute the total of the EIRP, $P_0$ , (in power units, not decibel units) of all the measurement cells in the measurement span. Compute $P_1$ , the EIRP outside the occupied bandwidth on each side. $P_1$ is half of the total EIRP outside the bandwidth. $P_1$ is half of $(100 \% - (\text{occupied percentage}))$ of $P_0$ . Measure the EIRP for any two orthogonal polarizations (denoted $p_1$ and $p_2$ ) and calculate total radiated transmit power for particular *beam direction pair* as $EIRP = EIRP_{p1} + EIRP_{p2}$ . +- 8) Determine the lowest frequency, $f_1$ , for which the sum of all EIRP in the measurement cells from the beginning of the span to $f_1$ exceeds $P_1$ . +- 9) Determine the highest frequency, $f_2$ , for which the sum of all EIRP in the measurement cells from the end of the span to $f_2$ exceeds $P_1$ . + +10) Compute the OTA occupied bandwidth as $f_2 - f_1$ . + +### 9.7.2.5 Test requirement + +The OTA occupied bandwidth for each NR carrier shall be less than the channel bandwidth as defined in TS 38.108 [2], table 5.3.5-1. + +## 9.7.3 OTA Adjacent Channel Leakage Power Ratio (ACLR) + +### 9.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. + +For a *RIB* operating in multi-carrier, the OTA ACLR requirements in clause 9.7.3.2 apply to *SAN channel bandwidths* of the outermost carrier. + +### 9.7.3.2 Minimum requirement + +The minimum requirement for *SAN type 1-O* is in TS 38.108 [2], clause 9.7.3.2. + +### 9.7.3.3 Test purpose + +To verify that the OTA adjacent channel leakage ratio requirement shall be met as specified by the minimum requirement. + +### 9.7.3.4 Method of test + +#### 9.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. + +*SAN RF bandwidth* positions to be tested for multi-carrier: $B_{RFBW}$ and $T_{RFBW}$ in single-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 TS 38.141-2 [18], annex I) as long as the required TRP level is achieved. + +#### 9.7.3.4.2 Procedure + +The following procedure for measuring TRP is based on the directional power measurements as described in TS 38.141-2 [18], 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, and 11. + +- 1) Place the SAN at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (D.2) of the SAN with the test system. +- 3) The measurement devices characteristics shall be: + - Measurement filter bandwidth: defined in clause 9.7.3.5. + - Detection mode: true RMS voltage or true power averaging. + - The emission power should be averaged over an appropriate time duration to ensure the measurement is within the measurement uncertainty in table 4.1.2.2-2. + +- 4) For single carrier operation, set the SAN 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 TRP output power* declared per RIB ( $P_{\text{rated,c,TRP}}$ ). + +For SAN declared to be capable of multi-carrier 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. + +- 5) Orient the positioner (and SAN) in order that the direction to be tested aligns with the test antenna such that measurements to determine TRP can be performed (see TS 38.141-2 [18], 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 $TRP_{\text{Estimate}}$ (see TS 38.141-2 [18], annex I). +- 8) Calculate $TRP_{\text{Estimate}}$ 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 9.7.3.5-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 9.7.3.5-1 for *SAN type 1-O*. In multiple carrier case only offset frequencies below the lowest and above the highest carrier frequency used shall be measured. +- 11) Repeat the test with the channel set-up using NR-SAN-FR1-TM1.2. + +### 9.7.3.5 Test requirements + +The OTA ACLR limit specified in table 9.7.3.5-1 for SAN GEO class and 9.7.3.5-2 for SAN LEO class shall apply. + +**Table 9.7.3.5-1: OTA ACLR limit for GEO class** + +| SAN channel bandwidth of lowest/highest carrier transmitted $BW_{\text{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 | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|-----------------------------------------------------------------------------|------------| +| 5, 10, 15, 20 | $BW_{\text{Channel}}$ | NR of same BW (NOTE 2) | Square ( $BW_{\text{Config}}$ ) (NOTE 1) | 13 | +| | $2 \times BW_{\text{Channel}}$ | NR of same BW (NOTE 2) | Square ( $BW_{\text{Config}}$ ) (NOTE 1) | 13 | +| NOTE 1: $BW_{\text{Channel}}$ and $BW_{\text{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_{\text{Config}}$ ). | | | | | + +**Table 9.7.3.5-2: OTA 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 | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|------------------------------------------------------------------------------------|-------------------| +| 5, 10, 15, 20 | $BW_{Channel}$ | NR of same BW (NOTE 2) | Square ( $BW_{Config}$ ) (NOTE 1) | 23 | +| | $2 \times BW_{Channel}$ | NR of same BW (NOTE 2) | Square ( $BW_{Config}$ ) (NOTE 1) | 23 | +| 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}$ ). | | | | | + +## 9.7.4 OTA out-of-band emissions + +### 9.7.4.1 Definition and applicability + +The OTA limits for out-of-band emissions are specified as TRP per RIB unless otherwise stated. + +For a *RIB* operating in multi-carrier, the requirements apply to *SAN channel bandwidths* of the outermost carrier. + +### 9.7.4.2 Minimum requirement + +The minimum requirement for *SAN type 1-O* is defined in TS 38.108 [2], clause 9.7.4.2. + +### 9.7.4.3 Test purpose + +This test measures the emissions of the SAN, close to the assigned channel bandwidth of the wanted signal, while the SAN is in operation. + +### 9.7.4.4 Method of test + +#### 9.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. + +*SAN RF bandwidth* positions to be tested for multi-carrier: $B_{RFBW}$ , $M_{RFBW}$ and $T_{RFBW}$ in single-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 TS 38.141-2 [18], annex I) as long as the required TRP level is achieved. + +#### 9.7.4.4.2 Procedure + +The following procedure for measuring TRP is based on the directional power measurements as described in TS 38.141-2 [18], 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. + +- 1) Place the SAN at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (D.2) of the SAN with the test system. +- 3) The measurement devices characteristics shall be: + - Measurement filter bandwidth: as defined in clause 6.7.4.5. + +- Detection mode: true RMS voltage or true power averaging. + +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 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-2. + +- 4) For single carrier operation, set the SAN 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 TRP output power* declared per RIB ( $P_{\text{rated,c,TRP}}$ ). + +For a SAN declared to be capable of multi-carrier 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. + +- 5) Orient the positioner (and SAN) in order that the direction to be tested aligns with the test antenna such that measurements to determine TRP can be performed (see TS 38.141-2 [18], 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 TS 38.141-2 [18], annex I). +- 8) Calculate $\text{TRP}_{\text{Estimate}}$ using the measurements made in step 6. + +#### 9.7.4.5 Test requirements + +The OTA out-of-band emissions requirement for *SAN type 1-O* shall not exceed each applicable limit in 9.7.4.2 of TS 38.108[2]. + +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. + +For a multi-carrier *single-band RIB* 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. + +### 9.7.5 OTA transmitter spurious emissions + +#### 9.7.5.1 General + +Unless otherwise stated, all requirements are measured as mean power. + +The OTA transmitter spurious emissions limits are specified as TRP per RIB, unless otherwise stated. + +The OTA transmitter spurious emission limits for FR1 shall apply from 30 MHz to 11 GHz, excluding the *SAN transponder bandwidth* $\text{BW}_{\text{SAN}}$ and the frequency range where the out-of-band emissions apply. + +The lower limit and upper limit are as per ITU-R recommendation SM.329, Table 1: For systems operating within 600 MHz and 5.2 GHz, the lower limit is 30 MHz and the upper limit is the 5th harmonic of the higher frequency. + +The lower limit of 30 MHz can be replaced as per ITU-R SM.329-12: 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 wavelength, do not require spurious domain emission measurements below 0.7 times the waveguide cut-off frequency. + +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. + +*SAN type 1-O* requirements consists of OTA transmitter spurious emission requirements based on TRP. + +## 9.7.5.2 General OTA transmitter spurious emissions requirements + +### 9.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. + +### 9.7.5.2.2 Minimum requirement + +The minimum requirement for *SAN type 1-O* is specified in TS 38.108 [2], clause 9.7.5.2.2. + +### 9.7.5.2.3 Test purpose + +The test purpose is to verify if the radiated spurious emissions from the SAN at the RIB are within the specified minimum requirements. + +### 9.7.5.2.4 Method of test + +#### 9.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: + +- B when testing from 30 MHz to the lower frequency edge of the *SAN transponder bandwidth* minus 2 times $BW_{SAN}$ +- T when testing from the upper frequency edge of the *SAN transponder bandwidth* plus 2 times $BW_{SAN}$ to 5th harmonic + +RF bandwidth positions to be tested in single-band multi-carrier operation, see clause 4.9.1: + +- $B_{RFBW}$ when testing from 30 MHz to the lower frequency edge of the *SAN transponder bandwidth* minus 2 times $BW_{SAN}$ +- $T_{RFBW}$ when testing from the upper frequency edge of the *SAN transponder bandwidth* plus 2 times $BW_{SAN}$ to 5th harmonic + +Directions to be tested: As the requirement is TRP the beam pattern(s) may be set up to optimise the TRP measurement procedure (see TS 38.141-2 [18], annex I) as long as the required TRP level is achieved. + +#### 9.7.5.2.4.2 Procedure + +The following procedure for measuring TRP is based on directional power measurements as described in TS 38.141-2 [18], 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. + +- 1) Place the SAN at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (D.2) of the SAN with the test system. +- 3) Measurements shall use a measurement bandwidth in accordance to the conditions in clause 9.7.5.2.5. +- 4) The measurement device characteristics shall be: + - Detection mode: True RMS. + +- The emission power should be averaged over an appropriate time duration to ensure the measurement is within the measurement uncertainty in Table 4.1.2.2-2. +- 5) Set the SAN 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. NR-SAN-FR1-TM1.1 for *SAN type 1-O*), at manufacturer's declared rated output power $P_{\text{rated,c,TRP}}$ . + - For a RIB declared to be capable of multi-carrier 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. +- 6) Orient the positioner (and SAN) in order that the direction to be tested aligns with the test antenna such that measurements to determine TRP can be performed (see TS 38.141-2 [18], 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 TS 38.141-2 [18], 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. + +#### 9.7.5.2.5 Test requirement + +##### 9.7.5.2.5.1 Test requirement for SAN type 1-O + +For a *SAN type 1-O*, the TRP of any spurious emission shall not exceed the limits in table 9.7.5.2.5.1-1. + +**Table 9.7.5.2.5.1-1: General OTA SAN transmitter spurious emission limits for SAN type 1-O** + +| 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 [4], s4.1.
NOTE 2: Upper frequency as in ITU-R SM.329 [4], 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 [4], 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.8 OTA transmitter intermodulation + +The requirement is not applicable in this version of the specification. + +# 10 Radiated receiver characteristic + +## 10.1 General + +General test conditions for receiver tests are given in clause 4, including interpretation of measurement results and configurations for testing. SAN configurations for the tests are defined in clause 4.5. + +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 Definition and applicability + +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 TR 37. 941 [13]. +- 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 4: 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 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 TS 38.108 [2] clause 10.2.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.2.3 Test Purpose + +The test purpose is to verify that the SAN 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. + +## 10.2.4 Method of test + +### 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. + +Directions to be tested: + +- receiver target reference direction (D.26), +- conformance test directions (D.28). + +### 10.2.4.2 Procedure + +- 1) Place the SAN with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex D.4.1. +- 2) Align the manufacturer declared coordinate system orientation of the SAN with the test system. +- 3) Align the SAN 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 SAN under test. +- 5) Configure the beam peak direction for the transmitter according to the declared reference beam direction pair for the appropriate beam identifier. +- 6) For FDD operation, set the SAN to transmit beam(s) of the same operational band as the OSDD being tested according to the appropriate test configuration in clauses 4.7 and 4.8. +- 7) Start the signal generator for the wanted signal to transmit: + +- The test signal as specified in clause 10.2.5. +- 8) Set the test signal mean power so the calibrated radiated power at the SAN Antenna Array coordinate system reference point is as specified in clause 10.2.5. +- 9) Measure the throughput according to annex A.1 for each supported polarization. +- 10) Repeat steps 3 to 9 for all OSDD(s) declared for the SAN (D.19), and supported polarizations. + +## 10.2.5 Test requirements + +### 10.2.5.1 General + +The minimum EIS level is a declared figure (D.23) for each OSDD (D.19). The test requirement is calculated from the declared value offset by the EIS Test Tolerance specified in clause 4.1. + +### 10.2.5.2 Test requirements for *SAN type 1-H* and *SAN type 1-O* + +For each measured carrier, the throughput measured in step 9 of clause 10.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: SAN GEO and LEO class EIS levels** + +| SAN channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel (NOTE) | OTA sensitivity level, EIS (dBm) | +|-----------------------------|---------------------------|--------------------------------------|----------------------------------| +| 5, 10, 15 | 15 | G-FR1-A1-1 | Declared minimum EIS + 1.3 | +| 10, 15 | 30 | G-FR1-A1-2 | | +| 10, 15 | 60 | G-FR1-A1-3 | | +| 20 | 15 | G-FR1-A1-4 | | +| 20 | 30 | G-FR1-A1-5 | | +| 20 | 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 *SAN channel bandwidth*. + +## 10.3 OTA reference sensitivity level + +### 10.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 requirement shall apply to each supported polarization, under the assumption of *polarization match*. + +### 10.3.2 Minimum requirement + +For *SAN type 1-O* the minimum requirement is in TS 38.108 [2], clause 10.3.2. + +### 10.3.3 Test Purpose + +The test purpose is to verify that the SAN receiver 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*. + +## 10.3.4 Method of test + +### 10.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.44), +- OTA REFSENS conformance test directions (D.45) + +### 10.3.4.2 Procedure + +- 1) Place the SAN with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex D.4.1. +- 2) Align the manufacturer declared coordinate system orientation of the SAN with the test system. +- 3) Align the SAN 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 SAN under test. +- 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 SAN to transmit beam(s) of the same operational band as the *OTA REFSENS RoAoA* being tested according to the appropriate test configuration in clauses 4.7 and 4.8. +- 7) Start the signal generator for the wanted signal to transmit: + - The test signal as specified in clause 10.3.5. +- 8) Set the test signal mean power so the calibrated radiated power at the SAN Antenna Array coordinate system reference point is as specified in clause 10.3.5. +- 9) Measure the throughput according to annex A.1 for each supported polarization. +- 10) Repeat steps 3 to 9 for all OTA REFSENS conformance test directions of the SAN (D.45) and supported polarizations. + +## 10.3.5 Test requirements + +### 10.3.5.1 General + +The $EIS_{REFSENS}$ level is the conducted REFSENS requirement value offset by $\Delta_{OTAREFSENS}$ . The test requirement is calculated from the $EIS_{REFSENS}$ level offset by the $EIS_{REFSENS}$ Test Tolerance specified in clause 4.1. + +### 10.3.5.2 Test requirements for SAN type 1-O + +For each measured carrier, the throughput measured in step 9 of clause 10.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 10.3.5.2-1 and 10.3.5.2-2. + +**Table 10.3.5-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 | $-98.0 - \Delta_{OTAREFSENS}$ | +| 10, 15 | 30 | G-FR1-A1-2 | $-98.1 - \Delta_{OTAREFSENS}$ | +| 10, 15 | 60 | G-FR1-A1-3 | $-95.2 - \Delta_{OTAREFSENS}$ | +| 20 | 15 | G-FR1-A1-4 | $-91.6 - \Delta_{OTAREFSENS}$ | +| 20 | 30 | G-FR1-A1-5 | $-91.9 - \Delta_{OTAREFSENS}$ | +| 20 | 60 | G-FR1-A1-6 | $-92.0 - \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.5-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 | $-101.1 - \Delta_{OTAREFSENS}$ | +| 10, 15 | 30 | G-FR1-A1-2 | $-101.2 - \Delta_{OTAREFSENS}$ | +| 10, 15 | 60 | G-FR1-A1-3 | $-98.3 - \Delta_{OTAREFSENS}$ | +| 20 | 15 | G-FR1-A1-4 | $-94.7 - \Delta_{OTAREFSENS}$ | +| 20 | 30 | G-FR1-A1-5 | $-95.0 - \Delta_{OTAREFSENS}$ | +| 20 | 60 | G-FR1-A1-6 | $-95.1 - \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 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 *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 I-O*, the minimum requirement is in TS 38.108 [2], clause 10.4.2. + +### 10.4.3 Test purpose + +The test purpose is to verify that at the SAN receiver dynamic range, the relative throughput shall fulfil the specified limit. + +## 10.4.4 Method of test + +### 10.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.44). + +### 10.4.4.2 Procedure + +- 1) Place the SAN with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex D.4.2. +- 2) Align the manufacturer declared coordinate system orientation of the SAN with the test system. +- 3) Align the SAN 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 SAN under test. +- 5) Configure the beam peak direction for the transmitter according to the declared reference beam direction pair for the appropriate beam identifier. +- 6) For FDD operation, set the SAN to transmit beam(s) of the same operational band as the *OTA REFSENS RoAoA* being tested according to the appropriate test configuration in clauses 4.7 and 4.8. +- 7) Set the test signal mean power so that the calibrated radiated power at the SAN Antenna Array coordinate system reference point is as follows: + - a) Set the signal generator for the wanted signal to transmit as specified in table 10.4.5.2-1. + - b) Set the signal generator for the AWGN interfering signal at the same frequency as the wanted signal to transmit as specified in table 10.4.5.2-1. +- 8) Measure the throughput according to annex A.2 for each supported polarization. + +## 10.4.5 Test requirement + +### 10.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. + +### 10.4.5.2 Test requirements for SAN type 1-O + +For each measured carrier, the throughput measured in step 6 of clause 10.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 10.4.5.2-1. + +**Table 10.4.5.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) / BWConfig | Type of interfering signal | +|------------------------------------|---------------------------------|--------------------------------------|---------------------------------------|------------------------------------------------------------------|-----------------------------------| +| 5 | 15 | G-FR1-A2-1 | -76.1 - $\Delta_{\text{OTAREFSENS}}$ | -88.2 - $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-2 | -76.8 - $\Delta_{\text{OTAREFSENS}}$ | | | +| 10 | 15 | G-FR1-A2-1 | -76.1 - $\Delta_{\text{OTAREFSENS}}$ | -85.0 - $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-2 | -76.8 - $\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-3 | -73.8 - $\Delta_{\text{OTAREFSENS}}$ | | | +| 15 | 15 | G-FR1-A2-1 | -76.1 - $\Delta_{\text{OTAREFSENS}}$ | -83.2 - $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-2 | -76.8 - $\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-3 | -73.8 - $\Delta_{\text{OTAREFSENS}}$ | | | +| 20 | 15 | G-FR1-A2-4 | -69.9 - $\Delta_{\text{OTAREFSENS}}$ | -81.9 - $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -69.9 - $\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -70.2 - $\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 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. + +#### 10.5.1.2 Minimum requirement + +For *SAN type I-O*, the minimum requirement is in TS 38.108 [2], clause 10.5.1.2. + +#### 10.5.1.3 Test purpose + +The test purpose is to verify the ability of the SAN receiver filter to suppress interfering signals in the channels adjacent to the wanted channel. + +#### 10.5.1.4 Method of test + +##### 10.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. + +*SAN RF Bandwidth* edge position to be tested for multi-carrier : + +- $M_{RFBW}$ in single-band operation, see clause 4.9.1; + +Directions to be tested: + +- For SAN type 1-O, receiver target reference direction (D.26), + +#### 10.5.1.4.2 Procedure + +- 1) Place the SAN with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex D.4.2. +- 2) Align the manufacturer declared coordinate system orientation of the SAN with the test system. +- 3) Align the SAN with the test antenna in the declared direction to be tested. +- 4) Align the SAN 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) For FDD operation, set the SAN to transmit beam(s) of the same operational band as the OSDD or *OTA REFSENS RoAoA* being tested according to the appropriate test configuration in clauses 4.7 and 4.8. +- 7) Set the test signal mean power so that the calibrated radiated power at the SAN Antenna Array coordinate system reference point is as follows: + - a) Set the signal generator for the wanted signal to transmit as specified in table 10.5.1.2.1-1 for *SAN type 1-O* + - b) Set the signal generator for the interfering signal at the adjacent channel frequency of the wanted signal to transmit as specified in table 10.5.1.2.1-1 for *SAN type 1-O*. +- 8) Measure throughput according to annex A.1 for each supported polarization, for multi-carrier operation the throughput shall be measured for relevant carriers specified by the test configuration specified in clauses 4.7.2 and 4.8. + +#### 10.5.1.5 Test requirement + +##### 10.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 clause 4.1. + +##### 10.5.1.5.2 Test requirements 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 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 10.5.1.5.2-1 and table 10.5.1.5.2-2 for ACS. The reference measurement channel for the OTA wanted signal is identified in clause 10.5.1.2 and is further specified in annex A.1. The characteristics of the interfering signal is further specified in TS 38.108 [2] 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.5.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 | LEO SAN class: -60 – Δ minSENS
GEO SAN 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.5.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 Base Station 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 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. + +### 10.6.2 Minimum requirement + +The minimum requirement for SAN type 1-O is defined in TS 38.108 [2], clause 10.6.2. + +### 10.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. + +### 10.6.4 Method of test + +#### 10.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. + +SAN RF bandwidth positions to be tested for multi-carrier (MC): MRFBW in *single-band RIB*, see clause 4.9.1. + +Directions to be tested: For *SAN type 1-O*, receiver target reference direction (D.26). + +#### 10.6.4.2 Procedure + +- 1) Place SAN and the test antenna(s) according to annex D.4.3. +- 2) Align the SAN and test antenna(s) according to the directions to be tested. +- 3) Connect test antenna(s) to the measurement equipment as shown in annex D.4.3. +- 4) The test antenna(s) shall be dual (or single) polarized covering the same frequency ranges as the SAN 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. +- 7) For FDD operation, configure the beam peak direction for the transmitter units associated with the RIB under test according to the declared reference beam direction pair for the appropriate beam identifier with the carrier set-up and power allocation according to the applicable test configuration(s) (see clause 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. +- 8) Adjust the signal generators to the type of interfering signals, levels and the frequency offsets as specified for general test requirements in table 10.6.5-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. +- 9) The CW interfering signal shall be swept with a step size of 1 MHz within the frequency range specified in clause 10.6.5. +- 10) Measure the performance of the wanted signal at the receiver unit associated with the RIB, as defined in the clause 10.6.5, for the relevant carriers specified by the test configuration in clause 4.7 and 4.8. +- 11) Repeat for all supported polarizations. + +#### 10.6.5 Test requirements + +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*. + +For OTA wanted and OTA interfering signals provided at the RIB using the parameters in table 10.6.5-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.5-2. + +**Table 10.6.5-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: EIS minSENS 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 $r$ , where EIRP is in W and $r$ is in m. | | | + +**Table 10.6.5-2: $\Delta f_{\text{oob}}$ offset for satellite operating bands** + +| SAN type | Operating band characteristics | \Delta f_{\text{oob}} (MHz) | +|---------------------|------------------------------------------------------------|-------------------------------------------------| +| SAN type 1-O | $F_{\text{UL,high}} - F_{\text{UL,low}} < 100 \text{ MHz}$ | 20 | + +## 10.7 OTA receiver spurious emissions + +The requirement is not applicable in this version of the specification. + +## 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 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 and shall be time aligned with the wanted signal. + +### 10.9.2 Minimum requirement + +The minimum requirement for *SAN type 1-O* is in TS 38.108 [2], clause 10.9.2. + +### 10.9.3 Test purpose + +The purpose of this test is to verify the SAN receiver ability to suppress the IQ leakage. + +### 10.9.4 Method of test + +#### 10.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 SAN type 1-O, receiver target reference direction (D.26), + +#### 10.9.4.2 Procedure + +- 1) Place the SAN with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex [D.4.x]. + +- 2) Align the manufacturer declared coordinate system orientation of the SAN with the test system. +- 3) Align the SAN with the test antenna in the declared direction to be tested. +- 4) Align the SAN 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) For FDD operation, set the SAN to transmit beam(s) of the same operational band as the *OTA REFSENS RoAoA* or OSDD being tested according to the appropriate test configuration in clauses 4.7 and 4.8. +- 7) Set the test signal mean power so the calibrated radiated power at the SAN Antenna Array coordinate system reference point is as specified as follows: + - a) Adjust the signal generator for the wanted signal as specified in: +For *SAN type 1-O*, table 10.9.5.1-1 for SAN GEO class, in table 10.9.5.1-2 for SAN LEO class on one side of the $F_C$ . + - b) Adjust the signal generator for the interfering signal as specified in: +For *SAN type 1-O*, table 10.9.5.1-1 for SAN GEO class, in table 10.9.5.1-2 for SAN LEO class at opposite side of the $F_C$ and adjacent to the wanted signal. +- 8) Measure throughput according to annex A.1 for each supported polarization. +- 9) 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. +- 10) Repeat for all the specified measurement directions and supported polarizations. + +## 10.9.5 Test requirement + +### 10.9.5.1 *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.5.1-1 for SAN GEO class, in table 10.9.5.1-2 for SAN LEO class. + +**Table 10.9.5.1-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 | -96.5 - $\Delta_{\min\text{SENS}}$ | -92.0 - $\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 10 RBs | +| 10,15,20 | 15 | G-FR1-A1-1 | -94.6 - $\Delta_{\min\text{SENS}}$ | -88.1 - $\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 5 | 30 | G-FR1-A1-8 | -97.2 - $\Delta_{\min\text{SENS}}$ | -92.0 - $\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 5 RBs | +| 10,15,20 | 30 | G-FR1-A1-2 | -94.7 - $\Delta_{\min\text{SENS}}$ | -89.0 - $\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 10 RBs | +| 10,15,20 | 60 | G-FR1-A1-9 | -94.1 - $\Delta_{\min\text{SENS}}$ | -89.0 - $\Delta_{\min\text{SENS}}$ | 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.5.1-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 | -99.6 - $\Delta_{\min\text{SENS}}$ | -83.1 - $\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 10 RBs | +| 10,15,20 | 15 | G-FR1-A1-1 | -97.7 - $\Delta_{\min\text{SENS}}$ | -79.2 - $\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 5 | 30 | G-FR1-A1-8 | -100.3 - $\Delta_{\min\text{SENS}}$ | -83.1 - $\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 5 RBs | +| 10,15,20 | 30 | G-FR1-A1-2 | -97.8 - $\Delta_{\min\text{SENS}}$ | -80.1 - $\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 10 RBs | +| 10,15,20 | 60 | G-FR1-A1-9 | -97.2 - $\Delta_{\min\text{SENS}}$ | -80.1 - $\Delta_{\min\text{SENS}}$ | 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-O* 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 TS 38.108 [2] 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. + +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.1.3 Applicability rule + +### 11.1.3.1 General + +Unless otherwise stated, for a SAN declared to support more than 2 demodulation branches (for *SAN type 1-O*), the performance requirement tests for 2 demodulation branches shall apply, and the mapping between connectors and demodulation branches is up to SAN implementation. + +The tests requiring more than [20] dB SNR level are set to N/A in the test requirements. + +### 11.1.3.2 Applicability of PUSCH performance requirements + +#### 11.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). + +#### 11.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 SAN 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. + +#### 11.1.3.2.3 Applicability of requirements for different configurations + +Unless otherwise stated, for *SAN 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. + +### 11.1.3.3 Applicability of PUCCH performance requirements + +#### 11.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.101 in table 4.6-1). + +#### 11.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). + +#### 11.1.3.3.3 Applicability of requirements for different channel bandwidths + +For each subcarrier spacing declared to be supported by the SAN, the test requirements for a specific channel bandwidth shall apply only if the SAN 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. + +#### 11.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.103 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.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. + +#### 11.1.3.3.5 Applicability of requirements for multi-slot PUCCH + +Unless otherwise stated, multi-slot PUCCH requirement tests shall apply only if the SAN supports it (see D.105 in table 4.6-1). + +#### 11.1.3.4 Applicability of PRACH performance requirements + +##### 11.1.3.4.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.102 in table 4.6-1). + +##### 11.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.102 in table 4.6-1). + +##### 11.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). + +### 11.2 OTA performance requirements for PUSCH + +#### 11.2.1 Performance requirements for PUSCH with transform precoding disabled + +##### 11.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 SAN is based on the test applicability rules defined in clause 11.1.3. + +##### 11.2.1.2 Minimum Requirement + +For *SAN type I-O*, the minimum requirement is in TS 38.108 [2] clause 11.2.1. + +##### 11.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. + +##### 11.2.1.4 Method of test + +###### 11.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.44 in table 4.6-1). + +#### 11.2.1.4.2 Procedure + +- 1) Place the SAN with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex D.7. +- 2) Align the manufacturer declared coordinate system orientation of the SAN with the test system. +- 3) Set the SAN in the declared direction to be tested. +- 4) Connect the SAN 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 D.7. 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 11.2.1.4.2-1. + +**Table 11.2.1.4.2-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 | + +- 6) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G. +- 7) Adjust the test signal mean power so the calibrated radiated SNR value at the SAN receiver is as specified in clause 11.2.1.5 for *SAN type I-O*, and that the SNR at the SAN 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 11.2.1.4.2-2. + +**Table 11.2.1.4.2-2: AWGN power level at the SAN input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|-------------------------|----------------------------------------------| +| 15 | 5 | $-86.5 - \Delta_{OTAREFSENS}$ dBm / 4.5 MHz | +| 30 | 10 | $-83.6 - \Delta_{OTAREFSENS}$ dBm / 8.64 MHz | + +NOTE 1: $\Delta_{OTAREFSENS}$ as declared in D.43 in table 4.6-1 and clause 10.1 +[NOTE 2: 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.] + +- 8) For reference channels applicable to the SAN, measure the throughput. + +#### 11.2.1.5 Test Requirement + +The throughput measured according to clause 11.2.1.4.2 shall not be below the limits for the SNR levels specified in table 11.2.1.5-1 to 11.2.1.5-4. + +**Table 11.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 demodulation branches | 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.8 | +| | | Normal | NTN-TDLC5-200 Low | 70 % | G-FR1-A3-1 | pos1 | 2.2 | +| | 2 | Normal | NTN-TDLA100-200 Low | 70 % | G-FR1-A3-1 | pos1 | -0.1 | +| | | Normal | NTN-TDLC5-200 Low | 70% | G-FR1-A3-1 | pos1 | -0.6 | + +**Table 11.2.1.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 demodulation branches | 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-2 | pos1 | 3.5 | +| | | Normal | NTN-TDLC5-200 Low | 70 % | G-FR1-A3-2 | pos1 | 2.0 | +| | 2 | Normal | NTN-TDLA100-200 Low | 70 % | G-FR1-A3-2 | pos1 | -0.4 | +| | | Normal | NTN-TDLC5-200 Low | 70% | G-FR1-A3-2 | pos1 | -0.8 | + +**Table 11.2.1.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 demodulation branches | 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.9 | +| | | Normal | NTN-TDLC5-200 Low | 70 % | G-FR1-A3-1 | pos1 | 2.2 | +| | 2 | Normal | NTN-TDLA100-200 Low | 70 % | G-FR1-A3-1 | pos1 | 0.0 | +| | | Normal | NTN-TDLC5-200 Low | 70% | G-FR1-A3-1 | pos1 | -0.6 | + +**Table 11.2.1.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 demodulation branches | 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-2 | pos1 | 3.5 | +| | | Normal | NTN-TDLC5-200 Low | 70 % | G-FR1-A3-2 | pos1 | 1.9 | +| | 2 | Normal | NTN-TDLA100-200 Low | 70 % | G-FR1-A3-2 | pos1 | -0.4 | +| | | Normal | NTN-TDLC5-200 Low | 70% | G-FR1-A3-2 | pos1 | -0.8 | + +## 11.2.2 Performance requirements for PUSCH with transform precoding enabled + +### 11.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 SAN is based on the test applicability rules defined in clause 11.1.3. + +### 11.2.2.2 Minimum Requirement + +For *SAN type 1-O*, the minimum requirement is in TS 38.108 [2] clause 11.2.2. + +### 11.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. + +### 11.2.2.4 Method of test + +#### 11.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 REFSENS *receiver target reference direction* (see D.44 in table 4.6-1). + +#### 11.2.2.4.2 Procedure + +- 1) Place the SAN with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex D.7. +- 2) Align the manufacturer declared coordinate system orientation of the SAN with the test system. +- 3) Set the SAN in the declared direction to be tested. +- 4) Connect the SAN 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 D.7. 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 11.2.2.4.2-1. + +**Table 11.2.2.4.2-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 | + +- 6) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G. +- 7) Adjust the test signal mean power so the calibrated radiated SNR value at the SAN receiver is as specified in clause 11.2.2.5 for *SAN type 1-O*, and that the SNR at the SAN 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 11.2.2.4.2-2. + +**Table 11.2.2.4.2-2: AWGN power level at the SAN input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|----------------------------------------------| +| 15 | 5 | $-86.5 - \Delta_{OTAREFSENS}$ dBm / 4.5 MHz | +| 30 | 10 | $-83.6 - \Delta_{OTAREFSENS}$ dBm / 8.64 MHz | +| NOTE 1: $\Delta_{OTAREFSENS}$ as declared in D.43 in table 4.6-1 and clause 10.1.
[NOTE 2: 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.] | | | + +- 8) For reference channels applicable to the SAN, measure the throughput. + +## 11.2.2.5 Test Requirement + +The throughput measured according to clause 11.2.2.4.2 shall not be below the limits for the SNR levels specified in table 11.2.2.5-1 to 11.2.2.5-4. + +**Table 11.2.2.5-1: Test 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 demodulation branches | 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 | 4.3 | +| | | Normal | NTN-TDLC5-200 Low | 70 % | G-FR1-A3-3 | pos1 | 2.2 | +| | 2 | Normal | NTN-TDLA100-200 Low | 70 % | G-FR1-A3-3 | pos1 | 0.1 | +| | | Normal | NTN-TDLC5-200 Low | 70% | G-FR1-A3-3 | pos1 | -0.6 | + +**Table 11.2.2.5-2: Test 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 demodulation branches | 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-4 | pos1 | 4.1 | +| | | Normal | NTN-TDLC5-200 Low | 70 % | G-FR1-A3-4 | pos1 | 1.9 | +| | 2 | Normal | NTN-TDLA100-200 Low | 70 % | G-FR1-A3-4 | pos1 | -0.1 | +| | | Normal | NTN-TDLC5-200 Low | 70% | G-FR1-A3-4 | pos1 | -0.8 | + +**Table 11.2.2.5-3: Test 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 demodulation branches | 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 | 4.3 | +| | | Normal | NTN-TDLC5-200 Low | 70 % | G-FR1-A3-3 | pos1 | 2.2 | +| | 2 | Normal | NTN-TDLA100-200 Low | 70 % | G-FR1-A3-3 | pos1 | 0.1 | +| | | Normal | NTN-TDLC5-200 Low | 70% | G-FR1-A3-3 | pos1 | -0.6 | + +**Table 11.2.2.5-4: Test 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 demodulation branches | 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-4 | pos1 | 4.1 | +| | | Normal | NTN-TDLC5-200 Low | 70 % | G-FR1-A3-4 | pos1 | 1.9 | +| | 2 | Normal | NTN-TDLA100-200 Low | 70 % | G-FR1-A3-4 | pos1 | -0.1 | +| | | Normal | NTN-TDLC5-200 Low | 70% | G-FR1-A3-4 | pos1 | -0.8 | + +## 11.2.3 Performance requirements for UL timing adjustment + +### 11.2.3.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. + +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-3 are applied for both UEs. The received power for both UEs is the same. The resource blocks allocated for both UEs are consecutive. + +Which specific test(s) are applicable to SAN is based on the test applicability rules defined in clause 11.1.3. + +### 11.2.3.2 Minimum Requirement + +For *SAN type 1-O*, the minimum requirement is in TS 38.108 [2] clause 11.2.3. + +### 11.2.3.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. + +### 11.2.3.4 Method of test + +#### 11.2.3.4.1 Initial Conditions + +Test environment: Normal, see annex B.2. + +RF channels to be tested: M; see clause 4.9.1. + +Direction to be tested: OTA REFSENS *receiver target reference direction* (see D.44 in table 4.6-1). + +#### 11.2.3.4.2 Procedure + +- 1) Place the SAN with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex D.7. +- 2) Align the manufacturer declared coordinate system orientation of the SAN with the test system. +- 3) Set the SAN in the declared direction to be tested. +- 4) Connect the SAN 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 D.7. 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 11.2.3.4.2-1. + +**Table 11.2.3.4.2-1 Test parameters for testing UL timing adjustment for SAN type 1-O** + +| 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 | 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$ 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. | | | + +- 6) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G. Unless stated otherwise, the MIMO correlation matrices for the gNB are defined in annex G for low correlation. +- 7) Adjust the test signal mean power so the calibrated radiated SNR value at the SAN receiver is as specified in clause 11.2.3.5 and that the SNR at the SAN 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 11.2.3.4.2-2. + +**Table 11.2.3.4.2-2: AWGN power level at the SAN input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|-------------------------|----------------------------------------------------------------------| +| 15 | 5 | $-86.5\text{dBm} - \Delta_{OTAREFSENS}\text{ dBm} / 4.5\text{MHz}$ | +| 30 | 10 | $-83.6\text{ dBm} - \Delta_{OTAREFSENS}\text{ dBm} / 8.64\text{MHz}$ | + +NOTE 1: $\Delta_{OTAREFSENS}$ as declared in D.43 in table 4.6-1 and clause 10.1. +[NOTE 2: 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.] + +- 8) For reference channels applicable to the SAN, measure the throughput. + +### 11.2.3.5 Test Requirement + +The throughput measured according to clause 11.2.3.4.2 shall not be below the limits for the SNR levels specified in table 11.2.3.5-1 to 11.2.3.5-4. + +**Table 11.2.3.5-1: Test 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 demodulation branches | 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-5 | pos1 | 4.7 | +| | 2 | Normal | Scenario X | 70 % | G-FR1-A3-5 | pos1 | 0.3 | + +**Table 11.2.3.5-2: Test 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 demodulation branches | 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-6 | pos1 | 4.2 | +| | 2 | Normal | Scenario X | 70 % | G-FR1-A3-6 | pos1 | 0.1 | + +**Table 11.2.3.5-3: Test 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 demodulation branches | 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-5 | pos1 | 4.8 | +| | 2 | Normal | Scenario X | 70 % | G-FR1-A3-5 | pos1 | 0.3 | + +**Table 11.2.3.5-4: Test 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 demodulation branches | 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-6 | pos1 | 4.2 | +| | 2 | Normal | Scenario X | 70 % | G-FR1-A3-6 | pos1 | 0.2 | + +## 11.2.4 Performance requirements for PUSCH repetition Type A + +### 11.2.4.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 SAN is based on the test applicability rules defined in clause 11.1.3. + +### 11.2.4.2 Minimum Requirement + +For *SAN type 1-O*, the minimum requirement is in TS 38.108 [2] clause 11.2.4. + +### 11.2.4.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. + +### 11.2.4.4 Method of test + +#### 11.2.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.44 in table 4.6-1). + +#### 11.2.4.4.2 Procedure + +- 1) Place the SAN with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex D.7. +- 2) Align the manufacturer declared coordinate system orientation of the SAN with the test system. +- 3) Set the SAN in the declared direction to be tested. +- 4) Connect the SAN 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 D.7. 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 11.2.4.4.2-1. + +**Table 11.2.4.4.2-1: Test parameters for testing PUSCH repetition Type A** + +| Parameter | | Value | +|--------------------------------------------------------------------------|-------------------------------------------|--------------------------------| +| Transform precoding | | Disabled | +| HARQ | Maximum number of HARQ transmissions | 4 | +| | RV sequence | 0, 3, 0, 3 [Note 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 | +| | 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. | | | + +- 6) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G. + +- 7) Adjust the test signal mean power so the calibrated radiated SNR value at the SAN receiver is as specified in clause 11.2.4.5 for *SAN type I-O*, and that the SNR at the SAN 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 11.2.4.4.2-2. + +**Table 11.2.4.4.2-2: AWGN power level at the SAN input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|-------------------------|-----------------------------------------------------| +| 15 | 5 | $-86.5 - \Delta_{\text{OTAREFSENS}}$ dBm / 4.5 MHz | +| 30 | 10 | $-83.6 - \Delta_{\text{OTAREFSENS}}$ dBm / 8.64 MHz | + +NOTE 1: $\Delta_{\text{OTAREFSENS}}$ as declared in D.43 in table 4.6-1 and clause 10.1. +[NOTE 2: 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.] + +- 8) For reference channels applicable to the SAN, measure the throughput. + +## 11.2.4.5 Test Requirement + +The BLER measured according to clause 11.2.4.4.2 shall not be above the limits for the SNR levels specified in table 11.2.4.5-1 to 11.2.4.5-4. + +**Table 11.2.4.5-1: Test requirements for PUSCH repetition TypeA, PUSCH mapping Type A, 5 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | 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 | -4.5 | +| | 2 | Normal | NTN-TDLA100-200 Low | 1% (Note 1) | G-FR1-A3A-1 | pos1 | -7.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 11.2.4.5-2: Test requirements for PUSCH, PUSCH mapping Type A, 10 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | 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 | -4.5 | +| | 2 | Normal | NTN-TDLA100-200 Low | 1% (Note 1) | G-FR1-A3A-2 | pos1 | -7.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 11.2.4.5-3: Test requirements for PUSCH, PUSCH mapping Type B, 5 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | 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 | -4.5 | +| | 2 | Normal | NTN-TDLA100-200 Low | 1% (Note 1) | G-FR1-A3A-1 | pos1 | -7.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 11.2.4.5-4: Test requirements for PUSCH, PUSCH mapping Type B, 10 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | 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 | -4.5 | +| | 2 | Normal | NTN-TDLA100-200 Low | 1% (Note 1) | G-FR1-A3A-2 | pos1 | -7.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. + +## 11.3 OTA performance requirements for PUCCH + +### 11.3.1 Performance requirements for PUCCH format 0 + +#### 11.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-5 [12] 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. + +Which specific test(s) are applicable to SAN is based on the test applicability rules defined in clause 11.1.3. + +#### 11.3.1.2 Minimum Requirement + +For *SAN type 1-O*, the minimum requirements are in TS 38.108 [2] clause 11.3.1.1 and 11.3.1.2. + +#### 11.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. + +### 11.3.1.4 Method of test + +#### 11.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.44 in table 4.6-1). + +#### 11.3.1.4.2 Procedure + +- 1) Place the SAN with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex D.7. +- 2) Align the manufacturer declared coordinate system orientation of the SAN with the test system. +- 3) Set the SAN in the declared direction to be tested. +- 4) Connect the SAN 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 D.7. 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 [8] and according to additional test parameters listed in table 11.3.1.4.2-1. + +**Table 11.3.1.4.2-1: Test parameters** + +| Parameter | SAN type 1-O | +|--------------------------------------|--------------| +| 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 | + +- 6) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G.2. +- 7) Adjust the test signal mean power so the calibrated radiated SNR value at the SAN receiver is as specified in clause 11.3.1.5.1, and that the SNR at the SAN 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 11.3.1.4.2-2. + +**Table 11.3.1.4.2-2: AWGN power level at the SAN input** + +| SAN type | Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|-------------------------|-----------------------------------------------------| +| SAN type 1-O
(Note 2) | 15 | 5 | $-86.5 - \Delta_{\text{OTAREFSENS}}$ dBm / 4.5 MHz | +| | 30 | 10 | $-83.6 - \Delta_{\text{OTAREFSENS}}$ dBm / 8.64 MHz | +| NOTE 1: $\Delta_{\text{OTAREFSENS}}$ as declared in D.43 in table 4.6-1 and clause 10.1. | | | | +| NOTE 2: 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. | | | | + +- 8) The signal generator sends a test pattern with the pattern outlined in figure 11.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 11.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.](223792b3652794024244c277cc46394b_img.jpg) + +Figure 11.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 11.3.1.4.2-1: Test signal pattern for single user PUCCH format 0 demodulation tests** + +### 11.3.1.5 Test Requirement + +#### 11.3.1.5.1 Test requirement for SAN 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 11.3.1.5.1-1 and in table 11.3.1.5.1-2. + +**Table 11.3.1.5-1: Required SNR for PUCCH format 0, 15 kHz SCS and 5MHz channel bandwidth** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex X) | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------| +| 1 | 1 | NTN-TDLA100-200 Low | 9.5 | +| | 2 | NTN-TDLA100-200 Low | 3.9 | + +**Table 11.3.1.5-2: Required SNR for PUCCH format 0, 30 kHz SCS and 10MHz channel bandwidth** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex X) | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------| +| 1 | 1 | NTN-TDLA100-200 Low | 11.7 | +| | 2 | NTN-TDLA100-200 Low | 5.4 | + +## 11.3.2 Performance requirements for PUCCH format 1 + +### 11.3.2.1 NACK to ACK detection + +#### 11.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 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 transient period as specified in TS 38.101-5 [12] 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. + +Which specific test(s) are applicable to SAN is based on the test applicability rules defined in clause 11.1.3. + +#### 11.3.2.1.2 Minimum Requirement + +For SAN type 1-O, the minimum requirement is in TS 38.108 [2], clause 11.3.1.3. + +### 11.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. + +### 11.3.2.1.4 Method of test + +#### 11.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.44 in table 4.6-1). + +#### 11.3.2.1.4.2 Procedure + +- 1) Place the SAN with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex D.7. +- 2) Align the manufacturer declared coordinate system orientation of the SAN with the test system. +- 3) Set the SAN in the declared direction to be tested. +- 4) Connect the SAN 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 D.7. 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 [8], and according to additional test parameters listed in table 11.3.2.1.4.2-1. + +**Table 11.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 | + +- 6) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G.2. +- 7) Adjust the test signal mean power so the calibrated radiated SNR value at the SAN receiver is as specified in clause 11.3.2.1.5.1 for SAN type 1-O, and that the SNR at the SAN 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 11.3.2.1.4.2-2. + +**Table 11.3.2.1.4.2-2: AWGN power level at the SAN input** + +| SAN type | Subcarrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|--------------------------|---------------------------------|--------------------------------|-----------------------------------------------------| +| SAN type 1-O
(Note 2) | 15 kHz | 5 | $-86.5 - \Delta_{\text{OTAREFSENS}}$ dBm / 4.5 MHz | +| | 30 kHz | 10 | $-83.6 - \Delta_{\text{OTAREFSENS}}$ dBm / 8.64 MHz | + +NOTE 1: $\Delta_{\text{OTAREFSENS}}$ as declared in D.43 in table 4.6-1 and clause 10.1. +NOTE 2: 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. + +- 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. + +### 11.3.2.1.5 Test Requirement + +#### 11.3.2.1.5.1 Test Requirement for SAN 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 11.3.2.1.5.1-1 and table 11.3.2.1.5.1-2. + +**Table 11.3.2.1.5.1-1: Required SNR for PUCCH format 1 with 15 kHz SCS 5MHz channel bandwidth** + +| Number of TX antennas | Number of demodulation branches | Cyclis Prefix | Propagation conditions and correlation matrix (Annex X) | SNR (dB) | +|------------------------------|----------------------------------------|----------------------|----------------------------------------------------------------|-----------------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 2.8 | +| | 2 | Normal | NTN-TDLA100-200 Low | -3.5 | + +**Table 11.3.2.1.5.1-2: Required SNR for PUCCH format 1 with 30 kHz SCS 10MHz channel bandwidth** + +| Number of TX antennas | Number of demodulation branches | Cyclis Prefix | Propagation conditions and correlation matrix (Annex X) | SNR (dB) | +|------------------------------|----------------------------------------|----------------------|----------------------------------------------------------------|-----------------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 3.6 | +| | 2 | Normal | NTN-TDLA100-200 Low | -2.9 | + +### 11.3.2.2 ACK missed detection + +#### 11.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-5 [12] 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. + +Which specific test(s) are applicable to SAN is based on the test applicability rules defined in clause 11.1.3. + +### 11.3.2.2.2 Minimum Requirement + +For SAN type 1-O, the minimum requirement is in TS 38.108 [2], clause 11.3.1.3. + +### 11.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. + +### 11.3.2.2.4 Method of test + +#### 11.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 REFSENS receiver target reference direction (see D.44 in table 4.6-1). + +#### 11.3.2.2.4.2 Procedure + +- 1) Place the SAN with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex D.7. +- 2) Align the manufacturer declared coordinate system orientation of the SAN with the test system. +- 3) Set the SAN in the declared direction to be tested. +- 4) Connect the SAN 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 D.7. 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 [8], and according to additional test parameters listed in table 11.3.2.2.4.2-1. + +**Table 11.3.2.2.4.2-1: Test Parameters** + +| Parameter | Value | +|---------------------------------------------------|-------------------------------------------| +| 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 | + +- 6) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G.2. +- 7) Adjust the test signal mean power so the calibrated radiated SNR value at the SAN receiver is as specified in clause 11.3.2.2.5.1 for SAN type 1-O, and that the SNR at the SAN 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 11.3.2.2.4.2-2. + +**Table 11.3.2.2.4.2-2: AWGN power level at the SAN input** + +| SAN type | Subcarrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|-------------------------|-----------------------------------------------------| +| SAN type 1-O
(Note 2) | 15 kHz | 5 | $-86.5 - \Delta_{\text{OTAREFSENS}}$ dBm / 4.5 MHz | +| | 30 kHz | 10 | $-83.6 - \Delta_{\text{OTAREFSENS}}$ dBm / 8.64 MHz | +| NOTE 1: $\Delta_{\text{OTAREFSENS}}$ as declared in D.43 in table 4.6-1 and clause 10.1. | | | | +| NOTE 2: 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. | | | | + +- 8) 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 11.3.2.1.4.2 for NACK to ACK detection. Both statistics are measured in the same testing. + +### 11.3.2.2.5 Test Requirement + +#### 11.3.2.2.5.1 Test Requirement for SAN 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 11.3.2.2.5-1 and table 11.3.2.2.5-2. + +**Table 11.3.2.2.5.1-1: Required SNR for PUCCH format 1 with 15 kHz SCS 5MHz channel bandwidth** + +| Number of TX antennas | Number of demodulation branches | Cyclis Prefix | Propagation conditions and correlation matrix (Annex X) | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 2.1 | +| | 2 | Normal | NTN-TDLA100-200 Low | -4.0 | + +**Table 11.3.2.2.5.1-2: Required SNR for PUCCH format 1 with 30 kHz SCS 10MHz channel bandwidth** + +| Number of TX antennas | Number of demodulation branches | Cyclis Prefix | Propagation conditions and correlation matrix (Annex X) | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 3.7 | +| | 2 | Normal | NTN-TDLA100-200 Low | -2.8 | + +## 11.3.3 Performance requirements for PUCCH format 2 + +### 11.3.3.1 ACK missed detection performance requirements + +#### 11.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 SAN is based on the test applicability rules defined in clause 11.1.3. + +The transient period as specified in TS 38.101-5 [12] 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. + +#### 11.3.3.1.2 Minimum Requirement + +For *SAN type 1-O*, the minimum requirement is in TS 38.108 [2] clause 11.3.1.4. + +#### 11.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. + +#### 11.3.3.1.4 Method of test + +##### 11.3.3.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.44 in table.4.6-1). + +##### 11.3.3.1.4.2 Procedure + +- 1) Place the SAN with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex D.7. +- 2) Align the manufacturer declared coordinate system orientation of the SAN with the test system. +- 3) Set the SAN in the declared direction to be tested. +- 4) Connect the SAN 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 D.7. 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 [8], and according to additional test parameters listed in table 11.3.3.1.4.2-1. + +**Table 11.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$ | + +- 6) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G.2. +- 7) Adjust the test signal mean power so the calibrated radiated SNR value at the SAN receiver is as specified in clause 11.3.3.1.5.1 for *SAN type 1-O*, and that the SNR at the SAN 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 11.3.3.1.4.2-2. + +**Table 11.3.3.1.4.2-2: AWGN power level at the SAN input** + +| SAN type | Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|-------------------------|-----------------------------------------------------| +| SAN type 1-O
(Note 2) | 15 kHz | 5 | $-86.5 - \Delta_{\text{OTAREFSENS}}$ dBm / 4.5 MHz | +| | 30 kHz | 10 | $-83.6 - \Delta_{\text{OTAREFSENS}}$ dBm / 8.64 MHz | +| NOTE 1: $\Delta_{\text{OTAREFSENS}}$ as declared in D.43 in table 4.6-1 and clause 10.1. | | | | +| NOTE 2: 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. | | | | + +- 8) The signal generator sends a test pattern with pattern outlined in figure 11.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 11.3.3.1.4.2-1: Test signal pattern for PUCCH format 2 demodulation tests. The diagram shows a sequence of three rectangular boxes, each containing the text 'ACK', followed by three dots, indicating a repeating pattern of ACK signals.](51501a01b2c29ac95e126882508f8831_img.jpg) + +Figure 11.3.3.1.4.2-1: Test signal pattern for PUCCH format 2 demodulation tests. The diagram shows a sequence of three rectangular boxes, each containing the text 'ACK', followed by three dots, indicating a repeating pattern of ACK signals. + +**Figure 11.3.3.1.4.2-1: Test signal pattern for PUCCH format 2 demodulation tests** + +### 11.3.3.1.5 Test requirement + +#### 11.3.3.1.5.1 Requirements for SAN 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 11.3.3.1.5.1-1 and table 11.3.3.1.5.1-2. + +**Table 11.3.3.1.5.1-1: Required SNR for PUCCH format 2 with 15 kHz SCS 5MHz channel bandwidth** + +| Number of TX antennas | Number of demodulation branches | Cyclis Prefix | Propagation conditions and correlation matrix (Annex X) | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 15.2 | +| | 2 | Normal | NTN-TDLA100-200 Low | 5.3 | + +**Table 11.3.3.1.5.1-2: Required SNR for PUCCH format 2 with 30 kHz SCS 10MHz channel bandwidth** + +| Number of TX antennas | Number of demodulation branches | Cyclis Prefix | Propagation conditions and correlation matrix (Annex X) | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 12.6 | +| | 2 | Normal | NTN-TDLA100-200 Low | 5.0 | + +### 11.3.3.2 UCI BLER performance requirements + +#### 11.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 1 and part 2. + +Which specific test(s) are applicable to SAN is based on the test applicability rules defined in clause 11.1.3. + +The transient period as specified in TS 38.101-5 [12] 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. + +#### 11.3.3.2.2 Minimum Requirement + +For SAN type 1-O, the minimum requirement is in TS 38.108 [2] clause 11.3.1.4. + +### 11.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. + +### 11.3.3.2.4 Method of test + +#### 11.3.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 + +Direction to be tested: OTA REFSENS *receiver target reference direction* (see D.44 in table 4.6-1). + +#### 11.3.3.2.4.2 Procedure + +- 1) Place the SAN with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex D.7. +- 2) Align the manufacturer declared coordinate system orientation of the SAN with the test system. +- 3) Set the SAN in the declared direction to be tested. +- 4) Connect the SAN 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 D.7. 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 [8], and according to additional test parameters listed in table 11.3.3.2.4.2-1. + +**Table 11.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$ | + +- 6) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G.2. +- 7) Adjust the test signal mean power so the calibrated radiated SNR value at the SAN receiver is as specified in clause 11.3.3.2.5.1 for *SAN type 1-O*, and that the SNR at the SAN 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 11.3.3.2.4.2-2. + +**Table 11.3.3.2.4.2-2: AWGN power level at the SAN input** + +| SAN type | Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|--------------------------|---------------------------|-------------------------|----------------------------------------------| +| SAN type 1-O
(Note 2) | 15 kHz | 5 | $-86.5 - \Delta_{OTAREFSENS}$ dBm / 4.5 MHz | +| | 30 kHz | 10 | $-83.6 - \Delta_{OTAREFSENS}$ dBm / 8.64 MHz | + +NOTE 1: $\Delta_{OTAREFSENS}$ as declared in D.43 in table 4.6-1 and clause 10.1. + +NOTE 2: 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. + +- 8) The signal generator sends a test pattern with the pattern outlined in figure 11.3.3.2.4.2-1. The following statistics are kept: the number of incorrectly decoded UCI. + +![Figure 11.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, indicating a sequence of such boxes.](c5d9ee57705b6598bd43f9c075fec3c7_img.jpg) + +Figure 11.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, indicating a sequence of such boxes. + +**Figure 11.3.3.2.4.2-1: Test signal pattern for PUCCH format 2 demodulation tests** + +### 11.3.3.2.5 Test requirement + +#### 11.3.3.2.5.1 Requirements for SAN type 1-O + +The fraction of incorrectly decoded UCI shall be less than 1% for the SNR listed in table 11.3.3.2.5.1-1 and table 11.3.3.2.5.1-2. + +**Table 11.3.3.2.5.1-1: Required SNR for PUCCH format 2 with 15 kHz SCS 5MHz channel bandwidth** + +| Number of TX antennas | Number of demodulation branches | Cyclis Prefix | Propagation conditions and correlation matrix (Annex X) | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 6.9 | +| | 2 | Normal | NTN-TDLA100-200 Low | 1.4 | + +**Table 11.3.3.2.5.1-2: Required SNR for PUCCH format 2 with 30 kHz SCS 10MHz channel bandwidth** + +| Number of TX antennas | Number of demodulation branches | Cyclis Prefix | Propagation conditions and correlation matrix (Annex X) | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 7.0 | +| | 2 | Normal | NTN-TDLA100-200 Low | 1.1 | + +## 11.3.4 Performance requirements for PUCCH format 3 + +### 11.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 1 and part 2. + +The transient period as specified in TS 38.101-5 [12] 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. + +Which specific test(s) are applicable to SAN is based on the test applicability rules defined in clause 11.1.3. + +### 11.3.4.2 Minimum requirement + +For *SAN type 1-O*, the minimum requirement is in TS 38.108 [2], clause 11.3.1.5. + +### 11.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. + +### 11.3.4.4 Method of test + +#### 11.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.44 in table 4.6-1). + +#### 11.3.4.4.2 Procedure + +- 1) Place the SAN with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex D.7. +- 2) Align the manufacturer declared coordinate system orientation of the SAN with the test system. +- 3) Set the SAN in the declared direction to be tested. +- 4) Connect the SAN 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 D.7. 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 [8], and according to additional test parameters listed in table 11.3.4.4.2-1. + +**Table 11.3.4.4.2-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 | + +- 6) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G.2. +- 7) Adjust the test signal mean power so the calibrated radiated SNR value at the SAN receiver is as specified in clause 11.3.4.5.1 for *SAN type 1-O*, and the SNR at the SAN 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 11.3.4.4.2-2. + +**Table 11.3.4.4.2-2: AWGN power level at the SAN input** + +| SAN type | Subcarrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|-------------------------|----------------------------------------------------| +| SAN type 1-O
(Note 2) | 15 | 5 | $-86.5 - \Delta_{\text{OTAREFSENS}}$ dBm / 4.5MHz | +| | 30 | 10 | $-83.6 - \Delta_{\text{OTAREFSENS}}$ dBm / 8.64MHz | +| NOTE 1: $\Delta_{\text{OTAREFSENS}}$ as declared in D.43 in table 4.6-1 and clause 10.1. | | | | +| NOTE 2: 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. | | | | + +### 11.3.4.5 Test requirement + +#### 11.3.4.5.1 Test requirement for SAN type 1-O + +The fraction of incorrectly decoded UCI shall be less than 1% for the SNR listed in table 11.3.4.5.1-1 and table 11.3.4.5.1-2. + +**Table 11.3.4.5.1-1: Required SNR for PUCCH format 3 with 15 kHz SCS 5MHz channel bandwidth** + +| Number of TX antennas | Number of demodulation branches | 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 | 7.2 | +| | | | | Additional DM-RS | 7.0 | +| | 2 | Normal | NTN-TDLA100-200 Low | No additional DM-RS | 0.9 | +| | | | | Additional DM-RS | 0.6 | + +**Table 11.3.4.5.1-2: Required SNR for PUCCH format 3 with 30 kHz SCS 10MHz channel bandwidth** + +| Number of TX antennas | Number of demodulation branches | 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.8 | +| | | | | Additional DM-RS | 9.2 | +| | 2 | Normal | NTN-TDLA100-200 Low | No additional DM-RS | 2.2 | +| | | | | Additional DM-RS | 1.9 | + +### 11.3.5 Performance requirements for PUCCH format 4 + +#### 11.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 1 and part 2. + +The transient period as specified in TS 38.101-5 [12] 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. + +Which specific test(s) are applicable to SAN is based on the test applicability rules defined in clause 11.1.3. + +#### 11.3.5.2 Minimum requirement + +For SAN type 1-O, the minimum requirement is in TS 38.108 [2], clause 11.3.1.6. + +#### 11.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. + +#### 11.3.5.4 Method of test + +##### 11.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.44 in table 4.6-1). + +#### 11.3.5.4.2 Procedure + +- 1) Place the SAN with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex D.7. +- 2) Align the manufacturer declared coordinate system orientation of the SAN with the test system. +- 3) Set the SAN in the declared direction to be tested. +- 4) Connect the SAN 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 D.7. 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 [8], and according to additional test parameters listed in table 11.3.5.4.2-1. + +**Table 11.3.5.4.2-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 | + +- 6) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G.2. +- 7) Adjust the test signal mean power so the calibrated radiated SNR value at the SAN receiver is as specified in clause 11.3.5.5.1 for *SAN type 1-O*, and that the SNR at the SAN 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 11.3.5.4.2-2. + +**Table 11.3.5.4.2-2: AWGN power level at the SAN input** + +| SAN type | Subcarrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|------------------------------------------------------------------------------------------|--------------------------|-------------------------|----------------------------------------------------| +| SAN type 1-O | 15 | 5 | $-86.5 - \Delta_{\text{OTAREFSENS}}$ dBm / 4.5MHz | +| | 30 | 10 | $-83.6 - \Delta_{\text{OTAREFSENS}}$ dBm / 8.64MHz | +| NOTE 1: $\Delta_{\text{OTAREFSENS}}$ as declared in D.43 in table 4.6-1 and clause 10.1. | | | | + +#### 11.3.5.5 Test requirement + +##### 11.3.5.5.1 Test requirement for *SAN type 1-O* + +The fraction of incorrectly decoded UCI shall be less than 1% for the SNR listed in table 11.3.5.5.1-1 and table 11.3.5.5.1-2. + +**Table 11.3.5.5.1-1: Required SNR for PUCCH format 4 with 15 kHz SCS 5MHz channel bandwidth** + +| Number of TX antennas | Number of demodulation branches | Cyclis Prefix | Propagation conditions and correlation matrix (Annex G) | Additioan DM-RS configuration | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|-------------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | No additional DM-RS | 9.5 | +| | | | | Additional DM-RS | 9.2 | +| | 2 | Normal | NTN-TDLA100-200 Low | No additional DM-RS | 3.1 | +| | | | | Additional DM-RS | 2.8 | + +**Table 11.3.5.5.1-2: Required SNR for PUCCH format 4 with 30 kHz SCS 10MHz channel bandwidth** + +| Number of TX antennas | Number of demodulation branches | Cyclis Prefix | Propagation conditions and correlation matrix (Annex G) | Additioan DM-RS configuration | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|-------------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | No additional DM-RS | 11.1 | +| | | | | Additional DM-RS | 11.1 | +| | 2 | Normal | NTN-TDLA100-200 Low | No additional DM-RS | 4.1 | +| | | | | Additional DM-RS | 3.9 | + +## 11.3.6 Performance requirements for multi-slot PUCCH format + +### 11.3.6.1 Performance requirements for multi-slot PUCCH format 1 + +#### 11.3.6.1.1 NACK to ACK detection + +##### 11.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 SAN is based on the test applicability rules defined in clause 11.1.3. + +##### 11.3.6.1.1.2 Minimum Requirement + +For *SAN type I-O*, the minimum requirement is in TS 38.108 [2], clause 11.3.1.7. + +##### 11.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. + +##### 11.3.6.1.1.4 Method of test + +###### 11.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.44). + +#### 11.3.6.1.1.4.2 Procedure + +- 1) Place the SAN with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex D.7. +- 2) Align the manufacturer declared coordinate system orientation of the SAN with the test system. +- 3) Set the SAN in the declared direction to be tested. +- 4) Connect the SAN 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 D.7. 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 [8], and according to additional test parameters listed in table 11.3.6.1.1.4.2-1. + +**Table 11.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 | + +- 6) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G.2. +- 7) Adjust the test signal mean power so the calibrated radiated SNR value at the SAN receiver is as specified in clause 11.3.6.1.1.5.1 for *SAN type 1-O*, and that the SNR at the SAN 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 11.3.6.1.1.4.2-2 + +**Table 11.3.6.1.1.4.2-2: AWGN power level at the SAN input** + +| SAN type | Subcarrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|-------------------------------------------------------------------------------------------|--------------------------|-------------------------|-----------------------------------------------------| +| SAN type 1-O | 15 | 5 | $-86.5 - \Delta_{\text{OTAREFSSENS}}$ dBm / 4.5MHz | +| | 30 | 10 | $-83.6 - \Delta_{\text{OTAREFSSENS}}$ dBm / 8.64MHz | +| NOTE 1: $\Delta_{\text{OTAREFSSENS}}$ as declared in D.43 in table 4.6-1 and clause 10.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. + +#### 11.3.6.1.1.5 Test Requirement + +##### 11.3.6.1.1.5.1 Test Requirement for *SAN 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 11.3.6.1.1.5.1-1 and 11.3.6.1.1.5.1-2. + +**Table 11.3.6.1.1.5-1: Minimum requirements for multi-slot PUCCH format 1 with 15kHz SCS 5MHz channel bandwidth** + +| Number of TX antennas | Number of demodulation branches | 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 | -6.0 | + +**Table 11.3.6.1.1.5-2: Minimum requirements for multi-slot PUCCH format 1 with 30kHz SCS 10MHz channel bandwidth** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 1.8 | +| | 2 | Normal | NTN-TDLA100-200 Low | -5.0 | + +### 11.3.6.1.2 ACK missed detection + +#### 11.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. + +#### 11.3.6.1.2.2 Minimum Requirement + +For SAN type I-O, the minimum requirement is in TS 38.108 [2], clause 11.3.1.7. + +#### 11.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. + +#### 11.3.6.1.2.4 Method of test + +##### 11.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 REFSSENS receiver target reference direction (D.44). + +##### 11.3.6.1.2.4.2 Procedure + +- 1) Place the SAN with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex D.7. + +- 2) Align the manufacturer declared coordinate system orientation of the SAN with the test system. +- 3) Set the SAN in the declared direction to be tested. +- 4) Connect the SAN 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 D.7. 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 [8], and according to additional test parameters listed in table 11.3.6.1.2.4.2-1. + +**Table 11.3.6.1.2.4.2-1: Test Parameters for multi-slot PUCCH format 1** + +| Parameter | Value | +|---------------------------------------------------------|----------------------------------------| +| 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 | + +- 6) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G.2. +- 7) Adjust the test signal mean power so the calibrated radiated SNR value at the SAN receiver is as specified in clause 11.3.6.1.2.5.1 for *SAN type 1-O*, and that the SNR at the SAN 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 11.3.6.1.2.4.2-2. + +**Table 11.3.6.1.2.4.2-2: AWGN power level at the SAN input** + +| SAN type | Subcarrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|------------------------------------------------------------------------------------------|--------------------------|-------------------------|----------------------------------------------------| +| SAN type 1-O | 15 | 5 | $-86.5 - \Delta_{\text{OTAREFSENS}}$ dBm / 4.5MHz | +| | 30 | 10 | $-83.6 - \Delta_{\text{OTAREFSENS}}$ dBm / 8.64MHz | +| NOTE 1: $\Delta_{\text{OTAREFSENS}}$ as declared in D.43 in table 4.6-1 and clause 10.1. | | | | + +- 8) The signal generator sends a test pattern with the pattern outlined in figure 11.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 11.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', followed by three dots (ellipsis) indicating a continuation of the pattern.](e034b0863f1ccdc3e0b3d0e2f449be66_img.jpg) + +Figure 11.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', followed by three dots (ellipsis) indicating a continuation of the pattern. + +**Figure 11.3.6.1.2.4.2-1: Test signal pattern for PUCCH format 1 demodulation tests** + +#### 11.3.6.1.2.5 Test Requirement + +##### 11.3.6.1.2.5.1 Test Requirement for SAN 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 11.3.6.1.2.5.1-1 and 11.3.6.1.2.5.1-2. + +**Table 11.3.6.1.2.5-1: Minimum requirements for multi-slot PUCCH format 1 with 15kHz SCS 5MHz channel bandwidth** + +| Number of TX antennas | Number of demodulation branches | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | SNR (dB) | +|-----------------------|---------------------------------|---------------|---------------------------------------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | -1.3 | +| | 2 | Normal | NTN-TDLA100-200 Low | -7.4 | + +**Table 11.3.6.1.2.5-2: Minimum requirements for multi-slot PUCCH format 1 with 30kHz SCS 10MHz channel bandwidth** + +| Number of TX antennas | Number of demodulation branches | 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 | -7.0 | + +## 11.4 OTA performance requirements for PRACH + +### 11.4.1 PRACH false alarm probability and missed detection + +#### 11.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, and 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 values given in table 11.4.1.1-1. + +**Table 11.4.1.1-1: Time error tolerance for AWGN, NTN-TDLA100** + +| 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. Which specific test(s) are applicable to SAN is based on the test applicability rules defined in clause 11.1.3. + +#### 11.4.1.2 Minimum requirement + +For SAN type 1-O, the minimum requirement is in TS 38.108 [2] clause 11.4.1.1 and 11.4.1.2. + +### 11.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. + +### 11.4.1.4 Method of test + +#### 11.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.44 in table 4.6-1). + +#### 11.4.1.4.2 Procedure + +- 1) Place the SAN with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex D.7. +- 2) Align the manufacturer declared coordinate system orientation of the SAN with the test system. +- 3) Set the SAN in the declared direction to be tested. +- 4) Connect the SAN 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 D.7. 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 G. +- 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 11.4.1.4.2-1. + +**Table 11.4.1.4.2-1: AWGN power level at the SAN input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|-------------------------|----------------------------------------------------| +| 15 | 5 | $-83.5 - \Delta_{\text{OTAREFSENS}}$ dBm / 4.5MHz | +| 30 | 10 | $-80.6 - \Delta_{\text{OTAREFSENS}}$ dBm / 8.64MHz | + +NOTE 1: $\Delta_{\text{OTAREFSENS}}$ as declared in D.43 in table 4.6-1 and clause 10.1. +NOTE 2: 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. + +- 8) Adjust the frequency offset of the test signal according to table 11.4.1.5-1 or 11.4.1.5-2 or 11.4.1.5-3. +- 9) Adjust the equipment so that the SNR specified in table 11.4.1.5-1 or 11.4.1.5-2 or 11.4.1.5-3 is achieved at the SAN 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 11.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 11.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 repeating pattern.](bd7d36eb91fa35077ac820550097bac2_img.jpg) + +Figure 11.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 repeating pattern. + +**Figure 11.4.1.4.2-1: PRACH preamble test pattern** + +Unless otherwise stated, the timing offset base value for PRACH preamble format 0 and 2 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 and 2 is presented in Figure 11.4.1.4.2-2. + +![Figure 11.4.1.4.2-2: Timing offset scheme for PRACH preamble format 0 and 2. The diagram shows a horizontal timeline with 10 vertical tick marks. Below each tick mark is a semi-circular arc pointing downwards. A long curved arrow at the top points from the first tick mark to the tenth, indicating a continuous loop of timing offsets.](f26e237ac9b5c1b2cbbb849964f978f0_img.jpg) + +Figure 11.4.1.4.2-2: Timing offset scheme for PRACH preamble format 0 and 2. The diagram shows a horizontal timeline with 10 vertical tick marks. Below each tick mark is a semi-circular arc pointing downwards. A long curved arrow at the top points from the first tick mark to the tenth, indicating a continuous loop of timing offsets. + +**Figure 11.4.1.4.2-2: Timing offset scheme for PRACH preamble format 0 and 2** + +Unless otherwise stated, the timing offset base value for PRACH preamble format B4 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 B4 and C2 is presented in Figure 11.4.1.4.2-3. + +![Figure 11.4.1.4.2-3: Timing offset scheme for PRACH preamble format B4 and C2. The diagram is identical to Figure 11.4.1.4.2-2, showing a horizontal timeline with 10 vertical tick marks, semi-circular arcs below each, and a long curved arrow at the top indicating a continuous loop of timing offsets.](7b49a5e2da4a559dce8c167c9203ad8e_img.jpg) + +Figure 11.4.1.4.2-3: Timing offset scheme for PRACH preamble format B4 and C2. The diagram is identical to Figure 11.4.1.4.2-2, showing a horizontal timeline with 10 vertical tick marks, semi-circular arcs below each, and a long curved arrow at the top indicating a continuous loop of timing offsets. + +**Figure 11.4.1.4.2-3: Timing offset scheme for PRACH preamble format B4 and C2** + +### 11.4.1.5 Test requirement + +Pfa shall not exceed 0.1%. Pd shall not be below 99% for the SNRs in tables 11.4.1.5-1 to 11.4.1.5-3. + +**Table 11.4.1.5-1: PRACH missed detection test requirements, 1.25 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex G) | Frequency offset | SNR (dB) | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------|----------------|----------------| +| | | | | Burst format 0 | Burst format 2 | +| 1 | 1 | AWGN | 0 | -11.7 | -17.1 | +| | | NTN-TDLA100 Low | 200 Hz | 1.3 | -9.1 | +| | 2 | AWGN | 0 | -14.2 | -19.5 | +| | | NTN-TDLA100 Low | 200 Hz | -6.2 | -14.3 | + +**Table 11.4.1.5-2: PRACH missed detection test requirements, 15 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex G) | Frequency offset | SNR (dB) | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------|-----------------|-----------------| +| | | | | Burst format B4 | Burst format C2 | +| 1 | 1 | AWGN | 0 | -14.3 | -8.9 | +| | | NTN-TDLA100 Low | 200 Hz | -2.1 | 2.5 | +| | 2 | AWGN | 0 | -16.5 | -12.2 | +| | | NTN-TDLA100 Low | 200 Hz | -8.4 | -4.2 | + +**Table 11.4.1.5-3: PRACH missed detection test requirements, 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex G) | Frequency offset | SNR (dB) | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------|-----------------|-----------------| +| | | | | Burst format B4 | Burst format C2 | +| 1 | 1 | AWGN | 0 | -14.1 | -8.9 | +| | | NTN-TDLA100 Low | 200 Hz | -3.7 | 0.7 | +| | 2 | AWGN | 0 | -16.2 | -11.6 | +| | | NTN-TDLA100 Low | 200 Hz | -9.4 | -5.2 | + +## Annex A (normative): Reference measurement channel + +### A.1 Fixed Reference Channels for RF Rx requirement (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 [7]. + +## 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 [7]. + +## A.3 Fixed Reference Channels for performance requirements (QPSK, R=308/1024) + +The parameters for the reference measurement channels are specified in table A.3-1 to table A.3-3 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 = pos1 and 1 transmission layer. +- FRC parameters are specified in table A.3-2 for FR1 PUSCH with transform precoding enabled, additional DM-RS position = pos1 and 1 transmission layer. +- FRC parameters are specified in table A.3-3 for FR1 PUSCH with transform precoding disabled, additional DM-RS position = pos1 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 | +|-----------------------------------------------|------------|------------| +| Subcarrier spacing (kHz) | 15 | 30 | +| Allocated resource blocks | 25 | 24 | +| CP-OFDM Symbols per slot (Note 1) | 12 | 12 | +| MCS table | 64QAM | 64QAM | +| 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 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, and $l_0 = 2$ or 3 for PUSCH mapping type A, as per table 6.4.1.1.3-3 of TS 38.211 [8]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [7]. + +**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-3 | G-FR1-A3-4 | +|-----------------------------------------------|------------|------------| +| Subcarrier spacing (kHz) | 15 | 30 | +| Allocated resource blocks | 25 | 24 | +| MCS table | 64QAM | 64QAM | +| 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 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, and $l_0 = 2$ or 3 for PUSCH mapping type A, as per table 6.4.1.1.3-3 of TS 38.211 [8]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [7]. + +**Table A.3-3: 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-5 | G-FR1-A3-6 | +|-----------------------------------------------|------------|------------| +| Subcarrier spacing (kHz) | 15 | 30 | +| Allocated resource blocks | 12 | 12 | +| CP-OFDM Symbols per slot (Note 1) | 12 | 12 | +| MCS table | 64QAM | 64QAM | +| Modulation | QPSK | QPSK | +| Code rate (Note 2) | 308/1024 | 308/1024 | +| Payload size (bits) | 1032 | 1032 | +| 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) | 1048 | 1048 | +| Total number of bits per slot | 3456 | 3456 | +| Total symbols per slot | 1728 | 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, and $l_0$ = 2 or 3 for PUSCH mapping type A, as per table 6.4.1.1.3-3 of TS 38.211 [8]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [7]. + +## 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-3 | +|-----------------------------------------------|-------------|-------------| +| Subcarrier spacing (kHz) | 15 | 30 | +| Allocated resource blocks | 25 | 24 | +| CP-OFDM Symbols per slot (Note 1) | 12 | 12 | +| MCS table | 64QAMLowSE | 64QAMLowSE | +| 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 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 = 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 [8]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [7]. + +## 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 (informative): Environmental requirements for the SAN equipment + +### B.1 General + +For each test in the present document, the environmental conditions under which the SAN 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 SAN hardware or alternative OTA measurements which are then related to the original specification are acceptable, see annex B.6. + +SAN involves two categories of equipment, differentiated by the operation environment: + +- Equipment deployed in space as part of Satellite Payload RF (SPRF) +- Equipment deployed on the ground (SAN terrestrial equipment). + +### B.2 Normal test environment + +#### B.2.1 Normal test environment for SPRF + +When a normal test environment is specified for a test, the SPRF shall be tested within the minimum and maximum limits of the conditions stated in table B.2.1-1. + +Additional environmental parameters specific to space operation might be considered and included in test report. + +Table B.2.1-1: Limits of conditions for normal test environment for SPRF + +| Condition | Minimum | Maximum | +|-----------------------------|---------------------------------------------------------------------------------------------------------------|-----------------------------| +| Barometric pressure | As declared by manufacturer | As declared by manufacturer | +| Temperature | As declared by manufacturer | As declared by manufacturer | +| Relative humidity | As declared by manufacturer | As declared by manufacturer | +| Power supply | Nominal, as declared by the manufacturer | | +| Vibration | As declared by manufacturer | | +| Other additional parameters | As declared by manufacturer | | +| NOTE: | Space operation conditions are defined outside 3GPP and are depending on characteristics of each application. | | + +## B.2.2 Normal test environment for SAN terrestrial equipment + +When a normal test environment is specified for a test, the SAN terrestrial equipment shall be tested within the minimum and maximum limits of the conditions stated in table B.2.2-1. + +**Table B.2.2-1: Limits of conditions for normal test environment for SAN terrestrial equipment** + +| Condition | Minimum | Maximum | +|---------------------|------------------------------------------|---------| +| Barometric pressure | 86 kPa | 106 kPa | +| Temperature | 15 °C | 30 °C | +| Relative humidity | 20 % | 85 % | +| Power supply | Nominal, as declared by the manufacturer | | +| Vibration | Negligible | | + +The ranges of barometric pressure, temperature and humidity represent the maximum variation expected in the uncontrolled environment of a test laboratory. If it is not possible to maintain these parameters within the specified limits, the actual values shall be recorded in the test report. + +## B.3 Extreme test environment + +### B.3.1 Extreme test environment for SPRF + +The manufacturer shall declare the following parameters supported by the equipment: + +- 1) minimum and maximum operating temperatures +- 2) maximum and minimum power supply + +When an extreme test environment is specified for a test, the SPRF shall be tested within the limits of the conditions stated in table B.3.1-1. + +**Table B.3.1-1: Limits of conditions for extreme test environment for SPRF** + +| Condition | Minimum | Maximum | +|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------| +| Barometric pressure | Declared by manufacturer | Declared by manufacturer | +| Relative humidity | Declared by manufacturer | Declared by manufacturer | +| Vibration | Declared by manufacturer | Declared by manufacturer | +| Additional conditions | Declared by manufacturer | Declared by manufacturer | +| NOTE: | Additional extreme test conditions might be decided outside 3GPP, according to the specific mission requirements, together with operator and manufacturer customizations. | | + +### B.3.2 Extreme test environment for SAN terrestrial equipment + +For SAN terrestrial equipment, 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.3 Extreme temperature + +When an extreme temperature test environment is specified for a test, the test shall be performed at the minimum and maximum operating temperatures declared by the manufacturer for the equipment under test. + +NOTE: It is recommended that the equipment is made fully operational prior to the equipment being taken to its lower operating temperature. + +For SPRF: + +The test at minimum and maximum temperatures shall be performed with the environment test equipment and methods including the required environmental phenomena into the equipment, conforming to the test procedures specific to space equipment, as declared by the manufacturer. + +For SAN terrestrial equipment: + +The test at minimum temperature 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 [14]. It is allowed to exclude from this test condition the equipment which is difficult to include due to size limitations. Such exclusion shall be recorded in the test report. + +The test at maximum temperature 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 [15]. It is allowed to exclude from this test condition the equipment which is difficult to include due to size limitations. Such exclusion shall be recorded in the test report. + +### B.3.4 Extreme 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). + +For SPRF the tests shall be carried out at the steady state minimum and maximum temperature limits declared by the manufacturer for the equipment, as described in clause B.3.2. For SAN terrestrial 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 [14] Test Ab/Ad and IEC 60 068-2-2 [15] Test Bb/Bd: Dry heat. It is allowed to exclude from this test condition the equipment which is difficult to include due to size limitations. Such exclusion shall be recorded in the test report. + +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). + +For SPRF the tests shall be carried out at the steady state minimum and maximum temperature limits declared by the manufacturer for the equipment, as described in clause B.3.2. + +For SAN terrestrial 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 [14] Test Ab/Ad and IEC 60 068-2-2 [15] Test Bb/Bd: Dry heat. It is allowed to exclude from this test condition the equipment, which is difficult to include due to size limitations. Such exclusion shall be recorded in the test report. + +--- + +## 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. + +For SPRF this shall use the environment test equipment and methods including the required environmental phenomena into the equipment, conforming to the test procedures specific to space equipment, as declared by the manufacturer. For SAN terrestrial equipment 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 [16]. Other environmental conditions shall be within the ranges specified in annex B.2. It is allowed to exclude from this test condition the equipment which is difficult to include due to size limitations. Such exclusion shall be recorded in the test report. + +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 Measurement of test environment + +The measurement accuracy of the 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 + +The test requirements explicitly defined in this specification have been calculated by relaxing the minimum requirements of the core specification TS 38.108 [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 for conducted transmitter tests** + +| Test | Minimum requirement in TS 38.108 [2] | Test Tolerance (TT) | Test requirement in the present document | +|---------------------------------------------------|--------------------------------------|------------------------------------------|-------------------------------------------------| +| 6.2 SAN output power | clause 6.2 | Normal and extreme conditions:
0.7 dB | Formula:
Upper limit + TT, Lower limit - TT | +| 6.3 Output power dynamics | clause 6.3 | 0.4 dB | Formula:
Total power dynamic range – TT (dB) | +| 6.5.1 Frequency error | clause 6.5.1 | 12 Hz | Formula:
Frequency Error limit + TT | +| 6.5.2 Modulation quality (EVM) | clause 6.5.2 | 1% | Formula:
EVM limit + TT | +| 6.6.2 Occupied bandwidth | clause 6.6.2 | 0 Hz | Formula:
Minimum Requirement + TT | +| 6.6.3 Adjacent Channel Leakage Power Ratio (ACLR) | clause 6.6.3 | ACLR:
BW ≤ 20MHz:
0.8dB | Formula:
ACLR Minimum Requirement - TT | +| 6.6.4 Out-of-band emissions | clause 6.6.4 | 0dB | Formula:
Minimum Requirement + TT | +| 6.6.5 Transmitter spurious emissions | clause 6.6.5 | 0dB | Formula:
Minimum Requirement + TT | + +NOTE 1: TT values are applicable for normal condition unless otherwise stated. + +**Table C.1-2: Derivation of test requirements for OTA transmitter tests** + +| Test | Minimum requirement in TS 38.108 [2] | Test Tolerance (TT OTA ) | Test requirement in the present document | +|-------------------------------------------------------|--------------------------------------|---------------------------------------------------------------|------------------------------------------------| +| 9.2 Radiated transmit power | clause 9.2 | Normal conditions:
1.1 dB
Extreme conditions:
2.5 dB | Formula:
Upper limit + TT, Lower limit – TT | +| 9.3 OTA SAN output power | clause 9.3 | 1.4 dB | Formula:
Upper limit + TT, Lower limit – TT | +| 9.4 OTA output power dynamics | clause 9.4 | 0.4 dB | Formula:
Total power dynamic range – TT | +| 9.6.1 OTA frequency Error | clause 9.6.1 | 12 Hz | Formula:
Frequency Error limit + TT | +| 9.6.2 OTA Modulation quality (EVM) | clause 9.6.2 | 1% | Formula:
EVM limit + TT | +| 9.7.2 OTA occupied bandwidth | clause 9.7.2 | 0 Hz | Formula:
Minimum Requirement + TT | +| 9.7.3 OTA Adjacent Channel Leakage Power Ratio (ACLR) | clause 9.7.3 | Relative: 1 dB | Formula:
Relative limit - TT | +| 9.7.4 OTA out-of-band emissions | clause 9.7.4 | 0 dB | Formula:
Minimum Requirement + TT | +| 9.7.5.2 General transmitter spurious emissions | clause 9.7.5.2.2 | 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 for conducted receiver tests** + +| Test | Minimum requirement in TS 38.108 [2] | Test Tolerance (TT) | Test requirement in the present document | +|--------------------------------------|--------------------------------------|---------------------------------------|-------------------------------------------------| +| 7.2 Reference sensitivity level | clause 7.2 | Normal and extreme conditions: 0.7 dB | Formula: Reference sensitivity power level + TT | +| 7.3 Dynamic range | clause 7.3 | 0.3 dB | Formula: Wanted signal power + TT | +| 7.4 In-band selectivity and blocking | clause 7.4 | 0dB | Formula: Wanted signal power + TT | +| 7.5 Out-of-band blocking | clause 7.5 | 0dB | Formula: Wanted signal power + TT | +| 7.8 In-channel selectivity | clause 7.8 | 1.4 dB | Formula: Wanted signal power + TT | + +NOTE: TT values are applicable for normal condition unless otherwise stated. + +**Table C.2-2: Derivation of test requirements for OTA receiver tests** + +| Test | Minimum requirement in TS 38.108 [2] | Test Tolerance (TT OTA ) | Test requirement in the present document | +|-----------------------------------------|--------------------------------------|-------------------------------------|--------------------------------------------------------------------------------| +| 10.2 OTA sensitivity | clause 10.2 | 1.3 dB | Formula:
Declared Minimum EIS + TT | +| 10.3 OTA reference sensitivity level | clause 10.3 | 1.3 dB | Formula:
$EIS_{REFSENS} + TT$ | +| 10.4 OTA dynamic range | clause 10.4 | 0.3 dB | Formula:
Wanted signal power + TT

Interferer signal power unchanged. | +| 10.5.1 OTA adjacent channel selectivity | clause 10.5.1 | 0 dB | Formula:
Wanted signal power + TT

Interferer signal power unchanged. | +| 10.6 OTA out-of-band blocking | clause 10.6 | 0 dB | Formula:
Wanted signal power + TT | +| 10.9 OTA in-channel selectivity | clause 10.9 | 1.7 dB | 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 + +**Table C.3-1: Derivation of Test Requirements (Performance tests)** + +| Test | Minimum Requirement in TS 38.108 [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 | 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 UL timing adjustment | SNRs as specified | [0.3] dB for AWGN | Formula: SNR + TT
T-put limit unchanged | +| 8.2.4 Performance requirements for PUSCH repetition Type A | 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.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 | + +**Table C.3-2: Derivation of test requirements (FR1 OTA performance tests)** + +| Test | Minimum Requirement in TS 38.108 [2] | Test Tolerance (TT OTA ) | Test requirement in the present document | +|-----------------------------------------------------------------------------|--------------------------------------|------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------| +| 11.2.1 Performance requirements for PUSCH with transform precoding disabled | See clause 11.2.1.1 | [0.6] dB | Formula: SNR + TT OTA
T-put limit unchanged | +| 11.2.2 Performance requirements for PUSCH with transform precoding enabled | See clause 11.2.1.2 | [0.6] dB | Formula: SNR + TT OTA
T-put limit unchanged | +| 11.2.3 Performance requirements for UL timing adjustment | See clause 11.2.1.3 | [0.3] dB for AWGN cases | Formula: SNR + TT OTA
T-put limit unchanged | +| 11.2.4 Performance requirements for PUSCH repetition Type A | See clause 11.2.1.4 | [0.6] dB | Formula: SNR + TT OTA
BLER limit unchanged | +| 11.3.1 Performance requirements for PUCCH format 0 | See clause 11.3.1.1 | [0.6] dB | Formula: SNR + TT OTA
False ACK limit unchanged
Correct ACK limit unchanged | +| 11.3.2 Performance requirements for PUCCH format 1 | See clause 11.3.1.3 | [0.6] dB | Formula: SNR + TT OTA
False ACK limit unchanged

False NACK limit unchanged
Correct ACK limit unchanged | +| 11.3.3 Performance requirements for PUCCH format 2 | See clause 11.3.1.4 | [0.6] dB | Formula: SNR + TT OTA
False ACK limit unchanged
Correct ACK limit unchanged
UCI BLER limit unchanged | +| 11.3.4 Performance requirements for PUCCH format 3 | See clause 11.3.1.5 | [0.6] dB | Formula: SNR + TT OTA
UCI BLER limit unchanged | +| 11.3.5 Performance requirements for PUCCH format 4 | See clause 11.3.1.6 | [0.6] dB | Formula: SNR + TT OTA
UCI BLER limit unchanged | +| 11.4.1 PRACH false alarm probability and missed detection | See clause 11.4.1 | [0.6] dB for fading cases
[0.3] dB for AWGN cases | Formula: SNR + TT OTA
PRACH False detection limit unchanged
PRACH detection limit unchanged | + +NOTE: TT values are applicable for normal condition unless otherwise stated. + +## Annex D (informative): Measurement system set-up + +### D.1 SAN type 1-H transmitter + +#### D.1.1 SAN output power, output power dynamics, frequency error, EVM, unwanted emissions for SAN type 1-H + +*TAB connectors* may be connected to the measurement equipment singularly and tested one at a time (figure D.1.1-1), or may be tested simultaneously in groups (figure D.1.1-2) where the group size may range from two to all the *TAB connectors* which are subject to particular transmitter test in this test setup. + +In all cases the measurement is per *TAB connector* but the measurement may be done in parallel. + +![Figure D.1.1-1: Measuring system set-up for SAN type 1-H output power, output power dynamics, frequency error, EVM, unwanted emissions for a single TAB connector. 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. At the boundary, there are multiple connectors labeled #1, #2, ..., #K. Connector #1 is connected to a box labeled 'Measurement equipment'. Connectors #2 and #K are connected to boxes labeled 'Load'. An arrow points to the boundary line with the label 'Transceiver array boundary connector TAB(n)'.](313826501fcb4294a5d337702ea35f2d_img.jpg) + +Figure D.1.1-1: Measuring system set-up for SAN type 1-H output power, output power dynamics, frequency error, EVM, unwanted emissions for a single TAB connector. 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. At the boundary, there are multiple connectors labeled #1, #2, ..., #K. Connector #1 is connected to a box labeled 'Measurement equipment'. Connectors #2 and #K are connected to boxes labeled 'Load'. An arrow points to the boundary line with the label 'Transceiver array boundary connector TAB(n)'. + +**Figure D.1.1-1: Measuring system set-up for SAN type 1-H output power, output power dynamics, frequency error, EVM, unwanted emissions for a single *TAB connector*** + +![Figure D.1.1-2: Measuring system set-up for SAN type 1-H output power, output power dynamics, 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. At the boundary, there are multiple connectors labeled #1, #2, ..., #K. All these connectors are connected to a single large box labeled 'Measurement Equipment'. An arrow points to the boundary line with the label 'Transceiver array boundary connector TAB(n)'.](9af97997b7d3fbca90b8ddba0ea39c6c_img.jpg) + +Figure D.1.1-2: Measuring system set-up for SAN type 1-H output power, output power dynamics, 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. At the boundary, there are multiple connectors labeled #1, #2, ..., #K. All these connectors are connected to a single large box labeled 'Measurement Equipment'. An arrow points to the boundary line with the label 'Transceiver array boundary connector TAB(n)'. + +**Figure D.1.1-2: Measuring system set-up for SAN type 1-H output power, output power dynamics, frequency error, EVM, unwanted emissions for multiple *TAB connectors*** + +## D.1.2 Transmitter intermodulation for SAN type 1-H + +The requirement and the measuring system set-up are not applicable in this version of the specification. + +## D.1.3 Transmitter spurious emissions for SAN type 1-H + +*TAB connectors* may be connected to the measurement equipment singularly and tested one at a time (figure D.1.3-1), or may be tested simultaneously in groups (figure D.1.3-2) where the group size may range from two to all the *TAB connectors* which are subject to transmitter spurious emissions test. + +In all cases the measurement is per *TAB connector* but the measurement may be done in parallel. + +![Diagram of measuring system set-up for transmitter spurious emissions for a single TAB connector. 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 K connectors labeled #1, #2, ..., #K. Connector #1 is connected to a 'TX notch' block, which is then connected to 'Measurement equipment'. Connectors #2 through #K are each connected to a 'Load' block. An arrow points to the boundary line with the label 'Transceiver array boundary connector TAB(n)'.](d77263a08ee7c05fd8a0edf5b071b865_img.jpg) + +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 K connectors labeled #1, #2, ..., #K. Connector #1 is connected to a 'TX notch' block, which is then connected to 'Measurement equipment'. Connectors #2 through #K are each connected to a 'Load' block. An arrow points to the boundary line with the label 'Transceiver array boundary connector TAB(n)'. + +**Figure D.1.3-1: Measuring system set-up for transmitter spurious emissions for a single TAB connector** + +![Diagram of measuring system set-up for transmitter spurious emissions for multiple TAB connectors in parallel test. Similar to Figure D.1.3-1, but instead of a single 'Measurement equipment' block, there are K 'TX notch' blocks, one for each connector (#1, #2, ..., #K). All K 'TX notch' blocks are connected to a single, larger 'Measurement equipment' block on the far right. Connectors #2 through #K are also connected to 'Load' blocks. An arrow points to the boundary line with the label 'Transceiver array boundary connector TAB(n)'.](235956431f37eb6f426ad00290e52a08_img.jpg) + +Diagram of measuring system set-up for transmitter spurious emissions for multiple TAB connectors in parallel test. Similar to Figure D.1.3-1, but instead of a single 'Measurement equipment' block, there are K 'TX notch' blocks, one for each connector (#1, #2, ..., #K). All K 'TX notch' blocks are connected to a single, larger 'Measurement equipment' block on the far right. Connectors #2 through #K are also connected to 'Load' blocks. An arrow points to the boundary line with the label 'Transceiver array boundary connector TAB(n)'. + +**Figure D.1.3-2: Measuring system set-up for transmitter spurious emissions for multiple TAB connectors in parallel test** + +## D.1.4 Time alignment error for SAN type 1-H + +The requirement and the measuring system set-up are not applicable in this version of the specification. + +## D.2 SAN type 1-H receiver + +### D.2.1 Reference sensitivity level for SAN type 1-H + +![Diagram of measuring system set-up for SAN type 1-H reference sensitivity level test. It shows a transceiver unit array on the left, separated by a dashed line representing the transceiver array boundary. Inside the array, there are multiple connectors labeled #1, #2, ..., #K. Connector #1 is connected to a 'Signal generator for the wanted signal'. Connectors #2 and #K are connected to 'Load' blocks. An arrow points to the boundary line labeled 'Transceiver array boundary connector TAB(n)'.](39fbaf75053c08ab3bb2cbff5ad6ec67_img.jpg) + +transceiver array boundary + +#1 + +#2 + +⋮ + +#K + +Signal generator for the wanted signal + +Load + +Load + +transceiver unit array + +Transceiver array boundary connector TAB(n) + +Diagram of measuring system set-up for SAN type 1-H reference sensitivity level test. It shows a transceiver unit array on the left, separated by a dashed line representing the transceiver array boundary. Inside the array, there are multiple connectors labeled #1, #2, ..., #K. Connector #1 is connected to a 'Signal generator for the wanted signal'. Connectors #2 and #K are connected to 'Load' blocks. An arrow points to the boundary line labeled 'Transceiver array boundary connector TAB(n)'. + +Figure D.2.1-1: Measuring system set-up for SAN type 1-H reference sensitivity level test + +### D.2.2 Receiver dynamic range for SAN type 1-H + +![Diagram of measuring system set-up for SAN type 1-H dynamic range test. It shows a transceiver unit array on the left, separated by a dashed line representing the transceiver array boundary. Inside the array, there are multiple connectors labeled #1, #2, ..., #K. Connector #1 is connected to a 'Hybrid' block, which is then connected to two signal generators: 'Signal generator for the wanted signal' and 'Signal generator for the AWGN interfering signal'. Connectors #2 and #K are connected to 'Load' blocks. An arrow points to the boundary line labeled 'Transceiver array boundary connector TAB(n)'.](7478250c3f9a732a15bbd7d500d1c8f1_img.jpg) + +transceiver array boundary + +#1 + +#2 + +⋮ + +#K + +Hybrid + +Signal generator for the wanted signal + +Signal generator for the AWGN interfering signal + +Load + +Load + +transceiver unit array + +Transceiver array boundary connector TAB(n) + +Diagram of measuring system set-up for SAN type 1-H dynamic range test. It shows a transceiver unit array on the left, separated by a dashed line representing the transceiver array boundary. Inside the array, there are multiple connectors labeled #1, #2, ..., #K. Connector #1 is connected to a 'Hybrid' block, which is then connected to two signal generators: 'Signal generator for the wanted signal' and 'Signal generator for the AWGN interfering signal'. Connectors #2 and #K are connected to 'Load' blocks. An arrow points to the boundary line labeled 'Transceiver array boundary connector TAB(n)'. + +Figure D.2.2-1: Measuring system set-up for SAN type 1-H dynamic range test + +### D.2.3 Receiver adjacent channel selectivity and narrowband blocking for SAN type 1-H + +![Diagram of the measuring system set-up for SAN type 1-H adjacent channel selectivity and narrowband blocking test. It shows a transceiver unit array connected via a transceiver array boundary to a Hybrid and multiple Load units. Signal generators for wanted and interfering signals are connected through ATT1 and ATT2 respectively.](6cdb31bed6791fa0bd3fbc1e583b07ed_img.jpg) + +The diagram illustrates the test setup for adjacent channel selectivity and narrowband blocking. On the left, a dashed box labeled 'transceiver unit array' contains multiple units. A vertical dashed line labeled 'transceiver array boundary' separates this from the test equipment. At the boundary, there are connectors labeled #1, #2, ..., #K. Connector #1 is connected to a 'Hybrid' block. Connector #2 and connector #K are connected to 'Load' blocks. The 'Hybrid' block has two output ports on its right side. The top output port is connected to an 'ATT1' block, which is in turn connected to a 'Signal generator for the wanted signal'. The bottom output port is connected to an 'ATT2' block, which is connected to a 'Signal generator for the interfering signal'. An arrow points to the boundary line with the label 'Transceiver array boundary connector TAB(n)'. + +Diagram of the measuring system set-up for SAN type 1-H adjacent channel selectivity and narrowband blocking test. It shows a transceiver unit array connected via a transceiver array boundary to a Hybrid and multiple Load units. Signal generators for wanted and interfering signals are connected through ATT1 and ATT2 respectively. + +Figure D.2.3-1: Measuring system set-up for SAN type 1-H adjacent channel selectivity and narrowband blocking test + +### D.2.4 Receiver spurious emissions + +The requirement and the measuring system set-up are not applicable in this version of the specification. + +### D.2.5 Receiver In-channel selectivity for SAN type 1-H + +![Diagram of the measuring system set-up for SAN type 1-H in-channel selectivity test. It shows a transceiver unit array connected via a transceiver array boundary to a Hybrid and multiple Load units. A single signal generator for both wanted and interfering signals is connected to the Hybrid block.](d4735388eddeb40049070f8ab30921be_img.jpg) + +The diagram illustrates the test setup for in-channel selectivity. On the left, a dashed box labeled 'transceiver unit array' contains multiple units. A vertical dashed line labeled 'transceiver array boundary' separates this from the test equipment. At the boundary, there are connectors labeled #1, #2, ..., #K. Connector #1 is connected to a 'Hybrid' block. Connector #2 and connector #K are connected to 'Load' blocks. The 'Hybrid' block has one output port on its right side, which is connected to a 'Signal generator for the wanted signal and interfering signal'. An arrow points to the boundary line with the label 'Transceiver array boundary connector TAB(n)'. + +Diagram of the measuring system set-up for SAN type 1-H in-channel selectivity test. It shows a transceiver unit array connected via a transceiver array boundary to a Hybrid and multiple Load units. A single signal generator for both wanted and interfering signals is connected to the Hybrid block. + +Figure D.2.5-1: Measuring system set-up for SAN type 1-H in-channel selectivity test + +### D.2.6 Receiver intermodulation for SAN type 1-H + +The requirement and the measuring system set-up are not applicable in this version of the specification. + +## D.3 SAN type 1-H and type 1-O transmitter + +The OTA chamber configuration shown in this section is intended to be generic and may represent any suitable OTA chamber (e.g. far field anechoic chamber, Compact Antenna Test Range (CATR), near field chamber, Reverberation chamber). + +The link between the satellite and the Gateway is made in conducted mode. The Gateway equipment (modems, RF chain, commands, telemetries, etc.) may be partially or completely located outside the chamber. + +### D.3.1 Radiated transmit power, output power, output power dynamics, transmitted signal quality, OTA unwanted emissions, OTA transmitter spurious emissions + +![Diagram of the measurement setup for radiated transmit power, OTA output power dynamics, and OTA transmitted signal quality (SAN type 1-O).](8512afe2a50a7087c8b77a68dd354994_img.jpg) + +The diagram illustrates the measurement setup within a 'Test system enclosure' lined with anechoic chamber wave absorbers. Inside, a 'Satellite' is mounted on a 'Positioner' that allows for rotation. A 'Test system calibrated point' is marked at the center of the satellite. A 'Declared coordinate reference point and orientation' is indicated by a vertical dashed line passing through the center. The satellite's orientation is defined by angles $\theta$ (polar angle) and $\phi$ (azimuthal angle) relative to the reference point. 'Gateway equipment' is shown inside the enclosure, connected to the satellite. On the right side, a 'Test antenna' is positioned to receive signals from the satellite, and it is connected to 'Measurement equipment' located outside the enclosure. + +Diagram of the measurement setup for radiated transmit power, OTA output power dynamics, and OTA transmitted signal quality (SAN type 1-O). + +Figure D.3.1-1: Measurement set up for radiated transmit power, OTA output power dynamics and OTA transmitted signal quality (SAN type 1-O) + +## D.4 SAN type 1-H and type 1-O receiver + +The OTA chamber configurations shown in this section are intended to be generic and may represent any suitable OTA chamber (e.g. Far field anechoic chamber, Compact Antenna Test Range (CATR), Near field chamber). + +The link between the satellite and the Gateway is made in conducted mode. The Gateway equipment (modems, RF chain, commands, telemetries, etc.) may be partially or completely located outside the chamber. + +### D.4.1 OTA sensitivity and OTA reference sensitivity level + +![Diagram of measurement setup for OTA sensitivity and OTA reference sensitivity level.](037f0f683efaa7f7d98458c351d3ce6b_img.jpg) + +This diagram illustrates the measurement setup for OTA sensitivity and OTA reference sensitivity level. It features a 'Test system enclosure' with a jagged border. Inside, a 'Satellite' is mounted on a 'Positioner' that can rotate. A 'Test system calibrated point' is marked at the center of the satellite. A 'Declared coordinate reference point and orientation' is indicated by a vertical dashed line passing through the calibrated point. The satellite's orientation is defined by angles $\theta$ and $\phi$ . 'Gateway equipment' is connected to the satellite. On the right, a 'Test antenna' is positioned to receive signals from the satellite. This antenna is connected to a 'Signal generator for the wanted signal'. + +Diagram of measurement setup for OTA sensitivity and OTA reference sensitivity level. + +Figure D.4.1-1: Measurement set up for OTA sensitivity and OTA reference sensitivity level + +### D.4.2 OTA dynamic range, OTA adjacent channel selectivity + +![Diagram of measurement setup for OTA dynamic range.](88f5a639e0e8bae43a30c7ebe33752e5_img.jpg) + +This diagram illustrates the measurement setup for OTA dynamic range. It shows the same 'Test system enclosure' and internal components as the previous diagram: 'Satellite' on a 'Positioner', 'Test system calibrated point', 'Declared coordinate reference point and orientation' with angles $\theta$ and $\phi$ , and 'Gateway equipment'. The 'Test antenna' on the right is connected to a 'Coupler'. The 'Coupler' has two input paths: one from a 'Signal generator for the wanted signal' via 'Attenuator 1', and another from a 'Signal generator for the unwanted signal' via another 'Attenuator 1'. + +Diagram of measurement setup for OTA dynamic range. + +Figure D.4.2-1: Measurement set up for OTA dynamic range + +### D.4.3 OTA out-of-band blocking + +![Diagram of the measurement setup for general OTA out-of-band blocking. It shows a satellite on a positioner inside a test system enclosure. The satellite is connected to gateway equipment. Two test antennas, one in-band and one out-of-band, are connected to signal generators for wanted and unwanted signals respectively. The diagram includes labels for the test system calibrated point, declared coordinate reference point and orientation, and angles theta and phi.](bbd1d8687d2e06af9f71954d66034838_img.jpg) + +The diagram illustrates the measurement setup for general OTA out-of-band blocking. It features a satellite mounted on a positioner within a test system enclosure. The satellite is connected to gateway equipment. Two test antennas are positioned to receive signals from the satellite: one in-band and one out-of-band. The in-band antenna is connected to a signal generator for the wanted signal, and the out-of-band antenna is connected to a signal generator for the unwanted signal. The diagram also indicates the test system calibrated point, the declared coordinate reference point and orientation, and the angles $\theta$ and $\phi$ . + +Diagram of the measurement setup for general OTA out-of-band blocking. It shows a satellite on a positioner inside a test system enclosure. The satellite is connected to gateway equipment. Two test antennas, one in-band and one out-of-band, are connected to signal generators for wanted and unwanted signals respectively. The diagram includes labels for the test system calibrated point, declared coordinate reference point and orientation, and angles theta and phi. + +Figure D.4.3-1: Measurement set up for general OTA out-of-band blocking + +### D.5 Void + +## D.6 SAN type 1-H performance requirements + +### D.6.1 Performance requirements for PUSCH, single user PUCCH, PRACH on single antenna port in multipath fading conditions + +![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 for SAN with 1Rx. The diagram shows a transceiver unit array with K ports. Port #1 is connected to a circulator, which is then connected to a Channel Simulator and an AWGN Generator. Port #2 is connected to a Load. Port #K is connected to a Load. A SAN tester is connected to the Channel Simulator. A HARQ feedback line (only for PUSCH) is shown between the SAN tester and the transceiver unit array. The transceiver array boundary is indicated by a dashed line.](c28a32402d58c11a48dfffe91182e745_img.jpg) + +The diagram illustrates the functional setup for a Single Antenna Network (SAN) with one receive (1Rx) configuration. On the left, a dashed box labeled 'transceiver unit array' contains K ports, numbered #1, #2, ..., #K. A vertical dashed line labeled 'transceiver array boundary' separates the unit array from the external test equipment. Port #1 is connected to a circulator. The circulator's output is connected to two parallel blocks: 'Channel Simulator' and 'AWGN Generator'. Both of these blocks are connected to a 'SAN tester' block. Port #2 is connected to a 'Load' block. Port #K is also connected to a 'Load' block. A feedback line labeled 'HARQ feedback (only for PUSCH)' originates from the 'SAN tester' and returns to the 'transceiver unit array'. An arrow points to the connection point between the unit array and the boundary line, labeled 'Transceiver array boundary connector TAB(n)'. + +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 for SAN with 1Rx. The diagram shows a transceiver unit array with K ports. Port #1 is connected to a circulator, which is then connected to a Channel Simulator and an AWGN Generator. Port #2 is connected to a Load. Port #K is connected to a Load. A SAN tester is connected to the Channel Simulator. A HARQ feedback line (only for PUSCH) is shown between the SAN tester and the transceiver unit array. The transceiver array boundary is indicated by a dashed line. + +**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 for SAN with 1Rx** + +![Figure D.6.1-2: Functional set-up for performance requirements for PUSCH, single user PUCCH, PRACH on single antenna port in multipath fading conditions for SAN with Rx diversity (2 Rx case shown). The diagram shows a transceiver unit array with K ports. Port #1 is connected to a circulator, which is then connected to a Channel Simulator and an AWGN Generator. Port #2 is connected to a circulator, which is then connected to a Channel Simulator and an AWGN Generator. Port #K is connected to a Load. The outputs of the circulators for ports #1 and #2 are combined and connected to a SAN tester. A HARQ feedback line (only for PUSCH) is shown between the SAN tester and the transceiver unit array. The transceiver array boundary is indicated by a dashed line.](dcff3b4c32053e26f2c807df3c11b55b_img.jpg) + +This diagram shows the functional setup for a SAN with receive diversity, specifically a 2 Rx case. It features a 'transceiver unit array' with K ports (#1, #2, ..., #K) separated from the test equipment by a 'transceiver array boundary'. Port #1 connects to a circulator, which is linked to a 'Channel Simulator' and an 'AWGN Generator'. Port #2 connects to another circulator, which is also linked to a 'Channel Simulator' and an 'AWGN Generator'. The outputs from both circulators are combined via a second circulator and then connected to the 'SAN tester'. Port #K is connected to a 'Load'. A 'HARQ feedback (only for PUSCH)' line is provided from the 'SAN tester' back to the unit array. The connection point at the boundary is labeled 'Transceiver array boundary connector TAB(n)'. + +Figure D.6.1-2: Functional set-up for performance requirements for PUSCH, single user PUCCH, PRACH on single antenna port in multipath fading conditions for SAN with Rx diversity (2 Rx case shown). The diagram shows a transceiver unit array with K ports. Port #1 is connected to a circulator, which is then connected to a Channel Simulator and an AWGN Generator. Port #2 is connected to a circulator, which is then connected to a Channel Simulator and an AWGN Generator. Port #K is connected to a Load. The outputs of the circulators for ports #1 and #2 are combined and connected to a SAN tester. A HARQ feedback line (only for PUSCH) is shown between the SAN tester and the transceiver unit array. The transceiver array boundary is indicated by a dashed line. + +**Figure D.6.1-2: Functional set-up for performance requirements for PUSCH, single user PUCCH, PRACH on single antenna port in multipath fading conditions for SAN with Rx diversity (2 Rx case shown)** + +NOTE 1: 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 and PRACH in static conditions + +![Functional set-up for performance requirements for PUSCH and PRACH in static conditions for SAN with 1Rx case shown. The diagram shows a 'transceiver unit array' on the left, separated by a 'transceiver array boundary' from the external components. At the boundary, there are connectors labeled #1, #2, ..., #K. Connector #1 is connected to a circulator. The circulator's output is connected to a 'SAN tester' and an 'AWGN Generator'. Connector #2 is connected to a 'Load'. Connector #K is also connected to a 'Load'. An arrow points to the boundary line with the label 'Transceiver array boundary connector TAB(n)'.](0b8f0df92a831a94cdac664d8b05f0ec_img.jpg) + +Functional set-up for performance requirements for PUSCH and PRACH in static conditions for SAN with 1Rx case shown. The diagram shows a 'transceiver unit array' on the left, separated by a 'transceiver array boundary' from the external components. At the boundary, there are connectors labeled #1, #2, ..., #K. Connector #1 is connected to a circulator. The circulator's output is connected to a 'SAN tester' and an 'AWGN Generator'. Connector #2 is connected to a 'Load'. Connector #K is also connected to a 'Load'. An arrow points to the boundary line with the label 'Transceiver array boundary connector TAB(n)'. + +Figure D.6.2-1: Functional set-up for performance requirements for PUSCH and PRACH in static conditions for SAN with 1Rx case shown + +![Functional set-up for performance requirements for PUSCH and PRACH in static conditions for SAN with Rx diversity (2 Rx case shown). This diagram is similar to Figure D.6.2-1 but includes an additional circulator. The output of the first circulator (connected to connector #1) is split: one path goes to the 'SAN tester' and the other goes to a second circulator. The second circulator's output is also connected to the 'SAN tester'. The second circulator's input is connected to an 'AWGN Generator'. Connector #2 is connected to another circulator, whose output is connected to a second 'AWGN Generator'. Connector #K remains connected to a 'Load'. The 'Transceiver array boundary connector TAB(n)' label and arrow are also present.](be2dee4acf57ae6f4e3a015e28bcfb61_img.jpg) + +Functional set-up for performance requirements for PUSCH and PRACH in static conditions for SAN with Rx diversity (2 Rx case shown). This diagram is similar to Figure D.6.2-1 but includes an additional circulator. The output of the first circulator (connected to connector #1) is split: one path goes to the 'SAN tester' and the other goes to a second circulator. The second circulator's output is also connected to the 'SAN tester'. The second circulator's input is connected to an 'AWGN Generator'. Connector #2 is connected to another circulator, whose output is connected to a second 'AWGN Generator'. Connector #K remains connected to a 'Load'. The 'Transceiver array boundary connector TAB(n)' label and arrow are also present. + +Figure D.6.2-2: Functional set-up for performance requirements for PUSCH and PRACH in static conditions for SAN with Rx diversity (2 Rx case shown) + +### D.6.3 Performance requirements for UL timing adjustment + +![Functional set-up for performance requirement for UL timing adjustment diagram](3893e26cb0b95e076fdc8953d2db0072_img.jpg) + +The diagram illustrates the functional set-up for UL timing adjustment. On the left, a dashed box labeled 'transceiver unit array' contains multiple transceivers. The boundary of this array is marked by a vertical dashed line labeled 'transceiver array boundary'. Transceivers are labeled #1, #2, ..., #K. Transceiver #1 is connected to a circulator, which is connected to an 'AWGN Generator' and a 'SAN tester'. Transceiver #2 is also connected to a circulator and an 'AWGN Generator'. Transceiver #K is connected to a 'Load'. A line labeled 'Transceiver array boundary connector TAB(n)' points to the boundary between the unit array and the external components. A feedback line labeled 'HARQ feedback (only for PUSCH)' connects the 'SAN tester' back to the transceiver unit array. The 'SAN tester' is connected to 'Stationary UE' and 'Moving UE'. + +Functional set-up for performance requirement for UL timing adjustment diagram + +Figure D.6.3-1: Functional set-up for performance requirement for UL timing adjustment + +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.7 SAN type 1-O performance requirements + +![Measurement set up for single TX, single demodulation branch radiated performance requirements diagram](aa2c37b4b3f732603f944bbda641b722_img.jpg) + +The diagram shows the measurement set-up for single TX, single demodulation branch radiated performance requirements. On the left, a 'Signal generator for the AWGN signal' is connected to 'ATT1', which is connected to a 'Hybrid'. A 'Signal generator for the wanted signal' is connected to 'Fading channel emulator #1', which is connected to 'ATT2', which is also connected to the 'Hybrid'. The 'Hybrid' is connected to a 'PA' (Power Amplifier), which is connected to a 'Test antenna'. The 'Test antenna' is inside a 'Test system enclosure' with a jagged border. Inside the enclosure, there is a 'SAN' (Stationary User Equipment) with a coordinate system showing angles $\theta$ and $\phi$ . A label 'SAN declared coordinate reference point and orientation' points to the SAN's position and orientation. + +Measurement set up for single TX, single demodulation branch radiated performance requirements diagram + +Figure D.7-1: Measurement set up for single TX, single demodulation branch radiated performance requirements + +![Figure D.7-2: Measurement set up for single TX, dual polarization radiated performance requirements. The diagram shows a signal generator for the first AWGN signal connected to ATT1, and a signal generator for the wanted signal connected to Fading channel emulator #1 and Fading channel emulator #2. These emulators are connected to ATT2 and ATT3 respectively. Both ATT1 and ATT2/ATT3 are connected to Hybrid 1. Hybrid 1 is connected to PA 1, which is connected to Test antenna polarization A. The signal generator for the second AWGN signal is connected to ATT4, which is connected to Hybrid 2. Hybrid 2 is connected to PA 2, which is connected to Test antenna polarization B. Both antennas are inside a Test system enclosure containing a SAN (Spatial Antenna Network) with a coordinate reference point and orientation.](7c19fc92dc74a74ec346d46bc39a3946_img.jpg) + +Figure D.7-2: Measurement set up for single TX, dual polarization radiated performance requirements. The diagram shows a signal generator for the first AWGN signal connected to ATT1, and a signal generator for the wanted signal connected to Fading channel emulator #1 and Fading channel emulator #2. These emulators are connected to ATT2 and ATT3 respectively. Both ATT1 and ATT2/ATT3 are connected to Hybrid 1. Hybrid 1 is connected to PA 1, which is connected to Test antenna polarization A. The signal generator for the second AWGN signal is connected to ATT4, which is connected to Hybrid 2. Hybrid 2 is connected to PA 2, which is connected to Test antenna polarization B. Both antennas are inside a Test system enclosure containing a SAN (Spatial Antenna Network) with a coordinate reference point and orientation. + +**Figure D.7-2: Measurement set up for single TX, dual polarization radiated performance requirements** + +![Figure D.7-3: Measurement set up for UL timing adjustment, single TX, dual polarization radiated performance requirements. This diagram is similar to Figure D.7-2 but includes a 'Signal generator for stationary UE' and a 'Signal generator for moving UE'. The stationary UE signal is connected to Hybrid 2, which is then connected to ATT2 and ATT3. The moving UE signal is connected to Hybrid 3, which is connected to PA 2 and Test antenna polarization B. A HARQ feedback + TA commands line is shown between the SAN and the moving UE signal generator.](ff3a3d26b4b40920cf1377205fb08445_img.jpg) + +Figure D.7-3: Measurement set up for UL timing adjustment, single TX, dual polarization radiated performance requirements. This diagram is similar to Figure D.7-2 but includes a 'Signal generator for stationary UE' and a 'Signal generator for moving UE'. The stationary UE signal is connected to Hybrid 2, which is then connected to ATT2 and ATT3. The moving UE signal is connected to Hybrid 3, which is connected to PA 2 and Test antenna polarization B. A HARQ feedback + TA commands line is shown between the SAN and the moving UE signal generator. + +**Figure D.7-3: Measurement set up for UL timing adjustment, single TX, dual polarization radiated performance requirements** + +The OTA chambers shown in figures D.7-1, D.7-2, D.7-3 and D.7-4 are intended to be generic and can be replaced with any suitable OTA chamber (e.g. far field anechoic chamber, CATR, etc.). The PA(s) depicted in figures D.7-1, D.7-2, and D.7-3 is optional. Fading channel emulators are included when needed according to the requirement description. + +NOTE: The HARQ Feedback (only for PUSCH) could be done as an RF feedback or as a digital feedback. The HARQ Feedback should be error free. + +## Annex E (normative): Characteristic of interfering signal + +The interfering signal shall be a PUSCH or PDSCH 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 [8]. Mapping of PUSCH or PDSCH modulation to receiver requirement are specified in table E-1. + +**Table E-1: Modulation of the interfering signal** + +| Receiver requirement | Modulation | Interfering signal | Clauses | +|----------------------------------|------------|--------------------|---------| +| In-channel selectivity | 16QAM | PUSCH | 7.8 | +| OTA in-channel selectivity | | | 10.9 | +| Adjacent channel selectivity | QPSK | PDSCH | 7.4.1 | +| OTA adjacent channel selectivity | | | 10.5.1 | + +--- + +## 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. + +#### G.2.1 Delay profiles + +The delay profiles are simplified from the TR 38.811 [17] 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 [17]. +- 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 [11]. +- 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. + +### G.2.1.1 Delay profiles for FR1 + +The delay profiles for FR1 are selected to be representative of NLOS and LOS scenarios. 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 and table G.2.1.1-3. + +**Table G.2.1.1-1: Delay profiles for SAN 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 ns | 5 ns | +| NTN-TDLC5 | 2 | 5 ns | 60 ns | 5 ns | + +**Table G.2.1.1-2: NTN-TDLA100 (DS = 100 ns)** + +| Tap # | Delay (ns) | Power (dB) | Fading distribution | +|-------|------------|------------|---------------------| +| 1 | 0 | 0 | Rayleigh | +| 2 | 110 | -4.7 | | +| 3 | 285 | -6.5 | | + +**Table G.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 | + +NOTE: The first tap follows a Rician distribution with a K-factor of $K_1 = 8.05$ dB and a mean power of 0dB + +### 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., NTN-TDLA- or NTN-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 | +|------------------|-------------|---------------------------| +| NTN-TDLA100-200 | NTN-TDLA100 | 200 Hz | +| NTN-TDLC5-200 | NTN-TDLC5 | 200 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 SAN 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 SAN 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 SAN. + +**Table G.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 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 | +|----------------|--------------------| +| UE correlation | $R_{UE} = 1$ | + +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 SAN and UE respectively. + +**Table G.2.3.1.1-3: $R_{spat}$ correlation matrices** + +| | | +|----------|--| +| 1x1 case | | +| 1x2 case | | + +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 and according to . + +#### 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. + +**Table G.2.3.1.2-2: MIMO correlation matrices for high correlation** + +| | | +|----------|---------------------------------------------------------------| +| 1x1 case | | +| 1x2 case | $R_{high} = \begin{pmatrix} 1 & 0.9 \\ 0.9 & 1 \end{pmatrix}$ | + +**Table G.2.3.1.2-3: MIMO correlation matrices for medium correlation** + +| | | +|----------|-----| +| 1x1 case | N/A | +| 1x2 case | N/A | + +**Table G.2.3.1.2-4: MIMO correlation matrices for low correlation** + +| | | +|----------|--| +| 1x1 case | | +| 1x2 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.3 Moving propagation conditions + +Figure G.3-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 to Equation (G.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 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.3-1. + +![Figure G.3-1: Moving propagation conditions diagram. It shows a horizontal timeline with a reference point 'Ref' at time t0. A triangle labeled 'Δτ' is positioned between t0 and t1. At time t1, there is a dashed vertical arrow pointing up to a box labeled 'P1'. Further to the right, there are two more dashed vertical arrows of decreasing height, representing subsequent taps of a channel impulse response.](345a37f4d6b16c98368c8144e67313d0_img.jpg) + +Figure G.3-1: Moving propagation conditions diagram. It shows a horizontal timeline with a reference point 'Ref' at time t0. A triangle labeled 'Δτ' is positioned between t0 and t1. At time t1, there is a dashed vertical arrow pointing up to a box labeled 'P1'. Further to the right, there are two more dashed vertical arrows of decreasing height, representing subsequent taps of a channel impulse response. + +**Figure G.3-1: Moving propagation conditions** + +$$(G.3-1)$$ + +**Table G.3-1: Parameters for UL timing adjustment** + +| Parameter | Scenario X | +|----------------|--------------------------------------------------------------| +| Channel model | Stationary UE: AWGN
Moving UE: NTN-TDLA100-200 | +| UE speed | 120 km/h | +| CP length | Normal | +| A | 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}$ | + +--- + +## Annex H (normative): In-channel Tx test + +--- + +### 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 $s_{ideal}$ 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 box labeled 'Reference point for EVM measurement' has a dashed arrow pointing to the Per-subcarrier Amplitude/phase correction block.](29178b001cb4c04e0c5ab60662ce5d80_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] + Pre_post[Pre-/post FFT time / frequency synchronization] -.-> Remove_CP + Pre_post -.-> FFT + Pre_post -.-> 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 box labeled 'Reference point for EVM measurement' has a dashed arrow pointing 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 , + +- , and +- . + +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 SAN 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 and : + +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 , 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 is a Dirac peak and that the correlation between the ideal signal 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 . This subset of samples is called . + +From the acquired samples one timing can be derived. + +The timing of the centre is determined according to the cyclic prefix length of the OFDM symbols. For normal CP, there are two values for in a 1 ms period: + +- = length of cyclic prefix / 2, +- = Longer CP length - 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: + +- = 144 within the CP of length 288 for OFDM symbols 1 to 13 of a slot, +- = 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 with the FFT window timing . The result is called . 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 is the number of slots in a 10 ms measurement interval for FDD. + +For the example used in the annex, and . + +## H.6 Post-FFT equalisation + +Perform FFTs on $y$ , one for each OFDM symbol within 10 ms measurement interval with the FFT window timing to produce an array of samples, $y_t$ in the time axis $t$ by $FFT\ size$ in the frequency axis $f$ . + +For the example in the annex, 280 FFTs are performed on $y$ . The result is an array of samples, 280 in the time axis by 4096 in the frequency axis. + +The equalizer coefficients $\hat{h}$ and $\hat{p}$ 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{h}$ 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 $y_t$ for each demodulation reference signal subcarrier $f$ . + +3. The equalizer coefficients for amplitude and phase $\hat{h}$ and $\hat{p}$ 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}$ and $\hat{p}$ to compute coefficients, $\hat{h}$ and $\hat{p}$ , for each subcarrier. + +![Figure H.6-1: Reference subcarrier smoothing in the frequency domain. The figure contains two diagrams, A and B, illustrating moving averaging for reference subcarriers. Diagram A shows the process at the channel edge where the window size changes. Diagram B shows the process when the number of available reference subcarriers is smaller than the moving average window size.](bf15a4a25f6e71dea348cde412f1df55_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 H.6-1: Reference subcarrier smoothing in the frequency domain. The figure contains two diagrams, A and B, illustrating moving averaging for reference subcarriers. Diagram A shows the process at the channel edge where the window size changes. Diagram B shows the process when 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 , according to the timing and , using the equalizer coefficients from H.6. + +The equivalent ideal samples are calculated from (annex H.2.2) and are called . + +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, +- $\mathcal{S}_t$ is the set of subcarriers within the resource blocks with the considered modulation scheme being active in symbol $t$ , +- $\tilde{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_{\text{slots}}$ slots where $N_{\text{slots}}$ 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_{\text{RB}}$ 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 $\text{EVM}_{\text{low}}$ is calculated using $\text{EVM}_{i,l}$ in the expressions above and $\text{EVM}_{\text{high}}$ is calculated using $\text{EVM}_{i,h}$ in the calculation where ( $l$ and $h$ , low and high; where low is the timing $t_{\text{low}}$ and high is the timing $t_{\text{high}}$ ). + +Thus: + +The resulting $\text{EVM}_{\text{avg}}$ is compared against the limit. + +--- + +## Annex I (informative): Change history + +| Change history | | | | | | | | +|----------------|----------------|------------|----|-----|-----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-05 | RAN4#103-e | R4-2208251 | | | | Specification Skeleton | 0.0.1 | +| 2022-08 | RAN4#104-e | R4-2211688 | | | | Agreed Text Proposal in RAN4 #104-e:
R4-2214833 , "TP for TS 38.181 – Clause 6.6.3 ACLR"
R4-2214834 , "TP for TS 38.181 – Clause 6.5.3 EVM" | 0.1.0 | +| 2022-10 | RAN4#104-bis-e | R4-2215802 | | | | R4-2215339 , "TP for TS 38.181 - Clause 6.5.3 EVM"
R4-2215397 , "TP for TS 38.181: Clause 1 Scope, Clause 2 References and Clause 3 Definition of terms, symbols and abbreviations"
R4-2215399 , "TP for TS 38.181: Clause 4.6 Manufacturer declarations"
R4-2215401 , "TP for TS 38.181: Clause 4.9 RF channels and test models"
R4-2215402 , "TP for TS 38.181: Clause 6.1 General and Clause 6.2 Satellite Access Node output power"
R4-2215403 , "TP for TS 38.181: Clause 7.1 General and Clause 7.2 Reference sensitivity level"
R4-2215404 , "TP for TS 38.181: Clause 9.1 General"
R4-2215405 , "TP for TS 38.181: Clause 10.1 General and Clause 10.2 OTA sensitivity"
R4-2215406 , "TP for TS 38.181: A.1 FRCs for RF Rx requirement (QPSK, R=1/3) and A.2 FRCs for dynamic range (16QAM, R=2/3)"
R4-2215408 , "TP for TS 38.181: Annex H In-channel Tx test"
R4-2215409 , "TP for TS 38.181: Annex I Transmitter spatial emissions declaration"
R4-2215410 , "TP for TS 38.181: Annex K Measuring noise close to the noise-floor"
R4-2216489 , "TS 38.181: TP on clause 5"
R4-2216563 , "TP for TS 38.181: Section 7.6~7.8"
R4-2216565 , "TP for TS 38.181: Section 10.4"
R4-2216566 , "TP for TS 38.181: Section 10.7~10.9"
R4-2217321 , "TP for TS 38.181 - Clause 6.6.5 Spurious Emissions"
R4-2217322 , "TP for TS 38.181 - Annex D"
R4-2217323 , "TP for TS 38.181: Clause 4.1 Measurement uncertainties and test requirements"
R4-2217324 , "TP for TS 38.181: Annex F Calibration"
R4-2217325 , "TP to TS 38.181 – Clauses 4.10 and 4.11"
R4-2217326 , "TP to TS 38.181 – Clause 7.4 In-band selectivity and blocking"
R4-2217333 , "TP for TS 38.181: Section 6.3"
R4-2217334 , "TP for TS 38.181: Section 7.3"
R4-2217335 , "TP for TS 38.181: Section 9.4"
R4-2217336 , "TP to TS 38.181: General test conditions and declarations (4.2 - 4.5)"
R4-2217337 , "TP to TS 38.181: occupied bandwidth (6.6.1, 6.6.2)"
R4-2217338 , "TP to TS 38.181: Operating band unwanted emissions (6.6.4)"
R4-2217339 , "TP to TS 38.181: Out-of-band blocking (7.5)"
R4-2217340 , "TP to TS 38.181: OTA occupied bandwidth (9.7.1, 9.7.2)"
R4-2217341 , "TP to TS 38.181: OTA ACLR (9.7.3)"
R4-2217342 , "TP to TS 38.181: OTA OBUE (9.7.4)"
R4-2217343 , "TP to TS 38.181: OTA out-of-band blocking (10.6)"
R4-2217503 , "TP for TS 38.181: Clause 4.7 Test configurations and Clause 4.8 Applicability of requirements"
R4-2217508 , "TP to TS 38.181 – Clause 10.5 In-band selectivity and blocking"
R4-2217350 , "pCR on FRC of NTN SAN performance requirements (TS38.181, Rel-17)"
R4-2217354 , "pCR on NTN SAN PUSCH performance requirements (TS38.181, Rel-17)"
R4-2217357 , "pCR on SAN PUCCH radiated performance requirements (TS38.181, Rel-17)"
R4-2217358 , "pCR on NTN SAN PUCCH performance requirements (TS38.181, Rel-17)"
R4-2217359 , "pCR on SAN PRACH radiated performance requirements (TS38.181, Rel-17)"
R4-2217361 , "pCR on NTN SAN PRACH performance requirements (TS38.181, Rel-17)" | 0.2.0 | + +| | | | | | | | | +|---------|----------|------------|--|--|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------| +| 2022-11 | RAN4#105 | R4-2218455 | | | | R4-2219833 , "TP to TS 38.181: Clause 10.3 OTA Reference sensitivity"
R4-2219835 , "TS 38.181: TP on Annex C"
R4-2220230 , "TP for TS 38.181 - Annex D Updates"
R4-2220231 , "TP for TS 38.181: TP on Annex B"
R4-2220232 , "TP to TS 38.181: Annex E"
R4-2220234 , "TP for TS 38.181 - Clause 6.5 Transmitted signal quality"
R4-2220235 , "TP for TS 38.181: Remove co-location requirement related content"
R4-2220236 , "TP for TS 38.181 - Clause 9.6 OTA transmitted signal quality"
R4-2220237 , "TP for TS 38.181 - Clause 9.7.5 OTA transmitter spurious emissions"
R4-2220238 , "TP for TS 38.181 - Clauses 9.2 Radiated transmit power and 9.3 OTA SAN output power"
R4-2220290 , "TP for TS 38.181: Clause 4.1.2 Acceptable uncertainty of Test System"
R4-2220292 , "TP for TS 38.181 - DUT size for applicable MU values"
R4-2220293 , "TP to TS 38.181: Annex J"
R4-2220305 , "TP for TS 38.181 - Corrections to Clause 6.6 Unwanted emissions"
R4-2220306 , "TP for TS 38.181 - Corrections to Clause 9.7 OTA unwanted emissions"
R4-2219665 , "pCR on FRC of NTN SAN performance requirements (TS38.181, Rel-17)"
R4-2220162 , "TP for TS 38.181 - Clauses 8.1 and 11.1 General performance parts"
R4-2220165 , "pCR on SAN PUSCH conducted performance requirements (TR38.181, Rel-17)"
R4-2220167 , "pCR on NTN SAN PUSCH performance requirements (TS38.181, Rel-17)"
R4-2220169 , "pCR on SAN PUCCH radiated performance requirements (TR38.181, Rel-17)"
R4-2220170 , "pCR on NTN SAN PUCCH performance requirements (TS38.181, Rel-17)"
R4-2220171 , "pCR on SAN PRACH radiated performance requirements (TR38.181, Rel-17)"
R4-2220173 , "pCR on NTN SAN PRACH performance requirements (TS38.181, Rel-17)" | 0.3.0 | +| 2022-12 | RAN#98-e | RP-222880 | | | | Presented to TSG RAN for approval (specification v1.0.0) | 1.0.0 | + +| Change history | | | | | | | | +|----------------|----------|------------|----|-----|-----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-12 | RAN#98-e | | | | | MCC - Editorial changes | 1.0.1 | +| 2023-03 | RAN4#106 | R4-2300604 | | | | R4-2302937 , "TP for TS 38.181: On general and annex parts for RF"
R4-2300571 , "TP for TS 38.181: On conducted transmitter and receiver characteristics in clause 6 and 7"
R4-2300572 , "TP for TS 38.181: On radiated transmitter and receiver characteristics in clause 9 and 10"
R4-2302938 , "TP to TS 38.181: Multiple corrections (test requirements, declarations, annexes)"
R4-2302867 , "TP for TS 38.181 - Clause 4.1 Measurement uncertainties and test requirements"
R4-2302845 , "pCR on NTN SAN performance requirements (TS38.181, Rel-17)" | 1.0.2 | +| 2023-03 | RAN#99 | RP-230423 | | | | Presented to TSG RAN for approval (specification v2.0.0) | 2.0.0 | + +| Change history | | | | | | | | +|-----------------------|----------------|-------------|-----------|------------|------------|-----------------------------------------------------------------------------------|--------------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2023-03 | RAN#99 | | | | | Approved by plenary – Rel-17 spec under change control | 17.0.0 | +| 2023-06 | RAN#100 | RP-231344 | 0003 | 1 | F | Corrections to SAN TS 38.181 | 17.1.0 | +| 2023-09 | RAN#101 | RP-232494 | 0004 | | F | CR for TS 38.181, Correction on antenna connector | 17.2.0 | +| 2023-09 | RAN#101 | RP-232494 | 0005 | 1 | F | CR for TS 38.181, Correction on out-of-band emissions | 17.2.0 | +| 2023-09 | RAN#101 | RP-232494 | 0006 | 1 | F | CR to 38.181: Out-of-band emissions requirements | 17.2.0 | +| 2023-09 | RAN#101 | RP-232494 | 0007 | 1 | F | CR to 38.181: Application of unwanted emissions requirements | 17.2.0 | +| 2023-09 | RAN#101 | RP-232494 | 0008 | | F | CR to 38.181: Characteristic of interfering signal | 17.2.0 | +| 2023-09 | RAN#101 | RP-232494 | 0010 | | F | [NR_NTN_solutions-Perf] CR on NTN SAN performance requirements (TS38.181, Rel-17) | 17.2.0 | +| 2023-12 | RAN#102 | RP-233349 | 0011 | 1 | F | CR for TS 38.181, Correction on out-of-band emissions | 17.3.0 | + +| Change history | | | | | | | | +|-----------------------|----------------|-------------|-----------|------------|------------|--------------------------------------------------------------|--------------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2023-12 | RAN#102 | RP-233366 | 0012 | 1 | B | CR for TS 38.181, On introduction of the satellite L-/S-band | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38202/07b17a620c75522d53916a11e12d1bff_img.jpg b/marked/Rel-18/38_series/38202/07b17a620c75522d53916a11e12d1bff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b80020896f75fc5b575475eb8739b9fc82d25a2 --- /dev/null +++ b/marked/Rel-18/38_series/38202/07b17a620c75522d53916a11e12d1bff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:885329de7f67b53a7015832be405a1afcfb97f2df25ba9fca4c08fedf2bb9ace +size 98223 diff --git a/marked/Rel-18/38_series/38202/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-18/38_series/38202/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9cd6036963c70c06dff369d0db6e471a09d47fc --- /dev/null +++ b/marked/Rel-18/38_series/38202/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9be4d57fc193d927d618e511f99769f4366b9c14450f396a0ed63175b2fc1fd4 +size 60463 diff --git a/marked/Rel-18/38_series/38202/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-18/38_series/38202/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc3a1fd9f5f635f68585ad93460b28032241ff98 --- /dev/null +++ b/marked/Rel-18/38_series/38202/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4536a9ff872218159ed8604bf11bca0e73e88b86f9f19a7232d8628a898bcaac +size 91582 diff --git a/marked/Rel-18/38_series/38202/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38202/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a5aadb8d71b4957d48c0d177f99f7a2bebb33f1 --- /dev/null +++ b/marked/Rel-18/38_series/38202/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce7263e4053c38a94b9e6ed628261e69830522f1936ac8dc0606c4a9d9bb1c00 +size 9539 diff --git a/marked/Rel-18/38_series/38202/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38202/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dcbc8c42ecf57a5be191dc7088bdcdef679d271d --- /dev/null +++ b/marked/Rel-18/38_series/38202/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cdd7637ee213707504c42f24c2e3f5a837634a6da310aa3a151608c444cb35de +size 5744 diff --git a/marked/Rel-18/38_series/38202/7a0db9703b68b3d06cdaeefc084c0006_img.jpg b/marked/Rel-18/38_series/38202/7a0db9703b68b3d06cdaeefc084c0006_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..764a069457ac714eb30d18c163dbd42e262c4577 --- /dev/null +++ b/marked/Rel-18/38_series/38202/7a0db9703b68b3d06cdaeefc084c0006_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e3b27673f31062e71ac30eb00713149567d0e02e42fc76b495e2a84955de7ec0 +size 42047 diff --git a/marked/Rel-18/38_series/38202/9791722d75115ddcc599b07d7bc35d73_img.jpg b/marked/Rel-18/38_series/38202/9791722d75115ddcc599b07d7bc35d73_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..516379363b9899facba35b9044d30cce65f48bde --- /dev/null +++ b/marked/Rel-18/38_series/38202/9791722d75115ddcc599b07d7bc35d73_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:13a7eae01d2645dcf9a968655253c97a9d0f8f5906744aa360da826cc5253564 +size 99378 diff --git a/marked/Rel-18/38_series/38202/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-18/38_series/38202/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c2a37cf92c79c1bc75586b984fc54f5fd540c69 --- /dev/null +++ b/marked/Rel-18/38_series/38202/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:345752f53ae2f3e77944734bf6901cfa21a0c5ef51d7dc5c5523f84ec2b4f107 +size 71795 diff --git a/marked/Rel-18/38_series/38202/raw.md b/marked/Rel-18/38_series/38202/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..03ac5835170bcf3453508224cf40472d3830ae6d --- /dev/null +++ b/marked/Rel-18/38_series/38202/raw.md @@ -0,0 +1,599 @@ + + +# 3GPP TS 38.202 V18.1.0 (2023-12) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Services provided by the physical layer (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 + +## --- **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 ..... | 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 Services and functions of the physical layer..... | 6 | +| 4.1 General ..... | 6 | +| 4.2 Overview of L1 functions ..... | 6 | +| 5 Model of physical layer of the UE..... | 6 | +| 5.1 Uplink model..... | 7 | +| 5.1.1 Uplink shared channel..... | 7 | +| 5.1.2 Random access channel..... | 7 | +| 5.2 Downlink model..... | 8 | +| 5.2.1 Downlink shared channel ..... | 8 | +| 5.2.2 Broadcast channel..... | 8 | +| 5.2.3 Paging channel..... | 9 | +| 5.3 Sidelink model..... | 10 | +| 5.3.1 Sidelink shared channel..... | 10 | +| 5.3.2 Broadcast channel..... | 11 | +| 6 Simultaneous transmission and reception of physical channels and physical signals ..... | 12 | +| 6.1 Uplink..... | 12 | +| 6.2 Downlink..... | 13 | +| 6.3 Sidelink..... | 15 | +| 7 Measurements provided by the physical layer..... | 17 | +| 7.1 UE measurements..... | 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 a technical specification of the services provided by the physical layer of 5G-NR to upper layers. + +# --- 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" +- [6] 3GPP TS 38.214: "NR; Physical layer procedures for data" +- [7] 3GPP TS 38.215: "NR; Physical layer measurements" +- [8] 3GPP TS 38.306: "NR; User Equipment (UE) radio access capabilities" + +# --- 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]. + +For the purposes of the present document, the following abbreviations apply: + +| | | +|-------|-----------------------------------| +| ARQ | Automatic Repeat Request | +| BCH | Broadcast Channel | +| CA | Carrier Aggregation | +| CRC | Cyclic Redundancy Check | +| DC | Dual Connectivity | +| DL | Downlink | +| FEC | Forward Error Correction | +| GF | Grant-Free | +| MAC | Medium Access Control | +| MIMO | Multiple Input Multiple Output | +| PBCH | Physical Broadcast Channel | +| PCH | Paging Channel | +| PDCCH | Physical Downlink Control Channel | + +| | | +|-------|------------------------------------| +| PDSCH | Physical Downlink Shared Channel | +| PRACH | Physical Random Access Channel | +| PUCCH | Physical Uplink Control Channel | +| PUSCH | Physical Uplink Shared Channel | +| RACH | Random Access Channel | +| RF | Radio Frequency | +| RNTI | Radio Network Temporary Identifier | +| SCH | Shared Channel | +| SI | System Information | +| SPS | Semi-Persistent Scheduling | +| SRS | Sounding Reference Signal | +| TPC | Transmit Power Control | +| UL | Uplink | + +# --- 4 Services and functions of the physical layer + +## 4.1 General + +The physical layer offers data transport services to higher layers. + +The access to these services is through the use of transport channels via the MAC sub-layer. + +A transport block is defined as the data delivered by MAC layer to the physical layer and vice versa. + +## 4.2 Overview of L1 functions + +As mentioned in [2, TS 38.201], the physical layer is expected to perform the following functions to provide the data transport service: + +- Error detection on the transport channel and indication to higher layers; +- FEC encoding/decoding of the transport channel; +- Hybrid ARQ soft-combining; +- Rate matching of the coded transport channel to physical channels; +- Mapping of the coded transport channel onto physical channels; +- Power weighting of physical channels; +- Modulation and demodulation of physical channels; +- Frequency and time synchronisation; +- Radio characteristics measurements and indication to higher layers; +- Multiple Input Multiple Output (MIMO) antenna processing; +- RF processing. + +L1 functions are modelled for each transport channel in clause 5. + +# --- 5 Model of physical layer of the UE + +The 5G-NR physical-layer model captures those characteristics of the 5G-NR physical-layer that are relevant from the point-of-view of higher layers. More specifically, the physical-layer model captures: + +- The structure of higher-layer data being passed down to or up from the physical layer; +- The means by which higher layers can configure the physical layer; + +- The different indications (error indications, channel-quality indications, etc.) that are provided by the physical layer to higher layers. + +## 5.1 Uplink model + +### 5.1.1 Uplink shared channel + +The physical-layer model for Uplink Shared Channel transmission is described based on the corresponding PUSCH physical-layer-processing chain, see Figure 5.1.1-1. Processing steps that are relevant for the physical-layer model, e.g. in the sense that they are configurable by higher layers, are highlighted in blue. + +- Higher-layer data passed to/from the physical layer +- CRC and transport-block-error indication +- FEC and rate matching +- Data modulation +- Mapping to physical resource +- Multi-antenna processing +- Support of L1 control and Hybrid-ARQ-related signalling + +![Figure 5.1.1-1: Physical-layer model for UL-SCH transmission. The diagram shows the processing flow between a gNode B and a UE. On the gNode B side, transport blocks are processed through CRC, Coding + RM, Data demodulation, Resource mapping, and Antenna mapping. The MAC scheduler provides inputs like redundancy version, modulation scheme, and resource/power assignment. Error indications and HARQ info are sent back to the MAC. On the UE side, the process is reversed: Antenna mapping, Resource mapping, Data Modulation, Coding + RM, and CRC. Transport blocks are sent to the MAC, which provides HARQ info and ACK/NACK. A vertical green bar on the far right is labeled 'Uplink transmission control'.](9791722d75115ddcc599b07d7bc35d73_img.jpg) + +Figure 5.1.1-1: Physical-layer model for UL-SCH transmission. The diagram shows the processing flow between a gNode B and a UE. On the gNode B side, transport blocks are processed through CRC, Coding + RM, Data demodulation, Resource mapping, and Antenna mapping. The MAC scheduler provides inputs like redundancy version, modulation scheme, and resource/power assignment. Error indications and HARQ info are sent back to the MAC. On the UE side, the process is reversed: Antenna mapping, Resource mapping, Data Modulation, Coding + RM, and CRC. Transport blocks are sent to the MAC, which provides HARQ info and ACK/NACK. A vertical green bar on the far right is labeled 'Uplink transmission control'. + +Figure 5.1.1-1: Physical-layer model for UL-SCH transmission + +### 5.1.2 Random access channel + +The physical-layer model for RACH transmission is characterized by a PRACH preamble format that consists of a cyclic prefix, a preamble, and a guard time during which nothing is transmitted. + +## 5.2 Downlink model + +### 5.2.1 Downlink shared channel + +The physical-layer model for Downlink Shared Channel transmission is described based on the corresponding PDSCH physical-layer-processing chain, see Figure 5.2.1-1. Processing steps that are relevant for the physical-layer model, e.g. in the sense that they are configurable by higher layers, are highlighted in blue. + +- Higher-layer data passed to/from the physical layer; +- CRC and transport-block-error indication; +- FEC and rate matching; +- Data modulation; +- Mapping to physical resource; +- Multi-antenna processing; +- Support of L1 control and Hybrid-ARQ-related signalling. + +![Figure 5.2.1-1: Physical-layer model for DL-SCH transmission. The diagram shows the data flow between a gNode B (left) and a UE (right). At the gNode B, transport blocks are processed through CRC, Coding + RM, Data modulation, Resource mapping, and Antenna mapping. A MAC scheduler provides channel state information, redundancy version, modulation scheme, resource/power assignment, and antenna mapping. HARQ feedback (ACK/NACK and HARQ info) is sent from the UE. At the UE, the process is reversed: Antenna mapping, Resource mapping, Data demodulation, Coding + RM, and CRC. Error indications are sent from the UE to the gNode B. Downlink transmission control is shown on the far right.](07b17a620c75522d53916a11e12d1bff_img.jpg) + +The diagram illustrates the physical-layer model for DL-SCH transmission between a gNode B and a UE. At the gNode B (left), transport blocks are processed through a series of steps: CRC, Coding + RM, Data modulation, Resource mapping, and Antenna mapping. A MAC scheduler provides channel state information, redundancy version, modulation scheme, resource/power assignment, and antenna mapping. HARQ feedback (ACK/NACK and HARQ info) is sent from the UE. At the UE (right), the process is reversed: Antenna mapping, Resource mapping, Data demodulation, Coding + RM, and CRC. Error indications are sent from the UE to the gNode B. Downlink transmission control is shown on the far right. + +Figure 5.2.1-1: Physical-layer model for DL-SCH transmission. The diagram shows the data flow between a gNode B (left) and a UE (right). At the gNode B, transport blocks are processed through CRC, Coding + RM, Data modulation, Resource mapping, and Antenna mapping. A MAC scheduler provides channel state information, redundancy version, modulation scheme, resource/power assignment, and antenna mapping. HARQ feedback (ACK/NACK and HARQ info) is sent from the UE. At the UE, the process is reversed: Antenna mapping, Resource mapping, Data demodulation, Coding + RM, and CRC. Error indications are sent from the UE to the gNode B. Downlink transmission control is shown on the far right. + +Figure 5.2.1-1: Physical-layer model for DL-SCH transmission + +### 5.2.2 Broadcast channel + +The physical-layer model for BCH transmission is characterized by a fixed pre-defined transport format. There is one transport block for the BCH every 80ms. The BCH physical-layer model is described based on the corresponding PBCH physical-layer-processing chain, see Figure 5.2.2-1: + +- Higher-layer data passed to/from the physical layer; +- CRC and transport-block-error indication; +- FEC and rate matching; +- Data modulation; + +- Mapping to physical resource; +- Multi-antenna processing. + +![Figure 5.2.2-1: Physical-layer model for BCH transmission. The diagram shows two vertical processing chains. The left chain, labeled 'gNode B', starts with a 'Transport block (fixed size)' at the top, followed by 'CRC', 'Coding + RM', 'Data modulation', 'Resource mapping', and 'Antenna mapping' at the bottom. The right chain, labeled 'UE', starts with 'Antenna mapping' at the bottom, followed by 'Resource mapping', 'Data modulation', 'Coding + RM', and 'CRC' at the top. Above the 'CRC' block in the UE chain, there is an 'Error indication' label with an upward-pointing arrow. Dashed horizontal lines separate the top transport block from the CRC block in both chains. Dashed vertical lines connect the 'Resource mapping' and 'Antenna mapping' blocks in both chains. At the bottom of each chain, there are two antenna symbols (Y-shapes).](7a0db9703b68b3d06cdaeefc084c0006_img.jpg) + +Figure 5.2.2-1: Physical-layer model for BCH transmission. The diagram shows two vertical processing chains. The left chain, labeled 'gNode B', starts with a 'Transport block (fixed size)' at the top, followed by 'CRC', 'Coding + RM', 'Data modulation', 'Resource mapping', and 'Antenna mapping' at the bottom. The right chain, labeled 'UE', starts with 'Antenna mapping' at the bottom, followed by 'Resource mapping', 'Data modulation', 'Coding + RM', and 'CRC' at the top. Above the 'CRC' block in the UE chain, there is an 'Error indication' label with an upward-pointing arrow. Dashed horizontal lines separate the top transport block from the CRC block in both chains. Dashed vertical lines connect the 'Resource mapping' and 'Antenna mapping' blocks in both chains. At the bottom of each chain, there are two antenna symbols (Y-shapes). + +Figure 5.2.2-1: Physical-layer model for BCH transmission + +### 5.2.3 Paging channel + +The physical-layer model for PCH transmission is described based on the corresponding physical-layer-processing chain, see Figure 5.2.3-1. The PCH is carried on PDSCH. Processing steps that are relevant for the physical-layer model, e.g. in the sense that they are configurable by higher layers, are highlighted in blue. + +- Higher-layer data passed to/from the physical layer; +- CRC and transport-block-error indication; +- FEC and rate matching; +- Data modulation; +- Mapping to physical resource; +- Multi-antenna processing. + +![Figure 5.2.3-1: Physical-layer model for PCH transmission. The diagram shows the data flow from a Transport block through various processing stages in a gNode B and a UE. In the gNode B, the stages are CRC, Coding + RM, Data modulation, Resource mapping, and Antenna mapping. In the UE, the stages are Antenna mapping, Resource mapping, Data demodulation, Coding + RM, and CRC. Control signals from the MAC scheduler and Downlink transmission control are shown interacting with these stages. An Error indication is shown at the UE output.](e6df2733626a85205c1db682e6259c46_img.jpg) + +The diagram illustrates the physical-layer model for PCH transmission between a gNode B and a UE. At the gNode B, a Transport block is processed through CRC, Coding + RM, Data modulation, Resource mapping, and Antenna mapping. The MAC scheduler provides Modulation scheme, Resource/power assignment, and Antenna mapping to the Data modulation, Resource mapping, and Antenna mapping blocks respectively. At the UE, the process is reversed: Antenna mapping, Resource mapping, Data demodulation, Coding + RM, and CRC. The Downlink transmission control provides Modulation scheme and Resource/power assignment to the Data demodulation and Resource mapping blocks. An Error indication is shown at the UE output. + +Figure 5.2.3-1: Physical-layer model for PCH transmission. The diagram shows the data flow from a Transport block through various processing stages in a gNode B and a UE. In the gNode B, the stages are CRC, Coding + RM, Data modulation, Resource mapping, and Antenna mapping. In the UE, the stages are Antenna mapping, Resource mapping, Data demodulation, Coding + RM, and CRC. Control signals from the MAC scheduler and Downlink transmission control are shown interacting with these stages. An Error indication is shown at the UE output. + +Figure 5.2.3-1: Physical-layer model for PCH transmission + +## 5.3 Sidelink model + +### 5.3.1 Sidelink shared channel + +The physical-layer model for Sidelink Shared Channel transmission is described based on the corresponding SL-SCH physical-layer-processing chain, see Figure 5.3.1-1. Processing steps that are relevant for the physical-layer model, e.g. in the sense that they are configurable by higher layers, are highlighted in blue. + +- Higher-layer data passed to/from the physical layer; +- CRC and transport-block-error indication; +- FEC and rate matching; +- Data modulation; +- Mapping to physical resource; +- Multi-antenna processing; +- Support of L1 control and Hybrid-ARQ-related signalling. + +![Figure 5.3.1-1: Physical-layer model for SL-SCH transmission. The diagram shows the transmitter and receiver chains for SL-SCH. The Transmitter UE includes a MAC scheduler, HARQ, CRC, Coding + RM, Data modulation, Resource mapping, and Antenna mapping. The Receiver UE includes Antenna demapping, Resource demapping, Data demodulation, Decoding + RM, CRC, HARQ, and Sidelink transmission control. Arrows indicate the flow of data and control information between the layers and the HARQ process.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +The diagram illustrates the physical-layer model for SL-SCH transmission, divided into Transmitter UE and Receiver UE. + +**Transmitter UE:** + +- Inputs: Channel state information, etc. +- MAC scheduler: Provides Redundancy version, Modulation scheme, Resource/power assignment, and Antenna mapping to the HARQ and mapping stages. +- HARQ: Interacts with the MAC scheduler and the CRC stage. It receives ACK/NACK and HARQ info. +- CRC: Processes data from the HARQ stage. +- Coding + RM: Processes data from the CRC stage. +- Data modulation: Processes data from the Coding + RM stage. +- Resource mapping: Processes data from the Data modulation stage. +- Antenna mapping: Processes data from the Resource mapping stage and sends it to the antennas. + +**Receiver UE:** + +- Antenna demapping: Receives data from the antennas and sends it to the Resource demapping stage. +- Resource demapping: Processes data from the Antenna demapping stage. +- Data demodulation: Processes data from the Resource demapping stage. +- Decoding + RM: Processes data from the Data demodulation stage. +- CRC: Processes data from the Decoding + RM stage. +- HARQ: Interacts with the CRC stage and the Sidelink transmission control. It receives ACK/NACK and HARQ info. +- Sidelink transmission control: Provides Redundancy version, Modulation scheme, and Resource/power assignment to the HARQ and demapping stages. It also receives Error indications from the CRC stage. + +Figure 5.3.1-1: Physical-layer model for SL-SCH transmission. The diagram shows the transmitter and receiver chains for SL-SCH. The Transmitter UE includes a MAC scheduler, HARQ, CRC, Coding + RM, Data modulation, Resource mapping, and Antenna mapping. The Receiver UE includes Antenna demapping, Resource demapping, Data demodulation, Decoding + RM, CRC, HARQ, and Sidelink transmission control. Arrows indicate the flow of data and control information between the layers and the HARQ process. + +Figure 5.3.1-1: Physical-layer model for SL-SCH transmission + +### 5.3.2 Broadcast channel + +The physical-layer model for Sidelink Broadcast Channel transmission is characterized by a fixed pre-defined transport format. There is one transport block for every slot in which the UE transmits SL-BCH, if the UE is configured to transmit on SL-BCH. The SL-BCH physical-layer model is described based on the corresponding SL-BCH physical-layer-processing chain, see Figure 5.3.2-1: + +- Higher-layer data passed to/from the physical layer; +- CRC and transport-block-error indication; +- FEC and rate matching; +- Data modulation; +- Mapping to physical resource; +- Multi-antenna processing. + +![Figure 5.3.2-1: Physical-layer model for SL-BCH transmission. The diagram shows the processing flow for a Transmitter UE and a Receiver UE. On the transmitter side, data is processed through CRC, Coding + RM, Data modulation, Resource mapping (receiving input from Sidelink Transmission Control), and Antenna mapping. On the receiver side, the process is reversed: Antenna demapping, Resource demapping, Data demodulation, Decoding + RM, and CRC. An 'Error indication' is shown at the top of the receiver side.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +Figure 5.3.2-1: Physical-layer model for SL-BCH transmission. The diagram shows the processing flow for a Transmitter UE and a Receiver UE. On the transmitter side, data is processed through CRC, Coding + RM, Data modulation, Resource mapping (receiving input from Sidelink Transmission Control), and Antenna mapping. On the receiver side, the process is reversed: Antenna demapping, Resource demapping, Data demodulation, Decoding + RM, and CRC. An 'Error indication' is shown at the top of the receiver side. + +Figure 5.3.2-1: Physical-layer model for SL-BCH transmission + +# 6 Simultaneous transmission and reception of physical channels and physical signals + +This clause describes the requirements from the UE to send and receive multiple physical channels and physical signals simultaneously depending on the capabilities and service requirements. The following notation is used between both the uplink and downlink clauses below. + +- $p$ is the number of uplink carriers configured for the UE on which physical channels can be transmitted +- $p'$ is the number of uplink carriers configured for the UE on which SRS can be transmitted +- $q$ is the number of downlink carriers configured for the UE +- $j$ is the number of cell groups configured for the UE. +- $k$ is the number of PUCCH groups configured for the UE. + +## 6.1 Uplink + +The tables 6.1-1 and 6.1-2 describe the possible combinations of physical channels and SRS that can be sent in simultaneously in the uplink by one UE. Table 6.1-1 introduces notation for a "Transmission Type" which represents a physical channel or sounding reference signal, and any associated transport channel. Table 6.1-2 describes the combinations of these "Transmission Types" which are supported by the UE depending on capabilities [8, TS 38.306], and enumerates how many of each can be transmitted simultaneously. + +Table 6.1-1: Uplink "Transmission Types" + +| "Transmission Type" | Physical Channel or SRS | Associated Transport Channel | Comment | +|---------------------|-------------------------|------------------------------|----------------| +| A | PRACH | RACH | Note 1, Note 3 | +| B | PUCCH | N/A | | +| C | PUSCH | UL-SCH | Note 2, Note 3 | +| D | SRS | N/A | | + +Note 1: RACH corresponds to contention based. +Note 2: UCI on PUSCH without UL-SCH is possible. +Note 3: For SCell, MsgA PRACH and MsgA PUSCH is not supported. + +Table 6.1-2: Uplink "Transmission Type" combinations + +| Supported Combinations | Comment | +|-----------------------------------------------------------------------|-------------------------| +| $j \times A$ | Note 1 | +| $k \times B$ | Note 2 | +| $(\sum_{i=1}^p m_i) \times C$ | Note 3, Note 4, Note 10 | +| $p' \times D$ | Note 3, Note 5 | +| $\tilde{j} \times A + \tilde{k} \times B$ | Note 6 | +| $\tilde{j} \times A + (\sum_{i=1}^{\tilde{p}} \tilde{m}_i) \times C$ | Note 6, Note 10 | +| $\tilde{j} \times A + \tilde{p}' \times D$ | Note 6 | +| $\tilde{k} \times B + (\sum_{i=1}^{\tilde{p}} \tilde{m}_i) \times C$ | Note 8, Note 10 | +| $B + (\sum_{i=1}^{\tilde{p}} \tilde{m}_i) \times C$ | Note 9, Note 10 | +| $\tilde{k} \times B + \tilde{p}' \times D$ | Note 7 | +| $(\sum_{i=1}^{\tilde{p}} \tilde{m}_i) \times C + \tilde{p}' \times D$ | Note 7, Note 10 | + +Note 1: The number of cell groups $j$ in the supported combination is subject to UE capability. +Note 2: The number of PUCCH groups $k$ in the supported combination is subject to UE capability. +Note 3: The number of carriers $p$ , and $p'$ in the supported combinations are subject to UE capability. +Note 4: In the case there is one SUL carrier, then $p-1$ would be supported. +Note 5: UE may be configured with $p'$ but may also have capability to simultaneously sound less than this number. +Note 6: Simultaneous PRACH with PUCCH (or PUSCH or SRS) is supported only in the case of inter-band CA, with $\tilde{j} \leq j$ , $\tilde{k} \leq k$ , $\tilde{p} \leq p$ , and $\tilde{p}' \leq p'$ depending on the configuration, and subject to UE capability for parallel transmission. +Note 7: Simultaneous SRS with PUCCH (or PUSCH) is supported only in the case of inter-band CA, with $\tilde{k} \leq k$ , $\tilde{p} \leq p$ , and $\tilde{p}' \leq p'$ depending on the configuration, and subject to UE capability for parallel transmission. +Note 8: Simultaneous PUCCH and PUSCH(s) for the case that multiple PUCCH groups are configured and the respective PUCCH and PUSCH(s) are transmitted in the different PUCCH groups, with $\tilde{k} < k$ and $\tilde{p} \leq p$ . $k$ and $p$ are subject to UE capability for supported number of PUCCH groups and UL carriers, respectively. $\tilde{k}$ and $\tilde{p}$ depend on configuration. +Note 9: Simultaneous PUCCH and PUSCH(s) within the same PUCCH group in the case of inter-band CA, $\tilde{p}'$ depending on the configuration, and subject to UE capability for parallel transmission of PUCCH and PUSCH within the same PUCCH group. +Note 10: Simultaneous transmission of up to 2 PUSCHs within the same active UL BWP, with $p, \tilde{p}, \hat{p}, \hat{p}'$ depending on the configuration, $m_i, \tilde{m}_i, \hat{m}_i, \hat{m}'_i$ equal to 1 or 2, subject to UE capability for parallel transmission of PUSCH and PUSCH within the same active UL BWP. + +## 6.2 Downlink + +The tables 6.2-1, 6.2-2 describe the possible combinations of physical channels that can be received simultaneously in the downlink by one UE. Table 6.2-1 introduces notation for a "Reception Type" which represents a physical channel and any associated transport channel. Table 6.2-2 describes the combinations of these "Reception Types" which are supported by the UE depending on capabilities [8, TS 38.306], and enumerates how many of each can be received simultaneously. The UE shall be able to receive all TBs according to the indication on PDCCH. Any subset of the combinations specified in table 6.2-2 is also supported. + +Table 6.2-1: Downlink "Reception Types" + +| "Reception Type" | Physical Channel(s) | Monitored RNTI | Associated Transport Channel | Comment | +|------------------|---------------------|------------------------------------------|------------------------------|----------------| +| A | PBCH | N/A | BCH | | +| B | PDCCH+PDSCH | SI-RNTI | DL-SCH | Note 1 | +| C0 | PDCCH | P-RNTI | N/A | Note 1, Note 2 | +| C1 | PDCCH+PDSCH | P-RNTI | PCH | Note 1 | +| D0 | PDCCH+PDSCH | RA-RNTI or Temporary C-RNTI or MsgB-RNTI | DL-SCH | Note 3 | +| D1 | PDCCH+PDSCH | C-RNTI, CS-RNTI, MCS-C-RNTI | DL-SCH | | +| D2 | PDCCH | C-RNTI, CS-RNTI, MCS-C-RNTI | DL-SCH | | +| D3 | PDCCH+PDSCH | G-RNTI, G-CS-RNTI | DL-SCH | Note 6 | +| D4 | PDCCH | G-CS-RNTI | N/A | Note 7 | +| D5 | PDCCH+PDSCH | MCCH-RNTI | DL-SCH | Note 8 | +| D6 | PDCCH+PDSCH | G-RNTI | DL-SCH | Note 9 | +| D7 | PDCCH+PDSCH | C-RNTI | DL-SCH | Note 10 | +| D8 | PDCCH+PDSCH | multicast-MCCH-RNTI | DL-SCH | Note 11 | +| E | PDCCH | C-RNTI | N/A | Note 4 | +| F0 | PDCCH | Temporary C-RNTI | UL-SCH | Note 3 | +| F1 | PDCCH | C-RNTI, CS-RNTI, MCS-C-RNTI | UL-SCH | | +| F2 | PDCCH | C-RNTI, CS-RNTI | UL-SCH | Note 10 | +| G | PDCCH | SFI-RNTI | N/A | | +| H | PDCCH | INT-RNTI | N/A | | +| J0 | PDCCH | TPC-PUSCH-RNTI | N/A | | +| J1 | PDCCH | TPC-PUCCH-RNTI | N/A | | +| J2 | PDCCH | TPC-SRS-RNTI | N/A | | +| K | PDCCH | SP-CSI-RNTI | N/A | | +| L0 | PDCCH | SL-RNTI | SL-SCH | | +| L1 | PDCCH | SL-CS-RNTI | SL-SCH | | +| M | PDCCH | SL Semi-Persistent Scheduling V-RNTI | SL-SCH | Note 5 | +| N | PDCCH | PS-RNTI | N/A | | +| O | PDCCH | AI-RNTI | N/A | | +| P | PDCCH | CI-RNTI | N/A | | +| Q | PDCCH | PEI-RNTI | N/A | Note 1 | + +Note 1: These are received from PCell only. +Note 2: In some cases UE is only required to monitor the short message within the DCI for P-RNTI. +Note 3: These are received from PCell or PSCell. +Note 4: This corresponds to PDCCH-ordered PRACH. +Note 5: This corresponds to PDCCH scheduling LTE PC5. +Note 6: This is for multicast in RRC connected state. +Note 7: This corresponds to DL Semi-Persistent Scheduling release for multicast in RRC connected state. +Note 8: This is for broadcast MCCH. +Note 9: This is for broadcast MTCH. UE is not required to decode more than one PDSCH for MTCH simultaneously. +Note 10: This is for small data transmission in RRC inactive state. +Note 11: This is for multicast MCCH in RRC inactive state. + +Table 6.2-2: Downlink "Reception Type" combinations + +| Supported Combinations | | | Comment | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|--| +| PCell | PSCell | SCell | | | +| 1. RRC_IDLE | | | | | +| 1.1 All UEs | | | | | +| A + (B and/or (C1 or Q) and/or D0) + F0 | | | Note 1 | | +| 1.2 UEs supporting MBS broadcast reception_ | | | | | +| A+D5 | | | | | +| 2. RRC_INACTIVE | | | | | +| 2.1 All UEs | | | | | +| A + (B and/or (C0 or C1 or Q) and/or (D0 or D7)) + (F0 or F2) | | | Note 1 | | +| 2.2 UEs supporting MBS broadcast reception_ | | | | | +| A+D5 | | | | | +| 2.3 UE supporting MBS multicast reception | | | | | +| A+D8 | | | | | +| 3. RRC_CONNECTED | | | | | +| (A + ((C0 + (B and/or (D0 or (m1*D1+m2*D2+((m3*D3+m4*D4) or m5*(D5 or D6)))) + E + F0 + n*F1 + G + H + J0 + J1 + J2 + K + O + L0 + L1 + M + N + P) or D5)) | (A + (D0 or (m1*D1+m2*D2)) + E + F0 + n*F1 + G + H + J0 + J1 + J2 + K + O + N + P) | m1*D1 + m2*D2 + ((m3*D3+m4*D4) or m5*(D5 or D6)) + E + n*F1 + G + H + J0 + J1 + J2 + K + O + L0 + L1 + M + P | Note 2, Note 3, Note 4, Note 5, Note 6, Note 7, Note 8, Note 9, Note 10, Note 11, Note 12, Note 13, Note 14 | | +| Note 1: UE is not required to decode more than two PDSCH simultaneously, and decoding prioritization when more than two are received is up to UE implementation. | | | | | +| Note 2: For PCell, UE is not required to decode SI-RNTI PDSCH simultaneously with C-RNTI PDSCH, unless in FR1. | | | | | +| Note 3: Supported combinations are subject to UE capabilities for dual connectivity, carrier aggregation, receiving of group TPC commands, pre-emption indication and dynamic SFI monitoring. | | | | | +| Note 4: The values of m2 ≥ 0 and n ≥ 0 in the supported combinations are subject to the UE capability. | | | | | +| Note 5: Support of monitoring PDCCH with SL-RNTI, SL-CS-RNTI, SL Semi-Persistent Scheduling V-RNTI are subject to UE capability. | | | | | +| Note 6: The values of m1 ≥ 1 in the supported combinations are subject to the UE capability. | | | | | +| Note 7: In Active time, a UE is not expected to monitor the DCI format for the PDCCH scrambled by PS-RNTI. | | | | | +| Note 8: The PDCCH scrambled by PS-RNTI can only be configured on the PCell and PSCell. | | | | | +| Note 9: For a UE supporting MBS multicast reception, the values of 1 ≥ m3 ≥ 0 and m4 ≥ 0 are subject to UE capability and applicable to RRC connected UEs. If m3 = 1, then m1 ≤ 1. | | | | | +| Note 10: For a UE supporting MBS multicast or broadcast reception, the UE is not expected to be configured simultaneously with more than one component carrier for multicast or broadcast reception. | | | | | +| Note 11: For a UE supporting MBS broadcast reception, the values of 1 ≥ m5 ≥ 0 are subject to UE capability and applicable to RRC connected UEs. If m5=1, then m1≤1. | | | | | +| Note 12: For a UE supporting MBS broadcast reception in RRC_CONNECTED state, it is required to support reception of FDMe MCCH PDSCH and PBCH in Pcell. | | | | | +| Note 13: For a UE supporting MBS multicast or broadcast reception in RRC_CONNECTED state, it is not required to support reception of FDMe MCCH PDSCH/broadcast MTCH PDSCH/multicast MTCH PDSCH and SIB PDSCH in PCell. | | | | | +| Note 14: For a UE supporting MBS multicast or broadcast reception in RRC_CONNECTED state, it is not required to support reception of FDMe broadcast MTCH PDSCH/multicast MTCH PDSCH and PBCH in PCell. | | | | | + +## 6.3 Sidelink + +The tables 6.3-1 and 6.3-2 describe the possible combinations of physical channels that can be sent simultaneously in the sidelink by a UE. Table 6.3-1 introduces notation for a sidelink "Transmission Type" which represents a physical channel, and any associated transport channel. Table 6.3-2 describes the combinations of these "Transmission Types" + +which are supported by the UE depending on capabilities [8, TS 38.306], and enumerates how many of each can be transmitted simultaneously. + +**Table 6.3-1: Sidelink "Transmission Types"** + +| "Transmission Type" | Physical Channel | Associated Transport Channel | Comment | +|---------------------|------------------|------------------------------|---------| +| A | PSBCH | SL-BCH | | +| B | PSSCH | SL-SCH | | +| C | PSCCH | SL-SCH | | +| D | PSFCH | N/A | | +| E | SL PRS | N/A | | + +**Table 6.3-2: Sidelink "Transmission Type" combinations** + +| Supported Combinations | Comment | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------| +| A | Note 2 | +| B | Note 2 | +| C | Note 2 | +| E | Note 4 | +| E | Note 5 | +| $N \times D$ | Note 2 | +| B+C | Note 2 | +| Note 1: Depending on the UE capability, the UE may be able to perform simultaneous Uplink and Sidelink transmissions. If the simultaneous transmission of Sidelink and Uplink is beyond the UE capability, the one not prioritized can be dropped according to [TS 38.321].
Note 2: Depending on the UE capability, the UE may be able to perform simultaneous sidelink communication transmissions of the same sidelink "Transmission Type" combinations across multiple SL carriers.
Note 3: Simultaneous transmissions over multiple SL carriers with one or more UL carriers is left up to UE implementation.
Note 4: Applicable for a shared SL PRS resource pool.
Note 5: Applicable for a dedicated SL PRS resource pool. | | + +The tables 6.3-3 and 6.3-4 describe the possible combinations of physical channels that can be received simultaneously in the sidelink by a UE. Table 6.3-3 introduces notation for a sidelink "Reception Type" which represents a physical channel, and any associated transport channel. Table 6.3-4 describes the combinations of these "Reception Types" which are supported by the UE depending on capabilities [8, TS 38.306], and enumerates how many of each can be received simultaneously. + +**Table 6.3-3: Sidelink "Reception Types"** + +| "Reception Type" | Physical Channel | Associated Transport Channel | Comment | +|------------------|------------------|------------------------------|---------| +| A | PSBCH | SL-BCH | | +| B | PSSCH | SL-SCH | | +| C | PSCCH | SL-SCH | | +| D | PSFCH | N/A | | +| E | SL PRS | N/A | | + +Table 6.3-4: Sidelink "Reception Type" combinations + +| Supported Combinations | Comment | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------| +| A | | +| B | Note 1, Note 2 | +| C | Note 1, Note 2 | +| E | Note 3 | +| $M_1 \times E$ | Note 4 | +| $M \times D$ | Note 2 | +| B+C | Note 1, Note 2 | +| Note 1: Corresponds to simultaneous reception within one sub-channel
Note 2: Depending on the UE capability, the UE may be able to perform simultaneous sidelink communication receptions of the same sidelink "Reception Type" combinations across multiple SL carriers.
Note 3: Applicable for a shared SL PRS resource pool.
Note 4: Applicable for a dedicated SL PRS resource pool with $M_1 \geq 1$ . | | + +# 7 Measurements provided by the physical layer + +## 7.1 UE measurements + +The list and detailed definition of UE measurements is provided in [7, TS 38.215]. + +# --- Annex A (informative): Change history + +| Change history | | | | | | | | | +|----------------|----------|------------|------|-----|-----|--------------------------------------------------------------------------------------------------------------------|-------------|--| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | | +| 2017-05 | RAN1#89 | R1-1712013 | | | | Draft skeleton | 0.0.0 | | +| 2017-07 | AH 1706 | R1-1712013 | | | | Update for agreements from meetings up to RAN1 NR AH2 | 0.0.1 | | +| 2017-08 | RAN1#90 | R1-1713371 | | | | Update for agreements from meetings up to RAN1 NR AH2 | 0.0.2 | | +| 2017-08 | RAN1#90 | R1-1714655 | | | | Update with change marks removed for RAN1 #90 endorsement | 0.1.0 | | +| 2017-09 | RAN1#90 | R1-1715320 | | | | Updated with minor editorial changes for review after RAN1 #90 | 0.1.1 | | +| 2017-09 | RAN#77 | RP-172006 | | | | For information to plenary | 1.0.0 | | +| 2017-10 | RAN1#90b | R1-1719229 | | | | Updated for agreements from meetings up to RAN1 #90b | 1.0.1 | | +| 2017-11 | RAN1#91 | R1-1721047 | | | | Updated after email discussion | 1.1.0 | | +| 2017-12 | RAN1#91 | R1-1721340 | | | | Updated to reflect agreements from RAN1 #91 | 1.2.0 | | +| 2017-12 | RAN#78 | RP-172630 | | | | 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.202 capturing the RAN1#92bis and RAN1#93 meeting agreements | 15.2.0 | | +| 2018-06 | RAN#80 | RP-181257 | 0003 | - | B | CR to 38.202 capturing the RAN1#92bis and RAN1#93 meeting agreements related to URLLC | 15.2.0 | | +| 2018-09 | RAN#81 | RP-181789 | 0004 | - | B | CR to 38.202 capturing RAN1#94 meeting agreements | 15.3.0 | | +| 2018-12 | RAN#82 | RP-182523 | 0005 | - | F | CR to 38.202 capturing RAN1#95 meeting agreements | 15.4.0 | | +| 2019-06 | RAN#84 | RP-191277 | 0006 | - | F | Correction to simultaneous reception of DL Channels | 15.5.0 | | +| 2019-06 | RAN#84 | RP-191277 | 0007 | - | F | CR on inclusion of TC-RNTI for monitored RNTI for UL-SCH and inclusion of monitoring PDCCH ordering PRACH on SCell | 15.5.0 | | +| 2019-12 | RAN#86 | RP-192623 | 0008 | 1 | F | CR on simultaneous transmission of UL channels | 15.6.0 | | +| 2019-12 | RAN#86 | RP-192635 | 0009 | - | B | Introduction of two-step RACH | 16.0.0 | | +| 2019-12 | RAN#86 | RP-192637 | 0010 | - | B | Introduction of integrated access and backhaul for NR | 16.0.0 | | +| 2019-12 | RAN#86 | RP-192638 | 0011 | - | B | Introduction of V2X | 16.0.0 | | +| 2019-12 | RAN#86 | RP-192639 | 0012 | - | B | Introduction of Physical Layer Enhancements for URLLC | 16.0.0 | | +| 2019-12 | RAN#86 | RP-192641 | 0013 | - | B | Introduction of MIMO enhancements | 16.0.0 | | +| 2019-12 | RAN#86 | RP-192642 | 0014 | - | B | Introduction of UE Power Savings | 16.0.0 | | +| 2020-06 | RAN#88-e | RP-200692 | 0015 | - | F | Corrections to MIMO enhancements | 16.1.0 | | +| 2020-09 | RAN#89-e | RP-201810 | 0017 | - | F | DL Channel Combination associated with DCI format 2_6 monitoring | 16.2.0 | | +| 2020-09 | RAN#89-e | RP-201807 | 0018 | - | F | Corrections on 5G V2X sidelink features | 16.2.0 | | +| 2021-12 | RAN#94-e | RP-212960 | 0019 | - | F | Alignment CR for TS 38.202 | 16.3.0 | | +| 2021-12 | RAN#94-e | RP-212968 | 0020 | - | B | Introduction of IIoT/URLLC enhancements in NR | 17.0.0 | | +| 2021-12 | RAN#94-e | RP-212979 | 0021 | - | B | Introduction of multicast and broadcast services | 17.0.0 | | +| 2022-03 | RAN#95-e | RP-220263 | 0022 | - | F | Corrections to NR support of multicast and broadcast services | 17.1.0 | | +| 2022-03 | RAN#95-e | RP-220256 | 0023 | - | F | Corrections on NR UE Power Saving Enhancements | 17.1.0 | | +| 2022-06 | RAN#96 | RP-221612 | 0024 | - | F | Corrections to NR support of multicast and broadcast services | 17.2.0 | | +| 2022-12 | RAN#98-e | RP-222864 | 0025 | - | F | CR on the MBS reception type combinations to TS 38.202 | 17.3.0 | | +| 2023-09 | RAN#101 | RP-232450 | 0026 | - | F | Correction on simultaneous reception of SDT and other channels in TS 38.202 | 17.4.0 | | +| 2023-09 | RAN#101 | RP-232458 | 0027 | - | B | Release 18 TS38.202 Editor CR for MIMO | 18.0.0 | | +| 2023-09 | RAN#101 | RP-232469 | 0028 | - | B | Release 18 TS38.202 Editor CR for NR sidelink evolution | 18.0.0 | | +| 2023-12 | RAN#102 | RP-233723 | 0031 | 1 | A | Correction on NR Sidelink | 18.1.0 | | +| 2023-12 | RAN#102 | RP-233733 | 0032 | - | B | Release 18 TS38.202 Editor CR for multicast in RRC_INACTIVE state | 18.1.0 | | +| 2023-12 | RAN#102 | RP-233719 | 0033 | - | F | Release 18 TS38.202 Editor CR for SL-PRS transmission and Reception | 18.1.0 | | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38211/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38211/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..09cf312511d0d38ee42d3baab65db7bfeaed1416 --- /dev/null +++ b/marked/Rel-18/38_series/38211/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:804446b0a6e7712c8e5f460248afa65a1cdb81180a7345e47886886212604213 +size 9492 diff --git a/marked/Rel-18/38_series/38211/63e0c22852c26699d0bd095a2d796bab_img.jpg b/marked/Rel-18/38_series/38211/63e0c22852c26699d0bd095a2d796bab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eca8fa1d6057279a56d8887a971839d783361891 --- /dev/null +++ b/marked/Rel-18/38_series/38211/63e0c22852c26699d0bd095a2d796bab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b0b3e9956e1e2866cbb4addf59f0ae3f7901780025712123ac127c8863d290db +size 11926 diff --git a/marked/Rel-18/38_series/38211/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38211/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..319cfe71da3339d0036c3a755a85a00f15364027 --- /dev/null +++ b/marked/Rel-18/38_series/38211/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c0136cbed636287efb481ca8390ec73a12a75063056fced2d6a47f52875a760 +size 6236 diff --git a/marked/Rel-18/38_series/38211/85b4e4eafb7d71fbf621097515942e50_img.jpg b/marked/Rel-18/38_series/38211/85b4e4eafb7d71fbf621097515942e50_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0f4964b371a4396da06176afbbcdb2738026609b --- /dev/null +++ b/marked/Rel-18/38_series/38211/85b4e4eafb7d71fbf621097515942e50_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c741c24b9c9685c44f7760dafa65bb5f68aecec4b4510f6d2defb01219513aea +size 4239 diff --git a/marked/Rel-18/38_series/38211/raw.md b/marked/Rel-18/38_series/38211/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..1491d192aae0270c5c273c5c302112a226cb8406 --- /dev/null +++ b/marked/Rel-18/38_series/38211/raw.md @@ -0,0 +1,5848 @@ + + +# 3GPP TS 38.211 V18.1.0 (2023-12) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical channels and modulation (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 +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..... | 8 | +| 1 Scope..... | 9 | +| 2 References..... | 9 | +| 3 Definitions of terms, symbols and abbreviations..... | 9 | +| 3.1 Terms..... | 9 | +| 3.2 Symbols..... | 9 | +| 3.3 Abbreviations..... | 11 | +| 4 Frame structure and physical resources..... | 11 | +| 4.1 General..... | 11 | +| 4.2 Numerologies..... | 11 | +| 4.3 Frame structure..... | 12 | +| 4.3.1 Frames and subframes..... | 12 | +| 4.3.2 Slots..... | 12 | +| 4.4 Physical resources..... | 13 | +| 4.4.1 Antenna ports..... | 13 | +| 4.4.2 Resource grid..... | 14 | +| 4.4.3 Resource elements..... | 14 | +| 4.4.4 Resource blocks..... | 14 | +| 4.4.4.1 General..... | 14 | +| 4.4.4.2 Point A..... | 14 | +| 4.4.4.3 Common resource blocks..... | 15 | +| 4.4.4.4 Physical resource blocks..... | 15 | +| 4.4.4.5 Virtual resource blocks..... | 15 | +| 4.4.4.6 Interlaced resource blocks..... | 15 | +| 4.4.5 Bandwidth part..... | 15 | +| 4.4.6 Common MBS frequency resource..... | 16 | +| 4.5 Carrier aggregation..... | 16 | +| 5 Generic functions..... | 16 | +| 5.1 Modulation mapper..... | 16 | +| 5.1.1 $\pi/2$ -BPSK..... | 17 | +| 5.1.2 BPSK..... | 17 | +| 5.1.3 QPSK..... | 17 | +| 5.1.4 16QAM..... | 17 | +| 5.1.5 64QAM..... | 17 | +| 5.1.6 256QAM..... | 17 | +| 5.1.7 1024QAM..... | 17 | +| 5.2 Sequence generation..... | 18 | +| 5.2.1 Pseudo-random sequence generation..... | 18 | +| 5.2.2 Low-PAPR sequence generation type 1..... | 18 | +| 5.2.2.1 Base sequences of length 36 or larger..... | 18 | +| 5.2.2.2 Base sequences of length less than 36..... | 18 | +| 5.2.3 Low-PAPR sequence generation type 2..... | 22 | + +# 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 + +| | | | +|-------------|----------------------------------------------------------------------------------------|-----| +| 5.2.3.1 | Sequences of length 30 or larger..... | 22 | +| 5.2.3.2 | Sequences of length less than 30..... | 22 | +| 5.3 | OFDM baseband signal generation..... | 26 | +| 5.3.1 | OFDM baseband signal generation for all channels except PRACH and RIM-RS..... | 26 | +| 5.3.2 | OFDM baseband signal generation for PRACH..... | 28 | +| 5.3.3 | OFDM baseband signal generation for RIM-RS..... | 30 | +| 5.4 | Modulation and upconversion..... | 30 | +| 6 | Uplink..... | 31 | +| 6.1 | Overview..... | 31 | +| 6.1.1 | Overview of physical channels..... | 31 | +| 6.1.2 | Overview of physical signals..... | 31 | +| 6.2 | Physical resources..... | 31 | +| 6.3 | Physical channels..... | 32 | +| 6.3.1 | Physical uplink shared channel..... | 32 | +| 6.3.1.1 | Scrambling..... | 32 | +| 6.3.1.2 | Modulation..... | 33 | +| 6.3.1.3 | Layer mapping..... | 33 | +| 6.3.1.4 | Transform precoding..... | 33 | +| 6.3.1.5 | Precoding..... | 34 | +| 6.3.1.6 | Mapping to virtual resource blocks..... | 59 | +| 6.3.1.7 | Mapping from virtual to physical resource blocks..... | 60 | +| 6.3.2 | Physical uplink control channel..... | 60 | +| 6.3.2.1 | General..... | 60 | +| 6.3.2.2 | Sequence and cyclic shift hopping..... | 60 | +| 6.3.2.2.1 | Group and sequence hopping..... | 60 | +| 6.3.2.2.2 | Cyclic shift hopping..... | 61 | +| 6.3.2.3 | PUCCH format 0..... | 62 | +| 6.3.2.3.1 | Sequence generation..... | 62 | +| 6.3.2.3.2 | Mapping to physical resources..... | 62 | +| 6.3.2.4 | PUCCH format 1..... | 62 | +| 6.3.2.4.1 | Sequence modulation..... | 62 | +| 6.3.2.4.2 | Mapping to physical resources..... | 63 | +| 6.3.2.5 | PUCCH format 2..... | 63 | +| 6.3.2.5.1 | Scrambling..... | 63 | +| 6.3.2.5.2 | Modulation..... | 64 | +| 6.3.2.5.2A | Spreading..... | 64 | +| 6.3.2.5.3 | Mapping to physical resources..... | 65 | +| 6.3.2.6 | PUCCH formats 3 and 4..... | 65 | +| 6.3.2.6.1 | Scrambling..... | 65 | +| 6.3.2.6.2 | Modulation..... | 66 | +| 6.3.2.6.3 | Block-wise spreading..... | 66 | +| 6.3.2.6.4 | Transform precoding..... | 67 | +| 6.3.2.6.5 | Mapping to physical resources..... | 67 | +| 6.3.3 | Physical random-access channel..... | 67 | +| 6.3.3.1 | Sequence generation..... | 67 | +| 6.3.3.2 | Mapping to physical resources..... | 74 | +| 6.4 | Physical signals..... | 91 | +| 6.4.1 | Reference signals..... | 91 | +| 6.4.1.1 | Demodulation reference signal for PUSCH..... | 91 | +| 6.4.1.1.1 | Sequence generation..... | 91 | +| 6.4.1.1.2 | (void)..... | 93 | +| 6.4.1.1.3 | Precoding and mapping to physical resources..... | 93 | +| 6.4.1.2 | Phase-tracking reference signals for PUSCH..... | 98 | +| 6.4.1.2.1 | Sequence generation..... | 98 | +| 6.4.1.2.1.1 | Sequence generation if transform precoding is not enabled..... | 98 | +| 6.4.1.2.1.2 | Sequence generation if transform precoding is enabled..... | 98 | +| 6.4.1.2.2 | Mapping to physical resources..... | 99 | +| 6.4.1.2.2.1 | Precoding and mapping to physical resources if transform precoding is not enabled..... | 99 | +| 6.4.1.2.2.2 | Mapping to physical resources if transform precoding is enabled..... | 100 | +| 6.4.1.3 | Demodulation reference signal for PUCCH..... | 102 | +| 6.4.1.3.1 | Demodulation reference signal for PUCCH format 1..... | 102 | + +| | | | +|-------------|------------------------------------------------------------------------|-----| +| 6.4.1.3.1.1 | Sequence generation..... | 102 | +| 6.4.1.3.1.2 | Mapping to physical resources..... | 102 | +| 6.4.1.3.2 | Demodulation reference signal for PUCCH format 2..... | 103 | +| 6.4.1.3.2.1 | Sequence generation..... | 103 | +| 6.4.1.3.2.2 | Mapping to physical resources..... | 103 | +| 6.4.1.3.3 | Demodulation reference signal for PUCCH formats 3 and 4..... | 103 | +| 6.4.1.3.3.1 | Sequence generation..... | 103 | +| 6.4.1.3.3.2 | Mapping to physical resources..... | 104 | +| 6.4.1.4 | Sounding reference signal..... | 104 | +| 6.4.1.4.1 | SRS resource..... | 104 | +| 6.4.1.4.2 | Sequence generation..... | 105 | +| 6.4.1.4.3 | Mapping to physical resources..... | 107 | +| 6.4.1.4.4 | Sounding reference signal slot configuration..... | 111 | +| 7 | Downlink..... | 111 | +| 7.1 | Overview..... | 111 | +| 7.1.1 | Overview of physical channels..... | 111 | +| 7.1.2 | Overview of physical signals..... | 112 | +| 7.2 | Physical resources..... | 112 | +| 7.3 | Physical channels..... | 112 | +| 7.3.1 | Physical downlink shared channel..... | 112 | +| 7.3.1.1 | Scrambling..... | 112 | +| 7.3.1.2 | Modulation..... | 113 | +| 7.3.1.3 | Layer mapping..... | 113 | +| 7.3.1.4 | Antenna port mapping..... | 114 | +| 7.3.1.5 | Mapping to virtual resource blocks..... | 115 | +| 7.3.1.6 | Mapping from virtual to physical resource blocks..... | 115 | +| 7.3.2 | Physical downlink control channel (PDCCH)..... | 117 | +| 7.3.2.1 | Control-channel element (CCE)..... | 117 | +| 7.3.2.2 | Control-resource set (CORESET)..... | 117 | +| 7.3.2.3 | Scrambling..... | 119 | +| 7.3.2.4 | PDCCH modulation..... | 119 | +| 7.3.2.5 | Mapping to physical resources..... | 119 | +| 7.3.3 | Physical broadcast channel..... | 120 | +| 7.3.3.1 | Scrambling..... | 120 | +| 7.3.3.2 | Modulation..... | 120 | +| 7.3.3.3 | Mapping to physical resources..... | 120 | +| 7.4 | Physical signals..... | 120 | +| 7.4.1 | Reference signals..... | 120 | +| 7.4.1.1 | Demodulation reference signals for PDSCH..... | 120 | +| 7.4.1.1.1 | Sequence generation..... | 120 | +| 7.4.1.1.2 | Mapping to physical resources..... | 121 | +| 7.4.1.2 | Phase-tracking reference signals for PDSCH..... | 125 | +| 7.4.1.2.1 | Sequence generation..... | 125 | +| 7.4.1.2.2 | Mapping to physical resources..... | 125 | +| 7.4.1.3 | Demodulation reference signals for PDCCH..... | 127 | +| 7.4.1.3.1 | Sequence generation..... | 127 | +| 7.4.1.3.2 | Mapping to physical resources..... | 127 | +| 7.4.1.4 | Demodulation reference signals for PBCH..... | 128 | +| 7.4.1.4.1 | Sequence generation..... | 128 | +| 7.4.1.4.2 | Mapping to physical resources..... | 128 | +| 7.4.1.5 | CSI reference signals..... | 128 | +| 7.4.1.5.1 | General..... | 128 | +| 7.4.1.5.2 | Sequence generation..... | 129 | +| 7.4.1.5.3 | Mapping to physical resources..... | 129 | +| 7.4.1.6 | RIM reference signals..... | 132 | +| 7.4.1.6.1 | General..... | 132 | +| 7.4.1.6.2 | Sequence generation..... | 132 | +| 7.4.1.6.3 | Mapping to physical resources..... | 133 | +| 7.4.1.6.4 | RIM-RS configuration..... | 133 | +| 7.4.1.6.4.1 | General..... | 133 | +| 7.4.1.6.4.2 | Time-domain parameters and mapping from to time-domain parameters..... | 133 | + +| | | | +|-------------|----------------------------------------------------------------------------------|-----| +| 7.4.1.6.4.3 | Frequency-domain parameters and mapping from to frequency-domain parameters..... | 134 | +| 7.4.1.6.4.4 | Sequence parameters and mapping from to sequence parameters..... | 135 | +| 7.4.1.6.4.5 | Mapping between resource triplet and set ID..... | 135 | +| 7.4.1.7 | Positioning reference signals..... | 136 | +| 7.4.1.7.1 | General..... | 136 | +| 7.4.1.7.2 | Sequence generation..... | 136 | +| 7.4.1.7.3 | Mapping to physical resources in a downlink PRS resource..... | 136 | +| 7.4.1.7.4 | Mapping to slots in a downlink PRS resource set..... | 137 | +| 7.4.2 | Synchronization signals..... | 138 | +| 7.4.2.1 | Physical-layer cell identities..... | 138 | +| 7.4.2.2 | Primary synchronization signal..... | 138 | +| 7.4.2.2.1 | Sequence generation..... | 138 | +| 7.4.2.2.2 | Mapping to physical resources..... | 138 | +| 7.4.2.3 | Secondary synchronization signal..... | 138 | +| 7.4.2.3.1 | Sequence generation..... | 138 | +| 7.4.2.3.2 | Mapping to physical resources..... | 138 | +| 7.4.3 | SS/PBCH block..... | 139 | +| 7.4.3.1 | Time-frequency structure of an SS/PBCH block..... | 139 | +| 7.4.3.1.1 | Mapping of PSS within an SS/PBCH block..... | 140 | +| 7.4.3.1.2 | Mapping of SSS within an SS/PBCH block..... | 140 | +| 7.4.3.1.3 | Mapping of PBCH and DM-RS within an SS/PBCH block..... | 140 | +| 7.4.3.2 | Time location of an SS/PBCH block..... | 140 | +| 8 | Sidelink..... | 141 | +| 8.1 | Overview..... | 141 | +| 8.1.1 | Overview of physical channels..... | 141 | +| 8.1.2 | Overview of physical signals..... | 141 | +| 8.2 | Physical resources..... | 141 | +| 8.2.1 | General..... | 141 | +| 8.2.2 | Numerologies..... | 141 | +| 8.2.3 | Frame structure..... | 142 | +| 8.2.3.1 | Frames and subframes..... | 142 | +| 8.2.3.2 | Slots..... | 142 | +| 8.2.4 | Antenna ports..... | 142 | +| 8.2.5 | Resource grid..... | 142 | +| 8.2.6 | Resource elements..... | 143 | +| 8.2.7 | Resource blocks..... | 143 | +| 8.2.8 | Bandwidth part..... | 143 | +| 8.3 | Physical channels..... | 143 | +| 8.3.1 | Physical sidelink shared channel..... | 143 | +| 8.3.1.1 | Scrambling..... | 143 | +| 8.3.1.2 | Modulation..... | 144 | +| 8.3.1.3 | Layer mapping..... | 144 | +| 8.3.1.4 | Precoding..... | 144 | +| 8.3.1.5 | Mapping to virtual resource blocks..... | 144 | +| 8.3.1.6 | Mapping from virtual to physical resource blocks..... | 145 | +| 8.3.2 | Physical sidelink control channel..... | 145 | +| 8.3.2.1 | Scrambling..... | 145 | +| 8.3.2.2 | Modulation..... | 145 | +| 8.3.2.3 | Mapping to physical resources..... | 145 | +| 8.3.3 | Physical sidelink broadcast channel..... | 145 | +| 8.3.3.1 | Scrambling..... | 145 | +| 8.3.3.2 | Modulation..... | 146 | +| 8.3.3.3 | Mapping to physical resources..... | 146 | +| 8.3.4 | Physical sidelink feedback channel..... | 146 | +| 8.3.4.1 | General..... | 146 | +| 8.3.4.2 | PSFCH format 0..... | 146 | +| 8.3.4.2.1 | Sequence generation..... | 146 | +| 8.3.4.2.2 | Mapping to physical resources..... | 146 | +| 8.4 | Physical signals..... | 147 | +| 8.4.1 | Reference signals..... | 147 | +| 8.4.1.1 | Demodulation reference signals for PSSCH..... | 147 | + +| | | | +|-------------------------------------|------------------------------------------------------------|------------| +| 8.4.1.1.1 | Sequence generation..... | 147 | +| 8.4.1.1.2 | Mapping to physical resources..... | 147 | +| 8.4.1.2 | Phase-tracking reference signals for PSSCH..... | 148 | +| 8.4.1.2.1 | Sequence generation..... | 148 | +| 8.4.1.2.2 | Mapping to physical resources..... | 148 | +| 8.4.1.3 | Demodulation reference signals for PSCCH..... | 149 | +| 8.4.1.3.1 | Sequence generation..... | 149 | +| 8.4.1.3.2 | Mapping to physical resources..... | 150 | +| 8.4.1.4 | Demodulation reference signals for PSBCH..... | 150 | +| 8.4.1.4.1 | Sequence generation..... | 150 | +| 8.4.1.4.2 | Mapping to physical resources..... | 150 | +| 8.4.1.5 | CSI reference signals..... | 151 | +| 8.4.1.5.1 | General..... | 151 | +| 8.4.1.5.2 | Sequence generation..... | 151 | +| 8.4.1.5.3 | Mapping to physical resources..... | 151 | +| 8.4.1.6 | Positioning reference signals..... | 151 | +| 8.4.1.6.1 | General..... | 151 | +| 8.4.1.6.2 | Sequence generation..... | 151 | +| 8.4.1.6.3 | Mapping to physical resources..... | 152 | +| 8.4.2 | Synchronization signals..... | 152 | +| 8.4.2.1 | Physical-layer sidelink synchronization identities..... | 152 | +| 8.4.2.2 | Sidelink primary synchronization signal..... | 153 | +| 8.4.2.2.1 | Sequence generation..... | 153 | +| 8.4.2.2.2 | Mapping to physical resources..... | 153 | +| 8.4.2.3 | Sidelink secondary synchronization signal..... | 153 | +| 8.4.2.3.1 | Sequence generation..... | 153 | +| 8.4.2.3.2 | Mapping to physical resources..... | 153 | +| 8.4.3 | S-SS/PSBCH block..... | 153 | +| 8.4.3.1 | Time-frequency structure of an S-SS/PSBCH block..... | 153 | +| 8.4.3.1.1 | Mapping of S-PSS within an S-SS/PSBCH block..... | 154 | +| 8.4.3.1.2 | Mapping of S-SSS within an S-SS/PSBCH block..... | 154 | +| 8.4.3.1.3 | Mapping of PSBCH and DM-RS within an S-SS/PSBCH block..... | 154 | +| 8.4.3.2 | Time location of an S-SS/PSBCH block..... | 154 | +| 8.5 | Timing..... | 155 | +| Annex A: Change history..... | | 156 | + +# --- 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 channels and signals 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.212: "NR; Multiplexing and channel coding" +- [5] 3GPP TS 38.213: "NR; Physical layer procedures for control " +- [6] 3GPP TS 38.214: "NR; Physical layer procedures for data " +- [7] 3GPP TS 38.215: "NR; Physical layer measurements" +- [8] 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception" +- [9] void +- [10] 3GPP TS 38.306: "NR; User Equipment (UE) radio access capabilities" +- [11] 3GPP TS 38.321: "NR; Medium Access Control (MAC) protocol specification" +- [12] 3GPP TS 38.133: "NR; Requirements for support of radio resource management" +- [13] 3GPP TS 38.304: "NR; User Equipment (UE) procedures in Idle mode and RRC Inactive state" +- [14] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone" + +# 3 Definitions of terms, symbols and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the following definitions apply: + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Resource element with frequency-domain index $n$ and time-domain index $m$ for antenna port $p$ and subcarrier spacing configuration $\mu$ ; see clause 4.4.3 | +| $\beta$ | Value of resource element for antenna port and subcarrier spacing configuration ; see clause 4.4.3 | +| $\alpha$ | Amplitude scaling for a physical channel/signal | +| $c$ | PN sequence; see clause 5.2.1 | +| $\Delta f$ | Subcarrier spacing | +| $\Delta f_{RA}$ | Subcarrier spacing for random-access preambles | +| $T_c$ | The ratio between $T_s$ and $T_c$ ; see clause 4.1 | + +| | | +|----------|---------------------------------------------------------------------------------------------------------------------------------| +| $k$ | Subcarrier index relative to a reference | +| $l$ | OFDM symbol index relative to a reference | +| | Subcarrier spacing configuration, | +| | Number of coded bits to transmit on a physical channel [for codeword ] | +| | Number of modulation symbols to transmit on a physical channel [for codeword ] | +| | Number of modulation symbols to transmit per layer for a physical channel | +| | Scheduled bandwidth for uplink transmission, expressed as a number of subcarriers | +| | Scheduled bandwidth for uplink transmission, expressed as a number of resource blocks | +| | Number of modulation symbols to transmit per antenna port for a physical channel | +| | Number of transmission layers | +| | Size of bandwidth part ; see clause 4.4.4.4 | +| | Start of bandwidth part ; see clause 4.4.4.4 | +| | Cyclic prefix length; see clause 5.3.1 | +| | The size of the resource grid; see clauses 4.4.2 and 5.3 | +| | The start of the resource grid; see clause 4.4.2 | +| | The number of PT-RS groups; see clause 6.3.1.4 | +| | Physical layer cell identity; see clause 7.4.2.1 | +| | Physical-layer sidelink identity; see clause 8.4.2.1 | +| | Frequency-domain size of a control resource set; see clause 7.3.2.2 | +| | Number of resource-element groups in a CORESET; see clause 7.3.2.2 | +| | Number of samples per PT-RS group; see clause 6.3.1.4 | +| | Number of subcarriers per resource block, see clause 4.4.4.1 | +| | Number of slots per subframe for subcarrier spacing configuration , see clause 4.3.2 | +| | Number of slots per frame for subcarrier spacing configuration , see clause 4.3.2 | +| | Time duration of a control resource set; see clause 7.3.2.2 | +| | Length of the PUCCH transmission in OFDM symbols; see clause 6.3.2.1 | +| | Number of OFDM symbols per subframe for subcarrier spacing configuration ; see clause 4.3.1 | +| | Number of symbols per slot | +| | Timing advance between downlink and uplink; see clause 4.3.1 | +| | A fixed offset used to calculate the timing advance; see clause 4.3.1 | +| | Network-controlled timing correction; see clause 4.3.1 | +| | UE-derived timing correction; see clause 4.3.1 | +| | Minimum time from reception to transmission for a half-duplex UE; see clause 4.3.2 | +| | System frame number (SFN) | +| | Common resource block number for subcarrier spacing configuration , see clause 4.4.4.3 | +| | Hyper-frame number | +| | Physical resource block number; see clause 4.4.4.4 | +| | Radio network temporary identifier | +| | Slot number within a subframe for subcarrier spacing configuration ; see clause 4.3.2 | +| | Slot number within a frame for subcarrier spacing configuration ; see clause 4.3.2 | +| | Antenna port number | +| $Q_m$ | Modulation order | +| $\rho$ | Number of antenna ports | +| | Low-PAPR base sequence; see clause 5.2.2 | +| | Low-PAPR sequence; see clause 5.2.2 | +| | The time-continuous signal on antenna port and subcarrier spacing configuration for OFDM symbol in a subframe; see clause 5.3.1 | +| $T_c$ | Basic time unit for NR; see clause 4.1 | +| | Radio frame duration; see clause 4.3.1 | +| | Basic time unit for LTE | +| $T_{sf}$ | Subframe duration; see clause 4.3.1 | +| | Slot duration; see clause 4.3.2 | +| $T_{TA}$ | Timing advance between downlink and uplink; see clause 4.3.1 | +| | Precoding matrix for spatial multiplexing | + +## 3.3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|---------|-------------------------------------------------| +| BWP | Bandwidth Part | +| CCE | Control Channel Element | +| CORESET | Control Resource Set | +| CRB | Common Resource Block | +| CSI | Channel-State Information | +| CSI-RS | CSI Reference Signal | +| DCI | Downlink Control Information | +| DM-RS | Demodulation Reference Signal | +| FR1 | Frequency Range 1 as defined in TS 38.104 [8] | +| FR2 | Frequency Range 2 as defined in TS 38.104 [8] | +| IAB | Integrated Access and Backhaul | +| IAB-MT | IAB Mobile Termination | +| IE | Information Element | +| NCR | Network-Controlled repeater | +| NCR-MT | NCR Mobile Termination | +| PBCH | Physical Broadcast Channel | +| PDCCH | Physical Downlink Control Channel | +| PDSCH | Physical Downlink Shared Channel | +| PRACH | Physical Random-Access Channel | +| PRB | Physical Resource Block | +| PSS | Primary Synchronization Signal | +| PT-RS | Phase-tracking reference signal | +| PUCCH | Physical Uplink Control Channel | +| PUSCH | Physical Uplink Shared Channel | +| RAR | Random Access Response | +| REG | Resource-Element Group | +| RIM | Remote Interference Management | +| RIM-RS | Remote Interference Management Reference Signal | +| SRS | Sounding Reference Signal | +| SSS | Secondary Synchronization Signal | +| VRB | Virtual Resource Block | + +# --- 4 Frame structure and physical resources + +## 4.1 General + +Throughout this specification, unless otherwise noted, the size of various fields in the time domain is expressed in time units where Hz and . The constant where , and . + +Throughout this specification, unless otherwise noted, statements using the term "UE" in clauses 4, 5, 6, or 7 are equally applicable to the IAB-MT part of an IAB-node and the NCR-MT part of an NCR node. + +## 4.2 Numerologies + +supported as given by Table 4.2-1 where and the cyclic prefix for a downlink or + +Multiple OFDM numerologies are uplink bandwidth part are obtained from the higher-layer parameters *subcarrierSpacing* and *cyclicPrefix*, respectively. + +**Table 4.2-1: Supported transmission numerologies.** + +| | | Cyclic prefix | +|---|-----|------------------| +| 0 | 15 | Normal | +| 1 | 30 | Normal | +| 2 | 60 | Normal, Extended | +| 3 | 120 | Normal | +| 4 | 240 | Normal | +| 5 | 480 | Normal | +| 6 | 960 | Normal | + +## 4.3 Frame structure + +### 4.3.1 Frames and subframes + +Downlink, uplink, and sidelink transmissions are organized into frames with duration, each consisting of ten subframes of duration. The number of consecutive OFDM symbols per subframe is . Each frame is divided into two equally-sized half-frames of five subframes each with half-frame 0 consisting of subframes 0 – 4 and half-frame 1 consisting of subframes 5 – 9. + +There is one set of frames in the uplink and one set of frames in the downlink on a carrier. + +Uplink frame number for transmission from the UE shall start before the start of the corresponding downlink frame at the UE where + +- and are given by clause 4.2 of [5, TS 38.213], except for msgA transmission on PUSCH where shall be used; +- given by clause 4.2 of [5, TS 38.213] is derived from the higher-layer parameters *ta-Common*, *ta-CommonDrift*, and *ta-CommonDriftVariant* if configured, otherwise ; +- given by clause 4.2 of [5, TS 38.213] is computed by the UE based on UE position and serving-satellite-ephemeris-related higher-layers parameters if configured, otherwise . + +![Diagram illustrating the uplink-downlink timing relation. It shows two horizontal bars: 'Downlink frame i' at the top and 'Uplink frame i' below it. The 'Uplink frame i' bar is shifted to the left relative to the 'Downlink frame i' bar. A double-headed arrow labeled T_TA indicates the time difference between the start of the downlink frame and the start of the uplink frame.](63e0c22852c26699d0bd095a2d796bab_img.jpg) + +Diagram illustrating the uplink-downlink timing relation. It shows two horizontal bars: 'Downlink frame i' at the top and 'Uplink frame i' below it. The 'Uplink frame i' bar is shifted to the left relative to the 'Downlink frame i' bar. A double-headed arrow labeled T\_TA indicates the time difference between the start of the downlink frame and the start of the uplink frame. + +**Figure 4.3.1-1: Uplink-downlink timing relation.** + +### 4.3.2 Slots + +For subcarrier spacing configuration , slots are numbered in increasing order within a subframe and in increasing order within a frame. There are consecutive OFDM symbols in a slot where depends on the cyclic prefix as given by Tables 4.3.2-1 and 4.3.2-2. The start of slot in a subframe is aligned in time with the start of OFDM symbol in the same subframe. + +OFDM symbols in a slot in a downlink or uplink frame can be classified as 'downlink', 'flexible', or 'uplink'. Signaling of slot formats is described in clause 11.1 of [5, TS 38.213]. + +In a slot in a downlink frame, the UE shall assume that downlink transmissions only occur in 'downlink' or 'flexible' symbols. + +In a slot in an uplink frame, the UE shall only transmit in 'uplink' or 'flexible' symbols. + +A UE not capable of full-duplex communication and not supporting simultaneous transmission and reception as defined by parameter *simultaneousRxFxInterBandENDC*, *simultaneousRxFxInterBandCA* or *simultaneousRxFxSUL* [10, TS 38.306] among all cells within a group of cells is not expected to transmit in the uplink in one cell within the group of cells earlier than after the end of the last received downlink symbol in the same or different cell within the group of cells where is given by Table 4.3.2-3. + +A UE not capable of full-duplex communication and not supporting simultaneous transmission and reception as defined by parameter *simultaneousRxFxInterBandENDC*, *simultaneousRxFxInterBandCA* or *simultaneousRxFxSUL* [10, TS 38.306] among all cells within a group of cells is not expected to receive in the downlink in one cell within the group of cells earlier than after the end of the last transmitted uplink symbol in the same or different cell within the group of cells where is given by Table 4.3.2-3. + +For DAPS handover operation, a UE not capable of full-duplex communication is not expected to transmit in the uplink to a cell earlier than after the end of the last received downlink symbol in the different cell where is given by Table 4.3.2-3. + +For DAPS handover operation, a UE not capable of full-duplex communication is not expected to receive in the downlink from a cell earlier than after the end of the last transmitted uplink symbol in the different cell where is given by Table 4.3.2-3. + +A UE not capable of full-duplex communication is not expected to transmit in the uplink earlier than after the end of the last received downlink symbol in the same cell where is given by Table 4.3.2-3. + +A UE not capable of full-duplex communication is not expected to receive in the downlink earlier than after the end of the last transmitted uplink symbol in the same cell where is given by Table 4.3.2-3. + +**Table 4.3.2-1: Number of OFDM symbols per slot, slots per frame, and slots per subframe for normal cyclic prefix.** + +| | | | | +|---|----|-----|----| +| | | | | +| 0 | 14 | 10 | 1 | +| 1 | 14 | 20 | 2 | +| 2 | 14 | 40 | 4 | +| 3 | 14 | 80 | 8 | +| 4 | 14 | 160 | 16 | +| 5 | 14 | 320 | 32 | +| 6 | 14 | 640 | 64 | + +**Table 4.3.2-2: Number of OFDM symbols per slot, slots per frame, and slots per subframe for extended cyclic prefix.** + +| | | | | +|---|----|----|---| +| | | | | +| 2 | 12 | 40 | 4 | + +**Table 4.3.2-3: Transition time and** + +| Transition time | FR1 | FR2 | +|-----------------|-------|-------| +| | 25600 | 13792 | +| | 25600 | 13792 | + +## 4.4 Physical resources + +### 4.4.1 Antenna ports + +An antenna port is defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed. + +Two antenna ports are said to be quasi co-located if the large-scale properties of the channel over which a symbol on one antenna port is conveyed can be inferred from the channel over which a symbol on the other antenna port is conveyed. The large-scale properties include one or more of delay spread, Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters. + +### 4.4.2 Resource grid + +For each numerology and carrier, a resource grid of subcarriers and OFDM symbols is defined, starting at common resource block indicated by higher-layer signalling. There is one set of resource grids per transmission direction (uplink, downlink, or sidelink) with the subscript set to DL, UL, and SL for downlink, uplink, and sidelink, respectively. When there is no risk for confusion, the subscript may be dropped. There is one resource grid for a given antenna port, subcarrier spacing configuration, and transmission direction (downlink, uplink, or sidelink). + +For uplink and downlink, the carrier bandwidth for subcarrier spacing configuration is given by the higher-layer parameter *carrierBandwidth* in the *SCS-SpecificCarrier* IE. The starting position for subcarrier spacing configuration is given by the higher-layer parameter *offsetToCarrier* in the *SCS-SpecificCarrier* IE. + +The frequency location of a subcarrier refers to the center frequency of that subcarrier. + +For the downlink, the higher-layer parameter *txDirectCurrentLocation* in the *SCS-SpecificCarrier* IE indicates the location of the transmitter DC subcarrier in the downlink for each of the numerologies configured in the downlink. Values in the range 0 – 3299 represent the number of the DC subcarrier and the value 3300 indicates that the DC subcarrier is located outside the resource grid. + +For the uplink, the higher-layer parameter *txDirectCurrentLocation* in the *UplinkTxDirectCurrentBWP* IE indicates the location of the transmitter DC subcarrier in the uplink for each of the configured bandwidth parts, including whether the DC subcarrier location is offset by 7.5 kHz relative to the center of the indicated subcarrier or not. Values in the range 0 – 3299 represent the number of the DC subcarrier, the value 3300 indicates that the DC subcarrier is located outside the resource grid, and the value 3301 indicates that the position of the DC subcarrier in the uplink is undetermined. + +### 4.4.3 Resource elements + +Each element in the resource grid for antenna port and subcarrier spacing configuration is called a resource element and is uniquely identified by where $k$ is the index in the frequency domain and $n$ refers to the symbol position in the time domain relative to some reference point. Resource element $(k, n)$ corresponds to a physical resource and the complex value $s(k, n)$ . When there is no risk for confusion, or no particular antenna port or subcarrier spacing is specified, the indices $k$ and $n$ may be dropped, resulting in $s$ . + +### 4.4.4 Resource blocks + +#### 4.4.4.1 General + +A resource block is defined as consecutive subcarriers in the frequency domain. + +#### 4.4.4.2 Point A + +Point A serves as a common reference point for resource block grids and is obtained from: + +- *offsetToPointA* for a PCell downlink where *offsetToPointA* represents the frequency offset between point A and the lowest subcarrier of the lowest resource block, which overlaps with the SS/PBCH block, or the SS/PBCH block after puncturing if applicable, used by the UE for initial cell selection, expressed in units of resource blocks assuming 15 kHz subcarrier spacing for FR1 and 60 kHz subcarrier spacing for FR2; +- for operation without shared spectrum channel access in FR1 and FR2-1, the lowest resource block has the subcarrier spacing provided by the higher layer parameter *subCarrierSpacingCommon*; +- for operation with shared spectrum channel access in FR1 or FR2, and for operation without shared spectrum channel access in FR2-2, the lowest resource block has the subcarrier spacing same as the SS/PBCH block used by the UE for initial cell selection; +- *absoluteFrequencyPointA* for all other cases where *absoluteFrequencyPointA* represents the frequency-location of point A expressed as in ARFCN. + +#### 4.4.4.3 Common resource blocks + +Common resource blocks are numbered from 0 and upwards in the frequency domain for subcarrier spacing configuration. The center of subcarrier 0 of common resource block 0 for subcarrier spacing configuration coincides with 'point A'. + +The relation between the common resource block number in the frequency domain and resource elements for subcarrier spacing configuration is given by + +where is defined relative to point A such that corresponds to the subcarrier centered around point A. + +#### 4.4.4.4 Physical resource blocks + +Physical resource blocks for subcarrier spacing configuration are defined within a bandwidth part and numbered from 0 to where is the number of the bandwidth part. The relation between the physical resource block in bandwidth part and the common resource block is given by + +where is the common resource block where bandwidth part starts relative to common resource block 0. When there is no risk for confusion the index may be dropped. + +#### 4.4.4.5 Virtual resource blocks + +Virtual resource blocks are defined within a bandwidth part and numbered from 0 to where is the number of the bandwidth part. + +#### 4.4.4.6 Interlaced resource blocks + +Multiple interlaces of resource blocks are defined where interlace consists of common resource blocks , with being the number of interlaces given by Table 4.4.4.6-1. The relation between the interlaced resource block in bandwidth part and interlace and the common resource block is given by + +where is the common resource block where bandwidth part starts relative to common resource block 0. When there is no risk for confusion the index may be dropped. + +The UE expects that the number of common resource blocks in an interlace contained within bandwidth part is no less than 10. + +**Table 4.4.4.6-1: The number of resource block interlaces.** + +| | | +|---|----| +| | | +| 0 | 10 | +| 1 | 5 | + +### 4.4.5 Bandwidth part + +A bandwidth part is a subset of contiguous common resource blocks defined in clause 4.4.4.3 for a given numerology in bandwidth part on a given carrier. The starting position and the number of resource blocks in a bandwidth part shall fulfil and , respectively. Configuration of a bandwidth part is described in clause 12 of [5, TS 38.213]. + +A UE can be configured with up to four bandwidth parts in the downlink with a single downlink bandwidth part being active at a given time. The UE is not expected to receive PDSCH, PDCCH, or CSI-RS (except for RRM) outside an active bandwidth part. + +A UE can be configured with up to four bandwidth parts in the uplink with a single uplink bandwidth part being active at a given time. If a UE is configured with a supplementary uplink, the UE can in addition be configured with up to four bandwidth parts in the supplementary uplink with a single supplementary uplink bandwidth part being active at a given time. The UE shall not transmit PUSCH or PUCCH outside an active bandwidth part. For an active cell, the UE shall not transmit SRS outside an active bandwidth part. + +Unless otherwise noted, the description in this specification applies to each of the bandwidth parts. When there is no risk of confusion, the index may be dropped from , , , and . + +### 4.4.6 Common MBS frequency resource + +A common MBS frequency resource is a contiguous set of common resource blocks. The starting position of the common MBS frequency resource is defined relative to point A and the size of the common MBS frequency resource is given by . Resource blocks in a common MBS frequency resource are numbered in the same way as resource blocks in clause 4.4.4.4 with and replaced by and , respectively. + +A UE is not expected to receive PDSCH or PDCCH associated with MBS transmissions scheduled with G-RNTI, G-CS-RNTI, MCCH-RNTI, or multicast-MCCH-RNTI outside the common MBS frequency resource. + +## 4.5 Carrier aggregation + +Transmissions in multiple cells can be aggregated. Unless otherwise noted, the description in this specification applies to each of the serving cells. + +For carrier aggregation of cells with unaligned frame boundaries, the slot offset between a PCell/PSCell and an SCell is determined by higher-layer parameter *ca-SlotOffset* for the SCell. The quantity is defined as the maximum of the lowest subcarrier spacing configuration among the subcarrier spacings given by the higher-layer parameters *scs-SpecificCarrierList* configured for PCell/PSCell and the SCell, respectively. The slot offset fulfills + +- when the lowest subcarrier spacing configuration among the subcarrier spacings configured for the cell is for both cells or for both cells, the start of slot 0 for the cell whose point A has a lower frequency coincides with the start of slot for the other cell where if point A of the PCell/PSCell has a frequency lower than the frequency of point A for the SCell, otherwise ; +- otherwise, the start of slot 0 for the cell with the lower subcarrier spacing of the lowest subcarrier spacing given by the higher-layer parameters *scs-SpecificCarrierList* configured for the two cells, or the PCell/PSCell if both cells have the same lowest subcarrier spacing given by the higher-layer parameters *scs-SpecificCarrierList* configured for the two cells, coincides with the start of slot for the other cell where if the lowest subcarrier spacing configuration given by *scs-SpecificCarrierList* of the PCell/PSCell is smaller than or equal to the lowest subcarrier spacing given by *scs-SpecificCarrierList* for the SCell, otherwise . + +# 5 Generic functions + +## 5.1 Modulation mapper + +The modulation mapper takes binary digits, 0 or 1, as input and produces complex-valued modulation symbols as output. + +### 5.1.1 $\pi/2$ -BPSK + +In case of $\pi/2$ -BPSK modulation, bit is mapped to complex-valued modulation symbol according to + +### 5.1.2 BPSK + +In case of BPSK modulation, bit is mapped to complex-valued modulation symbol according to + +### 5.1.3 QPSK + +In case of QPSK modulation, pairs of bits, $b(2i), b(2i+1)$ , are mapped to complex-valued modulation symbols according to + +$$d(i) = \frac{1}{\sqrt{2}} [(1 - 2b(2i)) + j(1 - 2b(2i+1))]$$ + +### 5.1.4 16QAM + +In case of 16QAM modulation, quadruplets of bits, $b(4i), b(4i+1), b(4i+2), b(4i+3)$ , are mapped to complex-valued modulation symbols according to + +$$d(i) = \frac{1}{\sqrt{10}} \left\{ (1 - 2b(4i)) [2 - (1 - 2b(4i+2))] + j(1 - 2b(4i+1)) [2 - (1 - 2b(4i+3))] \right\}$$ + +### 5.1.5 64QAM + +In case of 64QAM modulation, hextuplets of bits, $b(6i), b(6i+1), b(6i+2), b(6i+3), b(6i+4), b(6i+5)$ , are mapped to complex-valued modulation symbols according to + +$$d(i) = \frac{1}{\sqrt{42}} \left\{ (1 - 2b(6i)) [4 - (1 - 2b(6i+2))] [2 - (1 - 2b(6i+4))] + j(1 - 2b(6i+1)) [4 - (1 - 2b(6i+3))] [2 - (1 - 2b(6i+5))] \right\}$$ + +### 5.1.6 256QAM + +In case of 256QAM modulation, octuplets of bits, $b(8i), b(8i+1), b(8i+2), b(8i+3), b(8i+4), b(8i+5), b(8i+6), b(8i+7)$ , are mapped to complex-valued modulation symbols according to + +$$d(i) = \frac{1}{\sqrt{170}} \left\{ (1 - 2b(8i)) [8 - (1 - 2b(8i+2))] [4 - (1 - 2b(8i+4))] [2 - (1 - 2b(8i+6))] + j(1 - 2b(8i+1)) [8 - (1 - 2b(8i+3))] [4 - (1 - 2b(8i+5))] [2 - (1 - 2b(8i+7))] \right\}$$ + +### 5.1.7 1024QAM + +In case of 1024QAM modulation, 10-tuplets of bits, , are mapped to complex-valued modulation symbols according to + +## 5.2 Sequence generation + +### 5.2.1 Pseudo-random sequence generation + +Generic pseudo-random sequences are defined by a length-31 Gold sequence. The output sequence of length, where, is defined by + +where and the first m-sequence shall be initialized with. The initialization of the second m-sequence, , is denoted by with the value depending on the application of the sequence. + +### 5.2.2 Low-PAPR sequence generation type 1 + +The low-PAPR sequence is defined by a cyclic shift of a base sequence according to + +where is the length of the sequence. Multiple sequences are defined from a single base sequence through different values of and . + +Base sequences are divided into groups, where is the group number and is the base sequence number within the group, such that each group contains one base sequence () of each length, $1/2 \leq m/2^{\delta} \leq 5$ and two base sequences () of each length, $6 \leq m/2^{\delta}$ . The definition of the base sequence depends on the sequence length. + +#### 5.2.2.1 Base sequences of length 36 or larger + +For, the base sequence is given by + +where + +The length is given by the largest prime number such that. + +#### 5.2.2.2 Base sequences of length less than 36 + +For the base sequence is given by + +where the value of is given by Tables 5.2.2.2-1 to 5.2.2.2-4. + +For , the base sequence is given by + +**Table 5.2.2.2-1: Definition of for.** + +| | $\varphi(0), \dots, \varphi(5)$ | | | | | | +|----|---------------------------------|---|----|---|----|----| +| 0 | -3 | 1 | 3 | 3 | -1 | -3 | +| 1 | -3 | 3 | -1 | 1 | 3 | -3 | +| 2 | -3 | 3 | -3 | 3 | 1 | -3 | +| 3 | 1 | 1 | 1 | 3 | -1 | -3 | +| 4 | 1 | 1 | 1 | 3 | -1 | 3 | +| 5 | -3 | 1 | -1 | 3 | -3 | -3 | +| 6 | -3 | 1 | 3 | 3 | -3 | -3 | +| 7 | -3 | 1 | 1 | 3 | 1 | -1 | +| 8 | -3 | 1 | -3 | 1 | -3 | -3 | +| 9 | -3 | 3 | 1 | 3 | 3 | -3 | +| 10 | -3 | 1 | 3 | 1 | -3 | -3 | +| 11 | -3 | 1 | -3 | 1 | 1 | -3 | +| 12 | 1 | 1 | 3 | 1 | -3 | 3 | +| 13 | 1 | 1 | 3 | 3 | -1 | 3 | +| 14 | 1 | 1 | 1 | 3 | 3 | -1 | +| 15 | 1 | 1 | 1 | 1 | 3 | -3 | +| 16 | -3 | 1 | -1 | 1 | 3 | -1 | +| 17 | -3 | 3 | -1 | 1 | -1 | -3 | +| 18 | -3 | 3 | -3 | 1 | -3 | -1 | +| 19 | -3 | 1 | 1 | 3 | -1 | -3 | +| 20 | -3 | 3 | -3 | 1 | 1 | -3 | +| 21 | -3 | 1 | -3 | 3 | -3 | -1 | +| 22 | 1 | 1 | -3 | 3 | 1 | 3 | +| 23 | 1 | 1 | -3 | 3 | 1 | -3 | +| 24 | 1 | 1 | 3 | 1 | 3 | 3 | +| 25 | 1 | 1 | -3 | 1 | 3 | 3 | +| 26 | 1 | 1 | -1 | 1 | 3 | -1 | +| 27 | 1 | 1 | -1 | 3 | -1 | -1 | +| 28 | 1 | 1 | -1 | 3 | -3 | -1 | +| 29 | 1 | 1 | -3 | 1 | -1 | -1 | + +Table 5.2.2.2-2: Definition of for. + +| | | | | | | | | | | | | | | +|----|----|----|----|----|----|----|----|----|----|----|----|----|----| +| | | | | | | | | | | | | | | +| 0 | -3 | 1 | -3 | -3 | -3 | 3 | -3 | -1 | 1 | 1 | 1 | 1 | -3 | +| 1 | -3 | 3 | 1 | -3 | 1 | 3 | -1 | -1 | 1 | 3 | 3 | 3 | 3 | +| 2 | -3 | 3 | 3 | 1 | -3 | 3 | -1 | 1 | 3 | -3 | 3 | -3 | -3 | +| 3 | -3 | -3 | -1 | 3 | 3 | 3 | -3 | 3 | -3 | 1 | 1 | -1 | -3 | +| 4 | -3 | -1 | -1 | 1 | 3 | 1 | 1 | -1 | 1 | -1 | -3 | 1 | 1 | +| 5 | -3 | -3 | 3 | 1 | -3 | -3 | -3 | -1 | 3 | -1 | 1 | 3 | 3 | +| 6 | 1 | -1 | 3 | -1 | -1 | -1 | -3 | -1 | 1 | 1 | 1 | 1 | -3 | +| 7 | -1 | -3 | 3 | -1 | -3 | -3 | -3 | -1 | 1 | -1 | 1 | -3 | -3 | +| 8 | -3 | -1 | 3 | 1 | -3 | -1 | -3 | 3 | 1 | 3 | 3 | 1 | 1 | +| 9 | -3 | -1 | -1 | -3 | -3 | -1 | -3 | 3 | 1 | 3 | -1 | -3 | -3 | +| 10 | -3 | 3 | -3 | 3 | 3 | -3 | -1 | -1 | 3 | 3 | 1 | -3 | -3 | +| 11 | -3 | -1 | -3 | -1 | -1 | -3 | 3 | 3 | -1 | -1 | 1 | -3 | -3 | +| 12 | -3 | -1 | 3 | -3 | -3 | -1 | -3 | 1 | -1 | -3 | 3 | 3 | 3 | +| 13 | -3 | 1 | -1 | -1 | 3 | 3 | -3 | -1 | -1 | -3 | -1 | -3 | -3 | +| 14 | 1 | 3 | -3 | 1 | 3 | 3 | 3 | 1 | -1 | 1 | 1 | -1 | 3 | +| 15 | -3 | 1 | 3 | -1 | -1 | -3 | -3 | -1 | -1 | 3 | 1 | -3 | -3 | +| 16 | -1 | -1 | -1 | -1 | 1 | -3 | -1 | 3 | 3 | -1 | -3 | 1 | 1 | +| 17 | -1 | 1 | 1 | -1 | 1 | 3 | 3 | -1 | -1 | -3 | 1 | -3 | -3 | +| 18 | -3 | 1 | 3 | 3 | -1 | -1 | -3 | 3 | 3 | -3 | 3 | -3 | -3 | +| 19 | -3 | -3 | 3 | -3 | -1 | 3 | 3 | 3 | -1 | -3 | 1 | -3 | -3 | +| 20 | 3 | 1 | 3 | 1 | 3 | -3 | -1 | 1 | 3 | 1 | -1 | -3 | -3 | +| 21 | -3 | 3 | 1 | 3 | -3 | 1 | 1 | 1 | 1 | 3 | -3 | 3 | 3 | +| 22 | -3 | 3 | 3 | 3 | -1 | -3 | -3 | -1 | -3 | 1 | 3 | -3 | -3 | +| 23 | 3 | -1 | -3 | 3 | -3 | -1 | 3 | 3 | 3 | -3 | -1 | -3 | -3 | +| 24 | -3 | -1 | 1 | -3 | 1 | 3 | 3 | 3 | -1 | -3 | 3 | 3 | 3 | +| 25 | -3 | 3 | 1 | -1 | 3 | 3 | -3 | 1 | -1 | 1 | 1 | -1 | 1 | +| 26 | -1 | 1 | 3 | -3 | 1 | -1 | 1 | -1 | -1 | -3 | 1 | -1 | -1 | +| 27 | -3 | -3 | 3 | 3 | 3 | -3 | -1 | 1 | -3 | 3 | 1 | -3 | -3 | +| 28 | 1 | -1 | 3 | 1 | 1 | -1 | -1 | -1 | 1 | 3 | -3 | 1 | 1 | +| 29 | -3 | 3 | -3 | 3 | -3 | -3 | 3 | -1 | -1 | 1 | 3 | -3 | -3 | + +Table 5.2.2.2-3: Definition of for + +| | | | | | | | | | | | | | | | | | | | +|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----| +| 0 | -1 | 3 | -1 | -3 | 3 | 1 | -3 | -1 | 3 | -3 | -1 | -1 | 1 | 1 | 1 | -1 | -1 | -1 | +| 1 | 3 | -3 | 3 | -1 | 1 | 3 | -3 | -1 | -3 | -3 | -1 | -3 | 3 | 1 | -1 | 3 | -3 | 3 | +| 2 | -3 | 3 | 1 | -1 | -1 | 3 | -3 | -1 | 1 | 1 | 1 | 1 | 1 | -1 | 3 | -1 | -3 | -1 | +| 3 | -3 | -3 | 3 | 3 | 3 | 1 | -3 | 1 | 3 | 3 | 1 | -3 | -3 | 3 | -1 | -1 | -1 | 1 | +| 4 | 1 | 1 | -1 | -1 | -1 | -1 | 1 | -3 | -3 | -3 | 1 | -3 | -1 | -1 | 1 | -1 | 3 | 1 | +| 5 | 3 | -3 | 1 | 1 | 3 | -1 | 1 | -1 | -1 | -3 | 1 | 1 | -1 | 3 | 3 | -3 | 3 | -1 | +| 6 | -3 | 3 | -1 | 1 | 3 | 1 | -3 | -1 | 1 | 1 | -3 | 1 | 3 | 3 | -1 | -3 | -3 | -3 | +| 7 | 1 | 1 | -3 | 3 | 3 | 1 | 3 | -3 | 3 | -1 | 1 | 1 | -1 | 1 | -3 | -1 | -1 | 3 | +| 8 | -3 | 1 | -3 | -3 | 1 | -3 | -3 | 3 | 1 | -3 | -1 | -3 | -3 | -3 | -1 | 1 | 1 | 3 | +| 9 | 3 | -1 | 3 | 1 | -3 | -3 | -1 | 1 | -3 | -3 | 3 | 3 | 3 | 1 | 3 | -3 | 3 | -3 | +| 10 | -3 | -3 | -3 | 1 | -3 | 3 | 1 | 1 | 3 | -3 | -3 | 1 | 3 | -1 | 3 | -3 | -3 | 3 | +| 11 | -3 | -3 | 3 | 3 | 3 | -1 | -1 | -3 | -1 | -1 | -1 | 3 | 1 | -3 | -3 | -3 | 3 | -1 | +| 12 | -3 | -1 | -3 | -3 | 1 | 1 | -1 | -3 | -1 | -1 | -1 | -1 | 3 | 3 | -1 | 3 | 1 | 3 | +| 13 | 1 | 1 | -3 | -3 | -3 | -3 | 1 | 3 | -3 | 3 | 3 | 1 | -3 | -1 | 3 | -1 | -3 | 1 | +| 14 | -3 | 3 | -1 | -3 | -1 | -3 | 1 | 1 | -3 | -3 | -1 | -1 | 3 | -3 | 1 | 3 | 1 | 1 | +| 15 | 3 | 1 | -3 | 1 | -3 | 3 | 3 | -1 | -3 | -3 | -1 | -3 | -3 | 3 | -3 | -1 | 1 | 3 | +| 16 | -3 | -1 | -3 | -1 | -1 | 1 | 3 | -3 | -1 | 3 | 3 | 3 | 1 | -1 | -3 | 3 | -1 | -3 | +| 17 | -3 | -1 | 3 | 3 | -1 | 3 | -1 | -3 | -1 | 1 | -1 | -3 | -1 | -1 | -1 | 3 | 3 | 1 | +| 18 | -3 | 1 | -3 | -1 | -1 | 3 | 1 | -3 | -3 | -3 | -1 | -3 | -3 | 1 | 1 | 1 | -1 | -1 | +| 19 | 3 | 3 | 3 | -3 | -1 | -3 | -1 | 3 | -1 | 1 | -1 | -3 | 1 | -3 | -3 | -1 | 3 | 3 | +| 20 | -3 | 1 | 1 | -3 | 1 | 1 | 3 | -3 | -1 | -1 | -1 | 3 | -3 | 3 | -1 | -1 | -1 | -3 | +| 21 | 1 | -3 | -1 | -3 | 3 | 3 | -1 | -3 | 1 | -3 | -3 | -1 | -3 | -1 | 1 | 3 | 3 | 3 | +| 22 | -3 | -3 | 1 | -1 | -1 | 1 | 1 | -3 | -1 | 3 | 3 | 3 | 3 | -1 | 3 | 1 | 3 | 1 | +| 23 | 3 | -1 | -3 | 1 | -3 | -3 | -3 | 3 | 3 | -1 | 1 | -3 | -1 | 3 | 1 | 1 | 3 | 3 | +| 24 | 3 | -1 | -1 | 1 | -1 | -1 | -3 | -1 | -3 | -3 | -1 | -3 | 1 | 1 | 1 | -3 | -3 | 3 | +| 25 | -3 | -3 | 1 | -3 | 3 | 3 | 3 | -1 | 3 | 1 | 1 | -3 | -3 | -3 | 3 | -1 | -1 | -1 | +| 26 | -3 | -1 | -1 | -3 | 1 | -3 | 3 | -1 | -1 | -3 | 3 | 3 | -3 | -1 | 3 | -1 | -1 | -1 | +| 27 | -3 | -3 | 3 | 3 | -1 | 1 | 3 | -1 | -3 | 1 | -1 | -3 | 3 | -3 | -1 | -1 | -1 | 3 | +| 28 | -1 | -3 | 1 | -3 | -3 | -3 | 1 | 1 | 3 | 3 | -3 | 3 | 3 | -3 | -1 | 3 | -3 | 1 | +| 29 | -3 | 3 | 1 | -1 | -1 | -1 | -1 | 1 | -1 | 3 | 3 | -3 | -1 | 1 | 3 | -1 | 3 | -1 | + +Table 5.2.2.2-4: Definition of for + +| | | | | | | | | | | | | | | | | | | | | | | | | | | +|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----| +| 0 | -1 | -3 | 3 | -1 | 3 | 1 | 3 | -1 | 1 | -3 | -1 | -3 | -1 | 1 | 3 | -3 | -1 | -3 | 3 | 3 | 3 | -3 | -3 | -3 | | +| 1 | -1 | -3 | 3 | 1 | 1 | -3 | 1 | -3 | - | 1 | -3 | -1 | -1 | 3 | -3 | 3 | 3 | 3 | - | 1 | 3 | 3 | -3 | -3 | | +| 2 | -1 | -3 | -3 | 1 | -1 | -1 | -3 | 1 | 3 | -1 | -3 | -1 | -1 | -3 | 1 | 1 | 3 | 1 | - | -1 | -1 | 3 | -3 | -3 | | +| 3 | 1 | -3 | 3 | -1 | -3 | -1 | 3 | 3 | 1 | -1 | 1 | 1 | 3 | -3 | -1 | -3 | -3 | -3 | - | 3 | -3 | -1 | -3 | -3 | | +| 4 | -1 | 3 | -3 | -3 | -1 | 3 | -1 | -1 | 1 | 3 | 1 | 3 | -1 | -1 | -3 | 1 | 3 | 1 | - | -3 | 1 | -1 | -3 | -3 | | +| 5 | -3 | -1 | 1 | -3 | -3 | 1 | 1 | -3 | 3 | -1 | -1 | -3 | 1 | 3 | 1 | -1 | -3 | -1 | - | 1 | -3 | -3 | -3 | -3 | | +| 6 | -3 | 3 | 1 | 3 | -1 | 1 | -3 | 1 | - | 1 | -1 | -3 | -1 | -3 | -3 | -3 | -3 | -1 | - | -1 | 1 | 1 | -3 | -3 | | +| 7 | -3 | 1 | 3 | -1 | 1 | -1 | 3 | -3 | 3 | -1 | -3 | -1 | -3 | 3 | -1 | -1 | -1 | -3 | - | -1 | -3 | 3 | 3 | -3 | | +| 8 | -3 | 1 | -3 | 3 | -1 | -1 | -1 | -3 | 3 | 1 | -1 | -3 | -1 | 1 | 3 | -1 | 1 | -1 | 1 | -3 | -3 | -3 | -3 | -3 | | +| 9 | 1 | 1 | -1 | -3 | -1 | 1 | 1 | -3 | 1 | -1 | 1 | -3 | 3 | -3 | -3 | 3 | -1 | -3 | 1 | 3 | -3 | 1 | -3 | -3 | | +| 10 | -3 | -3 | -3 | -1 | 3 | -3 | 3 | 1 | 3 | 1 | -3 | -1 | -1 | -3 | 1 | 1 | 3 | 1 | - | -3 | 3 | 1 | 3 | -3 | | +| 11 | -3 | 3 | -1 | 3 | 1 | -1 | -1 | -1 | 3 | 3 | 1 | 1 | 1 | 3 | 3 | 1 | -3 | -3 | - | 1 | -3 | 1 | 3 | -3 | | +| 12 | 1 | 3 | -3 | 3 | -1 | -3 | 1 | 3 | 1 | - | -1 | -3 | -1 | 3 | -3 | 3 | -1 | -1 | 3 | 3 | -3 | -3 | 3 | -3 | -3 | +| 13 | 1 | -3 | 3 | -1 | 3 | -1 | 3 | 3 | 1 | 1 | -3 | 1 | 3 | -3 | 3 | -3 | -3 | -1 | 1 | 3 | -3 | -1 | -1 | -3 | -3 | +| 14 | 1 | -3 | 1 | -3 | -1 | -1 | 3 | 1 | 3 | - | 1 | -1 | 3 | 3 | -1 | -3 | 3 | -3 | -1 | - | -3 | -3 | -3 | 3 | -3 | +| 15 | 1 | -3 | -1 | -1 | -3 | 1 | -3 | -3 | -1 | - | 3 | -1 | 1 | -1 | 3 | 1 | -3 | -1 | 3 | 1 | 1 | -1 | -1 | -3 | -3 | +| 16 | 1 | -3 | -3 | 1 | -1 | 3 | 3 | -3 | -1 | 1 | -1 | -1 | 1 | 1 | -1 | -1 | 3 | -3 | 1 | - | 1 | -1 | -1 | -1 | -3 | +| 17 | 1 | 3 | -1 | 3 | -1 | 1 | -3 | 1 | 1 | - | -3 | 3 | -3 | -1 | -1 | -1 | -1 | -1 | -3 | - | -1 | 1 | 1 | -3 | -3 | +| 18 | 1 | -3 | 1 | -3 | 1 | -3 | -3 | 1 | -3 | 1 | -3 | -3 | -3 | -3 | 1 | -3 | -3 | 1 | 1 | -3 | 1 | 1 | -3 | -3 | | +| 19 | 1 | -3 | -3 | 3 | 3 | 1 | -1 | -1 | -1 | 1 | -3 | -1 | 1 | -1 | 3 | -3 | -1 | -3 | -1 | - | 1 | -3 | 3 | -1 | -3 | +| 20 | 2 | -3 | -3 | -1 | -1 | -1 | -3 | 1 | -1 | - | -1 | 3 | -3 | 1 | -3 | 3 | -3 | 3 | 3 | 1 | -1 | -1 | 1 | -3 | -3 | +| 21 | 2 | 3 | -1 | 1 | -1 | 3 | -3 | 1 | 1 | 3 | -1 | -3 | 3 | 1 | -3 | 3 | -1 | -1 | -1 | - | 1 | -3 | -3 | -3 | -3 | +| 22 | 2 | -3 | 1 | -3 | 3 | -3 | 1 | -3 | 3 | 1 | -1 | -3 | -1 | -3 | -3 | -3 | -3 | 1 | 3 | - | 1 | 3 | 3 | 3 | -3 | +| 23 | 2 | -3 | -1 | 1 | -3 | -1 | -1 | 1 | 1 | 1 | 3 | 3 | -1 | 1 | -1 | 1 | -1 | -1 | -3 | - | -3 | 3 | 1 | -1 | -3 | +| 24 | 2 | -3 | 3 | -1 | -3 | -1 | -1 | -1 | 3 | - | -1 | 3 | -3 | -1 | 3 | -3 | 3 | -3 | -1 | 3 | 1 | 1 | -1 | -3 | -3 | +| 25 | 2 | -3 | 1 | -1 | -3 | -3 | -1 | 1 | -3 | - | -3 | 1 | 1 | -1 | 1 | 1 | 3 | 3 | 3 | - | 1 | -1 | 1 | -1 | -3 | +| 26 | 2 | -1 | 3 | -1 | -1 | 3 | 3 | -1 | -1 | - | 3 | -1 | -3 | 1 | 3 | 1 | 1 | -3 | -3 | - | -1 | -3 | -1 | -3 | -3 | +| 27 | 2 | 3 | -3 | -3 | -1 | 3 | 3 | -3 | -1 | 3 | 1 | 1 | 1 | 3 | -1 | 3 | -3 | -1 | 3 | - | 3 | 1 | -1 | -3 | -3 | +| 28 | 2 | -3 | 1 | -3 | 1 | -3 | 1 | 1 | 3 | 1 | -3 | -3 | -1 | 1 | 3 | -1 | -3 | 3 | 1 | - | -3 | -3 | -3 | -3 | -3 | +| 29 | 2 | 3 | -3 | -1 | 1 | 3 | -1 | -1 | -3 | - | 3 | -1 | -3 | -1 | -3 | 3 | -1 | 3 | 1 | 1 | -3 | 3 | -3 | -3 | -3 | + +### 5.2.3 Low-PAPR sequence generation type 2 + +The low-PAPR sequence is defined by a base sequence according to + +where $N$ is the length of the sequence. + +Base sequences are divided into groups, where $u$ is the group number and $v$ is the base sequence number within the group, such that each group contains one base sequence $(u, v)$ of length $N$ . The sequence $c_{u,v}(n)$ is defined by + +where the definition of $\alpha$ depends on the sequence length. + +#### 5.2.3.1 Sequences of length 30 or larger + +For $N \geq 30$ , the sequence $c_{u,v}(n)$ is obtained as the complex-valued modulations symbols resulting from $\pi/2$ -BPSK modulation as defined in clause 5.1.1 applied to the binary sequence $b_{u,v}(n)$ given by clause 5.2.1, initialized with $b_{u,v}(0) = 1$ . + +#### 5.2.3.2 Sequences of length less than 30 + +For $N < 30$ , the sequence $c_{u,v}(n)$ is given by + +where the value of $\alpha$ is given by Table 5.2.3.2-1. + +For $N < 30$ , the sequence $c_{u,v}(n)$ is obtained as the complex-valued modulations symbols resulting from $\pi/2$ -BPSK modulation as defined in clause 5.1.1 applied to the binary sequence $b_{u,v}(n)$ given by Tables 5.2.3.2-2 to 5.2.3.2-4. + +**Table 5.2.3.2-1: Definition of $\alpha$ .** + +| | | | | | | | +|----|----|---|----|---|----|----| +| | | | | | | | +| 0 | -1 | - | -3 | - | -1 | 3 | +| | | 7 | | 5 | | | +| 1 | -1 | 3 | 7 | - | 7 | 3 | +| | | | | 3 | | | +| 2 | -1 | 3 | 1 | 5 | -1 | -5 | +| 3 | -7 | - | -7 | 5 | -7 | -3 | +| | | 3 | | | | | +| 4 | 7 | 5 | -1 | - | -3 | 1 | +| | | | | 7 | | | +| 5 | 3 | - | 1 | 5 | -1 | -1 | +| | | 3 | | | | | +| 6 | -7 | - | -7 | - | 7 | -5 | +| | | 3 | | 3 | | | +| 7 | -7 | - | 1 | - | -1 | -5 | +| | | 3 | | 5 | | | +| 8 | -7 | - | 3 | - | -7 | -3 | +| | | 3 | | 3 | | | +| 9 | -7 | - | -1 | 1 | -5 | 1 | +| | | 7 | | | | | +| 10 | -7 | - | -7 | 5 | -1 | 5 | +| | | 3 | | | | | +| 11 | -7 | - | -3 | 1 | 5 | -1 | +| | | 7 | | | | | +| 12 | 5 | 7 | -3 | - | 5 | -5 | +| | | | | 5 | | | +| 13 | -3 | 7 | -5 | - | -5 | -1 | +| | | | | 1 | | | +| 14 | 5 | - | 7 | 1 | 5 | 1 | +| | | 7 | | | | | +| 15 | -7 | 3 | 1 | 5 | -1 | 3 | +| | | | | | | | +| 16 | -7 | - | -1 | - | -5 | 5 | +| | | 5 | | 7 | | | +| 17 | -7 | 1 | -3 | 3 | 7 | 5 | +| | | | | | | | +| 18 | -7 | - | 3 | 5 | 1 | 5 | +| | | 7 | | | | | +| 19 | -7 | - | 3 | - | 3 | -5 | +| | | 3 | | 1 | | | +| 20 | -7 | - | 5 | 3 | -7 | -1 | +| | | 5 | | | | | +| 21 | 1 | 5 | 1 | 5 | 3 | 7 | +| | | | | | | | +| 22 | 1 | - | 1 | - | -1 | 3 | +| | | 3 | | 5 | | | +| 23 | 1 | 7 | 1 | - | -7 | -1 | +| | | | | 5 | | | +| 24 | 1 | - | 3 | - | -7 | -3 | +| | | 1 | | 1 | | | +| 25 | 1 | - | -5 | - | 3 | -3 | +| | | 1 | | 1 | | | +| 26 | 1 | - | 3 | - | 3 | 7 | +| | | 1 | | 1 | | | +| 27 | -5 | 3 | 7 | 5 | 3 | 7 | +| | | | | | | | +| 28 | -7 | 1 | -3 | 1 | 5 | 1 | +| | | | | | | | +| 29 | 1 | 5 | 3 | - | 5 | -3 | +| | | | | 7 | | | + +**Table 5.2.3.2-2: Definition of $\rho$ for .** + +| | | +|----|-----------------------------| +| 0 | 0 0 0 0 0 0 1 1 0 1 1 0 | +| 1 | 0 0 0 0 0 0 1 0 0 0 1 1 1 | +| 2 | 0 0 0 0 0 0 1 1 1 1 0 1 1 1 | +| 3 | 1 1 0 1 1 0 1 0 1 0 0 0 0 | +| 4 | 1 1 0 0 1 0 1 0 1 0 0 1 | +| 5 | 1 0 1 1 0 1 0 0 1 0 1 1 | +| 6 | 0 0 0 1 0 0 1 0 0 0 1 0 | +| 7 | 0 1 0 0 0 1 0 0 1 0 0 0 | +| 8 | 1 0 1 1 1 1 0 1 1 0 1 1 | +| 9 | 1 0 1 1 0 1 1 1 1 0 0 0 | +| 10 | 1 0 1 1 0 1 0 0 0 1 1 0 | +| 11 | 1 0 1 0 0 1 0 0 1 0 1 0 | +| 12 | 1 1 0 0 0 0 0 1 1 1 1 0 | +| 13 | 0 1 0 0 0 1 1 0 1 0 1 1 | +| 14 | 0 0 0 0 0 1 1 0 0 0 1 1 | +| 15 | 0 0 0 0 0 1 0 0 1 0 0 1 | +| 16 | 0 0 1 0 0 1 0 0 0 0 0 1 | +| 17 | 0 0 0 0 0 1 1 0 1 1 1 0 | +| 18 | 0 0 0 1 1 1 1 1 0 0 0 1 | +| 19 | 1 0 0 0 1 0 0 0 0 0 1 1 | +| 20 | 0 1 1 1 1 0 1 0 1 1 1 1 | +| 21 | 0 1 1 1 0 1 0 0 1 1 0 1 | +| 22 | 0 1 1 1 1 1 0 0 1 0 0 0 | +| 23 | 0 1 1 1 0 0 0 0 0 1 0 0 | +| 24 | 0 0 1 1 1 1 1 1 1 1 0 0 | +| 25 | 0 1 1 1 0 0 1 1 0 1 0 0 | +| 26 | 0 1 1 1 0 1 1 1 0 1 1 1 | +| 27 | 0 1 1 1 1 1 1 0 0 0 1 1 | +| 28 | 0 1 1 1 1 0 0 0 0 0 1 1 | +| 29 | 0 1 1 1 0 1 1 1 1 0 1 1 | + +**Table 5.2.3.2-3: Definition of for .** + +| | | | | | | | | | | | | | | | | | | | | | +|----|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---| +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | 0 | 0 | 1 | +| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | +| 2 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 0 | 1 | 1 | 1 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | +| 3 | 0 | 1 | 0 | 1 | 1 | 0 | 1 | 1 | 0 | 0 | 0 | 1 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | +| 4 | 1 | 1 | 0 | 1 | 0 | 0 | 1 | 0 | 1 | 0 | 1 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 0 | 0 | +| 5 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 0 | 0 | 1 | 0 | 1 | 1 | 0 | 1 | 1 | 0 | 0 | 0 | +| 6 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 7 | 0 | 1 | 0 | 1 | 0 | 0 | 0 | 1 | 1 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | +| 8 | 0 | 0 | 1 | 0 | 1 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | 1 | +| 9 | 1 | 0 | 1 | 1 | 0 | 0 | 1 | 0 | 1 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | 1 | +| 10 | 1 | 0 | 1 | 1 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | +| 11 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | 1 | 1 | 0 | 1 | 1 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | +| 12 | 1 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | 1 | 0 | 0 | 0 | 1 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | +| 13 | 1 | 0 | 1 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | +| 14 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | +| 15 | 0 | 0 | 1 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | 0 | 0 | 0 | 1 | 1 | 0 | 1 | 0 | 0 | 0 | +| 16 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | 1 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | +| 17 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | +| 18 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | +| 19 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | 1 | 1 | 1 | 1 | +| 20 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | +| 21 | 1 | 1 | 1 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | +| 22 | 1 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 1 | 1 | 0 | 1 | 1 | 1 | 1 | 1 | +| 23 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 1 | 0 | 1 | +| 24 | 1 | 1 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 1 | 1 | 0 | 0 | 0 | +| 25 | 1 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 0 | +| 26 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | +| 27 | 0 | 1 | 1 | 0 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | +| 28 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | +| 29 | 0 | 1 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | + +Table 5.2.3.2-4: Definition of for + +| | | | | | | | | | | | | | | | | | | | | | | | | +|----|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---| +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | +| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 1 | 1 | 0 | 1 | 1 | 1 | 0 | 0 | 0 | 1 | 1 | 0 | +| 2 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 1 | 1 | 0 | 1 | 1 | +| 3 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 1 | 1 | 0 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 0 | 1 | 1 | +| 4 | 1 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | 1 | 1 | 0 | 1 | 1 | 0 | 0 | 0 | 1 | 1 | +| 5 | 1 | 0 | 1 | 0 | 1 | 1 | 0 | 1 | 1 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | 1 | 0 | 1 | 1 | +| 6 | 0 | 1 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 1 | 1 | 0 | +| 7 | 1 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | 1 | 0 | 0 | 1 | 1 | 1 | 0 | 0 | 1 | 1 | 0 | +| 8 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 1 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | +| 9 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 1 | 0 | +| 10 | 1 | 0 | 1 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | 0 | 1 | 1 | 1 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | +| 11 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 1 | +| 12 | 1 | 0 | 1 | 0 | 0 | 1 | 1 | 1 | 1 | 0 | 1 | 0 | 0 | 1 | 0 | 1 | 1 | 1 | 0 | 0 | 1 | 0 | 1 | +| 13 | 1 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 0 | 1 | 1 | 0 | 0 | 1 | +| 14 | 1 | 0 | 1 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | +| 15 | 1 | 0 | 0 | 1 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | 0 | +| 16 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | 0 | 1 | 0 | 0 | 1 | 1 | 1 | 0 | 1 | 1 | 1 | 0 | 0 | +| 17 | 1 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 0 | 0 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 1 | +| 18 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 0 | 0 | 0 | 1 | 0 | 1 | 1 | 0 | 0 | 0 | 1 | +| 19 | 1 | 0 | 0 | 0 | 1 | 0 | 1 | 1 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | +| 20 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | 1 | 1 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | +| 21 | 0 | 1 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | +| 22 | 1 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | 1 | 0 | 0 | 0 | 1 | 0 | 1 | 1 | +| 23 | 1 | 0 | 0 | 1 | 1 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | +| 24 | 1 | 0 | 0 | 0 | 1 | 1 | 0 | 1 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | +| 25 | 1 | 0 | 1 | 0 | 1 | 1 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | +| 26 | 0 | 1 | 0 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | +| 27 | 0 | 1 | 0 | 1 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 0 | 1 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | +| 28 | 0 | 1 | 0 | 0 | 0 | 1 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | +| 29 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | 0 | 1 | + +## 5.3 OFDM baseband signal generation + +### 5.3.1 OFDM baseband signal generation for all channels except PRACH and RIM-RS + +The time-continuous signal on antenna port and subcarrier spacing configuration for OFDM symbol $l \in \{0, 1, \dots, N_{\text{slot}}^{\text{subframe}, \mu} N_{\text{symb}}^{\text{slot}} - 1\}$ in a subframe for any physical channel or signal except PRACH is defined by + +where at the start of the subframe, + +and + +- is given by clause 4.2; +- is the subcarrier spacing configuration; +- is the largest value among the subcarrier spacing configurations by *scs-SpecificCarrierList* for each of uplink and downlink and by *sl-SCS-SpecificCarrierList* for sidelink. + +The starting position of OFDM symbol for subcarrier spacing configuration in a subframe is given by + +In case of cyclic prefix extension of the first OFDM symbol allocated for PUSCH, SRS, PUCCH, PSCCH/PSSCH, PSFCH, or S-SS/PSBCH block transmission, the time-continuous signal for the interval preceding the first OFDM symbol for PUSCH, SRS, PUCCH, PSCCH/PSSCH, PSFCH, or S-SS/PSBCH block is given by + +where refers to the signal in the previous subframe and + +- for dynamically scheduled PUSCH, SRS, and PUCCH transmissions + +where is given by Table 5.3.1-1 with for , for , and and given by the higher-layer parameters *cp-ExtensionC2* and *cp-ExtensionC3*, respectively, and given by clause 4.3.1. For contention-based random access, or in absence of higher-layer configuration of and , the value of shall be set to the largest integer fulfilling for each of the values of . *Text* is applied to the first UL transmission scheduled by the scheduling DCI. + +- for a PUSCH transmission using configured grant + +where is given by Table 5.3.1-2 with the index given by the procedure in [6, TS 38.214]. + +- for PSCCH/PSSCH, PSFCH, and S-SS/PSBCH block transmission + +where and are given by Table 5.3.1-3 with the index given by the procedure in [5, TS 38.213] or [6, TS 38.214]. + +**Table 5.3.1-1: The variables and for uplink cyclic prefix extension** + +| index | | | +|-------|---|---| +| 0 | - | - | +| 1 | | | +| 2 | | | +| 3 | | | + +**Table 5.3.1-2: The variable for uplink cyclic prefix extension with configured grants.** + +| index | | +|-------|--| +| 0 | | +| 1 | | +| 2 | | +| 3 | | +| 4 | | +| 5 | | +| 6 | | + +**Table 5.3.1-3: The variables and for sidelink cyclic prefix extension** + +| Index | | | | | | | +|-------|--|--|--|--|--|--| +|-------|--|--|--|--|--|--| + +| | | | | | | | +|---|---|---|---|---|---|---| +| 0 | - | - | - | - | - | - | +| 1 | 1 | | 1 | | 1 | | +| 2 | 1 | | 1 | | 2 | | +| 3 | 1 | | 2 | | 2 | | +| 4 | 1 | | 2 | | - | - | +| 5 | 1 | | 2 | | - | - | +| 6 | 1 | | 2 | | - | - | +| 7 | - | - | 2 | | - | - | +| 8 | - | - | 2 | | - | - | + +### 5.3.2 OFDM baseband signal generation for PRACH + +The time-continuous signal on antenna port for PRACH is defined by + +where and + +- is given by clause 6.3.3; +- is the subcarrier spacing of the initial uplink bandwidth part during initial access. Otherwise, is the subcarrier spacing of the active uplink bandwidth part; +- is the largest value among the subcarrier spacing configurations by the higher-layer parameter *scs-SpecificCarrierList*; +- $N_{\text{BWP},i}^{\text{start}}$ is the lowest numbered resource block of the initial uplink bandwidth part and is derived by the higher-layer parameter *initialUplinkBWP* during initial access. Otherwise, $N_{\text{BWP},i}^{\text{start}}$ is the lowest numbered resource block of the active uplink bandwidth part and is derived by the higher-layer parameter *BWP-Uplink*; +- is the frequency offset of the lowest PRACH transmission occasion in frequency domain with respect to physical resource block 0 of the active uplink bandwidth part. The quantity is given by the higher-layer parameter *msgA-RO-FrequencyStart* if configured and a type-2 random-access procedure is initiated as described in clause 8.1 of [5, TS 38.213], otherwise by *msg1-FrequencyStart* as described in clause 8.1 of [5 TS 38.213]; +- $n_{\text{RA}}$ is the PRACH transmission occasion index in frequency domain for a given PRACH transmission occasion in one time instance as given by clause 6.3.3.2; +- $N_{\text{RB}}^{\text{RA}}$ is the number of resource blocks occupied and is given by the parameter allocation expressed in number of RBs for PUSCH in Table 6.3.3.2-1. +- is the start CRB index of uplink RB set corresponding to the quantity . 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] +- is the index of the RB set which contains the lowest PRACH transmission occasion in frequency domain indicated by . The UE may assume that is configured such that each PRACH transmission occasion is fully contained within an RB set. +- and are given by clause 6.3.3 +- where + - for , + - for kHz, is the number of times the interval overlaps with either time instance 0 or time instance in a subframe + +The starting position of the PRACH preamble in a subframe (for $\Delta f_{\text{RA}} \in \{1.25, 5, 15, 30\} \text{ kHz}$ ) or in a 60 kHz slot (for kHz) is given by + +$$t_{\text{start}}^{\text{RA}} = t_{\text{start},l}^{\mu}$$ + +$$t_{\text{start},l}^{\mu} = \begin{cases} 0 & l = 0 \\ t_{\text{start},l-1}^{\mu} + (N_{\text{u}}^{\mu} + N_{\text{CP},l-1}^{\mu}) \cdot T_{\text{c}} & \text{otherwise} \end{cases}$$ + +where + +- the subframe or 60 kHz slot is assumed to start at ; +- a timing advance value shall be assumed; +- and are given by clause 5.3.1; +- $\mu = 0$ shall be assumed for kHz, otherwise the value of corresponds to kHz and the symbol position $l$ is given by + +where + +- $l_0$ is given by the parameter "starting symbol" in Tables 6.3.3.2-2 to 6.3.3.2-4; +- $n_t^{\text{RA}}$ is the PRACH transmission occasion within the PRACH slot, numbered in increasing order from 0 to $N_t^{\text{RA,slot}} - 1$ within a RACH slot where $N_t^{\text{RA,slot}}$ is given Tables 6.3.3.2-2 to 6.3.3.2-4 for and fixed to 1 for $L_{\text{RA}} = 839$ ; +- $N_{\text{dur}}^{\text{RA}}$ is given by Tables 6.3.3.2-2 to 6.3.3.2-4; +- $n_{\text{slot}}^{\text{RA}}$ is given by + - if kHz, then $n_{\text{slot}}^{\text{RA}} = 0$ + - if kHz and either of "Number of PRACH slots within a subframe" in Tables 6.3.3.2-2 to 6.3.3.2-3 or "Number of PRACH slots within a 60 kHz slot" in Table 6.3.3.2-4 is equal to 1, then , otherwise + - if kHz and + - the "Number of PRACH slots within a 60 kHz slot" in Table 6.3.3.2-4 is equal to 1, then for kHz and for kHz, or + - the "Number of PRACH slots within a 60 kHz slot" in Table 6.3.3.2-4 is equal to 2, then for kHz and for kHz. + +If the preamble format given by Tables 6.3.3.2-2 to 6.3.3.2-4 is A1/B1, A2/B2 or A3/B3, then + +- if , then the PRACH preamble with the corresponding PRACH preamble format from B1, B2 and B3 is transmitted in the PRACH transmission occasion; +- otherwise the PRACH preamble with the corresponding PRACH preamble format from A1, A2 and A3 is transmitted in the PRACH transmission occasion + +### 5.3.3 OFDM baseband signal generation for RIM-RS + +The time-continuous signal on antenna port for RIM-RS is defined by + +where + +and + +- where $\Delta f$ is the subcarrier spacing configuration for the RIM-RS; +- $f_{start}$ is the starting frequency offset of the RIM-RS as given by clause 7.4.1.6.4.3; +- $N$ is the length of the RIM-RS sequence where $N$ is the bandwidth of the RIM-RS in resource blocks; +- $s$ is the starting symbol given by clause 7.4.1.6.3; +- $\rho$ is given by clause 5.3.1 with $\rho = 1$ ; +- $\rho$ is given by clause 5.3.1 with $\rho = 2$ . + +## 5.4 Modulation and upconversion + +Modulation and upconversion to the carrier frequency $f_c$ of the complex-valued OFDM baseband signal for antenna port $p$ , subcarrier spacing configuration $\Delta f$ , and OFDM symbol $s$ in a subframe assumed to start at $t$ is given by + +- for PRACH +- for RIM-RS + +where $f_{ref}$ is the configured reference point for RIM-RS; + +- for all other channels and signals + +NOTE: For the uplink, the signal $s(t)$ and the baseband signals part thereof should be filtered per UE-implementation, as required, to meet the minimum requirements as specified in [38.101-1] and [38.101-2] for the respective frequency range. + +# 6 Uplink + +## 6.1 Overview + +### 6.1.1 Overview of physical channels + +An uplink physical channel corresponds to a set of resource elements carrying information originating from higher layers. The following uplink physical channels are defined: + +- Physical Uplink Shared Channel, PUSCH +- Physical Uplink Control Channel, PUCCH +- Physical Random Access Channel, PRACH + +### 6.1.2 Overview of physical signals + +An uplink physical signal is used by the physical layer but does not carry information originating from higher layers. The following uplink physical signals are defined: + +- Demodulation reference signals, DM-RS +- Phase-tracking reference signals, PT-RS + +- Sounding reference signal, SRS + +## 6.2 Physical resources + +The frame structure and physical resources the UE shall use when transmitting in the uplink transmissions are defined in Clause 4. + +The following antenna ports are defined for the uplink: + +- Antenna ports starting with 0 for demodulation reference signals for PUSCH +- Antenna ports starting with 1000 for SRS, PUSCH +- Antenna ports starting with 2000 for PUCCH +- Antenna port 4000 for PRACH + +If PUSCH repetition Type B as described in clause 6.1 of [6, TS38.214] is applied to a physical channel, the UE transmission shall be such that the channel over which a symbol on the antenna port used for uplink transmission is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed if the two symbols correspond to the same actual repetition of a PUSCH transmission with repetition Type B. + +If intra-slot frequency hopping is not enabled for a physical channel and PUSCH repetition Type B is not applied to the physical channel, the UE transmission shall be such that the channel over which a symbol on the antenna port used for uplink transmission is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed if the two symbols correspond to the same slot. + +If intra-slot frequency hopping is enabled for a physical channel, the UE transmission shall be such that the channel over which a symbol on the antenna port used for uplink transmission is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed only if the two symbols correspond to the same frequency hop, regardless of whether the frequency hop distance is zero or not. + +If DM-RS bundling is applied to PUSCH and/or PUCCH repetitions and/or transport-block processing over multiple slots as described in clause 6.1.7 of [6, 38.214], the UE transmission shall be such that the channel over which a symbol on the antenna port used for uplink transmission is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed if the two symbols are transmitted within the same actual time-domain window. + +## 6.3 Physical channels + +### 6.3.1 Physical uplink shared channel + +#### 6.3.1.1 Scrambling + +Up to two codewords can be transmitted. In case of single-codeword transmission, . + +For each codeword, the block of bits $c_i$ , where $c_i$ is the number of bits in codeword transmitted on the physical channel, shall be scrambled prior to modulation, resulting in a block of scrambled bits according to the following pseudo code + +Set $i = 0$ + +while + +if // UCI placeholder bits + +else + +if // UCI placeholder bits + +else + +end if + +end if + +$i = i + 1$ + +end while + +where $x$ and $y$ are tags defined in [4, TS 38.212] and where the scrambling sequence is given by clause 5.2.1. The scrambling sequence generator shall be initialized with + +where + +- equals the higher-layer parameter *dataScramblingIdentityPUSCH* if configured and the RNTI equals the C-RNTI, MCS-C-RNTI, SP-CSI-RNTI or CS-RNTI, and the transmission is not scheduled using DCI format 0\_0 in a common search space; +- equals the higher-layer parameter *msgA-DataScramblingIndex* if configured and the PUSCH transmission is triggered by a Type-2 random access procedure as described in clause 8.1A of [5, TS 38.213]; +- otherwise +- is the index of the random-access preamble transmitted for msgA as described in clause 5.1.3A of [11, TS 38.321] + +and where $n_{\text{RNTI}}$ equals the RA-RNTI for msgA and otherwise corresponds to the RNTI associated with the PUSCH transmission as described in clause 6.1 of [6, TS 38.214] and clause 8.3 of [5, TS 38.213]. + +### 6.3.1.2 Modulation + +For each codeword, the block of scrambled bits shall be modulated as described in clause 5.1 using one of the modulation schemes in Table 6.3.1.2-1, resulting in a block of complex-valued modulation symbols. + +**Table 6.3.1.2-1: Supported modulation schemes.** + +| Transform precoding disabled | | Transform precoding enabled | | +|------------------------------|------------------------|-----------------------------|------------------------| +| Modulation scheme | Modulation order $Q_m$ | Modulation scheme | Modulation order $Q_m$ | +| | | $\pi/2$ -BPSK | 1 | +| QPSK | 2 | QPSK | 2 | +| 16QAM | 4 | 16QAM | 4 | +| 64QAM | 6 | 64QAM | 6 | +| 256QAM | 8 | 256QAM | 8 | + +### 6.3.1.3 Layer mapping + +The complex-valued modulation symbols for each of the codewords to be transmitted shall be mapped onto up to four layers according to Table 7.3.1.3-1. Complex-valued modulation symbols for codeword shall be mapped onto the layers, where is the number of layers and is the number of modulation symbols per layer. + +### 6.3.1.4 Transform precoding + +If transform precoding is not enabled according to 6.1.3 of [6, TS38.214], for each layer. + +If transform precoding is enabled according to 6.1.3 of [6, TS38.214], and $\tilde{x}^{(0)}(i)$ depends on the configuration of phase-tracking reference signals. + +If the procedure in [6, TS 38.214] indicates that phase-tracking reference signals are not being used, the block of complex-valued symbols for the single layer shall be divided into sets, each corresponding to one OFDM symbol and $\tilde{x}^{(0)}(i) = x^{(0)}(i)$ . + +If the procedure in [6, TS 38.214] indicates that phase-tracking reference signals are being used, the block of complex-valued symbols shall be divided into sets, each set corresponding to one OFDM symbol, and where set $l$ contains $M_{sc}^{PUSCH} - \varepsilon_l N_{samp}^{group} N_{group}^{PTRS}$ symbols and is mapped to the complex-valued symbols corresponding to OFDM symbol $l$ prior to transform precoding, with $i' \neq m$ . The index of PT-RS samples in set $l$ , the number of samples per PT-RS group, and the number of PT-RS groups are defined in clause 6.4.1.2.2.2. The quantity $\varepsilon_l = 1$ when OFDM symbol $l$ contains one or more PT-RS samples, otherwise $\varepsilon_l = 0$ . + +Transform precoding shall be applied according to + +$$y^{(0)}(l \cdot M_{sc}^{PUSCH} + k) = \frac{1}{\sqrt{M_{sc}^{PUSCH}}} \sum_{i=0}^{M_{sc}^{PUSCH} - 1} \tilde{x}^{(0)}(l \cdot M_{sc}^{PUSCH} + i) e^{-j \frac{2\pi i k}{M_{sc}^{PUSCH}}}$$ + +$$k = 0, \dots, M_{sc}^{PUSCH} - 1$$ + +$$l = 0, \dots, M_{symb}^{layer} / M_{sc}^{PUSCH} - 1$$ + +resulting in a block of complex-valued symbols. The variable, where represents the bandwidth of the PUSCH in terms of resource blocks, and shall fulfil + +$$M_{RB}^{PUSCH} = 2^{a_2} \cdot 3^{a_3} \cdot 5^{a_5}$$ + +where is a set of non-negative integers. + +### 6.3.1.5 Precoding + +The block of vectors shall be precoded according to + +where . The set of antenna ports shall be determined according to the procedure in [6, TS 38.214]. + +For non-codebook-based transmission, the precoding matrix equals the identity matrix. + +For codebook-based transmission, the precoding matrix depends on the number of antenna ports used for the transmission: + +- for single-layer transmission on a single antenna port, ; +- for transmissions using 2, or 4 antenna ports, is given by Tables 6.3.1.5-1 to 6.3.1.5-7; +- for transmissions using 8 antenna ports, is given by + +where + +- the subscripts and denote the row of the respective matrix; +- is given by Table 6.3.1.5-8; +- the intermediate precoding matrix is given by Tables 6.3.1.5-9 to 6.3.1.5-24, 6.3.1.5-29 to 6.3.1.5-36, and 6.3.1.5-39 to 6.3.1.5-47 with representing the all-zero matrix with rows and columns; +- the submatrices are given by Tables 6.3.1.5-25 to 6.3.1.5-28 and 6.3.1.5-37 to 6.3.1.5-38. + +The TPMI index used in the tables above is obtained from the DCI scheduling the uplink transmission or the higher layer parameters according to the procedure in [6, TS 38.214]. + +When the higher-layer parameter *txConfig* is not configured, the precoding matrix . + +**Table 6.3.1.5-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 | | | $\frac{1}{\sqrt{2}} \begin{bmatrix} 1 \\ 1 \end{bmatrix}$ | $\frac{1}{\sqrt{2}} \begin{bmatrix} 1 \\ -1 \end{bmatrix}$ | $\frac{1}{\sqrt{2}} \begin{bmatrix} 1 \\ j \end{bmatrix}$ | $\frac{1}{\sqrt{2}} \begin{bmatrix} 1 \\ -j \end{bmatrix}$ | - | - | + +**Table 6.3.1.5-2: Precoding matrix for single-layer transmission using four antenna ports with transform precoding enabled.** + +| TPMI index | (ordered from left to right in increasing order of TPMI index) | | | | | | | | +|------------|----------------------------------------------------------------|--|--|--|---|---|---|---| +| 0 – 7 | | | | | | | | | +| 8 – 15 | | | | | | | | | +| 16 – 23 | | | | | | | | | +| 24 – 27 | | | | | - | - | - | - | + +**Table 6.3.1.5-3: Precoding matrix for single-layer transmission using four antenna ports with transform precoding disabled.** + +| TPMI index | (ordered from left to right in increasing order of TPMI index) | | | | | | | | +|------------|----------------------------------------------------------------|--|--|--|---|---|---|---| +| 0 – 7 | | | | | | | | | +| 8 – 15 | | | | | | | | | +| 16 – 23 | | | | | | | | | +| 24 – 27 | | | | | - | - | - | - | + +**Table 6.3.1.5-4: Precoding matrix for two-layer transmission using two antenna ports with transform precoding disabled.** + +| TPMI index | (ordered from left to right in increasing order of TPMI index) | | | | +|------------|----------------------------------------------------------------|--|--|---| +| 0 – 2 | | | | - | + +**Table 6.3.1.5-5: Precoding matrix for two-layer transmission using four antenna ports with transform precoding disabled.** + +| TPMI index | (ordered from left to right in increasing order of TPMI index) | | | | +|------------|----------------------------------------------------------------|--|---|---| +| 0 – 3 | | | | | +| 4 – 7 | | | | | +| 8 – 11 | | | | | +| 12 – 15 | | | | | +| 16 – 19 | | | | | +| 20 – 21 | | | - | - | + +**Table 6.3.1.5-6: Precoding matrix for three-layer transmission using four antenna ports with transform precoding disabled.** + +| TPMI index | (ordered from left to right in increasing order of TPMI index) | | | | +|------------|----------------------------------------------------------------|--|--|---| +| 0 – 3 | | | | | +| 4 – 6 | | | | - | + +**Table 6.3.1.5-7: Precoding matrix for four-layer transmission using four antenna ports with transform precoding disabled.** + +| TPMI index | (ordered from left to right in increasing order of TPMI index) | | | | +|------------|----------------------------------------------------------------|---|---|---| +| 0 – 3 | | | | | +| 4 | | - | - | - | + +**Table 6.3.1.5-8: The port mapping function for transmission using 8 antenna ports.** + +| | Higher-layer parameter CodebookType | | | | | | | | +|---|--------------------------------------------|---|--------------------|---|--------------------|---|--------------------|---| +| | codebook1 | | codebook2 | | codebook3 | | codebook4 | | +| | antenna port group | | antenna port group | | antenna port group | | antenna port group | | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | | 1 | | 1 | | 4 | 1 | 1 | +| 2 | | 2 | | 4 | 1 | 1 | 2 | 2 | +| 3 | | 3 | | 5 | | 5 | 3 | 3 | +| 4 | | 4 | 1 | 2 | 2 | 2 | 4 | 4 | +| 5 | | 5 | | 3 | | 6 | 5 | 5 | +| 6 | | 6 | | 6 | 3 | 3 | 6 | 6 | +| 7 | | 7 | | 7 | | 7 | 7 | 7 | + +**Table 6.3.1.5-9: Intermediate precoding matrix for *codebook1=ng1n4n1* and single-layer transmission using eight antenna ports.** + +| TPMI index | Intermediate precoder matrix (ordered from left to right in increasing order of TPMI index) | | | | | | | | +|------------|---------------------------------------------------------------------------------------------|--|--|--|--|--|--|--| +| 0 – 7 | | | | | | | | | +| 8 – 15 | | | | | | | | | + +**Table 6.3.1.5-10: Intermediate precoding matrix for *codebook1=ng1n4n1* and two-layer transmission using eight antenna ports with transform precoding disabled.** + +| TPMI index | Intermediate precoder matrix (ordered from left to right in increasing order of TPMI index) | | | | | | | | +|------------|---------------------------------------------------------------------------------------------|--|--|--|--|--|--|--| +| 0 – 7 | | | | | | | | | +| 8 – 15 | | | | | | | | | +| 16 – 23 | | | | | | | | | +| 24 – 31 | | | | | | | | | + +**Table 6.3.1.5-11: Intermediate precoding matrix for *codebook1=ng1n4n1* and three-layer transmission using eight antenna ports with transform precoding disabled.** + +| TPMI index | Intermediate precoder matrix (ordered from left to right in increasing order of TPMI index) | | | | +|------------|---------------------------------------------------------------------------------------------|--|--|--| +| 0 – 3 | | | | | +| 4 – 7 | | | | | +| 8 – 11 | | | | | +| 12 – 15 | | | | | +| 16 – 19 | | | | | +| 20 – 23 | | | | | + +**Table 6.3.1.5-12: Intermediate precoding matrix for *codebook1=ng1n4n1* and four-layer transmission using eight antenna ports with transform precoding disabled.** + +| TPMI index | Intermediate precoder matrix (ordered from left to right in increasing order of TPMI index) | | | | +|------------|---------------------------------------------------------------------------------------------|--|--|--| +| 0 – 3 | | | | | +| 4 – 7 | | | | | +| 8 – 11 | | | | | +| 12 – 15 | | | | | +| 16 – 19 | | | | | +| 20 – 23 | | | | | + +**Table 6.3.1.5-13: Intermediate precoding matrix for *codebook1=ng1n4n1* and five-layer transmission using eight antenna ports with transform precoding disabled.** + +| TPMI index | Intermediate precoder matrix (ordered from left to right in increasing order of TPMI index) | | +|------------|---------------------------------------------------------------------------------------------|--| +| 0 – 1 | | | +| 2 – 3 | | | +| 4 – 5 | | | +| 6 – 7 | | | + +**Table 6.3.1.5-14: Intermediate precoding matrix for *codebook1=ng1n4n1* and six-layer transmission using eight antenna ports with transform precoding disabled.** + +| TPMI index | Intermediate precoder matrix (ordered from left to right in increasing order of TPMI index) | | +|------------|---------------------------------------------------------------------------------------------|--| +| 0 – 1 | | | +| 2 – 3 | | | +| 4 – 5 | | | +| 6 – 7 | | | + +**Table 6.3.1.5-15: Intermediate precoding matrix for *codebook1=ng1n4n1* and seven-layer transmission using eight antenna ports with transform precoding disabled.** + +| TPMI index | Intermediate precoder matrix (ordered from left to right in increasing order of TPMI index) | | +|------------|---------------------------------------------------------------------------------------------|--| +| 0 – 1 | | | +| 2 – 3 | | | + +**Table 6.3.1.5-16: Intermediate precoding matrix for *codebook1=ng1n4n1* and eight-layer transmission using eight antenna ports with transform precoding disabled.** + +| TPMI index | Intermediate precoder matrix (ordered from left to right in increasing order of TPMI index) | | +|------------|---------------------------------------------------------------------------------------------|--| +| 0 – 1 | | | +| 2 – 3 | | | + +**Table 6.3.1.5-17: Intermediate precoding matrix for *codebook1=ng1n2n2* and single-layer transmission using eight antenna ports.** + +| TPMI index | Intermediate precoder matrix (ordered from left to right in increasing order of TPMI index) | | | | | | | | +|------------|---------------------------------------------------------------------------------------------|--|--|--|--|--|--|--| +| 0 – 7 | | | | | | | | | +| 8 – 15 | | | | | | | | | + +**Table 6.3.1.5-18: Intermediate precoding matrix for *codebook1=ng1n2n2* and two-layer transmission using eight antenna ports with transform precoding disabled.** + +| TPMI index | Intermediate precoder matrix (ordered from left to right in increasing order of TPMI index) | | | | | | | | +|------------|---------------------------------------------------------------------------------------------|--|--|--|--|--|--|--| +| 0 – 7 | | | | | | | | | +| 8 – 15 | | | | | | | | | +| 16 – 23 | | | | | | | | | +| 24 – 31 | | | | | | | | | + +**Table 6.3.1.5-19: Intermediate precoding matrix for *codebook1=ng1n2n2* and three-layer transmission using eight antenna ports with transform precoding disabled.** + +| TPMI index | Intermediate precoder matrix (ordered from left to right in increasing order of TPMI index) | | | | +|------------|---------------------------------------------------------------------------------------------|--|--|--| +| 0 – 3 | | | | | +| 4 – 7 | | | | | +| 8 – 11 | | | | | +| 12 – 15 | | | | | +| 16 – 19 | | | | | +| 20 – 23 | | | | | + +**Table 6.3.1.5-20: Intermediate precoding matrix for *codebook1=ng1n2n2* and four-layer transmission using eight antenna ports with transform precoding disabled.** + +| TPMI index | Intermediate precoder matrix (ordered from left to right in increasing order of TPMI index) | | | | +|------------|---------------------------------------------------------------------------------------------|--|--|--| +| 0 – 3 | | | | | +| 4 – 7 | | | | | +| 8 – 11 | | | | | +| 12 – 15 | | | | | +| 16 – 19 | | | | | +| 20 – 23 | | | | | + +**Table 6.3.1.5-21: Intermediate precoding matrix for *codebook1=ng1n2n2* and five-layer transmission using eight antenna ports with transform precoding disabled.** + +| TPMI index | Intermediate precoder matrix (ordered from left to right in increasing order of TPMI index) | | +|------------|---------------------------------------------------------------------------------------------|--| +| 0 – 1 | | | +| 2 – 3 | | | +| 4 – 5 | | | +| 6 – 7 | | | + +**Table 6.3.1.5-22: Intermediate precoding matrix for *codebook1=ng1n2n2* and six-layer transmission using eight antenna ports with transform precoding disabled.** + +| TPMI index | Intermediate precoder matrix (ordered from left to right in increasing order of TPMI index) | | +|------------|---------------------------------------------------------------------------------------------|--| +| 0 – 1 | | | +| 2 – 3 | | | +| 4 – 5 | | | +| 6 – 7 | | | + +**Table 6.3.1.5-23: Intermediate precoding matrix for *codebook1=ng1n2n2* and seven-layer transmission using eight antenna ports with transform precoding disabled.** + +| TPMI index | Intermediate precoder matrix (ordered from left to right in increasing order of TPMI index) | | +|------------|---------------------------------------------------------------------------------------------|--| +| 0 – 1 | | | +| 2 – 3 | | | +| 4 – 5 | | | +| 6 – 7 | | | + +**Table 6.3.1.5-24: Intermediate precoding matrix for *codebook1=ng1n2n2* and eight-layer transmission using eight antenna ports with transform precoding disabled.** + +| TPMI index | Intermediate precoder matrix (ordered from left to right in increasing order of TPMI index) | | +|------------|---------------------------------------------------------------------------------------------|--| +| 0 – 1 | | | +| 2 – 3 | | | +| 4 – 5 | | | +| 6 – 7 | | | + +**Table 6.3.1.5-25: Submatrices for *codebook2* and used in Tables 6.3.1.5-29 to 6.3.1.5-31.** + +| | (ordered from left to right in increasing order of ) | | | | | | | | +|--------|------------------------------------------------------|--|--|--|--|--|--|--| +| 0 – 7 | | | | | | | | | +| 8 – 15 | | | | | | | | | + +**Table 6.3.1.5-26: Submatrices for *codebook2* and used in Tables 6.3.1.5-30 to 6.3.1.5-33.** + +| | (ordered from left to right in increasing order of ) | | | | +|-------|------------------------------------------------------|--|--|--| +| 0 – 3 | | | | | +| 4 – 7 | | | | | + +**Table 6.3.1.5-27: Submatrices for *codebook2* and used in Tables 6.3.1.5-31, 6.3.1.5-33, 6.3.1.5-34, and 6.3.1.5-35.** + +| | (ordered from left to right in increasing order of ) | | | | +|-------|------------------------------------------------------|--|--|--| +| 0 – 3 | | | | | + +**Table 6.3.1.5-28: Submatrices for *codebook2* and used in Tables 6.3.1.5-32, 6.3.1.5-35, and 6.3.1.5-36.** + +| | (ordered from left to right in increasing order of ) | | +|-------|------------------------------------------------------|--| +| 0 – 1 | | | + +**Table 6.3.1.5-29: Intermediate precoding matrix for *codebook2* and single-layer transmission using eight antenna ports.** + +| TPMI index | Intermediate precoder matrix | +|------------|------------------------------| +| 0 – 15 | | +| 16 – 31 | | +| 32 | | + +**Table 6.3.1.5-30: Intermediate precoding matrix for *codebook2* and two-layer transmission using eight antenna ports with transform precoding disabled.** + +| TPMI index | Intermediate precoder matrix | +|------------|------------------------------| +| 0 – 7 | | +| 8 – 15 | | +| 16 – 271 | | + +**Table 6.3.1.5-31: Intermediate precoding matrix for *codebook2* and three-layer transmission using eight antenna ports with transform precoding disabled.** + +| TPMI index | Intermediate precoder matrix | +|------------|------------------------------| +| 0 – 3 | | +| 4 – 7 | | +| 8 – 135 | | +| 136 – 263 | | + +**Table 6.3.1.5-32: Intermediate precoding matrix for *codebook2* and four-layer transmission using eight antenna ports with transform precoding disabled.** + +| TPMI index | Intermediate precoder matrix | +|------------|------------------------------| +| 0 – 1 | | +| 2 – 3 | | +| 4 – 67 | | + +**Table 6.3.1.5-33: Intermediate precoding matrix for *codebook2* and five-layer transmission using eight antenna ports with transform precoding disabled.** + +| TPMI index | Intermediate precoder matrix | +|------------|------------------------------| +| 0 – 31 | | + +**Table 6.3.1.5-34: Intermediate precoding matrix for *codebook2* and six-layer transmission using eight antenna ports with transform precoding disabled.** + +| TPMI index | Intermediate precoder matrix | +|------------|------------------------------| +| 0 – 15 | | + +**Table 6.3.1.5-35: Intermediate precoding matrix for *codebook2* and seven-layer transmission using eight antenna ports with transform precoding disabled.** + +| TPMI index | Intermediate precoder matrix | +|------------|------------------------------| +| 0 – 7 | | + +**Table 6.3.1.5-36: Intermediate precoding matrix for *codebook2* and eight-layer transmission using eight antenna ports with transform precoding disabled.** + +| TPMI index | Intermediate precoder matrix | +|------------|------------------------------| +| 0 – 3 | | + +**Table 6.3.1.5-37: Submatrices for *codebook3* and used in Tables 6.3.1.5-39 to 6.3.1.5-45.** + +| | (ordered from left to right in increasing order of ) | | | | +|-------|------------------------------------------------------|--|--|--| +| 0 – 3 | | | | | + +**Table 6.3.1.5-38: Submatrices for *codebook3* and used in Tables 6.3.1.5-40 to 6.3.1.5-46.** + +| | (ordered from left to right in increasing order of ) | | +|-------|------------------------------------------------------|--| +| 0 – 1 | | | + +**Table 6.3.1.5-39: Intermediate precoding matrix for *codebook3* and single-layer transmission using eight antenna ports.** + +| TPMI index | Intermediate precoder matrix | +|------------|------------------------------| +| 0 – 3 | | +| 4 – 7 | | +| 8 – 11 | | +| 12 – 15 | | +| 16 | | + +**Table 6.3.1.5-40: Intermediate precoding matrix for *codebook3* and two-layer transmission using eight antenna ports with transform precoding disabled.** + +| TPMI index | Intermediate precoder matrix | +|------------|------------------------------| +| 0 – 1 | | +| 2 – 3 | | +| 4 – 5 | | +| 6 – 7 | | +| 8 – 23 | | +| 24 – 39 | | +| 40 – 55 | | +| 56 – 71 | | +| 72 – 87 | | +| 88 – 103 | | +| 104 | | + +**Table 6.3.1.5-41: Intermediate precoding matrix for *codebook3* and three-layer transmission using eight antenna ports with transform precoding disabled.** + +| TPMI index | Intermediate precoder matrix | +|------------|------------------------------| +| 0 – 7 | | +| 8 – 15 | | +| 16 – 23 | | +| 24 – 31 | | +| 32 – 39 | | +| 40 – 47 | | +| 48 – 111 | | +| 112 – 175 | | +| 176 – 239 | | +| 240 – 303 | | +| 304 | | + +**Table 6.3.1.5-42: Intermediate precoding matrix for *codebook3* and four-layer transmission using eight antenna ports with transform precoding disabled.** + +| TPMI index | Intermediate precoder matrix | +|------------|------------------------------| +| 0 – 255 | | +| 256 – 259 | | +| 260 – 263 | | +| 264 – 267 | | +| 268 – 271 | | +| 272 – 275 | | +| 276 – 279 | | + +**Table 6.3.1.5-43: Intermediate precoding matrix for *codebook3* and five-layer transmission using eight antenna ports with transform precoding disabled.** + +| TPMI index | Intermediate precoder matrix | +|------------|------------------------------| +| 0 – 15 | | +| 16 – 31 | | +| 32 – 159 | | + +**Table 6.3.1.5-44: Intermediate precoding matrix for *codebook3* and six-layer transmission using eight antenna ports with transform precoding disabled.** + +| TPMI index | Intermediate precoder matrix | +|------------|------------------------------| +| 0 – 7 | | +| 8 – 15 | | +| 16 – 79 | | + +**Table 6.3.1.5-45: Intermediate precoding matrix for *codebook3* and seven-layer transmission using eight antenna ports with transform precoding disabled.** + +| TPMI index | Intermediate precoder matrix | +|------------|------------------------------| +| 0 – 31 | | + +**Table 6.3.1.5-46: Intermediate precoding matrix for *codebook3* and eight-layer transmission using eight antenna ports with transform precoding disabled.** + +| TPMI index | Intermediate precoder matrix | +|------------|------------------------------| +| 0 – 15 | | + +**Table 6.3.1.5-47: Intermediate precoding matrix for *codebook4* and transmission using eight antenna ports. Up to 8 layers are supported with transform precoding disabled and up to one layer with transform precoding enabled.** + +| TPMI index | Intermediate precoder matrix | +|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 – |

where column i, denoted \mathbf{e}_i, has an element 1 on the row corresponding to the port on which layer i is to be transmitted, and element 0 in all other rows, i = 0, 1, \dots, L-1, where L is the number of layers to be transmitted on port i and otherwise, and for i \geq L, where L is defined by Table 5.2.2.2.5-4 of [6, TS 38.214].

TPMI indices 0, 1, \dots, 255 are mapped to values of L, first by increasing values of the number of transmitted layers, and then by increasing values of i for a given number of layers.

| +| 255 | | +| 256 | | +| 257 | | +| 258 | | + +### 6.3.1.6 Mapping to virtual resource blocks + +For each of the antenna ports used for transmission of the PUSCH, the block of complex-valued symbols shall be multiplied with the amplitude scaling factor in order to conform to the transmit power specified in [5, TS 38.213] and mapped in sequence starting with $n$ to resource elements in the virtual resource blocks assigned for transmission which meet all of the following criteria: + +- they are in the virtual resource blocks assigned for transmission, and +- the corresponding resource elements in the corresponding physical resource blocks are not used for transmission of the associated DM-RS, PT-RS, or DM-RS intended for other co-scheduled UEs as described in clause 6.4.1.1.3 + +The mapping to resource elements allocated for PUSCH according to [6, TS 38.214] shall be in increasing order of first the index $n$ over the assigned virtual resource blocks, where $n$ is the first subcarrier in the lowest-numbered virtual resource block assigned for transmission, and then the index $n$ , with the starting position given by [6, TS 38.214]. + +### 6.3.1.7 Mapping from virtual to physical resource blocks + +Virtual resource blocks shall be mapped to physical resource blocks according to non-interleaved mapping. + +For non-interleaved VRB-to-PRB mapping for uplink resource allocation types 0 and 1 [6, TS 38.214], virtual resource block $n$ is mapped to physical resource block $n$ except for PUSCH scheduled by RAR UL grant or PUSCH scheduled by + +DCI format 0\_0 with CRC scrambled by TC-RNTI in active uplink bandwidth part starting at $n_{\text{start}}$ , including all resource blocks of the initial uplink bandwidth part starting at $n_{\text{start}}$ , and having the same subcarrier spacing and cyclic prefix as the initial uplink bandwidth part, in which case virtual resource block $n_{\text{VRB}}$ is mapped to physical resource block $n_{\text{PRB}}$ . + +For non-interleaved VRB-to-PRB mapping for uplink resource allocation type 2 [6, TS 38.214], virtual resource block $n_{\text{VRB}}$ is mapped to physical resource block $n_{\text{PRB}}$ . + +## 6.3.2 Physical uplink control channel + +### 6.3.2.1 General + +The physical uplink control channel supports multiple formats as shown in Table 6.3.2.1-1. In case intra-slot frequency hopping is configured for PUCCH formats 1, 3, or 4 according to clause 9.2.1 of [5, TS38.213], the number of symbols in the first hop is given by $n_{\text{symbols}}$ where $n_{\text{symbols}}$ is the length of the PUCCH transmission in OFDM symbols. + +**Table 6.3.2.1-1: PUCCH formats.** + +| PUCCH format | Length in OFDM symbols | Number of bits | +|--------------|------------------------|----------------| +| 0 | 1 – 2 | $\leq 2$ | +| 1 | 4 – 14 | $\leq 2$ | +| 2 | 1 – 2 | $> 2$ | +| 3 | 4 – 14 | $> 2$ | +| 4 | 4 – 14 | $> 2$ | + +### 6.3.2.2 Sequence and cyclic shift hopping + +PUCCH formats 0, 1, 3, and 4 use sequences given by clause 5.2.2 with $n_{\text{group}}$ where the sequence group $n_{\text{group}}$ and the sequence number $n_{\text{seq}}$ depend on the sequence hopping in clause 6.3.2.2.1 and the cyclic shift $\alpha$ depends on the cyclic shift hopping in clause 6.3.2.2.2. + +#### 6.3.2.2.1 Group and sequence hopping + +The sequence group $n_{\text{group}}$ and the sequence number $n_{\text{seq}}$ within the group depends on the higher-layer parameter *pucch-GroupHopping*: + +- if *pucch-GroupHopping* equals 'neither' + +where $n_{\text{ID}}$ is given by the higher-layer parameter *hoppingId* if configured, otherwise . + +- if *pucch-GroupHopping* equals 'enable' + +$$f_{\text{gh}} = \left( \sum_{m=0}^7 2^m c(8(2n_{\text{s,f}}^{\mu} + n_{\text{hop}}) + m) \right) \bmod 30$$ + +$$f_{\text{ss}} = n_{\text{ID}} \bmod 30$$ + +$$v = 0$$ + +where the pseudo-random sequence $c(n)$ is defined by clause 5.2.1 and shall be initialized at the beginning of each radio frame with $n_{\text{ID}}$ where $n_{\text{ID}}$ is given by the higher-layer parameter *hoppingId* if configured, otherwise . + +- if *pucch-GroupHopping* equals 'disable' + +$$f_{\text{gh}} = 0$$ + +$$f_{\text{ss}} = n_{\text{ID}} \bmod 30$$ + +$$v = c(2n_{\text{s,f}}^{\mu} + n_{\text{hop}})$$ + +where the pseudo-random sequence $c(n)$ is defined by clause 5.2.1 and shall be initialized at the beginning of each radio frame with $n_{\text{ID}}$ where $n_{\text{ID}}$ is given by the higher-layer parameter *hoppingId* if configured, otherwise . + +The frequency hopping index if intra-slot frequency hopping is disabled by the higher-layer parameter *intraSlotFrequencyHopping*. If frequency hopping is enabled by the higher-layer parameter *intraSlotFrequencyHopping*, $n_{\text{hop}} = 0$ for the first hop and $n_{\text{hop}} = 1$ for the second hop. + +#### 6.3.2.2.2 Cyclic shift hopping + +The cyclic shift varies as a function of the symbol and slot number according to + +where + +- is the slot number in the radio frame +- is the OFDM symbol number in the PUCCH transmission where corresponds to the first OFDM symbol of the PUCCH transmission, +- is the index of the OFDM symbol in the slot that corresponds to the first OFDM symbol of the PUCCH transmission in the slot given by [5, TS 38.213] +- is given by [5, TS 38.213] for PUCCH format 0 and 1 while for PUCCH format 3 and 4 is defined in clause 6.4.1.3.3.1 +- except for PUCCH format 0 when it depends on the information to be transmitted according to clause 9.2 of [5, TS 38.213]. +- is given by + - for PUCCH formats 0 and 1 if PUCCH shall use interlaced mapping according to any of the higher-layer parameters *useInterlacePUCCH-PUSCH* in *BWP-UplinkCommon* or *useInterlacePUCCH-PUSCH* in *BWP-UplinkDedicated*, where is the resource block number within the interlace; + - otherwise + +The function is given by + +where the pseudo-random sequence is defined by clause 5.2.1. The pseudo-random sequence generator shall be initialized with , where is given by the higher-layer parameter *hoppingId* if configured, otherwise . + +#### 6.3.2.3 PUCCH format 0 + +##### 6.3.2.3.1 Sequence generation + +The sequence shall be generated according to + +where is given by clause 6.3.2.2 with depending on the information to be transmitted according to clause 9.2 of [5, TS 38.213]. The quantity is given by clause 9.2.1 of [5, TS 38.213]. + +##### 6.3.2.3.2 Mapping to physical resources + +The sequence shall be multiplied with the amplitude scaling factor in order to conform to the transmit power specified in [5, TS 38.213] and mapped in sequence starting with to resource elements assigned for transmission according to clause 9.2.1 of [5, TS 38.213] in increasing order of first the index over the assigned physical resources spanning resource blocks, and then the index on antenna port . + +For interlaced transmission, the mapping operation shall be repeated for each resource block in the interlace and in the active bandwidth part over the assigned physical resource blocks according to clause 9.2.1 of [5, TS 38.213], with the resource-block dependent sequence generated according to clause 6.3.2.2. + +### 6.3.2.4 PUCCH format 1 + +#### 6.3.2.4.1 Sequence modulation + +The block of bits shall be modulated as described in clause 5.1 using BPSK if $b(0)$ and QPSK if $b(0) \neq 0$ , resulting in a complex-valued symbol $\tilde{s}(m)$ . + +The complex-valued symbol $\tilde{s}(m)$ shall be multiplied with a sequence according to + +where $w_i(m)$ is given by clause 6.3.2.2. The quantity $N_{SF,m}$ is given by clause 9.2.1 of [5, TS 38.213]. + +The block of complex-valued symbols shall be block-wise spread with the orthogonal sequence according to + +where $\tilde{s}(m)$ is given by Table 6.3.2.4.1-1. Intra-slot frequency hopping shall be assumed when the higher-layer parameter *intraSlotFrequencyHopping* is provided, regardless of whether the frequency-hop distance is zero or not, and interlaced mapping is not enabled, otherwise no intra-slot frequency hopping shall be assumed. + +The orthogonal sequence $w_i(m)$ is given by Table 6.3.2.4.1-2 where $i$ is the index of the orthogonal sequence to use according to clause 9.2.1 of [5, TS 38.213]. In case of a PUCCH transmission spanning multiple slots according to clause 9.2.6 of [5, TS38.213], the complex-valued symbol $\tilde{s}(m)$ is repeated for the subsequent slots. + +**Table 6.3.2.4.1-1: Number of PUCCH symbols and the corresponding $N_{SF,m}$ .** + +| PUCCH length, | No intra-slot hopping | | Intra-slot hopping | | +|---------------|-----------------------|------------|--------------------|------------| +| | $N_{SF,m}$ | $N_{SF,m}$ | $N_{SF,m}$ | $N_{SF,m}$ | +| 4 | 2 | 2 | 1 | 1 | +| 5 | 2 | 2 | 1 | 1 | +| 6 | 3 | 3 | 1 | 2 | +| 7 | 3 | 3 | 1 | 2 | +| 8 | 4 | 4 | 2 | 2 | +| 9 | 4 | 4 | 2 | 2 | +| 10 | 5 | 5 | 2 | 3 | +| 11 | 5 | 5 | 2 | 3 | +| 12 | 6 | 6 | 3 | 3 | +| 13 | 6 | 6 | 3 | 3 | +| 14 | 7 | 7 | 3 | 4 | + +**Table 6.3.2.4.1-2: Orthogonal sequences $w_i(m) = e^{j2\pi\phi(m)/N_{SF,m}}$ for PUCCH format 1.** + +| $i$ | $w_i(0)$ | $w_i(1)$ | $w_i(2)$ | $w_i(3)$ | $w_i(4)$ | $w_i(5)$ | $w_i(6)$ | +|-----|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| 1 | [0] | - | - | - | - | - | - | +| 2 | [0 0] | [0 1] | - | - | - | - | - | +| 3 | [0 0 0] | [0 1 2] | [0 2 1] | - | - | - | - | +| 4 | [0 0 0 0] | [0 2 0 2] | [0 0 2 2] | [0 2 2 0] | - | - | - | +| 5 | [0 0 0 0 0] | [0 1 2 3 4] | [0 2 4 1 3] | [0 3 1 4 2] | [0 4 3 2 1] | - | - | +| 6 | [0 0 0 0 0 0] | [0 1 2 3 4 5] | [0 2 4 0 2 4] | [0 3 0 3 0 3] | [0 4 2 0 4 2] | [0 5 4 3 2 1] | - | +| 7 | [0 0 0 0 0 0 0] | [0 1 2 3 4 5 6] | [0 2 4 6 1 3 5] | [0 3 6 2 5 1 4] | [0 4 1 5 2 6 3] | [0 5 3 1 6 4 2] | [0 6 5 4 3 2 1] | + +#### 6.3.2.4.2 Mapping to physical resources + +The sequence shall be multiplied with the amplitude scaling factor in order to conform to the transmit power specified in [5, TS 38.213] and mapped in sequence starting with $m$ to resource elements which meet all of the following criteria: + +- they are in the resource blocks assigned for transmission, +- they are not used by the associated DM-RS + +The mapping to resource elements not reserved for other purposes shall be in increasing order of first the index over the assigned physical resource blocks according to clause 9.2.1 of [5, TS 38.213], and then the index on antenna port. + +For interlaced transmission, the mapping operation shall be repeated for each resource block in the interlace and in the active bandwidth part over the assigned physical resource blocks according to clause 9.2.1 of [5, TS 38.213], with the resource-block dependent sequence generated according to clause 6.3.2.2. + +### 6.3.2.5 PUCCH format 2 + +#### 6.3.2.5.1 Scrambling + +The block of bits $y$ , where $y$ is the number of bits transmitted on the physical channel, shall be scrambled prior to modulation, resulting in a block of scrambled bits according to the following pseudo code + +Set $i = 0$ + +while + +if // UCI placeholder bits + +else + +end if + +$i = i + 1$ + +end while + +where $y$ is the tag defined in [4, TS38.212] and the scrambling sequence is given by clause 5.2.1. The scrambling sequence generator shall be initialized with + +where + +- $c_{init}$ equals the higher-layer parameter *dataScramblingIdentityPUSCH* if configured, +- otherwise + +and $c_{init}$ is given by the C-RNTI. + +#### 6.3.2.5.2 Modulation + +The block of scrambled bits shall be modulated as described in clause 5.1 using QPSK, resulting in a block of complex-valued modulation symbols where $n$ . + +##### 6.3.2.5.2A Spreading + +Spreading shall be applied according to + +resulting in a block of complex-valued symbols $\tilde{y}(n)$ . + +If the higher layer parameter *interlace1* is not configured, and the higher-layer parameter *occ-Length* is configured, + +- $c_{init}$ is given by the higher-layer parameter *occ-Length*; +- $n$ is given by Tables 6.3.2.5A-1 and 6.3.2.5A-2 where $n$ , the quantity $n$ is the index of the orthogonal sequence to use given by the higher-layer parameter *occ-Index*, and $n$ is the interlaced resource block number as defined in clause 4.4.4.6 within the interlace given by the higher-layer parameter *Interlace0*. + +otherwise and + +**Table 6.3.2.5A-1: Orthogonal sequences for PUCCH format 2 when .** + +| | | +|---|--| +| | | +| 0 | | +| 1 | | + +**Table 6.3.2.5A-2: Orthogonal sequences for PUCCH format 2 when .** + +| | | +|---|--| +| | | +| 0 | | +| 1 | | +| 2 | | +| 3 | | + +**6.3.2.5.3 Mapping to physical resources** + +The block of complex-valued symbols shall be multiplied with the amplitude scaling factor in order to conform to the transmit power specified in [5, TS 38.213] and mapped in sequence starting with to resource elements which meet all of the following criteria: + +- they are in the resource blocks assigned for transmission, +- they are not used by the associated DM-RS. + +The mapping to resource elements not reserved for other purposes shall be in increasing order of first the index over the assigned physical resource blocks according to clause 9.2.1 of [5, TS 38.213], and then the index on antenna port . + +**6.3.2.6 PUCCH formats 3 and 4** + +**6.3.2.6.1 Scrambling** + +The block of bits , where is the number of bits transmitted on the physical channel, shall be scrambled prior to modulation, resulting in a block of scrambled bits according to the following pseudo code + +Set $i = 0$ + +while + +if // UCI placeholder bits + +else + +end if + +$i = i + 1$ + +end while + +where $y$ is the tag defined in [4, TS38.212] and the scrambling sequence is given by clause 5.2.1. The scrambling sequence generator shall be initialized with + +where + +- equals the higher-layer parameter *dataScramblingIdentityPUSCH* if configured, +- otherwise + +and is given by the C-RNTI. + +### 6.3.2.6.2 Modulation + +The block of scrambled bits shall be modulated as described in clause 5.1 using QPSK unless $\pi/2$ -BPSK is configured, resulting in a block of complex-valued modulation symbols where for QPSK and for $\pi/2$ -BPSK. + +### 6.3.2.6.3 Block-wise spreading + +For both PUCCH format 3 and 4, with representing the bandwidth of the PUCCH in terms of resource blocks according to clauses 9.2.3, 9.2.5.1 and 9.2.5.2 of [5, TS 38.213] and shall for non-interlaced mapping fulfil + +where is a set of non-negative integers and . For interlaced mapping, if a single interlace is configured and if two interlaces are configured. + +For PUCCH format 3, if interlaced mapping is not configured, no block-wise spreading is applied and + +where is given by clauses 9.2.3, 9.2.5.1 and 9.2.5.2 of [5, TS 38.213] and . + +For PUCCH format 3 with interlaced mapping and PUCCH format 4, block-wise spreading shall be applied according to + +where + +- for PUCCH format 3 with interlaced mapping, if a single interlace is configured and , if two interlaces are configured; +- for PUCCH format 4, is given by the higher-layer parameter *occ-Length*; + +and is given by Tables 6.3.2.6.3-1 and 6.3.2.6.3-2 for where is the index of the orthogonal sequence to use according to clause 9.2.1 of [5, TS 38.213]. The quantity is given by the higher-layer parameter *occ-Length* if provided, otherwise . + +**Table 6.3.2.6.3-1: Orthogonal sequences for PUCCH format 3 with interlaced mapping and PUCCH format 4 when .** + +| | | +|---|--| +| | | +| 0 | | +| 1 | | + +**Table 6.3.2.6.3-2: Orthogonal sequences for PUCCH format 3 with interlaced mapping and PUCCH format 4 when .** + +| | | +|---|--| +| | | +| 0 | | +| 1 | | +| 2 | | +| 3 | | + +### 6.3.2.6.4 Transform precoding + +The block of complex-valued symbols shall be transform precoded according to + +resulting in a block of complex-valued symbols . + +### 6.3.2.6.5 Mapping to physical resources + +The block of modulation symbols shall be multiplied with the amplitude scaling factor in order to conform to the transmit power specified in [5, TS 38.213] and mapped in sequence starting with to resource elements which meet all of the following criteria: + +- they are in the resource blocks assigned for transmission, +- they are not used by the associated DM-RS + +The mapping to resource elements not reserved for other purposes shall be in increasing order of first the index over the assigned physical resource blocks according to clause 9.2.1 of [5, TS 38.213], and then the index on antenna port. + +In case of intra-slot frequency hopping according to clause 9.2.1 of [5, TS 38.213], OFDM symbols shall be transmitted in the first hop and symbols in the second hop where is the total number of OFDM symbols used in one slot for PUCCH transmission. + +## 6.3.3 Physical random-access channel + +### 6.3.3.1 Sequence generation + +The set of random-access preambles shall be generated according to + +from which the frequency-domain representation shall be generated according to + +where , , or depending on the PRACH preamble format as given by Tables 6.3.3.1-1 and 6.3.3.1-2. + +There are 64 preambles defined in each time-frequency PRACH occasion, enumerated in increasing order of first increasing cyclic shift of a logical root sequence, and then in increasing order of the logical root sequence index, starting with the index obtained from the higher-layer parameter *prach-RootSequenceIndex* or *rootSequenceIndex-BFR* or by *msgA-PRACH-RootSequenceIndex* if configured and a type-2 random-access procedure is initiated as described in clause 8.1 of [5, TS 38.213]. Additional preamble sequences, in case 64 preambles cannot be generated from a single root Zadoff-Chu sequence, are obtained from the root sequences with the consecutive logical indexes until all the 64 sequences are found. The logical root sequence order is cyclic; the logical index 0 is consecutive to . The sequence number is obtained from the logical root sequence index according to Tables 6.3.3.1-3 to 6.3.3.1-4B. + +The cyclic shift is given by + +where is given by Tables 6.3.3.1-5 to 6.3.3.1-7, the higher-layer parameter *msgA-RestrictedSetConfig*, if provided, determines the type of restricted sets (unrestricted, restricted type A, restricted type B); otherwise, the higher-layer parameter *restrictedSetConfig* determines the type of restricted sets (unrestricted, restricted type A, restricted type B), and Tables 6.3.3.1-1 and 6.3.3.1-2 indicate the type of restricted sets supported for the different preamble formats. + +The variable is given by + +where is the smallest non-negative integer that fulfils . The parameters for restricted sets of cyclic shifts depend on . + +For restricted set type A, the parameters are given by: + +- for +- for + +For restricted set type B, the parameters are given by: + +- for +- for +- for +- for +- for +- for + +For all other values of , there are no cyclic shifts in the restricted set. + +**Table 6.3.3.1-1: PRACH preamble formats for and kHz.** + +| Format | | | | | Support for restricted sets | +|--------|-----|----------|--|--|-----------------------------| +| 0 | 839 | 1.25 kHz | | | Type A, Type B | +| 1 | 839 | 1.25 kHz | | | Type A, Type B | +| 2 | 839 | 1.25 kHz | | | Type A, Type B | +| 3 | 839 | 5 kHz | | | Type A, Type B | + +**Table 6.3.3.1-2: Preamble formats for and kHz where .** + +| Format | | | | | | | Support for restricted sets | +|--------|-----|------|-----|--|--|--|-----------------------------| +| A1 | 139 | 1151 | 571 | | | | - | +| A2 | 139 | 1151 | 571 | | | | - | +| A3 | 139 | 1151 | 571 | | | | - | +| B1 | 139 | 1151 | 571 | | | | - | +| B2 | 139 | 1151 | 571 | | | | - | +| B3 | 139 | 1151 | 571 | | | | - | +| B4 | 139 | 1151 | 571 | | | | - | +| C0 | 139 | 1151 | 571 | | | | - | +| C2 | 139 | 1151 | 571 | | | | | + +**Table 6.3.3.1-3: Mapping from *logical index* to sequence number for preamble formats with .** + +| | Sequence number in increasing order of | | | | | | | | | | | | | | | | | | | | +|-----------|----------------------------------------|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----| +| | 0 – 19 | 129 | 710 | 140 | 699 | 120 | 719 | 210 | 629 | 168 | 671 | 84 | 755 | 105 | 734 | 93 | 746 | 70 | 769 | 60 | +| 20 – 39 | 2 | 837 | 1 | 838 | 56 | 783 | 112 | 727 | 148 | 691 | 80 | 759 | 42 | 797 | 40 | 799 | 35 | 804 | 73 | 766 | +| 40 – 59 | 146 | 693 | 31 | 808 | 28 | 811 | 30 | 809 | 27 | 812 | 29 | 810 | 24 | 815 | 48 | 791 | 68 | 771 | 74 | 765 | +| 60 – 79 | 178 | 661 | 136 | 703 | 86 | 753 | 78 | 761 | 43 | 796 | 39 | 800 | 20 | 819 | 21 | 818 | 95 | 744 | 202 | 637 | +| 80 – 99 | 190 | 649 | 181 | 658 | 137 | 702 | 125 | 714 | 151 | 688 | 217 | 622 | 128 | 711 | 142 | 697 | 122 | 717 | 203 | 636 | +| 100 – 119 | 118 | 721 | 110 | 729 | 89 | 750 | 103 | 736 | 61 | 778 | 55 | 784 | 15 | 824 | 14 | 825 | 12 | 827 | 23 | 816 | +| 120 – 139 | 34 | 805 | 37 | 802 | 46 | 793 | 207 | 632 | 179 | 660 | 145 | 694 | 130 | 709 | 223 | 616 | 228 | 611 | 227 | 612 | +| 140 – 159 | 132 | 707 | 133 | 706 | 143 | 696 | 135 | 704 | 161 | 678 | 201 | 638 | 173 | 666 | 106 | 733 | 83 | 756 | 91 | 748 | +| 160 – 179 | 66 | 773 | 53 | 786 | 10 | 829 | 9 | 830 | 7 | 832 | 8 | 831 | 16 | 823 | 47 | 792 | 64 | 775 | 57 | 782 | +| 180 – 199 | 104 | 735 | 101 | 738 | 108 | 731 | 208 | 631 | 184 | 655 | 197 | 642 | 191 | 648 | 121 | 718 | 141 | 698 | 149 | 690 | +| 200 – 219 | 216 | 623 | 218 | 621 | 152 | 687 | 144 | 695 | 134 | 705 | 138 | 701 | 199 | 640 | 162 | 677 | 176 | 663 | 119 | 720 | +| 220 – 239 | 158 | 681 | 164 | 675 | 174 | 665 | 171 | 668 | 170 | 669 | 87 | 752 | 169 | 670 | 88 | 751 | 107 | 732 | 81 | 758 | +| 240 – 259 | 82 | 757 | 100 | 739 | 98 | 741 | 71 | 768 | 59 | 780 | 65 | 774 | 50 | 789 | 49 | 790 | 26 | 813 | 17 | 822 | +| 260 – 279 | 13 | 826 | 6 | 833 | 5 | 834 | 33 | 806 | 51 | 788 | 75 | 764 | 99 | 740 | 96 | 743 | 97 | 742 | 166 | 673 | +| 280 – 299 | 172 | 667 | 175 | 664 | 187 | 652 | 163 | 676 | 185 | 654 | 200 | 639 | 114 | 725 | 189 | 650 | 115 | 724 | 194 | 645 | +| 300 – 319 | 195 | 644 | 192 | 647 | 182 | 657 | 157 | 682 | 156 | 683 | 211 | 628 | 154 | 685 | 123 | 716 | 139 | 700 | 212 | 627 | +| 320 – 339 | 153 | 686 | 213 | 626 | 215 | 624 | 150 | 689 | 225 | 614 | 224 | 615 | 221 | 618 | 220 | 619 | 127 | 712 | 147 | 692 | +| 340 – 359 | 124 | 715 | 193 | 646 | 205 | 634 | 206 | 633 | 116 | 723 | 160 | 679 | 186 | 653 | 167 | 672 | 79 | 760 | 85 | 754 | +| 360 – 379 | 77 | 762 | 92 | 747 | 58 | 781 | 62 | 777 | 69 | 770 | 54 | 785 | 36 | 803 | 32 | 807 | 25 | 814 | 18 | 821 | +| 380 – 399 | 11 | 828 | 4 | 835 | 3 | 836 | 19 | 820 | 22 | 817 | 41 | 798 | 38 | 801 | 44 | 795 | 52 | 787 | 45 | 794 | +| 400 – 419 | 63 | 776 | 67 | 772 | 72 | 767 | 76 | 763 | 94 | 745 | 102 | 737 | 90 | 749 | 109 | 730 | 165 | 674 | 111 | 728 | +| 420 – 439 | 209 | 630 | 204 | 635 | 117 | 722 | 188 | 651 | 159 | 680 | 198 | 641 | 113 | 726 | 183 | 656 | 180 | 659 | 177 | 662 | +| 440 – 459 | 196 | 643 | 155 | 684 | 214 | 625 | 126 | 713 | 131 | 708 | 219 | 620 | 222 | 617 | 226 | 613 | 230 | 609 | 232 | 607 | +| 460 – 479 | 262 | 577 | 252 | 587 | 418 | 421 | 416 | 423 | 413 | 426 | 411 | 428 | 376 | 463 | 395 | 444 | 283 | 556 | 285 | 554 | +| 480 – 499 | 379 | 460 | 390 | 449 | 363 | 476 | 384 | 455 | 388 | 451 | 386 | 453 | 361 | 478 | 387 | 452 | 360 | 479 | 310 | 529 | +| 500 – 519 | 354 | 485 | 328 | 511 | 315 | 524 | 337 | 502 | 349 | 490 | 335 | 504 | 324 | 515 | 323 | 516 | 320 | 519 | 334 | 505 | +| 520 – 539 | 359 | 480 | 295 | 544 | 385 | 454 | 292 | 547 | 291 | 548 | 381 | 458 | 399 | 440 | 380 | 459 | 397 | 442 | 369 | 470 | +| 540 – 559 | 377 | 462 | 410 | 429 | 407 | 432 | 281 | 558 | 414 | 425 | 247 | 592 | 277 | 562 | 271 | 568 | 272 | 567 | 264 | 575 | +| 560 – 579 | 259 | 580 | 237 | 602 | 239 | 600 | 244 | 595 | 243 | 596 | 275 | 564 | 278 | 561 | 250 | 589 | 246 | 593 | 417 | 422 | +| 580 – 599 | 248 | 591 | 394 | 445 | 393 | 446 | 370 | 469 | 365 | 474 | 300 | 539 | 299 | 540 | 364 | 475 | 362 | 477 | 298 | 541 | +| 600 – 619 | 312 | 527 | 313 | 526 | 314 | 525 | 353 | 486 | 352 | 487 | 343 | 496 | 327 | 512 | 350 | 489 | 326 | 513 | 319 | 520 | +| 620 – 639 | 332 | 507 | 333 | 506 | 348 | 491 | 347 | 492 | 322 | 517 | 330 | 509 | 338 | 501 | 341 | 498 | 340 | 499 | 342 | 497 | +| 640 – 659 | 301 | 538 | 366 | 473 | 401 | 438 | 371 | 468 | 408 | 431 | 375 | 464 | 249 | 590 | 269 | 570 | 238 | 601 | 234 | 605 | +| 660 – 679 | 257 | 582 | 273 | 566 | 255 | 584 | 254 | 585 | 245 | 594 | 251 | 588 | 412 | 427 | 372 | 467 | 282 | 557 | 403 | 436 | +| 680 – 699 | 396 | 443 | 392 | 447 | 391 | 448 | 382 | 457 | 389 | 450 | 294 | 545 | 297 | 542 | 311 | 528 | 344 | 495 | 345 | 494 | +| 700 – 719 | 318 | 521 | 331 | 508 | 325 | 514 | 321 | 518 | 346 | 493 | 339 | 500 | 351 | 488 | 306 | 533 | 289 | 550 | 400 | 439 | +| 720 – 739 | 378 | 461 | 374 | 465 | 415 | 424 | 270 | 569 | 241 | 598 | 231 | 608 | 260 | 579 | 268 | 571 | 276 | 563 | 409 | 430 | +| 740 – 759 | 398 | 441 | 290 | 549 | 304 | 535 | 308 | 531 | 358 | 481 | 316 | 523 | 293 | 546 | 288 | 551 | 284 | 555 | 368 | 471 | +| 760 – 779 | 253 | 586 | 256 | 583 | 263 | 576 | 242 | 597 | 274 | 565 | 402 | 437 | 383 | 456 | 357 | 482 | 329 | 510 | 317 | 522 | +| 780 – 799 | 307 | 532 | 286 | 553 | 287 | 552 | 266 | 573 | 261 | 578 | 236 | 603 | 303 | 536 | 356 | 483 | 355 | 484 | 405 | 434 | +| 800 – 819 | 404 | 435 | 406 | 433 | 235 | 604 | 267 | 572 | 302 | 537 | 309 | 530 | 265 | 574 | 233 | 606 | 367 | 472 | 296 | 543 | +| 820 – 837 | 336 | 503 | 305 | 534 | 373 | 466 | 280 | 559 | 279 | 560 | 419 | 420 | 240 | 599 | 258 | 581 | 229 | 610 | - | - | + +**Table 6.3.3.1-4: Mapping from *logical index* to sequence number for preamble formats with .** + +| | Sequence number in increasing order of | | | | | | | | | | | | | | | | | | | | | +|-----------|----------------------------------------|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----| +| | 0 – 19 | 1 | 138 | 2 | 137 | 3 | 136 | 4 | 135 | 5 | 134 | 6 | 133 | 7 | 132 | 8 | 131 | 9 | 130 | 10 | 129 | +| 20 – 39 | 11 | 128 | 12 | 127 | 13 | 126 | 14 | 125 | 15 | 124 | 16 | 123 | 17 | 122 | 18 | 121 | 19 | 120 | 20 | 119 | | +| 40 – 59 | 21 | 118 | 22 | 117 | 23 | 116 | 24 | 115 | 25 | 114 | 26 | 113 | 27 | 112 | 28 | 111 | 29 | 110 | 30 | 109 | | +| 60 – 79 | 31 | 108 | 32 | 107 | 33 | 106 | 34 | 105 | 35 | 104 | 36 | 103 | 37 | 102 | 38 | 101 | 39 | 100 | 40 | 99 | | +| 80 – 99 | 41 | 98 | 42 | 97 | 43 | 96 | 44 | 95 | 45 | 94 | 46 | 93 | 47 | 92 | 48 | 91 | 49 | 90 | 50 | 89 | | +| 100 – 119 | 51 | 88 | 52 | 87 | 53 | 86 | 54 | 85 | 55 | 84 | 56 | 83 | 57 | 82 | 58 | 81 | 59 | 80 | 60 | 79 | | +| 120 – 137 | 61 | 78 | 62 | 77 | 63 | 76 | 64 | 75 | 65 | 74 | 66 | 73 | 67 | 72 | 68 | 71 | 69 | 70 | - | - | | +| 138 – 837 | N/A | | | | | | | | | | | | | | | | | | | | | + +**Table 6.3.3.1-4A: Mapping from *logical index* to sequence number for preamble formats with .** + +| | Sequence number in increasing order of | | | | | | | | | | | | | | | | | | | | +|-----------|----------------------------------------|------|-----|------|-----|------|-----|------|-----|------|-----|------|-----|------|-----|------|-----|------|-----|------| +| 0-19 | 1 | 1150 | 2 | 1149 | 3 | 1148 | 4 | 1147 | 5 | 1146 | 6 | 1145 | 7 | 1144 | 8 | 1143 | 9 | 1142 | 10 | 1141 | +| 20-39 | 11 | 1140 | 12 | 1139 | 13 | 1138 | 14 | 1137 | 15 | 1136 | 16 | 1135 | 17 | 1134 | 18 | 1133 | 19 | 1132 | 20 | 1131 | +| 40-59 | 21 | 1130 | 22 | 1129 | 23 | 1128 | 24 | 1127 | 25 | 1126 | 26 | 1125 | 27 | 1124 | 28 | 1123 | 29 | 1122 | 30 | 1121 | +| 60-79 | 31 | 1120 | 32 | 1119 | 33 | 1118 | 34 | 1117 | 35 | 1116 | 36 | 1115 | 37 | 1114 | 38 | 1113 | 39 | 1112 | 40 | 1111 | +| 80-99 | 41 | 1110 | 42 | 1109 | 43 | 1108 | 44 | 1107 | 45 | 1106 | 46 | 1105 | 47 | 1104 | 48 | 1103 | 49 | 1102 | 50 | 1101 | +| 100-119 | 51 | 1100 | 52 | 1099 | 53 | 1098 | 54 | 1097 | 55 | 1096 | 56 | 1095 | 57 | 1094 | 58 | 1093 | 59 | 1092 | 60 | 1091 | +| 120-139 | 61 | 1090 | 62 | 1089 | 63 | 1088 | 64 | 1087 | 65 | 1086 | 66 | 1085 | 67 | 1084 | 68 | 1083 | 69 | 1082 | 70 | 1081 | +| 140-159 | 71 | 1080 | 72 | 1079 | 73 | 1078 | 74 | 1077 | 75 | 1076 | 76 | 1075 | 77 | 1074 | 78 | 1073 | 79 | 1072 | 80 | 1071 | +| 160-179 | 81 | 1070 | 82 | 1069 | 83 | 1068 | 84 | 1067 | 85 | 1066 | 86 | 1065 | 87 | 1064 | 88 | 1063 | 89 | 1062 | 90 | 1061 | +| 180-199 | 91 | 1060 | 92 | 1059 | 93 | 1058 | 94 | 1057 | 95 | 1056 | 96 | 1055 | 97 | 1054 | 98 | 1053 | 99 | 1052 | 100 | 1051 | +| 200-219 | 101 | 1050 | 102 | 1049 | 103 | 1048 | 104 | 1047 | 105 | 1046 | 106 | 1045 | 107 | 1044 | 108 | 1043 | 109 | 1042 | 110 | 1041 | +| 220-239 | 111 | 1040 | 112 | 1039 | 113 | 1038 | 114 | 1037 | 115 | 1036 | 116 | 1035 | 117 | 1034 | 118 | 1033 | 119 | 1032 | 120 | 1031 | +| 240-259 | 121 | 1030 | 122 | 1029 | 123 | 1028 | 124 | 1027 | 125 | 1026 | 126 | 1025 | 127 | 1024 | 128 | 1023 | 129 | 1022 | 130 | 1021 | +| 260-279 | 131 | 1020 | 132 | 1019 | 133 | 1018 | 134 | 1017 | 135 | 1016 | 136 | 1015 | 137 | 1014 | 138 | 1013 | 139 | 1012 | 140 | 1011 | +| 280-299 | 141 | 1010 | 142 | 1009 | 143 | 1008 | 144 | 1007 | 145 | 1006 | 146 | 1005 | 147 | 1004 | 148 | 1003 | 149 | 1002 | 150 | 1001 | +| 300-319 | 151 | 1000 | 152 | 999 | 153 | 998 | 154 | 997 | 155 | 996 | 156 | 995 | 157 | 994 | 158 | 993 | 159 | 992 | 160 | 991 | +| 320-339 | 161 | 990 | 162 | 989 | 163 | 988 | 164 | 987 | 165 | 986 | 166 | 985 | 167 | 984 | 168 | 983 | 169 | 982 | 170 | 981 | +| 340-359 | 171 | 980 | 172 | 979 | 173 | 978 | 174 | 977 | 175 | 976 | 176 | 975 | 177 | 974 | 178 | 973 | 179 | 972 | 180 | 971 | +| 360-379 | 181 | 970 | 182 | 969 | 183 | 968 | 184 | 967 | 185 | 966 | 186 | 965 | 187 | 964 | 188 | 963 | 189 | 962 | 190 | 961 | +| 380-399 | 191 | 960 | 192 | 959 | 193 | 958 | 194 | 957 | 195 | 956 | 196 | 955 | 197 | 954 | 198 | 953 | 199 | 952 | 200 | 951 | +| 400-419 | 201 | 950 | 202 | 949 | 203 | 948 | 204 | 947 | 205 | 946 | 206 | 945 | 207 | 944 | 208 | 943 | 209 | 942 | 210 | 941 | +| 420-439 | 211 | 940 | 212 | 939 | 213 | 938 | 214 | 937 | 215 | 936 | 216 | 935 | 217 | 934 | 218 | 933 | 219 | 932 | 220 | 931 | +| 440-459 | 221 | 930 | 222 | 929 | 223 | 928 | 224 | 927 | 225 | 926 | 226 | 925 | 227 | 924 | 228 | 923 | 229 | 922 | 230 | 921 | +| 460-479 | 231 | 920 | 232 | 919 | 233 | 918 | 234 | 917 | 235 | 916 | 236 | 915 | 237 | 914 | 238 | 913 | 239 | 912 | 240 | 911 | +| 480-499 | 241 | 910 | 242 | 909 | 243 | 908 | 244 | 907 | 245 | 906 | 246 | 905 | 247 | 904 | 248 | 903 | 249 | 902 | 250 | 901 | +| 500-519 | 251 | 900 | 252 | 899 | 253 | 898 | 254 | 897 | 255 | 896 | 256 | 895 | 257 | 894 | 258 | 893 | 259 | 892 | 260 | 891 | +| 520-539 | 261 | 890 | 262 | 889 | 263 | 888 | 264 | 887 | 265 | 886 | 266 | 885 | 267 | 884 | 268 | 883 | 269 | 882 | 270 | 881 | +| 540-559 | 271 | 880 | 272 | 879 | 273 | 878 | 274 | 877 | 275 | 876 | 276 | 875 | 277 | 874 | 278 | 873 | 279 | 872 | 280 | 871 | +| 560-579 | 281 | 870 | 282 | 869 | 283 | 868 | 284 | 867 | 285 | 866 | 286 | 865 | 287 | 864 | 288 | 863 | 289 | 862 | 290 | 861 | +| 580-599 | 291 | 860 | 292 | 859 | 293 | 858 | 294 | 857 | 295 | 856 | 296 | 855 | 297 | 854 | 298 | 853 | 299 | 852 | 300 | 851 | +| 600-619 | 301 | 850 | 302 | 849 | 303 | 848 | 304 | 847 | 305 | 846 | 306 | 845 | 307 | 844 | 308 | 843 | 309 | 842 | 310 | 841 | +| 620-639 | 311 | 840 | 312 | 839 | 313 | 838 | 314 | 837 | 315 | 836 | 316 | 835 | 317 | 834 | 318 | 833 | 319 | 832 | 320 | 831 | +| 640-659 | 321 | 830 | 322 | 829 | 323 | 828 | 324 | 827 | 325 | 826 | 326 | 825 | 327 | 824 | 328 | 823 | 329 | 822 | 330 | 821 | +| 660-679 | 331 | 820 | 332 | 819 | 333 | 818 | 334 | 817 | 335 | 816 | 336 | 815 | 337 | 814 | 338 | 813 | 339 | 812 | 340 | 811 | +| 680-699 | 341 | 810 | 342 | 809 | 343 | 808 | 344 | 807 | 345 | 806 | 346 | 805 | 347 | 804 | 348 | 803 | 349 | 802 | 350 | 801 | +| 700-719 | 351 | 800 | 352 | 799 | 353 | 798 | 354 | 797 | 355 | 796 | 356 | 795 | 357 | 794 | 358 | 793 | 359 | 792 | 360 | 791 | +| 720-739 | 361 | 790 | 362 | 789 | 363 | 788 | 364 | 787 | 365 | 786 | 366 | 785 | 367 | 784 | 368 | 783 | 369 | 782 | 370 | 781 | +| 740-759 | 371 | 780 | 372 | 779 | 373 | 778 | 374 | 777 | 375 | 776 | 376 | 775 | 377 | 774 | 378 | 773 | 379 | 772 | 380 | 771 | +| 760-779 | 381 | 770 | 382 | 769 | 383 | 768 | 384 | 767 | 385 | 766 | 386 | 765 | 387 | 764 | 388 | 763 | 389 | 762 | 390 | 761 | +| 780-799 | 391 | 760 | 392 | 759 | 393 | 758 | 394 | 757 | 395 | 756 | 396 | 755 | 397 | 754 | 398 | 753 | 399 | 752 | 400 | 751 | +| 800-819 | 401 | 750 | 402 | 749 | 403 | 748 | 404 | 747 | 405 | 746 | 406 | 745 | 407 | 744 | 408 | 743 | 409 | 742 | 410 | 741 | +| 820-839 | 411 | 740 | 412 | 739 | 413 | 738 | 414 | 737 | 415 | 736 | 416 | 735 | 417 | 734 | 418 | 733 | 419 | 732 | 420 | 731 | +| 840-859 | 421 | 730 | 422 | 729 | 423 | 728 | 424 | 727 | 425 | 726 | 426 | 725 | 427 | 724 | 428 | 723 | 429 | 722 | 430 | 721 | +| 860-879 | 431 | 720 | 432 | 719 | 433 | 718 | 434 | 717 | 435 | 716 | 436 | 715 | 437 | 714 | 438 | 713 | 439 | 712 | 440 | 711 | +| 880-899 | 441 | 710 | 442 | 709 | 443 | 708 | 444 | 707 | 445 | 706 | 446 | 705 | 447 | 704 | 448 | 703 | 449 | 702 | 450 | 701 | +| 900-919 | 451 | 700 | 452 | 699 | 453 | 698 | 454 | 697 | 455 | 696 | 456 | 695 | 457 | 694 | 458 | 693 | 459 | 692 | 460 | 691 | +| 920-939 | 461 | 690 | 462 | 689 | 463 | 688 | 464 | 687 | 465 | 686 | 466 | 685 | 467 | 684 | 468 | 683 | 469 | 682 | 470 | 681 | +| 940-959 | 471 | 680 | 472 | 679 | 473 | 678 | 474 | 677 | 475 | 676 | 476 | 675 | 477 | 674 | 478 | 673 | 479 | 672 | 480 | 671 | +| 960-979 | 481 | 670 | 482 | 669 | 483 | 668 | 484 | 667 | 485 | 666 | 486 | 665 | 487 | 664 | 488 | 663 | 489 | 662 | 490 | 661 | +| 980-999 | 491 | 660 | 492 | 659 | 493 | 658 | 494 | 657 | 495 | 656 | 496 | 655 | 497 | 654 | 498 | 653 | 499 | 652 | 500 | 651 | +| 1000-1019 | 501 | 650 | 502 | 649 | 503 | 648 | 504 | 647 | 505 | 646 | 506 | 645 | 507 | 644 | 508 | 643 | 509 | 642 | 510 | 641 | +| 1020-1039 | 511 | 640 | 512 | 639 | 513 | 638 | 514 | 637 | 515 | 636 | 516 | 635 | 517 | 634 | 518 | 633 | 519 | 632 | 520 | 631 | +| 1040-1059 | 521 | 630 | 522 | 629 | 523 | 628 | 524 | 627 | 525 | 626 | 526 | 625 | 527 | 624 | 528 | 623 | 529 | 622 | 530 | 621 | +| 1060-1079 | 531 | 620 | 532 | 619 | 533 | 618 | 534 | 617 | 535 | 616 | 536 | 615 | 537 | 614 | 538 | 613 | 539 | 612 | 540 | 611 | +| 1080-1099 | 541 | 610 | 542 | 609 | 543 | 608 | 544 | 607 | 545 | 606 | 546 | 605 | 547 | 604 | 548 | 603 | 549 | 602 | 550 | 601 | +| 1100-1119 | 551 | 600 | 552 | 599 | 553 | 598 | 554 | 597 | 555 | 596 | 556 | 595 | 557 | 594 | 558 | 593 | 559 | 592 | 560 | 591 | +| 1120-1139 | 561 | 590 | 562 | 589 | 563 | 588 | 564 | 587 | 565 | 586 | 566 | 585 | 567 | 584 | 568 | 583 | 569 | 582 | 570 | 581 | +| 1140-1149 | 571 | 580 | 572 | 579 | 573 | 578 | 574 | 577 | 575 | 576 | - | - | - | - | - | - | - | - | - | - | + +**Table 6.3.3.1-4B: Mapping from *logical index* to sequence number for preamble formats with .** + +| | Sequence number in increasing order of | | | | | | | | | | | | | | | | | | | | +|---------|----------------------------------------|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----| +| | 0-19 | 1 | 570 | 2 | 569 | 3 | 568 | 4 | 567 | 5 | 566 | 6 | 565 | 7 | 564 | 8 | 563 | 9 | 562 | 10 | +| 20-39 | 11 | 560 | 12 | 559 | 13 | 558 | 14 | 557 | 15 | 556 | 16 | 555 | 17 | 554 | 18 | 553 | 19 | 552 | 20 | 551 | +| 40-59 | 21 | 550 | 22 | 549 | 23 | 548 | 24 | 547 | 25 | 546 | 26 | 545 | 27 | 544 | 28 | 543 | 29 | 542 | 30 | 541 | +| 60-79 | 31 | 540 | 32 | 539 | 33 | 538 | 34 | 537 | 35 | 536 | 36 | 535 | 37 | 534 | 38 | 533 | 39 | 532 | 40 | 531 | +| 80-99 | 41 | 530 | 42 | 529 | 43 | 528 | 44 | 527 | 45 | 526 | 46 | 525 | 47 | 524 | 48 | 523 | 49 | 522 | 50 | 521 | +| 100-119 | 51 | 520 | 52 | 519 | 53 | 518 | 54 | 517 | 55 | 516 | 56 | 515 | 57 | 514 | 58 | 513 | 59 | 512 | 60 | 511 | +| 120-139 | 61 | 510 | 62 | 509 | 63 | 508 | 64 | 507 | 65 | 506 | 66 | 505 | 67 | 504 | 68 | 503 | 69 | 502 | 70 | 501 | +| 140-159 | 71 | 500 | 72 | 499 | 73 | 498 | 74 | 497 | 75 | 496 | 76 | 495 | 77 | 494 | 78 | 493 | 79 | 492 | 80 | 491 | +| 160-179 | 81 | 490 | 82 | 489 | 83 | 488 | 84 | 487 | 85 | 486 | 86 | 485 | 87 | 484 | 88 | 483 | 89 | 482 | 90 | 481 | +| 180-199 | 91 | 480 | 92 | 479 | 93 | 478 | 94 | 477 | 95 | 476 | 96 | 475 | 97 | 474 | 98 | 473 | 99 | 472 | 100 | 471 | +| 200-219 | 101 | 470 | 102 | 469 | 103 | 468 | 104 | 467 | 105 | 466 | 106 | 465 | 107 | 464 | 108 | 463 | 109 | 462 | 110 | 461 | +| 220-239 | 111 | 460 | 112 | 459 | 113 | 458 | 114 | 457 | 115 | 456 | 116 | 455 | 117 | 454 | 118 | 453 | 119 | 452 | 120 | 451 | +| 240-259 | 121 | 450 | 122 | 449 | 123 | 448 | 124 | 447 | 125 | 446 | 126 | 445 | 127 | 444 | 128 | 443 | 129 | 442 | 130 | 441 | +| 260-279 | 131 | 440 | 132 | 439 | 133 | 438 | 134 | 437 | 135 | 436 | 136 | 435 | 137 | 434 | 138 | 433 | 139 | 432 | 140 | 431 | +| 280-299 | 141 | 430 | 142 | 429 | 143 | 428 | 144 | 427 | 145 | 426 | 146 | 425 | 147 | 424 | 148 | 423 | 149 | 422 | 150 | 421 | +| 300-319 | 151 | 420 | 152 | 419 | 153 | 418 | 154 | 417 | 155 | 416 | 156 | 415 | 157 | 414 | 158 | 413 | 159 | 412 | 160 | 411 | +| 320-339 | 161 | 410 | 162 | 409 | 163 | 408 | 164 | 407 | 165 | 406 | 166 | 405 | 167 | 404 | 168 | 403 | 169 | 402 | 170 | 401 | +| 340-359 | 171 | 400 | 172 | 399 | 173 | 398 | 174 | 397 | 175 | 396 | 176 | 395 | 177 | 394 | 178 | 393 | 179 | 392 | 180 | 391 | +| 360-379 | 181 | 390 | 182 | 389 | 183 | 388 | 184 | 387 | 185 | 386 | 186 | 385 | 187 | 384 | 188 | 383 | 189 | 382 | 190 | 381 | +| 380-399 | 191 | 380 | 192 | 379 | 193 | 378 | 194 | 377 | 195 | 376 | 196 | 375 | 197 | 374 | 198 | 373 | 199 | 372 | 200 | 371 | +| 400-419 | 201 | 370 | 202 | 369 | 203 | 368 | 204 | 367 | 205 | 366 | 206 | 365 | 207 | 364 | 208 | 363 | 209 | 362 | 210 | 361 | +| 420-439 | 211 | 360 | 212 | 359 | 213 | 358 | 214 | 357 | 215 | 356 | 216 | 355 | 217 | 354 | 218 | 353 | 219 | 352 | 220 | 351 | +| 440-459 | 221 | 350 | 222 | 349 | 223 | 348 | 224 | 347 | 225 | 346 | 226 | 345 | 227 | 344 | 228 | 343 | 229 | 342 | 230 | 341 | +| 460-479 | 231 | 340 | 232 | 339 | 233 | 338 | 234 | 337 | 235 | 336 | 236 | 335 | 237 | 334 | 238 | 333 | 239 | 332 | 240 | 331 | +| 480-499 | 241 | 330 | 242 | 329 | 243 | 328 | 244 | 327 | 245 | 326 | 246 | 325 | 247 | 324 | 248 | 323 | 249 | 322 | 250 | 321 | +| 500-519 | 251 | 320 | 252 | 319 | 253 | 318 | 254 | 317 | 255 | 316 | 256 | 315 | 257 | 314 | 258 | 313 | 259 | 312 | 260 | 311 | +| 520-539 | 261 | 310 | 262 | 309 | 263 | 308 | 264 | 307 | 265 | 306 | 266 | 305 | 267 | 304 | 268 | 303 | 269 | 302 | 270 | 301 | +| 540-559 | 271 | 300 | 272 | 299 | 273 | 298 | 274 | 297 | 275 | 296 | 276 | 295 | 277 | 294 | 278 | 293 | 279 | 292 | 280 | 291 | +| 560-569 | 281 | 290 | 282 | 289 | 283 | 288 | 284 | 287 | 285 | 286 | - | - | - | - | - | - | - | - | - | - | + +**Table 6.3.3.1-5: for preamble formats with kHz.** + +| zeroCorrelationZoneConfig, msgA-ZeroCorrelationZoneConfig | value | | | +|------------------------------------------------------------------|------------------|-----------------------|-----------------------| +| | Unrestricted set | Restricted set type A | Restricted set type B | +| 0 | 0 | 15 | 15 | +| 1 | 13 | 18 | 18 | +| 2 | 15 | 22 | 22 | +| 3 | 18 | 26 | 26 | +| 4 | 22 | 32 | 32 | +| 5 | 26 | 38 | 38 | +| 6 | 32 | 46 | 46 | +| 7 | 38 | 55 | 55 | +| 8 | 46 | 68 | 68 | +| 9 | 59 | 82 | 82 | +| 10 | 76 | 100 | 100 | +| 11 | 93 | 128 | 118 | +| 12 | 119 | 158 | 137 | +| 13 | 167 | 202 | - | +| 14 | 279 | 237 | - | +| 15 | 419 | - | - | + +**Table 6.3.3.1-6: for preamble formats with kHz.** + +| zeroCorrelationZoneConfig, msgA-ZeroCorrelationZoneConfig | value | | | +|------------------------------------------------------------------|------------------|-----------------------|-----------------------| +| | Unrestricted set | Restricted set type A | Restricted set type B | +| 0 | 0 | 36 | 36 | +| 1 | 13 | 57 | 57 | +| 2 | 26 | 72 | 60 | +| 3 | 33 | 81 | 63 | +| 4 | 38 | 89 | 65 | +| 5 | 41 | 94 | 68 | +| 6 | 49 | 103 | 71 | +| 7 | 55 | 112 | 77 | +| 8 | 64 | 121 | 81 | +| 9 | 76 | 132 | 85 | +| 10 | 93 | 137 | 97 | +| 11 | 119 | 152 | 109 | +| 12 | 139 | 173 | 122 | +| 13 | 209 | 195 | 137 | +| 14 | 279 | 216 | - | +| 15 | 419 | 237 | - | + +**Table 6.3.3.1-7: for preamble formats with .** + +| zeroCorrelationZoneConfig, msgA-ZeroCorrelationZoneConfig | value | | | +|------------------------------------------------------------------|-------|-----|-----| +| | | | | +| 0 | 0 | 0 | 0 | +| 1 | 2 | 8 | 17 | +| 2 | 4 | 10 | 21 | +| 3 | 6 | 12 | 25 | +| 4 | 8 | 15 | 30 | +| 5 | 10 | 17 | 35 | +| 6 | 12 | 21 | 44 | +| 7 | 13 | 25 | 52 | +| 8 | 15 | 31 | 63 | +| 9 | 17 | 40 | 82 | +| 10 | 19 | 51 | 104 | +| 11 | 23 | 63 | 127 | +| 12 | 27 | 81 | 164 | +| 13 | 34 | 114 | 230 | +| 14 | 46 | 190 | 383 | +| 15 | 69 | 285 | 575 | + +### 6.3.3.2 Mapping to physical resources + +The preamble sequence shall be mapped to physical resources according to + +where $\alpha$ is an amplitude scaling factor in order to conform to the transmit power specified in [5, TS38.213], and $p$ is the antenna port. Baseband signal generation shall be done according to clause 5.3 using the parameters in Table 6.3.3.1-1 or Table 6.3.3.1-2 with $\beta$ given by Table 6.3.3.2-1. + +Random access preambles can only be transmitted in the time resources obtained from Tables 6.3.3.2-2 to 6.3.3.2-4 and depends on FR1 or FR2 and the spectrum type as defined in [8, TS38.104]. The PRACH configuration index in Tables 6.3.3.2-2 to 6.3.3.2-4 is + +- for Table 6.3.3.2-3 given by the higher-layer parameter *prach-ConfigurationIndex*, or by *msgA-PRACH-ConfigurationIndex* if configured; and +- for Tables 6.3.3.2-2 and 6.3.3.2-4 given by the higher-layer parameter *prach-ConfigurationIndex*, or by *msgA-PRACH-ConfigurationIndex* if configured. + +For the IAB-MT part of an IAB-node, the following applies: + +- if the higher-layer parameter *prach-ConfigurationPeriodScaling-IAB* is configured, the variable used in of Tables 6.3.3.2-2 to 6.3.3.2-4 shall be replaced by $\text{prach-ConfigurationPeriodScaling-IAB}$ , where $\text{prach-ConfigurationPeriodScaling-IAB}$ is given by the higher-layer parameter *prach-ConfigurationPeriodScaling-IAB* and the IAB-node does not expect $\text{prach-ConfigurationPeriodScaling-IAB}$ to be larger than 64; +- if the higher-layer parameter *prach-ConfigurationFrameOffset-IAB* is configured, the variable used in of Tables 6.3.3.2-2 to 6.3.3.2-4 shall be replaced by $\text{prach-ConfigurationFrameOffset-IAB}$ , where $\text{prach-ConfigurationFrameOffset-IAB}$ is given by the higher-layer parameter *prach-ConfigurationFrameOffset-IAB*, and ; +- if the higher-layer parameter *prach-ConfigurationSOffset-IAB* is configured, the subframe number from Tables 6.3.3.2-2 to 6.3.3.2-3 and the slot number from Table 6.3.3.2-4 shall be replaced by $\text{prach-ConfigurationSOffset-IAB}$ , where $\text{prach-ConfigurationSOffset-IAB}$ is given by the higher-layer parameter *prach-ConfigurationSOffset-IAB*, and $\text{prach-ConfigurationSOffset-IAB}$ is the number of subframes in a frame when using Tables 6.3.3.2-2 to 6.3.3.2-3 and the number of slots in a frame for 60 kHz subcarrier spacing when using in Table 6.3.3.2-4. + +Random access preambles can only be transmitted in the frequency resources given by either the higher-layer parameter *msg1-FrequencyStart* or *msgA-RO-FrequencyStart* if configured as described in clause 8.1 of [5 TS 38.213]. The PRACH frequency resources $\text{PRACH\_FDM\_Index}$ , where $\text{PRACH\_FDM\_Index}$ equals the higher-layer parameter *msg1-FDM* or *msgA-RO-FDM* if configured, are numbered in increasing order within the initial uplink bandwidth part during initial access, starting from the lowest frequency. Otherwise, $\text{PRACH\_FDM\_Index}$ are numbered in increasing order within the active uplink bandwidth part, starting from the lowest frequency. + +For operation with shared spectrum channel access, for $\text{PRACH\_FDM\_Index}$ , a UE expects to be provided with higher-layer parameter *msg1-FrequencyStart* or *msgA-RO-FrequencyStart* if configured, and higher-layer parameter *msg1-FDM* or *msgA-RO-FDM* if configured, such that a random-access preamble is confined within a single RB set. 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]. + +For operation with shared spectrum channel access, for $\text{PRACH\_FDM\_Index}$ or $\text{PRACH\_FDM\_Index}$ and Type-2 random access, a UE expects to be provided with higher-layer parameter *msgA-RO-FDM* equals to one. + +For the purpose of slot numbering in the tables, the following subcarrier spacing shall be assumed: + +- 15 kHz for FR1 +- 60 kHz for FR2. + +For handover purposes to a target cell in paired or unpaired spectrum where the target cell uses $\text{PRACH\_FDM\_Index}$ , the UE may assume the absolute value of the time difference between radio frame $\text{radio\_frame\_index}$ in the current cell and radio frame $\text{radio\_frame\_index}$ in the target cell is less than $\text{association\_pattern\_period}$ if the association pattern period in clause 8.1 of [5, TS 38.213] is not equal to 10 ms. + +For inter frequency handover purposes where the source cell is either in paired or unpaired spectrum and the target cell is in unpaired spectrum and uses $\text{PRACH\_FDM\_Index}$ , the UE may assume the absolute value of the time difference between radio frame $\text{radio\_frame\_index}$ in the current cell and radio frame $\text{radio\_frame\_index}$ in the target cell is less than + +**Table 6.3.3.2-1: Supported combinations of $N_{RB}^{RA}$ and $N_{RB}^{PUSCH}$ , and the corresponding value of $N_{RB}^{PRACH}$ .** + +| | for PRACH | for PUSCH | $N_{RB}^{RA}$ , allocation expressed in number of RBs for PUSCH | | +|------|-----------|-----------|-----------------------------------------------------------------|-----| +| 839 | 1.25 | 15 | 6 | 7 | +| 839 | 1.25 | 30 | 3 | 1 | +| 839 | 1.25 | 60 | 2 | 133 | +| 839 | 5 | 15 | 24 | 12 | +| 839 | 5 | 30 | 12 | 10 | +| 839 | 5 | 60 | 6 | 7 | +| 139 | 15 | 15 | 12 | 2 | +| 139 | 15 | 30 | 6 | 2 | +| 139 | 15 | 60 | 3 | 2 | +| 139 | 30 | 15 | 24 | 2 | +| 139 | 30 | 30 | 12 | 2 | +| 139 | 30 | 60 | 6 | 2 | +| 139 | 60 | 60 | 12 | 2 | +| 139 | 60 | 120 | 6 | 2 | +| 139 | 120 | 60 | 24 | 2 | +| 139 | 120 | 120 | 12 | 2 | +| 139 | 120 | 480 | 3 | 1 | +| 139 | 120 | 960 | 2 | 23 | +| 139 | 480 | 120 | 48 | 2 | +| 139 | 480 | 480 | 12 | 2 | +| 139 | 480 | 960 | 6 | 2 | +| 139 | 960 | 120 | 96 | 2 | +| 139 | 960 | 480 | 24 | 2 | +| 139 | 960 | 960 | 12 | 2 | +| 571 | 30 | 15 | 96 | 2 | +| 571 | 30 | 30 | 48 | 2 | +| 571 | 30 | 60 | 24 | 2 | +| 571 | 120 | 120 | 48 | 2 | +| 571 | 120 | 480 | 12 | 1 | +| 571 | 120 | 960 | 7 | 47 | +| 571 | 480 | 120 | 192 | 2 | +| 571 | 480 | 480 | 48 | 2 | +| 571 | 480 | 960 | 24 | 2 | +| 1151 | 15 | 15 | 96 | 1 | +| 1151 | 15 | 30 | 48 | 1 | +| 1151 | 15 | 60 | 24 | 1 | +| 1151 | 120 | 120 | 97 | 6 | +| 1151 | 120 | 480 | 25 | 23 | +| 1151 | 120 | 960 | 13 | 45 | + +**Table 6.3.3.2-2: Random access configurations for FR1 and paired spectrum/supplementary uplink.** + +| PRACH | Preamble | Subframe number | Starting | Number | | | +|-------|----------|-----------------|----------|--------|--|--| +|-------|----------|-----------------|----------|--------|--|--| + +| Configuration Index | format | $x$ | $y$ | | symbol | of PRACH slots within a subframe | $N_t^{\text{RA,slot}}$ , | $N_{\text{dur}}^{\text{RA}}$ , | +|---------------------|--------|-----|-----|---------------------|--------|----------------------------------|-----------------------------------------------------------|--------------------------------| +| | | | | | | | number of time-domain PRACH occasions within a PRACH slot | PRACH duration | +| 0 | 0 | 16 | 1 | 1 | 0 | - | - | 0 | +| 1 | 0 | 16 | 1 | 4 | 0 | - | - | 0 | +| 2 | 0 | 16 | 1 | 7 | 0 | - | - | 0 | +| 3 | 0 | 16 | 1 | 9 | 0 | - | - | 0 | +| 4 | 0 | 8 | 1 | 1 | 0 | - | - | 0 | +| 5 | 0 | 8 | 1 | 4 | 0 | - | - | 0 | +| 6 | 0 | 8 | 1 | 7 | 0 | - | - | 0 | +| 7 | 0 | 8 | 1 | 9 | 0 | - | - | 0 | +| 8 | 0 | 4 | 1 | 1 | 0 | - | - | 0 | +| 9 | 0 | 4 | 1 | 4 | 0 | - | - | 0 | +| 10 | 0 | 4 | 1 | 7 | 0 | - | - | 0 | +| 11 | 0 | 4 | 1 | 9 | 0 | - | - | 0 | +| 12 | 0 | 2 | 1 | 1 | 0 | - | - | 0 | +| 13 | 0 | 2 | 1 | 4 | 0 | - | - | 0 | +| 14 | 0 | 2 | 1 | 7 | 0 | - | - | 0 | +| 15 | 0 | 2 | 1 | 9 | 0 | - | - | 0 | +| 16 | 0 | 1 | 0 | 1 | 0 | - | - | 0 | +| 17 | 0 | 1 | 0 | 4 | 0 | - | - | 0 | +| 18 | 0 | 1 | 0 | 7 | 0 | - | - | 0 | +| 19 | 0 | 1 | 0 | 1,6 | 0 | - | - | 0 | +| 20 | 0 | 1 | 0 | 2,7 | 0 | - | - | 0 | +| 21 | 0 | 1 | 0 | 3,8 | 0 | - | - | 0 | +| 22 | 0 | 1 | 0 | 1,4,7 | 0 | - | - | 0 | +| 23 | 0 | 1 | 0 | 2,5,8 | 0 | - | - | 0 | +| 24 | 0 | 1 | 0 | 3,6,9 | 0 | - | - | 0 | +| 25 | 0 | 1 | 0 | 0,2,4,6,8 | 0 | - | - | 0 | +| 26 | 0 | 1 | 0 | 1,3,5,7,9 | 0 | - | - | 0 | +| 27 | 0 | 1 | 0 | 0,1,2,3,4,5,6,7,8,9 | 0 | - | - | 0 | +| 28 | 1 | 16 | 1 | 1 | 0 | - | - | 0 | +| 29 | 1 | 16 | 1 | 4 | 0 | - | - | 0 | +| 30 | 1 | 16 | 1 | 7 | 0 | - | - | 0 | +| 31 | 1 | 16 | 1 | 9 | 0 | - | - | 0 | +| 32 | 1 | 8 | 1 | 1 | 0 | - | - | 0 | +| 33 | 1 | 8 | 1 | 4 | 0 | - | - | 0 | +| 34 | 1 | 8 | 1 | 7 | 0 | - | - | 0 | +| 35 | 1 | 8 | 1 | 9 | 0 | - | - | 0 | +| 36 | 1 | 4 | 1 | 1 | 0 | - | - | 0 | +| 37 | 1 | 4 | 1 | 4 | 0 | - | - | 0 | +| 38 | 1 | 4 | 1 | 7 | 0 | - | - | 0 | +| 39 | 1 | 4 | 1 | 9 | 0 | - | - | 0 | +| 40 | 1 | 2 | 1 | 1 | 0 | - | - | 0 | +| 41 | 1 | 2 | 1 | 4 | 0 | - | - | 0 | +| 42 | 1 | 2 | 1 | 7 | 0 | - | - | 0 | +| 43 | 1 | 2 | 1 | 9 | 0 | - | - | 0 | +| 44 | 1 | 1 | 0 | 1 | 0 | - | - | 0 | +| 45 | 1 | 1 | 0 | 4 | 0 | - | - | 0 | +| 46 | 1 | 1 | 0 | 7 | 0 | - | - | 0 | +| 47 | 1 | 1 | 0 | 1,6 | 0 | - | - | 0 | +| 48 | 1 | 1 | 0 | 2,7 | 0 | - | - | 0 | +| 49 | 1 | 1 | 0 | 3,8 | 0 | - | - | 0 | +| 50 | 1 | 1 | 0 | 1,4,7 | 0 | - | - | 0 | +| 51 | 1 | 1 | 0 | 2,5,8 | 0 | - | - | 0 | +| 52 | 1 | 1 | 0 | 3,6,9 | 0 | - | - | 0 | +| 53 | 2 | 16 | 1 | 1 | 0 | - | - | 0 | +| 54 | 2 | 8 | 1 | 1 | 0 | - | - | 0 | +| 55 | 2 | 4 | 0 | 1 | 0 | - | - | 0 | + +| | | | | | | | | | +|-----|-------|----|---|---------------------|---|---|---|---| +| 56 | 2 | 2 | 0 | 1 | 0 | - | - | 0 | +| 57 | 2 | 2 | 0 | 5 | 0 | - | - | 0 | +| 58 | 2 | 1 | 0 | 1 | 0 | - | - | 0 | +| 59 | 2 | 1 | 0 | 5 | 0 | - | - | 0 | +| 60 | 3 | 16 | 1 | 1 | 0 | - | - | 0 | +| 61 | 3 | 16 | 1 | 4 | 0 | - | - | 0 | +| 62 | 3 | 16 | 1 | 7 | 0 | - | - | 0 | +| 63 | 3 | 16 | 1 | 9 | 0 | - | - | 0 | +| 64 | 3 | 8 | 1 | 1 | 0 | - | - | 0 | +| 65 | 3 | 8 | 1 | 4 | 0 | - | - | 0 | +| 66 | 3 | 8 | 1 | 7 | 0 | - | - | 0 | +| 67 | 3 | 4 | 1 | 1 | 0 | - | - | 0 | +| 68 | 3 | 4 | 1 | 4 | 0 | - | - | 0 | +| 69 | 3 | 4 | 1 | 7 | 0 | - | - | 0 | +| 70 | 3 | 4 | 1 | 9 | 0 | - | - | 0 | +| 71 | 3 | 2 | 1 | 1 | 0 | - | - | 0 | +| 72 | 3 | 2 | 1 | 4 | 0 | - | - | 0 | +| 73 | 3 | 2 | 1 | 7 | 0 | - | - | 0 | +| 74 | 3 | 2 | 1 | 9 | 0 | - | - | 0 | +| 75 | 3 | 1 | 0 | 1 | 0 | - | - | 0 | +| 76 | 3 | 1 | 0 | 4 | 0 | - | - | 0 | +| 77 | 3 | 1 | 0 | 7 | 0 | - | - | 0 | +| 78 | 3 | 1 | 0 | 1,6 | 0 | - | - | 0 | +| 79 | 3 | 1 | 0 | 2,7 | 0 | - | - | 0 | +| 80 | 3 | 1 | 0 | 3,8 | 0 | - | - | 0 | +| 81 | 3 | 1 | 0 | 1,4,7 | 0 | - | - | 0 | +| 82 | 3 | 1 | 0 | 2,5,8 | 0 | - | - | 0 | +| 83 | 3 | 1 | 0 | 3,6,9 | 0 | - | - | 0 | +| 84 | 3 | 1 | 0 | 0,2,4,6,8 | 0 | - | - | 0 | +| 85 | 3 | 1 | 0 | 1,3,5,7,9 | 0 | - | - | 0 | +| 86 | 3 | 1 | 0 | 0,1,2,3,4,5,6,7,8,9 | 0 | - | - | 0 | +| 87 | A1 | 16 | 0 | 4,9 | 0 | 1 | 6 | 2 | +| 88 | A1 | 16 | 1 | 4 | 0 | 2 | 6 | 2 | +| 89 | A1 | 8 | 0 | 4,9 | 0 | 1 | 6 | 2 | +| 90 | A1 | 8 | 1 | 4 | 0 | 2 | 6 | 2 | +| 91 | A1 | 4 | 0 | 4,9 | 0 | 1 | 6 | 2 | +| 92 | A1 | 4 | 1 | 4,9 | 0 | 1 | 6 | 2 | +| 93 | A1 | 4 | 0 | 4 | 0 | 2 | 6 | 2 | +| 94 | A1 | 2 | 0 | 4,9 | 0 | 1 | 6 | 2 | +| 95 | A1 | 2 | 0 | 1 | 0 | 2 | 6 | 2 | +| 96 | A1 | 2 | 0 | 4 | 0 | 2 | 6 | 2 | +| 97 | A1 | 2 | 0 | 7 | 0 | 2 | 6 | 2 | +| 98 | A1 | 1 | 0 | 4 | 0 | 1 | 6 | 2 | +| 99 | A1 | 1 | 0 | 1,6 | 0 | 1 | 6 | 2 | +| 100 | A1 | 1 | 0 | 4,9 | 0 | 1 | 6 | 2 | +| 101 | A1 | 1 | 0 | 1 | 0 | 2 | 6 | 2 | +| 102 | A1 | 1 | 0 | 7 | 0 | 2 | 6 | 2 | +| 103 | A1 | 1 | 0 | 2,7 | 0 | 2 | 6 | 2 | +| 104 | A1 | 1 | 0 | 1,4,7 | 0 | 2 | 6 | 2 | +| 105 | A1 | 1 | 0 | 0,2,4,6,8 | 0 | 2 | 6 | 2 | +| 106 | A1 | 1 | 0 | 0,1,2,3,4,5,6,7,8,9 | 0 | 2 | 6 | 2 | +| 107 | A1 | 1 | 0 | 1,3,5,7,9 | 0 | 2 | 6 | 2 | +| 108 | A1/B1 | 2 | 0 | 4,9 | 0 | 1 | 7 | 2 | +| 109 | A1/B1 | 2 | 0 | 4 | 0 | 2 | 7 | 2 | +| 110 | A1/B1 | 1 | 0 | 4 | 0 | 1 | 7 | 2 | +| 111 | A1/B1 | 1 | 0 | 1,6 | 0 | 1 | 7 | 2 | +| 112 | A1/B1 | 1 | 0 | 4,9 | 0 | 1 | 7 | 2 | +| 113 | A1/B1 | 1 | 0 | 1 | 0 | 2 | 7 | 2 | +| 114 | A1/B1 | 1 | 0 | 7 | 0 | 2 | 7 | 2 | +| 115 | A1/B1 | 1 | 0 | 1,4,7 | 0 | 2 | 7 | 2 | +| 116 | A1/B1 | 1 | 0 | 0,2,4,6,8 | 0 | 2 | 7 | 2 | +| 117 | A2 | 16 | 1 | 2,6,9 | 0 | 1 | 3 | 4 | +| 118 | A2 | 16 | 1 | 4 | 0 | 2 | 3 | 4 | +| 119 | A2 | 8 | 1 | 2,6,9 | 0 | 1 | 3 | 4 | +| 120 | A2 | 8 | 1 | 4 | 0 | 2 | 3 | 4 | + +| | | | | | | | | | +|-----|-------|----|---|---------------------|---|---|---|---| +| 121 | A2 | 4 | 0 | 2,6,9 | 0 | 1 | 3 | 4 | +| 122 | A2 | 4 | 0 | 4 | 0 | 2 | 3 | 4 | +| 123 | A2 | 2 | 1 | 2,6,9 | 0 | 1 | 3 | 4 | +| 124 | A2 | 2 | 0 | 1 | 0 | 2 | 3 | 4 | +| 125 | A2 | 2 | 0 | 4 | 0 | 2 | 3 | 4 | +| 126 | A2 | 2 | 0 | 7 | 0 | 2 | 3 | 4 | +| 127 | A2 | 1 | 0 | 4 | 0 | 1 | 3 | 4 | +| 128 | A2 | 1 | 0 | 1,6 | 0 | 1 | 3 | 4 | +| 129 | A2 | 1 | 0 | 4,9 | 0 | 1 | 3 | 4 | +| 130 | A2 | 1 | 0 | 1 | 0 | 2 | 3 | 4 | +| 131 | A2 | 1 | 0 | 7 | 0 | 2 | 3 | 4 | +| 132 | A2 | 1 | 0 | 2,7 | 0 | 2 | 3 | 4 | +| 133 | A2 | 1 | 0 | 1,4,7 | 0 | 2 | 3 | 4 | +| 134 | A2 | 1 | 0 | 0,2,4,6,8 | 0 | 2 | 3 | 4 | +| 135 | A2 | 1 | 0 | 0,1,2,3,4,5,6,7,8,9 | 0 | 2 | 3 | 4 | +| 136 | A2 | 1 | 0 | 1,3,5,7,9 | 0 | 2 | 3 | 4 | +| 137 | A2/B2 | 2 | 1 | 2,6,9 | 0 | 1 | 3 | 4 | +| 138 | A2/B2 | 2 | 0 | 4 | 0 | 2 | 3 | 4 | +| 139 | A2/B2 | 1 | 0 | 4 | 0 | 1 | 3 | 4 | +| 140 | A2/B2 | 1 | 0 | 1,6 | 0 | 1 | 3 | 4 | +| 141 | A2/B2 | 1 | 0 | 4,9 | 0 | 1 | 3 | 4 | +| 142 | A2/B2 | 1 | 0 | 1 | 0 | 2 | 3 | 4 | +| 143 | A2/B2 | 1 | 0 | 7 | 0 | 2 | 3 | 4 | +| 144 | A2/B2 | 1 | 0 | 1,4,7 | 0 | 2 | 3 | 4 | +| 145 | A2/B2 | 1 | 0 | 0,2,4,6,8 | 0 | 2 | 3 | 4 | +| 146 | A2/B2 | 1 | 0 | 0,1,2,3,4,5,6,7,8,9 | 0 | 2 | 3 | 4 | +| 147 | A3 | 16 | 1 | 4,9 | 0 | 1 | 2 | 6 | +| 148 | A3 | 16 | 1 | 4 | 0 | 2 | 2 | 6 | +| 149 | A3 | 8 | 1 | 4,9 | 0 | 1 | 2 | 6 | +| 150 | A3 | 8 | 1 | 4 | 0 | 2 | 2 | 6 | +| 151 | A3 | 4 | 0 | 4,9 | 0 | 1 | 2 | 6 | +| 152 | A3 | 4 | 0 | 4 | 0 | 2 | 2 | 6 | +| 153 | A3 | 2 | 1 | 2,6,9 | 0 | 2 | 2 | 6 | +| 154 | A3 | 2 | 0 | 1 | 0 | 2 | 2 | 6 | +| 155 | A3 | 2 | 0 | 4 | 0 | 2 | 2 | 6 | +| 156 | A3 | 2 | 0 | 7 | 0 | 2 | 2 | 6 | +| 157 | A3 | 1 | 0 | 4 | 0 | 1 | 2 | 6 | +| 158 | A3 | 1 | 0 | 1,6 | 0 | 1 | 2 | 6 | +| 159 | A3 | 1 | 0 | 4,9 | 0 | 1 | 2 | 6 | +| 160 | A3 | 1 | 0 | 1 | 0 | 2 | 2 | 6 | +| 161 | A3 | 1 | 0 | 7 | 0 | 2 | 2 | 6 | +| 162 | A3 | 1 | 0 | 2,7 | 0 | 2 | 2 | 6 | +| 163 | A3 | 1 | 0 | 1,4,7 | 0 | 2 | 2 | 6 | +| 164 | A3 | 1 | 0 | 0,2,4,6,8 | 0 | 2 | 2 | 6 | +| 165 | A3 | 1 | 0 | 0,1,2,3,4,5,6,7,8,9 | 0 | 2 | 2 | 6 | +| 166 | A3 | 1 | 0 | 1,3,5,7,9 | 0 | 2 | 2 | 6 | +| 167 | A3/B3 | 2 | 1 | 2,6,9 | 0 | 2 | 2 | 6 | +| 168 | A3/B3 | 2 | 0 | 4 | 0 | 2 | 2 | 6 | +| 169 | A3/B3 | 1 | 0 | 4 | 0 | 1 | 2 | 6 | +| 170 | A3/B3 | 1 | 0 | 1,6 | 0 | 1 | 2 | 6 | +| 171 | A3/B3 | 1 | 0 | 4,9 | 0 | 1 | 2 | 6 | +| 172 | A3/B3 | 1 | 0 | 1 | 0 | 2 | 2 | 6 | +| 173 | A3/B3 | 1 | 0 | 7 | 0 | 2 | 2 | 6 | +| 174 | A3/B3 | 1 | 0 | 1,4,7 | 0 | 2 | 2 | 6 | +| 175 | A3/B3 | 1 | 0 | 0,2,4,6,8 | 0 | 2 | 2 | 6 | +| 176 | A3/B3 | 1 | 0 | 0,1,2,3,4,5,6,7,8,9 | 0 | 2 | 2 | 6 | +| 177 | B1 | 16 | 0 | 4,9 | 0 | 1 | 7 | 2 | +| 178 | B1 | 16 | 1 | 4 | 0 | 2 | 7 | 2 | +| 179 | B1 | 8 | 0 | 4,9 | 0 | 1 | 7 | 2 | +| 180 | B1 | 8 | 1 | 4 | 0 | 2 | 7 | 2 | +| 181 | B1 | 4 | 0 | 4,9 | 0 | 1 | 7 | 2 | +| 182 | B1 | 4 | 1 | 4,9 | 0 | 1 | 7 | 2 | +| 183 | B1 | 4 | 0 | 4 | 0 | 2 | 7 | 2 | +| 184 | B1 | 2 | 0 | 4,9 | 0 | 1 | 7 | 2 | +| 185 | B1 | 2 | 0 | 1 | 0 | 2 | 7 | 2 | + +| | | | | | | | | | +|-----|----|----|---|---------------------|---|---|---|----| +| 186 | B1 | 2 | 0 | 4 | 0 | 2 | 7 | 2 | +| 187 | B1 | 2 | 0 | 7 | 0 | 2 | 7 | 2 | +| 188 | B1 | 1 | 0 | 4 | 0 | 1 | 7 | 2 | +| 189 | B1 | 1 | 0 | 1,6 | 0 | 1 | 7 | 2 | +| 190 | B1 | 1 | 0 | 4,9 | 0 | 1 | 7 | 2 | +| 191 | B1 | 1 | 0 | 1 | 0 | 2 | 7 | 2 | +| 192 | B1 | 1 | 0 | 7 | 0 | 2 | 7 | 2 | +| 193 | B1 | 1 | 0 | 2,7 | 0 | 2 | 7 | 2 | +| 194 | B1 | 1 | 0 | 1,4,7 | 0 | 2 | 7 | 2 | +| 195 | B1 | 1 | 0 | 0,2,4,6,8 | 0 | 2 | 7 | 2 | +| 196 | B1 | 1 | 0 | 0,1,2,3,4,5,6,7,8,9 | 0 | 2 | 7 | 2 | +| 197 | B1 | 1 | 0 | 1,3,5,7,9 | 0 | 2 | 7 | 2 | +| 198 | B4 | 16 | 0 | 4,9 | 0 | 2 | 1 | 12 | +| 199 | B4 | 16 | 1 | 4 | 0 | 2 | 1 | 12 | +| 200 | B4 | 8 | 0 | 4,9 | 0 | 2 | 1 | 12 | +| 201 | B4 | 8 | 1 | 4 | 0 | 2 | 1 | 12 | +| 202 | B4 | 4 | 0 | 4,9 | 0 | 2 | 1 | 12 | +| 203 | B4 | 4 | 0 | 4 | 0 | 2 | 1 | 12 | +| 204 | B4 | 4 | 1 | 4,9 | 0 | 2 | 1 | 12 | +| 205 | B4 | 2 | 0 | 4,9 | 0 | 2 | 1 | 12 | +| 206 | B4 | 2 | 0 | 1 | 0 | 2 | 1 | 12 | +| 207 | B4 | 2 | 0 | 4 | 0 | 2 | 1 | 12 | +| 208 | B4 | 2 | 0 | 7 | 0 | 2 | 1 | 12 | +| 209 | B4 | 1 | 0 | 1 | 0 | 2 | 1 | 12 | +| 210 | B4 | 1 | 0 | 4 | 0 | 2 | 1 | 12 | +| 211 | B4 | 1 | 0 | 7 | 0 | 2 | 1 | 12 | +| 212 | B4 | 1 | 0 | 1,6 | 0 | 2 | 1 | 12 | +| 213 | B4 | 1 | 0 | 2,7 | 0 | 2 | 1 | 12 | +| 214 | B4 | 1 | 0 | 4,9 | 0 | 2 | 1 | 12 | +| 215 | B4 | 1 | 0 | 1,4,7 | 0 | 2 | 1 | 12 | +| 216 | B4 | 1 | 0 | 0,2,4,6,8 | 0 | 2 | 1 | 12 | +| 217 | B4 | 1 | 0 | 0,1,2,3,4,5,6,7,8,9 | 0 | 2 | 1 | 12 | +| 218 | B4 | 1 | 0 | 1,3,5,7,9 | 0 | 2 | 1 | 12 | +| 219 | C0 | 8 | 1 | 4 | 0 | 2 | 7 | 2 | +| 220 | C0 | 4 | 1 | 4,9 | 0 | 1 | 7 | 2 | +| 221 | C0 | 4 | 0 | 4 | 0 | 2 | 7 | 2 | +| 222 | C0 | 2 | 0 | 4,9 | 0 | 1 | 7 | 2 | +| 223 | C0 | 2 | 0 | 1 | 0 | 2 | 7 | 2 | +| 224 | C0 | 2 | 0 | 4 | 0 | 2 | 7 | 2 | +| 225 | C0 | 2 | 0 | 7 | 0 | 2 | 7 | 2 | +| 226 | C0 | 1 | 0 | 4 | 0 | 1 | 7 | 2 | +| 227 | C0 | 1 | 0 | 1,6 | 0 | 1 | 7 | 2 | +| 228 | C0 | 1 | 0 | 4,9 | 0 | 1 | 7 | 2 | +| 229 | C0 | 1 | 0 | 1 | 0 | 2 | 7 | 2 | +| 230 | C0 | 1 | 0 | 7 | 0 | 2 | 7 | 2 | +| 231 | C0 | 1 | 0 | 2,7 | 0 | 2 | 7 | 2 | +| 232 | C0 | 1 | 0 | 1,4,7 | 0 | 2 | 7 | 2 | +| 233 | C0 | 1 | 0 | 0,2,4,6,8 | 0 | 2 | 7 | 2 | +| 234 | C0 | 1 | 0 | 0,1,2,3,4,5,6,7,8,9 | 0 | 2 | 7 | 2 | +| 235 | C0 | 1 | 0 | 1,3,5,7,9 | 0 | 2 | 7 | 2 | +| 236 | C2 | 16 | 1 | 4,9 | 0 | 1 | 2 | 6 | +| 237 | C2 | 16 | 1 | 4 | 0 | 2 | 2 | 6 | +| 238 | C2 | 8 | 1 | 4,9 | 0 | 1 | 2 | 6 | +| 239 | C2 | 8 | 1 | 4 | 0 | 2 | 2 | 6 | +| 240 | C2 | 4 | 0 | 4,9 | 0 | 1 | 2 | 6 | +| 241 | C2 | 4 | 0 | 4 | 0 | 2 | 2 | 6 | +| 242 | C2 | 2 | 1 | 2,6,9 | 0 | 2 | 2 | 6 | +| 243 | C2 | 2 | 0 | 1 | 0 | 2 | 2 | 6 | +| 244 | C2 | 2 | 0 | 4 | 0 | 2 | 2 | 6 | +| 245 | C2 | 2 | 0 | 7 | 0 | 2 | 2 | 6 | +| 246 | C2 | 1 | 0 | 4 | 0 | 1 | 2 | 6 | +| 247 | C2 | 1 | 0 | 1,6 | 0 | 1 | 2 | 6 | +| 248 | C2 | 1 | 0 | 4,9 | 0 | 1 | 2 | 6 | +| 249 | C2 | 1 | 0 | 1 | 0 | 2 | 2 | 6 | +| 250 | C2 | 1 | 0 | 7 | 0 | 2 | 2 | 6 | + +| | | | | | | | | | +|-----|----|---|---|---------------------|---|---|---|---| +| 251 | C2 | 1 | 0 | 2,7 | 0 | 2 | 2 | 6 | +| 252 | C2 | 1 | 0 | 1,4,7 | 0 | 2 | 2 | 6 | +| 253 | C2 | 1 | 0 | 0,2,4,6,8 | 0 | 2 | 2 | 6 | +| 254 | C2 | 1 | 0 | 0,1,2,3,4,5,6,7,8,9 | 0 | 2 | 2 | 6 | +| 255 | C2 | 1 | 0 | 1,3,5,7,9 | 0 | 2 | 2 | 6 | + +**Table 6.3.3.2-3: Random access configurations for FR1 and unpaired spectrum.** + +| PRACH | Preamble | | Subframe number | Starting | Number | | | +|-------|----------|--|-----------------|----------|--------|--|--| +|-------|----------|--|-----------------|----------|--------|--|--| + +| Configuration Index | e format | $x$ | $y$ | | symbol | of PRACH slots within a subframe | $N_t^{\text{RA,slot}}$ , number of time-domain PRACH occasions within a PRACH slot | $N_{\text{dur}}^{\text{RA}}$ , PRACH duration | +|---------------------|----------|-----|-----|-----------|--------|----------------------------------|------------------------------------------------------------------------------------|-----------------------------------------------| +| | | | | | | | | | +| 0 | 0 | 16 | 1 | 9 | 0 | - | - | 0 | +| 1 | 0 | 8 | 1 | 9 | 0 | - | - | 0 | +| 2 | 0 | 4 | 1 | 9 | 0 | - | - | 0 | +| 3 | 0 | 2 | 0 | 9 | 0 | - | - | 0 | +| 4 | 0 | 2 | 1 | 9 | 0 | - | - | 0 | +| 5 | 0 | 2 | 0 | 4 | 0 | - | - | 0 | +| 6 | 0 | 2 | 1 | 4 | 0 | - | - | 0 | +| 7 | 0 | 1 | 0 | 9 | 0 | - | - | 0 | +| 8 | 0 | 1 | 0 | 8 | 0 | - | - | 0 | +| 9 | 0 | 1 | 0 | 7 | 0 | - | - | 0 | +| 10 | 0 | 1 | 0 | 6 | 0 | - | - | 0 | +| 11 | 0 | 1 | 0 | 5 | 0 | - | - | 0 | +| 12 | 0 | 1 | 0 | 4 | 0 | - | - | 0 | +| 13 | 0 | 1 | 0 | 3 | 0 | - | - | 0 | +| 14 | 0 | 1 | 0 | 2 | 0 | - | - | 0 | +| 15 | 0 | 1 | 0 | 1,6 | 0 | - | - | 0 | +| 16 | 0 | 1 | 0 | 1,6 | 7 | - | - | 0 | +| 17 | 0 | 1 | 0 | 4,9 | 0 | - | - | 0 | +| 18 | 0 | 1 | 0 | 3,8 | 0 | - | - | 0 | +| 19 | 0 | 1 | 0 | 2,7 | 0 | - | - | 0 | +| 20 | 0 | 1 | 0 | 8,9 | 0 | - | - | 0 | +| 21 | 0 | 1 | 0 | 4,8,9 | 0 | - | - | 0 | +| 22 | 0 | 1 | 0 | 3,4,9 | 0 | - | - | 0 | +| 23 | 0 | 1 | 0 | 7,8,9 | 0 | - | - | 0 | +| 24 | 0 | 1 | 0 | 3,4,8,9 | 0 | - | - | 0 | +| 25 | 0 | 1 | 0 | 6,7,8,9 | 0 | - | - | 0 | +| 26 | 0 | 1 | 0 | 1,4,6,9 | 0 | - | - | 0 | +| 27 | 0 | 1 | 0 | 1,3,5,7,9 | 0 | - | - | 0 | +| 28 | 1 | 16 | 1 | 7 | 0 | - | - | 0 | +| 29 | 1 | 8 | 1 | 7 | 0 | - | - | 0 | +| 30 | 1 | 4 | 1 | 7 | 0 | - | - | 0 | +| 31 | 1 | 2 | 0 | 7 | 0 | - | - | 0 | +| 32 | 1 | 2 | 1 | 7 | 0 | - | - | 0 | +| 33 | 1 | 1 | 0 | 7 | 0 | - | - | 0 | +| 34 | 2 | 16 | 1 | 6 | 0 | - | - | 0 | +| 35 | 2 | 8 | 1 | 6 | 0 | - | - | 0 | +| 36 | 2 | 4 | 1 | 6 | 0 | - | - | 0 | +| 37 | 2 | 2 | 0 | 6 | 7 | - | - | 0 | +| 38 | 2 | 2 | 1 | 6 | 7 | - | - | 0 | +| 39 | 2 | 1 | 0 | 6 | 7 | - | - | 0 | +| 40 | 3 | 16 | 1 | 9 | 0 | - | - | 0 | +| 41 | 3 | 8 | 1 | 9 | 0 | - | - | 0 | +| 42 | 3 | 4 | 1 | 9 | 0 | - | - | 0 | +| 43 | 3 | 2 | 0 | 9 | 0 | - | - | 0 | +| 44 | 3 | 2 | 1 | 9 | 0 | - | - | 0 | +| 45 | 3 | 2 | 0 | 4 | 0 | - | - | 0 | +| 46 | 3 | 2 | 1 | 4 | 0 | - | - | 0 | +| 47 | 3 | 1 | 0 | 9 | 0 | - | - | 0 | +| 48 | 3 | 1 | 0 | 8 | 0 | - | - | 0 | +| 49 | 3 | 1 | 0 | 7 | 0 | - | - | 0 | +| 50 | 3 | 1 | 0 | 6 | 0 | - | - | 0 | +| 51 | 3 | 1 | 0 | 5 | 0 | - | - | 0 | +| 52 | 3 | 1 | 0 | 4 | 0 | - | - | 0 | +| 53 | 3 | 1 | 0 | 3 | 0 | - | - | 0 | +| 54 | 3 | 1 | 0 | 2 | 0 | - | - | 0 | +| 55 | 3 | 1 | 0 | 1,6 | 0 | - | - | 0 | + +| | | | | | | | | | +|-----|----|----|---|---------------------|---|---|---|---| +| 56 | 3 | 1 | 0 | 1,6 | 7 | - | - | 0 | +| 57 | 3 | 1 | 0 | 4,9 | 0 | - | - | 0 | +| 58 | 3 | 1 | 0 | 3,8 | 0 | - | - | 0 | +| 59 | 3 | 1 | 0 | 2,7 | 0 | - | - | 0 | +| 60 | 3 | 1 | 0 | 8,9 | 0 | - | - | 0 | +| 61 | 3 | 1 | 0 | 4,8,9 | 0 | - | - | 0 | +| 62 | 3 | 1 | 0 | 3,4,9 | 0 | - | - | 0 | +| 63 | 3 | 1 | 0 | 7,8,9 | 0 | - | - | 0 | +| 64 | 3 | 1 | 0 | 3,4,8,9 | 0 | - | - | 0 | +| 65 | 3 | 1 | 0 | 1,4,6,9 | 0 | - | - | 0 | +| 66 | 3 | 1 | 0 | 1,3,5,7,9 | 0 | - | - | 0 | +| 67 | A1 | 16 | 1 | 9 | 0 | 2 | 6 | 2 | +| 68 | A1 | 8 | 1 | 9 | 0 | 2 | 6 | 2 | +| 69 | A1 | 4 | 1 | 9 | 0 | 1 | 6 | 2 | +| 70 | A1 | 2 | 1 | 9 | 0 | 1 | 6 | 2 | +| 71 | A1 | 2 | 1 | 4,9 | 7 | 1 | 3 | 2 | +| 72 | A1 | 2 | 1 | 7,9 | 7 | 1 | 3 | 2 | +| 73 | A1 | 2 | 1 | 7,9 | 0 | 1 | 6 | 2 | +| 74 | A1 | 2 | 1 | 8,9 | 0 | 2 | 6 | 2 | +| 75 | A1 | 2 | 1 | 4,9 | 0 | 2 | 6 | 2 | +| 76 | A1 | 2 | 1 | 2,3,4,7,8,9 | 0 | 1 | 6 | 2 | +| 77 | A1 | 1 | 0 | 9 | 0 | 2 | 6 | 2 | +| 78 | A1 | 1 | 0 | 9 | 7 | 1 | 3 | 2 | +| 79 | A1 | 1 | 0 | 9 | 0 | 1 | 6 | 2 | +| 80 | A1 | 1 | 0 | 8,9 | 0 | 2 | 6 | 2 | +| 81 | A1 | 1 | 0 | 4,9 | 0 | 1 | 6 | 2 | +| 82 | A1 | 1 | 0 | 7,9 | 7 | 1 | 3 | 2 | +| 83 | A1 | 1 | 0 | 3,4,8,9 | 0 | 1 | 6 | 2 | +| 84 | A1 | 1 | 0 | 3,4,8,9 | 0 | 2 | 6 | 2 | +| 85 | A1 | 1 | 0 | 1,3,5,7,9 | 0 | 1 | 6 | 2 | +| 86 | A1 | 1 | 0 | 0,1,2,3,4,5,6,7,8,9 | 7 | 1 | 3 | 2 | +| 87 | A2 | 16 | 1 | 9 | 0 | 2 | 3 | 4 | +| 88 | A2 | 8 | 1 | 9 | 0 | 2 | 3 | 4 | +| 89 | A2 | 4 | 1 | 9 | 0 | 1 | 3 | 4 | +| 90 | A2 | 2 | 1 | 7,9 | 0 | 1 | 3 | 4 | +| 91 | A2 | 2 | 1 | 8,9 | 0 | 2 | 3 | 4 | +| 92 | A2 | 2 | 1 | 7,9 | 9 | 1 | 1 | 4 | +| 93 | A2 | 2 | 1 | 4,9 | 9 | 1 | 1 | 4 | +| 94 | A2 | 2 | 1 | 4,9 | 0 | 2 | 3 | 4 | +| 95 | A2 | 2 | 1 | 2,3,4,7,8,9 | 0 | 1 | 3 | 4 | +| 96 | A2 | 1 | 0 | 2 | 0 | 1 | 3 | 4 | +| 97 | A2 | 1 | 0 | 7 | 0 | 1 | 3 | 4 | +| 98 | A2 | 2 | 1 | 9 | 0 | 1 | 3 | 4 | +| 99 | A2 | 1 | 0 | 9 | 0 | 2 | 3 | 4 | +| 100 | A2 | 1 | 0 | 9 | 9 | 1 | 1 | 4 | +| 101 | A2 | 1 | 0 | 9 | 0 | 1 | 3 | 4 | +| 102 | A2 | 1 | 0 | 2,7 | 0 | 1 | 3 | 4 | +| 103 | A2 | 1 | 0 | 8,9 | 0 | 2 | 3 | 4 | +| 104 | A2 | 1 | 0 | 4,9 | 0 | 1 | 3 | 4 | +| 105 | A2 | 1 | 0 | 7,9 | 9 | 1 | 1 | 4 | +| 106 | A2 | 1 | 0 | 3,4,8,9 | 0 | 1 | 3 | 4 | +| 107 | A2 | 1 | 0 | 3,4,8,9 | 0 | 2 | 3 | 4 | +| 108 | A2 | 1 | 0 | 1,3,5,7,9 | 0 | 1 | 3 | 4 | +| 109 | A2 | 1 | 0 | 0,1,2,3,4,5,6,7,8,9 | 9 | 1 | 1 | 4 | +| 110 | A3 | 16 | 1 | 9 | 0 | 2 | 2 | 6 | +| 111 | A3 | 8 | 1 | 9 | 0 | 2 | 2 | 6 | +| 112 | A3 | 4 | 1 | 9 | 0 | 1 | 2 | 6 | +| 113 | A3 | 2 | 1 | 4,9 | 7 | 1 | 1 | 6 | +| 114 | A3 | 2 | 1 | 7,9 | 7 | 1 | 1 | 6 | +| 115 | A3 | 2 | 1 | 7,9 | 0 | 1 | 2 | 6 | +| 116 | A3 | 2 | 1 | 4,9 | 0 | 2 | 2 | 6 | +| 117 | A3 | 2 | 1 | 8,9 | 0 | 2 | 2 | 6 | +| 118 | A3 | 2 | 1 | 2,3,4,7,8,9 | 0 | 1 | 2 | 6 | +| 119 | A3 | 1 | 0 | 2 | 0 | 1 | 2 | 6 | +| 120 | A3 | 1 | 0 | 7 | 0 | 1 | 2 | 6 | + +| | | | | | | | | | +|-----|----|----|---|---------------------|---|---|---|----| +| 121 | A3 | 2 | 1 | 9 | 0 | 1 | 2 | 6 | +| 122 | A3 | 1 | 0 | 9 | 0 | 2 | 2 | 6 | +| 123 | A3 | 1 | 0 | 9 | 7 | 1 | 1 | 6 | +| 124 | A3 | 1 | 0 | 9 | 0 | 1 | 2 | 6 | +| 125 | A3 | 1 | 0 | 2,7 | 0 | 1 | 2 | 6 | +| 126 | A3 | 1 | 0 | 8,9 | 0 | 2 | 2 | 6 | +| 127 | A3 | 1 | 0 | 4,9 | 0 | 1 | 2 | 6 | +| 128 | A3 | 1 | 0 | 7,9 | 7 | 1 | 1 | 6 | +| 129 | A3 | 1 | 0 | 3,4,8,9 | 0 | 1 | 2 | 6 | +| 130 | A3 | 1 | 0 | 3,4,8,9 | 0 | 2 | 2 | 6 | +| 131 | A3 | 1 | 0 | 1,3,5,7,9 | 0 | 1 | 2 | 6 | +| 132 | A3 | 1 | 0 | 0,1,2,3,4,5,6,7,8,9 | 7 | 1 | 1 | 6 | +| 133 | B1 | 4 | 1 | 9 | 2 | 1 | 6 | 2 | +| 134 | B1 | 2 | 1 | 9 | 2 | 1 | 6 | 2 | +| 135 | B1 | 2 | 1 | 7,9 | 2 | 1 | 6 | 2 | +| 136 | B1 | 2 | 1 | 4,9 | 8 | 1 | 3 | 2 | +| 137 | B1 | 2 | 1 | 4,9 | 2 | 2 | 6 | 2 | +| 138 | B1 | 1 | 0 | 9 | 2 | 2 | 6 | 2 | +| 139 | B1 | 1 | 0 | 9 | 8 | 1 | 3 | 2 | +| 140 | B1 | 1 | 0 | 9 | 2 | 1 | 6 | 2 | +| 141 | B1 | 1 | 0 | 8,9 | 2 | 2 | 6 | 2 | +| 142 | B1 | 1 | 0 | 4,9 | 2 | 1 | 6 | 2 | +| 143 | B1 | 1 | 0 | 7,9 | 8 | 1 | 3 | 2 | +| 144 | B1 | 1 | 0 | 1,3,5,7,9 | 2 | 1 | 6 | 2 | +| 145 | B4 | 16 | 1 | 9 | 0 | 2 | 1 | 12 | +| 146 | B4 | 8 | 1 | 9 | 0 | 2 | 1 | 12 | +| 147 | B4 | 4 | 1 | 9 | 2 | 1 | 1 | 12 | +| 148 | B4 | 2 | 1 | 9 | 0 | 1 | 1 | 12 | +| 149 | B4 | 2 | 1 | 9 | 2 | 1 | 1 | 12 | +| 150 | B4 | 2 | 1 | 7,9 | 2 | 1 | 1 | 12 | +| 151 | B4 | 2 | 1 | 4,9 | 2 | 1 | 1 | 12 | +| 152 | B4 | 2 | 1 | 4,9 | 0 | 2 | 1 | 12 | +| 153 | B4 | 2 | 1 | 8,9 | 0 | 2 | 1 | 12 | +| 154 | B4 | 2 | 1 | 2,3,4,7,8,9 | 0 | 1 | 1 | 12 | +| 155 | B4 | 1 | 0 | 1 | 0 | 1 | 1 | 12 | +| 156 | B4 | 1 | 0 | 2 | 0 | 1 | 1 | 12 | +| 157 | B4 | 1 | 0 | 4 | 0 | 1 | 1 | 12 | +| 158 | B4 | 1 | 0 | 7 | 0 | 1 | 1 | 12 | +| 159 | B4 | 1 | 0 | 9 | 0 | 1 | 1 | 12 | +| 160 | B4 | 1 | 0 | 9 | 2 | 1 | 1 | 12 | +| 161 | B4 | 1 | 0 | 9 | 0 | 2 | 1 | 12 | +| 162 | B4 | 1 | 0 | 4,9 | 2 | 1 | 1 | 12 | +| 163 | B4 | 1 | 0 | 7,9 | 2 | 1 | 1 | 12 | +| 164 | B4 | 1 | 0 | 8,9 | 0 | 2 | 1 | 12 | +| 165 | B4 | 1 | 0 | 3,4,8,9 | 2 | 1 | 1 | 12 | +| 166 | B4 | 1 | 0 | 1,3,5,7,9 | 2 | 1 | 1 | 12 | +| 167 | B4 | 1 | 0 | 0,1,2,3,4,5,6,7,8,9 | 0 | 2 | 1 | 12 | +| 168 | B4 | 1 | 0 | 0,1,2,3,4,5,6,7,8,9 | 2 | 1 | 1 | 12 | +| 169 | C0 | 16 | 1 | 9 | 2 | 2 | 6 | 2 | +| 170 | C0 | 8 | 1 | 9 | 2 | 2 | 6 | 2 | +| 171 | C0 | 4 | 1 | 9 | 2 | 1 | 6 | 2 | +| 172 | C0 | 2 | 1 | 9 | 2 | 1 | 6 | 2 | +| 173 | C0 | 2 | 1 | 8,9 | 2 | 2 | 6 | 2 | +| 174 | C0 | 2 | 1 | 7,9 | 2 | 1 | 6 | 2 | +| 175 | C0 | 2 | 1 | 7,9 | 8 | 1 | 3 | 2 | +| 176 | C0 | 2 | 1 | 4,9 | 8 | 1 | 3 | 2 | +| 177 | C0 | 2 | 1 | 4,9 | 2 | 2 | 6 | 2 | +| 178 | C0 | 2 | 1 | 2,3,4,7,8,9 | 2 | 1 | 6 | 2 | +| 179 | C0 | 1 | 0 | 9 | 2 | 2 | 6 | 2 | +| 180 | C0 | 1 | 0 | 9 | 8 | 1 | 3 | 2 | +| 181 | C0 | 1 | 0 | 9 | 2 | 1 | 6 | 2 | +| 182 | C0 | 1 | 0 | 8,9 | 2 | 2 | 6 | 2 | +| 183 | C0 | 1 | 0 | 4,9 | 2 | 1 | 6 | 2 | +| 184 | C0 | 1 | 0 | 7,9 | 8 | 1 | 3 | 2 | +| 185 | C0 | 1 | 0 | 3,4,8,9 | 2 | 1 | 6 | 2 | + +| | | | | | | | | | +|-----|-------|----|---|---------------------|---|---|---|---| +| 186 | C0 | 1 | 0 | 3,4,8,9 | 2 | 2 | 6 | 2 | +| 187 | C0 | 1 | 0 | 1,3,5,7,9 | 2 | 1 | 6 | 2 | +| 188 | C0 | 1 | 0 | 0,1,2,3,4,5,6,7,8,9 | 8 | 1 | 3 | 2 | +| 189 | C2 | 16 | 1 | 9 | 2 | 2 | 2 | 6 | +| 190 | C2 | 8 | 1 | 9 | 2 | 2 | 2 | 6 | +| 191 | C2 | 4 | 1 | 9 | 2 | 1 | 2 | 6 | +| 192 | C2 | 2 | 1 | 9 | 2 | 1 | 2 | 6 | +| 193 | C2 | 2 | 1 | 8,9 | 2 | 2 | 2 | 6 | +| 194 | C2 | 2 | 1 | 7,9 | 2 | 1 | 2 | 6 | +| 195 | C2 | 2 | 1 | 7,9 | 8 | 1 | 1 | 6 | +| 196 | C2 | 2 | 1 | 4,9 | 8 | 1 | 1 | 6 | +| 197 | C2 | 2 | 1 | 4,9 | 2 | 2 | 2 | 6 | +| 198 | C2 | 2 | 1 | 2,3,4,7,8,9 | 2 | 1 | 2 | 6 | +| 199 | C2 | 8 | 1 | 9 | 8 | 2 | 1 | 6 | +| 200 | C2 | 4 | 1 | 9 | 8 | 1 | 1 | 6 | +| 201 | C2 | 1 | 0 | 9 | 2 | 2 | 2 | 6 | +| 202 | C2 | 1 | 0 | 9 | 8 | 1 | 1 | 6 | +| 203 | C2 | 1 | 0 | 9 | 2 | 1 | 2 | 6 | +| 204 | C2 | 1 | 0 | 8,9 | 2 | 2 | 2 | 6 | +| 205 | C2 | 1 | 0 | 4,9 | 2 | 1 | 2 | 6 | +| 206 | C2 | 1 | 0 | 7,9 | 8 | 1 | 1 | 6 | +| 207 | C2 | 1 | 0 | 3,4,8,9 | 2 | 1 | 2 | 6 | +| 208 | C2 | 1 | 0 | 3,4,8,9 | 2 | 2 | 2 | 6 | +| 209 | C2 | 1 | 0 | 1,3,5,7,9 | 2 | 1 | 2 | 6 | +| 210 | C2 | 1 | 0 | 0,1,2,3,4,5,6,7,8,9 | 8 | 1 | 1 | 6 | +| 211 | A1/B1 | 2 | 1 | 9 | 2 | 1 | 6 | 2 | +| 212 | A1/B1 | 2 | 1 | 4,9 | 8 | 1 | 3 | 2 | +| 213 | A1/B1 | 2 | 1 | 7,9 | 8 | 1 | 3 | 2 | +| 214 | A1/B1 | 2 | 1 | 7,9 | 2 | 1 | 6 | 2 | +| 215 | A1/B1 | 2 | 1 | 4,9 | 2 | 2 | 6 | 2 | +| 216 | A1/B1 | 2 | 1 | 8,9 | 2 | 2 | 6 | 2 | +| 217 | A1/B1 | 1 | 0 | 9 | 2 | 2 | 6 | 2 | +| 218 | A1/B1 | 1 | 0 | 9 | 8 | 1 | 3 | 2 | +| 219 | A1/B1 | 1 | 0 | 9 | 2 | 1 | 6 | 2 | +| 220 | A1/B1 | 1 | 0 | 8,9 | 2 | 2 | 6 | 2 | +| 221 | A1/B1 | 1 | 0 | 4,9 | 2 | 1 | 6 | 2 | +| 222 | A1/B1 | 1 | 0 | 7,9 | 8 | 1 | 3 | 2 | +| 223 | A1/B1 | 1 | 0 | 3,4,8,9 | 2 | 2 | 6 | 2 | +| 224 | A1/B1 | 1 | 0 | 1,3,5,7,9 | 2 | 1 | 6 | 2 | +| 225 | A1/B1 | 1 | 0 | 0,1,2,3,4,5,6,7,8,9 | 8 | 1 | 3 | 2 | +| 226 | A2/B2 | 2 | 1 | 9 | 0 | 1 | 3 | 4 | +| 227 | A2/B2 | 2 | 1 | 4,9 | 6 | 1 | 2 | 4 | +| 228 | A2/B2 | 2 | 1 | 7,9 | 6 | 1 | 2 | 4 | +| 229 | A2/B2 | 2 | 1 | 4,9 | 0 | 2 | 3 | 4 | +| 230 | A2/B2 | 2 | 1 | 8,9 | 0 | 2 | 3 | 4 | +| 231 | A2/B2 | 1 | 0 | 9 | 0 | 2 | 3 | 4 | +| 232 | A2/B2 | 1 | 0 | 9 | 6 | 1 | 2 | 4 | +| 233 | A2/B2 | 1 | 0 | 9 | 0 | 1 | 3 | 4 | +| 234 | A2/B2 | 1 | 0 | 8,9 | 0 | 2 | 3 | 4 | +| 235 | A2/B2 | 1 | 0 | 4,9 | 0 | 1 | 3 | 4 | +| 236 | A2/B2 | 1 | 0 | 7,9 | 6 | 1 | 2 | 4 | +| 237 | A2/B2 | 1 | 0 | 3,4,8,9 | 0 | 1 | 3 | 4 | +| 238 | A2/B2 | 1 | 0 | 3,4,8,9 | 0 | 2 | 3 | 4 | +| 239 | A2/B2 | 1 | 0 | 1,3,5,7,9 | 0 | 1 | 3 | 4 | +| 240 | A2/B2 | 1 | 0 | 0,1,2,3,4,5,6,7,8,9 | 6 | 1 | 2 | 4 | +| 241 | A3/B3 | 2 | 1 | 9 | 0 | 1 | 2 | 6 | +| 242 | A3/B3 | 2 | 1 | 4,9 | 2 | 1 | 2 | 6 | +| 243 | A3/B3 | 2 | 1 | 7,9 | 0 | 1 | 2 | 6 | +| 244 | A3/B3 | 2 | 1 | 7,9 | 2 | 1 | 2 | 6 | +| 245 | A3/B3 | 2 | 1 | 4,9 | 0 | 2 | 2 | 6 | +| 246 | A3/B3 | 2 | 1 | 8,9 | 0 | 2 | 2 | 6 | +| 247 | A3/B3 | 1 | 0 | 9 | 0 | 2 | 2 | 6 | +| 248 | A3/B3 | 1 | 0 | 9 | 2 | 1 | 2 | 6 | +| 249 | A3/B3 | 1 | 0 | 9 | 0 | 1 | 2 | 6 | +| 250 | A3/B3 | 1 | 0 | 8,9 | 0 | 2 | 2 | 6 | + +| | | | | | | | | | +|-----|-------|----|---|---------------------|---|---|---|---| +| 251 | A3/B3 | 1 | 0 | 4,9 | 0 | 1 | 2 | 6 | +| 252 | A3/B3 | 1 | 0 | 7,9 | 2 | 1 | 2 | 6 | +| 253 | A3/B3 | 1 | 0 | 3,4,8,9 | 0 | 2 | 2 | 6 | +| 254 | A3/B3 | 1 | 0 | 1,3,5,7,9 | 0 | 1 | 2 | 6 | +| 255 | A3/B3 | 1 | 0 | 0,1,2,3,4,5,6,7,8,9 | 2 | 1 | 2 | 6 | +| 256 | 0 | 16 | 1 | 7 | 0 | - | - | 0 | +| 257 | 0 | 8 | 1 | 7 | 0 | - | - | 0 | +| 258 | 0 | 4 | 1 | 7 | 0 | - | - | 0 | +| 259 | 0 | 2 | 0 | 7 | 0 | - | - | 0 | +| 260 | 0 | 2 | 1 | 7 | 0 | - | - | 0 | +| 261 | 0 | 2 | 0 | 2 | 0 | - | - | 0 | +| 262 | 0 | 2 | 1 | 2 | 0 | - | - | 0 | + +**Table 6.3.3.2-4: Random access configurations for FR2 and unpaired spectrum.** + +| PRACH | Preamble | | Slot number | Starting | Number | | | +|--------------|-----------------|--|--------------------|-----------------|---------------|--|--| +|--------------|-----------------|--|--------------------|-----------------|---------------|--|--| + +| Config. Index | format | $x$ | $y$ | | symbol | of PRACH slots within a 60 kHz slot | $N_t^{\text{RA,slot}}$ , | $N_{\text{dur}}^{\text{RA}}$ , | +|---------------|--------|-----|-----|-----------------------------|--------|-------------------------------------|-----------------------------------------------------------|--------------------------------| +| | | | | | | | number of time-domain PRACH occasions within a PRACH slot | PRACH duration | +| 0 | A1 | 16 | 1 | 4,9,14,19,24,29,34,39 | 0 | 2 | 6 | 2 | +| 1 | A1 | 16 | 1 | 3,7,11,15,19,23,27,31,35,39 | 0 | 1 | 6 | 2 | +| 2 | A1 | 8 | 1,2 | 9,19,29,39 | 0 | 2 | 6 | 2 | +| 3 | A1 | 8 | 1 | 4,9,14,19,24,29,34,39 | 0 | 2 | 6 | 2 | +| 4 | A1 | 8 | 1 | 3,7,11,15,19,23,27,31,35,39 | 0 | 1 | 6 | 2 | +| 5 | A1 | 4 | 1 | 4,9,14,19,24,29,34,39 | 0 | 1 | 6 | 2 | +| 6 | A1 | 4 | 1 | 4,9,14,19,24,29,34,39 | 0 | 2 | 6 | 2 | +| 7 | A1 | 4 | 1 | 3,7,11,15,19,23,27,31,35,39 | 0 | 1 | 6 | 2 | +| 8 | A1 | 2 | 1 | 7,15,23,31,39 | 0 | 2 | 6 | 2 | +| 9 | A1 | 2 | 1 | 4,9,14,19,24,29,34,39 | 0 | 1 | 6 | 2 | +| 10 | A1 | 2 | 1 | 4,9,14,19,24,29,34,39 | 0 | 2 | 6 | 2 | +| 11 | A1 | 2 | 1 | 3,7,11,15,19,23,27,31,35,39 | 0 | 1 | 6 | 2 | +| 12 | A1 | 1 | 0 | 19,39 | 7 | 1 | 3 | 2 | +| 13 | A1 | 1 | 0 | 3,5,7 | 0 | 1 | 6 | 2 | +| 14 | A1 | 1 | 0 | 24,29,34,39 | 7 | 1 | 3 | 2 | +| 15 | A1 | 1 | 0 | 9,19,29,39 | 7 | 2 | 3 | 2 | +| 16 | A1 | 1 | 0 | 17,19,37,39 | 0 | 1 | 6 | 2 | +| 17 | A1 | 1 | 0 | 9,19,29,39 | 0 | 2 | 6 | 2 | +| 18 | A1 | 1 | 0 | 4,9,14,19,24,29,34,39 | 0 | 1 | 6 | 2 | +| 19 | A1 | 1 | 0 | 4,9,14,19,24,29,34,39 | 7 | 1 | 3 | 2 | +| 20 | A1 | 1 | 0 | 3,5,7,9,11,13 | 7 | 1 | 3 | 2 | +| 21 | A1 | 1 | 0 | 23,27,31,35,39 | 7 | 1 | 3 | 2 | +| 22 | A1 | 1 | 0 | 7,15,23,31,39 | 0 | 1 | 6 | 2 | +| 23 | A1 | 1 | 0 | 23,27,31,35,39 | 0 | 1 | 6 | 2 | +| 24 | A1 | 1 | 0 | 13,14,15, 29,30,31,37,38,39 | 7 | 2 | 3 | 2 | +| 25 | A1 | 1 | 0 | 3,7,11,15,19,23,27,31,35,39 | 7 | 1 | 3 | 2 | +| 26 | A1 | 1 | 0 | 3,7,11,15,19,23,27,31,35,39 | 0 | 1 | 6 | 2 | +| 27 | A1 | 1 | 0 | 1,3,5,7, ...,37,39 | 0 | 1 | 6 | 2 | +| 28 | A1 | 1 | 0 | 0,1,2, ...,39 | 7 | 1 | 3 | 2 | +| 29 | A2 | 16 | 1 | 4,9,14,19,24,29,34,39 | 0 | 2 | 3 | 4 | +| 30 | A2 | 16 | 1 | 3,7,11,15,19,23,27,31,35,39 | 0 | 1 | 3 | 4 | +| 31 | A2 | 8 | 1 | 4,9,14,19,24,29,34,39 | 0 | 2 | 3 | 4 | +| 32 | A2 | 8 | 1 | 3,7,11,15,19,23,27,31,35,39 | 0 | 1 | 3 | 4 | +| 33 | A2 | 8 | 1,2 | 9,19,29,39 | 0 | 2 | 3 | 4 | +| 34 | A2 | 4 | 1 | 4,9,14,19,24,29,34,39 | 0 | 1 | 3 | 4 | +| 35 | A2 | 4 | 1 | 4,9,14,19,24,29,34,39 | 0 | 2 | 3 | 4 | +| 36 | A2 | 4 | 1 | 3,7,11,15,19,23,27,31,35,39 | 0 | 1 | 3 | 4 | +| 37 | A2 | 2 | 1 | 7,15,23,31,39 | 0 | 2 | 3 | 4 | +| 38 | A2 | 2 | 1 | 4,9,14,19,24,29,34,39 | 0 | 1 | 3 | 4 | +| 39 | A2 | 2 | 1 | 4,9,14,19,24,29,34,39 | 0 | 2 | 3 | 4 | +| 40 | A2 | 2 | 1 | 3,7,11,15,19,23,27,31,35,39 | 0 | 1 | 3 | 4 | +| 41 | A2 | 1 | 0 | 19,39 | 5 | 1 | 2 | 4 | +| 42 | A2 | 1 | 0 | 3,5,7 | 0 | 1 | 3 | 4 | +| 43 | A2 | 1 | 0 | 24,29,34,39 | 5 | 1 | 2 | 4 | +| 44 | A2 | 1 | 0 | 9,19,29,39 | 5 | 2 | 2 | 4 | +| 45 | A2 | 1 | 0 | 17,19,37,39 | 0 | 1 | 3 | 4 | +| 46 | A2 | 1 | 0 | 9, 19, 29, 39 | 0 | 2 | 3 | 4 | +| 47 | A2 | 1 | 0 | 7,15,23,31,39 | 0 | 1 | 3 | 4 | +| 48 | A2 | 1 | 0 | 23,27,31,35,39 | 5 | 1 | 2 | 4 | +| 49 | A2 | 1 | 0 | 23,27,31,35,39 | 0 | 1 | 3 | 4 | +| 50 | A2 | 1 | 0 | 3,5,7,9,11,13 | 5 | 1 | 2 | 4 | +| 51 | A2 | 1 | 0 | 3,5,7,9,11,13 | 0 | 1 | 3 | 4 | +| 52 | A2 | 1 | 0 | 4,9,14,19,24,29,34,39 | 5 | 1 | 2 | 4 | +| 53 | A2 | 1 | 0 | 4,9,14,19,24,29,34,39 | 0 | 1 | 3 | 4 | +| 54 | A2 | 1 | 0 | 13,14,15, 29,30,31,37,38,39 | 5 | 2 | 2 | 4 | +| 55 | A2 | 1 | 0 | 3,7,11,15,19,23,27,31,35,39 | 5 | 1 | 2 | 4 | + +| | | | | | | | | | +|-----|----|----|-----|-----------------------------|---|---|---|----| +| 56 | A2 | 1 | 0 | 3,7,11,15,19,23,27,31,35,39 | 0 | 1 | 3 | 4 | +| 57 | A2 | 1 | 0 | 1,3,5,7,....,37,39 | 0 | 1 | 3 | 4 | +| 58 | A2 | 1 | 0 | 0,1,2,....,39 | 5 | 1 | 2 | 4 | +| 59 | A3 | 16 | 1 | 4,9,14,19,24,29,34,39 | 0 | 2 | 2 | 6 | +| 60 | A3 | 16 | 1 | 3,7,11,15,19,23,27,31,35,39 | 0 | 1 | 2 | 6 | +| 61 | A3 | 8 | 1 | 4,9,14,19,24,29,34,39 | 0 | 2 | 2 | 6 | +| 62 | A3 | 8 | 1 | 3,7,11,15,19,23,27,31,35,39 | 0 | 1 | 2 | 6 | +| 63 | A3 | 8 | 1,2 | 9,19,29,39 | 0 | 2 | 2 | 6 | +| 64 | A3 | 4 | 1 | 4,9,14,19,24,29,34,39 | 0 | 1 | 2 | 6 | +| 65 | A3 | 4 | 1 | 4,9,14,19,24,29,34,39 | 0 | 2 | 2 | 6 | +| 66 | A3 | 4 | 1 | 3,7,11,15,19,23,27,31,35,39 | 0 | 1 | 2 | 6 | +| 67 | A3 | 2 | 1 | 4,9,14,19,24,29,34,39 | 0 | 1 | 2 | 6 | +| 68 | A3 | 2 | 1 | 4,9,14,19,24,29,34,39 | 0 | 2 | 2 | 6 | +| 69 | A3 | 2 | 1 | 3,7,11,15,19,23,27,31,35,39 | 0 | 1 | 2 | 6 | +| 70 | A3 | 1 | 0 | 19,39 | 7 | 1 | 1 | 6 | +| 71 | A3 | 1 | 0 | 3,5,7 | 0 | 1 | 2 | 6 | +| 72 | A3 | 1 | 0 | 9,11,13 | 2 | 1 | 2 | 6 | +| 73 | A3 | 1 | 0 | 24,29,34,39 | 7 | 1 | 1 | 6 | +| 74 | A3 | 1 | 0 | 9,19,29,39 | 7 | 2 | 1 | 6 | +| 75 | A3 | 1 | 0 | 17,19,37,39 | 0 | 1 | 2 | 6 | +| 76 | A3 | 1 | 0 | 9,19,29,39 | 0 | 2 | 2 | 6 | +| 77 | A3 | 1 | 0 | 7,15,23,31,39 | 0 | 1 | 2 | 6 | +| 78 | A3 | 1 | 0 | 23,27,31,35,39 | 7 | 1 | 1 | 6 | +| 79 | A3 | 1 | 0 | 23,27,31,35,39 | 0 | 1 | 2 | 6 | +| 80 | A3 | 1 | 0 | 3,5,7,9,11,13 | 0 | 1 | 2 | 6 | +| 81 | A3 | 1 | 0 | 3,5,7,9,11,13 | 7 | 1 | 1 | 6 | +| 82 | A3 | 1 | 0 | 4,9,14,19,24,29,34,39 | 0 | 1 | 2 | 6 | +| 83 | A3 | 1 | 0 | 4,9,14,19,24,29,34,39 | 7 | 1 | 1 | 6 | +| 84 | A3 | 1 | 0 | 13,14,15, 29,30,31,37,38,39 | 7 | 2 | 1 | 6 | +| 85 | A3 | 1 | 0 | 3,7,11,15,19,23,27,31,35,39 | 7 | 1 | 1 | 6 | +| 86 | A3 | 1 | 0 | 3,7,11,15,19,23,27,31,35,39 | 0 | 1 | 2 | 6 | +| 87 | A3 | 1 | 0 | 1,3,5,7,....,37,39 | 0 | 1 | 2 | 6 | +| 88 | A3 | 1 | 0 | 0,1,2,....,39 | 7 | 1 | 1 | 6 | +| 89 | B1 | 16 | 1 | 4,9,14,19,24,29,34,39 | 2 | 2 | 6 | 2 | +| 90 | B1 | 8 | 1 | 4,9,14,19,24,29,34,39 | 2 | 2 | 6 | 2 | +| 91 | B1 | 8 | 1,2 | 9,19,29,39 | 2 | 2 | 6 | 2 | +| 92 | B1 | 4 | 1 | 4,9,14,19,24,29,34,39 | 2 | 2 | 6 | 2 | +| 93 | B1 | 2 | 1 | 4,9,14,19,24,29,34,39 | 2 | 2 | 6 | 2 | +| 94 | B1 | 2 | 1 | 3,7,11,15,19,23,27,31,35,39 | 2 | 1 | 6 | 2 | +| 95 | B1 | 1 | 0 | 19,39 | 8 | 1 | 3 | 2 | +| 96 | B1 | 1 | 0 | 3,5,7 | 2 | 1 | 6 | 2 | +| 97 | B1 | 1 | 0 | 24,29,34,39 | 8 | 1 | 3 | 2 | +| 98 | B1 | 1 | 0 | 9,19,29,39 | 8 | 2 | 3 | 2 | +| 99 | B1 | 1 | 0 | 17,19,37,39 | 2 | 1 | 6 | 2 | +| 100 | B1 | 1 | 0 | 9,19,29,39 | 2 | 2 | 6 | 2 | +| 101 | B1 | 1 | 0 | 7,15,23,31,39 | 2 | 1 | 6 | 2 | +| 102 | B1 | 1 | 0 | 23,27,31,35,39 | 8 | 1 | 3 | 2 | +| 103 | B1 | 1 | 0 | 23,27,31,35,39 | 2 | 1 | 6 | 2 | +| 104 | B1 | 1 | 0 | 3,5,7,9,11,13 | 8 | 1 | 3 | 2 | +| 105 | B1 | 1 | 0 | 4,9,14,19,24,29,34,39 | 8 | 1 | 3 | 2 | +| 106 | B1 | 1 | 0 | 4,9,14,19,24,29,34,39 | 2 | 1 | 6 | 2 | +| 107 | B1 | 1 | 0 | 3,7,11,15,19,23,27,31,35,39 | 8 | 1 | 3 | 2 | +| 108 | B1 | 1 | 0 | 13,14,15, 29,30,31,37,38,39 | 8 | 2 | 3 | 2 | +| 109 | B1 | 1 | 0 | 3,7,11,15,19,23,27,31,35,39 | 2 | 1 | 6 | 2 | +| 110 | B1 | 1 | 0 | 1,3,5,7,....,37,39 | 2 | 1 | 6 | 2 | +| 111 | B1 | 1 | 0 | 0,1,2,....,39 | 8 | 1 | 3 | 2 | +| 112 | B4 | 16 | 1,2 | 4,9,14,19,24,29,34,39 | 0 | 2 | 1 | 12 | +| 113 | B4 | 16 | 1,2 | 3,7,11,15,19,23,27,31,35,39 | 0 | 1 | 1 | 12 | +| 114 | B4 | 8 | 1,2 | 4,9,14,19,24,29,34,39 | 0 | 2 | 1 | 12 | +| 115 | B4 | 8 | 1,2 | 3,7,11,15,19,23,27,31,35,39 | 0 | 1 | 1 | 12 | +| 116 | B4 | 8 | 1,2 | 9,19,29,39 | 0 | 2 | 1 | 12 | +| 117 | B4 | 4 | 1 | 4,9,14,19,24,29,34,39 | 0 | 1 | 1 | 12 | +| 118 | B4 | 4 | 1 | 4,9,14,19,24,29,34,39 | 0 | 2 | 1 | 12 | +| 119 | B4 | 4 | 1,2 | 3,7,11,15,19,23,27,31,35,39 | 0 | 1 | 1 | 12 | +| 120 | B4 | 2 | 1 | 7,15,23,31,39 | 2 | 2 | 1 | 12 | + +| | | | | | | | | | +|-----|----|----|-----|-----------------------------|---|---|---|----| +| 121 | B4 | 2 | 1 | 4,9,14,19,24,29,34,39 | 0 | 1 | 1 | 12 | +| 122 | B4 | 2 | 1 | 4,9,14,19,24,29,34,39 | 0 | 2 | 1 | 12 | +| 123 | B4 | 2 | 1 | 3,7,11,15,19,23,27,31,35,39 | 0 | 1 | 1 | 12 | +| 124 | B4 | 1 | 0 | 19, 39 | 2 | 2 | 1 | 12 | +| 125 | B4 | 1 | 0 | 17, 19, 37, 39 | 0 | 1 | 1 | 12 | +| 126 | B4 | 1 | 0 | 24,29,34,39 | 2 | 1 | 1 | 12 | +| 127 | B4 | 1 | 0 | 9,19,29,39 | 2 | 2 | 1 | 12 | +| 128 | B4 | 1 | 0 | 9,19,29,39 | 0 | 2 | 1 | 12 | +| 129 | B4 | 1 | 0 | 7,15,23,31,39 | 0 | 1 | 1 | 12 | +| 130 | B4 | 1 | 0 | 7,15,23,31,39 | 0 | 2 | 1 | 12 | +| 131 | B4 | 1 | 0 | 23,27,31,35,39 | 0 | 1 | 1 | 12 | +| 132 | B4 | 1 | 0 | 23,27,31,35,39 | 2 | 2 | 1 | 12 | +| 133 | B4 | 1 | 0 | 9,11,13,15,17,19 | 0 | 1 | 1 | 12 | +| 134 | B4 | 1 | 0 | 3,5,7,9,11,13 | 2 | 1 | 1 | 12 | +| 135 | B4 | 1 | 0 | 4,9,14,19,24,29,34,39 | 0 | 1 | 1 | 12 | +| 136 | B4 | 1 | 0 | 4,9,14,19,24,29,34,39 | 2 | 2 | 1 | 12 | +| 137 | B4 | 1 | 0 | 13,14,15, 29,30,31,37,38,39 | 2 | 2 | 1 | 12 | +| 138 | B4 | 1 | 0 | 3,7,11,15,19,23,27,31,35,39 | 0 | 1 | 1 | 12 | +| 139 | B4 | 1 | 0 | 3,7,11,15,19,23,27,31,35,39 | 2 | 1 | 1 | 12 | +| 140 | B4 | 1 | 0 | 3, 5, 7, ..., 23,25 | 2 | 1 | 1 | 12 | +| 141 | B4 | 1 | 0 | 3, 5, 7, ..., 23,25 | 0 | 2 | 1 | 12 | +| 142 | B4 | 1 | 0 | 1,3,5,7,...,37,39 | 0 | 1 | 1 | 12 | +| 143 | B4 | 1 | 0 | 0, 1, 2, ..., 39 | 2 | 1 | 1 | 12 | +| 144 | C0 | 16 | 1 | 4,9,14,19,24,29,34,39 | 0 | 2 | 7 | 2 | +| 145 | C0 | 16 | 1 | 3,7,11,15,19,23,27,31,35,39 | 0 | 1 | 7 | 2 | +| 146 | C0 | 8 | 1 | 4,9,14,19,24,29,34,39 | 0 | 1 | 7 | 2 | +| 147 | C0 | 8 | 1 | 3,7,11,15,19,23,27,31,35,39 | 0 | 1 | 7 | 2 | +| 148 | C0 | 8 | 1,2 | 9,19,29,39 | 0 | 2 | 7 | 2 | +| 149 | C0 | 4 | 1 | 4,9,14,19,24,29,34,39 | 0 | 1 | 7 | 2 | +| 150 | C0 | 4 | 1 | 4,9,14,19,24,29,34,39 | 0 | 2 | 7 | 2 | +| 151 | C0 | 4 | 1 | 3,7,11,15,19,23,27,31,35,39 | 0 | 1 | 7 | 2 | +| 152 | C0 | 2 | 1 | 7,15,23,31,39 | 0 | 2 | 7 | 2 | +| 153 | C0 | 2 | 1 | 4,9,14,19,24,29,34,39 | 0 | 1 | 7 | 2 | +| 154 | C0 | 2 | 1 | 4,9,14,19,24,29,34,39 | 0 | 2 | 7 | 2 | +| 155 | C0 | 2 | 1 | 3,7,11,15,19,23,27,31,35,39 | 0 | 1 | 7 | 2 | +| 156 | C0 | 1 | 0 | 19,39 | 8 | 1 | 3 | 2 | +| 157 | C0 | 1 | 0 | 3,5,7 | 0 | 1 | 7 | 2 | +| 158 | C0 | 1 | 0 | 24,29,34,39 | 8 | 1 | 3 | 2 | +| 159 | C0 | 1 | 0 | 9,19,29,39 | 8 | 2 | 3 | 2 | +| 160 | C0 | 1 | 0 | 17,19,37,39 | 0 | 1 | 7 | 2 | +| 161 | C0 | 1 | 0 | 9,19,29,39 | 0 | 2 | 7 | 2 | +| 162 | C0 | 1 | 0 | 23,27,31,35,39 | 8 | 1 | 3 | 2 | +| 163 | C0 | 1 | 0 | 7,15,23,31,39 | 0 | 1 | 7 | 2 | +| 164 | C0 | 1 | 0 | 23,27,31,35,39 | 0 | 1 | 7 | 2 | +| 165 | C0 | 1 | 0 | 3,5,7,9,11,13 | 8 | 1 | 3 | 2 | +| 166 | C0 | 1 | 0 | 4,9,14,19,24,29,34,39 | 8 | 1 | 3 | 2 | +| 167 | C0 | 1 | 0 | 4,9,14,19,24,29,34,39 | 0 | 1 | 7 | 2 | +| 168 | C0 | 1 | 0 | 13,14,15, 29,30,31,37,38,39 | 8 | 2 | 3 | 2 | +| 169 | C0 | 1 | 0 | 3,7,11,15,19,23,27,31,35,39 | 8 | 1 | 3 | 2 | +| 170 | C0 | 1 | 0 | 3,7,11,15,19,23,27,31,35,39 | 0 | 1 | 7 | 2 | +| 171 | C0 | 1 | 0 | 1,3,5,7,...,37,39 | 0 | 1 | 7 | 2 | +| 172 | C0 | 1 | 0 | 0,1,2,...,39 | 8 | 1 | 3 | 2 | +| 173 | C2 | 16 | 1 | 4,9,14,19,24,29,34,39 | 0 | 2 | 2 | 6 | +| 174 | C2 | 16 | 1 | 3,7,11,15,19,23,27,31,35,39 | 0 | 1 | 2 | 6 | +| 175 | C2 | 8 | 1 | 4,9,14,19,24,29,34,39 | 0 | 2 | 2 | 6 | +| 176 | C2 | 8 | 1 | 3,7,11,15,19,23,27,31,35,39 | 0 | 1 | 2 | 6 | +| 177 | C2 | 8 | 1,2 | 9,19,29,39 | 0 | 2 | 2 | 6 | +| 178 | C2 | 4 | 1 | 4,9,14,19,24,29,34,39 | 0 | 1 | 2 | 6 | +| 179 | C2 | 4 | 1 | 4,9,14,19,24,29,34,39 | 0 | 2 | 2 | 6 | +| 180 | C2 | 4 | 1 | 3,7,11,15,19,23,27,31,35,39 | 0 | 1 | 2 | 6 | +| 181 | C2 | 2 | 1 | 7,15,23,31,39 | 2 | 2 | 2 | 6 | +| 182 | C2 | 2 | 1 | 4,9,14,19,24,29,34,39 | 0 | 1 | 2 | 6 | +| 183 | C2 | 2 | 1 | 4,9,14,19,24,29,34,39 | 0 | 2 | 2 | 6 | +| 184 | C2 | 2 | 1 | 3,7,11,15,19,23,27,31,35,39 | 0 | 1 | 2 | 6 | +| 185 | C2 | 1 | 0 | 19,39 | 2 | 1 | 2 | 6 | + +| | | | | | | | | | +|-----|-------|----|---|-----------------------------|---|---|---|---| +| 186 | C2 | 1 | 0 | 3,5,7 | 0 | 1 | 2 | 6 | +| 187 | C2 | 1 | 0 | 24,29,34,39 | 7 | 1 | 1 | 6 | +| 188 | C2 | 1 | 0 | 9,19,29,39 | 7 | 2 | 1 | 6 | +| 189 | C2 | 1 | 0 | 17,19,37,39 | 0 | 1 | 2 | 6 | +| 190 | C2 | 1 | 0 | 9,19,29,39 | 2 | 2 | 2 | 6 | +| 191 | C2 | 1 | 0 | 7,15,23,31,39 | 2 | 1 | 2 | 6 | +| 192 | C2 | 1 | 0 | 3,5,7,9,11,13 | 7 | 1 | 1 | 6 | +| 193 | C2 | 1 | 0 | 23,27,31,35,39 | 7 | 2 | 1 | 6 | +| 194 | C2 | 1 | 0 | 23,27,31,35,39 | 0 | 1 | 2 | 6 | +| 195 | C2 | 1 | 0 | 4,9,14,19,24,29,34,39 | 7 | 2 | 1 | 6 | +| 196 | C2 | 1 | 0 | 4,9,14,19,24,29,34,39 | 2 | 1 | 2 | 6 | +| 197 | C2 | 1 | 0 | 13,14,15, 29,30,31,37,38,39 | 7 | 2 | 1 | 6 | +| 198 | C2 | 1 | 0 | 3,7,11,15,19,23,27,31,35,39 | 7 | 1 | 1 | 6 | +| 199 | C2 | 1 | 0 | 3,7,11,15,19,23,27,31,35,39 | 0 | 1 | 2 | 6 | +| 200 | C2 | 1 | 0 | 1,3,5,7, ...,37,39 | 0 | 1 | 2 | 6 | +| 201 | C2 | 1 | 0 | 0,1,2, ...,39 | 7 | 1 | 1 | 6 | +| 202 | A1/B1 | 16 | 1 | 4,9,14,19,24,29,34,39 | 2 | 1 | 6 | 2 | +| 203 | A1/B1 | 16 | 1 | 3,7,11,15,19,23,27,31,35,39 | 2 | 1 | 6 | 2 | +| 204 | A1/B1 | 8 | 1 | 4,9,14,19,24,29,34,39 | 2 | 1 | 6 | 2 | +| 205 | A1/B1 | 8 | 1 | 3,7,11,15,19,23,27,31,35,39 | 2 | 1 | 6 | 2 | +| 206 | A1/B1 | 4 | 1 | 4,9,14,19,24,29,34,39 | 2 | 1 | 6 | 2 | +| 207 | A1/B1 | 4 | 1 | 3,7,11,15,19,23,27,31,35,39 | 2 | 1 | 6 | 2 | +| 208 | A1/B1 | 2 | 1 | 4,9,14,19,24,29,34,39 | 2 | 1 | 6 | 2 | +| 209 | A1/B1 | 1 | 0 | 19,39 | 8 | 1 | 3 | 2 | +| 210 | A1/B1 | 1 | 0 | 9,19,29,39 | 8 | 1 | 3 | 2 | +| 211 | A1/B1 | 1 | 0 | 17,19,37,39 | 2 | 1 | 6 | 2 | +| 212 | A1/B1 | 1 | 0 | 9,19,29,39 | 2 | 2 | 6 | 2 | +| 213 | A1/B1 | 1 | 0 | 23,27,31,35,39 | 8 | 1 | 3 | 2 | +| 214 | A1/B1 | 1 | 0 | 7,15,23,31,39 | 2 | 1 | 6 | 2 | +| 215 | A1/B1 | 1 | 0 | 23,27,31,35,39 | 2 | 1 | 6 | 2 | +| 216 | A1/B1 | 1 | 0 | 4,9,14,19,24,29,34,39 | 8 | 1 | 3 | 2 | +| 217 | A1/B1 | 1 | 0 | 4,9,14,19,24,29,34,39 | 2 | 1 | 6 | 2 | +| 218 | A1/B1 | 1 | 0 | 3,7,11,15,19,23,27,31,35,39 | 2 | 1 | 6 | 2 | +| 219 | A1/B1 | 1 | 0 | 1,3,5,7, ...,37,39 | 2 | 1 | 6 | 2 | +| 220 | A2/B2 | 16 | 1 | 4,9,14,19,24,29,34,39 | 2 | 1 | 3 | 4 | +| 221 | A2/B2 | 16 | 1 | 3,7,11,15,19,23,27,31,35,39 | 2 | 1 | 3 | 4 | +| 222 | A2/B2 | 8 | 1 | 4,9,14,19,24,29,34,39 | 2 | 1 | 3 | 4 | +| 223 | A2/B2 | 8 | 1 | 3,7,11,15,19,23,27,31,35,39 | 2 | 1 | 3 | 4 | +| 224 | A2/B2 | 4 | 1 | 4,9,14,19,24,29,34,39 | 2 | 1 | 3 | 4 | +| 225 | A2/B2 | 4 | 1 | 3,7,11,15,19,23,27,31,35,39 | 2 | 1 | 3 | 4 | +| 226 | A2/B2 | 2 | 1 | 4,9,14,19,24,29,34,39 | 2 | 1 | 3 | 4 | +| 227 | A2/B2 | 1 | 0 | 19,39 | 6 | 1 | 2 | 4 | +| 228 | A2/B2 | 1 | 0 | 9,19,29,39 | 6 | 1 | 2 | 4 | +| 229 | A2/B2 | 1 | 0 | 17,19,37,39 | 2 | 1 | 3 | 4 | +| 230 | A2/B2 | 1 | 0 | 9,19,29,39 | 2 | 2 | 3 | 4 | +| 231 | A2/B2 | 1 | 0 | 23,27,31,35,39 | 6 | 1 | 2 | 4 | +| 232 | A2/B2 | 1 | 0 | 7,15,23,31,39 | 2 | 1 | 3 | 4 | +| 233 | A2/B2 | 1 | 0 | 23,27,31,35,39 | 2 | 1 | 3 | 4 | +| 234 | A2/B2 | 1 | 0 | 4,9,14,19,24,29,34,39 | 6 | 1 | 2 | 4 | +| 235 | A2/B2 | 1 | 0 | 4,9,14,19,24,29,34,39 | 2 | 1 | 3 | 4 | +| 236 | A2/B2 | 1 | 0 | 3,7,11,15,19,23,27,31,35,39 | 2 | 1 | 3 | 4 | +| 237 | A2/B2 | 1 | 0 | 1,3,5,7, ...,37,39 | 2 | 1 | 3 | 4 | +| 238 | A3/B3 | 16 | 1 | 4,9,14,19,24,29,34,39 | 2 | 1 | 2 | 6 | +| 239 | A3/B3 | 16 | 1 | 3,7,11,15,19,23,27,31,35,39 | 2 | 1 | 2 | 6 | +| 240 | A3/B3 | 8 | 1 | 4,9,14,19,24,29,34,39 | 2 | 1 | 2 | 6 | +| 241 | A3/B3 | 8 | 1 | 3,7,11,15,19,23,27,31,35,39 | 2 | 1 | 2 | 6 | +| 242 | A3/B3 | 4 | 1 | 4,9,14,19,24,29,34,39 | 2 | 1 | 2 | 6 | +| 243 | A3/B3 | 4 | 1 | 3,7,11,15,19,23,27,31,35,39 | 2 | 1 | 2 | 6 | +| 244 | A3/B3 | 2 | 1 | 4,9,14,19,24,29,34,39 | 2 | 1 | 2 | 6 | +| 245 | A3/B3 | 1 | 0 | 19,39 | 2 | 1 | 2 | 6 | +| 246 | A3/B3 | 1 | 0 | 9,19,29,39 | 2 | 1 | 2 | 6 | +| 247 | A3/B3 | 1 | 0 | 17,19,37,39 | 2 | 1 | 2 | 6 | +| 248 | A3/B3 | 1 | 0 | 9,19,29,39 | 2 | 2 | 2 | 6 | +| 249 | A3/B3 | 1 | 0 | 7,15,23,31,39 | 2 | 1 | 2 | 6 | +| 250 | A3/B3 | 1 | 0 | 23,27,31,35,39 | 2 | 1 | 2 | 6 | + +| | | | | | | | | | +|-----|-------|---|---|-----------------------------|---|---|---|---| +| 251 | A3/B3 | 1 | 0 | 23,27,31,35,39 | 2 | 2 | 2 | 6 | +| 252 | A3/B3 | 1 | 0 | 4,9,14,19,24,29,34,39 | 2 | 1 | 2 | 6 | +| 253 | A3/B3 | 1 | 0 | 4,9,14,19,24,29,34,39 | 2 | 2 | 2 | 6 | +| 254 | A3/B3 | 1 | 0 | 3,7,11,15,19,23,27,31,35,39 | 2 | 1 | 2 | 6 | +| 255 | A3/B3 | 1 | 0 | 1,3,5,7,...,37,39 | 2 | 1 | 2 | 6 | + +## 6.4 Physical signals + +### 6.4.1 Reference signals + +#### 6.4.1.1 Demodulation reference signal for PUSCH + +##### 6.4.1.1.1 Sequence generation + +###### 6.4.1.1.1.1 Sequence generation when transform precoding is disabled + +If transform precoding for PUSCH is not enabled, the sequence $r(n)$ shall be generated according to + +$$r(n) = \frac{1}{\sqrt{2}}(1 - 2 \cdot c(2n)) + j \frac{1}{\sqrt{2}}(1 - 2 \cdot c(2n + 1))$$ + +where the pseudo-random sequence is defined in clause 5.2.1. The pseudo-random sequence generator shall be initialized with + +where is the OFDM symbol number within the slot, is the slot number within a frame, and + +- are given by the higher-layer parameters *scramblingID0* and *scramblingID1*, respectively, in the *DMRS-UplinkConfig* IE if provided and the PUSCH is scheduled by DCI format 0\_1, 0\_2, or 0\_3, or by a PUSCH transmission with a configured grant; +- is given by the higher-layer parameter *scramblingID0* in the *DMRS-UplinkConfig* IE if provided and the PUSCH is scheduled by DCI format 0\_0 with the CRC scrambled by C-RNTI, MCS-C-RNTI, or CS-RNTI; +- are, for each msgA PUSCH configuration, given by the higher-layer parameters *msgA-ScramblingID0* and *msgA-ScramblingID1*, respectively, in the *msgA-DMRS-Config* IE if provided and the PUSCH transmission is triggered by a Type-2 random access procedure as described in clause 8.1A of [5, TS 38.213]; +- otherwise; +- and are given by + - if the higher-layer parameter *dmrs-Uplink* in the *DMRS-UplinkConfig* IE is provided + +where is the CDM group defined in clause 6.4.1.1.3. + +- otherwise + +The quantity is + +- indicated by the DM-RS initialization field, if present, either in the DCI associated with the PUSCH transmission if DCI format 0\_1, 0\_2, or 0\_3, in [4, TS 38.212] is used; +- indicated by the higher layer parameter *dmrs-SeqInitialization*, if present, for a Type 1 PUSCH transmission with a configured grant; +- determined by the mapping between preamble(s) and a PUSCH occasion and the associated DMRS resource for a PUSCH transmission of Type-2 random access process in [5, TS 38.213]; + +- determined by the mapping between SS/PBCH block(s) and a PUSCH occasion and the associated DMRS resource for a configured-grant based PUSCH transmission in RRC\_INACTIVE state [5, TS 38.213]; +- otherwise . + +#### 6.4.1.1.1.2 Sequence generation when transform precoding is enabled + +If transform precoding for PUSCH is enabled, the reference-signal sequence $r(n)$ shall be generated according to + +$$r(n) = r_{u,v}^{(\alpha,\delta)}(n)$$ + +$$n = 0, 1, \dots, M_{sc}^{\text{PUSCH}} / 2^\delta - 1$$ + +where $\alpha$ depends on the configuration: + +- if the higher-layer parameter *dmrs-UplinkTransformPrecoding* is configured, $\pi/2$ -BPSK modulation is used for PUSCH, and the PUSCH transmission is not a msg3 transmission, and the transmission is not scheduled using DCI format 0\_0 in a common search space, $\alpha$ is given by clause 5.2.3 with $\delta$ given by + +where $\delta$ unless given by the DCI according to clause 7.3.1.1.2 in [4, TS38.212] for a transmission scheduled by DCI format 0\_1, or given by the DCI according to clause 7.3.1.1.3 in [4, TS38.212] for a transmission scheduled by DCI format 0\_2 if the antenna ports field in the DCI format 0\_2 is not 0 bit, or given by the DCI according to clause 7.3.1.1.4 in [4, TS38.212] for a transmission scheduled by DCI format 0\_3, or given by the higher-layer parameter *antennaPort* for a PUSCH transmission scheduled by a type-1 configured grant; and + +- $\alpha$ are given by the higher-layer parameters *pi2BPSK-ScramblingID0* and *pi2BPSK-ScramblingID1*, respectively, in the *DMRS-UplinkConfig* IE if provided and the PUSCH is scheduled by DCI format 0\_1, or by DCI format 0\_2 if the antenna ports field in the DCI format 0\_2 is not 0 bit, or by DCI format 0\_3, or by a PUSCH transmission with a configured grant; +- $\alpha$ is given by the higher-layer parameter *pi2BPSK-ScramblingID0* in the *DMRS-UplinkConfig* IE if provided and the PUSCH is scheduled by DCI format 0\_0 with the CRC scrambled by C-RNTI, MCS-C-RNTI, or CS-RNTI, or by DCI format 0\_2 if the antenna ports field in the DCI format 0\_2 is 0 bit; +- otherwise; +- otherwise, $\alpha$ is given by clause 5.2.2 with $\delta$ . + +The sequence group $u$ , where $u$ is given by + +- if $u$ is configured by the higher-layer parameter *nPUSCH-Identity* in the *DMRS-UplinkConfig* IE, and + - the higher-layer parameter *dmrs-UplinkTransformPrecoding* is not configured or the higher-layer parameter *dmrs-UplinkTransformPrecoding* is configured and $\pi/2$ -BPSK modulation is not used for PUSCH, and + - the PUSCH is neither scheduled by RAR UL grant nor scheduled by DCI format 0\_0 with CRC scrambled by TC-RNTI according to clause 8.3 in [5, TS 38.213]; +- if the higher-layer parameter *dmrs-UplinkTransformPrecoding* is configured, $\pi/2$ -BPSK modulation is used for PUSCH, the PUSCH transmission is not a msg3 transmission, and the transmission is not scheduled using DCI format 0\_0 in a common search space; +- otherwise + +where $f_{gh}$ and the sequence number $v$ are given by: + +- if neither group, nor sequence hopping is enabled + +$$f_{gh} = 0$$ + +$$v = 0$$ + +- if group hopping is enabled and sequence hopping is disabled + +$$f_{gh} = \left( \sum_{m=0}^7 2^m c(8(N_{symb}^{slot} n_{s,f}^{\mu} + l) + m) \right) \bmod 30$$ + +$$v = 0$$ + +where the pseudo-random sequence is defined by clause 5.2.1 and shall be initialized with $c_{init} = \lfloor n_{ID}^{RS} / 30 \rfloor$ at the beginning of each radio frame + +- if sequence hopping is enabled and group hopping is disabled + +$$f_{gh} = 0$$ + +$$v = \begin{cases} c(N_{symb}^{slot} n_{s,f}^{\mu} + l) & \text{if } M_{ZC} \geq 6N_{sc}^{RB} \\ 0 & \text{otherwise} \end{cases}$$ + +where the pseudo-random sequence is defined by clause 5.2.1 and shall be initialized with $c_{init} = n_{ID}^{RS}$ at the beginning of each radio frame. + +The hopping mode is controlled by higher-layer parameters: + +- for PUSCH transmission scheduled by RAR UL grant or by DCI format 0\_0 with CRC scrambled by TC-RNTI, sequence hopping is disabled and group hopping is enabled or disabled by the higher-layer parameter *groupHoppingEnabledTransformPrecoding*; +- for all other transmissions, sequence hopping and group hopping are enabled or disabled by the respective higher-layer parameters *sequenceHopping* and *sequenceGroupHopping* if these parameters are provided, otherwise, the same hopping mode as for Msg3 shall be used. + +The UE is not expected to handle the case of combined sequence hopping and group hopping. + +The quantity above is the OFDM symbol number in the slot except for the case of double-symbol DMRS in which case is the OFDM symbol number in the slot of the first symbol of the double-symbol DMRS. + +#### 6.4.1.1.2 (void) + +#### 6.4.1.1.3 Precoding and mapping to physical resources + +The sequence $r^{(m)}$ shall be mapped to the intermediate quantity according to + +- if transform precoding is not enabled, + - if the higher-layer parameter *enhanced-dmrs-Type* is configured + - otherwise +- if transform precoding is enabled + +where , , and are given by Tables 6.4.1.1.3-1 and 6.4.1.1.3-2 and the configuration type is given by the higher-layer parameter *DMRS-UplinkConfig*, and both and correspond to . The intermediate quantity if $\Delta$ corresponds to any other antenna ports than. + +The intermediate quantity shall be precoded, multiplied with the amplitude scaling factor $\beta_{PUSCH}^{DMRS}$ in order to conform to the transmit power specified in [6, TS 38.214], and mapped to physical resources according to + +where + +- the precoding matrix is given by clause 6.3.1.5, + +- the set of antenna ports is given by clause 6.3.1.5, and +- the set of antenna ports $\{\tilde{p}_0, \dots, \tilde{p}_{v-1}\}$ is given by [6, TS 38.214]; + +and the following conditions are fulfilled: + +- the resource elements are within the common resource blocks allocated for PUSCH transmission. + +The reference point for is + +- subcarrier 0 in common resource block 0 if transform precoding is not enabled, and +- subcarrier 0 of the lowest-numbered resource block of the scheduled PUSCH allocation if transform precoding is enabled. + +The reference point for and the position of the first DM-RS symbol depends on the mapping type: + +- for PUSCH mapping type A: + - is defined relative to the start of the slot if frequency hopping is disabled and relative to the start of each hop in case frequency hopping is enabled + - is given by the higher-layer parameter *dmrs-TypeA-Position* +- for PUSCH mapping type B: + - is defined relative to the start of the scheduled PUSCH resources if frequency hopping is disabled and relative to the start of each hop in case frequency hopping is enabled + - + +The position(s) of the DM-RS symbols is given by and duration where + +- is the duration between the first OFDM symbol of the slot and the last OFDM symbol of the scheduled PUSCH resources in the slot for PUSCH mapping type A according to Tables 6.4.1.1.3-3 and 6.4.1.1.3-4 if intra-slot frequency hopping is not used, or +- is the duration of scheduled PUSCH resources for PUSCH mapping type B according to Tables 6.4.1.1.3-3 and 6.4.1.1.3-4 if intra-slot frequency hopping is not used, or +- is the duration per hop according to Table 6.4.1.1.3-6 if intra-slot frequency hopping is used. +- if the higher-layer parameter *maxLength* in *DMRS-UplinkConfig* is not configured, or for a msgA transmission *msgA-MaxLength* in *msgA-DMRS-Config* is not configured, the tables shall be used according to single-symbol DM-RS +- if the higher-layer parameter *maxLength* in *DMRS-UplinkConfig* is equal to 'len2', the associated DCI or configured grant configuration determines whether single-symbol or double-symbol DM-RS shall be used +- if the higher-layer parameter *msgA-MaxLength* in *msgA-DMRS-Config* is equal to 'len2', double-symbol DM-RS shall be used +- if the higher-layer parameter *dmrs-AdditionalPosition* is not set to 'pos0' and intra-slot frequency hopping is enabled according to clause 7.3.1.1.2 in [4, TS 38.212] and by higher layer, Tables 6.4.1.1.3-6 shall be used assuming *dmrs-AdditionalPosition* is equal to 'pos1' for each hop. + +For PUSCH mapping type A, + +- the case *dmrs-AdditionalPosition* is equal to 'pos3' is only supported when *dmrs-TypeA-Position* is equal to 'pos2'; +- symbols in Table 6.4.1.1.3-4 is only applicable when *dmrs-TypeA-Position* is equal to 'pos2'. + +For msgA transmitted using PUSCH mapping type A, + +- the case *msgA-DMRS-AdditionalPosition* is equal to 'pos3' is only supported when *dmrs-TypeA-Position* is equal to 'pos2'; + +- 'dmrs-AdditionalPosition' in Tables 6.4.1.1.3-3 to 6.4.1.1.3-6 shall be replaced by *msgA-DMRS-AdditionalPosition*; +- only PUSCH DM-RS configuration type 1 is supported; +- only basic DM-RS multiplexing in Table 6.4.1.1.3-5 is supported. + +For msgA transmitted using PUSCH mapping type B, + +- 'dmrs-AdditionalPosition' in Tables 6.4.1.1.3-3 to 6.4.1.1.3-6 shall be replaced by *msgA-DMRS-AdditionalPosition*; +- only PUSCH DM-RS configuration type 1 is supported; +- only basic DM-RS multiplexing in Table 6.4.1.1.3-5 is supported. + +The time-domain index , and the supported antenna ports are given by Table 6.4.1.1.3-5. + +**Table 6.4.1.1.3-1: Parameters for PUSCH DM-RS configuration type 1.** + +| | CDM group | | | | +|----|------------------|---|--|--| +| 0 | 0 | 0 | | | +| 1 | 0 | 0 | | | +| 2 | 1 | 1 | | | +| 3 | 1 | 1 | | | +| 4 | 0 | 0 | | | +| 5 | 0 | 0 | | | +| 6 | 1 | 1 | | | +| 7 | 1 | 1 | | | +| 8 | 0 | 0 | | | +| 9 | 0 | 0 | | | +| 10 | 1 | 1 | | | +| 11 | 1 | 1 | | | +| 12 | 0 | 0 | | | +| 13 | 0 | 0 | | | +| 14 | 1 | 1 | | | +| 15 | 1 | 1 | | | + +**Table 6.4.1.1.3-2: Parameters for PUSCH DM-RS configuration type 2.** + +| | CDM group | | | | +|----|------------------|---|--|--| +| 0 | 0 | 0 | | | +| 1 | 0 | 0 | | | +| 2 | 1 | 2 | | | +| 3 | 1 | 2 | | | +| 4 | 2 | 4 | | | +| 5 | 2 | 4 | | | +| 6 | 0 | 0 | | | +| 7 | 0 | 0 | | | +| 8 | 1 | 2 | | | +| 9 | 1 | 2 | | | +| 10 | 2 | 4 | | | +| 11 | 2 | 4 | | | +| 12 | 0 | 0 | | | +| 13 | 0 | 0 | | | +| 14 | 1 | 2 | | | +| 15 | 1 | 2 | | | +| 16 | 2 | 4 | | | +| 17 | 2 | 4 | | | +| 18 | 0 | 0 | | | +| 19 | 0 | 0 | | | +| 20 | 1 | 2 | | | +| 21 | 1 | 2 | | | +| 22 | 2 | 4 | | | +| 23 | 2 | 4 | | | + +**Table 6.4.1.1.3-3: PUSCH DM-RS positions within a slot for single-symbol DM-RS and intra-slot frequency hopping disabled.** + +| in | DM-RS positions | +|-----------|------------------------| +|-----------|------------------------| + +| symbols | PUSCH mapping type A | | | | PUSCH mapping type B | | | | +|---------|--------------------------------|-------------|--------------|-----------------|--------------------------------|-------------|--------------|----------------| +| | dmrs-AdditionalPosition | | | | dmrs-AdditionalPosition | | | | +| | pos0 | pos1 | pos2 | pos3 | pos0 | pos1 | pos2 | pos3 | +| <4 | - | - | - | - | $l_0$ | $l_0$ | $l_0$ | $l_0$ | +| 4 | $l_0$ | $l_0$ | $l_0$ | $l_0$ | $l_0$ | $l_0$ | $l_0$ | $l_0$ | +| 5 | $l_0$ | $l_0$ | $l_0$ | $l_0$ | $l_0$ | $l_0, 4$ | $l_0, 4$ | $l_0, 4$ | +| 6 | $l_0$ | $l_0$ | $l_0$ | $l_0$ | $l_0$ | $l_0, 4$ | $l_0, 4$ | $l_0, 4$ | +| 7 | $l_0$ | $l_0$ | $l_0$ | $l_0$ | $l_0$ | $l_0, 4$ | $l_0, 4$ | $l_0, 4$ | +| 8 | $l_0$ | $l_0, 7$ | $l_0, 7$ | $l_0, 7$ | $l_0$ | $l_0, 6$ | $l_0, 3, 6$ | $l_0, 3, 6$ | +| 9 | $l_0$ | $l_0, 7$ | $l_0, 7$ | $l_0, 7$ | $l_0$ | $l_0, 6$ | $l_0, 3, 6$ | $l_0, 3, 6$ | +| 10 | $l_0$ | $l_0, 9$ | $l_0, 6, 9$ | $l_0, 6, 9$ | $l_0$ | $l_0, 8$ | $l_0, 4, 8$ | $l_0, 3, 6, 9$ | +| 11 | $l_0$ | $l_0, 9$ | $l_0, 6, 9$ | $l_0, 6, 9$ | $l_0$ | $l_0, 8$ | $l_0, 4, 8$ | $l_0, 3, 6, 9$ | +| 12 | $l_0$ | $l_0, 9$ | $l_0, 6, 9$ | $l_0, 5, 8, 11$ | $l_0$ | $l_0, 10$ | $l_0, 5, 10$ | $l_0, 3, 6, 9$ | +| 13 | $l_0$ | $l_0, 11$ | $l_0, 7, 11$ | $l_0, 5, 8, 11$ | $l_0$ | $l_0, 10$ | $l_0, 5, 10$ | $l_0, 3, 6, 9$ | +| 14 | $l_0$ | $l_0, 11$ | $l_0, 7, 11$ | $l_0, 5, 8, 11$ | $l_0$ | $l_0, 10$ | $l_0, 5, 10$ | $l_0, 3, 6, 9$ | + +Table 6.4.1.1.3-4: PUSCH DM-RS positions within a slot for double-symbol DM-RS and intra-slot frequency hopping disabled. + +| in symbols | DM-RS positions | | | | | | | | +|------------|--------------------------------|-------------|-------------|-------------|--------------------------------|-------------|-------------|-------------| +| | PUSCH mapping type A | | | | PUSCH mapping type B | | | | +| | dmrs-AdditionalPosition | | | | dmrs-AdditionalPosition | | | | +| | pos0 | pos1 | pos2 | pos3 | pos0 | pos1 | pos2 | pos3 | +| <4 | - | - | | | - | - | | | +| 4 | $l_0$ | $l_0$ | | | - | - | | | +| 5 | $l_0$ | $l_0$ | | | $l_0$ | $l_0$ | | | +| 6 | $l_0$ | $l_0$ | | | $l_0$ | $l_0$ | | | +| 7 | $l_0$ | $l_0$ | | | $l_0$ | $l_0$ | | | +| 8 | $l_0$ | $l_0$ | | | $l_0$ | $l_0, 5$ | | | +| 9 | $l_0$ | $l_0$ | | | $l_0$ | $l_0, 5$ | | | +| 10 | $l_0$ | $, 8$ | | | $l_0$ | $l_0, 7$ | | | +| 11 | $l_0$ | $, 8$ | | | $l_0$ | $l_0, 7$ | | | +| 12 | $l_0$ | $, 8$ | | | $l_0$ | $l_0, 9$ | | | +| 13 | $l_0$ | $, 10$ | | | $l_0$ | $l_0, 9$ | | | +| 14 | $l_0$ | $, 10$ | | | $l_0$ | $l_0, 9$ | | | + +Table 6.4.1.1.3-5: PUSCH DM-RS time index . + +| DM-RS multiplexing | DM-RS duration | | Supported antenna ports | | +|--------------------|---------------------|------|-------------------------|----------------------| +| | | | Configuration type 1 | Configuration type 2 | +| Basic | single-symbol DM-RS | 0 | 0 – 3 | 0 – 5 | +| | double-symbol DM-RS | 0, 1 | 0 – 7 | 0 – 11 | +| Enhanced | single-symbol DM-RS | 0 | 0 – 3, 8 – 11 | 0 – 5, 12 – 17 | +| | double-symbol DM-RS | 0, 1 | 0 – 15 | 0 – 23 | + +**Table 6.4.1.1.3-6: PUSCH DM-RS positions within a slot for single-symbol DM-RS and intra-slot frequency hopping enabled.** + +| in symbols | DM-RS positions | | | | | | | | | | | | +|------------|--------------------------------|---------------------|---------------------|---------------------|--------------------------------|---------------------|---------------------|---------------------|--------------------------------|---------------------|---------------------|---------------------| +| | PUSCH mapping type A | | | | | | | | PUSCH mapping type B | | | | +| | dmrs-AdditionalPosition | | | | dmrs-AdditionalPosition | | | | dmrs-AdditionalPosition | | | | +| | pos0 | pos1 | pos0 | pos1 | pos0 | pos1 | pos0 | pos1 | pos0 | pos1 | pos0 | pos1 | +| | 1 st hop | 2 nd hop | 1 st hop | 2 nd hop | 1 st hop | 2 nd hop | 1 st hop | 2 nd hop | 1 st hop | 2 nd hop | 1 st hop | 2 nd hop | +| ≤3 | - | - | - | - | - | - | - | - | 0 | 0 | | 0 | +| 4 | 2 | 0 | 2 | 0 | 3 | 0 | 3 | 0 | 0 | 0 | | 0 | +| 5, 6 | 2 | 0 | 2 | 0, 4 | 3 | 0 | 3 | 0, 4 | 0 | 0 | | 0, 4 | +| 7 | 2 | 0 | 2, 6 | 0, 4 | 3 | 0 | 3 | 0, 4 | 0 | 0 | | 0, 4 | + +### 6.4.1.2 Phase-tracking reference signals for PUSCH + +#### 6.4.1.2.1 Sequence generation + +##### 6.4.1.2.1.1 Sequence generation if transform precoding is not enabled + +If transform precoding is not enabled, the precoded phase-tracking reference signal for subcarrier $\tilde{p}_{j'}$ on layer $\tilde{l}$ is given by + +where + +- antenna ports $\tilde{p}_{j'}$ or $\{\tilde{p}_{j'}, \tilde{p}_{j''}\}$ associated with PT-RS transmission are given by clause 6.2.3 of [6, TS 38.214] +- $r(m)$ is given by clause 6.4.1.1.1.1 + - at the position of the first DM-RS symbol in absence of PUSCH intra-slot frequency hopping + - at the position of the first DM-RS symbol in hop $\tilde{h}$ in presence of PUSCH intra-slot frequency hopping + +##### 6.4.1.2.1.2 Sequence generation if transform precoding is enabled + +If transform precoding is enabled, the phase-tracking reference signal to be mapped in position $\tilde{p}_{j'}$ before transform precoding, where $\tilde{p}_{j'}$ depends on the number of PT-RS groups $N_{\text{group}}^{\text{PT-RS}}$ , the number of samples per PT-RS group $N_{\text{samp}}^{\text{group}}$ , and according to Table 6.4.1.2.2-1, shall be generated according to + +$$r_m(m') = w(k') \frac{e^{j\frac{\pi}{2}(m \bmod 2)}}{\sqrt{2}} [(1 - 2c(m')) + j(1 - 2c(m'))]$$ + +$$m' = N_{\text{samp}}^{\text{group}} s' + k'$$ + +$$s' = 0, 1, \dots, N_{\text{group}}^{\text{PT-RS}} - 1$$ + +$$k' = 0, 1, \dots, N_{\text{samp}}^{\text{group}} - 1$$ + +where the pseudo-random sequence $c(m')$ is defined in clause 5.2.1 and is given by Table 6.4.1.2.1.2-1. The pseudo-random sequence generator shall be initialized with + +where $\tilde{s}$ is the lowest OFDM symbol number in the PUSCH allocation in slot that contains PT-RS according to clause 6.4.1.2.2.2 and is given by the higher-layer parameter *nPUSCH-Identity*. + +**Table 6.4.1.2.1.2-1: The orthogonal sequence .** + +| $n_{\text{RNTI}} \bmod N_{\text{samp}}^{\text{group}}$ | $N_{\text{samp}}^{\text{group}} = 2$
$[w(0) \ w(1)]$ | $N_{\text{samp}}^{\text{group}} = 4$
$[w(0) \ w(1) \ w(2) \ w(3)]$ | +|--------------------------------------------------------|---------------------------------------------------------|-----------------------------------------------------------------------| +| 0 | | | +| 1 | | | +| 2 | - | | +| 3 | - | | + +#### 6.4.1.2.2 Mapping to physical resources + +##### 6.4.1.2.2.1 Precoding and mapping to physical resources if transform precoding is not enabled + +The UE shall transmit phase-tracking reference signals only in the resource blocks used for the PUSCH, and only if the procedure in [6, TS 38.214] indicates that phase-tracking reference signals are being used. + +The PUSCH PT-RS shall be mapped to resource elements according to + +when all the following conditions are fulfilled + +- $l$ is within the OFDM symbols allocated for the PUSCH transmission +- resource element $(k, l)$ is not used for DM-RS +- and correspond to + +The quantities $\alpha$ and $\beta$ are given by Tables 6.4.1.1.3-1 and 6.4.1.1.3-2, the configuration type is given by the higher-layer parameter *dmrs-Type* in the *DMRS-UplinkConfig* IE, and the precoding matrix is given by clause 6.3.1.5. The quantity $\alpha$ is an amplitude scaling factor to conform with the transmit power specified in clause 6.2.2 of [6, TS 38.214]. + +The set of time indices $l$ defined relative to the start of the PUSCH allocation is defined by + +1. set $\mathcal{L} = \emptyset$ and +2. if any symbol in the interval $[l_{\text{ref}}, l_{\text{ref}} + L_{\text{PT-RS}})$ overlaps with a symbol used for DM-RS according to clause 6.4.1.1.3 + - set $\mathcal{L} = \emptyset$ + - set $l_{\text{ref}}$ to the symbol index of the DM-RS symbol in case of a single-symbol DM-RS or to the symbol index of the second DM-RS symbol in case of a double-symbol DM-RS + - repeat from step 2 as long as $l_{\text{ref}} + iL_{\text{PT-RS}}$ is inside the PUSCH allocation +3. add $l_{\text{ref}} + iL_{\text{PT-RS}}$ to the set of time indices for PT-RS +4. increment $i$ by one +5. repeat from step 2 above as long as $l_{\text{ref}} + iL_{\text{PT-RS}}$ is inside the PUSCH allocation + +where $L_{\text{PT-RS}} \in \{1, 2, 4\}$ is defined in Table 6.2.3.1-1 of [6, TS 38.214]. + +For the purpose of PT-RS mapping, the resource blocks allocated for PUSCH transmission are numbered from 0 to $N_{\text{RB}}^{\text{PUSCH}} - 1$ from the lowest scheduled resource block to the highest. The corresponding subcarriers in this set of resource blocks are numbered in increasing order starting from the lowest frequency from 0 to $N_{\text{SC}}^{\text{PUSCH}} - 1$ . The subcarriers to which the PT-RS shall be mapped are given by + +$$k = k_{\text{ref}}^{\text{RE}} + (iK_{\text{PT-RS}} + k_{\text{ref}}^{\text{RB}})N_{\text{sc}}^{\text{RB}}$$ + +$$k_{\text{ref}}^{\text{RB}} = \begin{cases} n_{\text{RNTI}} \bmod K_{\text{PT-RS}} & \text{if } N_{\text{RB}} \bmod K_{\text{PT-RS}} = 0 \\ n_{\text{RNTI}} \bmod (N_{\text{RB}} \bmod K_{\text{PT-RS}}) & \text{otherwise} \end{cases}$$ + +where + +- $i = 0, 1, 2, \dots$ +- $k_{\text{ref}}^{\text{RE}}$ is given by Table 6.4.1.2.2.1-1 for the DM-RS port associated with the PT-RS port according to clause 6.2.3 in [6, TS 38.214]. If the higher-layer parameter *resourceElementOffset* in *PTRS-UplinkConfig* is not configured, the column corresponding to 'offset00' shall be used. +- is the RNTI associated with the DCI scheduling the transmission using C-RNTI, CS-RNTI, MCS-C-RNTI, SP-CSI-RNTI, or is the CS-RNTI in case of configured grant +- is the number of resource blocks scheduled +- is given by [6, TS 38.214]. + +**Table 6.4.1.2.2.1-1: The parameter $k_{\text{ref}}^{\text{RE}}$ .** + +| DM-RS antenna port | $k_{\text{ref}}^{\text{RE}}$ | | | | | | | | +|--------------------|------------------------------|----------|----------|----------|------------------------------|----------|----------|----------| +| | DM-RS Configuration type 1 | | | | DM-RS Configuration type 2 | | | | +| | resourceElementOffset | | | | resourceElementOffset | | | | +| | offset00 | offset01 | offset10 | offset11 | offset00 | offset01 | offset10 | offset11 | +| 0 | 0 | 2 | 6 | 8 | 0 | 1 | 6 | 7 | +| 1 | 2 | 4 | 8 | 10 | 1 | 6 | 7 | 0 | +| 2 | 1 | 3 | 7 | 9 | 2 | 3 | 8 | 9 | +| 3 | 3 | 5 | 9 | 11 | 3 | 8 | 9 | 2 | +| 4 | - | - | - | - | 4 | 5 | 10 | 11 | +| 5 | - | - | - | - | 5 | 10 | 11 | 4 | +| 8 | 4 | 6 | 10 | 0 | - | - | - | - | +| 9 | 6 | 8 | 0 | 2 | - | - | - | - | +| 10 | 5 | 7 | 11 | 1 | - | - | - | - | +| 11 | 7 | 9 | 1 | 3 | - | - | - | - | +| 12 | - | - | - | - | 6 | 7 | 0 | 1 | +| 13 | - | - | - | - | 7 | 0 | 1 | 6 | +| 14 | - | - | - | - | 8 | 9 | 2 | 3 | +| 15 | - | - | - | - | 9 | 2 | 3 | 8 | +| 16 | - | - | - | - | 10 | 11 | 4 | 5 | +| 17 | - | - | - | - | 11 | 4 | 5 | 10 | + +**6.4.1.2.2.2 Mapping to physical resources if transform precoding is enabled** + +The UE shall transmit phase-tracking reference signals only in the resource blocks and OFDM symbols used for the PUSCH, and only if the procedure in [6, TS 38.214] indicates that phase-tracking reference signals are being used. + +The sequence shall be multiplied by and mapped to complex valued symbols in $\tilde{x}^{(0)}(m)$ where + +- $\tilde{x}^{(0)}(m)$ are the complex-valued symbols in OFDM symbol before transform precoding according to clause 6.3.1.4 +- depends on the number of PT-RS groups $N_{\text{group}}^{\text{PT-RS}}$ , the number of samples per PT-RS group, and according to Table 6.4.1.2.2.2-1 +- is the ratio between amplitude of one of the outermost constellation points for the modulation scheme used for PUSCH and one of the outermost constellation points for $\pi/2$ -BPSK as defined in clause 6.2.3 of [TS 38.214] + +The set of time indices $l$ for which PT-RS shall be transmitted is defined relative to the start of the PUSCH allocation and is defined by + +1. set $i = 0$ and $l_{\text{ref}} = 0$ +2. if any symbol in the interval overlaps with a symbol used for DM-RS according to clause 6.4.1.1.3 + - set + - set $l_{\text{ref}}$ to the symbol index of the DM-RS symbol in case of a single-symbol DM-RS and to the symbol index of the second DM-RS symbol in case of a double-symbol DM-RS + - repeat from step 2 as long as $l_{\text{ref}} + iL_{\text{PT-RS}}$ is inside the PUSCH allocation +3. add $l_{\text{ref}} + iL_{\text{PT-RS}}$ to the set of time indices for PT-RS +4. increment $i$ by one +5. repeat from step 2 above as long as $l_{\text{ref}} + iL_{\text{PT-RS}}$ is inside the PUSCH allocation + +where $L_{\text{PT-RS}}$ is given by the higher-layer parameter *timeDensityTransformPrecoding* in the *PTRS-UplinkConfig* IE. + +**Table 6.4.1.2.2.2-1: PT-RS symbol mapping.** + +| Number of PT-RS groups $N_{\text{group}}^{\text{PT-RS}}$ | Number of samples per PT-RS group | Index of PT-RS samples in OFDM symbol prior to transform precoding | +|----------------------------------------------------------|-----------------------------------|--------------------------------------------------------------------| +| 2 | 2 | where $l = l_{\text{ref}}$ and $l = l_{\text{ref}} + 1$ | +| 2 | 4 | where $l = l_{\text{ref}}$ | +| 4 | 2 | where $l = l_{\text{ref}}$ and $l = l_{\text{ref}} + 2$ | +| 4 | 4 | where $l = l_{\text{ref}}$ | +| 8 | 4 | where $l = l_{\text{ref}}$ | + +### 6.4.1.3 Demodulation reference signal for PUCCH + +#### 6.4.1.3.1 Demodulation reference signal for PUCCH format 1 + +##### 6.4.1.3.1.1 Sequence generation + +The reference signal sequence is defined by + +where $c(n)$ is given by Table 6.4.1.3.1.1-1, by clause 9.2.1 of [5, TS 38.213], and the sequence $c(n)$ is given by clause 5.2.2. + +Intra-slot frequency hopping shall be assumed when the higher-layer parameter *intraSlotFrequencyHopping* is enabled, regardless of whether the frequency-hop distance is zero or not, otherwise no intra-slot frequency hopping shall be assumed. + +The orthogonal sequence is given by Table 6.3.2.4.1-2 with the same index as used in clause 6.3.2.4.1. + +**Table 6.4.1.3.1.1-1: Number of DM-RS symbols and the corresponding .** + +| PUCCH length, | No intra-slot hopping | Intra-slot hopping | | +|---------------|-----------------------|--------------------|---| +| | | | | +| 4 | 2 | 1 | 1 | +| 5 | 3 | 1 | 2 | +| 6 | 3 | 2 | 1 | +| 7 | 4 | 2 | 2 | +| 8 | 4 | 2 | 2 | +| 9 | 5 | 2 | 3 | +| 10 | 5 | 3 | 2 | +| 11 | 6 | 3 | 3 | +| 12 | 6 | 3 | 3 | +| 13 | 7 | 3 | 4 | +| 14 | 7 | 4 | 3 | + +#### 6.4.1.3.1.2 Mapping to physical resources + +The sequence shall be multiplied with the amplitude scaling factor in order to conform to the transmit power specified in [5, 38.213] and mapped in sequence starting with to resource elements in a slot on antenna port according to + +where corresponds to the first OFDM symbol of the PUCCH transmission and shall be within the resource blocks assigned for PUCCH transmission according to [5, TS 38.213]. + +For interlaced transmission, the mapping operation shall be repeated for each resource block in the interlace and in the active bandwidth part over the assigned physical resource blocks according to clause 9.2.1 of [5, TS 38.213], with the resource-block dependent sequence generated according to clause 6.3.2.2. + +#### 6.4.1.3.2 Demodulation reference signal for PUCCH format 2 + +##### 6.4.1.3.2.1 Sequence generation + +The reference-signal sequence shall be generated according to + +where the pseudo-random sequence is defined in clause 5.2. The pseudo-random sequence generator shall be initialized with + +where is the OFDM symbol number within the slot, is the slot number within the radio frame, and and are defined in clause 6.3.2.5.2A. + +The quantity is given by the higher-layer parameter *scramblingID0* in the *DMRS-UplinkConfig* IE if provided and by otherwise. If a UE is configured with both *dmrs-UplinkForPUSCH-MappingTypeA* and *dmrs-UplinkForPUSCH-MappingTypeB*, *scramblingID0* is obtained from *dmrs-UplinkForPUSCH-MappingTypeB*. + +##### 6.4.1.3.2.2 Mapping to physical resources + +The sequence shall be multiplied with the amplitude scaling factor in order to conform to the transmit power specified in [5, 38.213] and mapped in sequence starting with to resource elements in a slot on antenna port according to + +where is defined relative to subcarrier 0 of common resource block 0 and shall be within the resource blocks assigned for PUCCH transmission according to clause 9.2.1 of [5, TS 38.213]. + +### 6.4.1.3.3 Demodulation reference signal for PUCCH formats 3 and 4 + +#### 6.4.1.3.3.1 Sequence generation + +The reference-signal sequence shall be generated according to + +$$r_i(m) = r_{u,v}^{(\alpha,\delta)}(m)$$ + +$$m = 0, 1, \dots, M_{sc}^{\text{PUCCH},s} - 1$$ + +where $\alpha$ is given by clause 6.3.2.6.3 and depends on the configuration: + +- if the higher-layer parameter *dmrs-UplinkTransformPrecodingPUCCH* is configured, and -BPSK is used for PUCCH, $\alpha$ is given by clause 5.2.3 with $\delta$ given by clause 6.4.1.3.2.1. The sequence group $u$ and the sequence number $v$ depend on the sequence hopping in clause 6.3.2.2.1. +- otherwise, for PUCCH format 3, PUCCH format 4 with $\delta=1$ , and PUCCH format 4 with $\delta>1$ when -BPSK is not used for PUCCH, $\alpha$ is given by clause 6.3.2.2 and the cyclic shift $\delta$ varies with the symbol number and slot number according to clause 6.3.2.2.2 with + - for PUCCH format 3 without interlaced mapping; + - obtained from Table 6.4.1.3.3.1-1 with the orthogonal sequence index $m_0$ given by clause 6.3.2.6.3 for PUCCH format 3 with interlaced mapping and PUCCH format 4. + +**Table 6.4.1.3.3.1-1: Cyclic shift index for PUCCH format 3 with interlaced mapping and PUCCH format 4.** + +| Orthogonal sequence index | Cyclic shift index $m_0$ | | | +|---------------------------|--------------------------|------------|------------| +| | $\delta=1$ | $\delta=2$ | $\delta=3$ | +| 0 | 0 | 0 | 0 | +| 1 | - | 6 | 6 | +| 2 | - | - | 3 | +| 3 | - | - | 9 | + +#### 6.4.1.3.3.2 Mapping to physical resources + +The sequence shall be multiplied with the amplitude scaling factor $\beta$ , in order to conform to the transmit power specified in [5, 38.213] and mapped in sequence starting with $r_i^{(0)}$ to resource elements on antenna port according to + +$$a_{k,l}^{(p,\mu)} = \beta_{\text{PUCCH},s} \cdot r_i(m)$$ + +$$m = 0, 1, \dots, M_{sc}^{\text{PUCCH},s} - 1$$ + +where + +- $\beta$ is defined relative to subcarrier 0 of the lowest-numbered resource block assigned for PUCCH transmission, +- $\beta$ is given by Table 6.4.1.3.3.2-1 for the case with and without intra-slot frequency hopping and with and without additional DM-RS as described in clause 9.2.1 of [TS 38.213], where $l$ corresponds to the first OFDM symbol of the PUCCH transmission. + +The resource elements shall be within the resource blocks assigned for PUCCH transmission according to clause 9.2.1 of [5, TS 38.213]. + +**Table 6.4.1.3.3.2-1: DM-RS positions for PUCCH format 3 and 4.** + +| PUCCH length | DM-RS position within PUCCH span | | | | +|--------------|----------------------------------|---------|------------------|-------------| +| | No additional DM-RS | | Additional DM-RS | | +| | No hopping | Hopping | No hopping | Hopping | +| 4 | 1 | 0, 2 | 1 | 0, 2 | +| 5 | | 0, 3 | | 0, 3 | +| 6 | | 1, 4 | | 1, 4 | +| 7 | | 1, 4 | | 1, 4 | +| 8 | | 1, 5 | | 1, 5 | +| 9 | | 1, 6 | | 1, 6 | +| 10 | | 2, 7 | | 1, 3, 6, 8 | +| 11 | | 2, 7 | | 1, 3, 6, 9 | +| 12 | | 2, 8 | | 1, 4, 7, 10 | +| 13 | | 2, 9 | | 1, 4, 7, 11 | +| 14 | | 3, 10 | | 1, 5, 8, 12 | + +## 6.4.1.4 Sounding reference signal + +### 6.4.1.4.1 SRS resource + +An SRS resource is configured by the *SRS-Resource* IE or the *SRS-PosResource* IE and consists of + +- antenna ports , where the number of antenna ports is given by the higher layer parameter *nrofSRS-Ports* if configured, otherwise , and when the SRS resource is in a SRS resource set with higher-layer parameter *usage* in *SRS-ResourceSet* not set to 'nonCodebook', or determined according to [6, TS 38.214] when the SRS resource is in a SRS resource set with higher-layer parameter *usage* in *SRS-ResourceSet* set to 'nonCodebook'. +- , the number of hops for SRS Tx hopping for an SRS resource configured by *SRS-PosResource* given by the higher layer parameter *SRShoppingNrofHops* if configured, otherwise . +- consecutive OFDM symbols given by the field *nrofSymbols* contained in the higher layer parameter *resourceMapping*. If , is the number of consecutive OFDM symbol per hop. +- , the starting position in the time domain given by where the offset counts symbols backwards from the end of the slot and is given by the field *startPosition* contained in the higher layer parameter *resourceMapping* and . If \_ is the starting position of each hop in the time domain, determined by the field *startPosition* for each SRS transmission hop. +- , the frequency-domain starting position of the sounding reference signal. + +### 6.4.1.4.2 Sequence generation + +The sounding reference signal sequence for an SRS resource, or if *SRShoppingNrofHops* for *SRS-PosResource* is provided, for a given hop within an SRS resource, shall be generated according to + +where is given by clause 6.4.1.4.3, is given by clause 5.2.2 with and the transmission comb number is contained in the higher-layer parameter *transmissionComb*. The quantity is the OFDM symbol number within the SRS resource. + +The quantity is given by + +- if the higher-layer parameter *nrofSRS-Ports-n8* equals *ports8tdm* +- otherwise + +The cyclic shift for antenna port is given as + +where + +where is contained in the higher layer parameter *transmissionComb*. The maximum number of cyclic shifts is given by Table 6.4.1.4.2-1. + +The quantities and are given by + +- if the higher-layer parameter *nrofSRS-Ports-n8* equals *ports8tdm* +- otherwise + +The quantity is given by + +- if the higher-layer parameter *cyclicShiftHopping* is not configured: +- If the higher-layer parameter *cyclicShiftHopping* is configured: + +where and is the th entry and the cardinality of the set + +respectively, where is given by the higher-layer parameter *hoppingSubset* in the *cyclicShiftHopping* IE if configured, otherwise . The higher-layer parameter *hoppingSubset* in the *cyclicShiftHopping* IE includes a bitmap of bits with bits being set to 1, where the th bit being set to 1 corresponds to . + +The pseudo-random sequence is defined by clause 5.2.1 and shall be initialized with at the beginning of each radio frame for which , where the cyclic-shift hopping identity is contained in the higher-layer parameter *cyclicShiftHopping*. + +If the higher-layer parameter *hoppingFinerGranularity* is configured, , otherwise . + +The sequence group and the sequence number in clause 5.2.2 depends on the higher-layer parameter *groupOrSequenceHopping* in the *SRS-Resource* IE or the *SRS-PosResource* IE. The SRS sequence identity is given by the higher layer parameter *sequenceId* in the *SRS-Resource* IE, in which case , or the *SRS-PosResource-r16* IE, in which case . + +- if *groupOrSequenceHopping* equals 'neither', neither group, nor sequence hopping shall be used and +- if *groupOrSequenceHopping* equals 'groupHopping', group hopping but not sequence hopping shall be used and + +where the pseudo-random sequence is defined by clause 5.2.1 and shall be initialized with at the beginning of each radio frame. + +- if *groupOrSequenceHopping* equals 'sequenceHopping', sequence hopping but not group hopping shall be used and + +where the pseudo-random sequence is defined by clause 5.2.1 and shall be initialized with at the beginning of each radio frame. + +**Table 6.4.1.4.2-1: Maximum number of cyclic shifts as a function of .** + +| | | +|---|----| +| | | +| 2 | 8 | +| 4 | 12 | +| 8 | 6 | + +#### 6.4.1.4.3 Mapping to physical resources + +Throughout this clause, when the higher layer parameter *SRShoppingNrofHops* is provided for *SRS-PosResource*, the sounding reference signal sequence definitions applies to a given hop. + +When SRS is transmitted on a given SRS resource, the sequence for each OFDM symbol and for each of the antenna ports of the SRS resource shall be multiplied with the amplitude scaling factor in order to conform to the transmit power specified in [5, 38.213] and mapped in sequence starting with to resource elements in a slot for each of the antenna ports according to + +The length of the sounding reference signal sequence is given by + +where is given by a selected row of Table 6.4.1.4.3-1 with where is given by the field *b-SRS* contained in the higher-layer parameter *freqHopping* if configured, otherwise . The row of the table is selected according to the index given by the field *c-SRS* contained in the higher-layer parameter *freqHopping*. The quantity is given by the higher-layer parameter *FreqScalingFactor* if configured, otherwise . When *FreqScalingFactor* is configured, the UE expects the length of the SRS sequence to be a multiple of 6. + +The frequency-domain starting position is defined by + +where + +and + +and + +- is given by the higher-layer parameter *StartRBIndex* if configured, otherwise ; +- is given by Table 6.4.1.4.3-3 with + +if the higher-layer parameter *EnableStartRBHopping* is configured, otherwise . + +- is given by the higher-layer parameter YYY. +- is the hop transmission counter in the time domain. +- is the initial hop index. + +The quantity $N_{comb}$ is given by + +- if the higher-layer parameter *combOffsetHopping* is not configured: +- if the higher-layer parameter *combOffsetHopping* is configured: + +where $n$ is the $n$ th entry and the cardinality of the set + +respectively, where $N_{comb}$ is given by the higher-layer parameter *hoppingSubset* in the *combOffsetHopping* IE if configured, otherwise $N_{comb} = 1$ . The higher-layer parameter *hoppingSubset* in the *combOffsetHopping* IE includes a bitmap of $N_{comb}$ bits with bits being set to 1, where the $n$ th bit being set to 1 corresponds to $n$ . + +The pseudo-random sequence $c(n)$ is defined by clause 5.2.1 and shall be initialized with $c(0)$ at the beginning of each radio frame for which $n$ , where the comb offset hopping identity $n$ is contained in the higher-layer parameter *combOffsetHopping*. + +If the higher-layer parameter *hoppingWithRepetition* is set to *Repetition*, $n$ , otherwise $n = 0$ . + +If *SRShoppingNrofHops* is configured: + +- The reference point for $n$ is the lowest subcarrier of the configured bandwidth for SRS with Tx hopping configured by the parameter *XXX* in *TxhoppingBandwidth*. + +otherwise: + +- If the reference point for $n$ is subcarrier 0 in common resource block 0, otherwise the reference point is the lowest subcarrier of the BWP. + +If the SRS is configured by the IE *SRS-PosResource*, the quantity $n$ is given by Table 6.4.1.4.3-2, otherwise $n = 0$ . + +The frequency domain shift value $\alpha$ adjusts the SRS allocation with respect to the reference point grid and is contained in the higher-layer parameter *freqDomainShift* in the *SRS-Resource* IE or the *SRS-PosResource* IE. The transmission comb offset $n$ is contained in the higher-layer parameter *transmissionComb* in the *SRS-Resource* IE or the *SRS-PosResource* IE and $n$ is a frequency position index. + +Frequency hopping of the sounding reference signal is configured by the parameter $n$ , given by the field *b-hop* contained in the higher-layer parameter *freqHopping* if configured, otherwise $n = 0$ . + +If $n$ , frequency hopping is disabled and the frequency position index $n$ remains constant (unless re-configured) and is defined by + +for all OFDM symbols of the SRS resource. The quantity $n$ is given by the higher-layer parameter *freqDomainPosition* if configured, otherwise $n = 0$ , and the values of $n$ and $n$ for $n$ are given by the selected row of Table 6.4.1.4.3-1 corresponding to the configured value of $n$ . + +If $n$ , frequency hopping is enabled and the frequency position indices $n$ are defined by + +where $n$ is given by Table 6.4.1.4.3-1, + +and where $n$ regardless of the value of $n$ . The quantity $n$ counts the number of SRS transmissions. For the case of an SRS resource configured as aperiodic by the higher-layer parameter *resourceType*, it is given by $n$ within the slot in which the symbol SRS resource is transmitted. The quantity $n$ is given by $n$ if the higher-layer parameter *nrofSRS-Ports-n8* equals + +'ports8tdm', otherwise . The quantity is the repetition factor given by the field *repetitionFactor* if configured, otherwise . + +For the case of an SRS resource configured as periodic or semi-persistent by the higher-layer parameter *resourceType*, the SRS counter is given by + +for slots that satisfy . The periodicity in slots and slot offset are given in clause 6.4.1.4.4. + +**Table 6.4.1.4.3-1: SRS bandwidth configuration.** + +| | | | | | | | | | +|----|-----|---|-----|----|----|----|----|----| +| | | | | | | | | | +| 0 | 4 | 1 | 4 | 1 | 4 | 1 | 4 | 1 | +| 1 | 8 | 1 | 4 | 2 | 4 | 1 | 4 | 1 | +| 2 | 12 | 1 | 4 | 3 | 4 | 1 | 4 | 1 | +| 3 | 16 | 1 | 4 | 4 | 4 | 1 | 4 | 1 | +| 4 | 16 | 1 | 8 | 2 | 4 | 2 | 4 | 1 | +| 5 | 20 | 1 | 4 | 5 | 4 | 1 | 4 | 1 | +| 6 | 24 | 1 | 4 | 6 | 4 | 1 | 4 | 1 | +| 7 | 24 | 1 | 12 | 2 | 4 | 3 | 4 | 1 | +| 8 | 28 | 1 | 4 | 7 | 4 | 1 | 4 | 1 | +| 9 | 32 | 1 | 16 | 2 | 8 | 2 | 4 | 2 | +| 10 | 36 | 1 | 12 | 3 | 4 | 3 | 4 | 1 | +| 11 | 40 | 1 | 20 | 2 | 4 | 5 | 4 | 1 | +| 12 | 48 | 1 | 16 | 3 | 8 | 2 | 4 | 2 | +| 13 | 48 | 1 | 24 | 2 | 12 | 2 | 4 | 3 | +| 14 | 52 | 1 | 4 | 13 | 4 | 1 | 4 | 1 | +| 15 | 56 | 1 | 28 | 2 | 4 | 7 | 4 | 1 | +| 16 | 60 | 1 | 20 | 3 | 4 | 5 | 4 | 1 | +| 17 | 64 | 1 | 32 | 2 | 16 | 2 | 4 | 4 | +| 18 | 72 | 1 | 24 | 3 | 12 | 2 | 4 | 3 | +| 19 | 72 | 1 | 36 | 2 | 12 | 3 | 4 | 3 | +| 20 | 76 | 1 | 4 | 19 | 4 | 1 | 4 | 1 | +| 21 | 80 | 1 | 40 | 2 | 20 | 2 | 4 | 5 | +| 22 | 88 | 1 | 44 | 2 | 4 | 11 | 4 | 1 | +| 23 | 96 | 1 | 32 | 3 | 16 | 2 | 4 | 4 | +| 24 | 96 | 1 | 48 | 2 | 24 | 2 | 4 | 6 | +| 25 | 104 | 1 | 52 | 2 | 4 | 13 | 4 | 1 | +| 26 | 112 | 1 | 56 | 2 | 28 | 2 | 4 | 7 | +| 27 | 120 | 1 | 60 | 2 | 20 | 3 | 4 | 5 | +| 28 | 120 | 1 | 40 | 3 | 8 | 5 | 4 | 2 | +| 29 | 120 | 1 | 24 | 5 | 12 | 2 | 4 | 3 | +| 30 | 128 | 1 | 64 | 2 | 32 | 2 | 4 | 8 | +| 31 | 128 | 1 | 64 | 2 | 16 | 4 | 4 | 4 | +| 32 | 128 | 1 | 16 | 8 | 8 | 2 | 4 | 2 | +| 33 | 132 | 1 | 44 | 3 | 4 | 11 | 4 | 1 | +| 34 | 136 | 1 | 68 | 2 | 4 | 17 | 4 | 1 | +| 35 | 144 | 1 | 72 | 2 | 36 | 2 | 4 | 9 | +| 36 | 144 | 1 | 48 | 3 | 24 | 2 | 12 | 2 | +| 37 | 144 | 1 | 48 | 3 | 16 | 3 | 4 | 4 | +| 38 | 144 | 1 | 16 | 9 | 8 | 2 | 4 | 2 | +| 39 | 152 | 1 | 76 | 2 | 4 | 19 | 4 | 1 | +| 40 | 160 | 1 | 80 | 2 | 40 | 2 | 4 | 10 | +| 41 | 160 | 1 | 80 | 2 | 20 | 4 | 4 | 5 | +| 42 | 160 | 1 | 32 | 5 | 16 | 2 | 4 | 4 | +| 43 | 168 | 1 | 84 | 2 | 28 | 3 | 4 | 7 | +| 44 | 176 | 1 | 88 | 2 | 44 | 2 | 4 | 11 | +| 45 | 184 | 1 | 92 | 2 | 4 | 23 | 4 | 1 | +| 46 | 192 | 1 | 96 | 2 | 48 | 2 | 4 | 12 | +| 47 | 192 | 1 | 96 | 2 | 24 | 4 | 4 | 6 | +| 48 | 192 | 1 | 64 | 3 | 16 | 4 | 4 | 4 | +| 49 | 192 | 1 | 24 | 8 | 8 | 3 | 4 | 2 | +| 50 | 208 | 1 | 104 | 2 | 52 | 2 | 4 | 13 | +| 51 | 216 | 1 | 108 | 2 | 36 | 3 | 4 | 9 | +| 52 | 224 | 1 | 112 | 2 | 56 | 2 | 4 | 14 | +| 53 | 240 | 1 | 120 | 2 | 60 | 2 | 4 | 15 | +| 54 | 240 | 1 | 80 | 3 | 20 | 4 | 4 | 5 | +| 55 | 240 | 1 | 48 | 5 | 16 | 3 | 8 | 2 | +| 56 | 240 | 1 | 24 | 10 | 12 | 2 | 4 | 3 | +| 57 | 256 | 1 | 128 | 2 | 64 | 2 | 4 | 16 | +| 58 | 256 | 1 | 128 | 2 | 32 | 4 | 4 | 8 | +| 59 | 256 | 1 | 16 | 16 | 8 | 2 | 4 | 2 | +| 60 | 264 | 1 | 132 | 2 | 44 | 3 | 4 | 11 | +| 61 | 272 | 1 | 136 | 2 | 68 | 2 | 4 | 17 | +| 62 | 272 | 1 | 68 | 4 | 4 | 17 | 4 | 1 | + +| | | | | | | | | | +|----|-----|---|----|----|---|---|---|---| +| 63 | 272 | 1 | 16 | 17 | 8 | 2 | 4 | 2 | +|----|-----|---|----|----|---|---|---|---| + +**Table 6.4.1.4.3-2: The offset for SRS as a function of $n$ and $h$ .** + +| | $n=0$ | $n=1$ | $n=2$ | $n=3$ | $n=4$ | +|---|-------|-------|------------|------------------------|------------------------------------| +| 2 | 0 | 0,1 | 0,1,0,1 | - | - | +| 4 | - | 0, 2 | 0, 2, 1, 3 | 0, 2, 1, 3, 0, 2, 1, 3 | 0, 2, 1, 3, 0, 2, 1, 3, 0, 2, 1, 3 | +| 8 | - | - | 0, 4, 2, 6 | 0, 4, 2, 6, 1, 5, 3, 7 | 0, 4, 2, 6, 1, 5, 3, 7, 0, 4, 2, 6 | + +**Table 6.4.1.4.3-3: The quantity $n$ as a function of $h$ .** + +| | $h=0$ | $h=1$ | $h=2$ | $h=3$ | +|---|-------|-------|-------|-------| +| 0 | 0 | 0 | 0 | 0 | +| 1 | - | 1 | 2 | - | +| 2 | - | - | 1 | - | +| 3 | - | - | - | 3 | + +#### 6.4.1.4.4 Sounding reference signal slot configuration + +Throughout this clause, when the higher layer parameter *SRShoppingNrofHops* is provided for *SRS-PosResource*, the sounding reference signal slot configuration applies to a given hop. + +For an SRS resource configured as periodic or semi-persistent by the higher-layer parameter *resourceType*, a periodicity (in slots) and slot offset are configured according to the higher-layer parameter *periodicityAndOffset-p* or *periodicityAndOffset-sp* in the *SRS-Resource* IE, or *periodicityAndOffset-p* or *periodicityAndOffset-sp* in the *SRS-PosResource* IE. Candidate slots in which the configured SRS resource may be used for SRS transmission are the slots satisfying + +and, if the higher-layer parameter XXX is configured, also + +where $n$ is given by the higher-layer parameter XXX and $h$ is the hyper-frame number. + +SRS is transmitted as described in clause 6.2.1 of [6, TS 38.214]. + +## 7 Downlink + +### 7.1 Overview + +#### 7.1.1 Overview of physical channels + +A downlink physical channel corresponds to a set of resource elements carrying information originating from higher layers. The following downlink physical channels are defined: + +- Physical Downlink Shared Channel, PDSCH +- Physical Broadcast Channel, PBCH +- Physical Downlink Control Channel, PDCCH. + +#### 7.1.2 Overview of physical signals + +A downlink physical signal corresponds to a set of resource elements used by the physical layer but does not carry information originating from higher layers. + +The following downlink physical signals are defined: + +- Demodulation reference signals, DM-RS +- Phase-tracking reference signals, PT-RS +- Positioning reference signal, PRS +- Channel-state information reference signal, CSI-RS +- Primary synchronization signal, PSS +- Secondary synchronization signal, SSS + +## 7.2 Physical resources + +The frame structure and physical resources the UE shall assume when receiving downlink transmissions are defined in Clause 4. + +The following antenna ports are defined for the downlink: + +- Antenna ports starting with 1000 for PDSCH +- Antenna ports starting with 2000 for PDCCH +- Antenna ports starting with 3000 for channel-state information reference signals +- Antenna ports starting with 4000 for SS/PBCH block transmission +- Antenna ports starting with 5000 for positioning reference signals + +The UE shall not assume that two antenna ports are quasi co-located with respect to any QCL type unless specified otherwise. + +For DM-RS associated with a PDSCH, the channel over which a PDSCH symbol on one antenna port is conveyed can be inferred from the channel over which a DM-RS symbol on the same antenna port is conveyed only if the two symbols are within the same resource as the scheduled PDSCH, in the same slot, and in the same PRG as described in clause 5.1.2.3 of [6, TS 38.214]. + +For DM-RS associated with a PDCCH, the channel over which a PDCCH symbol on one antenna port is conveyed can be inferred from the channel over which a DM-RS symbol on the same antenna port is conveyed only if the two symbols are within resources for which the UE may assume the same precoding being used as described in clause 7.3.2.2. + +For DM-RS associated with a PBCH, the channel over which a PBCH symbol on one antenna port is conveyed can be inferred from the channel over which a DM-RS symbol on the same antenna port is conveyed only if the two symbols are within a SS/PBCH block transmitted within the same slot, and with the same block index according to clause 7.4.3.1. + +## 7.3 Physical channels + +### 7.3.1 Physical downlink shared channel + +#### 7.3.1.1 Scrambling + +Up to two codewords can be transmitted. In case of single-codeword transmission, . + +For each codeword , the UE shall assume the block of bits , where is the number of bits in codeword transmitted on the physical channel, are scrambled prior to modulation, resulting in a block of scrambled bits according to + +where the scrambling sequence is given by clause 5.2.1. The scrambling sequence generator shall be initialized with + +where + +- equals the higher-layer parameter *dataScramblingIdentityPDSCH* if configured and the RNTI equals the C-RNTI, MCS-C-RNTI, or CS-RNTI, and the transmission is not scheduled using DCI format 1\_0 in a common search space; +- equals the higher-layer parameter *dataScramblingIdentityPDSCH* if configured in a common MBS frequency resource and the RNTI equals the G-RNTI, G-CS-RNTI, MCCH-RNTI, or multicast-MCCH-RNTI, and the transmission is scheduled using DCI in a common search space configured in the common MBS frequency resource; +- equals + - the higher-layer parameter *dataScramblingIdentityPDSCH* if the codeword is scheduled using a CORESET with *CORESETPoolIndex* equal to 0; + - the higher-layer parameter *dataScramblingIdentityPDSCH2* if the codeword is scheduled using a CORESET with *CORESETPoolIndex* equal to 1; + +if the higher-layer parameters *dataScramblingIdentityPDSCH* and *dataScramblingIdentityPDSCH2* are configured together with the higher-layer parameter *CORESETPoolIndex* containing two different values, and the RNTI equals the C-RNTI, MCS-C-RNTI, or CS-RNTI, and the transmission is not scheduled using DCI format 1\_0 in a common search space; + +- otherwise + +and where $n_{\text{RNTI}}$ corresponds to the RNTI associated with the PDSCH transmission as described in clause 5.1 of [6, TS 38.214]. + +### 7.3.1.2 Modulation + +For each codeword, the UE shall assume the block of scrambled bits are modulated as described in clause 5.1 using one of the modulation schemes in Table 7.3.1.2-1, resulting in a block of complex-valued modulation symbols. + +**Table 7.3.1.2-1: Supported modulation schemes.** + +| Modulation scheme | Modulation order | +|-------------------|------------------| +| QPSK | 2 | +| 16QAM | 4 | +| 64QAM | 6 | +| 256QAM | 8 | +| 1024QAM | 10 | + +### 7.3.1.3 Layer mapping + +The UE shall assume that complex-valued modulation symbols for each of the codewords to be transmitted are mapped onto one or several layers according to Table 7.3.1.3-1. Complex-valued modulation symbols for codeword $c$ shall be mapped onto the layers $l$ , where $c$ is the number of codewords and $l$ is the number of modulation symbols per layer. + +**Table 7.3.1.3-1: Codeword-to-layer mapping for spatial multiplexing.** + +| Number of layers | Number of codewords | Codeword-to-layer mapping | +|------------------|---------------------|---------------------------| +| 1 | 1 | | +| 2 | 1 | | +| 3 | 1 | | +| 4 | 1 | | +| 5 | 2 | | +| 6 | 2 | | +| 7 | 2 | | +| 8 | 2 | | + +### 7.3.1.4 Antenna port mapping + +The block of vectors $\mathbf{y}$ , shall be mapped to antenna ports according to + +where $\mathbf{y}$ . The set of antenna ports shall be determined according to the procedure in [4, TS 38.212]. + +### 7.3.1.5 Mapping to virtual resource blocks + +The UE shall, for each of the antenna ports used for transmission of the physical channel, assume the block of complex-valued symbols conform to the downlink power allocation specified in [6, TS 38.214] and are mapped in sequence starting with $\mathbf{y}$ to resource elements in the virtual resource blocks assigned for transmission which meet all of the following criteria: + +- they are in the virtual resource blocks assigned for transmission; +- the corresponding physical resource blocks are declared as available for PDSCH according to clause 5.1.4 of [6, TS 38.214]; +- the corresponding resource elements in the corresponding physical resource blocks are + - not used for transmission of the associated DM-RS or DM-RS intended for other co-scheduled UEs as described in clause 7.4.1.1.2; + - not used for non-zero-power CSI-RS, which is according to clause 7.4.1.5 and not configured by *TRS-ResourceSet* IE, if the corresponding physical resource blocks are for a PDSCH scheduled by a PDCCH with the CRC scrambled by C-RNTI, MCS-C-RNTI, CS-RNTI, G-RNTI for multicast, G-CS-RNTI, or a PDSCH with SPS, except if the non-zero-power CSI-RS is a CSI-RS configured by the higher-layer parameter *CSI-RS-Resource-Mobility* in the *MeasObjectNR* IE or except if the non-zero-power CSI-RS is an aperiodic non-zero-power CSI-RS resource; + - not used for PT-RS according to clause 7.4.1.2; + - not declared as 'not available for PDSCH according to clause 5.1.4 of [6, TS 38.214]. + +The mapping to resource elements allocated for PDSCH according to [6, TS 38.214] and not reserved for other purposes shall be in increasing order of first the index $k$ over the assigned virtual resource blocks, where $k$ is the first subcarrier in the lowest-numbered virtual resource block assigned for transmission, and then the index $l$ . + +### 7.3.1.6 Mapping from virtual to physical resource blocks + +The UE shall assume the virtual resource blocks are mapped to physical resource blocks according to the indicated mapping scheme, non-interleaved or interleaved mapping. If no mapping scheme is indicated, the UE shall assume non-interleaved mapping. + +For non-interleaved VRB-to-PRB mapping, virtual resource block $n$ is mapped to physical resource block $n$ , except for PDSCH transmissions scheduled with DCI format 1\_0 in a common search space in which case virtual resource block $n$ is mapped to physical resource block $n$ where $n$ is the lowest-numbered physical resource block in the control resource set where the corresponding DCI was received. When two PDCCH candidates from two linked common search space sets as indicated by the higher-layer parameter *searchSpaceLinking* are detected, and the two linked common search space sets are associated with different control resource sets, the control resource set with the lowest number among the two linked control resource sets is used to determine $n$ . + +For interleaved VRB-to-PRB mapping, the mapping process is defined by: + +- Resource block bundles are defined as + - for PDSCH transmissions scheduled with DCI format 1\_0 with the CRC scrambled by SI-RNTI in Type0-PDCCH common search space in CORESET 0, the set of resource blocks in CORESET 0 are divided into resource-block bundles in increasing order of the resource-block number and bundle number where $B$ is the bundle size and $n$ is the size of CORESET 0. + +- resource block bundle consists of resource blocks if and resource blocks otherwise, +- all other resource block bundles consists of resource blocks. +- for PDSCH transmissions scheduled with DCI format 1\_0 in any common search space in bandwidth part with starting position , other than Type0-PDCCH common search space in CORESET 0, the set of virtual resource blocks , where is the size of CORESET 0 if CORESET 0 is configured for the cell and the size of initial downlink bandwidth part if CORESET 0 is not configured for the cell, are divided into virtual resource-block bundles in increasing order of the virtual resource-block number and virtual bundle number and the set of physical resource blocks are divided into physical resource-block bundles in increasing order of the physical resource-block number and physical bundle number, where , is the bundle size, and is the lowest-numbered physical resource block in the control resource set where the corresponding DCI was received. When two PDCCH candidates from two linked search space sets as indicated by the higher-layer parameter *searchSpaceLinking* are detected, and the two linked search space sets are associated with different control resource sets, the control resource set with the lowest number among the two linked control resource sets is used to determine . +- resource block bundle 0 consists of resource blocks, +- resource block bundle consists of resource blocks if and resource blocks otherwise, +- all other resource block bundles consists of resource blocks. +- for all other PDSCH transmissions, the set of resource blocks in bandwidth part with starting position are divided into resource-block bundles in increasing order of the resource-block number and bundle number where is the bundle size for bandwidth part provided by the higher-layer parameter *vrb-ToPRB-Interleaver* for DCI formats 1\_0, 1\_1, and 1\_3 in a UE-specific search space, or *vrb-ToPRB-InterleaverDCI-1-2* for DCI format 1\_2, and + - resource block bundle 0 consists of $L_i - (N_{\text{BWP},i}^{\text{start}} \bmod L_i)$ resource blocks, + - resource block bundle $N_{\text{bundle}} - 1$ consists of $(N_{\text{BWP},i}^{\text{start}} + N_{\text{BWP},i}^{\text{size}}) \bmod L_i$ resource blocks if $(N_{\text{BWP},i}^{\text{start}} + N_{\text{BWP},i}^{\text{size}}) \bmod L_i > 0$ and $L_i$ resource blocks otherwise, + - all other resource block bundles consists of $L_i$ resource blocks. +- Virtual resource blocks in the interval $j \in \{0, 1, \dots, N_{\text{bundle}} - 1\}$ are mapped to physical resource blocks according to + - virtual resource block bundle $N_{\text{bundle}} - 1$ is mapped to physical resource block bundle $N_{\text{bundle}} - 1$ + - virtual resource block bundle is mapped to physical resource block bundle where +- The UE is not expected to be configured with simultaneously with a PRG size of 4 as defined in [6, TS 38.214] + +The UE may assume that the same precoding in the frequency domain is used within a PRB bundle and the bundle size is determined by clause 5.1.2.3 in [6, TS 38.214]. The UE shall not make any assumption that the same precoding is used for different bundles of common resource blocks. + +For PDSCH transmissions scheduled by DCI format 4\_1 or 4\_2, and using G-RNTI or G-CS-RNTI, the quantities and in this clause are replaced by and , respectively, and is the bundle size for the common MBS frequency resource provided by the higher-layer parameter *vrb-ToPRB-Interleaver* in *pdsch-ConfigMulticast*. + +For PDSCH transmissions scheduled by DCI format 4\_0, and using G-RNTI for broadcast, MCCH-RNTI, or multicast-MCCH-RNTI, the quantities and in this clause are replaced by and , respectively, and . + +## 7.3.2 Physical downlink control channel (PDCCH) + +### 7.3.2.1 Control-channel element (CCE) + +A physical downlink control channel consists of one or more control-channel elements (CCEs) as indicated in Table 7.3.2.1-1. + +**Table 7.3.2.1-1: Supported PDCCH aggregation levels.** + +| Aggregation level | Number of CCEs | +|-------------------|----------------| +| 1 | 1 | +| 2 | 2 | +| 4 | 4 | +| 8 | 8 | +| 16 | 16 | + +### 7.3.2.2 Control-resource set (CORESET) + +A control-resource set consists of resource blocks in the frequency domain and symbols in the time domain. + +A control-channel element consists of 6 resource-element groups (REGs) where a resource-element group equals one resource block during one OFDM symbol. Resource-element groups within a control-resource set are numbered in increasing order in a time-first manner, starting with 0 for the first OFDM symbol and the lowest-numbered resource block in the control resource set. + +A UE can be configured with multiple control-resource sets. Each control-resource set is associated with one CCE-to-REG mapping only. + +The CCE-to-REG mapping for a control-resource set can be interleaved or non-interleaved and is described by REG bundles: + +- REG bundle is defined as REGs where is the REG bundle size, , and is the number of REGs in the CORESET +- CCE consists of REG bundles where is an interleaver + +For non-interleaved CCE-to-REG mapping, and . + +For interleaved CCE-to-REG mapping, for and for . The interleaver is defined by + +where . + +The UE is not expected to handle configurations resulting in the quantity not being an integer. + +For a CORESET configured by the *ControlResourceSet* IE: + +- is given by the higher-layer parameter *frequencyDomainResources*; +- is given by the higher-layer parameter *duration*, where is supported only if the higher-layer parameter *dmrs-TypeA-Position* equals 3; +- interleaved or non-interleaved mapping is given by the higher-layer parameter *cce-REG-MappingType*; +- equals 6 for non-interleaved mapping and is given by the higher-layer parameter *reg-BundleSize* for interleaved mapping; +- is given by the higher-layer parameter *interleaverSize*; +- is given by the higher-layer parameter *shiftIndex* if provided, otherwise ; +- for both interleaved and non-interleaved mapping: + - if the higher-layer parameter *precoderGranularity* equals *sameAsREG-bundle* the UE may assume the same precoding being used within a REG bundle + +- if the higher-layer parameter *precoderGranularity* equals *allContiguousRBs*, + - the UE may assume the same precoding being used across the all resource-element groups within the set of contiguous resource blocks in the CORESET; + - the UE may assume that no resource elements in the CORESET overlap with an SSB; + - if the UE is not provided with the higher-layer parameter *pdcchCandidateReception-WithCRSOverlap*, the UE may assume that no resource elements in the CORESET overlap with LTE cell-specific reference signals as indicated by the higher-layer parameter *lte-CRS-ToMatchAround*, *lte-CRS-PatternList1*, *lte-CRS-PatternList2*, *lte-CRS-PatternList3*, or *lte-CRS-PatternList4*. + +For CORESET 0 configured by the *ControlResourceSetZero* IE: + +- and are defined by clause 13 of [5, TS 38.213]; +- the UE may assume interleaved mapping; +- ; +- ; +- ; +- the UE may assume normal cyclic prefix when CORESET 0 is configured by MIB or SIB1; +- the UE may assume the same precoding being used within a REG bundle. + +For CORESET 0 on a carrier where the SS/PBCH block is detected at sync raster points defined in Tables 5.4.3.1-2 or 5.4.3.1-3 of [14, TS 38.101-1] and configured by the *ControlResourceSetZero* IE: + +- and are defined by Table 13-0 in clause 13 of [5, TS 38.213]; +- if on a carrier with a channel bandwidth of 3 MHz, the CORESET is obtained by applying the description above assuming interleaved mapping with ; +- if on a carrier with a channel bandwidth of 3 MHz, the CORESET is obtained by applying the description above assuming interleaved mapping with or non-interleaved mapping as defined by clause 13 of [5, TS 38.213], followed by puncturing the 9 highest-numbered resource blocks to obtain the 15 resource blocks forming CORESET 0; +- if on a carrier with a channel bandwidth of 5 MHz, the CORESET is obtained by applying the description above assuming interleaved mapping with , followed by puncturing the 4 highest-numbered resource blocks to obtain the 20 resource blocks forming CORESET 0; +- ; +- ; +- the UE may assume normal cyclic prefix when CORESET 0 is configured by MIB or SIB1; +- the UE may assume the same precoding being used within a REG bundle. + +### 7.3.2.3 Scrambling + +The UE shall assume the block of bits , where is the number of bits transmitted on the physical channel, is scrambled prior to modulation, resulting in a block of scrambled bits according to + +where the scrambling sequence is given by clause 5.2.1. The scrambling sequence generator shall be initialized with + +$$c_{\text{init}} = (n_{\text{RNTI}} \cdot 2^{16} + n_{\text{ID}}) \bmod 2^{31}$$ + +where + +- for a UE-specific search space as defined in clause 10 of [5, TS 38.213], $n_{ID} \in \{0, 1, \dots, 65535\}$ equals the higher-layer parameter *pdcch-DMRS-ScramblingID* if configured; +- for a PDCCH with the CRC scrambled by G-RNTI, G-CS-RNTI, MCCH-RNTI, or multicast-MCCH-RNTI in a common search space as defined in clause 10 of [5, TS 38.213], equals the higher-layer parameter *pdcch-DMRS-ScramblingID* if configured in a common MBS frequency resource; +- otherwise + +and where + +- $n_{RNTI}$ is given by the C-RNTI for a PDCCH in a UE-specific search space if the higher-layer parameter *pdcch-DMRS-ScramblingID* is configured, and +- $n_{RNTI} = 0$ otherwise. + +### 7.3.2.4 PDCCH modulation + +The UE shall assume the block of bits to be QPSK modulated as described in clause 5.1.3, resulting in a block of complex-valued modulation symbols . + +### 7.3.2.5 Mapping to physical resources + +The UE shall assume the block of complex-valued symbols to be scaled by a factor and mapped to resource elements used for the monitored PDCCH and not used for the associated PDCCH DMRS in increasing order of first , then . The antenna port . + +## 7.3.3 Physical broadcast channel + +### 7.3.3.1 Scrambling + +The UE shall assume the block of bits, where is the number of bits transmitted on the physical broadcast channel, are scrambled prior to modulation, resulting in a block of scrambled bits according to + +where the scrambling sequence is given by clause 5.2. The scrambling sequence shall be initialized with at the start of each SS/PBCH block where + +- for , is the two least significant bits of the candidate SS/PBCH block index +- for , is the three least significant bits of the candidate SS/PBCH block index + +with being the maximum number of candidate SS/PBCH blocks in a half frame, as described in [5, TS 38.213]. + +### 7.3.3.2 Modulation + +The UE shall assume the block of bits are QPSK modulated as described in clause 5.1.3, resulting in a block of complex-valued modulation symbols . + +### 7.3.3.3 Mapping to physical resources + +Mapping to physical resources is described in clause 7.4.3. + +## 7.4 Physical signals + +### 7.4.1 Reference signals + +#### 7.4.1.1 Demodulation reference signals for PDSCH + +##### 7.4.1.1.1 Sequence generation + +The UE shall assume the sequence is defined by + +$$r(n) = \frac{1}{\sqrt{2}}(1 - 2 \cdot c(2n)) + j \frac{1}{\sqrt{2}}(1 - 2 \cdot c(2n + 1))$$ + +where the pseudo-random sequence is defined in clause 5.2.1. The pseudo-random sequence generator shall be initialized with + +where is the OFDM symbol number within the slot, is the slot number within a frame, and + +- are given by the higher-layer parameters *scramblingID0* and *scramblingID1*, respectively, in the *DMRS-DownlinkConfig* IE if provided and the PDSCH is scheduled by PDCCH using DCI format 1\_1, 1\_2, or 1\_3 with the CRC scrambled by C-RNTI, MCS-C-RNTI, or CS-RNTI; +- is given by the higher-layer parameter *scramblingID0* in the *DMRS-DownlinkConfig* IE if provided and the PDSCH is scheduled by PDCCH using DCI format 1\_0 with the CRC scrambled by C-RNTI, MCS-C-RNTI, or CS-RNTI; +- are given by the higher-layer parameters *scramblingID0* and *scramblingID1*, respectively, in the *DMRS-DownlinkConfig* IE if provided in a common MBS frequency resource for multicast and the PDSCH is scheduled by PDCCH using DCI format 4\_2 with the CRC scrambled by G-RNTI or G-CS-RNTI; +- is given by the higher-layer parameter *scramblingID0* in the *DMRS-DownlinkConfig* IE if provided in a common MBS frequency resource and the PDSCH is scheduled by PDCCH with the CRC scrambled by G-RNTI, G-CS-RNTI, MCCH-RNTI, or multicast-MCCH-RNTI; +- otherwise; +- given by + - if the higher-layer parameter *dmrs-Downlink* in the *DMRS-DownlinkConfig* IE is provided + +where $\lambda$ is the CDM group defined in clause 7.4.1.1.2. + +- otherwise by + +The quantity is given by the DM-RS sequence initialization field, if present, in the DCI associated with the PDSCH transmission if DCI format 1\_1, 1\_2, 1\_3, or 4\_2 in [4, TS 38.212] is used, otherwise . + +#### 7.4.1.1.2 Mapping to physical resources + +The UE shall assume the PDSCH DM-RS being mapped to physical resources according to configuration type 1 or configuration type 2 as given by the higher-layer parameter *dmrs-Type*. + +The UE shall assume the sequence is scaled by a factor to conform with the transmission power specified in [6, TS 38.214] and mapped to resource elements according to + +- if the higher-layer parameter *enhanced-dmrs-Type* is configured +- otherwise + +where , , and are given by Tables 7.4.1.1.2-1 and 7.4.1.1.2-2 and the following conditions are fulfilled: + +- the resource elements are within the common resource blocks allocated for PDSCH transmission + +The reference point for $k_{sc}$ is + +- subcarrier 0 of the lowest-numbered resource block in CORESET 0 if the corresponding PDCCH is associated with CORESET 0 and Type0-PDCCH common search space and is addressed to SI-RNTI; +- otherwise, subcarrier 0 in common resource block 0 + +The reference point for $k_{sc}$ and the position $k_{sc}$ of the first DM-RS symbol depends on the mapping type: + +- for PDSCH mapping type A: + - $k_{sc}$ is defined relative to the start of the slot + - if the higher-layer parameter *dmrs-TypeA-Position* is equal to 'pos3' and $k_{sc}$ otherwise +- for PDSCH mapping type B: + - $k_{sc}$ is defined relative to the start of the scheduled PDSCH resources + - + +The position(s) of the DM-RS symbols is given by $k_{sc}$ and duration $L_{sc}$ where + +- for PDSCH mapping type A, $L_{sc}$ is the duration between the first OFDM symbol of the slot and the last OFDM symbol of the scheduled PDSCH resources in the slot +- for PDSCH mapping type B, $L_{sc}$ is the duration of the scheduled PDSCH resources + +and according to Tables 7.4.1.1.2-3 and 7.4.1.1.2-4. + +For PDSCH mapping type A + +- the case *dmrs-AdditionalPosition* equals to 'pos3' is only supported when *dmrs-TypeA-Position* is equal to 'pos2'; +- $k_{sc}$ and $L_{sc}$ symbols in Tables 7.4.1.1.2-3 and 7.4.1.1.2-4 respectively is only applicable when *dmrs-TypeA-Position* is equal to 'pos2'; +- single-symbol DM-RS, except if all of the following conditions are fulfilled in which case : + - the higher-layer parameter *lte-CRS-ToMatchAround*, *lte-CRS-PatternList1*, *lte-CRS-PatternList2*, *lte-CRS-PatternList3*, or *lte-CRS-PatternList4* is configured; and + - the higher-layer parameter *dmrs-AdditionalPosition* is equal to 'pos1' and $k_{sc}$ ; and + - the UE has indicated it is capable of *additionalDMRS-DL-Alt* + +For PDSCH mapping type B + +- if the PDSCH duration $L_{sc}$ OFDM symbols for normal cyclic prefix or $L_{sc}$ OFDM symbols for extended cyclic prefix, and the front-loaded DM-RS of the PDSCH allocation collides with resources reserved for a search space set associated with a CORESET, $k_{sc}$ shall be incremented such that the first DM-RS symbol occurs immediately after the CORESET and until no collision with any CORESET occurs, and + - if the PDSCH duration $L_{sc}$ is 2 symbols, the UE is not expected to receive a DM-RS symbol beyond the second symbol; + - if the PDSCH duration $L_{sc}$ is 5 symbols and if one additional single-symbol DMRS is configured, the UE only expects the additional DM-RS to be transmitted on the 5th symbol when the front-loaded DM-RS symbol is in the 1st symbol of the PDSCH duration, otherwise the UE should expect that the additional DM-RS is not transmitted; + - if the PDSCH duration $L_{sc}$ is 7 symbols for normal cyclic prefix or 6 symbols for extended cyclic prefix: + - if one additional single-symbol DM-RS is configured, the UE only expects the additional DM-RS to be transmitted on the 5th or 6th symbol when the front-loaded DM-RS symbol is in the 1st or 2nd symbol, respectively, of the PDSCH duration, otherwise the UE should expect that the additional DM-RS is not transmitted; + +- if the PDSCH duration is 2, 3, or 4 OFDM symbols, the UE is not expected to receive the front-loaded DM-RS beyond the 4th symbol; +- if the PDSCH duration is 12 or 13 symbols, the UE is not expected to receive DM-RS mapped to symbol 12 or later in the slot; +- for all values of the PDSCH duration other than 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, and 13 symbols, the UE is not expected to receive DM-RS beyond the 4th symbol; +- if the PDSCH duration is less than or equal to 4 OFDM symbols, only single-symbol DM-RS is supported. +- if the higher-layer parameter *lte-CRS-ToMatchAround*, *lte-CRS-PatternList1*, *lte-CRS-PatternList2*, *lte-CRS-PatternList3*, or *lte-CRS-PatternList4* is configured, the PDSCH duration symbols for normal cyclic prefix, the subcarrier spacing configuration, single-symbol DM-RS is configured, and at least one PDSCH DM-RS symbol in the PDSCH allocation collides with a symbol containing resource elements as indicated by the higher-layer parameter *lte-CRS-ToMatchAround*, *lte-CRS-PatternList1*, *lte-CRS-PatternList2*, *lte-CRS-PatternList3*, or *lte-CRS-PatternList4*, then shall be incremented by one in all slots. + +The time-domain index and the supported antenna ports are given by Table 7.4.1.1.2-5 where + +- single-symbol DM-RS is used if the higher-layer parameter *maxLength* in the *DMRS-DownlinkConfig* IE is not configured; +- single-symbol or double-symbol DM-RS is determined by the associated DCI if the higher-layer parameter *maxLength* in the *DMRS-DownlinkConfig* IE is equal to 'len2'; +- basic or enhanced DM-RS multiplexing is controlled by the higher-layer parameter *enhanced-dmrs-Type*. + +In absence of CSI-RS configuration, and unless otherwise configured, the UE may assume PDSCH DM-RS and SS/PBCH block to be quasi co-located with respect to Doppler shift, Doppler spread, average delay, delay spread, and, when applicable, spatial Rx parameters. Unless specified otherwise, the UE may assume that the PDSCH DM-RS within the same CDM group are quasi co-located with respect to Doppler shift, Doppler spread, average delay, delay spread, and spatial Rx (when applicable). The UE may assume that DMRS ports associated with a TCI state as described in clause 5.1.6.2 of [6, TS 38.214] of a PDSCH are QCL with QCL Type A, Type D (when applicable) and average gain. + +The UE may assume that no DM-RS collides with the SS/PBCH block. + +**Table 7.4.1.1.2-1: Parameters for PDSCH DM-RS configuration type 1.** + +| | CDM group | | | | +|------|------------------|---|--|--| +| 1000 | 0 | 0 | | | +| 1001 | 0 | 0 | | | +| 1002 | 1 | 1 | | | +| 1003 | 1 | 1 | | | +| 1004 | 0 | 0 | | | +| 1005 | 0 | 0 | | | +| 1006 | 1 | 1 | | | +| 1007 | 1 | 1 | | | +| 1008 | 0 | 0 | | | +| 1009 | 0 | 0 | | | +| 1010 | 1 | 1 | | | +| 1011 | 1 | 1 | | | +| 1012 | 0 | 0 | | | +| 1013 | 0 | 0 | | | +| 1014 | 1 | 1 | | | +| 1015 | 1 | 1 | | | + +**Table 7.4.1.1.2-2: Parameters for PDSCH DM-RS configuration type 2.** + +| | CDM group | | | | +|----|------------------|---|--|--| +| 0 | 0 | 0 | | | +| 1 | 0 | 0 | | | +| 2 | 1 | 2 | | | +| 3 | 1 | 2 | | | +| 4 | 2 | 4 | | | +| 5 | 2 | 4 | | | +| 6 | 0 | 0 | | | +| 7 | 0 | 0 | | | +| 8 | 1 | 2 | | | +| 9 | 1 | 2 | | | +| 10 | 2 | 4 | | | +| 11 | 2 | 4 | | | +| 12 | 0 | 0 | | | +| 13 | 0 | 0 | | | +| 14 | 1 | 2 | | | +| 15 | 1 | 2 | | | +| 16 | 2 | 4 | | | +| 17 | 2 | 4 | | | +| 18 | 0 | 0 | | | +| 19 | 0 | 0 | | | +| 20 | 1 | 2 | | | +| 21 | 1 | 2 | | | +| 22 | 2 | 4 | | | +| 23 | 2 | 4 | | | + +**Table 7.4.1.1.2-3: PDSCH DM-RS positions for single-symbol DM-RS.** + +| in symbols | DM-RS positions | | | | | | | | +|------------|--------------------------------|-------------|-------------|-------------|--------------------------------|-------------|-------------|-------------| +| | PDSCH mapping type A | | | | PDSCH mapping type B | | | | +| | dmrs-AdditionalPosition | | | | dmrs-AdditionalPosition | | | | +| | pos0 | pos1 | pos2 | pos3 | pos0 | pos1 | pos2 | pos3 | +| 2 | - | - | - | - | | | | | +| 3 | | | | | | | | | +| 4 | | | | | | | | | +| 5 | | | | | | | | | +| 6 | | | | | $l_0$ | $l_{0,4}$ | | | +| 7 | | | | | | $l_{0,4}$ | | | +| 8 | | , 7 | , 7 | , 7 | | | | | +| 9 | | , 7 | , 7 | , 7 | | | | | +| 10 | | , 9 | , 6, 9 | , 6, 9 | | | | | +| 11 | | , 9 | , 6, 9 | , 6, 9 | | | | | +| 12 | | , 9 | , 6, 9 | , 5, 8, 11 | | | | | +| 13 | | , | , 7, 11 | , 5, 8, 11 | | | | | +| 14 | | , | , 7, 11 | , 5, 8, 11 | - | - | - | - | + +**Table 7.4.1.1.2-4: PDSCH DM-RS positions for double-symbol DM-RS.** + +| in symbols | DM-RS positions | | | | | | +|------------|-----------------------------------------------|-------------|-------------|-----------------------------------------------|-------------|-------------| +| | PDSCH mapping type A | | | PDSCH mapping type B | | | +| | dmrs-AdditionalPosition
pos0 | pos1 | pos2 | dmrs-AdditionalPosition
pos0 | pos1 | pos2 | +| <4 | | | | - | - | | +| 4 | | | | - | - | | +| 5 | | | | | | | +| 6 | | | | $l_0$ | $l_0$ | | +| 7 | | | | | | | +| 8 | | | | | | | +| 9 | | | | | | | +| 10 | | , 8 | | | | | +| 11 | | , 8 | | | | | +| 12 | | , 8 | | | | | +| 13 | | , 10 | | | | | +| 14 | | , 10 | | - | - | | + +**Table 7.4.1.1.2-5: PDSCH DM-RS time index and antenna ports .** + +| DM-RS multiplexing | DM-RS duration | | Supported antenna ports | | +|--------------------|---------------------|------|--------------------------|--------------------------| +| | | | Configuration type 1 | Configuration type 2 | +| Basic | single-symbol DM-RS | 0 | 1000 – 1003 | 1000 – 1005 | +| | double-symbol DM-RS | 0, 1 | 1000 – 1007 | 1000 – 1011 | +| Enhanced | single-symbol DM-RS | 0 | 1000 – 1003, 1008 – 1011 | 1000 – 1005, 1012 – 1017 | +| | double-symbol DM-RS | 0, 1 | 1000 – 1015 | 1000 – 1023 | + +## 7.4.1.2 Phase-tracking reference signals for PDSCH + +### 7.4.1.2.1 Sequence generation + +The phase-tracking reference signal for subcarrier $k$ is given by + +where $r$ is the demodulation reference signal given by clause 7.4.1.1.2 at position $l$ and subcarrier $k$ + +### 7.4.1.2.2 Mapping to physical resources + +The UE shall assume phase-tracking reference signals being present only in the resource blocks used for the PDSCH, and only if the procedure in [6, TS 38.214] indicates phase-tracking reference signals being used. + +If present, the UE shall assume the PDSCH PT-RS is scaled by a factor $\alpha$ to conform with the transmission power specified in clause 4.1 of [6, TS 38.214] and mapped to resource elements according to + +when all the following conditions are fulfilled + +- $l$ is within the OFDM symbols allocated for the PDSCH transmission +- resource element $(k, l)$ is not used for DM-RS, non-zero-power CSI-RS (except for those configured for mobility measurements or with *resourceType* in corresponding *CSI-ResourceConfig* configured as 'aperiodic'), zero-power CSI-RS, SS/PBCH block, a detected PDCCH according to clause 5.1.4.1 of [6, TS38.214], or is declared as 'not available' by clause 5.1.4 of [6, TS 38.214] + +The set of time indices $\mathcal{L}$ defined relative to the start of the PDSCH allocation is defined by + +1. set $\mathcal{L} = \emptyset$ +2. if any symbol in the interval $[l_{start}, l_{end}]$ overlaps with a symbol used for DM-RS according to clause 7.4.1.1.2 + - set $\mathcal{L} = \mathcal{L} \cup \{l\}$ + +- set to the symbol index of the DM-RS symbol in case of a single-symbol DM-RS and to the symbol index of the second DM-RS symbol in case of a double-symbol DM-RS + - repeat from step 2 as long as is inside the PDSCH allocation +3. add to the set of time indices for PT-RS + 4. increment by one + 5. repeat from step 2 above as long as is inside the PDSCH allocation + +where . + +For the purpose of PT-RS mapping, the resource blocks allocated for PDSCH transmission are numbered from 0 to from the lowest scheduled resource block to the highest. The corresponding subcarriers in this set of resource blocks are numbered in increasing order starting from the lowest frequency from 0 to . The subcarriers to which the UE shall assume the PT-RS is mapped are given by + +$$k = k_{\text{ref}}^{\text{RE}} + (i K_{\text{PT-RS}} + k_{\text{ref}}^{\text{RB}}) N_{\text{sc}}^{\text{RB}}$$ + +$$k_{\text{ref}}^{\text{RB}} = \begin{cases} n_{\text{RNTI}} \bmod K_{\text{PT-RS}} & \text{if } N_{\text{RB}} \bmod K_{\text{PT-RS}} = 0 \\ n_{\text{RNTI}} \bmod (N_{\text{RB}} \bmod K_{\text{PT-RS}}) & \text{otherwise} \end{cases}$$ + +where + +- $k_{\text{ref}}^{\text{RE}}$ is given by Table 7.4.1.2.2-1 for the DM-RS port associated with the PT-RS port according to clause 5.1.6.3 in [6, TS 38.214]. If the higher-layer parameter *resourceElementOffset* in the *PTRS-DownlinkConfig* IE is not configured, the column corresponding to 'offset00' shall be used. +- is the RNTI associated with the DCI scheduling the transmission +- is the number of resource blocks scheduled +- is given by [6, TS 38.214]. + +**Table 7.4.1.2.2-1: The parameter $k_{\text{ref}}^{\text{RE}}$ .** + +| DM-RS antenna port $p$ | $k_{\text{ref}}^{\text{RE}}$ | | | | | | | | +|------------------------|------------------------------|----------|----------|----------|------------------------------|----------|----------|----------| +| | DM-RS Configuration type 1 | | | | DM-RS Configuration type 2 | | | | +| | resourceElementOffset | | | | resourceElementOffset | | | | +| | offset00 | offset01 | offset10 | offset11 | offset00 | offset01 | offset10 | offset11 | +| 1000 | 0 | 2 | 6 | 8 | 0 | 1 | 6 | 7 | +| 1001 | 2 | 4 | 8 | 10 | 1 | 6 | 7 | 0 | +| 1002 | 1 | 3 | 7 | 9 | 2 | 3 | 8 | 9 | +| 1003 | 3 | 5 | 9 | 11 | 3 | 8 | 9 | 2 | +| 1004 | - | - | - | - | 4 | 5 | 10 | 11 | +| 1005 | - | - | - | - | 5 | 10 | 11 | 4 | +| 1008 | 4 | 6 | 10 | 0 | - | - | - | - | +| 1009 | 6 | 8 | 0 | 2 | - | - | - | - | +| 1010 | 5 | 7 | 11 | 1 | - | - | - | - | +| 1011 | 7 | 9 | 1 | 3 | - | - | - | - | +| 1012 | - | - | - | - | 6 | 7 | 0 | 1 | +| 1013 | - | - | - | - | 7 | 0 | 1 | 6 | +| 1014 | - | - | - | - | 8 | 9 | 2 | 3 | +| 1015 | - | - | - | - | 9 | 2 | 3 | 8 | +| 1016 | - | - | - | - | 10 | 11 | 4 | 5 | +| 1017 | - | - | - | - | 11 | 4 | 5 | 10 | + +### 7.4.1.3 Demodulation reference signals for PDCCH + +#### 7.4.1.3.1 Sequence generation + +The UE shall assume the reference-signal sequence for OFDM symbol $l$ is defined by + +where the pseudo-random sequence is defined in clause 5.2.1. The pseudo-random sequence generator shall be initialized with + +where $l$ is the OFDM symbol number within the slot, $n$ is the slot number within a frame, and + +- $c_{init}$ is given by the higher-layer parameter *pdcch-DMRS-ScramblingID* if provided; +- $c_{init}$ is given by the higher-layer parameter *pdcch-DMRS-ScramblingID* if configured for a common search space in a common MBS frequency resource; +- otherwise. + +#### 7.4.1.3.2 Mapping to physical resources + +The UE shall assume the sequence is mapped to resource elements according to + +$$\begin{aligned} a_{k,l}^{(p,\mu)} &= \beta_{DMRS}^{PDCCH} \cdot r_l(3n + k') \\ k &= nN_{sc}^{RB} + 4k' + 1 \\ k' &= 0, 1, 2 \\ n &= 0, 1, \dots \end{aligned}$$ + +where the following conditions are fulfilled + +- they are within the resource element groups constituting the PDCCH the UE attempts to decode if the higher-layer parameter *precoderGranularity* equals *sameAsREG-bundle*, +- all resource-element groups within the set of contiguous resource blocks in the CORESET where the UE attempts to decode the PDCCH if the higher-layer parameter *precoderGranularity* equals *allContiguousRBs*. + +The reference point for $k$ is + +- subcarrier 0 of the lowest-numbered resource block in the CORESET if the CORESET is configured by the PBCH or by the *controlResourceSetZero* field in the *PDCCH-ConfigCommon* IE, +- subcarrier 0 in common resource block 0 otherwise + +The quantity $l$ is the OFDM symbol number within the slot. + +The antenna port $p$ . + +A UE not attempting to detect a PDCCH in a CORESET shall not make any assumptions on the presence or absence of DM-RS in the CORESET. + +In absence of CSI-RS configuration, and unless otherwise configured, the UE may assume PDCCH DM-RS and SS/PBCH block to be quasi co-located with respect to Doppler shift, Doppler spread, average delay, delay spread, and, when applicable, spatial Rx parameters. + +### 7.4.1.4 Demodulation reference signals for PBCH + +#### 7.4.1.4.1 Sequence generation + +The UE shall assume the reference-signal sequence for an SS/PBCH block is defined by + +where $c_{\text{init}}$ is given by clause 5.2. The scrambling sequence generator shall be initialized at the start of each SS/PBCH block occasion with + +$$c_{\text{init}} = 2^{11} (\bar{i}_{\text{SSB}} + 1) \left( \left\lfloor \frac{N_{\text{ID}}^{\text{cell}}}{4} \right\rfloor + 1 \right) + 2^6 (\bar{i}_{\text{SSB}} + 1) + (N_{\text{ID}}^{\text{cell}} \bmod 4)$$ + +where + +- for $\bar{i}_{\text{SSB}} = i_{\text{SSB}} + 4n_{\text{hf}}$ where $n_{\text{hf}}$ is the number of the half-frame in which the PBCH is transmitted in a frame with $n_{\text{hf}} = 0$ for the first half-frame in the frame and $n_{\text{hf}} = 1$ for the second half-frame in the frame, and $\bar{i}_{\text{SSB}}$ is the two least significant bits of the candidate SS/PBCH block index as defined in [5, TS 38.213] +- for $\bar{i}_{\text{SSB}} = i_{\text{SSB}}$ where $i_{\text{SSB}}$ is the three least significant bits of the candidate SS/PBCH block index as defined in [5, TS 38.213] + +with $N_{\text{SSB}}$ being the maximum number of candidate SS/PBCH blocks in a half frame, as described in [5, TS 38.213]. + +#### 7.4.1.4.2 Mapping to physical resources + +Mapping to physical resources is described in clause 7.4.3. + +#### 7.4.1.5 CSI reference signals + +##### 7.4.1.5.1 General + +Zero-power (ZP) and non-zero-power (NZP) CSI-RS are defined + +- for a non-zero-power CSI-RS configured by the *NZP-CSI-RS-Resource* IE or by the *CSI-RS-Resource-Mobility* field in the *CSI-RS-ResourceConfigMobility* IE or by the *TRS-ResourceSet* IE, the sequence shall be generated according to clause 7.4.1.5.2 and mapped to resource elements according to clause 7.4.1.5.3 +- for a zero-power CSI-RS configured by the *ZP-CSI-RS-Resource* IE, the UE shall assume that the resource elements defined in clause 7.4.1.5.3 are not used for PDSCH transmission subject to clause 5.1.4.2 of [6, TS 38.214]. The UE performs the same measurement/reception on channels/signals except PDSCH regardless of whether they collide with ZP CSI-RS or not. + +##### 7.4.1.5.2 Sequence generation + +The UE shall assume the reference-signal sequence $c_{\text{init}}$ is defined by + +where the pseudo-random sequence $c(n)$ is defined in clause 5.2.1. The pseudo-random sequence generator shall be initialised with + +at the start of each OFDM symbol where $n$ is the slot number within a radio frame, $l$ is the OFDM symbol number within a slot, and $c_{\text{init}}$ equals the higher-layer parameter *scramblingID* or *sequenceGenerationConfig*. + +##### 7.4.1.5.3 Mapping to physical resources + +For each CSI-RS configured, the UE shall assume the sequence $c_{\text{init}}$ being mapped to resources elements according to + +$$\begin{aligned} +a_{k,l}^{(p,\mu)} &= \beta_{\text{CSIRS}} w_f(k) \cdot w_t(l) \cdot r_{l,n_{s,f}}(m') \\ +m' &= \lfloor n\alpha \rfloor + k' + \left\lceil \frac{\bar{k}\rho}{N_{\text{sc}}^{\text{RB}}} \right\rceil \\ +k &= nN_{\text{sc}}^{\text{RB}} + \bar{k} + k' \\ +l &= \bar{l} + l' \\ +\alpha &= \begin{cases} \rho & \text{for } X = 1 \\ 2\rho & \text{for } X > 1 \end{cases} \\ +n &= 0, 1, \dots +\end{aligned}$$ + +when the following conditions are fulfilled: + +- the resource element is within the resource blocks occupied by the CSI-RS resource for which the UE is configured + +The reference point for is subcarrier 0 in common resource block 0. + +The value of is given by the higher-layer parameter *density* in the *CSI-RS-ResourceMapping* IE or the *CSI-RS-CellMobility* IE and the number of ports is given by the higher-layer parameter *nrofPorts*. For NZP CSI-RS configured by the *TRS-ResourceSet* IE, the density and number of ports. + +The UE is not expected to receive CSI-RS and DM-RS on the same resource elements. + +The UE shall assume for a non-zero-power CSI-RS where is selected such that the power offset specified by the higher-layer parameter *powerControlOffsetSS* in the *NZP-CSI-RS-Resource* IE or in the *TRS-ResourceSet* IE, if provided, is fulfilled. + +The quantities , , and are given by Tables 7.4.1.5.3-1 to 7.4.1.5.3-5 where each in a given row of Table 7.4.1.5.3-1 corresponds to a CDM group of size 1 (no CDM) or size 2, 4, or 8. The CDM type is provided by the higher layer parameter *cdm-Type* in the *CSI-RS-ResourceMapping* IE. For NZP CSI-RS configured by the *TRS-ResourceSet* IE, the CDM type is 'noCDM'. The indices and index resource elements within a CDM group. + +The time-domain locations and are provided by the higher-layer parameters *firstOFDMSymbolInTimeDomain* and *firstOFDMSymbolInTimeDomain2*, respectively, in the *CSI-RS-ResourceMapping* IE or the *CSI-RS-ResourceConfigMobility* IE and defined relative to the start of a slot. For NZP CSI-RS configured by *TRS-ResourceSet* IE, the time-domain location is provided by the higher-layer parameter *firstOFDMSymbolInTimeDomain* or *firstOFDMSymbolInTimeDomain+4*. + +The frequency-domain location is given by a bitmap provided by the higher-layer parameter *frequencyDomainAllocation* in the *CSI-RS-ResourceMapping* IE, the *CSI-RS-ResourceConfigMobility* IE, or the *TRS-ResourceSet* IE, with the bitmap and value of in Table 7.4.1.5.3-1 given by + +- , for row 1 of Table 7.4.1.5.3-1 +- , for row 2 of Table 7.4.1.5.3-1 +- , for row 4 of Table 7.4.1.5.3-1 +- , for all other cases + +where is the bit number of the bit in the bitmap set to one, repeated across every of the resource blocks configured for CSI-RS reception by the UE. The starting position and number of the resource blocks in which the UE shall assume that CSI-RS is transmitted are given by the higher-layer parameters *freqBand* and *density* in the *CSI-RS-ResourceMapping* IE for the bandwidth part given by the higher-layer parameter *BWP-Id* in the *CSI-ResourceConfig* IE or given by the higher-layer parameters *nrofPRBs* in the *CSI-RS-CellMobility* IE where the the *startPRB* given by *csi-rs-MeasurementBW* is relative to common resource block 0. For NZP CSI-RS configured by *TRS-ResourceSet* IE, the starting position and number of the resource blocks in which the CSI-RS can be transmitted are given by the higher-layer parameters *nrofRBs*, and *startingRB* in the *TRS-ResourceSet* IE, where *startingRB* is relative to common resource block 0 and the density. + +The UE shall assume that a CSI-RS is transmitted using antenna ports numbered according to + +where $n$ is the sequence index provided by Tables 7.4.1.5.3-2 to 7.4.1.5.3-5, $O$ is the CDM group size, and $X$ is the number of CSI-RS ports. The CDM group index $j$ given in Table 7.4.1.5.3-1 corresponds to the time/frequency locations for a given row of the table. The CDM groups are numbered in order of increasing frequency domain allocation first and then increasing time domain allocation. + +For a CSI-RS resource configured as periodic or semi-persistent by the higher-layer parameter *resourceType*, configured by the higher-layer parameter *CSI-RS-CellMobility* or configured by the higher-layer parameter *TRS-ResourceSet-r17*, the UE shall assume that the CSI-RS is transmitted in slots satisfying + +$$(N_{\text{slot}}^{\text{frame}, \mu} n_f + n_{s,f}^{\mu} - T_{\text{offset}}) \bmod T_{\text{CSI-RS}} = 0$$ + +where the periodicity $T_{\text{CSI-RS}}$ (in slots) and slot offset are obtained from the higher-layer parameter *CSI-ResourcePeriodicityAndOffset*, *slotConfig* or *periodicityAndOffset-r17*. The UE shall assume that CSI-RS is transmitted in a candidate slot as described in clause 11.1 of [5, TS 38.213], clause 10.4B of [5, TS 38.213]. + +The UE may assume that antenna ports within a CSI-RS resource are quasi co-located with QCL Type A, Type D (when applicable), and average gain. + +**Table 7.4.1.5.3-1: CSI-RS locations within a slot.** + +| Row | Ports $X$ | Density $\rho$ | cdm-Type | $(\bar{k}, \bar{l})$ | CDM group index $j$ | $k'$ | $l'$ | +|-----|-----------|----------------|-----------------|----------------------|------------------------------------------------------|------|------------| +| 1 | 1 | 3 | noCDM | , , | 0,0,0 | 0 | 0 | +| 2 | 1 | 1, 0.5 | noCDM | , | 0 | 0 | 0 | +| 3 | 2 | 1, 0.5 | fd-CDM2 | , | 0 | 0, 1 | 0 | +| 4 | 4 | 1 | fd-CDM2 | , | 0, 1 | 0, 1 | 0 | +| 5 | 4 | 1 | fd-CDM2 | , | 0, 1 | 0, 1 | 0 | +| 6 | 8 | 1 | fd-CDM2 | , , , | 0, 1, 2, 3 | 0, 1 | 0 | +| 7 | 8 | 1 | fd-CDM2 | , , , | 0, 1, 2, 3 | 0, 1 | 0 | +| 8 | 8 | 1 | cdm4-FD2-TD2 | , | 0, 1 | 0, 1 | 0, 1 | +| 9 | 12 | 1 | fd-CDM2 | , , , , | 0, 1, 2, 3, 4, 5 | 0, 1 | 0 | +| 10 | 12 | 1 | cdm4-FD2-TD2 | , , | 0, 1, 2 | 0, 1 | 0, 1 | +| 11 | 16 | 1, 0.5 | fd-CDM2 | , , , , , , | 0, 1, 2, 3, 4, 5, 6, 7 | 0, 1 | 0 | +| 12 | 16 | 1, 0.5 | cdm4-FD2-TD2 | , , , | 0, 1, 2, 3 | 0, 1 | 0, 1 | +| 13 | 24 | 1, 0.5 | fd-CDM2 | , , , , , , , , | 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11 | 0, 1 | 0 | +| 14 | 24 | 1, 0.5 | cdm4-FD2-TD2 | , , , , | 0, 1, 2, 3, 4, 5 | 0, 1 | 0, 1 | +| 15 | 24 | 1, 0.5 | cdm8-FD2-TD4 | , , | 0, 1, 2 | 0, 1 | 0, 1, 2, 3 | +| 16 | 32 | 1, 0.5 | fd-CDM2 | , , , , , , , , , , | 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15 | 0, 1 | 0 | +| 17 | 32 | 1, 0.5 | cdm4-FD2-TD2 | , , , , , , | 0, 1, 2, 3, 4, 5, 6, 7 | 0, 1 | 0, 1 | +| 18 | 32 | 1, 0.5 | cdm8-FD2-TD4 | , , , | 0, 1, 2, 3 | 0, 1 | 0, 1, 2, 3 | + +**Table 7.4.1.5.3-2: The sequences $n$ and $O$ for *cdm-Type* equal to 'noCDM'.** + +| Index | | | +|-------|---|---| +| 0 | 1 | 1 | + +**Table 7.4.1.5.3-3: The sequences and for *cdm-Type* equal to 'fd-CDM2'.** + +| Index | | | +|-------|--|---| +| 0 | | 1 | +| 1 | | 1 | + +**Table 7.4.1.5.3-4: The sequences and for *cdm-Type* equal to 'cdm4-FD2-TD2'.** + +| Index | | | +|-------|--|--| +| 0 | | | +| 1 | | | +| 2 | | | +| 3 | | | + +**Table 7.4.1.5.3-5: The sequences and for *cdm-Type* equal to 'cdm8-FD2-TD4'.** + +| Index | | | +|-------|--|--| +| 0 | | | +| 1 | | | +| 2 | | | +| 3 | | | +| 4 | | | +| 5 | | | +| 6 | | | +| 7 | | | + +## 7.4.1.6 RIM reference signals + +### 7.4.1.6.1 General + +RIM-RS can be used by an gNB to measure inter-cell interference and to provide information about the experienced interference to other gNBs. Up to two different types of RIM-RS can be configured where + +- the first RIM-RS type can be used to convey information, +- the second RIM-RS type depends on configuration only. + +### 7.4.1.6.2 Sequence generation + +The RIM-RS receiver shall assume the reference-signal sequence is defined by + +where the pseudo-random sequence is defined in clause 5.2.1. The pseudo-random sequence generator shall be initialised with + +where + +- is given by clause 7.4.1.6.4.4; +- where the pseudo-random sequence is given by clause 5.2.1, initialized with where the multiplier factor and the offset ; +- is the number of RIM-RS transmission periods since where + - is the time in seconds relative to of 00:00:00 on 1 January 1900, calculated as continuous time without leap second and traceable to a common time reference, and + - is the RIM-RS transmission periodicity in seconds assuming that the first RIM-RS transmission period starts at , and where is given by clause 7.4.1.6.4.2. + +#### 7.4.1.6.3 Mapping to physical resources + +The RIM-RS receiver shall assume the reference signal being mapped to physical resources according to + +where $\alpha$ is an amplitude scaling factor in order to control the RIM-RS transmission power and $n$ is the antenna port. Baseband signal generation shall be done according to clause 5.3.3. + +The starting position for RIM-RS type in slot in a frame is given by + +in slots satisfying + +where + +- $N_{\text{SFN}}$ counts the number of times the SFN periods within the RIM-RS transmission period; +- $\Delta$ where $\Delta$ is the symbol offset of the reference point after the starting boundary of the uplink-downlink switching period in which the RIM-RS is mapped to and $\Delta$ is obtained as described in clause 7.4.1.6.4.2; +- $N_{\text{slots}}$ is the total number of slots in a RIM-RS transmission period as defined in clause 7.4.1.6.4.2; +- $\Delta_{\text{slot}}$ is the slot offset of the uplink-downlink switching period with index $\Delta_{\text{slot}}$ with respect to the starting boundary of the RIM-RS transmission period and is defined in clause 7.4.1.6.4.2; +- $T_{\text{RIM-RS}}$ is the RIM-RS transmission periodicity in units of uplink-downlink switching period as defined in clause 7.4.1.6.4.2. + +#### 7.4.1.6.4 RIM-RS configuration + +##### 7.4.1.6.4.1 General + +A resource for RIM-RS transmission is defined by the indices $\Delta$ , $\Delta_{\text{slot}}$ , and $T_{\text{RIM-RS}}$ used as indices into configured lists of time, frequency, and sequence parameters, respectively. + +All RIM-RS resources occupy the same number of resource blocks, $N_{\text{RB}}$ . At most 32 RIM-RS resources can be configured within a 10 ms period. + +##### 7.4.1.6.4.2 Time-domain parameters and mapping from $\Delta$ to time-domain parameters + +RIM-RS are transmitted periodically with the RIM-RS transmission period defined in units of the uplink-downlink switching period determined from one or two configured uplink-downlink periods. + +- If a single uplink-downlink period is configured for RIM-RS purposes, + - $T_{\text{RIM-RS}}$ is the RIM-RS transmission periodicity in terms of uplink-downlink switching periods given by + +where $T_{\text{RIM-RS}}$ ms; + +- $N_{\text{slots}}$ is the total number of slots in a RIM-RS transmission period; +- $\Delta_{\text{slot}}$ is the slot offset of the uplink-downlink switching period with index $\Delta_{\text{slot}}$ with respect to the starting boundary of the RIM-RS transmission period +- If two uplink-downlink periods are configured for RIM-RS purposes, + - $T_{\text{RIM-RS}}$ is the RIM-RS transmission periodicity in terms of pairs of uplink-downlink switching periods and is given by + +where each pair consists of a first period of ms and a second period of ms and where divides 20 ms; + +- is the total number of slots in a RIM-RS transmission period; +- is the slot offset of the uplink-downlink switching period with index with respect to the starting boundary of the RIM-RS transmission period + +The intermediate quantity is given by + +where + +- and are the total number of setIDs for RIM-RS type 1 and RIM-RS type 2, respectively; +- is the number of candidate frequency resources configured in the network; +- is the number of candidate sequences assigned for RIM-RS type in the network; +- and are the number of consecutive uplink-downlink switching periods for RIM-RS type 1 and RIM-RS type 2, respectively. If near-far functionality is not configured, , otherwise and the first and second half of the consecutive uplink-downlink switching periods are for near functionality and far functionality, respectively. + +The quantity is obtained from entry in a list of configured symbol offsets for RIM-RS . + +#### 7.4.1.6.4.3 Frequency-domain parameters and mapping from to frequency-domain parameters + +The frequency-domain parameter in clause 5.3.3 is the frequency offset relative to a configured reference point for RIM-RS and is obtained from entry in a list of configured frequency offsets expressed in units of resource blocks. + +The number of candidate frequency resources configured in the network, , shall fulfil + +If , the frequency difference between any pair of configured frequency offsets in the list is not smaller than . + +The number of resource blocks for RIM-RS is given by + +#### 7.4.1.6.4.4 Sequence parameters and mapping from to sequence parameters + +The scrambling identity clause 7.4.1.6.2 is obtained from entry in a list of configured scrambling identities. + +#### 7.4.1.6.4.5 Mapping between resource triplet and set ID + +The resource indices , , and are determined from the index in the set ID according to + +where + +- is given by +- is the number of candidate frequency resources configured in the network; +- is the number of sequence candidates for the current RIM-RS resource given by +- is the starting time offset given by +- is given by + +where $N_{seq}$ is the number of candidate sequences assigned for RIM-RS type 1 + +- $N_{consec}$ is the number of consecutive uplink-downlink periods for RIM-RS type as given by clause 7.4.1.6.4.2; +- $N_{set}$ is the number of sets of candidate sequences. + +The set ID is determined from the resource triplet according to + +### 7.4.1.7 Positioning reference signals + +#### 7.4.1.7.1 General + +A positioning frequency layer consists of one or more downlink PRS resource sets, each of which consists of one or more downlink PRS resources as described in [6, TS 38.214]. + +#### 7.4.1.7.2 Sequence generation + +The UE shall assume the reference-signal sequence $c_{n,l}(n)$ is defined by + +where the pseudo-random sequence $c_i$ is defined in clause 5.2.1. The pseudo-random sequence generator shall be initialised with + +where $n$ is the slot number, the downlink PRS sequence ID $c_{ID}$ is given by the higher-layer parameter *dl-PRS-SequencelD*, and $l$ is the OFDM symbol within the slot to which the sequence is mapped. + +#### 7.4.1.7.3 Mapping to physical resources in a downlink PRS resource + +For each downlink PRS resource configured, the UE shall assume the sequence $c_{n,l}(n)$ is scaled with a factor $\alpha$ and mapped to resources elements $k$ according to + +when the following conditions are fulfilled: + +- the resource element $k$ is within the resource blocks occupied by the downlink PRS resource for which the UE is configured; +- the symbol $l$ is not used by any SS/PBCH block used by a serving cell for downlink PRS transmitted from the same serving cell or any SS/PBCH block from a non-serving cell whose time frequency location is provided to the UE by higher layers for downlink PRS transmitted from the same non-serving cell; +- the slot number satisfies the conditions in clause 7.4.1.7.4. + +and where + +- $n_{port}$ is the antenna port +- $l$ is the first symbol of the downlink PRS within a slot and given by the higher-layer parameter *dl-PRS-ResourceSymbolOffset*; +- the size of the downlink PRS resource in the time domain $N_{symbols}$ is given by the higher-layer parameter *dl-PRS-NumSymbols*; +- the comb size $N$ is given by the higher-layer parameter *dl-PRS-CombSizeN-AndReOffset* for a downlink PRS resource configured for RTT-based propagation delay compensation, otherwise by the higher-layer parameter *dl-PRS-CombSizeN* such that the combination $\{N, R\}$ is one of $\{1, 2\}$ , $\{2, 2\}$ , $\{4, 2\}$ , $\{6, 2\}$ , $\{12, 2\}$ , $\{1, 4\}$ , $\{4, 4\}$ , $\{12, 4\}$ , $\{1, 6\}$ , $\{6, 6\}$ , $\{12, 6\}$ , $\{1, 12\}$ and $\{12, 12\}$ ; +- the resource-element offset $R$ is obtained from the higher-layer parameter *dl-PRS-CombSizeN-AndReOffset*; + +- the quantity $\Delta f$ is given by Table 7.4.1.7.3-1. + +If the downlink PRS resource is configured for RTT based propagation delay compensation as described in clause 9 of [6, TS 38.214], the reference point for $\Delta f$ is subcarrier 0 in common resource block 0; Otherwise, the reference point for $\Delta f$ is the location of the point A of the positioning frequency layer, in which the downlink PRS resource is configured where point A is given by the higher-layer parameter *dl-PRS-PointA*. + +**Table 7.4.1.7.3-1: The frequency offset as a function of $\Delta f$ .** + +| | Symbol number within the downlink PRS resource | | | | | | | | | | | | +|----|------------------------------------------------|---|---|---|---|---|---|----|---|---|----|----| +| | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | +| 2 | 0 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | +| 4 | 0 | 2 | 1 | 3 | 0 | 2 | 1 | 3 | 0 | 2 | 1 | 3 | +| 6 | 0 | 3 | 1 | 4 | 2 | 5 | 0 | 3 | 1 | 4 | 2 | 5 | +| 12 | 0 | 6 | 3 | 9 | 1 | 7 | 4 | 10 | 2 | 8 | 5 | 11 | + +#### 7.4.1.7.4 Mapping to slots in a downlink PRS resource set + +For a downlink PRS resource in a downlink PRS resource set, the UE shall assume the downlink PRS resource being transmitted when the slot and frame numbers fulfil + +and one of the following conditions are fulfilled: + +- the higher-layer parameters *dl-PRS-MutingOption1* and *dl-PRS-MutingOption2* are not provided; +- the higher-layer parameter *dl-PRS-MutingOption1* is provided with bitmap $\mathbf{b}$ but *dl-PRS-MutingOption2* with bitmap $\mathbf{b}$ is not provided, and bit $b_i$ is set; +- the higher-layer parameter *dl-PRS-MutingOption2* is provided with bitmap $\mathbf{b}$ but *dl-PRS-MutingOption1* with bitmap $\mathbf{b}$ is not provided, and bit $b_i$ is set; +- the higher-layer parameters *dl-PRS-MutingOption1* with bitmap $\mathbf{b}$ and *dl-PRS-MutingOption2* with $\mathbf{b}$ are both provided, and both bit $b_i$ and $b_j$ are set. + +where + +- $i$ is bit $i$ in the bitmap given by the higher-layer parameter *dl-PRS-MutingOption1* where $N$ is the size of the bitmap; +- $j$ is bit $j$ in the bitmap given by the higher-layer parameter *dl-PRS-MutingOption2*; +- the periodicity $T$ and the slot offset $\Delta$ are given by the higher-layer parameter *dl-PRS-Periodicity-and-ResourceSetSlotOffset*; +- the downlink PRS resource slot offset $\Delta$ is given by the higher-layer parameter *dl-PRS-ResourceSlotOffset*; +- the repetition factor $R$ is given by the higher-layer parameter *dl-PRS-ResourceRepetitionFactor*; +- the muting repetition factor $M$ is given by the higher-layer parameter *dl-PRS-MutingBitRepetitionFactor*; +- the time gap $\Delta$ is given by the higher-layer parameter *dl-PRS-ResourceTimeGap*; + +For a downlink PRS resource in a downlink PRS resource set configured for RTT-based propagation delay compensation, the UE shall assume the downlink PRS resource being transmitted as described in clause 9 of [6, TS 38.214]; otherwise, the UE shall assume the downlink PRS resource being transmitted as described in clause 5.1.6.5 of [6, TS 38.214]. + +## 7.4.2 Synchronization signals + +### 7.4.2.1 Physical-layer cell identities + +There are 1008 unique physical-layer cell identities given by + +where $n_{ID}$ and $n_{ID}^{cell}$ . + +#### 7.4.2.2 Primary synchronization signal + +##### 7.4.2.2.1 Sequence generation + +The sequence $c_{PSS}$ for the primary synchronization signal is defined by + +where + +and + +##### 7.4.2.2.2 Mapping to physical resources + +Mapping to physical resources is described in clause 7.4.3. + +#### 7.4.2.3 Secondary synchronization signal + +##### 7.4.2.3.1 Sequence generation + +The sequence $c_{SSS}$ for the secondary synchronization signal is defined by + +where + +and + +##### 7.4.2.3.2 Mapping to physical resources + +Mapping to physical resources is described in clause 7.4.3. + +### 7.4.3 SS/PBCH block + +#### 7.4.3.1 Time-frequency structure of an SS/PBCH block + +In the time domain, an SS/PBCH block consists of 4 OFDM symbols, numbered in increasing order from 0 to 3 within the SS/PBCH block, where PSS, SSS, and PBCH with associated DM-RS are mapped to symbols as given by Table 7.4.3.1-1. + +In the frequency domain, an SS/PBCH block consists of 240 contiguous subcarriers with the subcarriers numbered in increasing order from 0 to 239 within the SS/PBCH block. The quantities $k$ and $l$ represent the frequency and time indices, respectively, within one SS/PBCH block. The UE may assume that the complex-valued symbols corresponding to resource elements denoted as 'Set to 0' in Table 7.4.3.1-1 are set to zero. The quantity $k_{offset}$ in Table 7.4.3.1-1 is given by $k_{offset} = n_{ID}^{cell} \bmod 4$ . The quantity $k_{offset}$ is the subcarrier offset from subcarrier 0 in common resource block $n_{CRB}$ to the lowest-numbered subcarrier of the SS/PBCH block, or the SS/PBCH block after puncturing if applicable, where $n_{CRB}$ is obtained from the higher-layer parameter *offsetToPointA*. + +- For operation with shared spectrum channel access in FR2-2 and for operation without shared spectrum channel access, the 4 least significant bits of $k_{offset}$ are given by the higher-layer parameter *ssb-SubcarrierOffset* and for FR1 the most significant bit of $k_{offset}$ is given by in the PBCH payload as defined in clause 7.1.1 of [4, TS 38.212]. +- For operation with shared spectrum channel access in FR1, the 4 least significant bits of $k_{offset}$ are given by the higher-layer parameter *ssb-SubcarrierOffset* and the most significant bit of $k_{offset}$ is given by in the PBCH payload as defined in clause 7.1.1 of [4, TS 38.212]. If $n_{ID}^{cell} \bmod 4 = 0$ ; otherwise, $k_{offset} = k_{offset} + 1$ . + +If *ssb-SubcarrierOffset* is not provided, is derived from the frequency difference between the SS/PBCH block and Point A. + +The UE may assume that the complex-valued symbols corresponding to resource elements that are part of a common resource block partially or fully overlapping with an SS/PBCH block, or an SS/PBCH block after puncturing if applicable, and not used for SS/PBCH transmission are set to zero in the OFDM symbols partially or fully overlapping with OFDM symbols where SS/PBCH is transmitted. + +For an SS/PBCH block, the UE shall assume + +- antenna port is used for transmission of PSS, SSS, PBCH and DM-RS for PBCH, +- the same cyclic prefix length and subcarrier spacing for the PSS, SSS, PBCH and DM-RS for PBCH, +- for SS/PBCH block type A, and with the quantities , and expressed in terms of 15 kHz subcarrier spacing, and +- for SS/PBCH block type B in FR2-1, and with the quantity expressed in terms of the subcarrier spacing provided by the higher-layer parameter *subCarrierSpacingCommon* and expressed in terms of 60 kHz subcarrier spacing; +- for SS/PBCH block type B in FR2-2, and with the quantity expressed in terms of the SS/PBCH block subcarrier spacing and expressed in terms of 60 kHz subcarrier spacing; +- the centre of subcarrier 0 of resource block coincides with the centre of subcarrier 0 of a common resource block with the subcarrier spacing + - provided by the higher-layer parameter *subCarrierSpacingCommon* for operation without shared spectrum channel access in FR1 and FR2-1; and + - same as the subcarrier spacing of the SS/PBCH block for operation without shared spectrum access in FR2-2 and for operation with shared spectrum channel access. +- This common resource block overlaps with subcarrier 0 of the lowest-numbered resource block of the SS/PBCH block, or the SS/PBCH block after puncturing if applicable. + +The UE may assume that SS/PBCH blocks transmitted with the same block index on the same center frequency location are quasi co-located with respect to Doppler spread, Doppler shift, average gain, average delay, delay spread, and, when applicable, spatial Rx parameters. The UE shall not assume quasi co-location for any other SS/PBCH block transmissions other than what is specified in [5, TS 38.213]. + +For cell search on a carrier with a channel bandwidth of 3 MHz, the UE is not expected to receive subcarriers 0 to 47 and 192 to 239 in any of the 4 OFDM symbols of the SS/PBCH block, where the remaining 12 resource blocks form the SS/PBCH block after puncturing. + +**Table 7.4.3.1-1: Resources within an SS/PBCH block for PSS, SSS, PBCH, and DM-RS for PBCH.** + +| Channel or signal | OFDM symbol number relative to the start of an SS/PBCH block | Subcarrier number relative to the start of an SS/PBCH block | +|-------------------|--------------------------------------------------------------|-------------------------------------------------------------| +| PSS | 0 | 56, 57, ..., 182 | +| SSS | 2 | 56, 57, ..., 182 | +| Set to 0 | 0 | 0, 1, ..., 55, 183, 184, ..., 239 | +| | 2 | 48, 49, ..., 55, 183, 184, ..., 191 | +| PBCH | 1, 3 | 0, 1, ..., 239 | +| | 2 | 0, 1, ..., 47,
192, 193, ..., 239 | +| DM-RS for PBCH | 1, 3 | | +| | 2 | | + +#### 7.4.3.1.1 Mapping of PSS within an SS/PBCH block + +The UE shall assume the sequence of symbols constituting the primary synchronization signal to be scaled by a factor to conform to the PSS power allocation specified in [5, TS 38.213] and mapped to resource elements in increasing order of where and are given by Table 7.4.3.1-1 and represent the frequency and time indices, respectively, within one SS/PBCH block. + +#### 7.4.3.1.2 Mapping of SSS within an SS/PBCH block + +The UE shall assume the sequence of symbols constituting the secondary synchronization signal to be scaled by a factor $\alpha$ and mapped to resource elements $(k, l)$ in increasing order of $k$ where $k$ and $l$ are given by Table 7.4.3.1-1 and represent the frequency and time indices, respectively, within one SS/PBCH block. + +#### 7.4.3.1.3 Mapping of PBCH and DM-RS within an SS/PBCH block + +The UE shall assume the sequence of complex-valued symbols constituting the physical broadcast channel to be scaled by a factor $\alpha$ to conform to the PBCH power allocation specified in [5, TS 38.213] and mapped in sequence starting with $k=0$ to resource elements $(k, l)$ which meet all the following criteria: + +- they are not used for PBCH demodulation reference signals + +The mapping to resource elements $(k, l)$ not reserved for PBCH DM-RS shall be in increasing order of first the index $l$ and then the index $k$ , where $k$ and $l$ represent the frequency and time indices, respectively, within one SS/PBCH block and are given by Table 7.4.3.1-1. + +The UE shall assume the sequence of complex-valued symbols constituting the demodulation reference signals for the SS/PBCH block to be scaled by a factor of $\alpha$ to conform to the PBCH power allocation specified in [5, TS 38.213] and to be mapped to resource elements $(k, l)$ in increasing order of first $l$ and then $k$ where $k$ and $l$ are given by Table 7.4.3.1-1 and represent the frequency and time indices, respectively, within one SS/PBCH block. + +#### 7.4.3.2 Time location of an SS/PBCH block + +The locations in the time domain where a UE shall monitor for a possible SS/PBCH block are described in clause 4.1 of [5, TS 38.213]. + +--- + +## 8 Sidelink + +### 8.1 Overview + +#### 8.1.1 Overview of physical channels + +A sidelink physical channel corresponds to a set of resource elements carrying information originating from higher layers. The following sidelink physical channels are defined: + +- Physical Sidelink Shared Channel, PSSCH +- Physical Sidelink Broadcast Channel, PSBCH +- Physical Sidelink Control Channel, PSCCH +- Physical Sidelink Feedback Channel, PSFCH + +#### 8.1.2 Overview of physical signals + +A sidelink physical signal corresponds to a set of resource elements used by the physical layer but does not carry information originating from higher layers. + +The following sidelink physical signals are defined: + +- Demodulation reference signals, DM-RS +- Channel-state information reference signal, CSI-RS +- Phase-tracking reference signals, PT-RS +- Sidelink primary synchronization signal, S-PSS +- Sidelink secondary synchronization signal, S-SSS +- Sidelink positioning reference signal, SL PRS + +## 8.2 Physical resources + +### 8.2.1 General + +In a shared SL PRS resource pool, the OFDM symbol immediately preceding the symbols which are configured for use by PSFCH if PSFCH is configured in this slot, and the last symbol configured for sidelink in a slot, serve as guard symbol(s). In a dedicated SL PRS resource pool, the last symbol configured for sidelink in a slot serves as a guard symbol. Otherwise, the OFDM symbol immediately following the last symbol used for PSSCH, PSFCH, or S-SSB serves as a guard symbol. + +The first OFDM symbol of a PSSCH and its associated PSCCH is duplicated as described in clauses 8.3.1.5 and 8.3.2.3. The first OFDM symbol of a PSFCH is duplicated as described in clause 8.3.4.2.2. + +The OFDM symbol immediately preceding an SL PRS transmission in a dedicated SL PRS resource pool is generated as described in clause 8.4.1.6.3. + +### 8.2.2 Numerologies + +Multiple OFDM numerologies are supported as given by Table 8.2.2-1 where $\mu$ and the cyclic prefix for a sidelink bandwidth part are obtained from the higher-layer parameter *sl-BWP*. + +**Table 8.2.2-1: Supported transmission numerologies.** + +| $\mu$ | [kHz] | Cyclic prefix | +|-------|-------|------------------| +| 0 | 15 | Normal | +| 1 | 30 | Normal | +| 2 | 60 | Normal, Extended | +| 3 | 120 | Normal | + +### 8.2.3 Frame structure + +#### 8.2.3.1 Frames and subframes + +The frame and subframe structure for sidelink transmission is defined in clause 4.3.1. + +#### 8.2.3.2 Slots + +The slot structure for sidelink transmission is defined in clause 4.3.2. + +### 8.2.4 Antenna ports + +An antenna port is defined in clause 4.4.1. + +The following antenna ports are defined for the sidelink: + +- Antenna ports starting with 1000 for PSSCH +- Antenna ports starting with 2000 for PSCCH +- Antenna ports starting with 3000 for CSI-RS +- Antenna ports starting with 4000 for S-SS/PSBCH block +- Antenna ports starting with 5000 for PSFCH +- Antenna ports starting with 6000 for SL PRS + +For DM-RS associated with a PSBCH, the channel over which a PSBCH symbol on one antenna port is conveyed can be inferred from the channel over which a DM-RS symbol on the same antenna port is conveyed only if the two symbols are within a S-SS/PSBCH block transmitted within the same slot, and with the same block index according to clause 8.4.3.1. + +For DM-RS associated with a PSSCH, the channel over which a PSSCH symbol on one antenna port is conveyed can be inferred from the channel over which a DM-RS symbol on the same antenna port is conveyed only if the two symbols are within the same frequency resource as the scheduled PSSCH and in the same slot. + +For DM-RS associated with a PSCCH, the channel over which a PSCCH symbol on one antenna port is conveyed can be inferred from the channel over which a DM-RS symbol on the same antenna port is conveyed only if the two symbols are within the same frequency resource as the transmitted PSCCH and in the same slot. + +## 8.2.5 Resource grid + +The resource grid for sidelink transmission is defined in clause 4.4.2. + +For sidelink, the carrier bandwidth and the starting position for subcarrier spacing configuration are obtained from the higher-layer parameter *sl-SCS-SpecificCarrierList*. + +For the sidelink, the higher-layer parameter *sl-TxDirectCurrentLocation* indicates the location of the transmitter DC subcarrier in the sidelink for each of the configured bandwidth parts. Values in the range 0 – 3299 represent the number of the DC subcarrier, the value 3300 indicates that the DC subcarrier is located outside the resource grid, and the value 3301 indicates that the position of the DC subcarrier in the sidelink is undetermined. The DC subcarrier location offset relative to the center of the indicated subcarrier is given by *if frequencyShift7p5khzSL* is provided and by *otherwise*, where *valueN* is given by the higher-layer parameter *valueN*. + +## 8.2.6 Resource elements + +Resource elements are defined in clause 4.4.3. + +## 8.2.7 Resource blocks + +Resource blocks are defined in clause 4.4.4. + +Point A for sidelink transmission/reception is obtained from the higher-layer parameter *sl-AbsoluteFrequencyPointA*. + +## 8.2.8 Bandwidth part + +Configuration of the single bandwidth part for sidelink transmission is described in clause 16 of [5, TS 38.213]. + +# 8.3 Physical channels + +## 8.3.1 Physical sidelink shared channel + +### 8.3.1.1 Scrambling + +For the single codeword, the block of bits, where *N* is the number of bits in codeword transmitted on the physical channel as defined in [4, TS 38.212], shall be scrambled prior to modulation. + +Scrambling shall be done according to the following pseudo code + +``` + +set +set +while + if // SCI placeholder bits + + else + +end if + +``` + +$i = i + 1$ + +end while + +where the scrambling sequence is given by clause 5.2.1 and + +- for +- +- The scrambling sequence generator shall be initialized with + +where and the quantity equals the decimal representation of the CRC on the PSCCH associated with the PSSCH according to with and given by clause 8.3.2 in [4, TS 38.212]. + +- for +- +- The scrambling sequence generator shall be initialized with + +where and the quantity equals the decimal representation of the CRC on the PSCCH associated with the PSSCH according to with and given by clause 8.3.2 in [4, TS 38.212]. + +### 8.3.1.2 Modulation + +For the single codeword , the block of scrambled bits shall be modulated, resulting in a block of complex-valued modulation symbols where . + +Modulation for shall be done as described in clause 5.1 using QPSK, where . + +Modulation for shall be done as described in clause 5.1 using one of the modulation schemes in Table 8.3.1.2-1 where . + +**Table 8.3.1.2-1: Supported modulation schemes.** + +| Modulation scheme | Modulation order | +|-------------------|------------------| +| QPSK | 2 | +| 16QAM | 4 | +| 64QAM | 6 | +| 256QAM | 8 | + +### 8.3.1.3 Layer mapping + +Layer mapping shall be done according to clause 7.3.1.3 with the number of layers , resulting in , . + +### 8.3.1.4 Precoding + +The block of vectors shall be precoded according to clause 6.3.1.5 where the precoding matrix equals the identity matrix and . + +### 8.3.1.5 Mapping to virtual resource blocks + +For each of the antenna ports used for transmission of the PSSCH, the block of complex-valued symbols shall be multiplied with the amplitude scaling factor in order to conform to the transmit power specified in [5, TS 38.213] and mapped to resource elements in the virtual resource blocks assigned for transmission, where is the first subcarrier in the lowest-numbered virtual resource block assigned for transmission. + +The mapping operation shall be done in two steps: + +- first, the complex-valued symbols corresponding to the bit for the 2nd-stage SCI in increasing order of first the index over the assigned virtual resource blocks and then the index , starting from the first PSSCH symbol carrying an associated DM-RS and meeting all of the following criteria: + - the corresponding resource elements in the corresponding physical resource blocks are not used for transmission of the associated DM-RS, PT-RS, or PSCCH; +- secondly, the complex-valued modulation symbols not corresponding to the 2nd-stage SCI shall be in increasing order of first the index over the assigned virtual resource blocks, and then the index with the starting position given by [6, TS 38.214] and meeting all of the following criteria: + - the resource elements are not used for 2nd-stage SCI in the first step; + - the resource elements are not in the symbols used for transmission of the associated SL PRS according to clause 8.2.4.1.1 of [6, TS 38.214]; + - the corresponding resource elements in the corresponding physical resource blocks are not used for transmission of the associated DM-RS, PT-RS, CSI-RS, or PSCCH. + +The resource elements used for the PSSCH in the first OFDM symbol in the mapping operation above, including any DM-RS, PT-RS, or CSI-RS occurring in the first OFDM symbol, shall be duplicated in the OFDM symbol immediately preceding the first OFDM symbol in the mapping. + +### 8.3.1.6 Mapping from virtual to physical resource blocks + +Virtual resource blocks shall be mapped to physical resource blocks according to non-interleaved mapping. + +For non-interleaved VRB-to-PRB mapping, virtual resource block is mapped to physical resource block . + +## 8.3.2 Physical sidelink control channel + +### 8.3.2.1 Scrambling + +The block of bits , where is the number of bits transmitted on the physical channel, shall be scrambled prior to modulation, resulting in a block of scrambled bits according to + +where the scrambling sequence is given by clause 5.2.1. The scrambling sequence generator shall be initialized with + +### 8.3.2.2 Modulation + +The block of scrambled bits shall be modulated as described in clause 5.1 using QPSK, resulting in a block of complex-valued modulation symbols where . + +### 8.3.2.3 Mapping to physical resources + +The set of complex-valued modulation symbols shall be multiplied with the amplitude scaling factor in order to conform to the transmit power specified in [5, TS 38.213] and mapped in sequence starting with to resource elements assigned for transmission according to clause 16.4 of [5, TS 38.213], and not used for the demodulation reference signals associated with PSCCH, in increasing order of first the index over the assigned physical resources, and then the index on antenna port. + +The resource elements used for the PSCCH in the first OFDM symbol in the mapping operation above, including any DM-RS, PT-RS, or CSI-RS occurring in the first OFDM symbol, shall be duplicated in the immediately preceding OFDM symbol. + +## 8.3.3 Physical sidelink broadcast channel + +### 8.3.3.1 Scrambling + +The block of bits, where is the number of bits transmitted on the physical sidelink broadcast channel, shall be scrambled prior to modulation, resulting in a block of scrambled bits according to + +where the scrambling sequence is given by clause 5.2.1. The scrambling sequence generator shall be initialized with at the start of each S-SS/PSBCH block. + +### 8.3.3.2 Modulation + +The block of bits shall be QPSK modulated as described in clause 5.1.3, resulting in a block of complex-valued modulation symbols where . + +### 8.3.3.3 Mapping to physical resources + +Mapping to physical resources is described in clause 8.4.3. + +## 8.3.4 Physical sidelink feedback channel + +### 8.3.4.1 General + +### 8.3.4.2 PSFCH format 0 + +#### 8.3.4.2.1 Sequence generation + +The sequence shall be generated according to + +where is given by clause 6.3.2.2 with the following exceptions: + +- is given by clause 16.3 of [5, TS 38.213]; +- is given by clause 16.3 of [5, TS 38.213]; +- is given by + - if the higher-layer parameter *transmissionStructureForPSFCH* is configured and set to ‘*dedicated interlace*’ and where is the resource block number within the interlace; + - otherwise +- ; +- is the index of the OFDM symbol in the slot that corresponds to the second OFDM symbol of the PSFCH transmission in the slot given by [5, TS 38.213]; +- and with given by the higher-layer parameter *sl-PSFCH-HopID* if configured; otherwise, . +- with given by the higher-layer parameter *sl-PSFCH-HopID* if configured; otherwise, . + +#### 8.3.4.2.2 Mapping to physical resources + +The sequence shall be multiplied with the amplitude scaling factor in order to conform to the transmit power specified in [5, TS 38.213] and mapped in sequence starting with to resource elements assigned for transmission of the second PSFCH symbol according to clause 16.3 of [5, TS 38.213] in increasing order of the index over the assigned physical resources on antenna port. + +The resource elements used for the PSFCH in the OFDM symbol in the mapping operation above shall be duplicated in the immediately preceding OFDM symbol. + +## 8.4 Physical signals + +### 8.4.1 Reference signals + +#### 8.4.1.1 Demodulation reference signals for PSSCH + +##### 8.4.1.1.1 Sequence generation + +The sequence $c(n)$ shall be generated according to + +where the pseudo-random sequence $c_i(n)$ is defined in clause 5.2.1. The pseudo-random sequence generator shall be initialized with + +where $n$ is the OFDM symbol number within the slot, $s$ is the slot number within a frame, and $c_{init}$ where the quantity $c_{init}$ equals the decimal representation of CRC on the PSCCH associated with the PSSCH according to $n_{ID}$ with $n_{ID}$ given by clause 7.3.2 in [4, TS 38.212]. + +##### 8.4.1.1.2 Mapping to physical resources + +The sequence $c(n)$ shall be mapped to the intermediate quantity $\tilde{c}(n)$ according to clause 6.4.1.1.3 using configuration type 1 without transform precoding, and where $\tilde{c}(n)$ , $n$ , and $s$ are given by Table 8.4.1.1.2-2, and $n_{ID}$ is specified in clause 8.4.1.1.1. + +The patterns used for the PSSCH DM-RS is indicated in the SCI as described in clause 8.3.1.1 of [4, TS 38.212]. + +The intermediate quantity $\tilde{c}(n)$ shall be precoded, multiplied with the amplitude scaling factor $\alpha$ specified in clause 8.3.1.5, and mapped to physical resources according to + +where + +- the precoding matrix $\mathbf{W}$ is given by clause 8.3.1.4, +- the set of antenna ports $\mathcal{P}$ is given by clause 8.3.1.4, and +- the set of antenna ports $\mathcal{P}$ is given by [6, TS 38.214]; + +and the following conditions are fulfilled: + +- the resource elements $(k, l)$ are within the common resource blocks allocated for PSSCH transmission. + +The quantity $k$ is defined relative to subcarrier 0 in common resource block 0 and the quantity $l$ is defined relative to the start of the scheduled resources for transmission of PSSCH and the associated PSCCH, including the OFDM symbol duplicated as described in clauses 8.3.1.5 and 8.3.2.3. + +The position(s) of the DM-RS symbols is given by $l_{DMRS}$ according to Table 8.4.1.1.2-1 where the number of PSSCH DM-RS is indicated in the SCI, and $l_{DMRS}$ is the duration of the scheduled resources for transmission of PSSCH according to clause 8.1.2.1 of [6, TS 38.214] and the associated PSCCH, including the OFDM symbol duplicated as described in clauses 8.3.1.5 and 8.3.2.3. + +**Table 8.4.1.1.2-1: PSSCH DM-RS time-domain location.** + +| in symbols | DM-RS position | | | | | | +|------------|--------------------------|----------|-------------|--------------------------|----------|-------------| +| | PSCCH duration 2 symbols | | | PSCCH duration 3 symbols | | | +| | Number of PSSCH DM-RS | | | Number of PSSCH DM-RS | | | +| | 2 | 3 | 4 | 2 | 3 | 4 | +| 6 | 1, 5 | | | 1, 5 | | | +| 7 | 1, 5 | | | 1, 5 | | | +| 8 | 1, 5 | | | 1, 5 | | | +| 9 | 3, 8 | 1, 4, 7 | | 4, 8 | 1, 4, 7 | | +| 10 | 3, 8 | 1, 4, 7 | | 4, 8 | 1, 4, 7 | | +| 11 | 3, 10 | 1, 5, 9 | 1, 4, 7, 10 | 4, 10 | 1, 5, 9 | 1, 4, 7, 10 | +| 12 | 3, 10 | 1, 5, 9 | 1, 4, 7, 10 | 4, 10 | 1, 5, 9 | 1, 4, 7, 10 | +| 13 | 3, 10 | 1, 6, 11 | 1, 4, 7, 10 | 4, 10 | 1, 6, 11 | 1, 4, 7, 10 | + +**Table 8.4.1.1.2-2: Parameters for PSSCH DM-RS.** + +| | CDM group | | | | | +|------|-----------|---|----|----|----| +| 1000 | 0 | 0 | +1 | +1 | +1 | +| 1001 | 0 | 0 | +1 | -1 | +1 | + +## 8.4.1.2 Phase-tracking reference signals for PSSCH + +### 8.4.1.2.1 Sequence generation + +The precoded sidelink phase-tracking reference signal for subcarrier $m$ on layer $l$ is given by + +where + +- antenna ports $p$ or $p'$ associated with PT-RS transmission are given by clause 8.2.3 of [6, TS 38.214]; +- $c_{n, l}$ is given by clause 8.4.1.1.1 at the position of the first PSSCH symbol carrying an associated DM-RS. + +### 8.4.1.2.2 Mapping to physical resources + +The UE shall transmit phase-tracking reference signals only in the resource blocks used for the PSSCH, and only if the procedure in [6, TS 38.214] indicates that phase-tracking reference signals are being used. + +The PSSCH PT-RS shall be mapped to resource elements according to + +when all the following conditions are fulfilled + +- $n$ is within the OFDM symbols allocated for the PSSCH transmission; +- resource element $m$ is not used for PSCCH, nor DM-RS associated with PSSCH; +- $l$ and $p$ correspond to + +The precoding matrix $W$ is given by clause 8.3.1.4. + +The set of time indices $\mathcal{N}$ defined relative to the start of the PSSCH allocation is defined by + +1. set $\mathcal{N} = \emptyset$ and +2. if any symbol in the interval $[n_{start}, n_{end}]$ overlaps with a symbol used for DM-RS according to clause 8.4.1.1.2 + - set + +- set $l$ to the symbol index of the DM-RS symbol + - repeat from step 2 as long as $l$ is inside the PSSCH allocation +3. add $l$ to the set of time indices for PT-RS + 4. increment $l$ by one + 5. repeat from step 2 above as long as $l$ is inside the PSSCH allocation + +where $l$ is given by clause 8.4.3 of [6, TS 38.214]. + +For the purpose of PT-RS mapping, the resource blocks allocated for PSSCH transmission are numbered from 0 to $N_{RB}^{PSSCH}-1$ from the lowest scheduled resource block to the highest. The corresponding subcarriers in this set of resource blocks are numbered in increasing order starting from the lowest frequency from 0 to $N_{SC}^{PSSCH}-1$ . The subcarriers to which the PT-RS shall be mapped are given by + +where + +- $l$ +- is given by Table 8.4.1.2.2-1 for the DM-RS port associated with the PT-RS port according to clause 8.2.3 in [6, TS 38.214]. +- is the number of resource blocks scheduled; +- is given by [6, TS 38.214]; +- where the quantity $c$ equals the decimal representation of CRC on the PSCCH associated with the PSSCH according to $c_{PSCCH}$ with $c_{PSSCH}$ given by clause 7.3.2 in [4, TS 38.212]. + +PSSCH PT-RS shall not be mapped to resource elements containing PSCCH or PSCCH DMRS by puncturing PSSCH PT-RS. + +A UE is not expected to receive sidelink CSI-RS and PSSCH PT-RS on the same resource elements. + +**Table 8.4.1.2.2-1: The parameter $resourceElementOffset$ .** + +| DM-RS antenna port | resourceElementOffset | | | | +|--------------------|------------------------------|----------|----------|----------| +| | offset00 | offset01 | offset10 | offset11 | +| 0 | 0 | 2 | 6 | 8 | +| 1 | 2 | 4 | 8 | 10 | + +#### 8.4.1.3 Demodulation reference signals for PSCCH + +##### 8.4.1.3.1 Sequence generation + +The sequence $c_{PSCCH}$ shall be generated according to + +where the pseudo-random sequence $c(n)$ is defined in clause 5.2.1. The pseudo-random sequence generator shall be initialized with + +where + +- $l$ is the OFDM symbol number within the slot, +- $n_{slot}$ is the slot number within a frame, and + +- is given by the higher-layer parameter *sl-DMRS-ScrambleID*. + +#### 8.4.1.3.2 Mapping to physical resources + +The sequence shall be multiplied with the amplitude scaling factor in order to conform to the transmit power specified in [5, 38.213] and mapped in sequence starting with to resource elements in a slot on antenna port according to + +where the following conditions are fulfilled + +- they are within the resource elements constituting the PSCCH + +The quantity is given by Table 8.4.1.3.2-1 and shall be randomly selected by the UE. + +The reference point for is subcarrier 0 in common resource block 0. + +The quantity is the OFDM symbol number within the slot. + +**Table 8.4.1.3.2-1: The quantity .** + +| | | | | +|---|---|---|---| +| | | | | +| 0 | 1 | 1 | 1 | +| 1 | 1 | | | +| 2 | 1 | | | + +#### 8.4.1.4 Demodulation reference signals for PSBCH + +##### 8.4.1.4.1 Sequence generation + +The reference-signal sequence for an S-SS/PSBCH block is defined by + +where is given by clause 5.2. The scrambling sequence generator shall be initialized at the start of each S-SS/PSBCH block occasion with + +##### 8.4.1.4.2 Mapping to physical resources + +Mapping to physical resources is described in clause 8.4.3. + +#### 8.4.1.5 CSI reference signals + +##### 8.4.1.5.1 General + +##### 8.4.1.5.2 Sequence generation + +The sequence shall be generated according to + +where the pseudo-random sequence is defined in clause 5.2.1. The pseudo-random sequence generator shall be initialised with + +at the start of each OFDM symbol where is the slot number within a radio frame, is the OFDM symbol number within a slot, and where the quantity equals the decimal representation of CRC for the sidelink control information mapped to the PSCCH associated with the CSI-RS according to with and given by clause 7.3.2 in [4, TS 38.212]. + +##### 8.4.1.5.3 Mapping to physical resources + +Mapping to resource elements shall be done according to clause 7.4.1.5.3 with the following exceptions: + +- only 1 and 2 antenna ports are supported, ; +- only density is supported; +- zero-power CSI-RS is not supported; +- the quantity is an amplitude scaling factor to conform with the transmit power specified in clause 8.2.1 of [6, TS 38.214]. + +#### 8.4.1.6 Positioning reference signals + +##### 8.4.1.6.1 General + +A SL PRS resource refers to a time-frequency resource within a slot, used for SL PRS transmission. + +##### 8.4.1.6.2 Sequence generation + +The sequence is defined by + +where the pseudo-random sequence is defined in clause 5.2.1. The pseudo-random sequence generator shall be initialised with + +where + +- is the slot number within the radio frame +- is the OFDM symbol number within the slot to which the sequence is mapped +- is the sidelink PRS sequence ID, which, if not provided by higher layers, is obtained from the decimal representation of the CRC for the sidelink control information mapped to the PSCCH associated with the SL PRS according to with and given by clause 7.3.2 in [4, TS 38.212]. + +##### 8.4.1.6.3 Mapping to physical resources + +The sequence shall be multiplied with the amplitude scaling factor in order to conform to the transmit power specified in [5, TS 38.213] and mapped to resources elements according to + +when the following conditions are fulfilled: + +- the resource element is within the common resource blocks occupied by the SL PRS resource + +and where + +- the comb size is provided by the higher layers +- the resource-element offset +- the frequency offset is given by Table 8.4.1.6.3-1 +- the starting symbol is provided by higher layers for a dedicated SL PRS resource pool, or is determined such that the symbols {} are mapped to the last consecutive symbols in the slot that can be used for SL PRS for a shared SL PRS resource pool as described in clause 8.2.4.1.1 in [6, TS38.214] +- the number of symbols is provided by higher layers and limited to combinations fulfilling + - in a dedicated SL PRS resource pool: {1, 2}, {2, 2}, {2, 4}, {4, 4}, {6, 6}, and combinations with and where + - in a shared SL PRS resource pool: {1, 1}, {1, 2}, {2, 1}, {2, 2}, {2, 4}, {4, 1}, {4, 2}, {4, 4} +- the antenna port + +The reference point for $k$ is subcarrier 0 in common resource block 0. + +For transmission of an SL PRS in a dedicated SL PRS resource pool, the content of the OFDM symbol immediately preceding the SL PRS resource shall be generated and mapped to resource elements with + +- the time-domain index +- the set of frequency-domain indices shall be identical to those of the last OFDM symbol in the SL PRS resource + +**Table 8.4.1.6.3-1: The frequency offset as a function of $n$ .** + +| | Symbol number within the sidelink PRS resource | | | | | | | | | +|---|------------------------------------------------|---|---|---|---|---|---|---|---| +| | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 2 | 0 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | 0 | +| 4 | 0 | 2 | 1 | 3 | 0 | 2 | 1 | 3 | 0 | +| 6 | 0 | 3 | 1 | 4 | 2 | 5 | 0 | 3 | 1 | + +## 8.4.2 Synchronization signals + +### 8.4.2.1 Physical-layer sidelink synchronization identities + +There are 672 unique physical-layer sidelink synchronization identities given by + +where $n$ and $m$ . The sidelink synchronization identities are divided into two sets, $id\_net$ consisting of $n$ and $id\_oon$ consisting of $m$ . + +### 8.4.2.2 Sidelink primary synchronization signal + +#### 8.4.2.2.1 Sequence generation + +The sequence $c_{n,m}$ for the sidelink primary synchronization signal is defined by + +where + +and + +#### 8.4.2.2.2 Mapping to physical resources + +Mapping to physical resources is described in clause 8.4.3. + +### 8.4.2.3 Sidelink secondary synchronization signal + +#### 8.4.2.3.1 Sequence generation + +The sequence $c_{n,m}$ for the sidelink secondary synchronization signal is defined by + +where + +and + +#### 8.4.2.3.2 Mapping to physical resources + +Mapping to physical resources is described in clause 8.4.3. + +### 8.4.3 S-SS/PSBCH block + +#### 8.4.3.1 Time-frequency structure of an S-SS/PSBCH block + +In the time domain, an S-SS/PSBCH block consists of OFDM symbols, numbered in increasing order from 0 to $N_{\text{symbols}}$ within the S-SS/PSBCH block, where S-PSS, S-SSS, and PSBCH with associated DM-RS are mapped to symbols as given by Table 8.4.3.1-1. The number of OFDM symbols in an S-SS/PSBCH block for normal cyclic prefix and for extended cyclic prefix. The first OFDM symbol in an S-SS/PSBCH block is the first OFDM symbol in the slot. + +In the frequency domain, an S-SS/PSBCH block consists of 132 contiguous subcarriers with the subcarriers numbered in increasing order from 0 to 131 within the sidelink S-SS/PSBCH block. The quantities $k$ and $l$ represent the frequency and time indices, respectively, within one sidelink S-SS/PSBCH block. + +For an S-SS/PSBCH block, the UE shall use + +- antenna port 4000 for transmission of S-PSS, S-SSS, PSBCH and DM-RS for PSBCH; +- the same cyclic prefix length and subcarrier spacing for the S-PSS, S-SSS, PSBCH and DM-RS for PSBCH, + +**Table 8.4.3.1-1: Resources within an S-SS/PSBCH block for S-PSS, S-SSS, PSBCH, and DM-RS.** + +| Channel or signal | OFDM symbol number relative to the start of an S-SS/PSBCH block | Subcarrier number relative to the start of an S-SS/PSBCH block | +|-------------------|-----------------------------------------------------------------|----------------------------------------------------------------| +| S-PSS | 1, 2 | 2, 3, ..., 127, 128 | +| S-SSS | 3, 4 | 2, 3, ..., 127, 128 | +| Set to zero | 1, 2, 3, 4 | 0, 1, 129, 130, 131 | +| PSBCH | 0, 5, 6, ..., | 0, 1, ..., 131 | +| DM-RS for PSBCH | 0, 5, 6, ..., | 0, 4, 8, ..., 128 | + +#### 8.4.3.1.1 Mapping of S-PSS within an S-SS/PSBCH block + +The sequence of symbols constituting the sidelink primary synchronization signal in one OFDM symbol shall be scaled by a factor to conform to the S-PSS power allocation specified in [5, TS 38.213] and mapped to resource elements in increasing order of $k$ in each of the symbols, where $k$ and $l$ are given by Table 8.4.3.1-1 and represent the frequency and time indices, respectively, within one S-SS/PSBCH block. + +#### 8.4.3.1.2 Mapping of S-SSS within an S-SS/PSBCH block + +The sequence of symbols constituting the sidelink secondary synchronization signal in one OFDM symbol shall be scaled by a factor to conform to the S-SSS power allocation specified in [5, TS 38.213] and mapped to resource elements in increasing order of $k$ in each of the symbols, where $k$ and $l$ are given by Table 8.4.3.1-1 and represent the frequency and time indices, respectively, within one S-SS/PSBCH block. + +#### 8.4.3.1.3 Mapping of PSBCH and DM-RS within an S-SS/PSBCH block + +The sequence of complex-valued symbols constituting the physical sidelink broadcast channel shall be scaled by a factor to conform to the PSBCH power allocation specified in [5, TS 38.213] and mapped in sequence starting with $k=0$ to resource elements which meet all the following criteria: + +- they are not used for PSBCH demodulation reference signals + +The mapping to resource elements not reserved for PSBCH DM-RS shall be in increasing order of first the index $l$ and then the index $k$ , where $k$ and $l$ represent the frequency and time indices, respectively, within one S-SS/PSBCH block and are given by Table 8.4.3.1-1. + +The sequence of complex-valued symbols constituting the demodulation reference signals for the S-SS/PSBCH block shall be scaled by a factor of $\alpha$ to conform to the PSBCH power allocation specified in [5, TS 38.213] and mapped to resource elements $(k, l)$ in increasing order of first $k$ and then $l$ where $k$ and $l$ are given by Table 8.4.3.1-1 and represent the frequency and time indices, respectively, within one S-SS/PSBCH block. + +#### 8.4.3.2 Time location of an S-SS/PSBCH block + +The locations in the time domain where a UE shall monitor for a possible S-SS/PSBCH block are described in clause 16.1 of [5, TS 38.213]. + +### 8.5 Timing + +Transmission of a sidelink radio frame number $n$ from the UE shall start $\Delta t$ seconds before the start of the corresponding timing reference frame at the UE. The UE is not required to receive sidelink or downlink transmissions earlier than the value of $\Delta t$ , which is given in [12, TS 38.133], after the end of a sidelink transmission. + +For sidelink transmissions: + +If the UE has a serving cell fulfilling the S criterion according to clause 8.2 of [13, TS 38.304] + +- The timing of reference radio frame $n$ equals that of downlink radio frame $n$ in the cell with the same uplink carrier frequency as the sidelink and +- $\Delta t$ is given by clause 4.3.1 of [TS 38.211], + +Otherwise + +- The timing of reference radio frame $i$ and $\Delta t$ value are given by clause 12.2.2, 12.2.3, 12.2.4 or 12.2.5 of [12, TS 38.133]. + +![A dashed rectangular box, likely a placeholder for a diagram or figure related to sidelink timing relations.](85b4e4eafb7d71fbf621097515942e50_img.jpg) + +A dashed rectangular box, likely a placeholder for a diagram or figure related to sidelink timing relations. + +**Figure 8.5-1: Sidelink timing relation** + +The quantity $\Delta t$ equals to 0. + +--- + +## Annex A: Change history + +| Change history | | | | | | | | +|----------------|----------|------------|------|-----|-----|----------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-04 | RAN1#89 | R1-1708219 | | | | Draft skeleton | 0.0.0 | +| 2017-05 | AH_1706 | R1-1711366 | | | | Inclusion of agreements up to and including RAN1#89 | 0.0.1 | +| 2017-06 | AH_1706 | R1-1711886 | | | | Updated editor's version | 0.0.2 | +| 2017-06 | AH_1706 | R1-1712004 | | | | Clean version further to RAN1's endorsement | 0.1.0 | +| 2017-07 | AH_1706 | R1-1712011 | | | | Inclusion of agreements up to and including RAN1 NR AdHoc #2 | 0.1.1 | +| 2017-08 | AH_1706 | R1-1712950 | | | | Updated editor's version | 0.1.2 | +| 2017-08 | RAN1#90 | R1-1713296 | | | | Updated editor's version | 0.1.3 | +| 2017-08 | RAN1#90 | R1-1714656 | | | | Endorsed by RAN1#90 | 0.2.0 | +| 2017-08 | RAN1#90 | R1-1715321 | | | | Inclusion of agreements from RAN1#90 | 0.2.1 | +| 2017-09 | RAN1#90 | R1-1715329 | | | | Updated editor's version | 0.2.2 | +| 2017-09 | RAN#77 | RP-171994 | | | | For information to plenary | 1.0.0 | +| 2017-09 | AH_1709 | R1-1716927 | | | | Inclusion of agreements from AdHoc#3 | 1.0.1 | +| 2017-09 | AH_1709 | R1-1718318 | | | | Updated editor's version | 1.0.2 | +| 2017-10 | RAN1#90b | R1-1719105 | | | | Endorsed by RAN1#90bis | 1.1.0 | +| 2017-10 | RAN1#90b | R1-1719224 | | | | Inclusion of agreements from RAN1#90bis | 1.1.1 | +| 2017-11 | RAN1#90b | R1-1719685 | | | | Updated editor's version | 1.1.2 | +| 2017-11 | RAN1#90b | R1-1720850 | | | | Updated editor's version | 1.1.3 | +| 2017-11 | RAN1#90b | R1-1721048 | | | | Endorsed by RAN1#90bis | 1.2.0 | +| 2017-12 | RAN1#91 | R1-17xxxxx | | | | Inclusion of agreements from RAN1#91 | 1.2.1 | +| 2017-12 | RAN1#91 | R1-1721341 | | | | Endorsed by RAN1#91 | 1.3.0 | +| 2017-12 | RAN#78 | RP-172284 | | | | 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.211 capturing the RAN1#92bis and RAN1#93 meeting agreements | 15.2.0 | +| 2018-09 | RAN#81 | RP-181789 | 0003 | - | F | Corrections according to agreements from RAN1#94 | 15.3.0 | +| 2018-12 | RAN#82 | RP-182523 | 0004 | 1 | F | Combined CR of all essential corrections to 38.211 from RAN1#94bis and RAN1#95 | 15.4.0 | +| 2019-03 | RAN#83 | RP-190447 | 0005 | - | F | CR for PUCCH Format 1 | 15.5.0 | +| 2019-03 | RAN#83 | RP-190447 | 0006 | - | F | CR on PDSCH mapping to virtual resource blocks | 15.5.0 | +| 2019-03 | RAN#83 | RP-190447 | 0007 | 2 | F | Alignment of terminology across specifications | 15.5.0 | +| 2019-03 | RAN#83 | RP-190447 | 0008 | - | F | Correction on physical resource mapping for PUSCH with configured grant | 15.5.0 | +| 2019-03 | RAN#83 | RP-190773 | 0009 | 1 | F | Correction to frequency-domain starting position for SRS resource mapping | 15.5.0 | +| 2019-06 | RAN#84 | RP-191281 | 0010 | - | F | CR on PUCCH format 1 | 15.6.0 | +| 2019-06 | RAN#84 | RP-191281 | 0011 | - | F | Correction on reference name of UE capability of additional DMRS for co-existence with LTE CRS | 15.6.0 | +| 2019-06 | RAN#84 | RP-191281 | 0012 | - | F | Correction on mapping from virtual to physical resource blocks | 15.6.0 | +| 2019-06 | RAN#84 | RP-191281 | 0014 | 2 | F | Corrections to 38.211 including alignment of terminology across specifications | 15.6.0 | +| 2019-06 | RAN#84 | RP-191281 | 0015 | - | F | Clarification regarding non-full-duplex UE communication | 15.6.0 | +| 2019-06 | RAN#84 | RP-191281 | 0016 | - | F | Corrections on PUSCH scheduled by RAR UL grant and Msg3 PUSCH retransmission | 15.6.0 | +| 2019-09 | RAN#85 | RP-191940 | 0017 | - | F | Correction on PUSCH scrambling | 15.7.0 | +| 2019-09 | RAN#85 | RP-191940 | 0018 | - | F | Correction on PDSCH resource allocation scheduled by PDCCH in Type 0 common search space | 15.7.0 | +| 2019-09 | RAN#85 | RP-191940 | 0019 | - | F | Corrections to 38.211 including alignment of terminology across specifications in RAN1#98 | 15.7.0 | +| 2019-12 | RAN#86 | RP-192624 | 0022 | - | F | Corrections to 38.211 including alignment of terminology across specifications in RAN1#98bis and RAN1#99 | 15.8.0 | +| 2019-12 | RAN#86 | RP-192634 | 0020 | 1 | B | Introduction of remote interference management | 16.0.0 | +| 2019-12 | RAN#86 | RP-192635 | 0023 | - | B | Introduction of two-step RACH | 16.0.0 | +| 2019-12 | RAN#86 | RP-192636 | 0024 | - | B | Introduction of NR-based access to unlicensed spectrum | 16.0.0 | +| 2019-12 | RAN#86 | RP-192637 | 0025 | - | B | Introduction of integrated access and backhaul for NR | 16.0.0 | +| 2019-12 | RAN#86 | RP-192638 | 0026 | - | B | Introduction of V2X | 16.0.0 | +| 2019-12 | RAN#86 | RP-192639 | 0027 | - | B | Introduction of eURLLC support | 16.0.0 | +| 2019-12 | RAN#86 | RP-192641 | 0028 | - | B | Introduction of MIMO enhancements | 16.0.0 | +| 2019-12 | RAN#86 | RP-192643 | 0029 | - | B | Introduction of NR positioning support | 16.0.0 | +| 2019-12 | RAN#86 | RP-192646 | 0030 | - | B | Introduction of enhanced support for dynamic spectrum sharing | 16.0.0 | + +| | | | | | | | | +|---------|----------|-----------|------|---|---|----------------------------------------------------------------------|--------| +| 2019-12 | RAN#86 | RP-192646 | 0031 | - | B | Introduction of additional RACH configurations for TDD FR1 | 16.0.0 | +| 2019-12 | RAN#86 | RP-192645 | 0032 | - | B | Introduction of cross-carrier scheduling with different numerologies | 16.0.0 | +| 2020-03 | RAN#87-e | RP-200186 | 0033 | - | F | Corrections to integrated access and backhaul for NR | 16.1.0 | +| 2020-03 | RAN#87-e | RP-200192 | 0034 | - | F | Corrections to NR positioning support | 16.1.0 | +| 2020-03 | RAN#87-e | RP-200184 | 0035 | - | F | Corrections to two-step RACH | 16.1.0 | +| 2020-03 | RAN#87-e | RP-200194 | 0036 | - | F | Corrections to cross-carrier scheduling with different numerologies | 16.1.0 | +| 2020-03 | RAN#87-e | RP-200185 | 0037 | - | F | Corrections to NR-based access to unlicensed spectrum | 16.1.0 | +| 2020-03 | RAN#87-e | RP-200187 | 0038 | - | F | Corrections to V2X | 16.1.0 | +| 2020-03 | RAN#87-e | RP-200190 | 0039 | - | F | Corrections to MIMO enhancements | 16.1.0 | +| 2020-06 | RAN#88-e | RP-200687 | 0040 | 1 | F | Corrections to NR-based access to unlicensed spectrum | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200694 | 0041 | 1 | F | Corrections to NR positioning support | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200692 | 0042 | 1 | F | Corrections to MIMO enhancements | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200686 | 0043 | 1 | F | Corrections to two-step RACH | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200696 | 0044 | 1 | F | Corrections to carrier aggregation with unaligned frame boundaries | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200689 | 0045 | 1 | F | Corrections to V2X | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200688 | 0046 | 1 | F | Corrections to integrated access and backhaul for NR | 16.2.0 | +| 2020-09 | RAN#89-e | RP-201804 | 0047 | - | F | CR on 2-step RACH for 38.211 | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201812 | 0048 | - | F | CR on correction half duplex operation during DAPS HO | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201807 | 0049 | - | F | Corrections to V2X | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201809 | 0050 | - | F | Corrections to MIMO enhancements | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201811 | 0051 | - | F | Corrections to NR positioning support | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201805 | 0052 | - | F | Corrections to NR-based access to unlicensed spectrum | 16.3.0 | +| 2020-12 | RAN#90-e | RP-202380 | 0053 | - | F | CR on the determination of DMRS sequences in 38.211 | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202383 | 0054 | - | F | Correction on sidelink timing definition | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202381 | 0055 | - | F | Correction to UE assumption on RB set configuration for PRACH | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202381 | 0057 | - | F | CR to 38.211 on NR-U PRACH RO configuration | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202383 | 0058 | - | F | Corrections on sidelink for PHY layer structure | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202383 | 0059 | - | F | Correction on SL PT-RS sequence generation | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202383 | 0060 | - | F | Correction on PSFCH mapping | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202387 | 0062 | - | F | Corrections to 38.211 for NR positioning | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202381 | 0063 | - | F | CR to 38.211 to correct CP extension for SRS | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202398 | 0064 | - | F | Alignment CR for TS 38.211 | 16.4.0 | +| 2021-03 | RAN#91-e | RP-210049 | 0065 | - | F | Correction on DM-RS presence with PDSCH mapping type B | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210049 | 0066 | - | F | Correction on usage of subCarrierSpacingCommon for unlicensed | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210050 | 0067 | - | F | Clarification on Sidelink SSID | 16.5.0 | + +| | | | | | | | | +|---------|----------|-----------|------|---|---|-----------------------------------------------------------------------------------|--------| +| 2021-03 | RAN#91-e | RP-210059 | 0068 | - | F | Alignment of notation | 16.5.0 | +| 2021-06 | RAN#92-e | RP-211248 | 0069 | - | F | Correction on RIM RS resource and set ID mapping | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211236 | 0070 | - | F | Correction on channel inference assumption for PUSCH repetition Type B | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211243 | 0071 | 1 | F | Alignment of notation | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211235 | 0072 | - | F | Correction on OFDM signal generation and PSSCH DM-RS time-domain OCC in TS 38.211 | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211233 | 0074 | - | A | Correction on channel properties assumption of UL transmission | 16.6.0 | +| 2021-09 | RAN#93-e | RP-211850 | 0076 | - | F | Alignment of notation | 16.7.0 | +| 2021-12 | RAN#94-e | RP-212958 | 0078 | - | A | Correction to CCE-to-REG mapping and CSI-RS mapping | 16.8.0 | +| 2021-12 | RAN#94-e | RP-212960 | 0079 | - | F | Correction to VRB-to-PRB mapping for DCI format 1_2 | 16.8.0 | +| 2021-12 | RAN#94-e | RP-212966 | 0080 | - | B | Introduction of MIMO enhancements | 17.0.0 | +| 2021-12 | RAN#94-e | RP-212967 | 0081 | - | B | Introduction of extensions to 71 GHz | 17.0.0 | +| 2021-12 | RAN#94-e | RP-212969 | 0082 | - | B | Introduction of Non-Terrestrial Networks (NTN) | 17.0.0 | +| 2021-12 | RAN#94-e | RP-212973 | 0083 | - | B | Introduction of coverage enhancements | 17.0.0 | +| 2021-12 | RAN#94-e | RP-212979 | 0084 | - | B | Introduction of Multicast and Broadcast Services (MBS) support | 17.0.0 | +| 2021-12 | RAN#94-e | RP-212982 | 0085 | - | B | Introduction of DL 1024QAM for NR FR1 | 17.0.0 | +| 2022-03 | RAN#95-e | RP-220920 | 0086 | 2 | C | Pi/2-BPSK specification updates for the merger of 5Gi into 3GPP | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220245 | 0088 | - | A | CR on corrections on SL timing | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220251 | 0089 | - | F | Corrections to NR in the 52.6 – 71 GHz range | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220263 | 0090 | - | F | Corrections to NR support of multicast and broadcast services | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220250 | 0091 | - | F | Corrections to MIMO enhancements | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220252 | 0092 | - | F | Corrections to IloT and URLLC enhancements | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220253 | 0093 | - | F | Corrections to NR NTN support | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220270 | 0094 | - | F | Corrections to small data transmissions in RRC_INACTIVE state | 17.1.0 | +| 2022-06 | RAN#96 | RP-221606 | 0095 | - | F | Corrections on NR UE Power Saving Enhancements | 17.2.0 | +| 2022-06 | RAN#96 | RP-221600 | 0096 | - | F | Corrections to MIMO enhancements | 17.2.0 | +| 2022-06 | RAN#96 | RP-221603 | 0097 | - | F | Corrections to timing advance for NTN | 17.2.0 | +| 2022-06 | RAN#96 | RP-221620 | 0099 | - | A | Clarification of PUSCH DM-RS generation | 17.2.0 | +| 2022-09 | RAN#97-e | RP-222401 | 0100 | - | F | Correction on the subcarrier offset, kssb | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222406 | 0101 | - | F | Corrections on UE Power Saving Enhancements for NR in TS 38.211 | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222412 | 0102 | - | F | Corrections to NR support of multicast and broadcast services | 17.3.0 | +| 2022-12 | RAN#98-e | RP-222863 | 0103 | - | F | Correction on sidelink timing | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222864 | 0104 | - | F | Corrections to NR support of multicast and broadcast services | 17.4.0 | +| 2023-06 | RAN#100 | RP-231226 | 0105 | 1 | F | Alignment of parameter names | 17.5.0 | +| 2023-09 | RAN#101 | RP-232449 | 0107 | - | F | Alignment of terminology across specifications | 17.6.0 | + +| | | | | | | | | +|---------|---------|-----------|------|---|---|--------------------------------------------------------------------------|--------| +| 2023-09 | RAN#101 | RP-232469 | 0108 | - | B | Introduction of NR sidelink evolution | 18.0.0 | +| 2023-09 | RAN#101 | RP-232480 | 0109 | - | B | Introduction of expanded and improved NR positioning | 18.0.0 | +| 2023-09 | RAN#101 | RP-232458 | 0110 | - | B | Introduction of MIMO evolution for downlink and uplink | 18.0.0 | +| 2023-09 | RAN#101 | RP-232477 | 0111 | - | B | Introduction of NR support for dedicated spectrum less than 5MHz for FR1 | 18.0.0 | +| 2023-09 | RAN#101 | RP-232470 | 0112 | - | B | Introduction of dynamic spectrum sharing enhancements | 18.0.0 | +| 2023-09 | RAN#101 | RP-232471 | 0113 | - | B | Introduction of multi-carrier enhancements | 18.0.0 | +| 2023-12 | RAN#102 | RP-233722 | 0114 | - | B | Introduction of additional PRS configurations [1symbol_PRS] | 18.1.0 | +| 2023-12 | RAN#102 | RP-233707 | 0115 | - | F | Corrections to NR Dynamic Spectrum Sharing (DSS) | 18.1.0 | +| 2023-12 | RAN#102 | RP-233716 | 0116 | - | F | Corrections to NR support for dedicated spectrum less than 5MHz for FR1 | 18.1.0 | +| 2023-12 | RAN#102 | RP-233705 | 0117 | - | F | Corrections to MIMO enhancements | 18.1.0 | +| 2023-12 | RAN#102 | RP-233718 | 0118 | - | F | Corrections to NR Network-controlled Repeaters | 18.1.0 | +| 2023-12 | RAN#102 | RP-233719 | 0119 | - | F | Corrections to positioning enhancements | 18.1.0 | +| 2023-12 | RAN#102 | RP-233733 | 0120 | - | B | Introduction of multicast reception in RRC_INACTIVE | 18.1.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38300/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-18/38_series/38300/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..118710cc84f683b53861efa37213f235e12fc696 --- /dev/null +++ b/marked/Rel-18/38_series/38300/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:40a8e1cf4bae2f6718607d4c749d0b00e151362e06cb202eb8fe8fece928d7c8 +size 5433 diff --git a/marked/Rel-18/38_series/38300/03a73cf37615028406f13c2aea732d60_img.jpg b/marked/Rel-18/38_series/38300/03a73cf37615028406f13c2aea732d60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..497fe1aa01aaf9ffcccf29057160030279766611 --- /dev/null +++ b/marked/Rel-18/38_series/38300/03a73cf37615028406f13c2aea732d60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1587d7b8f00054b3866d5e6ce86abd55d5674b13f0e921f19d4abd7edf23db50 +size 42027 diff --git a/marked/Rel-18/38_series/38300/057e0fadbc74743547d314f6fd0ff686_img.jpg b/marked/Rel-18/38_series/38300/057e0fadbc74743547d314f6fd0ff686_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..18f1d8c1a43fac28380822dc29fdcf606c1d7d37 --- /dev/null +++ b/marked/Rel-18/38_series/38300/057e0fadbc74743547d314f6fd0ff686_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:714c5b8b9c8b803ecc830c34f0880628ffed36c143e18d0508b8f02a1f91f5d3 +size 9511 diff --git a/marked/Rel-18/38_series/38300/0b998e3ad8f9d104768642612605cb35_img.jpg b/marked/Rel-18/38_series/38300/0b998e3ad8f9d104768642612605cb35_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20d079ec7945203d51b7e9b65b487ad3934239c8 --- /dev/null +++ b/marked/Rel-18/38_series/38300/0b998e3ad8f9d104768642612605cb35_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:70208cb344f10826eb8239d3ed5d17506587d872853e34158ea952ea71fb0bd7 +size 45459 diff --git a/marked/Rel-18/38_series/38300/0eb348bf17d67bf96326e07011d1c1ad_img.jpg b/marked/Rel-18/38_series/38300/0eb348bf17d67bf96326e07011d1c1ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0bd68fb21d8d52c4ad8e769720759d20e72ad538 --- /dev/null +++ b/marked/Rel-18/38_series/38300/0eb348bf17d67bf96326e07011d1c1ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4caf8cfe2198a51a3d14409dd1e84fd818e36085b906eab1a3e7468a31cf76f6 +size 8749 diff --git a/marked/Rel-18/38_series/38300/154b6a4d11b55f7fd962c3e201664066_img.jpg b/marked/Rel-18/38_series/38300/154b6a4d11b55f7fd962c3e201664066_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e93a9eda764dd8d9340436f940ff75b4ecaf7124 --- /dev/null +++ b/marked/Rel-18/38_series/38300/154b6a4d11b55f7fd962c3e201664066_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a942b75e653185101e2b44c0bcbb979132a947455003633f6a0faa9906937fde +size 35943 diff --git a/marked/Rel-18/38_series/38300/1750e325061d2206b5af0af175793d79_img.jpg b/marked/Rel-18/38_series/38300/1750e325061d2206b5af0af175793d79_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad9cc94293cc7aa004dfae3fde53146a2ad93e65 --- /dev/null +++ b/marked/Rel-18/38_series/38300/1750e325061d2206b5af0af175793d79_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a8773262ec65e0e22faae1eeb2a068108b982657d1ddeacda9238832349cb67 +size 28029 diff --git a/marked/Rel-18/38_series/38300/18003425d0e8638dde4acc9c5c468c5c_img.jpg b/marked/Rel-18/38_series/38300/18003425d0e8638dde4acc9c5c468c5c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7fa18e39a2891b94cc959a5f424751e1d85c6b5 --- /dev/null +++ b/marked/Rel-18/38_series/38300/18003425d0e8638dde4acc9c5c468c5c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4bac45851258a6bc84c43f04d8da74c6ccbe2b94589c99e4d8a987fa1d7d7bc3 +size 81465 diff --git a/marked/Rel-18/38_series/38300/1b2ad37940c441d410002c05ff71c7c5_img.jpg b/marked/Rel-18/38_series/38300/1b2ad37940c441d410002c05ff71c7c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..691921f8b3bfdda9c85c1b32a59bc70db195cdb3 --- /dev/null +++ b/marked/Rel-18/38_series/38300/1b2ad37940c441d410002c05ff71c7c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09410a07a553b62d3a76d1104d876a5a780e9ec0193dd1ee98f8f4b106ae3495 +size 57914 diff --git a/marked/Rel-18/38_series/38300/1b50f9f141d3d1a1de52e959f85f8fc2_img.jpg b/marked/Rel-18/38_series/38300/1b50f9f141d3d1a1de52e959f85f8fc2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..050e6394c19c7a829d4bcf1c29c4aaa37a5716d1 --- /dev/null +++ b/marked/Rel-18/38_series/38300/1b50f9f141d3d1a1de52e959f85f8fc2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9669174179fe0e5e755aac4485e3bde9a4b4b3bf1e0b474481b4ac0a7f415642 +size 31631 diff --git a/marked/Rel-18/38_series/38300/1c29dadab94c3fa552d270434db09c81_img.jpg b/marked/Rel-18/38_series/38300/1c29dadab94c3fa552d270434db09c81_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c33c38dc712d9bb05fe5b6155a626921fa4851e0 --- /dev/null +++ b/marked/Rel-18/38_series/38300/1c29dadab94c3fa552d270434db09c81_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23a3a7c04d190770fcef4b79eaa689c4d08e3d8772d21a8ae0ebf86153eb412d +size 16759 diff --git a/marked/Rel-18/38_series/38300/1c3a7d87de139c7d44f40acec0e4f3fb_img.jpg b/marked/Rel-18/38_series/38300/1c3a7d87de139c7d44f40acec0e4f3fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f29de91df0cb6b2fb908694b215b9e5511dfc69 --- /dev/null +++ b/marked/Rel-18/38_series/38300/1c3a7d87de139c7d44f40acec0e4f3fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fd614a4de6aa581c9461d3f4dca0e435e8dc7777b8d0d251a1fe061b8b4f2012 +size 44326 diff --git a/marked/Rel-18/38_series/38300/1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg b/marked/Rel-18/38_series/38300/1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f141363ce967ae91b0c3219fce2af668384bb297 --- /dev/null +++ b/marked/Rel-18/38_series/38300/1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b299561cf9730da64a07358350ae6156341763119a084a09938c0987b77e8e3 +size 50213 diff --git a/marked/Rel-18/38_series/38300/1f980b98800c29272e0e5ba2f6db4b98_img.jpg b/marked/Rel-18/38_series/38300/1f980b98800c29272e0e5ba2f6db4b98_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1bd10daa5b034c8f53b973ca9fcfa4c255c1448e --- /dev/null +++ b/marked/Rel-18/38_series/38300/1f980b98800c29272e0e5ba2f6db4b98_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f8a21cc902885eccfd44df9f9398018b12a836791894731492f00aab77682e5 +size 46866 diff --git a/marked/Rel-18/38_series/38300/20136850feb70fd71c7d41cdae203ebb_img.jpg b/marked/Rel-18/38_series/38300/20136850feb70fd71c7d41cdae203ebb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52c3eee7eb7d194c492c8ba59733da4c82b6f4b9 --- /dev/null +++ b/marked/Rel-18/38_series/38300/20136850feb70fd71c7d41cdae203ebb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:810c30245869b4d110702dfa1bf70138fc6d6cddbfaef8ff8404c379b9f499d8 +size 48472 diff --git a/marked/Rel-18/38_series/38300/26eb15ab3bef8b99ba79760363525e51_img.jpg b/marked/Rel-18/38_series/38300/26eb15ab3bef8b99ba79760363525e51_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..24d8e1bd899e626e8e52f96e7110ca92901ad97e --- /dev/null +++ b/marked/Rel-18/38_series/38300/26eb15ab3bef8b99ba79760363525e51_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:001956e06f428537e68b806bd60113eec61a19144c0e09ae881e1fc90db336f2 +size 40835 diff --git a/marked/Rel-18/38_series/38300/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-18/38_series/38300/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..385538d3ee3e489d27a0f403b1a2dc1a897d4050 --- /dev/null +++ b/marked/Rel-18/38_series/38300/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:323ff5f98564cf83d07b0b24657894d287fe3c86ac33fa2163cd8175f6e48cd8 +size 6563 diff --git a/marked/Rel-18/38_series/38300/29178b001cb4c04e0c5ab60662ce5d80_img.jpg b/marked/Rel-18/38_series/38300/29178b001cb4c04e0c5ab60662ce5d80_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..043ef7d399c0f5a186c813a2323011521ef4c6bb --- /dev/null +++ b/marked/Rel-18/38_series/38300/29178b001cb4c04e0c5ab60662ce5d80_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a595a83ad0892067fea7da6d2b88c67a2d8e2b20a97d6d0a5bd9a18a8a1c8f3e +size 48672 diff --git a/marked/Rel-18/38_series/38300/2aea72b147efb82b46a78aaea9f1ac22_img.jpg b/marked/Rel-18/38_series/38300/2aea72b147efb82b46a78aaea9f1ac22_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d6a2a7b834f425629798480a73422cca7b7a4ea --- /dev/null +++ b/marked/Rel-18/38_series/38300/2aea72b147efb82b46a78aaea9f1ac22_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:48fe54d03aff37c96ca3e2ef705754f819d198522b6025fd9d3d8619bdaed748 +size 32061 diff --git a/marked/Rel-18/38_series/38300/2cf3896394a2342a2b46c504ab9a8830_img.jpg b/marked/Rel-18/38_series/38300/2cf3896394a2342a2b46c504ab9a8830_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..05729509f177cf130dc5324cf831c44e93f372ea --- /dev/null +++ b/marked/Rel-18/38_series/38300/2cf3896394a2342a2b46c504ab9a8830_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b20770c56ee43dd2fcc1dbd9f547245bad35b970870343abf941f4bbe052c4c8 +size 70564 diff --git a/marked/Rel-18/38_series/38300/2d57a58ef48bbac3b7ea3da33b105f2d_img.jpg b/marked/Rel-18/38_series/38300/2d57a58ef48bbac3b7ea3da33b105f2d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7260542babea1296c2eaeb514c086afb103b6339 --- /dev/null +++ b/marked/Rel-18/38_series/38300/2d57a58ef48bbac3b7ea3da33b105f2d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf81c7cdecb56c1f25e31c932ea1c1842320fda95635c5ec1b03b878f52a9704 +size 35229 diff --git a/marked/Rel-18/38_series/38300/2e18ae7359d8c32e96919956f238ecc5_img.jpg b/marked/Rel-18/38_series/38300/2e18ae7359d8c32e96919956f238ecc5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..014ac148cfdfe3afd7ba0e779f558148ce96a6d7 --- /dev/null +++ b/marked/Rel-18/38_series/38300/2e18ae7359d8c32e96919956f238ecc5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:13efb6b985f71695c818daf330a9aa9a297cfcd08f00b596181b798aa8314f5c +size 29960 diff --git a/marked/Rel-18/38_series/38300/2ed8cadf211f7d2dba5eecc5f0ad1876_img.jpg b/marked/Rel-18/38_series/38300/2ed8cadf211f7d2dba5eecc5f0ad1876_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bcbe8c00ab778cc1ffa0c6d5c0d7cd32afe06ffc --- /dev/null +++ b/marked/Rel-18/38_series/38300/2ed8cadf211f7d2dba5eecc5f0ad1876_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b35cfc3fdec77f97fe62e1a7d5c0c12f8aec900d0dd5fb8d95ab82d08167ce8f +size 6166 diff --git a/marked/Rel-18/38_series/38300/2ff9776a780f30bc64c7a9ef23131cbf_img.jpg b/marked/Rel-18/38_series/38300/2ff9776a780f30bc64c7a9ef23131cbf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..01c140207b4b91d6bb29ebe829c642a8e4d57c82 --- /dev/null +++ b/marked/Rel-18/38_series/38300/2ff9776a780f30bc64c7a9ef23131cbf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb1e06d182d1e67a2d816e413eccb5a72ee7718770a751dd7e938ce31fd5b986 +size 9226 diff --git a/marked/Rel-18/38_series/38300/3054e46608784063609e8c7a253fcd24_img.jpg b/marked/Rel-18/38_series/38300/3054e46608784063609e8c7a253fcd24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..72a27ec98c4d5b38df8221d881bfa9a93028cbd8 --- /dev/null +++ b/marked/Rel-18/38_series/38300/3054e46608784063609e8c7a253fcd24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:40c9708ffd46e8d463c96f8999412957c4516b54fa41879775f0ff5722501e71 +size 33136 diff --git a/marked/Rel-18/38_series/38300/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg b/marked/Rel-18/38_series/38300/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4894164c9ad7ff21e07925336df10a4afafd9b6e --- /dev/null +++ b/marked/Rel-18/38_series/38300/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d497e561d46274dfd0b3d939c7ce29b1f938e9864af7149a04b6ff6492c7f1b +size 18546 diff --git a/marked/Rel-18/38_series/38300/31f5b6310f831ca3ea4f18453980c070_img.jpg b/marked/Rel-18/38_series/38300/31f5b6310f831ca3ea4f18453980c070_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..676dffd90e0bebb5f3621a563d9bb54af4c66606 --- /dev/null +++ b/marked/Rel-18/38_series/38300/31f5b6310f831ca3ea4f18453980c070_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e53929959eb7ba04e0110ebac163eae0c735ad4d040c9bdda0710c429b7d46bc +size 68554 diff --git a/marked/Rel-18/38_series/38300/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-18/38_series/38300/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1122ee5710121d2a4eac08e30d66c422a4c0032c --- /dev/null +++ b/marked/Rel-18/38_series/38300/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c267e78772ee103b4ac29c7c5256b3f80274ec6250ec537bc8088a933bb9e86 +size 14728 diff --git a/marked/Rel-18/38_series/38300/36e11608a186ec372afec7470985ff56_img.jpg b/marked/Rel-18/38_series/38300/36e11608a186ec372afec7470985ff56_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f24d6a703420688ae050689d09f97f240e6891b --- /dev/null +++ b/marked/Rel-18/38_series/38300/36e11608a186ec372afec7470985ff56_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d24bcf38732c62126d8ec6d77af16131a6cacedf97f50a28b199000cd397de24 +size 13022 diff --git a/marked/Rel-18/38_series/38300/38c0f202ad5767f3df428353919fa90a_img.jpg b/marked/Rel-18/38_series/38300/38c0f202ad5767f3df428353919fa90a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1fff34535bab9b90d70a09d18b3a8cc855cfcf96 --- /dev/null +++ b/marked/Rel-18/38_series/38300/38c0f202ad5767f3df428353919fa90a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:73646007cd5138e03640d24e0d11f7674717d42e4e24db6e2da80f184e922a12 +size 23749 diff --git a/marked/Rel-18/38_series/38300/38e67fda26b37cfba4e5ffa0f0fa61ab_img.jpg b/marked/Rel-18/38_series/38300/38e67fda26b37cfba4e5ffa0f0fa61ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a5acf1d9c65bd75ca3e6496d798a1bf3d32bdcd4 --- /dev/null +++ b/marked/Rel-18/38_series/38300/38e67fda26b37cfba4e5ffa0f0fa61ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:20cfb3e445acb4e87dfd80df70ba61c643b78e29a9658a33d90ccb575a713913 +size 31778 diff --git a/marked/Rel-18/38_series/38300/3ec35c497a0765a1a885c85f214b1bef_img.jpg b/marked/Rel-18/38_series/38300/3ec35c497a0765a1a885c85f214b1bef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df3c29442595cb0f812566e965078ce866377e7c --- /dev/null +++ b/marked/Rel-18/38_series/38300/3ec35c497a0765a1a885c85f214b1bef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67d4ddfc93950be6a75ed967fbe4a3850f4b1edaf9df58ca616f28fd779a594b +size 11554 diff --git a/marked/Rel-18/38_series/38300/4325ad0fb1a0bcc317492c16a5467f71_img.jpg b/marked/Rel-18/38_series/38300/4325ad0fb1a0bcc317492c16a5467f71_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d2fed7a46f053006f2def019f712fbfa5692e396 --- /dev/null +++ b/marked/Rel-18/38_series/38300/4325ad0fb1a0bcc317492c16a5467f71_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6908323890a73a6c167fdc529f88125cf46c3ff91e61d9af9b25cb1226929568 +size 36109 diff --git a/marked/Rel-18/38_series/38300/43979979715bb3304389a0cb18f34444_img.jpg b/marked/Rel-18/38_series/38300/43979979715bb3304389a0cb18f34444_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f5bb8b79cb531d09131d28eb81c859125c8f28f --- /dev/null +++ b/marked/Rel-18/38_series/38300/43979979715bb3304389a0cb18f34444_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:820b3fb968b88bfd7587912236819ef9094c515fd9f5f06492ddedccf076a111 +size 5870 diff --git a/marked/Rel-18/38_series/38300/4537891530c9f6f139a2e1ebf544edc4_img.jpg b/marked/Rel-18/38_series/38300/4537891530c9f6f139a2e1ebf544edc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a463e4b81b80af1e74aada2ca816accaffb82d9c --- /dev/null +++ b/marked/Rel-18/38_series/38300/4537891530c9f6f139a2e1ebf544edc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f01ffc0693c7cbb15f4fd233c41ab1fbe6b612ebbf84241deafdf7e5ed394a3e +size 44991 diff --git a/marked/Rel-18/38_series/38300/49fe8fe978c0f7e73112d231feb377eb_img.jpg b/marked/Rel-18/38_series/38300/49fe8fe978c0f7e73112d231feb377eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c9c8e054f85e40f6597b8099b3771dfb7781966d --- /dev/null +++ b/marked/Rel-18/38_series/38300/49fe8fe978c0f7e73112d231feb377eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:61f8f76e442ed9743f5d86c6c70e794caef32221090b1b9761a371b94d34f93f +size 31837 diff --git a/marked/Rel-18/38_series/38300/4a390493f601ce1ac6b9201db4e28b5a_img.jpg b/marked/Rel-18/38_series/38300/4a390493f601ce1ac6b9201db4e28b5a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa719f96771916a1f8bc6496bb10bed6d3b57f08 --- /dev/null +++ b/marked/Rel-18/38_series/38300/4a390493f601ce1ac6b9201db4e28b5a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:afea1bda85a4de4bc326e701837da42a68b5e9b625ce4bd10e5905a3de114dbf +size 34471 diff --git a/marked/Rel-18/38_series/38300/4af57aad638888edf2062306f8a54a6c_img.jpg b/marked/Rel-18/38_series/38300/4af57aad638888edf2062306f8a54a6c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a77aefc439295ba0478bd63a9b3d71264de03d61 --- /dev/null +++ b/marked/Rel-18/38_series/38300/4af57aad638888edf2062306f8a54a6c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9677b7f777b158038bca3ea30c9224bb0b712db162e7e39426d1d92c4a0a3bcf +size 8856 diff --git a/marked/Rel-18/38_series/38300/4c815618b2aaed14f81e59f6272d6511_img.jpg b/marked/Rel-18/38_series/38300/4c815618b2aaed14f81e59f6272d6511_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d404802593b4726f8188eb7c77fe4826a4a72510 --- /dev/null +++ b/marked/Rel-18/38_series/38300/4c815618b2aaed14f81e59f6272d6511_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c6fe1a93a036c2dbef470e8b48f4202cd627f36d4087213745b9a2698a5405a8 +size 57080 diff --git a/marked/Rel-18/38_series/38300/5199d255473623b85726fdb4f67dec8b_img.jpg b/marked/Rel-18/38_series/38300/5199d255473623b85726fdb4f67dec8b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4326bf470c1bf45421cd6afbdb9099097372831d --- /dev/null +++ b/marked/Rel-18/38_series/38300/5199d255473623b85726fdb4f67dec8b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:181d4d3f18d6583da35c1ed3bc82729b6e7fdc54eb8a58adb6b8d49f79146349 +size 12750 diff --git a/marked/Rel-18/38_series/38300/5525e7460947727851585808324e1f98_img.jpg b/marked/Rel-18/38_series/38300/5525e7460947727851585808324e1f98_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..95d825861f9e7e50682eba1fc9be256bb3397b9d --- /dev/null +++ b/marked/Rel-18/38_series/38300/5525e7460947727851585808324e1f98_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:977d4c942936f80cc4fd3480ba6d2625a7c2c1db5cc1177f9fff2689a7503d57 +size 35453 diff --git a/marked/Rel-18/38_series/38300/573293af67ee571aef04bf725fcefbe5_img.jpg b/marked/Rel-18/38_series/38300/573293af67ee571aef04bf725fcefbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53da92f309c6a2642e75b891fcad0852a1323603 --- /dev/null +++ b/marked/Rel-18/38_series/38300/573293af67ee571aef04bf725fcefbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:42188cccc657504c2d07586fdd389e4dcc17bcfdce1489b6a5e739843cc5c7db +size 53180 diff --git a/marked/Rel-18/38_series/38300/59121d561a4158609b4c354b9ffd0605_img.jpg b/marked/Rel-18/38_series/38300/59121d561a4158609b4c354b9ffd0605_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..23e1e6740a9e85f1522f9c146d9b48eb33717ce9 --- /dev/null +++ b/marked/Rel-18/38_series/38300/59121d561a4158609b4c354b9ffd0605_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0905b28c26bcbb489ce02975abf38a474cbc48b7b0f151928da7b159f3bb04f6 +size 61120 diff --git a/marked/Rel-18/38_series/38300/59b0fc7f07c6794ca85c36c2d06a5fd9_img.jpg b/marked/Rel-18/38_series/38300/59b0fc7f07c6794ca85c36c2d06a5fd9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c68afe69415790d7e368a5737bf228b3570e8645 --- /dev/null +++ b/marked/Rel-18/38_series/38300/59b0fc7f07c6794ca85c36c2d06a5fd9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef404394b87a467b16422fc02e76ad2f09cf4f8e04995e372c0d7245565de5eb +size 32802 diff --git a/marked/Rel-18/38_series/38300/59fdc1219e09c18d6a39e47092e3194d_img.jpg b/marked/Rel-18/38_series/38300/59fdc1219e09c18d6a39e47092e3194d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f3fcaa79cdd7763752800128265ec51befda63d --- /dev/null +++ b/marked/Rel-18/38_series/38300/59fdc1219e09c18d6a39e47092e3194d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:43ef6d9430e5b94899f0b31cabf2860817758e457d886a28e1fa57687fafc1f6 +size 12680 diff --git a/marked/Rel-18/38_series/38300/5d819f259411162c4e3371915818ae22_img.jpg b/marked/Rel-18/38_series/38300/5d819f259411162c4e3371915818ae22_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2482e670c9c42f29a2cd7b2a3ebb824f44a2abbe --- /dev/null +++ b/marked/Rel-18/38_series/38300/5d819f259411162c4e3371915818ae22_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e213db17130de147731dfc4b4e382ff6c551e7347f0be31ecef5693caa7e626 +size 20493 diff --git a/marked/Rel-18/38_series/38300/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38300/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e5e4e499718a130058244c5e52df68cb18c97ea --- /dev/null +++ b/marked/Rel-18/38_series/38300/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a9e5882560bfbc85c44892c9024c79c05cd3653bb65177471b0e71a87ac952b +size 8273 diff --git a/marked/Rel-18/38_series/38300/61c77cded492bbcd03eff79c850d92c2_img.jpg b/marked/Rel-18/38_series/38300/61c77cded492bbcd03eff79c850d92c2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4e046f9fe5a01efb1e732c9316b6431694ad945 --- /dev/null +++ b/marked/Rel-18/38_series/38300/61c77cded492bbcd03eff79c850d92c2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:159486ae0cedb6f256b86aecffca580387740be3dcf06261f99b3f3f5a567b1e +size 25411 diff --git a/marked/Rel-18/38_series/38300/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38300/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..821407e5e0b07c0f46f0d76cc55ed17c0dd6c25e --- /dev/null +++ b/marked/Rel-18/38_series/38300/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d9956646e8380b7cb04fe53655c6dedad389239aa08e96001edf6d4a531901cc +size 5407 diff --git a/marked/Rel-18/38_series/38300/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/marked/Rel-18/38_series/38300/65e8c0628536d6d4245e9ab46ba070c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c92be5d732dde4cdd97da63a2c181f5c1db8280 --- /dev/null +++ b/marked/Rel-18/38_series/38300/65e8c0628536d6d4245e9ab46ba070c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c7d14a48fd508cabdf396be2a06382405b920264f68770665bc8042472f1e56c +size 7899 diff --git a/marked/Rel-18/38_series/38300/67c232883c119b120d2fb337bf588e05_img.jpg b/marked/Rel-18/38_series/38300/67c232883c119b120d2fb337bf588e05_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b53a697015ac37814e1b60554d729b9e3e59c82 --- /dev/null +++ b/marked/Rel-18/38_series/38300/67c232883c119b120d2fb337bf588e05_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5514eb7c9ed9c1ac4327bada2a904f65374d401bf47df9bcf1fec1991c5f014 +size 20422 diff --git a/marked/Rel-18/38_series/38300/69981c87c5b93c90e9012f6dabce4215_img.jpg b/marked/Rel-18/38_series/38300/69981c87c5b93c90e9012f6dabce4215_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..565f3d9560800da6605105944bbdbf8a3c986984 --- /dev/null +++ b/marked/Rel-18/38_series/38300/69981c87c5b93c90e9012f6dabce4215_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:47de86e2446161da5b3fd36dec20e0118615adf1026f5f4426ebad01d35498c8 +size 64961 diff --git a/marked/Rel-18/38_series/38300/6a555cff11e140861ce08db72b01a6a2_img.jpg b/marked/Rel-18/38_series/38300/6a555cff11e140861ce08db72b01a6a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b17cb96149696690e5c2c88351e2f6faf0516780 --- /dev/null +++ b/marked/Rel-18/38_series/38300/6a555cff11e140861ce08db72b01a6a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f3094f9d8c7a7377fe92c807ef1471c9bc1e76bad697ae0155a9a5b35e9299b +size 6811 diff --git a/marked/Rel-18/38_series/38300/6be06b7dc72bb42afcb3465394667c3b_img.jpg b/marked/Rel-18/38_series/38300/6be06b7dc72bb42afcb3465394667c3b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4da8ada3a5b6aa8ece868adb467b0ac591b93c5c --- /dev/null +++ b/marked/Rel-18/38_series/38300/6be06b7dc72bb42afcb3465394667c3b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0815122829b9ad3fd0e37f8445f2898db507ab0a1f3edae52d607ceeb65328df +size 41619 diff --git a/marked/Rel-18/38_series/38300/719ef0f734259484038b2434e5dc3f24_img.jpg b/marked/Rel-18/38_series/38300/719ef0f734259484038b2434e5dc3f24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22e0532350012a03a412c90c2b9daaaa15c0d592 --- /dev/null +++ b/marked/Rel-18/38_series/38300/719ef0f734259484038b2434e5dc3f24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3580e3b6b8f3f64f94ceb86557201d012f79b405874722f2d6e0ffa07f7937ea +size 78142 diff --git a/marked/Rel-18/38_series/38300/750b1652a4f4791b84c02aa755a1dedd_img.jpg b/marked/Rel-18/38_series/38300/750b1652a4f4791b84c02aa755a1dedd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c65d3096759ccb417fe42a4fe4c74ea4456e2c4e --- /dev/null +++ b/marked/Rel-18/38_series/38300/750b1652a4f4791b84c02aa755a1dedd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4980fce29f9d32221409d8d1c94d5bce780b3a4dcd24ba5db2b547a4b10f5075 +size 155070 diff --git a/marked/Rel-18/38_series/38300/76f4756bc4fb7d52be4ad051adf9bd89_img.jpg b/marked/Rel-18/38_series/38300/76f4756bc4fb7d52be4ad051adf9bd89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..086f26b671b425e5c15eca2b9e0da2642dffb005 --- /dev/null +++ b/marked/Rel-18/38_series/38300/76f4756bc4fb7d52be4ad051adf9bd89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:97f3359b744025e9611ad20c9b96f787853e1c0af8f63a1e190b4635fb59c4bd +size 31904 diff --git a/marked/Rel-18/38_series/38300/7722d62e33dcc894cc8555e9474c5606_img.jpg b/marked/Rel-18/38_series/38300/7722d62e33dcc894cc8555e9474c5606_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..80dbed6260ff84a433ec326154e2c582e6473fb2 --- /dev/null +++ b/marked/Rel-18/38_series/38300/7722d62e33dcc894cc8555e9474c5606_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:91bc1e56c6cdea676ab42925687f407f492a042aab6875d392f18fea223f5319 +size 20504 diff --git a/marked/Rel-18/38_series/38300/7b24e2d4d1416a6411999a7f02fa5414_img.jpg b/marked/Rel-18/38_series/38300/7b24e2d4d1416a6411999a7f02fa5414_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be439bdd3652b70d831d098a00bd8706740f4b22 --- /dev/null +++ b/marked/Rel-18/38_series/38300/7b24e2d4d1416a6411999a7f02fa5414_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5cb3926b60aba79282375327ef8979557588518ed40afbf584eaa99687aabbaf +size 50916 diff --git a/marked/Rel-18/38_series/38300/7b2d685b805535c1e94aee1365753b92_img.jpg b/marked/Rel-18/38_series/38300/7b2d685b805535c1e94aee1365753b92_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d653e05b49897c4d06f3194931cc438ab2b1f5bf --- /dev/null +++ b/marked/Rel-18/38_series/38300/7b2d685b805535c1e94aee1365753b92_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b461751fd6aed879b2ad0b5dc767058a347ee6836412a43d71b896abc8bb5e96 +size 56777 diff --git a/marked/Rel-18/38_series/38300/7c19fc92dc74a74ec346d46bc39a3946_img.jpg b/marked/Rel-18/38_series/38300/7c19fc92dc74a74ec346d46bc39a3946_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e5bda2311711b2803c8a9c04406848d07fea073a --- /dev/null +++ b/marked/Rel-18/38_series/38300/7c19fc92dc74a74ec346d46bc39a3946_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b1b91cc1f6751f1a03a4d9f0f51aebdaf9e578de63b67c90f473c7e849b3b187 +size 26577 diff --git a/marked/Rel-18/38_series/38300/7cd0445f94b0b9c4e9566a23d221791e_img.jpg b/marked/Rel-18/38_series/38300/7cd0445f94b0b9c4e9566a23d221791e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f9d95f2a467d38c6d06f4730da86d3fad5dbda0d --- /dev/null +++ b/marked/Rel-18/38_series/38300/7cd0445f94b0b9c4e9566a23d221791e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c2a1943708fc315d44263b7517ed1f41bb9d3fa8861661c939981421306d21e +size 70965 diff --git a/marked/Rel-18/38_series/38300/803776dff64331076ffc951fc95358ee_img.jpg b/marked/Rel-18/38_series/38300/803776dff64331076ffc951fc95358ee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38abfcfbccd8efafc48ff8ce2611cd36f6b00fef --- /dev/null +++ b/marked/Rel-18/38_series/38300/803776dff64331076ffc951fc95358ee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:88ea81ddaed08e1667d2b0d12b71b9281be52913e8755d7dc5275709fa1261c4 +size 6294 diff --git a/marked/Rel-18/38_series/38300/819f1d00e68b342a246b64fa888a97f9_img.jpg b/marked/Rel-18/38_series/38300/819f1d00e68b342a246b64fa888a97f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..182ce219add9c4a3e18a0e747dced4ddf068ad20 --- /dev/null +++ b/marked/Rel-18/38_series/38300/819f1d00e68b342a246b64fa888a97f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:234849ff3426928af3b1920dc618cf998009652757e218d58a41de229240f98f +size 40130 diff --git a/marked/Rel-18/38_series/38300/835afd2841651b4ae5ee24f5a0025f9f_img.jpg b/marked/Rel-18/38_series/38300/835afd2841651b4ae5ee24f5a0025f9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0a6289b6dbd359a0c0be3aca18dafd7528f1932 --- /dev/null +++ b/marked/Rel-18/38_series/38300/835afd2841651b4ae5ee24f5a0025f9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e5cf19bc377a75b8a51ab071f7e78a7ec54fd9452e1aa53b7f48394f0ca13357 +size 41854 diff --git a/marked/Rel-18/38_series/38300/8768e42bf1062f1af11f259fc52a92e9_img.jpg b/marked/Rel-18/38_series/38300/8768e42bf1062f1af11f259fc52a92e9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99fa86500da735da31409b77c79de77a2bd401de --- /dev/null +++ b/marked/Rel-18/38_series/38300/8768e42bf1062f1af11f259fc52a92e9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:13e3d931952dceb4270c63ee76c2d80451a7d4f1015b521b71eeb352ebc5bb2d +size 25586 diff --git a/marked/Rel-18/38_series/38300/87f625baee73880fd5464a9f60b1b3b8_img.jpg b/marked/Rel-18/38_series/38300/87f625baee73880fd5464a9f60b1b3b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf74089a65b8c172e4b35821cc00065d4c213c1c --- /dev/null +++ b/marked/Rel-18/38_series/38300/87f625baee73880fd5464a9f60b1b3b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f3c15799adf007aafcd784d96ce7121a6b4bbc7976768d5fcdc07be8867b9352 +size 28115 diff --git a/marked/Rel-18/38_series/38300/92724c769da9d46b730fde1a6dccb023_img.jpg b/marked/Rel-18/38_series/38300/92724c769da9d46b730fde1a6dccb023_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..57b89739dd6e40979fe6206f1cf0e53dfd8bc329 --- /dev/null +++ b/marked/Rel-18/38_series/38300/92724c769da9d46b730fde1a6dccb023_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f6d0757ae5ec01e98dd3d4c5b4ff6f7f71f0b3703ad790d9b7ea6a0a90a9a13c +size 67543 diff --git a/marked/Rel-18/38_series/38300/94fd137860c16c8dfd75512f10161fe8_img.jpg b/marked/Rel-18/38_series/38300/94fd137860c16c8dfd75512f10161fe8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36b9f0f2fba5c3ec007545556db7ee3eee054e48 --- /dev/null +++ b/marked/Rel-18/38_series/38300/94fd137860c16c8dfd75512f10161fe8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a3254c051573950100706b0a36abb39c8a2c5b5f03e3f40a317d28e21d2b571 +size 51846 diff --git a/marked/Rel-18/38_series/38300/98e54d5540b2efe3e24af3cf936bc4ea_img.jpg b/marked/Rel-18/38_series/38300/98e54d5540b2efe3e24af3cf936bc4ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..12f3db311af3a70ff19acdc5e019c602d3b61a3e --- /dev/null +++ b/marked/Rel-18/38_series/38300/98e54d5540b2efe3e24af3cf936bc4ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d5f58360af43ae1dc783e83d09ee7d49261032a744d07bb108487e5a3b27b88 +size 19949 diff --git a/marked/Rel-18/38_series/38300/9ac8c3c5f82f3ec93caf43124af62cb2_img.jpg b/marked/Rel-18/38_series/38300/9ac8c3c5f82f3ec93caf43124af62cb2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a3b7d6523f1159c038943224cdeab72ef902a0a --- /dev/null +++ b/marked/Rel-18/38_series/38300/9ac8c3c5f82f3ec93caf43124af62cb2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba5b9ef0c0f5262d93e54281188961464811cf5b2feed02f28305313327b5e46 +size 65260 diff --git a/marked/Rel-18/38_series/38300/9c45844d796e85ae05505870a54e4eb4_img.jpg b/marked/Rel-18/38_series/38300/9c45844d796e85ae05505870a54e4eb4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b8a2af3e436d1948d2ad946d8a355a4a177df68 --- /dev/null +++ b/marked/Rel-18/38_series/38300/9c45844d796e85ae05505870a54e4eb4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb1c346c1172fdc5df6c5068a38710deb578326302d56f37a624e7b96b7ce58c +size 56726 diff --git a/marked/Rel-18/38_series/38300/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/marked/Rel-18/38_series/38300/9e8ebf03cae78f4f81b697548c2d7250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ce8e7f7d83061b08ec554b29e17d53405d6c8e33 --- /dev/null +++ b/marked/Rel-18/38_series/38300/9e8ebf03cae78f4f81b697548c2d7250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f648903f2bd7348d801a4a1f30df1e4b8c6443ff478e6238e2776ea472e2257e +size 15696 diff --git a/marked/Rel-18/38_series/38300/a0e8fe7862a6d7341faf5dac275277cc_img.jpg b/marked/Rel-18/38_series/38300/a0e8fe7862a6d7341faf5dac275277cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..71ec1f960d135a63433aa80299f0caa7fa8a1dd0 --- /dev/null +++ b/marked/Rel-18/38_series/38300/a0e8fe7862a6d7341faf5dac275277cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de930b189a530f64683155d12e818b0cf2e91aeadc636b2cc6065ee2c1c50740 +size 34359 diff --git a/marked/Rel-18/38_series/38300/a1890b9a9b85f13e67ed59bbad623659_img.jpg b/marked/Rel-18/38_series/38300/a1890b9a9b85f13e67ed59bbad623659_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b28f2dcb1ef7e963cbe66697ec1e0d06926a43b --- /dev/null +++ b/marked/Rel-18/38_series/38300/a1890b9a9b85f13e67ed59bbad623659_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:90d4b320d994ca4374248239775bfd103a8db20d933b865c226a473e6657516f +size 28701 diff --git a/marked/Rel-18/38_series/38300/a1b35c85c93d7a2e30d1feea2faac2e6_img.jpg b/marked/Rel-18/38_series/38300/a1b35c85c93d7a2e30d1feea2faac2e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..79d99229eea1173db00d11303f115fcde715356a --- /dev/null +++ b/marked/Rel-18/38_series/38300/a1b35c85c93d7a2e30d1feea2faac2e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7402ad34890491a888e86c77847993f4ed2d7454b430e5c66a936bb207401fca +size 34607 diff --git a/marked/Rel-18/38_series/38300/a5404b7275b06497eecf9b5883604753_img.jpg b/marked/Rel-18/38_series/38300/a5404b7275b06497eecf9b5883604753_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6fd749ae721c212288f0cbcb74fd3757dfd46090 --- /dev/null +++ b/marked/Rel-18/38_series/38300/a5404b7275b06497eecf9b5883604753_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b4a0c4c0799c4022fd101b7cacf31d7cd56bdde0e3bef61dca9b8fdb7e06f515 +size 19942 diff --git a/marked/Rel-18/38_series/38300/a74659686b764b14e7d9992d73e3a274_img.jpg b/marked/Rel-18/38_series/38300/a74659686b764b14e7d9992d73e3a274_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f5a9d18705917fb7b77972af3cc083f88ef3389b --- /dev/null +++ b/marked/Rel-18/38_series/38300/a74659686b764b14e7d9992d73e3a274_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95a381005ac20f49ef2b97a921b87bbb31279b7085e03ba595349e95e1b85344 +size 63527 diff --git a/marked/Rel-18/38_series/38300/aa22da43c463563d3d0035722bd79449_img.jpg b/marked/Rel-18/38_series/38300/aa22da43c463563d3d0035722bd79449_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..936840c477325ea9d037bfb11718164b3256dc12 --- /dev/null +++ b/marked/Rel-18/38_series/38300/aa22da43c463563d3d0035722bd79449_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe0a526fb9e341bc3d0fa2de43e718dc498ed42d1db8cf0dc717a20e7fea87f0 +size 61536 diff --git a/marked/Rel-18/38_series/38300/ae0dd5533e0b7fd2db452b5e2fdf8e5b_img.jpg b/marked/Rel-18/38_series/38300/ae0dd5533e0b7fd2db452b5e2fdf8e5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a951edd3fd5d9a33994ada6c076426a11c326d8 --- /dev/null +++ b/marked/Rel-18/38_series/38300/ae0dd5533e0b7fd2db452b5e2fdf8e5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:990a0d9ad40e183cbcb315352a9b152fec0d37c934c56b4b59fd97f4f2b78eca +size 22108 diff --git a/marked/Rel-18/38_series/38300/b0b07599997175149ac03e26e3247c9a_img.jpg b/marked/Rel-18/38_series/38300/b0b07599997175149ac03e26e3247c9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1da6a3cbabc92f23c7ab914aec4c4692131f7be --- /dev/null +++ b/marked/Rel-18/38_series/38300/b0b07599997175149ac03e26e3247c9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2e26bc8da1edb770233426ae6d674ee3cbe2db77e98d72ec2ab65e4126cd3660 +size 32380 diff --git a/marked/Rel-18/38_series/38300/b151ddbeea4f514f5f29ce489350c7f7_img.jpg b/marked/Rel-18/38_series/38300/b151ddbeea4f514f5f29ce489350c7f7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3b2074c5a950b8ba4bc644809f55f29d3a53c6b0 --- /dev/null +++ b/marked/Rel-18/38_series/38300/b151ddbeea4f514f5f29ce489350c7f7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1c6e6dc71ef67f1c46b9e524a4b5e3298b1920dc558b6f6d2edd3dc7bc220b52 +size 63872 diff --git a/marked/Rel-18/38_series/38300/b1a6ab9f3d33d6e8d64173bfa595b763_img.jpg b/marked/Rel-18/38_series/38300/b1a6ab9f3d33d6e8d64173bfa595b763_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a92db3fa3c5ec4f98fa3916c30ce765f064b2e56 --- /dev/null +++ b/marked/Rel-18/38_series/38300/b1a6ab9f3d33d6e8d64173bfa595b763_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1162b99bff9054aa8fe6d03d774ffa9b5b4fe8c89533499f1c7b4fe5cd1acebb +size 74695 diff --git a/marked/Rel-18/38_series/38300/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg b/marked/Rel-18/38_series/38300/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..35632555706de0556c2c202e4343dd38940d4095 --- /dev/null +++ b/marked/Rel-18/38_series/38300/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c4f8bc214223386a53d8da58616bda6adb7655f0a3b5ca5d546a9e847723c0a +size 27887 diff --git a/marked/Rel-18/38_series/38300/b437cd7078b36507e5d918fe6224e6dd_img.jpg b/marked/Rel-18/38_series/38300/b437cd7078b36507e5d918fe6224e6dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc88d2373c87f8cb93b6e9e0a663a7ce1b9b75e3 --- /dev/null +++ b/marked/Rel-18/38_series/38300/b437cd7078b36507e5d918fe6224e6dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d3224996c5256ad34f8c46c24162cd89994eca799212a6fa0f805370d1a6f60 +size 26916 diff --git a/marked/Rel-18/38_series/38300/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-18/38_series/38300/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2602f6cd7c14b6d528e76b83116cafe0a94ae034 --- /dev/null +++ b/marked/Rel-18/38_series/38300/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:449f90e13ddb96818c8de853246dedd212ed43aa811485abf9f9e2e177e3fc2b +size 15816 diff --git a/marked/Rel-18/38_series/38300/ba3c1ae751b210a44f2c210bf95210e0_img.jpg b/marked/Rel-18/38_series/38300/ba3c1ae751b210a44f2c210bf95210e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51b8fef9f4be8e989a7709987b7f6ca52273839d --- /dev/null +++ b/marked/Rel-18/38_series/38300/ba3c1ae751b210a44f2c210bf95210e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8614a3adab3c879b3bd0d50da48c0bbebf4c94a6cec131348191dacf9a3b130c +size 75483 diff --git a/marked/Rel-18/38_series/38300/c07e21a8d65991db04263322f859c94f_img.jpg b/marked/Rel-18/38_series/38300/c07e21a8d65991db04263322f859c94f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..44058aac1bc5b73650c493b801cb88aec4c9a742 --- /dev/null +++ b/marked/Rel-18/38_series/38300/c07e21a8d65991db04263322f859c94f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:84c8233994cfb52d45a61dbe65316971bcaf95b67439c81761849a1c7906880a +size 38487 diff --git a/marked/Rel-18/38_series/38300/c0ef0292328b1602e278f6a0b2ee07e0_img.jpg b/marked/Rel-18/38_series/38300/c0ef0292328b1602e278f6a0b2ee07e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bffefa1d7d9c1411c0205fa4a1c1ee722c804784 --- /dev/null +++ b/marked/Rel-18/38_series/38300/c0ef0292328b1602e278f6a0b2ee07e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ff7b8c7e4815b3a5f2fff5341ad1c497f6b6c5b825f7a0b2a2637563a1a4c82 +size 23495 diff --git a/marked/Rel-18/38_series/38300/c15cb6383bc35906e6b3c7c3aac621ed_img.jpg b/marked/Rel-18/38_series/38300/c15cb6383bc35906e6b3c7c3aac621ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ca180dea423ce0e7c7c10098a98c4a644124914 --- /dev/null +++ b/marked/Rel-18/38_series/38300/c15cb6383bc35906e6b3c7c3aac621ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e23175cecbd8d7ce1e12c3f5ae97d817827c35612f2faaa45892bd557d946500 +size 79857 diff --git a/marked/Rel-18/38_series/38300/c2dbaf7c88ad38cb8620f6d731935ed8_img.jpg b/marked/Rel-18/38_series/38300/c2dbaf7c88ad38cb8620f6d731935ed8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77f440f69bf33fca91c68376c2ca94b2af99ca40 --- /dev/null +++ b/marked/Rel-18/38_series/38300/c2dbaf7c88ad38cb8620f6d731935ed8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:99c8502f0f66423b5e325922585676cd72275decedc8d8793e298d16b80d16f6 +size 9257 diff --git a/marked/Rel-18/38_series/38300/c2f36c545b190860d04e1d84e58d22cc_img.jpg b/marked/Rel-18/38_series/38300/c2f36c545b190860d04e1d84e58d22cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6608b92f977d137ac8f66d00364a510333a39190 --- /dev/null +++ b/marked/Rel-18/38_series/38300/c2f36c545b190860d04e1d84e58d22cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:79cbf4b64cee0b36b559b3fdbdb20a147b098cddd36ff21fd33e0b85a0d20fd5 +size 30803 diff --git a/marked/Rel-18/38_series/38300/c71fd22661fbd344a66043940bbd84fc_img.jpg b/marked/Rel-18/38_series/38300/c71fd22661fbd344a66043940bbd84fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9503181cb77ad1625e38b63ac6cbce768ccf14b3 --- /dev/null +++ b/marked/Rel-18/38_series/38300/c71fd22661fbd344a66043940bbd84fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a2b51600586ed834830fa3dc96f9baf466df8adde46de80a1a6bd8f58b73da41 +size 68983 diff --git a/marked/Rel-18/38_series/38300/c7973a89da29a4a59561e36561984333_img.jpg b/marked/Rel-18/38_series/38300/c7973a89da29a4a59561e36561984333_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6adaa1c364c2c92f3570b39d6da06a8c40cf71b7 --- /dev/null +++ b/marked/Rel-18/38_series/38300/c7973a89da29a4a59561e36561984333_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fbbf2da6966717c53b90dead93f6a3285d7edbe0e971faae9500790afbe4b0d3 +size 48390 diff --git a/marked/Rel-18/38_series/38300/c995e0bb4efc8c0f2994428aa1245709_img.jpg b/marked/Rel-18/38_series/38300/c995e0bb4efc8c0f2994428aa1245709_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cfcdc2eea857432cb4a0ecd87236b2f71080de52 --- /dev/null +++ b/marked/Rel-18/38_series/38300/c995e0bb4efc8c0f2994428aa1245709_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c35db751f5c2d3e51da01d170a9a6767e38b7b3cb17a607b4cd7e6e10f801fe2 +size 47168 diff --git a/marked/Rel-18/38_series/38300/ca22c6236ae7c9a8e76d79c469c452a6_img.jpg b/marked/Rel-18/38_series/38300/ca22c6236ae7c9a8e76d79c469c452a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..71ac1ca57f9dd179d492a2dadcc4f3a8b5f8049b --- /dev/null +++ b/marked/Rel-18/38_series/38300/ca22c6236ae7c9a8e76d79c469c452a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:142914c6fbf032af0dbc37991fb1614225ab6bda7eef96421fbef29143ee2e73 +size 5255 diff --git a/marked/Rel-18/38_series/38300/ccf6853c7291703cb04568057fef5849_img.jpg b/marked/Rel-18/38_series/38300/ccf6853c7291703cb04568057fef5849_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6833d77700493512ce762c618727c7c6c0aa80de --- /dev/null +++ b/marked/Rel-18/38_series/38300/ccf6853c7291703cb04568057fef5849_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3cb771cc5bcd671d56cdb36f310c8c4210c847a061c450f041fe441667b03d22 +size 17294 diff --git a/marked/Rel-18/38_series/38300/cef981f48160da6ca248560bbf31eb7f_img.jpg b/marked/Rel-18/38_series/38300/cef981f48160da6ca248560bbf31eb7f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ce4ea6fa1df55f1600709be8b890c964d4c04b65 --- /dev/null +++ b/marked/Rel-18/38_series/38300/cef981f48160da6ca248560bbf31eb7f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6251ccb6d5076c519e103bb5a53c20d3d2cb5b2d38c049f043e156d4e8db523a +size 7029 diff --git a/marked/Rel-18/38_series/38300/cf734b5645d3e02a8df25f67904cd2d3_img.jpg b/marked/Rel-18/38_series/38300/cf734b5645d3e02a8df25f67904cd2d3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..afd22c9747b4ffcb46bc4e3f8d67ff451b777d05 --- /dev/null +++ b/marked/Rel-18/38_series/38300/cf734b5645d3e02a8df25f67904cd2d3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f407189060fa7ec0f498e8cf86fec2c81420945786dc58fbad82e5d20ce779e6 +size 35800 diff --git a/marked/Rel-18/38_series/38300/d2754c0f61ae5c9ddc3dbf38cecaff86_img.jpg b/marked/Rel-18/38_series/38300/d2754c0f61ae5c9ddc3dbf38cecaff86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a86f94539af104a85309324a6cd3eaae21ae5fad --- /dev/null +++ b/marked/Rel-18/38_series/38300/d2754c0f61ae5c9ddc3dbf38cecaff86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf5ce0132b868f898bd41982f551c7c7f8e3196c080ad4521ada25514b9e4d30 +size 32255 diff --git a/marked/Rel-18/38_series/38300/dd2ddef02cef83a06acfc3e710b36564_img.jpg b/marked/Rel-18/38_series/38300/dd2ddef02cef83a06acfc3e710b36564_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a54f672bceb120a98c16c5af5af5972cb23ba2bd --- /dev/null +++ b/marked/Rel-18/38_series/38300/dd2ddef02cef83a06acfc3e710b36564_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:652309bf4026297686207eb00e256cfba08744cf71ada16782ce86c841d2e070 +size 27802 diff --git a/marked/Rel-18/38_series/38300/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-18/38_series/38300/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ff863de29ecb037dd71388c8cdbedb7e2bc9e67 --- /dev/null +++ b/marked/Rel-18/38_series/38300/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df00b6c46d3cf25063bb444aba6ca499142a318ec3638daa027efa0eb4d38cce +size 24271 diff --git a/marked/Rel-18/38_series/38300/df1966d80c74bc127f159a48f38b13ee_img.jpg b/marked/Rel-18/38_series/38300/df1966d80c74bc127f159a48f38b13ee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba311904700c32cb28f7f31fc6b62a15800680a5 --- /dev/null +++ b/marked/Rel-18/38_series/38300/df1966d80c74bc127f159a48f38b13ee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0271102aff67d5b9d2805d2604c4666d6f71d090d0998726147e8bc671be910e +size 12377 diff --git a/marked/Rel-18/38_series/38300/e16bfa31d748f4d99ec4ae3d16656926_img.jpg b/marked/Rel-18/38_series/38300/e16bfa31d748f4d99ec4ae3d16656926_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6fbd8f0d1a8618e2dfbfcc17c4d0b736a2934339 --- /dev/null +++ b/marked/Rel-18/38_series/38300/e16bfa31d748f4d99ec4ae3d16656926_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b54fa7dd6272bf9b47876ee331fcec1dda9558cc4c59875db11ef14e9f861015 +size 119504 diff --git a/marked/Rel-18/38_series/38300/e29665b8abcea967ef289c6aff07ae4c_img.jpg b/marked/Rel-18/38_series/38300/e29665b8abcea967ef289c6aff07ae4c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3b8888744240ee1f0a202d72d7d308d2ea8c61c9 --- /dev/null +++ b/marked/Rel-18/38_series/38300/e29665b8abcea967ef289c6aff07ae4c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e16de861acb64afded31a29de294da29f2f0287efdfff128df2fd3b5e35fea2 +size 8001 diff --git a/marked/Rel-18/38_series/38300/e2c120be98ede6deb60dd341f5a9803b_img.jpg b/marked/Rel-18/38_series/38300/e2c120be98ede6deb60dd341f5a9803b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b2e7ac0fe4afeb7e23f8864bf70dcd46e89a6a1 --- /dev/null +++ b/marked/Rel-18/38_series/38300/e2c120be98ede6deb60dd341f5a9803b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5bf194a9bb09995dcb3877d18dbbad43443fc094c6b375cfdeb451f9dae933fe +size 35811 diff --git a/marked/Rel-18/38_series/38300/e33485d4301404e5a43a61e4cfb96fcc_img.jpg b/marked/Rel-18/38_series/38300/e33485d4301404e5a43a61e4cfb96fcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..90a6895ff176dc70fe739c89c65f6728b0300fca --- /dev/null +++ b/marked/Rel-18/38_series/38300/e33485d4301404e5a43a61e4cfb96fcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c20a799da85e2a9e0621987afa0814970afede65233259f5e5e92e17136a760 +size 63990 diff --git a/marked/Rel-18/38_series/38300/e94f8f1631cc515867e8c0ebd1bac7fe_img.jpg b/marked/Rel-18/38_series/38300/e94f8f1631cc515867e8c0ebd1bac7fe_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..356b36253f8e7704902361881ecadd2f1ad7f7dc --- /dev/null +++ b/marked/Rel-18/38_series/38300/e94f8f1631cc515867e8c0ebd1bac7fe_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c3bd3f23cc5fd71db025585570dd7f500191c04dfad457dd4dfaf27230cb203 +size 38001 diff --git a/marked/Rel-18/38_series/38300/e9ada921dc81492dd0cd7c59d7d20ae9_img.jpg b/marked/Rel-18/38_series/38300/e9ada921dc81492dd0cd7c59d7d20ae9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9694402337edf193b6c1f3d316731f7363a5e498 --- /dev/null +++ b/marked/Rel-18/38_series/38300/e9ada921dc81492dd0cd7c59d7d20ae9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ef2a78a4d2ac4b2a55622bc540e92e534d1e10639a880212ad62428c06c5dae +size 26005 diff --git a/marked/Rel-18/38_series/38300/ec15e024ce479a90bcd696b471bd9747_img.jpg b/marked/Rel-18/38_series/38300/ec15e024ce479a90bcd696b471bd9747_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b6ce38e0b7fb61bca5a6e4bf499c4e0b79f642b2 --- /dev/null +++ b/marked/Rel-18/38_series/38300/ec15e024ce479a90bcd696b471bd9747_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7dbba439a6936e63b542e9d8f5ed2c5f58385195a8e0a562901ec7d8dd730015 +size 99444 diff --git a/marked/Rel-18/38_series/38300/f1091147d93cee4dfa88498610e395a7_img.jpg b/marked/Rel-18/38_series/38300/f1091147d93cee4dfa88498610e395a7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..410abaa2dae4b8b6b27797d3657be1c9a7f58c01 --- /dev/null +++ b/marked/Rel-18/38_series/38300/f1091147d93cee4dfa88498610e395a7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:885e54c53bcbafdce74cb0a5582639495f503daefbc71064e1f042ae0237cd2c +size 6327 diff --git a/marked/Rel-18/38_series/38300/f3fd3ff8f78da4c2a4d39bb6330c49a1_img.jpg b/marked/Rel-18/38_series/38300/f3fd3ff8f78da4c2a4d39bb6330c49a1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36d40df2b509c56ed39e4f6704bfd2b757a53baa --- /dev/null +++ b/marked/Rel-18/38_series/38300/f3fd3ff8f78da4c2a4d39bb6330c49a1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:41baa79e4573fba7bb562b1b77dc8365cacbc66401a49ea378e2d4c31af477f7 +size 28563 diff --git a/marked/Rel-18/38_series/38300/f4e64712104f326ff259928d8126f1f6_img.jpg b/marked/Rel-18/38_series/38300/f4e64712104f326ff259928d8126f1f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1dcc175df6cdd56faa4fae71f0348be3d3425050 --- /dev/null +++ b/marked/Rel-18/38_series/38300/f4e64712104f326ff259928d8126f1f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c7322d8911655b869956d1b8affafca5ee8ce0fdd2b46ddcff99138457067250 +size 37034 diff --git a/marked/Rel-18/38_series/38300/f79cb254efa2e37d7facb055cf90086e_img.jpg b/marked/Rel-18/38_series/38300/f79cb254efa2e37d7facb055cf90086e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ffa7fb1a3d032e7c8fb193ac6fb2b1b6d1a27d3 --- /dev/null +++ b/marked/Rel-18/38_series/38300/f79cb254efa2e37d7facb055cf90086e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:41877c6f94a54c358526fc9d2309e177b0ae84bd35c08fea42c3b3d2ae47cba4 +size 99205 diff --git a/marked/Rel-18/38_series/38300/fcdcb5991d671cadf547dd3fbfe13486_img.jpg b/marked/Rel-18/38_series/38300/fcdcb5991d671cadf547dd3fbfe13486_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1cfa232c23603cc86cd2c8721112fdad2b4f3aa3 --- /dev/null +++ b/marked/Rel-18/38_series/38300/fcdcb5991d671cadf547dd3fbfe13486_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d84821f0c7b52dcbfee17bef6457b80a167409d9927a6898ea57d151e5e99890 +size 27231 diff --git a/marked/Rel-18/38_series/38300/ffe0fef452a0ae9a20253c319c54e13c_img.jpg b/marked/Rel-18/38_series/38300/ffe0fef452a0ae9a20253c319c54e13c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..18c20052a155d4cd970f3a6be3452d8ed44cbda1 --- /dev/null +++ b/marked/Rel-18/38_series/38300/ffe0fef452a0ae9a20253c319c54e13c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8da98b074950593b84876740575b9ef182c3aca80c70b128b88f66b515a84739 +size 152965 diff --git a/marked/Rel-18/38_series/38300/raw.md b/marked/Rel-18/38_series/38300/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e9e55f9998524fff6185e55a47d7a0329c881ca1 --- /dev/null +++ b/marked/Rel-18/38_series/38300/raw.md @@ -0,0 +1,9443 @@ + + +# 3GPP TS 38.300 V18.0.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2 (Release 18)** + +![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5G" text are three green curved lines representing signal waves. + +5G logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, featuring the text "3GPP" in a stylized, bold, black font. Below the "3GPP" text is a small red signal icon. At the bottom of 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..... | 13 | +| 1 Scope..... | 14 | +| 2 References..... | 14 | +| 3 Abbreviations and Definitions..... | 16 | +| 3.1 Abbreviations..... | 16 | +| 3.2 Definitions..... | 20 | +| 4 Overall Architecture and Functional Split..... | 24 | +| 4.1 Overall Architecture..... | 24 | +| 4.2 Functional Split..... | 24 | +| 4.3 Network Interfaces..... | 26 | +| 4.3.1 NG Interface..... | 26 | +| 4.3.1.1 NG User Plane..... | 26 | +| 4.3.1.2 NG Control Plane..... | 27 | +| 4.3.2 Xn Interface..... | 28 | +| 4.3.2.1 Xn User Plane..... | 28 | +| 4.3.2.2 Xn Control Plane..... | 28 | +| 4.4 Radio Protocol Architecture..... | 29 | +| 4.4.1 User Plane..... | 29 | +| 4.4.2 Control Plane..... | 29 | +| 4.5 Multi-Radio Dual Connectivity..... | 29 | +| 4.6 Radio Access Network Sharing..... | 30 | +| 4.7 Integrated Access and Backhaul..... | 30 | +| 4.7.1 Architecture..... | 30 | +| 4.7.2 Protocol Stacks..... | 31 | +| 4.7.3 User-plane Aspects..... | 32 | +| 4.7.3.1 Backhaul transport..... | 32 | +| 4.7.3.2 Flow and Congestion Control..... | 33 | +| 4.7.3.3 Uplink Scheduling Latency..... | 33 | +| 4.7.4 Signalling procedures..... | 33 | +| 4.7.4.1 IAB-node Integration..... | 33 | +| 4.7.4.2 IAB-node Migration..... | 34 | +| 4.7.4.3 Topological Redundancy..... | 34 | +| 4.7.4.4 Backhaul RLF Recovery..... | 34 | +| 4.7.4.5 OTA timing synchronization..... | 34 | +| 4.7.4.6 Inter node discovery..... | 35 | +| 4.7.5 Mobile IAB..... | 35 | +| 4.7.5.1 General..... | 35 | +| 4.7.5.2 RACH-less handover..... | 35 | +| 4.8 Non-Public Networks..... | 36 | +| 4.9 Network-Controlled Repeaters..... | 36 | +| 4.9.1 Architecture..... | 36 | +| 4.9.2 Capabilities..... | 36 | +| 4.9.3 Signalling procedures..... | 37 | +| 4.9.4 OAM aspects..... | 37 | +| 4.9.5 Network-controlled repeater management..... | 37 | +| 5 Physical Layer..... | 38 | +| 5.1 Waveform, numerology and frame structure..... | 38 | +| 5.2 Downlink..... | 39 | +| 5.2.1 Downlink transmission scheme..... | 39 | +| 5.2.2 Physical-layer processing for physical downlink shared channel..... | 39 | +| 5.2.3 Physical downlink control channels..... | 40 | +| 5.2.4 Synchronization signal and PBCH block..... | 41 | +| 5.2.5 Physical layer procedures..... | 42 | +| 5.2.5.1 Link adaptation..... | 42 | +| 5.2.5.2 Power Control..... | 42 | + +| | | | +|---------|-------------------------------------------------------------------------------|----| +| 5.2.5.3 | Cell search..... | 42 | +| 5.2.5.4 | HARQ..... | 43 | +| 5.2.5.5 | Reception of SIB1..... | 43 | +| 5.2.6 | Downlink Reference Signals and Measurements for Positioning..... | 43 | +| 5.3 | Uplink..... | 43 | +| 5.3.1 | Uplink transmission scheme..... | 43 | +| 5.3.2 | Physical-layer processing for physical uplink shared channel..... | 44 | +| 5.3.3 | Physical uplink control channel..... | 44 | +| 5.3.4 | Random access..... | 45 | +| 5.3.5 | Physical layer procedures..... | 46 | +| 5.3.5.1 | Link adaptation..... | 46 | +| 5.3.5.2 | Uplink Power control..... | 46 | +| 5.3.5.3 | Uplink timing control..... | 46 | +| 5.3.5.4 | HARQ..... | 47 | +| 5.3.5.5 | Prioritization of overlapping transmissions..... | 47 | +| 5.3.6 | Uplink Reference Signals and Measurements for Positioning..... | 47 | +| 5.4 | Carrier aggregation..... | 47 | +| 5.4.1 | Carrier aggregation..... | 47 | +| 5.4.2 | Supplementary Uplink..... | 47 | +| 5.4.3 | Uplink Tx switching..... | 48 | +| 5.5 | Transport Channels..... | 48 | +| 5.6 | Access to Shared Spectrum..... | 49 | +| 5.6.1 | Overview..... | 49 | +| 5.6.2 | Channel Access Priority Classes..... | 49 | +| 5.7 | Sidelink..... | 50 | +| 5.7.1 | General..... | 50 | +| 5.7.2 | Sidelink resource allocation modes..... | 50 | +| 5.7.3 | Physical sidelink channels and signals..... | 50 | +| 5.7.4 | Physical layer procedures for sidelink..... | 50 | +| 5.7.4.1 | HARQ feedback..... | 50 | +| 5.7.4.2 | Power Control..... | 51 | +| 5.7.4.3 | CSI report..... | 51 | +| 5.7.5 | Physical layer measurement definition..... | 51 | +| 5.7.6 | Sidelink Reference Signal and Measurements for Positioning..... | 51 | +| 6 | Layer 2..... | 51 | +| 6.1 | Overview..... | 51 | +| 6.2 | MAC Sublayer..... | 55 | +| 6.2.1 | Services and Functions..... | 55 | +| 6.2.2 | Logical Channels..... | 56 | +| 6.2.3 | Mapping to Transport Channels..... | 56 | +| 6.2.4 | HARQ..... | 56 | +| 6.3 | RLC Sublayer..... | 56 | +| 6.3.1 | Transmission Modes..... | 56 | +| 6.3.2 | Services and Functions..... | 57 | +| 6.3.3 | ARQ..... | 57 | +| 6.4 | PDCP Sublayer..... | 57 | +| 6.4.1 | Services and Functions..... | 57 | +| 6.5 | SDAP Sublayer..... | 58 | +| 6.6 | L2 Data Flow..... | 58 | +| 6.7 | Carrier Aggregation..... | 58 | +| 6.8 | Dual Connectivity..... | 60 | +| 6.9 | Supplementary Uplink..... | 60 | +| 6.10 | Bandwidth Adaptation..... | 60 | +| 6.11 | Backhaul Adaptation Protocol Sublayer..... | 61 | +| 6.11.1 | Services and Functions..... | 61 | +| 6.11.2 | Traffic Mapping from Upper Layers to Layer-2..... | 61 | +| 6.11.3 | Routing, BAP Header Rewriting and BH-RLC-channel Mapping on BAP sublayer..... | 62 | +| 6.12 | Multiple Transmit/Receive Point Operation..... | 64 | +| 7 | RRC..... | 64 | +| 7.1 | Services and Functions..... | 64 | + +| | | | +|-----------|--------------------------------------------------------------------------------------|-----| +| 7.2 | Protocol States..... | 65 | +| 7.3 | System Information Handling..... | 66 | +| 7.3.1 | Overview..... | 66 | +| 7.3.2 | Scheduling..... | 68 | +| 7.3.3 | SI Modification..... | 68 | +| 7.4 | Access Control..... | 69 | +| 7.5 | UE Capability Retrieval framework..... | 69 | +| 7.6 | Transport of NAS Messages..... | 69 | +| 7.7 | Carrier Aggregation..... | 70 | +| 7.8 | Bandwidth Adaptation..... | 70 | +| 7.9 | UE Assistance Information..... | 70 | +| 7.10 | Segmentation of RRC messages..... | 71 | +| 8 | NG Identities..... | 71 | +| 8.1 | UE Identities..... | 71 | +| 8.2 | Network Identities..... | 72 | +| 8.3 | User Data Transport on the CN-RAN Interface..... | 73 | +| 8.4 | NR sidelink communication and V2X sidelink communication related identities..... | 73 | +| 9 | Mobility and State Transitions..... | 74 | +| 9.1 | Overview..... | 74 | +| 9.2 | Intra-NR..... | 75 | +| 9.2.1 | Mobility in RRC_IDLE..... | 75 | +| 9.2.1.1 | Cell Selection..... | 75 | +| 9.2.1.2 | Cell Reselection..... | 76 | +| 9.2.1.3 | State Transitions..... | 76 | +| 9.2.2 | Mobility in RRC_INACTIVE..... | 78 | +| 9.2.2.1 | Overview..... | 78 | +| 9.2.2.2 | Cell Reselection..... | 79 | +| 9.2.2.3 | RAN-Based Notification Area..... | 79 | +| 9.2.2.4 | State Transitions..... | 80 | +| 9.2.2.4.1 | UE triggered transition from RRC_INACTIVE to RRC_CONNECTED..... | 80 | +| 9.2.2.4.2 | Network triggered transition from RRC_INACTIVE to RRC_CONNECTED..... | 82 | +| 9.2.2.5 | RNA update..... | 82 | +| 9.2.2.6 | Resume request responded with Release with Redirect, with UE context relocation..... | 84 | +| 9.2.3 | Mobility in RRC_CONNECTED..... | 85 | +| 9.2.3.1 | Overview..... | 85 | +| 9.2.3.2 | Handover..... | 87 | +| 9.2.3.2.1 | C-Plane Handling..... | 87 | +| 9.2.3.2.2 | U-Plane Handling..... | 91 | +| 9.2.3.2.3 | Data Forwarding..... | 93 | +| 9.2.3.3 | Re-establishment procedure..... | 94 | +| 9.2.3.4 | Conditional Handover..... | 95 | +| 9.2.3.4.1 | General..... | 95 | +| 9.2.3.4.2 | C-plane handling..... | 96 | +| 9.2.3.4.3 | U-plane handling..... | 98 | +| 9.2.3.4.4 | Data Forwarding..... | 98 | +| 9.2.3.5 | L1/L2-Triggered Mobility..... | 98 | +| 9.2.3.5.1 | General..... | 98 | +| 9.2.3.5.2 | C-Plane Handling..... | 99 | +| 9.2.3.5.3 | U-Plane Handling..... | 101 | +| 9.2.4 | Measurements..... | 101 | +| 9.2.5 | Paging..... | 104 | +| 9.2.6 | Random Access Procedure..... | 107 | +| 9.2.7 | Radio Link Failure..... | 110 | +| 9.2.8 | Beam failure detection and recovery..... | 111 | +| 9.2.9 | Timing Advance..... | 112 | +| 9.2.10 | Extended DRX for RRC_IDLE and RRC_INACTIVE..... | 112 | +| 9.3 | Inter RAT..... | 113 | +| 9.3.1 | NR-E-UTRA mobility: Intra 5GC..... | 113 | +| 9.3.1.1 | Cell Reselection..... | 113 | +| 9.3.1.2 | Handover..... | 113 | + +| | | | +|----------|--------------------------------------------------------------|-----| +| 9.3.1.3 | Measurements..... | 113 | +| 9.3.2 | NR-E-UTRA mobility: From 5GC to EPC..... | 114 | +| 9.3.2.1 | Cell Reselection..... | 114 | +| 9.3.2.2 | Handover and redirection..... | 114 | +| 9.3.2.3 | Measurements..... | 114 | +| 9.3.2.4 | Data Forwarding for the Control Plane..... | 114 | +| 9.3.2.5 | Data Forwarding for the User Plane..... | 115 | +| 9.3.3 | NR-E-UTRA mobility: From EPC to 5GC..... | 115 | +| 9.3.3.1 | Data Forwarding for the Control Plane..... | 115 | +| 9.3.3.2 | Data Forwarding for the User Plane..... | 116 | +| 9.3.4 | NR-UTRA mobility..... | 116 | +| 9.3.4.1 | Handover with SRVCC operation..... | 116 | +| 9.3.4.2 | Measurements..... | 117 | +| 9.4 | Roaming and Access Restrictions..... | 117 | +| 10 | Scheduling..... | 118 | +| 10.1 | Basic Scheduler Operation..... | 118 | +| 10.2 | Downlink Scheduling..... | 118 | +| 10.3 | Uplink Scheduling..... | 119 | +| 10.4 | Measurements to Support Scheduler Operation..... | 120 | +| 10.5 | Rate Control..... | 120 | +| 10.5.1 | Downlink..... | 120 | +| 10.5.2 | Uplink..... | 120 | +| 10.6 | Activation/Deactivation Mechanism..... | 121 | +| 10.7 | E-UTRA-NR Cell Resource Coordination..... | 121 | +| 10.8 | Cross Carrier Scheduling..... | 122 | +| 10.9 | IAB Resource Configuration..... | 122 | +| 10.10 | Autonomous Denial for IDC..... | 123 | +| 11 | UE Power Saving..... | 123 | +| 12 | QoS..... | 124 | +| 12.1 | Overview..... | 124 | +| 12.2 | Explicit Congestion Notification..... | 127 | +| 13 | Security..... | 127 | +| 13.1 | Overview and Principles..... | 127 | +| 13.2 | Security Termination Points..... | 129 | +| 13.3 | State Transitions and Mobility..... | 130 | +| 14 | UE Capabilities..... | 130 | +| 15 | Self-Configuration and Self-Optimisation..... | 132 | +| 15.1 | Definitions..... | 132 | +| 15.2 | Void..... | 132 | +| 15.3 | Self-configuration..... | 132 | +| 15.3.1 | Dynamic configuration of the NG-C interface..... | 132 | +| 15.3.1.1 | Prerequisites..... | 132 | +| 15.3.1.2 | SCTP initialization..... | 132 | +| 15.3.1.3 | Application layer initialization..... | 132 | +| 15.3.2 | Dynamic Configuration of the Xn interface..... | 132 | +| 15.3.2.1 | Prerequisites..... | 132 | +| 15.3.2.2 | SCTP initialization..... | 132 | +| 15.3.2.3 | Application layer initialization..... | 133 | +| 15.3.3 | Automatic Neighbour Cell Relation Function..... | 133 | +| 15.3.3.1 | General..... | 133 | +| 15.3.3.2 | Intra-system Automatic Neighbour Cell Relation Function..... | 134 | +| 15.3.3.3 | Void..... | 135 | +| 15.3.3.4 | Void..... | 135 | +| 15.3.3.5 | Inter-system Automatic Neighbour Cell Relation Function..... | 135 | +| 15.3.4 | Xn-C TNL address discovery..... | 135 | +| 15.4 | Support for Energy Saving..... | 136 | +| 15.4.1 | General..... | 136 | +| 15.4.2 | Solution description..... | 136 | + +| | | | +|------------|-----------------------------------------------------------------------------|-----| +| 15.4.2.1 | Intra-system energy saving..... | 136 | +| 15.4.2.2 | Inter-system energy saving..... | 137 | +| 15.4.2.3 | Cell DTX/DRX..... | 137 | +| 15.4.2.4 | Conditional Handover..... | 137 | +| 15.4.2.5 | Camping Restrictions..... | 137 | +| 15.4.2.6 | SSB-less SCell..... | 138 | +| 15.4.2.7 | Spatial and power domain adaptation..... | 138 | +| 15.4.3 | O&M requirements..... | 138 | +| 15.5 | Self-optimisation..... | 138 | +| 15.5.1 | Support for Mobility Load Balancing..... | 138 | +| 15.5.1.1 | General..... | 138 | +| 15.5.1.2 | Load reporting for intra-RAT and intra-system inter-RAT load balancing..... | 138 | +| 15.5.1.4 | Adapting handover and/or reselection configuration..... | 139 | +| 15.5.1.5 | Load reporting for inter-system load balancing..... | 139 | +| 15.5.2 | Support for Mobility Robustness Optimization..... | 140 | +| 15.5.2.1 | General..... | 140 | +| 15.5.2.2 | Connection failure..... | 140 | +| 15.5.2.2.1 | General..... | 140 | +| 15.5.2.2.2 | Connection failure due to intra-system mobility..... | 140 | +| 15.5.2.2.3 | Connection failure due to inter-system mobility..... | 142 | +| 15.5.2.3 | Inter-system Unnecessary HO..... | 143 | +| 15.5.2.4 | Inter-system Ping-pong..... | 143 | +| 15.5.2.5 | O&M Requirements..... | 144 | +| 15.5.2.6 | PSCell change failure..... | 144 | +| 15.5.2.7 | Successful HO..... | 144 | +| 15.5.2.8 | Successful PSCell Addition/Change Report..... | 145 | +| 15.5.3 | Support for RACH Optimization..... | 145 | +| 15.5.4 | UE History Information from the UE..... | 145 | +| 15.5.5 | Support for Coverage and Capacity Optimisation..... | 146 | +| 15.5.5.1 | General..... | 146 | +| 15.5.5.2 | OAM requirements..... | 146 | +| 15.5.5.3 | Dynamic coverage configuration changes..... | 146 | +| 15.5.6 | Support for PCI Optimisation..... | 146 | +| 15.5.6.1 | Centralized PCI Assignment..... | 146 | +| 15.5.6.2 | Distributed PCI Assignment..... | 146 | +| 16 | Verticals Support..... | 146 | +| 16.1 | URLLC..... | 146 | +| 16.1.1 | Overview..... | 146 | +| 16.1.2 | LCP Restrictions..... | 147 | +| 16.1.3 | Packet Duplication..... | 147 | +| 16.1.4 | CQI and MCS..... | 148 | +| 16.1.5 | DCI formats..... | 148 | +| 16.1.6 | Higher layer multi-connectivity..... | 148 | +| 16.1.6.1 | Redundant user plane paths based on dual connectivity..... | 148 | +| 16.1.6.2 | Redundant data transmission via single UPF and single RAN node..... | 148 | +| 16.1.7 | URLLC in Unlicensed Controlled Environment..... | 148 | +| 16.1.8 | PUCCH cell switching for TDD cells..... | 149 | +| 16.2 | IMS Voice..... | 149 | +| 16.2.0 | Support for IMS voice..... | 149 | +| 16.2.1 | Support for MMTEL IMS voice and video enhancements..... | 149 | +| 16.2.1.1 | RAN-assisted codec adaptation..... | 149 | +| 16.2.1.2 | MMTEL voice quality/coverage enhancements..... | 150 | +| 16.3 | Network Slicing..... | 150 | +| 16.3.1 | General Principles and Requirements..... | 150 | +| 16.3.2 | AMF and NW Slice Selection..... | 152 | +| 16.3.2.1 | CN-RAN interaction and internal RAN aspects..... | 152 | +| 16.3.2.2 | Radio Interface Aspects..... | 152 | +| 16.3.3 | Resource Isolation and Management..... | 152 | +| 16.3.3.1 | General..... | 152 | +| 16.3.3.2 | Handling of Slice Resources..... | 153 | +| 16.3.3a | Slice-based cell reselection..... | 153 | + +| | | | +|----------|------------------------------------------------------------------------|-----| +| 16.3.4 | Signalling Aspects..... | 153 | +| 16.3.4.1 | General..... | 153 | +| 16.3.4.2 | AMF and NW Slice Selection..... | 153 | +| 16.3.4.3 | UE Context Handling..... | 154 | +| 16.3.4.4 | PDU Session Setup Handling..... | 154 | +| 16.3.4.5 | Mobility..... | 155 | +| 16.4 | Public Warning System..... | 156 | +| 16.5 | Emergency Services..... | 157 | +| 16.5.1 | Overview..... | 157 | +| 16.5.2 | IMS Emergency call..... | 157 | +| 16.5.3 | eCall over IMS..... | 157 | +| 16.5.4 | Fallback..... | 157 | +| 16.6 | Stand-Alone NPN..... | 157 | +| 16.6.1 | General..... | 157 | +| 16.6.2 | Mobility..... | 158 | +| 16.6.2.1 | General..... | 158 | +| 16.6.2.2 | Inactive Mode..... | 158 | +| 16.6.2.3 | Connected Mode..... | 158 | +| 16.7 | Public Network Integrated NPN..... | 159 | +| 16.7.1 | General..... | 159 | +| 16.7.2 | Mobility..... | 159 | +| 16.7.2.1 | General..... | 159 | +| 16.7.2.2 | Inactive Mode..... | 160 | +| 16.7.2.3 | Connected Mode..... | 160 | +| 16.7.3 | Self-Configuration for PNI-NPN..... | 160 | +| 16.7.4 | Access Control..... | 160 | +| 16.7.5 | Paging..... | 160 | +| 16.8 | Support for Time Sensitive Communications..... | 160 | +| 16.8.1 | General..... | 160 | +| 16.8.2 | Network timing synchronization monitoring..... | 162 | +| 16.8.2.1 | General..... | 162 | +| 16.8.2.2 | Network timing synchronization monitoring towards CN..... | 162 | +| 16.8.2.3 | Network timing synchronization monitoring towards UE..... | 162 | +| 16.8.3 | RAN feedback for adaptation of Burst Arrival Time and Periodicity..... | 164 | +| 16.9 | Sidelink..... | 164 | +| 16.9.1 | General..... | 164 | +| 16.9.2 | Radio Protocol Architecture for NR sidelink communication..... | 165 | +| 16.9.2.1 | Overview..... | 165 | +| 16.9.2.2 | MAC..... | 166 | +| 16.9.2.3 | RLC..... | 167 | +| 16.9.2.4 | PDCP..... | 167 | +| 16.9.2.5 | SDAP..... | 167 | +| 16.9.2.6 | RRC..... | 167 | +| 16.9.3 | Radio Resource Allocation..... | 167 | +| 16.9.3.1 | General..... | 167 | +| 16.9.3.2 | Scheduled Resource Allocation..... | 168 | +| 16.9.3.3 | UE Autonomous Resource Selection..... | 168 | +| 16.9.4 | Uu Control..... | 168 | +| 16.9.4.1 | General..... | 168 | +| 16.9.4.2 | Control of connected UEs..... | 169 | +| 16.9.4.3 | Control of idle/inactive UEs..... | 169 | +| 16.9.5 | Sidelink Discovery..... | 170 | +| 16.9.6 | SL DRX..... | 170 | +| 16.9.6.1 | General..... | 170 | +| 16.9.6.2 | Unicast..... | 170 | +| 16.9.6.3 | Groupcast/Broadcast..... | 171 | +| 16.9.6.4 | Alignment between Uu DRX and SL DRX..... | 171 | +| 16.9.7 | Power Savings Resource Allocation..... | 171 | +| 16.9.8 | Inter-UE Coordination (IUC)..... | 172 | +| 16.9.9 | Sidelink in Unlicensed Spectrum (SL-U)..... | 172 | +| 16.9.9.1 | Overview..... | 172 | + +| | | | +|-------------|--------------------------------------------------------------------------------------------------|-----| +| 16.9.9.2 | Channel Access Priority Classes for Sidelink (SL-CAPC)..... | 172 | +| 16.9.9.3 | Sidelink Specific Consistent LBT Failure..... | 173 | +| 16.9.9.4 | COT Sharing..... | 173 | +| 16.9.9.5 | Resource Allocation..... | 174 | +| 16.9.10 | Sidelink CA..... | 174 | +| 16.10 | Multicast and Broadcast Services..... | 175 | +| 16.10.1 | General..... | 175 | +| 16.10.2 | Network Architecture..... | 175 | +| 16.10.3 | Protocol Architecture..... | 175 | +| 16.10.4 | Group Scheduling..... | 177 | +| 16.10.5 | Multicast Handling..... | 178 | +| 16.10.5.1 | Session Management..... | 178 | +| 16.10.5.2 | Configuration..... | 178 | +| 16.10.5.3 | Service Continuity..... | 179 | +| 16.10.5.3.1 | General..... | 179 | +| 16.10.5.3.2 | Handover between Multicast supporting cells..... | 180 | +| 16.10.5.3.3 | Handover between Multicast-supporting cell and Multicast non-supporting cell..... | 180 | +| 16.10.5.3.4 | MRB reconfiguration..... | 181 | +| 16.10.5.3.5 | Service Continuity in RRC_INACTIVE..... | 181 | +| 16.10.5.4 | Reception of MBS Multicast data..... | 181 | +| 16.10.5.5 | Support of CA..... | 182 | +| 16.10.5.6 | DRX..... | 182 | +| 16.10.5.7 | Physical Layer..... | 182 | +| 16.10.6 | Broadcast Handling..... | 182 | +| 16.10.6.1 | Session Management..... | 182 | +| 16.10.6.2 | Configuration..... | 182 | +| 16.10.6.3 | Support of CA..... | 183 | +| 16.10.6.4 | DRX..... | 183 | +| 16.10.6.5 | Service Continuity..... | 183 | +| 16.10.6.5.0 | General..... | 183 | +| 16.10.6.5.1 | Service Continuity in RRC_IDLE or RRC_INACTIVE..... | 183 | +| 16.10.6.5.2 | Service Continuity in RRC_CONNECTED..... | 184 | +| 16.10.6.5A | Reception of MBS Broadcast data..... | 184 | +| 16.10.6.6 | Physical Layer..... | 184 | +| 16.10.6.7 | Shared processing for MBS broadcast and unicast reception..... | 184 | +| 16.11 | Minimization of Service Interruption..... | 185 | +| 16.12 | Sidelink Relay..... | 185 | +| 16.12.1 | General..... | 185 | +| 16.12.2 | Protocol Architecture..... | 186 | +| 16.12.2.1 | L2 UE-to-Network Relay..... | 186 | +| 16.12.2.2 | L2 UE-to-UE Relay..... | 188 | +| 16.12.3 | Relay Discovery..... | 189 | +| 16.12.4 | Relay Selection/Reselection..... | 190 | +| 16.12.5 | Control plane procedures for L2 U2N Relay..... | 192 | +| 16.12.5.1 | RRC Connection Management..... | 192 | +| 16.12.5.2 | Radio Link Failure..... | 193 | +| 16.12.5.3 | RRC Connection Re-establishment..... | 193 | +| 16.12.5.4 | RRC Connection Resume..... | 193 | +| 16.12.5.5 | System Information..... | 193 | +| 16.12.5.6 | Paging..... | 194 | +| 16.12.5.7 | Access Control..... | 194 | +| 16.12.5.8 | Mobility Registration Update and RAN Area Update..... | 194 | +| 16.12.6 | Service Continuity for L2 U2N relay..... | 195 | +| 16.12.6.0 | General..... | 195 | +| 16.12.6.1 | Switching from indirect to direct path..... | 195 | +| 16.12.6.2 | Switching from direct to indirect path..... | 197 | +| 16.12.6.3 | Switching from indirect to indirect path..... | 200 | +| 16.12.7 | Control plane procedures for L2 U2U Relay..... | 203 | +| 16.13 | Support of Reduced Capability (RedCap) and enhanced Reduced Capability (eRedCap) NR devices..... | 205 | +| 16.13.1 | Introduction..... | 205 | +| 16.13.2 | Capabilities..... | 205 | + +| | | | +|-------------|------------------------------------------------------------------------|-----| +| 16.13.3 | Identification, access and camping restrictions..... | 205 | +| 16.13.4 | RRM measurement relaxations..... | 206 | +| 16.13.5 | BWP operation..... | 206 | +| 16.14 | Non-Terrestrial Networks..... | 206 | +| 16.14.1 | Overview..... | 206 | +| 16.14.2 | Timing and Synchronization..... | 208 | +| 16.14.2.1 | Scheduling and Timing..... | 208 | +| 16.14.2.2 | Timing Advance and Frequency Pre-compensation..... | 209 | +| 16.14.3 | Mobility and State transition..... | 209 | +| 16.14.3.1 | Mobility in RRC_IDLE and RRC_INACTIVE..... | 209 | +| 16.14.3.2 | Mobility in RRC_CONNECTED..... | 210 | +| 16.14.3.2.1 | Handover..... | 210 | +| 16.14.3.2.2 | Conditional Handover..... | 210 | +| 16.14.3.2.3 | Satellite switch with re-sync..... | 210 | +| 16.14.3.3 | Measurements..... | 211 | +| 16.14.4 | Switchover..... | 211 | +| 16.14.4.1 | Definitions..... | 211 | +| 16.14.4.2 | Assumptions..... | 211 | +| 16.14.4.3 | Procedures..... | 212 | +| 16.14.5 | NG-RAN signalling..... | 212 | +| 16.14.6 | AMF (Re-)Selection..... | 212 | +| 16.14.7 | O&M Requirements..... | 213 | +| 16.14.8 | Coarse UE location reporting..... | 213 | +| 16.14.9 | Support for NR NTN coverage enhancements..... | 213 | +| 16.14.10 | Verification of UE location..... | 214 | +| 16.15 | eXtended Reality Services..... | 214 | +| 16.15.1 | General..... | 214 | +| 16.15.2 | Awareness..... | 214 | +| 16.15.3 | Power Saving..... | 215 | +| 16.15.4 | Capacity..... | 215 | +| 16.15.4.1 | Physical Layer Enhancements..... | 215 | +| 16.15.4.2 | Layer 2 Enhancements..... | 215 | +| 16.15.4.2.1 | Assistance Information..... | 215 | +| 16.15.4.2.2 | Discard..... | 216 | +| 16.15.5 | Non-Homogeneous support of PDU set based handling in NG-RAN..... | 216 | +| 16.16 | ECN marking for L4S and congestion information exposure..... | 216 | +| 16.17 | Support for TSN enabled Transport Network..... | 216 | +| 16.18 | Support for Aerial UE Communication..... | 217 | +| 16.18.1 | General..... | 217 | +| 16.18.2 | Subscription-based Identification of Aerial UE..... | 217 | +| 16.18.3 | Height-based Reporting for Aerial UE Communication..... | 217 | +| 16.18.4 | Height-dependent Configurations for Aerial UE Communication..... | 217 | +| 16.18.5 | Interference Detection and Mitigation for Aerial UE Communication..... | 217 | +| 16.18.6 | Flight Path Information Reporting for Aerial UE Communication..... | 218 | +| 16.18.7 | Location Reporting for Aerial UE Communication..... | 218 | +| 16.18.8 | BRID and DAA Support via A2X Communication..... | 218 | +| 16.19 | Support for Air to Ground Networks..... | 218 | +| 16.19.1 | Overview..... | 218 | +| 16.19.2 | Timing and Synchronization..... | 218 | +| 16.19.2.1 | Scheduling and Timing..... | 218 | +| 16.19.2.2 | Timing Advance..... | 218 | +| 16.19.3 | Mobility..... | 219 | +| 16.19.3.1 | Mobility in RRC_IDLE and RRC_INACTIVE..... | 219 | +| 16.19.3.2 | Mobility in RRC_CONNECTED..... | 219 | +| 16.19.3.2.1 | Handover..... | 219 | +| 16.19.3.2.2 | Conditional Handover..... | 219 | +| 16.20 | Support of AI/ML for NG-RAN..... | 219 | +| 16.20.1 | General..... | 219 | +| 16.20.2 | Mechanisms and Principles..... | 219 | +| 16.21 | Multi-path Relay..... | 220 | +| 16.21.1 | General..... | 220 | + +| | | | +|-----------|---------------------------------------------------------------------|-----| +| 16.21.2 | Protocol Architecture..... | 221 | +| 16.21.2.1 | L2 MP Relay using SL indirect path..... | 221 | +| 16.21.2.2 | L2 MP Relay using N3C indirect path..... | 222 | +| 16.21.3 | Control plane procedure for multi-path relaying..... | 223 | +| 16.21.3.1 | Path Management..... | 223 | +| 16.21.3.2 | Path Failure Report..... | 228 | +| 17 | Interference Management..... | 229 | +| 17.1 | Remote Interference Management..... | 229 | +| 17.2 | Cross-Link Interference Management..... | 230 | +| 18 | Small Data Transmission..... | 230 | +| 18.0 | General..... | 230 | +| 18.1 | Support of SDT procedure over RACH..... | 231 | +| 18.2 | SDT with UE context relocation..... | 232 | +| 18.3 | SDT without UE context relocation..... | 233 | +| 18.4 | MT-SDT with/without UE context relocation..... | 234 | +| 19 | Support for NR coverage enhancements..... | 235 | +| 20 | Support for Multi-USIM devices..... | 236 | +| 20.1 | General..... | 236 | +| 20.2 | Paging Collision Avoidance..... | 236 | +| 20.3 | UE notification on Network Switching..... | 237 | +| 20.4 | Temporary UE capability restriction and removal of restriction..... | 237 | +| 21 | Application Layer Measurement Collection..... | 238 | +| 21.1 | Overview..... | 238 | +| 21.2 | QoE Measurement Configuration..... | 238 | +| 21.2.1 | QoE Measurement Collection Activation and Reporting..... | 238 | +| 21.2.2 | QoE Measurement Collection Deactivation..... | 239 | +| 21.2.3 | Handling of QMC during RAN Overload..... | 239 | +| 21.2.4 | QoE Measurement Handling in RRC_IDLE and RRC_INACTIVE States..... | 239 | +| 21.2.5 | Per-slice QoE Measurement..... | 240 | +| 21.3 | QoE Measurement Continuity for Mobility..... | 240 | +| 21.4 | RAN Visible QoE Measurements..... | 241 | +| 21.5 | Alignment of MDT and QoE Measurements..... | 241 | + +| | | | +|-------------------------------|--------------------------------------------------------------------------------------------------------------------------|------------| +| Annex A (informative): | QoS Handling in RAN..... | 243 | +| A.1 | PDU Session Establishment..... | 243 | +| A.2 | New QoS Flow with RQoS..... | 243 | +| A.3 | New QoS Flow with Explicit RRC Signalling..... | 244 | +| A.4 | New QoS Flow with Explicit NAS Signalling..... | 245 | +| A.5 | Release of QoS Flow with Explicit Signalling..... | 246 | +| A.6 | UE Initiated UL QoS Flow..... | 246 | +| Annex B (informative): | Deployment Scenarios..... | 248 | +| B.1 | Supplementary Uplink..... | 248 | +| B.2 | Multiple SSBs in a carrier..... | 248 | +| B.3 | NR Operation with Shared Spectrum..... | 249 | +| B.4 | Example implementation of Non-Terrestrial Networks..... | 249 | +| Annex C (informative): | I-RNTI Reference Profiles..... | 252 | +| Annex D (informative): | SPID ranges and mapping of SPID values to cell reselection and inter-RAT/inter frequency handover priorities..... | 253 | +| Annex E (informative): | NG-RAN Architecture for Radio Access Network Sharing with multiple cell ID broadcast..... | 254 | +| Annex F (normative): | Use and structure of the I-RNTI..... | 255 | +| Annex G (informative): | Components of Mobility Latency..... | 256 | +| Annex H (informative): | Change history..... | 258 | + +--- + +## Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# 1 Scope + +The present document provides an overview and overall description of the NG-RAN and focuses on the radio interface protocol architecture of NR connected to 5GC (E-UTRA connected to 5GC is covered in the 36 series). Details of the radio interface protocols are specified in companion specifications of the 38 series. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2". +- [3] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2". +- [4] 3GPP TS 38.401: "NG-RAN; Architecture description". +- [5] 3GPP TS 33.501: "Security Architecture and Procedures for 5G System". +- [6] 3GPP TS 38.321: "NR; Medium Access Control (MAC) protocol specification". +- [7] 3GPP TS 38.322: "NR; Radio Link Control (RLC) protocol specification". +- [8] 3GPP TS 38.323: "NR; Packet Data Convergence Protocol (PDCP) specification". +- [9] 3GPP TS 37.324: " E-UTRA and NR; Service Data Protocol (SDAP) specification". +- [10] 3GPP TS 38.304: "NR; User Equipment (UE) procedures in Idle mode and RRC Inactive state". +- [11] 3GPP TS 38.306: "NR; User Equipment (UE) radio access capabilities". +- [12] 3GPP TS 38.331: "NR; Radio Resource Control (RRC); Protocol specification". +- [13] 3GPP TS 38.133: "NR; Requirements for support of radio resource management". +- [14] 3GPP TS 22.168: "Earthquake and Tsunami Warning System (ETWS) requirements; Stage 1". +- [15] 3GPP TS 22.268: "Public Warning System (PWS) Requirements". +- [16] 3GPP TS 38.410: "NG-RAN; NG general aspects and principles". +- [17] 3GPP TS 38.420: "NG-RAN; Xn general aspects and principles". +- [18] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone". +- [19] 3GPP TS 22.261: "Service requirements for next generation new services and markets". +- [20] 3GPP TS 38.202: "NR; Physical layer services provided by the physical layer" +- [21] 3GPP TS 37.340: "NR; Multi-connectivity; Overall description; Stage-2". + +- [22] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2". +- [23] IETF RFC 4960 (2007-09): "Stream Control Transmission Protocol". +- [24] 3GPP TS 26.114: "Technical Specification Group Services and System Aspects; IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction". +- [25] Void. +- [26] 3GPP TS 38.413: "NG-RAN; NG Application Protocol (NGAP)". +- [27] IETF RFC 3168 (09/2001): "The Addition of Explicit Congestion Notification (ECN) to IP". +- [28] 3GPP TS 24.501: "NR; Non-Access-Stratum (NAS) protocol for 5G System (5GS)". +- [29] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification". +- [30] 3GPP TS 38.415: "NG-RAN; PDU Session User Plane Protocol". +- [31] 3GPP TS 38.340: "NR; Backhaul Adaptation Protocol (BAP) specification". +- [32] 3GPP TS 38.470: "NG-RAN; F1 application protocol (F1AP) ". +- [33] 3GPP TS 38.425: "NG-RAN; NR user plane protocol". +- [34] 3GPP TS 23.216: "Single Radio Voice Call Continuity (SRVCC); Stage 2". +- [35] 3GPP TS 38.101-2: "User Equipment (UE) radio transmission and reception; Part 2: Range 2 Standalone". +- [36] 3GPP TS 38.101-3: "User Equipment (UE) radio transmission and reception; Part 3: Range 1 and Range 2 Interworking operation with other radios". +- [37] 3GPP TS 37.213: "Physical layer procedures for shared spectrum channel access". +- [38] 3GPP TS 38.213: "NR; Physical layer procedures for control". +- [39] 3GPP TS 22.104 "Service requirements for cyber-physical control applications in vertical domains". +- [40] 3GPP TS 23.287: "Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services". +- [41] 3GPP TS 23.285: "Technical Specification Group Services and System Aspects; Architecture enhancements for V2X services". +- [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 37.355: "LTE Positioning Protocol (LPP)". +- [44] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". +- [45] 3GPP TS 23.247: "Architectural enhancements for 5G multicast-broadcast services; Stage 2". +- [46] 3GPP TS 26.346 "Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs". +- [47] 3GPP TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode". +- [48] 3GPP TS 23.304: "Proximity based Services (ProSe) in the 5G System (5GS)". +- [49] 3GPP TS 28.541: "5G Network Resource Model (NRM)". +- [50] 3GPP TS 38.423: "NG-RAN; Xn Application Protocol (XnAP)". + +- [51] NIMA TR 8350.2, Third Edition, Amendment 1, 3 January 2000: "DEPARTMENT OF DEFENSE WORLD GEODETIC SYSTEM 1984". +- [52] 3GPP TS 38.211: "NR; Physical channels and modulation". +- [53] 3GPP TS 24.587: "Vehicle-to-Everything (V2X) services in 5G System (5GS)". +- [54] 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)". +- [55] 3GPP TS 24.554: "Technical Specification Group Core Network and Terminals; Proximity-services (ProSe) in 5G System (5GS) protocol". +- [56] 3GPP TS 38.214: "Technical Specification Group Radio Access Network; NR; Physical layer procedures for data". +- [57] 3GPP TR 38.835: "NR; Study on XR enhancements for NR". +- [58] 3GPP TS 26.522: "5G Real-time Media Transport Protocol Configurations". +- [59] 3GPP TS 38.215: "NR; Physical layer measurements". +- [60] 3GPP TS 23.256: "Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2". + +--- + +## 3 Abbreviations and Definitions + +### 3.1 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1], in TS 36.300 [2] 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 TS 36.300 [2]. + +| | | +|--------|-----------------------------------------| +| 5GC | 5G Core Network | +| 5GS | 5G System | +| 5QI | 5G QoS Identifier | +| A2X | Aircraft-to-Everything | +| A-CSI | Aperiodic CSI | +| AGC | Automatic Gain Control | +| AI | Artificial Intelligence | +| AKA | Authentication and Key Agreement | +| AMBR | Aggregate Maximum Bit Rate | +| AMC | Adaptive Modulation and Coding | +| AMF | Access and Mobility Management Function | +| AR | Augmented Reality | +| ARP | Allocation and Retention Priority | +| ATG | Air to Ground | +| BA | Bandwidth Adaptation | +| BCCH | Broadcast Control Channel | +| BCH | Broadcast Channel | +| BFD | Beam Failure Detection | +| BH | Backhaul | +| BL | Bandwidth reduced Low complexity | +| BPSK | Binary Phase Shift Keying | +| BRID | Broadcast Remote Identification | +| C-RNTI | Cell RNTI | +| CAG | Closed Access Group | +| CAPC | Channel Access Priority Class | +| CBRA | Contention Based Random Access | +| CCE | Control Channel Element | +| CD-SSB | Cell Defining SSB | +| CFR | Common Frequency Resource | + +| | | +|-----------|----------------------------------------| +| CFRA | Contention Free Random Access | +| CG | Configured Grant | +| CHO | Conditional Handover | +| CIoT | Cellular Internet of Things | +| CLI | Cross Link interference | +| CMAS | Commercial Mobile Alert Service | +| CORESET | Control Resource Set | +| CP | Cyclic Prefix | +| CPA | Conditional PSCell Addition | +| CPC | Conditional PSCell Change | +| DAA | Detect And Avoid | +| DAG | Directed Acyclic Graph | +| DAPS | Dual Active Protocol Stack | +| DFT | Discrete Fourier Transform | +| DCI | Downlink Control Information | +| DCP | DCI with CRC scrambled by PS-RNTI | +| DCR | Direct Communication Request | +| DL-AoD | Downlink Angle-of-Departure | +| DL-SCH | Downlink Shared Channel | +| DL-TDOA | Downlink Time Difference Of Arrival | +| DMRS | Demodulation Reference Signal | +| DRX | Discontinuous Reception | +| DSR | Delay Status Report | +| DTX | Discontinuous Transmission | +| E-CID | Enhanced Cell-ID (positioning method) | +| EC | Energy Cost | +| EHC | Ethernet Header Compression | +| ePWS | enhancements of Public Warning System | +| ETWS | Earthquake and Tsunami Warning System | +| FS | Feature Set | +| FSA ID | Frequency Selection Area Identity | +| G-CS-RNTI | Group Configured Scheduling RNTI | +| G-RNTI | Group RNTI | +| GFBR | Guaranteed Flow Bit Rate | +| GIN | Group ID for Network selection | +| GNSS | Global Navigation Satellite System | +| GSO | Geosynchronous Orbit | +| H-SFN | Hyper System Frame Number | +| HAPS | High Altitude Platform Station | +| HRNN | Human-Readable Network Name | +| IAB | Integrated Access and Backhaul | +| IFRI | Intra Frequency Reselection Indication | +| I-RNTI | Inactive RNTI | +| INT-RNTI | Interruption RNTI | +| KPAS | Korean Public Alarm System | +| L2 | Layer-2 | +| L3 | Layer-3 | +| LDPC | Low Density Parity Check | +| LEO | Low Earth Orbit | +| LTM | L1/L2 Triggered Mobility | +| MBS | Multicast/Broadcast Services | +| MCE | Measurement Collection Entity | +| MCCH | MBS Control Channel | +| MDBV | Maximum Data Burst Volume | +| MEO | Medium Earth Orbit | +| MIB | Master Information Block | +| MICO | Mobile Initiated Connection Only | +| MFBR | Maximum Flow Bit Rate | +| ML | Machine Learning | +| MMTEL | Multimedia telephony | +| MNO | Mobile Network Operator | + +| | | +|-----------|--------------------------------------------| +| MO-SDT | Mobile Originated SDT | +| MP | Multi-Path | +| MPE | Maximum Permissible Exposure | +| MRB | MBS Radio Bearer | +| MT | Mobile Termination | +| MT-SDT | Mobile Terminated SDT | +| MTCH | MBS Traffic Channel | +| MTSI | Multimedia Telephony Service for IMS | +| MU-MIMO | Multi User MIMO | +| Multi-RTT | Multi-Round Trip Time | +| MUSIM | Multi-Universal Subscriber Identity Module | +| N3C | Non-3GPP Connection | +| NB-IoT | Narrow Band Internet of Things | +| NCD-SSB | Non Cell Defining SSB | +| NCGI | NR Cell Global Identifier | +| NCL | Neighbour Cell List | +| NCR | Neighbour Cell Relation | +| NCRT | Neighbour Cell Relation Table | +| NGAP | NG Application Protocol | +| NGSO | Non-Geosynchronous Orbit | +| NID | Network Identifier | +| NPN | Non-Public Network | +| NR | NR Radio Access | +| NSAG | Network Slice AS Group | +| NTN | Non-Terrestrial Network | +| P-MPR | Power Management Maximum Power Reduction | +| P-RNTI | Paging RNTI | +| PCH | Paging Channel | +| PCI | Physical Cell Identifier | +| PDB | Packet Delay Budget | +| PDC | Propagation Delay Compensation | +| PDCCH | Physical Downlink Control Channel | +| PDSCH | Physical Downlink Shared Channel | +| PEI | Paging Early Indication | +| PER | Packet Error Rate | +| PH | Paging Hyperframe | +| PLMN | Public Land Mobile Network | +| PNI-NPN | Public Network Integrated NPN | +| PO | Paging Occasion | +| PQI | PC5 5QI | +| PRACH | Physical Random Access Channel | +| PRB | Physical Resource Block | +| PRG | Precoding Resource block Group | +| PRS | Positioning Reference Signal | +| PS-RNTI | Power Saving RNTI | +| PSDB | PDU Set Delay Budget | +| PSER | PDU Set Error Rate | +| PSI | PDU Set Importance | +| PSIHI | PDU Set Integrated Handling Information | +| PSS | Primary Synchronisation Signal | +| PTM | Point to Multipoint | +| PTP | Point to Point | +| PTW | Paging Time Window | +| PUCCH | Physical Uplink Control Channel | +| PUSCH | Physical Uplink Shared Channel | +| PWS | Public Warning System | +| QAM | Quadrature Amplitude Modulation | +| QFI | QoS Flow ID | +| QMC | QoE Measurement Collection | +| QoE | Quality of Experience | +| QPSK | Quadrature Phase Shift Keying | + +| | | +|----------|-------------------------------------------------------| +| RA | Random Access | +| RA-RNTI | Random Access RNTI | +| RACH | Random Access Channel | +| RANAC | RAN-based Notification Area Code | +| REG | Resource Element Group | +| RIM | Remote Interference Management | +| RLM | Radio Link Monitoring | +| RMSI | Remaining Minimum SI | +| RNA | RAN-based Notification Area | +| RNAU | RAN-based Notification Area Update | +| RNTI | Radio Network Temporary Identifier | +| RQA | Reflective QoS Attribute | +| RQoS | Reflective Quality of Service | +| RS | Reference Signal | +| RSRP | Reference Signal Received Power | +| RSRQ | Reference Signal Received Quality | +| RSSI | Received Signal Strength Indicator | +| RSTD | Reference Signal Time Difference | +| RTT | Round Trip Time | +| RVQoE | RAN visible QoE | +| SCS | SubCarrier Spacing | +| SD | Slice Differentiator | +| SDAP | Service Data Adaptation Protocol | +| SDT | Small Data Transmission | +| SD-RSRP | Sidelink Discovery RSRP | +| SFI-RNTI | Slot Format Indication RNTI | +| SHR | Successful Handover Report | +| SIB | System Information Block | +| SI-RNTI | System Information RNTI | +| SLA | Service Level Agreement | +| SL-PRS | Sidelink Positioning Reference Signal | +| SL-RSRP | Sidelink RSRP | +| SMC | Security Mode Command | +| SMF | Session Management Function | +| SMTC | SS/PBCH block Measurement Timing Configuration | +| S-NSSAI | Single Network Slice Selection Assistance Information | +| SNPN | Stand-alone Non-Public Network | +| SNPN ID | Stand-alone Non-Public Network Identity | +| SPR | Successful PSCell Addition/Change Report | +| SPS | Semi-Persistent Scheduling | +| SR | Scheduling Request | +| SRAP | Sidelink Relay Adaptation Protocol | +| SRS | Sounding Reference Signal | +| SRVCC | Single Radio Voice Call Continuity | +| SS | Synchronization Signal | +| SSB | SS/PBCH block | +| SSS | Secondary Synchronisation Signal | +| SSSG | Search Space Set Group | +| SST | Slice/Service Type | +| SU-MIMO | Single User MIMO | +| SUL | Supplementary Uplink | +| TA | Timing Advance | +| TB | Transport Block | +| TCE | Trace Collection Entity | +| TNL | Transport Network Layer | +| TPC | Transmit Power Control | +| TRP | Transmit/Receive Point | +| TRS | Tracking Reference Signal | +| U2N | UE-to-Network | +| U2U | UE-to-UE | +| UAV | Uncrewed Aerial Vehicle | + +| | | +|--------------|-----------------------------------------------| +| UCI | Uplink Control Information | +| UDC | Uplink Data Compression | +| UDM | Unified Data Management | +| UE-Slice-MBR | UE Slice Maximum Bit Rate | +| UL-AoA | Uplink Angles of Arrival | +| UL-RTOA | Uplink Relative Time of Arrival | +| UL-SCH | Uplink Shared Channel | +| UPF | User Plane Function | +| URLLC | Ultra-Reliable and Low Latency Communications | +| VR | Virtual Reality | +| V2X | Vehicle-to-Everything | +| Xn-C | Xn-Control plane | +| Xn-U | Xn-User plane | +| XnAP | Xn Application Protocol | +| XR | eXtended Reality | + +## 3.2 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1], in TS 36.300 [2] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1] and TS 36.300 [2]. + +**A2X communication:** A communication to support A2X services leveraging PC5 reference points. A2X services are realized by various types of A2X applications, i.e. BRID or DAA. + +**Aerial UE communication:** functionality enabling Aerial UE function, as defined in 16.18. + +**Air to Ground network:** An NG-RAN consisting of ground-based gNBs, which provide cell towers that send signals up to an aircraft's antenna(s) of onboard ATG terminal, with typical vertical altitude of around 10,000m and take-off/landing altitudes down to 3000m. + +**BH RLC channel:** an RLC channel between two nodes, which is used to transport backhaul packets. + +**Boundary IAB-node:** as defined in TS 38.401 [4]. + +**Broadcast MRB:** A radio bearer configured for MBS broadcast delivery. + +**CAG Cell:** a PLMN cell broadcasting at least one Closed Access Group identity. + +**CAG Member Cell:** for a UE, a CAG cell broadcasting the identity of the selected PLMN, registered PLMN or equivalent PLMN, and for that PLMN, a CAG identifier belonging to the Allowed CAG list of the UE for that PLMN. + +**CAG-only cell:** a CAG cell that is only available for normal service for CAG UEs. + +**Cell-Defining SSB:** an SSB with an RMSI associated. + +**Child node:** IAB-DU's and IAB-donor-DU's next hop neighbour node; the child node is also an IAB-node. + +**Conditional Handover (CHO):** a handover procedure that is executed only when execution condition(s) are met. + +**CORESET#0:** the control resource set for at least SIB1 scheduling, can be configured either via MIB or via dedicated RRC signalling. + +**DAPS Handover:** a handover procedure that maintains the source gNB connection after reception of RRC message for handover and until releasing the source cell after successful random access to the target gNB. + +**Data Burst:** A set of multiple PDUs generated and sent by the application in a short period of time, as defined in TS 23.501 [3]. + +**Direct Path:** a type of UE-to-Network transmission path, where data is transmitted between a UE and the network without sidelink relaying. + +**Downstream:** direction toward child node or UE in IAB-topology. + +**Early Data Forwarding:** data forwarding that is initiated before the UE executes the handover. + +**Earth-centered, earth-fixed:** a global geodetic reference system for the Earth intended for practical applications of mapping, charting, geopositioning and navigation, as specified in NIMA TR 8350.2 [51]. + +**eRedCap UE:** a UE with enhanced reduced capabilities as specified in clause 4.2.22.1 in TS 38.306 [11]. + +**Feeder link:** wireless link between the NTN Gateway and the NTN payload. + +**Geosynchronous Orbit:** earth-centered orbit at approximately 35786 kilometres above Earth's surface and synchronised with Earth's rotation. A geostationary orbit is a non-inclined geosynchronous orbit, i.e. in the Earth's equator plane. + +**Group ID for Network Selection:** an identifier used during SNPN selection to enhance the likelihood of selecting a preferred SNPN that supports a Default Credentials Server or a Credentials Holder, as specified in TS 23.501 [3]. + +**gNB:** node providing NR user plane and control plane protocol terminations towards the UE, and connected via the NG interface to the 5GC. + +**High Altitude Platform Station:** airborne vehicle embarking the NTN payload placed at an altitude between 8 and 50 km. + +**IAB-donor:** gNB that provides network access to UEs via a network of backhaul and access links. + +**IAB-donor-CU:** as defined in TS 38.401 [4]. + +**IAB-donor-DU:** as defined in TS 38.401 [4]. + +**IAB-DU:** gNB-DU functionality supported by the IAB-node to terminate the NR access interface to UEs and next-hop IAB-nodes, and to terminate the F1 protocol to the gNB-CU functionality, as defined in TS 38.401 [4], on the IAB-donor. + +**IAB-MT:** IAB-node function that terminates the Uu interface to the parent node using the procedures and behaviours specified for UEs unless stated otherwise. IAB-MT function used in 38-series of 3GPP Specifications corresponds to IAB-UE function defined in TS 23.501 [3]. + +**IAB-node:** RAN node that supports NR access links to UEs and NR backhaul links to parent nodes and child nodes. The IAB-node does not support backhauling via LTE. + +**IAB topology:** the unison of all IAB-nodes and IAB-donor-DUs whose F1 and/or RRC connections are terminated at the same IAB-donor-CU. + +**Indirect Path:** a type of UE-to-Network transmission path, where data is forwarded via a U2N Relay UE between a U2N Remote UE and the network. + +**Inter-donor partial migration:** migration of an IAB-MT to a parent node underneath a different IAB-donor-CU while the collocated IAB-DU and its descendant IAB-node(s), if any, are terminated at the initial IAB-donor-CU. The procedure renders the said IAB-node as a boundary IAB-node. + +**Intra-system Handover:** handover that does not involve a CN change (EPC or 5GC). + +**Inter-system Handover:** handover that involves a CN change (EPC or 5GC). + +**Late Data Forwarding:** data forwarding that is initiated after the source NG-RAN node knows that the UE has successfully accessed a target NG-RAN node. + +**L1/L2 Triggered Mobility:** a cell switch procedure that the network triggers via MAC CE based on L1 measurements. + +**Mapped Cell ID:** in NTN, it corresponds to a fixed geographical area. + +**MBS Radio Bearer:** A radio bearer configured for MBS delivery. + +**Mobile-IAB cell:** a cell of a mobile IAB-DU. + +**Mobile IAB-DU:** gNB-DU functionality supported by the mobile IAB-node to terminate the NR access interface to UEs, and to terminate the F1 protocol to the gNB-CU functionality on the IAB-donor, as defined in TS 38.401 [4]. + +**Mobile IAB-DU migration:** procedure for a mobile IAB-node as defined in TS 38.401 [4]. + +**Mobile IAB-MT:** mobile IAB-node function that terminates the Uu interface to the parent node using the procedures and behaviours specified for UEs unless stated otherwise. + +**Mobile IAB-MT migration:** procedure for a mobile IAB-MT as defined in TS 38.401 [4]. + +**Mobile IAB-node:** RAN node that supports NR access links to UEs and an NR backhaul link to a parent node, and that can conduct physical mobility across the RAN area. The mobile IAB-node function used in 38-series of 3GPP Specifications corresponds to the MBSR function defined in TS 23.501 [3]. + +**MP Relay UE:** a UE that provides functionality to support connectivity to the network for MP Remote UE(s). + +**MP Remote UE:** a UE that communicates with the network via a direct Uu link and a MP Relay UE. + +**MSG1:** preamble transmission of the random access procedure for 4-step random access (RA) type. + +**MSG3:** first scheduled transmission of the random access procedure. + +**MSGA:** preamble and payload transmissions of the random access procedure for 2-step RA type. + +**MSGB:** response to MSGA in the 2-step random access procedure. MSGB may consist of response(s) for contention resolution, fallback indication(s), and backoff indication. + +**Multicast/Broadcast Service:** A point-to-multipoint service as defined in TS 23.247 [45]. + +**Multicast MRB:** A radio bearer configured for MBS multicast delivery. + +**Multi-hop backhauling:** using a chain of NR backhaul links between an IAB-node and an IAB-donor. + +**NCR-Fwd:** Network-Controlled Repeater node function, which performs amplifying-and-forwarding of UL/DL RF signals between gNB and UE. The behaviour of the NCR-Fwd is controlled according to the side control information received by the NCR-MT from a gNB. + +**NCR-Fwd access link:** link used for transmissions between the NCR-Fwd and UEs. + +**NCR-Fwd backhaul link:** link used for backhauling between the NCR-Fwd and gNB. + +**NCR-MT:** NCR-node entity which communicates with a gNB via a control link to receive side control information. The control link is based on NR Uu interface. + +**NCR-node:** RAN node comprising NCR-MT and NCR-Fwd. + +**ng-eNB:** node providing E-UTRA user plane and control plane protocol terminations towards the UE, and connected via the NG interface to the 5GC. + +**NG-C:** control plane interface between NG-RAN and 5GC. + +**NG-U:** user plane interface between NG-RAN and 5GC. + +**NG-RAN node:** either a gNB or an ng-eNB. + +**Non-CAG Cell:** a PLMN cell which does not broadcast any Closed Access Group identity. + +**Non-Cell Defining SSB:** an SSB without an RMSI associated. + +**Non-Geosynchronous orbit:** earth-centered orbit with an orbital period that does not match Earth's rotation on its axis. This includes Low and Medium Earth Orbit (LEO and MEO). LEO operates at altitudes between 300 km and 1500 km and MEO at altitudes between 7000 km and 25000 km, approximately. + +**Non-terrestrial network:** an NG-RAN consisting of gNBs, which provide non-terrestrial NR access to UEs by means of an NTN payload embarked on an airborne or space-borne NTN vehicle and an NTN Gateway. + +**NR backhaul link:** NR link used for backhauling between an IAB-node and an IAB-donor, and between IAB-nodes in case of a multi-hop backhauling. + +**NR sidelink communication:** AS functionality enabling at least V2X communication as defined in TS 23.287 [40] and the ProSe communication (including ProSe non-Relay and UE-to-Network Relay communication) as defined in TS 23.304 [48], between two or more nearby UEs, using NR technology but not traversing any network node. + +**NR sidelink discovery:** AS functionality enabling ProSe non-Relay Discovery and ProSe UE-to-Network Relay discovery for Proximity based Services as defined in TS 23.304 [48] between two or more nearby UEs, using NR technology but not traversing any network node. + +**NTN Gateway:** an earth station located at the surface of the earth, providing connectivity to the NTN payload using the feeder link. An NTN Gateway is a TNL node. + +**NTN payload:** a network node, embarked on board a satellite or high altitude platform station, providing connectivity functions, between the service link and the feeder link. In the current version of this specification, the NTN payload is a TNL node. + +**Numerology:** corresponds to one subcarrier spacing in the frequency domain. By scaling a reference subcarrier spacing by an integer $N$ , different numerologies can be defined. + +**Parent node:** IAB-MT's next hop neighbour node; the parent node can be IAB-node or IAB-donor-DU + +**PC5 Relay RLC channel:** an RLC channel between L2 U2N Remote UE and L2 U2N Relay UE, or between L2 U2U Remote UE and L2 U2U Relay UE, which is used to transport packets over PC5 for L2 UE-to-Network/UE-to-UE Relay. + +**PDU Set:** one or more PDUs carrying the payload of one unit of information generated at the application level (e.g. frame(s) or video slice(s) for XR Services), as defined in TS 23.501 [3]. + +**PLMN Cell:** a cell of the PLMN. + +**RACH-less LTM:** an LTM cell switch procedure where UE skips the random access procedure. + +**RedCap UE:** a UE with reduced capabilities as specified in clause 4.2.21.1 in TS 38.306 [11]. + +**Relay discovery:** AS functionality enabling 5G ProSe UE-to-Network Relay Discovery as defined in TS 23.304 [48], using NR technology but not traversing any network node. + +**Satellite:** a space-borne vehicle orbiting the Earth embarking the NTN payload. + +**Service link:** wireless link between the NTN payload and UE. + +**Sidelink Discovery RSRP:** RSRP measurements on PC5 link related to NR sidelink discovery. + +**Sidelink RSRP:** RSRP measurements on PC5 link related to NR sidelink communication. + +**SNPN Access Mode:** mode of operation whereby a UE only accesses SNPNs. + +**SNPN-only cell:** a cell that is only available for normal service for SNPN subscribers. + +**SNPN Identity:** the identity of Stand-alone NPN defined by the pair (PLMN ID, NID). + +**Subsequent LTM:** LTM cell switch procedures between candidate cells without RRC reconfiguration by the network in between. + +**Transmit/Receive Point:** part of the gNB transmitting and receiving radio signals to/from UE according to physical layer properties and parameters inherent to that element. + +**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. + +**Upstream:** direction toward parent node in IAB-topology. + +**Uu Relay RLC channel:** an RLC channel between L2 U2N Relay UE and gNB, which is used to transport packets over Uu for L2 UE-to-Network Relay. + +**V2X sidelink communication:** AS functionality enabling V2X communication as defined in TS 23.285 [41], between nearby UEs, using E-UTRA technology but not traversing any network node. + +**Xn:** network interface between NG-RAN nodes. + +## 4 Overall Architecture and Functional Split + +### 4.1 Overall Architecture + +An NG-RAN node is either: + +- a gNB, providing NR user plane and control plane protocol terminations towards the UE; or +- an ng-eNB, providing E-UTRA user plane and control plane protocol terminations towards the UE. + +The gNBs and ng-eNBs are interconnected with each other by means of the Xn interface. The gNBs and ng-eNBs are also connected by means of the NG interfaces to the 5GC, more specifically to the AMF (Access and Mobility Management Function) by means of the NG-C interface and to the UPF (User Plane Function) by means of the NG-U interface (see TS 23.501 [3]). + +NOTE: The architecture and the F1 interface for a functional split are defined in TS 38.401 [4]. + +The NG-RAN architecture is illustrated in Figure 4.1-1 below. + +![Diagram illustrating the Overall Architecture of NG-RAN nodes. It shows two nodes: a gNB (top) and an ng-eNB (bottom), both connected to a central vertical line representing the 5GC (5G Core Network). The gNB is labeled 'g N B' and the ng-eNB is labeled 'n g - e N B'.](6a555cff11e140861ce08db72b01a6a2_img.jpg) + +The diagram shows two base stations, a gNB and an ng-eNB, connected to a central vertical line representing the 5G Core Network (5GC). The gNB is at the top, labeled 'g N B', and the ng-eNB is at the bottom, labeled 'n g - e N B'. Both are shown with signal waves emanating from them, indicating their radio interfaces. + +Diagram illustrating the Overall Architecture of NG-RAN nodes. It shows two nodes: a gNB (top) and an ng-eNB (bottom), both connected to a central vertical line representing the 5GC (5G Core Network). The gNB is labeled 'g N B' and the ng-eNB is labeled 'n g - e N B'. + +**Figure 4.1-1: Overall Architecture** + +### 4.2 Functional Split + +The **gNB** and **ng-eNB** host the following functions: + +- Functions for Radio Resource Management: Radio Bearer Control, Radio Admission Control, Connection Mobility Control, Dynamic allocation of resources to UEs in uplink, downlink and sidelink (scheduling); +- IP and Ethernet header compression, uplink data decompression, encryption and integrity protection of data; +- Selection of an AMF at UE attachment when no routing to an AMF can be determined from the information provided by the UE; + +- Routing of User Plane data towards UPF(s); +- Routing of Control Plane information towards AMF; +- Connection setup and release; +- Scheduling and transmission of paging messages; +- Scheduling and transmission of system broadcast information (originated from the AMF or OAM); +- Measurement and measurement reporting configuration for mobility and scheduling; +- Transport level packet marking in the uplink; +- Session Management; +- Support of Network Slicing; +- QoS Flow management and mapping to data radio bearers; +- Support of UEs in RRC\_INACTIVE state; +- Distribution function for NAS messages; +- Radio access network sharing; +- Dual Connectivity; +- Tight interworking between NR and E-UTRA; +- Maintain security and radio configuration for User Plane CIoT 5GS Optimisation, as defined in TS 23.501 [3] (ng-eNB only). + +NOTE 1: BL UE or UE in enhanced coverage is only supported by ng-eNB, see TS 36.300 [2]. + +NOTE 2: NB-IoT UE is only supported by ng-eNB, see TS 36.300 [2]. + +The **AMF** hosts the following main functions (see TS 23.501 [3]): + +- NAS signalling termination; +- NAS signalling security; +- AS Security control; +- Inter CN node signalling for mobility between 3GPP access networks; +- Idle mode UE Reachability (including control and execution of paging retransmission); +- Registration Area management; +- Support of intra-system and inter-system mobility; +- Access Authentication; +- Access Authorization including check of roaming rights; +- Mobility management control (subscription and policies); +- Support of Network Slicing; +- SMF selection. +- Selection of CIoT 5GS optimisations; + +The **UPF** hosts the following main functions (see TS 23.501 [3]): + +- Anchor point for Intra-/Inter-RAT mobility (when applicable); + +- External PDU session point of interconnect to Data Network; +- Packet routing & forwarding; +- Packet inspection and User plane part of Policy rule enforcement; +- Traffic usage reporting; +- Uplink classifier to support routing traffic flows to a data network; +- Branching point to support multi-homed PDU session; +- QoS handling for user plane, e.g. packet filtering, gating, UL/DL rate enforcement; +- Uplink Traffic verification (SDF to QoS flow mapping); +- Downlink packet buffering and downlink data notification triggering. + +The Session Management function (**SMF**) hosts the following main functions (see TS 23.501 [3]): + +- Session Management; +- UE IP address allocation and management; +- Selection and control of UP function; +- Configures traffic steering at UPF to route traffic to proper destination; +- Control part of policy enforcement and QoS; +- Downlink Data Notification. + +This is summarized on the figure below where yellow boxes depict the logical nodes and white boxes depict the main functions. + +![Functional Split between NG-RAN and 5GC diagram](20136850feb70fd71c7d41cdae203ebb_img.jpg) + +The diagram illustrates the functional split between the NG-RAN and the 5GC. A vertical dashed line separates the two sides. On the left, the NG-RAN side contains a large yellow box labeled 'gNB or ng-eNB' at the top. Inside this box are seven stacked white boxes representing functions: 'Inter Cell RRM', 'RB Control', 'Connection Mobility Cont.', 'Radio admission Control', 'Measurement Configuration & Provision', 'Dynamic Resource Allocation (Scheduler)', and 'NG-RAN' at the bottom. On the right, the 5GC side contains two yellow boxes. The top one is labeled 'AMF' and contains two white boxes: 'NAS Security' and 'Idle State Mobility Handling'. The bottom one is labeled 'UPF' and contains two white boxes: 'Mobility anchoring' and 'PDU Handling'. To the right of the UPF is a cloud labeled 'Internet'. Above the UPF is another yellow box labeled 'SMF' containing two white boxes: 'UE IP address allocation' and 'PDU Session Control'. + +Functional Split between NG-RAN and 5GC diagram + +**Figure 4.2-1: Functional Split between NG-RAN and 5GC** + +## 4.3 Network Interfaces + +### 4.3.1 NG Interface + +#### 4.3.1.1 NG User Plane + +The NG user plane interface (NG-U) is defined between the NG-RAN node and the UPF. The user plane protocol stack of the NG interface is shown on Figure 4.3.1.1-1. The transport network layer is built on IP transport and GTP-U is used on top of UDP/IP to carry the user plane PDUs between the NG-RAN node and the UPF. + +![Figure 4.3.1.1-1: NG-U Protocol Stack diagram showing the layers for user plane data transfer.](e29665b8abcea967ef289c6aff07ae4c_img.jpg) + +The diagram illustrates the NG-U protocol stack. It consists of five layers stacked vertically. At the top is a box labeled 'User Plane PDUs'. Below it is a double-headed vertical arrow. The next four layers are stacked boxes labeled from top to bottom: 'GTP-U', 'UDP', 'IP', and 'Data Link Layer'. At the very bottom is a box labeled 'Physical Layer'. + +Figure 4.3.1.1-1: NG-U Protocol Stack diagram showing the layers for user plane data transfer. + +**Figure 4.3.1.1-1: NG-U Protocol Stack** + +NG-U provides non-guaranteed delivery of user plane PDUs between the NG-RAN node and the UPF. + +Further details of NG-U can be found in TS 38.410 [16]. + +#### 4.3.1.2 NG Control Plane + +The NG control plane interface (NG-C) is defined between the NG-RAN node and the AMF. The control plane protocol stack of the NG interface is shown on Figure 4.3.1.2-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). The SCTP layer provides guaranteed delivery of application layer messages. In the transport, IP layer point-to-point transmission is used to deliver the signalling PDUs. + +![Figure 4.3.1.2-1: NG-C Protocol Stack diagram showing the layers for control plane signalling.](803776dff64331076ffc951fc95358ee_img.jpg) + +The diagram illustrates the NG-C protocol stack. It consists of four layers stacked vertically. At the top is a box labeled 'NGAP'. Below it is a double-headed vertical arrow. The next three layers are stacked boxes labeled from top to bottom: 'SCTP', 'IP', and 'Data Link Layer'. At the very bottom is a box labeled 'Physical Layer'. + +Figure 4.3.1.2-1: NG-C Protocol Stack diagram showing the layers for control plane signalling. + +**Figure 4.3.1.2-1: NG-C Protocol Stack** + +NG-C provides the following functions: + +- NG interface management; +- UE context management; +- UE mobility management; + +- Transport of NAS messages; +- Paging; +- PDU Session Management; +- Configuration Transfer; +- Warning Message Transmission. + +Further details of NG-C can be found in TS 38.410 [16]. + +## 4.3.2 Xn Interface + +### 4.3.2.1 Xn User Plane + +The Xn User plane (Xn-U) interface is defined between two NG-RAN nodes. The user plane protocol stack on the Xn interface is shown in Figure 4.3.2.1-1. The transport network layer is built on IP transport and GTP-U is used on top of UDP/IP to carry the user plane PDUs. + +![Diagram of the Xn-U Protocol Stack showing layers from User Plane PDUs down to the Physical Layer.](4af57aad638888edf2062306f8a54a6c_img.jpg) + +The diagram illustrates the Xn-U Protocol Stack. At the top is a box labeled 'User Plane PDUs'. Below it is a double-headed vertical arrow indicating bidirectional communication. The stack consists of five layers, represented by boxes stacked vertically: 'GTP-U', 'UDP', 'IP', 'Data Link Layer', and 'Physical Layer' at the bottom. + +Diagram of the Xn-U Protocol Stack showing layers from User Plane PDUs down to the Physical Layer. + +**Figure 4.3.2.1-1: Xn-U Protocol Stack** + +Xn-U provides non-guaranteed delivery of user plane PDUs and supports the following functions: + +- Data forwarding; +- Flow control. + +Further details of Xn-U can be found in TS 38.420 [17]. + +### 4.3.2.2 Xn Control Plane + +The Xn control plane interface (Xn-C) is defined between two NG-RAN nodes. The control plane protocol stack of the Xn interface is shown on Figure 4.3.2.2-1. The transport network layer is built on SCTP on top of IP. The application layer signalling protocol is referred to as XnAP (Xn Application Protocol). The SCTP layer provides the guaranteed delivery of application layer messages. In the transport IP layer point-to-point transmission is used to deliver the signalling PDUs. + +![Figure 4.3.2.2-1: Xn-C Protocol Stack diagram showing a vertical stack of layers: Xn-AP, SCTP, IP, Data Link Layer, and Physical Layer.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +The diagram shows a vertical stack of five protocol layers for the Xn-C interface. From top to bottom, the layers are: Xn-AP, SCTP, IP, Data Link Layer, and Physical Layer. A double-headed vertical arrow is positioned between the Xn-AP layer and the SCTP layer, indicating bidirectional communication. + +Figure 4.3.2.2-1: Xn-C Protocol Stack diagram showing a vertical stack of layers: Xn-AP, SCTP, IP, Data Link Layer, and Physical Layer. + +**Figure 4.3.2.2-1: Xn-C Protocol Stack** + +The Xn-C interface supports the following functions: + +- Xn interface management; +- UE mobility management, including context transfer and RAN paging; +- Dual connectivity. + +Further details of Xn-C can be found in TS 38.420 [17]. + +## 4.4 Radio Protocol Architecture + +### 4.4.1 User Plane + +The figure below shows the protocol stack for the user plane, where SDAP, PDCP, RLC and MAC sublayers (terminated in gNB on the network side) perform the functions listed in clause 6. + +![Figure 4.4.1-1: User Plane Protocol Stack diagram showing two vertical stacks of layers (UE and gNB) connected by horizontal arrows. The layers are SDAP, PDCP, RLC, MAC, and PHY.](1c29dadab94c3fa552d270434db09c81_img.jpg) + +The diagram illustrates the User Plane Protocol Stack across two entities: UE (User Equipment) and gNB (Next Generation NodeB). Each entity has a vertical stack of five layers. From top to bottom, they are: SDAP, PDCP, RLC, MAC, and PHY. Horizontal double-headed arrows connect the corresponding layers in the UE stack to the corresponding layers in the gNB stack, representing the data flow across the interface. + +Figure 4.4.1-1: User Plane Protocol Stack diagram showing two vertical stacks of layers (UE and gNB) connected by horizontal arrows. The layers are SDAP, PDCP, RLC, MAC, and PHY. + +**Figure 4.4.1-1: User Plane Protocol Stack** + +### 4.4.2 Control Plane + +The figure below shows the protocol stack for the control plane, where: + +- PDCP, RLC and MAC sublayers (terminated in gNB on the network side) perform the functions listed in clause 6; +- RRC (terminated in gNB on the network side) performs the functions listed in clause 7; +- NAS control protocol (terminated in AMF on the network side) performs the functions listed in TS 23.501 [3]), for instance: authentication, mobility management, security control... + +![Figure 4.4.2-1: Control Plane Protocol Stack. The diagram shows three vertical boxes representing protocol stacks for UE, gNB, and AMF. The UE stack has layers: NAS, RRC, PDCP, RLC, MAC, PHY. The gNB stack has layers: RRC, PDCP, RLC, MAC, PHY. The AMF stack has a single layer: NAS. Arrows indicate connections: UE NAS to AMF NAS; UE RRC to gNB RRC; UE PDCP to gNB PDCP; UE RLC to gNB RLC; UE MAC to gNB MAC; UE PHY to gNB PHY.](dd5771673aececa53d42ece89218299d_img.jpg) + +Figure 4.4.2-1: Control Plane Protocol Stack. The diagram shows three vertical boxes representing protocol stacks for UE, gNB, and AMF. The UE stack has layers: NAS, RRC, PDCP, RLC, MAC, PHY. The gNB stack has layers: RRC, PDCP, RLC, MAC, PHY. The AMF stack has a single layer: NAS. Arrows indicate connections: UE NAS to AMF NAS; UE RRC to gNB RRC; UE PDCP to gNB PDCP; UE RLC to gNB RLC; UE MAC to gNB MAC; UE PHY to gNB PHY. + +Figure 4.4.2-1: Control Plane Protocol Stack + +## 4.5 Multi-Radio Dual Connectivity + +NG-RAN supports Multi-Radio Dual Connectivity (MR-DC) operation whereby a UE in RRC\_CONNECTED is configured to utilise radio resources provided by two distinct schedulers, located in two different NG-RAN nodes connected via a non-ideal backhaul, one providing NR access and the other one providing either E-UTRA or NR access. Further details of MR-DC operation, including Conditional PSCell Addition (CPA) and Conditional PSCell Change (CPC), can be found in TS 37.340 [21]. + +## 4.6 Radio Access Network Sharing + +NG-RAN supports radio access network sharing as defined in TS 23.501 [3]. + +If NR access is shared, system information broadcast in a shared cell indicates a TAC and a Cell Identity for each subset of PLMNs, PNI-NPNs and SNPNs. NR access provides only one TAC and one Cell Identity per cell per PLMN, SNPN or PNI-NPN. In this version of the specification, a Cell Identity can only belong to one network type among PLMN, PNI-NPN or SNPN as defined in TS 23.501 [3]. + +Each Cell Identity associated with a subset of PLMNs, SNPNs or PNI-NPNs identifies its serving NG-RAN node. + +## 4.7 Integrated Access and Backhaul + +### 4.7.1 Architecture + +Integrated access and backhaul (IAB) enables wireless relaying in NG-RAN. The relaying node, referred to as *IAB-node*, supports access and backhauling via NR. The terminating node of NR backhauling on network side is referred to as the *IAB-donor*, which represents a gNB with additional functionality to support IAB. Backhauling can occur via a single or via multiple hops. The IAB architecture is shown in Figure 4.7.1-1. + +The IAB-node supports the gNB-DU functionality, as defined in TS 38.401 [4], to terminate the NR access interface to UEs and next-hop IAB-nodes, and to terminate the F1 protocol to the gNB-CU functionality, as defined in TS 38.401 [4], on the IAB-donor. The gNB-DU functionality on the IAB-node is also referred to as *IAB-DU*. + +In addition to the gNB-DU functionality, the IAB-node also supports a subset of the UE functionality referred to as *IAB-MT*, which includes, e.g., physical layer, layer-2, RRC and NAS functionality to connect to the gNB-DU of another IAB-node or the IAB-donor, to connect to the gNB-CU on the IAB-donor, and to the core network. + +The IAB-node can access the network using either SA mode or EN-DC. In EN-DC, the IAB-node connects via E-UTRA to a MeNB, and the IAB-donor terminates X2-C as SgNB (TS 37.340 [21]). + +![Diagram of IAB architecture showing an IAB-node (represented by a blue antenna icon) connected to a base station (represented by a grey circle) via a red line representing the backhaul link.](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +Diagram of IAB architecture showing an IAB-node (represented by a blue antenna icon) connected to a base station (represented by a grey circle) via a red line representing the backhaul link. + +**Figure 4.7.1-1: IAB architecture; a) IAB-node using SA mode with 5GC; b) IAB-node using EN-DC** + +All IAB-nodes that are connected to an IAB-donor via one or multiple backhaul hops and controlled by this IAB-donor via F1AP and/or RRC form an IAB topology with the IAB-donor as its root (Fig. 4.7.1-2). In this IAB topology, the neighbour node of the IAB-DU or the IAB-donor-DU is referred to as the *child* node and the neighbour node of the IAB-MT is referred to as the *parent* node. The direction toward the child node is referred to as *downstream* while the direction toward the parent node is referred to as *upstream*. The IAB-donor performs centralized resource, topology and route management for its IAB topology. + +![Diagram illustrating the parent- and child-node relationship for IAB-nodes. A central IAB-node (represented by a box with blue and orange sections) is connected to two child nodes (boxes with orange sections) above it and two child nodes (boxes with blue and white sections) below it. Arrows indicate the flow of traffic: 'Upstream traffic' from the child nodes towards the central node, and 'Downstream traffic' from the central node towards the child nodes.](98e54d5540b2efe3e24af3cf936bc4ea_img.jpg) + +Diagram illustrating the parent- and child-node relationship for IAB-nodes. A central IAB-node (represented by a box with blue and orange sections) is connected to two child nodes (boxes with orange sections) above it and two child nodes (boxes with blue and white sections) below it. Arrows indicate the flow of traffic: 'Upstream traffic' from the child nodes towards the central node, and 'Downstream traffic' from the central node towards the child nodes. + +**Figure 4.7.1-2: Parent- and child-node relationship for IAB-node** + +## 4.7.2 Protocol Stacks + +Fig. 4.7.2-1 shows the protocol stack for F1-U and Fig. 4.7.2-2 shows the protocol stack for F1-C between IAB-DU and IAB-donor-CU. In these figures, F1-U and F1-C are carried over two backhaul hops. + +F1-U and F1-C use an IP transport layer between IAB-DU and IAB-donor-CU as defined in TS 38.470 [32]. F1-U and F1-C need to be security-protected as described in TS 33.501 [5] (the security layer is not shown in the Figures 4.7.2-1/2). + +On the wireless backhaul, the IP layer is carried over the Backhaul Adaptation Protocol (BAP) sublayer, which enables routing over multiple hops. The IP layer can also be used for *non-F1* traffic, such as OAM traffic as defined in TS 38.401 [4]. + +On each backhaul link, the BAP PDUs are carried by BH RLC channels. Multiple BH RLC channels can be configured on each BH link to allow traffic prioritization and QoS enforcement. The BH-RLC-channel mapping for BAP PDUs is performed by the BAP entities on each IAB-node and the IAB-donor-DU. + +Protocol stacks for an IAB-donor with split gNB architecture are specified in TS 38.401 [4]. + +![Fig. 4.7.2-1: Protocol stack for the support of F1-U protocol. The diagram shows three entities: IAB-node 2, IAB-node 1, and IAB-donor. IAB-node 2 and IAB-node 1 each have an IAB-DU and an IAB-MT. IAB-donor has a DU and a CU. The F1-U interface is between the IAB-DU of IAB-node 1 and the CU of IAB-donor. The protocol stack for F1-U traffic is: GTP-U, UDP, IP, BAP, RLC, MAC, PHY. The BAP layer is shown in the IAB-DU of IAB-node 1 and the DU of IAB-donor. The RLC, MAC, and PHY layers are shown in the IAB-MT of IAB-node 1 and the DU of IAB-donor. The BAP layer in IAB-node 1 is connected to the RLC layer, which is connected to the MAC layer, which is connected to the PHY layer. The BAP layer in IAB-donor is connected to the RLC layer, which is connected to the MAC layer, which is connected to the PHY layer. The RLC, MAC, and PHY layers in IAB-node 1 and IAB-donor are connected to the BH RLC channel.](94fd137860c16c8dfd75512f10161fe8_img.jpg) + +Fig. 4.7.2-1: Protocol stack for the support of F1-U protocol. The diagram shows three entities: IAB-node 2, IAB-node 1, and IAB-donor. IAB-node 2 and IAB-node 1 each have an IAB-DU and an IAB-MT. IAB-donor has a DU and a CU. The F1-U interface is between the IAB-DU of IAB-node 1 and the CU of IAB-donor. The protocol stack for F1-U traffic is: GTP-U, UDP, IP, BAP, RLC, MAC, PHY. The BAP layer is shown in the IAB-DU of IAB-node 1 and the DU of IAB-donor. The RLC, MAC, and PHY layers are shown in the IAB-MT of IAB-node 1 and the DU of IAB-donor. The BAP layer in IAB-node 1 is connected to the RLC layer, which is connected to the MAC layer, which is connected to the PHY layer. The BAP layer in IAB-donor is connected to the RLC layer, which is connected to the MAC layer, which is connected to the PHY layer. The RLC, MAC, and PHY layers in IAB-node 1 and IAB-donor are connected to the BH RLC channel. + +Fig. 4.7.2-1: Protocol stack for the support of F1-U protocol + +![Fig. 4.7.2-2: Protocol stack for the support of F1-C protocol. The diagram shows the same entities and interfaces as Fig. 4.7.2-1. The F1-C interface is between the IAB-DU of IAB-node 1 and the CU of IAB-donor. The protocol stack for F1-C traffic is: F1AP, SCTP, IP, BAP, RLC, MAC, PHY. The BAP layer is shown in the IAB-DU of IAB-node 1 and the DU of IAB-donor. The RLC, MAC, and PHY layers are shown in the IAB-MT of IAB-node 1 and the DU of IAB-donor. The BAP layer in IAB-node 1 is connected to the RLC layer, which is connected to the MAC layer, which is connected to the PHY layer. The BAP layer in IAB-donor is connected to the RLC layer, which is connected to the MAC layer, which is connected to the PHY layer. The RLC, MAC, and PHY layers in IAB-node 1 and IAB-donor are connected to the BH RLC channel.](1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg) + +Fig. 4.7.2-2: Protocol stack for the support of F1-C protocol. The diagram shows the same entities and interfaces as Fig. 4.7.2-1. The F1-C interface is between the IAB-DU of IAB-node 1 and the CU of IAB-donor. The protocol stack for F1-C traffic is: F1AP, SCTP, IP, BAP, RLC, MAC, PHY. The BAP layer is shown in the IAB-DU of IAB-node 1 and the DU of IAB-donor. The RLC, MAC, and PHY layers are shown in the IAB-MT of IAB-node 1 and the DU of IAB-donor. The BAP layer in IAB-node 1 is connected to the RLC layer, which is connected to the MAC layer, which is connected to the PHY layer. The BAP layer in IAB-donor is connected to the RLC layer, which is connected to the MAC layer, which is connected to the PHY layer. The RLC, MAC, and PHY layers in IAB-node 1 and IAB-donor are connected to the BH RLC channel. + +Fig. 4.7.2-2: Protocol stack for the support of F1-C protocol + +The IAB-MT further establishes SRBs (carrying RRC and NAS) with the IAB-donor-CU. For IAB-nodes operating in EN-DC, the IAB-MT establishes one or more DRBs with the eNB and one or more DRBs with the IAB-donor-CU, which can be used, e.g., to carry OAM traffic. For SA mode, the establishment of DRBs is optional. These SRBs and DRBs are transported between the IAB-MT and its parent node over Uu access channel(s). The protocol stacks for the SRB is shown in Fig. 4.7.2-3. + +![Diagram illustrating the protocol stack for the support of IAB-MT's RRC and NAS connections. It shows three vertical rectangles representing protocol layers. The leftmost rectangle has a horizontal line extending from its right side to a small rectangle inside the middle rectangle. The middle rectangle has a horizontal line extending from its right side to the rightmost rectangle. A thick black horizontal bar is positioned above the rectangles.](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +Diagram illustrating the protocol stack for the support of IAB-MT's RRC and NAS connections. It shows three vertical rectangles representing protocol layers. The leftmost rectangle has a horizontal line extending from its right side to a small rectangle inside the middle rectangle. The middle rectangle has a horizontal line extending from its right side to the rightmost rectangle. A thick black horizontal bar is positioned above the rectangles. + +**Figure 4.7.2-3: Protocol stack for the support of IAB-MT's RRC and NAS connections** + +## 4.7.3 User-plane Aspects + +### 4.7.3.1 Backhaul transport + +The IAB-DU's IP traffic is routed over the wireless backhaul via the BAP sublayer. The BAP sublayer is specified in TS 38.340 [31]. In downstream direction, upper layer packets are encapsulated by the BAP sublayer at the IAB-donor-DU and de-encapsulated at the destination IAB-node. In upstream direction, upper layer packets are encapsulated at the IAB-node and de-encapsulated at the IAB-donor-DU. IAB-specific transport between IAB-donor-CU and IAB-donor-DU is specified in TS 38.401 [4]. + +On the BAP sublayer, packets are routed based on the BAP routing ID, which is carried in the BAP header. The BAP header is added to the packet when it arrives from upper layers, and the BAP header is stripped off when the packet has reached its destination node. The selection of the packet's BAP routing ID is configured by the IAB-donor-CU. The BAP routing ID consists of BAP address and BAP path ID, where the BAP address indicates the destination node of the packet on the BAP sublayer, and the BAP path ID indicates the routing path the packet should follow to this destination. For the purpose of routing, each IAB-node and IAB-donor-DU is further configured with a designated BAP address. + +On each hop of the packet's path, the IAB-node inspects the packet's BAP address in the BAP routing ID carried in the BAP header to determine if the packet has reached its destination, i.e., matches the IAB-node's BAP address. In case the packet has *not* reached the destination, the IAB-node determines the next hop backhaul link, referred to as *egress* link, based on the BAP routing ID carried in the BAP header and a routing configuration it received from the IAB-donor-CU. + +For each packet, the IAB-node further determines the egress BH RLC channel on the designated egress link. For packets arriving from upper layers, the designated egress BH RLC channel is configured by the IAB-donor-CU, and it is based on upper layer traffic specifiers. Since each BH RLC channel is configured with QoS information or priority level, BH-RLC-channel selection facilitates traffic-specific prioritization and QoS enforcement on the BH. For F1-U traffic, it is possible to map each GTP-U tunnel to a dedicated BH RLC channel or to aggregate multiple GTP-U tunnels into one common BH RLC channel. For traffic other than F1-U traffic, it is possible to map UE-associated F1AP messages, non-UE-associated F1AP messages and non-F1 traffic onto the same or separate BH RLC channels. + +When packets are routed from one BH link to another, the egress BH RLC channel on the egress BH link is determined based on the mapping configuration between ingress BH RLC channels and egress BH RLC channels provided by the IAB-donor-CU. + +### 4.7.3.2 Flow and Congestion Control + +Flow and congestion control can be supported in both upstream and downstream directions in order to avoid congestion-related packet drops on IAB-nodes and IAB-donor-DU: + +- In upstream direction, UL scheduling on MAC layer can support flow control on each hop; +- In downstream direction, the NR user plane protocol (TS 38.425 [33]) supports flow and congestion control between the IAB-node and the IAB-donor-CU for UE bearers that terminate at this IAB-node. Further, flow control is supported on BAP sublayer, where the IAB-node can send feedback information on the available + +buffer size for an ingress BH RLC channel or BAP routing ID to its parent node. The feedback can be sent proactively, e.g., when the buffer load exceeds a certain threshold, or based on polling by the parent node. + +#### 4.7.3.3 Uplink Scheduling Latency + +The IAB-node can reduce UL scheduling latency through signalling of a Pre-emptive BSR to its parent node. The IAB-node can send the Pre-emptive BSR based on UL grants it has provided to child nodes and/or UEs, or based on BSRs it has received from child nodes or UEs (Figure 4.7.3.3-1). The Pre-emptive BSR conveys the data expected rather than the data buffered. + +![Figure 4.7.3.3-1: Scheduling of BSR in IAB. The diagram shows three scenarios (a, b, c) of BSR signaling between a Child Node, an IAB-node, and a Parent Node. In (a), the Child Node sends a Regular BSR to the IAB-node, which receives a UL Grant and Data, then sends a Regular BSR to the Parent Node. In (b), the Child Node sends a Regular BSR to the IAB-node, which receives a UL Grant and Data, then sends a Pre-emptive BSR to the Parent Node. In (c), the Child Node sends a Regular BSR to the IAB-node, which receives a UL Grant and Data, then sends a Pre-emptive BSR to the Parent Node.](a1890b9a9b85f13e67ed59bbad623659_img.jpg) + +``` + +sequenceDiagram + participant Child Node + participant IAB-node + participant Parent Node + + Note left of Child Node: a) + Child Node->>IAB-node: Regular BSR + IAB-node-->>Child Node: UL Grant + Child Node->>IAB-node: Data + IAB-node->>Parent Node: Regular BSR + + Note left of Child Node: b) + Child Node->>IAB-node: Regular BSR + IAB-node-->>Child Node: UL Grant + Child Node->>IAB-node: Data + IAB-node->>Parent Node: Pre-emptive BSR + + Note left of Child Node: c) + Child Node->>IAB-node: Regular BSR + IAB-node-->>Child Node: UL Grant + Child Node->>IAB-node: Data + IAB-node->>Parent Node: Pre-emptive BSR + +``` + +Figure 4.7.3.3-1: Scheduling of BSR in IAB. The diagram shows three scenarios (a, b, c) of BSR signaling between a Child Node, an IAB-node, and a Parent Node. In (a), the Child Node sends a Regular BSR to the IAB-node, which receives a UL Grant and Data, then sends a Regular BSR to the Parent Node. In (b), the Child Node sends a Regular BSR to the IAB-node, which receives a UL Grant and Data, then sends a Pre-emptive BSR to the Parent Node. In (c), the Child Node sends a Regular BSR to the IAB-node, which receives a UL Grant and Data, then sends a Pre-emptive BSR to the Parent Node. + +**Figure 4.7.3.3-1: Scheduling of BSR in IAB:** + +- a) regular BSR based on buffered data,** +- b) Pre-emptive BSR based on UL grant,** +- c) Pre-emptive BSR based on reception of regular BSR** + +#### 4.7.4 Signalling procedures + +##### 4.7.4.1 IAB-node Integration + +The IAB-node integration procedure is captured in TS 38.401 [4]. + +##### 4.7.4.2 IAB-node Migration + +The IAB-node can migrate to a different parent node underneath the same IAB-donor-CU. The IAB-node continues providing access and backhaul service when migrating to a different parent node. + +The IAB-MT can also migrate to a different parent node underneath another IAB-donor-CU. In this case, the collocated IAB-DU and the IAB-DU(s) of its descendant node(s) retain F1 connectivity with the initial IAB-donor-CU. The IAB-MT of each descendant node and all the served UEs retain the RRC connectivity with the initial IAB-donor-CU. This migration is referred to as *inter-donor partial migration*. The IAB-node, whose IAB-MT migrates to the new IAB-donor-CU, is referred to as a *boundary IAB-node*. After inter-donor partial migration, the F1 traffic of the IAB-DU and its descendant nodes is routed via the BAP layer of the IAB topology to which the IAB-MT has migrated. + +Inter-donor partial migration is only supported for SA-mode. + +The intra-donor IAB-node migration procedure and inter-donor partial migration procedures are captured in TS 38.401 [4]. + +##### 4.7.4.3 Topological Redundancy + +The IAB-node may have redundant routes to the IAB-donor-CU(s). + +For IAB-nodes operating in SA-mode, NR DC can be used to enable route redundancy in the BH by allowing the IAB-MT to have concurrent BH links with two parent nodes. The parent nodes may be connected to the same or to different + +IAB-donor-CUs, which control the establishment and release of redundant routes via these two parent nodes. Either parent node's gNB-DU functionality together with the respective IAB-donor-CU assumes the role of the IAB-MT's master node or secondary node. The NR DC framework (e.g., MCG/SCG-related procedures) is used to configure the dual radio links with the parent nodes (TS 37.340 [21]). + +The procedure for establishment of topological redundancy for IAB-nodes operating in SA-mode is captured in TS 38.401 [4]. + +An IAB-node operating in NR-DC may also use one of its links for BH connectivity with an IAB-donor and the other link for access-only connectivity with a separate gNB that does not assume IAB-donor role. The IAB-donor can assume the MN or the SN role. The IAB-node may exchange F1-C traffic with the IAB-donor via the backhaul link and/or via the access link with the gNB. In the latter case, the F1-C messages are carried over NR RRC between the IAB-node and the gNB, and via XnAP between the gNB and the IAB-donor. + +IAB-nodes operating in EN-DC can exchange F1-C traffic with the IAB-donor via the MeNB. The F1-C message is carried over LTE RRC using SRB2 between IAB-node and MeNB and via X2AP between the MeNB and the IAB-donor. + +The procedures for establishment of redundant transport of F1-C for IAB-nodes using NR-DC and EN-DC are captured in TS 37.340 [21] and TS 38.401 [4]. + +#### 4.7.4.4 Backhaul RLF Recovery + +When the IAB-node using SA-mode declares RLF on the backhaul link, it can perform RLF recovery at another parent node underneath the same or underneath a different IAB-donor-CU. In the latter case, the collocated IAB-DU and the IAB-DU(s) of its descendant node(s) may retain the F1 connectivity with the initial IAB-donor-CU, while the IAB-MT(s) of the descendant node(s) and all the served UEs retain the RRC connectivity with the initial IAB-donor-CU, in the same manner as for *inter-donor partial migration*. + +The BH RLF recovery procedure for the IAB-node is captured in TS 38.401 [4]. BH RLF declaration for IAB-node and the aspects of RLF recovery by the IAB-MT are handled in clause 9.2.7 of the present document. + +#### 4.7.4.5 OTA timing synchronization + +An IAB-DU is subject to the same downlink timing alignment of a gNB. The IAB-DU may use the received downlink signal from a parent as a reference to control its downlink timing using TA in conjunction with an additional Tdelta parameter received by the collocated IAB-MT from the parent via MAC-CE. + +#### 4.7.4.6 Inter node discovery + +Inter node discovery is supported via SSB-based and/or CSI-RS-based measurements. An IAB-node can be configured to transmit and receive off synchronization raster SSB signals to discover neighbouring IAB-nodes. The configuration is not expected to create a conflict between IAB-DU SSB transmission and IAB-MT SSB measurement windows. + +### 4.7.5 Mobile IAB + +#### 4.7.5.1 General + +*Mobile IAB* introduces the *mobile IAB-node*, which is a RAN node that provides NR access links to UEs and an NR backhaul link to a parent node, and that can conduct physical mobility across the RAN area. The mobile IAB-node includes a *mobile IAB-MT* and a *mobile IAB-DU*. Mobile IAB supports the same functionality as IAB unless explicitly specified. The following enhancements/restrictions *only* apply to mobile IAB: + +- The mobile IAB-node uses the mobile IAB-node authorization procedure defined in TS 38.401 [4] and the MBSR authorization procedure defined in TS 23.501 [3]. +- A RAN node operating as a mobile IAB-node shall not concurrently operate as an IAB-node. During network integration, the RAN node shall indicate whether it intends to operate as a mobile IAB-node or as an IAB-node via an indicator in the *RRCSetupComplete* message. + +- The parent node indicates support for mobile IAB-nodes by broadcasting a mobile-IAB-specific indicator in SIB1. +- The mobile IAB-node shall not have descendent nodes. A mobile-IAB cell shall therefore not broadcast any indication that it is a suitable parent node for IAB-nodes or mobile IAB-nodes. +- The cell of a mobile IAB-DU may indicate to UEs via a SIB1 indicator that it is a mobile-IAB cell. +- The mobile IAB-node uses the mobile IAB-node network integration procedure as defined in TS 38.401 [4]. +- The mobile IAB-MT can perform the mobile IAB-MT migration procedures via Xn handover and/or via NG handover as defined in TS 38.401 [4]. The mobile IAB-MT can also perform the mobile IAB-node recovery procedure as defined in TS 38.401 [4]. +- The mobile IAB-node can perform the mobile IAB-DU migration procedure, where a new logical mobile IAB-DU is established on the mobile IAB-node and the initial logical mobile IAB-DU is released some time later. During this procedure, the UEs connected via the mobile IAB-node are handed over from the initial logical mobile IAB-DU, referred to as the source logical mobile IAB-DU, to the new logical mobile IAB-DU, referred to as the target logical mobile IAB-DU. The details of this procedure are defined in TS 38.401 [4]. Enhancements related to BAP for mobile IAB-DU migration are defined in TS 38.340 [31]. +- When a RAN node is operating as a mobile IAB node, dual connectivity for this node is not supported. + +#### 4.7.5.2 RACH-less handover + +During the mobile IAB-DU migration procedure, RACH-less handover can be configured for a UE that is migrated from the source logical mobile IAB-DU to the target logical mobile IAB-DU. The RACH-less handover procedure applies the following functionality: + +- The UE uses the same timing advance at the cell of the target logical mobile IAB-DU as signalled by the cell of the source logical mobile IAB-DU. +- The handover command for the UE contains a beam identifier for the beam to be used by the UE at the target logical mobile-IAB cell. The beam may be determined based on a UE measurement report and/or based on implementation, e.g., using the target cell's knowledge about the beam(s) used by the UE at the co-located source cell. +- The handover command may include a pre-allocated UL grant. Alternatively, an UL grant is dynamically signalled by the target logical IAB-DU cell. +- The UE transmits the *RRCReconfigurationComplete* message using the pre-allocated or dynamically signalled UL grant. The UE's successful UL data reception on the target logical mobile-IAB cell terminates the RACH-less handover execution. + +## 4.8 Non-Public Networks + +A Non-Public Network (NPN) is a network for non-public use (see TS 22.261 [19]), which can be deployed as (see TS 23.501 [3]): + +- a Stand-alone Non-Public Network (SNPN) when not relying on network functions provided by a PLMN; or +- a Public Network Integrated (PNI) NPN when relying on the support of a PLMN. + +NOTE: As described in clause 5.30.3.1 of TS 23.501 [3], there are several approaches in which PNI-NPNs can be made available via PLMNs. The only approach visible to AS, and hence the only approach that is addressed in AS specifications is the approach of using CAGs. + +## 4.9 Network-Controlled Repeaters + +### 4.9.1 Architecture + +A Network-Controlled Repeater node, referred to as NCR-node, is an RF repeater that enables wireless amplifying-and-forwarding functionality in NG-RAN. The NCR-node is capable of receiving and applying side control information from a gNB with additional functionality to support Network-Controlled Repeater. + +The NCR-node comprises an NCR-MT and an NCR-Fwd. The NCR-MT is an entity supporting a subset of the UE functionality that communicates with the gNB to receive side control information via a control link based on the NR Uu interface. The NCR-Fwd is the function performing amplifying-and-forwarding of signals between gNB and UE via the NCR-Fwd backhaul link and NCR-Fwd access link, respectively. The NCR-Fwd can support multiple beams towards the UE. The behaviour of the NCR-Fwd is controlled according to the side control information received from the gNB. The NCR-node is modelled as depicted in Figure 4.9.1-1. + +![Figure 4.9.1-1: Conceptual model of network-controlled repeater. The diagram shows a gNB on the left, a Network-Controlled Repeater in the center, and a UE on the right. The gNB is connected to the NCR-MT (Mobile Termination) inside the repeater via a 'Control link' (black arrow). The gNB is also connected to the NCR-Fwd (RF forwarding) inside the repeater via an 'NCR-Fwd Backhaul link' (red arrow). The NCR-Fwd is connected to the UE via an 'NCR-Fwd Access link' (red arrow). A dashed red line labeled 'UE Access link' connects the gNB directly to the UE, bypassing the repeater.](6be06b7dc72bb42afcb3465394667c3b_img.jpg) + +Figure 4.9.1-1: Conceptual model of network-controlled repeater. The diagram shows a gNB on the left, a Network-Controlled Repeater in the center, and a UE on the right. The gNB is connected to the NCR-MT (Mobile Termination) inside the repeater via a 'Control link' (black arrow). The gNB is also connected to the NCR-Fwd (RF forwarding) inside the repeater via an 'NCR-Fwd Backhaul link' (red arrow). The NCR-Fwd is connected to the UE via an 'NCR-Fwd Access link' (red arrow). A dashed red line labeled 'UE Access link' connects the gNB directly to the UE, bypassing the repeater. + +**Figure 4.9.1-1: Conceptual model of network-controlled repeater.** + +An NCR-MT establishes SRBs and, optionally, DRB(s) with a gNB. The establishment of DRB(s) can be used to transport OAM traffic. + +The signal that NCR-Fwd forwards is associated to the cell that the NCR-MT is connected to via the control link. Whether the NCR-Fwd can forward other signals is up to implementation. + +### 4.9.2 Capabilities + +Carrier Aggregation (CA), Multi-Radio Dual Connectivity (MR-DC), handover and its related features (e.g., CHO, DAPS, CPAC, etc.) are not supported by NCR-MT, as defined together with other limitations in TS 38.306 [11]. + +### 4.9.3 Signalling procedures + +NR RRC signalling is utilized to configure the NCR-MT to receive side control information from a gNB, which is used by the NCR-Fwd to determine whether and how to amplify-and-forward RF signals. If the side control configuration is removed, the NCR-Fwd ceases its amplifying-and-forwarding function. + +When the NCR-MT is in RRC\_CONNECTED state, the NCR-Fwd may amplify-and-forward RF signals based on the side control information received from the gNB. The NCR-MT does not support RRM measurements in RRC\_CONNECTED. + +When the NCR-MT transitions from RRC\_CONNECTED state to RRC\_INACTIVE state, the NCR-Fwd may continue to amplify-and-forward RF signals in accordance with the last side control information received from the gNB. When the NCR-MT is in RRC\_INACTIVE state, the NCR-Fwd ceases to amplify-and-forward RF signals if no suitable cell is detected, or if the NCR-MT selects a different cell than the last serving cell on which side control configuration was received. + +When an NCR-MT in RRC\_INACTIVE state determines degradation of the NCR-Fwd backhaul link beam, then the NCR-Fwd should cease amplifying-and-forwarding RF signals, and the NCR-MT should attempt to resume its RRC connection (with cause value *mo-Signalling*). The criteria to evaluate backhaul beam degradation are left to the NCR-node implementation. + +When the NCR-MT transitions from RRC\_CONNECTED state to RRC\_IDLE, the NCR-Fwd ceases any amplifying-and-forwarding of RF signals. How an NCR-MT transitions back from RRC\_IDLE state to RRC\_CONNECTED state is left to NCR-node or network implementation. + +An NCR-MT can detect RLF on the control link as specified in TS 38.331 clause 5.3.10 [12]. When RLF is detected, the NCR-MT performs the RRC re-establishment procedure as specified in TS 38.331 [12]. During the RRC re-establishment procedure, the NCR-Fwd ceases to amplify-and-forward RF signals. + +After successfully performing the RRC re-establishment procedure, the NCR-MT waits for the new side control configuration for the NCR-Fwd to resume the amplifying-and-forwarding of RF signals. + +An NCR-MT can also perform Beam Failure Detection (BFD) and Beam Failure Recovery (BFR) as described in clause 9.2.8. Once the NCR-MT detects beam failure in the control link, the NCR-Fwd should cease amplifying-and-forwarding RF signals until BFR is completed. + +#### 4.9.4 OAM aspects + +The transport connection between the NCR-node and its OAM may be provided by the NCR-MT's PDU session. A Network-Controlled Repeater may be configured with a list of allowed gNB cell(s) that the NCR-MT is allowed to connect with, and/or a list of forbidden gNB cell(s) that the NCR-MT is not allowed to connect with. + +The information on the physical beam(s) used by NCR-Fwd for access link may be provided by OAM to the gNB and the Network-Controlled Repeater for operation. How to characterize and provide the physical beams of NCR-Fwd is up to implementation. + +#### 4.9.5 Network-controlled repeater management + +Network-Controlled Repeater identification is performed in RAN, and Network-Control Repeater authorization is performed in 5GC. The general procedure of the Network-Controlled Repeater management is illustrated in Figure 4.9.5-1: + +![Sequence diagram illustrating Network-Controlled Repeater management. The diagram shows interactions between a Network-Controlled Repeater, a gNB, and an AMF. The process starts with the gNB broadcasting SIB information to the Repeater. The Repeater then sends a RACH preamble (MSG1) to the gNB. The gNB responds with a RAR (MSG2). The Repeater sends an RRC Setup Request (MSG3) to the gNB. The gNB responds with an RRC Setup (MSG4). The Repeater sends an RRC Setup Complete message to the gNB, along with Network-Controlled Repeater Indication Information. The gNB then selects a Network-Controlled Repeater capable AMF and sends an INITIAL UE MESSAGE to the AMF. The AMF sends an INITIAL CONTEXT SETUP REQUEST to the gNB, which includes Network-Controlled Repeater Authorized information.](1b2ad37940c441d410002c05ff71c7c5_img.jpg) + +``` + +sequenceDiagram + participant NCR as Network-Controlled Repeater + participant gNB + participant AMF + Note right of gNB: 7. Select Network-Controlled Repeater capable AMF + gNB->>NCR: 1. SIB Broadcasting (Network-Controlled Repeater Supported Information) + NCR->>gNB: 2. RACH preamble (MSG1) + gNB->>NCR: 3. RAR (MSG2) + NCR->>gNB: 4. RRC Setup Request (MSG3) + gNB->>NCR: 5. RRC Setup (MSG4) + NCR->>gNB: 6. RRC Setup Complete (Network-Controlled Repeater Indication Information) + gNB->>AMF: 8. INITIAL UE MESSAGE + AMF->>gNB: 9. INITIAL CONTEXT SETUP REQUEST (Network-Controlled Repeater Authorized) + +``` + +Sequence diagram illustrating Network-Controlled Repeater management. The diagram shows interactions between a Network-Controlled Repeater, a gNB, and an AMF. The process starts with the gNB broadcasting SIB information to the Repeater. The Repeater then sends a RACH preamble (MSG1) to the gNB. The gNB responds with a RAR (MSG2). The Repeater sends an RRC Setup Request (MSG3) to the gNB. The gNB responds with an RRC Setup (MSG4). The Repeater sends an RRC Setup Complete message to the gNB, along with Network-Controlled Repeater Indication Information. The gNB then selects a Network-Controlled Repeater capable AMF and sends an INITIAL UE MESSAGE to the AMF. The AMF sends an INITIAL CONTEXT SETUP REQUEST to the gNB, which includes Network-Controlled Repeater Authorized information. + +**Figure 4.9.5-1: Network-Controlled Repeater management.** + +1. The gNB broadcasts the Network-Controlled Repeater supported information via system information. + +6. When a Network-Controlled Repeater is trying to access the network as a Network-Controlled Repeater, the Network-Controlled Repeater indication is sent to the serving gNB. +7. The serving gNB selects an appropriate AMF for the Network-Controlled Repeater. +9. AMF provides Network-Controlled Repeater authorization information to the gNB. + +Other steps refer to the signalling flow as defined in 9.2.1.3. + +## 5 Physical Layer + +### 5.1 Waveform, numerology and frame structure + +The downlink transmission waveform is conventional OFDM using a Cyclic Prefix. The uplink transmission waveform is conventional OFDM using a CP with a transform precoding function performing DFT spreading that can be disabled or enabled. For operation with shared spectrum channel access in FR1, the uplink transmission waveform subcarrier mapping can map to subcarriers in one or more PRB interlaces. + +![Figure 5.1-1: Transmitter block diagram for CP-OFDM with optional DFT-spreading. The diagram shows a sequence of four rectangular blocks connected by arrows from left to right, representing the signal flow through the transmitter stages.](f1091147d93cee4dfa88498610e395a7_img.jpg) + +Figure 5.1-1: Transmitter block diagram for CP-OFDM with optional DFT-spreading. The diagram shows a sequence of four rectangular blocks connected by arrows from left to right, representing the signal flow through the transmitter stages. + +**Figure 5.1-1: Transmitter block diagram for CP-OFDM with optional DFT-spreading** + +The numerology is based on exponentially scalable sub-carrier spacing $\Delta f = 2^\mu \times 15$ kHz with $\mu = \{0, 1, 3, 4, 5, 6\}$ for PSS, SSS and PBCH and $\mu = \{0, 1, 2, 3, 5, 6\}$ for other channels. Normal CP is supported for all sub-carrier spacings, Extended CP is supported for $\mu = 2$ . 12 consecutive sub-carriers form a Physical Resource Block (PRB). Up to 275 PRBs are supported on a carrier. + +**Table 5.1-1: Supported transmission numerologies.** + +| $\mu$ | $\Delta f = 2^\mu \cdot 15$ [kHz] | CP | Supported for data | Supported for synch | +|-------|-----------------------------------|------------------|--------------------|---------------------| +| 0 | 15 | Normal | Yes | Yes | +| 1 | 30 | Normal | Yes | Yes | +| 2 | 60 | Normal, Extended | Yes | No | +| 3 | 120 | Normal | Yes | Yes | +| 4 | 240 | Normal | No | Yes | +| 5 | 480 | Normal | Yes | Yes | +| 6 | 960 | Normal | Yes | Yes | + +The UE may be configured with one or more bandwidth parts on a given component carrier, of which only one can be active at a time, as described in clauses 7.8 and 6.10 respectively. The active bandwidth part defines the UE's operating bandwidth within the cell's operating bandwidth. For initial access, and until the UE's configuration in a cell is received, initial bandwidth part detected from system information is used. + +Downlink and uplink transmissions are organized into frames with 10 ms duration, consisting of ten 1 ms subframes. Each frame is divided into two equally-sized half-frames of five subframes each. The slot duration is 14 symbols with Normal CP and 12 symbols with Extended CP, and scales in time as a function of the used sub-carrier spacing so that there is always an integer number of slots in a subframe. + +Timing Advance $TA$ is used to adjust the uplink frame timing relative to the downlink frame timing. + +![Diagram illustrating the uplink-downlink timing relation. It shows two horizontal rectangles: the top one is labeled 'Downlink frame i' and the bottom one is labeled 'Uplink frame i'. The Uplink frame is shifted to the left relative to the Downlink frame. Two vertical dashed lines extend from the left edge of the Downlink frame and the left edge of the Uplink frame down to a horizontal line. From this line, two arrows point to the left: one originating from the Downlink frame's left edge and another from the Uplink frame's left edge, with the latter arrow being further left.](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +Diagram illustrating the uplink-downlink timing relation. It shows two horizontal rectangles: the top one is labeled 'Downlink frame i' and the bottom one is labeled 'Uplink frame i'. The Uplink frame is shifted to the left relative to the Downlink frame. Two vertical dashed lines extend from the left edge of the Downlink frame and the left edge of the Uplink frame down to a horizontal line. From this line, two arrows point to the left: one originating from the Downlink frame's left edge and another from the Uplink frame's left edge, with the latter arrow being further left. + +**Figure 5.1-2: Uplink-downlink timing relation** + +Operation on both paired and unpaired spectrum is supported. + +## 5.2 Downlink + +### 5.2.1 Downlink transmission scheme + +Demodulation Reference Signal (DMRS) based spatial multiplexing is supported for Physical Downlink Shared Channel (PDSCH). Up to 8, 12, 16 and 24 orthogonal DL DMRS ports are supported for type 1, type 2, enhanced type 1, and enhanced type 2 DMRS respectively. Up to 8 orthogonal DL DMRS ports per UE are supported for SU-MIMO and up to 4 orthogonal DL DMRS ports per UE are supported for MU-MIMO. The number of SU-MIMO code words is one for 1-4 layer transmissions and two for 5-8 layer transmissions. + +The DMRS and corresponding PDSCH are transmitted using the same precoding matrix and the UE does not need to know the precoding matrix to demodulate the transmission. The transmitter may use different precoder matrix for different parts of the transmission bandwidth, resulting in frequency selective precoding. The UE may also assume that the same precoding matrix is used across a set of Physical Resource Blocks (PRBs) denoted Precoding Resource Block Group (PRG). + +Transmission durations from 2 to 14 symbols in a slot is supported. + +Aggregation of multiple slots with Transport Block (TB) repetition is supported. + +### 5.2.2 Physical-layer processing for physical downlink shared channel + +The downlink physical-layer processing of transport channels consists of the following steps: + +- Transport block CRC attachment; +- Code block segmentation and code block CRC attachment; +- Channel coding: LDPC coding; +- Physical-layer hybrid-ARQ processing; +- Rate matching; +- Scrambling; +- Modulation: QPSK, 16QAM, 64QAM, 256QAM, and 1024QAM; +- Layer mapping; +- Mapping to assigned resources and antenna ports. + +The UE may assume that at least one symbol with demodulation reference signal is present on each layer in which PDSCH is transmitted to a UE, and up to 3 additional DMRS can be configured by higher layers. + +Phase Tracking RS may be transmitted on additional symbols to aid receiver phase tracking. + +The DL-SCH physical layer model is described in TS 38.202 [20]. + +### 5.2.3 Physical downlink control channels + +The Physical Downlink Control Channel (PDCCH) can be used to schedule DL transmissions on PDSCH and UL transmissions on PUSCH, where the Downlink Control Information (DCI) on PDCCH includes: + +- Downlink assignments containing at least modulation and coding format, resource allocation, and hybrid-ARQ information related to DL-SCH; +- Uplink scheduling grants containing at least modulation and coding format, resource allocation, and hybrid-ARQ information related to UL-SCH. + +In addition to scheduling, PDCCH can be used to for: + +- Activation and deactivation of configured PUSCH transmission with configured grant; +- Activation and deactivation of PDSCH semi-persistent transmission; +- Notifying one or more UEs of the slot format; +- Notifying one or more UEs of the PRB(s) and OFDM symbol(s) where the UE may assume no transmission is intended for the UE; +- Transmission of TPC commands for PUCCH and PUSCH; +- Transmission of one or more TPC commands for SRS transmissions by one or more UEs; +- Switching a UE's active bandwidth part; +- Initiating a random access procedure; +- Indicating the UE(s) to monitor the PDCCH during the next occurrence of the DRX on-duration; +- In IAB context, indicating the availability for soft symbols of an IAB-DU; +- Triggering one shot HARQ-ACK codebook feedback; +- For operation with shared spectrum channel access: + - Triggering search space set group switching; + - Indicating one or more UEs about the available RB sets and channel occupancy time duration; + - Indicating downlink feedback information for configured grant PUSCH (CG-DFI). + +A UE monitors a set of PDCCH candidates in the configured monitoring occasions in one or more configured Control REsource SETs (CORESETs) according to the corresponding search space configurations. + +A CORESET consists of a set of PRBs with a time duration of 1 to 3 OFDM symbols. The resource units Resource Element Groups (REGs) and Control Channel Elements (CCEs) are defined within a CORESET with each CCE consisting a set of REGs. Control channels are formed by aggregation of CCE. Different code rates for the control channels are realized by aggregating different number of CCE. Interleaved and non-interleaved CCE-to-REG mapping are supported in a CORESET. + +The PDCCH repetition is operated by using two search spaces which are explicitly linked by configuration provided by the RRC layer, and are associated with corresponding CORESETs. For PDCCH repetition, two linked search spaces are configured with the same number of candidates, and two PDCCH candidates in two search spaces are linked with the same candidate index. When PDCCH repetition is scheduled to a UE, an intra-slot repetition is allowed and each repetition has the same number of CCEs and coded bits, and corresponds to the same DCI payload. + +Polar coding is used for PDCCH. + +Each resource element group carrying PDCCH carries its own DMRS. + +QPSK modulation is used for PDCCH. + +## 5.2.4 Synchronization signal and PBCH block + +The Synchronization Signal and PBCH block (SSB) consists of primary and secondary synchronization signals (PSS, SSS), each occupying 1 symbol and 127 subcarriers, and PBCH spanning across 3 OFDM symbols and 240 subcarriers, but on one symbol leaving an unused part in the middle for SSS as shown in Figure 5.2.4-1. For the 3 MHz channel bandwidth, the PBCH is further equally punctured from both edges to span 144 subcarriers. The possible time locations of SSBs within a half-frame are determined by sub-carrier spacing and the periodicity of the half-frames where SSBs are transmitted is configured by the network. During a half-frame, different SSBs may be transmitted in different spatial directions (i.e. using different beams, spanning the coverage area of a cell). + +Within the frequency span of a carrier, multiple SSBs can be transmitted. The PCIs of SSBs transmitted in different frequency locations do not have to be unique, i.e. different SSBs in the frequency domain can have different PCIs. However, when an SSB is associated with an RMSI, the SSB is referred to as a Cell-Defining SSB (CD-SSB). A PCell is always associated to a CD-SSB located on the synchronization raster. + +When an SSB is not associated with an RMSI, the SSB is referred to as a non-Cell Defining SSB (NCD-SSB), which can be used to perform RLM, BFD, and RRM measurements and measurements for RA resource selection inside the active DL BWP when the active BWP does not contain the CD-SSB. A UE may be configured with multiple SSBs provided that each BWP is configured with at most one SSB (CD-SSB or NCD-SSB). + +![Figure 5.2.4-1: Time-frequency structure of SSB. The diagram shows a vertical rectangle representing the SSB in the time domain. It is divided into four horizontal sections. The top section is the largest, representing the PBCH. Below it is a smaller section representing the PSS. The third section is the smallest, representing the SSS. The bottom section is another small section representing the PBCH. A bracket on the left side groups the top and bottom sections, indicating they are part of the PBCH. The diagram illustrates the time-frequency structure of the SSB, showing the relative durations of the different signals.](43979979715bb3304389a0cb18f34444_img.jpg) + +Figure 5.2.4-1: Time-frequency structure of SSB. The diagram shows a vertical rectangle representing the SSB in the time domain. It is divided into four horizontal sections. The top section is the largest, representing the PBCH. Below it is a smaller section representing the PSS. The third section is the smallest, representing the SSS. The bottom section is another small section representing the PBCH. A bracket on the left side groups the top and bottom sections, indicating they are part of the PBCH. The diagram illustrates the time-frequency structure of the SSB, showing the relative durations of the different signals. + +**Figure 5.2.4-1: Time-frequency structure of SSB** + +Polar coding is used for PBCH. + +The UE may assume a band-specific sub-carrier spacing for the SSB unless a network has configured the UE to assume a different sub-carrier spacing. + +PBCH symbols carry its own frequency-multiplexed DMRS. + +QPSK modulation is used for PBCH. + +The PBCH physical layer model is described in TS 38.202 [20]. + +## 5.2.5 Physical layer procedures + +### 5.2.5.1 Link adaptation + +Link adaptation (AMC: adaptive modulation and coding) with various modulation schemes and channel coding rates is applied to the PDSCH. The same coding and modulation is applied to all groups of resource blocks belonging to the same L2 PDU scheduled to one user within one transmission duration and within a MIMO codeword. + +For channel state estimation purposes, the UE may be configured to measure CSI-RS and estimate the downlink channel state based on the CSI-RS measurements. The UE feeds the estimated channel state back to the gNB to be used in link adaptation. + +### 5.2.5.2 Power Control + +Downlink power control can be used. + +### 5.2.5.3 Cell search + +Cell search is the procedure by which a UE acquires time and frequency synchronization with a cell and detects the Cell ID of that cell. NR cell search is based on the primary and secondary synchronization signals, and PBCH DMRS, located on the synchronization raster. + +### 5.2.5.4 HARQ + +Asynchronous Incremental Redundancy Hybrid ARQ is supported. The gNB provides the UE with the HARQ-ACK feedback timing either dynamically in the DCI or semi-statically in an RRC configuration. Retransmission of HARQ-ACK feedback is supported by using enhanced dynamic codebook and/or one-shot triggering of HARQ-ACK transmission for (i) all configured CCs and HARQ processes in the PUCCH group, (ii) a configured subset of CCs and/or HARQ processes in the PUCCH group, or (iii) a dynamically indicated HARQ-ACK feedback instance. For HARQ-ACK of SPS PDSCH without associated PDCCH, in case of HARQ-ACK dropping due to TDD specific collisions, the HARQ-ACK feedback can be deferred to a next available PUCCH transmission occasion. + +The UE may be configured to receive code block group based transmissions where retransmissions may be scheduled to carry a sub-set of all the code blocks of a TB. + +### 5.2.5.5 Reception of SIB1 + +The Master Information Block (MIB) on PBCH provides the UE with parameters (e.g. CORESET#0 configuration) for monitoring of PDCCH for scheduling PDSCH that carries the System Information Block 1 (SIB1). PBCH may also indicate that there is no associated SIB1, in which case the UE may be pointed to another frequency from where to search for an SSB that is associated with a SIB1 as well as a frequency range where the UE may assume no SSB associated with SIB1 is present. The indicated frequency range is confined within a contiguous spectrum allocation of the same operator in which SSB is detected. + +## 5.2.6 Downlink Reference Signals and Measurements for Positioning + +The DL Positioning Reference Signals (DL PRS) are defined to facilitate support of different positioning methods such as DL-TDOA, DL-AoD, multi-RTT through the following set of UE measurements DL RSTD, DL PRS-RSRP, and UE Rx-Tx time difference respectively as described in TS 38.305 [42]. + +Besides DL PRS signals, UE can use SSB and CSI-RS for RRM (RSRP and RSRQ) measurements for E-CID type of positioning. + +## 5.3 Uplink + +### 5.3.1 Uplink transmission scheme + +Two transmission schemes are supported for PUSCH: codebook based transmission and non-codebook based transmission. + +For codebook based transmission, the gNB provides the UE with a transmit precoding matrix indication in the DCI. The UE uses the indication to select the PUSCH transmit precoder from the codebook. For non-codebook based transmission, the UE determines its PUSCH precoder based on wideband SRI field from the DCI. + +DMRS based spatial multiplexing is supported for PUSCH. Up to 8, 12, 16, and 24 orthogonal UL DMRS ports are supported for type 1, type 2, enhanced type 1, and enhanced type 2 DMRS respectively. For a given UE, up to 4 or up to 8 layer transmissions are supported. The number of code words is one for 1 to 4 layer transmission and two for 5 to 8 layer transmission. When transform precoding is used, only a single MIMO layer transmission is supported. + +Transmission durations from 1 to 14 symbols in a slot is supported. + +Aggregation of multiple slots with TB repetition is supported. + +Two types of frequency hopping are supported, intra-slot frequency hopping, and in case of slot aggregation, inter-slot frequency hopping. Intra-slot and inter-slot frequency hopping are not supported when PRB interlace uplink transmission waveform is used. + +PUSCH may be scheduled with DCI on PDCCH, or a semi-static configured grant may be provided over RRC, where two types of operation are supported: + +- The first PUSCH is triggered with a DCI, with subsequent PUSCH transmissions following the RRC configuration and scheduling received on the DCI, or +- The PUSCH is triggered by data arrival to the UE's transmit buffer and the PUSCH transmissions follow the RRC configuration. + +### 5.3.2 Physical-layer processing for physical uplink shared channel + +The uplink physical-layer processing of transport channels consists of the following steps: + +- Transport Block CRC attachment; +- Code block segmentation and Code Block CRC attachment; +- Channel coding: LDPC coding; +- Physical-layer hybrid-ARQ processing; +- Rate matching; +- Scrambling; +- Modulation: $\pi/2$ BPSK (with transform precoding only), QPSK, 16QAM, 64QAM and 256QAM; +- Layer mapping, transform precoding (enabled/disabled by configuration), and pre-coding; +- Mapping to assigned resources and antenna ports. + +The UE transmits at least one symbol with demodulation reference signal on each layer on each frequency hop in which the PUSCH is transmitted, and up to 3 additional DMRS can be configured by higher layers. + +Phase Tracking RS may be transmitted on additional symbols to aid receiver phase tracking. + +The UL-SCH physical layer model is described in TS 38.202 [20]. + +For configured grants operation with shared spectrum channel access, described in clause 10.3, a CG-UCI (Configured Grant Uplink Control Information) can be transmitted in PUSCH scheduled by configured uplink grant. + +### 5.3.3 Physical uplink control channel + +Physical uplink control channel (PUCCH) carries the Uplink Control Information (UCI) from the UE to the gNB. Five formats of PUCCH exist, depending on the duration of PUCCH and the UCI payload size: + +- Format #0: Short PUCCH of 1 or 2 symbols with small UCI payloads of up to two bits with UE multiplexing capacity of up to 6 UEs with 1-bit payload in the same PRB; +- Format #1: Long PUCCH of 4-14 symbols with small UCI payloads of up to two bits with UE multiplexing capacity of up to 84 UEs without frequency hopping and 36 UEs with frequency hopping in the same PRB; +- Format #2: Short PUCCH of 1 or 2 symbols with large UCI payloads of more than two bits with no UE multiplexing capability in the same PRBs; +- Format #3: Long PUCCH of 4-14 symbols with large UCI payloads with no UE multiplexing capability in the same PRBs; +- Format #4: Long PUCCH of 4-14 symbols with moderate UCI payloads with multiplexing capacity of up to 4 UEs in the same PRBs. + +The short PUCCH format of up to two UCI bits is based on sequence selection, while the short PUCCH format of more than two UCI bits frequency multiplexes UCI and DMRS. The long PUCCH formats time-multiplex the UCI and DMRS. Frequency hopping is supported for long PUCCH formats and for short PUCCH formats of duration of 2 symbols. Short and long PUCCH formats can be repeated over multiple slots or sub-slots, where the repetition factor is either indicated dynamically in the DCI or semi-statically in an RRC configuration. + +For operation with shared spectrum channel access in FR1, PUCCH Format #0, #1, #2, #3 are extended to use resource in one PRB interlace (up to two interlaces for Format #2 and Format #3) in one RB Set. PUCCH Format #2 and #3 are enhanced to support multiplexing capacity of up to 4 UEs in the same PRB interlace when one interlace is used. + +For operation in FR2-2, PUCCH Format #0, #1, #4 are extended to use resource in configurable number of continuous PRBs, up to 16 PRBs. + +Up to two PUCCH configurations can be configured for a UE per PUCCH group (see TS 38.331 [12]), where the first PUCCH configuration is associated with a PUCCH of priority index 0 (low) and the second PUCCH configuration is associated with a PUCCH of priority index 1 (high). + +UCI multiplexing in PUCCH is supported when PUCCH transmissions of UCIs coincide in time, and are associated with the same priority (high/low). In addition, multiplexing of HARQ-ACK of priority index 0 (low) and UCI of priority index 1 (high) in PUCCH of priority index 1 (high) is supported when PUCCH transmissions of HARQ-ACK of priority index 0 and UCI of priority index 1 (high) coincide in time. + +UCI multiplexing in PUSCH is supported when UCI and PUSCH transmissions coincide in time, either due to transmission of a UL-SCH transport block or due to triggering of A-CSI transmission without UL-SCH transport block, and are associated with the same priority (high/low). In addition, HARQ-ACK multiplexing of a certain priority in PUSCH of a different priority is supported when HARQ-ACK and PUSCH transmissions coincide in time, either due to transmission of a UL-SCH transport block or due to triggering of A-CSI transmission without UL-SCH transport block: + +- UCI carrying HARQ-ACK feedback with 1 or 2 bits is multiplexed by puncturing PUSCH; +- In all other cases UCI is multiplexed by rate matching PUSCH. + +UCI consists of the following information: + +- CSI; +- ACK/NAK; +- Scheduling request. + +Simultaneous transmission of PUCCH and PUSCH associated with different priorities on cells of different bands in a PUCCH group is supported, where UCI multiplexing in the PUCCH associated with a priority in combination of UCI multiplexing in a PUSCH associated with a different priority is supported if the UCI multiplexed on PUSCH is of same priority as the PUSCH. + +For operation with shared spectrum channel access, multiplexing of CG-UCI and PUCCH carrying HARQ-ACK feedback can be configured by the gNB. If not configured, when PUCCH overlaps with PUSCH scheduled by a configured grant within a PUCCH group and PUCCH carries HARQ ACK feedback, PUSCH scheduled by configured grant is skipped. + +QPSK and $\pi/2$ BPSK modulation can be used for long PUCCH with more than 2 bits of information, QPSK is used for short PUCCH with more than 2 bits of information and BPSK and QPSK modulation can be used for long PUCCH with up to 2 information bits. + +Transform precoding is applied to PUCCH Format #3 and Format #4. + +Channel coding used for uplink control information is described in table 5.3.3-1. + +**Table 5.3.3-1: Channel coding for uplink control information** + +| Uplink Control Information size including CRC, if present | Channel code | +|-----------------------------------------------------------|------------------| +| 1 | Repetition code | +| 2 | Simplex code | +| 3-11 | Reed Muller code | +| >11 | Polar code | + +## 5.3.4 Random access + +Random access preamble sequences, of four different lengths are supported. Sequence length 839 is applied with subcarrier spacings of 1.25 and 5 kHz, sequence length 139 is applied with subcarrier spacings of 15, 30, 60, 120, 480, and 960 kHz, sequence length of 571 is applied with subcarrier spacings of 30, 120, and 480 kHz, and sequence length 1151 is applied with subcarrier spacings of 15 and 120 kHz. Sequence length 839 supports unrestricted sets and restricted sets of Type A and Type B, while sequence lengths 139, 571, and 1151 support unrestricted sets only. Sequence length 839 is only used for operation with licensed channel access while sequence length 139 can be used for operation with either licensed or shared spectrum channel access. For FR1, sequence lengths of 571 and 1151 can be used only for operation with shared spectrum channel access. For FR2-2, sequence lengths of 571 can be used for operation with either licensed or shared spectrum channel access only with subcarrier spacings of 120 kHz and 480 kHz and sequence lengths of 1151 can be used for operation with either licensed or shared spectrum channel access only with subcarrier spacings of 120 kHz. + +Multiple PRACH preamble formats are defined with one or more PRACH OFDM symbols, and different CP and guard time. The PRACH preamble configuration to use is provided to the UE in the system information. + +For IAB additional random access configurations are defined. These configurations are obtained by extending the random access configurations defined for UEs via scaling the periodicity and/or offsetting the time domain position of the RACH occasions. + +IAB-MTs can be provided with random access configurations (as defined for UEs or after applying the aforementioned scaling/offsetting) different from random access configurations provided to UEs. + +The UE calculates the PRACH transmit power for the retransmission of the preamble based on the most recent estimate pathloss and power ramping counter. + +The system information provides information for the UE to determine the association between the SSB and the RACH resources. The RSRP threshold for SSB selection for RACH resource association is configurable by network. + +## 5.3.5 Physical layer procedures + +### 5.3.5.1 Link adaptation + +Four types of link adaptation are supported as follows: + +- Adaptive transmission bandwidth; +- Adaptive transmission duration; + +- Transmission power control; +- Adaptive modulation and channel coding rate. + +For channel state estimation purposes, the UE may be configured to transmit SRS that the gNB may use to estimate the uplink channel state and use the estimate in link adaptation. + +### 5.3.5.2 Uplink Power control + +The gNB determines the desired uplink transmit power and provides uplink transmit power control commands to the UE. The UE uses the provided uplink transmit power control commands to adjust its transmit power. + +### 5.3.5.3 Uplink timing control + +The gNB (including IAB-DU and IAB-donor-DU) determines the desired Timing Advance setting and provides that to the UE (or IAB-MT). The UE/IAB-MT uses the provided TA to determine its uplink transmit timing relative to the UE's/IAB-MT's observed downlink receive timing. + +An IAB-node may support additional modes for uplink timing: + +- The IAB-MT uses the provided TA plus a provided additional offset to determine its uplink transmission timing, to facilitate parent node's IAB-MT Rx / IAB-DU Rx multiplexing; +- The IAB-MT aligns its uplink transmission timing to that of the collocated IAB-DU downlink transmission timing, to facilitate IAB-MT Tx / IAB-DU Tx multiplexing of this IAB-node. + +The IAB-node uplink timing mode is indicated by the parent node via MAC-CE. + +### 5.3.5.4 HARQ + +Asynchronous Incremental Redundancy Hybrid ARQ is supported. The gNB schedules each uplink transmission and retransmission using the uplink grant on DCI. For operation with shared spectrum channel access, UE can also retransmit on configured grants if configured. + +The UE may be configured to transmit code block group based transmissions where retransmissions may be scheduled to carry a sub-set of all the code blocks of a transport block. + +Up to two HARQ-ACK codebooks corresponding to a priority (high/low) can be constructed simultaneously. For each HARQ-ACK codebook, more than one PUCCH for HARQ-ACK transmission within a slot is supported. Each PUCCH is limited within one sub-slot, and the sub-slot pattern is configured per HARQ-ACK codebook. + +### 5.3.5.5 Prioritization of overlapping transmissions + +PUSCH and PUCCH can be associated with a priority (high/low) by RRC or L1 signalling. If a PUCCH transmission overlaps in time with a transmission of a PUSCH or another PUCCH, only the PUCCH or PUSCH associated with a high priority can be transmitted. + +## 5.3.6 Uplink Reference Signals and Measurements for Positioning + +The periodic, semipersistent and aperiodic transmission of Rel-15 SRS is defined for gNB UL RTOA, UL SRS-RSRP, UL-AoA measurements to facilitate support of UL TDOA and UL AoA positioning methods as described in TS 38.305 [42]. + +The periodic, semipersistent and aperiodic transmission of SRS for positioning is defined for gNB UL RTOA, UL SRS-RSRP, UL-AoA, gNB Rx-Tx time difference measurements to facilitate support of UL TDOA, UL AoA and multi-RTT positioning methods as described in TS 38.305 [42]. + +## 5.4 Carrier aggregation + +### 5.4.1 Carrier aggregation + +In Carrier Aggregation (CA), two or more Component Carriers (CCs) are aggregated. A UE may simultaneously receive or transmit on one or multiple CCs depending on its capabilities: + +- A UE with single timing advance capability for CA can simultaneously receive and/or transmit on multiple CCs corresponding to multiple serving cells sharing the same timing advance (multiple serving cells grouped in one TAG); +- A UE with multiple timing advance capability for CA can simultaneously receive and/or transmit on multiple CCs corresponding to multiple serving cells with different timing advances (multiple serving cells grouped in multiple TAGs). NG-RAN ensures that each TAG contains at least one serving cell; +- A non-CA capable UE can receive on a single CC and transmit on a single CC corresponding to one serving cell only (one serving cell in one TAG). + +CA is supported for both contiguous and non-contiguous CCs. When CA is deployed frame timing and SFN are aligned across cells that can be aggregated, or an offset in multiples of slots between the PCell/PSCell and an SCell is configured to the UE. The maximum number of configured CCs for a UE is 16 for DL and 16 for UL. + +### 5.4.2 Supplementary Uplink + +In conjunction with a UL/DL carrier pair (FDD band) or a bidirectional carrier (TDD band), a UE may be configured with additional, Supplementary Uplink (SUL). SUL differs from the aggregated uplink in that the UE may be scheduled to transmit either on the supplementary uplink or on the uplink of the carrier being supplemented, but not on both at the same time. + +### 5.4.3 Uplink Tx switching + +In uplink CA or SUL, a UE configured with uplink Tx switching can have Tx chain(s) dynamically switched from one uplink band or two uplink bands to another uplink band or two uplink bands for enabling up to 2Tx UL transmission in one uplink band or simultaneous UL transmissions in two uplink bands at a time. + +## 5.5 Transport Channels + +The physical layer offers information transfer services to MAC and higher layers. The physical layer transport services are described by *how* and with what characteristics data are transferred over the radio interface. An adequate term for this is "Transport Channel". This should be clearly separated from the classification of *what* is transported, which relates to the concept of logical channels at MAC sublayer. + +Downlink transport channel types are: + +1. **Broadcast Channel (BCH)** characterised by: + - fixed, pre-defined transport format; + - requirement to be broadcast in the entire coverage area of the cell, either as a single message or by beamforming different BCH instances. +2. **Downlink Shared Channel (DL-SCH)** characterised by: + - support for HARQ; + - support for dynamic link adaptation by varying the modulation, coding and transmit power; + - possibility to be broadcast in the entire cell; + - possibility to use beamforming; + - support for both dynamic and semi-static resource allocation; + +- support for UE discontinuous reception (DRX) to enable UE power saving. + +3. **Paging Channel (PCH)** characterised by: + +- support for UE discontinuous reception (DRX) to enable UE power saving (DRX cycle is indicated by the network to the UE); +- requirement to be broadcast in the entire coverage area of the cell, either as a single message or by beamforming different BCH instances; +- mapped to physical resources which can be used dynamically also for traffic/other control channels. + +Uplink transport channel types are: + +1. **Uplink Shared Channel (UL-SCH)** characterised by: + +- possibility to use beamforming; +- support for dynamic link adaptation by varying the transmit power and potentially modulation and coding; +- support for HARQ; +- support for both dynamic and semi-static resource allocation. + +2. **Random Access Channel(s) (RACH)** characterised by: + +- limited control information; +- collision risk. + +Sidelink transport channel types are: + +1. **Sidelink broadcast channel (SL-BCH)** characterised by: + +- pre-defined transport format. + +2. **Sidelink shared channel (SL-SCH)** characterised by: + +- support for unicast transmission, groupcast transmission and broadcast transmission; +- support for both UE autonomous resource selection and scheduled resource allocation by NG-RAN; +- support for both dynamic and semi-static resource allocation when UE is allocated resources by the NG-RAN; +- support for HARQ; +- support for dynamic link adaptation by varying the transmit power, modulation and coding; +- support for SL discontinuous reception (SL DRX) to enable UE power saving. + +Association of transport channels to physical channels is described in TS 38.202 [20]. + +## 5.6 Access to Shared Spectrum + +### 5.6.1 Overview + +NR Radio Access operating with shared spectrum channel access can operate in different modes where either PCell, PSCell, or SCells can be in shared spectrum and an SCell may or may not be configured with uplink. The applicable deployment scenarios are described in Annex B.3. + +The gNB performs channel access mode procedures as described in TS 37.213 [37]. The gNB and the UE may apply Listen-Before-Talk (LBT) before performing a transmission on a cell configured with shared spectrum channel access. When LBT is applied, the transmitter listens to/senses the channel to determine whether the channel is free or busy and performs transmission only if the channel is sensed free. + +When the UE detects consistent uplink LBT failures, it takes actions as specified in TS 38.321 [6]. The detection is per Bandwidth Part (BWP) and based on all uplink transmissions within this BWP. When consistent uplink LBT failures are detected on SCell(s), the UE reports this to the corresponding gNB (MN for MCG, SN for SCG) via MAC CE on a different serving cell than the SCell(s) where the failures were detected. If no resources are available to transmit the MAC CE, a Scheduling Request (SR) can be transmitted by the UE. When consistent uplink LBT failures are detected on SpCell, the UE switches to another UL BWP with configured RACH resources on that cell, initiates RACH, and reports the failure via MAC CE. When multiple UL BWPs are available for switching, it is up to the UE implementation which one to select. For PSCell, if consistent uplink LBT failures are detected on all the UL BWPs with configured RACH resources, the UE declares SCG RLF and reports the failure to the MN via *SCGFailureInformation*. For PCell, if the uplink LBT failures are detected on all the UL BWP(s) with configured RACH resources, the UE declares RLF. + +## 5.6.2 Channel Access Priority Classes + +The Channel Access Priority Classes (CAPC) of radio bearers and MAC CEs are either fixed or configurable for operation in FR1: + +- Fixed to the lowest priority for the padding BSR and recommended bit rate MAC CEs; +- Fixed to the highest priority for SRB0, SRB1, SRB3 and other MAC CEs; +- Configured by the gNB for SRB2 and DRB. + +When choosing the CAPC of a DRB, the gNB takes into account the 5QIs of all the QoS flows multiplexed in that DRB while considering fairness between different traffic types and transmissions. Table 5.6.2-1 below shows which CAPC should be used for which standardized 5QIs i.e. which CAPC to use for a given QoS flow. + +NOTE: A QoS flow corresponding to a non-standardized 5QI (i.e. operator specific 5QI) should use the CAPC of the standardized 5QI which best matches the QoS characteristics of the non-standardized 5QI. + +**Table 5.6.2-1: Mapping between Channel Access Priority Classes and 5QI** + +| CAPC | 5QI | +|-------|-----------------------------------------------------| +| 1 | 1, 3, 5, 65, 66, 67, 69, 70, 79, 80, 82, 83, 84, 85 | +| 2 | 2, 7, 71 | +| 3 | 4, 6, 8, 9, 72, 73, 74, 76 | +| 4 | - | +| NOTE: | lower CAPC value means higher priority | + +When performing Type 1 LBT for the transmission of an uplink TB (see TS 37.213 [37], clause 4.2.1.1) and when the CAPC is not indicated in the DCI, the UE shall select the CAPC as follows: + +- If only MAC CE(s) are included in the TB, the highest priority CAPC of those MAC CE(s) is used; or +- If CCCH SDU(s) are included in the TB, the highest priority CAPC is used; or +- If DCCH SDU(s) are included in the TB, the highest priority CAPC of the DCCH(s) is used; or +- The lowest priority CAPC of the logical channel(s) with MAC SDU multiplexed in the TB is used otherwise. + +## 5.7 Sidelink + +### 5.7.1 General + +Sidelink supports UE-to-UE direct communication using the sidelink resource allocation modes, physical-layer signals/channels, and physical layer procedures below. + +## 5.7.2 Sidelink resource allocation modes + +Two sidelink resource allocation modes are supported: mode 1 and mode 2. In mode 1, the sidelink resource allocation is provided by the network. In mode 2, UE decides the SL transmission resources in the resource pool(s). + +## 5.7.3 Physical sidelink channels and signals + +Physical Sidelink Control Channel (PSCCH) indicates resource and other transmission parameters used by a UE for PSSCH. PSCCH transmission is associated with a DM-RS. + +Physical Sidelink Shared Channel (PSSCH) transmits the TBs of data themselves, and control information for HARQ procedures and CSI feedback triggers, etc. At least 6 OFDM symbols within a slot are used for PSSCH transmission. PSSCH transmission is associated with a DM-RS and may be associated with a PT-RS. + +Physical Sidelink Feedback Channel (PSFCH) carries HARQ feedback over the sidelink from a UE which is an intended recipient of a PSSCH transmission to the UE which performed the transmission. PSFCH sequence is transmitted in one PRB repeated over two OFDM symbols near the end of the sidelink resource in a slot. + +The Sidelink synchronization signal consists of sidelink primary and sidelink secondary synchronization signals (S-PSS, S-SSS), each occupying 2 symbols and 127 subcarriers. Physical Sidelink Broadcast Channel (PSBCH) occupies 9 and 7 symbols for normal and extended CP cases respectively, including the associated DM-RS. + +## 5.7.4 Physical layer procedures for sidelink + +### 5.7.4.1 HARQ feedback + +Sidelink HARQ feedback uses PSFCH and can be operated in one of two options. In one option, which can be configured for unicast and groupcast, PSFCH transmits either ACK or NACK using a resource dedicated to a single PSFCH transmitting UE. In another option, which can be configured for groupcast, PSFCH transmits NACK, or no PSFCH signal is transmitted, on a resource that can be shared by multiple PSFCH transmitting UEs. The latter option is not supported for sidelink in unlicensed spectrum. + +In sidelink resource allocation mode 1, a UE which received PSFCH can report sidelink HARQ feedback to gNB via PUCCH or PUSCH. + +### 5.7.4.2 Power Control + +For in-coverage operation, the power spectral density of the sidelink transmissions can be adjusted based on the pathloss from the gNB. + +For unicast, the power spectral density of some sidelink transmissions can be adjusted based on the pathloss between the two communicating UEs. + +### 5.7.4.3 CSI report + +For unicast, channel state information reference signal (CSI-RS) is supported for CSI measurement and reporting in sidelink. A CSI report is carried in a sidelink MAC CE. + +## 5.7.5 Physical layer measurement definition + +For measurement on the sidelink, the following UE measurement quantities are supported: + +- PSBCH reference signal received power (PSBCH RSRP); +- PSSCH reference signal received power (PSSCH-RSRP); +- PSCCH reference signal received power (PSCCH-RSRP); +- Sidelink received signal strength indicator (SL RSSI); +- Sidelink channel occupancy ratio (SL CR); + +- Sidelink channel busy ratio (SL CBR). + +## 5.7.6 Sidelink Reference Signal and Measurements for Positioning + +The Sidelink Positioning Reference Signal (SL-PRS) is defined to facilitate Ranging/Sidelink positioning methods, such as SL-TOA, SL-TDOA, SL-RTT, SL-AoA, through the following set of measurements SL-PRS RSRP, RSRPP, RTOA, RSTD, Rx-Tx timing difference and AoA as described in TS 38.305 [42]. + +--- + +# 6 Layer 2 + +## 6.1 Overview + +The layer 2 of NR is split into the following sublayers: Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP) and Service Data Adaptation Protocol (SDAP). The two figures below depict the Layer 2 architecture for downlink and uplink, where: + +- The physical layer offers to the MAC sublayer transport channels; +- The MAC sublayer offers to the RLC sublayer logical channels; +- The RLC sublayer offers to the PDCP sublayer RLC channels; +- The PDCP sublayer offers to the SDAP sublayer radio bearers; +- The SDAP sublayer offers to 5GC QoS flows; +- *Comp.* refers to header compression or uplink data compression; +- *Segm.* refers to segmentation; +- Control channels (BCCH, PCCH are not depicted for clarity). + +NOTE: The gNB may not be able to guarantee that a L2 buffer overflow will never occur. If such overflow occurs, the UE may discard packets in the L2 buffer. + +![Downlink Layer 2 Structure diagram showing data flow from a top block through two intermediate layers to a bottom layer, with various sub-components and interfaces indicated by lines and dashed separators.](a0e8fe7862a6d7341faf5dac275277cc_img.jpg) + +The diagram illustrates the Downlink Layer 2 Structure. It consists of four main horizontal layers separated by dashed lines. The top layer is a large black rectangle with a small white rectangle at its base. The second layer is a black rectangle containing a long white rectangle and a white trapezoid. The third layer is a black rectangle with a small white rectangle at its base. The bottom layer is a white rectangle. Vertical lines connect the layers, indicating data flow and interfaces. + +Downlink Layer 2 Structure diagram showing data flow from a top block through two intermediate layers to a bottom layer, with various sub-components and interfaces indicated by lines and dashed separators. + +Figure 6.1-1: Downlink Layer 2 Structure + +![Uplink Layer 2 Structure diagram showing data flow from a bottom block through two intermediate layers to a top layer, with various sub-components and interfaces indicated by lines and dashed separators.](df1966d80c74bc127f159a48f38b13ee_img.jpg) + +The diagram illustrates the Uplink Layer 2 Structure. It consists of four main horizontal layers separated by dashed lines. The bottom layer is a white rectangle. The second layer is a black rectangle with a small white rectangle at its base. The third layer is a black rectangle containing a long white rectangle. The top layer is a white rectangle. Vertical lines connect the layers, indicating data flow and interfaces. + +Uplink Layer 2 Structure diagram showing data flow from a bottom block through two intermediate layers to a top layer, with various sub-components and interfaces indicated by lines and dashed separators. + +Figure 6.1-2: Uplink Layer 2 Structure + +Radio bearers are categorized into two groups: data radio bearers (DRB) for user plane data and signalling radio bearers (SRB) for control plane data. + +For IAB, the Layer 2 of NR includes: MAC, RLC, Backhaul Adaptation Protocol (BAP), PDCP and optionally SDAP. The BAP sublayer supports routing across the IAB topology and traffic mapping to BH RLC channels for enforcement of traffic prioritization and QoS. + +Figures 6.1-3 below depicts the Layer-2 architecture for downlink on the IAB-donor. Figures 6.1-4 and 6.1-5 depict the Layer-2 architecture for downlink and uplink on the IAB-node, where the BAP sublayer offers routing functionality and mapping to BH RLC channels. + +![Diagram of DL L2-structure for user plane at IAB-donor](7722d62e33dcc894cc8555e9474c5606_img.jpg) + +The diagram illustrates the Layer 2 architecture for the user plane in a downlink scenario at an IAB-donor. It shows two parallel vertical paths representing different data flows. The left path consists of two vertical lines with horizontal dashed lines intersecting them at various points, representing the flow of data through different protocol layers. The right path is a single vertical line that passes through a trapezoidal shape (representing the MAC layer) and a rectangular shape (representing the RLC layer), both of which are also intersected by horizontal dashed lines. The overall structure shows the hierarchical processing of user plane data at the donor node. + +Diagram of DL L2-structure for user plane at IAB-donor + +**Figure 6.1-3: DL L2-structure for user plane at IAB-donor** + +![Diagram illustrating the DL L2-structure at an IAB-node. It shows a hierarchy of nodes connected by vertical lines, with horizontal dashed lines separating different levels. The structure includes a top node, two intermediate nodes, and a bottom node represented by a trapezoidal shape.](9e8ebf03cae78f4f81b697548c2d7250_img.jpg) + +The diagram illustrates the DL L2-structure at an IAB-node. It features a hierarchical tree structure. At the top, a vertical line descends to a horizontal dashed line. From this line, two vertical lines descend to another horizontal dashed line. From the right vertical line, two more vertical lines descend to a third horizontal dashed line. Below this, a single horizontal dashed line is shown. At the bottom, a trapezoidal shape (wider at the top) is connected to a vertical line that descends to a final horizontal dashed line. A small vertical line segment is also present between the third and fourth horizontal dashed lines. + +Diagram illustrating the DL L2-structure at an IAB-node. It shows a hierarchy of nodes connected by vertical lines, with horizontal dashed lines separating different levels. The structure includes a top node, two intermediate nodes, and a bottom node represented by a trapezoidal shape. + +Figure 6.1-4: DL L2-structure at IAB-node + +![Figure 6.1-5: UL L2-structure at IAB-node. This diagram illustrates the Layer 2 protocol stack for an IAB-node, showing data flow from child IAB-nodes and local UEs through various processing blocks like HARQ, RLC, and MAC.](2cf3896394a2342a2b46c504ab9a8830_img.jpg) + +The diagram shows the UL L2-structure at an IAB-node. It is divided into three main vertical paths for data flow: + +- Backhaul Link from child IAB-node (left):** Data flows from the child IAB-node through a **RX HARQ** block, then a **De-multiplexing Backhaul Link** block. It then splits into two parallel **Reassemble ARQ** blocks. These are followed by **BH RLC Channels** and **BH Logical Channels**. The data then enters a **Scheduling / Priority Handling** block, followed by **Multiplexing Backhaul Link**, and finally a **TX HARQ** block before being sent to the **Backhaul Link towards IAB-donor or parent IAB-node**. +- Backhaul Link from child IAB-node (middle):** This path is identical to the left path, showing another instance of the same processing chain. +- Access Link from Local UE (right):** Data flows from the Local UE through a **RX HARQ** block, then a **De-multiplexing Access Link UE** block. It then splits into two parallel **Reassemble ARQ** blocks. These are followed by **Access RLC Channels** and **Upper layer processing** blocks. The data then enters the same **Scheduling / Priority Handling** block as the backhaul data. + +Horizontal dashed lines represent the interfaces between protocol layers: **Transport Channels** (top and bottom), **MAC RX** and **MAC TX** (top and bottom), **RLC RX** and **RLC TX** (middle), **BAP RX** and **BAP TX** (middle), and **BH RLC Channels** (middle). + +Figure 6.1-5: UL L2-structure at IAB-node. This diagram illustrates the Layer 2 protocol stack for an IAB-node, showing data flow from child IAB-nodes and local UEs through various processing blocks like HARQ, RLC, and MAC. + +Figure 6.1-5: UL L2-structure at IAB-node + +## 6.2 MAC Sublayer + +### 6.2.1 Services and Functions + +The main services and functions of the MAC sublayer include: + +- Mapping between logical channels and transport channels; +- Multiplexing/demultiplexing of MAC SDUs belonging to one or different logical channels into/from transport blocks (TB) delivered to/from the physical layer on transport channels; +- Scheduling information reporting; +- Error correction through HARQ (one HARQ entity per cell in case of CA); +- Priority handling between UEs by means of dynamic scheduling; +- Priority handling between logical channels of one UE by means of logical channel prioritisation; +- Priority handling between overlapping resources of one UE; +- Padding. + +A single MAC entity can support multiple numerologies, transmission timings and cells. Mapping restrictions in logical channel prioritisation control which numerology(ies), cell(s), and transmission timing(s) a logical channel can use (see clause 16.1.2). + +## 6.2.2 Logical Channels + +Different kinds of data transfer services as offered by MAC. Each logical channel type is defined by what type of information is transferred. Logical channels are classified into two groups: Control Channels and Traffic Channels. Control channels are used for the transfer of control plane information only: + +- Broadcast Control Channel (BCCH): a downlink channel for broadcasting system control information. +- Paging Control Channel (PCCH): a downlink channel that carries paging messages. +- Common Control Channel (CCCH): channel for transmitting control information between UEs and network. This channel is used for UEs having no RRC connection with the network. +- Dedicated Control Channel (DCCH): a point-to-point bi-directional channel that transmits dedicated control information between a UE and the network. Used by UEs having an RRC connection. + +Traffic channels are used for the transfer of user plane information only: + +- Dedicated Traffic Channel (DTCH): point-to-point channel, dedicated to one UE, for the transfer of user information. A DTCH can exist in both uplink and downlink. + +## 6.2.3 Mapping to Transport Channels + +In Downlink, the following connections between logical channels and transport channels exist: + +- BCCH can be mapped to BCH; +- BCCH can be mapped to DL-SCH; +- PCCH can be mapped to PCH; +- CCCH can be mapped to DL-SCH; +- DCCH can be mapped to DL-SCH; +- DTCH can be mapped to DL-SCH. + +In Uplink, the following connections between logical channels and transport channels exist: + +- CCCH can be mapped to UL-SCH; +- DCCH can be mapped to UL- SCH; +- DTCH can be mapped to UL-SCH. + +## 6.2.4 HARQ + +The HARQ functionality ensures delivery between peer entities at Layer 1. A single HARQ process supports one TB when the physical layer is not configured for downlink/uplink spatial multiplexing, and when the physical layer is configured for downlink/uplink spatial multiplexing, a single HARQ process supports one or multiple TBs. + +# 6.3 RLC Sublayer + +## 6.3.1 Transmission Modes + +The RLC sublayer supports three transmission modes: + +- Transparent Mode (TM); +- Unacknowledged Mode (UM); +- Acknowledged Mode (AM). + +The RLC configuration is per logical channel with no dependency on numerologies and/or transmission durations, and ARQ can operate on any of the numerologies and/or transmission durations the logical channel is configured with. + +For SRB0, paging and broadcast system information, TM mode is used. For other SRBs AM mode used. For DRBs, either UM or AM mode are used. + +## 6.3.2 Services and Functions + +The main services and functions of the RLC sublayer depend on the transmission mode and include: + +- Transfer of upper layer PDUs; +- Sequence numbering independent of the one in PDCP (UM and AM); +- Error Correction through ARQ (AM only); +- Segmentation (AM and UM) and re-segmentation (AM only) of RLC SDUs; +- Reassembly of SDU (AM and UM); +- Duplicate Detection (AM only); +- RLC SDU discard (AM and UM); +- RLC re-establishment; +- Protocol error detection (AM only). + +## 6.3.3 ARQ + +The ARQ within the RLC sublayer has the following characteristics: + +- ARQ retransmits RLC SDUs or RLC SDU segments based on RLC status reports; +- Polling for RLC status report is used when needed by RLC; +- RLC receiver can also trigger RLC status report after detecting a missing RLC SDU or RLC SDU segment. + +# 6.4 PDCP Sublayer + +## 6.4.1 Services and Functions + +The main services and functions of the PDCP sublayer include: + +- Transfer of data (user plane or control plane); +- Maintenance of PDCP SNs; +- Header compression and decompression using the ROHC protocol; +- Header compression and decompression using EHC protocol; +- Compression and decompression of uplink PDCP SDUs: DEFLATE based UDC only; +- Ciphering and deciphering; +- Integrity protection and integrity verification; +- Timer based SDU discard; +- For split bearers, routing; +- Duplication; + +- Reordering and in-order delivery; +- Out-of-order delivery; +- Duplicate discarding. + +Since PDCP does not allow COUNT to wrap around in DL and UL, it is up to the network to prevent it from happening (e.g. by using a release and add of the corresponding radio bearer or a full configuration). + +## 6.5 SDAP Sublayer + +The main services and functions of SDAP include: + +- Mapping between a QoS flow and a data radio bearer; +- Marking QoS flow ID (QFI) in both DL and UL packets. + +A single protocol entity of SDAP is configured for each individual PDU session. + +## 6.6 L2 Data Flow + +An example of the Layer 2 Data Flow is depicted on Figure 6.6-1, where a transport block is generated by MAC by concatenating two RLC PDUs from $RB_x$ and one RLC PDU from $RB_y$ . The two RLC PDUs from $RB_x$ each corresponds to one IP packet ( $n$ and $n+1$ ) while the RLC PDU from $RB_y$ is a segment of an IP packet ( $m$ ). + +NOTE: H depicts the headers and subheaders. + +![Figure 6.6-1: Data Flow Example. The diagram shows a large black rectangle representing a transport block. Inside this rectangle, at the top left, there is a small white rectangle representing a header or subheader. The rest of the rectangle is empty, representing the data payload.](ccf6853c7291703cb04568057fef5849_img.jpg) + +Figure 6.6-1: Data Flow Example. The diagram shows a large black rectangle representing a transport block. Inside this rectangle, at the top left, there is a small white rectangle representing a header or subheader. The rest of the rectangle is empty, representing the data payload. + +Figure 6.6-1: Data Flow Example + +## 6.7 Carrier Aggregation + +In case of CA, the multi-carrier nature of the physical layer is only exposed to the MAC layer for which one HARQ entity is required per serving cell as depicted on Figures 6.7-1 and 6.7-2 below: + +- In both uplink and downlink, there is one independent hybrid-ARQ entity per serving cell and one transport block is generated per assignment/grant per serving cell in the absence of spatial multiplexing. Each transport block and its potential HARQ retransmissions are mapped to a single serving cell. + +![Diagram showing Layer 2 structure for DL with CA configured. It features a large black rectangle containing three white shapes: a small rectangle at the top, a long horizontal bar in the middle, and a trapezoid at the bottom right. Below the rectangle, a vertical line descends from a small white rectangle to a horizontal dashed line.](b34c69e1ec326b01c3a485b27b1df5f6_img.jpg) + +The diagram illustrates the Layer 2 structure for Downlink (DL) with Carrier Aggregation (CA) configured. It consists of a large black rectangular area representing the protocol stack. Inside this area, there are three white geometric shapes: a small rectangle near the top, a long horizontal bar across the middle, and a trapezoid in the bottom right corner. Below the black rectangle, a vertical line descends from a small white rectangle to a horizontal dashed line. + +Diagram showing Layer 2 structure for DL with CA configured. It features a large black rectangle containing three white shapes: a small rectangle at the top, a long horizontal bar in the middle, and a trapezoid at the bottom right. Below the rectangle, a vertical line descends from a small white rectangle to a horizontal dashed line. + +Figure 6.7-1: Layer 2 Structure for DL with CA configured + +![Diagram illustrating the Layer 2 Structure for UL with CA configured. It shows a stack of three layers: a top layer (PDCP), a middle layer (RLC), and a bottom layer (MAC). The MAC layer is connected to two vertical lines representing the radio interface, which are bounded by horizontal dashed lines above and below.](65e8c0628536d6d4245e9ab46ba070c3_img.jpg) + +The diagram shows a vertical stack of three rectangular blocks representing Layer 2 protocols. From top to bottom, they are PDCP, RLC, and MAC. Two vertical lines pass through the center of each block, representing the data flow. These lines are terminated by horizontal dashed lines above and below the stack, representing the radio interface boundaries. + +Diagram illustrating the Layer 2 Structure for UL with CA configured. It shows a stack of three layers: a top layer (PDCP), a middle layer (RLC), and a bottom layer (MAC). The MAC layer is connected to two vertical lines representing the radio interface, which are bounded by horizontal dashed lines above and below. + +Figure 6.7-2: Layer 2 Structure for UL with CA configured + +## 6.8 Dual Connectivity + +When the UE is configured with SCG, the UE is configured with two MAC entities: one MAC entity for the MCG and one MAC entity for the SCG. Further details of DC operation can be found in TS 37.340 [21]. + +## 6.9 Supplementary Uplink + +In case of Supplementary Uplink (SUL, see TS 38.101-1 [18]), the UE is configured with 2 ULs for one DL of the same cell, and uplink transmissions on those two ULs are controlled by the network to avoid overlapping PUSCH/PUCCH transmissions in time. Overlapping transmissions on PUSCH are avoided through scheduling while overlapping transmissions on PUCCH are avoided through configuration (PUCCH can only be configured for only one of the 2 ULs of the cell). In addition, initial access is supported in each of the uplink (see clause 9.2.6). An example of SUL is given in Annex B. + +## 6.10 Bandwidth Adaptation + +With Bandwidth Adaptation (BA), the receive and transmit bandwidth of a UE need not be as large as the bandwidth of the cell and can be adjusted: the width can be ordered to change (e.g. to shrink during period of low activity to save power); the location can move in the frequency domain (e.g. to increase scheduling flexibility); and the subcarrier spacing can be ordered to change (e.g. to allow different services). A subset of the total cell bandwidth of a cell is referred to as a Bandwidth Part (BWP) and BA is achieved by configuring the UE with BWP(s) and telling the UE which of the configured BWPs is currently the active one. + +Figure 6.10-1 below describes a scenario where 3 different BWPs are configured: + +- BWP1 with a width of 40 MHz and subcarrier spacing of 15 kHz; + +- BWP2 with a width of 10 MHz and subcarrier spacing of 15 kHz; +- BWP3 with a width of 20 MHz and subcarrier spacing of 60 kHz. + +![Figure 6.10-1: BA Example. A graph showing frequency on the y-axis and time on the x-axis. The graph illustrates the activation of different Bandwidth Parts (BWPs) over time. BWP1 (40MHz/15kHz) is active at the beginning and end. BWP2 (10MHz/15kHz) is active in the middle. BWP3 (20MHz/60kHz) is active in the middle, above BWP2. The activation periods are indicated by vertical dashed lines.](fcdcb5991d671cadf547dd3fbfe13486_img.jpg) + +The figure shows a plot of frequency versus time. The y-axis is labeled 'frequency' and the x-axis is labeled 'time'. The plot shows three distinct bandwidth parts (BWPs) being activated over time. BWP1 (40MHz/15kHz) is shown as a yellow rectangle at the start and end of the timeline. BWP2 (10MHz/15kHz) is shown as a green rectangle in the middle. BWP3 (20MHz/60kHz) is shown as a blue rectangle in the middle, above BWP2. Vertical dashed lines indicate the boundaries between these activation periods. An ellipsis (...) is shown at the end of the timeline. + +Figure 6.10-1: BA Example. A graph showing frequency on the y-axis and time on the x-axis. The graph illustrates the activation of different Bandwidth Parts (BWPs) over time. BWP1 (40MHz/15kHz) is active at the beginning and end. BWP2 (10MHz/15kHz) is active in the middle. BWP3 (20MHz/60kHz) is active in the middle, above BWP2. The activation periods are indicated by vertical dashed lines. + +Figure 6.10-1: BA Example + +## 6.11 Backhaul Adaptation Protocol Sublayer + +### 6.11.1 Services and Functions + +The main service and functions of the BAP sublayer include: + +- Transfer of data; +- Routing of packets to next hop; +- Determination of BAP destination and BAP path for packets from upper layers; +- Determination of egress BH RLC channels for packets routed to next hop; +- Differentiating traffic to be delivered to upper layers from traffic to be delivered to egress link; +- Flow control feedback and polling signalling; +- BH RLF detection indication, BH RLF recovery indication, and BH RLF indication; +- BAP header rewriting. + +### 6.11.2 Traffic Mapping from Upper Layers to Layer-2 + +In upstream direction, the IAB-donor-CU configures the IAB-node with mappings between upstream F1 and non-F1 traffic originated at the IAB-node, and the appropriate BAP routing ID, next-hop BAP address and BH RLC channel. A specific mapping is configured: + +- for each F1-U GTP-U tunnel; +- for non-UE associated F1AP messages; +- for UE-associated F1AP messages; +- for non-F1 traffic. + +Multiple mappings can contain the same BH RLC channel and/or next-hop BAP address and/or BAP routing ID. In case the IAB-MT is NR-dual-connected (SA mode only), the mapping may include two separate BH RLC channels, where the two BH RLC channels are established toward different parent nodes. + +In case the IAB-node is configured with multiple IP addresses for F1-C on the NR leg, multiple mappings can be configured for non-UE-associated F1AP messages or UE-associated F1AP messages. The appropriate mapping is selected based on the IAB-node's implementation. + +These traffic mapping configurations are performed via F1AP. For a boundary IAB-node, the traffic mapping configuration includes information that allows the boundary IAB-node to determine the IAB topology the mapping applies to. + +During IAB-node integration, a default BH RLC channel and a default BAP routing ID may be configured via RRC, which can be used for non-F1-U traffic. These default configurations may be updated during topology adaptation scenarios as discussed in TS 38.401 [4]. + +In downstream direction, traffic mapping occurs internal to the IAB-donor. Transport for IAB-donors that use split-gNB architecture is handled in TS 38.401 [4]. + +### 6.11.3 Routing, BAP Header Rewriting and BH-RLC-channel Mapping on BAP sublayer + +![Diagram illustrating routing and BH RLC channel selection on the BAP sublayer. It shows a central IAB-node connected to an IAB-donor (top) and two child IAB-nodes (bottom left and bottom right). Arrows indicate traffic flow from the donor through the central node to the child nodes. Labels include 'IAB-donor', 'IAB-node', 'BH RLC channel', and 'BAP routing ID'.](ae0dd5533e0b7fd2db452b5e2fdf8e5b_img.jpg) + +The diagram shows a central IAB-node (middle circle) connected to an IAB-donor (top circle) and two child IAB-nodes (bottom left and bottom right circles). Each connection is represented by a vertical stack of three rectangles: a blue rectangle at the top, an orange rectangle in the middle, and a blue rectangle at the bottom. Arrows indicate traffic flow: from the IAB-donor, through the central IAB-node, and then branching out to the two child IAB-nodes. Labels with leader lines point to these components: 'IAB-donor' points to the top circle, 'IAB-node' points to the central circle, 'BH RLC channel' points to the orange rectangles, and 'BAP routing ID' points to the blue rectangles. + +Diagram illustrating routing and BH RLC channel selection on the BAP sublayer. It shows a central IAB-node connected to an IAB-donor (top) and two child IAB-nodes (bottom left and bottom right). Arrows indicate traffic flow from the donor through the central node to the child nodes. Labels include 'IAB-donor', 'IAB-node', 'BH RLC channel', and 'BAP routing ID'. + +**Figure 6.11.3-1: Routing and BH RLC channel selection on BAP sublayer** + +Routing on BAP sublayer uses the BAP routing ID, which is configured by the IAB-donor-CU. The BAP routing ID consists of BAP address and BAP path ID. The BAP address is used for the following purposes: + +1. Determination if a packet has reached the destination node, i.e. IAB-node or IAB-donor-DU, on BAP sublayer. This is the case if the BAP address in the packet's BAP header matches the BAP address configured via RRC on the IAB-node, or via F1AP on the IAB-donor-DU. For a dual-connected boundary IAB-node that is configured with two BAP addresses, the BAP address in the packet's BAP header is matched with the BAP address configured by the CU of the IAB topology, where the packet has been received. +2. Determination of the next-hop node for packets that have not reached their destination. This applies to packets arriving from a prior hop on BAP sublayer or that have been received from IP layer. + +For packets arriving from a prior hop or from upper layers, the determination of the next-hop node is based on a routing configuration provided by the IAB-donor-CU via F1AP signalling or a default configuration provided by the IAB-donor-CU via RRC signalling. This F1AP configuration contains the mapping between the BAP routing ID carried in the packet's BAP header and the next-hop node's BAP address. + +**Table 6.11.3-1: Routing configuration** + +| BAP routing ID | Next-hop BAP address | +|--------------------------------------|----------------------------------| +| Derived from BAP packet's BAP header | Egress BH link to forward packet | + +The IAB-node resolves the next-hop BAP address to a physical backhaul link. For this purpose, the IAB-donor-CU provides the IAB-node/IAB-donor-DU with its child-node's BAP address via F1AP, and it provides the IAB-node with its parent-node's BAP address via RRC. For a boundary IAB-node, the routing configuration also indicates the IAB topology it applies to. The BH link to the next-hop node and the next-hop BAP address belong to the IAB topology of the CU that provided the RRC configuration of the BH link to that next-hop node. + +The IAB-node can receive multiple routing configurations with the same destination BAP address but different BAP path IDs. These routing configurations may resolve to the same or different egress BH links. + +In case the BH link resolved from the routing entry is considered *unavailable* for this packet, the IAB-node may perform local rerouting as defined in TS 38.340 [31], i.e., select another BH link by considering only the packet's BAP address or, in some cases, by header rewriting. In this manner, the packet can be delivered via an alternative path as defined in TS 38.340 [31]. + +A BH link may be considered *unavailable* in case the BH link has RLF. A parent link may be considered *unavailable* after a BH RLF detection indication has been received on this parent link and before a subsequent BH RLF recovery indication has been received on the same parent link. For DL traffic, a BH link may be considered *unavailable* for BAP PDUs carrying a certain BAP routing ID due to congestion derived from flow-control feedback information related to this BAP routing ID, as defined in TS 38.340 [31]. + +For a boundary IAB-node, the routing configuration may carry information on the IAB topology the configuration applies to. + +The IAB-node may rewrite the BAP routing ID in the packet's BAP header under the following circumstances: + +- A packet is routed between two IAB topologies via a boundary IAB-node as defined in TS 38.401[31]. In this case, the BAP routing ID carried by the received BAP PDU is allocated by the IAB-donor-CU of the ingress IAB topology, while the BAP routing ID carried by the BAP PDU after header rewriting is allocated by the IAB-donor-CU of the egress IAB topology. +- An upstream packet is locally re-routed to a different IAB-donor-DU than indicated by the BAP address in the BAP header of the received packet. The rewritten BAP header carries the BAP address of the alternative IAB-donor-DU and the BAP path ID for a path to this alternative IAB-donor-DU. BAP header rewriting for upstream inter-IAB-donor-DU local rerouting is only applied if neither routing nor local re-routing without header rewriting resolve to an available egress BH link. + +For packets that are routed between two IAB topologies via a boundary node, the BAP header rewriting configuration is provided via F1AP, and it includes the ingress BAP routing ID, the egress BAP routing ID, and it indicates the egress IAB topology: + +**Table 6.11.3-2a: BAP header rewriting configuration** + +| Ingress BAP routing ID | Egress BAP routing ID | Egress topology indicator | +|------------------------------------------------------------------|---------------------------------------------------------------------|------------------------------------| +| BAP routing ID carried in the BAP header of the received BAP PDU | BAP routing ID carried in the BAP header of the transmitted BAP PDU | Indicates the egress IAB topology. | + +For upstream packets that are locally re-routed to a different IAB-donor-DU, the BAP header is rewritten with a BAP routing ID contained in the routing entry that was selected for re-routing. + +Details of BAP header rewriting are defined in TS 38.340 [31]. + +When routing a packet from an ingress to an egress BH link, the IAB-node derives the egress BH RLC channel on the egress BH link through an F1AP-configured mapping from the BH RLC channel used on the ingress BH link. The BH RLC channel IDs used for ingress and egress BH RLC channels are generated by the IAB-donor-CU. Since the BH RLC channel ID only has link-local scope, the mapping configurations also include the BAP addresses of prior and next hop: + +**Table 6.11.3-2: BH RLC channel mapping configuration** + +| Next-hop BAP address | Prior-hop BAP address | Ingress RLC channel ID | Egress RLC channel ID | +|------------------------------------|---------------------------------------|----------------------------------------------|----------------------------------------------------| +| Derived from routing configuration | Derived from packet's ingress BH link | Derived from packet's ingress BH RLC channel | BH RLC channel on egress BH link to forward packet | + +For a boundary IAB-node, the BH RLC channel mapping configuration may also include indicators for the IAB topology of the ingress and of the egress BH link. + +The IAB-node resolves the BH RLC channel IDs from logical channel IDs based on the configuration by the IAB-donor-CU. The IAB-MT obtains the BH RLC channel ID in the RRC configuration of the corresponding logical channel. The IAB-DU obtains the BH RLC channel ID in the F1AP configuration of the BH RLC channel. + +## 6.12 Multiple Transmit/Receive Point Operation + +In Multiple Transmit/Receive Point (multi-TRP) operation, a serving cell can schedule the UE from two TRPs, providing better coverage, reliability and/or data rates for PDSCH, PDCCH, PUSCH, and PUCCH. + +There are two different operation modes to schedule multi-TRP PDSCH transmissions: single-DCI and multi-DCI. For both modes, control of uplink and downlink operation can be done by physical layer and MAC layer, within the configuration provided by the RRC layer. In single-DCI mode, the UE is scheduled by the same DCI for both TRPs and in multi-DCI mode, the UE is scheduled by independent DCIs from each TRP. + +There are two different operation modes for multi-TRP PDCCH: PDCCH repetition as in Clause 5.2.3 and Single Frequency Network (SFN) based PDCCH transmission. In both modes, the UE can receive two PDCCH transmissions, one from each TRP, carrying the same DCI. In PDCCH repetition mode, the UE can receive the two PDCCH transmissions carrying the same DCI from two linked search spaces each associated with a different CORESET. In SFN based PDCCH transmission mode, the UE can receive the two PDCCH transmissions carrying the same DCI from a single search space/CORESET using different TCI states. + +For multi-TRP PUSCH repetition, according to indications in a single DCI or in a semi-static configured grant provided over RRC, the UE performs PUSCH transmission of the same contents toward two TRPs with corresponding beam directions associated with different spatial relations. For multi-TRP PUCCH repetition, the UE performs PUCCH transmission of the same contents toward two TRPs with corresponding beam directions associated with different spatial relations. + +For inter-cell multi-TRP operation, for multi-DCI PDSCH transmission, one or more TCI states can be associated with SSB with a PCI different from the serving cell PCI. The activated TCI states can be associated with at most one PCI different from the serving cell PCI at a time. + +For inter-cell and intra-cell multi-DCI multi-TRP operation, up to two TAGs with associated TAG IDs can be configured per serving cell. Each UL/Joint TCI state is associated with a TAG ID and the UE applies the timing advance of the TAG ID associated with the UL/joint TCI state utilized for UL transmission. + +For single-DCI multi-TRP Simultaneous Transmission with Multi-Panel (STxMP) Spatial Domain Multiplexing (SDM) PUSCH transmission, different layers of one PUSCH are separately transmitted towards two TRPs. For single-DCI multi-TRP STxMP SFN PUSCH transmission, same layers of one PUSCH are transmitted towards two TRPs. For multi-DCI based multi-TRP STxMP PUSCH+PUSCH transmission, two PUSCHs are transmitted towards two TRPs. For single-DCI multi-TRP STxMP SFN PUCCH transmission, one PUCCH is transmitted towards two TRPs. + +--- + +## 7 RRC + +### 7.1 Services and Functions + +The main services and functions of the RRC sublayer over the Uu interface include: + +- Broadcast of System Information related to AS and NAS; + +- Paging initiated by 5GC or NG-RAN; +- Establishment, maintenance and release of an RRC connection between the UE and NG-RAN including: + - Addition, modification and release of carrier aggregation; + - Addition, modification and release of Dual Connectivity in NR or between E-UTRA and NR. +- Security functions including key management; +- Establishment, configuration, maintenance and release of Signalling Radio Bearers (SRBs) and Data Radio Bearers (DRBs); +- Mobility functions including: + - Handover and context transfer; + - UE cell selection and reselection and control of cell selection and reselection; + - Inter-RAT mobility. +- QoS management functions; +- UE measurement reporting and control of the reporting; +- Detection of and recovery from radio link failure; +- NAS message transfer to/from NAS from/to UE. + +The sidelink specific services and functions of the RRC sublayer over the Uu interface include: + +- Configuration of sidelink resource allocation via system information or dedicated signalling; +- Reporting of UE sidelink information; +- Measurement configuration and reporting related to sidelink; +- Reporting of UE assistance information for SL traffic pattern(s). + +## 7.2 Protocol States + +RRC supports the following states which can be characterised as follows: + +- **RRC\_IDLE:** + - PLMN selection; + - Broadcast of system information; + - Cell re-selection mobility; + - Paging for mobile terminated data is initiated by 5GC; + - Transfer of MBS broadcast data to the UE over MRB(s); + - DRX for CN paging configured by NAS. +- **RRC\_INACTIVE:** + - PLMN selection; + - Broadcast of system information; + - Cell re-selection mobility; + - Paging is initiated by NG-RAN (RAN paging); + +- RAN-based notification area (RNA) is managed by NG- RAN; +- DRX for RAN paging configured by NG-RAN; +- 5GC - NG-RAN connection (both C/U-planes) is established for UE; +- The UE Inactive AS context is stored in NG-RAN and the UE; +- NG-RAN knows the RNA which the UE belongs to; +- Transfer of MBS broadcast data to the UE over MRB(s); +- Transfer of unicast data and/or signalling to/from the UE over radio bearers configured for SDT. +- **RRC\_CONNECTED:** + - 5GC - NG-RAN connection (both C/U-planes) is established for UE; + - The UE AS context is stored in NG-RAN and the UE; + - NG-RAN knows the cell which the UE belongs to; + - Transfer of unicast data to/from the UE; + - Transfer of MBS multicast/broadcast data to the UE over MRB(s); + - Network controlled mobility including measurements. + +## 7.3 System Information Handling + +### 7.3.1 Overview + +System Information (SI) consists of a MIB and a number of SIBs, which are divided into Minimum SI and Other SI: + +- **Minimum SI** comprises basic information required for initial access and information for acquiring any other SI. Minimum SI consists of: + - *MIB* contains cell barred status information and essential physical layer information of the cell required to receive further system information, e.g. CORESET#0 configuration. *MIB* is periodically broadcast on BCH. + - *SIB1* defines the scheduling of other system information blocks and contains information required for initial access. *SIB1* is also referred to as Remaining Minimum SI (RMSI) and is periodically broadcast on DL-SCH or sent in a dedicated manner on DL-SCH to UEs in RRC\_CONNECTED. +- **Other SI** encompasses all SIBs not broadcast in the Minimum SI. Those SIBs can either be periodically broadcast on DL-SCH, broadcast on-demand on DL-SCH (i.e. upon request from UEs in RRC\_IDLE, RRC\_INACTIVE, or RRC\_CONNECTED), or sent in a dedicated manner on DL-SCH to UEs in RRC\_CONNECTED (i.e., upon request, if configured by the network, from UEs in RRC\_CONNECTED or when the UE has an active BWP with no common search space configured or when the UE configured with inter cell beam management is receiving DL-SCH from a TRP with PCI different from serving cell's PCI). Other SI consists of: + - *SIB2* contains cell re-selection information, mainly related to the serving cell; + - *SIB3* contains information about the serving frequency and intra-frequency neighbouring cells relevant for cell re-selection (including cell re-selection parameters common for a frequency as well as cell specific re-selection parameters); + - *SIB4* contains information about other NR frequencies and inter-frequency neighbouring cells relevant for cell re-selection (including cell re-selection parameters common for a frequency as well as cell specific re-selection parameters), which can also be used for NR idle/inactive measurements; + +- *SIB5* contains information about E-UTRA frequencies and E-UTRA neighbouring cells relevant for cell re-selection (including cell re-selection parameters common for a frequency as well as cell specific re-selection parameters); +- *SIB6* contains an ETWS primary notification; +- *SIB7* contains an ETWS secondary notification; +- *SIB8* contains a CMAS warning notification; +- *SIB9* contains information related to GPS time and Coordinated Universal Time (UTC); +- *SIB10* contains the Human-Readable Network Names (HRNN) of the NPNs listed in *SIB1*; +- *SIB11* contains information related to idle/inactive measurements; +- *SIB15* contains information related to disaster roaming; +- *SIB16* contains slice-based cell reselection information; +- *SIB17* contains information related to TRS configuration for UEs in RRC\_IDLE/RRC\_INACTIVE; +- *SIBpos* contains positioning assistance data as defined in TS 37.355 [43] and TS 38.331 [12]; +- *SIB18* contains information related to the Group IDs for Network selection (GINs) associated with SNPNs listed in *SIB1*. +- *SIB19* in TN contains NTN-specific parameters for NTN neighbour cells as defined in TS 38.331 [12]. + +For sidelink, Other SI also includes: + +- *SIB12* contains information related to NR sidelink communication; +- *SIB13* contains information related to *SystemInformationBlockType21* for V2X sidelink communication as specified in TS 36.331 clause 5.2.2.28 [29]; +- *SIB14* contains information related to *SystemInformationBlockType26* for V2X sidelink communication as specified in TS 36.331 clause 5.2.2.33 [29]; +- *SIB23* contains information related to ranging and sidelink positioning. + +For non-terrestrial network, Other SI also includes: + +- *SIB19* contains NTN-specific parameters for serving cell and optionally NTN-specific parameters for neighbour cells as defined in TS 38.331 [12]. +- *SIB25* contains TN coverage area information as defined in TS 38.331 [12]. + +For MBS broadcast, Other SI also includes: + +- *SIB20* contains MCCH configuration; +- *SIB21* contains information related to service continuity for MBS broadcast reception. + +For ATG network, Other SI also includes: + +- *SIB22* contains ATG-specific parameters for serving cell and optionally ATG-specific parameters for neighbour cells as defined in TS 38.331 [12]. + +Figure 7.3.1-1 below summarises System Information provisioning. + +![Sequence diagram showing System Information Provisioning between a UE and a gNB. The diagram illustrates the transmission of various System Information (SI) messages. The UE sends a request for 'Minimum SI (SIB1)' to the gNB. The gNB responds with 'Minimum SI (MIB)' periodically broadcast on BCH, and 'Minimum SI (SIB1)' periodically broadcast on DL-SCH. Subsequently, the UE requests 'Other SI (SIBn)' messages. The gNB provides these 'Other SI (SIBn)' messages either periodically broadcast on DL-SCH, broadcast on-demand on DL-SCH, or unicast on-demand on DL-SCH, as indicated by the dashed lines in the diagram.](e2c120be98ede6deb60dd341f5a9803b_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB + Note right of UE: Request Minimum SI (SIB1) + gNB->>UE: Minimum SI (MIB) +periodically broadcast on BCH + gNB->>UE: Minimum SI (SIB1) +periodically broadcast on DL-SCH + Note right of UE: Request Other SI (SIBn) + gNB-->>UE: Other SI (SIBn) +periodically broadcast on DL-SCH + gNB-->>UE: Other SI (SIBn) +broadcast on-demand on DL-SCH + gNB-->>UE: Other SI (SIBn) +unicast on DL-SCH + gNB-->>UE: Other SI (SIBn) +unicast on-demand on DL-SCH + +``` + +Sequence diagram showing System Information Provisioning between a UE and a gNB. The diagram illustrates the transmission of various System Information (SI) messages. The UE sends a request for 'Minimum SI (SIB1)' to the gNB. The gNB responds with 'Minimum SI (MIB)' periodically broadcast on BCH, and 'Minimum SI (SIB1)' periodically broadcast on DL-SCH. Subsequently, the UE requests 'Other SI (SIBn)' messages. The gNB provides these 'Other SI (SIBn)' messages either periodically broadcast on DL-SCH, broadcast on-demand on DL-SCH, or unicast on-demand on DL-SCH, as indicated by the dashed lines in the diagram. + +**Figure 7.3.1-1: System Information Provisioning** + +For a cell/frequency that is considered for camping by the UE, the UE is not required to acquire the contents of the minimum SI of that cell/frequency from another cell/frequency layer. This does not preclude the case that the UE applies stored SI from previously visited cell(s). + +If the UE cannot determine the full contents of the minimum SI of a cell by receiving from that cell, the UE shall consider that cell as barred. + +In case of BA, the UE only acquires SI on the active BWP. + +If the UE is configured with inter cell beam management: + +- the UE is not required to acquire the SI from the serving cell while it is receiving DL-SCH from a TRP with PCI different from serving cell's PCI. + +## 7.3.2 Scheduling + +The MIB is mapped on the BCCH and carried on BCH while all other SI messages are mapped on the BCCH, where they are dynamically carried on DL-SCH. The scheduling of SI messages part of Other SI is indicated by *SIB1*. + +For UEs in RRC\_IDLE and RRC\_INACTIVE while SDT procedure is not ongoing (see clause 18), a request for Other SI triggers a random access procedure (see clause 9.2.6) where MSG3 includes the SI request message unless the requested SI is associated to a subset of the PRACH resources, in which case MSG1 is used for indication of the requested Other SI. When MSG1 is used, the minimum granularity of the request is one SI message (i.e. a set of SIBs), one RACH preamble and/or PRACH resource can be used to request multiple SI messages and the gNB acknowledges the request in MSG2. When MSG 3 is used, the gNB acknowledges the request in MSG4. + +For UEs in RRC\_CONNECTED, a request for Other SI may be sent to the network, if configured by the network, in a dedicated manner (i.e., via UL-DCCH) and the granularity of the request is one SIB. The gNB may respond with an *RRCReconfiguration* including the requested SIB(s). It is a network choice to decide which requested SIBs are delivered in a dedicated or broadcasted manner. + +The Other SI may be broadcast at a configurable periodicity and for a certain duration. The Other SI may also be broadcast when it is requested by UE in RRC\_IDLE/RRC\_INACTIVE/RRC\_CONNECTED. + +For a UE to be allowed to camp on a cell it must have acquired the contents of the Minimum SI from that cell. There may be cells in the system that do not broadcast the Minimum SI and where the UE therefore cannot camp. + +## 7.3.3 SI Modification + +Change of system information (other than for ETWS/CMAS, see clause 16.4) only occurs at specific radio frames, i.e. the concept of a modification period is used. System information may be transmitted a number of times with the same content within a modification period, as defined by its scheduling. The modification period is configured by system information. + +When the network changes (some of the) system information, it first notifies the UEs about this change, i.e. this may be done throughout a modification period. In the next modification period, the network transmits the updated system information. Upon receiving a change notification, the UE acquires the new system information from the start of the next modification period. The UE applies the previously acquired system information until the UE acquires the new system information. + +## 7.4 Access Control + +NG-RAN supports overload and access control functionality such as RACH back off, RRC Connection Reject, RRC Connection Release and UE based access barring mechanisms. + +One unified access control framework as specified in TS 22.261 [19] applies to all UE states (RRC\_IDLE, RRC\_INACTIVE and RRC\_CONNECTED) for NR. NG-RAN broadcasts barring control information associated with Access Categories and Access Identities (in case of network sharing, the barring control information can be set individually for each PLMN). The UE determines whether an access attempt is authorized based on the barring information broadcast for the selected PLMN, and the selected Access Category and Access Identity(ies) for the access attempt: + +- For NAS triggered requests, NAS determines the Access Category and Access Identity(ies); +- For AS triggered requests, RRC determines the Access Category while NAS determines the Access Identity(ies). + +The gNB handles access attempts with establishment causes "emergency", "mps-PriorityAccess" and "mcs-PriorityAccess" (i.e. Emergency calls, MPS, MCS subscribers) with high priority and responds with RRC Reject to these access attempts only in extreme network load conditions that may threaten the gNB stability. + +Unified access control does not apply to IAB-MTs or NCR-MTs. + +## 7.5 UE Capability Retrieval framework + +The UE reports its UE radio access capabilities which are static at least when the network requests. The gNB can request what capabilities for the UE to report based on band information. The UE capability can be represented by a capability ID, which may be exchanged in NAS signalling over the air and in network signalling instead of the UE capability structure. + +In IAB, it is optional for an IAB-MT to support UE capability Retrieval framework and the related signalling. In case IAB-MT does not support UE capability Retrieval framework, IAB-MT capabilities are assumed to be known to the network by other means, e.g. OAM. + +## 7.6 Transport of NAS Messages + +NR provides reliable in-sequence delivery of NAS messages over SRBs in RRC, except at handover where losses or duplication can occur when PDCP is re-established. In RRC, NAS messages are sent in transparent containers. Piggybacking of NAS messages can occur in the following scenarios: + +- At bearer establishment/modification/release in the DL; +- For transferring the initial NAS message during connection setup and connection resume in the UL. + +NOTE: In addition to the integrity protection and ciphering performed by NAS, NAS messages can also be integrity protected and ciphered by PDCP. + +Multiple NAS messages can be sent in a single downlink RRC message during PDU Session Resource establishment or modification. In this case, the order of the NAS messages contained in the RRC message shall be in the same order as that in the corresponding NG-AP message in order to ensure the in-sequence delivery of NAS messages. + +NG-RAN node may trigger the NAS Non Delivery Indication procedure to report the non-delivery of the non PDU Session related NAS PDU received from the AMF as specified in TS 38.413 [26]. + +## 7.7 Carrier Aggregation + +When CA is configured, the UE only has one RRC connection with the network. At RRC connection establishment/re-establishment/handover, one serving cell provides the NAS mobility information, and at RRC connection re-establishment/handover, one serving cell provides the security input. This cell is referred to as the Primary Cell (PCell). Depending on UE capabilities, Secondary Cells (SCells) can be configured to form together with the PCell a set of serving cells. The configured set of serving cells for a UE therefore always consists of one PCell and one or more SCells. + +The reconfiguration, addition and removal of SCells can be performed by RRC. At intra-NR handover and during connection resume from RRC\_INACTIVE, the network can also add, remove, keep, or reconfigure SCells for usage with the target PCell. When adding a new SCell, dedicated RRC signalling is used for sending all required system information of the SCell i.e. while in connected mode, UEs need not acquire broadcast system information directly from the SCells. + +## 7.8 Bandwidth Adaptation + +To enable BA on the PCell, the gNB configures the UE with UL and DL BWP(s). To enable BA on SCells in case of CA, the gNB configures the UE with DL BWP(s) at least (i.e. there may be none in the UL). For the PCell, the BWP used for initial access is configured via system information. For the SCell(s), the BWP used after initial activation is configured via dedicated RRC signalling. + +In paired spectrum, DL and UL can switch BWP independently. In unpaired spectrum, DL and UL switch BWP simultaneously. Switching between configured BWPs happens by means of RRC signalling, DCI, inactivity timer or upon initiation of random access. When an inactivity timer is configured for a serving cell, the expiry of the inactivity timer associated to that cell switches the active BWP to a default BWP configured by the network. There can be at most one active BWP per cell, except when the serving cell is configured with SUL, in which case there can be at most one on each UL carrier. + +## 7.9 UE Assistance Information + +When configured to do so, the UE can signal the network through *UEAssistanceInformation*: + +- If it prefers an adjustment in the connected mode DRX cycle length, for the purpose of delay budget reporting; +- If it is experiencing internal overheating; +- If it prefers certain DRX parameter values, and/or a reduced maximum number of secondary component carriers, and/or a reduced maximum aggregated bandwidth and/or a reduced maximum number of MIMO layers and/or minimum scheduling offsets K0 and K2 for power saving purpose; +- If it expects not to send or receive any more data in the near future, and in this case, it can provide its preference to transition out of RRC\_CONNECTED where this indication may express its preferred RRC state, or alternately, it may cancel an earlier indicated preference to transition out of RRC\_CONNECTED; +- If it prefers (not) to be provisioned with reference time information; +- If it prefers to transition out of RRC\_CONNECTED state for MUSIM operation and its preferred RRC state after transition; +- If it wants to include assistance information for setup or release of gaps for MUSIM operation; +- When affected by IDC problems that it cannot solve by itself: + - The list of frequencies affected by IDC problems (see clause 23.4 of TS 36.300 [2]); + - The list of frequency ranges/frequency range combinations affected by the IDC problems; + - DRX based TDM assistance information (see clause 23.4.2 of TS 36.300 [2]); +- Its RRM measurement relaxation status indicating whether RRM measurement relaxation criteria are met or not; + +- Its RLM measurement relaxation status indicating whether the UE is applying RLM measurements relaxation; +- Its BFD measurement relaxation status indicating whether the UE is applying BFD measurements relaxation; +- If it prefers not operating on multi-Rx (i.e. not supporting simultaneous reception with different QCL-typeD) for FR2. + +NOTE: The requirements on RRM/RLM/CSI measurements in different phases of IDC interference defined in TS 36.300 [2] are applicable except that for NR serving cell, the requirements in TS 38.133 [13] and TS 38.101-1 [18], TS 38.101-2 [35], TS 38.101-3 [36] apply. + +In the second case, the UE can express a preference for temporarily reducing the number of maximum secondary component carriers, the maximum aggregated bandwidth and the number of maximum MIMO layers. In all cases, it is up to the gNB whether to accommodate the request. + +For sidelink, the UE can report SL traffic pattern(s) to NG-RAN, for periodic traffic. + +## 7.10 Segmentation of RRC messages + +An RRC message may be segmented in case the size of the encoded RRC message PDU exceeds the maximum PDCP SDU size. Segmentation is performed in the RRC layer using a separate RRC PDU to carry each segment. The receiver reassembles the segments to form the complete RRC message. All segments of an RRC message are transmitted before sending another RRC message. Segmentation is supported in both uplink and downlink as specified in TS 38.331 [12]. + +--- + +## 8 NG Identities + +### 8.1 UE Identities + +In this clause, the identities used by NR connected to 5GC are listed. For scheduling at cell level, the following identities are used: + +- C-RNTI: unique UE identification used as an identifier of the RRC Connection and for scheduling; +- CG-SDT-CS-RNTI: unique UE identification used for Configured Grant-based SDT in the uplink; +- CI-RNTI: identification of cancellation in the uplink; +- CS-RNTI: unique UE identification used for Semi-Persistent Scheduling in the downlink or configured grant in the uplink; +- INT-RNTI: identification of pre-emption in the downlink; +- MCS-C-RNTI: unique UE identification used for indicating an alternative MCS table for PDSCH and PUSCH; +- P-RNTI: identification of Paging and System Information change notification in the downlink; +- SI-RNTI: identification of Broadcast and System Information in the downlink; +- SP-CSI-RNTI: unique UE identification used for semi-persistent CSI reporting on PUSCH. + +For power and slot format control, the following identities are used: + +- SFI-RNTI: identification of slot format; +- TPC-PUCCH-RNTI: unique UE identification to control the power of PUCCH; +- TPC-PUSCH-RNTI: unique UE identification to control the power of PUSCH; +- TPC-SRS-RNTI: unique UE identification to control the power of SRS. + +During the random access procedure, the following identities are also used: + +- RA-RNTI: identification of the Random Access Response in the downlink; +- MSGRNTI: identification of the Random Access Response for 2-step RA type in the downlink; +- Temporary C-RNTI: UE identification temporarily used for scheduling during the random access procedure; +- Random value for contention resolution: UE identification temporarily used for contention resolution purposes during the random access procedure. + +For NR connected to 5GC, the following UE identity is used at NG-RAN level: + +- I-RNTI: used to identify the UE context in RRC\_INACTIVE. + +For UE power saving purpose, the following identities are used: + +- PS-RNTI: used to determine if the UE needs to monitor PDCCH on the next occurrence of the connected mode DRX on-duration; +- PEI-RNTI: used to determine if the UE needs to monitor the associated PO. + +For IAB the following identity is used: + +- AI-RNTI: identification of the DCI carrying availability indication for soft symbols of an IAB-DU. + +For Network-Controlled Repeater the following identity is used: + +- NCR-RNTI: identification of the DCI carrying side control information. + +For MBS, the following identities are used: + +- G-RNTI: Identifies dynamically scheduled PTM transmissions of MTCH(s); +- G-CS-RNTI: Identifies configured scheduled PTM transmissions of MTCH(s) scheduled with configured grant; +- MCCH-RNTI: Identifies transmissions of MCCH and MCCH change notification. + +For sidelink, the following identities are used: + +- SL-RNTI: unique UE identification used for NR sidelink communication scheduling; +- SL-CS-RNTI: unique UE identification used for configured sidelink grant for NR sidelink communication; +- SL Semi-Persistent Scheduling V-RNTI: unique UE identification used for semi-persistent scheduling for V2X sidelink communication; +- SL-PRS-RNTI: unique UE identification used for SL-PRS transmission scheduling on dedicated SL-PRS resource pool; +- SL-PRS-CS-RNTI: unique UE identification used for configured sidelink grant for SL-PRS transmission on dedicated SL-PRS resource pool. + +## 8.2 Network Identities + +The following identities are used in NG-RAN for identifying a specific network entity: + +- AMF Name: used to identify an AMF. +- NR Cell Global Identifier (NCGI): used to identify NR cells globally. The NCGI is constructed from the PLMN identity the cell belongs to and the NR Cell Identity (NCI) of the cell. The PLMN ID included in the NCGI should be the first PLMN ID within the set of PLMN IDs associated to the NR Cell Identity in SIB1, following the order of broadcast. + +NOTE 1: How to manage the scenario where a different PLMN ID has been allocated by the operator for an NCGI is left to OAM and/or implementation. + +- gNB Identifier (gNB ID): used to identify gNBs within a PLMN. The gNB ID is contained within the NCI of its cells. +- Global gNB ID: used to identify gNBs globally. The Global gNB ID is constructed from the PLMN identity the gNB belongs to and the gNB ID. The MCC and MNC are the same as included in the NCGI. + +NOTE 2: It is not precluded that a cell served by a gNB does not broadcast the PLMN ID included in the Global gNB ID. + +- Tracking Area identity (TAI): used to identify tracking areas. The TAI is constructed from the PLMN identity the tracking area belongs to and the TAC (Tracking Area Code) of the Tracking Area. +- Single Network Slice Selection Assistance information (S-NSSAI): identifies a network slice. +- Network Slice AS Group (NSAG): identifies an association to a slice or a set of slices. An NSAG is defined within a TA, used for slice-based cell reselection and/or slice-based RACH configuration. Values of NSAG IDs associated with different slice or set of slices shall be unique within a TA, also when slice-based cell reselection and slice-based RACH configuration are both supported in the TA. +- Network Identifier (NID): identifies an SNPN in combination with a PLMN ID. +- Closed Access Group Identifier: identifies a CAG within a PLMN. +- Local NG-RAN Node Identifier: used as reference to the NG-RAN node in the I-RNTI. + +## 8.3 User Data Transport on the CN-RAN Interface + +The core network may provide two transport layer addresses of different versions to enable that a NG-RAN node can select either IPv4 or IPv6. + +## 8.4 NR sidelink communication and V2X sidelink communication related identities + +The following identities are used for NR sidelink communication: + +- Source Layer-2 ID: Identifies the sender of the data in NR sidelink communication. The Source Layer-2 ID is 24 bits long and is split in the MAC layer into two bit strings: + - One bit string is the LSB part (8 bits) of Source Layer-2 ID and forwarded to physical layer of the sender. This identifies the source of the intended data in sidelink control information and is used for filtering of packets at the physical layer of the receiver; + - Second bit string is the MSB part (16 bits) of the Source Layer-2 ID and is carried within the MAC header. This is used for filtering of packets at the MAC layer of the receiver. +- Destination Layer-2 ID: Identifies the target of the data in NR sidelink communication. For NR sidelink communication, the Destination Layer-2 ID is 24 bits long and is split in the MAC layer into two bit strings: + - One bit string is the LSB part (16 bits) of Destination Layer-2 ID and forwarded to physical layer of the sender. This identifies the target of the intended data in sidelink control information and is used for filtering of packets at the physical layer of the receiver; + - Second bit string is the MSB part (8 bits) of the Destination Layer-2 ID and is carried within the MAC header. This is used for filtering of packets at the MAC layer of the receiver. +- PC5 Link Identifier: Uniquely identifies the PC5 unicast link in a UE for the lifetime of the PC5 unicast link as specified in TS 23.287 [40]. The PC5 Link Identifier is used to indicate to upper layers the PC5 unicast link in which sidelink RLF was declared and corresponding PC5-RRC connection was released. + +V2X sidelink communication related identities are specified in clause 8.3 of TS 36.300 [2]. + +## 9 Mobility and State Transitions + +### 9.1 Overview + +Load balancing is achieved in NR with handover, redirection mechanisms upon RRC release and through the usage of inter-frequency and inter-RAT absolute priorities and inter-frequency Offset parameters. + +Measurements to be performed by a UE for connected mode mobility are classified in at least four measurement types: + +- Intra-frequency NR measurements; +- Inter-frequency NR measurements; +- Inter-RAT measurements for E-UTRA; +- Inter-RAT measurements for UTRA. + +For each measurement type one or several measurement objects can be defined (a measurement object defines e.g. the carrier frequency to be monitored). + +For each measurement object one or several reporting configurations can be defined (a reporting configuration defines the reporting criteria). Three reporting criteria are used: event triggered reporting, periodic reporting and event triggered periodic reporting. + +The association between a measurement object and a reporting configuration is created by a measurement identity (a measurement identity links together one measurement object and one reporting configuration of the same RAT). By using several measurement identities (one for each measurement object, reporting configuration pair) it is then possible to: + +- Associate several reporting configurations to one measurement object and; +- Associate one reporting configuration to several measurement objects. + +The measurements identity is used as well when reporting results of the measurements. + +Measurement quantities are considered separately for each RAT. + +Measurement commands are used by NG-RAN to order the UE to start, modify or stop measurements. + +Handover can be performed within the same RAT and/or CN, or it can involve a change of the RAT and/or CN. + +Inter system fallback towards E-UTRAN is performed when 5GC does not support emergency services, voice services, for load balancing etc. Depending on factors such as CN interface availability, network configuration and radio conditions, the fallback procedure results in either RRC\_CONNECTED state mobility (handover procedure) or RRC\_IDLE state mobility (redirection), see TS 23.501 [3] and TS 38.331 [12]. + +SRVCC from 5G to UTRAN, if supported by both the UE and the network, may be performed to handover a UE with an ongoing voice call from NR to UTRAN. The overall procedure is described in TS 23.216 [34]. See also TS 38.331 [12] and TS 38.413 [26]. + +In the NG-C signalling procedure, the AMF based on support for emergency services, voice service, any other services or for load balancing etc, may indicate the target CN type as EPC or 5GC to the gNB node. When the target CN type is received by gNB, the target CN type is also conveyed to the UE in *RRCRelease* Message. + +Inter-gNB CSI-RS based mobility, i.e. handover, is supported between two neighbour gNBs by enabling that neighbour gNBs can exchange and forward their own CSI-RS configurations and on/off status. + +## 9.2 Intra-NR + +### 9.2.1 Mobility in RRC\_IDLE + +#### 9.2.1.1 Cell Selection + +The principles of PLMN selection in NR are based on the 3GPP PLMN selection principles. Cell selection is required on transition from RM-DEREGISTERED to RM-REGISTERED, from CM-IDLE to CM-CONNECTED and from CM-CONNECTED to CM-IDLE and is based on the following principles: + +- The UE NAS layer identifies a selected PLMN and equivalent PLMNs; +- Cell selection is always based on CD-SSBs located on the synchronization raster (see clause 5.2.4): + - The UE searches the NR frequency bands and for each carrier frequency identifies the strongest cell as per the CD-SSB. It then reads cell system information broadcast to identify its PLMN(s): + - The UE may search each carrier in turn ("initial cell selection") or make use of stored information to shorten the search ("stored information cell selection"). +- The UE seeks to identify a suitable cell; if it is not able to identify a suitable cell it seeks to identify an acceptable cell. When a suitable cell is found or if only an acceptable cell is found it camps on that cell and commence the cell reselection procedure: + - A suitable cell is one for which the measured cell attributes satisfy the cell selection criteria; the cell PLMN is the selected PLMN, registered or an equivalent PLMN; the cell is not barred or reserved and the cell is not part of a tracking area which is in the list of "forbidden tracking areas for roaming"; + - An acceptable cell is one for which the measured cell attributes satisfy the cell selection criteria and the cell is not barred. +- The IAB-MT and NCR-MT apply the cell selection procedure as described for the UE with the following differences: + - The IAB-MT and NCR-MT ignore cell-barring or cell-reservation indications contained in cell system information broadcast; + - The IAB-MT only considers a cell as a candidate for cell selection if the cell system information broadcast indicates IAB support for the selected PLMN or the selected SNPN, and the NCR-MT only considers a cell as a candidate for cell selection if the cell system information broadcast indicates Network-Controlled Repeater support. +- The mobile IAB-MT applies the cell selection procedure as described for the IAB-MT with the following differences: + - The mobile IAB-MT only considers a cell as a candidate cell for cell selection if the cell system information broadcast indicates mobile IAB support. + +Transition to RRC\_IDLE: + +On transition from RRC\_CONNECTED or RRC\_INACTIVE to RRC\_IDLE, a UE should camp on a cell as result of cell selection according to the frequency be assigned by RRC in the state transition message if any. + +Recovery from out of coverage: + +The UE should attempt to find a suitable cell in the manner described for stored information or initial cell selection above. If no suitable cell is found on any frequency or RAT, the UE should attempt to find an acceptable cell. + +In multi-beam operations, the cell quality is derived amongst the beams corresponding to the same cell (see clause 9.2.4). + +### 9.2.1.2 Cell Reselection + +A UE in RRC\_IDLE performs cell reselection. The principles of the procedure are the following: + +- Cell reselection is always based on CD-SSBs located on the synchronization raster (see clause 5.2.4). +- The UE makes measurements of attributes of the serving and neighbour cells to enable the reselection process: + - For the search and measurement of inter-frequency neighbouring cells, only the carrier frequencies need to be indicated. +- Cell reselection identifies the cell that the UE should camp on. It is based on cell reselection criteria which involves measurements of the serving and neighbour cells: + - Intra-frequency reselection is based on ranking of cells; + - Inter-frequency reselection is based on absolute priorities where a UE tries to camp on the highest priority frequency available; + - A Neighbour Cell List (NCL) can be provided by the serving cell to handle specific cases for intra- and inter-frequency neighbouring cells; + - Exclude-lists can be provided to prevent the UE from reselecting to specific intra- and inter-frequency neighbouring cells; + - Allow-lists can be provided to request the UE to reselect to only specific intra- and inter-frequency neighbouring cells; + - Cell reselection can be speed dependent; + - Service specific prioritisation; + - Slice-based cell reselection information can be provided to facilitate the UE to reselect a cell that supports specific slices. + +In multi-beam operations, the cell quality is derived amongst the beams corresponding to the same cell (see clause 9.2.4). + +### 9.2.1.3 State Transitions + +The following figure describes the UE triggered transition from RRC\_IDLE to RRC\_CONNECTED (for the NAS part, see TS 23.502 [22]): + +![Sequence diagram showing the UE triggered transition from RRC_IDLE to RRC_CONNECTED. The diagram involves three entities: UE, gNB, and AMF. The UE starts in RRC_IDLE and CM-IDLE state. It sends an RRCSetupRequest to the gNB. The gNB responds with RRCSetup. The UE then enters RRC_CONNECTED and CM-IDLE state. It sends RRCSetupComplete to the gNB. The gNB then sends an INITIAL UE MESSAGE to the AMF. The AMF responds with DOWNLINK NAS TRANSPORT. The UE sends DLInformationTransfer to the gNB. The gNB sends ULInformationTransfer to the AMF. The AMF responds with UPLINK NAS TRANSPORT. The gNB sends INITIAL CONTEXT SETUP REQUEST to the AMF. The AMF responds with SecurityModeCommand. The gNB sends SecurityModeComplete to the UE. The gNB then sends RRCReconfiguration to the UE. The UE responds with RRCReconfigurationComplete. Finally, the gNB sends INITIAL CONTEXT SETUP RESPONSE to the AMF. The UE is now in RRC_CONNECTED and CM-CONNECTED state.](719ef0f734259484038b2434e5dc3f24_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB + participant AMF + Note left of UE: UE in RRC_IDLE +CM-IDLE + UE->>gNB: 1. RRCSetupRequest + gNB-->>UE: 2. RRCSetup + Note left of UE: UE in RRC_CONNECTED +CM-IDLE + UE->>gNB: 2a. RRCSetupComplete + gNB->>AMF: 3. INITIAL UE MESSAGE + Note right of AMF: 4. DOWNLINK NAS TRANSPORT + UE-->>gNB: 4a. DLInformationTransfer + gNB-->>AMF: 5. ULInformationTransfer + Note right of AMF: 5a. UPLINK NAS TRANSPORT + gNB->>AMF: 6. INITIAL CONTEXT SETUP REQUEST + AMF-->>gNB: 7. SecurityModeCommand + gNB-->>UE: 7a. SecurityModeComplete + gNB->>UE: 8. RRCReconfiguration + UE-->>gNB: 8a. RRCReconfigurationComplete + Note left of UE: UE in RRC_CONNECTED +CM-CONNECTED + gNB->>AMF: 9. INITIAL CONTEXT SETUP RESPONSE + +``` + +Sequence diagram showing the UE triggered transition from RRC\_IDLE to RRC\_CONNECTED. The diagram involves three entities: UE, gNB, and AMF. The UE starts in RRC\_IDLE and CM-IDLE state. It sends an RRCSetupRequest to the gNB. The gNB responds with RRCSetup. The UE then enters RRC\_CONNECTED and CM-IDLE state. It sends RRCSetupComplete to the gNB. The gNB then sends an INITIAL UE MESSAGE to the AMF. The AMF responds with DOWNLINK NAS TRANSPORT. The UE sends DLInformationTransfer to the gNB. The gNB sends ULInformationTransfer to the AMF. The AMF responds with UPLINK NAS TRANSPORT. The gNB sends INITIAL CONTEXT SETUP REQUEST to the AMF. The AMF responds with SecurityModeCommand. The gNB sends SecurityModeComplete to the UE. The gNB then sends RRCReconfiguration to the UE. The UE responds with RRCReconfigurationComplete. Finally, the gNB sends INITIAL CONTEXT SETUP RESPONSE to the AMF. The UE is now in RRC\_CONNECTED and CM-CONNECTED state. + +**Figure 9.2.1.3-1: UE triggered transition from RRC\_IDLE to RRC\_CONNECTED** + +1. The UE requests to setup a new connection from RRC\_IDLE. + +2/2a. The gNB completes the RRC setup procedure. + +NOTE: The scenario where the gNB rejects the request is described below. + +3. The first NAS message from the UE, piggybacked in *RRCSetupComplete*, is sent to AMF. + +4/4a/5/5a. Additional NAS messages may be exchanged between UE and AMF, see TS 23.502 [22]. + +6. The AMF prepares the UE context data (including PDU session context, the Security Key, UE Radio Capability and UE Security Capabilities, etc.) and sends it to the gNB. + +7/7a. The gNB activates the AS security with the UE. + +8/8a. The gNB performs the reconfiguration to setup SRB2 and DRBs for UE, or SRB2 and optionally DRBs for IAB-MT. + +9. The gNB informs the AMF that the setup procedure is completed. + +NOTE 1: RRC messages in step 1 and 2 use SRB0, all the subsequent messages use SRB1. Messages in steps 7/7a are integrity protected. From step 8 on, all the messages are integrity protected and ciphered. + +NOTE 2: For signalling only connection, step 8 is skipped since SRB2 and DRBs are not setup. + +The following figure describes the rejection from the network when the UE attempts to setup a connection from RRC\_IDLE: + +![Sequence diagram showing the rejection of a UE triggered transition from RRC_IDLE. The diagram involves a UE and a gNB. The UE is in RRC_IDLE and CM-IDLE states. The sequence of messages is: 1. RRCSetupRequest from UE to gNB; 2. A box labeled 'Procedure cannot be handled (e.g. congestion)' on the gNB side; 3. RRCReject (wait time) from gNB to UE.](3198cdf0dbe501c46fe0e4073c7d8451_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB + Note left of UE: UE in RRC_IDLE +CM-IDLE + UE->>gNB: 1. RRCSetupRequest + Note right of gNB: 2. Procedure cannot be handled +(e.g. congestion) + gNB-->>UE: 3. RRCReject (wait time) + +``` + +Sequence diagram showing the rejection of a UE triggered transition from RRC\_IDLE. The diagram involves a UE and a gNB. The UE is in RRC\_IDLE and CM-IDLE states. The sequence of messages is: 1. RRCSetupRequest from UE to gNB; 2. A box labeled 'Procedure cannot be handled (e.g. congestion)' on the gNB side; 3. RRCReject (wait time) from gNB to UE. + +**Figure 9.2.1.3-2: Rejection of UE triggered transition from RRC\_IDLE** + +1. UE attempts to setup a new connection from RRC\_IDLE. +2. The gNB is not able to handle the procedure, for instance due to congestion. +3. The gNB sends *RRCReject* (with a wait time) to keep the UE in RRC\_IDLE. + +## 9.2.2 Mobility in RRC\_INACTIVE + +### 9.2.2.1 Overview + +RRC\_INACTIVE is a state where a UE remains in CM-CONNECTED and can move within an area configured by NG-RAN (the RNA) without notifying NG-RAN. In RRC\_INACTIVE, the last serving gNB node keeps the UE context and the UE-associated NG connection with the serving AMF and UPF. + +For a UE in RRC\_INACTIVE with eDRX cycle longer than 10.24 seconds, the NG-RAN node may, based on implementation, send a request to the AMF to perform MT Communication Handling as described in TS 23.501 [3]. + +If the last serving gNB receives DL data from the UPF or DL UE-associated signalling from the AMF (except the UE Context Release Command message) while the UE is in RRC\_INACTIVE, it pages in the cells corresponding to the RNA and may send XnAP RAN Paging to neighbour gNB(s) if the RNA includes cells of neighbour gNB(s). + +Upon receiving the RAN Paging Request message from the AMF while the UE is in RRC\_INACTIVE with eDRX beyond 10.24 seconds, the last serving gNB may page in its cells comprised in the RNA and may send XnAP RAN Paging to neighbour gNB(s) if the RNA includes cells of neighbour gNB(s), in order for the gNB to trigger the UE to resume connection in RRC\_CONNECTED state or RRC\_INACTIVE state. + +Upon receiving the UE Context Release Command message while the UE is in RRC\_INACTIVE, the last serving gNB may page in the cells corresponding to the RNA and may send XnAP RAN Paging to neighbour gNB(s) if the RNA includes cells of neighbour gNB(s), in order to release UE explicitly. + +Upon receiving the NG RESET message while the UE is in RRC\_INACTIVE, the last serving gNB may page involved UEs in the cells corresponding to the RNA and may send XnAP RAN Paging to neighbour gNB(s) if the RNA includes cells of neighbour gNB(s) in order to explicitly release involved UEs. + +Upon RAN paging failure, the gNB behaves according to TS 23.501 [3]. + +The AMF provides to the NG-RAN node the Core Network Assistance Information to assist the NG-RAN node's decision whether the UE can be sent to RRC\_INACTIVE, and to assist UE configuration and paging in RRC\_INACTIVE. The Core Network Assistance Information includes the registration area configured for the UE, the Periodic Registration Update timer, and the UE Identity Index value, and may include the UE specific DRX, an indication if the UE is configured with Mobile Initiated Connection Only (MICO) mode by the AMF, the Expected UE Behaviour, the UE Radio Capability for Paging, the PEI with Paging Subgrouping assistance information, the NR Paging eDRX Information, the Paging Cause Indication for Voice Service, the Hashed UE Identity Index Value and the CN support indication for MT Communication Handling. The UE registration area is taken into account by the NG-RAN node when configuring the RNA. The UE specific DRX and UE Identity Index value are used by the NG-RAN node for RAN paging. The Periodic Registration Update timer is taken into account by the NG-RAN node to configure Periodic RNA Update timer. The NG-RAN node takes into account the Expected UE Behaviour to assist the UE RRC state transition decision. The NG-RAN node may use the UE Radio Capability for Paging during RAN Paging. The + +NG-RAN node takes into account the PEI with Paging Subgrouping assistance information for subgroup paging in RRC\_INACTIVE except when the UE context contains an emergency PDU session in which case the PEI with Paging Subgrouping assistance information shall not be used according to TS 24.501 [28]. When sending the XnAP RAN Paging to neighbour NG-RAN node(s), the PEI with Paging Subgrouping assistance information may be included. The NG-RAN node takes into account the NR Paging eDRX Information to configure the RAN Paging when the NR UE is in RRC\_INACTIVE. When sending XnAP RAN Paging to neighbour NG-RAN node(s), the NR Paging eDRX Information for RRC\_IDLE and for RRC\_INACTIVE may be included. The NG-RAN node takes into consideration the Paging Cause Indication for Voice Service to include the Paging Cause in RAN Paging for a UE in RRC\_INACTIVE state. When sending XnAP RAN Paging to neighbour NG-RAN node(s), the Paging Cause may be included. When sending XnAP RAN Paging to neighbour NG-RAN node(s), the Hashed UE Identity Index Value may be included to determine the start point of PTW. The NG-RAN takes into account the CN support indication for MT Communication Handling when deciding to request the AMF for MT Communication Handling for a UE in RRC\_INACTIVE state with long eDRX beyond 10.24 seconds as described in TS 23.501 [3]. + +At transition to RRC\_INACTIVE the NG-RAN node may configure the UE with a periodic RNA Update timer value. At periodic RNA Update timer expiry without notification from the UE, the gNB behaves as specified in TS 23.501 [3]. + +If the UE accesses a gNB other than the last serving gNB, the receiving gNB triggers the XnAP Retrieve UE Context procedure to get the UE context from the last serving gNB and may also trigger an Xn-U Address Indication procedure including tunnel information for potential recovery of data from the last serving gNB. Upon successful UE context retrieval, the receiving gNB shall perform the slice-aware admission control in case of receiving slice information and becomes the serving gNB and it further triggers the NGAP Path Switch Request and applicable RRC procedures. After the path switch procedure, the serving gNB triggers release of the UE context at the last serving gNB by means of the XnAP UE Context Release procedure. + +In case the UE is not reachable at the last serving gNB, the gNB shall fail any AMF initiated UE-associated class 1 procedure which allows the signalling of unsuccessful operation in the respective response message. It may trigger the NAS Non Delivery Indication procedure to report the non-delivery of any non PDU Session related NAS PDU received from the AMF as specified in TS 38.413 [26]. + +If the UE accesses a gNB other than the last serving gNB and the receiving gNB does not find a valid UE Context, the receiving gNB can perform establishment of a new RRC connection instead of resumption of the previous RRC connection. UE context retrieval will also fail and hence a new RRC connection needs to be established if the serving AMF changes. + +A UE in the RRC\_INACTIVE state is required to initiate RNA update procedure when it moves out of the configured RNA. When receiving RNA update request from the UE, the receiving gNB triggers the XnAP Retrieve UE Context procedure to get the UE context from the last serving gNB and may decide to send the UE back to RRC\_INACTIVE state, move the UE into RRC\_CONNECTED state, or send the UE to RRC\_IDLE. In case of periodic RNA update, if the last serving gNB decides not to relocate the UE context, it fails the Retrieve UE Context procedure and sends the UE back to RRC\_INACTIVE, or to RRC\_IDLE directly by an encapsulated *RRCRelease* message. + +### 9.2.2.2 Cell Reselection + +A UE in RRC\_INACTIVE performs cell reselection. The principles of the procedure are as for the RRC\_IDLE state (see clause 9.2.1.2). + +### 9.2.2.3 RAN-Based Notification Area + +A UE in the RRC\_INACTIVE state can be configured by the last serving NG-RAN node with an RNA, where: + +- the RNA can cover a single or multiple cells, and shall be contained within the CN registration area; in this release Xn connectivity should be available within the RNA; +- a RAN-based notification area update (RNAU) is periodically sent by the UE and is also sent when the cell reselection procedure of the UE selects a cell that does not belong to the configured RNA. + +There are several different alternatives on how the RNA can be configured: + +- List of cells: + - A UE is provided an explicit list of cells (one or more) that constitute the RNA. + +- List of RAN areas: + - A UE is provided (at least one) RAN area ID, where a RAN area is a subset of a CN Tracking Area or equal to a CN Tracking Area. A RAN area is specified by one RAN area ID, which consists of a TAC and optionally a RAN area Code; + - A cell broadcasts one or, in case of network sharing with multiple cell ID broadcast, more RAN area IDs in the system information. + +NG-RAN may provide different RNA definitions to different UEs but not mix different definitions to the same UE at the same time. UE shall support all RNA configuration options listed above. + +## 9.2.2.4 State Transitions + +### 9.2.2.4.1 UE triggered transition from RRC\_INACTIVE to RRC\_CONNECTED + +The following figure describes the UE triggered transition from RRC\_INACTIVE to RRC\_CONNECTED in case of UE context retrieval success: + +![Sequence diagram showing the UE triggered transition from RRC_INACTIVE to RRC_CONNECTED. The diagram involves four lifelines: UE, gNB, Last Serving gNB, and AMF. The process starts with the UE in RRC_INACTIVE CM-CONNECTED state. The UE sends an RRCResumeRequest to the gNB. The gNB sends a RETRIEVE UE CONTEXT REQUEST to the Last Serving gNB. The Last Serving gNB responds with a RETRIEVE UE CONTEXT RESPONSE. The gNB then sends an RRCResume to the UE. The UE transitions to RRC_CONNECTED CM-CONNECTED state and sends an RRCResumeComplete to the gNB. The gNB sends an Xn-U ADDRESS INDICATION to the Last Serving gNB. The gNB then sends a PATH SWITCH REQUEST to the AMF. The AMF responds with a PATH SWITCH REQUEST RESPONSE. Finally, the gNB sends a UE CONTEXT RELEASE to the Last Serving gNB.](59121d561a4158609b4c354b9ffd0605_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB + participant Last Serving gNB + participant AMF + + Note left of UE: UE in RRC_INACTIVE CM-CONNECTED + UE->>gNB: 1. RRCResumeRequest + gNB->>Last Serving gNB: 2. RETRIEVE UE CONTEXT REQUEST + Last Serving gNB-->>gNB: 3. RETRIEVE UE CONTEXT RESPONSE + gNB->>UE: 4. RRCResume + Note left of UE: UE in RRC_CONNECTED CM-CONNECTED + UE->>gNB: 5. RRCResumeComplete + gNB-->>Last Serving gNB: 6. Xn-U ADDRESS INDICATION + gNB->>AMF: 7. PATH SWITCH REQUEST + AMF-->>gNB: 8. PATH SWITCH REQUEST RESPONSE + gNB->>Last Serving gNB: 9. UE CONTEXT RELEASE + +``` + +Sequence diagram showing the UE triggered transition from RRC\_INACTIVE to RRC\_CONNECTED. The diagram involves four lifelines: UE, gNB, Last Serving gNB, and AMF. The process starts with the UE in RRC\_INACTIVE CM-CONNECTED state. The UE sends an RRCResumeRequest to the gNB. The gNB sends a RETRIEVE UE CONTEXT REQUEST to the Last Serving gNB. The Last Serving gNB responds with a RETRIEVE UE CONTEXT RESPONSE. The gNB then sends an RRCResume to the UE. The UE transitions to RRC\_CONNECTED CM-CONNECTED state and sends an RRCResumeComplete to the gNB. The gNB sends an Xn-U ADDRESS INDICATION to the Last Serving gNB. The gNB then sends a PATH SWITCH REQUEST to the AMF. The AMF responds with a PATH SWITCH REQUEST RESPONSE. Finally, the gNB sends a UE CONTEXT RELEASE to the Last Serving gNB. + +**Figure 9.2.2.4.1-1: UE triggered transition from RRC\_INACTIVE to RRC\_CONNECTED (UE context retrieval success)** + +1. The UE resumes from RRC\_INACTIVE, providing the I-RNTI, allocated by the last serving gNB. +2. The gNB, if able to resolve the gNB identity contained in the I-RNTI, requests the last serving gNB to provide UE Context data. +3. The last serving gNB provides UE context data. +- 4/5. The gNB and UE completes the resumption of the RRC connection. + +NOTE: User Data can also be sent in step 5 if the grant allows. + +6. If loss of DL user data buffered in the last serving gNB shall be prevented, the gNB provides forwarding addresses. +- 7/8. The gNB performs path switch. +9. The gNB triggers the release of the UE resources at the last serving gNB. + +After step 1 above, when the gNB decides to use a single RRC message to reject the Resume Request right away and keep the UE in RRC\_INACTIVE without any reconfiguration (e.g. as described in the two examples below), or when the gNB decides to setup a new RRC connection, SRB0 (without security) is used. Conversely, when the gNB decides to reconfigure the UE (e.g. with a new DRX cycle or RNA) or when the gNB decides to push the UE to RRC\_IDLE, SRB1 (with integrity protection and ciphering as previously configured for that SRB) shall be used. + +NOTE: SRB1 can only be used once the UE Context is retrieved i.e. after step 3. + +The following figure describes the UE triggered transition from RRC\_INACTIVE to RRC\_CONNECTED in case of UE context retrieval failure: + +![Sequence diagram showing UE triggered transition from RRC_INACTIVE to RRC_CONNECTED due to UE context retrieval failure. Lifelines: UE, gNB, Last Serving gNB, AMF. The UE sends an RRCResumeRequest. The gNB sends a RETRIEVE UE CONTEXT REQUEST to the Last Serving gNB. The Last Serving gNB responds with a failure. The gNB then sends an RRCSetup to the UE, leading to a 'Setup New RRC Connection'.](4537891530c9f6f139a2e1ebf544edc4_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB + participant LastServinggNB as Last Serving gNB + participant AMF + Note left of UE: UE in RRC_INACTIVE CM-CONNECTED + UE->>gNB: 1. RRCResumeRequest + gNB->>LastServinggNB: 2. RETRIEVE UE CONTEXT REQUEST + LastServinggNB-->>gNB: 3. Failure to retrieve or verify UE context + gNB->>LastServinggNB: 4. RETRIEVE UE CONTEXT FAILURE + gNB->>UE: 5. RRCSetup + Note over UE, gNB, LastServinggNB, AMF: 6. Setup New RRC Connection + +``` + +Sequence diagram showing UE triggered transition from RRC\_INACTIVE to RRC\_CONNECTED due to UE context retrieval failure. Lifelines: UE, gNB, Last Serving gNB, AMF. The UE sends an RRCResumeRequest. The gNB sends a RETRIEVE UE CONTEXT REQUEST to the Last Serving gNB. The Last Serving gNB responds with a failure. The gNB then sends an RRCSetup to the UE, leading to a 'Setup New RRC Connection'. + +**Figure 9.2.2.4.1-2: UE triggered transition from RRC\_INACTIVE to RRC\_CONNECTED (UE context retrieval failure)** + +1. The UE resumes from RRC\_INACTIVE, providing the I-RNTI, allocated by the last serving gNB. +2. The gNB, if able to resolve the gNB identity contained in the I-RNTI, requests the last serving gNB to provide UE Context data. +3. The last serving gNB cannot retrieve or verify the UE context data. +4. The last serving gNB indicates the failure to the gNB. +5. The gNB performs a fallback to establish a new RRC connection by sending *RRCSetup*. +6. A new connection is setup as described in clause 9.2.1.3. + +The following figure describes the rejection from the network when the UE attempts to resume a connection from RRC\_INACTIVE: + +![Sequence diagram showing a rejection from the network. Lifelines: UE, gNB. The UE sends an RRCResumeRequest. The gNB responds with 'Procedure cannot be handled (e.g. congestion)' and then sends an RRCReject (wait time) to the UE.](67c232883c119b120d2fb337bf588e05_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB + Note left of UE: UE in RRC_INACTIVE CM-CONNECTED + UE->>gNB: 1. RRCResumeRequest + gNB-->>gNB: 2. Procedure cannot be handled (e.g. congestion) + gNB->>UE: 3. RRCReject (wait time) + +``` + +Sequence diagram showing a rejection from the network. Lifelines: UE, gNB. The UE sends an RRCResumeRequest. The gNB responds with 'Procedure cannot be handled (e.g. congestion)' and then sends an RRCReject (wait time) to the UE. + +**Figure 9.2.2.4.1-3: Reject from the network, UE attempts to resume a connection** + +1. UE attempts to resume the connection from RRC\_INACTIVE. + +2. The gNB is not able to handle the procedure, for instance due to congestion. +3. The gNB sends *RRReject* (with a wait time) to keep the UE in RRC\_INACTIVE. + +#### 9.2.2.4.2 Network triggered transition from RRC\_INACTIVE to RRC\_CONNECTED + +The following figure describes the network triggered transition from RRC\_INACTIVE to RRC\_CONNECTED: + +![Sequence diagram for network triggered transition from RRC_INACTIVE to RRC_CONNECTED. Lifelines: UE, Last Serving gNB, gNB, AMF. The UE is in RRC_INACTIVE CM-CONNECTED state. The sequence of messages is: 1. RAN Paging Trigger (from Last Serving gNB to gNB), 2. RAN Paging (from gNB to Last Serving gNB), 3. Paging UE (from Last Serving gNB to UE), 4. Resuming from RRC_INACTIVE (from UE to Last Serving gNB).](c2f36c545b190860d04e1d84e58d22cc_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Last Serving gNB + participant gNB + participant AMF + Note left of UE: UE in RRC_INACTIVE CM-CONNECTED + Last Serving gNB->>gNB: 1. RAN Paging Trigger + gNB-->>Last Serving gNB: 2. RAN Paging + Last Serving gNB->>UE: 3. Paging UE + UE->>Last Serving gNB: 4. Resuming from RRC_INACTIVE + +``` + +Sequence diagram for network triggered transition from RRC\_INACTIVE to RRC\_CONNECTED. Lifelines: UE, Last Serving gNB, gNB, AMF. The UE is in RRC\_INACTIVE CM-CONNECTED state. The sequence of messages is: 1. RAN Paging Trigger (from Last Serving gNB to gNB), 2. RAN Paging (from gNB to Last Serving gNB), 3. Paging UE (from Last Serving gNB to UE), 4. Resuming from RRC\_INACTIVE (from UE to Last Serving gNB). + +**Figure 9.2.2.4.2-1: Network triggered transition from RRC\_INACTIVE to RRC\_CONNECTED** + +1. A RAN paging trigger event occurs (incoming DL user plane, DL signalling from 5GC, etc.). +2. RAN paging is triggered; either only in the cells controlled by the last serving gNB or also by means of Xn RAN Paging in cells controlled by other gNBs, configured to the UE in the RAN-based Notification Area (RNA). +3. The UE is paged with the I-RNTI. +4. If the UE has been successfully reached, it attempts to resume from RRC\_INACTIVE, as described in clause 9.2.2.4.1. + +#### 9.2.2.5 RNA update + +The following figure describes the UE triggered RNA update procedure involving context retrieval over Xn. The procedure may be triggered when the UE moves out of the configured RNA, or periodically. + +![Sequence diagram for RNA update procedure with UE context relocation. Lifelines: UE, gNB, Last Serving gNB, AMF. The UE is in RRC_INACTIVE CM-CONNECTED state. The sequence of messages is: 1. RRCResumeRequest with RNA Update (from UE to gNB), 2. RETRIEVE UE CONTEXT REQUEST (from gNB to Last Serving gNB), 3. RETRIEVE UE CONTEXT RESPONSE (from Last Serving gNB to gNB), 4. Send UE to INACTIVE (from gNB to Last Serving gNB), 5. Xn-U ADDRESS INDICATION (from Last Serving gNB to gNB), 6. PATH SWITCH REQUEST (from gNB to AMF), 7. PATH SWITCH REQUEST RESPONSE (from AMF to gNB), 8. RRCRelease with Suspend Indication (from gNB to UE), 9. UE CONTEXT RELEASE (from gNB to Last Serving gNB).](7b2d685b805535c1e94aee1365753b92_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB + participant Last Serving gNB + participant AMF + Note left of UE: UE in RRC_INACTIVE CM-CONNECTED + UE->>gNB: 1. RRCResumeRequest +RNA Update + gNB->>Last Serving gNB: 2. RETRIEVE UE CONTEXT REQUEST + Last Serving gNB-->>gNB: 3. RETRIEVE UE CONTEXT RESPONSE + gNB->>Last Serving gNB: 4. Send UE to INACTIVE + Last Serving gNB-->>gNB: 5. Xn-U ADDRESS INDICATION + gNB->>AMF: 6. PATH SWITCH REQUEST + AMF-->>gNB: 7. PATH SWITCH REQUEST RESPONSE + gNB->>UE: 8. RRCRelease +Suspend Indication + gNB->>Last Serving gNB: 9. UE CONTEXT RELEASE + +``` + +Sequence diagram for RNA update procedure with UE context relocation. Lifelines: UE, gNB, Last Serving gNB, AMF. The UE is in RRC\_INACTIVE CM-CONNECTED state. The sequence of messages is: 1. RRCResumeRequest with RNA Update (from UE to gNB), 2. RETRIEVE UE CONTEXT REQUEST (from gNB to Last Serving gNB), 3. RETRIEVE UE CONTEXT RESPONSE (from Last Serving gNB to gNB), 4. Send UE to INACTIVE (from gNB to Last Serving gNB), 5. Xn-U ADDRESS INDICATION (from Last Serving gNB to gNB), 6. PATH SWITCH REQUEST (from gNB to AMF), 7. PATH SWITCH REQUEST RESPONSE (from AMF to gNB), 8. RRCRelease with Suspend Indication (from gNB to UE), 9. UE CONTEXT RELEASE (from gNB to Last Serving gNB). + +**Figure 9.2.2.5-1: RNA update procedure with UE context relocation** + +1. The UE resumes from RRC\_INACTIVE, providing the I-RNTI allocated by the last serving gNB and appropriate cause value, e.g., RAN notification area update. +2. The gNB, if able to resolve the gNB identity contained in the I-RNTI, requests the last serving gNB to provide UE Context, providing the cause value received in step 1. +3. The last serving gNB may provide the UE context (as assumed in the following). Alternatively, the last serving gNB may decide to move the UE to RRC\_IDLE (and the procedure follows steps 3 and later of figure 9.2.2.5-3) or, if the UE is still within the previously configured RNA, to keep the UE context in the last serving gNB and to keep the UE in RRC\_INACTIVE (and the procedure follows steps 3 and later of figure 9.2.2.5-2). +4. The gNB may move the UE to RRC\_CONNECTED (and the procedure follows step 4 of Figure 9.2.2.4.1-1), or send the UE back to RRC\_IDLE (in which case an *RRCRelease* message is sent by the gNB), or send the UE back to RRC\_INACTIVE as assumed in the following. +5. If loss of DL user data buffered in the last serving gNB shall be prevented, the gNB provides forwarding addresses. +- 6/7. The gNB performs path switch. +8. The gNB keeps the UE in RRC\_INACTIVE state by sending *RRCRelease* with suspend indication. +9. The gNB triggers the release of the UE resources at the last serving gNB. + +The following figure describes the RNA update procedure for the case when the UE is still within the configured RNA and the last serving gNB decides not to relocate the UE context and to keep the UE in RRC\_INACTIVE: + +![Sequence diagram of the periodic RNA update procedure without UE context relocation. The diagram shows three participants: UE, gNB, and Last Serving gNB. The UE is in RRC_INACTIVE CM-CONNECTED state. The sequence of messages is: 1. UE sends RRCResumeRequest (RNA Update) to gNB; 2. gNB sends RETRIEVE UE CONTEXT REQUEST (RNA Update) to Last Serving gNB; 3. Last Serving gNB responds with RETRIEVE UE CONTEXT FAILURE; 4. gNB sends RRCRelease (Suspend Indication) to UE. A URL 'http://msc-generator.sourceforge.net v6.3.5' is visible at the bottom right.](4a390493f601ce1ac6b9201db4e28b5a_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB + participant LastServinggNB as Last Serving gNB + Note left of UE: UE in RRC_INACTIVE CM-CONNECTED + UE->>gNB: 1. RRCResumeRequest
RNA Update + gNB->>LastServinggNB: 2. RETRIEVE UE CONTEXT REQUEST
RNA Update + LastServinggNB-->>gNB: 3. RETRIEVE UE CONTEXT FAILURE + gNB->>UE: 4. RRCRelease
Suspend Indication + +``` + +http://msc-generator.sourceforge.net v6.3.5 + +Sequence diagram of the periodic RNA update procedure without UE context relocation. The diagram shows three participants: UE, gNB, and Last Serving gNB. The UE is in RRC\_INACTIVE CM-CONNECTED state. The sequence of messages is: 1. UE sends RRCResumeRequest (RNA Update) to gNB; 2. gNB sends RETRIEVE UE CONTEXT REQUEST (RNA Update) to Last Serving gNB; 3. Last Serving gNB responds with RETRIEVE UE CONTEXT FAILURE; 4. gNB sends RRCRelease (Suspend Indication) to UE. A URL 'http://msc-generator.sourceforge.net v6.3.5' is visible at the bottom right. + +**Figure 9.2.2.5-2: Periodic RNA update procedure without UE context relocation** + +1. The UE resumes from RRC\_INACTIVE, providing the I-RNTI allocated by the last serving gNB and appropriate cause value, e.g., RAN notification area update. +2. The gNB, if able to resolve the gNB identity contained in the I-RNTI, requests the last serving gNB to provide UE Context, providing the cause value received in step 1. +3. The last serving gNB stores received information to be used in the next resume attempt (e.g. C-RNTI and PCI related to the resumption cell), and responds to the gNB with the RETRIEVE UE CONTEXT FAILURE message including an encapsulated *RRCRelease* message. The *RRCRelease* message includes Suspend Indication. +4. The gNB forwards the *RRCRelease* message to the UE. + +The following figure describes the RNA update procedure for the case when the last serving gNB decides to move the UE to RRC\_IDLE: + +![Sequence diagram of RNA update procedure with transition to RRC_IDLE. The diagram shows three lifelines: UE, gNB, and Last Serving gNB. The UE starts in RRC_INACTIVE CM-CONNECTED state. It sends an RRCResumeRequest with an RNA update to the gNB. The gNB sends a RETRIEVE UE CONTEXT REQUEST to the Last Serving gNB. The Last Serving gNB responds with a RETRIEVE UE CONTEXT FAILURE and an RRC Release message. The gNB then sends an RRCRelease message to the UE, which transitions to RRC_IDLE CM-IDLE state. The Last Serving gNB also releases the UE context.](c07e21a8d65991db04263322f859c94f_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB + participant LastServinggNB as Last Serving gNB + + Note left of UE: UE in RRC_INACTIVE +CM-CONNECTED + UE->>gNB: 1. RRCResumeRequest +RNA update + gNB->>LastServinggNB: 2. RETRIEVE UE CONTEXT REQUEST + LastServinggNB-->>gNB: 3. RETRIEVE UE CONTEXT FAILURE +RRC Release + Note right of LastServinggNB: 4. Release UE context + gNB-->>UE: 5. RRCRelease + Note left of UE: UE in RRC_IDLE +CM-IDLE + +``` + +Sequence diagram of RNA update procedure with transition to RRC\_IDLE. The diagram shows three lifelines: UE, gNB, and Last Serving gNB. The UE starts in RRC\_INACTIVE CM-CONNECTED state. It sends an RRCResumeRequest with an RNA update to the gNB. The gNB sends a RETRIEVE UE CONTEXT REQUEST to the Last Serving gNB. The Last Serving gNB responds with a RETRIEVE UE CONTEXT FAILURE and an RRC Release message. The gNB then sends an RRCRelease message to the UE, which transitions to RRC\_IDLE CM-IDLE state. The Last Serving gNB also releases the UE context. + +**Figure 9.2.2.5-3: RNA update procedure with transition to RRC\_IDLE** + +1. The UE resumes from RRC\_INACTIVE, providing the I-RNTI allocated by the last serving gNB and appropriate cause value, e.g., RAN notification area update. +2. The gNB, if able to resolve the gNB identity contained in the I-RNTI, requests the last serving gNB to provide UE Context, providing the cause value received in step 1. +3. Instead of providing the UE context, the last serving gNB provides an *RRCRelease* message to move the UE to RRC\_IDLE. +4. The last serving gNB deletes the UE context. +5. The gNB sends the *RRCRelease* which triggers the UE to move to RRC\_IDLE. + +#### 9.2.2.6 Resume request responded with Release with Redirect, with UE context relocation + +The following figure describes a UE triggered NAS procedure responded by the network with a release with redirect, with UE context relocation. + +![Sequence diagram for Resume request responded with Release with Redirect, with UE Context relocation. The diagram shows interactions between UE, gNB, Last Serving gNB, and AMF. The UE sends an RRCResumeRequest. The gNB sends a RETRIEVE UE CONTEXT REQUEST to the Last Serving gNB, which responds with RETRIEVE UE CONTEXT RESPONSE. The gNB then sends a message to move the UE to INACTIVE state. The gNB sends an Xn-U ADDRESS INDICATION to the AMF, followed by a PATH SWITCH REQUEST. The AMF responds with PATH SWITCH REQUEST RESPONSE. The gNB sends an RRCRelease with Suspend Indication to the UE. Finally, the gNB sends a UE CONTEXT RELEASE to the Last Serving gNB.](9c45844d796e85ae05505870a54e4eb4_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB + participant Last Serving gNB + participant AMF + Note left of UE: UE in RRC_INACTIVE CM-CONNECTED + UE->>gNB: 1. RRCResumeRequest + gNB->>Last Serving gNB: 2. RETRIEVE UE CONTEXT REQUEST + Last Serving gNB-->>gNB: 3. RETRIEVE UE CONTEXT RESPONSE + gNB->>UE: 4. Send UE to INACTIVE + gNB-->>AMF: 5. Xn-U ADDRESS INDICATION + gNB->>AMF: 6. PATH SWITCH REQUEST + AMF-->>gNB: 7. PATH SWITCH REQUEST RESPONSE + gNB->>UE: 8. RRCRelease +Suspend Indication + gNB->>Last Serving gNB: 9. UE CONTEXT RELEASE + +``` + +Sequence diagram for Resume request responded with Release with Redirect, with UE Context relocation. The diagram shows interactions between UE, gNB, Last Serving gNB, and AMF. The UE sends an RRCResumeRequest. The gNB sends a RETRIEVE UE CONTEXT REQUEST to the Last Serving gNB, which responds with RETRIEVE UE CONTEXT RESPONSE. The gNB then sends a message to move the UE to INACTIVE state. The gNB sends an Xn-U ADDRESS INDICATION to the AMF, followed by a PATH SWITCH REQUEST. The AMF responds with PATH SWITCH REQUEST RESPONSE. The gNB sends an RRCRelease with Suspend Indication to the UE. Finally, the gNB sends a UE CONTEXT RELEASE to the Last Serving gNB. + +**Figure 9.2.2.6-1: Resume request responded with Release with Redirect, with UE Context relocation** + +1. The UE resumes from RRC\_INACTIVE, providing the I-RNTI allocated by the last serving gNB. +2. The gNB, if able to resolve the gNB identity contained in the I-RNTI, requests the last serving gNB to provide UE Context data. +3. The last serving gNB provides the UE context. +4. The gNB may move the UE to RRC\_CONNECTED (and the procedure follows step 4 of Figure 9.2.2.4.1-1), or send the UE back to RRC\_IDLE (in which case an *RRCRelease* message is sent by the gNB), or send the UE back to RRC\_INACTIVE, including a release with redirect indication (as assumed in the following). +5. If loss of DL user data buffered in the last serving gNB shall be prevented, the gNB provides forwarding addresses. +- 6./7. The gNB performs path switch. +8. The gNB keeps the UE in RRC\_INACTIVE state by sending *RRCRelease* with suspend indication, including redirection information (frequency layer the UE performs cell selection upon entering RRC\_INACTIVE). +9. The gNB triggers the release of the UE resources at the last serving gNB. + +NOTE1: Upon receiving the release with redirect, the higher layers trigger a pending procedure so the UE tries to resume again after cell selection. + +## 9.2.3 Mobility in RRC\_CONNECTED + +### 9.2.3.1 Overview + +Network controlled mobility applies to UEs in RRC\_CONNECTED and is categorized into two types of mobility: cell level mobility and beam level mobility. Beam level mobility includes intra-cell beam level mobility and inter-cell beam level mobility. + +**Cell Level Mobility** requires explicit RRC signalling to be triggered, i.e. handover. For inter-gNB handover, the signalling procedures consist of at least the following elemental components illustrated in Figure 9.2.3.1-1: + +![Sequence diagram of Inter-gNB handover procedures. The diagram shows three main entities: UE, Source gNB, and Target gNB. The sequence of messages is: 1. HANDOVER REQUEST from Source gNB to Target gNB; 2. HANDOVER REQUEST ACKNOWLEDGE from Target gNB (via Admission Control) to Source gNB; 3. RRCReconfiguration from Source gNB to UE; 4. RRCReconfigurationComplete from UE to Target gNB. A 'Switch to New Cell' box is shown on the UE side between steps 3 and 4.](49fe8fe978c0f7e73112d231feb377eb_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Source gNB + participant Target gNB + Note right of Target gNB: Admission Control + Source gNB->>Target gNB: 1. HANDOVER REQUEST + Target gNB->>Source gNB: 2. HANDOVER REQUEST ACKNOWLEDGE + Source gNB->>UE: 3. RRCReconfiguration + Note left of UE: Switch to New Cell + UE->>Target gNB: 4. RRCReconfigurationComplete + +``` + +Sequence diagram of Inter-gNB handover procedures. The diagram shows three main entities: UE, Source gNB, and Target gNB. The sequence of messages is: 1. HANDOVER REQUEST from Source gNB to Target gNB; 2. HANDOVER REQUEST ACKNOWLEDGE from Target gNB (via Admission Control) to Source gNB; 3. RRCReconfiguration from Source gNB to UE; 4. RRCReconfigurationComplete from UE to Target gNB. A 'Switch to New Cell' box is shown on the UE side between steps 3 and 4. + +**Figure 9.2.3.1-1: Inter-gNB handover procedures** + +1. The source gNB initiates handover and issues a HANDOVER REQUEST over the Xn interface. +2. The target gNB performs admission control and provides the new RRC configuration as part of the HANDOVER REQUEST ACKNOWLEDGE. +3. The source gNB provides the RRC configuration to the UE by forwarding the *RRCReconfiguration* message received in the HANDOVER REQUEST ACKNOWLEDGE. The *RRCReconfiguration* message includes at least cell ID and all information required to access the target cell so that the UE can access the target cell without reading system information. For some cases, the information required for contention-based and contention-free random access can be included in the *RRCReconfiguration* message. The access information to the target cell may include beam specific information, if any. +4. The UE moves the RRC connection to the target gNB and replies with the *RRCReconfigurationComplete*. + +NOTE 1: User Data can also be sent in step 4 if the grant allows. + +In case of DAPS handover, the UE continues the downlink user data reception from the source gNB until releasing the source cell and continues the uplink user data transmission to the source gNB until successful random access procedure to the target gNB. + +Only source and target PCell are used during DAPS handover. CA, DC, SUL, multi-TRP, EHC, CHO, UDC, NR sidelink configurations and V2X sidelink configurations are released by the source gNB before the handover command is sent to the UE and are not configured by the target gNB until the DAPS handover has completed (i.e. at earliest in the same message that releases the source PCell). + +The handover mechanism triggered by RRC requires the UE at least to reset the MAC entity and re-establish RLC, except for DAPS handover, where upon reception of the handover command, the UE: + +- Creates a MAC entity for target; +- Establishes the RLC entity and an associated DTCH logical channel for target for each DRB configured with DAPS; +- For each DRB configured with DAPS, reconfigures the PDCP entity with separate security and ROHC functions for source and target and associates them with the RLC entities configured by source and target respectively; +- Retains the rest of the source configurations until release of the source. + +The cell switch mechanism triggered by MAC, (i.e., LTM cell switch) requires the UE at least to reset the MAC entity. RLC handling depends on the network configuration. + +NOTE 2: Void. + +NOTE 3: Void. + +RRC managed handovers with and without PDCP entity re-establishment are both supported. For DRBs using RLC AM mode, PDCP can either be re-established together with a security key change or initiate a data recovery procedure without a key change. For DRBs using RLC UM mode, PDCP can either be re-established together with a security key + +change or remain as it is without a key change. For SRBs, PDCP can either remain as it is, discard its stored PDCP PDUs/SDUs without a key change or be re-established together with a security key change. + +Data forwarding, in-sequence delivery and duplication avoidance at handover can be guaranteed when the target gNB uses the same DRB configuration as the source gNB. + +Timer based handover failure procedure is supported in NR. RRC connection re-establishment procedure is used for recovering from handover failure except in certain CHO, DAPS handover or LTM cell switch scenarios: + +- When DAPS handover fails, the UE falls back to the source cell configuration, resumes the connection with the source cell, and reports DAPS handover failure via the source without triggering RRC connection re-establishment if the source link has not been released. +- When initial CHO execution attempt fails or HO fails, the UE performs cell selection, and if the selected cell is a CHO candidate and if network configured the UE to try CHO after handover/CHO failure, then the UE attempts CHO execution once, otherwise re-establishment is performed. +- When initial LTM execution attempt fails or HO fails, the UE performs cell selection and if the selected cell is an LTM candidate cell and if network configured the UE to try LTM after LTM execution failure, then the UE attempts LTM execution once, otherwise re-establishment is performed. + +DAPS handover for FR2 to FR2 case is not supported in this release of the specification. + +The handover of the IAB-MT in SA mode follows the same procedure as described for the UE. After the backhaul has been established, the handover of the IAB-MT is part of the intra-CU or inter-CU topology adaptation procedures defined in TS 38.401 [4]. Modifications to the configuration of BAP sublayer and higher protocol layers above the BAP sublayer are described in TS 38.401 [4]. + +The handover of the mobile IAB-MT follows the same procedure as described for the UE. After the backhaul has been established, the handover of the mobile IAB-MT is part of the mobile IAB-MT migration procedure defined in TS 38.401 [4]. + +**Beam Level Mobility** does not require explicit RRC signalling to be triggered. Beam level mobility can be within a cell, or between cells, the latter is referred to as inter-cell beam management (ICBM). For ICBM, a UE can receive or transmit UE dedicated channels/signals via a TRP associated with a PCI different from the PCI of a serving cell, while non-UE-dedicated channels/signals can only be received via a TRP associated with a PCI of the serving cell. The gNB provides via RRC signalling the UE with measurement configuration containing configurations of SSB/CSI resources and resource sets, reports and trigger states for triggering channel and interference measurements and reports. In case of ICBM, a measurement configuration includes SSB resources associated with PCIs different from the PCI of a serving cell. Beam Level Mobility is then dealt with at lower layers by means of physical layer and MAC layer control signalling, and RRC is not required to know which beam is being used at a given point in time. + +SSB-based Beam Level Mobility is based on the CD-SSB associated to the initial DL BWP and can be configured for the initial DL BWPs, for DL BWPs containing the CD-SSB associated to the initial DL BWP, and if supported, for DL BWPs not containing the CD-SSB associated to the initial DL BWP. SSB-based Beam Level Mobility can be also performed based on an NCD-SSB, if configured for the active DL BWP. For other DL BWPs, Beam Level Mobility can only be performed based on CSI-RS, if configured for the active DL BWP. + +## 9.2.3.2 Handover + +### 9.2.3.2.1 C-Plane Handling + +The intra-NR RAN handover performs the preparation and execution phase of the handover procedure performed without involvement of the 5GC, i.e. preparation messages are directly exchanged between the gNBs. The release of the resources at the source gNB during the handover completion phase is triggered by the target gNB. The figure below depicts the basic handover scenario where neither the AMF nor the UPF changes: + +![Sequence diagram for Intra-AMF/UPF Handover. Lifelines: UE, Source gNB, Target gNB, AMF, UPF(s). The process is divided into three phases: Handover Preparation, Handover Execution, and Handover Completion. The diagram shows the flow of user data, mobility control information, and various signaling messages between the entities.](750b1652a4f4791b84c02aa755a1dedd_img.jpg) + +The sequence diagram illustrates the Intra-AMF/UPF Handover process. The lifelines involved are UE, Source gNB, Target gNB, AMF, and UPF(s). The process is divided into three main phases: Handover Preparation, Handover Execution, and Handover Completion. + +- Handover Preparation:** + - 0. Mobility control information provided by AMF: AMF provides mobility control information to the Source gNB. + - 1. Measurement Control and Reports: Source gNB configures measurement procedures for the UE, and the UE reports measurements. + - 2. Handover Decision: Source gNB makes a handover decision based on measurement reports and RRM information. + - 3. HANDOVER REQUEST: Source gNB sends a HANDOVER REQUEST to the Target gNB. + - 4. Admission Control: Target gNB performs admission control. + - 5. HANDOVER REQUEST ACKNOWLEDGE: Target gNB sends a HANDOVER REQUEST ACKNOWLEDGE to the Source gNB. +- Handover Execution:** + - 6. RAN Handover Initiation: Source gNB initiates RAN handover to the UE. + - Detach from old cell / Synchronise to new cell: UE detaches from the old cell and synchronizes to the new cell. + - Deliver buffered data and new data from UPF(s): Source gNB receives buffered and new data from the UPF(s). + - 7a. EARLY STATUS TRANSFER: Source gNB sends EARLY STATUS TRANSFER to the Target gNB. + - 7. SN STATUS TRANSFER: Source gNB sends SN STATUS TRANSFER to the Target gNB. + - User Data: User data is transferred from the UPF(s) to the Target gNB. + - Buffer User Data from Source gNB: Source gNB buffers user data for the Target gNB. +- Handover Completion:** + - 8. RAN Handover Completion: Source gNB completes RAN handover with the UE. + - 8a. HANDOVER SUCCESS: Source gNB sends HANDOVER SUCCESS to the Target gNB. + - 8b. SN STATUS TRANSFER: Source gNB sends SN STATUS TRANSFER to the Target gNB. + - User Data: User data is transferred from the Source gNB to the Target gNB. + - 9. PATH SWITCH REQUEST: Target gNB sends a PATH SWITCH REQUEST to the AMF. + - 10. Path Switch in UPF(s): AMF performs a path switch in the UPF(s). + - End Marker: AMF sends an End Marker to the Target gNB. + - User Data: User data is transferred from the UPF(s) to the Target gNB. + - 11. PATH SWITCH REQUEST ACKNOWLEDGE: AMF sends a PATH SWITCH REQUEST ACKNOWLEDGE to the Target gNB. + - 12. UE CONTEXT RELEASE: Target gNB sends a UE CONTEXT RELEASE to the Source gNB. + + v6.3.7 + +Sequence diagram for Intra-AMF/UPF Handover. Lifelines: UE, Source gNB, Target gNB, AMF, UPF(s). The process is divided into three phases: Handover Preparation, Handover Execution, and Handover Completion. The diagram shows the flow of user data, mobility control information, and various signaling messages between the entities. + +Figure 9.2.3.2.1-1: Intra-AMF/UPF Handover + +0. The UE context within the source gNB contains information regarding roaming and access restrictions which were provided either at connection establishment or at the last TA update. +1. The source gNB configures the UE measurement procedures and the UE reports according to the measurement configuration. +2. The source gNB decides to handover the UE, based on *MeasurementReport* and RRM information. + +3. The source gNB issues a Handover Request message to the target gNB passing a transparent RRC container with necessary information to prepare the handover at the target side. The information includes at least the target cell ID, KgNB\*, the C-RNTI of the UE in the source gNB, RRM-configuration including UE inactive time, basic AS-configuration including *antenna Info and DL Carrier Frequency*, the current QoS flow to DRB mapping rules applied to the UE, the SIB1 information from source gNB, the UE capabilities for different RATs, PDU session related information, and can include the UE reported measurement information including beam-related information if available. The PDU session related information includes the slice information and QoS flow level QoS profile(s). The source gNB may also request a DAPS handover for one or more DRBs. + +NOTE 1: After issuing a Handover Request, the source gNB should not reconfigure the UE, including performing Reflective QoS flow to DRB mapping. + +4. Admission Control may be performed by the target gNB. Slice-aware admission control shall be performed if the slice information is sent to the target gNB. If the PDU sessions are associated with non-supported slices the target gNB shall reject such PDU Sessions. +5. The target gNB prepares the handover with L1/L2 and sends the HANDOVER REQUEST ACKNOWLEDGE to the source gNB, which includes a transparent container to be sent to the UE as an RRC message to perform the handover. The target gNB also indicates if a DAPS handover is accepted. + +NOTE 2: As soon as the source gNB receives the HANDOVER REQUEST ACKNOWLEDGE, or as soon as the transmission of the handover command is initiated in the downlink, data forwarding may be initiated. + +NOTE 3: For DRBs configured with DAPS, downlink PDCP SDUs are forwarded with SN assigned by the source gNB, until SN assignment is handed over to the target gNB in step 8b, for which the normal data forwarding follows as defined in 9.2.3.2.3. + +6. The source gNB triggers the Uu handover by sending an *RRCReconfiguration* message to the UE, containing the information required to access the target cell: at least the target cell ID, the new C-RNTI, the target gNB security algorithm identifiers for the selected security algorithms. It can also include a set of dedicated RACH resources, the association between RACH resources and SSB(s), the association between RACH resources and UE-specific CSI-RS configuration(s), common RACH resources, and system information of the target cell, etc. + +NOTE 4: For DRBs configured with DAPS, the source gNB does not stop transmitting downlink packets until it receives the HANDOVER SUCCESS message from the target gNB in step 8a. + +NOTE 4a: CHO cannot be configured simultaneously with DAPS handover. + +- 7a. For DRBs configured with DAPS, the source gNB sends the EARLY STATUS TRANSFER message. The DL COUNT value conveyed in the EARLY STATUS TRANSFER message indicates PDCP SN and HFN of the first PDCP SDU that the source gNB forwards to the target gNB. The source gNB does not stop assigning SNs to downlink PDCP SDUs until it sends the SN STATUS TRANSFER message to the target gNB in step 8b. +7. For DRBs not configured with DAPS, the source gNB sends the SN STATUS TRANSFER message to the target gNB to convey the uplink PDCP SN receiver status and the downlink PDCP SN transmitter status of DRBs for which PDCP status preservation applies (i.e. for RLC AM). The uplink PDCP SN receiver status includes at least the PDCP SN of the first missing UL PDCP SDU and may include a bit map of the receive status of the out of sequence UL PDCP SDUs that the UE needs to retransmit in the target cell, if any. The downlink PDCP SN transmitter status indicates the next PDCP SN that the target gNB shall assign to new PDCP SDUs, not having a PDCP SN yet. + +NOTE 5: In case of DAPS handover, the uplink PDCP SN receiver status and the downlink PDCP SN transmitter status for a DRB with RLC-AM and not configured with DAPS may be transferred by the SN STATUS TRANSFER message in step 8b instead of step 7. + +NOTE 6: For DRBs configured with DAPS, the source gNB may additionally send the EARLY STATUS TRANSFER message(s) between step 7 and step 8b, to inform discarding of already forwarded PDCP SDUs. The target gNB does not transmit forwarded downlink PDCP SDUs to the UE, whose COUNT is less than the conveyed DL COUNT value and discards them if transmission has not been attempted already. + +8. The UE synchronises to the target cell and completes the RRC handover procedure by sending *RRCReconfigurationComplete* message to target gNB. In case of DAPS handover, the UE does not detach from the source cell upon receiving the *RRCReconfiguration* message. The UE releases the source resources and + +configurations and stops DL/UL reception/transmission with the source upon receiving an explicit release from the target node. + +NOTE 6a: From RAN point of view, the DAPS handover is considered to only be completed after the UE has released the source cell as explicitly requested from the target node. RRC suspend, a subsequent handover or inter-RAT handover cannot be initiated until the source cell has been released. + +8a/b In case of DAPS handover, the target gNB sends the HANDOVER SUCCESS message to the source gNB to inform that the UE has successfully accessed the target cell. In return, the source gNB sends the SN STATUS TRANSFER message for DRBs configured with DAPS for which the description in step 7 applies, and the normal data forwarding follows as defined in 9.2.3.2.3. + +NOTE 7: The uplink PDCP SN receiver status and the downlink PDCP SN transmitter status are also conveyed for DRBs with RLC-UM in the SN STATUS TRANSFER message in step 8b, if configured with DAPS. + +NOTE 8: For DRBs configured with DAPS, the source gNB does not stop delivering uplink QoS flows to the UPF until it sends the SN STATUS TRANSFER message in step 8b. The target gNB does not forward QoS flows of the uplink PDCP SDUs successfully received in-sequence to the UPF until it receives the SN STATUS TRANSFER message, in which UL HFN and the first missing SN in the uplink PDCP SN receiver status indicates the start of uplink PDCP SDUs to be delivered to the UPF. The target gNB does not deliver any uplink PDCP SDUs which has an UL COUNT lower than the provided. + +NOTE 9: Void. + +9. The target gNB sends a PATH SWITCH REQUEST message to AMF to trigger 5GC to switch the DL data path towards the target gNB and to establish an NG-C interface instance towards the target gNB. + +10. 5GC switches the DL data path towards the target gNB. The UPF sends one or more "end marker" packets on the old path to the source gNB per PDU session/tunnel and then can release any U-plane/TNL resources towards the source gNB. + +11. The AMF confirms the PATH SWITCH REQUEST message with the PATH SWITCH REQUEST ACKNOWLEDGE message. + +12. Upon reception of the PATH SWITCH REQUEST ACKNOWLEDGE message from the AMF, the target gNB sends the UE CONTEXT RELEASE to inform the source gNB about the success of the handover. The source gNB can then release radio and C-plane related resources associated to the UE context. Any ongoing data forwarding may continue. + +The RRM configuration can include both beam measurement information (for layer 3 mobility) associated to SSB(s) and CSI-RS(s) for the reported cell(s) if both types of measurements are available. Also, if CA is configured, the RRM configuration can include the list of best cells on each frequency for which measurement information is available. And the RRM measurement information can also include the beam measurement for the listed cells that belong to the target gNB. + +The common RACH configuration for beams in the target cell is only associated to the SSB(s). The network can have dedicated RACH configurations associated to the SSB(s) and/or have dedicated RACH configurations associated to CSI-RS(s) within a cell. The target gNB can only include one of the following RACH configurations in the Handover Command to enable the UE to access the target cell: + +- i) Common RACH configuration; +- ii) Common RACH configuration + Dedicated RACH configuration associated with SSB; +- iii) Common RACH configuration + Dedicated RACH configuration associated with CSI-RS. + +The dedicated RACH configuration allocates RACH resource(s) together with a quality threshold to use them. When dedicated RACH resources are provided, they are prioritized by the UE and the UE shall not switch to contention-based RACH resources as long as the quality threshold of those dedicated resources is met. The order to access the dedicated RACH resources is up to UE implementation. + +Upon receiving a handover command requesting DAPS handover, the UE suspends source cell SRBs, stops sending and receiving any RRC control plane signalling toward the source cell, and establishes SRBs for the target cell. The UE releases the source cell SRBs configuration upon receiving source cell release indication from the target cell after successful DAPS handover execution. When DAPS handover to the target cell fails and if the source cell link is + +available, then the UE reverts back to the source cell configuration and resumes source cell SRBs for control plane signalling transmission. + +#### 9.2.3.2.2 U-Plane Handling + +The U-plane handling during the Intra-NR-Access mobility activity for UEs in RRC\_CONNECTED takes the following principles into account to avoid data loss during HO: + +- During HO preparation, U-plane tunnels can be established between the source gNB and the target gNB; +- During HO execution, user data can be forwarded from the source gNB to the target gNB; + - Forwarding should take place in order as long as packets are received at the source gNB from the UPF or the source gNB buffer has not been emptied. +- During HO completion: + - The target gNB sends a path switch request message to the AMF to inform that the UE has gained access and the AMF then triggers path switch related 5GC internal signalling and actual path switch of the source gNB to the target gNB in UPF; + - The source gNB should continue forwarding data as long as packets are received at the source gNB from the UPF or the source gNB buffer has not been emptied. + +##### For RLC-AM bearers: + +- For in-sequence delivery and duplication avoidance, PDCP SN is maintained on a per DRB basis and the source gNB informs the target gNB about the next DL PDCP SN to allocate to a packet which does not have a PDCP sequence number yet (either from source gNB or from the UPF). +- For security synchronisation, HFN is also maintained and the source gNB provides to the target one reference HFN for the UL and one for the DL i.e. HFN and corresponding SN. +- In both the UE and the target gNB, a window-based mechanism is used for duplication detection and reordering. +- The occurrence of duplicates over the air interface in the target gNB is minimised by means of PDCP SN based reporting at the target gNB by the UE. In uplink, the reporting is optionally configured on a per DRB basis by the gNB and the UE should first start by transmitting those reports when granted resources are in the target gNB. In downlink, the gNB is free to decide when and for which bearers a report is sent and the UE does not wait for the report to resume uplink transmission. +- The target gNB re-transmits and prioritizes all downlink data forwarded by the source gNB (i.e. the target gNB should first send all forwarded PDCP SDUs with PDCP SNs, then all forwarded downlink PDCP SDUs without SNs before sending new data from 5GC), excluding PDCP SDUs for which the reception was acknowledged through PDCP SN based reporting by the UE. + +NOTE 1: Lossless delivery when a QoS flow is mapped to a different DRB at handover, requires the old DRB to be configured in the target cell. For in-order delivery in the DL, the target gNB should first transmit the forwarded PDCP SDUs on the old DRB before transmitting new data from 5GC on the new DRB. In the UL, the target gNB should not deliver data of the QoS flow from the new DRB to 5GC before receiving the end marker on the old DRB from the UE. + +- The UE re-transmits in the target gNB all uplink PDCP SDUs starting from the oldest PDCP SDU that has not been acknowledged at RLC in the source, excluding PDCP SDUs for which the reception was acknowledged through PDCP SN based reporting by the target. +- In case of handovers involving Full Configuration, the following description below for RLC-UM bearers applies for RLC-AM bearers instead. Data loss may happen. + +##### For RLC-UM bearers: + +- The PDCP SN and HFN are reset in the target gNB, unless the bearer is configured with DAPS handover; +- No PDCP SDUs are retransmitted in the target gNB; + +- The target gNB prioritises all downlink SDAP SDUs forwarded by the source gNB over the data from the core network; + +NOTE 2: To minimise losses when a QoS flow is mapped to a different DRB at handover, the old DRB needs to be configured in the target cell. For in-order delivery in the DL, the target gNB should first transmit the forwarded PDCP SDUs on the old DRB before transmitting new data from 5GC on the new DRB. In the UL, the target gNB should not deliver data of the QoS flow from the new DRB to 5GC before receiving the end marker on the old DRB from the UE. + +- The UE does not retransmit any PDCP SDU in the target cell for which transmission had been completed in the source cell. + +#### For DAPS handover: + +A DAPS handover can be used for an RLC-AM or RLC-UM bearer. For a DRB configured with DAPS, the following principles are additionally applied. + +##### Downlink: + +- During HO preparation, a forwarding tunnel is always established. +- The source gNB is responsible for allocating downlink PDCP SNs until the SN assignment is handed over to the target gNB and data forwarding in 9.2.3.2.3 takes place. That is, the source gNB does not stop assigning PDCP SNs to downlink packets until it receives the HANDOVER SUCCESS message and sends the SN STATUS TRANSFER message to the target gNB. +- Upon allocation of downlink PDCP SNs by the source gNB, it starts scheduling downlink data on the source radio link and also starts forwarding downlink PDCP SDUs along with assigned PDCP SNs to the target gNB. +- For security synchronisation, HFN is maintained for the forwarded downlink SDUs with PDCP SNs assigned by the source gNB. The source gNB sends the EARLY STATUS TRANSFER message to convey the DL COUNT value, indicating PDCP SN and HFN of the first PDCP SDU that the source gNB forwards to the target gNB. +- HFN and PDCP SN are maintained after the SN assignment is handed over to the target gNB. The SN STATUS TRANSFER message indicates the next DL PDCP SN to allocate to a packet which does not have a PDCP sequence number yet, even for RLC-UM. +- During handover execution period, the source and target gNBs separately perform ROHC header compression, ciphering, and adding PDCP header. +- During handover execution period, the UE continues to receive downlink data from both source and target gNBs until the source gNB connection is released by an explicit release command from the target gNB. +- During handover execution period, the UE PDCP entity configured with DAPS maintains separate security and ROHC header decompression functions associated with each gNB, while maintaining common functions for reordering, duplicate detection and discard, and PDCP SDUs in-sequence delivery to upper layers. PDCP SN continuity is supported for both RLC AM and UM DRBs configured with DAPS. + +##### Uplink: + +- The UE transmits UL data to the source gNB until the random access procedure toward the target gNB has been successfully completed. Afterwards the UE switches its UL data transmission to the target gNB. +- Even after switching its UL data transmissions towards the target gNB, the UE continues to send UL layer 1 CSI feedback, HARQ feedback, layer 2 RLC feedback, ROHC feedback, HARQ data (re-)transmissions, and RLC data (re-)transmissions to the source gNB. +- During handover execution period, the UE maintains separate security context and ROHC header compressor context for uplink transmissions towards the source and target gNBs. The UE maintains common UL PDCP SN allocation. PDCP SN continuity is supported for both RLC AM and UM DRBs configured with DAPS. +- During handover execution period, the source and target gNBs maintain their own security and ROHC header decompressor contexts to process UL data received from the UE. +- The establishment of a forwarding tunnel is optional. + +- HFN and PDCP SN are maintained in the target gNB. The SN STATUS TRANSFER message indicates the COUNT of the first missing PDCP SDU that the target should start delivering to the 5GC, even for RLC-UM. + +### 9.2.3.2.3 Data Forwarding + +The following description depicts the data forwarding principles for intra-system handover. + +The source NG-RAN node may suggest downlink data forwarding per QoS flow established for a PDU session and may provide information how it maps QoS flows to DRBs. The target NG-RAN node decides data forwarding per QoS flow established for a PDU Session. + +If "lossless handover" is required and the QoS flows to DRB mapping applied at the target NG-RAN node allows applying for data forwarding the same QoS flows to DRB mapping as applied at the source NG-RAN node for a DRB and if all QoS flows mapped to that DRB are accepted for data forwarding, the target NG-RAN node establishes a downlink forwarding tunnel for that DRB. + +For a DRB for which preservation of SN status applies, the target NG-RAN node may decide to establish an UL data forwarding tunnel. + +The target NG-RAN node may also decide to establish a downlink forwarding tunnel for each PDU session. In this case the target NG-RAN node provides information for which QoS flows data forwarding has been accepted and corresponding UP TNL information for data forwarding tunnels to be established between the source NG-RAN node and the target NG-RAN node. + +If QoS flows have been re-mapped at the source NG-RAN node and user packets along the old source mapping are still being processed at handover preparation, and if the source NG-RAN node has not yet received the SDAP end marker for certain QoS flows when providing the SN status to the target NG-RAN node, the source NG-RAN node provides the old side QoS mapping information for UL QoS flows to the target NG-RAN node for which no SDAP end marker was yet received. The target NG-RAN will receive for those QoS flows the end marker when the UE finalises to send UL user data according to the old source side mapping. + +The source NG-RAN node may also propose to establish uplink forwarding tunnels for some PDU sessions in order to transfer SDAP SDUs corresponding to QoS flows for which flow re-mapping happened before the handover and the SDAP end marker has not yet been received, and for which user data was received at the source NG-RAN node via the DRB to which the QoS flow was remapped. If accepted the target NG-RAN node shall provide the corresponding UP TNL information for data forwarding tunnels to be established between the source NG-RAN node and the target NG-RAN node. + +As long as data forwarding of DL user data packets takes place, the source NG-RAN node shall forward user data in the same forwarding tunnel, i.e. + +- for any QoS flow accepted for data forwarding by the target NG-RAN node and for which a DRB DL forwarding tunnel was established for a DRB to which this QoS flow was mapped at the source NG-RAN node, any fresh packets of this QoS flow shall be forwarded as PDCP SDUs via the mapped DRB DL forwarding tunnel. +- for DRBs for which preservation of SN status applies, the source NG-RAN node may forward in order to the target NG-RAN node via the DRB DL forwarding tunnel all downlink PDCP SDUs with their SN corresponding to PDCP PDUs which have not been acknowledged by the UE. + +NOTE: The SN of forwarded PDCP SDUs is carried in the "PDCP PDU number" field of the GTP-U extension header. + +- for any QoS flow accepted for data forwarding by the target NG-RAN node for which a DL PDU session forwarding tunnel was established, the source NG-RAN node forwards SDAP SDUs as received on NG-U from the UPF. + +For handovers involving Full Configuration, the source NG-RAN node behaviour is unchanged from the description above. In case a DRB DL forwarding tunnel was established, the target NG-RAN node may identify the PDCP SDUs for which delivery was attempted by the source NG-RAN node, by the presence of the PDCP SN in the forwarded GTP-U packet and may discard them. + +As long as data forwarding of UL user data packets takes place for DRBs for which preservation of SN status applies the source NG-RAN node either: + +- discards the uplink PDCP PDUs received out of sequence if the source NG-RAN node has not accepted the request from the target NG-RAN node for uplink forwarding or if the target NG-RAN node has not requested uplink forwarding for the bearer during the Handover Preparation procedure; or +- forwards to the target NG-RAN node via the corresponding DRB UL forwarding tunnel, the uplink PDCP SDUs with their SN corresponding to PDCP PDUs received out of sequence if the source NG-RAN node has accepted the request from the target NG-RAN node for uplink forwarding for the bearer during the Handover Preparation procedure, including PDCP SDUs corresponding to user data of those QoS flows, for which re-mapping happened for a QoS flow before the handover and the SDAP end marker has not yet been received at the source NG-RAN node. + +As long as data forwarding of UL user data packets takes place for a PDU session, the source NG-RAN node forwards via the corresponding PDU session UL forwarding tunnel, the uplink SDAP SDUs corresponding to QoS flows for which flow re-mapping happened before the handover and the SDAP end marker has not yet been received at the source NG-RAN node, and which were received at the source NG-RAN node via the DRB to which the QoS flow was remapped. + +For DRBs configured with DAPS handover, data forwarding after the source gNB receives the HANDOVER SUCCESS message from the target gNB follows the same behaviours as described above. + +For DRBs configured with DAPS handover, before the source gNB receives the HANDOVER SUCCESS message: + +- The source gNB may forward to the target gNB downlink PDCP SDUs with SNs assigned by the source gNB. No downlink PDCP SDU without a SN assigned or SDAP SDU is forwarded. No uplink PDCP SDU or SDAP SDU is forwarded. +- The source gNB sends the EARLY STATUS TRANSFER message to maintain HFN continuity by indicating PDCP SN and HFN of the first PDCP SDU that the source gNB forwards to the target gNB. The subsequent messages may be sent for discarding of already forwarded downlink PDCP SDUs in the target gNB. +- The source gNB does not stop transmitting downlink packets to the UE. The source gNB keeps forwarding to the 5GC the uplink SDAP SDUs successfully received in-sequence from the UE. + +Handling of end marker packets: + +- The source NG-RAN node receives one or several GTP-U end marker packets per PDU session from the UPF and replicates the end marker packets into each data forwarding tunnel when no more user data packets are to be forwarded over that tunnel. +- End marker packets sent via a data forwarding tunnel are applicable to all QoS flows forwarded via that tunnel. After end marker packets have been received over a forwarding tunnel, the target NG-RAN node can start taking into account the packets of QoS flows associated with that forwarding tunnel received at the target NG-RAN node from the NG-U PDU session tunnel. + +### 9.2.3.3 Re-establishment procedure + +A UE in RRC\_CONNECTED may initiate the re-establishment procedure to continue the RRC connection when a failure condition occurs (e.g. radio link failure, reconfiguration failure, integrity check failure...). + +The following figure describes the re-establishment procedure started by the UE: + +![Sequence diagram of the Re-establishment procedure. Lifelines: UE, gNB, Last Serving gNB, AMF. The UE sends an RRCReestablishmentRequest to the gNB. The gNB sends a RETRIEVE UE CONTEXT REQUEST to the Last Serving gNB, which responds with RETRIEVE UE CONTEXT RESPONSE. The gNB then sends RRCReestablishment and RRCReconfiguration to the UE. The UE responds with RRCReestablishmentComplete and RRCReconfigurationComplete. The gNB sends XN-U ADDRESS INDICATION and SN STATUS TRANSFER to the Last Serving gNB. The gNB sends a PATH SWITCH REQUEST to the AMF, which responds with PATH SWITCH REQUEST RESPONSE. Finally, the gNB sends a UE CONTEXT RELEASE to the Last Serving gNB.](18003425d0e8638dde4acc9c5c468c5c_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB + participant Last Serving gNB + participant AMF + + Note left of UE: UE in RRC_CONNECTED +CM-CONNECTED + + UE->>gNB: 1. RRCReestablishmentRequest + gNB->>Last Serving gNB: 2. RETRIEVE UE CONTEXT REQUEST + Last Serving gNB-->>gNB: 3. RETRIEVE UE CONTEXT RESPONSE + gNB->>UE: 4. RRCReestablishment + gNB-->>UE: 5. RRCReconfiguration + UE-->>gNB: 4a. RRCReestablishmentComplete + UE-->>gNB: 5a. RRCReconfigurationComplete + gNB-->>Last Serving gNB: 6. XN-U ADDRESS INDICATION + gNB-->>Last Serving gNB: 7. SN STATUS TRANSFER + gNB->>AMF: 8. PATH SWITCH REQUEST + AMF-->>gNB: 9. PATH SWITCH REQUEST RESPONSE + gNB-->>Last Serving gNB: 10. UE CONTEXT RELEASE + +``` + +Sequence diagram of the Re-establishment procedure. Lifelines: UE, gNB, Last Serving gNB, AMF. The UE sends an RRCReestablishmentRequest to the gNB. The gNB sends a RETRIEVE UE CONTEXT REQUEST to the Last Serving gNB, which responds with RETRIEVE UE CONTEXT RESPONSE. The gNB then sends RRCReestablishment and RRCReconfiguration to the UE. The UE responds with RRCReestablishmentComplete and RRCReconfigurationComplete. The gNB sends XN-U ADDRESS INDICATION and SN STATUS TRANSFER to the Last Serving gNB. The gNB sends a PATH SWITCH REQUEST to the AMF, which responds with PATH SWITCH REQUEST RESPONSE. Finally, the gNB sends a UE CONTEXT RELEASE to the Last Serving gNB. + +**Figure 9.2.3.3-1: Re-establishment procedure** + +1. The UE re-establishes the connection, providing the UE Identity (PCI+C-RNTI) to the gNB where the trigger for the re-establishment occurred. +2. If the UE Context is not locally available, the gNB, requests the last serving gNB to provide UE Context data. +3. The last serving gNB provides UE context data. +- 4/4a. The gNB continues the re-establishment of the RRC connection. The message is sent on SRB1. +- 5/5a. The gNB may perform the reconfiguration to re-establish SRB2 and DRBs when the re-establishment procedure is ongoing. +- 6/7. If loss of user data buffered in the last serving gNB shall be prevented, the gNB provides forwarding addresses, and the last serving gNB provides the SN status to the gNB. +- 8/9. The gNB performs path switch. +10. The gNB triggers the release of the UE resources at the last serving gNB. + +The IAB-MT in SA mode follows the same re-establishment procedure as described for the UE. After the backhaul has been established, the re-establishment procedure of the IAB-MT is part of the intra-CU backhaul RLF recovery procedure for IAB-nodes defined in TS 38.401 [4]. Modifications to the configuration of BAP sublayer and higher protocol layers above the BAP sublayer are described in TS 38.401 [4]. + +### 9.2.3.4 Conditional Handover + +#### 9.2.3.4.1 General + +A Conditional Handover (CHO) is defined as a handover that is executed by the UE when one or more handover execution conditions are met. The UE starts evaluating the execution condition(s) upon receiving the CHO configuration, and stops evaluating the execution condition(s) once a handover is executed. + +The following principles apply to CHO: + +- The CHO configuration contains the configuration of CHO candidate cell(s) generated by the candidate gNB(s) and execution condition(s) generated by the source gNB. +- An execution condition may consist of one or two trigger condition(s) (CHO events A3/A5, as defined in [12]). Only single RS type is supported and at most two different trigger quantities (e.g. RSRP and RSRQ, RSRP and SINR, etc.) can be configured simultaneously for the evaluation of CHO execution condition of a single candidate cell. +- Before any CHO execution condition is satisfied, upon reception of HO command (without CHO configuration), the UE executes the HO procedure as described in clause 9.2.3.2, regardless of any previously received CHO configuration. +- While executing CHO, i.e. from the time when the UE starts synchronization with target cell, UE does not monitor source cell. + +CHO is also supported for the IAB-MT in context of intra- and inter-donor IAB-node migration and BH RLF recovery. + +CHO is not supported for NG-C based handover in this release of the specification. + +#### 9.2.3.4.2 C-plane handling + +As in intra-NR RAN handover, in intra-NR RAN CHO, the preparation and execution phase of the conditional handover procedure is performed without involvement of the 5GC; i.e. preparation messages are directly exchanged between gNBs. The release of the resources at the source gNB during the conditional handover completion phase is triggered by the target gNB. The figure below depicts the basic conditional handover scenario where neither the AMF nor the UPF changes: + +![Sequence diagram for Intra-AMF/UPF Conditional Handover. Lifelines: UE, Source gNB, Target gNB, Other potential target gNB(s), AMF, UPF(s). The process is divided into three phases: Handover Preparation, Handover Execution, and Handover Completion. Steps include Measurement Control, CHO Decision, HO Request, Admission Control, RRC Reconfiguration, Early Status Transfer, and HO Success/Cancel messages.](ffe0fef452a0ae9a20253c319c54e13c_img.jpg) + +The sequence diagram illustrates the Intra-AMF/UPF Conditional Handover process. The lifelines involved are UE, Source gNB, Target gNB, Other potential target gNB(s), AMF, and UPF(s). The process is divided into three main phases: Handover Preparation, Handover Execution, and Handover Completion. + +- Handover Preparation:** + - 0. Mobility control information provided by AMF + - 1. Measurement Control and Reports (UE to Source gNB) + - 2. CHO Decision (Source gNB) + - 3. HANDOVER REQUEST (Source gNB to Target gNB and Other potential target gNB(s)) + - 4. Admission Control (Target gNB and Other potential target gNB(s)) + - 5. HANDOVER REQUEST ACKNOWLEDGE (Target gNB and Other potential target gNB(s) to Source gNB) +- Handover Execution:** + - 6. RRCReconfiguration (Source gNB to UE) + - UE actions: Evaluate the CHO conditions, Detach from the old cell, synchronize to the new cell. + - 7a. EARLY STATUS TRANSFER (Source gNB to Target gNB) + - User Data transfer between Source gNB and UPF(s) +- Handover Completion:** + - 8. CHO Handover completion (UE to Source gNB) + - 8a. HANDOVER SUCCESS (Source gNB to Target gNB) + - 8b. SN STATUS TRANSFER (Source gNB to Target gNB) + - User Data transfer between Source gNB and UPF(s) + - 8c. HANDOVER CANCEL (Source gNB to Other potential target gNB(s)) + +Figure 9.2.3.2.1-1 step 9-12 + + + +Sequence diagram for Intra-AMF/UPF Conditional Handover. Lifelines: UE, Source gNB, Target gNB, Other potential target gNB(s), AMF, UPF(s). The process is divided into three phases: Handover Preparation, Handover Execution, and Handover Completion. Steps include Measurement Control, CHO Decision, HO Request, Admission Control, RRC Reconfiguration, Early Status Transfer, and HO Success/Cancel messages. + +**Figure 9.2.3.4.2-1: Intra-AMF/UPF Conditional Handover** + +- 0/1. Same as step 0, 1 in Figure 9.2.3.2.1-1 of clause 9.2.3.2.1. +2. The source gNB decides to use CHO. +3. The source gNB requests CHO for one or more candidate cells belonging to one or more candidate gNBs. A CHO request message is sent for each candidate cell. +4. Same as step 4 in Figure 9.2.3.2.1-1 of clause 9.2.3.2.1. +5. The candidate gNB(s) sends CHO response (HO REQUEST ACKNOWLEDGE) including configuration of CHO candidate cell(s) to the source gNB. The CHO response message is sent for each candidate cell. +6. The source gNB sends an *RRCReconfiguration* message to the UE, containing the configuration of CHO candidate cell(s) and CHO execution condition(s). + +NOTE 1: CHO configuration of candidate cells can be followed by another reconfiguration from the source gNB. + +NOTE 1a: A configuration of a CHO candidate cell cannot contain a DAPS handover configuration. + +7. The UE sends an *RRCReconfigurationComplete* message to the source gNB. + +7a If early data forwarding is applied, the source gNB sends the EARLY STATUS TRANSFER message. + +8. The UE maintains connection with the source gNB after receiving CHO configuration, and starts evaluating the CHO execution conditions for the candidate cell(s). If at least one CHO candidate cell satisfies the corresponding CHO execution condition, the UE detaches from the source gNB, applies the stored corresponding configuration for that selected candidate cell, synchronises to that candidate cell and completes the RRC handover procedure by sending *RRCReconfigurationComplete* message to the target gNB. The UE releases stored CHO configurations after successful completion of RRC handover procedure. + +8a/b The target gNB sends the HANDOVER SUCCESS message to the source gNB to inform that the UE has successfully accessed the target cell. In return, the source gNB sends the SN STATUS TRANSFER message following the principles described in step 7 of Intra-AMF/UPF Handover in clause 9.2.3.2.1. + +NOTE 2: Late data forwarding may be initiated as soon as the source gNB receives the HANDOVER SUCCESS message. + +8c. The source gNB sends the HANDOVER CANCEL message toward the other signalling connections or other candidate target gNBs, if any, to cancel CHO for the UE. + +#### 9.2.3.4.3 U-plane handling + +The U-plane handling for Conditional Handover follows the same principles for DAPS handover in 9.2.3.2.2, if early data forwarding is applied, except that, in case of Full Configuration, HFN and PDCP SN are reset in the target gNB after the SN assignment is handed over to the target gNB. If late data forwarding is applied, the U-plane handling follows the RLC-AM or RLC-UM bearer principles defined in 9.2.3.2.2. + +#### 9.2.3.4.4 Data Forwarding + +If late data forwarding is applied, the source NG-RAN node initiates data forwarding once it knows which target NG-RAN node the UE has successfully accessed. In that case the behavior of the Conditional Handover data forwarding follows the same behavior as defined in 9.2.3.2.3 for the intra-system handover data forwarding, except the behavior for DRBs configured with DAPS handover. + +If early data forwarding is applied instead, the source NG-RAN node initiates data forwarding before the UE executes the handover, to a candidate target node of interest. The behavior of early data forwarding for the Conditional Handover follows the same principles for DRBs configured with DAPS handover in the intra-system handover as defined in 9.2.3.2.3. + +### 9.2.3.5 L1/L2-Triggered Mobility + +#### 9.2.3.5.1 General + +LTM is a procedure in which a gNB receives L1 measurement report(s) from a UE, and on their basis the gNB changes UE serving cell by a cell switch command signalled via a MAC CE. The cell switch command indicates an LTM candidate configuration that the gNB previously prepared and provided to the UE through RRC signalling. Then the UE switches to the target configuration according to the cell switch command. The LTM procedure can be used to reduce the mobility latency as described in Annex G. + +When configured by the network, it is possible to activate TCI states of one or multiple cells that are different from the current serving cell. For instance, the TCI states of the LTM candidate cells can be activated in advance before any of those cells become the serving cell. This allows the UE to be DL synchronized with those cells, thereby facilitating a faster cell switch to one of those cells when cell switch is triggered. + +When configured by the network, it is possible to initiate UL TA acquisition (called early TA) procedure of one or multiple cells that are different from the current serving cells. If the cell has the same $N_{TA}$ as the current serving cells or $N_{TA}=0$ , early TA acquisition procedure is not required. The network may request the UE to perform early TA acquisition of a candidate cell before a cell switch. The early TA acquisition procedure is triggered by PDCCH order as specified in clause 9.2.6 or realized through UE-based TA measurement as configured by RRC. In the former case, the + +gNB to which the candidate cell belongs calculates the TA value and sends it to the gNB to which the serving cell belongs. The serving cell sends the TA value in the LTM cell switch command MAC CE when triggering LTM cell switch. In the latter case, the UE performs TA measurement for the candidate cells after being configured by RRC but the exact time the UE performs TA measurement is up to UE implementation. The UE applies the TA value measured by itself and performs RACH-less LTM upon receiving the cell switch command. The network may also send a TA value in the LTM cell switch command MAC CE without early TA acquisition. + +Depending on the availability of a valid TA value, the UE performs either a RACH-less LTM or RACH-based LTM cell switch. If the TA value is provided in the cell switch command, the UE applies the TA value as instructed by the network. In the case where UE-based TA measurement is configured, but no TA value is provided in the cell switch command, the UE applies the TA value by itself if available. Meanwhile, the UE performs RACH-less LTM cell switch upon receiving the cell switch command. If no valid TA value is available, the UE performs RACH-based LTM cell switch. + +Regardless of whether the UE is configured for UE-based TA measurement for a certain candidate cell, it will still follow the PDCCH order, which includes requesting a random access procedure towards the candidate cells. This also applies to the candidate cells for which the UE is capable of deriving TA values by itself. Additionally, regardless of whether the UE has already performed a random access procedure towards the candidate cells, it will still follow the UE-based measurement configuration if configured by the network. + +For RACH-less LTM, the UE accesses the target cell using either a configured grant or a dynamic grant. The configured grant is provided in the LTM candidate configuration, and the UE selects the configured grant occasion associated with the beam indicated in the cell switch command. Upon initiation of LTM cell switch to the target cell, the UE starts to monitor PDCCH on the target cell for dynamic scheduling. Before RACH-less LTM procedure completion, the UE shall not trigger random access procedure if it does not have a valid PUCCH resource for triggered SRs. + +The following principles apply to LTM: + +- Security key is maintained upon an LTM cell switch; +- Subsequent LTM is supported. + +LTM supports both intra-gNB-DU and intra-gNB-CU inter-gNB-DU mobility. LTM supports both intra-frequency and inter-frequency mobility, including mobility to inter-frequency cell that is not a current serving cell. LTM is supported only for licensed spectrum. The following scenarios are supported: + +- PCell change in non-CA scenario and non-DC scenario; +- PCell and SCell(s) change in CA scenario; +- Dual connectivity scenario, PCell and MCG SCell(s) change and intra-SN PSCell and SCG SCell(s) change without MN involvement. LTM for simultaneous PCell and PSCell change is not supported. + +While the UE has stored LTM candidate configurations the UE can also execute any L3 handover command sent by the network. + +### 9.2.3.5.2 C-Plane Handling + +Cell switch command is conveyed in a MAC CE, which contains the necessary information to perform the LTM cell switch. + +The overall procedure for LTM is shown in Figure 9.2.3.5.2-1 below. Subsequent LTM is done by repeating the early synchronization, LTM cell switch execution, and LTM cell switch completion steps without releasing other LTM candidate configurations after each LTM cell switch completion. The general procedure over the air interface is applicable to SCG LTM. Further details of SCG LTM can be found in TS 37.340 [21]. + +![Sequence diagram illustrating the signalling procedure for LTM (Link Time Measurement) between a UE and a gNB. The diagram is divided into four phases: UE in RRC_CONNECTED, LTM preparation, Early sync, and LTM cell switch execution. The steps are: 1. Measurement report from UE to gNB; 2. RRC reconfiguration (LTM candidate cell configuration) from gNB to UE; 3. RRC reconfiguration complete from UE to gNB; 4a. DL synchronization with candidate cells (UE to gNB); 4b. UL synchronization with candidate cells (UE to gNB); 5. L1 measurement report from UE to gNB; 6. Cell switch command (MAC CE) from gNB to UE; 7. RACH Procedure (UE to gNB); 8. LTM cell switch completion (UE to gNB).](e16bfa31d748f4d99ec4ae3d16656926_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB + Note left of UE: UE in RRC_CONNECTED + UE->>gNB: 1: Measurement report + Note right of gNB: LTM candidate preparation + gNB->>UE: 2: RRC reconfiguration (LTM candidate cell configuration) + UE->>gNB: 3: RRC reconfiguration complete + Note left of UE: Early sync + Note right of gNB: LTM preparation + UE->>gNB: 4a: DL synchronization with candidate cells + UE->>gNB: 4b: UL synchronization with candidate cells + Note left of UE: LTM cell switch execution + UE->>gNB: 5: L1 measurement report + Note right of gNB: LTM decision + gNB->>UE: 6: Cell switch command (MAC CE) + Note left of UE: Detach from source, apply target configurations + Note right of gNB: LTM cell switch completion + UE->>gNB: 7: RACH Procedure + UE->>gNB: 8: LTM cell switch completion + +``` + +Sequence diagram illustrating the signalling procedure for LTM (Link Time Measurement) between a UE and a gNB. The diagram is divided into four phases: UE in RRC\_CONNECTED, LTM preparation, Early sync, and LTM cell switch execution. The steps are: 1. Measurement report from UE to gNB; 2. RRC reconfiguration (LTM candidate cell configuration) from gNB to UE; 3. RRC reconfiguration complete from UE to gNB; 4a. DL synchronization with candidate cells (UE to gNB); 4b. UL synchronization with candidate cells (UE to gNB); 5. L1 measurement report from UE to gNB; 6. Cell switch command (MAC CE) from gNB to UE; 7. RACH Procedure (UE to gNB); 8. LTM cell switch completion (UE to gNB). + +**Figure 9.2.3.5.2-1. Signalling procedure for LTM** + +The procedure for LTM is as follows: + +1. The UE sends a *MeasurementReport* message to the gNB. The gNB decides to configure LTM and initiates LTM preparation. +2. The gNB transmits an *RRCReconfiguration* message to the UE including the LTM candidate configurations. +3. The UE stores the LTM candidate configurations and transmits an *RRCReconfigurationComplete* message to the gNB. +- 4a. The UE performs DL synchronization with the candidate cell(s) before receiving the cell switch command. +- 4b. When UE-based TA measurement is configured, UE acquires the TA value(s) of the candidate cell(s) by measurement. UE performs early TA acquisition with the candidate cell(s) as requested by the network before receiving the cell switch command as specified in clause 9.2.6. This is done via CFRA triggered by a PDCCH order from the source cell, following which the UE sends preamble towards the indicated candidate cell. In order to minimize the data interruption of the source cell due to CFRA towards the candidate cell(s), the UE does not receive random access response from the network for the purpose of TA value acquisition and the TA value of the candidate cell is indicated in the cell switch command. The UE does not maintain the TA timer for the candidate cell and relies on network implementation to guarantee the TA validity. +5. The UE performs L1 measurements on the configured candidate cell(s) and transmits L1 measurement reports to the gNB. L1 measurement should be performed as long as RRC reconfiguration (step 2) is applicable. + +6. The gNB decides to execute cell switch to a target cell and transmits a MAC CE triggering cell switch by including the candidate configuration index of the target cell. The UE switches to the target cell and applies the configuration indicated by candidate configuration index. +7. The UE performs the random access procedure towards the target cell, if UE does not have valid TA of the target cell as specified in clause 6.1.3.xy of TS 38.321[6]. +8. The UE completes the LTM cell switch procedure by sending *RRCReconfigurationComplete* message to target cell. If the UE has performed a RA procedure in step 7 the UE considers that LTM cell switch execution is successfully completed when the random access procedure is successfully completed. For RACH-less LTM, the UE considers that LTM cell switch execution is successfully completed when the UE determines that the network has successfully received its first UL data. + +The steps 4-8 can be performed multiple times for subsequent LTM using the LTM candidate configuration(s) provided in step 2. + +The procedure over the air interface described in Figure x is applicable to both intra-gNB-DU LTM and inter-gNB-DU LTM. The overall LTM procedures over F1-C interface are captured in TS 38.401[4]. + +### 9.2.3.5.3 U-Plane Handling + +After receiving an LTM cell switch command MAC CE, the UE performs MAC reset. Whether the UE performs RLC re-establishment and PDCP data recovery during cell switch is explicitly controlled by the network through RRC signalling. + +## 9.2.4 Measurements + +In RRC\_CONNECTED, the UE measures multiple beams (at least one) of a cell and the measurements results (power values) are averaged to derive the cell quality. In doing so, the UE is configured to consider a subset of the detected beams. Filtering takes place at two different levels: at the physical layer to derive beam quality and then at RRC level to derive cell quality from multiple beams. Cell quality from beam measurements is derived in the same way for the serving cell(s) and for the non-serving cell(s). Measurement reports may contain the measurement results of the *X* best beams if the UE is configured to do so by the gNB. + +The corresponding high-level measurement model is described below: + +![Figure 9.2.4-1: Measurement Model diagram showing the flow of measurement data from multiple beams through various processing stages including beam filtering, beam selection, and cell quality derivation.](2e18ae7359d8c32e96919956f238ecc5_img.jpg) + +The diagram illustrates the measurement model flow. On the left, a dashed box labeled 'K beams' contains five horizontal bars representing beam-specific samples. Arrows from these bars point to two parallel processing paths. The top path consists of three rectangular blocks: 'beam filtering' (receiving input from the beams), 'beam selection' (receiving input from 'beam filtering'), and 'cell quality derivation' (receiving input from 'beam selection'). The bottom path consists of two rectangular blocks: 'beam filtering' (receiving input from the beams) and 'cell quality derivation' (receiving input from 'beam filtering'). Vertical arrows point from the top 'cell quality derivation' block and the bottom 'cell quality derivation' block to a final output arrow on the right. Additionally, there are vertical arrows pointing from the bottom of the diagram up into the 'beam filtering' and 'cell quality derivation' blocks of the bottom path. + +Figure 9.2.4-1: Measurement Model diagram showing the flow of measurement data from multiple beams through various processing stages including beam filtering, beam selection, and cell quality derivation. + +Figure 9.2.4-1: Measurement Model + +NOTE 1: K beams correspond to the measurements on SSB or CSI-RS resources configured for L3 mobility by gNB and detected by UE at L1. + +- A: measurements (beam specific samples) internal to the physical layer. + +- **Layer 1 filtering:** internal layer 1 filtering of the inputs measured at point A. Exact filtering is implementation dependent. How the measurements are actually executed in the physical layer by an implementation (inputs A and Layer 1 filtering) is not constrained by the standard. +- **A1:** measurements (i.e. beam specific measurements) reported by layer 1 to layer 3 after layer 1 filtering. +- **Beam Consolidation/Selection:** beam specific measurements are consolidated to derive cell quality. The behaviour of the Beam consolidation/selection is standardised and the configuration of this module is provided by RRC signalling. Reporting period at B equals one measurement period at A1. +- **B:** a measurement (i.e. cell quality) derived from beam-specific measurements reported to layer 3 after beam consolidation/selection. +- **Layer 3 filtering for cell quality:** filtering performed on the measurements provided at point B. The behaviour of the Layer 3 filters is standardised and the configuration of the layer 3 filters is provided by RRC signalling. Filtering reporting period at C equals one measurement period at B. +- **C:** a measurement after processing in the layer 3 filter. The reporting rate is identical to the reporting rate at point B. This measurement is used as input for one or more evaluation of reporting criteria. +- **Evaluation of reporting criteria:** checks whether actual measurement reporting is necessary at point D. The evaluation can be based on more than one flow of measurements at reference point C e.g. to compare between different measurements. This is illustrated by input C and C1. The UE shall evaluate the reporting criteria at least every time a new measurement result is reported at point C, C1. The reporting criteria are standardised and the configuration is provided by RRC signalling (UE measurements). +- **D:** measurement report information (message) sent on the radio interface. +- **L3 Beam filtering:** filtering performed on the measurements (i.e. beam specific measurements) provided at point A1. The behaviour of the beam filters is standardised and the configuration of the beam filters is provided by RRC signalling. Filtering reporting period at E equals one measurement period at A1. +- **E:** a measurement (i.e. beam-specific measurement) after processing in the beam filter. The reporting rate is identical to the reporting rate at point A1. This measurement is used as input for selecting the X measurements to be reported. +- **Beam Selection for beam reporting:** selects the X measurements from the measurements provided at point E. The behaviour of the beam selection is standardised and the configuration of this module is provided by RRC signalling. +- **F:** beam measurement information included in measurement report (sent) on the radio interface. + +Layer 1 filtering introduces a certain level of measurement averaging. How and when the UE exactly performs the required measurements is implementation specific to the point that the output at B fulfils the performance requirements set in TS 38.133 [13]. Layer 3 filtering for cell quality and related parameters used are specified in TS 38.331 [12] and do not introduce any delay in the sample availability between B and C. Measurement at point C, C1 is the input used in the event evaluation. L3 Beam filtering and related parameters used are specified in TS 38.331 [12] and do not introduce any delay in the sample availability between E and F. + +Measurement reports are characterized by the following: + +- Measurement reports include the measurement identity of the associated measurement configuration that triggered the reporting; +- Cell and beam measurement quantities to be included in measurement reports are configured by the network; +- The number of non-serving cells to be reported can be limited through configuration by the network; +- Cells belonging to an exclude-list configured by the network are not used in event evaluation and reporting, and conversely when an allow-list is configured by the network, only the cells belonging to the allow-list are used in event evaluation and reporting; +- Beam measurements to be included in measurement reports are configured by the network (beam identifier only, measurement result and beam identifier, or no beam reporting). + +Intra-frequency neighbour (cell) measurements and inter-frequency neighbour (cell) measurements are defined as follows: + +- SSB based intra-frequency measurement: a measurement is defined as an SSB based intra-frequency measurement provided the center frequency of the SSB of the serving cell and the center frequency of the SSB of the neighbour cell are the same, and the subcarrier spacing of the two SSBs is also the same. +- SSB based inter-frequency measurement: a measurement is defined as an SSB based inter-frequency measurement provided the center frequency of the SSB of the serving cell and the center frequency of the SSB of the neighbour cell are different, or the subcarrier spacing of the two SSBs is different. + +NOTE 2: For SSB based measurements, one measurement object corresponds to one SSB and the UE considers different SSBs as different cells. + +NOTE 2a: If a UE is configured to perform serving cell measurements based on an NCD-SSB configured in its active BWP, this NCD-SSB is considered as the SSB of the serving cell in the definition of intra-frequency and inter-frequency measurements as above. + +- CSI-RS based intra-frequency measurement: a measurement is defined as a CSI-RS based intra-frequency measurement provided that: + - The subcarrier spacing of CSI-RS resources on the neighbour cell configured for measurement is the same as the SCS of CSI-RS resources on the serving cell indicated for measurement; and + - For 60kHz subcarrier spacing, the CP type of CSI-RS resources on the neighbour cell configured for measurement is the same as the CP type of CSI-RS resources on the serving cell indicated for measurement; and + - The centre frequency of CSI-RS resources on the neighbour cell configured for measurement is the same as the centre frequency of CSI-RS resource on the serving cell indicated for measurement. +- CSI-RS based inter-frequency measurement: a measurement is defined as a CSI-RS based inter-frequency measurement if it is not a CSI-RS based intra-frequency measurement. + +NOTE 3: Extended CP for CSI-RS based measurement is not supported in this release. + +Whether a measurement is non-gap-assisted or gap-assisted depends on the capability of the UE, the active BWP of the UE and the current operating frequency: + +- For SSB based inter-frequency measurement, if the measurement gap requirement information is reported by the UE, a measurement gap configuration may be provided according to the information. Otherwise, a measurement gap configuration is always provided in the following cases: + - If the UE only supports per-UE measurement gaps; + - If the UE supports per-FR measurement gaps and any of the serving cells are in the same frequency range of the measurement object. +- For SSB based intra-frequency measurement, if the measurement gap requirement information is reported by the UE, a measurement gap configuration may be provided according to the information. Otherwise, a measurement gap configuration is always provided in the following case: + - Other than the initial BWP, if any of the UE configured BWPs do not contain the frequency domain resources of the SSB associated to the initial DL BWP, and are not configured with NCD-SSB for serving cell measurement. + +In non-gap-assisted scenarios, the UE shall be able to carry out such measurements without measurement gaps. In gap-assisted scenarios, the UE cannot be assumed to be able to carry out such measurements without measurement gaps. + +Network may request the UE to measure NR and/or E-UTRA carriers in RRC\_IDLE or RRC\_INACTIVE via system information or via dedicated measurement configuration in *RRRelease*. If the UE was configured to perform measurements of NR and/or E-UTRA carriers while in RRC\_IDLE or in RRC\_INACTIVE, it may provide an indication of the availability of corresponding measurement results to the gNB in the *RRSetupComplete* message. The network may request the UE to report those measurements after security activation. The request for the measurements + +can be sent by the network immediately after transmitting the Security Mode Command (i.e. before the reception of the Security Mode Complete from the UE). + +If the UE was configured to perform measurements of NR and/or E-UTRA carriers while in RRC\_INACTIVE, the gNB can request the UE to provide corresponding measurement results in the *RRCResume* message and then the UE can include the available measurement results in the *RRCResumeComplete* message. Alternatively, the UE may provide an indication of the availability of the measurement results to the gNB in the *RRCResumeComplete* message and the gNB can then request the UE to provide these measurement results. + +## 9.2.5 Paging + +Paging allows the network to reach UEs in RRC\_IDLE and in RRC\_INACTIVE state through *Paging* messages, and to notify UEs in RRC\_IDLE, RRC\_INACTIVE and RRC\_CONNECTED state of system information change (see clause 7.3.3) and ETWS/CMAS indications (see clause 16.4) through *Short Messages*. Both *Paging* messages and *Short Messages* are addressed with P-RNTI on PDCCH, but while the former is sent on PCCH, the latter is sent over PDCCH directly (see clause 6.5 of TS 38.331 [12]). + +While in RRC\_IDLE the UE monitors the paging channels for CN-initiated paging. While in RRC\_INACTIVE with no ongoing SDT procedure (see clause 18.0) the UE monitors paging channels for RAN-initiated paging and CN-initiated paging. A UE need not monitor paging channels continuously though; Paging DRX is defined where the UE in RRC\_IDLE or RRC\_INACTIVE is only required to monitor paging channels during one Paging Occasion (PO) per DRX cycle (see TS 38.304 [10]). The Paging DRX cycles are configured by the network: + +- 1) For CN-initiated paging, a default cycle is broadcast in system information; + - 2) For CN-initiated paging, a UE specific cycle can be configured via NAS signalling; + - 3) For RAN-initiated paging, a UE-specific cycle is configured via RRC signalling; +- The UE uses the shortest of the DRX cycles applicable i.e. a UE in RRC\_IDLE uses the shortest of the first two cycles above, while a UE in RRC\_INACTIVE uses the shortest of the three. + +The POs of a UE for CN-initiated and RAN-initiated paging are based on the same UE ID, resulting in overlapping POs for both. The number of different POs in a DRX cycle is configurable via system information and a network may distribute UEs to those POs based on their IDs. + +While in RRC\_CONNECTED and while in RRC\_INACTIVE with ongoing SDT procedure, the UE monitors the paging channels in any PO signalled in system information for SI change indication and PWS notification. In case of BA, a UE in RRC\_CONNECTED only monitors paging channels on the active BWP with common search space configured. + +For operation with shared spectrum channel access, a UE can be configured for an additional number of PDCCH monitoring occasions in its PO to monitor for paging. However, when the UE detects a PDCCH transmission within the UE's PO addressed with P-RNTI, the UE is not required to monitor the subsequent PDCCH monitoring occasions within this PO. + +If Paging Cause is included in the Paging message, a UE in RRC\_IDLE or RRC\_INACTIVE state may use the Paging Cause as per TS 23.501[3]. + +**Paging optimization for UEs in CM\_IDLE:** at UE context release, the NG-RAN node may provide the AMF with a list of recommended cells and NG-RAN nodes as assistance info for subsequent paging. The AMF may also provide Paging Attempt Information consisting of a Paging Attempt Count and the Intended Number of Paging Attempts and may include the Next Paging Area Scope. If Paging Attempt Information is included in the Paging message, each paged NG-RAN node receives the same information during a paging attempt. The Paging Attempt Count shall be increased by one at each new paging attempt. The Next Paging Area Scope, when present, indicates whether the AMF plans to modify the paging area currently selected at next paging attempt. If the UE has changed its state to CM\_CONNECTED the Paging Attempt Count is reset. + +**Paging optimization for UEs in RRC\_INACTIVE:** at RAN Paging, the serving NG-RAN node provides RAN Paging area information. The serving NG-RAN node may also provide RAN Paging attempt information. Each paged NG-RAN node receives the same RAN Paging attempt information during a paging attempt with the following content: Paging Attempt Count, the intended number of paging attempts and the Next Paging Area Scope. The Paging Attempt Count shall be increased by one at each new paging attempt. The Next Paging Area Scope, when present, indicates + +whether the serving NG\_RAN node plans to modify the RAN Paging Area currently selected at next paging attempt. If the UE leaves RRC\_INACTIVE state the Paging Attempt Count is reset. + +**UE power saving for paging monitoring:** in order to reduce UE power consumption due to false paging alarms, the group of UEs monitoring the same PO can be further divided into multiple subgroups. With subgrouping, a UE shall monitor PDCCH in its PO for paging if the subgroup to which the UE belongs is paged as indicated via associated PEI. If a UE cannot find its subgroup ID with the PEI configurations in a cell or if the UE is unable to monitor the associated PEI occasion corresponding to its PO, it shall monitor the paging in its PO. + +These subgroups have the following characteristics: + +- They are formed based on either CN controlled subgrouping or UE ID based subgrouping; +- If CN controlled subgroup ID is not provided from AMF, UE ID based subgrouping is used if supported by the UE and network; +- The RRC state (RRC\_IDLE or RRC\_INACTIVE state) does not impact which subgroup the UE belongs to; +- Subgrouping support for a cell is broadcast in the system information as one of the following: Only CN controlled subgrouping supported, only UE ID based subgrouping supported, or both CN controlled subgrouping and UE ID based subgrouping supported; +- Total number of subgroups allowed in a cell is up to 8 and represents the sum of CN controlled and UE ID based subgrouping configured by the network; +- A UE configured with CN controlled subgroup ID applies CN controlled subgroup ID if the cell supports CN controlled subgrouping; otherwise, it derives UE ID based subgroup ID if the cell supports only UE ID based subgrouping. + +PEI associated with subgroups has the following characteristics: + +- If the PEI is supported by the UE, it shall at least support UE ID based subgrouping method; + - PEI monitoring can be limited via system information to the last used cell (i.e., the cell in which the UE most recently received *RRCRelease* without indicating that the last used cell for PEI shall not be updated); + - A PEI-capable UE shall store its last used cell information; + - gNBs supporting the PEI monitoring to the last used cell function provide the UE's last used cell information to the AMF in the NG-AP UE Context Release Complete message for PEI capable UEs, as described in TS 38.413 [26]; + - UE that expects MBS group notification shall ignore the PEI and shall monitor paging in its PO. + +**CN controlled subgrouping:** For CN controlled subgrouping, AMF is responsible for assigning subgroup ID to the UE. The total number of subgroups for CN controlled subgrouping which can be configured, e.g. by OAM is up to 8. It is assumed that CN controlled subgrouping support is homogeneous within an RNA. + +The following figure describes the procedure for CN controlled subgrouping: + +![Sequence diagram for CN controlled subgrouping involving UE, gNB, and AMF.](0b998e3ad8f9d104768642612605cb35_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB + participant AMF + Note right of AMF: 2. UE subgroup determination + UE->>AMF: 1. UE support of CN controlled subgrouping + AMF->>UE: 3. Subgroup ID assignment + AMF->>gNB: 4. Assigned subgroup ID + Note left of gNB: 5. Arrival/generation of paging message for the UE + gNB->>UE: 6. PEI + +``` + +Sequence diagram for CN controlled subgrouping involving UE, gNB, and AMF. + +Figure 9.2.5-1: Procedure for CN controlled subgrouping + +1. The UE indicates its support of CN controlled subgrouping via NAS signalling. +2. If the UE supports CN controlled subgrouping, the AMF determines the subgroup ID assignment for the UE. +3. The AMF sends subgroup ID to the UE via NAS signalling. +4. The AMF informs the gNB about the CN assigned subgroup ID for paging the UE in RRC\_IDLE/ RRC\_INACTIVE state. +5. When the paging message for the UE is received from the CN or is generated by the gNB, the gNB determines the PO and the associated PEI occasion for the UE. +6. Before the UE is paged in the PO, the gNB transmits the associated PEI and indicates the corresponding CN controlled subgroup of the UE that is to be paged in the PEI. + +**UE ID based subgrouping:** For UE ID based subgrouping, the gNB and UE can determine the subgroup ID based on the UE ID and the total number of subgroups for UE ID based subgrouping in the cell. The total number of subgroups for UE ID based subgrouping is decided by the gNB for each cell and can be different in different cells. The following figure describes the procedure for UE ID based subgrouping: + +![Sequence diagram for UE ID based subgrouping involving UE and gNB.](c995e0bb4efc8c0f2994428aa1245709_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB + Note right of gNB: 1. NW determines the total number of subgroups + gNB->>UE: 2. The total number of subgroups for UE ID based subgrouping is broadcasted in System Information + Note left of UE: 3. UE subgroup determination + Note right of gNB: 4. Arrival/generation of paging message for the UE + gNB->>UE: 5. PEI + +``` + +Sequence diagram for UE ID based subgrouping involving UE and gNB. + +Figure 9.2.5-2: Procedure for UE ID based subgrouping + +1. The gNB determines the total number of subgroups for UE ID based subgrouping in a cell. +2. The gNB broadcasts the total number of subgroups for UE ID based subgrouping in a cell. + +3. UE determines its subgroup in a cell. +4. When paging message for the PEI capable UE is received from the CN at the gNB or is generated by the gNB, the gNB determines the PO and the associated PEI occasion for the UE. +5. Before the UE is paged in the PO, the gNB transmits the associated PEI and indicates the corresponding subgroup derived based on UE ID of the UE that is paged in the PEI. + +## 9.2.6 Random Access Procedure + +The random access procedure is triggered by a number of events: + +- Initial access from RRC\_IDLE; +- RRC Connection Re-establishment procedure; +- DL or UL data arrival, during RRC\_CONNECTED or during RRC\_INACTIVE while SDT procedure (see clause 18.0) is ongoing, when UL synchronisation status is "non-synchronised"; +- UL data arrival, during RRC\_CONNECTED or during RRC\_INACTIVE while SDT procedure is ongoing, when there are no PUCCH resources for SR available; +- Handover; +- SR failure; +- Explicit request by RRC upon synchronous reconfiguration; +- RRC Connection Resume procedure from RRC\_INACTIVE; +- To establish time alignment for a primary or a secondary TAG; +- Request for Other SI (see clause 7.3); +- Beam failure recovery; +- Consistent UL LBT failure on SpCell; +- SDT in RRC\_INACTIVE (see clause 18); +- Positioning purpose during RRC\_CONNECTED requiring random access procedure, e.g., when timing advance is needed for UE positioning; +- Early UL synchronization with an LTM candidate cell; +- RACH-based LTM cell switch. + +Two types of random access procedure are supported: 4-step RA type with MSG1 and 2-step RA type with MSGA. Both types of RA procedure support contention-based random access (CBRA) and contention-free random access (CFRA) as shown on Figure 9.2.6-1 below. + +The UE selects the type of random access at initiation of the random access procedure based on network configuration: + +- when CFRA resources are not configured, an RSRP threshold is used by the UE to select between 2-step RA type and 4-step RA type; +- when CFRA resources for 4-step RA type are configured, UE performs random access with 4-step RA type; +- when CFRA resources for 2-step RA type are configured, UE performs random access with 2-step RA type. + +The network does not configure CFRA resources for 4-step and 2-step RA types at the same time for a Bandwidth Part (BWP). CFRA with 2-step RA type is only supported for handover. + +The MSG1 of the 4-step RA type consists of a preamble on PRACH. After MSG1 transmission, the UE monitors for a response from the network within a configured window. For CFRA, dedicated preamble for MSG1 transmission is assigned by the network and upon receiving random access response from the network, the UE ends the random access + +procedure as shown in Figure 9.2.6-1(c). For CBRA, upon reception of the random access response, the UE sends MSG3 using the UL grant scheduled in the response and monitors contention resolution as shown in Figure 9.2.6-1(a). If contention resolution is not successful after MSG3 (re)transmission(s), the UE goes back to MSG1 transmission. + +The MSGA of the 2-step RA type includes a preamble on PRACH and a payload on PUSCH. After MSGA transmission, the UE monitors for a response from the network within a configured window. For CFRA, dedicated preamble and PUSCH resource are configured for MSGA transmission and upon receiving the network response, the UE ends the random access procedure as shown in Figure 9.2.6-1(d). For CBRA, if contention resolution is successful upon receiving the network response, the UE ends the random access procedure as shown in Figure 9.2.6-1(b); while if fallback indication is received in MSGB, the UE performs MSG3 transmission using the UL grant scheduled in the fallback indication and monitors contention resolution as shown in Figure 9.2.6-2. If contention resolution is not successful after MSG3 (re)transmission(s), the UE goes back to MSGA transmission. + +If the random access procedure with 2-step RA type is not completed after a number of MSGA transmissions, the UE can be configured to switch to CBRA with 4-step RA type. + +For the random access procedure towards an LTM candidate cell for early UL TA acquisition, CFRA triggered by a PDCCH order is used. The UE sends MSG1 towards the cell without monitoring for a response from it as shown in Figure 9.2.6-1 (e). To support UE power ramping, the UE may perform MSG1 retransmission as indicated by the network. + +![Four sequence diagrams illustrating random access procedures: (a) CBRA with 4-step RA type, (b) CBRA with 2-step RA type, (c) CFRA with 4-step RA type, and (d) CFRA with 2-step RA type. Each diagram shows the interaction between a UE and a gNB with numbered or lettered markers for key events.](aa22da43c463563d3d0035722bd79449_img.jpg) + +(a) CBRA with 4-step RA type + +(b) CBRA with 2-step RA type + +(c) CFRA with 4-step RA type + +(d) CFRA with 2-step RA type + +Four sequence diagrams illustrating random access procedures: (a) CBRA with 4-step RA type, (b) CBRA with 2-step RA type, (c) CFRA with 4-step RA type, and (d) CFRA with 2-step RA type. Each diagram shows the interaction between a UE and a gNB with numbered or lettered markers for key events. + +![Sequence diagram for CFRA without network response with 4-step RA type. The diagram shows three vertical lifelines: UE, gNB (Serving cell), and gNB (Candidate cell). Step 0: An arrow labeled 'RA Preamble assignment' points from the gNB (Serving cell) to the UE. Step 1: An arrow labeled 'Random Access Preamble' points from the UE to the gNB (Candidate cell). Green circles with numbers 0, 1, and 0 are placed near the respective messages to indicate the sequence of events.](a5404b7275b06497eecf9b5883604753_img.jpg) + +Sequence diagram for CFRA without network response with 4-step RA type. The diagram shows three vertical lifelines: UE, gNB (Serving cell), and gNB (Candidate cell). Step 0: An arrow labeled 'RA Preamble assignment' points from the gNB (Serving cell) to the UE. Step 1: An arrow labeled 'Random Access Preamble' points from the UE to the gNB (Candidate cell). Green circles with numbers 0, 1, and 0 are placed near the respective messages to indicate the sequence of events. + +(e) CFRA without network response with 4-step RA type + +Figure 9.2.6-1: Random Access Procedures + +![Sequence diagram for Fallback for CBRA with 2-step RA type. The diagram shows two vertical lifelines representing the UE and the gNB. The first part of the diagram is obscured by a black rectangle. Below it, the sequence shows: 1. An arrow from the gNB to the UE. 2. An arrow from the UE to the gNB. 3. An arrow from the gNB to the UE. 4. An arrow from the UE to the gNB. Green circles are placed near the messages to indicate the sequence of events.](36e11608a186ec372afec7470985ff56_img.jpg) + +Sequence diagram for Fallback for CBRA with 2-step RA type. The diagram shows two vertical lifelines representing the UE and the gNB. The first part of the diagram is obscured by a black rectangle. Below it, the sequence shows: 1. An arrow from the gNB to the UE. 2. An arrow from the UE to the gNB. 3. An arrow from the gNB to the UE. 4. An arrow from the UE to the gNB. Green circles are placed near the messages to indicate the sequence of events. + +Figure 9.2.6-2: Fallback for CBRA with 2-step RA type + +For random access in a cell configured with SUL, the network can explicitly signal which carrier to use (UL or SUL). Otherwise, the UE selects the SUL carrier if and only if the measured quality of the DL is lower than a broadcast threshold. UE performs carrier selection before selecting between 2-step and 4-step RA type. The RSRP threshold for selecting between 2-step and 4-step RA type can be configured separately for UL and SUL. Once started, all uplink transmissions of the random access procedure remain on the selected carrier. + +The network can associate a set of RACH resources with feature(s) applicable to a Random Access procedure: Network Slicing (see clause 16.3), (e)RedCap (see clause 16.13), SDT (see clause 18), and NR coverage enhancement (see clause 19). A set of RACH resources associated with a feature is only valid for random access procedures applicable to at least that feature; and a set of RACH resources associated with several features is only valid for random access procedures having at least all of these features. The UE selects the set(s) of applicable RACH resources, after uplink carrier (i.e. NUL or SUL) and BWP selection and before selecting the RA type. + +When CA is configured, random access procedure with 2-step RA type is only performed on PCell while contention resolution can be cross-scheduled by the PCell. + +When CA is configured, for random access procedure with 4-step RA type, the first three steps of CBRA always occur on the PCell while contention resolution (step 4) can be cross-scheduled by the PCell. The three steps of a CFRA started on the PCell remain on the PCell. CFRA on SCell can only be initiated by the gNB to establish timing advance for a secondary TAG: the procedure is initiated by the gNB with a PDCCH order (step 0) that is sent on an activated SCell of the secondary TAG, preamble transmission (step 1) takes place on the SCell, and Random Access Response (step 2) takes place on PCell. + +When two TAG IDs are configured for the serving cell, the TAG for which the TA command is applied is indicated in Random Access Response message or in MSG B. + +## 9.2.7 Radio Link Failure + +In RRC\_CONNECTED, the UE performs Radio Link Monitoring (RLM) in the active BWP based on reference signals (SSB/CSI-RS) and signal quality thresholds configured by the network. SSB-based RLM is based on the CD-SSB associated to the initial DL BWP and can be configured for the initial DL BWP, for DL BWPs containing the CD-SSB associated to the initial DL BWP, and, if supported, for DL BWPs not containing the CD-SSB associated to the initial DL BWP. Besides, SSB-based RLM can be also performed based on a non-cell defining SSB, if configured for the active DL BWP. For other DL BWPs, RLM can only be performed based on CSI-RS, if configured for the active DL BWP. In case of DAPS handover, the UE continues the detection of radio link failure at the source cell until the successful completion of the random access procedure to the target cell. + +The UE declares Radio Link Failure (RLF) when one of the following criteria are met: + +- Expiry of a radio problem timer started after indication of radio problems from the physical layer (if radio problems are recovered before the timer is expired, the UE stops the timer); or +- Expiry of a timer started upon triggering a measurement report for a measurement identity for which the timer has been configured while another radio problem timer is running; or +- Random access procedure failure; or +- RLC failure; or +- Detection of consistent uplink LBT failures for operation with shared spectrum channel access as described in 5.6.1; or +- For IAB-MT, the reception of a BH RLF indication received from its parent node. + +After RLF is declared, the UE: + +- stays in RRC\_CONNECTED; +- in case of DAPS handover, for RLF in the source cell: + - stops any data transmission or reception via the source link and releases the source link, but maintains the source RRC configuration; + - if handover failure is then declared at the target cell, the UE: + - selects a suitable cell and then initiates RRC re-establishment; + - enters RRC\_IDLE if a suitable cell was not found within a certain time after handover failure was declared. +- in case of CHO, for RLF in the source cell: + - selects a suitable cell and if the selected cell is a CHO candidate and if network configured the UE to try CHO after RLF then the UE attempts CHO execution once, otherwise re-establishment is performed; + - enters RRC\_IDLE if a suitable cell was not found within a certain time after RLF was declared. +- in case of MCG LTM, for RLF in the source cell: + - selects a suitable cell and if the selected cell is an LTM candidate cell and if network configured the UE to try LTM after RLF then the UE attempts LTM execution once, otherwise re-establishment is performed; + - enters RRC\_IDLE if a suitable cell was not found within a certain time after RLF was declared. +- otherwise, for RLF in the serving cell or in case of DAPS handover, for RLF in the target cell before releasing the source cell: + - selects a suitable cell and then initiates RRC re-establishment; + - enters RRC\_IDLE if a suitable cell was not found within a certain time after RLF was declared. + +When RLF occurs at the IAB BH link, the same mechanisms and procedures are applied as for the access link. This includes BH RLF detection and RLF recovery. + +The IAB-DU can transmit a BH RLF detection indication to its child nodes in the following cases: + +- The collocated IAB-MT initiates RRC re-establishment; +- The collocated IAB-MT is dual-connected, detects BH RLF on a BH link, and cannot perform UL re-routing for any traffic. This includes the scenario of an IAB-node operating in EN-DC or NR-DC, which uses only one link for backhauling and has BH RLF on this BH link; +- The collocated IAB-MT has received a BH RLF detection indication from a parent node, and there is no remaining backhaul link that is unaffected by the BH RLF condition indicated. + +Upon reception of the BH RLF detection indication, the child node may perform local rerouting for upstream traffic, if possible, over an available BH link. + +If the IAB-DU has transmitted a BH RLF detection indication to a child node due to an RLF condition on the collocated IAB-MT's parent link, and the collocated IAB-MT's subsequent RLF recovery is successful, the IAB-DU may transmit a BH RLF recovery indication to this child node. + +If the IAB-DU has transmitted a BH RLF detection indication to a child node due to the reception of a BH RLF detection indication by the collocated IAB-MT, and the collocated IAB-MT receives a BH RLF recovery indication, the IAB-DU may also transmit a BH RLF recovery indication to this child node. + +Upon reception of the BH RLF recovery indication, the child node reverts the actions triggered by the reception of the previous BH RLF detection indication. + +In case the RRC re-establishment procedure fails, the IAB-node may transmit a BH RLF indication to its child nodes. The BH RLF detection indication, BH RLF recovery indication and BH RLF indication are transmitted as BAP Control PDUs. + +## 9.2.8 Beam failure detection and recovery + +For beam failure detection, the gNB configures the UE with beam failure detection reference signals (SSB or CSI-RS) and the UE declares beam failure when the number of beam failure instance indications from the physical layer reaches a configured threshold before a configured timer expires. For beam failure detection in multi-TRP operation, the gNB configures the UE with two sets of beam failure detection reference signals, and the UE declares beam failure for a TRP / BFD-RS set when the number of beam failure instance indications associated with the corresponding set of beam failure detection reference signals from the physical layer reaches a configured threshold before a configured timer expires. + +SSB-based Beam Failure Detection is based on the CD-SSB associated to the initial DL BWP and can be configured for the initial DL BWPs, for DL BWPs containing the CD-SSB associated to the initial DL BWP, and, if supported, for DL BWPs not containing the CD-SSB associated to the initial DL BWP. Besides, SSB-based Beam Failure Detection can be also performed based on the non-cell defining SSB, if configured for the active DL BWP. For other DL BWPs, Beam Failure Detection can only be performed based on CSI-RS, if configured for the active DL BWP. + +After beam failure is detected on PCell, the UE: + +- triggers beam failure recovery by initiating a Random Access procedure on the PCell; +- selects a suitable beam to perform beam failure recovery (if the gNB has provided dedicated Random Access resources for certain beams, those will be prioritized by the UE). +- includes an indication of a beam failure on PCell in a BFR MAC CE if the Random Access procedure involves contention-based random access. + +Upon completion of the Random Access procedure, beam failure recovery for PCell is considered complete. + +After beam failure is detected on an SCell, the UE: + +- triggers beam failure recovery by initiating a transmission of a BFR MAC CE for this SCell; + +- selects a suitable beam for this SCell (if available) and indicates it along with the information about the beam failure in the BFR MAC CE. + +Upon reception of a PDCCH indicating an uplink grant for a new transmission for the HARQ process used for the transmission of the BFR MAC CE, beam failure recovery for this SCell is considered complete. + +After beam failure is detected for a BFD-RS set of a Serving Cell, the UE: + +- triggers beam failure recovery by initiating a transmission of a BFR MAC CE for this BFD-RS set; +- selects a suitable beam for this BFD-RS set (if available) and indicates whether the suitable (new) beam is found or not along with the information about the beam failure in the BFR MAC CE for this BFD-RS set. + +Upon reception of a PDCCH indicating an uplink grant for a new transmission for the HARQ process used for the transmission of the BFR MAC CE for this BFD-RS set, beam failure recovery for this BFD-RS set is considered complete. + +After beam failure is detected for both BFD-RS sets of PCell concurrently, the UE: + +- triggers beam failure recovery by initiating a Random Access procedure on the PCell; +- selects a suitable beam for each failed BFD-RS set (if available) and indicates whether the suitable (new) beam is found or not along with the information about the beam failure in the BFR MAC CE for each failed BFD-RS set; +- upon completion of the Random Access procedure, beam failure recovery for both BFD-RS sets of PCell is considered complete. + +## 9.2.9 Timing Advance + +In RRC\_CONNECTED, the gNB is responsible for maintaining the timing advance to keep the L1 synchronised. Serving cells having UL to which the same timing advance applies and using the same timing reference cell are grouped in a TAG. Each TAG contains at least one serving cell with configured uplink, and the mapping of each serving cell to a TAG is configured by RRC. + +For the primary TAG the UE uses the PCell as timing reference, except with shared spectrum channel access where an SCell can also be used in certain cases (see clause 7.1, TS 38.133 [13]). In a secondary TAG, the UE may use any of the activated SCells of this TAG as a timing reference cell, but should not change it unless necessary. + +Timing advance updates are signalled by the gNB to the UE via MAC CE commands. Such commands restart a TAG-specific timer which indicates whether the L1 can be synchronised or not: when the timer is running, the L1 is considered synchronised, otherwise, the L1 is considered non-synchronised (in which case uplink transmission can only take place through MSG1/MSG3). + +When two TAG IDs are configured for the PCell, both TAGs are regarded as primary TAG. + +## 9.2.10 Extended DRX for RRC\_IDLE and RRC\_INACTIVE + +When extended DRX (eDRX) is used, the following applies: + +- For RRC\_INACTIVE, eDRX configuration for RAN paging is decided and configured by NG-RAN. In RRC\_INACTIVE the UE monitors both RAN and CN paging; +- For RRC\_IDLE, eDRX for CN paging is configured by upper layers. In RRC\_IDLE the UE monitors only CN paging; +- Information on whether eDRX for CN paging and RAN paging is allowed on the cell is provided separately in system information; +- The maximum value of the eDRX cycle is 10485.76 seconds (2.91 hours) while the minimum value of the eDRX cycle is 2.56 seconds; +- The hyper SFN (H-SFN) is broadcast by the cell and increments by one when the SFN wraps around; + +- Paging Hyperframe (PH) refers to the H-SFN in which the UE starts monitoring paging according to DRX during a Paging Time Window (PTW). The PH and PTW are determined based on a formula (see TS 38.304 [10]) that is known by the AMF, UE and NG-RAN; +- H-SFN, PH and PTW are used if the eDRX cycle is greater than 10.24 seconds; +- When the RRC\_IDLE eDRX cycle is longer than the system information modification period, the UE verifies that stored system information remains valid before resuming/establishing an RRC connection. + +## 9.3 Inter RAT + +### 9.3.1 NR-E-UTRA mobility: Intra 5GC + +#### 9.3.1.1 Cell Reselection + +Cell reselection is characterised by the following: + +- Cell reselection between NR RRC\_IDLE and E-UTRA RRC\_IDLE is supported; +- Cell reselection from NR RRC\_INACTIVE to E-UTRA RRC\_IDLE is supported. + +#### 9.3.1.2 Handover + +Inter RAT mobility is characterised by the following: + +- The Source RAT configures Target RAT measurement and reporting. +- The source RAT decides on the preparation initiation and provides the necessary information to the target RAT in the format required by the target RAT: + - For handover preparation from E-UTRA to NR, the source RAT issues a handover preparation request message to the target RAT passing a transparent RRC container with necessary information to prepare the handover at the target side. The information for the target RAT is the same type as specified in clause 9.2.3.2.1 including the current QoS flow to DRB mapping applied to the UE and RRM configuration. + - The details of RRM configuration are the same type as specified for NR in clause 9.2.3.2.1 including beam measurement information for the listed cells if the measurements are available. +- Radio resources are prepared in the target RAT before the handover. +- The RRC reconfiguration message from the target RAT is delivered to the source RAT via a transparent container, and is passed to the UE by the source RAT in the handover command: + - The inter-RAT handover command message carries the same type of information required to access the target cell as specified for NR baseline handover in clause 9.2.3.2.1. +- The in-sequence and lossless handover is supported for the handover between gNB and ng-eNB. +- Both Xn and NG based inter-RAT handover between NG-RAN nodes is supported. Whether the handover is over Xn or CN is transparent to the UE. +- In order to keep the SDAP and PDCP configurations for in-sequence and lossless inter-RAT handover, delta-configuration for the radio bearer configuration is used. + +#### 9.3.1.3 Measurements + +Inter RAT measurements in NR for this use case are limited to E-UTRA. + +Whether a measurement is non-gap-assisted or gap-assisted depends on the capability of the UE and the current operating frequency: + +- For E-UTRA Inter RAT measurement, if the measurement gap requirement information is reported by the UE, a measurement gap configuration may be provided according to the information. Otherwise, a measurement gap configuration is always provided when: + - The UE only supports per-UE measurement gaps; or + - The UE supports per-FR measurement gaps and at least one of the NR serving cells is in FR1. + +## 9.3.2 NR-E-UTRA mobility: From 5GC to EPC + +### 9.3.2.1 Cell Reselection + +Cell reselection is characterised by the following: + +- Cell reselection between NR RRC\_IDLE and E-UTRA RRC\_IDLE is supported; +- Cell reselection from NR RRC\_INACTIVE to E-UTRA RRC\_IDLE is supported. + +### 9.3.2.2 Handover and redirection + +The source NG-RAN node decides between handover or redirection to EPS based on radio criteria and availability of the N26 interface. + +NOTE: Information about the availability of the N26 interface may be configured by OAM at the NG-RAN. + +Inter RAT handover is characterised by the following: + +- The Source RAT configures Target RAT measurement and reporting. +- The source RAT decides on the preparation initiation and provides the necessary information to the target RAT in the format required by the target RAT. +- Radio resources are prepared in the target RAT before the handover. +- The RRC reconfiguration message from the target RAT is delivered to the source RAT via a transparent container, and is passed to the UE by the source RAT in the handover command. +- In-sequence and lossless handovers are not supported. +- Security procedures for handover to E-UTRA/EPC should follow E-UTRA handover procedures. + +### 9.3.2.3 Measurements + +Inter RAT measurements in NR for this use case are limited to E-UTRA. + +Whether a measurement is non-gap-assisted or gap-assisted depends on the capability of the UE and the current operating frequency: + +- For E-UTRA Inter RAT measurement, if the measurement gap requirement information is reported by the UE, a measurement gap configuration may be provided according to the information. Otherwise, a measurement gap configuration is always provided when: + - The UE only supports per-UE measurement gaps; or + - The UE supports per-FR measurement gaps and at least one of the NR serving cells is in FR1. + +### 9.3.2.4 Data Forwarding for the Control Plane + +Control plane handling for inter-System data forwarding from 5GS to EPS follows the following key principles: + +- Only forwarding of downlink data is supported. +- PDU session information at the serving NG-RAN node contains mapping information per QoS Flow to a corresponding E-RAB. + +- At handover preparation, the source NG-RAN node shall decide which mapped E-RABs are proposed to be subject to data forwarding and provide this information in the source-to-target container to the target eNB. Based on availability of direct data forwarding path the source NG-RAN node may request to apply direct data forwarding by indicating direct data forwarding path availability to the 5GC. +- The target eNB assigns forwarding TEID/TNL address(es) for the E-RAB(s) for which it accepts data forwarding. +- In case of indirect data forwarding, a single data forwarding tunnel is established between the source NG-RAN node and UPF per PDU session for which at least data for a single QoS Flow is subject to data forwarding. +- In case of direct data forwarding, the source NG-RAN node receives a TEID/TNL address for each E-RAB accepted for data forwarding as assigned by the target eNB. + +### 9.3.2.5 Data Forwarding for the User Plane + +In case of indirect data forwarding, user plane handling for inter-System data forwarding from 5GS to EPS follows the following key principles: + +- For the QoS flows accepted for data forwarding, the NG-RAN node initiates data forwarding to the UPF by the corresponding PDU session data forwarding tunnel(s). +- The UPF maps forwarded data received from the per PDU session data forwarding tunnel(s) to the mapped EPS bearer(s) removing the QFI. +- Handling of end marker packets: + - The source NG-RAN node receives one or several end marker packets per PDU session from the UPF. When there are no more data packets to be forwarded for QoS flows mapped to an E-RAB, the source NG-RAN node sends one or several end markers including one QFI (by means of the PDU Session User Plane protocol TS 38.415 [30]) of those QoS flows mapped to that E-RAB and sends the end marker packets to the UPF over the PDU session tunnel. From the included QFI in the end markers and its mapping to an EPS bearer ID, the UPF knows which EPS bearer tunnel it needs to forward the end-markers to the SGW. The QFI is removed in the end marker packets sent to the SGW. + +In case of direct data forwarding, user plane handling for inter-System data forwarding from 5GS to EPS follows the following key principles: + +- For the QoS flows accepted for data forwarding, the source NG-RAN node maps data received from the NG-U PDU session tunnel to the respective E-RAB data forwarding tunnel and forwards each user packet as PDCP SDU without PDCP SN and QFI information. +- The source NG-RAN node receives one or several GTP-U end marker packets per PDU session from the UPF and replicates the end marker packets into each E-RAB data forwarding tunnel when no more user data packets are to be forwarded over that tunnel. + +## 9.3.3 NR-E-UTRA mobility: From EPC to 5GC + +### 9.3.3.1 Data Forwarding for the Control Plane + +Control plane handling for inter-System data forwarding from EPS to 5GS follows the following key principles: + +- Only forwarding of downlink data is supported. +- The target NG-RAN node receives in the Handover Request message the mapping between E-RAB ID(s) and QoS Flow ID(s). It decides whether to accept the data forwarding for E-RAB IDs proposed for forwarding within the Source NG-RAN Node to Target NG-RAN Node Transparent Container. Based on availability of direct data forwarding path the source eNB may request to apply direct data forwarding by indicating direct data forwarding availability to the CN. +- In case of indirect data forwarding: + +- The target NG-RAN node assigns a TEID/TNL address for each PDU session for which at least one QoS flow is involved in the accepted data forwarding. +- The target NG-RAN node sends the Handover Request Acknowledge message in which it indicates the list of PDU sessions and QoS flows for which it has accepted the data forwarding. +- A single data forwarding tunnel is established between the UPF and the target NG-RAN node per PDU session for which at least data for a single QoS Flow is subject to data forwarding. +- The source eNB receives in the Handover Command message the list of E-RAB IDs for which the target NG-RAN node has accepted data forwarding of corresponding PDU sessions and QoS flows. +- In case of direct data forwarding: + - The source eNB indicates direct path availability to the CN. The source eNB's decision is indicated by the CN to the target NG-RAN node. + - The target NG-RAN node assigns a TEID/TNL address for each E-RAB it accepted for data forwarding. + - The source eNB receives in the Handover Command message the list of E-RAB IDs for which the target NG-RAN node has accepted data forwarding. + +### 9.3.3.2 Data Forwarding for the User Plane + +In case of indirect data forwarding, user plane handling for inter-System data forwarding from EPS to 5GS follows the following key principles: + +- For each E-RAB accepted for data forwarding, the source eNB forwards data to the SGW in the corresponding E-RAB tunnel and the SGW forwards the received data to the UPF in the E-RAB tunnel. +- The UPF maps the forwarded data received from an E-RAB tunnel to the corresponding mapped PDU session tunnel, adding a QFI value (by means of the PDU Session User Plane protocol TS 38.415 [30]). +- The target NG-RAN node maps a forwarded packet to the corresponding DRB based on the received QFI value. It prioritizes the forwarded packets over the fresh packets for those QoS flows. +- Handling of end marker packets: + - The UPF/PGW-U sends one or several end marker packets to the SGW per EPS bearer. The SGW forwards the received end markers per EPS bearer to the source eNB. When there are no more data packets to be forwarded for an E-RAB, the source eNB forwards the received end markers in the EPS bearer tunnel to the SGW and the SGW forwards them to the UPF. The UPF adds one QFI (by means of the PDU Session User Plane protocol TS 38.415 [30]) among the QoS flows mapped to that E-RAB to the end markers and sends those end markers to the target NG-RAN node in the per PDU session tunnel. When the target NG-RAN node receives an end marker with a QFI added, the target NG-RAN node starts to transmit the data packets of all QoS flows mapped to the corresponding E-RAB received from the core network towards the UE. + +In case of direct data forwarding, user plane handling for inter-System data forwarding from EPS to 5GS follows the following key principles: + +- For each E-RAB accepted for data forwarding, the source node forwards data to the target NG-RAN node in the corresponding E-RAB data forwarding tunnel. +- Until a GTP-U end marker packet is received, the target NG-RAN node prioritizes the forwarded packets over the fresh packets for those QoS flows which are involved in the accepted data forwarding. + +NOTE: The target NG-RAN node should remove the forwarded PDCP SNs if received in the forwarded GTP-U packets, and deliver the forwarded PDCP SDUs to the UE. + +## 9.3.4 NR-UTRA mobility + +### 9.3.4.1 Handover with SRVCC operation + +The source NR node decides to handover the UE with ongoing IMS voice from NR to UTRAN according the following principles: + +- The source NR node determines that the UE supports UTRA and requests the UE to send its UTRA radio access capabilities to the NG-RAN; +- The source NR node configures target RAT measurement and reporting; +- The source NR node determines based on the radio conditions and the indication that SRVCC operation is possible that handover to UTRAN should be initiated; +- The source NR node initiates the handover preparation only for the ongoing IMS voice and provides the indication to AMF that the handover is towards UTRAN together with the target UTRAN Node ID. The source NR node also provides an indication to the target UTRAN that the incoming handover originates from 5G. The SRVCC proceeds as specified in TS 23.216 [34]; +- The source NR node ensures that the size of the source-to-target container does not exceed the limits that can be handled by the interfaces involved in the handover; + +NOTE: For SRVCC handover, the size limit of the inter-node source-to-target container is 2560 octets (see AN-APDU in TS 29.002 [44]). + +- Radio resources are prepared in the target RAT before the handover; +- The RRC reconfiguration message from the target RAT is delivered to the source NR node via a transparent container and is passed to the UE by the source NR node in the handover command; +- In-sequence and lossless handovers are not supported; +- Only voice bearer is handed over to target RAT; +- Security procedures for handover to UTRA follows the procedures as specified in TS 33.501 [5]; +- Only handover to UTRA-FDD is supported. + +### 9.3.4.2 Measurements + +Inter RAT measurements are performed for UTRA. + +## 9.4 Roaming and Access Restrictions + +The roaming and access restriction information for a UE includes information on restrictions to be applied for subsequent mobility action during CM-CONNECTED state. It may be provided by the AMF and also may be updated by the AMF later. + +It includes the forbidden RAT, the forbidden area and the service area restrictions as specified in TS 23.501 [3]. It also includes serving PLMN/SNPN and may include a list of equivalent PLMNs or a list of equivalent SNPNs. It may also include PNI-NPN mobility restrictions (i.e. list of CAGs allowed for the UE and whether the UE can also access non-CAG cells). The gNB shall consider that roaming or access to CAG cells is only allowed if PNI-NPN mobility information is available for the UE. + +Upon receiving the roaming and access restriction information for a UE, if applicable, the gNB should use it to determine whether to apply restriction handling for subsequent mobility action, e.g., handover, redirection. + +If the roaming and access restriction information is not available for a UE at the gNB, the gNB shall consider that there is no restriction for subsequent mobility actions except for the PNI-NPN mobility as described in TS 23.501 [3]. + +Only if received over NG or Xn signalling, the roaming and access restriction information shall be propagated over Xn by the source gNB during Xn handover. If the Xn handover results in a change of serving PLMN (to an equivalent + +PLMN), the source gNB shall replace the serving PLMN with the identity of the target PLMN and move the serving PLMN to the equivalent PLMN list, before propagating the roaming and access restriction information. If the Xn handover results in a change of serving SNPN (to an equivalent SNPN), the source gNB shall replace the serving SNPN with the identity of the target SNPN and move the serving SNPN to the equivalent SNPN list, before propagating the roaming and access restriction information. + +If NG-RAN nodes with different versions of the XnAP or NGAP protocol are deployed, information provided by the 5GC within the NGAP Mobility Restriction List may be lost in the course of Xn mobility. In order to avoid such loss of information at Xn handover or UE context retrieval due to a source NG-RAN node or an old NG-RAN node not able to recognise the entire content, the source NG-RAN node or the old NG-RAN node may provide an 5GC Mobility Restriction List Container to the target NG-RAN node or the new NG-RAN node, containing the Mobility Restriction List as received from the 5GC. The target NG-RAN node or the new NG-RAN node shall use the information contained in the 5GC Mobility Restriction List Container as the Mobility Restriction List, except for the Serving PLMN/SNPN and the Equivalent PLMNs/SNPNs, which the NG-RAN node shall use from the XnAP Mobility Restriction List. The 5GC Mobility Restriction List Container may be propagated at future Xn handover and UE context retrieval. + +--- + +## 10 Scheduling + +### 10.1 Basic Scheduler Operation + +In order to utilise radio resources efficiently, MAC in gNB includes dynamic resource schedulers that allocate physical layer resources for the downlink and the uplink. In this clause, an overview of the scheduler is given in terms of scheduler operation, signalling of scheduler decisions, and measurements. + +Scheduler Operation: + +- Taking into account the UE buffer status and the QoS requirements of each UE and associated radio bearers, schedulers assign resources between UEs; +- Schedulers may assign resources taking account the radio conditions at the UE identified through measurements made at the gNB and/or reported by the UE; +- Resource assignment consists of radio resources (resource blocks). + +Signalling of Scheduler Decisions: + +- UEs identify the resources by receiving a scheduling (resource assignment) channel. + +Measurements to Support Scheduler Operation: + +- Uplink buffer status reports (measuring the data that is buffered in the logical channel queues in the UE) are used to provide support for QoS-aware packet scheduling; +- Power headroom reports (measuring the difference between the nominal UE maximum transmit power and the estimated power for uplink transmission) are used to provide support for power aware packet scheduling. + +### 10.2 Downlink Scheduling + +In the downlink, the gNB can dynamically allocate resources to UEs via the C-RNTI on PDCCH(s). A UE always monitors the PDCCH(s) in order to find possible assignments when its downlink reception is enabled (activity governed by DRX and cell DTX when configured). When CA is configured, the same C-RNTI applies to all serving cells. + +The gNB may pre-empt an ongoing PDSCH transmission to one UE with a latency-critical transmission to another UE. The gNB can configure UEs to monitor interrupted transmission indications using INT-RNTI on a PDCCH. If a UE receives the interrupted transmission indication, the UE may assume that no useful information to that UE was carried by the resource elements included in the indication, even if some of those resource elements were already scheduled to this UE. + +In addition, with Semi-Persistent Scheduling (SPS), the gNB can allocate downlink resources for the initial HARQ transmissions to UEs: RRC defines the periodicity of the configured downlink assignments while PDCCH addressed to + +CS-RNTI can either signal and activate the configured downlink assignment, or deactivate it; i.e. a PDCCH addressed to CS-RNTI indicates that the downlink assignment can be implicitly reused according to the periodicity defined by RRC, until deactivated. + +NOTE: When required, retransmissions are explicitly scheduled on PDCCH(s). + +The dynamically allocated downlink reception overrides the configured downlink assignment in the same serving cell, if they overlap in time. Otherwise a downlink reception according to the configured downlink assignment is assumed, if activated. + +The UE may be configured with up to 8 active configured downlink assignments for a given BWP of a serving cell. When more than one is configured: + +- The network decides which of these configured downlink assignments are active at a time (including all of them); and +- Each configured downlink assignment is activated separately using a DCI command and deactivation of configured downlink assignments is done using a DCI command, which can either deactivate a single configured downlink assignment or multiple configured downlink assignments jointly. + +## 10.3 Uplink Scheduling + +In the uplink, the gNB can dynamically allocate resources to UEs via the C-RNTI on PDCCH(s). A UE always monitors the PDCCH(s) in order to find possible grants for uplink transmission when its downlink reception is enabled (activity governed by DRX and cell DTX when configured). When CA is configured, the same C-RNTI applies to all serving cells. + +The gNB may cancel a PUSCH transmission, or a repetition of a PUSCH transmission, or an SRS transmission of a UE for another UE with a latency-critical transmission. The gNB can configure UEs to monitor cancelled transmission indications using CI-RNTI on a PDCCH. If a UE receives the cancelled transmission indication, the UE shall cancel the PUSCH transmission from the earliest symbol overlapped with the resource or the SRS transmission overlapped with the resource indicated by cancellation (see clause 11.2A of TS 38.213 [38]). + +In addition, with Configured Grants, the gNB can allocate uplink resources for the initial HARQ transmissions and HARQ retransmissions to UEs. Two types of configured uplink grants are defined: + +- With Type 1, RRC directly provides the configured uplink grant (including the periodicity). +- With Type 2, RRC defines the periodicity of the configured uplink grant while PDCCH addressed to CS-RNTI can either signal and activate the configured uplink grant, or deactivate it; i.e. a PDCCH addressed to CS-RNTI indicates that the uplink grant can be implicitly reused according to the periodicity defined by RRC, until deactivated. + +If the UE is not configured with enhanced intra-UE overlapping resources prioritization, the dynamically allocated uplink transmission overrides the configured uplink grant in the same serving cell, if they overlap in time. Otherwise an uplink transmission according to the configured uplink grant is assumed, if activated. + +If the UE is configured with enhanced intra-UE overlapping resources prioritization, in case a configured uplink grant transmission overlaps in time with dynamically allocated uplink transmission or with another configured uplink grant transmission in the same serving cell, the UE prioritizes the transmission based on the comparison between the highest priority of the logical channels that have data to be transmitted and which are multiplexed or can be multiplexed in MAC PDUs associated with the overlapping resources. Similarly, in case a configured uplink grant transmissions or a dynamically allocated uplink transmission overlaps in time with a scheduling request transmission, the UE prioritizes the transmission based on the comparison between the priority of the logical channel which triggered the scheduling request and the highest priority of the logical channels that have data to be transmitted and which are multiplexed or can be multiplexed in MAC PDU associated with the overlapping resource. In case the MAC PDU associated with a deprioritized transmission has already been generated, the UE keeps it stored to allow the gNB to schedule a retransmission. The UE may also be configured by the gNB to transmit the stored MAC PDU as a new transmission using a subsequent resource of the same configured uplink grant configuration when an explicit retransmission grant is not provided by the gNB. + +Retransmissions other than repetitions are explicitly allocated via PDCCH(s) or via configuration of a retransmission timer. + +The UE may be configured with up to 12 active configured uplink grants for a given BWP of a serving cell. When more than one is configured, the network decides which of these configured uplink grants are active at a time (including all of them). Each configured uplink grant can either be of Type 1 or Type 2. For Type 2, activation and deactivation of configured uplink grants are independent among the serving cells. When more than one Type 2 configured grant is configured, each configured grant is activated separately using a DCI command and deactivation of Type 2 configured grants is done using a DCI command, which can either deactivate a single configured grant configuration or multiple configured grant configurations jointly. + +When SUL is configured, the network should ensure that an active configured uplink grant on SUL does not overlap in time with another active configured uplink grant on the other UL configuration. + +For both dynamic grant and configured grant, for a transport block, two or more repetitions can be in one slot, or across slot boundary in consecutive available slots with each repetition in one slot. For both dynamic grant and configured grant Type 2, the number of repetitions can be also dynamically indicated in the L1 signalling. The dynamically indicated number of repetitions shall override the RRC configured number of repetitions, if both are present. + +## 10.4 Measurements to Support Scheduler Operation + +Measurement reports are required to enable the scheduler to operate in both uplink and downlink. These include transport volume and measurements of a UE's radio environment. + +Uplink buffer status reports (BSR) are needed to provide support for QoS-aware packet scheduling. In NR, uplink buffer status reports refer to the data that is buffered in for a group of logical channels (LCG) in the UE. Four formats are used for reporting in uplink: + +- A short format to report only one BSR (of one LCG); +- A flexible long format to report several BSRs (up to all eight LCGs); +- An extended short format to report one BSR (of one LCG); +- An extended long format to report several BSRs (up to all 256 LCGs). + +NOTE: The Extended versions of the BSR formats can only be used by IAB nodes. + +Uplink buffer status reports are transmitted using MAC signalling. When a BSR is triggered (e.g. when new data arrives in the transmission buffers of the UE), a Scheduling Request (SR) can be transmitted by the UE (e.g. when no resources are available to transmit the BSR). + +For IAB, the Pre-emptive BSR can be configured on the backhaul links. The Pre-emptive BSR is sent based on expected data rather than buffered data, as described in clause 4.7.3.3. + +Power headroom reports (PHR) are needed to provide support for power-aware packet scheduling. In NR, three types of reporting are supported: a first one for PUSCH transmission, a second one for PUSCH and PUCCH transmission in an LTE Cell Group in EN-DC (see TS 37.340 [21]) and a third one for SRS transmission on SCells configured with SRS only. In case of CA, when no transmission takes place on an activated SCell, a reference power is used to provide a virtual report. To allow network to detect UL power reduction, the PHR reports may also contain Power Management Maximum Power Reduction (P-MPR, see TS 38.101-2 [35]) information that UE uses to ensure UE compliance with the Maximum Permissible Exposure (MPE) exposure regulation for FR2, which is set for limiting RF exposure on human body. Power headroom reports are transmitted using MAC signalling. + +## 10.5 Rate Control + +### 10.5.1 Downlink + +In downlink, for GBR flows, the gNB guarantees the GFBR and ensures that the MFBR is not exceeded while for non-GBR flows, it ensures that the UE-AMBR is not exceeded (see clause 12). When configured for a GBR flow, the gNB also ensures that the MDBV is not exceeded. When received and supported, the gNB in addition ensures that the UE-Slice-MBR is not exceeded as specified in TS 23.501 [3]. + +## 10.5.2 Uplink + +The UE has an uplink rate control function which manages the sharing of uplink resources between logical channels. RRC controls the uplink rate control function by giving each logical channel a priority, a prioritised bit rate (PBR), and a buffer size duration (BSD). The values signalled need not be related to the ones signalled via NG to the gNB. In addition, mapping restrictions can be configured (see clause 16.1.2). + +The uplink rate control function ensures that the UE serves the logical channel(s) in the following sequence: + +1. All relevant logical channels in decreasing priority order up to their PBR; +2. All relevant logical channels in decreasing priority order for the remaining resources assigned by the grant. + +NOTE 1: In case the PBRs are all set to zero, the first step is skipped and the logical channels are served in strict priority order: the UE maximises the transmission of higher priority data. + +NOTE 2: The mapping restrictions tell the UE which logical channels are relevant for the grant received. If no mapping restrictions are configured, all logical channels are considered. + +NOTE 3: Through radio protocol configuration and scheduling, the gNB can guarantee the GFBR(s) and ensure that any of the MFBR(s), the UE-AMBR and, when supported and feasible, the UE-Slice-MBR is not exceeded in uplink (see clause 12). + +NOTE 4: The mapping restrictions allows the gNB to fulfil the MDBV requirements through scheduling at least for the case where logical channels are mapped to separate serving cells. + +If more than one logical channel have the same priority, the UE shall serve them equally. + +## 10.6 Activation/Deactivation Mechanism + +To enable reasonable UE battery consumption when CA is configured, an activation/deactivation mechanism of Cells is supported. When an SCell is deactivated, the UE does not need to receive the corresponding PDCCH or PDSCH, cannot transmit in the corresponding uplink, nor is it required to perform CQI measurements. Conversely, when an SCell is active, the UE shall receive PDSCH and PDCCH (if the UE is configured to monitor PDCCH from this SCell) and is expected to be able to perform CQI measurements. NG-RAN ensures that while PUCCH SCell (a Secondary Cell configured with PUCCH) is deactivated, SCells of secondary PUCCH group (a group of SCells whose PUCCH signalling is associated with the PUCCH on the PUCCH SCell) should not be activated. NG-RAN ensures that SCells mapped to PUCCH SCell are deactivated before the PUCCH SCell is changed or removed. + +When reconfiguring the set of serving cells: + +- SCells added to the set are initially activated or deactivated; +- SCells which remain in the set (either unchanged or reconfigured) do not change their activation status (*activated or deactivated*). + +At handover, LTM cell switch execution or connection resume from RRC\_INACTIVE: + +- SCells are activated or deactivated. + +To enable reasonable UE battery consumption when BA is configured, only one UL BWP for each uplink carrier and one DL BWP or only one DL/UL BWP pair can be active at a time in an active serving cell, all other BWPs that the UE is configured with being deactivated. On deactivated BWPs, the UE does not monitor the PDCCH, does not transmit on PUCCH, PRACH and UL-SCH. + +To enable fast SCell activation when CA is configured, one dormant BWP can be configured for an SCell. If the active BWP of the activated SCell is a dormant BWP, the UE stops monitoring PDCCH and transmitting SRS/PUSCH/PUCCH on the SCell but continues performing CSI measurements, AGC and beam management, if configured. A DCI is used to control entering/leaving the dormant BWP for one or more SCell(s) or one or more SCell group(s). + +The dormant BWP is one of the UE's dedicated BWPs configured by network via dedicated RRC signalling. The SpCell and PUCCH SCell cannot be configured with a dormant BWP. + +To enable fast SCell activation when CA is configured, aperiodic CSI-RS for tracking for fast SCell activation can be configured for an SCell to assist AGC and time/frequency synchronization. A MAC CE is used to trigger activation of one or more SCell(s) and trigger the aperiodic CSI-RS for tracking for fast SCell activation for a (set of) deactivated SCell(s). + +## 10.7 E-UTRA-NR Cell Resource Coordination + +An NR cell may use spectrum that overlaps or is adjacent to spectrum in use for E-UTRA cells. In this case network signalling enables coordination of TDM and FDM cell resources between MAC in the gNB and the corresponding entity in the ng-eNB. Both the gNB and the ng-eNB can trigger the E-UTRA - NR Cell Resource Coordination procedure over Xn to its peer node. + +## 10.8 Cross Carrier Scheduling + +Cross-carrier scheduling with the Carrier Indicator Field (CIF) allows the PDCCH of a serving cell to schedule resources on another serving cell but with the following restrictions: + +- When cross-carrier scheduling from an SCell to PCell is not configured, PCell can only be scheduled via its PDCCH; +- When cross-carrier scheduling from an SCell to PCell is configured: + - PDCCH on that SCell can schedule PCell's PDSCH and PUSCH; + - PDCCH on the PCell can schedule PCell's PDSCH and PUSCH but cannot schedule PDSCH and PUSCH on any other cell; + - Only one SCell can be configured to be used for cross-carrier scheduling to PCell. +- When an SCell is configured with a PDCCH, that cell's PDSCH and PUSCH are always scheduled by the PDCCH on this SCell; +- When an SCell is not configured with a PDCCH, that SCell's PDSCH and PUSCH are always scheduled by a PDCCH on another serving cell; +- The scheduling PDCCH and the scheduled PDSCH/PUSCH can use the same or different numerologies. + +## 10.9 IAB Resource Configuration + +If the IAB-DU and the IAB-MT of an IAB-node are subject to a half-duplex constraint, correct transmission/reception by one cannot be guaranteed during transmission/reception by the other and vice versa, e.g., when collocated and operating in the same frequency. If an IAB-node supports enhanced frequency or spatial multiplexing capabilities, additional multiplexing modes can be supported, i.e., simultaneous operation of IAB-MT Rx / IAB-DU Rx, IAB-MT Tx / IAB-DU Tx, IAB-MT Rx / IAB-DU Tx, IAB-MT Tx / IAB-DU Rx. An IAB-node can report its duplexing constraints between the IAB-MT and the collocated IAB-DU via F1AP. An IAB-node can indicate via F1AP whether or not FDM is required for an enhanced multiplexing operation. + +The scheduler on an IAB-DU or IAB-donor-DU complies with the gNB-DU resource configuration received via F1AP, which defines the usage of scheduling resources to account for the aforementioned duplexing constraint. + +The resource configuration assigns an attribute of hard, soft or unavailable to each symbol of each DU cell. Transmission/reception can occur for symbols configured as hard, whereas scheduling cannot occur, except for some special cases, for symbols configured as unavailable. For symbols configured as soft, scheduling can occur conditionally on an explicit indication of availability by the parent node via DCI format 2\_5, or on an implicit determination of availability by the IAB-node. The implicit determination of availability is determined by the IAB-node depending on whether or not the operation of the IAB-DU would have an impact on the collocated IAB-MT. + +The resource configuration can be shared among neighbouring IAB-nodes and IAB-donors to facilitate interference management, dual connectivity, and enhanced multiplexing. + +To facilitate transitioning from IAB-MT to IAB-DU operation and vice versa, guard symbols can be used to overcome potentially misaligned symbol boundaries between the IAB-MT operation and the IAB-DU operation (e.g., IAB-MT Rx boundaries are not aligned with the IAB-DU Tx boundaries). Specifically, an IAB-node can indicate to a parent node a number of desired guard symbols, while the parent node can indicate to the IAB-node the number of actually provided guard symbols for specific transitions. + +An IAB-node supporting enhanced multiplexing capabilities, i.e., IAB-MT Rx / IAB-DU Rx, IAB-MT Tx / IAB-DU Tx, IAB-MT Rx / IAB-DU Tx, IAB-MT Tx / IAB-DU Rx, can provide via MAC-CE to a parent node information to facilitate scheduling for enhanced multiplexing operation by the IAB-node, specifically: + +- recommended IAB-MT's Tx/Rx beams; +- desired IAB-MT Tx PSD range; +- desired parent node's IAB-DU Tx power adjustment; +- required IAB-MT's uplink transmission timing mode. + +Correspondingly, the parent node can provide information via MAC-CE to the IAB-node to facilitate enhanced multiplexing at the IAB-node and/or at the parent node: + +- restricted IAB-DU Tx beams; +- actual parent node's IAB-DU Tx power adjustment; +- IAB-MT's uplink transmission timing mode. + +## 10.10 Autonomous Denial for IDC + +The network may configure a long-term denial rate per CG by dedicated RRC signalling to limit the amount of NR UL autonomous denials. Once configured by the network, the UE can autonomously deny NR UL transmission. Otherwise, the UE shall not perform any NR UL autonomous denials for IDC. + +--- + +## 11 UE Power Saving + +The PDCCH monitoring activity of the UE in RRC connected mode is governed by DRX, BA, DCP and cell DTX (see clause 15.4.2.3). + +When DRX is configured, the UE does not have to continuously monitor PDCCH. DRX is characterized by the following: + +- **on-duration**: duration that the UE waits for, after waking up, to receive PDCCHs. If the UE successfully decodes a PDCCH, the UE stays awake and starts the inactivity timer; +- **inactivity-timer**: duration that the UE waits to successfully decode a PDCCH, from the last successful decoding of a PDCCH, failing which it can go back to sleep. The UE shall restart the inactivity timer following a single successful decoding of a PDCCH for a first transmission only (i.e. not for retransmissions); +- **retransmission-timer**: duration until a retransmission can be expected; +- **cycle**: specifies the periodic repetition of the on-duration followed by a possible period of inactivity (see figure 11-1 below); +- **active-time**: total duration that the UE monitors PDCCH. This includes the "on-duration" of the DRX cycle, the time UE is performing continuous reception while the inactivity timer has not expired, and the time when the UE is performing continuous reception while waiting for a retransmission opportunity. + +![Figure 11-1: DRX Cycle diagram. The diagram shows a horizontal timeline with two repeating patterns. Each pattern consists of a short white horizontal bar (representing the 'on-duration') followed by a longer black horizontal bar (representing the 'off-duration'). Vertical dashed lines separate the repeating cycles. The first cycle starts with a white bar, and the second cycle starts with a white bar further to the right.](3ec35c497a0765a1a885c85f214b1bef_img.jpg) + +Figure 11-1: DRX Cycle diagram. The diagram shows a horizontal timeline with two repeating patterns. Each pattern consists of a short white horizontal bar (representing the 'on-duration') followed by a longer black horizontal bar (representing the 'off-duration'). Vertical dashed lines separate the repeating cycles. The first cycle starts with a white bar, and the second cycle starts with a white bar further to the right. + +**Figure 11-1: DRX Cycle** + +A SL UE can be configured with DRX, in which case, PDCCH providing SL grants can be sent to the UE only during its active time. + +When BA is configured, the UE only has to monitor PDCCH on the one active BWP i.e. it does not have to monitor PDCCH on the entire DL frequency of the cell. A BWP inactivity timer (independent from the DRX inactivity-timer described above) is used to switch the active BWP to the default one: the timer is restarted upon successful PDCCH decoding and the switch to the default BWP takes place when it expires. + +In addition, the UE may be indicated, when configured accordingly, whether it is required to monitor or not the PDCCH during the next occurrence of the on-duration by a DCP monitored on the active BWP. If the UE does not detect a DCP on the active BWP, it does not monitor the PDCCH during the next occurrence of the on-duration, unless it is explicitly configured to do so in that case. + +A UE can only be configured to monitor DCP when connected mode DRX is configured, and at occasion(s) at a configured offset before the on-duration. More than one monitoring occasion can be configured before the on-duration. The UE does not monitor DCP on occasions occurring during active-time, measurement gaps, BWP switching, or when it monitors response for a CFRA preamble transmission for beam failure recovery (see clause 9.2.6), in which case it monitors the PDCCH during the next on-duration. If no DCP is configured in the active BWP, UE follows normal DRX operation. + +When CA is configured, DCP is only configured on the PCell. + +One DCP can be configured to control PDCCH monitoring during on-duration for one or more UEs independently. + +Power saving in RRC\_IDLE and RRC\_INACTIVE can also be achieved by UE relaxing neighbour cells RRM measurements when it meets the criteria determining it is in low mobility and/or not at cell edge. + +UE power saving may be enabled by adapting the DL maximum number of MIMO layers by BWP switching. + +Power saving is also enabled during active-time via cross-slot scheduling, which facilitates UE to achieve power saving with the assumption that it won't be scheduled to receive PDSCH, triggered to receive A-CSI or transmit a PUSCH scheduled by the PDCCH until the minimum scheduling offsets K0 and K2. Dynamic adaptation of the minimum scheduling offsets K0 and K2 is controlled by PDCCH. + +Serving Cells of a MAC entity may be configured by RRC in two DRX groups with separate DRX parameters. When RRC does not configure a secondary DRX group, there is only one DRX group and all Serving Cells belong to that one DRX group. When two DRX groups are configured, each Serving Cell is uniquely assigned to either of the two groups. The DRX parameters that are separately configured for each DRX group are on-duration and inactivity-timer. + +UE power saving in RRC\_IDLE/RRC\_INACTIVE may be achieved by providing the configuration for TRS with CSI-RS for tracking in TRS occasions. The TRS in TRS occasions may allow UEs in RRC\_IDLE/RRC\_INACTIVE to sleep longer before waking-up for its paging occasion. The TRS occasions configuration is provided in SIB17. The availability of TRS in the TRS occasions is indicated by L1 availability indication. These TRSs may also be used by the UEs configured with eDRX. + +UE power saving may be achieved by UE relaxing measurements for RLM/BFD. When configured, UE determines whether it is in low mobility state and/or whether its serving cell radio link quality is better than a threshold. The configuration for low mobility and good serving cell quality criterion is provided through dedicated RRC signalling. + +RLM and BFD relaxation may be enabled/disabled separately through RRC Configuration. Additionally, RLM relaxation may be enabled/disabled on per Cell Group basis while BFD relaxation may be enabled/disabled on per serving cell basis. + +The UE is only allowed to perform RLM and/or BFD relaxation when relaxed measurement criterion for low mobility and/or for good serving cell quality is met. If configured to do so, the UE shall trigger reporting of its RLM and/or BFD relaxation status through UE assistance information if the UE changes its respective RLM and/or BFD relaxation status while meeting the UE minimum requirements specified in TS 38.133 [13]. + +UE power saving may also be achieved through PDCCH monitoring adaptation mechanisms when configured by the network, including skipping of PDCCH monitoring and Search space set group (SSSG) switching. In this case UE does not monitor PDCCH during the PDCCH skipping duration except for the cases as specified in TS 38.213 [38], or monitors PDCCH according to the search space sets applied in SSSG. + +## 12 QoS + +### 12.1 Overview + +The **5G QoS model** is based on QoS Flows (see TS 23.501 [3]) and supports both QoS Flows that require guaranteed flow bit rate (GBR QoS Flows) and QoS Flows that do not require guaranteed flow bit rate (non-GBR QoS Flows). At NAS level (see TS 23.501 [3]), the QoS flow is thus the finest granularity of QoS differentiation in a PDU session. A QoS flow is identified within a PDU session by a QoS Flow ID (QFI) carried in an encapsulation header over NG-U. + +The **QoS architecture** in NG-RAN, both for NR connected to 5GC and for E-UTRA connected to 5GC, is depicted in the Figure 12-1 and described in the following: + +- For each UE, 5GC establishes one or more PDU Sessions; +- Except for NB-IoT, IAB-MT in SA mode, and NCR-MT, for each UE, the NG-RAN establishes at least one Data Radio Bearers (DRB) together with the PDU Session and additional DRB(s) for QoS flow(s) of that PDU session can be subsequently configured (it is up to NG-RAN when to do so); +- If NB-IoT UE supports NG-U data transfer, the NG-RAN may establish Data Radio Bearers (DRB) together with the PDU Session and one PDU session maps to only one DRB; +- The NG-RAN maps packets belonging to different PDU sessions to different DRBs; +- NAS level packet filters in the UE and in the 5GC associate UL and DL packets with QoS Flows; +- AS-level mapping rules in the UE and in the NG-RAN associate UL and DL QoS Flows with DRBs. + +![Diagram of QoS architecture showing the mapping of QoS flows to Data Radio Bearers (DRBs) within a UE and NG-RAN.](d2754c0f61ae5c9ddc3dbf38cecaff86_img.jpg) + +The diagram illustrates the QoS architecture within a User Equipment (UE) and an NG-RAN. The UE is represented by a green vertical rectangle on the left, and the NG-RAN is represented by an orange vertical rectangle on the right. Between them, a stack of five horizontal white rectangles represents the protocol layers. At the top and bottom of this stack, blue rectangles represent the PDU Session anchors. Vertical dashed lines indicate the mapping of QoS flows (represented by colored segments within the protocol layers) to Data Radio Bearers (DRBs, represented by the horizontal white rectangles). The mapping shows multiple QoS flows being aggregated into a single DRB, and different DRBs being used for different QoS flows. + +Diagram of QoS architecture showing the mapping of QoS flows to Data Radio Bearers (DRBs) within a UE and NG-RAN. + +Figure 12-1: QoS architecture + +NG-RAN and 5GC ensure quality of service (e.g. reliability and target delay) by mapping packets to appropriate QoS Flows and DRBs. Hence there is a 2-step mapping of IP-flows to QoS flows (NAS) and from QoS flows to DRBs (Access Stratum). + +At **NAS level**, a QoS flow is characterised by a QoS profile provided by 5GC to NG-RAN and QoS rule(s) provided by 5GC to the UE. The QoS profile is used by NG-RAN to determine the treatment on the radio interface while the QoS rules dictates the mapping between uplink User Plane traffic and QoS flows to the UE. A QoS flow may either be GBR or Non-GBR depending on its profile. The QoS profile of a QoS flow contains QoS parameters, for instance (see TS 23.501 [3]): + +- For each QoS flow: + - A 5G QoS Identifier (5QI); + - An Allocation and Retention Priority (ARP). +- In case of a GBR QoS flow only: + - Guaranteed Flow Bit Rate (GFBR) for both uplink and downlink; + - Maximum Flow Bit Rate (MFBR) for both uplink and downlink; + - Maximum Packet Loss Rate for both uplink and downlink; + - Delay Critical Resource Type; + - Notification Control. + +NOTE: The Maximum Packet Loss Rate (UL, DL) is only provided for a GBR QoS flow belonging to voice media. + +- In case of Non-GBR QoS only: + - Reflective QoS Attribute (RQA): the RQA, when included, indicates that some (not necessarily all) traffic carried on this QoS flow is subject to reflective quality of service (RQoS) at NAS; + - Additional QoS Flow Information. + +The QoS parameter Notification Control indicates whether notifications are requested from the RAN when the GFBR can no longer (or again) be fulfilled for a QoS Flow. If, for a given GBR QoS Flow, notification control is enabled and the RAN determines that the GFBR cannot be guaranteed, RAN shall send a notification towards SMF and keep the QoS Flow (i.e. while the NG-RAN is not delivering the requested GFBR for this QoS Flow), unless specific conditions at the NG-RAN require the release of the NG-RAN resources for this GBR QoS Flow, e.g. due to Radio link failure or RAN internal congestion. When applicable, NG-RAN sends a new notification, informing SMF that the GFBR can be guaranteed again. + +If Alternative QoS parameters Sets are received with the Notification Control parameter, the NG-RAN may also include in the notification a reference corresponding to the QoS Parameter Set which it can currently fulfil as specified in TS 23.501 [3]. The target NG-RAN node may include in the notification control indication the reference to the QoS Parameter Set which it can currently fulfil over Xn to the source NG-RAN node during handover. + +In addition, an Aggregate Maximum Bit Rate is associated to each PDU session (Session-AMBR), to each UE (UE-AMBR) and to each slice per UE (UE-Slice-MBR). The Session-AMBR limits the aggregate bit rate that can be expected to be provided across all Non-GBR QoS Flows for a specific PDU Session and is ensured by the UPF. The UE-AMBR limits the aggregate bit rate that can be expected to be provided across all Non-GBR QoS Flows of a UE and is ensured by the RAN (see clause 10.5.1). The UE-Slice-MBR limits the aggregate bit rate that can be expected to be provided across all GBR and Non-GBR QoS Flows corresponding to PDU Sessions of the UE for the same slice (S-NSSAI) as specified in TS 23.501 [3] and is ensured by the RAN (see clause 10.5.1). + +The 5QI is associated to QoS characteristics giving guidelines for setting node specific parameters for each QoS Flow. Standardized or pre-configured 5G QoS characteristics are derived from the 5QI value and are not explicitly signalled. Signalled QoS characteristics are included as part of the QoS profile. The QoS characteristics consist for instance of (see TS 23.501 [3]): + +- Priority level; + +- Packet Delay Budget (including Core Network Packet Delay Budget); +- Packet Error Rate; +- Averaging window; +- Maximum Data Burst Volume. + +At **Access Stratum** level, the data radio bearer (DRB) defines the packet treatment on the radio interface (Uu). A DRB serves packets with the same packet forwarding treatment. The QoS flow to DRB mapping by NG-RAN is based on QFI and the associated QoS profiles (i.e. QoS parameters and QoS characteristics). Separate DRBs may be established for QoS flows requiring different packet forwarding treatment, or several QoS Flows belonging to the same PDU session can be multiplexed in the same DRB. + +In the uplink, the mapping of QoS Flows to DRBs is controlled by mapping rules which are signalled in two different ways: + +- **Reflective mapping:** for each DRB, the UE monitors the QFI(s) of the downlink packets and applies the same mapping in the uplink; that is, for a DRB, the UE maps the uplink packets belonging to the QoS flows(s) corresponding to the QFI(s) and PDU Session observed in the downlink packets for that DRB. To enable this reflective mapping, the NG-RAN marks downlink packets over Uu with QFI. +- **Explicit Configuration:** QoS flow to DRB mapping rules can be explicitly signalled by RRC. + +The UE always applies the latest update of the mapping rules regardless of whether it is performed via reflecting mapping or explicit configuration. + +When a QoS flow to DRB mapping rule is updated, the UE sends an end marker on the old bearer. + +In the downlink, the QFI is signalled by NG-RAN over Uu for the purpose of RQoS and if neither NG-RAN, nor the NAS (as indicated by the RQA) intend to use reflective mapping for the QoS flow(s) carried in a DRB, no QFI is signalled for that DRB over Uu. In the uplink, NG-RAN can configure the UE to signal QFI over Uu. + +For each PDU session, a default DRB may be configured: if an incoming UL packet matches neither an RRC configured nor a reflective mapping rule, the UE then maps that packet to the default DRB of the PDU session. For non-GBR QoS flows, the 5GC may send to the NG-RAN the Additional QoS Flow Information parameter associated with certain QoS flows to indicate that traffic is likely to appear more often on them compared to other non-GBR QoS flows established on the same PDU session. + +Within each PDU session, it is up to NG-RAN how to map multiple QoS flows to a DRB. The NG-RAN may map a GBR flow and a non-GBR flow, or more than one GBR flow to the same DRB, but mechanisms to optimise these cases are not within the scope of standardization. + +## 12.2 Explicit Congestion Notification + +The gNB and the UE support of the Explicit Congestion Notification (ECN) is specified in clause 5 of [27]. + +--- + +## 13 Security + +### 13.1 Overview and Principles + +The following principles apply to NR connected to 5GC security, see TS 33.501 [5]: + +- For user data (DRBs), ciphering provides user data confidentiality and integrity protection provides user data integrity; +- For RRC signalling (SRBs), ciphering provides signalling data confidentiality and integrity protection signalling data integrity; + +NOTE: Ciphering and integrity protections are optionally configured except for RRC signalling for which integrity protection is always configured. Ciphering and integrity protection can be configured per DRB but all DRBs belonging to a PDU session for which the User Plane Security Enforcement information indicates that UP integrity protection is required (see TS 23.502 [22]), are configured with integrity protection. + +- For key management and data handling, any entity processing cleartext shall be protected from physical attacks and located in a secure environment; +- The gNB (AS) keys are cryptographically separated from the 5GC (NAS) keys; +- Separate AS and NAS level Security Mode Command (SMC) procedures are used; +- A sequence number (COUNT) is used as input to the ciphering and integrity protection and a given sequence number must only be used once for a given key (except for identical re-transmission) on the same radio bearer in the same direction. + +The keys are organised and derived as follows: + +- Key for AMF: + - $K_{AMF}$ is a key derived by ME and SEAF from $K_{SEAF}$ . +- Keys for NAS signalling: + - $K_{NASint}$ is a key derived by ME and AMF from $K_{AMF}$ , which shall only be used for the protection of NAS signalling with a particular integrity algorithm; + - $K_{NASenc}$ is a key derived by ME and AMF from $K_{AMF}$ , which shall only be used for the protection of NAS signalling with a particular encryption algorithm. + +Key for gNB: + +- $K_{gNB}$ is a key derived by ME and AMF from $K_{AMF}$ . $K_{gNB}$ is further derived by ME and source gNB when performing horizontal or vertical key derivation. + +Keys for UP traffic: + +- $K_{UPenc}$ is a key derived by ME and gNB from $K_{gNB}$ , which shall only be used for the protection of UP traffic between ME and gNB with a particular encryption algorithm; +- $K_{UPint}$ is a key derived by ME and gNB from $K_{gNB}$ , which shall only be used for the protection of UP traffic between ME and gNB with a particular integrity algorithm. + +Keys for RRC signalling: + +- $K_{RRCint}$ is a key derived by ME and gNB from $K_{gNB}$ , which shall only be used for the protection of RRC signalling with a particular integrity algorithm; +- $K_{RRCenc}$ is a key derived by ME and gNB from $K_{gNB}$ , which shall only be used for the protection of RRC signalling with a particular encryption algorithm. + +Intermediate keys: + +- NH is a key derived by ME and AMF to provide forward security. +- $K_{gNB}^*$ is a key derived by ME and gNB when performing a horizontal or vertical key derivation. + +The primary authentication enables mutual authentication between the UE and the network and provide an anchor key called $K_{SEAF}$ . From $K_{SEAF}$ , $K_{AMF}$ is created during e.g. primary authentication or NAS key re-keying and key refresh events. Based on $K_{AMF}$ , $K_{NASint}$ and $K_{NASenc}$ are then derived when running a successful NAS SMC procedure. + +Whenever an initial AS security context needs to be established between UE and gNB, AMF and the UE derive a $K_{gNB}$ and a Next Hop parameter (NH). The $K_{gNB}$ and the NH are derived from the $K_{AMF}$ . A NH Chaining Counter (NCC) is associated with each $K_{gNB}$ and NH parameter. Every $K_{gNB}$ is associated with the NCC corresponding to the NH value from which it was derived. At initial setup, the $K_{gNB}$ is derived directly from $K_{AMF}$ , and is then considered to be + +associated with a virtual NH parameter with NCC value equal to zero. At initial setup, the derived NH value is associated with the NCC value one. On handovers, the basis for the $K_{gNB}$ that will be used between the UE and the target gNB, called $K_{gNB}^*$ , is derived from either the currently active $K_{gNB}$ or from the NH parameter. If $K_{gNB}^*$ is derived from the currently active $K_{gNB}$ , this is referred to as a horizontal key derivation and is indicated to UE with an NCC that does not increase. If the $K_{gNB}^*$ is derived from the NH parameter, the derivation is referred to as a vertical key derivation and is indicated to UE with an NCC increase. Finally, $K_{RRCint}$ , $K_{RRCenc}$ , $K_{UPint}$ and $K_{UPenc}$ are derived based on $K_{gNB}$ after a new $K_{gNB}$ is derived. This is depicted on Figure 13.1-1 below: + +![Figure 13.1-1: 5G Key Derivation diagram. The diagram shows a flow of key derivation starting from a top box (AMF) down to a central box (gNB). From the gNB, the flow splits into four parallel boxes representing the derivation of K_RRCint, K_RRCenc, K_UPint, and K_UPenc. A large black arrow on the left points downwards, indicating the sequence of operations. A feedback loop is shown from the bottom of the four parallel boxes back up to the gNB box.](8768e42bf1062f1af11f259fc52a92e9_img.jpg) + +Figure 13.1-1: 5G Key Derivation diagram. The diagram shows a flow of key derivation starting from a top box (AMF) down to a central box (gNB). From the gNB, the flow splits into four parallel boxes representing the derivation of K\_RRCint, K\_RRCenc, K\_UPint, and K\_UPenc. A large black arrow on the left points downwards, indicating the sequence of operations. A feedback loop is shown from the bottom of the four parallel boxes back up to the gNB box. + +**Figure 13.1-1: 5G Key Derivation** + +With such key derivation, a gNB with knowledge of a $K_{gNB}$ , shared with a UE, is unable to compute any previous $K_{gNB}$ that has been used between the same UE and a previous gNB, therefore providing backward security. Similarly, a gNB with knowledge of a $K_{gNB}$ , shared with a UE, is unable to predict any future $K_{gNB}$ that will be used between the same UE and another gNB after n or more handovers (since NH parameters are only computable by the UE and the AMF). + +The AS SMC procedure is for RRC and UP security algorithms negotiation and RRC security activation. When AS security context is to be established in the gNB, the AMF sends the complete UE 5G security capabilities to the gNB (i.e., all bits for every capability defined in TS 24.501 [28] and received in NAS signalling). At handover (or at UE Context retrieval), the complete UE 5G security capabilities are also sent by the source gNB to the target gNB (or by the last serving gNB to the receiving gNB respectively). The gNB chooses the ciphering algorithm which has the highest priority from its configured list and is also present in the UE 5G security capabilities. The gNB also chooses the integrity algorithm which has the highest priority from its configured list and is also present in the UE 5G security capabilities. The chosen algorithms are indicated to the UE in the AS SMC and this message is integrity protected. RRC downlink ciphering (encryption) at the gNB starts after sending the AS SMC message. RRC uplink deciphering (decryption) at the gNB starts after receiving and successful verification of the integrity protected AS security mode complete message from the UE. The UE verifies the validity of the AS SMC message from the gNB by verifying the integrity of the received message. RRC uplink ciphering (encryption) at the UE starts after sending the AS security mode complete message. RRC downlink deciphering (decryption) at the UE shall start after receiving and successful verification of the AS SMC message. The RRC Connection Reconfiguration procedure used to add DRBs shall be performed only after RRC security has been activated as part of the AS SMC procedure. + +A UE connected to 5GC, shall support integrity protected DRBs at any data rate, up to and including the highest data rate supported by the UE for both UL and DL. In case of failed integrity check (i.e. faulty or missing MAC-I), the concerned PDU shall be discarded by the receiving PDCP entity. + +Key refresh is possible for $K_{gNB}$ , $K_{RRC-enc}$ , $K_{RRC-int}$ , $K_{UP-enc}$ , and $K_{UP-int}$ and can be initiated by the gNB when a PDCP COUNTs are about to be re-used with the same Radio Bearer identity and with the same $K_{gNB}$ . Key re-keying is also possible for the $K_{gNB}$ , $K_{RRC-enc}$ , $K_{RRC-int}$ , $K_{UP-enc}$ , and $K_{UP-int}$ and can be initiated by the AMF when a 5G AS security context different from the currently active one shall be activated. + +## 13.2 Security Termination Points + +The table below describes the security termination points. + +**Table 13.2-1 Security Termination Points** + +| | Ciphering | Integrity Protection | +|-----------------|-----------|----------------------| +| NAS Signalling | AMF | AMF | +| RRC Signalling | gNB | gNB | +| User Plane Data | gNB | gNB | + +## 13.3 State Transitions and Mobility + +As a general principle, on RRC\_IDLE to RRC\_CONNECTED transitions, RRC protection keys and UP protection keys are generated while keys for NAS protection as well as higher layer keys are assumed to be already available. These higher layer keys may have been established as a result of an AKA run, or as a result of a transfer from another AMF during handover or idle mode mobility see TS 23.502 [22]). + +On RRC\_CONNECTED to RRC\_IDLE transitions, the gNBs deletes the keys it stores for that UE such that state information for idle mode UEs only has to be maintained in AMF. It is also assumed that gNB does no longer store state information about the corresponding UE and deletes the current keys from its memory. In particular, on connected to idle transitions: + +- The gNB and UE delete NH, $K_{gNB}$ , $K_{RRInt}$ , $K_{RREnc}$ , $K_{UPInt}$ and $K_{UPEnc}$ and related NCC; +- AMF and UE keeps $K_{AMF}$ , $K_{NASInt}$ and $K_{NASEnc}$ stored. + +On mobility with vertical key derivation the NH is further bound to the target PCI and its frequency ARFCN-DL before it is taken into use as the $K_{gNB}$ in the target gNB. On mobility with horizontal key derivation the currently active $K_{gNB}$ is further bound to the target PCI and its frequency ARFCN-DL before it is taken into use as the $K_{gNB}$ in the target gNB (see clause 13.1). In both cases, ARFCN-DL is the absolute frequency of SSB of the target PCell. + +It is not required to change the AS security algorithms during intra-gNB-CU handover. If the UE does not receive an indication of new AS security algorithms during an intra-gNB-CU handover, the UE shall continue to use the same algorithms as before the handover (see TS 38.331 [12]). + +## 14 UE Capabilities + +The UE capabilities in NR rely on a hierarchical structure where each capability parameter is defined per UE, per duplex mode (FDD/TDD), per frequency range (FR1/FR2), per band, per band combinations, ... as the UE may support different functionalities depending on those (see TS 38.306 [11]). + +NOTE 1: Some capability parameters are always defined per UE (e.g. SDAP, PDCP and RLC parameters) while some other not always (e.g. MAC and Physical Layer Parameters). + +The UE capabilities in NR do not rely on UE categories: UE categories associated to fixed peak data rates are only defined for marketing purposes and not signalled to the network. Instead, the peak data rate for a given set of aggregated carriers in a band or band combination is the sum of the peak data rates of each individual carrier in that band or band combination, where the peak data rate of each individual carrier is computed according to the capabilities supported for that carrier in the corresponding band or band combination. + +For each block of contiguous serving cells in a band, the set of features supported thereon is defined in a Feature Set (FS). The UE may indicate several Feature Sets for a band (also known as feature sets per band) to advertise different alternative features for the associated block of contiguous serving cells in that band. The two-dimensional matrix of feature sets for all the bands of a band combination (i.e. all the feature sets per band) is referred to as a feature set combination. In a feature set combination, the number of feature sets per band is equal to the number of band entries in the corresponding band combination, and all feature sets per band have the same number of feature sets. Each band combination is linked to one feature set combination. This is depicted on Figure 14-1 below: + +![Diagram illustrating Feature Set Combinations. The top part shows a stack of boxes representing 'band combinations', containing 'Band 1', 'Band 2', '...', and 'Band z'. The bottom part shows a stack of boxes representing 'feature set combinations', containing columns for each band: 'FS 1,1', 'FS 1,2', '...', 'FS 1,n' for Band 1; 'FS 2,1', 'FS 2,2', '...', 'FS 2,n' for Band 2; and 'FS z,1', 'FS z,2', '...', 'FS z,n' for Band z. Arrows indicate that 'band combinations' lead to 'feature set combinations', and 'feature sets per band' lead to the columns of 'feature set combinations'.](92724c769da9d46b730fde1a6dccb023_img.jpg) + +The diagram illustrates the relationship between band combinations and feature set combinations. At the top, a stack of boxes represents 'band combinations', containing 'Band 1', 'Band 2', '...', and 'Band z'. At the bottom, a stack of boxes represents 'feature set combinations', containing columns for each band: 'FS 1,1', 'FS 1,2', '...', 'FS 1,n' for Band 1; 'FS 2,1', 'FS 2,2', '...', 'FS 2,n' for Band 2; and 'FS z,1', 'FS z,2', '...', 'FS z,n' for Band z. Arrows indicate that 'band combinations' lead to 'feature set combinations', and 'feature sets per band' lead to the columns of 'feature set combinations'. + +Diagram illustrating Feature Set Combinations. The top part shows a stack of boxes representing 'band combinations', containing 'Band 1', 'Band 2', '...', and 'Band z'. The bottom part shows a stack of boxes representing 'feature set combinations', containing columns for each band: 'FS 1,1', 'FS 1,2', '...', 'FS 1,n' for Band 1; 'FS 2,1', 'FS 2,2', '...', 'FS 2,n' for Band 2; and 'FS z,1', 'FS z,2', '...', 'FS z,n' for Band z. Arrows indicate that 'band combinations' lead to 'feature set combinations', and 'feature sets per band' lead to the columns of 'feature set combinations'. + +**Figure 14-1: Feature Set Combinations** + +In addition, for some features in intra-band contiguous CA, the UE reports its capabilities individually per carrier. Those capability parameters are sent in feature set per component carrier and they are signalled in the corresponding FSs (per Band) i.e. for the corresponding block of contiguous serving cells in a band. The capability applied to each individual carrier in a block is agnostic to the order in which they are signalled in the corresponding FS. + +NOTE 2: For intra-band non-contiguous CA, there are as many feature sets per band signalled as the number of (groups of contiguous) carriers that the UE is able to aggregate non-contiguously in the corresponding band. + +To limit signalling overhead, the gNB can request the UE to provide NR capabilities for a restricted set of bands. When responding, the UE can skip a subset of the requested band combinations when the corresponding UE capabilities are the same. An eRedCap UE may ignore UE capability filtering and send all supported bands in the mirrored UE capability filter with an explicit indication on whether the filter was ignored or not. + +If supported by the UE and the network, the UE may provide an ID in NAS signalling that represents its radio capabilities for one or more RATs in order to reduce signalling overhead. The ID may be assigned either by the manufacturer or by the serving PLMN. The manufacturer-assigned ID corresponds to a pre-provisioned set of capabilities. In the case of the PLMN-assigned ID, assignment takes place in NAS signalling. + +The AMF stores the UE Radio Capability uploaded by the gNB as specified in TS 23.501 [3]. + +The gNB can request the UE capabilities for RAT-Types NR, EUTRA, UTRA-FDD. The UTRAN capabilities, i.e. the INTER RAT HANDOVER INFO, include START-CS, START-PS and "predefined configurations", which are "dynamic" IEs. In order to avoid the START values desynchronisation and the key replaying issue, the gNB always requests the UE UTRA-FDD capabilities before handover to UTRA-FDD. The gNB does not upload the UE UTRA-FDD capabilities to the AMF. + +## 15 Self-Configuration and Self-Optimisation + +### 15.1 Definitions + +Void. + +### 15.2 Void + +### 15.3 Self-configuration + +#### 15.3.1 Dynamic configuration of the NG-C interface + +##### 15.3.1.1 Prerequisites + +The following prerequisites are assumed: + +- An initial remote IP end point to be used for SCTP initialisation is provided to the NG-RAN node for each AMF the NG-RAN node is supposed to connect to. + +##### 15.3.1.2 SCTP initialization + +NG-RAN establishes the first SCTP (IETF RFC 4960 [23]) using a configured IP address. + +NOTE: The NG-RAN node may use different source and/or destination IP end point(s) if the SCTP establishment towards one IP end point fails. How the NG-RAN node gets the remote IP end point(s) and its own IP address are outside the scope of this specification. + +##### 15.3.1.3 Application layer initialization + +Once SCTP connectivity has been established, the NG-RAN node and the AMF shall exchange application level configuration data over NGAP with the NG Setup procedure, which is needed for these two nodes to interwork correctly on the NG interface: + +- The NG-RAN node provides the relevant configuration information to the AMF, which includes list of supported TA(s), etc.; +- The AMF provides the relevant configuration information to the NG-RAN node, which includes PLMN ID, etc.; +- When the application layer initialization is successfully concluded, the dynamic configuration procedure is completed and the NG-C interface is operational. + +After the application layer initialization is successfully completed, the AMF may add or update or remove SCTP endpoints to be used for NG-C signalling between the AMF and the NG-RAN node pair as specified in TS 23.501 [3]. + +#### 15.3.2 Dynamic Configuration of the Xn interface + +##### 15.3.2.1 Prerequisites + +The following prerequisites are necessary: + +- An initial remote IP end point to be used for SCTP initialisation is provided to the NG-RAN node. + +##### 15.3.2.2 SCTP initialization + +NG-RAN establishes the first SCTP (IETF RFC 4960 [23]) using a configured IP address. + +NOTE: The NG-RAN node may use different source and/or destination IP end point(s) if the SCTP establishment towards one IP end point fails. + +### 15.3.2.3 Application layer initialization + +Once SCTP connectivity has been established, the NG-RAN node and its candidate peer NG-RAN node are in a position to exchange application level configuration data over XnAP needed for the two nodes to interwork correctly on the Xn interface: + +- The NG-RAN node provides the relevant configuration information to the candidate NG-RAN node, which includes served cell information; +- The candidate NG-RAN node provides the relevant configuration information to the initiating NG-RAN node, which includes served cell information; +- When the application layer initialization is successfully concluded, the dynamic configuration procedure is completed and the Xn interface is operational; +- The NG-RAN node shall keep neighbouring NG-RAN nodes updated with the complete list of served cells, or, if requested by the peer NG-RAN node, by a limited list of served cells, while the Xn interface is operational. + +### 15.3.3 Automatic Neighbour Cell Relation Function + +#### 15.3.3.1 General + +The purpose of ANR function is to relieve the operator from the burden of manually managing NCRs. Figure 15.3.3.1-1 shows ANR and its environment: + +![Diagram showing the interaction between gNB and OAM due to ANR. It includes a Neighbour Cell Relation Table, an ANR function block with NCRT Management, Neighbour Removal, and Neighbour Detection functions, and an RRC function.](c71fd22661fbd344a66043940bbd84fc_img.jpg) + +The diagram illustrates the architecture of the Automatic Neighbour Cell Relation (ANR) function within a gNB. At the top, the OAM (Operations, Administration, and Management) block is connected to the gNB via two vertical arrows: 'NCR report' (upwards) and 'Add/Update NCR' (downwards). Below OAM is a large box labeled 'gNB' containing the 'ANR function' (shaded orange). Inside the ANR function, there is a central 'NCRT Management Function' box. To its right are two other boxes: 'Neighbour Removal Function' and 'Neighbour Detection Function'. Arrows indicate interactions: 'NCR\_remove' from Removal to Management, 'NCR\_add' from Detection to Management, and 'NCR\_update' from Management to the 'Neighbour Cell Relation Table'. The 'Internal Information' from OAM also feeds into the Management function. At the bottom of the gNB box is the 'RRC' (Radio Resource Control) function, which sends 'Mrmnt requests' to the Detection function and receives 'Mrmnt reports' from it. On the left, the 'Neighbour Cell Relation Table' is shown with the following structure: + +| Neighbour Cell Relation | | O&M controlled Attributes | | | +|-------------------------|-------|---------------------------|-------|-------| +| NCR | TCI | No Remove | No HO | Nb Xn | +| 1 | TCI#1 | | | | +| 2 | TCI#1 | X | | X | +| 3 | TCI#1 | X | | | +| | | | | | + +Diagram showing the interaction between gNB and OAM due to ANR. It includes a Neighbour Cell Relation Table, an ANR function block with NCRT Management, Neighbour Removal, and Neighbour Detection functions, and an RRC function. + +Figure 15.3.3.1-1: Interaction between gNB and OAM due to ANR + +The ANR function resides in the gNB and manages the Neighbour Cell Relation Table (NCRT). Located within ANR, the Neighbour Detection Function finds new neighbours and adds them to the NCRT. ANR also contains the Neighbour Removal Function which removes outdated NCRs. The Neighbour Detection Function and the Neighbour Removal Function are implementation specific. + +An existing NCR from a source cell to a target cell means that gNB controlling the source cell: + +- a) Knows the global and physical IDs (e.g. NR CGI/NR PCI, ECGI/PCI) of the target cell; and +- b) Has an entry in the NCRT for the source cell identifying the target cell; and +- c) Has the attributes in this NCRT entry defined, either by OAM or set to default values. + +NCRs are cell-to-cell relations, while an Xn link is set up between two gNBs. Neighbour Cell Relations are unidirectional, while an Xn link is bidirectional. + +NOTE: The neighbour information exchange, which occurs during the Xn Setup procedure or in the gNB Configuration Update procedure, may be used for ANR purpose. + +The ANR function also allows OAM to manage the NCRT. OAM can add and delete NCRs. It can also change the attributes of the NCRT. The OAM system is informed about changes in the NCRT. + +### 15.3.3.2 Intra-system Automatic Neighbour Cell Relation Function + +ANR relies on NCGI (see clause 8.2) and ANR reporting of E-UTRA cells as specified in TS 36.300 [2]. + +![Sequence diagram illustrating the Automatic Neighbour Relation Function. It shows three entities: Cell A (Phy-CID=3, Global-CID=17), UE, and Cell B (Phy-CID=5, Global-CID=19). The sequence of messages is: 1. UE sends a 'Report' to Cell A with 'Phy-CID=5, strong signal'; 2. Cell A sends a 'Report Global-CID Request' to the UE with 'Target Phy-CID=5'; 3. UE sends a 'Report Global-CID=19' to Cell A. A dashed line labeled '2b. BCCH (...)' indicates a broadcast channel from Cell B to the UE.](61c77cded492bbcd03eff79c850d92c2_img.jpg) + +``` + +sequenceDiagram + participant Cell A as Cell A +Phy-CID=3 +Global-CID=17 + participant UE + participant Cell B as Cell B +Phy-CID=5 +Global-CID=19 + Note right of Cell A: 1. Report +(Phy-CID=5, strong signal) + Cell A->>UE: 2. Report Global-CID Request +(Target Phy-CID=5) + Note right of Cell B: 2b. BCCH (...) + Note right of UE: 3. Report Global-CID=19 + UE->>Cell A: 3. Report Global-CID=19 + +``` + +Sequence diagram illustrating the Automatic Neighbour Relation Function. It shows three entities: Cell A (Phy-CID=3, Global-CID=17), UE, and Cell B (Phy-CID=5, Global-CID=19). The sequence of messages is: 1. UE sends a 'Report' to Cell A with 'Phy-CID=5, strong signal'; 2. Cell A sends a 'Report Global-CID Request' to the UE with 'Target Phy-CID=5'; 3. UE sends a 'Report Global-CID=19' to Cell A. A dashed line labeled '2b. BCCH (...)' indicates a broadcast channel from Cell B to the UE. + +**Figure 15.3.3.2-1: Automatic Neighbour Relation Function** + +Figure 15.3.3.2-1 depicts an example where the NG-RAN node serving cell A has an ANR function. In RRC\_CONNECTED, the NG-RAN node instructs each UE to perform measurements on neighbour cells. The NG-RAN node may use different policies for instructing the UE to do measurements, and when to report them to the NG-RAN node. This measurement procedure is as specified in TS 38.331[12] and TS 36.331 [29]. + +1. The UE sends a measurement report regarding cell B. This report contains Cell B's PCI, but not its NCGI/ECGI. + +When the NG-RAN node receives a UE measurement report containing the PCI, the following sequence may be used. + +2. The NG-RAN node instructs the UE, using the newly discovered PCI as parameter, to read all the broadcast NCGI(s)/ECGI(s), TAC(s), RANAC(s), PLMN ID(s) and, for neighbour NR cells, NR frequency band(s) and the gNB ID length(s). To do so, the NG-RAN node may need to schedule appropriate idle periods to allow the UE to read the NCGI/ECGI from the broadcast channel of the detected neighbour cell. How the UE reads the NCGI/ECGI is specified in TS 38.331 [12] and TS 36.331 [29]. +3. When the UE has found out the new cell's NCGI(s)/ECGI(s), the UE reports all the broadcast NCGI(s)/ECGI(s) to the serving cell NG-RAN node. In addition, the UE reports all the tracking area code(s), RANAC(s), PLMN IDs and, for neighbour NR cells, NR frequency band(s), and the gNB ID length(s) that have been read by the UE. In case the detected NR cell does not broadcast SIB1, the UE may report *noSIB1* indication as specified in TS 38.331 [12]. +4. The NG-RAN node decides to add this neighbour relation, and can use PCI and NCGI(s)/ECGI(s) to: + - a. Lookup a transport layer address to the new NG-RAN node; + - b. Update the Neighbour Cell Relation List; + - c. If needed, setup a new Xn interface towards this NG-RAN node. + +15.3.3.3 Void + +15.3.3.4 Void + +### 15.3.3.5 Inter-system Automatic Neighbour Cell Relation Function + +For Inter-system ANR, each cell contains an Inter Frequency Search list. This list contains all frequencies that shall be searched. Figure 15.3.3.5-1 depicts an example where the NG-RAN node serving cell A has an ANR function. + +![Sequence diagram illustrating the Automatic Neighbour Relation Function (ANR) in the case of an E-UTRAN detected cell. The diagram shows interactions between Cell A (NR), a UE, and Cell B (LTE).](a1b35c85c93d7a2e30d1feea2faac2e6_img.jpg) + +``` + +sequenceDiagram + participant Cell A + participant UE + participant Cell B + Note right of Cell A: Cell A Type=NR, Phy-CID=3, Global-CID=17 + Note right of Cell B: Cell B Type=LTE, Phy-CID=PSC=5, Global-CID=19 + Cell A->>UE: 1. Report Neighbour Request (RAT, Frequency) + UE-->>Cell A: 2. Report Neighbour Response (Phy-CID, Signal Level) + Cell A->>UE: 3. Report Global-CID Request (Target Phy-CID=5) + Note right of UE: 3b. BCCH (...) + UE-->>Cell A: 4. Report Global-CID=19 + +``` + +Sequence diagram illustrating the Automatic Neighbour Relation Function (ANR) in the case of an E-UTRAN detected cell. The diagram shows interactions between Cell A (NR), a UE, and Cell B (LTE). + +**Figure 15.3.3.5-1: Automatic Neighbour Relation Function in case of E-UTRAN detected cell** + +In RRC\_CONNECTED, the NG-RAN node instructs a UE to perform measurements and detect E-UTRA cells connected to EPC.: + +- 1 The NG-RAN node instructs a UE to look for neighbour cells in the target system. To do so the NG-RAN node may need to schedule appropriate idle periods to allow the UE to scan all cells in the target system. +- 2 The UE reports the PCI and carrier frequency of the detected cells in the target system. + +NOTE: The NG-RAN node may use different policies for instructing the UE to do measurements, and when to report them to the NG-RAN node. + +When the NG-RAN node receives the UE reports containing PCIs of cell(s), the following sequence may be used: + +- 3 The NG-RAN node instructs the UE, using the newly discovered PCI as parameter, to read the ECGI, the TAC and all available PLMN ID(s) of the newly detected cell in case of E-UTRA detected cells. The UE ignores transmissions from the serving cell while finding the requested information transmitted in the broadcast channel of the detected inter-system/inter-frequency neighbour cell. To do so, the NG-RAN node may need to schedule appropriate idle periods to allow the UE to read the requested information from the broadcast channel of the detected inter-system neighbour cell. +- 4 After the UE has read the requested information in the new cell, it reports the detected ECGI, TAC, and available PLMN ID(s) to the serving cell NG-RAN node. +- 5 The NG-RAN node updates its inter-system NCRT. + +## 15.3.4 Xn-C TNL address discovery + +If the NG-RAN node is aware of the RAN node ID of the candidate NG-RAN node (e.g. via the ANR function) but not of a TNL address suitable for SCTP connectivity, then the NG-RAN node can utilize the 5GC (an AMF it is connected to) to determine the TNL address as follows: + +- The NG-RAN node sends the UPLINK RAN CONFIGURATION TRANSFER message to the AMF to request the TNL address of the candidate NG-RAN node, and includes relevant information such as the source and target RAN node ID; + +- The AMF relays the request by sending the DOWNLINK RAN CONFIGURATION TRANSFER message to the candidate NG-RAN node identified by the target RAN node ID; +- The candidate NG-RAN node responds by sending the UPLINK RAN CONFIGURATION TRANSFER message containing one or more TNL addresses to be used for SCTP connectivity with the initiating NG-RAN node, and includes other relevant information such as the source and target RAN node ID; +- The AMF relays the response by sending the DOWNLINK CONFIGURATION TRANSFER message to the initiating NG-RAN node identified by the target RAN node ID. + +NOTE: Void. + +The NG-RAN node may determine the gNB ID length of the candidate gNB based on, e.g. OAM configuration or UE reporting in ANR function. If the NG-RAN node is not able to make this determination, it may include the NR cell identifier in the UPLINK RAN CONFIGURATION TRANSFER message to the AMF. The AMF may, if supported, determine the target gNB ID by matching the NR cell identifier with a gNB ID of a gNB it connects to. + +## 15.4 Support for Energy Saving + +### 15.4.1 General + +The aim of this function is to reduce operational expenses through energy savings. + +The function allows, for example in a deployment where capacity boosters can be distinguished from cells providing basic coverage, to optimize energy consumption enabling the possibility for an E-UTRA or NR cell providing additional capacity via single or dual connectivity, to be switched off when its capacity is no longer needed and to be re-activated on a need basis, or to support various adaptation techniques in time, frequency, spatial and power domains. + +### 15.4.2 Solution description + +#### 15.4.2.1 Intra-system energy saving + +The solution builds upon the possibility for the NG-RAN node owning a capacity booster cell to autonomously decide to switch-off such cell to lower energy consumption (inactive state). The decision is typically based on cell load information, consistently with configured information. The switch-off decision may also be taken by O&M. + +The NG-RAN node may initiate handover actions in order to off-load the cell being switched off and may indicate the reason for handover with an appropriate cause value to support the target node in taking subsequent actions, e.g. when selecting the target cell for subsequent handovers. + +All neighbour NG-RAN nodes are informed by the NG-RAN node owning the concerned cell about the switch-off actions over the Xn interface, by means of the NG-RAN node Configuration Update procedure. + +All informed nodes maintain the cell configuration data, e.g., neighbour relationship configuration, also when a certain cell is inactive. If basic coverage is ensured by NG-RAN node cells, NG-RAN node owning non-capacity boosting cells may request a re-activation over the Xn interface if capacity needs in such cells demand to do so. This is achieved via the Cell Activation procedure. During switch off time period of the boost cell, the NG-RAN node may prevent idle mode UEs from camping on this cell and may prevent incoming handovers to the same cell. + +The NG-RAN node receiving a request should act accordingly. The switch-on decision may also be taken by O&M. All peer NG-RAN nodes are informed by the NG-RAN node owning the concerned cell about the re-activation by an indication on the Xn interface. + +The solution also builds upon the possibility for the NG-RAN node owning a coverage cell to request neighbouring NG-RAN node(s) owning a capacity booster cell to switch on some SSB beams within the cell which are deactivated. The receiving NG-RAN node should act accordingly. + +The solution also builds upon the possibility for an NG-RAN node to page certain UEs (e.g., stationary UEs) in RRC\_INACTIVE state on a limited set of beams, instead of paging on all the beams within the cell. It is up to the gNB's implementation to select the UEs in RRC\_INACTIVE for which paging in limited set of beams applies. If the paging + +over the limited set of beams fails, the gNB performs subsequent paging by implementation, e.g., by ensuring the same paging message is repeated in all the transmitted SSB beams. + +#### 15.4.2.2 Inter-system energy saving + +The solution builds upon the possibility for the NG-RAN node owning a capacity booster cell to autonomously decide to switch-off such cell to dormant state. The decision is typically based on cell load information, consistently with configured information. The switch-off decision may also be taken by O&M. The NG-RAN node indicates the switch-off action to the eNB over NG interface and S1 interface. The NG-RAN node could also indicate the switch-on action to the eNB over NG interface and S1 interface. + +The eNB providing basic coverage may request a NG-RAN node's cell re-activation based on its own cell load information or neighbour cell load information, the switch-on decision may also be taken by O&M. The eNB requests a NG-RAN node's cell re-activation and receives the NG-RAN node's cell re-activation reply from the NG-RAN node over the S1 interface and NG interface. Upon reception of the re-activation request, the NG-RAN node's cell should remain switched on at least until expiration of the minimum activation time. The minimum activation time may be configured by O&M or be left to the NG-RAN node's implementation. + +#### 15.4.2.3 Cell DTX/DRX + +To facilitate reducing gNB downlink transmission/uplink reception active time, UE can be configured with a periodic cell DTX/DRX pattern (i.e. active and non-active periods). The pattern configuration for cell DTX/DRX is common for the UEs configured with this feature in the cell. The cell DTX and cell DRX patterns can be configured and activated separately. A maximum of two cell DTX/DRX patterns can be configured per MAC entity for different serving cells. When cell DTX is configured and activated for the concerned cell, the UE may not monitor PDCCH in selected cases or does not monitor SPS occasions during cell DTX non-active duration. When cell DRX is configured and activated for the concerned cell, the UE does not transmit on CG resources or does not transmit a SR during cell DRX non-active duration. This feature is only applicable to UEs in RRC\_CONNECTED state and it does not impact Random Access procedure, SSB transmission, paging, and system information broadcasting. Cell DTX/DRX can be activated/deactivated by RRC signalling or L1 group common signalling. Cell DTX/DRX is characterized by the following: + +- **active duration:** duration that the UE waits for to receive PDCCHs or SPS occasions, and transmit SR or CG. In this duration, the gNB transmission/reception of PDCCH, SPS, SR, CG, periodic and semi-persistent CSI report are not impacted for the purpose of network energy saving; +- **cycle:** specifies the periodic repetition of the active-duration followed by a period of non-active duration. + +Active duration and cycle parameters are common between cell DTX and cell DRX, when both are configured; + +Once the gNB recognizes there is an emergency call or public safety related service (e.g. MPS or MCS), the network should ensure that there is no impact to that service (e.g. it may release or deactivate cell DTX/DRX configuration). The network should also ensure that there is at least partial overlapping between UE's connected mode DRX on-duration and cell DTX/DRX active duration, i.e. the UE's connected mode DRX periodicity is a multiple of cell DTX/DRX periodicity or vice versa. + +#### 15.4.2.4 Conditional Handover + +The same principle as described in 9.2.3.4 applies to conditional handover in case the source cell is using a network energy saving solution (e.g., the cell is activating cell DTX/DRX or turning off), unless hereunder specified. In this case, the following additional triggering conditions are supported, upon which UE may use NES-specific CHO event for executing CHO to a candidate cell, as defined in TS 38.331 [12]: + +- The UE may be notified via DCI to enable CHO conditions(s) configured with NES event indication. + +#### 15.4.2.5 Camping Restrictions + +If a cell is activating or going to activate NES cell DTX/DRX, the cell can allow the access of UEs capable of NES cell DTX/DRX via a single bit in SIB1 but prevent the access of UEs not capable of cell DTX/DRX using barring mechanisms described in clause 7.4. + +#### 15.4.2.6 SSB-less SCell + +For an intra-band or inter-band CA SCell, a UE may obtain timing reference and AGC source from another serving cell in case the UE is not provided with SSB nor SMTC configuration for this SCell, as described in TS 38.331 [12]. + +#### 15.4.2.7 Spatial and power domain adaptation + +To assist the gNB on muting transceivers and/or adapting transmission power, the UE can be configured to report multiple CSI entries in a CSI report based on two or more sub-configurations, as specified in clause 5.2.1.6 in TS 38.214 [56]. Each sub-configuration corresponds to a spatial domain adaptation pattern (subsets of available spatial elements) and/or a power offset between PDSCH and CSI-RS. + +### 15.4.3 O&M requirements + +Operators should be able to configure the energy saving function. + +The configured information should include: + +- The ability of an NG-RAN node to perform autonomous cell switch-off; +- The ability of an NG-RAN node to request the re-activation of a configured list of inactive cells owned by a peer NG-RAN node. + +O&M may also configure: + +- policies used by the NG-RAN node for cell switch-off decision; +- policies used by peer NG-RAN nodes for requesting the re-activation of an inactive cell; +- The minimum time an NG-RAN node's cell should remain activated upon reception of a re-activation request from an eNB. + +## 15.5 Self-optimisation + +### 15.5.1 Support for Mobility Load Balancing + +#### 15.5.1.1 General + +The objective of mobility load balancing is to distribute load evenly among cells and among areas of cells, or to transfer part of the traffic from congested cell or from congested areas of cells, or to offload users from one cell, cell area, carrier or RAT to achieve network energy saving. This can be done by means of optimization of cell reselection/handover parameters and handover actions. The automation of such optimisation can provide high quality user experience, while simultaneously improving the system capacity and also to minimize human intervention in the network management and optimization tasks. + +Intra-RAT, intra-system inter-RAT and inter-system load balancing scenarios are supported. + +In general, support for mobility load balancing consists of one or more of following functions: + +- Load reporting for intra-RAT and intra-system inter-RAT load balancing; +- Load balancing action based on handovers; +- Adapting handover and/or reselection configuration; +- Load reporting for inter-system load balancing. + +#### 15.5.1.2 Load reporting for intra-RAT and intra-system inter-RAT load balancing + +The load reporting function is executed by exchanging load information over the Xn/X2/F1/E1 interfaces. + +The following load related information should be supported which consists of: + +- Radio resource usage (per-cell and per SSB area PRB usage: DL/UL GBR PRB usage, DL/UL non-GBR PRB usage, DL/UL total PRB usage, and DL/UL scheduling PDCCH CCE usage; PRB usage for slice(s): DL/UL GBR PRB usage, DL/UL non-GBR PRB usage, and DL/UL Total PRB allocation); +- TNL capacity indicator (UL/DL TNL offered capacity and available capacity); +- Cell Capacity Class value (UL/DL relative capacity indicator); +- Capacity value (per cell, per SSB area and per slice: UL/DL available capacity); +- HW capacity indicator (offered throughput and available throughput over E1, percentage utilisation over F1); +- RRC connections (number of RRC connections, and available RRC Connection Capacity); +- Number of active UEs; +- NR-U channel load (DL/UL channel occupancy time percentage, DL/UL energy detection threshold, radio resource usage). + +To achieve load reporting function, Resource Status Reporting Initiation & Resource Status Reporting procedures are used. + +#### 15.5.1.3 Load balancing action based on handovers + +The source cell may initiate handover due to load. The target cell performs admission control for the load balancing handovers. A handover preparation related to a mobility load balancing action is distinguishable from other handovers, so that the target cell is able to apply appropriate admission control. + +#### 15.5.1.4 Adapting handover and/or reselection configuration + +This function enables requesting of a change of handover and/or reselection parameters at target cell. The source cell that initialized the load balancing estimates if it is needed to change mobility configuration in the source and/or target cell. If the amendment is needed, the source cell initializes mobility negotiation procedure toward the target cell. + +The source cell informs the target cell about the new mobility setting and provides cause for the change (e.g. load balancing related request). The proposed change is expressed by the means of the difference (delta) between the current and the new values of the handover trigger. The handover trigger is the cell specific offset that corresponds to the threshold at which a cell initialises the handover preparation procedure. Cell reselection configuration may be amended to reflect changes in the HO setting. The target cell responds to the information from the source cell. The allowed delta range for HO trigger parameter may be carried in the failure response message. The source cell should consider the responses before executing the planned change of its mobility setting. + +All automatic changes on the HO and/or reselection parameters must be within the range allowed by OAM. + +#### 15.5.1.5 Load reporting for inter-system load balancing + +The load reporting function for inter-system load balancing is executed by exchanging load information between NG-RAN and E-UTRAN. Both event-triggered and periodic inter-system load reporting are supported. Event-triggered inter-system load reports are sent when the reporting node detects crossing of cell load thresholds. + +The following load related information should be supported: + +- Cell Capacity Class value (UL/DL relative capacity indicator); +- Capacity value (per cell: UL/DL available capacity); +- RRC connections (number of RRC connections, and available RRC Connection Capacity); +- Number of active UEs; +- Radio Resource Status (per cell PRB usage: UL/DL GBR PRB usage for MIMO, DL/UL non-GBR PRB usage for MIMO, DL/UL total PRB usage for MIMO). + +NGAP procedures used for inter-system load balancing are Uplink RAN Configuration Transfer and Downlink RAN Configuration Transfer. + +SIAP procedures used for inter-system load balancing are eNB Configuration Transfer and MME Configuration Transfer. + +## 15.5.2 Support for Mobility Robustness Optimization + +### 15.5.2.1 General + +Mobility Robustness Optimisation aims at detecting and enabling correction of following problems: + +- Connection failure due to intra-system or inter-system mobility; +- Inter-system Unnecessary HO (too early inter-system HO from NR to E-UTRAN with no radio link failure); +- Inter-system HO ping-pong; +- PSCell change failure; +- Inter-system voice fallback failure; +- Fast MCG recovery failure. + +MRO provides means to distinguish the above problems from NR coverage related problems and other problems, not related to mobility. + +For detection of a sub-optimal successful handovers, MRO additionally enables observability of: + +- Successful HO due to intra-NR mobility; +- Successful HO due to inter-RAT mobility. + +For detection of a sub-optimal successful PSCell addition/change, MRO additionally enables observability of: + +- Successful PSCell addition/change. + +### 15.5.2.2 Connection failure + +#### 15.5.2.2.1 General + +For analysis of connection failures, the UE makes the RLF Report available to the network. + +The UE stores the latest RLF Report, including both LTE and NR RLF report until the RLF report is fetched by the network or for 48 hours after the connection failure is detected. + +The UE only indicates RLF report availability and only provides the RLF report to the network if the current RPLMN is a PLMN that was present in the UE's EPLMN List or was the RPLMN at the time the connection failure was detected. In case RLF happens in an E-UTRA cell, the UE makes the LTE RLF Report available to NG-RAN nodes and eNB(s), and in case RLF happens in an NR cell the UE makes the NR RLF Report available to gNB(s). + +If the LTE RLF Report is reported to a NG-RAN node, and the last serving node is an E-UTRAN node, the NG-RAN node may transfer it to the E-UTRAN node by triggering the Uplink RAN configuration transfer procedure over NG and the E-UTRAN node can take this into account as defined in TS 36.300 [2]. + +#### 15.5.2.2.2 Connection failure due to intra-system mobility + +One of the functions of Mobility Robustness Optimization is to detect connection failures that occur due to Too Early or Too Late Handovers, or Handover to Wrong Cell. These problems are defined as follows: + +- Intra-system Too Late Handover: an RLF occurs after the UE has stayed for a long period of time in the cell; the UE attempts to re-establish the radio link connection in a different cell. + +- Intra-system Too Early Handover: an RLF occurs shortly after a successful handover from a source cell to a target cell or a handover failure occurs during the handover procedure; the UE attempts to re-establish the radio link connection in the source cell. +- Intra-system Handover to Wrong Cell: an RLF occurs shortly after a successful handover from a source cell to a target cell or a handover failure occurs during the handover procedure; the UE attempts to re-establish the radio link connection in a cell other than the source cell and the target cell. + +In the definition above, the "successful handover" refers to the UE state, namely the successful completion of the RA procedure. + +In case of CHO, the Too Late Handover, Too Early Handover and Handover to Wrong Cell in the definition above means Too Late CHO Execution, Too Early CHO Execution and CHO Execution to Wrong Cell. + +### Detection mechanism + +A failure indication may be initiated after a UE attempts to re-establish the radio link connection at NG-RAN node B after a failure at NG-RAN node A. NG-RAN node B may initiate the Failure Indication procedure towards multiple NG-RAN nodes if they control cells which use the PCI signalled by the UE during the re-establishment procedure. The NG-RAN node receiving this selects the UE context that matches the received Failure Cell ID and C-RNTI, and, if available, uses the shortMAC-I to confirm this identification, by calculating the shortMAC-I and comparing it to the received IE. + +A failure indication may also be sent to the node last serving the UE when the NG-RAN node fetches the RLF REPORT from UE by triggering: + +- The Failure Indication procedure over Xn; +- The Uplink RAN configuration transfer procedure and Downlink RAN configuration transfer procedure over NG. + +The detailed detection mechanisms for too late handover, too early handover and handover to wrong cell are carried out through the following in the NG-RAN node that served the UE before the reported connection failure: + +- Intra-system Too Late Handover: there is no recent handover for the UE prior to the connection failure e.g. the UE reported timer is absent or larger than the configured threshold (e.g. Tstore\_UE\_cntxt), or if CHO is configured but the CHO execution is not initiated for the UE prior to the connection failure, e.g. the UE reported timer is absent or larger than the configured threshold (e.g. Tstore\_UE\_cntxt). +- Intra-system Too Early Handover: there is a recent handover for the UE prior to the connection failure e.g. the UE reported timer is smaller than the configured threshold (e.g. Tstore\_UE\_cntxt), and the first re-establishment attempt cell/the successful re-connect cell is the cell that served the UE at the last handover initialisation or fall back to the source cell configuration in case of DAPS HO. +- Intra-system Handover to Wrong Cell: there is a recent handover for the UE prior to the connection failure e.g. the UE reported timer is smaller than the configured threshold (e.g. Tstore\_UE\_cntxt), and the first re-establishment attempt cell/ the cell UE attempts to re-connect/the cell UE attempts CHO recovery is neither the cell that served the UE at the last handover initialisation nor the cell that served the UE where the RLF happened or the cell that the handover was initialized toward. + +The "UE reported timer" above indicates the time elapsed since the last handover initialisation until connection failure or the time elapsed since the CHO execution until connection failure. + +In case of Too Early Handover or Handover to Wrong Cell, the NG-RAN node receiving the failure indication may inform the NG-RAN node controlling the cell where the mobility configuration caused the failure by means of the Handover Report procedure over Xn or the Uplink RAN Configuration Transfer procedure over NG. This may include the RLF report. + +For MRO analysis, a gNB may take into account the information regarding the LBT failures occurred during the handover execution for a specific UE, as detected by the UE for UL, and by the target gNB for DL. + +### Retrieval of information needed for problem analysis + +In order to retrieve relevant information collected at the network side as part of the UE context, the UE provides C-RNTI used in the last serving cell. If the cause for the failure is identified as a "Too Early HO" or a "HO to Wrong + +Cell", the NG-RAN node controlling the last serving cell shall, include in the HANDOVER REPORT message the C-RNTI used in the source cell of the last completed handover before the failure. If the NG RAN node controlling that source cell provided the Mobility Information, it is also included in the HANDOVER REPORT message. If used, the Mobility Information is prepared at the source NG RAN node of a handover and may refer to or identify any handover-related data at this NG RAN node. In the Handover Preparation procedure, the source gNB can request the target gNB to provide information on DL LBT failures at the target gNB during handover execution. + +#### Handling multiple reports from a single failure event + +In case the RRC re-establishment fails and the RRC connection setup succeeds, MRO evaluation of intra-RAT mobility connection failures may be triggered twice for the same failure event. In this case, only one failure event should be counted. + +#### 15.5.2.2.3 Connection failure due to inter-system mobility + +One of the functions of Mobility Robustness Optimization is to detect connection failures that occurred due to Too Early or Too Late inter-system handovers or inter-system Mobility Failure for Voice Fallback. These problems are defined as follows: + +- Inter-system/ Too Late Handover: an RLF occurs after the UE has stayed in a cell belonging to an NG-RAN node for a long period of time; the UE attempts to re-connect to a cell belonging to an E-UTRAN node. +- Inter-system/ Too Early Handover: an RLF occurs shortly after a successful handover from a cell belonging to an E-UTRAN node to a target cell belonging to an NG-RAN node; the UE attempts to re-connect to the source cell or to another cell belonging to an E-UTRAN node. +- Inter-system Mobility Failure for Voice Fallback: an RLF occurs shortly after a successful handover triggered due to Voice Fallback, or a failure occurs during an handover triggered due to Voice Fallback, from a cell belonging to an NG-RAN node to a cell belonging to an E-UTRAN node; the UE attempts to re-connect to a cell belonging to an E-UTRAN node, or an NG-RAN node. + +#### Detection mechanism + +A failure indication may be sent to the node last serving the UE when the NG-RAN node fetches the RLF REPORT from UE by triggering: + +- The Failure Indication procedure over Xn; +- The Uplink RAN configuration transfer procedure and Downlink RAN configuration transfer procedure over NG. + +In case the last serving node is an E-UTRAN node, the detection mechanism proceeds as defined in TS 36.300 [2]. + +In case the last serving node is an NG-RAN node, the detection mechanisms for Too Late Inter-system Handover, Too Early Inter-system Handover, and Inter-system Mobility Failure for Voice Fallback are carried out through the following: + +- Too Late Inter-system Handover: the connection failure occurs while being connected to a NG-RAN node, and there is no recent handover for the UE prior to the connection failure i.e., the UE reported timer is absent or larger than the configured threshold, e.g., *Tstore\_UE\_cntxt*, and the first node where the UE attempts to re-connect is a E-UTRAN node. +- Too Early Inter-system Handover: the connection failure occurs while being connected to a NG-RAN node, and there is a recent inter-system handover for the UE prior to the connection failure i.e., the UE reported timer is smaller than the configured threshold, e.g., *Tstore\_UE\_cntxt*, and the first cell where the UE attempts to re-connect and the node that served the UE at the last handover initialisation are both E-UTRAN node. +- Inter-system Mobility Failure for Voice Fallback: in case the connection failure occurs during an inter-system handover for voice fall back from NR, the RLF Report from the UE includes a voice fallback indication, as defined in TS 38.331 [12]. + +The "UE reported timer" above indicates the time elapsed since the last handover initialisation until connection failure. The UE may make the RLF Report available to an NG-RAN node. The NG-RAN node may forward the information using the FAILURE INDICATION message over Xn or by means of the Uplink RAN configuration transfer procedure + +and Downlink RAN configuration transfer over NG to the node that served the UE before the reported connection failure. + +In case the failure is a Too Early Inter-system Handover, the NG-RAN node receiving the failure indication may inform the E-UTRAN node by means of the Uplink RAN Configuration Transfer procedure over NG. This may include the RLF report. + +### 15.5.2.3 Inter-system Unnecessary HO + +One of the purposes of inter-system Mobility Robustness Optimisation is the detection of a non-optimal use of network resources. In particular, in case of inter-system operations and when NR is considered, the case known as Unnecessary HO to another system is identified. The problem is defined as follows: + +- UE is handed over from NR to E-UTRAN even though quality of the NR coverage was sufficient for the service used by the UE. The handover may therefore be considered as unnecessary HO to another system (i.e. EPS) (too early inter-system HO without connection failure). + +In inter-system HO, if the serving cell threshold (NR cell) is set too high, and cell in another system (i.e. EPS) with good signal strength is available, a handover to another system may be triggered unnecessarily, resulting in an inefficient use of the networks. With a lower threshold the UE could have continued in the source system (5GS). + +To be able to detect the Unnecessary HO to another system, a gNB node may choose to put additional coverage and quality condition information into the HANDOVER REQUIRED message in the Handover Preparation procedure when an inter-system HO from gNB to another system occurs. The RAN node in the other system, upon receiving this additional coverage and quality information, may instruct the UE to continue measuring the cell(s) in source system during a period of time, while being connected to another system, and send periodic or single measurement reports to the node in other system. When the period of time indicated by the node in source system expires, the RAN node in the other system, may evaluate the received measurement reports with the coverage/quality condition received during the inter-system HO procedure and decide if an inter-system unnecessary HO report should be sent to the gNB in the source system. + +The inter-system unnecessary HO report shall only be sent in cases where, in all UE measurement reports collected during the measurement period, any cells in the source system exceed the radio coverage and/or quality threshold (the radio threshold RSRP, RSRQ or/and SINR and the measurement period are indicated in the additional coverage and quality information in the Handover Preparation procedure). If an inter-system handover towards 5GS is executed from EPS within the indicated measurement period, the measurement period expires. In this case, the eNB in EPS may also send the HO Report. No HO Report shall be sent in case no NR cell could be included, or if the indicated period of time is interrupted by an inter-system handover to a system different than 5GS. + +The RAN node in the source system (5GS) upon receiving of the report, can decide if/how its parameters (e.g., threshold to trigger Inter-system HO) should be adjusted. + +### 15.5.2.4 Inter-system Ping-pong + +One of the functions of Mobility Robustness Optimization is to detect ping-pongs that occur in inter-system environment. The problem is defined as follows: + +- A UE is handed over from a cell in a source system (e.g. 5GS) to a cell in a target system different from the source system (e.g. EPS), then within a predefined limited time the UE is handed over back to a cell in the source system, while the coverage of the source system was sufficient for the service used by the UE. The event may occur more than once. + +The solution for the problem may consist of the following steps: + +- 1) Statistics regarding inter-system ping-pong occurrences are collected by the responsible node; +- 2) Coverage verification is performed to check if the mobility to other system was inevitable. + +The statistics regarding ping-pong occurrence may be based on evaluation of the *UE History Information* IE in the HANDOVER REQUIRED message. If the evaluation indicates a potential ping-pong case and the source NG\_RAN node of the 1st inter-system handover is different than the target NG-RAN node of the 2nd inter-system handover, the target NG-RAN node may use the HANDOVER REPORT message or the UPLINK RAN CONFIGURATION TRANSFER message to indicate the occurrence of potential ping-pong cases to the source NG-RAN node. + +If NG-RAN coverage during the potential ping-pong event needs to be verified for the purpose of determining corrective measures, the Unnecessary HO to another system procedure may be used. + +NOTE: Inter-system mobility triggered by Voice Fallback is not considered as inter-system ping-pong. + +### 15.5.2.5 O&M Requirements + +All automatic changes of the HO and/or reselection parameters for mobility robustness optimisation shall be within the ranges allowed by OAM and specified below. + +The following control parameters shall be provided by OAM to control MRO behaviour: + +- Maximum deviation of Handover Trigger: this parameter defines the maximum allowed absolute deviation of the Handover Trigger, from the default point of operation defined by the parameter values assigned by OAM. +- Minimum time between Handover Trigger changes: this parameter defines the minimum allowed time interval between two Handover Trigger change performed by MRO. This is used to control the stability and convergence of the algorithm. + +Furthermore, in order to support the solutions for detection of mobility optimisation, the parameter *Tstore\_UE\_cntxt* shall be configurable by the OAM system. + +### 15.5.2.6 PSCell change failure + +For analysis of PSCell change failures, the UE makes the SCG Failure Information available to the MN. If the MN can perform an initial analysis, it transfers the SCG Failure Information together with the analysis results to the relevant SN which is responsible for the PSCell change failures. Otherwise, the MN transfers the SCG Failure Information to the last serving SN, which may respond using the SCG Failure Transfer procedure to inform the MN it is not responsible for the SCG failure. If needed, the MN transfer the SCG Failure Information to the source SN. + +### 15.5.2.7 Successful HO + +One of the functions of Mobility Robustness Optimization is to detect a sub-optimal successful handover event. The aim is to identify underlying conditions during successful ordinary handovers, successful DAPS handovers, or successful Conditional handovers. + +For analysis of successful handover, the UE may collect Successful Handover Report (SHR) based on configuration by network, if stored, and makes the SHR available to the network as specified in TS 38.331 [12]. The UE stores the SHR until it is fetched by the network or for 48 hours after the SHR is recorded. + +For SHR collected during intra-NR handover, if the target NR node fetches the SHR from the UE and the trigger of SHR is T310/T312, it may forward the information to the source NR node, i.e. the node handling the cell reported as source cell in this SHR, by using the ACCESS AND MOBILITY INDICATION message over Xn or by means of the Uplink RAN configuration transfer procedure and Downlink RAN configuration transfer procedure over NG. + +If the NG-RAN node that fetches the SHR from the UE is neither the source node nor the target node of the handover, it forwards the information to the node(s) which configured the SHR trigger causing the SHR to be generated, by using the ACCESS AND MOBILITY INDICATION message over Xn or by means of the Uplink RAN configuration transfer procedure and Downlink RAN configuration transfer procedure over NG. + +In case of failure shortly after successful Handover, the same mobility event may generate both a SHR and a RLF report. In this case, the node(s), which configured the SHR trigger causing the SHR, may take the duplication into account e.g. ignore the SHR. + +Upon retrieval of an SHR, the receiving node may analyse whether its mobility configuration needs adjustment. + +The SHR report can be used to detect one case of Intra-system Too Late Handover, namely when DAPS HO is configured but an RLF is detected in the source cell during a successful DAPS HO. + +### 15.5.2.8 Successful PSCell Addition/Change Report + +For the analysis of successful PSCell addition/change, the UE supports Successful PSCell Addition/Change Report (SPR) based on the configuration by network, if received, and makes the SPR available to the network as specified in TS 38.331 [12]. + +The UE stores the SPR until the SPR is fetched by the network or for 48 hours after the SPR is recorded. + +The UE makes the SPR available to gNB(s). + +When a gNB fetches the SPR from UE, it forwards the SPR to the MN that was serving the UE at the time the SPR was generated by using the ACCESS AND MOBILITY INDICATION message over Xn or by means of the Uplink RAN configuration transfer procedure and Downlink RAN configuration transfer over NG. + +### 15.5.3 Support for RACH Optimization + +RACH optimization is supported by UE reported information made available at the NG RAN node as specified in TS 38.331 [12] and by PRACH parameters exchange between NG RAN nodes. + +The contents of the RA Report comprise of the following: + +- Contention detection indication per RACH attempt; +- Indexes of the SSBs and number of RACH preambles sent on each tried SSB listed in chronological order of attempts; +- Indication whether the selected SSB is above or below the configured RSRP threshold per RACH attempt; +- 2-step RACH information as specified in clause 5.7.10.4 of TS 38.331 [12]. + +#### SN RA Reports + +The UE operating in NR-DC, may also support collection of RA Reports by the SN. + +The RA report retrieval and forwarding in case of NGEN-DC is specified in TS 37.340 [21]. + +### 15.5.4 UE History Information from the UE + +The source NG-RAN node collects and stores the UE History Information for as long as the UE stays in one of its cells. + +The UE may report the UE history information when connecting to a cell of the NG-RAN node, consisting of PCell and PSCell mobility history information, as specified in TS 38.331 [12]. + +When information needs to be discarded because the list is full, such information will be discarded in order of its position in the list, starting with the oldest cell record. If the list is full, and the UE history information from the UE is available, the UE history information from the UE should also be discarded. + +The resulting information is then used in subsequent handover preparations by means of the Handover Preparation procedures over the NG and XN interfaces, which provide the target NG-RAN node with a list of previously visited cells and associated (per-cell) information elements. The Handover Preparation procedures also trigger the target NG-RAN node to start collection and storage of UE history Information and thus to propagate the collected information. + +In case of CHO, the target NG-RAN node updates the time UE stayed in cell of the latest PCell entry (i.e. the source cell) when the UE successfully accesses a candidate cell of the target NG-RAN node. The updated value of the time UE stayed in the source cell is equal to the value received from the source NG-RAN node during the Handover Preparation plus the time from receiving the Handover Request message from the source NG-RAN node to receiving the RRC Reconfiguration Complete message from the UE. When the target NG-RAN node receives the SCG UHI from the source NG-RAN node via the Handover Request message, the target NG-RAN node also updates the time UE stayed in cell of the latest PSCell entry (i.e. the source PSCell) as specified in TS 37.340 [21]. + +## 15.5.5 Support for Coverage and Capacity Optimisation + +### 15.5.5.1 General + +The objective of NR Coverage and Capacity Optimization (CCO) function is to detect and resolve or mitigate CCO issues, e.g. coverage and cell edge interference issues. + +### 15.5.5.2 OAM requirements + +Each NG-RAN node may be configured with *alternative coverage configurations* by OAM. The alternative coverage configurations contain relevant radio parameters and may also include a range for how each parameter is allowed to be adjusted. + +### 15.5.5.3 Dynamic coverage configuration changes + +An NG-RAN node may autonomously adjust within and switch between coverage configurations. When a change is executed, a NG-RAN node may notify its neighbour NG-RAN nodes using the NG-RAN NODE CONFIGURATION UPDATE message with the list of cells and SSBs with modified coverage included. The list contains the CGI of each modified cell with its coverage state indicator and optionally the SSB index of each modified SSB with its coverage state indicator. + +The coverage state indicator may be used at the receiving NG-RAN node to adjust the functions of the Mobility Robustness Optimisation, e.g. by using the coverage state indicator to retrieve a previously stored Mobility Robustness Optimisation state. The coverage state indicator may also be used at the receiving NG-RAN node to adopt coverage configurations matching with neighbouring cells coverage configurations. + +If the list includes indication about planned reconfiguration and possibly a list of replacing cells, the receiving NG-RAN node may use this to avoid connection or re-establishment failures during the reconfiguration. Also, if the sending NG-RAN node adds cells in inactive state, the receiving NG-RAN node may use this information to avoid connection or re-establishment failures. The receiving NG-RAN node may also use the notification to reduce the impact on mobility. The receiving NG-RAN node should avoid triggering handovers towards cell(s) that are indicated to be inactive. + +## 15.5.6 Support for PCI Optimisation + +The PCI Optimization Function in split gNB case is specified in TS 38.401 [4]. + +### 15.5.6.1 Centralized PCI Assignment + +For centralized PCI assignment in gNB, the OAM assigns a single PCI for each NR cell in the gNB, and the gNB selects this value as the PCI of the NR cell. + +### 15.5.6.2 Distributed PCI Assignment + +For distributed PCI assignment in gNB, the OAM assigns a list of PCIs for each NR cell in the gNB, and the gNB selects a PCI value from the list of PCIs. The gNB may restrict this list by removing some PCIs that are reported by UEs, reported over the Xn interface by neighbouring gNBs, and/or acquired through other methods, e.g. detected over the air using a downlink receiver. + +--- + +## 16 Verticals Support + +### 16.1 URLLC + +#### 16.1.1 Overview + +The support of Ultra-Reliable and Low Latency Communications (URLLC) services is facilitated by the introduction of the mechanisms described in the following clauses. Please note however that those mechanisms need not be limited to + +the provision of URLLC services. Furthermore, RRC can associate logical channels with different SR configurations, for instance, to provide more frequent SR opportunities to URLLC services. + +### 16.1.2 LCP Restrictions + +With LCP restrictions in MAC, RRC can restrict the mapping of a logical channel to a subset of the configured cells, numerologies, PUSCH transmission durations, configured grant configurations and control whether a logical channel can utilise the resources allocated by a Type 1 Configured Grant (see clause 10.3) or whether a logical channel can utilise dynamic grants indicating a certain physical priority level. With such restrictions, it then becomes possible to reserve, for instance, the numerology with the largest subcarrier spacing and/or shortest PUSCH transmission duration for URLLC services. Furthermore, RRC can associate logical channels with different SR configurations, for instance, to provide more frequent SR opportunities to URLLC services. + +### 16.1.3 Packet Duplication + +When duplication is configured for a radio bearer by RRC, at least one secondary RLC entity is added to the radio bearer to handle the duplicated PDCP PDUs as depicted on Figure 16.1.3-1, where the logical channel corresponding to the primary RLC entity is referred to as *the primary logical channel*, and the logical channel corresponding to the secondary RLC entity(ies), the *secondary logical channel(s)*. All RLC entities have the same RLC mode. Duplication at PDCP therefore consists in submitting the same PDCP PDUs multiple times: once to each activated RLC entity for the radio bearer. With multiple independent transmission paths, packet duplication therefore increases reliability and reduces latency and is especially beneficial for URLLC services. + +![Diagram of Packet Duplication architecture showing PDCP at the top, connected to a primary RLC entity and a secondary RLC entity. The primary RLC entity is connected to a Primary LCH, and the secondary RLC entity is connected to a Secondary LCH.](5199d255473623b85726fdb4f67dec8b_img.jpg) + +``` + +graph TD + PDCP[PDCP] --> RLC_primary[RLC primary] + PDCP -.-> RLC_secondary[RLC secondary] + RLC_primary --> Primary_LCH[Primary LCH] + RLC_secondary -.-> Secondary_LCH[Secondary LCH] + +``` + +Diagram of Packet Duplication architecture showing PDCP at the top, connected to a primary RLC entity and a secondary RLC entity. The primary RLC entity is connected to a Primary LCH, and the secondary RLC entity is connected to a Secondary LCH. + +**Figure 16.1.3-1: Packet Duplication** + +NOTE: PDCP control PDUs are not duplicated and always submitted to the primary RLC entity. + +When configuring duplication for a DRB, RRC also sets the state of PDCP duplication (either activated or deactivated) at the time of (re-)configuration. After the configuration, the PDCP duplication state can then be dynamically controlled by means of a MAC control element and in DC, the UE applies the MAC CE commands regardless of their origin (MCG or SCG). When duplication is configured for an SRB the state is always active and cannot be dynamically controlled. When configuring duplication for a DRB with more than one secondary RLC entity, RRC also sets the state of each of them (i.e. either activated or deactivated). Subsequently, a MAC CE can be used to dynamically control whether each of the configured secondary RLC entities for a DRB should be activated or deactivated, i.e. which of the RLC entities shall be used for duplicate transmission. Primary RLC entity cannot be deactivated. When duplication is deactivated for a DRB, all secondary RLC entities associated to this DRB are deactivated. When a secondary RLC entity is deactivated, it is not re-established, the HARQ buffers are not flushed, and the transmitting PDCP entity should indicate to the secondary RLC entity to discard all duplicated PDCP PDUs. + +When activating duplication for a DRB, NG-RAN should ensure that at least one serving cell is activated for each logical channel associated with an activated RLC entity of the DRB; and when the deactivation of SCells leaves no serving cells activated for a logical channel of the DRB, NG-RAN should ensure that duplication is also deactivated for the RLC entity associated with the logical channel. + +When duplication is activated, the original PDCP PDU and the corresponding duplicate(s) shall not be transmitted on the same carrier. The logical channels of a radio bearer configured with duplication can either belong to the same MAC entity (referred to as CA duplication) or to different ones (referred to as DC duplication). CA duplication can also be configured in either or both of the MAC entities together with DC duplication when duplication over more than two + +RLC entities is configured for the radio bearer. In CA duplication, logical channel mapping restrictions are used in a MAC entity to ensure that the different logical channels of a radio bearer in the MAC entity are not sent on the same carrier. When CA duplication is configured for an SRB, one of the logical channels associated to the SRB is mapped to SpCell. + +When CA duplication is deactivated for a DRB in a MAC entity (i.e. none or only one of RLC entities of the DRB in the MAC entity remains activated), the logical channel mapping restrictions of the logical channels of the DRB are lifted for as long as CA duplication remains deactivated for the DRB in the MAC entity. + +When an RLC entity acknowledges the transmission of a PDCP PDU, the PDCP entity shall indicate to the other RLC entity(ies) to discard it. In addition, in case of CA duplication, when an RLC entity restricted to only SCell(s) reaches the maximum number of retransmissions for a PDCP PDU, the UE informs the gNB but does not trigger RLF. + +## 16.1.4 CQI and MCS + +For channel state reporting, a CQI table for target block error rate $10^{-5}$ is introduced. + +For scheduling data packets with higher reliability, 64QAM MCS tables containing entries with lower spectral efficiency are introduced for both downlink and uplink. The tables are different for CP-OFDM and DFT-s-OFDM. The MCS tables can be configured semi-statically or dynamically. The dynamic signalling of MCS table is supported by configuring UE with MCS-C-RNTI, where the scrambling of DCI CRC by MCS-C-RNTI indicates the 64QAM MCS tables with entries of lower spectral efficiency. + +## 16.1.5 DCI formats + +For PDCCH transmission with higher reliability, two DCI formats are introduced for uplink and downlink scheduling respectively. + +## 16.1.6 Higher layer multi-connectivity + +The redundant transmission may be applied on the user plane path between the UE and the network for URLLC service as specified in TS 23.501 [3]. + +### 16.1.6.1 Redundant user plane paths based on dual connectivity + +UE may initiate two redundant PDU Sessions over the 5G network. The 5GS sets up the user plane paths of the two redundant PDU sessions to be disjoint. When PDU session setup or modification is initiated, the RAN can configure dual connectivity in one NG-RAN node or two NG-RAN nodes for the two redundant PDU sessions to ensure the disjoint user plane paths according to the redundancy information received from the 5GC. The RAN shall ensure that the resources of the data radio bearers for the two redundant PDU sessions are isolated. If the RAN cannot satisfy the disjoint user plane requirement, the redundant PDU sessions may be kept or not kept according to the RAN local configuration. The redundancy information is transferred to the target NG-RAN node in case of handover. + +### 16.1.6.2 Redundant data transmission via single UPF and single RAN node + +Two NG-U tunnels are setup between single UPF and single NG-RAN node for redundant transmission of the QoS flows when PDU session setup or modification is initiated. The two NG-U tunnels are transferred via disjointed transport layer paths. The 5GC provides the indicator per QoS flow to the NG-RAN for the redundant transmission. For downlink, the NG-RAN node eliminates the duplicated packets per QoS flow. For uplink, the NG-RAN node replicates the packets and transmits them via the two NG-U tunnels. The indicator per QoS flow for redundant transmission is transferred to the target NG-RAN node in case of handover. + +## 16.1.7 URLLC in Unlicensed Controlled Environment + +URLLC services can be supported in shared spectrum where LBT failures are assumed to be not frequent. In this case, a channel access procedure for semi-static channel occupancy can be initiated by the gNB or the UE, or the gNB operates in dynamic channel access mode, as described in TS 37.213 [37]. To handle potential LBT failures on configured grants (CG), the CG retransmission timer can be optionally configured to enable autonomous retransmissions, and it may be configured simultaneously with enhanced intra-UE overlapping resource prioritization mechanisms. When the CG retransmission timer is configured, the UE shall select the HARQ process for each CG resource by itself. If the enhanced + +intra-UE overlapping resource prioritization mechanisms is also configured, the UE may be further configured to select the HARQ process for a CG resource based on logical channel priority. + +### 16.1.8 PUCCH cell switching for TDD cells + +To reduce the delay for HARQ-ACK feedback for TDD operation with URLLC services, PUCCH cell switching for TDD cells is supported. The UE can be provided in each PUCCH group with a PUCCH switching SCell (PUCCH sSCell) that can be used for PUCCH transmission in addition to PCell / PSCell / PUCCH SCell. The applicable cell for PUCCH transmission to be either on PCell / PSCell / PUCCH SCell or the PUCCH sSCell at a time is either defined by: + +- a higher layer configured semi-static time-domain pattern of the applicable cell for PUCCH transmission; or +- dynamic indication of the cell for PUCCH transmission through a PDCCH scheduling a PUCCH transmission. + +The PUCCH cell switching is applicable to all UCI types when using the higher layer configured time-domain pattern, but is only applicable to HARQ feedback for the dynamic indication of the cell for PUCCH transmission through a PDCCH scheduling PUCCH. + +## 16.2 IMS Voice + +### 16.2.0 Support for IMS voice + +For IMS voice support in NG-RAN, the following is assumed: + +- Network ability to support IMS voice sessions, i.e. ability to support QoS flows with 5QI for voice and IMS signalling (see clause 12 and TS 23.501 [3]), or through EPC System fallback; +- UE capability to support "IMS voice over PS", see TS 24.501 [28]. + +The capabilities indications check is handled at NAS layer. To maintain the voice service in NG-RAN, the UE provides additional capabilities over RRC (see TS 38.331 [12]), that are used to determine accurate NR voice support options. + +Further MMTEL IMS voice and video enhancements are facilitated by the mechanisms described in the following clauses. + +### 16.2.1 Support for MMTEL IMS voice and video enhancements + +#### 16.2.1.1 RAN-assisted codec adaptation + +RAN-assisted codec adaptation provides a means for the gNB to send codec adaptation indication with recommended bit rate to assist the UE to select or adapt to a codec rate for MMTEL voice or MMTEL video. The RAN-assisted codec adaptation mechanism supports the uplink/downlink bit rate increase or decrease. For a bearer associated with configuration of MBR greater than GBR, the recommended uplink/downlink bit rate is within boundaries set by the MBR and GBR of the concerned bearer. + +For uplink or downlink bit rate adaptation, gNB may send a recommended bit rate to the UE to inform the UE on the currently recommended transport bit rate on the local uplink or downlink, which the UE may use in combination with other information to adapt the bit rate, e.g. the UE may send a bit rate request to the peer UE via application layer messages as specified in TS 26.114 [24], which the peer UE may use in combination with other information to adapt the codec bit rate. The recommended bit rate is in kbps at the physical layer at the time when the decision is made. + +The recommended bit rate for UL and DL is conveyed as a MAC Control Element (CE) from the gNB to the UE as outlined in Figure 16.2.1.1-1. + +![Diagram showing a UE sending a UL/DL bit rate recommendation to a gNB.](2ed8cadf211f7d2dba5eecc5f0ad1876_img.jpg) + +A sequence diagram showing a User Equipment (UE) on the left and a gNB on the right. A horizontal arrow points from the UE to the gNB, labeled "UL/DL bit rate recommendation". + +Diagram showing a UE sending a UL/DL bit rate recommendation to a gNB. + +**Figure 16.2.1.1-1: UL or DL bit rate recommendation** + +Based on the recommended bit rate from the gNB, a UE may initiate an end-to-end bit rate adaptation with its peer (UE or MGW). The UE may also send a query message to its local gNB to check if a bit rate recommended by its peer can be provided by the gNB. The UE is not expected to go beyond the recommended bit rate from the gNB. + +The recommended bit rate query message is conveyed as a MAC CE from the UE to the gNB as outlined in Figure 16.2.1.1-2. + +![Diagram showing a UE sending a UL/DL bit rate recommendation query to a gNB.](cef981f48160da6ca248560bbf31eb7f_img.jpg) + +A sequence diagram showing a User Equipment (UE) on the left and a gNB on the right. A horizontal arrow points from the UE to the gNB, labeled "UL/DL bit rate recommendation query". + +Diagram showing a UE sending a UL/DL bit rate recommendation query to a gNB. + +**Figure 16.2.1.1-2: UL or DL bit rate recommendation query** + +A prohibit timer can be configured per logical channel by the network to limit UEs sending frequent query MAC CEs. Independent prohibit timers are used for each direction (uplink and downlink) to prohibit the UE from retransmitting exactly the same query MAC CE to the gNB during the configured time. + +### 16.2.1.2 MMTEL voice quality/coverage enhancements + +The air interface delay budget can be relaxed to increase the robustness of the transmission for coverage enhancement. Such relaxation may be achieved when a UE in good coverage indicates a preference to the gNB to reduce the local air interface delay by sending a *DelayBudgetReport* message to decrease the DRX cycle length, so that the E2E delay and jitter can be reduced. When the UE detects changes such as end-to-end MMTEL voice quality or local radio quality, the UE may inform the gNB its new preference by sending *DelayBudgetReport* messages with updated contents. + +## 16.3 Network Slicing + +### 16.3.1 General Principles and Requirements + +In this clause, the general principles and requirements related to the realization of network slicing in the NG-RAN for NR connected to 5GC and for E-UTRA connected to 5GC are given. + +A network slice always consists of a RAN part and a CN part. The support of network slicing relies on the principle that traffic for different slices is handled by different PDU sessions. Network can realise the different network slices by scheduling and also by providing different L1/L2 configurations. + +Each network slice is uniquely identified by a S-NSSAI, as defined in TS 23.501 [3]. NSSAI (Network Slice Selection Assistance Information) includes one or a list of S-NSSAIs (Single NSSAI) where a S-NSSAI is a combination of: + +- mandatory SST (Slice/Service Type) field, which identifies the slice type and consists of 8 bits (with range is 0-255); +- optional SD (Slice Differentiator) field, which differentiates among Slices with same SST field and consist of 24 bits. + +The list includes at most 8 S-NSSAI(s). + +The UE provides NSSAI (Network Slice Selection Assistance Information) for network slice selection in *RRCSsetupComplete*, if it has been provided by NAS (see clause 9.2.1.3). While the network can support large number of slices (hundreds), the UE need not support more than 8 slices simultaneously. A BL UE or a NB-IoT UE supports a maximum of 8 slices simultaneously. + +Network Slicing is a concept to allow differentiated treatment depending on each customer requirements. With slicing, it is possible for Mobile Network Operators (MNO) to consider customers as belonging to different tenant types with each having different service requirements that govern in terms of what slice types each tenant is eligible to use based on Service Level Agreement (SLA) and subscriptions. + +The following key principles apply for support of Network Slicing in NG-RAN: + +#### **RAN awareness of slices** + +- NG-RAN supports a differentiated handling of traffic for different network slices which have been pre-configured. How NG-RAN supports the slice enabling in terms of NG-RAN functions (i.e. the set of network functions that comprise each slice) is implementation dependent. + +#### **Selection of RAN part of the network slice** + +- NG-RAN supports the selection of the RAN part of the network slice, by NSSAI provided by the UE or the 5GC which unambiguously identifies one or more of the pre-configured network slices in the PLMN. + +#### **Resource management between slices** + +- NG-RAN supports policy enforcement between slices as per service level agreements. It should be possible for a single NG-RAN node to support multiple slices. The NG-RAN should be free to apply the best RRM policy for the SLA in place to each supported slice. + +#### **Support of QoS** + +- NG-RAN supports QoS differentiation within a slice, and per Slice-Maximum Bit Rate may be enforced per UE, if feasible. How NG-RAN enables UE-Slice-MBR enforcement and rate limitation (see TS 23.501 [3]) is up to network implementation. + +#### **RAN selection of CN entity** + +- For initial attach, the UE may provide NSSAI to support the selection of an AMF. If available, NG-RAN uses this information for routing the initial NAS to an AMF. If the NG-RAN is unable to select an AMF using this information or the UE does not provide any such information the NG-RAN sends the NAS signalling to one of the default AMFs. +- For subsequent accesses, the UE provides a Temp ID, which is assigned to the UE by the 5GC, to enable the NG-RAN to route the NAS message to the appropriate AMF as long as the Temp ID is valid (NG-RAN is aware of and can reach the AMF which is associated with the Temp ID). Otherwise, the methods for initial attach applies. + +#### **Resource isolation between slices** + +- The NG-RAN supports resource isolation between slices. NG-RAN resource isolation may be achieved by means of RRM policies and protection mechanisms that should avoid that shortage of shared resources in one slice breaks the service level agreement for another slice. It should be possible to fully dedicate NG-RAN resources to a certain slice. Some RACH resources can be associated to specific NSAG(s). Other aspects how NG-RAN supports resource isolation is implementation dependent. + +#### **Access control** + +- By means of the unified access control (see clause 7.4), operator-defined access categories can be used to enable differentiated handling for different slices. NG-RAN may broadcast barring control information (i.e. a list of barring parameters associated with operator-defined access categories) to minimize the impact of congested slices. + +#### **Slice Availability** + +- Some slices may be available only in part of the network. A slice is considered available in a cell if it is supported by the TA comprising the cell and the slice is not configured with zero resources, as specified in TS 23.501 [3]. A slice is supported within a TA if it is included in the slice support list for the TA signalled from the NG-RAN to the AMF. The NG-RAN supported S-NSSAI(s), NSAG(s) and NSAG related information such as NSAG associated Cell Reselection Priority and/or NSAG associated RACH resources are configured by OAM. Awareness in the NG-RAN of the slices supported in the cells of its neighbours may be beneficial for inter- + +frequency mobility in connected mode. In order to support the NSAG, the NG-RAN provides the AMF with the NSAG information per TA in the appropriate NG interface management procedures, as specified in TS 38.413 [26]. Awareness in the NG-RAN of the NSAG information supported in the list(s) of neighbour cells may be configured by OAM, or exchanged with neighbour NG-RAN nodes. + +- The NG-RAN and the 5GC are responsible to handle a service request for a slice that may or may not be available in a given area. Admission or rejection of access to a slice may depend by factors such as support for the slice, availability of resources, support of the requested service by NG-RAN. +- The NG-RAN may be signalled with the Partially Allowed NSSAI from the AMF as specified in TS 23.501 [3]. The NG-RAN may decide to use the Partially Allowed NSSAI for mobility decision. +- Support for Network Slices with Network Slice Area of Service not matching deployed Tracking Areas is specified in TS 23.501 [3]. NG-RAN cells that are outside the Area of Service may be configured with zero resources for the concerned slice(s). The concerned slice(s) cannot use any dedicated, prioritized nor any shared resources of that cell. Awareness of zero resources configured for a slice in one or more cells may be exchanged with neighbour NG-RAN nodes for mobility reasons. + +#### Support for UE associating with multiple network slices simultaneously + +- In case a UE is associated with multiple slices simultaneously, only one signalling connection is maintained and for intra-frequency cell reselection, the UE always tries to camp on the best cell. For inter-frequency cell reselection, dedicated priorities can be used to control the frequency on which the UE camps. + +#### Granularity of slice awareness + +- Slice awareness in NG-RAN is introduced at PDU session level, by indicating the S-NSSAI corresponding to the PDU Session, in all signalling containing PDU session resource information. + +#### Validation of the UE rights to access a network slice + +- It is the responsibility of the 5GC to validate that the UE has the rights to access a network slice. Prior to receiving the Initial Context Setup Request message, the NG-RAN may be allowed to apply some provisional/local policies, based on awareness of which slice the UE is requesting access to. During the initial context setup, the NG-RAN is informed of the slice for which resources are being requested. + +#### Network slice replacement + +- NG-RAN may support network slice replacement for a PDU session as defined in TS 23.501 [3]. + +### 16.3.2 AMF and NW Slice Selection + +#### 16.3.2.1 CN-RAN interaction and internal RAN aspects + +NG-RAN selects AMF based on a Temp ID or NSSAI provided by the UE over RRC as specified in TS 38.410 [16]. The mechanisms used in the RRC protocol are described in the next clause. + +**Table 16.3.2.1-1 AMF selection based on Temp ID and NSSAI** + +| Temp ID | NSSAI | AMF Selection by NG-RAN | +|--------------------------------------------------------------------------|---------------------------|----------------------------------------------------| +| not available or invalid | not available | One of the default AMFs is selected (NOTE) | +| not available or invalid | present | Selects AMF which supports UE requested slices | +| valid | not available, or present | Selects AMF per CN identity information in Temp ID | +| NOTE: The set of default AMFs is configured in the NG-RAN nodes via OAM. | | | + +#### 16.3.2.2 Radio Interface Aspects + +When triggered by the upper layer, the UE conveys the NSSAI over RRC in the format explicitly indicated by the upper layer. + +## 16.3.3 Resource Isolation and Management + +### 16.3.3.1 General + +Resource isolation enables specialized customization and avoids one slice affecting another slice. + +Hardware/software resource isolation is up to implementation. Each slice may be assigned with either shared, prioritized or dedicated radio resource up to RRM implementation and SLA as in TS 28.541 [49]. + +To enable differentiated handling of traffic for network slices with different SLA: + +- NG-RAN is configured with a set of different configurations for different network slices by OAM; +- To select the appropriate configuration for the traffic for each network slice, NG-RAN receives relevant information indicating which of the configurations applies for this specific network slice. + +Slice-based RACH configuration for RA isolation and prioritization can be included in SIB1 messages. The slice-based RACH configurations are associated to specific NSAG(s), and if not provided for a NSAG that UE considers for selecting the RACH configuration, then the UE does not consider the NSAG for selecting the slice-based RACH configuration. The UE determines the NSAG to be considered during RA as specified in TS 23.501 [3]. When the UE AS does not receive any NSAG information from NAS for Random Access, the UE does not apply the slice-based RACH configuration. + +### 16.3.3.2 Handling of Slice Resources + +The NG-RAN node may use Multi-Carrier Resource Sharing or Resource Repartitioning to allocate resources to a slice during the procedures described in 16.3.4 to support the slice service continuity in case of slice resources shortage. + +In Multi-Carrier Resource Sharing the RAN node can setup the dual connectivity or carrier aggregation with different frequency and overlapping coverage where the same slice is available. + +The Resource Repartitioning allows a slice to use resources from the shared pool or/and prioritized pool when its own dedicated or prioritized resources are not available and the use of unused resources in the prioritized pool is as specified in TS 28.541 [49]. + +Slice RRM policies/restrictions associated with Resource Repartitioning are configured from O&M. + +Measurements of RRM policy utilization according to resource types defined in TS 28.541 [49] are reported from RAN nodes to O&M and may lead O&M to update the configuration of the Slice RRM policies/restrictions. + +### 16.3.3a Slice-based cell reselection + +Slice-based cell reselection information can be included in SIB16 and in *RRRelease* messages. The slice-based cell reselection information may include reselection priorities per NSAG per frequency and corresponding list(s) of cells where the slices of the NSAG are supported or not supported. The UE determines the NSAG(s) and their priorities to be considered during cell reselection as specified in TS 23.501 [3], and in TS 38.304 [10]. + +When a UE supports slice-based cell reselection, and when slice-based cell reselection information is provided to the UE, then the UE uses the slice-based cell reselection information. Valid cell reselection information provided in *RRRelease* always has a priority over cell reselection information provided in SIB messages. When no slice-based cell reselection information is provided for any NSAG that was determined to be considered during cell reselection (as specified in TS 23.501 [3]), then the UE uses the general cell reselection information, i.e., without considering the NSAG(s) and their priorities. + +## 16.3.4 Signalling Aspects + +### 16.3.4.1 General + +In this clause, signalling flows related to the realization of network slicing in the NG-RAN are given. + +### 16.3.4.2 AMF and NW Slice Selection + +RAN selects the AMF based on a Temp ID or NSSAI provided by the UE. + +![Sequence diagram for AMF selection (Figure 16.3.4.2-1).](9ac8c3c5f82f3ec93caf43124af62cb2_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB + participant AMF1 + participant AMF2 + + Note right of gNB: identify slice policies +identify CN node supporting concerned slice(s) +or select default CN node + + gNB->>AMF1: NG SETUP REQUEST +(List of S-NSSAI(s) supported per TA) + AMF1-->>gNB: NG SETUP RESPONSE +(List of S-NSSAI(s) supported per PLMN) + gNB->>AMF2: NG SETUP REQUEST +(List of S-NSSAI(s) supported per TA) + AMF2-->>gNB: NG SETUP RESPONSE +(List of S-NSSAI(s) supported per PLMN) + + UE->>gNB: RRC(Connection)Setup Complete +(Temp ID optional, NSSAI optional) + + Note right of gNB: INITIAL UE MESSAGE + gNB->>AMF1: INITIAL UE MESSAGE + + Note right of AMF1: validate UE rights +and slice(s)availability + +``` + +The diagram illustrates the AMF selection process. It begins with the gNB sending an NG SETUP REQUEST to AMF1, followed by a response. The gNB then sends another NG SETUP REQUEST to AMF2 and receives a response. After the UE sends an RRC(Connection)Setup Complete message to the gNB, the gNB identifies slice policies and selects an AMF. Finally, the gNB sends an INITIAL UE MESSAGE to AMF1, which validates UE rights and slice availability. + +Sequence diagram for AMF selection (Figure 16.3.4.2-1). + +Figure 16.3.4.2-1: AMF selection + +In case a Temp ID is not available, the NG-RAN uses the NSSAI provided by the UE at RRC connection establishment to select the appropriate AMF (the information is provided after MSG3 of the random access procedure). If such information is also not available, the NG-RAN routes the UE to one of the configured default AMF(s). + +The NG-RAN uses the list of supported S-NSSAI(s) previously received in the NG Setup Response message when selecting the AMF with the NSSAI. This list may be updated via the AMF Configuration Update message. + +### 16.3.4.3 UE Context Handling + +Following the initial access, the establishment of the RRC connection and the selection of the correct AMF, the AMF establishes the complete UE context by sending the Initial Context Setup Request message to the NG-RAN over NG-C. The message contains the Allowed NSSAI and additionally contains the S-NSSAI(s) as part of the PDU session(s) resource description when present in the message and may contain Partially Allowed NSSAI. Upon successful establishment of the UE context and allocation of PDU session resources to the relevant network slice(s) when present, the NG-RAN responds with the Initial Context Setup Response message. + +![Sequence diagram for Network Slice-aware Initial Context Setup (Figure 16.3.4.3-1).](03a73cf37615028406f13c2aea732d60_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB + participant AMF1 + participant AMF2 + + Note over UE, AMF2: Preconditions: RRC Connection Establishment, AMF Instance Selection, Provisional policies may be applied + + AMF1->>gNB: INITIAL CONTEXT SETUP REQUEST +(Allowed NSSAI, one S-NSSAI per PDU Session when present) + + Note right of gNB: UE slice access confirmed +policies updated if needed + + gNB-->>AMF1: INITIAL CONTEXT SETUP RESPONSE + +``` + +The diagram shows the Network Slice-aware Initial Context Setup. It starts with a precondition note covering RRC Connection Establishment, AMF Instance Selection, and provisional policies. The AMF1 sends an INITIAL CONTEXT SETUP REQUEST to the gNB, which includes the Allowed NSSAI and one S-NSSAI per PDU Session. The gNB then confirms UE slice access and updates policies if needed. Finally, the gNB sends an INITIAL CONTEXT SETUP RESPONSE back to the AMF1. + +Sequence diagram for Network Slice-aware Initial Context Setup (Figure 16.3.4.3-1). + +Figure 16.3.4.3-1: Network Slice-aware Initial Context Setup + +### 16.3.4.4 PDU Session Setup Handling + +When new PDU sessions need to be established, the 5GC requests the NG-RAN to allocate/ resources relative to the relevant PDU sessions by means of the PDU Session Resource Setup procedures over NG-C. One S-NSSAI is added per PDU session to be established, so NG-RAN is enabled to apply policies at PDU session level according to the SLA represented by the network slice, while still being able to apply (for example) differentiated QoS within the slice. + +NG-RAN confirms the establishment of the resources for a PDU session associated to a certain network slice by responding with the PDU Session Resource Setup Response message over the NG-C interface. + +![Sequence diagram for Network Slice-aware PDU Session Resource Setup. Lifelines: UE, gNB, AMF1, AMF2. The process starts with a precondition 'UE Context is established in NG-RAN'. AMF1 sends a 'PDU SESSION RESOURCE SETUP REQUEST' (one S-NSSAI per PDU Session) to gNB. gNB verifies resources and sends a 'PDU SESSION RESOURCE SETUP RESPONSE' back to AMF1.](819f1d00e68b342a246b64fa888a97f9_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB + participant AMF1 + participant AMF2 + Note left of gNB: Precondition: UE Context is established in NG-RAN + AMF1->>gNB: PDU SESSION RESOURCE SETUP REQUEST +(one S-NSSAI per PDU Session) + Note right of gNB: NG-RAN verifies PDU session resources can be established for given Network Slice (in case of establishment) + gNB->>AMF1: PDU SESSION RESOURCE SETUP RESPONSE + +``` + +Sequence diagram for Network Slice-aware PDU Session Resource Setup. Lifelines: UE, gNB, AMF1, AMF2. The process starts with a precondition 'UE Context is established in NG-RAN'. AMF1 sends a 'PDU SESSION RESOURCE SETUP REQUEST' (one S-NSSAI per PDU Session) to gNB. gNB verifies resources and sends a 'PDU SESSION RESOURCE SETUP RESPONSE' back to AMF1. + +Figure 16.3.4.4-1: Network Slice-aware PDU Session Resource Setup + +### 16.3.4.5 Mobility + +To make mobility slice-aware in case of Network Slicing, S-NSSAI is introduced as part of the PDU session information that is transferred during mobility signalling. This enables slice-aware admission and congestion control. + +Both NG and Xn handovers are allowed regardless of the slice support of the target NG-RAN node i.e. even if the target NG-RAN node does not support the same slices as the source NG-RAN node. An example for the case of connected mode mobility across different Registration Areas is shown in Figure 16.3.4.5-1 for the case of NG based handover and in Figure 16.3.4.5-2 for the case of Xn based handover. + +![Sequence diagram for NG based mobility across different Registration Areas. Lifelines: UE, gNB1 (in Registration Area 1), gNB2 (in Registration Area 2), AMF. The process starts with 'UE in RRC_CONNECTED with n slices configured at NAS level and with m PDU sessions active'. Handover preparation to gNB2 is triggered. gNB1 sends 'HANDOVER REQUIRED' to AMF. AMF sends 'HANDOVER REQUEST' (Allowed NSSAI, one S-NSSAI per PDU Session) to gNB2. gNB2 sends 'HANDOVER REQUEST ACKNOWLEDGE' (List of accepted and failed PDU Sessions) to AMF. AMF sends 'HANDOVER COMMAND' to gNB1. Handover Execution occurs, followed by a 'Registration Area Update (alignment of slices supported in the new RA between UE and Network)'.](7cd0445f94b0b9c4e9566a23d221791e_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB1 as gNB1 in Registration Area 1 + participant gNB2 as gNB2 in Registration Area 2 + participant AMF + Note left of gNB1: UE in RRC_CONNECTED with n slices configured at NAS level and with m PDU sessions active + Note right of gNB1: Handover preparation to gNB2 triggered + gNB1->>AMF: HANDOVER REQUIRED + AMF->>gNB2: HANDOVER REQUEST +(Allowed NSSAI, one S-NSSAI per PDU Session) + gNB2->>AMF: HANDOVER REQUEST ACKNOWLEDGE +(List of accepted and failed PDU Sessions) + AMF->>gNB1: HANDOVER COMMAND + Note right of gNB1: Handover Execution + Note right of gNB1: Registration Area Update (alignment of slices supported in the new RA between UE and Network) + +``` + +Sequence diagram for NG based mobility across different Registration Areas. Lifelines: UE, gNB1 (in Registration Area 1), gNB2 (in Registration Area 2), AMF. The process starts with 'UE in RRC\_CONNECTED with n slices configured at NAS level and with m PDU sessions active'. Handover preparation to gNB2 is triggered. gNB1 sends 'HANDOVER REQUIRED' to AMF. AMF sends 'HANDOVER REQUEST' (Allowed NSSAI, one S-NSSAI per PDU Session) to gNB2. gNB2 sends 'HANDOVER REQUEST ACKNOWLEDGE' (List of accepted and failed PDU Sessions) to AMF. AMF sends 'HANDOVER COMMAND' to gNB1. Handover Execution occurs, followed by a 'Registration Area Update (alignment of slices supported in the new RA between UE and Network)'. + +Figure 16.3.4.5-1: NG based mobility across different Registration Areas + +![Sequence diagram illustrating Xn based mobility across different Registration Areas. The diagram shows the interaction between a UE, gNB1 (in Registration Area 1), gNB2 (in Registration Area 2), and AMF. The process starts with the UE in RRC_CONNECTED with n slices and m PDU sessions. gNB1 triggers Slice Aware Handover Preparation. A HANDOVER REQUEST (one S-NSSAI per PDU Session) is sent from gNB1 to gNB2. gNB2 performs Slice Aware Admission Control and sends a HANDOVER REQUEST ACKNOWLEDGE (List of admitted and non admitted PDU Sessions) back to gNB1. Handover Execution occurs. gNB2 sends a PATH SWITCH REQUEST (List of accepted and failed PDU Sessions) to the AMF. The AMF sends a PATH SWITCH REQUEST ACKNOWLEDGE (List of switched and released PDU Sessions, Allowed NSSAI) back to gNB2. Finally, a Registration Area Update (alignment of slices supported in the new RA between UE and Network) is performed.](c15cb6383bc35906e6b3c7c3aac621ed_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB1 as gNB1 in Registration Area 1 + participant gNB2 as gNB2 in Registration Area 2 + participant AMF + + Note left of UE: UE in RRC_CONNECTED with n slices configured at NAS level and with m PDU sessions active at AS level + Note right of gNB1: Slice Aware Handover Preparation from gNB1 to gNB2 triggered + gNB1->>gNB2: HANDOVER REQUEST (one S-NSSAI per PDU Session) + Note right of gNB2: Slice Aware Admission Control + gNB2->>gNB1: HANDOVER REQUEST ACKNOWLEDGE (List of admitted and non admitted PDU Sessions) + Note over UE, gNB1, gNB2: Handover Execution + gNB2->>AMF: PATH SWITCH REQUEST (List of accepted and failed PDU Sessions) + AMF->>gNB2: PATH SWITCH REQUEST ACKNOWLEDGE (List of switched and released PDU Sessions, Allowed NSSAI) + Note over UE, gNB1, gNB2, AMF: Registration Area Update (alignment of slices supported in the new RA between UE and Network) + +``` + +Sequence diagram illustrating Xn based mobility across different Registration Areas. The diagram shows the interaction between a UE, gNB1 (in Registration Area 1), gNB2 (in Registration Area 2), and AMF. The process starts with the UE in RRC\_CONNECTED with n slices and m PDU sessions. gNB1 triggers Slice Aware Handover Preparation. A HANDOVER REQUEST (one S-NSSAI per PDU Session) is sent from gNB1 to gNB2. gNB2 performs Slice Aware Admission Control and sends a HANDOVER REQUEST ACKNOWLEDGE (List of admitted and non admitted PDU Sessions) back to gNB1. Handover Execution occurs. gNB2 sends a PATH SWITCH REQUEST (List of accepted and failed PDU Sessions) to the AMF. The AMF sends a PATH SWITCH REQUEST ACKNOWLEDGE (List of switched and released PDU Sessions, Allowed NSSAI) back to gNB2. Finally, a Registration Area Update (alignment of slices supported in the new RA between UE and Network) is performed. + +Figure 16.3.4.5-2: Xn based mobility across different Registration Areas + +## 16.4 Public Warning System + +NR connected to 5GC provides support for public warning systems (PWS) through means of system information broadcast capability. NR is responsible for scheduling and broadcasting of the warning messages as well as for paging the UE to provide indication that the warning message is being broadcast: + +- Earthquake and Tsunami Warning System: ETWS is a public warning system developed to meet the regulatory requirements for warning notifications related to earthquake and/or tsunami events (see TS 22.168 [14]). ETWS warning notifications can either be a primary notification (short notification) or secondary notification (providing detailed information). +- Commercial Mobile Alert System: CMAS is a public warning system developed for the delivery of multiple, concurrent warning notifications (see TS 22.268 [15]). + +Different SIBs are defined for ETWS primary notification, ETWS secondary notification and CMAS notification. Paging is used to inform UEs about ETWS indication and CMAS indication (see clause 9.2.5). UE monitors ETWS/CMAS indication in its own paging occasion for RRC\_IDLE and for RRC\_INACTIVE while no SDT procedure (see clause 18.0) is ongoing. UE monitors ETWS/CMAS indication in any paging occasion for RRC Connected and during the SDT procedure in RRC\_INACTIVE. Paging indicating ETWS/CMAS notification triggers acquisition of system information (without delaying until the next modification period). + +Enhancements of public warning system (ePWS) enable broadcast of language-independent content and notifications to UEs with no user interface or with a user interface that is incapable of displaying text, see clause 9 in TS 22.268 [15] and TS 23.041 [54]. ETWS/CMAS notifications with ePWS functionality use the same AS mechanisms as ETWS/CMAS. + +KPAS and EU-Alert are public warning systems developed for the delivery of multiple, concurrent warning notifications (see TS 22.268 [15]). KPAS and EU-Alert uses the same AS mechanisms as CMAS. Therefore, the NR procedures defined for CMAS equally apply for KPAS and EU-Alert. + +## 16.5 Emergency Services + +### 16.5.1 Overview + +NG-RAN provides support for Emergency Services either directly or through fallback mechanisms towards E-UTRA. The support of Emergency Services is broadcast in system information (see TS 38.331 [12]). + +### 16.5.2 IMS Emergency call + +An IMS Emergency call support indication is provided to inform the UE that emergency bearer services are supported. In normal service state the UE is informed if the PLMN supports emergency services through an Emergency Service Support indicator in the Attach and TAU procedures (see TS 23.501 [3]). In limited service state and for emergency services other than eCall over IMS, a UE is informed about if a cell supports emergency services over NG-RAN from a broadcast indication (*ims-EmergencySupport*). The broadcast indicator is set to "support" if any AMF in a non-shared environment or at least one of the PLMN's in a shared environment supports IMS emergency bearer services. + +### 16.5.3 eCall over IMS + +NG-RAN broadcast an indication to indicate support of eCall over IMS (*eCallOverIMS-Support*). UEs that are in limited service state need to consider both *eCallOverIMS-Support* and *ims-EmergencySupport* to determine if eCall over IMS is possible. UEs that are not in limited service state need to only consider *eCallOverIMS-Support* to determine if eCall over IMS is possible. The broadcast indicator is set to "support" if the PLMN in a non-shared environment, or all PLMNs in a shared environment, supports eCall over IMS. + +### 16.5.4 Fallback + +RAT fallback towards E-UTRA connected to 5GC is performed when NR does not support Emergency Services and System fallback towards E-UTRA connected to EPS is performed when 5GC does not support Emergency Services. Depending on factors such as CN interface availability, network configuration and radio conditions, the fallback procedure results in either CONNECTED state mobility (handover procedure) or IDLE state mobility (redirection) - see TS 23.501 [3] and TS 38.331 [12]. + +## 16.6 Stand-Alone NPN + +### 16.6.1 General + +An SNPN is a network deployed for non-public use which does not rely on network functions provided by a PLMN (see clause 4.8). An SNPN is identified by a PLMN ID and NID (see clause 8.2) broadcast in SIB1. + +An SNPN-capable UE supports the SNPN access mode. When the UE is set to operate in SNPN access mode, the UE only selects and registers with SNPNs. When the UE is not set to operate in SNPN access mode, the UE performs normal PLMN selection procedures. + +Emergency services and ETWS /CMAS can be supported by SNPNs. An IMS Emergency call support indication is provided per SNPN to inform the UE which SNPN(s) support emergency bearer. In normal service state the indication is provided in the same way as in case of PLMNs (see clause 16.5.2). In limited service state and for emergency services other than eCall over IMS, a UE is informed whether an SNPN of the cell supports emergency services over NG-RAN from a per SNPN broadcast indication (*imsEmergencySupportForSNPN*). The broadcast indicator for an SNPN may be set to "support" if any AMF of the SNPN supports IMS emergency bearer services. + +NR-NR Dual Connectivity within a single SNPN or across SNPNs as indicated in the mobility restriction list is supported. + +## 16.6.2 Mobility + +### 16.6.2.1 General + +The same principles as described in 9.2 apply to SNPN except for what is described below. + +UEs operating in SNPN access mode only (re)select cells within the selected/registered SNPN or within equivalent SNPNs and a cell can only be considered as suitable if the PLMN and NID broadcast by the cell matches the selected/registered SNPN or an equivalent SNPN. + +In addition, manual selection of SNPN(s) is supported, for which HRNN(s) can be optionally provided. + +The roaming and access restrictions applicable to SNPN are described in clause 9.4. + +### 16.6.2.2 Inactive Mode + +The mobility of a UE in inactive mode builds on existing functionality described in clause 9.2.2 and is limited to the SNPN(s) identified within the mobility restrictions received in the UE context. + +### 16.6.2.3 Connected Mode + +The NG-RAN node is aware of the SNPN ID(s) supported by neighbour cells. + +At the time of handover, cells that do not support the serving SNPN ID or the SNPN ID of an equivalent SNPN within the mobility restrictions received in the UE context are not considered as candidate target cells by the source NG-RAN node. + +The target NG-RAN node performs access control. In case it cannot accept the handover for the serving SNPN the target NG-RAN node fails the handover including an appropriate cause value. + +## 16.6.3 Self-Configuration for SNPN + +Self-configuration is described in clause 15. In addition, on NG, the NG-RAN node signals the SNPN ID(s) supported per tracking area and the AMF signals the SNPN ID(s) supported per node; on Xn, NG-RAN nodes exchange SNPN ID(s) supported per cell. + +## 16.6.4 Access Control + +During the establishment of the UE-associated logical NG-connection towards the 5GC, the AMF checks whether the UE is allowed to access the cell for the signalled SNPN ID as specified in TS 23.501 [3]. + +If the check is successful, the AMF sets up the UE-associated logical NG-connection and provides the NG-RAN node with the mobility restrictions applicable for the SNPN. + +If the check is not successful, the AMF shall reject setting up the UE-associated NG connection and inform the NG-RAN node with an appropriate cause value as specified in TS 23.501 [3]. + +## 16.6.5 Access with subscription/credentials owned by a Credentials Holder + +An SNPN may allow access to UEs being authorized using credentials or subscription owned by a separate Credentials Holder (CH). The support of this feature is uniform across the SNPN as specified in TS 23.501 [3]. + +The following information is broadcast to support SNPN access with subscription of a Credentials Holder: + +- an indication per SNPN in SIB1 that access using credentials from a Credentials Holder is supported; +- optionally a list of supported GINs in SIB18 (each GIN may be assigned to one or more SNPNs); +- an optional indication per SNPN in SIB1 that the SNPN allows registration attempts from UEs that are not explicitly configured to select the SNPN. + +The above listed items are forwarded to the UE NAS layer that uses them for SNPN selection. + +## 16.6.6 Support of UE onboarding and remote provisioning + +An SNPN may offer support for restricted 3GPP connectivity for remote provisioning of credentials. The feature is enabled/disabled per cell. + +The following information is broadcast to support UE onboarding and remote provisioning: + +- an indication per onboarding SNPN in SIB1 that UE onboarding is enabled; +- optionally a list of supported GINs in SIB18 (each GIN may be assigned to one or more onboarding SNPNs). + +The above listed items are forwarded to the UE NAS layer that uses them for onboarding SNPN selection. When a UE intends to perform onboarding, it sends the onboarding request indication to the gNB during RRC connection establishment. + +The NG-RAN nodes receive information about onboarding support capabilities of the AMF(s). This information is used by the NG-RAN node to select a suitable AMF when receiving the onboarding request indication from the UE. + +## 16.7 Public Network Integrated NPN + +### 16.7.1 General + +A PNI-NPN is a network deployed for non-public use which relies on network functions provided by a PLMN (see clause 4.8). In PNI-NPN, a Closed Access Groups (CAG) identifies a group of subscribers who are permitted to access one or more CAG cells associated to the CAG. A CAG is identified by a CAG identifier broadcast in SIB1. + +A CAG-capable UE can be configured with the following per PLMN (see clause 5.30.3.3 of TS 23.501 [3]): + +- an Allowed CAG list containing the CAG identifiers which the UE is allowed to access; and +- a CAG-only indication if the UE is only allowed to access 5GS via CAG cells. + +Dual Connectivity is supported and may involve both PNI-NPN and PLMN cells, according to the mobility restrictions in the UE context as described in TS 37.340 [21]. + +### 16.7.2 Mobility + +#### 16.7.2.1 General + +The same principles as described in 9.2 apply to CAG cells except for what is described below. + +Cell selection/reselection to CAG cells may be based on a UE autonomous search function, which determines itself when/where to search, but cannot contradict the dedicated cell reselection priority information if any is stored. + +A range of PCI values reserved by the network for use by CAG cells may be broadcast. + +A CAG Member Cell for a UE is a cell broadcasting the identity of the selected PLMN, registered PLMN or equivalent PLMN, and for that PLMN, a CAG identifier belonging to the Allowed CAG list of the UE for that PLMN. The UE checks the suitability of CAG cells based on the Allowed CAG list provided by upper layers and a CAG-only cell can only be suitable for its subscribers but can be acceptable for the rest. + +**NOTE:** A non-CAG-capable UE (e.g. Rel-15 UE) considers a CAG-only cell as acceptable cell if the cell is not barred to Rel-15 UEs, and if a PLMN ID without CAG list is broadcast and that PLMN is forbidden (e.g. by use of a PLMN ID for which all registration attempts are rejected such that the PLMN ID becomes forbidden). + +When the UE is configured with a CAG-only indication, only CAG Member Cells can be suitable. A non-suitable cell can be acceptable though if the UE is configured with a CAG-only indication for one of the PLMN broadcast by the cell. + +In addition, manual selection of CAG cell(s) is supported, for which an HRNN(s) can be optionally provided. + +The roaming and access restrictions applicable to PNI-NPN are described in clause 9.4. + +### 16.7.2.2 Inactive Mode + +The mobility of a UE in inactive mode builds on existing functionality described in clause 9.2.2 according to the mobility restrictions received in the UE context. + +### 16.7.2.3 Connected Mode + +The source NG-RAN node is aware of the list of CAG IDs supported by the candidate target cells which are CAG cells. + +At the time of handover, the source NG-RAN node determines a target cell among the candidates which is compatible with the received PNI-NPN restrictions. + +At incoming handover, the target NG-RAN node receives the PNI-NPN mobility restrictions and checks that the selected target cell is compatible with the received mobility restrictions. + +Mobility between PNI-NPN and PLMN cells is supported according to the mobility restrictions in the UE context. + +## 16.7.3 Self-Configuration for PNI-NPN + +Self-configuration is described in clause 15. + +In addition, each NG-RAN node informs the connected neighbour NG-RAN nodes of the list of supported CAG ID(s) per CAG cell in the appropriate Xn interface management procedures. + +## 16.7.4 Access Control + +During the establishment of the UE-associated logical NG-connection towards the 5GC, the AMF checks whether the UE is allowed to access the cell as specified in TS 23.501 [3]. + +If the check is successful, the AMF sets up the UE-associated logical NG-connection and provides the NG-RAN node with the list of CAGs allowed for the UE and, whether the UE is allowed to access non-CAG cells. This information is used by the NG-RAN for access control of subsequent mobility. + +If the check is not successful, the AMF shall reject setting up the UE-associated NG connection and inform the NG-RAN node with an appropriate cause value as specified in TS 23.501 [3]. + +## 16.7.5 Paging + +The NG-RAN node may receive a paging message including the list of CAGs allowed for the UE, and whether the UE is allowed to access non-CAG cells. The NG-RAN node may use this information to avoid paging in cells on which the UE is not allowed to camp. + +For UEs in RRC\_INACTIVE state, the NG-RAN node may page a neighbour NG-RAN node including the list of CAGs allowed for the UE, and whether the UE is allowed to access non-CAG cells. The neighbour NG-RAN node may use this information to avoid paging in cells on which the UE is not allowed to camp. + +# 16.8 Support for Time Sensitive Communications + +## 16.8.1 General + +Time Sensitive Communications (TSC), as defined in TS 23.501 [3], is a communication service that supports deterministic communication and/or isochronous communication with high reliability and availability. Examples of such services are the ones in the area of Industrial Internet of Things, e.g. related to cyber-physical control applications as described in TS 22.104 [39]. + +To support strict synchronization accuracy requirements of TSC applications, the gNB may signal 5G system time reference information to the UE using unicast or broadcast RRC signalling with a granularity of 10 ns. Uncertainty parameter may be included in reference time information to indicate its accuracy. The UE may indicate to the gNB a preference to be provisioned with reference time information using UE Assistance Information procedure. Propagation delay compensation (PDC) mechanisms may be applied based on RTT or TA, and can be performed at the UE or gNB side. When performed at UE side, the PDC mechanisms are controlled via RRC signalling by the gNB. + +The RTT-based PDC mechanism is achieved by using Rx-Tx time difference measurements of a single pair of configured TRS/PRS and SRS. The following figure describes the signalling procedures of UE-side RTT-based PDC: + +![Figure 16.8-1: Signalling Procedure of UE-side RTT-based PDC. This sequence diagram shows the interaction between a UE and a gNB. 1. The gNB sends a 'UE measurement configuration' to the UE. 2a. The gNB sends 'TRS or PRS' to the UE. 2b. The UE sends 'SRS' to the gNB. 3a. The UE performs a 'UE Rx-Tx time difference measurement'. 3b. The gNB performs a 'gNB Rx-Tx time difference measurement'. 4. The gNB sends its 'gNB Rx-Tx time difference measurement' to the UE. 5. The UE performs PDC based on both measurements.](5525e7460947727851585808324e1f98_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB + Note left of UE: 3a. UE Rx-Tx time difference measurement + Note right of gNB: 3b. gNB Rx-Tx time difference measurement + gNB->>UE: 1. UE measurement configuration + gNB->>UE: 2a. TRS or PRS + UE->>gNB: 2b. SRS + Note left of UE: 3a. UE Rx-Tx time difference measurement + Note right of gNB: 3b. gNB Rx-Tx time difference measurement + gNB->>UE: 4. gNB Rx-Tx time difference measurement + Note left of UE: 5. UE performs PDC + +``` + +Figure 16.8-1: Signalling Procedure of UE-side RTT-based PDC. This sequence diagram shows the interaction between a UE and a gNB. 1. The gNB sends a 'UE measurement configuration' to the UE. 2a. The gNB sends 'TRS or PRS' to the UE. 2b. The UE sends 'SRS' to the gNB. 3a. The UE performs a 'UE Rx-Tx time difference measurement'. 3b. The gNB performs a 'gNB Rx-Tx time difference measurement'. 4. The gNB sends its 'gNB Rx-Tx time difference measurement' to the UE. 5. The UE performs PDC based on both measurements. + +**Figure 16.8-1: Signalling Procedure of UE-side RTT-based PDC** + +1. The gNB provides measurement configurations to the UE; +- 2a/b. The gNB transmits TRS or PRS to the UE for measurements, and the UE transmits SRS to the gNB for measurement; +- 3a/b. Both the UE and the gNB perform Rx-Tx time difference measurements; +4. The gNB provides its Rx-Tx time difference measurement to the UE; +5. The UE performs PDC based on Rx-Tx time difference measurements from itself and the gNB. + +The following figure describes the signalling procedures of gNB-side RTT-based PDC: + +![Figure 16.8-2: Signalling Procedure of gNB-side RTT-based PDC. This sequence diagram shows the interaction between a UE and a gNB. 1. The gNB sends a 'UE measurement configuration' to the UE. 2a. The gNB sends 'TRS or PRS' to the UE. 2b. The UE sends 'SRS' to the gNB. 3a. The UE performs a 'UE Rx-Tx time difference measurement'. 3b. The gNB performs a 'gNB Rx-Tx time difference measurement'. 4. The UE sends its 'UE Rx-Tx time difference measurement report' to the gNB. 5. The gNB performs PDC based on both measurements.](f4e64712104f326ff259928d8126f1f6_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB + Note left of UE: 3a. UE Rx-Tx time difference measurement + Note right of gNB: 3b. gNB Rx-Tx time difference measurement + gNB->>UE: 1. UE measurement configuration + gNB->>UE: 2a. TRS or PRS + UE->>gNB: 2b. SRS + Note left of UE: 3a. UE Rx-Tx time difference measurement + Note right of gNB: 3b. gNB Rx-Tx time difference measurement + UE->>gNB: 4. UE Rx-Tx time difference measurement report + Note right of gNB: 5. gNB performs PDC + +``` + +Figure 16.8-2: Signalling Procedure of gNB-side RTT-based PDC. This sequence diagram shows the interaction between a UE and a gNB. 1. The gNB sends a 'UE measurement configuration' to the UE. 2a. The gNB sends 'TRS or PRS' to the UE. 2b. The UE sends 'SRS' to the gNB. 3a. The UE performs a 'UE Rx-Tx time difference measurement'. 3b. The gNB performs a 'gNB Rx-Tx time difference measurement'. 4. The UE sends its 'UE Rx-Tx time difference measurement report' to the gNB. 5. The gNB performs PDC based on both measurements. + +**Figure 16.8-2: Signalling Procedure of gNB-side RTT-based PDC** + +1. The gNB provides measurement configurations to the UE; + +- 2a/b. The gNB transmits TRS or PRS to the UE for measurements, and the UE transmits SRS to the gNB for measurement; +- 3a/b. Both the UE and the gNB perform Rx-Tx time difference measurements; +- 4. The UE reports its Rx-Tx time difference measurement to the gNB; +- 5. The gNB performs PDC based on Rx-Tx time difference measurements from itself and the UE. + +The gNB may also receive TSC Assistance Information (TSCAI), see TS 23.501 [3], from the Core Network, e.g. during QoS flow establishment, or from another gNB during handover. TSCAI contains additional information about the traffic flow such as burst arrival time, burst periodicity, and survival time. TSCAI knowledge may be leveraged in the gNB's scheduler to more efficiently schedule periodic, deterministic traffic flows either via Configured Grants, Semi-Persistent Scheduling or with dynamic grants, and/or to improve the associated link reliability to meet the survival time requirement (see TS 22.104 [39]). + +To support uplink periodic traffics of services with survival time requirement, configured grant resources can be used such that the mapping relation between the service and the configured grant is known to both gNB and UE, thus allowing the gNB to use configured grant retransmission scheduling (addressed by CS-RNTI) to trigger survival time state entry for the corresponding DRB. Upon survival time state entry, all RLC entities configured for the DRB are activated by the UE for duplication to prevent failure of subsequent messages and hence fulfilling the survival time requirement. If CA or DC duplication for the DRB is already activated, the DRB should enter survival time state when any retransmission grant for any of its active LCHs is received. + +## 16.8.2 Network timing synchronization monitoring + +### 16.8.2.1 General + +While time synchronization service is offered by the 5GS, the network timing synchronization status of the gNB may change. The gNB detects timing synchronization degradation or improvement locally and informs the consumer of the information as follows: + +- TSCTSF may receive information about timing synchronization status from the gNB via the AMF based on node-level reporting configuration; +- UE may receive clock quality information from the gNB based on UE-level clock quality control information. + +### 16.8.2.2 Network timing synchronization monitoring towards CN + +For NG-RAN timing synchronization monitoring support, the 5GC initiates RAN Timing Synchronisation Status (TSS) Reporting procedure to obtain the change of network timing synchronization status of gNBs. + +The gNB may receive RAN timing synchronization status information request from the AMF, see TS 23.501 [3]. The RAN timing synchronization status information includes the gNB node-level information about timing synchronization operation status. The gNB timing synchronization status may comprise one or more of the following information elements: synchronization state, traceability to UTC, traceability to GNSS, clock frequency stability, clock accuracy, parent time source, as defined in Table 5.27.1.12-1 in TS 23.501 [3]. + +Based on NG-RAN's capabilities of reporting timing synchronisation status, NG-RAN accepts or rejects the request from AMF. NG-RAN can be pre-configured with thresholds for attributes on timing synchronisation status reporting via OAM. When the thresholds are met or exceeded, events will be triggered and NG-RAN reports Timing Synchronization Status to AMF. For detailed procedure on the Timing Synchronization Status reporting, refer to TS 38.401 Clause 8.x.1 [4]. + +### 16.8.2.3 Network timing synchronization monitoring towards UE + +The gNB may receive clock quality reporting control information for a UE from the AMF, see TS 23.501 [3]. The clock quality reporting control information contains the clock quality detail level (i.e., "metrics" or "acceptable/not acceptable indication") and clock quality acceptance criteria for the UE (if the clock quality detail level equals "acceptable/not acceptable indication"). Based on the clock quality reporting control information, the gNB determines how to provision clock quality information to the UE: + +- If the clock quality detail level equals "clock quality metrics", the gNB provides clock quality metrics supported by the gNB to the UE, i.e., one or more of the following information elements: synchronization state, traceability to UTC, traceability to GNSS, clock frequency stability, clock accuracy, parent time source, as defined in Table 5.27.1.12-1 in TS 23.501 [3]. +- If the clock quality detail level equals "acceptable/not acceptable indication", the gNB indicates "acceptable" to the UE if the gNB's timing synchronization status matches the acceptance criteria received from the AMF; otherwise, the gNB indicates "not acceptable" to the UE. Clock quality acceptance criteria can be defined based on one or more information elements listed in Table 5.27.1.12-1 in TS 23.501 [3]. + +To provision clock quality information to the UEs: + +- For UEs in the RRC CONNECTED state, the gNB uses unicast RRC signalling. The RRC signalling includes Event ID and clock quality information. +- For UEs that are not in the RRC\_CONNECTED state, the UE first needs to establish or resume the RRC connection to receive the gNB timing synchronization status information from the gNB via unicast RRC signalling. The gNB broadcasts Event ID in SIB9 to notify its timing synchronization status. Event ID or gNB ID change serves as a notification for the UEs reading the SIB information that there is new RAN timing synchronization status information available. + +The following figure describes the signalling procedure of gNB reporting clock quality information to a UE: + +![Sequence diagram showing the signalling procedure of gNB reporting clock quality information to a UE. The diagram involves two main entities: UE and gNB. The sequence starts with the UE in RRC_INACTIVE/IDLE state and the gNB detecting a time synchronization status change. The gNB then broadcasts SIB9 (Event ID) to the UE. The UE determines if there is a clock quality information update available. If so, it initiates RRC Setup for RRC_IDLE or RRC Resume for RRC_INACTIVE. The gNB then determines the clock quality information reporting for the UE and sends a DLInfoTransfer message (clock quality information) to the UE.](7b24e2d4d1416a6411999a7f02fa5414_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB + Note left of UE: RRC_INACTIVE/IDLE state + Note right of gNB: 0. Time synchronization status change at the gNB + gNB->>UE: 1. SIB9 (Event ID) + Note left of UE: 2. UE determines if there is clock quality information update available + Note left of UE: 3. RRC Setup for RRC_IDLE or RRC Resume for RRC_INACTIVE + Note right of gNB: 4. gNB determines clock quality information reporting for the UE + gNB->>UE: 5. DLInfoTransfer message (clock quality information) + +``` + +Sequence diagram showing the signalling procedure of gNB reporting clock quality information to a UE. The diagram involves two main entities: UE and gNB. The sequence starts with the UE in RRC\_INACTIVE/IDLE state and the gNB detecting a time synchronization status change. The gNB then broadcasts SIB9 (Event ID) to the UE. The UE determines if there is a clock quality information update available. If so, it initiates RRC Setup for RRC\_IDLE or RRC Resume for RRC\_INACTIVE. The gNB then determines the clock quality information reporting for the UE and sends a DLInfoTransfer message (clock quality information) to the UE. + +**Figure 16.8.2-1: Signalling procedure of gNB reporting clock quality information to a UE** + +0. The gNB node is pre-configured for the thresholds for each timing synchronization status attribute as described in clause 5.27.1.12 in TS 23.501 [3]. If there is a change on its primary source so that the thresholds are exceeded or met again, the NG-RAN node detects a change on its timing synchronization state (e.g., degradation, failure, recovery). +1. The gNB notifies a change on its timing synchronization operation using Event ID in SIB9. The Event ID scope is local to gNB. +2. The UE in RRC\_INACTIVE or RRC\_IDLE determines if there is clock quality information update available at the gNB based on SIB9 information. For a UE in RRC\_CONNECTED state, steps 2-3 can be skipped. +3. If there is a RAN timing synchronization status update available, the UE's RRC layer indicates this to the NAS layer which may request the RRC layer to initiate RRC Setup or RRC Resume procedure. +4. The gNB determines clock quality information reporting to the UE (e.g., metrics or "acceptable/not acceptable"). + +5. The gNB sends the clock quality information to the UE via unicast RRC signalling. + +### 16.8.3 RAN feedback for adaptation of Burst Arrival Time and Periodicity + +The NG-RAN may support the proactive feedback and reactive feedback mechanisms as specified in TS 23.501 [3]. The NG-RAN can provide the feedback in order to align the arrival of the traffic bursts with the next expected transmission opportunity over the air interface in each direction (i.e. DL or UL) for a QoS flow. + +## 16.9 Sidelink + +### 16.9.1 General + +In this clause, an overview of NR sidelink communication and how NG-RAN supports NR sidelink communication, V2X sidelink communication and Ranging/Sidelink positioning is given. V2X sidelink communication is specified in TS 36.300 [2]. Ranging/Sidelink positioning is specified in TS 38.305 [42]. + +The NG-RAN architecture supports the PC5 interface as illustrated in Figure 16.9.1-1. Sidelink transmission and reception over the PC5 interface are supported when the UE is inside NG-RAN coverage, irrespective of which RRC state the UE is in, and when the UE is outside NG-RAN coverage. + +![Diagram illustrating the NG-RAN Architecture supporting the PC5 interface. Two User Equipment (UE) icons, represented as blue cones with antennas, are shown. A horizontal green line connects the two UEs, representing the PC5 interface. Each UE is positioned above a grey oval representing its coverage area.](ca22c6236ae7c9a8e76d79c469c452a6_img.jpg) + +Diagram illustrating the NG-RAN Architecture supporting the PC5 interface. Two User Equipment (UE) icons, represented as blue cones with antennas, are shown. A horizontal green line connects the two UEs, representing the PC5 interface. Each UE is positioned above a grey oval representing its coverage area. + +**Figure 16.9.1-1: NG-RAN Architecture supporting the PC5 interface** + +Support of V2X services via the PC5 interface can be provided by NR sidelink communication and/or V2X sidelink communication. NR sidelink communication may be used to support other services than V2X services. + +NR sidelink communication can support one of three types of transmission modes for a pair of a Source Layer-2 ID and a Destination Layer-2 ID in the AS: + +- **Unicast transmission**, characterized by: + - Support of one PC5-RRC connection between peer UEs for the pair; + - Transmission and reception of control information and user traffic between peer UEs in sidelink; + - Support of sidelink HARQ feedback; + - Support of sidelink transmit power control; + - Support of RLC AM; + - Detection of radio link failure for the PC5-RRC connection. + +- **Groupcast transmission**, characterized by: + - Transmission and reception of user traffic among UEs belonging to a group in sidelink; + - Support of sidelink HARQ feedback. +- **Broadcast transmission**, characterized by: + - Transmission and reception of user traffic among UEs in sidelink. + +## 16.9.2 Radio Protocol Architecture for NR sidelink communication + +### 16.9.2.1 Overview + +The AS protocol stack for the control plane for SCCH for RRC in the PC5 interface consists of RRC, PDCP, RLC and MAC sublayers, and the physical layer. The protocol stack of control plane for SCCH for RRC is shown in Figure 16.9.2.1-1. + +![Diagram of the control plane protocol stack for SCCH for RRC. It shows two User Equipment (UE) blocks, each represented by a large black rectangle. Below each black rectangle is a dashed box containing two smaller white rectangles. A horizontal double-headed arrow connects the two white rectangles, representing the RRC protocol stack across the PC5 interface.](057e0fadbc74743547d314f6fd0ff686_img.jpg) + +Diagram of the control plane protocol stack for SCCH for RRC. It shows two User Equipment (UE) blocks, each represented by a large black rectangle. Below each black rectangle is a dashed box containing two smaller white rectangles. A horizontal double-headed arrow connects the two white rectangles, representing the RRC protocol stack across the PC5 interface. + +**Figure 16.9.2.1-1: Control plane protocol stack for SCCH for RRC.** + +For support of PC5-S protocol specified in TS 23.287 [40], PC5-S is located on top of PDCP, RLC and MAC sublayers, and the physical layer in the control plane protocol stack for SCCH for PC5-S, as shown in Figure 16.9.2.1-2. + +![Diagram of the control plane protocol stack for SCCH for PC5-S. It shows two User Equipment (UE) blocks, each represented by a large black rectangle. Below each black rectangle is a dashed box containing two smaller white rectangles. A horizontal double-headed arrow connects the two white rectangles, representing the PC5-S protocol stack across the PC5 interface.](2ff9776a780f30bc64c7a9ef23131cbf_img.jpg) + +Diagram of the control plane protocol stack for SCCH for PC5-S. It shows two User Equipment (UE) blocks, each represented by a large black rectangle. Below each black rectangle is a dashed box containing two smaller white rectangles. A horizontal double-headed arrow connects the two white rectangles, representing the PC5-S protocol stack across the PC5 interface. + +**Figure 16.9.2.1-2: Control plane protocol stack for SCCH for PC5-S.** + +The AS protocol stack for SBCCH in the PC5 interface consists of RRC, RLC, MAC sublayers, and the physical layer as shown below in Figure 16.9.2.1-3. + +![Figure 16.9.2.1-3: Control plane protocol stack for SBCCH. The diagram shows two protocol stacks. The left stack has a black top section, a dashed box containing two white rectangles, and a bottom white rectangle. The right stack is identical. A horizontal double-headed arrow connects the two bottom white rectangles, indicating bidirectional communication between the control plane protocols of two User Equipment (UE) devices.](0eb348bf17d67bf96326e07011d1c1ad_img.jpg) + +Figure 16.9.2.1-3: Control plane protocol stack for SBCCH. The diagram shows two protocol stacks. The left stack has a black top section, a dashed box containing two white rectangles, and a bottom white rectangle. The right stack is identical. A horizontal double-headed arrow connects the two bottom white rectangles, indicating bidirectional communication between the control plane protocols of two User Equipment (UE) devices. + +**Figure 16.9.2.1-3: Control plane protocol stack for SBCCH.** + +The AS protocol stack for user plane in the PC5 interface consists of SDAP, PDCP, RLC and MAC sublayers, and the physical layer. The protocol stack of user plane is shown in Figure 16.9.2.1-4. + +![Figure 16.9.2.1-4: User plane protocol stack for STCH. The diagram shows two protocol stacks. The left stack has a black top section, a dashed box containing two white rectangles, and a bottom white rectangle. The right stack is identical. A horizontal double-headed arrow connects the two bottom white rectangles, indicating bidirectional communication between the user plane protocols of two User Equipment (UE) devices.](c2dbaf7c88ad38cb8620f6d731935ed8_img.jpg) + +Figure 16.9.2.1-4: User plane protocol stack for STCH. The diagram shows two protocol stacks. The left stack has a black top section, a dashed box containing two white rectangles, and a bottom white rectangle. The right stack is identical. A horizontal double-headed arrow connects the two bottom white rectangles, indicating bidirectional communication between the user plane protocols of two User Equipment (UE) devices. + +**Figure 16.9.2.1-4: User plane protocol stack for STCH.** + +Sidelink Radio bearers (SLRB) are categorized into two groups: sidelink data radio bearers (SL DRB) for user plane data and sidelink signalling radio bearers (SL SRB) for control plane data. Separate SL SRBs using different SCCHs are configured for PC5-RRC and PC5-S signalling respectively. + +## 16.9.2.2 MAC + +The MAC sublayer provides the following services and functions over the PC5 interface in addition to the services and functions specified in clause 6.2.1: + +- Radio resource selection; +- Packet filtering; +- Priority handling between uplink and sidelink transmissions for a given UE; +- Sidelink CSI reporting. + +With LCP restrictions in MAC, only sidelink logical channels belonging to the same destination can be multiplexed into a MAC PDU for every unicast, groupcast and broadcast transmission which is associated to the destination. NG-RAN can also control whether a sidelink logical channel can utilise the resources allocated to a configured sidelink grant Type 1 (see clause 16.9.3.2). For transmissions to RX UE(s) using SL DRX operation, LCP ensures that a TX UE transmits data in the active time of the RX UE(s). + +For packet filtering, a SL-SCH MAC header including portions of both Source Layer-2 ID and a Destination Layer-2 ID is added to each MAC PDU as specified in clause 8.4. LCID included within a MAC subheader uniquely identifies a logical channel within the scope of the Source Layer-2 ID and Destination Layer-2 ID combination. + +The following logical channels are used in sidelink: + +- Sidelink Control Channel (SCCH): a sidelink channel for transmitting control information (i.e. PC5-RRC and PC5-S messages) and NR sidelink discovery messages from one UE to other UE(s); + +- Sidelink Traffic Channel (STCH): a sidelink channel for transmitting user information from one UE to other UE(s); +- Sidelink Broadcast Control Channel (SBCCH): a sidelink channel for broadcasting sidelink system information from one UE to other UE(s). + +The following connections between logical channels and transport channels exist: + +- SCCH can be mapped to SL-SCH; +- STCH can be mapped to SL-SCH; +- SBCCH can be mapped to SL-BCH. + +### 16.9.2.3 RLC + +The services and functions of the RLC sublayer as specified in clause 6.3.2 are supported for sidelink. TM is used for SBCCH. Both UM and AM are used in unicast transmission while only UM is used in groupcast or broadcast transmission. For UM, only unidirectional transmission is supported for groupcast and broadcast. + +### 16.9.2.4 PDCP + +The services and functions of the PDCP sublayer as specified in clause 6.4.1 are supported for sidelink with some restrictions: + +- Out-of-order delivery is supported only for unicast transmission; +- Duplication is not supported over the PC5 interface. + +### 16.9.2.5 SDAP + +The SDAP sublayer provides the following service and function over the PC5 interface: + +- Mapping between a QoS flow and a sidelink data radio bearer. + +There is one SDAP entity per destination for one of unicast, groupcast and broadcast which is associated to the destination. Reflective QoS is not supported over the PC5 interface. + +### 16.9.2.6 RRC + +The RRC sublayer provides the following services and functions over the PC5 interface: + +- Transfer of a PC5-RRC message between peer UEs; +- Maintenance and release of a PC5-RRC connection between two UEs; +- Detection of sidelink radio link failure for a PC5-RRC connection; +- Measurement configuration and reporting related to sidelink. + +A PC5-RRC connection is a logical connection between two UEs for a pair of Source and Destination Layer-2 IDs which is considered to be established after a corresponding PC5 unicast link is established as specified in TS 23.287 [40]. There is one-to-one correspondence between the PC5-RRC connection and the PC5 unicast link. A UE may have multiple PC5-RRC connections with one or more UEs for different pairs of Source and Destination Layer-2 IDs. + +Separate PC5-RRC procedures and messages are used for a UE to transfer UE capability and sidelink configuration to the peer UE, as specified in TS 38.331 [3]. Both peer UEs can exchange their own UE capability and sidelink configuration using separate bi-directional procedures in both sidelink directions. + +If it is not interested in sidelink transmission, if sidelink RLF on the PC5-RRC connection is declared, or if the Layer-2 link release procedure is completed as specified in TS 23.287 [40], UE releases the PC5-RRC connection. + +## 16.9.3 Radio Resource Allocation + +### 16.9.3.1 General + +For NR sidelink communication, the UE can operate in two modes as specified in 5.7.2 for resource allocation in sidelink: + +- Scheduled resource allocation, characterized by: + - The UE needs to be RRC\_CONNECTED in order to transmit data; + - NG-RAN schedules transmission resources. +- UE autonomous resource selection, characterized by: + - The UE can transmit data when inside NG-RAN coverage, irrespective of which RRC state the UE is in, and when outside NG-RAN coverage; + - The UE autonomously selects transmission resources from resource pool(s). + +For NR sidelink communication, the UE performs sidelink transmissions only on a single carrier. + +### 16.9.3.2 Scheduled Resource Allocation + +NG-RAN can dynamically allocate resources to the UE via the SL-RNTI on PDCCH(s) for NR sidelink communication. + +In addition, NG-RAN can allocate sidelink resources to a UE with two types of configured sidelink grants: + +- With type 1, RRC directly provides the configured sidelink grant only for NR sidelink communication; +- With type 2, RRC defines the periodicity of the configured sidelink grant while PDCCH can either signal and activate the configured sidelink grant, or deactivate it. The PDCCH is addressed to SL-CS-RNTI for NR sidelink communication. + +Besides, NG-RAN can also semi-persistently allocate sidelink resources to the UE via the SL Semi-Persistent Scheduling V-RNTI on PDCCH(s) for V2X sidelink communication. + +For the UE performing NR sidelink communication, there can be more than one configured sidelink grant activated at a time on the carrier configured for sidelink transmission. + +When beam failure or physical layer problem occurs on MCG, the UE can continue using the configured sidelink grant Type 1 until initiation of the RRC connection re-establishment procedure as specified in TS 38.331 [12]. During handover, the UE can be provided with configured sidelink grants via handover command, regardless of the type. If provided, the UE activates the configured sidelink grant Type 1 upon reception of the handover command or execution of CHO. + +The UE can send sidelink buffer status report to support scheduler operation in NG-RAN. For NR sidelink communication, the sidelink buffer status reports refer to the data that is buffered in for a group of logical channels (LCG) per destination in the UE. Eight LCGs are used for reporting of the sidelink buffer status reports. Two formats, which are SL BSR and truncated SL BSR, are used. + +### 16.9.3.3 UE Autonomous Resource Selection + +The UE autonomously selects sidelink resource(s) from resource pool(s) provided by broadcast system information or dedicated signalling while inside NG-RAN coverage or by pre-configuration while outside NG-RAN coverage. + +For NR sidelink communication, the resource pool(s) can be provided for a given validity area where the UE does not need to acquire a new pool of resources while moving within the validity area, at least when this pool is provided by SIB. The NR SIB area scope mechanism as specified in TS 38.331 [12] is reused to enable validity area for SL resource pool configured via broadcasted system information. + +The UE is allowed to temporarily use UE autonomous resource selection with random selection for sidelink transmission based on configuration of the exceptional transmission resource pool as specified in TS 38.331 [12]. + +## 16.9.4 Uu Control + +### 16.9.4.1 General + +When a UE is inside NG-RAN coverage, NR sidelink communication and/or V2X sidelink communication can be configured and controlled by NG-RAN via dedicated signalling or system information: + +- The UE should support and be authorized to perform NR sidelink communication and/or V2X sidelink communication in NG-RAN; +- If configured, the UE performs V2X sidelink communication as specified in TS 36.300 [2] unless otherwise specified, with the restriction that the dynamic scheduling for V2X sidelink communication (i.e. based on SL-V-RNTI) is not supported; +- NG-RAN can provide the UE with intra-carrier sidelink configuration, inter-carrier sidelink configuration and anchor carrier(s) which provide sidelink configuration via a Uu carrier for NR sidelink communication and/or V2X sidelink communication; +- When the UE cannot simultaneously perform both NR sidelink transmission and NR uplink transmission in time domain, prioritization between both transmissions is done based on their priorities and thresholds configured by the NG-RAN or pre-configured. When the UE cannot simultaneously perform both V2X sidelink transmission and NR uplink transmission in time domain, prioritization between both transmissions is done based on the priorities (i.e. PPPP) of V2X sidelink communication and a threshold configured by the NG-RAN or pre-configured. + +When a UE is outside NG-RAN coverage, SL DRB configuration(s) are preconfigured to the UE for NR sidelink communication. If UE changes the RRC state but has not received the SL DRB configuration(s) for the new RRC state, UE continues using the configuration obtained in the previous RRC state to perform sidelink data transmissions and receptions until the configuration for the new RRC state is received. + +### 16.9.4.2 Control of connected UEs + +The UE in RRC\_CONNECTED performs NR sidelink communication and/or V2X sidelink communication, as configured by the upper layers. The UE sends Sidelink UE Information to NG-RAN in order to request or release sidelink resources and report QoS information for each destination. + +NG-RAN provides *RRReconfiguration* to the UE in order to provide the UE with dedicated sidelink configuration. The *RRReconfiguration* may include SL DRB configuration(s) for NR sidelink communication as well as mode 1 resource configuration and/or mode 2 resource configuration. If UE has received SL DRB configuration via system information, UE should continue using the configuration to perform sidelink data transmissions and receptions until a new configuration is received via the *RRReconfiguration*. + +NG-RAN may also configure measurement and reporting of CBR for NR sidelink communication and V2X sidelink communication, and reporting of location information for V2X sidelink communication to the UE via *RRReconfiguration*. + +During handover, the UE performs sidelink transmission and reception based on configuration of the exceptional transmission resource pool or configured sidelink grant Type 1 and reception resource pool of the target cell as provided in the handover command. + +### 16.9.4.3 Control of idle/inactive UEs + +The UE in RRC\_IDLE or RRC\_INACTIVE performs NR sidelink communication and/or V2X sidelink communication, as configured by the upper layers. NG-RAN may provide common sidelink configuration to the UE in RRC\_IDLE or RRC\_INACTIVE via system information for NR sidelink communication and/or V2X sidelink communication. UE receives resource pool configuration and SL DRB configuration via *SIB12* for NR sidelink communication as specified in TS 38.331 [12], and/or resource pool configuration via *SIB13* and *SIB14* for V2X sidelink communication as specified in TS 38.331 [12]. + +When the UE performs cell reselection, the UE interested in V2X service(s) considers at least whether NR sidelink communication and/or V2X sidelink communication are supported by the cell. The UE may consider the following carrier frequency as the highest priority frequency, except for the carrier only providing the anchor carrier: + +- the frequency providing both NR sidelink communication configuration and V2X sidelink communication configuration, if configured to perform both NR sidelink communication and V2X sidelink communication; +- the frequency providing NR sidelink communication configuration, if configured to perform only NR sidelink communication. +- the frequency providing V2X sidelink communication configuration, if configured to perform only V2X sidelink communication. + +When the UE performs cell reselection, the UE interested in ProSe service(s) considers at least whether NR sidelink communication/discovery is supported by the cell. The UE may consider the carrier frequency providing NR sidelink communication/discovery configuration as the highest priority frequency, except for the carrier only providing the anchor carrier. + +## 16.9.5 Sidelink Discovery + +The UE may perform NR sidelink discovery while in-coverage or out-of-coverage for non-relay operation. + +The Relay discovery mechanism described in clause 16.12.3 (except the U2N Relay specific threshold based discovery message transmission and U2N Relay specific resource allocation mode restriction) is also applied to sidelink discovery. + +## 16.9.6 SL DRX + +### 16.9.6.1 General + +Sidelink supports SL DRX for unicast, groupcast, and broadcast. Similar parameters as defined in clause 11 for Uu (on-duration, inactivity-timer, retransmission-timer, cycle) are defined for SL to determine the SL active time for SL DRX. During the SL active time, the UE performs SCI monitoring for data reception (i.e., PSCCH and 2nd stage SCI on PSSCH). The UE may skip monitoring of SCI for data reception during SL DRX inactive time. + +The actual parameters supported for each cast type (unicast, groupcast, broadcast) are specified in the following clauses. + +The SL active time of the RX UE includes the time in which any of its applicable SL on-duration timer(s), SL inactivity-timer(s) or SL HARQ retransmission timer(s) (for any of unicast, groupcast, or broadcast) are running. In addition, the slots associated with announced periodic transmissions by the TX UE and the time in which a UE is expecting CSI report following a CSI request (for unicast) are considered as SL active time of the RX UE. The time for the unicast link establishment procedure and the time for the PC5 RRC reconfiguration with initial SL DRX configuration procedure as specified in clause 5.28.2 of TS 38.321 [6] are considered as SL active time of the RX UE. + +The TX UE maintains a set of timers corresponding to the SL DRX timers in the RX UE(s) for each pair of source/destination L2 ID for unicast or destination L2 ID for groupcast/broadcast. When data is available for transmission to one or more RX UE(s) configured with SL DRX, the TX UE selects resources taking into account the active time of the RX UE(s). + +The UE can determine from SIB12 whether the gNB supports SL DRX or not. + +### 16.9.6.2 Unicast + +For unicast, SL DRX is configured per pair of source L2 ID and destination L2 ID. + +The UE maintains a set of SL DRX timers for each direction per pair of source L2 ID and destination L2 ID. The SL DRX configuration for a pair of source/destination L2 IDs for a direction may be negotiated between the UEs in the AS layer. For SL DRX configuration of each direction, where one UE is the TX UE and the other is the RX UE: + +- RX UE may send assistance information, which includes its desired SL on-duration timer, SL DRX start offset, SL DRX slot offset, and SL DRX cycle, to the TX UE and the TX UE using mode 2 resource allocation may use it to determine the SL DRX configuration for the RX UE; +- Regardless of whether assistance information is provided or not, the TX UE in RRC\_IDLE/RRC\_INACTIVE/OOC, or in RRC\_CONNECTED and using mode 2 resource allocation, + +determines the SL DRX Configuration for the RX UE. For a TX UE in RRC\_CONNECTED and using mode 1 resource allocation, the SL DRX configuration for the RX UE is determined by the serving gNB of the TX UE; + +- TX UE sends the SL DRX configuration to be used by the RX UE to the RX UE; +- The RX UE may accept or reject the SL DRX configuration. + +When the TX UE is in RRC\_CONNECTED and using mode 1 resource allocation, the TX UE may report the received assistance information or the received SL DRX configuration reject information to its serving gNB supporting SL DRX and sends the SL DRX configuration to the RX UE upon receiving the SL DRX configuration in dedicated RRC signalling from the gNB. When the RX UE is in RRC\_CONNECTED and using mode 1 resource allocation, the RX UE can report the received SL DRX configuration to its serving gNB supporting SL DRX, e.g. for alignment of the Uu and SL DRX configurations. + +SL on-duration timer, SL inactivity-timer, SL HARQ RTT timer, and SL HARQ retransmission timer are supported in unicast. SL HARQ RTT timer and SL HARQ retransmission timer are maintained per SL process at the RX UE. In addition to (pre)configured values for each of these timers, SL HARQ RTT timer value can be derived from the retransmission resource timing when SCI indicates more than one transmission resource. SL HARQ RTT timer can be set to different values to support both HARQ enabled and HARQ disabled transmissions. + +SL DRX MAC CE is introduced for SL DRX operation in unicast only. + +### 16.9.6.3 Groupcast/Broadcast + +For groupcast/broadcast, SL DRX is configured commonly among multiple UEs based on QoS profile and Destination L2 ID. Multiple SL DRX configurations can be supported for each of groupcast/broadcast. + +SL on-duration timer, SL inactivity-timer, SL HARQ RTT and SL HARQ retransmission timers are supported for groupcast. Only SL on-duration timer is supported for broadcast. SL DRX cycle, SL on-duration, and SL inactivity timer (only for groupcast) are configured per QoS profile. The starting offset and slot offset of the SL DRX cycle is determined based on the destination L2 ID. The SL HARQ RTT timer (only for groupcast) and SL HARQ retransmission timer (only for groupcast) are not configured per QoS profile or per destination L2 ID. For groupcast, the RX UE maintains a SL inactivity timer for each destination L2 ID, and selects the largest SL inactivity timer value if multiple SL inactivity timer values associated with different QoS profiles are configured for that L2 ID. For groupcast and broadcast, the RX UE maintains a single SL DRX cycle (selected as the smallest SL DRX cycle of any QoS profile of that L2 ID) and single SL on-duration (selected as the largest SL on-duration of any QoS profile of that L2 ID) for each destination L2 ID when multiple QoS profiles are configured for that L2 ID. + +For groupcast, SL HARQ RTT timer and SL HARQ retransmission timer are maintained per SL process at the RX UE. SL HARQ RTT timer can be set to different values to support both HARQ enabled and HARQ disabled transmissions. + +A default SL DRX configuration, common between groupcast and broadcast, can be used for a QoS profile which is not mapped onto any non-default SL DRX configuration(s). The default SL DRX configuration for groupcast and broadcast can also be used for discovery message in sidelink discovery in clause 16.9.5 and relay discovery messages in clause 16.12.3, for ProSe Direct Link Establishment Request message as specified in TS 24.554 [55], and for Direct Link Establishment Request message as specified in TS 24.587 [53]. + +In-coverage TX and RX UEs in RRC\_IDLE/RRC\_INACTIVE obtain their SL DRX configuration from SIB. UEs (TX or RX) in RRC\_CONNECTED can obtain the SL DRX configuration from SIB, or from dedicated RRC signalling during handover. For the out of coverage case, the SL DRX configuration is obtained from pre-configuration. + +For groupcast, the TX UE restarts its timer corresponding to the SL inactivity timer for the destination L2 ID (used for determining the allowable transmission time) upon reception of new data with the same destination L2 ID. + +TX profile is introduced to ensure compatibility for groupcast and broadcast communication between UEs supporting/not-supporting SL DRX functionality. A TX profile is provided by upper layers to AS layer and identifies one or more sidelink feature group(s). Multiple TX profiles with the support of SL DRX and without the support of SL DRX can be associated to a destination L2 ID. For a given destination L2 ID, all TX and RX UEs should be configured with the same set of TX profile(s). A UE only assumes SL DRX for the given destination L2 ID when all the associated TX profiles correspond to support of SL DRX. A UE assumes no SL DRX for the given destination L2 ID if there is no associated TX profile. An RX UE determines that SL DRX is used if all destination L2 IDs of interest are assumed to support SL DRX. For groupcast, when the UE is in RRC\_CONNECTED and using mode 1 resource allocation, the UE reports each destination L2 ID and associated SL DRX on/off indication to the gNB supporting SL DRX. + +#### 16.9.6.4 Alignment between Uu DRX and SL DRX + +Alignment of Uu DRX and SL DRX for a UE in RRC\_CONNECTED is supported for unicast, groupcast, and broadcast. Alignment of Uu DRX and SL DRX at the same UE is supported. In addition, for mode 1 resource allocation, the alignment of Uu DRX of the TX UE and SL DRX of the RX UE is supported. + +Alignment may comprise of either full overlap or partial overlap in time between Uu DRX and SL DRX. For SL RX UEs in RRC\_CONNECTED, alignment is achieved by the gNB. + +#### 16.9.7 Power Savings Resource Allocation + +The SL UE in Mode 2 can support partial sensing-based resource allocation and random resource selection as power saving resource allocation methods. A SL mode 2 TX resource pool can be (pre)configured to allow full sensing only, partial sensing only, random selection only, or any combination(s) thereof. A UE decides which resource allocation scheme(s) can be used in the AS based on its capability (for a UE in RRC\_IDLE/RRC\_INACTIVE/OOC) and the allowed resource schemes in the resource pool configuration. + +Random resource selection is applicable to both periodic and aperiodic traffic. + +A UE capable for partial sensing can perform periodic-based partial sensing and/or contiguous partial sensing for resource (re)selection. Periodic-based partial sensing can only be performed if periodic resource reservation is configured in the resource pool. In periodic-based partial sensing, the UE monitors slots in periodic sensing occasion(s) for a given resource reservation periodicity. Contiguous partial sensing is performed by a UE capable of partial sensing when resource (re)selection is triggered by a UE in a TX pool configured with partial sensing. In contiguous partial sensing, the UE monitors slots in a contiguous sensing window which occur prior to the selected transmission resource. + +#### 16.9.8 Inter-UE Coordination (IUC) + +The SL UE can support inter-UE coordination (IUC) in Mode 2, whereby a UE sends information about resources to a peer UE, which the peer UE then uses for resource (re)selection. The following schemes of inter-UE coordination are supported: + +- IUC scheme 1, where the IUC information sent from a UE to a peer UE is the preferred or non-preferred resources for the peer UE's transmission, and +- IUC scheme 2, where the IUC information sent from a UE to a peer UE is the presence of expected/potential resource conflict on the resources indicated by the peer UE's SCI. + +In scheme 1, the transmission of IUC information from a UE can be triggered by a condition at this UE, or by an explicit request from a peer UE. The UE determines the set of resources reserved by other UEs or slots where the UE, when it is the intended receiver of the peer UE, does not expect to perform SL reception from the peer UE due to half-duplex operation. The UE uses these resources as the set of non-preferred resources, or excludes these resources to determine a set of preferred resources and sends the preferred/non-preferred resources to the peer UE. Regarding the IUC information received from the UE, the peer UE's resources for resource (re)selection can be based on both the peer UE's sensing results (if available) and the IUC information, or it can be based only on the IUC information. For scheme 1, MAC CE and second-stage SCI or MAC CE only can be used to send IUC information. For IUC information transmission triggered by an explicit request, both the explicit request and the IUC information are transmitted in unicast manner. For IUC information transmission triggered by a condition other than the explicit request, the IUC information indicating preferred resource set is transmitted in unicast manner, and the IUC information indicating non-preferred resource set is transmitted in unicast, groupcast or broadcast manner. + +In scheme 2, a UE determines the expected/potential resource conflict within the resources indicated by a peer UE's SCI as either resources reserved by other UEs and identified by the UE as fully/partially overlapping with the resources indicated by the peer UE's SCI, or as slots where the UE is the intended receiver of the peer UE and does not expect to perform SL reception on those slots due to half-duplex operation. The peer UE uses the conflicting resources to determine the resources to be reselected and exclude the conflicting resources from the reselected resources. For scheme 2, PSFCH is used to send IUC information. + +## 16.9.9 Sidelink in Unlicensed Spectrum (SL-U) + +### 16.9.9.1 Overview + +Sidelink supports operation in unlicensed spectrum for both mode 1 and mode 2. Type1 and Type2 (2A/2B/2C) channel access procedures specified in TS 37.213 [37] are used for NR sidelink operation in a shared channel. + +### 16.9.9.2 Channel Access Priority Classes for Sidelink (SL-CAPC) + +The SL-CAPC of SL radio bearers and SL MAC CEs are either fixed or (pre)configurable as follows: + +- Fixed to the highest priority for all SL-SRBs and SL MAC CEs +- (Pre)configurable per DRB for all SL-DRBs + +When choosing the SL-CAPC for a SL-DRB the network takes into account the PQIs of all QoS flows mapped to that SL DRB. Table 16.9.9-1 below shows which SL-CAPC should be used for which standardized PQI(s), i.e., which SL-CAPC to use for a given QoS flow. For a UE in RRC\_IDLE/RRC\_INACTIVE or OOC, the UE uses the SL-CAPC configured in SIB/Pre-configuration when the QoS flow can be mapped to a non-default SLRB, or when the default SLRB is used for the QoS flow and the SL-CAPC of the default SLRB is configured. + +When the default SLRB is used for the QoS flow and the SL-CAPC of the default SLRB is not configured: + +- if the QoS flow is associated with standardized PQI, the UE derives SL-CAPC for the flow directly from the table below +- if the QoS flow is associated with non-standardized PQI, the UE may select the SL-CAPC of the standardized PQI having the closest PDB. + +The UE then selects the lowest SL-CAPC priority level (highest SL-CAPC value) among the QoS flows to determine the SL-CAPC for the default SLRB. + +**Table 16.9.9-1: Mapping between Channel Access Priority Classes for SL-U and PQI** + +| SL-CAPC | PQI | +|---------|-----------------------------------------------------| +| 1 | 21, 22, 23, 24, 26, 55, 56, 57, 58, 60, 90, 91, 92, | +| 2 | 25 | +| 3 | 59, 61 | +| 4 | - | +| NOTE: | lower SL-CAPC value means higher priority | + +When performing Type 1 LBT for the transmission of a sidelink TB, the SL UE shall select the SL-CAPC as follows: + +- If only SL MAC CE(s) are included in the SL TB, the highest priority SL-CAPC is used; or +- If SCCH SDU(s) are included in the SL TB, the highest priority SL-CAPC is used; or +- The lowest priority SL-CAPC of the SL logical channel(s) with MAC SDU(s) multiplexed in the TB is used otherwise. + +The highest priority SL-CAPC is used for SBCCH SDU transmissions and PSFCH transmissions. + +### 16.9.9.3 Sidelink Specific Consistent LBT Failure + +SL-specific consistent LBT failure detection and recovery procedure is supported for SL-U. When the UE detects SL-specific consistent LBT failure, it performs the actions as specified in TS 38.321 [6]. SL-specific consistent LBT failure detection is per RB-set. + +A SL UE in RRC\_CONNECTED can indicate SL-specific consistent LBT failure to the gNB using a SL MAC CE that indicates the RB set(s) where SL-specific consistent LBT failure was detected. A SL UE using mode 2 resource allocation triggers resource reselection and/or resource pool reselection upon SL-specific consistent LBT failure. In such case, resources in failed RB set(s) are excluded from resource (re)selection until consistent LBT failure on the RB + +set(s) is cancelled based on conditions in TS 38.321 [6]. The UE triggers SL RLF for all PC5-RRC connections when the UE has triggered SL-specific consistent LBT failure in all RB sets. + +#### 16.9.9.4 COT Sharing + +UE to UE COT sharing is supported in NR sidelink operation for SL-U. When performing SL-SSB transmission(s), a responding UE can utilize a COT shared by a COT initiating UE when the responding UE intends to transmit SL-SSB in the shared COT. When performing PSFCH transmissions, a responding UE can utilize a COT shared by a COT initiating UE when at least one of the responding UE's PSFCH transmissions is intended for the COT initiating UE. + +When performing PSSCH/PSCCH transmissions, a responding UE can utilize a COT shared by a COT initiating UE when the responding UE's transmission(s) is intended for the COT initiating UE. In unicast, the destination/source ID of the responding UE's transmission should match the source/destination ID of the initiator UE's transmission for the same unicast link. In groupcast/broadcast, destination ID of the responding UE's transmission should match the initiator's destination ID. In addition, a COT initiating UE may transmit an additional pair of source/destination ID in either unicast, groupcast, or broadcast. In this case, the responding UE can utilize a COT shared by a COT initiating UE if the destination/source (for unicast) or destination (for groupcast/broadcast) of the responding UE transmission match what is carried in the additional ID(s). In all cases, a UE's transmissions in a shared COT should have SL-CAPC value that is equal to or smaller than the SL-CAPC value indicated in the COT sharing information. In order to satisfy the COT sharing requirements, a responding UE may perform an enhanced LCP procedure as specified in 38.321 [6]. When receiving multiple COT sharing indications from different COT initiators, it is up to UE implementation which shared COT is used. + +#### 16.9.9.5 Resource Allocation + +A UE using mode 2 resource allocation may support resource selection enhancements to avoid LBT blocking and increase COT resource utilization. If transmission in slot(s) before a reserved resource is able to share its initiated COT to the reservation, the UE may be (pre)configured to prioritize/select resource(s) in the slot(s) for transmission. To avoid blocking, a UE may avoid selection of a number of consecutive resources (up to UE implementation) before a reserved resource. Furthermore, a UE may avoid selection of a number of consecutive resources (up to UE implementation) after a reserved resource. + +A UE using mode 2 resource allocation supports resource selection for multiple consecutive slot transmission (MCSt). A UE autonomously determines whether to use MCSt, and the number of consecutive slots in an MCSt up to the maximum COT duration for a specific SL-CAPC as defined in TS 37.213 [37]. MCSt can be used for transmission of a single TB or multiple TBs. For each TB transmitted in an MCSt, the UE triggers resource (re)selection only when LBT failure is detected on the resources for the initial transmission and all retransmissions of the TB. When performing LCP procedure for transmission of multiple TBs in an MCSt, a UE may perform an enhanced LCP procedure as specified in TS 38.321 [6] based on the SL-CAPC used for LBT of the first TB. + +#### 16.9.10 Sidelink CA + +Carrier aggregation (CA) in sidelink is supported for mode 2 and in V2X case only. It applies to both in coverage UEs and out of coverage UEs. Each resource pool (pre)configured for sidelink is associated to a single carrier. A UE using mode 2 resource allocation performs carrier (re)selection and may select one or more carriers used for sidelink. + +The carrier(s) that can be used for transmitting data are provided by the V2X layer per QoS flow, and LCP ensures that data from a SLRB is transmitted on a carrier for which all mapped QoS flows are allowed to use the carrier. + +For groupcast and broadcast, when the V2X layer provides multiple carriers in QoS flow to carrier mapping information to the AS, TX profile is used to indicate whether the transmission corresponding to the QoS flow is backward compatible or not. When backward compatibility is needed, the TX UE uses only the legacy carrier without PDCP duplication, or uses PDCP duplication with at least the legacy carrier. + +For groupcast and broadcast, carrier selection is performed at MAC layer, depending on the CBR of the configured carriers and logical channel priority. Carrier (re)selection may be performed when resource (re)selection is triggered, or when there is no SL grant for a sidelink process on any allowed carrier, and is triggered for each sidelink process. In order to avoid frequent switching across different carriers, the UE may keep using a carrier already selected for transmission, if the measured CBR on this carrier is lower than a (pre)configured threshold. For a UE using mode 2 resource allocation, logical channel prioritization is performed for a sidelink resource on a carrier depending on the CBR measured on the carrier and the logical channel priority, as specified in TS 38.321 [6]. For unicast, SL CA related + +capability is exchanged between the TX UE and RX UE, and the TX UE delivers the carrier configuration to the RX UE in PC5-RRC. For unicast, carrier selection and logical channel prioritization is performed similar to groupcast and broadcast among the carriers delivered in the carrier configuration. SL CA for unicast is not applied until the carrier configuration signalling is complete. Carrier (re)selection may be performed and a new carrier configuration is sent to the RX UE when the TX UE detects carrier failure on a specific carrier, as specified in TS 38.321 [6]. + +Sidelink packet duplication is supported for sidelink CA and is performed at PDCP layer. For sidelink packet duplication for transmission, a PDCP PDU is duplicated at the PDCP entity. The duplicated PDCP PDUs of the same PDCP entity are submitted to two different RLC entities and associated to two different sidelink logical channels respectively. The duplicated PDCP PDUs of the same PDCP entity are only allowed to be transmitted on different sidelink carriers. For a SL DRB, sidelink packet duplication is (pre)configured in the bearer configuration. For applicable SL SRBs, whether to use duplication is decided by the TX UE. In unicast, the TX UE sends the duplication configuration to the RX UE in PC5-RRC. + +There are specified logical channel identities which apply to the sidelink logical channel used for sidelink packet duplication exclusively as specified in TS 38.321 [6]. + +## 16.10 Multicast and Broadcast Services + +### 16.10.1 General + +NR system enables resource efficient delivery of multicast/broadcast services (MBS). + +For broadcast communication service, the same service and the same specific content data are provided simultaneously to all UEs in a geographical area (i.e., all UEs in the broadcast service area as defined in TS 23.247 [45] are authorized to receive the data). A broadcast communication service is delivered to the UEs using a broadcast session. A UE can receive a broadcast communication service in RRC\_IDLE, RRC\_INACTIVE and RRC\_CONNECTED state. + +For multicast communication service, the same service and the same specific content data are provided simultaneously to a dedicated set of UEs (i.e., not all UEs in the MBS service area as defined in TS 23.247 [45] are authorized to receive the data). A multicast communication service is delivered to the UEs using a multicast session. A UE can receive a multicast communication service in RRC\_CONNECTED state with mechanisms such as PTP and/or PTM delivery, as defined in clause 16.10.5.4. HARQ feedback/retransmission can be applied to both PTP and PTM transmission. + +### 16.10.2 Network Architecture + +The overall NG-RAN architecture specified in clause 4 applies for NR MBS. MBS multicast can only be supported in MCG side in NE-DC and NR-DC scenarios, i.e., only for MN-terminated MCG MRB. The configuration of MBS broadcast on SCG is not supported for the UE. + +The QoS model for NR MBS can be found in TS 23.247 [45]. + +### 16.10.3 Protocol Architecture + +Figure 16.10.3-1 and 16.10.3-2 depict the downlink Layer 2 architecture for multicast session and broadcast session respectively, where MBS protocol stack comprises the same layer 2 sublayers as described in clause 6 with the following differences: + +- SDAP sublayer provides only the following functionalities: + - Mapping between an MBS QoS flow and an MRB; + - Transfer of user plane data. +- PDCP sublayer provides only the following functionalities: + - Transfer of user plane data; + - Maintenance of PDCP SNs; + +- Header compression and decompression using the ROHC protocol or EHC protocol; +- Reordering and in-order delivery; +- Duplicate discarding. +- For a multicast session, gNB provides one or more of the following multicast MRB configuration(s) to the UE via dedicated RRC signalling: + - Multicast MRB with DL only RLC-UM or bidirectional RLC-UM configuration for PTP transmission; + - Multicast MRB with RLC-AM entity configuration for PTP transmission; + - Multicast MRB with DL only RLC-UM entity for PTM transmission; + - 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; + - 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; + - Multicast MRB with two RLC entities, one RLC-AM entity for PTP transmission and the other DL only RLC-UM entity for PTM transmission. +- For a multicast session, gNB may change the MRB type using RRC signalling. + +![Figure 16.10.3-1: Downlink Layer 2 Architecture for Multicast Session. The diagram illustrates the protocol stack for a Multicast Session and a PDU Session. The Multicast Session stack includes SDAP (QoS flow handling), MRB1, MRB2, and MRB3. MRB1 and MRB2 lead to PDCP (ROHC), which then leads to RLC (Segm.). MRB3 leads to PDCP (ROHC), which leads to RLC (Segm. ARQ). The RLC (Segm.) from MRB1 and MRB2 lead to MTCH, which then leads to Scheduling/ Priority Handling. The RLC (Segm. ARQ) from MRB3 leads to DTCH, which leads to Unicast Scheduling / Priority Handling. Both Scheduling/ Priority Handling and Unicast Scheduling / Priority Handling lead to MAC (Multiplexing), which leads to HARQ, which leads to DL-SCH. The PDU Session stack includes SDAP (QoS flow handling), DRB, PDCP (ROHC, Security), RLC (Segm. ARQ), DTCH, Unicast Scheduling / Priority Handling, MAC (Multiplexing UEn), HARQ, and DL-SCH. The diagram is divided into layers: QoS Flows, Radio Bearers, RLC Channels, Logical Channels, and Transport Channels.](f79cb254efa2e37d7facb055cf90086e_img.jpg) + +Figure 16.10.3-1: Downlink Layer 2 Architecture for Multicast Session. The diagram illustrates the protocol stack for a Multicast Session and a PDU Session. The Multicast Session stack includes SDAP (QoS flow handling), MRB1, MRB2, and MRB3. MRB1 and MRB2 lead to PDCP (ROHC), which then leads to RLC (Segm.). MRB3 leads to PDCP (ROHC), which leads to RLC (Segm. ARQ). The RLC (Segm.) from MRB1 and MRB2 lead to MTCH, which then leads to Scheduling/ Priority Handling. The RLC (Segm. ARQ) from MRB3 leads to DTCH, which leads to Unicast Scheduling / Priority Handling. Both Scheduling/ Priority Handling and Unicast Scheduling / Priority Handling lead to MAC (Multiplexing), which leads to HARQ, which leads to DL-SCH. The PDU Session stack includes SDAP (QoS flow handling), DRB, PDCP (ROHC, Security), RLC (Segm. ARQ), DTCH, Unicast Scheduling / Priority Handling, MAC (Multiplexing UEn), HARQ, and DL-SCH. The diagram is divided into layers: QoS Flows, Radio Bearers, RLC Channels, Logical Channels, and Transport Channels. + +**Figure 16.10.3-1: Downlink Layer 2 Architecture for Multicast Session** + +- For broadcast session, gNB provides the following broadcast MRB configuration to the UE using broadcast RRC signalling: + - Broadcast MRB with one DL only RLC-UM entity for PTM transmission. + +![Figure 16.10.3-2: Downlink Layer 2 Architecture for Broadcast Session. The diagram illustrates the protocol stack for a broadcast session, showing the flow of data from QoS Flows down to Transport Channels (DL-SCH).](b151ddbeea4f514f5f29ce489350c7f7_img.jpg) + +The diagram shows the downlink Layer 2 architecture for a broadcast session. It is organized into five layers, each with a corresponding label on the left and a descriptive label on the right: + +- SDAP**: The top layer, labeled *QoS Flows*. It contains a block labeled "QoS flow handling" which receives four input lines from the top. +- PDCP**: The second layer, labeled *Radio Bearers*. It contains two blocks labeled "ROHC" (Robust Header Compression). +- RLC**: The third layer, labeled *RLC Channels*. It contains three blocks labeled "Segm." (Segmentation), with an ellipsis between the second and third blocks. +- MAC**: The fourth layer, labeled *Logical Channels*. It contains a block labeled "Scheduling / Priority Handling". Below this block, there are two blocks labeled "Multiplexing". The first "Multiplexing" block receives input from the "MCCH" (Master Information Channel) and the first "Segm." block. The second "Multiplexing" block receives input from the second and third "Segm." blocks via "MTCH" (Multicast Traffic Channel) labels. +- Transport Channels**: The bottom layer, labeled *Transport Channels*. It consists of two "DL-SCH" (Downlink Shared Channel) labels at the bottom, which are the output of the "Multiplexing" blocks. + +Figure 16.10.3-2: Downlink Layer 2 Architecture for Broadcast Session. The diagram illustrates the protocol stack for a broadcast session, showing the flow of data from QoS Flows down to Transport Channels (DL-SCH). + +**Figure 16.10.3-2: Downlink Layer 2 Architecture for Broadcast Session** + +## 16.10.4 Group Scheduling + +The following logical channels are used for MBS delivery: + +- MTCH: A PTM downlink channel for transmitting MBS data of either multicast session or broadcast session from the network to the UE; +- DTCH: A PTP channel defined in clause 6.2.2 for transmitting MBS data of a multicast session from the network to the UE; +- MCCH: A PTM downlink channel used for transmitting MBS broadcast or MBS multicast control information associated to one or several MTCH(s) from the network to the UE. Broadcast MCCH and multicast MCCH are independent channels. The multicast MCCH is used only for multicast reception in RRC\_INACTIVE state. + +The following connections between logical channels and transport channels for PTM transmission exist: + +- MCCH can be mapped to DL-SCH; +- MTCH can be mapped to DL-SCH. + +The following depicts the usage of RNTI for PTM transmission: + +- A UE can receive different services using same or different G-RNTIs; +- A UE can receive different services using same or different G-CS-RNTIs. + +## 16.10.5 Multicast Handling + +### 16.10.5.1 Session Management + +There are two delivery modes as specified in TS 23.247 [45]: + +- 5GC Shared MBS traffic delivery; +- 5GC Individual MBS traffic delivery. + +As specified in TS 23.247 [45], if the gNB supports MBS, the network shall use the 5GC Shared MBS traffic delivery in which case an MBS Session Resource context for a multicast session is setup in the gNB when the first UE joins the multicast session. + +For 5GC Shared MBS traffic delivery mode, shared NG-U resources are used to provide MBS user data to the gNB. The gNB initiates the Multicast Distribution Setup procedure towards the 5GC, to allocate shared NG-U resources for a multicast session. In case multiple MBS session areas as specified in TS 23.247 [45] are associated with the same multicast session for location dependent MBS services, multiple NG-U shared resources are established for the same multicast session per MBS Area Session ID served by the gNB. + +A shared NG-U resource applies one of the following transport options: + +- unicast transport; +- multicast transport. + +For 5GC Shared MBS traffic delivery an MBS Session Resource comprises one or several MRBs. If minimisation of data loss is applied for a given MRB, synchronisation of allocation of PDCP COUNT values is applied by either or a combination of the following methods: + +- derivation of the PDCP COUNT values by means of a DL MBS QFI Sequence Number provided on NG-U. Synchronisation in terms of MBS QoS flow to MRB mapping and PDCP SN size of the corresponding MRB among gNBs are achieved by means of network implementation. +- deployment of a Shared NG-U Termination at NG-RAN, shared among gNBs, which comprises a common entity for assignment of PDCP COUNT values. Synchronisation in terms of MBS QoS flow to MRB mapping and PDCP SN size of the corresponding MRB among gNBs may be achieved by means of network implementation. + +If PDCP COUNT values are derived from a DL MBS QFI Sequence Number provided on NG-U and only one QoS Flow is mapped to an MRB, the gNB shall set the PDCP COUNT value of PDCP PDU to the value of the DL MBS QFI Sequence Number provided with the received packet over NG-U. If PDCP COUNT values are derived from a DL MBS QFI Sequence Number provided on NG-U and multiple QoS Flows are mapped to an MRB, the gNB may derive the PDCP COUNT value of the PDCP PDU from the sum of the DL MBS QFI Sequence Numbers of the QoS Flows mapped to this MRB. + +NOTE: Synchronisation of PDCP COUNT values in case user data for MBS QoS flows mapped to the same MRB arrive over NG-U at different gNBs in different order or in case of loss of data over NG-U, and related handling of minimisation of data loss is left to implementation. + +As specified in TS 23.247 [45], the gNB may receive from the 5GC MBS Assistance Information associated with a multicast MBS session for a UE, which assists the gNB in configuring the UE properly. The MBS Assistance Information indicates that the UE is expected to require dedicated resources very frequently. Based on this information, the gNB may decide the RRC state of the UE. The QoS requirements of the multicast session apply regardless of the RRC state within which the UE receives multicast session data. + +### 16.10.5.2 Configuration + +A UE can be configured to receive data of MBS multicast session only in RRC\_CONNECTED state or RRC\_INACTIVE state. To receive the multicast service, the UE needs to perform MBS Session Join procedure as specified in TS 23.247 [45]. It is up to gNB to decide whether the UE receives data of MBS multicast session in RRC\_CONNECTED state or RRC\_INACTIVE state. The gNB moves the UE from RRC\_CONNECTED state to + +RRC\_INACTIVE state via *RRCRelease* message, and moves the UE from RRC\_INACTIVE state to RRC\_CONNECTED state via group notification or UE-specific paging. + +If the UE which joined a multicast session is in RRC\_CONNECTED state and when the multicast session is activated, the gNB may send *RRCReconfiguration* message with relevant MBS configuration for the multicast session to the UE. + +If the gNB configures the UE to receive the MBS multicast session in RRC\_INACTIVE state, the gNB may provide the PTM configuration via *RRCRelease* message for the MBS multicast session as well as information which multicast service(s) can be continued to be received in RRC\_INACTIVE state. The UE does not suspend MRBs of the multicast session indicated to be continued to be received in RRC\_INACTIVE state. Multicast MCCH is used in case a cell supports updating PTM configuration or providing PTM configuration to UEs in RRC\_INACTIVE state moved from other cells. Otherwise, multicast MCCH can be optionally present. + +A notification mechanism is used to announce the change of the multicast MCCH contents due to multicast session modification or session deactivation or due to neighbouring cell information modification. The scheduling information for multicast MCCH reception is provided via *SIB24* and optionally via *RRCRelease* message. + +When there is temporarily no data to be sent to the UEs for a multicast session that is active, the gNB may move the UE to RRC\_INACTIVE state. When an MBS multicast session is deactivated, the gNB may move the UE in RRC\_CONNECTED state to RRC\_IDLE or RRC\_INACTIVE state. For UEs receiving data of MBS multicast session in RRC\_INACTIVE state, the gNB notifies the UE to stop monitoring PDCCH addressed by corresponding G-RNTI via *RRCRelease message* or multicast MCCH when there is temporarily no data to be sent or when the session is deactivated. gNBs supporting MBS use a group notification mechanism to notify the UEs in RRC\_IDLE or RRC\_INACTIVE state when a multicast session has been activated by the CN. gNBs supporting MBS use a group notification mechanism to notify the UEs in RRC\_INACTIVE state when the session is already activated and the gNB has multicast session data to deliver. If the UE receiving data of MBS multicast session in RRC\_INACTIVE state in a cell is notified to stop monitoring PDCCH addressed by G-RNTI for all the joined multicast sessions, the UE does not monitor PDCCH addressed by multicast-MCCH-RNTI until the group notification is received. Upon reception of the group notification, the UEs reconnect to the network or resume the connection and transition to RRC\_CONNECTED state from either RRC\_IDLE state or RRC\_INACTIVE state. Upon reception of the group notification that indicates to allow the multicast reception in RRC\_INACTIVE state, the UE stays in RRC\_INACTIVE state and behaves as specified in TS 38.331 [12]. If the UE is notified by both group notification and the UE-specific paging, the UE follows the UE-specific paging and goes to RRC\_CONNECTED state. + +The group notification is addressed with P-RNTI on PDCCH, and the paging channels are monitored by the UE as described in clause 9.2.5. Paging message for group notification contains MBS session ID which is utilized to page all UEs in RRC\_IDLE and RRC\_INACTIVE states that joined the associated MBS multicast session, i.e., UEs are not paged individually. The UE stops monitoring for group notifications related to a specific multicast session, i.e., stops checking for the MBS session ID in the Paging message, when the UE enters RRC\_CONNECTED state. The UE does not monitor for group notifications for these cases, i.e., once this UE leaves this multicast session or the network requests the UE to leave, or the network releases the multicast session. + +NOTE: The gNB's decision to keep a UE in RRC\_CONNECTED (e.g., to meet latency requirements for mission critical service) or move the UE to RRC\_INACTIVE or RRC\_IDLE (e.g., when there is temporarily no data to be sent to the UE or to address congestion in the cell) may consider 5QI value(s) or other QoS parameters for mission critical and non-mission critical UEs. + +If the UE in RRC\_IDLE state that joined an MBS multicast session is camping on the gNB not supporting MBS, the UE may be notified by CN-initiated paging where CN pages each UE individually due to session activation or data availability, as described in clause 9.2.5. If the UE in RRC\_INACTIVE state that joined MBS multicast session is camping on the gNB not supporting MBS, the UE may be notified individually by RAN-initiated paging due to session activation or data availability, as described in clause 9.2.5. + +### 16.10.5.3 Service Continuity + +#### 16.10.5.3.1 General + +Mobility principles build on existing functionality including functions described in clause 9.2. + +### 16.10.5.3.2 Handover between Multicast supporting cells + +Mobility procedures for multicast reception allow the UE to continue receiving multicast service(s) via PTM or PTP in a new cell after handover. + +During handover preparation phase, the source gNB transfers to the target gNB about the MBS multicast sessions the UE has joined in the UE context information. To support provision of local multicast service with location dependent content as specified in TS 23.247 [45], for each active multicast session, service area information per Area Session ID may be provided to the target gNB. + +The source gNB may propose data forwarding for some MRBs to minimize data loss and may exchange the corresponding MRB PDCP Sequence Number with the target gNB during the handover preparation: + +- The lossless handover for multicast service is supported for the handover between MBS supporting cells if the UE is configured with PTP RLC AM entity in target cell MRB of a UE, regardless of whether the UE is configured with PTP RLC AM entity in the source cell or not. +- In order to support lossless handover for multicast service, the network has to ensure DL PDCP COUNT value synchronization and continuity between the source cell and the target cell. Furthermore, data forwarding from the source gNB to the target gNB and/or PDCP status report provided by a UE for an MRB for multicast session can be used during lossless handover. + +For each multicast session with ongoing user data transmission for which no MBS Session Resources exist at the target gNB, the target gNB triggers the setup of MBS user plane resources towards the 5GC using the NGAP Distribution Setup procedure. If unicast transport is used, the target gNB provides the DL tunnel endpoint to be used to the MB-SMF. If multicast transport is used, the target gNB receives the IP multicast address from the MB-SMF. + +During handover execution, the MBS configuration decided at target gNB is sent to the UE via the source gNB within an RRC container as specified in TS 38.331 [12]. The PDCP entities for multicast MRBs in the UE can either be re-established or remain as it is. When the UE connects to the target gNB, the target gNB sends an indication that it is an MBS-supporting node to the SMF in the Path Switch Request message (Xn handover) or Handover Request Acknowledge message (NG handover). + +Upon successful handover completion, the source gNB may trigger the release of the MBS user plane resources towards the 5GC using the NGAP Distribution Release procedure for any multicast session for which there is no remaining joined UE in the gNB. + +### 16.10.5.3.3 Handover between Multicast-supporting cell and Multicast non-supporting cell + +During an MBS multicast session, at mobility from an MBS-supporting cell to an MBS non-supporting cell, the target gNB sets up PDU Session Resources mapped to the MBS multicast session. The 5GC infers from the absence of an "MBS-support" indication from gNB in the Path Switch Request message (Xn handover) or Handover Request Acknowledge message (NG handover) that MBS multicast data packets delivery has to be switched to 5GC individual MBS traffic delivery as specified in TS 23.247 [45]. If data forwarding is applied, the source gNB infers from the handover preparation response message that the target gNB does not support MBS and changes the QFI(s) in the forwarded packets to the associated PDU Session QFI(s) if respective mapping information is available. The source gNB may be aware that the target gNB is non-MBS supporting already before Handover Preparation. + +For mobility from MBS non-supporting cell to MBS-supporting cell, the existing Xn/NG handover procedures apply. The 5GC infers from the presence of the "MBS-support" indicator from gNB in the Path Switch Request message (Xn handover) or in the Handover Request Acknowledge message (NG handover) that MBS multicast data packets delivery can be switched from 5GC Individual MBS traffic delivery to 5GC Shared MBS traffic delivery. After Xn handover, the SMF triggers switching MBS multicast data packets delivery from 5GC Individual to 5GC Shared MBS traffic delivery by providing MBS Session IDs joined by the UE to the target gNB by means of the PDU Session Resource Modification procedure. For NG handover, the SMF provides the MBS Session IDs joined by the UE to the target gNB by means of NGAP Handover Request. Minimization of data loss and duplication avoidance may be applied by means of identical MBS QFI SNs received over the shared NG-U tunnel against those received over unicast NG-U tunnels or forwarding tunnels. + +Mobility from a multicast-supporting cell to a multicast non-supporting cell can be achieved by switching the MRB to a DRB in the source gNB before a handover. + +NOTE: A UE may be handed over to a target gNB not supporting MBS without prior reconfiguration from MRB to the DRB in the source gNB. In this case, the AS configuration may not be comprehended by the target gNB causing full configuration. + +#### 16.10.5.3.4 MRB reconfiguration + +The gNB may use *RRCREconfiguration* message to configure or reconfigure a multicast MRB, e.g., add/release/modify the MRB's RLC entities as described in clause 16.10.3. In order to minimize the data loss due to MRB reconfiguration, gNB may configure UE to send a PDCP status report during reconfiguration for MRB type change. + +#### 16.10.5.3.5 Service Continuity in RRC\_INACTIVE + +Mobility procedures for multicast reception allow the UE in RRC\_INACTIVE state to continue receiving MBS service(s) when changing cells without resuming RRC connection if the PTM configuration of the new cell can be acquired by the UE from the multicast MCCH after cell reselection. During an active MBS multicast session, the UE is required to resume RRC connection to get the PTM configuration if the PTM configuration is not provided on the multicast MCCH of the new cell. Even if the UE in RRC\_INACTIVE state received indication to stop monitoring PDCCH addressed by G-RNTI for an MBS multicast session in the source cell, the UE acquires MCCH in the reselected cell after cell reselection. + +The gNB may indicate in the multicast MCCH the list of neighbour cells providing the same MBS multicast service(s) for UEs in RRC\_INACTIVE state as provided in the serving cell. This allows the UE, e.g., to resume RRC connection without reading *SIB24* and multicast MCCH of the neighbour cell, if the interested service which is activated is not available to the UE in RRC\_INACTIVE state. + +The gNB may provide an indication on cell PDCP COUNT synchronization for an MBS session with PTM configuration in *RRCRElease* message. If indicated by the gNB, all cells within the RNA are synchronized in terms of PDCP COUNT value to the MRBs of the corresponding MBS service, and the order of MRBs within the list of multicast MRB configuration for the same MBS multicast session in the multicast MCCH message of the last serving cell and (re)selected cell within the RNA should be consistent. Upon reselection to a cell indicated as synchronized in terms of PDCP COUNT value, the UE does not initialize the PDCP state variables. Otherwise, the UE initializes the PDCP state variables as defined in TS 38.323 [8]. + +The UE may be configured with dedicated frequency priorities in *RRCRElease* message which the UE applies during cell reselection while receiving data of MBS multicast session in RRC\_INACTIVE state. + +The UE receiving multicast session(s) in RRC\_INACTIVE state triggers RRC connection resumption if the latest measured RSRP or RSRQ of the serving cell becomes lower than the threshold configured by the network. The threshold can be configured per MBS session via *RRCRElease* message or multicast MCCH. + +#### 16.10.5.4 Reception of MBS Multicast data + +For multicast service, gNB may deliver MBS multicast data packets using the following methods: + +- PTP Transmission: gNB individually delivers separate copies of MBS data packets to each UEs independently, i.e., gNB uses UE-specific PDCCH with CRC scrambled by UE-specific RNTI (e.g., C-RNTI) to schedule UE-specific PDSCH which is scrambled with the same UE-specific RNTI. +- PTM Transmission: gNB delivers a single copy of MBS data packets to a set of UEs, e.g., gNB uses group-common PDCCH with CRC scrambled by group-common RNTI to schedule group-common PDSCH which is scrambled with the same group-common RNTI. + +If a UE is configured with both PTM and PTP transmissions, a gNB dynamically decides whether to deliver multicast data by PTM leg and/or PTP leg for a given UE based on the protocol stack defined in clause 16.10.3, based on information such as MBS Session QoS requirements, number of joined UEs, UE individual feedback on reception quality, and other criteria. The same QoS requirements apply regardless of the decision. + +PTP transmission is not supported for MBS multicast session data reception for UEs in RRC\_INACTIVE state. + +SPS is not supported for MBS multicast session data reception for UEs in RRC\_INACTIVE state. + +### 16.10.5.5 Support of CA + +UE can be configured to receive MBS multicast data either from a PCell or a single SCell at a time. + +### 16.10.5.6 DRX + +The following DRX configurations for PTM/PTP transmission by RRC\_CONNECTED UEs are possible: + +- For PTM transmission, multicast DRX is configured per G-RNTI/G-CS-RNTI which is independent of UE-specific DRX; +- For PTP transmission, UE-specific DRX is reused, i.e., UE-specific DRX is used for both unicast transmission and PTP transmission of MBS multicast. For PTM retransmission via PTP, UE monitors PDCCH scrambled by C-RNTI/CS-RNTI during UE-specific DRX's Active Time. + +The following DRX configuration for PTM transmission by RRC\_INACTIVE UEs is possible: + +- For PTM transmission, multicast DRX is configured per G-RNTI. + +### 16.10.5.7 Physical Layer + +A CFR configured by *RRCReconfiguration* message is defined for multicast scheduling as an 'MBS frequency region' with a number of contiguous PRBs confined within and with the same numerology as the DL BWP, and multicast scheduling may have specific characteristics (e.g., PDCCH, PDSCH and SPS configurations). The CFR for the multicast reception in RRC\_INACTIVE state and the CFR for broadcast can be configured differently. If one CFR is not completely contained within the other CFR, the UE in RRC\_INACTIVE state is not required to receive both broadcast and multicast simultaneously. + +Two HARQ-ACK reporting modes are defined for MBS: + +- For the first HARQ-ACK reporting mode, the UE generates HARQ-ACK information with ACK value when a UE correctly decodes a transport block or detects a DCI format indicating an SPS PDSCH release; otherwise, the UE generates HARQ-ACK information with NACK value. +- For the second HARQ-ACK reporting mode, the UE does not transmit a PUCCH that would include only HARQ-ACK information with ACK values. + +HARQ-ACK feedback for multicast can be enabled or disabled by higher layer configuration per G-RNTI or per G-CS-RNTI and/or indication in the DCI scheduling multicast transmission. + +HARQ feedback is not supported for MBS multicast session data reception for UEs in RRC\_INACTIVE state. + +## 16.10.6 Broadcast Handling + +### 16.10.6.1 Session Management + +For delivery of location dependent contents of a broadcast session, Area Session ID is included in the NGAP broadcast session resource setup procedure associated with MBS service area information and per Area Session ID NG-U tunnels are established. + +The 5GC may also provide information to the NG-RAN node whether the broadcast session is intended to be received by RedCap UEs only, non-RedCap UEs only or both non-RedCap and RedCap UEs. The NG-RAN may take this into account when configuring MBS session resources. + +### 16.10.6.2 Configuration + +MBS broadcast can be received by UEs in RRC\_IDLE, RRC\_INACTIVE and RRC\_CONNECTED state. A UE can receive the MBS configuration for broadcast session (e.g., parameters needed for MTCH reception) via MCCH in RRC\_IDLE, RRC\_INACTIVE and RRC\_CONNECTED state. The parameters needed for the reception of MCCH are provided via System Information. + +The following principles govern the MCCH structure: + +- MCCH provides the list of all broadcast services with ongoing sessions transmitted on MTCH(s) and the associated information for broadcast session includes MBS session ID, associated G-RNTI scheduling information and information about neighbouring cells providing certain service on MTCH(s). MCCH content is transmitted within periodically occurring time domain windows, referred to as MCCH transmission window defined by MCCH repetition period, MCCH window duration and radio frame/slot offset; +- MCCH uses a modification period and MCCH contents are only allowed to be modified at each modification period boundary; a notification mechanism is used to announce the change of MCCH contents due to broadcast session start, modification or stop and due to neighbouring cell information modification; + +NOTE: It is up to UE implementation to use the start and stop times in the USD to determine when to start monitoring the MCCH for the session the UE is interested in. + +- When the UE receives an MCCH change notification, it acquires the updated MCCH in the same MCCH modification period where the change notification is sent. + +### 16.10.6.3 Support of CA + +UE can be configured to receive MBS broadcast data and MCCH either from a PCell or a single SCell at a time. Meanwhile, dedicated RRC signalling is used for providing SIB20 of the SCell i.e., while in RRC\_CONNECTED state, UEs need not acquire broadcast SIB20 directly from the SCells. + +NOTE: The UE may be able to receive MBS broadcast also from a non-serving cell, which is transparent to the network, e.g., it does not require UE capability or MBS Interest Indication to be sent by the UE. + +### 16.10.6.4 DRX + +Via MCCH, the UE can be configured with a PTM DRX configuration for G-RNTI reception. One PTM DRX configuration can be mapped to more than one G-RNTI. + +### 16.10.6.5 Service Continuity + +#### 16.10.6.5.0 General + +Mobility principles build on existing functionality including functions described in clause 9.2. + +NR MBS supports MBS frequency layer prioritization for MBS broadcast sessions. The gNBs may be configured with the MBS FSA ID(s) supported by each of their cells. The gNBs may exchange this information with their neighbours within Xn Setup messages and subsequent Xn Configuration Update messages to help with frequency layer prioritization. + +#### 16.10.6.5.1 Service Continuity in RRC\_IDLE or RRC\_INACTIVE + +Mobility procedures for MBS reception allow the UE to start or continue receiving MBS service(s) when changing cells. The gNB may indicate in the MCCH the list of neighbour cells providing the same MBS broadcast service(s) as provided in the serving cell. This allows the UE, e.g., to request unicast reception of the service before moving to a cell not providing the MBS broadcast service(s) using PTM transmission. To avoid the need to read MBS broadcast related system information and potentially MCCH on neighbour frequencies, the UE is made aware of which frequency is providing which MBS broadcast services via PTM, through User Service Description (USD), as defined in TS 26.346 [46], or the combination of the following: + +- USD; +- SIB21, as defined in clause 7.3.1. + +NOTE: UE can request unicast reception of the service after moving to a cell not providing the MBS broadcast service(s) using PTM transmission. + +In RRC\_IDLE and RRC\_INACTIVE, the UE applies the normal cell reselection rules with the following modifications: + +- the UE which is receiving or interested to receive MBS broadcast service(s) via PTM and can only receive these MBS broadcast service(s) via PTM while camping on the frequency providing these MBS broadcast service(s) is allowed to make this frequency highest priority when the conditions described in TS 38.304 [10] are met; +- when the MBS broadcast service(s) which the UE is interested in are no longer available (after the end of the session) or the UE is no longer interested in receiving the service(s), the UE no longer prioritises the frequency providing these MBS broadcast service(s). + +#### 16.10.6.5.2 Service Continuity in RRC\_CONNECTED + +To ensure service continuity of MBS broadcast, the UE in RRC\_CONNECTED state may send MBS Interest Indication to the gNB, consisting of the following information: + +- List of MBS frequencies UE is receiving or interested to receive, sorted in decreasing order of interest; +- Priority between the reception of all listed MBS frequencies and the reception of any unicast bearer and multicast MRB; +- List of MBS broadcast services the UE is receiving or interested to receive, in case SIB20 is provided for PCell or SCell. + +MBS Interest Indication information reporting can be implicitly enabled/disabled by the presence of SIB21. + +The gNB may use this information, together with the information about the UE's capabilities (e.g., supported band combinations), when providing an RRC configuration and/or downlink assignments to the UE or to release DRBs/multicast MRBs, to allow the UE to receive the MBS services the UE is interested in. MBS Interest Indication information can be exchanged between source gNB and target gNB during handover. + +#### 16.10.6.5A Reception of MBS Broadcast data + +For broadcast service, gNB may deliver Broadcast MBS data packets using the following method: + +- PTM Transmission: gNB delivers a single copy of MBS data packets to a set of UEs, e.g., gNB uses group-common PDCCH with CRC scrambled by group-common RNTI to schedule group-common PDSCH which is scrambled with the same group-common RNTI. + +#### 16.10.6.6 Physical Layer + +A CFR configured by SIB is defined for broadcast scheduling as an 'MBS frequency region' with a number of contiguous PRBs with a bandwidth equal to or larger than CORESET0, with the same numerology as CORESET0, and broadcast scheduling may have specific characteristics (e.g., PDCCH and PDSCH configurations). + +The maximum number of MIMO layers is one for MBS broadcast scheduling. RB-level rate matching, and RE-level rate matching around LTE-CRS configured by higher layer signalling are supported for MCCH and MTCH. Slot-level repetition is supported for MTCH. + +HARQ-ACK feedback is not supported for MBS broadcast. + +Only dynamic scheduling is supported for MBS broadcast. + +#### 16.10.6.7 Shared processing for MBS broadcast and unicast reception + +If the UE in RRC\_CONNECTED state is receiving or interested to receive an MBS broadcast service from a non-serving cell as described in TS 38.306 [11], the UE may use MBS Interest Indication message to inform the serving gNB about the parameters used for the non-serving cell broadcast reception as described in TS 38.331 [12]. The gNB may enable the sending of the MBS Interest Indication by including an indication in SIB1. The UE may indicate to the serving cell the UE capability for receiving MBS broadcast service from a non-serving cell. It is up to gNB implementation to consider the MBS Interest Indication and the UE capability for receiving MBS broadcast service from a non-serving cell, if indicated, when scheduling the UE. + +In case the UE only reports the frequency for broadcast service reception from the non-serving cell in MBS Interest Indication due to some parameters (e.g., SCS, bandwidth) not being available, the UE may transmit updated MBS + +Interest Indication once the parameters are available to the UE. It is up to network implementation on how to enable the UE to acquire these parameters from the non-serving cell. + +### 16.10.6.8 Support of Resource Sharing across multiple Broadcast MBS sessions in RAN Sharing Scenario + +NGAP supports resource sharing efficient scheme for broadcast delivery in RAN sharing. Such scheme enables the gNB to identify broadcast MBS sessions from different PLMNs providing identical content. The identification is based on information provided by the involved 5GCs in the Associated Session ID as specified in TS 23.247 [45]. + +If in the MBS Broadcast Setup Request message an Associated Session ID is received from a 5GC participating in RAN sharing, the gNB uses it to determine whether MBS Session resources can be shared with a broadcast MBS session(s) associated with the same Associated Session ID requested from another 5GC participating in RAN sharing. + +The identification of MBS Broadcast Sessions providing identical content may also be based on implementation specific configuration as specified in TS 23.247 [45]. + +The gNB applying this resource efficiency scheme: + +- may decide whether NG-U resources are established towards all involved 5GCs or only some of them; +- resolves different QoS requirements or different S-NSSAIs received from the participating 5GCs in an implementation specific way. + +The gNB may also trigger the NGAP Broadcast Session Transport procedure towards one 5GC participating in RAN sharing to set up NG-U resources to maintain NG-U connectivity as specified in TS 23.247 [45]. + +## 16.11 Minimization of Service Interruption + +In case of a disaster, a radio access network can experience outage, which can result in that UEs belonging to the network experience service interruptions. For this scenario, another network not affected by the disaster, which during non-disaster situations is considered by the UEs as a forbidden network, can allow roaming of the UEs belonging to the network experiencing such disaster service interruptions. Such roaming is referred to as disaster roaming. This is further described in clause 5.40 of TS 23.501 [3] and 3.10 of TS 23.122 [47]. + +To allow such disaster roaming, a cell can broadcast a list of PLMNs with disaster conditions for which disaster roaming is offered. Disaster roaming service is provided only for the area that covers the area with disaster condition. + +Further, to be able to control the load that disaster roaming UEs put on a cell, the cell can broadcast access control parameters applicable specifically for disaster roaming UEs. Access attempts of disaster roaming UEs are based on Access Identity 3. The network can for example set the access control parameters for Access Identity 3 so that access attempts of disaster roaming UEs are more likely to be barred compared to non-disaster roaming UEs. + +## 16.12 Sidelink Relay + +### 16.12.1 General + +Sidelink relay is introduced to support 5G ProSe UE-to-Network Relay (U2N Relay) function (specified in TS 23.304 [48]) to provide connectivity to the network for U2N Remote UE(s). Both L2 and L3 U2N Relay architectures are supported. The L3 U2N Relay architecture is transparent to the serving NG-RAN of the U2N Relay UE, except for controlling sidelink resources. The detailed architecture and procedures for L3 U2N Relay can be found in TS 23.304 [48]. + +A U2N Relay UE shall be in RRC\_CONNECTED to perform relaying of unicast data. + +For L2 U2N Relay operation, the following RRC state combinations are supported: + +- Both L2 U2N Relay UE and L2 U2N Remote UE shall be in RRC\_CONNECTED to perform transmission/reception of relayed unicast data; and + +- The L2 U2N Relay UE can be in RRC\_IDLE, RRC\_INACTIVE or RRC\_CONNECTED as long as all the L2 U2N Remote UE(s) that are connected to the L2 U2N Relay UE are either in RRC\_INACTIVE or in RRC\_IDLE. + +A single unicast link is established between one L2 U2N Relay UE and one L2 U2N Remote UE. The traffic to the NG-RAN of L2 U2N Remote UE via a given L2 U2N Relay UE and the traffic of the L2 U2N Relay UE shall be separated in different Uu RLC channels. + +For L2 U2N Relay, the L2 U2N Remote UE can only be configured to use resource allocation mode 2 (as specified in 5.7.2 and 16.9.3.1) for data to be relayed. + +Sidelink relay is introduced to support 5G ProSe UE-to-UE Relay (U2U Relay) function (specified in TS 23.304 [48]) to provide connectivity between U2U Remote UEs. Both L2 and L3 U2U Relay architectures are supported. The L3 U2U Relay architecture is transparent to the AS layer of the U2U Relay UE. The detailed architecture and procedures for L3 U2U Relay can be found in TS 23.304 [48]. + +A U2U Relay UE is to support the U2U Relay function as specified in TS 23.304 [48] to provide coverage extension of the sidelink transmissions between two U2U Remote UEs. For the coverage extension, the U2U Remote UE can communicate with the peer U2U Remote UE(s) which are not reachable within the sidelink coverage. + +The U2U Relay UE and U2U Remote UE can be in any RRC state. The U2U Relay UE and the U2U Remote UEs can be in the coverage of different cells or out-of-coverage. Both sidelink resource allocation modes, i.e., mode 1 and mode 2 are supported for the U2U Relay UE and U2U Remote UEs. For U2U Relay, NR sidelink is supported between U2U Relay UE and U2U Remote UEs. After NR sidelink establishment between U2U Relay UE and U2U Remote UEs, end-to-end PC5 unicast link connection establishment is performed between U2U Remote UEs. Only unicast is supported between U2U Relay UE and U2U Remote UEs. + +## 16.12.2 Protocol Architecture + +### 16.12.2.1 L2 UE-to-Network Relay + +The protocol stacks for the user plane and control plane of L2 U2N Relay architecture are illustrated in Figure 16.12.2.1-1 and Figure 16.12.2.1-2. The SRAP sublayer is placed above the RLC sublayer for both CP and UP at both PC5 interface and Uu interface. The Uu SDAP, PDCP and RRC are terminated between L2 U2N Remote UE and gNB, while SRAP, RLC, MAC and PHY are terminated in each hop (i.e., the link between L2 U2N Remote UE and the L2 U2N Relay UE and the link between L2 U2N Relay UE and the gNB). + +For L2 U2N Relay, the SRAP sublayer over PC5 hop is only for the purpose of bearer mapping. The SRAP sublayer is not present over PC5 hop for relaying the L2 U2N Remote UE's message on BCCH and PCCH. For L2 U2N Remote UE's message on SRB0, the SRAP header is not present over PC5 hop, but the SRAP header is present over Uu hop for both DL and UL. + +![User plane protocol stack for L2 UE-to-Network Relay diagram showing Remote UE, UE-to-Network Relay UE, and gNB layers.](69981c87c5b93c90e9012f6dabce4215_img.jpg) + +This diagram illustrates the user plane protocol stack for an L2 UE-to-Network Relay. It consists of three main entities: Remote UE, UE-to-Network Relay UE, and gNB. The Remote UE contains layers Uu-SDAP, Uu-PDCP, PC5-SRAP, PC5-RLC, PC5-MAC, and PC5-PHY. The UE-to-Network Relay UE contains two parallel stacks: one for PC5 (PC5-SRAP, PC5-RLC, PC5-MAC, PC5-PHY) and one for Uu (Uu-SRAP, Uu-RLC, Uu-MAC, Uu-PHY). The gNB contains layers Uu-SDAP, Uu-PDCP, Uu-SRAP, Uu-RLC, Uu-MAC, and Uu-PHY. Connections are shown between the Remote UE and the Relay UE via PC5 channels, and between the Relay UE and the gNB via Uu channels. Specifically, the PC5 Relay RLC Channel connects the Remote UE's PC5-RLC to the Relay UE's PC5-RLC, and the Uu Relay RLC Channel connects the Relay UE's Uu-RLC to the gNB's Uu-RLC. + +User plane protocol stack for L2 UE-to-Network Relay diagram showing Remote UE, UE-to-Network Relay UE, and gNB layers. + +Figure 16.12.2.1-1: User plane protocol stack for L2 UE-to-Network Relay + +![Control plane protocol stack for L2 UE-to-Network Relay diagram showing Remote UE, UE-to-Network Relay UE, and gNB layers.](e33485d4301404e5a43a61e4cfb96fcc_img.jpg) + +This diagram illustrates the control plane protocol stack for an L2 UE-to-Network Relay. It consists of three main entities: Remote UE, UE-to-Network Relay UE, and gNB. The Remote UE contains layers Uu-RRC, Uu-PDCP, PC5-SRAP, PC5-RLC, PC5-MAC, and PC5-PHY. The UE-to-Network Relay UE contains two parallel stacks: one for PC5 (PC5-SRAP, PC5-RLC, PC5-MAC, PC5-PHY) and one for Uu (Uu-SRAP, Uu-RLC, Uu-MAC, Uu-PHY). The gNB contains layers Uu-RRC, Uu-PDCP, Uu-SRAP, Uu-RLC, Uu-MAC, and Uu-PHY. Connections are shown between the Remote UE and the Relay UE via PC5 channels, and between the Relay UE and the gNB via Uu channels. Specifically, the PC5 Relay RLC Channel connects the Remote UE's PC5-RLC to the Relay UE's PC5-RLC, and the Uu Relay RLC Channel connects the Relay UE's Uu-RLC to the gNB's Uu-RLC. + +Control plane protocol stack for L2 UE-to-Network Relay diagram showing Remote UE, UE-to-Network Relay UE, and gNB layers. + +Figure 16.12.2.1-2: Control plane protocol stack for L2 UE-to-Network Relay + +For L2 U2N Relay, for uplink: + +- The Uu SRAP sublayer performs UL bearer mapping between end-to-end Uu Radio Bearers of L2 U2N remote UE (identified for the purposes of this mapping by the local Remote UE ID and an associated bearer ID) and egress Uu Relay RLC channels over the L2 U2N Relay UE Uu interface. For uplink relaying traffic, the different end-to-end Uu Radio Bearers (SRBs or DRBs) of the same L2 U2N Remote UE and/or different L2 U2N Remote UEs can be multiplexed over the same egress Uu Relay RLC channel; +- The Uu SRAP sublayer supports L2 U2N Remote UE identification for the UL traffic. The identity information of L2 U2N Remote UE end-to-end Uu Radio Bearer and a local Remote UE ID are included in the Uu SRAP header at UL in order for gNB to correlate the received packets for the specific PDCP entity associated with the right end-to-end Uu Radio Bearer of the L2 U2N Remote UE; +- The PC5 SRAP sublayer at the L2 U2N Remote UE supports UL bearer mapping between L2 U2N Remote UE end-to-end Uu Radio Bearers and egress PC5 Relay RLC channels. + +For L2 U2N Relay, for downlink: + +- The Uu SRAP sublayer performs DL bearer mapping at gNB to map end-to-end Uu Radio Bearer (SRB, DRB) of L2 U2N Remote UE (identified for the purposes of this mapping by the local Remote UE ID and an associated bearer ID) into Uu Relay RLC channel. The Uu SRAP sublayer performs DL bearer mapping and data multiplexing between multiple end-to-end Radio Bearers (SRBs or DRBs) of a L2 U2N Remote UE and/or different L2 U2N Remote UEs and one Uu Relay RLC channel over the L2 U2N Relay UE Uu interface; +- The Uu SRAP sublayer supports L2 U2N Remote UE identification for DL traffic. The identity information of L2 U2N Remote UE end-to-end Uu Radio Bearer and a local Remote UE ID are included into the Uu SRAP header by the gNB at DL for the L2 U2N Relay UE to identify the corresponding end-to-end Uu Radio Bearer(s) of L2 U2N Remote UE; +- The PC5 SRAP sublayer at the L2 U2N Relay UE performs DL bearer mapping between end-to-end Uu Radio Bearers of L2 U2N remote UE and egress PC5 Relay RLC channels; +- The PC5 SRAP sublayer at the L2 U2N Remote UE correlates the received packets with the right PDCP entity associated with the given end-to-end Uu Radio Bearer of the L2 U2N Remote UE based on the identity information included in the PC5 SRAP header. + +A local Remote UE ID is included in both PC5 SRAP header and Uu SRAP header. L2 U2N Relay UE is configured by the gNB with the local Remote UE ID(s) to be used in SRAP header. L2 U2N Remote UE obtains the local Remote ID from the gNB via Uu RRC messages including *RRCSsetup*, *RRRCReconfiguration*, *RRRCResume* and *RRRCReestablishment*. + +The end-to-end DRB(s) or end-to-end SRB(s), except SRB0, of L2 U2N Remote UE can be multiplexed to the PC5 Relay RLC channels and Uu Relay RLC channels in both PC5 hop and Uu hop, but an end-to-end DRB and an end-to-end SRB can neither be mapped into the same PC5 Relay RLC channel nor be mapped into the same Uu Relay RLC channel. + +It is the gNB responsibility to avoid collision on the usage of local Remote UE ID. The gNB can update the local Remote UE ID by sending the updated local Remote UE ID via *RRRCReconfiguration* message. The serving gNB can perform local Remote UE ID update independent of the PC5 unicast link L2 ID update procedure. + +## 16.12.2.2 L2 UE-to-UE Relay + +The protocol stacks for the user plane and the control plane of the L2 U2U Relay architecture are illustrated in Figure 16.12.2.2-1 and Figure 16.12.2.2-2. The SRAP sublayer is placed above the RLC sublayer for both CP and UP at both PC5 interfaces. The sidelink SDAP, PDCP and RRC are terminated between two L2 U2U Remote UEs (i.e., end-to-end), while SRAP, RLC, MAC and PHY are terminated in each hop of PC5 link. + +![Figure 16.12.2.2-1: User plane protocol stack for L2 UE-to-UE Relay. The diagram shows three main components: a Remote UE (left), a Relay UE (middle), and a gNB (right). The Remote UE contains a stack of SDAP, PDCP, and RRC layers. The Relay UE contains a stack of SRAP, RLC, MAC, and PHY layers. The gNB contains a stack of SDAP, PDCP, and RRC layers. Arrows indicate the flow of data: from the Remote UE's RRC layer, through the Relay UE's SRAP, RLC, MAC, and PHY layers, to the gNB's SDAP layer. The Relay UE's SDAP layer is also shown, indicating data flow to the gNB. The diagram illustrates that the SDAP, PDCP, and RRC layers are terminated at the Remote UE and the gNB, while the SRAP, RLC, MAC, and PHY layers are terminated at the Relay UE.](e9ada921dc81492dd0cd7c59d7d20ae9_img.jpg) + +Figure 16.12.2.2-1: User plane protocol stack for L2 UE-to-UE Relay. The diagram shows three main components: a Remote UE (left), a Relay UE (middle), and a gNB (right). The Remote UE contains a stack of SDAP, PDCP, and RRC layers. The Relay UE contains a stack of SRAP, RLC, MAC, and PHY layers. The gNB contains a stack of SDAP, PDCP, and RRC layers. Arrows indicate the flow of data: from the Remote UE's RRC layer, through the Relay UE's SRAP, RLC, MAC, and PHY layers, to the gNB's SDAP layer. The Relay UE's SDAP layer is also shown, indicating data flow to the gNB. The diagram illustrates that the SDAP, PDCP, and RRC layers are terminated at the Remote UE and the gNB, while the SRAP, RLC, MAC, and PHY layers are terminated at the Relay UE. + +Figure 16.12.2.2-1: User plane protocol stack for L2 UE-to-UE Relay + +![Figure 16.12.2.2-2: Control plane protocol stack for L2 UE-to-UE Relay. The diagram shows three vertical protocol stacks. The left stack (L2 U2U Remote UE) has a black top section, followed by a white section with a grey box, and then a white section with four stacked boxes. The middle stack (L2 U2U Relay UE) has a black top section, followed by a white section with a grey box, and then a white section with four stacked boxes. The right stack (L2 U2U Remote UE) has a black top section, followed by a white section with a grey box, and then a white section with four stacked boxes. Horizontal lines connect the boxes across the stacks, representing protocol layers and their interactions.](7c19fc92dc74a74ec346d46bc39a3946_img.jpg) + +Figure 16.12.2.2-2: Control plane protocol stack for L2 UE-to-UE Relay. The diagram shows three vertical protocol stacks. The left stack (L2 U2U Remote UE) has a black top section, followed by a white section with a grey box, and then a white section with four stacked boxes. The middle stack (L2 U2U Relay UE) has a black top section, followed by a white section with a grey box, and then a white section with four stacked boxes. The right stack (L2 U2U Remote UE) has a black top section, followed by a white section with a grey box, and then a white section with four stacked boxes. Horizontal lines connect the boxes across the stacks, representing protocol layers and their interactions. + +**Figure 16.12.2.2-2: Control plane protocol stack for L2 UE-to-UE Relay** + +For L2 UE-to-UE Relay, the SRAP sublayer at L2 U2U Remote UE: + +- The SRAP sublayer at L2 U2U Remote UE performs bearer mapping between end-to-end PC5 Radio Bearers (SL-SRBs or SL-DRBs) of the L2 U2U Remote UE and at each hop of PC5 Relay RLC Channel between the L2 U2U Remote UE and the L2 U2U Relay UE. +- For the traffic transmitted from an L2 U2U Remote UE to an L2 U2U Relay UE, the different end-to-end PC5 Radio Bearers (SL-SRBs or SL-DRBs) towards the same peer L2 U2U Remote UE and/or different peer L2 U2U Remote UEs can be multiplexed to the same PC5 Relay RLC channel, which is between the L2 U2U Remote UE(s) and the L2 U2U Relay UE. +- For the traffic received at L2 U2U Remote UE, the same PC5 Relay RLC channel from one L2 U2U Relay UE can be de-multiplexed to the different end-to-end PC5 Radio Bearers (SL-SRBs or SL-DRBs) of the same peer L2 U2U Remote UE and/or different peer L2 U2U Remote UEs. +- The SRAP sublayer at L2 U2U Remote UE supports identification of the peer L2 U2U Remote UE and itself. The local IDs are assigned by L2 U2U Relay UE to both L2 U2U Remote UEs for identification. For the two local IDs, one of them identifies L2 U2U Remote UE and the other identifies the peer L2 U2U Remote UE. The local ID of the peer L2 U2U Remote UE and the local ID of L2 U2U Remote UE are delivered by L2 U2U Relay UE to the L2 U2U Remote UEs along with the corresponding L2 ID of the peer L2 U2U Remote UE. The identity information of the end-to-end PC5 Radio Bearer and two local IDs are included in the SRAP header in order for the peer L2 U2U Remote UE to correlate the received packets for the specific PDCP entity associated with the right end-to-end PC5 Radio Bearer of the L2 U2U Remote UEs. + +For L2 UE-to-UE Relay, the SRAP sublayer at L2 U2U Relay UE: + +- The SRAP sublayer at L2 U2U Relay UE determines the egress PC5 Relay RLC Channel based on the mapping of the end-to-end PC5 Radio Bearer and egress PC5 Relay RLC Channel for a particular pair between the L2 U2U Remote UE and the peer L2 U2U Remote UE. +- For the ingress traffic received from an/multiple L2 U2U Remote UE(s) at L2 U2U Relay UE, the different end-to-end PC5 Radio Bearers (SL-SRBs or SL-DRBs) of the same L2 U2U Remote UE and/or the same/different end-to-end PC5 Radio Bearers (SL-SRBs or SL-DRBs) of L2 U2U Remote UEs can be multiplexed to the same egress PC5 Relay RLC channel, which is in between the L2 U2U Relay UE and the peer L2 U2U Remote UE. + +### 16.12.3 Relay Discovery + +Model A and Model B discovery models as defined in TS 23.304 [48] are supported for U2N/U2U Relay discovery. The protocol stack used for discovery is illustrated in Figure 16.12.3-1. + +![Figure 16.12.3-1: Protocol Stack of Discovery Message for UE-to-Network/UE-to-UE Relay. The diagram shows two protocol stacks, Remote UE and Relay UE, connected by horizontal arrows representing data flow. Both stacks consist of five layers: Discovery, PDCP, RLC, MAC, and PHY. The Discovery layer is at the top, followed by PDCP, RLC, MAC, and PHY at the bottom. Arrows connect corresponding layers between the Remote UE and the Relay UE, indicating bidirectional communication at each layer.](1750e325061d2206b5af0af175793d79_img.jpg) + +Figure 16.12.3-1: Protocol Stack of Discovery Message for UE-to-Network/UE-to-UE Relay. The diagram shows two protocol stacks, Remote UE and Relay UE, connected by horizontal arrows representing data flow. Both stacks consist of five layers: Discovery, PDCP, RLC, MAC, and PHY. The Discovery layer is at the top, followed by PDCP, RLC, MAC, and PHY at the bottom. Arrows connect corresponding layers between the Remote UE and the Relay UE, indicating bidirectional communication at each layer. + +**Figure 16.12.3-1: Protocol Stack of Discovery Message for UE-to-Network/UE-to-UE Relay** + +The U2N Remote UE can perform Relay discovery message (i.e., as specified in TS 23.304 [48]) transmission and may monitor the sidelink for Relay discovery message while in RRC\_IDLE, RRC\_INACTIVE or RRC\_CONNECTED. The network may broadcast or configure via dedicated RRC signalling a Uu RSRP threshold, which is used by the U2N Remote UE to determine if it can transmit Relay discovery messages to U2N Relay UE(s). + +The U2N Relay UE can perform Relay discovery message (i.e., as specified in TS 23.304 [48]) transmission and may monitor the sidelink for Relay discovery message while in RRC\_IDLE, RRC\_INACTIVE or RRC\_CONNECTED. The network may broadcast or configure via dedicated RRC signalling a maximum Uu RSRP threshold, a minimum Uu RSRP threshold, or both, which are used by the U2N Relay UE to determine if it can transmit Relay discovery messages to U2N Remote UE(s). + +The U2U Remote UE and U2U Relay UE can perform Relay discovery message transmission or DCR message with integrated discovery transmission and may monitor for Relay discovery message or DCR message with integrated discovery while in coverage (i.e. RRC\_IDLE, RRC\_INACTIVE, or RRC\_CONNECTED) or out-of-coverage. + +The network may provide the Relay discovery configuration using broadcast or dedicated signalling. In addition, the U2N/U2U Remote UE and L3 U2N/U2U Relay UE may use pre-configuration for Relay discovery. + +The resource pool(s) used for NR sidelink communication can be used for Relay discovery or the network may configure resource pool(s) dedicated for Relay discovery. Resource pool(s) dedicated for Relay discovery can be configured simultaneously with resource pool(s) for NR sidelink communication in system information, dedicated signalling and/or pre-configuration. Whether dedicated resource pool(s) for Relay discovery are configured is based on network implementation. If resource pool(s) dedicated for Relay discovery are configured, only those resource pool(s) dedicated for Relay discovery shall be used for Relay discovery. If only resource pool(s) for NR sidelink communication are configured, all the configured resource pool(s) can be used for Relay discovery and NR sidelink communication. Only communication resource pool is used for the DCR/DCA message with integrated discovery. + +For U2N Remote UE (including both in-coverage and out of coverage cases) that has been connected to the network via a U2N Relay UE, only resource allocation mode 2 is used for Relay discovery message transmission. + +For in-coverage U2N Relay UE, and for both in-coverage and out of coverage U2N Remote UEs, NR sidelink resource allocation principles are applied for Relay discovery message transmission. + +For U2U Remote UE and U2U Relay UE, NR sidelink resource allocation principles, both mode 1 and mode 2, can be applied for Relay discovery message transmission. + +The sidelink power control for the transmission of Relay discovery messages is same as for NR sidelink communication. + +No ciphering or integrity protection in PDCP layer is applied for the Relay discovery messages. + +The U2N/U2U Remote UE and U2N/U2U Relay UE can determine from SIB12 whether the gNB supports Relay discovery, or Non-Relay discovery, or both. + +## 16.12.4 Relay Selection/Reselection + +The U2N Remote UE performs radio measurements at PC5 interface and uses them for U2N Relay selection and reselection along with higher layer criteria, as specified in TS 23.304 [48]. When there is no unicast PC5 connection + +between the U2N Relay UE and the U2N Remote UE, the U2N Remote UE uses SD-RSRP measurements to evaluate whether PC5 link quality towards a U2N Relay UE satisfies relay selection criterion. + +For relay reselection, U2N Remote UE uses SL-RSRP measurements towards the serving U2N Relay UE for relay reselection trigger evaluation when there is data transmission from U2N Relay UE to U2N Remote UE, and it is left to UE implementation whether to use SL-RSRP or SD-RSRP for relay reselection trigger evaluation in case of no data transmission from U2N Relay UE to U2N Remote UE. + +A U2N Relay UE is considered suitable by a U2N Remote UE in terms of radio criteria if the PC5 link quality measured by U2N Remote UE towards the U2N Relay UE exceeds configured threshold (pre-configured or provided by gNB). The U2N Remote UE searches for suitable U2N Relay UE candidates that meet all AS layer and higher layer criteria (see TS 23.304 [48]). If there are multiple such suitable U2N Relay UEs, it is up to U2N Remote UE implementation to choose one U2N Relay UE among them. For L2 U2N Relay (re)selection, the PLMN ID and cell ID can be used as additional AS criteria. + +The U2N Remote UE triggers U2N Relay selection in following cases: + +- Direct Uu signal strength of current serving cell of the U2N Remote UE is below a configured signal strength threshold; +- Indicated by upper layer of the U2N Remote UE. + +The U2N Remote UE may trigger U2N Relay reselection in following cases: + +- PC5 signal strength of current U2N Relay UE is below a (pre)configured signal strength threshold; +- Cell reselection, handover, Uu RLF, or Uu RRC connection establishment/resume failure has been indicated by U2N Relay UE via PC5-RRC signalling; +- When U2N Remote UE receives a PC5-S link release message from U2N Relay UE; +- When U2N Remote UE detects PC5 RLF; +- Indicated by upper layer. + +For L2 U2N Remote UEs in RRC\_IDLE or RRC\_INACTIVE and L3 U2N Remote UEs, the cell (re)selection procedure and relay (re)selection procedure run independently. If both suitable cells and suitable U2N Relay UEs are available, it is up to the U2N Remote UE implementation to select either a cell or a U2N Relay UE. A L3 U2N Remote UE may select a cell and a L3 U2N Relay UE simultaneously and this is up to implementation of L3 U2N Remote UE. + +For both L2 and L3 U2N Relay UEs in RRC\_IDLE or RRC\_INACTIVE, the PC5-RRC message(s) are used to inform their connected U2N Remote UE(s) when U2N Relay UEs select a new cell. The PC5-RRC message(s) are also used to inform their connected L2 or L3 U2N Remote UE(s) when L2 or L3 U2N Relay UE performs handover, detects Uu RLF, or its Uu RRC connection establishment/resume fails. Upon reception of the PC5 RRC message for notification, it is up to U2N Remote UE implementation whether to release or keep the unicast PC5 link. If U2N Remote UE decides to release the unicast PC5 link, it triggers the PC5 release procedure and may perform cell or relay reselection. + +The U2U Remote UE performs radio measurements (i.e., SD-RSRP and/or SL-RSRP) at PC5 interface and uses them for U2U Relay selection and reselection along with higher layer criteria, as specified in TS 23.304 [48]. + +For relay selection, U2U Remote UE uses SL-RSRP measurements towards the peer U2U Remote UE for relay selection trigger evaluation when valid SL-RSRP measurements are available. For relay reselection, U2U Remote UE uses SL-RSRP measurement towards the U2U Relay UE for relay reselection trigger evaluation when there is data transmission from U2U Relay UE to U2U Remote UE. It is left to U2U Remote UE implementation whether to use SL-RSRP or SD-RSRP for relay selection or reselection trigger evaluation in case of no data transmission. The thresholds for SD-RSRP and SL-RSRP can be configured separately for the trigger evaluation of U2U relay selection or reselection. The same threshold value(s) are applied for all the discovery models including DCR with integrated discovery. The same threshold value(s) are applied for relay selection and relay reselection. + +The U2U Remote UE may trigger U2U Relay selection in the following cases: + +- When the SL-RSRP or SD-RSRP between U2U Remote UEs is below a (pre)configured signal strength threshold; +- When U2U Remote UE receives an indication to trigger U2U relay selection from the upper layer of the UE. + +The U2U Remote UE may trigger U2U Relay reselection in the following cases: + +- When the SL-RSRP or SD-RSRP of the current U2U Relay UE is below a (pre)configured signal strength threshold; +- When U2U Remote UE receives an indication from the upper layer due to detecting PC5 RLF; +- When L2 U2U Remote UE receives an indication from the upper layer due to receiving the PC5 RLF indication from the L2 U2U Relay UE; +- When U2U Remote UE receives a PC5-S link release message from U2U Relay UE; +- When U2U Remote UE receives an indication to trigger U2U relay reselection from the upper layer of the UE. + +For the discovery model A, the U2U Relay UE should announce via discovery announcement message only the neighbour U2U Remote UE(s) for which the SD-RSRP/SL-RSRP between the U2U Relay and the neighbour U2U Remote UE(s) is above a configured threshold. Upon discovery message reception, U2U Remote UE considers a U2U Relay UE as a candidate U2U Relay UE if the SD-RSRP towards the U2U Relay UE is above a configured threshold and the upper layer criteria are met. + +For the discovery model B, when the U2U Relay UE receives the discovery solicitation message from U2U Remote UE, the U2U Relay UE forwards the discovery solicitation message only if the SD-RSRP between the U2U Relay UE and the U2U Remote UE is above a threshold. After the peer U2U Remote UE receives a discovery solicitation message from the U2U Relay UE, the peer U2U Remote UE transmits the discovery response message only if the SD-RSRP between the peer U2U Remote UE and the U2U Relay UE is above a configured threshold. Upon discovery response message reception forwarded by the U2U Relay UE, the U2U Remote UE considers a U2U Relay UE as a candidate U2U Relay UE if the SD-RSRP towards the U2U Relay UE is above a configured threshold and the upper layer criteria are met. + +For the DCR message with integrated discovery, when the U2U Relay UE receives the DCR message with integrated discovery from U2U Remote UE, the U2U Relay UE forwards the DCR message with integrated discovery only if the SL-RSRP between the U2U Relay UE and the U2U Remote UE is above a threshold. Upon receiving DCR message with integrated discovery from one or multiple U2U Relay UEs, the peer U2U Remote UE should consider candidate U2U Relay UEs towards which the SL-RSRP is above a configured SD-RSRP threshold (not the SL-RSRP, as broadcast is used) to respond and that satisfy upper-layer criteria, and select a U2U Relay UE among them. + +## 16.12.5 Control plane procedures for L2 U2N Relay + +### 16.12.5.1 RRC Connection Management + +The L2 U2N Remote UE needs to establish its own PDU sessions/DRBs with the network before user plane data transmission. + +The NR sidelink PC5 unicast link establishment procedures can be used to setup a secure unicast link between L2 U2N Remote UE and L2 U2N Relay UE before L2 U2N Remote UE establishes a Uu RRC connection with the network via L2 U2N Relay UE. + +The establishment of Uu SRB1/SRB2 and DRB of the L2 U2N Remote UE is subject to Uu configuration procedures for L2 UE-to-Network Relay. + +The following high level connection establishment procedure in Figure 16.12.5.1-1 applies to a L2 U2N Relay and L2 U2N Remote UE: + +![Sequence diagram illustrating the procedure for L2 U2N Remote UE connection establishment. The diagram shows three participants: Remote UE, Relay UE, and gNB. The sequence of messages is: 1. Discovery (Remote UE to Relay UE), 1. PC5 Connection Establishment (Remote UE to Relay UE), 2. RRCSetupRequest (Remote UE to gNB via Relay UE), 2. RRCSetup (gNB to Remote UE via Relay UE), 3. Prepare PC5 and Uu Relay RLC channel for SRB1 (gNB to Relay UE), 4. RRCSetupComplete (Remote UE to gNB via Relay UE), 5. SecurityModeCommand (gNB to Remote UE via Relay UE), 5. SecurityModeComplete (Remote UE to gNB via Relay UE), 6. RRCReconfiguration (gNB to Remote UE via Relay UE), 6. RRCReconfigurationComplete (Remote UE to gNB via Relay UE), 6. Prepare PC5 and Uu Relay RLC channel for SRB2/DRB (gNB to Relay UE).](b1a6ab9f3d33d6e8d64173bfa595b763_img.jpg) + +``` + +sequenceDiagram + participant Remote UE + participant Relay UE + participant gNB + Note left of Remote UE: 1. Discovery + Note left of Remote UE: 1. PC5 Connection Establishment + Remote UE->>gNB: 2. RRCSetupRequest + gNB-->>Remote UE: 2. RRCSetup + Note right of gNB: 3. Prepare PC5 and Uu Relay RLC channel for SRB1 + Remote UE->>gNB: 4. RRCSetupComplete + gNB-->>Remote UE: 5. SecurityModeCommand + Remote UE-->>gNB: 5. SecurityModeComplete + gNB-->>Remote UE: 6. RRCReconfiguration + Remote UE-->>gNB: 6. RRCReconfigurationComplete + Note right of gNB: 6. Prepare PC5 and Uu Relay RLC channel for SRB2/DRB + +``` + +Sequence diagram illustrating the procedure for L2 U2N Remote UE connection establishment. The diagram shows three participants: Remote UE, Relay UE, and gNB. The sequence of messages is: 1. Discovery (Remote UE to Relay UE), 1. PC5 Connection Establishment (Remote UE to Relay UE), 2. RRCSetupRequest (Remote UE to gNB via Relay UE), 2. RRCSetup (gNB to Remote UE via Relay UE), 3. Prepare PC5 and Uu Relay RLC channel for SRB1 (gNB to Relay UE), 4. RRCSetupComplete (Remote UE to gNB via Relay UE), 5. SecurityModeCommand (gNB to Remote UE via Relay UE), 5. SecurityModeComplete (Remote UE to gNB via Relay UE), 6. RRCReconfiguration (gNB to Remote UE via Relay UE), 6. RRCReconfigurationComplete (Remote UE to gNB via Relay UE), 6. Prepare PC5 and Uu Relay RLC channel for SRB2/DRB (gNB to Relay UE). + +**Figure 16.12.5.1-1: Procedure for L2 U2N Remote UE connection establishment** + +1. The L2 U2N Remote and L2 U2N Relay UE perform discovery procedure, and establish a PC5-RRC connection using the NR sidelink PC5 unicast link establishment procedure. +2. The L2 U2N Remote UE sends the first RRC message (i.e., *RRCSetupRequest*) for its connection establishment with gNB via the L2 U2N Relay UE, using a specified PC5 Relay RLC channel configuration. The L2 U2N Relay UE sends the *SidelinkUEInformationNR* message to request for the dedicated configurations required to support the relay operation for the L2 U2N Remote UE. If the L2 U2N Relay UE is not in *RRC\_CONNECTED*, it needs to do its own Uu RRC connection establishment upon reception of a message on the specified PC5 Relay RLC channel. After L2 U2N Relay UE's RRC connection establishment procedure and sending the *SidelinkUEInformationNR* message, gNB configures SRB0 relaying Uu Relay RLC channel to the U2N Relay UE. The gNB responds with an *RRCSetup* message to L2 U2N Remote UE. The *RRCSetup* message is sent to the L2 U2N Remote UE using SRB0 relaying Uu Relay RLC channel over Uu and a specified PC5 Relay RLC channel over PC5. + +NOTE 1: Void. + +3. The gNB and L2 U2N Relay UE perform relaying channel setup procedure over Uu. According to the configuration from gNB, the L2 U2N Relay/Remote UE establishes a PC5 Relay RLC channel for relaying of SRB1 towards the L2 U2N Remote/Relay UE over PC5. +4. The *RRCSetupComplete* message is sent by the L2 U2N Remote UE to the gNB via the L2 U2N Relay UE using SRB1 relaying channel over PC5 and SRB1 relaying channel configured to the L2 U2N Relay UE over Uu. Then the L2 U2N Remote UE is as in *RRC\_CONNECTED* with the gNB. +5. The L2 U2N Remote UE and gNB establish security following the Uu security mode procedure and the security messages are forwarded through the L2 U2N Relay UE. +6. The gNB sends an *RRCReconfiguration* message to the L2 U2N Remote UE via the L2 U2N Relay UE, to setup the end-to-end SRB2/DRBs of the L2 U2N Remote UE. The L2 U2N Remote UE sends an *RRCReconfigurationComplete* message to the gNB via the L2 U2N Relay UE as a response. In addition, the gNB may configure additional Uu Relay RLC channels between the gNB and L2 U2N Relay UE, and PC5 Relay RLC channels between L2 U2N Relay UE and L2 U2N Remote UE for the relaying traffic. + +### 16.12.5.2 Radio Link Failure + +The L2 U2N Remote UE in RRC\_CONNECTED suspends Uu RLM (as described in clause 9.2.7) when connected to the gNB via a L2 U2N Relay UE. + +The L2 U2N Relay UE declares Uu Radio Link Failure (RLF) following the same criteria as described in clause 9.2.7. + +After Uu RLF is declared, the L2 U2N Relay UE takes the following action on top of the actions described in clause 9.2.7: + +- a PC5-RRC message can be used for sending an indication to its connected L2 U2N Remote UE(s), which may trigger RRC connection re-establishment for L2 U2N Remote UE; or +- indicating to upper layer to trigger PC5 unicast link release. + +Upon detecting PC5 RLF, the L2 U2N Remote UE may trigger RRC connection re-establishment. + +### 16.12.5.3 RRC Connection Re-establishment + +The L2 U2N Remote UE may perform the following actions during the RRC connection re-establishment procedure: + +- If only suitable cell(s) are available, the L2 U2N Remote UE initiates RRC re-establishment procedure towards a suitable cell; +- If only suitable L2 U2N Relay UE(s) are available, the L2 U2N Remote UE initiates RRC re-establishment procedure towards a suitable relay UE's serving cell via selected suitable L2 U2N Relay; +- If both a suitable cell and a suitable relay are available, the L2 U2N Remote UE can select either one to initiate RRC re-establishment procedure based on implementation. + +### 16.12.5.4 RRC Connection Resume + +The RRC connection resume procedure described in clause 9.2.2 is applied to L2 U2N Remote UE. + +### 16.12.5.5 System Information + +The in-coverage L2 U2N Remote UE is allowed to acquire any necessary SIB(s) over Uu interface irrespective of its PC5 connection to L2 U2N Relay UE. The L2 U2N Remote UE can also receive the system information from the L2 U2N Relay UE after PC5 connection establishment with L2 U2N Relay UE. + +The L2 U2N Remote UE in RRC\_CONNECTED can use the on-demand SIB framework as specified in TS 38.331 [12] to request the SIB(s) via L2 U2N Relay UE. The L2 U2N Remote UE in RRC\_IDLE or RRC\_INACTIVE can inform L2 U2N Relay UE of its requested SIB type(s) via PC5-RRC message. Then, L2 U2N Relay UE triggers on-demand SI/SIB acquisition procedure as specified in TS 38.331 [12] according to its own RRC state (if needed) and sends the acquired SI(s)/SIB(s) to L2 U2N Remote UE via PC5-RRC message. + +Any SIB that the RRC\_IDLE or RRC\_INACTIVE L2 U2N Remote UE has a requirement to use (e.g., for relay purpose) can be requested by the L2 U2N Remote UE (from the L2 U2N Relay UE or the network). For SIBs that have been requested by the L2 U2N Remote UE from the L2 U2N Relay UE, the L2 U2N Relay UE forwards them again in case of any update for requested SIB(s). In case of RRC\_CONNECTED L2 U2N Remote UE(s), it is the responsibility of the network to send updated SIB(s) to L2 U2N Remote UE(s) when they are updated. The L2 U2N Remote UE de-configures SI request with L2 U2N Relay UE when entering into RRC\_CONNECTED state. + +For SIB1 forwarding, for L2 U2N Remote UE, both request-based delivery (i.e., SIB1 request by the U2N Remote UE) and unsolicited forwarding are supported by L2 U2N Relay UE, of which the usage is left to L2 U2N Relay UE implementation. If SIB1 changes, for L2 U2N Remote UE in RRC\_IDLE or RRC\_INACTIVE, the L2 U2N Relay UE always forwards SIB1. + +For the L2 U2N Remote UE in RRC\_IDLE or RRC\_INACTIVE, the short message over Uu interface is not forwarded by the L2 U2N Relay UE to the L2 U2N Remote UE. The L2 U2N Relay UE can forward PWS SIBs to its connected L2 U2N Remote UE(s). + +RAN sharing is supported for L2 U2N Relay UE. In particular, the L2 U2N Relay UE may forward, via discovery message, cell access related information before the establishment of a PC5-RRC connection. + +### 16.12.5.6 Paging + +When both L2 U2N Relay UE and L2 U2N Remote UE are in RRC IDLE or RRC INACTIVE, the L2 U2N Relay UE monitors paging occasions of its connected L2 U2N Remote UE(s). When a L2 U2N Relay UE needs to monitor paging for a L2 U2N Remote UE, the L2 U2N Relay UE should monitor all POs of the L2 U2N Remote UE. + +When L2 U2N Relay UE is in RRC\_CONNECTED and L2 U2N Remote UE(s) is in RRC\_IDLE or RRC\_INACTIVE, there are two options for paging delivery: + +- The L2 U2N Relay UE monitors POs of its connected L2 U2N Remote UE(s) if the active DL BWP of the L2 U2N Relay UE is configured with common search space including paging search space; +- The delivery of the L2 U2N Remote UE's paging can be performed through a dedicated RRC message from the gNB to the L2 U2N Relay UE. The dedicated RRC message for delivering L2 U2N Remote UE paging to the RRC\_CONNECTED L2 U2N Relay UE may contain one or more Remote UE IDs (5G-S-TMSI or I-RNTI). + +It is up to network implementation to decide which of the above two options to use. The L2 U2N Relay UE in RRC\_CONNECTED, if configured with paging search space, can determine whether to monitor POs for a L2 U2N Remote UE based on the indication within the PC5-RRC signalling received from the L2 U2N Remote UE. + +The L2 U2N Remote UE in RRC\_IDLE provides 5G-S-TMSI and UE specific DRX cycle (if configured by upper layer) to the L2 U2N Relay UE for requesting to perform PO monitoring. The L2 U2N Remote UE in RRC\_INACTIVE provides the minimum value of two UE specific DRX cycles (if configured respectively by upper layer and NG-RAN), 5G-S-TMSI and I-RNTI to the L2 U2N Relay UE for PO monitoring. The L2 U2N Relay UE in RRC\_CONNECTED can notify the L2 U2N Remote UE information (i.e. 5G-S-TMSI/I-RNTI) to the gNB via the *SidelinkUEInformationNR* message for paging delivery purpose. The L2 U2N Relay UE receives paging messages to check the 5G-S-TMSI/I-RNTI and sends relevant paging record to the L2 U2N Remote UE accordingly. + +The L2 U2N Relay UE uses unicast signalling to send paging to the L2 U2N Remote UE via PC5. + +### 16.12.5.7 Access Control + +The L2 U2N Remote UE performs unified access control as defined in TS 38.331 [12]. The L2 U2N Relay UE does not perform UAC for L2 U2N Remote UE's data. + +### 16.12.5.8 Mobility Registration Update and RAN Area Update + +The L2 U2N Remote UE performs Mobility Registration Update/RNAU based on the L2 U2N Relay UE's serving cell when it is connected with the L2 U2N Relay UE. A L2 U2N Remote UE in RRC\_IDLE or RRC\_INACTIVE initiates Mobility Registration Update/RNAU procedure if the serving cell changes (due to cell change by the L2 U2N Relay UE) and the new serving cell is outside of the L2 U2N Remote UE's configured RNA/TA. + +## 16.12.6 Service Continuity for L2 U2N relay + +### 16.12.6.0 General + +The service continuity procedure is applicable only for the mobility cases of path switch from indirect to direct path, and from direct to indirect path when the L2 U2N Remote UE and L2 U2N Relay UE belong to the same gNB or different gNB. This procedure is also applicable for the mobility cases of path switch from indirect to indirect path when the two L2 U2N Relay UEs belong to the same gNB or different gNBs. For inter-gNB path switching, the source gNB decides to trigger path switching and the path switch type, i.e. direct or indirect path. + +### 16.12.6.1 Switching from indirect to direct path + +For service continuity of L2 U2N Relay, the following procedure is used, in case of L2 U2N Remote UE switching from indirect to direct path under the same gNB: + +![Sequence diagram illustrating the procedure for L2 U2N Remote UE intra-gNB switching from indirect to direct path. The diagram shows interactions between Remote UE, Relay UE, and gNB. The sequence starts with 0. UL/DL data (dashed line). Step 1: Measurement configuration and reporting (solid line from gNB to Remote UE via Relay UE). Step 2: Decision of switching to a direct cell (internal gNB process). Step 3: RRC Reconfiguration message (solid line from gNB to Remote UE via Relay UE). Step 4: RA to gNB (solid line from Remote UE to gNB). Step 5: RRC Reconfiguration Complete message (solid line from Remote UE to gNB). Step 6: RRC Reconfiguration (solid line from gNB to Relay UE). Step 7: PC5 link release (solid line from Remote UE to Relay UE). Step 8: UL/DL data (dashed line).](29178b001cb4c04e0c5ab60662ce5d80_img.jpg) + +``` + +sequenceDiagram + participant Remote UE + participant Relay UE + participant gNB + + Note left of Remote UE: 0. UL/DL data + Remote UE-->>gNB: 1. Measurement configuration and reporting + Note right of gNB: 2. Decision of switching to a direct cell + gNB-->>Remote UE: 3. RRC Reconfiguration message + Remote UE-->>gNB: 4. RA to gNB + Remote UE-->>gNB: 5. RRC Reconfiguration Complete message + gNB-->>Relay UE: 6. RRC Reconfiguration + Remote UE-->>Relay UE: 7. PC5 link release + Note right of Remote UE: 8. UL/DL data + +``` + +Sequence diagram illustrating the procedure for L2 U2N Remote UE intra-gNB switching from indirect to direct path. The diagram shows interactions between Remote UE, Relay UE, and gNB. The sequence starts with 0. UL/DL data (dashed line). Step 1: Measurement configuration and reporting (solid line from gNB to Remote UE via Relay UE). Step 2: Decision of switching to a direct cell (internal gNB process). Step 3: RRC Reconfiguration message (solid line from gNB to Remote UE via Relay UE). Step 4: RA to gNB (solid line from Remote UE to gNB). Step 5: RRC Reconfiguration Complete message (solid line from Remote UE to gNB). Step 6: RRC Reconfiguration (solid line from gNB to Relay UE). Step 7: PC5 link release (solid line from Remote UE to Relay UE). Step 8: UL/DL data (dashed line). + +**Figure 16.12.6.1-1: Procedure for L2 U2N Remote UE intra-gNB switching from indirect to direct path** + +1. The Uu measurement configuration and measurement report signalling procedures are performed to evaluate both relay link measurement and Uu link measurement. The measurement results from L2 U2N Remote UE are reported when configured measurement reporting criteria are met. The sidelink relay measurement report shall include at least L2 U2N Relay UE's source L2 ID, serving cell ID (i.e., NCGI/NCI), and sidelink measurement quantity result. The sidelink measurement quantity can be SL-RSRP of the serving L2 U2N Relay UE, and if SL-RSRP is not available, SD-RSRP is used. +2. The gNB decides to switch the L2 U2N Remote UE onto direct Uu path. +3. The gNB sends the *RRCReconfiguration* message to the L2 U2N Remote UE. The L2 U2N Remote UE stops User Plane and Control Plane transmission via the L2 U2N Relay UE after reception of the *RRCReconfiguration* message with the path switch configuration. +4. The L2 U2N Remote UE synchronizes with the gNB and performs Random Access. +5. The UE (i.e., L2 U2N Remote UE in previous steps) sends the *RRCReconfigurationComplete* message to the gNB via the direct path, using the configuration provided in the *RRCReconfiguration* message. From this step, the UE (i.e., L2 U2N Remote UE in previous steps) uses the RRC connection via the direct path to the gNB. +6. The gNB sends the *RRCReconfiguration* message to the L2 U2N Relay UE to reconfigure the connection between the L2 U2N Relay UE and the gNB. The *RRCReconfiguration* message to the L2 U2N Relay UE can be sent any time after step 3 based on gNB implementation (e.g., to release Uu Relay RLC Channel and PC5 Relay RLC channel configuration for relaying, and bearer mapping configuration related to the L2 U2N Remote UE). +7. Either L2 U2N Relay UE or L2 U2N Remote UE's AS layer indicates upper layers to release PC5 unicast link after receiving the *RRCReconfiguration* message from the gNB. The timing to execute link release is up to UE implementation. +8. The data path is switched from indirect path to direct path between the UE (i.e., previous L2 U2N Remote UE) and the gNB. The PDCP re-establishment or PDCP data recovery in uplink is performed by the UE (i.e., previous L2 U2N Remote UE) for lossless delivery during path switch if gNB configures it. + +NOTE 1: Step 8 can be executed any time after step 4. Step 8 is independent of step 6 and step 7. + +For service continuity of L2 U2N Relay, the following procedure is used, in case of L2 U2N Remote UE switching from indirect to direct path under another gNB: + +![Sequence diagram illustrating the procedure for L2 U2N Remote UE inter-gNB switching from indirect to direct path. The diagram shows interactions between Remote UE, Relay UE, Source gNB, and Target gNB. The process starts with UL/DL data exchange, followed by measurement configuration and reporting. The Source gNB makes a decision to switch to another gNB, then sends a HANDOVER REQUEST to the Target gNB. The Target gNB performs admission control and sends a HANDOVER REQUEST ACKNOWLEDGE. The Source gNB then sends an RRCReconfiguration message to the Remote UE. The Source gNB also sends an SN STATUS TRANSFER and RA to target gNB to the Target gNB. The Remote UE sends an RRCReconfigurationComplete message. The Source gNB sends a UE CONTEXT RELEASE to the Target gNB. Finally, the Remote UE sends an RRC Reconfiguration message to the Relay UE, and the PC5 link is released.](573293af67ee571aef04bf725fcefbe5_img.jpg) + +``` + +sequenceDiagram + participant Remote UE + participant Relay UE + participant Source gNB + participant Target gNB + + Note left of Remote UE: 0. UL/DL data + Remote UE->>Source gNB: 1. Measurement configuration and reporting + Note right of Source gNB: 2. Decision of switching to another gNB + Source gNB->>Target gNB: 3. HANDOVER REQUEST + Note right of Target gNB: 4. Admission control + Target gNB->>Source gNB: 5. HANDOVER REQUEST ACKNOWLEDGE + Source gNB->>Remote UE: 6. RRCReconfiguration + Source gNB->>Target gNB: 7. SN STATUS TRANSFER + Source gNB->>Target gNB: 8. RA to target gNB + Remote UE->>Target gNB: 9. RRCReconfigurationComplete + Source gNB->>Target gNB: 10. UE CONTEXT RELEASE + Remote UE->>Relay UE: 11. RRC Reconfiguration + Remote UE->>Relay UE: 12. PC5 link release + +``` + +Sequence diagram illustrating the procedure for L2 U2N Remote UE inter-gNB switching from indirect to direct path. The diagram shows interactions between Remote UE, Relay UE, Source gNB, and Target gNB. The process starts with UL/DL data exchange, followed by measurement configuration and reporting. The Source gNB makes a decision to switch to another gNB, then sends a HANDOVER REQUEST to the Target gNB. The Target gNB performs admission control and sends a HANDOVER REQUEST ACKNOWLEDGE. The Source gNB then sends an RRCReconfiguration message to the Remote UE. The Source gNB also sends an SN STATUS TRANSFER and RA to target gNB to the Target gNB. The Remote UE sends an RRCReconfigurationComplete message. The Source gNB sends a UE CONTEXT RELEASE to the Target gNB. Finally, the Remote UE sends an RRC Reconfiguration message to the Relay UE, and the PC5 link is released. + +**Figure 16.12.6.1-2: Procedure for L2 U2N Remote UE inter-gNB switching from indirect to direct path** + +1. The Uu measurement configuration is configured by the source gNB, and measurement report signalling procedures are performed by the L2 U2N Remote UE to evaluate both relay link measurement and Uu link measurement. The measurement results from L2 U2N Remote UE are reported when configured measurement reporting criteria are met. The sidelink relay measurement report shall include at least L2 U2N Relay UE's source L2 ID, serving cell ID (i.e., NCGI/NCI), and sidelink measurement quantity result. The sidelink measurement quantity can be SL-RSRP of the serving L2 U2N Relay UE, and if SL-RSRP is not available, SD-RSRP is used. + 2. The source gNB decides to trigger path switch for the L2 U2N Remote UE, onto direct path. + 3. The source gNB sends the HANDOVER REQUEST message to the target gNB with necessary information to prepare the handover at the target side. +- NOTE 2: In order to support the DL lossless handover for the L2 U2N Remote UE, the source gNB may not discard the DL data even though the delivery of the data has been acknowledged by the L2 U2N Relay UE based on the gNB implementation. Then, the source gNB forwards the buffered DL data to the target gNB during the data forwarding procedure. +4. Admission Control may be performed by the target gNB. + 5. The target gNB sends the HANDOVER REQUEST ACKNOWLEDGE message to the source gNB, which contains new RRC configuration for the L2 U2N Remote UE. + 6. The source gNB triggers the path switch by sending an *RRCReconfiguration* message to the L2 U2N Remote UE, containing at least cell ID and the information required to access the target cell. The L2 U2N Remote UE stops User Plane and Control Plane transmission via the L2 U2N Relay UE after reception of the *RRCReconfiguration* message. + 7. The source gNB sends the SN STATUS TRANSFER message to the target gNB to convey the uplink PDCP SN receiver status and the downlink PDCP SN transmitter status of the L2 U2N Remote UE's DRBs for which PDCP status preservation applies (i.e. for RLC AM). + 8. The L2 U2N Remote UE synchronizes with the target gNB and performs Random Access. + +9. The L2 U2N Remote UE sends *RRCReconfigurationComplete* message to target gNB via the direct path. +10. The target gNB sends the UE CONTEXT RELEASE message to inform the source gNB about the success of the path switch. +11. The source gNB sends *RRCReconfiguration* message to the L2 U2N Relay UE to reconfigure the connection between the L2 U2N Relay UE and the source gNB. The *RRCReconfiguration* message to the L2 U2N Relay UE can be sent any time after step 6 based on source gNB implementation (e.g., to release Uu Relay RLC channel and PC5 Relay RLC channel configuration for relaying, and bearer mapping configuration related to the L2 U2N Remote UE). +12. Either L2 U2N Relay UE or L2 U2N Remote UE's AS layer indicates upper layer to release PC5 unicast link after receiving the *RRCReconfiguration* message from the source gNB. The timing to execute link release is up to UE implementation. + +### 16.12.6.2 Switching from direct to indirect path + +The gNB can select a L2 U2N Relay UE in any RRC state i.e., RRC\_IDLE, RRC\_INACTIVE, or RRC\_CONNECTED, as a target L2 U2N Relay UE for direct to indirect path switch. + +For service continuity of L2 U2N Remote UE, the following procedure is used, in case of the L2 U2N Remote UE switching from direct to indirect path under the same gNB via a L2 U2N Relay UE in RRC\_CONNECTED: + +![Sequence diagram illustrating the procedure for L2 U2N Remote UE intra-gNB switching from direct to indirect path via a L2 U2N Relay UE in RRC_CONNECTED. The diagram shows three participants: Remote UE, Relay UE, and gNB. The sequence of messages is: 0. UL/DL data (dashed line between Remote UE and gNB); 1. Measurement configuration and reporting (solid line from gNB to Remote UE); 2. Decision of switching to a target relay UE (internal gNB process); 3. RRC Reconfiguration message (solid line from gNB to Relay UE); 4. PC5 connection establishment (solid line from Relay UE to Remote UE); 5. RRC Reconfiguration Complete message (solid line from Remote UE to gNB); 6. UL/DL data (dashed line between Remote UE and gNB, with a circle at the Relay UE indicating the path switch).](1f980b98800c29272e0e5ba2f6db4b98_img.jpg) + +Sequence diagram illustrating the procedure for L2 U2N Remote UE intra-gNB switching from direct to indirect path via a L2 U2N Relay UE in RRC\_CONNECTED. The diagram shows three participants: Remote UE, Relay UE, and gNB. The sequence of messages is: 0. UL/DL data (dashed line between Remote UE and gNB); 1. Measurement configuration and reporting (solid line from gNB to Remote UE); 2. Decision of switching to a target relay UE (internal gNB process); 3. RRC Reconfiguration message (solid line from gNB to Relay UE); 4. PC5 connection establishment (solid line from Relay UE to Remote UE); 5. RRC Reconfiguration Complete message (solid line from Remote UE to gNB); 6. UL/DL data (dashed line between Remote UE and gNB, with a circle at the Relay UE indicating the path switch). + +**Figure 16.12.6.2-1: Procedure for L2 U2N Remote UE intra-gNB switching from direct to indirect path via a L2 U2N Relay UE in RRC\_CONNECTED** + +1. The L2 U2N Remote UE reports one or multiple candidate L2 U2N Relay UE(s) and Uu measurements, after it measures/discovers the candidate L2 U2N Relay UE(s): + - The L2 U2N Remote UE filters the appropriate L2 U2N Relay UE(s) according to relay selection criteria before reporting. The L2 U2N Remote UE shall report only the L2 U2N Relay UE candidate(s) that fulfil the higher layer criteria; + - The reporting includes at least a L2 U2N Relay UE ID, a L2 U2N Relay UE's serving cell ID, and a sidelink measurement quantity information. SD-RSRP is used as sidelink measurement quantity. +2. The gNB decides to switch the L2 U2N Remote UE to a target L2 U2N Relay UE. Then the gNB sends an *RRCReconfiguration* message to the target L2 U2N Relay UE, which includes at least the L2 U2N Remote UE's local ID and L2 ID, Uu Relay RLC channel and PC5 Relay RLC channel configuration for relaying, and bearer mapping configuration. + +3. The gNB sends the *RRCReconfiguration* message to the L2 U2N Remote UE. The *RRCReconfiguration* message includes at least the L2 U2N Relay UE ID, Remote UE's local ID, PC5 Relay RLC channel configuration for relay traffic and the associated end-to-end Uu radio bearer(s). The L2 U2N Remote UE stops User Plane and Control Plane transmission over the direct path after reception of the *RRCReconfiguration* message from the gNB. +4. The L2 U2N Remote UE establishes PC5-RRC connection with target L2 U2N Relay UE. +5. The L2 U2N Remote UE completes the path switch procedure by sending the *RRCReconfigurationComplete* message to the gNB via the L2 U2N Relay UE. +6. The data path is switched from direct path to indirect path between the L2 U2N Remote UE and the gNB. + +In case the selected L2 U2N Relay UE for direct to indirect path switch is in RRC\_IDLE or RRC\_INACTIVE, after receiving the path switch command, the L2 U2N Remote UE establishes a PC5 link with the L2 U2N Relay UE and sends the *RRCReconfigurationComplete* message via the L2 U2N Relay UE, which triggers the L2 U2N Relay UE to enter RRC\_CONNECTED state. The procedure for L2 U2N Remote UE switching to indirect path in Figure 16.12.6.2-1 can be also applied for the case that the selected L2 U2N Relay UE for direct to indirect path switch is in RRC\_IDLE or RRC\_INACTIVE with the exception that the *RRCReconfiguration* message is sent from the gNB to the L2 U2N Relay UE after the L2 U2N Relay UE enters RRC\_CONNECTED state, which happens during step 5. + +For service continuity of L2 U2N Remote UE, the following procedure is used, in case of the L2 U2N Remote UE switching from direct to indirect path via a L2 U2N Relay UE in RRC\_CONNECTED under another gNB: + +![Sequence diagram for L2 U2N Remote UE inter-gNB switching from direct to indirect path via a L2 U2N Relay UE in RRC_CONNECTED. The diagram shows interactions between Remote UE, Source gNB, Relay UE, and Target gNB.](ba3c1ae751b210a44f2c210bf95210e0_img.jpg) + +``` + +sequenceDiagram + participant Remote UE + participant Source gNB + participant Relay UE + participant Target gNB + + Note left of Remote UE: 0. UL/DL data + Remote UE->>Source gNB: 1. Measurement and reporting + Note right of Source gNB: 2. Decision of switching to another gNB via relay + Source gNB->>Target gNB: 3. HANDOVER REQUEST + Note right of Target gNB: 4. Admission control + Target gNB->>Relay UE: 5. RRC Reconfiguration + Target gNB->>Source gNB: 6. HANDOVER REQUEST ACKNOWLEDGE + Source gNB->>Remote UE: 7. RRCReconfiguration + Source gNB->>Target gNB: 8. SN STATUS TRANSFER + Remote UE->>Relay UE: 9. PC5 connection establishment + Remote UE->>Target gNB: 10. RRCReconfigurationComplete + Note left of Remote UE: 11. UL and DL data + Source gNB->>Target gNB: 12. UE CONTEXT RELEASE + +``` + +Sequence diagram for L2 U2N Remote UE inter-gNB switching from direct to indirect path via a L2 U2N Relay UE in RRC\_CONNECTED. The diagram shows interactions between Remote UE, Source gNB, Relay UE, and Target gNB. + +**Figure 16.12.6.2-2: Procedure for L2 U2N Remote UE inter-gNB switching from direct to indirect path via a L2 U2N Relay UE in RRC\_CONNECTED** + +1. The L2 U2N Remote UE reports one or multiple candidate L2 U2N Relay UE(s) and Uu measurements to the source gNB, after it measures/discovers the candidate L2 U2N Relay UE(s): + - The L2 U2N Remote UE filters the appropriate L2 U2N Relay UE(s) according to relay selection criteria before reporting. The L2 U2N Remote UE shall report only the L2 U2N Relay UE candidate(s) that fulfil the higher layer criteria; + +- The reporting includes at least a L2 U2N Relay UE ID, a L2 U2N Relay UE's serving cell ID, and a sidelink measurement quantity information. SD-RSRP is used as sidelink measurement quantity. +2. The source gNB decides to trigger path switch for the L2 U2N Remote UE onto indirect path of the target gNB, based on *MeasurementReport* and RRM information. + 3. The source gNB sends a HANDOVER REQUEST message to the target gNB to prepare the path switch at the target side. The HANDOVER REQUEST message includes Remote UE L2 ID and a list of candidate target relay UE IDs belonging to one cell. + 4. Admission Control may be performed by the target gNB. + 5. The target gNB selects one target Relay UE from the list of candidate Relay UEs provided by the source gNB, and sends the *RRCReconfiguration* message to L2 U2N Relay UE for relaying configuration, which includes at least the L2 U2N Remote UE's local ID and L2 ID, Uu Relay RLC channel and PC5 Relay RLC channel configuration for relaying, and bearer mapping configuration. + 6. The target gNB sends the HANDOVER REQUEST ACKNOWLEDGE message to the source gNB, which contains new RRC configuration for L2 U2N Remote UE. + 7. The source gNB sends the *RRCReconfiguration* message to the L2 U2N Remote UE, which includes at least the L2 U2N Relay UE ID, Remote UE's local ID, PC5 Relay RLC channel configuration for relay traffic and the associated Uu end-to-end radio bearer(s). The L2 U2N Remote UE stops User Plane and Control Plane transmission over the direct path after reception of the *RRCReconfiguration* message from the source gNB. + 8. The source gNB sends the SN STATUS TRANSFER message to the target gNB to convey the uplink PDCP SN receiver status and the downlink PDCP SN transmitter status of the L2 U2N Remote UE's DRBs for which PDCP status preservation applies (i.e. for RLC AM). + 9. The L2 U2N Remote UE establishes PC5 connection with L2 U2N Relay UE. + 10. The L2 U2N Remote UE sends the *RRCReconfigurationComplete* message to target gNB via the L2 U2N Relay UE. + 11. The data path is switched from direct path to indirect path between the L2 U2N Remote UE and the target gNB via the target L2 U2N Relay UE. + 12. The target gNB sends the UE CONTEXT RELEASE message to inform the source gNB about the success of the path switch. + +### 16.12.6.3 Switching from indirect to indirect path + +The gNB can select an L2 U2N Relay UE in any RRC state i.e., RRC\_IDLE, RRC\_INACTIVE, or RRC\_CONNECTED, as a target L2 U2N Relay UE for indirect to indirect path switch. + +For service continuity of L2 U2N Remote UE, the following procedure is used, in case of the L2 U2N Remote UE switching from indirect path via L2 U2N Relay UE to indirect path via a target L2 U2N Relay UE in RRC\_CONNECTED: + +![Sequence diagram illustrating the procedure for L2 U2N Remote UE intra-gNB switching from indirect to indirect path via a target L2 U2N Relay UE in RRC_CONNECTED. The diagram shows four lifelines: Source L2 U2N Relay UE, L2 U2N Remote UE, Target L2 U2N Relay UE, and gNB. The sequence starts with the Remote UE sending a measurement report to the gNB. The gNB then sends an RRCReconfiguration message to the Target L2 U2N Relay UE. The gNB also sends an RRCReconfiguration message to the Remote UE. The Remote UE establishes a PC5-RR connection with the Target L2 U2N Relay UE. The Remote UE completes the path switch procedure by sending an RRCReconfigurationComplete message to the gNB via the Target L2 U2N Relay UE. The gNB sends an RRCReconfiguration message to the Source L2 U2N Relay UE to reconfigure the connection. Finally, either the Source L2 U2N Relay UE's AS layer or the Remote UE's AS layer indicates upper layers to release the PC5 unicast link.](3054e46608784063609e8c7a253fcd24_img.jpg) + +``` + +sequenceDiagram + participant SourceL2U2NRelayUE as Source L2 U2N Relay UE + participant RemoteUE as L2 U2N Remote UE + participant TargetL2U2NRelayUE as Target L2 U2N Relay UE + participant gNB as gNB + + Note left of SourceL2U2NRelayUE: Indirect path via Source L2 U2N Relay UE + RemoteUE->>gNB: Measurement Report + gNB-->>TargetL2U2NRelayUE: RRCReconfiguration + gNB-->>RemoteUE: RRCReconfiguration + RemoteUE->>TargetL2U2NRelayUE: PC5-RR Connection + RemoteUE->>gNB: RRCReconfigurationComplete (via Target) + gNB-->>SourceL2U2NRelayUE: RRCReconfiguration + Note right of TargetL2U2NRelayUE: Indirect path via Target L2 U2N Relay UE + +``` + +Sequence diagram illustrating the procedure for L2 U2N Remote UE intra-gNB switching from indirect to indirect path via a target L2 U2N Relay UE in RRC\_CONNECTED. The diagram shows four lifelines: Source L2 U2N Relay UE, L2 U2N Remote UE, Target L2 U2N Relay UE, and gNB. The sequence starts with the Remote UE sending a measurement report to the gNB. The gNB then sends an RRCReconfiguration message to the Target L2 U2N Relay UE. The gNB also sends an RRCReconfiguration message to the Remote UE. The Remote UE establishes a PC5-RR connection with the Target L2 U2N Relay UE. The Remote UE completes the path switch procedure by sending an RRCReconfigurationComplete message to the gNB via the Target L2 U2N Relay UE. The gNB sends an RRCReconfiguration message to the Source L2 U2N Relay UE to reconfigure the connection. Finally, either the Source L2 U2N Relay UE's AS layer or the Remote UE's AS layer indicates upper layers to release the PC5 unicast link. + +**Figure 16.12.6.3-1: Procedure for L2 U2N Remote UE intra-gNB switching from indirect to indirect path via a target L2 U2N Relay UE in RRC\_CONNECTED** + +1. The L2 U2N Remote UE reports one or multiple candidate L2 U2N Relay UE(s) and the measurement result(s) between L2 U2N Remote UE and the candidate L2 U2N Relay UE(s). The detailed reporting components can be referred to the cases for switching from direct to indirect path (see clause 16.12.6.2). The L2 U2N Remote UE can provide information to the gNB according to the measurement configuration on which the gNB can decide indirect path switching. +2. The gNB decides to switch the L2 U2N Remote UE to a target L2 U2N Relay UE under the same gNB. +3. The gNB sends an *RRCReconfiguration* message to the target L2 U2N Relay UE, which includes at least the L2 U2N Remote UE's local ID and L2 ID, Uu and PC5 Relay RLC channel configuration for relaying, and bearer mapping configuration. +4. The gNB sends the *RRCReconfiguration* message to the L2 U2N Remote UE. The *RRCReconfiguration* message includes at least the target L2 U2N Relay UE ID, Remote UE's local ID, PC5 Relay RLC channel configuration for relay traffic, and the associated end-to-end radio bearer(s). The L2 U2N Remote UE stops UP and CP transmission over the indirect path via the Source L2 U2N Relay UE after the reception of the *RRCReconfiguration* message from the gNB. +5. The L2 U2N Remote UE establishes PC5-RR connection with the target L2 U2N Relay UE. +6. The L2 U2N Remote UE completes the path switch procedure by sending the *RRCReconfigurationComplete* message to the gNB via the target L2 U2N Relay UE. +7. The gNB sends the *RRCReconfiguration* message to the Source L2 U2N Relay UE to reconfigure the connection between the Source L2 U2N Relay UE and the gNB. The *RRCReconfiguration* message to the Source L2 U2N Relay UE can be sent any time after step 4 based on gNB implementation (e.g., to release Uu and PC5 Relay RLC channel configuration for relaying, and bearer mapping configuration related to the L2 U2N Remote UE). +8. Either Source L2 U2N Relay UE's AS layer or L2 U2N Remote UE's AS layer indicates upper layers to release PC5 unicast link after receiving the *RRCReconfiguration* message from the gNB. The timing to execute link release is up to UE implementation after step 4 or step 7. + +- 9. The data path is switched from the source relay UE to the target relay UE between the L2 U2N Remote UE and the gNB. This step can be any time after step 6. + +In case that the selected L2 U2N Relay UE for indirect to indirect path switch is in RRC\_IDLE or RRC\_INACTIVE, the specific operation of the L2 U2N Remote UE and the selected L2 U2N Relay UE is the same as the case of direct to indirect path switch (see clause 16.12.6.2). + +For service continuity of L2 U2N Remote UE between inter-gNBs, the following procedure is used, in case of the L2 U2N Remote UE, which is connected to indirect path, switching to another indirect path via a target L2 U2N Relay UE in RRC\_CONNECTED under another gNB: + +![Sequence diagram showing the procedure for L2 U2N Remote UE inter-gNB switching from indirect to indirect path via a target L2 U2N Relay UE in RRC_CONNECTED. The diagram involves five entities: Remote UE, Source Relay UE, Source gNB, Target Relay UE, and Target gNB. The sequence starts with UL/DL data exchange, followed by measurement and reporting, a decision to switch, and then a series of handover messages (REQUEST, ACKNOWLEDGE, RRC Reconfiguration) and context transfers between the gNBs and UEs.](ec15e024ce479a90bcd696b471bd9747_img.jpg) + +``` + +sequenceDiagram + participant Remote UE + participant Source Relay UE + participant Source gNB + participant Target Relay UE + participant Target gNB + + Note left of Remote UE: 0. UL/DL data + Remote UE->>Source gNB: 1. Measurement and reporting + Note right of Source gNB: 2. Decision of switching to another gNB + Source gNB->>Target gNB: 3. HANDOVER REQUEST + Note right of Target gNB: 4. Admission control + Target gNB->>Target Relay UE: 5. RRC Reconfiguration + Target gNB->>Source gNB: 6. HANDOVER REQUEST ACKNOWLEDGE + Source gNB->>Remote UE: 7. RRC Reconfiguration + Source gNB->>Target gNB: 8. SN STATUS TRANSFER + Source gNB->>Remote UE: 9. PC5 connection establishment + Remote UE->>Target gNB: 10. RRC ReconfigurationComplete + Note left of Remote UE: 11. UL and DL data + Source gNB->>Target gNB: 12. UE CONTEXT RELEASE + Note right of Source gNB: 13. RRC Reconfiguration + Source gNB->>Remote UE: 14. PC5 connection release + +``` + +Sequence diagram showing the procedure for L2 U2N Remote UE inter-gNB switching from indirect to indirect path via a target L2 U2N Relay UE in RRC\_CONNECTED. The diagram involves five entities: Remote UE, Source Relay UE, Source gNB, Target Relay UE, and Target gNB. The sequence starts with UL/DL data exchange, followed by measurement and reporting, a decision to switch, and then a series of handover messages (REQUEST, ACKNOWLEDGE, RRC Reconfiguration) and context transfers between the gNBs and UEs. + +**Figure 16.12.6.3-2: Procedure for L2 U2N Remote UE inter-gNB switching from indirect to indirect path via a target L2 U2N Relay UE in RRC\_CONNECTED** + +- The L2 U2N Remote UE reports one or multiple candidate L2 U2N Relay UE(s) and Uu measurements to the source gNB, after it measures/discovers the candidate L2 U2N Relay UE(s): + - The L2 U2N Remote UE filters the appropriate L2 U2N Relay UE(s) according to relay selection criteria before reporting. The L2 U2N Remote UE shall report only the L2 U2N Relay UE candidate(s) that fulfil the higher layer criteria; + - The reporting includes at least a L2 U2N Relay UE ID, a L2 U2N Relay UE's serving cell ID, and a sidelink measurement quantity information. SD-RSRP is used as sidelink measurement quantity. +- The source gNB decides to trigger the L2 U2N Remote UE to switch to an indirect path of another gNB. +- The source gNB sends a HANDOVER REQUEST message to the target gNB to prepare the path switch at the target side. The HANDOVER REQUEST message includes Remote UE L2 ID and a list of candidate target relay UE IDs belonging to one cell. + +- NOTE: In order to support the DL lossless handover for the L2 U2N Remote UE, the source gNB may not discard the DL data even though the delivery of the data has been acknowledged by the source L2 U2N Relay UE based on the gNB implementation. Then, the source gNB forwards the buffered DL data to the target gNB during the data forwarding procedure. +4. Admission Control may be performed by the target gNB. + 5. The target gNB selects one target Relay UE from the list of candidate Relay UEs provided by the source gNB, sends the *RRCReconfiguration* message to the L2 U2N Relay UE for relaying configuration, which includes at least the L2 U2N Remote UE's local ID and L2 ID, Uu Relay RLC channel and PC5 Relay RLC channel configuration for relaying, and bearer mapping configuration. + 6. The target gNB sends the HANDOVER REQUEST ACKNOWLEDGE message to the source gNB, which contains new RRC configuration for L2 U2N Remote UE. + 7. The source gNB sends the *RRCReconfiguration* message to the L2 U2N Remote UE, which includes at least the target L2 U2N Relay UE ID, Remote UE's local ID, PC5 Relay RLC channel configuration for relay traffic and the associated end-to-end Uu radio bearer(s). The L2 U2N Remote UE stops User Plane and Control plane transmission over the (source) indirect path after reception of the *RRCReconfiguration* message from the source gNB. + 8. The source gNB sends the SN STATUS TRANSFER message to the target gNB to convey the uplink PDCP SN receiver status and the downlink PDCP SN transmitter status of the L2 U2N Remote UE's DRBs for which PDCP status preservation applies (i.e. for RLC AM). + 9. The L2 U2N Remote UE establishes PC5 connection to the target L2 U2N Relay UE. + 10. The L2 U2N Remote UE sends the *RRCReconfigurationComplete* message to the target gNB via the target L2 U2N Relay UE. + 11. The data path is switched from indirect path to indirect path between the L2 U2N Remote UE and the target gNB via the target L2 U2N Relay UE. + 12. The target gNB sends the UE CONTEXT RELEASE message to inform the source gNB about the success of the path switch. + 13. The source gNB sends the *RRCReconfiguration* message to the source L2 U2N Relay UE to reconfigure the connection between the source L2 U2N Relay UE and the source gNB. The *RRCReconfiguration* message to the source L2 U2N Relay UE can be sent any time after step 7 based on source gNB implementation (e.g., to release Uu Relay RLC channel and PC5 Relay RLC channel configuration for relaying, and bearer mapping configuration related to the L2 U2N Remote UE). + 14. Either L2 U2N Relay UE or L2 U2N Remote UE's AS layer indicates upper layer to release PC5 unicast link after receiving the *RRCReconfiguration* message from the source gNB. The timing to execute link release is up to UE implementation. + +## 16.12.7 Control plane procedures for L2 U2U Relay + +The L2 U2U Remote UE needs to establish end-to-end SL-SRB/DRBs with the peer L2 U2U Remote UE before user plane data transmission. + +The following high level connection establishment procedure in Figure 16.12.7-1 applies to a L2 U2U Relay UE and L2 U2U Remote UE: + +![Sequence diagram illustrating the procedure for L2 U2U Remote UE connection establishment. The diagram shows three vertical lifelines representing the L2 U2U Remote UE, the L2 U2U Relay UE, and the peer L2 U2U Remote UE. The sequence of messages is as follows: 1. Discovery procedure between all three UEs. 2a. The Remote UE establishes a PC5-RRC connection with the Relay UE. 2b. The Relay UE establishes a PC5-RRC connection with the peer Remote UE. 3. The Relay UE sends an RRCReconfigurationSidelink message to both Remote UEs, allocating local IDs. 4. The Remote UE establishes an end-to-end PC5-RRC connection with the peer Remote UE via the Relay UE. 5. The Remote UE sends QoS profiles to the Relay UE. 6. The Relay UE performs QoS split for PDB. The diagram uses solid lines for direct messages and dashed lines for indirect messages through the Relay UE.](cf734b5645d3e02a8df25f67904cd2d3_img.jpg) + +Sequence diagram illustrating the procedure for L2 U2U Remote UE connection establishment. The diagram shows three vertical lifelines representing the L2 U2U Remote UE, the L2 U2U Relay UE, and the peer L2 U2U Remote UE. The sequence of messages is as follows: 1. Discovery procedure between all three UEs. 2a. The Remote UE establishes a PC5-RRC connection with the Relay UE. 2b. The Relay UE establishes a PC5-RRC connection with the peer Remote UE. 3. The Relay UE sends an RRCReconfigurationSidelink message to both Remote UEs, allocating local IDs. 4. The Remote UE establishes an end-to-end PC5-RRC connection with the peer Remote UE via the Relay UE. 5. The Remote UE sends QoS profiles to the Relay UE. 6. The Relay UE performs QoS split for PDB. The diagram uses solid lines for direct messages and dashed lines for indirect messages through the Relay UE. + +**Figure 16.12.7-1: Procedure for L2 U2U Remote UE connection establishment** + +1. The L2 U2U Remote UE, L2 U2U Relay UE, and peer L2 U2U Remote UE perform discovery procedure or integrated discovery procedure. +- 2a. The L2 U2U Remote UE establishes/modifies a PC5-RRC connection with the selected L2 U2U Relay UE (i.e., as specified in TS 23.304 [48]). +- 2b. The L2 U2U Relay UE establishes/modifies a PC5-RRC connection with the peer L2 U2U Remote UE (i.e., as specified in TS 23.304 [48]). +3. The L2 U2U Relay UE allocates two local IDs and it is delivered via *RRCReconfigurationSidelink* message to each of the L2 U2U Remote UEs: one local ID to identify the L2 U2U Remote UE, the other local ID to identify the peer L2 U2U Remote UE. When the local ID is delivered, an L2 ID of the peer L2 U2U Remote UE is also delivered to the U2U Remote UE for making the association between the local ID and the L2 ID of the peer U2U Remote UE. +4. The L2 U2U Remote UE establishes end-to-end PC5-RRC connection with the peer L2 U2U Remote UE via the L2 U2U Relay UE. For the end-to-end connection establishment, fixed indexes (i.e., 0/1/2/3) are defined for end-to-end SL-SRB 0/1/2/3 respectively, and specified PC5 Relay RLC Channel configuration is used on each hop. The sidelink UE capability is exchanged between the L2 U2U Remote UEs via PC5-RRC (e.g., SL-SRB3) message. +5. The L2 U2U Remote UE sends to the L2 U2U Relay UE all the QoS profiles for the end-to-end QoS flows via PC5-RRC. +6. The L2 U2U Relay UE performs QoS split only for PDB. + +NOTE: It is up to L2 U2U Relay UE implementation on how to split PDB. + +7. The L2 U2U Relay UE sends the split QoS value (i.e., PDB) via PC5-RRC message to the L2 U2U Remote UE. The L2 U2U Remote UE or the serving gNB of the L2 U2U Remote UE derives the PDCP and SDAP configuration for end-to-end SL-DRB and provides the portion of the configuration related to reception to the peer L2 U2U Remote UE using end-to-end *RRCREconfigurationSidelink* messages. The end-to-end bearer IDs for SL-SRB and SL-DRB are used as input for the L2 U2U Relay ciphering and deciphering at PDCP. +- 9a. The L2 U2U Remote UE or the serving gNB of the L2 U2U Remote UE derives the first hop configuration (e.g. PC5 Relay RLC Channel configuration) for SL-DRB and provides to the L2 U2U Relay UE of the configuration related to receiving on the first hop (i.e., Rx by the relay UE), using per-hop *RRCREconfigurationSidelink* message. +- 9b. The L2 U2U Relay UE or the serving gNB of the L2 U2U Relay UE derives the second hop configuration (e.g. PC5 Relay RLC Channel configuration) for each SL-DRB and provides to the peer L2 U2U Remote UE of the configuration related to receiving data packets on the second hop (i.e., RX by the peer remote UE), using per-hop *RRCREconfigurationSidelink* message. +10. The L2 U2U Remote UE and the peer L2 U2U Remote UE transmit or receive data via L2 U2U Relay UE. + +## 16.13 Support of Reduced Capability (RedCap) and enhanced Reduced Capability (eRedCap) NR devices + +### 16.13.1 Introduction + +A RedCap UE has reduced capabilities with the intention to have lower complexity with respect to non-RedCap UEs. It is mandatory for a RedCap UE to support 20 MHz maximum UE channel bandwidth in FR1 and 100 MHz in FR2. An eRedCap UE has further reduced capabilities with the intention to have lower complexity with respect to RedCap UEs. It is mandatory for an eRedCap UE to support reduced DL/UL peak data rate of 10 Mbps, with or without reduced baseband bandwidth of 5 MHz for unicast PDSCH/PUSCH in FR1. + +### 16.13.2 Capabilities + +CA, MR-DC, DAPS, CPA, CPC and IAB related capabilities are not supported by (e)RedCap UEs, as defined together with other limitations in TS 38.306 [11]. It is up to the network to prevent (e)RedCap UEs from using radio capabilities not intended for (e)RedCap UEs. + +### 16.13.3 Identification, access and camping restrictions + +A RedCap UE can be identified by the network during Random Access procedure via MSG3/MSGA from a RedCap specific LCID(s) and optionally via MSG1/MSGA (PRACH occasion or PRACH preamble). An eRedCap UE can be identified by the network during Random Access procedure via MSG3/MSGA from an eRedCap specific LCID(s) and optionally via MSG1. For RedCap UE identification via MSG1/MSGA, RedCap specific Random Access configuration may be configured by the network. For eRedCap UE identification via MSG1, eRedCap specific Random Access configuration may be configured by the network. For MSG3/MSGA, an (e)RedCap UE is identified by the dedicated LCID(s) indicated for CCCH identification (CCCH or CCCH1) regardless whether (e)RedCap specific Random Access configuration is configured by the network. + +(e)RedCap UEs with 1 Rx branch and 2 Rx branches can be allowed separately via system information. In addition, (e)RedCap UEs in Half-Duplex FDD mode can be allowed via system information. A RedCap specific IFRI can be provided in SIB1, when absent, RedCap UEs access is not allowed. An eRedCap specific IFRI can be provided in SIB1, when absent, eRedCap UEs access is not allowed. Information on which frequencies (e)RedCap UE access is allowed can be provided in system information. + +An (e)RedCap UE with 1 Rx branch applies the associated offset for broadcasted cell specific RSRP thresholds for random access, SDT, cell edge condition and cell (re)selection criterion as specified in TS 38.133 [13]. + +NOTE: It is up to the E-UTRA network, if possible, to avoid handover attempts of an (e)RedCap UE to a target NR cell not supporting (e)RedCap. It is up to the (e)RedCap UE implementation, if possible, to recover from handover attempts to a target NR cell not supporting (e)RedCap. + +### 16.13.4 RRM measurement relaxations + +RRM measurement relaxation is enabled and disabled by the network. In RRC\_IDLE and RRC\_INACTIVE an (e)RedCap UE is allowed to relax neighbour cell RRM measurements when the stationary criterion is met or when both stationary criterion and not-at-cell-edge criterion are met. Network may configure stationary criterion for an (e)RedCap UE in RRC\_CONNECTED and the UE reports its RRM measurement relaxation fulfilment status using UE Assistance Information when the stationarity criterion is met or no longer met. + +### 16.13.5 BWP operation + +An (e)RedCap UE in RRC\_IDLE or RRC\_INACTIVE monitors paging only in an initial BWP (default or RedCap specific) associated with CD-SSB and performs cell (re-)selection and related measurements on the CD-SSB. If a RedCap-specific initial UL BWP is configured and NUL is selected, (e)RedCap UEs shall use only the RedCap-specific initial UL BWP to perform RACH procedure in RRC\_IDLE and RRC\_INACTIVE or to perform CG-SDT procedure (as described in clause 18.0) in RRC\_INACTIVE. + +An (e)RedCap UE may be configured with multiple NCD-SSBs provided that each BWP is configured with at most one SSB. NCD-SSB may be configured for an (e)RedCap UE in RRC\_CONNECTED to perform RLM, BFD, and RRM measurements and RA resource selection when the active BWP does not contain CD-SSB. + +An (e)RedCap UE may be configured with NCD-SSB for a RedCap-specific initial DL BWP to perform SDT procedure in RRC\_INACTIVE (as described in clause 18.0) in case the RedCap-specific initial DL BWP does not contain CD-SSB. + +## 16.14 Non-Terrestrial Networks + +### 16.14.1 Overview + +Figure 16.14.1-1 below illustrates an example of a Non-Terrestrial Network (NTN) providing non-terrestrial NR access to the UE by means of an NTN payload and an NTN Gateway, depicting a service link between the NTN payload and a UE, and a feeder link between the NTN Gateway and the NTN payload. + +![Figure 16.14.1-1: Overall illustration of an NTN. The diagram shows a vertical stack of components. At the top is the AMF/UPF (represented by a server icon). Below it is the NG interface (a green line). The gNB is enclosed in a dashed box and contains an NTN Gateway (a satellite dish icon) and an NTN payload (a satellite icon). A blue dashed line labeled 'feeder link' connects the NTN Gateway to the NTN payload. At the bottom, outside the gNB box, is the NR Uu interface (a red line) connecting to the User Equipment (UE). A blue dashed line labeled 'service link' connects the NTN payload to the NR Uu interface.](c0ef0292328b1602e278f6a0b2ee07e0_img.jpg) + +Figure 16.14.1-1: Overall illustration of an NTN. The diagram shows a vertical stack of components. At the top is the AMF/UPF (represented by a server icon). Below it is the NG interface (a green line). The gNB is enclosed in a dashed box and contains an NTN Gateway (a satellite dish icon) and an NTN payload (a satellite icon). A blue dashed line labeled 'feeder link' connects the NTN Gateway to the NTN payload. At the bottom, outside the gNB box, is the NR Uu interface (a red line) connecting to the User Equipment (UE). A blue dashed line labeled 'service link' connects the NTN payload to the NR Uu interface. + +**Figure 16.14.1-1: Overall illustration of an NTN** + +NOTE 1: Figure 16.14.1-1 illustrates an NTN; RAN4 aspects are out of scope. + +The NTN payload transparently forwards the radio protocol received from the UE (via the service link) to the NTN Gateway (via the feeder link) and vice-versa. The following connectivity is supported by the NTN payload: + +- An NTN gateway may serve multiple NTN payloads; +- An NTN payload may be served by multiple NTN gateways. + +NOTE 2: In this release, the NTN-payload may change the carrier frequency, before re-transmitting it on the service link, and vice versa (respectively on the feeder link). + +For NTN, the following applies in addition to Network Identities as described in clause 8.2: + +- A Tracking Area corresponds to a fixed geographical area. Any respective mapping is configured in the RAN; +- A Mapped Cell ID as specified in clause 16.14.5. + +Three types of service links are supported: + +- Earth-fixed: provisioned by beam(s) continuously covering the same geographical areas all the time (e.g., the case of GSO satellites); +- Quasi-Earth-fixed: provisioned by beam(s) covering one geographic area for a limited period and a different geographic area during another period (e.g., the case of NGSO satellites generating steerable beams); +- Earth-moving: provisioned by beam(s) whose coverage area slides over the Earth surface (e.g., the case of NGSO satellites generating fixed or non-steerable beams). + +With NGSO satellites, the gNB can provide either quasi-Earth-fixed service link or Earth-moving service link, while gNB operating with GSO satellite can provide Earth fixed service link. + +In this release, the UE supporting NTN is GNSS-capable. + +In NTN, the distance refers to Euclidean distance. + +## 16.14.2 Timing and Synchronization + +### 16.14.2.1 Scheduling and Timing + +DL and UL are frame aligned at the uplink time synchronization reference point (RP) with an offset given by $N_{TA,offset}$ (see clause 4.2 of TS 38.213 [38]). + +To accommodate the propagation delay in NTN, several timing relationships are enhanced by a Common Timing Advance (Common TA) and two offsets and : + +- is a configured timing offset that is equal to the RTT between the RP and the NTN payload. +- is a configured scheduling offset that needs to be larger or equal to the sum of the service link RTT and the Common TA. +- is a configured offset that is approximately equal to the RTT between the RP and the gNB. + +The scheduling offset is used to allow the UE sufficient processing time between a downlink reception and an uplink transmission, see TS 38.213 [38]. + +The offset is used to delay the application of a downlink configuration indicated by a MAC CE command on PDSCH, see TS 38.213 [38], and in estimation of UE-gNB RTT, see TS 38.321 [6]. It may be provided by the network when downlink and uplink frame timing are not aligned at gNB. The is also used in the random access procedure, to determine the start time of RAR window/MsgB window after a Msg1/MsgA transmission (see TS 38.213 [38]). + +The Service link RTT, Feeder link RTT, RP, Common TA, and $T_{TA}$ (see clause 16.14.2.2) are illustrated in Figure 16.14.2.1-1. + +![Diagram illustrating timing relationships in an NTN system. A satellite is at the top, a User Equipment (UE) is at the bottom left, and a Relay Point (RP) is at the bottom right. The diagram shows the following timing components: T_TA (Common Timing Advance) is the time offset between the UE and the satellite; Service link RTT is the round-trip time between the UE and the satellite; Feeder link RTT is the round-trip time between the RP and the satellite; K_mac is the MAC layer processing time at the RP; and Common TA is the time offset between the RP and the satellite.](835afd2841651b4ae5ee24f5a0025f9f_img.jpg) + +The diagram illustrates the timing relationships in an NTN system. A satellite is at the top, a User Equipment (UE) is at the bottom left, and a Relay Point (RP) is at the bottom right. The diagram shows the following timing components: + +- $T_{TA}$ (Common Timing Advance): The time offset between the UE and the satellite. +- Service link RTT: The round-trip time between the UE and the satellite. +- Feeder link RTT: The round-trip time between the RP and the satellite. +- $K_{mac}$ : The MAC layer processing time at the RP. +- Common TA: The time offset between the RP and the satellite. + +Diagram illustrating timing relationships in an NTN system. A satellite is at the top, a User Equipment (UE) is at the bottom left, and a Relay Point (RP) is at the bottom right. The diagram shows the following timing components: T\_TA (Common Timing Advance) is the time offset between the UE and the satellite; Service link RTT is the round-trip time between the UE and the satellite; Feeder link RTT is the round-trip time between the RP and the satellite; K\_mac is the MAC layer processing time at the RP; and Common TA is the time offset between the RP and the satellite. + +Figure 16.14.2.1-1: Illustration of timing relationship (for collocated gNB and NTN Gateway) + +The network may configure the HARQ operation as follows: + +- For downlink, HARQ feedback can be enabled or disabled per HARQ process (as specified in clause 5.3.2.2 and clause 5.7 of TS 38.321 [6]). Disabling HARQ feedback allows scheduling a HARQ process before one HARQ RTT has elapsed since last scheduled. +- For uplink, HARQ mode (i.e. HARQ mode A or HARQ mode B) can be configured per HARQ process (as specified in clause 5.4.3.1 and clause 5.7 of TS 38.321 [6]). HARQ mode B allows scheduling a HARQ process before one HARQ RTT has elapsed since last scheduled. + +NOTE: For the HARQ processes configured with HARQ feedback enabled/disabled, it is up to network implementation to ensure a proper configuration of HARQ feedback (e.g., either all enabled or all disabled) for HARQ processes used by an SPS configuration. For the HARQ processes configured with HARQ mode, it is up to network implementation to ensure a proper configuration of HARQ mode (e.g., either all HARQ mode A or all HARQ mode B) for HARQ processes used by a CG configuration. + +## 16.14.2.2 Timing Advance and Frequency Pre-compensation + +For the serving cell, the network broadcast valid ephemeris information and Common TA parameters. The UE shall have valid GNSS position as well as ephemeris and Common TA before connecting to an NTN cell. To achieve synchronisation, before and during connection to an NTN cell, the UE shall compute the RTT between UE and the RP based on the GNSS position, the ephemeris, and the Common TA parameters (see clause 4.2 in TS 38.213 [38]), and autonomously pre-compensate the $T_{TA}$ for the RTT between the UE and the RP as illustrated in Figure 16.14.2.1-1 (see clause 4.3 of TS 38.211 [52]). + +The UE shall compute the frequency Doppler shift of the service link, and autonomously pre-compensate for it in the uplink transmissions, by considering UE position and the ephemeris. If the UE does not have a valid GNSS position and/or valid ephemeris and Common TA, it shall not transmit until both are regained. + +In connected mode, the UE shall be able to continuously update the Timing Advance and frequency pre-compensation. + +The UE may be configured to report Timing Advance during Random Access procedures or in connected mode. In connected mode, event-triggered reporting of the Timing Advance is supported. + +### Figure 16.14.2.2-1: Void + +While the pre-compensation of the instantaneous Doppler shift experienced on the service link is to be performed by the UE, the management of Doppler shift experienced over the feeder link and transponder frequency error is left to the network implementation. + +## 16.14.3 Mobility and State transition + +### 16.14.3.1 Mobility in RRC\_IDLE and RRC\_INACTIVE + +The same principles as described in 9.2.1 apply to mobility in RRC\_IDLE for NTN and the same principles as described in 9.2.2 apply to mobility in RRC\_INACTIVE for NTN unless hereunder specified. + +The network may broadcast multiple Tracking Area Codes (TACs) per PLMN in an NR NTN cell. A TAC change in the System Information is under network control, i.e. it may not be exactly synchronised with real-time illumination of beams on ground. + +For the NTN-TN mobility, the network may broadcast cell information on NR TN and EUTRA TN coverage areas in SIB25. This is supported for Earth-Fixed, Quasi-Earth-fixed and Earth-Moving cells. The coverage information consists in a list of geographical TN areas, with associated frequency information also indicated. UE can skip TN measurement based on the broadcast TN coverage information. + +The UE can determine the network type (terrestrial or non-terrestrial) implicitly by the existence of *cellBarredNTN* in SIB1. + +The NTN ephemeris is provided in SIB19. In an NTN cell, it includes serving cell's NTN payload ephemeris and optionally neighbouring cell's NTN payload ephemeris. + +### 16.14.3.2 Mobility in RRC\_CONNECTED + +#### 16.14.3.2.1 Handover + +The same principle as described in 9.2.3.2 applies unless hereunder specified: + +During mobility between NTN and Terrestrial Network (TN), a UE is not required to connect to both NTN and TN at the same time. + +NOTE: NTN TN handover refers to mobility in both directions, i.e. from NTN to TN (hand-in) and from TN to NTN (hand-out). + +DAPS handover is not supported for NTN in this release of the specification. + +UE may support mobility between gNBs operating with NTN payloads in different orbits (e.g., GSO, NGSO at different altitudes). + +RACH-less handover as specified in TS 38.321 [6] is supported in NTNs. + +#### 16.14.3.2.2 Conditional Handover + +The same principle as described in 9.2.3.4 applies to NTN unless hereunder specified. + +NTN supports the following additional trigger conditions upon which UE may execute CHO to a candidate cell, as defined in TS 38.331 [12]: + +- The RRM measurement-based event A4; +- A time-based trigger condition; +- A location-based trigger condition. + +Time-based or location-based trigger conditions may be configured independently from the measurement condition for CHO in NTN in at least hard satellite switch case where the service discontinuity gap time length is assumed to be zero or negligible. Otherwise, a time-based or a location-based trigger condition is always configured together with one of the measurement-based trigger conditions (CHO events A3/A4/A5) as defined in TS 38.331 [12]. + +A time-based or a location-based trigger condition is always configured together with one of the measurement-based trigger conditions (CHO events A3/A4/A5) as defined in TS 38.331 [12]. + +It is up to UE implementation how the UE evaluates the time- or location-based trigger condition together with the RRM measurement-based event. + +When a time-based trigger condition is used, the source gNB may signal the corresponding parameters to a single target gNB via the Source NG-RAN Node to Target NG-RAN Node Transparent Container in an NG-C based handover, see TS 23.502 [22]. The source gNB signals the corresponding CHO configuration to the UE in the RRC Reconfiguration message during handover execution. + +When time-based trigger condition is used, the source NG-RAN node should consider the time indicated to the UE to decide when to start the early data forwarding to the target NG-RAN node. + +Time-based CHO can be performed via RACH-less. + +#### 16.14.3.2.3 Satellite switch with re-sync + +Upon both hard and soft satellite switch over in the quasi-Earth fixed scenario with the same SSB frequency and the same gNB, the satellite switch with re-sync procedure is supported. The satellite switch with re-sync avoids a L3 mobility for UEs in the cell by maintaining the same PCI on the geographical area covered by quasi-Earth fixed beam. CHO can be configured simultaneously with the satellite switch with re-sync procedure. + +For soft satellite switch over, the UE can start synchronizing with the target satellite before the source satellite ends to serve the cell. It is not required for the UE to be connected to source satellite when the UE switches to target satellite. + +### 16.14.3.3 Measurements + +The same principle as described in 9.2.4 applies to measurements in NTN unless hereunder specified. + +The network can configure: + +- multiple SMTCs in parallel per carrier and for a given set of cells depending on UE capabilities; +- measurement gaps based on multiple SMTCs; +- assistance information (e.g., ephemeris, Common TA parameters, ) provided in SIB19 for UE to perform measurement on neighbour cells in RRC\_IDLE/RRC\_INACTIVE/RRC\_CONNECTED. + +NW-controlled adjustment of SMTCs can be based on UE assistance information reported in RRC\_CONNECTED. A UE in RRC\_IDLE/RRC\_INACTIVE can adjust SMTCs based on its location and assistance information in SIB19. + +UE assistance information consists of the service link propagation delay difference(s) between serving the cell and neighbour cell(s). + +For a UE in Idle/Inactive mode it's up to UE implementation whether to perform NTN neighbour cell measurements on a cell indicated in SIB3/SIB4 but not included in SIB19. + +For a UE in Connected mode, it's up to UE implementation whether to perform NTN neighbour cell measurements on a cell included in the measurement configuration but not included in SIB19. + +UE can perform time-based and location-based measurements on neighbour cells in RRC\_IDLE/RRC\_INACTIVE: + +- The timing and location information associated to the serving cell is provided in SIB19; +- Timing information refers to the UTC time when the serving cell stops serving the current geographical area; +- Location information refers: + - In the quasi-Earth fixed cell scenario, to the reference location of the serving cell and a distance threshold to the reference location. + - In the Earth moving cell scenario, to the reference location of the serving cell at the epoch time and a distance threshold to the reference location. + +The time-based measurement initiation may be applicable for the feeder link switchover case for cell (re)selection. + +Measurement rules for cell re-selection based on timing information and location information are specified in clause 5.2.4.2 in TS 38.304 [10]. + +## 16.14.4 Switchover + +### 16.14.4.1 Definitions + +A feeder link switchover is the procedure where the feeder link is changed from a source NTN Gateway to a target NTN Gateway for a specific NTN payload. The feeder link switchover is a Transport Network Layer procedure. Service link switch refers to a change of the serving NTN payload. + +Both hard and soft feeder link switchover are supported in NTN. + +### 16.14.4.2 Assumptions + +A feeder link switch over may result in transferring the established connection for the affected UEs between two gNBs. + +For soft feeder link switch over, an NTN payload is able to connect to more than one NTN Gateway during a given period, i.e. a temporary overlap can be ensured during the transition between the feeder links. + +For hard feeder link switch over, an NTN payload connects to only one NTN Gateway at any given time, i.e. a radio link interruption may occur during the transition between the feeder links. + +#### 16.14.4.3 Procedures + +The NTN Control function (see Annex B.4) determines the point in time when the feeder link switch over between two gNBs is performed. The transfer of the affected UE(s)' context between the two gNBs at feeder link switch over is performed by means of either NG based or Xn based handover, and it depends on the gNBs' implementation and configuration information provided to the gNBs by the NTN Control function. + +#### 16.14.5 NG-RAN signalling + +The Cell Identity, as defined in TS 38.413 [26] and TS 38.423 [50], used in following cases corresponds to a Mapped Cell ID, irrespective of the orbit of the NTN payload or the types of service links supported: + +- The Cell Identity indicated by the gNB to the Core Network as part of the User Location Information; +- The Cell Identity used for Paging Optimization in NG interface; +- The Cell Identity used for Area of Interest; +- The Cell Identity used for PWS. + +The Cell Identity included within the target identification of the handover messages allows identifying the correct target cell. The cell identity used in the NG and Xn handover messages, Xn Setup and Xn NG-RAN Node Configuration Update procedures is expected to be Uu Cell ID. + +The Cell Identities used in the RAN Paging Area during Xn RAN paging allow the identification of the correct target cells for RAN paging. + +NOTE 1: The Cell Identity used for RAN Paging is assumed to typically represent a Uu Cell ID. + +The mapping between Mapped Cell IDs and geographical areas is configured in the RAN and Core Network. + +NOTE 2: A specific geographical location may be mapped to multiple Mapped Cell ID(s), and such Mapped Cell IDs may be configured to indicate different geographical areas (e.g. overlapping and/or with different dimensions). + +The gNB is responsible for constructing the Mapped Cell ID based on the UE location information received from the UE, if available. The mapping may be pre-configured (e.g., up to operator's policy) or up to implementation. + +NOTE 3: As described in TS 23.501 [3], the User Location Information may enable the AMF to determine whether the UE is allowed to operate at its present location. Special Mapped Cell IDs or TACs may be used to indicate areas outside the serving PLMN's country. + +The gNB reports the broadcasted TAC(s) of the selected PLMN to the AMF as part of ULI. In case the gNB knows the UE's location information, the gNB may determine the TAI the UE is currently located in and provide that TAI to the AMF as part of ULI. + +#### 16.14.6 AMF (Re-)Selection + +The gNB implements the NAS Node Selection Function specified in TS 38.410 [16]. + +For an RRC\_CONNECTED UE, when the gNB is configured to ensure that the UE connects to an AMF that serves the country in which the UE is located, if the gNB detects that the UE is in a different country to that served by the serving AMF, then it should perform an NG handover to change to an appropriate AMF, or initiate an UE Context Release Request procedure towards the serving AMF (in which case the AMF may decide to de-register the UE). + +For the purpose of selecting an appropriate AMF, the 5GC may verify the UE location according to TS 23.501 [3] and TS 38.305 [42] after the UE has attached to the network. + +NOTE: UE location verification for AMF selection should not be necessary if NTN cell(s) do not extend across countries. + +## 16.14.7 O&M Requirements + +The following NTN related parameters shall be provided by O&M to the gNB providing NTN access: + +- Ephemeris information describing the orbital trajectory information or coordinates for the NTN payload. This information is provided on a regular basis or upon demand to the gNB; +- Two different sets of ephemeris format shall be supported: + - Set 1: NTN payload position and velocity state vectors: + - Position; + - Velocity. + - Set 2: At least the following parameters in orbital parameter ephemeris format, as specified in NIMA TR 8350.2 [51]: + - Semi-major axis; + - Eccentricity; + - Argument of periapsis; + - Longitude of ascending node; + - Inclination; + - Mean anomaly at epoch time. +- The explicit epoch time associated to ephemeris data; +- The location of the NTN Gateways; + +NOTE 1: The ephemeris of the NTN payloads and the location of the NTN Gateways, are used at least for the Uplink timing and frequency synchronization. It may also be used for the random access and the mobility management purposes. + +- Additional information to enable gNB operation for feeder/service link switch overs. + +NOTE 2: The NTN related parameters provided by O&M to the gNB may depend on the type of supported service links, i.e., Earth-fixed, quasi-Earth-fixed, or Earth-moving. + +## 16.14.8 Coarse UE location reporting + +Upon network request, after AS security is established in connected mode, a UE should report its coarse UE location information (most significant bits of the GNSS coordinates, ensuring an accuracy in the order of 2 km) to the NG-RAN if available. + +## 16.14.9 Support for NR NTN coverage enhancements + +To improve NR uplink coverage in NTN, the following enhancements are supported: + +- PUCCH repetition for Msg4 HARQ-ACK configured in system information or dynamically in DCI for Msg4 when multiple repetition factors are configured in the system information: + - UEs reports the capability of PUCCH repetition for Msg4 HARQ-ACK in Msg3 PUSCH; + - When Msg4 HARQ-ACK is repeated, PUCCH repetition is applied for all PUCCH transmission before dedicated PUCCH resource is provided. +- Improved channel estimation by NTN-specific PUSCH DMRS bundling enhancement that enables DMRS bundling in presence of timing drift, where the UE can maintain phase continuity by considering effects of transmission delay variation between the UE and the uplink time synchronization reference point. + +## 16.14.10 Verification of UE location + +For UE location verification based on multi-RTT with single satellite in NTN, at least the following UE and gNB measurements specified in TS 38.215 [59] are reported: gNB receive-transmit time difference at the uplink time synchronization reference point, UE receive-transmit time difference, UE receive-transmit time difference subframe offset and DL timing drift. + +The assistance information provided to the CN may include ephemeris information including accurate satellite position and velocity at the time of multi-RTT measurement, and common TA parameters (*ta-Common*, *ta-CommonDrift*, *ta-CommonDriftVariant*), and Epoch time. + +## 16.15 eXtended Reality Services + +### 16.15.1 General + +This clause describes the functionalities for the support of eXtended Reality (XR) services that require high data rate and low latency communications. An overview of XR services is available in TR 38.835 [57], while the service requirements are documented in TS 22.261 [19]. + +### 16.15.2 Awareness + +XR-Awareness relies on QoS flows, PDU Sets, Data Bursts and traffic assistance information (see TS 23.501 [3]). + +The following **PDU Set QoS Parameters** may be provided by the SMF to the gNB as part of the QoS profile of the QoS flow, and to enable PDU Set based QoS handling at least one of them shall be provided: + +- PDU Set Delay Budget (PSDB): as defined in TS 23.501 [3], upper bound for the duration between the reception time of the first PDU (at the UPF for DL, at the UE for UL) and the time when all PDUs of a PDU Set have been successfully received (at the UE in DL, at the UPF in UL). A QoS Flow is associated with only one PSDB, and when available, it applies to both DL and UL and supersedes the PDB of the QoS flow. +- PDU Set Error Rate (PSER): as defined in TS 23.501 [3], upper bound for a rate of non-congestion related PDU Set losses between RAN and the UE. A QoS Flow is associated with only one PSER, and when available, it applies to both DL and UL and supersedes the PER of the QoS flow. + +NOTE 1: In this release, a PDU set is considered as successfully delivered only when all PDUs of a PDU Set are delivered successfully. + +- PDU Set Integrated Handling Information (PSIHI): indicates whether all PDUs of the PDU Set are needed for the usage of PDU Set by application layer, as defined in TS 23.501 [3]. + +NOTE 2: The PDU Set QoS parameters are common for all PDU Sets within a QoS flow. + +During the Xn-handover preparation procedure, the source gNB sends the stored PDU Set QoS Parameters as part of the QoS profile to the target NG-RAN node. + +In addition, the UPF can identify PDUs that belong to PDU Sets, and may indicate to the gNB the following **PDU Set Information** in the GTP-U header: + +- PDU Set Sequence Number; +- Indication of End PDU of the PDU Set; +- PDU Sequence Number within a PDU Set; +- PDU Set Size in bytes; +- PDU Set Importance (PSI), which identifies the relative importance of a PDU Set compared to other PDU Sets within the same QoS Flow. + +5GC may provide XR traffic assistance information to gNB through NG AP TSC Assistance Information (TSCAI) as specified in clause 5.37.8 of TS 23.501[3] (for both GBR and non-GBR QoS flows): + +- UL and/or DL Periodicity; +- N6 Jitter Information (i.e. between UPF and Data Network) associated with the DL Periodicity. + +This assistance information can be used by the gNB to configure DRX to enable better UE power saving. + +In addition, 5GC may provide the following information through NG-U as specified in clause 5.37.5.2 of TS 23.501[3]: + +- Indication of End of Data Burst in the GTP-U header of the last PDU in downlink. + +This information can be used by the gNB to push the UE back to sleep when possible. + +In the uplink, the UE needs to be able to identify PDU Sets and Data Bursts dynamically, including PSI. How this is done is left up to UE implementation but when possible for a QoS flow, this is indicated to the gNB via UE Assistance Information. + +## 16.15.3 Power Saving + +Most XR video frame rates (15, 30, 45, 60, 72, 90 and 120 fps) correspond to periodicities that are not an integer (66.66, 33.33, 22.22, 16.66, 13.88, 11.11 and 8.33 ms respectively). The gNB may configure a DRX cycle expressed in rational numbers so that the DRX cycle matches those periodicities, e.g. for the traffic with a frame rate of 60 fps, the network may configure the UE with a DRX cycle of 50/3 ms. + +Configured grants may be configured without the need for the UE to monitor possible UL retransmissions, thus increasing the number of power saving opportunities for the UE. + +## 16.15.4 Capacity + +### 16.15.4.1 Physical Layer Enhancements + +The following enhancements for configured grant-based PUSCH transmission are introduced: + +- Support of multiple CG PUSCH transmission occasions within a single period of a CG configuration; +- Indication of unused CG PUSCH occasion(s) of a CG configuration with Uplink Control Information multiplexed in CG PUSCH transmission of the CG configuration. + +### 16.15.4.2 Layer 2 Enhancements + +#### 16.15.4.2.1 Assistance Information + +In order to enhance the scheduling of uplink resources for XR, the following improvements are introduced: + +- One additional buffer size table to reduce the quantisation errors in BSR reporting (e.g. for high bit rates): + - Whether, for an LCG, the new table can be used in addition to the regular one is configured by the gNB; + - When the new table is configured for an LCG, it is used whenever the amount of the buffered data of that LCG is within the range of the new table, otherwise the regular table is used. +- Delay Status Report (DSR) of buffered data via a dedicated MAC CE: + - Triggered for an LCG when the remaining time before discard of any buffered PDCP SDU goes below a configured threshold (threshold configured per LCG by the gNB); + - When triggered for an LCG, reports the amount of data buffered with a remaining time before discard below the configured threshold, together with the shortest remaining time of any PDCP SDU buffered. +- Reporting of uplink assistance information (jitter range, burst arrival time, UL data burst periodicity) per QoS flow by the UE via UE Assistance Information. + +#### 16.15.4.2.2 Discard + +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 at the transmitter to free up radio resources. + +NOTE 1: It cannot always be assumed that the remaining PDUs are not useful and can safely be discarded. Also, 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. + +In uplink, the UE may be configured with PDU Set based discard operation for a specific DRB. When configured, the UE discards all packets in a PDU set when one PDU belonging to this PDU set is discarded due to discard timer expiry. + +The gNB may perform downlink PDU Set discarding based on implementation by taking at least PSDB, PSI, PSIHI parameters into account. + +In case of congestion, the gNB may use the PSI for PDU set discarding. For uplink, dedicated downlink signalling is used to request the UE to apply a shorter discard timer to *low importance* SDUs in PDCP. + +NOTE 2: How SDUs are identified as *low importance* is left up to UE implementation. When a PSI is available, it can be used to classify the PDCP SDUs of a PDU Set according to the guidelines specified in TS 26.522 [58]. + +### 16.15.5 Non-Homogeneous support of PDU set based handling in NG-RAN + +During a handover from a gNB supporting PDU Set based handling to another gNB, the source gNB signals the PDU Set Information over Xn-U if the target node has signalled the support of PDU Set based handling in the Xn Handover Request Acknowledge message. + +During a handover from a gNB not supporting PDU Set based handling to a gNB supporting PDU Set based handling, the target gNB may indicate the support of PDU Set based handling to the SMF during the Path Switch Request procedure (in case of Xn handover) or Handover Resource Allocation procedure (in case of NG handover), the SMF will act as specified in TS 23.501[3]. If the indication is absent, the SMF infers that PDU Set based handling is not supported by the target NG-RAN node, then the SMF will act as specified in TS 23.501[3]. + +### 16.16 ECN marking for L4S and congestion information exposure + +In order to support ECN marking for L4S at gNB as specified in TS 23.501[3], SMF provides ECN marking request per QoS flow level to the gNB as part of PDU Session Resource Management procedure. If the gNB supports ECN marking, it provides the status indication back to the SMF which is used by the SMF as specified in TS 23.501[3]. During Xn Handover Preparation procedure, source gNB provides the ECN marking request to target gNB. + +For ECN marking for L4S at UPF, SMF requests the gNB to report congestion information per QoS flow level as part of PDU Session Resource Management procedure. If the gNB supports ECN marking for L4S at UPF, it provides the status indication back to the SMF which is used by SMF as specified in TS 23.501[3]. During Xn Handover Preparation procedure, source gNB provides the ECN marking UPF request to target gNB. + +For congestion reporting from gNB to UPF, SMF requests the gNB to report congestion information per QoS flow level as part of PDU Session Resource Management procedure. If the NG-RAN supports congestion information reporting, it provides the status indication back to the SMF which is used by the SMF as specified in TS 23.501[3]. During Xn Handover Preparation procedure, source gNB provides the congestion information request to target gNB. + +### 16.17 Support for TSN enabled Transport Network + +The NG-RAN may support the TSN enabled Transport Network during PDU Session Resource establishment or modification procedure as specified in TS 23.501 [3]. + +## 16.18 Support for Aerial UE Communication + +### 16.18.1 General + +NR connectivity for UEs capable of Aerial communication is supported via the following functionalities: + +- subscription-based Aerial UE identification and authorization, as specified in TS 23.502 [22], clause 5.2.3.3.1; +- height reporting based on the measurement event(s) where the UE's altitude has crossed a network-configured reference altitude threshold; +- height-dependent configurations which apply only to specific height regions; +- interference detection based on a measurement reporting that is triggered when a configured number of cells (i.e. larger than one) fulfils the triggering criteria simultaneously; +- signalling of flight path information from UE to NG-RAN and from the source gNB to target gNB during handover; +- location information reporting, including UE's horizontal and vertical velocity; +- broadcasting of BRID and DAA messages via PC5 interface. + +### 16.18.2 Subscription-based Identification of Aerial UE + +Support for Aerial UE functions is stored in the user's subscription information in UDM. UDM transfers this information to the AMF during Registration, Service Request and Mobility Registration Update procedures. + +The Aerial UE subscription information can be provided by the AMF to the NG-RAN node via the NGAP INITIAL CONTEXT SETUP REQUEST message during the Registration, Mobility Registration Update and Service Request procedures. The subscription information can also be updated via the NGAP UE Context Modification procedure and NGAP Path Switch Acknowledge procedure. In addition, for Xn-based handover, the source NG-RAN node can include the Aerial UE subscription information in the XnAP HANDOVER REQUEST message and RETRIEVE UE CONTEXT RESPONSE message to the target NG-RAN node. + +For intra- and inter-AMF NG-based handover, the AMF provides the Aerial UE subscription information to the target NG-RAN node after the handover procedure. + +### 16.18.3 Height-based Reporting for Aerial UE Communication + +An Aerial UE can be configured with height-dependent, event-based measurement reporting (i.e., *eventH1* and *eventH2* as defined in TS 38.331 [12]). An Aerial UE sends a measurement report when its altitude becomes higher or lower than configured threshold. The UE includes its height and location information in the measurement report if configured to do so by NG-RAN. RSRP/RSRQ measurement results are always reported when height reporting is configured. + +The Aerial UE can also be configured to trigger measurement reporting only when both a height-dependent condition and a RSRP/RSRQ/SINR-based condition are met (i.e., *eventA3H1*, *eventA3H2*, *eventA4H1*, *eventA4H2*, *eventA5H1* and *eventA5H2* in TS 38.331 [12], commonly denoted as *eventAxHy*). For the content of *eventAxHy* measurement report, the same rules as described above for *eventH1* and *eventH2* apply. + +### 16.18.4 Height-dependent Configurations for Aerial UE Communication + +An Aerial UE can be configured with multiple height-dependent configurations, each of which is applied in its corresponding height range. Height-dependent configurations can be provided independently in measurement object (i.e. *SSB-ToMeasureAltitudeBased* in TS 38.331 [12]) and an Aerial UE can use those when in RRC\_CONNECTED. + +### 16.18.5 Interference Detection and Mitigation for Aerial UE Communication + +For interference detection, an Aerial UE can be configured with RRM event A3, A4, A5 or AxHy that triggers measurement report when individual (per cell) RSRP values for a configured number of cells fulfil the configured event. Once such condition is met and a measurement report is sent, the list of triggered cells is updated when + +subsequent cell(s) fulfil the event. However, further measurement reports are not sent while the list of triggered cells remains larger than or equal to the configured number of cells unless *reportOnLeave* is configured (see TS 38.331 [12] for details). + +## 16.18.6 Flight Path Information Reporting for Aerial UE Communication + +Following an indication from the Aerial UE that flight path information is available, NG-RAN can request the Aerial UE to report flight path information consisting of a number of waypoints defined as 3D locations, as defined in TS 37.355 [43]. Aerial UE reports up to a configured number of waypoints if flight path information is available at the UE. The report can also contain a time stamp per waypoint if configured by the NG-RAN and if available at the UE. The flight path information can be also provided by the source gNB to the target gNB during handover. If configured by the NG-RAN and if the associated distance- or time-based condition (see *flightPathUpdateDistanceThr* and *flightPathUpdateTimeThr* in TS 38.331 [12], respectively) for indication reporting are met for any of the waypoints, the Aerial UE indicates the availability of the updated flight path information. The Aerial UE can also indicate the availability of the updated flight path information if a new waypoint has been added or if a future waypoint has been removed from the flight path information. + +## 16.18.7 Location Reporting for Aerial UE Communication + +Location information for Aerial UE communication can include horizontal and vertical speed if configured. Location information can be included in RRM report and in height-based reporting (as described in 16.18.3). + +## 16.18.8 BRID and DAA Support via A2X Communication + +The Aerial UE supports A2X communication which is broadcasting of BRID and DAA messages using NR sidelink. DAA can also be provided via unicast transmissions in NR sidelink. BRID and DAA message transmission is supported in both in-coverage and out-of-coverage scenarios and relies only on UE autonomous resource selection for NR sidelink communication. BRID and DAA follow the QoS framework defined for NR sidelink and dedicated A2X PQI values are stored in table 6.2.4.1-1 of TS 23.256 [60]. The NG-RAN can configure a separate SL Tx resource pool for BRID and DAA. The SL Tx pool selection for A2X is described in TS 38.321 [6], clause 5.22. + +# 16.19 Support for Air to Ground Networks + +## 16.19.1 Overview + +In Air-to-ground (ATG) network, an NG-RAN consisting of ground-based gNBs, which provide cell towers that send signals up to an aircraft's antenna(s) of onboard ATG terminal, with typical vertical altitude of around 10,000m and take-off/landing altitudes down to 3000m. + +CA and DC are not supported for ATG in this release of the specification. + +## 16.19.2 Timing and Synchronization + +### 16.19.2.1 Scheduling and Timing + +To accommodate the propagation delay in ATG, the timing relationship is enhanced by one cell-specific offset $K_{\text{offset}}$ : + +- $K_{\text{offset}}$ is a configured scheduling offset that needs to be larger or equal to the max RTT. + +The scheduling offset $K_{\text{offset}}$ is used to allow the UE sufficient processing time between a downlink reception and an uplink transmission, see TS 38.213 [38]. + +### 16.19.2.2 Timing Advance + +For the serving cell, the network broadcasts coarse gNB location information. The UE shall have valid GNSS position as well as gNB location before connecting to an ATG cell. To achieve synchronisation, before and during connection to + +an ATG cell, the UE shall compute the RTT between UE and the gNB based on the GNSS position and the gNB location parameters, and autonomously pre-compensate the TTA for the RTT between the UE and the gNB. + +In connected mode, the UE shall be able to continuously update the Timing Advance. + +The UE may be configured to report Timing Advance during Random Access procedures or in connected mode. For an RRC\_CONNECTED UE, event-triggered reporting of the Timing Advance is supported. + +## 16.19.3 Mobility + +### 16.19.3.1 Mobility in RRC\_IDLE and RRC\_INACTIVE + +The same principles as described in 9.2.1 apply to mobility in RRC\_IDLE for ATG and the same principles as described in 9.2.2 apply to mobility in RRC\_INACTIVE for ATG unless hereunder specified. The gNB reference location of the serving cell and neighbour cell(s) provided in *SIB22* can be used for the UE to perform the idle/inactive measurement and mobility. + +The UE can determine whether a network is for ATG connectivity implicitly by the existence of *cellBarredATG* in SIB1. + +### 16.19.3.2 Mobility in RRC\_CONNECTED + +#### 16.19.3.2.1 Handover + +The same principle as described in 9.2.3.2 applies to ATG unless hereunder specified. + +#### 16.19.3.2.2 Conditional Handover + +The same principle as described in 9.2.3.4 applies to ATG unless hereunder specified. + +ATG supports the following additional trigger conditions upon which UE may execute CHO to a candidate cell, as defined in TS 38.331 [12]: + +- The RRM measurement-based event A4; +- A location-based trigger condition. + +A location-based trigger condition is always configured together with one of the measurement-based trigger conditions (CHO events A3/A4/A5) as defined in TS 38.331 [12]. + +## 16.20 Support of AI/ML for NG-RAN + +### 16.20.1 General + +Support of AI/ML for NG-RAN, as a RAN internal function, is used to facilitate Artificial Intelligence (AI) and Machine Learning (ML) techniques in NG-RAN. + +The objective of AI/ML for NG-RAN is to improve network performance and user experience, through analysing the data collected and autonomously processed by the NG-RAN, which can yield further insights, e.g., for Network Energy Saving, Load Balancing, Mobility Optimization. + +### 16.20.2 Mechanisms and Principles + +Support of AI/ML in NG-RAN requires inputs from neighbour NG-RAN nodes (e.g. predicted information, feedback information, measurements) and/or UEs (e.g. measurement results). + +Signalling procedures used for the exchange of information to support AI/ML in NG-RAN, are use case and data type agnostic, which means that the intended usage of the data exchanged via these procedures (e.g., input, output, feedback) is not indicated. + +AI/ML algorithms and models are out of 3GPP scope, and the details of model performance feedback are also out of 3GPP scope. + +Support of AI/ML in NG-RAN does not apply to ng-eNB. + +For the deployment of AI/ML in NG-RAN, the following scenarios may be supported: + +- AI/ML Model Training is located in the OAM and AI/ML Model Inference is located in the NG-RAN node; +- AI/ML Model Training and AI/ML Model Inference are both located in the NG-RAN node. + +The following information can be configured to be reported by an NG-RAN node: + +- Predicted resource status information; +- UE performance feedback; +- Measured UE trajectory; +- Energy Cost (EC). + +The collection and reporting are configured through the Data Collection Reporting Initiation procedure, while the actual reporting is performed through the Data Collection Reporting procedure. + +The collection of measured UE trajectory and UE performance feedback is triggered at successful Handover execution. + +Cell-based UE trajectory prediction, which can be used e.g. for the Mobility Optimization use case, is transferred to the target NG-RAN node via the Handover Preparation procedure to provide information for e.g. subsequent mobility decisions. Cell-based UE trajectory prediction is limited to the first-hop target NG-RAN node. + +## 16.21 Multi-path Relay + +### 16.21.1 General + +In multi-path relay scenario, a MP Remote UE is connected to a single gNB via one direct path and one indirect path while the MP Remote UE is in RRC\_CONNECTED state. For the indirect path, both L2 and L3 MP Relay architectures are supported. The L3 MP Relay architecture is transparent to the serving NG-RAN of the MP Relay UE, except for controlling sidelink resources. In the case of MP Remote UE using SL indirect path, mode 1 resource allocation is supported only for intra-DU case, with the SR/BSR and grant sent on the direct path. + +In multi-path relay, the interface between MP Remote UE and MP Relay UE can be either PC5 or N3C. When the interface between MP Remote UE and MP Relay UE is N3C interface, the relationship of MP Remote UE and MP Relay UE is pre-configured or static, and it is up to implementation how to pre-configure or make it static. + +Multi-path relay supports MP Remote UE and MP Relay UE when they are in the intra-gNB, and PCell is always on the direct path. + +Multi-path relay is supported in the following cell deployment scenarios: + +- The MP Relay UE and MP Remote UE are served by the same cell; +- The MP Relay UE and MP Remote UE are served by different intra-frequency cells of the same gNB; +- The MP Relay UE and MP Remote UE are served by different inter-frequency cells of the same gNB. + +Multi-path relay is supported in the following sidelink scenarios: + +- Sidelink TX/RX and Uu link share the same carrier at the MP Remote UE; +- Sidelink TX/RX and Uu link use different carriers at the MP Remote UE; +- Sidelink TX/RX and Uu link share the same carrier at the MP Relay UE; +- Sidelink TX/RX and Uu link use different carriers at the MP Relay UE. + +## 16.21.2 Protocol Architecture + +From L2 MP Remote UE perspective, three bearer types exist: direct bearer, indirect bearer, and split bearer. For direct bearer, only Uu radio resources are involved, and for indirect bearer, only PC5 or N3C radio resources are involved. For split bearer, both Uu and PC5/N3C radio resources are involved. + +### 16.21.2.1 L2 MP Relay using SL indirect path + +For multi-path relay operation by using SL indirect path, the protocol stacks for the user plane and control plane of L2 MP Relay architecture are illustrated in Figure 16.21.2.1-1, 16.21.2.1-2. + +If PC5 interface is used between L2 MP Remote UE and L2 MP Relay UE, the SRAP sublayer is placed above the RLC sublayer for both CP and UP at both PC5 interface and Uu interface of the indirect path. For the direct path, the Uu SDAP, PDCP, RLC, MAC, PHY, and RRC are terminated at gNB and MP Remote UE. But for the indirect path, only the Uu SDAP, PDCP and RRC are terminated at gNB and MP Remote UE, while SRAP, RLC, MAC, and PHY are terminated in each hop (i.e., the link between L2 MP Remote UE and L2 MP Relay UE and the link between L2 MP Relay UE and the gNB). If duplication is not activated for a split bearer, in UL, a PDCP entity in the L2 MP Remote UE delivers a PDCP PDU to either a Uu RLC entity or a PC5 RLC entity having an SRAP entity over it. If duplication is activated for a split bearer, a PDCP entity in the L2 MP Remote UE delivers the same PDCP PDU to the Uu RLC entity and the PC5 RLC entity. + +![Figure 16.21.2.1-1: User plane protocol stack for L2 Multi-path Relay using SL indirect path. The diagram shows three protocol stacks. The left stack represents the gNB, with layers SDAP, PDCP, RLC, MAC, and PHY. The middle stack represents the L2 MP Relay UE, with layers SRAP, RLC, MAC, and PHY. The right stack represents the L2 MP Remote UE, with layers SDAP, PDCP, RLC, MAC, and PHY. The stacks are connected by lines representing the interfaces: Uu between gNB and Relay UE, and PC5 between Relay UE and Remote UE. The Remote UE has two additional blocks at the top representing higher layers.](2aea72b147efb82b46a78aaea9f1ac22_img.jpg) + +Figure 16.21.2.1-1: User plane protocol stack for L2 Multi-path Relay using SL indirect path. The diagram shows three protocol stacks. The left stack represents the gNB, with layers SDAP, PDCP, RLC, MAC, and PHY. The middle stack represents the L2 MP Relay UE, with layers SRAP, RLC, MAC, and PHY. The right stack represents the L2 MP Remote UE, with layers SDAP, PDCP, RLC, MAC, and PHY. The stacks are connected by lines representing the interfaces: Uu between gNB and Relay UE, and PC5 between Relay UE and Remote UE. The Remote UE has two additional blocks at the top representing higher layers. + +Figure 16.21.2.1-1: User plane protocol stack for L2 Multi-path Relay using SL indirect path + +![Control plane protocol stack for L2 Multi-path Relay using SL indirect path. The diagram shows a stack of protocol layers for a Remote UE, a Relay UE, and a gNB. The Remote UE and Relay UE are connected via an SL indirect path, while the Relay UE is connected to the gNB via a Uu interface. The stack includes RRC, SDAP, PDCP, RLC, MAC, and PHY layers.](59b0fc7f07c6794ca85c36c2d06a5fd9_img.jpg) + +Control plane protocol stack for L2 Multi-path Relay using SL indirect path. The diagram shows a stack of protocol layers for a Remote UE, a Relay UE, and a gNB. The Remote UE and Relay UE are connected via an SL indirect path, while the Relay UE is connected to the gNB via a Uu interface. The stack includes RRC, SDAP, PDCP, RLC, MAC, and PHY layers. + +Figure 16.21.2.1-2: Control plane protocol stack for L2 Multi-path Relay using SL indirect path + +### 16.21.2.2 L2 MP Relay using N3C indirect path + +For the multi-path relay using N3C indirect path between the Remote UE and Relay UE, the protocol stacks for the user plane and control plane of L2 MP Relay architecture are illustrated in Figure 16.21.2.2-1 and Figure 16.21.2.2-2. The L2 MP Relay UE and the L2 MP Remote UE are connected via a N3C interface. + +In the multi-path relay using N3C indirect path, the SRAP sublayer does not exist on the protocol stack. Without the SRAP entity between L2 MP Remote UE and L2 MP Relay UE, the Uu SDAP, PDCP, and RRC are terminated at gNB and L2 MP Remote UE. While RLC, MAC, and PHY are terminated in Uu hop. An UL PDCP PDU in the L2 MP Remote UE can be delivered to a Uu RLC entity and an intended PDCP entity or RLC entity in the L2 MP Relay UE. It is supported for more than one RB over the Uu link of the L2 MP Relay UE by configuring 1:1 bearer mapping between the Radio bearer in the L2 MP Remote UE and Uu Relay RLC channel in the L2 MP Relay UE. The Uu Relay RLC channels for the PDU delivery of the L2 MP Relay UE's local traffic and relay traffic are configured differently. Bearer identification except LCID is not needed in L2 PDU over the Uu link. If the split bearer is configured and the PDCP PDU duplication is activated on the PDCP entity, the duplicated PDCP PDUs are delivered via both direct path and indirect path. + +![User plane protocol stack for L2 Multi-path Relay using N3C indirect path. The diagram shows a stack of protocol layers for a Remote UE, a Relay UE, and a gNB. The Remote UE and Relay UE are connected via an N3C interface, while the Relay UE is connected to the gNB via a Uu interface. The stack includes SDAP, PDCP, RLC, MAC, and PHY layers. Notably, the RRC layer is absent in the Remote UE's stack for the user plane.](dd2ddef02cef83a06acfc3e710b36564_img.jpg) + +User plane protocol stack for L2 Multi-path Relay using N3C indirect path. The diagram shows a stack of protocol layers for a Remote UE, a Relay UE, and a gNB. The Remote UE and Relay UE are connected via an N3C interface, while the Relay UE is connected to the gNB via a Uu interface. The stack includes SDAP, PDCP, RLC, MAC, and PHY layers. Notably, the RRC layer is absent in the Remote UE's stack for the user plane. + +Figure 16.21.2.2-1: User plane protocol stack for L2 Multi-path Relay using N3C indirect path + +![Figure 16.21.2.2-2: Control plane protocol stack for L2 Multi-path Relay using N3C indirect path. The diagram shows a stack of protocol layers for a User Equipment (UE) and a gNB. The UE stack includes RRC, SDAP, PDCP, RLC, MAC, and PHY layers. The gNB stack includes RRC, SDAP, PDCP, RLC, MAC, and PHY layers. The UE is connected to the gNB via a direct path (RRC, SDAP, PDCP, RLC, MAC, PHY) and an indirect path (RRC, SDAP, PDCP, RLC, MAC, PHY) through a relay node. The relay node is shown as a stack of RRC, SDAP, PDCP, RLC, MAC, and PHY layers. The direct path is highlighted in the diagram.](87f625baee73880fd5464a9f60b1b3b8_img.jpg) + +Figure 16.21.2.2-2: Control plane protocol stack for L2 Multi-path Relay using N3C indirect path. The diagram shows a stack of protocol layers for a User Equipment (UE) and a gNB. The UE stack includes RRC, SDAP, PDCP, RLC, MAC, and PHY layers. The gNB stack includes RRC, SDAP, PDCP, RLC, MAC, and PHY layers. The UE is connected to the gNB via a direct path (RRC, SDAP, PDCP, RLC, MAC, PHY) and an indirect path (RRC, SDAP, PDCP, RLC, MAC, PHY) through a relay node. The relay node is shown as a stack of RRC, SDAP, PDCP, RLC, MAC, and PHY layers. The direct path is highlighted in the diagram. + +Figure 16.21.2.2-2: Control plane protocol stack for L2 Multi-path Relay using N3C indirect path + +### 16.21.3 Control plane procedure for multi-path relaying + +#### 16.21.3.1 Path Management + +The L2 MP Remote UE needs to establish both a direct path and an indirect path. The L2 MP Remote UE adds the indirect path using PC5 link on top of the only direct path under the same gNB. And also, the L2 MP Remote UE using PC5 link adds the direct path on top of the only indirect path under the same gNB. + +Meanwhile, the L2 MP Remote UE adds the indirect path using N3C link on the only direct path under the same gNB. But it is not allowed that the L2 MP Remote UE using N3C link adds the direct path on the indirect path. The MP Relay UE using N3C indirect path is restricted to serve only one MP Remote UE. + +For L2 MP Remote UE, only a single cell group is configured (i.e., only MCG is configured for the direct path and indirect path). The primary path of split SRB1 and SRB2 is always configured on direct path. In the L2 MP Remote UE, non-split SRB1/2 is allowed to be configured only on direct path. + +Figure 16.21.3.1-1 describes the procedures for the indirect path addition on the direct path for the L2 MP relaying. This procedure is applicable to the L2 MP Remote UE using SL indirect path or N3C indirect path except step 5. + +![Sequence diagram showing the procedure for indirect path addition. Lifelines are L2 MP Remote UE, L2 MP Relay UE, and gNB. Steps include data transmission on direct path, reporting candidate relay UEs, gNB decision, RRCReconfiguration messages to relay and remote UEs, PC5 link establishment, and RRCReconfigurationComplete messages.](38c0f202ad5767f3df428353919fa90a_img.jpg) + +``` + +sequenceDiagram + participant Remote as L2 MP Remote UE + participant Relay as L2 MP Relay UE + participant gNB as gNB + + Note over Remote, gNB: 0. Data transmission/reception via direct path + Remote->>gNB: 1. Measurement Report (Relay UE ID, Cell ID) + Note over gNB: 2. gNB decides to add indirect path + gNB->>Relay: 3. RRCReconfiguration + Relay-->>gNB: RRCReconfigurationComplete + gNB->>Remote: 4. RRCReconfiguration + Remote->>Relay: 5. PC5 Link Establishment + Remote->>gNB: 6a. RRCReconfigurationComplete (Direct Path) + Remote->>Relay: 6b. RRCReconfigurationComplete (Indirect Path) + Relay->>gNB: 6b. RRCReconfigurationComplete (Forwarded) + Note over Remote, gNB: 7. Data transmission/reception via both paths + +``` + +Sequence diagram showing the procedure for indirect path addition. Lifelines are L2 MP Remote UE, L2 MP Relay UE, and gNB. Steps include data transmission on direct path, reporting candidate relay UEs, gNB decision, RRCReconfiguration messages to relay and remote UEs, PC5 link establishment, and RRCReconfigurationComplete messages. + +**Figure 16.21.3.1-1: Procedure for indirect path addition on top of direct path** + +0. The L2 MP Remote UE performs data transmission and reception by using direct path on PCell. +1. If the L2 MP Remote UE will be connected with L2 MP Relay UE using PC5 link, the L2 MP Remote UE reports at least the list of the candidate L2 MP Relay UE ID and the cell ID of the candidate L2 MP Relay UEs. + +Meanwhile, if the MP Remote UE will be connected with L2 MP Relay UE using N3C link, the MP Remote UE reports at least the list of the C-RNTI and the cell ID of the connected candidate MP Relay UEs. + +NOTE 1: The C-RNTI and cell ID of MP Relay UE using N3C link can be reported only if the secure connection between MP Remote UE and MP Relay UE is established. + +2. The gNB decides to add the indirect path for the L2 MP Remote UE. The cell serving the direct path and the cell serving the L2 MP Relay UE on the indirect path belong to the same gNB but can be same or different. +3. The gNB sends an *RRCReconfiguration* message to the L2 MP Relay UE to configure the indirect path of the L2 MP Remote UE, if the L2 MP Relay UE is in RRC\_CONNECTED. + +4. The gNB sends the *RRCReconfiguration* message to the L2 MP Remote UE. + +5. The L2 MP Remote UE establishes a PC5 unicast link with the target L2 MP Relay UE. + +NOTE 2: For the N3C indirect path addition, step 5 is omitted. It is L2 MP Remote UE's implementation how to make N3C indirect path between L2 MP Remote UE and L2 MP Relay UE. + +- 6a. The L2 MP Remote UE sends the *RRCReconfigurationComplete* message to the gNB at least via the direct path in order to complete the indirect path addition procedure. +- 6b. If a split SRB1 with duplication is configured, the L2 MP Remote UE also sends the *RRCReconfigurationComplete* message to the gNB via the indirect path served by the L2 MP Relay UE. + +NOTE 3: Step 5 can be executed after step 6a. Step 5 is independent of step 6a. + +7. The L2 MP Remote UE performs data transmission and reception by using both the direct path on PCell and the indirect path served by a L2 MP Relay UE. + +In the case that the selected L2 MP Relay UE for indirect path addition is in RRC\_IDLE or RRC\_INACTIVE, after receiving the path addition command, the L2 MP Remote UE should trigger the L2 MP Relay UE in RRC\_IDLE or + +RRC\_INACTIVE to move to RRC\_CONNECTED. If the L2 MP Remote UE and L2 MP Relay UE are connected by using N3C link, it is L2 MP Remote/Relay UE's implementation on how to trigger the RRC\_IDLE/RRC\_INACTIVE L2 MP Relay UE to initiate RRC connection establishment procedure. + +If the split SRB1 with duplication is not configured at the L2 MP Remote UE, the L2 MP Remote UE using SL indirect path sends PC5-RRC message to the L2 MP Relay UE. Upon receiving the PC5-RRC message, the L2 MP Relay UE in RRC\_IDLE or RRC\_INACTIVE initiates a Uu RRC connection establishment or an RRC connection resume. + +If the split SRB1 with duplication is configured at the L2 MP Remote UE, the L2 MP Relay UE in RRC\_IDLE or RRC\_INACTIVE received *RRCReconfigurationComplete* message from the L2 MP Remote UE may a Uu RRC connection establishment or an RRC connection resume for sending the *RRCReconfigurationComplete* message to the gNB. + +Figure 16.21.3.1-2 describes the procedures for the indirect path change under the single direct path in the L2 MP Relay operation. This procedure is applicable to the L2 MP Remote UE using SL indirect path or N3C indirect path except step 5. + +![Sequence diagram illustrating the procedure for indirect path change under a single procedure. The diagram shows four vertical lifelines representing the L2 MP Remote UE, Source L2 MP Relay UE, Target L2 MP Relay UE, and gNB. The sequence of messages is: 1. The Remote UE sends a measurement report to the gNB. 2. The gNB sends an RRCReconfiguration message to the Source Relay UE. 3. The Source Relay UE sends an RRCReconfiguration message to the Remote UE. 4. The Remote UE sends an RRCReconfigurationComplete message to the Source Relay UE. 5. The Source Relay UE sends an RRCReconfiguration message to the Target Relay UE. 6. The Target Relay UE sends an RRCReconfigurationComplete message to the gNB. 7. The gNB sends an RRCReconfiguration message to the Remote UE. 8. The Remote UE sends an RRCReconfigurationComplete message to the gNB.](76f4756bc4fb7d52be4ad051adf9bd89_img.jpg) + +Sequence diagram illustrating the procedure for indirect path change under a single procedure. The diagram shows four vertical lifelines representing the L2 MP Remote UE, Source L2 MP Relay UE, Target L2 MP Relay UE, and gNB. The sequence of messages is: 1. The Remote UE sends a measurement report to the gNB. 2. The gNB sends an RRCReconfiguration message to the Source Relay UE. 3. The Source Relay UE sends an RRCReconfiguration message to the Remote UE. 4. The Remote UE sends an RRCReconfigurationComplete message to the Source Relay UE. 5. The Source Relay UE sends an RRCReconfiguration message to the Target Relay UE. 6. The Target Relay UE sends an RRCReconfigurationComplete message to the gNB. 7. The gNB sends an RRCReconfiguration message to the Remote UE. 8. The Remote UE sends an RRCReconfigurationComplete message to the gNB. + +**Figure 16.21.3.1-2: Procedure for indirect path change under a single procedure** + +0. The L2 MP Remote UE performs data transmission and reception by using both the direct path on PCell and the indirect path served by a source L2 MP Relay UE. +1. The L2 MP Remote UE and the L2 MP Relay UE perform measurements based on measurement configuration. When the measurement reporting is triggered, the L2 MP Remote UE using SL indirect link reports at least signal strength (e.g., SD-RSRP/SL-RSRP) of the serving indirect path, the list of the candidate L2 MP Relay UE ID and the cell ID of the candidate L2 MP Relay UEs. Meanwhile, the MP Remote UE using N3C link reports at least the list of the C-RNTI and the cell ID of the connected candidate MP Relay UEs. +2. The gNB decides to change the indirect path of L2 MP Remote UE from the source L2 MP Relay UE to a target L2 MP Relay UE. The cell serving the direct path and the cell serving the source/target L2 MP Relay UE on the indirect path belong to the same gNB but can be same or different. +- 3a. The gNB sends an *RRCReconfiguration* message to the source L2 MP Relay UE to release the indirect path of the L2 MP Remote UE. +- 3b. The gNB sends an *RRCReconfiguration* message to the target L2 MP Relay UE to add the indirect path for the L2 MP Remote UE. + +4. The gNB sends the *RRCReconfiguration* message to the L2 MP Remote UE on the direct path and/or the indirect path for indirect path change. If SRB1 is configured either direct path or indirect path to the L2 MP Remote UE, the *RRCReconfiguration* message is sent via one of the path on which the SRB1 is configured. If split SRB1 is configured, it is up to gNB implementation whether the *RRCReconfiguration* is sent via one of the paths or both paths. + +5. The L2 MP Remote UE establishes a PC5-RRC connection with the target L2 MP Relay UE for using SL indirect path. + +NOTE 4: For the N3C indirect path addition, step 5 is omitted. It is L2 MP Remote UE's implementation how to make N3C indirect path between L2 MP Remote UE and L2 MP Relay UE. + +6a. The L2 MP Remote UE sends the *RRCReconfigurationComplete* message to the gNB at least via the direct path in order to complete the indirect path change procedure. + +NOTE 5: Step 5 can be executed after step 6a. Step 5 is independent of step 6a. + +6b. If a split SRB1 with duplication is configured, the L2 MP Remote UE also sends the *RRCReconfigurationComplete* message to the gNB via the indirect path served by the target L2 MP Relay UE. + +7. The L2 MP Remote UE performs data transmission and reception by using both the direct path on PCell and the indirect path served by a target L2 MP Relay UE. + +In the case that the selected target L2 MP Relay UE for indirect path change is in RRC\_IDLE or RRC\_INACTIVE, after receiving the path change command, the L2 MP Remote UE should trigger the target L2 MP Relay UE in RRC\_IDLE or RRC\_INACTIVE to be in RRC\_CONNECTED. If the target L2 MP Relay UE is not in RRC\_CONNECTED in step 3, the gNB sends an *RRCReconfiguration* message to the target L2 MP Relay UE after the target L2 MP Relay UE enters RRC\_CONNECTED. + +If the split SRB1 with duplication is not configured at the L2 MP Remote UE, the L2 MP Remote UE sends the *RRCReconfigurationComplete* message only on the direct path in Step 6a. The L2 MP Remote UE using SL indirect path can send a PC5-RRC message to the target L2 MP Relay UE in RRC\_IDLE or RRC\_INACTIVE after or during Step 5. The target L2 MP Relay UE in RRC\_IDLE or RRC\_INACTIVE initiates an RRC connection establishment or an RRC connection resume upon receiving the PC5-RRC message from the L2 MP Remote UE. If the target L2 MP Relay UE is in RRC\_IDLE or RRC\_INACTIVE, the *RRCReconfigurationComplete* message at Step 6b is sent to the gNB after the target L2 MP Relay UE enters RRC\_CONNECTED. + +If the split SRB1 with duplication is configured at the L2 MP Remote UE, the target L2 MP Relay UE in RRC\_IDLE or RRC\_INACTIVE receiving *RRCReconfigurationComplete* message from the L2 MP Remote UE initiates an RRC connection establishment or an RRC connection resume for sending the *RRCReconfigurationComplete* message to the gNB at Step 6b. + +Figure 16.21.3.1-3 describes the procedures for the direct path addition on top of the indirect path for the L2 MP Relay operation. This procedure is only applicable to the L2 MP Remote UE using SL indirect path. + +![Sequence diagram illustrating the procedure for direct path addition on top of indirect path. The diagram shows three vertical lifelines: L2 MP Remote UE (left), gNB (middle), and L2 MP Relay UE (right). The sequence of messages is: 1. gNB sends a message to Remote UE via Relay UE (dashed arrow). 2. gNB sends a message to Remote UE via Relay UE (dashed arrow). 3. gNB sends a message to Remote UE via Relay UE (solid arrow). 4. gNB sends a message to Remote UE via Relay UE (solid arrow). 5. gNB sends a message to Remote UE via Relay UE (solid arrow). 6. gNB sends a message to Remote UE via Relay UE (dashed arrow). 7. gNB sends a message to Remote UE via Relay UE (dashed arrow). 8. gNB sends a message to Remote UE via Relay UE (dashed arrow). 9. gNB sends a message to Remote UE via Relay UE (dashed arrow).](b437cd7078b36507e5d918fe6224e6dd_img.jpg) + +Sequence diagram illustrating the procedure for direct path addition on top of indirect path. The diagram shows three vertical lifelines: L2 MP Remote UE (left), gNB (middle), and L2 MP Relay UE (right). The sequence of messages is: 1. gNB sends a message to Remote UE via Relay UE (dashed arrow). 2. gNB sends a message to Remote UE via Relay UE (dashed arrow). 3. gNB sends a message to Remote UE via Relay UE (solid arrow). 4. gNB sends a message to Remote UE via Relay UE (solid arrow). 5. gNB sends a message to Remote UE via Relay UE (solid arrow). 6. gNB sends a message to Remote UE via Relay UE (dashed arrow). 7. gNB sends a message to Remote UE via Relay UE (dashed arrow). 8. gNB sends a message to Remote UE via Relay UE (dashed arrow). 9. gNB sends a message to Remote UE via Relay UE (dashed arrow). + +**Figure 16.21.3.1-3: Procedure for direct path addition on top of indirect path** + +0. The L2 MP Remote UE performs data transmission and reception by using indirect path via PC5 link. +1. The L2 MP Remote UE perform measurements based on measurement configuration. When the measurement reporting is triggered, the L2 MP Remote UE reports at least the Uu signal strength of the serving cell and neighbour cells with the cell IDs (i.e., NCGI/NCI). +2. The gNB decides to add the direct path for the L2 MP Remote UE. The cell serving the direct path and the cell serving the L2 MP Relay UE on the indirect path belong to the same gNB but can be same or different. +3. The gNB sends an *RRReconfiguration* message to the L2 MP Relay UE to update the indirect path configuration, if necessary. +4. The gNB sends the *RRReconfiguration* message to the L2 MP Remote UE via the L2 MP Relay UE. The contents in the *RRReconfiguration* message includes at least a target cell within direct path addition configuration. +5. The L2 MP Remote UE synchronizes to DL of the target cell serving the direct path and performs random access procedure towards the cell serving the direct path. The L2 MP Remote UE configures the target cell as PCell. +- 6a. The L2 MP Remote UE sends the *RRReconfigurationComplete* message to the gNB at least via the direct path in order to complete the direct path addition procedure. +- 6b. If a split SRB1 with duplication is configured, the L2 MP Remote UE also sends the *RRReconfigurationComplete* message to the gNB via the indirect path served by the L2 MP Relay UE. +7. The L2 MP Remote UE performs data transmission and reception by using both the direct path on PCell and the indirect path served by a L2 MP Relay UE. + +Figure 16.21.3.1-4 describes the procedures for the direct path change on top of the indirect path for the L2 MP Relay operation. This procedure is only applicable to the L2 MP Remote UE using SL indirect path. + +![Sequence diagram illustrating the procedure for direct path change under a single procedure. The diagram shows three vertical lifelines: a source gNB (left), a target gNB (middle), and an L2 MP Remote UE (right). The L2 MP Remote UE is connected to the source gNB via a direct path and to the target gNB via an indirect path through an L2 MP Relay UE. The sequence of messages is: 1. The L2 MP Remote UE sends a measurement report to the source gNB. 2. The source gNB sends an RRCReconfiguration message to the L2 MP Relay UE. 3. The source gNB sends an RRCReconfiguration message to the L2 MP Remote UE. 4. The L2 MP Remote UE synchronizes to the target gNB and performs random access. 5. The L2 MP Remote UE sends an RRCReconfigurationComplete message to the source gNB. 6a. The L2 MP Remote UE sends an RRCReconfigurationComplete message to the target gNB. 6b. The L2 MP Remote UE sends an RRCReconfigurationComplete message to the source gNB via the L2 MP Relay UE. 7. The L2 MP Remote UE performs data transmission and reception using both the direct path on the target gNB and the indirect path served by the L2 MP Relay UE.](5d819f259411162c4e3371915818ae22_img.jpg) + +Sequence diagram illustrating the procedure for direct path change under a single procedure. The diagram shows three vertical lifelines: a source gNB (left), a target gNB (middle), and an L2 MP Remote UE (right). The L2 MP Remote UE is connected to the source gNB via a direct path and to the target gNB via an indirect path through an L2 MP Relay UE. The sequence of messages is: 1. The L2 MP Remote UE sends a measurement report to the source gNB. 2. The source gNB sends an RRCReconfiguration message to the L2 MP Relay UE. 3. The source gNB sends an RRCReconfiguration message to the L2 MP Remote UE. 4. The L2 MP Remote UE synchronizes to the target gNB and performs random access. 5. The L2 MP Remote UE sends an RRCReconfigurationComplete message to the source gNB. 6a. The L2 MP Remote UE sends an RRCReconfigurationComplete message to the target gNB. 6b. The L2 MP Remote UE sends an RRCReconfigurationComplete message to the source gNB via the L2 MP Relay UE. 7. The L2 MP Remote UE performs data transmission and reception using both the direct path on the target gNB and the indirect path served by the L2 MP Relay UE. + +**Figure 16.21.3.1-4: Procedure for direct path change under a single procedure** + +0. The L2 MP Remote UE performs data transmission and reception by using both the direct path on the source PCell and the indirect path served by a L2 MP Relay UE. +1. The L2 MP Remote UE and the L2 MP Relay UE perform measurements based on measurement configuration. The L2 MP Remote UE may report measurement results. +2. The gNB decides to change the direct path of the L2 MP Remote UE from the PCell (i.e. source PCell) to a new cell (i.e. target PCell). The source/target PCell serving the old/new direct path and the cell serving the L2 MP Relay UE on the indirect path belong to the same gNB but can be same or different. +3. The gNB sends an *RRCReconfiguration* message to the L2 MP Relay UE to update the indirect path configuration, if necessary. +4. The gNB sends the *RRCReconfiguration* message to the L2 MP Remote UE on the direct path and/or the indirect path for direct path change. +5. The L2 MP Remote UE synchronizes to DL of the target PCell serving the new direct path and performs random access procedure towards the target PCell serving the new direct path. +- 6a. The L2 MP Remote UE sends the *RRCReconfigurationComplete* message to the gNB at least via the direct path in order to complete the direct path change procedure. +- 6b. If a split SRB1 with duplication is configured, the L2 MP Remote UE also sends the *RRCReconfigurationComplete* message to the gNB via the indirect path served by the L2 MP Relay UE. +7. The L2 MP Remote UE performs data transmission and reception by using both the direct path on the target PCell and the indirect path served by a L2 MP Relay UE. + +If the direct path addition/change is failed, the L2 U2N Remote UE always shall trigger *RRCReestablishment*. + +### 16.21.3.2 Path Failure Report + +The L2 MP Remote UE in RRC\_CONNECTED performs Uu RLM (as described in clause 9.2.7). + +When the L2 MP Remote UE detects Uu Radio Link Failure (RLF) on the direct path, the L2 MP Remote UE triggers path failure reporting through the indirect path via a RRC message if split SRB1 is configured and the indirect path is not suspended. Otherwise, RRC connection re-establishment is initiated. + +When the L2 MP Remote UE using PC5 indirect path detects PC5 Radio Link Failure (RLF) and/or Uu link failure on the indirect path, the L2 MP Remote UE triggers path failure reporting through the direct path via a RRC message, if the direct path is not suspended. + +When the L2 MP Remote UE using N3C indirect path detects N3C link failure and/or Uu link failure on the indirect path, the L2 MP Remote UE triggers path failure reporting through the direct path via a RRC message, if the direct path is not suspended. + +### 16.21.3.3 System Information + +The L2 MP Remote UE can acquire any necessary SIB(s) over Uu interface or indirect path. If common search space for system information is configured with the active BWP on PCell, the L2 MP Remote UE can perform direct system information acquisition on PCell. The L2 MP Remote UE can also receive system information at least PBCH/MIB on the direct path and directly acquires SFN from MIB on the direct path. Besides, the L2 MP Remote UE can receive the system information via dedicated RRC signalling via SRB1. + +--- + +## 17 Interference Management + +### 17.1 Remote Interference Management + +The atmospheric ducting phenomenon, caused by lower densities at higher altitudes in the Earth's atmosphere, causes a reduced refractive index, causing the signals to bend back towards the Earth. A signal trapped in the atmospheric duct can reach distances far greater than normal. In TDD networks with the same UL/DL slot configuration, and in the absence of atmospheric ducting, a guard period is used to avoid the interference between UL and DL transmissions in different cells. However, when the atmospheric ducting phenomenon happens, radio signals can travel a relatively long distance, and the propagation delay exceeds the guard period. Consequently, the DL signals of an aggressor cell can interfere with the UL signals of a victim cell that is far away from the aggressor. Such interference is termed as remote interference. The further the aggressor is to the victim, the more UL symbols of the victim will be impacted. + +A remote interference scenario may involve a number of victim and aggressor cells, where the gNBs execute Remote Interference Management (RIM) coordination on behalf of their respective cells. Aggressor and victim gNBs can be grouped into semi-static sets, where each cell is assigned a set ID, and is configured with a RIM Reference Signal (RIM-RS) and the radio resources associated with the set ID. Each aggressor gNB can be configured with multiple set IDs and each victim gNB can be configured with multiple set IDs, whereas each cell can have at most one victim set ID and one aggressor set ID. Consequently, each gNB can be an aggressor and a victim at the same time. + +To mitigate remote interference, the network enables RIM frameworks for coordination between victim and aggressor gNBs. The coordination communication in RIM frameworks can be wireless- or backhaul-based. The backhaul-based RIM framework uses a combination of wireless and backhaul communication, while in the wireless framework, the communication is purely wireless. + +In both frameworks, all gNBs in a victim set simultaneously transmit an identical RIM reference signal carrying the victim set ID over the air. + +In the wireless framework, upon reception of the RIM reference signal from the victim set, aggressor gNBs undertake RIM measures, and send back a RIM reference signal carrying the aggressor set ID. The RIM reference signal sent by the aggressor is able to provide information whether the atmospheric ducting phenomenon exists. The victim gNBs realize the atmospheric ducting phenomenon have ceased upon not receiving any reference signal sent from aggressors. + +In the RIM backhaul framework, upon reception of the RIM reference signal from the victim set, aggressor gNBs undertake RIM measures, and establish backhaul coordination towards the victim gNB set. The backhaul messages are sent from individual aggressor gNBs to individual victim gNB, where the signalling is transparent to the core network. The RIM backhaul messages from aggressor to victim gNBs carry the indication about the detection or disappearance of RIM reference signal. Based on the indication from the backhaul message, the victim gNBs realize whether the atmospheric ducting and the consequent remote interference have ceased. + +In both frameworks, upon realizing that the atmospheric ducting has disappeared, the victim gNBs stop transmitting the RIM reference signal. + +## 17.2 Cross-Link Interference Management + +When different TDD DL/UL patterns are used between neighbouring cells, UL transmission in one cell may interfere with DL reception in another cell: this is referred to as Cross Link Interference (CLI). + +To mitigate CLI, gNBs can exchange and coordinate their intended TDD DL-UL configurations over Xn and F1 interfaces; and the victim UEs can be configured to perform CLI measurements. There are two types of CLI measurements: + +- SRS-RSRP measurement in which the UE measures SRS-RSRP over SRS resources of aggressor UE(s); +- CLI-RSSI measurement in which the UE measures the total received power observed over RSSI resources. + +Layer 3 filtering applies to CLI measurement results and both event triggered and periodic reporting are supported. + +--- + +## 18 Small Data Transmission + +### 18.0 General + +Small Data Transmission (SDT) is a procedure allowing data and/or signalling transmission while remaining in RRC\_INACTIVE state (i.e. without transitioning to RRC\_CONNECTED state). SDT is enabled on a radio bearer basis and can be initiated either by the UE in case of MO-SDT (Mobile Originated SDT) or by the network in case of MT-SDT (Mobile Terminated SDT). MO-SDT is initiated by the UE only if less than or equal to a configured amount of UL data awaits transmission across all radio bearers for which SDT is enabled, the DL RSRP is above a configured threshold, and a valid SDT resource is available as specified in clause 5.27.1 of TS 38.321 [6]. MT-SDT is initiated by the network with an indication to the UE in a paging message when DL data awaits transmission for radio bearers configured for SDT; based on the indication, the UE initiates the MT-SDT only if the DL RSRP is above a configured threshold as specified in clause 5.27.1 of TS 38.321 [6]. When MT-SDT is initiated by the UE, a resume cause indicating MT-SDT is included in the *RRRCResumeRequest/RRRCResumeRequest1*. Maximum duration the SDT procedure can last is dictated by a SDT failure detection timer that is configured by the network (see clause 6.2.2 of TS 38.331 [12]). Network can enable MO-SDT, MT-SDT, or both in a cell. + +SDT procedure is initiated with either a transmission over RACH (configured via system information) or over Type 1 CG resources (configured via dedicated signalling in *RRRCRelease*). The SDT resources can be configured on initial BWP for both RACH and CG. RACH and CG resources for SDT can be configured on either or both of NUL and SUL carriers. The CG resources for SDT are valid only within the PCell of the UE when the *RRRCRelease* with suspend indication is received. CG resources are associated with one or multiple SSB(s). For RACH, the network can configure 2-step and/or 4-step RA resources for MO-SDT. When both 2-step and 4-step RA resources for MO-SDT are configured, the UE selects the RA type according to clause 9.2.6. If MT-SDT procedure is initiated over RACH, only the RACH resources not configured for SDT can be used by the UE. CFRA is not supported for SDT over RACH. + +Once initiated, the SDT procedure is either: + +- successfully completed after the UE is directed to RRC\_IDLE (via *RRRCRelease*) or to continue in RRC\_INACTIVE (via *RRRCRelease* or *RRRCReject*) or to RRC\_CONNECTED (via *RRRCResume* or *RRRCSetup*); or +- unsuccessfully completed upon cell re-selection, expiry of the SDT failure detection timer, a MAC entity reaching a configured maximum PRACH preamble transmission threshold, an RLC entity reaching a configured maximum retransmission threshold, or integrity check failure while SDT procedure is ongoing, or expiry of SDT-specific timing alignment timer or *configuredGrantTimer* while SDT procedure is ongoing over CG and the UE has not received a response from the network after the initial PUSCH transmission. + +Upon unsuccessful completion of the SDT procedure, the UE transitions to RRC\_IDLE. + +For SDT, network should not send *RRRCReject* in response to *RRRCResumeRequest/RRRCResumeRequest1* if DL data over any radio bearer configured for SDT is transmitted. + +The initial PUSCH transmission during the SDT procedure includes at least the CCCH message. When using CG resources for initial SDT transmission, the UE can perform autonomous retransmission of the initial transmission if the UE does not receive confirmation from the network (dynamic UL grant or DL assignment) before a configured timer expires as specified in clause 5.4.1 of TS 38.321 [6]. After the initial PUSCH transmission, subsequent transmissions are handled differently depending on the type of resource used to initiate the SDT procedure: + +- When using CG resources, the network can schedule subsequent UL transmissions using dynamic grants or they can take place on the following CG resource occasions. The DL transmissions are scheduled using dynamic assignments. The UE can initiate subsequent UL transmission only after reception of confirmation (dynamic UL grant or DL assignment) for the initial PUSCH transmission from the network. For subsequent UL transmission, the UE cannot initiate re-transmission over a CG resource. +- When using RACH resources, the network can schedule subsequent UL and DL transmissions using dynamic UL grants and DL assignments, respectively, after the completion of the RA procedure. + +When SDT procedure is initiated, AS security is applied for all the radio bearers enabled for SDT as specified in clause 5.3.13.3 of TS 38.331 [12]. + +While the SDT procedure is ongoing, if data appears in a buffer of any radio bearer not enabled for SDT, the UE initiates a transmission of a non-SDT data arrival indication using *UEAssistanceInformation* message to the network and, if available, includes the resume cause. + +SDT procedure over CG resources can only be initiated with valid UL timing alignment. The UL timing alignment is maintained by the UE based on a SDT-specific timing alignment timer configured by the network via dedicated signalling and, for initial CG-SDT transmission, also by DL RSRP of configured number of highest ranked SSBs which are above a configured RSRP threshold. Upon expiry of the SDT-specific timing alignment timer, the CG resources are released while maintaining the CG resource configuration. + +Logical channel restrictions configured by the network while in RRC\_CONNECTED state and/or in *RRRelease* message for radio bearers enabled for SDT, if any, are applied by the UE during SDT procedure. + +The network may configure UE to apply ROHC continuity for SDT either when the UE initiates SDT in the PCell of the UE when the *RRRelease* with suspend indication was received or when the UE initiates SDT in a cell of its RNA. + +For SDT procedure over CG resources, the network may configure maximum time duration until the next valid CG occasion for initial CG-SDT transmission based on which the UE decides whether SDT procedure over CG resources can be initiated. The maximum time duration is configured per logical channel for MO-SDT and per UE for MT-SDT. + +## 18.1 Support of SDT procedure over RACH + +For SDT procedure over RACH, if the UE accesses a gNB other than the last serving gNB, the UL SDT data/signalling is buffered at the receiving gNB, and then the receiving gNB triggers the XnAP Retrieve UE Context procedure. The receiving gNB indicates SDT to the last serving gNB and the last serving gNB decides whether to relocate the UE context or not. Other SDT assistance information (e.g., single packet, multiple packets) may also be provided by the receiving gNB to help the decision of UE context relocation. If the UE is configured with the clock quality control information, the last serving gNB may perform full UE context relocation. + +If the last serving gNB decides not to relocate the full UE context, it transfers a partial UE context containing SDT RLC context information necessary for the receiving gNB to handle SDT via the Partial UE Context Transfer procedure. + +Then, in case SDT is used for user data over DRBs, UL/DL tunnels are established for DRBs configured for SDT between the receiving gNB and the last serving gNB. The PDCP PDU of UL/DL data is transferred over the tunnels, until the last serving gNB terminates the SDT session and directs the UE to continue in RRC\_INACTIVE by sending the *RRRelease* message. + +Or in case SDT is used for signalling, SRB PDCP PDUs are transferred between the receiving gNB and the last serving gNB via the XnAP RRC Transfer procedure, until the last serving gNB terminates the SDT session and directs the UE to continue in RRC\_INACTIVE by sending the *RRRelease* message. + +During the SDT session, in case the receiving gNB detects that no more packets are to be transmitted, or radio link problem is detected, the receiving gNB may also request to terminate the SDT session to the last serving gNB via the UE Context Retrieve Confirmation procedure. + +## 18.2 SDT with UE context relocation + +The overall procedure for SDT procedure over RACH with UE context relocation is illustrated in the figure 18.2-1. + +![Sequence diagram illustrating the RA-based SDT with UE context relocation procedure. The diagram shows five vertical lifelines representing network entities. The first lifeline on the left has a rounded rectangle at the top, representing the UE. The other four lifelines have rectangular boxes at the top, representing gNBs. Arrows indicate the flow of messages: from the UE to the second lifeline (Receiving gNB), and from the second lifeline to the third lifeline (Last Serving gNB).](b0b07599997175149ac03e26e3247c9a_img.jpg) + +Sequence diagram illustrating the RA-based SDT with UE context relocation procedure. The diagram shows five vertical lifelines representing network entities. The first lifeline on the left has a rounded rectangle at the top, representing the UE. The other four lifelines have rectangular boxes at the top, representing gNBs. Arrows indicate the flow of messages: from the UE to the second lifeline (Receiving gNB), and from the second lifeline to the third lifeline (Last Serving gNB). + +**Figure 18.2-1. RA-based SDT with UE context relocation** + +1. The UE sends an *RRResumeRequest* as well as UL SDT data and/or UL SDT signalling to the Receiving gNB. +2. The Receiving gNB identifies the Last Serving gNB using the I-RNTI and retrieves the UE context by means of Xn-AP Retrieve UE Context procedure. The Receiving gNB indicates that the UE request is for an SDT and may also provide SDT assistance information (e.g., single packet, multiple packets). +3. The Last Serving gNB decides to relocate UE context and responds with the RETRIEVE UE CONTEXT RESPONSE message. The UL SDT data, if any, is delivered from the Receiving gNB to the UPF. +- 4-6. The Receiving gNB decides to keep UE in RRC\_INACTIVE state for SDT. If loss of DL user data buffered in the Last Serving gNB shall be prevented, the Receiving gNB provides forwarding addresses via the Xn-U ADDRESS INDICATION message. The Receiving gNB also initiates NGAP Path Switch Request procedure to establish a NG UE-associated signalling connection to the AMF. After the Path Switch Request procedure, the buffered UL NAS PDU, if any, is delivered from the Receiving gNB to the AMF. And then, the subsequent UL/DL SDT data and/or signalling are transferred between UE and core network via the Receiving gNB. + +NOTE 1: If the UP policy received from the Last Serving gNB is different from that received in the PATH SWITCH REQUEST ACKNOWLEDGE message, the Receiving gNB may either send the UE back to RRC\_IDLE or move the UE to RRC\_CONNECTED to update the security configuration. + +7. After the SDT transmission is terminated, the Receiving gNB generates and sends the *RRRelease* message including the suspend indication to the UE to terminate the SDT procedure and continue in RRC\_INACTIVE state. + +- NOTE 2: In case DL non-SDT data or DL non-SDT signalling arrives, or the UE assistance information (i.e. UL non-SDT data arrival indication) is received from the UE, the Receiving gNB may decide to directly send the UE to RRC\_CONNECTED state by sending the *RRCResume* message. +- NOTE 3: The Receiving gNB may decide to directly send the UE to RRC\_CONNECTED state by sending the *RRCResume* message based on (e.g. large size of) DL SDT data or DL SDT signalling. +- NOTE 4: The Receiving gNB may decide to directly send the UE to RRC\_CONNECTED state by sending the *RRCResume* message based on the BSR received from the UE in case of uplink SDT data exceeding the data size threshold. +8. The Receiving gNB indicates to the Last Serving gNB to remove the UE context by sending the XnAP UE CONTEXT RELEASE message. The XnAP UE CONTEXT RELEASE message can be sent after step 6. + +## 18.3 SDT without UE context relocation + +The overall procedure for SDT procedure over RACH without UE context relocation is illustrated in the figure 18.3-1. + +![Sequence diagram for RA-based SDT without UE context relocation. The diagram shows five vertical lifelines representing network entities. A horizontal arrow points from the first lifeline to the second lifeline, representing the initial message exchange. The remaining three lifelines are shown but have no messages depicted on them in this partial view.](f3fd3ff8f78da4c2a4d39bb6330c49a1_img.jpg) + +Sequence diagram for RA-based SDT without UE context relocation. The diagram shows five vertical lifelines representing network entities. A horizontal arrow points from the first lifeline to the second lifeline, representing the initial message exchange. The remaining three lifelines are shown but have no messages depicted on them in this partial view. + +**Figure 18.3-1. RA-based SDT without UE context relocation** + +- 1/2. The steps 1/2 are as defined in steps 1/2 in Figure 18.2-1. +3. The last serving gNB decides not to relocate the full UE context for SDT. +4. The last serving gNB transfers a partial UE context including the SDT related RLC context. +5. The receiving gNB acknowledges receiving the partial UE context and provides associated DL TNL address. The UE context is kept at the last serving gNB and the SDT related RLC context is established at the receiving gNB. Then UL/DL GTP-U tunnels are established for DRBs configured for SDT, if any, and the UL SDT data and/or signalling, if any, are forwarded to the last serving gNB, and then delivered to the core network. + +NOTE 1: The DL signalling from the last serving gNB, if any, is forwarded to the receiving gNB via the RRC TRANSFER message, for which the receiving gNB delivers it to the UE. + +NOTE 1a: In case DL non-SDT data or DL non-SDT signalling arrives, or UE assistance information (i.e. UL non-SDT data arrival indication) is received from the UE, the last serving gNB terminates the SDT procedure and directs the UE to continue in RRC\_INACTIVE state by sending the *RRCRelease* message. + +NOTE 1b: The last serving gNB may terminate the SDT procedure and direct the UE to continue in RRC\_INACTIVE state by sending the *RRCRelease* message based on (e.g. large size of) DL SDT data or DL SDT signalling. + +6. The receiving gNB detects the end of SDT session and sends the RETRIEVE UE CONTEXT CONFIRM message including whether this is a "normal" end of SDT transaction or a radio link problem, or large SDT volume from BSR. + +7. Upon receiving the RETRIEVE UE CONTEXT CONFIRM message and deciding to terminate the SDT, the last serving gNB responds to the receiving gNB with the RETRIEVE UE CONTEXT FAILURE message including an encapsulated *RRCRelease* message. The receiving gNB shall release the established partial UE context. + +NOTE 2: Void. + +NOTE 3: Void. + +8. The receiving gNB sends the *RRCRelease* message to the UE. + +NOTE 4: Void. + +NOTE 5: The last serving gNB may terminate the SDT procedure and direct the UE to continue in RRC\_INACTIVE state by sending the *RRCRelease* message upon receiving the indication about large uplink SDT data from the BSR from the receiving gNB in step 6. + +9. The UE moves to RRC\_INACTIVE state if the suspend indication is included in the *RRCRelease* message. Or else, the UE moves to RRC\_IDLE state. + +## 18.4 MT-SDT with/without UE context relocation + +The overall procedure for MT-SDT procedure with/without UE context relocation is illustrated in the figure 18.4-1. + +![Sequence diagram for MT-SDT with/without UE context relocation. The diagram shows the interaction between UE, Receiving gNB, Last Serving gNB, AMF, and UPF(S). The process starts with the UE in RRC_INACTIVE CM-CONNECTED state. DL user data and DL NAS signaling are received at the Last Serving gNB. The Last Serving gNB sends RAN Paging (MT-SDT information) to the Receiving gNB. The Receiving gNB sends Uu Paging (MT-SDT indicator) to the UE. The UE decides to initiate the MT-SDT procedure and sends an RRCResumeRequest to the Receiving gNB. The subsequent steps are the same as Figure 18.2-1/18.3-1 from step 2.](31f5b6310f831ca3ea4f18453980c070_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Receiving gNB + participant Last Serving gNB + participant AMF + participant UPF(S) + + Note left of UE: 0. UE in RRC_INACTIVE CM-CONNECTED + Note right of Last Serving gNB: Buffer DL user data/NAS signaling + UPF(S)->>Last Serving gNB: 1. DL user data + UPF(S)->>Last Serving gNB: 1. DL NAS signaling + Last Serving gNB->>Receiving gNB: 2. RAN Paging (MT-SDT information) + Receiving gNB->>UE: 3. Uu Paging (MT-SDT indicator) + Note left of UE: 4. UE decides to initiate MT-SDT procedure + UE->>Receiving gNB: 5. RRCResumeRequest + Note right of Receiving gNB: 6. The following steps are the same as Figure 18.2-1/18.3-1 from step 2 + +``` + +Sequence diagram for MT-SDT with/without UE context relocation. The diagram shows the interaction between UE, Receiving gNB, Last Serving gNB, AMF, and UPF(S). The process starts with the UE in RRC\_INACTIVE CM-CONNECTED state. DL user data and DL NAS signaling are received at the Last Serving gNB. The Last Serving gNB sends RAN Paging (MT-SDT information) to the Receiving gNB. The Receiving gNB sends Uu Paging (MT-SDT indicator) to the UE. The UE decides to initiate the MT-SDT procedure and sends an RRCResumeRequest to the Receiving gNB. The subsequent steps are the same as Figure 18.2-1/18.3-1 from step 2. + +**Figure 18.4-1: MT-SDT with/without UE context relocation** + +1. DL user data and/or DL NAS signalling are received at the Last Serving gNB for the UE in RRC\_INACTIVE state. +2. The Last Serving gNB may send MT-SDT information to the neighbour gNBs within the RNA, via XnAP RAN PAGING message. +3. The gNB that receives MT-SDT information within the RNA, takes into account the MT-SDT information received in the XnAP RAN PAGING message to decide whether to trigger MT-SDT Paging. The gNB which ultimately reaches the UE via the Uu Paging becomes the Receiving gNB. + +NOTE 1: In case that the Receiving gNB decides not to trigger MT-SDT paging, the above step 3 and subsequent steps are the same as Figure 9.2.2.4.2 from step 3. + +- 4/5. The UE may decide to initiate MT-SDT procedure and in this case sends an RRCResumeRequest message with an MT-SDT resume cause to the Receiving gNB. + +6. The following steps are the same as Figure 18.2-1/18.3-1 from step 2, except that the first SDT user data and/or NAS signalling is DL SDT data and/or DL SDT NAS signalling. + +NOTE 2: In case DL non-SDT data or DL non-SDT signalling has arrived between step 2 and step 6, the Last Serving gNB should relocate the UE context to the Receiving gNB and forward the received data to the Receiving gNB. + +## 19 Support for NR coverage enhancements + +To improve NR uplink coverage for both FR1 and FR2, the following enhancements on PUSCH, PUCCH, PRACH and MSG3 PUSCH are supported: + +- Enhanced aggregation of multiple slots with TB repetition is supported for both PUSCH transmission with dynamic and configured grant. In addition, counting based on available slots is supported. The maximum number of aggregated slots for counting based on available slots and counting based on physical slots are both 32. + +- TB processing over multiple slots with and without repetition is supported for both PUSCH transmission with dynamic grant and configured grant. For a single transmission of TB processing over multiple slots PUSCH, the TB size is determined based on multiple slots. +- DMRS bundling where the UE maintains phase continuity and power consistency across PUSCH transmissions or PUCCH repetitions to enable improved channel estimation is supported. Inter-slot frequency hopping with DMRS bundling is supported. +- Dynamic PUCCH repetition factor indication configured per PUCCH resource is introduced, applicable to all PUCCH formats. +- Aggregation of multiple slots with TB repetition for MSG3 transmission is supported on both NUL and SUL, applicable to CBRA with 4-step RA type. If configured, the UE requests MSG3 repetition via separate RACH resources when the RSRP of DL path-loss reference is lower than a configured threshold. BWP configured with RACH resources solely for MSG3 repetition is also supported without the need to consider the RSRP of DL path-loss reference by the UE. +- MSG1 repetition with same beam is supported on both NUL and SUL for 4-step RA type. For CBRA, network broadcasts separate RSRP thresholds for different repetition numbers. UE performs MSG1 repetition via RACH resources that are different from RACH resources without MSG1 repetition. CFRA for MSG1 repetition for *ReconfigurationWithSync* is supported and the network signals the MSG1 repetition number explicitly. Fallback from lower number to higher number of MSG1 repetition is supported among the set(s) of RACH resources associated with same feature(s). Fallback from lower number to higher number of MSG1 repetition is not supported for MSG1-based SI request or if UE has performed fallback from CFRA to CBRA. Fallback from CFRA with MSG1 repetition to 4-step CBRA with MSG1 repetition using the same MSG1 repetition number as the one used for CFRA is supported. +- Dynamic switching between DFT-S-OFDM and CP-OFDM for PUSCH is supported. The indication for switching between DFT-S-OFDM and CP-OFDM for PUSCH is contained in DCI format 0\_1/0\_2, which is configured separately for each BWP. PHR can be reported for current transmission of PUSCH using one of the DFT-S-OFDM or CP-OFDM waveform and an assumed transmission of PUSCH using the other waveform than the current one. +- Frequency domain spectrum shaping without frequency extension is supported for MPR/PAR reduction on the PUSCH transmission, and the change value of UE power class is reported in the PHR. + +--- + +## 20 Support for Multi-USIM devices + +### 20.1 General + +NG-RAN may support one or more of the following enhancements for MUSIM device operation: + +- Paging Collision Avoidance, as described in clause 20.2; +- UE notification on Network Switching, as described in clause 20.3; +- Temporary UE capability restriction and removal of restriction, as described in clause 20.4. + +### 20.2 Paging Collision Avoidance + +The purpose of paging collision avoidance is to address the overlap of paging occasions on both USIMs when a MUSIM device (e.g. dual USIM device) is in RRC\_IDLE/RRC\_INACTIVE state in both the networks (e.g. Network A and Network B) associated with respective USIMs. Network A is NR and Network B is E-UTRA or NR. + +A MUSIM device may determine potential paging collision on two networks and may trigger actions to prevent potential paging collision on NR network as specified in TS 23.501 [3]. + +NOTE: It is left to UE implementation as to how it selects one of the two RATs/networks for paging collision avoidance. + +## 20.3 UE notification on Network Switching + +For MUSIM operation, a MUSIM device in RRC\_CONNECTED state in Network A may have to switch from Network A to Network B. Network A is NR and Network B can either be E-UTRA or NR. Before switching from Network A, a MUSIM device should notify Network A to either leave RRC\_CONNECTED state, or be kept in RRC\_CONNECTED state in Network A while temporarily switching to Network B. + +When configured to do so, a MUSIM device can signal to the Network A a preference to leave RRC\_CONNECTED state by using RRC (see TS 38.331 [12]) or NAS signalling (see TS 23.501 [3]). After sending a preference to leave RRC\_CONNECTED state by using RRC signalling, if the MUSIM device does not receive an *RRCRelease* message from the Network A within a certain time period (configured by the Network A, see TS 38.331 [12]), the MUSIM device can enter RRC\_IDLE state in Network A. + +When configured to do so, a MUSIM device can signal to the Network A a preference to be temporarily switching to Network B while remaining in RRC\_CONNECTED state in Network. This is indicated by scheduling gaps preference. This preference can include information for setup or release of gap(s). The Network A can configure at most 4 gap patterns for MUSIM purpose: three periodic gaps and a single aperiodic gap. The Network A should always provide at least one of the requested gap pattern or no gaps. Network providing an alternative gap pattern instead of the one requested by the UE is not supported in this release. + +When configured to do so, a MUSIM device can include priority of periodic gap(s) in addition to scheduling gaps preference, and the priority preference should be indicated for all periodic gap(s). If the MUSIM device indicates gap priority preference, it can also indicate its preference on using *keep solution* (defined in TS 38.133[13]). + +## 20.4 Temporary UE capability restriction and removal of restriction + +For MUSIM operation, a MUSIM device in RRC\_CONNECTED state in Network A may indicate its preference on temporary UE capability restriction or removal of restriction with Network A when the MUSIM device needs transmission or reception in Network B (e.g., including start/stop connection to Network B). Network A is NR and Network B can either be E-UTRA or NR. The MUSIM device may request a temporary capability restriction only after the Network signals via RRC that this is allowed. + +When configured to do so, a MUSIM device can indicate one or more of the following temporary capability restriction or removal of restriction to the Network A: + +- A MUSIM device can explicitly request SCell(s) or SCG to be released; +- A MUSIM device can indicate its preference on temporary maximum MIMO layers and/or supported channel bandwidth for specific serving cells for both UL/DL; +- A MUSIM device can indicate its preference on the temporary maximum number of CCs per UL/DL; +- A MUSIM device can indicate its preference on the concerned band(s) or band combination(s) (e.g. forbidden and/or affected band(s) or band combination(s)) based on a band-filter list configured by network. For affected band(s) and band combination(s), this preference can include temporary maximum MIMO layers and/or supported channel bandwidth for both UL/DL; +- A MUSIM device can indicate the measurement gap requirement changes. + +When it is allowed by Network A in SIB1, a MUSIM device can indicate to the Network A that its capabilities are temporarily restricted in *RRCSsetupComplete/RRCSresumeComplete* message while the MUSIM device is already in RRC\_CONNECTED state in Network B. + +When a MUSIM device is in RRC\_CONNECTED state in both Network A and Network B, if Network B is NR, it is up to UE implementation to select which network to request temporary UE capability restriction; if Network B is E-UTRA, the request for temporary UE capability restriction can only be performed on Network A. + +## 21 Application Layer Measurement Collection + +### 21.1 Overview + +The QoE Measurement Collection function enables collection of application layer measurements from the UE. The supported service types are: + +- QoE Measurement Collection for DASH streaming services; +- QoE Measurement Collection for MTSI services; +- QoE Measurement Collection for VR services. + +For DASH, MTSI, VR, the QoE measurement collection is supported in RRC\_CONNECTED state only, unless the application data is delivered via MBS broadcast communication service. + +The QoE Measurement Collection function supports collection of QoE measurements for MBS communication service. The measurement collection is supported for the following two communication service types: + +- MBS broadcast; +- MBS multicast. + +QoE measurement collection for application sessions delivered via MBS broadcast is supported in RRC\_CONNECTED, RRC\_INACTIVE, and RRC\_IDLE states. QoE measurement collection for the application sessions delivered via MBS multicast is supported in RRC\_CONNECTED state only. Both signalling based and management based QoE measurement collection are supported in NR SA and NR-DC. Further details of NR-DC operation can be found in TS 37.340 [21] and clause 21.7. + +NOTE: The naming QoE Measurement is used in NG, Xn, and interfaces between the OAM and the gNB. In the Uu interface, the naming application layer measurement is used and it is equal to QoE Measurement. + +### 21.2 QoE Measurement Configuration + +#### 21.2.1 QoE Measurement Collection Activation and Reporting + +The feature is activated in the gNB either by direct configuration from the OAM system (management-based activation), or by signalling from the OAM via the 5GC (signalling-based activation), containing UE-associated QoE configuration. One or more QoE measurement collection jobs can be activated at a UE per service type, and each QoE measurement configuration is uniquely identified by a QoE reference. + +For signalling-based QoE measurements, the OAM initiates the QoE measurement activation for a specific UE via the 5GC, and the gNB receives one or more QoE measurement configurations by means of UE-associated signalling. The QoE measurement configuration for signalling-based activation includes an application layer measurement configuration list and the corresponding information for QoE measurement collection, e.g., QoE reference, service type, MCE IP address, slice scope, area scope, MDT alignment information, the indication of available RAN visible QoE metrics and assistance information. + +For management-based QoE measurement activation, the OAM sends one or more QoE measurement configurations directly to the gNB. The QoE measurement configuration for management-based activation also includes an application layer measurement configuration list and the corresponding information for QoE measurement collection. The gNB selects UE(s) that meet the required QoE measurement capability, area scope and slice scope. + +Application layer measurement configuration received by the gNB from OAM or 5GC is encapsulated in a transparent container, which is forwarded to a UE as Application layer configuration in the *RRCReconfiguration* message (there can be multiple configurations in the same message). Application layer measurement reports received from UE's application layer are encapsulated in a transparent container and sent to the network in the *MeasurementReportAppLayer* message, as specified in TS 38.331 [12]. The UE can send multiple application layer measurement reports to the gNB in one *MeasurementReportAppLayer* message. In order to allow the transmission of application layer measurement reports which exceed the maximum PDCP SDU size, segmentation of the *MeasurementReportAppLayer* message may be + +enabled by the gNB. A measurement configuration application layer ID conveyed in the RRC signalling is used to identify the application layer measurement configuration and report between the gNB and the UE. The measurement configuration application layer ID is mapped to the QoE reference in the gNB, and the gNB forwards the application layer measurement report to MCE together with the QoE reference. The gNB can release one or multiple application layer measurement configurations from the UE in one *RRCReconfiguration* message at any time. The UE may additionally be configured by the gNB to report when a QoE measurement session starts or stops for a certain application layer measurement configuration. + +## 21.2.2 QoE Measurement Collection Deactivation + +The QoE Measurement Collection deactivation permanently stops all or some of the QoE measurement collection jobs towards a UE, resulting in the release of the corresponding QoE measurement configuration(s) in the UE. The deactivation of QoE measurement collection is supported by using UE-associated signalling. A list of QoE references is used to deactivate the corresponding QoE measurement collection job(s). + +Upon reception of the QoE release message in an application layer measurement configuration, the UE discards any unsent application layer measurement reports corresponding to the released application layer configuration. The UE discards the reports received from application layer when it has no associated application layer measurement configuration configured. + +The network can replace a QoE measurement configuration with another one by deactivating an existing QoE measurement configuration and activating another QoE measurement configuration of the same QoE measurement configuration type. + +## 21.2.3 Handling of QMC during RAN Overload + +The QoE measurement collection pause/resume procedure is used to pause/resume reporting of one or multiple QoE measurement configurations in a UE in RAN overload situation. + +The gNB can use the *RRCReconfiguration* message to temporarily stop the UE from sending application layer measurement reports associated with one or multiple application layer measurement configurations. When the UE receives the QoE measurement collection pause indication, the UE temporarily stores application layer measurement reports in AS layer. When the UE receives the QoE measurement collection resume indication, the UE sends the stored application layer measurement reports to the gNB. + +For a QoE measurement configuration, the assistance information provided by the OAM may be considered by the gNB for deciding whether to pause/resume the measurement reporting of certain QoE measurement configurations in case of RAN overload. + +## 21.2.4 QoE Measurement Handling in RRC\_IDLE and RRC\_INACTIVE States + +If the UE enters RRC\_INACTIVE, the UE AS configuration for the QoE is stored in the UE Inactive AS context. + +If the UE enters RRC\_IDLE state, the UE releases all application layer measurement configurations except the application layer configurations explicitly indicated by the gNB as applicable in RRC\_IDLE and RRC\_INACTIVE states. + +For application measurement configurations applicable in RRC\_IDLE and RRC\_INACTIVE states, the UE continues on-going QoE measurement collection when entering RRC\_IDLE or RRC\_INACTIVE state, and also when returning to RRC\_CONNECTED state. The UE may also start QoE collection according to the stored QoE configuration while in RRC\_IDLE or RRC\_INACTIVE state. The UE keeps the application layer measurement configurations but does not start new QoE sessions when it is outside of the area scope for QoE configurations in RRC\_IDLE and/or RRC\_INACTIVE state. The UE stores the application layer measurement reports generated while in RRC\_IDLE and/or RRC\_INACTIVE state in the AS layer. The gNB can retrieve the application layer measurement reports/configurations and session status indication by configuring SRB4 or SRB5 after it receives application layer measurement reports/configurations availability indication. The UE can send idle/inactive application layer measurement reports to the gNB only when it has moved to RRC\_CONNECTED state due to other reasons. + +Upon UE's transition from RRC\_IDLE to RRC\_CONNECTED, the gNB serving the UE should ensure that it does not release an already configured signalling-based QoE measurement configuration for the sake of configuring a new management-based QoE measurement configuration. + +## 21.2.5 Per-slice QoE Measurement + +When a service is provided within a configured slice, the QoE Measurement for this service type can also be configured together with the corresponding slice scope, so that the user experience of this service can also be evaluated on a per-slice basis. Multiple QoE measurement configurations can be configured for the same service type, and each configuration can pertain to different slices, where each QoE measurement configuration is identified with a QoE reference. + +The UE includes the network slice identifier inside the QoE report container when reporting QoE measurement reports. + +## 21.3 QoE Measurement Continuity for Mobility + +QoE measurement collection continuity for intra-system intra-RAT handover is supported, with the Area Scope parameters configured by the OAM, where the network is responsible for keeping track of whether the UE is inside or outside the area scope. A UE continues an ongoing QoE measurement even if it leaves the area scope, unless the network indicates to the UE to release the application layer measurement configuration. + +For the handover, the source gNB may transmit the information related to one or more application layer measurement configurations of the UE to the target gNB via XnAP or NGAP. For signalling-based QoE, the service type indication, QoE reference, and, optionally, the MCE IP address, measurement configuration application layer ID, MDT alignment information, area scope, slice support list for QMC, available RAN visible QoE metrics and measurement status are passed to the target gNB. For management-based QoE, the service type indication, measurement configuration application layer ID, the MCE IP address and QoE measurement status are passed to the target gNB. For RRC\_INACTIVE state mobility, QoE measurement configuration(s) of a specific UE can be retrieved from the gNB hosting the UE context when it resumes to the RRC\_CONNECTED state. + +For signalling-based QoE, at handover to a target gNB that supports QoE measurement collection, the target gNB decides which of the application layer measurement configurations should be kept or released, e.g., based on application layer measurement configuration information received from the source gNB in Xn/NG signalling. + +The continuity of QoE measurement configuration and reporting in NR-DC scenario is supported as specified in TS 37.340 [21]. + +For QoE sessions pertaining to data flows received via MBS broadcast, QoE measurement collection may continue during the RRC\_INACTIVE and RRC\_IDLE. + +Upon UE's transition from RRC\_IDLE to RRC\_CONNECTED, the gNB serving the UE should ensure that it does not release an already configured signalling-based QoE measurement configuration for the sake of configuring a new management-based QoE measurement configuration. + +QoE measurements for ongoing sessions should be continued when switching between MBS multicast and unicast transmission modes. + +When the UE resumes the connection with a gNB that does not support QoE, the UE releases all application layer measurement configurations. + +QoE measurement collection continuity for intra-system inter-RAT handover is supported. For the handover from NR to LTE, only one QoE measurement can be continued when the UE connects to the target LTE node. The source gNB decides which QoE measurement to keep and sends the information about this QoE measurement to the target ng-eNB. + +For intra-5GC handover from E-UTRA to NR, the UE releases the LTE QoE configuration if received from the source RAT and the UE applies NR QoE configuration(s) if received from the target RAT. + +For intra-5GC handover from NR to E-UTRA, the UE releases all NR QoE configuration(s) if received from the source RAT, and the UE applies the LTE QoE configuration if received from the target RAT. + +## 21.4 RAN Visible QoE Measurements + +RAN visible QoE measurements are configured at the UE by the gNB, where a subset of configured QoE metrics is reported from the UE to the gNB as an explicit IE readable by the gNB. The RAN visible QoE measurements can be used by the gNB for network optimization. The RAN visible QoE measurements are supported for the DASH streaming and VR services. The gNB configures the RAN visible QoE measurement of all or some of the available RAN visible QoE metrics, where the indication of metric availability is received by the gNB as part of management-based or the signalling-based QoE configuration. The set of available RAN visible QoE metrics is a subset of the metrics configured as part of QoE measurement configuration encapsulated in the application layer measurement configuration container. RAN visible QoE measurements and encapsulated QoE measurements can be configured together or separately. RAN visible QoE measurements can only be configured if there is a corresponding QoE measurement configuration for the same service type configured at the UE. The gNB may modify a RAN visible QoE configuration by releasing it and configuring the UE with a new RAN visible QoE configuration pertaining to the same QoE reference. In this case, the new RAN visible QoE configuration applies immediately, i.e., even during the same application session. + +Multiple simultaneous RAN visible QoE measurement configurations and reports can be supported for RAN visible QoE measurements, and each RAN visible QoE measurement configuration and report is identified by the same measurement configuration application layer ID as the corresponding QoE measurement configuration and measurement report. After receiving the RAN visible QoE measurement configuration, the UE RRC layer forwards the configuration to the application layer, indicating the service type, the measurement configuration application layer ID and, optionally, the reporting periodicity for RAN visible QoE. The application layer sends the RAN visible QoE measurement report associated with the measurement configuration application layer ID to the UE's AS layer. The PDU session ID(s) and QoS Flow ID(s) per PDU session ID corresponding to the service that is subject to QoE measurements can also be reported by the UE along with the RAN visible QoE measurement results. + +If there is no reporting periodicity defined in the RAN visible QoE configuration, the UE sends both RAN visible QoE measurement reports and the QoE measurement reports to the gNB in the same *MeasurementReportAppLayer* message, except when QoE measurement reporting pause indication is received (e.g., in case of RAN overload). When a QoE measurement collection is paused, if there is no reporting periodicity defined in the RAN visible QoE configuration, the encapsulated QoE reports are stored at the UE's RRC layer, but the RAN visible QoE reports continue to be reported to the gNB with the reporting periodicity configured for encapsulated QoE reporting. The RAN visible QoE measurements can be reported with a reporting periodicity different from the one of the corresponding encapsulated QoE measurements, when a dedicated RAN visible QoE reporting periodicity is configured by the gNB. The UE Application layer can measure the RAN visible QoE metrics based on this reporting periodicity. + +The gNB can release one or multiple RAN visible QoE measurement configurations from the UE in one *RRCREconfiguration* message at any time. If the encapsulated QoE configuration is released, the corresponding RAN visible QoE configuration shall be released as well. + +The RAN visible QoE configuration can be transferred from the source gNB to the target gNB upon mobility and from the old gNB to the new gNB during context retrieval. The target gNB or the new gNB can generate a new RAN visible QoE configuration based on the available RAN visible QoE metrics received and can send the new RAN visible QoE configuration to the UE during handover or the RRC resume procedure. + +## 21.5 Alignment of MDT and QoE Measurements + +The radio-related measurements may be collected via immediate MDT for all types of supported services for the purpose of QoE analysis. The MCE/TCE performs the correlation of the immediate MDT measurement results and the QoE measurement results collected at the same UE. + +The following is supported: + +- Alignment between a signalling-based QoE measurement and a signalling-based MDT measurement. In this case, the signalling-based QoE configuration sent to the gNB includes the NG-RAN Trace ID of the signalling-based MDT measurement. +- Alignment between a management-based QoE measurement and a management-based MDT measurement. + +The UE configured with QoE measurements sends an indication to inform the gNB about the start or the stop of a QoE measurement session of configured QoE measurements. The gNB can activate the MDT measurements that are to be aligned with the QoE measurements performed by the UE upon/after receiving the QoE measurement session start indication from the UE. The gNB may activate the MDT measurements upon/after receiving the MDT activation + +message from the OAM. The gNB can deactivate the aligned MDT measurements according to an OAM command which may, e.g., be triggered by the session stop indication. + +The gNB includes time stamp information to the QoE measurement reports to enable the correlation of corresponding measurement results of MDT and QoE at the MCE/TCE. In addition, the gNB includes the MDT session identifiers (Trace Reference and Trace Recording Session Reference) in the corresponding QoE measurement report. + +## 21.6 QoE Measurement Collection in High Mobility Scenarios + +QoE measurements can be confined to high mobility state of the UE and/or to HSDN cells. + +## 21.7 Support for RAN visible QoE measurements and reporting in NR-DC + +Either the MN or the SN can generate and send a RAN visible QoE configuration to the UE. The gNB that has initially configured a UE in NR-DC with an RVQoE configuration can modify and release the RAN visible QoE configuration as long as the UE is connected to this gNB. The gNB that configures the encapsulated QoE measurements to UE is referred to as the RAN visible QoE-configuring gNB, and the peer node is referred to as the non-RAN visible QoE-configuring gNB. Upon mobility, the RAN visible QoE-configuring gNB may be changed. + +The UE may send RAN visible QoE reports to the network using either SRB4 or SRB5. In addition, the gNB that received a RAN visible QoE report can forward the report to the other gNB (the SN or the MN). QoE reports and RAN visible QoE reports pertaining to the same QoE Reference can be sent over the same SRB or they can be sent over different SRBs. + +The RAN visible QoE-configuring gNB can configure RAN visible QoE measurements at a UE without a priori knowledge about which gNB(s) will provide the bearer(s) for a future application session. During the lifetime of an application session, to ensure that the RAN visible QoE reports are sent to the gNB(s) that provide the bearer(s) which carry the data flow(s) associated with the RAN visible QoE measurement result in a RAN visible QoE report, the gNB receiving the RAN visible QoE reports determines the bearer(s) used to deliver the application session data flow(s) and the associated gNB(s). The determination may be based on the PDU session ID(s) and the QoS flow ID(s) indicated in a received RAN visible QoE report. + +When the RAN visible QoE-configuring gNB receives a RAN visible QoE measurement report and determines that the non-RAN Visible QoE-configuring gNB provides at least one bearer for the application session, the RAN Visible QoE-configuring gNB indicates that to the non-RAN Visible QoE-configuring gNB. The non-RAN Visible QoE-configuring gNB can then, if needed, indicate to the RAN visible QoE-configuring gNB its preference with respect to the reporting path for the subsequent RAN visible QoE reports and its preferred RAN visible QoE configuration parameters. + +If a gNB receives a RAN visible QoE report from a UE in NR-DC, and determines that the bearer(s) for the application session data flow(s) is (are) also provided by the other gNB, or only, provided by the other gNB, the gNB that received the RAN visible QoE measurement report may forward the received RAN visible QoE report to the other gNB. The RAN visible QoE reports can be transferred between the MN and the SN via the RRC TRANSFER message. The RAN visible QoE configuration may also be modified or released. + +## Annex A (informative): QoS Handling in RAN + +### A.1 PDU Session Establishment + +The following figure shows an example message flow for a PDU session establishment. NAS procedures details between gNB and 5GC can be found in TS 23.501 [3], TS 23.502 [22] and TS 38.413 [26]. + +![Sequence diagram of PDU session establishment between UE, gNB, UPF, and AMF.](26eb15ab3bef8b99ba79760363525e51_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB + participant UPF + participant AMF + Note left of UE: + UE->>AMF: 1. PDU Session Establishment Request + AMF->>gNB: 2. PDU SESSION RESOURCE SETUP REQUEST + gNB->>UE: 3. RRCReconfiguration + Note left of UE: 4. DRB(s) established + UE->>gNB: 5. RRCReconfigurationComplete + gNB->>AMF: 6. PDU SESSION RESOURCE SETUP RESPONSE + Note left of gNB: + UE->>gNB: 7. UP Data (QFI) + gNB->>UPF: 7. UP Data (QFI) + +``` + +The diagram illustrates the message flow for PDU session establishment. It involves four main entities: UE (User Equipment), gNB (Next Generation NodeB), UPF (UPF), and AMF (AMF). The sequence of messages is as follows: 1. UE sends a PDU Session Establishment Request to AMF. 2. AMF sends a PDU SESSION RESOURCE SETUP REQUEST to gNB. 3. gNB sends an RRCReconfiguration message to UE. 4. UE establishes the DRB(s) for the new PDU session and creates the QFI to DRB mapping rules. 5. UE sends an RRCReconfigurationComplete message to gNB. 6. gNB sends a PDU SESSION RESOURCE SETUP RESPONSE message to AMF. 7. User Plane Data can then be exchanged between UE and gNB over DRB(s) according to the mapping rules and between UPF and gNB over the tunnel for the PDU session. QFI marking over Uu is optional (see clause 12) while QFI marking over NG-U is always present. + +Sequence diagram of PDU session establishment between UE, gNB, UPF, and AMF. + +Figure A.1-1: PDU session establishment + +1. UE requests a PDU session establishment to AMF. +2. AMF sends a PDU SESSION RESOURCE SETUP REQUEST message to gNB, which includes the NAS message to be sent to the UE with NAS QoS related information. +3. gNB sends an *RRCReconfiguration* message to UE including the configuration of at least one DRB and the NAS message received at Step 2. +4. UE establishes the DRB(s) for the new PDU session and creates the QFI to DRB mapping rules. +5. UE sends an *RRCReconfiguration Complete* message to gNB. +6. gNB sends a PDU SESSION RESOURCE SETUP RESPONSE message to AMF. +7. User Plane Data can then be exchanged between UE and gNB over DRB(s) according to the mapping rules and between UPF and gNB over the tunnel for the PDU session. QFI marking over Uu is optional (see clause 12) while QFI marking over NG-U is always present. + +### A.2 New QoS Flow with RQoS + +The following figure shows an example message flow when RQoS is used for a new QoS flow. In this example, the gNB receives from UPF a first downlink packet associated with a QFI for which the QoS parameters are known from the PDU session establishment, but for which there is no association to any DRB yet in AS. + +![Sequence diagram for Figure A.2-1: DL data with new QFI sent over existing DRB. The diagram shows interactions between UE, gNB, UPF, and AMF. It starts with '0. PDU Session and DRB(s) established'. Then '1. DL Packet (QFI)' from UPF to gNB. gNB performs '2. Use an existing DRB for the new QoS flow'. Then '3. DL Packet (QFI, RDI)' from gNB to UE. UE performs '4. Mapping rules updated'. Finally, '5. UP Data (QFI)' is exchanged between UE and gNB, and between gNB and UPF.](1b50f9f141d3d1a1de52e959f85f8fc2_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB + participant UPF + participant AMF + Note over UE, gNB, UPF, AMF: 0. PDU Session and DRB(s) established + UPF->>gNB: 1. DL Packet (QFI) + Note right of gNB: 2. Use an existing DRB for the new QoS flow + gNB->>UE: 3. DL Packet (QFI, RDI) + Note left of UE: 4. Mapping rules updated + UE->>gNB: 5. UP Data (QFI) + gNB->>UPF: 5. UP Data (QFI) + +``` + +Sequence diagram for Figure A.2-1: DL data with new QFI sent over existing DRB. The diagram shows interactions between UE, gNB, UPF, and AMF. It starts with '0. PDU Session and DRB(s) established'. Then '1. DL Packet (QFI)' from UPF to gNB. gNB performs '2. Use an existing DRB for the new QoS flow'. Then '3. DL Packet (QFI, RDI)' from gNB to UE. UE performs '4. Mapping rules updated'. Finally, '5. UP Data (QFI)' is exchanged between UE and gNB, and between gNB and UPF. + +**Figure A.2-1: DL data with new QFI sent over existing DRB** + +0. PDU session and DRB(s) have been already established. +1. gNB receives a downlink packet with a new QFI from UPF. +2. gNB decides to send the new QoS flow over an existing DRB. + +NOTE: If gNB decides to send it over a new DRB, it needs to establish the DRB first. + +3. gNB sends the DL packet over the selected DRB with the new QFI and RDI set in the SDAP header. +4. UE identifies the QFI and RDI in the received DL packet and the DRB on which the packet was received. The AS mapping rules are then updated accordingly. +5. User Plane Data for the new QoS flow can then be exchanged between UE and gNB over the DRB according to the updated mapping rules and between UPF and gNB over the tunnel for the PDU session. + +## A.3 New QoS Flow with Explicit RRC Signalling + +The following figure shows an example message flow when explicit RRC signalling is used for a new QoS flow. In this example, the gNB receives from UPF a first downlink packet associated with a QFI, for which the QoS parameters are already known from the PDU session establishment, but for which there is no association to any DRB yet in AS. + +![Sequence diagram for Figure A.3-1: DL data with new QFI sent over existing DRB. The diagram shows interactions between UE, gNB, UPF, and AMF. It starts with '0. PDU Session and DRB(s) established'. Then '1. DL Packet (QFI)' from UPF to gNB. gNB performs '2. Map new QoS flow to existing DRB'. Then '3. RRCReconfiguration' from gNB to UE. UE performs '4. Mapping rules updated'. Then '5. RRCReconfigurationComplete' from UE to gNB. Finally, '6. UP Data (QFI)' is exchanged between UE and gNB, and between gNB and UPF.](e94f8f1631cc515867e8c0ebd1bac7fe_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB + participant UPF + participant AMF + Note over UE, gNB, UPF, AMF: 0. PDU Session and DRB(s) established + UPF->>gNB: 1. DL Packet (QFI) + Note right of gNB: 2. Map new QoS flow to existing DRB + gNB->>UE: 3. RRCReconfiguration + Note left of UE: 4. Mapping rules updated + UE->>gNB: 5. RRCReconfigurationComplete + UE->>gNB: 6. UP Data (QFI) + gNB->>UPF: 6. UP Data (QFI) + +``` + +Sequence diagram for Figure A.3-1: DL data with new QFI sent over existing DRB. The diagram shows interactions between UE, gNB, UPF, and AMF. It starts with '0. PDU Session and DRB(s) established'. Then '1. DL Packet (QFI)' from UPF to gNB. gNB performs '2. Map new QoS flow to existing DRB'. Then '3. RRCReconfiguration' from gNB to UE. UE performs '4. Mapping rules updated'. Then '5. RRCReconfigurationComplete' from UE to gNB. Finally, '6. UP Data (QFI)' is exchanged between UE and gNB, and between gNB and UPF. + +**Figure A.3-1: DL data with new QFI sent over existing DRB** + +0. PDU session and DRB(s) have been already established. +1. gNB receives a downlink packet with a new QFI from UPF. + +2. gNB decides to send the new QoS flow over an existing DRB using explicit RRC signalling for updating the AS mapping rules. +3. gNB sends an *RRReconfiguration* message to UE with the new QFI to DRB mapping rule. gNB may also decide to update the DRB configuration if required to meet the QoS requirements for the new QoS Flow. +4. UE updates the QFI to DRB mapping rules and configuration (if received). +5. UE sends an *RRReconfigurationComplete* message to gNB. +6. User Plane Data for the new QoS flow can then be exchanged between UE and gNB over the DRB according to the updated mapping rules and between UPF and gNB over the tunnel for the PDU session. + +## A.4 New QoS Flow with Explicit NAS Signalling + +The following figure shows an example message flow when the gNB receives a new QoS flow establishment request from CN that involves NAS explicit signalling. The QoS flow establishment request provides the gNB and UE with the QoS parameters for the QFI. In this example, the gNB decides to establish a new DRB (rather than re-use an existing one) for this QoS flow and provides the mapping rule over RRC signalling. NAS procedures details between gNB and 5GC can be found in TS 23.501 [3], TS 23.502 [22] and TS 38.413 [26]. + +![Sequence diagram showing the message flow for establishing a new QoS flow with explicit NAS signalling. The diagram involves four entities: UE, gNB, UPF, and AMF. The process starts with an initial state '0. PDU Session and DRB(s) established'. The AMF sends a '1. PDU SESSION RESOURCE MODIFY REQUEST (QFI)' to the gNB. The gNB then performs an internal step '2. Set up new DRB'. Next, the gNB sends a '3. RRReconfiguration' message to the UE. The UE responds with '4. New DRB established' and '5. RRReconfigurationComplete' to the gNB. The gNB then sends a '6. PDU SESSION RESOURCE MODIFY RESPONSE' to the AMF. Finally, '7. UP Data (QFI)' is exchanged between the UE and gNB, and between the gNB and UPF.](c7973a89da29a4a59561e36561984333_img.jpg) + +``` +sequenceDiagram + participant UE + participant gNB + participant UPF + participant AMF + Note over UE, gNB, UPF, AMF: 0. PDU Session and DRB(s) established + AMF->>gNB: 1. PDU SESSION RESOURCE MODIFY REQUEST (QFI) + gNB->>gNB: 2. Set up new DRB + gNB->>UE: 3. RRReconfiguration + UE->>gNB: 4. New DRB established + UE->>gNB: 5. RRReconfigurationComplete + gNB->>AMF: 6. PDU SESSION RESOURCE MODIFY RESPONSE + UE->>gNB: 7. UP Data (QFI) + gNB->>UPF: 7. UP Data (QFI) +``` + +Sequence diagram showing the message flow for establishing a new QoS flow with explicit NAS signalling. The diagram involves four entities: UE, gNB, UPF, and AMF. The process starts with an initial state '0. PDU Session and DRB(s) established'. The AMF sends a '1. PDU SESSION RESOURCE MODIFY REQUEST (QFI)' to the gNB. The gNB then performs an internal step '2. Set up new DRB'. Next, the gNB sends a '3. RRReconfiguration' message to the UE. The UE responds with '4. New DRB established' and '5. RRReconfigurationComplete' to the gNB. The gNB then sends a '6. PDU SESSION RESOURCE MODIFY RESPONSE' to the AMF. Finally, '7. UP Data (QFI)' is exchanged between the UE and gNB, and between the gNB and UPF. + +**Figure A.4-1: DL data with new QoS Flow ID sent over new DRB with explicit signalling** + +0. PDU session DRB(s) have been already established. +1. gNB receives a PDU SESSION RESOURCE MODIFY REQUEST message from AMF for a new QoS flow. +2. If gNB cannot find an existing DRB to map this new QoS flow, it decides to establish a new DRB. +3. gNB sends an *RRReconfiguration* message to UE including the DRB configuration with the new QFI to DRB mapping rule and the NAS message received at step 1. +4. UE establishes the DRB for the new QoS flow associated with this PDU session and updates the mapping rules. +5. UE sends an *RRReconfigurationComplete* message to gNB. +6. gNB sends a PDU SESSION RESOURCE MODIFY RESPONSE message to AMF. +7. User Plane Data can then be exchanged between UE and gNB over DRB(s) according to the mapping rules and between UPF and gNB over the tunnel for the PDU session. + +## A.5 Release of QoS Flow with Explicit Signalling + +The following figure shows an example message flow when the gNB receives a request to release a QoS flow from CN that involves explicit NAS signalling. NAS procedures details between gNB and 5GC can be found in TS 23.501 [3], TS 23.502 [22] and TS 38.413 [26]. + +![Sequence diagram showing the release of a QoS flow with explicit signalling between UE, gNB, UPF, and AMF.](1c3a7d87de139c7d44f40acec0e4f3fb_img.jpg) + +``` +sequenceDiagram + participant UE + participant gNB + participant UPF + participant AMF + Note over UE, gNB, UPF, AMF: 0. PDU Session and DRB(s) established + AMF->>gNB: 1. PDU SESSION RESOURCE MODIFY REQUEST + Note right of gNB: 2. Release QoS flow mapping + gNB->>UE: 3. RRCReconfiguration + Note left of UE: 4. Mapping rules updated + UE->>gNB: 5. RRCReconfigurationComplete + gNB->>AMF: 6. PDU SESSION RESOURCE MODIFY RESPONSE +``` + +The diagram illustrates a sequence of messages for releasing a QoS flow. It starts with a state where the PDU Session and DRB(s) are established. The AMF sends a PDU SESSION RESOURCE MODIFY REQUEST to the gNB. The gNB then performs an internal action to release the QoS flow mapping. Next, the gNB sends an RRCReconfiguration message to the UE. The UE updates its mapping rules and responds with RRCReconfigurationComplete. Finally, the gNB sends a PDU SESSION RESOURCE MODIFY RESPONSE back to the AMF. + +Sequence diagram showing the release of a QoS flow with explicit signalling between UE, gNB, UPF, and AMF. + +Figure A.5-1: Release of QoS Flow with Explicit Signalling + +0. PDU session and DRB(s) have been already established. +1. gNB receives a PDU SESSION RESOURCE MODIFY REQUEST message from AMF to release a QoS flow. +2. The gNB decides to release corresponding the QFI to DRB mapping rule. Since the DRB also carries other QoS flows, the DRB is not released. +3. gNB sends an *RRCReconfiguration* message to UE to release the QFI to DRB mapping rule. +4. UE updates the AS QFI to DRB mapping rules to release this QFI to DRB mapping rule. +5. UE sends an *RRCReconfigurationComplete* message to gNB. +6. gNB sends a PDU SESSION RESOURCE MODIFY RESPONSE message to AMF. + +## A.6 UE Initiated UL QoS Flow + +The following figure shows an example message flow when the UE AS receives an UL packet for a new QoS flow for which a QFI to DRB mapping rule does not exist. + +![Sequence diagram illustrating the uplink packet handling for a new QoS flow. The diagram shows interactions between UE, gNB, UPF, and AMF. Step 0: PDU Session and DRB(s) established. Step 1: UE sends UL packet (QFI) to gNB. Step 2: UE uses Default DRB if no mapping rules. Step 3: UE sends User Data over DRB (QFI) to gNB. Step 4: gNB sends PDU Data Tunnel (QFI) to UPF. Step 5: gNB sends RRC Reconfiguration to UE. Step 6: UE and gNB exchange UP Data (QFI) over the DRB, and gNB and UPF exchange UP Data (QFI) over the tunnel.](4325ad0fb1a0bcc317492c16a5467f71_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB + participant UPF + participant AMF + Note over UE, gNB, UPF, AMF: 0. PDU Session and DRB(s) established + UE->>gNB: 1. UL packet (QFI) + Note right of UE: 2. Default DRB if no mapping rules + UE->>gNB: 3. User Data over DRB (QFI) + gNB->>UPF: 4. PDU Data Tunnel (QFI) + gNB-->>UE: 5. RRC Reconfiguration + UE->>gNB: 6. UP Data (QFI) + gNB->>UPF: 6. UP Data (QFI) + +``` + +Sequence diagram illustrating the uplink packet handling for a new QoS flow. The diagram shows interactions between UE, gNB, UPF, and AMF. Step 0: PDU Session and DRB(s) established. Step 1: UE sends UL packet (QFI) to gNB. Step 2: UE uses Default DRB if no mapping rules. Step 3: UE sends User Data over DRB (QFI) to gNB. Step 4: gNB sends PDU Data Tunnel (QFI) to UPF. Step 5: gNB sends RRC Reconfiguration to UE. Step 6: UE and gNB exchange UP Data (QFI) over the DRB, and gNB and UPF exchange UP Data (QFI) over the tunnel. + +**Figure A.6-1: UL packet with a new QoS flow for which a mapping does not exist in UE** + +0. PDU session and DRBs (including a default DRB) have been already established. +1. UE AS receives a packet with a new QFI from UE NAS. +2. UE uses the QFI of the packet to map it to a DRB. If there is no mapping of the QFI to a DRB in the AS mapping rules for this PDU session, then the packet is assigned to the default DRB. +3. UE sends the UL packet on the default DRB. The UE includes the QFI in the SDAP header. +4. gNB sends UL packets to UPF and includes the corresponding QFI. +5. If gNB wants to use a new DRB for this QoS flow, it sets up one. It can also choose to move the QoS flow to an existing DRB using RQoS or RRC signalling (see clauses A.2 and A.3). +6. User Plane Data for the new QoS flow can then be exchanged between UE and gNB over the DRB according to the updated mapping rules and between UPF and gNB over the tunnel for the PDU session. + +## Annex B (informative): Deployment Scenarios + +### B.1 Supplementary Uplink + +To improve UL coverage for high frequency scenarios, SUL can be configured (see TS 38.101-1 [18]). With SUL, the UE is configured with 2 ULs for one DL of the same cell as depicted on Figure B.1-1 below: + +![Diagram illustrating the Supplementary Uplink (SUL) scenario. A User Equipment (UE) icon is shown on the left, and a base station icon is on the right. The base station is surrounded by two concentric green ellipses representing the downlink (DL) coverage area. Below the base station, a green rectangular block represents the uplink (UL) coverage area, with an arrow pointing to the right, indicating the direction of the uplink transmission.](59fdc1219e09c18d6a39e47092e3194d_img.jpg) + +Diagram illustrating the Supplementary Uplink (SUL) scenario. A User Equipment (UE) icon is shown on the left, and a base station icon is on the right. The base station is surrounded by two concentric green ellipses representing the downlink (DL) coverage area. Below the base station, a green rectangular block represents the uplink (UL) coverage area, with an arrow pointing to the right, indicating the direction of the uplink transmission. + +Figure B.1-1: Example of Supplementary Uplink + +### B.2 Multiple SSBs in a carrier + +For a UE in RRC\_CONNECTED, the BWPs configured by a serving cell may overlap in the frequency domain with the BWPs configured for other UEs by other cells within a carrier. Multiple SSBs may also be transmitted within the frequency span of a carrier used by the serving cell. However, from the UE perspective, each serving cell is associated to at most a single SSB. Figure B.2-1 below describes a scenario with multiple SSBs in a carrier, identifying two different cells (NCGI = 5, associated to SSB1, and NCGI = 6, associated to SSB3) with overlapping BWPs, and where RRM measurements can be configured to be performed by the UE on each of the available SSBs, i.e. SSB1, SSB2, SSB3 and SSB4. + +![Figure B.2-1: Example of multiple SSBs in a carrier. The diagram shows a carrier with four SSBs (SSB1, SSB2, SSB3, SSB4). SSB1 and SSB3 are associated with RMSI NCGI = 5 and NCGI = 6 respectively. Below the carrier, three UEs are shown with their initial and dedicated bandwidth parts (BWPs). UE 1 (connected to NCGI 5) has an initial BWP, dedicated BWP1, and dedicated BWP2. UE 2 (connected to NCGI 5) has an initial BWP and dedicated BWP1. UE 3 (connected to NCGI 6) has an initial BWP, dedicated BWP1, and dedicated BWP2. A frequency axis is shown at the bottom.](a74659686b764b14e7d9992d73e3a274_img.jpg) + +The diagram illustrates the frequency domain representation of a carrier and the bandwidth parts (BWPs) for three User Equipment (UE) devices. At the top, a horizontal line represents the 'Carrier'. Below it, four Synchronization Signal Blocks (SSBs) are shown: SSB1 (pink), SSB2 (grey), SSB3 (pink), and SSB4 (grey). Above SSB1 and SSB3 are yellow boxes indicating RMSI NCGI values: 'RMSI NCGI = 5' for SSB1 and 'RMSI NCGI = 6' for SSB3. Below the carrier, three UEs are shown with their BWPs: + + +- UE 1 connected to NCGI 5:** Shows an 'Initial BWP' (light green) starting at the beginning, followed by 'Dedicated BWP1' (light green) which extends across the middle, and 'Dedicated BWP2' (light green) starting towards the right. +- UE 2 connected to NCGI 5:** Shows an 'Initial BWP' (light blue) starting at the beginning, followed by 'Dedicated BWP1' (light blue) which extends across the middle. +- UE 3 connected to NCGI 6:** Shows an 'Initial BWP' (light orange) starting towards the right, followed by 'Dedicated BWP1' (light orange) which extends across the middle, and 'Dedicated BWP2' (light orange) starting towards the right. + + At the bottom, a horizontal line with an arrow pointing right is labeled 'Frequency'. + +Figure B.2-1: Example of multiple SSBs in a carrier. The diagram shows a carrier with four SSBs (SSB1, SSB2, SSB3, SSB4). SSB1 and SSB3 are associated with RMSI NCGI = 5 and NCGI = 6 respectively. Below the carrier, three UEs are shown with their initial and dedicated bandwidth parts (BWPs). UE 1 (connected to NCGI 5) has an initial BWP, dedicated BWP1, and dedicated BWP2. UE 2 (connected to NCGI 5) has an initial BWP and dedicated BWP1. UE 3 (connected to NCGI 6) has an initial BWP, dedicated BWP1, and dedicated BWP2. A frequency axis is shown at the bottom. + +Figure B.2-1: Example of multiple SSBs in a carrier + +## B.3 NR Operation with Shared Spectrum + +NR Radio Access operating with shared spectrum channel access can support the following deployment scenarios: + +- Scenario A: Carrier aggregation between NR in licensed spectrum (SpCell) and NR in shared spectrum (SCell); + - Scenario A.1: SCell is not configured with uplink (DL only); + - Scenario A.2: SCell is configured with uplink (DL+UL). +- Scenario B: Dual connectivity between LTE in licensed spectrum and NR in shared spectrum (PSCell); +- Scenario C: NR in shared spectrum (PCell); +- Scenario D: NR cell in shared spectrum and uplink in licensed spectrum; +- Scenario E: Dual connectivity between NR in licensed spectrum (PCell) and NR in shared spectrum (PSCell). + +Carrier aggregation of cells in shared spectrum is applicable to all deployment scenarios. + +## B.4 Example implementation of Non-Terrestrial Networks + +The following figure illustrates an example implementation of a Non-Terrestrial Network for transparent NTN payload: + +![Figure B.4-1: NTN based NG-RAN architecture diagram. The diagram shows a User Equipment (UE) connected to a gNB via an NR-Uu service link. The gNB is divided into two main parts: the NTN Service Link provisioning System and the non-NTN infrastructure gNB functions. The NTN Service Link provisioning System contains an NTN-Payload (represented by a satellite and a HAPS) and an NTN-Gateway, connected by a feeder link. The non-NTN infrastructure gNB functions are connected to the 5GC via an NG interface. The NTN infrastructure, which includes the NTN Service Link provisioning System and the NTN Control function, is shown as a dashed box. The O&M function is also connected to the non-NTN infrastructure gNB functions.](4c815618b2aaed14f81e59f6272d6511_img.jpg) + +Figure B.4-1: NTN based NG-RAN architecture diagram. The diagram shows a User Equipment (UE) connected to a gNB via an NR-Uu service link. The gNB is divided into two main parts: the NTN Service Link provisioning System and the non-NTN infrastructure gNB functions. The NTN Service Link provisioning System contains an NTN-Payload (represented by a satellite and a HAPS) and an NTN-Gateway, connected by a feeder link. The non-NTN infrastructure gNB functions are connected to the 5GC via an NG interface. The NTN infrastructure, which includes the NTN Service Link provisioning System and the NTN Control function, is shown as a dashed box. The O&M function is also connected to the non-NTN infrastructure gNB functions. + +**Figure B.4-1: NTN based NG-RAN** + +The gNB depicted in Figure B.4-1 may be subdivided into non-NTN infrastructure gNB functions and the NTN Service Link provisioning system. The NTN infrastructure may be thought of being subdivided into the NTN Service Link provisioning system and the NTN Control function. The NTN Service Link provisioning system may consist of one or more NTN payloads and NTN Gateways. + +The NTN payload is embarked on a spaceborne (or airborne) vehicle, providing a structure, power, commanding, telemetry, attitude control for the satellite (resp. HAPS) and possibly an appropriate thermal environment, radiation shielding. + +The NTN Service Link provisioning system maps the NR-Uu radio protocol over radio resources of the NTN infrastructure (e.g. beams, channels, Tx power). + +The NTN control function controls the spaceborne (or airborne) vehicles as well as the radio resources of the NTN infrastructure (NTN payload(s) & NTN Gateway(s)). It provides control data, e.g. Ephemeris, to the non-NTN infrastructure gNB functions of the gNB. + +Provision of NTN control data to the gNB is out of 3GPP scope. + +**NOTE:** The transport of NR-Uu protocol between the NTN Service Link provisioning system and the non-NTN infrastructure gNB functions is out of 3GPP scope. + +At least the following NTN related parameters are expected to be provided by O&M to the gNB for its operation: + +a) Earth-fixed beams: for each beam provided by a given NTN-payload: + +- The Cell identifier (NG and Uu) mapped to the beam; +- The Cell's reference location (e.g. cell's center and range). + +b) Quasi-Earth-fixed: for each beam provided by a given NTN payload: + +- The Cell identifier (NG and Uu) and time window mapped to a beam; +- The Cell's/beam's reference location (e.g. cell's center and range); +- The time window of the successive switch overs (feeder link, service link); +- The identifier and time window of all serving satellites (resp. HAPS) and NTN Gateways. + +c) Earth moving beams: for each beam provided by a given NTN payload: + +- The Uu Cell identifier mapped to a beam and mapping information to fixed geographical areas reported on NG, including information about the beams direction and motion of the beam's foot print on Earth; +- Its elevation wrt NTN payload; +- Schedule of successive serving NTN Gateways/gNBs; + +- Schedule of successive switch overs (feeder link, service link). + +## Annex C (informative): I-RNTI Reference Profiles + +The I-RNTI provides the new NG-RAN node a reference to the UE context in the old NG-RAN node. How the new NG-RAN node is able to resolve the old NG-RAN ID from the I-RNTI is a matter of proper configuration in the old and new NG-RAN node. + +Table C-1 below provides some typical partitioning of a 40bit I-RNTI, assuming the following content: + +- **UE specific reference:** reference to the UE context within a logical NG-RAN node; +- **NG-RAN node address index:** information to identify the NG-RAN node that has allocated the UE specific part; + +NOTE: **RAT-specific information** may be introduced in a later release, containing information to identify the RAT of the cell within which the UE was sent to RRC\_INACTIVE. This version of the specification only supports intra-RAT mobility of UEs in RRC\_INACTIVE. + +- **PLMN-specific information:** information supporting network sharing deployments, providing an index to the PLMN ID part of the Global NG-RAN node identifier. + +**Table C-1: I-RNTI reference profiles** + +| Profile ID | UE specific reference | NG-RAN node address index (e.g., gNB ID, eNB ID) | RAT-specific information | PLMN-specific information | Comment | +|------------|-----------------------------|--------------------------------------------------|--------------------------|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------| +| 1 | 20 bits (~1 million values) | 20 bits (~1 million values) | N/A | N/A | NG-RAN node address index may be very well represented by the LSBs of the gNB ID. This profile may be applicable for any NG-RAN RAT. | +| 2 | 20 bits (~1 million values) | 16 bits (65.000 nodes) | N/A | 4 bits (Max 16 PLMNs) | Max number of PLMN IDs broadcast in NR is 12. This profile may be applicable for any NG-RAN RAT. | +| 3 | 24 bits (16 million values) | 16 bits (65.000 nodes) | N/A | N/A | Reduced node address to maximise addressable UE contexts. This profile may be applicable for any NG-RAN RAT. | + +--- + +## Annex D (informative): SPID ranges and mapping of SPID values to cell reselection and inter-RAT/inter frequency handover priorities + +The SPID values are defined in Annex I of TS 36.300 [2]. + +From the SPID reference values, only the SPID=253 also applies for 5GC. + +--- + +## Annex E (informative): NG-RAN Architecture for Radio Access Network Sharing with multiple cell ID broadcast + +Each NG-RAN node serving a cell identified by a Cell Identity associated with either a subset of PLMNs, or a subset of SNPNs, or a subset of PNI-NPNs is connected to another NG-RAN node via a single Xn-C interface instance. + +Each Xn-C interface instance is setup and removed individually. + +Xn-C interface instances terminating at NG-RAN nodes which share the same physical radio resources may share the same signalling transport resources. If this option is applied: + +- Non-UE associated signalling is associated to an Xn-C interface instance by including an Interface Instance Indication in the XnAP message; +- Node related, non-UE associated Xn-C interface signalling may provide information destined for multiple logical nodes in a single XnAP procedure instance once the Xn-C interface instance is setup; + +NOTE 1: If the Interface Instance Indication corresponds to more than one interface instance, the respective XnAP message carries information destined for multiple logical nodes. + +- A UE associated signalling connection is associated to an Xn-C interface instance by allocating values for the corresponding NG-RAN node UE XnAP IDs so that they can be mapped to that Xn-C interface instance. + +NOTE 2: One possible implementation is to partition the value ranges of the NG-RAN node UE XnAP IDs and associate each value range with an Xn-C interface instance. + +## Annex F (normative): Use and structure of the I-RNTI + +The I-RNTI provides an NG-RAN node with a reference to the UE context and a reference to the NG-RAN node that allocated the UE context. + +To support an NG-RAN node in resolving the Local NG-RAN ID of the NG-RAN node that allocated the UE context, the I-RNTI structure is as follows: + +- the first part (starting from the MSB of the I-RNTI) identifies the I-RNTI profile. It is 2 bits long for a Full I-RNTI or 1 bit long for a short I-RNTI, and it indicates the length of a Local NG-RAN Node Identifier of the NG-RAN Node that allocated the I-RNTI; +- the second part, immediately following the first part, is a Local NG-RAN Node Identifier; +- the third part, immediately following the second part, identifies the UE context stored in the NG-RAN node that allocated the I-RNTI. + +In case a NG-RAN node takes an additional Local NG-RAN Node identifier into use or removes a Local NG-RAN Node identifier currently in use it informs its neighbour NG-RAN nodes about this change. + +The I-RNTI profiles for Full I-RNTI are described in table F-1. + +**Table F-1: I-RNTI profiles for Full I-RNTI** + +| I-RNTI Profile Identity | I-RNTI profile value (binary encoding) | +|-------------------------|----------------------------------------| +| 0 | 0b00 | +| 1 | 0b01 | +| 2 | 0b10 | +| 3 | 0b11 | + +The I-RNTI profiles for Short I-RNTI are described in table F-2. + +**Table F-2: I-RNTI profiles for Short I-RNTI** + +| I-RNTI Profile Identity | I-RNTI profile value (binary encoding) | +|-------------------------|----------------------------------------| +| 0 | 0b0 | +| 1 | 0b1 | + +# Annex G (informative): Components of Mobility Latency + +HO interruption time for L1/L2-based inter-cell mobility is the time from UE receives the cell switch command to UE performs the first DL/UL reception/transmission on the indicated beam of the target cell. + +For Rel-18, RAN2 assumed the latency of the mobility procedure is characterized by the terms illustrated in Figure G-1. + +![Figure G-1: Components of Mobility Latency. A timeline diagram showing the sequence of events for LTM candidate configuration, LTM Cell Switch Command, UE Reconfiguration, T/F tracking, UL synchronization, and final data transmission. The interruption period is marked between the command and the first data transmission.](154b6a4d11b55f7fd962c3e201664066_img.jpg) + +The diagram illustrates the components of mobility latency for LTM. It starts with 'LTM candidate configuration' and 'LTM Cell Switch Command'. The 'UE Reconfiguration' phase includes $T_{RRc}$ , $T_{cmd}$ , $T_{LTM-RRC-processing}$ , and $T_{LTM-processing}$ . The 'T/F tracking' phase includes $T_{first-RS}$ and $T_{RS-proc}$ . The 'UL synchronization' phase includes $T_{LTM-IU}$ and $T_{RAR}$ . The final phase is 'Data using indicated beam' with $T_{first-data}$ . The 'Interruption' period is shown between the start of the command and the start of the first data transmission. + +Figure G-1: Components of Mobility Latency. A timeline diagram showing the sequence of events for LTM candidate configuration, LTM Cell Switch Command, UE Reconfiguration, T/F tracking, UL synchronization, and final data transmission. The interruption period is marked between the command and the first data transmission. + +Figure G-1: Components of Mobility Latency + +Each component of mobility latency is described in the table below, the values of which are specified in TS 38.133[13]. + +Table G-1: Components of Mobility Latency + +| Component | Meaning | +|--------------------------|------------------------------------------------------------------------------------------------------------------| +| $T_{RRc}$ | Processing time for RRCReconfiguration carrying candidate configurations | +| $T_{cmd}$ | Time for processing L1/L2-command (HARQ and parsing) | +| $T_{LTM-RRC-processing}$ | Early ASN.1 decoding and validity/compliance check | +| $T_{LTM-processing}$ | UE processing including applying target cell parameters and L1/L2 change | +| $T_{first-RS}$ | Time for fine tracking and acquiring full timing information | +| $T_{RS-proc}$ | Time for SSB processing | +| $T_{LTM-IU}$ | Interruption uncertainty in acquiring the first UL transmission | +| $T_{RAR}$ | Time for RAR delay | +| $T_{first-data}$ | Time for UE performs the first DL/UL reception/ transmission on the indicated beam of the target cell, after RAR | + +For Rel-18, RAN2 assumed that the latency of the RACH-based and RACH-less LTM procedure is characterized by the terms illustrated in Figure G-2 and Figure G-3. The overall mobility latency of LTM can be largely reduced by early synchronization procedure. + +![Figure G-2: Mobility Latency for RACH-based LTM. A timeline diagram similar to Figure G-1 but with an additional 'DL Synchronization' phase following the command. The interruption period is shorter than in Figure G-1.](2d57a58ef48bbac3b7ea3da33b105f2d_img.jpg) + +This diagram shows the mobility latency for RACH-based LTM. It includes an additional 'DL Synchronization' phase (orange box) immediately following the 'LTM Cell Switch Command'. The 'UE Reconfiguration' phase follows, containing $T_{RRc}$ , $T_{cmd}$ , $T_{LTM-RRC-processing}$ , and $T_{LTM-processing}$ . The 'T/F tracking' phase ( $T_{first-RS}$ , $T_{RS-proc}$ ) and 'UL synchronization' phase ( $T_{LTM-IU}$ , $T_{RAR}$ ) follow. The final 'Data using indicated beam' phase ( $T_{first-data}$ ) occurs after. The 'Interruption' period is marked from the start of the command to the start of the first data transmission. + +Figure G-2: Mobility Latency for RACH-based LTM. A timeline diagram similar to Figure G-1 but with an additional 'DL Synchronization' phase following the command. The interruption period is shorter than in Figure G-1. + +Figure G-2: Mobility Latency for RACH-based LTM + +![Timing diagram for RACH-less LTM mobility latency showing the sequence from configuration to data transmission in a new cell.](38e67fda26b37cfba4e5ffa0f0fa61ab_img.jpg) + +The diagram illustrates the timing sequence for RACH-less LTM mobility. It begins with an arrow pointing to **LTM candidate configuration**. The sequence of time blocks is as follows: + +- An initial interval $T_{RRC}$ leads into a block for **DL Synchronization** (orange dashed outline). +- This is followed by **UL Synchronization** (blue dashed outline), with an arrow pointing to a **Preamble**. +- An **LTM Cell Switch Command** triggers the next phase at time $T_{cmd}$ . +- The **UE Reconfiguration** phase (grey dashed outline) consists of two sub-blocks: $T_{\text{LTM-RRC-processing}}$ and $T_{\text{LTM-processing}}$ . +- Finally, a green block $T_{\text{first-data}}$ represents the time until **Data using indicated beam** is sent. + +An **Interruption** period is marked with a horizontal line starting from the beginning of the UE Reconfiguration phase and ending at the start of the $T_{\text{first-data}}$ block, leading to the **New Cell & TCI state**. + +Timing diagram for RACH-less LTM mobility latency showing the sequence from configuration to data transmission in a new cell. + +**Figure G-3: Mobility Latency for RACH-less LTM** + +## Annex H (informative): Change history + +| Change history | | | | | | | | +|----------------|------------|------------|----|-----|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New Version | +| 2017.03 | RAN2 97bis | R2-1702627 | - | - | - | First version. | 0.1.0 | +| 2017.04 | RAN2 97bis | R2-1703825 | - | - | - | Editorial Updates:
- Stage 2 Details of ARQ operation marked as FFS
- Placeholder for CU/DU Split overview added
- Outdated editor notes removed
- Protocol Architecture updated
- NG-RAN terminology aligned
- Header placement in the L2 overview put as FFS | 0.1.1 | +| 2017.04 | RAN2 97bis | R2-1703952 | - | - | - | Editorial Updates:
- description of measurements for mobility clarified
- some cell reselection details put FFS
- outdated references removed | 0.1.2 | +| 2017.04 | RAN2 98 | R2-1704296 | - | - | - | Editorial updates:
- NG interfaces naming aligned to RAN3
- 5GC used consistently
- Statement on lossless delivery removed from 9.3.2
- Overview of PDCP function for CP detailed | 0.1.3 | +| 2017.05 | RAN2 98 | R2-1704298 | - | - | - | Agreements of RAN2#97bis captured:
- overview of duplication operation
- RLC modes for DRBs and SRBs
- Condition for lossless mobility
- L2 handling at handover
- RLF triggers
- Measurement details (filtering, beams, quality...)
- QoS flow handling in DC
- RACH procedure message usage for on-demand SI
- Random Access Procedure triggers
- DRX baseline | 0.2.0 | +| 2017.05 | RAN2 98 | R2-1704452 | - | - | - | RAN3 agreements captured (R3-171329)
5G logo and specification title updated | 0.2.1 | +| 2017.05 | RAN2 98 | R2-1705994 | - | - | - | RLC failure for RLF generalized. | 0.3.0 | +| 2017.06 | RAN2 98 | R2-1706204 | - | - | - | Agreements of RAN2#98 captured:
- Duplication Control
- RLC mode for SRB0 and System Info
- Provision of Assistance Info for AMF Selection
- QoS Handling from R2-1706011
- Beam measurements combining
- MSG1 request details for on-demand SI
- RNA and RLAU terminology introduced for INACTIVE
- Skipping of SPS resources when nothing to transmit
- Duplication detection at RLC only for AM
- Provision of access category by NAS for connection control
Editorial updates in addition:
- QFI used consistently | 0.3.1 | +| 2017.06 | RAN2 98 | R2-1706205 | - | - | - | RAN3 agreements captured (R3-171932) | 0.4.0 | +| 2017.06 | RAN2 98 | R2-1706206 | - | - | - | Corrections:
- provision of AC in INACTIVE is FFS
- agreements on measurement moved from 9.2.1.1 to 9.2.4 | 0.4.1 | +| 2017.06 | NR Adhoc 2 | R2-1706540 | - | - | - | Editorial corrections
Agreement on RLC Segmentation captured
Duplicated statement in 9.2.1.1. and 7.3 removed | 0.5.0 | +| 2017.08 | RAN2 99 | R2-1707748 | - | - | - | Agreements of RAN2 NR June Adhoc captured:
- TP on Security in R2-1707466
- TP on Measurement Model in R2-1707480
- NCR Acronym addition
- Duplication control details
- UE capabilities and band combinations
- Disabling of PDPC reordering as PDCP function
- On-Demand SI and RACH details
- Measurement Report Characteristics
- Mapping rules update handling
- UE Capabilities and Band Combination handling
In addition:
- ARQ overview aligned with Stage 3 agreements | 0.6.0 | + +| | | | | | | | | +|---------|------------|------------|------|---|---|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| | | | | | | - L2 Data Flow aligned with Stage 3 agreements
- References updated
RAN3 TP incorporated (R3-172610) | | +| 2017.08 | RAN2 99 | R2-1709937 | - | - | - | Agreements of RAN2 99 captured:
- QoS update in R2-1709830
- Description of the RRC states in R2-1707690
- Correction on RRC_INACTIVE state in R2-1709833
- LCP description in R2-1709829
- Baseline HO procedure update in R2-1709850 with corrections
- UE identities in R2-1709868
- Radio Link Failure handling in R2-1709870
- RAN3 agreements on roaming restrictions in R3-172655
- Integrity protection configurable on a per DRB basis
- Various Acronyms added
- Slicing details
- PWS basic principles
- UE capability restrictions | 0.7.0 | +| 2017.09 | RAN 77 | RP-171730 | - | - | - | Provided for information to RAN | 1.0.0 | +| 2017.10 | RAN2 99bis | R2-1710693 | - | - | - | Editorial Updates and Corrections:
- inter RAT mobility in 9.3.2 restructured
- SON promoted to top clause level (as it is not a vertical)
- Obsolete clauses 14 and 15 removed.
- Description of paging in idle aligned with 23.501
- I-RNTI suggested for INACTIVE
- Missing agreement from RAN2 99 on INACTIVE captured | 1.0.1 | +| 2017.10 | RAN2 99bis | R2-1711936 | - | - | - | Clean version | 1.1.0 | +| 2017.10 | RAN2 99bis | R2-1711972 | - | - | - | Corrections:
- Container for mobility in 9.2.3.2.1
- "HO" changed to "handover" for consistency
Agreements from RAN2 99bis captured:
- URLLC text in R2-1710253
- Clarification on RRC States in R2-1710074
- Resume ID terminology in R2-1711778
- Slicing clarifications in R2-1712034
- Usage of SRB0 and SRB1 in INACTIVE
- Prioritisation of RACH resources for handover
- SPS configuration per SCell in CA
- Enabling / Disabling IP on DRB via handover only
- First agreements on Supplementary Uplink
- Maximum supported data rate calculation
RAN3 agreements:
- R3-173639 on Rapporteur updates to RAN3-related clauses
- R3-174162 on AMF discovery by NG-RAN
- R3-174187 on RAN paging failure handling in RRC_INACTIVE
- R3-174188 on Unreachability in RAN Inactive State
- R3-174225 on Inter System Handover
- R3-174230 on RRC Inactive Assistant Information
RAN agreement:
- RP-172113 on UE categories. | 1.1.1 | +| 2017.11 | RAN2 100 | R2-1712266 | - | - | - | Clean version | 1.2.0 | +| 2017.11 | RAN2 100 | R2-1712355 | - | - | - | Editorial Clean Up:
- Editor's Notes & relevant FFS moved to R2-17112357
- Protocol stack figures for NG interface updated
- Dual Connectivity changed to Multi-RAT connectivity
- Details about SI handling added to tackle RMSI
- Access Control updated and reference to 22.261 added
- DC specific details removed (37.340 is used instead)
- Notes numbered wherever required | 1.2.1 | +| 2017.12 | RAN2 100 | R2-174079 | - | - | - | Agreements from RAN2 100 captured:
- QoS update in R2-1714230
- Updates to stage 2 QoS flow in R2-1712687
- BWP Description in R2-172360
- Transition from INACTIVE to CONNECTED in R2-173937
- SUL overview
- Removal of DC related definitions
- BWP agreements
- SPS terminology changed to CS to cover both types
RAN3 agreements in R3-175011
RAN1 agreements in R1-1721728 | 1.2.2 | +| 2017.12 | RAN2 100 | R2-1714252 | - | - | - | Clean version | 1.3.0 | +| 2017.12 | RP-78 | RP-172496 | - | - | - | Provided for approval to RAN | 2.0.0 | +| 2017/12 | RP-78 | | | | | Upgraded to Rel-15 (MCC) | 15.0.0 | +| 2018/03 | RP-79 | RP-180440 | 0009 | 1 | F | Miscellaneous Corrections & Additions | 15.1.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|---------------------------------------------------------------------------------------------------------------------------|--------| +| 2018/06 | RP-80 | RP-181214 | 0010 | 1 | F | Clarification on NR Carrier Aggregation | 15.2.0 | +| | RP-80 | RP-181214 | 0011 | 2 | F | Miscellaneous Corrections | 15.2.0 | +| | RP-80 | RP-181214 | 0012 | 1 | F | Paging Mechanisms | 15.2.0 | +| | RP-80 | RP-181214 | 0013 | 2 | F | Security Update | 15.2.0 | +| | RP-80 | RP-181214 | 0014 | 1 | F | UE Identities | 15.2.0 | +| | RP-80 | RP-181214 | 0015 | 1 | F | Corrections on deactivation of PUCCH SCell | 15.2.0 | +| | RP-80 | RP-181214 | 0022 | 2 | F | Clarification on count wrap around | 15.2.0 | +| | RP-80 | RP-181214 | 0024 | 1 | F | Slicing assistance information | 15.2.0 | +| | RP-80 | RP-181214 | 0025 | - | F | Physical Layer Update | 15.2.0 | +| | RP-80 | RP-181214 | 0026 | 1 | F | Default DRB & QoS Remapping | 15.2.0 | +| | RP-80 | RP-181214 | 0027 | 1 | F | SSB Clarifications | 15.2.0 | +| | RP-80 | RP-181217 | 0029 | 2 | B | CR on U-plane handling for handover | 15.2.0 | +| | RP-80 | RP-181217 | 0030 | 2 | B | CR on message content in inter-RAT handover | 15.2.0 | +| | RP-80 | RP-181215 | 0032 | 1 | F | Clarifications on (de)activation of Duplication and (de)activation of SCells | 15.2.0 | +| | RP-80 | RP-181216 | 0033 | 2 | B | Introduce ANR in NR | 15.2.0 | +| | RP-80 | RP-181215 | 0036 | 1 | F | Corrections to Unified Access Control | 15.2.0 | +| | RP-80 | RP-181215 | 0040 | - | F | Correction to TS 38.300 on Open Issues for Handover | 15.2.0 | +| | RP-80 | RP-181216 | 0041 | - | B | Baseline CR for June version of RAN2 TS 38.300 (RAN3 part) covering agreements of RAN3#100 | 15.2.0 | +| | RP-80 | RP-181216 | 0042 | - | B | Delay budget report and MAC CE adaptation for NR for TS 38.300 | 15.2.0 | +| 2018/09 | RP-81 | RP-181941 | 0035 | 3 | B | ECN support in NR | 15.3.0 | +| | RP-81 | RP-181938 | 0043 | 2 | D | Miscellaneous Clean Up and Corrections | 15.3.0 | +| | RP-81 | RP-181938 | 0045 | 1 | F | Mobility Call Flows | 15.3.0 | +| | RP-81 | RP-181938 | 0046 | 2 | F | QoS Handling Corrections | 15.3.0 | +| | RP-81 | RP-181938 | 0047 | 4 | F | MDBV Enforcement | 15.3.0 | +| | RP-81 | RP-181939 | 0050 | 1 | F | Completion of description of power saving | 15.3.0 | +| | RP-81 | RP-181940 | 0051 | 1 | F | Correction to description of bandwidth adaptation | 15.3.0 | +| | RP-81 | RP-181939 | 0053 | 1 | F | Clarification of PDCP functionality | 15.3.0 | +| | RP-81 | RP-181939 | 0062 | 2 | F | Clarification on number of CC for NR CA | 15.3.0 | +| | RP-81 | RP-181938 | 0070 | 1 | F | Beam management, failure detection and recovery | 15.3.0 | +| | RP-81 | RP-181941 | 0071 | - | F | System Information Handling in TS38.300 | 15.3.0 | +| | RP-81 | RP-181941 | 0072 | 1 | F | Correction on RRC Resume procedure | 15.3.0 | +| | RP-81 | RP-181940 | 0077 | - | F | CR on RACH configuration during HO | 15.3.0 | +| | RP-81 | RP-181941 | 0078 | 1 | F | Missing Call Flows | 15.3.0 | +| | RP-81 | RP-181942 | 0079 | 1 | F | CN type indication for Redirection from NR to E-UTRA | 15.3.0 | +| | RP-81 | RP-181942 | 0080 | 1 | F | QoS Flow to DRB Remapping during Handover | 15.3.0 | +| | RP-81 | RP-181941 | 0081 | 1 | F | NR Corrections (38.300 Baseline CR covering RAN3-101 agreements) | 15.3.0 | +| 2018/10 | - | - | - | - | - | Changes of CR0035 rev 3 were undone since this CR was actually not approved by RAN #81 as it was not submitted to RAN #81 | 15.3.1 | +| 2018/12 | RP-82 | RP-182656 | 0028 | 5 | F | Slice Aware Access Control | 15.4.0 | +| | RP-82 | RP-182649 | 0035 | 4 | B | ECN support in NR | 15.4.0 | +| | RP-82 | RP-182653 | 0074 | 2 | F | Corrections to System Information | 15.4.0 | +| | RP-82 | RP-182655 | 0075 | 2 | F | Stage2 Corrections on UE capability | 15.4.0 | +| | RP-82 | RP-182657 | 0083 | 3 | F | Clarifications on dynamic scheduling | 15.4.0 | +| | RP-82 | RP-182658 | 0084 | 2 | F | Clarification of AMF Switch in RRC_INACTIVE | 15.4.0 | +| | RP-82 | RP-182657 | 0086 | 2 | F | Correction to the system information in Handover Request message | 15.4.0 | +| | RP-82 | RP-182654 | 0087 | 2 | F | Capture signalling flows where the last serving gNB moves the UE to RRC_IDLE | 15.4.0 | +| | RP-82 | RP-182649 | 0088 | 2 | F | Scheduling Request Overview | 15.4.0 | +| | RP-82 | RP-182649 | 0089 | 1 | F | System Information Provisioning | 15.4.0 | +| | RP-82 | RP-182657 | 0090 | 3 | F | Transport of NAS Messages | 15.4.0 | +| | RP-82 | RP-182649 | 0091 | 2 | F | SON Overview | 15.4.0 | +| | RP-82 | RP-182649 | 0093 | 2 | F | RDI handling for data forwarding at handover | 15.4.0 | +| | RP-82 | RP-182656 | 0095 | 2 | F | Clarification on basic voice support | 15.4.0 | +| | RP-82 | RP-182659 | 0096 | 2 | F | Relation between SSB and SS-Burst | 15.4.0 | +| | RP-82 | RP-182659 | 0097 | 3 | F | Defining inter-system and intra-system handover | 15.4.0 | +| | RP-82 | RP-182659 | 0099 | 3 | F | Correction regarding key deletion at state transition to RRC_IDLE | 15.4.0 | +| | RP-82 | RP-182656 | 0102 | 2 | F | Clarification on SSB-based BM, RLM and BFD | 15.4.0 | +| | RP-82 | RP-182653 | 0103 | 1 | F | Correction to beam failure detection in Stage-2 | 15.4.0 | +| | RP-82 | RP-182655 | 0106 | 2 | F | Random Access Triggers | 15.4.0 | +| | RP-82 | RP-182649 | 0107 | - | F | Correction of BWP adaptation | 15.4.0 | +| | RP-82 | RP-182657 | 0108 | 1 | F | Notification Control | 15.4.0 | +| | RP-82 | RP-182665 | 0109 | 1 | F | PDU Session AMBR | 15.4.0 | +| | RP-82 | RP-182649 | 0110 | - | F | Logical channel restrictions clarifications and correction | 15.4.0 | +| | RP-82 | RP-182666 | 0111 | 2 | F | CORESET#0 | 15.4.0 | +| | RP-82 | RP-182659 | 0115 | 2 | F | Corrections to activation of SCells | 15.4.0 | +| | RP-82 | RP-182657 | 0116 | 1 | F | Description of RLM aspects | 15.4.0 | +| | RP-82 | RP-182651 | 0120 | - | F | Minor corrections to paging | 15.4.0 | +| | RP-82 | RP-182659 | 0125 | 1 | F | Clarification on power ramping counter | 15.4.0 | +| | RP-82 | RP-182658 | 0127 | 1 | F | Corrections on the descriptions of active BWP | 15.4.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|---------------------------------------------------------------------------------------------------------------|--------| +| | RP-82 | RP-182653 | 0131 | - | F | Stage 2 Correction on Mobility in RRC_IDLE | 15.4.0 | +| | RP-82 | RP-182660 | 0133 | 1 | F | Stage 2 CR on Measurement gap configuration scenarios | 15.4.0 | +| | RP-82 | RP-182659 | 0134 | 1 | F | CR on the carrier selection for random access | 15.4.0 | +| | RP-82 | RP-182659 | 0137 | 1 | F | Corrections on Multi-Radio dual connectivity | 15.4.0 | +| | RP-82 | RP-182670 | 0138 | 2 | F | Inter-system HO | 15.4.0 | +| | RP-82 | RP-182787 | 0139 | - | F | Baseline CR for TS 38.300 | 15.4.0 | +| | RP-82 | RP-182799 | 0140 | - | B | Addition of Annex X for SPID ranges | 15.4.0 | +| 2019/03 | RP-83 | RP-190542 | 0142 | 2 | F | RRc Reject Handling for MPS and MCS | 15.5.0 | +| | RP-83 | RP-190540 | 0143 | - | F | Misalignments with other Specifications | 15.5.0 | +| | RP-83 | RP-190543 | 0146 | 2 | F | RLF triggering when RLC reaches maximum number of retransmission | 15.5.0 | +| | RP-83 | RP-190543 | 0147 | 1 | F | Correction on RLC modes for duplication | 15.5.0 | +| | RP-83 | RP-190545 | 0148 | 1 | F | Correction of Data Forwarding over Xn | 15.5.0 | +| | RP-83 | RP-190544 | 0149 | - | F | Correction to RNAU without context relocation | 15.5.0 | +| | RP-83 | RP-190544 | 0150 | - | F | Correction of handling of PDCP SN during Data Forwarding | 15.5.0 | +| | RP-83 | RP-190545 | 0151 | 1 | F | Correction of stage 2 for slicing | 15.5.0 | +| | RP-83 | RP-190544 | 0152 | - | F | Energy Saving Support in R15 | 15.5.0 | +| 2019/06 | RP-84 | RP-191373 | 0154 | - | F | CQI and MCS for URLLC | 15.6.0 | +| | RP-84 | RP-191373 | 0155 | 1 | F | Miscellaneous Corrections | 15.6.0 | +| | RP-84 | RP-191373 | 0156 | 1 | F | CA Clarifications - RACH and Timing Advance | 15.6.0 | +| | RP-84 | RP-191373 | 0157 | - | F | Cross Carrier Scheduling | 15.6.0 | +| | RP-84 | RP-191379 | 0159 | 1 | F | CR on 38.300 for SRB cell mapping for CA duplication | 15.6.0 | +| | RP-84 | RP-191380 | 0160 | 1 | F | Support of ongoing re-mapping on source side during SDAP mobility | 15.6.0 | +| | RP-84 | RP-191379 | 0161 | - | F | Correction of data forwarding | 15.6.0 | +| | RP-84 | RP-191379 | 0162 | - | F | Slicing information during handover | 15.6.0 | +| | RP-84 | RP-191380 | 0163 | - | F | Corrections for support of data forwarding for reestablishment UE | 15.6.0 | +| | RP-84 | RP-191380 | 0164 | - | F | Correction of QoS flow re-mapping before handover | 15.6.0 | +| | RP-84 | RP-191380 | 0165 | - | F | Correction of NAS PDU | 15.6.0 | +| | RP-84 | RP-191380 | 0168 | - | F | Support for network sharing | 15.6.0 | +| 2019/09 | RP-85 | RP-192191 | 0171 | 1 | F | Correction on 5GC to EPC inter-RAT inter-system handover | 15.7.0 | +| 2019/12 | RP-86 | RP-192934 | 0173 | 2 | F | Clarification on measurement gap configuration in NR SA | 15.8.0 | +| | RP-86 | RP-192934 | 0174 | 1 | F | KgNB derivation upon mobility | 15.8.0 | +| | RP-86 | RP-192934 | 0178 | - | F | Correction on PUCCH transform precoding | 15.8.0 | +| | RP-86 | RP-192935 | 0181 | - | F | Correction on mini-slot scheduling | 15.8.0 | +| | RP-86 | RP-192937 | 0182 | - | F | Independent migration to IPv6 on NG-U | 15.8.0 | +| | RP-86 | RP-192938 | 0183 | - | F | Correction of QoS flow re-mapping before handover | 15.8.0 | +| | RP-86 | RP-192944 | 0184 | - | B | CR TS 38.300 Remote Interference Management | 16.0.0 | +| | RP-86 | RP-192942 | 0185 | - | B | Introduction of direct data forwarding for inter-system HO between EPS and 5GS | 16.0.0 | +| 2020/03 | RP-87 | RP-200349 | 0153 | 8 | B | CR to 38.300 on Integrated Access and Backhaul for NR | 16.1.0 | +| | RP-87 | RP-200347 | 0172 | 3 | B | Introduction of NR mobility enhancement | 16.1.0 | +| | RP-87 | RP-200360 | 0175 | 3 | B | Introduction of additional enhancements for eMTC | 16.1.0 | +| | RP-87 | RP-200361 | 0176 | 3 | B | Introduction of additional enhancements for NB-IoT | 16.1.0 | +| | RP-87 | RP-200350 | 0186 | 2 | B | Introduction of SRVCC from 5G to 3G | 16.1.0 | +| | RP-87 | RP-200351 | 0187 | 1 | B | Introduction of RACS and DL RRC segmentation | 16.1.0 | +| | RP-87 | RP-200335 | 0189 | 2 | A | Security and RRC Resume Request | 16.1.0 | +| | RP-87 | RP-200357 | 0190 | - | B | Introduction of NR IDC solution | 16.1.0 | +| | RP-87 | RP-200344 | 0193 | 2 | B | Introduction of UE Power Saving in NR | 16.1.0 | +| | RP-87 | RP-200341 | 0194 | 2 | B | Introduction of on-demand SI procedure in RRC_CONNECTED | 16.1.0 | +| | RP-87 | RP-200353 | 0195 | 2 | B | Non-Public Networks | 16.1.0 | +| | RP-87 | RP-200342 | 0197 | 1 | B | Introduction of 2-step RACH | 16.1.0 | +| | RP-87 | RP-200348 | 0198 | 2 | B | CR for 38.300 for CA/DC enhancements | 16.1.0 | +| | RP-87 | RP-200341 | 0199 | 2 | B | Introduction of NR operation with Shared Spectrum Access to Stage 2 | 16.1.0 | +| | RP-87 | RP-200343 | 0200 | 1 | B | Introduction of NR eURLLC | 16.1.0 | +| | RP-87 | RP-200340 | 0201 | 2 | B | Introduction of cross link interference management | 16.1.0 | +| | RP-87 | RP-200352 | 0203 | - | B | Introduction of NR Industrial IoT features | 16.1.0 | +| | RP-87 | RP-200346 | 0204 | - | B | Introduction of 5G V2X with NR Sidelink | 16.1.0 | +| | RP-87 | RP-200334 | 0207 | - | A | Propagation of Roaming and Access Restriction information in NG-RAN in non-homogenous NG-RAN node deployments | 16.1.0 | +| | RP-87 | RP-200345 | 0209 | - | B | RAN1 stage 2 agreements related to positioning | 16.1.0 | +| 2020/07 | RP-88 | RP-201165 | 0191 | 3 | B | Introduction of NeedForGap capability for NR measurement | 16.2.0 | +| | RP-88 | RP-201177 | 0211 | 2 | F | Corrections to Mobility Enhancements | 16.2.0 | +| | RP-88 | RP-201173 | 0214 | 1 | F | 4-step RA type figure description | 16.2.0 | +| | RP-88 | RP-201181 | 0215 | 1 | F | Stage-2 updates for IIOT | 16.2.0 | +| | RP-88 | RP-201171 | 0217 | 4 | F | CLI Corrections | 16.2.0 | +| | RP-88 | RP-201179 | 0220 | 1 | C | CR to 38.300 on Integrated Access and Backhaul for NR | 16.2.0 | +| | RP-88 | RP-201161 | 0222 | 1 | A | Clarification on pdcp-Duplication at RRC Reconfiguration | 16.2.0 | +| | RP-88 | RP-201164 | 0224 | 1 | A | Correction on bandwidth adaptation | 16.2.0 | +| | RP-88 | RP-201182 | 0225 | 2 | F | Miscellaneous corrections to NPN | 16.2.0 | +| | RP-88 | RP-201175 | 0227 | 1 | F | Missing SIB for positioning | 16.2.0 | +| | RP-88 | RP-201172 | 0229 | 1 | F | Miscellaneous corrections for NR operation with shared spectrum | 16.2.0 | +| | RP-88 | RP-201177 | 0230 | 2 | F | Corrections on NR mobility enhancements | 16.2.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|---------------------------------------------------------------------------------------|--------| +| | RP-88 | RP-201178 | 0236 | 2 | F | Clarification of DAPS configuration in MR-DC | 16.2.0 | +| | RP-88 | RP-201176 | 0237 | 1 | F | Introduction of on-demand SIB(s) procedure in RRC_CONNECTED | 16.2.0 | +| | RP-88 | RP-201190 | 0239 | - | C | Introduction of eCall over IMS for NR | 16.2.0 | +| | RP-88 | RP-201176 | 0245 | 1 | F | Correction for NR sidelink communication | 16.2.0 | +| | RP-88 | RP-201165 | 0246 | - | A | Global Cell Identities and Global NG-RAN Node Identities when NR access is shared | 16.2.0 | +| | RP-88 | RP-201176 | 0248 | 1 | B | Support for Alternative QoS profiles | 16.2.0 | +| | RP-88 | RP-201211 | 0249 | 1 | C | Introduction of Inter-gNB CSI-RS Based Mobility | 16.2.0 | +| | RP-88 | RP-201165 | 0251 | - | A | Correction of NAS NON Delivery | 16.2.0 | +| | RP-88 | RP-201177 | 0252 | 1 | B | Baseline CR for introducing Rel-16 NR mobility enhancement | 16.2.0 | +| | RP-88 | RP-201181 | 0253 | - | B | NRIOT Higher Layer Multi-Connectivity | 16.2.0 | +| | RP-88 | RP-201182 | 0254 | 1 | B | Introduction of Non Public Networks | 16.2.0 | +| | RP-88 | RP-201179 | 0255 | - | B | Mapping of Uplink Traffic to Backhaul RLC Channels | 16.2.0 | +| | RP-88 | RP-201354 | 0256 | - | B | Addition of SON features | 16.2.0 | +| 2020/09 | RP-89 | RP-201937 | 0232 | 1 | A | Clarification for KPAS and EU-alert | 16.3.0 | +| | RP-89 | RP-201931 | 0258 | 1 | F | Drafting Rules in Subclause 15 on SON | 16.3.0 | +| | RP-89 | RP-201928 | 0259 | - | F | Missing RACH Figure | 16.3.0 | +| | RP-89 | RP-201937 | 0260 | - | F | Clarification on NCGI | 16.3.0 | +| | RP-89 | RP-201963 | 0263 | 1 | F | Stage-2 CR for clarifications of Rel-16 PDCP Duplication | 16.3.0 | +| | RP-89 | RP-201926 | 0265 | - | F | Correction on CSI-RS Based Intra-frequency and Inter-frequency Measurement Definition | 16.3.0 | +| | RP-89 | RP-201930 | 0274 | - | F | Various corrections to NR Mobility enhancements description | 16.3.0 | +| | RP-89 | RP-201930 | 0278 | - | F | DAPS handover corrections | 16.3.0 | +| | RP-89 | RP-201922 | 0284 | 1 | F | Misc corrections for Rel-16 DCCA | 16.3.0 | +| | RP-89 | RP-201932 | 0285 | 1 | F | Mandatory support of full rate user plane integrity protection | 16.3.0 | +| | RP-89 | RP-201922 | 0286 | 1 | F | Correction on UL behaviours in the dormant BWP | 16.3.0 | +| | RP-89 | RP-201923 | 0293 | 1 | F | CR to 38.300 on Integrated Access and Backhaul for NR | 16.3.0 | +| | RP-89 | RP-201921 | 0294 | 1 | F | Correction of CAPC for NR-U | 16.3.0 | +| | RP-89 | RP-201929 | 0295 | - | F | Correction on prioritization between DCP and RAR to C-RNTI for CFRA BFR | 16.3.0 | +| | RP-89 | RP-201928 | 0296 | - | F | Correction of NPN CAG cells and non-CAG cells | 16.3.0 | +| 2020/12 | RP-90 | RP-202776 | 0299 | 1 | F | Stage-2 description of MPE reporting | 16.4.0 | +| | RP-90 | RP-202771 | 0300 | 3 | F | Description of Multi-TRP operation | 16.4.0 | +| | RP-90 | RP-202774 | 0305 | 1 | F | Miscellaneous corrections to Mobility Enhancements | 16.4.0 | +| | RP-90 | RP-202774 | 0307 | 1 | F | Clarification on no support of CA, DC or multi-TRP with DAPS | 16.4.0 | +| | RP-90 | RP-202771 | 0310 | 1 | F | BFR on SCell | 16.4.0 | +| | RP-90 | RP-202776 | 0317 | 3 | F | Dynamic UMTS Radio Capability impact on SRVCC and RACS | 16.4.0 | +| | RP-90 | RP-202772 | 0318 | 1 | F | Corrections on non DRB operation for IAB-MT | 16.4.0 | +| | RP-90 | RP-202774 | 0322 | 1 | F | Correction to RLF in case of DAPS HO | 16.4.0 | +| | RP-90 | RP-202769 | 0323 | - | F | Stage-2 corrections for NR sidelink communication | 16.4.0 | +| | RP-90 | RP-202771 | 0324 | - | F | Clarifying the use of PNI-NPN term in RAN specifications | 16.4.0 | +| | RP-90 | RP-202777 | 0325 | 1 | F | Clarification on the indication of eCall over IMS | 16.4.0 | +| | RP-90 | RP-202777 | 0326 | 1 | F | Secondary DRX group description is missing | 16.4.0 | +| | RP-90 | RP-202774 | 0327 | - | F | CHO in stage-2 | 16.4.0 | +| | RP-90 | RP-202769 | 0328 | - | F | Corrections on AQP for notification control | 16.4.0 | +| | RP-90 | RP-202774 | 0330 | - | F | Correction for NR CHO and Full Configuration | 16.4.0 | +| | RP-90 | RP-202767 | 0331 | - | F | Update the deployment scenarios in Annex B.3 | 16.4.0 | +| 2021/03 | RP-91 | RP-210701 | 0302 | 2 | A | UE Capabilities Description | 16.5.0 | +| | RP-91 | RP-210692 | 0333 | 1 | F | Clarification on no support of SUL with DAPS | 16.5.0 | +| | RP-91 | RP-210691 | 0337 | 1 | F | Miscellaneous Stage-2 corrections of IAB in 38.300 | 16.5.0 | +| | RP-91 | RP-210695 | 0338 | 2 | F | Release with Redirect for connection resume triggered by NAS | 16.5.0 | +| | RP-91 | RP-210702 | 0339 | 1 | A | Clarification of data forwarding upon intra-system HO using full configuration | 16.5.0 | +| | RP-91 | RP-210692 | 0340 | 2 | F | Addition of releasing the source part of DAPS DRBS upon DAPS release | 16.5.0 | +| | RP-91 | RP-210689 | 0343 | - | F | Correction on uplink transmission allowed without TA | 16.5.0 | +| | RP-91 | RP-210689 | 0346 | 1 | F | Clarification on DAPS HO configuration | 16.5.0 | +| | RP-91 | RP-210694 | 0347 | - | F | PDCP SN issue for EPC to 5GC handover | 16.5.0 | +| 2021-06 | RP-92 | RP-211475 | 0352 | 2 | F | Addition of size limitation for SRVCC | 16.6.0 | +| | RP-92 | RP-211473 | 0353 | 2 | F | Transmissions to the source that continue upon DAPS UL switching | 16.6.0 | +| | RP-92 | RP-211473 | 0354 | 1 | F | Removing ambiguous legacy and normal terms from handover descriptions | 16.6.0 | +| | RP-92 | RP-211472 | 0359 | 1 | F | Updated description of multi-TRP | 16.6.0 | +| | RP-92 | RP-211484 | 0364 | 3 | A | SRB PDCP handling upon handover | 16.6.0 | +| | RP-92 | RP-211472 | 0366 | 3 | F | Missing IAB SA mode for QoS description | 16.6.0 | +| | RP-92 | RP-211473 | 0368 | 1 | F | Clarification on RLF detection of source PCell | 16.6.0 | +| | RP-92 | RP-211473 | 0370 | 1 | F | Miscellaneous corrections to DAPS handover | 16.6.0 | +| | RP-92 | RP-211480 | 0373 | 1 | F | Miscellaneous Corrections | 16.6.0 | +| | RP-92 | RP-211471 | 0379 | - | F | Correction of MRO in stage 2 | 16.6.0 | +| | RP-92 | RP-211484 | 0380 | - | F | Supporting use of UE Radio Capability for Paging in RRC_INACTIVE | 16.6.0 | +| 2021-09 | RP-93 | RP-212443 | 0381 | 1 | F | Correction to Rel-16 HARQ description | 16.7.0 | +| | RP-93 | RP-212442 | 0387 | 1 | F | Miscellaneous corrections to eURLLC for 38.300 | 16.7.0 | + +| | | | | | | | | +|---------|-------|-----------|------|----|---|-------------------------------------------------------------------------------------------------------|--------| +| | RP-93 | RP-212440 | 0388 | 1 | F | NAS PDU handling | 16.7.0 | +| 2021-12 | RP-94 | RP-213343 | 0391 | 1 | F | Miscellaneous Corrections | 16.8.0 | +| | RP-94 | RP-213343 | 0398 | - | F | Handling of mobility and dual connectivity in mixed PNI-NPN/PLMN cell scenarios | 16.8.0 | +| 2022-03 | RP-95 | RP-220484 | 0342 | 10 | B | Introduction of NR MBS | 17.0.0 | +| | RP-95 | RP-220487 | 0357 | 7 | B | Introduction of SDT | 17.0.0 | +| | RP-95 | RP-220486 | 0389 | 4 | B | Introduction of IAB enhancements | 17.0.0 | +| | RP-95 | RP-220477 | 0400 | 1 | B | Introduction of NR dynamic spectrum sharing | 17.0.0 | +| | RP-95 | RP-220506 | 0401 | 1 | D | Inclusive Language Review for TS 38.300 | 17.0.0 | +| | RP-95 | RP-220837 | 0402 | 1 | B | Introduction of MINT [MINT] | 17.0.0 | +| | RP-95 | RP-220491 | 0403 | 2 | B | Introduction of Sidelink Relay | 17.0.0 | +| | RP-95 | RP-220476 | 0405 | 1 | B | Introduction of eSL in TS 38.300 | 17.0.0 | +| | RP-95 | RP-220837 | 0407 | 1 | B | Introduction of RACH triggers for T_ADV in NR E-CID [NRTADV] | 17.0.0 | +| | RP-95 | RP-220475 | 0408 | 1 | B | Introduction of NR operation up to 71GHz | 17.0.0 | +| | RP-95 | RP-220499 | 0411 | 1 | B | Stage 2 CR for UL Tx switching enhancement | 17.0.0 | +| | RP-95 | RP-220478 | 0412 | 1 | B | Introduction of NR coverage enhancements | 17.0.0 | +| | RP-95 | RP-220490 | 0413 | 1 | B | RAN enhancements in the support of slicing | 17.0.0 | +| | RP-95 | RP-220493 | 0414 | 2 | B | Introducing NPN enhancements: Credential Holders, Onboarding, IMS emergency, and PWS support in SNPNS | 17.0.0 | +| | RP-95 | RP-220489 | 0415 | - | B | Introduction of the support for UDC in NR | 17.0.0 | +| | RP-95 | RP-220481 | 0416 | 1 | B | Introduction of Rel-17 IIoT/URLLC to TS 38.300 | 17.0.0 | +| | RP-95 | RP-220960 | 0417 | 2 | B | Introduction of UE power saving enhancements In 38.300 | 17.0.0 | +| | RP-95 | RP-220496 | 0420 | 1 | B | Introduction of DL 1024 QAM in NR | 17.0.0 | +| | RP-95 | RP-220480 | 0421 | 2 | B | Introduction of RedCap in TS 38.300 | 17.0.0 | +| | RP-95 | RP-220488 | 0422 | 1 | B | Running CR to 38300 for Multi-USIM devices support | 17.0.0 | +| | RP-95 | RP-220482 | 0423 | 2 | B | Support of Non-Terrestrial Networks | 17.0.0 | +| | RP-95 | RP-220494 | 0424 | - | B | 38.300 CR for Introduction of QoE measurements in NR | 17.0.0 | +| | RP-95 | RP-220510 | 0426 | - | B | Introduction of Local NG-RAN Node IDs for RRC_INACTIVE [RRCInactive] | 17.0.0 | +| | RP-95 | RP-220510 | 0427 | 1 | C | UE Security Capabilities signaling in NG-RAN [UE_Sec_Caps] | 17.0.0 | +| | RP-95 | RP-220839 | 0431 | - | B | Addition of SON features enhancement | 17.0.0 | +| | RP-95 | RP-220474 | 0439 | - | B | Introduction of feMIMO | 17.0.0 | +| 2022-06 | RP-96 | RP-221728 | 0362 | 2 | B | Introduction of further MRDC enhancements | 17.1.0 | +| | RP-96 | RP-221732 | 0440 | 1 | F | Correction on stage 2 for sidelink relay | 17.1.0 | +| | RP-96 | RP-221735 | 0441 | 1 | F | 38.300 CR Correction for Introduction of QoE measurements in NR | 17.1.0 | +| | RP-96 | RP-221715 | 0447 | 1 | F | Stage-2 corrections for 71 GHz | 17.1.0 | +| | RP-96 | RP-221727 | 0458 | 2 | F | Corrections to UE power saving enhancements In 38.300 | 17.1.0 | +| | RP-96 | RP-221719 | 0462 | - | C | Updates for RAN Slicing from RAN2#118 | 17.1.0 | +| | RP-96 | RP-221716 | 0464 | 1 | F | Corrections on RedCap in TS 38.300 | 17.1.0 | +| | RP-96 | RP-221729 | 0465 | 1 | F | Corrections on SDT | 17.1.0 | +| | RP-96 | RP-221729 | 0466 | 2 | F | Introduction of RACH partitioning | 17.1.0 | +| | RP-96 | RP-221762 | 0469 | 2 | F | Miscellaneous Corrections to eSL | 17.1.0 | +| | RP-96 | RP-221724 | 0472 | - | F | Correction for NR coverage enhancements | 17.1.0 | +| | RP-96 | RP-221736 | 0474 | 1 | B | Introduction of gNB ID length reporting in the NR CGI report [gNB_ID_Length] | 17.1.0 | +| | RP-96 | RP-221718 | 0476 | - | F | Various corrections to IAB enhancements | 17.1.0 | +| | RP-96 | RP-221726 | 0477 | - | F | Corrections for IIoT on simultaneous PUCCH and PUSCH transmission | 17.1.0 | +| | RP-96 | RP-221717 | 0478 | - | F | Corrections to stage 2 for NR NTN | 17.1.0 | +| | RP-96 | RP-221714 | 0480 | - | A | Inter-system direct data forwarding between source SgNB and target gNB | 17.1.0 | +| | RP-96 | RP-221754 | 0483 | - | F | Correction on NR MBS | 17.1.0 | +| | RP-96 | RP-221754 | 0484 | 1 | F | Correction of MBS data forwarding | 17.1.0 | +| | RP-96 | RP-221729 | 0485 | - | F | Correction on RA-SDT overall procedures | 17.1.0 | +| | RP-96 | RP-221717 | 0486 | - | F | Corrections for NR NTN | 17.1.0 | +| | RP-96 | RP-221733 | 0487 | - | F | Correction on R17 SON MDT for 38.300 | 17.1.0 | +| | RP-96 | RP-221727 | 0488 | - | F | Correction of the "last used cell" in UE Context Release Complete | 17.1.0 | +| | RP-96 | RP-221754 | 0490 | - | F | Correction on NR MBS mobility for 38300 | 17.1.0 | +| | RP-96 | RP-221733 | 0491 | - | F | TS 38.300 corrections for CCO | 17.1.0 | +| | RP-96 | RP-221754 | 0492 | - | F | Corrections on MBS | 17.1.0 | +| 2022-09 | RP-97 | RP-222524 | 0509 | 2 | F | Rel-17 NTN related Rapporteur's corrections to TS 38.300 | 17.2.0 | +| | RP-97 | RP-222516 | 0515 | 1 | A | NR Correction related to RNA | 17.2.0 | +| | RP-97 | RP-222525 | 0519 | 1 | F | Corrections on SDT | 17.2.0 | +| | RP-97 | RP-222523 | 0524 | - | F | Clarification on PUCCH cell switching for TDD cells | 17.2.0 | +| | RP-97 | RP-222525 | 0535 | 2 | F | Corrections on RedCap in TS 38.300 | 17.2.0 | +| | RP-97 | RP-222524 | 0543 | 2 | F | Stage-2 corrections to Rel-17 QoE | 17.2.0 | +| | RP-97 | RP-222522 | 0546 | 1 | F | Miscellaneous Corrections | 17.2.0 | +| | RP-97 | RP-222524 | 0547 | 1 | F | 38.300 corrections for sidelink enhancements | 17.2.0 | +| | RP-97 | RP-222522 | 0548 | - | F | Stage-2 corrections on MUSIM | 17.2.0 | +| | RP-97 | RP-222525 | 0549 | 1 | F | Corrections on TS 38.300 for RAN Slicing | 17.2.0 | +| | RP-97 | RP-222524 | 0550 | 2 | F | Correction on stage 2 for sidelink relay | 17.2.0 | +| | RP-97 | RP-222525 | 0552 | - | F | Corrections to UE power saving enhancements in TS 38.300 | 17.2.0 | +| | RP-97 | RP-222523 | 0553 | - | F | Correction to Rel-17 SON features | 17.2.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------------------|--------| +| | RP-97 | RP-222523 | 0555 | - | F | Correction of MBS stage 2 | 17.2.0 | +| | RP-97 | RP-222519 | 0557 | - | A | CAG access control without mobility restrictions | 17.2.0 | +| | RP-97 | RP-222523 | 0558 | - | F | Completion of the missing description of SCG MRO handling | 17.2.0 | +| | RP-97 | RP-222525 | 0559 | - | F | Correction on Slice Group Configuration | 17.2.0 | +| | RP-97 | RP-222526 | 0561 | - | F | Support for flexible gNB ID length [gNB_ID_Length] | 17.2.0 | +| 2022-12 | RP-98 | RP-223406 | 0564 | 2 | F | Corrections on MBS | 17.3.0 | +| | RP-98 | RP-223411 | 0572 | 4 | F | Corrections to TS 38.300 for Rel-17 NR NTN | 17.3.0 | +| | RP-98 | RP-223412 | 0583 | 2 | F | Miscellaneous corrections on TS 38.300 for NR sidelink | 17.3.0 | +| | RP-98 | RP-223411 | 0587 | 2 | F | Miscellaneous RedCap corrections in stage-2 | 17.3.0 | +| | RP-98 | RP-223413 | 0595 | 1 | F | Clarifications for SDT Stage-2 | 17.3.0 | +| | RP-98 | RP-223410 | 0596 | 1 | F | Clarification on BFD-RS set based BFR | 17.3.0 | +| | RP-98 | RP-223412 | 0598 | 1 | F | Correction on SL relay | 17.3.0 | +| | RP-98 | RP-223413 | 0599 | 1 | D | Clarification on PDCCH skipping | 17.3.0 | +| | RP-98 | RP-223404 | 0601 | 1 | A | Clarification for ePWS | 17.3.0 | +| | RP-98 | RP-223410 | 0602 | - | F | CR to TS 38.300 on IAB-topology definition | 17.3.0 | +| | RP-98 | RP-223412 | 0603 | - | F | Correction on NSAG | 17.3.0 | +| | RP-98 | RP-223412 | 0604 | - | F | NSAG for cell reselection and random access | 17.3.0 | +| | RP-98 | RP-223406 | 0605 | - | F | Minimization of data loss and duplication avoidance during mobility from MBS non supporting gNB to supporting gNB | 17.3.0 | +| | RP-98 | RP-223410 | 0607 | - | F | Correction of UE History Information for CHO | 17.3.0 | +| | RP-98 | RP-223410 | 0608 | - | F | SHR correction | 17.3.0 | +| | RP-98 | RP-223411 | 0609 | 1 | F | CR to TS 38.300 on RAN visible QoE | 17.3.0 | +| | RP-98 | RP-223412 | 0610 | - | F | Clarification on slice group information provided by NAS | 17.3.0 | +| 2023-03 | RP-99 | RP-230690 | 0611 | 1 | F | Correction on Stage-2 descriptions for NR NTN | 17.4.0 | +| | RP-99 | RP-230690 | 0613 | 2 | F | MBS corrections for multicast configuration and service continuity | 17.4.0 | +| | RP-99 | RP-230691 | 0614 | - | F | Corrections to description of RAN Visible QoE Measurements | 17.4.0 | +| | RP-99 | RP-230691 | 0619 | 2 | F | Clarification of UE Behaviour upon Pause of QoE Reporting | 17.4.0 | +| | RP-99 | RP-230689 | 0621 | 1 | F | Removal of editor's note on sequence length 1151 for PRACH usage | 17.4.0 | +| | RP-99 | RP-230692 | 0627 | - | F | Correction to 38.300 on SRAP operation | 17.4.0 | +| | RP-99 | RP-230688 | 0628 | 2 | F | Correction on RRCReject handling for SDT | 17.4.0 | +| | RP-99 | RP-230685 | 0639 | 1 | A | Clarification on the PDCCH Ordered RACH for SCell in 38.300 | 17.4.0 | +| | RP-99 | RP-230692 | 0642 | 2 | F | Miscellaneous corrections on TS 38.300 for NR sidelink | 17.4.0 | +| | RP-99 | RP-230686 | 0644 | - | A | Corrections on PSBCH Symbols number for NR sidelink | 17.4.0 | +| 2023-06 | RP-100 | RP-231418 | 0647 | 5 | F | NTN stage-2 correction | 17.5.0 | +| | RP-100 | RP-231416 | 0656 | 2 | F | Miscellaneous corrections for Stage 2 NR sidelink relay | 17.5.0 | +| | RP-100 | RP-231415 | 0666 | 1 | F | Clarification on the application of slice-based RACH configuration | 17.5.0 | +| | RP-100 | RP-231414 | 0672 | - | F | Miscellaneous Corrections | 17.5.0 | +| | RP-100 | RP-231416 | 0673 | 2 | F | Miscellaneous corrections on TS 38.300 for NR sidelink | 17.5.0 | +| | RP-100 | RP-231415 | 0678 | 1 | F | Corrections on eDRX and RRM measurement relaxation for RedCap | 17.5.0 | +| | RP-100 | RP-231415 | 0684 | 2 | F | Corrections to Security Issues for MO-SDT | 17.5.0 | +| | RP-100 | RP-231413 | 0686 | - | F | Correction of QoE stage-2 description | 17.5.0 | +| | RP-100 | RP-231415 | 0687 | 1 | F | Introduction of Hashed UE Identity Index Value for RRC_INACTIVE with eDRX | 17.5.0 | +| | RP-100 | RP-231415 | 0688 | - | F | Correction to Security Issues for MO-SDT | 17.5.0 | +| 2023-09 | RP-101 | RP-232570 | 0691 | 3 | F | Correction on SDT | 17.6.0 | +| | RP-101 | RP-232667 | 0697 | 1 | F | Correction on gap requirement for inter-RAT LTE measurement | 17.6.0 | +| | RP-101 | RP-232566 | 0701 | 1 | A | Miscellaneous stage 2 corrections for sidelink | 17.6.0 | +| | RP-101 | RP-232566 | 0705 | - | A | Stage2 correction on UE Identities | 17.6.0 | +| | RP-101 | RP-232570 | 0707 | - | F | Correction on SDT Triggering | 17.6.0 | +| | RP-101 | RP-232667 | 0708 | 1 | F | RedCap specific SDT configuration | 17.6.0 | +| | RP-101 | RP-232667 | 0709 | - | F | Rapporteur Miscellaneous Stage 2 Corrections | 17.6.0 | +| | RP-101 | RP-232570 | 0710 | - | F | Correction on R17 MO SDT termination | 17.6.0 | +| 2023-12 | RP-102 | RP-233890 | 0726 | 1 | F | Miscellaneous Corrections | 17.7.0 | +| | RP-102 | RP-233890 | 0735 | 1 | F | Clarification for Mission Critical UEs | 17.7.0 | +| | RP-102 | RP-233885 | 0738 | 1 | A | Correction on NR SL Stage 2 | 17.7.0 | +| | RP-102 | RP-233888 | 0744 | 1 | F | Correction on the SidelinkUEInformationNR message | 17.7.0 | +| | RP-102 | RP-233889 | 0747 | - | F | Correction of Paging with PEI | 17.7.0 | +| | RP-102 | RP-233887 | 0749 | - | F | Correction on SHR for intra-NR mobility | 17.7.0 | +| 2023-12 | RP-102 | RP-233905 | 0680 | 5 | B | Introduction of In-Device Co-existence (IDC) enhancements for NR | 18.0.0 | +| | RP-102 | RP-233898 | 0685 | 5 | B | Introducing support for Network-Controlled Repeaters to 38.300 | 18.0.0 | +| | RP-102 | RP-233900 | 0689 | 7 | B | Introduction of Network Energy Savings | 18.0.0 | +| | RP-102 | RP-233902 | 0711 | 2 | B | Introduction of MT-SDT in Stage-2 | 18.0.0 | +| | RP-102 | RP-233956 | 0721 | 1 | B | Introduction of support for BWP operation without restriction | 18.0.0 | +| | RP-102 | RP-233901 | 0722 | 2 | B | Introduction of sidelink positioning in 38300 | 18.0.0 | +| | RP-102 | RP-233912 | 0723 | 1 | B | Introduction of R18 eNPN for TS 38.300 | 18.0.0 | +| | RP-102 | RP-233908 | 0724 | 1 | B | Introduction of XR Enhancements | 18.0.0 | +| | RP-102 | RP-233933 | 0727 | 2 | B | Introduction of Mobile IAB | 18.0.0 | +| | RP-102 | RP-233897 | 0728 | 1 | B | Introduction of NR Sidelink Evolution | 18.0.0 | +| | RP-102 | RP-233899 | 0729 | 1 | B | Introduction of eRedCap in TS 38.300 | 18.0.0 | +| | RP-102 | RP-233911 | 0730 | 2 | B | Introduction of Timing Resiliency and URLLC enhancements | 18.0.0 | +| | RP-102 | RP-233913 | 0731 | - | B | Introduction on UE preference for multi-Rx operation in UAI | 18.0.0 | + +| | | | | | | | | +|--|--------|-----------|------|---|---|----------------------------------------------------------------------------------|--------| +| | RP-102 | RP-233907 | 0732 | 2 | B | Introduction of eMBS in TS 38.300 | 18.0.0 | +| | RP-102 | RP-233895 | 0733 | 1 | B | Introduction of Further NR coverage enhancements to 38.300 | 18.0.0 | +| | RP-102 | RP-233906 | 0734 | 1 | B | Introduction of NTN enhancements | 18.0.0 | +| | RP-102 | RP-233932 | 0736 | 1 | B | Introduction of NR Support for Uncrewed Aerial Vehicles | 18.0.0 | +| | RP-102 | RP-233916 | 0740 | 1 | B | Introduction of NR ATG in TS 38.300 | 18.0.0 | +| | RP-102 | RP-233903 | 0741 | 1 | B | Introduction of NR MUSIM enhancements in TS 38.300 | 18.0.0 | +| | RP-102 | RP-233896 | 0742 | 1 | B | Introduction of MIMO evolution for Downlink and Uplink | 18.0.0 | +| | RP-102 | RP-233882 | 0743 | 1 | B | Introduction of maximum time duration to initiate CG-SDT in Stage-2 [CG-SDT-Enh] | 18.0.0 | +| | RP-102 | RP-233882 | 0748 | - | B | Support of oversize UL SDT Data Arrival [Large SDT Uplink Data] | 18.0.0 | +| | RP-102 | RP-233902 | 0751 | - | B | Introduction on MT-SDT | 18.0.0 | +| | RP-102 | RP-233882 | 0753 | - | B | Introduction of RedCap UE MBS Broadcast reception [RedcapMBS] | 18.0.0 | +| | RP-102 | RP-233935 | 0754 | - | B | Enhancement of RAN Slicing for NR | 18.0.0 | +| | RP-102 | RP-233934 | 0756 | - | B | AI/ML for NG-RAN | 18.0.0 | +| | RP-102 | RP-233909 | 0757 | - | B | Addition of SON features enhancement | 18.0.0 | +| | RP-102 | RP-233936 | 0766 | 1 | B | Introduction of NR support for dedicated spectrum less than 5MHz for FR1 | 18.0.0 | +| | RP-102 | RP-233910 | 0768 | 1 | B | Introduction of R18 QoE enhancement in TS 38.300 | 18.0.0 | +| | RP-102 | RP-233894 | 0769 | - | B | Introduction of Multi-carrier enhancements | 18.0.0 | +| | RP-102 | RP-233930 | 0770 | - | B | Introduction of NR further mobility enhancements in TS 38.300 | 18.0.0 | +| | RP-102 | RP-233904 | 0771 | 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/38306/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38306/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bab13b5e7f834d4f18d6513c81d07acfc0fac8a9 --- /dev/null +++ b/marked/Rel-18/38_series/38306/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed7ba78f49d7ddf0cfeecda14e706cc780c6f23b4fcb4ea60e0793308176e241 +size 9118 diff --git a/marked/Rel-18/38_series/38306/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38306/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d049b3de17a27b693cb42c94a8ce8ed12c18927 --- /dev/null +++ b/marked/Rel-18/38_series/38306/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:72c7408ee713eaf880ff6db1593a7a276e37067cbcf9fc4a1b1f2f05511e1653 +size 5858 diff --git a/marked/Rel-18/38_series/38306/raw.md b/marked/Rel-18/38_series/38306/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..62cfc7ceec895a25f2fb60ace9c28ca4a0561009 --- /dev/null +++ b/marked/Rel-18/38_series/38306/raw.md @@ -0,0 +1,4145 @@ + + +# 3GPP TS 38.306 V18.0.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; User Equipment (UE) radio access capabilities (Release 18)** + +![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5G" text are three green curved lines representing signal waves. + +5G logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, featuring the text "3GPP" in a stylized, bold, black font. Below the "3GPP" text is the phrase "A GLOBAL INITIATIVE" in a smaller, all-caps, sans-serif font. There is a small red signal icon between the "3G" and "PP". + +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..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions, symbols and abbreviations..... | 8 | +| 3.1 Definitions..... | 8 | +| 3.2 Symbols..... | 9 | +| 3.3 Abbreviations..... | 9 | +| 4 UE radio access capability parameters..... | 10 | +| 4.1 Supported max data rate..... | 10 | +| 4.1.1 General..... | 10 | +| 4.1.2 Supported max data rate for DL/UL..... | 10 | +| 4.1.3 Void..... | 12 | +| 4.1.4 Total layer 2 buffer size for DL/UL..... | 12 | +| 4.1.5 Supported max data rate for SL..... | 12 | +| 4.1.6 Total layer 2 buffer size for NR SL..... | 13 | +| 4.2 UE Capability Parameters..... | 13 | +| 4.2.1 Introduction..... | 13 | +| 4.2.2 General parameters..... | 16 | +| 4.2.3 SDAP Parameters..... | 21 | +| 4.2.4 PDCP Parameters..... | 22 | +| 4.2.5 RLC parameters..... | 25 | +| 4.2.6 MAC parameters..... | 26 | +| 4.2.7 Physical layer parameters..... | 31 | +| 4.2.7.1 BandCombinationList parameters..... | 31 | +| 4.2.7.2 BandNR parameters ..... | 41 | +| 4.2.7.2a SharedSpectrumChAccessParamsPerBand ..... | 105 | +| 4.2.7.2b FR2-2-AccessParamsPerBand ..... | 111 | +| 4.2.7.3 CA-ParametersEUTRA ..... | 115 | +| 4.2.7.4 CA-ParametersNR ..... | 116 | +| 4.2.7.5 FeatureSetDownlink parameters..... | 154 | +| 4.2.7.6 FeatureSetDownlinkPerCC parameters..... | 164 | +| 4.2.7.7 FeatureSetUplink parameters..... | 170 | +| 4.2.7.8 FeatureSetUplinkPerCC parameters..... | 183 | +| 4.2.7.9 MRDC-Parameters ..... | 188 | +| 4.2.7.10 Phy-Parameters ..... | 192 | +| 4.2.7.11 Other PHY parameters..... | 209 | +| 4.2.7.12 NRDC-Parameters ..... | 212 | +| 4.2.7.13 CarrierAggregationVariant ..... | 214 | +| 4.2.7.14 Phy-ParametersSharedSpectrumChAccess ..... | 215 | +| 4.2.8 Void..... | 217 | +| 4.2.9 MeasAndMobParameters ..... | 218 | +| 4.2.9a MeasAndMobParametersMRDC ..... | 228 | +| 4.2.10 Inter-RAT parameters..... | 231 | + +## Copyright Notification + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +| | | | +|------------|----------------------------------------------------------------------|-----| +| 4.2.10.1 | Void..... | 231 | +| 4.2.10.2 | Void..... | 231 | +| 4.2.11 | Void..... | 231 | +| 4.2.12 | Void..... | 231 | +| 4.2.13 | IMS Parameters..... | 231 | +| 4.2.14 | RRC buffer size..... | 232 | +| 4.2.15 | IAB Parameters..... | 232 | +| 4.2.15.1 | Mandatory IAB-MT features..... | 232 | +| 4.2.15.1a | Mandatory mobile IAB-MT features..... | 238 | +| 4.2.15.2 | General Parameters..... | 238 | +| 4.2.15.3 | SDAP Parameters..... | 238 | +| 4.2.15.4 | PDCP Parameters..... | 238 | +| 4.2.15.5 | BAP Parameters..... | 239 | +| 4.2.15.6 | MAC Parameters..... | 239 | +| 4.2.15.7 | Physical layer parameters..... | 239 | +| 4.2.15.7.1 | BandNR parameters..... | 239 | +| 4.2.15.7.2 | Phy-Parameters..... | 240 | +| 4.2.15.8 | MeasAndMobParameters Parameters..... | 242 | +| 4.2.15.9 | MR-DC Parameters..... | 242 | +| 4.2.15.10 | NRDC Parameters..... | 242 | +| 4.2.16 | Sidelink Parameters..... | 243 | +| 4.2.16.1 | Sidelink Parameters in NR..... | 243 | +| 4.2.16.1.1 | Sidelink General Parameters..... | 243 | +| 4.2.16.1.2 | Sidelink PDCP Parameters..... | 244 | +| 4.2.16.1.3 | Sidelink RLC Parameters..... | 244 | +| 4.2.16.1.4 | Sidelink MAC Parameters..... | 244 | +| 4.2.16.1.5 | Other PHY parameters..... | 245 | +| 4.2.16.1.6 | BandSidelink Parameters..... | 246 | +| 4.2.16.1.7 | BandCombinationListSidelinkEUTRA-NR Parameters..... | 256 | +| 4.2.16.2 | Sidelink Parameters in E-UTRA..... | 259 | +| 4.2.16.2.0 | General..... | 259 | +| 4.2.16.2.1 | BandSideLinkEUTRA parameters..... | 260 | +| 4.2.17 | SON parameters..... | 260 | +| 4.2.18 | UE-based performance measurement parameters..... | 261 | +| 4.2.19 | High speed parameters..... | 262 | +| 4.2.20 | Application layer measurement parameters..... | 263 | +| 4.2.21 | RedCap Parameters..... | 263 | +| 4.2.21.1 | Definition of RedCap UE..... | 263 | +| 4.2.21.2 | General parameters..... | 264 | +| 4.2.21.3 | PDCP parameters..... | 264 | +| 4.2.21.4 | RLC parameters..... | 265 | +| 4.2.21.5 | MeasAndMobParameters..... | 265 | +| 4.2.21.6 | Physical layer parameters..... | 265 | +| 4.2.21.6.1 | BandNR parameters..... | 265 | +| 4.2.22 | eRedCap Parameters..... | 265 | +| 4.2.22.1 | Definition of eRedCap UE..... | 265 | +| 4.2.22.2 | General parameters..... | 266 | +| 4.2.23 | NCR Parameters..... | 267 | +| 4.2.23.1 | Mandatory NCR-MT features..... | 267 | +| 4.2.23.2 | General Parameters..... | 272 | +| 4.2.23.3 | SDAP Parameters..... | 273 | +| 4.2.23.4 | PDCP Parameters..... | 273 | +| 4.2.23.5 | RLC Parameters..... | 273 | +| 4.2.23.6 | Physical layer Parameters..... | 274 | +| 4.2.23.6.1 | Phy-Parameters..... | 274 | +| 4.2.24 | Aerial UE Parameters..... | 275 | +| 5 | Optional features without UE radio access capability parameters..... | 276 | +| 5.1 | PWS features..... | 276 | +| 5.2 | UE receiver features..... | 276 | +| 5.3 | RRC connection..... | 276 | +| 5.4 | Other features..... | 277 | + +| | | | +|-------------------------------|---------------------------------------------------------------------------------------------------------|------------| +| 5.5 | Sidelink Features..... | 277 | +| 5.6 | RRM measurement features..... | 278 | +| 5.7 | MDT and SON features..... | 279 | +| 5.8 | Extended DRX features..... | 279 | +| 5.9 | Sidelink Relay Features..... | 280 | +| 5.10 | MBS features..... | 280 | +| 6 | Conditionally mandatory features without UE radio access capability parameters..... | 282 | +| 7 | Void..... | 282 | +| 8 | UE Capability Constraints..... | 282 | +| Annex A (normative): | Differentiation of capabilities..... | 284 | +| A.1: | TDD/FDD differentiation of capabilities in TDD-FDD CA..... | 284 | +| A.2: | FR1/FR2 differentiation of capabilities in FR1-FR2 CA..... | 285 | +| A.3: | TDD/FDD differentiation of capabilities for sidelink..... | 286 | +| A.4: | Sidelink capabilities applicable to Uu and PC5..... | 287 | +| A.5: | General differentiation of capabilities in Cross-Carrier operation..... | 290 | +| Annex B (informative): | UE capability indication for UE capabilities with both FDD/TDD and FR1/FR2 differentiations..... | 292 | +| Annex C (informative): | Change history..... | 294 | + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# 1 Scope + +The present document defines the NR UE Radio Access Capability Parameters. + +# 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-1: "NR; User Equipment (UE) radio transmission and reception Part 1: Range 1 Standalone". +- [3] 3GPP TS 38.101-2: "NR; User Equipment (UE) radio transmission and reception Part 2: Range 2 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.133: "NR; Requirements for support of radio resource management". +- [6] 3GPP TS 38.211: "NR; Physical channels and modulation". +- [7] 3GPP TS 37.340: "Evolved Universal Terrestrial Radio Access (E-UTRA) and NR Multi-connectivity". +- [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.212: "NR; Multiplexing and channel coding". +- [11] 3GPP TS 38.213: "NR; Physical layer procedures for control". +- [12] 3GPP TS 38.214: "NR; Physical layer procedures for data". +- [13] 3GPP TS 38.215: "NR; Physical layer measurements". +- [14] 3GPP TS 36.101: "Evolved Universal Terrestrial Radio Access (E-UTRA) radio transmission and reception". +- [15] 3GPP TS 36.306: "Evolved Universal Terrestrial Radio Access (E-UTRA) User Equipment (UE) radio access capabilities". +- [16] 3GPP TS 38.323: "NR; Packet Data Convergence Protocol (PDCP) specification". +- [17] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource Control (RRC); Protocol Specification". +- [18] 3GPP TS 38.101-4: "NR; User Equipment (UE) radio transmission and reception Part 4: Performance requirements". + +- [19] 3GPP TS 36.213: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures". +- [20] 3GPP TS 25.306: "UE radio access capabilities". +- [21] 3GPP TS 38.304: "User Equipment (UE) procedures in Idle mode and RRC Inactive state". +- [22] 3GPP TS 37.355: " LTE Positioning Protocol (LPP)". +- [23] 3GPP TS 38.340: "NR; Backhaul Adaptation Protocol (BAP) specification". +- [24] 3GPP TR 38.822: "NR; User Equipment (UE) feature list". +- [25] 3GPP TS 37.324: "E-UTRA and NR; Service Data Adaptation Protocol (SDAP) specification" +- [26] 3GPP TS 38.314: "NR; Layer 2 Measurements". +- [27] 3GPP TS 36.133: "Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management". +- [28] 3GPP TS 38.300: "NR; NR and NG-RAN Overall Description; Stage-2". +- [29] 3GPP TS 26.247: "Transparent end-to-end Packet-switched Streaming Service (PSS); Progressive Download and Dynamic Adaptive Streaming over HTTP (3GP-DASH)". +- [30] 3GPP TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction". +- [31] 3GPP TS 26.118: "Virtual Reality (VR) profiles for streaming applications". +- [32] 3GPP TS 37.213: "Physical layer procedures for shared spectrum channel access". +- [33] 3GPP TS 38.401: "NG-RAN; Architecture description". +- [34] 3GPP TS 38.101-5: "NR; User Equipment (UE) radio transmission and reception; Part 5: Satellite access Radio Frequency (RF) and performance requirements". +- [35] 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception". +- [36] 3GPP TS 38.322: "NR; Radio Link Control (RLC) protocol specification". + +# --- 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]. + +**eRedCap UE:** a UE with enhanced reduced capabilities as specified in clause 4.2.22.1. + +**Fallback band combination:** A Uu band combination that would result from another Uu band combination (parent band combination) by releasing at least one SCell or uplink configuration of SCell, or SCG, or SUL. A PC5 band combination that would result from another PC5 band combination (parent band combination) by releasing at least one sidelink carrier. An intra-band non-contiguous band combination is not considered to be a fallback band combination of an intra-band contiguous band combination. A fallback band combination supports the same channel bandwidth(s) for each carrier as its parent band combination(s). + +**Fallback per band feature set:** A feature set per band that has same or lower capabilities than the reported capabilities from the reported feature set per band for a given band. + +**Fallback per CC feature set:** A feature set per CC that has same or lower capabilities than the capabilities of UE (e.g. supported MIMO layers, BW, modulation order) while keeping the numerology the same from the reported feature set + +per CC for a given carrier per band. The *supportedMinBandwidthDL/supportedMinBandwidthUL* defines the lower bound of the bandwidth supported by the UE. + +**RedCap UE:** The UE with reduced capabilities as specified in clause 4.2.21.1. + +**Switching SCell (sSCell):** The SCell configured with cross-carrier scheduling to PCell/PSCell. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|-------------------|--------------------------------------| +| MaxDLDataRate: | Maximum DL data rate | +| MaxDLDataRate_MN: | Maximum DL data rate in the MN | +| MaxDLDataRate_SN: | Maximum DL data rate in the SN | +| MaxULDataRate: | Maximum UL data rate | +| MaxSLtxDataRate: | Maximum SL data rate in transmission | +| MaxSLrxDataRate: | Maximum SL data rate in reception | + +## 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]. + +| | | +|--------|-----------------------------------------------| +| A-CSI | Aperiodic-CSI | +| ATG | Air To Ground | +| BAP | Backhaul Adaptation Protocol | +| BC | Band Combination | +| BPS | Body Proximity Sensing | +| BT | Bluetooth | +| CCS | Cross Carrier Scheduling | +| CMR | Channel Measurement Resource | +| CPAC | Conditional PSCell Addition/Change | +| DAPS | Dual Active Protocol Stack | +| DL | Downlink | +| EHC | Ethernet Header Compression | +| FS | Feature Set | +| FSPC | Feature Set Per Component-carrier | +| GSO | Geosynchronous Orbit | +| HSDN | High Speed Dedicated Network | +| IAB-MT | Integrated Access Backhaul Mobile Termination | +| IDC | In-Device Coexistence | +| MAC | Medium Access Control | +| MHI | Mobility History Information | +| MBS | Multicast/Broadcast Service | +| MCG | Master Cell Group | +| MN | Master Node | +| MO-SDT | Mobile Originated Small Data Transmission | +| MRB | MBS Radio Bearer | +| MR-DC | Multi-Radio Dual Connectivity | +| MSD | Maximum Sensitivity Degradation | +| MT-SDT | Mobile Terminated Small Data Transmission | +| mTRP | Multiple TRP | +| MUSIM | Multi-Universal Subscriber Identity Module | +| NCJT | Non-Coherent Joint Transmission | +| NCR | Network Controlled Repeater | +| NCR-MT | NCR Mobile Termination | +| NCSG | Network Controlled Small Gap | +| NES | Network Energy Savings | +| NGSO | Non-Geosynchronous Orbit | +| NTN | Non-Terrestrial Network | + +| | | +|-------|----------------------------------| +| P-CSI | Periodic CSI | +| PDCP | Packet Data Convergence Protocol | +| PSI | PDU Set Importance | +| QoE | Quality of Experience | +| RLC | Radio Link Control | +| RTT | Round Trip Time | +| SCG | Secondary Cell Group | +| SDAP | Service Data Adaptation Protocol | +| SN | Secondary Node | +| sTRP | Serving TRP | +| TN | Terrestrial Network | +| TRP | Transmit/Receive Point | +| UDC | Uplink Data Compression | +| UL | Uplink | +| WLAN | Wireless Local Area Network | +| XR | eXtended Reality | + +# 4 UE radio access capability parameters + +## 4.1 Supported max data rate + +### 4.1.1 General + +The DL, UL and SL max data rate supported by the UE is calculated by band or band combinations supported by the UE. A UE supporting NR (NR SA, MR-DC) shall support the calculated DL and UL max data rate defined in 4.1.2. A UE supporting NR sidelink communication shall support the calculated SL max data rate defined in 4.1.5. + +### 4.1.2 Supported max data rate for DL/UL + +For NR, the approximate data rate for a given number of aggregated carriers in a band or band combination is computed as follows. + +wherein + +J is the number of aggregated component carriers in a band or band combination + +$R_{max} = 948/1024$ + +For the j-th CC, + +$v_{Layers}^{(j)}$ is the maximum number of supported layers given by *maxNumberMIMO-LayersPDSCH* for downlink and maximum of *maxNumberMIMO-LayersCB-PUSCH* and *maxNumberMIMO-LayersNonCB-PUSCH* for uplink. + +is the maximum supported modulation order given by *supportedModulationOrderDL* for downlink and *supportedModulationOrderUL* for uplink. + +is the scaling factor given by *scalingFactor* or *scalingFactor-1024QAM-FR1* and can take the values 1, 0.8, 0.75, and 0.4. + +is the numerology (as defined in TS 38.211 [6]) + +is the average OFDM symbol duration in a subframe for numerology , i.e. . Note that normal cyclic prefix is assumed. + +is the maximum RB allocation in bandwidth with numerology , as defined in 5.3 TS 38.101-1 [2], 5.3 TS 38.101-2 [3], and 5.3 TS 38.101-5 [34], where is the UE supported maximum bandwidth in the given band or band combination. + +is the overhead and takes the following values + +- 0.14, for frequency range FR1 for DL +- 0.18, for frequency range FR2 for DL +- 0.08, for frequency range FR1 for UL +- 0.10, for frequency range FR2 for UL + +NOTE 1: Only one of the UL or SUL carriers (the one with the higher data rate) is counted for a cell operating SUL. + +NOTE 2: For UL Tx switching between carriers, only the supported MIMO layer combination across carriers that results in the highest combined data rate is counted for the carriers in the supported maximum UL data rate. + +The approximate maximum data rate can be computed as the maximum of the approximate data rates computed using the above formula for each of the supported band or band combinations. For the CCs where UE supports *pdsch-1024QAM-2MIMO-FR1-r17* for the concerned band, data rate shall be derived as maximum what UE would support if using 1024 QAM (when *mcs-Table-r17* or *mcs-TableDCI-1-2-r17* is configured) or 256 QAM. + +For single carrier NR SA operation and except for UEs supporting *supportOfERedCap-r18*, the UE shall support a data rate for the carrier that is no smaller than the data rate computed using the above formula, with $\mu$ and component $\kappa$ is no smaller than 4. + +NOTE 3: As an example, the value 4 in the component above can correspond to $\mu$ , and $\kappa$ . + +For single carrier NR SA operation and for UEs supporting *supportOfERedCap-r18*, the UE shall support a data rate for the carrier that is the data rate computed using the above formula, with $\mu$ and $\kappa$ : + +if the UE supports *eRedCapNotReducedBB-BW-r18*: + +- component $\kappa$ is 0.75 if $\mu = 0$ , or; +- component $\kappa$ is 0.8 if $\mu = 1$ ; +- else: +- component $\kappa$ is 3.2, and; +- $\mu$ is 25 if $\mu = 0$ or, 12 if $\mu = 1$ ; + +For EUTRA in case of MR-DC, the approximate data rate for a given number of aggregated carriers in a band or band combination is computed as follows. + +$$\text{Data rate (in Mbps)} = 10^{-3} \cdot \sum_{j=1}^J TBS_j$$ + +wherein + +$J$ is the number of aggregated EUTRA component carriers in MR-DC band combination + +$TBS_j$ is the total maximum number of DL-SCH transport block bits received or the total maximum number of UL-SCH transport block bits transmitted, within a 1ms TTI for j-th CC, as derived from TS 36.213 [19] based on the UE supported maximum MIMO layers for the j-th CC, and based on the maximum modulation order for the j-th CC and number of PRBs based on the bandwidth of the j-th CC according to indicated UE capabilities. + +The approximate maximum data rate can be computed as the maximum of the approximate data rates computed using the above formula for each of the supported band or band combinations. + +For MR-DC, the approximate maximum data rate is computed as the sum of the approximate maximum data rates from NR and EUTRA. + +### 4.1.3 Void + +### 4.1.4 Total layer 2 buffer size for DL/UL + +The total layer 2 buffer size is defined as the sum of the number of bytes that the UE is capable of storing in the RLC transmission windows and RLC reception and reassembly windows and also in PDCP reordering windows for all radio bearers. + +The required total layer 2 buffer size in MR-DC is the maximum value of the calculated values based on the following equations: + +- $MaxULDataRate\_MN * RLCRTT\_MN + MaxULDataRate\_SN * RLCRTT\_SN + MaxDLDataRate\_SN * RLCRTT\_SN + MaxDLDataRate\_MN * (RLCRTT\_SN + X2/Xn\ delay + Queuing\ in\ SN)$ +- $MaxULDataRate\_MN * RLCRTT\_MN + MaxULDataRate\_SN * RLCRTT\_SN + MaxDLDataRate\_MN * RLCRTT\_MN + MaxDLDataRate\_SN * (RLCRTT\_MN + X2/Xn\ delay + Queuing\ in\ MN)$ + +Otherwise it is calculated by $MaxDLDataRate * RLC\ RTT + MaxULDataRate * RLC\ RTT$ . + +NOTE: Additional L2 buffer required for preprocessing of data is not taken into account in above formula. + +The required total layer 2 buffer size is determined as the maximum total layer 2 buffer size of all the calculated ones for each band combination and the applicable Feature Set combination in the supported MR-DC or NR band combinations. The RLC RTT for NR cell group corresponds to the smallest SCS numerology supported in the band combination and the applicable Feature Set combination. + +wherein + +X2/Xn delay + Queuing in SN = 25ms if SCG is NR, and 55ms if SCG is EUTRA + +X2/Xn delay + Queuing in MN = 25ms if MCG is NR, and 55ms if MCG is EUTRA + +RLC RTT for EUTRA cell group = 75ms + +RLC RTT for NR cell group is defined in Table 4.1.4-1 + +**Table 4.1.4-1: RLC RTT for NR cell group per SCS** + +| SCS (kHz) | RLC RTT (ms) | +|-----------|--------------| +| 15KHz | 50 | +| 30KHz | 40 | +| 60KHz | 30 | +| 120KHz | 20 | +| 480KHz | 20 | +| 960KHz | 20 | + +### 4.1.5 Supported max data rate for SL + +For NR sidelink, the approximate data rate is computed as follows. + +wherein + +$R_{max} = 948/1024$ , + +is the the maximum number of supported layers for sidelink transmission (or reception) given by UE capability on supporting rank 2 PSSCH transmission and *rankTwoReception*, + +is the maximum supported modulation order between 6 or 8 given by *sl-Tx-256QAM* and *sl-Rx-256QAM*, + +is the scaling factor for sidelink transmission and reception given by *scalingFactorTxSidelink* and *scalingFactorRxSidelink* respectively, as specified in TS 36.331 [17] and TS 38.331 [9], and can take the values 1, 0.8, 0.75, and 0.4. + +is the numerology (as defined in TS 38.211 [6]) + +is the average OFDM symbol duration in a subframe for numerology , i.e. . Note that normal cyclic prefix is assumed. + +is the maximum possible RB allocation in bandwidth BW for PSSCH, where BW is the UE supported maximum bandwidth in the given band or band combination, + +is the overhead and takes the following values + +0.217, for frequency range FR1 for SL + +0.25, for frequency range FR2 for SL + +### 4.1.6 Total layer 2 buffer size for NR SL + +The total layer 2 buffer size for NR sidelink communication is defined as the sum of the number of bytes that the UE is capable of storing in the RLC transmission windows and RLC reception and reassembly windows and also in PDCP reordering windows for all radio bearers for NR sidelink communication. + +The required total layer 2 buffer size for NR sidelink communication is the maximum value of the calculated values based on the following equations: + +$$\text{MaxSLtxDataRate} * \text{RLC RTT} + \text{MaxSLrxDataRate} * \text{RLC RTT}.$$ + +NOTE: Additional L2 buffer required for preprocessing of data is not taken into account in above formula. + +The required total layer 2 buffer size for NR sidelink communication is determined as the maximum total layer 2 buffer size of all the calculated ones for each band combination and the applicable Feature Set combination in the supported NR sidelink band combinations. The RLC RTT for NR sidelink communication corresponds to the smallest SCS numerology supported in the band combination and the applicable Feature Set combination. + +wherein + +RLC RTT for NR sidelink communication is defined in Table 4.1.6-1 + +**Table 4.1.6-1: RLC RTT for NR sidelink communication per SCS** + +| SCS (kHz) | RLC RTT (ms) | +|-----------|--------------| +| 15KHz | 200 | +| 30KHz | 100 | +| 60KHz | 50 | +| 120KHz | 25 | + +## 4.2 UE Capability Parameters + +### 4.2.1 Introduction + +The following clauses define the UE radio access capability parameters. Only parameters for which there is the possibility for UEs to signal different values are considered as UE radio access capability parameters. Therefore, mandatory features without capability parameters that are the same for all UEs are not listed here. + +The network needs to respect the signalled UE radio access capability parameters when configuring the UE and when scheduling the UE. + +For capabilities that required to be set consistently for all FDD-FR1 bands (i.e. capabilities that are supposed to be per UE), the UE shall also set capability values for all SUL bands with same values for FDD-FR1 bands if SUL band is supported by the UE. + +The UE may support different functionalities between FDD and TDD, and/or between FR1 and FR2. The UE shall indicate the UE capabilities as follows. In the table of UE capability parameter in subsequent clauses, "Yes" in the column by "FDD-TDD DIFF" and "FR1-FR2 DIFF" indicates the UE capability field can have a different value for between FDD and TDD or between FR1 and FR2 and "No" indicates if it cannot. "(Incl FR2-2 DIFF)" in the column by "FR1-FR2 DIFF" indicates the UE capability field can have a different value for between FR2-1 and FR2-2. Regarding to the per UE capabilities that are FDD/TDD differentiated(i.e. capabilities indicated as "Yes" in the column by "FDD- + +TDD DIFF"), the corresponding capabilities indicated by the FDD capability is applied to SUL if SUL band is supported by the UE. "FD" in the column indicates to refer the associated field description. "FR1 only" or "FR2 only" in the column indicates the associated feature is only supported in FR1 or FR2 and "TDD only" indicates the associated feature is only supported in TDD and not applicable to SUL carriers. "N/A" in the column indicates it is not applicable to the feature (e.g. the signalling supports the UE to have different values between FDD and TDD or between FR1 and FR2). + +- 1> set all fields of UE-NR/MRDC-Capability except fdd-Add-UE-NR/MRDC/Sidelink-Capabilities, tdd-Add-UE-NR/MRDC/Sidelink-Capabilities, fr1-Add-UE-NR/MRDC-Capabilities and fr2-Add-UE-NR/MRDC-Capabilities, to include the values applicable for all duplex mode(s) and frequency range(s) that the UE supports; +- 1> if UE supports both FDD (or SUL) and TDD and if (some of) the UE capability fields have a different value for FDD (or SUL) and TDD + - 2> if for FDD (and, if the UE supports SUL, for SUL), the UE supports additional functionality compared to what is indicated by the previous fields of UE-NR/MRDC-Capability/SidelinkParameters: + - 3> include field fdd-Add-UE-NR/MRDC/Sidelink-Capabilities and set it to include fields reflecting the additional functionality applicable for FDD; + - 2> if for TDD, the UE supports additional functionality compared to what is indicated by the previous fields of UE-NR/MRDC-Capability/SidelinkParameters: + - 3> include field tdd-Add-UE-NR/MRDC/Sidelink-Capabilities and set it to include fields reflecting the additional functionality applicable for TDD; +- 1> if UE supports both FR1 and FR2 and if (some of) the UE capability fields have a different value for FR1 and FR2: + - 2> if for FR1, the UE supports additional functionality compared to what is indicated by the previous fields of UE-NR/MRDC-Capability: + - 3> include field fr1-Add-UE-NR/MRDC-Capabilities and set it to include fields reflecting the additional functionality applicable for FR1; + - 2> if for FR2, the UE supports additional functionality compared to what is indicated by the previous fields of UE-NR/MRDC-Capability: + - 3> include field fr2-Add-UE-NR/MRDC-Capabilities and set it to include fields reflecting the additional functionality applicable for FR2; + +NOTE 1: The fields which indicate "shall be set to 1" or "shall be set to *supported*" in the following tables means these features are purely mandatory and are assumed they are the same as mandatory without capability signalling. + +NOTE 2: For the case where the UE is allowed to support different functionality between FDD and TDD and between FR1 and FR2 according to the specification, the UE capability indication is clarified in Annex B. + +For optional features, the UE radio access capability parameter indicates whether the feature has been implemented and successfully tested. For mandatory features with the UE radio access capability parameter, the parameter indicates whether the feature has been successfully tested. In the table of UE capability parameter in subsequent clauses, "Yes" in the column by "M" indicates the associated feature is mandatory and "No" indicates the associated feature is optional. "CY" in the column indicates the associated feature is conditional mandatory and the condition is described in the field description and the associated feature is considered mandatory with capability parameter, when the described condition is satisfied. "FD" in the column indicates to refer the associated field description. Some parameters in subsequent clauses are not related to UE features and in the case, "N/A" is indicated in the column. + +UE capability parameters have hierarchical structure. In the table of UE capability parameter in subsequent clauses, "Per" indicates the level the associated parameter is included. "UE" in the column indicates the associated parameter is signalled per UE, "Band" indicates it is signalled per band, "BC" indicates it is signalled per band combination, "FS" indicates it is signalled per feature set (per band per band combination), "FSPC" indicates it is signalled per feature set per component carrier (per CC per band per band combination), and "FD" in the column indicates to refer the associated field description. + +NOTE 3: Unless otherwise specified, for dependent capabilities with prerequisite capability in a finer granularity, the UE should indicate support of the prerequisite capability in at least one finer granularity. And the dependent capability is supported only in the finer granularity where the prerequisite capability is supported, e.g. a UE indicating support of *supportNewDMRS-Port-r16* (dependent capability which is defined per band) should indicate at least one band combination where *singleDCI-SDM-scheme-r16* (prerequisite capability which is defined per feature set) is supported in the corresponding band. In this case, *supportNewDMRS-Port-r16* is considered supported only in the corresponding band of the band combination where *singleDCI-SDM-scheme-r16* is supported. + +### 4.2.2 General parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|-----|--------------|--------------| +| accessStratumRelease
Indicates the access stratum release the UE supports as specified in TS 38.331 [9]. | UE | Yes | No | No | +| additionalBSR-Table-r18
Indicates whether the UE supports the BSR enhancements associated with the additional BSR table as specified in TS 38.321 [8] and TS 38.331 [9]. | UE | No | No | No | +| airToGroundNetwork-r18
Indicates whether the UE supports air to ground network access. If the UE indicates this capability the UE shall support the following ATG essential features, e.g., acquiring ATG cell specific SIBxx and ATG cell specific P-Max. | UE | No | No | FR1 only | +| crossCarrierSchedulingConfigurationRelease-r17
Indicates whether the UE supports using crossCarrierSchedulingConfigRelease to release the configurations configured by crossCarrierSchedulingConfig . | UE | No | No | No | +| delayBudgetReporting
Indicates whether the UE supports delay budget reporting as specified in TS 38.331 [9]. | UE | No | No | No | +| delayStatusReport-r18
Indicates whether the UE supports the delay status report of the buffered data as specified in TS 38.321 [8], TS 38.331 [9], TS 38.323 [16] and TS 38.322 [36]. | UE | No | No | No | +| disableCG-RetransmissionMonitoring-r18
Indicates whether the UE supports to disable monitoring for retransmissions corresponding to a ConfiguredGrantConfig as specified in TS 38.321 [8] and TS 38.331 [9]. | UE | No | No | No | +| dl-DedicatedMessageSegmentation-r16
Indicates whether the UE supports reception of segmented DL RRC messages. | UE | No | No | No | +| drx-Preference-r16
Indicates whether the UE supports providing its preference of a cell group on DRX parameters for power saving in RRC_CONNECTED, as specified in TS 38.331 [9]. | UE | No | No | No | +| enhancedDRX-r18
Indicates whether the UE supports DRX enhancements including the support of non-integer DRX periodicity and addressing the SFN wrap around as specified in TS 38.331 [9] and TS 38.321 [8]. | UE | No | No | No | +| gNB-SideRTT-BasedPDC-r17
Indicates whether the UE supports gNB-side RTT-based PDC, as specified in TS 38.300 [28]. A UE supporting this feature shall also support rtt-BasedPDC-CSI-RS-ForTracking-r17 and/or rtt-BasedPDC-PRS-r17 . | UE | No | No | No | +| hardSatelliteSwitchResyncNTN-r18
Indicates whether UE supports hard satellite switch with re-sync, as specified in TS 38.331 [9].
A UE supporting this feature shall also indicate the support of nonTerrestrialNetwork-r17 .
When UE supports this feature and does not support softSatelliteSwitchResyncNTN-r18 , this UE is able to perform hard satellite switch with re-sync in a network supporting soft satellite switch with re-sync, as specified in TS 38.331 [9]. | UE | No | No | No | +| inactiveState
Indicates whether the UE supports RRC_INACTIVE as specified in TS 38.331 [9]. This capability is not applicable to NCR-MT. | UE | Yes | No | No | +| inactiveStateNTN-r17
Indicates whether the UE supports RRC_INACTIVE in NTN as specified in TS 38.331 [9]. It is mandated if the UE indicates the support of nonTerrestrialNetwork-r17 . | UE | CY | No | No | +| inactiveStatePO-Determination-r17
Indicates whether the UE supports to use the same i_s to determine PO in RRC_INACTIVE state as in RRC_IDLE state. | UE | No | No | No | +| inDeviceCoexInd-r16
Indicates whether the UE supports reporting of affected NR carrier frequencies in IDC assistance information as specified in TS 38.331 [9]. | UE | No | No | No | +| inDeviceCoexIndAutonomousDenial-r18
Indicates whether the UE supports IDC autonomous denial as specified in TS 38.331 [9]. A UE supporting this feature shall also support inDeviceCoexInd-r16 . | UE | No | No | No | +| inDeviceCoexIndFDM-r18
Indicates whether the UE supports reporting of affected NR carrier frequency ranges in IDC assistance information as specified in TS 38.331 [9]. A UE supporting this feature shall also support inDeviceCoexInd-r16 . | UE | No | No | No | + +| | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|----|--------------------------| +| inDeviceCoexIndTDM-r18
Indicates whether the UE supports reporting of IDC TDM assistance information as specified in TS 38.331 [9]. A UE supporting this feature shall also support inDeviceCoexInd-r16 . | UE | No | No | No | +| maxBW-Preference-r16, maxBW-Preference-r17
Indicates whether the UE supports providing its preference of a cell group on the maximum aggregated bandwidth for power saving in RRC_CONNECTED, as specified in TS 38.331 [9]. | UE | No | No | Yes
(Incl FR2-2 DIFF) | +| maxCC-Preference-r16
Indicates whether the UE supports providing its preference of a cell group on the maximum number of secondary component carriers for power saving in RRC_CONNECTED, as specified in TS 38.331 [9]. | UE | No | No | No | +| maxMIMO-LayerPreference-r16, maxMIMO-LayerPreference-r17
Indicates whether the UE supports providing its preference of a cell group on the maximum number of MIMO layers for power saving in RRC_CONNECTED, as specified in TS 38.331 [9]. | UE | No | No | Yes
(Incl FR2-2 DIFF) | +| maxMRB-Add-r17
Indicates the additional maximum number of MRBs that the UE supports for MBS multicast reception in RRC_CONNECTED as specified in TS 38.331 [9].

For the UE indicating support of multicastInactive-r18 , this capability is also applicable to multicast reception in RRC_INACTIVE, as specified in TS 38.331 [9]. | UE | No | No | No | +| mcgRLF-RecoveryViaSCG-r16
Indicates whether the UE supports recovery from MCG RLF via split SRB1 (if supported) and via SRB3 (if supported) as specified in TS 38.331[9]. | UE | No | No | No | +| minSchedulingOffsetPreference-r16
Indicates whether the UE supports providing its preference on the minimum scheduling offset for cross-slot scheduling of the cell group for power saving in RRC_CONNECTED, as specified in TS 38.331 [9]. | UE | No | No | No | +| mpsPriorityIndication-r16
Indicates whether the UE supports mpsPriorityIndication on RRC release with redirect as defined in TS 38.331 [9]. | UE | No | No | No | +| mt-SDT-r18
Indicates whether the UE supports initiating MT-SDT procedure via random access procedure with 4-step RA type and if UE supports twoStepRACH-r16 , with 2-step RA type, in response to the reception of MT-SDT indication in paging message, as specified in TS 38.331 [9]. | UE | No | No | No | +| mt-SDT-NTN-r18
Indicates whether the UE supports initiating MT-SDT procedure in NTN via random access procedure with 4-step RA type and if UE supports twoStepRACH-r16 for NTN, with 2-step RA type, in response to the reception of MT-SDT indication in paging message, as specified in TS 38.331 [9]. | UE | No | No | No | +| multiRx-FR2-Preference-r18
Indicates whether the UE supports providing multi-Rx operation preference (i.e. not supporting simultaneous reception with different QCL-typeD) for FR2, as defined in TS 38.331 [9]. | UE | No | No | FR2 only | +| musim-CapabilityRestriction-r18
Indicates whether the UE supports providing MUSIM assistance information with temporary capability restriction and capability restriction indication (i.e., musim-CapabilityRestrictionIndication ), as defined in TS 38.331 [9]. | UE | No | No | No | +| musim-GapPreference-r17
Indicates whether the UE supports providing MUSIM assistance information with MUSIM gap preference and related MUSIM gap configuration, as defined in TS 38.331 [9]. UE supporting this feature supports 3 periodic gaps and 1 aperiodic gap. | UE | No | No | No | +| musim-GapPriorityPreference-r18
Indicates whether the UE supports providing MUSIM assistance information with periodic MUSIM gap priority preference and related periodic MUSIM gap priority configuration, and its preference of keeping all collided MUSIM gaps, as defined in TS 38.331 [9]. A UE supporting this feature shall support musim-GapPreference-r17 . | UE | No | No | No | +| musimLeaveConnected-r17
Indicates whether the UE supports providing MUSIM assistance information with indication of leaving RRC_CONNECTED state as defined in TS 38.331 [9]. | UE | No | No | No | + +| | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|----|----| +| nonTerrestrialNetwork-r17
Indicates whether the UE supports NR NTN access. If the UE indicates this capability the UE shall support the following NTN essential features, e.g., timer extension in MAC/RLC/PDCP layers and RACH adaptation to handle long RTT, acquiring NTN specific SIB and more than one TAC per PLMN broadcast in one cell. | UE | No | No | No | +| ntn-ScenarioSupport-r17
Indicates whether the UE supports the NTN features in GSO scenario or NGSO scenario. If a UE does not include this field but includes nonTerrestrialNetwork-r17 , the UE supports the NTN features for both GSO and NGSO scenarios, and also supports mobility between GSO and NGSO scenarios. | UE | No | No | No | +| onDemandSIB-Connected-r16
Indicates whether the UE supports the on-demand request procedure of SIB(s) or posSIB(s) while in RRC_CONNECTED, as specified in TS 38.331 [9]. | UE | No | No | No | +| overheatingInd
Indicates whether the UE supports overheating assistance information. | UE | No | No | No | +| pei-SubgroupingSupportBandList-r17
Indicates whether the UE supports receiving paging early indication in DCI format 2_7 as specified in TS 38.304 [21] for a list of frequency band. The UE shall support UEID based subgrouping for a frequency band if it indicates supporting of paging early indication reception for the frequency band. The set of OFDM symbols within a slot where UE can monitor the PEI PDCCH in Type 2A CSS is the same as the requirement for paging PDCCH in Type 2 CSS for IDLE and INACTIVE mode UEs. | UE | No | No | No | +| partialFR2-FallbackRX-Req
Indicates whether the UE meets only a partial set of the UE minimum receiver requirements for the eligible FR2 fallback band combinations as defined in Clause 4.2 of TS 38.101-2 [3] and Clause 4.2 of TS 38.101-3 [4]. If not indicated, the UE shall meet all the UE minimum receiver requirements for all the FR2 fallback combinations in TS 38.101-2 [3] and TS 38.101-3 [4]. The UE shall support configuration of any of the FR2 fallback band combinations regardless of the presence or the absence of this field. | UE | No | No | No | +| pdu-SetDiscard-r18
Indicates whether the UE supports PDU set based discard operation (i.e. pdu-SetDiscard-r18 configuration, as specified in TS 38.331 [9]).
UE supporting pdu-SetDiscard-r18 shall also support the ability to identify PDU sets for UL XR traffic. | UE | No | No | No | +| psi-BasedDiscard-r18
Indicates whether the UEs supports PSI based discard (i.e. discardTimerForLowImportance-r18 configuration, as specified in TS 38.331 [9]).
UE supporting psi-BasedDiscard-r18 shall also support the ability to identify PDU sets and PSI for UL XR traffic. | UE | No | No | No | +| ra-InsteadCG-SDT-r18
Indicates whether the UE supports the selection of RACH resources instead of configured grant type 1 resource when triggering resume for MO-SDT or MT-SDT and next configured grant type 1 resource is too far, as specified in TS 38.331 [9].
A UE supporting this feature shall also indicate the support of cgr-SDT-r17 , or mt-cgr-SDT-r18 . | UE | No | No | No | +| ra-SDT-r17
Indicates whether the UE supports initiating MO-SDT procedure (i.e. transmission of data and/or signalling over allowed radio bearers in RRC_INACTIVE state) via Random Access procedure (i.e., RA-SDT) with 4-step RA type and if UE supports twoStepRACH-r16 , with 2-step RA type, as specified in TS 38.331 [9]. | UE | No | No | No | +| ra-SDT-NTN-r17
Indicates whether the UE supports initiating MO-SDT procedure (i.e. transmission of data and/or signalling over allowed radio bearers in RRC_INACTIVE state) in NTN via Random Access procedure (i.e., RA-SDT) with 4-step RA type and if UE supports twoStepRACH-r16 for NTN, with 2-step RA type, as specified in TS 38.331 [9]. A UE supporting this feature shall also indicate the support of nonTerrestrialNetwork-r17 . | UE | No | No | No | +| redirectAtResumeByNAS-r16
Indicates whether the UE supports reception of redirectedCarrierInfo in an RRCRelease message in response to an RRCResumeRequest or RRCResumeRequest1 which is triggered by the NAS layer, as specified in TS 38.331 [9]. | UE | No | No | No | +| reducedCP-Latency
Indicates whether the UE supports reduced control plane latency as defined in TS 38.331 [9] | UE | No | No | No | + +| | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|-----|----|----------| +| referenceTimeProvision-r16
Indicates whether the UE supports provision of referenceTimeInfo in DLInformationTransfer message and in SIB9 and reference time information preference indication via assistance information, as specified in TS 38.331 [9]. | UE | No | No | No | +| releasePreference-r16
Indicates whether the UE supports providing its preference assistance information to transition out of RRC_CONNECTED for power saving, as specified in TS 38.331 [9]. | UE | No | No | No | +| requirementTypeIndication-r16
Indicates whether the UE supports network control of requirement applicability for UE supporting interBandMRDC-WithOverlapDL-Bands-r16. This field is only applicable to the UE indicating interBandMRDC-WithOverlapDL-Bands-r16 .
The UE supports this feature shall also indicate support of interBandMRDC-WithOverlapDL-Bands-r16 . | UE | No | No | FR1 only | +| resumeAfterSDT-Release-r18
Indicates whether the UE supports immediate RRC connection resume procedure triggering after receiving RRCRelease message with a resumeIndication included during an ongoing SDT procedure, as specified in TS 38.331 [9].
The UE indicating support of this feature shall also support any of ra-SDT-r17 , ra-SDT-NTN-r17 , cq-SDT-r17 , mt-SDT-r18 , mt-SDT-NTN-r18 or mt-CG-SDT-r18 . | UE | No | No | No | +| resumeWithStoredMCG-SCells-r16
Indicates whether the UE supports not deleting the stored MCG SCell configuration when initiating the resume procedure. | UE | No | No | No | +| resumeWithStoredSCG-r16
Indicates whether the UE supports not deleting the stored SCG configuration when initiating resume. The UE which indicates support for resumeWithStoredSCG-r16 shall also indicate support for resumeWithSCG-Config-r16 . | UE | No | No | No | +| resumeWithSCG-Config-r16
Indicates whether the UE supports (re-)configuration of an SCG during the resume procedure. | UE | No | No | No | +| sliceInfoforCellReselection-r17
Indicates whether the UE supports slice-based cell reselection information in SIB and on RRC release for slice-based cell reselection in RRC_IDLE and RRC_INACTIVE as defined in TS 38.304 [21]. | UE | No | No | No | +| splitSRB-WithOneUL-Path
Indicates whether the UE supports UL transmission via MCG path and DL reception via either MCG path or SCG path, as specified for the split SRB in TS 37.340 [7].
The UE shall not set the FDD/TDD specific fields for this capability (i.e. it shall not include this field in UE-MRDC-CapabilityAddXDD-Mode ). | UE | No | No | No | +| softSatelliteSwitchResyncNTN-r18
Indicates whether UE supports soft satellite switch with re-sync, as specified in TS 38.331 [9].
A UE supporting this feature shall also indicate support of hardSatelliteSwitchResyncNTN-r18 . | UE | No | No | No | +| splitDRB-withUL-Both-MCG-SCG
Indicates whether the UE supports UL transmission via both MCG path and SCG path for the split DRB as specified in TS 37.340 [7]. The UE shall not set the FDD/TDD specific fields for this capability (i.e. it shall not include this field in UE-MRDC-CapabilityAddXDD-Mode ). | UE | Yes | No | No | +| srb3
Indicates whether the UE supports SRB3 which is a direct SRB between the SN and the UE as specified in TS 37.340 [7]. The UE shall not set the FDD/TDD specific fields for this capability (i.e. it shall not include this field in UE-MRDC-CapabilityAddXDD-Mode ). This field is not applied to NE-DC. | UE | Yes | No | No | +| srb-SDT-NTN-r17
Indicates whether the UE supports the usage of signalling radio bearer SRB2 for MO-SDT (over RA-SDT or CG-SDT) or MT-SDT (over RA or CG-SDT) in NTN, as specified in TS 38.331 [9].

A UE supporting this feature shall also indicate support of ra-SDT-NTN-r17 , cq-SDT-r17 , mt-SDT-NTN-r18 or mt-CG-SDT-r18 in NTN bands. A UE supporting this feature shall also indicate the support of nonTerrestrialNetwork-r17 . | UE | No | No | No | +| srb-SDT-r17
Indicates whether the UE supports the usage of signalling radio bearer SRB2 for MO-SDT (over RA-SDT or CG-SDT) or MT-SDT (over RA or CG-SDT), as specified in TS 38.331 [9].

A UE supporting this feature shall also indicate support of ra-SDT-r17 , cq-SDT-r17 , mt-SDT-r18 or mt-CG-SDT-r18 . | UE | No | No | No | + +| | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|----|----------| +| ul-GapFR2-Pattern-r17
Indicates FR2 UL gap pattern(s) supported by the UE for NR SA, for NR-DC without FR2-FR2 band combination, for NE-DC, and for (NG)EN-DC, if UE supports a band in FR2. The leading / leftmost bit (bit 0) corresponds to the FR2 UL gap pattern 0, the next bit corresponds to the FR2 UL gap pattern 1, as specified in TS 38.133 [5] and so on. The UE shall set at least one of the bits to 1 for FR2 UL gap pattern 1 and 3, if the UE indicates support for ul-GapFR2-r17 in an FR2 band. | UE | CY | No | FR2 only | +| ul-RRC-Segmentation-r16
Indicates whether the UE supports uplink RRC segmentation of UECapabilityInformation as specified in TS 38.331 [9]. | UE | No | No | No | +| ul-TrafficInfo-r18
Indicates whether UE supports sending UE assistance information with UL traffic information such as jitter range, burst arrival time, data burst periodicity and whether UE is able to identify PDU Set related information per UL QoS flow as specified in TS 38.331 [9]. | UE | No | No | No | + +### 4.2.3 SDAP Parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | +|---------------------------------------------------------------------------------|-----|----|--------------| +| as-ReflectiveQoS
Indicates whether the UE supports AS reflective QoS. | UE | No | No | + +### 4.2.4 PDCP Parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|-----|--------------| +| continueEHC-Context-r16
Indicates that the UE supports EHC context continuation operation where the UE keeps the established EHC context(s) upon PDCP re-establishment, as specified in TS 38.323 [16]. | UE | No | No | +| continueROHC-Context
Defines whether the UE supports ROHC context continuation operation where the UE does not reset the current ROHC context upon PDCP re-establishment, as specified in TS 38.323 [16]. | UE | No | No | +| ehc-r16
Indicates that the UE supports Ethernet header compression and decompression using EHC protocol, as specified in TS 38.323 [16]. The UE indicating this capability and indicating support for at least one ROHC profile, shall support simultaneous configuration of EHC and ROHC on different DRBs/multicast MRBs. | UE | No | No | +| extendedDiscardTimer-r16
Indicates whether the UE supports the additional values of PDCP discard timer. The supported additional values are 0.5ms, 1ms, 2ms, 4ms, 6ms and 8ms, as specified in TS 38.331 [9]. | UE | No | No | +| jointEHC-ROHC-Config-r16
Indicates whether the UE supports simultaneous configuration of EHC and ROHC protocols for the same DRB/multicast MRB. | UE | No | No | +| maxNumberROHC-ContextSessions
Defines the maximum number of ROHC header compression context sessions supported by the UE across all DRBs and multicast MRBs, excluding context sessions that leave all headers uncompressed. | UE | No | No | +| maxNumberEHC-Contexts-r16
Defines the maximum number of Ethernet header compression contexts supported by the UE across all DRBs and multicast MRBs and across UE's EHC compressor and EHC decompressor. The indicated number defines the number of contexts in addition to CID = "all zeros" as specified in TS 38.323 [16]. | UE | No | No | +| outOfOrderDelivery
Indicates whether UE supports out of order delivery of data to upper layers by PDCP. | UE | No | No | +| pdcp-DuplicationMCG-OrSCG-DRB
Indicates whether the UE supports CA-based PDCP duplication over MCG or SCG DRB as specified in TS 38.323 [16]. | UE | No | No | +| pdcp-DuplicationMoreThanTwoRLC-r16
Defines whether the UE supports PDCP duplication with more than two RLC entities as specified in TS 38.323 [16]. The UE supporting this feature supports secondary RLC entity(ies) activation and deactivation based on duplication RLC Activation/Deactivation MAC CE as specified in TS 38.321 [8]. A UE supporting this feature shall also support pdcp-DuplicationMCG-OrSCG-DRB , pdcp-DuplicationSplitDRB , pdcp-DuplicationSplitSRB and pdcp-DuplicationSRB . | UE | No | No | +| pdcp-DuplicationSplitDRB
Indicates whether the UE supports PDCP duplication over split DRB as specified in TS 38.323 [16]. | UE | No | No | +| pdcp-DuplicationSplitSRB
Indicates whether the UE supports PDCP duplication over split SRB1/2 as specified in TS 38.323 [16]. | UE | No | No | +| pdcp-DuplicationSRB
Indicates whether the UE supports CA-based PDCP duplication over SRB1/2 and/or, if (NG)EN-DC is supported, SRB3 as specified in TS 38.323 [16]. | UE | No | No | +| shortSN
Indicates whether the UE supports 12 bit length of PDCP sequence number. | UE | Yes | No | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|----| +|

supportedROHC-Profiles
Defines which ROHC profiles from the list below are supported by the UE:

  • - 0x0000 ROHC No compression (RFC 5795)
  • - 0x0001 ROHC RTP/UDP/IP (RFC 3095, RFC 4815)
  • - 0x0002 ROHC UDP/IP (RFC 3095, RFC 4815)
  • - 0x0003 ROHC ESP/IP (RFC 3095, RFC 4815)
  • - 0x0004 ROHC IP (RFC 3843, RFC 4815)
  • - 0x0006 ROHC TCP/IP (RFC 6846)
  • - 0x0101 ROHC RTP/UDP/IP (RFC 5225)
  • - 0x0102 ROHC UDP/IP (RFC 5225)
  • - 0x0103 ROHC ESP/IP (RFC 5225)
  • - 0x0104 ROHC IP (RFC 5225)

A UE that supports one or more of the listed ROHC profiles shall support ROHC profile 0x0000 ROHC uncompressed (RFC 5795).
An IMS voice capable UE shall indicate support of ROHC profiles 0x0000, 0x0001, 0x0002 and be able to compress and decompress headers of PDCP SDUs at a PDCP SDU rate corresponding to supported IMS voice codecs.

| UE | No | No | +|

udc-r17
Indicates whether the UE supports the uplink data compression operation as specified in TS 38.323 [16]. The capability signalling comprises of the following parameters:

  • - standardDictionary-r17 indicates whether the UE supports UL data compression with SIP static dictionary as defined in TS 38.323 [16].
  • - operatorDictionary-r17 indicates whether the UE supports UL data compression with operator defined dictionary. In this release, the UE can only support one operator defined dictionary. If the UE supports operator defined dictionary, the UE shall report versionOfDictionary-r17 and associatedPLMN-ID-r17 of the stored operator defined dictionary as defined in TS 38.331 [9]. This parameter is not required to be present if the UE is in VPLMN. The associatedPLMN-ID-r17 is only associated to the operator defined dictionary which has no relationship with UE's HPLMN ID.
  • - continueUDC-r17 indicates whether the UE supports continuation of uplink data compression protocol operation where the UE does not reset the buffer upon PDCP re-establishment, as specified in TS 38.323 [16].
  • - supportOfBufferSize-r17 indicates which compression buffer size the UE supports as specified in TS 38.323 [16]. Value kbyte4 means the UE supports 4096 bytes for compression buffer per UDC DRB. Value kbyte8 means the UE supports 8192 bytes for compression buffer per UDC DRB.

A UE that supports the uplink data compression operation shall support 2048 bytes for compression buffer per UDC DRB and support up to 2 UDC DRBs.

| UE | No | No | +|

uplinkOnlyROHC-Profiles
Indicates the ROHC profile(s) that are supported in uplink-only ROHC operation by the UE.

  • - 0x0006 ROHC TCP (RFC 6846)

A UE that supports uplink-only ROHC profile(s) shall support ROHC profile 0x0000 ROHC uncompressed (RFC 5795).

| UE | No | No | + +### 4.2.5 RLC parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|-----|--------------| +| am-WithShortSN
Indicates whether the UE supports AM DRB with 12 bit length of RLC sequence number. | UE | Yes | No | +| extendedT-PollRetransmit-r16
Indicates whether the UE supports the additional values of T-PollRetransmit timer . The supported additional values are 1ms, 2ms, 3ms and 4ms, as specified in TS 38.331 [9]. | UE | No | No | +| extendedT-StatusProhibit-r16
Indicates whether the UE supports the additional values of T-StatusProhibit timer . The supported additional values are 1ms, 2ms, 3ms and 4ms, as specified in TS 38.331 [9]. | UE | No | No | +| um-WithLongSN
Indicates whether the UE supports UM DRB with 12 bit length of RLC sequence number. | UE | Yes | No | +| um-WithShortSN
Indicates whether the UE supports UM DRB with 6 bit length of RLC sequence number. | UE | Yes | No | + +### 4.2.6 MAC parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----|--------------|-----------------------| +| autonomousTransmission-r16
Indicates whether the UE supports autonomous transmission of the MAC PDU generated for a deprioritized configured uplink grant as specified in TS 38.321 [8]. A UE supporting this feature shall also support Ich-priorityBasedPrioritization-r16 . | UE | No | No | No | +| directMCG-SCellActivation-r16, directMCG-SCellActivation-r17
Indicates whether the UE supports direct NR MCG SCell activation, as specified in TS 38.321 [8], upon SCell addition, upon reconfiguration with sync of the MCG, as specified in TS 38.331 [9]. | UE | No | No | Yes (Incl FR2-2 DIFF) | +| directMCG-SCellActivationResume-r16, directMCG-SCellActivationResume-r17
Indicates whether the UE supports direct NR MCG SCell activation, as specified in TS 38.321 [8], upon reception of an RRCResume message, as specified in TS 38.331 [9]. | UE | No | No | Yes (Incl FR2-2 DIFF) | +| directSCG-SCellActivation-r16, directSCG-SCellActivation-r17
Indicates whether the UE supports direct NR SCG SCell activation, as specified in TS 38.321 [8], upon SCell addition and upon reconfiguration with sync of the SCG, both performed via an RRCReconfiguration message received via SRB3 or contained in an RRC(Connection)Reconfiguration message received via SRB1, as specified in TS 38.331 [9] and TS 36.331 [17].
A UE indicating support of directSCG-SCellActivation-r16 shall indicate support of EN-DC or support of NGEN-DC as specified in TS 36.331 [17] or support of NR-DC as specified in TS 38.331 [9]. | UE | No | No | Yes (Incl FR2-2 DIFF) | +| directSCG-SCellActivationResume-r16, directSCG-SCellActivationResume-r17
Indicates whether the UE supports direct NR SCG SCell activation, as specified in TS 38.321 [8]:
- upon reception of an RRCReconfiguration included in an RRCConnectionResume message, as specified in TS 38.331 [9] and TS 36.331 [17], if the UE indicates support of EN-DC or NGEN-DC, and support of resumeWithSCG-Config-r16 as specified in TS 36.331 [17],
- upon reception of an RRCReconfiguration included in an RRCResume message, as specified in TS 38.331 [9], if the UE indicates support of NR-DC and of resumeWithSCG-Config-r16 as specified in TS 38.331 [9].
A UE indicating support of directSCG-SCellActivationResume-r16 shall indicate support of EN-DC or NGEN-DC and support of resumeWithSCG-Config-r16 as specified in TS 36.331 [17] or indicate support of NR-DC and of resumeWithSCG-Config-r16 as specified in TS 38.331 [9]. | UE | No | No | Yes (Incl FR2-2 DIFF) | + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|-----------------------| +|

drx-Adaptation-r16, drx-Adaptation-r17
Indicates whether the UE supports DRX adaptation comprised of the following functional components:

  • - Configured ps-Offset for the detection of DCI format 2_6 with CRC scrambling by ps-RNTI and reported MinTimeGap or MinTimeGapFR2-2 before the start of drx-onDurationTimer of Long DRX
  • - Indication of UE whether or not to start drx-onDurationTimer for the next Long DRX cycle by detection of DCI format 2_6
  • - Configured UE wakeup or not when DCI format 2_6 is not detected at all monitoring occasions outside Active Time
  • - Configured periodic CSI report apart from L1-RSRP (ps-TransmitOtherPeriodicCSI) when impacted by DCI format 2_6 that drx-onDurationTimer does not start for the next Long DRX cycle
  • - Configured periodic L1-RSRP report (ps-TransmitPeriodicL1-RSRP) when impacted by DCI format 2_6 that drx-onDurationTimer does not start for the next Long DRX cycle

The capability signalling includes the minimum time gap between the end of the slot of last DCI format 2_6 monitoring occasion and the beginning of the slot where the UE would start the drx-onDurationTimer of Long DRX for each SCS. The value sl1 indicates 1 slot. The value sl2 indicates 2 slots, and so on. Support of this feature is reported for licensed and unlicensed bands, respectively. When drx-Adaptation-r16 is reported, either of sharedSpectrumChAccess-r16 or non-SharedSpectrumChAccess-r16 shall be reported, at least. When drx-Adaptation-r17 is reported, either of sharedSpectrumChAccess-r17 or non-SharedSpectrumChAccess-r17 shall be reported, at least.

| UE | No | No | Yes (Incl FR2-2 DIFF) | +|

enhancedSkipUplinkTxConfigured-r16
Indicates whether the UE supports skipping UL transmission for a configured uplink grant only if no data is available for transmission and no UCI is multiplexed on the corresponding PUSCH of the uplink grant as specified in TS 38.321 [8].

| UE | No | Yes | No | +|

enhancedSkipUplinkTxDynamic-r16
Indicates whether the UE supports skipping UL transmission for an uplink grant addressed to a C-RNTI only if no data is available for transmission and no UCI is multiplexed on the corresponding PUSCH of the uplink grant as specified in TS 38.321 [8].

| UE | No | Yes | No | +|

enhancedUuDRX-forSidelink-r17
Indicates whether UE supports sidelink related Uu-DRX mechanisms for PDCCH monitoring. This field is only applicable if the UE supports sl-TransmissionMode1-r16.

| UE | No | No | No | +|

extendedDRX-CycleInactive-r17
Indicates whether UE supports the extended DRX in RRC_INACTIVE with values of 256, 512 and 1024 radio frames as specified in TS 38.331 [9]. The UE may indicate support for extended DRX in RRC_INACTIVE only if it supports extended DRX in RRC_IDLE.

| UE | No | No | No | +|

extendedDRX-CycleInactive-r18
Indicates whether UE supports the extended DRX in RRC_INACTIVE with values above 1024 radio frames as specified in TS 38.331 [9] and TS 38.304 [21]. The UE may indicate support of this capability only if it supports extended DRX in RRC_IDLE.

| UE | No | No | No | +|

harq-FeedbackDisabled-r17
Indicates whether the UE supports disabled HARQ feedback for downlink transmission. A UE supporting this feature shall also indicate the support of nonTerrestrialNetwork-r17.

| UE | No | No | No | +|

intraCG-Prioritization-r17
Indicates whether the UE supports the HARQ process ID selection based on LCH priority as specified in TS 38.321 [8]. A UE supporting this feature shall also support jointPrioritizationCG-Retx-Timer-r17.

| UE | No | No | No | +|

jointPrioritizationCG-Retx-Timer-r17
Indicates whether the UE supports simultaneous configuration of LCH based prioritization and cg-RetransmissionTimer-r16 as specified in TS 38.321 [8]. A UE supporting this feature shall also support lch-priorityBasedPrioritization-r16 and configuredGrantWithRetx-r16.

| UE | No | No | No | +|

lastTransmissionUL-r17
Indicates whether the UE supports starting the drx-HARQ-RTT-TimerUL after the end of the last transmission within a bundle as specified in TS 38.321 [8].

| UE | No | No | No | + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|-----|-----|----| +| lch-PriorityBasedPrioritization-r16
Indicates whether the UE supports prioritization between overlapping grants and between scheduling request and overlapping grants based on LCH priority as specified in TS 38.321 [8]. | UE | No | No | No | +| lch-ToConfiguredGrantMapping-r16
Indicates whether the UE supports restricting data transmission from a given LCH to a configured (sub-) set of configured grant configurations (see allowedCG-List-r16 in LogicalChannelConfig in TS 38.331 [9]) as specified in TS 38.321 [8]. | UE | No | No | No | +| lch-ToGrantPriorityRestriction-r16
Indicates whether the UE supports restricting data transmission from a given LCH to a configured (sub-) set of dynamic grant priority levels (see allowedPHY-PriorityIndex-r16 in LogicalChannelConfig in TS 38.331 [9]) as specified in TS 38.321 [8]. | UE | No | No | No | +| lch-ToSCellRestriction
Indicates whether the UE supports restricting data transmission from a given LCH to a configured (sub-) set of serving cells (see allowedServingCells in LogicalChannelConfig ). A UE supporting pdcp-DuplicationMCG-OrSCG-DRB or pdcp-DuplicationSRB (see PDCP-Config ) shall also support lch-ToSCellRestriction . | UE | No | No | No | +| lcp-Restriction
Indicates whether UE supports the selection of logical channels for each UL grant based on RRC configured restriction using RRC parameters allowedSCS-List , maxPUSCH-Duration , and configuredGrantType1Allowed as specified in TS 38.321 [8]. | UE | No | No | No | +| logicalChannelSR-DelayTimer
Indicates whether the UE supports the logicalChannelSR-DelayTimer as specified in TS 38.321 [8]. | UE | No | Yes | No | +| longDRX-Cycle
Indicates whether UE supports long DRX cycle as specified in TS 38.321 [8]. | UE | Yes | Yes | No | +| mg-ActivationCommPRS-Meas-r17
Indicates whether UE supports preconfiguration of MGs in RRC signalling for PRS measurements and the use of DL MAC CE from the gNB, as specified in TS 38.321 [8], to activate/deactivate the preconfigured MG for PRS measurements. | UE | No | No | No | +| mg-ActivationRequestPRS-Meas-r17
Indicates whether UE supports preconfiguration of MGs in RRC signalling for PRS measurements and supports the use of UL MAC CE, as specified in TS 38.321 [8], to request the activation/deactivation of the preconfigured MG for PRS measurements. The UE can include this field only if the UE supports mg-ActivationCommPRS-Meas-r17 . | UE | No | No | No | +| multipleConfiguredGrants
Indicates whether UE supports more than one configured grant configurations (including both Type 1 and Type 2) in a cell group. For each cell, the UE supports at most one configured grant per BWP and the maximum number of configured grant configurations per cell group is 2. If absent, for each configured cell group, the UE only supports one configured grant configuration on one serving cell. | UE | No | Yes | No | +| multipleSR-Configurations
Indicates whether the UE supports 8 SR configurations per PUCCH cell group as specified in TS 38.321 [8]. | UE | No | Yes | No | +| ptmRetransmission-r18
Indicates whether the UE supports starting drx-HARQ-RTT-TimerDL-PTM and drx-RetransmissionTimerDL-PTM during multicast reception in RRC_CONNECTED state as specified in TS 38.321 [8], when HARQ feedback is disabled for the UE.

A UE supporting this feature shall also indicate support of dynamicMulticastPCell-r17 , and at least one of the following features:
  • - ack-NACK-FeedbackForMulticast-r17
  • - ack-NACK-FeedbackForSPS-Multicast-r17
  • - nack-OnlyFeedbackForMulticast-r17
  • - nack-OnlyFeedbackForSPS-Multicast-r17
| UE | No | Yes | No | +| ptmRetransmissionInactive-r18
Indicates whether the UE supports receiving PTM retransmission by starting the drx-HARQ-RTT-TimerDL-PTM and drx-RetransmissionTimerDL-PTM during multicast reception in RRC_INACTIVE as specified in TS 38.321 [8]. A UE supporting this feature shall also indicate support of multicastInactive-r18 . | UE | No | Yes | No | +| recommendedBitRate
Indicates whether the UE supports the bit rate recommendation message from the gNB to the UE as specified in TS 38.321 [8]. | UE | No | No | No | + +| | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|-----|----------|----------| +| recommendedBitRateMultiplier-r16
Indicates whether the UE supports the bit rate multiplier for recommended bit rate MAC CE as specified in TS 38.321 [8], clause 6.1.3.20. This field is only applicable if the UE supports recommendedBitRate . | UE | No | No | No | +| recommendedBitRateQuery
Indicates whether the UE supports the bit rate recommendation query message from the UE to the gNB as specified in TS 38.321 [8]. This field is only applicable if the UE supports recommendedBitRate . | UE | No | No | No | +| secondaryDRX-Group-r16
Indicates whether UE supports secondary DRX group as specified in TS 38.321 [8]. | UE | No | Yes | No | +| shortDRX-Cycle
Indicates whether UE supports short DRX cycle as specified in TS 38.321 [8]. | UE | Yes | Yes | No | +| simultaneousSR-PUSCH-DiffPUCCH-groups-r17
Indicates whether the UE supports simultaneous transmission of SR and PUSCH in different PUCCH groups as specified in TS 38.321 [8]. | UE | No | No | No | +| singlePHR-P-r16
Indicates whether UE supports the P bit in single PHR MAC CE as specified in TS 38.321 [8]. | UE | No | No | No | +| skipUplinkTxDynamic
Indicates whether the UE supports skipping of UL transmission for an uplink grant indicated on PDCCH if no data is available for transmission as specified in TS 38.321 [8]. | UE | No | Yes | No | +| spCell-BFR-CBRA-r16
Indicates whether the UE supports sending BFR MAC CE for SpCell BFR as specified in TS 38.321 [8]. | UE | No | No | No | +| srs-ResourceId-Ext-r16
Indicates whether the UE supports the extended 6-bit (Positioning) SRS resource ID in SP Positioning SRS Activation/Deactivation MAC CE, as specified in TS 38.321 [8]. | UE | No | No | No | +| sr-TriggeredBy-TA-Report-r17
Indicates whether the UE supports triggering of SR when a TA report is triggered and there are no available UL-SCH resources. A UE supporting this feature shall also indicate the support of nonTerrestrialNetwork-r17 . | UE | No | No | No | +| sr-TriggeredByTA-ReportATG-r18
Indicates whether the UE supports triggering of SR when a TA report is triggered and there are no available UL-SCH resources. A UE supporting this feature shall also indicate the support of uplinkTA-ReportingATG-r18 . | UE | No | No | FR1 only | +| survivalTime-r17
Indicates whether the UE supports services with survival time requirement using configured grant resource and PDCP duplication, as specified in TS 38.321 [8]. A UE supporting this feature shall support pdcp-DuplicationMCG-orSCG-DRB or pdcp-DuplicationSplitDRB . A UE supporting this feature shall also support configuredUL-GrantType1-v1650 or configuredUL-GrantType2-v1650 . | UE | No | No | No | +| tdd-MPE-P-MPR-Reporting-r16
Indicates whether the UE supports P-MPR reporting for Maximum Permissible Exposure, as specified in TS 38.321 [8]. | UE | No | TDD only | FR2 only | +| ul-LBT-FailureDetectionRecovery-r16
Indicates whether the UE supports consistent uplink LBT detection and recovery, as specified in TS 38.321 [8], for cells operating with shared spectrum channel access. This field applies to all serving cells with which the UE is configured with shared spectrum channel access. | UE | No | No | No | +| uplink-Harq-ModeB-r17
Indicates whether the UE supports HARQ Mode B and the corresponding LCP restrictions for uplink transmission. A UE supporting this feature shall also indicate the support of nonTerrestrialNetwork-r17 . | UE | No | No | No | +| uplinkTA-ReportingATG-r18
Indicates whether the UE supports reporting of information related to TA pre-compensation as specified in TS 38.321 [8]. The UE indicating support of this feature shall also indicate support of uplinkPreCompensationATG-r18 . | UE | No | No | FR1 only | + +### 4.2.7 Physical layer parameters + +#### 4.2.7.1 *BandCombinationList* parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----|--------------|--------------| +| bandEUTRA
Defines supported EUTRA frequency band by NR frequency band number, as specified in TS 36.101 [14]. | Band | Yes | N/A | N/A | +| bandList
Each entry of the list should include at least one bandwidth class for UL or DL. | BC | Yes | N/A | N/A | +| bandNR
Defines supported NR frequency band by NR frequency band number, as specified in TS 38.101-1 [2] and TS 38.101-2 [3]. | Band | Yes | N/A | N/A | +| ca-BandwidthClassDL-EUTRA
Defines for DL, the class defined by the aggregated transmission bandwidth configuration and maximum number of component carriers supported by the UE, as specified in TS 36.101 [14]. When all FeatureSetEUTRA-DownlinkId:s in the corresponding FeatureSetsPerBand are zero, this field is absent. | Band | No | N/A | N/A | +| ca-BandwidthClassDL-NR
Defines for DL, the class defined by the aggregated transmission bandwidth configuration and maximum number of component carriers supported by the UE, as specified in TS 38.101-1 [2] and TS 38.101-2 [3]. When all FeatureSetDownlinkId:s in the corresponding FeatureSetsPerBand are zero, this field is absent. For FR1, the value 'F' shall not be used as it is invalidated in TS 38.101-1 [2]. | Band | No | N/A | N/A | +| ca-BandwidthClassDL-NR-r17
Defines for DL, additional FR2 CA bandwidth class (e.g., R, S, T, U) as specified in TS 38.101-2 [3]. When all FeatureSetDownlinkId:s in the corresponding FeatureSetsPerBand are zero, this field is absent.

If this field is indicated for a band, the UE shall also set ca-BandwidthClassDL-NR (without suffix) to the highest bandwidth class from the same fallback group that it supports in this band combination and with the given bandwidth combination set ID in case that the bandwidth combination consists of a sub-set of carriers and the same or a sub-set of carrier bandwidths on those carriers with respect to the bandwidth combination corresponding to ca-BandwidthClassDL-NR-r17 ; otherwise, it shall omit the ca-BandwidthClassDL-NR (without suffix) field.

NOTE: If the UE includes ca-BandwidthClassDL-NR-r17 in a BandParameter the network ignores the ca-BandwidthClassDL-NR therein, if signalled. | Band | No | N/A | FR2 only | +| ca-BandwidthClassUL-EUTRA
Defines for UL, the class defined by the aggregated transmission bandwidth configuration and maximum number of component carriers supported by the UE, as specified in TS 36.101 [14]. When all FeatureSetEUTRA-UplinkId:s in the corresponding FeatureSetsPerBand are zero, this field is absent. | Band | No | N/A | N/A | +| ca-BandwidthClassUL-NR
Defines for UL, the class defined by the aggregated transmission bandwidth configuration and maximum number of component carriers supported by the UE, as specified in TS 38.101-1 [2] and TS 38.101-2 [3]. When all FeatureSetUplinkId:s in the corresponding FeatureSetsPerBand are zero, this field is absent. For FR1, the value 'F' shall not be used as it is invalidated in TS 38.101-1 [2]. | Band | No | N/A | N/A | +| ca-BandwidthClassUL-NR-r17
Defines for UL, additional FR2 CA bandwidth class (e.g., R, S, T, U) as specified in TS 38.101-2 [3]. When all FeatureSetUplinkId:s in the corresponding FeatureSetsPerBand are zero, this field is absent.

If this field is indicated for a band, the UE shall also set ca-BandwidthClassUL-NR (without suffix) to the highest bandwidth class from the same fallback group that it supports in this band combination and with the given bandwidth combination set ID in case that the bandwidth combination consists of a sub-set of carriers and the same or a sub-set of carrier bandwidths on those carriers with respect to the bandwidth combination corresponding to ca-BandwidthClassUL-NR-r17 ; otherwise, it shall omit the ca-BandwidthClassUL-NR (without suffix) field.

NOTE: If the UE includes ca-BandwidthClassUL-NR-r17 in a BandParameter the network ignores the ca-BandwidthClassUL-NR therein, if signalled. | Band | No | N/A | FR2 only | +| ca-ParametersEUTRA
Contains the EUTRA part of band combination parameters for a given (NG)EN-DC/NE-DC band combination. | BC | No | N/A | N/A | + +| | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|-----|-----|----------| +| ca-ParametersNR
Contains the NR band combination parameters for a given (NG)EN-DC/NE-DC and/or NR CA band combination. | BC | No | N/A | N/A | +| ca-ParametersNRDC
Indicates whether the UE supports NR-DC for the band combination. It contains the NR band combination parameters applicable across MCG and SCG. If the band combination includes both FR1 and FR2 bands, a UE indicating support for NR-DC shall support synchronous NR-DC configuration where all serving cells of the MCG are in FR1 and all serving cells of the SCG are in FR2. | BC | No | N/A | N/A | +| featureSetCombination
Indicates the feature set that the UE supports on the NR and/or MR-DC band combination by FeatureSetCombinationId. | BC | N/A | N/A | N/A | +| featureSetCombinationDAPS-r16
Indicates the feature set that the UE supports for DAPS handover on the NR band combination by FeatureSetCombinationId. A UE shall include this field if intra-frequency or inter-frequency DAPS handover is supported for this band combination. For a band entry where it indicates the support for intra-frequency DAPS handover, the UE shall include at least two CCs and shall support intra-frequency DAPS handover between any CC pair within the same band entry. If the number of CCs within a band combination is more than one and if inter-frequency DAPS handover is supported, UE shall support inter-frequency DAPS handover between every CC pair in the same or different band entries in the band combination, except for the CC pair within a band entry with bandwidth class A. A feature set including intraFreqDAPS-r16 can only be referred to by featureSetCombinationDAPS-r16 , not by featureSetCombination . A feature set without intraFreqDAPS-r16 is only applied to inter-freq DAPS handover if it is referred to by featureSetCombinationDAPS . Both feature sets with and without intraFreqDAPS-r16 can be referred to by the same featureSetCombinationDAPS-r16 . | BC | N/A | N/A | N/A | +| intraBandConcurrentOperationPowerClass-r16
Indicates the power class, of a particular Uu band combination and the intra-band PC5 band combination(s) on which the UE supports transmission of PC5 simultaneous with Uu uplink (as indicated by supportedTxBandCombListPerBC-Sidelink-r16 ). The leading/leftmost value corresponds to the band combination of the particular Uu band combination and the first intra-band PC5 band combination included in BandCombinationListSidelinkEUTRA-NR which is indicated with value 1 by supportedTxBandCombListPerBC-Sidelink-r16 , the next value corresponds to the band combination of the particular Uu band combination and the second intra-band PC5 band combination included in BandCombinationListSidelinkEUTRA-NR which is indicated with value 1 by supportedTxBandCombListPerBC-Sidelink-r16 and so on. If this power class is higher than the power class that the UE supports on the individual Uu or PC5 interface of this band combination, the latter determines maximum TX power available in each interface. | BC | No | N/A | N/A | +| mrdc-Parameters
Contains the band combination parameters for a given (NG)EN-DC/NE-DC band combination. | BC | No | N/A | N/A | +| ne-DC-BC
Indicates whether the UE supports NE-DC for the band combination. | BC | No | N/A | N/A | +| powerClass, powerClass-v1610
Indicates power class the UE supports when operating according to this band combination. If the field is absent, the UE supports the default power class. If this power class is higher than the power class that the UE supports on the individual bands of this band combination ( ue-PowerClass in BandNR ), the latter determines maximum TX power available in each band. The UE sets the power class parameter only in band combinations that are applicable as specified in TS 38.101-1 [2] and TS 38.101-3 [4]. This capability is not applicable to IAB-MT. | BC | No | N/A | FR1 only | +| powerClassNRPart-r16
Indicates NR part power class the UE supports when operating according to this band combination.
This field only applies for MR-DC BCs containing only single CC or intra-band CA in NR side in this release. | BC | No | N/A | FR1 only | + +| | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|-----| +|

scalingFactorTxSidelink-r16, scalingFactorRxSidelink-r16
Indicates, for a particular Uu band combination, the scaling factor for the PC5 band combination(s) on which the UE supports transmission/reception of PC5 simultaneous with Uu uplink/downlink respectively (as indicated by supportedTxBandCombListPerBC-Sidelink-r16 / supportedRxBandCombListPerBC-Sidelink-r16). The leading / leftmost value corresponds to the first band combination included in BandCombinationListSidelinkEUTRA-NR which is indicated with value 1 by supportedTxBandCombListPerBC-Sidelink-r16 / supportedRxBandCombListPerBC-Sidelink-r16, the next value corresponds to the second band combination included in BandCombinationListSidelinkEUTRA-NR which is indicated with value 1 by supportedTxBandCombListPerBC-Sidelink-r16 / supportedRxBandCombListPerBC-Sidelink-r16 and so on. For each value of ScalingFactorSidelink-r16, value f0p4 indicates the scaling factor 0.4, f0p75 indicates 0.75, and so on.

| BC | No | N/A | N/A | +|

srs-SwitchingAffectedBandsListNR-r17
Indicates which other bands in the band combination are affected by the SRS switch and the dropping rules / timelines apply to the indicated bands when SRS carrier switching on target CC and other UL on source CC are overlapped in the same symbol. UE indicating support of this feature shall indicate support of srs-CarrierSwitch.

NOTE: For each "source-target" pair (as indicated by srs-SwitchingTimesListNR), the UE can indicate which other bands in the band combination are affected by the SRS switch.

| BC | No | N/A | N/A | +|

SRS-SwitchingTimeNR
Indicates the interruption time on DL/UL reception within a NR band pair during the RF retuning for switching between a carrier on one band and another (PUSCH-less) carrier on the other band to transmit SRS. switchingTimeDL / switchingTimeUL: n0us represents 0 us, n30us represents 30us, and so on. switchingTimeDL / switchingTimeUL is mandatory present if switching between the NR band pair is supported, otherwise the field is absent. It is signalled per pair of bands per band combination.

| FD | No | N/A | N/A | +|

SRS-SwitchingTimeEUTRA
Indicates the interruption time on DL/UL reception within a EUTRA band pair during the RF retuning for switching between a carrier on one band and another (PUSCH-less) carrier on the other band to transmit SRS. switchingTimeDL / switchingTimeUL: n0 represents 0 OFDM symbols, n0dot5 represents 0.5 OFDM symbols, n1 represents 1 OFDM symbol and so on. switchingTimeDL / switchingTimeUL is mandatory present if switching between the EUTRA band pair is supported, otherwise the field is absent. It is signalled per pair of bands per band combination.

| FD | No | N/A | N/A | + +|

srs-TxSwitch, srs-TxSwitch-v1610

Defines whether UE supports SRS for DL CSI acquisition as defined in clause 6.2.1.2 of TS 38.214 [12]. The capability signalling comprises of the following parameters:

  • - supportedSRS-TxPortSwitch indicates SRS Tx port switching pattern supported by the UE, which is mandatory with capability signalling. The indicated UE antenna switching capability of 'xTyR' corresponds to a UE, capable of SRS transmission on 'x' antenna ports over total of 'y' antennas, where 'y' corresponds to all or subset of UE receive antennas, where 2T4R is two pairs of antennas. supportedSRS-TxPortSwitch-v1610, which is optional to report, indicates downgrading configuration of SRS Tx port switching pattern. If the UE indicates the support of downgrading configuration of SRS Tx port switching pattern using supportedSRS-TxPortSwitch-v1610, the UE shall report the values for this as below, based on what is reported in supportedSRS-TxPortSwitch.
supportedSRS-TxPortSwitch supportedSRS-TxPortSwitch-v1610
t1r2 t1r1-t1r2
t1r4 t1r1-t1r2-t1r4
t2r4 t1r1-t1r2-t2r2-t2r4
t2r2 t1r1-t2r2
t4r4 t1r1-t2r2-t4r4
t1r4-t2r4 t1r1-t1r2-t2r2-t1r4-t2r4
  • - txSwitchImpactToRx indicates the lowest band entry number of the UL group (see txSwitchWithAnotherBand) that impacts the DL of this band entry;
  • - txSwitchWithAnotherBand indicates the lowest band entry of the UL group, which is defined as band entries with UL (see NOTE) that impact each other's UL (i.e. SRS TX port switching on any of the cells in the group will impact UL on all the cells in the group). This parameter is absent if an UL group contains only one band entry.

For txSwitchImpactToRx and txSwitchWithAnotherBand, value 1 means first entry, value 2 means second entry and so on. The UE may include txSwitchImpactToRx and txSwitchWithAnotherBand for a band entry even if supportedSRS-TxPortSwitch is set to 'notSupported' for that band entry. All DL and UL that switch together indicate the same entry number.

The entry number is the band entry number in a band combination. The UE is restricted not to include fallback band combinations for the purpose of indicating different SRS antenna switching capabilities.

NOTE: The band with UL includes a band associated with FeatureSetUplinkId set to 0 corresponding to the support of SRS-SwitchingTimeNR.

| supportedSRS-TxPortSwitch | supportedSRS-TxPortSwitch-v1610 | t1r2 | t1r1-t1r2 | t1r4 | t1r1-t1r2-t1r4 | t2r4 | t1r1-t1r2-t2r2-t2r4 | t2r2 | t1r1-t2r2 | t4r4 | t1r1-t2r2-t4r4 | t1r4-t2r4 | t1r1-t1r2-t2r2-t1r4-t2r4 | BC | FD | N/A | N/A | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|----------------------------------------|------|-----------|------|----------------|------|---------------------|------|-----------|------|----------------|-----------|--------------------------|----|----|-----|-----| +| supportedSRS-TxPortSwitch | supportedSRS-TxPortSwitch-v1610 | | | | | | | | | | | | | | | | | | +| t1r2 | t1r1-t1r2 | | | | | | | | | | | | | | | | | | +| t1r4 | t1r1-t1r2-t1r4 | | | | | | | | | | | | | | | | | | +| t2r4 | t1r1-t1r2-t2r2-t2r4 | | | | | | | | | | | | | | | | | | +| t2r2 | t1r1-t2r2 | | | | | | | | | | | | | | | | | | +| t4r4 | t1r1-t2r2-t4r4 | | | | | | | | | | | | | | | | | | +| t1r4-t2r4 | t1r1-t1r2-t2r2-t1r4-t2r4 | | | | | | | | | | | | | | | | | | +|

srs-AntennaSwitchingBeyond4RX-r17

Indicates whether the UE supports SRS Antenna switching for more than 4 Rx. The capability signalling comprises the following parameters:

  • - supportedSRS-TxPortSwitchBeyond4Rx-r17 indicates a combination of supported xTyRs. It includes 11-bit bitmap, where starting from the leading / leftmost bit (bit 0), each bit corresponds to {t1r1, t2r2, t1r2, t4r4, t2r4, t1r4, t2r6, t1r6, t4r8, t2r8, t1r8}. For any indicated value, x shall be equal to or smaller than the one associated with the largest y.
  • - entryNumberAffectBeyond4Rx-r17 indicates the entry number of the first-listed band with UL in the band combination that affects this DL.
  • - entryNumberSwitchBeyond4Rx-r17 indicates the entry number of the first-listed band with UL in the band combination that switches together with this UL.

The UE indicating support of this shall indicate support of srs-TxSwitch.

NOTE: If reported for the same values of xTyR in supportedSRS-TxPortSwitchBeyond4Rx-r17 as reported with supportedSRS-TxPortSwitch/supportedSRS-TxPortSwitch-v1610, the reported values for entryNumberAffectBeyond4Rx-r17 and entryNumberSwitchBeyond4Rx-r17 are not valid.

| BC | No | N/A | N/A | | | | | | | | | | | | | | | + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|-----| +|

supportedBandwidthCombinationSet

Defines the supported bandwidth combination set for a band combination as defined in TS 38.101-1 [2], TS 38.101-2 [3] and TS 38.101-3 [4]. For NR SA CA, NR-DC, inter-band (NG)EN-DC without intra-band (NG)EN-DC component, inter-band NE-DC without intra-band NE-DC component and intra-band (NG)EN-DC/NE-DC with additional inter-band NR CA component, the field defines the bandwidth combinations for the NR part of the band combination. For intra-band (NG)EN-DC/NE-DC without additional inter-band NR and LTE CA component, the field indicates the supported bandwidth combination set applicable to intra-band (NG)EN-DC/NE-DC band combination. This field is not applicable to source and target cells in intra-frequency DAPS handover.

Field encoded as a bit map, where bit N is set to "1" if UE supports Bandwidth Combination Set N for this band combination as defined in the TS 38.101-1 [2], TS 38.101-2 [3] and TS 38.101-3 [4]. The leading / leftmost bit (bit 0) corresponds to the Bandwidth Combination Set 0, the next bit corresponds to the Bandwidth Combination Set 1 and so on. It is mandatory if

  • - the band combination has more than one NR carrier (at least one SCell in an NR cell group);
  • - or is an intra-band (NG)EN-DC/NE-DC combination without additional inter-band NR and LTE CA component;
  • - or both.

The corresponding bits of Bandwidth Combination Set 4 and Bandwidth Combination Set 5 shall not both be set to "1" for the same band combination.

| BC | CY | N/A | N/A | +|

supportedBandwidthCombinationSetIntraENDC

Defines the supported bandwidth combination set for a band combination that allows configuration of at least one EUTRA serving cell and at least one NR serving cell in the same band, as defined in the TS 38.101-3 [4], table 5.3B.1.2-1 and table 5.3B.1.3-1.

  • - For intra-band (NG)EN-DC with additional inter-band CA component(s) of LTE and/or NR, the field defines the bandwidth combinations for the intra-band (NG)EN-DC component.
  • - For intra-band NE-DC with additional inter-band CA component(s) of LTE and/or NR, the field defines the bandwidth combinations for the intra-band NE-DC component.

Field encoded as a bit map, where bit N is set to "1" if UE support Bandwidth Combination Set N for this band combination as defined in the TS 38.101-3 [4]. The leading / leftmost bit (bit 0) corresponds to the Bandwidth Combination Set 0, the next bit corresponds to the Bandwidth Combination Set 1 and so on.

  • - It is mandatory if the band combination is an intra-band (NG)EN-DC/NE-DC combination supporting both UL and DL intra-band (NG)EN-DC/NE-DC parts with additional inter-band NR/LTE CA component.
  • - It is optional if the band combination is an intra-band (NG)EN-DC/NE-DC combination without supporting UL in both the bands of the intra-band (NG)EN-DC/NE-DC UL part. If not included, the network assumes the UE supports BCS0 as defined in TS 38.101-3 [4], table 5.3B.1.2-1 and table 5.3B.1.3-1 for the intra-band (NG)EN-DC/NE-DC.
| BC | CY | N/A | N/A | +|

supportedTxBandCombListPerBC-Sidelink-r16, supportedRxBandCombListPerBC-Sidelink-r16

Indicates, for a particular Uu band combination, the PC5 band combination(s) on which the UE supports transmission/reception of PC5 simultaneously with Uu uplink/downlink respectively. The leading / leftmost bit (bit 0) corresponds to the first band combination included in BandCombinationListSidelinkEUTRA-NR, the next bit corresponds to the second band combination included in BandCombinationListSidelinkEUTRA-NR and so on. with value 1 indicating simultaneous transmission/reception is supported.

| BC | No | N/A | N/A | + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|----------| +|

supportedBandCombListPerBC-SL-RelayDiscovery-r17,
supportedBandCombListPerBC-SL-NonRelayDiscovery-r17
Indicates, for a particular Uu band combination, the PC5 Relay discovery and non-Relay discovery band combination(s) on which the UE supports simultaneous transmission/reception of PC5 data (Relay discovery or non-Relay discovery) and Uu uplink/downlink respectively.
The leading / leftmost bit (bit 0) corresponds to the first band combination included in supportedBandCombinationListSL-RelayDiscovery-r17/supportedBandCombinationListSL-NonRelayDiscovery-r17, the next bit corresponds to the second band combination included in supportedBandCombinationListSL-RelayDiscovery-r17/supportedBandCombinationListSL-NonRelayDiscovery-r17 and so on. with value 1 indicating simultaneous transmission/reception is supported.

| BC | No | N/A | N/A | +|

supportedBandCombListPerBC-SL-U2U-RelayDiscovery-r18
Indicates, for a particular Uu band combination, the PC5 U2U relay discovery band combination(s) on which the UE supports simultaneous transmission/reception of PC5 data (U2U relay discovery) and Uu uplink/downlink respectively.
The leading / leftmost bit (bit 0) corresponds to the first band combination included in supportedBandCombinationListSL-U2U-RelayDiscovery-r18, the next bit corresponds to the second band combination included in supportedBandCombinationListSL-U2U-RelayDiscovery-r18 and so on with value 1 indicating simultaneous transmission/reception is supported.

| BC | No | N/A | N/A | +|

ULTxSwitchingBandPair-r16, ULTxSwitchingBandPair-v1700
Indicates UE supports dynamic UL 1Tx-2Tx switching in case of inter-band CA, SUL, and (NG)EN-DC, and UL 2Tx-2Tx switching in case of inter-band CA and SUL as defined in TS 38.214 [12], TS 38.101-1 [2] and TS 38.101-3 [4]. The capability signalling comprises of the following parameters:

  • - bandIndexUL1-r16 and bandIndexUL2-r16 indicate the band pair on which UE supports dynamic UL Tx switching. bandindexUL1/bandindexUL2 xx refers to the xxth band entry in the band combination. UE shall indicate support for 2-layer UL MIMO capabilities on one of the indicated two bands in each FeatureSet entry supporting UL 1Tx-2Tx switching and indicate support for 2-layer UL MIMO capabilities on both bands in each FeatureSet entry supporting UL 2T-2Tx switching, and only the band where UE supports 2-layer UL MIMO capability can work as carrier2 as defined in TS 38.101-1 [2] and TS 38.101-3 [4].
  • - uplinkTxSwitchingPeriod-r16 indicates the length of UL Tx switching period of 1Tx-2Tx switching per pair of UL bands per band combination when dynamic UL Tx switching is configured, as specified in TS 38.101-1 [2] and TS 38.101-3 [4]. UE shall not report the value n210us for EN-DC band combinations. n35us represents 35 us, n140us represents 140us, and so on, as specified in TS 38.101-1 [2] and TS 38.101-3 [4].
  • - uplinkTxSwitchingPeriod2T2T-r17 indicates the length of UL Tx switching period of 2Tx-2Tx switching per pair of UL bands per band combination when dynamic UL Tx switching is configured, as specified in TS 38.101-1 [2] and TS 38.101-3 [4]. n35us represents 35 us, n140us represents 140us, and so on, as specified in TS 38.101-1 [2] and TS 38.101-3 [4].
  • - uplinkTxSwitching-DL-Interruption-r16 indicates that DL interruption on the band will occur during UL Tx switching, as specified in TS 38.133 [5] and in TS 36.133 [27]. UE is not allowed to set this field for the band combination of SUL band+TDD band, for which no DL interruption is allowed.

Field encoded as a bit map, where bit N is set to "1" if DL interruption on band N will occur during uplink Tx switching as specified in TS 38.133 [5] and in TS 36.133 [27]. The leading / leftmost bit (bit 0) corresponds to the first band of this band combination, the next bit corresponds to the second band of this band combination and so on. The capability is not applicable to the following band combinations, in which DL reception interruption is not allowed:

  • - TDD+TDD CA with the same UL-DL pattern
  • - TDD+TDD EN-DC with the same UL-DL pattern
| BC | FD | N/A | FR1 only | +|

uplinkTxSwitching-OptionSupport-r16
Indicates which option is supported for dynamic UL 1Tx-2Tx switching for inter-band UL CA and (NG)EN-DC. switchedUL represents option 1 as specified in TS 38.214 [12], dualUL represents option 2 as specified in TS 38.214 [12], both represents both option 1 and option2 as specified in TS 38.214 [12]. UE shall not report the value both for (NG)EN-DC case. The field is mandatory for inter-band UL CA and (NG)EN-DC case where UE supports dynamic UL 1Tx-2Tx switching.

| BC | CY | N/A | FR1 only | + +| | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|----------| +|

uplinkTxSwitching-OptionSupport2T2T-r17
Indicates which option is supported for dynamic UL 2Tx-2Tx switching for inter-band UL CA. switchedUL represents option 1 as specified in TS 38.214 [12], dualUL represents option 2 as specified in TS 38.214 [12], both represents both option 1 and option 2 as specified in TS 38.214 [12]. The field is mandatory for inter-band UL CA cases where UE supports dynamic UL 2Tx-2Tx switching. The UE indicating support of this feature shall indicate support of at least one common switching option between uplinkTxSwitching-OptionSupport2T2T-r17 and uplinkTxSwitching-OptionSupport-r16.

| BC | CY | N/A | FR1 only | +|

uplinkTxSwitching-PowerBoosting-r16
Indicates the support of 3dB boosting on the maximum output power for UE transmission under the operation state in which 2-port transmission can be supported on carrier2 in case of inter-band UL CA case where UE supports dynamic UL Tx switching. A UE shall only indicate this capability in case the UE supports power class 3 for inter-band UL CA for the band combination as defined in TS 38.101-1 [2].

| BC | No | N/A | FR1 only | +|

UplinkTxSwitchingAdditionalPeriodDualUL-r18
Indicates the UL Tx switching period for switching between a band pair and another band pair or another band, when Rel-18 UL Tx switching is configured by uplinkTxSwitchingMoreBands-r18. If the capability is not reported, the switching period reported in switchingPeriodFor2T-r18 or switchingPeriodFor1T-r18 applies, as specified in TS 38.214 [12] and TS 38.101-1 [2].

  • - bandPairIndex1-r18/bandPairIndex2-r18 xx refers to the xxth band pair entry in the band pair list indicated by ULTxSwitchingBandPair-r18. The two band pairs consist of mutually exclusive bands.
  • - bandIndex-r18 xx refers to the xxth band entry in this band combination, which indicates a different band from those indicated by bandPairIndex1-r18.
  • - switchingAdditionalPeriodDualUL-r18 indicates the length of switching period for switching between one band pair indicated by bandPairIndex1-r18 and another band pair indicated by bandPairIndex2-r18 or another band indicated by bandIndex-r18.
  • - n35us represents 35 us, n140us represents 140us, and so on, as specified in TS 38.101-1 [2].

A UE supporting this feature shall also indicate the support of dualUL switching option for the band pair(s) indicated in bandPairIndex1-r18/bandPairIndex2-r18.

| BC | No | N/A | FR1 only | + +| ULTxSwitchingBandPair-r18 | BC | FD | N/A | FR1 only | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|----------| +|

Indicates UE supports R18 dynamic UL Tx switching across up to 4 bands in case of inter-band CA, SUL as defined in TS 38.214 [12] and TS 38.101-1 [2]. The capability signalling comprises of the following parameters:

  • - bandIndexUL1-r18 and bandIndexUL2-r18 indicate the band pair on which UE supports dynamic UL Tx switching. bandindexUL1bandindexUL2 xx refers to the xxth UL band entry in the band combination. UE shall indicate support of 2-layer UL MIMO in FeatureSet on both bands for 2Tx-2Tx switching, or indicate support of 2-layer UL MIMO on one band and 1-layer MIMO on the other band for 1Tx-2Tx switching, or indicate support of 1-layer UL MIMO on both bands for 1Tx-1Tx switching.
  • - uplinkTxSwitchingOptionForBandPair-r18 indicates whether switchedUL or dualUL or both switching options is supported for a given band pair as specified in TS 38.214 [12].
  • - switchingPeriodFor2T-r18 indicates the length of 2Tx-2Tx switching period. switchingPeriodFor1T-r18 indicates the length of 1Tx-2Tx switching and/or 1Tx-1Tx switching period, as specified in TS 38.101-1 [2]. n35us represents 35 us, n140us represents 140us, and so on, as specified in TS 38.101-1 [2].
  • - uplinkTxSwitching-DL-Interruption-r18 indicates that DL interruption on the band will occur during UL Tx switching, as specified in TS 38.133 [5]. UE is not allowed to set this field for the band combination of SUL band+TDD band, for which no DL interruption is allowed.
    Field encoded as a bit map, where bit N is set to "1" if DL interruption on band N will occur during uplink Tx switching as specified in TS 38.133 [5]. The leading / leftmost bit (bit 0) corresponds to the first band of this band combination, the next bit corresponds to the second band of this band combination and so on. The capability is not applicable to the following band combinations, in which DL reception interruption is not allowed:
    • - TDD+TDD CA with the same UL-DL pattern
  • - SwitchingPeriodUnaffectedBandDualUL-r18 indicates for a given band pair {band X and band Y}, whether/how the switching period is to be applied on band Z (as well as band X and Y), when a UL Tx switching is triggered from band pair {band X and band Z} to band pair {band Y and band Z}, as defined in 38.101-1 [2]. If absent for band Z, the UE is not required to transmit on any UL bands during the switching period reported for the band pair of band X and band Y, as defined in 38.101-1 [2].
    • - bandIndexUnaffected-r18 xx indicates the band index of band Z and refers to the xxth UL band entry in the band combination.
    • - maintainedUL-Trans-r18 indicates that the UE is capable of uplink transmission on band Z and is not required to transmit on band X and Y during the switching period reported for the band pair of band X and band Y, as specified in 38.101-1 [2].
  • - periodOnULBands-r18 indicates the switching period to be applied on any UL bands as specified in 38.101-1 [2]. n35us represents 35 us, n140us represents 140us, and so on.
| | | | | + +| | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|----------| +|

UplinkTxSwitchingBandParameters-v1700
Contains the UL Tx switching specific band parameters for a given band combination.
The capability signalling comprises of the following parameters:

  • - bandIndex-r17 indicates a band on which UE supports dynamic UL Tx switching with another band in the band combination. bandIndex xx refers to the xxth band entry in the band combination.
  • - uplinkTxSwitching2T2T-PUSCH-TransCoherence-r17 indicates support of the uplink codebook subset for the carrier(s) on a band capable of two antenna connectors on which UE supports dynamic UL 2Tx-2Tx switching with another band in the band combination. UE indicating support of full coherent codebook subset shall also support non-coherent codebook subset. If this field is absent,
    • - When 2Tx-2Tx switching between two bands is configured by uplinkTxSwitching-2T-Mode-r17, the per BC UE capability reported in uplinkTxSwitching-PUSCH-TransCoherence-r16 is applied, and if this field and uplinkTxSwitching-PUSCH-TransCoherence-r16 are both absent, the UE capability reported in pusch-TransCoherence is applied when uplink Tx switching is triggered between last transmitted SRS and scheduled PUSCH transmission, as specified in TS 38.101-1 [2].
    • - When R18 dynamic UL Tx switching is configured by uplinkTxSwitchingMoreBands-r18, the UE capability reported in pusch-TransCoherence is applied when uplink Tx switching is triggered between last transmitted SRS and scheduled PUSCH transmission, as specified in TS 38.101-1 [2].

NOTE: If UplinkTxSwitchingBandParameters-v1700 is absent for one or more bands of a band combination, the per BC UE capability reported in uplinkTxSwitching-PUSCH-TransCoherence-r16 is applied for corresponding band(s), and if uplinkTxSwitching-PUSCH-TransCoherence-r16 is also absent, the UE capability reported in pusch-TransCoherence is applied for corresponding band(s) when uplink Tx switching is triggered between last transmitted SRS and scheduled PUSCH transmission, as specified in TS 38.101-1 [2].

| BC | No | N/A | FR1 only | +|

uplinkTxSwitchingMinimumSeparationTime-r18
Indicates the minimum separation time for two uplink switching on more than 2 bands within any two consecutive reference slots as specified in TS 38.214 [12]. The field is mandatory when UE supports dynamic UL Tx switching across more than two bands.

| BC | CY | N/A | FR1 only | +|

uplinkTxSwitching-PUSCH-TransCoherence-r16
Indicates support of the uplink codebook subset when uplink 1Tx-2Tx switching is triggered between last transmitted SRS and scheduled PUSCH transmission, as specified in TS 38.101-1 [2].
UE indicating support of full coherent codebook subset shall also support non-coherent codebook subset.
If the field is absent, the supported uplink codebook subset indicated by pusch-TransCoherence applies when the uplink switching is triggered between last transmitted SRS and scheduled transmission.

| BC | No | N/A | FR1 only | + +#### 4.2.7.2 *BandNR parameters* + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| activeConfiguredGrant-r16
Indicates whether the UE supports up to 12 configured/active configured grant configurations in a BWP of a serving cell. This field includes the following parameters:
  • - maxNumberConfigsPerBWP-r16 indicates the maximum number of configured/active configured grant configurations in a BWP of a serving cell.
  • - maxNumberConfigsAllCC-r16 indicates the maximum number of configured/active configured grant configurations across all serving cells in a MAC entity, and across MCG and SCG in case of NR-DC.
The UE can include this feature only if the UE indicates support of either configuredUL-GrantType1 or configuredUL-GrantType1-v1650 and/or configuredUL-GrantType2 or configuredUL-GrantType2-v1650 .

NOTE:
  • - For all the reported bands in FR1, a same X1 value is reported for maxNumberConfigsAllCC-r16. For all the reported bands in FR2, a same X2 value is reported for maxNumberConfigsAllCC-r16.
  • - The total number of configured/active configured grant configurations across all serving cells in FR1 is no greater than X1.
  • - The total number of configured/active configured grant configurations across all serving cells in FR2 is no greater than X2.
  • - If the CA have some serving cell(s) in FR1 and some serving cell(s) in FR2, the total number of configured/active configured grant configurations across all serving cells is no greater than max(X1, X2).
| Band | No | N/A | N/A | +| additionalActiveTCI-StatePDCCH
Indicates whether the UE supports one additional active TCI-State for control in addition to the supported number of active TCI-States for PDSCH. The UE can include this field only if maxNumberActiveTCI-PerBWP in tc-StatePDSCH is set to n1 . Otherwise, the UE does not include this field. | Band | No | N/A | N/A | +| antennaArrayType-r18
Indicates whether the UE supports the RF and RRM requirements with antenna array as specified in TS 38.101-1 [2] clause 6.1J, 7.1J and TS 38.133 [5]. If the field is absent, the RF and RRM requirements with omni-directional antenna applies as specified in TS 38.101-1 [2] clause 6.1J, 7.1J and TS 38.133 [5]. The UE indicating support of this feature shall also indicate support of airToGroundNetwork-r18 . This field is only applicable for bands as specified for ATG in clause 5.2J of TS 38.101-1 [2]. | Band | CY | N/A | FR1 only | +| aperiodicBeamReport
Indicates whether the UE supports aperiodic 'CRI/RSRP' or 'SSBRI/RSRP' reporting on PUSCH. The UE provides the capability for the band number for which the report is provided (where the measurement is performed). | Band | Yes | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| aperiodicCSI-RS-AdditionalBandwidth-r17
Indicates the UE supported TRS bandwidths for fast SCell activation, in addition to 52 RBs, for a 10MHz UE channel bandwidth. This field only applies for the BWPs configured with 52 RBs size and 15kHz SCS, in FDD bands and indicates the values:
Value addBW-Set1 indicates 28, 32, 36, 40, 44, 48 RBs.
Value addBW-Set2 indicates 32, 36, 40, 44, 48 RBs.

The UE can include this feature only if the UE indicates support of aperiodicCSI-RS-FastSCellActivation-r17 . | Band | No | FDD only | FR1 only | +| aperiodicCSI-RS-FastSCellActivation-r17
Indicates whether the UE supports aperiodic CSI-RS for tracking for fast SCell activation, i.e.,
1) Aperiodic CSI-RS for tracking for fast SCell activation is triggered by enhanced SCell activation/deactivation MAC CE;
2) Aperiodic CSI-RS for tracking for fast SCell activation is triggered within the BWP indicated by firstActiveDownlinkBWP-Id for the SCell.

This field includes the following parameters:
- maxNumberAperiodicCSI-RS-PerCC-r17 indicates the maximum number of aperiodic CSI-RS resource set configurations for tracking for fast SCell activation that can be configured to UE per CC in a reported band. Value n8 corresponds to 8, n16 corresponds to 16, and so on.
- maxNumberAperiodicCSI-RS-AcrossCCs-r17 indicates the maximum number of aperiodic CSI-RS resource set configurations for tracking for fast SCell activation that can be configured to UE across CCs in a reported band. Value n8 corresponds to 8, n16 corresponds to 16, and so on.

NOTE:
- maxNumberAperiodicCSI-RS-PerCC-r17 and maxNumberAperiodicCSI-RS-AcrossCCs-r17 values refer to the number of RS configurations for fast SCell activation that can be indicated by the MAC CE.
- The NZP-CSI-RS configured as RS for tracking for fast SCell activation are not considered when counting the maximum NZP-CSI-RS configurations of CSI-RS and CSI-IM reception for CSI feedback. | Band | No | N/A | N/A | +| aperiodicTRS
Indicates whether the UE supports DCI triggering aperiodic TRS associated with periodic TRS. | Band | No | N/A | Yes | +| asymmetricBandwidthCombinationSet
Defines the supported asymmetric channel bandwidth combination for the band as defined in the TS 38.101-1 [2]. Field encoded as a bit map, where bit N is set to "1" if UE support asymmetric channel bandwidth combination set N for this band as defined in the TS 38.101-1 [2]. The leading / leftmost bit (bit 0) corresponds to the asymmetric channel bandwidth combination set 1, the next bit corresponds to the asymmetric channel bandwidth combination set 2 and so on. UE shall support asymmetric channel bandwidth combination set 0. If the field is absent, the UE supports asymmetric channel bandwidth combination set 0. | Band | No | N/A | N/A | +| bandNR
Defines supported NR frequency band by NR frequency band number, as specified in TS 38.101-1 [2], TS 38.101-2 [3], and TS 38.101-5 [34]. | Band | Yes | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| beamCorrespondenceCSI-RS-based-r16
Indicates whether the UE support for beam correspondence based on CSI-RS has the ability to select its uplink beam based on measurement of CSI-RS. If a UE supports beam correspondence based on CSI-RS, then the network can expect the UE to also fulfil Rel-15 beam correspondence requirements.

If UE supports neither beamCorrespondenceSSB-based-r16 nor beamCorrespondenceCSI-RS-based-r16 , gNB can expect the UE to fulfil beam correspondence based on Rel-15 beam correspondence requirements. | Band | No | TDD only | FR2 only | +| beamCorrespondenceSSB-based-r16
Indicates whether the UE support for beam correspondence based on SSB has the ability to select its uplink beam based on measurement of SSB. If a UE supports beam correspondence based on SSB, then the network can expect the UE to also fulfil Rel-15 beam correspondence requirements.

If UE supports neither beamCorrespondenceSSB-based-r16 nor beamCorrespondenceCSI-RS-based-r16 , gNB can expect the UE to fulfil beam correspondence based on Rel-15 beam correspondence requirements. | Band | No | TDD only | FR2 only | +| beamCorrespondenceWithoutUL-BeamSweeping
Indicates how UE supports FR2 beam correspondence as specified in TS 38.101-2 [3], clause 6.6. The UE that fulfils the beam correspondence requirement without the uplink beam sweeping (as specified in TS 38.101-2 [3], clause 6.6) shall set the field to supported . The UE that fulfils the beam correspondence requirement with the uplink beam sweeping (as specified in TS 38.101-2 [3], clause 6.6) shall not report this field. | Band | Yes | N/A | FR2 only | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| beamManagementSSB-CSI-RS
Defines support of SS/PBCH and CSI-RS based RSRP measurements. The capability comprises signalling of
  • - maxNumberSSB-CSI-RS-ResourceOneTx indicates maximum total number of configured one port NZP CSI-RS resources and SS/PBCH blocks that are supported by the UE to measure L1-RSRP as specified in TS 38.215 [13] within a slot and across all serving cells (see NOTE). On FR2, it is mandatory to report \geq 8; On FR1, it is mandatory with capability signalling to report \geq 8.
  • - maxNumberCSI-RS-Resource indicates maximum total number of configured NZP-CSI-RS resources that are supported by the UE to measure L1-RSRP as specified in TS 38.215 [13] across all serving cells (see NOTE). It is mandated to report at least n8 for FR1.
  • - maxNumberCSI-RS-ResourceTwoTx indicates maximum total number of two ports NZP CSI-RS resources that are supported by the UE to measure L1-RSRP as specified in TS 38.215 [13] within a slot and across all serving cells (see NOTE).
  • - supportedCSI-RS-Density indicates density of one RE per PRB for one port NZP CSI-RS resource for RSRP reporting, if supported. On FR2, it is mandatory to report either "three" or "oneAndThree"; On FR1, it is mandatory with capability signalling to report either "three" or "oneAndThree".
  • - maxNumberAperiodicCSI-RS-Resource indicates maximum number of configured aperiodic CSI-RS resources across all serving cells (see NOTE). For FR1 and FR2, the UE is mandated to report at least n4.
NOTE: If the UE sets a value other than n0 in an FR1 band, it shall set that same value in all FR1 bands. If the UE sets a value other than n0 in an FR2 band, it shall set that same value in all FR2 bands. The UE supports a total number of resources equal to the maximum of the FR1 and FR2 value, but no more than the FR1 value across all FR1 serving cells and no more than the FR2 value across all FR2 serving cells. | Band | Yes | N/A | FD | +| beamReportTiming, beamReportTiming-v1710
Indicates the number of OFDM symbols between the end of the last symbol of SSB/CSI-RS and the start of the first symbol of the transmission channel containing beam report. The UE provides the capability for the band number for which the report is provided (where the measurement is performed). The UE includes this field for each supported sub-carrier spacing. | Band | Yes | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| beamSweepingFactorReduction-r18
Indicates whether the UE supports beam sweeping factor reduction for FR2 unknown SCell activation.
The capability comprises signalling of
  • - reduceForCellDetection indicates reducing beam sweeping factor for cell detection if UE has full set (N=8) of beam sweeping during AGC settling part during FR2-1 unknown SCell activation procedure.
  • - reduceForSSB-L1-RSRP-Meas indicates reducing beam sweeping factor for SSB based L1-RSRP measurement if UE has full set (N=8) of beam sweeping during AGC settling part during FR2-1 unknown SCell activation procedure.
UE is required to meet the shortened SCell activation delay requirement in TS 38.133 [5] if the feature is supported. | Band | No | TDD only | FR2-1 only | +| beamSwitchTiming, beamSwitchTiming-v1710
Indicates the minimum number of OFDM symbols between the DCI triggering of aperiodic CSI-RS and aperiodic CSI-RS transmission. The number of OFDM symbols is measured from the end of the last symbol containing the indication to the start of the first symbol of CSI-RS. The UE includes this field for each supported sub-carrier spacing.
NOTE: beamSwitchTiming of value ( sym224 or sym336 for 60kHz and 120kHz SCS, sym896 or sym1344 for 480kHz SCS and sym1792 or sym2688 for 960kHz SCS) will be used to determine UE expectation/behaviour for aperiodic CSI-RS for tracking and latency requirements for L1-RSRP reporting as described in clause 5.1.6.1.1 of TS 38.214 [12], while UE behaviour/assumption regarding before or after beam switch timing is unspecified for measuring AP CSI-RS for CSI acquisition (without trs-Info and without repetition) and for beam management (with repetition 'off'). | Band | No | N/A | FR2 only | +| beamSwitchTiming-r16, beamSwitchTiming-r17
Indicates the minimum number of required OFDM symbols ( sym224 , sym336 for 60kHz and 120kHz SCS, sym896 or sym1344 for 480kHz SCS and sym1792 or sym2688 for 960kHz SCS) between the DCI triggering aperiodic CSI-RS and the corresponding aperiodic CSI-RS transmission in a CSI-RS resource set configured with repetition 'ON' if enableBeamSwitchTiming-r16 is configured.
For CSI-RS configured with repetition "off", the UE applies beam switch time of sym48 if beamSwitchTiming-r16 is reported and enableBeamSwitchTiming-r16 is configured. For CSI-RS configured without repetition and without trs-info , the UE applies beam switch time of sym48 if beamSwitchTiming-r16 is reported and enableBeamSwitchTiming-r16 is configured. | Band | No | N/A | FR2 only | +| bfd-Relaxation-r17
Indicates whether the UE supports BFD relaxation criteria and requirement as specified in TS 38.133 [5]. UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands, all TDD-FR2-1 bands and all TDD-FR2-2 bands respectively.

UE indicating support of this feature shall also indicate support of maxNumberCSI-RS-BFD , maxNumberSSB-BFD and maxNumberCSI-RS-SSB-CBD . | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| bwp-DiffNumerology
Indicates whether the UE supports BWP adaptation up to 4 BWPs with the different numerologies, via DCI and timer. Except for SUL, the UE only supports the same numerology for the active UL and DL BWP. For the UE that is capable of this feature but is not indicating supportOfRedCap-r17 nor supportOfERedCap-r18 , the bandwidth of a UE-specific RRC configured DL BWP includes the bandwidth of the CORESET#0 (if CORESET#0 is present) and SSB for PCell and PSCell (if configured). For the UE which is a (e)RedCap UE capable of this feature, the bandwidth of a UE-specific RRC configured DL BWP may not include the bandwidth of the CORESET#0 (if configured) and SSB for PCell. For SCell(s), the bandwidth of the UE-specific RRC configured DL BWP includes SSB, if there is SSB on SCell(s). | Band | No | N/A | N/A | +| bwp-SameNumerology
Indicates whether UE supports BWP adaptation (up to 2/4 BWPs) with the same numerology, via DCI and timer. Except for SUL, the UE only supports the same numerology for the active UL and DL BWP. For the UE that is capable of this feature but is not indicating supportOfRedCap-r17 nor supportOfERedCap-r18 , the bandwidth of a UE-specific RRC configured DL BWP includes the bandwidth of the CORESET#0 (if CORESET#0 is present) and SSB for PCell and PSCell (if configured). For the UE which is a (e)RedCap UE capable of this feature, the bandwidth of a UE-specific RRC configured DL BWP may not include the bandwidth of the CORESET#0 (if configured) and SSB for PCell. For SCell(s), the bandwidth of the UE-specific RRC configured DL BWP includes SSB, if there is SSB on SCell(s). | Band | No | N/A | N/A | +| bwp-WithoutRestriction
Indicates support of BWP operation without bandwidth restriction. The Bandwidth restriction in terms of DL BWP for PCell and PSCell means that the bandwidth of a UE-specific RRC configured DL BWP may not include the bandwidth of CORESET #0 (if configured) and SSB. For SCell(s), it means that the bandwidth of DL BWP may not include SSB. | Band | No | N/A | N/A | +| cancelOverlappingPUSCH-r16
Indicates whether UE supports the cancellation of the (repetition of the) PUSCHs transmission on all other intra-band serving cell(s). The cancellation of the (repetition of the) PUSCH transmission on a the set of intra-band serving cell(s) includes all symbols from the earliest symbol that is overlapping with the first cancelled symbol of the PUSCH on the serving cell for which the DCI format 2_4 is applicable to. If the UE supports this feature, the UE needs to report pa-PhaseDiscontinuityImpacts and ul-CancellationSelfCarrier-r16 . | Band | No | N/A | N/A | +| cg-PUSCH-UTO-UCI-Ind-r18
Indicates whether the UE supports multiplexing of the unused transmission occasions UCI (UTO-UCI) on a CG-PUSCH.
The UE indicating support of this feature shall also indicate support of at least one of configuredUL-GrantType1 , configuredUL-GrantType1-v1650 , configuredUL-GrantType2 , configuredUL-GrantType2-v1650 . | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| cg-SDT-r17
Indicates whether the UE supports transmission of data and/or signalling over allowed radio bearers in RRC_INACTIVE state via configured grant type 1 (i.e. CG-SDT), as specified in TS 38.331 [9]. Except for NTN bands, UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands and all TDD-FR2 bands respectively. For NTN, UE shall set the capability value consistently for all FDD-FR1 NTN bands.
UE supports multiple CG-SDT configurations when a UE indicates the support of this feature and activeConfiguredGrant-r16 ; otherwise UE only supports one CG-SDT configuration. | Band | No | N/A | N/A | +| cg-SDT-PeriodicityExt-r18
Indicates whether the UE supports to extend the range of CG-SDT periodicities for MO-SDT and/or MT-SDT, as specified in TS 38.331 [9].
A UE supporting this feature shall also indicate the support of ra-InsteadCG-SDT-r18 . A UE supporting this feature shall also indicate the support of cg-SDT-r17 or mt-CG-SDT-r18 . | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| channelBWs-DL
Indicates for each subcarrier spacing the UE supported channel bandwidths. Absence of the channelBWs-DL (without suffix) for a band or absence of specific scs-XXXkHz entry for a supported subcarrier spacing means that the UE supports the channel bandwidths among [5, 10, 15, 20, 25, 30, 40, 50, 60, 80, 100] and [50, 100, 200] that were defined in clause 5.3.5 of TS 38.101-1 version 15.7.0 [2] and TS 38.101-2 version 15.7.0 [3] for the given band or the specific SCS entry. For IAB-MT, to determine whether the IAB-MT supports a channel bandwidth of 100 MHz, the network checks channelBW-DL-IAB-r16 .
For FR1, the bits in channelBWs-DL (without suffix) starting from the leading / leftmost bit indicate 5, 10, 15, 20, 25, 30, 40, 50, 60 and 80MHz. For FR2, the bits in channelBWs-DL (without suffix) starting from the leading / leftmost bit indicate 50, 100 and 200MHz. The third / rightmost bit (for 200MHz) shall be set to 1. For IAB-MT the third / rightmost bit (for 200MHz) is ignored. To determine whether the IAB-MT supports a channel bandwidth of 200 MHz, the network checks channelBW-DL-IAB-r16 .
For FR1, the leading/leftmost bit in channelBWs-DL-v1590 indicates 70MHz, the second leftmost bit indicates 45MHz, the third leftmost bit indicates 35MHz, the fourth leftmost bit indicates 100MHz and all the remaining bits in channelBWs-DL-v1590 shall be set to 0. The fourth leftmost bit (for 100MHz) is not applicable for bands n41, n48, n77, n78, n79 and n90 as defined in TS 38.101-1 [2]. For each band, (e)RedCap UEs shall indicate supporting the maximum of those channel bandwidths that are less than or equal to 20 MHz for FR1 and less than or equal to 100 MHz for FR2, taking restrictions in TS 38.101-1 [2] and TS 38.101-2 [3] into consideration. For each band, NTN capable UEs shall indicate the supported channel bandwidths for FR1, taking restrictions in TS 38.101-5 [34] into consideration.

This feature is applicable only for FR1 and FR2-1 band, otherwise it is absent.

NOTE: To determine whether the UE supports a specific SCS for a given band, the network validates the supportedSubCarrierSpacingDL and the scs-60kHz .
To determine whether the UE supports a channel bandwidth of 90 MHz, the network may ignore this capability and validate instead the channelBW-90mhz , the supportedBandwidthCombinationSet and the supportedBandwidthCombinationSetIntraENDC . To determine whether the UE supports a channel bandwidth of 400 MHz, the network may ignore this capability and validate the supportedBandwidthCombinationSet , the supportedBandwidthCombinationSetIntraENDC , and the supportedBandwidthDL . For serving cell(s) with other channel bandwidths the network validates the channelBWs-DL , the supportedBandwidthCombinationSet , the supportedBandwidthCombinationSetIntraENDC , the asymmetricBandwidthCombinationSet (for a band supporting asymmetric channel bandwidth as defined in clause 5.3.6 of TS 38.101-1 [2]), supportedBandwidthDL/supportBandwidthDL-v1710 and supportedMinBandwidthDL . | Band | Yes | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| channelBWs-DL-SCS-120kHz-FR2-2-r17
Indicates the UE supported channel bandwidths in DL for the SCS 120kHz.
The bits in channelBWs-DL-SCS-120kHz-FR2-2 starting from the leading / leftmost bit indicate 100 and 400MHz.
100 and 400 MHz are mandatory channel bandwidths if the UE supports 120 kHz SCS (i.e. the bit for 100 and 400MHz shall always be set to 1).
UE supporting this feature shall also indicate support of dl-FR2-2-SCS-120kHz-r17 .

NOTE: To determine whether the UE supports a SCS 120kHz for a given band, the network validates the supportedSubCarrierSpacingDL .
To determine the supported carrier bandwidths, the network validates the channelBWs-DL-SCS-120kHz-FR2-2-r17 , the supportedBandwidthCombinationSet and the supportedBandwidthDL-v1710 . | Band | CY | N/A | N/A | +| channelBWs-DL-SCS-480kHz-FR2-2-r17
Indicates the UE supported channel bandwidths in DL for the SCS 480kHz.
The bits in channelBWs-DL-SCS-480kHz-FR2-2 starting from the leading / leftmost bit indicate 400, 800 and 1600MHz.
400 MHz is a mandatory channel bandwidth if the UE supports 480 kHz SCS (i.e. the bit for 400MHz shall always be set to 1).
UE supporting this feature shall also indicate support of dl-FR2-2-SCS-480kHz-r17 .

NOTE: To determine whether the UE supports a SCS 480kHz for a given band, the network validates the supportedSubCarrierSpacingDL .
To determine the supported carrier bandwidths, the network validates the channelBWs-DL-SCS-480kHz-FR2-2-r17 , the supportedBandwidthCombinationSet and supportedBandwidthDL-v1710 . | Band | CY | N/A | N/A | +| channelBWs-DL-SCS-960kHz-FR2-2-r17
Indicates the UE supported channel bandwidths in DL for the SCS 960kHz.
The bits in channelBWs-DL-SCS-960kHz-FR2-2 starting from the leading / leftmost bit indicate 400, 800, 1600 and 2000MHz.
400 MHz is a mandatory channel bandwidth if the UE supports 960 kHz SCS (i.e. the bit for 400MHz shall always be set to 1).
UE supporting this feature shall also indicate support of dl-FR2-2-SCS-960kHz-r17 .

NOTE: To determine whether the UE supports a SCS 960kHz for a given band, the network validates the supportedSubCarrierSpacingDL .
To determine the supported carrier bandwidths, the network validates the channelBWs-DL-SCS-960kHz-FR2-2-r17 , the supportedBandwidthCombinationSet and supportedBandwidthDL-v1710 . | Band | CY | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| channelBWs-UL
Indicates for each subcarrier spacing the UE supported channel bandwidths. Absence of the channelBWs-UL (without suffix) for a band or absence of specific scs-XXXkHz entry for a supported subcarrier spacing means that the UE supports the channel bandwidths among [5, 10, 15, 20, 25, 30, 40, 50, 60, 80, 100] and [50, 100, 200] that were defined in clause 5.3.5 of TS 38.101-1 version 15.7.0 [2] and TS 38.101-2 version 15.7.0 [3] for the given band or the specific SCS entry. For IAB-MT, to determine whether the IAB-MT supports a channel bandwidth of 100 MHz, the network checks channelBW-UL-IAB-r16 .
For FR1, the bits in channelBWs-UL (without suffix) starting from the leading / leftmost bit indicate 5, 10, 15, 20, 25, 30, 40, 50, 60 and 80MHz. For FR2, the bits in channelBWs-UL (without suffix) starting from the leading / leftmost bit indicate 50, 100 and 200MHz. The third / rightmost bit (for 200MHz) shall be set to 1. For IAB-MT the third / rightmost bit (for 200MHz) is ignored. To determine whether the IAB-MT supports a channel bandwidth of 200 MHz, the network checks channelBW-UL-IAB-r16 .
For FR1, the leading/leftmost bit in channelBWs-UL-v1590 indicates 70 MHz, the second leftmost bit indicates 45MHz, the third leftmost bit indicates 35MHz, the fourth leftmost bit indicates 100MHz and all the remaining bits in channelBWs-UL-v1590 shall be set to 0. The fourth leftmost bit (for 100MHz) is not applicable for bands n41, n48, n77, n78, n79 and n90 as defined in TS 38.101-1 [2]. For each band, (e)RedCap UEs shall indicate supporting the maximum of those channel bandwidths that are less than or equal to 20 MHz for FR1 and less than or equal to 100 MHz for FR2, taking restrictions in TS 38.101-1 [2] and TS 38.101-2 [3] into consideration. For each band, NTN capable UEs shall indicate the supported channel bandwidths for FR1, taking restrictions in TS 38.101-5 [34] into consideration.

This feature is applicable only for FR1 and FR2-1 band, otherwise it is absent.

NOTE: To determine whether the UE supports a specific SCS for a given band, the network validates the supportedSubCarrierSpacingUL and the scs-60kHz .
To determine whether the UE supports a channel bandwidth of 90 MHz the network may ignore this capability and validate instead the channelBW-90mhz , the supportedBandwidthCombinationSet and the supportedBandwidthCombinationSetIntraENDC . To determine whether the UE supports a channel bandwidth of 400 MHz, the network may ignore this capability and validate the supportedBandwidthCombinationSet , the supportedBandwidthCombinationSetIntraENDC , and the supportedBandwidthUL . For serving cell(s) with other channel bandwidths the network validates the channelBWs-UL , the supportedBandwidthCombinationSet , the supportedBandwidthCombinationSetIntraENDC , the asymmetricBandwidthCombinationSet (for a band supporting asymmetric channel bandwidth as defined in clause 5.3.6 of TS 38.101-1 [2]), supportedBandwidthUL/supportBandwidthUL-v1710 and supportedMinBandwidthUL . | Band | Yes | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| channelBWs-UL-SCS-120kHz-FR2-2-r17
Indicates the UE supported channel bandwidths in UL for the SCS 120kHz.
The bits in channelBWs-UL-SCS-120kHz-FR2-2 starting from the leading / leftmost bit indicate 100 and 400MHz.
100 and 400 MHz are mandatory channel bandwidths if the UE supports 120 kHz SCS (i.e. the bit for 100 and 400MHz shall always be set to 1).
UE supporting this feature shall also indicate support of ul-FR2-2-SCS-120kHz-r17 .

NOTE: To determine whether the UE supports a SCS 120kHz for a given band, the network validates the supportedSubCarrierSpacingUL .
To determine the supported carrier bandwidths, the network validates the channelBWs-UL-SCS-120kHz-FR2-2-r17 , the supportedBandwidthCombinationSet and the supportedBandwidthUL-v1710 . | Band | CY | N/A | N/A | +| channelBWs-UL-SCS-480kHz-FR2-2-r17
Indicates the UE supported channel bandwidths in UL for the SCS 480kHz.
The bits in channelBWs-UL-SCS-480kHz-FR2-2 starting from the leading / leftmost bit indicate 400, 800 and 1600MHz.
400 MHz is a mandatory channel bandwidth if the UE supports 480 kHz SCS (i.e. the bit for 400MHz shall always be set to 1).
UE supporting this feature shall also indicate support of ul-FR2-2-SCS-480kHz-r17 .

NOTE: To determine whether the UE supports a SCS 480kHz for a given band, the network validates the supportedSubCarrierSpacingUL .
To determine the supported carrier bandwidths, the network validates the channelBWs-UL-SCS-480kHz-FR2-2-r17 , the supportedBandwidthCombinationSet and supportedBandwidthUL-v1710 . | Band | CY | N/A | N/A | +| channelBWs-UL-SCS-960kHz-FR2-2-r17
Indicates the UE supported channel bandwidths in UL for the SCS 960kHz.
The bits in channelBWs-UL-SCS-960kHz-FR2-2 starting from the leading / leftmost bit indicate 400, 800, 1600 and 2000MHz.

400 MHz is a mandatory channel bandwidth if the UE supports 960 kHz SCS (i.e. the bit for 400MHz shall always be set to 1).
UE supporting this feature shall also indicate support of ul-FR2-2-SCS-960kHz-r17 .

NOTE: To determine whether the UE supports a SCS 960kHz for a given band, the network validates the supportedSubCarrierSpacingUL .
To determine the supported carrier bandwidths, the network validates the channelBWs-UL-SCS-960kHz-FR2-2-r17 , the supportedBandwidthCombinationSet and supportedBandwidthUL-v1710 . | Band | CY | N/A | N/A | +| channelBW-DL-IAB-r16
Indicates whether the IAB-MT supports channel bandwidth of 100 MHz for a given SCS in FR1 for DL or whether the IAB-MT supports channel bandwidth of 200 MHz for a given SCS in FR2 for DL. | Band | No | N/A | N/A | +| channelBW-UL-IAB-r16
Indicates whether the IAB-MT supports channel bandwidth of 100 MHz for a given SCS in FR1 for UL or whether the IAB-MT supports channel bandwidth of 200 MHz for a given SCS in FR2 for UL. | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| codebookComboParametersAddition-r16
Indicates the UE supports the mixed codebook combinations and the corresponding parameters supported by the UE.

For mixed codebook types, UE reports support active CSI-RS resources and ports for up to 4 mixed codebook combinations in any slot. The following is the possible mixed codebook combinations:
  • - {Type 1 Single Panel, Type 2, Null}
  • - {Type 1 Single Panel, Type 2 with port selection, Null}
  • - {Type 1 Single Panel, eType 2 with R=1, Null}
  • - {Type 1 Single Panel, eType 2 with R=2, Null}
  • - {Type 1 Single Panel, eType 2 with R=1 and port selection, Null}
  • - {Type 1 Single Panel, eType 2 with R=2 and port selection, Null}
  • - {Type 1 Single Panel, Type 2, Type 2 with port selection}
  • - {Type 1 Multi Panel, Type 2, Null}
  • - {Type 1 Multi Panel, Type 2 with port selection, Null}
  • - {Type 1 Multi Panel, eType 2 with R=1, Null}
  • - {Type 1 Multi Panel, eType 2 with R=2, Null}
  • - {Type 1 Multi Panel, eType 2 with R=1 with port selection, Null}
  • - {Type 1 Multi Panel, eType 2 with R=2 with port selection, Null}
  • - {Type 1 Multi Panel, Type 2, Type 2 with port selection}
Parameters for each mixed codebook supported by the UE:
  • - supportedCSI-RS-ResourceListAdd-r16 indicates the list of supported CSI-RS resources in a band by referring to codebookVariantsList. The following parameters are included in codebookVariantsList:
For supportedCSI-RS-ResourceListAdd-r16 related to the additional codebooks:
  • - The minimum of maxNumberTxPortsPerResource is 'p4';
  • - The minimum value of totalNumberTxPortsPerBand is 4.
If a UE reports one or more mixed codebook combinations, then usage of active CSI-RS resources and ports for multiple codebooks in any slot is allowed only within those combinations. For coexisting of mixed codebooks in any slot, gNB needs to consider the mixed codebook combination capability as well as per codebook capability of each codebook type in the mixed codebook combination. UE indicates support of a codebook type in the mixed codebook combination shall indicates support of the individual codebook type in the per band capability. | Band | No | N/A | N/A | +| codebookParameters
Indicates the codebooks and the corresponding parameters supported by the UE.

Parameters for type I single panel codebook (type1 singlePanel) supported by the UE, which are mandatory to report:
  • - supportedCSI-RS-ResourceList;
    • - a UE shall support a maxNumberTxPortsPerResource minimum value of 4 for codebook type I single panel in FR1 in the case of a single active CSI-resource across all bands in a band combination, regardless of what it reports in supportedCSI-RS-ResourceList with maxNumberTxPortsPerResource;
    • - a UE shall support a maxNumberTxPortsPerResource minimum value of 8 when configured with wideband CSI report for codebook type I single
| Band | FD | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| panel in FR1 in the case of a single active CSI-resource across all bands in a band combination, regardless of what it reports in supportedCSI-RS-ResourceList with maxNumberTxPortsPerResource ;
  • - a UE shall support a maxNumberTxPortsPerResource minimum value of 2 for codebook type I single panel in FR2 in the case of a single active CSI-resource across all bands in a band combination, regardless of what it reports in supportedCSI-RS-ResourceList with maxNumberTxPortsPerResource.
  • - modes indicates supported codebook modes (mode 1, both mode 1 and mode 2);
  • - maxNumberCSI-RS-PerResourceSet indicates the maximum number of CSI-RS resource in a resource set.
Parameters for type I multi-panel codebook (type1 multiPanel) supported by the UE, which are optional:
  • - supportedCSI-RS-ResourceList;
  • - modes indicates supported codebook modes (mode 1, mode 2, or both mode 1 and mode 2);
  • - maxNumberCSI-RS-PerResourceSet indicates the maximum number of CSI-RS resource in a resource set;
  • - nrofPanels indicates supported number of panels.
Parameters for type II codebook (type2) supported by the UE, which are optional:
  • - supportedCSI-RS-ResourceList;
  • - parameterLx indicates the parameter "Lx" in codebook generation where x is an index of Tx ports indicated by maxNumberTxPortsPerResource;
  • - amplitudeScalingType indicates the amplitude scaling type supported by the UE (wideband or both wideband and sub-band);
  • - amplitudeSubsetRestriction indicates whether amplitude subset restriction is supported for the UE.
Parameters for type II codebook with port selection (type2-PortSelection) supported by the UE, which are optional:
  • - supportedCSI-RS-ResourceList;
  • - parameterLx indicates the parameter "Lx" in codebook generation where x is an index of Tx ports indicated by maxNumberTxPortsPerResource;
  • - amplitudeScalingType indicates the amplitude scaling type supported by the UE (wideband or both wideband and sub-band).
supportedCSI-RS-ResourceList includes list of the following parameters:
  • - maxNumberTxPortsPerResource indicates the maximum number of Tx ports in a resource;
  • - maxNumberResourcesPerBand indicates the maximum number of resources across all CCs within a band simultaneously;
  • - totalNumberTxPortsPerBand indicates the total number of Tx ports across all CCs within a band simultaneously.
For each codebook type, the UE may report another list of supported CSI-RS resources via supportedCSI-RS-ResourceListAlt in codebookParametersPerBand .
For type I single panel codebook (type1 singlePanel) supportedCSI-RS-ResourceListAlt,
  • - a UE shall report at least one triplet in supportedCSI-RS-ResourceListAlt with maxNumberTxPortsPerResource greater than or equal to 8 for FR1;
| | | | | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| codebookParametersAddition-r16
Indicates the UE support of additional codebooks and the corresponding parameters supported by the UE.

Codebook etype 2 R=1 support parameter combination 1 to 6 and rank 1 to 2. Parameters for etype 2 R=1 ( etype2R1-r16 ) supported by the UE, which are optional:
  • - supportedCSI-RS-ResourceListAdd-r16 indicates the list of supported CSI-RS resources in a band by referring to codebookVariantsList. The following parameters are included in codebookVariantsList:
    • - maxNumberTxPortsPerResource indicates the maximum number of Tx ports in a resource of a band;
    • - maxNumberResourcesPerBand indicates the maximum number of resources across all CCs in a band, simultaneously;
    • - totalNumberTxPortsPerBand indicates the total number of Tx ports across all CCs in a band, simultaneously.
  • - paramComb7-8-r16 indicates the support of parameter combinations 7-8 for etype 2 R=1
  • - rank3-4-r16 indicates the support of rank 3,4.
  • - amplitudeSubsetRestriction-r16 indicates the support of amplitude subset restriction.
Parameters for etype 2 R=2 ( etype2R2-r16 ) supported by the UE, which are optional:
  • - supportedCSI-RS-ResourceListAdd-r16;
UE supporting etype2R2-r16 supports also indicates support of etype2R1-r16 .

Codebook etype 2 R=1 with port selection supports 6 parameter combinations and rank 1,2. Parameters for etype 2 R=1 with port selection ( etype2R1-PortSelection-r16 ) supported by the UE, which are optional:
  • - supportedCSI-RS-ResourceListAdd-r16;
  • - rank3-4-r16 indicates the support of rank 3,4
Parameters for etype 2 R=2 with port selection ( etype2R2-PortSelection-r16 ) supported by the UE, which are optional:
  • - supportedCSI-RS-ResourceListAdd-r16;
UE supporting etype2R2-PortSelection-r16 also indicates support of etype2R1-PortSelection-r16 .

For supportedCSI-RS-ResourceListAdd-r16 related to the additional codebooks:
  • - The minimum of maxNumberTxPortsPerResource is 'p4';
  • - The minimum value of totalNumberTxPortsPerBand is 4.
| Band | No | N/A | N/A | +| codebookParametersetype2DopplerCSI-r18
Indicates the UE support of additional codebooks and the corresponding parameters supported by the UE of Enhanced Type II Codebook (eType-II) based on doppler CSI as specified in TS 38.214 [12].

The UE indicating this feature shall include eType2Doppler-r18 to indicate basic features of eType-II. This capability signalling comprises the following parameters:
  • - supportedCSI-RS-ResourceList-r18 indicates the list of supported CSI-RS resources in a band by referring to codebookVariantsList. The following parameters are included in codebookVariantsList:
| Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +|

ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17

Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17.

| Band | No | N/A | N/A | +|

ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17

Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17.

| Band | No | N/A | N/A | +|
  • - maxNumberTxPortsPerResource indicates the maximum number of Tx ports in a resource of a band
  • - maxNumberResourcesPerBand indicates the maximum number of resources across all CCs in a band, simultaneously
  • - totalNumberTxPortsPerBand indicates the total number of Tx ports across all CCs in a band, simultaneously
  • - valueY-P-SP-CSI-RS-r18 indicates value of Y for CPU occupation (OCPU = Y.N4), when P/SP-CSI-RS is configured for CMR
  • - valueY-A-CSI-RS-r18 indicates value of Y for CPU occupation (OCPU = Y.K), when A-CSI-RS is configured for CMR
  • - scalingfactor-r18 indicates scaling factor for active resource counting Kp

The UE indicating eType2Doppler-r18 shall support X=1 CQI based on the first/earliest slot of the CSI reporting window and the first/earliest predicted PMI (TDCQI='1-1'), support eType-II regular codebook refinement for predicted PMI with PMI subband R=1 3, support parameter combinations with L=2,4, support for rank = 1,2, and support for the size of DD-basis, N4=1. A UE indicating this feature shall also indicate the support of csi-ReportFramework.

The UE optionally includes eType2DopplerN4-r18 to indicate whether the UE supports doppler measurement with N4>1 for eType-II. This capability signalling comprises the following parameters:

  • - supportedCSI-RS-ReportSettingList1-r18 indicates the list of supported combinations across all CCs simultaneously by referring to supportedCSI-RS-ReportSettingList The following parameters are included in supportedCSI-RS-ReportSettingList-r18
    • - maxN4-r18 indicates the max number of N4
    • - maxNumberTxPortsPerResource-r18 indicates the maximum number of Tx ports in a resource of a band
    • - maxNumberResourcesPerBand-r18 indicates the maximum number of resources across all CCs in a band, simultaneously
    • - totalNumberTxPortsPerBand-r18 indicates the total number of Tx ports across all CCs in a band, simultaneously
  • - supportedCSI-RS-ReportSettingList2-r18 indicates the list of supported combinations for one CSI report setting by referring to supportedCSI-RS-ReportSettingList-r18.

The UE indicating support of eType2DopplerN4-r18 shall also indicate support of eType2Doppler-r18, support for the size of DD-basis, N4>1, and Value of d=m for the DD unit size when A-CSI-RS is configured for CMR.

The UE optionally includes ddUnitSize-A-CSI-RS-CMR-r18 to indicate the support of value of d=1 for the DD unit size when A-CSI-RS is configured for CMR. A UE supporting this feature shall also indicate support of eType2DopplerN4-r18.

The UE optionally includes eType2DopplerR2-r18 to indicate whether the UE supports R=2 for eType-II. This capability signalling comprises the following parameters:

  • - indicates the list of supported CSI-RS resources in a band by referring to codebookVariantsList.
| | | | | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| UE indicating support of eType2DopplerR2-r18 shall also indicate support of eType2Doppler-r18 .

The UE optionally includes eType2DopplerX1-r18 to indicate whether the UE support X=1 based on first and last slot of WCSI, for eType-II doppler codebook.

The UE optionally includes eType2DopplerX2-r18 to indicate whether the UE support X=2 CQI based on 2 slots for eType-II doppler codebook.

The UE optionally includes eType2DopplerL-N4D1-r18 to indicate whether the UE support support of $l = (n - n_{CSI,ref})$ for CSI reference slot for eType-II doppler codebook. UE indicating support of eType2DopplerL-N4D1-r18 shall indicate support of eType2Doppler-r18 .

For codebookVariantsList-r16 related to the eType-II:
  • - The minimum of maxNumberTxPortsPerResource is 'p4';
  • - The minimum of maxNumberResourcesPerBand is 2, except for eType2DopplerR2-r18.
  • - The minimum value of totalNumberTxPortsPerBand is 4.
| | | | | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| codebookParametersFetype2-r17
Indicates the UE support of additional codebooks and the corresponding parameters supported by the UE of Further Enhanced Port-Selection Type II Codebook (FeType-II) as specified in TS 38.214 [12] clause 5.2.2.2.7.

The UE indicating this feature shall include fetype2basic-r17 to indicate basic features of FeType-II. This capability signalling comprises the following parameters:
  • - indicates the list of supported CSI-RS resources in a band by referring to codebookVariantsList. The following parameters are included in codebookVariantsList:
    • - maxNumberTxPortsPerResource indicates the maximum number of Tx ports in a resource of a band
    • - maxNumberResourcesPerBand indicates the maximum number of resources across all CCs in a band, simultaneously
    • - totalNumberTxPortsPerBand indicates the total number of Tx ports across all CCs in a band, simultaneously
The UE indicating fetype2basic-r17 shall support parameter combinations with M=1 and support rank 1 and 2. UE indicating this feature shall also include csi-ReportFramework .

The UE optionally includes fetype2R1-r17 to indicate whether the UE supports M=2 and R=1 for FeType-II. This capability signalling comprises the following parameters:
  • - indicates the list of supported CSI-RS resources in a band by referring to codebookVariantsList.
The UE indicating support of fetype2R1-r17 shall also indicate support of fetype2basic-r17 and parameter combinations with M=2.

The UE optionally includes fetype2R2-r17 to indicate whether the UE supports R=2 for FeType-II. This capability signalling comprises the following parameters:
  • - indicates the list of supported CSI-RS resources in a band by referring to codebookVariantsList.
UE indicating support of fetype2R2-r17 shall also indicate support of fetype2R1-r17 .

The UE optionally includes fetype2Rank3Rank4-r17 to indicate whether the UE supports rank = 3 and rank = 4 for FeType-II. UE indicating support of fetype2Rank3Rank4-r17 shall indicate support of fetype2basic-r17 .

For codebookVariantsList related to the FeType-II:
  • - The minimum of maxNumberTxPortsPerResource is 'p4';
  • - The minimum value of totalNumberTxPortsPerBand is 4.
| Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +|

ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17.

| Band | No | N/A | N/A | +|

ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17.

| Band | No | N/A | N/A | +|

codebookParametersFeType2DopplerCSI-r18
Indicates the UE support of additional codebooks and the corresponding parameters supported by the UE of Further Enhanced Type II Codebook (FeType-II) based on doppler CSI as specified in TS 38.214 [12].

The UE indicating this feature shall include feType2Doppler-r18 to indicate basic features of FeType-II. This capability signalling comprises the following parameters:

  • - supportedCSI-RS-ResourceList-r18 indicates the list of supported CSI-RS resources in a band by referring to codebookVariantsList. The following parameters are included in codebookVariantsList:
    • - maxNumberTxPortsPerResource indicates the maximum number of Tx ports in a resource of a band
    • - maxNumberResourcesPerBand indicates the maximum number of resources across all CCs in a band, simultaneously
    • - totalNumberTxPortsPerBand indicates the total number of Tx ports across all CCs in a band, simultaneously
  • - valueY-A-CSI-RS-r18 indicates value of Y for CPU occupation (OCPU = Y·K), when A-CSI-RS is configured for CMR
  • - scalingfactor-r18 indicates scaling factor for active resource counting Kp

The UE indicating feType2Doppler-r18 shall support X=1 CQI based on the first/earliest slot of the CSI reporting window and the first/earliest predicted PMI, support FeType-II regular codebook refinement for predicted PMI with PMI subband R=1, support parameter combinations with M=1, support for rank = 1,2, and support N4=1. A UE indicating this feature shall also indicate the support of csi-ReportFramework.

The UE optionally includes feType2DopplerM2R1-r18 to indicate whether the UE supports M=2 and R=1 for FeType-II doppler codebook. This capability signalling comprises the following parameters:

  • - indicates the list of supported CSI-RS resources in a band by referring to codebookVariantsList.

The UE indicating support of feType2DopplerM2R1-r18 shall also indicate support of feType2Doppler-r18.

The UE optionally includes feType2DopplerR2-r18 to indicate whether the UE supports R=2 for FeType-II. This capability signalling comprises the following parameters:

  • - indicates the list of supported CSI-RS resources in a band by referring to codebookVariantsList.

UE indicating support of feType2DopplerR2-r18 shall also indicate support of feType2Doppler-r18.

The UE optionally includes feType2DopplerL-N4D1-r18 to indicate whether the UE support support of l = (n – nCSI,ref) for CSI reference slot for FeType-II doppler codebook. UE indicating support of feType2DopplerL-N4D1-r18 shall indicate support of feType2Doppler-r18.

For codebookVariantsList-r16 related to the FeType-II:

  • - The minimum of maxNumberTxPortsPerResource is 'p4'.
| Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| codebookComboParameterMixedType-r17
Indicates the support of active CSI-RS resources and ports for mixed codebook types in any slot. The UE reports support active CSI-RS resources and ports for up to 4 mixed codebook combinations in any slot. The following are the possible mixed codebook combinations {Codebook1, Codebook2, Codebook3}:
  • - type1SP-feType2PS-null-r17 indicates {Type 1 Single Panel, FeType II PS M=1, NULL}
  • - type1SP-feType2PS-M2R1-null-r17 indicates {Type 1 Single Panel, FeType II PS M=2 R=1, NULL}
  • - type1SP-feType2PS-M2R2-null-r17 indicates {Type 1 Single Panel, FeType II PS M=2 R=2, NULL}
  • - type1SP-Type2-feType2-PS-M1-r17 indicates {Type 1 Single Panel, Type II, FeType II PS M=1}
  • - type1SP-Type2-feType2-PS-M2R1-r17 indicates {Type 1 Single Panel, Type II, FeType II PS M=2 R=1}
  • - type1SP-eType2R1-feType2-PS-M1-r17 indicates {Type 1 Single Panel, eType II R=1, FeType II PS M=1}
  • - type1SP-eType2R1-feType2-PS-M2R1-r17 indicates {Type 1 Single Panel, eType II R=1, FeType II PS M=2 R=1}
  • - type1MP-feType2PS-null-r17 indicates {Type 1 Multi Panel, FeType II PS M=1, NULL}
  • - type1MP-feType2PS-M2R1-null-r17 indicates {Type 1 Multi Panel, FeType II PS M=2 R=1, NULL}
  • - type1MP-feType2PS-M2R2-null-r17 indicates {Type 1 Multi Panel, FeType II PS M=2 R=2, NULL}
  • - type1MP-Type2-feType2-PS-M1-r17 indicates {Type 1 Multi Panel, Type II, FeType II PS M=1}
  • - type1MP-Type2-feType2-PS-M2R1-r17 indicates {Type 1 Multi Panel, Type II, FeType II PS M=2 R=1}
  • - type1MP-eType2R1-feType2-PS-M1-r17 indicates {Type 1 Multi Panel, eType II R=1, FeType II PS M=1}
  • - type1MP-eType2R1-feType2-PS-M2R1-r17 indicates {Type 1 Multi Panel, eType II R=1, FeType II PS M=2 R=1}
For each mixed codebook supported by the UE, supportedCSI-RS-ResourceListAdd-r16 indicates the list of supported CSI-RS resources in a band by referring to codebookVariantsList . The following parameters are included for the supported CSI-RS resource:
  • - maxNumberTxPortsPerResource indicates the maximum number of Tx ports in a resource of a band. The minimum of maxNumberTxPortsPerResource is 'p4';
  • - maxNumberResourcesPerBand indicates the maximum number of resources across all CCs in a band;
  • - totalNumberTxPortsPerBand indicates the total number of Tx ports across all CCs in a band. The minimum value of totalNumberTxPortsPerBand is 4.
The UE supporting this feature shall indicate the support of fetype2basic-r17 , etype2R1-r16 , CodebookComboParametersAddition-r16 , supportedCSI-RS-ResourceList , fetype2R1-r17 , fetype2R2-r17 . | Band | No | N/A | N/A | +| codebookComboParameterMultiTRP-r17 | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| Indicates the support of active CSI-RS resources and ports in the presence of multi-TRP CSI.
Indicates the support of active CSI-RS resources and ports for mixed codebook types in any slot. The UE reports supported active CSI-RS resources and ports for up to 4 mixed codebook combinations. The following are the possible mixed codebook combinations {Codebook1, Codebook2, Codebook3}:
  • - nCJT-null-null indicates {NCJT, NULL, NULL}
  • - nCJT1SP-null-null indicates {NCJT+Type 1 SP for sTRP, NULL, NULL}
  • - nCJT-Type2-null-r16 indicates {NCJT, Type 2, Null}
  • - nCJT-Type2PS-null-r16 indicates {NCJT, Type 2 with port selection, Null}
  • - nCJT-eType2R1-null-r16 indicates {NCJT, eType 2 with R=1, Null}
  • - nCJT-eType2R2-null-r16 indicates {NCJT, eType 2 with R=2, Null}
  • - nCJT-eType2R1PS-null-r16 indicates {NCJT, eType 2 with R=1 and port selection, Null}
  • - nCJT-eType2R2PS-null-r16 indicates {NCJT, eType 2 with R=2 and port selection, Null}
  • - nCJT-Type2-Type2PS-r16 indicates {NCJT, Type 2, Type 2 with port selection}
  • - nCJT1SP-Type2-null-r16 indicates {NCJT+Type 1 SP for sTRP, Type 2, Null}
  • - nCJT1SP-Type2PS-null-r16 indicates {NCJT+Type 1 SP for sTRP, Type 2 with port selection, Null}
  • - nCJT1SP-eType2R1-null-r16 indicates {NCJT+Type 1 SP for sTRP, eType 2 with R=1, Null}
  • - nCJT1SP-eType2R2-null-r16 indicates {NCJT+Type 1 SP for sTRP, eType 2 with R=2, Null}
  • - nCJT1SP-eType2R1PS-null-r16 indicates {NCJT+Type 1 SP for sTRP, eType 2 with R=1 and port selection, Null}
  • - nCJT1SP-eType2R2PS-null-r16 indicates {NCJT+Type 1 SP for sTRP, eType 2 with R=2 and port selection, Null}
  • - nCJT1SP-Type2-Type2PS-r16 indicates {NCJT+Type 1 SP for sTRP, Type 2, Type 2 with port selection}
  • - nCJT-feType2PS-null-r17 indicates {NCJT, FeType II PS M=1, NULL}
  • - nCJT-feType2PS-M2R1-null-r17 indicates {NCJT, FeType II PS M=2 R=1, NULL}
  • - nCJT-feType2PS-M2R2-null-r17 indicates {NCJT, FeType II PS M=2 R=2, NULL}
  • - nCJT-Type2-feType2-PS-M1-r17 indicates {NCJT, Type II, FeType II PS M=1}
  • - nCJT-Type2-feType2-PS-M2R1-r17 indicates {NCJT, Type II, FeType II PS M=2 R=1}
  • - nCJT-eType2R1-feType2-PS-M1-r17 indicates {NCJT, eType II R=1, FeType II PS M=1}
  • - nCJT-eType2R1-feType2-PS-M2R1-r17 indicates {NCJT, eType II R=1, FeType II PS M=2 R=1}
  • - nCJT1SP-feType2PS-null-r17 indicates {NCJT+Type 1 SP for sTRP, FeType II PS M=1, NULL}
  • - nCJT1SP-feType2PS-M2R1-null-r17 indicates {NCJT+Type 1 SP for sTRP, FeType II PS M=2 R=1, NULL}
  • - nCJT1SP-feType2PS-M2R2-null-r17 indicates {NCJT+Type 1 SP for sTRP, FeType II PS M=2 R=2, NULL}
| | | | | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +|
  • - nCJT1SP-Type2-feType2-PS-M1-r17 indicates {NCJT+Type 1 SP for sTRP, Type II, FeType II PS M=1}
  • - nCJT1SP-Type2-feType2-PS-M2R1-r17 indicates {NCJT+Type 1 SP for sTRP, Type II, FeType II PS M=2 R=1}
  • - nCJT1SP-eType2R1-feType2-PS-M1-r17 indicates {NCJT+Type 1 SP for sTRP, eType II R=1, FeType II PS M=1}
  • - nCJT1SP-eType2R1-feType2-PS-M2R1-r17 indicates {NCJT+Type 1 SP for sTRP, eType II R=1, FeType II PS M=2 R=1}
For each mixed codebook supported by the UE, supportedCSI-RS-ResourceListAdd-r16 indicates the list of supported CSI-RS resources in a band by referring to codebookVariantsList . The following parameters are included in codebookVariantsList :
  • - maxNumberTxPortsPerResource indicates the maximum number of Tx ports in a resource of a band combination.
  • - maxNumberResourcesPerBand indicates the maximum number of resources across all CCs in a band combination.
  • - totalNumberTxPortsPerBand indicates the total number of Tx ports across all CCs in a band combination.
NOTE 1: A CMR pair configured for NCJT will be counted as two activated resources, a CMR configured for sTRP will be counted as one activated resource for a triplet.

NOTE 2: This capability is relevant only when UE is configured with NCJT CSI in at least one CSI report setting in at least one CC in the band and/or band combination.

The UE indicating support of this feature shall also indicate the support of mTRP-CSI-EnhancementPerBand-r17 . | | | | | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| condHandover-r16
Indicates whether the UE supports conditional handover including execution condition, candidate cell configuration and maximum 8 candidate cells. Except for NTN bands, UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands, all TDD-FR2-1 bands and all TDD-FR2-2 bands respectively. For NTN, UE shall set the capability value consistently for all FDD-FR1 NTN bands. | Band | No | N/A | N/A | +| condHandoverFailure-r16
Indicates whether the UE supports conditional handover during re-establishment procedure when the selected cell is configured as candidate cell for condition handover. Except for NTN bands, UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands, all TDD-FR2-1 bands and all TDD-FR2-2 bands respectively. For NTN, UE shall set the capability value consistently for all FDD-FR1 NTN bands. | Band | No | N/A | N/A | +| condHandoverTwoTriggerEvents-r16
Indicates whether the UE supports 2 trigger events for same execution condition. This feature is mandatory supported if the UE supports condHandover-r16 . Except for NTN bands, UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands, all TDD-FR2-1 bands and all TDD-FR2-2 bands respectively. For NTN, UE shall set the capability value consistently for all FDD-FR1 NTN bands. | Band | CY | N/A | N/A | +| condPSCellChange-r16
Indicates whether the UE supports conditional PSCell change including execution condition, candidate cell configuration and maximum 8 candidate cells. UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands, all TDD-FR2-1 bands and all TDD-FR2-2 bands respectively. | Band | No | N/A | N/A | +| condPSCellChangeTwoTriggerEvents-r16
Indicates whether the UE supports 2 trigger events for same execution condition. This feature is mandatory supported if the UE supports condPSCellChange-r16 . UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands, all TDD-FR2-1 bands and all TDD-FR2-2 bands respectively. | Band | CY | N/A | N/A | +| configuredUL-GrantType1-v1650
Indicates whether the UE supports Type 1 PUSCH transmissions with configured grant as specified in TS 38.214 [12] with UL-TWG-repK value of one. This applies only to non-shared spectrum channel access. For shared spectrum channel access, configuredUL-GrantType1-r16 applies. UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands, all TDD-FR2-1 bands and all TDD-FR2-2 bands respectively.

The UE only includes configuredUL-GrantType1-v1650 if configuredUL-GrantType1 is absent. | Band | No | N/A | N/A | +| configuredUL-GrantType2-v1650
Indicates whether the UE supports Type 2 PUSCH transmissions with configured grant as specified in TS 38.214 [12] with UL-TWG-repK value of one. This applies only to non-shared spectrum channel access. For shared spectrum channel access, configuredUL-GrantType2-r16 applies. UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands, all TDD-FR2-1 bands and all TDD-FR2-2 bands respectively.

The UE only includes configuredUL-GrantType2-v1650 if configuredUL-GrantType2 is absent. | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| cqi-4-BitsSubbandNTN-SharedSpectrumChAccess-r17
Indicates whether the UE supports CQI reporting with 4 bits per subband for NTN and shared spectrum channel access. | Band | No | N/A | N/A | +| crossCarrierScheduling-SameSCS
Indicates whether the UE supports cross carrier scheduling for the same numerology with carrier indicator field (CIF) in carrier aggregation where numerologies for the scheduling cell and scheduled cell are same. | Band | No | N/A | N/A | +| csi-ReportFramework
Indicates whether the UE supports CSI report framework. This capability signalling comprises the following parameters:
  • - maxNumberPeriodicCSI-PerBWP-ForCSI-Report indicates the maximum number of periodic CSI report setting per BWP for CSI report;
  • - maxNumberPeriodicCSI-PerBWP-ForBeamReport indicates the maximum number of periodic CSI report setting per BWP for beam report.
  • - maxNumberAperiodicCSI-PerBWP-ForCSI-Report indicates the maximum number of aperiodic CSI report setting per BWP for CSI report;
  • - maxNumberAperiodicCSI-PerBWP-ForBeamReport indicates the maximum number of aperiodic CSI report setting per BWP for beam report;
  • - maxNumberAperiodicCSI-triggeringStatePerCC indicates the maximum number of aperiodic CSI triggering states in CSI-AperiodicTriggerStateList per CC;
  • - maxNumberSemiPersistentCSI-PerBWP-ForCSI-Report indicates the maximum number of semi-persistent CSI report setting per BWP for CSI report;
  • - maxNumberSemiPersistentCSI-PerBWP-ForBeamReport indicates the maximum number of semi-persistent CSI report setting per BWP for beam report;
  • - simultaneousCSI-ReportsPerCC indicates the number of CSI report(s) for which the UE can measure and process reference signals simultaneously in a CC of the band for which this capability is provided. The CSI report comprises periodic, semi-persistent and aperiodic CSI and any latency classes and codebook types. The CSI report in simultaneousCSI-ReportsPerCC includes the beam report and CSI report.
The UE is mandated to report csi-ReportFramework . | Band | Yes | N/A | N/A | +| csi-ReportFrameworkExt-r16
Indicates whether the UE supports the extension of the maximum number of configured aperiodic CSI report settings for all codebook types. The capability signalling comprises the following:
maxNumberAperiodicCSI-PerBWP-ForCSI-ReportExt-r16 indicates the extended maximum number of aperiodic CSI report setting per BWP for CSI report. If present, the value of maxNumberAperiodicCSI-PerBWP-ForCSI-Report-r16 shall replace the corresponding value in csi-ReportFramework . | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| csi-RS-ForTracking
Indicates support of CSI-RS for tracking (i.e. TRS). This capability signalling comprises the following parameters:
  • - maxBurstLength indicates the TRS burst length. Value 1 indicates 1 slot and value 2 indicates both of 1 slot and 2 slots. In this release UE is mandated to report value 2;
  • - maxSimultaneousResourceSetsPerCC indicates the maximum number of TRS resource sets per CC which the UE can track simultaneously;
  • - maxConfiguredResourceSetsPerCC indicates the maximum number of TRS resource sets configured to UE per CC. It is mandated to report at least 8 for FR1 and 16 for FR2;
  • - maxConfiguredResourceSetsAllCC indicates the maximum number of TRS resource sets configured to UE across CCs. If the UE includes the field in an FR1 band, it shall set the same value in all FR1 bands. If the UE includes the field in an FR2 band, it shall set the same value in all FR2 bands. The UE supports a total number of resources equal to the maximum of the FR1 and FR2 value, but no more than the FR1 value across all FR1 serving cells and no more than the FR2 value across all FR2 serving cells. The UE is mandated to report at least 16 for FR1 and 32 for FR2.
The UE is mandated to report csi-RS-ForTracking . | Band | Yes | N/A | N/A | +| csi-RS-IM-ReceptionForFeedback
Indicates support of CSI-RS and CSI-IM reception for CSI feedback. This capability signalling comprises the following parameters:
  • - maxConfigNumberNZP-CSI-RS-PerCC indicates the maximum number of configured NZP-CSI-RS resources per CC;
  • - maxConfigNumberPortsAcrossNZP-CSI-RS-PerCC indicates the maximum number of ports across all configured NZP-CSI-RS resources per CC;
  • - maxConfigNumberCSI-IM-PerCC indicates the maximum number of configured CSI-IM resources per CC;
  • - maxNumberSimultaneousNZP-CSI-RS-PerCC indicates the maximum number of simultaneous CSI-RS-resources per CC;
  • - totalNumberPortsSimultaneousNZP-CSI-RS-PerCC indicates the total number of CSI-RS ports in simultaneous CSI-RS resources per CC.
The UE is mandated to report csi-RS-IM-ReceptionForFeedback . | Band | Yes | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| csi-RS-ProcFrameworkForSRS
Indicates support of CSI-RS processing framework for SRS. This capability signalling comprises the following parameters:
  • - maxNumberPeriodicSRS-AssocCSI-RS-PerBWP indicates the maximum number of periodic SRS resources associated with CSI-RS per BWP;
  • - maxNumberAperiodicSRS-AssocCSI-RS-PerBWP indicates the maximum number of aperiodic SRS resources associated with CSI-RS per BWP;
  • - maxNumberSP-SRS-AssocCSI-RS-PerBWP indicates the maximum number of semi-persistent SRS resources associated with CSI-RS per BWP;
  • - simultaneousSRS-AssocCSI-RS-PerCC indicates the number of SRS resources that the UE can process simultaneously in a CC, including periodic, aperiodic and semi-persistent SRS.
| Band | No | N/A | N/A | +| cyclicShiftHoppingWithinSubset-r18
Indicates whether the UE supports configuration of subset of cyclic shifts for cyclic shift hopping.
A UE supporting this feature shall also indicate the support FG40-5-2. | Band | No | N/A | N/A | +| defaultQCL-PerCORESETPoolIndex-r16
Indicates whether the UE supports default QCL assumption per CORESET pool index using multi-DCI based multi-TRP. The UE that indicates support of this feature shall support multiDCI-MultiTRP-r16 and simultaneousReceptionDiffTypeD-r16 . | Band | No | N/A | FR2 only | +| defaultQCL-TwoTCI-r16
Indicates whether the UE supports default QCL assumption with two TCI states using single-DCI based multi-TRP. The UE can include this field only if simultaneousReceptionDiffTypeD-r16 is present. Otherwise, the UE does not include this field. | Band | No | N/A | FR2 only | +| dmrs-BundlingNonBackToBackTX-r17
Indicates whether the UE supports DM-RS bundling for non-back-to-back transmission for consecutive slots for PUSCH and PUCCH only for corresponding supported back-to-back transmission as reported in dmrs-BundlingPUSCH-RepTypeA-r17 , dmrs-BundlingPUSCH-RepTypeB-r17 , dmrs-BundlingPUSCH-multiSlot-r17 or dmrs-BundlingPUCCH-Rep-r17 . The UE is considered to support the feature in a band of a band combination if the UE indicates support of the feature for the corresponding band and for the band combination.

UE indicating support of this feature shall also indicate support of at least one of dmrs-BundlingPUSCH-RepTypeA-r17 , dmrs-BundlingPUSCH-RepTypeB-r17 , dmrs-BundlingPUSCH-multiSlot-r17 or dmrs-BundlingPUCCH-Rep-r17 . | Band | No | N/A | N/A | +| dmrs-BundlingPUCCH-Rep-r17
Indicates whether the UE supports DM-RS bundling for PUCCH repetitions for PUCCH formats 1/3/4 over consecutive symbols. The UE is considered to support the feature in a band of a band combination if the UE indicates support of the feature for the corresponding band and for the band combination.

UE indicating support of this feature shall also indicate support of maxDurationDMRS-Bundling-r17 and pucch-Repetition-F1-3-4 . | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| dmrs-BundlingPUSCH-multiSlot-r17
Indicates whether the UE supports DM-RS bundling for TB processing over multi-slot PUSCH over consecutive symbols. The UE is considered to support the feature in a band of a band combination if the UE indicates support of the feature for the corresponding band and for the band combination.

UE indicating support of this feature shall also indicate support of maxDurationDMRS-Bundling-r17 and tb-ProcessingMultiSlotPUSCH-r17 . | Band | No | N/A | N/A | +| dmrs-BundlingPUSCH-RepTypeA-r17
Indicates whether the UE supports DM-RS bundling for PUSCH repetition type A over consecutive symbols. The UE is considered to support the feature in a band of a band combination if the UE indicates support of the feature for the corresponding band and for the band combination.

UE indicating support of this feature shall also indicate support of maxDurationDMRS-Bundling-r17 and at least one of type1-PUSCH-RepetitionMultiSlots , type2-PUSCH-RepetitionMultiSlots or pusch-RepetitionMultiSlots . | Band | No | N/A | N/A | +| dmrs-BundlingPUSCH-RepTypeB-r17
Indicates whether the UE supports DM-RS bundling for PUSCH repetition type B over consecutive symbols. The UE is considered to support the feature in a band of a band combination if the UE indicates support of the feature for the corresponding band and for the band combination.

UE indicating support of this feature shall also indicate support of maxDurationDMRS-Bundling-r17 and pusch-RepetitionTypeB-r16 . | Band | No | N/A | N/A | +| dmrs-BundlingRestart-r17
Indicates whether the UE supports restarting DM-RS bundling after the events triggered by DCI or MAC CE that violate power consistency and phase continuity. The UE is considered to support the feature in a band of a band combination if the UE indicates support of the feature for the corresponding band and for the band combination.

UE indicating support of this feature shall also indicate support of maxDurationDMRS-Bundling-r17 .

NOTE: Events which are triggered by DCI or MAC CE, but do not require UE capability to resume maintaining power consistency and/or phase continuity as specified in clause 6.1.7 of TS 38.214 [12] are excluded from this feature. | Band | No | N/A | N/A | +| dmrs-PortEntrySingleDCI-SDM-r18
Indicates whether the UE supports DMRS port entry {0, 2, 3}.
A UE indicates supporting of this feature shall also indicate support of pusch-CB-SingleDCI-STx2P-SDM-r18 and pusch-NonCB-SingleDCI-STx2P-SDM-r18 . | Band | No | N/A | FR2 only | +| dynamicMulticastDCI-Format4-2-r17
Indicates whether the UE supports DCI format 4_2 with CRC scrambled with G-RNTI for multicast.
A UE supporting this feature shall also indicate support of dynamicMulticastPCell-r17 . | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| dynamicSlotRepetitionMulticastNTN-SharedSpectrumChAccess-r17
Indicates the maximum number of supported dynamic slot-level repetitions for group-common PDSCH for multicast for NTN and shared spectrum channel access. Value n8 corresponds to 8, and value n16 corresponds to 16.
A UE supporting this feature shall also indicate support of dynamicMulticastPCell-r17 . | Band | No | N/A | N/A | +| dynamicSlotRepetitionMulticastTN-NonSharedSpectrumChAccess-r17
Indicates the maximum number of supported dynamic slot-level repetitions for group-common PDSCH for multicast for TN and non-shared spectrum channel access. Value n8 corresponds to 8, and value n16 corresponds to 16. UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands, all TDD-FR2 bands respectively.
A UE supporting this feature shall also indicate support of dynamicMulticastPCell-r17 . | Band | No | N/A | N/A | +| enhancedSkipUplinkTxConfigured-v1660
Indicates whether the UE supports skipping UL transmission for a configured uplink grant only if no data is available for transmission and no UCI is multiplexed on the corresponding PUSCH of the uplink grant as specified in TS 38.321 [8]. UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands, all TDD-FR2-1 bands and all TDD-FR2-2 bands respectively.
The UE only includes enhancedSkipUplinkTxConfigured-v1660 if enhancedSkipUplinkTxConfigured-r16 is absent. | Band | No | N/A | N/A | +| enhancedSkipUplinkTxDynamic-v1660
Indicates whether the UE supports skipping UL transmission for an uplink grant addressed to a C-RNTI only if no data is available for transmission and no UCI is multiplexed on the corresponding PUSCH of the uplink grant as specified in TS 38.321 [8]. UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands, all TDD-FR2-1 bands and all TDD-FR2-2 bands respectively.
The UE only includes enhancedSkipUplinkTxDynamic-v1660 if enhancedSkipUplinkTxDynamic-r16 is absent. | Band | No | N/A | N/A | +| enhancedType3-HARQ-CodebookFeedback-r17
Indicates whether the UE supports enhanced type 3 HARQ-ACK codebook feedback based on triggering information in DCI 1_1 and DCI 1_2 (for a UE supporting DCI format 1_2 as indicated in dci-Format1-2And0-2-r16 ) and also supports transmission of enhanced type 3 HARQ-ACK codebook using the first or second PUCCH configuration based on PHY priority indication in the triggering DCI (for a UE supporting two HARQ-ACK codebooks / PUCCH config as indicated in twoHARQ-ACK-Codebook-type1-r16 ). The capability signalling comprises the following parameters:
  • - enhancedType3-HARQ-Codebooks-r17 indicates the maximum number of supported enhanced type 3 HARQ-ACK codebooks;
  • - maxNumberPUCCH-Transmissions-r17 indicates the maximum number of actual PUCCH transmissions for type 3 or enhanced type 3 HARQ-ACK codebook feedback within a slot.
UE only supports feedback of a dynamically selected enhanced type 3 HARQ-ACK codebook based on triggering information in DCI 1_1 and DCI 1_2 (for a UE supporting DCI format 1_2 as indicated in dci-Format1-2And0-2-r16 ) if the UE supports more than one enhanced type 3 HARQ-ACK codebook to be configured (as indicated in enhancedType3-HARQ-Codebooks-r17 ). The UE indicates support of this capability shall also indicates support of oneShotHARQ-feedback-r16 . | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| enhancedUL-TransientPeriod-r16
Indicates whether the UE supports enhanced UL performance for the transient period as specified in clause 6.3.3 of TS 38.101-1 [2] and in clause 6.3.3 of TS 38.101-5 [34]. If not reported, the UE supports transient period of 10us. | Band | No | N/A | FR1 only | +| eventA4BasedCondHandover-r17
Indicates whether the UE supports Event A4 based conditional handover in NTN bands, i.e., CondEvent A4 as specified in TS 38.331 [9]. A UE supporting this feature shall also indicate the support of condHandover-r16 for NTN bands and the support of nonTerrestrialNetwork-r17 . UE shall set the capability value consistently for all FDD-FR1 NTN bands. | Band | No | N/A | N/A | +| eventA4BasedCondHandoverNES-r18
Indicates whether the UE supports Event A4 based conditional handover for NES, i.e., CondEvent A4 as specified in TS 38.331 [9]. A UE supporting this feature shall also indicate the support of nesBasedCondHandoverWithDCI-r18 . UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands, all TDD-FR2-1 bands and all TDD-FR2-2 bands respectively. | Band | No | N/A | N/A | +| extendedCP
Indicates whether the UE supports 60 kHz subcarrier spacing with extended CP length for reception of PDCCH, and PDSCH, and transmission of PUCCH, PUSCH, and SRS. | Band | No | N/A | N/A | +| groupBeamReporting
Indicates whether UE supports RSRP reporting for the group of two reference signals. | Band | No | N/A | N/A | +| groupSINR-reporting-r16
Indicates whether UE supports group based L1-SINR reporting. UE indicates support of this feature shall indicate support of ssb-csirs-SINR-measurement-r16 . | Band | No | N/A | N/A | +| handoverUTRA-FDD-r16
Indicates whether the UE supports NR to UTRA-FDD CELL_DCH CS handover for the PCell on the band. It is mandatory to support both UTRA-FDD measurement and event B triggered reporting, and periodic UTRA-FDD measurement and reporting if the UE supports HO to UTRA-FDD. If this field is included, then UE shall support IMS voice over NR. UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands, all TDD-FR2-1 bands and all TDD-FR2-2 bands respectively. | Band | No | N/A | N/A | +| interCellCrossTRP-PDCCH-OrderCFRA-r18
Indicates whether the UE supports cross-TRP PDCCH order based on CFRA for inter-cell multi-DCI based mTRP. | Band | No | N/A | N/A | +| interSlotFreqHopInterSlotBundlingPUSCH-r17
Indicates whether the UE supports enhanced inter-slot frequency hopping with inter-slot bundling for PUSCH.

UE indicating support of this feature shall also indicate support of at least one of dmrs-BundlingPUSCH-RepTypeA-r17 , dmrs-BundlingPUSCH-RepTypeB-r17 or dmrs-BundlingPUSCH-multiSlot-r17 . | Band | No | N/A | N/A | +| interSlotFreqHopPUCCH-r17
Indicates whether the UE supports enhanced inter-slot frequency hopping for PUCCH repetitions with DMRS bundling.

UE indicating support of this feature shall also indicate support of dmrs-BundlingPUCCH-Rep-r17 . | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| intraCellCrossTRP-PDCCH-OrderCFRA-r18
Indicates whether the UE supports cross-TRP PDCCH order based on CFRA for intra-cell multi-DCI based mTRP. | Band | No | N/A | N/A | +| lowerMSD-r18
Indicates whether the UE supports lower maximum sensitivity degradation when the band is the victim band with sensitivity degradation as specified in TS 38.101-1 [2]. The victim band and associated aggressor band(s) are within at least one of inter-band CA or EN-DC band combinations supported by the UE.
This feature includes following parameters:
  • - aggressorband1-r18 indicates the aggressor band which causes sensitivity degradation to the victim band.
  • - aggressorband2-r18 indicates the additional aggressor band only when the sensitivity degradation to the victim band is caused by IMD of another two bands, i.e. aggressorband1-r18 and aggressorband2-r18 together.
  • - msd-Type-r18 indicates the MSD type, including harmonic, harmonic mixing, cross band isolation, IMD2, IMD3, IMD4, IMD5 and 'all'. Value 'all' indicates the MSD capability class is applicable for all MSD types defined in this release, which are applicable to the associated victim band/aggressor band(s).
  • - msd-PowerClass-r18 indicates the applicable power class for the lower MSD capability class reported in msd-Class-r18.
  • - msd-Class-r18 indicates the lower MSD capability class as specified in 7.3A.7 in TS 38.101-1 [2].
The victim band and aggressor band(s) only consist of the bands requested by the network in frequencyBandListFilter . | Band | No | N/A | FR1 only | +| maxDurationDMRS-Bundling-r17
Indicates whether the UE supports the maximum duration during which UE is able to maintain power consistency and phase continuity to support DM-RS bundling for PUSCH/PUCCH.

NOTE: DM-RS bundling is only applicable for UL transmissions with pi/2 BPSK, BPSK, and QPSK modulation orders for the corresponding physical channels. | Band | No | N/A | N/A | +| maxMIMO-LayersForMulti-DCI-mTRP-r16
Indicates the interpretation of maxNumberMIMO-LayersPDSCH for multi-DCI based mTRP. If this field is included, maxNumberMIMO-LayersPDSCH is interpreted as the maximum number of layers per PDSCH for multi-DCI multi-TRP operation. If this field is not included, maxNumberMIMO-LayersPDSCH is interpreted as the maximum number of layers across two PDSCHs if having at least one RE overlapped, for multi-DCI multi-TRP operation. The UE that indicates support of this feature shall support overlapPDSCHsFullyFreqTime-r16 .

NOTE 1: For data rate calculation in clause 4.1.2, if this feature is indicated, each multi-DCI based multi-TRP CC is counted two times toward J. | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| max-HARQ-ProcessNumber-r17
Indicates the maximal supported HARQ process numbers for UL and for DL respectively. For each value of max-HARQ-ProcessNumber-r17 , value u16d32 indicates the maximal supported HARQ process number is 16 for UL and 32 for DL, value u32d16 indicates the maximal supported HARQ process number is 32 for UL and 16 for DL, value u32d32 indicates the maximal supported HARQ process number is 32 for UL and 32 for DL. This field is only applicable for bands in Table 5.2.2-1 in TS 38.101-5 [34] and HAPS operation bands in clause 5.2 of TS 38.104 [35]. | Band | No | N/A | N/A | +| maxNumberPUSCH-TypeA-Repetition-r17
Indicates whether the UE supports the increased maximum number of PUSCH Type A repetitions to 32.

A UE that indicates support of this feature shall support type1-PUSCH-RepetitionMultiSlots , type2-PUSCH-RepetitionMultiSlots , pusch-RepetitionTypeA-r16 or pusch-RepetitionTypeA-v16c0 .

NOTE: For DG PUSCH, the number of repetitions is indicated in a TDRA list. A row index of the TDRA list is indicated by a DCI. For Type 1 CG PUSCH, the number of repetitions is indicated by repK-v1710 . For Type 2 CG PUSCH, the number of repetitions is indicated in a TDRA list or by repK-v1710 . | Band | No | N/A | N/A | +| mux-HARQ-ACK-DiffPriorities-r17
Indicates whether the UE supports HARQ-ACK with different priorities multiplexing on a PUCCH/PUSCH, comprised of the following functional components:
  • - Supports multiplexing a high-priority HARQ-ACK and a low-priority HARQ-ACK into a PUCCH. Supports separate coding for the two HARQ-ACKs;
  • - Supports multiplexing a low-priority HARQ-ACK, a high-priority HARQ-ACK and a high-priority SR into a PUCCH;
  • - Supports multiplexing a low-priority HARQ-ACK in a high-priority PUSCH (conveying UL-SCH only). Supports separate beta_offset values for this priority combination;
  • - Supports multiplexing a high-priority HARQ-ACK in a low-priority PUSCH (conveying UL-SCH only). Supports separate beta_offset values for this priority combination;
  • - Supports multiplexing a low-priority HARQ-ACK, a high-priority PUSCH, a high-priority HARQ-ACK and/or CSI;
  • - Supports multiplexing a high-priority HARQ-ACK, a low-priority PUSCH, a low-priority HARQ-ACK and/or CSI.
The UE indicating support of this feature shall also indicate the support of twoHARQ-ACK-Codebook-type1-r16 . | Band | No | N/A | N/A | +| jointConfigDMRSPortDynamicSwitching-r18
Indicates whether the UE supports joint configuration of DMRS ports and dynamic switching between DFT-S-OFDM and CP-OFDM for PUSCH.
A UE supporting this feature shall also indicate the support of FG40-4-6 or 40-4-6a, and FG54-3. | Band | No | N/A | N/A | +| jointReleaseConfiguredGrantType2-r16
Indicates whether the UE supports joint release in a DCI for two or more configured grant Type 2 configurations for a given BWP of a serving cell. The UE can include this feature only if the UE indicates support of activeConfiguredGrant-r16 . | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| jointReleaseSPS-r16
Indicates whether the UE supports joint release in a DCI for two or more SPS configurations for a given BWP of a serving cell. The UE can include this feature only if the UE indicates support of sps-r16 . | Band | No | N/A | N/A | +| k1-RangeExtension-r17
Indicates whether the UE supports extended K1 value range of (0..31) for unpaired spectrum. This field is only applicable for bands in Table 5.2.2-1 in TS 38.101-5 [34] and HAPS operation bands in clause 5.2 of TS 38.104 [35]. | Band | No | N/A | N/A | +| locationBasedCondHandover-r17
Indicates whether the UE supports location based conditional handover, i.e., CondEvent D1 as specified in TS 38.331 [9]. A UE supporting this feature shall also indicate the support of condHandover-r16 for NTN bands and the support of nonTerrestrialNetwork-r17 . UE shall set the capability value consistently for all FDD-FR1 NTN bands. | Band | No | N/A | N/A | +| locationBasedCondHandoverATG-r18
Indicates whether the UE supports location based conditional handover, i.e., CondEvent D1 , CondEvent A3 , CondEvent A4 and CondEvent A5 as specified in TS 38.331 [9]. A UE supporting this feature shall also indicate the support of condHandover-r16 for bands as specified for ATG in clause 5.2J of TS 38.101-1 [2] and the support of airToGroundNetwork-r18 . UE shall set the capability value consistently for all bands as specified for ATG in clause 5.2J of TS 38.101-1 [2]. | Band | No | N/A | FR1 only | +| locationBasedCondHandoverEMC-r18
Indicates whether the UE supports location based conditional handover for an NTN Earth-moving system, i.e. condEventD2 as specified in TS 38.331 [9].
A UE supporting this feature shall also indicate the support of condHandover-r16 for NTN bands and the support of nonTerrestrialNetwork-r17 . UE shall set the capability value consistently for all FDD-FR1 NTN bands. | Band | No | N/A | N/A | +| lowPAPR-DMRS-PDSCH-r16
Indicates whether the UE supports low PAPR DMRS for PDSCH. | Band | No | N/A | N/A | +| lowPAPR-DMRS-PUCCH-r16
Indicates whether the UE supports low PAPR DMRS for PUCCH format 3 and format 4 with transform precoding and with pi/2 BPSK modulation. UE indicates support of this feature shall indicate support of pucch-F3-4-HalfPi-BPSK and any combination of support of pucch-F3-WithFH , pucch-F4-WithFH and pucch-F1-3-4WithoutFH . It is mandatory with capability signalling. | Band | Yes | N/A | N/A | +| lowPAPR-DMRS-PUSCHwithoutPrecoding-r16
Indicates whether the UE supports low PAPR DMRS for PUSCH without transform precoding. | Band | No | N/A | N/A | +| lowPAPR-DMRS-PUSCHwithPrecoding-r16
Indicates whether the UE supports low PAPR DMRS for PUSCH with transform precoding and with pi/2 BPSK modulation. It is mandatory with capability signalling. UE indicates support of this feature shall indicate support of pusch-HalfPi-BPSK . | Band | Yes | N/A | N/A | +| maxDynamicSlotRepetitionForSPS-Multicast-r17
Indicates maximum number of dynamic slot-level repetitions for SPS group-common PDSCH for multicast. For TN, the UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands and all TDD-FR2 bands, associated with supported shared and non-shared spectrum respectively. For NTN, UE shall set the capability value consistently for all FDD-FR1 NTN bands.

A UE that indicates support of this feature shall indicate support of sps-Multicast-r17 . | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| maxModulationOrderForMulticast-r17
Defines the maximal modulation order for multicast PDSCH. If not reported, UE supports the same modulation order as unicast.
  • - For FR1, up to 1024QAM is supported.
  • - For FR2, up to 256QAM is supported.
A UE supporting this feature shall also indicate support of dynamicMulticastPCell-r17 .

NOTE: A UE shall support the corresponding mandatory maximum modulation for unicast. | Band | No | N/A | N/A | +| maxNumberActivatedTCI-States-r16
Indicates maximum number of activated TCI states. This capability signalling includes the following:
  • - maxNumberPerCORESET-Pool-r16 indicates maximal number of activated TCI states per CORESETPoolIndex per BWP per CC including data and control
  • - maxTotalNumberAcrossCORESET-Pool-r16 indicates maximal total number of activated TCI states across CORESETPoolIndex per BWP per CC including data and control
The UE that indicates support of this feature shall support multiDCI-MultiTRP-r16 . | Band | No | N/A | N/A | +| maxNumberCSI-RS-BFD
Indicates maximal number of CSI-RS resources across all CCs, and across MCG and SCG in case of NR-DC, for UE to monitor PDCCH quality. In this release, the maximum value that can be signalled is 16. If the UE includes the field in an FR1 band, it shall set the same value in all FR1 bands. If the UE includes the field in an FR2 band, it shall set the same value in all FR2 bands. The UE supports a total number of resources equal to the maximum of the FR1 and FR2 value, but no more than the FR1 value across all FR1 serving cells and no more than the FR2 value across all FR2 serving cells. It is mandatory with capability signalling for FR2 and optional for FR1. | Band | CY | N/A | N/A | +| maxNumberCSI-RS-SSB-CBD
Defines maximal number of different CSI-RS [and/or SSB] resources across all CCs, and across MCG and SCG in case of NR-DC, for new beam identifications. In this release, the maximum value that can be signalled is 128. If the UE includes the field in an FR1 band, it shall set the same value in all FR1 bands. If the UE includes the field in an FR2 band, it shall set the same value in all FR2 bands. The UE supports a total number of resources equal to the maximum of the FR1 and FR2 value, but no more than the FR1 value across all FR1 serving cells and no more than the FR2 value across all FR2 serving cells. It is mandatory with capability signalling for FR2 and optional for FR1. The UE is mandated to report at least 32 for FR2. | Band | CY | N/A | N/A | +| maxNumberG-CS-RNTI-r17
Defines maximum number of G-CS-RNTIs for SPS multicast. For TN, the UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands and all TDD-FR2 bands, associated with supported shared and non-shared spectrum respectively. For NTN, UE shall set the capability value consistently for all FDD-FR1 NTN bands.

A UE supporting this feature shall also indicate support of sps-Multicast-r17 . | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| maxNumberG-RNTI-r17
Defines maximum number of G-RNTIs for multicast in RRC_CONNECTED. For TN, the UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands and all TDD-FR2 bands, associated with supported shared and non-shared spectrum respectively. For NTN, UE shall set the capability value consistently for all FDD-FR1 NTN bands.

A UE supporting this feature shall also indicate support of dynamicMulticastPCell-r17 .
For the UE indicating support of multicastInactive-r18 , this capability is also applicable to multicast reception in RRC_INACTIVE, as specified in TS 38.331 [9]. | Band | No | N/A | N/A | +| maxNumberNonGroupBeamReporting
Defines support of non-group based RSRP reporting using N_max RSRP values reported. | Band | Yes | N/A | N/A | +| maxNumberRxBeam, maxNumberRxBeam-v1720
Defines whether UE supports receive beamforming switching using NZP CSI-RS resource. UE shall indicate a single value for the preferred number of NZP CSI-RS resource repetitions per CSI-RS resource set. Support of Rx beam switching is mandatory for FR2. | Band | CY | N/A | N/A | +| maxNumberRxBTxBBeamSwitchDL, maxNumberRxBTxBBeamSwitchDL-v1710
Defines the number of Tx and Rx beam changes UE can perform on this band within a slot. UE shall report one value per each subcarrier spacing supported by the UE. In this release, the number of Tx and Rx beam changes for scs-15kHz and scs-30kHz are not included. | Band | No | N/A | FR2 only | +| maxNumberSCellBFR-r16
Defines the maximum number of SCells configured for SCell beam failure recovery simultaneously. The UE indicating support of this also indicates the capabilities of maxNumberCSI-RS-BFD , maxNumberSSB-BFD and maxNumberCSI-RS-SSB-CBD . | Band | No | N/A | N/A | +| maxNumberSSB-BFD
Defines maximal number of different SSBs across all CCs, and across MCG and SCG in case of NR-DC, for UE to monitor PDCCH quality. In this release, the maximum value that can be signalled is 16. If the UE includes the field in an FR1 band, it shall set the same value in all FR1 bands. If the UE includes the field in an FR2 band, it shall set the same value in all FR2 bands. The UE supports a total number of resources equal to the maximum of the FR1 and FR2 value, but no more than the FR1 value across all FR1 serving cells and no more than the FR2 value across all FR2 serving cells. It is mandatory with capability signalling for FR2 and optional for FR1. | Band | CY | N/A | N/A | +| maxNumber-LEO-SatellitesPerCarrier-r17
Indicates the number of target LEO satellites the UE can monitor per carrier. For serving carrier, the number of target LEO satellites also includes the serving satellite. If this field is not included, the number of target satellites UE can monitor per carrier is 2. The value shall be larger than or equal to the reported value on maxNumber-NGSO-SatellitesWithinOneSMTC-r17 . | Band | No | FDD only | FR1 only | +| maxNumber-NGSO-SatellitesWithinOneSMTC-r17
Indicates the number of different NGSO satellites for target cells that the UE supports of simultaneous measurements within a SMTC with value n1 corresponds to 1, value n2 corresponds to 2 and so on. | Band | No | FDD only | FR1 only | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| maxOutputPowerATG-r18
Indicates the maximum output power rating at maximum modulation order and full RB allocation as specified in clause 6.2J of TS 38.101-1 [2]. Value 1 indicates 23dBm, value 2 indicates 24dBm and so on. If present, the ue-PowerClass is not included, and default UE power class is not applicable. The UE indicating support of this feature shall also indicate support of airToGroundNetwork-r18 . This field is only applicable for bands as specified for ATG in clause 5.2J of TS 38.101-1 [2]. | Band | CY | N/A | FR1 only | +| maxUplinkDutyCycle-PC2-FR1
Indicates the maximum percentage of symbols during a certain evaluation period that can be scheduled for uplink transmission to ensure compliance with applicable electromagnetic energy absorption requirements provided by regulatory bodies. This field is applicable for FR1 power class 2 UE and also applicable for FR1 power class 1.5 UE as specified in clause 6.2.1 of TS 38.101-1 [2]. If the field and maxUplinkDutyCycle-PC1dot5-MPE-FR1-r16 are both absent, 50% shall be applied as the upper limit of the UL duty cycle for power class 2. Value n60 corresponds to 60%, value n70 corresponds to 70% and so on. This capability is not applicable to IAB-MT. | Band | No | N/A | FR1 only | +| maxUplinkDutyCycle-FR2
Indicates the maximum percentage of symbols during 1s that can be scheduled for uplink transmission at the UE maximum transmission power, so as to ensure compliance with applicable electromagnetic power density exposure requirements provided by regulatory bodies. This field is applicable for all power classes UE in FR2 as specified in TS 38.101-2 [3]. Value n15 corresponds to 15%, value n20 corresponds to 20% and so on. If the field is absent or the percentage of uplink symbols transmitted within any 1s evaluation period is larger than maxUplinkDutyCycle-FR2 , the UE behaviour is specified in TS 38.101-2 [3]. This capability is not applicable to IAB-MT. | Band | No | N/A | FR2 only | +| maxUplinkDutyCycle-PC1dot5-MPE-FR1-r16
Indicates the maximum percentage of symbols during a certain evaluation period that can be scheduled for uplink transmission to ensure compliance with applicable electromagnetic energy absorption requirements provided by regulatory bodies. This field is only applicable for FR1 power class 1.5 UE as specified in clause 6.2.1 of TS 38.101-1 [2]. If the field and maxUplinkDutyCycle-PC2-FR1 are both absent, 25% shall be applied as the upper limit of the UL duty cycle for power class 1.5. | Band | No | N/A | FR1 only | +| mn-InitiatedCondPSCellChangeNRDC-r17
Indicates whether the UE supports MN initiated conditional PSCell change in NR-DC, which is configured by NR conditionalReconfiguration using MN configured measurement as triggering condition. The UE supporting this feature shall also support 2 trigger events for same execution condition in MN initiated conditional PSCell change in NR-DC. UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands and all TDD-FR2 bands respectively. | Band | No | N/A | N/A | +| modifiedMPR-Behaviour
Indicates whether UE supports modified MPR behaviour defined in TS 38.101-1 [2], TS 38.101-2 [3], and TS 38.101-5 [34]. | Band | No | N/A | N/A | +| mpr-PowerBoost-FR2-r16
Indicates whether UE supports uplink transmission power boost by suspension of in-band emission (IBE) requirements as specified in TS 38.101-2 [3]. | Band | No | TDD only | FR2 only | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| mpe-Mitigation-r17
Indicates the support of enhanced PHR reporting which includes pairs of (P-MPR, SSBR/CRI).
This feature also includes following parameters:
  • - maxNumP-MPR-RI-pairs-r17 indicates the maximum number of reported P-MPR and SSBR/CRI pairs;
  • - maxNumConfRS-r17 indicates the maximum number of candidate RS(s) configured in a RRC pool for MPE mitigation.
NOTE: maxNumConfRS-r17 is also counted in maxTotalResourcesForOneFreqRange-r16 /
maxTotalResourcesForAcrossFreqRanges-r16 . | Band | No | N/A | FR2 only | +| mt-CG-SDT-r18
Indicates whether the UE supports initiating MT-SDT procedure over configured grant type 1, as specified in TS 38.331 [9]. Except for NTN bands, UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands and all TDD-FR2 bands respectively. For NTN, UE shall set the capability value consistently for all FDD-FR1 NTN bands.
Except for NTN, a UE supporting this feature shall also support mt-SDT-r18 . For NTN, a UE supporting this feature shall also support mt-SDT-NTN-r18 . | Band | No | N/A | N/A | +| mTRP-PUCCH-InterSlot-r17
Indicates whether the UE supports the following features:
  • - support of PUCCH repetition scheme 1 (inter-slot repetition) with sequential mapping for repetitions larger than 2 and with cyclic mapping for 2 repetitions.
  • - support of up to two PUCCH power control parameter sets/spatial relation information per PUCCH resource. The power control parameter sets only apply to FR1 and spatial relation information only applies to FR2.
  • - supported PUCCH formats for PUCCH repetition scheme 1.
| Band | No | N/A | N/A | +| mTRP-PUCCH-CyclicMapping-r17
Indicates whether the UE supports cyclic mapping for beam mapping/power control parameter set mapping for PUCCH repetitions scheme 1 and/or 3 when the number of repetitions is larger than 2.
The UE that indicates support of this feature shall also indicate support of mTRP-PUCCH-InterSlot-r17 . | Band | No | N/A | N/A | +| mTRP-PUCCH-SecondTPC-r17
Indicates whether the UE supports second TPC field for per TRP closed-loop power control for PUCCH with DCI formats 1_1 / 1_2.
The UE that indicates support of this feature shall also indicate support of mTRP-PUCCH-InterSlot-r17 . | Band | No | N/A | N/A | +| mTRP-PUSCH-twoCSI-RS-r17
Indicates whether the UE supports up to two NZP CSI-RS resources associated with the two SRS resource sets for non-codebook-based mTRP PUSCH.
The UE that indicates support of this feature shall also indicate support of srs-AssocCSI-RS , csi-RS-IM-ReceptionForFeedbackPerBandComb and mTRP-PUSCH-RepetitionTypeA-r17 . | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| mTRP-BFR-twoBFD-RS-Set-r17
Indicates whether the UE supports mTRP BFR based on two BFD-RS sets. The capability signalling comprises the following parameters:
  • - maxBFD-RS-resourcesPerSetPerBWP-r17 indicates the maximum number of supported measured BFD-RS resources per set per BWP.
  • - maxBFR-r17 indicates the maximum number of CCs per band configured with BFR (including spCell/SCell/MTRP BFR).
  • - maxBFD-RS-resourcesAcrossSetsPerBWP-r17 indicates the supported maximum number of measured BFD-RS resources across two BFD-RS sets per BWP.
maxBFD-RS-resourcesAcrossSetsPerBWP-r17 is also counted in maxTotalResourcesForOneFreqRange-r16 and maxTotalResourcesForAcrossFreqRanges-r16 . | Band | No | N/A | N/A | +| mTRP-BFR-PUCCH-SR-perCG-r17
Indicates the maximum number of supported PUCCH-SR resources for MTRP BFR per cell group. A UE that supports mTRP-BFR-twoBFD-RS-Set-r17 shall indicate support of this feature with at least 1 PUCCH-SR resources for MTRP BFR per cell group.

UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands, all TDD-FR2-1 bands and all TDD-FR2-2 bands respectively. | Band | No | N/A | N/A | +| mTRP-BFR-association-PUCCH-SR-r17
Indicates whether the UE supports association between a BFD-RS resource set on SpCell and a PUCCH SR resource.
The UE indicating support of this feature shall support mTRP-BFR-PUCCH-SR-perCG-r17 . UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands, all TDD-FR2-1 bands and all TDD-FR2-2 bands respectively. | Band | No | N/A | N/A | +| mTRP-BFD-RS-MAC-CE-r17
Indicates the support of MAC-CE based update of explicit BFD-RS for mTRP BFR with maximum number of configured candidate BFD-RS per BWP for MAC-CE based update.
The UE indicating support of this feature shall also indicate the support of mTRP-BFR-twoBFD-RS-Set-r17 . | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| mTRP-CSI-EnhancementPerBand-r17
Indicates support of CSI enhancements for multi-TRP including support of NZP CSI-RS resource pairs used as CMR (channel measurement resource) pairs for NCJT measurement hypothesis with N=1.
This feature also includes following parameters:
  • - maxNumNZP-CSI-RS-r17 indicates the maximum number of NZP CSI-RS resources in one CSI-RS resource set: Ks,max
  • - cSI-Report-mode-r17 indicates the CSI report mode selection. Mode1 indicates mode 1 with X=0, mode2 indicates mode 2, both indicate the support of both mode 1 with X=0 and mode 2.
  • - A list of supported combinations, up to 16, across all CCs simultaneously, where each combination includes:
    • - maxNumTx-Ports-r17 indicates the maximum number of Tx ports in one NZP CSI-RS resource associated with an NCJT measurement hypothesis
    • - maxTotalNumCMR-r17 indicates the maximum total number of CMRs for NCJT measurement
    • - maxTotalNumTx-PortsNZP-CSI-RS-r17 indicates the maximum total number of Tx ports of NZP CSI-RS resources associated with NCJT measurement hypotheses
    • - codebookModeNCJT-r17 indicates the supported codebook modes for NCJT CSI.
| Band | No | N/A | N/A | +| mTRP-CSI-numCPU-r17
Indicates the number of CSI processing units (CPUs) occupied by a pair of CMRs for NCJT CSI hypotheses. Maximum number of CPUs is reported in csi-ReportFramework .
The UE indicating support of this feature shall also indicate the support of mTRP-CSI-EnhancementPerBand-r17 . | Band | No | N/A | N/A | +| mTRP-CSI-additionalCSI-r17
Indicates the maximum value of numberOfSingleTRP-CSI-Mode1 .

The UE indicating support of this feature shall also indicate 'mode1' or 'both' in cSI-Report-mode-r17 of mTRP-CSI-EnhancementPerBand-r17 . | Band | No | N/A | N/A | +| mTRP-CSI-N-Max2-r17
Indicates the support of maximum number of CMR pairs Nmax=2 configured in NZP-CSI-RS-ResourceSet for a given CSI report setting.

The UE indicating support of this feature shall also indicate the support of mTRP-CSI-EnhancementPerBand-r17 . | Band | No | N/A | N/A | +| mTRP-CSI-CMR-r17
Indicates the support of a NZP CSI-RS resource referred by both a CMR pair configured for Rel-17 Multi-TRP CSI enhancement and a single CMR configured for Single-TRP measurement in a CSI reporting setting.

The UE indicating support of this feature shall also indicate the support of mTRP-CSI-EnhancementPerBand-r17 . | Band | No | N/A | FR2 only | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| mTRP-PDCCH-individual-r17
Indicates the support of monitoring of individual candidates when one of the linked PDCCH candidates uses the same set of CCEs as an individual (unlinked) PDCCH candidate, and they both are associated with the same DCI size, scrambling, and CORESET.

The UE indicating support of this feature shall also indicate support of mTRP-PDCCH-Repetition-r17 . | Band | No | N/A | N/A | +| mTRP-PDCCH-anySpan-3Symbols-r17
Indicates support of PDCCH repetition for PDCCH monitoring on any span of up to 3 consecutive OFDM symbols of a slot. It is applicable to 15kHz SCS only.
The UE indicating support of this feature shall also indicate support of pdcchMonitoringSingleOccasion and mTRP-PDCCH-Repetition-r17 . | Band | No | N/A | FR1 only | +| mTRP-PDCCH-TwoQCL-TypeD-r17
Indicates the support of determining two QCL-TypeD for time-domain overlapping CORESETs in the same CC or for intra-band CA when UE is configured with PDCCH repetition.
The UE indicating support of this feature shall also indicate support of mTRP-PDCCH-Repetition-r17 . | Band | No | N/A | FR2 only | +| mTRP-PUSCH-CSI-RS-r17
Indicates the support of CSI-RS processing framework for SRS with two associated CSI-RS resources.

This feature also includes following parameters:
  • - maxNumPeriodicSRS-r17 indicates the maximum number of periodic SRS resources associated with first and second CSI-RS per BWP.
  • - maxNumAperiodicSRS-r17 indicates the maximum number of aperiodic SRS resources associated with first and second CSI-RS per BWP.
  • - maxNumSP-SRS-r17 indicates the maximum number of semi-persistent SRS resources associated with first and second CSI-RS per BWP.
  • - numSRS-ResourcePerCC-r17: UE can process Y SRS resources associated with first and second CSI-RS resources simultaneously in a CC. Includes Periodic/Semi-Persistent/Aperiodic SRS.
  • - numSRS-ResourceNonCodebook-r17: UE can process up to X CSI-RS resources associated with SRS for non-codebook based transmission simultaneously.
The UE indicating support of this feature shall also indicate the support of mTRP-PUSCH-twoCSI-RS-r17 . | Band | No | N/A | N/A | +| mTRP-PUSCH-cyclicMapping-r17
Indicates the support of cyclic mapping when the number of repetitions is larger than 2 with repetition type.

The UE indicating support of this feature shall also indicate the support of mTRP-PUSCH-TypeA-CB-r17 or mTRP-PUSCH-RepetitionTypeA-r17 . | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| mTRP-PUSCH-secondTPC-r17
Indicates the support of second TPC field for per TRP closed-loop power control for PUSCH with DCI formats 0_1 and 0_2.

The UE indicating support of this feature shall also indicate the support of mTRP-PUSCH-TypeA-CB-r17 or mTRP-PUSCH-RepetitionTypeA-r17 . | Band | No | N/A | N/A | +| mTRP-PUSCH-twoPHR-Reporting-r17
Indicates the support of PHR reporting related to M-TRP PUSCH repetition (calculate two PHRs (at least corresponding to the CC that applies m-TRP PUSCH repetitions), each associated with a first PUSCH occasion corresponding to each SRS resource set, and report two PHRs).
The UE indicating support of this feature shall also indicate the support of mTRP-PUSCH-TypeA-CB-r17 or mTRP-PUSCH-RepetitionTypeA-r17 . | Band | No | N/A | N/A | +| mTRP-PUSCH-A-CSI-r17
Indicates the support of A-CSI report on two PUSCH repetitions.

The UE indicating support of this feature shall also indicate the support of mTRP-PUSCH-TypeA-CB-r17 or mTRP-PUSCH-RepetitionTypeA-r17 . | Band | No | N/A | N/A | +| mTRP-PUSCH-SP-CSI-r17
Indicates the support of SP-CSI report on two PUSCH repetitions.

The UE indicating support of this feature shall also indicate the support of mTRP-PUSCH-TypeA-CB-r17 or mTRP-PUSCH-RepetitionTypeA-r17 . | Band | No | N/A | N/A | +| mTRP-PUSCH-CG-r17
Indicates the support of CG PUSCH transmission towards M-TRPs using a single CG configuration. The UE uses same beam mapping principals as dynamic grant PUSCH repetition scheme.

The UE indicating support of this feature shall also indicate the support of mTRP-PUSCH-TypeA-CB-r17 or mTRP-PUSCH-RepetitionTypeA-r17 . | Band | No | N/A | N/A | +| mTRP-PUCCH-MAC-CE-r17
Indicates the support of updating two Spatial Relation Info's and two sets of power control parameters for a group of PUCCH resources in a CC by MAC-CE.

The UE indicates support of this feature shall also indicate support of mTRP-PUCCH-InterSlot-r17 . | Band | No | N/A | N/A | +| mTRP-PUCCH-maxNum-PC-FR1-r17
Indicates the maximum number of power control parameter sets configured for multi-TRP PUCCH repetition in FR1.

The UE indicating support of this feature shall also indicate the support of mTRP-PUCCH-InterSlot-r17 . | Band | No | N/A | FR1 only | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| mTRP-inter-Cell-r17
Indicates the support of RRC configuration of additional PCI different from serving cell associated with the TCI state and/or QCL-info.
This feature also includes following parameters:
  • - maxNumAdditionalPCI-Case1-r17 indicates the maximum number of configured additional PCIs per CC is X1 (Case 1) when each configuration of SSB time domain positions and periodicity of the additional PCIs is the same as SSB time domain positions and periodicity of the serving cell PCI.
  • - maxNumAdditionalPCI-Case2-r17 indicates the maximum number of configured additional PCIs per CC is X2 (Case 2) when the configurations of SSB time domain positions and periodicity of the additional PCIs is not according to Case 1.
The UE indicating support of this feature shall also indicate the support of multiDCI-MultiTRP-r16 . | Band | No | N/A | N/A | +| mTRP-GroupBasedL1-RSRP-r17
Indicates the support of group based L1-RSRP reporting enhancements.
This feature also includes following parameters:
  • - maxNumBeamGroups-r17 indicates the maximum number N of beam groups (M=2 beams per beam group) in a single L1-RSRP reporting instance based on measurement on two CMR resource sets.
  • - maxNumRS-WithinSlot-r17 indicates the maximum number of SSB and CSI-RS resources for measurement in both CMR sets within a slot across all CCs.
  • - maxNumRS-AcrossSlot-r17 indicates the maximum number of configured SSB and CSI-RS resources for measurement in both CMR sets across all CCs.
maxNumRS-WithinSlot-r17 and maxNumRS-AcrossSlot-r17 are also counted in maxTotalResourcesForOneFreqRange-r16 and maxTotalResourcesForAcrossFreqRanges-r16 . | Band | No | N/A | N/A | +| multiPDSCH-SingleDCI-FR2-1-SCS-120kHz-r17
Indicates whether the UE supports multi-PDSCH scheduling by single DCI for the operation with 120kHz SCS in FR2-1 and HARQ enhancements for both type 1 and type 2 HARQ codebook. | Band | No | N/A | N/A | +| multiPUCCH-HARQ-ACK-ForMulticastUnicast-r17
Indicates whether the UE supports two non-overlapping slot-based PUCCHs for ACK/NACK based HARQ-ACK feedback for multicast or for unicast and multicast with different priorities in a slot.

For TN, the UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands and all TDD-FR2 bands, associated with supported shared and non-shared spectrum respectively. For NTN, UE shall set the capability value consistently for all FDD-FR1 NTN bands.

A UE supporting this feature shall also indicate support of priorityIndicatorInDCI-Multicast-r17 and twoHARQ-ACK-CodebookForUnicastAndMulticast-r17 . | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| multiPUSCH-ActiveConfiguredGrant-r18
Indicates whether the UE supports multiple active multi-PUSCHs configured grant configurations for a BWP of a serving cell.
This feature also includes following parameters:
  • - maxNumberConfigsPerBWP indicates the supported maximum number of configured/active configured grant configurations in a BWP of a serving cell.
  • - maxNumberConfigsAllCC-FR1 indicates the supported maximum number of configured/active configured grant configurations across all serving cells, and across MCG and SCG in case of NR-DC in FR1.
  • - maxNumberConfigsAllCC-FR2 indicates the supported maximum number of configured/active configured grant configurations across all serving cells, and across MCG and SCG in case of NR-DC in FR2.
A UE supporting this feature shall also indicate support of multiPUSCH-CG-r18 .

When UE supports both activeConfiguredGrant-r16 and multiPUSCH-ActiveConfiguredGrant-r18 , the total number which can be configured for CG of activeConfiguredGrant-r16 and multi-PUSCH CG should not exceed the value reported by activeConfiguredGrant-r16 .

For all the reported bands in FR1, a same value is reported for maxNumberConfigsAllCC . For all the reported bands in FR2, a same value is reported for maxNumberConfigsAllCC .

The total number of configured/active configured grant configurations across all serving cells in FR1 is no greater than maxNumberConfigsAllCC in FR1.

The total number of configured/active configured grant configurations across all serving cells in FR2 is no greater than maxNumberConfigsAllCC in FR2.

If there are some serving cell(s) in FR1 and some serving cell(s) in FR2, the total number of configured/active configured grant configurations across all serving cells is no greater than $\max(\max\text{NumberConfigsAllCC-FR1}, \max\text{NumberConfigsAllCC-FR2})$ . | Band | No | N/A | N/A | +| multiPUSCH-CG-r18
Indicates whether the UE supports multi-PUSCHs for configured grant by indicating whether the UE supports the determination of time-domain resource allocation for CG-PUSCHs associated to a multi-PUSCHs CG and also the maximum supported number of consecutive slots configured for CG-PUSCH TOs in one CG period.
This feature also includes following parameters:
  • - n16 indicates the maximum supported number of consecutive slots configured for CG-PUSCH TOs in one CG period is 16.
  • - n32 indicates the maximum supported number of consecutive slots configured for CG-PUSCH TOs in one CG period is 32.
A UE supporting this feature shall also indicate support of at least one of configuredUL-GrantType1 , configuredUL-GrantType1-v1650 , configuredUL-GrantType2 , and configuredUL-GrantType2-v1650 . | Band | No | N/A | N/A | +| multiPUSCH-SingleDCI-FR2-1-SCS-120kHz-r17
Indicates whether the UE supports multi-PUSCH scheduling by single DCI for the operation with 120kHz SCS in FR2-1 with non-contiguous allocation. | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| multiPUSCH-SingleDCI-NonConsSlots-r18
Indicates support of Multi-PUSCH scheduling by single DCI format 0_1 for the operation with non-contiguous allocation.
A UE supporting this feature shall also indicate support of multiPUSCH-UL-grant-r16 . | Band | No | N/A | FR1 only | +| multipleRateMatchingEUTRA-CRS-r16
Indicates whether the UE supports multiple E-UTRA CRS rate matching patterns, which is supported only for FR1. The capability signalling comprises the following parameters:
  • - maxNumberPatterns-r16 indicates the maximum number of LTE-CRS rate matching patterns in total within a NR carrier using 15 kHz SCS. The UE can report the value larger than 2 only if UE reports the value of maxNumberNon-OverlapPatterns-r16 is larger than 1.
  • - maxNumberNon-OverlapPatterns-r16 indicates the maximum number of LTE-CRS non-overlapping rate matching patterns within a NR carrier using 15 kHz SCS.
The UE can include this feature only if the UE indicates support of rateMatchingLTE-CRS . | Band | No | N/A | FR1 only | +| multipleTCI
Indicates whether UE supports more than one TCI state configurations per CORESET. UE is only required to track one active TCI state per CORESET. UE is required to support minimum between 64 and number of configured TCI states indicated by tcI-StatePDSCH . This field shall be set to supported . | Band | Yes | N/A | N/A | +| nack-OnlyFeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling NACK-only based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.
A UE supporting this feature shall also indicate support of nack-OnlyFeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| nack-OnlyFeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling NACK-only based HARQ-ACK feedback configured per G-CS-RNTI by RRC signalling via DCI format 4_2.

A UE that indicates support of this feature shall indicate support of nack-OnlyFeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ncd-SSB-BWP-Wor-r18
Indicates whether the UE supports RLM/BM/BFD and gapless L3 intra-frequency measurements based on NCD-SSB within active BWP. Bandwidth of UE-specific RRC configured BWP may not include bandwidth of the CORESET#0 (if CORESET#0 is present) and CD-SSB for PCell/PSCell (if configured) and bandwidth of the UE-specific RRC configured BWP may not include CD-SSB for Scell. NCD-SSB within the active DL BWP can be used as the QCL source for other reference signal. UE performs L3 intra-frequency measurements without gaps based on NCD-SSB, where the NCD-SSB is within the active DL BWP.
NOTE: this feature applies only to PCell.
It is not applicable to RedCap or eRedCap UEs. | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| nesBasedCondHandoverWithDCI-r18
Indicates whether the UE supports DCI-based enabling/disabling NES-specific CHO execution condition, i.e. NES-specific CHO execution condition based on source cell NES mode indicated via DCI format 2_9 as specified in TS 38.331 [9]. A UE supporting this feature shall also indicate the support of condHandover-r16 . UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands, all TDD-FR2-1 bands and all TDD-FR2-2 bands respectively. | Band | No | N/A | N/A | +| nes-CellDTX-DRX-r18
Indicates whether the UE supports cell DTX and/or DRX operation by RRC configuration. The supported number of cell DTX/DRX patterns per cell group is 2, regardless of each pattern is for cell DTX only, cell DRX only, or both. | Band | No | N/A | N/A | +| nes-CellDTX-DRX-DCI2-9-r18
Indicates whether the UE supports cell DTX/DRX configuration activation and deactivation via DCI 2_9.
A UE supporting this feature shall also indicate support of nes-CellDTX-DRX-r18 . | Band | No | N/A | N/A | +| nonGroupSINR-reporting-r16
Indicates N_max L1-SINR values reported when UE supports non-group based L1-SINR reporting. UE indicates support of this feature shall indicate support of ssb-csirs-SINR-measurement-r16 . | Band | No | N/A | N/A | +| nr-PDCCH-OverlapLTE-CRS-RE-r18
Indicates whether the UE supports reception of NR PDCCH candidates that overlap with LTE CRS REs within a NR carrier using 15 kHz SCS. The UE is provided with LTE CRS RM pattern by configuration of one CRS rate matching pattern via lte-CRS-ToMatchAround . NR PDCCH that overlaps with LTE CRS REs is in Type-1 CSS with dedicated RRC configuration, Type-3 CSS, and/or USS that are monitored within the first 3 OFDM symbols of a slot. This feature comprises following components:
  • - overlapInRE-r18 indicates reception of a NR PDCCH candidate in REs that overlap with LTE CRS: Value oneSymbolNoOverlap indicates when at least one symbol of the NR PDCCH candidate and the DMRS for demodulation of the NR PDCCH candidate is not overlapped with LTE CRS. Value someOrAllSymOverlap indicates when some or all of symbols of NR PDCCH candidate overlap with LTE CRS.
  • - overlapInSymbol-r18 indicates reception of NR PDCCH candidates that overlap with LTE CRS REs on the X-th symbols of an NR slot: Value symbol2 indicates only 2nd symbol, Value symbol1And2 indicates 1st and 2nd symbols;
The UE supporting this feature shall also indicate support of rateMatchingLTE-CRS .

NOTE: this feature is supported by UE performing channel estimation with a regular legacy DMRS pattern in frequency dimension, i.e., no change to UE assumption on PDCCH DMRS RE positions/pattern in a symbol that are used for the purpose of channel estimation. | Band | No | N/A | FR1 only | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| nr-PDCCH-OverlapLTE-CRS-RE-MultiPatterns-r18
Indicates whether the UE supports reception of NR PDCCH candidates in REs that overlap with LTE CRS when UE is provided with LTE CRS RM patterns by configuration of one or multiple non-overlapping CRS rate matching patterns via lte-CRS-PatternList1-r16 if the UE supports multipleRateMatchingEUTRA-CRS-r16 or lte-CRS-PatternList3-r18 if the UE supports nr-PDCCH-OverlapLTE-CRS-RE-MultiPatterns-r18 .
The UE supporting of this feature shall also indicate support of nr-PDCCH-OverlapLTE-CRS-RE-r18 and at least one of multipleRateMatchingEUTRA-CRS-r16 and twoRateMatchingEUTRA-CRS-patterns-3-4-r18 .

NOTE: the feature is supported by UE performing channel estimation with a regular legacy DMRS pattern in frequency dimension, i.e., no change to UE assumption on PDCCH DMRS RE positions/pattern in a symbol that are used for the purpose of channel estimation. | Band | No | N/A | FR1 only | +| nr-PDCCH-OverlapLTE-CRS-RE-Span-3-4-r18
Indicates whether the UE supports NR PDCCH that overlaps with LTE CRS REs is in Type-1 CSS with dedicated RRC configuration, Type-3 CSS, and/or USS that are monitored within a single span of 3 consecutive OFDM symbols that is within the first 4 OFDM symbols in a slot.
The UE supporting of this feature shall also indicate support of nr-PDCCH-OverlapLTE-CRS-RE-r18 and pdcch-MonitoringSingleSpanFirst4Sym-r16 . | Band | No | N/A | FR1 only | +| nr-UE-TxTEG-ID-MaxSupport-r17
Indicates the maximum number of UE TxTEG for SRS resource for positioning, which is supported and reported by UE for UL TDOA. The UE can include this field only if the UE supports srs-AllPosResources-r16 . | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| olpc-SRS-Pos-r16
Indicates whether the UE supports OLPC for SRS for positioning. The capability signalling comprises the following parameters.
  • - olpc-SRS-PosBasedOnPRS-Serving-r16 indicates whether the UE supports OLPC for SRS for positioning based on PRS from the serving cell in the same band. The UE can include this field only if the UE supports NR-DL-PRS-ProcessingCapability-r16 defined in TS 37.355 [22], and srs-PosResources-r16. Otherwise, the UE does not include this field;
  • - olpc-SRS-PosBasedOnSSB-Neigh-r16 indicates whether the UE supports OLPC for SRS for positioning based on SSB from the neighbouring cell in the same band. The UE can include this field only if the UE supports srs-PosResources-r16. Otherwise, the UE does not include this field;
  • - olpc-SRS-PosBasedOnPRS-Neigh-r16 indicates whether the UE supports OLPC for SRS for positioning based on PRS from the neighbouring cell in the same band. The UE can include this field only if the UE supports olpc-SRS-PosBasedOnPRS-Serving-r16. Otherwise, the UE does not include this field;
NOTE: A PRS from a PRS-only TP is treated as PRS from a non-serving cell.
  • - maxNumberPathLossEstimatePerServing-r16 indicates the maximum number of pathloss estimates that the UE can simultaneously maintain for all the SRS resource sets for positioning per serving cell in addition to the up to four pathloss estimates that the UE maintains per serving cell for the PUSCH/PUCCH/SRS transmissions. The UE shall include this field if the UE supports any of olpc-SRS-PosBasedOnPRS-Serving-r16, olpc-SRS-PosBasedOnSSB-Neigh-r16 and olpc-SRS-PosBasedOnPRS-Neigh-r16. Otherwise, the UE does not include this field.
| Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| olpc-SRS-PosRRC-Inactive-r17
Indicates whether the UE supports OLPC for SRS for positioning in RRC_INACTIVE. The capability signalling comprises the following parameters.
  • - olpc-SRS-PosBasedOnPRS-Serving-r16 indicates whether the UE supports OLPC for SRS for positioning based on PRS from the serving cell in the same band. The UE can include this field only if the UE supports NR-DL-PRS-ProcessingCapability-r16 defined in TS 37.355 [22], and srs-PosResourcesRRC-Inactive-r17. Otherwise, the UE does not include this field;
  • - olpc-SRS-PosBasedOnSSB-Neigh-r16 indicates whether the UE supports OLPC for SRS for positioning based on SSB from the neighbouring cell in the same band. The UE can include this field only if the UE supports srs-PosResourcesRRC-Inactive-r17. Otherwise, the UE does not include this field;
  • - olpc-SRS-PosBasedOnPRS-Neigh-r16 indicates whether the UE supports OLPC for SRS for positioning based on PRS from the neighbouring cell in the same band. The UE can include this field only if the UE supports olpc-SRS-PosBasedOnPRS-Serving-r16. Otherwise, the UE does not include this field;
NOTE: A PRS from a PRS-only TP is treated as PRS from a non-serving cell.
  • - maxNumberPathLossEstimatePerServing-r16 indicates the maximum number of pathloss estimates that the UE can simultaneously maintain for all the SRS resource sets for positioning per serving cell in addition to the up to four pathloss estimates that the UE maintains per serving cell for the PUSCH/PUCCH/SRS transmissions. The UE shall include this field if the UE supports any of olpc-SRS-PosBasedOnPRS-Serving-r16, olpc-SRS-PosBasedOnSSB-Neigh-r16 and olpc-SRS-PosBasedOnPRS-Neigh-r16. Otherwise, the UE does not include this field.
| Band | No | N/A | N/A | +| oneShotHARQ-feedbackPhy-Priority-r17
Indicates whether the UE supports transmission of type 3 HARQ-ACK codebook using the first or second PUCCH configuration based on PHY priority indication in the triggering DCI.
A UE supporting this feature shall also indicate support of oneShotHARQ-feedback-r16 and twoHARQ-ACK-Codebook-type1-r16 . | Band | No | N/A | N/A | +| oneShotHARQ-feedbackTriggeredByDCI-1-2-r17
Indicates whether the UE supports one-shot HARQ ACK feedback triggered by DCI format 1_2, comprised of the following functional components:
  • - Supports feedback of type 3 HARQ-ACK codebook, triggered by a DCI 1_2 scheduling a PDSCH;
  • - Supports feedback of type 3 HARQ-ACK codebook, triggered by a DCI 1_2 without scheduling a PDSCH using a reserved FDRA value.
A UE supporting this feature shall also indicate support of oneShotHARQ-feedback-r16 and dci-Format1-2And0-2-r16 . | Band | No | N/A | N/A | +| oneSlotPeriodicTRS-r16
Indicates whether the UE supports one-slot periodic TRS configuration only when no two consecutive slots are indicated as downlink slots by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigDedicated . If the UE supports this feature, the UE needs to report csi-RS-ForTracking . | Band | No | TDD only | FR1 only | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| outOfOrderOperationDL-r16
Indicates whether the UE supports out of order operation for DL. The UE that indicates support of this feature shall support multiDCI-MultiTRP-r16 . The capability signalling comprises the following parameters:
  • - supportPDCCH-ToPDSCH-r16 indicates support out-of-order operation for PDCCH to PDSCH;
  • - supportPDSCH-ToHARQ-ACK-r16 indicates support out-of-order operation for PDSCH to HARQ-ACK.
| Band | No | N/A | N/A | +| outOfOrderOperationUL-r16
Indicates whether the UE supports out of order operation for UL. The UE that indicates support of this feature shall support multiDCI-MultiTRP-r16 .

Note: Same closed loop index for power control across PUSCHs associated with different CORESETPoolIndex values is not supported by a UE indicating the support of this feature when TPC accumulation is enabled. | Band | No | N/A | N/A | +| overlapPDSCHsFullyFreqTime-r16
Indicates the maximal number of PDSCH scrambling sequences per serving cell when the UE supports PDSCHs with fully overlapping Resource Elements. The UE that indicates support of this feature shall support multiDCI-MultiTRP-r16 .

Note: A UE may assume that its maximum receive timing difference between the DL transmissions from two TRPs is within a Cyclic Prefix | Band | No | N/A | N/A | +| overlapPDSCHsInTimePartiallyFreq-r16
Indicates whether the UE supports PDSCHs with partially overlapping Resource Elements. The UE that indicates support of this feature shall support overlapPDSCHsFullyFreqTime-r16 . | Band | No | N/A | N/A | +| overlapRateMatchingEUTRA-CRS-r16
Indicates whether the UE supports two LTE-CRS overlapping rate matching patterns within a part of NR carrier using 15 kHz SCS overlapping with a LTE carrier. If the UE supports this feature, the UE needs to report multipleRateMatchingEUTRA-CRS-r16 and multiDCI-MultiTRP-r16 . | Band | No | N/A | FR1 only | +| overlapRateMatchingEUTRA-CRS-Patterns-3-4-Diff-CS-Pool-r18
Indicates whether the UE supports two LTE-CRS overlapping rate matching patterns configured by lte-CRS-PatternList3-r18 and lte-CRS-PatternList4-r18 with two different values of coresetPoolIndex within a part of NR carrier using 15 kHz overlapping with a LTE carrier for the case when crs-RateMatchPerCoresetPoolIndex is configured.
UE supporting this feature shall support twoRateMatchingEUTRA-CRS-patterns-3-4-r18 and multiDCI-MultiTRP-r16 . | Band | No | N/A | FR1 only | +| overlapUL-TransReduction-r18
Indicates whether the UE supports reducing the overlapping duration of the later of the two time-domain overlapping UL transmissions when the UE is not configured with UL STx2P for multi-DCI based multi-TRP operation with two TA enhancement.

NOTE: If UE does not support this feature, UE does not expect the two UL transmissions to overlap (i.e., scheduling restriction is applied to avoid overlap between the two UL transmissions). | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| parallelMeasurementWithoutRestriction-r17
Indicates whether the UE supports measurements on cells belonging to different satellites as the serving cell in parallel with normal operation (i.e. data/control transmission and/or reception, and L1 measurements) of serving cell without scheduling restrictions. The feature is applicable only when the serving satellite is NGSO. If the serving cell belongs to GSO satellite, the scheduling restriction is not applied on the premise that a mixed type of satellites on the same frequency layer is not supported in this release. If not reported, for measurements in parallel with normal operation of serving cell scheduling restrictions shall apply. | Band | No | FDD only | FR1 only | +| parallelPRS-MeasRRC-Inactive-r17
Indicates whether the UE supports performing RRM measurement and PRS measurement in parallel. UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands, all TDD-FR2-1 bands and all TDD-FR2-2 bands respectively | Band | No | N/A | N/A | +| pdcch-MonitoringResumptionAfterUL-NACK-r18
Indicates whether the UE supports PDCCH monitoring resumption after UL NACK. The UE indicating support of this feature shall also indicate support of pdcch-SkippingWithoutSSSG-r17 . | Band | No | N/A | N/A | +| pdcch-SkippingWithoutSSSG-r17
Indicates whether the UE supports up to 2-bit indication of PDCCH skipping by scheduling DCI if SSSG is not configured as specified in TS 38.213 [11], clause 10.4. | Band | No | N/A | N/A | +| pdcch-SkippingWithSSSG-r17
Indicates whether the UE supports 2-bit indication of SSSG switching between 2 SSSGs, PDCCH skipping by scheduling DCI, and timer based SSSG switching as specified in TS 38.213 [11], clause 10.4. UE supports search space set group switching capability-1 according to Table 10.4-1 of TS 38.213 [11].

UE indicating support of this feature shall also indicate support of pdcch-SkippingWithoutSSSG-r17 and sssg-Switching-1bitInd-r17 . | Band | No | N/A | N/A | +| pdc-maxNumberPRS-ResourceProcessedPerSlot-r18
Indicates the maximum number of single-symbol DL-PRS resources used in RTT-based Propagation delay compensation that UE can process in a slot. SCS: 15 kHz, 30 kHz, 60 kHz are applicable for FR1 bands. SCS: 60 kHz, 120 kHz are applicable for FR2 bands. A UE which supports pdc-maxNumberPRS-ResourceProcessedPerSlot-r18 shall support single-symbol DL-PRS for PDC with the comb sizes from {2,4,6,12}.
A UE supporting this feature shall also indicate support of rtt-BasedPDC-PRS-r17 . | Band | No | N/A | N/A | +| pdsch-1024QAM-2MIMO-FR1-r17
Indicates whether the UE supports 1024QAM modulation scheme for PDSCH with maximum 2 MIMO layers for FR1 as defined in TS 38.211 [6], MCS and CQI feedback tables based on 1024QAM modulation order as defined in TS 38.214 [12].

UE indicating support of this feature shall also indicate support of pdsch-256QAM-FR1 and shall not indicate support of pdsch-1024QAM-FR1-r17 . | Band | No | N/A | FR1 only | +| pdsch-1024QAM-FR1-r17
Indicates whether the UE supports 1024QAM modulation scheme for PDSCH for FR1 as defined in TS 38.211 [6], MCS and CQI feedback tables based on 1024QAM modulation order as defined in TS 38.214 [12].

UE indicating support of this feature shall also indicate support of pdsch-256QAM-FR1 and shall not indicate support of pdsch-1024QAM-2MIMO-FR1-r17 . | Band | No | N/A | FR1 only | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| pdsch-256QAM-FR2
Indicates whether the UE supports 256QAM modulation scheme for PDSCH for FR2 as defined in 7.3.1.2 of TS 38.211 [6]. | Band | No | N/A | FR2 only | +| pdsch-MappingTypeB-Alt-r16
Indicates whether the UE supports PDSCH Type B scheduling of length 9 and 10 OFDM symbols, and DMRS shift for length-10 symbols. If the UE supports this feature, the UE needs to report pdsch-MappingTypeB . | Band | No | N/A | FR1 only | +| periodicBeamReport
Indicates whether UE supports periodic 'CRI/RSRP' or 'SSBRI/RSRP' reporting using PUCCH formats 2, 3 and 4 in one slot. | Band | Yes | N/A | N/A | +| posJointTriggerBySingleDCI-RRC-Connected-r18
Indicates whether UE supports of a Rel-17 single DCI scheduling positioning SRS resource sets across the linked carriers for SRS bandwidth aggregation in RRC_CONNECTED state.
A UE indicating support of this feature shall also indicate support of FG41-4-6. | Band | No | N/A | N/A | +| posSRS-RRC-Inactive-OutsideInitialUL-BWP-r17
Indicates support of Positioning SRS transmission in RRC_INACTIVE state configured outside initial UL BWP. The capability signalling comprises the following parameters:
  • - maxSRSposBandwidthForEachSCS-withinCC-FR1-r17 Indicates the maximum SRS bandwidth supported for each SCS that UE supports within a single CC for FR1;
  • - maxSRSposBandwidthForEachSCS-withinCC-FR2-r17 indicates the maximum SRS bandwidth supported for each SCS that UE supports within a single CC for FR2;
  • - maxNumOfSRSposResourceSets-r17 indicates the max number of SRS Resource Sets for positioning supported by UE;
  • - maxNumOfPeriodicSRSposResources-r17 indicates the max number of periodic SRS Resources for positioning;
  • - maxNumOfPeriodicSRSposResourcesPerSlot-r17 indicates the max number of periodic SRS Resources for positioning per slot;
  • - differentNumerologyBetweenSRSposAndInitialBWP-r17 indicates the support of different numerology between the SRS and the initial UL BWP;
  • - srsPosWithoutRestrictionOnBWP-r17 indicates the support of SRS operation without restriction on the BW: BW of the SRS may not include BW of the CORESET#0 and SSB;
  • - maxNumOfPeriodicAndSemipersistentSRSposResources-r17 indicates the max number of P/SP SRS Resources for positioning;
  • - maxNumOfPeriodicAndSemipersistentSRSposResourcesPerSlot-r17 indicates the max number of P/SP SRS Resources for positioning per slot;
  • - differentCenterFreqBetweenSRSposAndInitialBWP-r17 indicates the support of a different center frequency between the SRS for positioning and the initial UL BWP;
| Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +|
  • - switchingTimeSRS-TX-OtherTX-r17 indicates the switching time between SRS TX and other TX in initial UL BWP or RX in initial DL BWP
  • - maxNumOfSemiPersistentSRSPosResources-r17 indicates the max number of semi-persistent SRS Resources for positioning;
  • - maxNumOfSemiPersistentSRSPosResourcesPerSlot-r17 indicates the max number of semi-persistent SRS Resources for positioning per slot.

The UE can include this field only if the UE supports srs-PosResourcesRRC-Inactive-r17. Otherwise, the UE does not include this field;

NOTE 1: The BWP with SRS for positioning is defined by the parameters locationAndBandwidth, SCS, CP in the same way as other BWPs.

NOTE 2: If differentCenterFreqBetweenSRSPosAndInitialBWP-r17 is not signalled, the UE only supports same center frequency between the SRS for positioning and initial UL BWP.

NOTE 3: If differentNumerologyBetweenSRSPosAndInitialBWP-r17 is not signalled, the UE only supports same numerology between the SRS and the initial UL BWP.

NOTE 4: If srsPosWithoutRestrictionOnBWP-r17 is not signalled, the UE supports only SRS BW that include the BW of the CORESET #0 and SSB.

NOTE 5: The fields of maxNumOfSemiPersistentSRSPosResources-r17 and maxNumOfSemiPersistentSRSPosResourcesPerSlot-r17 shall be reported together if supported by UE. One of the fields between maxSRSPosBandwidthForEachSCS-withinCC-FR1-r17 and maxSRSPosBandwidthForEachSCS-withinCC-FR2-r17, and the fields of maxNumOfSRSPosResourceSets-r17, maxNumOfPeriodicSRSPosResources-r17, maxNumOfPeriodicSRSPosResourcesPerSlot-r17, maxNumOfPeriodicAndSemipersistentSRSPosResources-r17, maxNumOfPeriodicAndSemipersistentSRSPosResourcesPerSlot-r17, and switchingTimeSRS-TX-OtherTX-r17 shall be reported together if supported by UE.

NOTE 6: srsPosWithoutRestrictionOnBWP-r17 is not applicable to FDD or SUL bands.

| | | | | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| posSRS-RRC-InactiveInitialUL-BWP-r18
Indicates whether UE supports of preconfigured SRS with validity area in RRC_INACTIVE for initial BWP. The UE can include this field only if the UE support of SRS for positioning configuration in multiple cells for UEs in RRC_INACTIVE state for initial UL BWP. | Band | No | N/A | N/A | +| posSRS-RRC-InactiveOutsideInitialUL-BWP-r18
Indicates whether UE supports preconfigured SRS with validity area in RRC_INACTIVE outside initial BWP. The UE can include this field only if the UE support of SRS for positioning configuration in multiple cells for UEs in RRC_INACTIVE state configured outside initial UL BWP. | Band | No | N/A | N/A | +| posUE-TA-AutoAdjustment-r18
Indicates whether UE supports autonomous TA adjustment when cell-reselection happens. | Band | No | N/A | N/A | +| powerBoosting-pi2BPSK
Indicates whether UE supports power boosting for pi/2 BPSK, when applicable as defined in 6.2 of TS 38.101-1 [2] v16.9.0. It is mandatory with capability signalling. This capability is not applicable to IAB-MT. | Band | CY | TDD only | FR1 only | +| priorityIndicatorInDCI-Multicast-r17
Indicates whether the UE supports DL priority indication for multicast in DCI, comprised of the following functional components:
  • - Support of priority indicator field configured in DCI formats 4_2 with CRC scrambled with G-RNTI for multicast;
  • - Supports two HARQ-ACK codebooks with different priorities to be simultaneously constructed different priorities for multicast and multicast at a UE.
For TN, the UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands and all TDD-FR2 bands, associated with supported shared and non-shared spectrum respectively. For NTN, UE shall set the capability value consistently for all FDD-FR1 NTN bands.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| priorityIndicatorInDCI-SPS-Multicast-r17
Indicates whether the UE supports priority indicator field configured in DCI format 4_2 for multicast HARQ-ACK feedback of SPS multicast.

For TN, the UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands and all TDD-FR2 bands, associated with supported shared and non-shared spectrum respectively. For NTN, UE shall set the capability value consistently for all FDD-FR1 NTN bands.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| prs-MeasurementWithoutMG-r17
Indicates whether the UE supports using the threshold to compare the Rx time difference between the serving cell and a neighbor cell/TRP for PRS measurements, as defined in clause 9.9.1.2 of TS 38.133 [5], to determine whether the PRS from the non-serving cell satisfy the condition of PRS measurement outside MG. The UE can include this field only if the UE supports one of prs-ProcessingWindowType1A-r17 , prs-ProcessingWindowType1B-r17 and prs-ProcessingWindowType2-r17 . | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| prs-ProcessingCapabilityOutsideMGinPPW-r17
Indicates the DL-PRS Processing Capability outside MG of each of the supported PRS Processing Window (PPW) Type in the case the UE supports multiple PPW Types in a band and comprises the following subfields:
  • - prsProcessingType-r17: Indicates the PPW Type for which the prs-ProcessingCapabilityOutsideMGinPPW-r17 are provided.
  • - ppw-dl-PRS-BufferType-r17: Indicates DL-PRS buffering capability. Value 'type1' indicates sub-slot/symbol level buffering and value 'type2' indicates slot level buffering.
  • - ppw-durationOfPRS-Processing1-r17: Indicates the duration of DL-PRS symbols N in units of ms a UE can process every T ms assuming maximum DL-PRS bandwidth provided in ppw-maxNumOfDL-Bandwidth-r17 and comprises the following subfields
    • - ppw-durationOfPRS-ProcessingSymbolsN-r17: This field specifies the values for N with values msDot125 indicates 0.125ms, msDot25 indicates 0.25ms, and so on
    • - ppw-durationOfPRS-ProcessingSymbolsT-r17: This field specifies the values for T with values ms1 indicates 1ms, ms2 indicates 2ms, and so on.
  • - ppw-durationOfPRS-Processing2-r17: Indicates the duration of DL-PRS symbols N2 in units of ms a UE can process every T2 ms assuming maximum DL-PRS bandwidth provided in ppw-maxNumOfDL-Bandwidth-r17 and comprises the following subfields:
    • - ppw-durationOfPRS-ProcessingSymbolsN2-r17: This field specifies the values for N2 with values msDot125 indicates 0.125ms, msDot25 indicates 0.25ms, and so on.
    • - ppw-durationOfPRS-ProcessingSymbolsT2-r17: This field specifies the values for T2 with values ms4 indicates 4ms, ms5 indicates 5ms, and so on.
  • - ppw-maxNumOfDL-PRS-ResProcessedPerSlot-r17: Indicates the maximum number of DL PRS bandwidth in MHz, which is supported and reported by UE for PRS measurement outside MG within the PPW.
  • - ppw-maxNumOfDL-Bandwidth-r17: Indicates the maximum number of DL PRS bandwidth in MHz for FR1 and FR2, which is supported and reported by UE for PRS measurement outside MG within the PPW.
The UE can include this field only if the UE supports one of prs-ProcessingWindowType1A-r17 , prs-ProcessingWindowType1B-r17 and prs-ProcessingWindowType2-r17 . Otherwise, the UE does not include this field.

NOTE 1: A UE that supports one of prs-ProcessingWindowType1A-r17 , prs-ProcessingWindowType1B-r17 or prs-ProcessingWindowType2-r17 shall always include the prs-ProcessingCapabilityOutsideMGinPPW-r17 .
NOTE 2: The (N, T) in ppw-durationOfPRS-Processing1-r17 is interpreted as in (N, T) in durationOfPRS-Processing-r16 in TS 37.355 [22], and the UE is expected to receive the DL-PRS within the PPW but the processing of the received DL-PRS may be outside a PPW
NOTE 3: The (N2, T2) in ppw-durationOfPRS-Processing2-r17 is interpreted such that the UE is capable of measuring up to N2 ms DL-PRS within a PPW and is capable of completing the DL-PRS processing within the PPW, e.g., if the time duration from the last symbol of the measured DL-PRS resource(s) inside the PPW to the end of PPW is not smaller than T2 ms.
NOTE 4: A UE which supports prs-ProcessingCapabilityOutsideMGinPPW-r17 shall support either ppw-durationOfPRS-Processing1-r17 or ppw- | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| prs-ProcessingRRC-Inactive-r17
Indicates whether the UE supports PRS processing in RRC_INACTIVE. | Band | No | N/A | N/A | +| prs-ProcessingWindowType1A-r17
Indicates whether the UE supports PRS processing Type 1A, subject to the UE determining that DL PRS to be higher priority for PRS measurement outside MG and in a PRS processing window and the priority handling options of PRS as follows:
  • - Option 1: Support of "st1" and "st3" defined in clause 5.1.6.5 of TS 38.214 [12].
  • - Option 2: Support of "st1", "st2", and "st3" defined in clause 5.1.6.5 of TS 38.214 [12].
NOTE 1: Void.
  • - Option 3: Support of "st1" only defined in clause 5.1.6.5 of TS 38.214 [12].
The UE can include this field only if the UE supports prs-ProcessingCapabilityBandList-r16 defined in TS 37.355 [22].
A UE supporting this feature shall also indicate support of prs-ProcessingCapabilityOutsideMGinPPW-r17 .

NOTE 2: Type 1A refers to the determination of prioritization between DL PRS and other DL signals/channels in all OFDM symbols within the PRS processing window. The DL signals/channels from all DL CCs (per UE) are affected across LTE and NR.
NOTE 3: Within a PRS processing window, UE measurement is inside the active DL BWP with PRS having the same numerology as the active DL BWP.
NOTE 4: Support of configuration of PRS processing window in RRC and support of using DL MAC CE to activate/deactivate the PRS processing window for PRS measurements is part of the feature.
NOTE 5: When the UE determines higher priority for other DL signals/channels over the DL-PRS measurement/processing, the UE is not expected to measure/process DL-PRS. | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| prs-ProcessingWindowType1B-r17
Indicates whether the UE supports PRS processing Type 1B, subject to the UE determining that DL PRS to be higher priority for PRS measurement outside MG and in a PRS processing window and the priority handling options of PRS as follows:
  • - Option 1: Support of "st1" and "st3" defined in clause 5.1.6.5 of TS 38.214 [12].
  • - Option 2: Support of "st1", "st2", and "st3" defined in clause 5.1.6.5 of TS 38.214 [12].
    NOTE 1: Void.
  • - Option 3: Support of "st1" only defined in clause 5.1.6.5 of TS 38.214 [12].
The UE can include this field only if the UE supports prs-ProcessingCapabilityBandList-r16 defined in TS 37.355 [22].
A UE supporting this feature shall also indicate support of prs-ProcessingCapabilityOutsideMGinPPW-r17 .

NOTE 2: Type 1B refers to the determination of prioritization between DL PRS and other DL signals/channels in all OFDM symbols within the PRS processing window. The DL signals/channels from a certain band are affected.
NOTE 3: Within a PRS processing window, UE measurement is inside the active DL BWP with PRS having the same numerology as the active DL BWP.
NOTE 4: Support of configuration of PRS processing window in RRC and support of using DL MAC CE to activate/deactivate the PRS processing window for PRS measurements is part of the feature.
NOTE 5: When the UE determines higher priority for other DL signals/channels over the DL-PRS measurement/processing, the UE is not expected to measure/process DL-PRS. | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| prs-ProcessingWindowType2-r17
Indicates whether the UE supports PRS processing Type 2, subject to the UE determining that DL PRS to be higher priority for PRS measurement outside MG and in a PRS processing window and the priority handling options of PRS as follows:
  • - Option 1: Support of "st1" and "st3" defined in clause 5.1.6.5 of TS 38.214 [12].
  • - Option 2: Support of "st1", "st2", and "st3" defined in clause 5.1.6.5 of TS 38.214 [12].
    NOTE 1: Void.
  • - Option 3: Support of "st1" only defined in clause 5.1.6.5 of TS 38.214 [12].
The UE can include this field only if the UE supports prs-ProcessingCapabilityBandList-r16 defined in TS 37.355 [22].
A UE supporting this feature shall also indicate support of prs-ProcessingCapabilityOutsideMGinPPW-r17 .

NOTE 2: Type 2 refers to the determination of prioritization between DL PRS and other DL signals/channels only in DL PRS symbols within the PRS processing window.
NOTE 3: Within a PRS processing window, UE measurement is inside the active DL BWP with PRS having the same numerology as the active DL BWP.
NOTE 4: Support of configuration of PRS processing window in RRC and support of using DL MAC CE to activate/deactivate the PRS processing window for PRS measurements is part of the feature.
NOTE 5: When the UE determines higher priority for other DL signals/channels over the DL-PRS measurement/processing, the UE is not expected to measure/process DL-PRS. | Band | No | N/A | N/A | +| ptrs-DensityRecommendationSetDL
For each supported sub-carrier spacing, indicates preferred threshold sets for determining DL PTRS density. It is mandated for FR2. For each supported sub-carrier spacing, this field comprises:
  • - two values of frequencyDensity;
  • - three values of timeDensity.
| Band | CY | N/A | N/A | +| ptrs-DensityRecommendationSetUL
For each supported sub-carrier spacing, indicates preferred threshold sets for determining UL PTRS density. For each supported sub-carrier spacing, this field comprises:
  • - two values of frequencyDensity;
  • - three values of timeDensity;
  • - five values of sampleDensity.
| Band | No | N/A | N/A | +| pucch-Repetition-F0-2-r17
Indicates whether the UE supports transmission of a PUCCH format 0 and 2 over multiple slots with the repetition factor 2, 4 or 8.
A UE supporting this feature shall also indicate support of pucch-Repetition-F1-3-4 . | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| pucch-RepetitionDynamicIndicationSFN-r18
Indicates whether the UE supports STxMP SFN PUCCH scheme together with pucch-Repetition-F0-1-2-3-4-DynamicIndication-r17 .
A UE supporting this feature shall also indicate support of pucch-SingleDCI-STx2P-SFN-r18 and slotBasedDynamicPUCCH-Rep-r17 . | Band | No | N/A | FR2 only | +| pucch-SpatialRelInfoMAC-CE
Indicates whether the UE supports indication of PUCCH-spatialrelationinfo by a MAC CE per PUCCH resource. It is mandatory for FR2 and optional for FR1. | Band | CY | N/A | N/A | +| pusch-256QAM
Indicates whether the UE supports 256QAM modulation scheme for PUSCH as defined in 6.3.1.2 of TS 38.211 [6]. | Band | No | N/A | N/A | +| pusch-CB-2PTRS-SingleDCI-STx2P-SDM-r18
Indicates whether the UE supports 2 PTRS ports for single-DCI based STx2P SDM scheme for PUSCH codebook.
A UE supporting this feature shall also indicate support of pusch-CB-SingleDCI-STx2P-SDM-r18 . | Band | No | N/A | FR2 only | +| pusch-CB-2PTRS-SingleDCI-STx2P-SFN-r18
Indicates whether the UE supports 2 PTRS ports for single-DCI based STx2P SFN scheme for PUSCH codebook.
A UE supporting this feature shall also indicate support of pusch-CB-SingleDCI-STx2P-SFN-r18 . | Band | No | N/A | FR2 only | +| pusch-NonCB-2PTRS-SingleDCI-STx2P-SDM-r18
Indicates whether the UE supports 2 PTRS ports for single-DCI based STx2P SDM scheme for PUSCH—noncodebook.
A UE supporting this feature shall also indicate support of pusch-NonCB-SingleDCI-STx2P-SDM-r18 . | Band | No | N/A | FR2 only | +| pusch-NonCB-2PTRS-SingleDCI-STx2P-SFN-r18
Indicates whether the UE supports 2 PTRS ports for single-DCI based STx2P SFN scheme for PUSCH—noncodebook.
A UE supporting this feature shall also indicate support of pusch-NonCB-SingleDCI-STx2P-SFN-r18 . | Band | No | N/A | FR2 only | +| pusch-NonCB-SingleDCI-STx2P-SDM-CSI-RS-SRS-r18
Indicates whether the UE supports up to two NZP CSI-RS resources associated with the two SRS resource sets for non-codebook based STxMP SDM scheme for PUSCH. This capability comprises:
  • - maxNumberPeriodicSRS-Resource-PerBWP-r18 indicates the maximum number of periodic SRS resources associated with first and second CSI-RS per BWP.
  • - maxNumberAperiodicSRS-Resource-PerBWP-r18 indicates the maximum number of aperiodic SRS resources associated with first and second CSI-RS per BWP.
  • - maxNumberSemiPersistentSRS-ResourcePerBWP-r18 indicates the maximum number of semi-persistent SRS resources associated with first and second CSI-RS per BWP.
  • - valueY-SRS-ResourceAssociate-r18 indicates UE can process (Y) SRS resources associated with first and second CSI-RS resources simultaneously in a CC. Includes P/SP/A SRS
  • - valueX-CSI-RS-ResourceAssociate-r18 indicates UE can process up to (X) CSI-RS resources associated with SRS for non-codebook-based transmission simultaneously
A UE supporting this feature shall also indicate support of srs-AssocCSI-RS and pusch-NonCB-SingleDCI-STx2P-SDM-r18 . | Band | No | N/A | FR2 only | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| pusch-NonCB-SingleDCI-STx2P-SFN-CSI-RS-SRS-r18
Indicates whether the UE supports up to two NZP CSI-RS resources associated with the two SRS resource sets for non-codebook based STxMP SFN scheme for PUSCH. This capability comprises:
  • - maxNumberPeriodicSRS-Resource-PerBWP-r18 indicates the maximum number of periodic SRS resources associated with first and second CSI-RS per BWP.
  • - maxNumberAperiodicSRS-Resource-PerBWP-r18 indicates the maximum number of aperiodic SRS resources associated with first and second CSI-RS per BWP.
  • - maxNumberSemiPersistentSRS-ResourcePerBWP-r18 indicates the maximum number of semi-persistent SRS resources associated with first and second CSI-RS per BWP.
  • - valueY-SRS-ResourceAssociate-r18 indicates UE can process (Y) SRS resources associated with first and second CSI-RS resources simultaneously in a CC. Includes P/SP/A SRS
  • - valueX-CSI-RS-ResourceAssociate-r18 indicates UE can process up to (X) CSI-RS resources associated with SRS for non-codebook-based transmission simultaneously
A UE supporting this feature shall also indicate support of srs-AssocCSI-RS and pusch-NonCB-SingleDCI-STx2P-SFN-r18 . | Band | No | N/A | FR2 only | +| pusch-RepetitionMsg3-r17
Indicates whether the UE supports repetition of PUSCH transmission scheduled by RAR UL grant and DCI format 0_0 with CRC scrambled by TC-RNTI. | Band | No | N/A | N/A | +| pusch-RepetitionMultiSlots-v1650
Indicates whether the UE supports transmitting PUSCH scheduled by DCI format 0_1 when configured with pusch-AggregationFactor > 1, as defined in clause 6.1.2.1 of TS 38.214 [12]. This applies only to non-shared spectrum channel access. For shared spectrum channel access, pusch-RepetitionMultiSlots-r16 applies. UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands, all TDD-FR2-1 bands and all TDD-FR2-2 bands respectively.

The UE only includes pusch-RepetitionMultiSlots-v1650 if pusch-RepetitionMultiSlots is absent. | Band | Yes | N/A | N/A | +| pusch-RepetitionTypeA-v16c0
Indicates whether the UE supports the dynamic indication of the number of repetitions for PUSCH transmission as specified in TS 38.214 [12], clause 6.1.2.1. Support of this field is reported for shared spectrum channel access and non-shared spectrum channel access, respectively. UE indicating support of this feature shall support at least one of type2-PUSCH-RepetitionMultiSlots and pusch-RepetitionMultiSlots for shared spectrum and non-shared spectrum respectively.

UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands and all TDD-FR2 bands respectively.

The UE only includes pusch-RepetitionTypeA-v16c0 if pusch-RepetitionTypeA-r16 is absent. | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| pusch-TransCoherence
Defines support of the uplink codebook subset by the UE for UL precoding for PUSCH transmission as described in clause 6.1.1.1 of TS 38.214 [12]. UE indicated support of partial coherent codebook subset shall also support non-coherent codebook subset. UE indicated support of full coherent codebook subset shall also support partial and non-coherent codebook subset. | Band | No | N/A | N/A | +| puschTypeA-RepetitionsAvailSlot-r17
Indicates whether UE supports dynamic and configured grant PUSCH repetitions based on available slots. Transmission occasions for the repetitions for dynamic and configured grant PUSCH are determined on the basis of available slots.

A UE that indicates support of this feature shall support type1-PUSCH-RepetitionMultiSlots , type2-PUSCH-RepetitionMultiSlots or pusch-RepetitionMultiSlots . | Band | No | N/A | N/A | +| rachLessHandoverNTN-r18
Indicates whether the UE supports RACH-less handover in NTN. For NTN, UE shall set the capability value consistently for all FDD-FR1 NTN bands. For NTN bands, a UE supporting this feature shall also indicate the support of nonTerrestrialNetwork-r17 . | Band | No | N/A | N/A | +| rateMatchingLTE-CRS
Indicates whether the UE supports receiving PDSCH with resource mapping that excludes the REs determined by the higher layer configuration LTE-carrier configuring common RS, as specified in TS 38.214 [12]. | Band | Yes | N/A | N/A | +| releaseSPS-MulticastWithCS-RNTI-r17
Indicates whether UE supports unicast PDCCH scrambled with CS-RNTI to release SPS group-common PDSCH. For TN, the UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands and all TDD-FR2 bands, associated with supported shared and non-shared spectrum respectively. For NTN, UE shall set the capability value consistently for all FDD-FR1 NTN bands.

A UE that indicates the support of this feature shall indicate support of sps-Multicast-r17 and sps-r16 . | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| re-LevelRateMatchingForMulticast-r17
Indicates whether the UE supports group-common PDSCH RE-level rate matching for multicast, comprised of the following functional components:
  • - Supports SP ZP-CSI-RS for group-common PDSCH RE-mapping patterns;
  • - Supports P ZP-CSI-RS for group-common PDSCH RE-mapping patterns;
  • - Supports p-ZP-CSI-RS-ResourceSet configured in PDSCH-Config-Multicast same as or different from the p-ZP-CSI-RS-ResourceSet configured in PDSCH-Config;
  • - Supports AP ZP-CSI-RS for group-common PDSCH RE-mapping patterns.
For TN, the UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands and all TDD-FR2 bands, associated with supported shared and non-shared spectrum respectively. For NTN, UE shall set the capability value consistently for all FDD-FR1 NTN bands.

A UE supporting this feature shall also indicate support of dynamicMulticastPCell-r17 . A UE supporting this feature in FR1 bands shall also indicate support of pdsch-RE-MappingFR1-PerSymbol or pdsch-RE-MappingFR1-PerSlot . A UE supporting this feature in FR2 bands shall also indicate support of pdsch-RE-MappingFR2-PerSymbol or pdsch-RE-MappingFR2-PerSlot .

NOTE: The total number of semi-persistent ZP-CSI-RS-ResourceSet that a UE can be configured with is the same as for unicast in Rel-16. | Band | No | N/A | N/A | +| rlm-BM-BFD-CSI-RS-OutsideActiveBWP-r18
Indicates whether the UE supports RLM/BM/BFD measurements based on CSI-RS, when CD-SSB is outside active DL BWP.

Bandwidth of UE-specific RRC configured BWP may not include bandwidth of the CORESET#0 (if CORESET#0 is present) and CD-SSB for PCell/PSCell (if configured) and bandwidth of the UE-specific RRC configured BWP may not include CD-SSB for SCell.

The UE supporting this feature shall also indicate support of csi-RS-RLM , beamManagementSSB-CSI-RS and maxNumberCSI-RS-BFD , maxNumberSSB-BFD , maxNumberCSI-RS-SSB-CBD . The UEs indicating the support of this feature group shall not indicate the support of bwp-WithoutRestriction .

NOTE: The CD-SSB is still within the bandwidth of the carrier configured by SCS-SpecificCarrier of downlinkChannelBW-PerSCS-List in ServingCellConfig .

It is not applicable to RedCap or eRedCap UEs. | Band | No | N/A | N/A | +| rlm-Relaxation-r17
Indicates whether the UE supports RLM relaxation criteria and requirement as specified in TS 38.133 [5]. UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands, all TDD-FR2-1 bands and all TDD-FR2-2 bands respectively.

UE indicating support of this feature shall also indicate support of ssb-RLM and/or csi-RS-RLM . | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| searchSpaceSetGrp-switchCap2-r17
Indicates whether UE supports search space set group switching capability 2 for FR1 according to Table 10.4-1 of TS 38.213 [11] for SSSG switching.

UE indicating support of this feature shall also indicate support of sssg-Switching-1bitInd-r17 .

NOTE: For UE supporting this feature and also sssg-Switching-1BitInd-r17 , sssg-Switching-2BitInd-r17 , and/or pdcch-SkippingWithSSSG-r17 , search space set group switching Capability-2 is applied to sssg-Switching-1BitInd-r17 , sssg-Switching-2BitInd-r17 , and/or pdcch-SkippingWithSSSG-r17 . | Band | No | N/A | FR1 only | +| semi-PersistentL1-SINR-Report-PUCCH-r16
Indicates whether the UE supports semi-persistent L1-SINR report on PUCCH. The UE indicating support of this feature shall include at least one of the following capabilities:
  • - supportReportFormat1-2OFDM-syms-r16 indicates support of report on PUCCH formats over 1 – 2 OFDM symbols once per slot (or piggybacked on a PUSCH)
  • - supportReportFormat4-14OFDM-syms-r16 indicates support of report on PUCCH formats over 4 – 14 OFDM symbols once per slot (or piggybacked on a PUSCH).
The UE indicating support of this feature shall also indicate support of ssb-csirs-SINR-measurement-r16 . | Band | No | N/A | N/A | +| semi-PersistentL1-SINR-Report-PUSCH-r16
Indicates whether the UE supports semi-persistent L1-SINR report on PUSCH. The UE indicating support of this feature shall also indicate support of ssb-csirs-SINR-measurement-r16 . | Band | No | N/A | N/A | +| separateCRS-RateMatching-r16
Indicates whether the UE supports rate match around configured CRS patterns which is associated with CORESETPoolIndex (if configured) and are applied to the PDSCH scheduled with a DCI detected on a CORESET with the same value of CORESETPoolIndex . The UE that indicates support of this feature shall support multiDCI-MultiTRP-r16 and overlapRateMatchingEUTRA-CRS-r16 . This is only applicable for 15kHz SCS. | Band | No | N/A | FR1 only | +| sfn-SimulTwoTCI-AcrossMultiCC-r17
Indicates whether the UE supports simultaneous activation of two TCI states for CORESETs with the same CORESET ID in all BWPs across a set of configured component carriers by single MAC-CE. The UE indicating support of this feature shall also indicate sfn-schemeA-r17 or sfn-schemeB-r17 or sfn-SchemeA-PDCCH-only-r17 .
The UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands, all TDD-FR2-1 bands and all TDD-FR2-2 bands respectively. | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| sfn-DefaultDL-BeamSetup-r17
Indicates whether the UE supports the following features:
  • - For FR2 only, PDSCH reception using default beam for enhanced SFN scheme when PDSCH is scheduled with offset less than threshold.
  • - For FR1 and FR2, PDSCH reception using default beam for enhanced SFN scheme when TCI field is not present in DCI format 1_0/1_1/1_2 when PDSCH is scheduled with offset equal or larger than the threshold, if applicable.
  • - For FR2 only, aperiodic CSI-RS reception using default beam for enhanced SFN scheme when scheduling offset is less than threshold.
The UE indicating support of this feature shall also indicate sfn-schemeA-r17 or sfn-schemeB-r17 . | Band | No | N/A | N/A | +| sfn-DefaultUL-BeamSetup-r17
Indicates whether the UE supports the following features:
  • - Support of single-TRP PUCCH transmission using default beam when enhanced SFN PDCCH transmission scheme is configured.
  • - Support of single-TRP PUSCH transmission using default beam when enhanced SFN PDCCH transmission scheme is configured.
  • - Support of single-TRP SRS resource transmission using default beam when enhanced SFN PDCCH transmission scheme is configured.
The UE indicating support of this feature shall also indicate sfn-schemeA-r17 or sfn-schemeB-r17 or sfn-SchemeA-PDCCH-only-r17 . | Band | No | N/A | FR2 only | +| sfn-ImplicitRS-twoTCI-r17
Indicates whether the UE supports RS(s) with two TCI states configured implicitly for beam failure detection enhancement for HST. | Band | No | N/A | N/A | +| sfn-QCL-TypeD-Collision-twoTCI-r17
Indicates whether the UE supports identification of two QCL-TypeD properties for multiple overlapping CORESETs when a CORESET is activated with two TCI states which overlaps with another CORESET. | Band | No | N/A | N/A | +| simul-SpatialRelationUpdatePUCCHResGroup-r16
Indicates whether the UE support PUCCH resource groups per BWP for simultaneous spatial relation update. The UE indicating support of this also indicates the capabilities of supported SRS resources and maximum supported spatial relations for the supported bands using supportedSRS-Resources , maxNumberConfiguredSpatialRelations and pucch-SpatialRelInfoMAC-CE . | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| simuITX-SRS-AntSwitchingIntraBandUL-CA-r16
Indicates whether the UE support simultaneous transmission of SRS on different CCs for intra-band UL CA. The UE indicating support of this feature shall include at least one of the following capabilities:
  • - supportSRS-xTyR-xLessThanY-r16 indicates support transmission of SRS for xTyR (x<y) based antenna switching and SRS for CB/NCB/BM on different CCs in overlapped symbol(s) for intra-band UL CA.
  • - supportSRS-xTyR-xEqualToY-r16 indicates support transmission of SRS for xTyR (x=y) based antenna switching and SRS for CB/NCB/BM on different CCs in overlapped symbol(s) for intra-band UL CA.
  • - supportSRS-AntennaSwitching-r16 Indicates whether the UE support simultaneous transmission of SRS for antenna switching on different CCs in overlapped symbol(s) for intra-band UL CA.
NOTE: For simultaneously antenna switching and antenna switching SRS in intra-band CAs with bands whose UL are switched together according to the reported supportSRS-AntennaSwitching-r16 , the UE expects the same configuration of xTyR across the different CCs and the SRS resources overlapped in time domain from UE perspective are from the same UE antenna ports. | Band | No | N/A | N/A | +| simuSRS-MIMO-TransWithinBand-r16
Indicates the number of SRS resources for positioning and SRS resource for MIMO on a symbol within a band across multiple CCs. The UE can include this field only if the UE supports srs-PosResources-r16 . Otherwise, the UE does not include this field. | Band | No | N/A | N/A | +| simuSRS-TransWithinBand-r16
Indicates the number of SRS resources for positioning on a symbol within a band across multiple CCs. The UE can include this field only if the UE supports srs-PosResources-r16 . Otherwise, the UE does not include this field. | Band | No | N/A | N/A | +| simultaneousReceptionDiffTypeD-r16
Indicates whether the UE supports simultaneous reception with different QCL Type D reference signal as specified in TS 38.213 [11]. | Band | No | N/A | FR2 only | +| sn-InitiatedCondPSCellChangeNRDC-r17
Indicates whether the UE supports SN initiated inter-SN conditional PSCell change in NR-DC, which is configured by NR conditionalReconfiguration using SN configured measurement as triggering condition. The UE supporting this feature shall also support 2 trigger events for same execution condition in SN initiated inter-SN conditional PSCell change in NR-DC. UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands and all TDD-FR2 bands respectively. | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and spsMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| spatialRelations, spatialRelations-v1640
Indicates whether the UE supports spatial relations. The capability signalling comprises the following parameters.
  • - maxNumberConfiguredSpatialRelations indicates the maximum number of configured spatial relations per CC for PUCCH and SRS. It is not applicable to FR1 and applicable to FR2 only. The UE is mandated to report 16 or higher values. maxNumberConfiguredSpatialRelations-v1640 indicates the maximum number of configured spatial relations per CC for PUCCH and SRS with UE supporting the configuration of maximum 64 PUCCH spatial relations per BWP per CC;
  • - maxNumberActiveSpatialRelations indicates the maximum number of active spatial relations with regarding to PUCCH and SRS for PUSCH, per BWP per CC. It is not applicable to FR1 and applicable and mandatory to report one or higher value for FR2 only;
  • - additionalActiveSpatialRelationPUCCH indicates support of one additional active spatial relation for PUCCH. It is mandatory with capability signalling if maxNumberActiveSpatialRelations is set to n1;
  • - maxNumberDL-RS-QCL-TypeD indicates the maximum number of downlink RS resources used for QCL type D in the active TCI states and active spatial relation information, which is optional.
The UE is mandated to report spatialRelations for FR2. if maxNumberConfiguredSpatialRelations-v1640 is reported, UE shall report value n96 in maxNumberConfiguredSpatialRelations . | Band | FD | N/A | FD | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| spatialRelationsSRS-Pos-r16
Indicates whether the UE supports spatial relations for SRS for positioning. The capability signalling comprises the following parameters.
  • - spatialRelation-SRS-PosBasedOnSSB-Serving-r16 indicates whether the UE supports spatial relation for SRS for positioning based on SSB from the serving cell in the same band. The UE can include this field only if the UE supports srs-PosResources-r16. Otherwise, the UE does not include this field;
  • - spatialRelation-SRS-PosBasedOnCSI-RS-Serving-r16 indicates whether the UE supports spatial relation for SRS for positioning based on CSI-RS from the serving cell in the same band. The UE can include this field only if the UE supports spatialRelation-SRS-PosBasedOnSSB-Serving-r16. Otherwise, the UE does not include this field;
  • - spatialRelation-SRS-PosBasedOnPRS-Serving-r16 indicates whether the UE supports spatial relation for SRS for positioning based on PRS from the serving cell in the same band. The UE can include this field only if the UE supports any of DL PRS Resources for DL AoD, DL PRS Resources for DL-TDOA or DL PRS Resources for Multi-RTT defined in TS 37.355 [22], or srs-PosResources-r16. Otherwise, the UE does not include this field;
  • - spatialRelation-SRS-PosBasedOnSRS-r16 indicates whether the UE supports spatial relation for SRS for positioning based on SRS in the same band. The UE can include this field only if the UE supports srs-PosResources-r16. Otherwise, the UE does not include this field;
  • - spatialRelation-SRS-PosBasedOnSSB-Neigh-r16 indicates whether the UE supports spatial relation for SRS for positioning based on SSB from the neighbouring cell in the same band. The UE can include this field only if the UE supports spatialRelation-SRS-PosBasedOnSSB-Serving-r16. Otherwise, the UE does not include this field;
  • - spatialRelation-SRS-PosBasedOnPRS-Neigh-r16 indicates whether the UE supports spatial relation for SRS for positioning based on PRS from the neighbouring cell in the same band. The UE can include this field only if the UE supports spatialRelation-SRS-PosBasedOnPRS-Serving-r16. Otherwise, the UE does not include this field;
NOTE: A PRS from a PRS-only TP is treated as PRS from a non-serving cell. | Band | No | N/A | FR2 only | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| spatialRelationsSRS-PosRRC-Inactive-r17
Indicates whether the UE supports spatial relations for SRS for positioning in RRC_INACTIVE. The capability signalling comprises the following parameters:
  • - spatialRelation-SRS-PosBasedOnSSB-Serving-r16 indicates whether the UE supports spatial relation for SRS for positioning based on SSB from the serving cell in the same band. The UE indicating support of this feature shall also indicate support of srs-PosResourcesRRC-Inactive-r17;
  • - spatialRelation-SRS-PosBasedOnCSI-RS-Serving-r16 indicates whether the UE supports spatial relation for SRS for positioning based on CSI-RS from the serving cell in the same band. The UE indicating support of this feature shall also indicate support of spatialRelation-SRS-PosBasedOnSSB-Serving-r16;
  • - spatialRelation-SRS-PosBasedOnPRS-Serving-r16 indicates whether the UE supports spatial relation for SRS for positioning based on PRS from the serving cell in the same band. The UE indicating support of this feature shall also indicate support any of DL PRS Resources for DL AoD, DL PRS Resources for DL-TDOA or DL PRS Resources for Multi-RTT defined in TS 37.355 [22], or srs-PosResourcesRRC-Inactive-r17;
  • - spatialRelation-SRS-PosBasedOnSRS-r16 indicates whether the UE supports spatial relation for SRS for positioning based on SRS in the same band. The UE indicating support of this feature shall also indicate support of srs-PosResourcesRRC-Inactive-r17;
  • - spatialRelation-SRS-PosBasedOnSSB-Neigh-r16 indicates whether the UE supports spatial relation for SRS for positioning based on SSB from the neighbouring cell in the same band. The UE indicating support of this feature shall also indicate support of spatialRelation-SRS-PosBasedOnSSB-Serving-r16;
  • - spatialRelation-SRS-PosBasedOnPRS-Neigh-r16 indicates whether the UE supports spatial relation for SRS for positioning based on PRS from the neighbouring cell in the same band. The UE indicating support of this feature shall also indicate support of spatialRelation-SRS-PosBasedOnPRS-Serving-r16.
NOTE: A PRS from a PRS-only TP is treated as PRS from a non-serving cell. | Band | No | N/A | FR2 only | +| sp-BeamReportPUCCH
Indicates support of semi-persistent 'CRI/RSRP' or 'SSBRI/RSRP' reporting using PUCCH formats 2, 3 and 4 in one slot. | Band | No | N/A | N/A | +| sp-BeamReportPUSCH
Indicates support of semi-persistent 'CRI/RSRP' or 'SSBRI/RSRP' reporting on PUSCH. | Band | No | N/A | N/A | +| spCell-TAG-Ind-r18
Indicates whether the UE supports indicating one of two TAG IDs configured in the SpCell via absolute TA command MAC CE. | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| sps-MulticastDCI-Format4-2-r17
Indicates whether the UE supports transmission and retransmission scheduled by DCI format 4_2 with CRC scrambled with G-CS-RNTI for multicast SPS scheduling.

A UE that indicates support of this feature shall indicate support of sps-Multicast-r17 . | Band | No | N/A | N/A | +| sps-MulticastMultiConfig-r17
Indicates whether the UE supports up to 8 SPS group-common PDSCH configurations per CFR for multicast on PCell. The value indicates the maximum number of activated SPS group-common PDSCH configurations per CFR for multicast.
The total number of SPS configurations for both multicast and unicast is no larger than 8 in a BWP of a serving cell. The total number of SPS configurations for both multicast and unicast in a cell group is no larger than 32.

For TN, the UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands and all TDD-FR2 bands, associated with supported shared and non-shared spectrum respectively. For NTN, UE shall set the capability value consistently for all FDD-FR1 NTN bands.

A UE that indicates support of this feature shall indicate support of sps-Multicast-r17 . | Band | No | N/A | N/A | +| sps-r16
Indicates whether the UE support of up to 8 configured SPS configurations in a BWP of a serving cell and up to 32 configured SPS configurations in a cell group.
This field includes the following parameters:
  • - maxNumberConfigsPerBWP-r16 indicates the maximum number of active SPS configurations in a BWP of a serving cell.
  • - maxNumberConfigsAllCC-r16 indicates the maximum number of active SPS configurations across all serving cells in a MAC entity, and across MCG and SCG in case of NR-DC.
The UE can include this feature only if the UE indicates support of downlinkSPS .

NOTE:
  • - For all the reported bands in FR1, a same X1 value is reported for maxNumberConfigsAllCC-r16. For all the reported bands in FR2, a same X2 value is reported for maxNumberConfigsAllCC-r16.
  • - The total number of active SPS configurations across all serving cells in FR1 is no greater than X1.
  • - The total number of active SPS configurations across all serving cells in FR2 is no greater than X2.
  • - If the CA have some serving cell(s) in FR1 and some serving cell(s) in FR2, the total number of active SPS configurations across all serving cells is no greater than max(X1, X2).
| Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| srs-AssocCSI-RS
Parameters for the calculation of the precoder for SRS transmission based on channel measurements using associated NZP CSI-RS resource ( srs-AssocCSI-RS ) as described in clause 6.1.1.2 of TS 38.214 [12]. UE supporting this feature shall also indicate support of non-codebook based PUSCH transmission.
This capability signalling includes list of the following parameters:
  • - maxNumberTxPortsPerResource indicates the maximum number of Tx ports in a resource;
  • - maxNumberResourcesPerBand indicates the maximum number of resources across all CCs within a band simultaneously;
  • - totalNumberTxPortsPerBand indicates the total number of Tx ports across all CCs within a band simultaneously.
| Band | No | N/A | N/A | +| srs-combEight-r17
Indicates whether the UE supports comb-8 for SRS other than for positioning. | Band | No | N/A | N/A | +| srs-combOffsetCombinedGroupSequence-r18
Indicates whether the UE supports SRS comb offset hopping combined with legacy group/sequence hopping.
The UE supporting this feature shall also indicate the support of Feature 40-5-1. | Band | No | N/A | N/A | +| srs-combOffsetHoppingWithinSubset-r18
Indicates whether the UE supports configuration of subset of comb offsets for comb offset hopping.
A UE supporting this feature shall also indicate support of FG40-5-1. | Band | No | N/A | N/A | +| srs-combOffsetInTime-r18
Indicates whether the UE supports comb offset hopping granularity in time when repetition factor $R > 1$ is configured. Value srs indicates the granularity is per SRS symbol, Value rsrs indicates the granularity is per R SRS symbols, Value both indicates both of per SRS symbol and per R SRS symbols are supported.
The UE supporting this feature shall also indicate the support of Feature 40-5-1. | Band | No | N/A | N/A | +| srs-cyclicShiftCombinedCombOffset-r18
Indicates whether the UE supports SRS cyclic shift hopping combined SRS comb offset hopping.
The UE supporting this feature shall also indicate the support of Feature 40-5-1 and Feature 40-5-2. | Band | No | N/A | N/A | +| srs-cyclicShiftCombinedGroupSequence-r18
Indicates whether the UE supports SRS cyclic shift hopping combined with legacy group/sequence hopping.
The UE supporting this feature shall also indicate the support of Feature 40-5-2. | Band | No | N/A | N/A | +| srs-cyclicShiftHoppingSmallGranularity-r18
Indicates whether the UE supports configuration of cyclic shift hopping with smaller granularity (with factor $K=2$ ).
A UE supporting this feature shall also indicate the support FG40-5-2. | Band | No | N/A | N/A | +| srs-increasedRepetition-r17
Indicates whether the UE supports increased repetition patterns (8, 10, 12, 14 symbols) for SRS resource.

The UE supporting this feature shall also indicate the support of srs-StartAnyOFDM-Symbol-r16 . | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| srs-partialFreqSounding-r17
Indicates the support of partial frequency sounding for SRS for non-frequency hopping case.

The UE indicating support of this feature shall also indicate the support of srs-partialFrequencySounding-r17 . | Band | No | N/A | N/A | +| srs-partialFrequencySounding-r17
Indicates whether the UE supports partial frequency sounding for SRS with frequency hopping. | Band | No | N/A | N/A | +| srs-PosResourcesRRC-Inactive-r17
Indicates support of positioning SRS transmission in RRC_INACTIVE for initial UL BWP. The capability signalling comprises the following parameters:
  • - maxNumberSRS-PosResourceSetPerBWP-r17 Indicates the max number of SRS Resource Sets for positioning supported by UE;
  • - maxNumberSRS-PosResourcesPerBWP-r17 indicates the max number of P/SP SRS Resources for positioning;
  • - maxNumberSRS-ResourcesPerBWP-PerSlot-r17 indicates the max number of P/SP SRS Resources for positioning per slot;
  • - maxNumberPeriodicSRS-PosResourcesPerBWP-r17 indicates the max number of periodic SRS Resources for positioning;
  • - maxNumberPeriodicSRS-PosResourcesPerBWP-PerSlot-r17 indicates the max number of periodic SRS Resources for positioning per slot.
NOTE: OLPC for SRS for positioning based on SSB from the last serving cell (the cell that releases UE from connection) is part of this feature. No dedicated capability signalling is intended for this component | Band | No | N/A | N/A | +| srs-SemiPersistent-PosResourcesRRC-Inactive-r17
Indicates support of positioning SRS transmission in RRC_INACTIVE for initial UL BWP with semi-persistent SRS. UE indicating support of this feature shall indicate support of srs-PosResourcesRRC-Inactive-r17 .

The capability signalling comprises the following parameters:
  • - maxNumOfSemiPersistentSRSPosResources-r17 indicates the max number of semi-persistent SRS Resources for positioning;
  • - maxNumOfSemiPersistentSRSPosResourcesPerSlot-r17 indicates the max number of semi-persistent SRS Resources for positioning per slot.
| Band | No | N/A | N/A | +| srs-PortReport-r17
Indicates the maximum number of SRS ports for each UE reported quantity in reportQuantity-r17 . | Band | No | N/A | N/A | +| srs-PortReportSP-AP-r17
Indicates that the UE supports the maximum number of SRS ports with semi-persistent/aperiodic capability value reporting.
The UE supporting this feature shall also indicate support of srs-PortReport-r17 and one of aperiodicBeamReport , sp-BeamReportPUCCH , sp-BeamReportPUSCH , ssb-csirs-SINR-measurement-r16 , semi-PersistentL1-SINR-Report-PUCCH-r16 or semi-PersistentL1-SINR-Report-PUSCH-r16 . | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| srs-startRB-locationHoppingPartial-r17
Indicates whether the UE supports start RB location hopping in partial frequency SRS transmission across different SRS frequency hopping periods for periodic/semi-persistent/aperiodic SRS.

The UE supporting this feature shall also indicate the support of srs-partialFrequencySounding-r17 . | Band | No | N/A | N/A | +| srs-TriggeringOffset-r17
Indicates the maximum number of configured available slots offsets for determining aperiodic SRS location based on available slot. | Band | No | N/A | N/A | +| srs-TriggeringDCI-r17
Indicates whether the UE supports triggering SRS in DCI 0_1/0_2 without data and without CSI. | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ssb-csirs-SINR-measurement-r16
Indicates the limitations of the UE support of SSB/CSI-RS for L1-SINR measurement.
This capability signalling includes list of the following parameters:
Per slot limitations:
  • - maxNumberSSB-CSI-RS-OneTx-CMR-r16 indicates the maximum number of SSB/CSI-RS (1TX) across all CCs within a band for Channel Measurement Report
  • - maxNumberCSI-IM-NZP-IMR-res-r16 indicates the maximum number of CSI-IM/NZP-IMR resources across all CCs within a band
  • - maxNumberCSIRS-2Tx-res-r16 indicates the maximum number of CSI-RS (2TX) resources across all CCs within a band for Channel Measurement Report
Memory limitations:
  • - maxNumberSSB-CSI-RS-res-r16 indicates the max number of SSB/CSI-RS resources across all CCs within a band as Channel Measurement Report
  • - maxNumberCSI-IM-NZP-IMR-res-mem-r16 indicates the maximum number of CSI-IM/NZP-IMR resources across all CCs within a band
Other limitations:
  • - supportedCSI-RS-Density-CMR-r16 indicates supported density of CSI-RS for Channel Measurement Report.
  • - maxNumberAperiodicCSI-RS-Res-r16 indicates the maximum number of aperiodic CSI-RS resources across all CCs within a band configured to measure L1-SINR (including CMR and IMR)
  • - supportedSINR-meas indicates the supported SINR measurements.
    • - supportedSINR-meas-r16 contains values {ssbWithCSI-IM, ssbWithNZP-IMR, csirsWithNZP-IMR, csi-RSWithoutIMR} representing {SSB as CMR with dedicated CSI-IM, SSB as CMR with dedicated NZP IMR, CSI-RS as CMR with dedicated NZP IMR configured, CSI-RS as CMR without dedicated IMR configured}.
    • - supportedSINR-meas-v1670 indicates a 4-bit bitmap {ssbWithCSI-IM, ssbWithNZP-IMR, csirsWithNZP-IMR, csi-RSWithoutIMR}, where the leftmost bit corresponds to ssbWithCSI-IM, the next bit corresponds to ssbWithNZP-IMR and so on. UE indicating supportedSINR-meas-v1670 shall always indicate supportedSINR-meas-r16.
UE supporting this feature shall also indicate support of CSI-RS as CMR with dedicated CSI-IM. UE indicating support of this feature shall also indicate support of periodicBeamReport and aperiodicBeamReport or sp-BeamReportPUCCH and sp-BeamReportPUSCH . UE indicating support of ssb-csirs-SINR-measurement-r16 shall support periodic and aperiodic L1-SINR report.

NOTE 1: The reference slot duration is the shortest slot duration defined for the frequency range where the reported band belongs.
NOTE 2: For maxNumberSSB-CSI-RS-res-r16 and maxNumberCSI-IM-NZP-IMR-res-mem-r16 the configured CSI-RS resources for both active and inactive BWPs are counted.
NOTE 3: For maxNumberSSB-CSI-RS-OneTx-CMR-r16 , maxNumberCSI-IM-NZP-IMR-res-r16 and maxNumberCSIRS-2Tx-res-r16 , CSI-RS resources configured as CMR without dedicated IMR are counted both as CMR and IMR.
NOTE 4: For maxNumberSSB-CSI-RS-OneTx-CMR-r16 , maxNumberCSI-IM-NZP-IMR-res-r16 , maxNumberCSIRS-2Tx-res-r16 , maxNumberAperiodicCSI-RS-Res-r16 , a SSB/CSI-RS resource is counted within the duration of a | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| sssg-Switching-1BitInd-r17
Indicates whether the UE supports 1-bit indication of SSSG switching between 2 SSSGs by scheduling DCI, and timer based SSSG switching, if pdcch-SkippingDurationList is not configured as specified in TS 38.213 [11], clause 10.4. UE supports search space set group switching capability-1 according to Table 10.4-1 of TS 38.213 [11]. | Band | No | N/A | N/A | +| sssg-Switching-2BitInd-r17
Indicates whether the UE supports 2-bit indication of SSSG switching among 3 SSSGs by scheduling DCI and timer based SSSG switching, if pdcch-SkippingDurationList is not configured as specified in TS 38.213 [11], clause 10.4. UE supports search space set group switching capability-1 according to Table 10.4-1 of TS 38.213 [11].

UE indicating support of this feature shall also indicate support of sssg-Switching-1bitInd-r17 . | Band | No | N/A | N/A | +| support-3MHz-ChannelBW-r18
Indicates whether the UE supports the following functional components:
  • - Reception of 12 PRB PBCH based on RB-level puncturing;
  • - Short RACH preamble formats with 15kHz SCS, and long PRACH formats with 1.25kHz SCS;
  • - Reception of 15 PRB CORESET0.
This feature is supported for 15kHz SCS only. It is applicable only when an associated SS/PBCH block is located according to Table 5.4.3.3-2 in TS 38.101-1 [2].

NOTE: The UE supporting this capability supports configuration of 15 PRB BWP operation. | Band | No | FDD only | FR1 only | +| support-12PRB-CORESET0-r18
Indicates whether the UE supports reception of 12 PRB CORESET0.
A UE supporting this feature shall also indicate support of support-3MHz-ChannelBW-r18 .
This feature is supported for 15kHz SCS only.

NOTE: The UE supporting this capability supports configuration of 12 PRB BWP operation. | Band | No | FDD only | FR1 only | +| support64CandidateBeamRS-BFR-r16
Indicates UE support of configuring maximum 64 candidate beam RSs per BWP per CC. UE indicating support of this feature shall also indicate support of maxNumberCSI-RS-BFD , maxNumberSSB-BFD and maxNumberCSI-RS-SSB-CBD . | Band | No | N/A | N/A | +| supportCodeWordSoftCombining-r16
Indicates whether UE supports codeword soft combining for FDMSchemeB. UE indicates support of this feature depends on whether the supportFDM-SchemeB-r16 is also supported. | Band | No | N/A | N/A | +| supportFDM-SchemeA-r16
Indicates whether UE supports single DCI based FDMSchemeA. | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| supportInter-slotTDM-r16
Indicates whether UE supports single-DCI based inter-slot TDM. This capability signalling includes the following:
  • - supportRepNumPDSCH-TDRA-r16 indicates support of repetitionNumber-r16 in PDSCH-TimeDomainResourceAllocation-r16 and the maximum value of repetitionNumber-r16
  • - maxTBS-Size-r16 indicates maximum TBS size.
  • - maxNumberTCI-states-r16 indicates the maximum number of TCI states.
| Band | No | N/A | N/A | +| supportNewDMRS-Port-r16
Indicates whether UE supports new DMRS port entry {0,2,3}. UE supports this feature should indicate support singleDCI-SDM-scheme-r16 for the band. | Band | No | N/A | N/A | +| supportRepNumPDSCH-TDRA-DCI-1-2-r17
Indicates support of repetitionNumber-v1730 in PDSCH-TimeDomainResourceAllocation for DCI format 1_2 and the maximum value of repetitionNumber-v1730 . The UE indicating support of this field shall also indicate support of dci-Format1-2And0-2-r16 . | Band | No | N/A | N/A | +| supportTDM-SchemeA-r16
Indicates whether UE supports single DCI based TDMSchemeA. The capability signalling includes the maximum TBS size. | Band | No | N/A | N/A | +| supportTwoPortDL-PTRS-r16
Indicates whether UE supports 2-port DL PT-RS. UE supports this feature should indicate support singleDCI-SDM-scheme-r16 for the band. | Band | No | N/A | N/A | +| ta-BasedPDC-NTN-SharedSpectrumChAccess-r17
Indicates whether the UE supports propagation delay compensation based on Rel-15 TA procedure for NTN and shared spectrum channel access. | Band | No | N/A | N/A | +| ta-IndicationCellSwitch-r18
Indicates whether the UE supports TA indication in cell switch command. | Band | No | N/A | N/A | +| tb-ProcessingMultiSlotPUSCH-r17
Indicates whether UE supports TB processing over multi-slot PUSCH for DG and Type 2 CG without repetition in RRC connected mode. | Band | No | N/A | N/A | +| tb-ProcessingRepMultiSlotPUSCH-r17
Indicates whether UE supports repetition of TB processing over multi-slot PUSCH in RRC connected mode.

UE supporting this feature shall also indicates support of tb-ProcessingMultiSlotPUSCH-r17 . | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| tci-StatePDSCH
Defines support of TCI-States for PDSCH. The capability signalling comprises the following parameters:
  • - maxNumberConfiguredTCIstatesPerCC indicates the maximum number of configured TCI-states per CC for PDSCH. For FR2, the UE is mandated to set the value at least to 64 (i.e. value 128 is an optional value). For FR1, the UE is mandated to set these values at least to the maximum number of allowed SSBs in the supported band;
  • - maxNumberActiveTCI-PerBWP indicates the maximum number of activated TCI-states per BWP per CC, including control and data. If a UE reports X active TCI state(s), it is not expected that more than X active QCL type D assumption(s) for any PDSCH and any CORESETs for a given BWP of a serving cell become active for the UE. The UE shall include this field.
Note the UE is required to track only the active TCI states.

The UE is mandated to report tci-StatePDSCH . | Band | Yes | N/A | N/A | +| tci-JointTCI-UpdateMultiActiveTCI-PerCC-r18
Indicates whether the UE supports unified TCI with joint DL/UL TCI update for single-DCI based intra-cell multi-TRP with multiple activated TCI codepoints per CC. The capability signaling comprises the following parameters:
  • - tci-StateInd-r18 indicates TCI state indication for update and activation. Value withAssignment corresponds to MAC-CE+DCI-based TCI state indication (use of monitored DCI formats 1_1 and if supported 1_2) with DL assignment, value withoutAssignment corresponds to MAC-CE+DCI-based TCI state indication (use of monitored DCI formats 1_1 and if supported 1_2) without DL assignment;
  • - maxNumberActiveJointTCI-PerCC-r18 indicates the maximum number of activated joint TCI states per CC.
A UE supporting this feature shall also indicate support FG40-1-1.

NOTE: defaultQCL-TwoTCI-r16 can be used to indicate support of two default beams | Band | No | N/A | N/A | +| tci-SelectionAperiodicCSI-RS-r18
Indicates whether the UE supports per aperiodic CSI-RS resource/resource set configuration for TCI selection in S-DCI based MTRP. | Band | No | N/A | N/A | +| tci-SelectionDCI-r18
Indicates whether the UE supports DCI format 1_1 and if supported 1_2 configured with TCI selection field.
The UE supporting this feature shall also indicates support at least one of tci-JointTCI-UpdateMultiActiveTCI-PerCC-r18 , tci-SeperateTCI-UpdateSingleActiveTCI-PerCC-r18 , and 40-1-1/2a. | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| tci-SeparateTCI-UpdateSingleActiveTCI-PerCC-r18
Indicates whether the UE supports Unified TCI with separate DL/UL TCI update for single-DCI based intra-cell multi-TRP with single activated TCI codepoint per CC.
The capability signalling comprises the following parameters:
  • - maxNumConfigDL-TCI-PerCC-PerBWP-r18 indicates the maximum number of configured DL TCI states per CC per BWP ,
  • - maxNumConfigUL-TCI-PerCC-PerBWP-r18 indicates the maximum number of configured UL TCI states per CC per BWP.
  • - maxNumActiveDL-TCI-AcrossCC-r18 indicates the maximum number of activated DL TCI states across all CCs,
  • - maxNumActiveUL-TCI-AcrossCC-r18 indicates the maximum number of activated UL TCI states across all CCs.
A UE supporting this feature shall also indicate support of FG40-1-1 and unifiedJointTCI-commonUpdate-r17 .

NOTE: defaultQCL-TwoTCI-r16 can be used to indicate support of two default beams | Band | No | N/A | N/A | +| timeBasedCondHandover-r17
Indicates whether the UE supports time based conditional handover, i.e., CondEvent T1 as specified in TS 38.331 [9]. A UE supporting this feature shall also indicate the support of condHandover-r16 for NTN bands and the support of nonTerrestrialNetwork-r17 . UE shall set the capability value consistently for all FDD-FR1 NTN bands. | Band | No | N/A | N/A | +| triggeredHARQ-CodebookRetx-r17
Indicates whether the UE supports triggered HARQ-ACK codebook re-transmission from an earlier PUCCH slot based on the triggering information in DCI format 1_1 and DCI format 1_2 (for a UE supporting DCI format 1_2 as indicated in dci-Format1-2And0-2-r16 ) and support the related PHY priority handling in terms of HARQ-ACK codebook selection and the applicable PUCCH configuration (for a UE supporting two HARQ-ACK codebooks / PUCCH config as indicated in twoHARQ-ACK-Codebook-type1-r16 ). The capability signalling comprises the following parameters:
  • - minHARQ-Retx-Offset-r17 indicates minimum value for the HARQ re-tx offset. Value n-7 corresponds to -7, value n-5 corresponds to -5, and so on.
  • - maxHARQ-Retx-Offset-r17 indicates maximum value for the HARQ re-tx offset.
NOTE: The minimum requirement for minHARQ-Retx-Offset-r17 and maxHARQ-Retx-Offset-r17 is valid for HARQ CBs consisted of HARQ Processes with a single HARQ bit per HARQ Process ID. | Band | No | N/A | N/A | +| trs-AdditionalBandwidth-r16
Indicates the UE supported TRS bandwidths, in addition to 52 RBs, for a 10MHz UE channel bandwidth. This field only applies for the BWPs configured with 52 RBs size and 15kHz SCS, in FDD bands.
Value trs-AddBW-Set1 indicates 28, 32, 36, 40, 44, 48 RBs.
Value trs-AddBW-Set2 indicates 32, 36, 40, 44, 48 RBs. | Band | No | FDD only | FR1 only | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| twoHARQ-ACK-CodebookForUnicastAndMulticast-r17
Indicates whether the UE supports two HARQ-ACK codebooks simultaneously constructed for supporting HARQ-ACK codebooks with different priorities for unicast and multicast at a UE.

For TN, the UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands and all TDD-FR2 bands, associated with supported shared and non-shared spectrum respectively. For NTN, UE shall set the capability value consistently for all FDD-FR1 NTN bands.

A UE supporting this feature shall also indicate support of priorityIndicatorInDCI-Multicast-r17 . | Band | No | N/A | N/A | +| twoPortsPTRS-UL
Defines whether UE supports PT-RS with 2 antenna ports for UL transmission. | Band | No | N/A | N/A | +| twoPUSCH-CB-MultiDCI-STx2P-FullTimeFullFreqOverlap-r18
Indicates whether the UE supports fully overlapping PUSCHs in time and fully overlapping in frequency for codebook multi-DCI based STx2P PUSCH+PUSCH.
A UE supporting this feature shall also indicate support of twoPUSCH-CB-MultiDCI-STx2P-DG-DG-r18 . | Band | No | N/A | FR2 only | +| twoPUSCH-CB-MultiDCI-STx2P-FullTimePartialFreqOverlap-r18
Indicates whether the UE supports fully overlapping PUSCHs in time and partially overlapping in frequency for codebook multi-DCI based STx2P PUSCH+PUSCH.
A UE supporting this feature shall also indicate support of twoPUSCH-CB-MultiDCI-STx2P-DG-DG-r18 . | Band | No | N/A | FR2 only | +| twoPUSCH-CB-MultiDCI-STx2P-PartialTimeFullFreqOverlap-r18
Indicates whether the UE supports partially overlapping PUSCHs in time and fully overlapping in frequency for codebook multi-DCI based STx2P PUSCH+PUSCH.
A UE supporting this feature shall also indicate support of twoPUSCH-CB-MultiDCI-STx2P-DG-DG-r18 . | Band | No | N/A | FR2 only | +| twoPUSCH-CB-MultiDCI-STx2P-PartialTimeNonFreqOverlap-r18
Indicates whether the UE supports the partially overlapping PUSCHs in time, non-overlapping in frequency for codebook multi-DCI based STx2P PUSCH+PUSCH.
A UE supporting this feature shall also indicate support of twoPUSCH-CB-MultiDCI-STx2P-DG-DG-r18 . | Band | No | N/A | FR2 only | +| twoPUSCH-CB-MultiDCI-STx2P-PartialTimePartialFreqOverlap-r18
Indicates whether the UE supports the partially overlapping PUSCHs in time, partially overlapping in frequency for codebook multi-DCI based STx2P PUSCH+PUSCH.
A UE supporting this feature shall also indicate support of twoPUSCH-CB-MultiDCI-STx2P-DG-DG-r18 . | Band | No | N/A | FR2 only | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| twoRateMatchingEUTRA-CRS-patterns-3-4-r18
Indicates whether the UE supports two LTE-CRS overlapping rate matching patterns configured by lte-CRS-PatternList3-r18 and lte-CRS-PatternList4-r18 within a part of NR carrier using 15 kHz overlapping with a LTE carrier (regardless of support or configuration of multi-TRP) for the case when crs-RateMatchPerCoresetPoolIndex is not configured. The capability signalling comprises the following parameters:
  • - maxNumberPatterns-r18 indicates the maximum number of LTE-CRS rate matching patterns in total within a NR carrier using 15 kHz SCS.
  • - maxNumberNon-OverlapPatterns-r18 indicates the maximum number of LTE-CRS non-overlapping rate matching patterns within a NR carrier using 15 kHz SCS.
UE supporting this feature shall support rateMatchingLTE-CRS .

NOTE: If a UE supports this feature and multipleRateMatchingEUTRA-CRS-r16 , multipleRateMatchingEUTRA-CRS-r16 is reported for lte-CRS-PatternList1-r16 and lte-CRS-PatternList2-r16 and twoRateMatchingEUTRA-CRS-patterns-3-4-r18 is reported for lte-CRS-PatternList3-r16 and lte-CRS-PatternList4-r16 . | Band | No | N/A | FR1 only | +| twoTCI-StatePDSCH-CJT-TxScheme-r18
Indicates whether the UE supports two TCI states for CJT Tx scheme for PDSCH. Value cjtSchemeA corresponds to PDSCH DMRS port(s) is QCled with the DL RSs of both indicated joint/DL TCI states with respect to QCL-TypeA, value cjtSchemeB corresponds to PDSCH DMRS port(s) is QCled with the DL RSs of both indicated joint/DL TCI states with respect to QCL-TypeA except for QCL parameters {Doppler shift, Doppler spread} of the second indicated joint/DL TCI state. Value both corresponds to the supporting of both cjtSchemeA and cjtSchemeB . | Band | No | N/A | N/A | +| type1-HARQ-Codebook-r17
Indicates whether the UE supports Type-1 HARQ codebook enhancements when there are feedback-disabled HARQ processes. UE indicating support of this feature shall also indicate support of harq-FeedbackDisabled-r17 . This field is only applicable for bands in Table 5.2.2-1 in TS 38.101-5 [34] and HAPS operation bands in clause 5.2 of TS 38.104 [35]. | Band | No | N/A | N/A | +| type2-HARQ-Codebook-r17
Indicates whether the UE supports Type-2 HARQ codebook enhancements when there are feedback-disabled HARQ processes. UE indicating support of this feature shall also indicate support of harq-FeedbackDisabled-r17 . This field is only applicable for bands in Table 5.2.2-1 in TS 38.101-5 [34] and HAPS operation bands in clause 5.2 of TS 38.104 [35]. | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| type1-PUSCH-RepetitionMultiSlots-v1650
Indicates whether the UE supports Type 1 PUSCH transmissions with configured grant as specified in TS 38.214 [12] with UL-TWG-repK value equal to 2, 4, or 8 with a single repetition of the transport block within each slot, and redundancy version pattern as indicated by UL-TWG-RV-rep. A UE supporting this feature shall also support Type 1 PUSCH transmissions with configured grant as specified in TS 38.214 [12] with UL-TWG-repK value of one. This applies only to non-shared spectrum channel access. For shared spectrum channel access, type1-PUSCH-RepetitionMultiSlots-r16 applies. UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands, all TDD-FR2-1 bands and all TDD-FR2-2 bands respectively.

The UE only includes type1-PUSCH-RepetitionMultiSlots-v1650 if type1-PUSCH-RepetitionMultiSlots is absent | Band | No | N/A | N/A | +| type2-PUSCH-RepetitionMultiSlots-v1650
Indicates whether the UE supports Type 2 PUSCH transmissions with configured grant as specified in TS 38.214 [12] with UL-TWG-repK value equal to 2, 4, or 8 with a single repetition of the transport block within each slot, and redundancy version pattern as indicated by UL-TWG-RV-rep. A UE supporting this feature shall also support Type 2 PUSCH transmissions with configured grant as specified in TS 38.214 [12] with UL-TWG-repK value of one. This applies only to non-shared spectrum channel access. For shared spectrum channel access, type2-PUSCH-RepetitionMultiSlots-r16 applies. UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands, all TDD-FR2-1 bands and all TDD-FR2-2 bands respectively.

The UE only includes type2-PUSCH-RepetitionMultiSlots-v1650 if type2-PUSCH-RepetitionMultiSlots is absent | Band | No | N/A | N/A | +| type3-HARQ-Codebook-r17
Indicates whether the UE supports Type-3 HARQ codebook enhancements when there are feedback-disabled HARQ processes. UE indicating support of this feature shall also indicate support of harq-FeedbackDisabled-r17 . This field is only applicable for bands in Table 5.2.2-1 in TS 38.101-5 [34] and HAPS operation bands in clause 5.2 of TS 38.104 [35]. | Band | No | N/A | N/A | +| txDiversity-r16
Indicates whether the UE supports transparent Tx diversity requirements as specified in the suffix G clauses of TS 38.101-1 [2] (see also clauses 4.2 and 4.3 of TS 38.101-1 [2]). | Band | No | N/A | FR1 only | +| ue-OneShotUL-TimingAdj-r17
Indicates whether the UE supports one shot large UL timing adjustment.

UE indicating support of this feature shall indicate support of ue-PowerClass-v1700 set to 'pc6'. | Band | No | N/A | FR2 only | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ue-PowerClass, ue-PowerClass-v1610, ue-PowerClass-v1700
For FR1, if the UE supports the different UE power class than the default UE power class as defined in clause 6.2 of TS 38.101-1 [2], or in clause 6.2 of TS 38.101-5 [34], the UE shall report the supported UE power class in this field. For FR2, UE shall report the supported UE power class as defined in clause 6 and 7 of TS 38.101-2 [3] in this field. UE indicating support for pc6 supports the enhanced intra-NR RRM and demodulation processing requirements for FR2 to support high speed up to 350 km/h as specified in TS 38.133 [5]. This capability is not applicable to IAB-MT. The power class pc7 is only applicable for RedCap UEs operation in FR2. This capability is not applicable for UEs indicating support of maxOutputPowerATG-r18 . | Band | Yes | N/A | N/A | +| ue-specific-K-Offset-r17
Indicates whether the UE supports the reception of UE-specific K_offset comprised of the following functional components:
  • - Support of reception of UE-specific K_offset via MAC-CE
  • - Support of determining the timing of PUSCH, PUCCH, CSI reference resource, transmission of aperiodic SRS, activation of TA command, first PUSCH transmission in CG Type 2 with UE-specific Koffset
UE indicating support of this feature shall also indicate support of uplinkPreCompensation-r17 and uplink-TA-Reporting-r17 for this band. This field is only applicable for bands in Table 5.2.2-1 in TS 38.101-5 [34] and HAPS operation bands in clause 5.2 of TS 38.104 [35]. | Band | No | N/A | N/A | +| ue-TA-Measurement-r18
Indicates whether the UE supports UE-based TA measurement by indicating the maximum number of candidate cells that the UE maintains the TA for. | Band | No | N/A | N/A | +| ul-GapFR2-r17
Indicates whether the UE supports FR2 UL gap to perform BPS sensing for Tx power management by the use of uplink gap patterns as specified in TS 38.133 [5] if UE supports a band in FR2. | Band | No | No | FR2 only | +| unifiedJointTCI-BeamAlignDLRS-r17
Indicates the support of beam misalignment between the DL source RS in the TCI state to provide spatial relation indication and the PL-RS. The UE indicating support of this feature shall also indicate support of unifiedJointTCI-r17 . | Band | No | N/A | FR2 only | +| unifiedJointTCI-commonMultiCC-r17
Indicates the support of common multi-CC TCI state ID update and activation. The UE indicating support of this feature shall also indicate support of unifiedJointTCI-r17 . | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| unifiedJointTCI-InterCell-r17
Indicates the support of Unified TCI with joint DL/UL TCI update for inter-cell beam management including following parameters:
  • - additionalMAC-CE-PerCC-r17 indicates the number of K additional MAC-CEs to indicate joint TCI states per CC in a band.
  • - additionalMAC-CE-AcrossCC-r17 indicates the number of K additional MAC-CE activated joint TCI states across all CC(s) in a band.
A UE indicating support of this shall also indicate support of unifiedJointTCI-r17 and unifiedJointTCI-mTRP-InterCell-BM-r17 .

NOTE: A UE that supports unifiedJointTCI-InterCell-r17 supports K additional MAC-CE activated joint TCI states across all CC(s) in a band in addition to the maximum number of MAC-CE activated joint TCI states across all CC(s) in a band signalled in unifiedJointTCI-r17 . The signalled value in additionalMAC-CE-AcrossCC-r17 plus the signalled value in maxActivatedTCIAcrossCC-r17 determine the maximum number of MAC-CE activated joint TCI states across all CC(s) in a band that are applied to intra and inter-cell beam management jointly. | Band | No | N/A | N/A | +| unifiedJointTCI-Legacy-CORESET0-r17
Indicates the support of indication/configuration of R17 TCI states for CORESET #0 and the respective PDSCH reception reusing the Rel-15/16 signalling/configuration design(s).
The UE indicating support of this feature shall also indicate support of unifiedJointTCI-r17 . | Band | No | N/A | N/A | +| unifiedJointTCI-Legacy-SRS-r17
Indicates the support of indication/configuration of R17 TCI states for SRS (except for periodic/semi-persistent SRS for BM) reusing the Rel-15/16 signalling/configuration design(s).
The UE indicating support of this feature shall also indicate support of unifiedJointTCI-r17 . | Band | No | N/A | N/A | +| unifiedJointTCI-Legacy-r17
Indicates the support of indication/configuration of R17 TCI states for aperiodic CSI-RS, PDCCH, PDSCH (except for TRS and for CORESET #0 and the respective PDSCH reception) reusing the Rel-15/16 signalling/configuration design(s).
The UE indicating support of this feature shall also indicate support of unifiedJointTCI-r17 . | Band | No | N/A | N/A | +| unifiedJointTCI-ListSharingCA-r17
Indicates the support of reference BWP/serving cell index to indicate reference TCI state list shared by multiple BWPs/serving cells. The value indicates the maximum number of configured joint TCI state lists across all BWPs and all Serving cells in a band.

The UE indicating support of this feature shall also indicate support of unifiedJointTCI-r17 . A UE that supports CA and unifiedJointTCI-r17 shall indicate support of this feature. | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| unifiedJointTCI-mTRP-InterCell-BM-r17
Indicates the support of inter-cell beam measurement and reporting for inter-cell BM and mTRP. This feature includes support of L1-RSRP measurement and reporting on SSB(s) with PCI(s) different from serving cell PCI (additional PCI) and support of up to K SSBRI-RSRP pairs in one report where a pair is associated with a PCI different from serving cell PCI can be reported, where K is equal to maxNumberNonGroupBeamReporting .

This feature also includes following parameters:
  • - maxNumAdditionalPCI-L1-RSRP-r17 indicates the maximum number of RRC-configured] PCI(s) different from serving cell PCI for L1-RSRP measurement.
  • - maxNumSSB-ResourceL1-RSRP-AcrossCC-r17 indicates the maximum number of SSB resources configured to measure L1-RSRP within a slot with PCI(s) same as or different from serving cell PCI [across all CC].
NOTE: maxNumSSBResource-L1-RSRP-AcrossCC-r17 is also counted in maxTotalResourcesForOneFreqRange-r16/ maxTotalResourcesForAcrossFreqRanges-r16 . | Band | No | N/A | N/A | +| unifiedJointTCI-multiMAC-CE-r17
Indicates the support of unified TCI state operation with joint DL/UL TCI update for intra- and inter-cell beam management with more than one MAC-CE activated joint TCI state per CC with MAC CE and DCI based TCI state indication in DCI formats 1_1 and 1_2 with and without DL assignment.
This capability signalling includes the following parameters:
  • - minBeamApplicationTime-r17 indicates the minimum beam application time in Y symbols per SCS indicated only for FR2.
  • - maxNumMAC-CE-PerCC-r17 indicates the maximum number of MAC-CE activated joint TCI states per CC in a band.
The UE indicating support of this feature shall also indicate support of unifiedJointTCI-r17 .

NOTE 1: The maximum number of MAC-CE activated joint TCI states across all CC(s) in a band for more than one MAC-CE activated joint TCI state is signaled in unifiedJointTCI-r17 .
NOTE 2: Activated joint TCI state(s) include all PDCCH/PDSCH receptions and PUSCH/PUCCH. | Band | No | N/A | N/A | +| unifiedJointTCI-PC-association-r17
Indicates the support of association between TCI state and UL PC settings except for PL RS for PUCCH, PUSCH, and SRS.
The UE indicating support of this feature shall also indicate support of unifiedJointTCI-r17 . | Band | No | N/A | N/A | +| unifiedJointTCI-perBWP-CA-r17
Indicates the support of TCI state list configuration per BWP when CA is configured.
The UE indicating support of this feature shall also indicate support of unifiedJointTCI-r17 . | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| unifiedJointTCI-r17
Indicates the support of unified TCI state operation with joint DL/UL TCI update for intra-cell beam management including the support of:
  • - One MAC-CE activated joint TCI state per CC in a band
  • - TCI state indication for update and activation of MAC CE based TCI state indication for one active TCI state
The capability signalling comprises the following parameters:
  • - maxConfiguredJointTCI-r17 indicates the maximum number of configured joint TCI states per BWP per CC in a band
  • - maxActivatedTCIAcrossCC-r17 indicates the maximum number of MAC-CE activated joint TCI states across all CC(s) in a band
If a UE supports unifiedJointTCI-InterCell-r17 , the signalled component values (except additionalMAC-CE-AcrossCC-r17 ) also apply to inter-cell beam management,

NOTE: Activated joint TCI state(s) include all PDCCH/PDSCH receptions and PUSCH/PUCCH transmissions | Band | No | N/A | N/A | +| unifiedJointTCI-SCellBFR-r17
Indicates the support of SCell BFR with unified TCI operation. The maximum number of CCs configured with SCell BFR with unified TCI framework in a band with SpCell BFR is given by maxNumberSCellBFR-r16 . The UE supporting this feature assumes that maxNumberSCellBFR-r16 includes SpCell. | Band | No | N/A | N/A | +| unifiedSeparateTCI-commonMultiCC-r17
Indicates the Common multi-CC DL/UL-TCI state ID update and activation.

The UE indicating support of this feature shall also indicate support of unifiedSeparateTCI-r17 . | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| unifiedSeparateTCI-InterCell-r17
Indicates the support of unified TCI with separate DL/UL TCI update for inter-cell beam management with more than one MAC-CE activated separate TCI state per CC.

This feature also includes following parameters:
  • - k-DL-PerCC-r17 indicates the number of additional MAC-CE activated DL TCI states per CC in a band
  • - k-UL-PerCC-r17 indicates the number of additional MAC-CE activated UL TCI states per CC in a band
  • - k-DL-AcrossCC-r17 indicates the number of additional MAC-CE activated DL TCI states across all CC(s) in a band
  • - k-UL-AcrossCC-r17 indicates the number of additional MAC-CE activated UL TCI states across all CC(s) in a band
The UE indicating support of this feature shall also indicate support of unifiedSeparateTCI-r17 .

NOTE: A UE that supports this feature supports K additional MAC-CE activated DL and K additional MAC-CE activated UL TCI states across all CC(s) in a band in addition to the maximum number of MAC-CE activated DL and UL TCI states across all CC(s) in a band signalled in unifiedSeparateTCI-r17 . The signalled value in k-DL-AcrossCC-r17 ( k-UL-AcrossCC-r17 ) plus the signalled value in maxActivatedDL-TCIAcrossCC-r17 ( maxActivatedUL-TCIAcrossCC-r17 ) determine the maximum number of MAC-CE activated DL (UL) TCI states across all CC(s) in a band that are applied to intra and inter-cell beam management jointly. | Band | No | N/A | N/A | +| unifiedSeparateTCI-ListSharingCA-r17
Indicates the support of reference BWP/serving cell configured with reference TCI state pool shared by a set of BWPs/serving cells. The value indicates the maximum number of configured DL/UL TCI state pools across all BWPs and all serving cells in a band. | Band | No | N/A | N/A | +| unifiedSeparateTCI-multiMAC-CE-r17
Indicates TCI state indication for update and activation a) MAC-CE+DCI-based TCI state indication (use of DCI formats 1_1/1_2 with DL assignment) And b) MAC-CE+DCI-based TCI state indication (use of DCI formats 1_1/1_2 without DL assignment).

This capability signalling includes the following parameters:
  • - minBeamApplicationTime-r17 indicates the minimum beam application time in Y symbols per SCS.
  • - maxActivatedDL-TCIPerCC-r17 indicates the maximum number of MAC-CE activated DL TCI states per CC in a band
  • - maxActivatedUL-TCIPerCC-r17 indicates the maximum number of MAC-CE activated UL TCI states per CC in a band
The UE indicating support of this feature shall also indicate support of unifiedSeparateTCI-r17 . | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| unifiedSeparateTCI-perBWP-CA-r17
Indicates the support of DL/UL TCI state pool configuration per BWP for CA mode.

The UE indicating support of this feature shall also indicate support of unifiedSeparateTCI-r17 . | Band | No | N/A | N/A | +| unifiedSeparateTCI-r17
Indicates the support of unified TCI state operation with joint DL/UL TCI update for intra-cell beam management including the support of:
  • - One MAC-CE activated DL TCI state per CC in a band
  • - One MAC-CE activated UL TCI state per CC in a band
  • - TCI state indication for update and activation including MAC CE based TCI state indication for one active DL/UL TCI state
The capability signalling comprises the following parameters:
  • - maxConfiguredDL-TCI-r17 indicates the maximum number of configured DL TCI states per BWP per CC
  • - maxConfiguredUL-TCI-r17 indicates the maximum number of configured UL TCI states per BWP per CC
  • - maxActivatedDL-TCIAcrossCC-r17 indicates the maximum number of MAC-CE activated DL TCI states across all CC(s) in a band
  • - maxActivatedUL-TCIAcrossCC-r17 indicates the maximum number of MAC-CE activated UL TCI states across all CC(s) in a band
The UE indicating support of this feature shall also indicate support of unifiedJointTCI-r17 . If a UE supports unifiedSeparateTCI-InterCell-r17 , the maxConfiguredDL-TCI-r17 and maxConfiguredUL-TCI-r17 apply to intra- and inter-cell beam management jointly. | Band | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|--------------|---|---|---|---|---|---|---|---|---|---|---|---|---|---|------|----|-----|----------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | | | | | | | | | | | | | | | | | | | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | | | | | | | | | | | | | | | | | | | +| uplinkBeamManagement
Defines support of beam management for UL. This capability signalling comprises the following parameters:
  • - maxNumberSRS-ResourcePerSet-BM indicates the maximum number of SRS resources per SRS resource set configurable for beam management, supported by the UE.
  • - maxNumberSRS-ResourceSet indicates the maximum number of SRS resource sets configurable for beam management, supported by the UE.
If the UE does not set beamCorrespondenceWithoutUL-BeamSweeping to supported , the UE shall report this capability. This feature is optional for the UE that supports beam correspondence without uplink beam sweeping as defined in clause 6.6, TS 38.101-2 [3].

NOTE: The network uses maxNumberSRS-ResourceSet to determine the maximum number of SRS resource sets that can be configured to the UE for periodic/semi-persistent/aperiodic configurations as below:

Maximum number of SRS resource sets across all time domain behaviour (periodic/semi-persistent/aperiodic) reported in maxNumberSRS-ResourceSet Additional constraint on the maximum number of SRS resource sets configured to the UE for each supported time domain behaviour (periodic/semi-persistent/aperiodic)
11
21
31
42
52
62
74
84
| Maximum number of SRS resource sets across all time domain behaviour (periodic/semi-persistent/aperiodic) reported in maxNumberSRS-ResourceSet | Additional constraint on the maximum number of SRS resource sets configured to the UE for each supported time domain behaviour (periodic/semi-persistent/aperiodic) | 1 | 1 | 2 | 1 | 3 | 1 | 4 | 2 | 5 | 2 | 6 | 2 | 7 | 4 | 8 | 4 | Band | No | N/A | FR2 only | +| Maximum number of SRS resource sets across all time domain behaviour (periodic/semi-persistent/aperiodic) reported in maxNumberSRS-ResourceSet | Additional constraint on the maximum number of SRS resource sets configured to the UE for each supported time domain behaviour (periodic/semi-persistent/aperiodic) | | | | | | | | | | | | | | | | | | | | | | +| 1 | 1 | | | | | | | | | | | | | | | | | | | | | | +| 2 | 1 | | | | | | | | | | | | | | | | | | | | | | +| 3 | 1 | | | | | | | | | | | | | | | | | | | | | | +| 4 | 2 | | | | | | | | | | | | | | | | | | | | | | +| 5 | 2 | | | | | | | | | | | | | | | | | | | | | | +| 6 | 2 | | | | | | | | | | | | | | | | | | | | | | +| 7 | 4 | | | | | | | | | | | | | | | | | | | | | | +| 8 | 4 | | | | | | | | | | | | | | | | | | | | | | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17
Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17 . | Band | No | N/A | N/A | +| uplinkPreCompensation-r17
Indicates whether the UE supports the uplink time and frequency pre-compensation and timing relationship enhancements comprised of the following functional components:
  • - Support of UE specific TA calculation based on its GNSS-acquired position and the serving satellite ephemeris.
  • - Support of common TA calculation according to the parameters provided by the network (UE considers common TA as 0 if the parameters are not provided)
  • - For TA update in RRC_CONNECTED state, support of combination of both open (i.e. UE autonomous TA estimation, and common TA estimation) and closed (i.e., received TA commands) control loops
  • - Support of pre-compensation of the calculated TA in its uplink transmissions
  • - Support of estimating UE-gNB RTT and delaying the start of RAR window by UE-gNB RTT
  • - Support of frequency pre-compensation to counter shift the Doppler experienced on the service link
  • - Support of determining timing of the scheduling of PUSCH, PUCCH and PDCCH ordered PRACH, CSI reference resource, transmission of aperiodic SRS activation of TA command, first PUSCH transmission in CG Type 2 with cell-specific K_offset if indicated
  • - Support of determining timing of the UE action and assumption on a downlink configuration carried by MAC CE command by K_mac if it is indicated and determining the timing of PDCCH monitoring in recovery search space using K-mac during beam failure recovery procedure
  • - Support of UE receiving cell-specific K_offset/K_mac in system information
Support of this feature in NTN bands is mandatory for UE supporting nonTerrestrialNetwork-r17 . This field is only applicable for bands in Table 5.2.2-1 in TS 38.101-5 [34] and HAPS operation bands in clause 5.2 of TS 38.104 [35]. | Band | CY | N/A | N/A | +| uplink-TA-Reporting-r17
Indicates whether the UE supports UE reporting of information related to TA pre-compensation as specified in TS 38.321 [8]. UE indicating support of this feature shall also indicate support of uplinkPreCompensation-r17 for this band. This field is only applicable for bands in Table 5.2.2-1 in TS 38.101-5 [34] and HAPS operation bands in clause 5.2 of TS 38.104 [35]. | Band | No | N/A | N/A | + +4.2.7.2a *SharedSpectrumChAccessParamsPerBand* + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| ul-DynamicChAccess-r16
Indicates whether the UE supports UL channel access for dynamic channel access mode.
Support of this feature is mandatory if UE supports any of the deployment scenarios A.2, B, C, D and E in Annex B.3 of TS 38.300 [28] with dynamic channel access mode. | Band | CY | N/A | N/A | +| ul-Semi-StaticChAccess-r16
Indicates whether the UE supports UL channel access for semi-static channel access mode.
Support of this feature is mandatory if UE supports any of the deployment scenarios A.2, B, C, D and E in Annex B.3 of TS 38.300 [28] with semi-static channel access mode. | Band | CY | N/A | N/A | +| ssb-RRM-DynamicChAccess-r16
Indicates whether the UE supports SSB-based RRM for dynamic channel access mode.
Support of this feature is mandatory if UE supports any of the deployment scenarios A.1, A.2, B, C, D and E in Annex B.3 of TS 38.300 [28] with dynamic channel access mode. | Band | CY | N/A | N/A | +| ssb-RRM-Semi-StaticChAccess-r16
Indicates whether the UE supports SSB-based RRM for semi-static channel access mode, when SMTC window is no longer than the fixed frame period.
Support of this feature is mandatory if UE supports any of the deployment scenarios A.1, A.2, B, C, D and E in Annex B.3 of TS 38.300 [28] with semi-static channel access mode. | Band | CY | N/A | N/A | +| mib-Acquisition-r16
Indicates whether the UE supports acquiring MIB on an unlicensed cell for SpCell.
Support of this feature is mandatory if UE supports any of the deployment scenarios B, C, D and E in Annex B.3 of TS 38.300 [28]. | Band | CY | N/A | N/A | +| ssb-RLM-DynamicChAccess-r16
Indicates whether the UE supports SSB-based RLM for dynamic channel access mode.
Support of this feature is mandatory if UE supports any of the deployment scenarios B, C, D and E in Annex B.3 of TS 38.300 [28] with dynamic channel access mode. | Band | CY | N/A | N/A | +| ssb-RLM-Semi-StaticChAccess-r16
Indicates whether the UE supports SSB-based RLM for semi-static channel access mode, when discovery burst transmission window is no longer than the fixed frame period.
Support of this feature is mandatory if UE supports any of the deployment scenarios B, C, D and E in Annex B.3 of TS 38.300 [28] with semi-static channel access mode. | Band | CY | N/A | N/A | +| sib1-Acquisition-r16
Indicates whether the UE supports acquiring SIB1 on an unlicensed cell for PCell.
Support of this feature is mandatory if UE supports any of the deployment scenarios C and D in Annex B.3 of TS 38.300 [28]. | Band | CY | N/A | N/A | +| extRA-ResponseWindow-r16
Indicates whether the UE supports the configuration of maximum length of RAR window with a value larger than 10ms and up to 40ms by decoding of the 2 LSBs of SFN in the DCI format 1_0 for 4-step RA type. Support of this feature is mandatory if the UE supports any of the deployment scenarios B, C, D and E in Annex B.3 of TS 38.300 [28]. | Band | CY | N/A | N/A | +| ssb-BFD-CBD-dynamicChannelAccess-r16
Indicates whether the UE supports SSB based Beam Failure Detection and Candidate Beam Detection with $N_{\text{SSB}}^{\text{QCL}}$ for dynamic channel access mode. | Band | No | N/A | N/A | +| ssb-BFD-CBD-semi-staticChannelAccess-r16
Indicates whether the UE supports SSB based Beam Failure Detection and Candidate Beam Detection with $N_{\text{SSB}}^{\text{QCL}}$ for semi-static channel access mode. | Band | No | N/A | N/A | +| csi-RS-BFD-CBD-r16
Indicates whether the UE supports CSI-RS based Beam Failure Detection and Candidate Beam Detection for shared spectrum operation. | Band | No | N/A | N/A | +| ul-ChannelBW-SCell-10mhz-r16
Indicates whether the UE supports 10 MHz of LBT bandwidth for an SCell. A UE that supports this feature shall also support ul-DynamicChAccess-r16 or ul-Semi-StaticChAccess-r16 . | Band | No | N/A | N/A | +| rssi-ChannelOccupancyReporting-r16
Indicates whether the UE supports RSSI measurements and channel occupancy | Band | No | N/A | N/A | + +| | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|-----|-----| +| reporting. | | | | | +| srs-StartAnyOFDM-Symbol-r16
Indicates whether the UE supports transmitting SRS starting in all symbols (0 to 13) of a slot. This capability is also applicable to a frequency band that does not require shared spectrum access. | Band | No | N/A | N/A | +| searchSpaceFreqMonitorLocation-r16
Indicates the maximum number of frequency domain locations supported by the UE, for a search space set configuration with freqMonitorLocations-r16 . | Band | No | N/A | N/A | +| coreset-RB-Offset-r16
Indicates whether the UE supports CORESET configuration with rb-Offset-r16 . This capability is also applicable to a frequency band that does not require shared spectrum access. | Band | No | N/A | N/A | +| cgi-Acquisition-r16
Indicates whether the UE supports acquisition of CGI information from a neighbouring NR unlicensed cell in an unlicensed carrier by reading SIB1 of the neighbouring unlicensed cell and reporting the acquired information to the network. | Band | No | N/A | N/A | +| configuredUL-Tx-r16
Indicates whether the UE supports configuration of enableConfiguredUL-r16 and enable transmission of higher-layer configured UL (SRS, PUCCH, CG-PUSCH, etc) when SFI field in DCI 2_0 is configured but DCI 2_0 is not detected. | Band | No | N/A | N/A | +| prach-Wideband-r16
Indicates whether the UE supports enhanced PRACH design for operation with shared spectrum channel access by adopting a single long ZC sequence, with ZC sequence = 1151 for 15 kHz and ZC sequence = 571 for 30 kHz. | Band | No | N/A | N/A | +| dci-AvailableRB-Set-r16
Indicates whether the UE supports monitoring DCI 2_0 to read available RB set indicator. | Band | No | N/A | N/A | +| dci-ChOccupancyDuration-r16
Indicates whether the UE supports monitoring DCI 2_0 to read COT duration. | Band | No | N/A | N/A | +| typeB-PDSCH-length-r16
Indicates whether the UE supports 1. Type B PDSCH length {3, 5, 6, 8, 9, 10, 11, 12, 13} without DMRS shift due to CRS collision. This capability is also applicable to a frequency band that does not require shared spectrum access. | Band | No | N/A | N/A | +| searchSpaceSwitchWithDCI-r16
Indicates whether the UE supports switching between two groups of search space sets with DCI 2_0 monitoring that comprises of the following functional components:
  • - Monitor DCI 2_0 with a search space set switching field;
  • - Support switching the search space set group with PDCCH decoding in group 1;
  • - Support a timer to switch back to original search space set group;
  • - Monitor DCI 2_0 for channel occupancy time and use the end of channel occupancy time to switch back to the original search space set group.
The UE can switch search space set groups for different cells independently, unless the UE supports jointSearchSpaceSwitchAcrossCells-r16 . The UE supports search space set group switching capability-1: P=25/25/25 symbols for $\mu=0/1/2$ , unless the UE supports searchSpaceSwitchCapability2-r16 . The UE supports search space switching triggers to be configured for up to 4 cells or 4 cell groups. | Band | No | N/A | N/A | +| extendedSearchSpaceSwitchWithDCI-r16
Indicates whether the UE supports search space switching triggers to be individually configured for up to 16 cells. UE indicating support of this feature shall indicate support of searchSpaceSwitchWithDCI-r16 . | Band | No | N/A | N/A | +| searchSpaceSwitchWithoutDCI-r16
Indicates whether the UE supports switching between two groups of search space sets without DCI 2_0 monitoring (i.e. implicit PDCCH decoding) that comprises of the following functional components:
  • - Support switching the search space set group with PDCCH decoding in group 1;
  • - Support a timer to switch back to original search space set group.
The UE can switch search space set groups for different cells independently, unless the UE supports jointSearchSpaceSwitchAcrossCells-r16 . The UE supports search space set group switching capability-1: P=25/25/25 symbols for $\mu=0/1/2$ , unless the UE supports searchSpaceSwitchCapability2-r16 . | Band | No | N/A | N/A | +| searchSpaceSwitchCapability2-r16 | Band | No | N/A | N/A | + +| | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|-----|-----| +| Indicates whether the UE supports search space set group switching Capability-2: P=10/12/22 symbols for $\mu = 0/1/2$ SCS. If the UE supports this feature, the UE needs to report searchSpaceSwitchWithDCI-r16 or searchSpaceSwitchWithoutDCI-r16 . | | | | | +| non-numericalPDSCH-HARQ-timing-r16
Indicates whether the UE supports configuration of a value for dl-DataToUL-ACK-r16 indicating an inapplicable time to report HARQ ACK. | Band | No | N/A | N/A | +| enhancedDynamicHARQ-codebook-r16
Indicates whether the UE supports enhanced dynamic HARQ codebook supporting grouping of HARQ ACK and triggering the retransmission of HARQ ACK in each group. The enhanced dynamic HARQ codebook comprises of the following functional components:
  • - Support of bit fields signalling PDSCH HARQ group index and NFI in DCI 1_1 (configuration of nfi-TotalDAI-Included);
  • - Support of bit field in DCI 0_1 for other group total DAI if configured. (configuration of ul-TotalDAI-Included);
  • - Support the retransmission of HARQ ACK (pdsch-HARQ-ACK-Codebook = enhancedDynamic-r16).
This capability is also applicable to a frequency band that does not require shared spectrum access. | Band | No | N/A | N/A | +| oneShotHARQ-feedback-r16
Indicates whether the UE supports one shot HARQ ACK feedback comprised of the following functional components:
  • - Support feedback of type 3 HARQ-ACK codebook, triggered by a DCI 1_1 scheduling a PDSCH;
  • - Support feedback of type 3 HARQ-ACK codebook, triggered by a DCI 1_1 without scheduling a PDSCH using a reserved FDRA value.
This capability is also applicable to a frequency band that does not require shared spectrum access. | Band | No | N/A | N/A | +| multiPUSCH-UL-grant-r16
Indicates whether the UE supports scheduling up to 8 PUSCH with a single DCI 0_1. This capability is also applicable to a frequency band that does not require shared spectrum access. | Band | No | N/A | N/A | +| csi-RS-RLM-r16
Indicates whether the UE supports CSI-RS based RLM for NR-Unlicensed. | Band | No | N/A | N/A | +| csi-RSRP-AndRSRQ-MeasWithSSB-r16
Indicates whether the UE can perform CSI-RSRP and CSI-RSRQ measurement as specified in TS 38.215 [13], where CSI-RS resource is configured with an associated SS/PBCH in shared spectrum channel access. | Band | No | N/A | N/A | +| csi-RSRP-AndRSRQ-MeasWithoutSSB-r16
Indicates whether the UE can perform CSI-RSRP and CSI-RSRQ measurement as specified in TS 38.215 [13], where CSI-RS resource is configured for a cell that transmits SS/PBCH block and without an associated SS/PBCH block in shared spectrum channel access. | Band | No | N/A | N/A | +| csi-SINR-Meas-r16
Indicates whether the UE can perform CSI-SINR measurements based on configured CSI-RS resources as specified in TS 38.215 [13] in shared spectrum channel access. If the UE supports this feature, the UE needs to report maxNumberCSI-RS-RRM-RS-SINR . UE indicating support of this feature shall indicate support of csi-RSRP-AndRSRQ-MeasWithSSB-r16 . | Band | No | N/A | N/A | +| ssb-AndCSI-RS-RLM-r16
Indicates whether the UE can perform radio link monitoring procedure based on measurement of SS/PBCH block and CSI-RS as specified in TS 38.213 [11] and TS 38.133 [5] in shared spectrum channel access. If the UE supports this feature, the UE needs to report maxNumberResource-CSI-RS-RLM .

UE indicating support of this feature shall indicate support of csi-RS-RLM-r16 and either ssb-RLM-DynamicChAccess-r16 or ssb-RLM-Semi-StaticChAccess-r16 . | Band | No | N/A | N/A | +| csi-RS-CFRA-ForHO-r16
Indicates whether the UE can perform reconfiguration with sync using a contention free random access with 4-step RA type on PRACH resources that are associated with CSI-RS resources of the target cell in shared spectrum channel access.

UE indicating support of this feature shall indicate support of either csi-RSRP- | Band | No | N/A | N/A | + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|-----|-----| +| AndRSRQ-MeasWithSSB-r16 or csi-RSRP-AndRSRQ-MeasWithoutSSB-r16. | | | | | +| periodicAndSemi-PersistentCSI-RS-r16
indicates whether the UE supports validating P/SP-CSI-RS reception when receiving a DCI granting a PDSCH over the same set of symbols, and when receiving a DCI triggering an A-CSI-RS over the same set of symbols. | Band | No | N/A | N/A | +| pusch-PRB-interlace-r16
Indicates whether the UE supports PRB interlace frequency domain resource allocation for PUSCH. | Band | No | N/A | N/A | +| pucch-F0-F1-PRB-Interlace-r16
Indicates whether the UE supports PRB interlace frequency domain resource allocation for PUCCH format 0, 1, 2 and 3. | Band | No | N/A | N/A | +| occ-PRB-PF2-PF3-r16
Indicates whether the UE supports OCC for PRB interface mapping for PUCCH format 2 and 3. If the UE supports this feature, the UE needs to report pucch-F0-F1-PRB-Interlace-r16 . | Band | No | N/A | N/A | +| extCP-rangeCG-PUSCH-r16
Indicates whether the UE supports generating a CP extension of length longer than 1 symbol for Configured Grant PUSCH transmission. If the UE supports this feature, the UE needs to report configuredUL-GrantType1 or configuredUL-GrantType1-v1650 and/or configuredUL-GrantType2 or configuredUL-GrantType2-v1650 . | Band | No | N/A | N/A | +| configuredGrantWithReTx-r16
Indicates whether the UE supports configured grant with retransmission in configured grant resource, comprised of retransmission timer, DFI monitoring and CG-UCI in CG-PUSCH. If the UE supports this feature, the UE needs to report configuredUL-GrantType1 or configuredUL-GrantType1-v1650 and/or configuredUL-GrantType2 or configuredUL-GrantType2-v1650 . | Band | No | N/A | N/A | +| ed-Threshold-r16
Indicates whether the UE supports using ED threshold given by gNB for UL to DL COT sharing. A UE that supports this feature shall also support ul-DynamicChAccess-r16 . | Band | No | N/A | N/A | +| ul-DL-COT-Sharing-r16
Indicates whether the UE supports UL to DL COT sharing. A UE that supports this feature shall also support ul-DynamicChAccess-r16 . | Band | No | N/A | N/A | +| mux-CG-UCI-HARQ-ACK-r16
Indicates whether the UE supports multiplexing CG-UCI with HARQ ACK. If the UE supports this feature, the UE needs to report configuredGrantWithReTx-r16 . | Band | No | N/A | N/A | +| cg-resourceConfig-r16
Indicates whether the UE supports configuration of resources with cg-nrofSlots-r16 and cg-nrofPUSCH-InSlot-r16 . If the UE supports this feature, the UE needs to report configuredUL-GrantType1 or configuredUL-GrantType1-v1650 and/or configuredUL-GrantType2 or configuredUL-GrantType2-v1650 . | Band | No | N/A | N/A | +| dl-ReceptionLBT-subsetRB-r16
Indicates whether the UE supports reception in a wideband carrier when LBT is successful in a subset of the configured RB sets, which are either contiguous or non-contiguous, of the carrier. | Band | No | N/A | N/A | +| dl-ReceptionIntraCellGuardband-r16
Indicates whether the UE supports reception in the non-zero intra-cell guardband between contiguous RB sets in DL wideband carrier operation wider than 20MHz when LBT is successful only in a subset of RB sets. The UE indicates support of this capability shall also indicates support of dl-ReceptionLBT-subsetRB-r16 . | Band | No | N/A | N/A | +| ul-Semi-StaticChAccessDependentConfig-r17
Indicates whether the UE supports initiating a semi-static channel occupancy with configurations dependent on gNB semi-static channel access configurations, comprised of the following functional components:
  • - Support initiating a semi-static channel access occupancy by the UE where the corresponding period is the same as, integer multiple of, or inter-factor of the period configured for a semi-static channel occupancy that can be initiated by gNB;
  • - Sensing to initiate a semi-static CO or transmit after a gap greater than 16us from any transmission burst within a UE-initiated CO;
  • - Determination of COT initiator assumption based on rules for configured UL;
  • - Validating COT initiator assumption indicated in UL scheduling DCI.
A UE supporting this feature shall also indicate support of ul-Semi-StaticChAccess-r16 . | Band | No | N/A | N/A | +| ul-Semi-StaticChAccessIndependentConfig-r17
Indicates whether the UE supports initiating a semi-static channel access occupancy by the UE where the corresponding period is independently configured from the period configured for a semi-static channel occupancy that can be initiated | Band | No | N/A | N/A | + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|--|--| +| by gNB. A UE supporting this feature shall also indicate support of ul-Semi-StaticChAccess-r16 and ul-Semi-StaticChAccessDependentConfig-r17 . | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|--|--| + +#### 4.2.7.2b *FR2-2-AccessParamsPerBand* + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| dl-FR2-2-SCS-120kHz-r17
Indicates whether the UE supports reception of 120kHz subcarrier spacing for DL data and control channels, SSB, and reference signals in FR2-2 for non-initial access.

It is mandatory for UE supporting at least one FR2-2 frequency band. | Band | CY | N/A | N/A | +| dl-FR2-2-SCS-480kHz-r17
Indicates whether the UE supports the following:
  • - Reception of 480kHz subcarrier spacing for DL data and control channels, SSB, and reference signals in FR2-2 for non-initial access.
  • - Multiple-slot PDCCH monitoring for 480kHz with (Xs,Ys) = (4,1)
  • - Multi-PDSCH scheduling by single DCI for the operation with 480 kHz SCS and corresponding HARQ enhancements.
  • - Within the Ys = 1 slot (with Xs=4), monitoring of type 1 CSS with dedicated RRC configuration, type 3 CSS, and UE-SS with a maximum of two monitoring spans per slot with a span duration of Y symbols and a minimum gap of X symbols between the start of two spans, where (X,Y) = (4, 3) and (7, 3) are supported.
  • - Processing one unicast DCI scheduling DL and one unicast DCI scheduling UL per slot group of Xs slots per scheduled CC for FDD.
  • - Processing one unicast DCI scheduling DL and 2 unicast DCI scheduling UL per slot group of Xs slots per scheduled CC for TDD.
  • - For type 1 CSS without dedicated RRC configuration and for type 0, 0A, and 2 CSS, the configured monitoring occasion(s) can be any OFDM symbol(s) of any slot(s) of the slot group, and the actual monitoring occasions for any one of Type 1- CSS without dedicated RRC configuration, or Types 0, 0A, or 2 CSS is within a single span of three consecutive OFDM symbols within a single slot of the slot group.
UE indicating support of this feature shall also indicate support of dl-FR2-2-SCS-120kHz-r17 . | Band | No | N/A | N/A | +| dl-FR2-2-SCS-960kHz-r17
Indicates whether the UE supports the following:
  • - Reception of 960kHz subcarrier spacing for DL data and control channels, SSB, and reference signals in FR2-2 for non-initial access.
  • - Multiple-slot PDCCH monitoring for 960kHz with (Xs,Ys) = (8,1).
  • - Multi-PDSCH scheduling by single DCI for the operation with 960 kHz SCS and corresponding HARQ enhancements.
  • - Within the Ys = 1 slot (with Xs=8), monitoring of type 1 CSS with dedicated RRC configuration, type 3 CSS, and UE-SS with a maximum of two monitoring spans per slot with a span duration of Y symbols and a minimum gap of X symbols between the start of two spans, where (X,Y) = (7, 3) is supported.
  • - Processing one unicast DCI scheduling DL and one unicast DCI scheduling UL per slot group of Xs slots per scheduled CC for FDD.
  • - Processing one unicast DCI scheduling DL and 2 unicast DCI scheduling UL per slot group of Xs slots per scheduled CC for TDD.
  • - For type 1 CSS without dedicated RRC configuration and for type 0, 0A, and 2 CSS, the configured monitoring occasion(s) can be any OFDM symbol(s) of any slot(s) of the slot group, and the actual monitoring occasions for any one of Type 1- CSS without dedicated RRC configuration, or Types 0, 0A, or 2 CSS is within a single span of three consecutive OFDM symbols within a single slot of the slot group.
UE indicating support of this feature shall also indicate support of dl-FR2-2-SCS-120kHz-r17 . | Band | No | N/A | N/A | +| enhancedPDCCH-monitoringSCS-480kHz-r17
Indicates whether the UE supports multiple-slot PDCCH monitoring of type 1 CSS with dedicated RRC configuration, type 3 CSS, and UE-SS in the first 3 OFDM symbols of each slot within each of the Ys=2 slots (with Xs=4) for 480kHz with (Xs,Ys)=(4,2).

UE indicating support of this feature shall also indicate support of dl-FR2-2-SCS-480kHz-r17 . | Band | No | N/A | N/A | +| enhancedPDCCH-monitoringSCS-960kHz-r17 | Band | No | N/A | N/A | + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|-----|-----| +| Indicates whether the UE supports multiple-slot PDCCH monitoring for one or more of (Xs, Ys) = {(4,1), (4,2), (8,4)} for 960kHz:
  • - Type 1 CSS with dedicated RRC configuration, type 3 CSS, and UE-SS in the first 3 OFDM symbols of each slot within each of the Ys=2 slots (with Xs=4) or Ys=4 slots (with Xs=8).
  • - Type 1 CSS with dedicated RRC configuration, type 3 CSS, and UE-SS with a span duration of Y symbols and a minimum gap of X symbols between the start of two spans where (X,Y) = (7, 3) within the Ys=1 slot (with Xs=4).
UE indicating support of this feature shall also indicate support of dl-FR2-2-SCS-960kHz-r17 and shall include at least one of pdccch-monitoring4-1 , pdccch-monitoring4-2 , or pdccch-monitoring8-4 . | | | | | +| modulation64-QAM-PUSCH-FR2-2-r17
Indicates whether the UE supports 64-QAM modulation for FR2-2 PUSCH. | Band | No | N/A | N/A | +| ul-FR2-2-SCS-120kHz-r17
Indicates whether the UE supports PRACH with 120kHz SCS and length 139 and transmission of 120kHz subcarrier spacing for UL data and control channels and reference signals in FR2-2.

UE indicating support of this feature shall also indicate support of dl-FR2-2-SCS-120kHz-r17 . | Band | No | N/A | N/A | +| ul-FR2-2-SCS-480kHz-r17
Indicates whether the UE supports the following:
  • - PRACH with 480kHz SCS and length 139.
  • - Transmission of 4800kHz subcarrier spacing for UL data and control channels and reference signals in FR2-2.
  • - Multi-PUSCH scheduling by single DCI for the operation with 480 kHz SCS.
UE indicating support of this feature shall also indicate support of dl-FR2-2-SCS-480kHz-r17 and ul-FR2-2-SCS-120kHz-r17 . | Band | No | N/A | N/A | +| ul-FR2-2-SCS-960kHz-r17
Indicates whether the UE supports the following:
  • - PRACH with 960kHz SCS and length 139.
  • - Transmission of 960kHz subcarrier spacing for UL data and control channels and reference signals in FR2-2.
  • - Multi-PUSCH scheduling by single DCI for the operation with 960 kHz SCS.
UE indicating support of this feature shall also indicate support of dl-FR2-2-SCS-960kHz-r17 and ul-FR2-2-SCS-120kHz-r17 . | Band | No | N/A | N/A | +| initialAccessSSB-120kHz-r17
Indicates whether the UE supports 120kHz SSB for initial access in FR2-2.

UE indicating support of this feature shall also indicate support of dl-FR2-2-SCS-120kHz-r17 and ul-FR2-2-SCS-120kHz-r17 . | Band | No | N/A | N/A | +| initialAccessSSB-480kHz-r17
Indicates whether the UE supports 480kHz SSB for initial access in FR2-2.

UE indicating support of this feature shall also indicate support of initialAccessSSB-120kHz-r17 , dl-FR2-2-SCS-480kHz-r17 and ul-FR2-2-SCS-480kHz-r17 . | Band | No | N/A | N/A | +| multiPDSCH-SingleDCI-FR2-2-SCS-120kHz-r17
Indicates whether the UE supports multi-PDSCH scheduling by single DCI for the operation with 120 kHz SCS in FR2-2 and HARQ enhancements for both type 1 and type 2 HARQ codebook.

UE indicating support of this feature shall also indicate support of dl-FR2-2-SCS-120kHz-r17 . | Band | No | N/A | N/A | +| multiPUSCH-SingleDCI-FR2-2-SCS-120kHz-r17
Indicates whether the UE supports multi-PUSCH scheduling by single DCI for the operation with 120 kHz SCS in FR2-2.

UE indicating support of this feature shall also indicate support of ul-FR2-2-SCS-120kHz-r17 . | Band | No | N/A | N/A | +| multiRB-PUCCH-SCS-120kHz-r17
Indicates whether the UE supports multi-RB PUCCH format 0/1/4 for 120kHz SCS. This feature is only applicable when PSD limitation applies within FR2-2 based on the regional regulations. | Band | No | N/A | N/A | + +| | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|-----|-----| +| UE indicating support of this feature shall also indicate support of ul-FR2-2-SCS-120kHz-r17 . | | | | | +| multiRB-PUCCH-SCS-480kHz-r17
Indicates whether the UE supports multi-RB PUCCH format 0/1/4 for 480kHz SCS. This feature is only applicable when PSD limitation applies within FR2-2 based on the regional regulations.

UE indicating support of this feature shall also indicate support of ul-FR2-2-SCS-480kHz-r17 . | Band | No | N/A | N/A | +| multiRB-PUCCH-SCS-960kHz-r17
Indicates whether the UE supports multi-RB PUCCH format 0/1/4 for 960kHz SCS. This feature is only applicable when PSD limitation applies within FR2-2 based on the regional regulations.

UE indicating support of this feature shall also indicate support of ul-FR2-2-SCS-960kHz-r17 . | Band | No | N/A | N/A | +| reduced-BeamSwitchTiming-FR2-2-r17
Indicates whether the UE supports reduced beam switching time delay $d = 56$ symbols for 480 kHz SCS as specified in TS 38.214 [12], clause 5.2.1.5.1a.

If this capability is not reported and the UE supports both dl-FR2-2-SCS-480kHz-r17 and dl-FR2-2-SCS-960kHz-r17 , the default value of 112 symbols is assumed. | Band | No | N/A | N/A | +| support32-DL-HARQ-ProcessPerSCS-r17
Indicates whether the UE supports 32 HARQ processes in DL for each SCS in FR2-2 (i.e. SCS 120kHz/480kHz/960kHz).

A UE supporting 32 HARQ processes for 480/960 kHz SCS for DL shall support 32 as the maximum number of HARQ processes for 120 kHz SCS for DL in FR2-2. UE indicating support of this feature shall indicate support of dl-FR2-2-SCS-120kHz-r17 . | Band | No | N/A | N/A | +| support32-UL-HARQ-ProcessPerSCS-r17
Indicates whether the UE supports 32 HARQ processes in UL for each SCS in FR2-2 (i.e. SCS 120kHz/480kHz/960kHz).

A UE supporting 32 HARQ processes for 480/960 kHz SCS for UL shall support 32 as the maximum number of HARQ processes for 120 kHz SCS for UL in FR2-2. UE indicating support of this feature shall indicate support of dl-FR2-2-SCS-120kHz-r17 . | Band | No | N/A | N/A | +| type1-ChannelAccess-FR2-2-r17
Indicates whether the UE supports Type 1 channel access procedure in uplink for FR2-2 with shared spectrum channel access and supports LBT performed per channel, as defined in TS 37.213 [32], clause 4.4.

UE indicating support of this feature shall also indicate support of ul-FR2-2-SCS-120kHz-r17 . It is mandatory for UE supporting FR2-2 frequency band to indicate this when required by regulation. | Band | CY | N/A | N/A | +| type2-ChannelAccess-FR2-2-r17
Indicates whether the UE supports Type 2 channel access procedure in uplink for FR2-2 with shared spectrum channel access and supports LBT performed per channel, as defined in TS 37.213 [32], clause 4.4.

UE indicating support of this feature shall also indicate support of ul-FR2-2-SCS-120kHz-r17 and type1-ChannelAccess-FR2-2-r17 . It is mandatory for UE supporting FR2-2 frequency band to indicate this when required by regulation. | Band | CY | N/A | N/A | +| widebandPRACH-SCS-120kHz-r17
Indicates whether the UE supports enhanced PRACH design for operation by adopting a single long ZC sequence, with ZC sequence equal to 1151 and 571 for 120kHz SCS.

This feature is only applicable when PSD limitation applies within FR2-2 based on the regional regulations.

UE indicating support of this feature shall also indicate support of ul-FR2-2-SCS-120kHz-r17 . | Band | No | N/A | N/A | +| widebandPRACH-SCS-480kHz-r17
Indicates whether the UE supports enhanced PRACH design for operation with ZC sequence equal to 571 for 480kHz SCS.

This feature is only applicable when PSD limitation applies within FR2-2 based on the regional regulations. | Band | No | N/A | N/A | + +| | | | | | +|-------------------------------------------------------------------------------------------------------|--|--|--|--| +| UE indicating support of this feature shall also indicate support of ul-FR2-2-SCS-480kHz-r17 . | | | | | +|-------------------------------------------------------------------------------------------------------|--|--|--|--| + +#### 4.2.7.3 CA-ParametersEUTRA + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----|--------------|--------------| +| additionalRx-Tx-PerformanceReq
additionalRx-Tx-PerformanceReq defined in 4.3.5.22, TS 36.306 [15]. | BC | No | N/A | N/A | +| dl-1024QAM-TotalWeightedLayers
Indicates total number of weighted layers for the LTE part of the concerned (NG)EN-DC/NE-DC band combination the UE can process for 1024QAM, as described in TS 36.306 [15] equation 4.3.5.31-1. Actual value = (10 + indicated value x 2), i.e. value 0 indicates 10 layers, value 1 indicates 12 layers and so on. For an (NG)EN-DC/NE-DC band combination for which this field is not included, dl-1024QAM-TotalWeightedLayers-r15 as described in TS 36.331 [17] applies, if included. | BC | No | N/A | N/A | +| multipleTimingAdvance
multipleTimingAdvance defined in 4.3.5.3, TS 36.306 [15]. | BC | No | N/A | N/A | +| simultaneousRx-Tx
simultaneousRx-Tx defined in 4.3.5.4, TS 36.306 [15]. | BC | No | N/A | N/A | +| supportedBandwidthCombinationSetEUTRA
Indicates the set of supported bandwidth combinations for the LTE part for inter-band (NG)EN-DC without intra-band (NG)EN-DC component, inter-band NE-DC without intra-band NE-DC component and intra-band (NG)EN-DC/NE-DC with additional inter-band LTE CA component. The field is encoded as a bit map, where bit N is set to "1" if UE support Bandwidth Combination Set N for this band combination. The leading / leftmost bit (bit 0) corresponds to the Bandwidth Combination Set 0, the next bit corresponds to the Bandwidth Combination Set 1 and so on. The UE shall neither include the field for a (NG)EN-DC/NE-DC combination which has only one LTE carrier, nor for a (NG)EN-DC/NE-DC combination which has more than one LTE carrier for which the UE only supports Bandwidth Combination Set 0 for the LTE part. If the inter-band (NG)EN-DC/NE-DC has more than one LTE carrier, the UE shall support at least one bandwidth combination for the supported LTE part. | BC | CY | N/A | N/A | +| supportedNAICS-2CRS-AP
supportedNAICS-2CRS-AP defined in 4.3.5.8, TS 36.306 [15]. | BC | No | N/A | N/A | +| fd-MIMO-TotalWeightedLayers
Indicates total number of weighted layers for the LTE part of the concerned (NG)EN-DC/NE-DC band combination the UE can process for FD-MIMO, as described in TS 36.306 [15] equation 4.3.28.13-1 and TS 36.331 [17] clause 6.3.6, NOTE 8 in UE-EUTRA-Capability field descriptions. For an (NG)EN-DC/NE-DC band combination for which this field is not included, totalWeightedLayers-r13 as described in TS 36.331 [17] applies, if included. | BC | No | N/A | N/A | +| ue-CA-PowerClass-N
ue-CA-PowerClass-N defined in 4.3.5.1.3, TS 36.306 [15]. | BC | No | N/A | N/A | + +#### 4.2.7.4 *CA-ParametersNR* + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|-----|--------------|--------------| +| ack-NACK-FeedbackForMulticast-r17
Indicates whether the UE supports ACK/NACK based HARQ-ACK feedback and RRC-based enabling/disabling ACK/NACK-based feedback for dynamic scheduling for multicast, comprised of the following functional components:
  • - Supports ACK/NACK based HARQ-ACK feedback, and support of enabling/disabling ACK/NACK based HARQ-ACK feedback configured by RRC signalling;
  • - Supports PTM retransmission for multicast;
  • - Supports Type-1 and Type-2 HARQ-ACK CB for multicast feedback only;
  • - Supports shared PUCCH resource configurations with unicast;
  • - Supports Type-2 HARQ-ACK codebook for multicast on PUSCH/PUCCH with max number of G-RNTIs indicated in maxNumberG-RNTI-HARQ-ACK-Codebook-r17, which is not larger than max number of G-RNTIs indicated in maxNumberG-RNTI-r17.
A UE supporting this feature shall also indicate support of dynamicMulticastPCell-r17 . | BC | No | N/A | N/A | +| ack-NACK-FeedbackForSPS-Multicast-r17
Indicates whether the UE supports ACK/NACK based HARQ-ACK feedback and RRC-based enabling/disabling ACK/NACK-based feedback for SPS group-common PDSCH for multicast, comprised of the following functional components:
  • - Support of ACK/NACK based HARQ-ACK feedback, enabling/disabling ACK/NACK based HARQ-ACK feedback configured by RRC signalling for SPS group-common PDSCH without PDCCH scheduling and first PDSCH after SPS activation;
  • - Support of PTM retransmission for SPS multicast associated with G-CS-RNTI;
  • - Support of Type-1 and Type-2 HARQ-ACK CB for SPS multicast feedback only;
  • - Support of shared SPS-PUCCH-AN-List configuration from unicast SPS.
A UE supporting this feature shall also indicate support of sps-Multicast-r17 . | BC | No | N/A | N/A | +| beamManagementType-r16, beamManagementType-CBM-r17
Indicates the supported beam management type for inter-band CA within FR2. Beam management type can be independent beam management (IBM) or common beam management (CBM). The UE can support independent beam management (IBM) only or common beam management (CBM) only or both.

NOTE: beamManagementType-CBM-r17 is only applicable to the band combinations with 2 bands. | BC | Yes | TDD only | FR2 only | +| blindDetectFactor-r16
Defines the value of factor R for blind detection as specified in Clause 10.1 [11]. The UE that indicates support of this feature shall support multiDCI-MultiTRP-r16 . | BC | No | N/A | N/A | +| codebookComboParametersAdditionPerBC-r16
Indicates the list of supported CSI-RS resources across all bands in a band combination by referring to codebookVariantsList for the mixed codebook types. For mixed codebook types, UE reports support active CSI-RS resources and ports for up to 4 mixed codebook combinations in any slot. The following parameters are included in codebookVariantsList for each code book type:
  • - maxNumberTxPortsPerResource indicates the maximum number of Tx ports in a resource across all bands within a band combination;
  • - maxNumberResourcesPerBand indicates the maximum number of resources across all CCs within a band combination, simultaneously;
  • - totalNumberTxPortsPerBand indicates the total number of Tx ports across all CCs within a band combination, simultaneously.
For each band in a band combination, supported values for these three parameters are determined in conjunction with codebookComboParametersAddition-r16 reported in MIMO-ParametersPerBand . | BC | No | N/A | N/A | + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|-----| +|

codebookParametersAdditionPerBC-r16
Indicates the list of supported CSI-RS resources across all bands in a band combination by referring to codebookVariantsList for the additional codebook types. The following parameters are included in codebookVariantsList for each code book type:

  • - maxNumberTxPortsPerResource indicates the maximum number of Tx ports in a resource across all bands within a band combination;
  • - maxNumberResourcesPerBand indicates the maximum number of resources across all CCs within a band combination, simultaneously;
  • - totalNumberTxPortsPerBand indicates the total number of Tx ports across all CCs within a band combination, simultaneously.

For each band in a band combination, supported values for these three parameters are determined in conjunction with codebookParametersAddition-r16 reported in MIMO-ParametersPerBand.

| BC | No | N/A | N/A | +|

codebookParametersetType2DopplerCSI-PerBC-r18
Indicates the UE support of additional codebooks and the corresponding parameters supported by the UE of Enhanced Type II Codebook (eType-II) based on doppler CSI as specified in TS 38.214 [12].

The UE indicating this feature shall include eType2Doppler-r18 to indicate basic features of eType-II. This capability signalling comprises the following parameters:

  • - supportedCSI-RS-ResourceList-r18 indicates the list of supported CSI-RS resources in a band by referring to codebookVariantsList. The following parameters are included in codebookVariantsList:
    • - maxNumberTxPortsPerResource indicates the maximum number of Tx ports in a resource of a band
    • - maxNumberResourcesPerBand indicates the maximum number of resources across all CCs in a band, simultaneously
    • - totalNumberTxPortsPerBand indicates the total number of Tx ports across all CCs in a band, simultaneously
  • - valueY-P-SP-CSI-RS-r18 indicates value of Y for CPU occupation (OCPU = Y.N4), when P/SP-CSI-RS is configured for CMR
  • - valueY-A-CSI-RS-r18 indicates value of Y for CPU occupation (OCPU = Y.K), when A-CSI-RS is configured for CMR
  • - scalingfactor-r18 indicates scaling factor for active resource counting Kp

The UE indicating eType2Doppler-r18 shall support X=1 CQI based on the first/earliest slot of the CSI reporting window and the first/earliest predicted PMI (TDCQI='1-1'), support eType-II regular codebook refinement for predicted PMI with PMI subband R=1 3, support parameter combinations with L=2,4, support for rank = 1,2, and support for the size of DD-basis, N4=1. A UE indicating this feature shall also indicate the support of csi-ReportFramework.

The UE indicating support of eType2Doppler-r18 shall also indicate support of codebookParametersetType2PerBC-r17.

NOTE 1: When N4=1, OCPU =4.
NOTE 2: OCPU ≥ 4 when P/SP-CSI-RS is configured for CMR.
NOTE 3: when K=12, OCPU =8
NOTE 4: A UE that supports CSI enhancement for Rel. 16-based type-2 doppler must support this FG.

The UE optionally includes eType2DopplerN4-r18 to indicate whether the UE supports doppler measurement with N4>1 for eType-II. This capability signalling comprises the following parameters:

  • - supportedCSI-RS-ReportSettingList1-r18 indicates the list of supported combinations across all CCs simultaneously by referring to supportedCSI-RS-ReportSettingList The following parameters are included in supportedCSI-RS-ReportSettingList-r18
    • - maxN4-r18 indicates the max number of N4
    • - maxNumberTxPortsPerResource-r18 indicates the maximum number of Tx ports in a resource of a band
    • - maxNumberResourcesPerBand-r18 indicates the maximum number of resources across all CCs in a band, simultaneously
    • - totalNumberTxPortsPerBand-r18 indicates the total number of Tx ports across all CCs in a band, simultaneously
  • - supportedCSI-RS-ReportSettingList2-r18 indicates the list of supported
| BC | No | N/A | N/A | + +| | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|--|--| +|

combinations for one CSI report setting by referring to supportedCSI-RS-ReportSettingList-r18.

The UE indicating support of eType2DopplerN4-r18 shall also indicate support of eType2Doppler-r18, support for the size of DD-basis, N4 > 1, and Value of d=m for the DD unit size when A-CSI-RS is configured for CMR.

The UE optionally includes ddUnitSize-A-CSI-RS-CMR-r18 to indicate the support of value of d=1 for the DD unit size when A-CSI-RS is configured for CMR. A UE supporting this feature shall also indicate support of eType2DopplerN4-r18.

The UE optionally includes eType2DopplerR2-r18 to indicate whether the UE supports R=2 for eType-II. This capability signalling comprises the following parameters:

  • - indicates the list of supported CSI-RS resources in a band by referring to codebookVariantsList.

UE indicating support of eType2DopplerR2-r18 shall also indicate support of eType2Doppler-r18.

The UE optionally includes eType2DopplerX1-r18 to indicate whether the UE support X=1 based on first and last slot of WCSI, for eType-II doppler codebook.

The UE optionally includes eType2DopplerX2-r18 to indicate whether the UE support X=2 CQI based on 2 slots for eType-II doppler codebook.

The UE optionally includes eType2DopplerL-N4D1-r18 to indicate whether the UE support support of l = (n - n_{CSI,ref}) for CSI reference slot for eType-II doppler codebook. UE indicating support of eType2DopplerL-N4D1-r18 shall indicate support of eType2Doppler-r18.

For codebookVariantsList-r16 related to the eType-II:

  • - The minimum of maxNumberTxPortsPerResource is 'p4';
  • - The minimum of maxNumberResourcesPerBand is 2, except for eType2DopplerR2-r18.
  • - The minimum value of totalNumberTxPortsPerBand is 4.
| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|--|--| + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|-----| +|

codebookParametersfetype2DopplerCSI-r18
Indicates the UE support of additional codebooks and the corresponding parameters supported by the UE of Further Enhanced Type II Codebook (FeType-II) based on doppler CSI as specified in TS 38.214 [12].

The UE indicating this feature shall include feType2Doppler-r18 to indicate basic features of FeType-II. This capability signalling comprises the following parameters:

  • - supportedCSI-RS-ResourceList-r18 indicates the list of supported CSI-RS resources in a band by referring to codebookVariantsList. The following parameters are included in codebookVariantsList:
    • - maxNumberTxPortsPerResource indicates the maximum number of Tx ports in a resource of a band combination
    • - maxNumberResourcesPerBand indicates the maximum number of resources across all CCs within a band combination, simultaneously
    • - totalNumberTxPortsPerBand indicates the total number of Tx ports across all CCs within a band combination, simultaneously
  • - valueY-A-CSI-RS-r18 indicates value of Y for CPU occupation (OCPU = Y.K), when A-CSI-RS is configured for CMR
  • - scalingfactor-r18 indicates scaling factor for active resource counting Kp

The UE indicating feType2Doppler-r18 shall support X=1 CQI based on the first/earliest slot of the CSI reporting window and the first/earliest predicted PMI, support FeType-II regular codebook refinement for predicted PMI with PMI subband R=1, support parameter combinations with M=1, support for rank = 1,2, and support N4=1. A UE indicating this feature shall also indicate the support of csi-ReportFramework.

The UE indicating support of feType2Doppler-r18 shall also indicate support of eType2Doppler-r18 and codebookParametersfetype2PerBC-r17.

NOTE 1: OCPU = 4 when P/SP-CSI-RS is configured for CMR.
NOTE 2: when K=12, OCPU =8.
NOTE 3: A UE that supports CSI enhancement for Rel. 17-based type-2 doppler must support this FG.

The UE optionally includes feType2DopplerM2R1-r18 to indicate whether the UE supports M=2 and R=1 for FeType-II doppler codebook. This capability signalling comprises the following parameters:

  • - indicates the list of supported CSI-RS resources in a band by referring to codebookVariantsList.

The UE indicating support of feType2DopplerM2R1-r18 shall also indicate support of feType2Doppler-r18.

The UE optionally includes feType2DopplerR2-r18 to indicate whether the UE supports R=2 for FeType-II. This capability signalling comprises the following parameters:

  • - indicates the list of supported CSI-RS resources in a band by referring to codebookVariantsList.

UE indicating support of feType2DopplerR2-r18 shall also indicate support of feType2Doppler-r18.

The UE optionally includes feType2DopplerL-N4D1-r18 to indicate whether the UE support support of l = (n - n_{CSI,ref}) for CSI reference slot for FeType-II doppler codebook. UE indicating support of feType2DopplerL-N4D1-r18 shall indicate support of feType2Doppler-r18.

For codebookVariantsList-r16 related to the feType-II:

  • - The minimum of maxNumberTxPortsPerResource is 'p4';
  • - The minimum of maxNumberResourcesPerBand is 2, except for eType2DopplerR2-r18.
  • - The minimum value of totalNumberTxPortsPerBand is 4.
| BC | No | N/A | N/A | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|-----| + +| | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|-----| +|

codebookParametersfetype2perBC-r17

Indicates the list of supported CSI-RS resources across all bands in a band combination by referring to codebookVariantsList for the additional codebook types. The following parameters are included in codebookVariantsList for each code book type:

  • - maxNumberTxPortsPerResource indicates the maximum number of Tx ports in a resource across all bands within a band combination;
  • - maxNumberResourcesPerBand indicates the maximum number of resources across all CCs within a band combination, simultaneously;
  • - totalNumberTxPortsPerBand indicates the total number of Tx ports across all CCs within a band combination, simultaneously.

For each band in a band combination, supported values for these three parameters are determined in conjunction with CodebookParametersfetyp2-r17 reported in MIMO-ParametersPerBand.

For codebookVariantsList related to the FeType-II:

  • - The minimum of maxNumberTxPortsPerResource is 'p4';
  • - The minimum value of totalNumberTxPortsPerBand is 4.
| BC | No | N/A | N/A | +|

codebookComboParameterMixedTypePerBC-r17

Indicates the support of active CSI-RS resources and ports for mixed codebook types in any slot. The UE reports supported active CSI-RS resources and ports for up to 4 mixed codebook combinations in any slot. The following are the possible mixed codebook combinations {Codebook1, Codebook2, Codebook3}:

  • - type1SP-fetype2PS-null-r17 indicates {Type 1 Single Panel, FeType II PS M=1, NULL}
  • - type1SP-fetype2PS-M2R1-null-r17 indicates {Type 1 Single Panel, FeType II PS M=2 R=1, NULL}
  • - type1SP-fetype2PS-M2R2-null-r17 indicates {Type 1 Single Panel, FeType II PS M=2 R=2, NULL}
  • - type1SP-Type2-fetype2-PS-M1-r17 indicates {Type 1 Single Panel, Type II, FeType II PS M=1}
  • - type1SP-Type2-fetype2-PS-M2R1-r17 indicates {Type 1 Single Panel, Type II, FeType II PS M=2 R=1}
  • - type1SP-eType2R1-fetype2-PS-M1-r17 indicates {Type 1 Single Panel, eType II R=1, FeType II PS M=1}
  • - type1SP-eType2R1-fetype2-PS-M2R1-r17 indicates {Type 1 Single Panel, eType II R=1, FeType II PS M=2 R=1}
  • - type1MP-fetype2PS-null-r17 indicates {Type 1 Multi Panel, FeType II PS M=1, NULL}
  • - type1MP-fetype2PS-M2R1-null-r17 indicates {Type 1 Multi Panel, FeType II PS M=2 R=1, NULL}
  • - type1MP-fetype2PS-M2R2-null-r17 indicates {Type 1 Multi Panel, FeType II PS M=2 R=2, NULL}
  • - type1MP-Type2-fetype2-PS-M1-r17 indicates {Type 1 Multi Panel, Type II, FeType II PS M=1}
  • - type1MP-Type2-fetype2-PS-M2R1-r17 indicates {Type 1 Multi Panel, Type II, FeType II PS M=2 R=1}
  • - type1MP-eType2R1-fetype2-PS-M1-r17 indicates {Type 1 Multi Panel, eType II R=1, FeType II PS M=1}
  • - type1MP-eType2R1-fetype2-PS-M2R1-r17 indicates {Type 1 Multi Panel, eType II R=1, FeType II PS M=2 R=1}

For each mixed codebook supported by the UE, supportedCSI-RS-ResourceListAdd-r16 indicates the list of supported CSI-RS resources in a band by referring to codebookVariantsList. The following parameters are included in codebookVariantsList:

  • - maxNumberTxPortsPerResource indicates the maximum number of Tx ports in a resource of a band combination with the minimum value of 'p4'.
  • - maxNumberResourcesPerBand indicates the maximum number of resources across all CCs in a band combination with the minimum value of 4.
  • - totalNumberTxPortsPerBand indicates the total number of Tx ports across all CCs in a band combination.

The UE supporting this feature shall indicate the support of fetype2basic-r17, etype2R1-r16, codebookParameters (type1-singlePanel, type1-multiPanel, type2), fetype2R1-r17, fetype2R2-r17.

| BC | No | N/A | N/A | + +|

codebookComboParameterMultiTRP-PerBC-r17

Indicates the support of active CSI-RS resources and ports in the presence of multi-TRP CSI.
Indicates the support of active CSI-RS resources and ports for mixed codebook types in any slot. The UE reports supported active CSI-RS resources and ports for up to 4 mixed codebook combinations. The following are the possible mixed codebook combinations {Codebook1, Codebook2, Codebook3}:

  • - nCJT-null-null indicates {NCJT, NULL, NULL}
  • - nCJT1SP-null-null indicates {NCJT+Type 1 SP for sTRP, NULL, NULL}
  • - nCJT-Type2-null-r16 indicates {NCJT, Type 2, Null}
  • - nCJT-Type2PS-null-r16 indicates {NCJT, Type 2 with port selection, Null}
  • - nCJT-eType2R1-null-r16 indicates {NCJT, eType 2 with R=1, Null}
  • - nCJT-eType2R2-null-r16 indicates {NCJT, eType 2 with R=2, Null}
  • - nCJT-eType2R1PS-null-r16 indicates {NCJT, eType 2 with R=1 and port selection, Null}
  • - nCJT-eType2R2PS-null-r16 indicates {NCJT, eType 2 with R=2 and port selection, Null}
  • - nCJT-Type2-Type2PS-r16 indicates {NCJT, Type 2, Type 2 with port selection}
  • - nCJT1SP-Type2-null-r16 indicates {NCJT+Type 1 SP for sTRP, Type 2, Null}
  • - nCJT1SP-Type2PS-null-r16 indicates {NCJT+Type 1 SP for sTRP, Type 2 with port selection, Null}
  • - nCJT1SP-eType2R1-null-r16 indicates {NCJT+Type 1 SP for sTRP, eType 2 with R=1, Null}
  • - nCJT1SP-eType2R2-null-r16 indicates {NCJT+Type 1 SP for sTRP, eType 2 with R=2, Null}
  • - nCJT1SP-eType2R1PS-null-r16 indicates {NCJT+Type 1 SP for sTRP, eType 2 with R=1 and port selection, Null}
  • - nCJT1SP-eType2R2PS-null-r16 indicates {NCJT+Type 1 SP for sTRP, eType 2 with R=2 and port selection, Null}
  • - nCJT1SP-Type2-Type2PS-r16 indicates {NCJT+Type 1 SP for sTRP, Type 2, Type 2 with port selection}
  • - nCJT-feType2PS-null-r17 indicates {NCJT, FeType II PS M=1, NULL}
  • - nCJT-feType2PS-M2R1-null-r17 indicates {NCJT, FeType II PS M=2 R=1, NULL}
  • - nCJT-feType2PS-M2R2-null-r17 indicates {NCJT, FeType II PS M=2 R=2, NULL}
  • - nCJT-Type2-feType2-PS-M1-r17 indicates {NCJT, Type II, FeType II PS M=1}
  • - nCJT-Type2-feType2-PS-M2R1-r17 indicates {NCJT, Type II, FeType II PS M=2 R=1}
  • - nCJT-eType2R1-feType2-PS-M1-r17 indicates {NCJT, eType II R=1, FeType II PS M=1}
  • - nCJT-eType2R1-feType2-PS-M2R1-r17 indicates {NCJT, eType II R=1, FeType II PS M=2 R=1}
  • - nCJT1SP-feType2PS-null-r17 indicates {NCJT+Type 1 SP for sTRP, FeType II PS M=1, NULL}
  • - nCJT1SP-feType2PS-M2R1-null-r17 indicates {NCJT+Type 1 SP for sTRP, FeType II PS M=2 R=1, NULL}
  • - nCJT1SP-feType2PS-M2R2-null-r17 indicates {NCJT+Type 1 SP for sTRP, FeType II PS M=2 R=2, NULL}
  • - nCJT1SP-Type2-feType2-PS-M1-r17 indicates {NCJT+Type 1 SP for sTRP, Type II, FeType II PS M=1}
  • - nCJT1SP-Type2-feType2-PS-M2R1-r17 indicates {NCJT+Type 1 SP for sTRP, Type II, FeType II PS M=2 R=1}
  • - nCJT1SP-eType2R1-feType2-PS-M1-r17 indicates {NCJT+Type 1 SP for sTRP, eType II R=1, FeType II PS M=1}
  • - nCJT1SP-eType2R1-feType2-PS-M2R1-r17 indicates {NCJT+Type 1 SP for sTRP, eType II R=1, FeType II PS M=2 R=1}

For each mixed codebook supported by the UE, supportedCSI-RS-ResourceListAdd-r16 indicates the list of supported CSI-RS resources in a band by referring to codebookVariantsList. The following parameters are included in codebookVariantsList:

  • - maxNumberTxPortsPerResource indicates the maximum number of Tx ports in a resource of a band combination.
| Band | No | N/A | N/A | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|-----|-----| +| | | | | | + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|--|--| +|
  • - maxNumberResourcesPerBand indicates the maximum number of resources across all CCs in a band combination.
  • - totalNumberTxPortsPerBand indicates the total number of Tx ports across all CCs in a band combination.

NOTE 1: A CMR pair configured for NCJT will be counted as two activated resources, a CMR configured for sTRP will be counted as one activated resource for a triplet.

NOTE2: his capability is relevant only when UE is configured with NCJT CSI in at least one CSI report setting in at least one CC in the band and/or band combination.

The UE indicating support of this feature shall also indicate the support of mTRP-CSI-EnhancementPerBand-r17.

| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|--|--| + +| | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|-----| +|

crossCarrierA-CSI-trigDiffSCS-r16
Indicates the UE support of handling cross-carrier aperiodic CSI report with aperiodic CSI-RS where triggering PDCCH and triggered CSI-RS resource are on different cells with different SCS. Value higherA-CSI-SCS indicates the UE support of PDCCH cell of lower SCS and CSI RS cell of higher SCS and value lowerA-CSI-SCS indicates the UE support of PDCCH cell of higher SCS and CSI RS cell of lower SCS, and value both indicates the support of both variations. A UE supporting this feature shall also indicate support of CSI-RS and CSI-IM reception for CSI feedback using csi-RS-IM-ReceptionForFeedback

| BC | No | N/A | N/A | +|

crossCarrierSchedulingDefaultQCL-r16
Indicates whether the UE can be configured with enabledDefaultBeamForCCS for default QCL assumption for cross-carrier scheduling for same/different numerologies. A UE supporting this feature shall either indicate support of crossCarrierScheduling-SameSCS or crossCarrierSchedulingDL-DiffSCS-r16.

Value diff-only indicates UE supports this feature only for different SCS combination(s).
Value both indicates UE supports this feature for same SCS and for different SCS combination(s).

| BC | No | N/A | N/A | +|

crossCarrierSchedulingDL-DiffSCS-r16
Indicates the UE supports cross carrier scheduling for the different numerologies with carrier indicator field (CIF) in DL carrier aggregation where numerologies for the scheduling CC and scheduled CC are different.

Value low-to-high indicates UE supports scheduling CC of lower SCS to scheduled CC of higher SCS;
Value high-to-low indicates UE supports scheduling CC of higher SCS to scheduled CC of lower SCS;
Value both indicates UE supports both scheduling CC of lower SCS to scheduled CC of higher SCS and scheduling CC of higher SCS to scheduled CC of lower SCS.

NOTE 1: Following components are applicable to cross carrier scheduling from lower SCS to higher SCS when the UE reports this feature:

  • - Processing one unicast DCI scheduling DL per scheduling CC slot per scheduled CC for FDD scheduling CC
  • - Processing one unicast DCI scheduling DL per scheduling CC slot per scheduled CC for TDD scheduling CC

NOTE 2: Following components are applicable to cross carrier scheduling from higher SCS to lower SCS when the UE reports this feature:

  • - Processing one unicast DCI scheduling DL per N consecutive scheduling CC slot per scheduled CC for FDD scheduling CC
  • - Processing one unicast DCI scheduling DL per N consecutive scheduling CC slot per scheduled CC for TDD scheduling CC
  • - N is based on pair of (scheduling CC SCS, scheduled CC SCS): N=2 for (30,15), (60,30), (120,60) and N=4 for (60,5), (120,30), N = 8 for (120,15)
| BC | No | N/A | N/A | + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|----------| +|

crossCarrierSchedulingSCell-SpCellTypeB-r17

Indicates whether the UE supports cross-carrier scheduling from SCell configured with cross-carrier scheduling to PCell/PSCell (sSCell) to PCell/PSCell (Type B). This capability signalling comprises the following parameters:

  • - supportedSCS-Combinations-r17 indicates which {PCell/PSCell SCS in kHz, sSCell SCS in kHz} combinations are supported. For {PCell/PSCell SCS in kHz, sSCell SCS in kHz} combinations = {(30,30), (30, 60), (60,60)}, the capability also indicates the band pair(s) that are supported. The band-pair is encoded as a bitmap with size L * (L - 1) / 2, and bit N (leftmost bit is indexed as bit 0) is set to "1" if the UE supports cross-carrier scheduling from SCell to PCell/PSCell for the band pair (x, y), where L is the number of band entries in the band combination, x and y are the indices of the band entry in the band combination (the first band entry is indexed as 0), x < y, and N = x*(2*L - x - 1)/2 + y - x - 1.
  • - sSCell USS set(s) (for CCS from sSCell to PCell/PSCell) and search space sets on PCell/PSCell can be configured so that the UE monitors them in overlapping slot of PCell/PSCell and sSCell.
  • - Configuration of scaling factor \alpha for BD and CCE limit handling and PDCCH overbooking handling on P(S)Cell
  • - The number of unicast DCI limits for PCell/PSCell scheduling
    • - Processing K1 unicast DCI scheduling DL on PCell/PSCell per PCell/PSCell slot and its aligned N consecutive sSCell slot(s)
    • - Processing K2 unicast DCI scheduling UL on PCell/PSCell per PCell/PSCell slot and its aligned N consecutive sSCell slot(s)
    • - N is based on pair of (PCell/PSCell SCS, sSCell SCS): N=1 for (15,15), (30,30), (60,60) and N=2 for (15,30), (30,60) and N=4 for (15, 60)
    • - (K1, K2) = \{(1,1) \text{ for FDD P(S)Cell}; (K1, K2) = (1,2) \text{ for TDD P(S)Cell}\}
  • - Same numerology between sSCell and P(S)Cell or sSCell SCS is larger than P(S)Cell SCS.
  • - USS set(s) for DCI format 0_1_1_1 configured on sSCell for CCS from sSCell to PCell/PSCell and USS set(s) for DCI format 0_2_1_2 configured on sSCell for CCS from sSCell to PCell/PSCell if UE supports dci-Format1-2And0-2-r16
  • - pdcch-MonitoringOccasion-r17 indicates the PDCCH monitoring occasion(s) on sSCell for cross-carrier scheduling to PCell/PSCell. There are 2 values {val1, val2} where val1 = within the first 3 OFDM symbols of sSCell slot overlapping with the first 3 OFDM symbols of PCell/PSCell slot and val2 = within the first 3 OFDM symbols of any sSCell slot overlapping with a PCell/PSCell slot.
  • - Frame boundary alignment between PCell/PSCell and sSCell.

NOTE 1: A UE supporting this FG does not imply that the UE can be configured with sSCell in shared channel access spectrum.

NOTE 2: The CCS from sSCell to PCell is applicable to FR1 only but there can be other SCells in FR2 configured for the UE.

NOTE 3: Parameters in CSI-MeasConfig of P(S)Cell and sSCell are configured such that combination of P(S)Cell and sSCell configurations does not result in exceeding any of the UE's capabilities for A-/SP-CSI reporting on PUSCH on P(S)Cell.

| BC | No | N/A | FR1 only | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|----------| + +| | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|----------| +|

crossCarrierSchedulingSCell-SpCellTypeA-r17

Indicates whether the UE supports cross-carrier scheduling from SCell configured with cross-carrier scheduling to PCell/PSCell (sSCell) to PCell/PSCell with search space restrictions (Type A). This capability signalling comprises the following parameters:

  • - supportedSCS-Combinations-r17 indicates which {PCell/PSCell SCS in kHz, sSCell SCS in kHz} combinations are supported. For {PCell/PSCell SCS in kHz, sSCell SCS in kHz} combinations = {(30,30), (30, 60), (60,60)}, the capability also indicates the band pair(s) that are supported. The band-pair is encoded as a bitmap with size L * (L - 1) / 2, and bit N (leftmost bit is indexed as bit 0) is set to "1" if the UE supports cross-carrier scheduling from SCell to PCell/PSCell for band pair (x, y), where L is the number of band entries in the band combination, x and y are the indices of the band entry in the band combination (the first band entry is indexed as 0), x < y, and N = x*(2*L - x - 1)/2 + y - x - 1.
  • - Search space restrictions: sSCell USS set(s) (for CCS from sSCell to PCell/PSCell) and following search space sets on PCell/PSCell can only be configured such that UE does not monitor them in overlapping slot of PCell/PSCell and sSCell:
    • - USS sets for DCI formats 0_1_1_1_0_2_1_2.
    • - USS sets for DCI formats 0_0_1_0.
    • - Type3-CSS set(s) for DCI formats 1_0/0_0 with C-RNTI/CS-RNTI/MCS-C-RNTI.
  • - Configuration of scaling factor \alpha for BD and CCE limit handling and PDCCH overbooking handling on P(S)Cell.
  • - The number of unicast DCI limits for PCell/PSCell scheduling:
    • - Processing K1 unicast DCI scheduling DL on PCell/PSCell per PCell/PSCell slot and its aligned N consecutive sSCell slot(s).
    • - Processing K2 unicast DCI scheduling UL on PCell/PSCell per PCell/PSCell slot and its aligned N consecutive sSCell slot(s).
    • - N is based on pair of (PCell/PSCell SCS, sSCell SCS): N=1 for (15,15), (30,30), (60,60) and N=2 for (15,30), (30,60) and N=4 for (15, 60).
    • - (K1, K2) = {(1,1) for FDD P(S)Cell; (K1, K2) = (1,2) for TDD P(S)Cell}.
  • - Same numerology between sSCell and P(S)Cell or sSCell SCS is larger than P(S)Cell SCS.
  • - USS set(s) for DCI format 0_1_1_1 configured on sSCell for CCS from sSCell to PCell/PSCell and USS set(s) for DCI format 0_2_1_2 configured on sSCell for CCS from sSCell to PCell/PSCell if UE supports dci-Format1-2And0-2-r16.
  • - sSCell USS set(s) (for CCS from sSCell to PCell/PSCell) and Type0/0A/1/2 CSS sets on PCell/PSCell can be configured so that the UE monitors them in overlapping slot of PCell/PSCell and sSCell
    • - no simultaneous monitoring between 'USS sets (for P(S)Cell scheduling) on sSCell' and 'Type 0/0A/1/2 CSS sets on P(S)Cell for DCI formats with CRC scrambled by C-RNTI/MCS-C-RNTI/CS-RNTI'
    • - simultaneous monitoring of 'USS sets (for P(S)Cell scheduling) on sSCell' and 'Type 0/0A/1/2 CSS sets on P(S)Cell for DCI formats with CRC not scrambled by C-RNTI/MCS-C-RNTI/CS-RNTI'.
  • - pdcch-MonitoringOccasion-r17 indicates the PDCCH monitoring occasion(s) on sSCell for cross-carrier scheduling to PCell/PSCell. There are 2 values {val1, val2} where val1 = within the first 3 OFDM symbols of sSCell slot overlapping with the first 3 OFDM symbols of PCell/PSCell slot and val2 = within the first 3 OFDM symbols of any sSCell slot overlapping with a PCell/PSCell slot.
  • - Frame boundary alignment between PCell/PSCell and sSCell.

NOTE 1: A UE supporting this FG does not imply that the UE can be configured with sSCell in shared channel access spectrum.

NOTE 2: The CCS from sSCell to PCell is applicable to FR1 only but there can be other SCells in FR2 configured for the UE.

NOTE 3: Parameters in CSI-MeasConfig of P(S)Cell and sSCell are configured such that combination of P(S)Cell and sSCell configurations does not result in exceeding any of the UE's capabilities for A-/SP-CSI reporting on PUSCH on P(S)Cell.

| BC | No | N/A | FR1 only | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|----------| + +| | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|-----| +|

crossCarrierSchedulingUL-DiffSCS-r16

Indicates the UE supports cross carrier scheduling for the different numerologies with carrier indicator field (CIF) in UL carrier aggregation where numerologies for the scheduling CC and scheduled CC are different.

Value low-to-high indicates UE supports scheduling CC of lower SCS to scheduled CC of higher SCS;

Value high-to-low indicates UE supports scheduling CC of higher SCS to scheduled CC of lower SCS;

Value both indicates UE supports both scheduling CC of lower SCS to scheduled CC of higher SCS and scheduling CC of higher SCS to scheduled CC of lower SCS.

NOTE 1: Following components are applicable to cross carrier scheduling from lower SCS to higher SCS when the UE reports this feature:

  • - Processing one unicast DCI scheduling UL per scheduling CC slot per scheduled CC for FDD scheduling CC
  • - Processing 2 unicast DCI scheduling UL per scheduling CC slot per scheduled CC for TDD scheduling CC

NOTE 2: Following components are applicable to cross carrier scheduling from higher SCS to lower SCS when the UE reports this feature:

  • - Processing one unicast DCI scheduling UL per N consecutive scheduling CC slot per scheduled CC for FDD scheduling CC
  • - Processing 2 unicast DCI scheduling UL per N consecutive scheduling CC slot per scheduled CC for TDD scheduling CC
  • - N is based on pair of (scheduling CC SCS, scheduled CC SCS): N=2 for (30,15), (60,30), (120,60) and N=4 for (60,15), (120,30), N = 8 for (120,15)
| BC | No | N/A | N/A | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|-----| + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|-----|-----|-----| +|

csi-ReportingCrossPUCCH-Grp-r16
Indicates the support of CSI reporting cross PUCCH group, comprised of the following functional components:

  • - Support reporting CSI of an SCell belonging to secondary PUCCH group by PUSCH or PUCCH of active serving cells belonging to primary PUCCH group, for both during and after SCell activation procedure;
  • - Support reporting CSI of an SCell belonging to primary PUCCH group by PUSCH or PUCCH of active serving cells belonging to secondary PUCCH group, for both during and after SCell activation procedure;
  • - Support for P-CSI and A-CSI for cross-PUCCH group CSI reporting;
  • - computationTimeForA-CSI-r16 indicates the CSI computation time for A-CSI; if 'relaxed' is reported, the additionalSymbols-r16 shall be reported to indicate for each supported SCS the required additional number of symbols in addition to existing Z and Z' for aperiodic CSI report for cross-PUCCH group CSI reporting (the same SCS set definition as in clause 5.4 of TS 38.214 [12]). The value s14 indicates 14 symbols, and so on. For FR2-2 bands, the time relaxation values of the required additional number of symbols for SCS 480/960 kHz (\mu=5 and \mu=6) are the same amount of absolute time as UE reported for SCS 120kHz (\mu=3).
  • - sp-CSI-ReportingOnPUCCH-r16 indicates whether the UE supports SP-CSI reporting on PUCCH for cross-PUCCH group CSI reporting;
  • - sp-CSI-ReportingOnPUSCH-r16 indicates whether the UE supports SP-CSI reporting on PUSCH for cross-PUCCH group CSI reporting;
  • - carrierTypePairList-r16 indicates one or multiple supported carrier type pairs(s). For each supported carrier type pair in carrierTypePairList-r16:
    • - carrierForCSI-Measurement-r16 indicates the carrier type in a PUCCH group in which CSI measurement is performed;
    • - carrierForCSI-Reporting-r16 indicates the carrier type in the other PUCCH group in which CSI report is performed,
    • - where a carrier type is one of {fr1-NonSharedTDD-r16, fr1-SharedTDD-r16, fr1-NonSharedFDD-r16, fr2-r16}

UE indicating support of this feature shall indicate csi-ReportFramework and indicate support of either twoPUCCH-Group or twoPUCCH-Grp-ConfigurationsList-r16.

NOTE 1: For a band combination with SUL, the SUL band is counted as one of the bands.

NOTE 2: For a band combination with SDL, the SDL band is counted as one of the bands. SDL is indicated as 'FR1-NonSharedFDD' carrier type. Per UE capabilities that are TDD only are not applicable to SDL.

NOTE 3: When the carrier type of NUL is indicated for PUCCH/PUSCH transmission location for CSI measurement or CSI reporting, the SUL in the same cell as in the NUL can also be configured for PUCCH/PUSCH transmission.

| BC | No | N/A | N/A | +|

csi-RS-IM-ReceptionForFeedbackPerBandComb
Indicates support of CSI-RS and CSI-IM reception for CSI feedback. This capability signalling comprises the following parameters:

  • - maxNumberSimultaneousNZP-CSI-RS-ActBWP-AllCC indicates the maximum number of simultaneous CSI-RS resources (irrespective of the associated codebook type) in active BWPs across all CCs, and across MCG and SCG in case of NR-DC. The network applies this limit in addition to the limits signalled in MIMO-ParametersPerBand->maxNumberSimultaneousNZP-CSI-RS-PerCC and in Phy-ParametersFRX-Diff->maxNumberSimultaneousNZP-CSI-RS-PerCC;
  • - totalNumberPortsSimultaneousNZP-CSI-RS-ActBWP-AllCC indicates the total number of CSI-RS ports in simultaneous CSI-RS resources (irrespective of the associated codebook type) in active BWPs across all CCs, and across MCG and SCG in case of NR-DC. The network applies this limit in addition to the limits signalled in MIMO-ParametersPerBand->totalNumberPortsSimultaneousNZP-CSI-RS-PerCC and in Phy-ParametersFRX-Diff->totalNumberPortsSimultaneousNZP-CSI-RS-PerCC.

The UE is mandated to report csi-RS-IM-ReceptionForFeedbackPerBandComb.

| BC | Yes | N/A | N/A | + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|----------| +| dci-FormatsPCellPSCellUSS-Sets-r17
Indicates whether UE supports the monitoring DCI formats 0_1, 1_1, 1_0_2 (if supported), 1_2 (if supported) on PCell/PSCell USS set(s).

UE indicating support of this feature shall indicate support of crossCarrierSchedulingSCell-SpCellTypeA-r17 . | BC | No | N/A | FR1 only | +| defaultQCL-CrossCarrierA-CSI-Trig-r16
Indicates whether the UE can be configured with enabledDefaultBeamForCCS for default QCL assumption for cross-carrier A-CSI-RS triggering for same/different numerologies as specified in TS 38.213 [11].

Value diffOnly indicates the UE supports this feature for different SCS combination(s).
Value both indicates the UE supports this feature for same SCS and for different SCS combination(s) (low-to-high, high-to-low or both) reported for crossCarrierA-CSI-trigDiffSCS-r16 . | BC | No | N/A | N/A | +| demodulationEnhancementCA-r17
Indicates whether the UE supports the enhanced demodulation processing for carrier aggregation for HST-SFN joint transmission scheme with velocity up to 500km/h as specified in TS 38.101-4 [18].

UE indicating support of this feature shall indicate support of demodulationEnhancement-r16 . | BC | No | No | FR1 only | +| diffNumerologyAcrossPUCCH-Group
Indicates whether different numerology across two NR PUCCH groups for data and control channel at a given time in NR CA and (NG)EN-DC/NE-DC is supported by the UE. | BC | No | N/A | N/A | +| diffNumerologyAcrossPUCCH-Group-CarrierTypes-r16
Indicates whether different numerology across two NR PUCCH groups for data and control channel at a given time in NR CA for UE supporting two PUCCH groups with 3 or more bands with at least two carrier types. UE indicating support of this feature shall indicate support of twoPUCCH-Grp-ConfigurationsList-r16 . | BC | No | N/A | N/A | +| diffNumerologyWithinPUCCH-GroupLargerSCS
Indicates whether UE supports different numerology across carriers within a PUCCH group and a same numerology between DL and UL per carrier for data/control channel at a given time in NR CA, (NG)EN-DC/NE-DC and NR-DC. In case of NR CA and (NG)EN-DC/NE-DC with one NR PUCCH group and in case of NR CA with two NR PUCCH groups, it also indicates whether the UE supports different numerologies across NR carriers within the same NR PUCCH group up to two different numerologies within the same NR PUCCH group, wherein NR PUCCH is sent on the carrier with larger SCS for data and control channel at a given time. In case of (NG)EN-DC/NE-DC with two NR PUCCH groups, it indicates whether the UE supports different numerologies across NR carriers up to two different numerologies within an NR PUCCH group in FR1, wherein NR PUCCH is sent on the carrier with larger SCS, and same numerology across NR carriers within another NR PUCCH group in FR2 for data and control channel at a given time. In case of NR-DC, it indicates whether the UE supports different numerologies across NR carriers within the same NR PUCCH group in MCG (in FR1) up to two different numerologies within the same NR PUCCH group wherein NR PUCCH is sent on the carrier with larger SCS for data/control channel at a given time; and same numerology across NR carriers in SCG (in FR2). | BC | No | N/A | N/A | +| diffNumerologyWithinPUCCH-GroupLargerSCS-CarrierTypes-r16
Indicates whether UE supports different numerology across carriers up to 2 different numerologies within the same PUCCH group wherein PUCCH is sent on the carrier with larger SCS for data/control channel at a given time in NR CA for UE supporting two PUCCH groups with 3 or more bands with at least two carrier types. UE indicating support of this feature shall indicate support of twoPUCCH-Grp-ConfigurationsList-r16 .

NOTE: PUCCH is sent on a carrier with SCS not smaller than SCS of any DL carriers corresponding to the PUCCH group. | BC | No | N/A | N/A | + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|----------| +|

diffNumerologyWithinPUCCH-GroupSmallerSCS
Indicates whether UE supports different numerology across carriers within a PUCCH group and a same numerology between DL and UL per carrier for data/control channel at a given time in NR CA, (NG)EN-DC/NE-DC and NR-DC. In case of NR CA and (NG)EN-DC/NE-DC with one NR PUCCH group and in case of NR CA with two NR PUCCH groups, it also indicates whether the UE supports different numerologies across NR carriers within the same NR PUCCH group up to two different numerologies within the same NR PUCCH group, wherein NR PUCCH is sent on the carrier with smaller SCS for data and control channel at a given time. In case of (NG)EN-DC/NE-DC with two NR PUCCH groups, it indicates whether the UE supports different numerologies across NR carriers up to two different numerologies within an NR PUCCH group in FR1, wherein NR PUCCH is sent on the carrier with smaller SCS, and same numerology across NR carriers within another NR PUCCH group in FR2 for data and control channel at a given time. In case of NR-DC, it indicates whether the UE supports different numerologies across NR carriers within the same NR PUCCH group in MCG (in FR1) up to two different numerologies within the same NR PUCCH group wherein NR PUCCH is sent on the carrier with smaller SCS for data/control channel at a given time; and same numerology across NR carriers in SCG (in FR2).

| BC | No | N/A | N/A | +|

diffNumerologyWithinPUCCH-GroupSmallerSCS-CarrierTypes-r16
Indicates whether UE supports different numerology across carriers up to 2 different numerologies within the same PUCCH group wherein PUCCH is sent on the carrier with smaller SCS for data/control channel at a given time in NR CA for UE supporting two PUCCH groups with 3 or more bands with at least two carrier types. UE indicating support of this feature shall indicate support of twoPUCCH-Grp-ConfigurationsList-r16.

NOTE: NR PUCCH is sent on a carrier with SCS not larger than SCS of any DL carriers corresponding to the NR PUCCH group.

| BC | No | N/A | N/A | +|

disablingScalingFactorDeactSCell-r17
Indicates whether UE supports disabling scaling factor \alpha for Cross-carrier scheduling (CCS) from SCell configured with cross-carrier scheduling to PCell/PSCell (sSCell) to PCell/PSCell(Type A or Type B) when sSCell is deactivated (i.e. scaling factor \alpha is not applied for PDCCH overbooking/BD/CCE limit computation when sSCell is deactivated).

UE indicating support of this feature shall indicate support of crossCarrierSchedulingSCell-SpCellTypeA-r17 or crossCarrierSchedulingSCell-SpCellTypeB-r17.

| BC | No | N/A | FR1 only | +|

disablingScalingFactorDormantSCell-r17
Indicates whether UE supports disabling scaling factor \alpha for Cross-carrier scheduling (CCS) from SCell configured with cross-carrier scheduling to PCell/PSCell (sSCell) to PCell/PSCell(Type A or Type B) when sSCell is switched to dormant BWP (i.e. scaling factor \alpha is not applied for PDCCH overbooking/BD/CCE limit computation when sSCell is switched to dormant BWP).

UE indicating support of this feature shall indicate support of crossCarrierSchedulingSCell-SpCellTypeA-r17 or crossCarrierSchedulingSCell-SpCellTypeB-r17.

| BC | No | N/A | FR1 only | +|

dmrs-BundlingNonBackToBackTX-PerBC-r17
Indicates whether the UE supports DM-RS bundling for non-back-to-back transmission for consecutive slots for PUSCH and PUCCH only for corresponding supported back-to-back transmission as reported in dmrs-BundlingPUSCH-RepTypeAPerBC-r17, dmrs-BundlingPUSCH-RepTypeBPerBC-r17, dmrs-BundlingPUSCH-multiSlotPerBC-r17 or dmrs-BundlingPUCCH-RepPerBC-r17.

UE indicating support of this feature shall also indicate support of at least one of dmrs-BundlingPUSCH-RepTypeAPerBC-r17, dmrs-BundlingPUSCH-RepTypeBPerBC-r17, dmrs-BundlingPUSCH-multiSlotPerBC-r17 or dmrs-BundlingPUCCH-RepPerBC-r17.

NOTE: This capability is only applicable when UE is configured with single uplink carrier within a frequency range.

| BC | No | N/A | N/A | + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|-----| +|

dmrs-BundlingPUCCH-RepPerBC-r17
Indicates whether the UE supports DM-RS bundling for PUCCH repetitions for PUCCH formats 1/3/4 over consecutive symbols.

UE indicating support of this feature shall also indicate support of maxDurationDMRS-Bundling-r17 in at least one of the bands in the band combination and pucch-Repetition-F1-3-4.

This feature is applicable to following multiple carrier scenarios in addition to single carrier scenarios:

  • - FR1+FR2 UL CA, FR1+FR2 DC, and EN-DC with NR on FR2. DMRS bundling configuration is limited to one uplink NR carrier in total on all FRs at a time.
  • - FR1 inter-band DL CA with a "single" uplink band configured, meaning no switching to transmit SRS on another carrier.
  • - DL CA with "additional" UL carrier configured with SRS only (i.e. no PUCCH/PUSCH configured).
  • - FR1 inter-band UL CA with DMRS bundling.
  • - SUL with DMRS bundling.

For the last three scenarios listed above, DMRS bundling can be applied with the following conditions:

  • - Concurrent transmissions scheduled/configured over multiple carriers are not expected by UE.
  • - Only configuration of a single TAG.
  • - Only applicable for the back-to-back case (i.e., zero gap between two transmissions within an actual TDW).
  • - Only one band can be configured with DMRS bundling at a time.

NOTE 1: Under the above conditions, phase continuity and power consistency within any actual TDW on one carrier is not impacted by operations on a different carrier.

NOTE 2: Under the above conditions, the events defined in clause 6.1.7 of TS 38.214 [12] for the carrier with DMRS bundling are not triggered by any transmission within any actual TDW on the other carrier.

NOTE 3: If the modulation scheme higher than QPSK is scheduled for transmission on any carrier configured with DMRS bundling, DMRS bundling is not applicable (i.e., the error case and up to UE implementation).

| BC | No | N/A | N/A | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|-----| + +| | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|-----| +|

dmrs-BundlingPUSCH-multiSlotPerBC-r17
Indicates whether the UE supports DM-RS bundling for TB processing over multi-slot (TBoMS) PUSCH over consecutive symbols.

UE indicating support of this feature shall also indicate support of maxDurationDMRS-Bundling-r17 and tb-ProcessingMultiSlotPUSCH-r17 in at least one of the bands in the band combination.

This feature is applicable to following multiple carrier scenarios in addition to single carrier scenarios:

  • - FR1+FR2 UL CA, FR1+FR2 DC, and EN-DC with NR on FR2. DMRS bundling configuration is limited to one uplink NR carrier in total on all FRs at a time.
  • - FR1 inter-band DL CA with a "single" uplink band configured, meaning no switching to transmit SRS on another carrier.
  • - DL CA with "additional" UL carrier configured with SRS only (i.e. no PUCCH/PUSCH configured).
  • - FR1 inter-band UL CA with DMRS bundling.
  • - SUL with DMRS bundling.

For the last three scenarios listed above, DMRS bundling can be applied with the following conditions:

  • - Concurrent transmissions scheduled/configured over multiple carriers are not expected by UE.
  • - Only configuration of a single TAG.
  • - Only applicable for the back-to-back case (i.e., zero gap between two transmissions within an actual TDW).
  • - Only one band can be configured with DMRS bundling at a time.

NOTE 1: Under the above conditions, phase continuity and power consistency within any actual TDW on one carrier is not impacted by operations on a different carrier.

NOTE 2: Under the above conditions, the events defined in clause 6.1.7 of TS 38.214 [12] for the carrier with DMRS bundling are not triggered by any transmission within any actual TDW on the other carrier.

NOTE 3: If the modulation scheme higher than QPSK is scheduled for transmission on any carrier configured with DMRS bundling, DMRS bundling is not applicable (i.e., the error case and up to UE implementation).

NOTE 4: If a UE reports support of tb-ProcessingRepMultiSlotPUSCH-r17 and dmrs-BundlingPUSCH-multiSlot-r17 in a band in the band combination and dmrs-BundlingPUSCH-multiSlotPerBC-r17 is supported for the band combination, the UE supports DMRS bundling for the repetitions of TBoMS for the band.

| BC | No | N/A | N/A | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|-----| + +| | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|-----| +|

dmrs-BundlingPUSCH-RepTypeAPerBC-r17
Indicates whether the UE supports DM-RS bundling for PUSCH repetition type A over consecutive symbols.

UE indicating support of this feature shall also indicate support of maxDurationDMRS-Bundling-r17 in at least one of the bands in the band combination and at least one of type1-PUSCH-RepetitionMultiSlots, type2-PUSCH-RepetitionMultiSlots or pusch-RepetitionMultiSlots.

This feature is applicable to following multiple carrier scenarios in addition to single carrier scenarios:

  • - FR1+FR2 UL CA, FR1+FR2 DC, and EN-DC with NR on FR2. DMRS bundling configuration is limited to one uplink NR carrier in total on all FRs at a time.
  • - FR1 inter-band DL CA with a "single" uplink band configured, meaning no switching to transmit SRS on another carrier.
  • - DL CA with "additional" UL carrier configured with SRS only (i.e. no PUCCH/PUSCH configured)
  • - FR1 inter-band UL CA with DMRS bundling
  • - SUL with DMRS bundling

For the last three scenarios listed above, DMRS bundling can be applied with the following conditions:

  • - Concurrent transmissions scheduled/configured over multiple carriers are not expected by UE
  • - Only configuration of a single TAG
  • - Only applicable for the back-to-back case (i.e., zero gap between two transmissions within an actual TDW)
  • - Only one band can be configured with DMRS bundling at a time

NOTE 1: Under the above conditions, phase continuity and power consistency within any actual TDW on one carrier is not impacted by operations on a different carrier.

NOTE 2: Under the above conditions, the events defined in clause 6.1.7 of TS 38.214 [12] for the carrier with DMRS bundling are not triggered by any transmission within any actual TDW on the other carrier.

NOTE 3: If the modulation scheme higher than QPSK is scheduled for transmission on any carrier configured with DMRS bundling, DMRS bundling is not applicable (i.e., the error case and up to UE implementation).

| BC | No | N/A | N/A | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|-----| + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|-----| +|

dmrs-BundlingPUSCH-RepTypeBPerBC-r17
Indicates whether the UE supports DM-RS bundling for PUSCH repetition type B over consecutive symbols.

UE indicating support of this feature shall also indicate support of maxDurationDMRS-Bundling-r17 in at least one of the bands in the band combination and pusch-RepetitionTypeB-r16.

This feature is applicable to following multiple carrier scenarios in addition to single carrier scenarios:

  • - FR1+FR2 UL CA, FR1+FR2 DC, and EN-DC with NR on FR2. DMRS bundling configuration is limited to one uplink NR carrier in total on all FRs at a time.
  • - FR1 inter-band DL CA with a "single" uplink band configured, meaning no switching to transmit SRS on another carrier.
  • - DL CA with "additional" UL carrier configured with SRS only (i.e. no PUCCH/PUSCH configured).
  • - FR1 inter-band UL CA with DMRS bundling.
  • - SUL with DMRS bundling.

For the last three scenarios listed above, DMRS bundling can be applied with the following conditions:

  • - Concurrent transmissions scheduled/configured over multiple carriers are not expected by UE.
  • - Only configuration of a single TAG.
  • - Only applicable for the back-to-back case (i.e., zero gap between two transmissions within an actual TDW).
  • - Only one band can be configured with DMRS bundling at a time.

NOTE 1: Under the above conditions, phase continuity and power consistency within any actual TDW on one carrier is not impacted by operations on a different carrier.

NOTE 2: Under the above conditions, the events defined in clause 6.1.7 of TS 38.214 [12] for the carrier with DMRS bundling are not triggered by any transmission within any actual TDW on the other carrier.

NOTE 3: If the modulation scheme higher than QPSK is scheduled for transmission on any carrier configured with DMRS bundling, DMRS bundling is not applicable (i.e., the error case and up to UE implementation).

| BC | No | N/A | N/A | +|

dmrs-BundlingRestartPerBC-r17
Indicates whether the UE supports restarting DM-RS bundling after the events triggered by DCI or MAC CE that violate power consistency and phase continuity.

UE indicating support of this feature shall also indicate support of maxDurationDMRS-Bundling-r17 in at least one of the bands in the band combination.

NOTE: Events which are triggered by DCI or MAC CE, but do not require UE capability to resume maintaining power consistency and/or phase continuity as specified in clause 6.1.7 of TS 38.214 [12] are excluded from this feature.

| BC | No | N/A | N/A | +|

dualPA-Architecture
For band combinations with single-band with UL CA, this field indicates the support of dual PA and dual LO frequencies for FR1, or dual LO frequencies for FR2. If absent in such band combinations, the UE supports single PA and single LO frequency for all the ULs for FR1, or single LO frequency for all the ULs for FR2. For other band combinations, this field is not applicable.

| BC | No | N/A | N/A | + +| | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|----------|-----| +|

dynamicPUCCH-CellSwitchDiffLengthSingleGroup-r17
Indicates whether the UE supports PUCCH cell switching based on dynamic indication in the DCI scheduling the PUCCH for different length (in physical time) of overlapping PUCCH slots/sub-slots for a single PUCCH group only. The capability signalling comprises the following parameters:

  • - pucch-Group-r17 indicates for which PUCCH group the UE supports PUCCH cell switching based on dynamic indication. Value primaryGroupOnly indicates that only primary PUCCH group can support PUCCH cell switch, value secondaryGroupOnly indicates that only secondary PUCCH group can support PUCCH cell switch, and value eitherPrimaryOrSecondaryGroup indicates that either primary or secondary PUCCH group can support PUCCH cell switch.
  • - pucch-Group-Config-r17 indicates one or multiple of supported carrier type pairs that can support PUCCH cell switch, with fr1-FR1-NonSharedTDD-r17 indicating the carrier type pair (FR1 licensed TDD, FR1 licensed TDD), fr2-FR2-NonSharedTDD-r17 indicating the carrier type pair (FR2 licensed TDD, FR2 licensed TDD), and fr1-FR2-NonSharedTDD-r17 indicating the carrier type pair (FR1 licensed TDD, FR2 licensed TDD).

NOTE: This feature applies to cells in the same TAG only. If UE supporting this FG also supports both diffNumerologyWithinPUCCH-GroupSmallerSCS and diffNumerologyWithinPUCCH-GroupLargerSCS or both diffNumerologyWithinPUCCH-GroupSmallerSCS-CarrierTypes-r16 and diffNumerologyWithinPUCCH-GroupLargerSCS-CarrierTypes-r16 or maxUpTo3Diff-NumerologiesConfigSinglePUCCH-grp-r16 or maxUpTo4Diff-NumerologiesConfigSinglePUCCH-grp-r16 when UE is not configured with two NR PUCCH groups, the UE supports the cases of both same and different numerologies between switchable cells. Otherwise, the UE supports the case of same numerology between switchable cells.

| BC | No | TDD only | N/A | +|

dynamicPUCCH-CellSwitchSameLengthSingleGroup-r17
Indicates whether the UE supports PUCCH cell switching based on dynamic indication in the DCI scheduling the PUCCH for same length (in physical time) of overlapping PUCCH slots/sub-slots for a single PUCCH group only. The capability signalling comprises the following parameters:

  • - pucch-Group-r17 indicates for which PUCCH group the UE supports PUCCH cell switching based on dynamic indication. Value primaryGroupOnly indicates that only primary PUCCH group can support PUCCH cell switch, value secondaryGroupOnly indicates that only secondary PUCCH group can support PUCCH cell switch, and value eitherPrimaryOrSecondaryGroup indicates that either primary or secondary PUCCH group can support PUCCH cell switch.
  • - pucch-Group-Config-r17 indicates one or multiple of supported carrier type pairs that can support PUCCH cell switch, with fr1-FR1-NonSharedTDD-r17 indicating the carrier type pair (FR1 licensed TDD, FR1 licensed TDD), fr2-FR2-NonSharedTDD-r17 indicating the carrier type pair (FR2 licensed TDD, FR2 licensed TDD), and fr1-FR2-NonSharedTDD-r17 indicating the carrier type pair (FR1 licensed TDD, FR2 licensed TDD).

NOTE: This feature applies to cells in the same TAG only. If UE supporting this FG also supports both diffNumerologyWithinPUCCH-GroupSmallerSCS and diffNumerologyWithinPUCCH-GroupLargerSCS or both diffNumerologyWithinPUCCH-GroupSmallerSCS-CarrierTypes-r16 and diffNumerologyWithinPUCCH-GroupLargerSCS-CarrierTypes-r16 or maxUpTo3Diff-NumerologiesConfigSinglePUCCH-grp-r16 or maxUpTo4Diff-NumerologiesConfigSinglePUCCH-grp-r16 when UE is not configured with two NR PUCCH groups, the UE supports the cases of both same and different numerologies between switchable cells. Otherwise, the UE supports the case of same numerology between switchable cells.

| BC | No | TDD only | N/A | + +| | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|----------|-----| +|

dynamicPUCCH-CellSwitchDiffLengthTwoGroups-r17
Indicates whether the UE supports PUCCH cell switching based on dynamic indication in the DCI scheduling the PUCCH for different length (in physical time) of overlapping PUCCH slots/sub-slots for two PUCCH groups. The capability indicates one or multiple of supported configuration(s) of {primary PUCCH group config, secondary PUCCH group config}. The capability signalling of each primary or secondary PUCCH group configuration indicates one or multiple of carrier type pairs that can support PUCCH cell switch, with fr1-FR1-NonSharedTDD-r17 indicating the carrier type pair (FR1 licensed TDD, FR1 licensed TDD), fr2-FR2-NonSharedTDD-r17 indicating the carrier type pair (FR2 licensed TDD, FR2 licensed TDD), and fr1-FR2-NonSharedTDD-r17 indicating the carrier type pair (FR1 licensed TDD, FR2 licensed TDD).

NOTE: This feature applies to cells in the same TAG only. If UE supporting this FG also supports both diffNumerologyWithinPUCCH-GroupSmallerSCS and diffNumerologyWithinPUCCH-GroupLargerSCS or both diffNumerologyWithinPUCCH-GroupSmallerSCS-CarrierTypes-r16 and diffNumerologyWithinPUCCH-GroupLargerSCS-CarrierTypes-r16, the UE supports the cases of both same and different numerologies between switchable cells. Otherwise, the UE supports the case of same numerology between switchable cells.

| BC | No | TDD only | N/A | +|

dynamicPUCCH-CellSwitchSameLengthTwoGroups-r17
Indicates whether the UE supports PUCCH cell switching based on dynamic indication in the DCI scheduling the PUCCH for same length (in physical time) of overlapping PUCCH slots/sub-slots for two PUCCH groups. The capability indicates one or multiple of supported configuration(s) of {primary PUCCH group config, secondary PUCCH group config}. The capability signalling of each primary or secondary PUCCH group configuration indicates one or multiple of carrier type pairs that can support PUCCH cell switch, with fr1-FR1-NonSharedTDD-r17 indicating the carrier type pair (FR1 licensed TDD, FR1 licensed TDD), fr2-FR2-NonSharedTDD-r17 indicating the carrier type pair (FR2 licensed TDD, FR2 licensed TDD), and fr1-FR2-NonSharedTDD-r17 indicating the carrier type pair (FR1 licensed TDD, FR2 licensed TDD).

NOTE: This feature applies to cells in the same TAG only. If UE supporting this FG also supports both diffNumerologyWithinPUCCH-GroupSmallerSCS and diffNumerologyWithinPUCCH-GroupLargerSCS or both diffNumerologyWithinPUCCH-GroupSmallerSCS-CarrierTypes-r16 and diffNumerologyWithinPUCCH-GroupLargerSCS-CarrierTypes-r16, the UE supports the cases of both same and different numerologies between switchable cells. Otherwise, the UE supports the case of same numerology between switchable cells.

| BC | No | TDD only | N/A | +|

fdm-CodebookForMux-UnicastMulticastHARQ-ACK-r17
Indicates whether the UE supports FDM-ed Type-1 and Type-2 HARQ-ACK codebooks for multiplexing HARQ-ACK for unicast and HARQ-ACK for multicast, comprised of the following functional components:

  • - Support of FDM-ed Type-1 HARQ-ACK codebooks for multiplexing HARQ-ACK for unicast and ACK/NACK-based HARQ-ACK for multicast on PUCCH or PUSCH;
  • - Support of Type-2 HARQ-ACK codebooks for multiplexing HARQ-ACK for unicast and HARQ-ACK for multicast on PUCCH or PUSCH with max number of G-RNTIs indicated in maxNumberG-RNTI-HARQ-ACK-Codebook-r17, which is not larger than max number of G-RNTIs indicated in maxNumberG-RNTI-r17 or G-CS-RNTIs indicated in maxNumberG-CS-RNTI-r17.

A UE supporting this feature shall also indicate support of fdm-MulticastUnicast-r17, and at least one of {ack-NACK-FeedbackForMulticast-r17, nack-OnlyFeedbackForMulticast-r17, ack-NACK-FeedbackForSPS-Multicast-r17, nack-OnlyFeedbackForSPS-Multicast-r17}.

NOTE 1: FDM-ed Type-1 HARQ-ACK codebook is generated by concatenating the Type-1 sub-codebook for unicast and the Type-1 sub-codebook for multicast.

NOTE 2: The Type-2 HARQ-ACK codebook is generated by concatenating the Type-2 sub-codebook for unicast and the Type-2 sub-codebook for multicast.

| BC | No | N/A | N/A | + +| | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|----------|----------| +| half-DuplexTDD-CA-SameSCS-r16
Indicates whether the UE supports directional collision handling between reference and other cell(s) for half-duplex operation in TDD CA with same SCS. The UE can include this field for band combinations including only intra-band TDD CA or if simultaneousRxBTxInterBandCA is not present for band combinations involving mix of intra-band TDD CA and inter-band TDD CA.
If this field is included in ca-ParametersNR-forDC-v1610 for IAB-MT, it indicates IAB-MT supports directional collision handling between reference and other cells for half-duplex operation in TDD NR-DC with same SCS across MCG and SCG. | BC | No | TDD only | N/A | +| higherPowerLimit-r17
Indicates whether UE supports increase in maximum output power above the power class indication for inter-band UL CA and NR-DC band combinations as defined in clause 6.2A of TS 38.101-1 [2]. | BC | No | N/A | FR1 only | +| interCA-NonAlignedFrame-r16
Indicates whether the UE supports inter-band carrier aggregation operation where, within the same cell group, the frame boundaries of the SpCell and the SCell(s) are not aligned, the slot boundaries are aligned and the lowest subcarrier spacing of the subcarrier spacings given in scs-SpecificCarrierList for SpCell is smaller than or equal to the lowest subcarrier spacing of the subcarrier spacings given in scs-SpecificCarrierList for each of the non-aligned SCells. | BC | No | N/A | N/A | +| interCA-NonAlignedFrame-B-r16
Indicates whether the UE supports inter-band carrier aggregation operation where, within the same cell group, the frame boundaries of the SpCell and the SCell(s) are not aligned, the slot boundaries are aligned and the lowest subcarrier spacing of the subcarrier spacings given in scs-SpecificCarrierList for SpCell is larger than the lowest subcarrier spacing of the subcarrier spacings given in scs-SpecificCarrierList for at least one of the non-aligned SCells.
A UE indicating support of interCA-NonAlignedFrame-B-r16 shall also indicate support of interCA-NonAlignedFrame-r16 . | BC | No | N/A | N/A | +| interFreqDAPS-r16
Indicates whether the UE supports inter-frequency handover, e.g. support of simultaneous DL reception of PDCCH and PDSCH from source and target cell. A UE indicating this capability shall also support inter-frequency synchronous DAPS handover, and single UL transmission for inter-frequency DAPS handover. The capability signalling comprises of the following parameters:
  • - interFreqAsyncDAPS-r16 indicates whether the UE supports asynchronous DAPS handover.
  • - interFreqDiffSCS-DAPS-r16 indicates whether the UE supports different SCSs in source PCell and inter-frequency target PCell in DAPS handover. The UE only includes this field if different SCSs can be supported in both UL and DL. If absent, the UE does not support either UL or DL SCS being different in DAPS handover.
  • - interFreqMultiUL-TransmissionDAPS-r16 indicates whether the UE supports simultaneous UL transmission in source PCell and target PCell during a DAPS handover. The UE can include this field only if any of semiStaticPowerSharingDAPS-Mode1-r16, semiStaticPowerSharingDAPS-Mode2-r16 or dynamicPowersharingDAPS-r16 are included. Otherwise, the UE does not include this field.
  • - interFreqSemiStaticPowerSharingDAPS-Mode1-r16 indicates whether the UE supports semi-static UL power sharing mode 1 during DAPS handover between source and target cells of same FR.
  • - interFreqSemiStaticPowerSharingDAPS-Mode2-r16 indicates whether the UE supports semi-static UL power sharing mode 2 during DAPS handover between source and target cells of same FR. It is only applicable to DAPS Handover in synchronous scenarios. The UE only includes this field if semiStaticPowerSharingDAPS-Mode1-r16 is included. Otherwise, the UE does not include this field.
  • - interFreqDynamicPowersharingDAPS-r16 indicates the value of T offset (short or long) that the UE supports for dynamic UL power sharing during DAPS handover between source and target cells of same FR. The UE only include this field if semiStaticPowerSharingDAPS-Mode1-r16 is included. Otherwise, the UE does not include this field.
  • - interFreqUL-TransCancellationDAPS-r16 indicates support of cancelling UL transmission to the source PCell for inter-frequency DAPS handover.
| BC | No | N/A | N/A | + +| | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|----------| +| intraBandFreqSeparationUL-AggBW-GapBW-r16
Indicates the UL frequency separation class between lower edge of lowest CC and upper edge of highest CC of Intra-band UL non-contiguous CA, i.e. including both the aggregated bandwidth and the gap bandwidth. 3 frequency separation classes are introduced and the values are defined in Table 5.3A.5-2 of TS 38.101-1 [2]. | BC | No | N/A | FR1 only | +| intraBandNR-CA-non-collocated-r18
Indicates whether the UE supports TDD-TDD intra-band non-collocated NR-CA operation with MTTC/MRTD requirements according to Table 7.5.4.1/Table 7.6.4-2 in 38.133 [5] and UE RF requirements for intra-band non-collocated NR-CA including 7.10A in 38.101-1 [2]. And the UE also supports TDD-TDD intra-band NR-CA operation with MRTD according to Table 7.6.4-1 in 38.133 and UE RF requirements for intra-band NR-CA except for 7.10A in 38.101-1 [2].

This capability is only supported for band n77/n78. | BC | No | N/A | FR1 only | +| jointSearchSpaceSwitchAcrossCells-r16
Indicates whether the UE supports being configured with a group of cells and switching search space set group jointly over these cells. If the UE supports this feature, the UE needs to report searchSpaceSwitchWithDCI-r16 or searchSpaceSwitchWithoutDCI-r16 . | BC | No | N/A | N/A | +| maxCC-32-DL-HARQ-ProcessFR2-2-r17
Indicates the maximum number of component carriers that can be configured with 32 DL HARQ processes. Value n1 means 1 DL HARQ process, value n2 means 2 DL HARQ processes, and so on.

UE supporting this feature shall indicate support of support32-DL-HARQ-ProcessPerSCS-r17 . | BC | No | NA | NA | +| maxCC-32-UL-HARQ-ProcessFR2-2-r17
Indicates the maximum number of component carriers that can be configured with 32 UL HARQ processes. Value n1 means 1 UL HARQ process, value n2 means 2 UL HARQ processes, and so on.

UE supporting this feature shall indicate support of support32-UL-HARQ-ProcessPerSCS-r17 . | BC | No | NA | NA | +| maxUplinkDutyCycle-interBandCA-PC2-r17
Indicates the maximum average percentage of symbols during a certain evaluation period that can be scheduled for uplink transmission so as to ensure compliance with applicable electromagnetic energy absorption requirements provided by regulatory bodies. The average percentage of uplink symbols is specified in 6.2A.1.3 in TS 38101-1[2] and the capability applies to the CA combinations listed in table 6.2A.1.3-1 in TS 38101-1[2]. If the field is absent, UE shall work on power class 2 regardless of UL duty cycle and may use P-MPR c as defined in 6.2.4 in TS 38101-1[2] if necessary.
Value n50 corresponds to 50%, value n60 corresponds to 60% and so on.

NOTE: Specific targeted UL duty cycle percentage is not assumed if the field is absent. | BC | No | N/A | FR1 only | +| maxUplinkDutyCycle-SULcombination-PC2-r17
Indicates the maximum average percentage of symbols during a certain evaluation period that can be scheduled for uplink transmission so as to ensure compliance with applicable electromagnetic energy absorption requirements provided by regulatory bodies. The average percentage of uplink symbols is specified in 6.2C.1 in TS 38101-1[2] and the capability applies to all the SUL configurations with 1 SUL band + 1 TDD band.
If the field is absent, UE shall work on power class 2 regardless of UL duty cycle and may use P-MPR c as defined in 6.2.4 in TS 38101-1[2] if necessary.
Value n50 corresponds to 50%, value n60 corresponds to 60% and so on.

NOTE: Specific targeted UL duty cycle percentage is not assumed if the field is absent. | BC | No | N/A | FR1 only | + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|-----| +|

maxUpTo3Diff-NumerologiesConfigSinglePUCCH-grp-r16
Indicates the UE support of up to 3 different numerologies in the same PUCCH group where UE is not configured with two NR PUCCH groups by indicating one or multiple NR carrier types {FR1 licensed TDD (fr1-NonSharedTDD-r16), FR1 unlicensed TDD (fr1-SharedTDD-r16), FR1 licensed FDD (fr1-NonSharedFDD-r16), FR2(fr2-r16)} that can transmit the PUCCH for NR part of (NG)EN-DC, NE-DC and NR-CA.

NOTE: When the carrier type of NUL is indicated for PUCCH transmission location, the SUL in the same cell as in the NUL can also be configured for PUCCH transmission.

| BC | No | N/A | N/A | +|

maxUpTo4Diff-NumerologiesConfigSinglePUCCH-grp-r16
Indicates the UE support of up to 4 different numerologies in the same PUCCH group where UE is not configured with two NR PUCCH groups by indicating one or multiple the NR carrier types {FR1 licensed TDD (fr1-NonSharedTDD-r16), FR1 unlicensed TDD (fr1-SharedTDD-r16), FR1 licensed FDD (fr1-NonSharedFDD-r16), FR2(fr2-r16)} that can transmit the PUCCH for NR part of (NG)EN-DC, NE-DC and NR-CA.

NOTE: When the carrier type of NUL is indicated for PUCCH transmission location, the SUL in the same cell as in the NUL can also be configured for PUCCH transmission.

| BC | No | N/A | N/A | +|

mode1-ForType1-CodebookGeneration-r17
Indicates whether the UE supports type1-Codebook-Generation-Mode configured as mode 1, for multiplexing HARQ-ACK for unicast and HARQ-ACK for multicast on PUCCH or PUSCH.

A UE supporting this feature shall also indicate support of mode2-TDM-CodebookForMux-UnicastMulticastHARQ-ACK-r17.

| BC | No | N/A | N/A | +|

mode2-TDM-CodebookForMux-UnicastMulticastHARQ-ACK-r17
Indicates whether the UE supports Mode 2 TDM-ed Type-1 and Type-2 HARQ-ACK codebook for multiplexing HARQ-ACK for unicast and HARQ-ACK for multicast, comprised of the following functional components:

  • - Support of Mode 2 TDM-ed Type-1 HARQ-ACK codebook for multiplexing HARQ-ACK for unicast and ACK/NACK-based HARQ-ACK for multicast on PUCCH or PUSCH;
  • - Support of Type-2 HARQ-ACK codebooks for multiplexing HARQ-ACK for unicast and HARQ-ACK for multicast on PUCCH or PUSCH with max number of G-RNTIs indicated in maxNumberG-RNTI-HARQ-ACK-Codebook-r17, which is not larger than max number of G-RNTIs indicated in maxNumberG-RNTI-r17 or G-CS-RNTIs indicated in maxNumberG-CS-RNTI-r17.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 or nack-OnlyFeedbackForMulticast-r17 or ack-NACK-FeedbackForSPS-Multicast-r17 or nack-OnlyFeedbackForSPS-Multicast-r17.

NOTE 1: Mode 2 TDM-ed Type-1 HARQ-ACK codebook is generated based on the union TDRA tables from unicast and multicast and the union of k1 sets from unicast and multicast.

NOTE 2: The Type-2 HARQ-ACK codebook is generated by concatenating the Type-2 sub-codebook for unicast and the Type-2 sub-codebook for multicast.

| BC | No | N/A | N/A | +|

msgA-SUL-r16
Indicates whether the UE supports MSGA transmission in a band combination including SUL. A UE supporting this feature shall also indicate support of twoStepRACH-r16.

| BC | No | N/A | N/A | + +| | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|-----| +|

mTRP-CSI-EnhancementPerBC-r17
Indicates support of CSI enhancements for multi-TRP including support of NZP CSI-RS resource pairs used as CMR (channel measurement resource) pairs for NCJT measurement hypothesis with N=1.
This feature also includes following parameters:

  • - maxNumNZP-CSI-RS-r17 indicates the maximum number of NZP CSI-RS resources in one CSI-RS resource set: Ks,max
  • - cSI-Report-mode-r17 indicates the CSI report mode selection. Mode indicates mode 1 with X=0, mode2 indicates mode 2, both indicate the support of both mode 1 with X=0 and mode 2.
  • - A list of supported combinations, up to 16, across all CCs simultaneously, where each combination is
    • - maxNumTx-Ports-r17 indicates the maximum number of Tx ports in one NZP CSI-RS resource associated with an NCJT measurement hypothesis
    • - maxTotalNumCMR-r17 indicates the maximum total number of CMRs for NCJT measurement
    • - maxTotalNumTx-PortsNZP-CSI-RS-r17: indicates the maximum total number of Tx ports of NZP CSI-RS resources associated with NCJT measurement hypotheses
    • - codebookMode-NCJT-r17 indicates the supported codebook modes for NCJT CSI.
| BC | No | N/A | N/A | +|

multiCell-PDSCH-DCI-1-3-DiffSCS-r18
Indicates whether the UE supports monitoring DCI format 1_3 for DL scheduling where scheduling cell is not included in a set of cells in same PUCCH group and supports Type-2 for 'Antenna port(s)' field
The number of unicast DL DCIs to process per N consecutive slots of scheduling cell for a set of cells configured for multi-cell PDSCH scheduling by DCI format 1_3

  • - One DCI format 1_3 for the set of cells and,
  • - One unicast DL DCI formats 1_0/1_1/1_2 (if supported) for each of the cells that are not scheduled by DCI 1_3
  • - For low-to-high SCS, N = 1.
  • - For high-to-low SCS, N is based on pair of (scheduling CC SCS, scheduled CC SCS): N=2 for (30,15), (60,30), (120,60) and N=4 for (60,15), (120,30), N = 8 for (120,15)

The UE monitors SS set(s) for DCI format 1_3 for a set of cells when search space set configurations for DCI format 1_3 for the set of cells with the same searchSpaceId are provided on both the scheduling cell and a serving cell in the set of cells Scheduling cell is PCell or SCell, and a set of cells includes only SCells.
The capability signalling comprises of the following parameters:

  • - coScheduledCellSCS-r18 indicates scheduling cell and co-scheduled cells have different SCS. The set of co-scheduled cells share the same SCS and carrier type
  • - combinationCarrierType-r18 indicates Scheduling cell and co-scheduled cells have same or different carrier type (FR1 licensed FDD or FR1 licensed TDD or FR1 unlicensed TDD or FR2-1 or FR2-2).
  • - maxNumberCoScheduledCell-r18 indicates the max number of co-scheduled cells per set of cells supported by UE is reported
  • - maxNumberSetsOfCellAcrossPUCCH-Group-r18 indicates the max number of sets of cells supported by UE across PUCCH groups
  • - maxNumberSetsOfCellScheduling-r18 indicates the max number of sets of cells supported by UE for a same scheduling cell
  • - harqFeedbackType-r18 indicates the supported HARQ feedback types. The UE shall report the same value for all supported BC.
  • - coScheduledCellIndicationScheme-r18 indicates the supported co-scheduled cell indication schemes

NOTE: Support of CCS with DL DCI formats 1_1/1_2 is according to crossCarrierSchedulingDL-DiffSCS-r16.

| BC | No | N/A | N/A | +|

multiPUCCH-ConfigForMulticast-r17
Indicates whether the UE supports PUCCH-ConfigurationList for multicast HARQ-ACK feedback, separate from that of unicast configurations.

A UE supporting this feature shall also indicate support of singlePUCCH-ConfigForMulticast-r17 and priorityIndicatorInDCI-Multicast-r17.

| BC | No | N/A | N/A | + +| | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|-----| +|

mux-HARQ-ACK-UnicastMulticast-r17
Indicates whether the UE supports multiplexing HARQ-ACK for unicast and for multicast with the same priority and different HARQ-ACK codebook types in a PUCCH or in a PUSCH.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 or nack-OnlyFeedbackForMulticast-r17 or ack-NACK-FeedbackForSPS-Multicast-r17 or nack-OnlyFeedbackForSPS-Multicast-r17.

| BC | No | N/A | N/A | +|

nack-OnlyFeedbackForMulticast-r17
Indicates whether the UE supports NACK-only based HARQ-ACK feedback for multicast RRC-based enabling/disabling with ACK/NACK transforming, comprised of the following functional components:

  • - Supports NACK-only based HARQ-ACK feedback and enabling/disabling NACK-only based HARQ-ACK feedback configured by RRC signalling for dynamic scheduling for multicast, including:
    • - A single TB with NACK-only feedback transmitted in PUCCH
    • - Multiple TB with NACK-only feedback transmitted in PUCCH by transforming into ACK/NACK bits
  • - Supports shared PUCCH resource configurations with unicast;
  • - Supports one or multiple TB with NACK-only feedback transmitted in PUSCH by transforming into ACK/NACK bits;
  • - Supports One or multiple TB with NACK-only feedback transmitted in PUCCH by transforming into ACK/NACK bits when multiplexing with other UCI.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17.

| BC | No | N/A | N/A | +|

nack-OnlyFeedbackForSPS-Multicast-r17
Indicates whether the UE supports RRC-based enabling/disabling NACK-only based feedback for SPS group-common PDSCH for multicast, comprised of the following functional components:

  • - Support NACK-only based HARQ-ACK feedback, and support of enabling/disabling NACK-only based HARQ-ACK feedback configured by RRC signalling for SPS group-common PDSCH without PDCCH scheduling, including:
    • - A single TB with NACK-only feedback transmitted in PUCCH
    • - Multiple TBs with NACK-only feedback transmitted in PUCCH by transforming into ACK/NACK bits
  • - Support of shared PUCCH resource configurations with unicast
  • - One or multiple TB with NACK-only feedback transmitted in PUSCH by transforming into ACK/NACK bits
  • - One or multiple TB with NACK-only feedback transmitted in PUCCH by transforming into ACK/NACK bits when multiplexing with other UCI

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17.

| BC | No | N/A | N/A | +|

nack-OnlyFeedbackSpecificResourceForMulticast-r17
Indicates whether the UE supports NACK-only based HARQ-ACK feedback for multicast corresponding to a specific sequence or a PUCCH transmission, comprised of the following functional components:

  • - Supports NACK-only based HARQ-ACK feedback for dynamic scheduling for multicast, including:
    • - Up to 4 TBs with NACK-only feedback transmitted in PUCCH by select one PUCCH resource
  • - Supports separate PUCCH resource configurations from unicast;
  • - Supports single TB with NACK-only feedback transmitted in PUCCH;
  • - Supports up to 4TBs with NACK-only feedback transmitted in PUSCH by transforming into ACK/NACK bits.

A UE supporting this feature shall also indicate support of nack-OnlyFeedbackForMulticast-r17.

| BC | No | N/A | N/A | + +| | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|----------| +|

nack-OnlyFeedbackSpecificResourceForSPS-Multicast-r17

Indicates whether the UE supports NACK-only based HARQ-ACK feedback for multicast corresponding to a specific sequence or a PUCCH transmission for SPS group-common PDSCH for multicast, comprised of the following functional components:

  • - Supports NACK-only based HARQ-ACK feedback for SPS PDSCH for multicast, including:
    • - Up to 2TBs with NACK-only feedback transmitted in PUCCH by select one PUCCH resource
  • - Supports separate SPS-PUCCH-AN-List from unicast;
  • - Single TB with NACK-only feedback transmitted in PUCCH;
  • - Up to 2TBs with NACK-only feedback transmitted in PUSCH by transforming into ACK/NACK bits.

UE supporting this feature shall also indicate support of nack-OnlyFeedbackForSPS-Multicast-r17.

| BC | No | N/A | N/A | +|

non-AlignedFrameBoundaries-r17

Indicates whether UE supports carrier aggregation with non-aligned frame boundaries for PCell/PSCell and SCell configured with cross-carrier scheduling to PCell/PSCell (sSCell) in inter-band CA. The capability indicates the band pairs of the {PCell/PSCell SCS in kHz, sSCell SCS in kHz} combination which supports non-aligned frame boundary PCell/PSCell and SCell. The band-pair is encoded as a bitmap with size L * (L - 1) / 2, and bit N (leftmost bit is indexed as bit 0) is set to "1" if the UE supports non-frame boundary for PCell/PSCell and SCell for the band pair (x, y), where L is the number of band entries in the band combination, x and y are the indices of the band entry in the band combination (the first band entry is indexed as 0), x < y, and N = x*(2*L - x - 1)/2 + y - x - 1.

UE indicating support of this feature shall indicate support of crossCarrierSchedulingSCell-SpCellTypeA-r17 or crossCarrierSchedulingSCell-SpCellTypeB-r17.

| BC | No | N/A | FR1 only | +|

parallelTxMsgA-SRS-PUCCH-PUSCH-r16

Indicates whether the UE supports parallel transmission of MsgA and SRS/PUCCH/PUSCH across CCs in an inter-band CA band combination. A UE supporting this feature shall also indicate support of parallelTxPRACH-SRS-PUCCH-PUSCH.

| BC | No | N/A | N/A | +|

parallelTxMsgA-SRS-PUCCH-PUSCH-intraBand-r17

Indicates whether the UE supports parallel transmission of MsgA and SRS/PUCCH/PUSCH across CCs in an intra-band non-contiguous CA band combination. The UE indicating support of this field shall also indicate support of parallelTxMsgA-SRS-PUCCH-PUSCH-r16 and parallelTxPRACH-SRS-PUCCH-PUSCH-intraBand-r17.

| BC | No | N/A | N/A | +|

parallelTxSRS-PUCCH-PUSCH

Indicates whether the UE supports parallel transmission of SRS and PUCCH/PUSCH across CCs in an inter-band CA band combination.

| BC | No | N/A | N/A | +|

parallelTxSRS-PUCCH-PUSCH-intraBand-r17

Indicates whether the UE supports parallel transmission of SRS and PUCCH/PUSCH across CCs in an intra-band non-contiguous CA band combination.

| BC | No | N/A | N/A | +|

parallelTxPRACH-SRS-PUCCH-PUSCH

Indicates whether the UE supports parallel transmission of PRACH and SRS/PUCCH/PUSCH across CCs in an inter-band CA band combination.

| BC | No | N/A | N/A | +|

parallelTxPRACH-SRS-PUCCH-PUSCH-intraBand-r17

Indicates whether the UE supports parallel transmission of PRACH and SRS/PUCCH/PUSCH across CCs in an intra-band non-contiguous CA band combination.

| BC | No | N/A | N/A | +|

parallelTxPUCCH-PUSCH-r17

Indicates whether the UE supports simultaneous PUCCH and PUSCH transmissions of different priority on different cells for inter-band CA.

| BC | No | N/A | N/A | +|

parallelTxPUCCH-PUSCH-SamePriority-r17

Indicates whether the UE supports simultaneous PUCCH and PUSCH transmissions of same priority on different cells in different bands for inter-band CA as specified in clause 9 of TS 38.213 [11].

| BC | No | N/A | N/A | + +| | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|-----| +|

pdcch-BlindDetectionCA-Mixed-r16, pdcch-BlindDetectionCA-Mixed-v16a0

This field indicates mixed operation of two variants of the number of blind detections in case of CA. UE indicating support of this feature shall also indicate support of pdcch-MonitoringMixed-r16. UE indicating support of pdcch-BlindDetectionCA-Mixed-v16a0 shall also indicate support of pdcch-MonitoringMixed-r16. Only one between pdcch-BlindDetectionCA-Mixed-r16 and pdcch-BlindDetectionCA-Mixed-NonAlignedSpan-r16 can be reported by UE.

| BC | No | N/A | N/A | +|

pdcch-BlindDetectionCA-Mixed-r18

Indicates the supported combinations of the capability on the number of CCs for CCE/BD scaling with DL CA with mix of Rel. 16 and Rel. 15 PDCCH monitoring capabilities on different carriers.

The capability signalling comprises the following parameters:

  • - blindDetectionCA-Mixed-r18 indicates the supported combination(s) of (pdcch-BlindDetectionCA-R15, pdcch-BlindDetectionCA-R16)
  • - supportedSpanArrangement-r18 indicates the supported span arrangement for CA

When a UE reports both pdcch-BlindDetectionCA-MixedExt-r16 and this capability, the value reported in this capability is used if the configured span pattern of any serving cell satisfies pdcch-MonitoringSpan2-2-r18.

UE indicating support of this feature shall also indicate support of (7,3) or (4,3) span based PDCCH monitoring for pdcch-MonitoringMixed-r16 and (2,2) span based PDCCH monitoring for pdcch-MonitoringMixed-r18 with additional restriction(s).

| BC | No | N/A | N/A | +|

pdcch-BlindDetectionCA-Mixed-NonAlignedSpan-r16, pdcch-BlindDetectionCA-Mixed-NonAlignedSpan-v16a0

This field indicates mixed operation of two variants of the number of blind detections in case of CA when the UE supports aligned span and non-aligned span. In the case of non-aligned span, when the configured number of CCs with Rel-16 PDCCH monitoring is larger than the UE reported value, PDCCH monitoring occasion(s) should be configured only on same symbol(s) every slot. UE indicating support of this feature shall also indicate support of pdcch-MonitoringMixed-r16. The minimum of the summation of capability on the number of CCs with Rel-15 PDCCH monitoring capability and the capability on the number of CCs with Rel-16 PDCCH monitoring capability is 3.

UE indicating support of pdcch-BlindDetectionCA-Mixed-NonAlignedSpan-v16a0 shall also indicate support of pdcch-BlindDetectionCA-Mixed-NonAlignedSpan-r16. Only one between pdcch-BlindDetectionCA-Mixed-r16 and pdcch-BlindDetectionCA-Mixed-NonAlignedSpan-r16 can be reported by UE.

| BC | No | N/A | N/A | +|

pdcch-BlindDetectionCA-Mixed-NonAlignedSpan-r18

Indicates the supported combination of the capability on the number of CCs for CCE/BD scaling with DL CA with mix of Rel. 16 and Rel. 15 PDCCH monitoring capabilities on different carriers with restriction for non-aligned span case.

In case of non-aligned span when the configured number of cells with Rel-16 PDCCH monitoring is larger than the UE reported value, PDCCH monitoring occasion(s) should be configured only on same symbol(s) every slot.

When a UE reports both pdcch-BlindDetectionCA-Mixed-NonAlignedSpan-r16 and this capability, the value reported in this capability is used if the configured span pattern of any serving cell satisfies pdcch-MonitoringSpan2-2-r18.

UE indicating support of this feature shall also indicate support of (7,3) or (4,3) span based PDCCH monitoring for pdcch-MonitoringMixed-r16 and (2,2) span based PDCCH monitoring for pdcch-MonitoringMixed-r18 with additional restriction(s).

| BC | No | N/A | N/A | +|

pdcch-BlindDetectionMCG-UE-r16, pdcch-BlindDetectionSCG-UE-r16

This field indicates the number of blind detections supported for MCG and SCG, respectively as specified in clause 10 in TS 38.213 [11] for the NR-DC. UE shall report the fields for MCG and for SCG together if supported.

If a UE supports pdcch-MonitoringCA-r16 or pdcch-MonitoringCA-NonAlignedSpan-r16, then the capability defined by pdcch-MonitoringCA-r16 or pdcch-MonitoringCA-NonAlignedSpan-r16 is applied to the feature as defined in clause 10 in TS 38.213 [11].

| BC | No | N/A | N/A | + +| | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|-----| +|

pdcch-BlindDetectionMCG-SCG-List-r17

Indicates the supported combinations of the capability on the number of CCs for monitoring a maximum number of BDs and non-overlapped CCEs for MCG and for SCG (i.e. pdcch-BlindDetectionMCG-UE-r17 and pdcch-BlindDetectionSCG-UE-r17) when configured for NR-DC operation with Rel-17 PDCCH monitoring capability on all the serving cells.

UE indicating support of this feature shall also indicate support of dl-FR2-2-SCS-480kHz-r17 or dl-FR2-2-SCS-960kHz-r17.

NOTE: If the UE reports pdcch-MonitoringCA-r17,

  • - Candidate values for pdcch-BlindDetectionMCG-UE-r17 is 1 to pdcch-MonitoringCA-r17-1
  • - Candidate values for pdcch-BlindDetectionSCG-UE-r17 is 1 pdcch-MonitoringCA-r17-1
  • - pdcch-BlindDetectionMCG-UE-r17 + pdcch-BlindDetectionSCG-UE-r17 >= pdcch-MonitoringCA-r17

Otherwise, the value of pdcch-BlindDetectionMCG-UE-r17 or of pdcchBlindDetectionSCG-UE-r17 is {1, 2, 3}

| BC | No | N/A | N/A | +|

pdcch-BlindDetectionMCG-SCG-List-r18

Indicates the supported combination of capability on the number of CCs for CCE/BD scaling for MCG and for SCG when configured for NR-DC operation with mix of Rel. 16 and Rel. 15 PDCCH monitoring capabilities on different carriers.

When a UE reports both pdcch-BlindDetectionCG-UE-MixedExt-r16 and this capability, the value reported in this capability is used if the configured span pattern of any serving cell satisfies pdcch-MonitoringSpan2-2-r18.

UE indicating support of this feature shall also indicate support of (7,3) or (4,3) span based PDCCH monitoring for pdcch-MonitoringMixed-r16 and (2,2) span based PDCCH monitoring for pdcch-MonitoringMixed-r18 with additional restriction(s).

| BC | No | N/A | N/A | +|

pdcch-BlindDetectionMCG-UE-Mixed-r16, pdcch-BlindDetectionSCG-UE-Mixed-r16, pdcch-BlindDetectionMCG-UE-Mixed-v16a0, pdcch-BlindDetectionSCG-UE-Mixed-v16a0

This field indicates mixed operation of two variants of the number of blind detections supported for MCG and SCG, respectively. UE shall report the fields for MCG and for SCG together if supported. UE indicating support of pdcch-BlindDetectionMCG-UE-Mixed-v16a0 and pdcch-BlindDetectionSCG-UE-Mixed-v16a0 shall also indicate support of pdcch-BlindDetectionMCG-UE-Mixed-r16 and pdcch-BlindDetectionSCG-UE-Mixed-r16.

If a UE supports pdcch-BlindDetectionCA-Mixed or pdcch-BlindDetectionCA-Mixed-NonAlignedSpan, then the capability defined by pdcch-BlindDetectionCA-Mixed or pdcch-BlindDetectionCA-Mixed-NonAlignedSpan is applied to the combination of pdcch-BlindDetectionMCG-UE-Mixed and pdcch-BlindDetectionSCG-UE-Mixed correspondingly as defined in clause 10 in TS 38.213 [11].

| BC | No | N/A | N/A | + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----------|------------|------------| +|

pdcch-BlindDetectionMixedList1-r17
Indicates the supported combinations of the number of carriers for CCE/BD scaling for MCG and for SCG when configured for NR-DC operation and/or with DL CA with mix of Rel. 15 and Rel. 17 PDCCH monitoring capabilities on different carriers.

UE indicating support of this feature shall also indicate support of dl-FR2-2-SCS-480kHz-r17 or dl-FR2-2-SCS-960kHz-r17.

NOTE 1: For DL CA combinations, the range of pdcch-BlindDetectionCA1-r17 (for Rel-15) + pdcch-BlindDetectionCA2-r17 (for Rel-17) is {4, ..., 16}.

NOTE 2: For NR-DC operation:
If the UE reports pdcch-BlindDetectionCA1-r17 (for Rel-15),

  • - Candidate values for pdcch-BlindDetectionMCG-UE1 (for Rel-15) are 0 to pdcch-BlindDetectionCA1-r17 (for Rel-15)
  • - Candidate values for pdcch-BlindDetectionSCG-UE1 (for Rel-15) are 0 to pdcch-BlindDetectionCA1-r17 (for Rel-15)
  • - pdcch-BlindDetectionMCG-UE1 (for Rel-15) + pdcch-BlindDetectionSCG-UE1 (for Rel-15) >= pdcch-BlindDetectionCA1-r17 (for Rel-15),

Otherwise,

  • - Candidate values for pdcch-BlindDetectionMCG-UE1 (for Rel-15) are {0, 1, 2, 3}
  • - Candidate values for pdcch-BlindDetectionSCG-UE1 (for Rel-15) are {0, 1, 2, 3}

If the UE reports pdcch-BlindDetectionCA2-r17 (for Rel-17),

  • - Candidate values for pdcch-BlindDetectionMCG-UE2 (for Rel-17) are 0 to pdcch-BlindDetectionCA2-r17 (for Rel-17)
  • - Candidate values for pdcch-BlindDetectionSCG-UE2 (for Rel-17) are 0 to pdcch-BlindDetectionCA2-r17 (for Rel-17)
  • - pdcch-BlindDetectionMCG-UE2 (for Rel-17) + pdcch-BlindDetectionSCG-UE2 (for Rel-17) >= pdcch-BlindDetectionCA2-r17 (for Rel-17),

Otherwise,

  • - Candidate values for pdcch-BlindDetectionMCG-UE2 (for Rel-17) are {0, 1, 2, 3}
  • - Candidate values for pdcch-BlindDetectionSCG-UE2 (for Rel-17) are {0, 1, 2, 3}
|

BC

|

No

|

N/A

|

N/A

| +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----------|------------|------------| + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----------|------------|------------| +|

pdcch-BlindDetectionMixedList2-r17
Indicates the supported combinations of the number of carriers for CCE/BD scaling for MCG and for SCG when configured for NR-DC operation and/or with DL CA with mix of Rel. 16 and Rel. 17 PDCCH monitoring capabilities on different carriers.

UE indicating support of this feature shall also indicate support of dl-FR2-2-SCS-480kHz-r17 or dl-FR2-2-SCS-960kHz-r17

NOTE 1: For DL CA combinations, the range of pdcch-BlindDetectionCA1-r17 (for Rel-16) + pdcch-BlindDetectionCA2-r17 (for Rel-17) is \{3, \dots, 16\}

NOTE 2: For NR-DC operation:
If the UE reports pdcch-BlindDetectionCA1-r17 (for Rel-16),

  • - Candidate values for pdcch-BlindDetectionMCG-UE1 (for Rel-16) are 0 to pdcch-BlindDetectionCA1-r17 (for Rel-16)
  • - Candidate values for pdcch-BlindDetectionSCG-UE1 (for Rel-16) are 0 to pdcch-BlindDetectionCA1-r17 (for Rel-16)
  • - pdcch-BlindDetectionMCG-UE1 (for Rel-16) + pdcch-BlindDetectionSCG-UE1 (for Rel-16) \ge pdcch-BlindDetectionCA1-r17 (for Rel-16),

Otherwise,

  • - Candidate values for pdcch-BlindDetectionMCG-UE1 (for Rel-16) are \{0, 1\}
  • - Candidate values for pdcch-BlindDetectionSCG-UE1 (for Rel-16) are \{0, 1\}

If the UE reports pdcch-BlindDetectionCA2-r17 (for Rel-17),

  • - Candidate values for pdcch-BlindDetectionMCG-UE2 (for Rel-17) are 0 to pdcch-BlindDetectionCA2-r17 (for Rel-17)
  • - Candidate values for pdcch-BlindDetectionSCG-UE2 (for Rel-17) are 0 to pdcch-BlindDetectionCA2-r17 (for Rel-17)
  • - pdcch-BlindDetectionMCG-UE2 (for Rel-17) + pdcch-BlindDetectionSCG-UE2 (for Rel-17) \ge pdcch-BlindDetectionCA2-r17 (for Rel-17),

Otherwise,

  • - Candidate values for pdcch-BlindDetectionMCG-UE2 (for Rel-17) are \{0, 1, 2\}
  • - Candidate values for pdcch-BlindDetectionSCG-UE2 (for Rel-17) are \{0, 1, 2\}
|

BC

|

No

|

N/A

|

N/A

| +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----------|------------|------------| + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|-----| +|

pdcch-BlindDetectionMixedList3-r17

Indicates the supported combinations of the number of carriers for CCE/BD scaling for MCG and for SCG when configured for NR-DC operation and/or with DL CA with mix of Rel. 15, Rel. 16 and Rel. 17 PDCCH monitoring capabilities on different carriers.

UE indicating support of this feature shall also indicate support of dl-FR2-2-SCS-480kHz-r17 or dl-FR2-2-SCS-960kHz-r17

NOTE 1: For DL CA combinations, the range of pdcch-BlindDetectionCA1-r17 (for Rel-15) plus pdcch-BlindDetectionCA2-r17 (for Rel-16) + pdcch-BlindDetectionCA3-r17 (for Rel-17) is {3, ..., 16}.

NOTE 2: For NR-DC operation:

If the UE reports pdcch-BlindDetectionCA1-r17 (for Rel-15),

  • - Candidate values for pdcch-BlindDetectionMCG-UE1 (for Rel-15) are 0 to pdcch-BlindDetectionCA1-r17 (for Rel-15)
  • - Candidate values for pdcch-BlindDetectionSCG-UE1 (for Rel-15) are 0 to pdcch-BlindDetectionCA1-r17 (for Rel-15)
  • - pdcch-BlindDetectionMCG-UE1 (for Rel-15) + pdcch-BlindDetectionSCG-UE1 (for Rel-15) >= pdcch-BlindDetectionCA1-r17 (for Rel-15),

Otherwise,

  • - Candidate values for pdcch-BlindDetectionMCG-UE1 (for Rel-15) are {0, 1}
  • - Candidate values for pdcch-BlindDetectionSCG-UE1 (for Rel-15) are {0, 1}

If the UE reports pdcch-BlindDetectionCA2-r17 (for Rel-16),

  • - Candidate values for pdcch-BlindDetectionMCG-UE2 (for Rel-16) are 0 to pdcch-BlindDetectionCA2-r17 (for Rel-16)
  • - Candidate values for pdcch-BlindDetectionSCG-UE2 (for Rel-16) are 0 to pdcch-BlindDetectionCA2-r17 (for Rel-16)
  • - pdcch-BlindDetectionMCG-UE2 (for Rel-16) + pdcch-BlindDetectionSCG-UE2 (for Rel-16) >= pdcch-BlindDetectionCA2-r17 (for Rel-16),

Otherwise,

  • - Candidate values for pdcch-BlindDetectionMCG-UE2 (for Rel-16) are {0, 1}
  • - Candidate values for pdcch-BlindDetectionSCG-UE2 (for Rel-16) are {0, 1}

If the UE reports pdcch-BlindDetectionCA3-r17 (for Rel-17),

  • - Candidate values for pdcch-BlindDetectionMCG-UE3 (for Rel-17) are 0 to pdcch-BlindDetectionCA3-r17 (for Rel-17)
  • - Candidate values for pdcch-BlindDetectionSCG-UE3 (for Rel-17) are 0 to pdcch-BlindDetectionCA3-r17 (for Rel-17)
  • - pdcch-BlindDetectionMCG-UE3 (for Rel-17) + pdcch-BlindDetectionSCG-UE3 (for Rel-17) >= pdcch-BlindDetectionCA3-r17 (for Rel-17),

Otherwise,

  • - Candidate values for pdcch-BlindDetectionMCG-UE3 (for Rel-17) are {0, 1}
  • - Candidate values for pdcch-BlindDetectionSCG-UE3 (for Rel-17) are {0, 1}
| BC | No | N/A | N/A | +|

pdcch-BlindDetectionNRDC-r18

Indicates the supported combinations of the number of CCs for monitoring a maximum number of BDs and non-overlapped CCEs per span for MCG and for SCG when configured for NR-DC operation with Rel-16 PDCCH monitoring on all the serving cells.

When a UE reports both pdcch-BlindDetectionMCG-UE-r16, pdcch-BlindDetectionSCG-UE-r16 and this capability, the value reported in this capability is used if the configured span pattern of any serving cell satisfies pdcch-MonitoringSpan2-2-r18.

UE indicating support of this feature shall also indicate support of (7,3) or (4,3) span based PDCCH monitoring for pdcch-Monitoring-r16 and (2,2) span based PDCCH monitoring for pdcch-MonitoringSpan2-2-r18 with additional restriction(s).

| BC | No | N/A | N/A | + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|-----| +|

pdcch-MonitoringCA-r16
Indicates the number of CCs for monitoring a maximum number of blind detections and non-overlapped CCEs per span when configured with DL CA with Rel-16 PDCCH monitoring capability on all the serving cells. This field also indicates supported span arrangement for CA. UE indicating support of this feature shall also indicate support of pdcch-Monitoring-r16. Only one between pdcch-MonitoringCA-r16 and pdcch-MonitoringCA-NonAlignedSpan-r16 can be reported by UE.

| BC | No | N/A | N/A | +|

pdcch-MonitoringCA-r17
Indicates the number of CCs for monitoring a maximum number of blind detections and non-overlapped CCEs per span when configured with DL CA with Rel-17 PDCCH monitoring capability on all the serving cells.

UE indicating support of this feature shall also indicate support of dl-FR2-2-SCS-480kHz-r17 or dl-FR2-2-SCS-960kHz-r17.

| BC | No | N/A | N/A | +|

pdcch-MonitoringCA-r18
Indicates whether the UE supports capability on the number of CCs for monitoring a maximum number of BDs and non-overlapped CCEs per span when configured with DL CA with Rel-16 PDCCH monitoring capability on all the serving cells. This capability signalling comprises the following parameters:

  • - maxNumberOfMonitoringCC-r18 indicates the number of CCs for monitoring a maximum number of BDs and non-overlapped CCEs per span when configured with DL CA with Rel-16 PDCCH monitoring capability on all the serving cells;
  • - supportedSpanArrangement-r18 indicates the supported span arrangement for CA. Value alignedOnly indicates the supported span arrangement for CA is aligned spans only, Value alignedAndNonAligned indicates the supported span arrangement for CA includes aligned spans and non-aligned spans.

A UE shall indicate the same value for the same position in all FeatureSetsPerBands in the indicated FeatureSetCombination.

When a UE reports both pdcch-MonitoringCA-r16 and this capability, the value reported in this capability is used if the configured span pattern of any serving cell satisfies pdcch-MonitoringSpan2-2-r18.

| BC | No | N/A | N/A | +|

pdcch-MonitoringCA-NonAlignedSpan-r16
Indicates the number of CCs for monitoring a maximum number of blind detections and non-overlapped CCEs per span when configured with DL CA with Rel-16 PDCCH monitoring capability on all the serving cells in the case UE supports aligned span and non-aligned span. In the case of non-aligned span, when the configured number of CCs with Rel-16 PDCCH monitoring is larger than the UE reported value and PDCCH monitoring occasion(s) should be configured only on same symbol(s) every slot. UE indicating support of this feature shall also indicate support of pdcch-Monitoring-r16. Only one between pdcch-MonitoringCA-r16 and pdcch-MonitoringCA-NonAlignedSpan-r16 can be reported by UE.

| BC | No | N/A | N/A | +|

pdcch-MonitoringCA-NonAlignedSpan-r18
Indicates whether the UE supports capability on the number of CCs for monitoring a maximum number of BDs and non-overlapped CCEs per span when configured with DL CA with pdcch-MonitoringAnyOccasionsWithSpanGap on all the serving cells with restriction for non-aligned span case. It also indicates whether the UE supports aligned span and non-aligned span. In case of non-aligned span when the configured number of cells with Rel-16 PDCCH monitoring capability is larger than the UE reported value, PDCCH monitoring occasion(s) should be configured only on same symbol(s) every slot. The UE supporting this feature shall also indicate support of pdcch-Monitoring-r16 for (7,3) or (4,3) span based PDCCH monitoring.

The UE supporting this feature shall also indicate support of pdcch-MonitoringSpan2-2-r18 for (2, 2) span based PDCCH monitoring with additional restriction(s).

A UE shall indicate the same value for the same position in all FeatureSetsPerBands in the indicated FeatureSetCombination.

When a UE reports both pdcch-MonitoringCA-NonAlignedSpan-r16 and capability, the value reported in this capability is used if the configured span pattern of any serving cell satisfies pdcch-MonitoringSpan2-2-r18.

| BC | No | N/A | N/A | + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|-----| +| prioSCellPRACH-OverSP-PeriodicSRS-Support-r17
Indicates whether the UE supports RRC configuration prioSCellPRACH-OverSP-PeriodicSRS as specified in TS 38.331 [9]. | BC | No | N/A | N/A | +| ptp-Retx-Multicast-r17
Indicates whether the UE supports PTP retransmission for multicast on the same cell as multicast initial transmission.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 . | BC | No | N/A | N/A | +| ptp-Retx-SPS-Multicast-r17
Indicates whether the UE supports PTP retransmission associated with CS-RNTI for SPS multicast on the cell same as multicast initial transmission.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 . | BC | No | N/A | N/A | +| pucch-ConfigForSPS-Multicast-r17
Indicates whether the UE supports SPS-PUCCH-AN-List for multicast HARQ-ACK feedback of all multicast SPS configuration(s), separate from that of SPS unicast configurations.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 . | BC | No | N/A | N/A | +| scellDormancyWithinActiveTime-r16
Indicates whether the UE supports SCell dormancy indication received on SPCell with DCI format 0_1/1_1 sent within the active time as defined in clause 10.3 of TS 38.213 [11]. If the UE indicates the support of this, the UE supports one dormant BWP and at least one non-dormant BWP per carrier. To support more than one non-dormant BWP in a carrier, the UE indicates support of upto4 in bwp-SameNumerology or upto4 in bwp-DiffNumerology . One dormant BWP and one non-dormant BWP are UE specific BWPs even for UEs not supporting bwp-SameNumerology . | BC | No | N/A | N/A | +| scellDormancyOutsideActiveTime-r16
Indicates whether the UE supports SCell dormancy indication received on SPCell using DCI format 2_6 sent outside the active time as defined in clause 10.3 of TS 38.213 [11]. A UE supporting this feature shall also indicate support of power saving DRX adaptation using drx-Adaptation-r16 and shall also support one dormant BWP and at least one non-dormant BWP per carrier. To support more than one non-dormant BWP in a carrier, the UE indicates support of upto4 in bwp-SameNumerology or upto4 in bwp-DiffNumerology . One dormant BWP and one non-dormant BWP are UE specific BWPs even for UEs not supporting bwp-SameNumerology . | BC | No | N/A | N/A | + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|-----|----------|-----| +|

semiStaticPUCCH-CellSwitchSingleGroup-r17

Indicates whether the UE supports semi-static PUCCH cell switching for a single PUCCH group only. The capability signalling comprises the following parameters:

  • - pucch-Group-r17 indicates for which PUCCH group the UE supports semi-static PUCCH cell switching using configured time-domain domain pattern of applicable PUCCH cell / carrier. Value primaryGroupOnly indicates that only primary PUCCH group can support PUCCH cell switch, value secondaryGroupOnly indicates that only secondary PUCCH group can support PUCCH cell switch, and value eitherPrimaryOrSecondaryGroup indicates that either primary or secondary PUCCH group can support PUCCH cell switch.
  • - pucch-Group-Config-r17 indicates one or multiple of supported carrier type pairs that can support PUCCH cell switch, with fr1-FR1-NonSharedTDD-r17 indicating the carrier type pair (FR1 licensed TDD, FR1 licensed TDD), fr2-FR2-NonSharedTDD-r17 indicating the carrier type pair (FR2 licensed TDD, FR2 licensed TDD), and fr1-FR2-NonSharedTDD-r17 indicating the carrier type pair (FR1 licensed TDD, FR2 licensed TDD).

NOTE: This feature applies to cells in the same TAG only. If UE supporting this FG also supports both diffNumerologyWithinPUCCH-GroupSmallerSCS and diffNumerologyWithinPUCCH-GroupLargerSCS or both diffNumerologyWithinPUCCH-GroupSmallerSCS-CarrierTypes-r16 and diffNumerologyWithinPUCCH-GroupLargerSCS-CarrierTypes-r16 or maxUpTo3Diff-NumerologiesConfigSinglePUCCH-grp-r16 or maxUpTo4Diff-NumerologiesConfigSinglePUCCH-grp-r16 when UE is not configured with two NR PUCCH groups, the UE supports the cases of both same and different numerologies between switchable cells. Otherwise, the UE supports the case of same numerology between switchable cells.

| BC | No | TDD only | N/A | +|

semiStaticPUCCH-CellSwitchTwoGroups-r17

Indicates whether the UE supports semi-static PUCCH cell switching for two PUCCH groups using configured time-domain domain pattern of applicable PUCCH cell / carrier. The capability indicates one or multiple of supported configuration(s) of {primary PUCCH group config, secondary PUCCH group config}. The capability signalling of each primary or secondary PUCCH group configuration indicates one or multiple of carrier type pairs that can support PUCCH cell switch, with fr1-FR1-NonSharedTDD-r17 indicating the carrier type pair (FR1 licensed TDD, FR1 licensed TDD), fr2-FR2-NonSharedTDD-r17 indicating the carrier type pair (FR2 licensed TDD, FR2 licensed TDD), and fr1-FR2-NonSharedTDD-r17 indicating the carrier type pair (FR1 licensed TDD, FR2 licensed TDD).

NOTE: This feature applies to cells in the same TAG only. If UE supporting this FG also supports both diffNumerologyWithinPUCCH-GroupSmallerSCS and diffNumerologyWithinPUCCH-GroupLargerSCS or both diffNumerologyWithinPUCCH-GroupSmallerSCS-CarrierTypes-r16 and diffNumerologyWithinPUCCH-GroupLargerSCS-CarrierTypes-r16, the UE supports the cases of both same and different numerologies between switchable cells. Otherwise, the UE supports the case of same numerology between switchable cells.

| BC | No | TDD only | N/A | +|

simultaneousCSI-ReportsAllCC

Indicates whether the UE supports CSI report framework and the number of CSI report(s) which the UE can simultaneously process across all CCs, and across MCG and SCG in case of NR-DC. The CSI report comprises periodic, semi-persistent and aperiodic CSI and any latency classes and codebook types. The CSI report in simultaneousCSI-ReportsAllCC includes the beam report and CSI report. This parameter may further limit simultaneousCSI-ReportsPerCC in MIMO-ParametersPerBand and Phy-ParametersFRX-Diff for each band in a given band combination.

| BC | Yes | N/A | N/A | + +| | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|-----| +|

simul-SRS-Trans-BC-r16
Indicates the number of SRS resources for positioning on a symbol for a given band combination. The UE can include this field only if the UE supports srs-PosResources-r16. Otherwise, the UE does not include this field;

NOTE 1: For single-band band combinations, it defines the capability for intra-band CA, and for band combinations with at least two bands, it defines the capability for inter-band carrier aggregation.

NOTE 2: if the UE does not indicate this capability for a band combination, the UE does not support the feature in this band combination.

| BC | No | N/A | N/A | +|

simul-SRS-MIMO-Trans-BC-r16
Indicates the number of SRS resources for positioning and SRS resource for MIMO on a symbol for a given BC. The UE can include this field only if the UE supports srs-PosResources-r16. Otherwise, the UE does not include this field.

NOTE 1: If UE reports 2 for the candidate value, it means both the number of SRS resource for positioning and SRS resource for MIMO equals to 1.

NOTE 2: For single-band band combinations, it defines the capability for intra-band carrier aggregation, and for band combinations with at least two bands, it defines the capability for inter-band carrier aggregation.

NOTE 3: if the UE does not indicate this capability for a band combination, the UE does not support the feature in this band combination.

| BC | No | N/A | N/A | +|

simulTX-SRS-AntSwitchingInterBandUL-CA-r16
Indicates whether the UE support simultaneous transmission of SRS on different CCs for inter-band UL CA. The UE indicating support of this feature shall include at least one of the following capabilities:

  • - supportSRS-xTyR-xLessThanY-r16 indicates support transmission of SRS for xTyR (x<y) based antenna switching and SRS for CB/NCB/BM on different CCs in overlapped symbol(s) for inter-band UL CA.
  • - supportSRS-xTyR-xEqualToY-r16 indicates support transmission of SRS for xTyR (x=y) based antenna switching and SRS for CB/NCB/BM on different CCs in overlapped symbol(s) for inter-band UL CA.
  • - supportSRS-AntennaSwitching-r16 Indicates whether the UE support simultaneous transmission of SRS for antenna switching on different CCs in overlapped symbol(s) for inter-band UL CA.

NOTE: For simultaneously antenna switching and antenna switching SRS in inter-band CAs with bands whose UL are switched together according to the reported supportSRS-AntennaSwitching-r16, the UE expects the same configuration of xTyR across the different CCs and the SRS resources overlapped in time domain from UE perspective are from the same UE antenna ports.

| BC | No | N/A | N/A | +|

simultaneousRxTxInterBandCA
Indicates whether the UE supports simultaneous transmission and reception in TDD-TDD and TDD-FDD inter-band NR CA. If this field is included in ca-ParametersNR-ForDC, it indicates the UE supports simultaneous transmission and reception between any UL/DL band pair within a cell group and across MCG and SCG in TDD-TDD and TDD-FDD inter-band NR-DC. It is mandatory for certain TDD-FDD and TDD-TDD band combinations defined in TS 38.101-1 [2], TS 38.101-2 [3] and TS 38.101-3 [4].

This capability does not apply to the following components within TDD-TDD and TDD-FDD inter-band NR-CA or NR-DC combinations:

  • - Intra-band NR-CA or NR-DC component
  • - Inter-band NR-CA or NR-DC component where the frequency range of one TDD band is a subset of the frequency range of the other NR TDD band (as specified in TS 38.101-1 [2]).
| BC | CY | N/A | N/A | + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|-----| +|

simultaneousRxBTxInterBandCAPerBandPair

Indicates whether the UE supports simultaneous transmission and reception in TDD-TDD and TDD-FDD inter-band NR CA for each band pair in the band combination.

Encoded as a bitmap with size L * (L - 1) / 2, and bit N (leftmost bit is indexed as bit 0) is set to "1" if the UE supports simultaneous transmission and reception for band pair (x, y), where L is the number of band entries in the band combination, x and y are the indices of the band entry in the band combination (the first band entry is indexed as 0), x < y, and N = x * (2 * L - x - 1) / 2 + y - x - 1.

If this field is included in ca-ParametersNR-ForDC, each bit of this field indicates whether the UE supports simultaneous transmission and reception between each band pair, within a cell group and across MCG and SCG in TDD-TDD and TDD-FDD inter-band NR-DC.

The UE does not include this field if the UE supports simultaneous transmission and reception for all applicable band pairs in the band combination (in which case simultaneousRxBTxInterBandCA is included) or does not support for any band pair in the band combination. It is mandatory for certain band pairs as specified in TS 38.101-1 [2], TS 38.101-2 [3] and TS 38.101-3 [4]. The UE shall consistently set the bits which correspond to the same band pair.

| BC | CY | N/A | N/A | +|

simultaneousRxBTxSUL

Indicates whether the UE supports simultaneous reception and transmission for a NR band combination including SUL. Mandatory/Optional support depends on band combination and captured in TS 38.101-1 [2].

| BC | CY | N/A | N/A | +|

simultaneousRxBTxSULPerBandPair

Indicates whether the UE supports simultaneous reception and transmission for a NR band combination including SUL for each band pair in the band combination.

Encoded in the same manner as simultaneousRxBTxInterBandCAPerBandPair.

The UE does not include this field if the UE supports simultaneous transmission and reception for all applicable band pairs in the band combination (in which case simultaneousRxBTxSUL is included) or does not support for any band pair in the band combination. It is mandatory for certain band pairs as specified in TS 38.101-1 [2]. The UE shall consistently set the bits which correspond to the same band pair.

| BC | CY | N/A | N/A | +|

simultaneousSRS-AssocCSI-RS-AllCC

Indicates support of CSI-RS processing framework for SRS and the number of SRS resources that the UE can process simultaneously across all CCs, and across MCG and SCG in case of NR-DC, including periodic, aperiodic and semi-persistent SRS. This parameter may further limit simultaneousSRS-AssocCSI-RS-PerCC in MIMO-ParametersPerBand and Phy-ParametersFRX-Diff for each band in a given band combination.

| BC | No | N/A | N/A | +|

singlePUCCH-ConfigForMulticast-r17

Indicates whether the UE supports a PUCCH-Config for multicast HARQ-ACK feedback, separate from that of unicast configurations.

A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 or nack-OnlyFeedbackForMulticast-r17.

NOTE: With ack-NACK-FeedbackForMulticast-r17 or nack-OnlyFeedbackForMulticast-r17 as prerequisite, this feature includes the case of ACK/NACK for multicast or NACK-only mode1 for multicast.

| BC | No | N/A | N/A | +|

stayOnTargetCC-SRS-CarrierSwitch-r17

Indicates whether the UE supports staying on the target CC when remaining SRS resource set(s) for SRS carrier switching exists. UE indicating support of this feature shall indicate support of srs-CarrierSwitch.

NOTE 1: When UE supports this capability, if the time period between the SRS resource sets is smaller than the total required RF switching time to the source CC and back to the target CC and a higher priority UL transmission and/or DL reception is not scheduled on the source CC in the time period between the two SRS resources sets, the UE stays in the target CC in the period between the SRS resource sets; otherwise, the UE switches back to the source CC after transmitting each SRS resource set.

NOTE 2: If the UE does not indicate this capability, the UE switches back to source CC between the SRS resource sets.

| BC | No | N/A | N/A | + +| | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|-----| +|

supportedCSI-RS-ResourceListAlt-r16
Indicates the list of supported CSI-RS resources across all bands in a band combination by referring to codebookVariantsList. The following parameters are included in codebookVariantsList for each code book type:

  • - maxNumberTxPortsPerResource indicates the maximum number of Tx ports in a resource across all bands within a band combination;
  • - maxNumberResourcesPerBand indicates the maximum number of resources across all CCs within a band combination, simultaneously;
  • - totalNumberTxPortsPerBand indicates the total number of Tx ports across all CCs within a band combination, simultaneously.

For each band in a band combination, supported values for these three parameters are determined in conjunction with supportedCSI-RS-ResourceListAlt reported in MIMO-ParametersPerBand.

| BC | No | N/A | N/A | +|

supportedNumberTAG
Defines the number of timing advance groups supported by the UE. It is applied to NR CA, NR-DC, (NG)EN-DC/NE-DC and DAPS handover. For (NG)EN-DC/NE-DC, it indicates number of TAGs only for NR CG. The number of TAGs for the LTE MCG is signalled by existing LTE TAG capability signalling. For NR CA/NR-DC band combination, if the band combination comprised of more than one band entry (i.e., inter-band or intra-band non-contiguous band combination), it indicates that different timing advances on different band entries are supported. If absent, the UE supports only one TAG for the NR part. It is mandatory for the UE to support more than one TAG for NR-DC and it is mandatory for the UE to support 2 TAGs for inter-frequency DAPS. For the mixed inter-band and intra-band NR CA/NR-DC band combination, if the network configures more non-contiguous UL serving cells than the number of supported TAG, the UE only supports the configuration where all UL CCs of the same frequency band are configured with the same Timing Advance Group ID.

| BC | CY | N/A | N/A | +|

twoPUCCH-Grp-ConfigurationsList-r16
Indicates one or multiple of supported configuration(s) of {primary PUCCH group config, secondary PUCCH group config} for the band combination where for each of the supported configuration the carrier type(s) (FR1-NonSharedTDD, FR1-SharedTDD, FR1-NonSharedFDD, FR2) that can be mapped to a PUCCH group and also the carrier types that can be configured with PUCCH transmission for primary PUCCH group and secondary PUCCH group for NR-CA band combination with 3 or more bands. The capability signalling of each primary or secondary PUCCH group configuration comprises of the following parameters:

  • - pucch-GroupMapping-r16 indicates the PUCCH group(s) that a carrier type can be mapped to.
  • - pucch-TX-r16 indicates the PUCCH group(s) that a carrier type can be configured for PUCCH transmission

NOTE 1: For a band combination with SUL, the SUL band is counted as one of the bands.
NOTE 2: For a band combination with SDL, the SDL band is counted as one of the bands. SDL is indicated as 'FR1-NonSharedFDD' carrier type. Per UE capabilities that are TDD only are not applicable to SDL.
NOTE 3: When the carrier type of NUL is indicated for PUCCH transmission location, the SUL in the same cell as in the NUL can also be configured for PUCCH transmission.
NOTE 4: When the carrier type of NUL is indicated for one PUCCH group config, the SUL in the same cell as in the NUL can also be configured for the PUCCH group.
NOTE 5: If UE indicating this field does not support diffNumerologyAcrossPUCCH-Group-CarrierTypes-r16, the UE can only be configured with the same SCS across NR PUCCH groups.

| BC | No | N/A | N/A | +|

uplinkTxDC-TwoCarrierReport-r16
Indicates whether the UE supports the uplink Tx Direct Current subcarrier location(s) reporting when configured with uplink CA with two carriers. It is applicable only for (NG)EN-DC/NE-DC and NR CA where the NR has intra-band uplink CA with two uplink carriers.

| BC | No | N/A | N/A | + +#### 4.2.7.5 *FeatureSetDownlink* parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----|--------------|--------------| +| additionalDMRS-DL-Alt
Indicates whether the UE supports the alternative additional DMRS position for co-existence with LTE CRS. It is applied to 15kHz SCS and one additional DMRS case only. | FS | No | N/A | FR1 only | +| bwpOperationMeasWithInterrupt-r18
Indicates whether the UE supports RLM/BM/BFD measurements based on CD-SSB outside active BWP with interruptions, where the CD-SSB is outside active DL BWP but is within the bandwidth of the corresponding carrier(s) to be measured. Bandwidth of UE-specific RRC configured BWP may not include bandwidth of the CORESET#0 (if CORESET#0 is present) and CD-SSB for PCell/PSCell (if configured) and bandwidth of the UE-specific RRC configured BWP may not include CD-SSB for SCell. CD-SSB outside active DL BWP but within the bandwidth of the corresponding carrier(s) to be measured can be used as the QCL source for other reference signal.

NOTE1: This feature only applies if there is no CSI-RS, no NCD- SSB, and no CD-SSB configured for RLM/BM/BFD in the active BWP of the corresponding carrier(s) to be measured.
NOTE2: The CD-SSB is still within the bandwidth of the carrier configured by SCS-SpecificCarrier of downlinkChannelBW-PerSCS-List in ServingCellConfig
NOTE3: If a UE is configured with more than one UE-specific DL BWP configurations, the CD-SSB is within the bandwidth of at least one of the UE-specific DL BWP configurations.
NOTE4: UE shall not indicate support of both bwpOperationMeasWithoutInterrupt-r18 and bwpOperationMeasWithInterrupt-r18 for the same band in the same reported band combination.

A UE supporting this feature shall also indicate support of ncd-SSB-BWP-Wor-r18 . This capability is not applicable to RedCap or eRedCap UEs. | FS | No | N/A | N/A | +| bwpOperationMeasWithoutInterrupt-r18
Indicates whether the UE supports RLM/BM/BFD and gapless L3 intra-frequency measurements based on CD-SSB outside active BWP without interruptions. Bandwidth of UE-specific RRC configured BWP may not include bandwidth of the CORESET#0 (if CORESET#0 is present) and CD-SSB for PCell/PSCell (if configured) and bandwidth of the UE-specific RRC configured BWP may not include CD-SSB for SCell. CD-SSB outside active DL BWP but within the bandwidth of the corresponding carrier(s) to be measured can be used as the QCL source for other reference signal. UE performs L3 intra-frequency measurements without gaps based on CD-SSB, where the CD-SSB is outside the active DL BWP but is within the bandwidth of the corresponding carrier(s) to be measured.

NOTE1: The CD-SSB is still within the bandwidth of the carrier configured by SCS-SpecificCarrier of downlinkChannelBW-PerSCS-List in ServingCellConfig.
NOTE2: If a UE is configured with more than one UE-specific DL BWP configurations, the CD-SSB is within the bandwidth of at least one of the UE-specific DL BWP configurations.
NOTE3: UE shall not indicate support of both bwpOperationMeasWithoutInterrupt-r18 and bwpOperationMeasWithInterrupt-r18 for the same band in the same reported band combination.
NOTE4: If a UE additionally indicates support of NeedForGap or NeedForGapNCSG and/or NeedForInterruption , the UE shall report no gap and no interruption/no NCSG for intra-frequency measurement.

This capability is not applicable to RedCap or eRedCap UEs. | FS | No | N/A | N/A | +| cbgPDSCH-ProcessingType1-DifferentTB-PerSlot-r16
Defines whether the UE capable of processing time capability 1 supports CBG based reception with one or with up to two or with up to four or with up to seven unicast PDSCHs per slot per CC. | FS | No | N/A | N/A | +| cbgPDSCH-ProcessingType2-DifferentTB-PerSlot-r16
Defines whether the UE capable of processing time capability 2 supports CBG based reception with one or with up to two or with up to four or with up to seven unicast PDSCHs per slot per CC. | FS | No | N/A | N/A | + +| | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|-----|-----|----------| +| crossCarrierSchedulingProcessing-DiffSCS-r16
Indicates the UE cross carrier scheduling processing capability for DL carrier aggregation processing up to X unicast DCI scheduling for DL per scheduled CC. X is based on pair of (scheduling CC SCS, scheduled CC SCS) where a pair of (15,120), (15,60), (30,120) kHz SCS can have X = {1,2,4} while a pair of (15,30), (30,60), (60,120) kHz SCS can have X = {2}, and X applies per slot of scheduling CC. | FS | No | N/A | N/A | +| csi-RS-MeasSCellWithoutSSB
Defines whether the UE can perform CSI-RSRP and CSI-RSRQ measurement as specified in TS 38.215 [13], where CSI-RS resource is configured for a cell that does not transmit SS/PBCH block. A UE that supports this feature shall also support scellWithoutSSB. | FS | No | N/A | N/A | +| dl-MCS-TableAlt-DynamicIndication
Indicates whether the UE supports dynamic indication of MCS table for PDSCH. | FS | No | N/A | N/A | +| dmrs-MultiTRP-AddtionRows-r18
Indicates whether the UE supports additional row(s) for antenna ports (0,2,3) for DMRS ports for single-DCI based M-TRP.
A UE supporting this feature shall also indicate support of FG40-4-5. | FS | No | N/A | N/A | +| dynamicMulticastPCell-r17
Indicates whether the UE supports dynamic scheduling for multicast for PCell comprised of the following functional components:
  • - Supports group-common PDCCH/PDSCH for multicast with CRC scrambled by G-RNTI for PCell;
  • - Supports CFR configuration for multicast;
  • - Supports CORESET and common search space configuration for multicast;
  • - Supports DCI format 4_1 with CRC scrambled with G-RNTI for multicast;
  • - Supports inter-slot TDM between group-common PDSCH for multicast and other PDSCHs in different slots;
  • - Supports {2, 4, 8} times semi-static slot-level repetition for group-common PDSCH for multicast;
  • - Supports long DRX cycle for MBS multicast reception as specified in TS 38.321 [8].
NOTE: One G-RNTI per UE is supported for multicast reception. | FS | No | N/A | N/A | +| featureSetListPerDownlinkCC
Indicates which features the UE supports on the individual DL carriers of the feature set (and hence of a band entry that refer to the feature set) by FeatureSetDownlinkPerCC-Id . The order of the elements in this list is not relevant, i.e., the network may configure any of the carriers in accordance with any of the FeatureSetDownlinkPerCC-Id in this list. A fallback per CC feature set resulting from the reported feature set per DL CC is not signalled but the UE shall support it. | FS | N/A | N/A | N/A | +| intraBandFreqSeparationDL, intraBandFreqSeparationDL-v1620
Indicates DL frequency separation class the UE supports, which indicates a maximum frequency separation between lower edge of lowest CC and upper edge of highest CC in a frequency band, for intra-band non-contiguous CA. The UE sets the same value in the FeatureSetDownlink of each band entry within a band. The values mhzX correspond to the values XMHz defined in TS 38.101-2 [3]. It is mandatory to report for UE which supports DL intra-band non-contiguous CA in FR2.
If the UE sets the field intraBandFreqSeparationDL-v1620 it shall set intraBandFreqSeparationDL (without suffix) to the nearest smaller value. | FS | CY | N/A | FR2 only | +| intraBandFreqSeparationDL-Only-r16
Indicates whether the UE supports frequency separation class of DL only extension. If present, the field extends the maximum frequency separation between the lower edge of lowest CC and the upper edge of highest CC in a frequency band that the UE supports according to intraBandFreqSeparationDL . The frequency range extension is either above or below the frequency range indicated by intraBandFreqSeparationDL and extends it in contiguous manner with no frequency gap, and the network may configure contiguous or non-contiguous downlink serving cells in that extended range. The UE sets the same value in the FeatureSetDownlink of each band entry within a band. The values mhzX correspond to the values XMHz defined in TS 38.101-2 [3]. The sum of intraBandFreqSeparationDL and intraBandFreqSeparationDL-Only shall not exceed 2400 MHz. If the UE sets this field, the sum of intraBandFreqSeparationDL and intraBandFreqSeparationDL-Only shall be larger than 1400 MHz.

A UE supporting this feature shall also support intraBandFreqSeparationDL . | FS | No | N/A | FR2 only | + +| | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|-----| +|

intraFreqDAPS-r16
Indicates whether UE supports intra-frequency DAPS handover, e.g. support of simultaneous DL reception of PDCCH and PDSCH from source and target cell. A UE indicating this capability shall also support intra-frequency synchronous DAPS handover, single UL transmission and cancelling UL transmission to the source cell for intra-frequency DAPS handover. The capability signalling comprises of the following parameters:

  • - intraFreqAsyncDAPS-r16 indicates whether the UE supports asynchronous DAPS handover.
  • - intraFreqDiffSCS-DAPS-r16 indicates whether the UE supports different SCSs in source PCell and intra-frequency target PCell in DAPS handover. The UE only includes this field if different SCSs can be supported in both UL and DL. If absent, the UE does not support either UL or DL SCS being different in DAPS handover.
| FS | No | N/A | N/A | +|

mappingTypeA-1SymbolFL-DMRS-Addition2Symbol-r18
Indicates whether the UE supports Support 1 symbol FL DMRS and 2 additional DMRS symbols for at least one port for mapping type A.
A UE supporting this feature shall also indicate support of FG40-4-1.

| FS | No | N/A | N/A | +|

maxNumberTRS-ResourceSet-r18
Indicates the maximum number of TRS resource sets in a single CSI-RS resource setting.
A UE supporting this feature shall also indicate support of FG40-3-3-1.

| FS | No | N/A | N/A | +|

mTRP-PDCCH-Repetition-r17
Indicates the support of intra-slot PDCCH repetition based on two linked SS sets associated with corresponding CORESETs.
This feature also includes following parameters:

  • - numBD-twoPDCCH-r17 indicates the number of BDs for the two PDCCH candidates.
  • - maxNumOverlaps-r17 indicates the maximum number of overlaps when one of the linked PDCCH candidates uses the same set of CCEs as an individual (unlinked) PDCCH candidate per scheduled component carrier per slot.

NOTE 1: UE supports PDCCH repetition for the following (basic) PDCCH monitoring capability: For type 1 CSS with dedicated RRC configuration, type 3 CSS, and UE-SS, the monitoring occasion is within the first 3 OFDM symbols of a slot.
NOTE 2: For maxNumOverlaps-r17, each unique pair of overlaps is counted as one.
NOTE 3: This feature does not include supporting two QCL-TypeD in time-domain overlapping CORESETs in FR2.

| FS | No | N/A | N/A | +|

mTRP-PDCCH-Case2-1SpanGap-r17
Indicates the support of PDCCH repetition for PDCCH monitoring of any occasions with span gap as defined in pdcch-MonitoringAnyOccasionsWithSpanGap for each SCS with the following parameters:

  • - supportedMode-r17 indicates supported mode of PDCCH repetition.
  • - limitX-PerCC-r17: limit (X) per CC.
  • - limitX-AcrossCC-r17: limit (X) per across all CCs.

The limit (X) is the total number of linked candidates of which the first candidate is received and the second one has not been received at any given span, where "received" and "not been received" is with respect to the end of the corresponding span of PDCCH candidate. It is indicated as a total count assuming count 1 for AL=1; 2 for AL=2; 4 for AL=4 or 8 or 16.
The UE indicates limitX-PerCC-r17 and limitX-AcrossCC-r17 if supportedMode-r17 is set to inter-span or both. A candidate value "nolimit" does not imply BD limit can be exceeded.
The UE indicating support of this feature shall also indicate support of pdcch-MonitoringAnyOccasionsWithSpanGap and mTRP-PDCCH-Repetition-r17.

| FS | No | N/A | N/A | + +| | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|-----|-----|-----| +|

mTRP-PDCCH-legacyMonitoring-r17
Indicates the support of PDCCH repetition with Rel-16 PDCCH monitoring capability as defined in pdcch-Monitoring-r16 for 15kHz and 30kHz SCS with the following parameters:

  • - supportedMode-r17 indicates the supported mode of PDCCH repetition.
  • - limitX-PerCC-r17 indicates the limit (X) per CC.
  • - limitX-AcrossCC-r17 indicates the limit (X) per across all CCs.

The limit (X) is the total number of linked candidates of which the first candidate is received and the second one has not been received at any given span, where "received" and "not been received" is with respect to the end of the corresponding span of PDCCH candidate. It is indicated as a total count assuming count 1 for AL=1; 2 for AL=2; 4 for AL=4 or 8 or 16. The UE indicates limitX-PerCC-r17 and limitX-AcrossCC-r17 if supportedMode-r17 is set to inter-span or both. A candidate value "nolimit" does not imply BD limit can be exceeded. The UE indicating support of this feature shall also indicate support of pdcch-Monitoring-r16 and mTRP-PDCCH-Repetition-r17.

| FS | No | N/A | N/A | +|

mTRP-PDCCH-multiDCI-multiTRP-r17
Indicates the support of simultaneous configuration of PDCCH repetition and multi-DCI based multi-TRP. Two linked PDCCH candidates are not expected to be associated with different CORESETPoolIndex values

The UE indicating support of this feature shall also indicate support of multiDCI-MultiTRP-r16 and mTRP-PDCCH-Repetition-r17.

| FS | No | N/A | N/A | +|

multicastInactive-r18
Indicates whether the UE supports multicast reception in RRC_INACTIVE as specified in TS 38.331 [9], comprised of the following functional components:

  • - Supports group-common PDCCH/PDSCH for multicast with CRC scrambled by Multicast MCCH-RNTI;
  • - Supports group-common PDCCH/PDSCH for multicast with CRC scrambled by G-RNTI;
  • - Supports DCI format 4_0 with CRC scrambled with Multicast MCCH-RNTI for multicast MCCH;
  • - Supports DCI format 4_1 with CRC scrambled with G-RNTI for multicast MTCH;
  • - Supports multicast MCCH change notification indication via DCI;
  • - Supports CFR configuration for multicast;
  • - Supports CORESET and common search space configuration for multicast;
  • - Supports one G-RNTI for multicast reception;
  • - Supports RRC configured slot-level repetition up to 8 for multicast MTCH;
  • - Supports inter-slot TDM between group-common PDSCH for multicast MCCH and group-common PDSCH for multicast MTCH, or among group-common PDSCH for multicast MCCH, group-common PDSCH for multicast MTCH and other PDSCHs in different slots;
  • - Supports up to 64QAM for FR1/FR2;
  • - Supports 12-bit length of PDCP sequence number;
  • - Supports ROHC profiles 0x0000, 0x0001 and 0x0002;
  • - Supports 4 ROHC header compression context sessions;
  • - Supports UM MRB with 12-bit length of RLC sequence number;
  • - Supports UM MRB with 6-bit length of RLC sequence number;
  • - Supports long DRX cycle for MBS multicast reception as specified in TS 38.321 [8].

A UE supporting this feature shall also indicate support of dynamicMulticastPCell-r17.

| FS | No | N/A | N/A | +|

oneFL-DMRS-ThreeAdditionalDMRS-DL
Defines whether the UE supports DM-RS pattern for DL transmission with 1 symbol front-loaded DM-RS with three additional DM-RS symbols.

| FS | No | N/A | N/A | +|

oneFL-DMRS-TwoAdditionalDMRS-DL
Defines support of DM-RS pattern for DL transmission with 1 symbol front-loaded DM-RS with 2 additional DM-RS symbols and more than 1 antenna ports.

| FS | Yes | N/A | N/A | + +| | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|-----| +| pdcch-Monitoring-r16
Indicates whether the UE supports PDCCH search space monitoring occasions in any symbol of the slot with minimum time separation between two consecutive transmissions of PDCCH with span up to two OFDM symbols for two OFDM symbols or span up to three OFDM symbols for four and seven OFDM symbols. The different value can be reported for PDSCH processing type 1 and PDSCH processing type 2, respectively. For each sub-carrier spacing, the leading / leftmost bit (bit 0) corresponds to the supported value set (X,Y) of (7,3). The next bit (bit 1) corresponds to the supported value set (X,Y) of (4,3). The rightmost bit (bit 2) corresponds to the supported value set (X,Y) of (2,2). | FS | No | N/A | N/A | +| pdcch-MonitoringAnyOccasions
Defines the supported PDCCH search space monitoring occasions. withoutDCI-gap indicates whether the UE supports PDCCH search space monitoring occasions in any symbol of the slot for Type 1-PDCCH common search space configured by dedicated RRC signalling, for a Type 3-PDCCH common search space, or for a UE-specific search space with the capability of supporting at least 44, 36, 22, and 20 blind decodes in a slot for 15 kHz, 30 kHz, 60kHz, and 120 kHz subcarrier spacing values respectively. withDCI-gap indicates whether the UE supports PDCCH search space monitoring occasions in any symbol of the slot with minimum time separation of two OFDM symbols for 15 kHz, four OFDM symbols for 30 kHz, seven OFDM symbols for 60 kHz with NCP, and 14OFDM symbols for 120kHz between two consecutive transmissions of PDCCH scrambled with C-RNTI, MCS-C-RNTI, or CS-RNTI for Type 1-PDCCH common search space configured by dedicated RRC signalling, for a Type 3-PDCCH common search space, or for a UE-specific search space, with the capability of supporting at least 44, 36, 22, and 20 blind decodes in a slot for 15 kHz, 30 kHz, 60kHz, and 120 kHz subcarrier spacing values respectively. | FS | No | N/A | N/A | +| pdcch-MonitoringAnyOccasionsWithSpanGap
Indicates whether the UE supports PDCCH search space monitoring occasions in any symbol of the slot with minimum time separation between two consecutive transmissions of PDCCH with span up to two OFDM symbols for two OFDM symbols or span up to three OFDM symbols for four and seven OFDM symbols. Value set1 indicates the supported value set (X,Y) is (7,3), value set2 indicates the supported value set (X,Y) is (4,3) and (7,3) and value set 3 indicates the supported value set (X,Y) is (2,2), (4,3) and (7,3). | FS | No | N/A | N/A | +| pdcch-MonitoringMixed-r16
Indicates support of Rel-15 monitoring capability and pdcch-Monitoring-r16 on different serving cells. | FS | No | N/A | N/A | +| pdcch-MonitoringMixed-r18
Indicates whether the UE support Rel-15 monitoring capability and pdcch-Monitoring-r16 monitoring capability on different serving cells.

The UE supporting this feature shall also indicate support of pdcch-Monitoring-r16 for (7,3) or (4,3) span based PDCCH monitoring.

The UE supporting this feature shall also indicate support of pdcch-MonitoringSpan2-2-r18 for (2, 2) span based PDCCH monitoring with additional restriction(s).

When a UE reports both pdcch-MonitoringMixed-r16 and this capability, the value reported in this capability is used if the configured span pattern of any serving cell satisfies pdcch-MonitoringSpan2-2-r18 . | FS | No | N/A | N/A | +| pdcch-MonitoringSpan2-2-r18
Indicates support of (2, 2) span-based PDCCH monitoring with the additional restriction that there is at least one OFDM symbol gap between two PDCCH monitoring occasions.
When a UE reports both pdcch-Monitoring-r16 and this capability, the union of supported span patterns in pdcch-Monitoring-r16 and this capability establishes the multiple combinations (X,Y) used to determine per-span BD/CCE limit as described in Clause 10 of TS 38.213 [11]. | FS | No | N/A | N/A | +| pdsch-1PortDL-PTTRS-r18
Indicates whether the UE supports 1 port DL PTRS for enhanced DMRS ports for PDSCH with rank 1-8.
A UE supporting this feature shall also indicate support of FG40-4-1. | FS | No | N/A | N/A | +| pdsch-1SymbolFL-DMRS-Addition2Symbol-r18
Indicates whether the UE supports 1 symbol FL DMRS and 2 additional DMRS symbols for more than one port for enhanced DMRS ports for PDSCH.
A UE supporting this feature shall also indicate support of FG40-4-1. | FS | No | N/A | N/A | + +| | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|----------| +| pdsch-1SymbolFL-DMRS-Addition3Symbol-r18
Indicates whether the UE supports 1 symbol FL DMRS and 3 additional DMRS symbols for enhanced DMRS ports for PDSCH.
A UE supporting this feature shall also indicate support of FG40-4-1. | FS | No | N/A | N/A | +| pdsch-2SymbolFL-DMRS-r18
Indicates whether the UE supports 2 symbols FL-DMRS for enhanced DMRS ports for PDSCH.
A UE supporting this feature shall also indicate support of FG40-4-1. | FS | No | N/A | N/A | +| pdsch-2SymbolFL-DMRS-Addition2Symbol-r18
Indicates whether the UE supports 2-symbol FL DMRS + one additional 2-symbols DMRS for enhanced DMRS ports for PDSCH.
A UE supporting this feature shall also indicate support of FG40-4-1. | FS | No | N/A | N/A | +| pdsch-AlternativeDMRS-Coexistence-r18
Indicates whether the UE supports alternative additional DMRS position for co-existence with LTE CRS for enhanced DMRS ports for PDSCH.
A UE supporting this feature shall also indicate support of FG40-4-1 and rateMatchingL TE-CRS . | FS | No | N/A | N/A | +| pdsch-DMRS-Type-r18
Indicates whether the UE supports DMRS type for enhanced DMRS ports for PDSCH.
A UE supporting this feature shall also indicate support of FG40-4-1. | FS | No | N/A | N/A | +| pdsch-ProcessingType1-DifferentTB-PerSlot
Defines whether the UE capable of processing time capability 1 supports reception of up to two, four or seven unicast PDSCHs for several transport blocks with PDSCH scrambled using C-RNTI, TC-RNTI, MCS-C-RNTI or CS-RNTI in one serving cell within the same slot per CC that are multiplexed in time domain only.
NOTE: PDSCH(s) for Msg.4 is included. | FS | No | N/A | N/A | +| pdsch-ProcessingType2
Indicates whether the UE supports PDSCH processing capability 2. The UE supports it only if all serving cells are self-scheduled and if all serving cells in one band on which the network configured processingType2 use the same subcarrier spacing. This capability signalling comprises the following parameters for each sub-carrier spacing supported by the UE.
  • - fallback indicates whether the UE supports PDSCH processing capability 2 when the number of configured carriers is larger than numberOfCarriers for a reported value of differentTB-PerSlot. If fallback = 'sc', UE supports capability 2 processing time on lowest cell index among the configured carriers in the band where the value is reported, if fallback = 'cap1-only', UE supports only capability 1, in the band where the value is reported;
  • - differentTB-PerSlot indicates whether the UE supports processing type 2 for 1, 2, 4 and/or 7 unicast PDSCHs for different transport blocks per slot per CC; and if so, it indicates up to which number of CA serving cells the UE supports that number of unicast PDSCHs for different TBs. The UE shall include at least one of numberOfCarriers for 1, 2, 4 or 7 transport blocks per slot in this field if pdsch-ProcessingType2 is indicated.
| FS | No | N/A | FR1 only | +| pdsch-ProcessingType2-Limited
Indicates whether the UE supports PDSCH processing capability 2 with scheduling limitation for SCS 30kHz. This capability signalling comprises the following parameter.
  • - differentTB-PerSlot-SCS-30kHz indicates the number of different TBs per slot.
The UE supports this limited processing capability 2 only if:
  1. 1) One carrier is configured in the band, independent of the number of carriers configured in the other bands;
  2. 2) The maximum bandwidth of PDSCH is 136 PRBs;
  3. 3) N1 based on Table 5.3-2 of TS 38.214 [12] for SCS 30 kHz.
| FS | No | N/A | FR1 only | + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|----------| +| pdsch-ReceptionWithoutSchedulingRestriction-r18
Indicates whether the UE supports reception of PDSCH without the scheduling restriction for eType1 DMRS ports.

NOTE: If this feature is not supported, UE expects that gNB shall apply at least the following scheduling restriction for PDSCH for FD-OCC 4 in eType 1 DMRS:
1) The number of consecutively scheduled PRBs for PDSCH is even
2) The number of PRBs offset of scheduled PDSCH from point A (common resource block 0) is even | FS | No | N/A | N/A | +| pdsch-SeparationWithGap
Indicates whether the UE supports separation of two unicast PDSCHs with a gap, applicable to Sub-carrier spacings of 30 kHz and 60 kHz only. For any two consecutive slots n and n+1, if there are more than 1 unicast PDSCH in either slot, the minimum time separation between starting time of any two unicast PDSCHs within the duration of these slots is 4 OFDM symbols for 30kHz and 7 OFDM symbols for 60kHz. | FS | No | N/A | N/A | +| prs-AsSpatialRelationRS-For-SRS-r17
Indicates whether the UE supports PRS as spatial relation RS for SRS.
A UE supporting this feature shall also indicate support of rtt-BasedPDC-PRS-r17 . | FS | No | N/A | FR2 only | +| rtt-BasedPDC-CSI-RS-ForTracking-r17
Indicates whether the UE supports RTT-based propagation delay compensation for time synchronization of the Uu interface based on CSI-RS for tracking and SRS.
A UE supporting this feature shall also indicate support of csi-RS-ForTracking and supportedSRS-Resources . | FS | No | N/A | N/A | +| rtt-BasedPDC-PRS-r17
Indicates whether the UE supports RTT-based Propagation delay compensation for time synchronization of the Uu interface based on DL PRS and SRS. The capability signalling comprises the following parameters:
- maxNumberPRS-Resource-r17 indicates the maximum number of DL PRS Resources in DL PRS Resource Set for PDC, with value n16, n32, and n64 only applicable to FR2 bands.

- maxNumberPRS-ResourceProcessedPerSlot-r17 indicates the maximum number of DL PRS resources that UE can process in a slot.

A UE supporting this feature shall also indicate support of supportedSRS-Resources . | FS | No | N/A | N/A | +| scalingFactor
Indicates the scaling factor to be applied to the serving cell in the max data rate calculation when mcs-Table-r17 and mcs-TableDCI-1-2-r17 are not configured for the serving cell as defined in 4.1.2. Value f0p4 indicates the scaling factor 0.4, f0p75 indicates 0.75, and so on. If absent, the scaling factor 1 is applied to the band in the max data rate calculation. | FS | No | N/A | N/A | +| scalingFactor-1024QAM-FR1-r17
Indicates the scaling factor to be applied to the serving cell in the max data rate calculation when mcs-Table-r17 or mcs-TableDCI-1-2-r17 is configured for the serving cell as defined in 4.1.2 when support of 1024-QAM for PDSCH is signalled for the band. Value f0p4 indicates the scaling factor 0.4, f0p75 indicates 0.75, and so on. If absent, the scaling factor 1 is applied to the band in the max data rate calculation.

UE indicating support of this feature shall also indicate support of pdsch-1024QAM-FR1-r17 or pdsch-1024QAM-2MIMO-FR1-r17 to the band. | FS | No | N/A | FR1 only | +| scellWithoutSSB
Defines whether the UE supports configuration of SCell that does not transmit SS/PBCH block. This is conditionally mandatory with capability signalling for intra-band CA but not supported for inter-band CA. | FS | CY | N/A | N/A | +| searchSpaceSharingCA-DL
Defines whether the UE supports DL PDCCH search space sharing for carrier aggregation operation. | FS | No | N/A | N/A | +| sfn-SchemeA-r17
Indicates whether the UE supports SFN scheme A for PDCCH scheduling SFN Scheme A PDSCH. | FS | No | N/A | N/A | + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|-----| +| sfn-SchemeA-DynamicSwitching-r17
Indicates whether the UE supports dynamic switching between single-TRP and PDSCH SFN scheme A by TCI state field in DCI formats 1_1 and 1_2. The UE supporting this feature shall indicate sfn-SchemeA-r17 or sfn-SchemeA-PDSCH-only-r17 . | FS | No | N/A | N/A | +| sfn-SchemeA-PDCCH-only-r17
Indicates whether the UE supports SFN scheme A for PDCCH scheduling single TRP for PDSCH. | FS | No | N/A | N/A | +| sfn-SchemeA-PDSCH-only-r17
Indicates whether the UE supports SFN scheme A for PDSCH scheduled by single TRP PDCCH. | FS | No | N/A | N/A | +| sfn-SchemeB-r17
Indicates whether the UE supports SFN scheme B for PDCCH scheduling SFN Scheme B PDSCH. | FS | No | N/A | N/A | +| sfn-SchemeB-DynamicSwitching-r17
Indicates whether the UE supports dynamic switching between single-TRP and PDSCH SFN scheme B by TCI state field in DCI formats 1_1 and 1_2. The UE supporting this feature shall indicate sfn-schemeB-r17 or sfn-schemeB-PDSCH-only-r17 . | FS | No | N/A | N/A | +| sfn-SchemeB-PDSCH-only-r17
Indicates whether the UE supports SFN scheme B for PDSCH scheduled by single TRP PDCCH. | FS | No | N/A | N/A | +| simulDMRS-PDSCH-r18
Indicates whether the UE supports Rel-18 DMRS and PDSCH processing capability 2 simultaneously. Additional processing relaxation $d_3$ independently for each SCS in unit of symbols is reported.

A UE supporting this feature shall also indicate support of FG40-4-1/1a, and pdsch-ProcessingType2 or pdsch-ProcessingType2-Limited .

NOTE: PDSCH processing Additional processing relaxation $d_3$ follows pdsch-ProcessingType2 , pdsch-ProcessingType2-Limited , pdsch-ProcessingType2 . | FS | No | N/A | N/A | +| singleDCI-SDM-scheme-r16
Indicates whether the UE supports single DCI based spatial division multiplexing scheme. | FS | No | N/A | N/A | +| sps-Multicast-r17
Indicates whether the UE supports SPS group-common PDSCH for multicast on PCell, comprised of the following functional components:
  • - Supports one SPS group-common PDSCH configuration for multicast;
  • - Supports {2, 4, 8} times semi-static slot-level repetition for SPS group-common PDSCH;
  • - Supports group-common PDCCH/PDSCH with CRC scrambled by G-CS-RNTI(s) for multicast;
  • - Supports DCI format 4_1 with CRC scrambled with G-CS-RNTI for multicast;
  • - Supports ACK/NACK-based HARQ-ACK feedback for SPS release associated with G-CS-RNTI.
A UE supporting this feature shall also indicate support of dynamicMulticastPCell-r17 .

NOTE: One G-CS-RNTI per UE is supported for multicast reception. | FS | No | N/A | N/A | + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|-----|-----|----------| +| supportedSRS-Resources
Defines support of SRS resources for SRS carrier switching for a band without associated FeatureSetUplink. The capability signalling comprising indication of:
  • - maxNumberAperiodicSRS-PerBWP indicates supported maximum number of aperiodic SRS resources that can be configured for the UE per each BWP
  • - maxNumberAperiodicSRS-PerBWP-PerSlot indicates supported maximum number of aperiodic SRS resources per slot in the BWP
  • - maxNumberPeriodicSRS-PerBWP indicates supported maximum number of periodic SRS resources per BWP
  • - maxNumberPeriodicSRS-PerBWP-PerSlot indicates supported maximum number of periodic SRS resources per slot in the BWP
  • - maxNumberSemiPersistentSRS-PerBWP indicate supported maximum number of semi-persistent SRS resources that can be configured for the UE per each BWP
  • - maxNumberSemiPersistentSRS-PerBWP-PerSlot indicates supported maximum number of semi-persistent SRS resources per slot in the BWP
  • - maxNumberSRS-Ports-PerResource indicates supported maximum number of SRS antenna port per each SRS resource
If the UE indicates the support of srs-CarrierSwitch for this band and this field is absent, the UE supports one periodic, one aperiodic, no semi-persistent SRS resources per BWP per slot and one SRS antenna port per SRS resource. | FS | FD | N/A | N/A | +| timeDurationForQCL, timeDurationForQCL-v1710
Defines minimum number of OFDM symbols required by the UE to perform PDCCH reception and applying spatial QCL information received in DCI for PDSCH processing as described in TS 38.214 [12] clause 5.1.5. The number of OFDM symbols is measured from the end of the last symbol of the PDCCH reception to the start of the first symbol of the PDSCH reception. UE shall indicate one value of the minimum number of OFDM symbols per each subcarrier spacing of 60kHz, 120kHz, 480kHz and 960kHz. | FS | Yes | N/A | FR2 only | +| twoFL-DMRS-TwoAdditionalDMRS-DL
Defines whether the UE supports DM-RS pattern for DL transmission with 2 symbols front-loaded DM-RS with one additional 2 symbols DM-RS. | FS | No | N/A | N/A | +| type1-3-CSS
Defines whether the UE is able to receive PDCCH in FR2 in a Type1-PDCCH common search space configured by dedicated RRC signalling, in a Type3-PDCCH common search space or a UE-specific search space if those are associated with a CORESET with a duration of 3 symbols. | FS | Yes | N/A | FR2 only | +| ue-SpecificUL-DL-Assignment
Indicates whether the UE supports dynamic determination of UL and DL link direction and slot format based on Layer 1 scheduling DCI and higher layer configured parameter TDD-UL-DL-ConfigDedicated as specified in TS 38.213 [11]. This capability is not applicable to NCR-MT. | FS | No | N/A | N/A | + +#### 4.2.7.6 *FeatureSetDownlinkPerCC* parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| broadcastSCell-r17
Indicates whether the UE supports MBS reception via broadcast in RRC_CONNECTED, on one frequency indicated in an MBSInterestIndication message, when an SCell is configured and activated on that frequency, as specified in TS 38.331 [9].

NOTE: The UE is not required to receive MBS via broadcast on PCell and SCell simultaneously | FSPC | No | No | No | +| broadcastNonServingCell-r18
Indicates whether the UE supports simultaneous MBS broadcast reception on a non-serving cell on this CC and unicast/multicast reception on other CCs within the same band combination in RRC_CONNECTED. | FSPC | No | N/A | N/A | +| channelBW-90mhz
Indicates whether the UE supports the channel bandwidth of 90 MHz.
For FR1, the UE shall indicate support according to TS 38.101-1 [2], Table 5.3.5-1. | FSPC | CY | N/A | FR1 only | +| dci-BroadcastWith16Repetitions-r17
Indicates whether the UE supports up to 16 times dynamic slot-level repetition for broadcast MTCH. | FSPC | No | No | No | +| fdm-BroadcastUnicast-r17
Indicates whether the UE supports overlapping PDSCH reception that one unicast PDSCH and one group-common PDSCH for broadcast in RRC_CONNECTED in a slot are partially or fully overlapping in time domain and non-overlapping in frequency domain.

A UE supporting this feature shall also support broadcast reception as specified in clause 5.10. | FSPC | No | N/A | N/A | +| fdm-MulticastUnicast-r17
Indicates whether the UE supports overlapping PDSCH reception that one dynamically scheduled unicast PDSCH and one dynamically scheduled group-common PDSCH for multicast in RRC_CONNECTED in a slot are partially or fully overlapping in time domain and non-overlapping in frequency domain.

A UE supporting this feature shall also indicate support of dynamicMulticastPCell-r17 , or at least one of { ack-NACK-FeedbackForSPS-Multicast-r17 , nack-OnlyFeedbackForSPS-Multicast-r17 }.

NOTE: The UE supporting this feature is not required to support FDMeS SPS. | FSPC | No | N/A | N/A | +| intraSlotTDM-UnicastGroupCommonPDSCH-r17
Indicates whether the UE supports Intra-slot TDM-ed unicast PDSCH and group-common PDSCH. The value indicates that for any two consecutive slots n and n+1, if there are more than 1 broadcast/multicast/unicast PDSCH in either slot, whether to require the minimum time separation (4 OFDM symbols for 30kHz and 7 OFDM symbols for 60kHz) between starting time of any two broadcast/multicast/unicast PDSCHs within the duration of these slots.

This feature includes the following functional components:
  • - Supports TDM between one unicast PDSCH and one group-common PDSCH in a slot;
  • - Support TDM between M (M>1) TDMeS unicast PDSCHs and one group-common PDSCH in a slot per CC;
  • - Support TDM among N (N>1) group-common PDSCHs in a slot per CC;
  • - Support TDM between K (K>1) TDMeS unicast PDSCHs and L (L>1) TDMeS group-common PDSCHs in a slot per CC;
  • - The UE maximum number of TDMeS PDSCH receptions capability in a slot per CC is kept based on pdsch-ProcessingType1-DifferentTB-PerSlot;
  • - Up to one broadcast PDSCH is supported in a slot.
A UE supporting this feature shall support broadcast reception as specified in clause 5.10 and/or indicate support of dynamicMulticastPCell-r17 , and shall indicate support of pdsch-ProcessingType1-DifferentTB-PerSlot .

NOTE1: Group-common PDSCH(s) are counted as unicast PDSCH(s).
NOTE2: The max number of (M+1), N, (K+L) are determined based on the numbers reported by pdsch-ProcessingType1-DifferentTB-PerSlot . | FSPC | No | N/A | N/A | + +| | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|-----|----------| +|

supportedCRS-InterfMitigation-r17
Indicates whether the UE supports CRS interference mitigation (CRS-IM) in both DSS and non-DSS scenarios with overlapping spectrum for LTE and NR, which is defined in TS 38.101-4 [18]. The capability signalling contains the following:

  • - crs-IM-DSS-15kHzSCS-r17 indicates whether the UE supports neighboring LTE cell CRS-IM in DSS scenario with NR 15 kHz SCS. UE can indicate support of this capability on the CC(s) in a band only if the UE indicates support of rateMatchingLTE-CRS on that band.
  • - crs-IM-nonDSS-15kHzSCS-r17 indicates whether the UE supports neighboring LTE cell CRS-IM in non-DSS and 15 kHz NR SCS scenario, without the assistance of network signalling on LTE channel bandwidth.
  • - crs-IM-nonDSS-NWA-15kHzSCS-r17 indicates whether the UE supports neighboring LTE cell CRS-IM in non-DSS and 15 kHz NR SCS scenario, with the assistance of network signalling on LTE channel bandwidth.
  • - crs-IM-nonDSS-30kHzSCS-r17 indicates whether the UE supports neighboring LTE cell CRS-IM in non-DSS and 30 kHz NR SCS scenario, without the assistance of network signalling on LTE channel bandwidth.
  • - crs-IM-nonDSS-NWA-30kHzSCS-r17 indicates whether the UE supports neighboring LTE cell CRS-IM in non-DSS and 30 kHz NR SCS scenario, with the assistance of network signalling on LTE channel bandwidth.

For the UE supporting the capability of crs-IM-DSS-15kHzSCS-r17, the UE can perform CRS-IM without the assistant configuration information of neighbour LTE cells when RateMatchPatternLTE-CRS is configured for the serving cell, and if lte-NeighCellsCRS-Assumptions-r17 is not configured.

For the UE supporting the capability of crs-IM-nonDSS-15kHzSCS-r17, the UE can perform CRS-IM without the assistant configuration information of neighbour LTE cells with 15 kHz SCS when RateMatchPatternLTE-CRS is not configured for the serving cell, and if MeasObjectEUTRA is configured, the configured measurement gaps overlap with neighbour LTE cell PBCH position and lte-NeighCellsCRS-Assumptions-r17 is not configured.

For the UE supporting the capabilities of crs-IM-nonDSS-30kHzSCS-r17, the UE can perform CRS-IM without the assistant configuration information of neighbour LTE cells with 30 kHz SCS when RateMatchPatternLTE-CRS is not configured for the serving cell, and if MeasObjectEUTRA is configured, the configured measurement gaps overlap with neighbour LTE cell PBCH position and lte-NeighCellsCRS-Assumptions-r17 is not configured.

NOTE 1: In the DSS scenario, serving and neighboring cells are both operating with dynamic spectrum sharing (DSS) of NR and LTE.

NOTE 2: In the non-DSS scenario, serving cell is operating in NR, and neighboring cells are operating in LTE.

| FSPC | No | No | FR1 only | +|

dynamicMulticastSCell-r17
Indicates whether the UE supports to receive group-common PDCCH/PDSCH with CRC scrambled by G-RNTI for SCell on one frequency, when an SCell is configured and activated on that frequency, as specified in TS 38.331 [9].

A UE supporting this feature shall also indicate support of dynamicMulticastPCell-r17.

NOTE: UE is not expected to be configured simultaneously with more than one component carrier for multicast reception.

| FSPC | No | N/A | N/A | +|

maxModulationOrderForMulticastDataRateCalculation-r17
Defines the maximum modulation order used for maximum data rate calculation for multicast PDSCH.

  • - For FR1, up to 1024QAM is supported as maximum modulation order used for maximum data rate calculation for multicast PDSCH, with candidate values {qam256, qam1024}.
  • - For FR2, up to 256QAM is supported as maximum modulation order used for maximum data rate calculation for multicast PDSCH, with candidate values {qam64, qam256}.

A UE supporting this feature shall also indicate support of dynamicMulticastPCell-r17.

| FSPC | No | N/A | N/A | + +| | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|-----|----------| +| maxNumberMIMO-LayersPDSCH
Defines the maximum number of spatial multiplexing layer(s) supported by the UE for DL reception. For single CC standalone NR, it is mandatory with capability signalling to support at least 4 MIMO layers in the bands where 4Rx is specified as mandatory for the given UE and at least 2 MIMO layers in FR2. If absent, the UE does not support MIMO on this carrier.
For the bands where pdsch-1024QAM-2MIMO-FR1-r17 is indicated, MIMO layers for 1024 QAM is the smaller value between 2 and maxNumberMIMO-LayersPDSCH . | FSPC | CY | N/A | N/A | +| maxNumberMIMO-LayersMulticastPDSCH-r17
Defines the maximum number of spatial multiplexing layer(s) supported by the UE for multicast PDSCH. If not reported, UE supports 1 MIMO layer only for multicast PDSCH.
A UE supporting this feature shall also indicate support of dynamicMulticastPCell-r17 .
NOTE: If the UE supports up to 8 layers, the UE supports second TB (TB2). | FSPC | No | N/A | N/A | +| multiDCI-InterCellMultiTRP-TwoTA-r18
Indicates whether the UE supports two TA enhancement for multi-DCI based inter-cell Multi-TRP operation by indicating the maximum number {1,2} of n-TimingAdvanceOffset value per serving cell.
A UE supporting this feature shall also indicate support of multiDCI-MultiTRP-r16 . | FSPC | No | N/A | N/A | +| multiDCI-IntraCellMultiTRP-TwoTA-r18
Indicates whether the UE supports two TA enhancement for multi-DCI based intra-cell Multi-TRP operation.
A UE supporting this feature shall also indicate support of multiDCI-MultiTRP-r16 . | FSPC | No | N/A | N/A | +| multiDCI-MultiTRP-r16
Indicates whether the UE supports multi-DCI based multi-TRP PDSCH/PUSCH operation and support of fully/partially overlapping PDschs in time and non-overlapping in frequency. This capability applies only to BWPs where two values of coresetPoolIndex are configured. The capability signalling contains the following:
  • - maxNumberCORESET-r16 indicates maximum number of CORESETs configured per BWP per cell in addition to CORESET 0 for multi-DCI based multi-TRP PDSCH/PUSCH operation.
  • - maxNumberCORESETPerPoolIndex-r16 indicates maximum number of CORESETs configured per coresetPoolIndex per BWP per cell in addition to CORESET 0 for multi-DCI based multi-TRP PDSCH/PUSCH operation.
  • - maxNumberUnicastPDSCH-PerPool-r16 indicates maximum number of unicast PDschs per coresetPoolIndex per slot.
NOTE 1: A UE may assume that its maximum receive timing difference between the DL transmissions from two TRPs is within a Cyclic Prefix.
NOTE 2: Processing capability 2 is not supported in any CC if at least one CC is configured with two values of coresetPoolIndex .
NOTE 3: If UE reports value N1 for maxNumberCORESET-r16 , that means UE supports up to min (N1+1, 5) CORESETs in total (including CORESET#0) if there is CORESET#0, and supports maximal N1 CORESETs if there is no CORESET#0.
NOTE 4: If UE reports value N2 for maxNumberCORESETPerPoolIndex-r16 , that means UE supports up to min (N2+1, 3) CORESETs in total (including CORESET#0) for a TRP if there is CORESET#0, and supports maximal N2 CORESETs for another TRP if there is no CORESET#0.
NOTE 5: For the multi-DCI based multi-TRP PUSCH operation, the maximum number of unicast PUSCHs that UE can support per slot is based on pusch-ProcessingType1-DifferentTB-PerSlot , and it is counted across both coresetPoolIndex of TRPs. | FSPC | No | N/A | N/A | +| multiDCI-MultiTRP-CORESET-Monitoring-r18
Indicates whether the UE supports determining two QCL-TypeD for time-domain overlapping CORESETs in the same CC or for intra-band CA associated with coresetPoolIndex value 0 and 1.
The UE supporting this feature shall also indicate support of multiDCI-MultiTRP-r16 . | FSPC | No | N/A | FR2 only | +| rxTimingDiff-r18
Indicates whether the UE supports the Rx timing difference between the two DL reference timings is larger than CP length. | FSPC | No | N/A | N/A | + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|-----|-----| +|

sps-MulticastSCell-r17
Indicates whether the UE supports one SPS group-common PDSCH configuration for multicast for SCell, comprised of the following functional components:

  • - Supports one SPS group-common PDSCH configuration for multicast for SCell;
  • - Supports {2, 4, 8} times semi-static slot-level repetition for SPS group-common PDSCH for SCell;
  • - Supports group-common PDCCH/PDSCH with CRC scrambled by G-CS-RNTI(s) for multicast;
  • - Supports DCI format 4_1 with CRC scrambled with G-CS-RNTI for multicast;
  • - Supports ACK/NACK-based HARQ-ACK feedback for SPS release associated with G-CS-RNTI.

A UE supporting this feature shall also indicate support of sps-Multicast-r17 and dynamicMulticastSCell-r17.

| FSPC | No | N/A | N/A | +|

sps-MulticastSCellMultiConfig-r17
Indicates whether the UE supports up to 8 SPS group-common PDSCH configurations per CFR for multicast for SCell. The value indicates the maximum number of activated SPS group-common PDSCH configurations per CFR for multicast for SCell.
The total number of SPS configurations for both multicast and unicast is no larger than 8 in a BWP of a serving cell. The total number of SPS configurations for both multicast and unicast in a cell group is no larger than 32.

A UE supporting this feature shall also indicate support of sps-MulticastSCell-r17.

| FSPC | No | N/A | N/A | +|

supportedBandwidthDL, supportedBandwidthDL-v1710
Indicates maximum DL channel bandwidth supported for a given SCS that UE supports within a single CC (and in case of DAPS handover for the source or target cell), which is defined in Table 5.3.5-1 in TS 38.101-1 [2] for FR1 and Table 5.3.5-1 in TS 38.101-2 [3] for FR2.
For FR1, all the bandwidths listed in TS 38.101-1 [2], Table 5.3.5-1 for each band shall be mandatory with a single CC unless indicated optional. For FR2, the set of mandatory CBW is 50, 100, 200 MHz. When this field is included in a band combination with a single band entry and a single CC entry (i.e. non-CA band combination), the UE shall indicate the maximum channel bandwidth for the band according to TS 38.101-1 [2] and TS 38.101-2 [3]. For FR2, supportedBandwidthDL-v1710 is included if the maximum DL channel bandwidth supported by the UE within a single CC is greater than 400MHz. When the supportedBandwidthDL and the supportedBandwidthDL-v1710 are reported together for a CC, the network which is able to decode the supportedBandwidthDL-v1710 ignores the supportedBandwidthDL.
The UE may report a supportedBandwidthDL wider than the channelBWs-DL; this supportedBandwidthDL may not be included in the Table 5.3.5-1 of TS 38.101-1 [2]/TS 38.101-2 [3] for the case that the UE is unable to report the actual supported bandwidth according to the Table 5.3.5-1 of TS 38.101-1 [2]/TS 38.101-2 [3]. For each band, (e)RedCap UEs shall indicate its maximum channel bandwidth, which is the maximum of those channel bandwidths that are less than or equal to 20 MHz for FR1 and less than or equal to 100 Mhz for FR2, taking restrictions in TS 38.101-1 [2] and TS 38.101-2 [3] into consideration.

NOTE: To determine whether the UE supports a channel bandwidth of 90 MHz, the network may ignore this capability and validate instead the channelBW-90mhz, the supportedBandwidthCombinationSet and the supportedBandwidthCombinationSetIntraENDC. To determine whether the UE supports a channel bandwidth of 400 MHz, the network validates this capability, the supportedBandwidthCombinationSet, and the supportedBandwidthCombinationSetIntraENDC. For serving cell(s) with other channel bandwidths the network validates the channelBWs-DL, the supportedBandwidthCombinationSet, the supportedBandwidthCombinationSetIntraENDC, the asymmetricBandwidthCombinationSet (for a band supporting asymmetric channel bandwidth as defined in clause 5.3.6 of TS 38.101-1 [2]), supportedBandwidthDL/supportedBandwidthDL-v1710 and supportedMinBandwidthDL.

| FSPC | CY | N/A | N/A | + +| | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|-----|-----| +| supportedMinBandwidthDL-r17
Indicates minimum DL channel bandwidth supported for a given SCS that UE supports within a single CC (and in case of intra-frequency DAPS handover for the source and target cells), which is defined in Table 5.3.5-1 in TS 38.101-1 [2] for FR1 and Table 5.3.5-1 in TS 38.101-2 [3] for FR2. This parameter is only applicable to the Bandwidth Combination Set 5. This field does not restrict the bandwidths configured for a single CC (i.e. non-CA case). | FSPC | CY | N/A | N/A | +| supportedModulationOrderDL
Indicates the maximum supported modulation order to be applied for downlink in the carrier in the max data rate calculation as defined in 4.1.2. If included, the network may use a modulation order on this serving cell which is higher than the value indicated in this field as long as UE supports the modulation of higher value for downlink. If not included:
  • - for FR1, the network uses the modulation order signalled per band i.e. pdsch-1024QAM-FR1-r17 or pdsch-1024QAM-2MIMO-FR1-r17 when pdsch-1024QAM-FR1-r17 or pdsch-1024QAM-2MIMO-FR1-r17 is signalled for the band, otherwise the network uses the modulation order signalled in pdsch-256QAM-FR1. The network uses the modulation order 64QAM if pdsch-256QAM-FR1 is not signalled for the band for RedCap UE.
  • - for FR2, the network uses the modulation order signalled per band i.e. pdsch-256QAM-FR2 if signalled. If not signalled in a given band, the network shall use the modulation order 64QAM.
In all the cases, it shall be ensured that the data rate does not exceed the max data rate ( DataRate ) and max data rate per CC ( DataRateCC ) according to TS 38.214 [12]. | FSPC | No | N/A | N/A | +| supportedSubCarrierSpacingDL
Defines the supported sub-carrier spacing for DL by the UE, as defined in clause 4.2-1 of TS 38.211 [6], indicating the UE supports simultaneous reception with same or different numerologies in CA. Support of simultaneous reception with same numerology for intra-band NR CA including both contiguous and non-contiguous is mandatory with capability in both FR1 and FR2. Support of simultaneous reception with two different numerologies between FR1 band(s) and FR2 band(s) in DL is mandatory with capability if UE supports inter-band NR CA including both FR1 band(s) and FR2 band(s). Optional for other cases. Support of simultaneous reception of with different numerologies in CA for other cases is optional. | FSPC | CY | N/A | N/A | +| supportFDM-SchemeB-r16
Indicates whether UE supports single DCI based FDMSchemeB. | FSPC | No | N/A | N/A | + +#### 4.2.7.7 *FeatureSetUplink* parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|-----|--------------|--------------| +| scalingFactor
Indicates the scaling factor to be applied to the band in the max data rate calculation as defined in 4.1.2. Value f0p4 indicates the scaling factor 0.4, f0p75 indicates 0.75, and so on. If absent, the scaling factor 1 is applied to the band in the max data rate calculation. | FS | No | N/A | N/A | +| cbgPUSCH-ProcessingType1-DifferentTB-PerSlot-r16
Defines whether the UE capable of processing time capability 1 supports CBG based transmission with one or with up to two or with up to four or with up to seven unicast PUSCHs per slot per CC. | FS | No | N/A | N/A | +| cbgPUSCH-ProcessingType2-DifferentTB-PerSlot-r16
Defines whether the UE capable of processing time capability 2 supports CBG based transmission with one or with up to two or with up to four or with up to seven unicast PUSCHs per slot per CC. | FS | No | N/A | N/A | +| crossCarrierSchedulingProcessing-DiffSCS-r16
Indicates the UE cross carrier scheduling processing capability for UL carrier aggregation processing up to X unicast DCI scheduling for UL per scheduled CC. X is based on pair of (scheduling CC SCS, scheduled CC SCS) where a pair of (15, 120), (15, 60), (30, 120) kHz SCS can have X = {1, 2, 4} while a pair of (15, 30), (30, 60), (60, 120) kHz SCS can have X = {2}, and X applies per slot of scheduling CC. | FS | No | N/A | N/A | +| dynamicSwitchSUL
Indicates whether the UE supports supplemental uplink with dynamic switch (DCI based selection of PUSCH carrier). The UE supports this among a carrier on a band X and a band Y if it sets this capability parameter for both band X and band Y. | FS | No | N/A | N/A | +| extendedDC-LocationReport-r17
Indicates whether the UE supports extended DC location reporting (based on indicated default DC location) for at least 2 UL CCs in one band. A UE that supports this feature also supports extended DC location reporting for 1 UL CC in one band. | FS | No | N/A | N/A | +| featureSetListPerUplinkCC
Indicates which features the UE supports on the individual UL carriers of the feature set (and hence of a band entry that refer to the feature set) by FeatureSetUplinkPerCC-Id . The order of the elements in this list is not relevant, i.e., the network may configure any of the carriers in accordance with any of the FeatureSetUplinkPerCC-Id in this list. A fallback per CC feature set resulting from the reported feature set per UL CC is not signalled but the UE shall support it. | FS | N/A | N/A | N/A | +| interSubslotFreqHopping-PUCCH-r17
Indicates whether the UE supports inter-subslot frequency hopping for PUCCH repetitions comprised of the following functional components:
  • - Inter-subslot frequency hopping for PUCCH repetition operation of PUCCH Formats 0, 1, 2, 3 and 4 for 7OS slot-based PUCCH configurations;
  • - Inter-subslot frequency hopping for PUCCH repetition operation of PUCCH Format 0 and Format 2 for 20S slot-based PUCCH configurations.
The UE indicating support of this feature shall also indicate the support of pucch-Repetition-F0-1-2-3-4-RRConfig-r17 . | FS | No | N/A | N/A | +| intraBandFreqSeparationUL-v1620
Indicates UL frequency separation class the UE supports, which indicates a maximum frequency separation between lower edge of lowest CC and upper edge of highest CC in a frequency band, for intra-band non-contiguous CA. The UE sets the same value in the FeatureSetUplink of each band entry within a band. The values mhzX corresponds to the values XMHz defined in TS 38.101-2 [3]. It is mandatory to report for UE which supports UL non-contiguous CA in FR2. If the UE sets the field intraBandFreqSeparationUL-v1620 it shall set intraBandFreqSeparationUL (without suffix) to the nearest smaller value. | FS | CY | N/A | FR2 only | +| intraFreqDAPS-UL-r16
Indicates whether UE supports enhanced uplink capabilities for intra-frequency DAPS handover. The UE only includes this capability signalling if intraFreqDAPS-r16 is included in the FeatureSetDownlink for the same FeatureSet . The capability signalling comprises of the following parameter:
  • - intraFreqTwoTAGs-DAPS-r16 indicates whether the UE supports different timing advance groups in source PCell and intra-frequency target PCell. It is mandatory with capability signalling.
| FS | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----|--------------|--------------| +| scalingFactor
Indicates the scaling factor to be applied to the band in the max data rate calculation as defined in 4.1.2. Value f0p4 indicates the scaling factor 0.4, f0p75 indicates 0.75, and so on. If absent, the scaling factor 1 is applied to the band in the max data rate calculation. | FS | No | N/A | N/A | +| cbgPUSCH-ProcessingType1-DifferentTB-PerSlot-r16
Defines whether the UE capable of processing time capability 1 supports CBG based transmission with one or with up to two or with up to four or with up to seven unicast PUSCHs per slot per CC. | FS | No | N/A | N/A | +| cbgPUSCH-ProcessingType2-DifferentTB-PerSlot-r16
Defines whether the UE capable of processing time capability 2 supports CBG based transmission with one or with up to two or with up to four or with up to seven unicast PUSCHs per slot per CC. | FS | No | N/A | N/A | +| max2SP1SRS8T8R-AntennaSwitch-r18
Indicates whether the UE supports maximum 2 SP SRS resource sets and maximum 1 periodic SRS resource set for 8T8R antenna switching.
A UE supports this feature shall also indicate support of FG40-5-4.

NOTE 1: If UE does NOT support this feature, support maximum one SRS resource set for periodic SRS and maximum one SRS resource set for semi-persistent SRS

NOTE 2: The two SP-SRS resource sets are not activated at the same time. | FS | No | N/A | N/A | +| mTRP-PUCCH-IntraSlot-r17
Indicates whether the UE supports PUCCH repetition scheme 3 (intra-slot repetition) with sequential mapping for repetitions larger than 2 and cyclic mapping for 2 repetitions by indicating the supported PUCCH formats for this scheme. The UE indicating this feature shall also support up to two PUCCH power control parameter sets/spatial relation info per PUCCH resource.
Power control parameter sets feature is applicable to FR1 only (without spatial relation info) and spatial relation info is applicable to FR2 only. | FS | No | N/A | N/A | +| mTRP-PUSCH-TypeA-CB-r17
Indicates the support of multi-TRP PUSCH repetition based on codebook with PUSCH repetition type A. The value indicates the supported number of SRS resources in one SRS resource set.

This feature includes the following features:
  • - sequential mapping for repetitions larger than 2.
  • - cyclic mapping for 2 repetitions.
  • - two SRS resource sets with usage set to 'codebook'.
The UE indicating support of this feature shall also indicate the support of mimo-CB-PUSCH . If the value of supported number of SRS resources is 4 then the UE shall also indicate support of ul-FullPwrMode2-MaxSRS-ResInSet set to n4. | FS | No | N/A | N/A | +| mTRP-PUSCH-RepetitionTypeA-r17
Indicates whether the UE supports multi-TRP PUSCH repetition for non-codebook based PUSCH repetition type A with sequential mapping for repetitions larger than 2 and cyclic mapping for 2 repetitions by indicating the supported number of SRS resources in one SRS resource set. The UE indicating this feature shall also support two SRS resource sets with usage set to 'nonCodebook'.
The UE indicating this feature shall indicate support of maxNumberMIMO-LayersNonCB-PUSCH and mimo-NonCB-PUSCH . | FS | No | N/A | N/A | +| multiPUCCH-r16
Indicates whether the UE supports more than one PUCCH for HARQ-ACK transmission within a slot. This field includes the following parameters:
  • - sub-SlotConfig-NCP-r16 indicates the sub-slot configuration for NCP;
  • - sub-SlotConfig-ECP-r16 indicates the sub-slot configuration for ECP.
For NCP, the value set1 denotes 7-symbol*2, and set2 denotes 2-symbol*7 and 7-symbol*2.
For ECP, the value set1 denotes 6-symbol*2, and set2 denotes 2-symbol*6 and 6-symbol*2. | FS | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----|--------------|--------------| +| scalingFactor
Indicates the scaling factor to be applied to the band in the max data rate calculation as defined in 4.1.2. Value f0p4 indicates the scaling factor 0.4, f0p75 indicates 0.75, and so on. If absent, the scaling factor 1 is applied to the band in the max data rate calculation. | FS | No | N/A | N/A | +| cbgPUSCH-ProcessingType1-DifferentTB-PerSlot-r16
Defines whether the UE capable of processing time capability 1 supports CBG based transmission with one or with up to two or with up to four or with up to seven unicast PUSCHs per slot per CC. | FS | No | N/A | N/A | +| cbgPUSCH-ProcessingType2-DifferentTB-PerSlot-r16
Defines whether the UE capable of processing time capability 2 supports CBG based transmission with one or with up to two or with up to four or with up to seven unicast PUSCHs per slot per CC. | FS | No | N/A | N/A | +| mux-SR-HARQ-ACK-r16
Indicates whether the UE supports SR/HARQ-ACK multiplexing once per subslot using a PUCCH (or HARQ-ACK piggybacked on a PUSCH) when SR/HARQ-ACK are supposed to be sent with different starting symbols in a subslot. | FS | No | N/A | N/A | +| offsetSRS-CB-PUSCH-Ant-Switch-fr1-r16
Indicates whether UE requires minimum of 19 symbols offset between aperiodic SRS triggering and transmission for SRS for codebook based PUSCH and antenna switching.

UE indicating support of this shall indicate support of supportedSRS-Resources . | FS | No | N/A | FR1 only | +| offsetSRS-CB-PUSCH-PDCCH-MonitorSingleOcc-fr1-r16
Indicates whether UE requires minimum of 19 symbols offset between aperiodic SRS triggering and transmission for SRS for codebook based PUSCH and antenna switching for the case of PDCCH monitoring on any span of up to 3 consecutive OFDM symbols of a slot.

UE indicating support of this shall indicate support of supportedSRS-Resources . | FS | No | N/A | FR1 only | +| offsetSRS-CB-PUSCH-PDCCH-MonitorAnyOccWithoutGap-fr1-r16
Indicates whether UE requires minimum of 19 symbols offset between aperiodic SRS triggering and transmission for the case of PDCCH search space monitoring occasions in any symbol of the slot for Type 1-PDCCH common search space configured by dedicated RRC signalling, for a Type 3-PDCCH common search space, or for a UE-specific search space with the capability of supporting at least 44, 36, 22, and 20 blind decodes in a slot for 15 kHz, 30 kHz, 60kHz, and 120 kHz subcarrier spacing values respectively.

UE indicating support of this shall indicate support of supportedSRS-Resources . | FS | No | N/A | FR1 only | +| offsetSRS-CB-PUSCH-PDCCH-MonitorAnyOccWithGap-fr1-r16
Indicates whether UE requires minimum of 19 symbols offset between aperiodic SRS triggering and transmission for SRS for codebook based PUSCH and antenna switching for the case of PDCCH search space monitoring occasions in any symbol of the slot with minimum time separation of two OFDM symbols for 15 kHz, four OFDM symbols for 30 kHz, seven OFDM symbols for 60 kHz with NCP, and 14OFDM symbols for 120kHz between two consecutive transmissions of PDCCH scrambled with C-RNTI, MCS-C-RNTI, or CS-RNTI for Type 1-PDCCH common search space configured by dedicated RRC signalling, for a Type 3-PDCCH common search space, or for a UE-specific search space, with the capability of supporting at least 44, 36, 22, and 20 blind decodes in a slot for 15 kHz, 30 kHz, 60kHz, and 120 kHz subcarrier spacing values respectively.

UE indicating support of this shall indicate support of pdcch-MonitoringAnyOccasions with value withDCI-Gap and supportedSRS-Resources . | FS | No | N/A | FR1 only | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----|--------------|--------------| +| scalingFactor
Indicates the scaling factor to be applied to the band in the max data rate calculation as defined in 4.1.2. Value f0p4 indicates the scaling factor 0.4, f0p75 indicates 0.75, and so on. If absent, the scaling factor 1 is applied to the band in the max data rate calculation. | FS | No | N/A | N/A | +| cbgPUSCH-ProcessingType1-DifferentTB-PerSlot-r16
Defines whether the UE capable of processing time capability 1 supports CBG based transmission with one or with up to two or with up to four or with up to seven unicast PUSCHs per slot per CC. | FS | No | N/A | N/A | +| cbgPUSCH-ProcessingType2-DifferentTB-PerSlot-r16
Defines whether the UE capable of processing time capability 2 supports CBG based transmission with one or with up to two or with up to four or with up to seven unicast PUSCHs per slot per CC. | FS | No | N/A | N/A | +| offsetSRS-CB-PUSCH-PDCCH-MonitorAnyOccWithSpanGap-fr1-r16
Indicates whether UE requires minimum of 19 symbols offset between aperiodic SRS triggering and transmission for the case of PDCCH search space monitoring occasions in any symbol of the slot with minimum time separation between two consecutive transmissions of PDCCH with span up to two OFDM symbols for two OFDM symbols or span up to three OFDM symbols for four and seven OFDM symbols. Value set1 indicates the supported value set (X,Y) is (7,3), value set2 indicates the supported value set (X,Y) is (4,3) and (7,3) and value set 3 indicates the supported value set (X,Y) is (2,2), (4,3) and (7,3). | FS | No | N/A | FR1 only | +| UE indicating support of this shall indicate support of supportedSRS-Resources . | | | | | +| pa-PhaseDiscontinuityImpacts
Indicates incapability motivated by impacts of PA phase discontinuity with overlapping transmissions with non-aligned starting or ending times or hop boundaries across carriers for intra-band (NG)EN-DC/NE-DC, intra-band CA and FDM based ULSUP. | FS | No | N/A | N/A | +| This capability applies to:
  • - Intra-band (NG)EN-DC/NE-DC combination without additional inter-band NR and LTE CA component;
  • - Intra-band (NG)EN-DC/NE-DC combination supporting both UL and DL intra-band (NG)EN-DC/NE-DC parts with additional inter-band NR/LTE CA component;
  • - Inter-band (NG)EN-DC/NE-DC combination, where the frequency range of the E-UTRA band is a subset of the frequency range of the NR band (as specified in Table 5.5B.4.1-1 of TS 38.101-3 [4]).
If this capability is included in an "Intra-band (NG)EN-DC/NE-DC combination supporting both UL and DL intra-band (NG)EN-DC/NE-DC parts with additional inter-band NR/LTE CA component", this capability applies to the intra-band (NG)EN-DC/NE-DC BC part. | | | | | +| partialCancellationPUCCH-PUSCH-PRACH-TX-r16
Indicates whether UE supports the partial cancellation of the configured PUCCH or PUSCH or PRACH transmission in set of symbols of a slot due to:
  • - Detection of 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;
  • - DCI format 2_0 being configured but not detected, when either a subset of symbols from the set of symbols are indicated as flexible by tdd-UL-DL-ConfigurationCommon, and tdd-UL-DL-ConfigurationDedicated if provided, or tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated are not provided to the UE;
  • - Detection of a DCI format 1_0, DCI format 1_1, DCI format 1_2 or DCI format 0_1 and DCI format 0_2 indicating to the UE to receive CSI-RS or PDSCH in a subset of symbols from the set of symbols.
| FS | No | N/A | N/A | +| phaseReportMoreThanOne-r18
Indicates whether the UE supports phase report for Y>=1.
A UE supporting this feature shall also indicate support of FG40-3-3-1. | FS | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----|--------------|--------------| +| scalingFactor
Indicates the scaling factor to be applied to the band in the max data rate calculation as defined in 4.1.2. Value f0p4 indicates the scaling factor 0.4, f0p75 indicates 0.75, and so on. If absent, the scaling factor 1 is applied to the band in the max data rate calculation. | FS | No | N/A | N/A | +| cbgPUSCH-ProcessingType1-DifferentTB-PerSlot-r16
Defines whether the UE capable of processing time capability 1 supports CBG based transmission with one or with up to two or with up to four or with up to seven unicast PUSCHs per slot per CC. | FS | No | N/A | N/A | +| cbgPUSCH-ProcessingType2-DifferentTB-PerSlot-r16
Defines whether the UE capable of processing time capability 2 supports CBG based transmission with one or with up to two or with up to four or with up to seven unicast PUSCHs per slot per CC. | FS | No | N/A | N/A | +| phy-PrioritizationHighPriorityDG-LowPriorityCG-r17
Indicates whether the UE supports PHY prioritization of overlapping high-priority DG-PUSCH and low-priority CG-PUSCH comprised of the following functional components:
  • - PHY prioritization of overlapping high-priority dynamic grant PUSCH and low-priority configured grant PUSCH on a BWP of a serving cell;
  • - Configuration of PHY priority level for CG PUSCH, and dynamic indication of priority level for dynamic PUSCH with a single DCI format.
The capability signalling comprises the following parameters:
  • - pusch-PreparationLowPriority-r17 indicates additional number of symbols (d1) needed beyond the PUSCH preparation time for cancelling a low priority UL transmission;
  • - additionalCancellationTime-r17 indicates additional number of symbols (d3) needed on top of Rel-16 cancellation time (which results N2+d1+d3 in total cancellation time);
  • - maxNumberCarriers-r17 indicates maximum number of supported carriers on the band across a set of contiguous carriers for the reported FS of that band.
The value sym0 denotes 0 symbol, sym1 denotes one symbol, and so on. | FS | No | N/A | N/A | +| phy-PrioritizationLowPriorityDG-HighPriorityCG-r17
Indicates whether the UE supports PHY prioritization of overlapping low-priority DG-PUSCH and high-priority CG-PUSCH comprised of the following functional components:
  • - PHY prioritization for the case where low-priority DG-PUSCH collides with high-priority CG-PUSCH;
  • - Configuration of PHY priority level for CG PUSCH, and dynamic indication of priority level for dynamic PUSCH with a single DCI format.
The value indicates maximum number of supported carriers on the band across a set of contiguous carriers for the reported FS of that band. | FS | No | N/A | N/A | +| pucch-Repetition-F0-1-2-3-4-DynamicIndication-r17
Indicates whether the UE supports repetitions for PUCCH format 0, 1, 2, 3 and 4 over multiple PUCCH subslots based on dynamic repetition indication.

The UE indicating support of this feature shall also indicate the support of pucch-Repetition-F0-1-2-3-4-RRC-Config-r17 .

NOTE: Dynamic PUCCH repetition factor indication is only supported for HARQ-ACK. | FS | No | N/A | N/A | +| pucch-Repetition-F0-1-2-3-4-RRC-Config-r17
Indicates whether the UE supports repetitions for PUCCH format 0, 1, 2, 3 and 4 over multiple PUCCH subslots with RRC configured repetition factor K = 2, 4, 8. A UE supporting this feature shall also indicate support of pucch-Repetition-F1-3-4 and multiPUCCH-r16 .

NOTE: The support of this feature doesn't imply an increase of the maximum number of PUCCHs per slot that supported by the UE. | FS | No | N/A | N/A | +| pucch-SingleDCI-STx2P-SFN-r18
Indicates whether the UE supports single-DCI based STx2P SFN scheme for PUCCH and the supported PUCCH formats for STxMP SFN scheme. | FS | No | N/A | FR2 only | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----|--------------|--------------| +| scalingFactor
Indicates the scaling factor to be applied to the band in the max data rate calculation as defined in 4.1.2. Value f0p4 indicates the scaling factor 0.4, f0p75 indicates 0.75, and so on. If absent, the scaling factor 1 is applied to the band in the max data rate calculation. | FS | No | N/A | N/A | +| cbgPUSCH-ProcessingType1-DifferentTB-PerSlot-r16
Defines whether the UE capable of processing time capability 1 supports CBG based transmission with one or with up to two or with up to four or with up to seven unicast PUSCHs per slot per CC. | FS | No | N/A | N/A | +| cbgPUSCH-ProcessingType2-DifferentTB-PerSlot-r16
Defines whether the UE capable of processing time capability 2 supports CBG based transmission with one or with up to two or with up to four or with up to seven unicast PUSCHs per slot per CC. | FS | No | N/A | N/A | +| pusch-1SymbolFL-DMRS-Addition3Symbol-r18
Indicates whether the UE supports 1 symbol FL DMRS and 3 additional DMRS symbols for enhanced DMRS ports for PUSCH.
A UE supporting this feature shall also indicate support of FG40-4-6. | FS | No | N/A | N/A | +| pusch-2SymbolFL-DMRS-r18
Indicates whether the UE supports 2 symbols FL-DMRS for enhanced DMRS ports for PUSCH.
A UE supporting this feature shall also indicate support of FG40-4-6. | FS | No | N/A | N/A | +| pusch-2SymbolFL-DMRS-Addition2Symbol-r18
Indicates whether the UE supports 2-symbol FL DMRS + one additional 2-symbols DMRS for enhanced DMRS ports for PUSCH.
A UE supporting this feature shall also indicate support of FG40-4-6. | FS | No | N/A | N/A | +| pusch-ProcessingType1-DifferentTB-PerSlot
Indicates whether the UE capable of processing time capability 1 supports transmission of up to two, four or seven unicast PUSCHs for several transport blocks in one serving cell within the same slot per CC that are multiplexed in time domain only. | FS | No | N/A | N/A | +| pusch-ProcessingType2
Indicates whether the UE supports PUSCH processing capability 2. The UE supports it only if all serving cells are self-scheduled and if all serving cells in one band on which the network configured processingType2 use the same subcarrier spacing. This capability signalling comprises the following parameters for each sub-carrier spacing supported by the UE.
  • - fallback indicates whether the UE supports PUSCH processing capability 2 when the number of configured carriers is larger than numberOfCarriers for a reported value of differentTB-PerSlot. If fallback = 'sc', UE supports capability 2 processing time on lowest cell index among the configured carriers in the band where the value is reported, if fallback = 'cap1-only', UE supports only capability 1, in the band where the value is reported;
  • - differentTB-PerSlot indicates whether the UE supports processing type 2 for 1, 2, 4 and/or 7 unicast PUSCHs for different transport blocks per slot per CC; and if so, it indicates up to which number of CA serving cells the UE supports that number of unicast PUSCHs for different TBs. The UE shall include at least one of numberOfCarriers for 1, 2, 4 or 7 transport blocks per slot in this field if pusch-ProcessingType2 is indicated.
| FS | No | N/A | FR1 only | +| pusch-RepetitionTypeB-r16, pusch-RepetitionTypeB-v16d0
Indicates whether the UE supports PUSCH repetition type B, as specified in 6.1.2 of TS 38.214 [12].
The maxNumberPUSCH-Tx-r16 in pusch-RepetitionTypeB-r16 indicates the supported maximum number of PUSCH transmissions within a slot for all TB(s) for processing capability 1 if pusch-ProcessingType2 is not included, or for both processing capability 1 and processing capability 2 if pusch-ProcessingType2 is included. The maxNumberPUSCH-Tx-Cap1-r16 and maxNumberPUSCH-Tx-Cap2-r16 in pusch-RepetitionTypeB-v16d0 are for processing capability 1 and processing capability 2 separately, which are only included when different values are supported for the processing capabilities. The maxNumberPUSCH-Tx-r16 will be ignored by the network if the pusch-RepetitionTypeB-v16d0 is included. | FS | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----|--------------|--------------| +| scalingFactor
Indicates the scaling factor to be applied to the band in the max data rate calculation as defined in 4.1.2. Value f0p4 indicates the scaling factor 0.4, f0p75 indicates 0.75, and so on. If absent, the scaling factor 1 is applied to the band in the max data rate calculation. | FS | No | N/A | N/A | +| cbgPUSCH-ProcessingType1-DifferentTB-PerSlot-r16
Defines whether the UE capable of processing time capability 1 supports CBG based transmission with one or with up to two or with up to four or with up to seven unicast PUSCHs per slot per CC. | FS | No | N/A | N/A | +| cbgPUSCH-ProcessingType2-DifferentTB-PerSlot-r16
Defines whether the UE capable of processing time capability 2 supports CBG based transmission with one or with up to two or with up to four or with up to seven unicast PUSCHs per slot per CC. | FS | No | N/A | N/A | +| pusch-SeparationWithGap
Indicates whether the UE supports separation of two unicast PUSCHs with a gap, applicable to Sub-carrier spacings of 15 kHz, 30 kHz and 60 kHz only. For any two consecutive slots n and n+1, if there are more than 1 unicast PUSCH in either slot, the minimum time separation between starting time of any two unicast PUSCHs within the duration of these slots is 2 OFDM symbols for 15kHz, 4 OFDM symbols for 30kHz and 7 OFDM symbols for 60kHz. | FS | No | N/A | N/A | +| searchSpaceSharingCA-UL
Defines whether the UE supports UL PDCCH search space sharing for carrier aggregation operation. | FS | No | N/A | N/A | +| semiStaticHARQ-ACK-CodebookSub-SlotPUCCH-r17
Indicates whether the UE supports Semi-static (Type 1) HARQ-ACK codebook for sub-slot based PUCCH configuration.
A UE supporting this feature shall also indicate support of semiStaticHARQ-ACK-Codebook and multiPUCCH-r16 . | FS | No | N/A | N/A | +| simultaneousTxSUL-NonSUL
Indicates whether the UE supports simultaneous transmission of SRS on an SUL/non-SUL carrier and PUSCH/PUCCH/SRS on the other UL carrier in the same cell. The UE supports simultaneous transmission on an SUL band X and a Non-SUL band Y if it sets this capability parameter for both band X and band Y. | FS | No | N/A | N/A | +| srs-AntennaSwitching2SP-1Periodic-r17
Indicates whether the UE supports maximum 2 SP SRS resource sets and maximum 1 periodic SRS resource set for antenna switching.
The UE indicating support of this shall indicate support of supportedSRS-Resources .

NOTE:
- Applies for all supported xTyR where y<=8
- For xTyR where y>4, if UE does not support this feature, UE supports maximum one SRS resource set for periodic SRS and maximum one SRS resource set for semi-persistent SRS
- For xTyR where y<=4, if UE does not support this feature, UE follows Rel-15 on the number of resource sets for periodic and semi-persistent SRS

The two SP-SRS resource sets are not activated at the same time. | FS | No | N/A | N/A | +| srs-ExtensionAperiodicSRS-r17
Indicates whether the UE supports 4 aperiodic SRS resource sets for 1T4R and 2 aperiodic resource sets for 1T2R/2T4R.
The UE indicating support of this shall indicate support of srs-TxSwitch and supportedSRS-Resources . | FS | No | N/A | N/A | +| srs-OneAP-SRS-r17
Indicates the support of 1 aperiodic SRS resource sets for 1T4R.

The UE indicating support of this feature shall also indicate the support of srs-StartAnyOFDM-Symbol-r16 and srs-TxSwitch . | FS | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----|--------------|--------------| +| scalingFactor
Indicates the scaling factor to be applied to the band in the max data rate calculation as defined in 4.1.2. Value f0p4 indicates the scaling factor 0.4, f0p75 indicates 0.75, and so on. If absent, the scaling factor 1 is applied to the band in the max data rate calculation. | FS | No | N/A | N/A | +| cbgPUSCH-ProcessingType1-DifferentTB-PerSlot-r16
Defines whether the UE capable of processing time capability 1 supports CBG based transmission with one or with up to two or with up to four or with up to seven unicast PUSCHs per slot per CC. | FS | No | N/A | N/A | +| cbgPUSCH-ProcessingType2-DifferentTB-PerSlot-r16
Defines whether the UE capable of processing time capability 2 supports CBG based transmission with one or with up to two or with up to four or with up to seven unicast PUSCHs per slot per CC. | FS | No | N/A | N/A | +| srs-PosResources-r16
Indicates support of SRS for positioning. UE supporting this feature should also support open loop power control for positioning SRS based on SSB from the serving cell. The capability signalling comprises the following parameters:
  • - maxNumberSRS-PosResourceSetPerBWP-r16 Indicates the max number of SRS Resource Sets for positioning supported by UE per BWP;
  • - maxNumberSRS-PosResourcesPerBWP-r16 indicates the max number of SRS resources for positioning supported by UE per BWP, including periodic, semi-persistent, and aperiodic SRS;
  • - maxNumberSRS-ResourcesPerBWP-PerSlot-r16 indicates the max number of SRS resources configured by SRS-Resource and SRS-PosResource-r16 supported by UE per BWP, including periodic, semi-persistent, and aperiodic SRS;
  • - maxNumberPeriodicSRS-PosResourcesPerBWP-r16 indicates the max number of periodic SRS resources for positioning supported by UE per BWP;
  • - maxNumberPeriodicSRS-PosResourcesPerBWP-PerSlot-r16 indicates the max number of periodic SRS resources for positioning supported by UE per BWP per slot.
| FS | No | N/A | N/A | +| srs-PosResourceAP-r16
Indicates support of aperiodic SRS for positioning. The UE can include this field only if the UE supports srs-PosResources-r16 . Otherwise, the UE does not include this field. The capability signalling comprises the following parameters:
  • - maxNumberAP-SRS-PosResourcesPerBWP-r16 indicates the max number of aperiodic SRS resources for positioning supported by UE per BWP;
  • - maxNumberAP-SRS-PosResourcesPerBWP-PerSlot-r16 indicates the max number of aperiodic SRS resources for positioning supported by UE per BWP per slot.
| FS | No | N/A | N/A | +| srs-PosResourceSP-r16
Indicates support of semi-persistent SRS for positioning. The UE can include this field only if the UE supports srs-PosResources-r16 . Otherwise, the UE does not include this field. The capability signalling comprises the following parameters:
  • - maxNumberSP-SRS-PosResourcesPerBWP-r16 indicates the max number of semi-persistent SRS resources for positioning supported by UE per BWP;
  • - maxNumberSP-SRS-PosResourcesPerBWP-PerSlot-r16 indicates the max number of semi-persistent SRS resources for positioning supported by UE per BWP per slot
| FS | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----|--------------|--------------| +| scalingFactor
Indicates the scaling factor to be applied to the band in the max data rate calculation as defined in 4.1.2. Value f0p4 indicates the scaling factor 0.4, f0p75 indicates 0.75, and so on. If absent, the scaling factor 1 is applied to the band in the max data rate calculation. | FS | No | N/A | N/A | +| cbgPUSCH-ProcessingType1-DifferentTB-PerSlot-r16
Defines whether the UE capable of processing time capability 1 supports CBG based transmission with one or with up to two or with up to four or with up to seven unicast PUSCHs per slot per CC. | FS | No | N/A | N/A | +| cbgPUSCH-ProcessingType2-DifferentTB-PerSlot-r16
Defines whether the UE capable of processing time capability 2 supports CBG based transmission with one or with up to two or with up to four or with up to seven unicast PUSCHs per slot per CC. | FS | No | N/A | N/A | +| supportedSRS-Resources
Defines support of SRS resources. The capability signalling comprising indication of:
  • - maxNumberAperiodicSRS-PerBWP indicates supported maximum number of aperiodic SRS resources that can be configured for the UE per each BWP
  • - maxNumberAperiodicSRS-PerBWP-PerSlot indicates supported maximum number of aperiodic SRS resources per slot in the BWP
  • - maxNumberPeriodicSRS-PerBWP indicates supported maximum number of periodic SRS resources per BWP
  • - maxNumberPeriodicSRS-PerBWP-PerSlot indicates supported maximum number of periodic SRS resources per slot in the BWP
  • - maxNumberSemiPersistentSRS-PerBWP indicate supported maximum number of semi-persistent SRS resources that can be configured for the UE per each BWP
  • - maxNumberSemiPersistentSRS-PerBWP-PerSlot indicates supported maximum number of semi-persistent SRS resources per slot in the BWP
  • - maxNumberSRS-Ports-PerResource indicates supported maximum number of SRS antenna port per each SRS resource.
If this field is not included, the UE supports one periodic, one aperiodic, no semi-persistent SRS resources per BWP and one periodic, one aperiodic, no semi-persistent SRS resources per BWP per slot and one SRS antenna port per SRS resource. | FS | FD | N/A | N/A | +| tdcpNumberDelayValue-r18
Indicates whether the UE supports number Y>1 of delay values for which TDCP is reported.
A UE supporting this feature shall also indicate support of FG40-3-3-1. | FS | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----|--------------|--------------| +| scalingFactor
Indicates the scaling factor to be applied to the band in the max data rate calculation as defined in 4.1.2. Value f0p4 indicates the scaling factor 0.4, f0p75 indicates 0.75, and so on. If absent, the scaling factor 1 is applied to the band in the max data rate calculation. | FS | No | N/A | N/A | +| cbgPUSCH-ProcessingType1-DifferentTB-PerSlot-r16
Defines whether the UE capable of processing time capability 1 supports CBG based transmission with one or with up to two or with up to four or with up to seven unicast PUSCHs per slot per CC. | FS | No | N/A | N/A | +| cbgPUSCH-ProcessingType2-DifferentTB-PerSlot-r16
Defines whether the UE capable of processing time capability 2 supports CBG based transmission with one or with up to two or with up to four or with up to seven unicast PUSCHs per slot per CC. | FS | No | N/A | N/A | +| twoHARQ-ACK-Codebook-type1-r16
Indicates whether the UE supports two HARQ-ACK codebooks with up to one subslot based HARQ-ACK codebook (i.e. slot-based + slot-based, or slot-based + subslot based) simultaneously constructed for supporting HARQ-ACK codebooks with different priorities at a UE. The capability signalling comprises the following parameters:
  • - sub-SlotConfig-NCP-r16 indicates the maximum number of actual PUCCH transmissions for HARQ-ACK within a slot for NCP with 2-symbol*7 sub-slot configuration;
  • - sub-SlotConfig-ECP-r16 indicates the maximum number of actual PUCCH transmissions for HARQ-ACK within a slot for ECP with 2-symbol*6 sub-slot configuration;
For the 7-symbol*2 sub-slot configuration of NCP or the 6-symbol*2 sub-slot configuration of ECP, the value of the maximum number of actual PUCCH transmissions for HARQ-ACK within a slot is {2}.
NOTE 1: If the UE indicates support of this feature and is simultaneously configured with two slot-based HARQ-ACK codebooks:
  • - whether the UE supports two PUCCH of format 0 or 2 in consecutive symbols in the same slot for each HARQ-ACK codebook is subject to the capability reported by twoPUCCH-F0-2-ConsecSymbols.
  • - whether the UE supports one PUCCH format 0 or 2 and one PUCCH format 1, 3 or 4 in the same slot for each HARQ-ACK codebook is subject to the capability reported by onePUCCH-LongAndShortFormat.
  • - whether the UE supports two PUCCH transmissions in the same slot for each HARQ-ACK codebook not covered by twoPUCCH-F0-2-ConsecSymbols and onePUCCH-LongAndShortFormat is subject to the capability reported by twoPUCCH-AnyOthersInSlot.
NOTE 2: If a UE reports both multiPUCCH-r16 and twoHARQ-ACK-Codebook-type1-r16 , it can support two slot-based HARQ-ACK codebooks, and one slot-based and one sub-slot-based HARQ-ACK codebooks. If a UE reports twoHARQ-ACK-Codebook-type1-r16 but does not report multiPUCCH-r16 , it can only support two slot-based HARQ-ACK codebooks. | FS | No | N/A | N/A | +| twoHARQ-ACK-Codebook-type2-r16
Indicates whether the UE supports two subslot based HARQ-ACK codebooks simultaneously constructed for supporting HARQ-ACK codebooks with different priorities at a UE. The capability signalling comprises the following parameters:
  • - sub-SlotConfig-NCP-r16 indicates the maximum number of actual PUCCH transmissions for HARQ-ACK within a slot for NCP with 2-symbol*7 sub-slot configuration;
  • - sub-SlotConfig-ECP-r16 indicates the maximum number of actual PUCCH transmissions for HARQ-ACK within a slot for ECP with 2-symbol*6 sub-slot configuration;
For the 7-symbol*2 sub-slot configuration of NCP or the 6-symbol*2 sub-slot configuration of ECP, the value of the maximum number of actual PUCCH transmissions for HARQ-ACK within a slot is {2}. | FS | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----|--------------|--------------| +| scalingFactor
Indicates the scaling factor to be applied to the band in the max data rate calculation as defined in 4.1.2. Value f0p4 indicates the scaling factor 0.4, f0p75 indicates 0.75, and so on. If absent, the scaling factor 1 is applied to the band in the max data rate calculation. | FS | No | N/A | N/A | +| cbgPUSCH-ProcessingType1-DifferentTB-PerSlot-r16
Defines whether the UE capable of processing time capability 1 supports CBG based transmission with one or with up to two or with up to four or with up to seven unicast PUSCHs per slot per CC. | FS | No | N/A | N/A | +| cbgPUSCH-ProcessingType2-DifferentTB-PerSlot-r16
Defines whether the UE capable of processing time capability 2 supports CBG based transmission with one or with up to two or with up to four or with up to seven unicast PUSCHs per slot per CC. | FS | No | N/A | N/A | +| twoPUCCH-Group
Indicates whether two PUCCH group in CA with a same numerology across CCs for data and control channel [at a given time] is supported by the UE. For NR CA, two PUCCH group is supported with the same numerology across NR carriers for data and control channel at a given time. For (NG)EN-DC/NE-DC, two PUCCH group is supported with the same numerology across NR carriers for data and control channel at a given time, wherein an NR PUCCH group is configured in FR1 and another NR PUCCH group is configured in FR2. The UE supports two PUCCH groups with PUCCH on a band X and a band Y if it sets this capability parameter for both band X and band Y. | FS | No | N/A | N/A | +| twoPUCCH-Type1-r16
Indicates whether the UE supports two PUCCH of format 0 or 2 in the same subslot for a single 7*2-symbol subslot based HARQ-ACK codebook. | FS | No | N/A | N/A | +| twoPUCCH-Type2-r16
Indicates whether the UE supports two PUCCH of format 0 or 2 in consecutive symbols in the same subslot for a single 2*7-symbol subslot based HARQ-ACK codebook. | FS | No | N/A | N/A | +| twoPUCCH-Type3-r16
Indicates whether the UE supports one PUCCH format 0 or 2 and one PUCCH format 1, 3 or 4 in the same subslot for a single 2*7-symbol HARQ-ACK codebook. | FS | No | N/A | N/A | +| twoPUCCH-Type4-r16
Indicates whether the UE supports two PUCCH transmissions in the same subslot for a single 2*7-symbol HARQ-ACK codebook which are not covered by twoPUCCH-Type2-r16 and twoPUCCH-Type3-r16 . | FS | No | N/A | N/A | +| twoPUCCH-Type5-r16
Indicates whether the UE supports two PUCCH of format 0 or 2 for two HARQ-ACK codebooks with one 7*2-symbol subslot based HARQ-ACK codebook and one slot based HARQ-ACK codebook. | FS | No | N/A | N/A | +| twoPUCCH-Type6-r16
Indicates whether the UE supports two PUCCH of format 0 or 2 in consecutive symbols in the same subslot for two HARQ-ACK codebooks with one 2*7-symbol subslot based HARQ-ACK codebook and one slot based HARQ-ACK codebook. | FS | No | N/A | N/A | +| twoPUCCH-Type7-r16
Indicates whether the UE supports two PUCCH of format 0 or 2 in consecutive symbols in the same subslot for two subslot based HARQ-ACK codebooks. | FS | No | N/A | N/A | +| twoPUCCH-Type8-r16
Indicates whether the UE supports one PUCCH format 0 or 2 and one PUCCH format 1, 3 or 4 in the same subslot for two HARQ-ACK codebooks with one 2*7-symbol subslot based HARQ-ACK codebook and one slot based HARQ-ACK codebook. | FS | No | N/A | N/A | +| twoPUCCH-Type9-r16
Indicates whether the UE supports one PUCCH format 0 or 2 and one PUCCH format 1, 3 or 4 in the same subslot for two subslot based HARQ-ACK codebooks. | FS | No | N/A | N/A | +| twoPUCCH-Type10-r16
Indicates whether the UE supports two PUCCH transmissions in the same subslot for two HARQ-ACK codebooks with one 2*7-symbol subslot and one slot based HARQ-ACK codebook which are not covered by twoPUCCH-Type6-r16 and twoPUCCH-Type8-r16 . | FS | No | N/A | N/A | +| twoPUCCH-Type11-r16
Indicates whether the UE supports two PUCCH transmissions in the same subslot for two subslot based HARQ-ACK codebooks which are not covered by twoPUCCH-Type7-r16 and twoPUCCH-Type9-r16 . | FS | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----|--------------|--------------| +| scalingFactor
Indicates the scaling factor to be applied to the band in the max data rate calculation as defined in 4.1.2. Value f0p4 indicates the scaling factor 0.4, f0p75 indicates 0.75, and so on. If absent, the scaling factor 1 is applied to the band in the max data rate calculation. | FS | No | N/A | N/A | +| cbgPUSCH-ProcessingType1-DifferentTB-PerSlot-r16
Defines whether the UE capable of processing time capability 1 supports CBG based transmission with one or with up to two or with up to four or with up to seven unicast PUSCHs per slot per CC. | FS | No | N/A | N/A | +| cbgPUSCH-ProcessingType2-DifferentTB-PerSlot-r16
Defines whether the UE capable of processing time capability 2 supports CBG based transmission with one or with up to two or with up to four or with up to seven unicast PUSCHs per slot per CC. | FS | No | N/A | N/A | +| txDiversity2Tx-r18
Indicates whether the UE supports 2Tx Tx diversity for the band configured. This capability is applicable for both single band (non-CA) case and CA case. | FS | No | N/A | FR1 only | +| txDiversity4Tx-r18
Indicates whether the UE supports Tx diversity for 4Tx for the band configured. This capability is applicable for both single band (non-CA) case and CA case. | FS | No | N/A | FR1 only | +| tx-Support-UL-GapFR2-r17
Indicates whether the UE supports UL transmission in FR2 bands within an FR2 UL gap when the FR2 UL gap is activated in inter-band UL CA. The UE which indicates support for tx-Support-UL-GapFR2-r17 shall also indicate support for ul-GapFR2-r17 in an FR2 band. | FS | No | No | FR2 only | +| ue-PowerClassPerBandPerBC-r17
Indicates the UE power class per band per band combination. | FS | No | N/A | FR1 only | +| NOTE: Void. | | | | | +| ul-CancellationCrossCarrier-r16
Indicates whether the UE supports UL cancellation scheme for cross-carrier comprised of the following functional components:
  • - Supports group common DCI (i.e. DCI format 2_4) for cancellation indication on a different DL CC than that scheduling PUSCH or SRS;
  • - UL cancellation for PUSCH. Cancellation is applied to each PUSCH repetition individually in case of PUSCH repetitions;
  • - UL cancellation for SRS symbols that overlap with the cancelled symbols.
| FS | No | N/A | N/A | +| ul-CancellationSelfCarrier-r16
Indicates whether the UE supports UL cancellation scheme for self-carrier comprised of the following functional components:
  • - Supports group common DCI (i.e. DCI format 2_4) for cancellation indication on the same DL CC as that scheduling PUSCH or SRS;
  • - UL cancellation for PUSCH. Cancellation is applied to each PUSCH repetition individually in case of PUSCH repetitions;
  • - UL cancellation for SRS symbols that overlap with the cancelled symbols.
| FS | No | N/A | N/A | +| ul-DMRS-SingleDCI-M-TRP-r18
Indicates whether the UE supports UL DMRS with Single-DCI based M-TRP. | FS | No | N/A | N/A | +| ul-DMRS-M-DCI-M-TRP-r18
Indicates whether the UE supports UL DMRS with M-DCI based M-TRP. | FS | No | N/A | N/A | +| ul-FullPwrMode-r16
Indicates the UE support of UL full power transmission mode of fullpower as specified in clause 7.1 of TS 38.213 [11]. If the UE indicates this capability the UE also indicates the support of codebook based PUSCH MIMO transmission using mimo-CB-PUSCH and the support of PUSCH codebook coherency subset using pusch-TransCoherence . | FS | No | N/A | N/A | +| ul-FullPwrMode1-r16
Indicates the UE support of UL full power transmission mode of fullpowerMode1 . If the UE indicates this capability the UE also indicates the support of codebook based PUSCH MIMO transmission using mimo-CB-PUSCH and the support of PUSCH codebook coherency subset using pusch-TransCoherence . | FS | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----|--------------|--------------| +| scalingFactor
Indicates the scaling factor to be applied to the band in the max data rate calculation as defined in 4.1.2. Value f0p4 indicates the scaling factor 0.4, f0p75 indicates 0.75, and so on. If absent, the scaling factor 1 is applied to the band in the max data rate calculation. | FS | No | N/A | N/A | +| cbgPUSCH-ProcessingType1-DifferentTB-PerSlot-r16
Defines whether the UE capable of processing time capability 1 supports CBG based transmission with one or with up to two or with up to four or with up to seven unicast PUSCHs per slot per CC. | FS | No | N/A | N/A | +| cbgPUSCH-ProcessingType2-DifferentTB-PerSlot-r16
Defines whether the UE capable of processing time capability 2 supports CBG based transmission with one or with up to two or with up to four or with up to seven unicast PUSCHs per slot per CC. | FS | No | N/A | N/A | +| ul-FullPwrMode2-MaxSRS-ResInSet-r16
Indicates the UE support of the maximum number of SRS resources in one SRS resource set with usage set to 'codebook' for uplink full power Mode 2 operation. If the UE indicates this capability the UE also indicates the support of codebook based PUSCH MIMO transmission using mimo-CB-PUSCH and the support of PUSCH codebook coherency subset using pusch-TransCoherence . A UE supports this feature shall support at least full power operation with single port. | FS | No | N/A | N/A | +| ul-FullPwrMode2-SRSConfig-diffNumSRSPorts-r16
Indicates the UE supported SRS configuration with different number of antenna ports per SRS resource for uplink full power Mode 2 operation. The possible different number of antenna ports that can be configured for a SRS resource are as follow:
  • - value p1-2 means that each SRS resource can be configured with 1 port or 2 ports
  • - value p1-4 means that each SRS resource can be configured with 1 port or 4 ports
  • - value p1-2-4 means that each SRS resource can be configured with 1 port or 2 ports or 4 ports
UE indicates support of this feature shall also indicate support of ul-FullPwrMode2-MaxSRS-ResInSet .
NOTE: The values p1-2 , p1-4 or p1-2-4 can be used if ul-FullPwrMode2-MaxSRS-ResInSet is reported as n2 or n4 . | FS | No | N/A | N/A | + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----|--------------|--------------| +| scalingFactor
Indicates the scaling factor to be applied to the band in the max data rate calculation as defined in 4.1.2. Value f0p4 indicates the scaling factor 0.4, f0p75 indicates 0.75, and so on. If absent, the scaling factor 1 is applied to the band in the max data rate calculation. | FS | No | N/A | N/A | +| cbgPUSCH-ProcessingType1-DifferentTB-PerSlot-r16
Defines whether the UE capable of processing time capability 1 supports CBG based transmission with one or with up to two or with up to four or with up to seven unicast PUSCHs per slot per CC. | FS | No | N/A | N/A | +| cbgPUSCH-ProcessingType2-DifferentTB-PerSlot-r16
Defines whether the UE capable of processing time capability 2 supports CBG based transmission with one or with up to two or with up to four or with up to seven unicast PUSCHs per slot per CC. | FS | No | N/A | N/A | +| ul-FullPwrMode2-TPMIGroup-r16
Indicates the UE supported TPMI group(s) which delivers full power. The capability signalling comprises the following values:
  • - twoPorts-r16 indicates a 2-bit bitmap, where the leading / leftmost bit (bit 0) corresponds to {TPMI index = 0}. The next bit (bit 1) corresponds to {TPMI index = 1} and the TPMI index is as specified in Table 6.3.1.5-1 of TS 38.211 [6]
  • - fourPortsNonCoherent-r16 indicates the TPMI groups {G0-3}
  • - fourPortsPartialCoherent-r16 indicates the TPMI groups {G0-6}
UE indicates support of this feature shall also indicate support of ul-FullPwrMode2-MaxSRS-ResInSet .
Definition of G0~G6 can be found in the table below: | FS | No | N/A | N/A | + + + +| ID | TPMI groups | +|----|-------------| +| G0 | 0 | +| G1 | 0 1 | +| G2 | 0 1 2 | +| G3 | 0 1 2 3 | +| G4 | 0 1 | +| G5 | 0 1 2 3 | +| G6 | 0 1 2 3 4 5 | + +NOTE 1: When a full coherent UE operates in mode 2, it reports TPMIs the same as a partial-coherent UE. + +NOTE 2: For 4 port partial-coherent or full-coherent UE, UE can report: 2-port {2-bit bitmap} and one of 4-port non-coherent {G0~G3} and one of 4-port partial-coherent {G0~G6} +For 4 port non-coherent UE, UE can report: 2-port {2-bit bitmap} and one + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----|--------------|--------------| +| scalingFactor
Indicates the scaling factor to be applied to the band in the max data rate calculation as defined in 4.1.2. Value f0p4 indicates the scaling factor 0.4, f0p75 indicates 0.75, and so on. If absent, the scaling factor 1 is applied to the band in the max data rate calculation. | FS | No | N/A | N/A | +| cbgPUSCH-ProcessingType1-DifferentTB-PerSlot-r16
Defines whether the UE capable of processing time capability 1 supports CBG based transmission with one or with up to two or with up to four or with up to seven unicast PUSCHs per slot per CC. | FS | No | N/A | N/A | +| cbgPUSCH-ProcessingType2-DifferentTB-PerSlot-r16
Defines whether the UE capable of processing time capability 2 supports CBG based transmission with one or with up to two or with up to four or with up to seven unicast PUSCHs per slot per CC. | FS | No | N/A | N/A | +| ul-IntraUE-Mux-r16
Indicates whether the UE supports intra-UE multiplexing/prioritization of overlapping PUCCH/PUCCH and PUCCH/PUSCH with two priority levels in the physical layer. This field includes the following parameters:
  • - pusch-PreparationLowPriority-r16 indicates the additional number of symbols needed beyond the PUSCH preparation time for cancelling a low priority UL transmission;
  • - pusch-PreparationHighPriority-r16 indicates the additional number of the preparation time needed for the high priority UL transmission that cancels a low priority UL transmission.
The value sym0 denotes 0 symbol, sym1 denotes one symbol, and so on. | FS | No | N/A | N/A | +| ul-MCS-TableAlt-DynamicIndication
Indicates whether the UE supports dynamic indication of MCS table using MCS-C-RNTI for PUSCH. | FS | No | N/A | N/A | +| zeroSlotOffsetAperiodicSRS
Indicates whether the UE supports 0 slot offset between aperiodic SRS triggering and transmission, for SRS for CB PUSCH and antenna switching on FR1. | FS | No | N/A | N/A | + +#### 4.2.7.8 *FeatureSetUplinkPerCC* parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| channelBW-90mhz
Indicates whether the UE supports the channel bandwidth of 90 MHz.

For FR1, the UE shall indicate support according to TS 38.101-1 [2], Table 5.3.5-1. | FSPC | CY | N/A | FR1 only | +| codebook1-8TxPUSCH-r18
Indicates whether the UE supports (N1, N2) codebook-based 8Tx PUSCH—codebook1.
Value n4-1 corresponds to (4,1) codebook, value n2-2 corresponds to (2,2) codebook, value both corresponds to both codebooks.
A UE supporting this feature shall also indicate support of FG40-7-1. | FSPC | No | N/A | N/A | +| codebook2-8TxPUSCH-r18
Indicates whether the UE supports codebook-based 8Tx PUSCH—codebook2.
A UE supporting this feature shall also indicate support of FG40-7-1. | FSPC | No | N/A | N/A | +| codebook3-8TxPUSCH-r18
Indicates whether the UE supports codebook-based 8Tx PUSCH—codebook3.
A UE supporting this feature shall also indicate support of FG40-7-1. | FSPC | No | N/A | N/A | +| codebook4-8TxPUSCH-r18
Indicates whether the UE supports codebook-based 8Tx PUSCH—codebook4.
A UE supporting this feature shall also indicate support of FG40-7-1. | FSPC | No | N/A | N/A | +| maxNumberMIMO-LayersNonCB-PUSCH
Defines supported maximum number of MIMO layers at the UE for PUSCH transmission using non-codebook precoding.
A UE supporting non-codebook based PUSCH transmission shall indicate support of maxNumberMIMO-LayersNonCB-PUSCH and mimo-NonCB-PUSCH together. | FSPC | No | N/A | N/A | +| mimo-CB-PUSCH
Indicates whether the UE supports codebook based PUSCH MIMO Transmission. If supported, it includes 2 parameters as follows:
  • - maxNumberMIMO-LayersCB-PUSCH defines supported maximum number of MIMO layers at the UE for PUSCH transmission with codebook precoding.
  • - maxNumberSRS-ResourcePerSet defines the maximum number of SRS resources per SRS resource set configured for codebook based transmission to the UE.
A UE indicating support of this feature shall also indicate support of pusch-TransCoherence . | FSPC | No | N/A | N/A | +| mimo-NonCB-PUSCH
Indicates whether the UE supports non-codebook based PUSCH MIMO Transmission. If supported, it includes 2 parameters as follows:
  • - maxNumberSimultaneousSRS-ResourceTx defines the maximum number of simultaneous transmitted SRS resources at one symbol for non-codebook based transmission to the UE.
  • - maxNumberSRS-ResourcePerSet defines the maximum number of SRS resources per SRS resource set configured for non-codebook based transmission to the UE.
| FSPC | No | N/A | N/A | +| mTRP-PUSCH-RepetitionTypeB-r17
Indicates whether the UE supports multi-TRP PUSCH repetition for non-codebook based PUSCH repetition type B with sequential mapping for repetitions larger than 2 and cyclic mapping for 2 repetitions by indicating the supported number of SRS resources in one SRS resource set. The UE shall also support two SRS resource sets with usage set to 'nonCodebook'. The UE indicating support of this feature shall also indicate support of maxNumberMIMO-LayersNonCB-PUSCH , mimo-NonCB-PUSCH and pusch-RepetitionTypeB-r16 . | FSPC | No | N/A | N/A | +| mTRP-PUSCH-TypeB-CB-r17
Indicates the support of multi-TRP PUSCH repetition based on codebook with PUSCH repetition type B. The value indicates the number of SRS resources in one SRS resource set.
This feature includes the following features:
  • - sequential mapping for repetitions larger than 2.
  • - cyclic mapping for 2 repetitions.
  • - two SRS resource sets with usage set to 'codebook'.
The UE indicating support of this feature shall also indicate the support of mimo-CB-PUSCH and pusch-RepetitionTypeB-r16 . | FSPC | No | N/A | N/A | + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|-----|----------| +|

pusch-CB-SingleDCI-STx2P-SDM-r18
Indicates whether the UE supports 1) Dynamic switching by DCI 0_1/0_2 between single-DCI STxMP SDM and sTRP for PUSCH—codebook; 2) 1 PTRS port for single-DCI based STx2P SDM scheme for PUSCH—codebook 3) Support of two SRS resource sets with usage set to 'codebook'. The feature also comprises following parameters:

  • - maxNumberSRS-ResourcePerSet-r18 indicates the maximum number of SRS resources in one SRS resource set. If value 4 is reported, UE also reports value 4 in ul-FullPwrMode2-MaxSRS-ResInSet.
  • - maxNumberLayerPerPanel-r18 indicates the maximum number of layers of each panel for Single-DCI STx2P with SDM
  • - maxNumberNZP-PUSCH-PortsPerSet-r18 indicates the max number of NZP PUSCH ports associated with one SRS resource set. If a row of the TPMI consists of all 0's, the corresponding PUSCH port is not counted.
  • - maxNumberSRS-AntennaPortsPerSet-r18 indicates the maximum number of SRS antenna ports for each SRS resource in each SRS resource set.

A UE indicating support of this feature shall also indicate support of mimo-CB-PUSCH.

| FSPC | No | N/A | FR2 only | +|

pusch-CB-SingleDCI-STx2P-SFN-r18
Indicates whether the UE supports 1) Dynamic switching by DCI 0_1/0_2 between single-DCI STxMP SFN and sTRP; 2) 1 PTRS port for single-DCI based STx2P SFN scheme for PUSCH—codebook; 3) Support of two SRS resource sets with usage set to 'codebook'. The feature also comprises following parameters:

  • - maxNumberSRS-ResourcePerSet-r18 indicates the maximum number of SRS resources in one SRS resource set. If value 4 is reported, UE also reports value 4 in ul-FullPwrMode2-MaxSRS-ResInSet.
  • - maxNumberLayerPerSet-r18 indicates the maximum number of MIMO layers of each SRS resource set for CB PUSCH with SFN scheme
  • - maxNumberSRS-AntennaPortsPerSet-r18 indicates the maximum number of SRS antenna ports for each SRS resource in each SRS resource set.
  • - maxNumberNZP-PUSCH-PortsPerSet-r18 indicates the max number of NZP PUSCH ports associated with one SRS resource set. If a row of the TPMI consists of all 0's, the corresponding PUSCH port is not counted.

A UE indicating support of this feature shall also indicate support of mimo-CB-PUSCH.

| FSPC | No | N/A | FR2 only | +|

pusch-NonCB-SingleDCI-STx2P-SDM-r18
Indicates whether the UE supports: 1) Dynamic switching by DCI 0_1/0_2 between single-DCI STxMP SDM and sTRP for PUSCH—noncodebook, 2) 1 PTRS port for single-DCI based STx2P SDM scheme for PUSCH—noncodebook, 3) Support of two SRS resource sets with usage set to 'noncodebook'. The feature also comprises following parameters:

  • - maxNumberSRS-ResourcePerSet-r18 indicates the maximum number of SRS resources in one SRS resource set.
  • - maxNumberLayerPerPanel-r18 indicates the maximum number of layers of each panel for Single-DCI STx2P with SDM.
  • - maxNumberSimulSRS-ResourcePerSet-r18 indicates the Maximum number of simultaneous transmitted SRS resources from one SRS resource set at one symbol.

A UE indicating support of this feature shall also indicate support of mimo-NonCB-PUSCH.

| FSPC | No | N/A | FR2 only | +|

pusch-NonCB-SingleDCI-STx2P-SFN-r18
Indicates whether the UE supports: 1) Dynamic switching by DCI 0_1/0_2 between single-DCI STxMP SFN and sTRP, 2) 1 PTRS port for single-DCI based STx2P SFN scheme for PUSCH—noncodebook, 3) Support of two SRS resource sets with usage set to 'noncodebook'. The feature also comprises following parameters:

  • - maxNumberSRS-ResourcePerSet-r18 indicates the maximum number of SRS resources in one SRS resource set.
  • - maxNumberLayerPerSet-r18 indicates the maximum number of MIMO layers of each SRS resource set for NCB PUSCH with SFN scheme.
  • - maxNumberSimulSRS-ResourcePerSet-r18 indicates the Maximum number of simultaneous transmitted SRS resources from one SRS resource set at one symbol.

A UE indicating support of this feature shall also indicate support of mimo-NonCB-PUSCH.

| FSPC | No | N/A | FR2 only | + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|-----|-----| +|

supportedBandwidthUL, supportedBandwidthUL-v1710
Indicates maximum UL channel bandwidth supported for a given SCS that UE supports within a single CC (and in case of DAPS handover for the source or target cell), which is defined in Table 5.3.5-1 in TS 38.101-1 [2] for FR1 and Table 5.3.5-1 in TS 38.101-2 [3] for FR2.
For FR1, all the bandwidths listed in TS 38.101-1 [2], Table 5.3.5-1 for each band shall be mandatory with a single CC unless indicated optional. For FR2, the set of mandatory CBW is 50, 100, 200 MHz. When this field is included in a band combination with a single band entry and a single CC entry (i.e. non-CA band combination), the UE shall indicate the maximum channel bandwidth for the band according to TS 38.101-1 [2] and TS 38.101-2 [3]. For FR2, supportedBandwidthUL-v1710 is included if the maximum UL channel bandwidth supported by the UE within a single CC is greater than 400MHz. When the supportedBandwidthUL and the supportedBandwidthUL-v1710 are reported together for a CC, the network which is able to decode the supportedBandwidthUL-v1710 ignores the supportedBandwidthUL.

The UE may report a supportedBandwidthUL wider than the channelBWs-UL; this supportedBandwidthUL may not be included in the Table 5.3.5-1 of TS 38.101-1 [2]/TS 38.101-2 [3] for the case that the UE is unable to report the actual supported bandwidth according to the Table 5.3.5-1 of TS 38.101-1 [2]/TS 38.101-2 [3]. For each band, (e)RedCap UEs shall indicate its maximum channel bandwidth, which is the maximum of those channel bandwidths that are less than or equal to 20 MHz for FR1 and less than or equal to 100 MHz for FR2, taking restrictions in TS 38.101-1 [2] and TS 38.101-2 [3] into consideration.

NOTE: To determine whether the UE supports a channel bandwidth of 90 MHz the network may ignore this capability and validate instead the channelBW-90mhz, the supportedBandwidthCombinationSet and the supportedBandwidthCombinationSetIntraENDC. To determine whether the UE supports a channel bandwidth of 400 MHz, the network validates this capability, the supportedBandwidthCombinationSet, and the supportedBandwidthCombinationSetIntraENDC. For serving cell(s) with other channel bandwidths the network validates the channelBWs-UL, the supportedBandwidthCombinationSet, the supportedBandwidthCombinationSetIntraENDC, the asymmetricBandwidthCombinationSet (for a band supporting asymmetric channel bandwidth as defined in clause 5.3.6 of TS 38.101-1 [2]), supportedBandwidthUL/supportedBandwidthUL-v1710 and supportedMinBandwidthUL.

| FSPC | CY | N/A | N/A | +|

supportedMinBandwidthUL-r17
Indicates minimum UL channel bandwidth supported for a given SCS that UE supports within a single CC (and in case of intra-frequency DAPS handover for the source and target cells), which is defined in Table 5.3.5-1 in TS 38.101-1 [2] for FR1 and Table 5.3.5-1 in TS 38.101-2 [3] for FR2. This parameter is only applicable to the Bandwidth Combination Set 5. This field does not restrict the bandwidths configured for a single CC (i.e. non-CA case).

| FSPC | CY | N/A | N/A | +|

supportedModulationOrderUL
Indicates the maximum supported modulation order to be applied for uplink in the carrier in the max data rate calculation as defined in 4.1.2. If included, the network may use a modulation order on this serving cell which is higher than the value indicated in this field as long as UE supports the modulation of higher value for uplink. If not included,

  • - for FR1 and FR2, the network uses the modulation order signalled per band i.e. pusch-256QAM if signalled. If not signalled in a given band, the network shall use the modulation order 64QAM.

In all the cases, it shall be ensured that the data rate does not exceed the max data rate (DataRate) and max data rate per CC (DataRateCC) according to TS 38.214 [12].

| FSPC | No | N/A | N/A | + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|-----|----------| +|

supportedSubCarrierSpacingUL
Defines the supported sub-carrier spacing for UL by the UE, as defined in 4.2-1 of TS 38.211 [6], indicating the UE supports simultaneous transmission with same or different numerologies in CA, or indicating the UE supports different numerologies on NR UL and SUL within one cell. Support of simultaneous transmissions with same numerology for intra-band NR CA including both contiguous and non-contiguous is mandatory with capability in both FR1 and FR2. Support of simultaneous transmission with two different numerologies between FR1 band(s) and FR2 band(s) in UL is mandatory with capability if UE supports inter-band NR CA including both FR1 band(s) and FR2 band(s). Support of simultaneous transmission with different numerologies in CA for other cases is optional.

| FSPC | CY | N/A | N/A | +|

twoPUSCH-CB-MultiDCI-STx2P-DG-DG-r18
Indicates whether the UE supports multi-DCI based STx2P PUSCH+PUSCH for codebook-based PUSCH with fully overlapping PUSCHs in time and overlapping in frequency and two SRS resource sets with usage set to 'codebook' associated with two coresetPoolIndex values.

  • - maxNumberSRS-ResourcePerSet-r18 indicates the maximum number of SRS resources in one SRS resource set. If value n4 is reported, the UE also reports value n4 in ul-FullPwrMode2-MaxSRS-ResInSet-r16.
  • - maxNumberLayerOverlapping-r18 indicates the maximum number of layers of each PUSCH of PUSCH+PUSCH overlapping in time domain.
  • - maxNumberNZP-PUSCH-Overlapping-r18 indicates the maximum number of NZP PUSCH ports for each PUSCH of PUSCH+PUSCH overlapping in time domain.
  • - maxNumberPUSCH-PerCORESET-PerSlot-r18 indicates the maximum number of PUSCHs per CORESETPoolIndex per slot
  • - maxNumberTotalLayerOverlapping-r18 indicates the maximum total number of layers across two overlapping PUSCH.
  • - maxNumberSRS-AntennaPortsPerSet-r18 indicates the maximum number of SRS antenna ports for each SRS resource in each SRS resource set.

A UE supporting this feature shall also indicate support of mimo-CB-PUSCH.

NOTE: Processing support of two SRS resource sets with usage set to 'codebook' associated with two coresetPoolIndex values is not supported in any CC if at least one CC is configured with two values of CORESETPoolIndex.

| FSPC | No | N/A | FR2 only | +|

twoPUSCH-MultiDCI-STx2P-OutOfOrder-r18
Indicates whether the UE supports out-of-order operation for multi-DCI based STx2P PUSCH+PUSCH.

A UE supporting this feature shall also indicate support of twoPUSCH-CB-MultiDCI-STx2P-DG-DG-r18 or twoPUSCH-NonCB-MultiDCI-STx2P-DG-DG-r18.

| FSPC | No | N/A | FR2 only | +|

twoPUSCH-NonCB-MultiDCI-STx2P-DG-DG-r18
Indicates whether the UE supports multi-DCI based STxMP PUSCH+PUSCH for noncodebook-based PUSCH with fully overlapping PUSCHs in time and non-overlapping in frequency and two SRS resource sets with usage set to 'noncodebook' associated with two coresetPoolIndex values.

  • - maxNumberSRS-ResourcePerSet-r18 indicates the maximum number of SRS resources in one SRS resource set.
  • - maxNumberLayerOverlapping-r18 indicates the maximum number of layers of each PUSCH of PUSCH+PUSCH overlapping in time domain.
  • - maxNumberSimulSRS-ResourcePerSet-r18 indicates the maximum number of simultaneously transmitted SRS resources in one symbol per SRS resource set.
  • - maxNumberPUSCH-PerCORESET-PerSlot-r18 indicates the maximum number of PUSCHs per CORESETPoolIndex per slot
  • - maxNumberTotalLayerOverlapping-r18 indicates the maximum total number of layers across two overlapping PUSCH.

A UE supporting this feature shall also indicate support of mimo-NonCB-PUSCH.

NOTE: Processing support of two SRS resource sets with usage set to 'codebook' associated with two coresetPoolIndex values is not supported in any CC if at least one CC is configured with two values of CORESETPoolIndex.

| FSPC | No | N/A | FR2 only | + +#### 4.2.7.9 *MRDC-Parameters* + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|-----|--------------|--------------| +| asynclntraBandENDC
Indicates whether the UE supports asynchronous FDD-FDD intra-band (NG)EN-DC with MRTD and MTTD as specified in clause 7.5 and 7.6 of TS 38.133 [5]. If asynchronous FDD-FDD intra-band (NG)EN-DC is not supported, the UE supports only synchronous FDD-FDD intra-band (NG)EN-DC.

This capability applies to:
  • - Intra-band (NG)EN-DC combination without additional inter-band NR and LTE CA component;
  • - Intra-band (NG)EN-DC combination supporting both UL and DL intra-band (NG)EN-DC parts with additional inter-band NR/LTE CA component;
  • - Intra-band (NG)EN-DC combination without supporting UL in both the bands of the intra-band (NG)EN-DC UL part;
  • - Inter-band (NG)EN-DC combination, where the frequency range of the E-UTRA band is a subset of the frequency range of the NR band (as specified in Table 5.5B.4.1-1 of TS 38.101-3 [4]).
If this capability is included in an "Intra-band (NG)EN-DC combination supporting both UL and DL intra-band (NG)EN-DC parts with additional inter-band NR/LTE CA component" or in an "Intra-band (NG)EN-DC combination without supporting UL in both the bands of the intra-band (NG)EN-DC UL part", this capability applies to the intra-band (NG)EN-DC BC part. | BC | No | FDD only | FR1 only | +| condPSCellAdditionENDC-r17
Indicates whether the UE supports conditional PSCell addition in EN-DC. The UE supporting this feature shall also support 2 trigger events for same execution condition in conditional PSCell addition in EN-DC. | BC | No | N/A | N/A | +| dualPA-Architecture
For an intra-band band combination, this field indicates the support of dual PAs. If absent in an intra-band band combination, the UE supports single PA for all the ULs in the intra-band band combination. For other band combinations, this field is not applicable.

This capability applies to:
  • - Intra-band (NG)EN-DC/NE-DC combination without additional inter-band NR and LTE CA component;
  • - Intra-band (NG)EN-DC/NE-DC combination supporting both UL and DL intra-band (NG)EN-DC/NE-DC parts with additional inter-band NR/LTE CA component;
  • - Inter-band (NG)EN-DC/NE-DC combination, where the frequency range of the E-UTRA band is a subset of the frequency range of the NR band (as specified in Table 5.5B.4.1-1 of TS 38.101-3 [4]).
If this capability is included in an "Intra-band (NG)EN-DC/NE-DC combination supporting both UL and DL intra-band (NG)EN-DC/NE-DC parts with additional inter-band NR/LTE CA component", this capability applies to the intra-band (NG)EN-DC/NE-DC BC part. | BC | No | N/A | N/A | +| dynamicPowerSharingENDC
Indicates whether the UE supports dynamic (NG)EN-DC power sharing between NR FR1 carriers and the LTE carriers. If the UE supports this capability the UE supports the dynamic power sharing behaviour as specified in clause 7 of TS 38.213 [11]. In this release of the specification, the UE supporting (NG)EN-DC shall set this field to supported . | BC | Yes | N/A | FR1 only | +| dynamicPowerSharingNEDC
Indicates whether the UE supports dynamic NE-DC power sharing between NR FR1 carriers and the LTE carriers. If the UE supports this capability, the UE supports the dynamic power sharing behavior as specified in clause 7 of TS 38.213 [11]. | BC | Yes | N/A | FR1 only | +| higherPowerLimitMRDC-r17
Indicates whether UE supports increase in maximum output power above the power class indication for inter-band UL (NG)EN-DC band combinations as defined in clause 6.2B of TS 38.101-3 [4]. | BC | No | N/A | FR1 only | + +| | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|----------|----------| +| intraBandENDC-Support
Indicates whether the UE supports intra-band (NG)EN-DC with only non-contiguous spectrum, or with both contiguous and non-contiguous spectrum for the (NG)EN-DC combination as specified in TS 38.101-3 [4].
If the UE does not include this field for an intra-band (NG)EN-DC combination the UE only supports the contiguous spectrum for the intra-band (NG)EN-DC combination.
If intraBandENDC-Support-UL is absent and the band combination supports intra-band (NG)EN-DC only in DL, this field indicates the DL capability. If intraBandENDC-Support-UL is absent and the band combination supports intra-band (NG)EN-DC in DL and UL, this field indicates the common capability for both DL and UL. If intraBandENDC-Support-UL is included, intraBandENDC-Support indicates the DL capability. | BC | No | N/A | N/A | +| intraBandENDC-Support-UL
Indicates whether the UE supports intra-band (NG)EN-DC in UL with only non-contiguous spectrum, or with both contiguous and non-contiguous spectrum for the intra-band (NG)EN-DC combination as specified in TS 38.101-3 [4]. The UE includes this field only if the UE supports different UL and DL capabilities for the intra-band (NG)EN-DC band combination.
When 'both' is indicated in intraBandENDC-Support and in intraBandENDC-Support-UL , the UE supports the following three cases of intra-band (NG)EN-DC: contiguous DL/contiguous UL, non-contiguous DL/non-contiguous UL, contiguous DL/non-contiguous UL. | BC | No | N/A | N/A | +| interBandContiguousMRDC
Indicates for an inter-band (NG)EN-DC/NE-DC combination, where the frequency range of the E-UTRA band is a subset of the frequency range of the NR band (as specified in Table 5.5B.4.1-1 of TS 38.101-3 [4]), that the UE supports intra-band contiguous (NG)EN-DC/NE-DC requirements (see TS 38.101-3 [4]). If the field is absent for such an inter-band (NG)EN-DC/NE-DC combination, the UE supports intra-band non-contiguous (NG)EN-DC/NE-DC requirements. | BC | CY | N/A | N/A | +| interBandMRDC-WithOverlapDL-Bands-r16
Indicates whether the UE supports FDD-FDD or TDD-TDD inter-band (NG)EN-DC/NE-DC operation with overlapping or partially overlapping DL bands with an (NG)EN-DC MTTD/MRTD according to clause 7.5.2/7.6.2 in TS 38.133 [5] and NE-DC MTTD/MRTD according to clause 7.5.5/7.6.5 in TS 38.133 [5] and inter-band RF requirements. If the capability is not reported, the UE supports FDD-FDD or TDD-TDD inter-band operation with overlapping or partially overlapping DL bands with (NG)EN-DC/NE-DC MTTD/MRTD according to clause 7.5.3/7.6.3 in TS 38.133 [5] and intra-band RF requirements. | BC | No | N/A | FR1 only | +| maxUplinkDutyCycle-interBandENDC-FDD-TDD-PC2-r16
Indicates the maximum percentage of symbols during a certain evaluation period that can be scheduled for NR uplink transmission and EUTRA FDD uplink transmission so as to ensure compliance with applicable electromagnetic energy absorption requirements provided by regulatory bodies. This field is only applicable for inter-band FDD+TDD EN-DC power class 2 UE as specified in TS 38.101-3 [4]. This capability signalling comprises of maxUplinkDutyCycle-FDD-TDD-EN-DC1 and maxUplinkDutyCycle-FDD-TDD-EN-DC2 which indicate the maxUplinkDutyCycle capability of NR band corresponding to different LTE reference configurations as described in TS 38.101-3 [4], clause 6.2B.1.3. Value n30 corresponds to 30%, value n40 corresponds to 40% and so on. | BC | No | N/A | FR1 only | +| maxUplinkDutyCycle-interBandENDC-TDD-PC2-r16
Indicates the maximum percentage of symbols during a certain evaluation period that can be scheduled for NR uplink transmission under different EUTRA TDD uplink-downlink configurations so as to ensure compliance with applicable electromagnetic energy absorption requirements provided by regulatory bodies. This field is only applicable for inter-band TDD+TDD EN-DC power class 2 UE as specified in TS 38.101-3 [4]. If the field is absent, 30% shall be applied to all EUTRA TDD uplink-downlink configurations. If eutra-TDD-Configx is absent, 30% shall be applied to the corresponding EUTRA TDD uplink-downlink configuration. Value n20 corresponds to 20%, value n40 corresponds to 40% and so on. | BC | No | TDD only | FR1 only | +| scg-ActivationDeactivationENDC-r17
Indicates whether the UE supports activation (with or without RACH) and deactivation on SCG in EN-DC, upon SCG addition and upon reconfiguration of the SCG, as specified in TS 38.331 [9]. A UE supporting this feature shall indicate support of EN-DC as specified in TS 36.331 [17]. For the UE supporting this feature, it is mandatory to report maxNumberCSI-RS-BFD and maxNumberSSB-BFD for all NR bands of this band combination where the UE supports SpCell. | BC | No | N/A | N/A | + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|----------| +|

scg-ActivationDeactivationResumeENDC-r17

Indicates whether the UE supports activation (with or without RACH) and deactivation on SCG in EN-DC, upon reception of an RRCReconfiguration included in an RRCConnectionResume message, as specified in TS 38.331 [9] and TS 36.331 [17]. A UE supporting this feature shall indicate support of EN-DC and support of resumeWithSCG-Config-r16 as specified in TS 36.331 [17]. For the UE supporting this feature, it is mandatory to report maxNumberCSI-RS-BFD and maxNumberSSB-BFD for all NR bands of this band combination where the UE supports SpCell.

| BC | No | N/A | N/A | +|

simultaneousRxTxInterBandENDC

Indicates whether the UE supports simultaneous transmission and reception in TDD-TDD and TDD-FDD inter-band (NG)EN-DC/NE-DC. It is mandatory for certain TDD-FDD and TDD-TDD band combinations defined in TS 38.101-3 [4].

This capability does not apply to the following components within TDD-TDD and TDD-FDD inter-band (NG)EN-DC/NE-DC combination:

  • - Intra-band (NG)EN-DC/NE-DC component
  • - Inter-band (NG)EN-DC/NE-DC component where the frequency range of the E-UTRA band is a subset of the frequency range of the NR band (as specified in Table 5.5B.4.1-1 of TS 38.101-3 [4]).
| BC | CY | N/A | N/A | +|

simultaneousRxTxInterBandENDCPerBandPair

Indicates whether the UE supports simultaneous transmission and reception in TDD-TDD and TDD-FDD inter-band (NG)EN-DC/NE-DC for each band pair in the band combination.

Encoded in the same manner as simultaneousRxTxInterBandCAPerBandPair.

The UE does not include this field if the UE supports simultaneous transmission and reception for all applicable band pairs in the band combination (in which case simultaneousRxTxInterBandENDC is included) or does not support for any band pair in the band combination. It is mandatory for certain band pairs as specified in TS 38.101-3 [4]. The UE shall consistently set the bits which correspond to the same band pair.

Each bit of the capability only applies to TDD-TDD and TDD-FDD Inter-band (NG)EN-DC/NE-DC band pairs, except for the band pairs where the frequency range of the E-UTRA band is a subset of the frequency range of the NR band (as specified in Table 5.5B.4.1-1 of TS 38.101-3 [4]).

| BC | CY | N/A | N/A | +|

singleUL-HARQ-offsetTDD-PCell-r16

Indicate support of HARQ offset for single UL transmission in synchronous (NG)EN-DC with LTE TDD PCell. UE indicates support of this feature shall indicate support of tdm-restrictionTDD-endc-r16.

| BC | No | N/A | N/A | +|

singleUL-Transmission

Indicates that the UE does not support simultaneous UL transmissions as defined in TS 38.101-3 [4]. The UE may only include this field for certain band combinations defined in TS 38.101-3 [4]. If included for a particular band combination, the field applies to all fallback band combinations of this band combination that are defined in TS 38.101-3 [4] as being allowed to include this field and does not apply to any other fallback band combinations defined in TS 38.101-3 [4].

The UE shall include this field for band combinations containing a band pair for which single UL transmission is the only specified operation mode in TS 38.101-3 [4] and if the UE supports UL on both bands. Otherwise, this feature is optional.

| BC | FD | N/A | N/A | +|

spCellPlacement

Indicates whether the UE supports a SpCell on FR1-FDD, FR1-TDD and/or FR2-TDD depending on which additional SCells of other frequency range(s) / duplex mode(s) are configured. It is applicable to SCG of (NG)EN-DC and MCG of NE-DC, where UL is configured on more than one of FR1-FDD, FR1-TDD and FR2-TDD in a cell group. If not included, the UE supports SpCell on any serving cell with UL in supported band combinations.

| UE | No | N/A | N/A | +|

tdm-Pattern

Indicates whether the UE supports the tdm-PatternConfig for singleUL-transmission associated functionality, as specified in TS 36.331 [17]. Support is conditionally mandatory in (NG)EN-DC for UEs that do not support dynamicPowerSharingENDC and for UEs that indicate single UL transmission for any (NG)EN-DC BC. Support is conditionally mandatory in NE-DC for UEs that do not support dynamicPowerSharingNEDC and for UEs that indicate single UL transmission for any NE-DC BC. The feature is optional otherwise.

| BC | CY | N/A | FR1 only | + +| | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|-----|----------| +| tdm-restrictionDualTX-FDD-endc-r16
Indicates whether the UE supports TDM restriction to LTE FDD PCell in (NG)EN-DC for dual UL transmission operation when tdm-PatternConfig2-R16 is configured, as specified in TS 36.331 [17]. UE indicates support this feature shall also indicate support of tdm-Pattern . | BC | No | N/A | FR1 only | +| tdm-restrictionFDD-endc-r16
Indicates whether the UE supports TDM restriction to LTE FDD PCell for single UL-transmission associated functionality when tdm-PatternConfig2-R16 is configured, as specified in TS 36.331 [17]. This is applicable for FDD (NG)EN-DC. UE indicates support this feature shall also indicate support of tdm-Pattern . | BC | No | N/A | FR1 only | +| tdm-restrictionTDD-endc-r16
Indicates whether the UE supports TDM restriction to LTE TDD PCell for single UL-transmission associated functionality when tdm-PatternConfig2-R16 is configured, as specified in TS 36.331 [17]. This is applicable for synchronous TDD-TDD (NG)EN-DC. | BC | No | N/A | FR1 only | +| ul-SharingEUTRA-NR
Indicates whether the UE supports (NG)EN-DC/NE-DC with EUTRA-NR coexistence in UL sharing via TDM only, FDM only, or both TDM and FDM from UE perspective as specified in TS 38.101-3 [4]. | BC | No | N/A | FR1 only | +| ul-SwitchingTimeEUTRA-NR
Indicates support of switching type between LTE UL and NR UL for (NG)EN-DC/NE-DC with LTE-NR coexistence in UL sharing from UE perspective as defined in clause 6.3B of TS 38.101-3 [4]. It is mandatory to report switching time type 1 or type 2 if UE reports ul-SharingEUTRA-NR is tdm or both . | BC | CY | N/A | FR1 only | +| ul-TimingAlignmentEUTRA-NR
Indicates whether to apply the same UL timing between NR and LTE for dynamic power sharing capable UE operating in a synchronous intra-band contiguous (NG)EN-DC. If this field is absent, UE shall be capable of handling a timing difference up to applicable MTTC requirements when operating in a synchronous intra-band contiguous (NG)EN-DC network, as specified in TS 38.133 [5].

This capability applies to:
  • - Intra-band contiguous (NG)EN-DC combination without additional inter-band NR and LTE CA component;
  • - Intra-band contiguous (NG)EN-DC combination supporting both UL and DL intra-band (NG)EN-DC parts with additional inter-band NR/LTE CA component;
  • - Inter-band (NG)EN-DC combination, where the frequency range of the E-UTRA band is a subset of the frequency range of the NR band (as specified in Table 5.5B.4.1-1 of TS 38.101-3 [4]).
If this capability is included in an "Intra-band contiguous (NG)EN-DC combination supporting both UL and DL intra-band (NG)EN-DC parts with additional inter-band NR/LTE CA component", this capability applies to the intra-band (NG)EN-DC BC part. | BC | No | N/A | N/A | + +#### 4.2.7.10 *Phy-Parameters* + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----|--------------|--------------| +| absoluteTPC-Command
Indicates whether the UE supports absolute TPC command mode. | UE | No | No | Yes | +| additionalSR-Periodicities-r18
Indicates whether the UE supports the following SR periodicities in the periodicityAndOffset parameter as specified in TS 38.331 [9]. The capability signalling comprises the following parameters:
  • - Value scs-30kHz-r18 indicates the support of 5slots for 30 kHz SCS
  • - Value scs-120kHz-r18 indicates the support of 5slots and 10slots for 120 kHz SCS
| UE | No | No | No | +| aggregationFactorSPS-DL-r16
Indicates whether the UE supports configurable PDSCH aggregation factor ({1, 2, 4, 8}) per DL SPS configuration. The UE can include this feature only if the UE indicates support of downlinkSPS . | UE | No | No | Yes | +| almostContiguousCP-OFDM-UL
Indicates whether the UE supports almost contiguous UL CP-OFDM transmissions as defined in clause 6.2 of TS 38.101-1 [2]. | UE | No | No | Yes | +| bwp-SwitchingDelay
Defines whether the UE supports DCI and timer based active BWP switching delay type1 or type2 specified in clause 8.6.2 of TS 38.133 [5]. It is mandatory to report type 1 or type 2 when bwp-SameNumerology or bwp-DiffNumerology is supported on at least one band. This capability is not applicable to IAB-MT. | UE | CY | No | No | +| bwp-SwitchingMultiCCs-r16
Indicates whether the UE supports incremental delay for DCI and timer based active BWP switching on multiple CCs simultaneously as specified in TS 38.133 [5]. The capability signalling comprises of the following:
  • - type1-r16 indicates the delay value for type 1 BWP switching delay and has values of {100us, 200us}
  • - type2-r16 indicates the delay value for type 2 BWP switching delay and has values of {200us, 400us, 800us, 1000us}

The UE indicating support of this feature shall also support bwp-SwitchingDelay, bwp-SameNumerology and/or bwp-DiffNumerology. It is mandatory to report either type1-r16 or type2-r16 for a UE which supports CA.

| UE | CY | No | No | +| bwp-SwitchingMultiDormancyCCs-r16
Indicates whether the UE supports incremental delay for BWP switch processing on additional SCells in DCI based simultaneous dormant BWP switching on multiple SCells as specified in TS 38.133 [5]. The capability signalling comprises of the following:
  • - type1-r16 indicates the delay value for type 1 BWP switching delay and has values of {100us, 200us}
  • - type2-r16 indicates the delay value for type 2 BWP switching delay and has values of {200us, 400us, 800us, 1000us}

The UE indicating support of this feature shall also support scellDormancyWithinActiveTime-r16 or scellDormancyOutsideActiveTime-r16.

| UE | No | No | No | +| cbg-FlushIndication-DL
Indicates whether the UE supports CBG-based (re)transmission for DL using CBG flushing out information (CBGFI) as specified in TS 38.214 [12]. | UE | No | No | No | +| cbg-TransIndication-DL
Indicates whether the UE supports CBG-based (re)transmission for DL using CBG transmission information (CBGTI) as specified in TS 38.214 [12]. | UE | No | No | No | +| cbg-TransIndication-UL
Indicates whether the UE supports both in-order and out-of-order CBG-based (re)transmission for UL using CBG transmission information (CBGTI) as specified in TS 38.214 [12]. | UE | No | No | No | + +| | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|-----|----------|-----| +| cbg-TransInOrderPUSCH-UL-r16
Indicates whether the UE supports CBG-based re-transmission(s) of a TB using CBG transmission information (CBGTI) as specified in TS 38.214 [12] in the following two cases (both are considered as in-order CBG-based retransmission(s)):
1. if the initial PUSCH transmission was not cancelled due to gNB scheduling/indication/configuration; and
2. if the initial PUSCH transmission was cancelled due to gNB scheduling/indication/configuration and the following condition is satisfied: the UE is scheduled for a re-transmission of a CBG #N in a given TB when CBG #N-1 has been transmitted before or is scheduled in the same UL grant that includes CBG#N. | UE | No | No | No | +| cg-TimeDomainAllocationExtension-r17
Indicates whether UE supports the timeDomainAllocation-v1710 configured in rrc-ConfiguredUplinkGrant to indicate 16 or more entries in PUSCH TDRA table. This field is only applicable if the UE supports both pusch-RepetitionTypeB-r16 and either configuredUL-GrantType1 or configuredUL-GrantType1-v1650 . | UE | No | No | No | +| cli-RSSI-FDM-DL-r16
Indicates whether serving cell DL signal/channel (e.g. PDSCH/PDCCH) and CLI-RSSI FDMed reception is supported as specified in TS 38.215 [13]. | UE | No | TDD only | Yes | +| cli-SRS-RSRP-FDM-DL-r16
Indicates whether serving cell DL signal/channel (e.g. PDSCH/PDCCH) and SRS-RSRP FDMed reception is supported as specified in TS 38.215 [13]. | UE | No | TDD only | Yes | +| codebookVariantsList-r16
Indicates the list of SupportedCSI-RS-Resource applicable to the codebook types supported by the UE. | UE | No | No | No | +| configurableType-1A-FieldsForDCI-0-3-And-1-3-r18
Indicates support of Type-1A for 'Antenna port(s)' field for DCI format 1_3 and Type-1A for 'Antenna port(s)', 'Precoding information and number of layers' and 'SRS resource indicator' fields for DCI format 0_3.
The UE indicating support for this feature also indicates support at least one of 49-1, multiCell-PDSCH-DCI-1-3-DiffSCS-r18 , 49-2 or 49-2b | UE | No | No | No | +| configuredUL-GrantType1
Indicates whether the UE supports Type 1 PUSCH transmissions with configured grant as specified in TS 38.214 [12] with UL-TWG-repK value of one. This applies only to non-shared spectrum channel access. For shared spectrum channel access, configuredUL-GrantType1-r16 applies. | UE | No | No | No | +| configuredUL-GrantType2
Indicates whether the UE supports Type 2 PUSCH transmissions with configured grant as specified in TS 38.214 [12] with UL-TWG-repK value of one. This applies only to non-shared spectrum channel access. For shared spectrum channel access, configuredUL-GrantType2-r16 applies. | UE | No | No | No | +| cqi-4-BitsSubbandTN-NonSharedSpectrumChAccess-r17
Indicates whether the UE supports subband CQI reporting with 4 bits per subband for TN and non-shared spectrum channel access. | UE | No | No | No | +| cqi-TableAlt
Indicates whether UE supports the CQI table with target BLER of $10^{-5}$ . | UE | No | No | Yes | +| cri-RI-CQI-WithoutNon-PMI-PortInd-r16
Indicates whether UE supports CSI-ReportConfig with the reportQuantity set to 'cri-RI-CQI' and the non-PMI-PortIndication is not configured.

UE indicating support of this feature shall also indicate support of csi-ReportFramework . | UE | No | No | Yes | +| crossSlotScheduling-r16
Indicates whether UE supports dynamic indication of applicable minimum scheduling restriction by DCI format 0_1 and 1_1, and the minimum scheduling offset for PDSCH and aperiodic CSI-RS triggering offset (K0), and PUSCH (K2), and the extended value range for aperiodic CSI-RS triggering offset. Support of this feature is reported for licensed and unlicensed bands, respectively. When this field is reported, either of non-SharedSpectrumChAccess-r16 or sharedSpectrumChAccess-r16 shall be reported, at least. | UE | No | No | No | +| csi-ReportFramework
See csi-ReportFramework in 4.2.7.2. For a band combination comprised of FR1 and FR2 bands, this parameter, if present, limits the corresponding parameter in MIMO-ParametersPerBand . | UE | Yes | No | N/A | +| csi-ReportFrameworkExt-r16
See csi-ReportFramework in 4.2.7.2. For a band combination comprised of FR1 and FR2 bands, this parameter, if present, limits the corresponding parameter in MIMO-ParametersPerBand . | UE | No | No | N/A | + +| | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|-----|-----|----------| +| csi-ReportWithoutCQI
Indicates whether UE supports CSI reporting with report quantity set to 'CRI/RI/i1' as defined in clause 5.2.1.4 of TS 38.214 [12]. | UE | No | No | Yes | +| csi-ReportWithoutPMI
Indicates whether UE supports CSI reporting with report quantity set to 'CRI/RI/CQI' as defined in clause 5.2.1.4 of TS 38.214 [12]. | UE | No | No | Yes | +| csi-RS-CFRA-ForHO
Indicates whether the UE can perform reconfiguration with sync using a contention free random access with 4-step RA type on PRACH resources that are associated with CSI-RS resources of the target cell. This applies only to non-shared spectrum channel access. For shared spectrum channel access, csi-RS-CFRA-ForHO-r16 applies. | UE | No | No | No | +| csi-RS-IM-ReceptionForFeedback
See csi-RS-IM-ReceptionForFeedback in 4.2.7.2. For a band combination comprised of FR1 and FR2 bands, this parameter, if present, limits the corresponding parameter in MIMO-ParametersPerBand . | UE | Yes | No | N/A | +| csi-RS-ProcFrameworkForSRS
See csi-RS-ProcFrameworkForSRS in 4.2.7.2. For a band combination comprised of FR1 and FR2 bands, this parameter, if present, limits the corresponding parameter in MIMO-ParametersPerBand . | UE | No | No | N/A | +| csi-TriggerStateNon-ActiveBWP-r16
Indicates whether the UE supports CSI trigger states containing non-active BWP. | UE | No | No | No | +| dci-DL-PriorityIndicator-r16
Indicates whether the UE supports the priority indicator field configured in DCI formats 1_1 and 1_2 in a BWP when configured to monitor both DCI formats 1_1 and 1_2 in the BWP. | UE | No | No | No | +| dci-Format1-2And0-2-r16
Indicates whether the UE supports monitoring DCI format 1_2 for DL scheduling and monitoring DCI format 0_2 for UL scheduling. | UE | No | No | No | +| dci-UL-PriorityIndicator-r16
Indicates whether the UE supports the priority indicator field configured in DCI formats 0_1 and 0_2 in a BWP when configured to monitor both DCI formats 0_1 and 0_2 in the BWP. A UE supporting this feature shall also support ul-IntraUE-Mux-r16 and dci-Format1-2And0-2-r16 . | UE | No | No | No | +| defaultSpatialRelationPathlossRS-r16
Indicates the UE support of default spatial relation and pathloss reference RS for dedicated PUCCH/SRS and PUSCH. The UE indicating support of this also indicates the capabilities of supported SRS resources and maximum supported spatial relations for the supported FR2 bands using supportedSRS-Resources and maxNumberConfiguredSpatialRelations . | UE | No | No | FR2 only | +| dl-64QAM-MCS-TableAlt
Indicates whether the UE supports the alternative 64QAM MCS table for PDSCH. | UE | No | No | Yes | +| dl-SchedulingOffset-PDSCH-TypeA
Indicates whether the UE supports DL scheduling slot offset (K0) greater than 0 for PDSCH mapping type A. | UE | Yes | Yes | Yes | +| dl-SchedulingOffset-PDSCH-TypeB
Indicates whether the UE supports DL scheduling slot offset (K0) greater than 0 for PDSCH mapping type B. | UE | Yes | Yes | Yes | +| downlinkSPS
Indicates whether the UE supports PDSCH reception based on semi-persistent scheduling. One SPS configuration is supported per cell group. This applies only to non-shared spectrum channel access. For shared spectrum channel access, downlinkSPS-r16 applies. | UE | No | No | No | +| dynamicBetaOffsetInd-HARQ-ACK-CSI
Indicates whether the UE supports indicating beta-offset (UCI repetition factor onto PUSCH) for HARQ-ACK and/or CSI via DCI among the RRC configured beta-offsets. | UE | No | No | No | +| dynamicHARQ-ACK-Codebook
Indicates whether the UE supports HARQ-ACK codebook dynamically constructed by DCI(s). This field shall be set to supported . | UE | Yes | No | No | +| dynamicHARQ-ACK-CodeB-CBG-Retx-DL
Indicates whether the UE supports HARQ-ACK codebook size for CBG-based (re)transmission based on the DAI-based solution as specified in TS 38.213 [11]. | UE | No | No | No | +| dynamicPRB-BundlingDL
Indicates whether UE supports DCI-based indication of the PRG size for PDSCH reception. | UE | No | No | No | + +| | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|-----|----------|----------| +| dynamicSFI
Indicates whether the UE supports monitoring for DCI format 2_0 and determination of slot formats via DCI format 2_0. This applies only to non-shared spectrum channel access. For shared spectrum channel access, dynamicSFI-r16 applies. This capability is not applicable to NCR-MT. | UE | No | Yes | Yes | +| dynamicSwitchRA-Type0-1-PDSCH
Indicates whether the UE supports dynamic switching between resource allocation Types 0 and 1 for PDSCH as specified in TS 38.212 [10]. | UE | No | No | No | +| dynamicSwitchRA-Type0-1-PUSCH
Indicates whether the UE supports dynamic switching between resource allocation Types 0 and 1 for PUSCH as specified in TS 38.212 [10]. | UE | No | No | No | +| enhancedPowerControl-r16
For DG-PUSCH, one bit (separately from SRI) in UL grant is used to indicate the P0 value if SRI is present in the UL grant, and 1 or 2 bits is used to indicate the P0 value if SRI is not present in the UL grant. | UE | No | No | Yes | +| extendedCG-Periodicities-r16
Indicates that the UE supports extended periodicities for CG Type 1 (if the UE indicates configuredUL-GrantType1 or configuredUL-GrantType1-v1650 capability) or CG Type 2 (if the UE indicates configuredUL-GrantType2 or configuredUL-GrantType2-v1650 capability) as specified by periodicityExt-r16 field of IE ConfiguredGrantConfig in TS 38.331 [9]. | UE | No | No | No | +| extendedSPS-Periodicities-r16
Indicates that the UE supports extended periodicities for downlink SPS as specified by periodicityExt-r16 field of IE SPS-Config in TS 38.331 [9]. | UE | No | No | No | +| fdd-PCellUL-TX-AllUL-Subframe-r16
Indicates whether the UE configured with tdm-patternConfig-r16 can be semi-statically configured with LTE UL transmissions in all UL subframes not limited to the reference tdm-pattern (only for type 1 UE) in case of LTE FDD PCell. UE indicating support can configure its LTE FDD PCell with this feature on the band combination which indicates support of either tdm-restrictionFDD-endc-r16 or tdm-restrictionDualTX-FDD-endc-r16 . | UE | No | FDD only | FR1 only | +| fdra-Type-1-Gty-2-4-8-16-RBs-RIV-DCI-1-3-And-0-3-r18
Indicates support of FDRA Type 1 granularity of 2, 4, 8, or 16 consecutive RBs based RIV for DCI format 0_3 and FDRA Type 1 granularity of 2, 4, 8, or 16 consecutive RBs based RIV for DCI format 1_3.
The UE indicating support for this feature also indicates support at least one of 49-1, multiCell-PDSCH-DCI-1-3-DiffSCS-r18 , 49-2 or 49-2b | UE | No | No | No | +| harqACK-CB-SpatialBundlingPUCCH-Group-r16
Indicates whether the UE supports HARQ-ACK codebook type and HARQ-ACK spatial bundling configuration per PUCCH group as specified in TS 38.213 [11]. If the UE indicates support of this, it also supports two NR PUCCH groups with same numerology by setting twoPUCCH-Group to supported . | UE | No | No | No | +| harqACK-separateMultiDCI-MultiTRP-r16
Indicates whether the UE support of separate HARQ-ACK. The capability signalling of this feature includes the following:
  • - maxNumberLongPUCCHs-r16 indicates maximum number of long PUCCHs within a slot for separate HARQ-Ack
The UE that indicates support of this feature shall support multiDCI-MultiTRP-r16 . | UE | No | No | No | +| harqACK-jointMultiDCI-MultiTRP-r16
Indicates whether the UE support of joint HARQ-ACK. The UE that indicates support of this feature shall support multiDCI-MultiTRP-r16 . | UE | No | No | No | +| k1-RangeExtensionATG-r18
Indicates whether the UE supports extended K1 value range of (0..31) for unpaired spectrum. The UE indicating support of this feature shall also indicate support of airToGroundNetwork-r18 . | UE | No | TDD only | FR1 only | +| pucch-F0-2WithoutFH
Indicates whether the UE supports transmission of a PUCCH format 0 or 2 without frequency hopping. When included, the UE does not support PUCCH formats 0 and 2 without frequency hopping. When not included, the UE supports the PUCCH formats 0 and 2 without frequency hopping. | UE | Yes | No | Yes | +| pucch-F1-3-4WithoutFH
Indicates whether the UE supports transmission of a PUCCH format 1, 3 or 4 without frequency hopping. When included, the UE does not support PUCCH formats 1, 3 and 4 without frequency hopping. When not included, the UE supports the PUCCH formats 1, 3 and 4 without frequency hopping. | UE | Yes | No | Yes | + +| | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|-----|----|----------| +| interleavingVRB-ToPRB-PDSCH
Indicates whether the UE supports receiving PDSCH with interleaved VRB-to-PRB mapping as specified in TS 38.211 [6]. | UE | Yes | No | No | +| interSlotFreqHopping-PUSCH
Indicates whether the UE supports inter-slot frequency hopping for PUSCH transmissions. | UE | No | No | No | +| intraSlotFreqHopping-PUSCH
Indicates whether the UE supports intra-slot frequency hopping for PUSCH transmission, except for PUSCH scheduled by PDCCH in the Type1-PDCCH common search space before RRC connection establishment. | UE | Yes | No | Yes | +| maxHARQ-ProcessNumberATG-r18
Indicates the maximal supported HARQ process numbers for UL and for DL respectively. For each value of maxHARQ-ProcessNumberATG-r18 , value u16d32 indicates the maximal supported HARQ process number is 16 for UL and 32 for DL, value u32d16 indicates the maximal supported HARQ process number is 32 for UL and 16 for DL, value u32d32 indicates the maximal supported HARQ process number is 32 for UL and 32 for DL. The UE indicating support of this feature shall also indicate support of airToGroundNetwork-r18 . | UE | No | No | FR1 only | +| maxLayersMIMO-Adaptation-r16
Indicates whether the UE supports the network configuration of maxMIMO-Layers per DL BWP. If the UE supports this feature, the UE needs to report maxLayersMIMO-Indication . | UE | No | No | Yes | +| maxLayersMIMO-Indication
Indicates whether the UE supports the network configuration of maxMIMO-Layers as specified in TS 38.331 [9]. | UE | Yes | No | No | +| maxNumberPathlossRS-update-r16
Indicates the maximum number of configured pathloss reference RSs for PUSCH/PUCCH/SRS by RRC that the UE can support for MAC-CE based pathloss reference RS update. | UE | No | No | No | +| maxNumberSearchSpaces
Indicates whether the UE supports up to 10 search spaces in an SCell per BWP. | UE | No | No | No | +| maxNumberSRS-PosPathLossEstimateAllServingCells-r16
Indicates the maximum number of pathloss estimates that the UE can simultaneously maintain for all the SRS resource sets for positioning across all cells in addition to the up to four pathloss estimates that the UE maintains per serving cell for the PUSCH/PUCCH/SRS transmissions. The UE shall include this field if the UE supports any of olpc-SRS-PosBasedOnPRS-Serving-r16 , olpc-SRS-PosBasedOnSSB-Neigh-r16 and olpc-SRS-PosBasedOnPRS-Neigh-r16 . Otherwise, the UE does not include this field; | UE | No | No | No | +| maxNumberSRS-PosSpatialRelationsAllServingCells-r16
Indicates the maximum number of maintained spatial relations for all the SRS resource sets for positioning across all serving cells in addition to the spatial relations maintained spatial relations per serving cell for the PUSCH/PUCCH/SRS transmissions. It is only applied for FR2. The UE can include this field only if the UE supports any of spatialRelation-SRS-PosBasedOnSSB-Serving-r16 , spatialRelation-SRS-PosBasedOnCSI-RS-Serving-r16 , spatialRelation-SRS-PosBasedOnPRS-Serving-r16 , spatialRelation-SRS-PosBasedOnSSB-Neigh-r16 or spatialRelation-SRS-PosBasedOnPRS-Neigh-r16 . Otherwise, the UE does not include this field; | UE | No | No | FR2 only | + +| | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|----|----| +|

maxTotalResourcesForAcrossFreqRanges-r16

Indicates the maximum total number of SSB/CSI-RS/CSI-IM resources for beam management, pathloss measurement, BFD, RLM and new beam identification across frequency ranges (both FR1 and FR2) that the UE supports. The capability signalling includes the following:

  • - maxNumberResWithinSlotAcrossCC-AcrossFR-r16 indicates maximum total number of SSB/CSI-RS/CSI-IM resources configured to measure within a slot across all CCs across all frequency ranges for any of L1-RSRP measurement, L1-SINR measurement, pathloss measurement, BFD, RLM and new beam identification.
  • - maxNumberResAcrossCC-AcrossFR-r16 indicates maximum total number of SSB/CSI-RS/CSI-IM resources configured across all CCs across all frequency ranges for any of L1-RSRP measurement, L1-SINR measurement, pathloss measurement, BFD, RLM and new beam identification.

gNB takes into conjunction of this feature and the features maxTotalResourcesForOneFreqRange-r16, beamManagementSSB-CSI-RS, maxNumberCSI-RS-BFD, maxNumberSSB-BFD and maxNumberCSI-RS-SSB-CBD when configuring SSB/CSI-RS/CSI-IM resources for beam management, pathloss measurement, BFD, RLM and new beam identification across frequency ranges. The signalled values apply to the shortest slot duration defined in any FR(s) that are supported by the UE.

NOTE 1: The "configured to measure" RS is counted within the duration of a reference slot in which the corresponding reference signals are transmitted.

NOTE 2: Regarding the "configured to measure" RS counting

  • - (basic usage 1): If one resource is used for one or multiple of BFD/RLM, it is counted as one.
  • - (basic usage 2): If one resource is used for one or multiple of New Beam Identification/PL-RS/L1-RSRP, add 1.
    • - L1-RSRP measurement includes cases associated with reports with reportQuantity set to 'ssb-Index-RSRP', 'cri-RSRP' or with reportQuantity set to 'none' and CSI-RS-ResourceSet with trs-Info not configured.
  • - If one resource is used for L1-SINR in addition to basic usage 1 & 2, add N if referred N times by one or more CSI Reporting settings with reportQuantity-r16 = 'ssb-Index-SINR-r16' or 'cri-SINR-r16'.
| UE | No | No | No | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|----|----| + +| | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|----|----------| +|

maxTotalResourcesForOneFreqRange-r16
Indicates the maximum total number of SSB/CSI-RS/CSI-IM resources for beam management, pathloss measurement, BFD, RLM and new beam identification for one frequency range that the UE supports.
The capability signalling includes the following:

  • - maxNumberResWithinSlotAcrossCC-OneFR-r16 indicates maximum total number of SSB/CSI-RS/CSI-IM resources configured to measure within a slot across all CCs in one frequency range for any of L1-RSRP measurement, L1-SINR measurement, pathloss measurement, BFD, RLM and new beam identification
  • - maxNumberResAcrossCC-OneFR-r16 indicates maximum total number of SSB/CSI-RS/CSI-IM resources configured across all CCs in one frequency range for any of L1-RSRP measurement, L1-SINR measurement, pathloss measurement, BFD, RLM and new beam identification.

gNB takes into conjunction of this feature and the features beamManagementSSB-CSI-RS, maxNumberCSI-RS-BFD, maxNumberSSB-BFD and maxNumberCSI-RS-SSB-CBD when configuring SSB/CSI-RS/CSI-IM resources for beam management, pathloss measurement, BFD, RLM and new beam identification across one frequency range.

NOTE 1: The reference slot duration is the shortest slot duration defined for the reported FR supported by the UE.

NOTE 2: For RS configured for new beam identification, they are always counted regardless of beam failure event.

NOTE 3: The maxNumberResWithinSlotAcrossCC-AcrossFR-r16 only counts those in active BWP but the maxNumberResAcrossCC-AcrossFR-r16 counts all configured including both active and inactive BWP.

NOTE 4: The "configured to measure" RS is counted within the duration of a reference slot in which the corresponding reference signals are transmitted.

NOTE 5: Regarding the "configured to measure" RS counting

  • - (basic usage 1): If one resource is used for one or multiple of BFD/RLM, it is counted as one.
  • - (basic usage 2): If one resource is used for one or multiple of New Beam Identification/PL-RS/L1-RSRP, add 1.
    • - L1-RSRP measurement includes cases associated with reports with reportQuantity set to 'ssb-Index-RSRP', 'cri-RSRP' or with reportQuantity set to 'none' and CSI-RS-ResourceSet with trs-Info not configured.
  • - If one resource is used for L1-SINR in addition to basic usage 1 & 2, add N if referred N times by one or more CSI Reporting settings with reportQuantity-r16 = 'ssb-Index-SINR-r16' or 'cri-SINR-r16'.
| UE | No | No | Yes | +|

monitoringDCI-SameSearchSpace-r16
Indicates whether the UE supports monitoring both DCI format 0_1/1_1 and DCI format 0_2/1_2 in the same search space. If the UE supports this feature, the UE needs to report dci-Format1-2And0-2-r16.

| UE | No | No | No | +|

mTRP-PDCCH-singleSpan-r17
Indicates the support of PDCCH repetition for PDCCH monitoring with a single span of three contiguous OFDM symbols that is within the first four OFDM symbols in a slot. It is applicable to 15kHz SCS only.

The UE indicating support of this feature shall also indicate support of pdcch-MonitoringSingleSpanFirst4Sym-r16 and mTRP-PDCCH-Repetition-r17.

| UE | No | No | FR1 only | +|

multiPDSCH-PerSlotType1-CB-Support-r17
Indicates whether the UE supports RRC configuration multiPDSCH-PerSlotType1-CB-r17 as specified in TS 38.331 [9].

| UE | No | No | No | +|

multipleCORESET
Indicates whether the UE supports configuration of up to two PDCCH CORESETs per BWP in addition to the CORESET with CORESET-ID 0 in the BWP. If this is not supported, the UE supports one PDCCH CORESET per BWP in addition to the CORESET with CORESET-ID 0 in the BWP. It is mandatory with capability signalling for FR2 and optional for FR1.

| UE | CY | No | Yes | + +| | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|-----|----|-----| +| multipleCORESET-RedCap-r17
Indicates whether the RedCap UE supports configuration of up to three PDCCH CORESETs in the RedCap specific initial DL BWP when it does not contain CD-SSB and CORESET#0. If this is not supported, the field description of multipleCORESET applies to the RedCap-specific initial BWP. The RedCap UE reporting this capability shall also report multipleCORESET . | UE | No | No | No | +| mux-HARQ-ACK-PUSCH-DiffSymbol
Indicates whether the UE supports HARQ-ACK piggyback on a PUSCH with/without aperiodic CSI once per slot when the starting OFDM symbol of the PUSCH is different from the starting OFDM symbols of the PUCCH resource that HARQ-ACK would have been transmitted on. This applies only to non-shared spectrum channel access. For shared spectrum channel access, mux-HARQ-ACK-PUSCH-DiffSymbol-r16 applies. | UE | Yes | No | Yes | +| mux-HARQ-ACK-withoutPUCCH-onPUSCH-r16
Indicates that the UE is implemented according to the definition in TS 38.213 [11] for multiplexing HARQ-ACK in a PUSCH in a PUCCH slot when the UE has no HARQ-ACK for any DL activity to transmit, but it receives UL grant(s) with UL-TDAI field indicating HARQ-ACK multiplexing on a PUSCH, and it transmits multiple PUSCHs in the PUCCH slot. | UE | No | No | No | +| mux-MultipleGroupCtrlCH-Overlap
Indicates whether the UE supports more than one group of overlapping PUCCHs and PUSCHs per slot per PUCCH cell group for control multiplexing. | UE | No | No | Yes | +| mux-SR-HARQ-ACK-CSI-PUCCH-MultiPerSlot
Indicates whether the UE supports multiplexing SR, HARQ-ACK and CSI on a PUCCH or piggybacking on a PUSCH more than once per slot when SR, HARQ-ACK and CSI are supposed to be sent with the same or different starting symbol in a slot. This applies only to non-shared spectrum channel access. For shared spectrum channel access, mux-SR-HARQ-ACK-CSI-PUCCH-MultiPerSlot-r16 applies. | UE | No | No | Yes | +| mux-SR-HARQ-ACK-CSI-PUCCH-OncePerSlot
sameSymbol indicates the UE supports multiplexing SR, HARQ-ACK and CSI on a PUCCH or piggybacking on a PUSCH once per slot, when SR, HARQ-ACK and CSI are supposed to be sent with the same starting symbols on the PUCCH resources in a slot. diffSymbol indicates the UE supports multiplexing SR, HARQ-ACK and CSI on a PUCCH or piggybacking on a PUSCH once per slot, when SR, HARQ-ACK and CSI are supposed to be sent with the different starting symbols in a slot. The UE is mandated to support the multiplexing and piggybacking features indicated by sameSymbol while the UE is optional to support the multiplexing and piggybacking features indicated by diffSymbol .
If the UE indicates sameSymbol in this field and does not support mux-HARQ-ACK-PUSCH-DiffSymbol , the UE supports HARQ-ACK/CSI piggyback on PUSCH once per slot, when the starting OFDM symbol of the PUSCH is the same as the starting OFDM symbols of the PUCCH resource(s) that would have been transmitted on.
If the UE indicates sameSymbol in this field and supports mux-HARQ-ACK-PUSCH-DiffSymbol , the UE supports HARQ-ACK/CSI piggyback on PUSCH once per slot for which case the starting OFDM symbol of the PUSCH is the different from the starting OFDM symbols of the PUCCH resource(s) that would have been transmitted on. This applies only to non-shared spectrum channel access. For shared spectrum channel access, mux-SR-HARQ-ACK-CSI-PUCCH-OncePerSlot-r16 applies. | UE | FD | No | Yes | +| mux-SR-HARQ-ACK-PUCCH
Indicates whether the UE supports multiplexing SR and HARQ-ACK on a PUCCH or piggybacking on a PUSCH once per slot, when SR and HARQ-ACK are supposed to be sent with the different starting symbols in a slot. This applies only to non-shared spectrum channel access. For shared spectrum channel access, mux-SR-HARQ-ACK-PUCCH-r16 applies. | UE | No | No | Yes | +| newBeamIdentifications2PortCSI-RS-r16
Indicates whether the UE supports 2 port CSI-RS for new beam identification with the same resource counting as in maxTotalResourcesForOneFreqRange-r16 and maxTotalResourcesForAcrossFreqRanges-r16 . | UE | No | No | No | +| nominalRBG-SizeOfConfig-3-FDRA-Type-0-DCI-0-3-r18
Indicates support of nominal RBG size of Configuration 3 for FDRA type 0 for DCI format 0_3.
The UE indicating support for this feature also indicates support at least one of 49-2 or 49-2b | UE | No | No | No | + +| | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|-----|----|----------| +| nominalRBG-SizeOfConfig-3-FDRA-Type-0-DCI-1-3-r18
Indicates support of nominal RBG size of Configuration 3 for FDRA type 0 for DCI format 1_3.
The UE indicating support for this feature also indicates support at least one of 49-1 or multiCell-PDSCH-DCI-1-3-DiffSCS-r18 | UE | No | No | No | +| nzp-CSI-RS-IntefMgmt
Indicates whether the UE supports interference measurements using NZP CSI-RS. | UE | No | No | No | +| oneFL-DMRS-ThreeAdditionalDMRS-UL
Defines whether the UE supports DM-RS pattern for UL transmission with 1 symbol front-loaded DM-RS with three additional DM-RS symbols. | UE | No | No | Yes | +| oneFL-DMRS-TwoAdditionalDMRS-UL
Defines support of DM-RS pattern for UL transmission with 1 symbol front-loaded DM-RS with 2 additional DM-RS symbols and more than 1 antenna ports. | UE | Yes | No | Yes | +| onePortsPTRS
Defines whether UE supports PT-RS with 1 antenna port in DL reception and/or UL transmission. It is mandatory with UE capability signalling for FR2 and optional for FR1. The left most in the bitmap corresponds to DL reception and the right most bit in the bitmap corresponds to UL transmission. | UE | CY | No | Yes | +| onePUCCH-LongAndShortFormat
Indicates whether the UE supports transmission of one long PUCCH format and one short PUCCH format in TDM in the same slot. | UE | No | No | Yes | +| pathlossEstimation2PortCSI-RS-r16
Indicates whether the UE supports 2 port CSI-RS for pathloss estimation with the same resource counting as in maxTotalResourcesForOneFreqRange-r16 and maxTotalResourcesForAcrossFreqRanges-r16 . | UE | No | No | No | +| pathlossRS-UpdateForType1CG-PUSCH-r18
Indicates whether the UE supports configuration of enablePL-RS-UpdateForType1CG-PUSCH-SRS-r18 as specified in TS 38.331 [9].
A UE supporting this feature shall also support configuredUL-GrantType1 and maxNumberPathlossRS-Update-r16 . | UE | No | No | No | +| pCell-FR2
Indicates whether the UE supports PCell operation on FR2. | UE | Yes | No | FR2 only | +| pdccch-MonitoringSingleOccasion
Indicates whether the UE supports receiving PDCCH in a search space configured to be monitored within a single span of any three contiguous OFDM symbols in a slot with the capability of supporting at least 44 blind decodes in a slot for 15 kHz subcarrier spacing. | UE | No | No | FR1 only | +| pdccch-BlindDetectionCA
Indicates PDCCH blind decoding capabilities supported by the UE for CA with more than 4 CCs as specified in TS 38.213 [11]. The field value is from 4 to 16. | UE | No | No | No | +| NOTE: FR1-FR2 differentiation is not allowed in this release, although the capability signalling is supported for FR1-FR2 differentiation. | | | | | +| pdccch-BlindDetectionMCG-UE
Indicates PDCCH blind decoding capabilities supported for MCG when in NR-DC. The field value is from 1 to 15. The UE sets the value in accordance with the constraints specified in TS 38.213 [11].
Additionally, if the UE does not report pdccch-BlindDetectionCA , and if X is the maximum number of CCs supported by the UE across all NR-DC band combinations then there is at least one parameter pair (X1, X2) such that X1 + X2 = X and the UE supports at least one NR-DC band combination with X1 CCs in MCG and X2 CCs in SCG and for which X1 <= pdccch-BlindDetectionMCG-UE and X2 <= pdccch-BlindDetectionSCG-UE . | UE | No | No | Yes | +| pdccch-BlindDetectionSCG-UE
Indicates PDCCH blind decoding capabilities supported for SCG when in NR-DC. The field value is from 1 to 15. The UE sets the value in accordance with the constraints specified in TS 38.213 [11].
Additionally, if the UE does not report pdccch-BlindDetectionCA , and if X is the maximum number of CCs supported by the UE across all NR-DC band combinations then there is at least one parameter pair (X1, X2) such that X1 + X2 = X and the UE supports at least one NR-DC band combination with X1 CCs in MCG and X2 CCs in SCG and for which X1 <= pdccch-BlindDetectionMCG-UE and X2 <= pdccch-BlindDetectionSCG-UE . | UE | No | No | Yes | + +| | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|-----|----|----------| +|

pdcch-MonitoringAnyOccasionsWithSpanGapCrossCarrierSch-r16

Indicates how the UE supports pdcch-MonitoringAnyOccasionsWithSpanGap in case of cross-carrier scheduling with different SCSs in the scheduling cell and the scheduled cell.

Value 'mode2' indicates pdcch-MonitoringAnyOccasionsWithSpanGap is supported for the band of the scheduling/triggering/indicating cell.

Value 'mode3' indicates pdcch-MonitoringAnyOccasionsWithSpanGap is supported in both the band of the scheduled/triggered/indicated cell and the band of the scheduling/triggering/indicating cell.

UE indicating support of these feature indicates support of pdcch-MonitoringAnyOccasionsWithSpanGap and crossCarrierSchedulingDL-DiffSCS-r16.

NOTE: For pdcch-MonitoringAnyOccasionsWithSpanGap, the supported set (set1, set2 or set 3) for cross-carrier scheduling with the different SCSs in the scheduling cell and the scheduled cell is still based on the indicated value for the band of the scheduling cell.

| UE | No | No | No | +|

pdcch-MonitoringSingleSpanFirst4Sym-r16

Indicates whether the UE supports receiving PDCCH in a search space configured to be monitored within a single span of any three contiguous OFDM symbols that are within the first four OFDM symbols in a slot with the capability of supporting at least 44 blind decodes in a slot for 15 kHz subcarrier spacing.

| UE | No | No | FR1 only | +|

pdsch-256QAM-FR1

Indicates whether the UE supports 256QAM modulation scheme for PDSCH for FR1 as defined in 7.3.1.2 of TS 38.211 [6].

It is optional for (e)RedCap UEs and mandatory with capability signalling for other UEs.

| UE | CY | No | FR1 only | +|

pdsch-MappingTypeA

Indicates whether the UE supports receiving PDSCH using PDSCH mapping type A with less than seven symbols. This field shall be set to supported.

| UE | Yes | No | No | +|

pdsch-MappingTypeB

Indicates whether the UE supports receiving PDSCH using PDSCH mapping type B.

| UE | Yes | No | No | +|

pdsch-RepetitionMultiSlots

Indicates whether the UE supports receiving PDSCH scheduled by DCI format 1_1 when configured with pdsch-AggregationFactor > 1, as defined in 5.1.2.1 of TS 38.214 [12]. This applies only to non-shared spectrum channel access. For shared spectrum channel access, pdsch-RepetitionMultiSlots-r16 applies.

| UE | No | No | No | +|

pdsch-RE-MappingFR1-PerSymbol/pdsch-RE-MappingFR1-PerSlot

Indicates the maximum number of supported PDSCH Resource Element (RE) mapping patterns for FR1, each described as a resource (including NZP/ZP CSI-RS, CRS, CORESET and SSB) or bitmap. The number of patterns coinciding in a symbol in a CC and in a slot in a CC are limited by the respective capability parameters. Value n10 means 10 RE mapping patterns and n16 means 16 RE mapping patterns, and so on. The UE shall set the fields pdsch-RE-MappingFR1-PerSymbol and pdsch-RE-MappingFR1-PerSlot to at least n10 and n16, respectively. In the exceptional case that the UE does not include the fields, the network may anyway assume that the UE supports the required minimum values.

| UE | Yes | No | FR1 only | +|

pdsch-RE-MappingFR2-PerSymbol/pdsch-RE-MappingFR2-PerSlot

Indicates the maximum number of supported PDSCH Resource Element (RE) mapping patterns for FR2, each described as a resource (including NZP/ZP CSI-RS, CORESET and SSB) or bitmap. The number of patterns coinciding in a symbol in a CC and in a slot in a CC are limited by the respective capability parameters. Value n6 means 6 RE mapping patterns and n16 means 16 RE mapping patterns, and so on. The UE shall set the fields pdsch-RE-MappingFR2-PerSymbol and pdsch-RE-MappingFR2-PerSlot to at least n6 and n16, respectively. In the exceptional case that the UE does not include the fields, the network may anyway assume that the UE supports the required minimum values.

| UE | Yes | No | FR2 only | +|

precoderGranularityCORESET

Indicates whether the UE supports receiving PDCCH in CORESETs configured with CORESET-precoder-granularity equal to the size of the CORESET in the frequency domain as specified in TS 38.211 [6].

| UE | No | No | No | +|

pre-EmptIndication-DL

Indicates whether the UE supports interrupted transmission indication for PDSCH reception based on reception of DCI format 2_1 as defined in TS 38.213 [11]. This applies only to non-shared spectrum channel access. For shared spectrum channel access, pre-EmptIndication-DL-r16 applies.

| UE | No | No | No | + +| | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|-----|----|-----| +| pucch-F2-WithFH
Indicates whether the UE supports transmission of a PUCCH format 2 (2 OFDM symbols in total) with frequency hopping in a slot. This field shall be set to supported . | UE | Yes | No | Yes | +| pucch-F3-WithFH
Indicates whether the UE supports transmission of a PUCCH format 3 (4~14 OFDM symbols in total) with frequency hopping in a slot. This field shall be set to supported . | UE | Yes | No | Yes | +| pucch-F3-4-HalfPi-BPSK
Indicates whether the UE supports pi/2-BPSK for PUCCH format 3/4 as defined in 6.3.2.6 of TS 38.211 [6]. It is mandatory with capability signalling for FR1 and FR2. This capability is not applicable to IAB-MT. | UE | Yes | No | Yes | +| pucch-F4-WithFH
Indicates whether the UE supports transmission of a PUCCH format 4 (4~14 OFDM symbols in total) with frequency hopping in a slot. | UE | Yes | No | Yes | +| pusch-Repetition-CG-SDT-r17
Indicates whether the UE supports PUSCH repetitions for CG-SDT, as defined in TS 38.214 [12]. A UE supporting this feature shall also indicate the support of type1-PUSCH-RepetitionMultiSlots or pusch-RepetitionTypeB-r16 . When UE indicates type1-PUSCH-RepetitionMultiSlots and pusch-Repetition-CG-SDT-r17 , the UE supports PUSCH repetition for type A. When UE indicates pusch-RepetitionTypeB-r16 and pusch-Repetition-CG-SDT-r17 , UE supports PUSCH repetition for type B. For MO-SDT, a UE can include this feature only if the UE indicates the support of cg-SDT-r17 . For MT-SDT, a UE can include this feature only if the UE indicates the support of mt-SDT-r18 and mt-CG-SDT-r18 | UE | No | No | No | +| pusch-RepetitionMultiSlots
Indicates whether the UE supports transmitting PUSCH scheduled by DCI format 0_1 when configured with pusch-AggregationFactor > 1, as defined in clause 6.1.2.1 of TS 38.214 [12]. This applies only to non-shared spectrum channel access. For shared spectrum channel access, pusch-RepetitionMultiSlots-r16 applies. | UE | Yes | No | No | +| pucch-Repetition-F1-3-4
Indicates whether the UE supports transmission of a PUCCH format 1 or 3 or 4 over multiple slots with the repetition factor 2, 4 or 8. This applies only to non-shared spectrum channel access. For shared spectrum channel access, pucch-Repetition-F1-3-4-r16 applies. | UE | Yes | No | No | +| pusch-HalfPi-BPSK
Indicates whether the UE supports pi/2-BPSK modulation scheme for PUSCH as defined in 6.3.1.2 of TS 38.211 [6]. It is mandatory with capability signalling for FR1 and FR2. This capability is not applicable to IAB-MT. | UE | Yes | No | Yes | +| pusch-LBRM
Indicates whether the UE supports limited buffer rate matching in UL as specified in TS 38.212 [10]. | UE | No | No | Yes | +| pusch-RepetitionTypeA-r16
Indicates whether the UE supports the dynamic indication of the number of repetitions for PUSCH transmission as specified in TS 38.214 [12], clause 6.1.2.1. Support of this field is reported for shared spectrum channel access and non-shared spectrum channel access, respectively. UE indicating support of this feature shall support at least one of type2-PUSCH-RepetitionMultiSlots and pusch-RepetitionMultiSlots for shared spectrum and non-shared spectrum respectively. | UE | No | No | No | +| ra-Type0-PUSCH
Indicates whether the UE supports resource allocation Type 0 for PUSCH as specified in TS 38.214 [12]. | UE | No | No | No | +| rateMatchingCtrlResrcSetDynamic
Indicates whether the UE supports dynamic rate matching for DL control resource set. | UE | Yes | No | No | +| rateMatchingResrcSetDynamic
Indicates whether the UE supports receiving PDSCH with resource mapping that excludes the REs corresponding to resource sets configured with RB-symbol level granularity indicated by bitmaps (see patternType in RateMatchPattern in TS 38.331[9]) based on dynamic indication in the scheduling DCI as specified in TS 38.214 [12]. | UE | No | No | No | +| rateMatchingResrcSetSemi-Static
Indicates whether the UE supports receiving PDSCH with resource mapping that excludes the REs corresponding to resource sets configured with RB-symbol level granularity indicated by bitmaps and controlResourceSet (see patternType in RateMatchPattern in TS 38.331[9]) following the semi-static configuration as specified in TS 38.214 [12]. | UE | Yes | No | No | + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|-----|----------|----------| +| scs-60kHz
Indicates whether the UE supports 60kHz subcarrier spacing for data channel in FR1 as defined in clause 4.2-1 of TS 38.211 [6]. This capability is not applicable to eRedCap UEs. | UE | No | No | FR1 only | +| semiOpenLoopCSI
Indicates whether UE supports CSI reporting with report quantity set to 'CRI/RI/I1/CQI' as defined in clause 5.2.1.4 of TS 38.214 [12]. | UE | No | No | Yes | +| semiStaticHARQ-ACK-Codebook
Indicates whether the UE supports HARQ-ACK codebook constructed by semi-static configuration. | UE | Yes | No | No | +| simultaneousTCI-ActMultipleCC-r16
Indicates the UE support of simultaneous TCI state activation across multiple CCs. If the UE indicates support of this for a FR, the UE shall support this on the supported bands of the indicated FR where the UE reports the support of TCI-states for PDSCH using tci-StatePDSCH . | UE | No | No | Yes | +| simultaneousSpatialRelationMultipleCC-r16
Indicates the UE support of simultaneous spatial relation across multiple CCs for aperiodic and semi-persistent SRS. The UE indicating support of this also indicates the capabilities of maximum and active supported spatial relations for the supported FR2 bands using maxNumberConfiguredSpatialRelations and maxNumberActiveSpatialRelations . | UE | No | No | FR2 only | +| slotBasedDynamicPUCCH-Rep-r17
Indicates whether the UE supports both slot based dynamic PUCCH repetition and slot based dynamic repetition indication for PUCCH formats 0/1/2/3/4.

UE indicating support of this feature shall also indicate support of pucch-Repetition-F1-3-4 or pucch-Repetition-F0-2-r17 . | UE | No | No | No | +| spatialBundlingHARQ-ACK
Indicates whether the UE supports spatial bundling of HARQ-ACK bits carried on PUCCH or PUSCH per PUCCH group. With spatial bundling, two HARQ-ACK bits for a DL MIMO data is bundled into a single bit by logical "AND" operation. | UE | Yes | No | No | +| spatialRelationUpdateAP-SRS-r16
Indicates the UE support of spatial relation update for AP-SRS using MAC CE. The UE indicating support of this also indicates the capabilities of supported SRS resources and maximum supported spatial relations for the supported FR2 bands using supportedSRS-Resources and maxNumberConfiguredSpatialRelations . | UE | No | No | FR2 only | +| spCellPlacement
Indicates whether the UE supports a SpCell on FR1-FDD, FR1-TDD and/or FR2-TDD depending on which additional SCells of other frequency range(s) / duplex mode(s) are configured. It is applicable to NR SA and NR-DC (both MCG and SCG), where UL is configured on more than one of FR1-FDD, FR1-TDD and FR2-TDD in a cell group. If not included, the UE supports SpCell on any serving cell with UL in supported band combinations. | UE | No | No | No | +| sps-HARQ-ACK-Deferral-r17
Indicates whether the UE supports SPS HARQ-ACK deferral in case of TDD collision comprised of the following functional components:
  • - Identify HARQ-ACK bits of active SPS configurations for deferral in the initial PUCCH slot;
  • - Determination of the target PUCCH slot for SPS HARQ-ACK deferral;
  • - Multiplexing and transmission of deferred SPS HARQ-ACK information in the target PUCCH slot;
  • - Handling of the collision for the same HARQ process due to deferred SPS HARQ-ACK.
Support of this feature is reported for licensed and unlicensed bands, respectively. When this field is reported, either of non-SharedSpectrumChAccess-r17 or sharedSpectrumChAccess-r17 shall be reported, at least. A UE supporting this feature shall also indicate support of downlinkSPS . | UE | No | TDD only | No | +| sp-CSI-IM
Indicates whether the UE supports semi-persistent CSI-IM. | UE | No | No | Yes | +| sp-CSI-ReportPUCCH
Indicates whether UE supports semi-persistent CSI reporting using PUCCH formats 2, 3 and 4. This applies only to non-shared spectrum channel access. For shared spectrum channel access, sp-CSI-ReportPUCCH-r16 applies. | UE | No | No | No | +| sp-CSI-ReportPUSCH
Indicates whether UE supports semi-persistent CSI reporting using PUSCH. This applies only to non-shared spectrum channel access. For shared spectrum channel access, sp-CSI-ReportPUSCH-r16 applies. | UE | No | No | No | + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|-----|----------|----------| +| sp-CSI-RS
Indicates whether the UE supports semi-persistent CSI-RS. | UE | Yes | No | Yes | +| sps-ReleaseDCI-1-1-r16
Indicates whether the UE supports SPS release by DCI format 1_1. If the UE supports this feature, the UE needs to report downlinkSPS . | UE | No | No | No | +| sps-ReleaseDCI-1-2-r16
Indicates whether the UE supports SPS release by DCI format 1_2. If the UE supports this feature, the UE needs to report downlinkSPS and dci-Format1-2And0-2-r16 . | UE | No | No | No | +| srs-AdditionalRepetition-r17
Indicates support of the value "n3" for repetitionFactor-r17 .

The UE indicating support of this feature shall also indicate support of srs-increasedRepetition-r17 . | UE | No | No | No | +| srs-PeriodicityAndOffsetExt-r16
Indicates whether the UE supports the periodicity of semi-persistent and periodic SRS with 128, 256, 512, and 20480 slots. | UE | No | No | No | +| support-5MHz-ChannelBW-20PRB-CORESET0-r18
Indicates whether the UE supports short RACH preamble formats with 15kHz SCS, and long PRACH formats with 1.25kHz SCS, and the reception of 20 PRB CORESET0. This FG is supported for 15 kHz SCS only.

This feature is only applicable when an associated SS/PBCH block is located in band n100 at GSCN 41638 of Table 5.4.3.1-3 in TS 38.101-1 [2].

NOTE: The UE supporting this feature supports configuration of 20 PRB BWP operation. | UE | No | FDD only | FR1 only | +| supportedActivatedPRS-ProcessingWindow-r17
Indicates the number of supported activated PRS processing windows across all active DL BWPs. The UE can include this field only if the UE supports one of prs-ProcessingWindowType1A-r17 , prs-ProcessingWindowType1B-r17 or prs-ProcessingWindowType2-r17 . Otherwise, the UE does not include this field. | UE | No | No | No | +| supportedDMRS-TypeDL
Defines supported DM-RS configuration types at the UE for DL reception. Type 1 is mandatory with capability signalling. Type 2 is optional. If this field is not included, Type 1 is supported. | UE | FD | No | Yes | +| supportedDMRS-TypeUL
Defines supported DM-RS configuration types at the UE for UL transmission. Support of both type 1 and type 2 is mandatory with capability signalling. If this field is not included, Type 1 is supported. | UE | FD | No | Yes | +| supportRepetitionZeroOffsetRV-r16
Indicates whether UE supports the value 0 for the parameter sequenceOffsetforRV . The UE indicating support of this capability shall also indicate support of supportInter-slotTDM-r16 with maxNumberTCI-states-r16 set to 2 for at least one band. | UE | No | No | No | +| supportRetx-Diff-CoresetPool-Multi-DCI-TRP-r16
Indicates that retransmission scheduled by a different CORESETPoolIndex for multi-DCI multi-TRP is not supported.

For multi-DCI multi-TRP operation, if this feature is reported, UE does not support retransmission scheduled by PDCCH received in a different CORESETPoolIndex compared to the CORESETPoolIndex of the initial transmission, i.e., the UE is not expected to receive, for the same HARQ process ID, DCI from a different CORESETPoolIndex that schedules the retransmission, i.e., NDI not flipped. This applies to both PDSCH and PUSCH retransmissions.

UE indicating support of this feature shall indicate support of multiDCI-MultiTRP-r16 . | UE | No | No | No | +| ta-BasedPDC-TN-NonSharedSpectrumChAccess-r17
Indicates whether the UE supports propagation delay compensation based on Rel-15 TA procedure for TN and non-shared spectrum channel access. | UE | No | No | No | +| targetSMTC-SCG-r16
Indicates the support of configuration of SMTC of target SCG cell with field targetCellSMTC-SCG . | UE | No | No | No | +| tdd-MultiDL-UL-SwitchPerSlot
Indicates whether the UE supports more than one switch points in a slot for actual DL/UL transmission(s). | UE | No | TDD only | Yes | + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|-----|----------|----------| +| tdd-PCellUL-TX-AllUL-Subframe-r16
Indicates whether the UE configured with tdm-patternConfig-r16 can be semi-statically configured with LTE UL transmissions in all UL subframes not limited to the reference tdm-pattern (only for type 1 UE) in case of TDD PCell. UE indicating support can configure LTE TDD PCell with this feature on the band combination which indicates support of tdm-restrictionTDD-endc-r16 . | UE | No | TDD only | FR1 only | +| tpc-PUCCH-RNTI
Indicates whether the UE supports group DCI message based on TPC-PUCCH-RNTI for TPC commands for PUCCH. | UE | No | No | Yes | +| tpc-PUSCH-RNTI
Indicates whether the UE supports group DCI message based on TPC-PUSCH-RNTI for TPC commands for PUSCH. | UE | No | No | Yes | +| tpc-SRS-RNTI
Indicates whether the UE supports group DCI message based on TPC-SRS-RNTI for TPC commands for SRS. | UE | No | No | Yes | +| twoDifferentTPC-Loop-PUCCH
Indicates whether the UE supports two different TPC loops for PUCCH closed loop power control. | UE | Yes | Yes | Yes | +| twoDifferentTPC-Loop-PUSCH
Indicates whether the UE supports two different TPC loops for PUSCH closed loop power control. | UE | Yes | Yes | Yes | +| twoFL-DMRS
Defines whether the UE supports DM-RS pattern for DL reception and/or UL transmission with 2 symbols front-loaded DM-RS without additional DM-RS symbols.
The left most in the bitmap corresponds to DL reception and the right most bit in the bitmap corresponds to UL transmission. | UE | Yes | No | Yes | +| twoFL-DMRS-TwoAdditionalDMRS-UL
Defines whether the UE supports DM-RS pattern for UL transmission with 2 symbols front-loaded DM-RS with one additional 2 symbols DM-RS. | UE | Yes | No | Yes | +| twoPUCCH-AnyOthersInSlot
Indicates whether the UE supports transmission of two PUCCH formats in TDM in the same slot, which are not covered by twoPUCCH-F0-2-ConsecSymbols and onePUCCH-LongAndShortFormat . | UE | No | No | Yes | +| twoPUCCH-F0-2-ConsecSymbols
Indicates whether the UE supports transmission of two PUCCHs of format 0 or 2 in consecutive symbols in a slot. | UE | No | Yes | Yes | +| twoStepRACH-r16
Indicates whether the UE supports the following basic structure and procedure of 2-step RACH:
  • - Fallback procedures from 2-step RA type to 4-step RA type;
  • - MSGA PRACH resource and format determination;
  • - MSGA PUSCH configuration;
  • - Validation and transmission of MSGA PRACH and PUSCH;
  • - Mapping between preamble of MSGA PRACH and PUSCH occasion with DMRS resource of MSGA PUSCH;
  • - MSGB monitoring and decoding;
  • - PUCCH transmission for HARQ-ACK feedback to a MSGB;
  • - Power control for MSGA PRACH, MSGA PUSCH and PUCCH carrying HARQ-ACK feedback to MSGB.
  • - Reconfiguration with sync using a contention free random access with 2-step RA type on MSGA PRACH and PUSCH resources that are associated with SSB resources of the target cell.
| UE | No | No | No | +| twoTCI-Act-servingCellInCC-List-r16
Indicates whether the UE supports receiving the Enhanced TCI States Activation/Deactivation for UE-specific PDSCH MAC CE (as specified in TS 38.321 [8] clause 6.1.3.24) indicating a serving cell configured as part of simultaneousTCI-UpdateList1 or simultaneousTCI-UpdateList2 as specified in TS 38.331 [9].
If the UE indicates support of simultaneousTCI-ActMultipleCC-r16 for a FR and support of at least one of singleDCI-SDM-scheme-r16 , supportFDM-SchemeA-r16 , supportFDM-SchemeB-r16 , supportTDM-SchemeA-r16 or supportInter-slotTDM-r16 for at least one band or component carrier of this FR, the UE shall indicate support of twoTCI-Act-servingCellInCC-List-r16 for this FR. | UE | CY | No | Yes | + +| | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|-----|-----|-----| +| type1-HARQ-ACK-Codebook-r16
Indicates whether the UE supports Type 1 HARQ-ACK codebook for TDRA using the starting symbol of the PDCCH monitoring occasion in which the DL assignment is detected as the reference of the SLIV. If the UE supports this feature, the UE needs to report dci-Format1-2And0-2-r16 . Support for FR1/FR2 is differentiated from the viewpoint of the scheduled carrier. | UE | No | No | Yes | +| type1-PUSCH-RepetitionMultiSlots
Indicates whether the UE supports Type 1 PUSCH transmissions with configured grant as specified in TS 38.214 [12] with UL-TWG-repK value equal to 2, 4, or 8 with a single repetition of the transport block within each slot, and redundancy version pattern as indicated by UL-TWG-RV-rep. A UE supporting this feature shall also support Type 1 PUSCH transmissions with configured grant as specified in TS 38.214 [12] with UL-TWG-repK value of one. This applies only to non-shared spectrum channel access. For shared spectrum channel access, type1-PUSCH-RepetitionMultiSlots-r16 applies. | UE | No | No | No | +| type2-CG-ReleaseDCI-0-1-r16
Indicates whether the UE supports type 2 configured grant release by DCI format 0_1. If the UE supports this feature, the UE needs to report configuredUL-GrantType2 or configuredUL-GrantType2-v1650 . | UE | No | No | No | +| type2-CG-ReleaseDCI-0-2-r16
Indicates whether the UE supports type 2 configured grant release by DCI format 0_2. If the UE supports this feature, the UE needs to report configuredUL-GrantType2 or configuredUL-GrantType2-v1650 and dci-Format1-2And0-2-r16 . | UE | No | No | No | +| type2-HARQ-ACK-Codebook-r16
Indicates whether the UE supports Type 2 HARQ-ACK codebook when HARQ-ACK feedback in a codebook corresponds to more than one unicast DL DCI for same scheduled cell in a monitoring occasion of a scheduling cell using the PDSCH starting time in addition to the existing monitoring occasion and Cell index to order the HARQ-ACK feedback. | UE | No | No | No | +| type2-PUSCH-RepetitionMultiSlots
Indicates whether the UE supports Type 2 PUSCH transmissions with configured grant as specified in TS 38.214 [12] with UL-TWG-repK value equal to 2, 4, or 8 with a single repetition of the transport block within each slot, and redundancy version pattern as indicated by UL-TWG-RV-rep. A UE supporting this feature shall also support Type 2 PUSCH transmissions with configured grant as specified in TS 38.214 [12] with UL-TWG-repK value of one. This applies only to non-shared spectrum channel access. For shared spectrum channel access, type2-PUSCH-RepetitionMultiSlots-r16 applies. | UE | No | No | No | +| type2-SP-CSI-Feedback-LongPUCCH
Indicates whether UE supports Type II CSI semi-persistent CSI reporting over PUCCH Formats 3 and 4 as defined in clause 5.2.4 of TS 38.214 [12]. | UE | No | No | No | +| uci-CodeBlockSegmentation
Indicates whether the UE supports segmenting UCI into multiple code blocks depending on the payload size. | UE | Yes | No | Yes | +| ul-64QAM-MCS-TableAlt
Indicates whether the UE supports the alternative 64QAM MCS table for PUSCH with and without transform precoding respectively. | UE | No | No | Yes | +| ul-SchedulingOffset
Indicates whether the UE supports UL scheduling slot offset (K2) greater than 12. | UE | Yes | Yes | Yes | +| unifiedJointTCI-commonUpdate-r17
Indicates the maximum number of configured CC lists per cell group for common multi-CC TCI state ID update and activation.
The UE indicating support of this feature shall also indicate support of unifiedJointTCI-commonMultiCC-r17 or unifiedSeparateTCI-commonMultiCC-r17 . | UE | No | No | No | + +| | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|----|----------| +|

uplinkPreCompensationATG-r18
Indicates whether the UE supports the uplink time and frequency pre-compensation and timing relationship enhancements comprised of the following functional components:

  • - Support of UE specific TA calculation based on its position and the serving ATG base station reference location.
  • - For TA update in RRC_CONNECTED state, support of combination of both open (i.e. UE autonomous TA estimation) and closed (i.e., received TA commands) control loops
  • - Support of pre-compensation of the calculated TA in its uplink transmissions
  • - Support of frequency pre-compensation to counter shift the Doppler experienced.
  • - Support of determining timing of the scheduling of PUSCH, PUCCH and PDCCH ordered PRACH, CSI reference resource, transmission of aperiodic SRS activation of TA command, first PUSCH transmission in CG Type 2 with cell-specific K_offset if indicated
  • - Support of receiving ATG base station reference location and cell-specific K_offset in system information

Support of this feature is mandatory for UE supporting airToGroundNetwork-r18.

| UE | CY | No | FR1 only | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|----|----------| + +#### 4.2.7.11 Other PHY parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----|--------------|--------------| +| appliedFreqBandListFilter
Mirrors the FreqBandList that the NW provided in the capability enquiry, if any. The UE filtered the band combinations in the supportedBandCombinationList in accordance with this appliedFreqBandListFilter . | UE | No | No | No | +| downlinkSetEUTRA
Indicates the features that the UE supports on the DL carriers corresponding to one EUTRA band entry in a band combination by FeatureSetEUTRA-DownlinkId. The FeatureSetEUTRA-DownlinkId = 0 means that the UE does not support a EUTRA DL carrier in this band of a band combination. | Band | N/A | N/A | N/A | +| downlinkSetNR
Indicates the features that the UE supports on the DL carriers corresponding to one NR band entry in a band combination by FeatureSetDownlinkId. The FeatureSetDownlinkId = 0 means that the UE does not support a DL carrier in this band of a band combination. A fallback per band feature set resulting from the reported DL feature set that has fallback per CC feature set is not signalled but the UE shall support it. | Band | N/A | N/A | N/A | +| extendedBand-n77-r16
This field is only applicable for UEs that indicate support for band n77. If present, the UE supports the restriction to 3450 - 3550 MHz and 3700 - 3980 MHz ranges of band n77 in the USA as specified in Note 12 of Table 5.2-1 in TS 38.101-1 [2]. If absent, the UE supports only restriction to the 3700 - 3980 MHz range of band n77 in the USA. A UE that indicates this field shall also support NS value 55 as specified in TS 38.101-1 [2]. A UE supporting NS value 55 shall indicate this field. | UE | No | No | No | +| extendedBand-n77-2-r17
This field is only applicable for UEs that indicate support for band n77. If present, the UE supports the restriction to 3450 - 3650 MHz and 3650 - 3980 ranges of band n77 in Canada as specified in Note 12 of Table 5.2-1 in TS 38.101-1 [2]. If absent, the UE supports only restriction to the 3450 - 3650 MHz range of band n77 in Canada. A UE that indicates this field shall also support NS value 57 as specified in TS 38.101-1 [2]. A UE supporting NS value 57 shall indicate this field. | UE | No | No | No | +| featureSetCombinations
Pools of feature sets that the UE supports on the NR or MR-DC band combinations. | UE | N/A | No | No | +| featureSets
Pools of downlink and uplink features sets as well as a pool of FeatureSetCombination elements. A FeatureSetCombination refers to the IDs of the feature set(s) that the UE supports in that FeatureSetCombination. The BandCombination entries in the BandCombinationList then indicate the ID of the FeatureSetCombination that the UE supports for that band combination. | UE | N/A | No | No | +| naics-Capability-List
Indicates that UE in MR-DC supports NAICS as defined in TS 36.331 [17]. | UE | No | No | No | +| receivedFilters
Contains all filters requested with UE-CapabilityRequestFilterNR from version 15.6.0 onwards. | UE | No | No | No | +| supportedBandCombinationList
Defines the supported NR and/or MR-DC band combinations by the UE. For each band combination the UE identifies the associated feature set combination by featureSetCombinations index referring to featureSetCombination. A fallback band combination resulting from the reported CA and MR-DC band combination is not signalled but the UE shall support it. For intra-band non-contiguous CA band combinations, the UE only includes one band combination, and exclude the others for which the presence of uplink CA bandwidth class in the band combination entry is different. One band combination entry can also indicate support of any other possible permutations in the presence of uplink CA bandwidth class where a paired downlink CA bandwidth class is the same or where the number of UL CCs is smaller than the one of paired DL CCs expressed by the CA bandwidth class, as specified in TS 36.306 [15]. For these band combinations not included in the capability, the supported feature set is the same as the ones for the band combination included in the UE capability. | UE | Yes | No | No | +| supportedBandCombinationListNEDC-Only
Defines the supported NE-DC only type of band combinations by the UE. | UE | No | No | No | + +| | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----|-----|-----| +| supportedBandCombinationList-UplinkTxSwitch-r16
Defines the NR inter-band UL CA, SUL and/or EN-DC band combinations where UE supports dynamic UL Tx switching. UE only includes this field if requested by the network. All fallback band combinations resulting from the reported band combination, which include at least one band pair supporting dynamic UL Tx switching as indicated in ULTxSwitchingBandPair , shall be supported by the UE. | UE | No | No | No | +| supportedBandListNR
Includes the supported NR bands as defined in TS 38.101-1 [2], TS 38.101-2 [3], and TS 38.101-5 [34]. | UE | Yes | No | No | +| uplinkSetEUTRA
Indicates the features that the UE supports on the UL carriers corresponding to one EUTRA band entry in a band combination by FeatureSetEUTRA-UplinkId. The FeatureSetUplinkId = 0 means that the UE does not support a UL carrier in this band of a band combination. | Band | N/A | N/A | N/A | +| uplinkSetNR
Indicates the features that the UE supports on the UL carriers corresponding to one NR band entry in a band combination by FeatureSetUplinkId. The FeatureSetUplinkId = 0 means that the UE does not support a UL carrier in this band of a band combination. A fallback per band feature set resulting from the reported UL feature set that has fallback per CC feature set is not signalled but the UE shall support it. | Band | N/A | N/A | N/A | + +#### 4.2.7.12 *NRDC-Parameters* + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----|--------------|--------------| +| asyncNRDC-r16
Indicates whether the UE supports asynchronous NR-DC with MRTD and MTTD as specified in clause 7.5 and 7.6 of TS 38.133 [5]. If the band combination is comprised of a single band entry for more than two carriers, the UE shall support any permutations of carriers to CGs. If the band combination is comprised of at least two band entries, the carriers corresponding to a band entry shall belong to only one cell group.
If the band combination includes both FR1 and FR2 bands, a UE indicating this capability shall support asynchronous NR-DC configuration where all serving cells of the MCG are in FR1 and all serving cells of the SCG are in FR2. | BC | No | No | No | +| condPSCellAdditionNRDC-r17
Indicates whether the UE supports conditional PSCell addition in NR-DC. The UE supporting this feature shall also support 2 trigger events for same execution condition in conditional PSCell addition in NR-DC. | BC | No | No | No | +| intraFR-NR-DC-PwrSharingMode1-r16
Indicates whether the UE supports intra-FR NR-DC with semi-static power sharing mode1 between MCG and SCG cells of same frequency range as defined in TS 38.213 [11]. If this field is absent, the UE does not support intra-FR NR-DC.
In case MCG and SCG have cells in different frequency ranges, this field indicates the support of power sharing only between MCG and SCG cells with UL in FR1. | BC | No | No | FR1 only | +| intraFR-NR-DC-PwrSharingMode2-r16
Indicates whether the UE supports semi-static power sharing mode2 between MCG and SCG cells of same frequency range for synchronous intra-FR NR-DC as defined in TS 38.213 [11]. The UE indicating the support of this also indicates the support of intraFR-NR-DC-PwrSharingMode1-r16 .
In case MCG and SCG have cells in different frequency ranges, this field indicates the support of power sharing only between MCG and SCG cells with UL in FR1. | BC | No | No | FR1 only | +| intraFR-NR-DC-DynamicPwrSharing-r16
Indicates the UE support of dynamic power sharing for intra-FR NR-DC between MCG and SCG cells of same frequency range with long or short offset as specified in TS 38.213 [11]. The UE indicating the support of this also indicates the support of intraFR-NR-DC-PwrSharingMode1-r16 .
In case MCG and SCG have cells in different frequency ranges, this field indicates the support of power sharing only between MCG and SCG cells with UL in FR1. | BC | No | No | FR1 only | +| scg-ActivationDeactivationNRDC-r17
Indicates whether the UE supports activation (with or without RACH) and deactivation on SCG in NR-DC, upon SCG addition and upon reconfiguration of the SCG, as specified in TS 38.331 [9]. A UE supporting this feature shall indicate support of NR-DC as specified in TS 38.331 [9]. For the UE supporting this feature, it is mandatory to report maxNumberCSI-RS-BFD and maxNumberSSB-BFD for all NR bands of this band combination where the UE supports SpCell. | BC | No | No | No | +| scg-ActivationDeactivationResumeNRDC-r17
Indicates whether the UE supports activation (with or without RACH) and deactivation on SCG in NR-DC, upon reception of an RRCReconfiguration included in an RRCResume message, as specified in TS 38.331 [9]. A UE supporting this feature shall indicate support of NR-DC and of resumeWithSCG-Config-r16 as specified in TS 38.331 [9]. For the UE supporting this feature, it is mandatory to report maxNumberCSI-RS-BFD and maxNumberSSB-BFD for all NR bands of this band combination where the UE supports SpCell. | BC | No | No | No | +| sfn-SyncNRDC
Indicates the UE supports NR-DC only with SFN and frame synchronization between PCell and PSCell. If not included by the UE supporting NR-DC, the UE supports NR-DC with slot-level synchronization without condition on SFN and frame synchronization. In this release of the specification, the UE shall not report this UE capability. | UE | No | No | No | +| supportedCellGrouping-r16
Indicates which NR-DC cell groupings the UE supports for the given NR-DC band combination, i.e., mapping of serving cells to MCG and SCG, and the operation mode (synchronous or asynchronous), as requested by the network via requestedCellGrouping-r16 .
The bitmap reported in this field refers to the cell grouping IDs that the network requested in requestedCellGrouping-r16 . The first (leftmost) bit corresponds to ID#0 (i.e. the first element in requestedCellGrouping-r16 ), the second bit corresponds to ID#1 (i.e. the second element in requestedCellGrouping-r16 ) and so on.
NOTE: Irrespective of the indicated supportedCellGrouping-r16 , the UE shall also support NR-DC where all FR1 serving cells are in the MCG and all | BC | No | No | No | + +#### 4.2.7.13 CarrierAggregationVariant + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----|--------------|--------------| +| fr1fdd-FR1TDD-CA-SpCellOnFR1FDD
Indicates whether the UE supports an FR1 FDD SpCell (and possibly SCells) when configured with an FR1 TDD SCell. | UE | No | No | No | +| fr1fdd-FR1TDD-CA-SpCellOnFR1TDD
Indicates whether the UE supports an FR1 TDD SpCell (and possibly SCells) when configured with an FR1 FDD SCell. | UE | No | No | No | +| fr1fdd-FR1TDD-FR2TDD-CA-SpCellOnFR1FDD
Indicates whether the UE supports an FR1 FDD SpCell (and possibly SCells) when configured with an FR1 TDD SCell and an FR2 TDD SCell. | UE | No | No | No | +| fr1fdd-FR1TDD-FR2TDD-CA-SpCellOnFR1TDD
Indicates whether the UE supports an FR1 TDD SpCell (and possibly SCells) when configured with an FR1 FDD SCell and an FR2 TDD SCell. | UE | No | No | No | +| fr1fdd-FR1TDD-FR2TDD-CA-SpCellOnFR2TDD
Indicates whether the UE supports an FR2 TDD SpCell (and possibly SCells) when configured with an FR1 FDD SCell and an FR1 TDD SCell. | UE | No | No | No | +| fr1fdd-FR2TDD-CA-SpCellOnFR1FDD
Indicates whether the UE supports an FR1 FDD SpCell (and possibly SCells) when configured with an FR2 TDD SCell. | UE | No | No | No | +| fr1fdd-FR2TDD-CA-SpCellOnFR2TDD
Indicates whether the UE supports an FR2 TDD SpCell (and possibly SCells) when configured with an FR1 FDD SCell. | UE | No | No | No | +| fr1tdd-FR2TDD-CA-SpCellOnFR1TDD
Indicates whether the UE supports an FR1 TDD SpCell (and possibly SCells) when configured with an FR2 TDD SCell. | UE | No | No | No | +| fr1tdd-FR2TDD-CA-SpCellOnFR2TDD
Indicates whether the UE supports an FR2 TDD SpCell (and possibly SCells) when configured with an FR1 TDD SCell. | UE | No | No | No | + +#### 4.2.7.14 *Phy-ParametersSharedSpectrumChAccess* + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----|--------------|--------------| +| configuredUL-GrantType1-r16
Indicates whether the UE supports Type 1 PUSCH transmissions with configured grant as specified in TS 38.214 [12] with UL-TWG-repK value of one in shared spectrum channel access. | UE | No | No | No | +| configuredUL-GrantType2-r16
Indicates whether the UE supports Type 2 PUSCH transmissions with configured grant as specified in TS 38.214 [12] with UL-TWG-repK value of one in shared spectrum channel access. | UE | No | No | No | +| downlinkSPS-r16
Indicates whether the UE supports PDSCH reception based on semi-persistent scheduling. One SPS configuration is supported per cell group in shared spectrum channel access. | UE | No | No | No | +| dynamicSFI-r16
Indicates whether the UE supports monitoring for DCI format 2_0 and determination of slot formats via DCI format 2_0 in shared spectrum channel access. | UE | No | No | No | +| mux-HARQ-ACK-PUSCH-DiffSymbol-r16
Indicates whether the UE supports HARQ-ACK piggyback on a PUSCH with/without aperiodic CSI once per slot when the starting OFDM symbol of the PUSCH is different from the starting OFDM symbols of the PUCCH resource that HARQ-ACK would have been transmitted on in shared spectrum channel access.

This feature is mandatory if UE supports any of the deployment scenarios A.2, B, C, D and E in Annex B.3 of TS 38.300 [28]. | UE | CY | No | No | +| mux-SR-HARQ-ACK-CSI-PUCCH-MultiPerSlot-r16
Indicates whether the UE supports multiplexing SR, HARQ-ACK and CSI on a PUCCH or piggybacking on a PUSCH more than once per slot when SR, HARQ-ACK and CSI are supposed to be sent with the same or different starting symbol in a slot in shared spectrum channel access. | UE | No | No | No | +| mux-SR-HARQ-ACK-CSI-PUCCH-OncePerSlot-r16
sameSymbol indicates the UE supports multiplexing SR, HARQ-ACK and CSI on a PUCCH or piggybacking on a PUSCH once per slot, when SR, HARQ-ACK and CSI are supposed to be sent with the same starting symbols on the PUCCH resources in a slot. diffSymbol indicates the UE supports multiplexing SR, HARQ-ACK and CSI on a PUCCH or piggybacking on a PUSCH once per slot, when SR, HARQ-ACK and CSI are supposed to be sent with the different starting symbols in a slot in shared spectrum channel access.

If the UE indicates sameSymbol in this field and does not support mux-HARQ-ACK-PUSCH-DiffSymbol-r16 , the UE supports HARQ-ACK/CSI piggyback on PUSCH once per slot, when the starting OFDM symbol of the PUSCH is the same as the starting OFDM symbols of the PUCCH resource(s) that would have been transmitted on.
If the UE indicates sameSymbol in this field and supports mux-HARQ-ACK-PUSCH-DiffSymbol-r16 , the UE supports HARQ-ACK/CSI piggyback on PUSCH once per slot for which case the starting OFDM symbol of the PUSCH is the different from the starting OFDM symbols of the PUCCH resource(s) that would have been transmitted on.

The UE is mandated to support the multiplexing and piggybacking features indicated by sameSymbol for mux-SR-HARQ-ACK-CSI-PUCCH-OncePerSlot-r16 if UE supports any of the deployment scenarios A.2, B, C, D and E in Annex B.3 of TS 38.300 [28]. | UE | CY | No | No | +| mux-SR-HARQ-ACK-PUCCH-r16
Indicates whether the UE supports multiplexing SR and HARQ-ACK on a PUCCH or piggybacking on a PUSCH once per slot, when SR and HARQ-ACK are supposed to be sent with the different starting symbols in a slot in shared spectrum channel access. | UE | No | No | No | +| pdsch-RepetitionMultiSlots-r16
Indicates whether the UE supports receiving PDSCH scheduled by DCI format 1_1 when configured with pdsch-AggregationFactor > 1, as defined in 5.1.2.1 of TS 38.214 [12] in shared spectrum channel access. | UE | No | No | No | +| pre-EmptIndication-DL-r16
Indicates whether the UE supports interrupted transmission indication for PDSCH reception based on reception of DCI format 2_1 as defined in TS 38.213 [11] in shared spectrum channel access. | UE | No | No | No | + +| | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|----|----| +| pusch-RepetitionMultiSlots-r16
Indicates whether the UE supports transmitting PUSCH scheduled by DCI format 0_1 when configured with pusch-AggregationFactor > 1, as defined in clause 6.1.2.1 of TS 38.214 [12] in shared spectrum channel access. This feature is mandatory if UE supports any of the deployment scenarios A.2, B, C, D and E in Annex B.3 of TS 38.300 [28]. | UE | CY | No | No | +| pucch-Repetition-F1-3-4-r16
Indicates whether the UE supports transmission of a PUCCH format 1 or 3 or 4 over multiple slots with the repetition factor 2, 4 or 8 in shared spectrum channel access. This feature is mandatory if UE supports any of the deployment scenarios A.2(whenever PUCCH is supported on shared spectrum channel access cell), B, C, D and E in Annex B.3 of TS 38.300 [28]. | UE | CY | No | No | +| sp-CSI-ReportPUCCH-r16
Indicates whether UE supports semi-persistent CSI reporting using PUCCH formats 2, 3 and 4 in shared spectrum channel access. | UE | No | No | No | +| sp-CSI-ReportPUSCH-r16
Indicates whether UE supports semi-persistent CSI reporting using PUSCH in shared spectrum channel access. | UE | No | No | No | +| ss-SINR-Meas-r16
Indicates whether the UE can perform SS-SINR measurement in shared spectrum channel access as specified in TS 38.215 [13]. | UE | No | No | No | +| type1-PUSCH-RepetitionMultiSlots-r16
Indicates whether the UE supports Type 1 PUSCH transmissions with configured grant in shared spectrum channel access as specified in TS 38.214 [12] with UL-TWG-repK value equal to 2, 4, or 8 with a single repetition of the transport block within each slot, and redundancy version pattern as indicated by UL-TWG-RV-rep. A UE supporting this feature shall also support Type 1 PUSCH transmissions with configured grant as specified in TS 38.214 [12] with UL-TWG-repK value of one. | UE | No | No | No | +| type2-PUSCH-RepetitionMultiSlots-r16
Indicates whether the UE supports Type 2 PUSCH transmissions with configured grant in shared spectrum channel access as specified in TS 38.214 [12] with UL-TWG-repK value equal to 2, 4, or 8 with a single repetition of the transport block within each slot, and redundancy version pattern as indicated by UL-TWG-RV-rep. A UE supporting this feature shall also support Type 2 PUSCH transmissions with configured grant as specified in TS 38.214 [12] with UL-TWG-repK value of one. | UE | No | No | No | + +### 4.2.8 Void + +### 4.2.9 *MeasAndMobParameters* + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|-----|--------------|--------------| +| cellIndividualOffsetPerMeasEvent-r18
Indicates whether the UE supports the configuration of a cell individual offset per measurement event within reportConfigNR or reportConfigInterRAT as specified in TS 38.331 [9]. | UE | No | No | No | +| cli-RSSI-Meas-r16
Indicates whether the UE can perform CLI RSSI measurements as specified in TS 38.215 [13] and supports periodical reporting and measurement event triggering as specified in TS 38.331 [9]. If the UE supports this feature, the UE needs to report maxNumberCLI-RSSI-r16 . If this parameter is indicated for FR1 and FR2 differently, each indication corresponds to the frequency range of measurement resources to be measured. | UE | No | TDD only | Yes | +| cli-SRS-RSRP-Meas-r16
Indicates whether the UE can perform SRS RSRP measurements as specified in TS 38.215 [13] and supports periodical reporting and measurement event triggering based on SRS-RSRP as specified in TS 38.331 [9]. If the UE supports this feature, the UE needs to report maxNumberCLI-SRS-RSRP-r16 and maxNumberPerSlotCLI-SRS-RSRP-r16 . If this parameter is indicated for FR1 and FR2 differently, each indication corresponds to the frequency range of measurement resources to be measured. | UE | No | TDD only | Yes | +| concurrentMeasGap-r17
Indicates whether the UE supports the concurrent measurements gaps as specified in TS 38.133 [5]. The capability signalling comprises the following parameters:
  • - concurrentPerUE-OnlyMeasGap-r17 indicates whether the UE supports more than 1 per-UE measurement gap configurations (i.e. gap combination configuration id = 2 as specified in TS 38.133 [5]), or
  • - concurrentPerUE-PerFRCombMeasGap-r17 indicates whether the UE supports all concurrent gap combination configurations as specified in TS 38.133 [5] including support of more than 1 per-UE measurement gap configurations. For UE capable of Rel-15 per-FR gap (independentGapConfig), this field indicates whether the UE supports more than 1 per-FR gap measurement gap configurations in an FR, or simultaneous 1 per UE measurement gap plus 1 per-FR measurement gap configurations in an FR, or more than 1 per-UE measurement gap configurations (i.e. gap combination configuration id = 2 as specified in TS 38.133 [5]).
| UE | No | No | No | +| concurrentMeasGapEUTRA-r17
Indicates whether the UE support the configurations of E-UTRAN measurement objectives associated with more than 1 concurrent measurement gaps as specified in TS 38.133 [5]. The UE indicating support of this feature shall also indicate support of concurrentMeasGap-r17 . | UE | No | No | No | +| condHandoverFDD-TDD-r16
Indicates whether the UE supports conditional handover between FDD and TDD cells. The parameter can only be set if condHandover-r16 is set for both FDD and TDD. The UE that indicates support of this feature shall also indicate support of handoverFDD-TDD . | UE | No | No | No | +| condHandoverFR1-FR2-r16
Indicates whether the UE supports conditional handover HO between FR1 and FR2. The parameter can only be set if condHandover-r16 is set for both FR1 and FR2. The UE that indicates support of this feature shall also indicate support of handoverFR1-FR2 . | UE | No | No | No | +| condHandoverWithSCG-NRDC-r17
Indicates whether the UE supports conditional handover with NR SCG configuration for NR-DC. The UE indicating support of this feature shall also indicate the support of condHandover-r16 and support of at least one NR-DC band combination. | UE | No | No | No | +| csi-RS-RLM
Indicates whether the UE can perform radio link monitoring procedure based on measurement of CSI-RS as specified in TS 38.213 [11] and TS 38.133 [5]. This parameter needs FR1 and FR2 differentiation. If the UE supports this feature, the UE needs to report maxNumberResource-CSI-RS-RLM . This applies only to non-shared spectrum channel access. For shared spectrum channel access, csi-RS-RLM-r16 applies. | UE | Yes | No | Yes | + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|----|-----| +| csi-RSRP-AndRSRQ-MeasWithSSB
Indicates whether the UE can perform CSI-RSRP and CSI-RSRQ measurement as specified in TS 38.215 [13], where CSI-RS resource is configured with an associated SS/PBCH. If this parameter is indicated for FR1 and FR2 differently, each indication corresponds to the frequency range of measured target cell. If the UE supports this feature, the UE needs to report maxNumberCSI-RS-RRM-RS-SINR . This applies only to non-shared spectrum channel access. For shared spectrum channel access, csi-RS-RLM-r16 applies. | UE | No | No | Yes | +| csi-RSRP-AndRSRQ-MeasWithoutSSB
Indicates whether the UE can perform CSI-RSRP and CSI-RSRQ measurement as specified in TS 38.215 [13], where CSI-RS resource is configured for a cell that transmits SS/PBCH block and without an associated SS/PBCH block. If this parameter is indicated for FR1 and FR2 differently, each indication corresponds to the frequency range of measured target cell. If the UE supports this feature, the UE needs to report maxNumberCSI-RS-RRM-RS-SINR . This applies only to non-shared spectrum channel access. For shared spectrum channel access, csi-RSRP-AndRSRQ-MeasWithoutSSB-r16 applies. | UE | No | No | Yes | +| csi-SINR-Meas
Indicates whether the UE can perform CSI-SINR measurements based on configured CSI-RS resources as specified in TS 38.215 [13]. If this parameter is indicated for FR1 and FR2 differently, each indication corresponding to the frequency range of measured target cell. If the UE supports this feature, the UE needs to report maxNumberCSI-RS-RRM-RS-SINR . This applies only to non-shared spectrum channel access. For shared spectrum channel access, csi-SINR-Meas-r16 applies. | UE | No | No | Yes | +| deriveSSB-IndexFromCellInterNon-NCSG-r17
Indicates whether the UE supports configuration of deriveSSB-IndexFromCellInter-r17 in MeasObjectNR . This field applies to NR SA, MN configured measurements when NR-DC or NE-DC is configured, and SN configured measurements when NR-DC or (NG)EN-DC is configured. UE supporting this feature is required to meet the measurement requirements in TS 38.133 [5]. This field applies only to non-NCSG capable UEs (i.e. UEs not supporting ncsg-MeasGapNR-Patterns-r17 ). | UE | No | No | No | +| eutra-AutonomousGaps-r16
Defines whether the UE supports, upon configuration of useAutonomousGaps by the network, acquisition of relevant information from a neighbouring E-UTRA cell by reading the SI of the neighbouring cell using autonomous gap and reporting the acquired information to the network as specified in TS 38.331 [9] when MR-DC is not configured. | UE | No | No | No | +| eutra-AutonomousGaps-NEDC-r16
Defines whether the UE supports, upon configuration of useAutonomousGaps by the network, acquisition of relevant information from a neighbouring E-UTRA cell by reading the SI of the neighbouring cell using autonomous gap and reporting the acquired information to the network as specified in TS 38.331 [9] when NE-DC is configured. | UE | No | No | No | +| eutra-AutonomousGaps-NRDC-r16
Defines whether the UE supports, upon configuration of useAutonomousGaps by the network, acquisition of relevant information from a neighbouring E-UTRA cell by reading the SI of the neighbouring cell using autonomous gap and reporting the acquired information to the network as specified in TS 38.331 [9] when NR-DC is configured. | UE | No | No | No | +| eutra-CGI-Reporting
Defines whether the UE supports acquisition of relevant CGI-information from a neighbouring E-UTRA cell by reading the SI of the neighbouring cell and reporting the acquired information to the network as specified in TS 38.331 [9] when the (NG)EN-DC and NE-DC are not configured or, when consistent DRX is configured in NR-DC. The consistent DRX configuration implies that MN and SN have the same DRX cycle and on-duration configured by MN completely contains on-duration configured by SN. It is mandated if the UE supports EUTRA. It is optional for (e)RedCap UEs. | UE | CY | No | No | +| eutra-CGI-Reporting-NEDC
Defines whether the UE supports acquisition of relevant information from a neighbouring E-UTRA cell by reading the SI of the neighbouring cell and reporting the acquired information to the network as specified in TS 38.331 [9] when the NE-DC is configured. | UE | No | No | No | + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|-----|-----|--------------------------------| +| eutra-CGI-Reporting-NRDC
Defines whether the UE supports acquisition of relevant information from a neighbouring E-UTRA cell by reading the SI of the neighbouring cell and reporting the acquired information to the network as specified in TS 38.331 [9] when the NR-DC is configured wherein MN and SN have different DRX cycles, or on-duration configured by MN does not contain on-duration configured by SN if the DRX cycles are the same. | UE | No | No | No | +| eutra-NeedForGapNCSG-Reporting-r17
Indicates whether the UE supports reporting of the NCSG and measurement gap requirement information for E-UTRA target bands in the UE response to a network configuration RRC message as specified in TS 38.331 [9]. | UE | No | No | No | +| eventA-MeasAndReport
Indicates whether the UE supports NR measurements and events A triggered reporting as specified in TS 38.331 [9]. This field only applies to SN configured measurement when (NG)EN-DC is configured. For NR SA, MN and SN configured measurement when NR-DC is configured, and MN configured measurement when NE-DC is configured, this feature is mandatory supported. | UE | Yes | Yes | No | +| eventB-MeasAndReport
Indicates whether the UE supports EUTRA measurement and event B triggered reporting as specified in TS 38.331 [9]. It is mandated if the UE supports EUTRA. | UE | CY | No | No | +| eventD1-MeasReportTrigger-r17
Indicates whether the UE supports location-based triggered measurement reporting (i.e., event D1) as specified in TS 38.331 [9]. It is mandated if the UE supports locationBasedCondHandover-r17 in any NTN band. | UE | CY | No | No | +| gNB-ID-LengthReporting-r17
Indicates whether the UE supports acquisition and reporting of gNB ID length from a neighbouring intra-frequency or inter-frequency NR cell by reading the SI of the neighbouring cell and reporting the acquired gNB ID length to the network as specified in TS 38.331 [9] when (NG)EN-DC and NE-DC are not configured or, when consistent DRX is configured in NR-DC. The consistent DRX configuration implies that MN and SN have the same DRX cycle and on-duration configured by MN completely contains on-duration configured by SN. It is mandated if UE supports NR CGI reporting (NG)EN-DC and NE-DC are not configured or, when consistent DRX is configured in NR-DC. | UE | CY | No | No | +| gNB-ID-LengthReporting-ENDC-r17
Indicates whether the UE supports acquisition and reporting of gNB ID length from a neighbouring intra-frequency or inter-frequency NR cell by reading the SI of the neighbouring cell and reporting the acquired gNB ID length to the network as specified in TS 38.331 [9] when the (NG)EN-DC is configured. It is mandated if UE supports NR CGI reporting when (NG)EN-DC is configured. | UE | CY | No | No | +| gNB-ID-LengthReporting-NEDC-r17
Indicates whether the UE supports acquisition and reporting of gNB ID length from a neighbouring intra-frequency or inter-frequency NR cell by reading the SI of the neighbouring cell and reporting the acquired gNB ID length to the network as specified in TS 38.331 [9] when the NE-DC is configured. It is mandated if UE supports NR CGI reporting when NE-DC is configured. | UE | CY | No | No | +| gNB-ID-LengthReporting-NRDC-r17
Indicates whether the UE supports acquisition and reporting of gNB ID length from a neighbouring intra-frequency or inter-frequency NR cell by reading the SI of the neighbouring cell and reporting the acquired gNB ID length to the network as specified in TS 38.331 [9] when the NR-DC is configured wherein MN and SN have different DRX cycles, or on-duration configured by MN does not contain on-duration configured by SN if the DRX cycles are the same. It is mandated if UE supports NR CGI reporting when NR-DC is configured. | UE | CY | No | No | +| gNB-ID-LengthReporting-NPN-r17
Indicates whether the UE supports acquisition of NPN-relevant gNB ID length from a neighbouring intra-frequency or inter-frequency NR NPN cell by reading the SI of the neighbouring cell and reporting the acquired gNB ID length to the network as specified in TS 38.331 [9]. It is mandated if UE supports NPN CGI reporting. | UE | CY | No | No | +| handoverLTE-5GC, handoverLTE-5GC-r17
Indicates whether the UE supports HO to EUTRA connected to 5GC. It is mandated if the UE supports EUTRA connected to 5GC. | UE | CY | Yes | Yes
(Incl
FR2-2
DIFF) | + +| | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|-----|-----|--------------------------------| +| handoverFDD-TDD
Indicates whether the UE supports HO between FDD and TDD. It is mandated if the UE supports both FDD and TDD. This field only applies to NR SA/NR-DC/NE-DC (e.g. PCell handover). For PSCell change when (NG)EN-DC/NR-DC is configured, this feature is mandatory supported. UEs supporting this shall indicate support of handoverInterF for both FDD and TDD. | UE | Yes | No | No | +| handoverFR1-FR2
Indicates whether the UE supports HO between FR1 and FR2. Support is mandatory for the UE supporting both FR1 and FR2. This field only applies to NR SA/NR-DC/NE-DC (e.g. PCell handover). For PSCell change when (NG)EN-DC/NR-DC is configured, this feature is mandatory supported. UEs supporting this shall indicate support of handoverInterF for both FR1 and FR2. | UE | Yes | No | No | +| handoverFR1-FR2-2-r17
Indicates whether the UE supports HO between FR1 and FR2-2. This field only applies to NR SA/NR-DC/NE-DC (e.g. PCell handover) and PSCell change when (NG)EN-DC/NR-DC is configured. UEs supporting this shall indicate support of handoverInterF for both FR1 and FR2-2. | UE | No | No | No | +| handoverFR2-1-FR2-2-r17
Indicates whether the UE supports HO between FR2-1 and FR2-2. This field only applies to NR SA/NR-DC/NE-DC (e.g. PCell handover) and PSCell change when (NG)EN-DC/NR-DC is configured. UEs supporting this shall indicate support of handoverInterF for both FR2-1 and FR2-2. | UE | No | No | No | +| handoverInterF, handoverInterF-r17
Indicates whether the UE supports inter-frequency HO. It indicates the support for inter-frequency HO from the corresponding duplex mode and from frequency range indicated to be supported as described in Annex B. This field only applies to NR SA/NR-DC/NE-DC (e.g. PCell handover). For PSCell change when (NG)EN-DC/NR-DC is configured, this feature is mandatory supported. | UE | Yes | Yes | Yes
(Incl
FR2-2
DIFF) | +| handoverLTE-EPC, handoverLTE-EPC-r17
Indicates whether the UE supports HO to EUTRA connected to EPC. It is mandated if the UE supports EUTRA connected to EPC. | UE | CY | Yes | Yes
(Incl
FR2-2
DIFF) | +| idleInactiveNR-MeasReport-r16, idleInactiveNR-MeasReport-r17
Indicates whether the UE supports configuration of NR SSB measurements in RRC_IDLE/RRC_INACTIVE and reporting of the corresponding results upon network request as specified in TS 38.331 [9]. If this parameter is indicated for FR1 and FR2 differently, each indication corresponds to the frequency range of measured target cell. | UE | No | No | Yes
(Incl
FR2-2
DIFF) | +| idleInactiveNR-MeasBeamReport-r16
Indicates whether the UE supports beam level measurements in RRC_IDLE/RRC_INACTIVE and reporting of the corresponding beam measurement results upon network request as specified in TS 38.331 [9]. A UE supports this feature shall also support idleInactiveNR-MeasReport-r16 . If this parameter is indicated for FR1 and FR2 differently, each indication corresponds to the frequency range of measured target cell. | UE | No | No | Yes | +| idleInactiveEUTRA-MeasReport-r16
Indicates whether the UE supports configuration of E-UTRA measurements in RRC_IDLE/RRC_INACTIVE and reporting of the corresponding results upon network request as specified in TS 38.331 [9]. | UE | No | No | No | +| idleInactive-ValidityArea-r16
Indicates whether the UE supports configuration of a validity area for NR measurements in RRC_IDLE/RRC_INACTIVE as specified in TS 38.331 [9]. | UE | No | No | No | +| increasedNumberOfCSI-RSPerMO-r16
Indicates support of up to 192 CSI-RS resource for L3 mobility configuration per measurement object configured with associatedSSB . | UE | No | No | Yes | +| independentGapConfig
This field indicates whether the UE supports two independent measurement gap configurations for FR1 and FR2 specified in clause 9.1.2 of TS 38.133 [5]. The field also indicates whether the UE supports the FR2 inter-RAT measurement without gaps when (NG)EN-DC is not configured. | UE | No | No | No | + +| | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|-----|----------|-----| +|

independentGapConfig-maxCC-r17
This field indicates whether the UE supports two independent measurement gap configurations for FR1 and FR2 as specified in clause 9.1.2 of TS 38.133 [5] while the number of configured serving cells is less than or equal to the indicated number.

The capability signaling includes the following parameters:

  • - fr1-Only-r17 indicates the maximum number of configured serving cells when only NR FR1 serving cells are configured
  • - fr2-Only-r17 indicates the maximum number of configured serving cells when only NR FR2 serving cells are configured
  • - fr1-AndFR2-r17 indicates the maximum number of configured serving cells when both NR FR1 and NR FR2 serving cells are configured

The absence of the fr1-Only-r17 or fr2-Only-r17 field indicates that per-FR gap is not supported when only FR1 or FR2 serving cells are configured. Absence of the fr1-AndFR2-r17 field indicates that per-FR-gap is not supported when both FR1 and FR2 serving cells are configured. Value "1" for fr1-Only-r17 or fr2-Only-r17 indicates support of the per-FR gap when only PCell is configured (no additional CC). Value "2" for fr1-Only-r17 or fr2-Only-r17 indicates support of the per-FR gap when PCell and 1 additional CC are configured, and so on. Value "1" or "2" for fr1-AndFR2-r17 indicates the support of per-FR gap when PCell and "1" additional CC are configured.

UE indicating support of this feature in UE-NR-Capability shall not indicate support of independentGapConfig in UE-NR-Capability.

| UE | No | No | No | +|

independentGapConfigPRS-r17
Indicates whether the UE supports two independent measurement gap configurations for FR1 and FR2 for PRS measurement, as specified in clause 9.1.2 of TS 38.133 [5].

| UE | No | No | No | +|

intraAndInterF-MeasAndReport
Indicates whether the UE supports NR intra-frequency and inter-frequency measurements and at least periodical reporting. This field only applies to SN configured measurement when (NG)EN-DC is configured. For NR SA, MN and SN configured measurement when NR-DC is configured, and MN configured measurement when NE-DC is configured, this feature is mandatory supported.

| UE | Yes | Yes | No | +|

interFrequencyMeas-NoGap-r16
Indicates whether the UE can perform inter-frequency SSB based measurements without measurement gaps if the SSB is completely contained in the active BWP of the UE as specified in TS 38.133 [5]. If this parameter is indicated for FR1 and FR2 differently, each indication corresponds to the frequency range of cells to be measured.

| UE | No | No | Yes | +|

interSatMeas-r17
Indicates whether the UE supports inter-satellite measurement as specified in TS 38.331 [9]. It is mandatory if the UE supports nonTerrestrialNetwork-r17.

| UE | CY | No | No | +|

l3-MeasUnknownSCellActivation-r18
Indicates whether the UE supports reporting valid L3 measurement results triggered by the unknown SCell activation command
UE is required to meet the shortened SCell activation delay requirement in TS 38.133 [5] if the feature is supported, including single SCell activation, single PUCCH SCell activation, and multiple SCell activation with/without PUCCH SCell.

| UE | No | No | No | +|

maxNumberCLI-RSSI-r16
Defines the maximum number of CLI-RSSI measurement resources for CLI RSSI measurement. If the UE supports cli-RSSI-Meas-r16, the UE shall report this capability.

| UE | CY | TDD only | No | +|

maxNumberCLI-SRS-RSRP-r16
Defines the maximum number of SRS-RSRP measurement resources for SRS-RSRP measurement. If the UE supports cli-SRS-RSRP-Meas-r16, the UE shall report this capability.

NOTE 1: A slot is based on minimum SCS among active BWPs across all CCs configured for SRS-RSRP measurement.
NOTE 2: A SRS resource occasion that overlaps with the slot is counted as one measurement resource in the slot.

| UE | CY | TDD only | No | + +| | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|----------|----------| +| maxNumberCSI-RS-RRM-RS-SINR
Defines the maximum number of CSI-RS resources for RRM and RS-SINR measurement across all measurement frequencies per slot. If UE supports any of csi-RSRP-AndRSRQ-MeasWithSSB , csi-RSRP-AndRSRQ-MeasWithoutSSB , and csi-SINR-Meas , UE shall report this capability.

NOTE: A slot is based on minimum SCS among all measurement frequencies configured for RRM and RS-SINR measurement. | UE | CY | No | No | +| maxNumberPerSlotCLI-SRS-RSRP-r16
Defines the maximum number of SRS-RSRP measurement resources per slot for SRS-RSRP measurement. If the UE supports cli-SRS-RSRP-Meas-r16 , the UE shall report this capability. | UE | CY | TDD only | No | +| maxNumberResource-CSI-RS-RLM
Defines the maximum number of CSI-RS resources within a slot per spCell for CSI-RS based RLM. If UE supports any of csi-RS-RLM and ssb-AndCSI-RS-RLM , UE shall report this capability. | UE | CY | No | Yes | +| measSequenceConfig-r18
Indicates whether the UE supports configuration of measSequence-r18 in MeasObjectNR and MeasObjectEUTRA for recommended sequence for intra/inter-RAT intra/inter-frequency measurement. | UE | No | No | No | +| ncsg-MeasGapNR-Patterns-r17
Indicates whether the UE supports NR-only NCSG patterns. The left most bit in the bitmap corresponds to NCSG pattern #0 and the right most bit in the bitmap corresponds to NCSG pattern #23. A bit in the bitmap is set to 1 if the corresponding pattern is supported by the UE. NCSG patterns #0 to #23 are as specified in TS 38.133 [5].

NCSG patterns #2 and #3 are mandatory (i.e. the corresponding bits in the bitmap is set to 1) if the UE includes this field. NCSG patterns #17 and #18 are mandatory (i.e. the corresponding bits in the bitmap is set to 1) if UE includes this field and supports a FR2 band. UEs supporting this shall indicate support of nr-NeedForGapNCSG-Reporting-r17 . | UE | No | No | No | +| ncsg-MeasGapPatterns-r17
Indicates whether the UE supports NCSG patterns. The left most bit in the bitmap corresponds to NCSG pattern #0 and the right most bit in the bitmap corresponds to NCSG pattern #23. A bit in the bitmap is set to 1 if the corresponding pattern is supported by the UE. NCSG patterns #0 to #23 are as specified in TS 38.133 [5].

NCSG patterns #0 and #1 are mandatory (i.e. the corresponding bits in the bitmap is set to 1) if the UE includes this field. NCSG patterns #13 and #14 are mandatory (i.e. the corresponding bits in the bitmap is set to 1) if UE supports ncsg-MeasGapPerFR-r17 or if the UE is NCSG capable and supports FR2 band in standalone mode. UEs supporting this shall indicate support of nr-NeedForGapNCSG-Reporting-r17 or eutra-NeedForGapNCSG-Reporting-r17 . | UE | No | No | No | +| ncsg-MeasGapPerFR-r17
Indicates whether the UE supports per-FR NCSG. UEs supporting this shall indicate support of nr-NeedForGapNCSG-Reporting-r17 . | UE | No | No | No | +| ncsg-SymbolLevelScheduleRestrictionInter-r17
Indicates whether the UE supports performing measurement with NCSG based on flag deriveSSB-IndexFromCell-inter and meeting the following requirements that the scheduling restriction in FR2 serving cell during NCSG ML is on SSB symbol level. UEs supporting this shall indicate support of nr-NeedForGapNCSG-Reporting-r17 . | UE | No | No | FR2 only | +| nr-AutonomousGaps-r16
Defines whether the UE supports, upon configuration of useAutonomousGaps by the network, acquisition of relevant information from a neighbouring NR cell by reading the SI of the neighbouring cell using autonomous gap and reporting the acquired information to the network as specified in TS 38.331 [9] when MR-DC is not configured. If this parameter is indicated for FR1 and FR2 differently, each indication corresponds to the frequency range of measured target cell. | UE | No | No | Yes | +| nr-AutonomousGaps-ENDC-r16
Defines whether the UE supports, upon configuration of useAutonomousGaps by the network, acquisition of relevant information from a neighbouring NR cell by reading the SI of the neighbouring cell using autonomous gap and reporting the acquired information to the network as specified in TS 38.331 [9] when (NG)EN-DC is configured. If this parameter is indicated for FR1 and FR2 differently, each indication corresponds to the frequency range of measured target cell. | UE | No | No | Yes | +| nr-AutonomousGaps-NEDC-r16 | UE | No | No | Yes | + +| | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|-----|----------|----------| +| Defines whether the UE supports, upon configuration of useAutonomousGaps by the network, acquisition of relevant information from a neighbouring NR cell by reading the SI of the neighbouring cell using autonomous gap and reporting the acquired information to the network as specified in TS 38.331 [9] when NE-DC is configured. If this parameter is indicated for FR1 and FR2 differently, each indication corresponds to the frequency range of measured target cell. | | | | | +| nr-AutonomousGaps-NRDC-r16
Defines whether the UE supports, upon configuration of useAutonomousGaps by the network, acquisition of relevant information from a neighbouring NR cell by reading the SI of the neighbouring cell using autonomous gap and reporting the acquired information to the network as specified in TS 38.331 [9] when NR-DC is configured. If this parameter is indicated for FR1 and FR2 differently, each indication corresponds to the frequency range of measured target cell. | UE | No | No | Yes | +| nr-CGI-Reporting
Defines whether the UE supports acquisition of relevant CGI-information from a neighbouring intra-frequency or inter-frequency NR cell by reading the SI of the neighbouring cell and reporting the acquired information to the network as specified in TS 38.331 [9] when (NG)EN-DC and NE-DC are not configured or, when consistent DRX is configured in NR-DC. The consistent DRX configuration implies that MN and SN have the same DRX cycle and on-duration configured by MN completely contains on-duration configured by SN. It is optional for (e)RedCap UEs. | UE | CY | No | No | +| nr-CGI-Reporting-ENDC
Defines whether the UE supports acquisition of relevant CGI-information from a neighbouring intra-frequency or inter-frequency NR cell by reading the SI of the neighbouring cell and reporting the acquired information to the network as specified in TS 38.331 [9] when the (NG)EN-DC is configured. | UE | Yes | No | No | +| nr-CGI-Reporting-NEDC
Defines whether the UE supports acquisition of relevant information from a neighbouring intra-frequency or inter-frequency NR cell by reading the SI of the neighbouring cell and reporting the acquired information to the network as specified in TS 38.331 [9] when the NE-DC is configured. | UE | Yes | No | No | +| nr-CGI-Reporting-NPN-r16
Defines whether the UE supports acquisition of NPN-relevant CGI-information from a neighbouring intra-frequency or inter-frequency NR NPN cell by reading the SI of the neighbouring cell and reporting the acquired information to the network as specified in TS 38.331 [9]. If UE supports NPN, UE shall report this capability. It is optional for (e)RedCap UEs. | UE | CY | No | No | +| nr-CGI-Reporting-NRDC
Defines whether the UE supports acquisition of relevant information from a neighbouring intra-frequency or inter-frequency NR cell by reading the SI of the neighbouring cell and reporting the acquired information to the network as specified in TS 38.331 [9] when the NR-DC is configured wherein MN and SN have different DRX cycles, or on-duration configured by MN does not contain on-duration configured by SN if the DRX cycles are the same. | UE | Yes | No | No | +| nr-NeedForGapNCSG-Reporting-r17
Indicates whether the UE supports reporting of the NCSG and measurement gap requirement information for SSB based measurement in the UE response to a network configuration RRC message as specified in TS 38.331 [9]. | UE | No | No | No | +| nr-NeedForGap-Reporting-r16
Indicates whether the UE supports reporting the measurement gap requirement information for NR target in the UE response to a network configuration RRC message. | UE | No | No | No | +| nr-NeedForInterruptionReport-r18
Indicates whether the UE supports reporting the interruption requirement information for SSB based measurement towards NR target without gap in the UE response to a network configuration RRC message. The UE supporting this feature shall also indicate support of nr-NeedForGap-Reporting-r16 . | UE | No | No | No | +| parallelMeasurementGap-r17
Indicates whether the UE supports 2 parallel measurement gaps for NTN SSB based RRM measurements. If a UE does not include this field but includes nonTerrestrialNetwork-r17 , the UE supports 1 measurement gap for NTN SSB based RRM measurements. If this parameter is indicated, a UE shall also support that two parallel measurement gaps with the same gap type can be associated to one frequency layer. A UE supporting this feature shall also indicate the support of nonTerrestrialNetwork-r17 . | UE | No | FDD only | FR1 only | + +| | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|----------|----------| +| parallelSMTC-r17
Indicates whether the UE supports NTN SSB based RRM measurements on target cells belonging to 4 SMTC-s on a single frequency carrier. If a UE does not include this field but includes nonTerrestrialNetwork-r17 , the UE supports NTN SSB based RRM measurements on target cells belonging to 2 SMTC-s on a single frequency carrier. | UE | No | FDD only | FR1 only | +| periodicEUTRA-MeasAndReport
Indicates whether the UE supports periodic EUTRA measurement and reporting. It is mandated if the UE supports EUTRA. | UE | CY | No | No | +| pcellT312-r16
Indicates whether the UE supports T312 based fast failure recovery for PCell. | UE | No | No | No | +| preconfiguredUE-AutonomousMeasGap-r17
Indicates whether the UE supports the preconfigured measurement gap with UE-autonomous mechanism for activation and deactivation as specified in TS 38.133 [5]. | UE | No | No | No | +| preconfiguredNW-ControlledMeasGap-r17
Indicates whether the UE supports the preconfigured measurement gap with network-controlled mechanism for activation and deactivation as specified in TS 38.133 [5]. | UE | No | No | No | +| reportAddNeighMeasForPeriodic-r16
Defines whether the UE supports periodic reporting of best neighbour cells per serving frequency, as defined in TS 38.331 [9]. It is optional for RedCap UEs. | UE | CY | No | No | +| serviceLinkPropDelayDiffReporting-r17
Indicates whether the UE supports the reporting of service link propagation delay difference between serving cell and neighbour cell(s). A UE supporting this feature shall also indicate the support of nonTerrestrialNetwork-r17 . | UE | No | No | No | +| shortMeasInterval-r18
Indicates whether the UE supports using SSB periodicity instead of SMTC periodicity for the measurement interval during unknown SCell activation when the SMTC is only configured in measurement object for enhanced unknown SCell activation requirement and performing L1-RSRP measurement in non-DRX mode even DRX is configured during unknown SCell activation.
UE is required to meet the shortened SCell activation delay requirement in TS 38.133 [5] if the feature is supported. | UE | No | No | No | +| simultaneousRxDatassB-DiffNumerology
Indicates whether the UE supports concurrent intra-frequency measurement on serving cell or neighbouring cell and PDCCH or PDSCH reception from the serving cell with a different numerology as defined in clause 8 and 9 of TS 38.133 [5]. | UE | No | No | Yes | +| simultaneousRxDatassB-DiffNumerology-Inter-r16
Indicates whether the UE supports concurrent SSB based inter-frequency measurement without measurement gap on neighbouring cell and PDCCH or PDSCH reception from the serving cell with a different numerology as defined in clause 8 and 9 of TS 38.133 [5]. UE indicates support of this indicates support of interFrequencyMeas-NoGap-r16 . If this parameter is indicated for FR1 and FR2 differently, each indication corresponds to the frequency range where the SSB and PDCCH/PDSCH are received. | UE | No | No | Yes | +| sftd-MeasPSCell
Indicates whether the UE supports SFTD measurements between the PCell and a configured PSCell. If this capability is included in UE-MRDC-Capability, it indicates that the UE supports SFTD measurement between PCell and PSCell in (NG)EN-DC. If this capability is included in UE-NR-Capability, it indicates that the UE supports SFTD measurement between PCell and PSCell in NR-DC. | UE | No | Yes | No | +| sftd-MeasPSCell-NEDC
Indicates whether the UE supports SFTD measurement between the NR PCell and a configured E-UTRA PSCell in NE-DC. | UE | No | Yes | No | +| sftd-MeasNR-Cell
Indicates whether the SFTD measurement with and without measurement gaps between the EUTRA PCell and the NR cells is supported by the UE which is capable of EN-DC/NGEN-DC when EN-DC/NGEN-DC is not configured. The SFTD measurement without gaps can be used when the UE supports at least one EN-DC band combination consisting of the set of the current E-UTRA serving frequencies and the NR frequency where SFTD measurement is configured. In UE-NR-Capability, this field is not used, and UE does not include the field. | UE | No | Yes | No | + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|-----|-----|-----| +| sftd-MeasNR-Neigh
Indicates whether the inter-frequency SFTD measurement with and without measurement gaps between the NR PCell and inter-frequency NR neighbour cells is supported by the UE when MR-DC is not configured. The SFTD measurement without gaps can be used when the UE supports at least one DC or CA band combination consisting of the set of the current NR serving frequencies and the NR frequency where SFTD measurement is configured. | UE | No | Yes | No | +| sftd-MeasNR-Neigh-DRX
Indicates whether the inter-frequency SFTD measurement using DRX off period between the NR PCell and the inter-frequency NR neighbour cells is supported by the UE when MR-DC is not configured. | UE | No | Yes | No | +| ssb-RLM
Indicates whether the UE can perform radio link monitoring procedure based on measurement of SS/PBCH block as specified in TS 38.213 [11] and TS 38.133 [5]. This field shall be set to supported . This applies only to non-shared spectrum channel access. For shared spectrum channel access, ssb-RLM-DynamicChAccess-r16 or ssb-RLM-Semi-StaticChAccess-r16 applies. | UE | Yes | No | No | +| ssb-AndCSI-RS-RLM
Indicates whether the UE can perform radio link monitoring procedure based on measurement of SS/PBCH block and CSI-RS as specified in TS 38.213 [11] and TS 38.133 [5]. If the UE supports this feature, the UE needs to report maxNumberResource-CSI-RS-RLM . This applies only to non-shared spectrum channel access. For shared spectrum channel access, ssb-AndCSI-RS-RLM-r16 applies. | UE | No | No | No | +| ss-SINR-Meas
Indicates whether the UE can perform SS-SINR measurement as specified in TS 38.215 [13]. If this parameter is indicated for FR1 and FR2 differently, each indication corresponds to the frequency range of measured target cell. This applies only to non-shared spectrum channel access. For shared spectrum channel access, ss-SINR-Meas-r16 applies. | UE | No | No | Yes | +| supportedGapPattern
Indicates measurement gap pattern(s) optionally supported by the UE for NR SA, for NR-DC, for NE-DC and for independent measurement gap configuration on FR2 in (NG)EN-DC. The leading / leftmost bit (bit 0) corresponds to the gap pattern 2, the next bit corresponds to the gap pattern 3, as specified in TS 38.133 [5] and so on. The UE shall set the bits corresponding to the measurement gap pattern 13, 14, 17, 18 and 19 to 1 if the UE is an NR standalone capable UE that supports a band in FR2 or if the UE is an (NG)EN-DC capable UE that supports independentGapConfig and supports a band in FR2. | UE | CY | No | No | +| supportedGapPattern-r16
Indicates measurement gap pattern(s) optionally supported by the UE for NR SA, for NR-DC for PRS measurement and NR/E-UTRA RRM measurement. The leading / leftmost bit (bit 0) corresponds to the gap pattern 24, the next bit corresponds to the gap pattern 25, as specified in TS 38.133 [5]. The applicability of the gap patterns 24 and 25 is defined in clause 9.1.2 of TS 38.133 [5]. A UE that indicates support of this capability shall indicate support of NR-DL-PRS-ProcessingCapability-r16 defined in TS 37.355 [22]. | UE | No | No | No | +| supportedGapPattern-NRonly-r16
Indicates measurement gap pattern(s) optionally supported by the UE for NR SA and NR-DC when the frequencies to be measured within this measurement gap are all NR frequencies. The leading / leftmost bit (bit 0) corresponds to the gap pattern 2, the next bit corresponds to the gap pattern 3 and so on. The UE shall set the bits corresponding to the measurement gap pattern 2, 3 and 11 to 1. | UE | FD | No | No | +| supportedGapPattern-NRonly-NEDC-r16
Indicates whether the UE supports gap patterns 2, 3 and 11 in NE-DC when the frequencies to be measured within this measurement gap are all NR frequencies. | UE | No | No | No | + +### 4.2.9a *MeasAndMobParametersMRDC* + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----|--------------|--------------| +| condHandoverWithSCG-ENDC-r17
Indicates whether the UE supports conditional handover with NR SCG configuration for EN-DC. The UE indicating support of this feature shall also indicate the support of cho-r16 as specified in TS 36.306 [15] and at least one EN-DC band combination. | UE | No | No | No | +| condHandoverWithSCG-NEDC-r17
Indicates whether the UE supports conditional handover with E-UTRA SCG configuration for NE-DC. The UE indicating support of this feature shall also indicate the support of condHandover-r16 and at least one NE-DC band combination. | UE | No | No | No | +| condPSCellChangeFDD-TDD-r16
Indicates whether the UE supports conditional PSCell change between FDD and TDD cells. The parameter can only be set if condPSCellChange-r16 is set for both FDD and TDD. | UE | No | No | No | +| condPSCellChangeFR1-FR2-r16
Indicates whether the UE supports conditional PSCell change between FR1 and FR2. The parameter can only be set if condPSCellChange-r16 is set for both FR1 and FR2. | UE | No | No | No | +| independentGapConfig-maxCC-r17
This field indicates whether the UE supports two independent measurement gap configurations for FR1 and FR2 as specified in clause 9.1.2 of TS 38.133 [5] while the number of configured serving cells is less than or equal to the indicated number.

The capability signaling includes the following parameters:
  • - fr1-Only-r17 indicates the maximum number of configured serving cells when E-UTRA and NR FR1 serving cells are configured
  • - fr2-Only-r17 is not applicable when the field independentGapConfig-maxCC-r17 is included in UE-MRDC-Capability.
  • - fr1-AndFR2-r17 indicates the maximum number of configured serving cells when E-UTRA and NR FR2 serving cells are configured or when E-UTRA, NR FR1 and NR FR2 serving cells are configured.
The absence of the fr1-Only-r17 field indicates that per-FR gap is not supported when E-UTRA and NR FR1 serving cells are configured. Absence of the fr1-AndFR2 field indicates that per-FR-gap is not supported when E-UTRA and NR FR2 serving cells are configured or when E-UTRA, NR FR1 and NR FR2 serving cells are configured. Value "1" or "2" for fr1-Only-r17 or fr1-AndFR2-r17 indicates the support of per-FR gap when PCell and "1" additional CC are configured.

UE indicating support of this feature in UE-MRDC-Capability shall not indicate support of independentGapConfig in UE-MRDC-Capability . | UE | No | No | No | +| inter-SN-condPSCellChangeFDD-TDD-ENDC-r17
Indicates whether the UE supports inter SN conditional PSCell change between FDD and TDD cells in EN-DC.
The parameter can only be set
  • - if mn-InitiatedCondPSCellChange-FR1FDD-ENDC-r17 is supported and at least one of mn-InitiatedCondPSCellChange-FR1TDD-ENDC-r17 and mn-InitiatedCondPSCellChange-FR2TDD-ENDC-r17 is supported; or
  • - if sn-InitiatedCondPSCellChange-FR1FDD-ENDC-r17 is supported and at least one of sn-InitiatedCondPSCellChange-FR1TDD-ENDC-r17 and sn-InitiatedCondPSCellChange-FR2TDD-ENDC-r17 is supported.
| UE | No | No | No | +| inter-SN-condPSCellChangeFDD-TDD-NRDC-r17
Indicates whether the UE supports inter SN conditional PSCell change between FDD and TDD cells in NR-DC. The parameter can only be set if mn-InitiatedCondPSCellChangeNRDC-r17 is set for FDD band(s) and TDD band(s), or sn-InitiatedCondPSCellChangeNRDC-r17 is set for FDD band(s) and TDD band(s). | UE | No | No | No | + +| | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|----|----| +| inter-SN-condPSCellChangeFR1-FR2-ENDC-r17
Indicates whether the UE supports inter SN conditional PSCell change between FR1 and FR2 cells in EN-DC.
The parameter can only be set:
  • - if mn-InitiatedCondPSCellChange-FR2TDD-ENDC-r17 is supported and at least one of mn-InitiatedCondPSCellChange-FR1TDD-ENDC-r17 and mn-InitiatedCondPSCellChange-FR1FDD-ENDC-r17 is supported; or
  • - if sn-InitiatedCondPSCellChange-FR2TDD-ENDC-r17 is supported and at least one of sn-InitiatedCondPSCellChange-FR1TDD-ENDC-r17 and sn-InitiatedCondPSCellChange-FR1FDD-ENDC-r17 is supported.
| UE | No | No | No | +| inter-SN-condPSCellChangeFR1-FR2-NRDC-r17
Indicates whether the UE supports inter SN conditional PSCell change between FR1 and FR2 cells. The parameter can only be set if mn-InitiatedCondPSCellChangeNRDC-r17 is set for FR1 band(s) and FR2 band(s), or sn-InitiatedCondPSCellChangeNRDC-r17 is set for FR1 band(s) and FR2 band(s). | UE | No | No | No | +| mn-InitiatedCondPSCellChange-FR1FDD-ENDC-r17
Indicates whether the UE supports MN initiated conditional PSCell change within all supported FR1-FDD bands in EN-DC, which is configured by E-UTRA conditionalReconfiguration field using MN configured measurement as triggering condition. The UE supporting this feature shall also support 2 trigger events for same execution condition in MN initiated conditional PSCell change in EN-DC. | UE | No | No | No | +| mn-InitiatedCondPSCellChange-FR1TDD-ENDC-r17
Indicates whether the UE supports MN initiated conditional PSCell change within all supported FR1-TDD bands in EN-DC, which is configured by E-UTRA conditionalReconfiguration field using MN configured measurement as triggering condition. The UE supporting this feature shall also support 2 trigger events for same execution condition in MN initiated conditional PSCell change in EN-DC. | UE | No | No | No | +| mn-InitiatedCondPSCellChange-FR2TDD-ENDC-r17
Indicates whether the UE supports MN initiated conditional PSCell change within all supported FR2-TDD bands in EN-DC, which is configured by E-UTRA conditionalReconfiguration field using MN configured measurement as triggering condition. The UE supporting this feature shall also support 2 trigger events for same execution condition in MN initiated conditional PSCell change in EN-DC. | UE | No | No | No | +| pscellT312-r16
Indicates whether the UE supports T312 based fast failure recovery for PSCell. | UE | No | No | No | +| sn-InitiatedCondPSCellChange-FR1FDD-ENDC-r17
Indicates whether the UE supports SN initiated inter-SN conditional PSCell change within all supported FR1-FDD bands in EN-DC, which is configured by E-UTRA conditionalReconfiguration field using SN configured measurement as triggering condition. The UE supporting this feature shall also support 2 trigger events for same execution condition in SN initiated inter-SN conditional PSCell change in EN-DC. | UE | No | No | No | +| sn-InitiatedCondPSCellChange-FR1TDD-ENDC-r17
Indicates whether the UE supports SN initiated inter-SN conditional PSCell change within all supported FR1-TDD bands in EN-DC, which is configured by E-UTRA conditionalReconfiguration field using SN configured measurement as triggering condition. The UE supporting this feature shall also support 2 trigger events for same execution condition in SN initiated inter-SN conditional PSCell change in EN-DC. | UE | No | No | No | +| sn-InitiatedCondPSCellChange-FR2TDD-ENDC-r17
Indicates whether the UE supports SN initiated inter-SN conditional PSCell change within all supported FR2-TDD bands in EN-DC, which is configured by E-UTRA conditionalReconfiguration field using SN configured measurement as triggering condition. The UE supporting this feature shall also support 2 trigger events for same execution condition in SN initiated inter-SN conditional PSCell change in EN-DC. | UE | No | No | No | + +### 4.2.10 Inter-RAT parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|-----|--------------| +| mfbi-EUTRA
Indicates whether the UE supports the mechanisms defined for cells broadcasting multi band information i.e. comprehending multiBandInfoList defined in TS 36.331 [17]. | UE | Yes | No | +| modifiedMPR-BehaviorEUTRA
modifiedMPR-Behavior in 4.3.5.10, TS 36.306 [15]. | UE | No | No | +| multiNS-Pmax-EUTRA
multiNS-Pmax defined in 4.3.5.16, TS 36.306 [15]. | UE | No | No | +| ne-DC
Indicates whether the UE supports NE-DC as specified in TS 37.340 [7]. | UE | No | No | +| nr-HO-ToEN-DC-r16
Indicates whether the UE supports inter-RAT handover from NR to EN-DC while NR-DC or NE-DC is not configured as defined in TS 36.306 [15]. It is mandated if the UE supports EN-DC. | UE | CY | No | +| rs-SINR-MeasEUTRA
rs-SINR-Meas in 4.3.6.13, TS 36.306 [15]. | UE | No | No | +| rsrqMeasWidebandEUTRA
rsrqMeasWideband in 4.3.6.2, TS 36.306 [15]. If this parameter is indicated for FDD and TDD differently, each indication corresponds to the duplex mode of measured target cell. | UE | No | Yes | +| supportedBandListEUTRA
supportedBandListEUTRA defined in 4.3.5.1, TS 36.306 [15]. | UE | No | No | +| supportedBandListUTRA-FDD-r16
Radio frequency bands defined in 4.5.7, TS 25.306 [20]. | UE | No | No | + +4.2.10.1 Void + +4.2.10.2 Void + +4.2.11 Void + +4.2.12 Void + +### 4.2.13 IMS Parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----|--------------|-----------------------| +| voiceFallbackIndicationEPS-r16
Indicates whether the UE supports voiceFallbackIndication in RRRelease and MobilityFromNRCommand . If this field is included, the UE shall support IMS voice over NR and IMS voice over E-UTRA via EPC. | UE | No | No | No | +| voiceOverEUTRA-5GC
Indicates whether the UE supports IMS voice over E-UTRA via 5GC. It is mandated to the UE if the UE is capable of IMS voice over E-UTRA via 5GC. Otherwise, the UE does not include this field. If this field is included and the UE is capable of E-UTRA with EPC, the UE shall support IMS voice over E-UTRA via EPC. | UE | No | No | No | +| voiceOverNR, voiceOverNR-r17
Indicates whether the UE supports IMS voice over NR. It is mandated to the UE if the UE is capable of IMS voice over NR (including SNPN if the UE is SNPN capable). Otherwise, the UE does not include this field. If this field is included and the UE is capable of E-UTRA with EPC, the UE shall support IMS voice over E-UTRA via EPC. | UE | No | No | Yes (Incl FR2-2 DIFF) | +| voiceOverSCG-BearerEUTRA-5GC
Indicates whether the UE supports IMS voice over SCG bearer of NE-DC. | UE | No | No | N/A | + +NOTE: In this release of specification, IMS voice over split bearer is not supported for NR-DC and NE-DC. + +### 4.2.14 RRC buffer size + +The RRC buffer size is defined as the maximum overall RRC configuration size that the UE is required to store. The RRC buffer size is 45Kbytes. + +### 4.2.15 IAB Parameters + +#### 4.2.15.1 Mandatory IAB-MT features + +Table 4.2.15.1-1, Table 4.2.15.1-2 and Table 4.2.15.1-3 capture feature groups, which are mandatory for an IAB-MT. All other feature groups or components of the feature groups as captured in TR 38.822 [24] as well as capabilities specified in this specification are optional for an IAB-MT, unless indicated otherwise. + +**Table 4.2.15.1-1: Layer-1 mandatory features for IAB-MT** + +| Features | Index | Feature group | Components | Additional information | +|------------------------------------------------------|-------|--------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------| +| 0. Waveform, modulation, subcarrier spacings, and CP | 0-1 | CP-OFDM waveform for DL and UL | 1) CP-OFDM for DL
2) CP-OFDM for UL | | +| | 0-3 | DL modulation scheme | 1) QPSK modulation
2) 16QAM modulation
3) 64QAM modulation for FR1 | | +| | 0-4 | UL modulation scheme | 1) QPSK modulation
2) 16QAM modulation | | +| 1. Initial access and mobility | 1-1 | Basic initial access channels and procedures | 1) RACH preamble format
2) SS block based RRM measurement
3) Broadcast SIB reception including RMSI/OSI and paging | Only 1 preamble for component 1), component 2), component 3) except paging | +| | 1-3 | SS block based RLM | SS-SINR measurement | | +| 2. MIMO | 2-1 | Basic PDSCH reception | 1) Data RE mapping
2) Single layer transmission
3) Support one TCI state | | +| | 2-5 | Basic downlink DMRS for scheduling type A | 1) Support 1 symbol FL DMRS without additional symbol(s)
2) Support 1 symbol FL DMRS and 1 additional DMRS symbol
3) Support 1 symbol FL DMRS and 2 additional DMRS symbols for at least one port. | | +| | 2-6 | Basic downlink DMRS for scheduling type B | 1) Support 1 symbol FL DMRS without additional symbol(s)
2) Support 1 symbol FL DMRS and 1 additional DMRS symbol | | +| | 2-12 | Basic PUSCH transmission | Data RE mapping
Single layer (single Tx) transmission
Single port, single resource SRS transmission (SRS set use is configured as for codebook) | | +| | 2-16 | Basic uplink DMRS (uplink) for scheduling type A | 1) Support 1 symbol FL DMRS without additional symbol(s)
2) Support 1 symbol FL DMRS and 1 additional DMRS symbols
3) Support 1 symbol FL DMRS and 2 additional DMRS symbols | | +| | 2-16a | Basic uplink DMRS for scheduling type B | 1) Support 1 symbol FL DMRS without additional symbol(s)
2) Support 1 symbol FL DMRS and 1 additional DMRS symbol | | +| | 2-22 | Aperiodic beam report | Support aperiodic report on PUSCH | | +| | 2-32 | Basic CSI feedback | 1) Type I single panel codebook based PMI (further discuss which mode or both to be supported as mandatory)
2) 2Tx codebook for FR1 and FR2
3) 4Tx codebook for FR1
4) 8Tx codebook for FR1 when configured as wideband CSI report
7) a-CSI on PUSCH (at least Z value >= 14 symbols, detail processing time to be discussed separately)
further check a-CSI on p-CSI-RS and/or SP-CSI-RS from component-7 | | +| | 2-50 | Basic TRS | 1) Support of TRS (mandatory)
2) All the periodicity are supported. | | +| | 2-52 | Basic SRS | 1) Support 1 port SRS transmission
2) Support periodic/aperiodic SRS transmission | | +| 3. DL control channel and procedure | 3-1 | Basic DL control channel | 1) One configured CORESET per BWP per cell in addition to CORESET0
- CORESET resource allocation of 6RB bit-map and duration of 1 – 3 OFDM symbols for FR1
- For type 1 CSS without dedicated RRC configuration and for type 0, 0A, and 2 CSSs, CORESET resource allocation of 6RB bit-map and duration 1-3 OFDM symbols for FR2
- For type 1 CSS with dedicated RRC configuration and for type 3 CSS, UE specific SS, CORESET resource allocation of 6RB bit-map and duration 1-2 OFDM symbols for FR2
- REG-bundle sizes of 2/3 RBs or 6 RBs
- Interleaved and non-interleaved CCE-to-REG mapping
- Precoder-granularity of REG-bundle size
- PDCCH DMRS scrambling determination
- TCI state(s) for a CORESET configuration | | + +| | | | | | +|-------------------------------------|-----|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| | | |

2) CSS and UE-SS configurations for unicast PDCCH transmission per BWP per cell

  • - PDCCH aggregation levels 1, 2, 4, 8, 16
  • - UP to 3 search space sets in a slot for a scheduled SCell per BWP

This search space limit is before applying all dropping rules.

  • - For type 1 CSS with dedicated RRC configuration, type 3 CSS, and UE-SS, the monitoring occasion is within the first 3 OFDM symbols of a slot
  • - For type 1 CSS without dedicated RRC configuration and for type 0, 0A, and 2 CSS, the monitoring occasion can be any OFDM symbol(s) of a slot, with the monitoring occasions for any of Type 1- CSS without dedicated RRC configuration, or Types 0, 0A, or 2 CSS configurations within a single span of three consecutive OFDM symbols within a slot

3) Monitoring DCI formats 0_0, 1_0, 0_1, 1_1

4) Number of PDCCH blind decodes per slot with a given SCS follows Case 1-1 table

5) Processing one unicast DCI scheduling DL and one unicast DCI scheduling UL per slot per scheduled CC for FDD

| | +| 4. UL control channel and procedure | 4-1 | Basic UL control channel |

1) PUCCH format 0 over 1 OFDM symbols once per slot

2) PUCCH format 0 over 2 OFDM symbols once per slot with frequency hopping as "enabled"

3) PUCCH format 1 over 4 – 14 OFDM symbols once per slot with intra-slot frequency hopping as "enabled"

5) One SR configuration per PUCCH group

6) HARQ-ACK transmission once per slot with its resource/timing determined by using the DCI

7) SR/HARQ multiplexing once per slot using a PUCCH when SR/HARQ-ACK are supposed to be sent by overlapping PUCCH resources with the same starting symbols in a slot

8) HARQ-ACK piggyback on PUSCH with/without aperiodic CSI once per slot when the starting OFDM symbol of the PUSCH is the same as the starting OFDM symbols of the PUCCH resource that HARQ-ACK would have been transmitted on

9) Semi-static beta-offset configuration for HARQ-ACK

10) Single group of overlapping PUCCH/PUCCH and overlapping PUCCH/PUSCH s per slot per PUCCH cell group for control multiplexing

| | + +| | | | | | +|-------------------------------|------|--------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| | 4-10 | Dynamic HARQ-ACK codebook | Dynamic HARQ-ACK codebook | | +| 5. Scheduling /HARQ operation | 5-1 | Basic scheduling/HARQ operation | 1) Frequency-domain resource allocation
- RA Type 0 only and Type 1 only for PDSCH without interleaving
- RA Type 1 for PUSCH without interleaving
2) Time-domain resource allocation
- 1-14 OFDM symbols for PUSCH once per slot
- One unicast PDSCH per slot
- Starting symbol, and duration are determined by using the DCI
- PDSCH mapping type A with 7-14 OFDM symbols
- PUSCH mapping type A and type B
- For type 1 CSS without dedicated RRC configuration and for type 0, 0A, and 2 CSS, PDSCH mapping type A with {4-14} OFDM symbols and type B with {2, 4, 7} OFDM symbols
3) TBS determination
4) Nominal UE processing time for N1 and N2 (Capability #1)
5) HARQ process operation with configurable number of DL HARQ processes of up to 16
6) Cell specific RRC configured UL/DL assignment for TDD
7) Dynamic UL/DL determination based on L1 scheduling DCI with/without cell specific RRC configured UL/DL assignment
9) In TDD support at most one switch point per slot for actual DL/UL transmission(s)
10) DL scheduling slot offset K0=0
12) UL scheduling slot offset K2<=12

For type 1 CSS without dedicated RRC configuration and for type 0, 0A, and 2 CSS, interleaving for VRB-to-PRB mapping for PDSCH | | +| 6. CA/DC, BWP, SUL | 6-1 | Basic BWP operation with restriction | 1) 1 UE-specific RRC configured DL BWP per carrier
2) 1 UE-specific RRC configured UL BWP per carrier
3) RRC reconfiguration of any parameters related to BWP
4) BW of a UE-specific RRC configured BWP includes BW of CORESET#0 (if CORESET#0 is present) and SSB for PCell/PSCell (if configured) and BW of the UE-specific RRC configured BWP includes SSB for SCell if there is SSB on SCell | | +| 7. Channel coding | 7-1 | Channel coding | 1) LDPC encoding and associated functions for data on DL and UL
2) Polar encoding and associated functions for PBCH, DCI, and UCI
3) Coding for very small blocks | | +| 8. UL TPC | 8-3 | Basic power control operation | 1) Accumulated power control mode for closed loop
2) 1 TPC command loop for PUSCH, PUCCH respectively
3) One or multiple DL RS configured for pathloss estimation
4) One or multiple p0-alpha values configured for open loop PC
5) PUSCH power control
6) PUCCH power control
7) PRACH power control
8) SRS power control
9) PHR | | + +**Table 4.2.15.1-2: Layer-2 and Layer-3 mandatory features for IAB-MT** + +| Features | Index | Feature group | Components | Additional information | +|------------|-------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0. General | N/A | IAB procedures | 1) Routing using BAP protocol, as specified in TS 38.340 [23]
2) Bearer mapping using BAP protocol, as specified in TS 38.340 [23]
3) IAB-node IP address signalling over RRC, as specified in TS 38.331 [9] | | +| 1. PDCP | 1-0 | Basic PDCP procedures | 1) (de)Ciphering on SRB
2) Integrity protection on SRB
3) Timer based SDU discard
4) Re-ordering and in-order delivery
6) Duplicate discarding
7) 18bits SN | | +| 2. RLC | 2-0 | Basic RLC procedures | 1) RLC TM
2) RLC AM with 18bits SN
3) SDU discard | | +| | 2-4 | NR RLC SN size for SRB | NR RLC SN size for SRB | | +| 3. MAC | 3-0 | Basic MAC procedures | 1) RA procedure on PCell
2) IAB-MT initiated RA procedure (including for beam recovery purpose)
3) NW initiated RA procedure (i.e. based on PDCCH)
4) Support of ssb-Threshold and association between preamble/PRACH occasion and SSB
5) Preamble grouping
6) UL single TA maintenance
7) HARQ operation for DL and UL
8) LCH prioritization
9) Prioritized bit rate
10) Multiplexing
11) SR with single SR configuration
12) BSR
13) PHR
14) 8bits and 16bits L field | | +| 9. RRC | 9-1 | RRC buffer size | Maximum overall RRC configuration size | 45 Kbytes | +| | 9-2 | RRC processing time | 1) RRC connection establishment
2) RRC connection resume without SCell addition/release and SCG establishment/modification/release
3) RRC connection reconfiguration without SCell addition/release and SCG establishment/modification/release
4) RRC connection re-establishment.
5) RRC connection reconfiguration with sync procedure
6) RRC connection reconfiguration with SCell addition/release or SCG establishment/modification/release
7) RRC connection resume
8) Initial security activation
9) Counter check
10) UE capability transfer | 1) to 3) 10ms
4) 10ms
5): 10ms + additional delay (cell search time and synchronization) defined in TS 38.133
6) and 7) 16ms
7) 10 or 6ms (See details in clause 12, TS 38.331)
8) and 9) 5ms
10) 80ms | + +**Table 4.2.15.1-3: RF/RRM mandatory features for IAB-MT** + +| Features | Index | Feature group | Components | Additional information | +|---------------------|-------|--------------------------------|--------------------------------|------------------------| +| 1. System parameter | 1-2 | 64QAM modulation for FR2 PDSCH | 64QAM modulation for FR2 PDSCH | | +| | 1-3 | 64QAM for PUSCH | 64QAM for PUSCH | | + +##### 4.2.15.1a Mandatory mobile IAB-MT features + +Mobile IAB-MT shall apply the same capabilities as IAB-MT unless indicated otherwise. In addition, it is mandatory for mobile IAB-MT to support the following features: + +- Acquisition of *gNB-ID-Length* from SIB1, as specified in TS 38.331 [9]. +- Cell barring based on *mobileIAB-Support*, as specified in TS 38.331 [9]. +- Inclusion of *mobileIAB-NodeIndication*, as specified in TS 38.331 [9]. + +#### 4.2.15.2 General Parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----|--------------|--------------| +| bh-RLF-DetectionRecovery-Indication-r17
Indicates whether the IAB-MT supports BH RLF detection indication and BH RLF recovery indication handling as specified in TS 38.340 [23] | IAB-MT | No | No | No | +| bh-RLF-Indication-r16
Indicates whether the IAB-MT supports BH RLF indication handling as specified in TS 38.331 [9] and in TS 38.340 [23] | IAB-MT | No | No | No | +| directSN-AdditionFirstRRC-IAB-r16
Indicates whether the IAB-MT supports direct SN addition in the first RRC connection reconfiguration after RRC connection establishment. | IAB-MT | No | No | No | + +#### 4.2.15.3 SDAP Parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----|--------------|--------------| +| sdap-QoS-IAB-r16
Indicates whether the IAB-MT supports flow-based QoS and multiple flows to 1 DRB mapping, as specified in TS 37.324 [25]. | IAB-MT | No | No | No | +| sdapHeaderIAB-r16
Indicates whether the IAB-MT supports UL SDAP header and SDAP End-marker, as specified in TS 37.324 [25]. | IAB-MT | No | No | No | + +#### 4.2.15.4 PDCP Parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----|--------------|--------------| +| drb-IAB-r16
Indicates whether the IAB-MT supports DRB configuration including split DRB with one UL path, (de)ciphering on DRB and PDCP status reporting. | IAB-MT | No | No | No | +| non-DRB-IAB-r16
Indicates whether the IAB-MT supports SRB2 configuration without a DRB, as specified in TS 38.331 [9]. | IAB-MT | No | No | No | + +#### 4.2.15.5 BAP Parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----|--------------|--------------| +| bapHeaderRewriting-Rerouting-r17
Indicates whether the IAB-MT supports BAP header rewriting for inter-donor-DU rerouting, as specified in TS 38.340 [23] and TS 38.300 [28]. IAB-donor-DUs can belong to the same or different IAB-donor CUs. | IAB-MT | No | No | No | +| bapHeaderRewriting-Routing-r17
Indicates whether the IAB-MT supports BAP header rewriting for inter-donor CU partial migration, inter-donor-CU RLF recovery and inter-donor-CU topology redundancy, as specified in TS 38.340 [23] and TS 38.300 [28]. | IAB-MT | No | No | No | +| flowControlBH-RLC-ChannelBased-r16
Indicates whether the IAB-MT supports flow control procedures and flow control feedback per backhaul RLC channel, as specified in TS 38.340 [23]. | IAB-MT | No | No | No | +| flowControlRouting-ID-Based-r16
Indicates whether the IAB-MT supports flow control procedures and flow control feedback per Routing ID, as specified in TS 38.340 [23]. | IAB-MT | No | No | No | + +#### 4.2.15.6 MAC Parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----|--------------|--------------| +| lcg-ExtensionIAB-r17
Indicates whether the IAB-MT supports extended logical channel group as specified in TS 38.321 [8]. A UE supporting this feature shall also support Extended Buffer Status Report formats and Extended Pre-emptive BSR formats (if preEmptiveBSR-r16 is supported). | IAB-MT | No | No | No | +| lcid-ExtensionIAB-r16
Indicates whether the IAB-MT supports extended Logical Channel ID space using two-octet eLCID, as specified in TS 38.321 [8]. | IAB-MT | No | No | No | +| preEmptiveBSR-r16
Indicates whether the IAB-MT supports Pre-emptive BSR as specified in TS 38.321 [8]. | IAB-MT | No | No | No | + +#### 4.2.15.7 Physical layer parameters + +##### 4.2.15.7.1 BandNR parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| handoverIntraF-IAB-r16
Indicates whether the IAB-MT supports intra-frequency HO. It indicates the support for intra-frequency HO from the corresponding duplex mode if this capability is included in fdd-Add-UE-NR-Capabilities or tdd-Add-UE-NR-Capabilities . It indicates the support for intra-frequency HO in the corresponding frequency range if this capability is included in fr1-Add-UE-NR-Capabilities or fr2-Add-UE-NR-Capabilities . IAB-MT shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands and all TDD-FR2 bands respectively. | Band | No | N/A | N/A | +| multipleTCI
Indicates whether IAB-MT supports more than one TCI state configurations per CORESET. UE is only required to track one active TCI state per CORESET. UE is required to support minimum between 64 and number of configured TCI states indicated by tci-StatePDSCH . | Band | No | N/A | N/A | +| rasterShift7dot5-IAB-r16
Indicates whether the IAB-MT supports 7.5kHz UL raster shift in the indicated band. | Band | No | N/A | N/A | + + + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----|--------------|--------------| +| case6-TimingAlignmentReception-IAB-r17
Indicates whether the IAB-MT supports case 6 timing alignment reception and signalling to the parent-node that case 6 timing mode is required for simultaneous transmission as specified in TS 38.213 [11]. | IAB-MT | No | No | No | +| case7-TimingAlignmentReception-IAB-r17
Indicates whether the IAB-MT supports case 7 timing offset indication reception and case 7 timing at parent-node indication reception as specified in TS 38.213 [11]. | IAB-MT | No | No | No | +| dft-S-OFDM-WaveformUL-IAB-r16
Indicates whether the IAB-MT supports DFT-S-OFDM waveform for UL and transform precoding for single-layer PUSCH. | IAB-MT | No | No | No | +| dci-25-AI-RNTI-Support-IAB-r16
Indicates the support of monitoring DCI Format 2_5 scrambled by AI-RNTI for indication of soft resource availability to an IAB node as specified in TS 38.212 [10]. | IAB-MT | No | No | No | +| directionalCollisionDC-IAB-r17
Indicates the support for directional collision handling between MCG and SCG cell(s) of the dual parent nodes for simultaneous operation in inter-donor and/or intra-donor DC operation. | IAB-MT | No | No | No | +| dl-tx-PowerAdjustment-IAB-r17
Indicates the support of desired DL Tx power adjustment reporting and DL Tx power adjustment reception. | IAB-MT | No | No | No | +| desired-ul-tx-PowerAdjustment-r17
Indicates the support of Desired IAB-MT PSD range reporting. | IAB-MT | No | No | No | +| fdm-SoftResourceAvailability-DynamicIndication-r17
Indicates the support of monitoring DCI Format 2_5 scrambled by AI-RNTI for indication of FDM soft resource availability to an IAB-node. | IAB-MT | No | No | No | +| guardSymbolReportReception-IAB-r16
Indicates the support of DesiredGuardSymbols reporting and ProvidedGuardSymbols reception as specified in TS 38.213 [11]. | IAB-MT | No | No | No | +| guardSymbolReportReception-IAB-r17
Indicates the support of extended DesiredGuardSymbols reporting and ProvidedGuardSymbols reception to new switching scenarios case#6 and case#7 as specified in TS 38.213 [11].

UE indicating support of this feature shall also indicate support of one or more of case6-TimingAlignmentReception-IAB-r17 and case7-TimingAlignmentReception-IAB-r17 .
NOTE: If an IAB node does not support a certain timing mode (Case 6, Case 7), the reported/provided values shall be ignored. | IAB-MT | No | No | No | +| pdsch-MappingTypeA
Indicates whether the IAB-MT supports receiving PDSCH using PDSCH mapping type A with less than seven symbols. | IAB-MT | No | No | No | +| pucch-F2-WithFH
Indicates whether the IAB-MT supports transmission of a PUCCH format 2 (2 OFDM symbols in total) with frequency hopping in a slot. | IAB-MT | No | No | Yes | +| pucch-F3-WithFH
Indicates whether the IAB-MT supports transmission of a PUCCH format 3 (4~14 OFDM symbols in total) with frequency hopping in a slot. | IAB-MT | No | No | Yes | +| restricted-IAB-DU-BeamReception-r17
Indicates the support of restricted IAB-DU beam reception. | IAB-MT | No | No | No | +| recommended-IAB-MT-BeamTransmission-r17
Indicates the support of recommended IAB-MT beam transmission for DL and UL beam. | IAB-MT | No | No | No | +| separateSMTC-InterIAB-Support-r16
Indicates the support of up to 4 SMTCs configurations per frequency location, including IAB-specific SMTC window periodicities. | IAB-MT | No | No | No | +| separateRACH-IAB-Support-r16
Indicates the support of separate RACH configurations including new IAB-specific offset and scaling factors. | IAB-MT | No | No | No | +| t-DeltaReceptionSupport-IAB-r16
Indicates the support of T_delta reception for case 1 OTA timing alignment as specified in TS 38.213 [11]. | IAB-MT | No | No | No | +| ul-flexibleDL-SlotFormatSemiStatic-IAB-r16
Indicates the support of semi-static configuration/indication of UL-Flexible-DL slot formats for IAB-MT resources. | IAB-MT | No | No | No | + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----|----|----| +| ul-flexibleDL-SlotFormatDynamics-IAB-r16
Indicates the support of dynamic indication of UL-Flexible-DL slot formats for IAB-MT resources. | IAB-MT | No | No | No | +| updated-T-DeltaRangeReception-r17
Indicates the support of updated T_Delta range reception.
UE indicating support of this feature shall also support case6-TimingAlignmentReception-IAB-r17 . | IAB-MT | No | No | No | + +#### 4.2.15.8 MeasAndMobParameters Parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|-----|--------------|--------------| +| eventA-MeasAndReport
Indicates whether the IAB-MT supports NR measurements and events A triggered reporting as specified in TS 38.331 [9]. | IAB-MT | Yes | Yes | No | +| handoverInterF
Indicates whether the IAB-MT supports inter-frequency HO. It indicates the support for inter-frequency HO from the corresponding duplex mode if this capability is included in fdd-Add-UE-NR-Capabilities or tdd-Add-UE-NR-Capabilities. It indicates the support for inter-frequency HO from the corresponding frequency range if this capability is included in fr1-Add-UE-NR-Capabilities or fr2-Add-UE-NR-Capabilities. | IAB-MT | No | Yes | Yes | +| mfbi-IAB-r16
Indicates whether the IAB-MT supports multiple frequency band indication. | IAB-MT | No | No | No | +| intraAndInterF-MeasAndReport
Indicates whether the IAB-MT supports NR intra-frequency and inter-frequency measurements and at least periodical reporting. | IAB-MT | Yes | Yes | No | + +#### 4.2.15.9 MR-DC Parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----|--------------|--------------| +| f1c-OverEUTRA-r16
Indicates whether the IAB-MT supports F1-C signalling over DLInformationTransfer and ULInformationTransfer messages via MN when IAB-MT operates in EN-DC mode, as specified in TS 36.331 [17]. | IAB-MT | No | No | No | +| scg-DRB-NR-IAB-r16
Indicates whether the IAB-MT supports SCG DRB with NR PDCP when IAB-MT operates in EN-DC mode. | IAB-MT | No | No | No | +| interNR-MeasEUTRA-IAB-r16
Indicates whether the IAB-MT supports NR measurement and reports while in EUTRA connected and event B1-based measurement and reports while in EUTRA connected. | IAB-MT | No | No | No | + +#### 4.2.15.10 NRDC Parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----|--------------|--------------| +| f1c-OverNR-RRC-r17
Indicates whether the IAB-MT supports F1-C signalling over DLInformationTransfer and ULInformationTransfer messages via MN when IAB-MT operates in NR-DC and MN is the non-F1-termination node or via SN when IAB-MT operates in NR-DC and SN is the non-F1-termination node, as specified in TS 38.401 [33] and TS 37.340 [7]. | IAB-MT | No | No | No | +| simultaneousRxTx-IAB-MultipleParents-r17
Indicates the support of simultaneous transmission and reception of an IAB-node from multiple parent nodes. | BC | No | No | No | + +### 4.2.16 Sidelink Parameters + +#### 4.2.16.1 Sidelink Parameters in NR + +##### 4.2.16.1.1 Sidelink General Parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|-----|--------------|--------------| +| accessStratumReleaseSidelink-r16
Indicates the access stratum release for NR sidelink communication the UE supports as specified in TS 38.331 [9]. | UE | Yes | No | No | +| multipathRelayUE-N3C-r18
Indicates whether L2 multi-path relay UE operation using non-3GPP connection is supported by the UE. | UE | No | No | No | +| multipathRelayUE-PC5L2-r18
Indicates whether L2 multi-path relay UE operation using PC5 connection is supported by the UE. | UE | No | No | No | +| multipathRemoteUE-N3C-r18
Indicates whether L2 multi-path remote UE operation using non-3GPP connection is supported by the UE. | UE | No | No | No | +| multipathRemoteUE-PC5L2-r18
Indicates whether L2 multi-path remote UE operation using PC5 connection is supported by the UE. | UE | No | No | No | +| pdcP-DuplicationMoreThanOneUuRLC-r18
Indicates whether L2 multi-path remote UE supports PDCP duplication with more than one RLC entity over Uu interface in L2 multi-path relay. | UE | No | No | No | +| posSIB-ForwardingSupported-r18
Indicates whether the UE, when operating as an NR L2 sidelink relay UE, supports forwarding of posSIBs. The UE capable of operation as an NR L2 sidelink relay UE shall set this field to supported if it is capable of obtaining posSIBs. | UE | CY | No | No | +| relayUE-Operation-L2-r17
Indicates whether NR L2 sidelink relay UE operation is supported by the UE. | UE | No | No | No | +| relayUE-U2U-OperationL2-r18
Indicates whether L2 U2U sidelink relay UE operation is supported by the UE. | UE | No | No | No | +| remoteUE-IndirectPathAddChangeToIdleInactiveRelay-r18
Indicates whether L2 multi-path remote UE supports indirect path addition or indirect path change with target relay UE in RRC_IDLE or RRC_INACTIVE state. | UE | No | No | No | +| remoteUE-Operation-L2-r17
Indicates whether NR L2 sidelink remote UE operation is supported by the UE. | UE | No | No | No | +| remoteUE-PathSwitchToIdleInactiveRelay-r17
Indicates whether L2 sidelink remote UE supports direct to indirect path switch with target relay in RRC_IDLE or RRC_INACTIVE state. | UE | No | No | No | +| remoteUE-U2N-PathSwitchOperationL2-r18
Indicates whether enhanced NR L2 U2N remote UE operation for indirect-to-indirect path switch and inter-gNB path switch is supported by the UE. | UE | No | No | No | +| remoteUE-U2U-OperationL2-r18
Indicates whether L2 U2U sidelink remote UE operation is supported by the UE. | UE | No | No | No | +| sfn-DFN-OffsetSupported-r18
Indicates whether the UE, when operating as an NR L2 sidelink relay UE, supports indication of the offset between SFN and DFN timelines. | UE | No | No | No | + +##### 4.2.16.1.2 Sidelink PDCP Parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|----------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----|--------------|--------------| +| outOfOrderDeliverySidelink-r16
Indicates whether UE supports out of order delivery of data to upper layers by PDCP for sidelink. | UE | No | No | No | +| pdcp-DuplicationDRB-sidelink-r18
Indicates whether the UE supports CA-based duplication over sidelink DRB as specified in TS 38.323 [16]. | UE | No | No | No | +| pdcp-DuplicationSRB-sidelink-r18
Indicates whether the UE supports CA-based duplication over sidelink SRB1/2/3 as specified in TS 38.323 [16]. | UE | No | No | No | + +##### 4.2.16.1.3 Sidelink RLC Parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|---------------------------------------------------------------------------------------------------------------------------------------|-----|----|--------------|--------------| +| am-WithLongSN-Sidelink-r16
Indicates whether the UE supports AM DRB with 18 bit length of RLC sequence number for sidelink. | UE | No | No | No | +| um-WithLongSN-Sidelink-r16
Indicates whether the UE supports UM DRB with 12 bit length of RLC sequence number for sidelink. | UE | No | No | No | + +##### 4.2.16.1.4 Sidelink MAC Parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----|--------------|--------------| +| drx-OnSidelink-r17
Indicates whether UE supports sidelink DRX for unicast, groupcast and broadcast. | UE | No | No | No | +| lcp-RestrictionSidelink-r16
Indicates whether UE supports the selection of logical channels for each SL grant based on RRC configured restriction. | UE | No | No | No | +| logicalChannelSR-DelayTimerSidelink-r16
Indicates whether the UE supports the logicalChannelSR-DelayTimer as specified in TS 38.321 [8] for sidelink logical channel(s). | UE | No | Yes | No | +| multipleSR-ConfigurationsSidelink-r16
Indicates whether the UE supports 8 SR configurations per PUCCH cell group as specified in TS 38.321 [8] for sidelink. | UE | No | Yes | No | +| multipleConfiguredGrantsSidelink-r16
Indicates whether UE supports 8 sidelink configured grant configurations (including both Type 1 and Type 2) in a resource pool. If absent, for each resource pool, the UE only supports one sidelink configured grant configuration. | UE | No | No | No | +| sl-LBT-FailureDetectionRecovery-r18
Indicates whether the UE supports sidelink consistent LBT detection and recovery, as specified in TS 38.321 [8], for shared spectrum channel access. | UE | No | No | No | + +##### 4.2.16.1.5 + +###### Other PHY parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----|--------------|--------------| +| p0-OLPC-Sidelink-r17
Indicates whether the UE supports the use of P0 parameters (i.e. dl-P0-PSSCH-PSCCH-r17 , sl-P0-PSSCH-PSCCH-r17 , dl-P0-PSBCH-r17 , dl-P0-PSFCH-r17 ) for sidelink open loop power control. | UE | No | No | No | +| supportedBandCombinationListSidelinkEUTRA-NR-r16
Defines the supported NR sidelink communication and/or V2X sidelink communication band combinations by the UE. A fallback band combination resulting from the reported sidelink band combination shall be supported by the UE. The UE does not include this field if the UE capability is requested by E-UTRAN (see TS 36.331 [17]) and the network request includes the field eutra-nr-only . | UE | No | No | No | +| supportedBandCombinationListSidelinkNR-r16
Defines the supported joint NR sidelink communication band combinations by the UE. A fallback band combination resulting from the reported sidelink band combination shall be supported by the UE. | UE | No | No | No | +| supportedBandCombinationListSL-NonRelayDiscovery-r17
Defines the supported band combinations of NR sidelink non-relay discovery message transmission and reception by the UE. | UE | No | No | No | +| supportedBandCombinationListSL-RelayDiscovery-r17
Defines the supported band combinations of NR sidelink relay discovery message transmission and reception by the UE. This parameter is used by the remote UE and relay UE, and for the case of L2 and L3 relay. | UE | No | No | No | +| supportedBandCombinationListSL-U2U-RelayDiscovery-r18
Defines the supported band combinations of NR U2U sidelink relay discovery message transmission and reception by the UE. This parameter is used by the remote UE and relay UE, and for the case of L2 and L3 relay. | UE | No | No | No | +| supportedBandListSidelink-r16
Indicates frequency bands supported for NR sidelink communications and parameters supported for each frequency band, as specified in 4.2.16.1.6. If a band is included in supportedBandCombinationListSL-NonRelayDiscovery-r17 , supportedBandCombinationListSL-RelayDiscovery-r17 or supportedBandCombinationListSL-U2U-RelayDiscovery-r18 , the band supports non-relay/relay NR sidelink discovery. | UE | No | No | No | + +##### 4.2.16.1.6 + +##### *BandSidelink* Parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +|

sl-Reception-r16

Indicates whether receiving NR sidelink communication is supported. If supported, this parameter indicates the support of the capabilities and includes the parameters as follows:

  • - UE can receive NR PSCCH/PSSCH.
  • - harq-RxProcessSidelink, which indicates the number of sidelink HARQ processes across all links that the UE supports for NR PSSCH reception. Value n16 corresponds to 16, n24 corresponds to 24, and so on.
  • - pscch-RxSidelink, which indicates the number of PSCCH that the supports for reception in a slot. Value value1 corresponds to floor (N_{RB} / 10 RBs), value2 corresponds to 2 * \text{floor} (N_{RB} / 10 \text{ RBs});
  • - UE can attempt to decode N_{RB} non-overlapping RBs per slot.
  • - UE supports reception of PSSCH according to the 64QAM MCS table.
  • - UE supports PT-RS reception in FR2.
  • - scs-CP-PatternRxSidelink, which indicates the subcarrier spacing with normal CP and the corresponding channel bandwidth that the UE supports for NR sidelink communication reception. Value scs-15kHz corresponds to 15kHz, scs-30kHz corresponds to 30kHz, and so on. It is mandatory for UE to support reception using 30 kHz subcarrier spacing with normal CP in FR1, and 120 kHz subcarrier spacing with normal CP FR2. For FR1, the bits in scs-XXkHz starting from the leading / leftmost bit indicate 5, 10, 15, 20, 25, 30, 40, 50, 60, 70, 80, 90 and 100MHz. For FR2, the bits in scs-XXkHz starting from the leading / leftmost bit indicate 50, 100 and 200MHz. This capability is not required to be signalled in a band indicated with only the PC5 interface in TS 38.101-1 [2], Table 5.2E.1-1. Otherwise, it is mandatory. For a band indicated with only the PC5 interface in 38.101-1 [2], Table 5.2E.1-1, UE supports reception using 30 kHz subcarrier spacing with normal CP in FR1, 120 kHz subcarrier spacing with normal CP in FR2.
  • - extendedCP-RxSidelink, which indicates whether the UE supports 60 kHz subcarrier spacing with extended CP length for NR sidelink communication reception. This capability is not required to be signalled in a band indicated with only the PC5 interface in TS 38.101-1 [2], Table 5.2E.1-1. Otherwise, it is mandatory.
  • - UE supports 14-symbol SL slot with all DMRS patterns corresponding to number of PSSCH symbols = {12, 9} for slots with and without PSFCH. If UE signals support of extended CP, support 12-symbol SL slot with all DMRS patterns corresponding to number of PSSCH symbols = {10,7} for slots with and without PSFCH.

NOTE 1: N_{RB} is the number of RBs defined per channel bandwidth by RAN4 in TS 38.101-1 [2], Table 5.3.2-1 for FR1 and TS 38.101-2 [3], Table 5.3.2.-1 for FR2.

NOTE 2: Configuration by NR Uu is not required to be supported in a band indicated with only the PC5 interface in TS 38.101-1 [2] Table 5.2E.1-1.

Support of this feature is mandatory if UE supports NR sidelink.
If a band is included in supportedBandCombinationListSL-NonRelayDiscovery-r17, supportedBandCombinationListSL-RelayDiscovery-r17 or supportedBandCombinationListSL-U2U-RelayDiscovery-r18, it indicates whether receiving non-relay/relay NR sidelink discovery is supported.

| Band | CY | N/A | N/A | + +|

sl-TransmissionMode1-r16
Indicates whether transmitting NR sidelink mode 1 scheduled by Uu is supported. If supported, this parameter indicates the support of the capabilities and includes the parameters as follows:

  • - UE can transmit PSCCH/PSSCH using configured grant type 1. For NR sidelink mode 1 scheduled by NR Uu, UE can additionally transmit PSCCH/PSSCH using dynamic scheduling or configured grant type 2. Up to 8 configured grants can be configured for a UE.
  • - harq-TxProcessModeOneSidelink, which indicates the number of sidelink HARQ processes across all links that the UE supports for NR PSSCH transmission using mode 1, including those for configured grants. Value n8 corresponds to 8, n16 corresponds to 16, and so on.
  • - UE can transmit PSSCH according to the normal 64QAM MCS OFDM table.
  • - UE supports PT-RS transmission in FR2.
  • - For NR sidelink mode 1 scheduled by NR Uu, UE can monitor DCI format 3_0 for NR sidelink dynamic scheduling and configured grant type 2 on the same carrier as sidelink.
  • - scs-CP-PatternTxSidelinkModeOne, which indicates the subcarrier spacing with normal CP and the corresponding bandwidth that the UE supports for NR sidelink communication transmission using NR sidelink mode 1. Value scs-15kHz corresponds to 15kHz, scs-30kHz corresponds to 30kHz, and so on. For FR1, the bits in scs-XXkHz starting from the leading / leftmost bit indicate 5, 10, 15, 20, 25, 30, 40, 50, 60, 70, 80, 90 and 100MHz. For FR2, the bits in scs-XXkHz starting from the leading / leftmost bit indicate 50, 100 and 200MHz. For a band indicated with only the PC5 interface in TS 38.101-1 [2], Table 5.2E.1-1, UE supports transmission using at least 30 kHz subcarrier spacing with normal CP in FR1, at least 120 kHz subcarrier spacing with normal CP in FR2. Otherwise, the reported subcarrier spacing with normal CP and the corresponding bandwidth that the UE supports shall be the same as reported for UL via channelBWs-UL.
  • - extendedCP-TxSidelink, which indicates whether the UE supports 60 kHz subcarrier spacing with extended CP length for NR sidelink communication transmission using mode 1. For a band indicated with only the PC5 interface in TS 38.101-1 [2], Table 5.2E.1-1, the reported subcarrier spacing with normal CP and the corresponding bandwidth that the UE supports shall be the same as reported for UL via channelBWs-UL.
  • - UE supports 14-symbol SL slot with all DMRS patterns corresponding to the number of PSSCH symbols = {12, 9} for slots with and without PSFCH. If UE signals support of extended CP, support 12-symbol SL slot with all DMRS patterns corresponding to the number of PSSCH symbols = {10,7} for slots with and without PSFCH.
  • - UE supports downlink pathloss based open loop power control for NR sidelink mode 1 scheduled by NR Uu if the band is not indicated with only the PC5 interface in TS 38.101-1 [2], Table 5.2E.1-1. Otherwise, it is not supported.
  • - harq-ReportOnPUCCH, which indicates whether UE supports reporting sidelink HARQ-ACK to gNB via PUCCH and PUSCH when it is operating in NR sidelink mode 1, for NR sidelink mode 1 scheduled by NR Uu, if the band is indicated with only the PC5 interface in TS 38.101-1 [2], Table 5.2E.1-1. Otherwise, it is mandatory.

NOTE: Random selection in the exceptional pool is supported.

Support of this feature is mandatory if UE supports NR sidelink in licensed spectrum where gNB is operating on or managing that spectrum.
If a band is included in supportedBandCombinationListSL-NonRelayDiscovery-r17, supportedBandCombinationListSL-RelayDiscovery-r17 or supportedBandCombinationListSL-U2U-RelayDiscovery-r18, it indicates whether receiving non-relay/relay NR sidelink discovery is supported.

| Band | CY | N/A | N/A | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|-----|-----| +| | | | | | + +| sl-TransmissionMode2-r16 | Band | CY | N/A | N/A | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|-----|-----| +|

Indicates whether transmitting NR sidelink mode 2 is supported. If supported, this parameter indicates the support of the capabilities and includes the parameters as follows:

  • - UE can transmit PSCCH/PSSCH using NR sidelink mode 2 configured by NR Uu or preconfiguration.
  • - harq-TxProcessModeTwoSidelink, which indicates the number of sidelink HARQ processes across all links that the UE supports for NR PSSCH transmission using mode 2. Value n8 corresponds to 8, n16 corresponds to 16.
  • - UE can transmit PSSCH according to the normal 64QAM MCS table.
  • - UE supports PT-RS transmission in FR2.
  • - UE can perform mode 2 sensing and resource allocation operations
  • - scs-CP-PatternTxSidelinkModeTwo, which indicates UE can transmit using the subcarrier spacing and CP length it reports in sl-Reception-r16. This capability is not required to be signalled in a band indicated with only the PC5 interface in TS 38.101-1 [2], Table 5.2E.1-1. Otherwise, it is mandatory. For a band indicated with only the PC5 interface in TS 38.101-1 [2], Table 5.2E.1-1, UE supports transmission using 30 kHz subcarrier spacing with normal CP in FR1, 120 kHz subcarrier spacing with normal CP in FR2.
  • - UE supports 14-symbol SL slot with all DMRS patterns corresponding to the number of PSSCH symbols = {12, 9} for slots with and without PSFCH. If UE signals support of extended CP, support 12-symbol SL slot with all DMRS patterns corresponding to the number of PSSCH symbols = {10,7} for slots with and without PSFCH.
  • - dl-openLoopPC-Sidelink, which indicates whether UE supports DL pathloss based open loop power control when mode 2 is configured by NR Uu, if the band is indicated with only the PC5 interface in TS 38.101-1 [2], Table 5.2E.1-1. Otherwise, it is mandatory.

This field is only applicable if the UE supports sl-Reception-r16.

NOTE 1: Random selection in the exceptional pool is supported.

NOTE 2: Configuration by NR Uu is not required to be supported in a band indicated with only the PC5 interface in TS 38.101-1 [2] Table 5.2E.1-1.

Support of this feature is mandatory if UE supports NR sidelink.

| | | | | + +| | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|-----|----------| +|

sync-Sidelink-r16
Indicates whether UE supports synchronization sources for NR sidelink. If supported, this parameter indicates the support of the capabilities and includes the parameters as follows:

  • - UE can receive S-SSB in NR sidelink if it supports sl-Reception-r16.
  • - UE can transmit S-SSB in NR sidelink if it supports sl-TransmissionMode1-r16 or sl-TransmissionMode2-r16.
  • - UE supports GNSS and SyncRef UE as the synchronization reference according to the synchronization procedure with sl-SyncPriority set to GNSS and sl-NbAsSync set to false.
  • - gNB-Sync, which indicates whether UE can transmit or receive NR sidelink based on the synchronization to an gNB for NR Uu, if the band is indicated with only the PC5 interface in TS 38.101-1 [2], Table 5.2E.1-1. Otherwise, it is mandatory.
  • - gNB-GNSS-UE-SyncWithPriorityOnGNB-ENB, which indicates whether UE additionally supports gNB, GNSS and SyncRef UE as the synchronization reference according to the synchronization procedure with sl-SyncPriority set to gnbEnb for NR Uu, if the band is indicated with only the PC5 interface in TS 38.101-1 [2], Table 5.2E.1-1. Otherwise, it is mandatory.
  • - gNB-GNSS-UE-SyncWithPriorityOnGNSS, which indicates whether UE additionally supports gNB, GNSS and SyncRef UE as the synchronization reference according to the synchronization procedure with sl-SyncPriority set to GNSS and sl-NbAsSync set to true for NR Uu, if the band is indicated with only the PC5 interface in TS 38.101-1 [2], Table 5.2E.1-1. Otherwise, it is mandatory.

This field is only applicable if the UE supports at least one of sl-Reception-r16, sl-TransmissionMode1-r16 and sl-TransmissionMode2-r16.

NOTE: Configuration by NR Uu is not required to be supported in a band indicated with only the PC5 interface in TS 38.101-1 [2] Table 5.2E.1-1.

Support of this feature is mandatory if UE supports NR sidelink.

| Band | CY | N/A | N/A | +|

congestionControlSidelink-r16
Indicates whether UE supports sidelink congestion control for NR sidelink. If supported, this parameter indicates the support of the capabilities and includes the parameters as follows:

  • - cbr-ReportSidelink, which indicates whether UE can report CBR measurement to gNB when operating in Mode 1 and mode 2, if the band is indicated with only the PC5 interface in TS 38.101-1 [2], Table 5.2E.1-1. Otherwise, it is mandatory.
  • - UE can adjust its radio parameters based on CBR measurement and CRIlimit.
  • - cbr-CR-TimeLimitSidelink, which indicates the time within which UE can process CBR and CR. Value time1 corresponds to congestion process time of 2, 2, 4, 8 slots for 15, 30, 60, 120 kHz subcarrier spacing, and value time2 corresponds to congestion process time of 2, 4, 8, 16 slots for 15, 30, 60, 120 kHz subcarrier spacing.

This field is only applicable if the UE supports sl-Reception-r16 and at least one of sl-TransmissionMode1-r16 and sl-TransmissionMode2-r16.

Support of this feature is mandatory if UE supports NR sidelink.

| Band | CY | N/A | N/A | +|

sl-Tx-256QAM-r16
Indicates UE can transmit PSSCH according to the 256QAM MCS table.
This field is only applicable if the UE supports at least one of sl-TransmissionMode1-r16 and sl-TransmissionMode2-r16.

| Band | No | N/A | FR1 only | +|

sl-Rx-256QAM-r16
Indicates UE can receive PSSCH according to the 256QAM MCS table.
This field is only applicable if the UE supports sl-Reception-r16.

| Band | No | N/A | FR1 only | + +| | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|-----|-----| +|

psfch-FormatZeroSidelink-r16
Indicates whether UE supports PSFCH format 0. If supported, this parameter indicates the support of the capabilities and includes the parameters as follows:

  • - UE can transmit and receive NR PSFCH format 0.
  • - psfch-RxNumber which indicates the number of PSFCH(s) resources that the UE can receive in a slot. Value n5 corresponds to 5, n15 corresponds to 15, and so on.
  • - psfch-TxNumber which indicates the number of PSFCH(s) resources that the UE can transmit in a slot. Value n4 corresponds to 4, n8 corresponds to 8, and so on.

This field is only applicable if the UE supports at least one of sl-Reception-r16 and sl-TransmissionMode2-r16.

NOTE: Configuration by NR Uu is not required to be supported in a band indicated with only the PC5 interface in TS 38.101-1 [2] Table 5.2E.1-1.

Support of this feature is mandatory if UE supports NR sidelink.

| Band | CY | N/A | N/A | +|

lowSE-64QAM-MCS-TableSidelink-r16
Indicates UE can transmit and receive PSSCH according to the low-spectral efficiency 64QAM MCS table.
This field is only applicable if the UE supports at least one of sl-Reception-r16, sl-TransmissionMode1-r16 and sl-TransmissionMode2-r16.

| Band | No | N/A | N/A | +|

csi-ReportSidelink-r16
Indicates UE supports Sidelink CSI report. If supported, this parameter indicates the support of the capabilities and includes the parameters as follows:

  • - csi-RS-PortsSidelink, which indicates the number of antenna port(s) up to which UE can transmit and receive sidelink CSI-RS with. Value p1 corresponds to 1, and value p2 corresponds to 2.
  • - UE supports RI and CQI feedback on sidelink.

This field is only applicable if the UE supports at least one of sl-Reception-r16, sl-TransmissionMode1-r16 and sl-TransmissionMode2-r16.

Support of this feature is mandatory if UE supports NR sidelink.

| Band | CY | N/A | N/A | +|

enb-Sync-Sidelink-r16
Indicates whether UE supports eNB type synchronization source for NR sidelink. If supported, this parameter indicates the support of the capabilities and includes the parameters as follows:

  • - UE can transmit or receive NR sidelink based on the synchronization to an eNB.
  • - If UE supports sync-Sidelink-r16, UE additionally supports eNB, GNSS and SyncRef UE as the synchronization reference according to the synchronization procedure with sl-SyncPriority set to gnbEnb.
  • - If UE supports sync-Sidelink-r16, UE additionally supports eNB, GNSS and SyncRef UE as the synchronization reference according to the synchronization procedure with sl-SyncPriority set to GNSS and sl-NbAsSync set to true.

This field is only applicable if the UE supports at least one of sl-Reception-r16, sl-TransmissionMode1-r16 and sl-TransmissionMode2-r16.

| Band | No | N/A | N/A | +|

rankTwoReception-r16
Indicates whether UE supports rank 2 PSSCH reception.
This field is only applicable if the UE supports sl-Reception-r16.

| Band | No | N/A | N/A | +|

fewerSymbolSlotSidelink-r16
Indicates whether UE supports transmission/reception of SL slot configured with 7, 8, 9, 10, 11, 12, 13 consecutive symbols and all the corresponding DMRS patterns in a slot.
This field is only applicable if the UE supports at least one of sl-Reception-r16, sl-TransmissionMode1-r16 and sl-TransmissionMode2-r16.

| Band | No | N/A | N/A | + +| | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|-----|-----| +|

sl-openLoopPC-RSRP-ReportSidelink-r16
Indicates whether UE supports sidelink pathloss based open loop power control and RSRP report in case of unicast.
This field is only applicable if the UE supports sl-Reception-r16 and at least one of sl-TransmissionMode1-r16 and sl-TransmissionMode2-r16.

Support of this feature is mandatory if UE supports NR sidelink.

| Band | CY | N/A | N/A | +|

sl-TransmissionMode2-RandomResourceSelection-r17
Indicates transmitting NR sidelink mode 2 with random resource selection is supported. If supported, this parameter indicates the support of the capabilities and includes the parameters as follows:

  • - UE can transmit PSCCH/PSSCH using NR sidelink mode 2 with random resource selection configured by NR Uu or preconfiguration.
  • - harq-TxProcessModeTwoSidelink-r17, which indicates the number of sidelink HARQ processes across all links that the UE supports for NR PSSCH transmission using mode 2. Value n8 corresponds to 8, n16 corresponds to 16.
  • - UE can transmit PSSCH according to the normal 64QAM MCS table.
  • - UE supports PT-RS transmission in FR2.
  • - scs-CP-PatternTxSidelinkModeTwo-r17, which indicates the subcarrier spacing with normal CP and the corresponding bandwidth that the UE supports for NR sidelink communication transmission using NR sidelink mode 2 with random resource selection. Value scs-15kHz corresponds to 15kHz, scs-30kHz corresponds to 30kHz, and so on. For FR1, the bits in scs-XXkHz starting from the leading / leftmost bit indicate 5, 10, 15, 20, 25, 30, 40, 50, 60, 70, 80, 90 and 100MHz. For FR2, the bits in scs-XXkHz starting from the leading / leftmost bit indicate 50, 100 and 200MHz. UE can transmit using the subcarrier spacing and CP length it reports in sl-Reception-r16. This capability is not required to be signalled in a band indicated with only the PC5 interface in TS 38.101-1 [2], Table 5.2E.1-1. Otherwise, it is mandatory. For a band indicated with only the PC5 interface in TS 38.101-1 [2], Table 5.2E.1-1, UE supports transmission using 30 kHz subcarrier spacing with normal CP in FR1, 120 kHz subcarrier spacing with normal CP in FR2.
  • - extendedCP-Mode2Random-r17, which indicates whether the UE supports 60 kHz subcarrier spacing with extended CP length for NR sidelink communication transmission using mode 2 with random resource selection.
  • - UE supports 14-symbol SL slot with all DMRS patterns corresponding to the number of PSSCH symbols = {12, 9} for slots with and without PSFCH. If UE signals support of extended CP, support 12-symbol SL slot with all DMRS patterns corresponding to the number of PSSCH symbols = {10, 7} for slots with and without PSFCH.
  • - dl-openLoopPC-Sidelink-r17, which indicates whether UE supports DL pathloss based open loop power control when mode 2 is configured by NR Uu, if the band is indicated with only the PC5 interface in TS 38.101-1 [2], Table 5.2E.1-1. Otherwise, it is mandatory.

UE supporting this feature shall support receiving NR sidelink of S-SSB or indicate support of sync-Sidelink-r16 or sync-Sidelink-v1710.
If a band is included in supportedBandCombinationListSL-NonRelayDiscovery-r17, supportedBandCombinationListSL-RelayDiscovery-r17 or supportedBandCombinationListSL-U2U-RelayDiscovery-r18, it indicates whether transmitting NR sidelink mode 2 with random resource selection is supported for non-relay/relay NR sidelink discovery.

NOTE 1: Configuration by NR Uu is not required to be supported in a band indicated with only the PC5 interface in TS 38.101-1 [2] Table 5.2E.1-1.

NOTE 2: If UE reports more than one features of sl-TransmissionMode2-r16, sl-TransmissionMode2-PartialSensing-r17 and sl-TransmissionMode2-RandomResourceSelection-r17, the reported value of harq-TxProcessModeTwoSidelink in each feature is the total number of SL processes and the same among those features.

NOTE 3: Random selection in the exceptional pool is supported.

| Band | No | N/A | N/A | + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|-----|-----| +|

sync-Sidelink-v1710
Indicates whether UE supports synchronization sources for NR sidelink. If supported, this parameter indicates the support of the capabilities and includes the parameters as follows:

  • - sync-GNSS-r17, which indicates UE supports GNSS as the synchronization reference according to the synchronization procedure with sl-SyncPriority set to GNSS and sl-NbAsSync set to false. This capability is only required to be supported in a band indicated with only the PC5 interface in TS 38.101-1 [2], Table 5.2E.1-1
  • - gNB-Sync-r17, which indicates whether UE can transmit NR sidelink based on the synchronization to an gNB for NR Uu, if the band is indicated with only the PC5 interface in TS 38.101-1 [2], Table 5.2E.1-1, it is not required to be supported. Otherwise, it is mandatory.
  • - gNB-GNSS-UE-SyncWithPriorityOnGNB-ENB-r17, which indicates whether UE additionally supports gNB, GNSS as the synchronization reference according to the synchronization procedure with sl-SyncPriority set to gnbEnb for NR Uu, if the band is indicated with only the PC5 interface in TS 38.101-1 [2], Table 5.2E.1-1, it is not required to be supported. Otherwise, it is mandatory.
  • - gNB-GNSS-UE-SyncWithPriorityOnGNSS-r17, which indicates whether UE additionally supports gNB, GNSS as the synchronization reference according to the synchronization procedure with sl-SyncPriority set to GNSS and sl-NbAsSync set to true for NR Uu, if the band is indicated with only the PC5 interface in TS 38.101-1 [2], Table 5.2E.1-1, it is not required to be supported. Otherwise, it is mandatory.
  • - UE can transmit S-SSB in NR sidelink if it supports sl-TransmissionMode1-r16 or sl-TransmissionMode2-r16 or sl-TransmissionMode2-PartialSensing-r17 or sl-TransmissionMode2-RandomResourceSelection-r17.
  • - UE supports synchronization to a reference UE if it supports sl-Reception-r16.

NOTE: Configuration by NR Uu is not required to be supported in a band indicated with only the PC5 interface in TS 38.101-1 [2] Table 5.2E.1-1.

| Band | No | N/A | N/A | +|

enb-Sync-Sidelink-v1710
Indicates whether UE supports eNB type synchronization source for NR sidelink. If supported, this parameter indicates the support of the capabilities and includes the parameters as follows:

  • - UE can transmit NR sidelink based on the synchronization to an eNB.
  • - If UE supports sync-GNSS-r17, UE additionally supports eNB, GNSS as the synchronization reference according to the synchronization procedure with sl-SyncPriority set to gnbEnb.
  • - If UE supports sync-GNSS-r17, UE additionally supports eNB, GNSS as the synchronization reference according to the synchronization procedure with sl-SyncPriority set to GNSS and sl-NbAsSync set to true.

This field is only applicable if the UE supports sync-Sidelink-v1710.

NOTE: Configuration by NR Uu is not required to be supported in a band indicated with only the PC5 interface in TS 38.101-1 [2] Table 5.2E.1-1.

| Band | No | N/A | N/A | +|

rx-IUC-Scheme1-PreferredMode2Sidelink-r17
Indicates whether UE supports reception of preferred resource set for NR sidelink for mode 2. If supported, this parameter indicates the support of the capabilities as follows:

  • - UE can receive inter-UE coordination information of preferred resource set and use the received information in its own resource (re-)selection in NR sidelink mode 2.
  • - UE can transmit an explicit request for inter-UE coordination information of preferred resource set only.

UE supporting this feature shall support receiving NR sidelink of S-SSB or indicate support of sync-Sidelink-r16 or sync-Sidelink-v1710.

NOTE: Configuration by NR Uu is not required to be supported in a band indicated with only the PC5 interface in TS 38.101-1 [2] Table 5.2E.1-1.

| Band | No | N/A | N/A | + +| | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|-----|----------| +|

rx-IUC-Scheme1-NonPreferredMode2Sidelink-r17

Indicates whether UE supports reception of non-preferred resource set for NR sidelink for mode 2. If supported, this parameter indicates the support of the capabilities as follows:

  • - UE can receive inter-UE coordination information of non-preferred resource set and use the received information in its own resource (re-)selection in NR sidelink mode 2.
  • - UE can transmit an explicit request for inter-UE coordination information of non-preferred resource set only.

UE supporting this feature shall support receiving NR sidelink of S-SSB or indicate support of sync-Sidelink-r16 or sync-Sidelink-v1710.

NOTE: Configuration by NR Uu is not required to be supported in a band indicated with only the PC5 interface in TS 38.101-1 [2] Table 5.2E.1-1.

| Band | No | N/A | N/A | +|

rx-IUC-Scheme2-Mode2Sidelink-r17

Indicates whether UE supports reception of inter-UE coordination scheme 2 for NR sidelink for mode 2. If supported, this parameter indicates the support of the capabilities and includes the parameters as follows:

  • - UE can receive inter-UE coordination information of presence of expected/potential resource conflict and use the received information in its own resource re-selection in NR sidelink mode 2.
  • - UE indicates the number of PSFCH(s) resources that the UE can receive in a slot. Value n5 corresponds to 5, n15 corresponds to 15, and so on.

UE supporting this feature shall support receiving NR sidelink of S-SSB or indicate support of sync-Sidelink-r16 or sync-Sidelink-v1710.

NOTE 1: If UE reports more than one capability of psfch-FormatZeroSidelink-r16, rx-sidelinkPSFCH-r17 and rx-IUC-Scheme1-PreferredMode2Sidelink-r17, the reported value of the number of PSFCH(s) resources in each capability is the total number and the same among those capabilities.

NOTE 2: Configuration by NR Uu is not required to be supported in a band indicated with only the PC5 interface in TS 38.101-1 [2] Table 5.2E.1-1.

| Band | No | N/A | N/A | +|

rx-IUC-Scheme1-SCI-r17

Indicates whether UE can receive Scheme 1 inter-UE coordination transmission over 2nd SCI that is used in addition to the MAC-CE carrying the same inter-UE coordination information in the same transmission.

UE indicating support of this feature shall indicate support of at least one of rx-IUC-Scheme1-Preferred-Mode2Sidelink-r17 and rx-IUC-Scheme1-NonPreferred-Mode2Sidelink-r17.

NOTE: Configuration by NR Uu is not required to be supported in a band indicated with only the PC5 interface in TS 38.101-1 [2] Table 5.2E.1-1.

| Band | No | N/A | N/A | +|

rx-IUC-Scheme1-SCI-ExplicitReq-r17

Indicates whether UE can receive an explicit request for inter-UE coordination information of both preferred resource set and non-preferred resource set over 2nd SCI that is used in addition to the MAC-CE carrying the explicit request in the same transmission. UE indicating support of this feature shall indicate support of tx-IUC-Scheme1-Mode2Sidelink-r17.

NOTE: Configuration by NR Uu is not required to be supported in a band indicated with only the PC5 interface in TS 38.101-1 [2] Table 5.2E.1-1.

| Band | No | N/A | N/A | +|

scheme2-ConflictDeterminationRSRP-r17

Indicates whether UE can determine a conflict for overlapping resource reservation between UE-B and another UE based on RSRP difference of the two reservations.

UE indicating support of this feature shall indicate support of tx-IUC-Scheme2-Mode2Sidelink-r17.

NOTE: Configuration by NR Uu is not required to be supported in a band indicated with only the PC5 interface in TS 38.101-1 [2] Table 5.2E.1-1.

| Band | No | N/A | N/A | +|

sl-ReceptionIntraCarrierGuardBand-r18

Indicates whether the UE supports reception in the non-zero intra-cell guardband between contiguous RB sets in SL wideband carrier operation wider than 20MHz when LBT is successful only in a subset of RB sets, where intra-cell guardband is specified in TS 38.101-1 [2].

| Band | No | N/A | FR1 only | + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|-----|-----| +| ue-PowerClassSidelink-r16
This parameter indicates the supported power class for this band used for sidelink.
If the field is absent, the UE supports the default power class in TS 38.101-1 [2],
Table 6.2E.1.2-2. | Band | No | N/A | N/A | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|-----|-----| + +##### 4.2.16.1.7 + +###### *BandCombinationListSidelinkEUTRA-NR* Parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| tx-Sidelink-r16
Indicates whether the UE supports sidelink transmission on the band.
For NR sidelink, this field is only applicable if the UE supports at least one of sl-TransmissionMode1-r16 and sl-TransmissionMode2-r16 on the band. | Band | No | N/A | N/A | +| rx-Sidelink-r16
Indicates whether the UE supports sidelink reception on the band.
For NR sidelink, this field is only applicable if the UE supports sl-Reception-r16 on the band. | Band | No | N/A | N/A | +| sl-CrossCarrierScheduling-r16
Indicates whether the UE supports monitoring DCI format 3_0 on a different carrier from sidelink for NR sidelink dynamic scheduling and configured grant type 2. If the UE indicates support for sl-TransmissionMode1-r16 in a band indicated with only the PC5 interface in Table 5.2E.1-1 of TS 38.101-1 [2], the UE shall indicate that sl-CrossCarrierScheduling-r16 is supported for a band combination with that band.
For NR sidelink, this field is only applicable if the UE supports sl-TransmissionMode1-r16 on the band. | Band | No | N/A | N/A | +| sl-TransmissionMode2-PartialSensing-r17
Indicates transmitting NR sidelink mode 2 with partial sensing is supported. If supported, this parameter indicates the support of the capabilities and includes the parameters as follows:
  • - UE can transmit PSCCH/PSSCH using NR sidelink mode 2 with partial sensing configured by NR Uu or preconfiguration.
  • - harq-TxProcessModeTwoSidelink-r17, which indicates the number of sidelink HARQ processes across all links that the UE supports for NR PSSCH transmission using mode 2. Value n8 corresponds to 8, n16 corresponds to 16.
  • - UE can transmit PSSCH according to the normal 64QAM MCS table.
  • - UE supports PT-RS transmission in FR2.
  • - UE can perform periodic-based partial sensing and resource allocation operation.
  • - UE can perform contiguous partial sensing and resource allocation operation.
  • - scs-CP-PatternTxSidelinkModeTwo-r17, the subcarrier spacing with normal CP and the corresponding bandwidth that the UE supports for NR sidelink communication transmission using NR sidelink mode 2 with partial sensing. Value scs-15kHz corresponds to 15kHz, scs-30kHz corresponds to 30kHz, and so on. For FR1, the bits in scs-XXkHz starting from the leading / leftmost bit indicate 5, 10, 15, 20, 25, 30, 40, 50, 60, 70, 80, 90 and 100MHz. For FR2, the bits in scs-XXkHz starting from the leading / leftmost bit indicate 50, 100 and 200MHz. This capability is not required to be signalled in a band indicated with only the PC5 interface in TS 38.101-1 [2], Table 5.2E.1-1. Otherwise, it is mandatory. For a band indicated with only the PC5 interface in TS 38.101-1 [2], Table 5.2E.1-1, UE supports transmission using 30 kHz subcarrier spacing with normal CP in FR1, 120 kHz subcarrier spacing with normal CP in FR2.
  • - extendedCP-Mode2PartialSensing-r17, which indicates whether the UE supports 60 kHz subcarrier spacing with extended CP length for NR sidelink communication transmission using mode 2 with partial sensing.
  • - UE supports 14-symbol SL slot with all DMRS patterns corresponding to the number of PSSCH symbols = {12, 9} for slots with and without PSFCH. If UE signals support of extended CP, support 12-symbol SL slot with all DMRS patterns corresponding to the number of PSSCH symbols = {10,7} for slots with and without PSFCH.
  • - dl-openLoopPC-Sidelink-r17, which indicates whether UE supports DL pathloss based open loop power control when mode 2 is configured by NR Uu, if the band is indicated with only the PC5 interface in TS 38.101-1 [2], Table 5.2E.1-1. Otherwise, it is mandatory.

UE supporting this feature shall support receiving NR sidelink of S-SSB or indicate support of sync-Sidelink-r16 or sync-Sidelink-v1710.
If a band combination is included in supportedBandCombinationListSL-NonRelayDiscovery-r17, supportedBandCombinationListSL-RelayDiscovery-r17 or supportedBandCombinationListSL-U2U-RelayDiscovery-r18, it indicates whether transmitting NR sidelink mode 2 with partial sensing is supported for non-relay/relay NR sidelink discovery.

| FS | No | N/A | N/A | + +#### 4.2.16.2 Sidelink Parameters in E-UTRA + +##### 4.2.16.2.0 General + +| Descriptions for parameters | Per | M | FDD-TDD DIFF | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----|--------------| +| supportedBandListSidelinkEUTRA-r16
Indicates E-UTRA frequency bands supported for V2X sidelink communications and parameters supported for each frequency band, as specified in 4.2.16.2.1. | UE | No | No | + +##### 4.2.16.2.1 BandSideLinkEUTRA parameters + +| Descriptions for parameters | Per | M | FDD-TDD DIFF | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------| +| gnb-ScheduledMode3SidelinkEUTRA-r16
Indicates whether transmitting V2X sidelink communication mode 3 scheduled by NR Uu is supported. If supported, this parameter indicates the support of the capabilities and includes the parameters as follows:
  • - the UE can be scheduled by gNB using DCI format 3_1 for V2X sidelink mode 3 transmission.
  • - gnb-ScheduledMode3DelaySidelinkEUTRA, which indicates the minimum value UE supports for the additional time indicated in the NR DCI scheduling V2X sidelink mode 3. Value ms0 corresponds to 0 ms, ms0dot25 corresponds to 0.25 ms, and so on.
This field is only applicable if the UE supports V2X sidelink communication. | Band | No | N/A | +| gnb-ScheduledMode4SidelinkEUTRA-r16
Indicates whether the UE can be scheduled by gNB for V2X sidelink mode 4 transmission. This field is only applicable if the UE supports V2X sidelink communication. | Band | No | N/A | + +### 4.2.17 SON parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----|--------------|--------------| +| onDemandSI-Report-r17
Indicates whether the UE supports delivery of on-Demand SI information upon request from the network as specified in TS 38.331 [9]. | UE | No | No | No | +| pscell-MHI-Report-r17
Indicates whether the UE supports the storage of PSCell mobility history information and the reporting in UEInformationResponse message as specified in TS 38.331 [9]. | UE | No | No | No | +| rach-Report-r16
Indicates whether the UE supports delivery of RA report upon request from the network. | UE | No | No | No | +| rlfReportCHO-r17
Indicates whether the UE supports RLF-Report for conditional handover. | UE | No | No | No | +| rlfReportDAPS-r17
Indicates whether the UE supports RLF-Report for DAPS handover. | UE | No | No | No | +| spr-Report-r18
Indicates whether the UE supports the storage and delivery of Successful PSCell Change/Addition Report upon request from the network. | UE | No | No | No | +| success-HO-Report-r17
Indicates whether the UE supports the storage and delivery of Successful Handover Report upon request from the network as specified in TS 38.331 [9]. | UE | No | No | No | +| successIRAT-HO-Report-r18
Indicates whether the UE supports the storage and delivery of Successful Handover Report for Handover from NR to E-UTRA, upon request from the network. | UE | No | No | No | +| twoStepRACH-Report-r17
Indicates whether the UE supports the storage and delivery of 2-step RACH related information upon request from the network as specified in TS 38.331 [9]. | UE | No | No | No | + +### 4.2.18 UE-based performance measurement parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----|--------------|--------------| +| barometerMeasReport-r16
Indicates whether the UE supports uncompensated barometric pressure measurement reporting upon request from the network. | UE | No | No | No | +| earlyMeasLog-r17
Indicates whether the UE supports the storage of Early Measurement Logging in logged measurements and the reporting upon request from the network as specified in TS 38.331 [9]. | UE | No | No | No | +| excessPacketDelay-r17
Indicates whether the UE supports the UL PDCP excess packet delay measurement per DRB as specified in TS 38.314 [26]. A UE that supports the UL PDCP excess packet delay measurement shall also support the measurement configuration and reporting as specified in TS 38.331 [9]. | UE | No | No | No | +| gnss-Location-r16
Indicates whether the UE is equipped with a GNSS or A-GNSS receiver that may be used to provide detailed location information along with SON, MDT, and NTN related measurements in RRC_CONNECTED, RRC_IDLE and RRC_INACTIVE state. A UE shall set this field to supported if it indicates the support of nonTerrestrialNetwork-r17 . | UE | CY | No | No | +| immMeasBT-r16
Indicates whether the UE supports Bluetooth measurements in RRC_CONNECTED state. | UE | No | No | No | +| immMeasWLAN-r16
Indicates whether the UE supports WLAN measurements in RRC_CONNECTED state. | UE | No | No | No | +| loggedMDT-PNI-NPN-r18
Indicates whether the UE supports Logged MDT for PNI-NPN(s). | UE | No | No | No | +| loggedMDT-SNPN-r18
Indicates whether the UE supports Logged MDT for SNPN(s). | UE | No | No | No | +| loggedMeasBT-r16
Indicates whether the UE supports Bluetooth measurements in RRC_IDLE and RRC_INACTIVE state. | UE | No | No | No | +| loggedMeasurements-r16
Indicates whether the UE supports logged measurements in RRC_IDLE and RRC_INACTIVE state. A UE that supports logged measurements shall support both periodical logging and event-triggered logging. The minimum memory size of MDT logged measurements is 64KB. | UE | No | No | No | +| loggedMeasWLAN-r16
Indicates whether the UE supports WLAN measurements in RRC_IDLE and RRC_INACTIVE state. | UE | No | No | No | +| multipleCEF-Report-r17
Indicates whether the UE supports the storage and delivery of multiple CEF reports upon request from the network as specified in TS 38.331 [9]. | UE | No | No | No | +| orientationMeasReport-r16
Indicates whether the UE supports orientation information reporting upon request from the network. | UE | No | No | No | +| sigBasedLogMDT-OverrideProtect-r17
Indicates whether the UE supports the override protection of the signalling based logged measurements configured in NR. | UE | No | No | No | +| speedMeasReport-r16
Indicates whether the UE supports speed information reporting upon request from the network. | UE | No | No | No | +| uiPDCP-Delay-r16
Indicates whether the UE supports UL PDCP Packet Average Delay measurement (as specified in TS 38.314 [26]) and reporting in RRC_CONNECTED state. | UE | No | No | No | + +### 4.2.19 High speed parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----|--------------|--------------| +| demodulationEnhancement-r16
Indicates whether the UE supports the enhanced demodulation processing for HST-SFN joint transmission scheme with velocity up to 500km/h as specified in TS 38.101-4 [18]. This field applies to MN configured demodulation enhancement when MR-DC is not configured and SN configured demodulation enhancement when (NG)EN-DC is configured. | UE | No | No | FR1 only | +| intraNR-MeasurementEnhancement-r16
Indicates whether the UE supports the enhanced intra-NR RRM requirements to support high speed up to 500 km/h as specified in TS 38.133 [5]. This field applies to MN configured measurement enhancement when MR-DC is not configured and SN configured measurement enhancement when (NG)EN-DC is configured.
The UE can include this field only if the UE does not indicate the support of measurementEnhancement-r16 and interRAT-MeasurementEnhancement-r16 .
Otherwise, the UE does not include this field. | UE | No | No | FR1 only | +| interRAT-MeasurementEnhancement-r16
Indicates whether the UE supports the enhanced inter-RAT E-UTRAN RRM requirements to support high speed up to 500 km/h as specified in TS 38.133 [5]. This field applies to MN configured measurement enhancement.
The UE can include this field only if the UE does not indicate the support of measurementEnhancement-r16 and intraNR-MeasurementEnhancement-r16 .
Otherwise, the UE does not include this field. | UE | No | No | FR1 only | +| measurementEnhancement-r16
Indicates whether the UE supports the enhanced intra-NR and inter-RAT E-UTRAN RRM requirements for MN configured measurement enhancement when MR-DC is not configured, and the enhanced intra-NR RRM requirements for SN configured measurement enhancement when (NG)EN-DC is configured, to support high speed up to 500 km/h as specified in TS 38.133 [5]. | UE | No | No | FR1 only | +| measurementEnhancementCA-r17
Indicates whether the UE supports the enhanced RRM requirements for carrier aggregation to support high speed up to 500 km/h as specified in TS 38.133 [5].

UE indicating support of this feature shall indicate support of measurementEnhancement-r16 or intraNR-MeasurementEnhancement-r16 . | UE | No | No | FR1 only | +| measurementEnhancementInterFreq-r17
Indicates whether the UE supports the enhanced RRM requirements for inter-frequency measurements in connected mode to support high speed up to 500 km/h as specified in TS 38.133 [5].

UE indicating support of this feature shall indicate support of measurementEnhancement-r16 or intraNR-MeasurementEnhancement-r16 . | UE | No | No | FR1 only | + +### 4.2.20 Application layer measurement parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----|--------------|--------------| +| qoe-AdditionalMemoryMeasReport-r18
Indicates the minimum AS layer memory size the UE supports for QoE measurement in RRC_IDLE and RRC_INACTIVE in addition to the "AS layer memory size for QoE paused measurement reports". Value kB128 means the UE supports at least 128 kilobytes for this purpose, and so on. A UE supporting this feature shall also support qoe-IdleInactiveMeasReport-r18 . | UE | No | No | No | +| qoe-IdleInactiveMeasReport-r18
Indicates whether the UE supports NR QoE Measurement Collection in RRC_IDLE and RRC_INACTIVE states for the services indicated with qoe-Streaming-MeasReport-r17 or qoe-MTSI-MeasReport-r17 or qoe-VR-MeasReport-r17 . | UE | No | No | No | +| qoe-NRDC-MeasReport-r18
Indicates whether the UE supports to receive QoE configuration(s) via SRB1 and/or SRB3 (if supported) from SN, and send the corresponding QoE report(s) via SRB4 and/or SRB5 (if the UE supports srb5). A UE supporting this feature shall also support qoe-Streaming-MeasReport-r17 or qoe-MTSI-MeasReport-r17 or qoe-VR-MeasReport-r17 . | UE | No | No | No | +| qoe-PriorityBasedDiscarding-r18
Indicates whether the UE supports to discard QoE report(s) stored during QoE pause for UE in RRC_CONNECTED and stored in RRC_IDLE/RRC_INACTIVE based on the priority information gNB provides. A UE supporting this feature shall also support qoe-Streaming-MeasReport-r17 or qoe-MTSI-MeasReport-r17 or qoe-VR-MeasReport-r17 , and conditionally support qoe-IdleInactiveMeasReport-r18 for QoE measurement reports in RRC_IDLE/RRC_INACTIVE. | UE | No | No | No | +| qoe-Streaming-MeasReport-r17
Indicates whether the UE supports NR QoE Measurement Collection for streaming services, see TS 26.247 [29]. | UE | No | No | No | +| qoe-MTSI-MeasReport-r17
Indicates whether the UE supports NR QoE Measurement Collection for MTSI services, see TS 26.114 [30]. | UE | No | No | No | +| qoe-VR-MeasReport-r17
Indicates whether the UE supports NR QoE Measurement Collection for VR services, see TS 26.118 [31]. | UE | No | No | No | +| ran-VisibleQoE-Streaming-MeasReport-r17
Indicates whether the UE supports RAN visible QoE Measurement Collection for streaming services. A UE supporting this feature shall also support qoe-Streaming-MeasReport-r17 . | UE | No | No | No | +| ran-VisibleQoE-VR-MeasReport-r17
Indicates whether the UE supports RAN visible QoE Measurement Collection for VR services. A UE supporting this feature shall also support qoe-VR-MeasReport-r17 . | UE | No | No | No | +| srb5-r18
Indicates whether the UE supports SRB5 which is a direct SRB between the SN and the UE as specified in TS 37.340 [7]. A UE supporting this feature shall also indicate support of qoe-NRDC-MeasReport-r18 . | UE | No | No | No | +| ul-MeasurementReportAppLayer-Seg-r17
Indicates whether the UE supports RRC segmentation of the MeasurementReportAppLayer message in UL, as specified in TS 38.331 [9]. | UE | No | No | No | + +### 4.2.21 RedCap Parameters + +#### 4.2.21.1 Definition of RedCap UE + +RedCap UE is the UE with reduced capability: + +- The maximum bandwidth is 20 MHz for FR1, and is 100 MHz for FR2. UE features and corresponding capabilities related to UE bandwidths wider than 20 MHz in FR1 or wider than 100 MHz in FR2 are not supported by RedCap UEs; + +- The maximum mandatory supported DRB number is 8; +- The mandatory supported PDCP SN length is 12 bits while 18 bits being optional; +- The mandatory supported RLC AM SN length is 12 bits while 18 bits being optional; +- For FR1, 1 DL MIMO layer if 1 Rx branch is supported, and 2 DL MIMO layers if 2 Rx branches are supported; for FR2, either 1 or 2 DL MIMO layers can be supported, while 2 Rx branches are always supported. For FR1 and FR2, UE features and corresponding capabilities related to more than 2 UE Rx branches or more than 2 DL MIMO layers, as well as UE features and capabilities related to more than 1 UE Tx branch or more than 1 UL MIMO layer are not supported by RedCap UEs; +- CA, MR-DC, DAPS, CPAC and IAB (i.e., the RedCap UE is not expected to act as IAB node) related UE features and corresponding capabilities are not supported by RedCap UEs. All other feature groups or components of the feature groups as captured in TR 38.822 [24] as well as capabilities specified in this specification remain applicable for RedCap UEs same as other UEs, unless indicated otherwise. + +#### 4.2.21.2 General parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----|--------------| +| ncd-SSB-ForRedCapInitialBWP-SDT-r17
Indicates that the UE supports using (e)RedCap-specific initial DL BWP associated with NCD-SSB for SDT. If absent, the UE only supports SDT in an initial DL BWP that includes the CD-SSB. For MO-SDT, UE supporting this feature shall indicate support of supportOfRedCap-r17 or supportOfERedCap-r18 , and ra-SDT-r17 and/or cq-SDT-r17 . For MT-SDT, UE supporting this feature shall indicate support of supportOfRedCap-r17 or supportOfERedCap-r18 and mt-SDT-r18 and/or mt-CG-SDT-r18 . | UE | No | No | +| supportOf16DRB-RedCap-r17
Indicates whether the (e)RedCap UE supports 16 DRBs. This capability is only applicable for (e)RedCap UEs. | UE | No | No | +| supportOfRedCap-r17
Indicates that the UE is a RedCap UE with comprised of at least the following functional components:
  • - Maximum FR1 RedCap UE bandwidth is 20 MHz;
  • - Maximum FR2 RedCap UE bandwidth is 100 MHz;
  • - Support of RedCap early indication based on Msg1, MsgA (if UE indicated support of twoStepRACH-r16) and Msg3 for random access;
  • - Separate initial UL BWP for RedCap UEs;
    • - It includes the configuration(s) needed for RedCap UE to perform random access
    • - Enabling/disabling of frequency hopping for common PUCCH resources
  • - Separate initial DL BWP for RedCap UEs;
    • - It includes CSS/CORESET for random access
    • - For separate initial DL BWP used for paging, CD-SSB is included
    • - For separate initial DL BWP only used for RACH, SSB may or may not be included
    • - For separate initial DL BWP used in connected mode as BWP#0 configuration option 1, CD-SSB is included
  • - 1 UE-specific RRC configured DL BWP per carrier;
  • - 1 UE-specific RRC configured UL BWP per carrier;
  • - UE-specific RRC-configured DL BWP with CD-SSB or NCD-SSB;
  • - NCD-SSB based measurements in RRC-configured DL BWP.
A RedCap UE shall set the field to supported . | UE | CY | No | + +#### 4.2.21.3 PDCP parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----|--------------| +| longSN-RedCap-r17
Indicates whether the (e)RedCap UE supports 18 bit length of PDCP sequence number. This capability is only applicable for (e)RedCap UEs. | UE | No | No | + +#### 4.2.21.4 RLC parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----|--------------| +| am-WithLongSN-RedCap-r17
Indicates whether the (e)RedCap UE supports AM DRB with 18 bit length of RLC sequence number. This capability is only applicable for (e)RedCap UEs. | UE | No | No | + +#### 4.2.21.5 MeasAndMobParameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----|--------------|--------------| +| rrm-RelaxationRRC-ConnectedRedCap-r17
Indicates whether (e)RedCap UE supports Rel-17 relaxed RRM measurements in RRC_CONNECTED as specified in TS 38.331 [9]. | UE | No | No | No | + +#### 4.2.21.6 Physical layer parameters + +##### 4.2.21.6.1 BandNR parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----|--------------|--------------| +| bwp-WithoutCD-SSB-OrNCD-SSB-RedCap-r17
Indicates support of RRC-configured DL BWP without CD-SSB or NCD-SSB. The UE can include this field only if the UE supports supportOfRedCap-r17 or supportOfERedCap-r18 . | Band | No | N/A | N/A | +| dl-PRS-MeasurementWithRxFH-RRC-IdleForRedCap-r18
Indicates whether UE supports PRS measurement with Rx frequency hopping in RRC_IDLE for RedCap UEs.
A UE supporting this feature shall also indicates the support of FG41-5-1. | Band | No | N/A | N/A | +| dl-PRS-MeasurementWithRxFH-RRC-InactiveForRedCap-r18
Indicates whether UE supports of PRS measurement with Rx frequency hopping in RRC_INACTIVE for RedCap UEs.
A UE supporting this feature shall also indicates the support of FG41-5-1 and prs-ProcessingRRC-Inactive-r17 . | Band | No | N/A | N/A | +| halfDuplexFDD-TypeA-RedCap-r17
Indicates support of Half-duplex FDD operation (instead of full-duplex FDD operation) type A for RedCap UE. The UE can include this field only if the UE supports supportOfRedCap-r17 . | Band | No | FDD only | FR1 only | + +### 4.2.22 eRedCap Parameters + +#### 4.2.22.1 Definition of eRedCap UE + +eRedCap UE is the UE with reduced peak data rate and, with or without reduced baseband bandwidth in FR1: + +- The maximum bandwidth is 20 MHz for FR1. UE features and corresponding capabilities related to UE bandwidths wider than 20 MHz in FR1 are not supported by eRedCap UEs. eRedCap UEs do not support operation in FR2 and in FR1 60kHz SCS. +- CA, MR-DC, DAPS, CPAC and IAB (i.e., the eRedCap UE is not expected to act as IAB node) related UE features and corresponding capabilities are not supported by eRedCap UEs. All other feature groups or components of the feature groups as captured in TR 38.822 [24] as well as capabilities specified in this specification remain applicable for eRedCap UEs same as other UEs, unless indicated otherwise. + +#### 4.2.22.2 General parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----|--------------|--------------| +| eRedCapIgnoreCapabilityFiltering-r18
Indicates that the eRedCap UE ignores the capability filtering enquiry and conveys all the supported bands in the appliedFreqBandListFilter , as specified in TS 38.331 [9].
An UE indicating this field shall also indicate the support of supportOfERedCap-r18 . | UE | No | No | FR1 only | +| eRedCapNotReducedBB-BW-r18
Indicates that the UE is an eRedCap UE without reduced baseband bandwidth in FR1.
DL/UL peak data rate of 10 Mbps corresponding to $v_{Layers} \cdot Q_m \cdot f = 0.75$ when $v_{Layers} = 1$ and $v_{Layers} \cdot Q_m \cdot f = 0.8$ when $v_{Layers} = 2$ .
UE supporting this feature shall also indicate the support of supportOfERedCap-r18 . | UE | No | No | FR1 only | +| supportOfERedCap-r18
Indicates that the UE is an eRedCap UE with reduced peak data rate and reduced baseband bandwidth in FR1. This capability comprises of at least the following functional components:

The following functional components are the same as for supportOfRedCap-r17 :
  • - Maximum FR1 bandwidth is 20 MHz;
  • - Support of RedCap early indication based on Msg1 for 4-step RACH;
  • - Separate initial UL BWP (NOTE-1):
    • - It includes the configuration(s) needed to perform random access
    • - Enabling/disabling of frequency hopping for common PUCCH resources
  • - Separate initial DL BWP (NOTE-1);
    • - It includes CSS/CORESET for random access
    • - For separate initial DL BWP used for paging, CD-SSB is included
    • - For separate initial DL BWP only used for RACH, SSB may or may not be included
    • - For separate initial DL BWP used in connected mode as BWP#0 configuration option 1 (as specified in Annex B2 in TS 38.331 [9]), CD-SSB is included
  • - 1 UE-specific RRC configured DL BWP per carrier;
  • - 1 UE-specific RRC configured UL BWP per carrier;
  • - UE-specific RRC-configured DL BWP with CD-SSB or NCD-SSB;
  • - NCD-SSB based measurements in RRC-configured DL BWP.

The following functional components are new compared to supportOfRedCap-r17 :
  • - DL/UL peak data rate of 10 Mbps corresponding to v_{Layers} \cdot Q_m \cdot f = 3.2.
    • - If UE supporting this feature also indicates eRedCapNotReducedBB-BW-r18, this component is not applicable.
  • - Maximum number of PDSCH/PUSCH PRBs that can be scheduled/configured for unicast is 25 PRBs for 15 kHz SCS and is 12 PRBs for 30 kHz SCS.
    • - If UE supporting this feature also indicates eRedCapNotReducedBB-BW-r18, this component is not applicable.
  • - Relaxed processing timeline of 1/0.5 ms for 15/30 kHz SCS when the RAR PDSCH and Msgb PDSCH (if supported) is larger than 25/12 PRBs for 15/30 kHz SCS.
    • - If UE supporting this feature also indicates eRedCapNotReducedBB-BW-r18, this component is only applicable during contention based random access.
  • - Network-configurable separate eRedCap early indication in Msg1.
  • - Support of eRedCap early indication based on MsgA PUSCH, if UE indicates the support of twoStepRACH-r16, and Msg3.
  • - Maximum number of Msg4 PDSCH PRBs, which is scheduled by DCI scrambled by a TC-RNTI, that can be decoded and maximum number of Msg 3 PUSCH PRBs and Msg A PUSCH PRBs (if supported), which 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, that can be transmitted is 25 PRBs for 15 kHz SCS and is 12 PRBs for 30 kHz SCS.

An eRedCap UE shall set this field to supported but shall not indicate support of supportOfRedCap-r17 .
NOTE 1: The Separate initial DL/UL BWP is shared by RedCap UEs and eRedCap UEs when the access of both UEs is allowed and RedCap-specific initial BWP is configured. | UE | CY | No | FR1 only | + +### 4.2.23 NCR Parameters + +#### 4.2.23.1 Mandatory NCR-MT features + +Table 4.2.23.1-1, Table 4.2.23.1-2 capture feature groups, which are mandatory for an NCR-MT. + +CA, MR-DC, handover (e.g. CHO, DAPS, CPAC, etc) related UE features and corresponding capabilities are not supported by an NCR-MT. All other feature groups or components of the feature groups as captured in TR 38.822 [24] as well as capabilities specified in this specification are optional for an NCR-MT, unless indicated otherwise. + +**Table 4.2.23.1-1: Layer-1 mandatory features for NCR-MT** + +| Features | Index | Feature group | Components | +|------------------------------------------------------|-------|--------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0. Waveform, modulation, subcarrier spacings, and CP | 0-1 | CP-OFDM waveform for DL and UL | 1) CP-OFDM for DL
2) CP-OFDM for UL | +| | 0-3 | DL modulation scheme | 1) QPSK modulation
2) 16QAM modulation
3) 64QAM modulation for FR1 | +| | 0-4 | UL modulation scheme | 1) QPSK modulation
2) 16QAM modulation | +| 1. Initial access and mobility | 1-1 | Basic initial access channels and procedures | 1) RACH preamble format
2) SS block based RRM measurement
3) Broadcast SIB reception including RMSI/OSI and paging | +| 2. MIMO | 2-1 | Basic PDSCH reception | 1) Data RE mapping
2) Single layer transmission
3) Support one TCI state | +| | 2-5 | Basic downlink DMRS for scheduling type A | 1) Support 1 symbol FL DMRS without additional symbol(s)
2) Support 1 symbol FL DMRS and 1 additional DMRS symbol
3) Support 1 symbol FL DMRS and 2 additional DMRS symbols for at least one port. | +| | 2-6 | Basic downlink DMRS for scheduling type B | 1) Support 1 symbol FL DMRS without additional symbol(s)
2) Support 1 symbol FL DMRS and 1 additional DMRS symbol | +| | 2-12 | Basic PUSCH transmission | Data RE mapping
Single layer (single Tx) transmission
Single port, single resource SRS transmission (SRS set use is configured as for codebook) | +| | 2-16 | Basic uplink DMRS (uplink) for scheduling type A | 1) Support 1 symbol FL DMRS without additional symbol(s)
2) Support 1 symbol FL DMRS and 1 additional DMRS symbols
3) Support 1 symbol FL DMRS and 2 additional DMRS symbols | +| | 2-16a | Basic uplink DMRS for scheduling type B | 1) Support 1 symbol FL DMRS without additional symbol(s)
2) Support 1 symbol FL DMRS and 1 additional DMRS symbol | +| | 2-32 | Basic CSI feedback | 1) Type I single panel codebook based PMI (further discuss which mode or both to be supported as mandatory)
2) 2Tx codebook for FR1 and FR2
3) 4Tx codebook for FR1
4) 8Tx codebook for FR1 when configured as wideband CSI report
7) a-CSI on PUSCH (at least Z value $\geq 14$ symbols, detail processing time to be discussed separately)
further check a-CSI on p-CSI-RS and/or SP-CSI-RS from component-7 | +| | 2-50 | Basic TRS | 1) Support of TRS (mandatory)
2) All the periodicity are supported. | +| | 2-52 | Basic SRS | 1) Support 1 port SRS transmission
2) Support periodic/aperiodic SRS transmission | +| 3. DL control channel and procedure | 3-1 | Basic DL control channel | 1) One configured CORESET per BWP per cell in addition to CORESET0
- CORESET resource allocation of 6RB bit-map and duration of 1 – 3 OFDM symbols for FR1
- For type 1 CSS without dedicated RRC configuration and for type 0, 0A, and 2 CSSs, CORESET resource allocation of 6RB bit-map and duration 1-3 OFDM symbols for FR2
- For type 1 CSS with dedicated RRC configuration and for type 3 CSS, UE specific SS, CORESET resource allocation of 6RB bit-map and duration 1-2 OFDM symbols for FR2
- REG-bundle sizes of 2/3 RBs or 6 RBs
- Interleaved and non-interleaved CCE-to-REG mapping
- Precoder-granularity of REG-bundle size
- PDCCH DMRS scrambling determination
- TCI state(s) for a CORESET configuration
2) CSS and UE-SS configurations for unicast PDCCH transmission per BWP per cell
- PDCCH aggregation levels 1, 2, 4, 8, 16
- UP to 3 search space sets in a slot for a scheduled SCell per BWP
This search space limit is before applying all dropping rules.
- For type 1 CSS with dedicated RRC configuration, type 3 CSS, and UE-SS, the monitoring occasion is within the first 3 OFDM symbols of a slot
- For type 1 CSS without dedicated RRC configuration and for type 0, 0A, and 2 CSS, the monitoring occasion can be any OFDM symbol(s) of a slot, with the monitoring occasions for any of Type 1- | + +| | | | | +|-------------------------------------|-----|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | CSS without dedicated RRC configuration, or Types 0, 0A, or 2 CSS configurations within a single span of three consecutive OFDM symbols within a slot
3) Monitoring DCI formats 0_0, 1_0, 0_1, 1_1
4) Number of PDCCH blind decodes per slot with a given SCS follows Case 1-1 table
5) Processing one unicast DCI scheduling DL and one unicast DCI scheduling UL per slot per scheduled CC for FDD | +| 4. UL control channel and procedure | 4-1 | Basic UL control channel | 1) PUCCH format 0 over 1 OFDM symbols once per slot
2) PUCCH format 0 over 2 OFDM symbols once per slot with frequency hopping as "enabled"
3) PUCCH format 1 over 4 – 14 OFDM symbols once per slot with intra-slot frequency hopping as "enabled"
5) One SR configuration per PUCCH group
6) HARQ-ACK transmission once per slot with its resource/timing determined by using the DCI
7)
SR/HARQ multiplexing once per slot using a PUCCH when SR/HARQ-ACK are supposed to be sent by overlapping PUCCH resources with the same starting symbols in a slot
8) HARQ-ACK piggyback on PUSCH with/without aperiodic CSI once per slot when the starting OFDM symbol of the PUSCH is the same as the starting OFDM symbols of the PUCCH resource that HARQ-ACK would have been transmitted on
9) Semi-static beta-offset configuration for HARQ-ACK
10) Single group of overlapping PUCCH/PUCCH and overlapping PUCCH/PUSCH s per slot per PUCCH cell group for control multiplexing | + +| | | | | +|-------------------------------|------|--------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 4-10 | Dynamic HARQ-ACK codebook | Dynamic HARQ-ACK codebook | +| 5. Scheduling /HARQ operation | 5-1 | Basic scheduling/HARQ operation | 1) Frequency-domain resource allocation
- RA Type 0 only and Type 1 only for PDSCH without interleaving
- RA Type 1 for PUSCH without interleaving
2) Time-domain resource allocation
- 1-14 OFDM symbols for PUSCH once per slot
- One unicast PDSCH per slot
- Starting symbol, and duration are determined by using the DCI
- PDSCH mapping type A with 7-14 OFDM symbols
- PUSCH mapping type A and type B
- For type 1 CSS without dedicated RRC configuration and for type 0, 0A, and 2 CSS, PDSCH mapping type A with {4-14} OFDM symbols and type B with {2, 4, 7} OFDM symbols
3) TBS determination
4) Nominal UE processing time for N1 and N2 (Capability #1)
5) HARQ process operation with configurable number of DL HARQ processes of up to 16
6) Cell specific RRC configured UL/DL assignment for TDD
7) Dynamic UL/DL determination based on L1 scheduling DCI with/without cell specific RRC configured UL/DL assignment
9) In TDD support at most one switch point per slot for actual DL/UL transmission(s)
10) DL scheduling slot offset K0=0
12) UL scheduling slot offset K2<=12

For type 1 CSS without dedicated RRC configuration and for type 0, 0A, and 2 CSS, interleaving for VRB-to-PRB mapping for PDSCH | +| 6. CA/DC, BWP, SUL | 6-1 | Basic BWP operation with restriction | 1) 1 UE-specific RRC configured DL BWP per carrier
2) 1 UE-specific RRC configured UL BWP per carrier
3) RRC reconfiguration of any parameters related to BWP
4) BW of a UE-specific RRC configured BWP includes BW of CORESET#0 (if CORESET#0 is present) and SSB for PCell and BW of the UE-specific RRC configured BWP includes SSB for SCell if there is SSB on SCell | +| 7. Channel coding | 7-1 | Channel coding | 1) LDPC encoding and associated functions for data on DL and UL
2) Polar encoding and associated functions for PBCH, DCI, and UCI
3) Coding for very small blocks | +| 8. UL TPC | 8-3 | Basic power control operation | 1) Accumulated power control mode for closed loop
2) 1 TPC command loop for PUSCH, PUCCH respectively
3) One or multiple DL RS configured for pathloss estimation
4) One or multiple p0-alpha values configured for open loop PC
5) PUSCH power control
6) PUCCH power control
7) PRACH power control
8) SRS power control
9) PHR | + +Table 4.2.23.1-2: Layer-2 and Layer-3 mandatory features for NCR-MT + +| Features | Index | Feature group | Components | Additional information | +|------------|-------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------| +| 0. General | 0-0 | NCR procedures | 1) Side control information over MAC CE and RRC, as specified in TS 38.321 [8] and TS 38.331 [9], respectively.
2) Switching OFF NCR-Fwd during radio link failure in TS 38.331 [9], beam failure recovery in TS 38.321 [8]. | | +| 1. PDCP | 1-0 | Basic PDCP procedures | 1) (de)Ciphering on SRB
2) Integrity protection on SRB
4) Re-ordering and in-order delivery
6) Duplicate discarding
7) 12bits SN | | +| 2. RLC | 2-0 | Basic RLC procedures | 1) RLC TM
2) RLC AM with 12bits SN | | +| | 2-4 | NR RLC SN size for SRB | NR RLC SN size for SRB | | +| 3. MAC | 3-0 | Basic MAC procedures | 1) RA procedure on PCell
2) NCR-MT initiated RA procedure (including for beam recovery purpose)
3) NW initiated RA procedure (i.e. based on PDCCH)
4) Support of ssb-Threshold and association between preamble/PRACH occasion and SSB
5) Preamble grouping
6) UL single TA maintenance
7) HARQ operation for DL and UL
8) LCH prioritization
9) Prioritized bit rate
10) Multiplexing
11) SR with single SR configuration
12) BSR
13) PHR
14) 8bits and 16bits L field | | +| 9. RRC | 9-1 | RRC buffer size | Maximum overall RRC configuration size | 45 Kbytes | +| | 9-2 | RRC processing time | 1) RRC connection establishment
3) RRC connection reconfiguration without SCell addition/release and SCG establishment/modification/release
4) RRC connection re-establishment.
5) RRC connection reconfiguration with sync procedure
8) Initial security activation
10) UE capability transfer | 1) to 3) 10ms
4) 10ms
5): 10ms + additional delay (cell search time and synchronization) defined in TS 38.133
8) 5ms
10) 80ms | + +#### 4.2.23.2 General Parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----|--------------|--------------| +| inactiveStateNCR-r18
Indicates whether the NCR-MT supports RRC_INACTIVE as specified in TS 38.331 [9]. | NCR-MT | No | No | No | +| nonDRB-NCR-r18
Indicates whether the NCR-MT supports SRB2 configuration without a DRB, as specified in TS 38.331 [9]. | NCR-MT | No | No | No | +| supportedNumberOfDRBs-NCR-r18
Indicates the number of DRB that NCR-MT supports. If absent, NCR-MT does not support DRB. If absent, NCR-MT also does not support SDU discard in PDCP and RLC, and counter check in RRC.
Value n1 indicates support of 1 DRB, value n16 indicates the support of 16 DRBs. | NCR-MT | No | No | No | + +#### 4.2.23.3 SDAP Parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----|--------------|--------------| +| sdap-HeaderNCR-r18
Indicates whether the NCR-MT supports UL SDAP header and SDAP End-marker, as specified in TS 37.324 [25]. | NCR-MT | No | No | No | +| sdap-QoS-NCR-r18
Indicates whether the NCR-MT supports flow-based QoS and multiple flows to 1 DRB mapping, as specified in TS 37.324 [25]. | NCR-MT | No | No | No | + +#### 4.2.23.4 PDCP Parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-------------------------------------------------------------------------------------------------------|--------|----|--------------|--------------| +| longSN-NCR-r18
Indicates whether the NCR-MT supports 18 bit length of PDCP sequence number. | NCR-MT | No | No | No | + +#### 4.2.23.5 RLC Parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|-------------------------------------------------------------------------------------------------------------------------|--------|----|--------------|--------------| +| am-WithLongSN-NCR-r18
Indicates whether the NCR-MT supports AM DRB with 18 bit length of RLC sequence number. | NCR-MT | No | No | No | + +#### 4.2.23.6 Physical layer Parameters + +##### 4.2.23.6.1 Phy-Parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----|--------------|--------------| +| ncr-AdaptiveBeamBackhaulAndC-Link-r18
Indicates whether NCR supports backhaul link beam determination based on predefined rule.
The UE indicating support of this feature shall also indicate support of timeDurationForQCL , tci-StatePDSCH and additionalActiveTCI-StatePDCCH . | NCR-MT | No | No | No | +| ncr-BackhaulBeamInd-r18
Indicates whether NCR supports dedicated signalling for backhaul link beam indication.
The UE indicating support of this feature shall also indicate support of ncr-AdaptiveBeamBackhaulAndC-Link-r18 . | NCR-MT | No | No | No | +| ncr-AperiodicBeamInd-AccessLink-r18
Indicates whether NCR supports aperiodic beam indication for access link. The capability signalling comprises the following parameters:
  • - ncr-AperiodicBeamInd-r18 indicates whether NCR supports aperiodic beam indication for access link,
  • - ncr-SlotOffset-r18 indicates the value of supported slot-offset for reference slot. ncr-SlotOffset-r18 is selected based on the SCS of the PDCCH received by the NCR-MT. If 0 is reported, the NCR expects that the time resource in NCR-AperiodicFwdConfig of the aperiodic beam indication is at least after the end of time resource for PDCCH carrying the DCI for aperiodic beam indication.
| NCR-MT | No | No | No | +| ncr-Semi-PersistentBeamInd-AccessLink-r18
Indicates whether NCR supports semi-persistent beam indication for access link, priority flag for semi-persistent indication and MAC CE override of the RRC configured of the beam index(es) at activation of semi-persistent beam indication. | NCR-MT | No | No | No | +| ncr-SimultaneousUL-BackhaulAndC-Link-r18
Indicates whether NCR supports simultaneous UL transmission of backhaul link and C-link. | NCR-MT | No | No | No | + +### 4.2.24 Aerial UE Parameters + +| Definitions for parameters | Per | M | FDD-TDD DIFF | FR1-FR2 DIFF | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----|--------------|--------------| +| aerialUE-Capability-r18
Indicates whether the UE supports aerial UE enhancements. | UE | No | No | No | +| altitudeMeas-r18
Indicates whether the UE supports altitude based measurement reporting as specified in TS 38.331 [9]. It is mandatory if the UE supports aerialUE-Capability-r18 . | UE | CY | No | No | +| altitudeBasedSSB-ToMeasure-r18
Indicates whether the UE supports altitude based ssb-ToMeasure as specified in TS 38.331 [9]. | UE | No | No | No | +| eventAxHy-r18
Indicates whether the UE supports events A3H1, A3H2, A4H1, A4H2, A5H1, and A5H2 as specified in TS 38.331 [9]. If the UE indicates support of eventAxHy-r18 , then the UE additionally supports multipleCellsMeasExtension-r18 for eventA3H1, eventA3H2, eventA4H1, eventA4H2, eventA5H1, and eventA5H2 as specified in TS 38.331 [9]. | UE | No | No | No | +| flightPathReporting-r18
Indicates whether the UE supports reporting of the flight path plan through the procedure defined in TS 38.331 [9]. | UE | No | No | No | +| flightPathAvailabilityIndicationUAI-r18
Indicates whether the UE supports indication of the flight path availability through the UAI message as defined in TS 38.331 [9]. If a UE supports this capability, the UE shall also support flightPathReporting-r18 . | UE | No | No | No | +| multipleCellsMeasExtension-r18
Indicates whether the UE supports measurement reporting triggered based on a number of cells for eventA3, eventA4, and eventA5 as specified in TS 38.331 [9]. It is mandatory if the UE supports aerialUE-Capability-r18 . | UE | CY | No | No | +| simulMultiTriggerSingleMeasReport-r18
Indicates whether the UE supports, for all the events of the same type for which the entry condition applicable for the event has been satisfied, measurement reporting considering only the configuration of the event with the smallest value between the altitude of the UE and the corresponding altitude threshold, as specified in TS 38.331 [9] | UE | No | No | No | +| si-A2X-Service-r18
Indicates whether the UE supports A2X service(s) which include BRID, DAA or both using A2X communication as specified in TS 38.331 [9]. This field also indicates whether the UE supports the dedicated resource pools as specified in TS 38.331 for the corresponding A2X service(s). | UE | No | No | No | + +# 5 Optional features without UE radio access capability parameters + +## 5.1 PWS features + +| Definitions for feature | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CMAS
It is optional for UE to support CMAS reception as specified in TS 38.331 [9]. It is optional for a CMAS-capable UE to support Geofencing information ( warningAreaCoordinates ) as specified in TS 38.331 [9]. | +| ETWS
It is optional for UE to support ETWS reception as specified in TS 38.331 [9]. | +| KPAS
It is optional for UE to support Korean Public Alert System (KPAS) reception as specified in TS 38.331 [9]. KPAS uses the same AS mechanisms as defined for CMAS. Therefore a KPAS-capable UE shall support all behaviour that is included in TS 38.331 [9] and TS 38.304 [21] for a CMAS-capable UE. | +| EU-Alert
It is optional for UE to support EU-Alert reception as specified in TS 38.331 [9]. EU-Alert uses the same AS mechanisms as defined for CMAS. Therefore a EU-Alert-capable UE shall support all behaviour that is included in TS 38.331 [9] and TS 38.304 [21] for a CMAS-capable UE. | + +## 5.2 UE receiver features + +| Definitions for feature | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SU-MIMO Interference Mitigation advanced receiver
  • - R-ML (reduced complexity ML) receivers with enhanced inter-stream interference suppression for SU-MIMO transmissions with rank 2 with 2 RX antennas
  • - R-ML (reduced complexity ML) receivers with enhanced inter-stream interference suppression for SU-MIMO transmissions with rank 2, 3, and 4 with 4 RX antennas
UE supporting the feature is required to meet the Enhanced Receiver Type requirements in TS 38.101-4 [18]. | + +## 5.3 RRC connection + +| Definitions for feature | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RRC connection release with deprioritisation
It is optional for UE to support RRCRelease with deprioritisationReq as specified in TS 38.331 [9]. | +| RRC connection establishment failure with temporary offset
It is optional for UE to support RRC connection establishment failure with temporary offset ( Qoffsettemp ) as specified in TS 38.331 [9]. | +| Selection of acceptable E-UTRA cell upon HO failure during EPS fallback for emergency call
It is optional for UE to support selecting an acceptable E-UTRA cell supporting emergency call if no suitable E-UTRA cell is available upon handover failure during EPS fallback when the UE has an ongoing emergency call as specified in TS 38.331 [9]. | +| E-UTRA cell selection upon HO failure during EPS services fallback
It is optional for UE to support selecting a suitable E-UTRA cell, and support selecting an acceptable E-UTRA cell supporting emergency call if no suitable E-UTRA cell is available upon handover failure when the UE is performing emergency services fallback as specified in TS 38.331 [9]. | + +## 5.4 Other features + +| Definitions for feature | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Access Category 1 selection assistance information enhancement
It is optional for UE that is configured for delay tolerant service to support Access Category 1 selection assistance information enhancement, according to uac-AC1-SelectAssistInfo-r16 as specified in TS 38.331 [9]. | +| eCall over IMS
It is optional for UE to support eCall over IMS as specified in TS 38.331 [9]. | +| Equivalent SNPNS for cell (re)selection
It is optional for UE in SNPN access mode to support cell (re)selection for equivalent SNPNS as specified in TS 38.304 [21]. | +| HSDN cell reselection
It is optional for UE to support HSDN cell reselection priority handling in RRC_IDLE/RRC_INACTIVE as specified in TS 38.304 [21] and TS 38.331 [9]. | +| Minimization of service interruption
It is optional for UE to support minimization of service interruption including reporting to NAS of disaster roaming information for available PLMNs and Access Barring check for Access Identity 3, as specified in TS 38.331 [9]. | +| Mobile IAB cell reselection
It is optional for UE to support mobile IAB cell reselection priority handling in RRC_IDLE/RRC_INACTIVE, as specified in TS 38.304 [21] and TS 38.331 [9]. | +| Random access prioritization for MPS and MCS
It is optional for UE that is configured for MPS or MCS to support random access prioritization for Access Identity 1 or 2 as specified in TS 38.321 [8]. | +| Random access prioritisation for Slicing
It is optional for UE to support slice-based prioritisation for random access as specified in TS 38.321 [8]. | +| Random access partitioning for Slicing
It is optional for UE to support slice-based RACH partitioning as specified in TS 38.321 [8]. | +| Relaxed cell reselection on GEO
It is optional for UE to support the relaxed cell reselection on GEO. | +| Support of polarization signalling in NR NTN
It is optional for UE to support the polarization signalling in NR NTN comprised of the following functional components:
  • - Support polarization indication reception in SIB indicating DL and/or UL polarization information using respective polarization type parameters to indicate: RHCP or LHCP or linear;
  • - Support polarization signalling for target serving cell in handover command message;
  • - Support polarization signalling for non-serving cell in RRM measurement configuration.
| +| TRS occasions for idle mode and RRC_INACTIVE UEs
It is optional for UE to support reading TRS configuration from SIB and receiving L1 indication for TRS availability.
NOTE: Receiving L1 indication via DCI format 2_7 is supported only if the UE supports receiving DCI format 2_7. | + +## 5.5 Sidelink Features + +| Definitions for feature | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Short-term time-scale TDM for in-device coexistence
It is optional for UE to support prioritization between LTE sidelink transmission/reception and NR sidelink transmission/reception.
This field is only applicable if the UE supports at least one of sl-Reception-r16 , sl-TransmissionMode1-r16 and sl-TransmissionMode2-r16 , and if the UE supports V2X sidelink communication in the band combination. | +| Rank 2 PSSCH transmission
It is optional for UE to support rank 2 PSSCH transmission. This field is only applicable if the UE supports csi-ReportSidelink-r16 with csi-RS-PortsSidelink = p2. | +| Receiving NR sidelink of S-SSB
It is optional for UE to receive S-SSB in NR sidelink and support synchronisation to a reference UE. | + +## 5.6 RRM measurement features + +| Definitions for feature | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Enhanced RRM requirements for measurements in IDLE and INACTIVE modes
It is optional for UE to support enhanced RRM requirements for measurements for NTN bands (FR1 only and FDD only) in RRC_IDLE/RRC_INACTIVE as specified in TS 38.133 [5]. If UE does not support this feature, other NTN measurement requirements (as specified in TS 38.133 [5], clause 4.2C.2 for RRC_IDLE and clause 5.1C.2 for RRC_INACTIVE) are applied for both LEO and GEO. | +| Enhanced RRM requirements for measurements in IDLE and INACTIVE modes for ATG
It is optional for the UE in RRC_IDLE/RRC_INACTIVE to support the enhanced inter-frequency cell re-selection requirements for ATG (as specified in TS 38.133 Table 4.2D.2.4-2). If UE does not support this feature, other measurement requirements as specified in TS 38.133 [5], Table 4.2D.2.4-1 are applied. | +| High speed inter-frequency IDLE/INACTIVE measurements
It is optional for UE to support high speed inter-frequency measurements in RRC_IDLE/RRC_INACTIVE as specified in TS 38.133 [5]. | +| Location-based measurement initiation
It is optional for the UE in RRC_IDLE/RRC_INACTIVE to support location based RRM measurements of neighbour cells in NTN quasi-Earth fixed system as specified in TS 38.304 [21]. | +| Location-based measurement initiation for NTN Earth-moving system
It is optional for the UE in RRC_IDLE/RRC_INACTIVE to support location based RRM measurements of neighbour cells in NTN Earth-moving system as specified in TS 38.304 [21]. | +| Relaxed measurement
It is optional for UE to support relaxed RRM measurements of neighbour cells in RRC_IDLE/RRC_INACTIVE as specified in TS 38.304 [21]. | +| Rel-17 relaxed measurement for RRC_IDLE/RRC_INACTIVE
It is optional for RedCap UE to support Rel-17 relaxed RRM measurements of neighbour cells in RRC_IDLE/RRC_INACTIVE as specified in TS 38.304 [21]. | +| Skipping TN measurements
It is optional for the UE in RRC_IDLE/RRC_INACTIVE to support skipping the neighbour cell measurements for TN neighbour cells in an area where there is no TN network coverage as specified in TS 38.304 [21]. | +| Time-based measurement initiation
It is optional for the UE in RRC_IDLE/RRC_INACTIVE to support time based RRM measurements of neighbour cells in NTN quasi-Earth fixed system as specified in TS 38.304 [21]. | +| Time-based measurement initiation for NTN Earth-moving system
It is optional for the UE in RRC_IDLE/RRC_INACTIVE to support time based RRM measurements of neighbour cells in NTN Earth-moving system as specified in TS 38.304 [21]. | + +## 5.7 MDT and SON features + +| Definitions for feature | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Cross RAT RLF Report
It is optional for UE to support the delivery of EUTRA RLF report to an NR node upon request from the network. | +| Mobility history information storage
It is optional for UE to support the storage of PCell mobility history information and the reporting in UEInformationResponse message as specified in TS 38.331 [9]. | +| Radio Link Failure Report for inter-RAT MRO EUTRA
It is optional for UE to support:
  • - Inclusion of EUTRA CGI and associated TAC, if available, and otherwise to include the physical cell identity and carrier frequency of the target PCell of the failed handover as failedPCellId in RLF-Report upon request from the network as specified in TS 38.331 [9].
  • - Inclusion of EUTRA CGI and associated TAC as previousPCellId in RLF-Report as specified in TS 38.331 [9].
  • - Inclusion of eutraReconnectCellId in reconnectCellId in the RLF-Report as specified in TS 38.331 [9] upon UE has radio link failure or handover failure and successfully re-connected to an E-UTRA cell.
| +| RACH Partitioning Information
It is optional for UE to support the delivery of RACH partitioning related information via RACH report procedure, upon request from the network. | +| RLF Report for Fast MCG Recovery
It is optional for UE to support the delivery of the Fast MCG recovery related information in the RLF-Report. | +| RLF Report for Inter-system HO for Voice Fallback
It is optional for UE to support the delivery of an explicit indication in the RLF-report when mobility from NR due to voice fallback fails. | +| SCG Failure Report for CPAC
It is optional for UE to support the delivery of the CPAC related parameters for MRO in SCGFailureInformation message to the network. | +| SCG Failure Report for MRO
It is optional for UE to support the delivery of the SCG failure related parameters for MRO in SCGFailureInformation message to the network. | +| SON enhancements for NR-U
It is optional for UE to support the delivery of NR-U related information (FR1 only) in RA-report/SHR/RLF report, upon request from the network. | +| SON Report in SNPN
It is optional for UE to support collection and delivery of SON reports in SNPN. UE is not required to support all SON reports if it supports collection and delivery of the SON reports in SNPN, it may support one or more SON report for SNPN. | +| SpCell ID indication
It is optional for UE to support the delivery of the spCellIDD-r17 in the RA-Report, if the RA procedure is performed in a SCell of the MCG/SCG. | +| Uplink PDCP delay measurements upon MO update
It is optional for UE to support not resetting the UL PDCP Packet Average Delay measurement or UL PDCP excess packet delay measurement when the associated measurement object is modified. A UE supporting this feature shall also indicate the support of at least one of ulPDCP-Delay-r16 and excessPacketDelay-r17 . | + +## 5.8 Extended DRX features + +| Definitions for feature | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Rel-17 extended DRX in RRC_IDLE
It is optional for UE to support Rel-17 extended DRX cycle up to 10485.76 seconds and paging in extended DRX in RRC_IDLE as specified in TS 38.331 [9] and TS 38.304 [21]. A UE that supports extended DRX shall also support inactiveStatePO-Determination-r17 . | + +## 5.9 Sidelink Relay Features + +| Definitions for feature | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| L3 sidelink relay UE operation
It is optional for UE to support L3 sidelink relay UE operation as specified in TS 38.331 [9]. | +| L3 sidelink remote UE operation
It is optional for UE to support L3 sidelink remote UE operation as specified in TS 38.331 [9]. | +| L3 sidelink U2U relay UE operation
It is optional for UE to support L3 sidelink U2U relay UE operation as specified in TS 38.331 [9]. | +| L3 sidelink U2U remote UE operation
It is optional for UE to support L3 sidelink U2U remote UE operation as specified in TS 38.331 [9]. | +| MUSIM paging cause forward
It is optional for L2 sidelink relay UE or L2 sidelink remote UE to support forwarding MUSIM paging cause as defined in TS 38.331 [9]. | + +## 5.10 MBS features + +| Definitions for feature | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Broadcast reception
It is optional for UE to support broadcast reception as specified in TS 38.331 [9]. A UE that supports the feature shall also support:
  • - Group-common PDCCH/PDSCH for broadcast with CRC scrambled by MCCH-RNTI;
  • - Group-common PDCCH/PDSCH for broadcast with CRC scrambled by G-RNTI(s) for MTCH;
  • - CFR configuration for broadcast;
  • - CORESET and common search space for broadcast;
  • - DCI format 4_0 with CRC scrambled with G-RNTI/MCCH-RNTI for broadcast;
  • - Inter-slot TDM between unicast PDSCH and MCCH group-common PDSCH or MTCH group-common PDSCH, or between MCCH group-common PDSCH and MTCH group-common PDSCH, or among unicast PDSCH and MCCH group-common PDSCH and MTCH group-common PDSCH in different slots;
  • - MCCH change notification indication via DCI;
  • - RRC configured slot-level repetition up to 8 for MTCH;
  • - One G-RNTI per UE is supported for broadcast reception;
  • - Support of FDMed MCCH and PBCH;
  • - Support of up to 64QAM for FR1/FR2;
  • - 4 broadcast MRBs as the minimum number;
  • - PDCP 12 bits SN;
  • - ROHC with profiles 0x0000, 0x0001 and 0x0002;
  • - 4 ROHC context sessions;
  • - RLC UM with 6 bits SN;
  • - RLC UM with 12 bits SN;
  • - DRX with long DRX cycle for MBS broadcast as specified in TS 38.321 [8].
| + +## 5.11 Idle/inactive measurement for voice fallback features + +| Definitions for feature | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Idle/Inactive measurement for voice fallback
It is optional for UE to support the idle/inactive measurement for EPS fallback in RRC_IDLE/RRC_INACTIVE as specified in TS 38.331 [9]. | + +## 5.12 NCR features + +### Definitions for feature + +### Basic NCR support + +It is optional for UE to support the NCR-MT feature as specified in TS 38.2xx [x]. An NCR node for which the NCR-MT includes *ncr-NodeIndication* in *RRCSsetupComplete* as specified in TS 38.331 [9] must support these feature components. + +- Support of fixed beam for C-link/backhaul link +- Support of TDMeD UL transmission of C-link and backhaul link +- Support of ON-OFF operation for NCR-Fwd based on access link beam indication +- Support of TDD UL/DL determination for backhaul/access link based on TDD UL/DL configuration of C-link +- Support of Tx/Rx timing determination for backhaul/access link based on Tx/Rx timing of C-link +- Support of beam correspondence of the DL/UL of the access link at NCR-Fwd +- Support periodic beam indication for access link +- Priority flag for periodic indication +- Support of simultaneous and TDMeD DL reception of C-link and backhaul link + +# 6 Conditionally mandatory features without UE radio access capability parameters + +| Features | Condition | +|-----------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Acquisition of SI messages with explicit SI window positions | It is mandatory to support acquisition of SI messages with explicit SI window positions for UEs which support the SIB types in schedulingInfoList2 as specified in TS 38.331 [9]. | +| AS layer memory size for QoE paused measurement reports | It is mandatory to support the minimum AS layer memory size of 64KB for QoE paused measurement reports for UEs which support qoe-Streaming-MeasReport-r17 , qoe-MTSI-MeasReport-r17 or qoe-VR-MeasReport-r17 . | +| AS layer memory size for QoE measurement reports in RRC_IDLE and RRC_INACTIVE | For non-RedCap UE, it is mandatory to support the minimum AS layer memory size of 64KB for QoE measurement reports stored in RRC_IDLE/RRC_INACTIVE for UEs which support qoe-IdleInactiveMeasReport-r18 and any of qoe-Streaming-MeasReport-r17 or qoe-MTSI-MeasReport-r17 or qoe-VR-MeasReport-r17 . This memory size is additional to "AS layer memory size for QoE paused measurement reports" | +| ATG specific P-max | It is mandatory to support the ATG specific P-max configured by network for UEs supporting airToGroundNetwork-r18 . | +| Downlink SDAP header | Either NAS reflective QoS or as-ReflectiveQoS is supported. | +| Extended values for drx-HARQ-RTT-TimerDL/UL | It is mandatory for UEs which support FR2-2 bands with SCS 480kHz and/or 960kHz. | +| IMS emergency call |

It is mandatory to support IMS emergency call over PLMN for UEs which are IMS voice capable in NR.

It is mandatory to support IMS emergency call over SNPN for UEs that are SNPN capable and IMS voice capable over SNPNs.

| +| Logged measurements suspension due to IDC interference | It is mandatory to support Logged measurements suspension due to IDC interference for UEs which are supporting logged measurements in RRC_IDLE and RRC_INACTIVE upon request from the network and in-device coexistence indication as specified in TS 38.331 [9]. | +| MAC subheaders with one-octet eLCID field | It is mandatory to support MAC subheaders with one-octet eLCID field for UEs/IAB-MTs supporting MAC CEs using extended LCID values as specified in TS 38.321 [8]. | +| Paging cause in RAN paging message | It is mandatory for a UE to support paging cause in RAN paging if UE supports paging cause in CN paging. | +| SON report in PNI-NPN | It is mandatory for a UE to support a SON report in PNI-NPN if UE supports PNI-NPN and supports the SON report in PLMN. | +| Skipping UL configured grant if no data to transmit, as specified in release-15 version of TS 38.321 [8]. | Either configuredUL-GrantType1 or configuredUL-GrantType1-v1650 or configuredUL-GrantType2 or configuredUL-GrantType2-v1650 is supported. | +| TA reporting during initial access | It is mandatory to support TA reporting during initial access for UEs supporting uplink-TA-Reporting-r17 as specified in TS 38.321 [8]. | + +# 7 Void + +# 8 UE Capability Constraints + +The following table lists constraints indicating the UE capabilities that the UE shall support. + +| Parameter | Description | Value | +|---------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------| +| #DRBs | The number of DRBs that a UE shall support. | 8 per UE, for (e)RedCap UEs.
16 per UE, otherwise.
NOTE 1
NOTE 3
NOTE 4 | +| #minCellperMeasObjectNR | The minimum number of neighbour cells (excluding exclude-list cells) that a UE shall be able to store associated with a MeasObjectNR. | 32
NOTE 2 | +| #minExcludedCellRangesperMeasObjectNR | The minimum number of exclude-list cell PCI ranges that a UE shall be able to store associated with a MeasObjectNR. | 8 | +| #minExcludedCellperMeasObjectEUTRA | The minimum number of exclude-list cells that a UE shall be able to store associated with a MeasObjectEUTRA. | 32 | +| #minCellperMeasObjectEUTRA | The minimum number of neighbour cells that a UE shall be able to store associated with a MeasObjectEUTRA. | 32
NOTE 2 | +| #minCellTotal | The minimum number of neighbour cells (excluding exclude-list cells) that UE shall be able to store in total from all measurement objects configured. | 256 with counting CSI-RS and SSB as 2. | +| #maxDeprioritisationFreq | The UE shall be able to store a deprioritisation request for up to 8 frequencies (applicable when receiving another frequency specific deprioritisation request via RRRelease before T325 expiry). | 8 | +| #minCellperMeasObjectUTRA-FDD | The minimum number of neighbour cells that a UE shall be able to store associated with a MeasObjectUTRA-FDD. | 32 | + +NOTE 1: For one MAC entity, the maximum number of DRBs configured with PDCP duplication and with RLC entity(ies) associated with this MAC entity is 8. + +NOTE 2: In case of CGI reporting, the limit regarding the cells configured includes the cell for which the UE is requested to report CGI i.e. the amount of neighbour cells that can be included is at most (# minCellperMeasObjectRAT - 1), where RAT represents NR and EUTRA. + +NOTE 3: This requirement is applicable in NR SA, NR-DC and NE-DC. + +NOTE 4: The value of parameter #DRBs defines the total number of multicast MRBs and DRBs, and each multicast MRB associated with two RLC entities is counted as two RBs. + +# Annex A (normative): Differentiation of capabilities + +## A.1: TDD/FDD differentiation of capabilities in TDD-FDD CA + +Annex A.1 specifies for which TDD and FDD serving cells a UE supporting TDD/FDD CA shall support a feature/capability for which it indicates support within the capability signalling. + +A UE that indicates support for TDD/FDD CA (e.g. MCG or SCG): + +- For the fields for which the UE is allowed to indicate different support for FDD and TDD, the UE shall support the feature on the PCell and/or SCell(s), as specified in tables A.1-1 in accordance to the following rules: + - PCell: the UE shall support the feature for the PCell, if the UE indicates support of the feature for the PCell duplex mode; + - PSCell: the UE shall support the feature for the PSCell, if the UE indicates support of the feature for the PSCell duplex mode; + - Per serving cell: the UE shall support the feature for a serving cell if the UE indicates support of the feature for the serving cell's duplex mode; + - All serving cells: UE shall support the feature for all serving cells in a CG if the UE indicates support of the feature for both TDD and FDD duplex modes; + - Associated serving cells: UE shall support the feature if the UE indicates support of the feature for all associated serving cells's duplex modes; +- For the fields where the UE is not allowed to indicate different support for FDD and TDD, the UE shall support the feature for PCell and SCell(s) if the UE indicates support of the feature via the common capability bit. + +**Table A.1-1: UE capabilities for which FDD/TDD differentiation is allowed** + +| UE-NR-Capability or
UE-MRDC-Capability | Classification | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------| +| eventA-MeasAndReport | PSCell | +| dl-SchedulingOffset-PDSCH-TypeA (Note3) | Associated serving cells | +| dl-SchedulingOffset-PDSCH-TypeB (Note3) | Associated serving cells | +| dynamicSFI (Note3) | Associated serving cells | +| handoverInterF | PCell | +| handoverLTE-EPC | PCell | +| handoverLTE-5GC | PCell | +| intraAndInterF-MeasAndReport | PSCell | +| logicalChannelSR-DelayTimer(Note2) | Associated serving cells | +| longDRX-Cycle | All serving cells | +| multipleConfiguredGrants(Note1) | Associated serving cells | +| multipleSR-Configurations | Per serving cell | +| secondaryDRX-Group-r16 | All serving cells | +| sftd-MeasNR-Cell | PCell | +| sftd-MeasNR-Neigh | PCell | +| sftd-MeasNR-Neigh-DRX | PCell | +| sftd-MeasPSCell | PCell | +| sftd-MeasPSCell-NEDC | PCell | +| shortDRX-Cycle | All serving cells | +| skipUplinkTxDynamic | Per serving cell | +| twoDifferentTPC-Loop-PUCCH (Note3) | Associated serving cells | +| twoDifferentTPC-Loop-PUSCH (Note3) | Associated serving cells | +| ul-SchedulingOffset (Note3) | Associated serving cells | +| NOTE 1: The associated serving cells including the serving cell(s) configured with configured grant. | | +| NOTE 2: For a given logical channel, the associated serving cells including the PUCCH cell(s) associated with this logical channel (via schedulingRequestID ). | | +| NOTE 3: The associated serving cells including both the cell sending the command and the cell applying the command. | | + +## A.2: FR1/FR2 differentiation of capabilities in FR1-FR2 CA + +Annex A.2 specifies for which FR1 and FR2 serving cells a UE supporting FR1/FR2 CA shall support a feature/capability for which it indicates support within the capability signalling. + +A UE that indicates support for FR1/FR2 CA (e.g. MCG or SCG): + +- For the fields for which the UE is allowed to indicate different support for FR1 and FR2, the UE shall support the feature on the PCell and/or SCell(s), as specified in tables A.2-1 in accordance to the following rules: + - PCell: the UE shall support the feature for the PCell, if the UE indicates support of the feature for the PCell FR mode; + - Associated serving cells: UE shall support the feature if the UE indicates support of the feature for associated serving cells's FR modes; +- For the fields where the UE is not allowed to indicate different support for FR1 and FR2, the UE shall support the feature for PCell and SCell(s) if the UE indicates support of the feature via the common capability bit. + +**Table A.2-1: UE capabilities for which FR1/FR2 differentiation is allowed** + +| UE-NR-Capability | Classification | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------| +| absoluteTPC-Command (Note2) | Associated serving cells | +| dl-SchedulingOffset-PDSCH-TypeA (Note2) | Associated serving cells | +| dl-SchedulingOffset-PDSCH-TypeB (Note2) | Associated serving cells | +| drx-Adaptation-r16 | PCell | +| dynamicSFI (Note2) | Associated serving cells | +| handoverInterF | PCell | +| handoverLTE-EPC | PCell | +| handoverLTE-5GC | PCell | +| tpc-PUCCH-RNTI (Note2) | Associated serving cells | +| tpc-PUSCH-RNTI (Note2) | Associated serving cells | +| tpc-SRS-RNTI (Note2) | Associated serving cells | +| twoDifferentTPC-Loop-PUCCH (Note2) | Associated serving cells | +| twoDifferentTPC-Loop-PUSCH (Note2) | Associated serving cells | +| ul-SchedulingOffset (Note2) | Associated serving cells | +| voiceOverNR (Note1) | Associated serving cells. | +| NOTE 1: For a UE that does not support Ich-ToSCellRestriction capability, the associated serving cells includes all serving cells in the CG; for a UE that supports Ich-ToSCellRestriction capability, the associated serving cells includes the serving cells indicated by allowedServingCells for the LCH. | | +| NOTE 2: The associated serving cells including both the cell sending the command and the cell applying the command. | | + +## A.3: TDD/FDD differentiation of capabilities for sidelink + +Annex A.3 specifies for which TDD and FDD serving cells for Uu interface and carrier for PC5 interface a UE supporting sidelink shall support a feature/capability for which it indicates support within the capability signalling. + +A UE that indicates support for sidelink: + +- For the fields for which the UE is allowed to indicate different support for FDD and TDD, the UE shall support the feature on the PCell and/or SCell(s) for Uu interface, as specified in tables A.3-1 in accordance to the following rules: + - Per serving cell: the UE shall support the feature for a serving cell if the UE indicates support of the feature for the serving cell's duplex mode; + - Associated serving cells: UE shall support the feature if the UE indicates support of the feature for all associated serving cells's duplex modes; +- For the fields where the UE is not allowed to indicate different support for FDD and TDD, the UE shall support the feature for PCell and SCell(s) for Uu interface and carrier for PC5 interface if the UE indicates support of the feature via the common capability bit. + +**Table A.3-1: Rel-16 UE capabilities for which FDD/TDD differentiation is allowed** + +| Sidelink Parameter | Classification | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------| +| logicalChannelSR-DelayTimerSidelink(Note1) | Associated serving cells | +| multipleSR-ConfigurationsSidelink | Per serving cell | +| NOTE 1: For a given logical channel, the associated serving cells including the PUCCH cell(s) associated with this logical channel (via schedulingRequestID ). | | + +## A.4: Sidelink capabilities applicable to Uu and PC5 + +Annex A.4 specifies for each sidelink related capability, in which interface (i.e., *UECapabilityInformation* in Uu RRC and *UECapabilityInformationSidelink* in PC5 RRC) a UE supporting sidelink shall report the concerned capability: + +- *UECapabilityInformation*: the concerned sidelink capability is reported within *UECapabilityInformation*; +- *UECapabilityInformationSidelink*: the concerned sidelink capability is reported within *UECapabilityInformationSidelink*; + +**Table A.4-1: Sidelink capability reported in *UECapabilityInformation/UECapabilityInformationSidelink*** + +| Sidelink Parameter | UECapabilityInformation | UECapabilityInformationSidelink | +|----------------------------------------------|---------------------------------------|-----------------------------------------------| +| accessStratumReleaseSidelink | | X | +| outOfOrderDeliverySidelink | | X | +| am-WithLongSN-Sidelink | X | X | +| um-WithLongSN-Sidelink | X | X | +| lcp-RestrictionSidelink | X | | +| logicalChannelSR-DelayTimerSidelink | X | | +| multipleSR-ConfigurationsSidelink | X | | +| multipleConfiguredGrantsSidelink | X | | +| supportedBandCombinationListSidelinkEUTRA-NR | X | | +| supportedBandCombinationListSidelinkNR | | X | +| gnb-ScheduledMode3SidelinkEUTRA | X | | +| gnb-ScheduledMode4SidelinkEUTRA | X | | +| sl-Reception | X | X | +| sl-TransmissionMode1 | X | | +| sl-TransmissionMode2 | X | | +| sl-TransmissionMode2-PartialSensing | X | | +| sl-TransmissionMode2-RandomResourceSelection | X | | +| sync-Sidelink | X | | +| congestionControlSidelink | X | | +| sl-Tx-256QAM | X | X | +| sl-Rx-256QAM | X | X | +| psfch-FormatZeroSidelink | X | | +| lowSE-64QAM-MCS-TableSidelink | X | X | +| csi-ReportSidelink | | X | +| enb-sync-Sidelink | X | | +| rankTwoReception | | X | +| fewerSymbolSlotSidelink | X | | +| sl-openLoopPC-RSRP-ReportSidelink | X | X | +| rx-IUC-Scheme1-PreferredMode2Sidelink | X | X | +| rx-IUC-Scheme1-NonPreferredMode2Sidelink | X | X | +| rx-IUC-Scheme2-Mode2Sidelink | X | X | +| rx-IUC-Scheme1-SCI | X | X | +| tx-Sidelink | X | | +| rx-Sidelink | X | | +| ue-PowerClassSidelink | X | | +| drx-OnSidelink | X | X | +| enhancedUuDRX-forSidelink | X | | +| relayUE-Operation-L2 | X | | +| remoteUE-Operation-L2 | X | | +| remoteUE-PathSwitchToIdleInactive Relay | X | | + +| | | | +|----------------------------------------------------|---|---| +| supportedBandCombinationListSL-RelayDiscovery | X | | +| supportedBandCombinationListSL-NonRelayDiscovery | X | | +| rx-IUC-Scheme1-SCI-ExplicitReq | X | X | +| scheme2-ConflictDeterminationRS RP | | X | +| tx-IUC-Scheme2-Mode2Sidelink | X | X | +| tx-IUC-Scheme1-Mode2Sidelink | X | X | +| rx-sidelinkPSFCH | X | | +| p0-OLPC-Sidelink | X | | +| sl-LBT-FailureDetectionRecovery | X | | +| pdcp-DuplicationSRB-sidelink | X | X | +| pdcp-DuplicationDRB-sidelink | X | X | +| supportedBandCombinationListSL-U2U-RelayDiscovery | X | | +| relayUE-U2U-Operation-L2 | X | | +| remoteUE-U2U-Operation-L2 | X | | +| remoteUE-U2N-PathSwitchOperation-L2 | X | | +| multipathRemoteUE-PC5-L2 | X | | +| multipathRelayUE-N3C | X | | +| multipathRemoteUE-N3C | X | | +| remoteUE-IndirectPathAddChangeT oldleInactiveRelay | X | | +| pdcp-DuplicationMoreThanOneUuRLC | X | | +| sl-ReceptionIntraCarrierGuardBand | X | X | + +## A.5: General differentiation of capabilities in Cross-Carrier operation + +Annex A.5 specifies for which multiple serving cells a UE supporting cross-carrier operation shall support a feature/capability for which it indicates support within the capability signalling. + +A UE that indicates support for cross-carrier operation in CA (e.g. MCG or SCG): + +- For the fields for which the UE is allowed to indicate different support for different bands, the UE shall support the feature on the PCell and/or SCell(s) in cross-carrier operation, as specified in table A.5-1 in accordance to the following rules: + - Triggered serving cell: the UE shall support the feature if the UE indicates support of the feature for the band of the scheduled/triggered/indicated serving cell; + +- Triggering&Triggered serving cells: UE shall support the feature if the UE indicates support of the feature for the band of both the scheduling/triggering/indicating serving cell and the scheduled/triggered/indicated serving cell; + +**Table A.5-1: General UE capabilities for which differentiation is allowed** + +| UE-NR-Capability | Classification | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------| +| activeConfiguredGrant-r16 | Triggered serving cell | +| aperiodicTRS | Triggered serving cell | +| beamSwitchTiming, beamSwitchTiming-r16 | Triggered serving cell | +| bwp-DiffNumerology (NOTE 1) | Triggering&Triggered serving cells | +| bwp-SameNumerology (NOTE 1) | Triggering&Triggered serving cells | +| crossCarrierScheduling-SameSCS | Triggering&Triggered serving cells | +| crossCarrierSchedulingProcessing-DiffSCS-r16 (NOTE 2) | Triggering&Triggered serving cells | +| dynamicSFI-r16 | Triggering&Triggered serving cells | +| jointReleaseConfiguredGrantType2-r16 | Triggered serving cell | +| jointReleaseSPS-r16 | Triggered serving cell | +| multiPUSCH-ActiveConfiguredGrant-r18 | Triggered serving cell | +| pdcch-MonitoringAnyOccasionsWithSpanGap (NOTE 3) | Triggering&Triggered serving cells | +| sps-r16 | Triggered serving cell | +| ue-SpecificUL-DL-Assignment | Triggering&Triggered serving cells | +| ul-CancellationCrossCarrier-r16 | Triggering&Triggered serving cells | +| NOTE 1: For bwp-DiffNumerology and bwp-SameNumerology , the supported number of BWPs for each band is still based on the indicated number for this band regardless of whether it is a scheduling cell or scheduled cell. | | +| NOTE 2: For crossCarrierSchedulingProcessing-DiffSCS-r16 , if reported value is different between the band of the scheduled/triggered/indicated cell and the band of the scheduling/triggering/indicating cell, the value reported for the scheduling/triggering/indicating cell is applied. | | +| NOTE 3: Applicable for cross carrier scheduling with the same SCS in the scheduling cell and the scheduled cell. If the reported value is different between the band of the scheduled/triggered/indicated cell and the band of the scheduling/triggering/indicating cell, the value reported for the scheduling/triggering/indicating cell is applied. | | + +# --- Annex B (informative): + +# UE capability indication for UE capabilities with both FDD/TDD and FR1/FR2 differentiations + +Annex B clarifies the UE capability indication for the case where the UE is allowed to support different functionality between FDD and TDD, and between FR1 and FR2. Table B-1 clarifies the setting of UE capability fields for cases where the UE supports the corresponding feature in different combinations of duplex mode and frequency range. There are two possible ways of UE capability indication in Case 3 and Case 8. + +**Table B-1: UE capability indication for UE capabilities with both FDD/TDD and FR1/FR2 differentiations** + +| Support for the feature | | Setting of UE capability fields | | | | | | +|-------------------------|----------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|------------------------------------------------|---------------------------------|---------------------------------|---------------------------------|---------------------------------| +| | | Common UE capability (with suffix '-XDD-Diff') | Common UE capability (with suffix '-FRX-diff') | fdd-Add-UE-NR/MRDC-Capabilities | tdd-Add-UE-NR/MRDC-Capabilities | fr1-Add-UE-NR/MRDC-Capabilities | fr2-Add-UE-NR/MRDC-Capabilities | +| Case 1 | FR1 FDD: 'supported'
FR1 TDD: 'supported'
FR2 TDD: 'supported' | Included | Included | Not included | Not included | Not included | Not included | +| Case 2 | FR1 FDD: 'not supported'
FR1 TDD: 'not supported'
FR2 TDD: 'not supported' | Not included | Not included | Not included | Not included | Not included | Not included | +| Case 3 | FR1 FDD: 'not supported'
FR1 TDD: 'supported'
FR2 TDD: 'supported' | Not included | Included | Not included | Included | Not included | Not included | +| | | Not included | Not included | Not included | Included | Not included | Not included | +| Case 4 | FR1 FDD: 'not supported'
FR1 TDD: 'not supported'
FR2 TDD: 'supported' | Not included | Not included | Not included | Included | Not included | Included | +| Case 5 | FR1 FDD: 'not supported'
FR1 TDD: 'supported'
FR2 TDD: 'not supported' | Not included | Not included | Not included | Included | Included | Not included | +| Case 6 | FR1 FDD: 'supported'
FR1 TDD: 'not supported'
FR2 TDD: 'supported' | The current UE capability signalling does not support the UE capability indication for this case. | | | | | | +| Case 7 | FR1 FDD: 'supported'
FR1 TDD: 'not supported'
FR2 TDD: 'not supported' | Not included | Not included | Included | Not included | Included | Not included | +| Case 8 | FR1 FDD: 'supported'
FR1 TDD: 'supported'
FR2 TDD: 'not supported' | Included | Not included | Not included | Not included | Included | Not included | +| | | Not included | Not included | Not included | Not included | Included | Not included | + +NOTE 1: For a UE capability which cannot be differentiated between FR2-1 and FR2-2, 'FR2 TDD' in Table B-1 includes both 'FR2-1 TDD' and 'FR2-2 TDD'. + +NOTE 2: For a UE capability which can be differentiated between FR2-1 and FR2-2, 'FR2 TDD' in Table B-1 only means 'FR2-1 TDD'. + +# --- Annex C (informative): Change history + +| Change history | | | | | | | | +|----------------|----------|------------|------|-----|-----|-------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 06/2017 | RAN2#98 | R2-1704810 | | | | First version | 0.0.1 | +| 06/2017 | RAN2#NR2 | R2-1707386 | | | | | 0.0.2 | +| 08/2017 | RAN2#99 | R2-1708750 | | | | | 0.0.3 | +| 12/2017 | RAN2#100 | R2-1712587 | | | | | 0.0.4 | +| 12/2017 | RAN2#100 | R2-1714141 | | | | | 0.0.5 | +| 12/2017 | RAN2#100 | R2-1714271 | | | | | 0.1.0 | +| 12/2017 | RP-78 | RP-172521 | | | | Submitted to RAN#78 for approval | 1.0.0 | +| 12/2017 | RP-78 | | | | | Upgraded to Rel-15 | 15.0.0 | +| 03/2018 | RP-79 | RP-180440 | 0003 | 3 | F | Updates on UE capabilities | 15.1.0 | +| 06/2018 | RP-80 | RP-181216 | 0009 | 2 | B | Introduce ANR in NR | 15.2.0 | +| | RP-80 | RP-181216 | 0012 | 1 | F | Miscellaneous corrections | 15.2.0 | +| | RP-80 | RP-181216 | 0013 | - | B | Delay budget report and MAC CE adaptation for NR for TS 38.306 | 15.2.0 | +| 09/2018 | RP-81 | RP-181940 | 0008 | 4 | F | Correction on total layer2 buffer size | 15.3.0 | +| | RP-81 | RP-181942 | 0024 | 1 | F | Introduction of UE capability constraints | 15.3.0 | +| | RP-81 | RP-181942 | 0030 | - | F | 38.306 corrections and cleanup | 15.3.0 | +| 12/2018 | RP-82 | RP-182651 | 0016 | 4 | F | Clarification for Interruption-based and gap-based SFTD measurement | 15.4.0 | +| | RP-82 | RP-182653 | 0033 | 1 | F | Timer based BWP switching | 15.4.0 | +| | RP-82 | RP-182652 | 0035 | 2 | F | Additional UE capabilities for NR standalone | 15.4.0 | +| | RP-82 | RP-182651 | 0037 | 1 | F | Clarification to UE capability of independentGapConfig for inter-RAT NR measurement not yet configured with EN-DC | 15.4.0 | +| | RP-82 | RP-182661 | 0038 | 2 | F | Update of L2 capability parameters | 15.4.0 | +| | RP-82 | RP-182660 | 0047 | 2 | F | Clarification on physical layer parameters of UE capability | 15.4.0 | +| | RP-82 | RP-182666 | 0050 | 3 | F | Introduce RRC buffer size in NR | 15.4.0 | +| | RP-82 | RP-182664 | 0051 | 2 | F | Clarification of multipleConfiguredGrants | 15.4.0 | +| | RP-82 | RP-182664 | 0052 | 2 | F | CR to 38.306 for PDCP CA duplication for SRB | 15.4.0 | +| | RP-82 | RP-182661 | 0054 | 1 | F | UE capability handling for FDD/TDD and FR1/FR2 | 15.4.0 | +| | RP-82 | RP-182663 | 0057 | 1 | F | Clarify for per CC UL/DL modulation order capabilities | 15.4.0 | +| | RP-82 | RP-182664 | 0058 | 1 | F | Inter-frequency handover capability | 15.4.0 | +| | RP-82 | RP-182665 | 0060 | 3 | F | UE capability on PA architecture | 15.4.0 | +| | RP-82 | RP-182661 | 0062 | 1 | F | CR on signaling contiguous and non-contiguous EN-DC capability | 15.4.0 | +| | RP-82 | RP-182813 | 0063 | 6 | F | Update of UE capabilities | 15.4.0 | +| | RP-82 | RP-182662 | 0065 | 2 | F | Introduction of SRS switching capability | 15.4.0 | +| | RP-82 | RP-182667 | 0068 | 2 | B | CR on introduction of UE overheating support in NR SA scenario | 15.4.0 | +| | RP-82 | RP-182664 | 0071 | - | F | Introduction of SRS switching capability | 15.4.0 | +| 03/2019 | RP-83 | RP-190634 | 0073 | 1 | F | Capability for aperiodic CSI-RS triggering with different numerology between PDCCH and CSI-RS | 15.5.0 | +| | RP-83 | RP-190542 | 0074 | 1 | F | Layer-1 capability update | 15.5.0 | +| | RP-83 | RP-190545 | 0075 | 2 | F | CR to 38.306 on introducing nr-CGI-Reporting-ENDC | 15.5.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|---------------------------------------------------------------------------------------------------------------|--------| +| | RP-83 | RP-190545 | 0086 | 2 | F | CR to clarify intra-NR handover capabilities | 15.5.0 | +| | RP-83 | RP-190546 | 0088 | 3 | F | Clarification for PDSCHs and PUSCHs per slot for different TBs for UE capable of processing time capability 1 | 15.5.0 | +| | RP-83 | RP-190542 | 0092 | 2 | F | Correction to mandatory supported capability signaling | 15.5.0 | +| | RP-83 | RP-190542 | 0097 | 2 | F | Miscellaneous corrections | 15.5.0 | +| | RP-83 | RP-190545 | 0098 | 2 | F | Correction on supportedBandwidthCombinationSetEUTRA-v1530 usage | 15.5.0 | +| | RP-83 | RP-190543 | 0099 | - | F | Clarification on signaling the bandwidth class | 15.5.0 | +| | RP-83 | RP-190545 | 0100 | 1 | F | Clarification on Frequency Separation Class | 15.5.0 | +| | RP-83 | RP-190544 | 0101 | - | F | CR on Processing delay requirements for RRC Resume procedures in TS 38.306 | 15.5.0 | +| 06/2019 | RP-84 | RP-191375 | 0094 | 1 | F | CR to clarify ul-TimingAlignmentEUTRA-NR | 15.6.0 | +| | RP-84 | RP-191373 | 0108 | - | F | Layer-1, RF and RRM capability updates | 15.6.0 | +| | RP-84 | RP-191373 | 0109 | - | F | Clarification on UE capability of Ich-ToSCellRestriction | 15.6.0 | +| | RP-84 | RP-191379 | 0110 | 2 | F | Correction on description of additionalActiveSpatialRelationPUCCH | 15.6.0 | +| | RP-84 | RP-191378 | 0111 | 1 | F | Clarification on csi-RS-CFRA-ForHO | 15.6.0 | +| | RP-84 | RP-191379 | 0114 | 2 | F | CR on capability of maxUplinkDutyCycle for FR2 | 15.6.0 | +| | RP-84 | RP-191380 | 0115 | 2 | F | 38.306 miscellaneous corrections | 15.6.0 | +| | RP-84 | RP-191378 | 0116 | 1 | B | 38.306 CR for late drop | 15.6.0 | +| | RP-84 | RP-191381 | 0118 | 4 | F | Clarification on supported modulation order capability | 15.6.0 | +| | RP-84 | RP-191374 | 0119 | - | F | Correction to PDCP parameters | 15.6.0 | +| | RP-84 | RP-191381 | 0121 | 3 | F | Corrections to UE Capability definitions | 15.6.0 | +| | RP-84 | RP-191378 | 0122 | 1 | F | 38.306 Clarification on multiple TA capabilities | 15.6.0 | +| | RP-84 | RP-191379 | 0123 | 2 | F | CR to clarify non-codebook based PUSCH transmission | 15.6.0 | +| | RP-84 | RP-191380 | 0124 | 3 | F | Clarification on pdsch-ProcessingType2 | 15.6.0 | +| | RP-84 | RP-191378 | 0125 | 1 | F | Clarification on present of tci-StatePDSCH | 15.6.0 | +| | RP-84 | RP-191378 | 0126 | 1 | F | Clarification on SA fallback BC support | 15.6.0 | +| | RP-84 | RP-191375 | 0128 | - | F | Correction to Beam Correspondence for CA | 15.6.0 | +| | RP-84 | RP-191379 | 0130 | 2 | F | Correction on the number of DRB in UE Capability Constraints | 15.6.0 | +| | RP-84 | RP-191379 | 0132 | 1 | F | CR to capture UE supported DL/UL bandwidths | 15.6.0 | +| | RP-84 | RP-191376 | 0133 | - | F | UE capability signalling for FD-MIMO processing capabilities for EN-DC | 15.6.0 | +| | RP-84 | RP-191376 | 0134 | - | F | Modified UE capability on different numerologies within the same PUCCH group | 15.6.0 | +| | RP-84 | RP-191554 | 0135 | - | F | Removal of "Capability for aperiodic CSI-RS triggering with different numerology between PDCCH and CSI-RS" | 15.6.0 | +| 09/2019 | RP-85 | RP-192196 | 0136 | 1 | C | Additional capability signalling for 1024QAM support | 15.7.0 | +| | RP-85 | RP-192191 | 0142 | 1 | B | Introduction of SFTD measurement to neighbour cells for NR SA | 15.7.0 | +| | RP-85 | RP-192193 | 0146 | 1 | F | MR-DC measurement gap pattern capability | 15.7.0 | +| | RP-85 | RP-192194 | 0151 | 3 | F | Clarifying UE capability freqHoppingPUCCH-F0-2 and freqHoppingPUCCH-F1-3-4 | 15.7.0 | +| | RP-85 | RP-192190 | 0152 | - | F | Clarification to dynamic power sharing capability | 15.7.0 | +| | RP-85 | RP-192192 | 0153 | 2 | F | Miscellaneous corrections | 15.7.0 | +| | RP-85 | RP-192190 | 0154 | - | F | Capability of measurement gap patterns | 15.7.0 | +| | RP-85 | RP-192193 | 0155 | 2 | F | Correction to IMS capability | 15.7.0 | +| | RP-85 | RP-192194 | 0156 | 3 | F | UE Capabilities covering across all serving cells | 15.7.0 | +| | RP-85 | RP-192190 | 0167 | - | F | Clarification on UE capability on different numerologies within the | 15.7.0 | + +| | | | | | | | | +|--|--|--|--|--|--|------------------|--| +| | | | | | | same PUCCH group | | +|--|--|--|--|--|--|------------------|--| + +| | | | | | | | | +|---------|-------|-----------|------|---|---|---------------------------------------------------------------------------------------------------------|--------| +| | RP-85 | RP-192193 | 0168 | 1 | F | Correction on CA parameters in NR-DC | 15.7.0 | +| | RP-85 | RP-192346 | 0169 | - | C | Introduction of UE capability for NR-DC with SFN synchronization between PCell and PSCell | 15.7.0 | +| 12/2019 | RP-86 | RP-192934 | 0185 | 1 | F | Clarification on the restriction of maximum SRS resource sets configuration for uplink beam management. | 15.8.0 | +| | RP-86 | RP-192936 | 0186 | 3 | F | Miscellaneous corrections on UE capability fields | 15.8.0 | +| | RP-86 | RP-192935 | 0191 | 1 | F | Corrections on PDCCH blind decoding in NR-DC | 15.8.0 | +| | RP-86 | RP-192937 | 0200 | 1 | F | Clarification on ne-DC capability | 15.8.0 | +| | RP-86 | RP-192935 | 0202 | 1 | F | Correction to channelBWs | 15.8.0 | +| | RP-86 | RP-192936 | 0204 | 1 | F | Use of splitSRB-WithOneUL-Path capability (38.306) | 15.8.0 | +| | RP-86 | RP-192935 | 0205 | - | F | Correction to pdsch-RepetitionMultiSlots and pusch-RepetitionMultiSlots | 15.8.0 | +| | RP-86 | RP-192937 | 0215 | 1 | F | Correction on initial BWP bandwidth capabilities | 15.8.0 | +| | RP-86 | RP-192937 | 0216 | 1 | F | NE-DC dynamic power sharing capability | 15.8.0 | +| | RP-86 | RP-192935 | 0219 | - | F | Clarification on crossCarrierScheduling-OtherSCS in R15 | 15.8.0 | +| | RP-86 | RP-192937 | 0220 | - | F | Correction on ambiguity of UE FDD/TDD FR1/FR2 capabilities | 15.8.0 | +| 03/2020 | RP-87 | RP-200334 | 0194 | 2 | F | Correction on parameter description of beamManagementSSB-CSI-RS | 15.9.0 | +| | RP-87 | RP-200335 | 0208 | 3 | F | CR on BWCS for inter-ENDC BC with intra-ENDC BC (38.306) | 15.9.0 | +| | RP-87 | RP-200335 | 0209 | 5 | F | CR to 38.306 on support of 70MHz channel bandwidth | 15.9.0 | +| | RP-87 | RP-200334 | 0236 | - | F | Correction on SRB capability in NR-DC | 15.9.0 | +| | RP-87 | RP-200335 | 0248 | 2 | F | Data rate for the case of single carrier standalone operation | 15.9.0 | +| | RP-87 | RP-200334 | 0254 | 1 | F | CR on the maximum stored number of deprioritisation frequencies | 15.9.0 | +| | RP-87 | RP-200335 | 0255 | 2 | F | Miscellaneous Corrections to UE capability parameters | 15.9.0 | +| | RP-87 | RP-200335 | 0259 | 1 | F | UE capability of intra-band requirements for inter-band EN-DC/NE-DC | 15.9.0 | +| 03/2020 | RP-87 | RP-200356 | 0145 | 1 | F | CR on capability of maxUplinkDutyCycle for inter-band EN-DC PC2 UE | 16.0.0 | +| | RP-87 | RP-200335 | 0214 | 2 | F | Correction on beamSwitchTiming values of 224 and 336 | 16.0.0 | +| | RP-87 | RP-200335 | 0223 | 1 | C | Inclusion of 90MHz UE Bandwidth | 16.0.0 | +| | RP-87 | RP-200358 | 0226 | 2 | B | Introducing autonomous gap in CGI reporting | 16.0.0 | +| | RP-87 | RP-200357 | 0229 | - | B | UE capability for IDC | 16.0.0 | +| | RP-87 | RP-200340 | 0230 | - | B | Introduction of Cross Link Interference (CLI) handling and Remote Interference Management (RIM) | 16.0.0 | +| | RP-87 | RP-200358 | 0233 | 1 | C | Introduction of EPS voice fallback enhancement | 16.0.0 | +| | RP-87 | RP-200350 | 0235 | - | B | Introduction of SRVCC from 5G to 3G | 16.0.0 | +| | RP-87 | RP-200358 | 0243 | 1 | B | Introduction of DL RRC segmentation | 16.0.0 | +| | RP-87 | RP-200358 | 0258 | 1 | B | Introduction of downgraded configuration for SRS antenna switching | 16.0.0 | +| | RP-87 | RP-200359 | 0260 | - | B | Recommended Bit Rate/Query for FLUS and MTSI | 16.0.0 | +| | RP-87 | RP-200358 | 0261 | - | B | Introduction of UE capability indicator of supporting inter-RAT handover from NR to EN-DC in 38.306. | 16.0.0 | +| 07/2020 | RP-88 | RP-201163 | 0288 | 2 | A | Correction to the serving cell number for ENDC power class | 16.1.0 | +| | RP-88 | RP-201187 | 0289 | 3 | A | CR on introduction of BCS to asymmetric channel bandwidths (38.306) | 16.1.0 | +| | RP-88 | RP-201160 | 0295 | 1 | A | SRS Capability report for SRS only Scell | 16.1.0 | +| | RP-88 | RP-201159 | 0299 | - | A | Clarification on L1 feature of NGEN-DC and NE-DC | 16.1.0 | +| | RP-88 | RP-201161 | 0304 | 2 | A | Default values for UE capability | 16.1.0 | +| | RP-88 | RP-201163 | 0312 | 1 | A | Invalidating bandwidth class F for FR1 | 16.1.0 | +| | RP-88 | RP-201163 | 0318 | 1 | A | Missing "Optional features without UE radio access capability | 16.1.0 | + +| | | | | | | | | +|--|--|--|--|--|--|-------------|--| +| | | | | | | parameters" | | +|--|--|--|--|--|--|-------------|--| + +| | | | | | | | | +|---------|-------|-----------|------|---|---|-------------------------------------------------------------------------------------------|--------| +| | RP-88 | RP-201163 | 0320 | 1 | A | Missing UE capability requirements | 16.1.0 | +| | RP-88 | RP-201198 | 0321 | 1 | C | Introduction of secondary DRX group CR 38.306 | 16.1.0 | +| | RP-88 | RP-201164 | 0324 | 2 | A | Correction on UE capability constraints | 16.1.0 | +| | RP-88 | RP-201183 | 0328 | 2 | B | UE capability of supporting UL Tx switching | 16.1.0 | +| | RP-88 | RP-201217 | 0329 | 2 | B | Release-16 UE capabilities based on RAN1, RAN4 feature lists and RAN2 | 16.1.0 | +| | RP-88 | RP-201163 | 0330 | 1 | A | Corrections on the number of DRBs | 16.1.0 | +| | RP-88 | RP-201166 | 0333 | 1 | F | On the capability of Basic CSI feedback (2-32) | 16.1.0 | +| | RP-88 | RP-201162 | 0339 | 1 | A | Clarification on the support of IMS voice over split bearer for NR-DC and NE-DC | 16.1.0 | +| | RP-88 | RP-201162 | 0343 | 1 | A | Clarification on maximum number of supported PDSCH Resource Element mapping patterns | 16.1.0 | +| | RP-88 | RP-201164 | 0344 | 2 | A | Introduction of CGI reporting capabilities | 16.1.0 | +| | RP-88 | RP-201165 | 0346 | 2 | A | UE Capability Enhancement for FR1(TDD/FDD) / FR2 CA and DC | 16.1.0 | +| | RP-88 | RP-201161 | 0353 | - | A | CR on unnecessary XDD FRX differentiation | 16.1.0 | +| | RP-88 | RP-201162 | 0355 | - | A | Clarification to maxUplinkDutyCycle-FR2 | 16.1.0 | +| | RP-88 | RP-201162 | 0357 | - | A | Clarification on L2 and RAN4 feature of NGEN-DC and NE-DC | 16.1.0 | +| | RP-88 | RP-201163 | 0360 | 1 | A | Correction on UE capability signalling for simultaneous SRS antenna and carrier switching | 16.1.0 | +| | RP-88 | RP-201163 | 0362 | - | A | Correction on UE capabilities with xDD and FRx differentiations | 16.1.0 | +| | RP-88 | RP-201166 | 0363 | - | C | Missing reportAddNeighMeas in periodic measurement reporting | 16.1.0 | +| 09/2020 | RP-89 | RP-201932 | 0370 | 2 | B | Release-16 UE capabilities based on RAN1, RAN4 feature lists and RAN2 corrections | 16.2.0 | +| | RP-89 | RP-201938 | 0378 | 1 | A | Corrections on UE capability constraints | 16.2.0 | +| | RP-89 | RP-201932 | 0382 | 1 | F | Correction on beamSwitchTiming values of 224 and 336 | 16.2.0 | +| | RP-89 | RP-201924 | 0383 | 2 | F | Update to IAB-MT capabilities | 16.2.0 | +| | RP-89 | RP-201937 | 0387 | 1 | F | Clarification on PDSCH rate-matching capabilities | 16.2.0 | +| | RP-89 | RP-201937 | 0389 | 2 | A | Corrections on the capabilities associated with multiple bands/Cells | 16.2.0 | +| | RP-89 | RP-201989 | 0393 | 2 | F | Correction on PRS measurement gap capability | 16.2.0 | +| | RP-89 | RP-201938 | 0402 | 2 | F | Clarification on the extended capability of NGEN-DC | 16.2.0 | +| | RP-89 | RP-201962 | 0407 | 1 | F | Miscellaneous corrections on UL Tx switching | 16.2.0 | +| | RP-89 | RP-201922 | 0408 | - | F | NR-DC UE capabilities | 16.2.0 | +| 12/2020 | RP-90 | RP-202790 | 0419 | 2 | A | CR to clarify UE capability in case of Cross-Carrier operation | 16.3.0 | +| | RP-90 | RP-202778 | 0422 | 1 | B | Release-16 UE capabilities based on RAN1, RAN4 feature lists and RAN2 corrections | 16.3.0 | +| | RP-90 | RP-202767 | 0424 | 3 | F | Correction on description for extendedRAR-Window | 16.3.0 | +| | RP-90 | RP-202789 | 0439 | 1 | F | Clarification on the inter-frequency handover capability | 16.3.0 | +| | RP-90 | RP-202789 | 0441 | - | A | Clarification on NE-DC for bandwidth combination set | 16.3.0 | +| | RP-90 | RP-202790 | 0453 | 1 | A | Removing contradiction on number of FSpUCC and FSpDCC | 16.3.0 | +| | RP-90 | RP-202789 | 0461 | - | F | Clarification on UE capabilities with FDD/TDD differentiation | 16.3.0 | +| | RP-90 | RP-202771 | 0472 | 4 | F | Introduction of capability bit for multi-CC simultaneous TCI activation with multi-TRP | 16.3.0 | +| | RP-90 | RP-202770 | 0476 | - | A | Dummify UE capability of crossCarrierScheduling-OtherSCS | 16.3.0 | +| | RP-90 | RP-202789 | 0479 | 1 | A | Clarification for multipleCORESET | 16.3.0 | +| | RP-90 | RP-202882 | 0481 | - | A | CR to 38.306 on handling of fallbacks for FR2 CA | 16.3.0 | +| 03/2021 | RP-91 | RP-210689 | 0482 | - | F | Update on V2X UE capability | 16.4.0 | +| | RP-91 | RP-210693 | 0483 | 1 | F | CR for the supported max date rate for uplink Tx switching | 16.4.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|----------------------------------------------------------------------------------------------|--------| +| | RP-91 | RP-210697 | 0485 | - | F | UE capability of NR to UTRA-FDD CELL_DCH CS handover | 16.4.0 | +| | RP-91 | RP-210697 | 0489 | 2 | A | Correction on beamSwitchTiming capability | 16.4.0 | +| | RP-91 | RP-210697 | 0490 | 1 | F | Correction on beamSwitchTiming-r16 capability | 16.4.0 | +| | RP-91 | RP-210697 | 0491 | 1 | F | Correction on TPMI grouping capability | 16.4.0 | +| | RP-91 | RP-210692 | 0501 | - | F | Dummifying intraFreqMultiUL-TransmissionDAPS-r16 capability | 16.4.0 | +| | RP-91 | RP-210694 | 0502 | 1 | F | Corrections on UE capability for NR-U | 16.4.0 | +| | RP-91 | RP-210703 | 0503 | 2 | F | Release with Redirect for connection resume triggered by NAS | 16.4.0 | +| | RP-91 | RP-210703 | 0505 | 2 | A | Clarification to LCP restrictions | 16.4.0 | +| | RP-91 | RP-210691 | 0506 | 1 | F | Introduction of the UE Capability for SpCell BFR Enhancement | 16.4.0 | +| | RP-91 | RP-210697 | 0509 | 2 | F | Clarification on UE capabilities with FDD/TDD differentiation | 16.4.0 | +| | RP-91 | RP-210805 | 0512 | 3 | B | Support of 35 MHz and 45 MHz channel bandwidth for FR1 | 16.4.0 | +| | RP-91 | RP-210697 | 0513 | 1 | F | Clarification on UE capabilities for enhanced MIMO | 16.4.0 | +| | RP-91 | RP-210703 | 0516 | 2 | A | CR on the SupportedBandwidth and channelBWs(R16) | 16.4.0 | +| | RP-91 | RP-210695 | 0520 | 2 | F | Correction to PUSCH skipping with UCI without LCH-based prioritization | 16.4.0 | +| | RP-91 | RP-210697 | 0521 | 1 | F | CR on the Capability of PUCCH Transmissions for HARQ-ACK-38306 | 16.4.0 | +| | RP-91 | RP-210703 | 0523 | 2 | F | Clarification on FDD-TDD differentiation for SUL band | 16.4.0 | +| | RP-91 | RP-210702 | 0525 | 1 | A | Clarification on single uplink operation capability report | 16.4.0 | +| | RP-91 | RP-210697 | 0528 | - | F | Addition of TEI16 features | 16.4.0 | +| | RP-91 | RP-210702 | 0529 | - | A | CR to clarify the definition of fallback per CC feature set | 16.4.0 | +| | RP-91 | RP-210697 | 0530 | - | F | Capability for dormant BWP switching of multiple SCells | 16.4.0 | +| | RP-91 | RP-210702 | 0533 | - | A | Dummy the capability bit v2x-EUTRA | 16.4.0 | +| | RP-91 | RP-210703 | 0534 | 2 | A | Clarification on the capability of supportedNumberTAG | 16.4.0 | +| | RP-91 | RP-210701 | 0537 | 1 | A | Clarification on the supportedBandwidthCombinationSetIntraENDC capability | 16.4.0 | +| | RP-91 | RP-210697 | 0538 | - | B | Release-16 UE capabilities based on updated RAN1 and RAN4 feature lists | 16.4.0 | +| | RP-91 | RP-210693 | 0539 | - | B | Uplink Tx DC location reporting for two carrier uplink CA | 16.4.0 | +| 06/2021 | RP-92 | RP-211487 | 0526 | 5 | C | Redirection with MPS Indication [Redirect_MPS_I] | 16.5.0 | +| | RP-92 | RP-211480 | 0541 | 4 | F | Miscellaneous corrections to Rel-16 UE capabilities | 16.5.0 | +| | RP-92 | RP-211475 | 0542 | 3 | F | Correction on Capability of two PUCCH transmission | 16.5.0 | +| | RP-92 | RP-211470 | 0543 | 3 | F | Correction on V2X UE capability | 16.5.0 | +| | RP-92 | RP-211483 | 0545 | 2 | A | CR on UE capability in case of Cross-Carrier operation | 16.5.0 | +| | RP-92 | RP-211470 | 0547 | 2 | F | Addition of total L2 buffer size and RLC RTT for NR SL | 16.5.0 | +| | RP-92 | RP-211483 | 0550 | 2 | A | Correction to BWP capabilities | 16.5.0 | +| | RP-92 | RP-211482 | 0566 | 2 | A | CR on the supportedBandwidthCombinationSet-R16 | 16.5.0 | +| | RP-92 | RP-211477 | 0568 | 3 | A | CR on the 35M45M supporting-R16 | 16.5.0 | +| | RP-92 | RP-211484 | 0571 | 2 | F | UL Config Grant capability differentiation for FR1(TDD/FDD) / FR2 | 16.5.0 | +| | RP-92 | RP-211474 | 0572 | 2 | F | Corrections on the UE capability of indication on supporting the extension of SRS resourceID | 16.5.0 | +| | RP-92 | RP-211478 | 0573 | 3 | B | Release-16 UE capabilities based on RAN1 and RAN4 feature lists | 16.5.0 | +| | RP-92 | RP-211480 | 0575 | 3 | F | Corrections to directional collision handling in half-duplex operation | 16.5.0 | +| | RP-92 | RP-211478 | 0578 | 1 | F | Introduction of the intra-NR and inter-RAT HST Capabilities | 16.5.0 | +| | RP-92 | RP-211483 | 0594 | - | A | Correction to the use of simultaneous CSI-RS resources | 16.5.0 | +| | RP-92 | RP-211478 | 0596 | 1 | A | Clarification on BCS of a fallback band combination | 16.5.0 | +| | RP-92 | RP-211478 | 0599 | 1 | A | Further clarification on supportedNumberTAG | 16.5.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|------------------------------------------------------------------------------------------------|--------| +| | RP-92 | RP-211478 | 0608 | 1 | A | Clarification on maximum number of TCI-state for PDSCH | 16.5.0 | +| | RP-92 | RP-211475 | 0609 | - | F | Capability bit for extending search space switching trigger configuration | 16.5.0 | +| | RP-92 | RP-211471 | 0610 | 1 | C | NR-DC Cell Group capability filtering | 16.5.0 | +| 09/2021 | RP-93 | RP-212439 | 0518 | 4 | A | CR on the Intra-band and Inter-band EN-DC Capabilities -R16 | 16.6.0 | +| | RP-93 | RP-212439 | 0562 | 3 | A | Clarification on the simultaneous RxTxInterBandCA capability in NR-DC | 16.6.0 | +| | RP-93 | RP-212438 | 0613 | 1 | A | Correction to the description of additionalActiveTCI-StatePDCCH | 16.6.0 | +| | RP-93 | RP-212439 | 0619 | 1 | A | Definition of fallback per CC feature set | 16.6.0 | +| | RP-93 | RP-212443 | 0626 | 1 | F | Miscellaneous corrections to UE capability descriptions | 16.6.0 | +| | RP-93 | RP-212439 | 0631 | 1 | A | Support of newly introduced 100M bandwidth for band n40 | 16.6.0 | +| | RP-93 | RP-212438 | 0633 | - | A | Correction on fallback band combination for SUL | 16.6.0 | +| | RP-93 | RP-212440 | 0641 | - | F | FR1/FR2 differentiation for enhanced UL grant skipping capabilities | 16.6.0 | +| | RP-93 | RP-212597 | 0643 | 2 | C | Distinguishing support of extended band n77 | 16.6.0 | +| 12/2021 | RP-94 | RP-213341 | 0640 | 2 | A | Simultaneous Rx/Tx UE capability per band pair | 16.7.0 | +| | RP-94 | RP-213344 | 0645 | 2 | F | Updates based on RAN1 NR positioning features list | 16.7.0 | +| | RP-94 | RP-213342 | 0646 | 1 | C | Duty cycle signalling for power class 1.5 | 16.7.0 | +| | RP-94 | RP-213343 | 0647 | 1 | F | Correction on R16 UE capability of supported SINR-meas-r16 | 16.7.0 | +| | RP-94 | RP-213341 | 0656 | 1 | A | Clarification on intraAndInterF-MeasAndReport capability | 16.7.0 | +| | RP-94 | RP-213341 | 0658 | - | A | Miscellaneous corrections for Rel-15 UE capabilities | 16.7.0 | +| | RP-94 | RP-213346 | 0659 | - | F | Miscellaneous corrections for Rel-16 UE capabilities | 16.7.0 | +| | RP-94 | RP-213345 | 0660 | 1 | C | CR on 38.306 for introducing UE capability of txDiversity | 16.7.0 | +| | RP-94 | RP-213346 | 0661 | 1 | F | Clarification on UL MIMO layer reporting for 1Tx-2Tx switching | 16.7.0 | +| | RP-94 | RP-213346 | 0664 | - | F | Correction on two HARQ-ACK codebooks capability | 16.7.0 | +| 03/2022 | RP-95 | RP-220835 | 0635 | 3 | F | Adding UE capability of UL MIMO coherence for UL Tx switching | 16.8.0 | +| | RP-95 | RP-220473 | 0677 | 1 | F | Correction on DAPS capability | 16.8.0 | +| | RP-95 | RP-220473 | 0688 | 1 | F | Introduction of sidelink power class capability indication | 16.8.0 | +| | RP-95 | RP-220473 | 0695 | 1 | F | Correction on ssb-csirs-SINR-measurement-r16 capability | 16.8.0 | +| 03/2022 | RP-95 | RP-220499 | 0532 | 2 | C | Remove the maximum number of MIMO layers restrictions for SUL | 17.0.0 | +| | RP-95 | RP-220837 | 0650 | 2 | B | Introduction of mobility-state-based cell reselection for NR HSDN [NR_HSDN] | 17.0.0 | +| | RP-95 | RP-220921 | 0667 | 2 | C | Pi/2-BPSK specification updates for the merger of 5Gi into 3GPP | 17.0.0 | +| | RP-95 | RP-220472 | 0679 | 1 | F | Correction on PO determination for UE in inactive state | 17.0.0 | +| | RP-95 | RP-220838 | 0685 | 1 | B | Release-17 UE capabilities based on R1 and R4 feature lists (TS38.306) | 17.0.0 | +| | RP-95 | RP-220506 | 0686 | 1 | D | Inclusive Language Review for TS 38.306 | 17.0.0 | +| | RP-95 | RP-220510 | 0698 | 1 | B | Capability for Explicit Indication of SI Scheduling window position [SI-SCHEDULING] | 17.0.0 | +| 06/2022 | RP-96 | RP-221721 | 0690 | 2 | B | CR on the CBM/IBM reporting-38306 | 17.1.0 | +| | RP-96 | RP-221756 | 0703 | 2 | B | Release-17 UE capabilities based on R1 and R4 feature lists (TS38.306) | 17.1.0 | +| | RP-96 | RP-221756 | 0710 | 1 | A | Clarification on simultaneous Rx/Tx capability per band pair | 17.1.0 | +| | RP-96 | RP-221736 | 0714 | 2 | C | Distinguishing support of band n77 restrictions in Canada [n77 Canada] | 17.1.0 | +| | RP-96 | RP-221756 | 0715 | 1 | F | Correction on the UE capability of extension of TDRA indication for Configured UL Grant type 1 | 17.1.0 | +| | RP-96 | RP-221756 | 0716 | 1 | A | Correction on the UE capability description of the overlapping PDSCH | 17.1.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------|--------| +| | RP-96 | RP-221756 | 0731 | 1 | C | Adding UE capability of CSI reporting cross PUCCH SCell group | 17.1.0 | +| | RP-96 | RP-221756 | 0733 | 1 | A | Clarification on miscellaneous UE capabilities | 17.1.0 | +| | RP-96 | RP-221756 | 0741 | 1 | A | Clarification on the applicability of mixed numerology on UE capability maxNumberCSI-RS-RRM-RS-SINR | 17.1.0 | +| | RP-96 | RP-221756 | 0743 | - | A | Correction to multi-DCI multi-TRP and new UE capability to limit PDCCH monitoring | 17.1.0 | +| | RP-96 | RP-221756 | 0744 | - | A | Clarification on configuredUL-GrantType1-v1650 | 17.1.0 | +| | RP-96 | RP-221756 | 0746 | 1 | C | Introduction UE capability for CHO with SCG configuration [CHOwithDCkept] | 17.1.0 | +| | RP-96 | RP-221736 | 0747 | 1 | B | Introduction of gNB ID length reporting in the NR CGI report [gNB_ID_Length] | 17.1.0 | +| | RP-96 | RP-221756 | 0750 | - | C | Introduction of uplink RRC Segmentation capability | 17.1.0 | +| | RP-96 | RP-221756 | 0751 | - | A | bwp-SwitchingDelay conditionally mandatory capability | 17.1.0 | +| | RP-96 | RP-221792 | 0756 | 2 | A | HARQ-ACK multiplexing on PUSCH in the absence of PUCCH | 17.1.0 | +| 09/2022 | RP-97 | RP-222519 | 0761 | 1 | A | Clarification on power sharing UE capability | 17.2.0 | +| | RP-97 | RP-222527 | 0764 | 1 | B | Release-17 UE capabilities based on R1 and R4 feature lists (TS38.306) | 17.2.0 | +| | RP-97 | RP-222526 | 0769 | - | F | Corrections to the description of gNB ID length reporting capabilities [gNB_ID_Length] | 17.2.0 | +| | RP-97 | RP-222526 | 0774 | 1 | B | 38306 CR for Early measurement for EPS fallback [IdleMeaEPSFB] | 17.2.0 | +| | RP-97 | RP-222521 | 0781 | 1 | A | Correction for the capability of SRS-PeriodicityAndOffset | 17.2.0 | +| | RP-97 | RP-222519 | 0786 | 1 | A | Correction on crossCarrierA-CSI-trigDiffSCS-r16 (38.306) | 17.2.0 | +| | RP-97 | RP-222526 | 0788 | 1 | F | Ensuring consistent support of capability bits and associated NS-values in n77 in USA and Canada | 17.2.0 | +| | RP-97 | RP-222520 | 0790 | 1 | A | Correction on PDCCH blind detection capability in CA | 17.2.0 | +| | RP-97 | RP-222520 | 0792 | 1 | A | Clarification on pusch-RepetitionTypeA-r16 capability | 17.2.0 | +| | RP-97 | RP-222518 | 0798 | 2 | A | Correction on sidelink capability | 17.2.0 | +| | RP-97 | RP-222526 | 0802 | - | B | Start drx-HARQ-RTT-TimerUL after last repetition [ulHARQ_RTT_Timer] | 17.2.0 | +| | RP-97 | RP-222522 | 0803 | - | F | Corrections on CRS-IM network assistance information | 17.2.0 | +| | RP-97 | RP-222552 | 0805 | 1 | B | 38.306 CR for introduction of MBS PDSCH FDM capabilities | 17.2.0 | +| 12/2022 | RP-98 | RP-223408 | 0699 | 2 | A | Corrections to SON/MDT capabilities | 17.3.0 | +| | RP-98 | RP-223413 | 0811 | 1 | A | Correction to definition of dualPA-Architecture capability indication | 17.3.0 | +| | RP-98 | RP-223414 | 0822 | 2 | C | Introduction of capabilities for emergency service related fallback [CellSelection_EmergencyFallback] | 17.3.0 | +| | RP-98 | RP-223415 | 0831 | 2 | B | Release-17 UE capabilities based on R1 and R4 feature lists (TS38.306) | 17.3.0 | +| | RP-98 | RP-223417 | 0840 | 1 | C | Higher granularity for per-FR gap capability [MaxCCPerFRGap] | 17.3.0 | +| | RP-98 | RP-223404 | 0845 | 1 | A | Clarification on 400MHz channel bandwidth | 17.3.0 | +| | RP-98 | RP-223409 | 0852 | - | F | Correction to support repetition on PDSCH time domain resource allocation for DCI format 1-2 | 17.3.0 | +| 03/2023 | RP-99 | RP-230687 | 0847 | 3 | A | Clarification on capabilities reported in different granularity with prerequisite | 17.4.0 | +| | RP-99 | RP-230690 | 0853 | 1 | F | IOT bit for inter satellite measurement (38.306) | 17.4.0 | +| | RP-99 | RP-230690 | 0856 | - | F | Correction to Enhanced RRM requirements for NTN measurements in IDLE and INACTIVE | 17.4.0 | +| | RP-99 | RP-230688 | 0859 | 2 | F | Release-17 UE capabilities updates/corrections based on latest R1 | 17.4.0 | + +| | | | | | | | | +|--|--|--|--|--|--|---------------------------------|--| +| | | | | | | and R4 feature lists (TS38.306) | | +|--|--|--|--|--|--|---------------------------------|--| + +| | | | | | | | | +|---------|--------|-----------|------|---|---|--------------------------------------------------------------------------------------------|--------| +| | RP-99 | RP-230691 | 0860 | 1 | F | Correction on the capability for 1024QAM | 17.4.0 | +| | RP-99 | RP-230685 | 0863 | - | A | Correction on Duty Cycle capability for PC1.5 | 17.4.0 | +| | RP-99 | RP-230691 | 0868 | 2 | F | Clarification on BWP capabilities of RedCap UEs | 17.4.0 | +| | RP-99 | RP-230686 | 0870 | 1 | A | Clarification on supportedCellGrouping capability | 17.4.0 | +| | RP-99 | RP-230685 | 0873 | 1 | A | CR on the intraBandFreqSeparationUL-AggBW-GapBW-r16_R17 | 17.4.0 | +| | RP-99 | RP-230690 | 0877 | - | F | Correction on NCSG gap pattern capability | 17.4.0 | +| | RP-99 | RP-230694 | 0879 | 2 | F | Band differentiation for capability pusCh-RepetitionTypeA-r16 | 17.4.0 | +| | RP-99 | RP-230689 | 0882 | 1 | F | Correction on codebook mode configuration for Rel-17 NCJT CSI measurement | 17.4.0 | +| | RP-99 | RP-230694 | 0885 | - | F | Introducing deriveSSB-IndexFromCellInter capability for non-NCSG UEs | 17.4.0 | +| | RP-99 | RP-230693 | 0886 | 3 | F | UE capability for NCD SSB for REDCAP for SDT | 17.4.0 | +| | RP-99 | RP-230690 | 0887 | - | B | Release-17 MBS UE capabilities based on latest R1 feature list (TS 38.306) | 17.4.0 | +| 06/2023 | RP-100 | RP-231418 | 0888 | 1 | F | Correction on NR NTN UE capabilities | 17.5.0 | +| | RP-100 | RP-231413 | 0893 | 1 | F | Corrections on the eIAB related capabilities | 17.5.0 | +| | RP-100 | RP-231418 | 0894 | 4 | F | Correction on missing referencing of the NTN spec in 38.306 | 17.5.0 | +| | RP-100 | RP-231409 | 0897 | 2 | A | Miscellaneous Correction on UE capability-R17 | 17.5.0 | +| | RP-100 | RP-231410 | 0899 | 1 | A | Correction on PDCCH Blind Detection-R17 | 17.5.0 | +| | RP-100 | RP-231418 | 0900 | 2 | F | Miscellaneous Correction on UE capability-R17 | 17.5.0 | +| | RP-100 | RP-231410 | 0902 | 1 | A | Correction on pusCh-RepetitionTypeB capability | 17.5.0 | +| | RP-100 | RP-231410 | 0904 | 1 | A | Corrections on NR-DC capabilities | 17.5.0 | +| | RP-100 | RP-231414 | 0908 | 1 | F | Correction on MBS capabilities | 17.5.0 | +| | RP-100 | RP-231417 | 0914 | - | F | Corrections to signaling of Rel-17 channel bandwidths in FR1 | 17.5.0 | +| | RP-100 | RP-231415 | 0916 | 1 | F | Correction on the capability of RedCap UE | 17.5.0 | +| | RP-100 | RP-231409 | 0919 | 1 | A | Clarification on SRS Tx switching capability | 17.5.0 | +| | RP-100 | RP-231418 | 0921 | 1 | F | Missing reference to cell reselection requirements for NTN UEs in RRC INACTIVE | 17.5.0 | +| | RP-100 | RP-231414 | 0925 | - | F | Alignment with RAN1 feature list update on MBS | 17.5.0 | +| | RP-100 | RP-231417 | 0930 | 1 | F | UE capability for releasing crossCarrierSchedulingConfig | 17.5.0 | +| 09/2023 | RP-101 | RP-232565 | 0929 | 1 | A | Introduction of intra-band EN-DC contiguous capability for UL | 17.6.0 | +| | RP-101 | RP-232565 | 0942 | 2 | A | Correction on the interpretation of the UE capability field simultaneousRxBTxInterBandENDC | 17.6.0 | +| | RP-101 | RP-232570 | 0949 | 1 | F | Miscellaneous corrections on UE capabilities | 17.6.0 | +| | RP-101 | RP-232697 | 0952 | 1 | F | Correction to SCell PRACH power scaling for UL CA | 17.6.0 | +| 12/2023 | RP-102 | RP-233888 | 0678 | 5 | B | Introduction of FR2 FBG2 CA BW classes | 17.7.0 | +| | RP-102 | RP-233884 | 0946 | 3 | A | Update to interBandMRDC-WithOverlapDL-Bands-r16 | 17.7.0 | +| | RP-102 | RP-233889 | 0957 | 1 | F | Correction on Type1 HARQ-ACK codebook generation | 17.7.0 | +| | RP-102 | RP-233888 | 0962 | 2 | F | Clarification on UplinkTxSwitchingBandParameters | 17.7.0 | +| | RP-102 | RP-233887 | 0967 | 1 | F | Correction to disabling scaling factor for Cross-carrier scheduling | 17.7.0 | +| | RP-102 | RP-233888 | 0977 | - | F | Removal of ambiguous term 'legacy' | 17.7.0 | +| | RP-102 | RP-233884 | 0987 | - | A | Correction on the interpretation of the UE capability field simultaneousRxBTxInterBandCA | 17.7.0 | +| | RP-102 | RP-233890 | 0989 | 1 | F | Clarifications on the applicability of independent gap UE capabilities | 17.7.0 | +| | RP-102 | RP-233884 | 0996 | 1 | A | Miscellaneous non-controversial rapporteur corrections on rel-17 38.306 | 17.7.0 | +| | RP-102 | RP-233940 | 1000 | 1 | F | Correction on UE capabilities of FR2-2 and IIoT | 17.7.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|---------------------------------------------------------------------------------------------------------------------|--------| +| | RP-102 | RP-233888 | 1003 | 1 | F | Correction on multipleCORESET for RedCap UEs | 17.7.0 | +| | RP-102 | RP-233889 | 1009 | - | F | Correction to support higher power limit capability for inter-band UL EN-DC | 17.7.0 | +| | RP-102 | RP-233890 | 1012 | - | F | Miscellaneous non-controversial rapporteur corrections on rel-17 38.306 | 17.7.0 | +| | RP-102 | RP-233884 | 1013 | 1 | F | Simultaneous PUSCH and PUCCH transmissions of same priority on different inter-band cells [SimultaneousPUSCH-PUCCH] | 17.7.0 | +| | RP-102 | RP-233888 | 1014 | 1 | F | Clarification on supportedModulationOrderDL for Redcap for FR1 | 17.7.0 | +| 12/2023 | RP-102 | RP-233881 | 0907 | 3 | C | Capabilities of L2 UE-to-network relay UEs for positioning [PosL2RemoteUE] | 18.0.0 | +| | RP-102 | RP-233882 | 0978 | 2 | B | MUSIM paging cause forwarding [MUSIMpagingCause] | 18.0.0 | +| | RP-102 | RP-233940 | 1015 | - | B | Introduction of Rel-18 UE capabilities | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38307/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38307/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e45d5922167165bc97c4c795e96e8fa6f5486b2 --- /dev/null +++ b/marked/Rel-18/38_series/38307/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:06dc9ba356ec05e0ef3bdf7cb0949b44b081c8a513ccc20d4ddbca64c9b19397 +size 7768 diff --git a/marked/Rel-18/38_series/38307/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38307/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..37c9dd47dfbe1328b9a11bfe7d1f5e0f85d09e0a --- /dev/null +++ b/marked/Rel-18/38_series/38307/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2e7187bffaad9b6fab81685d5c42231e60e3f8c9de299351a86013b4dd2820dd +size 5732 diff --git a/marked/Rel-18/38_series/38307/raw.md b/marked/Rel-18/38_series/38307/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..33133b870694319db0b50cd8179384b65ac18024 --- /dev/null +++ b/marked/Rel-18/38_series/38307/raw.md @@ -0,0 +1,1486 @@ + + +# 3GPP TS 38.307 V18.0.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Requirements on User Equipments (UEs) supporting a release-independent frequency band (Release 17)** + +![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, symbols and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Symbols..... | 8 | +| 3.3 Abbreviations ..... | 8 | +| 4 General..... | 8 | +| 5 Release independent features for NR frequency range 1 ..... | 9 | +| 5.1 Additional NR operating bands, UE power classes and channel bandwidths for NR frequency range 1..... | 9 | +| 5.2 Additional NR CA configurations for NR frequency range 1 ..... | 10 | +| 5.2.1 Intra-band CA..... | 10 | +| 5.2.2 Inter-band CA..... | 11 | +| 5.3 Additional NR SUL configurations for NR frequency range 1 ..... | 12 | +| 5.4 Other release independent features for NR frequency range 1 ..... | 13 | +| 5.5 Additional Inter-band NR-DC configurations for NR frequency range 1 ..... | 14 | +| 5.6 Void..... | 15 | +| 5.7 Additional Inter-band EN-DC or NR CA configurations involving shared spectrum access..... | 15 | +| 5.8 Additional V2X configurations for NR frequency range 1 ..... | 16 | +| 6 Release independent features for NR frequency range 2..... | 17 | +| 6.1 Additional NR operating bands and UE power classes for NR frequency range 2 ..... | 17 | +| 6.2 Additional NR CA configurations for NR frequency range 2 ..... | 17 | +| 6.2.1 Intra-band CA..... | 17 | +| 7 Release independent features for NR interworking between NR frequency range 1 and NR frequency range 2..... | 18 | +| 7.1 Additional NR inter-band CA configurations between frequency range 1 and frequency range 2 ..... | 18 | +| 7.2 Additional Inter-band NR-DC configurations between frequency range 1 and frequency range 2..... | 19 | +| 8 Release independent features for NR interworking between NR and E-UTRA..... | 20 | +| 8.1 Additional EN-DC configurations ..... | 20 | +| 8.1.1 Intra-band EN-DC ..... | 20 | +| 8.1.2 Inter-band EN-DC ..... | 21 | +| 8.1.2.1 Inter-band EN-DC within frequency range 1 ..... | 21 | +| 8.1.2.2 Inter-band EN-DC including frequency range 2..... | 22 | +| 8.1.2.3 Inter-band EN-DC including frequency range 1 and frequency range 2 ..... | 22 | +| 8.2 Additional NE-DC configurations ..... | 23 | +| 8.2.1 Interband NE-DC..... | 23 | +| 8.2.1.1 Interband NE-DC within frequency range 1 ..... | 23 | +| 8.2.1.2 Interband EN-DC including frequency range 2 ..... | 23 | +| 9 Release independent features for NR UE supporting satellite access operation..... | 24 | +| 9.1 Additional NR operating bands for NTN..... | 24 | +| Annex A : Frequency arrangement for overlapping operating bands..... | 25 | +| Annex B (normative): Common Requirements for bands, CA, SUL or DC ..... | 25 | +| B.1 Purpose of annex..... | 25 | +| B.2 Common RRM requirements ..... | 25 | +| B.3 Common UE performance requirements ..... | 26 | +| B.3.1 Common UE performance requirements for different CA configurations and combination sets..... | 26 | +| B.3.2 Common UE performance requirements for interworking between NR and E-UTRA..... | 26 | + +| | | | +|-------------------------------|--------------------------------------------------------------------------------------------------------------------------|-----------| +| B.3.3 | Common PDSCH demodulation and CSI requirements with inter cell interference and intra cell inter user interference ..... | 26 | +| B.3.4 | Common PDSCH absolute physical layer throughput requirements with link adaptation ..... | 27 | +| B.4 | Common UE RF requirements..... | 27 | +| B.4.1 | Common UE RF requirements for a release independent band..... | 27 | +| B.4.2 | Common UE RF requirements for CA configurations within NR frequency range 1 or NR frequency range 2 ..... | 28 | +| B.4.3 | Common UE RF requirements for SUL..... | 29 | +| B.4.4 | Common UE RF requirements for interband CA configurations between NR frequency range 1 and NR frequency range 2 ..... | 30 | +| B.4.5 | Common UE RF requirements for Inter-band NR-DC configurations between frequency range 1 and frequency range 2 ..... | 30 | +| B.4.6 | Common UE RF requirements for NR interworking between NR and E-UTRA..... | 30 | +| B.4.7 | Common UE RF requirements for UL 7.5KHz shift for TDD band n40..... | 31 | +| B.4.8 | Common UE RF requirements shared spectrum access..... | 32 | +| B.4.9 | Common UE RF requirements for Intra-band and Inter-band NR CA configurations involving shared spectrum access..... | 32 | +| B.4.10 | Common UE RF requirements for 4Rx..... | 32 | +| B.4.11 | Common UE RF requirements for transparent Tx diversity ..... | 33 | +| B.4.12 | Common UE RF requirements for NR V2X..... | 34 | +| B.4.13 | Common UE RF requirements for UL MIMO bands in FR1 ..... | 35 | +| B.4.14 | Common UE RF requirements for Inter-band CA configurations with Tx switching within NR FR1 ..... | 35 | +| B.4.15 | Common UE RF requirements for SUL configurations with Tx switching within NR FR1 ..... | 36 | +| B.4.16 | Common UE RF requirements for Inter-band EN-DC with tx switching..... | 36 | +| B.4.17 | Common UE RF requirements for 8Rx..... | 36 | +| B.4.18 | Common UE RF requirements for RedCap ..... | 37 | +| Annex C (normative): | Common Requirements for high speed train scenario..... | 38 | +| C.1 | Common RRM requirements for high speed train scenario..... | 38 | +| C.2 | Common UE demodulation requirements for high speed train scenario ..... | 38 | +| C.3 | Common RRM requirements for FR1 high speed train scenario enhancement..... | 39 | +| C.4 | Common UE demodulation requirements for FR1 high speed train scenario enhancement ..... | 39 | +| Annex D (normative): | Common PMI reporting requirements for 16TX and 32TX ..... | 41 | +| D.1 | Common UE PMI reporting requirements for 16TX and 32TX TypeI-SinglePanel Codebook ..... | 41 | +| D.2 | Common UE PMI reporting requirements for 16TX TypeII Codebook ..... | 41 | +| Annex E (normative): | Common PDSCH demodulation requirements with LTE CRS rate matching..... | 41 | +| E.1 | Common PDSCH demodulation requirements with LTE CRS rate matching ..... | 42 | +| Annex F (Informative): | Change history..... | 43 | + +# 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 requirements for Rel-16 UEs supporting release independent features like: + +- additional NR operating bands and power classes on top of Rel-16 of TS 38.101-1/-2/-3/-4 [2-5] and TS 38.133 [6]; + +Furthermore, for Rel-17 UEs supporting satellite access operation, the present document specifies requirements supporting release independent features like: + +- additional NR operating bands on top of Rel-17 of TS 38.101-5 [8] and TS 38.133 [6]. + +# --- 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-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone". +- [3] 3GPP TS 38.101-2: "NR; User Equipment (UE) radio transmission and reception; Part 2: Range 2 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.101-4: "NR; User Equipment (UE) radio transmission and reception; Part 4: UE performance requirements". +- [6] 3GPP TS 38.133: "NR; Requirements for support of radio resource management". +- [7] 3GPP TS 38.306: "NR; User Equipment (UE) radio access capabilities". +- [8] 3GPP TS 38.101-5: "NR; User Equipment (UE) radio transmission and reception; Part 5: Satellite access Radio Frequency (RF) and performance requirements". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**release independent:** applicable to some frozen releases, starting from a certain release Rel-M + +NOTE 1: Normally, a feature is introduced only in the latest open release Rel-N and future releases are based on the previous one so that future releases inherit the requirements of this feature. Introducing a feature "in a release independent way from Rel-M onwards" ( $M < N$ ) means it was decided by TSG RAN that this feature would be also beneficial in previous, already frozen releases starting with Rel-M until Rel-(N-1). In order to avoid touching TS 38.101 [2-5] or TS 38.133 [6] of these frozen releases, the corresponding requirements are captured in TS 38.307 via pointers to [2-5] or [6] of the release in which the feature was introduced. + +NOTE 2: Release independent does not mean applicable to all releases. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|---|-----------------------------------------------------------------------------------| +| N | Release in which a feature is introduced into TS 38.101 [2-5] or TS 38.133 [6] | +| M | Release from which onwards (including release M) a feature is release independent | + +## 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]. + +| | | +|--------|-----------------------------------------| +| BW | Bandwidth | +| CA | Carrier Aggregation | +| CC | Component carrier | +| DL | Downlink | +| EN-DC | Dual connectivity between E-UTRA and NR | +| FDD | Frequency Division Duplex | +| FR1 | Frequency range 1 | +| FR2 | Frequency range 2 | +| NR | New radio | +| RedCap | Reduced Capability | +| REL | Release | +| SDL | Supplementary downlink | +| SUL | Supplementary uplink | +| TDD | Time Division Duplex | +| UE | User Equipment | +| UL | Uplink | + +# --- 4 General + +TSG-RAN has agreed for certain features (see the following clauses) to introduce them in a "release independent way". + +This means for each feature: + +- it is "introduced" in a release N, i.e. TS 38.101 [2-5] and TS 38.133 [6] of release N define certain UE requirements for this feature; the feature is indicated in the tables of the following clauses; +- it is "release independent" starting from a release M ( $M < N$ ); M for the given feature is provided in the tables of the following clauses; +- UEs supporting this feature have to fulfil additional requirements in release M or higher which are specified in one or more Annexes of TS 38.307 of release N; the applicable Annexes for a given feature are provided in the tables of the following clauses. + +The applicable UE Categories are specified in TS 38.306 [7] according to the release to which the UE conforms. + +In the table of release independent features in subsequent clauses, "FDD, TDD" refers to CA or EN-DC configuration composed by only FDD bands or only TDD bands, respectively. "FDD and TDD" refers to CA or EN-DC configuration including both FDD and TDD bands. "SDL and FDD, SDL and TDD" refers to CA configuration including both SDL and FDD bands or both SDL and TDD bands, respectively. "TDD and SUL" refers to SUL configuration including both TDD and SUL bands. "FDD and TDD and SUL" refers to EN-DC configuration including both FDD, TDD and SUL bands. Unless stated otherwise, the release independent for the band combinations are from Rel-15. Configurations with BCSs other than BCS5 are release independent from Rel-15, where the BCSs for configurations are defined in TS 38.101-1 [2] and/or TS 38.101-3 [4]. Configurations with BCS5 are release independent from Rel-17, and BCS5 with signalling is allowed for early implementation from Rel-15. Note that BCS4/BCS5 is not applicable to intra-band EN-DC configurations. + +When a new feature is introduced only the latest release of release independent spec needs to be updated. The latest release of release independent spec refers to the release which the new feature is introduced in. If an RF feature introduced in the same release as the release which the feature is independent from, (i.e. $M=N$ ), the common UE RF requirements table in annex B.4 is specified from release $N+1$ , otherwise the common UE RF requirements table is specified from release $N$ . + +# 5 Release independent features for NR frequency range 1 + +## 5.1 Additional NR operating bands, UE power classes and channel bandwidths for NR frequency range 1 + +Requirements for a Rel-17 UE for additional NR operating bands and power classes compared to TS 38.101-1 of Rel-17 [2] are introduced via this clause. + +**Table 5.1-1: NR operating bands** + +| Feature | Duplex-mode | Release independent from | Requirements to be fulfilled
(see TS 38.307 of the release in which the band was introduced) | +|------------------------------------------------|--------------------|--------------------------|-------------------------------------------------------------------------------------------------| +| Operating bands | FDD, TDD, SDL, SUL | Rel-15 | Table B.4.1-1, Table B.4.3-1 | +| Shared spectrum access operating bands | TDD | Rel-16 | Table B.4.7-1 | +| UL MIMO operating bands without ULFPTx | FDD, TDD | Rel-15 | Table B.4.13-1 | +| UL MIMO operating bands with ULFPTx | FDD, TDD | Rel-16 | | +| UL MIMO operating bands with or without ULFPTx | SUL | Rel-17 | | + +**Table 5.1-2: NR UE power class** + +| Feature | Duplex-mode | Release independent from | Requirements to be fulfilled
(see TS 38.307 of the release in which the power class was introduced) | +|-----------------|---------------|--------------------------|--------------------------------------------------------------------------------------------------------| +| Power Class 1 | FDD | Rel-15 | Table B.4.1-1 | +| Power Class 1.5 | TDD | Rel-15 | Table B.4.1-1, Table B.4.3-1 | +| Power Class 2 | FDD, TDD | Rel-15 | Table B.4.1-1, Table B.4.3-1 | +| Power Class 3 | FDD, TDD, SUL | Rel-15 | Table B.4.1-1, Table B.4.3-1 | + +Table 5.1-3: NR channel bandwidths + +| Feature | Duplex-mode | Release independent from | Requirements to be fulfilled (see TS 38.307 of the release in which the channel bandwidth was introduced) | +|----------------------------------------------------|--------------------|--------------------------|-----------------------------------------------------------------------------------------------------------| +| NR channel bandwidths, all unless otherwise stated | FDD, TDD, SDL, SUL | Rel-15 | Table B.4.1-1, Table B.4.3-1 | +| Channel bandwidth of 3 MHz | FDD | Rel-18 | Table B.4.1-1 | + +## 5.2 Additional NR CA configurations for NR frequency range 1 + +### 5.2.1 Intra-band CA + +Requirements for a Rel-16 UE for additional NR intraband CA configurations within FR1 compared to TS 38.101-1 of Rel-16 [2] are introduced via this clause. + +Requirements for a Rel-17 UE for additional NR intraband CA configurations with UL MIMO within FR1 compared to TS 38.101-1 of Rel-17 [2] are introduced via this clause. + +Table 5.2.1-1: NR intra-band CA within FR1 + +| Feature | DL/UL | CA BW Class | Duplex-mode | Release independent from | requirements to be fulfilled (see 38.307 of the REL in which the CA configuration was introduced) | +|-----------------------------------------------------------------|-------|---------------------------------------|-------------|--------------------------|---------------------------------------------------------------------------------------------------| +| Intra-band contiguous CA configurations within FR1 | DL | B, C, D, E, G, H, I, J, K, L, M, N, O | FDD,TDD | Rel-15 | Table B.4.2-1 | +| | UL | A,B,C | FDD,TDD | Rel-15 | | +| Intra-band contiguous CA configurations with UL MIMO within FR1 | UL | C | FDD,TDD | Rel-15 | Table B.4.2-2 | + +Table 5.2.1-2: NR intra-band non-contiguous CA within FR1 + +| Feature | DL/UL | number of sub-blocks | maximum number of CCs within a sub-block | Duplex-mode | Release independent from | requirements to be fulfilled (see 38.307 of the REL in which the CA configuration was introduced) | +|--------------------------------------------------------|-------|----------------------|------------------------------------------|-------------|--------------------------|---------------------------------------------------------------------------------------------------| +| Intra-band non-contiguous CA configurations within FR1 | DL | 2 | 1 | FDD, TDD | Rel-15 | Table B.4.2-1 | +| | | 3 | 1 | TDD | Rel-15 | | +| | | 4 | 1 | TDD | Rel-15 | | +| | UL | 2 | 1 | TDD | Rel-15 | | + +### 5.2.2 Inter-band CA + +Requirements for a Rel-16 UE for additional NR inter-band CA configurations within FR1 compared to TS 38.101-1 of Rel-16 [2] are introduced via this clause. + +Requirements for a Rel-18 UE for additional NR inter-band CA configurations with UL MIMO within FR1 compared to TS 38.101-1 of Rel-18 [2] are introduced via this clause. + +Requirements for a Rel-18 UE for additional NR inter-band CA configurations with Tx Diversity within FR1 compared to TS 38.101-1 of Rel-18 [2] are introduced via this clause. + +**Table 5.2.2-0: NR inter-band CA UE power class within FR1** + +| Feature | Duplex-mode | Release independence from | Requirements to be fulfilled (see TS 38.307 of the release in which the power class was introduced) | +|-------------------------------|------------------------------------|---------------------------|-----------------------------------------------------------------------------------------------------| +| Inter-band CA Power Class 2 | TDD, FDD and TDD | Rel-15 | Table B.4.2-1 | +| Inter-band CA Power Class 3 | FDD, TDD, SDL and TDD, FDD and TDD | Rel-15 | | +| Inter-band CA Power Class 1.5 | FDD and TDD | Rel-17 | Table B.4.2-3, Table B.4.2-4 | + +Table 5.2.2-1: NR inter-band CA within FR1 + +| Feature | DL/UL | Maximum number of bands | number of CCs | CA BW Classes | Duplex-mode | Release independent from | requirements to be fulfilled (see 38.307 of the REL in which the CA configuration was introduced) | | +|-------------------------------------------------------------------|-------|-------------------------|---------------|---------------|-------------------------------------------------|--------------------------|---------------------------------------------------------------------------------------------------|--| +| Inter-band CA configurations within NR FR1 | DL | 4 | 5 | A, B, C | TDD, FDD, SDL and FDD, SDL and TDD, FDD and TDD | Rel-15 | Table B.4.2-1 | | +| | UL | 2 | 2 | A | TDD, FDD, FDD and TDD | Rel-15 | | | +| | | 1 | 2 | B, C, 2A | | | | | +| | | 2 | 3 | A, B, C | | | | | +| Inter-band CA configurations with UL MIMO within FR1 | DL | 2 | 2 | A | TDD, FDD and TDD | Rel-17 1 | Table B.4.2-3 | | +| | UL | 2 | 2 | A | TDD, FDD and TDD | Rel-17 1 | | | +| Inter-band CA configurations with Tx Diversity within FR1 | DL | 2 | 2 | A | FDD and TDD | Rel-17 1 | Table B.4.2-4 | | +| | UL | 2 | 2 | A | FDD and TDD | Rel-17 1 | | | +| Inter-band CA configurations with 1Tx-2Tx switching within NR FR1 | UL | 2 | 2 | A | TDD, FDD, FDD and TDD | Rel-16 | Table B.4.14-1 | | +| Inter-band CA configurations with 1Tx-2Tx switching within NR FR1 | UL | 2 | 3 | A, B, C | TDD, FDD, FDD and TDD | Rel-17 | Table B.4.14-1 | | +| Inter-band CA configurations with 2Tx-2Tx switching within NR FR1 | UL | 2 | 2 | A | TDD, FDD, FDD and TDD | Rel-17 | Table B.4.14-1 | | +| | | 2 | 3 | A, B, C | | | | | + +NOTE 1: This is applied to FWA UE only. + +## 5.3 Additional NR SUL configurations for NR frequency range 1 + +Requirements for a Rel-17 UE for additional NR SUL configurations within FR1 compared to TS 38.101-1 of Rel-17 [2] are introduced via this clause. + +When a UE is configured with both NR UL and NR SUL carriers in a serving cell with active transmission either on the UL carrier or SUL carrier, the release independent features in clause 5.1 are applicable for the UL carrier and the SUL carrier, respectively. + +Table 5.3-1: NR SUL within FR1 + +| Feature | DL/UL | number of bands | number of CCs | CA BW Classes | Duplex-mode | Release independent from | requirements to be fulfilled (see 38.307 of the REL in which the SUL) | +|---------|-------|-----------------|---------------|---------------|-------------|--------------------------|-----------------------------------------------------------------------| +| | | | | | | | | + +| | | | | | | | configuration was introduced) | +|--------------------------------------------------------------------|----|---|---|------|--------------------------|--------|-------------------------------| +| Inter-band SUL configurations within NR FR1 | DL | 3 | 3 | A, C | TDD, FDD, FDD and TDD | Rel-15 | Table B.4.3-1 | +| | UL | 2 | 3 | A, C | TDD and SUL, FDD and SUL | Rel-15 | | +| Inter-band SUL configurations with 1Tx-2Tx switching within NR FR1 | UL | 2 | 2 | A | TDD and SUL | Rel-16 | Table B.4.15-1 | +| Inter-band SUL configurations with 1Tx-2Tx switching within NR FR1 | UL | 2 | 3 | A, C | TDD and SUL, FDD and SUL | Rel-17 | Table B.4.15-1 | +| Inter-band SUL configurations with 2Tx-2Tx switching within NR FR1 | UL | 2 | 2 | A | TDD and SUL, FDD and SUL | Rel-17 | Table B.4.15-1 | +| | | 2 | 3 | A, C | | | | + +## 5.4 Other release independent features for NR frequency range 1 + +This clause covers requirements for a Rel-15 UE coming from all other release independent features that are not covered under clause 5.1, 5.2 and 5.3, e.g. generic baseband requirements or requirements that are not band/CA/SUL configuration specific. + +**Table 5.4-1: Additional requirements of other release independent features** + +| Feature | Release independent from | Requirements to be fulfilled (see 38.307 of the REL when the feature was introduced) | Further information | +|---------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| RRM requirements for high speed train scenario | Rel-15 (NOTE 1) | Table C.1-1 | Rel-16 WI NR_HST introduced band independent RRM requirements: see Table C.1-1 | +| UE demodulation requirements for high speed train scenario | Rel-15 (NOTE 1) | Table C.2-1 | Rel-16 WI NR_HST introduced band independent UE demodulation requirements: see Table C.2-1 | +| RF requirements for 4Rx UEs | Rel-15 | Table B.4.10-1, Table B.4.10-2 | | +| Transparent Tx diversity | Rel-15 | Table B.4.11-1 | Rel-17 WI NR_RF_TxD introduced transparent Tx diversity requirements: see Table B.4.11-1 | +| UE demodulation and CSI requirements for MMSE-IRC receiver for scenarios with inter cell and intra cell inter user interference | Rel-15 | Table B.3.3-1 | Rel-17 WI NR_demod_enh2-Perf: see Table B.3.3-1. These requirements are optional for Rel-15 and Rel-16 UEs and can be executed based on UE declaration. | +| RRM enhancement for FR1 high speed train scenario enhancement | Rel-16 (NOTE 2) | Table C.3-1 | Rel-17 WI NR_HST_FR1_enh introduced band independent RRM enhancement: see Table C.3-1 | +| HST-SFN CA demodulation enhancement for FR1 high speed train scenario enhancement | Rel-16 (NOTE 3) | Table C.4-1 | Rel-17 WI NR_HST_FR1_enh introduced band independent HST-SFN CA demodulation enhancement: see Table C.4-1 | +| HST-DPS CA demodulation enhancement for FR1 high speed train scenario enhancement | Rel-15 (NOTE 4) | Table C.4-1 | Rel-17 WI NR_HST_FR1_enh introduced band independent HST-DPS CA demodulation enhancement: see Table C.4-1 | +| PDSCH absolute physical layer throughput requirements with link adaptation | Rel-17 | Table B.3.4-1 | Rel-18 WI NR_demod_enh3-Perf: see Table B.3.4-1. These requirements are optional for Rel-17 and can be executed based on UE declaration. | +| RF requirements for 8Rx UE | Rel-17 | Table B.4.x-1, Table B.4.x-2 | | +| NOTE 1: Rel-15 UEs supporting the high speed train are assumed to read the Rel-16 high speed train scenario information, which is broadcast to all UEs. | | | | +| NOTE 2: Rel-16 UEs supporting the high speed train are assumed to read the Rel-17 high speed train scenario information, which is broadcast to all UEs. | | | | +| NOTE 3: Rel-16 UEs supporting the high speed train are assumed to read the Rel-17 high speed train scenario information, which is broadcast to all UEs. | | | | +| NOTE 4: Rel-15 UEs supporting the high speed train are assumed to read the Rel-17 high speed train scenario information, which is broadcast to all UEs. | | | | + +## 5.5 Additional Inter-band NR-DC configurations for NR frequency range 1 + +Requirements for a Rel-16 UE for additional NR-DC configurations within FR1 compared to TS 38.101-1 of Rel-16 [2] are introduced via this clause. + +Table 5.5.1-1: NR-DC within FR1 + +| Feature | DL/UL | Maximum number of bands | number of CCs | CA BW Classes | Duplex-mode | Release independent from | requirements to be fulfilled (see 38.307 of the REL in which the DC configuration was introduced) | +|------------------------------------|-------|-------------------------|---------------|---------------|-------------|--------------------------|---------------------------------------------------------------------------------------------------| +| NR-DC configurations within NR FR1 | DL | 2 | 2 | A | FDD | Rel-16 | | + +5.6 UL 7.5KHz shift for TDD band n40 Requirements for a Rel-17 UE for UL 7.5KHz shift for TDD band n40 within FR1 compared to TS 38.101-1 of Rel-17 [2] are introduced via this clause. For Band n40, UL shift is only applicable to uplink transmissions using a 15 kHz SCS. + +Table 5.3-2: UL 7.5KHz shift for band n40 in FR1 + +| Feature | DL/UL | Duplex-mode | Release independent from | requirements to be fulfilled (see 38.307 of the REL in which the configuration was introduced) | +|-------------------------------------|-------|-------------|--------------------------|------------------------------------------------------------------------------------------------| +| 7.5KHz UL shift for band n40 in FR1 | UL | TDD | Rel-15 | Table B.4.7-1 | + +## 5.6 Void + +## 5.7 Additional Inter-band EN-DC or NR CA configurations involving shared spectrum access + +Requirements for a Rel-17 UE for additional NR CA, EN-DC, and NR DC configurations involving shared spectrum access compared to TS 38.101-1 of Rel-16 [2] or TS 38.101-3 of Rel-17 [4] are introduced via this clause. + +Table 5.6-1: NR-DC within FR1 + +| Feature | Duplex-mode | Release independent from | Requirements to be fulfilled (see 38.307 of the REL in which the EN-DC or NR CA configuration was introduced) | +|---------------------------------------------------------------------------------|------------------|--------------------------|---------------------------------------------------------------------------------------------------------------| +| Intra-band and Inter-band NR CA configurations involving shared spectrum access | FDD and TDD, TDD | Rel-16 | Table B.3.1-1, Table B.4.2-1, Table B.4.8-1 | +| Inter-band EN-DC configurations involving shared spectrum access | FDD and TDD, TDD | Rel-16 | Table B.4.6-1 | +| Inter-band NR DC configurations involving shared spectrum access | FDD and TDD, TDD | Rel-16 | Table B.4.5-1 | + +## 5.8 Additional V2X configurations for NR frequency range 1 + +Requirements for a Rel-18 UE for additional NR SL configurations involving V2X con-current operation compared to TS 38.101-1 of Rel-18 [4] are introduced via this clause. + +Table 5.8-1: NR V2X con-current operation within in FR1 + +| Feature | Release independent from | Requirements to be fulfilled (see 38.307 of the REL when the feature was introduced) | Further information | +|------------------------------------------------------------------|--------------------------|--------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Operating bands for V2X communication with con-current operation | Rel-16 | Table B.4.12-1, Table B.4.12-2 | NR V2X new bands, intra-band/inter-band con-current operation, SL MIMO/TxD are release independent according to requirements in Table B.4.12-1, Table B.4.12-2 | + +## 5.9 Additional operating bands for Redcap for NR frequency range 1 + +Requirements for a Rel-18 Redcap UE for additional operating bands within FR1 compared to TS 38.101-1 of Rel-18 [2] are introduced via this clause. + +Table 5.9-1: NR RedCap operating band + +| Feature | Duplex-mode | Release independent from | Requirements to be fulfilled (see TS 38.307 of the release in which the band was introduced) | +|-----------------------|-------------|--------------------------|----------------------------------------------------------------------------------------------| +| Redcap operating band | FDD | Rel-17 | Table B.4.14-1 | + +# 6 Release independent features for NR frequency range 2 + +## 6.1 Additional NR operating bands and UE power classes for NR frequency range 2 + +Requirements for a Rel-16 UE for additional NR operating bands and power classes compared to TS 38.101-2 of Rel-16 [3] are introduced via this clause. + +**Table 6.1-1: NR operating bands** + +| Feature | Duplex-mode | Release independent from | Requirements to be fulfilled
(see TS 38.307 of the release in which the band was introduced) | +|-----------------|-------------|--------------------------|-------------------------------------------------------------------------------------------------| +| Operating bands | TDD | Rel-15 | Table B.4.1-1 | + +**Table 6.1-2: NR UE power class** + +| Feature | Duplex-mode | Release independent from | Requirements to be fulfilled
(see TS 38.307 of the release in which the band was introduced) | +|---------------------------|-------------|--------------------------|-------------------------------------------------------------------------------------------------| +| Power Class 1, 2, 3, 4, 5 | TDD | Rel-15 | Table B.4.1-1 | + +## 6.2 Additional NR CA configurations for NR frequency range 2 + +### 6.2.1 Intra-band CA + +Requirements for a Rel-16 UE for additional NR intra-band CA configurations within FR2 compared to TS 38.101-2 of Rel-16 [3] are introduced via this clause. + +**Table 6.2.1-1: NR intra-band contiguous CA within FR2** + +| Feature | DL/UL | CA BW Class | Duplex-mode | Release independent from | requirements to be fulfilled
(see 38.307 of the REL in which the CA configuration was introduced) | +|----------------------------------------------------|-------|---------------------------------------------|-------------|--------------------------|------------------------------------------------------------------------------------------------------| +| Intra-band contiguous CA configurations within FR2 | DL | B, C, D, E, F, G, H, I, J, K, L, M, O, P, Q | TDD | Rel-15 | Table B.4.2-1 | +| | UL | B, D, E, F, G, H, I, J, K, L, M, O, P, Q | TDD | Rel-15 | | + +Table 6.2.1-2: NR non-contiguous intra-band CA within FR2 + +| Feature | DL/UL | number of sub-blocks | maximum number of CCs within a sub-block | Duplex-mode | Release independent from | requirements to be fulfilled (see 38.307 of the REL in which the CA configuration was introduced) | +|--------------------------------------------------------|-------|----------------------|------------------------------------------|-------------|--------------------------|---------------------------------------------------------------------------------------------------| +| Intra-band non-contiguous CA configurations within FR2 | DL | 2 | 4 | TDD | Rel-15 | Table B.4.2-1 | +| | | 3 | 1 | TDD | Rel-15 | | +| | | 4 | 1 | TDD | Rel-15 | | +| | | 5 | 2 | TDD | Rel-15 | | +| | | 6 | 2 | TDD | Rel-15 | | +| | | 7 | 2 | TDD | Rel-15 | | +| | | 8 | 1 | TDD | Rel-15 | | +| | | 9 | 1 | TDD | Rel-15 | | +| | | 10 | 1 | TDD | Rel-15 | | + +Table 6.2.1-3: NR inter-band CA within FR2 + +| Feature | DL/UL | Maximum number of bands | CA BW Classes | Duplex-mode | Release independent from | requirements to be fulfilled (see 38.307 of the REL in which the CA configuration was introduced) | +|--------------------------------------------|-------|-------------------------|---------------------------------------------|-------------|--------------------------|---------------------------------------------------------------------------------------------------| +| Inter-band CA configurations within NR FR2 | DL | 2 | B, C, D, E, F, G, H, I, J, K, L, M, O, P, Q | TDD | Rel-16 | Table B.4.2-1 | +| | UL | 1 | B, C, D, E, F, G, H, I, J, K, L, M, O, P, Q | TDD | Rel-16 | | + +# 7 Release independent features for NR interworking between NR frequency range 1 and NR frequency range 2 + +## 7.1 Additional NR inter-band CA configurations between frequency range 1 and frequency range 2 + +Requirements for a Rel-16 UE for additional NR inter-band CA configurations between FR1 and FR2 compared to TS 38.101-3 of Rel-16 [4] are introduced via this clause. + +Table 7.1-1: NR inter-band CA between FR1 and FR2 + +| Feature | DL/UL | number of bands | maximum number of CCs | CA BW Classes | Duplex-mode | Release independent from | requirements to be fulfilled (see 38.307 of the REL in which the CA configuration was introduced) | +|----------------------------------------------------------------------|--------|-----------------|-----------------------|---------------------------------|-----------------------|--------------------------|---------------------------------------------------------------------------------------------------| +| Inter-band CA configurations for NR interworking between FR1 and FR2 | DL FR1 | 3 | 4 | A, C | FDD, TDD, FDD and TDD | Rel-15 | Table B.4.4-1 | +| | DL FR2 | 1 | 4 | A, D, E, F, G, H, I, J, K, L, M | TDD | Rel-15 | | +| | UL FR1 | 1 | 1 | A | FDD, TDD | Rel-15 | | +| | UL FR2 | 1 | 1 | A, D, G, H, I, J, K, L, M | TDD | Rel-15 | | + +## 7.2 Additional Inter-band NR-DC configurations between frequency range 1 and frequency range 2 + +Requirements for a Rel-16 UE for additional Inter-band NR-DC configurations between FR1 and FR2 compared to TS 38.101-3 of Rel-16 [4] are introduced via this clause. + +Table 7.2-1: Inter-band NR-DC between FR1 and FR2 + +| Feature | DL/UL | number of bands | maximum number of CCs | CA BW Classes | Duplex-mode | Release independent from | requirements to be fulfilled (see 38.307 of the REL in which the CA configuration was introduced) | +|----------------------------------------------------------------------|--------|-----------------|-----------------------|---------------------------------|-----------------------|--------------------------|---------------------------------------------------------------------------------------------------| +| Inter-band DC configurations for NR interworking between FR1 and FR2 | DL FR1 | 3 | 4 | A, C | FDD, TDD, FDD and TDD | Rel-15 | Table B.4.5-1 | +| | DL FR2 | 1 | 8 | A, D, E, F, G, H, I, J, K, L, M | TDD | Rel-15 | | +| | UL FR1 | 1 | 1 | A | FDD, TDD | Rel-15 | | +| | UL FR2 | 1 | 1 | A, D, G, H, I, J, K, L, M | TDD | Rel-15 | | + +# 8 Release independent features for NR interworking between NR and E-UTRA + +## 8.1 Additional EN-DC configurations + +### 8.1.1 Intra-band EN-DC + +Requirements for a Rel-16 UE for additional EN-DC intra-band configurations within FR1 compared to TS 38.101-3 of Rel-16 [4] are introduced via this clause. + +**Table 8.1.1-0: EN-DC intra-band UE power class** + +| Feature | Duplex-mode | Release independent from | Requirements to be fulfilled (see TS 38.307 of the release in which the band was introduced) | +|-------------------------------------------------|-------------|--------------------------|----------------------------------------------------------------------------------------------| +| Intra-band contiguous EN-DC power class 1.5 | TDD | Rel-15 | Table B.4.6-1 | +| Intra-band contiguous EN-DC power class 2 | TDD | Rel-15 | | +| Intra-band contiguous EN-DC power class 3 | FDD, TDD | Rel-15 | | +| Intra-band non-contiguous EN-DC power class 1.5 | TDD | Rel-15 | | +| Intra-band non-contiguous EN-DC power class 2 | TDD | Rel-15 | | +| Intra-band non-contiguous EN-DC power class 3 | FDD, TDD | Rel-15 | | + +**Table 8.1.1-1: EN-DC contiguous intra-band configurations within FR1** + +| Feature | DL/UL | maximum number of E-UTRA CCs | maximum number of NR CCs | Duplex-mode | Release independent from | requirements to be fulfilled (see 38.307 of the REL in which the CA configuration was introduced) | +|-----------------------------|-------|------------------------------|--------------------------|-------------|--------------------------|---------------------------------------------------------------------------------------------------| +| Intra-band contiguous EN-DC | DL | 3 | 2 | FDD, TDD | Rel-15 | Table B.3.2-1, Table B.4.6-1 | +| | UL | 1 | 1 | FDD, TDD | Rel-15 | | + +**Table 8.1.1-2: EN-DC non-contiguous intra-band configurations within FR1** + +| Feature | DL/UL | maximum number of sub-blocks | maximum number of E-UTRA CCs | maximum number of NR CCs | Duplex-mode | Release independent from | requirements to be fulfilled (see 38.307 of the REL in which the CA configuration was introduced) | +|---------------------------------|-------|------------------------------|------------------------------|--------------------------|-------------|--------------------------|---------------------------------------------------------------------------------------------------| +| Intra-band non-contiguous EN-DC | DL | 3 | 3 | 1 | FDD, TDD | Rel-15 | Table B.3.2-2, Table B.4.6-1 | +| | UL | 2 | 1 | 1 | FDD, TDD | Rel-15 | | + +### 8.1.2 Inter-band EN-DC + +#### 8.1.2.1 Inter-band EN-DC within frequency range 1 + +Requirements for a Rel-16 UE for additional EN-DC inter-band configurations within FR1 compared to TS 38.101-3 of Rel-16 [4] are introduced via this clause. + +Requirements for a Rel-18 UE for additional EN-DC inter-band configurations with UL MIMO within FR1 compared to TS 38.101-3 of Rel-18 [4] are introduced via this clause. + +Requirements for a Rel-18 UE for additional NR inter-band CA configurations with Tx Diversity within FR1 compared to TS 38.101-3 of Rel-18 [2] are introduced via this clause. + +**Table 8.1.2.1-0: EN-DC inter-band UE power class** + +| Feature | Duplex-mode | Release independent from | Requirements to be fulfilled (see TS 38.307 of the release in which the band was introduced) | +|--------------------------------|-----------------------|--------------------------|----------------------------------------------------------------------------------------------| +| Inter-band EN-DC Power Class 2 | TDD, FDD and TDD | Rel-15 | Table B.4.6-1 | +| Inter-band EN-DC Power Class 3 | FDD, TDD, FDD and TDD | Rel-15 | | + +**Table 8.1.2.1-1: EN-DC inter-band configurations without SUL within FR1** + +| Feature | DL/UL | maximum number of E-UTRA bands | maximum number of E-UTRA CCs | maximum number of NR bands | maximum number of NR CCs | Duplex-mode | Release independent from | requirements to be fulfilled (see 38.307 of the REL in which the CA configuration was introduced) | +|-----------------------------------------------|-------|--------------------------------|------------------------------|----------------------------|--------------------------|-----------------------|--------------------------|---------------------------------------------------------------------------------------------------| +| Inter-band EN-DC | DL | 6 | 6 | 2 | 3 | FDD, TDD, FDD and TDD | Rel-15 | Table B.4.6-1 | +| | UL | 1 | 2 contiguous | 1 | 2 contiguous | FDD, TDD, FDD and TDD | Rel-15 | | +| Inter-band EN-DC with UL MIMO within FR1 | DL | 1 | 1 | 1 | 1 | TDD, FDD and TDD | Rel-17 1 | Table B.4.6-2 | +| | UL | 1 | 1 | 1 | 1 | TDD, FDD and TDD | Rel-17 1 | | +| Inter-band EN-DC with Tx Diversity within FR1 | DL | 1 | 1 | 1 | 1 | FDD and TDD | Rel-17 1 | Table B.4.6-3 | +| | UL | 1 | 1 | 1 | 1 | FDD and TDD | Rel-17 1 | | +| Inter-band EN-DC with 1Tx-2Tx switching | UL | 1 | 1 | 1 | 1 | TDD, FDD and TDD | Rel-16 | Table B.4.16-1 | + +NOTE 1: This is applied to FWA UE only. + +Table 8.1.2.1-2: EN-DC inter-band configurations with SUL within FR1 + +| Feature | DL/UL | maximum number of E-UTRA bands | maximum number of E-UTRA CCs | maximum number of NR bands | maximum number of NR CCs | Duplex-mode | Release independent from | requirements to be fulfilled (see 38.307 of the REL in which the CA configuration was introduced) | +|------------------|-------|--------------------------------|------------------------------|----------------------------|--------------------------|-------------------------------|--------------------------|---------------------------------------------------------------------------------------------------| +| Inter-band EN-DC | DL | 2 | 3 | 1 | 1 | FDD, TDD, FDD and TDD | Rel-15 | Table B.4.6-1 | +| | UL | 1 | 1 | 2 | 2 contiguous | FDD, TDD, FDD and TDD and SUL | Rel-15 | | + +#### 8.1.2.2 Inter-band EN-DC including frequency range 2 + +Requirements for a Rel-16 UE for additional EN-DC inter-band configurations including FR2 compared to TS 38.101-3 of Rel-16 [4] are introduced via this clause. + +Table 8.1.2.2-1: EN-DC inter-band configurations including FR2 + +| Feature | DL/UL | number of E-UTRA bands | maximum number of E-UTRA CCs | number of NR bands | maximum number of NR CCs | Duplex-mode | Release independent from | requirements to be fulfilled (see 38.307 of the REL in which the CA configuration was introduced) | +|------------------|-------|------------------------|------------------------------|--------------------|--------------------------|------------------|--------------------------|---------------------------------------------------------------------------------------------------| +| Inter-band EN-DC | DL | 4 | 6 | 1 | 10 | TDD, FDD and TDD | Rel-15 | Table B.4.6-1 | +| | UL | 1 | 4 | 1 | 8 | TDD, FDD and TDD | Rel-15 | | + +#### 8.1.2.3 Inter-band EN-DC including frequency range 1 and frequency range 2 + +Requirements for a Rel-16 UE for additional EN-DC inter-band configurations including FR1 and FR2 compared to TS 38.101-3 of Rel-16 [4] are introduced via this clause. + +Table 8.1.2.3-1: EN-DC inter-band configurations including FR1 and FR2 + +| Feature | DL/UL | maximum number of E-UTRA bands | maximum number of E-UTRA CCs | maximum number of NR bands | maximum number of NR CCs | Duplex-mode | Release independent from | requirements to be fulfilled (see 38.307 of the REL in which the CA configuration was introduced) | +|------------------|--------|--------------------------------|------------------------------|----------------------------|--------------------------|-----------------------|--------------------------|---------------------------------------------------------------------------------------------------| +| Inter-band EN-DC | DL FR1 | 4 | 6 | 1 | 2 | TDD, FDD, FDD and TDD | Rel-15 | Table B.4.6-1 | +| | DL FR2 | | | 1 | 8 | TDD | Rel-15 | | +| | UL FR1 | 1 | 2 | 1 | 1 | FDD, TDD, FDD and TDD | Rel-15 | | +| | UL FR2 | | | 1 | 3 | TDD, | Rel-15 | | + +## 8.2 Additional NE-DC configurations + +### 8.2.1 Interband NE-DC + +#### 8.2.1.1 Interband NE-DC within frequency range 1 + +Requirements for a Rel-17 UE for additional NE-DC interband configurations within FR1 compared to TS 38.101-3 of Rel-17 [4] are introduced via this clause. + +**Table 8.2.1.1-0: NE-DC interband UE power class** + +| Feature | Duplex-mode | Release independent from | Requirements to be fulfilled (see TS 38.307 of the release in which the band was introduced) | +|-------------------------------|-----------------------|--------------------------|----------------------------------------------------------------------------------------------| +| Interband NE-DC Power Class 3 | FDD, TDD, FDD and TDD | Rel-15 | Table B.4.6-1 | + +**Table 8.2.1.1-1: NE-DC interband configurations without SUL within FR1** + +| Feature | DL/UL | maximum number of E-UTRA bands | maximum number of E-UTRA CCs | maximum number of NR bands | maximum number of NR CCs | Duplex-mode | Release independent from | requirements to be fulfilled (see 38.307 of the REL in which the CA configuration was introduced) | +|-----------------|-------|--------------------------------|------------------------------|----------------------------|--------------------------|-----------------------|--------------------------|---------------------------------------------------------------------------------------------------| +| Interband NE-DC | DL | 4 | 5 | 1 | 1 | FDD, TDD, FDD and TDD | Rel-15 | Table B.4.6-1 | +| | UL | 1 | 1 | 1 | 1 | FDD, TDD, FDD and TDD | Rel-15 | | + +#### 8.2.1.2 Interband EN-DC including frequency range 2 + +Requirements for a Rel-17 UE for additional NE-DC interband configurations including FR2 compared to TS 38.101-3 of Rel-17 [4] are introduced via this clause. + +**Table 8.2.1.2-1: NE-DC interband configurations including FR2** + +| Feature | DL/UL | number of E-UTRA bands | maximum number of E-UTRA CCs | number of NR bands | maximum number of NR CCs | Duplex-mode | Release independent from | requirements to be fulfilled (see 38.307 of the REL in which the CA configuration was introduced) | +|-----------------|-------|------------------------|------------------------------|--------------------|--------------------------|-------------|--------------------------|---------------------------------------------------------------------------------------------------| +| Interband NE-DC | DL | 4 | 5 | 1 | 8 | FDD and TDD | Rel-15 | Table B.4.6-1 | +| | UL | 1 | 2 | 1 | 8 | FDD and TDD | Rel-15 | | + +# 9 Release independent features for NR UE supporting satellite access operation + +## 9.1 Additional NR operating bands for NTN + +Requirements for a Rel-17 NR UE supporting satellite access operation, for additional NTN operating bands compared to TS 38.101-5 of Rel-17 [8] are introduced via this clause. + +**Table 9.1-1: Additional NR operating bands for NTN** + +| Feature | Duplex-mode | Release independent from | Requirements to be fulfilled
(see TS 38.307 of the release in which the band was introduced) | +|---------------------|-------------|--------------------------|-------------------------------------------------------------------------------------------------| +| NTN operating bands | FDD | Rel-17 | Table F.1-1 | + +**Table 9.1-2: NR NTN UE power class** + +| Feature | Duplex-mode | Release independent from | Requirements to be fulfilled
(see TS 38.307 of the release in which the power class was introduced) | +|---------------|-------------|--------------------------|--------------------------------------------------------------------------------------------------------| +| Power Class 3 | FDD | Rel-17 | | + +**Table 9.1-3: NR NTN UE channel bandwidth** + +| Feature | Duplex-mode | Release independent from | Requirements to be fulfilled
(see TS 38.307 of the release in which the UE channel bandwidth was introduced) | +|----------------------|-------------|--------------------------|-----------------------------------------------------------------------------------------------------------------| +| UE channel bandwidth | FDD | Rel-17 | | + +# Annex A : Frequency arrangement for overlapping operating bands + +The following information is provided in order to assist a UE derive the DL NR-ARFCN and UL NR-ARFCN in a multi-band environment, in which multiple overlapping operating bands may be indicated in the fields *freqBandIndicatorNR* and *MultiFrequencyBandListNR-SIB*. + +The overlapping bands, independent of release, which may be indicated in a cell are shown in Table A-1 for applicable NR operating bands. The DL NR-ARFCN and UL NR-ARFCN are derived according to TS 38.101-1 and TS 38.101-2. + +**Table A-1: Overlapping bands (multi-band environments) for each NR band** + +| NR Operating Band | Overlapping NR operating bands | Duplex Mode | +|-------------------|--------------------------------|-------------| +| n2 | n25 | FDD | +| n5 | n18, n26 | FDD | +| n8 | n106 | FDD | +| n18 | n5, n26 | FDD | +| n12 | n85 | FDD | +| n25 | n2 | FDD | +| n26 | n5, n18 | FDD | +| n31 | n72 | FDD | +| n38 | n41, n90 | TDD | +| n41 | n38, n90 | TDD | +| n48 | n78, n77 | TDD | +| n72 | n31 | FDD | +| n78 | n48, n77 | TDD | +| n77 | n48, n78 | TDD | +| n80 | n86 | SUL | +| n85 | n12 | FDD | +| n86 | n80 | SUL | +| n96 | n102 | TDD | +| n102 | n96 | TDD | +| n106 | n8 | FDD | +| n257 | n258 | TDD | +| n257 | n261 | TDD | +| n259 | n260 | TDD | + +# Annex B (normative): Common Requirements for bands, CA, SUL or DC + +## B.1 Purpose of annex + +The purpose of Annex B is to group the requirements that are common for several bands or CA configurations in this specification and use the common tables as references. + +## B.2 Common RRM requirements + +## B.3 Common UE performance requirements + +### B.3.1 Common UE performance requirements for different CA configurations and combination sets + +The requirements and test cases listed in Table B.3.1-1 are specified in Rel-16 version of TS 38.101-4 [5]. + +**Table B.3.1-1: Common UE performance requirements for different CA configurations and combination sets** + +| Section / Clause | Description | +|-------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------| +| 5.2A.2.1 | PDSCH 2RX demodulation requirements for NR FR1 CA configurations (Note 1) | +| 5.2A.3.1 | PDSCH 4RX demodulation requirements for NR FR1 CA configurations (Note 1) | +| 7.2A.2 | PDSCH 2RX demodulation requirements for NR FR2 CA configurations (Note 1) | +| 5.2A.2.2 | PDSCH 2RX demodulation requirements for NR FR1 intra-band contiguous CA with power imbalance (Note 2) | +| 5.2A.3.2 | PDSCH 4RX demodulation requirements for NR FR1 intra-band contiguous CA with power imbalance (Note 2) | +| 6.2A | Channel Quality Indicator (CQI) reporting requirements for NR FR1 CA (Note 3) | +| 8.2A | Channel Quality Indicator (CQI) reporting requirements for NR FR2 CA (Note 3) | +| NOTE 1: The applicability of requirements for different CA configurations and bandwidth combination sets is specified in Section 5.1.1.5 and 7.1.1.5. | | +| NOTE 2: The applicability of PDSCH performance requirements with power imbalance for intra-band contiguous CA is specified in Section 5.1.1.6. | | +| NOTE 3: The applicability of Channel Quality Indicator (CQI) reporting requirements for CA specified in Section 6.1.1.5 and 8.1.1.5. | | + +### B.3.2 Common UE performance requirements for interworking between NR and E-UTRA + +The requirements and test cases listed in Table B.3.2-1 and Table B.3.2-2 are specified in Rel-16 version of TS 38.101-4 [5]. + +**Table B.3.2-1: Common UE performance requirements for intra-band contiguous EN-DC within FR1** + +| Section / Clause | Description | +|-----------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------| +| 9.5B.1.1 | PDSCH demodulation for FR1 intra-band contiguous EN-DC with power imbalance (Note 1) | +| NOTE 1: The requirements applicability for UE supporting FR1 intra-band and inter-band EN-DC is specified in Section 9.1.1. | | + +**Table B.3.2-2: Common UE performance requirements for intra-band non-contiguous EN-DC within FR1** + +| Section / Clause | Description | +|-----------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------| +| 9.5B.1.2 | PDSCH demodulation for FR1 intra-band non-contiguous EN-DC with power imbalance (Note 1) | +| NOTE 1: The requirements applicability for UE supporting FR1 intra-band and inter-band EN-DC is specified in Section 9.1.1. | | + +### B.3.3 Common PDSCH demodulation and CSI requirements with inter cell interference and intra cell inter user interference + +The requirements and test cases listed in Table B.3.3-1 are specified in Rel-17 version of TS 38.101-4 [5]. + +**Table B.3.3-1: UE PDSCH demodulation and CSI requirements with MMSE-IRC receiver for scenarios with inter cell interference and intra cell inter user interference** + +| Section / Clause | Description | +|------------------|-------------------------------------------------------------------------------------| +| 5.2.2.1.15 | PDSCH demodulation requirements with inter cell interference for 2RX FDD | +| 5.2.3.1.15 | PDSCH demodulation requirements with inter cell interference for 4RX FDD | +| 5.2.2.2.16 | PDSCH demodulation requirements with inter cell interference for 2RX TDD | +| 5.2.3.2.16 | PDSCH demodulation requirements with inter cell interference for 4RX TDD | +| 5.2.2.1.16 | PDSCH demodulation requirements with intra cell inter user interference for 2RX FDD | +| 5.2.3.1.16 | PDSCH demodulation requirements with intra cell inter user interference for 4RX FDD | +| 5.2.2.2.17 | PDSCH demodulation requirements with intra cell inter user interference for 2RX TDD | +| 5.2.3.2.17 | PDSCH demodulation requirements with intra cell inter user interference for 4RX TDD | +| 6.2.2.1.2.3 | CQI requirements with inter cell interference for 2RX FDD | +| 6.2.3.1.2.3 | CQI requirements with inter cell interference for 4RX FDD | +| 6.2.2.2.2.2 | CQI requirements with inter cell interference for 2RX TDD | +| 6.2.3.2.2.2 | CQI requirements with inter cell interference for 4RX TDD | + +### B.3.4 Common PDSCH absolute physical layer throughput requirements with link adaptation + +The requirements and test cases listed in Table B.3.4-1 are specified in Rel-18 version of TS 38.101-4 [5]. + +**Table B.3.4-1: UE PDSCH absolute physical layer throughput requirements with link adaptation** + +| Section / Clause | Description | +|------------------|--------------------------------------------------------------------------------------------| +| 5.6.2.1.1 | FR1 PDSCH absolute physical layer throughput requirements with link adaptation for 2RX FDD | +| 5.6.3.1.1 | FR1 PDSCH absolute physical layer throughput requirements with link adaptation for 4RX FDD | +| 5.6.2.2.1 | FR1 PDSCH absolute physical layer throughput requirements with link adaptation for 2RX TDD | +| 5.6.3.2.1 | FR1 PDSCH absolute physical layer throughput requirements with link adaptation for 4RX TDD | +| 7.6.2.2.1 | FR2 PDSCH absolute physical layer throughput requirements with link adaptation for 2RX TDD | + +## B.4 Common UE RF requirements + +### B.4.1 Common UE RF requirements for a release independent band + +The requirements and test cases listed in Table B.4.1-1 are specified in REL-17 version of TS 38.101-1 [2] or TS 38.101-2 [3]. + +**Table B.4.1-1: Common UE RF requirements for a release independent band** + +| Clause / Clause | Description | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------| +| 5.2 | Operating bands | +| 5.3 | UE Channel bandwidth | +| 5.4 | Channel arrangement | +| 6.2 | Transmitter power | +| 6.3 | Output power dynamics | +| 6.4 | Transmit signal quality | +| 6.5 | Output RF spectrum emissions | +| 6.6 of [3] | Beam correspondence | +| 7.3 | Reference sensitivity | +| 7.4 | Maximum input level | +| 7.5 | Adjacent Channel Selectivity | +| 7.6 | Blocking characteristics | +| 7.7 of [2] | Spurious response | +| 7.8 of [2] | Intermodulation characteristics | +| 7.9 | Spurious emissions | +| L.1 | Indication of modified MPR behavior | +| NOTE: A UE which supports any FR2 band introduced in release N, where N > 15, shall meet the requirements according to the FR2 UE multi-band relaxation factors defined in Table 6.2.1.3-4 of the release N version of [3] for all FR2 bands which it supports. | | + +### B.4.2 Common UE RF requirements for CA configurations within NR frequency range 1 or NR frequency range 2 + +The requirements and test cases listed in Table B.4.2-1 are specified in in REL-16 version of TS 38.101-1 [2] or TS 38.101-2 [3]. + +**Table B.4.2-1: Common UE RF requirements for a release independent CA configurations within NR frequency range 1 or NR frequency range 2** + +| Clause | Description | +|-------------|----------------------------------------| +| 5.2A | Operating bands for CA | +| 5.3A | UE channel bandwidth for CA | +| 5.4A | Channel arrangement for CA | +| 6.2A | Transmitter power for CA | +| 6.3A | Output power dynamics for CA | +| 6.4A | Transmit signal quality for CA | +| 6.5A | Output RF spectrum emissions for CA | +| 6.6A of [3] | Beam correspondence for CA | +| 7.3A | Reference sensitivity for CA | +| 7.4A | Maximum input level for CA | +| 7.5A | Adjacent Channel Selectivity for CA | +| 7.6A | Blocking characteristics for CA | +| 7.7A of [2] | Spurious response for CA | +| 7.8A of [2] | Intermodulation characteristics for CA | +| 7.9A of [2] | Spurious emissions for CA | + +The requirements and test cases listed in Table B.4.2-2 are specified in in REL-17 version of TS 38.101-1 [2]. + +**Table B.4.2-2: Common UE RF requirements for a release independent intra-band contiguous UL CA configurations with UL MIMO within NR frequency range 1** + +| Clause | Description | +|--------|--------------------------------------------------------------------------| +| 6.2H | Transmitter power for CA with UL MIMO | +| 6.2H.1 | Transmitter power for intra-band UL contiguous CA for UL MIMO | +| 6.3H | Output power dynamics for intra-band UL contiguous CA for UL MIMO | +| 6.4H | Transmit signal quality for CA with UL MIMO | +| 6.4H.1 | Transmit signal quality for intra-band UL contiguous CA for UL MIMO | +| 6.5H | Output RF spectrum emissions for CA with UL MIMO | +| 6.5H.1 | Output RF spectrum emissions for intra-band UL contiguous CA for UL MIMO | + +The requirements and test cases listed in Table B.4.2-3 are specified in REL-18 version of TS 38.101-1 [2]. + +**Table B.4.2-3: Common UE RF requirements for a release independent inter-band UL CA configurations with UL MIMO within NR frequency range 1** + +| Clause | Description | +|----------|----------------------------------------------------------------| +| 6.2H.3 | Transmitter power for inter-band UL CA with UL MIMO | +| 6.3H.3 | Output power dynamics for inter-band UL CA with UL MIMO | +| 6.4H.3 | Transmit signal quality for inter-band UL CA with UL MIMO | +| 6.5H.3 | Output RF spectrum emissions for inter-band UL CA with UL MIMO | +| 7.3A.2.3 | Reference sensitivity power level for Inter-band CA | + +The requirements and test cases listed in Table B.4.2-4 are specified in REL-18 version of TS 38.101-1 [2]. + +**Table B.4.2-4: Common UE RF requirements for a release independent inter-band UL CA configurations with Tx Diversity within NR frequency range 1** + +| Clause | Description | +|----------|---------------------------------------------------------------------| +| 6.2L.3 | Transmitter power for inter-band UL CA with Tx Diversity | +| 6.3L.3 | Output power dynamics for inter-band UL CA with Tx Diversity | +| 6.4L.3 | Transmit signal quality for inter-band UL CA with Tx Diversity | +| 6.5L.3 | Output RF spectrum emissions for inter-band UL CA with Tx Diversity | +| 7.3A.2.3 | Reference sensitivity power level for Inter-band CA | + +### B.4.3 Common UE RF requirements for SUL + +The requirements and test cases listed in Table B.4.3-1 are specified in REL-17 version of TS 38.101-1 [2]. + +**Table B.4.3-1: Common UE RF requirements for a release independent SUL** + +| Clause | Description | +|---------|--------------------------------------------------------------| +| 5.2 | Operating bands | +| 5.2C | Operating band combination for SUL | +| 5.4.2.1 | NR-ARFCN and channel raster (7.5kHz frequency shift for SUL) | +| 5.5C | Configurations for SUL | +| 6.2C | Transmitter power for SUL | +| 6.4.2.2 | Carrier leakage (7.5 kHz shift with the carrier frequency.) | +| 7.3.3 | $\Delta RIB,c$ | +| 7.3C | Reference sensitivity for SUL | +| 7.6C | Blocking characteristics for SUL | + +### B.4.4 Common UE RF requirements for interband CA configurations between NR frequency range 1 and NR frequency range 2 + +The requirements and test cases listed in Table B.4.4-1 are specified in in REL-16 version of TS 38.101-3 [4]. + +**Table B.4.4-1: Common UE RF requirements for a release independent interband CA configurations between NR frequency range 1 and NR frequency range 2** + +| Clause | Description | +|--------|----------------------------------------| +| 5.2A | Operating bands for CA | +| 5.3A | UE channel bandwidth for CA | +| 5.4A | Channel arrangement for CA | +| 6.2A | Transmitter power for CA | +| 6.3A | Output power dynamics for CA | +| 6.4A | Transmit signal quality for CA | +| 6.5A | Output RF spectrum emissions for CA | +| 7.3A | Reference sensitivity for CA | +| 7.4A | Maximum input level for CA | +| 7.5A | Adjacent Channel Selectivity for CA | +| 7.6A | Blocking characteristics for CA | +| 7.7A | Spurious response for CA | +| 7.8A | Intermodulation characteristics for CA | +| 7.9A | Spurious emissions for CA | + +### B.4.5 Common UE RF requirements for Inter-band NR-DC configurations between frequency range 1 and frequency range 2 + +The requirements and test cases listed in Table B.4.5-1 are specified in in REL-16 version of TS 38.101-3 [4]. + +**Table B.4.5-1: Common UE RF requirements for a release independent Inter-band NR-DC configurations between frequency range 1 and frequency range 2** + +| Clause | Description | +|--------|---------------------------------------| +| 4.2 | Applicability of minimum requirements | +| 5.2B | Operating bands for DC | +| 6.2B.5 | Configured output power for NR-DC | + +### B.4.6 Common UE RF requirements for NR interworking between NR and E-UTRA + +The requirements and test cases listed in Table B.4.6-1 are specified in REL-16 version of TS 38.101-3 [4]. + +**Table B.4.6-1: Common UE RF requirements for a release independent NR interworking between NR and E-UTRA** + +| Clause | Description | +|--------|-----------------------------------------------| +| 4.2 | Applicability of minimum requirements | +| 5.2B | Operating bands for DC | +| 5.3B | UE channel bandwidth for DC | +| 5.4B | Channel arrangement for DC | +| 6.2B | Transmitter power for DC | +| 6.3B | Output power dynamics for DC | +| 6.4B | Transmit signal quality for DC | +| 6.5B | Output RF spectrum emissions for DC | +| 6.6B | Beam correspondence for DC | +| 7.3B | Reference sensitivity level for DC | +| 7.4B | Maximum input level for DC in FR1 | +| 7.5B | Adjacent Channel Selectivity for DC in FR1 | +| 7.6B | Blocking characteristics for DC in FR1 | +| 7.7B | Spurious response for DC in FR1 | +| 7.8B | Intermodulation characteristics for DC in FR1 | +| 7.9A | Spurious emissions for CA in FR1 | + +The requirements and test cases listed in Table B.4.6-2 are specified in REL-18 version of TS 38.101-3 [4]. + +**Table B.4.6-2: Common UE RF requirements for a release independent NR interworking between NR with UL MIMO within FR1 and E-UTRA** + +| Clause | Description | +|----------|--------------------------------------------------| +| 6.2H | Transmitter power for DC with UL MIMO | +| 6.3H | Output power dynamics for DC with UL MIMO | +| 6.4H | Transmit signal quality for DC with UL MIMO | +| 6.5H | Output RF spectrum emissions for DC with UL MIMO | +| 7.3B.2.3 | Inter-band EN-DC within FR1 | + +The requirements and test cases listed in Table B.4.6-3 are specified in REL-18 version of TS 38.101-3 [4]. + +**Table B.4.6-3: Common UE RF requirements for a release independent NR interworking between NR with Tx Diversity within FR1 and E-UTRA** + +| Clause | Description | +|----------|-------------------------------------------------------| +| 6.2L | Transmitter power for DC with Tx Diversity | +| 6.3L | Output power dynamics for DC with Tx Diversity | +| 6.4L | Transmit signal quality for DC with Tx Diversity | +| 6.5L | Output RF spectrum emissions for DC with Tx Diversity | +| 7.3B.2.3 | Inter-band EN-DC within FR1 | + +### B.4.7 Common UE RF requirements for UL 7.5KHz shift for TDD band n40 + +The requirements and test cases listed in Table B.4.7-1 are specified in REL-17 version of TS 38.101-1 [2]. For Band n40, UL shift is only applicable to uplink transmissions using a 15 kHz SCS. + +**Table B.4.7-1: Common UE RF requirements for UL 7.5KHz shift for TDD Band n40** + +| Clause | Description | +|---------|-----------------------------------------------------------------------| +| 5.4.2.1 | NR-ARFCN and channel raster (7.5kHz frequency shift for TDD band n40) | + +### B.4.8 Common UE RF requirements shared spectrum access + +The requirements and test cases listed in Table B.4.8-1 are specified in REL-17 version of TS 38.101-1 [2]. + +**Table B.4.8-1: Common UE RF requirements for shared spectrum access** + +| Clause | Description | +|--------|--------------------------------------------------------------------| +| 5.2A | Operating bands for CA | +| 5.3A | UE channel bandwidth for CA | +| 5.4A | Channel arrangement for CA | +| 6.2F | Transmitter power for shared spectrum channel access | +| 6.3F | Output power dynamics for shared spectrum channel access | +| 6.4F | Transmit signal quality for shared spectrum channel access | +| 6.5F | Output RF spectrum emissions | +| 7.3F | Reference sensitivity for shared spectrum channel access | +| 7.4 | Maximum input level | +| 7.5F | Adjacent channel selectivity | +| 7.6F | Blocking characteristics | +| 7.7F | Spurious response for shared spectrum channel access | +| 7.8F | Intermodulation characteristics for shared spectrum channel access | +| 7.9 | Spurious emissions | + +### B.4.9 Common UE RF requirements for Intra-band and Inter-band NR CA configurations involving shared spectrum access + +The requirements and test cases listed in Table B.4.9-1 are specified in REL-17 version of TS 38.101-1 [2]. + +**Table B.4.9-1: Common UE RF requirements for Intra-band and Inter-band NR CA configurations involving shared spectrum access** + +| Clause | Description | +|-----------|----------------------------------------------------------------| +| 6.2F.1A.1 | UE maximum output power for inter-band CA | +| 6.2F.2A.1 | UE maximum output power reduction for inter-band CA | +| 6.2F.3A.1 | UE additional maximum output power reduction for inter-band CA | +| 6.3F.3A.1 | General ON/OFF mask for inter-band CA | +| 6.4F.2A.1 | Transmit modulation quality for inter-band CA | +| 7.3F.3 | $\Delta R_{IB,c}$ | +| 7.3F.4 | Intra-band contiguous shared spectrum channel access CA | +| 7.3G.5 | Inter-band CA with shared spectrum channel access | +| 7.5F.2 | Intra-band contiguous shared spectrum channel access CA | +| 7.7F.2 | Intra-band contiguous shared spectrum channel access CA | + +### B.4.10 Common UE RF requirements for 4Rx + +The requirements and test cases listed in Table B.4.10-1 are specified in REL-17 version of TS 38.101-1 [2]. + +**Table B.4.10-1: Common UE RF requirements for 4Rx for single band in FR1** + +| Clause | Description | +|--------|---------------------------------| +| 6.2.4 | Configured transmitted power | +| 7.3 | Reference sensitivity | +| 7.4 | Maximum input level | +| 7.5 | Adjacent Channel Selectivity | +| 7.6 | Blocking characteristics | +| 7.7 | Spurious response | +| 7.8 | Intermodulation characteristics | +| 7.9 | Spurious emissions | + +The requirements and test cases listed in Table B.4.10-2 are specified in REL-17 version of TS 38.101-1 [2]. + +**Table B.4.10-2: Common UE RF requirements for 4Rx for CA in FR1** + +| Clause | Description | +|--------|----------------------------------------| +| 6.2A.4 | Configured output power for CA | +| 7.3A | Reference sensitivity for CA | +| 7.4A | Maximum input level for CA | +| 7.5A | Adjacent Channel Selectivity for CA | +| 7.6A | Blocking characteristics for CA | +| 7.7A | Spurious response for CA | +| 7.8A | Intermodulation characteristics for CA | +| 7.9A | Spurious emissions for CA | + +### B.4.11 Common UE RF requirements for transparent Tx diversity + +The requirements and test cases listed in Table B.4.11-1 are specified in in REL-17 version of TS 38.101-1 [2]. + +**Table B.4.11-1: Common UE RF requirements for a release independent transparent Tx diversity** + +| Clause | Description | +|----------|---------------------------------------------------------------| +| 6.2G | Transmitter power for Tx Diversity | +| 6.2G.1 | UE maximum output power for Tx Diversity | +| 6.2G.2 | UE maximum output power reduction for Tx Diversity | +| 6.2G.3 | UE additional maximum output power reduction for Tx Diversity | +| 6.2G.4 | Configured transmitted power for Tx Diversity | +| 6.3G | Output power dynamics for Tx Diversity | +| 6.3G.1 | Minimum output power for Tx Diversity | +| 6.3G.2 | Transmit OFF power for Tx Diversity | +| 6.3G.3 | Transmit ON/OFF time mask for Tx Diversity | +| 6.3G.4 | Power control for Tx Diversity | +| 6.4G | Transmit signal quality for Tx Diversity | +| 6.4G.1 | Frequency error for Tx Diversity | +| 6.4G.2 | Transmit modulation quality for Tx Diversity | +| 6.4G.2.1 | Error Vector Magnitude | +| 6.4G.2.2 | Carrier leakage | +| 6.4G.2.3 | In-band emissions | +| 6.4G.2.4 | EVM equalizer spectrum flatness for Tx Diversity | +| 6.5G | Output RF spectrum emissions for Tx Diversity | +| 6.5G.1 | Occupied bandwidth for Tx Diversity | +| 6.5G.2 | Out of band emission for Tx Diversity | +| 6.5G.3 | Spurious emission for Tx Diversity | +| 6.5G.4 | Transmit intermodulation for Tx Diversity | +| 7.3G | Reference sensitivity for Tx Diversity | +| F.8 | EVM measurement for dual Tx | + +### B.4.12 Common UE RF requirements for NR V2X + +The requirements and test cases listed in Table B.4.12-1 are specified in REL-18 version of TS 38.101-1 [2]. + +**Table B.4.12-1: Common UE RF requirements for release independent operating bands and concurrent operation for NR V2X** + +| Clause | Description | +|--------|-----------------------------------------------| +| 5.2E | Operating band for V2X | +| 5.2E.1 | V2X operating bands | +| 5.2E.2 | V2X operating bands for con-current operation | +| 5.3E | Channel bandwidth for V2X | +| 5.4E | Channel arrangement for V2X | +| 6.2E | Transmitter power for V2X | +| 6.3E | Output power dynamics for V2X | +| 6.4E | Transmit signal quality for V2X | +| 6.5E | Output RF spectrum emissions for V2X | +| 7.3E | Reference sensitivity for V2X | +| 7.4E | Maximum input level for V2X | +| 7.5E | Adjacent channel selectivity for V2X | +| 7.6E | Blocking characteristics for V2X | +| 7.7E | Spurious response for V2X | +| 7.8E | Intermodulation characteristics for V2X | + +The requirements and test cases listed in Table B.4.12-2 are specified in REL-18 version of TS 38.101-3 [2]. + +**Table B.4.12-2: Common UE RF requirements for release independent intra-band and inter-band concurrent operation for NR V2X** + +| Clause | Description | +|--------|----------------------------------------------------------| +| 5.2E | Operating bands for V2X | +| 5.3E | UE Channel bandwidth for V2X | +| 5.5E | Configuration for V2X operation | +| 6.2E | Transmitter power for V2X in FR1 | +| 6.3E | Output power dynamics for V2X | +| 6.4E | Transmit signal quality for V2X operation in FR1 | +| 6.5E | Output RF spectrum emissions for V2X operation in FR1 | +| 7.3E | Reference sensitivity for V2X operation in FR1 | +| 7.4E | Maximum input level for V2X operation in FR1 | +| 7.5E | Adjacent channel selectivity for V2X operation in FR1 | +| 7.6E | Blocking characteristics for V2X in FR1 | +| 7.7E | Spurious response for V2X in FR1 | +| 7.8E | Intermodulation characteristics for V2X operation in FR1 | + +### B.4.13 Common UE RF requirements for UL MIMO bands in FR1 + +The requirements and test cases listed in Table B.4.13-1 and Table B.4.13-2 are specified in REL-17 version of TS 38.101-1 [2]. + +**Table B.4.13-1: Common UE RF requirements for UL MIMO band in FR1** + +| Clause | Description | +|--------|---------------------------------------------| +| 6.2D | Transmitter power for UL MIMO | +| 6.3D | Output power dynamics for UL MIMO | +| 6.4D | Transmit signal quality for UL MIMO | +| 6.5D | Output RF spectrum emissions for UL MIMO | +| 7.3D | Reference sensitivity for UL MIMO | +| 7.4D | Maximum input level for UL MIMO | +| 7.5D | Adjacent channel selectivity for UL MIMO | +| 7.6D | Blocking characteristics for UL MIMO | +| 7.7D | Spurious response for UL MIMO | +| 7.8D | Intermodulation characteristics for UL MIMO | + +**Table B.4.13-2: Common UL MIMO requirements for shared spectrum channel access in FR1** + +| Clause | Description | +|---------|----------------------------------------------------------| +| 6.2F.1D | UE maximum output power for UL MIMO | +| 6.2F.2D | UE maximum output power reduction for UL MIMO | +| 6.2F.3D | UE additional maximum output power reduction for UL MIMO | +| 6.2F.4D | Configured transmitted power UL MIMO | + +### B.4.14 Common UE RF requirements for Inter-band CA configurations with Tx switching within NR FR1 + +The requirements and test cases listed in Table B.4.14-1 are specified in Rel-18 version of TS 38.101-1 [2]. + +**Table B.4.14-1: Common UE RF requirements for Inter-band CA configurations with Tx switching within NR FR1** + +| Clause | Description | +|----------|---------------------------------------------| +| 5.2A.2 | Operating bands for inter-band CA | +| 6.3A.3.3 | Transmit ON/OFF time mask for inter-band CA | + +### B.4.15 Common UE RF requirements for SUL configurations with Tx switching within NR FR1 + +The requirements and test cases listed in Table B.4.15-1 are specified in Rel-18 version of TS 38.101-1 [2]. + +**Table B.4.15-1: Common UE RF requirements for SUL configurations with Tx switching within NR FR1** + +| Clause | Description | +|--------|-----------------------------------| +| 6.3C.3 | Transmit ON/OFF time mask for SUL | + +### B.4.16 Common UE RF requirements for Inter-band EN-DC with tx switching + +The requirements and test cases listed in Table B.4.16-1 are specified in REL-18 version of TS 38.101-3 [4]. + +**Table B.4.16-1: Common UE RF requirements for Inter-band EN-DC with tx switching** + +| Clause | Description | +|--------|-----------------------------------------------------------------| +| 5.5B.4 | Configuration for Inter-band EN-DC within FR1 | +| 6.3B.4 | Output power dynamics for switching between two uplink carriers | + +### B.4.17 Common UE RF requirements for 8Rx + +The requirements and test cases listed in Table B.4.17-1 are specified in REL-18 version of TS 38.101-1 [2]. + +**Table B.4.17-1: Common UE RF requirements for 8Rx for single band in FR1** + +| Clause | Description | +|--------|---------------------------------| +| 6.2.4 | Configured output power | +| 7.3 | Reference sensitivity | +| 7.4 | Maximum input level | +| 7.5 | Adjacent Channel Selectivity | +| 7.6 | Blocking characteristics | +| 7.7 | Spurious response | +| 7.8 | Intermodulation characteristics | +| 7.9 | Spurious emissions | + +The requirements and test cases listed in Table B.4.17-2 are specified in REL-18 version of TS 38.101-1 [2]. + +**Table B.4.17-2: Common UE RF requirements for 8Rx for CA in FR1** + +| Clause | Description | +|--------|----------------------------------------| +| 6.2A.4 | Configured output power for CA | +| 7.3A | Reference sensitivity for CA | +| 7.4A | Maximum input level for CA | +| 7.5A | Adjacent Channel Selectivity for CA | +| 7.6A | Blocking characteristics for CA | +| 7.7A | Spurious response for CA | +| 7.8A | Intermodulation characteristics for CA | +| 7.9A | Spurious emissions for CA | + +### B.4.18 Common UE RF requirements for RedCap + +The requirements and test cases listed in Table B.4.18-1 are specified in REL-18 version of TS 38.101-1 [2]. + +**Table B.4.18-1: Common UE RF requirements for RedCap UE in FR1** + +| Clause | Description | +|--------|----------------------------------| +| 5.3 | UE channel bandwidth | +| 5.3I | Channel bandwidth for RedCap | +| 5.4 | Channel arrangement | +| 6.1 | General | +| 6.2 | Transmitter power | +| 6.2I | Transmitter power for RedCap | +| 6.3 | Output power dynamics | +| 6.4 | Transmit signal quality | +| 6.5 | Output RF spectrum emissions | +| 7.1 | General | +| 7.1I | General | +| 7.2 | Diversity characteristics | +| 7.3I | Reference sensitivity for RedCap | +| 7.4 | Maximum input level | +| 7.5 | Adjacent channel selectivity | +| 7.6 | Blocking characteristics | +| 7.7 | Spurious response | +| 7.8 | Intermodulation characteristics | +| 7.9 | Spurious emissions | + +# Annex C (normative): Common Requirements for high speed train scenario + +## C.1 Common RRM requirements for high speed train scenario + +The requirements and test cases listed in Table C.1-1 are specified in TS 38.133 Rel-16 and TS 36.133 Rel-16. + +**Table C.1-1: RRM requirements for high speed train scenario** + +| Clause | Description | +|-------------------------|-------------------------------------------------------------------------------------------| +| 4.2.2.2 in TS 38.133 | Cell Re-selection requirements for intra-frequency NR cells for high speed train scenario | +| 9.2.5 in TS 38.133 | NR intra-frequency measurements without measurement gaps for high speed train scenario | +| 9.2.6 in TS 38.133 | NR intra-frequency measurements with measurement gaps for high speed train scenario | +| 4.2.2.5 in TS 38.133 | Cell Re-selection measurements of inter-RAT E-UTRAN cells for high speed train scenario | +| 9.4.2 in TS 38.133 | NR – E-UTRAN FDD measurements for high speed train scenario | +| 9.4.3 in TS 38.133 | NR – E-UTRAN TDD measurements for high speed train scenario | +| 9.5.4 in TS 38.133 | L1-RSRP measurement requirements for high speed train scenario | +| 4.2.2.5.6 in TS 36.133 | Cell Re-selection measurements of inter-RAT NR cells for high speed train scenario | +| 8.1.2.4.21 in TS 36.133 | E-UTRAN FDD – NR measurements for high speed train scenario | +| 8.1.2.4.22 in TS 36.133 | E-UTRAN TDD – NR measurements for high speed train scenario | + +## C.2 Common UE demodulation requirements for high speed train scenario + +The requirements and test cases listed in Table C.2-1 are specified in TS 38.101-4 Rel-16. + +**Table C.2-1: UE demodulation requirements for high speed train scenario** + +| Clause | Description | +|-------------------------------|-------------------------------------------------------------------------------------------------| +| 5.2.2.2.9 test 1-1 | TDD PDSCH requirements for HST-SFN for high speed train scenario with 2RX | +| 5.2.3.2.9 test 1-1 | TDD PDSCH requirements for HST-SFN for high speed train scenario with 4RX | +| 5.2.2.1.9 test 1-1 | FDD PDSCH requirements for HST-SFN for high speed train scenario with 2RX | +| 5.2.3.1.9 test 1-1 | FDD PDSCH requirements for HST-SFN for high speed train scenario with 4RX | +| 5.2.2.2.1 test 1-10, 1-11 | TDD PDSCH requirements for HST single tap and multi-path for high speed train scenario with 2RX | +| 5.2.3.2.1 test 1-10, 1-11 | TDD PDSCH requirements for HST single tap and multi-path for high speed train scenario with 4RX | +| 5.2.2.1.1 test 1-6, 1-7 | FDD PDSCH requirements for HST single tap and multi-path for high speed train scenario with 2RX | +| 5.2.3.1.1 test 1-6, 1-7 | FDD PDSCH requirements for HST single tap and multi-path for high speed train scenario with 4RX | +| 5.2.2.1.10 test 1-1, test 1-2 | FDD PDSCH requirements for HST DPS for high speed train scenario with 2RX | +| 5.2.2.2.10 test 1-1, test 1-2 | TDD PDSCH requirements for HST DPS for high speed train scenario with 2RX | +| 5.2.3.1.10 test 1-1, test 1-2 | FDD PDSCH requirements for HST DPS for high speed train scenario with 4RX | +| 5.2.3.2.10 test 1-1, test 1-2 | TDD PDSCH requirements for HST DPS for high speed train scenario with 4RX | + +## C.3 Common RRM requirements for FR1 high speed train scenario enhancement + +The requirements and test cases listed in Table C.3-1 are specified in TS 38.133 Rel-17. + +**Table C.3-1: RRM requirements for FR1 high speed train scenario enhancement** + +| Clause | Description | +|----------------------|--------------------------------------------------------------------------------------------------------------------------------------| +| 4.2.2.4 in TS 38.133 | Cell Re-selection requirements for inter-frequency NR cells for FR1 high speed train scenario | +| 9.2.5 in TS 38.133 | NR intra-frequency measurements without measurement gaps for activated SCell and deactivated SCell for FR1 high speed train scenario | +| 9.2.6 in TS 38.133 | NR intra-frequency measurements with measurement gaps for active SCell for FR1 high speed train scenario | +| 9.3.4 in TS 38.133 | Inter-frequency measurement with measurement gaps for FR1 high speed train scenario | +| 9.3.5 in TS 38.133 | Inter-frequency measurement with measurement gaps for FR1 high speed train scenario | +| 9.3.9 in TS 38.133 | Inter frequency measurements without measurement gaps for FR1 high speed train scenario | +| 9.5.4 in TS 38.133 | L1-RSRP measurement requirements for FR1 high speed train scenario | + +## C.4 Common UE demodulation requirements for FR1 high speed train scenario enhancement + +The requirements and test cases listed in Table C.4-1 are specified in TS 38.101-4 Rel-17. + +**Table C.4-1: CA demodulation requirements for FR1 high speed train scenario enhancement** + +| Clause | Description | +|---------------|------------------------------------------------------------------------------| +| 5.2A.2.4 | PDSCH requirements for HST-SFN CA for FR1 high speed train scenario with 2RX | +| 5.2A.3.4 | PDSCH requirements for HST-SFN CA for FR1 high speed train scenario with 4RX | +| 5.2A.2.5 | PDSCH requirements for HST-DPS CA for FR1 high speed train scenario with 2RX | +| 5.2A.3.5 | PDSCH requirements for HST-DPS CA for FR1 high speed train scenario with 4RX | + +# --- Annex D (normative): Common PMI reporting requirements for 16TX and 32TX + +## D.1 Common UE PMI reporting requirements for 16TX and 32TX TypeI-SinglePanel Codebook + +The requirements and test cases listed in Table D.1-1 are specified in Rel-16 version of TS 38.101-4 [5]. + +**Table D.1-1: UE PMI reporting requirements for 16TX and 32TX TypeI-SinglePanel Codebook** + +| Section / Clause | Description | +|------------------|---------------------------------------------------------------| +| 6.3.2.1.3 | Multiple PMI with 16TX TypeI-SinglePanel Codebook for 2Rx FDD | +| 6.3.2.1.4 | Single PMI with 32TX TypeI-SinglePanel Codebook for 2Rx FDD | +| 6.3.2.2.3 | Multiple PMI with 16TX TypeI-SinglePanel Codebook for 2Rx TDD | +| 6.3.2.2.4 | Single PMI with 32TX TypeI-SinglePanel Codebook for 2Rx TDD | +| 6.3.3.1.3 | Multiple PMI with 16TX TypeI-SinglePanel Codebook for 4Rx FDD | +| 6.3.3.1.4 | Single PMI with 32TX TypeI-SinglePanel Codebook for 4Rx FDD | +| 6.3.3.2.3 | Multiple PMI with 16TX TypeI-SinglePanel Codebook for 4Rx TDD | +| 6.3.3.2.4 | Single PMI with 32TX TypeI-SinglePanel Codebook for 4Rx TDD | + +## --- D.2 Common UE PMI reporting requirements for 16TX TypeII Codebook + +The requirements and test cases listed in Table D.2-1 are specified in Rel-16 version of TS 38.101-4 [5]. + +**Table D.2-1: UE PMI reporting requirements for 16TX TypeII Codebook** + +| Section / Clause | Description | +|------------------|----------------------------------------------------| +| 6.3.2.1.5 | Multiple PMI with 16TX TypeII Codebook for 2Rx FDD | +| 6.3.2.2.5 | Multiple PMI with 16TX TypeII Codebook for 2Rx TDD | +| 6.3.3.1.5 | Multiple PMI with 16TX TypeII Codebook for 4Rx FDD | +| 6.3.3.2.5 | Multiple PMI with 16TX TypeII Codebook for 4Rx TDD | + +# --- Annex E (normative): Common PDSCH demodulation requirements with LTE CRS rate matching + +## E.1 Common PDSCH demodulation requirements with LTE CRS rate matching + +The requirements and test cases listed in Table E.1-1 are specified in Rel-16 version of TS 38.101-4 [5]. + +**Table E.1-1: UE PDSCH demodulation requirements with LTE CRS rate matching for TDD band** + +| Section / Clause | Description | +|------------------|------------------------------------------------------------------------| +| 5.2.2.2.4 | PDSCH demodulation requirements with LTE CRS rate matching for 2Rx TDD | +| 5.2.3.2.4 | PDSCH demodulation requirements with LTE CRS rate matching for 4Rx TDD | + +# --- Annex F (Informative): Change history + +| Change history | | | | | | | | +|----------------|----------|------------|------|-----|-----|---------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-09 | RAN4#85 | R4-1712166 | | | | Skeleton TS | 0.0.1 | +| 2018-03 | RAN4#86 | R4-1802107 | | | | TS 38.307 v0.1.0 | 0.1.0 | +| 2018-06 | RAN#80 | RP-180988 | | | | v1.0.0 submitted for plenary approval | 1.0.0 | +| 2018-06 | RAN#80 | | | | | Approved by plenary – Rel-15 spec under change control | 15.0.0 | +| 2018-09 | RAN#81 | RP-181896 | 0001 | | F | CR for FR2 Power Classes in TS38.307 | 15.1.0 | +| 2018-12 | RAN#82 | RP-182362 | 0002 | 2 | B | CR for TS 38.307 | 15.2.0 | +| 2019-06 | RAN#84 | RP-191237 | 0005 | | B | Addition of missing features for TS 38.307 | 15.3.0 | +| 2019-09 | RAN#85 | RP-192046 | 0007 | 1 | B | REL-16 TS 38.307 addition of Annexes for UE RF requirements | 16.0.0 | +| 2019-12 | RAN#86 | RP-193019 | 0009 | | B | CR for REL-16 TS 38.307 for PC2 EN-DC TDD+TDD | 16.1.0 | +| 2019-12 | RAN#86 | RP-193018 | 0012 | | B | CR for TS 38.307: additional UE channel bandwidth | 16.1.0 | +| 2019-12 | RAN#86 | RP-193036 | 0014 | | A | Adding SDL to 38.307 | 16.1.0 | +| 2020-03 | RAN#87 | RP-200404 | 0016 | | A | 38.307 CR power class | 16.2.0 | +| 2020-06 | RAN#88 | RP-201046 | 0018 | | F | CR to 38.307 on clarification of the FR2 multi-band requirement framework | 16.3.0 | +| 2020-06 | RAN#88 | RP-200986 | 0022 | | A | Maintenance CR to 38307 on a reference spec number R16 | 16.3.0 | +| 2020-06 | RAN#88 | RP-200959 | 0023 | | F | Endorsed CR to 38307 on applicable SUL requirements | 16.3.0 | +| 2020-06 | RAN#88 | RP-200965 | 0019 | 1 | B | CR for 38.307: Introduction of Power Class 1.5 | 16.3.0 | +| 2020-09 | RAN#89 | RP-201503 | 0028 | | B | CR for 38.307: Introduction of Power Class 1.5 | 16.4.0 | +| 2020-12 | RAN#90 | RP-202485 | 0032 | 1 | F | CR on adding NR overlapping bands list in TS38.307 in Rel-16 | 16.5.0 | +| 2020-12 | RAN#90 | RP-202428 | 0040 | 1 | B | CR to TS 38.307 on release independent update for the Rel.16 EN-DC and NR CA/DC | 16.5.0 | +| 2020-12 | RAN#90 | RP-202429 | 0041 | | B | CR to TS 38.307 on Release independence of FDD-TDD EN-DC High Power UE | 16.5.0 | +| 2020-12 | RAN#90 | RP-202422 | 0035 | 1 | B | CR on release independent for Rel.16 NR HST RRM requirements | 16.5.0 | +| 2020-12 | RAN#90 | RP-202422 | 0036 | 1 | B | CR on release independent for Rel.16 NR HST UE demodulation requirements | 16.5.0 | +| 2020-12 | RAN#90 | | 0024 | 3 | B | LTE/NR spectrum sharing in Band 40/n40 | 17.0.0 | +| 2021-03 | RAN#91 | RP-210093 | 0042 | | B | CR for 38.307: introduction of power class 5 for FR2 | 17.1.0 | +| 2021-03 | RAN#91 | RP-210065 | 0045 | | A | Draft CR for TS 38.307 on UE demodulation performance requirements (Rel-17) | 17.1.0 | +| 2021-03 | RAN#91 | RP-210078 | 0048 | | A | CR on release independent for Rel-16 NR HST UE demodulation requirements | 17.1.0 | +| 2021-03 | RAN#91 | RP-210098 | 0051 | 1 | B | CR to 38.807 Release independent for UE power class 2 NR inter-band CA and SUL configurations (R17) | 17.1.0 | +| 2021-06 | RAN#92 | RP-211104 | 0062 | | A | CR to 38.307 to add interband CA R17 CATA | 17.2.0 | +| 2021-09 | RAN#93 | RP-211921 | 0071 | | A | CR to TS 38.307 on the definition of the duplex-mode for the band configurations | 17.3.0 | +| 2021-09 | RAN#93 | RP-211922 | 0077 | | A | CR Correction of common UE RF requirement 38.307 Annex tables R17 | 17.3.0 | +| 2021-12 | RAN#94 | RP-212828 | 0080 | 1 | B | CR for REL-17 TS 38.307 for FR1 NE-DC | 17.4.0 | +| 2021-12 | RAN#94 | RP-212837 | 0085 | | F | Big CR for TS 38.307 Maintenance (Rel-17) | 17.4.0 | +| 2022-03 | RAN#95 | RP-220353 | 0087 | 1 | B | CR to TS 38.307 on Release independence of BCS4 and BCS5 | 17.5.0 | +| 2022-03 | RAN#95 | RP-220343 | 0088 | | B | CR to TS38.307: Release independent for PC2 FDD bands | 17.5.0 | +| 2022-03 | RAN#95 | RP-220349 | 0090 | 1 | B | Big CR for TS 38.307: release independent requirements for TxD | 17.5.0 | +| 2022-03 | RAN#95 | RP-220337 | 0093 | | A | Big CR for TS 38.307 Maintenance (Rel-17) | 17.5.0 | +| 2022-03 | RAN#95 | RP-220352 | 0096 | | F | CR for release independent for 4Rx support for NR band | 17.5.0 | +| 2022-06 | RAN#96 | RP-221685 | 0098 | | B | CR for release independent of Rel.17 NE-DC FR1 and FR2 combinations | 17.6.0 | +| 2022-06 | RAN#96 | RP-221686 | 0099 | | B | CR for 38.307 to update the release independence for R17 SUL band combinations | 17.6.0 | +| 2022-06 | RAN#96 | RP-221670 | 0100 | 1 | B | Big CR for TS 38.307: release independent for UL MIMO bands (R17) | 17.6.0 | +| 2022-06 | RAN#96 | RP-221661 | 0101 | 1 | B | Big CR to TS 38.307: intra-band CA with MIMO requirements (R17) | 17.6.0 | +| 2022-06 | RAN#96 | RP-221677 | 0102 | 1 | F | CR to TS 38.307: SL requirements (R17) | 17.6.0 | +| 2022-06 | RAN#96 | RP-221663 | 0104 | | A | Big CR for TS 38.307 Maintenance (Rel-17) | 17.6.0 | +| 2022-06 | RAN#96 | RP-221680 | 0106 | | B | CR to 38.307: release independent for FR1 HST demodulation (Rel-17) | 17.6.0 | +| 2022-09 | RAN#97 | RP-222036 | 0107 | | F | CR to R17 38307 to add UL configurations for inter-band combinations and overlapping bands | 17.7.0 | +| 2022-09 | RAN#97 | RP-222049 | 0109 | | B | CR for introduction of release independence for MMSE-IRC receiver requirements | 17.7.0 | +| 2022-12 | RAN#98-e | RP-223310 | 0111 | 1 | F | CR on release independent for Rel-17 FR1 HST RRM | 17.8.0 | +| 2022-12 | RAN#98-e | RP-223310 | 0112 | | F | CR on release independent for FR1 HST demodulation | 17.8.0 | +| 2023-03 | RAN#99 | RP-230501 | 0115 | | A | CR 38.307 Addition of FR2 overlapping bands into Annex-A R17 | 17.9.0 | +| 2023-06 | RAN#100 | RP-231341 | 0117 | 1 | F | Correction to Frequency arrangement for overlapping operating bands information R17 | 17.10.0 | +| 2023-06 | RAN#100 | RP-231350 | 0119 | | F | CR on 38.307: Cleanup the brackets of section number in UE PDSCH requirements with inter cell interference | 17.10.0 | +| 2023-12 | RAN#102 | RP-233370 | 0127 | | B | CR on release independent for concurrent operation of NR/LTE Uu bands/band combinations and one NR/LTE V2X PC5 band | 18.0.0 | + +| | | | | | | | | +|---------|---------|-----------|------|---|---|-----------------------------------------------------------------------------------------------|--------| +| 2023-12 | RAN#102 | RP-233351 | 0129 | | F | [NR_RF_TxD-Core] Removing brackets from TxD release independent information | 18.0.0 | +| 2023-12 | RAN#102 | RP-233363 | 0132 | | B | CR for 38.307: Release independence of NR 3 MHz channel bandwidth | 18.0.0 | +| 2023-12 | RAN#102 | RP-233366 | 0131 | | B | CR for 38.307 n106 and n8 overlapping bands | 18.0.0 | +| 2023-12 | RAN#102 | RP-233364 | 0133 | | B | Introducing release independence for Absolute physical layer throughput requirements | 18.0.0 | +| 2023-12 | RAN#102 | RP-233363 | 0134 | | B | TS 38.307 big CR for NR_ENDC_RF_FR1_enh2 | 18.0.0 | +| 2023-12 | RAN#102 | RP-233366 | 0135 | | B | CR to TS38.307: the introduction of NR bands n31 and n72 | 18.0.0 | +| 2023-12 | RAN#102 | RP-233332 | 0138 | | A | [NR_newRAT-Core] Common UE RF requirements for 4Rx | 18.0.0 | +| 2023-12 | RAN#102 | RP-233370 | 0139 | 1 | B | Release independent for 3Tx band combination | 18.0.0 | +| 2023-12 | RAN#102 | RP-233370 | 0146 | | B | CR to 38.307 Release independent requirements for 1Tx-2Tx switching and 2Tx-2Tx switching | 18.0.0 | +| 2023-12 | RAN#102 | RP-233366 | 0147 | | B | CR for adding RedCap UE for release independent feature | 18.0.0 | +| 2023-12 | RAN#102 | RP-233349 | 0145 | 1 | F | [NR_NTN_solutions-Core] CR to TS 38.307: release independent requirements for NTN FR1, Rel-17 | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38314/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38314/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6030e0f6afe4951e2992dfdf7081fc3aa8352c7 --- /dev/null +++ b/marked/Rel-18/38_series/38314/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e2c2bf3b9ace032e56f0a696f88c5c51a343b353f9710d42bbc72e6a384d596 +size 7653 diff --git a/marked/Rel-18/38_series/38314/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38314/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..49e39661cdc88434de6345b07ed9acbd843fccbf --- /dev/null +++ b/marked/Rel-18/38_series/38314/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df91f7ec4675ae4d1bf7a30a97d626984ea9afe26f7961f222001c369bed833c +size 5766 diff --git a/marked/Rel-18/38_series/38314/raw.md b/marked/Rel-18/38_series/38314/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e602a8bc78e2aa3bd2e6b6167a4444a43f511fa0 --- /dev/null +++ b/marked/Rel-18/38_series/38314/raw.md @@ -0,0 +1,1125 @@ + + +# 3GPP TS 38.314 V18.0.0 (2024-03) + +*Technical Specification|Report* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Layer 2 Measurements; (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 bold, black, stylized font. The "G" and "P" are connected by a red curved line at the bottom, resembling a signal wave. + +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 ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions of terms, symbols and abbreviations..... | 6 | +| 3.1 Terms..... | 6 | +| 3.2 Abbreviations ..... | 6 | +| 4 Layer 2 measurements ..... | 6 | +| 4.1 General ..... | 6 | +| 4.2 NR measurements performed by the gNB ..... | 7 | +| 4.2.1 Measurements valid for all gNB deployment scenarios..... | 7 | +| 4.2.1.1 Received Random Access Preambles ..... | 7 | +| 4.2.1.1.1 Received Random Access Preambles per cell..... | 7 | +| 4.2.1.1.1a Received 4-step Random Access Preambles per cell..... | 7 | +| 4.2.1.1.1b Received 2-step Random Access Preambles per cell..... | 7 | +| 4.2.1.1.2 Received Random Access Preambles per SSB ..... | 8 | +| 4.2.1.1.2a Received 4-step Random Access Preambles per SSB ..... | 8 | +| 4.2.1.1.2b Received 2-step Random Access Preambles per SSB ..... | 8 | +| 4.2.1.2 Packet delay ..... | 9 | +| 4.2.1.2.1 General ..... | 9 | +| 4.2.1.2.2 Average over-the-air interface packet delay in the UL per DRB per UE ..... | 10 | +| 4.2.1.2.3 Average RLC packet delay in the UL per DRB per UE ..... | 10 | +| 4.2.1.2.4 Average PDCP re-ordering delay in the UL per DRB per UE..... | 11 | +| 4.2.1.3 Number of active UEs in RRC_CONNECTED ..... | 11 | +| 4.2.1.3.1 General ..... | 11 | +| 4.2.1.3.2 Mean number of Active UEs in the DL per DRB per cell..... | 11 | +| 4.2.1.3.3 Max number of Active UEs in the DL per DRB per cell..... | 12 | +| 4.2.1.3.4 Mean number of Active UEs in the UL per DRB per cell..... | 13 | +| 4.2.1.3.5 Max number of Active UEs in the UL per DRB per cell..... | 13 | +| 4.2.1.3.6 Mean number of Active UEs per cell..... | 14 | +| 4.2.1.3.7 Max number of Active UEs per cell..... | 15 | +| 4.2.1.3.8 Mean number of Active UEs per DRB per cell ..... | 15 | +| 4.2.1.3.9 Max number of Active UEs per DRB per cell ..... | 16 | +| 4.2.1.4 Number of stored inactive UE contexts ..... | 17 | +| 4.2.1.4.1 General ..... | 17 | +| 4.2.1.4.2 Mean number of stored inactive UE contexts ..... | 17 | +| 4.2.1.4.3 Max number of stored inactive UE contexts..... | 18 | +| 4.2.1.5 Packet Loss Rate..... | 18 | +| 4.2.1.5.1 Packet Uu Loss Rate in the DL per DRB per UE ..... | 18 | +| 4.2.1.5.2 Packet Uu Loss Rate with delay threshold in the DL per DRB per UE..... | 19 | +| 4.2.1.6 Other measurements defined in TS 28.552 [2] ..... | 20 | +| 4.2.1.7.3 PDSCH PRB Usage based on statistical MIMO layer in the DL per cell..... | 22 | +| 4.2.1.7.4 PUSCH PRB Usage based on statistical MIMO layer in the UL per cell..... | 23 | +| 4.2.1.7.5 Enhanced PDSCH PRB Usage for MIMO in the DL per cell ..... | 24 | +| 4.2.1.7.6 Enhanced PUSCH PRB Usage for MIMO in the UL per cell ..... | 25 | +| 4.2.1.8 Number of PDCP Packets in Split-DRB Scenario..... | 26 | +| 4.2.1.8.1 Number of PDCP Non-duplicated Packets per cell group per Split-DRB per UE ..... | 26 | +| 4.2.1.8.2 Number of PDCP duplicated Packets per Split-DRB per UE..... | 26 | +| 4.2.1.9 Total RAN Delay in Split-DRB Scenario..... | 27 | +| 4.2.1.9.1 DL Delay Calculation per Split-DRB per UE when PDCP duplication is enabled for entire measurement period ..... | 27 | +| 4.2.1.9.2 UL Delay Calculation per Split-DRB per UE when PDCP duplication is enabled for entire measurement period ..... | 27 | +| 4.2.1.9.3 DL Delay Calculation per Split-DRB per UE when PDCP duplication is not enabled for entire measurement period ..... | 28 | + +- 4.2.1.9.4 UL Delay Calculation per Split-DRB per UE when PDCP duplication is not enabled for entire measurement period ..... 29 +- 4.2.1.10 PDCCH CCE Usage ..... 30 +- 4.2.1.10.1 PDCCH CCE Usage per cell..... 30 +- 4.3 NR measurements performed by the UE..... 30 +- 4.3.1 Packet delay..... 30 +- 4.3.1.1 UL PDCP Packet Average Delay per DRB per UE ..... 30 +- 4.3.1.2 UL PDCP Excess Packet Delay per DRB ..... 31 +- 4.3.1.2.1 Measurement report mapping for PDCP Excess Packet Delay..... 32 +- Annex A (informative): Change history..... 34** + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document contains the description and definition of the measurements performed by network or the UE that are transferred over the standardised interfaces in order to support NR radio link operations, radio resource management (RRM), network operations and maintenance (OAM), minimization of drive tests (MDT) and self-organising networks (SON). + +Only the differences relative to TS 28.552 v16.2.0 [2] are specified in this specification. + +# --- 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 28.552: "5G performance measurements". +- [3] 3GPP TS 38.331: "Radio Resource Control (RRC) protocol specification". +- [4] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2". + +# --- 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 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 Layer 2 measurements + +## 4.1 General + +All the per DRB per cell measurements and per DRB per UE measurements can be aggregated into per QoS level per cell and per PLMN ID per cell by network implementation. All the performance measurements for gNB defined in TS 28.552 [2] 5.1 can be calculated into per PLMN ID level by network implementation. Per QoS level refers to per mapped 5QI for NR SA or per QCI for EN-DC. + +## 4.2 NR measurements performed by the gNB + +### 4.2.1 Measurements valid for all gNB deployment scenarios + +#### 4.2.1.1 Received Random Access Preambles + +##### 4.2.1.1.1 Received Random Access Preambles per cell + +A use case for this measurement is RACH configuration optimization, where Received Random Access Preambles is signalled across an OAM interface. + +Protocol Layer: MAC + +**Table 4.2.1.1.1-1: Definition for Received Random Access Preambles per cell** + +| | | +|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Received Random Access Preambles per cell. This measurement is applicable to PRACH. The reference point is the Service Access Point between MAC and L1. The measured quantity is the number of received Random Access preambles during a time period over all PRACHs configured in a cell. The measurement is done separately for:
  • - Dedicated preambles
  • - Randomly selected preambles in the low range
  • - Randomly selected preambles in the high range.
The unit of the measured value is [/s]. | +|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +##### 4.2.1.1.1a Received 4-step Random Access Preambles per cell + +A use case for this measurement is RACH configuration optimization, where Received Random Access Preambles is signalled across an OAM interface. + +Protocol Layer: MAC + +**Table 4.2.1.1.1a-1: Definition for Received 4-step Random Access Preambles per cell** + +| | | +|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Received 4-step Random Access Preambles per cell. This measurement is applicable to PRACH. The reference point is the Service Access Point between MAC and L1. The measured quantity is the number of received Random Access preambles of 4-step RA attempts during a time period over all PRACHs configured in a cell. The measurement is done separately for:
  • - Dedicated preambles
  • - Randomly selected preambles in the low range
  • - Randomly selected preambles in the high range.
The unit of the measured value is [/s]. | +|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +##### 4.2.1.1.1b Received 2-step Random Access Preambles per cell + +A use case for this measurement is RACH configuration optimization, where Received Random Access Preambles is signalled across an OAM interface. + +Protocol Layer: MAC + +**Table 4.2.1.1.1b-1: Definition for Received 2-step Random Access Preambles per cell** + +| | | +|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Received 2-step Random Access Preambles per cell. This measurement is applicable to PRACH. The reference point is the Service Access Point between MAC and L1. The measured quantity is the number of received Random Access preambles of 2-step RA attempts during a time period over all PRACHs configured in a cell. The measurement is done separately for:
  • - Dedicated preambles
  • - Randomly selected preambles in the low range
  • - Randomly selected preambles in the high range.
The unit of the measured value is [/s]. | +|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +##### 4.2.1.1.2 Received Random Access Preambles per SSB + +A use case for this measurement is RACH configuration optimization, where Received Random Access Preambles is signalled across an OAM interface. + +Protocol Layer: MAC + +**Table 4.2.1.1.2-1: Definition for Received Random Access Preambles per SSB** + +| | | +|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Received Random Access Preambles per SSB. This measurement is applicable to PRACH. The reference point is the Service Access Point between MAC and L1. The measured quantity is the number of received Random Access preambles during a time period over all PRACHs configured in the SSB of the cell. The measurement is done separately for:
  • - Dedicated preambles
  • - Randomly selected preambles in the low range
  • - Randomly selected preambles in the high range.
The unit of the measured value is [/s]. | +|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +###### 4.2.1.1.2a Received 4-step Random Access Preambles per SSB + +A use case for this measurement is RACH configuration optimization, where Received Random Access Preambles is signalled across an OAM interface. + +Protocol Layer: MAC + +**Table 4.2.1.1.2a-1: Definition for Received 4-step Random Access Preambles per SSB** + +| | | +|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Received 4-step Random Access Preambles per SSB. This measurement is applicable to PRACH. The reference point is the Service Access Point between MAC and L1. The measured quantity is the number of received Random Access preambles of 4-step RA attempts during a time period over all PRACHs configured in the SSB of the cell. The measurement is done separately for:
  • - Dedicated preambles
  • - Randomly selected preambles in the low range
  • - Randomly selected preambles in the high range.
The unit of the measured value is [/s]. | +|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +##### 4.2.1.1.2b Received 2-step Random Access Preambles per SSB + +A use case for this measurement is RACH configuration optimization, where Received Random Access Preambles is signalled across an OAM interface. + +Protocol Layer: MAC + +**Table 4.2.1.1.2b-1: Definition for Received 2-step Random Access Preambles per SSB** + +| | | +|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

Received 2-step Random Access Preambles per SSB. This measurement is applicable to PRACH. The reference point is the Service Access Point between MAC and L1. The measured quantity is the number of received Random Access preambles of 2-step RA attempts during a time period over all PRACHs configured in the SSB of the cell. The measurement is done separately for:

  • - Dedicated preambles
  • - Randomly selected preambles in the low range
  • - Randomly selected preambles in the high range.

The unit of the measured value is [/s].

| +|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +#### 4.2.1.2 Packet delay + +##### 4.2.1.2.1 General + +Packet delay includes RAN part of delay and CN part of delay. + +The RAN part of DL packet delay measurement comprises: + +- D1 (DL delay in over-the-air interface), referring to Average delay DL air-interface in TS 28.552 [2] 5.1.1.1.1. +- D2 (DL delay on gNB-DU), referring to Average delay in RLC sublayer of gNB-DU in TS 28.552 [2] 5.1.3.3.3. +- D3 (DL delay on F1-U), referring to Average delay on F1-U in TS 28.552 [2] 5.1.3.3.2. +- D4 (DL delay in CU-UP), referring to Average delay DL in CU-UP in TS 28.552 [2] 5.1.3.3.1. + +The DL packet delay measurements, i.e. D1 (the DL delay in over-the-air interface ), D2 (the DL delay in gNB-DU), D3 (the DL delay on F1-U) and D4 (the DL delay in CU-UP), should be measured per DRB per UE. + +NOTE: The delay measurements D1, D2 and D4 are also applicable for EUTRA in case of EN-DC related DL delay measurements on the MN side. + +The RAN part (including UE) of UL packet delay measurement comprises: + +- D1 (UL PDCP packet average delay, as defined in clause 4.3.1.1). +- D2.1 (average over-the-air interface packet delay, as defined in 4.2.1.2.2). +- D2.2 (average RLC packet delay, as defined in 4.2.1.2.3). +- D2.3 (average delay UL on F1-U, it is measured using the same metric as the average delay DL on F1-U defined in TS 28.552 [2] clause 5.1.3.3.2). +- D2.4 (average PDCP re-ordering delay, as defined in 4.2.1.2.4). + +The UL packet delay measurements, i.e. D1(UL PDCP packet average delay), D2.1(average over-the-air interface packet delay), D2.2(average RLC packet delay), D2.3(average delay UL on F1-U) and D2.4(average PDCP re-ordering delay), should be measured per DRB per UE. The unit of D1, D2.1, D2.2, D2.3 and D2.4 is 0.1ms. + +NOTE: The delay measurements D1, D2.1, D2.2 and D2.4 are also applicable for EUTRA in case of EN-DC related UL delay measurements on the MN side. + +For non CU-UP and DU split case, RAN part of packet delay excludes the delay at FI-U interface, i.e. D2.3 and D3. + +For split-DRB scenario, total UL/DL delay on the MCG or on the SCG is calculated based on the above measurement definitions. For UL delay calculation, the D1 measurement is the same for total UL delay on the MCG and total UL delay on the SCG. + +If network disables the PDCP re-ordering function, the value of Average PDCP re-ordering delay i.e. D2.4 should be set to 0. + +For the QoS monitoring in TS 23.501 [4], RAN informs the RAN part of UL packet delay measurement, or the RAN part of DL packet delay measurement, or both to the CN. + +##### 4.2.1.2.2 Average over-the-air interface packet delay in the UL per DRB per UE + +The objective of this measurement is to measure air interface UL packet delay for OAM performance observability or for QoS verification of MDT or for the QoS monitoring as defined in TS 23.501 [4]. + +Protocol Layer: MAC + +**Table 4.2.1.2.2-1: Definition for Average over-the-air packet delay in the UL per DRB per UE** + +| | | +|------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

Average over-the-air packet delay in the UL per DRB per UE. This measurement is applicable for EN-DC and SA. This measurement refers to packet delay for DRBs. This measurement provides the average (arithmetic mean) time it takes to successfully receive a transport block from the time of UL transmission indicated in scheduling grant.

Detailed Definition:

$M(T, drbid) = \left\lfloor \frac{\sum_{\forall i \in I(T)} (tSucc(i, drbid) - tSched(i, drbid))}{I(T)} \right\rfloor, \text{ where}$

explanations can be found in the table 4.2.1.2.2-2 below.

| +|------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 4.2.1.2.2-2: Parameter description for Average over-the-air packet delay in the UL per DRB per UE** + +| | | +|--------------------|----------------------------------------------------------------------------------------------------------------| +| $M(T, drbid)$ | Over-the-air packet delay in the UL per DRB per UE, averaged during time period T . Unit: 0.1 ms. | +| $tSched(i, drbid)$ | The point in time when the UL MAC SDU i is scheduled in MAC layer as per the scheduling grant provided. | +| $tSucc(i, drbid)$ | The point in time when the UL MAC SDU i is successfully sent to RLC. | +| $i$ | A UL MAC SDU that arrives at the MAC during time period T . | +| $I(T)$ | Total number of UL MAC SDUs i . | +| $T$ | Time Period during which the measurement is performed | +| $drbid$ | The identity of the measured DRB. | + +##### 4.2.1.2.3 Average RLC packet delay in the UL per DRB per UE + +The objective of this measurement is to measure RLC delay in the UL for OAM performance observability or for QoS verification of MDT or for the QoS monitoring as defined in TS 23.501 [4]. + +Protocol Layer: RLC + +**Table 4.2.1.2.3-1: Definition for Average RLC packet delay in the UL per DRB per UE** + +| | | +|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

Average RLC delay in the UL per DRB per UE. This measurement is applicable for EN-DC and SA. This measurement refers to packet delay for DRBs. For CU-UP and DU split scenario or DC scenario, this measurement refers to the RLC delay on each DU or RAN node. This measurement provides the average (arithmetic mean) time it takes from the RLC PDU including the first part of an RLC SDU is received to the RLC SDU is sent to PDCP or CU-UP for split gNB.

Detailed Definition:

$M(T, drbid) = \left\lfloor \frac{\sum_{\forall i \in I(T)} (tSent(i, drbid) - tReceiv(i, drbid))}{I(T)} \right\rfloor, \text{ where}$

explanations can be found in the table 4.2.1.2.3-2 below.

| +|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 4.2.1.2.3-2: Parameter description for Average RLC packet delay in the UL per DRB per UE** + +| | | +|---------------------|---------------------------------------------------------------------------------------------------| +| $M(T, drbid)$ | RLC delay in the UL per DRB per UE, averaged during time period $T$ . Unit: 0.1 ms. | +| $tReceiv(i, drbid)$ | The point in time when the UL RLC PDU including the first part of the UL RLC SDU $i$ is received. | +| $tSent(i, drbid)$ | The point in time when the UL RLC SDU $i$ is sent to PDCP or CU-UP for split gNB. | +| $i$ | A UL RLC SDU that is received by the RLC during time period $T$ . | +| $I(T)$ | Total number of UL RLC SDUs $i$ . | +| $T$ | Time Period during which the measurement is performed | +| $drbid$ | The identity of the measured DRB. | + +##### 4.2.1.2.4 Average PDCP re-ordering delay in the UL per DRB per UE + +The objective of this measurement is to measure PDCP re-ordering delay in the UL for OAM performance observability or for QoS verification of MDT or for the QoS monitoring as defined in TS 23.501 [4]. + +Protocol Layer: PDCP + +**Table 4.2.1.2.4-1: Definition for Average PDCP re-ordering delay in the UL per DRB per UE** + +| | | +|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

Average PDCP re-ordering delay in the UL per DRB per UE. This measurement is applicable for EN-DC and SA. This measurement refers to packet delay for DRBs. This measurement provides the average (arithmetic mean) time it takes from the point a PDCP PDU is received to the PDCP SDU is sent to upper SAP.

Detailed Definition:
M(T, drbid) = \left[ \frac{\sum_{i} tSent(i, drbid) - tReceiv(i, drbid)}{I(T)} \right], where explanations can be found in the table 4.1.1.2.4-2 below.

| +|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 4.2.1.2.4-2: Parameter description for Average PDCP re-ordering delay in the UL per DRB per UE** + +| | | +|---------------------|--------------------------------------------------------------------------------------------------| +| $M(T, drbid)$ | PDCP re-ordering delay in the UL per DRB per UE, averaged during time period $T$ . Unit: 0.1 ms. | +| $tReceiv(i, drbid)$ | The point in time when the UL PDCP PDU including the UL PDCP SDU $i$ is received. | +| $tSent(i, drbid)$ | The point in time when the UL PDCP SDU $i$ is sent to upper SAP. | +| $i$ | A UL PDCP SDU that is received by the PDCP during time period $T$ . | +| $I(T)$ | Total number of UL PDCP SDUs received during time period $T$ . | +| $T$ | Time Period during which the measurement is performed | +| $drbid$ | The identity of the measured DRB. | + +#### 4.2.1.3 Number of active UEs in RRC\_CONNECTED + +##### 4.2.1.3.1 General + +The objective of the measurement is to measure the number of active UEs per QoS level for OAM performance observability or for SON functions e.g., mobility load balancing. It is intended to be part of a calculation to determine the bitrate UEs achieve when they are active, i.e. when applications are transmitting and receiving data. The measurements are applicable for both non-split gNB and split gNB deployment scenario. + +##### 4.2.1.3.2 Mean number of Active UEs in the DL per DRB per cell + +Protocol Layer: MAC, RLC + +**Table 4.2.1.3.2-1: Definition for Mean number of Active UEs in the DL per DRB per cell** + +| | | +|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Mean number of Active UEs in the DL per DRB per cell. The DRBs are mapped with the same 5QI for NR SA or mapped with the same QCI for EN-DC. This measurement refers to UEs for which there is data available for transmission for the DL for DRBs.
Detailed Definition:
$M(T, drbid, p) = \frac{\left[ \frac{\sum_{i=1}^{I(T,p)} N(i, drbid)}{I(T,p)} \times 10 \right]}{10}$ , where explanations can be found in the table 4.2.1.3.2-2 below. | +|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 4.2.1.3.2-2: Parameter description for Mean number of Active UEs in the DL per DRB per cell** + +| | | +|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $M(T, drbid, p)$ | Mean number of Active UEs in the DL per DRB per cell, averaged during time period $T$ . Unit: 0.1. | +| $N(i, drbid)$ | Number of UEs for which there is data available for transmission for the DL in MAC or RLC protocol layers for a Data Radio Bearer of traffic class at sampling occasion $i$ . Data available for transmission includes data for which HARQ transmission has not yet terminated. | +| $i$ | Sampling occasion during time period $T$ . A sampling occasion shall occur once every $p$ seconds. | +| $p$ | Sampling period length. Unit: second. The sampling period shall be at most 0.1 s. | +| $I(T, p)$ | Total number of sampling occasions during time period $T$ . | +| $T$ | Time Period during which the measurement is performed, Unit: second. | +| $drbid$ | The DRBs mapped with the same 5QI for NR SA or mapped with the same QCI for EN-DC. | + +##### 4.2.1.3.3 Max number of Active UEs in the DL per DRB per cell + +Protocol Layer: MAC, RLC + +**Table 4.2.1.3.3-1: Definition for Max number of Active UEs in the DL per DRB per cell** + +| | | +|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Maximum number of Active UEs in the DL per DRB per cell. The DRBs are mapped with the same 5QI for NR SA or mapped with the same QCI for EN-DC. This measurement refers to UEs for which there is data available for transmission for the DL for DRBs.
Detailed Definition:
$M(T, drbid, p) = \max_T(N(i, drbid))$ , where explanations can be found in the table 4.2.1.3.3-2 below. | +|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 4.2.1.3.3-2: Parameter description for Max number of Active UEs in the DL per DRB per cell** + +| | | +|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $M(T, drbid, p)$ | Maximum number of Active UEs in the DL per DRB per cell, averaged during time period $T$ . Unit: Integer. | +| $N(i, drbid)$ | Number of UEs for which there is data available for transmission for the DL in MAC or RLC protocol layers for a Data Radio Bearer of traffic class at sampling occasion $i$ . Data available for transmission includes data for which HARQ transmission has not yet terminated. | +| $i$ | Sampling occasion during time period $T$ . A sampling occasion shall occur once every $p$ seconds. | +| $p$ | Sampling period length. Unit: second. The sampling period shall be at most 0.1 s. | +| $T$ | Time Period during which the measurement is performed, Unit: second. | +| $drbid$ | The DRBs mapped with the same 5QI for NR SA or mapped with the same QCI for EN-DC. | + +##### 4.2.1.3.4 Mean number of Active UEs in the UL per DRB per cell + +Protocol Layer: MAC + +**Table 4.2.1.3.4-1: Definition for Mean number of Active UEs in the UL per DRB per cell** + +| | | +|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Mean number of Active UEs in the UL per DRB per cell. The DRBs are mapped with the same 5QI for NR SA or mapped with the same QCI for EN-DC. This measurement refers to UEs for which there is data available for transmission for the UL for DRBs.
Detailed Definition:
$M(T, drbid, p) = \frac{\left[ \frac{\sum_{i \in I(T,p)} N(i, drbid)}{I(T,p)} \times 10 \right]}{10}$ , where explanations can be found in the table 4.2.1.3.4-2 below. | +|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +NOTE: For this measurement, the expected accuracy is dependent on application scenario, cell load, UE configuration and how DRBs are distributed over logical channel groups. + +**Table 4.2.1.3.4-2: Parameter description for Mean number of Active UEs in the UL per DRB per cell** + +| | | +|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $M(T, drbid, p)$ | Mean number of Active UEs in the UL per DRB per cell, averaged during time period $T$ . Unit: 0.1. | +| $N(i, drbid)$ | Number of UEs for which there is data available for transmission for the UL in MAC or RLC protocol layers for a Data Radio Bearer of traffic class at sampling occasion $i$ . This is a gNB estimation that is expected to be based on Buffer Status Reporting, provided configured grants and progress of ongoing HARQ transmissions (by including data for which HARQ transmission has not yet terminated). In addition, the gNB can use the analysis of received data in the estimation. In such case, when DRB cannot be determined at the time of the sampling occasion, gNB can determine DRB after successful reception of data. | +| $i$ | Sampling occasion during time period $T$ . A sampling occasion shall occur once every $p$ seconds. | +| $p$ | Sampling period length. Unit: second. The sampling period shall be at most 0.1 s. | +| $I(T, p)$ | Total number of sampling occasions during time period $T$ . | +| $T$ | Time Period during which the measurement is performed, Unit: second. | +| $drbid$ | The DRBs mapped with the same 5QI for NR SA or mapped with the same QCI for EN-DC. | + +##### 4.2.1.3.5 Max number of Active UEs in the UL per DRB per cell + +Protocol Layer: MAC + +**Table 4.2.1.3.5-1: Definition for Max number of Active UEs in the UL per DRB per cell** + +| | | +|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Maximum number of Active UEs in the UL per DRB per cell. The DRBs are mapped with the same 5QI for NR SA or mapped with the same QCI for EN-DC. This measurement refers to UEs for which there is data available for transmission for the UL for DRBs.
Detailed Definition:
$M(T, drbid, p) = \max_T (N(i, drbid))$ , where explanations can be found in the table 4.2.1.3.5-2 below. | +|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +NOTE: For this measurement, the expected accuracy is dependent on application scenario, cell load, UE configuration and how DRBs are distributed over logical channel groups. + +**Table 4.2.1.3.5-2: Parameter description for Max number of Active UEs in the UL per DRB per cell** + +| | | +|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $M(T, drbid, p)$ | Maximum number of Active UEs in the UL per DRB per cell, averaged during time period $T$ . Unit: Integer. | +| $N(i, drbid)$ | Number of UEs for which there is data available for transmission for the UL in MAC or RLC protocol layers for a Data Radio Bearer of traffic class at sampling occasion $i$ . This is a gNB estimation that is expected to be based on Buffer Status Reporting, provided configured grants and progress of ongoing HARQ transmissions (by including data for which HARQ transmission has not yet terminated). In addition, the gNB can use the analysis of received data in the estimation. In such case, when DRB cannot be determined at the time of the sampling occasion, gNB can determine DRB after successful reception of data. | +| $i$ | Sampling occasion during time period $T$ . A sampling occasion shall occur once every $p$ seconds. | +| $p$ | Sampling period length. Unit: second. The sampling period shall be at most 0.1 s. | +| $T$ | Time Period during which the measurement is performed, Unit: second. | +| $drbid$ | The DRBs mapped with the same 5QI for NR SA or mapped with the same QCI for EN-DC. | + +##### 4.2.1.3.6 Mean number of Active UEs per cell + +Protocol Layer: MAC, RLC + +**Table 4.2.1.3.6-1: Definition for Mean number of Active UEs per cell** + +| | | +|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Mean number of Active UEs per cell. This measurement refers to UEs for which there is data available for transmission for the UL for DRBs, or there is data available for transmission for the DL for DRBs, or both.
Detailed Definition:
$M(T, p) = \frac{\left[ \frac{\sum_{i=1}^{I(T,p)} N(i)}{I(T,p)} \times 10 \right]}{10}$ , where explanations can be found in the table 4.2.1.3.6-2 below. | +|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +NOTE: For this measurement, the expected accuracy is dependent on application scenario, cell load, UE configuration and how DRBs are distributed over logical channel groups. + +**Table 4.2.1.3.6-2: Parameter description for Mean number of Active UEs per cell** + +| | | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $M(T, p)$ | Mean number of Active UEs per cell, averaged during time period $T$ . Unit: 0.1. | +| $N(i)$ | Number of UEs for which there is data available for transmission for the UL or for the DL or for both in MAC or RLC protocol layers at sampling occasion $i$ . For UL, this is a gNB estimation that is expected to be based on Buffer Status Reporting, provided configured grants and progress of ongoing HARQ transmissions (by including data for which HARQ transmission has not yet terminated). In addition, the gNB can use the analysis of received data in the estimation. | +| $i$ | Sampling occasion during time period $T$ . A sampling occasion shall occur once every $p$ seconds. | +| $p$ | Sampling period length. Unit: second. The sampling period shall be at most 0.1 s. | +| $I(T, p)$ | Total number of sampling occasions during time period $T$ . | +| $T$ | Time Period during which the measurement is performed, Unit: second. | + +##### 4.2.1.3.7 Max number of Active UEs per cell + +Protocol Layer: MAC, RLC + +**Table 4.2.1.3.7-1: Definition for Max number of Active UEs per cell** + +| | | +|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Maximum number of Active UEs per cell. This measurement refers to UEs for which there is data available for transmission for the UL for DRBs, or there is data available for transmission for the DL for DRBs, or both.
Detailed Definition:
$M(T, p) = \max_T(N(i))$ , where explanations can be found in the table 4.2.1.3.7-2 below. | +|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +NOTE: For this measurement, the expected accuracy is dependent on application scenario, cell load, UE configuration and how DRBs are distributed over logical channel groups. + +**Table 4.2.1.3.7-2: Parameter description for Max number of Active UEs per cell** + +| | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $M(T, p)$ | Maximum number of Active UEs per cell, averaged during time period $T$ . Unit: Integer. | +| $N(i)$ | Number of UEs for which there is data available for transmission for the UL or for the DL or for both in MAC or RLC protocol layers at sampling occasion $i$
For UL, this is a gNB estimation that is expected to be based on Buffer Status Reporting, provided configured grants and progress of ongoing HARQ transmissions (by including data for which HARQ transmission has not yet terminated). In addition, the gNB can use the analysis of received data in the estimation. | +| $i$ | Sampling occasion during time period $T$ . A sampling occasion shall occur once every $p$ seconds. | +| $p$ | Sampling period length. Unit: second. The sampling period shall be at most 0.1 s. | +| $T$ | Time Period during which the measurement is performed, Unit: second. | + +##### 4.2.1.3.8 Mean number of Active UEs per DRB per cell + +Protocol Layer: MAC, RLC + +**Table 4.2.1.3.8-1: Definition for Mean number of Active UEs per DRB per cell** + +| | | +|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Mean number of Active UEs per DRB per cell. The DRBs are mapped with the same 5QI for NR SA or mapped with the same QCI for EN-DC. This measurement refers to UEs for which there is data available for transmission for the UL for DRBs, or there is data available for transmission for the DL for DRBs, or both.
Detailed Definition:
$M(T, drbid, p) = \frac{\frac{\sum_{i \in I(T,p)} N(i, drbid)}{10} \times 10}{10}$ , where explanations can be found in the table 4.2.1.3.8-2 below. | +|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +NOTE: For this measurement, the expected accuracy is dependent on application scenario, cell load, UE configuration and how DRBs are distributed over logical channel groups. + +**Table 4.2.1.3.8-2: Parameter description for Mean number of Active UEs per DRB per cell** + +| | | +|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $M(T, drbid, p)$ | Mean number of Active UEs per DRB per cell, averaged during time period $T$ . Unit: 0.1. | +| $N(i, drbid)$ | Number of UEs for which there is data available for transmission for the UL or for the DL or for both in MAC or RLC protocol layers for a Data Radio Bearer of traffic class at sampling occasion $i$
For UL, this is a gNB estimation that is expected to be based on Buffer Status Reporting, provided configured grants and progress of ongoing HARQ transmissions (by including data for which HARQ transmission has not yet terminated). In addition, the gNB can use the analysis of received data in the estimation. In such case, when DRB cannot be determined at the time of the sampling occasion, gNB can determine DRB after successful reception of data. | +| $i$ | Sampling occasion during time period $T$ . A sampling occasion shall occur once every $p$ seconds. | +| $p$ | Sampling period length. Unit: second. The sampling period shall be at most 0.1 s. | +| $I(T, p)$ | Total number of sampling occasions during time period $T$ . | +| $T$ | Time Period during which the measurement is performed, Unit: second. | +| $drbid$ | The DRBs mapped with the same 5QI for NR SA or mapped with the same QCI for EN-DC. | + +##### 4.2.1.3.9 Max number of Active UEs per DRB per cell + +Protocol Layer: MAC, RLC + +**Table 4.2.1.3.9-1: Definition for Max number of Active UEs per DRB per cell** + +| | | +|------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Maximum number of Active UEs per DRB per cell. The DRBs are mapped with the same 5QI for NR SA or mapped with the same QCI for EN-DC. This measurement refers to UEs for which there is data available for transmission for the UL for DRBs, or there is data available for transmission for the DL for DRBs, or both.
Detailed Definition:
$M(T, drbid, p) = \max_T(N(i, drbid))$ , where explanations can be found in the table 4.2.1.3.9-1 below. | +|------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +NOTE: For this measurement, the expected accuracy is dependent on application scenario, cell load, UE configuration and how DRBs are distributed over logical channel groups. + +**Table 4.2.1.3.9-2: Parameter description for Max number of Active UEs per DRB per cell** + +| | | +|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $M(T, drbid, p)$ | Maximum number of Active UEs per DRB per cell, averaged during time period $T$ . Unit: Integer. | +| $N(i, drbid)$ | Number of UEs for which there is data available for transmission for the UL or for the DL or for both in MAC or RLC protocol layers for a Data Radio Bearer of traffic class at sampling occasion $i$
For UL, this is a gNB estimation that is expected to be based on Buffer Status Reporting, provided configured grants and progress of ongoing HARQ transmissions (by including data for which HARQ transmission has not yet terminated). In addition, the gNB can use the analysis of received data in the estimation. In such case, when DRB cannot be determined at the time of the sampling occasion, gNB can determine DRB after successful reception of data. | +| $i$ | Sampling occasion during time period $T$ . A sampling occasion shall occur once every $p$ seconds. | +| $p$ | Sampling period length. Unit: second. The sampling period shall be at most 0.1 s. | +| $T$ | Time Period during which the measurement is performed, Unit: second. | +| $drbid$ | The DRBs mapped with the same 5QI for NR SA or mapped with the same QCI for EN-DC. | + +#### 4.2.1.4 Number of stored inactive UE contexts + +##### 4.2.1.4.1 General + +The objective of the measurement is to measure number of stored inactive UE contexts for OAM performance observability. It is intended to be part of indication about the memory consumption in a RAN node. + +The measurement is obtained by sampling at a pre-defined interval, the number of inactive UE contexts for each gNB and then taking the arithmetic mean or maximum value over pre-defined time duration. + +##### 4.2.1.4.2 Mean number of stored inactive UE contexts + +Protocol Layer: RRC + +**Table 4.2.1.4.2-1: Definition for Mean number of stored inactive UE contexts** + +| | | +|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Mean number of stored inactive UE contexts.

Detailed Definition:
$M(T, p) = \left\lfloor \frac{\sum_{i \in I(T, p)} N(i)}{I(T, p)} \right\rfloor$ , where explanations can be found in the table 4.2.1.4.2-2 below. | +|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 4.2.1.4.2-2: Parameter description for Mean number of stored inactive UE contexts** + +| | | +|-----------|----------------------------------------------------------------------------------------------------| +| $M(T, p)$ | Mean number of stored Inactive UE contexts, averaged during time period $T$ . Unit: Integer. | +| $N(i)$ | Number of inactive UE contexts stored in the gNB at sampling occasion $i$ . | +| $i$ | Sampling occasion during time period $T$ . A sampling occasion shall occur once every $p$ seconds. | +| $p$ | Sampling period length. Unit: second. The sampling period shall be at most 0.1 s. | +| $I(T, p)$ | Total number of sampling occasions during time period $T$ . | +| $T$ | Time Period during which the measurement is performed, Unit: second. | + +##### 4.2.1.4.3 Max number of stored inactive UE contexts + +Protocol Layer: RRC + +**Table 4.2.1.4.3-1: Definition for Max number of stored inactive UE contexts** + +| | | +|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Maximum number of stored inactive UE contexts.
Detailed Definition:
$M(T, p) = \max_{T}(N(i))$ , where
explanations can be found in the table 4.2.1.4.3-2 below. | +|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 4.2.1.4.3-2: Parameter description for Max number of stored inactive UE contexts** + +| | | +|-----------|--------------------------------------------------------------------------------------------------------------| +| $M(T, p)$ | Maximum number of stored Inactive UE contexts sampled during time period T . Unit: Integer. | +| $N(i)$ | Number of inactive UE contexts stored in the gNB at sampling occasion i . | +| $i$ | Sampling occasion during time period T . A sampling occasion shall occur once every p seconds. | +| $p$ | Sampling period length. Unit: second. The sampling period shall be at most 0.1 s. | +| $T$ | Time Period during which the measurement is performed, Unit: second. | + +#### 4.2.1.5 Packet Loss Rate + +##### 4.2.1.5.1 Packet Uu Loss Rate in the DL per DRB per UE + +The objective of this measurement is to measure packets that are lost at Uu transmission, for OAM performance observability or for QoS verification of MDT. + +Protocol Layer: RLC + +**Table 4.2.1.5.1-1: Definition for Packet Uu Loss Rate in the DL per DRB per UE** + +| | | +|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Uu Packet Loss Rate in the DL per DRB per UE. One packet corresponds to one RLC SDU. The measurement is done separately per DRB.
Detailed Definition:
$M(T, drbid) = \left\lfloor \frac{Dloss(T, drbid) * 1000000}{N(T, drbid) + Dloss(T, drbid)} \right\rfloor$ , where
explanations can be found in the table 4.2.1.5.1-2 below. | +|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +NOTE 1: Packet loss is expected to be upper bounded by the PER (packet error rate, as defined in TS 23.501 [4]) of the DRB which takes values between $10^{-6}$ and $10^{-2}$ . The statistical accuracy of an individual packet loss rate measurement result is dependent on how many packets have been received, and thus the time for the measurement. + +NOTE 2: The granularity for Packet loss rate measurement is per DRB per UE, as defined in TS 28.552 [2]. + +**Table 4.2.1.5.1-2: Parameter description for Packet Uu Loss Rate in the DL per DRB per UE** + +| | | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $M(T, drbid)$ | Packet Loss Rate in the DL per DRB per UE. Unit: number of lost packets per transmitted packets per DRB * $10^6$ , Integer. | +| $Dloss(T, drbid)$ | Number of DL packets, of a data radio bearer with DRB Identity = drbid , for which at least a part has been transmitted over the air but not positively acknowledged, and it was decided during time period T that no more transmission attempts will be done. If transmission of a packet might continue in another cell, it shall not be included in this count. | +| $N(T, drbid)$ | Number of DL packets, of a data radio bearer with DRB Identity = drbid , which has been transmitted over the air and positively acknowledged during time period T . | +| $T$ | Time Period during which the measurement is performed, Unit: minutes. | +| $drbid$ | The identity of the measured DRB. | + +##### 4.2.1.5.2 Packet Uu Loss Rate with delay threshold in the DL per DRB per UE + +The objective of this measurement is to measure the DL packets loss including any packets not successfully transmitted or packets successfully received but delayed more than a delay threshold at Uu transmission, for OAM performance observability or for QoS verification of MDT. + +Protocol Layer: RLC + +**Table 4.2.1.5.2-1: Definition for Packet Uu Loss Rate with delay threshold in the DL per DRB per UE** + +| | | +|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Uu Packet Loss Rate with delay threshold in the DL per DRB per UE: One packet corresponds to one RLC SDU. The measurement is done separately per DRB.
Detailed definition:
$M\_dt(T, drbid) = \left\lfloor \frac{[Dloss(T, drbid) + Dexd(T, drbid)] * 1000000}{N\_dt(T, drbid) + Dloss(T, drbid) + Dexd(T, drbid)} \right\rfloor$ Where explanations can be found in the table 4.2.1.5.2-2 below. | +|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +NOTE 1: Packet loss rate with delay threshold can be used when the resource type of corresponding QoS Flow is Delay-critical GBR. It is expected to be upper bounded by the PER (packet error rate, as defined in TS 23.501[4]) of the DRB which takes values between $10^{-6}$ and $10^{-2}$ . The statistical accuracy of an individual packet loss rate measurement result is dependent on how many packets have been received, and thus the time for the measurement. + +NOTE 2: Delay threshold of this measurement can be determined by NW implementation (e.g. configured by OAM). + +NOTE 3: The granularity for Packet loss rate measurement with delay threshold is per DRB per UE. + +**Table 4.2.1.5.2-2: Parameter description for Packet Uu Loss Rate with delay threshold in the DL per DRB per UE** + +| | | +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $M\_dt(T, drbid)$ | Packet Loss Rate with delay threshold in the DL per DRB per UE. Unit: number of lost packets per transmitted packets per DRB * $10^6$ , Integer.
Lost packets here means the packets that delayed more than delay threshold or not successfully transmitted. | +| $Dloss(T, drbid)$ | Number of DL packets, of a data radio bearer with DRB Identity = $drbid$ , for which at least a part has been transmitted over the air but not positively acknowledged, and it was decided during time period $T$ that no more transmission attempts will be done. If transmission of a packet might continue in another cell, it shall not be included in this count. | +| $Dexd(T, drbid)$ | Number of DL packets, of a data radio bearer with DRB Identity = $drbid$ , for which is transmitted over air interface and positively acknowledged but the DL delay of the RLC SDU is more than corresponding delay threshold during time period $T$ .
The DL delay of a RLC SDU is calculated as follows "point in time when the last part of an RLC SDU packet was sent to the UE which was consequently confirmed by reception of HARQ ACK from UE for UM mode or point in time when the last part of an RLC SDU packet was sent to the UE which was consequently confirmed by reception of RLC ACK for AM mode, minus time when corresponding RLC SDU part arriving at MAC layer".
The delay threshold is as defined in Note 2. | +| $N\_dt(T, drbid)$ | Number of DL packets, of a data radio bearer with DRB Identity = $drbid$ , which has been transmitted over the air and positively acknowledged and delayed no more than the corresponding delay threshold during time period $T$ .
The delay threshold is as defined in Note 2. | +| $T$ | Time Period during which the measurement is performed, Unit: minutes. | +| $drbid$ | The identity of the measured DRB. | + +#### 4.2.1.6 Other measurements defined in TS 28.552 [2] + +The granularity for PDCP SDU Data Volume measurement defined in TS 28.552 [2] is per DRB per UE. + +The granularity for Average UE throughput measurement defined in TS 28.552 [2] is per UE and per DRB per UE. + +PRB usage measurements are defined in TS 28.552 [2], i.e. DL/UL Total PRB Usage, Distribution of DL/UL Total PRB Usage. $M(T)$ , $M1(T)$ , $P(T)$ are measured per cell. $P(T)$ is the total available PRBs for this cell. $M1(T)$ is the PRBs used for traffic transmission in this cell. Counting unit for PRB usage measurement is 1 Resource Block x 1 symbol. (1 Resource Block = 12 sub-carrier). + +#### 4.2.1.7 PRB Usage for MIMO + +##### 4.2.1.7.1 PDSCH PRB Usage for MIMO in the DL per cell + +This measurement provides the total usage (in percentage) of PDSCH physical resource blocks (PRBs) for MIMO in the downlink per cell. The objective of the measurement is to measure usage of time and frequency resources. A use-case is OAM performance observability. + +Protocol Layer: MAC, PHY + +**Table 4.2.1.7.1-1: Definition for PDSCH PRB Usage for MIMO in the DL per cell** + +| | | +|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

PDSCH PRB Usage for MIMO in the DL per cell is calculated in the time-frequency domain.

Detailed Definition:
M(T) = \left[ \frac{\sum_{v_i} \sum_{j} \{M1_{ij}(T) * L_{ij}(T)\}}{\sum_{v_j} \{P_j(T)\} * \text{Alpha}} * 100 \right], where explanations can be found in the table 4.2.1.7.1-2 below.

| +|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 4.2.1.7.1-2: Parameter description for PDSCH PRB Usage for MIMO in the DL per cell** + +| | | +|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $M(T)$ | Total PDSCH PRB usage per cell which is percentage of PRBs used, averaged during time period $T$ with integer value range: 0-100 | +| $M1_{ij}(T)$ | A count of PDSCH PRBs used for traffic transmission for UE $i$ on single MIMO layer per cell at sampling occasion $j$ . Counting unit for PRB is 1 Resource Block x 1 symbol. (1 Resource Block = 12 sub-carrier) | +| $L_{ij}(T)$ | The number of MIMO layers scheduled for UE $i$ at sampling occasion $j$ . | +| $i$ | A UE $i$ that is scheduled during time period $T$ . | +| $j$ | Sampling occasion during time period $T$ . A sampling occasion is 1 symbol. | +| $P_j(T)$ | Total number of PDSCH PRBs available for sampling occasion $j$ on single MIMO layer per cell. | +| $T$ | Time Period during which the measurement is performed. | +| Alpha | Constant value configured by OAM with float value range: 1.00-100.00. With this parameter, $M(T)$ should not be larger than 100. | + +##### 4.2.1.7.2 PUSCH PRB Usage for MIMO in the UL per cell + +This measurement provides the total usage (in percentage) of PUSCH physical resource blocks (PRBs) for MIMO in the uplink per cell. The objective of the measurement is to measure usage of time and frequency resources. A use-case is OAM performance observability. + +Protocol Layer: MAC, PHY + +**Table 4.2.1.7.2-1: Definition for PUSCH PRB Usage for MIMO in the UL per cell** + +| | | +|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

PUSCH PRB Usage for MIMO in the UL per cell is calculated in the time-frequency domain.

Detailed Definition:
M(T) = \left[ \frac{\sum_{v_i} \sum_{j} \{M1_{ij}(T) * L_{ij}(T)\}}{\sum_{v_j} \{P_j(T)\} * \text{Alpha}} * 100 \right], where explanations can be found in the table 4.2.1.7.2-2 below.

| +|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 4.2.1.7.2-2: Parameter description for PUSCH PRB Usage for MIMO in the UL per cell** + +| | | +|--------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $M(T)$ | Total PUSCH PRB usage per cell which is percentage of PRBs used, averaged during time period $T$ with integer value range: 0-100 | +| $M1_{ij}(T)$ | A count of PUSCH PRBs scheduled for traffic transmission for UE $i$ on single MIMO layer per cell at sampling occasion $j$ .
Counting unit for PRB is 1 Resource Block x 1 symbol. (1 Resource Block = 12 sub-carrier) | +| $L_{ij}(T)$ | The number of MIMO layers scheduled for UE $i$ at sampling occasion $j$ . | +| $i$ | A UE that is scheduled during time period $T$ . | +| $j$ | Sampling occasion during time period $T$ . A sampling occasion is 1 symbol. | +| $P_j(T)$ | Total number of PUSCH PRBs available for sampling occasion $j$ on single MIMO layer per cell. | +| $T$ | Time Period during which the measurement is performed. | +| Alpha | Constant value configured by OAM with float value range: 1.00-100.00. With this parameter, $M(T)$ should not be larger than 100. | + +##### 4.2.1.7.3 PDSCH PRB Usage based on statistical MIMO layer in the DL per cell + +This measurement provides the total usage (in percentage) of PDSCH physical resource blocks (PRBs) for statistical MIMO layer per cell. The objective of the measurement is to measure usage of time and frequency resources. A use-case is OAM performance observability. + +Protocol Layer: MAC, PHY + +**Table 4.2.1.7.3-1: Definition for PDSCH PRB Usage based on statistical MIMO layer in the DL per cell** + +| | | +|------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

PDSCH PRB Usage based on statistical MIMO layer in the DL per cell is calculated in the time-frequency domain.

Detailed Definition:

$M(T1) = \left[ \frac{\sum_{vi} \sum_{vj} \{M1_{ij}(T1) * L_{ij}(T1)\}}{\sum_{vj} \{P_j(T1)\} * \beta} * 100 \right]$ $\beta = \max_{T2} LaveDL(T)$

explanations can be found in the table 4.2.1.7.3-2 below.

| +|------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 4.2.1.7.3-2: Parameter description for PDSCH PRB Usage based on statistical MIMO layer in the DL per cell** + +| | | +|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $M(T1)$ | Total PDSCH PRB usage per cell which is percentage of PRBs used, averaged during time period $T1$ with integer value. | +| $M1_{ij}(T1)$ | A count of PDSCH PRBs used for traffic transmission for UE $i$ on single MIMO layer per cell at sampling occasion $j$ . Counting unit for PRB is 1 Resource Block x 1 symbol. (1 Resource Block = 12 sub-carrier) | +| $L_{ij}(T1)$ | The number of MIMO layers scheduled for UE $i$ at sampling occasion $j$ . | +| $i$ | A UE $i$ that is scheduled during time period $T1$ . | +| $j$ | Sampling occasion during time period $T1$ . A sampling occasion is 1 symbol. | +| $P_j(T1)$ | Total number of PDSCH PRBs available for sampling occasion $j$ on single MIMO layer per cell. | +| $T1$ | Time period during which the measurement is performed to calculate $M(T1)$ , e.g., 15min, 1 hour, etc. | +| $\beta$ | A variable factor for MIMO layer assigned with the maximum $LaveDL$ during time period $T2$ with float value 1.00-100.00. | +| $LaveDL(T)$ | Average value of scheduled MIMO layers per PRB on the DL during time period $T$ with float value 1.00-100.00, as defined in TS 28.552 [2]. | +| $T$ | Time period during which the measurement is performed to calculate $LaveDL(T)$ , as defined in TS 28.552 [2]. | +| $T2$ | Time period during which the measurement is performed to calculate $\beta$ , e.g., 1 week, etc. | + +NOTE: For this measurement, same $\beta$ value is used for the entire duration of $T1$ . + +##### 4.2.1.7.4 PUSCH PRB Usage based on statistical MIMO layer in the UL per cell + +This measurement provides the total usage (in percentage) of PUSCH physical resource blocks (PRBs) for statistical MIMO layer in the uplink per cell. The objective of the measurement is to measure usage of time and frequency resources. A use-case is OAM performance observability. + +Protocol Layer: MAC, PHY + +**Table 4.2.1.7.4-1: Definition for PUSCH PRB Usage based on statistical MIMO layer in the UL per cell** + +| | | +|------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

PUSCH PRB Usage based on statistical MIMO layer in the UL per cell is calculated in the time-frequency domain.

Detailed Definition:

$M(T1) = \left[ \frac{\sum_{vi} \sum_{vj} \{M1_{ij}(T1) * L_{ij}(T1)\}}{\sum_{vj} \{P_j(T1)\} * \beta} * 100 \right]$ $\beta = \max_{T2} LaveUL(T)$

explanations can be found in the table 4.2.1.7.4-2 below.

| +|------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 4.2.1.7.4-2: Parameter description for PUSCH PRB Usage based on statistical MIMO layer in the UL per cell** + +| | | +|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $M(T1)$ | Total PUSCH PRB usage per cell which is percentage of PRBs used, averaged during time period $T1$ with integer value. | +| $M1_{ij}(T1)$ | A count of PUSCH PRBs used for traffic transmission for UE $i$ on single MIMO layer per cell at sampling occasion $j$ . Counting unit for PRB is 1 Resource Block x 1 symbol. (1 Resource Block = 12 sub-carrier) | +| $L_{ij}(T1)$ | The number of MIMO layers scheduled for UE $i$ at sampling occasion $j$ . | +| $i$ | A UE $i$ that is scheduled during time period $T1$ . | +| $j$ | Sampling occasion during time period $T1$ . A sampling occasion is 1 symbol. | +| $P_j(T1)$ | Total number of PUSCH PRBs available for sampling occasion $j$ on single MIMO layer per cell. | +| $T1$ | Time period during which the measurement is performed to calculate $M(T1)$ , e.g., 15min, 1 hour, etc. | +| $\beta$ | A variable factor for MIMO layer assigned with the maximum $LaveUL$ during time period $T2$ with float value 1.00-100.00. | +| $LaveUL(T)$ | Average value of scheduled MIMO layers per PRB on the UL during time period $T$ with float value 1.00-100.00, as defined in TS 28.552 [2]. | +| $T$ | Time period during which the measurement is performed to calculate $LaveUL(T)$ , as defined in TS 28.552 [2]. | +| $T2$ | Time period during which the measurement is performed to calculate $\beta$ , e.g., 1 week, etc. | + +NOTE: For this measurement, same $\beta$ value is used for the entire duration of $T1$ . + +##### 4.2.1.7.5 Enhanced PDSCH PRB Usage for MIMO in the DL per cell + +This measurement provides the total usage (in percentage) of PDSCH physical resource blocks (PRBs) for MIMO in the downlink per cell. The objective of the measurement is to measure usage of time, frequency and spatial resources. A use-case is OAM performance observability. + +Protocol Layer: MAC, PHY + +**Table 4.2.1.7.5-1: Definition for enhanced PDSCH PRB Usage for MIMO in the DL per cell** + +| | | +|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

PDSCH PRB Usage for MIMO in the DL per cell is calculated in the time-frequency and spatial domain.

Detailed Definition:

$M(T) = \begin{cases} \left\lceil \frac{\sum_{i \in \mathcal{I}} \sum_{j \in \mathcal{J}} \{M1_{ij}(T) * L_{ij}(T)\}}{\sum_{j \in \mathcal{J}} P_j(T) * LM(T)} * 100 \right\rceil \text{ and } LM(T) = \frac{\sum_j Lmax_j(T)}{K(T)}; & \text{if } K(T) \neq 0 \\ 0; & \text{Otherwise} \end{cases}, \text{ where}$ $K(T) = \sum_{j, Lmax_j(T) \neq 0} 1$

explanations can be found in the table 4.2.1.7.5-2 below.

| +|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 4.2.1.7.5-2: Parameter description for enhanced PDSCH PRB Usage for MIMO in the DL per cell** + +| | | +|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $M(T)$ | Total PDSCH PRB usage per cell which is percentage of PRBs used, averaged during time period $T$ with integer value range: 0-100 | +| $M1_{ij}(T)$ | A count of PDSCH PRBs used for traffic transmission for UE $i$ on single MIMO layer per cell at sampling occasion $j$ . Counting unit for PRB is 1 Resource Block x 1 symbol. (1 Resource Block = 12 sub-carrier) | +| $L_{ij}(T)$ | The number of MIMO layers scheduled for UE $i$ at sampling occasion $j$ . | +| $i$ | A UE $i$ that is scheduled during time period $T$ . | +| $j$ | Sampling occasion during time period $T$ . A sampling occasion is 1 symbol. | +| $T$ | Time period during which the measurement is performed. | +| $P_j(T)$ | Total number of PDSCH PRBs available for sampling occasion $j$ on single MIMO layer per cell. | +| $LM(T)$ | PDSCH Time-domain average of the Maximum Scheduled Layer Number of the cell for MIMO scenario during time period $T$ , defined in TS 28.552 [2]. | +| $Lmax_j(T)$ | The maximum number of scheduling layer of PDSCH at sampling occasion $j$ ; | +| $K(T)$ | The number of sampling occasions at which $Lmax_j(T)$ is not 0. | + +##### 4.2.1.7.6 Enhanced PUSCH PRB Usage for MIMO in the UL per cell + +This measurement provides the total usage (in percentage) of PUSCH physical resource blocks (PRBs) for MIMO in the uplink per cell. The objective of the measurement is to measure usage of time, frequency and spatial resources. A use-case is OAM performance observability. + +Protocol Layer: MAC, PHY + +**Table 4.2.1.7.6-1: Definition for enhanced PUSCH PRB Usage for MIMO in the UL per cell** + +| | | +|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

PUSCH PRB Usage for MIMO in the UL per cell is calculated in the time-frequency and spatial domain.

Detailed Definition:

$M(T) = \begin{cases} \left\lceil \frac{\sum_{i \in \mathcal{U}} \sum_{j \in \mathcal{O}} \{M1_{ij}(T) * L_{ij}(T)\}}{\sum_{j \in \mathcal{O}} \{P_j(T) * LM(T)\}} * 100 \right\rceil \text{ and } LM(T) = \frac{\sum_j Lmax_j(T)}{K(T)}; & \text{if } K(T) \neq 0 \\ 0; & \text{Otherwise} \end{cases}$ $K(T) = \sum_{j, Lmax_j(T) \neq 0} 1$

explanations can be found in the table 4.2.1.7.6-2 below.

| +|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 4.2.1.7.6-2: Parameter description for enhanced PUSCH PRB Usage for MIMO in the UL per cell** + +| | | +|--------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $M(T)$ | Total PUSCH PRB usage per cell which is percentage of PRBs used, averaged during time period $T$ with integer value range: 0-100 | +| $M1_{ij}(T)$ | A count of PUSCH PRBs scheduled for traffic transmission for UE $i$ on single MIMO layer per cell at sampling occasion $j$ .
Counting unit for PRB is 1 Resource Block x 1 symbol. (1 Resource Block = 12 sub-carrier) | +| $L_{ij}(T)$ | The number of MIMO layers scheduled for UE $i$ at sampling occasion $j$ . | +| $i$ | A UE that is scheduled during time period $T$ . | +| $j$ | Sampling occasion during time period $T$ . A sampling occasion is 1 symbol. | +| $T$ | Time period during which the measurement is performed. | +| $P_j(T)$ | Total number of PUSCH PRBs available for sampling occasion $j$ on single MIMO layer per cell. | +| $LM(T)$ | PUSCH Time-domain average of the Maximum Scheduled Layer Number of the cell for MIMO scenario during time period $T$ , defined in TS 28.552 [2]. | +| $Lmax_j(T)$ | The maximum number of scheduling layer of PUSCH at sampling occasion $j$ . | +| $K(T)$ | The number of sampling occasions at which $Lmax_j(T)$ is not 0. | + +#### 4.2.1.8 Number of PDCP Packets in Split-DRB Scenario + +##### 4.2.1.8.1 Number of PDCP Non-duplicated Packets per cell group per Split-DRB per UE + +The objective of this measurement is to calculate number of PDCP non-duplicated packets sent per cell group per UE per split DRB, for QoS verification of MDT. + +Protocol layer: PDCP + +**Table 4.2.1.8.1-1: Definition for total number of PDCP non-duplicated packets per CG per Split-DRB per UE** + +| | | +|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Total number of PDCP non-duplicated packet sent over per cell groups per DRB per UE. This measurement is applicable for EN-DC and SA. This measurement provides the total number of PDCP non-duplicated packets sent over per cell groups.

Detailed Definition:
$I(T, drbid) = P(T, drbid) $ where explanations can be found in the table 4.2.1.8.1-2 below. | +|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 4.2.1.8.1-2: Parameter description for total number of PDCP non-duplicated packets per CG per Split-DRB per UE** + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------| +| $I(T, drbid)$ | Total number of PDCP non-duplicated packets sent per CG per DRB per UE during the time period $T$ . | +| $P(T, drbid)$ | A set of PDCP non duplicated packets sent per CG per UE per split DRB during the time period $T$ . | +| $ P(T, drbid) $ | Cardinality of the set $P$ . | + +##### 4.2.1.8.2 Number of PDCP duplicated Packets per Split-DRB per UE + +The objective of this measurement is to calculate number of PDCP duplicated packets per cell group per UE per split DRB, for QoS verification of MDT. + +Protocol layer: PDCP + +**Table 4.2.1.8.2-1: Definition for total number of PDCP duplicated packets per Split-DRB per UE** + +| | | +|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Total number of PDCP duplicated packet sent per Split-DRB per UE. This measurement is applicable for EN-DC and SA. This measurement provides the total number of PDCP duplicated packets sent over per DRB.

Detailed Definition:
$I(T, drbid) = P(T, drbid) $ , where explanations can be found in the table 4.2.1.8.1-2 below. | +|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 4.2.1.8.2-2: Parameter description for total number of PDCP duplicated packets per Split-DRB per UE** + +| | | +|-----------------|------------------------------------------------------------------------------------------------| +| $I(T, drbid)$ | Total number of PDCP duplicated packets sent per Split-DRB per UE during the time period $T$ . | +| $P(T, drbid)$ | A set of PDCP duplicated packets sent per split DRB per UE during the time period $T$ . | +| $ P(T, drbid) $ | Cardinality of the set P. | + +#### 4.2.1.9 Total RAN Delay in Split-DRB Scenario + +##### 4.2.1.9.1 DL Delay Calculation per Split-DRB per UE when PDCP duplication is enabled for entire measurement period + +The objective of this measurement is to calculate total DL RAN delay per split-DRB per UE when PDCP duplication is enabled for the entire measurement period, for QoS verification of MDT or for the QoS monitoring as defined in TS 23.501 [4]. + +Protocol layer: PDCP + +**Table 4.2.1.9.1-1: Definition for total DL delay for DL PDCP duplicated packets per Split-DRB per UE** + +| | | +|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | Total DL delay for DL PDCP duplicated packets per Split-DRB per UE. This measurement is applicable for EN-DC and SA. This measurement provides the total DL delay for a Split-DRB when PDCP duplication is enabled for the entire measurement period.

Detailed Definition:
$M\_DL(T, drbid) = \min(M\_DL_{MCG}(T, drbid), M\_DL_{SCG}(T, drbid))$ , where explanations can be found in the table 4.2.1.9.1-2 below. | +|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 4.2.1.9.1-2: Parameter description for total DL delay for DL PDCP duplicated packets per Split-DRB per UE** + +| | | +|------------------------------------------------------|-----------------------------------------------------------------------------------------------------------| +| $M\_DL(T, drbid)$ | Total DL Delay per Split-DRB per UE during the time period $T$ . | +| $M\_DL_{MCG}(T, drbid)$ | Total DL Delay on the MCG per split DRB per UE during the time period $T$ . | +| $M\_DL_{SCG}(T, drbid)$ | Total DL Delay on the SCG per split DRB per UE during the time period $T$ . | +| $\min(M\_DL_{MCG}(T, drbid), M\_DL_{SCG}(T, drbid))$ | Minimum of the total DL delays between MCG and SCG legs per Split-DRB per UE during the time period $T$ . | + +##### 4.2.1.9.2 UL Delay Calculation per Split-DRB per UE when PDCP duplication is enabled for entire measurement period + +The objective of this measurement is to calculate total UL RAN delay per split-DRB per UE when PDCP duplication is enabled for the entire measurement period, for QoS verification of MDT or for the QoS monitoring as defined in TS 23.501 [4]. + +Protocol layer: PDCP + +**Table 4.2.1.9.2-1: Definition for total UL delay for UL PDCP duplicated packets per Split-DRB per UE** + +| | | +|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

Total UL delay for UL PDCP duplicated packets per Split-DRB per UE. This measurement is applicable for EN-DC and SA. This measurement provides the total UL delay for a Split-DRB when PDCP duplication is enabled for the entire measurement period.

Detailed Definition:
M\_UL(T, drbid) = \min(M\_UL_{MCG}(T, drbid), M\_UL_{SCG}(T, drbid)), where explanations can be found in the table 4.2.1.9.2-2 below.

| +|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 4.2.1.9.2-2: Parameter description for total UL delay for UL PDCP duplicated packets per Split-DRB per UE** + +| | | +|------------------------------------------------------|-----------------------------------------------------------------------------------------------------------| +| $M\_UL(T, drbid)$ | Total UL Delay per Split-DRB per UE during the time period $T$ . | +| $M\_UL_{MCG}(T, drbid)$ | Total UL Delay on the MCG per split DRB per UE during the time period $T$ . | +| $M\_UL_{SCG}(T, drbid)$ | Total UL Delay on the SCG per split DRB per UE during the time period $T$ . | +| $\min(M\_UL_{MCG}(T, drbid), M\_UL_{SCG}(T, drbid))$ | Minimum of the total UL delays between MCG and SCG legs per Split-DRB per UE during the time period $T$ . | + +##### 4.2.1.9.3 DL Delay Calculation per Split-DRB per UE when PDCP duplication is not enabled for entire measurement period + +The objective of this measurement is to calculate total DL RAN delay per split-DRB per UE when PDCP duplication is not enabled for the entire measurement period, for QoS verification of MDT or for the QoS monitoring as defined in TS 23.501 [4]. + +Protocol layer: PDCP + +**Table 4.2.1.9.3-1: Definition for total DL delay for DL PDCP non-duplicated packets per Split-DRB per UE** + +| | | +|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

Total DL delay for DL PDCP non-duplicated packets per Split-DRB per UE. This measurement is applicable for EN-DC and SA. This measurement provides the total DL delay for a Split-DRB when PDCP duplication is not enabled for the entire measurement period.

Detailed Definition:
M\_DL(T, drbid) = \frac{I\_DL_{MCG}(T, drbid) \times M\_DL_{MCG}(T, drbid) + I\_DL_{SCG}(T, drbid) \times M\_DL_{SCG}(T, drbid)}{I\_DL(T, drbid)} I\_DL(T, drbid) = I\_DL_{MCG}(T, drbid) + I\_DL_{SCG}(T, drbid), where explanations can be found in the table 4.2.1.9.3-2 below.

| +|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 4.2.1.9.3-2: Parameter description for total DL delay for DL PDCP non-duplicated packets per Split-DRB per UE** + +| | | +|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| $M\_DL(T, drbid)$ | Total DL Delay per Split-DRB per UE during the time period $T$ . | +| $M\_DL_{MCG}(T, drbid)$ | Total DL Delay on the MCG per split DRB per UE during the time period $T$ . | +| $M\_DL_{SCG}(T, drbid)$ | Total DL Delay on the SCG per split DRB per UE during the time period $T$ . | +| $I\_DL(T, drbid)$ | Total number of DL PDCP non-duplicated packets sent per Split-DRB per UE during the time period $T$ . | +| $I\_DL_{MCG}(T, drbid)$ | Total number of DL PDCP non-duplicated packets sent on the MCG leg per Split-DRB per UE during the time period $T$ , as defined in Table 4.2.1.8.1-1. | +| $I\_DL_{SCG}(T, drbid)$ | Total number of DL PDCP non-duplicated packets sent on the SCG leg per Split-DRB per UE during the time period $T$ , as defined in Table 4.2.1.8.1-1. | + +##### 4.2.1.9.4 UL Delay Calculation per Split-DRB per UE when PDCP duplication is not enabled for entire measurement period + +The objective of this measurement is to calculate total UL RAN delay per split-DRB per UE when PDCP duplication is not enabled for the entire measurement period, for QoS verification of MDT or for the QoS monitoring as defined in TS 23.501 [4]. + +Protocol layer: PDCP + +**Table 4.2.1.9.4-1: Definition for total UL delay for UL PDCP non-duplicated packets per Split-DRB per UE** + +| | | +|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

Total UL delay for UL PDCP non-duplicated packets per Split-DRB per UE. This measurement is applicable for EN-DC and SA. This measurement provides the total UL delay for a Split-DRB when PDCP duplication is not enabled for the entire measurement period.

Detailed Definition:
M\_UL(T, drbid) = \frac{I\_UL_{MCG}(T, drbid) \times M\_UL_{MCG}(T, drbid) + I\_UL_{SCG}(T, drbid) \times M\_UL_{SCG}(T, drbid)}{I\_UL(T, drbid)} I\_UL(T, drbid) = I\_UL_{MCG}(T, drbid) + I\_UL_{SCG}(T, drbid), where explanations can be found in the table 4.2.1.9.4-2 below.

| +|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 4.2.1.9.4-2: Parameter description for total UL delay for UL PDCP non-duplicated packets per Split-DRB per UE** + +| | | +|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| $M\_UL(T, drbid)$ | Total UL Delay per Split-DRB per UE during the time period $T$ . | +| $M\_UL_{MCG}(T, drbid)$ | Total UL Delay on the MCG per split DRB per UE during the time period $T$ . | +| $M\_UL_{SCG}(T, drbid)$ | Total UL Delay on the SCG per split DRB per UE during the time period $T$ . | +| $I\_UL(T, drbid)$ | Total number of UL PDCP non-duplicated packets sent per Split-DRB per UE during the time period $T$ . | +| $I\_UL_{MCG}(T, drbid)$ | Total number of UL PDCP non-duplicated packets sent on the MCG leg per Split-DRB per UE during the time period $T$ , as defined in Table 4.2.1.8.1-1. | +| $I\_UL_{SCG}(T, drbid)$ | Total number of UL PDCP non-duplicated packets sent on the SCG leg per Split-DRB per UE during the time period $T$ , as defined in Table 4.2.1.8.1-1. | + +#### 4.2.1.10 PDCCH CCE Usage + +##### 4.2.1.10.1 PDCCH CCE Usage per cell + +This measurement provides the total usage (in percentage) of PDCCH control-channel elements (CCEs) per cell. The objective of the measurement is to measure usage of time, frequency and space resources. + +Protocol Layer: MAC, PHY + +**Table 4.2.1.10.1-1: Definition for PDCCH CCE Usage per cell** + +| | | +|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | PDCCH CCE Usage per cell is calculated in the time-frequency-space domain.
Detailed Definition:
$M(T) = \left[ \frac{\sum_{v_i} \sum_{j} \{M1_{ij}(T) * L_{ij}(T)\}}{\sum_{v_i} \{P_j(T)\} * \text{Alpha}} * 100 \right]$ , where explanations can be found in the table 4.2.1.10.1-2 below. | +|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 4.2.1.10.1-2: Parameter description for PDCCH CCE Usage per cell** + +| | | +|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $M(T)$ | Total PDCCH CCE usage per cell which is percentage of CCEs used for MIMO and non-MIMO, averaged during time period $T$ with integer value range: 0-100. | +| $M1_{ij}(T)$ | For MIMO, a count of PDCCH CCEs used for control information transmission for UE $i$ on single MIMO layer per cell at sampling occasion $j$ ;
For non-MIMO, a count of PDCCH CCEs used for control information transmission for UE $i$ per cell at sampling occasion $j$ . | +| $L_{ij}(T)$ | For MIMO, the number of MIMO layers scheduled for UE $i$ at sampling occasion $j$ ;
For non-MIMO, this parameter should be set to 1. | +| $i$ | A UE $i$ that is scheduled during time period $T$ . | +| $j$ | Sampling occasion during time period $T$ . A sampling occasion is 1 symbol. | +| $P_j(T)$ | For MIMO, total number of PDCCH CCEs available for sampling occasion $j$ on single MIMO layer per cell.
For non-MIMO, total number of PDCCH CCEs available for sampling occasion $j$ per cell. | +| $T$ | Time period during which the measurement is performed to calculate $M(T)$ , e.g., 15min, 1 hour, etc. | +| Alpha | A constant value configured by OAM during time period $T$ with float value range: 1.00-100.00.
For MIMO, this parameter should be set to 1.00-100.00;
For non-MIMO, this parameter should be set to 1.00.
With this parameter, $M(T)$ should not be larger than 100. | + +## 4.3 NR measurements performed by the UE + +### 4.3.1 Packet delay + +#### 4.3.1.1 UL PDCP Packet Average Delay per DRB per UE + +The objective of this measurement performed by UE is to measure Packet Delay in Layer PDCP for QoS verification of MDT or for the QoS monitoring as defined in TS 23.501 [4]. + +Protocol Layer: PDCP + +**Table 4.3.1.1-1: Definition for UL PDCP Packet Average Delay per DRB per UE** + +| | | +|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

PDCP Packet Delay in the UL per DRB. This measurement refers to PDCP queuing delay for DRBs in the UE, which captures the delay from packet arrival at PDCP upper SAP until the UL grant to transmit the packet is available, which has included the delay the UE gets resources granted (from sending SR/RACH to get the first grant). The measurement is done separately per DRB.

Detailed Definition:
M(T, drbid) = \left\lfloor \frac{\sum_{i} (tDeliv(i, drbid) - tArrival(i, drbid))}{I(T)} \right\rfloor, \text{where} explanations can be found in the table 4.3.1.1-2 below.

| +|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +NOTE: UE measures UL PDCP queuing delay at DRB level. It is up to gNB to convert DRB level delay to QoS level delay with the assumption that all QoS flows mapped to the same DRB get the same QoS treatment, and it is up to gNB to calculate QoS level delay if multiple DRBs mapped with the same QoS. + +**Table 4.3.1.1-2: Parameter description for UL PDCP Packet Average Delay per DRB per UE** + +| | | +|---------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $M(T, drbid)$ | PDCP average delay in the UL per DRB, averaged during time period T . Unit: 0.1 ms.
PDCP average delay in the UL per DRB is 1s if the actual value is larger than 1s. | +| $tArrival(i)$ | The point in time when the UL PDCP SDU i arrivals at PDCP upper SAP. | +| $tDeliv(i)$ | The point in time when the UL MAC PDU k including the first part of UL PDCP SDU i is scheduled for transmission. | +| $i$ | A UL PDCP SDU that is received by the PDCP during time period T . | +| $I(T)$ | Total number of UL PDCP SDUs received during time period T . | +| $T$ | Time Period during which the measurement is performed | +| $drbid$ | The identity of the measured DRB. | + +#### 4.3.1.2 UL PDCP Excess Packet Delay per DRB + +The objective of this measurement performed by UE is to measure Excess Packet Delay in Layer PDCP for QoS verification of MDT. + +Protocol Layer: PDCP + +**Table 4.3.1.2-1: Definition for UL PDCP Excess Packet Delay per DRB** + +| | | +|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

PDCP Excess Packet Delay in the UL per DRB. It represents the ratio of packets in UL per DRB exceeding the configured delay threshold among the UL PDCP SDUs received. The delay for each packet is calculated from packet arrival at PDCP upper SAP until the UL grant to transmit the packet is available, which has included the delay the UE gets resources granted (from sending SR/RACH to get the first grant). The measurement is done separately per DRB.

Detailed Definition:

$M(T, drbid) = \frac{nExcess(T, drbid)}{nTotal(T, drbid)}$

tULdelay(i, drbid) = tDeliv(i, drbid) - tArrival(i, drbid), where explanations can be found in the table 4.3.1.2-1 below.

| +|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +Table 4.3.1.2-2 + +| | | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $M(T, drbid)$ | Ratio of packets in UL per DRB exceeding the configured delay threshold among the UL PDCP SDUs for which the UL MAC PDU including the first part of UL PDCP SDU is scheduled for transmission during the time period T. | +| $nExcess(T, drbid)$ | Number of PDCP SDUs of a data radio bearer with DRB Identity = $drbid$ , for which $ULdelay(i, drbid)$ exceeded the configured $delayThreshold$ as defined in TS 38.331 [3] during the time period T. | +| $nTotal(T, drbid)$ | Number of PDCP SDUs of a data radio bearer with DRB Identity = $drbid$ , for which the UL MAC PDU including the first part of UL PDCP SDU is scheduled for transmission during the time period T. | +| $tULdelay(i, drbid)$ | Queuing delay observed at the UE PDCP layer from the UL PDCP SDU $i$ belonging to a data radio bearer with DRB Identity = $drbid$ arrival at PDCP upper SAP until the UL MAC PDU $k$ including the first part of UL PDCP SDU $i$ is scheduled for transmission during the time period T. | +| $tDeliv(i, drbid)$ | The point in time when the UL MAC PDU $k$ including the first part of UL PDCP SDU $i$ is scheduled for transmission. | +| $tArrival(i, drbid)$ | The point in time when the UL PDCP SDU $i$ arrivals at PDCP upper SAP. | +| $i$ | Index of PDCP SDU that arrives at the PDCP upper SAP during time period T. | +| $T$ | Time period during which the measurement is performed. | + +##### 4.3.1.2.1 Measurement report mapping for PDCP Excess Packet Delay + +UL PDCP excess packet delay shall be measured according to configuration as defined in TS 38.331 [3]. + +The UE shall report UL PDCP excess packet delay as the ratio of SDUs exceeding the configured delay threshold and the total number of SDUs received by the UE during the measurement period. + +The reported PDCP excess packet delay ratio is mapped to 32 levels with the quantities in the range of $0 < nExcess \leq 100\%$ with uniform quantization in the log domain. + +The mapping of measured quantity is defined in Table 4.3.1.2.1-1. + +Table 4.3.1.2.1-1: EXCESS DELAY measurement report mapping (5 -bit value) + +| Reported value | Measured quantity value | Unit | +|-----------------------|--------------------------------------------------|------| +| EXCESS DELAY RATIO_00 | $0 < \text{EXCESS DELAY RATIO} \leq 0,079$ | % | +| EXCESS DELAY RATIO_01 | $0,079 < \text{EXCESS DELAY RATIO} \leq 0,100$ | % | +| EXCESS DELAY RATIO_02 | $0,100 < \text{EXCESS DELAY RATIO} \leq 0,126$ | % | +| EXCESS DELAY RATIO_03 | $0,126 < \text{EXCESS DELAY RATIO} \leq 0,158$ | % | +| EXCESS DELAY RATIO_04 | $0,158 < \text{EXCESS DELAY RATIO} \leq 0,199$ | % | +| EXCESS DELAY RATIO_05 | $0,199 < \text{EXCESS DELAY RATIO} \leq 0,251$ | % | +| EXCESS DELAY RATIO_06 | $0,251 < \text{EXCESS DELAY RATIO} \leq 0,316$ | % | +| EXCESS DELAY RATIO_07 | $0,316 < \text{EXCESS DELAY RATIO} \leq 0,398$ | % | +| EXCESS DELAY RATIO_08 | $0,398 < \text{EXCESS DELAY RATIO} \leq 0,501$ | % | +| EXCESS DELAY RATIO_09 | $0,501 < \text{EXCESS DELAY RATIO} \leq 0,631$ | % | +| EXCESS DELAY RATIO_10 | $0,631 < \text{EXCESS DELAY RATIO} \leq 0,794$ | % | +| EXCESS DELAY RATIO_11 | $0,794 < \text{EXCESS DELAY RATIO} \leq 1,000$ | % | +| EXCESS DELAY RATIO_12 | $1,000 < \text{EXCESS DELAY RATIO} \leq 1,259$ | % | +| EXCESS DELAY RATIO_13 | $1,259 < \text{EXCESS DELAY RATIO} \leq 1,585$ | % | +| EXCESS DELAY RATIO_14 | $1,585 < \text{EXCESS DELAY RATIO} \leq 1,995$ | % | +| EXCESS DELAY RATIO_15 | $1,995 < \text{EXCESS DELAY RATIO} \leq 2,511$ | % | +| EXCESS DELAY RATIO_16 | $2,511 < \text{EXCESS DELAY RATIO} \leq 3,161$ | % | +| EXCESS DELAY RATIO_17 | $3,161 < \text{EXCESS DELAY RATIO} \leq 3,980$ | % | +| EXCESS DELAY RATIO_18 | $3,980 < \text{EXCESS DELAY RATIO} \leq 5,011$ | % | +| EXCESS DELAY RATIO_19 | $5,011 < \text{EXCESS DELAY RATIO} \leq 6,309$ | % | +| EXCESS DELAY RATIO_20 | $6,309 < \text{EXCESS DELAY RATIO} \leq 7,943$ | % | +| EXCESS DELAY RATIO_21 | $7,943 < \text{EXCESS DELAY RATIO} \leq 10,00$ | % | +| EXCESS DELAY RATIO_22 | $10,00 < \text{EXCESS DELAY RATIO} \leq 12,589$ | % | +| EXCESS DELAY RATIO_23 | $12,589 < \text{EXCESS DELAY RATIO} \leq 15,849$ | % | +| EXCESS DELAY RATIO_24 | $15,849 < \text{EXCESS DELAY RATIO} \leq 19,953$ | % | +| EXCESS DELAY RATIO_25 | $19,953 < \text{EXCESS DELAY RATIO} \leq 25,119$ | % | +| EXCESS DELAY RATIO_26 | $25,119 < \text{EXCESS DELAY RATIO} \leq 31,623$ | % | +| EXCESS DELAY RATIO_27 | $31,623 < \text{EXCESS DELAY RATIO} \leq 39,811$ | % | +| EXCESS DELAY RATIO_28 | $39,811 < \text{EXCESS DELAY RATIO} \leq 50,119$ | % | +| EXCESS DELAY RATIO_29 | $50,119 < \text{EXCESS DELAY RATIO} \leq 63,096$ | % | +| EXCESS DELAY RATIO_30 | $63,096 < \text{EXCESS DELAY RATIO} \leq 79,433$ | % | +| EXCESS DELAY RATIO_31 | $79,433 < \text{EXCESS DELAY RATIO} \leq 100$ | % | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38322/19a59d6b53059ebd27b13c98793f88e0_img.jpg b/marked/Rel-18/38_series/38322/19a59d6b53059ebd27b13c98793f88e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca1be210facb4a5c1591155e3709f941dba596b2 --- /dev/null +++ b/marked/Rel-18/38_series/38322/19a59d6b53059ebd27b13c98793f88e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c9faa24923a1c60cdf5aa0b09a4e5878e27ad00bb6cc24b411ccca6ab1660f18 +size 8965 diff --git a/marked/Rel-18/38_series/38322/1c94fd3cebf58af136144f14160d128e_img.jpg b/marked/Rel-18/38_series/38322/1c94fd3cebf58af136144f14160d128e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..05d0ce0c0dd2171ea12feaf9da559da57dbab079 --- /dev/null +++ b/marked/Rel-18/38_series/38322/1c94fd3cebf58af136144f14160d128e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e86844fed53dbdafea5b47955c0c5b8638262f3851b3940924ba186466e2352 +size 91171 diff --git a/marked/Rel-18/38_series/38322/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-18/38_series/38322/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a90d986e2c8335e8298abb240eacb0a3d84c9b9 --- /dev/null +++ b/marked/Rel-18/38_series/38322/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ebd89a2d1d709c13c2d682f744cdd94f8ffc8d50f58dcb170d11b25b83794f90 +size 19423 diff --git a/marked/Rel-18/38_series/38322/392a79ccd95e682ccd08f35ab2e64144_img.jpg b/marked/Rel-18/38_series/38322/392a79ccd95e682ccd08f35ab2e64144_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..489dae16f5426f802faa002db62e052000fccbf7 --- /dev/null +++ b/marked/Rel-18/38_series/38322/392a79ccd95e682ccd08f35ab2e64144_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6586389b8682190471bea6d6c3b3865cdd74598bed3a49cbf8a9dd22c90ddb44 +size 73894 diff --git a/marked/Rel-18/38_series/38322/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg b/marked/Rel-18/38_series/38322/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d19b070ee9e059755dc7bab62069e42137226232 --- /dev/null +++ b/marked/Rel-18/38_series/38322/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75e0b9ac5f886ff3cf7a63ad2362093e2b3c09519ab3304f1f67c15d4764c077 +size 24264 diff --git a/marked/Rel-18/38_series/38322/58f4167687de8d7339594e5f6fbe0bc6_img.jpg b/marked/Rel-18/38_series/38322/58f4167687de8d7339594e5f6fbe0bc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..acbfac7acb33e7f6987cd10ff58ebfdda0509d72 --- /dev/null +++ b/marked/Rel-18/38_series/38322/58f4167687de8d7339594e5f6fbe0bc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:492138f7442c39a23847348bea312f7eaef948a2c2c4aa5e8585472a85fe2866 +size 63273 diff --git a/marked/Rel-18/38_series/38322/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38322/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ba006ceae9ea439de6ee8968b446198c734fc10 --- /dev/null +++ b/marked/Rel-18/38_series/38322/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dde3c9ae520f4deed871c6bf9376944cba4c940a08fd30a8636906e5919dbfc4 +size 8467 diff --git a/marked/Rel-18/38_series/38322/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38322/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd9fec61e5520556d627603d19fb1208403a576f --- /dev/null +++ b/marked/Rel-18/38_series/38322/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0966ca60fc5a0c92e91343770fa99ed68192a9f5eac4e0bbed9db6c51745f09f +size 5910 diff --git a/marked/Rel-18/38_series/38322/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg b/marked/Rel-18/38_series/38322/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c277b5f1693afefababbf8d85b472a64201e8f3 --- /dev/null +++ b/marked/Rel-18/38_series/38322/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:457c18f3b334c5e354a53eabed568008739d2c2e2034d9577abdf99dd6d4466e +size 21315 diff --git a/marked/Rel-18/38_series/38322/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg b/marked/Rel-18/38_series/38322/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4daef8b017a9841e6310a83d4567f51e7711b148 --- /dev/null +++ b/marked/Rel-18/38_series/38322/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23152371b850dfc4c60b5cde09d4d401713bb307a522c29aae7cac1a04bca778 +size 24290 diff --git a/marked/Rel-18/38_series/38322/8e14350b4b669119a3bdfca7869110ca_img.jpg b/marked/Rel-18/38_series/38322/8e14350b4b669119a3bdfca7869110ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb518b907fb5c8506ed7a38309736fd6d0fdfa1c --- /dev/null +++ b/marked/Rel-18/38_series/38322/8e14350b4b669119a3bdfca7869110ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b712a887cd1e44268a4d0b7b02411653ea1792407ceaba718d4fe91febc600c +size 96934 diff --git a/marked/Rel-18/38_series/38322/99bae07626f60f9ede10e2e387ef7051_img.jpg b/marked/Rel-18/38_series/38322/99bae07626f60f9ede10e2e387ef7051_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ebe445a04bd83523c925dcf30b7ea17f24cd5858 --- /dev/null +++ b/marked/Rel-18/38_series/38322/99bae07626f60f9ede10e2e387ef7051_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96c17d0476a35e874ef16d76b3690ae9d4c00d3c49fd6c2aa3ba601afd697828 +size 47235 diff --git a/marked/Rel-18/38_series/38322/a0739aaf13fa5a632d4faa830f6b2708_img.jpg b/marked/Rel-18/38_series/38322/a0739aaf13fa5a632d4faa830f6b2708_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4005268aa6046142095ee277581da2ffa8de6f08 --- /dev/null +++ b/marked/Rel-18/38_series/38322/a0739aaf13fa5a632d4faa830f6b2708_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d376da0e7ab792944b4d4ad3fda4d9d7dec3bf085d6a1ae4c8e84325ac4554f2 +size 21283 diff --git a/marked/Rel-18/38_series/38322/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-18/38_series/38322/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38fdd8d47c4d3b94e5e72f84fb507fde90264467 --- /dev/null +++ b/marked/Rel-18/38_series/38322/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e30bd8bc74e06eea99b0a2114cb3525f38c36218f70c0f112b9d613581a215d4 +size 17444 diff --git a/marked/Rel-18/38_series/38322/b0e32f17c90ce1db73135488888ce558_img.jpg b/marked/Rel-18/38_series/38322/b0e32f17c90ce1db73135488888ce558_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf311cdac3a552c8d657d528df4ce8544a0aa5a4 --- /dev/null +++ b/marked/Rel-18/38_series/38322/b0e32f17c90ce1db73135488888ce558_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5eb19d80d55372276de8e378efb98bc35f9437f2a0277f7cd0abb40cea8cbf55 +size 14582 diff --git a/marked/Rel-18/38_series/38322/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg b/marked/Rel-18/38_series/38322/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1bd6bbd3aafa402d07cff6bfb5875ab8511f1d53 --- /dev/null +++ b/marked/Rel-18/38_series/38322/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51670c23ff182474a346cbee509ea727b051c08f560a81347d493c364dc8e2d0 +size 74439 diff --git a/marked/Rel-18/38_series/38322/ea4fd10a9a501c602f2bea0f7f711877_img.jpg b/marked/Rel-18/38_series/38322/ea4fd10a9a501c602f2bea0f7f711877_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..148b53caba22b67638254d7549f43b59b4a56dad --- /dev/null +++ b/marked/Rel-18/38_series/38322/ea4fd10a9a501c602f2bea0f7f711877_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d49263f0c2fa5b24cb3f68b107a6237ce44cf5fda071bee0768dd854b2db624 +size 26190 diff --git a/marked/Rel-18/38_series/38322/f6cdd72efb8120e38622b2b61d5639da_img.jpg b/marked/Rel-18/38_series/38322/f6cdd72efb8120e38622b2b61d5639da_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8141a3bcafbbb387c76cea5bc0be6c013d8fb8a9 --- /dev/null +++ b/marked/Rel-18/38_series/38322/f6cdd72efb8120e38622b2b61d5639da_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95f5bd996d43936a6548f6dffdf383f63c561274bd4371fbe26da3fc3b8a4c39 +size 13281 diff --git a/marked/Rel-18/38_series/38322/raw.md b/marked/Rel-18/38_series/38322/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..1151f463530313ef6463448ff7cb90680e26e8d4 --- /dev/null +++ b/marked/Rel-18/38_series/38322/raw.md @@ -0,0 +1,1437 @@ + + +# 3GPP TS 38.322 V18.0.0 (2023-12) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Link Control (RLC) protocol specification (Release 18)** + +![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5G" text is a green graphic consisting of three curved lines of increasing height, representing a signal or wave. + +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 by a single horizontal line. Below the "P" is a red graphic consisting of three curved lines of increasing height, representing a signal or wave. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, black, sans-serif font. + +3GPP logo + +# **3GPP** + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- ***Copyright Notification*** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|--------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions, symbols and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 7 | +| 4 General..... | 7 | +| 4.1 Introduction ..... | 7 | +| 4.2 RLC architecture ..... | 7 | +| 4.2.1 RLC entities..... | 7 | +| 4.2.1.1 TM RLC entity..... | 9 | +| 4.2.1.1.1 General ..... | 9 | +| 4.2.1.1.2 Transmitting TM RLC entity ..... | 9 | +| 4.2.1.1.3 Receiving TM RLC entity..... | 9 | +| 4.2.1.2 UM RLC entity ..... | 9 | +| 4.2.1.2.1 General ..... | 9 | +| 4.2.1.2.2 Transmitting UM RLC entity..... | 10 | +| 4.2.1.2.3 Receiving UM RLC entity ..... | 10 | +| 4.2.1.3 AM RLC entity ..... | 11 | +| 4.2.1.3.1 General ..... | 11 | +| 4.2.1.3.2 Transmitting side..... | 11 | +| 4.2.1.3.3 Receiving side ..... | 12 | +| 4.3 Services ..... | 12 | +| 4.3.1 Services provided to upper layers..... | 12 | +| 4.3.2 Services expected from lower layers..... | 12 | +| 4.4 Functions ..... | 12 | +| 5 Procedures..... | 13 | +| 5.1 RLC entity handling ..... | 13 | +| 5.1.1 RLC entity establishment ..... | 13 | +| 5.1.2 RLC entity re-establishment..... | 13 | +| 5.1.3 RLC entity release ..... | 13 | +| 5.2 Data transfer procedures..... | 13 | +| 5.2.1 TM data transfer ..... | 13 | +| 5.2.1.1 Transmit operations ..... | 13 | +| 5.2.1.1.1 General ..... | 13 | +| 5.2.1.2 Receive operations ..... | 14 | +| 5.2.1.2.1 General ..... | 14 | +| 5.2.2 UM data transfer..... | 14 | +| 5.2.2.1 Transmit operations ..... | 14 | +| 5.2.2.1.1 General ..... | 14 | +| 5.2.2.2 Receive operations ..... | 14 | +| 5.2.2.2.1 General ..... | 14 | +| 5.2.2.2.2 Actions when an UMD PDU is received from lower layer..... | 14 | +| 5.2.2.2.3 Actions when an UMD PDU is placed in the reception buffer..... | 15 | +| 5.2.2.2.4 Actions when t-Reassembly expires ..... | 15 | +| 5.2.3 AM data transfer..... | 16 | +| 5.2.3.1 Transmit operations ..... | 16 | +| 5.2.3.1.1 General ..... | 16 | +| 5.2.3.2 Receive operations ..... | 16 | +| 5.2.3.2.1 General ..... | 16 | +| 5.2.3.2.2 Actions when an AMD PDU is received from lower layer..... | 17 | +| 5.2.3.2.3 Actions when an AMD PDU is placed in the reception buffer..... | 17 | +| 5.2.3.2.4 Actions when t-Reassembly expires..... | 18 | +| 5.3 ARQ procedures..... | 18 | + +| | | | +|-------------------------------|------------------------------------------------------------------|-----------| +| 5.3.1 | General ..... | 18 | +| 5.3.2 | Retransmission ..... | 18 | +| 5.3.3 | Polling..... | 19 | +| 5.3.3.1 | General..... | 19 | +| 5.3.3.2 | Transmission of a AMD PDU ..... | 19 | +| 5.3.3.3 | Reception of a STATUS report ..... | 20 | +| 5.3.3.4 | Expiry of t-PollRetransmit ..... | 20 | +| 5.3.4 | Status reporting..... | 20 | +| 5.4 | SDU discard procedures..... | 21 | +| 5.5 | Data volume calculation..... | 21 | +| 5.6 | Handling of unknown, unforeseen and erroneous protocol data..... | 22 | +| 5.6.1 | Reception of PDU with reserved or invalid values ..... | 22 | +| 6 | Protocol data units, formats and parameters ..... | 22 | +| 6.1 | Protocol data units ..... | 22 | +| 6.1.1 | General ..... | 22 | +| 6.1.2 | RLC data PDU..... | 22 | +| 6.1.3 | RLC control PDU ..... | 22 | +| 6.2 | Formats and parameters ..... | 22 | +| 6.2.1 | General ..... | 22 | +| 6.2.2 | Formats ..... | 23 | +| 6.2.2.1 | General..... | 23 | +| 6.2.2.2 | TMD PDU..... | 23 | +| 6.2.2.3 | UMD PDU ..... | 23 | +| 6.2.2.4 | AMD PDU ..... | 24 | +| 6.2.2.5 | STATUS PDU ..... | 25 | +| 6.2.3 | Parameters ..... | 27 | +| 6.2.3.1 | General..... | 27 | +| 6.2.3.2 | Data field..... | 27 | +| 6.2.3.3 | Sequence Number (SN) field ..... | 27 | +| 6.2.3.4 | Segmentation Info (SI) field ..... | 27 | +| 6.2.3.5 | Segment Offset (SO) field ..... | 27 | +| 6.2.3.6 | Data/Control (D/C) field ..... | 28 | +| 6.2.3.7 | Polling bit (P) field ..... | 28 | +| 6.2.3.8 | Reserved (R) field..... | 28 | +| 6.2.3.9 | Control PDU Type (CPT) field..... | 28 | +| 6.2.3.10 | Acknowledgement SN (ACK_SN) field..... | 28 | +| 6.2.3.11 | Extension bit 1 (E1) field..... | 29 | +| 6.2.3.12 | Negative Acknowledgement SN (NACK_SN) field ..... | 29 | +| 6.2.3.13 | Extension bit 2 (E2) field..... | 29 | +| 6.2.3.14 | SO start (SOstart) field ..... | 29 | +| 6.2.3.15 | SO end (SOend) field..... | 29 | +| 6.2.3.16 | Extension bit 3 (E3) field..... | 30 | +| 6.2.3.17 | NACK range field..... | 30 | +| 7 | Variables, constants and timers..... | 30 | +| 7.1 | State variables ..... | 30 | +| 7.2 | Constants ..... | 32 | +| 7.3 | Timers..... | 32 | +| 7.4 | Configurable parameters ..... | 32 | +| Annex A (informative): | Change history..... | 33 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the NR Radio Link Control (RLC) protocol for the UE – NR radio interface. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 38.300: "NR Overall Description; Stage 2". +- [3] 3GPP TS 38.321: "NR MAC protocol specification". +- [4] 3GPP TS 38.323: "NR PDCP specification". +- [5] 3GPP TS 38.331: "NR RRC Protocol specification". +- [6] 3GPP TS 23.287: "Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services". +- [7] 3GPP TS 38.340: "NR; Backhaul Adaptation Protocol (BAP) specification". +- [8] 3GPP TS 23.304: "Proximity based Services (ProSe) in the 5G System (5GS)". +- [9] 3GPP TS 38.351: "NR; Sidelink Relay Adaptation Protocol (SRAP) Specification". + +# --- 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]. + +**Data field element:** An RLC SDU or an RLC SDU segment that is mapped to the Data field. + +**Delay-critical RLC SDU:** RLC SDU corresponding to a PDCP PDU indicated as delay-critical by PDCP (see TS 38.323 [4]). + +**NR sidelink communication:** AS functionality enabling at least V2X Communication as defined in TS 23.287 [6] and ProSe communication (including ProSe non-Relay, UE-to-Network Relay and UE-to-UE Relay communication (including ProSe UE-to-UE Relay communication with integrated discovery)) as defined in TS 23.304 [8], between two or more nearby UEs, using NR technology but not traversing any network node. + +**NR sidelink discovery:** AS functionality enabling ProSe non-Relay Discovery, ProSe UE-to-Network Relay discovery and ProSe UE-to-UE Relay discovery for Proximity based Services as defined in TS 23.304 [8] between two or more nearby UEs, using NR technology but not traversing any network node. + +**RLC data volume:** The amount of data available for transmission in an RLC entity. + +**RLC SDU segment:** A segment of an RLC SDU. + +## 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]. + +| | | +|-------|------------------------------------| +| AM | Acknowledged Mode | +| AMD | AM Data | +| ARQ | Automatic Repeat request | +| gNB | NR Node B | +| MBS | Multicast/Broadcast Services | +| MCCH | MBS Control Channel | +| MTCH | MBS Traffic Channel | +| PDU | Protocol Data Unit | +| RLC | Radio Link Control | +| SBCCH | Sidelink Broadcast Control Channel | +| SCCH | Sidelink Control Channel | +| SDU | Service Data Unit | +| SN | Sequence Number | +| STCH | Sidelink Traffic Channel | +| TB | Transport Block | +| TM | Transparent Mode | +| TMD | TM Data | +| UE | User Equipment | +| UM | Unacknowledged Mode | +| UMD | UM Data | + +# --- 4 General + +## 4.1 Introduction + +The objective is to describe the RLC architecture and the RLC entities from a functional point of view. + +## 4.2 RLC architecture + +### 4.2.1 RLC entities + +The description in this clause is a model and does not specify or restrict implementations. + +RRc is generally in control of the RLC configuration. + +Functions of the RLC sub layer are performed by RLC entities. For an RLC entity configured at the gNB, there is a peer RLC entity configured at the UE and vice versa. In NR sidelink communication, in NR sidelink discovery, for an RLC entity configured at the transmitting UE, there is a peer RLC entity configured at each receiving UE. + +An RLC entity receives/delivers RLC SDUs from/to upper layer and sends/receives RLC PDUs to/from its peer RLC entity via lower layers. + +An RLC PDU can either be an RLC data PDU or an RLC control PDU. If an RLC entity receives RLC SDUs from upper layer, it receives them through a single RLC channel between RLC and upper layer, and after forming RLC data PDUs from the received RLC SDUs, the RLC entity submits the RLC data PDUs to lower layer through a single logical channel. If an RLC entity receives RLC data PDUs from lower layer, it receives them through a single logical channel, and after forming RLC SDUs from the received RLC data PDUs, the RLC entity delivers the RLC SDUs to upper layer through a single RLC channel between RLC and upper layer. If an RLC entity submits/receives RLC control PDUs + +to/from lower layer, it submits/receives them through the same logical channel it submits/receives the RLC data PDUs through. + +NOTE 1: In case the upper layer is BAP as defined in TS 38.340 [7], an RLC channel refers to a Backhaul RLC channel. + +NOTE 2: In case the upper layer is SRAP as defined in TS 38.351 [9], an RLC channel refers to either a PC5 Relay RLC channel or a Uu Relay RLC channel. + +An RLC entity can be configured to perform data transfer in one of the following three modes: Transparent Mode (TM), Unacknowledged Mode (UM) or Acknowledged Mode (AM). Consequently, an RLC entity is categorized as a TM RLC entity, an UM RLC entity or an AM RLC entity depending on the mode of data transfer that the RLC entity is configured to provide. + +A TM RLC entity is configured either as a transmitting TM RLC entity or a receiving TM RLC entity. The transmitting TM RLC entity receives RLC SDUs from upper layer and sends RLC PDUs to its peer receiving TM RLC entity via lower layers. The receiving TM RLC entity delivers RLC SDUs to upper layer and receives RLC PDUs from its peer transmitting TM RLC entity via lower layers. + +An UM RLC entity is configured either as a transmitting UM RLC entity or a receiving UM RLC entity. The transmitting UM RLC entity receives RLC SDUs from upper layer and sends RLC PDUs to its peer receiving UM RLC entity via lower layers. The receiving UM RLC entity delivers RLC SDUs to upper layer and receives RLC PDUs from its peer transmitting UM RLC entity via lower layers. + +An AM RLC entity consists of a transmitting side and a receiving side. The transmitting side of an AM RLC entity receives RLC SDUs from upper layer and sends RLC PDUs to its peer AM RLC entity via lower layers. The receiving side of an AM RLC entity delivers RLC SDUs to upper layer and receives RLC PDUs from its peer AM RLC entity via lower layers. + +Figure 4.2.1-1 illustrates the overview model of the RLC sub layer. + +![Figure 4.2.1-1: Overview model of the RLC sub layer. The diagram shows the RLC sub layer between an upper layer and lower layers, split by a radio interface. On the gNB/UE side (top), there are five RLC entities: transmitting TM, receiving TM, transmitting UM, receiving UM, and AM. On the UE side (bottom), there are five corresponding RLC entities: receiving TM, transmitting TM, receiving UM, transmitting UM, and AM. Data flows are shown between the upper layer and RLC entities, and between RLC entities and lower layers, with arrows indicating the direction of data transfer (upwards for receiving, downwards for transmitting).](1c94fd3cebf58af136144f14160d128e_img.jpg) + +Figure 4.2.1-1: Overview model of the RLC sub layer. The diagram shows the RLC sub layer between an upper layer and lower layers, split by a radio interface. On the gNB/UE side (top), there are five RLC entities: transmitting TM, receiving TM, transmitting UM, receiving UM, and AM. On the UE side (bottom), there are five corresponding RLC entities: receiving TM, transmitting TM, receiving UM, transmitting UM, and AM. Data flows are shown between the upper layer and RLC entities, and between RLC entities and lower layers, with arrows indicating the direction of data transfer (upwards for receiving, downwards for transmitting). + +**Figure 4.2.1-1: Overview model of the RLC sub layer** + +RLC SDUs of variable sizes which are byte aligned (i.e. multiple of 8 bits) are supported for all RLC entity types (i.e. TM, UM and AM RLC entity). + +Each RLC SDU is used to construct an RLC PDU without waiting for notification from the lower layer (i.e., by MAC) of a transmission opportunity. In the case of UM and AM RLC entities, an RLC SDU may be segmented and transported using two or more RLC PDUs based on the notification(s) from the lower layer. + +RLC PDUs are submitted to lower layer only when a transmission opportunity has been notified by lower layer (i.e. by MAC). + +NOTE 3: The UE should aim to prevent excessive non-consecutive RLC PDUs in a MAC PDU when the UE is requested to generate more than one MAC PDU. + +Description of different RLC entity types are provided below. + +#### 4.2.1.1 TM RLC entity + +##### 4.2.1.1.1 General + +A TM RLC entity can be configured to submit/receive RLC PDUs through the following logical channels: + +- BCCH, DL/UL CCCH, PCCH, and SBCCH. + +![Diagram illustrating the model of two transparent mode peer entities (UE/GNB/UE A and GNB/UE/UE B) connected via a radio interface (Uu/PC5). The diagram shows the flow of data through TM-RLC channels and logical channels (BCCH/PCCH/CCCH/SBCCH).](99bae07626f60f9ede10e2e387ef7051_img.jpg) + +The diagram shows two peer entities, UE/GNB/UE A on the left and GNB/UE/UE B on the right, connected by a vertical line representing the radio interface (Uu/PC5). On the left side (UE/GNB/UE A), a downward arrow labeled 'TM-RLC channel' points into a box labeled 'Transmission buffer'. This buffer is part of a 'Transmitting TM-RLC entity'. Below the buffer, an arrow points down to a horizontal line labeled 'BCCH/PCCH/CCCH/SBCCH'. On the right side (GNB/UE/UE B), an arrow points up from the 'BCCH/PCCH/CCCH/SBCCH' line to a box labeled 'Receiving TM-RLC entity'. From this entity, an upward arrow labeled 'TM-RLC channel' points out. The horizontal line at the bottom connects the BCCH/PCCH/CCCH/SBCCH channels of both entities. + +Diagram illustrating the model of two transparent mode peer entities (UE/GNB/UE A and GNB/UE/UE B) connected via a radio interface (Uu/PC5). The diagram shows the flow of data through TM-RLC channels and logical channels (BCCH/PCCH/CCCH/SBCCH). + +**Figure 4.2.1.1.1-1: Model of two transparent mode peer entities** + +A TM RLC entity submits/receives the following RLC data PDU: + +- TMD PDU. + +##### 4.2.1.1.2 Transmitting TM RLC entity + +When a transmitting TM RLC entity forms TMD PDUs from RLC SDUs, it shall: + +- not segment the RLC SDUs; +- not include any RLC headers in the TMD PDUs. + +##### 4.2.1.1.3 Receiving TM RLC entity + +When a receiving TM RLC entity receives TMD PDUs, it shall: + +- deliver the TMD PDUs (which are just RLC SDUs) to upper layer. + +#### 4.2.1.2 UM RLC entity + +##### 4.2.1.2.1 General + +An UM RLC entity can be configured to submit/receive RLC PDUs through the following logical channels: + +- DL/UL DTCH, SCCH, STCH, MCCH, and MTCH. + +![Diagram illustrating the model of two unacknowledged mode peer entities (UE/GNB/UE A and GNB/UE/UE B) connected via a radio interface (Uu/PC5). The diagram shows the flow of data through the UM-RLC channel, including the generating of RLC headers, segmentation, and SDU reassembly.](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg) + +The diagram shows two peer entities, UE/GNB/UE A and GNB/UE/UE B, connected via a radio interface (Uu/PC5). The flow of data is as follows: + +- UE/GNB/UE A (Transmitting UM-RLC entity):** Data flows from the UM-RLC channel down through a series of steps: "Generate RLC header and store in transmission buffer", "Segmentation Modify RLC header", and "Add RLC header". The data then flows through the radio interface (Uu/PC5) to the receiving entity. +- GNB/UE/UE B (Receiving UM-RLC entity):** Data flows from the radio interface (Uu/PC5) up through a series of steps: "Reception buffer", "Remove RLC header", and "SDU reassembly". The data then flows to the UM-RLC channel. +- Radio Interface (Uu/PC5):** The interface is shown as a vertical line between the two entities. At the bottom, it is labeled with "DTCH/STCH/SCCH/MCCH/MTCH". + +Diagram illustrating the model of two unacknowledged mode peer entities (UE/GNB/UE A and GNB/UE/UE B) connected via a radio interface (Uu/PC5). The diagram shows the flow of data through the UM-RLC channel, including the generating of RLC headers, segmentation, and SDU reassembly. + +**Figure 4.2.1.2.1-1: Model of two unacknowledged mode peer entities** + +An UM RLC entity submits/receives the following RLC data PDU: + +- UMD PDU. + +An UMD PDU contains either one complete RLC SDU or one RLC SDU segment. + +NOTE: For groupcast and broadcast of NR sidelink communication or for NR sidelink discovery only unidirectional UM mode is supported. + +##### 4.2.1.2.2 Transmitting UM RLC entity + +The transmitting UM RLC entity generates UMD PDU(s) for each RLC SDU. It shall include relevant RLC headers in the UMD PDU. When notified of a transmission opportunity by the lower layer, the transmitting UM RLC entity shall segment the RLC SDUs, if needed, so that the corresponding UMD PDUs, with RLC headers updated as needed, fit within the total size of RLC PDU(s) indicated by lower layer. + +##### 4.2.1.2.3 Receiving UM RLC entity + +When a receiving UM RLC entity receives UMD PDUs, it shall: + +- detect the loss of RLC SDU segments at lower layers; +- reassemble RLC SDUs from the received UMD PDUs and deliver the RLC SDUs to upper layer as soon as they are available; +- discard received UMD PDUs that cannot be re-assembled into an RLC SDU due to loss at lower layers of an UMD PDU which belonged to the particular RLC SDU. + +#### 4.2.1.3 AM RLC entity + +##### 4.2.1.3.1 General + +An AM RLC entity can be configured to submit/receive RLC PDUs through the following logical channels: + +- DL/UL DCCH, DL/UL DTCH, SCCH, and STCH. + +![Figure 4.2.1.3.1-1: Model of an acknowledged mode entity. The diagram shows the internal structure of an AM RLC entity. At the top, an 'AM-RLC channel' is shown with bidirectional arrows. Below it, a large box represents the AM RLC entity. Inside, on the transmitting side (left), data flows from 'Generate RLC header and store in transmission buffer' to 'Segmentation Modify RLC header' to 'Add RLC header', which then connects to 'DTCH/DCCH/STCH/SCCH' channels. On the receiving side (right), data flows from 'DTCH/DCCH/STCH/SCCH' channels to 'Routing' to 'Reception buffer' to 'Remove RLC header' to 'SDU reassembly'. A central 'RLC control' block and a 'Retransmission buffer' are also shown, with arrows indicating their interaction with the data paths.](8e14350b4b669119a3bdfca7869110ca_img.jpg) + +Figure 4.2.1.3.1-1: Model of an acknowledged mode entity. The diagram shows the internal structure of an AM RLC entity. At the top, an 'AM-RLC channel' is shown with bidirectional arrows. Below it, a large box represents the AM RLC entity. Inside, on the transmitting side (left), data flows from 'Generate RLC header and store in transmission buffer' to 'Segmentation Modify RLC header' to 'Add RLC header', which then connects to 'DTCH/DCCH/STCH/SCCH' channels. On the receiving side (right), data flows from 'DTCH/DCCH/STCH/SCCH' channels to 'Routing' to 'Reception buffer' to 'Remove RLC header' to 'SDU reassembly'. A central 'RLC control' block and a 'Retransmission buffer' are also shown, with arrows indicating their interaction with the data paths. + +**Figure 4.2.1.3.1-1: Model of an acknowledged mode entity** + +An AM RLC entity delivers/receives the following RLC data PDUs: + +- AMD PDU. + +An AMD PDU contains either one complete RLC SDU or one RLC SDU segment. + +An AM RLC entity delivers/receives the following RLC control PDU: + +- STATUS PDU. + +##### 4.2.1.3.2 Transmitting side + +The transmitting side of an AM RLC entity generates AMD PDU(s) for each RLC SDU. When notified of a transmission opportunity by the lower layer, the transmitting AM RLC entity shall segment the RLC SDUs, if needed, so that the corresponding AMD PDUs, with RLC headers updated as needed, fit within the total size of RLC PDU(s) indicated by lower layer. + +The transmitting side of an AM RLC entity supports retransmission of RLC SDUs or RLC SDU segments (ARQ): + +- if the RLC SDU or RLC SDU segment to be retransmitted (including the RLC header) does not fit within the total size of RLC PDU(s) indicated by lower layer at the particular transmission opportunity notified by lower + +layer, the AM RLC entity can segment the RLC SDU or re-segment the RLC SDU segments into RLC SDU segments; + +- the number of re-segmentation is not limited. + +When the transmitting side of an AM RLC entity forms AMD PDUs from RLC SDUs or RLC SDU segments, it shall: + +- include relevant RLC headers in the AMD PDU. + +##### 4.2.1.3.3 Receiving side + +When the receiving side of an AM RLC entity receives AMD PDUs, it shall: + +- detect whether or not the AMD PDUs have been received in duplication, and discard duplicated AMD PDUs; +- detect the loss of AMD PDUs at lower layers and request retransmissions to its peer AM RLC entity; +- reassemble RLC SDUs from the received AMD PDUs and deliver the RLC SDUs to upper layer as soon as they are available. + +## 4.3 Services + +### 4.3.1 Services provided to upper layers + +The following services are provided by RLC to upper layer: + +- TM data transfer; +- UM data transfer; +- AM data transfer, including indication of successful delivery of upper layers PDUs. + +### 4.3.2 Services expected from lower layers + +The following services are expected by RLC from lower layer (i.e. MAC): + +- data transfer; +- notification of a transmission opportunity, together with the total size of the RLC PDU(s) to be transmitted in the transmission opportunity. + +## 4.4 Functions + +The following functions are supported by the RLC sub layer: + +- transfer of upper layer PDUs; +- error correction through ARQ (only for AM data transfer); +- segmentation and reassembly of RLC SDUs (only for UM and AM data transfer); +- re-segmentation of RLC SDU segments (only for AM data transfer); +- duplicate detection (only for AM data transfer); +- RLC SDU discard (only for UM and AM data transfer); +- RLC re-establishment; +- Protocol error detection (only for AM data transfer). + +# 5 Procedures + +## 5.1 RLC entity handling + +### 5.1.1 RLC entity establishment + +When upper layers request an RLC entity establishment, the UE shall: + +- establish a RLC entity; +- set the state variables of the RLC entity to initial values; +- follow the procedures in clause 5.2. + +For NR sidelink groupcast and broadcast or SL-SRB4, when receiving the first UMD PDU from a Source Layer 2 ID and Destination Layer 2 ID pair for an LCID, and there is not yet a corresponding receiving RLC entity for a radio bearer, the UE shall: + +- establish a receiving RLC entity; +- set the state variables of the RLC entity to initial values; +- follow the procedures in clause 5.2. + +NOTE: The receiving RLC entity of SL-SRB0 and SL-SRB1 is established same as NR sidelink groupcast and broadcast. + +### 5.1.2 RLC entity re-establishment + +When upper layers request an RLC entity re-establishment, the UE shall: + +- discard all RLC SDUs, RLC SDU segments, and RLC PDUs, if any; +- stop and reset all timers; +- reset all state variables to their initial values. + +### 5.1.3 RLC entity release + +When upper layers request an RLC entity release, the UE shall: + +- discard all RLC SDUs, RLC SDU segments, and RLC PDUs, if any; +- release the RLC entity. + +NOTE: For groupcast and broadcast of NR sidelink communication or for SL-SRB4, the receiving UM RLC entity release is up to UE implementation. + +## 5.2 Data transfer procedures + +### 5.2.1 TM data transfer + +#### 5.2.1.1 Transmit operations + +##### 5.2.1.1.1 General + +When submitting a new TMD PDU to lower layer, the transmitting TM RLC entity shall: + +- submit an RLC SDU without any modification to lower layer. + +#### 5.2.1.2 Receive operations + +##### 5.2.1.2.1 General + +When receiving a new TMD PDU from lower layer, the receiving TM RLC entity shall: + +- deliver the TMD PDU without any modification to upper layer. + +### 5.2.2 UM data transfer + +#### 5.2.2.1 Transmit operations + +##### 5.2.2.1.1 General + +When submitting a UMD PDU to lower layer, the transmitting UM RLC entity shall: + +- if the UMD PDU contains a segment of an RLC SDU, set the SN of the UMD PDU to TX\_Next; +- if the UMD PDU contains a segment that maps to the last byte of an RLC SDU, then increment TX\_Next by one. + +#### 5.2.2.2 Receive operations + +##### 5.2.2.2.1 General + +The receiving UM RLC entity shall maintain a reassembly window according to state variable RX\_Next\_Highest as follows: + +- a SN falls within the reassembly window if $(RX\_Next\_Highest - UM\_Window\_Size) \leq SN < RX\_Next\_Highest$ ; +- a SN falls outside of the reassembly window otherwise. + +When receiving an UMD PDU from lower layer, the receiving UM RLC entity shall: + +- either deliver the UMD PDU to upper layer after removing the RLC header, discard the received UMD PDU, or place it in the reception buffer (see clause 5.2.2.2.2); +- if the received UMD PDU was placed in the reception buffer: + - update state variables, reassemble and deliver RLC SDUs to upper layer and start/stop *t-Reassembly* as needed (see clause 5.2.2.2.3). + +When *t-Reassembly* expires, the receiving UM RLC entity shall: + +- update state variables, discard RLC SDU segments and start *t-Reassembly* as needed (see clause 5.2.2.2.4). + +##### 5.2.2.2.2 Actions when an UMD PDU is received from lower layer + +When an UMD PDU is received from lower layer, the receiving UM RLC entity shall: + +- if the UMD PDU header does not contain an SN: + - remove the RLC header and deliver the RLC SDU to upper layer. +- else if $(RX\_Next\_Highest - UM\_Window\_Size) \leq SN < RX\_Next\_Reassembly$ : + - discard the received UMD PDU. +- else: + - place the received UMD PDU in the reception buffer. + +##### 5.2.2.2.3 Actions when an UMD PDU is placed in the reception buffer + +When an UMD PDU with SN = x is placed in the reception buffer, the receiving UM RLC entity shall: + +- if all byte segments with SN = x are received: + - reassemble the RLC SDU from all byte segments with SN = x, remove RLC headers and deliver the reassembled RLC SDU to upper layer; + - if x = RX\_Next\_Reassembly: + - update RX\_Next\_Reassembly to the SN of the first SN > current RX\_Next\_Reassembly that has not been reassembled and delivered to upper layer. +- else if x falls outside of the reassembly window: + - update RX\_Next\_Highest to x + 1; + - discard any UMD PDUs with SN that falls outside of the reassembly window; + - if RX\_Next\_Reassembly falls outside of the reassembly window: + - set RX\_Next\_Reassembly to the SN of the first SN >= (RX\_Next\_Highest – UM\_Window\_Size) that has not been reassembled and delivered to upper layer. +- if *t-Reassembly* is running: + - if RX\_Timer\_Trigger <= RX\_Next\_Reassembly; or + - if RX\_Timer\_Trigger falls outside of the reassembly window and RX\_Timer\_Trigger is not equal to RX\_Next\_Highest; or + - if RX\_Next\_Highest = RX\_Next\_Reassembly + 1 and there is no missing byte segment of the RLC SDU associated with SN = RX\_Next\_Reassembly before the last byte of all received segments of this RLC SDU: + - stop and reset *t-Reassembly*. +- if *t-Reassembly* is not running (includes the case when *t-Reassembly* is stopped due to actions above): + - if RX\_Next\_Highest > RX\_Next\_Reassembly + 1; or + - if RX\_Next\_Highest = RX\_Next\_Reassembly + 1 and there is at least one missing byte segment of the RLC SDU associated with SN = RX\_Next\_Reassembly before the last byte of all received segments of this RLC SDU: + - start *t-Reassembly*; + - set RX\_Timer\_Trigger to RX\_Next\_Highest. + +##### 5.2.2.2.4 Actions when t-Reassembly expires + +When *t-Reassembly* expires, the receiving UM RLC entity shall: + +- update RX\_Next\_Reassembly to the SN of the first SN >= RX\_Timer\_Trigger that has not been reassembled; +- discard all segments with SN < updated RX\_Next\_Reassembly; +- if RX\_Next\_Highest > RX\_Next\_Reassembly + 1; or +- if RX\_Next\_Highest = RX\_Next\_Reassembly + 1 and there is at least one missing byte segment of the RLC SDU associated with SN = RX\_Next\_Reassembly before the last byte of all received segments of this RLC SDU: + - start *t-Reassembly*; + - set RX\_Timer\_Trigger to RX\_Next\_Highest. + +### 5.2.3 AM data transfer + +#### 5.2.3.1 Transmit operations + +##### 5.2.3.1.1 General + +The transmitting side of an AM RLC entity shall prioritize transmission of RLC control PDUs over AMD PDUs. The transmitting side of an AM RLC entity shall prioritize transmission of AMD PDUs containing previously transmitted RLC SDUs or RLC SDU segments over transmission of AMD PDUs containing not previously transmitted RLC SDUs or RLC SDU segments. + +The transmitting side of an AM RLC entity shall maintain a transmitting window according to the state variable TX\_Next\_Ack as follows: + +- a SN falls within the transmitting window if $TX\_Next\_Ack \leq SN < TX\_Next\_Ack + AM\_Window\_Size$ ; +- a SN falls outside of the transmitting window otherwise. + +The transmitting side of an AM RLC entity shall not submit to lower layer any AMD PDU whose SN falls outside of the transmitting window. + +For each RLC SDU received from the upper layer, the AM RLC entity shall: + +- associate a SN with the RLC SDU equal to TX\_Next and construct an AMD PDU by setting the SN of the AMD PDU to TX\_Next; +- increment TX\_Next by one. + +When submitting an AMD PDU that contains a segment of an RLC SDU, to lower layer, the transmitting side of an AM RLC entity shall: + +- set the SN of the AMD PDU to the SN of the corresponding RLC SDU. + +The transmitting side of an AM RLC entity can receive a positive acknowledgement (confirmation of successful reception by its peer AM RLC entity) for an RLC SDU by the following: + +- STATUS PDU from its peer AM RLC entity. + +When receiving a positive acknowledgement for an RLC SDU with SN = x, the transmitting side of an AM RLC entity shall: + +- send an indication to the upper layers of successful delivery of the RLC SDU; +- set TX\_Next\_Ack equal to the SN of the RLC SDU with the smallest SN, whose SN falls within the range $TX\_Next\_Ack \leq SN \leq TX\_Next$ and for which a positive acknowledgment has not been received yet. + +#### 5.2.3.2 Receive operations + +##### 5.2.3.2.1 General + +The receiving side of an AM RLC entity shall maintain a receiving window according to the state variable RX\_Next as follows: + +- a SN falls within the receiving window if $RX\_Next \leq SN < RX\_Next + AM\_Window\_Size$ ; +- a SN falls outside of the receiving window otherwise. + +When receiving an AMD PDU from lower layer, the receiving side of an AM RLC entity shall: + +- either discard the received AMD PDU or place it in the reception buffer (see clause 5.2.3.2.2); +- if the received AMD PDU was placed in the reception buffer: + +- update state variables, reassemble and deliver RLC SDUs to upper layer and start/stop *t-Reassembly* as needed (see clause 5.2.3.2.3). + +When *t-Reassembly* expires, the receiving side of an AM RLC entity shall: + +- update state variables and start *t-Reassembly* as needed (see clause 5.2.3.2.4). + +##### 5.2.3.2.2 Actions when an AMD PDU is received from lower layer + +When an AMD PDU is received from lower layer, where the AMD PDU contains byte segment numbers y to z of an RLC SDU with SN = x, the receiving side of an AM RLC entity shall: + +- if x falls outside of the receiving window; or +- if byte segment numbers y to z of the RLC SDU with SN = x have been received before: + - discard the received AMD PDU. +- else: + - place the received AMD PDU in the reception buffer; + - if some byte segments of the RLC SDU contained in the AMD PDU have been received before: + - discard the duplicate byte segments. + +##### 5.2.3.2.3 Actions when an AMD PDU is placed in the reception buffer + +When an AMD PDU with SN = x is placed in the reception buffer, the receiving side of an AM RLC entity shall: + +- if $x \geq RX\_Next\_Highest$ : + - update $RX\_Next\_Highest$ to $x+1$ . +- if all bytes of the RLC SDU with SN = x are received: + - reassemble the RLC SDU from AMD PDU(s) with SN = x, remove RLC headers when doing so and deliver the reassembled RLC SDU to upper layer; + - if $x = RX\_Highest\_Status$ : + - update $RX\_Highest\_Status$ to the SN of the first RLC SDU with $SN > current RX\_Highest\_Status$ for which not all bytes have been received. + - if $x = RX\_Next$ : + - update $RX\_Next$ to the SN of the first RLC SDU with $SN > current RX\_Next$ for which not all bytes have been received. +- if *t-Reassembly* is running: + - if $RX\_Next\_Status\_Trigger = RX\_Next$ ; or + - if $RX\_Next\_Status\_Trigger = RX\_Next + 1$ and there is no missing byte segment of the SDU associated with $SN = RX\_Next$ before the last byte of all received segments of this SDU; or + - if $RX\_Next\_Status\_Trigger$ falls outside of the receiving window and $RX\_Next\_Status\_Trigger$ is not equal to $RX\_Next + AM\_Window\_Size$ : + - stop and reset *t-Reassembly*. +- if *t-Reassembly* is not running (includes the case *t-Reassembly* is stopped due to actions above): + - if $RX\_Next\_Highest > RX\_Next + 1$ ; or + - if $RX\_Next\_Highest = RX\_Next + 1$ and there is at least one missing byte segment of the SDU associated with $SN = RX\_Next$ before the last byte of all received segments of this SDU: + +- start *t-Reassembly*; +- set RX\_Next\_Status\_Trigger to RX\_Next\_Highest. + +##### 5.2.3.2.4 Actions when *t-Reassembly* expires + +When *t-Reassembly* expires, the receiving side of an AM RLC entity shall: + +- update RX\_Highest\_Status to the SN of the first RLC SDU with SN $\geq$ RX\_Next\_Status\_Trigger for which not all bytes have been received; +- if RX\_Next\_Highest $>$ RX\_Highest\_Status + 1: or +- if RX\_Next\_Highest = RX\_Highest\_Status + 1 and there is at least one missing byte segment of the SDU associated with SN = RX\_Highest\_Status before the last byte of all received segments of this SDU: + - start *t-Reassembly*; + - set RX\_Next\_Status\_Trigger to RX\_Next\_Highest. + +## 5.3 ARQ procedures + +### 5.3.1 General + +ARQ procedures are only performed by an AM RLC entity. + +### 5.3.2 Retransmission + +The transmitting side of an AM RLC entity can receive a negative acknowledgement (notification of reception failure by its peer AM RLC entity) for an RLC SDU or an RLC SDU segment by the following: + +- STATUS PDU from its peer AM RLC entity. + +When receiving a negative acknowledgement for an RLC SDU or an RLC SDU segment by a STATUS PDU from its peer AM RLC entity, the transmitting side of the AM RLC entity shall: + +- if the SN of the corresponding RLC SDU falls within the range TX\_Next\_Ack $\leq$ SN $\leq$ the highest SN of the AMD PDU among the AMD PDUs submitted to lower layer: + - consider the RLC SDU or the RLC SDU segment for which a negative acknowledgement was received for retransmission. + +When an RLC SDU or an RLC SDU segment is considered for retransmission, the transmitting side of the AM RLC entity shall: + +- if the RLC SDU or RLC SDU segment is considered for retransmission for the first time: + - set the RETX\_COUNT associated with the RLC SDU to zero. +- else, if it (the RLC SDU or the RLC SDU segment that is considered for retransmission) is not pending for retransmission already and the RETX\_COUNT associated with the RLC SDU has not been incremented due to another negative acknowledgment in the same STATUS PDU: + - increment the RETX\_COUNT. +- if RETX\_COUNT = *maxRetxThreshold*: + - indicate to upper layers that max retransmission has been reached. + +When retransmitting an RLC SDU or an RLC SDU segment, the transmitting side of an AM RLC entity shall: + +- if needed, segment the RLC SDU or the RLC SDU segment; + +- form a new AMD PDU which will fit within the total size of AMD PDU(s) indicated by lower layer at the particular transmission opportunity; +- submit the new AMD PDU to lower layer. + +When forming a new AMD PDU, the transmitting side of an AM RLC entity shall: + +- only map the original RLC SDU or RLC SDU segment to the Data field of the new AMD PDU; +- modify the header of the new AMD PDU in accordance with the description in clause 6.2.2.4; +- set the P field according to clause 5.3.3. + +### 5.3.3 Polling + +#### 5.3.3.1 General + +An AM RLC entity can poll its peer AM RLC entity in order to trigger STATUS reporting at the peer AM RLC entity. + +#### 5.3.3.2 Transmission of a AMD PDU + +Upon notification of a transmission opportunity by lower layer, for each AMD PDU submitted for transmission such that the AMD PDU contains either a not previously transmitted RLC SDU or an RLC SDU segment containing not previously transmitted byte segment, the transmitting side of an AM RLC entity shall: + +- increment PDU\_WITHOUT\_POLL by one; +- increment BYTE\_WITHOUT\_POLL by every new byte of Data field element that it maps to the Data field of the AMD PDU; +- if PDU\_WITHOUT\_POLL >= pollPDU; or +- if BYTE\_WITHOUT\_POLL >= pollByte: + - include a poll in the AMD PDU as described below. + +Upon notification of a transmission opportunity by lower layer, for each AMD PDU submitted for transmission, the transmitting side of an AM RLC entity shall: + +- if both the transmission buffer and the retransmission buffer becomes empty (excluding transmitted RLC SDUs or RLC SDU segments awaiting acknowledgements) after the transmission of the AMD PDU; or +- if no new RLC SDU can be transmitted after the transmission of the AMD PDU (e.g. due to window stalling); + - include a poll in the AMD PDU as described below. + +NOTE: Empty RLC buffer (excluding transmitted RLC SDUs or RLC SDU segments awaiting acknowledgements) should not lead to unnecessary polling when data awaits in the upper layer. Details are left up to UE implementation. + +To include a poll in an AMD PDU, the transmitting side of an AM RLC entity shall: + +- set the P field of the AMD PDU to "1"; +- set PDU\_WITHOUT\_POLL to 0; +- set BYTE\_WITHOUT\_POLL to 0. + +Upon submission of an AMD PDU including a poll to lower layer, the transmitting side of an AM RLC entity shall: + +- set POLL\_SN to the highest SN of the AMD PDU among the AMD PDUs submitted to lower layer; +- if *t-PollRetransmit* is not running: + - start *t-PollRetransmit*. + +- else: + - restart *t-PollRetransmit*. + +#### 5.3.3.3 Reception of a STATUS report + +Upon reception of a STATUS report from the receiving RLC AM entity the transmitting side of an AM RLC entity shall: + +- if the STATUS report comprises a positive or negative acknowledgement for the RLC SDU with sequence number equal to POLL\_SN: + - if *t-PollRetransmit* is running: + - stop and reset *t-PollRetransmit*. + +#### 5.3.3.4 Expiry of *t-PollRetransmit* + +Upon expiry of *t-PollRetransmit*, the transmitting side of an AM RLC entity shall: + +- if both the transmission buffer and the retransmission buffer are empty (excluding transmitted RLC SDU or RLC SDU segment awaiting acknowledgements); or +- if no new RLC SDU or RLC SDU segment can be transmitted (e.g. due to window stalling): + - consider the RLC SDU with the highest SN among the RLC SDUs submitted to lower layer for retransmission; or + - consider any RLC SDU which has not been positively acknowledged for retransmission. +- include a poll in an AMD PDU as described in clause 5.3.3.2. + +### 5.3.4 Status reporting + +An AM RLC entity sends STATUS PDUs to its peer AM RLC entity in order to provide positive and/or negative acknowledgements of RLC SDUs (or portions of them). + +Triggers to initiate STATUS reporting include: + +- Polling from its peer AM RLC entity: + - When an AMD PDU with SN = x and the P field set to "1" is received from lower layer, the receiving side of an AM RLC entity shall: + - if the AMD PDU is to be discarded as specified in clause 5.2.3.2.2; or + - if $x < RX\_Highest\_Status$ or $x \geq RX\_Next + AM\_Window\_Size$ : + - trigger a STATUS report. + - else: + - delay triggering the STATUS report until $x < RX\_Highest\_Status$ or $x \geq RX\_Next + AM\_Window\_Size$ . + +NOTE 1: This ensures that the RLC Status report is transmitted after HARQ reordering. + +- Detection of reception failure of an AMD PDU + - The receiving side of an AM RLC entity shall trigger a STATUS report when *t-Reassembly* expires. + +NOTE 2: The expiry of *t-Reassembly* triggers both $RX\_Highest\_Status$ to be updated and a STATUS report to be triggered, but the STATUS report shall be triggered after $RX\_Highest\_Status$ is updated. + +When STATUS reporting has been triggered, the receiving side of an AM RLC entity shall: + +- if *t-StatusProhibit* is not running: + - at the first transmission opportunity indicated by lower layer, construct a STATUS PDU and submit it to lower layer. +- else: + - at the first transmission opportunity indicated by lower layer after *t-StatusProhibit* expires, construct a single STATUS PDU even if status reporting was triggered several times while *t-StatusProhibit* was running and submit it to lower layer. + +When a STATUS PDU has been submitted to lower layer, the receiving side of an AM RLC entity shall: + +- start *t-StatusProhibit*. + +When constructing a STATUS PDU, the AM RLC entity shall: + +- for the RLC SDUs with SN such that $RX\_Next \leq SN < RX\_Highest\_Status$ that has not been completely received yet, in increasing SN order of RLC SDUs and increasing byte segment order within RLC SDUs, starting with $SN = RX\_Next$ up to the point where the resulting STATUS PDU still fits to the total size of RLC PDU(s) indicated by lower layer: + - for an RLC SDU for which no byte segments have been received yet: + - include in the STATUS PDU a NACK\_SN which is set to the SN of the RLC SDU. + - for a continuous sequence of byte segments of a partly received RLC SDU that have not been received yet: + - include in the STATUS PDU a set of NACK\_SN, SOstart and SOend. + - for a continuous sequence of RLC SDUs that have not been received yet: + - include in the STATUS PDU a set of NACK\_SN and NACK range; + - include in the STATUS PDU, if required, a pair of SOstart and SOend. +- set the ACK\_SN to the SN of the next not received RLC SDU which is not indicated as missing in the resulting STATUS PDU. + +## 5.4 SDU discard procedures + +When indicated from upper layer (e.g. PDCP) to discard a particular RLC SDU, the transmitting side of an AM RLC entity or the transmitting UM RLC entity shall discard the indicated RLC SDU, if neither the RLC SDU nor a segment thereof has been submitted to the lower layers. The transmitting side of an AM RLC entity shall not introduce an RLC SN gap when discarding an RLC SDU. + +## 5.5 Data volume calculation + +For the purpose of MAC buffer status reporting, the UE shall consider the following as RLC data volume: + +- RLC SDUs and RLC SDU segments that have not yet been included in an RLC data PDU; +- RLC data PDUs that are pending for initial transmission; +- RLC data PDUs that are pending for retransmission (RLC AM). + +For the purpose of MAC delay status reporting, the UE shall consider the following as delay-critical RLC data volume: + +- delay-critical RLC SDUs and delay-critical RLC SDU segments that have not yet been included in an RLC data PDU; +- RLC data PDUs pending for initial transmission, and containing a delay-critical RLC SDU or a delay-critical RLC SDU segment; +- RLC data PDUs that are pending for retransmission (RLC AM). + +In addition, if a STATUS PDU has been triggered and *t-StatusProhibit* is not running or has expired, the UE shall estimate the size of the STATUS PDU that will be transmitted in the next transmission opportunity, and consider this as part of RLC data volume for MAC buffer status reporting and as part of delay-critical RLC data volume for MAC delay status reporting. + +## 5.6 Handling of unknown, unforeseen and erroneous protocol data + +### 5.6.1 Reception of PDU with reserved or invalid values + +When an RLC entity receives an RLC PDU that contains reserved or invalid values, the RLC entity shall: + +- discard the received RLC PDU. + +# --- 6 Protocol data units, formats and parameters + +## 6.1 Protocol data units + +### 6.1.1 General + +RLC PDUs can be categorized into RLC data PDUs and RLC control PDUs. RLC data PDUs in clause 6.1.2 are used by TM, UM and AM RLC entities to transfer upper layer PDUs (i.e. RLC SDUs). RLC control PDUs in clause 6.1.3 are used by AM RLC entity to perform ARQ procedures. + +### 6.1.2 RLC data PDU + +#### a) TMD PDU + +TMD PDU is used to transfer upper layer PDUs by a TM RLC entity. + +#### b) UMD PDU + +UMD PDU is used to transfer upper layer PDUs by an UM RLC entity. + +#### c) AMD PDU + +AMD PDU is used to transfer upper layer PDUs by an AM RLC entity. + +### 6.1.3 RLC control PDU + +#### a) STATUS PDU + +STATUS PDU is used by the receiving side of an AM RLC entity to inform the peer AM RLC entity about RLC data PDUs that are received successfully, and RLC data PDUs that are detected to be lost by the receiving side of an AM RLC entity. + +## 6.2 Formats and parameters + +### 6.2.1 General + +The formats of RLC PDUs are described in clause 6.2.2 and their parameters are described in clause 6.2.3. + +### 6.2.2 Formats + +#### 6.2.2.1 General + +RLC PDU is a bit string. In the figures in clause 6.2.2.2 to 6.2.2.5, bit strings are represented by tables in which the first and most significant bit is the left most bit of the first line of the table, the last and least significant bit is the rightmost bit of the last line of the table, and more generally the bit string is to be read from left to right and then in the reading order of the lines. + +RLC SDUs are bit strings that are byte aligned (i.e. multiple of 8 bits) in length. An RLC SDU is included into an RLC PDU from first bit onward. + +#### 6.2.2.2 TMD PDU + +TMD PDU consists only of a Data field and does not consist of any RLC headers. + +![Diagram of TMD PDU structure showing a single Data field spanning multiple octets (Oct 1 to Oct N).](19a59d6b53059ebd27b13c98793f88e0_img.jpg) + +The diagram shows a TMD PDU structure. It consists of a single Data field represented by a light blue rectangular box. Above the box, a horizontal line with eight tick marks indicates the bit string structure. To the right of the box, the first octet is labeled 'Oct 1' and the last octet is labeled 'Oct N'. Inside the box, the word 'Data' is centered, and below it, three dots indicate the continuation of the data. + +Diagram of TMD PDU structure showing a single Data field spanning multiple octets (Oct 1 to Oct N). + +Figure 6.2.2.2-1: TMD PDU + +#### 6.2.2.3 UMD PDU + +UMD PDU consists of a Data field and an UMD PDU header. The UMD PDU header is byte aligned. + +When an UMD PDU contains a complete RLC SDU, the UMD PDU header only contains the SI and R fields. + +An UM RLC entity is configured by RRC to use either a 6 bit SN or a 12 bit SN. For groupcast and broadcast of NR sidelink communication or for SL-SRB4, only 6 bit SN length is configured. An UMD PDU header contains the SN field only when the corresponding RLC SDU is segmented. An UMD PDU carrying the first segment of an RLC SDU does not carry the SO field in its header. The length of the SO field is 16 bits. + +![Diagram of UMD PDU containing a complete RLC SDU, showing a header with SI and R fields followed by a Data field spanning multiple octets (Oct 1 to Oct N).](b0e32f17c90ce1db73135488888ce558_img.jpg) + +The diagram shows a UMD PDU containing a complete RLC SDU. The header is an orange rectangular box at the top, divided into seven cells: the first cell is labeled 'SI', and the remaining six cells are each labeled 'R'. Below the header is a light blue rectangular box representing the Data field. Above the boxes, a horizontal line with eight tick marks indicates the bit string structure. To the right of the header, the first octet is labeled 'Oct 1'. To the right of the Data field, the second octet is labeled 'Oct 2' and the last octet is labeled 'Oct N'. Inside the Data field, the word 'Data' is centered, and below it, three dots indicate the continuation of the data. + +Diagram of UMD PDU containing a complete RLC SDU, showing a header with SI and R fields followed by a Data field spanning multiple octets (Oct 1 to Oct N). + +Figure 6.2.2.3-1: UMD PDU containing a complete RLC SDU + +![Diagram of UMD PDU with 6 bit SN (No SO), showing a header with SI and SN fields followed by a Data field spanning multiple octets (Oct 1 to Oct N).](f6cdd72efb8120e38622b2b61d5639da_img.jpg) + +The diagram shows a UMD PDU with a 6-bit SN and no SO field. The header is an orange rectangular box at the top, divided into two cells: the first cell is labeled 'SI' and the second, larger cell is labeled 'SN'. Below the header is a light blue rectangular box representing the Data field. Above the boxes, a horizontal line with eight tick marks indicates the bit string structure. To the right of the header, the first octet is labeled 'Oct 1'. To the right of the Data field, the second octet is labeled 'Oct 2' and the last octet is labeled 'Oct N'. Inside the Data field, the word 'Data' is centered, and below it, three dots indicate the continuation of the data. + +Diagram of UMD PDU with 6 bit SN (No SO), showing a header with SI and SN fields followed by a Data field spanning multiple octets (Oct 1 to Oct N). + +Figure 6.2.2.3-2: UMD PDU with 6 bit SN (No SO) + +![Figure 6.2.2.3-3: UMD PDU with 12 bit SN (No SO). The diagram shows a sequence of octets. Octet 1 contains SI, R, R, and SN. Octet 2 contains SN. Octet 3 contains Data. Octet N contains Data.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +| | | | | | +|------|---|---|----|-------| +| SI | R | R | SN | Oct 1 | +| SN | | | | Oct 2 | +| Data | | | | Oct 3 | +| ... | | | | Oct N | + +Figure 6.2.2.3-3: UMD PDU with 12 bit SN (No SO). The diagram shows a sequence of octets. Octet 1 contains SI, R, R, and SN. Octet 2 contains SN. Octet 3 contains Data. Octet N contains Data. + +Figure 6.2.2.3-3: UMD PDU with 12 bit SN (No SO) + +![Figure 6.2.2.3-4: UMD PDU with 6 bit SN and with SO. The diagram shows a sequence of octets. Octet 1 contains SI and SN. Octet 2 contains SO. Octet 3 contains SO. Octet 4 contains Data. Octet N contains Data.](7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg) + +| | | | +|------|----|-------| +| SI | SN | Oct 1 | +| SO | | Oct 2 | +| SO | | Oct 3 | +| Data | | Oct 4 | +| ... | | Oct N | + +Figure 6.2.2.3-4: UMD PDU with 6 bit SN and with SO. The diagram shows a sequence of octets. Octet 1 contains SI and SN. Octet 2 contains SO. Octet 3 contains SO. Octet 4 contains Data. Octet N contains Data. + +Figure 6.2.2.3-4: UMD PDU with 6 bit SN and with SO + +![Figure 6.2.2.3-5: UMD PDU with 12 bit SN and with SO. The diagram shows a sequence of octets. Octet 1 contains SI, R, R, and SN. Octet 2 contains SN. Octet 3 contains SO. Octet 4 contains SO. Octet 5 contains Data. Octet N contains Data.](5132b3a97ac70fe4765c1e07e66b72b3_img.jpg) + +| | | | | | +|------|---|---|----|-------| +| SI | R | R | SN | Oct 1 | +| SN | | | | Oct 2 | +| SO | | | | Oct 3 | +| SO | | | | Oct 4 | +| Data | | | | Oct 5 | +| ... | | | | Oct N | + +Figure 6.2.2.3-5: UMD PDU with 12 bit SN and with SO. The diagram shows a sequence of octets. Octet 1 contains SI, R, R, and SN. Octet 2 contains SN. Octet 3 contains SO. Octet 4 contains SO. Octet 5 contains Data. Octet N contains Data. + +Figure 6.2.2.3-5: UMD PDU with 12 bit SN and with SO + +#### 6.2.2.4 AMD PDU + +AMD PDU consists of a Data field and an AMD PDU header. The AMD PDU header is byte aligned. + +An AM RLC entity is configured by RRC to use either a 12 bit SN or a 18 bit SN. The length of the AMD PDU header is two and three bytes respectively. + +An AMD PDU header contains a D/C, a P, a SI, and a SN. An AMD PDU header contains the SO field only when the Data field consists of an RLC SDU segment which is not the first segment, in which case a 16 bit SO is present. + +![Diagram of AMD PDU with 12 bit SN (No SO). The diagram shows a sequence of Protocol Data Units (PDUs) over time (Oct 1 to Oct N). Each PDU has a header with D/C, P, SI, and SN fields, followed by a Data section. The SN field is 12 bits long.](26d664119ad25250780f554633444e54_img.jpg) + +| | | | | | +|------|---|----|----|-------| +| D/C | P | SI | SN | Oct 1 | +| SN | | | | Oct 2 | +| Data | | | | Oct 3 | +| ... | | | | | +| | | | | Oct N | + +Diagram of AMD PDU with 12 bit SN (No SO). The diagram shows a sequence of Protocol Data Units (PDUs) over time (Oct 1 to Oct N). Each PDU has a header with D/C, P, SI, and SN fields, followed by a Data section. The SN field is 12 bits long. + +Figure 6.2.2.4-1: AMD PDU with 12 bit SN (No SO) + +![Diagram of AMD PDU with 18 bit SN (No SO). The diagram shows a sequence of PDUs over time (Oct 1 to Oct N). Each PDU has a header with D/C, P, SI, R, R, and SN fields, followed by a Data section. The SN field is 18 bits long.](a0739aaf13fa5a632d4faa830f6b2708_img.jpg) + +| | | | | | | | +|------|---|----|---|---|----|-------| +| D/C | P | SI | R | R | SN | Oct 1 | +| SN | | | | | | Oct 2 | +| SN | | | | | | Oct 3 | +| Data | | | | | | Oct 4 | +| ... | | | | | | | +| | | | | | | Oct N | + +Diagram of AMD PDU with 18 bit SN (No SO). The diagram shows a sequence of PDUs over time (Oct 1 to Oct N). Each PDU has a header with D/C, P, SI, R, R, and SN fields, followed by a Data section. The SN field is 18 bits long. + +Figure 6.2.2.4-2: AMD PDU with 18 bit SN (No SO) + +![Diagram of AMD PDU with 12 bit SN with SO. The diagram shows a sequence of PDUs over time (Oct 1 to Oct N). Each PDU has a header with D/C, P, SI, and SN fields, followed by a Data section. The SN field is 12 bits long. There are also SO (Segment Offset) fields present in the header.](8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg) + +| | | | | | +|------|---|----|----|-------| +| D/C | P | SI | SN | Oct 1 | +| SN | | | | Oct 2 | +| SO | | | | Oct 3 | +| SO | | | | Oct 4 | +| Data | | | | Oct 5 | +| ... | | | | | +| | | | | Oct N | + +Diagram of AMD PDU with 12 bit SN with SO. The diagram shows a sequence of PDUs over time (Oct 1 to Oct N). Each PDU has a header with D/C, P, SI, and SN fields, followed by a Data section. The SN field is 12 bits long. There are also SO (Segment Offset) fields present in the header. + +Figure 6.2.2.4-3: AMD PDU with 12 bit SN with SO + +![Diagram of AMD PDU with 18 bit SN with SO. The diagram shows a sequence of PDUs over time (Oct 1 to Oct N). Each PDU has a header with D/C, P, SI, R, R, and SN fields, followed by a Data section. The SN field is 18 bits long. There are also SO (Segment Offset) fields present in the header.](ea4fd10a9a501c602f2bea0f7f711877_img.jpg) + +| | | | | | | | +|------|---|----|---|---|----|-------| +| D/C | P | SI | R | R | SN | Oct 1 | +| SN | | | | | | Oct 2 | +| SN | | | | | | Oct 3 | +| SO | | | | | | Oct 4 | +| SO | | | | | | Oct 5 | +| Data | | | | | | Oct 6 | +| ... | | | | | | | +| | | | | | | Oct N | + +Diagram of AMD PDU with 18 bit SN with SO. The diagram shows a sequence of PDUs over time (Oct 1 to Oct N). Each PDU has a header with D/C, P, SI, R, R, and SN fields, followed by a Data section. The SN field is 18 bits long. There are also SO (Segment Offset) fields present in the header. + +Figure 6.2.2.4-4: AMD PDU with 18 bit SN with SO + +#### 6.2.2.5 STATUS PDU + +STATUS PDU consists of a STATUS PDU payload and an RLC control PDU header. + +RLC control PDU header consists of a D/C and a CPT field. + +The STATUS PDU payload starts from the first bit following the RLC control PDU header, and it consists of one ACK\_SN and one E1, zero or more sets of a NACK\_SN, an E1, an E2 and an E3, and possibly a pair of a SOstart and a SOend or a NACK range field for each NACK\_SN. + +![Diagram of STATUS PDU with 12 bit SN. It shows a sequence of octets starting with D/C and CPT header, followed by ACK_SN, and then various combinations of NACK_SN, E1, E2, E3, R, SOstart, SOend, and NACK range fields.](58f4167687de8d7339594e5f6fbe0bc6_img.jpg) + +| | | | | | | | | | +|------------|-----|---|--------|----|----|---|-------|--------| +| D/C | CPT | | ACK_SN | | | | Oct 1 | | +| ACK_SN | | | | | | | | Oct 2 | +| E1 | R | R | R | R | R | R | R | Oct 3 | +| NACK_SN | | | | | | | | Oct 4 | +| NACK_SN | | | E1 | E2 | E3 | R | | Oct 5 | +| NACK_SN | | | | | | | | Oct 6 | +| NACK_SN | | | E1 | E2 | E3 | R | | Oct 7 | +| SOstart | | | | | | | | Oct 8 | +| SOstart | | | | | | | | Oct 9 | +| SOend | | | | | | | | Oct 10 | +| SOend | | | | | | | | Oct 11 | +| NACK range | | | | | | | | Oct 12 | +| NACK_SN | | | | | | | | Oct 13 | +| NACK_SN | | | E1 | E2 | E3 | R | | Oct 14 | +| ... | | | | | | | | | + +Diagram of STATUS PDU with 12 bit SN. It shows a sequence of octets starting with D/C and CPT header, followed by ACK\_SN, and then various combinations of NACK\_SN, E1, E2, E3, R, SOstart, SOend, and NACK range fields. + +Figure 6.2.2.5-1: STATUS PDU with 12 bit SN + +![Diagram of STATUS PDU with 18 bit SN. It shows a sequence of octets starting with D/C and CPT header, followed by ACK_SN, and then various combinations of NACK_SN, E1, E2, E3, R, SOstart, SOend, and NACK range fields.](392a79ccd95e682ccd08f35ab2e64144_img.jpg) + +| | | | | | | | | | +|------------|-----|----|--------|----|----|---|-------|--------| +| D/C | CPT | | ACK_SN | | | | Oct 1 | | +| ACK_SN | | | | | | | | Oct 2 | +| ACK_SN | | | | | E1 | R | | Oct 3 | +| NACK_SN | | | | | | | | Oct 4 | +| NACK_SN | | | | | | | | Oct 5 | +| NACK_SN | | E1 | E2 | E3 | R | R | R | Oct 6 | +| NACK_SN | | | | | | | | Oct 7 | +| NACK_SN | | | | | | | | Oct 8 | +| NACK_SN | | E1 | E2 | E3 | R | R | R | Oct 9 | +| SOstart | | | | | | | | Oct 10 | +| SOstart | | | | | | | | Oct 11 | +| SOend | | | | | | | | Oct 12 | +| SOend | | | | | | | | Oct 13 | +| NACK range | | | | | | | | Oct 14 | +| NACK_SN | | | | | | | | Oct 15 | +| NACK_SN | | | | | | | | Oct 16 | +| NACK_SN | | E1 | E2 | E3 | R | R | R | Oct 17 | +| ... | | | | | | | | Oct 18 | + +Diagram of STATUS PDU with 18 bit SN. It shows a sequence of octets starting with D/C and CPT header, followed by ACK\_SN, and then various combinations of NACK\_SN, E1, E2, E3, R, SOstart, SOend, and NACK range fields. + +Figure 6.2.2.5-2: STATUS PDU with 18 bit SN + +### 6.2.3 Parameters + +#### 6.2.3.1 General + +In the definition of each field in clauses 6.2.3.2 to 6.2.3.5, the bits in the parameters are represented in which the first and most significant bit is the left most bit and the last and least significant bit is the rightmost bit. Unless mentioned otherwise, integers are encoded in standard binary encoding for unsigned integers. + +#### 6.2.3.2 Data field + +Data field elements are mapped to the Data field in the order which they arrive to the RLC entity at the transmitter. + +For TMD PDU, UMD PDU and AMD PDU: + +- The granularity of the Data field size is one byte; +- The maximum Data field size is the maximum size of a PDCP PDU. + +NOTE: In case the upper layer is BAP as specified in TS 38.340 [7] or SRAP as specified in TS 38.351 [9], the maximum Data field size can be larger than the maximum size of a PDCP PDU. + +For TMD PDU: + +- Only one RLC SDU can be mapped to the Data field of one TMD PDU. + +For UMD PDU, and AMD PDU: + +- Either of the following can be mapped to the Data field of one UMD PDU, or AMD PDU: + - One RLC SDU; + - One RLC SDU segment. + +#### 6.2.3.3 Sequence Number (SN) field + +Length: 12 bits or 18 bits (configurable) for AMD PDU. 6 bits or 12 bits (configurable) for UMD PDU. + +The SN field indicates the sequence number of the corresponding RLC SDU. For RLC AM, the sequence number is incremented by one for every RLC SDU. For RLC UM, the sequence number is incremented by one for every segmented RLC SDU. + +#### 6.2.3.4 Segmentation Info (SI) field + +Length: 2 bits. + +The SI field indicates whether an RLC PDU contains a complete RLC SDU or the first, middle, last segment of an RLC SDU. + +**Table 6.2.3.4-1: SI field interpretation** + +| Value | Description | +|-------|----------------------------------------------------------------------| +| 00 | Data field contains all bytes of an RLC SDU | +| 01 | Data field contains the first segment of an RLC SDU | +| 10 | Data field contains the last segment of an RLC SDU | +| 11 | Data field contains neither the first nor last segment of an RLC SDU | + +#### 6.2.3.5 Segment Offset (SO) field + +Length: 16 bits + +The SO field indicates the position of the RLC SDU segment in bytes within the original RLC SDU. Specifically, the SO field indicates the position within the original RLC SDU to which the first byte of the RLC SDU segment in the + +Data field corresponds. The first byte of the original RLC SDU is referred by the SO field value "0000000000000000", i.e., numbering starts at zero. + +#### 6.2.3.6 Data/Control (D/C) field + +Length: 1 bit. + +The D/C field indicates whether the RLC PDU is an RLC data PDU or RLC control PDU. The interpretation of the D/C field is provided in Table 6.2.3.6-1. + +**Table 6.2.3.6-1: D/C field interpretation** + +| Value | Description | +|-------|-------------| +| 0 | Control PDU | +| 1 | Data PDU | + +#### 6.2.3.7 Polling bit (P) field + +Length: 1 bit. + +The P field indicates whether or not the transmitting side of an AM RLC entity requests a STATUS report from its peer AM RLC entity. The interpretation of the P field is provided in Table 6.2.3.7-1. + +**Table 6.2.3.7-1: P field interpretation** + +| Value | Description | +|-------|-----------------------------| +| 0 | Status report not requested | +| 1 | Status report is requested | + +#### 6.2.3.8 Reserved (R) field + +Length: 1 bit. + +The R field is a reserved field for this release of the protocol. The transmitting entity shall set the R field to "0". The receiving entity shall ignore this field. + +#### 6.2.3.9 Control PDU Type (CPT) field + +Length: 3 bits. + +The CPT field indicates the type of the RLC control PDU. The interpretation of the CPT field is provided in Table 6.2.3.9-1. + +**Table 6.2.3.9-1: CPT field interpretation** + +| Value | Description | +|-------|----------------------------------------------------------------------------------------------------------------| +| 000 | STATUS PDU | +| 001- | Reserved
(PDUs with this coding will be discarded by the receiving entity for this release of the protocol) | + +#### 6.2.3.10 Acknowledgement SN (ACK\_SN) field + +Length: 12 bits or 18 bits (configurable). + +The ACK\_SN field indicates the SN of the next not received RLC SDU which is not reported as missing in the STATUS PDU. When the transmitting side of an AM RLC entity receives a STATUS PDU, it interprets that all RLC SDUs up to but not including the RLC SDU with SN = ACK\_SN have been received by its peer AM RLC entity, excluding those RLC SDUs indicated in the STATUS PDU with NACK\_SN, portions of RLC SDUs indicated in the + +STATUS PDU with NACK\_SN, SOstart and SOend, RLC SDUs indicated in the STATUS PDU with NACK\_SN and NACK\_range, and portions of RLC SDUs indicated in the STATUS PDU with NACK\_SN, NACK\_range, SOstart and SOend. + +#### 6.2.3.11 Extension bit 1 (E1) field + +Length: 1 bit. + +The E1 field indicates whether or not a set of NACK\_SN, E1, E2 and E3 follows. The interpretation of the E1 field is provided in Table 6.2.3.11-1. + +**Table 6.2.3.11-1: E1 field interpretation** + +| Value | Description | +|-------|--------------------------------------------------| +| 0 | A set of NACK_SN, E1, E2 and E3 does not follow. | +| 1 | A set of NACK_SN, E1, E2 and E3 follows. | + +#### 6.2.3.12 Negative Acknowledgement SN (NACK\_SN) field + +Length: 12 bits or 18 bits (configurable). + +The NACK\_SN field indicates the SN of the RLC SDU (or RLC SDU segment) that has been detected as lost at the receiving side of the AM RLC entity. + +#### 6.2.3.13 Extension bit 2 (E2) field + +Length: 1 bit. + +The E2 field indicates whether or not a set of SOstart and SOend follows. The interpretation of the E2 field is provided in Table 6.2.3.13-1. + +**Table 6.2.3.13-1: E2 field interpretation** + +| Value | Description | +|-------|--------------------------------------------------------------| +| 0 | A set of SOstart and SOend does not follow for this NACK_SN. | +| 1 | A set of SOstart and SOend follows for this NACK_SN. | + +#### 6.2.3.14 SO start (SOstart) field + +Length: 16 bits. + +The SOstart field (together with the SOend field) indicates the portion of the RLC SDU with SN = NACK\_SN (the NACK\_SN for which the SOstart is related to) that has been detected as lost at the receiving side of the AM RLC entity. Specifically, the SOstart field indicates the position of the first byte of the portion of the RLC SDU in bytes within the original RLC SDU. The first byte of the original RLC SDU is referred by the SOstart field value "0000000000000000", i.e., numbering starts at zero. + +#### 6.2.3.15 SO end (SOend) field + +Length: 16 bits. + +When E3 is 0, the SOend field (together with the SOstart field) indicates the portion of the RLC SDU with SN = NACK\_SN (the NACK\_SN for which the SOend is related to) that has been detected as lost at the receiving side of the AM RLC entity. Specifically, the SOend field indicates the position of the last byte of the portion of the RLC SDU in bytes within the original RLC SDU. The first byte of the original RLC SDU is referred by the SOend field value "0000000000000000", i.e., numbering starts at zero. The special SOend value "1111111111111111" is used to indicate that the missing portion of the RLC SDU includes all bytes to the last byte of the RLC SDU. + +When E3 is 1, the SOend field indicates the portion of the RLC SDU with SN = NACK\_SN + NACK\_range - 1 that has been detected as lost at the receiving side of the AM RLC entity. Specifically, the SOend field indicates the position of + +the last byte of the portion of the RLC SDU in bytes within the original RLC SDU. The first byte of the original RLC SDU is referred by the SOend field value "0000000000000000", i.e., numbering starts at zero. The special SOend value "1111111111111111" is used to indicate that the missing portion of the RLC SDU includes all bytes to the last byte of the RLC SDU. + +#### 6.2.3.16 Extension bit 3 (E3) field + +Length: 1 bit. + +The E3 field indicates whether or not information about a continuous sequence of RLC SDUs that have not been received follows. + +**Table 6.2.3.16-1: E3 field interpretation** + +| Value | Description | +|-------|----------------------------------------------------| +| 0 | NACK range field does not follow for this NACK_SN. | +| 1 | NACK range field follows for this NACK_SN. | + +#### 6.2.3.17 NACK range field + +Length: 8 bits + +This NACK range field is the number of consecutively lost RLC SDUs starting from and including NACK\_SN. + +# 7 Variables, constants and timers + +## 7.1 State variables + +This clause describes the state variables used in AM and UM entities in order to specify the RLC protocol. The state variables defined in this clause are normative. + +All state variables and all counters are non-negative integers. + +All state variables related to AM data transfer can take values from 0 to 4095 for 12 bit SN or from 0 to 262143 for 18 bit SN. All arithmetic operations contained in the present document on state variables related to AM data transfer are affected by the AM modulus (i.e. final value = [value from arithmetic operation] modulo 4096 for 12 bit SN and 262144 for 18 bit SN). + +All state variables related to UM data transfer can take values from 0 to 63 for 6 bit SN or from 0 to 4095 for 12 bit SN. All arithmetic operations contained in the present document on state variables related to UM data transfer are affected by the UM modulus (i.e. final value = [value from arithmetic operation] modulo 64 for 6 bit SN and 4096 for 12 bit SN). + +When performing arithmetic comparisons of state variables or SN values, a modulus base shall be used. + +TX\_Next\_Ack and RX\_Next shall be assumed as the modulus base at the transmitting side and receiving side of an AM RLC entity, respectively. This modulus base is subtracted from all the values involved, and then an absolute comparison is performed (e.g. $RX\_Next \leq SN < RX\_Next + AM\_Window\_Size$ is evaluated as $[RX\_Next - RX\_Next] \bmod 2^{[sn-FieldLength]} \leq [SN - RX\_Next] \bmod 2^{[sn-FieldLength]} < [RX\_Next + AM\_Window\_Size - RX\_Next] \bmod 2^{[sn-FieldLength]}$ ), where *sn-FieldLength* is 12 or 18 for 12 bit SN and 18 bit SN, respectively. + +RX\_Next\_Highest- UM\_Window\_Size shall be assumed as the modulus base at the receiving UM RLC entity. This modulus base is subtracted from all the values involved, and then an absolute comparison is performed (e.g. $(RX\_Next\_Highest - UM\_Window\_Size) \leq SN < RX\_Next\_Highest$ is evaluated as $[(RX\_Next\_Highest - UM\_Window\_Size) - (RX\_Next\_Highest - UM\_Window\_Size)] \bmod 2^{[sn-FieldLength]} \leq [SN - (RX\_Next\_Highest - UM\_Window\_Size)] \bmod 2^{[sn-FieldLength]} < [RX\_Next\_Highest - (RX\_Next\_Highest - UM\_Window\_Size)] \bmod 2^{[sn-FieldLength]}$ ), where *sn-FieldLength* is 6 or 12 for 6 bit SN and 12 bit SN, respectively. + +The transmitting side of each AM RLC entity shall maintain the following state variables: + +### a) TX\_Next\_Ack – Acknowledgement state variable + +This state variable holds the value of the SN of the next RLC SDU for which a positive acknowledgment is to be received in-sequence, and it serves as the lower edge of the transmitting window. It is initially set to 0, and is updated whenever the AM RLC entity receives a positive acknowledgment for an RLC SDU with SN = TX\_Next\_Ack. + +### b) TX\_Next – Send state variable + +This state variable holds the value of the SN to be assigned for the next newly generated AMD PDU. It is initially set to 0, and is updated whenever the AM RLC entity constructs an AMD PDU with SN = TX\_Next and contains an RLC SDU or the last segment of a RLC SDU. + +### c) POLL\_SN – Poll send state variable + +This state variable holds the value of the highest SN of the AMD PDU among the AMD PDUs submitted to lower layer when POLL\_SN is set according to clause 5.3.3.2. It is initially set to 0. + +The transmitting side of each AM RLC entity shall maintain the following counters: + +### a) PDU\_WITHOUT\_POLL – Counter + +This counter is initially set to 0. It counts the number of AMD PDUs sent since the most recent poll bit was transmitted. + +### b) BYTE\_WITHOUT\_POLL – Counter + +This counter is initially set to 0. It counts the number of data bytes sent since the most recent poll bit was transmitted. + +### c) RETX\_COUNT – Counter + +This counter counts the number of retransmissions of an RLC SDU or RLC SDU segment (see clause 5.3.2). There is one RETX\_COUNT counter maintained per RLC SDU. + +The receiving side of each AM RLC entity shall maintain the following state variables: + +### a) RX\_Next – Receive state variable + +This state variable holds the value of the SN following the last in-sequence completely received RLC SDU, and it serves as the lower edge of the receiving window. It is initially set to 0, and is updated whenever the AM RLC entity receives an RLC SDU with SN = RX\_Next. + +### b) RX\_Next\_Status\_Trigger – *t-Reassembly* state variable + +This state variable holds the value of the SN following the SN of the RLC SDU which triggered *t-Reassembly*. + +### c) RX\_Highest\_Status – Maximum STATUS transmit state variable + +This state variable holds the highest possible value of the SN which can be indicated by "ACK\_SN" when a STATUS PDU needs to be constructed. It is initially set to 0. + +### d) RX\_Next\_Highest – Highest received state variable + +This state variable holds the value of the SN following the SN of the RLC SDU with the highest SN among received RLC SDUs. It is initially set to 0. + +Each transmitting UM RLC entity shall maintain the following state variables: + +### a) TX\_Next – UM send state variable + +This state variable holds the value of the SN to be assigned for the next newly generated UMD PDU with segment. It is initially set to 0, and is updated after the UM RLC entity submits a UMD PDU including the last segment of an RLC SDU to lower layers. + +Each receiving UM RLC entity shall maintain the following state variables: + +### a) RX\_Next\_Reassembly – UM receive state variable + +This state variable holds the value of the earliest SN that is still considered for reassembly. It is initially set to 0. For groupcast and broadcast of NR sidelink communication or for SL-SRB4 of NR sidelink discovery, it is initially set to + +the SN of the first received UMD PDU containing an SN. For the receiving UM RLC entity configured for MCCH or MTCH, it is up to UE implementation to set the initial value of RX\_Next\_Reassembly to a value before RX\_Next\_Highest. + +b) RX\_Timer\_Trigger – UM *t-Reassembly* state variable + +This state variable holds the value of the SN following the SN which triggered *t-Reassembly*. + +c) RX\_Next\_Highest– UM receive state variable + +This state variable holds the value of the SN following the SN of the UMD PDU with the highest SN among received UMD PDUs. It serves as the higher edge of the reassembly window. It is initially set to 0. For groupcast and broadcast of NR sidelink communication or for SL-SRB4 of NR sidelink discovery, it is initially set to the SN of the first received UMD PDU containing an SN. For the receiving UM RLC entity configured for MCCH or MTCH, it is initially set to the SN of the first received UMD PDU containing an SN. + +## 7.2 Constants + +a) AM\_Window\_Size + +This constant is used by both the transmitting side and the receiving side of each AM RLC entity. AM\_Window\_Size = 2048 when a 12 bit SN is used, AM\_Window\_Size = 131072 when an 18 bit SN is used. + +b) UM\_Window\_Size + +This constant is used by the receiving UM RLC entity to define SNs of those UMD SDUs that can be received without causing an advancement of the receiving window. UM\_Window\_Size = 32 when a 6 bit SN is configured, UM\_Window\_Size = 2048 when a 12 bit SN is configured. + +## 7.3 Timers + +The following timers are configured by TS 38.331 [5]: + +a) *t-PollRetransmit* + +This timer is used by the transmitting side of an AM RLC entity in order to retransmit a poll (see clause 5.3.3). + +b) *t-Reassembly* + +This timer is used by the receiving side of an AM RLC entity and receiving UM RLC entity in order to detect loss of RLC PDUs at lower layer (see clauses 5.2.2.2 and 5.2.3.2). If *t-Reassembly* is running, *t-Reassembly* shall not be started additionally, i.e. only one *t-Reassembly* per RLC entity is running at a given time. + +c) *t-StatusProhibit* + +This timer is used by the receiving side of an AM RLC entity in order to prohibit transmission of a STATUS PDU (see clause 5.3.4). + +## 7.4 Configurable parameters + +The following parameters are configured by TS 38.331 [5]: + +a) *maxRetxThreshold* + +This parameter is used by the transmitting side of each AM RLC entity to limit the number of retransmissions corresponding to an RLC SDU, including its segments (see clause 5.3.2). + +b) *pollPDU* + +This parameter is used by the transmitting side of each AM RLC entity to trigger a poll for every *pollPDU* PDUs (see clause 5.3.3). + +c) *pollByte* + +This parameter is used by the transmitting side of each AM RLC entity to trigger a poll for every *pollByte* bytes (see clause 5.3.3). + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|--------------|------------|------|-----|-----|---------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-04 | RAN2#97 bis | R2-1703648 | | | | Skeleton of NR RLC specification | x.y.z | +| 2017-05 | RAN2#98 | R2-1705513 | | | | Initial draft TS capturing outcome of email discussion [97bis#25] | 0.0.2 | +| 2017-06 | RAN#98 | R2-1707257 | | | | Draft TS capturing outcome of email discussion [98#36] | 0.1.0 | +| 2017-07 | RAN2 NR AH#2 | R2-1707508 | | | | Draft TS capturing outcome of email discussion [NR-AH2#06] | 0.2.0 | +| 2017-08 | RAN2#99 | R2-1709752 | | | | Draft TS capturing outcome of email discussion [99#11] | 0.3.0 | +| 2017-09 | RAN#77 | RP-171883 | | | | Submitted to RAN for information | 1.0.0 | +| 2017-10 | RAN2#99 bis | R2-1712478 | | | | Draft TS capturing outcome of email discussion [99bis#13] | 1.1.0 | +| 2017-12 | RAN2#100 | R2-1714261 | | | | Draft TS capturing outcome of email discussion [100#21] | 1.2.0 | +| 2017-12 | RP-78 | RP-172322 | | | | Submitted to RAN for approval | 2.0.0 | +| 2017-12 | RP-78 | | | | | Upgraded to Rel-15 | 15.0.0 | +| 2018-03 | RP-79 | RP-180440 | 0003 | - | F | Corrections for RLC specification | 15.1.0 | +| 2018-06 | RP-80 | RP-181214 | 0009 | 1 | F | CR on updating POLL_SN value and selecting the RLC SDU for retransmission | 15.2.0 | +| 2018-09 | RP-81 | RP-181939 | 0018 | 1 | F | Remaining corrections on TS 38.322 | 15.3.0 | +| 2018-12 | RP-82 | RP-182658 | 0028 | 1 | F | Ambiguity of POLL_SN update timing | 15.4.0 | +| 2019-03 | RP-83 | RP-190540 | 0029 | 1 | D | Corrections on RLC state variables | 15.5.0 | +| 2020-03 | RP-87 | RP-200346 | 0030 | 1 | B | CR for 38.322 for NR V2X | 16.0.0 | +| 2020-07 | RP-88 | RP-201179 | 0036 | 1 | F | Correction on RLC spec to support the BAP as upper layer | 16.1.0 | +| 2020-12 | RP-90 | RP-202772 | 0037 | 1 | F | CR to 38.322 on Backhaul RLC Channel | 16.2.0 | +| 2022-03 | RP-95 | RP-220484 | 0045 | 1 | B | Introduction of NR MBS into 38.322 | 17.0.0 | +| | RP-95 | RP-220491 | 0046 | 1 | B | Introduction of SL Relay in 38.322 | 17.0.0 | +| 2022-06 | RP-96 | RP-221732 | 0048 | 1 | F | Correction on RLC for SL relay | 17.1.0 | +| | RP-96 | RP-221712 | 0049 | - | A | Corrections on the receiving RLC entity establishment for SL-SRB0/SL-SRB1 | 17.1.0 | +| 2022-12 | RP-98 | RP-223412 | 0050 | 4 | F | RLC correction for SL relay | 17.2.0 | +| 2023-06 | RP-100 | RP-231416 | 0052 | 1 | F | Clarification on the maximum Data field size for L2 U2N relay | 17.3.0 | +| 2023-12 | RP-102 | RP-233908 | 0053 | 1 | B | Introduction of XR Enhancements | 18.0.0 | +| | RP-102 | RP-233904 | 0054 | 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/38323/052543d8c9c0643b05b3ce45c6decca1_img.jpg b/marked/Rel-18/38_series/38323/052543d8c9c0643b05b3ce45c6decca1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1bef0f9f3db546c0e41e0b09a75c7bd8f4efc3fd --- /dev/null +++ b/marked/Rel-18/38_series/38323/052543d8c9c0643b05b3ce45c6decca1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:17380451e1c9fb772c4b8d5bc137b66878eec2ebf051662b35b98044e860d8ae +size 14207 diff --git a/marked/Rel-18/38_series/38323/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg b/marked/Rel-18/38_series/38323/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f55c1413766c03b7edf4f780f6b9a11847579c4 --- /dev/null +++ b/marked/Rel-18/38_series/38323/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb3f621e6e36ea9cc7a6b0e5afe2b0630d0e68e54c0c97da7ce0f938393d2f93 +size 8706 diff --git a/marked/Rel-18/38_series/38323/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-18/38_series/38323/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..37ed32bb8a7ec86d057abccc9543807ebd2ca6ae --- /dev/null +++ b/marked/Rel-18/38_series/38323/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4affa68de77f3fb90a3a1900c47b645852f47bce1397b37dadded594326660e1 +size 51000 diff --git a/marked/Rel-18/38_series/38323/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Rel-18/38_series/38323/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8202b952ed6e8814a100cf894d4c62a0f0cac0d3 --- /dev/null +++ b/marked/Rel-18/38_series/38323/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee56d1f51120f3a9577eb9610c01530b12be8c1a79e8bb3fdfdf54018ab79337 +size 50989 diff --git a/marked/Rel-18/38_series/38323/315bdbeafb39026e19b77c26b19d9d1f_img.jpg b/marked/Rel-18/38_series/38323/315bdbeafb39026e19b77c26b19d9d1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..89672871842848a063c298bf4f02b4a8a4f3a3b3 --- /dev/null +++ b/marked/Rel-18/38_series/38323/315bdbeafb39026e19b77c26b19d9d1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6eca83da125fccc38c0160eeaf3994a17ca3ef99411bfafc24387761421faa1f +size 26500 diff --git a/marked/Rel-18/38_series/38323/382a9c9e4816bd229191ab4591424dd8_img.jpg b/marked/Rel-18/38_series/38323/382a9c9e4816bd229191ab4591424dd8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4eda9e119b768cc224a26873554f691d1c1320a9 --- /dev/null +++ b/marked/Rel-18/38_series/38323/382a9c9e4816bd229191ab4591424dd8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:15f7875866ad513900de36dddce9f0dab409680975021efa77cdf0b5ffe9ea31 +size 65165 diff --git a/marked/Rel-18/38_series/38323/4636adff5682a064f0ae5f13a1d464a6_img.jpg b/marked/Rel-18/38_series/38323/4636adff5682a064f0ae5f13a1d464a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb5224099695ff3bfc6832e608265dbeef6c0f9d --- /dev/null +++ b/marked/Rel-18/38_series/38323/4636adff5682a064f0ae5f13a1d464a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:69c9d034e6d9c2b17d9b1068720ba8e57a05c09abcb0e3a8761443262eb4c236 +size 115328 diff --git a/marked/Rel-18/38_series/38323/4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg b/marked/Rel-18/38_series/38323/4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a486e0cba63e8462329ebaa4248e48facd85a8a3 --- /dev/null +++ b/marked/Rel-18/38_series/38323/4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6481f06177e985dc3694242e81be003de03284d1fa914ea738ef2b5358d64353 +size 4145 diff --git a/marked/Rel-18/38_series/38323/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg b/marked/Rel-18/38_series/38323/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf2885380967e09524148bbfabdb5d03f2b535e3 --- /dev/null +++ b/marked/Rel-18/38_series/38323/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:45178dac2412e5614a909e819672b154bdbeeff52214986a652a8d526a23783b +size 54889 diff --git a/marked/Rel-18/38_series/38323/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-18/38_series/38323/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..948d4954fa2ef2f17cf3dc1f13f071328471949a --- /dev/null +++ b/marked/Rel-18/38_series/38323/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a03f5809757781d281a92158a16335e4a72a7b1980708bd58c1f217de9275ba +size 60119 diff --git a/marked/Rel-18/38_series/38323/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38323/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7fa743f21b2f99a42143c07f3df4eafd52c15152 --- /dev/null +++ b/marked/Rel-18/38_series/38323/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4fdadc13d47d15fe1393b70c5613721364651ebeeef549a52cab754c4c2a063 +size 8510 diff --git a/marked/Rel-18/38_series/38323/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38323/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3995ba68b90bea530f6f5fac1ed80123ea779e6c --- /dev/null +++ b/marked/Rel-18/38_series/38323/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5e1e0e00e9507c6309abea6d6261366fc4915b7f13cdce7d90b49b493406d37 +size 5517 diff --git a/marked/Rel-18/38_series/38323/678ac9faaa56bb929499cebeea83a110_img.jpg b/marked/Rel-18/38_series/38323/678ac9faaa56bb929499cebeea83a110_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ecfe8de17f8c205f571fa63d672d6125e4addd2b --- /dev/null +++ b/marked/Rel-18/38_series/38323/678ac9faaa56bb929499cebeea83a110_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1f363f2f300256b2f026b5b7280082382f76c421f5997a40605433b8b7cbf74f +size 14706 diff --git a/marked/Rel-18/38_series/38323/6be06b7dc72bb42afcb3465394667c3b_img.jpg b/marked/Rel-18/38_series/38323/6be06b7dc72bb42afcb3465394667c3b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6f05c54390ecbe6ba78a17f508ecc4343b56820 --- /dev/null +++ b/marked/Rel-18/38_series/38323/6be06b7dc72bb42afcb3465394667c3b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a027af0ba149b167df94ae1539d478cad622ddd2caac3085e0fd2784bb5c69c +size 55519 diff --git a/marked/Rel-18/38_series/38323/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-18/38_series/38323/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f98ed81c3d995427e18eb1e45348311cd16f621 --- /dev/null +++ b/marked/Rel-18/38_series/38323/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e6f42f8d5e0309da4989a57eaa51ceb9fb87faebc3dcb6435e370c43cfd87e0 +size 43857 diff --git a/marked/Rel-18/38_series/38323/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-18/38_series/38323/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd6b9df44a37f07f19adb15c0d5d5c905083c398 --- /dev/null +++ b/marked/Rel-18/38_series/38323/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:661c443d9acfda193d96040702b8a07c44fed67ee3027b0a2281b5d93c8128db +size 55514 diff --git a/marked/Rel-18/38_series/38323/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/Rel-18/38_series/38323/7e670a2b556b53ea9002dfff3a420e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59e8c961aba43a1c4fc0b305d2ad9a9714e0574b --- /dev/null +++ b/marked/Rel-18/38_series/38323/7e670a2b556b53ea9002dfff3a420e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a3370dcff165cd6f36db909bdd674ef0d19368948cd6bf1e576e00a93e95de4b +size 53853 diff --git a/marked/Rel-18/38_series/38323/875c6f4f441fdd3ca7e1908fd1582983_img.jpg b/marked/Rel-18/38_series/38323/875c6f4f441fdd3ca7e1908fd1582983_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43a1910063b168ea44780d436c289903ef19c34c --- /dev/null +++ b/marked/Rel-18/38_series/38323/875c6f4f441fdd3ca7e1908fd1582983_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ec38a59dc0719221a8aba84fa853afcf473fa25c9634b91ec4a6f0703daa24b +size 47012 diff --git a/marked/Rel-18/38_series/38323/8e80de0cac529b2c3775d677c5203133_img.jpg b/marked/Rel-18/38_series/38323/8e80de0cac529b2c3775d677c5203133_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..96593ff667f0a7b768c8c4e366187d6c1bdffe13 --- /dev/null +++ b/marked/Rel-18/38_series/38323/8e80de0cac529b2c3775d677c5203133_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:90d69782cba401e4277deec0c7fb7aa76c0dc11af2e2b9c25f0065338f992ba4 +size 75897 diff --git a/marked/Rel-18/38_series/38323/9dc9f41d7d76c1add4b190d348cb1533_img.jpg b/marked/Rel-18/38_series/38323/9dc9f41d7d76c1add4b190d348cb1533_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e0eb92d5247b4a9de3e981097d6eefd64812747 --- /dev/null +++ b/marked/Rel-18/38_series/38323/9dc9f41d7d76c1add4b190d348cb1533_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:428ec88ef3c3060bd7933bfbb944f16425743c72f6f7fe10321f2201d978b435 +size 27480 diff --git a/marked/Rel-18/38_series/38323/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-18/38_series/38323/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..41ac30943a54176cc3a1135bf5c6de168ee64e29 --- /dev/null +++ b/marked/Rel-18/38_series/38323/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a1e88d8df04dfaa51407404ef5f89838adcf817b81def9986c0213c2cb44ada4 +size 44926 diff --git a/marked/Rel-18/38_series/38323/9f862801bce82634d3b5a1e0a195a799_img.jpg b/marked/Rel-18/38_series/38323/9f862801bce82634d3b5a1e0a195a799_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..820c7679c22fdea503a9cb5c15d4af95e95f47ed --- /dev/null +++ b/marked/Rel-18/38_series/38323/9f862801bce82634d3b5a1e0a195a799_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae4baedb7351df2b803f3ad9026e2626be8554ef9f47e72b89cbd5537a08769a +size 20487 diff --git a/marked/Rel-18/38_series/38323/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-18/38_series/38323/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e63dde64c4f0394728cffeb94454d6b553cbe4d6 --- /dev/null +++ b/marked/Rel-18/38_series/38323/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5baf68af567bbfe4a36873ff2624e65935791e36e780b1977976dcd3ea763bf6 +size 113363 diff --git a/marked/Rel-18/38_series/38323/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-18/38_series/38323/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa35b13d81f1abc2aa13c4c591db0ebf0d1ff7e1 --- /dev/null +++ b/marked/Rel-18/38_series/38323/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d0ec4a82d6026f1ec31c7e0bd062db616fa50857982e13629477647e7a094d8 +size 23902 diff --git a/marked/Rel-18/38_series/38323/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg b/marked/Rel-18/38_series/38323/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cad1db2d8a5b17951f9283416ab24bed3bdd2109 --- /dev/null +++ b/marked/Rel-18/38_series/38323/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cde07d8eed88175b9b33fb690890c993d742fc8b9b5f5768daa0f293c79d0484 +size 22777 diff --git a/marked/Rel-18/38_series/38323/dfa6249d64e9f63db89f2c5b7bbd01de_img.jpg b/marked/Rel-18/38_series/38323/dfa6249d64e9f63db89f2c5b7bbd01de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c150f169f260edcf22b82dcb9df124a794d272e --- /dev/null +++ b/marked/Rel-18/38_series/38323/dfa6249d64e9f63db89f2c5b7bbd01de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:112aaaaee1e3ac525c6b99ae5f9efed3b220de9f5c21364f259f11f7c638cd72 +size 21802 diff --git a/marked/Rel-18/38_series/38323/f10dc32e3673e1392029a49e958a9d6c_img.jpg b/marked/Rel-18/38_series/38323/f10dc32e3673e1392029a49e958a9d6c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..87fad0b4356a6b7655e35f66bc67565411a97c3e --- /dev/null +++ b/marked/Rel-18/38_series/38323/f10dc32e3673e1392029a49e958a9d6c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dba85baed24b96c6cd8a4306bdc9438a544d7502d8ad46ceceda88d6461c0bfe +size 18419 diff --git a/marked/Rel-18/38_series/38323/raw.md b/marked/Rel-18/38_series/38323/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b7315e4bb9c2f134dbe75e0891d6ae40debb3236 --- /dev/null +++ b/marked/Rel-18/38_series/38323/raw.md @@ -0,0 +1,1924 @@ + + +# 3GPP TS 38.323 V18.0.0 (2023-12) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Packet Data Convergence Protocol (PDCP) specification (Release 18)** + +![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5G" text are three green, curved lines representing signal waves. + +5G logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, featuring the text "3GPP" in a bold, black, sans-serif font. 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 + +## **3GPP** + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- ***Copyright Notification*** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|----------------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions and abbreviations ..... | 8 | +| 3.1 Definitions..... | 8 | +| 3.2 Abbreviations ..... | 9 | +| 4 General..... | 10 | +| 4.1 Introduction ..... | 10 | +| 4.2 Architecture..... | 10 | +| 4.2.1 PDCP structure ..... | 10 | +| 4.2.2 PDCP entities..... | 13 | +| 4.3 Services ..... | 14 | +| 4.3.1 Services provided to upper layers..... | 14 | +| 4.3.2 Services expected from lower layers..... | 14 | +| 4.4 Functions ..... | 15 | +| 5 Procedures..... | 15 | +| 5.1 PDCP entity handling..... | 15 | +| 5.1.1 PDCP entity establishment..... | 15 | +| 5.1.2 PDCP entity re-establishment..... | 15 | +| 5.1.3 PDCP entity release..... | 17 | +| 5.1.4 PDCP entity suspend..... | 17 | +| 5.1.5 PDCP entity reconfiguration ..... | 18 | +| 5.2 Data transfer..... | 18 | +| 5.2.1 Transmit operation..... | 18 | +| 5.2.2 Receive operation..... | 20 | +| 5.2.2.1 Actions when a PDCP Data PDU is received from lower layers ..... | 20 | +| 5.2.2.2 Actions when a t-Reordering expires ..... | 21 | +| 5.2.2.3 Actions when the value of t-Reordering is reconfigured..... | 22 | +| 5.2.3 Sidelink transmit operation..... | 22 | +| 5.2.4 Sidelink receive operation ..... | 22 | +| 5.3 SDU discard ..... | 22 | +| 5.4 Status reporting ..... | 23 | +| 5.4.1 Transmit operation..... | 23 | +| 5.4.2 Receive operation ..... | 24 | +| 5.5 Data recovery ..... | 24 | +| 5.6 Data volume calculation..... | 24 | +| 5.7 Robust header compression and decompression..... | 25 | +| 5.7.1 Supported header compression protocols and profiles ..... | 25 | +| 5.7.2 Configuration of ROHC ..... | 25 | +| 5.7.3 Protocol parameters ..... | 26 | +| 5.7.4 Header compression using ROHC..... | 26 | +| 5.7.5 Header decompression using ROHC..... | 27 | +| 5.7.6 PDCP Control PDU for interspersed ROHC feedback ..... | 27 | +| 5.7.6.1 Transmit Operation..... | 27 | +| 5.7.6.2 Receive Operation..... | 27 | +| 5.8 Ciphering and deciphering ..... | 27 | +| 5.9 Integrity protection and verification..... | 28 | +| 5.10 Handling of unknown, unforeseen, and erroneous protocol data..... | 29 | +| 5.11 PDCP duplication..... | 29 | +| 5.11.1 Activation/Deactivation of PDCP duplication ..... | 29 | +| 5.11.2 Duplicate PDU discard..... | 29 | +| 5.12 Ethernet header compression and decompression..... | 30 | +| 5.12.1 Supported header compression protocols..... | 30 | +| 5.12.2 Configuration of EHC ..... | 30 | + +| | | | +|----------|------------------------------------------------------------------------------------------------------------------|----| +| 5.12.3 | Protocol parameters ..... | 30 | +| 5.12.4 | Header compression using EHC..... | 30 | +| 5.12.5 | Header decompression using EHC..... | 30 | +| 5.12.6 | PDCP Control PDU for EHC feedback..... | 31 | +| 5.12.6.1 | Transmit Operation..... | 31 | +| 5.12.6.2 | Receive Operation..... | 31 | +| 5.12.7 | Simultaneous configuration of ROHC and EHC..... | 31 | +| 5.13 | Uplink data switching..... | 31 | +| 5.14 | Uplink Data compression and decompression ..... | 32 | +| 5.14.1 | UDC protocol ..... | 32 | +| 5.14.2 | Configuration of UDC ..... | 32 | +| 5.14.3 | UDC header ..... | 32 | +| 5.14.4 | Uplink data compression ..... | 33 | +| 5.14.5 | PDCP Control PDU for UDC feedback ..... | 33 | +| 5.14.6 | Pre-defined dictionary ..... | 33 | +| 5.14.7 | UDC buffer reset procedure ..... | 33 | +| 5.14.8 | UDC checksum error handling ..... | 33 | +| 5.15 | Data volume calculation for delay status reporting..... | 33 | +| 6 | Protocol data units, formats, and parameters ..... | 34 | +| 6.1 | Protocol data units..... | 34 | +| 6.1.1 | Data PDU..... | 34 | +| 6.1.2 | Control PDU..... | 34 | +| 6.2 | Formats..... | 34 | +| 6.2.1 | General ..... | 34 | +| 6.2.2 | Data PDU..... | 34 | +| 6.2.2.1 | Data PDU for SRBs ..... | 34 | +| 6.2.2.2 | Data PDU for DRBs and MRBs with 12 bits PDCP SN ..... | 35 | +| 6.2.2.3 | Data PDU for DRBs and MRBs with 18 bits PDCP SN ..... | 35 | +| 6.2.2.4 | Data PDU for sidelink DRBs for groupcast and broadcast, for the sidelink SRB0 and for the
sidelink SRB4 ..... | 36 | +| 6.2.2.5 | Data PDU for sidelink SRBs for unicast ..... | 36 | +| 6.2.2.6 | Data PDU for sidelink DRBs for unicast with 12 bits PDCP SN..... | 37 | +| 6.2.2.7 | Data PDU for sidelink DRBs for unicast with 18 bits PDCP SN..... | 38 | +| 6.2.3 | Control PDU ..... | 38 | +| 6.2.3.1 | Control PDU for PDCP status report..... | 38 | +| 6.2.3.2 | Control PDU for interspersed ROHC feedback..... | 39 | +| 6.2.3.3 | Control PDU for EHC feedback ..... | 39 | +| 6.2.3.4 | Control PDU for UDC feedback..... | 40 | +| 6.3 | Parameters ..... | 40 | +| 6.3.1 | General ..... | 40 | +| 6.3.2 | PDCP SN ..... | 40 | +| 6.3.3 | Data..... | 40 | +| 6.3.4 | MAC-I ..... | 40 | +| 6.3.5 | COUNT ..... | 41 | +| 6.3.6 | R ..... | 41 | +| 6.3.7 | D/C ..... | 41 | +| 6.3.8 | PDU type ..... | 41 | +| 6.3.9 | FMC..... | 41 | +| 6.3.10 | Bitmap ..... | 42 | +| 6.3.11 | Interspersed ROHC feedback..... | 42 | +| 6.3.12 | SDU Type..... | 42 | +| 6.3.13 | K NRP-sess ID ..... | 42 | +| 6.3.14 | FE ..... | 42 | +| 7 | State variables, constants, and timers..... | 43 | +| 7.1 | State variables ..... | 43 | +| 7.2 | Constants ..... | 44 | +| 7.3 | Timers..... | 44 | + +| | | +|-----------------------------------------------------------------------------|-----------| +| Annex A (normative): Ethernet Header Compression (EHC) protocol..... | 44 | +| A.1 EHC principle ..... | 44 | +| A.2 EHC packet format and parameters ..... | 46 | +| A.2.1 EHC packet format..... | 46 | +| A.2.1.1 EHC Full Header packet and EHC Compressed Header packet ..... | 46 | +| A.2.1.2 EHC feedback packet ..... | 47 | +| A.2.2 Parameters ..... | 47 | +| A.2.2.1 F/C ..... | 47 | +| A.2.2.2 CID ..... | 47 | +| Annex B (normative): Uplink Data Compression Protocol..... | 48 | +| B.1 UDC general description..... | 48 | +| B.2 UDC packet format and parameters..... | 48 | +| B.2.1 UDC Header and UDC Data Block format..... | 48 | +| B.2.2 UDC parameters ..... | 48 | +| B.2.2.1 FU ..... | 48 | +| B.2.2.2 FR ..... | 48 | +| B.2.2.3 Checksum ..... | 49 | +| B.2.3 An example of UDC Checksum calculation ..... | 49 | +| Annex C (informative): Change history..... | 50 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document provides the description of the Packet Data Convergence Protocol (PDCP). + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP 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.321: "NR Medium Access Control (MAC) protocol specification". +- [5] 3GPP TS 38.322: "NR Radio Link Control (RLC) protocol specification". +- [6] 3GPP TS 33.501: "Security Architecture and Procedures for 5G System". +- [7] IETF RFC 5795: "The Robust Header Compression (ROHC) Framework". +- [8] IETF RFC 3095: "Robust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP and uncompressed". +- [9] IETF RFC 4815: "Robust Header Compression (ROHC): Corrections and Clarifications to RFC 3095". +- [10] IETF RFC 6846: "Robust Header Compression (ROHC): A Profile for TCP/IP (ROHC-TCP)". +- [11] IETF RFC 5225: "Robust Header Compression (ROHC) Version 2: Profiles for RTP, UDP, IP, ESP and UDP Lite". +- [12] 3GPP TS 36.321: "Evolved Universal Terrestrial Radio Access (E-UTRA) Medium Access Control (MAC) protocol specification". +- [13] 3GPP TS 23.287: "Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services". +- [14] 3GPP TS 33.536: "Security Aspect of 3GPP Support for Advanced V2X Services". +- [15] IEEE Standard 802.3™-2018: "Ethernet". +- [16] 3GPP TS 24.587: "Vehicle-to-Everything (V2X) services in 5G System (5GS), Stage 3". +- [17] 3GPP TS 33.401: "3GPP System Architecture Evolution (SAE); Security Architecture". +- [18] 3GPP TS 23.304: "Proximity based Services (ProSe) in the 5G System (5GS)". +- [19] IETF RFC 1951: "DEFLATE Compressed Data Format Specification version 1.3". + +- [20] IETF RFC 3485: "The Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Static Dictionary for Signaling Compression (SigComp)". +- [21] IETF RFC 1979: "PPP Deflate Protocol". +- [22] 3GPP TS 38.351: "NR; Sidelink Relay Adaptation Protocol (SRAP) Specification". +- [23] 3GPP TS 23.501: "System Architecture for the 5G System; 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]. + +**AM DRB:** a data radio bearer which utilizes RLC AM. + +**AM MRB:** an MRB associated with at least one AM RLC bearer for PTP transmission. + +**Broadcast MRB:** a radio bearer configured for MBS broadcast delivery. + +**DAPS bearer:** a bearer whose radio protocols are located in both the source gNB and the target gNB during DAPS handover to use both source gNB and target gNB resources. + +**Delay-critical PDCP SDU:** if *pdu-SetDiscard* is not configured, a PDCP SDU for which the remaining time till *discardTimer* expiry is less than the *remainingTimeThreshold*. If *pdu-SetDiscard* is configured, a PDCP SDU belonging to a PDU Set of which at least one PDCP SDU has the remaining time till *discardTimer* expiry less than the *remainingTimeThreshold*. + +**MBS Radio Bearer:** a radio bearer that is configured for MBS delivery. + +**Multicast MRB:** a radio bearer configured for MBS multicast delivery. + +**Multi-path:** Mode of operation of a remote UE in RRC\_CONNECTED configured with one direct path on which the UE connects to the gNB using NR Uu and one indirect path on which the UE connects to the same gNB via another UE using PC5 unicast link or Non-3GPP Connection. + +**Multi-path split bearer:** In multi-path, a bearer in which one PDCP entity is mapped to one or more (direct) Uu RLC entities and either one SRAP entity of a SL indirect path or non-3GPP connectivity. + +**N3C indirect path:** In multi-path, the indirect path on which the remote UE connects to the network via a relay UE using non-3GPP connectivity. + +**Non-split bearer:** a bearer whose radio protocols are located in either the MgNB or the SgNB to use MgNB or SgNB resource, respectively. + +**NR sidelink communication:** AS functionality enabling at least V2X communication as defined in TS 23.287 [13] and ProSe communication (including ProSe non-Relay, UE-to-Network Relay, and UE-to-UE Relay communication) as defined in TS 23.304 [18], between two or more nearby UEs, using NR technology but not traversing any network node. + +**NR sidelink discovery:** AS functionality enabling ProSe non-Relay Discovery, ProSe UE-to-Network Relay discovery, and ProSe UE-to-UE Relay discovery for Proximity based Services as defined in TS 23.304 [18] between two or more nearby UEs, using NR technology but not traversing any network node. + +**NR sidelink transmission:** any NR Sidelink-based transmission, including both transmission for NR sidelink discovery and transmission for NR sidelink communication. + +**PDCP data volume:** the amount of data available for transmission in a PDCP entity. + +**PDU Set:** one or more PDUs carrying the payload of one unit of information generated at the application level (e.g. frame(s) or video slice(s) etc. for XR services), as defined in TS 23.501 [23]. A PDU in the PDU Set corresponds to a PDCP SDU. + +**Primary Path:** In multi-path for a split DRB, the primary path is configured by RRC to be either the direct path or the indirect path. In multi-path for a split SRB, the primary path is always the direct path. + +**Secondary Path:** In multi-path, for a split DRB, the path (either direct or indirect) which is not configured by RRC as the primary path. In multi-path for a split SRB, the secondary path is always the indirect path (SL or N3C). + +**SL indirect path:** In multi-path, the indirect path on which the L2 U2N Remote UE connects to the network via a L2 U2N Relay UE. + +**Split bearer:** in dual connectivity, a bearer whose radio protocols are located in both the MgNB and the SgNB to use both MgNB and SgNB resources. + +**Split secondary RLC entity:** in dual connectivity, the RLC entity other than the primary RLC entity which is responsible for split bearer operation. If the PDCP entity is associated with two RLC entities, the split secondary RLC entity is the RLC entity other than the primary RLC entity. If the PDCP entity is associated with more than two RLC entities, the split secondary RLC entity is configured by upper layers. + +**UM DRB:** a data radio bearer which utilizes RLC UM. + +**UM MRB:** an MRB associated with only RLC UM. + +**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 another UE 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]. + +| | | +|-------|--------------------------------------------| +| AM | Acknowledged Mode | +| ARP | Address Resolution Protocol | +| CID | Context Identifier | +| DAPS | Dual Active Protocol Stack | +| DRB | Data Radio Bearer carrying user plane data | +| EHC | Ethernet Header Compression | +| FIFO | First In First Out | +| gNB | NR Node B | +| HFN | Hyper Frame Number | +| IETF | Internet Engineering Task Force | +| IP | Internet Protocol | +| MAC | Medium Access Control | +| MAC-I | Message Authentication Code for Integrity | +| MBS | Multicast/Broadcast Services | +| MP | Multi-path | +| MRB | MBS Radio Bearer | +| MTCH | MBS Traffic Channel | +| N3C | Non-3GPP Connectivity | +| PDCP | Packet Data Convergence Protocol | +| PDU | Protocol Data Unit | +| PSI | PDU Set Importance | +| RB | Radio Bearer | +| RFC | Request For Comments | +| RLC | Radio Link Control | + +| | | +|-------|-----------------------------------------------------------------------------------| +| ROHC | RObust Header Compression | +| RR | Radio Resource Control | +| RTP | Real Time Protocol | +| SAP | Service Access Point | +| SCCH | Sidelink Control Channel | +| SDU | Service Data Unit | +| SLRB | Sidelink Radio Bearer carrying NR sidelink communication or NR sidelink discovery | +| SN | Sequence Number | +| SRAP | Sidelink Relay Adaptation Protocol | +| SRB | Signalling Radio Bearer carrying control plane data | +| STCH | Sidelink Traffic Channel | +| TCP | Transmission Control Protocol | +| UDC | Uplink Data Compression | +| UDP | User Datagram Protocol | +| UE | User Equipment | +| UM | Unacknowledged Mode | +| U2N | UE-to-Network | +| X-MAC | Computed MAC-I | + +# --- 4 General + +## 4.1 Introduction + +The present document describes the functionality of the PDCP. + +## 4.2 Architecture + +### 4.2.1 PDCP structure + +Figure 4.2.1-1 represents one possible structure for the PDCP sublayer. Figure 4.2.1-2 represents one possible structure for the PDCP sublayer used in L2 U2N relay case, L2 U2U relay case, and for the indirect path in the case of multi-path with SL indirect path. Figure 4.2.1-3 represents one possible structure for PDCP sublayer used for the indirect path in the case of multi-path with N3C indirect path. These structures should not restrict implementation. The figures are based on the radio interface protocol architecture defined in TS 38.300 [2]. + +NOTE: The structure and interface of non-3GPP connectivity for the case of multi-path with N3C indirect path is out of the scope of this specification. + +![Diagram of PDCP layer structure in UE/NG-RAN showing PDCP entities, RLC channels, and interfaces.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +This diagram illustrates the PDCP layer structure in a UE/NG-RAN. At the top, the 'Radio Bearers' are shown, with two 'PDCP entity' blocks. Each PDCP entity is connected to a 'PDCP-SAP' (Service Access Point) at the top and has a 'C-SAP' (Control Service Access Point) on its left side. Below the PDCP entities, there are 'RLC channels'. Data flows from the PDCP entities down to the RLC channels, represented by 'PDCP - PDU' and 'RLC - SDU' blocks. The RLC channels are connected to 'RLC UM-SAP' (Unacknowledged Mode Service Access Point) and 'RLC AM-SAP' (Acknowledged Mode Service Access Point) at the bottom. The entire PDCP layer is labeled as 'PDCP sublayer' on the right, and the RLC layer below it is labeled as 'RLC sublayer' on the right. The top of the diagram is labeled 'UE/NG-RAN'. + +Diagram of PDCP layer structure in UE/NG-RAN showing PDCP entities, RLC channels, and interfaces. + +Figure 4.2.1-1: PDCP layer, structure view (normal) + +![Diagram of PDCP layer structure in Remote UE/NG-RAN showing PDCP entities, SRAP entity, and interfaces.](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +This diagram illustrates the PDCP layer structure in a Remote UE/NG-RAN. At the top, the 'Radio Bearers' are shown, with two 'PDCP entity' blocks. Each PDCP entity is connected to a 'PDCP-SAP' at the top and has a 'C-SAP' on its left side. Below the PDCP entities, there is an 'SRAP-SAP' (Service Request Access Point). Data flows from the PDCP entities down to the SRAP-SAP, represented by 'PDCP - PDU' and 'SRAP - SDU' blocks. The SRAP-SAP is connected to an 'SRAP entity' block at the bottom. The entire PDCP layer is labeled as 'PDCP sublayer' on the right, and the SRAP layer below it is labeled as 'SRAP sublayer' on the right. The top of the diagram is labeled 'Remote UE/NG-RAN'. + +Diagram of PDCP layer structure in Remote UE/NG-RAN showing PDCP entities, SRAP entity, and interfaces. + +Figure 4.2.1-2: PDCP layer, structure view (L2 U2N relay), L2 U2U relay and SL indirect path in multi-path + +![Diagram of the PDCP layer structure for an N3C indirect path in a multi-path scenario. At the top, 'Remote UE/NG-RAN' is connected to 'Radio Bearers'. Below 'Radio Bearers', there are two 'PDCP entity' blocks within a 'PDCP sublayer'. Each 'PDCP entity' is connected to a 'PDCP-SAP' (Service Access Point). The 'PDCP sublayer' is also connected to a 'C-SAP' (Control Service Access Point) on the left. Below the 'PDCP sublayer', a 'PDCP - PDU' (Protocol Data Unit) is shown. Below the 'PDCP - PDU', there is a 'Non-3GPP-SAP' (Service Access Point). At the bottom, the 'Non-3GPP-SAP' is connected to 'Non-3GPP connectivity'.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +Diagram of the PDCP layer structure for an N3C indirect path in a multi-path scenario. At the top, 'Remote UE/NG-RAN' is connected to 'Radio Bearers'. Below 'Radio Bearers', there are two 'PDCP entity' blocks within a 'PDCP sublayer'. Each 'PDCP entity' is connected to a 'PDCP-SAP' (Service Access Point). The 'PDCP sublayer' is also connected to a 'C-SAP' (Control Service Access Point) on the left. Below the 'PDCP sublayer', a 'PDCP - PDU' (Protocol Data Unit) is shown. Below the 'PDCP - PDU', there is a 'Non-3GPP-SAP' (Service Access Point). At the bottom, the 'Non-3GPP-SAP' is connected to 'Non-3GPP connectivity'. + +**Figure 4.2.1-3: PDCP layer, structure view (N3C indirect path in multi-path)** + +The PDCP sublayer is configured by upper layers TS 38.331 [3]. The PDCP sublayer is used for RBs mapped on DCCH, DTCH, MTCH, SCCH, and STCH type of logical channels. The PDCP sublayer is not used for any other type of logical channels. + +Each RB (except for SRB0 for Uu interface) is associated with one PDCP entity. Each PDCP entity is associated with one, two, three, four, six, or eight RLC entities depending on the RB characteristic (e.g. uni-directional/bi-directional or split/non-split) or RLC mode: + +- For split bearers, each PDCP entity is associated with two UM RLC entities (for same direction), four UM RLC entities (two for each direction), or two AM RLC entities; +- For RBs configured with PDCP duplication, each PDCP entity is associated with N UM RLC entities (for same direction), $2 \times N$ UM RLC entities (N for each direction), or N AM RLC entities, where $2 \leq N \leq 4$ ; +- For DAPS bearers, each PDCP entity is associated with two UM RLC entities (for same direction, one for source and one for target cell), four UM RLC entities (two for each direction on source cell and target cell), or two AM RLC entities (one for source cell and one for target cell); +- For UM MRBs, each PDCP entity is associated with one UM RLC entity (for MTCH or for downlink DTCH), two UM RLC entities (one for MTCH and one for downlink DTCH, or one for downlink DTCH and one for uplink DTCH), or three UM RLC entities (one for MTCH, one for downlink DTCH, and one for uplink DTCH); +- For AM MRBs, each PDCP entity is associated with one AM RLC entity (for downlink DTCH and uplink DTCH), or one UM RLC entity (for MTCH) and one AM RLC entity (for downlink DTCH and uplink DTCH); +- For MP split bearers with SL indirect path, each PDCP entity is associated with one or more Uu RLC entities and one SRAP entity; +- For MP split bearers with N3C indirect path, each PDCP entity is associated with one or more Uu RLC entities and the N3C; +- Otherwise, each PDCP entity is associated with one UM RLC entity, two UM RLC entities (one for each direction), or one AM RLC entity. + +For the case of L2 U2N relay, L2 U2U relay and SL indirect path of multi-path, all PDCP entities are associated with one SRAP entity. For the case of N3C indirect path for multi-path, all PDCP entities are associated with the N3C. + +### 4.2.2 PDCP entities + +The PDCP entities are located in the PDCP sublayer. Several PDCP entities may be defined for a UE. Each PDCP entity is carrying the data of one radio bearer. A PDCP entity is associated either to the control plane or the user plane depending on which radio bearer it is carrying data for. + +Figure 4.2.2-1 represents the functional view of the PDCP entity for the PDCP sublayer; it should not restrict implementation. The figure is based on the radio interface protocol architecture defined in TS 38.300 [2]. + +For split bearers, MP split bearers, and DAPS bearers, routing is performed in the transmitting PDCP entity. + +A PDCP entity associated with DRB can be configured by upper layers TS 38.331 [3] to use header compression or uplink data compression (UDC). A PDCP entity associated with MRB can be configured by upper layers TS 38.331 [3] to use header compression. In this version of the specification, the robust header compression protocol (ROHC), the Ethernet header compression protocol (EHC) and UDC are supported. Each header compression protocol is independently configured for a DRB/MRB. + +![Figure 4.2.2-1: PDCP layer, functional view. This diagram illustrates the functional components and data flow of a PDCP entity for both transmission and reception. On the left, the 'Transmitting PDCP entity' (UE/NG-RAN/UE A) shows data flow from top to bottom: Transmission buffer (Sequence numbering), Header or uplink data Compression, Packets associated to a PDCP SDU, Integrity Protection, Ciphering, Add PDCP header, and Routing/Duplication. On the right, the 'Receiving PDCP entity' (NG-RAN/UE/UE B) shows data flow from bottom to top: Remove PDCP Header, Deciphering, Integrity Verification, Reception buffer (Reordering, Duplicate discarding), Packets associated to a PDCP SDU, and Header or uplink data Decompression. A central 'Radio Interface (Uu/PC5/non-3GPP)' connects the two entities. Arrows indicate the direction of data flow, with labels 'Packets associated to a PDCP SDU' and 'Packets not associated to a PDCP SDU'.](4636adff5682a064f0ae5f13a1d464a6_img.jpg) + +Figure 4.2.2-1: PDCP layer, functional view. This diagram illustrates the functional components and data flow of a PDCP entity for both transmission and reception. On the left, the 'Transmitting PDCP entity' (UE/NG-RAN/UE A) shows data flow from top to bottom: Transmission buffer (Sequence numbering), Header or uplink data Compression, Packets associated to a PDCP SDU, Integrity Protection, Ciphering, Add PDCP header, and Routing/Duplication. On the right, the 'Receiving PDCP entity' (NG-RAN/UE/UE B) shows data flow from bottom to top: Remove PDCP Header, Deciphering, Integrity Verification, Reception buffer (Reordering, Duplicate discarding), Packets associated to a PDCP SDU, and Header or uplink data Decompression. A central 'Radio Interface (Uu/PC5/non-3GPP)' connects the two entities. Arrows indicate the direction of data flow, with labels 'Packets associated to a PDCP SDU' and 'Packets not associated to a PDCP SDU'. + +Figure 4.2.2-1: PDCP layer, functional view + +Figure 4.2.2-2 represents the functional view of the PDCP entity associated with the DAPS bearer for the PDCP sublayer; it should not restrict implementation. The figure is based on the radio interface protocol architecture defined in TS 38.300 [2]. + +For DAPS bearers, the PDCP entity is configured with two sets of security functions and keys and two sets of header compression protocols. + +![Figure 4.2.2-2: PDCP layer associated with DAPS bearer, functional view. The diagram shows the transmitting and receiving PDCP entities for a DAPS bearer. The transmitting entity (left) receives data from the UE, processes it through a transmission buffer with sequence numbering, header compression, integrity protection, and ciphering, then adds a PDCP header and routes it. The receiving entity (right) receives data from the radio interface, removes the PDCP header, decipheres it, verifies integrity, and processes it through a reception buffer for reordering and duplicate discarding before decompressing the header and sending it to the UE. Arrows indicate the flow of packets, distinguishing between those associated with a PDCP SDU and those not.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +Figure 4.2.2-2: PDCP layer associated with DAPS bearer, functional view. The diagram shows the transmitting and receiving PDCP entities for a DAPS bearer. The transmitting entity (left) receives data from the UE, processes it through a transmission buffer with sequence numbering, header compression, integrity protection, and ciphering, then adds a PDCP header and routes it. The receiving entity (right) receives data from the radio interface, removes the PDCP header, decipheres it, verifies integrity, and processes it through a reception buffer for reordering and duplicate discarding before decompressing the header and sending it to the UE. Arrows indicate the flow of packets, distinguishing between those associated with a PDCP SDU and those not. + +Figure 4.2.2-2: PDCP layer associated with DAPS bearer, functional view + +## 4.3 Services + +### 4.3.1 Services provided to upper layers + +The PDCP layer provides its services to the RRC or SDAP layers. The following services are provided by PDCP to upper layers: + +- transfer of user plane data; +- transfer of control plane data; +- header compression; +- uplink data compression; +- ciphering; +- integrity protection. + +The maximum supported size of a PDCP SDU is 9000 bytes. The maximum supported size of a PDCP Control PDU is 9000 bytes. + +### 4.3.2 Services expected from lower layers + +A PDCP entity expects the following services from lower layers per RLC entity (for a detailed description see TS 38.322 [5]): + +- acknowledged data transfer service, including indication of successful delivery of PDCP PDUs; +- unacknowledged data transfer service. + +A PDCP entity expects the following service from SRAP entity (for a detailed description see TS 38.351 [22]), if the PDCP entity is associated with an SRAP entity: + +- data transfer. + +A PDCP entity expects the following service from the N3C if the PDCP entity is associated with the N3C: + +- data transfer. + +## 4.4 Functions + +The PDCP layer supports the following functions: + +- transfer of data (user plane or control plane); +- maintenance of PDCP SNs; +- header compression and decompression using the ROHC protocol; +- header compression and decompression using the EHC protocol; +- uplink data compression and decompression using the UDC protocol; +- ciphering and deciphering; +- integrity protection and integrity verification; +- timer based SDU discard; +- PDU Set discard; +- PSI based SDU discard; +- for split bearers and DAPS bearer, routing; +- duplication; +- reordering and in-order delivery; +- out-of-order delivery; +- duplicate discarding. + +# --- 5 Procedures + +## 5.1 PDCP entity handling + +### 5.1.1 PDCP entity establishment + +When upper layers request a PDCP entity establishment for a radio bearer for Uu or PC5 interface; or for NR sidelink communication for groupcast and broadcast or for sidelink SRB4, when receiving the first PDCP PDU, and there is not yet a corresponding PDCP entity, the UE shall: + +- establish a PDCP entity for the radio bearer; +- set the state variables of the PDCP entity to initial values; +- follow the procedures in clause 5.2. + +NOTE: The receiving PDCP entity of sidelink SRB0 and sidelink SRB1 is established same as NR sidelink groupcast and broadcast. + +### 5.1.2 PDCP entity re-establishment + +When upper layers request a PDCP entity re-establishment, the UE shall additionally perform once the procedures described in this clause for Uu or PC5 interface. After performing the procedures in this clause, the UE shall follow the procedures in clause 5.2. + +When upper layers request a PDCP entity re-establishment, the transmitting PDCP entity shall: + +- for UM DRBs and AM DRBs, reset the ROHC protocol for uplink and start with an IR state in U-mode (as defined in RFC 3095 [8] and RFC 4815 [9]) if *drb-ContinueROHC* is not configured in TS 38.331 [3]; +- for UM DRBs and AM DRBs, reset the EHC protocol for uplink if *drb-ContinueEHC-UL* is not configured in TS 38.331 [3]; +- for AM DRBs, reset the UDC compression buffer to all zeros and prefill the dictionary if *drb-ContinueUDC* is not configured in TS 38.331 [3]; +- for SRBs and UM DRBs, set TX\_NEXT to the initial value; +- for SRBs, discard all stored PDCP SDUs and PDCP PDUs; +- apply the ciphering algorithm and key provided by upper layers during the PDCP entity re-establishment procedure; +- apply the integrity protection algorithm and key provided by upper layers during the PDCP entity re-establishment procedure; +- for UM DRBs, for each PDCP SDU already associated with a PDCP SN but for which a corresponding PDU has not previously been submitted to lower layers, and; +- for AM DRBs for Uu interface whose PDCP entities were suspended, from the first PDCP SDU for which the successful delivery of the corresponding PDCP Data PDU has not been confirmed by lower layers, for each PDCP SDU already associated with a PDCP SN: + - consider the PDCP SDUs as received from upper layer; + - perform transmission of the PDCP SDUs in ascending order of the COUNT value associated to the PDCP SDU prior to the PDCP re-establishment without restarting the *discardTimer* or the *discardTimerForLowImportance*, as specified in clause 5.2.1; +- for AM DRBs whose PDCP entities were not suspended, from the first PDCP SDU for which the successful delivery of the corresponding PDCP Data PDU has not been confirmed by lower layers, perform retransmission or transmission of all the PDCP SDUs already associated with PDCP SNs in ascending order of the COUNT values associated to the PDCP SDU prior to the PDCP entity re-establishment as specified below: + - perform header compression of the PDCP SDU using ROHC as specified in the clause 5.7.4 and/or using EHC as specified in the clause 5.12.4; + - If *drb-ContinueUDC* is configured and if the PDCP SDU has been compressed before: + - submit the PDCP SDU previously compressed to integrity protection and ciphering function; + - else: + - perform uplink data compression of the PDCP SDU as specified in clause 5.14.4, and submit the PDCP SDU to integrity protection and ciphering function; + - perform integrity protection and ciphering of the PDCP SDU using the COUNT value associated with this PDCP SDU as specified in the clause 5.9 and 5.8; + - submit the resulting PDCP Data PDU to lower layer, as specified in clause 5.2.1. + +When upper layers request a PDCP entity re-establishment, the receiving PDCP entity shall: + +- process the PDCP Data PDUs that are received from lower layers due to the re-establishment of the lower layers, as specified in the clause 5.2.2.1; +- for SRBs, discard all stored PDCP SDUs and PDCP PDUs; +- for SRBs, UM DRBs and UM MRBs, if *t-Reordering* is running: + - stop and reset *t-Reordering*; + +- for UM DRBs and UM MRBs, deliver all stored PDCP SDUs to the upper layers in ascending order of associated COUNT values after performing header decompression; +- for AM DRBs and AM MRBs for Uu interface, perform header decompression using ROHC for all stored PDCP SDUs if *drb-ContinueROHC* is not configured in TS 38.331 [3]; +- for AM DRBs for PC5 interface, perform header decompression using ROHC for all stored PDCP IP SDUs; +- for AM DRBs and AM MRBs for Uu interface, perform header decompression using EHC for all stored PDCP SDUs if *drb-ContinueEHC-DL* is not configured in TS 38.331 [3]; +- for UM DRBs, AM DRBs, UM MRBs and AM MRBs, reset the ROHC protocol for downlink and start with NC state in U-mode (as defined in RFC 3095 [8] and RFC 4815 [9]) if *drb-ContinueROHC* is not configured in TS 38.331 [3]; +- for UM DRBs, AM DRBs, UM MRBs and AM MRBs, reset the EHC protocol for downlink if *drb-ContinueEHC-DL* is not configured in TS 38.331 [3]; +- for SRBs and UM DRBs, set RX\_NEXT and RX\_DELIV to the initial value; +- for UM MRBs and AM MRBs, set RX\_NEXT and RX\_DELIV to the initial value if *initialRX-DELIV* is configured in TS 38.331 [3]; +- apply the ciphering algorithm and key provided by upper layers during the PDCP entity re-establishment procedure; +- apply the integrity protection algorithm and key provided by upper layers during the PDCP entity re-establishment procedure. + +NOTE 1: After PDCP re-establishment on a sidelink SRB/DRB, UE determines when to transmit and receive with the new key and discard the old key as specified in TS 33.536 [14]. + +NOTE 2: At PDCP re-establishment, the MRB type (i.e. UM MRB or AM MRB) is determined by the target configuration. + +### 5.1.3 PDCP entity release + +When upper layers request a PDCP entity release for a radio bearer for Uu or PC5 interface, the UE shall: + +- discard all stored PDCP SDUs and PDCP PDUs in the transmitting PDCP entity; +- for UM DRBs, AM DRBs, UM MRBs and AM MRBs, deliver the PDCP SDUs stored in the receiving PDCP entity to upper layers in ascending order of associated COUNT values after performing header decompression, if not decompressed before; +- release the PDCP entity for the radio bearer. + +NOTE: For NR sidelink communication for groupcast and broadcast or for sidelink SRB4, the receiving PDCP entity release for an SLRB is up to UE implementation. + +### 5.1.4 PDCP entity suspend + +When upper layers request a PDCP entity suspend, the transmitting PDCP entity shall: + +- set TX\_NEXT to the initial value; +- discard all stored PDCP PDUs; + +When upper layers request a PDCP entity suspend, the receiving PDCP entity shall: + +- if *t-Reordering* is running: + - stop and reset *t-Reordering*; + +- deliver all stored PDCP SDUs to the upper layers in ascending order of associated COUNT values after performing header decompression; +- set RX\_NEXT and RX\_DELIV to the initial value, except for MRB. + +### 5.1.5 PDCP entity reconfiguration + +When upper layers reconfigure the PDCP entity to configure DAPS, the UE shall: + +- establish a ciphering function for the radio bearer and apply the ciphering algorithm and key provided by upper layers for the ciphering function; +- establish an integrity protection function for the radio bearer and apply the integrity protection algorithm and key provided by upper layers for the integrity protection function; +- establish a header compression protocol for the radio bearer and apply the header compression configuration provided by upper layers for the header compression protocol. + +When upper layers reconfigure the PDCP entity to release DAPS, the UE shall: + +- release the ciphering function associated to the released RLC entity for the radio bearer; +- release the integrity protection function associated to the released RLC entity for the radio bearer; +- release the header compression protocol associated to the released RLC entity for the radio bearer. + +NOTE 1: The state variables which control the transmission and reception operation should not be reset, and the timers including *t-Reordering*, *discardTimer*, and *discardTimerForLowImportance* keep running during PDCP entity reconfiguration procedure. + +NOTE 2: Before releasing the header compression protocol associated to the released RLC entity, how to handle all stored PDCP SDUs received from the released RLC entity is left up to UE implementation. + +NOTE 3: No special handling for the header compression protocol is defined to avoid potential security issue (e.g. keystream reuse) for DAPS handover with no security key change. + +## 5.2 Data transfer + +### 5.2.1 Transmit operation + +At reception of a PDCP SDU from upper layers, the transmitting PDCP entity shall: + +- if *discardTimerForLowImportance* is configured and PSI based SDU discard is activated, and the PDCP SDU belongs to a low importance PDU Set: + - start the *discardTimerForLowImportance* associated with this PDCP SDU; +- else: + - start the *discardTimer* associated with this PDCP SDU (if configured). + +NOTE 0: Identification of PSI of a PDU Set and determination of low importance PDU Set are left up to UE implementation. + +For a PDCP SDU received from upper layers, the transmitting PDCP entity shall: + +- associate the COUNT value corresponding to TX\_NEXT to this PDCP SDU; + +NOTE 1: Associating more than half of the PDCP SN space of contiguous PDCP SDUs with PDCP SNs, when e.g., the PDCP SDUs are discarded or transmitted without acknowledgement, may cause HFN desynchronization problem. How to prevent HFN desynchronization problem is left up to UE implementation. + +- perform header compression of the PDCP SDU using ROHC as specified in the clause 5.7.4 and/or using EHC as specified in the clause 5.12.4; +- perform uplink data compression of the PDCP SDU as specified in clause 5.14.4; +- perform integrity protection, and ciphering using the TX\_NEXT as specified in the clause 5.9 and 5.8, respectively; +- set the PDCP SN of the PDCP Data PDU to TX\_NEXT modulo $2^{[pdcp-SN-SizeUL]}$ ; +- increment TX\_NEXT by one; +- submit the resulting PDCP Data PDU to lower layer as specified below. + +When submitting a PDCP PDU to lower layer, the transmitting PDCP entity shall: + +- if the transmitting PDCP entity is associated with one SRAP entity: + - submit the PDCP PDU to the associated SRAP entity; +- else, if the transmitting PDCP entity is associated with one RLC entity: + - submit the PDCP PDU to the associated RLC entity; +- else, if the transmitting PDCP entity is associated with one or more RLC entities and, either one SRAP entity or the N3C: + - if PDCP duplication is activated for the RB: + - if the PDCP PDU is a PDCP Data PDU: + - duplicate the PDCP Data PDU and submit the PDCP Data PDU to both the primary path and secondary path, including any associated Uu RLC entities activated for PDCP duplication; + - else: + - submit the PDCP Control PDU to the primary path; + - else (i.e., PDCP duplication is deactivated for the RB): + - if the total amount of PDCP data volume, RLC data volume pending for initial transmission (as specified in TS 38.322 [5]) in the RLC entity, and data volume pending for either transmission in the N3C (if available) or mapped SL RLC entity associated with the SRAP entity, is equal to or larger than *ul-DataSplitThreshold*: + - submit the PDCP PDU to either the primary path or secondary path; + - else: + - submit the PDCP PDU to the primary path; +- else, if the transmitting PDCP entity is associated with at least two RLC entities: + - if the PDCP duplication is activated for the RB: + - if the PDCP PDU is a PDCP Data PDU: + - duplicate the PDCP Data PDU and submit the PDCP Data PDU to the associated RLC entities activated for PDCP duplication; + - else: + - submit the PDCP Control PDU to the primary RLC entity; + - else (i.e. the PDCP duplication is deactivated for the RB or the RB is a DAPS bearer): + - if the split secondary RLC entity is configured; and + +- if the total amount of PDCP data volume and RLC data volume pending for initial transmission (as specified in TS 38.322 [5]) in the primary RLC entity and the split secondary RLC entity is equal to or larger than *ul-DataSplitThreshold*: + - submit the PDCP PDU to either the primary RLC entity or the split secondary RLC entity; +- else, if the transmitting PDCP entity is associated with the DAPS bearer: + - if the uplink data switching has not been requested: + - submit the PDCP PDU to the RLC entity associated with the source cell; + - else: + - if the PDCP PDU is a PDCP Data PDU: + - submit the PDCP Data PDU to the RLC entity associated with the target cell; + - else: + - if the PDCP Control PDU is associated with source cell: + - submit the PDCP Control PDU to the RLC entity associated with the source cell; + - else: + - submit the PDCP Control PDU to the RLC entity associated with the target cell; +- else: + - submit the PDCP PDU to the primary RLC entity. + +NOTE 2: If the transmitting PDCP entity is associated with two RLC entities, or with one or more RLC entities and either an SRAP entity or the N3C, the UE should minimize the amount of PDCP PDUs submitted to lower layers before receiving request from lower layers and minimize the PDCP SN gap between PDCP PDUs submitted to two associated RLC entities, or to the RLC entity and either the SRAP entity or the N3C, to minimize PDCP reordering delay in the receiving PDCP entity. + +### 5.2.2 Receive operation + +#### 5.2.2.1 Actions when a PDCP Data PDU is received from lower layers + +In this clause, following definitions are used: + +- HFN(State Variable): the HFN part (i.e. the number of most significant bits equal to HFN length) of the State Variable; +- SN(State Variable): the SN part (i.e. the number of least significant bits equal to PDCP SN length) of the State Variable; +- RCVD\_SN: the PDCP SN of the received PDCP Data PDU, included in the PDU header; +- RCVD\_HFN: the HFN of the received PDCP Data PDU, calculated by the receiving PDCP entity; +- RCVD\_COUNT: the COUNT of the received PDCP Data PDU = [RCVD\_HFN, RCVD\_SN]. + +At reception of a PDCP Data PDU from lower layers, the receiving PDCP entity shall determine the COUNT value of the received PDCP Data PDU, i.e. RCVD\_COUNT, as follows: + +- if RCVD\_SN < SN(RX\_DELIV) – Window\_Size: + - RCVD\_HFN = HFN(RX\_DELIV) + 1. +- else if RCVD\_SN >= SN(RX\_DELIV) + Window\_Size: + - RCVD\_HFN = HFN(RX\_DELIV) – 1. + +- else: + - RCVD\_HFN = HFN(RX\_DELIV); + - RCVD\_COUNT = [RCVD\_HFN, RCVD\_SN]. + +After determining the COUNT value of the received PDCP Data PDU = RCVD\_COUNT, the receiving PDCP entity shall: + +- perform deciphering and integrity verification of the PDCP Data PDU using COUNT = RCVD\_COUNT; + - if integrity verification fails: + - indicate the integrity verification failure to upper layer; + - discard the PDCP Data PDU and consider it as not received; +- if RCVD\_COUNT < RX\_DELIV; or +- if the PDCP Data PDU with COUNT = RCVD\_COUNT has been received before: + - discard the PDCP Data PDU; + +If the received PDCP Data PDU with COUNT value = RCVD\_COUNT is not discarded above, the receiving PDCP entity shall: + +- store the resulting PDCP SDU in the reception buffer; +- if RCVD\_COUNT >= RX\_NEXT: + - update RX\_NEXT to RCVD\_COUNT + 1. +- if *outOfOrderDelivery* is configured: + - deliver the resulting PDCP SDU to upper layers after performing header decompression using EHC. +- if RCVD\_COUNT = RX\_DELIV: + - deliver to upper layers in ascending order of the associated COUNT value after performing header decompression, if not decompressed before; + - all stored PDCP SDU(s) with consecutively associated COUNT value(s) starting from COUNT = RX\_DELIV; + - update RX\_DELIV to the COUNT value of the first PDCP SDU which has not been delivered to upper layers, with COUNT value > RX\_DELIV; +- if *t-Reordering* is running, and if RX\_DELIV >= RX\_REORD: + - stop and reset *t-Reordering*. +- if *t-Reordering* is not running (includes the case when *t-Reordering* is stopped due to actions above), and RX\_DELIV < RX\_NEXT: + - update RX\_REORD to RX\_NEXT; + - start *t-Reordering*. + +#### 5.2.2.2 Actions when a *t-Reordering* expires + +When *t-Reordering* expires, the receiving PDCP entity shall: + +- deliver to upper layers in ascending order of the associated COUNT value after performing header decompression, if not decompressed before; + - all stored PDCP SDU(s) with associated COUNT value(s) < RX\_REORD; + +- all stored PDCP SDU(s) with consecutively associated COUNT value(s) starting from RX\_REORD; +- update RX\_DELIV to the COUNT value of the first PDCP SDU which has not been delivered to upper layers, with COUNT value $\geq$ RX\_REORD; +- if RX\_DELIV < RX\_NEXT: + - update RX\_REORD to RX\_NEXT; + - start *t-Reordering*. + +#### 5.2.2.3 Actions when the value of *t-Reordering* is reconfigured + +When the value of the *t-Reordering* is reconfigured by upper layers while the *t-Reordering* is running, the receiving PDCP entity shall: + +- update RX\_REORD to RX\_NEXT; +- stop and restart *t-Reordering*. + +### 5.2.3 Sidelink transmit operation + +For NR sidelink transmission of the SLRB, the UE shall follow the procedures in clause 5.2.1 with following modification: + +- perform the header compression using ROHC as specified in clause 5.7.4, if SDU Type is IP; +- set the PDCP SN of the PDCP Data PDU to TX\_NEXT modulo $2^{[sl-PDCP-SN-Size]}$ ; +- if the transmitting PDCP entity is associated with two RLC entities: + - consider PDCP duplication as activated; + - submit the PDCP control PDU to one of the associated RLC entities. + +NOTE: How to decide to which RLC entity a PDCP control PDU is submitted is left up to UE implementation. + +### 5.2.4 Sidelink receive operation + +For sidelink reception of the SLRB, the UE shall follow the procedures in clause 5.2.2 with following modification: + +- perform the header decompression using ROHC as specified in clause 5.7.5, if SDU Type is IP. + +NOTE: For reception of sidelink SRBs except sidelink SRB3, the UE may deliver the PDCP SDU to the upper layer along with an indication whether it is PC5-S message or NR sidelink discovery message. + +## 5.3 SDU discard + +When the successful delivery of a PDCP SDU is confirmed by PDCP status report, the transmitting PDCP entity shall discard the PDCP SDU along with the corresponding PDCP Data PDU. + +When the *discardTimer* or *discardTimerForLowImportance* expires for a PDCP SDU, the transmitting PDCP entity shall: + +- if *pdu-SetDiscard* is configured: + - discard all PDCP SDUs belonging to the PDU Set to which the PDCP SDU belongs along with the corresponding PDCP Data PDUs; + +NOTE 1: PDCP SDUs subsequently received from upper layers are also discarded if they belong to the PDU Set. + +- else: + - discard the PDCP SDU along with the corresponding PDCP Data PDU. + +If the corresponding PDCP Data PDU has already been submitted to lower layers, the discard is indicated to lower layers. + +For SRBs, when upper layers request a PDCP SDU discard, the PDCP entity shall discard all stored PDCP SDUs and PDCP PDUs. + +NOTE 2: Discarding a PDCP SDU already associated with a PDCP SN causes a SN gap in the transmitted PDCP Data PDUs, which increases PDCP reordering delay in the receiving PDCP entity. It is up to UE implementation how to minimize SN gap after SDU discard. + +## 5.4 Status reporting + +### 5.4.1 Transmit operation + +For AM DRBs configured by upper layers to send a PDCP status report in the uplink (*statusReportRequired* in TS 38.331 [3]), the receiving PDCP entity shall trigger a PDCP status report when: + +- upper layer requests a PDCP entity re-establishment; +- upper layer requests a PDCP data recovery; +- upper layer requests a uplink data switching; +- upper layer reconfigures the PDCP entity to release DAPS and *daps-SourceRelease* is configured in TS 38.331 [3]. + +For UM DRBs configured by upper layers to send a PDCP status report in the uplink (*statusReportRequired* in TS 38.331 [3]), the receiving PDCP entity shall trigger a PDCP status report when: + +- upper layer requests a uplink data switching. + +For AM DRBs in the sidelink, the receiving PDCP entity shall trigger a PDCP status report when: + +- upper layer requests a PDCP entity re-establishment. + +For AM MRBs configured by upper layers to send a PDCP status report in the uplink (*statusReportRequired* in TS 38.331 [3]), the receiving PDCP entity shall trigger a PDCP status report when: + +- upper layer requests a PDCP entity re-establishment; +- upper layer requests a PDCP data recovery. + +If a PDCP status report is triggered, the receiving PDCP entity shall: + +- compile a PDCP status report as indicated below by: + - setting the FMC field to RX\_DELIV; + - if RX\_DELIV < RX\_NEXT: + - allocating a Bitmap field of length in bits equal to the number of COUNTs from and not including the first missing PDCP SDU up to and including the last out-of-sequence PDCP SDUs, rounded up to the next multiple of 8, or up to and including a PDCP SDU for which the resulting PDCP Control PDU size is equal to 9000 bytes, whichever comes first; + - setting in the bitmap field as '0' for all PDCP SDUs that have not been received, and optionally PDCP SDUs for which decompression have failed; + - setting in the bitmap field as '1' for all PDCP SDUs that have been received; +- submit the PDCP status report to lower layers as the first PDCP PDU for transmission via the transmitting PDCP entity as specified in clause 5.2.1 for Uu interface and in clause 5.2.3 for PC5 interface. + +### 5.4.2 Receive operation + +For AM DRBs, when a PDCP status report is received in the downlink or in the sidelink, the transmitting PDCP entity shall: + +- consider for each PDCP SDU, if any, with the bit in the bitmap set to '1', or with the associated COUNT value less than the value of FMC field as successfully delivered, and discard the PDCP SDU as specified in clause 5.3. + +## 5.5 Data recovery + +For AM DRBs, when upper layers request a PDCP data recovery for a radio bearer, the transmitting PDCP entity shall: + +- perform retransmission of all the PDCP Data PDUs previously submitted to re-established or released AM RLC entities in ascending order of the associated COUNT values for which the successful delivery has not been confirmed by lower layers, following the data submission procedure in clause 5.2.1. + +After performing the above procedures, the transmitting PDCP entity shall follow the procedures in clause 5.2.1. + +## 5.6 Data volume calculation + +For the purpose of MAC buffer status reporting, the transmitting PDCP entity shall consider the following as PDCP data volume: + +- the PDCP SDUs for which no PDCP Data PDUs have been constructed; +- the PDCP Data PDUs that have not been submitted to lower layers; +- the PDCP Control PDUs; +- for AM DRBs, the PDCP SDUs to be retransmitted according to clause 5.1.2 and clause 5.13; +- for AM DRBs, the PDCP Data PDUs to be retransmitted according to clause 5.5. + +If the transmitting PDCP entity is associated with at least two RLC entities, or with an RLC entity and either an SRAP entity or the N3C, when indicating the PDCP data volume to a MAC entity for BSR triggering and Buffer Size calculation (as specified in TS 38.321 [4] and TS 36.321 [12]), the transmitting PDCP entity shall: + +- if the PDCP duplication is activated for the RB: + - indicate the PDCP data volume to the MAC entity associated with the primary RLC entity or primary path; + - indicate the PDCP data volume excluding the PDCP Control PDU to the MAC entity associated with the RLC entity other than the primary RLC entity or primary path activated for PDCP duplication; + - indicate the PDCP data volume as 0 to the MAC entity associated with RLC entity deactivated for PDCP duplication; +- else (i.e. the PDCP duplication is deactivated for the RB or the RB is a DAPS bearer): + - if the split secondary RLC entity is configured; and + - if the total amount of PDCP data volume and RLC data volume pending for initial transmission (as specified in TS 38.322 [5]) in the primary RLC entity and the split secondary RLC entity is equal to or larger than *ul-DataSplitThreshold*: + - indicate the PDCP data volume to both the MAC entity associated with the primary RLC entity and the MAC entity associated with the split secondary RLC entity; + - indicate the PDCP data volume as 0 to the MAC entity associated with RLC entity other than the primary RLC entity and the split secondary RLC entity; + - else, if the total amount of PDCP data volume, RLC data volume pending for initial transmission (as specified in TS 38.322 [5]) in the RLC entity, and data volume pending for either transmission in the N3C (if + +available), or mapped SL RLC entity associated with the SRAP entity, is equal to or larger than *ul-DataSplitThreshold*: + +- indicate the PDCP data volume to the MAC entity; +- else, if the transmitting PDCP entity is associated with the DAPS bearer: + - if the uplink data switching has not been requested: + - indicate the PDCP data volume to the MAC entity associated with the source cell; + - else: + - indicate the PDCP data volume excluding the PDCP Control PDU for interspersed ROHC feedback associated with the source cell to the MAC entity associated with the target cell; + - indicate the PDCP data volume of PDCP Control PDU for interspersed ROHC feedback associated with the source cell to the MAC entity associated with the source cell; +- else: + - indicate the PDCP data volume to the MAC entity associated with the primary RLC entity or primary path; + - indicate the PDCP data volume as 0 to the MAC entity associated with the RLC entity other than the primary RLC entity or primary path. + +## 5.7 Robust header compression and decompression + +### 5.7.1 Supported header compression protocols and profiles + +The ROHC protocol is based on the Robust Header Compression (ROHC) framework defined in RFC 5795 [7]. There are multiple ROHC algorithms, called profiles, defined for the ROHC framework. Each profile is specific to the particular network layer, transport layer or upper layer protocol combination e.g. TCP/IP and RTP/UDP/IP. + +The detailed definition of the ROHC channel is specified as part of the ROHC framework defined in RFC 5795 [7]. This includes how to multiplex different flows (header compressed or not) over the ROHC channel, as well as how to associate a specific IP flow with a specific context state during initialization of the compression algorithm for that flow. + +The implementation of the functionality of the ROHC framework and of the functionality of the supported header compression profiles is not covered in this specification. + +In this version of the specification the support of the following profiles is described: + +**Table 5.7.1-1: Supported ROHC protocols and profiles** + +| Profile Identifier | Usage | Reference | +|--------------------|----------------|--------------------| +| 0x0000 | No compression | RFC 5795 | +| 0x0001 | RTP/UDP/IP | RFC 3095, RFC 4815 | +| 0x0002 | UDP/IP | RFC 3095, RFC 4815 | +| 0x0003 | ESP/IP | RFC 3095, RFC 4815 | +| 0x0004 | IP | RFC 3843, RFC 4815 | +| 0x0006 | TCP/IP | RFC 6846 | +| 0x0101 | RTP/UDP/IP | RFC 5225 | +| 0x0102 | UDP/IP | RFC 5225 | +| 0x0103 | ESP/IP | RFC 5225 | +| 0x0104 | IP | RFC 5225 | + +### 5.7.2 Configuration of ROHC + +PDCP entities associated with DRBs and MRBs can be configured by upper layers TS 38.331 [3] to use ROHC. Each PDCP entity carrying user plane data may be configured to use ROHC. PDCP entities associated with sidelink DRBs + +can be configured to use ROHC for IP SDUs. For DRBs and MRBs other than DAPS bearers, the PDCP entity uses at most one ROHC compressor instance and at most one ROHC decompressor instance. For DAPS bearers, the PDCP entity uses at most one ROHC compressor instance (i.e. use the ROHC compressor instance for source cell before uplink data switching, and use the ROHC compressor instance for target cell after uplink data switching) and at most two ROHC decompressor instances. + +### 5.7.3 Protocol parameters + +RFC 5795 [7] has configuration parameters that are mandatory and that must be configured by upper layers between compressor and decompressor peers ; these parameters define the ROHC channel. The ROHC channel is a unidirectional channel, i.e. if *rohc* is configured there is one channel for the downlink and one for the uplink, and if *uplinkOnlyROHC* is configured there is only one channel for the uplink. There is thus one set of parameters for each channel, and if *rohc* is configured the same values shall be used for both channels belonging to the same PDCP entity. + +These parameters are categorized in two different groups, as defined below: + +- M: Mandatory and configured by upper layers; +- N/A: Not used in this specification. + +The usage and definition of the parameters shall be as specified below. + +- MAX\_CID (M): This is the maximum CID value that can be used. One CID value shall always be reserved for uncompressed flows. The parameter MAX\_CID is configured by upper layers (*maxCID* in TS 38.331 [3]); +- LARGE\_CIDS: This value is not configured by upper layers, but rather it is inferred from the configured value of MAX\_CID according to the following rule: + - If MAX\_CID > 15 then LARGE\_CIDS = TRUE else LARGE\_CIDS = FALSE; +- PROFILES (M): Profiles are used to define which profiles are allowed to be used by the UE. The list of supported profiles is described in clause 5.7.1. The parameter PROFILES is configured by upper layers (*profiles* for uplink and downlink, *sl-RoHC-Profiles* in *SidelinkPreconfigNR* for sidelink in TS 38.331 [3]); +- FEEDBACK\_FOR (N/A): This is a reference to the channel in the opposite direction between two compression endpoints and indicates to what channel any feedback sent refers to. Feedback received on one ROHC channel for this PDCP entity shall always refer to the ROHC channel in the opposite direction for this same PDCP entity; +- MRRU (N/A): ROHC segmentation is not used. + +### 5.7.4 Header compression using ROHC + +If ROHC is configured, the ROHC protocol generates two types of output packets: + +- ROHC compressed packets, each associated with one PDCP SDU; +- standalone packets not associated with a PDCP SDU, i.e. interspersed ROHC feedback. + +A ROHC compressed packet is associated with the same PDCP SN and COUNT value as the related PDCP SDU. The header compression is not applicable to the SDAP header and the SDAP Control PDU if included in the PDCP SDU. + +For DAPS bearers, the PDCP entity shall perform the header compression for the PDCP SDU using the ROHC protocol either configured for the source cell or configured for the target cell, based on to which cell the PDCP SDU is transmitted. + +Interspersed ROHC feedback are not associated with a PDCP SDU. They are not associated with a PDCP SN and are not ciphered. + +NOTE 1: If the MAX\_CID number of ROHC contexts are already established for the compressed flows and a new IP flow does not match any established ROHC context, the compressor should associate the new IP flow with one of the ROHC CIDs allocated for the existing compressed flows or send PDCP SDUs belonging to the IP flow as uncompressed packet. + +NOTE 2: For downlink, the ROHC protocol of the target cell should maintain the IR state if operating in U-mode and O-mode during DAPS handover before release of source cell. + +### 5.7.5 Header decompression using ROHC + +If ROHC is configured by upper layers for PDCP entities associated with user plane data, the PDCP Data PDUs are decompressed by the ROHC protocol after performing deciphering as explained in clause 5.8. The header decompression is not applicable to the SDAP header and the SDAP Control PDU if included in the PDCP Data PDU. + +For DAPS bearers, the PDCP entity shall perform the header decompression for the PDCP SDU using the ROHC protocol either configured for the source cell or configured for the target cell, based on from which cell the PDCP SDU is received. + +### 5.7.6 PDCP Control PDU for interspersed ROHC feedback + +#### 5.7.6.1 Transmit Operation + +When an interspersed ROHC feedback is generated by the ROHC protocol, the transmitting PDCP entity shall: + +- submit to lower layers the corresponding PDCP Control PDU as specified in clause 6.2.3.2 i.e. without associating a PDCP SN, nor performing ciphering, as specified in clause 5.2.1. + +#### 5.7.6.2 Receive Operation + +At reception of a PDCP Control PDU for interspersed ROHC feedback from lower layers, the receiving PDCP entity shall: + +- deliver the corresponding interspersed ROHC feedback to the associated ROHC protocol without performing deciphering. + +## 5.8 Ciphering and deciphering + +The ciphering function includes both ciphering and deciphering and is performed in PDCP, if configured. The data unit that is ciphered is the MAC-I (see clause 6.3.4) and the data part of the PDCP Data PDU (see clause 6.3.3) except the SDAP header and the SDAP Control PDU if included in the PDCP SDU. The ciphering is not applicable to PDCP Control PDUs. + +For downlink and uplink, the ciphering algorithm and key to be used by the PDCP entity are configured by upper layers TS 38.331 [3] and the ciphering method shall be applied as specified in TS 33.501 [6]. + +The ciphering function is activated/suspended/resumed by upper layers TS 38.331 [3]. When security is activated and not suspended, the ciphering function shall be applied to all PDCP Data PDUs indicated by upper layers TS 38.331 [3] for the downlink and the uplink, respectively. + +For DAPS bearers, the PDCP entity shall perform the ciphering or deciphering for the PDCP SDU using the ciphering algorithm and key either configured for the source cell or configured for the target cell, based on to/from which cell the PDCP SDU is transmitted/received. + +For downlink and uplink ciphering and deciphering, the parameters that are required by PDCP for ciphering are defined in TS 33.501 [6] and are input to the ciphering algorithm. The required inputs to the ciphering function include the COUNT value, and DIRECTION (direction of the transmission: set as specified in TS 33.501 [6]). The parameters required by PDCP which are provided by upper layers TS 38.331 [3] are listed below: + +- BEARER (defined as the radio bearer identifier in TS 33.501 [6]. It will use the value RB identity –1 as in TS 38.331 [3]); +- KEY (the ciphering keys for the control plane and for the user plane are $K_{\text{RRCEnc}}$ and $K_{\text{UPEnc}}$ , respectively). + +For NR sidelink communication, the ciphering algorithm and key to be used by the PDCP entity are configured by upper layers as specified in TS 24.587 [16] and the ciphering method shall be applied as specified in TS 33.536 [14]. + +For NR sidelink communication, the ciphering function is activated for sidelink SRBs (except for SL-SRB0) and/or sidelink DRBs for a PC5 unicast link by upper layers, as specified in TS 38.331 [3]. When security is activated for sidelink SRBs, the ciphering function shall be applied to all PDCP Data PDUs (except for carrying Direct Security Mode Command message as specified in TS 33.536 [14]) for the sidelink SRBs which belong to the PC5 unicast link. When security is activated for sidelink DRBs, the ciphering function shall be applied to all PDCP Data PDUs for the sidelink DRBs which belong to the PC5 unicast link. + +For NR sidelink communication, the ciphering and deciphering function as specified in TS 33.536 [14] is applied with KEY (NRPEK), COUNT, BEARER (LSB 5 bits of LCID with values 1 to 19 associated with the PDCP entity, as specified in TS 38.321 [4]) and DIRECTION (which value shall be set is specified in TS 33.536 [14]) as input. + +The ciphering and deciphering are not applied to MRBs and sidelink SRB4. + +## 5.9 Integrity protection and verification + +The integrity protection function includes both integrity protection and integrity verification and is performed in PDCP, if configured. The data unit that is integrity protected is the PDU header and the data part of the PDU before ciphering. The integrity protection is always applied to PDCP Data PDUs of SRBs. The integrity protection is applied to sidelink SRB1, SRB2 and SRB3. The integrity protection is applied to PDCP Data PDUs of DRBs (including sidelink DRBs for unicast) for which integrity protection is configured. The integrity protection is not applicable to PDCP Control PDUs. + +For downlink and uplink, the integrity protection algorithm and key to be used by the PDCP entity are configured by upper layers TS 38.331 [3] and the integrity protection method shall be applied as specified in TS 33.501 [6] for NR and in TS 33.401 [17] for E-UTRA/EPC. + +The integrity protection function is activated/suspended/resumed by upper layers TS 38.331 [3]. When security is activated and not suspended, the integrity protection function shall be applied to all PDUs including and subsequent to the PDU indicated by upper layers TS 38.331 [3] for the downlink and the uplink, respectively. + +NOTE 1: As the RRC message which activates the integrity protection function is itself integrity protected with the configuration included in this RRC message, this message needs first be decoded by RRC before the integrity protection verification could be performed for the PDU in which the message was received. + +NOTE 2: As the PC5-S message which activates the integrity protection function is itself integrity protected with the configuration included in this PC5-S message, this message needs first be decoded by upper layer before the integrity protection verification could be performed for the PDU in which the message was received. + +For DAPS bearers, the PDCP entity shall perform the integrity protection or verification for the PDCP SDU using the integrity protection algorithm and key either configured for the source cell or configured for the target cell, based on to/from which cell the PDCP SDU is transmitted/received. + +For downlink and uplink integrity protection and verification, the parameters that are required by PDCP for integrity protection are defined in TS 33.501 [6] or TS 33.401 [17] and are input to the integrity protection algorithm. The required inputs to the integrity protection function include the COUNT value, and DIRECTION (direction of the transmission: set as specified in TS 33.501 [6]) or TS 33.401 [17]. The parameters required by PDCP which are provided by upper layers TS 38.331 [3] are listed below: + +- BEARER (defined as the radio bearer identifier in TS 33.501 [6] or TS 33.401 [17]. It will use the value RB identity –1 as in TS 38.331 [3]); +- KEY (the integrity protection keys for the control plane and for the user plane are $K_{RRCint}$ and $K_{UPint}$ , respectively). + +For NR sidelink communication, the integrity protection algorithm and key to be used by the PDCP entity are configured by upper layers TS 24.587 [16] and the integrity protection method shall be applied as specified in TS 33.536 [14]. + +For NR sidelink communication, the integrity protection function is activated for sidelink SRBs and/or sidelink DRBs for a PC5 unicast link by upper layers, as specified in TS 38.331 [3]. When security is activated for sidelink SRBs, the integrity protection function shall be applied to all PDUs including and subsequent to the PDU for the sidelink SRBs which belong to the PC5 unicast link. When security is activated for sidelink DRBs, the integrity protection function + +shall be applied to all PDUs including and subsequent to the PDU for the sidelink DRBs which belong to the PC5 unicast link. + +For the SLRB that needs integrity protection and verification, the parameters that are required by PDCP for integrity protection are defined in TS 33.536 [14] and are input to the integrity protection algorithm. The required inputs to the integrity protection function include the KEY (NRPIK), COUNT, BEARER (LSB 5 bits of LCID with values 1 to 19 associated with the PDCP entity, as specified in TS 38.321 [4]) and DIRECTION (which value shall be set is specified in TS 33.536 [14]). + +At transmission, the UE computes the value of the MAC-I field and at reception it verifies the integrity of the PDCP Data PDU by calculating the X-MAC based on the input parameters as specified above. If the calculated X-MAC corresponds to the received MAC-I, integrity protection is verified successfully. + +The integrity protection and verification are not applied to MRBs and sidelink SRB4. + +## 5.10 Handling of unknown, unforeseen, and erroneous protocol data + +When a PDCP PDU that contains reserved or invalid values is received, the receiving PDCP entity shall: + +- discard the received PDU. + +NOTE: For NR sidelink communication for unicast, the invalid values include the invalid value of $K_{\text{NRP-sess}}$ ID. + +## 5.11 PDCP duplication + +### 5.11.1 Activation/Deactivation of PDCP duplication + +For the PDCP entity configured with *pdcp-Duplication*, the transmitting PDCP entity shall: + +- for SRBs: + - activate the PDCP duplication; +- for DRBs: + - if the activation of PDCP duplication is indicated for the DRB: + - activate the PDCP duplication for the DRB; + - if the activation of PDCP duplication is indicated for at least one associated RLC entities: + - activate the PDCP duplication for the indicated associated RLC entities; + - activate the PDCP duplication for the DRB; + - if the deactivation of PDCP duplication is indicated for the DRB: + - deactivate the PDCP duplication for the DRB; + - if the deactivation of PDCP duplication is indicated for at least one associated RLC entities: + - deactivate the PDCP duplication for the indicated associated RLC entities; + - if all associated RLC entities other than the primary RLC entity are deactivated for PDCP duplication: + - deactivate the PDCP duplication for the DRB. + +### 5.11.2 Duplicate PDU discard + +For the PDCP entity configured with *pdcp-Duplication* or for the PDCP entity associated with two RLC entities for an SLRB, the transmitting PDCP entity shall: + +- if the successful delivery of a PDCP Data PDU is confirmed by one of the associated AM RLC entities and the AM RLC entity is not associated with an SRAP entity: + - indicate to the other AM RLC entities to discard the duplicated PDCP Data PDU; +- if the deactivation of PDCP duplication is indicated for the DRB: + - indicate to the RLC entities other than the primary RLC entity to discard all duplicated PDCP Data PDUs; +- if the deactivation of PDCP duplication is indicated for at least one associated RLC entities: + - indicate to the RLC entities deactivated for PDCP duplication to discard all duplicated PDCP Data PDUs. + +## 5.12 Ethernet header compression and decompression + +### 5.12.1 Supported header compression protocols + +The EHC protocol is based on the Ethernet Header Compression (EHC) framework defined in Annex A. + +### 5.12.2 Configuration of EHC + +PDCP entities associated with DRBs and MRBs can be configured by upper layers TS 38.331 [3] to use EHC. Each PDCP entity carrying user plane data may be configured to use EHC. Every PDCP entity uses at most one EHC compressor instance and at most one EHC decompressor instance. + +### 5.12.3 Protocol parameters + +The usage and definition of the parameters shall be as specified below. + +- MAX\_CID\_EHC\_UL: This is the maximum CID value that can be used for uplink. One CID value shall always be reserved for uncompressed flows. The parameter MAX\_CID\_EHC\_UL is configured by upper layers (*maxCID-EHC-UL* in TS 38.331 [3]); + +### 5.12.4 Header compression using EHC + +If EHC is configured, the EHC protocol generates two types of output packets: + +- EHC compressed packets (i.e. EHC full header packets and EHC compressed header packets), each associated with one PDCP SDU; +- standalone packets not associated with a PDCP SDU, i.e. EHC feedback. + +An EHC compressed packet is associated with the same PDCP SN and COUNT value as the related PDCP SDU. The header compression is not applicable to the SDAP header and the SDAP Control PDU if included in the PDCP SDU. + +EHC feedback are not associated with a PDCP SDU. They are not associated with a PDCP SN and are not ciphered/integrity protected. + +### 5.12.5 Header decompression using EHC + +If EHC is configured by upper layers for PDCP entities associated with user plane data, the PDCP Data PDUs are decompressed by the EHC protocol after performing deciphering and integrity verification as explained in clause 5.8 and 5.9, respectively. The header decompression is not applicable to the SDAP header and the SDAP Control PDU if included in the PDCP Data PDU. + +### 5.12.6 PDCP Control PDU for EHC feedback + +#### 5.12.6.1 Transmit Operation + +When an EHC feedback is generated by the EHC protocol, the transmitting PDCP entity shall: + +- submit to lower layers the corresponding PDCP Control PDU as specified in clause 6.2.3.3 i.e. without associating a PDCP SN, nor performing ciphering/integrity protection. + +#### 5.12.6.2 Receive Operation + +At reception of a PDCP Control PDU for EHC feedback from lower layers, the receiving PDCP entity shall: + +- deliver the corresponding EHC feedback to the EHC protocol without performing deciphering/integrity verification. + +### 5.12.7 Simultaneous configuration of ROHC and EHC + +If both ROHC and EHC are configured for a DRB/MRB, the ROHC header shall be located after the EHC header. Figure 5.12.7-1 shows the location of the ROHC header and the EHC header in a PDCP Data PDU. + +![Diagram showing the vertical stack of headers in a PDCP Data PDU: PDCP header at the top, followed by SDAP header, EHC header, ROHC header, and Payload at the bottom.](dfa6249d64e9f63db89f2c5b7bbd01de_img.jpg) + +| | +|-------------| +| PDCP header | +| SDAP header | +| EHC header | +| ROHC header | +| Payload | + +Diagram showing the vertical stack of headers in a PDCP Data PDU: PDCP header at the top, followed by SDAP header, EHC header, ROHC header, and Payload at the bottom. + +**Figure 5.12.7-1: Location of ROHC header and EHC header in a PDCP Data PDU** + +If a PDCP SDU including non-IP Ethernet packet is received from upper layers, the EHC compressor shall bypass the ROHC compressor and submit the EHC compressed non-IP Ethernet packet to lower layers according to clause 5.2.1. + +If a PDCP Data PDU including non-IP Ethernet packet is received from lower layers, the EHC decompressor shall bypass the ROHC decompressor and deliver the EHC decompressed non-IP Ethernet packet to upper layers according to clause 5.2.2. + +## 5.13 Uplink data switching + +For DAPS bearers, when upper layers request uplink data switching, the transmitting PDCP entity shall: + +- for AM DRBs, from the first PDCP SDU for which the successful delivery of the corresponding PDCP Data PDU has not been confirmed by the RLC entity associated with the source cell, perform retransmission or transmission of all the PDCP SDUs already associated with PDCP SNs in ascending order of the COUNT values associated to the PDCP SDU prior to uplink data switching to the RLC entity associated with the target cell as specified below: + - perform header compression of the PDCP SDU using ROHC as specified in the clause 5.7.4; + +- perform integrity protection and ciphering of the PDCP SDU using the COUNT value associated with this PDCP SDU as specified in the clause 5.9 and 5.8, respectively; +- submit the resulting PDCP Data PDU to lower layer, as specified in clause 5.2.1. +- for UM DRBs, for all PDCP SDUs which have been processed by PDCP but which have not yet been submitted to lower layers, perform transmission of the PDCP SDUs in ascending order of the COUNT values to the RLC entity associated with the target cell as specified below: + - perform header compression of the PDCP SDU using ROHC as specified in the clause 5.7.4; + - perform integrity protection and ciphering of the PDCP SDU using the COUNT value associated with this PDCP SDU as specified in the clause 5.9 and 5.8, respectively; + - submit the resulting PDCP Data PDU to lower layer, as specified in clause 5.2.1. + +## 5.14 Uplink Data compression and decompression + +### 5.14.1 UDC protocol + +The UDC protocol is based on IETF RFC 1951 (DEFLATE Compressed Data Format Specification) [19]. + +Static Huffman coding tree defined in [19] is used as the DEFLATE compression strategy. + +UDC Data Block should be byte-alignment. Z\_SYNC\_FLUSH is used as the DEFLATE byte-alignment with corresponding reference [21], wherein the fixed last four bytes, 0x00 0x00 0xFF 0xFF, are removed before transmission. + +### 5.14.2 Configuration of UDC + +The PDCP entities associated with DRBs can be configured by upper layers, see TS 38.331 [3], to use UDC. If UDC is configured, the UE shall apply UDC compression function (details see Annex B) to process the received PDCP SDU from upper layers corresponding to the configured DRB. The size of compression buffer is configured by upper layers via *bufferSize*. If pre-defined dictionary is configured by upper layers, the UE shall first set the compression buffer to all zeros and then prefill the configured pre-defined dictionary in the compression buffer upon configuration of UDC. If pre-defined dictionary is not configured by upper layers, UE shall set the compression buffer to all zeros. + +### 5.14.3 UDC header + +UDC header (1 byte) is added in UDC compression function followed by UDC data block. The UDC header contains the information about whether the current PDCP SDU is compressed by UDC protocol or not. Only the compressed packets are stored in the buffer. The UDC header also contains a reset bit to inform the decompressor that the compression buffer has been reset. The validation bits (checksum) of the compression buffer are also contained in UDC header. Checksum mechanism could be used to resolve miss-match (if any) between the compression and decompression buffers. If both SDAP and UDC are configured for a DRB, the UDC header shall be located after the SDAP header. Figure 5.14.3-1 shows the location of the UDC header in a PDCP data PDU. + +![Diagram showing the location of UDC header in a PDCP Data PDU. The PDU is shown as a stack of four layers: PDCP Header (top, orange), SDAP Header(if configured) (second, light orange), UDC Header (third, light blue), and UDC Data Block (bottom, light green).](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +| | +|----------------------------| +| PDCP Header | +| SDAP Header(if configured) | +| UDC Header | +| UDC Data Block | + +Diagram showing the location of UDC header in a PDCP Data PDU. The PDU is shown as a stack of four layers: PDCP Header (top, orange), SDAP Header(if configured) (second, light orange), UDC Header (third, light blue), and UDC Data Block (bottom, light green). + +Figure 5.14.3-1: Location of UDC header in a PDCP Data PDU + +### 5.14.4 Uplink data compression + +The UDC protocol generates UDC packets, each associated with one PDCP SDU. + +A UDC packet is associated with the same PDCP SN and COUNT values as the related PDCP SDU. The uplink data compression is not applicable to the SDAP header and the SDAP Control PDU if included in the PDCP Data PDU. + +### 5.14.5 PDCP Control PDU for UDC feedback + +At reception of a PDCP Control PDU for UDC feedback from lower layers, the receiving PDCP entity shall: + +- deliver the corresponding UDC feedback to the UDC protocol without performing deciphering/integrity verification. + +### 5.14.6 Pre-defined dictionary + +One standard dictionary for SIP and SDP and one operator defined dictionary can be used as pre-defined dictionaries in UDC. The standard dictionary for SIP and SDP consists of the first 3468 bytes of the dictionary for SigComp defined in RFC 3485 [20]. When UDC is configured, at most one dictionary, configured by upper layers, is put into the tail of the compression buffer. Also, the compression buffer acts as a FIFO and hence the content of the dictionary is to be totally pushed out of the compression buffer after the size of transmitted uncompressed packets compressed by UDC exceeds the compression buffer size. If the size of dictionary is larger than the compression buffer size, only the tail of the dictionary is inserted in the compression buffer. + +### 5.14.7 UDC buffer reset procedure + +UDC works on the condition that compression buffer and de-compression buffer are synchronized. UDC buffer reset mechanism is to resynchronize buffer when error is detected. For resynchronization, UE shall reset the compression buffer to all zeros. + +### 5.14.8 UDC checksum error handling + +UDC checksum error notification PDCP control PDU indicates the compression buffer and de-compression buffer are out of synchronization. When receiving the notification, the UE shall trigger UDC buffer reset procedure to resynchronize the compression buffer. + +## 5.15 Data volume calculation for delay status reporting + +For the purpose of MAC delay status reporting, the transmitting PDCP entity shall consider the following as delay-critical PDCP data volume: + +- the delay-critical PDCP SDUs for which no PDCP Data PDUs have been constructed; + +- the PDCP Data PDUs that contain the delay-critical PDCP SDUs and have not been submitted to lower layers; +- the PDCP Control PDUs; +- for AM DRBs, the PDCP SDUs to be retransmitted according to clause 5.1.2 and clause 5.13; +- for AM DRBs, the PDCP Data PDUs to be retransmitted according to clause 5.5. + +If a PDCP SDU becomes a delay-critical PDCP SDU, and if the corresponding PDCP Data PDU has already been submitted to lower layers, the delay-critical indication for the PDCP Data PDU is provided to lower layers. + +# --- 6 Protocol data units, formats, and parameters + +## 6.1 Protocol data units + +### 6.1.1 Data PDU + +The PDCP Data PDU is used to convey one or more of followings in addition to the PDU header: + +- user plane data; +- control plane data; +- a MAC-I. + +### 6.1.2 Control PDU + +The PDCP Control PDU is used to convey one of followings in addition to the PDU header: + +- a PDCP status report; +- an interspersed ROHC feedback; +- an EHC feedback; +- a UDC feedback. + +## 6.2 Formats + +### 6.2.1 General + +A PDCP PDU is a bit string that is byte aligned (i.e. multiple of 8 bits) in length. In the figures in clause 6.2, bit strings are represented by tables in which the most significant bit is the leftmost bit of the first line of the table, the least significant bit is the rightmost bit on the last line of the table, and more generally the bit string is to be read from left to right and then in the reading order of the lines. The bit order of each parameter field within a PDCP PDU is represented with the first and most significant bit in the leftmost bit and the last and least significant bit in the rightmost bit. + +PDCP SDUs are bit strings that are byte aligned (i.e. multiple of 8 bits) in length. A compressed or uncompressed SDU is included into a PDCP Data PDU from the first bit onward. + +### 6.2.2 Data PDU + +#### 6.2.2.1 Data PDU for SRBs + +Figure 6.2.2.1-1 shows the format of the PDCP Data PDU with 12 bits PDCP SN. This format is applicable for SRBs. + +![Figure 6.2.2.1-1: PDCP Data PDU format for SRBs. The diagram shows a sequence of octets. Octet 1 contains four 'R' (Retransmission) bits and the first part of the PDCP SN. Octet 2 contains the continuation of the PDCP SN. Octet 3 contains the Data. An ellipsis indicates intermediate octets. Octet N-3 contains the first part of the MAC-I. Octet N-2 contains the continuation of the MAC-I. Octet N-1 contains the continuation of the MAC-I. Octet N contains the continuation of the MAC-I.](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +| | | | | | | +|-----------------|---|---|---|---------|---------| +| R | R | R | R | PDCP SN | Oct 1 | +| PDCP SN (cont.) | | | | | Oct 2 | +| Data | | | | | Oct 3 | +| ... | | | | | | +| MAC-I | | | | | Oct N-3 | +| MAC-I (cont.) | | | | | Oct N-2 | +| MAC-I (cont.) | | | | | Oct N-1 | +| MAC-I (cont.) | | | | | Oct N | + +Figure 6.2.2.1-1: PDCP Data PDU format for SRBs. The diagram shows a sequence of octets. Octet 1 contains four 'R' (Retransmission) bits and the first part of the PDCP SN. Octet 2 contains the continuation of the PDCP SN. Octet 3 contains the Data. An ellipsis indicates intermediate octets. Octet N-3 contains the first part of the MAC-I. Octet N-2 contains the continuation of the MAC-I. Octet N-1 contains the continuation of the MAC-I. Octet N contains the continuation of the MAC-I. + +Figure 6.2.2.1-1: PDCP Data PDU format for SRBs + +#### 6.2.2.2 Data PDU for DRBs and MRBs with 12 bits PDCP SN + +Figure 6.2.2.2-1 shows the format of the PDCP Data PDU with 12 bits PDCP SN. This format is applicable for UM DRBs, AM DRBs, UM MRBs and AM MRBs. + +![Figure 6.2.2.2-1: PDCP Data PDU format with 12 bits PDCP SN. The diagram shows a sequence of octets. Octet 1 contains D/C (Data/Control), R (Retransmission), R (Retransmission), R (Retransmission), and the first part of the PDCP SN. Octet 2 contains the continuation of the PDCP SN. Octet 3 contains the Data. An ellipsis indicates intermediate octets. Octet N-3 contains the first part of the optional MAC-I. Octet N-2 contains the continuation of the optional MAC-I. Octet N-1 contains the continuation of the optional MAC-I. Octet N contains the continuation of the optional MAC-I.](875c6f4f441fdd3ca7e1908fd1582983_img.jpg) + +| | | | | | | +|--------------------------|---|---|---|---------|---------| +| D/C | R | R | R | PDCP SN | Oct 1 | +| PDCP SN (cont.) | | | | | Oct 2 | +| Data | | | | | Oct 3 | +| ... | | | | | | +| MAC-I (optional) | | | | | Oct N-3 | +| MAC-I (cont.) (optional) | | | | | Oct N-2 | +| MAC-I (cont.) (optional) | | | | | Oct N-1 | +| MAC-I (cont.) (optional) | | | | | Oct N | + +Figure 6.2.2.2-1: PDCP Data PDU format with 12 bits PDCP SN. The diagram shows a sequence of octets. Octet 1 contains D/C (Data/Control), R (Retransmission), R (Retransmission), R (Retransmission), and the first part of the PDCP SN. Octet 2 contains the continuation of the PDCP SN. Octet 3 contains the Data. An ellipsis indicates intermediate octets. Octet N-3 contains the first part of the optional MAC-I. Octet N-2 contains the continuation of the optional MAC-I. Octet N-1 contains the continuation of the optional MAC-I. Octet N contains the continuation of the optional MAC-I. + +Figure 6.2.2.2-1: PDCP Data PDU format with 12 bits PDCP SN + +#### 6.2.2.3 Data PDU for DRBs and MRBs with 18 bits PDCP SN + +Figure 6.2.2.3-1 shows the format of the PDCP Data PDU with 18 bits PDCP SN. This format is applicable for UM DRBs, AM DRBs, UM MRBs and AM MRBs. + +![Diagram of PDCP Data PDU format for DRBs with 18 bits PDCP SN. The diagram shows a sequence of PDUs over time (Oct 1 to Oct N). Oct 1 has fields D/C, R, R, R, R, R, and PDCP SN. Oct 2 and Oct 3 have PDCP SN (cont.). Oct 4 has Data. An ellipsis indicates intermediate PDUs. Oct N-3 to Oct N have optional MAC-I (cont.) fields.](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +| | | | | | | | | +|--------------------------|---|---|---|---|---|---------|---------| +| D/C | R | R | R | R | R | PDCP SN | Oct 1 | +| PDCP SN (cont.) | | | | | | | Oct 2 | +| PDCP SN (cont.) | | | | | | | Oct 3 | +| Data | | | | | | | Oct 4 | +| ... | | | | | | | | +| MAC-I (optional) | | | | | | | Oct N-3 | +| MAC-I (cont.) (optional) | | | | | | | Oct N-2 | +| MAC-I (cont.) (optional) | | | | | | | Oct N-1 | +| MAC-I (cont.) (optional) | | | | | | | Oct N | + +Diagram of PDCP Data PDU format for DRBs with 18 bits PDCP SN. The diagram shows a sequence of PDUs over time (Oct 1 to Oct N). Oct 1 has fields D/C, R, R, R, R, R, and PDCP SN. Oct 2 and Oct 3 have PDCP SN (cont.). Oct 4 has Data. An ellipsis indicates intermediate PDUs. Oct N-3 to Oct N have optional MAC-I (cont.) fields. + +Figure 6.2.2.3-1: PDCP Data PDU format for DRBs with 18 bits PDCP SN + +#### 6.2.2.4 Data PDU for sidelink DRBs for groupcast and broadcast, for the sidelink SRB0 and for the sidelink SRB4 + +Figure 6.2.2.4-1 shows the format of the PDCP Data PDU with 12 bits PDCP SN. This format is applicable for sidelink DRBs for groupcast and broadcast, for the sidelink SRB0 and for the sidelink SRB4. + +![Diagram of PDCP Data PDU format for sidelink DRBs for groupcast and broadcast. The diagram shows PDUs over time (Oct 1 to Oct 3+n). Oct 1 has SDU Type, R, and PDCP SN. Oct 2 has PDCP SN (cont.). Oct 3 and Oct 3+n have Data fields.](315bdbeafb39026e19b77c26b19d9d1f_img.jpg) + +| | | | | +|-----------------|---|---------|---------| +| SDU Type | R | PDCP SN | Oct 1 | +| PDCP SN (cont.) | | | Oct 2 | +| Data | | | Oct 3 | +| ... | | | | +| Data | | | Oct 3+n | + +Diagram of PDCP Data PDU format for sidelink DRBs for groupcast and broadcast. The diagram shows PDUs over time (Oct 1 to Oct 3+n). Oct 1 has SDU Type, R, and PDCP SN. Oct 2 has PDCP SN (cont.). Oct 3 and Oct 3+n have Data fields. + +Figure 6.2.2.4-1: PDCP Data PDU format for sidelink DRBs for groupcast and broadcast, for the sidelink SRB0 and for the sidelink SRB4 + +NOTE: There is no control PDU for SLRBs for groupcast and broadcast. Thus, there is no D/C field in the PDCP Data PDU format for SLRBs for groupcast and broadcast. SDU type is only applicable for sidelink DRB. + +#### 6.2.2.5 Data PDU for sidelink SRBs for unicast + +Figure 6.2.2.5-1 shows the format of the PDCP Data PDU with 12 bits PDCP SN. This format is applicable for sidelink SRB1, SRB2 and SRB3 for unicast. + +![Diagram of PDCP Data PDU format for sidelink SRB1, SRB2 and SRB3 for unicast. The diagram shows a sequence of octets (Oct 1 to Oct N) with fields: R (4 bits), PDCP SN (8 bits), PDCP SN (cont.) (8 bits), K_NRP-sess ID (16 bits), K_NRP-sess ID (cont.) (16 bits), Data, and MAC-I (optional) (8 bits).](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +| | | | | | | | | | +|----------------------------------|--|--|--|---------|-------|--|--|---------| +| R | | | | PDCP SN | Oct 1 | | | | +| PDCP SN (cont.) | | | | | | | | Oct 2 | +| $K_{\text{NRP-sess}}$ ID | | | | | | | | Oct 3 | +| $K_{\text{NRP-sess}}$ ID (cont.) | | | | | | | | Oct 4 | +| Data | | | | | | | | Oct 5 | +| ... | | | | | | | | | +| MAC-I (optional) | | | | | | | | Oct N-3 | +| MAC-I (cont.) (optional) | | | | | | | | Oct N-2 | +| MAC-I (cont.) (optional) | | | | | | | | Oct N-1 | +| MAC-I (cont.) (optional) | | | | | | | | Oct N | + +Diagram of PDCP Data PDU format for sidelink SRB1, SRB2 and SRB3 for unicast. The diagram shows a sequence of octets (Oct 1 to Oct N) with fields: R (4 bits), PDCP SN (8 bits), PDCP SN (cont.) (8 bits), K\_NRP-sess ID (16 bits), K\_NRP-sess ID (cont.) (16 bits), Data, and MAC-I (optional) (8 bits). + +Figure 6.2.2.5-1: PDCP Data PDU format for sidelink SRB1, SRB2 and SRB3 for unicast + +#### 6.2.2.6 Data PDU for sidelink DRBs for unicast with 12 bits PDCP SN + +Figure 6.2.2.6-1 shows the format of the PDCP Data PDU with 12 bits PDCP SN. This format is applicable for sidelink DRBs for unicast. + +![Diagram of PDCP Data PDU format for sidelink DRBs for unicast with 12 bits PDCP SN. The diagram shows a sequence of octets (Oct 1 to Oct N) with fields: D/C (1 bit), SDU Type (3 bits), PDCP SN (12 bits), PDCP SN (cont.) (12 bits), K_NRP-sess ID (16 bits), K_NRP-sess ID (cont.) (16 bits), Data, and MAC-I (optional) (8 bits).](6be06b7dc72bb42afcb3465394667c3b_img.jpg) + +| | | | | | | | | | +|----------------------------------|----------|--|--|---------|--|--|--|---------| +| D/C | SDU Type | | | PDCP SN | | | | Oct 1 | +| PDCP SN (cont.) | | | | | | | | Oct 2 | +| $K_{\text{NRP-sess}}$ ID | | | | | | | | Oct 3 | +| $K_{\text{NRP-sess}}$ ID (cont.) | | | | | | | | Oct 4 | +| Data | | | | | | | | Oct 5 | +| ... | | | | | | | | | +| MAC-I (optional) | | | | | | | | Oct N-3 | +| MAC-I (cont.) (optional) | | | | | | | | Oct N-2 | +| MAC-I (cont.) (optional) | | | | | | | | Oct N-1 | +| MAC-I (cont.) (optional) | | | | | | | | Oct N | + +Diagram of PDCP Data PDU format for sidelink DRBs for unicast with 12 bits PDCP SN. The diagram shows a sequence of octets (Oct 1 to Oct N) with fields: D/C (1 bit), SDU Type (3 bits), PDCP SN (12 bits), PDCP SN (cont.) (12 bits), K\_NRP-sess ID (16 bits), K\_NRP-sess ID (cont.) (16 bits), Data, and MAC-I (optional) (8 bits). + +Figure 6.2.2.6-1: PDCP Data PDU format for sidelink DRBs for unicast with 12 bits PDCP SN + +#### 6.2.2.7 Data PDU for sidelink DRBs for unicast with 18 bits PDCP SN + +Figure 6.2.2.7-1 shows the format of the PDCP Data PDU with 18 bits PDCP SN. This format is applicable for sidelink DRBs for unicast. + +![Diagram of PDCP Data PDU format for sidelink DRBs for unicast with 18 bits PDCP SN. The diagram shows a sequence of octets (Oct 1 to Oct N) with various fields. Oct 1 contains D/C, SDU Type, R, R, and PDCP SN. Oct 2 and Oct 3 contain PDCP SN (cont.). Oct 4 and Oct 5 contain K_NRP-sess ID and K_NRP-sess ID (cont.). Oct 6 contains Data. There is an ellipsis between Oct 6 and Oct N-3. Oct N-3, Oct N-2, Oct N-1, and Oct N contain MAC-I (optional) and its continuations.](382a9c9e4816bd229191ab4591424dd8_img.jpg) + +| | | | | | | | | | +|----------------------------------|----------|---|---|---------|--|--|-------|---------| +| | | | | | | | | | +| D/C | SDU Type | R | R | PDCP SN | | | Oct 1 | | +| PDCP SN (cont.) | | | | | | | | Oct 2 | +| PDCP SN (cont.) | | | | | | | | Oct 3 | +| $K_{\text{NRP-sess}}$ ID | | | | | | | | Oct 4 | +| $K_{\text{NRP-sess}}$ ID (cont.) | | | | | | | | Oct 5 | +| Data | | | | | | | | Oct 6 | +| ... | | | | | | | | | +| MAC-I (optional) | | | | | | | | Oct N-3 | +| MAC-I (cont.) (optional) | | | | | | | | Oct N-2 | +| MAC-I (cont.) (optional) | | | | | | | | Oct N-1 | +| MAC-I (cont.) (optional) | | | | | | | | Oct N | + +Diagram of PDCP Data PDU format for sidelink DRBs for unicast with 18 bits PDCP SN. The diagram shows a sequence of octets (Oct 1 to Oct N) with various fields. Oct 1 contains D/C, SDU Type, R, R, and PDCP SN. Oct 2 and Oct 3 contain PDCP SN (cont.). Oct 4 and Oct 5 contain K\_NRP-sess ID and K\_NRP-sess ID (cont.). Oct 6 contains Data. There is an ellipsis between Oct 6 and Oct N-3. Oct N-3, Oct N-2, Oct N-1, and Oct N contain MAC-I (optional) and its continuations. + +Figure 6.2.2.7-1: PDCP Data PDU format for sidelink DRBs for unicast with 18 bits PDCP SN + +### 6.2.3 Control PDU + +#### 6.2.3.1 Control PDU for PDCP status report + +Figure 6.2.3.1-1 shows the format of the PDCP Control PDU carrying one PDCP status report. This format is applicable for UM DRBs, AM DRBs (including sidelink DRBs for unicast) and AM MRBs. + +![Diagram of PDCP Control PDU format for PDCP status report. It shows a header with D/C, PDU Type, and four R bits, followed by FMC and optional Bitmap fields.](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +| | | | | | | | +|--------------------------------|----------|---|---|---|---|---------| +| D/C | PDU Type | R | R | R | R | Oct 1 | +| FMC | | | | | | Oct 2 | +| FMC (cont.) | | | | | | Oct 3 | +| FMC (cont.) | | | | | | Oct 4 | +| FMC (cont.) | | | | | | Oct 5 | +| Bitmap 1 (optional) | | | | | | Oct 6 | +| ... | | | | | | | +| Bitmap N (optional) | | | | | | Oct 5+N | + +Diagram of PDCP Control PDU format for PDCP status report. It shows a header with D/C, PDU Type, and four R bits, followed by FMC and optional Bitmap fields. + +Figure 6.2.3.1-1: PDCP Control PDU format for PDCP status report + +#### 6.2.3.2 Control PDU for interspersed ROHC feedback + +Figure 6.2.3.2-1 shows the format of the PDCP Control PDU carrying one interspersed ROHC feedback. This format is applicable for UM DRBs, AM DRBs (including sidelink DRBs for unicast), UM MRBs and AM MRBs. + +![Diagram of PDCP Control PDU format for interspersed ROHC feedback. It shows a header with D/C, PDU Type, and four R bits, followed by Interspersed ROHC feedback.](9f862801bce82634d3b5a1e0a195a799_img.jpg) + +| | | | | | | | +|----------------------------|----------|---|---|---|---|-------| +| D/C | PDU Type | R | R | R | R | Oct 1 | +| Interspersed ROHC feedback | | | | | | Oct 2 | +| ... | | | | | | | + +Diagram of PDCP Control PDU format for interspersed ROHC feedback. It shows a header with D/C, PDU Type, and four R bits, followed by Interspersed ROHC feedback. + +Figure 6.2.3.2-1: PDCP Control PDU format for interspersed ROHC feedback + +#### 6.2.3.3 Control PDU for EHC feedback + +Figure 6.2.3.3-1 shows the format of the PDCP Control PDU carrying one EHC feedback. This format is applicable for UM DRBs, AM DRBs, UM MRBs and AM MRBs. + +![Diagram of PDCP Control PDU format for EHC feedback. It shows a header with D/C, PDU Type, and four R bits, followed by EHC feedback.](f10dc32e3673e1392029a49e958a9d6c_img.jpg) + +| | | | | | | | +|--------------|----------|---|---|---|---|-------| +| D/C | PDU Type | R | R | R | R | Oct 1 | +| EHC feedback | | | | | | Oct 2 | +| ... | | | | | | | + +Diagram of PDCP Control PDU format for EHC feedback. It shows a header with D/C, PDU Type, and four R bits, followed by EHC feedback. + +Figure 6.2.3.3-1: PDCP Control PDU format for EHC feedback + +#### 6.2.3.4 Control PDU for UDC feedback + +Figure 6.2.3.4-1 shows the format of the PDCP Control PDU carrying one UDC feedback. This format is applicable for AM DRBs. + +![Diagram of PDCP Control PDU format for UDC feedback. The diagram shows a horizontal sequence of six fields: D/C, PDU Type, FE, R, R, and R. The fields are represented by orange rectangular boxes connected by vertical lines.](0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg) + +| | | | | | | +|-----|----------|----|---|---|---| +| D/C | PDU Type | FE | R | R | R | +|-----|----------|----|---|---|---| + +Diagram of PDCP Control PDU format for UDC feedback. The diagram shows a horizontal sequence of six fields: D/C, PDU Type, FE, R, R, and R. The fields are represented by orange rectangular boxes connected by vertical lines. + +Figure 6.2.3.4-1: PDCP Control PDU format for UDC feedback + +## 6.3 Parameters + +### 6.3.1 General + +If not otherwise mentioned in the definition of each field then the bits in the parameters shall be interpreted as follows: the left most bit string is the first and most significant and the right most bit is the last and least significant bit. + +Unless otherwise mentioned, integers are encoded in standard binary encoding for unsigned integers. In all cases the bits appear ordered from MSB to LSB when read in the PDU. + +### 6.3.2 PDCP SN + +Length: 12 or 18 bits as indicated in table 6.3.2-1. The length of the PDCP SN is configured by upper layers (*pdcp-SN-SizeUL*, *pdcp-SN-SizeDL*, or *sl-PDCP-SN-Size* in TS 38.331 [3]). + +Table 6.3.2-1: PDCP SN length + +| Length | Description | +|--------|-----------------------------------------------------------------------------------------| +| 12 | SRBs, UM DRBs, AM DRBs (including sidelink SRBs and sidelink DRBs), UM MRBs and AM MRBs | +| 18 | UM DRBs, AM DRBs (including sidelink DRBs for unicast), UM MRBs and AM MRBs | + +NOTE: For NR sidelink communication for groupcast and broadcast, only 12 bits PDCP SN length is used for the sidelink DRBs. + +### 6.3.3 Data + +Length: Variable + +This field includes one of the followings: + +- Uncompressed PDCP SDU (user plane data, or control plane data); +- Compressed PDCP SDU (user plane data only). + +NOTE: All fields other than PDCP PDU header and MAC-I belong to Data field. + +### 6.3.4 MAC-I + +Length: 32 bits + +This field carries a message authentication code calculated as specified in clause 5.9. + +For SRBs for Uu interface, the MAC-I field is always present. If integrity protection is not configured, the MAC-I field is still present but should be padded with padding bits set to 0. + +For sidelink SRB1, SRB2 and SRB3, the MAC-I field is present only when the sidelink SRB1, SRB2 and SRB3 are configured with integrity protection. + +For DRBs (including sidelink DRBs for unicast), the MAC-I field is present only when the DRB is configured with integrity protection. + +### 6.3.5 COUNT + +Length: 32 bits + +The COUNT value is composed of a HFN and the PDCP SN. The size of the HFN part in bits is equal to 32 minus the length of the PDCP SN. + +![](4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg) + +| | | +|-----|---------| +| HFN | PDCP SN | +|-----|---------| + +**Figure 6.3.5-1: Format of COUNT** + +NOTE: COUNT does not wrap around. + +### 6.3.6 R + +Length: 1 bit + +Reserved. In this version of the specification reserved bits shall be set to 0. Reserved bits shall be ignored by the receiver. + +### 6.3.7 D/C + +Length: 1 bit + +This field indicates whether the corresponding PDCP PDU is a PDCP Data PDU or a PDCP Control PDU. + +**Table 6.3.7-1: D/C field** + +| Bit | Description | +|-----|-------------| +| 0 | Control PDU | +| 1 | Data PDU | + +### 6.3.8 PDU type + +Length: 3 bits + +This field indicates the type of control information included in the corresponding PDCP Control PDU. + +**Table 6.3.8-1: PDU type** + +| Bit | Description | +|---------|----------------------------| +| 000 | PDCP status report | +| 001 | Interspersed ROHC feedback | +| 010 | EHC feedback | +| 011 | UDC feedback | +| 100-111 | Reserved | + +### 6.3.9 FMC + +Length: 32 bits + +First Missing COUNT. This field indicates the COUNT value of the first missing PDCP SDU within the reordering window, i.e. RX\_DELIV. + +### 6.3.10 Bitmap + +Length: Variable. The length of the bitmap field can be 0. + +This field indicates which SDUs are missing and which SDUs are correctly received in the receiving PDCP entity. The bit position of Nth bit in the Bitmap is N, i.e., the bit position of the first bit in the Bitmap is 1. + +**Table 6.3.10-1 Bitmap** + +| Bit | Description | +|-----|------------------------------------------------------------------------------------------| +| 0 | PDCP SDU with COUNT = (FMC + bit position) modulo 2 32 is missing. | +| 1 | PDCP SDU with COUNT = (FMC + bit position) modulo 2 32 is correctly received. | + +### 6.3.11 Interspersed ROHC feedback + +Length: Variable + +This field contains one ROHC packet with only feedback, i.e. a ROHC packet that is not associated with a PDCP SDU as defined in clause 5.7.4. + +### 6.3.12 SDU Type + +Length: 3 bits + +PDCP SDU type, i.e. Layer-3 Protocol Data Unit type as specified in [13] and [18]. PDCP entity may handle the SDU differently per SDU Type, e.g. ROHC is applicable to IP SDU but not Non-IP SDU, Ethernet SDU, Unstructured SDU and ARP SDU. + +**Table 6.3.12-1: SDU Type** + +| Bit | Description | +|---------|--------------| +| 000 | IP | +| 001 | Non-IP | +| 010 | Ethernet | +| 011 | Unstructured | +| 100 | ARP | +| 101-111 | Reserved | + +### 6.3.13 KNRP-sess ID + +Length: 16 bits + +KNRP-sess Identity as specified in TS 33.536 [14]. + +For the SLRB that does not need integrity and ciphering protection, the UE shall set KNRP-sess ID to "0" in the PDCP PDU header. + +### 6.3.14 FE + +Length: 1 bit + +Indication of whether checksum error is detected or not. Value '1' means checksum error is detected and the UE shall reset the compression buffer. + +Table 6.3.14-1: FE field + +| Bit | Description | +|-----|-----------------------------| +| 0 | No Error | +| 1 | Checksum Error Notification | + +# 7 State variables, constants, and timers + +## 7.1 State variables + +This clause describes the state variables used in PDCP entities in order to specify the PDCP protocol. The state variables defined in this clause are normative. + +All state variables are non-negative integers, and take values from 0 to $[2^{32} - 1]$ . + +PDCP Data PDUs are numbered integer sequence numbers (SN) cycling through the field: 0 to $[2^{[pdcp-SN-SizeUL]} - 1]$ or 0 to $[2^{[pdcp-SN-SizeDL]} - 1]$ or 0 to $[2^{[sl-PDCP-SN-Size]} - 1]$ . + +The transmitting PDCP entity shall maintain the following state variables: + +### a) TX\_NEXT + +This state variable indicates the COUNT value of the next PDCP SDU to be transmitted. The initial value is 0, except for SRBs configured with state variables continuation. For target SRB configured with state variables continuation, the initial value is the value stored in PDCP entity for the corresponding source SRB. For source SRB configured with state variables continuation, the initial value is the value stored in PDCP entity for the corresponding target SRB. + +The receiving PDCP entity shall maintain the following state variables: + +### a) RX\_NEXT + +This state variable indicates the COUNT value of the next PDCP SDU expected to be received. The initial value is 0, except for sidelink broadcast and groupcast, for SRBs configured with state variables continuation, for multicast MRBs whose PDCP COUNT is not synchronized as indicated by upper layer, and for broadcast MRBs. For NR sidelink communication for broadcast and groupcast or sidelink SRB4 for NR sidelink discovery, the initial value of the SN part of RX\_NEXT is $(x + 1)$ modulo $(2^{[sl-PDCP-SN-Size]})$ , where $x$ is the SN of the first received PDCP Data PDU. For multicast MRBs whose PDCP COUNT is not synchronized as indicated by upper layer, and for broadcast MRBs, the initial value of the SN part of RX\_NEXT is $(x + 1)$ modulo $(2^{[PDCP-SN-SizeDL]})$ , where $x$ is the SN of the first received PDCP Data PDU. For target SRB configured with state variables continuation, the initial value is the value stored in PDCP entity for the corresponding source SRB. For source SRB configured with state variables continuation, the initial value is the value stored in PDCP entity for the corresponding target SRB. + +NOTE 1: For NR sidelink communication for broadcast and groupcast or sidelink SRB4 for NR sidelink discovery, it is up to UE implementation to select the HFN part for RX\_NEXT such that initial value of RX\_DELIV should be a positive value. + +NOTE 2: For multicast MRBs whose PDCP COUNT is not synchronized as indicated by upper layer, and for broadcast MRBs, the initial value of the HFN part of RX\_NEXT is set by UE implementation. + +### b) RX\_DELIV + +This state variable indicates the COUNT value of the first PDCP SDU not delivered to the upper layers, but still waited for. The initial value is 0, except for sidelink broadcast and groupcast, for SRBs configured with state variables continuation, and for MRBs. For NR sidelink communication for broadcast and groupcast or sidelink SRB4 for NR sidelink discovery, the initial value of the SN part of RX\_DELIV is $(x - 0.5 \times 2^{[sl-PDCP-SN-Size-1]})$ modulo $(2^{[sl-PDCP-SN-Size]})$ , where $x$ is the SN of the first received PDCP Data PDU. For multicast MRBs whose PDCP COUNT is not synchronized as indicated by upper layer, and for broadcast MRBs, the initial value of the SN part of RX\_DELIV is set to $(x - 0.5 \times 2^{[PDCP-SN-SizeDL-1]})$ modulo $(2^{[PDCP-SN-SizeDL]})$ , where $x$ is the SN of the first received PDCP Data PDU. For multicast MRBs, the initial value of RX\_DELIV is set, if provided, by *initialRX-DELIV* in TS 38.331 [3]. For target SRB configured with state variables continuation, the initial value is the value stored in PDCP entity for the + +corresponding source SRB. For source SRB configured with state variables continuation, the initial value is the value stored in PDCP entity for the corresponding target SRB. + +NOTE 3: For multicast MRBs whose PDCP COUNT is not synchronized as indicated by upper layer, and for broadcast MRBs, the initial value of the HFN part of RX\_DELIV is set by UE implementation. + +### c) RX\_REORD + +This state variable indicates the COUNT value following the COUNT value associated with the PDCP Data PDU which triggered *t-Reordering*. For target SRB configured with state variables continuation, the initial value is the value stored in PDCP entity for the corresponding source SRB. For source SRB configured with state variables continuation, the initial value is the value stored in PDCP entity for the corresponding target SRB. + +## 7.2 Constants + +### a) Window\_Size + +This constant indicates the size of the reordering window. The value equals to $2^{[pdcp-SN-SizeDL]} - 1$ for SRB/DRB/MRB and $2^{[sl-PDCP-SN-Size]} - 1$ for SLRB. + +## 7.3 Timers + +The transmitting PDCP entity shall maintain the following timers: + +### a) *discardTimer* + +This timer is configured only for DRBs. The duration of the timer is configured by upper layers TS 38.331 [3]. In the transmitter, a new timer is started upon reception of an SDU from upper layer as specified in clause 5.2.1. + +### b) *discardTimerForLowImportance* + +This timer is configured only for DRBs. The duration of the timer is configured by upper layers TS 38.331 [3]. In the transmitter, a new timer is started upon reception of an SDU belonging to a low importance PDU Set from upper layer as specified in clause 5.2.1. + +The receiving PDCP entity shall maintain the following timers: + +### c) *t-Reordering* + +The duration of the timer is configured by upper layers TS 38.331 [3], except for the case of NR sidelink communication or sidelink SRB4. For NR sidelink communication or sidelink SRB4, the *t-Reordering* timer is determined by the UE implementation. This timer is used to detect loss of PDCP Data PDUs as specified in clause 5.2.2. If *t-Reordering* is running, *t-Reordering* shall not be started additionally, i.e. only one *t-Reordering* per receiving PDCP entity is running at a given time. + +# --- Annex A (normative): Ethernet Header Compression (EHC) protocol + +## A.1 EHC principle + +The Ethernet header compression (EHC) protocol compresses Ethernet header as shown in Figure A.1-1 [15]. The fields that are compressed (i.e. removed from the Ethernet header) by the EHC protocol are: DESTINATION ADDRESS, SOURCE ADDRESS, 802.1Q TAG, and LENGTH/TYPE. The fields PREAMBLE, SFD, and FCS are not transmitted in 3GPP system, and thus not considered in EHC protocol. There may be more than one 802.1Q TAG fields in the Ethernet header, and all are compressed by the EHC protocol. The padding (PAD) is not compressed by the EHC protocol. + +![](8e80de0cac529b2c3775d677c5203133_img.jpg) + +| | | | +|--------------------------------|----------------------------|-------------------| +| PREAMBLE | 7 octets : Not transmitted | | +| START OF FRAME DELIMITER (SFD) | 1 octet : Not transmitted | | +| DESTINATION ADDRESS | 6 octets | Compressed by EHC | +| SOURCE ADDRESS | 6 octets | | +| 802.1Q TAG (optional) | 4 octets | | +| LENGTH/TYPE | 2 octets | | +| PAYLOAD (+PAD) | 42-1500 octets | | +| FRAME CHECK SEQUENCE (FCS) | 4 octets : Not transmitted | | +| EXTENSION | | | + +**Figure A.1-1: Ethernet packet format [15]** + +The EHC compressor and the EHC decompressor store original header field information as a "EHC context". Each EHC context is identified by a unique identifier, called Context ID (CID). The EHC context must be synchronized between the EHC compressor and the EHC decompressor; otherwise, the EHC decompressor erroneously decompresses the "Compressed Header (CH)" packets. + +For an Ethernet packet stream, the EHC compressor establishes the EHC context and associates it with the CID. Then, the EHC compressor transmits the "Full Header (FH)" packet to the EHC decompressor including the associated CID. The EHC compressor keeps transmitting the FH packets until the EHC feedback is received from the EHC decompressor. + +NOTE: If the maximum number of EHC contexts are already established for the compressed flows and a new Ethernet flow does not match any established EHC context, the compressor should associate the new Ethernet flow with one of the EHC CIDs allocated for the existing compressed flows or send PDCP SDUs belonging to the Ethernet flow as uncompressed packet. + +When the EHC decompressor receives the FH packet, the EHC decompressor establishes the EHC context identified by the CID, and transmits the EHC feedback to the EHC compressor to indicate that the EHC context associated with the CID is successfully established in the EHC decompressor. + +After receiving the EHC feedback, the EHC compressor starts to transmit the CH packets to the EHC decompressor including the associated CID. The CH packet includes only the header fields not stored in the EHC context. + +When the EHC decompressor receives the CH packet, the EHC decompressor restores original header fields based on the stored EHC context identified by the associated CID. + +Figure A.1-2 represents a conceptual view of EHC operation. + +![Diagram of EHC operation showing Compressor and Decompressor blocks with context tables and packet structures.](4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg) + +The diagram illustrates the EHC operation. On the left, an 'Ethernet Header' and 'Payload' are input to a 'Compressor' block. Above the compressor is a context table with entries for CIDx, CIDy, and CIDz, each associated with an 'EHC Context'. The compressor outputs three types of packets: 'CIDx FH Payload', 'Feedback = CIDx', and 'CIDx CH Payload'. These are received by a 'Decompressor' block. Above the decompressor is another context table with the same entries. The decompressor outputs the reconstructed 'Ethernet Header' and 'Payload'. + +Diagram of EHC operation showing Compressor and Decompressor blocks with context tables and packet structures. + +Figure A.1-2: EHC operation + +## A.2 EHC packet format and parameters + +### A.2.1 EHC packet format + +#### A.2.1.1 EHC Full Header packet and EHC Compressed Header packet + +Figure A.2.1.1-1 and Figure A.2.1.1-2 show the formats of EHC FH packet and EHC CH packet, respectively. + +![Diagram of EHC Full Header packet format showing fields: F/C, CID, CID (15 bits), Ethernet header, and PAYLOAD (+PAD).](9dc9f41d7d76c1add4b190d348cb1533_img.jpg) + +The diagram shows the structure of an EHC Full Header packet. It consists of several fields: + + +- A top section with 'F/C' (1 bit) and 'CID' (15 bits). +- A second section for 'CID (present when 15 bits CID is configured)' (15 bits). +- An 'Ethernet header' section. +- A final 'PAYLOAD (+PAD)' section. + +Diagram of EHC Full Header packet format showing fields: F/C, CID, CID (15 bits), Ethernet header, and PAYLOAD (+PAD). + +Figure A.2.1.1-1: EHC Full Header packet format + +![Diagram of EHC Compressed Header packet format showing F/C, CID, and PAYLOAD (+PAD) fields.](be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg) + +The diagram illustrates the structure of an EHC Compressed Header packet. It consists of three main parts: a header section at the top, an optional CID section in the middle, and a payload section at the bottom. The header section is divided into two fields: F/C (Frame Control) on the left and CID (Context Identifier) on the right. The optional CID section is labeled 'CID (present when 15 bits CID is configured)'. The bottom section is labeled 'PAYLOAD (+PAD)'. + +Diagram of EHC Compressed Header packet format showing F/C, CID, and PAYLOAD (+PAD) fields. + +Figure A.2.1.1-2: EHC Compressed Header packet format + +#### A.2.1.2 EHC feedback packet + +Figure A.2.1.2-1 shows the format of the EHC feedback packet. + +![Diagram of EHC feedback packet format showing R, CID, and CID (present when 15 bits CID is configured) fields.](052543d8c9c0643b05b3ce45c6decca1_img.jpg) + +The diagram illustrates the structure of an EHC feedback packet. It consists of two main parts: a header section at the top and a CID section at the bottom. The header section is divided into two fields: R (Request) on the left and CID (Context Identifier) on the right. The bottom section is labeled 'CID (present when 15 bits CID is configured)'. + +Diagram of EHC feedback packet format showing R, CID, and CID (present when 15 bits CID is configured) fields. + +Figure A.2.1.2-1: EHC feedback packet format + +### A.2.2 Parameters + +#### A.2.2.1 F/C + +Length: 1 bit + +This field indicates whether the corresponding EHC packet is a FH packet or a CH packet. + +Table A.2.2.1-1: F/C field + +| Bit | Description | +|-----|-------------| +| 0 | FH packet | +| 1 | CH packet | + +#### A.2.2.2 CID + +Length: 7, or 15 bits. The length of the CID is configured by upper layers (*ehc-CID-Length* in TS 38.331 [3]). + +The CID = "all zeros" indicates that the corresponding Ethernet header is "uncompressed". The EHC decompressor does not establish the EHC context identified by the CID = "all zeros". + +# Annex B (normative): Uplink Data Compression Protocol + +## B.1 UDC general description + +A UDC packet consists of a UDC header and a UDC data block. A UDC data block contains either DEFLATE compressed blocks generated by UDC protocol or original PDCP SDU for SDU not compressed by UDC protocol; the type is specified in FU field (details see Annex B.2.2.1) in UDC header. The FR field (details see Annex B.2.2.2) and the Checksum field (details see Annex B.2.2.3) in UDC header are used only if FU field is set to 1. + +If reset procedure is triggered, after performing the reset, the FR field in UDC header of the first compressed PDU shall be set to 1. + +NOTE: UE is allowed not to compress the PDCP SDUs if the UL data rate before compression is higher than what the UE is capable of. + +## B.2 UDC packet format and parameters + +### B.2.1 UDC Header and UDC Data Block format + +Figure B.2.1-1 shows the format of UDC Header and UDC Data Block. + +![Diagram of UDC header and UDC data block format. The header is 1 octet long and contains fields FU, FR, R, R, and Checksum. The data block is 2 octets long and contains the UDC Data Block. The diagram shows the header and data block stacked vertically, with the header on top. The header is divided into five fields: FU, FR, R, R, and Checksum. The data block is a single field labeled UDC Data Block. The diagram also shows the start of the next octet (Oct 2) and an ellipsis indicating further data.](678ac9faaa56bb929499cebeea83a110_img.jpg) + +| | | | | | | +|----------------|----|---|---|----------|-------| +| FU | FR | R | R | Checksum | Oct 1 | +| UDC Data Block | | | | | Oct 2 | + +... + +Diagram of UDC header and UDC data block format. The header is 1 octet long and contains fields FU, FR, R, R, and Checksum. The data block is 2 octets long and contains the UDC Data Block. The diagram shows the header and data block stacked vertically, with the header on top. The header is divided into five fields: FU, FR, R, R, and Checksum. The data block is a single field labeled UDC Data Block. The diagram also shows the start of the next octet (Oct 2) and an ellipsis indicating further data. + +Figure B.2.1-1: UDC header and UDC data block format + +### B.2.2 UDC parameters + +#### B.2.2.1 FU + +Length: 1 bit + +Indication of whether this packet is compressed by UDC protocol or not. Value '1' means the packet is compressed by UDC protocol. + +Table B.2.2.1-1: FU field + +| Bit | Description | +|-----|---------------------------------------------| +| 0 | Packet is not compressed using UDC protocol | +| 1 | Packet is compressed using UDC protocol | + +#### B.2.2.2 FR + +Length: 1 bit + +Indication of whether UDC compression buffer is reset or not. Value '1' means this is the first compressed packet after UDC buffer reset. + +**Table B.2.2.2-1: FR field** + +| Bit | Description | +|-----|------------------------------------| +| 0 | Compression buffer is not reset. | +| 1 | Compression buffer has been reset. | + +#### B.2.2.3 Checksum + +Length: 4 bits + +This field contains the validation bits for the compression buffer content: The checksum is calculated by the content of current compression buffer before the current packet is put into buffer. + +The checksum is derived from the values of the first 4 bytes and the last 4 bytes in the whole compression buffer. The calculation is described as follows: + +- Each byte is divided into two 4-bit numbers. +- The 16 4-bit numbers are added together to obtain a sum; +- The checksum is one's complement of the right-most 4 bits (i.e. 4 LSB) of the sum. + +An example of checksum calculation is shown in Annex B.2.3. + +### B.2.3 An example of UDC Checksum calculation + +The current UDC compression/decompression buffer has the following binary values for example: + +Header <1,1,0,0,0,1,0,1,0,0,1,1,1,1,1,1,0,0,0,1,1,0,0,1,0,1,0,1,0,1,0,0,0,1, ..... , +0,1,1,1,1,1,0,1,1,0,0,0,1,0,1,0,1,0,0,1,1,1,1,1,1,1,0,0,1,1,1,0,0> Tail + +The sum of the first 4 bytes and the last 4 bytes can be calculated: + +$$1100+0101+0011+1111+0001+1001+0101+0001+0111+1101+1000+1010+1001+1111+1001+1100 = 10000110;$$ + +And checksum value will be one's complement of the right-most 4 bits (i.e. 4 LSB) of the above sum. Hence checksum is 1001. + +# --- Annex C (informative): Change history + +| Change history | | | | | | | | +|----------------|-------------|------------|------|-----|-----|--------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New Version | +| 2017.03 | RAN2#9 7bis | R2-1703512 | - | - | - | First version. | x.y.z | +| 2017.04 | RAN2#9 7bis | R2-1703916 | - | - | - | Change clause name "Retransmission" to "Data recovery" | 0.0.1 | +| 2017.05 | RAN2#9 8 | R2-1704076 | - | - | - | Initial draft TS capturing outcome of e-mail discussion [97bis#24] | 0.0.5 | +| 2017.06 | RAN2 NR AH | R2-1706868 | - | - | - | Capture agreements made in RAN2#98 | 0.1.0 | +| 2017.08 | RAN2 NR AH | R2-1707507 | - | - | - | Capture agreements made in RAN2 NR AH#2 | 0.2.0 | +| 2017.08 | RAN2#9 9 | R2-1709097 | - | - | - | Adding integrity protection in clause 5.1.2 | 0.2.1 | +| 2017.08 | RAN2#9 9 | R2-1709753 | - | - | - | Capture agreements made in RAN2#99 | 0.3.0 | +| 2017.09 | RANP#7 7 | RP-171993 | - | - | - | Provided for information to RAN | 1.0.0 | +| 2017.10 | RAN2#9 9bis | R2-1713660 | - | - | - | Capture agreements made in RAN2#99bis | 1.0.1 | +| 2017.11 | RAN2#1 00 | R2-1714273 | - | - | - | Capture agreements made in RAN2#100 | 1.1.0 | +| 2017.12 | RP-78 | RP-172335 | - | - | - | Provided for approval to RAN | 2.0.0 | +| 2017/12 | RP-78 | | | | | Upgraded to Rel-15 (MCC) | 15.0.0 | +| 2018/03 | RP-79 | RP-180440 | 0002 | 1 | F | Corrections to PDCP specification | 15.1.0 | +| 2018/06 | RP-80 | RP-181215 | 0006 | 3 | F | Corrections to PDCP specification | 15.2.0 | +| | RP-80 | RP-181215 | 0009 | 1 | B | Introduction of PDCP duplication | 15.2.0 | +| 2018/09 | RP-81 | RP-181942 | 0011 | 4 | F | Clarification on PDCP transmission | 15.3.0 | +| 2018/12 | RP-82 | RP-182650 | 0022 | 1 | F | Suspend and resume of security | 15.4.0 | +| | RP-82 | RP-182655 | 0023 | - | F | Introducing PDCP suspend procedure | 15.4.0 | +| | RP-82 | RP-182656 | 0024 | - | F | Clarification on ciphering MAC-I | 15.4.0 | +| 2019/03 | RP-83 | RP-190544 | 0025 | 2 | F | Correction on the PDCP re-establishment for AM DRB | 15.5.0 | +| | RP-83 | RP-190540 | 0027 | 1 | F | Correction on PDCP SN length | 15.5.0 | +| 2019/06 | RP-84 | RP-191375 | 0031 | 1 | F | PDCP association with RLC for RBs configured with PDCP duplication | 15.6.0 | +| 2020/03 | RP-87 | RP-200346 | 0038 | 2 | B | 38.323 CR for NR V2X | 16.0.0 | +| | RP-87 | RP-200352 | 0039 | 3 | B | Introduction of NR IIOT | 16.0.0 | +| | RP-87 | RP-200347 | 0042 | 2 | B | Introduction of DAPS handover | 16.0.0 | +| 2020/07 | RP-88 | RP-201190 | 0032 | 6 | F | PDCP security issue about duplicate detection | 16.1.0 | +| | RP-88 | RP-201195 | 0045 | 3 | C | CR on 38.323 for NR mobility enhancement | 16.1.0 | +| | RP-88 | RP-201176 | 0048 | 1 | F | 38.323 CR for NR V2X | 16.1.0 | +| | RP-88 | RP-201181 | 0049 | 1 | F | NR PDCP corrections for NR IIOT | 16.1.0 | +| 2020/09 | RP-89 | RP-201963 | 0050 | 2 | F | Correction on receive operation when both EHC and out-of-order delivery are configured for a DRB | 16.2.0 | +| | RP-89 | RP-201932 | 0052 | 1 | F | PDCP entity associated with AM RLC entity | 16.2.0 | +| | RP-89 | RP-201927 | 0056 | - | F | 38.323 corrections on Sidelink | 16.2.0 | +| 2021/03 | RP-91 | RP-210692 | 0064 | 1 | F | Correction on PDCP transmit operation | 16.3.0 | +| 2021/06 | RP-92 | RP-211485 | 0074 | 1 | A | Correction on suspended AM DRB in PDCP re-establishment | 16.4.0 | +| | RP-92 | RP-211470 | 0078 | 1 | F | PDCP miscellaneous corrections | 16.4.0 | +| 2021/09 | RP-93 | RP-212442 | 0080 | 1 | F | CR for the ciphering of EHC header | 16.5.0 | +| 2021/12 | RP-94 | RP-213342 | 0082 | 1 | F | Correction to Window_Size for SLRB | 16.6.0 | +| 2022/03 | RP-95 | RP-220495 | 0085 | 1 | B | Introducing support of UP IP for EPC connected architectures using NR PDCP | 17.0.0 | +| | RP-95 | RP-220491 | 0086 | 2 | B | Introduction of SL Relay in 38.323 | 17.0.0 | +| | RP-95 | RP-220489 | 0087 | 1 | B | Introduction of the support for UDC in NR | 17.0.0 | +| | RP-95 | RP-220484 | 0088 | - | B | Introduction of NR MBS into 38.323 | 17.0.0 | +| 2022/06 | RP-96 | RP-221712 | 0092 | - | A | Correction on PDCP SN setting for SLRB transmit operation | 17.1.0 | +| | RP-96 | RP-221732 | 0093 | 1 | F | Correction on PDCP for SL relay | 17.1.0 | +| | RP-96 | RP-221731 | 0094 | 1 | F | Corrections to UDC | 17.1.0 | +| | RP-96 | RP-221712 | 0095 | - | A | Corrections on receiving PDCP entity establishment for SL-SRB0/SL-SRB1 | 17.1.0 | +| | RP-96 | RP-221754 | 0096 | - | F | PDCP Corrections for MBS | 17.1.0 | +| 2022/09 | RP-97 | RP-222524 | 0097 | 1 | F | Correction on PDCP for L2 U2N Relay | 17.2.0 | +| | RP-97 | RP-222523 | 0098 | 1 | F | Corrections for MBS 38.323 | 17.2.0 | +| 2022/12 | RP-98 | RP-223406 | 0102 | 4 | F | MBS corrections for PDCP | 17.3.0 | +| | RP-98 | RP-223412 | 0104 | 2 | F | PDCP correction for SL relay | 17.3.0 | +| | RP-98 | RP-223413 | 0105 | 2 | F | Correction on PDCP Control PDU for UDC feedback | 17.3.0 | +| | RP-98 | RP-223414 | 0111 | 1 | A | Data volume calculation for DAPS | 17.3.0 | +| | RP-98 | RP-223406 | 0112 | - | F | PDCP Initialisation of MRB | 17.3.0 | +| 2023/03 | RP-99 | RP-230692 | 0115 | 1 | F | Clarification on PDCP for L2 U2N Relay | 17.4.0 | +| 2023/06 | RP-100 | RP-231416 | 0123 | 1 | F | Clarification on the services expected from SRAP layer | 17.5.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-----------------------------------------------------------|--------| +| 2023/12 | RP-102 | RP-233897 | 0126 | 2 | B | Introduction of NR sidelink PDCP duplication in TS 38.323 | 18.0.0 | +| | RP-102 | RP-233904 | 0127 | 1 | B | Introduction of Enhanced NR Sidelink Relay | 18.0.0 | +| | RP-102 | RP-233908 | 0128 | 2 | B | Introduction of XR Enhancements | 18.0.0 | +| | RP-102 | RP-233907 | 0130 | 1 | B | Introduction of eMBS in TS 38.323 | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38331/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg b/marked/Rel-18/38_series/38331/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5cad2e0498d5d079a620cdde8dba4d928fa8b324 --- /dev/null +++ b/marked/Rel-18/38_series/38331/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5cde17fd044a8963e937ec9ab4d13caae1b4a9679c81c79ebf53a78ce2bd93c8 +size 12318 diff --git a/marked/Rel-18/38_series/38331/16152cf1d84aea10848758f51a91ff6a_img.jpg b/marked/Rel-18/38_series/38331/16152cf1d84aea10848758f51a91ff6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1c9486903f0b7727a87a3ea8c406f0771d23315 --- /dev/null +++ b/marked/Rel-18/38_series/38331/16152cf1d84aea10848758f51a91ff6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dda617030bb7ad44700b4743978e1ee1515f8d63090e584bdbf65a5166651913 +size 7360 diff --git a/marked/Rel-18/38_series/38331/16da2d7b436c26f2efc4b51b2aae0fed_img.jpg b/marked/Rel-18/38_series/38331/16da2d7b436c26f2efc4b51b2aae0fed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8f373eb5b3d1bd54d537a03b7d1f51dd8ec1b46 --- /dev/null +++ b/marked/Rel-18/38_series/38331/16da2d7b436c26f2efc4b51b2aae0fed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ff5cc17ac49b46c7d28e09667b9df91168eed120b1ad1dcbb4fd89409c7782a +size 9559 diff --git a/marked/Rel-18/38_series/38331/180f1fb534ad2c1d918ede57612b3fb0_img.jpg b/marked/Rel-18/38_series/38331/180f1fb534ad2c1d918ede57612b3fb0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d7017df981888ddb5c97cd26c134b78b39dabb00 --- /dev/null +++ b/marked/Rel-18/38_series/38331/180f1fb534ad2c1d918ede57612b3fb0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:107ee2fab44faf71e008796151166b435e2604bb667421a87467b0cd6c4fb2db +size 14051 diff --git a/marked/Rel-18/38_series/38331/187d05bf7ead21e1394b61320d8b3632_img.jpg b/marked/Rel-18/38_series/38331/187d05bf7ead21e1394b61320d8b3632_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56c12c21c352f6d830b03b32724ce5fe7eb8479e --- /dev/null +++ b/marked/Rel-18/38_series/38331/187d05bf7ead21e1394b61320d8b3632_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e4b5656b45cf1721cf24d40c7c75b3002b64dad25d7b505392d55727d6b440b8 +size 15818 diff --git a/marked/Rel-18/38_series/38331/1ab8da167ae10f58b4b0b57e0c1283ad_img.jpg b/marked/Rel-18/38_series/38331/1ab8da167ae10f58b4b0b57e0c1283ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..379e342a6db92b8f20ab985c72c3693083964c44 --- /dev/null +++ b/marked/Rel-18/38_series/38331/1ab8da167ae10f58b4b0b57e0c1283ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:377381fb4adc34d174e347507a7dae568e8d42514ad8e15c4c58d7d58677e798 +size 26208 diff --git a/marked/Rel-18/38_series/38331/1bd6a020aa71784ed74367899560cbb9_img.jpg b/marked/Rel-18/38_series/38331/1bd6a020aa71784ed74367899560cbb9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba044e359b949ca0ae9cc3fcb5ec1d314ce98ce1 --- /dev/null +++ b/marked/Rel-18/38_series/38331/1bd6a020aa71784ed74367899560cbb9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7dfb3f773f16a90cd4c28f4bd68222449a3b78161c00e18fa58f0df5ce77a442 +size 13165 diff --git a/marked/Rel-18/38_series/38331/1d44bdd1863e06a905f90ab64d0daaa7_img.jpg b/marked/Rel-18/38_series/38331/1d44bdd1863e06a905f90ab64d0daaa7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f866baac8d88dda757932126537213486fa4a34 --- /dev/null +++ b/marked/Rel-18/38_series/38331/1d44bdd1863e06a905f90ab64d0daaa7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7de97cb6c8885416b129ed1248460cefe8560873930094fe41c4028f92eee4a5 +size 8964 diff --git a/marked/Rel-18/38_series/38331/20136850feb70fd71c7d41cdae203ebb_img.jpg b/marked/Rel-18/38_series/38331/20136850feb70fd71c7d41cdae203ebb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d087b347d4949d8c531b875c89a2a5a2efa117a0 --- /dev/null +++ b/marked/Rel-18/38_series/38331/20136850feb70fd71c7d41cdae203ebb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:69159d5819f61e17ad9099a44864d1c01d3a96f1fdbaaea80f9a28f9dcaac2b2 +size 23738 diff --git a/marked/Rel-18/38_series/38331/23cb65390082ab306c15bd3d8196135e_img.jpg b/marked/Rel-18/38_series/38331/23cb65390082ab306c15bd3d8196135e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..65e5e6c3222eaf302519983a199b27bcbc519073 --- /dev/null +++ b/marked/Rel-18/38_series/38331/23cb65390082ab306c15bd3d8196135e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9542473f95503e045eb94f3928ed53b06a62651156e77dcc135fabef9f04a638 +size 16713 diff --git a/marked/Rel-18/38_series/38331/29100fce6dce19cea57712363976bf2c_img.jpg b/marked/Rel-18/38_series/38331/29100fce6dce19cea57712363976bf2c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cb73e452c2eb4d36606fb003336a1ecc369448ec --- /dev/null +++ b/marked/Rel-18/38_series/38331/29100fce6dce19cea57712363976bf2c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ad9c41dfe971f726d50e57a5d3500cd8e2fa2bf2b0bff25b3781ef161a1e0b9 +size 10227 diff --git a/marked/Rel-18/38_series/38331/2beb95006f1933bed737cfe1e6598db8_img.jpg b/marked/Rel-18/38_series/38331/2beb95006f1933bed737cfe1e6598db8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..14a1a27f014f39280796f5cc97d05902c95dfc7d --- /dev/null +++ b/marked/Rel-18/38_series/38331/2beb95006f1933bed737cfe1e6598db8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6c8ff635950a3a1c678c5f348afc1f06fdaf64011171d25383a59f7af8d7cfa +size 23734 diff --git a/marked/Rel-18/38_series/38331/2cf3896394a2342a2b46c504ab9a8830_img.jpg b/marked/Rel-18/38_series/38331/2cf3896394a2342a2b46c504ab9a8830_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d0373fff53a082ce523f4ed0b60ae5d6b04ac06 --- /dev/null +++ b/marked/Rel-18/38_series/38331/2cf3896394a2342a2b46c504ab9a8830_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fcc37ce0fe36b7a2114171f76ffcbf5f8cb7b3aca3c94bf9b0bb4c0b759a6eef +size 18536 diff --git a/marked/Rel-18/38_series/38331/2dc649aff45a8a0924db45fc3bd6aabb_img.jpg b/marked/Rel-18/38_series/38331/2dc649aff45a8a0924db45fc3bd6aabb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..30857454c9748f7346419a27ee26a6ce4ac8520d --- /dev/null +++ b/marked/Rel-18/38_series/38331/2dc649aff45a8a0924db45fc3bd6aabb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f070fcc1279ceaf02696dabf3c8665c91c520a9653097abf0e2d7172136bb84 +size 20452 diff --git a/marked/Rel-18/38_series/38331/331afcb1534110b4c4f6ddf553a0f7e0_img.jpg b/marked/Rel-18/38_series/38331/331afcb1534110b4c4f6ddf553a0f7e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..41c38c851c25118471ce501681bda0a0b71ba08b --- /dev/null +++ b/marked/Rel-18/38_series/38331/331afcb1534110b4c4f6ddf553a0f7e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e76d19194126b1b5a681be17e4657a154d76744b42d59d7792d3a05391954090 +size 56568 diff --git a/marked/Rel-18/38_series/38331/350dece6293a0ac3d4c9e4bf41eefa5d_img.jpg b/marked/Rel-18/38_series/38331/350dece6293a0ac3d4c9e4bf41eefa5d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..062cbe34dd742ae95274bbf4fc54a685597e166e --- /dev/null +++ b/marked/Rel-18/38_series/38331/350dece6293a0ac3d4c9e4bf41eefa5d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cef33be63e6311365225a0e579e784dc838dd67cdab65e3d714091beadb2b53a +size 16416 diff --git a/marked/Rel-18/38_series/38331/3c88e5ce372025db2b065940e4a4391b_img.jpg b/marked/Rel-18/38_series/38331/3c88e5ce372025db2b065940e4a4391b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8b8a8e37262074112a981f60bcab0e9a0ad3e67 --- /dev/null +++ b/marked/Rel-18/38_series/38331/3c88e5ce372025db2b065940e4a4391b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e8994fc85b1f307de183fa3caf882d1669fbce019d50104ab51b6bc3fdd91bb4 +size 15822 diff --git a/marked/Rel-18/38_series/38331/487046a4bbc8c18c86fed4cd5a698fcc_img.jpg b/marked/Rel-18/38_series/38331/487046a4bbc8c18c86fed4cd5a698fcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d6292f7802a34d5791e6f52dd78f5160f4de62e5 --- /dev/null +++ b/marked/Rel-18/38_series/38331/487046a4bbc8c18c86fed4cd5a698fcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:81961ff5486447260e421b36f8fea45aea82970b30582001e01afb128af65297 +size 13422 diff --git a/marked/Rel-18/38_series/38331/497d7e14540664a2914557cad79f3791_img.jpg b/marked/Rel-18/38_series/38331/497d7e14540664a2914557cad79f3791_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d9cfb9266349ca9c11b65decf4f5cefc84ecdcab --- /dev/null +++ b/marked/Rel-18/38_series/38331/497d7e14540664a2914557cad79f3791_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa21fe902a65b9d529545900f770c567e2b7b629f1ffbecf2313264e4f97d186 +size 10233 diff --git a/marked/Rel-18/38_series/38331/5661815043254c37a4e3e4833f51e727_img.jpg b/marked/Rel-18/38_series/38331/5661815043254c37a4e3e4833f51e727_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..88dc5376e184308c204f23e739b6e89b74fd99bc --- /dev/null +++ b/marked/Rel-18/38_series/38331/5661815043254c37a4e3e4833f51e727_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2cc0dbb9280c4fa76624a8f3d973e23f7a0cbc49b54ba2ae6693ac976f426205 +size 3173 diff --git a/marked/Rel-18/38_series/38331/572cf014db14c8234f91c07d5a5a28c6_img.jpg b/marked/Rel-18/38_series/38331/572cf014db14c8234f91c07d5a5a28c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..23c599b0d09109dcf7b1342771ea00f5f3a96003 --- /dev/null +++ b/marked/Rel-18/38_series/38331/572cf014db14c8234f91c07d5a5a28c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6bee626224f6b89dc3ae5652333d5a2f7c9ec236b2f05d35c019f9c13ea1c786 +size 15022 diff --git a/marked/Rel-18/38_series/38331/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38331/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb4b9cff16303c5282d46b47ff42f2fc336a0626 --- /dev/null +++ b/marked/Rel-18/38_series/38331/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da555e3099b1c431594f2a269889361fc8edd6c97e1d00a0c79c3aa513c0c1bb +size 10782 diff --git a/marked/Rel-18/38_series/38331/600d42b593738a8e023082e291628eaf_img.jpg b/marked/Rel-18/38_series/38331/600d42b593738a8e023082e291628eaf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..34320790600600007550443f30c73c5b71a94eb4 --- /dev/null +++ b/marked/Rel-18/38_series/38331/600d42b593738a8e023082e291628eaf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9acd193ba39f58cea9a306db28126b09ec5c20a1481986dd8c724c370d810515 +size 17699 diff --git a/marked/Rel-18/38_series/38331/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38331/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..04e19bd146cf2f8856910f1982a21618aa11de44 --- /dev/null +++ b/marked/Rel-18/38_series/38331/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ad388975d5c2526709e8592ce85edabfeffb6bc809023fb4e2023638d3a53f1 +size 7654 diff --git a/marked/Rel-18/38_series/38331/67c5b121b58d497a6de5addf4e7bd555_img.jpg b/marked/Rel-18/38_series/38331/67c5b121b58d497a6de5addf4e7bd555_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..851772727f1e2b257a3d0c14c5ec2693fdcfc8a1 --- /dev/null +++ b/marked/Rel-18/38_series/38331/67c5b121b58d497a6de5addf4e7bd555_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ffba2488bd97a9a594ea558beb49f393e285bc4fd86a8cc513bd1d9a342a53d +size 18818 diff --git a/marked/Rel-18/38_series/38331/691626a7032a642bb74793336c37e274_img.jpg b/marked/Rel-18/38_series/38331/691626a7032a642bb74793336c37e274_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a90e89b9a32b5383d390b6f2af8d46abca30f4d3 --- /dev/null +++ b/marked/Rel-18/38_series/38331/691626a7032a642bb74793336c37e274_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2ede52330374198401b898dad7695dc14e6bd282a1e49e33ba23525719ad1c70 +size 6048 diff --git a/marked/Rel-18/38_series/38331/6984a27b2b89e0995d5216ec29b41d1c_img.jpg b/marked/Rel-18/38_series/38331/6984a27b2b89e0995d5216ec29b41d1c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e49d596d93bde757153f47b392d08a0f4bece6d9 --- /dev/null +++ b/marked/Rel-18/38_series/38331/6984a27b2b89e0995d5216ec29b41d1c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03acd67b6baf7a25bc9d6e14586c9ffffd68bb28052b27e27eeb8de97e303de0 +size 16223 diff --git a/marked/Rel-18/38_series/38331/6d67eee81b97a14e06a6fe57a95aff36_img.jpg b/marked/Rel-18/38_series/38331/6d67eee81b97a14e06a6fe57a95aff36_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..266b1fde40adc26aff344ff2dcda91c6c6407172 --- /dev/null +++ b/marked/Rel-18/38_series/38331/6d67eee81b97a14e06a6fe57a95aff36_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c39bd2ca8324062bda1b72b301ef990e5f1fa1ca70e6ac931b0c797f4e9a24c +size 15766 diff --git a/marked/Rel-18/38_series/38331/759c7d62402f0b4651ddce292be5bdef_img.jpg b/marked/Rel-18/38_series/38331/759c7d62402f0b4651ddce292be5bdef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..206f7a62b9d3c945a0e7133fe28417a9d12ca903 --- /dev/null +++ b/marked/Rel-18/38_series/38331/759c7d62402f0b4651ddce292be5bdef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1cd321a553d6328c80d38aa2a9351851f168f0ef0264f64bed6ee6207d452544 +size 11322 diff --git a/marked/Rel-18/38_series/38331/76d19e4271bf243b20d55a98efd51483_img.jpg b/marked/Rel-18/38_series/38331/76d19e4271bf243b20d55a98efd51483_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e7848e13443f1f43d5ee2630f661c6077ec79b49 --- /dev/null +++ b/marked/Rel-18/38_series/38331/76d19e4271bf243b20d55a98efd51483_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ad5812e098f58c500254bc9c528797da25077f260dc99dae5f86f3edd38f448 +size 18964 diff --git a/marked/Rel-18/38_series/38331/7ed5d5770331f31ade15439a21c31425_img.jpg b/marked/Rel-18/38_series/38331/7ed5d5770331f31ade15439a21c31425_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d8af185b83237bd7d4f7128c3e4140d53881c84 --- /dev/null +++ b/marked/Rel-18/38_series/38331/7ed5d5770331f31ade15439a21c31425_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:07e265d819ee2bc848bde8212fec7b1594863989cab0b37c82f36d73ea412ec6 +size 62038 diff --git a/marked/Rel-18/38_series/38331/8294325c2b0ef386b6f50eb1d6226b64_img.jpg b/marked/Rel-18/38_series/38331/8294325c2b0ef386b6f50eb1d6226b64_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1e7c1b79c5d8c9a17b7022d43cd4e1b2348bd1a --- /dev/null +++ b/marked/Rel-18/38_series/38331/8294325c2b0ef386b6f50eb1d6226b64_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cccd59bef134c04714fb83b999a1a23ca8502736b1085858d616905d95e2ceb5 +size 21183 diff --git a/marked/Rel-18/38_series/38331/84e5b251aa38db522f76f5cc3afcb853_img.jpg b/marked/Rel-18/38_series/38331/84e5b251aa38db522f76f5cc3afcb853_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..495e73123e2730a6c0df70b76067667c729b0190 --- /dev/null +++ b/marked/Rel-18/38_series/38331/84e5b251aa38db522f76f5cc3afcb853_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9175b3a2d947a860c8942b216bf6de35576ca804b340309c322397aabc79eeb2 +size 18684 diff --git a/marked/Rel-18/38_series/38331/886963464425186f4a465fa8155d2a3c_img.jpg b/marked/Rel-18/38_series/38331/886963464425186f4a465fa8155d2a3c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8cb3c8ef9864c47872b7e70da77e56665a39026b --- /dev/null +++ b/marked/Rel-18/38_series/38331/886963464425186f4a465fa8155d2a3c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:25488ed2edba6e47f375bbdc287e0a275816f21b7dcec0385b26335b8136503f +size 12958 diff --git a/marked/Rel-18/38_series/38331/8b5a2bf5517051acf8bcc2587bcb73a1_img.jpg b/marked/Rel-18/38_series/38331/8b5a2bf5517051acf8bcc2587bcb73a1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed8ee016153eee5bf3bea9b5589c3f767fa93c02 --- /dev/null +++ b/marked/Rel-18/38_series/38331/8b5a2bf5517051acf8bcc2587bcb73a1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6567940c3b682eef7c3df3e26845d5fc569bc21c3f892cc60d778e465691bdb0 +size 14785 diff --git a/marked/Rel-18/38_series/38331/902baf7323e91b89aba4ea27d9c3d13d_img.jpg b/marked/Rel-18/38_series/38331/902baf7323e91b89aba4ea27d9c3d13d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b388e10eb04409edf3c2e1e1fbaaac61c01c4eee --- /dev/null +++ b/marked/Rel-18/38_series/38331/902baf7323e91b89aba4ea27d9c3d13d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d143d0b9c695abe82ed1204d79774ff4ec75270800765f7cf106e6da20509f1 +size 10727 diff --git a/marked/Rel-18/38_series/38331/909e1cd5419742a8ea8a95a16a40d849_img.jpg b/marked/Rel-18/38_series/38331/909e1cd5419742a8ea8a95a16a40d849_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9657c902d228a6dfcf9ab814ec4abefe691329ad --- /dev/null +++ b/marked/Rel-18/38_series/38331/909e1cd5419742a8ea8a95a16a40d849_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f314e65491d89c29fdd328249916b4dfec5fcb8cd1ba745e0170eed4f86fc538 +size 15542 diff --git a/marked/Rel-18/38_series/38331/921f8fa0f7ce2c9956f20d33162c13a2_img.jpg b/marked/Rel-18/38_series/38331/921f8fa0f7ce2c9956f20d33162c13a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9fabcd5bd87910c7cc2b7fb25dbe9f561adcd63a --- /dev/null +++ b/marked/Rel-18/38_series/38331/921f8fa0f7ce2c9956f20d33162c13a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c7035582d3c6b299197ff81891571a6f0bcb98f49ea8e56b8fc45fca8a1f2440 +size 14910 diff --git a/marked/Rel-18/38_series/38331/977811d1c73b74f801be9f4c376694ca_img.jpg b/marked/Rel-18/38_series/38331/977811d1c73b74f801be9f4c376694ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3704b224c0c480d4f65bbf2f26e173bea3f12c5a --- /dev/null +++ b/marked/Rel-18/38_series/38331/977811d1c73b74f801be9f4c376694ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa694e6205bbed4a0d42b383958a55ff13d26daea2c2cee0b3a676dc53c88d3e +size 15398 diff --git a/marked/Rel-18/38_series/38331/985267cff5b5d65ce5c180ff2ef37118_img.jpg b/marked/Rel-18/38_series/38331/985267cff5b5d65ce5c180ff2ef37118_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad5e86901ddf7863fd6bb5a61ac12d01df9e200f --- /dev/null +++ b/marked/Rel-18/38_series/38331/985267cff5b5d65ce5c180ff2ef37118_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:203bbddd7565683dcd264ca8515a58052b35ce5cbab8d63ca8e21e24d1acc4a7 +size 15851 diff --git a/marked/Rel-18/38_series/38331/9e26cd5584f423e1b2155fb341db579f_img.jpg b/marked/Rel-18/38_series/38331/9e26cd5584f423e1b2155fb341db579f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7aeca96745f2e729962526e4cf3be24199019cdf --- /dev/null +++ b/marked/Rel-18/38_series/38331/9e26cd5584f423e1b2155fb341db579f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e8a166a3776bba2b1fdc00acd98ee7563164a41c7fb64815d3c437b4e3a9cd08 +size 21993 diff --git a/marked/Rel-18/38_series/38331/9ef15a4afab1416db28b91184862a3a5_img.jpg b/marked/Rel-18/38_series/38331/9ef15a4afab1416db28b91184862a3a5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92d4d3e602a2b95d8ccde723830651a4b91b77a8 --- /dev/null +++ b/marked/Rel-18/38_series/38331/9ef15a4afab1416db28b91184862a3a5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:34b40c457a339ec2ede536a588bdbf8dd8ff2bc96107ec82a41e897023833484 +size 33961 diff --git a/marked/Rel-18/38_series/38331/a057800564be3506d2d87b6a4daee25b_img.jpg b/marked/Rel-18/38_series/38331/a057800564be3506d2d87b6a4daee25b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad17fa8fb18b80dd1c9b0ca28ca2a401e8ff57b3 --- /dev/null +++ b/marked/Rel-18/38_series/38331/a057800564be3506d2d87b6a4daee25b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a4d12ff58dc2d16d4ccc48983e10fced076734f5b7cb627185c414888aa541ec +size 21392 diff --git a/marked/Rel-18/38_series/38331/a49e8b30bf89da457ff3ff90d029e4ec_img.jpg b/marked/Rel-18/38_series/38331/a49e8b30bf89da457ff3ff90d029e4ec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..594d3e71d4345c6fc7b6951cdfae5848f74d17a6 --- /dev/null +++ b/marked/Rel-18/38_series/38331/a49e8b30bf89da457ff3ff90d029e4ec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f2d655396340035849ca3060dc2805f43b8435f8b8eededc671d1b5724f33bbb +size 9269 diff --git a/marked/Rel-18/38_series/38331/a9241101d638c568cd5a84ab7ad39f15_img.jpg b/marked/Rel-18/38_series/38331/a9241101d638c568cd5a84ab7ad39f15_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..03411b150d40c9ed240ded8b085f1f0fd72f6fd5 --- /dev/null +++ b/marked/Rel-18/38_series/38331/a9241101d638c568cd5a84ab7ad39f15_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:302358fa6c7b9e27a91f60d76fba0f963be127e71ada336452a1228e67738121 +size 19376 diff --git a/marked/Rel-18/38_series/38331/aa0ca8b71d46db8787e0e4b249325750_img.jpg b/marked/Rel-18/38_series/38331/aa0ca8b71d46db8787e0e4b249325750_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62b02587726ce58d7e84be27ec300c8693f7a8de --- /dev/null +++ b/marked/Rel-18/38_series/38331/aa0ca8b71d46db8787e0e4b249325750_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ced2de4d98e45cd6e009ed32520cf959bab0dff6eb1690c2a0bedc33685df55 +size 14382 diff --git a/marked/Rel-18/38_series/38331/ada2aa7cce9cff9cf116d9ae2b8b7c27_img.jpg b/marked/Rel-18/38_series/38331/ada2aa7cce9cff9cf116d9ae2b8b7c27_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f75f8d39e8c187050ef0cc4ff2b33450b68c5ac --- /dev/null +++ b/marked/Rel-18/38_series/38331/ada2aa7cce9cff9cf116d9ae2b8b7c27_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed96e3ff0c647c7c242e6cb6f21fc8a0d9ad5131a841727559fa20bf771e0d5f +size 20870 diff --git a/marked/Rel-18/38_series/38331/b44f89b176c971c7dd264c07bfef2c2a_img.jpg b/marked/Rel-18/38_series/38331/b44f89b176c971c7dd264c07bfef2c2a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec6c88933931adbebc5c61fbf02f2bdd671ae724 --- /dev/null +++ b/marked/Rel-18/38_series/38331/b44f89b176c971c7dd264c07bfef2c2a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4307c8ee9ac8a3632b0a110f93a88f9349f2fda85bcea8728b7f1d2416413ae +size 7515 diff --git a/marked/Rel-18/38_series/38331/be385895e822fc377a2163dc96fd7eee_img.jpg b/marked/Rel-18/38_series/38331/be385895e822fc377a2163dc96fd7eee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..17bf22a6620744658bc417dd9259b21f256c89ed --- /dev/null +++ b/marked/Rel-18/38_series/38331/be385895e822fc377a2163dc96fd7eee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fab1db788d74a5e9d9556cce7d13433815ed5c48c51570d204f0d0cd60d3f794 +size 9037 diff --git a/marked/Rel-18/38_series/38331/bfc7918b689a38bc811276e0cc69477e_img.jpg b/marked/Rel-18/38_series/38331/bfc7918b689a38bc811276e0cc69477e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3df6214679d17dc35394834bac12edb0d15d728b --- /dev/null +++ b/marked/Rel-18/38_series/38331/bfc7918b689a38bc811276e0cc69477e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ca0cb2d6a9c0621d23ded4c4ff785d4b7ce1b3c0a5b09bfc43e6bc27314d920 +size 13387 diff --git a/marked/Rel-18/38_series/38331/bfca6639dd4b8480f2d96d2b61c806d9_img.jpg b/marked/Rel-18/38_series/38331/bfca6639dd4b8480f2d96d2b61c806d9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..902bffaad3859dda384bf556dfd5ff87884e57a0 --- /dev/null +++ b/marked/Rel-18/38_series/38331/bfca6639dd4b8480f2d96d2b61c806d9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f7dd52122c1c6d4f310e5f4de57504171bd284ecbff794a4cdcaae0f3270476 +size 18591 diff --git a/marked/Rel-18/38_series/38331/c1b762c358fd423d6686563b3fde7750_img.jpg b/marked/Rel-18/38_series/38331/c1b762c358fd423d6686563b3fde7750_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5d276890713492057123ae3bf83c0a5cf4d9c453 --- /dev/null +++ b/marked/Rel-18/38_series/38331/c1b762c358fd423d6686563b3fde7750_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e019e6cd92304d1d2a5229860cff71a8f550c403b3c51b0f7c7b913dd7d93b93 +size 15007 diff --git a/marked/Rel-18/38_series/38331/ca5555bb37f54857199d243feff8479e_img.jpg b/marked/Rel-18/38_series/38331/ca5555bb37f54857199d243feff8479e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..23d0a6e3650659b1c658651f1cf7559efda82b31 --- /dev/null +++ b/marked/Rel-18/38_series/38331/ca5555bb37f54857199d243feff8479e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e1f36fc492825db3380ceae4d4bd2c8cb8b7fe1aa210b8c4c1cfad1f390ecfe +size 17833 diff --git a/marked/Rel-18/38_series/38331/d04c50badc78d5ba47bf4e352af4a754_img.jpg b/marked/Rel-18/38_series/38331/d04c50badc78d5ba47bf4e352af4a754_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ecb64fe2874b3bc178d7210eba5ee9bf8788d5e2 --- /dev/null +++ b/marked/Rel-18/38_series/38331/d04c50badc78d5ba47bf4e352af4a754_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02b887698904faa3d0574fac5c0621797bc8c3ce182e8189a9551e554f4ae28a +size 11325 diff --git a/marked/Rel-18/38_series/38331/d197b6ded14ea918198a280ff07122b8_img.jpg b/marked/Rel-18/38_series/38331/d197b6ded14ea918198a280ff07122b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc49d113e184a85778499ad2cd081ccd00d1ab7a --- /dev/null +++ b/marked/Rel-18/38_series/38331/d197b6ded14ea918198a280ff07122b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6ca24afb031cd2c676020cc2ef4edff4f9191f2b5b1223738d826d079867dc6c +size 11395 diff --git a/marked/Rel-18/38_series/38331/d1ad67cff357f77c9114c037e193f585_img.jpg b/marked/Rel-18/38_series/38331/d1ad67cff357f77c9114c037e193f585_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f685af2ab2cd68138c68f7adcf21ee5e3ff68e1a --- /dev/null +++ b/marked/Rel-18/38_series/38331/d1ad67cff357f77c9114c037e193f585_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a4447dce21da503d41a68d52e0f614c1b9c70b769df0661167423d362191e9bf +size 9670 diff --git a/marked/Rel-18/38_series/38331/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-18/38_series/38331/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..868dc3bf6fad6158f2eb7a628b8fa17b1f792f0d --- /dev/null +++ b/marked/Rel-18/38_series/38331/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e4c8e9b81898235983ddc233ab75e650a63e59440da61d7b2a940cef913eefb9 +size 16960 diff --git a/marked/Rel-18/38_series/38331/ddee3e67e0dfc22e25188fa635a19558_img.jpg b/marked/Rel-18/38_series/38331/ddee3e67e0dfc22e25188fa635a19558_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f9aad0cbd81567ed5eeea7c4d33df646dde26b27 --- /dev/null +++ b/marked/Rel-18/38_series/38331/ddee3e67e0dfc22e25188fa635a19558_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26c24a766dbdf8c13b205698b204ef63711769eaf6f8f094512fbe37a087d3be +size 18046 diff --git a/marked/Rel-18/38_series/38331/df82d77a0d2637cbf2da9ea920a554fa_img.jpg b/marked/Rel-18/38_series/38331/df82d77a0d2637cbf2da9ea920a554fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0fbc55fb0a8e284631728781d1a9672ad9b1b5d8 --- /dev/null +++ b/marked/Rel-18/38_series/38331/df82d77a0d2637cbf2da9ea920a554fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e5137d0038957e901bc073ed53faa9cad58efd3d2c32769932c20c0c33aa51dd +size 10113 diff --git a/marked/Rel-18/38_series/38331/df935fc9efbd024af4ba77e46bb0bb19_img.jpg b/marked/Rel-18/38_series/38331/df935fc9efbd024af4ba77e46bb0bb19_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd48ee0a5787afc21d6d960446781aa95cb16c72 --- /dev/null +++ b/marked/Rel-18/38_series/38331/df935fc9efbd024af4ba77e46bb0bb19_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fea9c3fff4277ccb21655c9bf5420d429cfb8caeab444b480c4938ce20c795dd +size 9463 diff --git a/marked/Rel-18/38_series/38331/dfafe39c233a62ec8ebd71e42992c14d_img.jpg b/marked/Rel-18/38_series/38331/dfafe39c233a62ec8ebd71e42992c14d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6dd479bfb76ae6181ed89c3175428fe8c30f14e --- /dev/null +++ b/marked/Rel-18/38_series/38331/dfafe39c233a62ec8ebd71e42992c14d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:711231a59e0363fb24129ea2f0a97d60522b1d0aed2c029510986f8b76ab48f1 +size 24941 diff --git a/marked/Rel-18/38_series/38331/e2c120be98ede6deb60dd341f5a9803b_img.jpg b/marked/Rel-18/38_series/38331/e2c120be98ede6deb60dd341f5a9803b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fe3fed4d46323e13e9bd1ff1e0a2460e53cdcd1d --- /dev/null +++ b/marked/Rel-18/38_series/38331/e2c120be98ede6deb60dd341f5a9803b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6e51b5a49d44c0cba805b89fee842bbfeb3b6f4fb125142f94f47d5c9df45a33 +size 17149 diff --git a/marked/Rel-18/38_series/38331/edcb05fc7c8056bf485bf8adeb45e1c8_img.jpg b/marked/Rel-18/38_series/38331/edcb05fc7c8056bf485bf8adeb45e1c8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6bf500947d7a10465cfbcbe182ad07416972ac40 --- /dev/null +++ b/marked/Rel-18/38_series/38331/edcb05fc7c8056bf485bf8adeb45e1c8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:17358739516c935aa9d1c285b9402856989cdd74c0fd33cf97222bd52568b034 +size 14451 diff --git a/marked/Rel-18/38_series/38331/ef5f5c6665b6ae13660ede412333ba45_img.jpg b/marked/Rel-18/38_series/38331/ef5f5c6665b6ae13660ede412333ba45_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd9d43a9ac380d0608fae41d10372dab121d4196 --- /dev/null +++ b/marked/Rel-18/38_series/38331/ef5f5c6665b6ae13660ede412333ba45_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d0ebf589c6836060864051b3f897e92fba2f81804fa6b3e0b8a1fa5242fe4985 +size 14056 diff --git a/marked/Rel-18/38_series/38331/f806f2cd3ad03aea066cdb9a93f5bf56_img.jpg b/marked/Rel-18/38_series/38331/f806f2cd3ad03aea066cdb9a93f5bf56_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..19c5e04f1c9813768b577ede79e86761ef7a3539 --- /dev/null +++ b/marked/Rel-18/38_series/38331/f806f2cd3ad03aea066cdb9a93f5bf56_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5856318b25ee3e65ad94d9a6233c8624553da19c93c65b34ac9f0ff256b5098f +size 8224 diff --git a/marked/Rel-18/38_series/38331/ff08f7fb49327c692a7e63a670ad0433_img.jpg b/marked/Rel-18/38_series/38331/ff08f7fb49327c692a7e63a670ad0433_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7db3b7a5ca521c95fd36c382dc514f728f2637eb --- /dev/null +++ b/marked/Rel-18/38_series/38331/ff08f7fb49327c692a7e63a670ad0433_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa74a701b5e8ce15b6f7274f6bfaeacd4f7e44da69a706919ae242382c3a461c +size 15202 diff --git a/marked/Rel-18/38_series/38331/ffd8c2986aabedc8b6db2d8f2ed7a994_img.jpg b/marked/Rel-18/38_series/38331/ffd8c2986aabedc8b6db2d8f2ed7a994_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f4cf415e7565b2fec53fb0bf63eebaa04cb38134 --- /dev/null +++ b/marked/Rel-18/38_series/38331/ffd8c2986aabedc8b6db2d8f2ed7a994_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7de7234e0bafb0e3a6ea7510a229a77083cd42653c535d9640cf486cf018421e +size 11787 diff --git a/marked/Rel-18/38_series/38331/raw.md b/marked/Rel-18/38_series/38331/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0523e2cea156a81c6af404f4ef80d0116345f49b --- /dev/null +++ b/marked/Rel-18/38_series/38331/raw.md @@ -0,0 +1,66286 @@ +# 3GPP TS 38.331 V18.0.0 (2023-12) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 18)** + +![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +The 5G logo features the text "5G" in a bold, black, sans-serif font. Above the "5G" text is a green graphic 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 consists of the letters "3GPP" in a stylized, bold, black font. Below the "3G" is a red graphic of three curved lines, similar to the 5G logo. Below the entire 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 + + +**3GPP** + +# Contents + +| | | +|----------------------------------------------------------------|----| +| Foreword..... | 26 | +| 1 Scope..... | 27 | +| 2 References..... | 27 | +| 3 Definitions, symbols and abbreviations..... | 30 | +| 3.1 Definitions..... | 30 | +| 3.2 Abbreviations..... | 32 | +| 4 General..... | 36 | +| 4.1 Introduction..... | 36 | +| 4.2 Architecture..... | 36 | +| 4.2.1 UE states and state transitions including inter RAT..... | 36 | +| 4.2.2 Signalling radio bearers..... | 39 | +| 4.3 Services..... | 40 | +| 4.3.1 Services provided to upper layers..... | 40 | +| 4.3.2 Services expected from lower layers..... | 40 | +| 4.4 Functions..... | 40 | +| 5 Procedures..... | 41 | +| 5.1 General..... | 41 | +| 5.1.1 Introduction..... | 41 | +| 5.1.2 General requirements..... | 42 | +| 5.1.3 Requirements for UE in MR-DC..... | 42 | +| 5.2 System information..... | 43 | +| 5.2.1 Introduction..... | 43 | +| 5.2.2 System information acquisition..... | 44 | +| 5.2.2.1 General UE requirements..... | 44 | +| 5.2.2.2 SIB validity and need to (re)-acquire SIB..... | 44 | + +###### 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. + +| | | | +|------------|-----------------------------------------------------------------------------|----| +| 5.2.2.2.1 | SIB validity..... | 44 | +| 5.2.2.2.2 | SI change indication and PWS notification..... | 46 | +| 5.2.2.3 | Acquisition of System Information..... | 47 | +| 5.2.2.3.1 | Acquisition of MIB and SIB1 ..... | 47 | +| 5.2.2.3.2 | Acquisition of an SI message..... | 48 | +| 5.2.2.3.3 | Request for on demand system information..... | 50 | +| 5.2.2.3.3a | Request for on demand positioning system information..... | 51 | +| 5.2.2.3.4 | Actions related to transmission of RRCSystemInfoRequest message..... | 53 | +| 5.2.2.3.5 | Acquisition of SIB(s) or posSIB(s) in RRC_CONNECTED..... | 53 | +| 5.2.2.3.6 | Actions related to transmission of DedicatedSIBRequest message..... | 54 | +| 5.2.2.4 | Actions upon receipt of System Information..... | 55 | +| 5.2.2.4.1 | Actions upon reception of the MIB ..... | 55 | +| 5.2.2.4.2 | Actions upon reception of the SIB1 ..... | 55 | +| 5.2.2.4.3 | Actions upon reception of SIB2 ..... | 61 | +| 5.2.2.4.4 | Actions upon reception of SIB3 ..... | 62 | +| 5.2.2.4.5 | Actions upon reception of SIB4 ..... | 62 | +| 5.2.2.4.6 | Actions upon reception of SIB5 ..... | 63 | +| 5.2.2.4.7 | Actions upon reception of SIB6 ..... | 63 | +| 5.2.2.4.8 | Actions upon reception of SIB7 ..... | 63 | +| 5.2.2.4.9 | Actions upon reception of SIB8 ..... | 64 | +| 5.2.2.4.10 | Actions upon reception of SIB9 ..... | 65 | +| 5.2.2.4.11 | Actions upon reception of SIB10 ..... | 66 | +| 5.2.2.4.12 | Actions upon reception of SIB11 ..... | 66 | +| 5.2.2.4.13 | Actions upon reception of SIB12 ..... | 66 | +| 5.2.2.4.14 | Actions upon reception of SIB13 ..... | 67 | +| 5.2.2.4.15 | Actions upon reception of SIB14 ..... | 67 | +| 5.2.2.4.16 | Actions upon reception of SIBpos ..... | 67 | +| 5.2.2.4.17 | Actions upon reception of SIB15 ..... | 67 | +| 5.2.2.4.18 | Actions upon reception of SIB16 ..... | 67 | +| 5.2.2.4.19 | Actions upon reception of SIB17 ..... | 68 | +| 5.2.2.4.20 | Actions upon reception of SIB18 ..... | 68 | +| 5.2.2.4.21 | Actions upon reception of SIB19 ..... | 68 | +| 5.2.2.4.22 | Actions upon reception of SIB20 ..... | 68 | +| 5.2.2.4.23 | Actions upon reception of SIB21 ..... | 68 | +| 5.2.2.4.24 | Actions upon reception of SIB22 ..... | 68 | +| 5.2.2.4.26 | Actions upon reception of SIB24 ..... | 69 | +| 5.2.2.4.27 | Actions upon reception of SIB25 ..... | 69 | +| 5.2.2.5 | Essential system information missing..... | 69 | +| 5.2.2.6 | T430 expiry..... | 70 | +| 5.3 | Connection control..... | 70 | + +| | | | +|------------|-----------------------------------------------------------------------------------------------------------------|-----| +| 5.3.1 | Introduction..... | 70 | +| 5.3.1.1 | RRC connection control..... | 70 | +| 5.3.1.2 | AS Security..... | 71 | +| 5.3.2 | Paging..... | 72 | +| 5.3.2.1 | General..... | 72 | +| 5.3.2.2 | Initiation..... | 72 | +| 5.3.2.3 | Reception of the Paging message by the UE or PagingRecord by the L2 U2N Remote UE..... | 72 | +| 5.3.3 | RRC connection establishment..... | 75 | +| 5.3.3.1 | General..... | 75 | +| 5.3.3.1a | Conditions for establishing RRC Connection for NR sidelink communication/discovery/V2X sidelink communication | 75 | +| 5.3.3.1b | Conditions for establishing RRC Connection for NR sidelink Positioning..... | 76 | +| 5.3.3.2 | Initiation..... | 76 | +| 5.3.3.3 | Actions related to transmission of RRCSetupRequest message..... | 77 | +| 5.3.3.4 | Reception of the RRCSetup by the UE..... | 77 | +| 5.3.3.5 | Reception of the RRCReject by the UE..... | 82 | +| 5.3.3.6 | Cell re-selection or cell selection or relay (re)selection while T390, T300 or T302 is running (UE in RRC_IDLE) | 82 | +| 5.3.3.7 | T300 expiry..... | 83 | +| 5.3.3.8 | Abortion of RRC connection establishment..... | 85 | +| 5.3.4 | Initial AS security activation..... | 85 | +| 5.3.4.1 | General..... | 85 | +| 5.3.4.2 | Initiation..... | 85 | +| 5.3.4.3 | Reception of the SecurityModeCommand by the UE..... | 85 | +| 5.3.5 | RRC reconfiguration..... | 86 | +| 5.3.5.1 | General..... | 86 | +| 5.3.5.2 | Initiation..... | 88 | +| 5.3.5.3 | Reception of an RRCReconfiguration by the UE..... | 88 | +| 5.3.5.4 | Secondary cell group release..... | 103 | +| 5.3.5.5 | Cell Group configuration..... | 103 | +| 5.3.5.5.1 | General..... | 103 | +| 5.3.5.5.2 | Reconfiguration with sync..... | 105 | +| 5.3.5.5.3 | RLC bearer release..... | 107 | +| 5.3.5.5.4 | RLC bearer addition/modification..... | 107 | +| 5.3.5.5.5 | MAC entity configuration..... | 108 | +| 5.3.5.5.6 | RLF Timers & Constants configuration..... | 108 | +| 5.3.5.5.7 | SpCell Configuration..... | 109 | +| 5.3.5.5.8 | SCell Release..... | 110 | +| 5.3.5.5.9 | SCell Addition/Modification..... | 110 | +| 5.3.5.5.10 | BH RLC channel release..... | 111 | +| 5.3.5.5.11 | BH RLC channel addition/modification..... | 111 | +| 5.3.5.5.12 | Uu Relay RLC channel release..... | 112 | + +| | | | +|---------------|-------------------------------------------------------------------------------------------|-----| +| 5.3.5.5.13 | Uu Relay RLC channel addition/modification..... | 112 | +| 5.3.5.5.14 | NCR-Fwd configuration..... | 112 | +| 5.3.5.6 | Radio Bearer configuration..... | 112 | +| 5.3.5.6.1 | General..... | 112 | +| 5.3.5.6.2 | SRB release..... | 113 | +| 5.3.5.6.3 | SRB addition/modification..... | 113 | +| 5.3.5.6.4 | DRB release..... | 115 | +| 5.3.5.6.5 | DRB addition/modification..... | 115 | +| 5.3.5.6.6 | Multicast MRB release..... | 118 | +| 5.3.5.6.7 | Multicast MRB addition/modification..... | 119 | +| 5.3.5.7 | AS Security key update..... | 119 | +| 5.3.5.8 | Reconfiguration failure..... | 121 | +| 5.3.5.8.1 | Void..... | 121 | +| 5.3.5.8.2 | Inability to comply with RRCREconfiguration ..... | 121 | +| 5.3.5.8.3 | T304 expiry (Reconfiguration with sync Failure) or T420 expiry (Path switch failure)..... | 123 | +| 5.3.5.9 | Other configuration..... | 124 | +| 5.3.5.9a | MUSIM gap configuration..... | 129 | +| 5.3.5.10 | MR-DC release..... | 130 | +| 5.3.5.11 | Full configuration..... | 130 | +| 5.3.5.12 | BAP configuration..... | 132 | +| 5.3.5.12a | IAB Other Configuration..... | 133 | +| 5.3.5.12a.1 | IP address management..... | 133 | +| 5.3.5.12a.1.1 | IP Address Release..... | 133 | +| 5.3.5.12a.1.2 | IP Address Addition/Modification..... | 133 | +| 5.3.5.13 | Conditional Reconfiguration..... | 134 | +| 5.3.5.13.1 | General..... | 134 | +| 5.3.5.13.2 | Conditional reconfiguration removal..... | 135 | +| 5.3.5.13.3 | Conditional reconfiguration addition/modification..... | 136 | +| 5.3.5.13.4 | Conditional reconfiguration evaluation..... | 136 | +| 5.3.5.13.4a | Conditional reconfiguration evaluation of SN initiated inter-SN CPC for EN-DC..... | 139 | +| 5.3.5.13.5 | Conditional reconfiguration execution..... | 140 | +| 5.3.5.13.6 | Subsequent CPAC reference configuration addition/removal..... | 140 | +| 5.3.5.13.7 | sk-Counter configuration addition/modification/removal..... | 141 | +| 5.3.5.13.8 | Subsequent CPAC execution..... | 141 | +| 5.3.5.13a | SCG activation..... | 143 | +| 5.3.5.13b | SCG deactivation..... | 143 | +| 5.3.5.13b1 | SCG activation without SN message..... | 144 | +| 5.3.5.13c | FR2 UL gap configuration..... | 144 | +| 5.3.5.13d | Application layer measurement configuration..... | 144 | +| 5.3.5.14 | Sidelink dedicated configuration..... | 146 | + +| | | | +|----------------|----------------------------------------------------------------------------------|-----| +| 5.3.5.15 | L2 U2N or U2U Relay UE configuration..... | 148 | +| 5.3.5.15.1 | General..... | 148 | +| 5.3.5.15.2 | L2 U2N or U2U Remote UE Release..... | 149 | +| 5.3.5.15.3 | L2 U2N or U2U Remote UE Addition/Modification..... | 149 | +| 5.3.5.16 | L2 U2N or U2U Remote UE configuration..... | 150 | +| 5.3.5.16.1 | L2 U2U Relay UE Release..... | 151 | +| 5.3.5.16.2 | L2 U2U Relay UE Addition/Modification..... | 151 | +| 5.3.5.17 | MP configuration..... | 151 | +| 5.3.5.17.1 | Introduction..... | 151 | +| 5.3.5.17.2 | Configuration of SL indirect path..... | 152 | +| 5.3.5.17.2.1 | General..... | 152 | +| 5.3.5.17.2.2 | SL indirect path specific configuration..... | 152 | +| 5.3.5.17.2.3 | T421 expiry (Indirect path addition/change failure)..... | 152 | +| 5.3.5.17.3 | Configuration of N3C indirect path..... | 152 | +| 5.3.5.17.3.1 | General..... | 152 | +| 5.3.5.17.3.2 | N3C remote UE configuration..... | 153 | +| 5.3.5.17.3.3 | N3C relay UE configuration..... | 153 | +| 5.3.5.17.3.4 | Bearer mapping management on N3C indirect path..... | 153 | +| 5.3.5.17.3.4.1 | Bearer mapping release..... | 153 | +| 5.3.5.17.3.4.2 | Bearer mapping addition and modification..... | 153 | +| 5.3.5.18 | LTM configuration and execution..... | 154 | +| 5.3.5.18.1 | LTM configuration..... | 154 | +| 5.3.5.18.2 | LTM candidate configuration release..... | 155 | +| 5.3.5.18.3 | LTM candidate configuration addition/modification..... | 155 | +| 5.3.5.18.4 | LTM CSI resource configuration release..... | 157 | +| 5.3.5.18.5 | LTM CSI resource configuration addition/modification..... | 157 | +| 5.3.5.18.6 | LTM cell switch execution..... | 157 | +| 5.3.5.18.7 | LTM configuration release..... | 159 | +| 5.3.5.19 | T348 expiry..... | 159 | +| 5.3.6 | Counter check..... | 159 | +| 5.3.6.1 | General..... | 159 | +| 5.3.6.2 | Initiation..... | 160 | +| 5.3.6.3 | Reception of the CounterCheck message by the UE..... | 160 | +| 5.3.7 | RRC connection re-establishment..... | 160 | +| 5.3.7.1 | General..... | 160 | +| 5.3.7.2 | Initiation..... | 161 | +| 5.3.7.3 | Actions following cell selection while T311 is running..... | 165 | +| 5.3.7.3a | Actions following relay selection while T311 is running..... | 168 | +| 5.3.7.4 | Actions related to transmission of RRCReestablishmentRequest message..... | 168 | +| 5.3.7.5 | Reception of the RRCReestablishment by the UE..... | 169 | + +| | | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 5.3.7.6 | T311 expiry..... | 171 | +| 5.3.7.7 | T301 expiry or selected cell/L2 U2N Relay UE no longer suitable..... | 172 | +| 5.3.7.8 | Reception of the RRCSetup by the UE..... | 172 | +| 5.3.8 | RR connection release..... | 172 | +| 5.3.8.1 | General..... | 172 | +| 5.3.8.2 | Initiation..... | 172 | +| 5.3.8.3 | Reception of the RRCRelease by the UE..... | 172 | +| 5.3.8.4 | T320 expiry..... | 177 | +| 5.3.8.5 | UE actions upon the expiry of DataInactivityTimer ..... | 178 | +| 5.3.8.6 | T346g expiry..... | 178 | +| 5.3.9 | RR connection release requested by upper layers..... | 178 | +| 5.3.9.1 | General..... | 178 | +| 5.3.9.2 | Initiation..... | 178 | +| 5.3.10 | Radio link failure related actions..... | 178 | +| 5.3.10.1 | Detection of physical layer problems in RRC_CONNECTED..... | 178 | +| 5.3.10.2 | Recovery of physical layer problems..... | 178 | +| 5.3.10.3 | Detection of radio link failure..... | 179 | +| 5.3.10.4 | RLF cause determination..... | 181 | +| 5.3.10.5 | RLF report content determination..... | 181 | +| 5.3.11 | UE actions upon going to RRC_IDLE..... | 186 | +| 5.3.12 | UE actions upon PUCCH/SRS release request..... | 187 | +| 5.3.13 | RR connection resume..... | 188 | +| 5.3.13.1 | General..... | 188 | +| 5.3.13.1a | Conditions for resuming RRC Connection for NR sidelink communication/discovery/V2X sidelink communication | 189 | +| 5.3.13.1b | Conditions for initiating SDT..... | 190 | +| 5.3.13.1c | Conditions for resuming RRC Connection for NR sidelink Positioning..... | 190 | +| 5.3.13.1d | RR connection resume for multicast reception..... | 190 | +| 5.3.13.2 | Initiation..... | 190 | +| 5.3.13.3 | Actions related to transmission of RRResumeRequest or RRResumeRequest1 message..... | 194 | +| 5.3.13.4 | Reception of the RRResume by the UE..... | 196 | +| 5.3.13.5 | Handling of failure to resume RRC Connection..... | 202 | +| 5.3.13.6 | Cell re-selection or cell selection or L2 U2N relay (re)selection while T390, T319 or T302 is running or SDT procedure is ongoing (UE in RRC_INACTIVE) or SRS transmission in RRC_INACTIVE is configured..... | 204 | +| 5.3.13.7 | Reception of the RRCSetup by the UE..... | 205 | +| 5.3.13.8 | RNA update..... | 205 | +| 5.3.13.9 | Reception of the RRCRelease by the UE..... | 205 | +| 5.3.13.10 | Reception of the RRReject by the UE..... | 205 | +| 5.3.13.11 | Inability to comply with RRResume ..... | 205 | +| 5.3.13.12 | Inter RAT cell reselection..... | 206 | +| 5.3.14 | Unified Access Control..... | 206 | + +| | | | +|-----------|--------------------------------------------------------------|-----| +| 5.3.14.1 | General..... | 206 | +| 5.3.14.2 | Initiation..... | 206 | +| 5.3.14.3 | Void..... | 208 | +| 5.3.14.4 | T302, T390 expiry or stop (Barring alleviation)..... | 208 | +| 5.3.14.5 | Access barring check..... | 208 | +| 5.3.15 | RRC connection reject..... | 209 | +| 5.3.15.1 | Initiation..... | 209 | +| 5.3.15.2 | Reception of the RRCReject by the UE..... | 209 | +| 5.4 | Inter-RAT mobility..... | 210 | +| 5.4.1 | Introduction..... | 210 | +| 5.4.2 | Handover to NR..... | 210 | +| 5.4.2.1 | General..... | 210 | +| 5.4.2.2 | Initiation..... | 211 | +| 5.4.2.3 | Reception of the RRCReconfiguration by the UE..... | 211 | +| 5.4.3 | Mobility from NR..... | 211 | +| 5.4.3.1 | General..... | 211 | +| 5.4.3.2 | Initiation..... | 212 | +| 5.4.3.3 | Reception of the MobilityFromNRCommand by the UE..... | 212 | +| 5.4.3.4 | Successful completion of the mobility from NR..... | 213 | +| 5.4.3.5 | Mobility from NR failure..... | 213 | +| 5.5 | Measurements..... | 214 | +| 5.5.1 | Introduction..... | 214 | +| 5.5.2 | Measurement configuration..... | 217 | +| 5.5.2.1 | General..... | 217 | +| 5.5.2.2 | Measurement identity removal..... | 218 | +| 5.5.2.3 | Measurement identity addition/modification..... | 219 | +| 5.5.2.4 | Measurement object removal..... | 220 | +| 5.5.2.5 | Measurement object addition/modification..... | 220 | +| 5.5.2.6 | Reporting configuration removal..... | 222 | +| 5.5.2.7 | Reporting configuration addition/modification..... | 223 | +| 5.5.2.8 | Quantity configuration..... | 223 | +| 5.5.2.9 | Measurement gap configuration..... | 223 | +| 5.5.2.10 | Reference signal measurement timing configuration..... | 225 | +| 5.5.2.10a | RSSI measurement timing configuration..... | 226 | +| 5.5.2.11 | Measurement gap sharing configuration..... | 227 | +| 5.5.2.12 | Effective measurement window configuration..... | 227 | +| 5.5.3 | Performing measurements..... | 228 | +| 5.5.3.1 | General..... | 228 | +| 5.5.3.2 | Layer 3 filtering..... | 233 | +| 5.5.3.3 | Derivation of cell measurement results..... | 234 | + +| | | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 5.5.3.3a | Derivation of layer 3 beam filtered measurement..... | 235 | +| 5.5.3.4 | Derivation of L2 U2N Relay UE measurement results..... | 235 | +| 5.5.4 | Measurement report triggering..... | 235 | +| 5.5.4.1 | General..... | 235 | +| 5.5.4.2 | Event A1 (Serving becomes better than threshold)..... | 243 | +| 5.5.4.3 | Event A2 (Serving becomes worse than threshold)..... | 243 | +| 5.5.4.4 | Event A3 (Neighbour becomes offset better than SpCell)..... | 244 | +| 5.5.4.5 | Event A4 (Neighbour becomes better than threshold)..... | 245 | +| 5.5.4.6 | Event A5 (SpCell becomes worse than threshold1 and neighbour becomes better than threshold2)..... | 245 | +| 5.5.4.7 | Event A6 (Neighbour becomes offset better than SCell)..... | 246 | +| 5.5.4.8 | Event B1 (Inter RAT neighbour becomes better than threshold)..... | 247 | +| 5.5.4.9 | Event B2 (PCell becomes worse than threshold1 and inter RAT neighbour becomes better than threshold2) | 248 | +| 5.5.4.10 | Event I1 (Interference becomes higher than threshold)..... | 248 | +| 5.5.4.11 | Event C1 (The NR sidelink channel busy ratio is above a threshold)..... | 249 | +| 5.5.4.12 | Event C2 (The NR sidelink channel busy ratio is below a threshold)..... | 249 | +| 5.5.4.13 | Void..... | 250 | +| 5.5.4.14 | Void..... | 250 | +| 5.5.4.15 | Event D1 (Distance between UE and referenceLocation1 is above threshold1 and distance between UE and referenceLocation2 is below threshold2) | 250 | +| 5.5.4.15a | CondEvent D2 (Distance between UE and a moving referenceLocation1 is above threshold1 and distance between UE and a moving referenceLocation2 is below threshold2)..... | 251 | +| 5.5.4.16 | CondEvent T1 (Time measured at UE is within a duration from threshold)..... | 252 | +| 5.5.4.17 | Event X1 (Serving L2 U2N Relay UE becomes worse than threshold1 and NR Cell becomes better than threshold2) | 252 | +| 5.5.4.18 | Event X2 (Serving L2 U2N Relay UE becomes worse than threshold)..... | 253 | +| 5.5.4.19 | Event Y1 (PCell becomes worse than threshold1 and candidate L2 U2N Relay UE becomes better than threshold2) | 253 | +| 5.5.4.20 | Event Y2 (Candidate L2 U2N Relay UE becomes better than threshold)..... | 254 | +| 5.5.4.20b | Event Z1 (Serving L2 U2N Relay UE becomes worse than threshold1 and Candidate L2 U2N Relay UE becomes better than threshold2) | 255 | +| 5.5.4.21 | Event H1 (The Aerial UE altitude becomes higher than a threshold)..... | 255 | +| 5.5.4.22 | Event H2 (The Aerial UE altitude becomes lower than a threshold)..... | 256 | +| 5.5.4.23 | Event A3H1 (Neighbour becomes offset better than SpCell and the Aerial UE altitude becomes higher than a threshold) | 256 | +| 5.5.4.24 | Event A3H2 (Neighbour becomes offset better than SpCell and the Aerial UE altitude becomes lower than a threshold) | 257 | +| 5.5.4.25 | Event A4H1 (Neighbour becomes better than threshold1 and the Aerial UE altitude becomes higher than a threshold2) | 258 | +| 5.5.4.26 | Event A4H2 (Neighbour becomes better than threshold1 and the Aerial UE altitude becomes lower than a threshold2) | 259 | +| 5.5.4.27 | Event A5H1 (SpCell becomes worse than threshold1 and neighbour becomes better than threshold2 and the Aerial UE altitude becomes higher than a threshold3)..... | 260 | +| 5.5.4.28 | Event A5H2 (SpCell becomes worse than threshold1 and neighbour becomes better than threshold2 and the Aerial UE altitude becomes lower than a threshold3)..... | 261 | +| 5.5.5 | Measurement reporting..... | 262 | +| 5.5.5.1 | General..... | 262 | +| 5.5.5.2 | Reporting of beam measurement information..... | 271 | +| 5.5.5.3 | Sorting of cell measurement results..... | 271 | + +| | | | +|----------|--------------------------------------------------------------------------------------------------|-----| +| 5.5.6 | Location measurement indication..... | 272 | +| 5.5.6.1 | General..... | 272 | +| 5.5.6.2 | Initiation..... | 272 | +| 5.5.6.3 | Actions related to transmission of LocationMeasurementIndication message..... | 273 | +| 5.5a | Logged Measurements..... | 274 | +| 5.5a.1 | Logged Measurement Configuration..... | 274 | +| 5.5a.1.1 | General..... | 274 | +| 5.5a.1.2 | Initiation..... | 274 | +| 5.5a.1.3 | Reception of the LoggedMeasurementConfiguration by the UE..... | 274 | +| 5.5a.1.4 | T330 expiry..... | 275 | +| 5.5a.2 | Release of Logged Measurement Configuration..... | 275 | +| 5.5a.2.1 | General..... | 275 | +| 5.5a.2.2 | Initiation..... | 275 | +| 5.5a.3 | Measurements logging..... | 275 | +| 5.5a.3.1 | General..... | 275 | +| 5.5a.3.2 | Initiation..... | 275 | +| 5.5b | Application Layer Measurements in RRC_IDLE/RRC_INACTIVE..... | 279 | +| 5.5b.1 | Area handling and storing of Application Layer Measurement reports in RRC_IDLE/RRC_INACTIVE..... | 279 | +| 5.5b.1.1 | General..... | 279 | +| 5.5b.1.2 | Initiation..... | 279 | +| 5.6 | UE capabilities..... | 279 | +| 5.6.1 | UE capability transfer..... | 279 | +| 5.6.1.1 | General..... | 279 | +| 5.6.1.2 | Initiation..... | 280 | +| 5.6.1.3 | Reception of the UECapabilityEnquiry by the UE..... | 280 | +| 5.6.1.4 | Setting band combinations, feature set combinations and feature sets supported by the UE..... | 281 | +| 5.6.1.5 | Void..... | 284 | +| 5.7 | Other..... | 284 | +| 5.7.1 | DL information transfer..... | 284 | +| 5.7.1.1 | General..... | 284 | +| 5.7.1.2 | Initiation..... | 284 | +| 5.7.1.3 | Reception of the DLInformationTransfer by the UE..... | 284 | +| 5.7.1a | DL information transfer for MR-DC..... | 285 | +| 5.7.1a.1 | General..... | 285 | +| 5.7.1a.2 | Initiation..... | 285 | +| 5.7.1a.3 | Actions related to reception of DLInformationTransferMRDC message..... | 285 | +| 5.7.2 | UL information transfer..... | 286 | +| 5.7.2.1 | General..... | 286 | +| 5.7.2.2 | Initiation..... | 286 | +| 5.7.2.3 | Actions related to transmission of ULInformationTransfer message..... | 286 | + +| | | | +|----------|---------------------------------------------------------------------------------------|-----| +| 5.7.2.4 | Failure to deliver ULInformationTransfer message..... | 286 | +| 5.7.2a | UL information transfer for MR-DC..... | 287 | +| 5.7.2a.1 | General..... | 287 | +| 5.7.2a.2 | Initiation..... | 287 | +| 5.7.2a.3 | Actions related to transmission of ULInformationTransferMRDC message..... | 287 | +| 5.7.2b | UL transfer of IRAT information..... | 287 | +| 5.7.2b.1 | General..... | 287 | +| 5.7.2b.2 | Initiation..... | 288 | +| 5.7.2b.3 | Actions related to transmission of ULInformationTransferIRAT message..... | 288 | +| 5.7.3 | SCG failure information..... | 288 | +| 5.7.3.1 | General..... | 288 | +| 5.7.3.2 | Initiation..... | 288 | +| 5.7.3.3 | Failure type determination for (NG)EN-DC..... | 289 | +| 5.7.3.4 | Setting the contents of MeasResultSCG-Failure ..... | 290 | +| 5.7.3.5 | Actions related to transmission of SCGFailureInformation message..... | 290 | +| 5.7.3a | EUTRA SCG failure information..... | 293 | +| 5.7.3a.1 | General..... | 293 | +| 5.7.3a.2 | Initiation..... | 293 | +| 5.7.3a.3 | Actions related to transmission of SCGFailureInformationEUTRA message..... | 293 | +| 5.7.3b | MCG failure information..... | 294 | +| 5.7.3b.1 | General..... | 294 | +| 5.7.3b.2 | Initiation..... | 294 | +| 5.7.3b.3 | Failure type determination..... | 294 | +| 5.7.3b.4 | Actions related to transmission of MCGFailureInformation message..... | 295 | +| 5.7.3b.5 | T316 expiry..... | 296 | +| 5.7.3c | Indirect path failure information..... | 297 | +| 5.7.3c.1 | General..... | 297 | +| 5.7.3c.2 | Initiation..... | 297 | +| 5.7.3c.3 | Failure type determination..... | 297 | +| 5.7.3c.4 | Actions related to transmission of IndirectPathFailureInformation message..... | 298 | +| 5.7.4 | UE Assistance Information..... | 298 | +| 5.7.4.1 | General..... | 298 | +| 5.7.4.2 | Initiation..... | 299 | +| 5.7.4.3 | Actions related to transmission of UEAssistanceInformation message..... | 308 | +| 5.7.4.3a | Setting the contents of OverheatingAssistance IE..... | 319 | +| 5.7.4.4 | Relaxed measurement criterion for a stationary (e)RedCap UE..... | 320 | +| 5.7.4a | Void..... | 321 | +| 5.7.5 | Failure information..... | 321 | +| 5.7.5.1 | General..... | 321 | +| 5.7.5.2 | Initiation..... | 321 | + +| | | | +|----------|---------------------------------------------------------------------------------------|-----| +| 5.7.5.3 | Actions related to transmission of FailureInformation message..... | 321 | +| 5.7.6 | DL message segment transfer..... | 322 | +| 5.7.6.1 | General..... | 322 | +| 5.7.6.2 | Initiation..... | 322 | +| 5.7.6.3 | Reception of DL Dedicated Message Segment by the UE..... | 322 | +| 5.7.7 | UL message segment transfer..... | 322 | +| 5.7.7.1 | General..... | 322 | +| 5.7.7.2 | Initiation..... | 323 | +| 5.7.7.3 | Actions related to transmission of UL Dedicated Message Segment message..... | 323 | +| 5.7.8 | Idle/inactive Measurements..... | 323 | +| 5.7.8.1 | General..... | 323 | +| 5.7.8.1a | Measurement configuration..... | 323 | +| 5.7.8.2 | Void..... | 324 | +| 5.7.8.2a | Performing measurements..... | 324 | +| 5.7.8.3 | T331 expiry or stop..... | 327 | +| 5.7.8.4 | Cell re-selection or cell selection while T331 is running..... | 327 | +| 5.7.9 | Mobility history information..... | 328 | +| 5.7.9.1 | General..... | 328 | +| 5.7.9.2 | Initiation..... | 328 | +| 5.7.9.3 | Release of Mobility History Information..... | 331 | +| 5.7.10 | UE Information..... | 331 | +| 5.7.10.1 | General..... | 331 | +| 5.7.10.2 | Initiation..... | 331 | +| 5.7.10.3 | Reception of the UE Information Request message..... | 331 | +| 5.7.10.4 | Actions for the Random Access report determination..... | 335 | +| 5.7.10.5 | RA information determination..... | 337 | +| 5.7.10.6 | Actions for the successful handover report determination..... | 341 | +| 5.7.10.7 | Actions for the successful PSCell change or addition report determination..... | 345 | +| 5.7.11 | Void..... | 348 | +| 5.7.12 | IAB Other Information..... | 348 | +| 5.7.12.1 | General..... | 348 | +| 5.7.12.2 | Initiation..... | 348 | +| 5.7.12.3 | Actions related to transmission of IAB Other Information message..... | 348 | +| 5.7.13 | RLM/BFD relaxation..... | 350 | +| 5.7.13.1 | Relaxed measurement criterion for low mobility..... | 350 | +| 5.7.13.2 | Relaxed measurement criterion for good serving cell quality..... | 350 | +| 5.7.14 | UE Positioning Assistance Information..... | 350 | +| 5.7.14.1 | General..... | 350 | +| 5.7.14.2 | Initiation..... | 351 | +| 5.7.14.3 | Actions related to transmission of UE Positioning Assistance Info message..... | 351 | + +| | | | +|------------|-------------------------------------------------------------------------------------------------------------------------|-----| +| 5.7.15 | Void..... | 351 | +| 5.7.17 | Derivation of pathloss reference for TA validation of SRS for Positioning transmission and CG-SDT in RRC_INACTIVE ..... | 353 | +| 5.7.18 | Actions for SRS for Positioning transmission in RRC_INACTIVE in a Validity Area..... | 354 | +| 5.7.19 | Satellite switch with re-synchronization in RRC_CONNECTED..... | 354 | +| 5.8 | Sidelink..... | 354 | +| 5.8.1 | General..... | 354 | +| 5.8.2 | Conditions for NR sidelink communication/discovery/positioning operation..... | 355 | +| 5.8.3 | Sidelink UE information for NR sidelink communication/discovery/positioning..... | 356 | +| 5.8.3.1 | General..... | 356 | +| 5.8.3.2 | Initiation..... | 356 | +| 5.8.3.3 | Actions related to transmission of SidelinkUEInformationNR message..... | 363 | +| 5.8.4 | Void..... | 369 | +| 5.8.5 | Sidelink synchronisation information transmission for NR sidelink communication/discovery/positioning..... | 369 | +| 5.8.5.1 | General..... | 369 | +| 5.8.5.2 | Initiation..... | 369 | +| 5.8.5.3 | Transmission of SLSS..... | 370 | +| 5.8.5a | Sidelink synchronisation information transmission for V2X sidelink communication..... | 372 | +| 5.8.5a.1 | General..... | 372 | +| 5.8.5a.2 | Initiation..... | 372 | +| 5.8.6 | Sidelink synchronisation reference..... | 372 | +| 5.8.6.1 | General..... | 372 | +| 5.8.6.2 | Selection and reselection of synchronisation reference..... | 372 | +| 5.8.6.3 | Sidelink communication transmission reference cell selection..... | 378 | +| 5.8.7 | Sidelink communication reception..... | 378 | +| 5.8.8 | Sidelink communication transmission..... | 379 | +| 5.8.9 | Sidelink RRC procedure..... | 381 | +| 5.8.9.1 | Sidelink RRC reconfiguration..... | 381 | +| 5.8.9.1.1 | General..... | 381 | +| 5.8.9.1.2 | Actions related to transmission of RRReconfigurationSidelink message..... | 382 | +| 5.8.9.1.3 | Reception of an RRReconfigurationSidelink by the UE..... | 385 | +| 5.8.9.1.4 | Void..... | 388 | +| 5.8.9.1.5 | Void..... | 388 | +| 5.8.9.1.6 | Void..... | 388 | +| 5.8.9.1.7 | Void..... | 388 | +| 5.8.9.1.8 | Reception of an RRReconfigurationFailureSidelink by the UE..... | 388 | +| 5.8.9.1.9 | Reception of an RRReconfigurationCompleteSidelink by the UE..... | 388 | +| 5.8.9.1a | Sidelink radio bearer management..... | 389 | +| 5.8.9.1a.1 | Sidelink DRB release..... | 389 | +| 5.8.9.1a.2 | Sidelink DRB addition/modification..... | 390 | +| 5.8.9.1a.3 | Sidelink SRB release..... | 392 | + +| | | | +|--------------|------------------------------------------------------------------------------------------|-----| +| 5.8.9.1a.4 | Sidelink SRB addition..... | 392 | +| 5.8.9.1a.5 | Additional Sidelink RLC Bearer release..... | 392 | +| 5.8.9.1a.5.1 | Additional Sidelink RLC Bearer release conditions..... | 392 | +| 5.8.9.1a.5.2 | Additional Sidelink RLC Bearer release operation..... | 393 | +| 5.8.9.1a.6 | Additional Sidelink RLC Bearer addition/modification..... | 393 | +| 5.8.9.1a.6.1 | Additional Sidelink RLC Bearer addition/modification conditions..... | 393 | +| 5.8.9.1a.6.2 | Additional Sidelink RLC Bearer addition/modification operation..... | 394 | +| 5.8.9.1b | Sidelink Carrier Configuration..... | 395 | +| 5.8.9.1b.1 | Sidelink Carrier Release..... | 395 | +| 5.8.9.1b.2 | Sidelink Carrier Addition/Modification..... | 396 | +| 5.8.9.2 | Sidelink UE capability transfer..... | 396 | +| 5.8.9.2.1 | General..... | 396 | +| 5.8.9.2.2 | Initiation..... | 396 | +| 5.8.9.2.3 | Actions related to transmission of the UECapabilityEnquirySidelink by the UE..... | 396 | +| 5.8.9.2.4 | Actions related to reception of the UECapabilityEnquirySidelink by the UE..... | 397 | +| 5.8.9.3 | Sidelink radio link failure related actions..... | 397 | +| 5.8.9.4 | Sidelink common control information..... | 398 | +| 5.8.9.4.1 | General..... | 398 | +| 5.8.9.4.2 | Actions related to reception of MasterInformationBlockSidelink message..... | 398 | +| 5.8.9.4.3 | Transmission of MasterInformationBlockSidelink message..... | 398 | +| 5.8.9.5 | Actions related to PC5-RRC connection release requested by upper layers..... | 399 | +| 5.8.9.6 | Sidelink UE assistance information..... | 400 | +| 5.8.9.6.1 | General..... | 400 | +| 5.8.9.6.2 | Initiation..... | 400 | +| 5.8.9.6.3 | Actions related to reception of UEAssistanceInformationSidelink message..... | 400 | +| 5.8.9.7 | PC5 Relay RLC channel management for L2 U2N or U2U relay..... | 400 | +| 5.8.9.7.1 | PC5 Relay RLC channel release..... | 400 | +| 5.8.9.7.2 | PC5 Relay RLC channel addition/modification..... | 401 | +| 5.8.9.8 | Remote UE information..... | 402 | +| 5.8.9.8.1 | General..... | 402 | +| 5.8.9.8.2 | Actions related to transmission of RemoteUEInformationSidelink message..... | 402 | +| 5.8.9.8.3 | Reception of RemoteUEInformationSidelink message by the L2 U2N Relay UE..... | 403 | +| 5.8.9.9 | Uu message transfer in sidelink..... | 404 | +| 5.8.9.9.1 | General..... | 404 | +| 5.8.9.9.2 | Actions related to transmission of UuMessageTransferSidelink message..... | 404 | +| 5.8.9.9.3 | Reception of the UuMessageTransferSidelink ..... | 405 | +| 5.8.9.10 | Notification Message..... | 405 | +| 5.8.9.10.1 | General..... | 405 | +| 5.8.9.10.2 | Initiation..... | 405 | +| 5.8.9.10.3 | Actions related to transmission of NotificationMessageSidelink message..... | 406 | + +| | | | +|------------|-------------------------------------------------------------------------------------------|-----| +| 5.8.9.10.4 | Actions related to reception of NotificationMessageSidelink message..... | 406 | +| 5.8.9.11 | Sidelink UE information..... | 407 | +| 5.8.9.11.1 | General..... | 407 | +| 5.8.9.11.2 | Actions related to transmission of the UEInformationRequestSidelink by the UE..... | 407 | +| 5.8.9.11.3 | Actions related to reception of the UEInformationRequestSidelink by the UE..... | 408 | +| 5.8.10 | Sidelink measurement..... | 408 | +| 5.8.10.1 | Introduction..... | 408 | +| 5.8.10.2 | Sidelink measurement configuration..... | 409 | +| 5.8.10.2.1 | General..... | 409 | +| 5.8.10.2.2 | Sidelink measurement identity removal..... | 409 | +| 5.8.10.2.3 | Sidelink measurement identity addition/modification..... | 409 | +| 5.8.10.2.4 | Sidelink measurement object removal..... | 410 | +| 5.8.10.2.5 | Sidelink measurement object addition/modification..... | 410 | +| 5.8.10.2.6 | Sidelink reporting configuration removal..... | 410 | +| 5.8.10.2.7 | Sidelink reporting configuration addition/modification..... | 411 | +| 5.8.10.2.8 | Sidelink quantity configuration..... | 411 | +| 5.8.10.3 | Performing NR sidelink measurements..... | 411 | +| 5.8.10.3.1 | General..... | 411 | +| 5.8.10.3.2 | Derivation of NR sidelink measurement results..... | 412 | +| 5.8.10.4 | Sidelink measurement report triggering..... | 412 | +| 5.8.10.4.1 | General..... | 412 | +| 5.8.10.4.2 | Event S1 (Serving becomes better than threshold)..... | 413 | +| 5.8.10.4.3 | Event S2 (Serving becomes worse than threshold)..... | 413 | +| 5.8.10.5 | Sidelink measurement reporting..... | 414 | +| 5.8.10.5.1 | General..... | 414 | +| 5.8.11 | Zone identity calculation..... | 415 | +| 5.8.12 | DFN derivation from GNSS..... | 415 | +| 5.8.13 | NR sidelink discovery..... | 416 | +| 5.8.13.1 | General..... | 416 | +| 5.8.13.2 | NR sidelink discovery monitoring..... | 416 | +| 5.8.13.3 | NR sidelink discovery transmission..... | 416 | +| 5.8.14 | NR sidelink U2N Relay UE operation..... | 420 | +| 5.8.14.1 | General..... | 420 | +| 5.8.15 | NR sidelink U2N Remote UE operation..... | 420 | +| 5.8.15.1 | General..... | 420 | +| 5.8.15.2 | NR Sidelink U2N Remote UE threshold conditions..... | 420 | +| 5.8.15.3 | Selection and reselection of NR sidelink U2N Relay UE..... | 421 | +| 5.8.16 | NR sidelink U2U Relay UE operation..... | 422 | +| 5.8.16.1 | General..... | 422 | +| 5.8.16.2 | NR sidelink U2U Relay UE threshold conditions..... | 422 | + +| | | | +|----------|-------------------------------------------------------------------------------|-----| +| 5.8.16.3 | Neighbor UE(s) in proximity conditions..... | 422 | +| 5.8.17 | NR sidelink U2U Remote UE operation..... | 423 | +| 5.8.17.1 | General..... | 423 | +| 5.8.17.2 | NR Sidelink U2U Remote UE threshold conditions..... | 423 | +| 5.8.17.3 | Conditions for Selection and reselection of NR sidelink U2U Relay UE..... | 423 | +| 5.8.17.4 | Actions related to selection and reselection of NR sidelink U2U Relay UE..... | 424 | +| 5.8.18 | NR sidelink positioning..... | 425 | +| 5.8.18.1 | General..... | 425 | +| 5.8.18.2 | NR sidelink positioning reception..... | 425 | +| 5.8.18.3 | NR sidelink positioning transmission..... | 425 | +| 5.9 | MBS Broadcast..... | 427 | +| 5.9.1 | Introduction..... | 427 | +| 5.9.1.1 | General..... | 427 | +| 5.9.1.2 | MCCH scheduling..... | 427 | +| 5.9.1.3 | MCCH information validity and notification of changes..... | 428 | +| 5.9.2 | MCCH information acquisition..... | 428 | +| 5.9.2.1 | General..... | 428 | +| 5.9.2.2 | Initiation..... | 428 | +| 5.9.2.3 | MCCH information acquisition by the UE..... | 429 | +| 5.9.2.4 | Actions upon reception of the MBSBroadcastConfiguration message..... | 429 | +| 5.9.3 | Broadcast MRB configuration..... | 429 | +| 5.9.3.1 | General..... | 429 | +| 5.9.3.2 | Initiation..... | 429 | +| 5.9.3.3 | Broadcast MRB establishment..... | 429 | +| 5.9.3.4 | Broadcast MRB release..... | 430 | +| 5.9.4 | MBS Interest Indication..... | 430 | +| 5.9.4.1 | General..... | 430 | +| 5.9.4.2 | Initiation..... | 430 | +| 5.9.4.3 | MBS frequencies of interest determination..... | 431 | +| 5.9.4.4 | MBS services of interest determination..... | 432 | +| 5.9.4.5 | Setting of the contents of MBS Interest Indication..... | 432 | +| 5.10 | MBS multicast reception in RRC_INACTIVE..... | 433 | +| 5.10.1 | Introduction..... | 433 | +| 5.10.1.1 | General..... | 433 | +| 5.10.1.2 | Multicast MCCH scheduling..... | 433 | +| 5.10.1.3 | Multicast MCCH information validity and notification of changes..... | 433 | +| 5.10.2 | Multicast MCCH information acquisition..... | 434 | +| 5.10.2.1 | General..... | 434 | +| 5.10.2.2 | Initiation..... | 434 | +| 5.10.2.3 | Multicast MCCH information acquisition by the UE..... | 434 | + +| | | | +|----------|-----------------------------------------------------------------------------|-----| +| 5.10.2.4 | Actions upon reception of the MBSMulticastConfiguration message..... | 434 | +| 5.10.3 | MRB configuration..... | 434 | +| 5.10.3.1 | General..... | 434 | +| 5.10.3.2 | Multicast MRB establishment..... | 435 | +| 5.10.3.3 | Multicast MRB release..... | 435 | +| 6 | Protocol data units, formats and parameters (ASN.1)..... | 436 | +| 6.1 | General..... | 436 | +| 6.1.1 | Introduction..... | 436 | +| 6.1.2 | Need codes and conditions for optional fields..... | 436 | +| 6.1.3 | General rules..... | 439 | +| 6.2 | RRC messages..... | 439 | +| 6.2.1 | General message structure..... | 439 | +| – | NR-RRC-Definitions ..... | 439 | +| – | BCCH-BCH-Message ..... | 439 | +| – | BCCH-DL-SCH-Message ..... | 440 | +| – | DL-CCCH-Message ..... | 440 | +| – | DL-DCCH-Message ..... | 441 | +| – | MCCH-Message ..... | 441 | +| – | MulticastMCCH-Message ..... | 442 | +| – | PCCH-Message ..... | 442 | +| – | UL-CCCH-Message ..... | 443 | +| – | UL-CCCH1-Message ..... | 443 | +| – | UL-DCCH-Message ..... | 444 | +| 6.2.2 | Message definitions..... | 446 | +| – | CounterCheck ..... | 446 | +| – | CounterCheckResponse ..... | 447 | +| – | DedicatedSIBRequest ..... | 448 | +| – | DL Dedicated Message Segment ..... | 449 | +| – | DL Information Transfer ..... | 450 | +| – | DL Information Transfer MRDC ..... | 452 | +| – | Failure Information ..... | 453 | +| – | IAB Other Information ..... | 454 | +| – | Indirect Path Failure Information ..... | 457 | +| – | Location Measurement Indication ..... | 458 | +| – | Logged Measurement Configuration ..... | 459 | +| – | MBS Broadcast Configuration ..... | 461 | +| – | MBS Interest Indication ..... | 462 | +| – | MBS Multicast Configuration ..... | 463 | +| – | MCG Failure Information ..... | 465 | + +| | | | +|-------|------------------------------------------|-----| +| – | MeasurementReport ..... | 466 | +| – | MeasurementReportAppLayer ..... | 467 | +| – | MIB ..... | 469 | +| – | MobilityFromNRCommand ..... | 471 | +| – | Paging ..... | 472 | +| – | RRCREestablishment ..... | 474 | +| – | RRCREestablishmentComplete ..... | 475 | +| – | RRCREestablishmentRequest ..... | 476 | +| – | RRREconfiguration ..... | 477 | +| – | RRREconfigurationComplete ..... | 485 | +| – | RRReject ..... | 487 | +| – | RRRelease ..... | 488 | +| – | RRResume ..... | 500 | +| – | RRResumeComplete ..... | 504 | +| – | RRResumeRequest ..... | 506 | +| – | RRResumeRequest1 ..... | 507 | +| – | RRSetup ..... | 508 | +| – | RRSetupComplete ..... | 509 | +| – | RRSetupRequest ..... | 512 | +| – | RRSystemInfoRequest ..... | 513 | +| – | SCGFailureInformation ..... | 514 | +| – | SCGFailureInformationEUTRA ..... | 516 | +| – | SecurityModeCommand ..... | 517 | +| – | SecurityModeComplete ..... | 518 | +| – | SecurityModeFailure ..... | 519 | +| – | SIB1 ..... | 519 | +| – | SidelinkUEInformationNR ..... | 525 | +| – | SystemInformation ..... | 533 | +| – | UEAssistanceInformation ..... | 535 | +| – | UECapabilityEnquiry ..... | 550 | +| – | UECapabilityInformation ..... | 551 | +| – | UEInformationRequest ..... | 552 | +| – | UEInformationResponse ..... | 554 | +| – | UEPositioningAssistanceInfo ..... | 573 | +| – | ULDedicatedMessageSegment ..... | 575 | +| – | ULInformationTransfer ..... | 576 | +| – | ULInformationTransferIRAT ..... | 577 | +| – | ULInformationTransferMRDC ..... | 578 | +| 6.3 | RRC information elements..... | 579 | +| 6.3.0 | Parameterized types..... | 579 | + +| | | | +|--------|--------------------------------------------------|-----| +| – | SetupRelease ..... | 579 | +| 6.3.1 | System information blocks..... | 579 | +| – | SIB2 ..... | 579 | +| – | SIB3 ..... | 584 | +| – | SIB4 ..... | 586 | +| – | SIB5 ..... | 592 | +| – | SIB6 ..... | 596 | +| – | SIB7 ..... | 596 | +| – | SIB8 ..... | 597 | +| – | SIB9 ..... | 598 | +| – | SIB10 ..... | 599 | +| – | SIB11 ..... | 600 | +| – | SIB12 ..... | 601 | +| – | SIB13 ..... | 604 | +| – | SIB14 ..... | 605 | +| – | SIB15 ..... | 605 | +| – | SIB16 ..... | 606 | +| – | SIB17 ..... | 607 | +| – | SIB18 ..... | 609 | +| – | SIB19 ..... | 610 | +| – | SIB20 ..... | 612 | +| – | SIB21 ..... | 614 | +| – | SIB22 ..... | 615 | +| – | SIB23 ..... | 616 | +| – | SIB24 ..... | 616 | +| – | SIB25 ..... | 617 | +| 6.3.1a | Positioning System information blocks..... | 618 | +| – | PosSystemInformation-r16-IEs ..... | 618 | +| – | PosSI-SchedulingInfo ..... | 619 | +| – | SIBpos ..... | 622 | +| 6.3.2 | Radio resource control information elements..... | 622 | +| – | AdditionalSpectrumEmission ..... | 622 | +| – | AdvancedReceiver-MU-MIMO ..... | 623 | +| – | Alpha ..... | 624 | +| – | Altitude ..... | 624 | +| – | AMF-Identifier ..... | 625 | +| – | ARFCN-ValueEUTRA ..... | 625 | +| – | ARFCN-ValueNR ..... | 625 | +| – | ARFCN-ValueUTRA-FDD ..... | 626 | +| – | ATG-Config ..... | 626 | + +| | | | +|---|----------------------------------------------|-----| +| – | AvailabilityCombinationsPerCell ..... | 627 | +| – | AvailabilityIndicator ..... | 628 | +| – | BAP-RoutingID ..... | 629 | +| – | BeamFailureRecoveryConfig ..... | 630 | +| – | BeamFailureRecoveryRSConfig ..... | 633 | +| – | BetaOffsets ..... | 634 | +| – | BetaOffsetsCrossPri ..... | 635 | +| – | BH-LogicalChannelIdentity ..... | 635 | +| – | BH-LogicalChannelIdentity-Ext ..... | 636 | +| – | BH-RLC-ChannelConfig ..... | 636 | +| – | BH-RLC-ChannelID ..... | 637 | +| – | BSR-Config ..... | 637 | +| – | BWP ..... | 638 | +| – | BWP-Downlink ..... | 639 | +| – | BWP-DownlinkCommon ..... | 640 | +| – | BWP-DownlinkDedicated ..... | 640 | +| – | BWP-Id ..... | 643 | +| – | BWP-Uplink ..... | 644 | +| – | BWP-UplinkCommon ..... | 644 | +| – | BWP-UplinkDedicated ..... | 647 | +| – | CandidateBeamRS ..... | 651 | +| – | CandidateTCI-State ..... | 651 | +| – | CandidateTCI-UL-State ..... | 652 | +| – | CellAccessRelatedInfo ..... | 653 | +| – | CellAccessRelatedInfo-EUTRA-5GC ..... | 655 | +| – | CellAccessRelatedInfo-EUTRA-EPC ..... | 655 | +| – | CellDTXDRX-Config ..... | 656 | +| – | CellGroupConfig ..... | 657 | +| – | CellGroupId ..... | 671 | +| – | CellIdentity ..... | 671 | +| – | CellReselectionPriority ..... | 671 | +| – | CellReselectionSubPriority ..... | 672 | +| – | CFR-ConfigMulticast ..... | 672 | +| – | CGI-InfoEUTRA ..... | 673 | +| – | CGI-InfoEUTRALogging ..... | 673 | +| – | CGI-InfoNR ..... | 674 | +| – | CGI-Info-Logging ..... | 675 | +| – | CLI-RSSI-Range ..... | 676 | +| – | ClockQualityMetrics ..... | 676 | +| – | CodebookConfig ..... | 676 | + +| | | | +|---|---------------------------------------------------------|-----| +| – | CommonLocationInfo ..... | 683 | +| – | CondReconfigId ..... | 684 | +| – | CondReconfigToAddModList ..... | 684 | +| – | ConditionalReconfiguration ..... | 686 | +| – | ConfiguredGrantConfig ..... | 688 | +| – | ConfiguredGrantConfigIndex ..... | 700 | +| – | ConfiguredGrantConfigIndexMAC ..... | 701 | +| – | ConnEstFailureControl ..... | 701 | +| – | ControlResourceSet ..... | 702 | +| – | ControlResourceSetId ..... | 704 | +| – | ControlResourceSetZero ..... | 704 | +| – | CrossCarrierSchedulingConfig ..... | 705 | +| – | CSI-AperiodicTriggerStateList ..... | 706 | +| – | CSI-FrequencyOccupation ..... | 710 | +| – | CSI-IM-Resource ..... | 710 | +| – | CSI-IM-ResourceId ..... | 712 | +| – | CSI-IM-ResourceSet ..... | 712 | +| – | CSI-IM-ResourceSetId ..... | 712 | +| – | CSI-MeasConfig ..... | 713 | +| – | CSI-ReportConfig ..... | 715 | +| – | CSI-ReportConfigId ..... | 722 | +| – | CSI-ReportSubConfig ..... | 722 | +| – | CSI-ReportSubConfigId ..... | 723 | +| – | CSI-ReportSubConfigTriggerList ..... | 723 | +| – | CSI-ResourceConfig ..... | 724 | +| – | CSI-ResourceConfigId ..... | 725 | +| – | CSI-ResourcePeriodicityAndOffset ..... | 726 | +| – | CSI-RS-ResourceConfigMobility ..... | 726 | +| – | CSI-RS-ResourceMapping ..... | 729 | +| – | CSI-SemiPersistentOnPUSCH-TriggerStateList ..... | 730 | +| – | CSI-SSB-ResourceSet ..... | 731 | +| – | CSI-SSB-ResourceSetId ..... | 732 | +| – | DedicatedNAS-Message ..... | 732 | +| – | DL-PPW-PreConfig ..... | 733 | +| – | DMRS-BundlingPUCCH-Config ..... | 735 | +| – | DMRS-BundlingPUSCH-Config ..... | 736 | +| – | DMRS-DownlinkConfig ..... | 737 | +| – | DMRS-UplinkConfig ..... | 738 | +| – | DownlinkConfigCommon ..... | 741 | +| – | DownlinkConfigCommonSIB ..... | 741 | + +| | | | +|---|-----------------------------------------------|-----| +| – | DownlinkPreemption ..... | 746 | +| – | DRB-Identity ..... | 747 | +| – | DRX-Config ..... | 747 | +| – | DRX-ConfigSecondaryGroup ..... | 750 | +| – | DRX-ConfigSL ..... | 751 | +| – | EarlyUL-SyncConfig ..... | 752 | +| – | EphemerisInfo ..... | 753 | +| – | EUTRA-C-RNTI ..... | 754 | +| – | FeatureCombination ..... | 755 | +| – | FeatureCombinationPreambles ..... | 756 | +| – | FilterCoefficient ..... | 759 | +| – | FreqBandIndicatorNR ..... | 760 | +| – | FreqPriorityListDedicatedSlicing ..... | 760 | +| – | FreqPriorityListSlicing ..... | 761 | +| – | FrequencyInfoDL ..... | 762 | +| – | FrequencyInfoDL-SIB ..... | 763 | +| – | FrequencyInfoUL ..... | 764 | +| – | FrequencyInfoUL-SIB ..... | 765 | +| – | GapPriority ..... | 767 | +| – | HighSpeedConfig ..... | 767 | +| – | Hysteresis ..... | 769 | +| – | HysteresisAltitude ..... | 769 | +| – | HysteresisLocation ..... | 769 | +| – | InvalidSymbolPattern ..... | 770 | +| – | I-RNTI-Value ..... | 771 | +| – | LBT-FailureRecoveryConfig ..... | 771 | +| – | LocationInfo ..... | 772 | +| – | LocationMeasurementInfo ..... | 772 | +| – | LogicalChannelConfig ..... | 774 | +| – | LogicalChannelIdentity ..... | 776 | +| – | LTE-NeighCellsCRS-AssistInfoList ..... | 776 | +| – | LTM-CandidateId ..... | 778 | +| – | LTM-Candidate ..... | 778 | +| – | LTM-Config ..... | 781 | +| – | LTM-CSI-ReportConfig ..... | 782 | +| – | LTM-CSI-ReportConfigId ..... | 784 | +| – | LTM-CSI-ResourceConfig ..... | 784 | +| – | LTM-CSI-ResourceConfigId ..... | 785 | +| – | MAC-CellGroupConfig ..... | 785 | +| – | MeasConfig ..... | 790 | + +| | | | +|---|-------------------------------------------|-----| +| – | MeasGapConfig ..... | 791 | +| – | MeasGapId ..... | 795 | +| – | MeasGapSharingConfig ..... | 796 | +| – | MeasId ..... | 797 | +| – | MeasIdleConfig ..... | 797 | +| – | MeasIdToAddModList ..... | 800 | +| – | MeasObjectCLI ..... | 800 | +| – | MeasObjectEUTRA ..... | 803 | +| – | MeasObjectId ..... | 805 | +| – | MeasObjectNR ..... | 806 | +| – | MeasObjectNR-SL ..... | 815 | +| – | MeasObjectRxCvTxDiff ..... | 816 | +| – | MeasObjectToAddModList ..... | 816 | +| – | MeasObjectUTRA-FDD ..... | 817 | +| – | MeasResultCellListSFTD-NR ..... | 818 | +| – | MeasResultCellListSFTD-EUTRA ..... | 818 | +| – | MeasResults ..... | 819 | +| – | MeasResult2EUTRA ..... | 826 | +| – | MeasResult2NR ..... | 826 | +| – | MeasResultIdleEUTRA ..... | 827 | +| – | MeasResultIdleNR ..... | 828 | +| – | MeasResultRxCvTxTimeDiff ..... | 829 | +| – | MeasResultSCG-Failure ..... | 830 | +| – | MeasResultsSL ..... | 830 | +| – | MeasSequence ..... | 831 | +| – | MeasTriggerQuantityEUTRA ..... | 831 | +| – | MeasWindowConfig ..... | 832 | +| – | MobilityStateParameters ..... | 833 | +| – | MRB-Identity ..... | 833 | +| – | MsgA-ConfigCommon ..... | 834 | +| – | MsgA-PUSCH-Config ..... | 834 | +| – | MultiFrequencyBandListNR ..... | 838 | +| – | MultiFrequencyBandListNR-SIB ..... | 839 | +| – | MUSIM-GapConfig ..... | 840 | +| – | MUSIM-GapId ..... | 841 | +| – | MUSIM-GapInfo ..... | 841 | +| – | N3C-IndirectPathConfigRelay ..... | 843 | +| – | N3C-IndirectPathAddChange ..... | 843 | +| – | NCR-AperiodicFwdConfig ..... | 844 | +| – | NCR-FwdConfig ..... | 845 | + +| | | | +|---|-------------------------------------------------|-----| +| – | NCR-PeriodicityAndOffset ..... | 846 | +| – | NCR-PeriodicFwdResourceSet ..... | 847 | +| – | NCR-PeriodicFwdResourceSetId ..... | 849 | +| – | NCR-SemiPersistentFwdResourceSetId ..... | 851 | +| – | NeedForGapsConfigNR ..... | 851 | +| – | NeedForGapNCSG-ConfigEUTRA ..... | 853 | +| – | NeedForGapNCSG-ConfigNR ..... | 853 | +| – | NeedForGapNCSG-InfoEUTRA ..... | 854 | +| – | NeedForGapNCSG-InfoNR ..... | 855 | +| – | NeedForInterruptionInfoNR ..... | 856 | +| – | NextHopChainingCount ..... | 857 | +| – | NG-5G-S-TMSI ..... | 857 | +| – | NonCellDefiningSSB ..... | 858 | +| – | NPN-Identity ..... | 858 | +| – | NPN-IdentityInfoList ..... | 859 | +| – | NR-DL-PRS-PDC-Info ..... | 860 | +| – | NR-NS-PmaxList ..... | 864 | +| – | NSAG-ID ..... | 865 | +| – | NSAG-IdentityInfo ..... | 865 | +| – | NTN-Config ..... | 866 | +| – | NZP-CSI-RS-Resource ..... | 868 | +| – | NZP-CSI-RS-ResourceId ..... | 869 | +| – | NZP-CSI-RS-ResourceSet ..... | 870 | +| – | NZP-CSI-RS-ResourceSetId ..... | 872 | +| – | P-Max ..... | 872 | +| – | PathlossReferenceRS ..... | 872 | +| – | PathlossReferenceRS-Id ..... | 873 | +| – | PCI-ARFCN-EUTRA ..... | 873 | +| – | PCI-ARFCN-NR ..... | 874 | +| – | PCI-List ..... | 874 | +| – | PCI-Range ..... | 875 | +| – | PCI-RangeElement ..... | 875 | +| – | PCI-RangeIndex ..... | 876 | +| – | PCI-RangeIndexList ..... | 876 | +| – | PDCCH-Config ..... | 876 | +| – | PDCCH-ConfigCommon ..... | 879 | +| – | PDCCH-ConfigSIB1 ..... | 883 | +| – | PDCCH-ServingCellConfig ..... | 883 | +| – | PDCP-Config ..... | 884 | +| – | PDSCH-Config ..... | 891 | + +| | | | +|---|-----------------------------------------------------|-----| +| – | PDSCH-ConfigCommon ..... | 898 | +| – | PDSCH-ServingCellConfig ..... | 899 | +| – | PDSCH-TimeDomainResourceAllocationList ..... | 901 | +| – | PDU-SessionID ..... | 902 | +| – | PHR-Config ..... | 903 | +| – | PhysCellId ..... | 904 | +| – | PhysicalCellGroupConfig ..... | 905 | +| – | PLMN-Identity ..... | 914 | +| – | PLMN-IdentityInfoList ..... | 914 | +| – | PLMN-IdentityList2 ..... | 916 | +| – | PRB-Id ..... | 916 | +| – | PTRS-DownlinkConfig ..... | 916 | +| – | PTRS-UplinkConfig ..... | 917 | +| – | PUCCH-Config ..... | 918 | +| – | PUCCH-ConfigCommon ..... | 927 | +| – | PUCCH-ConfigurationList ..... | 928 | +| – | PUCCH-CSI-Resource ..... | 929 | +| – | PUCCH-PathlossReferenceRS-Id ..... | 929 | +| – | PUCCH-PowerControl ..... | 930 | +| – | PUCCH-SpatialRelationInfo ..... | 932 | +| – | PUCCH-SpatialRelationInfo-Id ..... | 933 | +| – | PUCCH-TPC-CommandConfig ..... | 933 | +| – | PUSCH-Config ..... | 934 | +| – | PUSCH-ConfigCommon ..... | 944 | +| – | PUSCH-PowerControl ..... | 945 | +| – | PUSCH-ServingCellConfig ..... | 949 | +| – | PUSCH-TimeDomainResourceAllocationList ..... | 951 | +| – | PUSCH-TPC-CommandConfig ..... | 954 | +| – | Q-OffsetRange ..... | 955 | +| – | Q-QualMin ..... | 955 | +| – | Q-RxLevMin ..... | 956 | +| – | QuantityConfig ..... | 956 | +| – | RACH-ConfigCommon ..... | 958 | +| – | RACH-ConfigCommonTwoStepRA ..... | 961 | +| – | RACH-ConfigDedicated ..... | 965 | +| – | RACH-ConfigGeneric ..... | 969 | +| – | RACH-ConfigGenericTwoStepRA ..... | 970 | +| – | RACH-ConfigTwoTA ..... | 973 | +| – | RA-Prioritization ..... | 974 | +| – | RA-PrioritizationForSlicing ..... | 975 | + +| | | | +|---|----------------------------------------------|------| +| – | RadioBearerConfig ..... | 975 | +| – | RadioLinkMonitoringConfig ..... | 979 | +| – | RadioLinkMonitoringRS-Id ..... | 981 | +| – | RAN-AreaCode ..... | 982 | +| – | RateMatchPattern ..... | 982 | +| – | RateMatchPatternId ..... | 984 | +| – | RateMatchPatternLTE-CRS ..... | 985 | +| – | ReferenceConfiguration ..... | 986 | +| – | ReferenceLocation ..... | 986 | +| – | ReferenceTimeInfo ..... | 986 | +| – | RejectWaitTime ..... | 988 | +| – | RepetitionSchemeConfig ..... | 988 | +| – | ReportConfigId ..... | 989 | +| – | ReportConfigInterRAT ..... | 989 | +| – | ReportConfigNR ..... | 995 | +| – | ReportConfigNR-SL ..... | 1009 | +| – | ReportConfigToAddModList ..... | 1011 | +| – | ReportInterval ..... | 1012 | +| – | ReselectionThreshold ..... | 1012 | +| – | ReselectionThresholdQ ..... | 1012 | +| – | ResumeCause ..... | 1013 | +| – | RLC-BearerConfig ..... | 1013 | +| – | RLC-Config ..... | 1015 | +| – | RLF-TimersAndConstants ..... | 1018 | +| – | RNTI-Value ..... | 1019 | +| – | RSRP-Range ..... | 1019 | +| – | RSRQ-Range ..... | 1019 | +| – | RSSI-Range ..... | 1020 | +| – | RxTxTimeDiff ..... | 1020 | +| – | SCellActivationRS-Config ..... | 1021 | +| – | SCellActivationRS-ConfigId ..... | 1021 | +| – | SCellIndex ..... | 1022 | +| – | SchedulingRequestConfig ..... | 1022 | +| – | SchedulingRequestId ..... | 1023 | +| – | SchedulingRequestResourceConfig ..... | 1024 | +| – | SchedulingRequestResourceId ..... | 1025 | +| – | ScramblingId ..... | 1025 | +| – | SCS-SpecificCarrier ..... | 1026 | +| – | SDAP-Config ..... | 1027 | +| – | SearchSpace ..... | 1028 | + +| | | | +|---|-----------------------------------------------|------| +| – | SearchSpaceId ..... | 1036 | +| – | SearchSpaceZero ..... | 1036 | +| – | SecurityAlgorithmConfig ..... | 1037 | +| – | SelectedPSCellForCHO-WithSCG ..... | 1038 | +| – | SemiStaticChannelAccessConfig ..... | 1038 | +| – | SemiStaticChannelAccessConfigUE ..... | 1038 | +| – | Sensor-LocationInfo ..... | 1039 | +| – | ServingCellAndBWP-Id ..... | 1040 | +| – | ServCellIndex ..... | 1040 | +| – | ServingCellConfig ..... | 1040 | +| – | ServingCellConfigCommon ..... | 1057 | +| – | ServingCellConfigCommonSIB ..... | 1060 | +| – | ShortI-RNTI-Value ..... | 1063 | +| – | ShortMAC-I ..... | 1063 | +| – | SINR-Range ..... | 1063 | +| – | SI-RequestConfig ..... | 1064 | +| – | SI-RequestConfigRepetition ..... | 1065 | +| – | SI-SchedulingInfo ..... | 1066 | +| – | SK-Counter ..... | 1070 | +| – | SlotFormatCombinationsPerCell ..... | 1070 | +| – | SlotFormatIndicator ..... | 1072 | +| – | S-NSSAI ..... | 1074 | +| – | SpeedStateScaleFactors ..... | 1075 | +| – | SPS-Config ..... | 1075 | +| – | SPS-ConfigIndex ..... | 1078 | +| – | SPS-PUCCH-AN ..... | 1078 | +| – | SPS-PUCCH-AN-List ..... | 1079 | +| – | SRB-Identity ..... | 1079 | +| – | SRS-CarrierSwitching ..... | 1079 | +| – | SRS-Config ..... | 1081 | +| – | SRS-PosTx-Hopping ..... | 1097 | +| – | SRS-PosResourceSetLinkedForAggBW ..... | 1097 | +| – | SRS-RSRP-Range ..... | 1098 | +| – | SRS-TPC-CommandConfig ..... | 1098 | +| – | SSB-Index ..... | 1099 | +| – | SSB-MTC ..... | 1099 | +| – | SSB-PositionQCL-Relation ..... | 1102 | +| – | SSB-ToMeasure ..... | 1102 | +| – | SS-RSSI-Measurement ..... | 1103 | +| – | SubcarrierSpacing ..... | 1104 | + +| | | | +|-------|---------------------------------------------------|------| +| – | TAG-Config ..... | 1104 | +| – | TAR-Config ..... | 1105 | +| – | TCI-ActivatedConfig ..... | 1106 | +| – | TCI-State ..... | 1106 | +| – | TCI-StateId ..... | 1108 | +| – | TCI-UL-State ..... | 1109 | +| – | TCI-UL-StateId ..... | 1110 | +| – | TDD-UL-DL-ConfigCommon ..... | 1111 | +| – | TDD-UL-DL-ConfigDedicated ..... | 1112 | +| – | TrackingAreaCode ..... | 1114 | +| – | T-Reselection ..... | 1114 | +| – | TimeAlignmentTimer ..... | 1115 | +| – | TimeToTrigger ..... | 1115 | +| – | TN-AreaId ..... | 1115 | +| – | UAC-BarringInfoSetIndex ..... | 1116 | +| – | UAC-BarringInfoSetList ..... | 1116 | +| – | UAC-BarringPerCatList ..... | 1117 | +| – | UAC-BarringPerPLMN-List ..... | 1118 | +| – | UAV-Config ..... | 1118 | +| – | UE-TimersAndConstants ..... | 1119 | +| – | UE-TimersAndConstantsRemoteUE ..... | 1119 | +| – | UL-DelayValueConfig ..... | 1120 | +| – | UL-ExcessDelayConfig ..... | 1120 | +| – | UL-GapFR2-Config ..... | 1121 | +| – | UplinkCancellation ..... | 1122 | +| – | UplinkConfigCommon ..... | 1124 | +| – | UplinkConfigCommonSIB ..... | 1125 | +| – | Uplink-PowerControl ..... | 1125 | +| – | Uu-RelayRLC-ChannelConfig ..... | 1126 | +| – | Uu-RelayRLC-ChannelID ..... | 1127 | +| – | UplinkTxDirectCurrentList ..... | 1127 | +| – | UplinkTxDirectCurrentMoreCarrierList ..... | 1128 | +| – | UplinkTxDirectCurrentTwoCarrierList ..... | 1130 | +| – | ZP-CSI-RS-Resource ..... | 1132 | +| – | ZP-CSI-RS-ResourceSet ..... | 1133 | +| – | ZP-CSI-RS-ResourceSetId ..... | 1133 | +| 6.3.3 | UE capability information elements..... | 1134 | +| – | AccessStratumRelease ..... | 1134 | +| – | AerialParameters ..... | 1134 | +| – | AppLayerMeasParameters ..... | 1135 | + +| | | | +|---|--------------------------------------------------|------| +| – | BandCombinationList ..... | 1136 | +| – | BandCombinationListSidelinkEUTRA-NR ..... | 1146 | +| – | BandCombinationListSL-Discovery ..... | 1148 | +| – | CA-BandwidthClassEUTRA ..... | 1148 | +| – | CA-BandwidthClassNR ..... | 1149 | +| – | CA-ParametersEUTRA ..... | 1149 | +| – | CA-ParametersNR ..... | 1150 | +| – | CA-ParametersNRDC ..... | 1160 | +| – | CarrierAggregationVariant ..... | 1162 | +| – | CodebookParameters ..... | 1163 | +| – | ERedCapParameters ..... | 1172 | +| – | FeatureSetCombination ..... | 1172 | +| – | FeatureSetCombinationId ..... | 1173 | +| – | FeatureSetDownlink ..... | 1174 | +| – | FeatureSetDownlinkId ..... | 1180 | +| – | FeatureSetDownlinkPerCC ..... | 1180 | +| – | FeatureSetDownlinkPerCC-Id ..... | 1182 | +| – | FeatureSetEUTRA-DownlinkId ..... | 1182 | +| – | FeatureSetEUTRA-UplinkId ..... | 1183 | +| – | FeatureSets ..... | 1183 | +| – | FeatureSetUplink ..... | 1185 | +| – | FeatureSetUplinkId ..... | 1191 | +| – | FeatureSetUplinkPerCC ..... | 1191 | +| – | FeatureSetUplinkPerCC-Id ..... | 1193 | +| – | FreqBandIndicatorEUTRA ..... | 1193 | +| – | FreqBandList ..... | 1194 | +| – | FreqSeparationClass ..... | 1195 | +| – | FreqSeparationClassDL-Only ..... | 1195 | +| – | FR2-2-AccessParamsPerBand ..... | 1195 | +| – | HighSpeedParameters ..... | 1197 | +| – | IMS-Parameters ..... | 1197 | +| – | InterRAT-Parameters ..... | 1198 | +| – | MAC-Parameters ..... | 1199 | +| – | MeasAndMobParameters ..... | 1202 | +| – | MeasAndMobParametersMRDC ..... | 1206 | +| – | MIMO-Layers ..... | 1208 | +| – | MIMO-ParametersPerBand ..... | 1208 | +| – | ModulationOrder ..... | 1220 | +| – | MRDC-Parameters ..... | 1220 | +| – | NCR-Parameters ..... | 1222 | + +| | | | +|-------|------------------------------------------------------------|------| +| – | NRDC-Parameters ..... | 1222 | +| – | NTN-Parameters ..... | 1223 | +| – | OLPC-SRS-Pos ..... | 1224 | +| – | PDCP-Parameters ..... | 1225 | +| – | PDCP-ParametersMRDC ..... | 1226 | +| – | Phy-Parameters ..... | 1226 | +| – | Phy-ParametersMRDC ..... | 1235 | +| – | Phy-ParametersSharedSpectrumChAccess ..... | 1235 | +| – | PosSRS-RRC-Inactive-OutsideInitialUL-BWP ..... | 1237 | +| – | PowSav-Parameters ..... | 1237 | +| – | ProcessingParameters ..... | 1238 | +| – | PRS-ProcessingCapabilityOutsideMGinPPWperType ..... | 1239 | +| – | RAT-Type ..... | 1240 | +| – | RedCapParameters ..... | 1240 | +| – | RF-Parameters ..... | 1240 | +| – | RF-ParametersMRDC ..... | 1253 | +| – | RLC-Parameters ..... | 1256 | +| – | SDAP-Parameters ..... | 1256 | +| – | SharedSpectrumChAccessParamsPerBand ..... | 1257 | +| – | SidelinkParameters ..... | 1260 | +| – | SimultaneousRxTxPerBandPair ..... | 1264 | +| – | SON-Parameters ..... | 1265 | +| – | SpatialRelationsSRS-Pos ..... | 1265 | +| – | SRS-AllPosResourcesRRC-Inactive ..... | 1266 | +| – | SRS-SwitchingTimeNR ..... | 1266 | +| – | SRS-SwitchingTimeEUTRA ..... | 1267 | +| – | SupportedBandwidth ..... | 1267 | +| – | UE-BasedPerfMeas-Parameters ..... | 1268 | +| – | UE-CapabilityRAT-ContainerList ..... | 1268 | +| – | UE-CapabilityRAT-RequestList ..... | 1269 | +| – | UE-CapabilityRequestFilterCommon ..... | 1270 | +| – | UE-CapabilityRequestFilterNR ..... | 1273 | +| – | UE-MRDC-Capability ..... | 1273 | +| – | UE-NR-Capability ..... | 1275 | +| – | UE-RadioPagingInfo ..... | 1280 | +| 6.3.4 | Other information elements..... | 1281 | +| – | AbsoluteTimeInfo ..... | 1281 | +| – | AppLayerIdleInactiveConfig ..... | 1281 | +| – | AppLayerMeasConfig ..... | 1282 | +| – | AreaConfiguration ..... | 1285 | + +| | | | +|-------|------------------------------------------------------|------| +| – | BT-NameList ..... | 1287 | +| – | DedicatedInfoFIc ..... | 1287 | +| – | EUTRA-AllowedMeasBandwidth ..... | 1288 | +| – | EUTRA-MBSFN-SubframeConfigList ..... | 1288 | +| – | EUTRA-MultiBandInfoList ..... | 1289 | +| – | EUTRA-MultiBandInfoListAerial ..... | 1289 | +| – | EUTRA-NS-PmaxList ..... | 1290 | +| – | EUTRA-PhysCellId ..... | 1290 | +| – | EUTRA-PhysCellIdRange ..... | 1291 | +| – | EUTRA-PresenceAntennaPort1 ..... | 1291 | +| – | EUTRA-Q-OffsetRange ..... | 1291 | +| – | IAB-IP-Address ..... | 1292 | +| – | IAB-IP-AddressIndex ..... | 1292 | +| – | IAB-IP-Usage ..... | 1293 | +| – | LoggingDuration ..... | 1293 | +| – | LoggingInterval ..... | 1293 | +| – | LogMeasResultListBT ..... | 1294 | +| – | LogMeasResultListWLAN ..... | 1294 | +| – | MeasConfigAppLayerId ..... | 1296 | +| – | OtherConfig ..... | 1296 | +| – | PhysCellIdUTRA-FDD ..... | 1305 | +| – | RRC-TransactionIdentifier ..... | 1306 | +| – | Sensor-NameList ..... | 1306 | +| – | TraceReference ..... | 1307 | +| – | UE-MeasurementsAvailable ..... | 1307 | +| – | UTRA-FDD-Q-OffsetRange ..... | 1308 | +| – | VisitedCellInfoList ..... | 1308 | +| – | WLAN-NameList ..... | 1309 | +| 6.3.5 | Sidelink information elements..... | 1310 | +| – | SL-BWP-Config ..... | 1310 | +| – | SL-BWP-ConfigCommon ..... | 1313 | +| – | SL-BWP-DiscPoolConfig ..... | 1316 | +| – | SL-BWP-DiscPoolConfigCommon ..... | 1316 | +| – | SL-BWP-PoolConfig ..... | 1317 | +| – | SL-BWP-PoolConfigCommon ..... | 1318 | +| – | SL-BWP-PRS-PoolConfig ..... | 1319 | +| – | SL-BWP-PRS-PoolConfigCommon ..... | 1320 | +| – | SL-CBR-PriorityTxConfigList ..... | 1320 | +| – | SL-CBR-CommonTxConfigList ..... | 1321 | +| – | SL-CBR-CommonTxDedicated-SL-PRS-RP-List ..... | 1322 | + +| | | | +|---|----------------------------------------------------------|------| +| – | SL-ConfigDedicatedNR ..... | 1323 | +| – | SL-ConfiguredGrantConfig ..... | 1327 | +| – | SL-ConfiguredGrantConfigDedicated-SL-PRS-RP ..... | 1330 | +| – | SL-DestinationIdentity ..... | 1331 | +| – | SL-DRX-Config ..... | 1331 | +| – | SL-DRX-ConfigGC-BC ..... | 1332 | +| – | SL-DRX-ConfigUC ..... | 1333 | +| – | SL-DRX-ConfigUC-SemiStatic ..... | 1335 | +| – | SL-FreqConfig ..... | 1336 | +| – | SL-FreqConfigCommon ..... | 1339 | +| – | SL-FreqSelectionConfig ..... | 1341 | +| – | SL-IndirectPathAddChange ..... | 1341 | +| – | SL-InterUE-CoordinationConfig ..... | 1342 | +| – | SL-LBT-FailureRecoveryConfig ..... | 1346 | +| – | SL-LogicalChannelConfig ..... | 1346 | +| – | SL-L2RelayUE-Config ..... | 1349 | +| – | SL-L2RemoteUE-Config ..... | 1350 | +| – | SL-MeasConfigCommon ..... | 1351 | +| – | SL-MeasConfigInfo ..... | 1352 | +| – | SL-MeasIdList ..... | 1353 | +| – | SL-MeasObjectList ..... | 1353 | +| – | SL-PagingIdentityRemoteUE ..... | 1354 | +| – | SL-PBPS-CPS-Config ..... | 1355 | +| – | SL-PDCP-Config ..... | 1357 | +| – | SL-PRS-ResourcePool ..... | 1357 | +| – | SL-PSSCH-TxConfigList ..... | 1362 | +| – | SL-QoS-FlowIdentity ..... | 1363 | +| – | SL-QoS-Profile ..... | 1363 | +| – | SL-QuantityConfig ..... | 1365 | +| – | SL-RadioBearerConfig ..... | 1365 | +| – | SL-RBSetConfig ..... | 1366 | +| – | SL-RelayUE-ConfigU2U ..... | 1368 | +| – | SL-RemoteUE-Config ..... | 1368 | +| – | SL-RemoteUE-ConfigU2U ..... | 1369 | +| – | SL-ReportConfigList ..... | 1370 | +| – | SL-ResourcePool ..... | 1372 | +| – | SL-RLC-BearerConfig ..... | 1385 | +| – | SL-RLC-BearerConfigIndex ..... | 1385 | +| – | SL-RLC-ChannelConfig ..... | 1386 | +| – | SL-RLC-ChannelID ..... | 1387 | + +| | | | +|-------|---------------------------------------------------|------| +| – | SL-RLC-Config ..... | 1387 | +| – | SL-ScheduledConfig ..... | 1388 | +| – | SL-SDAP-Config ..... | 1390 | +| – | SL-ServingCellInfo ..... | 1391 | +| – | SL-SourceIdentity ..... | 1391 | +| – | SL-SRAP-Config ..... | 1391 | +| – | SL-SRAP-ConfigU2U ..... | 1393 | +| – | SL-SyncConfig ..... | 1393 | +| – | SL-Thres-RSRP-List ..... | 1395 | +| – | SL-TxPower ..... | 1396 | +| – | SL-TypeTxSync ..... | 1396 | +| – | SL-UE-SelectedConfig ..... | 1397 | +| – | SL-ZoneConfig ..... | 1397 | +| – | SLRB-Uu-ConfigIndex ..... | 1398 | +| 6.3.6 | MBS information elements..... | 1398 | +| – | CarrierFreqListMBS ..... | 1398 | +| – | CFR-ConfigMCCH-MTCH ..... | 1399 | +| – | DRX-ConfigPTM ..... | 1400 | +| – | MBS-NeighbourCellList ..... | 1401 | +| – | MBS-NonServingInfoList ..... | 1402 | +| – | MBS-ServiceList ..... | 1403 | +| – | MBS-SessionInfoList ..... | 1404 | +| – | MBS-SessionInfoListMulticast ..... | 1407 | +| – | MTCH-SSB-MappingWindowList ..... | 1410 | +| – | PDSCH-ConfigBroadcast ..... | 1410 | +| – | TMGI ..... | 1412 | +| 6.4 | RRC multiplicity and type constraint values..... | 1413 | +| – | Multiplicity and type constraint definitions..... | 1413 | +| – | End of NR-RRC-Definitions..... | 1422 | +| 6.5 | Short Message..... | 1422 | +| 6.6 | PC5 RRC messages..... | 1423 | +| 6.6.1 | General message structure..... | 1423 | +| – | PC5-RRC-Definitions ..... | 1423 | +| – | SBCCH-SL-BCH-Message ..... | 1424 | +| – | SCCH-Message ..... | 1425 | +| – | MasterInformationBlockSidelink ..... | 1425 | +| – | MeasurementReportSidelink ..... | 1426 | +| – | NotificationMessageSidelink ..... | 1428 | +| – | RemoteUEInformationSidelink ..... | 1429 | +| – | RRCReconfigurationSidelink ..... | 1431 | + +| | | | +|-------|-------------------------------------------------|------| +| – | RRConfigurationCompleteSidelink ..... | 1436 | +| – | RRConfigurationFailureSidelink ..... | 1437 | +| – | UEAssistanceInformationSidelink ..... | 1438 | +| – | UECapabilityEnquirySidelink ..... | 1439 | +| – | UECapabilityInformationSidelink ..... | 1439 | +| – | UEInformationRequestSidelink ..... | 1442 | +| – | UEInformationResponseSidelink ..... | 1443 | +| – | UuMessageTransferSidelink ..... | 1444 | +| – | End of PC5-RR-Definitions ..... | 1445 | +| 7 | Variables and constants..... | 1446 | +| 7.1 | Timers..... | 1446 | +| 7.1.1 | Timers (Informative)..... | 1446 | +| 7.1.2 | Timer handling..... | 1456 | +| 7.2 | Counters..... | 1457 | +| 7.3 | Constants..... | 1457 | +| 7.4 | UE variables..... | 1457 | +| – | NR-UE-Variables ..... | 1457 | +| – | VarAppLayerIdleConfig ..... | 1459 | +| – | VarAppLayerPLMN-LisConfig ..... | 1460 | +| – | VarConditionalReconfig ..... | 1460 | +| – | VarConnEstFailReport ..... | 1461 | +| – | VarConnEstFailReportList ..... | 1461 | +| – | VarEventID ..... | 1462 | +| – | VarGnbID ..... | 1462 | +| – | VarLogMeasConfig ..... | 1462 | +| – | VarLogMeasReport ..... | 1463 | +| – | VarLTM-Config ..... | 1463 | +| – | VarLTM-ServingCellNoResetID ..... | 1464 | +| – | VarLTM-ServingCellUE-MeasuredTA-ID ..... | 1464 | +| – | VarMeasConfig ..... | 1465 | +| – | VarMeasConfigSL ..... | 1465 | +| – | VarMeasIdleConfig ..... | 1466 | +| – | VarMeasIdleReport ..... | 1466 | +| – | VarMeasReportList ..... | 1466 | +| – | VarMeasReportListSL ..... | 1467 | +| – | VarMobilityHistoryReport ..... | 1468 | +| – | VarPendingRNA-Update ..... | 1468 | +| – | VarRA-Report ..... | 1469 | +| – | VarResumeMAC-Input ..... | 1469 | + +| | | | +|---------|-------------------------------------------------|------| +| – | VarRLF-Report ..... | 1470 | +| – | VarServingSecurityCellSetID ..... | 1470 | +| – | VarShortMAC-Input ..... | 1471 | +| – | VarSuccessHO-Report ..... | 1471 | +| – | VarSuccessPSCell-Report ..... | 1472 | +| – | End of NR-UE-Variables ..... | 1472 | +| 8 | Protocol data unit abstract syntax..... | 1473 | +| 8.1 | General..... | 1473 | +| 8.2 | Structure of encoded RRC messages..... | 1473 | +| 8.3 | Basic production..... | 1473 | +| 8.4 | Extension..... | 1473 | +| 8.5 | Padding..... | 1474 | +| 9 | Specified and default radio configurations..... | 1474 | +| 9.1 | Specified configurations..... | 1474 | +| 9.1.1 | Logical channel configurations..... | 1474 | +| 9.1.1.1 | BCCH configuration..... | 1474 | +| 9.1.1.2 | CCCH configuration..... | 1475 | +| 9.1.1.3 | PCCH configuration..... | 1475 | +| 9.1.1.4 | SCCH configuration..... | 1475 | +| 9.1.1.5 | STCH configuration..... | 1482 | +| 9.1.1.6 | MCCH configuration..... | 1482 | +| 9.1.1.7 | MTCH configuration for MBS broadcast..... | 1483 | +| 9.1.2 | Void..... | 1483 | +| 9.2 | Default radio configurations..... | 1483 | +| 9.2.1 | Default SRB configurations..... | 1483 | +| 9.2.2 | Default MAC Cell Group configuration..... | 1483 | +| 9.2.3 | Default values timers and constants..... | 1484 | +| 9.2.4 | Default PC5 Relay RLC Channel..... | 1484 | +| 9.2.5 | Default SRAP configurations..... | 1484 | +| 9.3 | Sidelink pre-configured parameters..... | 1485 | +| – | NR-Sidelink-Preconf ..... | 1485 | +| – | SL-PosPreconfigurationNR ..... | 1485 | +| – | SL-PreconfigurationNR ..... | 1486 | +| – | End of NR-Sidelink-Preconf ..... | 1488 | +| – | SL-AccessInfo-L2U2N ..... | 1489 | +| 9.5 | Radio Information Related to TX Profile..... | 1490 | +| – | SL-TxProfile ..... | 1490 | + +| | | | +|-------------------------------|-------------------------------------------------------------------|-------------| +| 10 | Generic error handling..... | 1490 | +| 10.1 | General..... | 1490 | +| 10.2 | ASN.1 violation or encoding error..... | 1490 | +| 10.3 | Field set to a not comprehended value..... | 1490 | +| 10.4 | Mandatory field missing..... | 1491 | +| 10.5 | Not comprehended field..... | 1492 | +| 11 | Radio information related interactions between network nodes..... | 1493 | +| 11.1 | General..... | 1493 | +| 11.2 | Inter-node RRC messages..... | 1493 | +| 11.2.1 | General..... | 1493 | +| 11.2.2 | Message definitions..... | 1495 | +| – | CG-CandidateList ..... | 1495 | +| – | HandoverCommand ..... | 1496 | +| – | HandoverPreparationInformation ..... | 1497 | +| – | CG-Config ..... | 1502 | +| – | CG-ConfigInfo ..... | 1511 | +| – | MeasurementTimingConfiguration ..... | 1523 | +| – | UERadioPagingInformation ..... | 1525 | +| – | UERadioAccessCapabilityInformation ..... | 1527 | +| 11.2.3 | Mandatory information in inter-node RRC messages..... | 1528 | +| 11.3 | Inter-node RRC information element definitions..... | 1529 | +| – | ResourceConfigNRDC ..... | 1529 | +| 11.4 | Inter-node RRC multiplicity and type constraint values..... | 1531 | +| – | Multiplicity and type constraints definitions..... | 1531 | +| – | End of NR-InterNodeDefinitions ..... | 1531 | +| 12 | Processing delay requirements for RRC procedures..... | 1533 | +| Annex A (informative): | Guidelines, mainly on use of ASN.1..... | 1537 | +| A.1 | Introduction..... | 1537 | +| A.2 | Procedural specification..... | 1538 | +| A.2.1 | General principles..... | 1538 | +| A.2.2 | More detailed aspects..... | 1538 | +| A.3 | PDU specification..... | 1538 | +| A.3.1 | General principles..... | 1538 | +| A.3.1.1 | ASN.1 clauses..... | 1538 | +| A.3.1.2 | ASN.1 identifier naming conventions..... | 1539 | + +| | | | +|---------|---------------------------------------------------------------------------------------|------| +| A.3.1.3 | Text references using ASN.1 identifiers..... | 1541 | +| A.3.2 | High-level message structure..... | 1542 | +| A.3.3 | Message definition..... | 1543 | +| A.3.4 | Information elements..... | 1545 | +| A.3.5 | Fields with optional presence..... | 1546 | +| A.3.6 | Fields with conditional presence..... | 1547 | +| A.3.7 | Guidelines on use of lists with elements of SEQUENCE type..... | 1548 | +| A.3.8 | Guidelines on use of parameterised SetupRelease type..... | 1548 | +| A.3.9 | Guidelines on use of ToAddModList and ToReleaseList..... | 1550 | +| A.3.10 | Guidelines on use of lists (without ToAddModList and ToReleaseList)..... | 1551 | +| A.4 | Extension of the PDU specifications..... | 1552 | +| A.4.1 | General principles to ensure compatibility..... | 1552 | +| A.4.2 | Critical extension of messages and fields..... | 1552 | +| A.4.3 | Non-critical extension of messages..... | 1555 | +| A.4.3.1 | General principles..... | 1555 | +| A.4.3.2 | Further guidelines..... | 1556 | +| A.4.3.3 | Typical example of evolution of IE with local extensions..... | 1557 | +| A.4.3.4 | Typical examples of non critical extension at the end of a message..... | 1558 | +| A.4.3.5 | Examples of non-critical extensions not placed at the default extension location..... | 1559 | +| – | ParentIE-WithEM ..... | 1559 | +| – | ChildIE1-WithoutEM ..... | 1559 | +| – | ChildIE2-WithoutEM ..... | 1560 | + +| | | | +|-------------------------------|---------------------------------------------------------------------------------|-------------| +| A.5 | Guidelines regarding inclusion of transaction identifiers in RRC messages..... | 1564 | +| A.6 | Guidelines regarding use of need codes..... | 1565 | +| A.7 | Guidelines regarding use of conditions..... | 1565 | +| A.8 | Miscellaneous..... | 1566 | +| Annex B (informative): | RRC Information..... | 1567 | +| B.1 | Protection of RRC messages..... | 1567 | +| B.2 | Description of BWP configuration options..... | 1569 | +| Annex C (normative): | List of CRs Containing Early Implementable Features and Corrections..... | 1571 | +| Annex D (normative): | UE requirements on ASN.1 comprehension..... | 1575 | +| Annex E (informative): | Change history..... | 1577 | + +--- + +## Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +x the first digit: + +- 1 presented to TSG for information; +- 2 presented to TSG for approval; +- 3 or greater indicates TSG approved document under change control. + +y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. + +z the third digit is incremented when editorial only changes have been incorporated in the document. + +## 1 Scope + +The present document specifies the Radio Resource Control protocol for the radio interface between UE and NG-RAN. + +The scope of the present document also includes: + +- the radio related information transported in a transparent container between source gNB and target gNB upon inter gNB handover; +- the radio related information transported in a transparent container between a source or target gNB and another system upon inter RAT handover. +- the radio related information transported in a transparent container between a source eNB and target gNB during E-UTRA-NR Dual Connectivity. + +The RRC protocol is also used to configure the radio interface between an IAB-node and its parent node [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.300: "NR; Overall description; Stage 2". +- [3] 3GPP TS 38.321: "NR; Medium Access Control (MAC); 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) protocol specification". +- [6] ITU-T Recommendation X.680 (08/2015) "Information Technology – Abstract Syntax Notation One (ASN.1): Specification of basic notation" (Same as the ISO/IEC International Standard 8824-1). + +- [7] ITU-T Recommendation X.681 (08/2015) "Information Technology – Abstract Syntax Notation One (ASN.1): Information object specification" (Same as the ISO/IEC International Standard 8824-2). +- [8] ITU-T Recommendation X.691 (08/2015) "Information technology – ASN.1 encoding rules: Specification of Packed Encoding Rules (PER)" (Same as the ISO/IEC International Standard 8825-2). +- [9] 3GPP TS 38.215: "NR; Physical layer measurements". +- [10] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource Control (RRC); Protocol Specification". +- [11] 3GPP TS 33.501: "Security Architecture and Procedures for 5G System". +- [12] 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception". +- [13] 3GPP TS 38.213: "NR; Physical layer procedures for control". +- [14] 3GPP TS 38.133: "NR; Requirements for support of radio resource management". +- [15] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone". +- [16] 3GPP TS 38.211: "NR; Physical channels and modulation". +- [17] 3GPP TS 38.212: "NR; Multiplexing and channel coding". +- [18] ITU-T Recommendation X.683 (08/2015) "Information Technology – Abstract Syntax Notation One (ASN.1): Parameterization of ASN.1 specifications" (Same as the ISO/IEC International Standard 8824-4). +- [19] 3GPP TS 38.214: "NR; Physical layer procedures for data". +- [20] 3GPP TS 38.304: "NR; User Equipment (UE) procedures in Idle mode and RRC Inactive state". +- [21] 3GPP TS 23.003: "Numbering, addressing and identification". +- [22] 3GPP TS 36.101: "E-UTRA; User Equipment (UE) radio transmission and reception". +- [23] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3". +- [24] 3GPP TS 37.324: "Service Data Adaptation Protocol (SDAP) specification". +- [25] 3GPP TS 22.261: "Service requirements for the 5G System". +- [26] 3GPP TS 38.306: "User Equipment (UE) radio access capabilities". +- [27] 3GPP TS 36.304: "E-UTRA; User Equipment (UE) procedures in idle mode". + +- [28] ATIS 0700041: "WEA 3.0: Device-Based Geo-Fencing". +- [29] 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)". +- [30] 3GPP TS 33.401: "3GPP System Architecture Evolution (SAE); Security architecture". +- [31] 3GPP TS 36.211: "E-UTRA; Physical channels and modulation". +- [32] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2". +- [33] 3GPP TS 36.104: "E-UTRA; Base Station (BS) radio transmission and reception". +- [34] 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". +- [35] 3GPP TS 38.423: "NG-RAN, Xn application protocol (XnAP)". +- [36] 3GPP TS 38.473: "NG-RAN; F1 application protocol (F1AP)". +- [37] 3GPP TS 36.423: "E-UTRA; X2 application protocol (X2AP)". +- [38] 3GPP TS 24.008: "Mobile radio interface layer 3 specification; Core network protocols; Stage 3". +- [39] 3GPP TS 38.101-2 "NR; User Equipment (UE) radio transmission and reception; Part 2: Range 2 Standalone". +- [40] 3GPP TS 36.133: "E-UTRA; Requirements for support of radio resource management". +- [41] 3GPP TS 37.340: "E-UTRA and NR; Multi-connectivity; Stage 2". +- [42] 3GPP TS 38.413: "NG-RAN, NG Application Protocol (NGAP)". +- [43] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2". +- [44] 3GPP TR 36.816: "Evolved Universal Terrestrial Radio Access (E-UTRA); Study on signalling and procedure for interference avoidance for in-device coexistence ". +- [45] 3GPP TS 25.331: "Universal Terrestrial Radio Access (UTRA); Radio Resource Control (RRC); Protocol specification". +- [46] 3GPP TS 25.133: "Requirements for Support of Radio Resource Management (FDD)". +- [47] 3GPP TS 38.340: "Backhaul Adaptation Protocol (BAP) specification" +- [48] 3GPP TS 37.213: "Physical layer procedures for shared spectrum channel access". +- [49] 3GPP TS 37.355: "LTE Positioning Protocol (LPP)". + +- [50] IEEE 802.11-2012, Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications, IEEE Std. +- [51] Bluetooth Special Interest Group: "Bluetooth Core Specification v5.0", December 2016. +- [52] 3GPP TS 32.422: "Telecommunication management; Subscriber and equipment trace; Trace control and configuration management". +- [53] 3GPP TS 38.314: "NR; layer 2 measurements". +- [54] Void. +- [55] 3GPP TS 23.287: "Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services". +- [56] 3GPP TS 23.285: "Technical Specification Group Services and System Aspects; Architecture enhancements for V2X services". +- [57] 3GPP TS 24.587: " Technical Specification Group Core Network and Terminals; Vehicle-to-Everything (V2X) services in 5G System (5GS)". +- [58] Military Standard WGS84 Metric MIL-STD-2401 (11 January 1994): "Military Standard Department of Defence World Geodetic System (WGS)". +- [59] 3GPP TS 38.101-4 "NR; User Equipment (UE) radio transmission and reception; Part 4: Performance Requirements". +- [60] 3GPP TS 33.536: "Technical Specification Group Services and System Aspects; Security aspects of 3GPP support for advanced Vehicle-to-Everything (V2X) services". +- [61] 3GPP TS 37.320: "Radio measurement collection for Minimization of Drive Tests (MDT); Overall description; Stage 2". +- [62] 3GPP TS 36.306: "User Equipment (UE) radio access capabilities". +- [63] 3GPP TS 38.174: "NR; Integrated Access and Backhaul (IAB) radio transmission and reception". +- [64] 3GPP TS 38.472: "NG-RAN; F1 signalling transport". +- [65] 3GPP TS 23.304: "Proximity based Services (ProSe) in the 5G System (5GS)". +- [66] 3GPP TS 38.351: "NR; Sidelink Relay Adaptation Protocol (SRAP) Specification". +- [67] 3GPP TS 23.247: "Architectural enhancements for 5G multicast-broadcast services; Stage 2" +- [68] 3GPP TS 26.247: "Transparent end-to-end Packet-switched Streaming Service (PSS); Progressive Download and Dynamic Adaptive Streaming over HTTP (3GP-DASH)". +- [69] 3GPP TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction". +- [70] 3GPP TS 26.118: "Virtual Reality (VR) profiles for streaming applications". + +- [71] NIMA TR 8350.2, Third Edition, Amendment 1, 3 January 2000: "DEPARTMENT OF DEFENSE WORLD GEODETIC SYSTEM 1984". +- [72] 3GPP TS 24.554: "Technical Specification Group Core Network and Terminals; Proximity-services (ProSe) in 5G System (5GS) protocol". +- [73] 3GPP TS 38.305: "NG Radio Access Network (NG-RAN); Stage 2 functional specification of User Equipment (UE) positioning in NG-RAN". +- [74] 3GPP TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode". +- [75] 3GPP TS 38.101-5: "User Equipment (UE) radio transmission and reception; Part 5: Satellite access Radio Frequency (RF) and performance requirements". +- [76] 3GPP TS 23.256: "Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2". +- [77] 3GPP TS 38.355: "NR; Sidelink Positioning Protocol (SLPP); Protocol Specification". + +--- + +## 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]. + +**A2X communication:** A communication to support A2X services leveraging PC5 reference points, as defined in TS 23.256 [76]. A2X services are realized by various types of A2X applications, e.g., BRID or DAA. + +**Aerial UE:** UE performing Aerial UE communication, as defined in TS 38.300 [2], clause 16.18 and TS 23.256 [76]. + +**AM MRB:** An MRB associated with at least an AM RLC bearer for PTP transmission. + +**BH RLC channel:** An RLC channel between two nodes, which is used to transport backhaul packets. + +**Broadcast MRB:** A radio bearer configured for MBS broadcast delivery. + +**CEIL:** Mathematical function used to 'round up' i.e. to the nearest integer having a higher or equal value. + +**DAPS bearer:** a bearer whose radio protocols are located in both the source gNB and the target gNB during DAPS handover to use both source gNB and target gNB resources. + +**Data Burst:** A set of multiple PDUs generated and sent by the application in a short period of time, as defined in TS 23.501 [32]. + +**Dedicated signalling:** Signalling sent on DCCH logical channel between the network and a single UE. + +**Dormant BWP:** The dormant BWP is one of downlink BWPs configured by the network via dedicated RRC signalling. In the dormant BWP, the UE stops monitoring PDCCH on/for the SCell, but continues performing CSI measurements, Automatic Gain Control (AGC) and beam management, if configured. For each serving cell other than the SpCell or PUCCH SCell, the network may configure one BWP as a dormant BWP. + +**eRedCap UE:** A UE with enhanced reduced capabilities as specified in clause 4.2.22.1 in TS 38.306 [26]. + +**Field:** The individual contents of an information element are referred to as fields. + +**FLOOR:** Mathematical function used to 'round down' i.e. to the nearest integer having a lower or equal value. + +**Frequency Selection Area ID:** An identity used for broadcast MBS session to guide the frequency selection of the UE as defined in TS 23.247 [67]. + +**Global cell identity:** An identity to uniquely identifying an NR cell. It is consisted of *cellIdentity* and *plmn-Identity* of the first *PLMN-Identity* in *plmn-IdentityList* in SIB1. + +**Information element:** A structural element containing single or multiple fields is referred as information element. + +**Candidate configuration:** A configuration part of an *RRCREconfiguration* message associated with a candidate cell, e.g., for LTM or subsequent CPAC. A candidate configuration can be a complete candidate configuration or a delta configuration relatively to a reference configuration. + +**Reference configuration:** A configuration provided by the network to the UE that is common, within the same cell group, to a group of configured non-complete candidate configurations. + +**MBS Radio Bearer:** A radio bearer that is configured for MBS delivery. + +**Mobile IAB-MT:** mobile IAB-node function that terminates the Uu interface to the parent node using the procedures and behaviours specified for UEs unless stated otherwise. + +**Mobile IAB-node:** RAN node that supports NR access links to UEs and an NR backhaul link to a parent node, and that can conduct physical mobility across the RAN area. The mobile IAB-node function used in 38-series of 3GPP Specifications corresponds to the MBSR function defined in TS 23.501 [32]. + +**Multicast/Broadcast Service:** A point-to-multipoint service as defined in TS 23.247 [67]. + +**Multicast MRB:** A radio bearer configured for MBS multicast delivery. + +**MUSIM gap:** Period that the UE may use to perform MUSIM operations. + +**Multi-path:** Mode of operation of a UE in RRC\_CONNECTED configured with one direct path on which the UE connects to gNB using NR Uu, and one indirect path on which the UE connects to the same gNB via another UE using PC5 unicast link or Non-3GPP Connection. + +**MP remote UE:** A UE configured with Multi-path. When the connectivity of indirect path is PC5 unicast link, the MP remote UE is acting as a L2 U2N Remote UE. When the connectivity of indirect path is Non-3GPP Connection, the MP remote UE is acting as a N3C remote UE. + +**MP relay UE:** A UE that provides connectivity of indirect path to a MP remote UE. When the connectivity is PC5 unicast link, the MP relay UE is acting as a L2 U2N Relay UE. When the connectivity is Non-3GPP Connection, the MP relay UE is acting as a N3C relay UE. + +**NCSG:** Network controlled small gap as defined in TS 38.133 [14]. + +**NPN-only Cell:** A cell that is only available for normal service for NPNs' subscriber. An NPN-capable UE determines that a cell is NPN-only Cell by detecting that the *cellReservedForOtherUse* IE is set to true while the *npn-IdentityInfoList* IE is present in *CellAccessRelatedInfo*. + +**N3C indirect path:** In Multi-path, the indirect path using Non-3GPP Connection between remote UE and relay UE. + +**NR sidelink communication:** AS functionality enabling at least V2X Communication as defined in TS 23.287 [55], and ProSe Communication (including ProSe UE-to-Network Relay, non-Relay communication and ProSe UE-to-UE Relay Communication) as defined in TS 23.304 [65] between two or more nearby UEs, using NR technology but not traversing any network node. + +**NR sidelink discovery:** AS functionality enabling ProSe non-Relay Discovery, ProSe UE-to-Network Relay discovery and ProSe UE-to-UE Relay discovery for Proximity based Services as defined in TS 23.304 [65] between two or more nearby UEs, using NR technology but not traversing any network node. + +**NR sidelink positioning:** AS functionality enabling absolute positioning of a target UE or ranging via PC5 interface using SL-PRS transmission and reception as defined in TS 38.305 [73] and TS 38.355 [77]. + +**PNI-NPN identity:** an identifier of a PNI-NPN comprising of a PLMN ID and a CAG-ID combination. + +**Primary Cell:** The MCG cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure. + +**PC5 Relay RLC channel:** An RLC channel between L2 U2N Remote UE and L2 U2N Relay UE, or between L2 U2U Remote UE and L2 U2U Relay UE, which is used to transport packets over PC5 for L2 UE-to-Network relay or L2 UE-to-UE relay. + +**Primary SCG Cell:** For dual connectivity operation, the SCG cell in which the UE performs random access when performing the Reconfiguration with Sync procedure. + +**Primary Timing Advance Group:** Timing Advance Group containing the SpCell. + +**PUCCH SCell:** An SCell configured with PUCCH by *PUCCH-Config*. + +**PUSCH-Less SCell:** An SCell configured without PUSCH. + +**RedCap UE:** A UE with reduced capabilities as specified in clause 4.2.21.1 in TS 38.306 [26]. + +**RLC bearer configuration:** The lower layer part of the radio bearer configuration comprising the RLC and logical channel configurations. + +**Secondary Cell:** For a UE configured with CA, a cell providing additional radio resources on top of Special Cell. + +**Secondary Cell Group:** For a UE configured with dual connectivity, the subset of serving cells comprising of the PSCell and zero or more secondary cells. + +**Serving Cell:** For a UE in RRC\_CONNECTED not configured with CA/DC there is only one serving cell comprising of the primary cell. For a UE in RRC\_CONNECTED configured with CA/ DC the term 'serving cells' is used to denote the set of cells comprising of the Special Cell(s) and all secondary cells. + +**Small Data Transmission:** A procedure used for transmission of data and/or signalling over allowed radio bearers in RRC\_INACTIVE state (i.e. without the UE transitioning to RRC\_CONNECTED state). + +**SNPN identity:** an identifier of an SNPN comprising of a PLMN ID and an NID combination. + +**SL indirect path:** In Multi-path, the indirect path using PC5 unicast link between remote UE and relay UE. + +**Special Cell:** For Dual Connectivity operation the term Special Cell refers to the PCell of the MCG or the PSCell of the SCG, otherwise the term Special Cell refers to the PCell. + +**Split DRB:** In MR-DC or MP, a DRB that supports transmission via MCG and SCG/indirect path in MP, as well as duplication of PDCP PDUs as defined in TS 37.340 [41]. + +**Split SRB:** In MR-DC or MP, an SRB that supports transmission via MCG and SCG/indirect path in MP as well as duplication of RRC PDUs as defined in TS 37.340 [41]. + +**SSB Frequency:** Frequency referring to the position of resource element RE=#0 (subcarrier #0) of resource block RB#10 of the SS block. + +**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 U2U Remote UEs. + +**U2U Remote UE:** A UE that communicates with another UE via a U2U Relay UE. + +**Uu Relay RLC channel:** An RLC channel between L2 U2N Relay UE and gNB, which is used to transport packets over Uu for L2 UE-to-Network relay or for indirect path in case of MP. + +**UE Inactive AS Context:** UE Inactive AS Context is stored when the connection is suspended and restored when the connection is resumed. It includes information as defined in clause 5.3.8.3. + +**V2X sidelink communication:** AS functionality enabling V2X Communication as defined in TS 23.285 [56], between nearby UEs, using E-UTRA technology but not traversing any network node. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|-----|--------------------------| +| 5GC | 5G Core Network | +| A2X | Aircraft-to-Everything | +| ACK | Acknowledgement | +| AM | Acknowledged Mode | +| ARQ | Automatic Repeat Request | +| AS | Access Stratum | + +| | | +|--------|---------------------------------------| +| ASN.1 | Abstract Syntax Notation One | +| ATG | Air to Ground | +| BAP | Backhaul Adaptation Protocol | +| BCD | Binary Coded Decimal | +| BFD | Beam Failure Detection | +| BH | Backhaul | +| BLER | Block Error Rate | +| BRID | Broadcast Remote Identification | +| BSR | Buffer Status Report | +| BWP | Bandwidth Part | +| CA | Carrier Aggregation | +| CAG | Closed Access Group | +| CAG-ID | Closed Access Group Identifier | +| CAPC | Channel Access Priority Class | +| CBR | Channel Busy Ratio | +| CCCH | Common Control Channel | +| CFR | Common Frequency Resources | +| CG | Cell Group | +| CHO | Conditional Handover | +| CLI | Cross Link Interference | +| CMAS | Commercial Mobile Alert Service | +| CP | Control Plane | +| CPA | Conditional PSCell Addition | +| CPAC | Conditional PSCell Addition or Change | +| CPC | Conditional PSCell Change | +| C-RNTI | Cell RNTI | +| CSI | Channel State Information | +| DAA | Detect And Avoid | +| DAPS | Dual Active Protocol Stack | +| DC | Dual Connectivity | +| DCCH | Dedicated Control Channel | +| DCI | Downlink Control Information | +| DCP | DCI with CRC scrambled by PS-RNTI | +| DFN | Direct Frame Number | +| DL | Downlink | +| DL-PRS | Downlink Positioning Reference Signal | +| DL-SCH | Downlink Shared Channel | +| DM-RS | Demodulation Reference Signal | +| DRB | (user) Data Radio Bearer | +| DRX | Discontinuous Reception | + +| | | +|------------|----------------------------------------------------------| +| DSR | Delay Status Report | +| DTCH | Dedicated Traffic Channel | +| DTX | Discontinuous Transmission | +| ECEF | Earth-Centered, Earth-Fixed | +| ECI | Earth-Centered Inertial | +| EN-DC | E-UTRA NR Dual Connectivity with E-UTRA connected to EPC | +| EPC | Evolved Packet Core | +| EPS | Evolved Packet System | +| ETWS | Earthquake and Tsunami Warning System | +| E-UTRA | Evolved Universal Terrestrial Radio Access | +| E-UTRA/5GC | E-UTRA connected to 5GC | +| E-UTRA/EPC | E-UTRA connected to EPC | +| E-UTRAN | Evolved Universal Terrestrial Radio Access Network | +| FDD | Frequency Division Duplex | +| FFS | For Further Study | +| G-CS-RNTI | Group Configured Scheduling RNTI | +| GERAN | GSM/EDGE Radio Access Network | +| GIN | Group ID for Network selection | +| GNSS | Global Navigation Satellite System | +| G-RNTI | Group RNTI | +| GSM | Global System for Mobile Communications | +| HARQ | Hybrid Automatic Repeat Request | +| HRNN | Human Readable Network Name | +| HSDN | High Speed Dedicated Network | +| H-SFN | Hyper SFN | +| HST | High Speed Train | +| IAB | Integrated Access and Backhaul | +| IAB-DU | IAB-node DU | +| IAB-MT | IAB Mobile Termination | +| IDC | In-Device Coexistence | +| IE | Information element | +| IMSI | International Mobile Subscriber Identity | +| kB | Kilobyte (1000 bytes) | +| L1 | Layer 1 | +| L2 | Layer 2 | +| L3 | Layer 3 | +| LBT | Listen Before Talk | +| LEO | Low Earth Orbit | +| LTM | L1/L2 Triggered Mobility | +| MAC | Medium Access Control | + +| | | +|-----------|-----------------------------------------------------------------------| +| MBS | Multicast/Broadcast Service | +| MBS FSAI | MBS Frequency Selection Area Identity | +| MCCH | MBS Control Channel | +| MCG | Master Cell Group | +| MDT | Minimization of Drive Tests | +| MIB | Master Information Block | +| MO-SDT | Mobile Originated SDT | +| MPE | Maximum Permissible Exposure | +| MP | Multi-path | +| MRB | MBS Radio Bearer | +| MR-DC | Multi-Radio Dual Connectivity | +| MTCH | MBS Traffic Channel | +| MT-SDT | Mobile Terminated SDT | +| MTSI | Multimedia Telephony Service for IMS | +| MUSIM | Multi-Universal Subscriber Identity Module | +| N3C | Non-3GPP Connection | +| N/A | Not Applicable | +| NCR | Network-Controlled Repeater | +| NCR-Fwd | NCR Forwarding | +| NCR-MT | NCR Mobile Termination | +| NE-DC | NR E-UTRA Dual Connectivity | +| NES | Network Energy Savings | +| (NG)EN-DC | E-UTRA NR Dual Connectivity (covering E-UTRA connected to EPC or 5GC) | +| NGEN-DC | E-UTRA NR Dual Connectivity with E-UTRA connected to 5GC | +| NID | Network Identifier | +| NPN | Non-Public Network | +| NR-DC | NR-NR Dual Connectivity | +| NR/5GC | NR connected to 5GC | +| NSAG | Network Slice AS Group | +| NTN | Non-Terrestrial Network | +| PCell | Primary Cell | +| PDCP | Packet Data Convergence Protocol | +| PDU | Protocol Data Unit | +| PEI | Paging Early Indication | +| PEI-O | Paging Early Indication-Occasion | +| PLMN | Public Land Mobile Network | +| PNI-NPN | Public Network Integrated Non-Public Network | +| posSIB | Positioning SIB | +| PPW | PRS Processing Window | +| PRS | Positioning Reference Signal | + +| | | +|---------|---------------------------------------| +| PSCell | Primary SCG Cell | +| PSI | PDU Set Importance | +| PTM | Point to Multipoint | +| PTP | Point to Point | +| PWS | Public Warning System | +| QoE | Quality of Experience | +| QoS | Quality of Service | +| RAN | Radio Access Network | +| RAT | Radio Access Technology | +| RLC | Radio Link Control | +| RLM | Radio Link Monitoring | +| RMTC | RSSI Measurement Timing Configuration | +| RNA | RAN-based Notification Area | +| RNTI | Radio Network Temporary Identifier | +| ROHC | Robust Header Compression | +| RPLMN | Registered Public Land Mobile Network | +| RRC | Radio Resource Control | +| RS | Reference Signal | +| SBAS | Satellite Based Augmentation System | +| SCell | Secondary Cell | +| SCG | Secondary Cell Group | +| SCS | Subcarrier Spacing | +| SD-RSRP | Sidelink Discovery RSRP | +| SDT | Small Data Transmission | +| SFN | Single Frequency Network | +| SFN | System Frame Number | +| SFTD | SFN and Frame Timing Difference | +| SI | System Information | +| SIB | System Information Block | +| SL | Sidelink | +| SL-PRS | Sidelink Positioning Reference Signal | +| SLSS | Sidelink Synchronisation Signal | +| SNPN | Stand-alone Non-Public Network | +| SpCell | Special Cell | +| SRAP | Sidelink Relay Adaptation Protocol | +| SRB | Signalling Radio Bearer | +| SRS | Sounding Reference Signal | +| SSB | Synchronization Signal Block | +| TAG | Timing Advance Group | +| TDCP | Time Domain Channel Property | + +| | | +|------|---------------------------------| +| TDD | Time Division Duplex | +| TEG | Timing Error Group | +| TM | Transparent Mode | +| TMGI | Temporary Mobile Group Identity | +| TN | Terrestrial Network | +| U2N | UE-to-Network | +| U2U | UE-to-UE | +| UDC | Uplink Data Compression | +| UE | User Equipment | +| UL | Uplink | +| UM | Unacknowledged Mode | +| UP | User Plane | +| VR | Virtual Reality | +| XR | eXtended Reality | + +In the ASN.1, lower case may be used for some (parts) of the above abbreviations e.g. c-RNTI. + +--- + +## 4 General + +### 4.1 Introduction + +This specification is organised as follows: + +- clause 4.2 describes the RRC protocol model; +- clause 4.3 specifies the services provided to upper layers as well as the services expected from lower layers; +- clause 4.4 lists the RRC functions; +- clause 5 specifies RRC procedures, including UE state transitions; +- clause 6 specifies the RRC messages in ASN.1 and description; +- clause 7 specifies the variables (including protocol timers and constants) and counters to be used by the UE; +- clause 8 specifies the encoding of the RRC messages; +- clause 9 specifies the specified and default radio configurations; +- clause 10 specifies generic error handling; + +- clause 11 specifies the RRC messages transferred across network nodes; +- clause 12 specifies the UE capability related constraints and performance requirements. + +## 4.2 Architecture + +### 4.2.1 UE states and state transitions including inter RAT + +A UE is either in RRC\_CONNECTED state or in RRC\_INACTIVE state when an RRC connection has been established. If this is not the case, i.e. no RRC connection is established, the UE is in RRC\_IDLE state. The RRC states can further be characterised as follows: + +- **RRC\_IDLE:** + - A UE specific DRX may be configured by upper layers; + - At lower layers, the UE may be configured with a DRX for PTM transmission of MBS broadcast; + - UE controlled mobility based on network configuration; + - The UE: + - Monitors Short Messages transmitted with P-RNTI over DCI (see clause 6.5); + - Monitors a Paging channel for CN paging using 5G-S-TMSI, except if the UE is acting as a L2 U2N Remote UE; + - If configured by upper layers for MBS multicast reception, monitors a Paging channel for CN paging using TMGI; + - Performs neighbouring cell measurements and cell (re-)selection; + - Acquires system information and can send SI request (if configured); + - Performs logging of available measurements together with location and time for logged measurement configured UEs; + - Performs idle/inactive measurements for idle/inactive measurement configured UEs; + - If configured by upper layers for MBS broadcast reception, acquires MCCH change notification and MBS broadcast control information and data. +- **RRC\_INACTIVE:** + - A UE specific DRX may be configured by upper layers or by RRC layer; + - At lower layers, the UE may be configured with a DRX for PTM transmission of MBS broadcast and/or a DRX for PTM transmission of MBS multicast; + +- UE controlled mobility based on network configuration; +- The UE stores the UE Inactive AS context; +- A RAN-based notification area is configured by RRC layer; +- Transfer of unicast data and/or signalling to/from UE over radio bearers configured for SDT. +- The UE: + - Monitors Short Messages transmitted with P-RNTI over DCI (see clause 6.5); + - While T319a is running, monitors control channels associated with the shared data channel to determine if data is scheduled for it; + - While T319a is not running, monitors a Paging channel for CN paging using 5G-S-TMSI and RAN paging using fullI-RNTI, except if the UE is acting as a L2 U2N Remote UE; + - If configured by upper layers for MBS multicast reception, while T319a is not running, monitors a Paging channel for paging using TMGI; + - Performs neighbouring cell measurements and cell (re-)selection; + - Performs RAN-based notification area updates periodically and when moving outside the configured RAN-based notification area; + - Acquires system information and, while SDT procedure is not ongoing, can send SI request (if configured); + - While SDT procedure is not ongoing, performs logging of available measurements together with location and time for logged measurement configured UEs; + - While SDT procedure is not ongoing, performs idle/inactive measurements for idle/inactive measurement configured UEs; + - If configured by upper layers for MBS broadcast reception, acquires MCCH change notification and MBS broadcast control information and data; + - If configured for MBS multicast reception in RRC\_INACTIVE, acquires multicast MCCH change notification and MBS multicast control information and data; + - Transmits SRS for Positioning. +- **RRc\_CONNECTED:** + - The UE stores the AS context; + - Transfer of unicast data to/from UE; + - Transfer of MBS multicast data to UE; + - At lower layers, the UE may be configured with a UE specific DRX; + +- At lower layers, the UE may be configured with a DRX for PTM transmission of MBS broadcast and/or a DRX for MBS multicast; +- At lower layers, the UE may be configured with a cell specific cell DTX/DRX; +- For UEs supporting CA, use of one or more SCells, aggregated with the SpCell, for increased bandwidth; +- For UEs supporting DC, use of one SCG, aggregated with the MCG, for increased bandwidth; +- Network controlled mobility within NR, to/from E-UTRA, and to UTRA-FDD; +- Network controlled mobility (path switch) between a serving cell and a L2 U2N Relay UE, or vice versa. +- The UE: + - Monitors Short Messages transmitted with P-RNTI over DCI (see clause 6.5), if configured; + - Monitors control channels associated with the shared data channel to determine if data is scheduled for it; + - Provides channel quality and feedback information; + - Performs neighbouring cell measurements and measurement reporting; + - Acquires system information; + - Performs immediate MDT measurement together with available location reporting; + - If configured by upper layers for MBS broadcast reception, acquires MCCH change notification and MBS broadcast control information and data. + +Figure 4.2.1-1 illustrates an overview of UE RRC state machine and state transitions in NR. A UE has only one RRC state in NR at one time. + +![Diagram showing UE state machine and state transitions in NR. It features a top bar with states RRC_IDLE, RRC_INACTIVE, and RRC_CONNECTED, and a bottom rounded rectangle representing the RRC_CONNECTED state. Arrows indicate transitions between these states.](2cf3896394a2342a2b46c504ab9a8830_img.jpg) + +The diagram illustrates the UE state machine and state transitions in NR. At the top, a horizontal bar contains three states: **RRC\_IDLE**, **RRC\_INACTIVE**, and **RRC\_CONNECTED**. Below this bar, the text **Release** and **Suspend** are visible. Below the top bar is a rounded rectangle representing the **RRC\_CONNECTED** state. There are two vertical double-headed arrows: one on the left connecting the top bar to the rounded rectangle, and another on the right connecting the bottom of the rounded rectangle back to the top bar. Additionally, a vertical line extends downwards from the bottom of the rounded rectangle. + +Diagram showing UE state machine and state transitions in NR. It features a top bar with states RRC\_IDLE, RRC\_INACTIVE, and RRC\_CONNECTED, and a bottom rounded rectangle representing the RRC\_CONNECTED state. Arrows indicate transitions between these states. + +**Figure 4.2.1-1: UE state machine and state transitions in NR** + +Figure 4.2.1-2 illustrates an overview of UE state machine and state transitions in NR as well as the mobility procedures supported between NR/5GC, E-UTRA/EPC and E-UTRA/5GC. + +![UE state machine diagram showing transitions between EUTRA RRC_CONNECTED, EUTRA RRC_INACTIVE, NR RRC_CONNECTED, and NR RRC_INACTIVE states.](7ed5d5770331f31ade15439a21c31425_img.jpg) + +This diagram illustrates the UE state machine and state transitions between NR/5GC, E-UTRA/EPC, and E-UTRA/5GC. It features four main state boxes: 'EUTRA RRC\_CONNECTED' (top left), 'NR RRC\_CONNECTED' (top right), 'EUTRA RRC\_INACTIVE' (bottom left), and 'NR RRC\_INACTIVE' (bottom right). Transitions include: 'Establish / Release' (vertical double-headed arrows between connected and inactive states for both EUTRA and NR); 'Handover' (horizontal double-headed arrow between EUTRA RRC\_CONNECTED and NR RRC\_CONNECTED); 'Resume / Release with' (vertical double-headed arrow between NR RRC\_CONNECTED and NR RRC\_INACTIVE); 'Reselecti' (diagonal arrows from EUTRA RRC\_INACTIVE to NR RRC\_CONNECTED and from NR RRC\_INACTIVE to EUTRA RRC\_CONNECTED); and 'Releas' (vertical downward arrows from NR RRC\_INACTIVE). + +UE state machine diagram showing transitions between EUTRA RRC\_CONNECTED, EUTRA RRC\_INACTIVE, NR RRC\_CONNECTED, and NR RRC\_INACTIVE states. + +Figure 4.2.1-2: UE state machine and state transitions between NR/5GC, E-UTRA/EPC and E-UTRA/5GC + +Figure 4.2.1-3 illustrates the mobility procedure supported between NR/5GC and UTRA-FDD. + +![Mobility procedure diagram showing a handover from NR RRC_CONNECTED to UTRA-FDD CELL_DCH.](ef5f5c6665b6ae13660ede412333ba45_img.jpg) + +This diagram shows a mobility procedure between NR/5GC and UTRA-FDD. It consists of two state boxes: 'NR RRC\_CONNECTED' on the left and 'UTRA-FDD CELL\_DCH' on the right, connected by a single horizontal arrow labeled 'Handover'. + +Mobility procedure diagram showing a handover from NR RRC\_CONNECTED to UTRA-FDD CELL\_DCH. + +Figure 4.2.1-3: Mobility procedure supported between NR/5GC and UTRA-FDD + +## 4.2.2 Signalling radio bearers + +"Signalling Radio Bearers" (SRBs) are defined as Radio Bearers (RBs) that are used only for the transmission of RRC and NAS messages. More specifically, the following SRBs are defined: + +- SRB0 is for RRC messages using the CCCH logical channel; +- SRB1 is for RRC messages (which may include a piggybacked NAS message) as well as for NAS messages prior to the establishment of SRB2, all using DCCH logical channel; +- SRB2 is for NAS messages and for RRC messages which include logged measurement information, all using DCCH logical channel. SRB2 has a lower priority than SRB1 and may be configured by the network after AS security activation; +- SRB3 is for specific RRC messages when UE is in (NG)EN-DC or NR-DC, all using DCCH logical channel; +- SRB4 is for RRC messages which include application layer measurement report information, all using DCCH logical channel. SRB4 has a lower priority than SRB1 and can only be configured by the network after AS security activation. +- SRB5 is for RRC messages which include application layer measurement report information, all using DCCH logical channel. SRB5 has a lower priority than SRB1 and SRB3 and can only be configured by the SN serving the SCG when the UE is in NR-DC, after AS security activation. + +In downlink, piggybacking of NAS messages is used only for one dependant (i.e. with joint success/failure) procedure: bearer establishment/modification/release. In uplink piggybacking of NAS message is used only for transferring the initial NAS message during connection setup and connection resume. + +NOTE 1: The NAS messages transferred via SRB2 are also contained in RRC messages, which however do not include any RRC protocol control information. + +Once AS security is activated, all RRC messages on SRB1, SRB2, SRB3, SRB4 and SRB5, including those containing NAS messages, are integrity protected and ciphered by PDCP. NAS independently applies integrity protection and ciphering to the NAS messages, see TS 24.501 [23]. + +Split SRB is supported for all the MR-DC options as well as MP in both SRB1 and SRB2 (split SRB is not supported for SRB0, SRB3, SRB4 and SRB5). + +For operation with shared spectrum channel access in FR1, SRB0, SRB1 and SRB3 are assigned with the highest priority Channel Access Priority Class (CAPC), (i.e. CAPC = 1) while CAPC for SRB2 is configurable. + +## 4.3 Services + +### 4.3.1 Services provided to upper layers + +The RRC protocol offers the following services to upper layers: + +- Broadcast of common control information; +- Notification of UEs in RRC\_IDLE, e.g. about a mobile terminating call; +- Notification of UEs about ETWS and/or CMAS; +- Transfer of dedicated signalling; +- Broadcast of positioning assistance data; +- Transfer of application layer measurement configuration and reporting. + +### 4.3.2 Services expected from lower layers + +In brief, the following are the main services that RRC expects from lower layers: + +- Integrity protection, ciphering and loss-less in-sequence delivery of information without duplication; + +## 4.4 Functions + +The RRC protocol includes the following main functions: + +- Broadcast of system information: + - Including NAS common information; + - Information applicable for UEs in RRC\_IDLE and RRC\_INACTIVE (e.g. cell (re-)selection parameters, neighbouring cell information) and information (also) applicable for UEs in RRC\_CONNECTED (e.g. common channel configuration information); + - Including ETWS notification, CMAS notification; + - Including positioning assistance data. +- RRC connection control: + - Paging; + +- Establishment/modification/suspension/resumption/release of RRC connection, including e.g. assignment/modification of UE identity (C-RNTI, fullI-RNTI, etc.), establishment/modification/suspension/resumption/release of SRBs (except for SRB0); +- Access barring; +- Initial AS security activation, i.e. initial configuration of AS integrity protection (SRBs, DRBs) and AS ciphering (SRBs, DRBs); +- RRC connection mobility including e.g. intra-frequency and inter-frequency handover, path switch from a PCell to a target L2 U2N Relay UE or from a L2 U2N Relay UE to a target PCell or from a source L2 U2N Relay UE to a target L2 U2N Relay UE, associated AS security handling, i.e. key/algorithm change, specification of RRC context information transferred between network nodes; +- Establishment/modification/suspension/resumption/release of RBs carrying user data (DRBs/MRBs); +- Radio configuration control including e.g. assignment/modification of ARQ configuration, HARQ configuration, DRX configuration; +- In case of DC, cell management including e.g. change of PSCell, addition/modification/release of SCG cell(s); +- In case of CA, cell management including e.g. addition/modification/release of SCell(s); +- In case of MP, path management including e.g. addition/modification/release of indirect path; +- QoS control including assignment/ modification of semi-persistent scheduling (SPS) configuration and configured grant configuration for DL and UL respectively, assignment/ modification of parameters for UL rate control in the UE, i.e. allocation of a priority and a prioritised bit rate (PBR) for each RB of UE and logical channel of IAB-MT. +- Recovery from radio link failure. +- Inter-RAT mobility including e.g. AS security activation, transfer of RRC context information; +- Measurement configuration and reporting: + - Establishment/modification/release of measurement configuration (e.g. intra-frequency, inter-frequency and inter- RAT measurements); + - Setup and release of measurement gaps; + - Measurement reporting. +- Configuration of BAP entity and BH RLC channels for the support of IAB-node. +- Configuration of SRAP entity and Uu/PC5 Relay RLC channels for the support of L2 U2N relay. +- Other functions including e.g. generic protocol error handling, transfer of dedicated NAS information, transfer of UE radio access capability information. +- Support of self-configuration and self-optimisation. + +- Support of measurement logging and reporting for network performance optimisation, as specified in TS 37.320 [61]; +- Support of transfer of application layer measurement configuration and reporting. +- Configuration of side control information for NCR-node. + +--- + +## 5 Procedures + +### 5.1 General + +#### 5.1.1 Introduction + +This clause covers the general requirements. + +#### 5.1.2 General requirements + +The UE shall: + +1> process the received messages in order of reception by RRC, i.e. the processing of a message shall be completed before starting the processing of a subsequent message; + +NOTE: Network may initiate a subsequent procedure prior to receiving the UE's response of a previously initiated procedure. + +1> within a clause execute the steps according to the order specified in the procedural description; + +1> consider the term 'radio bearer' (RB) to cover SRBs, DRBs and MRBs unless explicitly stated otherwise; + +1> set the *rrc-TransactionIdentifier* in the response message, if included, to the same value as included in the message received from the network that triggered the response message; + +1> upon receiving a choice value set to *setup*: + +2> apply the corresponding received configuration and start using the associated resources, unless explicitly specified otherwise; + +1> upon receiving a choice value set to *release*: + +2> clear the corresponding configuration and stop using the associated resources; + +1> in case the size of a list is extended, upon receiving an extension field comprising the entries in addition to the ones carried by the original field (regardless of whether the network signals more entries in total); apply the following generic behaviour unless explicitly stated otherwise: + +2) create a combined list by concatenating the additional entries included in the extension field to the original field while maintaining the order among both the original and the additional entries; + +2) for the combined list, created according to the previous, apply the same behaviour as defined for the original field. + +### 5.1.3 Requirements for UE in MR-DC + +In this specification, the UE considers itself to be in: + +- EN-DC, if and only if it is configured with *nr-SecondaryCellGroupConfig* according to TS 36.331[10], and it is connected to EPC, +- NGEN-DC, if and only if it is configured with *nr-SecondaryCellGroupConfig* according to TS 36.331[10], and it is connected to 5GC, +- NE-DC, if and only if it is configured with *mrdc-SecondaryCellGroup* set to *eutra-SCG*, +- NR-DC, if and only if it is configured with *mrdc-SecondaryCellGroup* set to *nr-SCG*, +- MR-DC, if and only if it is in (NG)EN-DC, NE-DC or NR-DC. + +NOTE: This use of these terms deviates from the definition in TS 37.340 [41] and other specifications. In TS 37.340, these terms include also the case where the UE is configured with E-UTRA or NR MCG only (i.e. no NR or E-UTRA SCG) but with one or more bearers terminated in a secondary node (i.e. using NR PDCP). + +The UE in (NG)EN-DC only executes a subclause of clause 5 in this specification when the subclause: + +- is referred to from a subclause under execution, either in this specification or in TS 36.331 [10]; or +- applies to a message received on SRB3 (if SRB3 is established); or +- applies to field(s), IE(s), UE variable(s) or timer(s) in this specification that the UE is configured with. + +When executing a subclause of clause 5 in this specification, the UE follows the requirements in clause 5.1.2 and in all subclauses of this specification applicable to the messages (including processing time requirements), fields, IEs, timers and UE variables indicated in the subclause under execution. + +## 5.2 System information + +### 5.2.1 Introduction + +System Information (SI) is divided into the *MIB* and a number of SIBs and posSIBs where: + +- the *MIB* is always transmitted on the BCH with a periodicity of 80 ms and repetitions made within 80 ms (TS 38.212 [17], clause 7.1) and it includes parameters that are needed to acquire *SIB1* from the cell. The first transmission of the *MIB* is scheduled in subframes as defined in TS 38.213 [13], clause 4.1 and repetitions are scheduled according to the period of SSB; + +NOTE 1: If the period of SSB is larger than 80 ms, the MIB is transmitted with the same periodicity as that of SSB. + +- the *SIB1* is transmitted on the DL-SCH with a periodicity of 160 ms and variable transmission repetition periodicity within 160 ms as specified in TS 38.213 [13], clause 13. The default transmission repetition periodicity of *SIB1* is 20 ms but the actual transmission repetition periodicity is up to network implementation. For SSB and CORESET multiplexing pattern 1, *SIB1* repetition transmission period is 20 ms. For SSB and CORESET multiplexing pattern 2/3, *SIB1* transmission repetition period is the same as the SSB period (TS 38.213 [13], clause 13). *SIB1* includes information regarding the availability and scheduling (e.g. mapping of SIBs to SI message, periodicity, SI-window size) of other SIBs with an indication whether one or more SIBs are only provided on-demand and, in that case, the configuration needed by the UE to perform the SI request. *SIB1* is cell-specific SIB; +- SIBs other than *SIB1* and posSIBs are carried in *SystemInformation* (SI) messages, which are transmitted on the DL-SCH. Only SIBs or posSIBs having the same periodicity can be mapped to the same SI message. SIBs and posSIBs are mapped to different SI messages, i.e. an SI message contains either only SIBs or only posSIBs. Each SI message is transmitted within periodically occurring time domain windows (referred to as SI-windows with same length for all SI messages). Each SI message is associated with an SI-window and the SI-windows of different SI messages do not overlap. That is, within one SI-window only the corresponding SI message is transmitted. An SI message may be repeated with the same content a number of times within the SI-window. Any SIB or posSIB except *SIB1* can be configured to be cell specific or area specific, using an indication in *SIB1*. The cell specific SIB is applicable only within a cell that provides the SIB while the area specific SIB is applicable within an area referred to as SI area, which consists of one or several cells and is identified by *systemInformationAreaID*; +- The mapping of SIBs to SI messages is configured in *schedulingInfoList* and *schedulingInfoList2*, while the mapping of posSIBs to SI messages is configured in *posSchedulingInfoList* and *schedulingInfoList2*. +Each SIB and each posSIB is mapped to a single SI message. posSIBs of the same *posSibType* carrying GNSS Generic Assistance Data for different GNSS/SBAS (identified by *gnss-id/sbas-id*, see TS 37.355 [49]) are mapped to different SI messages. +Each SIB and posSIB is contained at most once in an SI message. +For SIBs and posSIBs with segments, the segments contained in SI messages are transmitted according to the SI message periodicity, with one segment of a particular *sibType/posSibType* in each SI message; +- For a UE in RRC\_CONNECTED, the network can provide system information through dedicated signalling using the *RRCReconfiguration* message, e.g. if the UE has an active BWP with no common search space configured to monitor system information, paging, or upon request from the UE. +- For PSCell and SCells, the network provides the required SI by dedicated signalling, i.e. within an *RRCReconfiguration* message. Nevertheless, the UE shall acquire *MIB* of the PSCell to get SFN timing of the SCG (which may be different from MCG). Upon change of relevant SI for SCell, the network releases and adds the concerned SCell. For PSCell, the required SI can only be changed with Reconfiguration with Sync. + +NOTE 2: The physical layer imposes a limit to the maximum size a SIB can take. The maximum *SIB1* or *SI message* size is 2976 bits. + +## 5.2.2 System information acquisition + +### 5.2.2.1 General UE requirements + +![Sequence diagram illustrating System Information acquisition between a UE and a Network. The sequence starts with the Network broadcasting the MIB. The UE receives the MIB and then broadcasts SIB1. The UE then sends a SystemInformationRequest to the Network. The Network responds with SystemInformation messages.](977811d1c73b74f801be9f4c376694ca_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Network + Note right of Network: MIB + Note left of UE: SIB1 + Note left of UE: SystemInformationRequest + Note right of Network: SystemInformation messages + +``` + +Sequence diagram illustrating System Information acquisition between a UE and a Network. The sequence starts with the Network broadcasting the MIB. The UE receives the MIB and then broadcasts SIB1. The UE then sends a SystemInformationRequest to the Network. The Network responds with SystemInformation messages. + +Figure 5.2.2.1-1: System information acquisition + +The UE applies the SI acquisition procedure to acquire the AS, NAS- and positioning assistance data information. The procedure applies to UEs in RRC\_IDLE, in RRC\_INACTIVE and in RRC\_CONNECTED. + +The UE in RRC\_IDLE and RRC\_INACTIVE shall ensure having a valid version of (at least) the *MIB*, *SIB1* through *SIB4*, *SIB5* (if the UE supports E-UTRA), *SIB11* (if the UE is configured for idle/inactive measurements), *SIB12* (if UE is capable of NR sidelink communication/discovery and is configured by upper layers to receive or transmit NR sidelink communication/discovery), and *SIB13*, *SIB14* (if UE is capable of V2X sidelink communication and is configured by upper layers to receive or transmit V2X sidelink communication), *SIB15* (if UE is configured by upper layers to report disaster roaming related information), *SIB16* (if the UE is capable of slice-based cell reselection and the UE receives NSAG information for cell reselection from upper layer), *SIB17* (if the UE is using TRS resources for power saving in RRC\_IDLE and RRC\_INACTIVE), *SIB19* (if UE is accessing NR via NTN access) and *SIB22* (for ATG access). + +The UE capable of MBS broadcast which is receiving or interested to receive MBS broadcast service(s) via a broadcast MRB shall ensure having a valid version of *SIB20*, regardless of the RRC state the UE is in. + +The UE shall ensure having a valid version of the posSIB requested by upper layers. + +### 5.2.2.2 SIB validity and need to (re)-acquire SIB + +#### 5.2.2.2.1 SIB validity + +The UE shall apply the SI acquisition procedure as defined in clause 5.2.2.3 upon cell selection (e.g. upon power on), cell-reselection, return from out of coverage, after reconfiguration with sync completion, after entering the network from another RAT, upon receiving an indication that the system information has changed, upon receiving a PWS notification, upon receiving request (e.g., a positioning request) from upper layers; and whenever the UE does not have a valid version of a stored SIB or posSIB or a valid version of a requested SIB. + +When the UE acquires a *MIB* or a *SIB1* or an SI message in a serving cell as described in clause 5.2.2.3, and if the UE stores the acquired SIB, then the UE shall store the associated *areaScope*, if present, the first *PLMN-Identity* in the *PLMN-IdentityInfoList* for non-NPN-only cells or the first NPN identity (SNPN identity in case of SNPN, or PNI-NPN identity in case of PNI-NPN) in the *NPN-IdentityInfoList* for NPN-only cells, the *cellIdentity*, the *systemInformationAreaID*, if present, and the *valueTag*, if present, as indicated in the *si-SchedulingInfo* for the SIB. If the UE stores the acquired posSIB, then the UE shall store the associated *areaScope*, if present, the *cellIdentity*, the *systemInformationAreaID*, if present, the *valueTag*, if provided in *assistanceDataSIB-Element*, and the *expirationTime* if provided in *assistanceDataSIB-Element*. The UE may use a valid stored version of the SI except *MIB*, *SIB1*, *SIB6*, *SIB7* or *SIB8* e.g. after cell re-selection, upon return from out of coverage or after the reception of SI change indication. The *valueTag* and *expirationTime* for posSIB is optionally provided in *assistanceDataSIB-Element*, as specified in TS 37.355 [49]. + +A L2 U2N Remote UE in RRC\_IDLE or RRC\_INACTIVE can inform the interested SIB(s) to the connected L2 U2N Relay UE as defined in clause 5.8.9.8.2 and receive the SIB(s) from the L2 U2N Relay UE as defined in clause 5.8.9.9.3. A L2 U2N Remote UE in RRC\_CONNECTED receives SIB1 and other SIB(s) in *RRCReconfiguration* message and performs on-demand SI request if required, as defined in clause 5.2.2.3.5 and 5.2.2.3.6. The L2 U2N Remote UE in RRC\_IDLE or RRC\_INACTIVE or RRC\_CONNECTED is not required to obtain SI over Uu interface, but it may decide to perform the SI acquisition procedure over Uu interface as defined in clause 5.2.2.3 by UE implementation. + +NOTE: The storage and management of the stored SIBs in addition to the SIBs valid for the current serving cell is left to UE implementation. + +The UE shall: + +- 1> delete any stored version of a SIB after 3 hours from the moment it was successfully confirmed as valid; +- 1> for each stored version of a SIB: + - 2> if the *areaScope* is associated and its value for the stored version of the SIB is the same as the value received in the *si-SchedulingInfo* for that SIB from the serving cell: + - 3> if the UE is NPN capable and the cell is an NPN-only cell: + - 4> if the first NPN identity included in the *NPN-IdentityInfoList*, the *systemInformationAreaID* and the *valueTag* that are included in the *si-SchedulingInfo* for the SIB received from the serving cell are identical to the NPN identity, the *systemInformationAreaID* and the *valueTag* associated with the stored version of that SIB: + - 5> consider the stored SIB as valid for the cell; + - 3> else if the first *PLMN-Identity* included in the *PLMN-IdentityInfoList*, the *systemInformationAreaID* and the *valueTag* that are included in the *si-SchedulingInfo* for the SIB received from the serving cell are identical to the *PLMN-Identity*, the *systemInformationAreaID* and the *valueTag* associated with the stored version of that SIB: + - 4> consider the stored SIB as valid for the cell; + - 2> if the *areaScope* is not present for the stored version of the SIB and the *areaScope* value is not included in the *si-SchedulingInfo* for that SIB from the serving cell: + - 3> if the UE is NPN capable and the cell is an NPN-only cell: + - 4> if the first NPN identity in the *NPN-IdentityInfoList*, the *cellIdentity* and *valueTag* that are included in the *si-SchedulingInfo* for the SIB received from the serving cell are identical to the NPN identity, the *cellIdentity* and the *valueTag* associated with the stored version of that SIB: + - 5> consider the stored SIB as valid for the cell; + +5> consider the stored SIB as valid for the cell; + +3> else if the first *PLMN-Identity* in the *PLMN-IdentityInfoList*, the *cellIdentity* and *valueTag* that are included in the *si-SchedulingInfo* for the SIB received from the serving cell are identical to the *PLMN-Identity*, the *cellIdentity* and the *valueTag* associated with the stored version of that SIB: + +4> consider the stored SIB as valid for the cell; + +1> for each stored version of a posSIB: + +2> if the *areaScope* is associated and its value for the stored version of the posSIB is the same as the value received in the *posSIB-MappingInfo* for that posSIB from the serving cell and the *systemInformationAreaID* included in the *si-SchedulingInfo* is identical to the *systemInformationAreaID* associated with the stored version of that posSIB: + +3> if the *valueTag* (see TS 37.355 [49]) for the posSIB received from the serving cell is identical to the *valueTag* associated with the stored version of that posSIB; or if the *expirationTime* (see TS 37.355 [49]) associated with the stored posSIB has not been expired: + +4> consider the stored posSIB as valid for the cell; + +2> if the *areaScope* is not present for the stored version of the posSIB and the *areaScope* value is not included in the *posSIB-MappingInfo* for that posSIB from the serving cell and the *cellIdentity* for the posSIB received from the serving cell is identical to the *cellIdentity* associated with the stored version of that posSIB: + +3> if the *valueTag* (see TS 37.355 [49]) for the posSIB received from the serving cell is identical to the *valueTag* associated with the stored version of that posSIB; or if the *expirationTime* (see TS 37.355 [49]) associated with the stored posSIB has not been expired: + +4> consider the stored posSIB as valid for the cell; + +#### 5.2.2.2.2 SI change indication and PWS notification + +A modification period is used, i.e. updated SI message (other than SI message for ETWS, CMAS, positioning assistance data, and some NTN-specific information as specified in the field descriptions) is broadcasted in the modification period following the one where SI change indication is transmitted. The modification period boundaries are defined by SFN values for which $\text{SFN mod } m = 0$ , where $m$ is the number of radio frames comprising the modification period. The modification period is configured by system information. If H-SFN is provided in *SIB1*, and UE is configured with eDRX, modification period boundaries are defined by SFN values for which $(\text{H-SFN} * 1024 + \text{SFN}) \bmod m = 0$ . + +For UEs in RRC\_IDLE or RRC\_INACTIVE configured to use an IDLE eDRX cycle longer than the modification period, an eDRX acquisition period is defined. The boundaries of the eDRX acquisition period are determined by H-SFN values for which $\text{H-SFN mod } 1024 = 0$ . + +The UE receives indications about SI modifications and/or PWS notifications using Short Message transmitted with P-RNTI over DCI (see clause 6.5). Repetitions of SI change indication may occur within preceding modification period or within preceding eDRX acquisition period. SI change indication is not applicable for SI messages containing posSIBs. + +UEs in RRC\_IDLE or in RRC\_INACTIVE while SDT procedure is not ongoing shall monitor for SI change indication in its own paging occasion(s) that the UE monitors as specified in TS 38.304 [20]. UEs in RRC\_CONNECTED shall monitor for SI change indication in any paging occasion at least once per modification period if the UE is provided + +with common search space, including *pagingSearchSpace*, *searchSpaceSIB1* and *searchSpaceOtherSystemInformation*, on the active BWP to monitor paging, as specified in TS 38.213 [13], clause 13. + +UEs in RRC\_INACTIVE while SDT procedure is ongoing shall monitor for SI change indication in any paging occasion at least once per modification period, if the initial downlink BWP on which the SDT procedure is ongoing is associated with a CD-SSB. + +During a modification period where ETWS or CMAS transmission is started or stopped, the SI messages carrying the posSIBs scheduled in *posSchedulingInfoList* may change, so the UE might not be able to successfully receive those posSIBs in the remainder of the current modification period and next modification period according to the scheduling information received prior to the change. + +ETWS or CMAS capable UEs in RRC\_IDLE or in RRC\_INACTIVE while SDT procedure is not ongoing shall monitor for indications about PWS notification in its own paging occasion(s) that the UE monitors as specified in TS 38.304 [20]. ETWS or CMAS capable UEs in RRC\_CONNECTED shall monitor for indication about PWS notification in any paging occasion at least once every *defaultPagingCycle* if the UE is provided with common search space, including *pagingSearchSpace*, *searchSpaceSIB1* and *searchSpaceOtherSystemInformation*, on the active BWP to monitor paging. + +ETWS or CMAS capable UEs in RRC\_INACTIVE while SDT procedure is ongoing shall monitor for indication about PWS notification in any paging occasion at least once every *defaultPagingCycle*, if the initial downlink BWP on which the SDT procedure is ongoing is associated with a CD-SSB. + +For Short Message reception in a paging occasion, the UE monitors the PDCCH monitoring occasion(s) for paging as specified in TS 38.304 [20] and TS 38.213 [13]. + +A L2 U2N Remote UE is not required to monitor paging occasion for SI modifications and/or PWS notifications. It obtains the updated system information and SIB6/7/8 from the connected L2 U2N Relay UE as defined in clause 5.8.9.9.3. + +If the UE receives a Short Message, the UE shall: + +- 1> if the UE is ETWS capable or CMAS capable, the *etwsAndCmasIndication* bit of Short Message is set, and the UE is provided with *searchSpaceSIB1* and *searchSpaceOtherSystemInformation* on the active BWP or the initial BWP: + - 2> immediately re-acquire the *SIB1*; + - 2> if the UE is ETWS capable and *si-SchedulingInfo* includes scheduling information for *SIB6*: + - 3> acquire *SIB6*, as specified in clause 5.2.2.3.2, immediately; + - 2> if the UE is ETWS capable and *si-SchedulingInfo* includes scheduling information for *SIB7*: + - 3> acquire *SIB7*, as specified in clause 5.2.2.3.2, immediately; + - 2> if the UE is CMAS capable and *si-SchedulingInfo* includes scheduling information for *SIB8*: + - 3> acquire *SIB8*, as specified in clause 5.2.2.3.2, immediately; + +NOTE: In case *SIB6*, *SIB7*, or *SIB8* overlap with a measurement gap it is left to UE implementation how to immediately acquire *SIB6*, *SIB7*, or *SIB8*. + +- 1> if the UE does not operate an IDLE eDRX cycle longer than the modification period and the *systemInfoModification* bit of Short Message is set: + - 2> apply the SI acquisition procedure as defined in clause 5.2.2.3 from the start of the next modification period; +- 1> if the UE operates an IDLE eDRX cycle longer than the modification period and the *systemInfoModification-eDRX* bit of Short Message is set: + - 2> apply the SI acquisition procedure as defined in clause 5.2.2.3 from the start of the next eDRX acquisition period boundary. + +### 5.2.2.3 Acquisition of System Information + +#### 5.2.2.3.1 Acquisition of *MIB* and *SIB1* + +The UE shall: + +- 1> apply the specified BCCH configuration defined in 9.1.1.1; +- 1> if the UE is in RRC\_IDLE or in RRC\_INACTIVE; or +- 1> if the UE is in RRC\_CONNECTED while T311 is running: + - 2> acquire the *MIB*, which is scheduled as specified in TS 38.213 [13]; + - 2> if the UE is unable to acquire the *MIB*: + - 3> perform the actions as specified in clause 5.2.2.5; + - 2> else: + - 3> perform the actions specified in clause 5.2.2.4.1. +- 1> if the UE is in RRC\_CONNECTED with an active BWP with common search space configured by *searchSpaceSIB1* and *pagingSearchSpace* and has received an indication about change of system information; or +- 1> if the UE is in RRC\_CONNECTED with an active BWP with common search space configured by *searchSpaceSIB1* and the UE has not stored a valid version of a SIB or posSIB, in accordance with clause 5.2.2.2.1, of one or several required SIB(s) or posSIB(s) in accordance with clause 5.2.2.1, and, UE has not acquired SIB1 in current modification period; or +- 1> if the UE is in RRC\_CONNECTED with an active BWP with common search space configured by *searchSpaceSIB1*, and, the UE has not stored a valid version of a SIB or posSIB, in accordance with clause 5.2.2.2.1, of one or several required SIB(s) or posSIB(s) in accordance with clause 5.2.2.1, and, *si-BroadcastStatus* for the required SIB(s) or *posSI-BroadcastStatus* for the required posSIB(s) is set to *notBroadcasting* in acquired *SIB1* in current modification period; or +- 1> if the UE is in RRC\_IDLE or in RRC\_INACTIVE; or + +- 1> if the UE is in RRC\_CONNECTED while T311 is running: + - 2> if *ssb-SubcarrierOffset* indicates *SIB1* is transmitted in the cell (TS 38.213 [13]) and if *SIB1* acquisition is required for the UE: + - 3> acquire the *SIB1*, which is scheduled as specified in TS 38.213 [13]; + - 3> if the UE is unable to acquire the *SIB1*: + - 4> perform the actions as specified in clause 5.2.2.5; + - 3> else: + - 4> upon acquiring *SIB1*, perform the actions specified in clause 5.2.2.4.2. + - 2> else if *SIB1* acquisition is required for the UE and *ssb-SubcarrierOffset* indicates that *SIB1* is not scheduled in the cell: + - 3> perform the actions as specified in clause 5.2.2.5. + +NOTE 1: The UE in RRC\_CONNECTED is only required to acquire broadcasted *SIB1* and MBS broadcast if the UE can acquire it without disrupting unicast or MBS multicast data reception, i.e., the broadcast and unicast/MBS multicast beams are quasi co-located. The UE in RRC\_INACTIVE state while SDT procedure is ongoing, is only required to acquire broadcasted *SIB1* and *MIB* if the UE can acquire them without disrupting unicast data reception, i.e. the broadcast and unicast beams are quasi co-located. + +NOTE 2: UE in RRC\_INACTIVE that does not support *inactiveStateNTN-r17* enters RRC\_IDLE upon cell reselection between TN cell and NTN cell, and initiates the NAS signalling connection recovery (see TS 24.501 [23]). + +### 5.2.2.3.2 Acquisition of an SI message + +For SI message acquisition PDCCH monitoring occasion(s) are determined according to *searchSpaceOtherSystemInformation*. If *searchSpaceOtherSystemInformation* is set to zero, PDCCH monitoring occasions for SI message reception in SI-window are same as PDCCH monitoring occasions for *SIB1* where the mapping between PDCCH monitoring occasions and SSBs is specified in TS 38.213[13]. If *searchSpaceOtherSystemInformation* is not set to zero, PDCCH monitoring occasions for SI message are determined based on search space indicated by *searchSpaceOtherSystemInformation*. PDCCH monitoring occasions for SI message which are not overlapping with UL symbols (determined according to *tdd-UL-DL-ConfigurationCommon*) are sequentially numbered from one in the SI window. The $[x \times N + K]^{\text{th}}$ PDCCH monitoring occasion (s) for SI message in SI-window corresponds to the $K^{\text{th}}$ transmitted SSB, where $x = 0, 1, \dots, X-1$ , $K = 1, 2, \dots, N$ , $N$ is the number of actual transmitted SSBs determined according to *ssb-PositionsInBurst* in *SIB1* and $X$ is equal to $\text{CEIL}(\text{number of PDCCH monitoring occasions in SI-window}/N)$ . The actual transmitted SSBs are sequentially numbered from one in ascending order of their SSB indexes. The UE assumes that, in the SI window, PDCCH for an SI message is transmitted in at least one PDCCH monitoring occasion corresponding to each transmitted SSB and thus the selection of SSB for the reception SI messages is up to UE implementation. + +When acquiring an SI message, the UE shall: + +- 1> determine the start of the SI-window for the concerned SI message as follows: + - 2> if the concerned SI message is configured in the *schedulingInfoList*: + +- 3> for the concerned SI message, determine the number $n$ which corresponds to the order of entry in the list of SI messages configured by *schedulingInfoList* in *si-SchedulingInfo* in *SIB1*; + - 3> determine the integer value $x = (n - 1) \times w$ , where $w$ is the *si-WindowLength*; + - 3> the SI-window starts at the slot # $a$ , where $a = x \bmod N$ , in the radio frame for which $\text{SFN} \bmod T = \text{FLOOR}(x/N)$ , where $T$ is the *si-Periodicity* of the concerned SI message and $N$ is the number of slots in a radio frame as specified in TS 38.213 [13]; + - 2> else if the concerned SI message is configured in the *schedulingInfoList2*; + - 3> determine the integer value $x = (\text{si-WindowPosition} - 1) \times w$ , where $w$ is the *si-WindowLength*; + - 3> the SI-window starts at the slot # $a$ , where $a = x \bmod N$ , in the radio frame for which $\text{SFN} \bmod T = \text{FLOOR}(x/N)$ , where $T$ is the *si-Periodicity* of the concerned SI message and $N$ is the number of slots in a radio frame as specified in TS 38.213 [13]; + - 2> else if the concerned SI message is configured in the *posSchedulingInfoList* and *offsetToSI-Used* is not configured: + - 3> create a concatenated list of SI messages by appending the *posSchedulingInfoList* in *posSI-SchedulingInfo* in *SIB1* to *schedulingInfoList* in *si-SchedulingInfo* in *SIB1*; + - 3> for the concerned SI message, determine the number $n$ which corresponds to the order of entry in the concatenated list; + - 3> determine the integer value $x = (n - 1) \times w$ , where $w$ is the *si-WindowLength*; + - 3> the SI-window starts at the slot # $a$ , where $a = x \bmod N$ , in the radio frame for which $\text{SFN} \bmod T = \text{FLOOR}(x/N)$ , where $T$ is the *posSI-Periodicity* of the concerned SI message and $N$ is the number of slots in a radio frame as specified in TS 38.213 [13]; + - 2> else if the concerned SI message is configured by the *posSchedulingInfoList* and *offsetToSI-Used* is configured: + - 3> determine the number $m$ which corresponds to the number of SI messages with an associated *si-Periodicity* of 8 radio frames (80 ms), configured by *schedulingInfoList* in *SIB1*; + - 3> for the concerned SI message, determine the number $n$ which corresponds to the order of entry in the list of SI messages configured by *posSchedulingInfoList* in *SIB1*; + - 3> determine the integer value $x = m \times w + (n - 1) \times w$ , where $w$ is the *si-WindowLength*; + - 3> the SI-window starts at the slot # $a$ , where $a = x \bmod N$ , in the radio frame for which $\text{SFN} \bmod T = \text{FLOOR}(x/N) + 8$ , where $T$ is the *posSI-Periodicity* of the concerned SI message and $N$ is the number of slots in a radio frame as specified in TS 38.213 [13]; +- 1> receive the PDCCH containing the scheduling RNTI, i.e. SI-RNTI in the PDCCH monitoring occasion(s) for SI message acquisition, from the start of the SI-window and continue until the end of the SI-window whose absolute length in time is given by *si-WindowLength*, or until the SI message was received; + +- 1> if the SI message was not received by the end of the SI-window, repeat reception at the next SI-window occasion for the concerned SI message in the current modification period; + - 1> if all the SIB(s) and/or posSIB(s) requested in *DedicatedSIBRequest* message have been acquired: + - 2> stop timer T350, if running; +- NOTE 1: The UE is only required to acquire broadcasted SI message if the UE can acquire it without disrupting unicast or MBS multicast data reception, i.e. the broadcast and unicast/MBS multicast beams are quasi co-located. +- NOTE 2: The UE is not required to monitor PDCCH monitoring occasion(s) corresponding to each transmitted SSB in SI-window. +- NOTE 3: If the concerned SI message was not received in the current modification period, handling of SI message acquisition is left to UE implementation. +- NOTE 4: A UE in RRC\_CONNECTED may stop the PDCCH monitoring during the SI window for the concerned SI message when the requested SIB(s) are acquired. +- NOTE 5: A UE capable of NR sidelink communication/discovery and configured by upper layers to perform NR sidelink communication/discovery on a frequency, may acquire *SIB12* or *SystemInformationBlockType28* from a cell other than current serving cell (for RRC\_INACTIVE or RRC\_IDLE) or current PCell (for RRC\_CONNECTED), if *SIB12* of current serving cell (for RRC\_INACTIVE or RRC\_IDLE) or current PCell (for RRC\_CONNECTED) does not provide configuration for NR sidelink communication/discovery for the frequency, and if the other cell providing configuration for NR sidelink communication/discovery for the frequency meets the S-criteria as defined in TS 38.304 [20] or TS 36.304 [27]. +- 1> perform the actions for the acquired SI message as specified in clause 5.2.2.4. + +### 5.2.2.3.3 Request for on demand system information + +The UE shall, while SDT procedure is not ongoing: + +- 1> if *SIB1* includes *si-SchedulingInfo* containing *si-RequestConfigSUL-MSG1-Repetition* and criteria to select supplementary uplink as defined in TS 38.321[3], clause 5.1.1 is met and if criteria to apply MSG1 repetition as defined in TS 38.321[3], clause 5.1.1e for the concerned *si-RequestConfigSUL-MSG1-Repetition* is met: + - 2> trigger the lower layer to initiate the Random Access procedure on supplementary uplink in accordance with TS 38.321 [3] using the PRACH preamble(s) and PRACH resource(s) associated with the applicable MSG1 repetition number in *si-RequestConfigSUL-MSG1-Repetition* corresponding to the SI message(s) that the UE requires to operate within the cell, and for which *si-BroadcastStatus* is set to *notBroadcasting*; + - 2> if acknowledgement for SI request is received from lower layers: + - 3> acquire the requested SI message(s) as defined in clause 5.2.2.3.2, immediately; +- 1> else if the UE is a RedCap UE and if *initialUplinkBWP-RedCap* is configured in *UplinkConfigCommonSIB* and if *SIB1* includes *si-SchedulingInfo* containing *si-RequestConfigRedCap-MSG1-Repetition* and criteria to select normal uplink as defined in TS 38.321[3], clause 5.1.1 is met and if criteria to apply MSG1 repetition as defined in TS 38.321[3], clause 5.1.1e for the concerned *si-RequestConfigRedCap-MSG1-Repetition* is met: + +- 2> trigger the lower layer to initiate the Random Access procedure on normal uplink in accordance with TS 38.321 [3] using the PRACH preamble(s) and PRACH resource(s) associated with the applicable MSG1 repetition number in *si-RequestConfigRedCap-MSG1-Repetition* corresponding to the SI message(s) that the UE requires to operate within the cell, and for which *si-BroadcastStatus* is set to *notBroadcasting*; +- 2> if acknowledgement for SI request is received from lower layers: + - 3> acquire the requested SI message(s) as defined in clause 5.2.2.3.2, immediately; +- 1> else if *SIB1* includes *si-SchedulingInfo* containing *si-RequestConfigSUL* and criteria to select supplementary uplink as defined in TS 38.321[3], clause 5.1.1 is met: + - 2> trigger the lower layer to initiate the Random Access procedure on supplementary uplink in accordance with TS 38.321 [3] using the PRACH preamble(s) and PRACH resource(s) in *si-RequestConfigSUL* corresponding to the SI message(s) that the UE requires to operate within the cell, and for which *si-BroadcastStatus* is set to *notBroadcasting*; + - 2> if acknowledgement for SI request is received from lower layers: + - 3> acquire the requested SI message(s) as defined in clause 5.2.2.3.2, immediately; +- 1> else if the UE is an (e)RedCap UE and if *initialUplinkBWP-RedCap* is configured in *UplinkConfigCommonSIB* and if *SIB1* includes *si-SchedulingInfo* containing *si-RequestConfigRedCap* and criteria to select normal uplink as defined in TS 38.321[3], clause 5.1.1 is met: + - 2> trigger the lower layer to initiate the Random Access procedure on normal uplink in accordance with TS 38.321 [3] using the PRACH preamble(s) and PRACH resource(s) in *si-RequestConfigRedCap* corresponding to the SI message(s) that the UE requires to operate within the cell, and for which *si-BroadcastStatus* is set to *notBroadcasting*; + - 2> if acknowledgement for SI request is received from lower layers: + - 3> acquire the requested SI message(s) as defined in clause 5.2.2.3.2, immediately; +- 1> else: + - 2> if the UE is not a RedCap UE and if *SIB1* includes *si-SchedulingInfo* containing *si-RequestConfigMSG1-Repetition* and criteria to select normal uplink and to apply MSG1 repetition as defined in TS 38.321[3], clause 5.1.1e for the concerned *si-RequestConfigMSG1-Repetition* are met; or + - 2> if the UE is a RedCap UE and if *initialUplinkBWP-RedCap* is not configured in *UplinkConfigCommonSIB* and if *SIB1* includes *si-SchedulingInfo* containing *si-RequestConfigMSG1-Repetition* and criteria to select normal uplink and to apply MSG1 repetition as defined in TS 38.321[3], clause 5.1.1e for the concerned *si-RequestConfigMSG1-Repetition* are met: + - 3> trigger the lower layer to initiate the Random Access procedure on normal uplink in accordance with TS 38.321 [3] using the PRACH preamble(s) and PRACH resource(s) associated with the applicable MSG1 repetition number in corresponding to the SI message(s) that the UE requires to operate within the cell, and for which *si-BroadcastStatus* is set to *notBroadcasting*; + - 3> if acknowledgement for SI request is received from lower layers: + +- 4> acquire the requested SI message(s) as defined in clause 5.2.2.3.2, immediately; + - 2> else if the UE is neither a RedCap nor an eRedCap UE and if *SIB1* includes *si-SchedulingInfo* containing *si-RequestConfig* and criteria to select normal uplink as defined in TS 38.321[3], clause 5.1.1 is met; or + - 2> if the UE is an (e)RedCap UE and if *initialUplinkBWP-RedCap* is not configured in *UplinkConfigCommonSIB* and if *SIB1* includes *si-SchedulingInfo* containing *si-RequestConfig* and criteria to select normal uplink as defined in TS 38.321[3], clause 5.1.1 is met: + - 3> trigger the lower layer to initiate the Random Access procedure on normal uplink in accordance with TS 38.321 [3] using the PRACH preamble(s) and PRACH resource(s) in *si-RequestConfig* corresponding to the SI message(s) that the UE requires to operate within the cell, and for which *si-BroadcastStatus* is set to *notBroadcasting*; + - 3> if acknowledgement for SI request is received from lower layers: + - 4> acquire the requested SI message(s) as defined in clause 5.2.2.3.2, immediately; + - 2> else: + - 3> apply the default L1 parameter values as specified in corresponding physical layer specifications except for the parameters for which values are provided in *SIB1*; + - 3> apply the default MAC Cell Group configuration as specified in 9.2.2; + - 3> apply the *timeAlignmentTimerCommon* included in *SIB1*; + - 3> apply the CCCH configuration as specified in 9.1.1.2; + - 3> initiate transmission of the *RRCSystemInfoRequest* message with *rrcSystemInfoRequest* in accordance with 5.2.2.3.4; + - 3> if acknowledgement for *RRCSystemInfoRequest* message with *rrcSystemInfoRequest* is received from lower layers: + - 4> acquire the requested SI message(s) as defined in clause 5.2.2.3.2, immediately; +- 1> if cell reselection occurs while waiting for the acknowledgment for SI request from lower layers: + - 2> reset MAC; + - 2> if SI request is based on *RRCSystemInfoRequest* message with *rrcSystemInfoRequest*: + - 3> release RLC entity for SRB0. + +NOTE: After RACH failure for SI request it is up to UE implementation when to retry the SI request. + +### 5.2.2.3.3a Request for on demand positioning system information + +The UE shall, while SDT procedure is not ongoing: + +- 1> if *SIB1* includes *si-SchedulingInfo* containing *posSI-RequestConfigSUL-MSG1-Repetition* and criteria to select supplementary uplink as defined in TS 38.321[3], clause 5.1.1 is met and if criteria to apply MSG1 repetition as defined in TS 38.321[3], clause 5.1.1e for the concerned *posSI-RequestConfigSUL-MSG1-Repetition* is met: + - 2> trigger the lower layer to initiate the Random Access procedure on supplementary uplink in accordance with TS 38.321 [3] using the PRACH preamble(s) and PRACH resource(s) associated with the applicable MSG1 repetition number in *posSI-RequestConfigSUL-MSG1-Repetition* corresponding to the SI message(s) that the UE requires to operate within the cell, and for which *si-BroadcastStatus* is set to *notBroadcasting*; + - 2> if acknowledgement for SI request is received from lower layers: + - 3> acquire the requested SI message(s) as defined in clause 5.2.2.3.2, immediately; +- 1> else if the UE is a RedCap UE and if *initialUplinkBWP-RedCap* is configured in *UplinkConfigCommonSIB* and if *SIB1* includes *si-SchedulingInfo* containing *posSI-RequestConfigRedCap-MSG1-Repetition* and criteria to select normal uplink as defined in TS 38.321[3], clause 5.1.1 is met and if criteria to apply MSG1 repetition as defined in TS 38.321[3], clause 5.1.1e for the concerned *posSI-RequestConfigRedCap-MSG1-Repetition* is met: + - 2> trigger the lower layer to initiate the Random Access procedure on normal uplink in accordance with TS 38.321 [3] using the PRACH preamble(s) and PRACH resource(s) associated with the applicable MSG1 repetition number in *posSI-RequestConfigRedCap-MSG1-Repetition* corresponding to the SI message(s) that the UE requires to operate within the cell, and for which *si-BroadcastStatus* is set to *notBroadcasting*; + - 2> if acknowledgement for SI request is received from lower layers: + - 3> acquire the requested SI message(s) as defined in clause 5.2.2.3.2, immediately; +- 1> else if *SIB1* includes *posSI-SchedulingInfo* containing *posSI-RequestConfigSUL* and criteria to select supplementary uplink as defined in TS 38.321[3], clause 5.1.1 is met: + - 2> trigger the lower layer to initiate the Random Access procedure on supplementary uplink in accordance with TS 38.321 [3] using the PRACH preamble(s) and PRACH resource(s) in *posSI-RequestConfigSUL* corresponding to the SI message(s) that the UE upper layers require for positioning operations, and for which *posSI-BroadcastStatus* is set to *notBroadcasting*; + - 2> if acknowledgement for SI request is received from lower layers: + - 3> acquire the requested SI message(s) as defined in clause 5.2.2.3.2, immediately; +- 1> else if the UE is an (e)RedCap UE and if *initialUplinkBWP-RedCap* is configured in *UplinkConfigCommonSIB* and if *SIB1* includes *posSI-SchedulingInfo* containing *posSI-RequestConfigRedCap* and criteria to select normal uplink as defined in TS 38.321[3], clause 5.1.1 is met: + - 2> trigger the lower layer to initiate the Random Access procedure on normal uplink in accordance with TS 38.321 [3] using the PRACH preamble(s) and PRACH resource(s) in *posSI-RequestConfigRedCap* corresponding to the SI message(s) that the UE upper layers require for positioning operations, and for which *posSI-BroadcastStatus* is set to *notBroadcasting*; + +2> if acknowledgement for SI request is received from lower layers: + +3> acquire the requested SI message(s) as defined in clause 5.2.2.3.2, immediately; + +1> else: + +2> if the UE is not a RedCap UE and if *SIB1* includes *si-SchedulingInfo* containing *posSI-RequestConfigMSG1-Repetition* and criteria to select normal uplink and to apply MSG1 repetition as defined in TS 38.321[3], clause 5.1.1e for the concerned *posSI-RequestConfigMSG1-Repetition* are met; or + +2> if the UE is a RedCap UE and if *initialUplinkBWP-RedCap* is not configured in *UplinkConfigCommonSIB* and if *SIB1* includes *si-SchedulingInfo* containing *posSI-RequestConfigMSG1-Repetition* and criteria to select normal uplink and to apply MSG1 repetition as defined in TS 38.321[3], clause 5.1.1e for the concerned *posSI-RequestConfigMSG1-Repetition* are met: + +3> trigger the lower layer to initiate the Random Access procedure on normal uplink in accordance with TS 38.321 [3] using the PRACH preamble(s) and PRACH resource(s) associated with the applicable MSG1 repetition number in *posSI-RequestConfigMSG1-Repetition* corresponding to the SI message(s) that the UE requires to operate within the cell, and for which *si-BroadcastStatus* is set to *notBroadcasting*; + +3> if acknowledgement for SI request is received from lower layers: + +4> acquire the requested SI message(s) as defined in clause 5.2.2.3.2, immediately; + +2> else if the UE is not an (e)RedCap UE and if *SIB1* includes *posSI-SchedulingInfo* containing *posSI-RequestConfig* and criteria to select normal uplink as defined in TS 38.321[3], clause 5.1.1 is met; or + +2> if the UE is an (e)RedCap UE and if *initialUplinkBWP-RedCap* is not configured in *UplinkConfigCommonSIB* and if *SIB1* includes *posSI-SchedulingInfo* containing *posSI-RequestConfig* and criteria to select normal uplink as defined in TS 38.321[3], clause 5.1.1 is met: + +3> trigger the lower layer to initiate the Random Access procedure on normal uplink in accordance with TS 38.321 [3] using the PRACH preamble(s) and PRACH resource(s) in *posSI-RequestConfig* corresponding to the SI message(s) that the UE upper layers require for positioning operations , and for which *posSI-BroadcastStatus* is set to *notBroadcasting*; + +3> if acknowledgement for SI request is received from lower layers: + +4> acquire the requested SI message(s) as defined in clause 5.2.2.3.2, immediately; + +2> else: + +3> apply the default L1 parameter values as specified in corresponding physical layer specifications except for the parameters for which values are provided in *SIB1*; + +3> apply the default MAC Cell Group configuration as specified in 9.2.2; + +3> apply the *timeAlignmentTimerCommon* included in *SIB1*; + +3> apply the CCCH configuration as specified in 9.1.1.2; + +3> initiate transmission of the *RRCSystemInfoRequest* message with *rrcPosSystemInfoRequest* in accordance with 5.2.2.3.4; + +3> if acknowledgement for *RRCSystemInfoRequest* message with *rrcPosSystemInfoRequest* is received from lower layers: + +4> acquire the requested SI message(s) as defined in clause 5.2.2.3.2, immediately; + +1> if cell reselection occurs while waiting for the acknowledgment for SI request from lower layers: + +2> reset MAC; + +2> if SI request is based on *RRCSystemInfoRequest* message with *rrcPosSystemInfoRequest*: + +3> release RLC entity for SRB0. + +NOTE: After RACH failure for SI request it is up to UE implementation when to retry the SI request. + +#### 5.2.2.3.4 Actions related to transmission of *RRCSystemInfoRequest* message + +The UE shall set the contents of *RRCSystemInfoRequest* message as follows: + +1> if the procedure is triggered to request the required SI message(s) other than positioning: + +2> set the *requested-SI-List* to indicate the SI message(s) that the UE requires to operate within the cell, and for which *si-BroadcastStatus* is set to *notBroadcasting*; + +1> else if the procedure is triggered to request the required SI message(s) for positioning: + +2> set the *requestedPosSI-List* to indicate the SI message(s) that the UE upper layers require for positioning operations, and for which *posSI-BroadcastStatus* is set to *notBroadcasting*. + +The UE shall submit the *RRCSystemInfoRequest* message to lower layers for transmission. + +#### 5.2.2.3.5 Acquisition of SIB(s) or posSIB(s) in RRC\_CONNECTED + +The UE shall: + +1> if the UE is in RRC\_CONNECTED with an active BWP not configured with common search space with the field *searchSpaceOtherSystemInformation* and the UE has not stored a valid version of a SIB or posSIB, in accordance with clause 5.2.2.2.1, of one or several required SIB(s) or posSIB(s) in accordance with clause 5.2.2.1, or + +1> if the UE is in RRC\_CONNECTED and acting as a L2 U2N Remote UE and the UE has not stored a valid version of a SIB, in accordance with clause 5.2.2.2.1, of one or several required SIB(s) in accordance with clause 5.2.2.1: + +2> for the SI message(s) that, according to the *si-SchedulingInfo* or *posSI-SchedulingInfo* in the stored SIB1, contain at least one required SIB or requested posSIB: + +3> if *onDemandSIB-Request* is configured and timer T350 is not running: + +- 4> initiate transmission of the *DedicatedSIBRequest* message in accordance with 5.2.2.3.6; + - 4> start timer T350 with the timer value set to the *onDemandSIB-RequestProhibitTimer*; +- 1> else if the UE is in RRC\_CONNECTED with an active BWP configured with common search space with the field *searchSpaceOtherSystemInformation* and the UE has not stored a valid version of a SIB or posSIB, in accordance with clause 5.2.2.2.1, of one or several required SIB(s) or posSIB(s) in accordance with clause 5.2.2.1: + - 2> for the SI message(s) that, according to the *si-SchedulingInfo* in the stored SIB1, contain at least one required SIB and for which *si-BroadcastStatus* is set to *broadcasting*: + - 3> acquire the SI message(s) as defined in clause 5.2.2.3.2; + - 2> for the SI message(s) that, according to the *si-SchedulingInfo* in the stored SIB1, contain at least one required SIB and for which *si-BroadcastStatus* is set to *notBroadcasting*: + - 3> if *onDemandSIB-Request* is configured and timer T350 is not running: + - 4> initiate transmission of the *DedicatedSIBRequest* message in accordance with 5.2.2.3.6; + - 4> start timer T350 with the timer value set to the *onDemandSIB-RequestProhibitTimer*; + - 4> acquire the requested SI message(s) corresponding to the requested SIB(s) as defined in clause 5.2.2.3.2. + - 2> for the SI message(s) that, according to the *posSI-SchedulingInfo* in the stored SIB1, contain at least one requested posSIB and for which *posSI-BroadcastStatus* is set to *broadcasting*: + - 3> acquire the SI message(s) as defined in clause 5.2.2.3.2; + - 2> for the SI message(s) that, according to the *posSI-SchedulingInfo* in the stored SIB1, contain at least one requested posSIB and for which *posSI-BroadcastStatus* is set to *notBroadcasting*: + - 3> if *onDemandSIB-Request* is configured and timer T350 is not running: + - 4> initiate transmission of the *DedicatedSIBRequest* message in accordance with 5.2.2.3.6; + - 4> start timer T350 with the timer value set to the *onDemandSIB-RequestProhibitTimer*; + - 4> acquire the requested SI message(s) corresponding to the requested posSIB(s) as defined in clause 5.2.2.3.2. + +NOTE: UE may include on demand request for SIB and/or posSIB(s) in the same *DedicatedSIBRequest* message. + +#### 5.2.2.3.6 Actions related to transmission of *DedicatedSIBRequest* message + +The UE shall set the contents of *DedicatedSIBRequest* message as follows: + +- 1> if the procedure is triggered to request the required SIB(s): + - 2> include *requestedSIB-List* in the *onDemandSIB-RequestList* to indicate the requested SIB(s); +- 1> if the procedure is triggered to request the required posSIB(s): + - 2> include *requestedPosSIB-List* in the *onDemandSIB-RequestList* to indicate the requested posSIB(s). + +The UE shall submit the *DedicatedSIBRequest* message to lower layers for transmission. + +#### 5.2.2.4 Actions upon receipt of System Information + +##### 5.2.2.4.1 Actions upon reception of the *MIB* + +Upon receiving the *MIB* the UE shall: + +- 1> store the acquired *MIB*; +- 1> if the UE is in RRC\_IDLE or in RRC\_INACTIVE, or if the UE is in RRC\_CONNECTED while *T311* is running: + - 2> if the access is not for NTN or the UE is not capable of NTN or the UE is not capable of NES cell DTX/DRX; and + - 2> if the access is not for ATG or the UE is not capable of ATG; and + - 2> if the *cellBarred* in the acquired *MIB* is set to *barred*: + - 3> if the UE is an (e)RedCap UE and *ssb-SubcarrierOffset* indicates *SIB1* is transmitted in the cell (TS 38.213 [13]): + - 4> acquire the *SIB1*, which is scheduled as specified in TS 38.213 [13]; + - 3> consider the cell as barred in accordance with TS 38.304 [20]; + - 3> perform cell re-selection to other cells on the same frequency as the barred cell as specified in TS 38.304 [20]; + - 2> else: + - 3> apply the received *systemFrameNumber*, *pdcch-ConfigSIB1*, *subCarrierSpacingCommon*, *ssb-SubcarrierOffset* and *dmrs-TypeA-Position*. + +NOTE 1: A UE capable of NTN access should acquire *SIB1* to determine whether the cell is an NTN cell. + +NOTE 2: A UE capable of ATG access should acquire *SIB1* to determine whether the cell is an ATG cell. + +NOTE 3: A UE capable of NES cell DTX/DRX should acquire *SIB1* to determine the cell barring status when the *cellBarred* in *MIB* is set to *barred*. + +#### 5.2.2.4.2 Actions upon reception of the *SIB1* + +Upon receiving the *SIB1* the UE shall: + +- 1> store the acquired *SIB1*; +- 1> if the access is for NTN: + - 2> if the UE is in RRC\_IDLE or in RRC\_INACTIVE, or if the UE is in RRC\_CONNECTED while *T311* is running; and + - 2> if the *cellBarredNTN* in the acquired *SIB1* is set to *barred* or the *cellBarredNTN* is not included in the acquired *SIB1*: + - 3> consider the cell as barred in accordance with TS 38.304 [20]; + - 3> perform cell re-selection to other cells on the same frequency as the barred cell as specified in TS 38.304 [20], upon which the procedure ends; +- 1> if the access is for ATG: + - 2> if the UE is in RRC\_IDLE or in RRC\_INACTIVE, or if the UE is in RRC\_CONNECTED while *T311* is running; and + - 2> if the *cellBarredNTN* in the acquired *SIB1* is set to *barred* or the *cellBarredNTN* is not included in the acquired *SIB1*: + - 3> consider the cell as barred in accordance with TS 38.304 [20]; + - 3> perform cell re-selection to other cells on the same frequency as the barred cell as specified in TS 38.304 [20]; +- 1> if the UE is a RedCap UE and it is in RRC\_IDLE or in RRC\_INACTIVE, or if the RedCap UE is in RRC\_CONNECTED while *T311* is running: + - 2> if *intraFreqReselectionRedCap* is not present in *SIB1*: + - 3> consider the cell as barred in accordance with TS 38.304 [20]; + - 3> perform barring as if *intraFreqReselectionRedCap* is set to allowed, upon which the procedure ends; + - 2> else: + - 3> if the *cellBarredRedCap1Rx* is present in the acquired *SIB1* and is set to *barred* and the UE is equipped with 1 Rx branch; or + - 3> if the *cellBarredRedCap2Rx* is present in the acquired *SIB1* and is set to *barred* and the UE is equipped with 2 Rx branches; or + - 3> if the *halfDuplexRedCapAllowed* is not present in the acquired *SIB1* and the UE supports only half-duplex FDD operation: + - 4> consider the cell as barred in accordance with TS 38.304 [20]; + - 4> perform barring based on *intraFreqReselectionRedCap* as specified in TS 38.304 [20], upon which the procedure ends; + +- 1> if the UE supports NES cell DTX/DRX and it is in RRC\_IDLE or in RRC\_INACTIVE, or if the UE supporting NES cell DTX/DRX is in RRC\_CONNECTED while *T311* is running: + - 2> if *cellBarred* in the acquired *MIB* is set to *barred*: + - 3> if *cellBarredNES* is absent in the acquired *SIB1*: + - 4> consider the cell as barred in accordance with TS 38.304 [20]; + - 4> perform cell re-selection to other cells on the same frequency as the barred cell as specified in TS 38.304 [20]; +- 1> if the UE is an eRedCap UE and it is in RRC\_IDLE or in RRC\_INACTIVE, or if the eRedCap UE is in RRC\_CONNECTED while *T311* is running: + - 2> if *intraFreqReselection-eRedCap* is not present in *SIB1*: + - 3> consider the cell as barred in accordance with TS 38.304 [20]; + - 3> perform barring as if *intraFreqReselection-eRedCap* is set to allowed upon which the procedure ends; + - 2> else: + - 3> if the *cellBarred-eRedCap1Rx* is present in the acquired *SIB1* and is set to *barred* and the UE is equipped with 1 Rx branch; or + - 3> if the *cellBarred-eRedCap2Rx* is present in the acquired *SIB1* and is set to *barred* and the UE is equipped with 2 Rx branches; or + - 3> if the *halfDuplexRedCapAllowed* is not present in the acquired *SIB1* and the UE supports only half-duplex FDD operation: + - 4> consider the cell as barred in accordance with TS 38.304 [20]; + - 4> perform barring based on *intraFreqReselection-eRedCap* as specified in TS 38.304 [20] upon which the procedure ends; +- 1> if the *cellAccessRelatedInfo* contains an entry of a selected SNPN or PLMN and in case of PLMN the UE is either allowed or instructed to access the PLMN via a cell for which at least one CAG ID is broadcast: + - 2> in the remainder of the procedures use *npn-IdentityList*, *trackingAreaCode*, and *cellIdentity* for the cell as received in the corresponding entry of *npn-IdentityInfoList* containing the selected PLMN or SNPN; +- 1> else if the *cellAccessRelatedInfo* contains an entry with the *PLMN-Identity* of the selected PLMN: + - 2> in the remainder of the procedures use *plmn-IdentityList*, *trackingAreaCode*, *trackingAreaList*, and *cellIdentity* for the cell as received in the corresponding *PLMN-IdentityInfo* containing the selected PLMN; +- 1> if the UE in RRC\_INACTIVE is configured for feature(s) that it does not support in current serving cell: + +2> not use the corresponding configuration in current serving cell; + +NOTE 0: The requirement above applies only to UE that indicates different support of UE capabilities for TN and NTN. + +1> if in RRC\_CONNECTED while T311 is not running: + +2> disregard the *frequencyBandList*, if received, while in RRC\_CONNECTED; + +2> forward the *cellIdentity* to upper layers; + +2> forward the *trackingAreaCode* to upper layers, if included; + +2> forward the *trackingAreaList* to upper layers, if included; + +2> forward the received *posSIB-MappingInfo* to upper layers, if included; + +2> apply the configuration included in the *servingCellConfigCommon*; + +2> if the UE has a stored valid version of a SIB or posSIB, in accordance with clause 5.2.2.2.1, that the UE requires to operate within the cell in accordance with clause 5.2.2.1: + +3> use the stored version of the required SIB or posSIB; + +2> else: + +3> acquire the required SIB or posSIB requested by upper layer as defined in clause 5.2.2.3.5; + +NOTE 1: Void. + +1> else: + +2> if the UE supports one or more of the frequency bands indicated in the *frequencyBandList* or *frequencyBandListAerial* for downlink for TDD, or one or more of the frequency bands indicated in the *frequencyBandList* or *frequencyBandListAerial* for uplink for FDD, and they are not downlink only bands, and + +2> if the UE is IAB-MT or supports at least one *additionalSpectrumEmission* in the *nr-NS-PmaxList* or *nr-NS-PmaxListAerial* for a supported band in the downlink for TDD, or a supported band in uplink for FDD, and + +2> if the UE supports an uplink channel bandwidth with a maximum transmission bandwidth configuration (see TS 38.101-1 [15], TS 38.101-2 [39], and TS 38.101-5 [75]) which + +- is smaller than or equal to the *carrierBandwidth* (indicated in *uplinkConfigCommon* for the SCS of the initial uplink BWP or, for (e)RedCap UE, of the (e)RedCap-specific initial uplink BWP if configured), and which +- is wider than or equal to the bandwidth of the initial uplink BWP or, for (e)RedCap UE, of the (e)RedCap-specific initial uplink BWP if configured, and + +- 2> if the UE supports a downlink channel bandwidth with a maximum transmission bandwidth configuration (see TS 38.101-1 [15], TS 38.101-2 [39], and TS 38.101-5 [75]) which + - is smaller than or equal to the *carrierBandwidth* (indicated in *downlinkConfigCommon* for the SCS of the initial downlink BWP or, for (e)RedCap UE, of the (e)RedCap-specific initial downlink BWP if configured), and which + - is wider than or equal to the bandwidth of the initial downlink BWP or, for (e)RedCap UE, of the (e)RedCap-specific initial downlink BWP if configured, and +- 2> if *frequencyShift7p5khz* is present and the UE supports corresponding 7.5kHz frequency shift on this band; or *frequencyShift7p5khz* is not present, and +- 2> if the UE is not a RedCap UE, or if the UE is a RedCap UE and *halfDuplexRedCapAllowed* is present, or if the UE is a RedCap UE and the RedCap UE supports full-duplex FDD operation on this band: + - 3> if neither *trackingAreaCode* nor *trackingAreaList* is provided for the selected PLMN nor the registered PLMN nor PLMN of the equivalent PLMN list: + - 4> consider the cell as barred in accordance with TS 38.304 [20]; + - 4> perform cell re-selection to other cells on the same frequency as the barred cell as specified in TS 38.304 [20]; + - 3> else if UE is IAB-MT and if *iab-Support* is not provided for the selected PLMN nor the registered PLMN nor PLMN of the equivalent PLMN list nor the selected SNPN nor the registered SNPN nor SNPN of the equivalent SNPN list: + - 4> consider the cell as barred in accordance with TS 38.304 [20]; + - 3> else if UE is NCR-MT and if *ncr-Support* is not provided: + - 4> consider the cell as barred in accordance with TS 38.304 [20]; + - 3> else if UE is a mobile IAB-MT and if *mobileIAB-Support* is not provided for the selected PLMN nor the registered PLMN nor PLMN of the equivalent PLMN list nor the selected SNPN nor the registered SNPN nor SNPN of the equivalent SNPN list: + - 4> consider the cell as barred in accordance with TS 38.304 [20]; + +*Editor's Note: FFS whether a cell can be barred for a mobile IAB-MT.* + +- 3> else: + - 4> apply a supported uplink channel bandwidth with a maximum transmission bandwidth which + - is contained within the *carrierBandwidth* indicated in *uplinkConfigCommon* for the SCS of the initial uplink BWP or, for (e)RedCap UEs, (e)RedCap-specific initial uplink BWP, if configured, and which + - is wider than or equal to the bandwidth of the initial BWP for the uplink or, for a (e)RedCap UE, of the (e)RedCap-specific initial uplink BWP if configured; + - 4> apply a supported downlink channel bandwidth with a maximum transmission bandwidth which + +- is contained within the *carrierBandwidth* indicated in *downlinkConfigCommon* for the SCS of the initial downlink BWP or, for (e)RedCap UEs, (e)RedCap-specific initial downlink BWP, if configured, and which + - is wider than or equal to the bandwidth of the initial BWP for the downlink or, for a (e)RedCap UE, of the (e)RedCap-specific initial downlink BWP if configured; +- 4> if the UE is aerial UE and it supports at least one frequency band in the *frequencyBandListAerial*, for FDD from *frequencyBandListAerial* for uplink, or for TDD from *frequencyBandListAerial* for downlink, for which the UE supports at least one of the *additionalSpectrumEmission* values in *nr-NS-PmaxListAerial*, if present: +- 5> select the first frequency band in the *frequencyBandListAerial*, for FDD from *frequencyBandListAerial* for uplink, or for TDD from *frequencyBandListAerial* for downlink, which the UE supports and for which the UE supports at least one of the *additionalSpectrumEmission* values in *nr-NS-PmaxListAerial*; +- 4> else: +- 5> select the first frequency band in the *frequencyBandList*, for FDD from *frequencyBandList* for uplink, or for TDD from *frequencyBandList* for downlink, which the UE supports and for which the UE supports at least one of the *additionalSpectrumEmission* values in *nr-NS-PmaxList*, if present, and for RedCap UEs if the *halfDuplexRedCapAllowed* is not present, for which the UE supports full-duplex FDD operation; +- 4> forward the *cellIdentity* to upper layers; +- 4> forward the *trackingAreaCode* to upper layers; +- 4> forward the *trackingAreaList* to upper layers, if included; +- 4> forward the received *posSIB-MappingInfo* to upper layers, if included; +- 4> forward the PLMN identity or SNPN identity or PNI-NPN identity to upper layers; +- 4> if in RRC\_INACTIVE and the forwarded information does not trigger message transmission by upper layers: +- 5> if the serving cell does not belong to the configured *ran-NotificationAreaInfo*: + - 6> initiate an RNA update as specified in 5.3.13.8; - 5> if configured to receive MBS multicast in RRC\_INACTIVE and not indicated to stop monitoring G-RNTI for at least one MBS multicast session: + - 6> if SIB24 is not scheduled in SIB1 in the cell after cell selection or cell reselection: + - 7> initiate an RRC connection resume procedure for multicast reception as specified in 5.3.13.1d; +- 4> forward the *ims-EmergencySupport* to upper layers, if present; + +- 4> forward the *eCallOverIMS-Support* to upper layers, if present; +- 4> forward the *UAC-AccessCategory1-SelectionAssistanceInfo* or *UAC-AC1-SelectAssistInfo* for the selected PLMN/SNPN to upper layers, if present and set to *a*, *b* or *c*; +- 4> if the UE is in SNPN access mode: + - 5> forward the *imsEmergencySupportForSNPN* indicators with the corresponding SNPN identities to upper layers, if present; +- 4> apply the configuration included in the *servingCellConfigCommon*; +- 4> apply the specified PCCH configuration defined in 9.1.1.3; +- 4> if the UE has a stored valid version of a SIB, in accordance with clause 5.2.2.2.1, that the UE requires to operate within the cell in accordance with clause 5.2.2.1: + - 5> use the stored version of the required SIB; +- 4> if the UE has not stored a valid version of a SIB, in accordance with clause 5.2.2.2.1, of one or several required SIB(s), in accordance with clause 5.2.2.1: + - 5> for the SI message(s) that, according to the *si-SchedulingInfo*, contain at least one required SIB and for which *si-BroadcastStatus* is set to broadcasting: + - 6> acquire the SI message(s) as defined in clause 5.2.2.3.2; + - 5> for the SI message(s) that, according to the *si-SchedulingInfo*, contain at least one required SIB and for which *si-BroadcastStatus* is set to *notBroadcasting*: + - 6> trigger a request to acquire the SI message(s) as defined in clause 5.2.2.3.3; +- 4> if the UE has a stored valid version of a posSIB, in accordance with clause 5.2.2.2.1, of one or several required posSIB(s), in accordance with clause 5.2.2.1: + - 5> use the stored version of the required posSIB; +- 4> if the UE has not stored a valid version of a posSIB, in accordance with clause 5.2.2.2.1, of one or several posSIB(s) in accordance with clause 5.2.2.1: + - 5> for the SI message(s) that, according to the *posSI-SchedulingInfo*, contain at least one requested posSIB and for which *posSI-BroadcastStatus* is set to *broadcasting*: + - 6> acquire the SI message(s) as defined in clause 5.2.2.3.2; + - 5> for the SI message(s) that, according to the *posSI-SchedulingInfo*, contain at least one requested posSIB for which *posSI-BroadcastStatus* is set to *notBroadcasting*: + - 6> trigger a request to acquire the SI message(s) as defined in clause 5.2.2.3.3a; + +- 4> if the UE is aerial UE and it supports at least one *additionalSpectrumEmission* values in *nr-NS-PmaxListAerial* within *frequencyBandListAerial* in *uplinkConfigCommon* for FDD or in *downlinkConfigCommon* for TDD: + - 5> apply the first listed *additionalSpectrumEmission* which it supports among the values included in *nr-NS-PmaxListAerial* within *frequencyBandListAerial* in *uplinkConfigCommon* for FDD or in *downlinkConfigCommon* for TDD; +- 4> else: + - 5> apply the first listed *additionalSpectrumEmission* which it supports among the values included in *nr-NS-PmaxList* within *frequencyBandList* in *uplinkConfigCommon* for FDD or in *downlinkConfigCommon* for TDD; +- 4> if the *additionalPmax* is present in the same entry of the selected *additionalSpectrumEmission* within *nr-NS-PmaxList* or *nr-NS-PmaxListAerial*: + - 5> apply the *additionalPmax* for UL; +- 4> else: + - 5> apply the *p-Max* in *uplinkConfigCommon* for UL; +- 4> if *supplementaryUplink* is present in *servingCellConfigCommon*; and +- 4> if the UE supports one or more of the frequency bands indicated in the *frequencyBandList* for the *supplementaryUplink*; and +- 4> if the UE supports at least one *additionalSpectrumEmission* in the *nr-NS-PmaxList* for a supported supplementary uplink band; and +- 4> if the UE is not a RedCap UE, or if the UE is a RedCap UE and *halfDuplexRedCapAllowed* is present, or if the UE is a RedCap UE and the RedCap UE supports full-duplex FDD operation on the frequency bands indicated in the *frequencyBandList* for the *supplementaryUplink*; and +- 4> if the UE supports an uplink channel bandwidth with a maximum transmission bandwidth configuration (see TS 38.101-1 [15] and TS 38.101-2 [39]) which + - is smaller than or equal to the *carrierBandwidth* (indicated in *supplementaryUplink* for the SCS of the initial uplink BWP), and which + - is wider than or equal to the bandwidth of the initial uplink BWP of the SUL: +- 5> consider supplementary uplink as configured in the serving cell; +- 5> select the first frequency band in the *frequencyBandList* for the *supplementaryUplink* which the UE supports and for which the UE supports at least one of the *additionalSpectrumEmission* values in *nr-NS-PmaxList*, if present, and for RedCap UEs if the *halfDuplexRedCapAllowed* is not present, for which the UE supports full-duplex FDD operation; +- 5> apply a supported supplementary uplink channel bandwidth with a maximum transmission bandwidth which + - is contained within the *carrierBandwidth* (indicated in *supplementaryUplink* for the SCS of the initial uplink BWP), and which + +- is wider than or equal to the bandwidth of the initial BWP of the SUL; + +5> apply the first listed *additionalSpectrumEmission* which it supports among the values included in *nr-NS-PmaxList* within *frequencyBandList* for the *supplementaryUplink*; + +5> if the *additionalPmax* is present in the same entry of the selected *additionalSpectrumEmission* within *nr-NS-PmaxList* for the *supplementaryUplink*: + +6> apply the *additionalPmax* in *supplementaryUplink* for SUL; + +5> else: + +6> apply the *p-Max* in *supplementaryUplink* for SUL; + +NOTE 2: For an out of coverage L2 U2N Remote UE in RRC\_IDLE or RRC\_INACTIVE receiving SIB1 from its connected L2 U2N Relay UE, it is up to Remote UE implementation whether to consider and apply the following parameters: *frequencyBandList*, *carrierBandwidth*, *frequencyShift7p5khz*, frequency band, channel bandwidth, the configuration included in the *servingCellConfigCommon*, the specified PCCH configuration, *additionalSpectrumEmission*, *additionalPmax*, and *p-Max*. + +2> else: + +3> consider the cell as barred in accordance with TS 38.304 [20]; and + +3> perform barring as if *intraFreqReselection*, or *intraFreqReselectionRedCap* for RedCap UEs, or *intraFreqReselection-eRedCap* for eRedCap UEs, is set to *notAllowed*; + +#### 5.2.2.4.3 Actions upon reception of SIB2 + +Upon receiving SIB2, the UE shall: + +1> if in RRC\_IDLE or in RRC\_INACTIVE or in RRC\_CONNECTED while T311 is running: + +2> if, for the entry in *frequencyBandList* with the same index as the frequency band selected in clause 5.2.2.4.2, the UE supports at least one *additionalSpectrumEmission* in the *nr-NS-PmaxList* within the *frequencyBandList* or + +2> if, for the entry in *frequencyBandListAerial* with the same index as the frequency band selected in clause 5.2.2.4.2, the UE supports at least one *additionalSpectrumEmission* in the *nr-Ns-PmaxListAerial* within the *frequencyBandListAerial*: + +3> if the UE is aerial UE and it supports at least one *additionalSpectrumEmission* values in *nr-NS-PmaxListAerial* within the *frequencyBandListAerial*: + +4> apply the first listed *additionalSpectrumEmission* which it supports among the values included in *nr-NS-PmaxListAerial* within *frequencyBandListAerial*; + +3> else: + +4> apply the first listed *additionalSpectrumEmission* which it supports among the values included in *nr-NS-PmaxList* within *frequencyBandList*; + +- 3> if the *additionalPmax* is present in the same entry of the selected *additionalSpectrumEmission* within *nr-NS-PmaxList* or *nr-NS-PmaxListAerial*: + - 4> apply the *additionalPmax*; +- 3> else: + - 4> apply the *p-Max*; +- 3> if the UE selects a frequency band (from the procedure in clause 5.2.2.4.2) for the supplementary uplink: + - 4> if, for the entry in *frequencyBandListSUL* with the same index as the frequency band selected in clause 5.2.2.4.2, the UE supports at least one *additionalSpectrumEmission* in the *nr-NS-PmaxList* within the *frequencyBandListSUL*: + - 5> apply the first listed *additionalSpectrumEmission* which it supports among the values included in *nr-NS-PmaxList* within *frequencyBandListSUL*; + - 5> if the *additionalPmax* is present in the same entry of the selected *additionalSpectrumEmission* within *nr-NS-PmaxList*: + - 6> apply the *additionalPmax*; + - 5> else: + - 6> apply the *p-Max*; + - 4> else: + - 5> apply the *p-Max*. +- 2> else: + - 3> apply the *p-Max*; + +#### 5.2.2.4.4 Actions upon reception of *SIB3* + +No UE requirements related to the contents of this *SIB3* apply other than those specified elsewhere e.g. within procedures using the concerned system information, and/ or within the corresponding field descriptions. + +#### 5.2.2.4.5 Actions upon reception of *SIB4* + +Upon receiving *SIB4* the UE shall: + +- 1> if in *RRC\_IDLE*, or in *RRC\_INACTIVE* or in *RRC\_CONNECTED* while *T311* is running: + - 2> for each entry in the *interFreqCarrierFreqList*: + +- 3> if the UE is neither a RedCap nor an eRedCap UE; or +- 3> if the UE is a RedCap UE and the *interFreqCarrierFreqList-v1700* is absent; or +- 3> if the UE is an eRedCap UE and the *interFreqCarrierFreqList-v1800* is absent; or +- 3> if the UE is a RedCap UE and *redCapAccessAllowed* is present in *interFreqCarrierFreqList-v1700*; or +- 3> if the UE is an eRedCap UE and *eRedCapAccessAllowed* is present in *interFreqCarrierFreqList-v1800*: + - 4> select the first frequency band in the *frequencyBandList* (or for aerial UE *frequencyBandListAerial*), and *frequencyBandListSUL*, if present, which the UE supports and for which the UE supports at least one of the *additionalSpectrumEmission* values in *nr-NS-PmaxList* (or for aerial UE *nr-NS-PmaxListAerial*), if present: + - 4> if, the frequency band selected by the UE in *frequencyBandList* or *frequencyBandListAerial* to represent a non-serving NR carrier frequency is not a downlink only band: + - 5> if, for the selected frequency band, the UE supports at least one *additionalSpectrumEmission* in the *nr-NS-PmaxList* within the *frequencyBandList*; or + - 5> if, for the selected frequency band, the UE supports at least one *additionalSpectrumEmission* in the *nr-NS-PmaxListAerial* within the *frequencyBandListAerial*: + - 6> if the UE is aerial UE and it supports at least one *additionalSpectrumEmission* values in *nr-NS-PmaxListAerial* within the *frequencyBandListAerial*: + - 7> apply the first listed *additionalSpectrumEmission* which it supports among the values included in *nr-NS-PmaxListAerial* within *frequencyBandListAerial*; + - 6> else: + - 7> apply the first listed *additionalSpectrumEmission* which it supports among the values included in *nr-NS-PmaxList* within *frequencyBandList*; + - 6> if the *additionalPmax* is present in the same entry of the selected *additionalSpectrumEmission* within *nr-NS-PmaxList* or *nr-NS-PmaxListAerial*: + - 7> apply the *additionalPmax*; + - 6> else: + - 7> apply the *p-Max*; + - 6> if *frequencyBandListSUL* is present in SIB4 and, for the frequency band selected in *frequencyBandListSUL*, the UE supports at least one *additionalSpectrumEmission* in the *nr-NS-PmaxList* within *frequencyBandListSUL*: + - 7> apply the first listed *additionalSpectrumEmission* which it supports among the values included in *nr-NS-PmaxList* within *frequencyBandListSUL*; + +- 7> if the *additionalPmax* is present in the same entry of the selected *additionalSpectrumEmission* within *nr-NS-PmaxList*: + - 8> apply the *additionalPmax*; +- 7> else: + - 8> apply the *p-Max*; +- 6> else: + - 7> apply the *p-Max*; +- 5> else: + - 6> apply the *p-Max*; +- 1> if in RRC\_IDLE or RRC\_INACTIVE, and T331 is running: + - 2> perform the actions as specified in 5.7.8.1a; + +#### 5.2.2.4.6 Actions upon reception of *SIB5* + +No UE requirements related to the contents of this *SIB5* apply other than those specified elsewhere e.g. within procedures using the concerned system information, and/ or within the corresponding field descriptions. + +#### 5.2.2.4.7 Actions upon reception of *SIB6* + +Upon receiving the *SIB6* the UE shall: + +- 1> forward the received *warningType*, *messageIdentifier* and *serialNumber* to upper layers; + +#### 5.2.2.4.8 Actions upon reception of *SIB7* + +Upon receiving the *SIB7* the UE shall: + +- 1> if there is no current value for *messageIdentifier* and *serialNumber* for *SIB7*; or +- 1> if either the received value of *messageIdentifier* or of *serialNumber*, or of both *messageIdentifier* and *serialNumber* are different from the current values of *messageIdentifier* and *serialNumber* for *SIB7*: + - 2> use the received values of *messageIdentifier* and *serialNumber* for *SIB7* as the current values of *messageIdentifier* and *serialNumber* for *SIB7*; + - 2> discard any previously buffered *warningMessageSegment*; + +- 2> if all segments of a warning message have been received: + - 3> assemble the warning message from the received *warningMessageSegment(s)*; + - 3> forward the received warning message, *messageIdentifier*, *serialNumber* and *dataCodingScheme* to upper layers; + - 3> stop reception of *SIB7*; + - 3> discard the current values of *messageIdentifier* and *serialNumber* for *SIB7*; +- 2> else: + - 3> store the received *warningMessageSegment*; + - 3> continue reception of *SIB7*; +- 1> else if all segments of a warning message have been received: + - 2> assemble the warning message from the received *warningMessageSegment(s)*; + - 2> forward the received complete warning message, *messageIdentifier*, *serialNumber* and *dataCodingScheme* to upper layers; + - 2> stop reception of *SIB7*; + - 2> discard the current values of *messageIdentifier* and *serialNumber* for *SIB7*; +- 1> else: + - 2> store the received *warningMessageSegment*; + - 2> continue reception of *SIB7*; + +The UE should discard any stored *warningMessageSegment* and the current value of *messageIdentifier* and *serialNumber* for *SIB7* if the complete warning message has not been assembled within a period of 3 hours. + +#### 5.2.2.4.9 Actions upon reception of *SIB8* + +Upon receiving the *SIB8* the UE shall: + +- 1> if the *SIB8* contains a complete warning message and the complete geographical area coordinates (if any): + - 2> forward the received warning message, *messageIdentifier*, *serialNumber*, *dataCodingScheme* and the geographical area coordinates (if any) to upper layers; + - 2> continue reception of *SIB8*; + +- 1> else: + - 2> if the received values of *messageIdentifier* and *serialNumber* are the same (each value is the same) as a pair for which a warning message and the geographical area coordinates (if any) are currently being assembled: + - 3> store the received *warningMessageSegment*; + - 3> store the received *warningAreaCoordinatesSegment* (if any); + - 3> if all segments of a warning message and geographical area coordinates (if any) have been received: + - 4> assemble the warning message from the received *warningMessageSegment*; + - 4> assemble the geographical area coordinates from the received *warningAreaCoordinatesSegment* (if any); + - 4> forward the received warning message, *messageIdentifier*, *serialNumber*, *dataCodingScheme* and geographical area coordinates (if any) to upper layers; + - 4> stop assembling a warning message and geographical area coordinates (if any) for this *messageIdentifier* and *serialNumber* and delete all stored information held for it; + - 3> continue reception of *SIB8*; + - 2> else if the received values of *messageIdentifier* and/or *serialNumber* are not the same as any of the pairs for which a warning message is currently being assembled: + - 3> start assembling a warning message for this *messageIdentifier* and *serialNumber* pair; + - 3> start assembling the geographical area coordinates (if any) for this *messageIdentifier* and *serialNumber* pair; + - 3> store the received *warningMessageSegment*; + - 3> store the received *warningAreaCoordinatesSegment* (if any); + - 3> continue reception of *SIB8*; + +The UE should discard *warningMessageSegment* and *warningAreaCoordinatesSegment* (if any) and the associated values of *messageIdentifier* and *serialNumber* for *SIB8* if the complete warning message and the geographical area coordinates (if any) have not been assembled within a period of 3 hours. + +NOTE: The number of warning messages that a UE can re-assemble simultaneously is a function of UE implementation. + +#### 5.2.2.4.10 Actions upon reception of *SIB9* + +Upon receiving *SIB9* with *referenceTimeInfo*, the UE may perform the related actions except for the action of ignoring all further *referenceTimeInfo* received in *SIB9* as specified in clause 5.7.1.3. + +Upon receiving *SIB9* with *eventID-TSS*, the UE shall perform the related actions if requested by upper layers: + +- 1> if *VarEventID* has an entry with a *storedEventID* value: + - 2> if the *storedEventID* value within *VarEventID* is different from the *eventID-TSS* value received within *SIB9*: + - 3> consider that the content of *clockQualityDetailsLevel* may have changed; + - 3> notify upper layers that *clockQualityDetailsLevel* may have changed; + - 3> replace the *storedEventID* value within *VarEventID* with the *eventID-TSS* value received within *SIB9*; + - 3> replace the *storedGnbID* value within *VarGnbID* with the gNB identity value received within *SIB1*; + - 2> else: + - 3> if the *VarGnbID* has an entry with a *storedGnbID* value: + - 4> if the *storedGnbID* value within *VarGnbID* is different from the gNB identity value received within *SIB1*: + - 5> consider that the content of *clockQualityDetailsLevel* may have changed; + - 5> notify upper layers that *clockQualityDetailsLevel* may have changed; + - 5> replace the *storedGnbID* value within *VarGnbID* with the gNB identity value received within *SIB1*; + +NOTE: The UE should calculate the value of the gNB identity as the value of *gNB-ID-Length* leftmost bits of the 36-bit long *cellIdentity* in the first *PLMN-IdentityInfo* IE of *PLMN-IdentityInfoList* in *SIB1*. + +- 1> else: + - 2> add a new entry of *storedEventID* within the *VarEventID* with the *eventID-TSS* value received within *SIB9*; + - 2> add a new entry of *storedGnbID* within the *VarGnbID* with the gNB identity value received within *SIB1*; + - 2> notify upper layers that *clockQualityDetailsLevel* may have changed; + +#### 5.2.2.4.11 Actions upon reception of *SIB10* + +Upon receiving *SIB10*, the UE shall: + +- 1> Forward the *HRNN-list* entries with the corresponding PNI-NPN and SNPN identities to upper layers; + +#### 5.2.2.4.12 Actions upon reception of *SIB11* + +Upon receiving *SIB11*, the UE shall: + +- 1> if in RRC\_IDLE or RRC\_INACTIVE, and T331 is running: + - 2> perform the actions as specified in 5.7.8.1a; + +#### 5.2.2.4.13 Actions upon reception of *SIB12* + +Upon receiving *SIB12*, the UE shall: + +- 1> if the UE has stored at least one segment of *SIB12* and the value tag of *SIB12* has changed since a previous segment was stored: + - 2> discard all stored segments; +- 1> store the segment; +- 1> if all segments have been received: + - 2> assemble *SIB12-IEs* from the received segments; + - 2> if *sl-FreqInfoList/sl-FreqInfoListSizeExt* is included in *SIB12-IEs*: + - 3> if configured to receive NR sidelink communication: + - 4> use the resource pool(s) indicated by *sl-RxPool* for NR sidelink communication reception, as specified in 5.8.7; + - 3> if configured to transmit NR sidelink communication: + - 4> use the resource pool(s) indicated by *sl-TxPoolSelectedNormal*, or *sl-TxPoolExceptional* for NR sidelink communication transmission, as specified in 5.8.8; + - 4> perform CBR measurement on the transmission resource pool(s) indicated by *sl-TxPoolSelectedNormal* or *sl-TxPoolExceptional* for NR sidelink communication transmission, as specified in 5.5.3.1; + - 4> use the synchronization configuration parameters for NR sidelink communication on frequencies included in *sl-FreqInfoList/sl-FreqInfoListSizeExt*, as specified in 5.8.5; + - 3> if configured to receive NR sidelink discovery: + - 4> use the resource pool(s) indicated by *sl-DiscRxPool* or *sl-RxPool* for NR sidelink discovery reception, as specified in 5.8.13.2; + - 3> if configured to transmit NR sidelink discovery: + +4> if the UE is configured by upper layers to transmit NR sidelink L2 U2N relay discovery messages and *sl-L2U2N-Relay* is included in SIB12; or + +4> if the UE is configured by upper layers to transmit NR sidelink L3 U2N relay discovery messages and *sl-L3U2N-RelayDiscovery* is included in SIB12; or + +4> if the UE is configured by upper layers to transmit NR sidelink non-relay discovery messages and *sl-NonRelayDiscovery* is included in SIB12: + +5> use the resource pool(s) indicated by *sl-DiscTxPoolSelected*, *sl-TxPoolExceptional* or *sl-TxPoolSelectedNormal* for NR sidelink discovery transmission, as specified in 5.8.13.3; + +5> perform CBR measurement on the transmission resource pool(s) indicated by *sl-TxPoolSelectedNormal*, *sl-DiscTxPoolSelected* or *sl-TxPoolExceptional* for NR sidelink discovery transmission, as specified in 5.5.3.1; + +5> use the synchronization configuration parameters for NR sidelink discovery on frequencies included in *sl-FreqInfoList*, as specified in 5.8.5; + +2> if *sl-RadioBearerConfigList* or *sl-RLC-BearerConfigList* is included in *sl-ConfigCommonNR*: + +3> perform sidelink DRB addition/modification/release as specified in 5.8.9.1a.1/5.8.9.1a.2; + +3> if *sl-RLC-BearerConfigListSizeExt* is included in *SIB12-IEs*: + +4> perform additional sidelink RLC bearer addition/modification/release as specified in 5.8.9.1a.5/5.8.9.1a.6; + +2> if *sl-MeasConfigCommon* is included in *sl-ConfigCommonNR*: + +3> store the NR sidelink measurement configuration; + +2> if *sl-DRX-ConfigCommonGC-BC* is included in *SIB12-IEs*: + +3> store the NR sidelink DRX configuration and configure lower layers to perform sidelink DRX operation for groupcast and broadcast as specified in TS 38.321 [3]; + +1> if the UE is acting as L2 U2N Remote UE: + +2> if the *sl-TimersAndConstantsRemoteUE* is included in *SIB12*: + +3> use values for timers T300, T301 and T319 as included in the *sl-TimersAndConstantsRemoteUE* received in *SIB12*; + +2> else: + +3> use values for timers T300, T301 and T319 as included in the *ue-TimersAndConstants* received in *SIB1*; + +The UE should discard any stored segments for *SIB12* if the complete *SIB12* has not been assembled within a period of 3 hours. The UE shall discard any stored segments for *SIB12* upon cell (re-)selection. + +#### 5.2.2.4.14 Actions upon reception of *SIB13* + +Upon receiving *SIB13*, the UE shall perform the actions upon reception of *SystemInformationBlockType21* as specified in 5.2.2.28 in TS 36.331 [10]. + +#### 5.2.2.4.15 Actions upon reception of *SIB14* + +Upon receiving *SIB14*, the UE shall perform the actions upon reception of *SystemInformationBlockType26* as specified in 5.2.2.33 in TS 36.331 [10]. + +#### 5.2.2.4.16 Actions upon reception of *SIBpos* + +No UE requirements related to the contents of the *SIBpos* apply other than those specified elsewhere e.g. within TS 37.355 [49], and/or within the corresponding field descriptions. + +#### 5.2.2.4.17 Actions upon reception of *SIB15* + +Upon receiving *SIB15*, the UE shall: + +- 1> forward the applicable disaster roaming information for each PLMN sharing the cell to upper layers. + +#### 5.2.2.4.18 Actions upon reception of *SIB16* + +Upon receiving *SIB16* with cell reselection priorities for slicing, the UE shall perform the actions as specified in TS 38.304 [20]. + +#### 5.2.2.4.19 Actions upon reception of *SIB17* + +Upon receiving *SIB17*, the UE shall: + +- 1> if the UE has stored at least one segment of *SIB17* and the value tag of *SIB17* has changed since a previous segment was stored: + - 2> discard all stored segments; +- 1> store the segment; +- 1> if all segments have been received: + - 2> assemble *SIB17-IEs* from the received segments. + +The UE should discard any stored segments for *SIB17* if the complete *SIB17* has not been assembled within a period of 3 hours. The UE shall discard any stored segments for *SIB17* upon cell (re-) selection. + +#### 5.2.2.4.20 Actions upon reception of *SIB18* + +Upon receiving *SIB18*, the UE shall: + +1> forward the Group IDs for Network selection (GINs) in *SIB18* with the corresponding SNPN identities to upper layers; + +#### 5.2.2.4.21 Actions upon reception of *SIB19* + +Upon receiving *SIB19* in an NTN cell, the UE in RRC\_CONNECTED shall: + +- 1> start or restart T430 for serving cell with the timer value set to *ntn-UISyncValidityDuration* for the serving cell from the subframe indicated by *epochTime* for the serving cell; +- 1> if *SatSwitchWithReSync* and *t-Service* are included, and the UE supports hard satellite switch with resynchronization; + - 2> if *t-ServiceStart* is included and the UE supports soft satellite switch with resynchronization: + - 3> perform the satellite switch with resynchronization as specified in 5.7.19 between the time indicated by *t-ServiceStart* and the time indicated by *t-Service* for the serving cell. + - 2> else: + - 3> perform the satellite switch with resynchronization as specified in 5.7.19 at the time indicated by *t-Service* for the serving cell. + +NOTE: UE should attempt to re-acquire *SIB19* before the end of the duration indicated by *ntn-UISyncValidityDuration* and *epochTime* by UE implementation. + +#### 5.2.2.4.22 Actions upon reception of *SIB20* + +No UE requirements related to the contents of *SIB20* apply other than those specified elsewhere e.g. within procedures using the concerned system information, and/or within the corresponding field descriptions. + +#### 5.2.2.4.23 Actions upon reception of *SIB21* + +No UE requirements related to the contents of *SIB21* apply other than those specified elsewhere e.g. within procedures using the concerned system information, and/or within the corresponding field descriptions. + +#### 5.2.2.4.24 Actions upon reception of *SIB22* + +No UE requirements related to the contents of *SIB22* apply other than those specified elsewhere e.g. within procedures using the concerned system information, and/or within the corresponding field descriptions. + +#### 5.2.2.4.25 Actions upon reception of *SIB23* + +Upon receiving *SIB23*, the UE shall: + +- 1> if *sl-FreqInfoList* is included in *sl-PosConfigCommonNR*: + +- 2> if configured to receive sidelink control information for SL-PRS measurement: + - 3> use the resource pool(s) indicated by *sl-RxPool* and/or *sl-PRS-RxPool* for sidelink control information reception for SL-PRS , as specified in 5.8.18.2; +- 2> if configured to transmit SL-PRS: + - 3> use the resource pool(s) indicated by *sl-TxPoolSelectedNormal*, *sl-TxPoolExceptional*, *sl-PRS-TxPoolSelectedNormal* or *sl-PRS-TxPoolExceptional* for SL-PRS transmission, as specified in 5.8.18.3; + - 3> perform CBR measurement on the transmission resource pool(s) indicated by *sl-TxPoolSelectedNormal*, *sl-TxPoolExceptional*, *sl-PRS-TxPoolSelectedNormal* or *sl-PRS-TxPoolExceptional* for SL-PRS transmission, as specified in 5.5.3.1; + - 3> use the synchronization configuration parameters for NR sidelink positioning on frequencies included in *sl-FreqInfoList*, as specified in 5.8.5; + +The UE should discard any stored segments for *SIB23* if the complete *SIB23* has not been assembled within a period of 3 hours. The UE shall discard any stored segments for *SIB23* upon cell (re-)selection. + +#### 5.2.2.4.26 Actions upon reception of *SIB24* + +No UE requirements related to the contents of *SIB24* apply other than those specified elsewhere e.g., within procedures using the concerned system information, and/or within the corresponding field descriptions. + +#### 5.2.2.4.27 Actions upon reception of *SIB25* + +No UE requirements related to the contents of *SIB25* apply other than those specified elsewhere e.g. within procedures using the concerned system information, and/or within the corresponding field descriptions. + +#### 5.2.2.5 Essential system information missing + +The UE shall: + +- 1> if in RRC\_IDLE or in RRC\_INACTIVE or in RRC\_CONNECTED while T311 is running: + - 2> if the UE is unable to acquire the *MIB*: + - 3> consider the cell as barred in accordance with TS 38.304 [20]; + - 3> perform barring as if *intraFreqReselection*, or *intraFreqReselectionRedCap* for RedCap UEs, or *intraFreqReselection-eRedCap* for eRedCap UEs, is set to *allowed*; + - 2> else if the UE is unable to acquire the *SIB1*: + - 3> consider the cell as barred in accordance with TS 38.304 [20]; + +- 3> if the UE is a RedCap UE: + - 4> perform barring as if *intraFreqReselectionRedCap* is set to *allowed*; +- 3> else if the UE is an eRedCap UE: + - 4> perform barring as if *intraFreqReselection-eRedCap* is set to *allowed*; +- 3> else: + - 4> perform cell re-selection to other cells on the same frequency as the barred cell as specified in TS 38.304 [20]. + +NOTE 1: The *SIB19* is essential for NTN access. If UE is unable to acquire the *SIB19* for NTN access, the action is up to UE implementation (e.g., cell re-selection to other cells). + +NOTE 2: The *SIB22* is essential for ATG access. If UE is unable to acquire the *SIB22* for ATG access, the action is up to UE implementation (e.g., cell re-selection to other cells). + +## 5.2.2.6 T430 expiry + +The UE shall: + +- 1> if T430 for serving cell expires and if in RRC\_CONNECTED: + - 2> inform lower layers that UL synchronisation is lost; + - 2> acquire *SIB19* as defined in clause 5.2.2.3.2; + - 2> upon successful acquisition of *SIB19*: + - 3> inform lower layers when UL synchronisation is obtained; + +NOTE: The exact time when UL synchronisation is obtained (after *SIB19* is acquired) is left to UE implementation, which can be from the subframe indicated by *epochTime* and optionally before the subframe indicated by *epochTime*. + +# 5.3 Connection control + +## 5.3.1 Introduction + +### 5.3.1.1 RRC connection control + +RRC connection establishment involves the establishment of SRB1. The network completes RRC connection establishment prior to completing the establishment of the NG connection, i.e. prior to receiving the UE context information from the 5GC. Consequently, AS security is not activated during the initial phase of the RRC connection. During + +this initial phase of the RRC connection, the network may configure the UE to perform measurement reporting, but the UE only sends the corresponding measurement reports after successful AS security activation. However, the UE only accepts a re-configuration with sync message when AS security has been activated. + +Upon receiving the UE context from the 5GC, the RAN activates AS security (both ciphering and integrity protection) using the initial AS security activation procedure. The RRC messages to activate AS security (command and successful response) are integrity protected, while ciphering is started only after completion of the procedure. That is, the response to the message used to activate AS security is not ciphered, while the subsequent messages (e.g. used to establish SRB2, DRBs and multicast MRBs) are both integrity protected and ciphered. After having initiated the initial AS security activation procedure, the network may initiate the establishment of SRB2 and DRBs and/or multicast MRBs, i.e. the network may do this prior to receiving the confirmation of the initial AS security activation from the UE. In any case, the network will apply both ciphering and integrity protection for the RRC reconfiguration messages used to establish SRB2, DRBs and/or multicast MRBs. The network should release the RRC connection if the initial AS security activation and/or the radio bearer establishment fails. A configuration with SRB2 without DRB or multicast MRB, or with DRB or multicast MRB without SRB2 is not supported (i.e., SRB2 and at least one DRB or multicast MRB must be configured in the same RRC Reconfiguration message, and it is not allowed to release all the DRBs and multicast MRBs without releasing the RRC Connection). For IAB-MT and NCR-MT, a configuration with SRB2 without any DRB/MRB is supported. + +The release of the RRC connection normally is initiated by the network. The procedure may be used to re-direct the UE to an NR frequency or an E-UTRA carrier frequency. + +The suspension of the RRC connection is initiated by the network. When the RRC connection is suspended, the UE stores the UE Inactive AS context and any configuration received from the network, and transits to RRC\_INACTIVE state. The RRC message to suspend the RRC connection is integrity protected and ciphered. + +The resumption of a suspended RRC connection is initiated by upper layers when the UE needs to transit from RRC\_INACTIVE state to RRC\_CONNECTED state or by RRC layer to perform a RNA update or by RAN paging from NG-RAN or for SDT. When the RRC connection is resumed, network configures the UE according to the RRC connection resume procedure based on the stored UE Inactive AS context and any RRC configuration received from the network. The RRC connection resume procedure re-activates AS security and re-establishes SRB(s) and DRB(s) and/or multicast MRB(s), if configured. + +Upon initiating the resume procedure for SDT, AS security (both ciphering and integrity protection) is re-activated for SRB2 (if configured for SDT) and for SRB1. In addition, AS security is also re-activated (if security is configured) for all the DRBs configured for SDT. Further, the PDCP entities of SRB1 and PDCP entities of the radio bearers configured for SDT are re-established and resumed whilst the UE remains in RRC\_INACTIVE state. Transmission and reception of data and/or signalling messages over radio bearers configured for SDT can happen whilst the UE is in RRC\_INACTIVE state and SDT procedure is ongoing. + +In response to a request to resume the RRC connection or in response to a resume procedure initiated for SDT, the network may resume the suspended RRC connection and send UE to RRC\_CONNECTED, or reject the request to resume and send UE to RRC\_INACTIVE (with a wait timer), or directly re-suspend the RRC connection and send UE to RRC\_INACTIVE, or directly release the RRC connection and send UE to RRC\_IDLE, or instruct the UE to initiate NAS level recovery (in this case the network sends an RRC setup message). + +NOTE: In case the UE receives the configurations for NR sidelink communication via the E-UTRA, the configurations for NR sidelink communication in *SIB12* and *sl-ConfigDedicatedNR* within *RRCREconfiguration* used in clause 5.3 are provided by the configurations in *SystemInformationBlockType28* and *sl-ConfigDedicatedForNR* within *RRCConnectionReconfiguration* as specified in TS 36.331[10], respectively. + +### 5.3.1.2 AS Security + +AS security comprises of the integrity protection and ciphering of RRC signalling (SRBs) and user data (DRBs). + +RRC handles the configuration of the AS security parameters which are part of the AS configuration: the integrity protection algorithm, the ciphering algorithm, if integrity protection and/or ciphering is enabled for a DRB and two parameters, namely the *keySetChangeIndicator* and the *nextHopChainingCount*, which are used by the UE to determine the AS security keys upon reconfiguration with sync (with key change), connection re-establishment and/or connection resume. + +The integrity protection algorithm is common for SRB1, SRB2, SRB3 (if configured), SRB4 (if configured), SRB5 (if configured) and DRBs configured with integrity protection, with the same *keyToUse* value. The ciphering algorithm is common for SRB1, SRB2, SRB3 (if configured), SRB4 (if configured), SRB5 (if configured) and DRBs configured with the same *keyToUse* value. Neither integrity protection nor ciphering applies for SRB0. + +NOTE 0: All DRBs related to the same PDU session have the same enable/disable setting for ciphering and the same enable/disable setting for integrity protection, as specified in TS 33.501 [11]. + +RRC integrity protection and ciphering are always activated together, i.e. in one message/procedure. RRC integrity protection and ciphering for SRBs are never de-activated. However, it is possible to switch to a 'NULL' ciphering algorithm (*nea0*). + +The 'NULL' integrity protection algorithm (*nia0*) is used only for SRBs and for the UE in limited service mode, see TS 33.501 [11] and when used for SRBs, integrity protection is disabled for DRBs. In case the 'NULL' integrity protection algorithm is used, 'NULL' ciphering algorithm is also used. + +NOTE 1: Lower layers discard RRC messages for which the integrity protection check has failed and indicate the integrity protection verification check failure to RRC. + +The AS applies four different security keys: one for the integrity protection of RRC signalling ( $K_{\text{RRCint}}$ ), one for the ciphering of RRC signalling ( $K_{\text{RRCenc}}$ ), one for integrity protection of user data ( $K_{\text{UPint}}$ ) and one for the ciphering of user data ( $K_{\text{UPenc}}$ ). All four AS keys are derived from the $K_{\text{gNB}}$ key. The $K_{\text{gNB}}$ key is based on the $K_{\text{AMF}}$ key (as specified in TS 33.501 [11]), which is handled by upper layers. + +The integrity protection and ciphering algorithms can only be changed with reconfiguration with sync. The AS keys ( $K_{\text{gNB}}$ , $K_{\text{RRCint}}$ , $K_{\text{RRCenc}}$ , $K_{\text{UPint}}$ and $K_{\text{UPenc}}$ ) change upon reconfiguration with sync (if *masterKeyUpdate* is included), and upon connection re-establishment and connection resume. + +For each radio bearer an independent counter (*COUNT*, as specified in TS 38.323 [5]) is maintained for each direction. For each radio bearer, the *COUNT* is used as input for ciphering and integrity protection. + +It is not allowed to use the same *COUNT* value more than once for a given security key. As specified in TS 33.501 clause 6.9.4.1 [11], the network is responsible for avoiding reuse of the *COUNT* with the same RB identity and with the same key, e.g. due to the transfer of large volumes of data, release and establishment of new RBs, and multiple termination point changes for RLC-UM bearers and multiple termination point changes for RLC-AM bearer with SN terminated PDCP re-establishment (*COUNT* reset) due to SN only full configuration whilst the key stream inputs (i.e. bearer ID, security key) at MN have not been updated. In order to avoid such re-use, the network may e.g. use different RB identities for RB establishments, change the AS security key, or an RRC\_CONNECTED to RRC\_IDLE/RRC\_INACTIVE and then to RRC\_CONNECTED transition. + +In order to limit the signalling overhead, individual messages/ packets include a short sequence number (PDCP SN, as specified in TS 38.323 [5]). In addition, an overflow counter mechanism is used: the hyper frame number (*HFN*, as specified in TS 38.323 [5]). The HFN needs to be synchronized between the UE and the network. + +For each SRB, the value provided by RRC to lower layers to derive the 5-bit BEARER parameter used as input for ciphering and for integrity protection is the value of the corresponding *srb-Identity* with the MSBs padded with zeroes. + +For a UE provided with an *sk-counter*, *keyToUse* indicates whether the UE uses the master key ( $K_{gNB}$ ) or the secondary key ( $S-K_{gNB}$ or $S-K_{gNB}$ ) for a particular DRB. The secondary key is derived from the master key and *sk-Counter*, as defined in TS 33.501[11]. Whenever there is a need to refresh the secondary key, e.g. upon change of MN with $K_{gNB}$ change or to avoid COUNT reuse, the security key update is used (see 5.3.5.7). When the UE is in NR-DC, the network may provide a UE configured with an SCG with an *sk-Counter* even when no DRB is setup using the secondary key ( $S-K_{gNB}$ ) in order to allow the configuration of SRB3. The network can also provide the UE with an *sk-Counter*, even if no SCG is configured, when using SN terminated MCG bearers. + +## 5.3.2 Paging + +### 5.3.2.1 General + +![Sequence diagram showing the Paging procedure. A vertical line on the left is labeled 'UE' and a vertical line on the right is labeled 'Network'. A horizontal arrow points from the Network line to the UE line, with the word 'Paging' written above it.](691626a7032a642bb74793336c37e274_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Network + Note left of UE: + Network->>UE: Paging + Note right of Network: + +``` + +Sequence diagram showing the Paging procedure. A vertical line on the left is labeled 'UE' and a vertical line on the right is labeled 'Network'. A horizontal arrow points from the Network line to the UE line, with the word 'Paging' written above it. + +Figure 5.3.2.1-1: Paging + +The purpose of this procedure is: + +- to transmit paging information to a UE in RRC\_IDLE or RRC\_INACTIVE. +- to transmit paging information for a L2 U2N Remote UE in RRC\_IDLE or RRC\_INACTIVE to its serving L2 U2N Relay UE in any RRC state. + +### 5.3.2.2 Initiation + +The network initiates the paging procedure by transmitting the *Paging* message at the UE's paging occasion as specified in TS 38.304 [20]. The network may address multiple UEs within a *Paging* message by including one *PagingRecord* for each UE. The network may also include one or multiple TMGI(s) in the *Paging* message to page UEs for specific MBS multicast session(s). + +### 5.3.2.3 Reception of the *Paging message* by the UE or *PagingRecord* by the L2 U2N Remote UE + +Upon receiving the *Paging* message by the UE or receiving *PagingRecord* from its connected L2 U2N Relay UE by a L2 U2N Remote UE, the UE shall: + +- 1> if in RRC\_IDLE, for each of the *PagingRecord*, if any, included in the *Paging* message, or +- 1> if in RRC\_IDLE, for the *PagingRecord*, if any, included in the *UuMessageTransferSidelink* message received from the connected L2 U2N Relay UE: + - 2> if the *ue-Identity* included in the *PagingRecord* matches the UE identity allocated by upper layers: + +- 3> if upper layers indicate the support of paging cause: + - 4> forward the *ue-Identity*, *accessType* (if present) and paging cause (if determined) to the upper layers; +- 3> else: + - 4> forward the *ue-Identity* and *accessType* (if present) to the upper layers; + +NOTE 1: If the L2 U2N Relay UE supports the MUSIM feature, it can forward the paging cause to the connected L2 U2N Remote UE. + +- 1> if in RRC\_INACTIVE, for each of the *PagingRecord*, if any, included in the *Paging* message, or +- 1> if in RRC\_INACTIVE, for the *PagingRecord*, if any, included in the *UuMessageTransferSidelink* message received from the connected L2 U2N Relay UE: + +- 2> if the *ue-Identity* included in the *PagingRecord* matches the UE's stored *fullI-RNTI*: + - 3> if the UE is configured by upper layers with Access Identity 1: + - 4> initiate the RRC connection resumption procedure according to 5.3.13 with *resumeCause* set to *mps-PriorityAccess*; + - 3> else if the UE is configured by upper layers with Access Identity 2: + - 4> initiate the RRC connection resumption procedure according to 5.3.13 with *resumeCause* set to *mcs-PriorityAccess*; + - 3> else if the UE is configured by upper layers with one or more Access Identities equal to 11-15: + - 4> initiate the RRC connection resumption procedure according to 5.3.13 with *resumeCause* set to *highPriorityAccess*; + - 3> else if *mt-SDT* indication was included in the paging message and if the conditions for initiating SDT for a resume procedure initiated in response to RAN paging according to 5.3.13.1b are fulfilled: + - 4> initiate the RRC connection resumption procedure according to 5.3.13 with *resumeCause* set to *mt-SDT*; + - 3> else: + - 4> initiate the RRC connection resumption procedure according to 5.3.13 with *resumeCause* set to *mt-Access*; + +NOTE 2: If both conditions for initiating MT-SDT and MO-SDT according to 5.3.13.1b are fulfilled, UE may initiate RRC connection resumption procedure for MT-SDT or MO-SDT based on implementation. + +NOTE 3: A MUSIM UE may not initiate the RRC connection resumption procedure, e.g. when it decides not to respond to the *Paging* message due to UE implementation constraints as specified in TS 24.501 [23]. + +- 2> else if the *ue-Identity* included in the *PagingRecord* matches the UE identity allocated by upper layers: + +- 3> if upper layers indicate the support of paging cause: + - 4> forward the *ue-Identity*, *accessType* (if present) and paging cause (if determined) to the upper layers; + - 3> else: + - 4> forward the *ue-Identity* and *accessType* (if present) to the upper layers; + - 3> perform the actions upon going to RRC\_IDLE as specified in 5.3.11 with release cause 'other'; +- 1> if in RRC\_IDLE, for each *TMGI* included in *pagingGroupList*, if any, included in the *Paging* message: + - 2> if the UE has joined an MBS session indicated by the *TMGI* included in the *pagingGroupList*: + - 3> forward the *TMGI* to the upper layers; + - 1> if in RRC\_INACTIVE and the UE has joined one or more MBS session(s) indicated by the *TMGI(s)* included in the *pagingGroupList*: + - 2> if the UE is not configured to receive multicast in RRC\_INACTIVE or if *inactiveReceptionAllowed* is not included for at least one of the MBS session (s) indicated by the *TMGI(s)* that the UE has joined: + - 3> if *PagingRecordList* is not included in the *Paging* message; or + - 3> if none of the *ue-Identity* included in any of the *PagingRecord* matches the UE identity allocated by upper layers or the UE's stored *fullI-RNTI*: + - 4> initiate the RRC connection resumption procedure according to 5.3.13 with *resumeCause* set as below: + - 5> if the UE is configured by upper layers with Access Identity 1: + - 6> set *resumeCause* to *mps-PriorityAccess*; + - 5> else if the UE is configured by upper layers with Access Identity 2: + - 6> set *resumeCause* to *mcs-PriorityAccess*; + - 5> else if the UE is configured by upper layers with one or more Access Identities equal to 11-15: + - 6> set *resumeCause* to *highPriorityAccess*; + - 5> else: + - 6> set *resumeCause* to *mt-Access*; + - 3> else if the *ue-Identity* included in any of the *PagingRecord* matches the UE identity allocated by upper layers: + +- 4> forward the *TMGI(s)* to the upper layers; +- 2> else: + - 3> start monitoring the G-RNTI(s) corresponding to the *TMGI(s)*, if configured; + - 3> if the UE was notified to stop monitoring the G-RNTI(s) for all the joined multicast sessions that are configured for reception in RRC\_INACTIVE: + - 4> start monitoring the Multicast MCCH-RNTI; + - 4> acquire the *MBSMulticastConfiguration* message on multicast MCCH, if present; + - 3> else if the UE was notified to stop monitoring the G-RNTI for at least one multicast session for which the PTM configuration was not included in *RRRelease* message: + - 4> acquire the *MBSMulticastConfiguration* message on multicast MCCH; +- 1> if the UE is acting as a L2 U2N Relay UE, for each of the *PagingRecord*, if any, included in the *Paging* message: + - 2> if the *ue-Identity* included in the *PagingRecord* in the *Paging* message matches the UE identity in *sl-PagingIdentityRemoteUE* included in *sl-PagingInfo-RemoteUE* received in *RemoteUEInformationSidelink* message from a L2 U2N Remote UE: + - 3> initiate the Uu Message transfer in sidelink to that UE as specified in 5.8.9.9; + +### 5.3.3 RRC connection establishment + +#### 5.3.3.1 General + +![Sequence diagram of RRC connection establishment between UE and Network.](6d67eee81b97a14e06a6fe57a95aff36_img.jpg) + +``` +sequenceDiagram + participant UE + participant Network + Note left of UE: RRCSetupRequest + UE->>Network: RRCSetupRequest + Note right of Network: RRCSetup + Network-->>UE: RRCSetup + Note left of UE: RRCSetupComplete + UE->>Network: RRCSetupComplete +``` + +The diagram illustrates the RRC connection establishment process between a User Equipment (UE) and a Network. It consists of three main steps: 1. The UE sends an *RRCSetupRequest* message to the Network. 2. The Network responds with an *RRCSetup* message. 3. The UE completes the process with an *RRCSetupComplete* message. The sequence is shown as a vertical timeline with arrows indicating the direction of message flow. + +Sequence diagram of RRC connection establishment between UE and Network. + +Figure 5.3.3.1-1: RRC connection establishment, successful + +![Sequence diagram showing RRC connection establishment where the network rejects the request. The UE sends an RRCSetupRequest to the Network, and the Network responds with an RRCReject.](d04c50badc78d5ba47bf4e352af4a754_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Network + Note left of UE: RRC connection establishment + UE->>Network: RRCSetupRequest + Network-->>UE: RRCReject + +``` + +Sequence diagram showing RRC connection establishment where the network rejects the request. The UE sends an RRCSetupRequest to the Network, and the Network responds with an RRCReject. + +**Figure 5.3.3.1-2: RRC connection establishment, network reject** + +The purpose of this procedure is to establish an RRC connection. RRC connection establishment involves SRB1 establishment. The procedure is also used to transfer the initial NAS dedicated information/ message from the UE to the network. + +The network applies the procedure e.g. as follows: + +- When establishing an RRC connection; +- When UE is resuming or re-establishing an RRC connection, and the network is not able to retrieve or verify the UE context. In this case, UE receives *RRCSetup* and responds with *RRCSetupComplete*. + +### 5.3.3.1a Conditions for establishing RRC Connection for NR sidelink communication/discovery/V2X sidelink communication + +For NR sidelink communication/discovery, an RRC connection establishment is initiated only in the following cases: + +- 1> if configured by upper layers to transmit NR sidelink communication and related data is available for transmission: + - 2> if the frequency on which the UE is configured to transmit NR sidelink communication is included in *sl-FreqInfoList/sl-FreqInfoListSizeExt* within *SIB12* provided by the cell on which the UE camps; and if the valid version of *SIB12* does not include *sl-TxPoolSelectedNormal* for the concerned frequency; +- 1> if configured by upper layers to transmit NR sidelink discovery and related data is available for transmission: + - 2> if the UE is configured by upper layers to transmit NR sidelink L2 U2N relay discovery messages and *sl-L2U2N-Relay* is included in *SIB12*; or + - 2> if the UE is configured by upper layers to transmit NR sidelink L3 U2N relay discovery messages and *sl-L3U2N-RelayDiscovery* is included in *SIB12*; or + - 2> if the UE is configured by upper layers to transmit NR sidelink non-relay discovery messages and *sl-NonRelayDiscovery* is included in *SIB12*: + - 3> if the frequency on which the UE is configured to transmit NR sidelink discovery is included in *sl-FreqInfoList/sl-FreqInfoListSizeExt* within *SIB12* provided by the cell on which the UE camps; and if the valid version of *SIB12* includes neither *sl-DiscTxPoolSelected* nor *sl-TxPoolSelectedNormal* for the concerned frequency; + +For L2 U2N Relay UE in RRC\_IDLE, an RRC connection establishment is initiated in the following cases: + +- 1> if any message is received from a L2 U2N Remote UE via SL-RLC0 as specified in 9.1.1.4 or SL-RLC1 as specified in 9.2.4; or +- 1> if *RemoteUEInformationSidelink* containing the *connectionForMP* is received from a L2 U2N Remote UE as specified in 5.8.9.8.3; + +For V2X sidelink communication, an RRC connection is initiated only when the conditions specified for V2X sidelink communication in clause 5.3.3.1a of TS 36.331 [10] are met. + +NOTE: Upper layers initiate an RRC connection (except if the RRC connection is initiated at the L2 U2N Relay UE upon reception of a message from a L2 U2N Remote UE via SL-RLC0 or SL-RLC1). The interaction with NAS is left to UE implementation. + +### 5.3.3.1b Conditions for establishing RRC Connection for NR sidelink Positioning + +For NR sidelink positioning an RRC connection is established only in the following cases: + +- 1> if SL-PRS transmission is triggered: + - 2> if the frequency on which the UE is configured to transmit NR sidelink positioning is included in *sl-FreqInfoList* within *SIB23* provided by the cell on which the UE camps; and if the valid version of *SIB23* does not include *sl-PRS-TxPoolSelectedNormal* for the concerned frequency. + +### 5.3.3.2 Initiation + +The UE initiates the procedure when upper layers request establishment of an RRC connection while the UE is in RRC\_IDLE and it has acquired essential system information, or for sidelink communication as specified in clause 5.3.3.1a. + +The UE shall ensure having valid and up to date essential system information as specified in clause 5.2.2.2 before initiating this procedure. + +Upon initiation of the procedure, the UE shall: + +- 1> if the upper layers provide an Access Category and one or more Access Identities upon requesting establishment of an RRC connection: + - 2> perform the unified access control procedure as specified in 5.3.14 using the Access Category and Access Identities provided by upper layers; + - 3> if the access attempt is barred, the procedure ends; +- 1> if the upper layers provide NSAG information and one or more S-NSSAI(s) triggering the access attempt (TS 23.501 [32] and TS 24.501 [23]): + - 2> apply the NSAG with highest NSAG priority among the NSAGs that are included in *SIB1* (i.e., in *FeatureCombination* and/or in *RA-PrioritizationSliceInfo*), and that are associated with the S-NSSAI(s) triggering the access attempt, in the Random Access procedure (TS 38.321 [3], clause 5.1); + +NOTE: If there are multiple NSAGs with the same highest NAS-provided NSAG priority identified for access attempt as above, it is left to UE implementation to select the NSAG to be applied in the Random Access procedure. + +- 1> if the UE is acting as L2 U2N Remote UE: + - 2> establish a SRAP entity as specified in TS 38.351 [66], if no SRAP entity has been established; + - 2> apply the specified configuration of SL-RLC0 as specified in 9.1.1.4; + - 2> apply the SDAP configuration and PDCP configuration as specified in 9.1.1.2 for SRB0; +- 1> else: + - 2> apply the default L1 parameter values as specified in corresponding physical layer specifications except for the parameters for which values are provided in *SIB1*; + - 2> apply the default MAC Cell Group configuration as specified in 9.2.2; + - 2> apply the CCCH configuration as specified in 9.1.1.2; + - 2> apply the *timeAlignmentTimerCommon* included in *SIB1*; +- 1> start timer T300; +- 1> initiate transmission of the *RRCSsetupRequest* message in accordance with 5.3.3.3; + +### 5.3.3.3 Actions related to transmission of *RRCSsetupRequest* message + +The UE shall set the contents of *RRCSsetupRequest* message as follows: + +- 1> set the *ue-Identity* as follows: + - 2> if upper layers provide a 5G-S-TMSI: + - 3> set the *ue-Identity* to *ng-5G-S-TMSI-Part1*; + - 2> else: + - 3> draw a 39-bit random value in the range $0..2^{39}-1$ and set the *ue-Identity* to this value; + +NOTE 1: Upper layers provide the *5G-S-TMSI* if the UE is registered in the TA of the current cell. + +- 1> if the establishment of the RRC connection is the result of release with redirect with *mpsPriorityIndication* (either in NR or E-UTRAN): + - 2> set the *establishmentCause* to *mps-PriorityAccess*; +- 1> else: + +2> set the *establishmentCause* in accordance with the information received from upper layers; + +NOTE 2: In case the L2 U2N Relay UE initiates RRC connection establishment triggered by reception of message from a L2 U2N Remote UE via SL-RLC0 or SL-RLC1 as specified in 5.3.3.1a, the L2 U2N Relay UE sets the *establishmentCause* by implementation, but it can only set the *emergency*, *mps-PriorityAccess*, or *mcs-PriorityAccess* as *establishmentCause* if the same cause value is in the message received from the L2 U2N Remote UE via SL-RLC0. + +1> if *ta-Report* or *ta-ReportATG* is configured with value *enabled* and the UE supports TA reporting: + +2> indicate TA report initiation to lower layers; + +The UE shall submit the *RRCSsetupRequest* message to lower layers for transmission. + +If the UE is an (e)RedCap UE and the (e)RedCap-specific initial downlink BWP is not associated with CD-SSB, the UE may continue cell re-selection related measurements as well as cell re-selection evaluation, otherwise the UE shall continue cell re-selection related measurements as well as cell re-selection evaluation. If the conditions for cell re-selection are fulfilled, the UE shall perform cell re-selection as specified in 5.3.3.6. + +NOTE 3: For L2 U2N Remote UE in RRC\_IDLE, the cell (re)selection procedure as specified in TS 38.304 [20] and relay (re)selection procedure as specified in 5.8.15.3 are performed independently and up to UE implementation to select either a cell or a L2 U2N Relay UE. + +### 5.3.3.4 Reception of the *RRCSsetup* by the UE + +The UE shall perform the following actions upon reception of the *RRCSsetup*: + +1> if the *RRCSsetup* is received in response to an *RRCReestablishmentRequest*; or + +1> if the *RRCSsetup* is received in response to an *RRCResumeRequest* or *RRCResumeRequest1*: + +2> if the UE is NCR-MT: + +3> indicate to NCR-Fwd to cease forwarding; + +2> if *sdt-MAC-PHY-CG-Config* is configured: + +3> instruct the MAC entity to stop the *cgi-SDT-TimeAlignmentTimer*, if it is running; + +3> instruct the MAC entity to start the *timeAlignmentTimer* associated with the PTAG, if it is not running; + +2> if *srs-PosRRc-Inactive* is configured: + +3> instruct the MAC entity to stop the *inactivePosSRS-TimeAlignmentTimer*, if it is running; + +2> if *srs-PosRRc-InactiveValidityAreaConfig* is configured: + +3> instruct the MAC entity to stop the *inactivePosSRS-ValidityAreaTAT*, if it is running; + +- 2> discard any stored UE Inactive AS context and *suspendConfig*; +- 2> discard any current AS security context including the $K_{RRCenc}$ key, the $K_{RRCint}$ key, the $K_{UPint}$ key and the $K_{UPenc}$ key; +- 2> release radio resources for all established RBs except SRB0 and broadcast MRBs, including release of the RLC entities, of the associated PDCP entities and of SDAP; +- 2> release the RRC configuration except for the default L1 parameter values, default MAC Cell Group configuration, CCCH configuration and broadcast MRBs; +- 2> indicate to upper layers fallback of the RRC connection; +- 2> for each application layer measurement configuration with *configForRRC-IdleInactive* absent or not set to *true*: + - 3> discard any application layer measurement reports which were not transmitted yet; + - 3> inform upper layers about the release of all application layer measurement configurations; +- 2> stop timer T380, if running; +- 1> perform the cell group configuration procedure in accordance with the received *masterCellGroup* and as specified in 5.3.5.5; +- 1> perform the radio bearer configuration procedure in accordance with the received *radioBearerConfig* and as specified in 5.3.5.6; +- 1> if stored, discard the cell reselection priority information provided by the *cellReselectionPriorities* or inherited from another RAT; +- 1> stop timer T300, T301, T319; +- 1> if T319a is running: + - 2> stop T319a; + - 2> consider SDT procedure is not ongoing; +- 1> if T390 is running: + - 2> stop timer T390 for all access categories; + - 2> perform the actions as specified in 5.3.14.4; +- 1> if T302 is running: + - 2> stop timer T302; + - 2> perform the actions as specified in 5.3.14.4; +- 1> stop timer T320, if running; + +- 1> if the *RRCSsetup* is received in response to an *RRCResumeRequest*, *RRCResumeRequest1* or *RRCSsetupRequest*: + - 2> if T331 is running: + - 3> stop timer T331; + - 3> perform the actions as specified in 5.7.8.3; + - 2> enter RRC\_CONNECTED; + - 2> stop the cell re-selection procedure; + - 2> stop relay (re)selection procedure if any for L2 U2N Remote UE; +- 1> consider the current cell to be the PCell; +- 1> perform the L2 U2N Remote UE configuration procedure in accordance with the received *sl-L2RemoteUE-Config* as specified in 5.3.5.16; +- 1> perform the sidelink dedicated configuration procedure in accordance with the received *sl-ConfigDedicatedNR* as specified in 5.3.5.14; +- 1> if the UE has radio link failure or handover failure information available in *VarRLF-Report* and if the RPLMN is included in *plmn-IdentityList* stored in *VarRLF-Report*: + - 2> if *reconnectCellId* in *VarRLF-Report* is not set after failing to perform reestablishment and if this is the first *RRCSsetup* received by the UE after declaring the failure: + - 3> if the UE supports RLF-Report for conditional handover and if *choCellId* in *VarRLF-Report* is set: + - 4> set *timeUntilReconnection* in *VarRLF-Report* to the time that elapsed since the radio link failure or handover failure experienced in the *failedPCellId* stored in *VarRLF-Report*; + - 3> else: + - 4> set *timeUntilReconnection* in *VarRLF-Report* to the time that elapsed since the last radio link failure or handover failure; + - 3> set *nrReconnectCellId* in *reconnectCellId* in *VarRLF-Report* to the global cell identity and the tracking area code of the PCell; +- 1> if the UE supports RLF report for inter-RAT MRO NR as defined in TS 36.306 [62], and if the UE has radio link failure or handover failure information available in *VarRLF-Report* of TS 36.331 [10] and if the RPLMN is included in *plmn-IdentityList* stored in *VarRLF-Report* of TS 36.331 [10]: + - 2> if *reconnectCellId* in *VarRLF-Report* of TS 36.331[10] is not set after failing to perform reestablishment and if this is the first *RRCSsetup* received by the UE after declaring the failure: + - 3> set *timeUntilReconnection* in *VarRLF-Report* of TS 36.331[10] to the time that elapsed since the last radio link failure or handover failure in LTE; + - 3> set *nrReconnectCellId* in *reconnectCellId* in *VarRLF-Report* of TS 36.331[10] to the global cell identity and the tracking area code of the PCell; + +- 1> set the content of *RRCSetupComplete* message as follows: + - 2> if upper layers provide a 5G-S-TMSI: + - 3> if the *RRCSetup* is received in response to an *RRCSetupRequest*: + - 4> set the *ng-5G-S-TMSI-Value* to *ng-5G-S-TMSI-Part2*; + - 3> else: + - 4> set the *ng-5G-S-TMSI-Value* to *ng-5G-S-TMSI*; + - 2> if upper layers selected an SNPN or a PLMN and in case of PLMN UE is either allowed or instructed to access the PLMN via a cell for which at least one CAG ID is broadcast: + - 3> set the *selectedPLMN-Identity* from the *npn-IdentityInfoList*; + - 2> else: + - 3> set the *selectedPLMN-Identity* to the PLMN selected by upper layers from the *plmn-IdentityInfoList*; + - 2> if upper layers provide the 'Registered AMF': + - 3> include and set the *registeredAMF* as follows: + - 4> if the PLMN identity of the 'Registered AMF' is different from the PLMN selected by the upper layers: + - 5> include the *plmnIdentity* in the *registeredAMF* and set it to the value of the PLMN identity in the 'Registered AMF' received from upper layers; + - 4> set the *amf-Identifier* to the value received from upper layers; + - 3> include and set the *guami-Type* to the value provided by the upper layers; + - 2> if upper layers provide one or more S-NSSAI (see TS 23.003 [21]): + - 3> include the *s-NSSAI-List* and set the content to the values provided by the upper layers; + - 2> if upper layers provide onboarding request indication: + - 3> include the *onboardingRequest*; + - 2> set the *dedicatedNAS-Message* to include the information received from upper layers; + - 2> if connecting as an IAB-node: + +- 3> include the *iab-NodeIndication*; +- 2> else if connecting as a mobile IAB-node: + - 3> include the *mobileIAB-NodeIndication*; +- 2> if connecting as an NCR-node: + - 3> include the *ncr-NodeIndication*; +- 2> if the SIB1 contains *idleModeMeasurementsNR* and the UE has NR idle/inactive measurement information concerning cells other than the PCell available in *VarMeasIdleReport*; or +- 2> if the SIB1 contains *idleModeMeasurementsEUTRA* and the UE has E-UTRA idle/inactive measurement information available in *VarMeasIdleReport*: + - 3> include the *idleMeasAvailable*; +- 2> if the UE has logged measurements available for NR and if the RPLMN is included in *plmn-IdentityList* stored in *VarLogMeasReport*; or +- 2> if the UE has logged measurements available for NR and if the current registered SNPN is included in *snpn-ConfigIDList* stored in *VarLogMeasReport*: + - 3> include the *logMeasAvailable* in the *RRCSsetupComplete* message; + - 3> if Bluetooth measurement results are included in the logged measurements the UE has available for NR: + - 4> include the *logMeasAvailableBT* in the *RRCSsetupComplete* message; + - 3> if WLAN measurement results are included in the logged measurements the UE has available for NR: + - 4> include the *logMeasAvailableWLAN* in the *RRCSsetupComplete* message; +- 2> if the *sigLoggedMeasType* in *VarLogMeasReport* is included; or +- 2> if the UE is capable of reporting availability of signalling based logged MDT for inter-RAT (i.e. LTE to NR), and if the *sigLoggedMeasType* in *VarLogMeasReport* of TS 36.331 [10] is included: + - 3> if T330 timer is running (associated to the logged measurement configuration for NR or for LTE): + - 4> set *sigLogMeasConfigAvailable* to *true* in the *RRCSsetupComplete* message; + - 3> else: + - 4> if the UE has logged measurements: + +5> set *sigLogMeasConfigAvailable* to *false* in the *RRCSsetupComplete* message; + +- 2> if the UE has connection establishment failure or connection resume failure information available in *VarConnEstFailReport* or *VarConnEstFailReportList* and if the RPLMN is equal to *plmn-Identity* stored in *VarConnEstFailReport* or in at least one of the entries of *VarConnEstFailReportList*; or +- 2> if the UE has connection establishment failure information or connection resume failure information available in *VarConnEstFailReport* or *VarConnEstFailReportList* and if the current registered SNPN identity is equal to *snpn-identity* stored in *VarConnEstFailReport* or any entry of *VarConnEstFailReportList*: + - 3> include *connEstFailInfoAvailable* in the *RRCSsetupComplete* message; +- 2> if the UE has radio link failure or handover failure information available in *VarRLF-Report* and if the RPLMN is included in *plmn-IdentityList* stored in *VarRLF-Report*, or +- 2> if the UE has radio link failure or handover failure information available in *VarRLF-Report* of TS 36.331 [10], and if the UE is capable of cross-RAT RLF reporting and if the RPLMN is included in *plmn-IdentityList* stored in *VarRLF-Report* of TS 36.331 [10]; or +- 2> if the UE has radio link failure or handover failure information available in *VarRLF-Report* and if the current registered SNPN is included in *snpn-IdentityList* stored in the *VarRLF-Report*: + - 3> include *rlf-InfoAvailable* in the *RRCSsetupComplete* message; +- 2> if the UE has successful handover information available in *VarSuccessHO-Report* and if the RPLMN is included in *plmn-IdentityList* stored in *VarSuccessHO-Report*; or +- 2> if the UE has successful handover information available in *VarSuccessHO-Report* and if the current registered SNPN is included in *snpn-IdentityList* stored in the *VarSuccessHO-Report*: + - 3> include *successHO-InfoAvailable* in the *RRCSsetupComplete* message; +- 2> if the UE has successful PSCell change or addition information available in *VarSuccessPSCell-Report* and if the RPLMN is included in *plmn-IdentityList* stored in *VarSuccessPSCell-Report*; or +- 2> if the UE has successful PSCell change or addition information available in *VarSuccessPSCell-Report* and if the current registered SNPN is included in *snpn-IdentityList* stored in the *VarSuccessPSCell-Report*: + - 3> include *successPSCell-InfoAvailable* in the *RRCSsetupComplete* message; +- 2> if the UE supports storage of mobility history information and the UE has mobility history information available in *VarMobilityHistoryReport*: + - 3> include the *mobilityHistoryAvail* in the *RRCSsetupComplete* message; +- 2> if the UE is configured with at least one application layer measurement with *configForRRc-IdleInactive* set to *true*: + - 3> for each application layer measurement configuration with *configForRRc-IdleInactive* set to *true*: + +- 4> if the RPLMN is not included in *plmn-IdentityList* in *VarAppLayerPLMN-ListConfig*: + - 5> forward the *measConfigAppLayerId* and inform upper layers about the release of the application layer measurement configuration; + - 5> discard any application layer measurement reports which were not yet submitted to lower layers for transmission; + - 5> release the application layer measurement configuration in UE variables *VarAppLayerIdleConfig* and *VarAppLayerPLMN-ListConfig*; + - 5> consider itself not to be configured to send application layer measurement report for the *measConfigAppLayerId*; +- 3> if at least one stored application layer measurement configuration or application layer measurement report container has not been released: + - 4> include *measConfigReportAppLayerAvailable* in the *RRCSsetupComplete* message; +- 2> if the UE supports uplink RRC message segmentation of *UECapabilityInformation*: + - 3> may include the *ul-RRC-Segmentation* in the *RRCSsetupComplete* message; +- 2> if the *RRCSsetup* is received in response to an *RRCResumeRequest*, *RRCResumeRequest1* or *RRCSsetupRequest*: + - 3> if *speedStateReselectionPars* is configured in the *SIB2*: + - 4> include the *mobilityState* in the *RRCSsetupComplete* message and set it to the mobility state (as specified in TS 38.304 [20]) of the UE just prior to entering *RRC\_CONNECTED* state; +- 2> if the *SIB1* contains *musim-CapRestrictionAllowed* and the UE capability is restricted for MUSIM operation: + - 3> if supported, include the *musim-CapRestrictionInd* in the *RRCSsetupComplete* message upon determining it has temporary capability restriction; +- 2> if the UE has flight path information available: + - 3> include *flightPathInfoAvailable*; +- 1> submit the *RRCSsetupComplete* message to lower layers for transmission, upon which the procedure ends. + +### 5.3.3.5 Reception of the *RRCRReject* by the UE + +The UE shall: + +- 1> perform the actions as specified in 5.3.15; + +### 5.3.3.6 Cell re-selection or cell selection or relay (re)selection while T390, T300 or T302 is running (UE in *RRC\_IDLE*) + +The UE shall: + +- 1> if cell reselection occurs while T300 or T302 is running; or +- 1> if relay reselection occurs while T300 is running; or +- 1> if cell changes due to relay reselection while T302 is running: + - 2> perform the actions upon going to RRC\_IDLE as specified in 5.3.11 with release cause 'RRC connection failure'; +- 1> else: + - 2> if cell selection or reselection occurs while T390 is running; or + - 2> cell change due to relay selection or reselection occurs while T390 is running: + - 3> stop T390 for all access categories; + - 3> perform the actions as specified in 5.3.14.4. + +### 5.3.3.7 T300 expiry + +The UE shall: + +- 1> if timer T300 expires: + - 2> reset MAC, release the MAC configuration and re-establish RLC for all RBs that are established (except broadcast MRBs); + - 2> if the UE supports RRC Connection Establishment failure with temporary offset and the T300 has expired a consecutive *connEstFailCount* times on the same cell for which *connEstFailureControl* is included in *SIB1*: + - 3> for a period as indicated by *connEstFailOffsetValidity*: + - 4> use *connEstFailOffset* for the parameter *Qoffsettemp* for the concerned cell when performing cell selection and reselection according to TS 38.304 [20] and TS 36.304 [27]; + +NOTE 1: When performing cell selection, if no suitable or acceptable cell can be found, it is up to UE implementation whether to stop using *connEstFailOffset* for the parameter *Qoffsettemp* during *connEstFailOffsetValidity* for the concerned cell. + +- 2> if the UE supports multiple CEF report: + - 3> if the UE is not registered in SNPN and if the UE has connection establishment failure information or connection resume failure information available in *VarConnEstFailReport* and if the RPLMN is equal to *plmn-identity* in *network-Identity* stored in *VarConnEstFailReport*; or + - 3> if the UE is registered in SNPN and if the UE has connection establishment failure information or connection resume failure information available in *VarConnEstFailReport* and if the registered SNPN identity is not equal to *snpn-identity* in *network-Identity* stored in any entry of *VarConnEstFailReportList*: + +- 4> if the cell identity of current cell is not equal to the cell identity stored in *measResultFailedCell* in *VarConnEstFailReport* and if the *maxCEFReport-r17* has not been reached: + - 5> append the *VarConnEstFailReport* as a new entry in the *VarConnEstFailReportList*; +- 2> if the UE has connection establishment failure information or connection resume failure information available in *VarConnEstFailReport* and if the RPLMN is not equal to *plmn-identity* in *network-Identity* stored in *VarConnEstFailReport*; or +- 2> if the UE is registered in SNPN and if the UE has connection establishment failure information or connection resume failure information available in *VarConnEstFailReport* and if the registered SNPN identity is not equal to *snpn-identity* in *network-Identity* stored in any entry of *VarConnEstFailReportList*: +- 2> if the cell identity of current cell is not equal to the cell identity stored in *measResultFailedCell* in *VarConnEstFailReport*: + - 3> reset the *numberOfConnFail* to 0; +- 2> if the UE supports multiple CEF report and if the UE has connection establishment failure information or connection resume failure information available in *VarConnEstFailReportList* and if the RPLMN is not equal to *plmn-identity* in *network-Identity* stored in any entry of *VarConnEstFailReportList*; or +- 2> if the UE supports multiple CEF report and if the UE has connection establishment failure information or connection resume failure information available in *VarConnEstFailReportList* and if the registered SNPN identity is not equal to *snpn-identity* in *network-Identity* stored in any entry of *VarConnEstFailReportList*: + - 3> clear the content included in *VarConnEstFailReportList*; +- 2> clear the content included in *VarConnEstFailReport* except for the *numberOfConnFail*, if any; +- 2> store the following connection establishment failure information in the *VarConnEstFailReport* by setting its fields as follows: + - 3> if the UE is not in SNPN access mode: + - 4> set the *plmn-Identity* in *network-Identity* to the PLMN selected by upper layers (see TS 24.501 [23]) from the PLMN(s) included in the *plmn-IdentityInfoList* in *SIB1*; + - 3> else if the UE is in SNPN access mode: + - 4> set the *snpn-Identity* in *network-Identity* to include the SNPN identity selected by upper layers (see TS 24.501 [23]) from the list of SNPN(s) included in the *spn-IdentityInfoList* in *SIB1*; + - 3> set the *measResultFailedCell* to include the global cell identity, tracking area code, the cell level and SS/PBCH block level RSRP, and RSRQ, and SS/PBCH block indexes, of the failed cell based on the available SSB measurements collected up to the moment the UE detected connection establishment failure; + - 3> if available, set the *measResultNeighCells*, in order of decreasing ranking-criterion as used for cell re-selection, to include neighbouring cell measurements for at most the following number of neighbouring cells: 6 intra-frequency and 3 inter-frequency neighbours per frequency as well as 3 inter-RAT neighbours, per frequency/ set of frequencies per RAT and according to the following: + +4> for each neighbour cell included, include the optional fields that are available; + +NOTE 2: The UE includes the latest results of the available measurements as used for cell reselection evaluation, which are performed in accordance with the performance requirements as specified in TS 38.133 [14]. + +3> if available, set the *locationInfo* as follows: + +4> if available, set the *commonLocationInfo* to include the detailed location information; + +4> if available, set the *bt-LocationInfo* to include the Bluetooth measurement results, in order of decreasing RSSI for Bluetooth beacons; + +4> if available, set the *wlan-LocationInfo* to include the WLAN measurement results, in order of decreasing RSSI for WLAN APs; + +4> if available, set the *sensor-LocationInfo* to include the sensor measurement results as follows; + +5> if available, include the *sensor-MeasurementInformation*; + +5> if available, include the *sensor-MotionInformation*; + +NOTE 3: Which location information related configuration is used by the UE to make the *locationInfo* available for inclusion in the *VarConnEstFailReport* is left to UE implementation. + +3> set *perRAInfoList* to indicate the performed random access procedure related information as specified in 5.7.10.5; + +3> if the *numberOfConnFail* is smaller than 8: + +4> increment the *numberOfConnFail* by 1; + +2> inform upper layers about the failure to establish the RRC connection, upon which the procedure ends; + +The UE may discard the connection establishment failure or connection resume failure information, i.e. release the UE variable *VarConnEstFailReport* and the UE variable *VarConnEstFailReportList*, 48 hours after the last connection establishment failure is detected. + +The L2 U2N Relay UE either indicates to upper layers (to trigger PC5 unicast link release) or sends *NotificationMessageSidelink* message to the connected L2 U2N Remote UE(s) in accordance with 5.8.9.10. + +### 5.3.3.8 Abortion of RRC connection establishment + +If upper layers abort the RRC connection establishment procedure, due to a NAS procedure being aborted as specified in TS 24.501 [23], while the UE has not yet entered RRC\_CONNECTED, the UE shall: + +1> stop timer T300, if running; + +1> reset MAC, release the MAC configuration and re-establish RLC for all RBs that are established (except broadcast MRBs). + +The L2 U2N Relay UE either indicates to upper layers (to trigger PC5 unicast link release) or sends *NotificationMessageSidelink* message to the connected L2 U2N Remote UE(s) in accordance with 5.8.9.10. + +The L2 U2N Remote UE indicates to upper layers to trigger PC5 unicast link release with its connected L2 U2N Relay UE. + +## 5.3.4 Initial AS security activation + +### 5.3.4.1 General + +![Sequence diagram for successful security mode command](bfc7918b689a38bc811276e0cc69477e_img.jpg) + +``` +sequenceDiagram + participant UE + participant Network + Note left of UE: + Network->>UE: SecurityModeCommand + Note right of Network: + UE-->>Network: SecurityModeComplete + Note left of UE: + Note right of Network: +``` + +A sequence diagram showing a successful security mode command procedure. It starts with a 'SecurityModeCommand' message from the Network to the UE, followed by a 'SecurityModeComplete' message from the UE back to the Network. + +Sequence diagram for successful security mode command + +Figure 5.3.4.1-1: Security mode command, successful + +![Sequence diagram for failed security mode command](1bd6a020aa71784ed74367899560cbb9_img.jpg) + +``` +sequenceDiagram + participant UE + participant Network + Note left of UE: + Network->>UE: SecurityModeCommand + Note right of Network: + UE-->>Network: SecurityModeFailure + Note left of UE: + Note right of Network: +``` + +A sequence diagram showing a failed security mode command procedure. It starts with a 'SecurityModeCommand' message from the Network to the UE, followed by a 'SecurityModeFailure' message from the UE back to the Network. + +Sequence diagram for failed security mode command + +Figure 5.3.4.1-2: Security mode command, failure + +The purpose of this procedure is to activate AS security upon RRC connection establishment. + +### 5.3.4.2 Initiation + +The network initiates the security mode command procedure to a UE in RRC\_CONNECTED. Moreover, the network applies the procedure as follows: + +- when only SRB1 is established, i.e. prior to establishment of SRB2, multicast MRBs and/ or DRBs. + +### 5.3.4.3 Reception of the *SecurityModeCommand* by the UE + +The UE shall: + +- 1> derive the $K_{\text{gNB}}$ key, as specified in TS 33.501 [11]; +- 1> derive the $K_{\text{RRCint}}$ key associated with the *integrityProtAlgorithm* indicated in the *SecurityModeCommand* message, as specified in TS 33.501 [11]; +- 1> request lower layers to verify the integrity protection of the *SecurityModeCommand* message, using the algorithm indicated by the *integrityProtAlgorithm* as included in the *SecurityModeCommand* message and the $K_{\text{RRCint}}$ key; +- 1> if the *SecurityModeCommand* message passes the integrity protection check: + - 2> derive the $K_{\text{RRCenc}}$ key and the $K_{\text{UPenc}}$ key associated with the *cipheringAlgorithm* indicated in the *SecurityModeCommand* message, as specified in TS 33.501 [11]; + - 2> derive the $K_{\text{UPint}}$ key associated with the *integrityProtAlgorithm* indicated in the *SecurityModeCommand* message, as specified in TS 33.501 [11]; + - 2> configure lower layers to apply SRB integrity protection using the indicated algorithm and the $K_{\text{RRCint}}$ key immediately, i.e. integrity protection shall be applied to all subsequent messages received and sent by the UE, including the *SecurityModeComplete* message; + - 2> configure lower layers to apply SRB ciphering using the indicated algorithm, the $K_{\text{RRCenc}}$ key after completing the procedure, i.e. ciphering shall be applied to all subsequent messages received and sent by the UE, except for the *SecurityModeComplete* message which is sent unciphered; + - 2> consider AS security to be activated; + - 2> submit the *SecurityModeComplete* message to lower layers for transmission, upon which the procedure ends; +- 1> else: + - 2> continue using the configuration used prior to the reception of the *SecurityModeCommand* message, i.e. neither apply integrity protection nor ciphering. + - 2> submit the *SecurityModeFailure* message to lower layers for transmission, upon which the procedure ends. + +## 5.3.5 RRC reconfiguration + +### 5.3.5.1 General + +![Sequence diagram for successful RRC reconfiguration](c1b762c358fd423d6686563b3fde7750_img.jpg) + +``` +sequenceDiagram + participant UE + participant Network + Note left of UE: + UE->>Network: RRCReconfiguration + Note right of Network: + Network->>UE: RRCReconfigurationComplete + Note left of UE: + Note right of Network: +``` + +A sequence diagram showing a successful RRC reconfiguration. The UE sends an *RRCReconfiguration* message to the Network. The Network responds with an *RRCReconfigurationComplete* message. The diagram includes lifelines for the UE and Network, and message arrows with associated activation bars. + +Sequence diagram for successful RRC reconfiguration + +Figure 5.3.5.1-1: RRC reconfiguration, successful + +![Sequence diagram for RRC reconfiguration failure](8b5a2bf5517051acf8bcc2587bcb73a1_img.jpg) + +``` +sequenceDiagram + participant UE + participant Network + Note left of UE: + UE->>Network: RRCReconfiguration + Note right of Network: + Network->>UE: RRC connection re-establishment + Note left of UE: + Note right of Network: +``` + +A sequence diagram showing an RRC reconfiguration failure. The UE sends an *RRCReconfiguration* message to the Network. Instead of a completion message, the Network responds with an *RRC connection re-establishment* message. The diagram includes lifelines for the UE and Network, and message arrows with associated activation bars. + +Sequence diagram for RRC reconfiguration failure + +Figure 5.3.5.1-2: RRC reconfiguration, failure + +The purpose of this procedure is to modify an RRC connection, e.g. to establish/modify/release RBs/BH RLC channels/Uu Relay RLC channels/PC5 Relay RLC channels, to perform reconfiguration with sync, to setup/modify/release measurements, to add/modify/release SCells and cell groups, to add/modify/release conditional handover configuration, to add/modify/release conditional PSCell change or conditional PSCell addition configuration, to add/modify/release LTM configuration. As part of the procedure, NAS dedicated information may be transferred from the Network to the UE. + +RRC reconfiguration to perform reconfiguration with sync includes, but is not limited to, the following cases: + +- reconfiguration with sync and security key refresh, involving RA to the PCell/PSCell, MAC reset, refresh of security and re-establishment of RLC and PDCP triggered by explicit indicators; +- reconfiguration with sync but without security key refresh, involving RA to the PCell/PSCell, MAC reset and RLC re-establishment and PDCP data recovery (for AM DRB or AM MRB) triggered by explicit indicators. + +- reconfiguration with sync for DAPS and security key refresh, involving RA to the target PCell, establishment of target MAC, and + - for non-DAPS bearer: refresh of security and re-establishment of RLC and PDCP triggered by explicit indicators; + - for DAPS bearer: establishment of RLC for the target PCell, refresh of security and reconfiguration of PDCP to add the ciphering function, the integrity protection function and ROHC function of the target PCell; + - for SRB: refresh of security and establishment of RLC and PDCP for the target PCell; +- reconfiguration with sync for DAPS but without security key refresh, involving RA to the target PCell, establishment of target MAC, and + - for non-DAPS bearer: RLC re-establishment and PDCP data recovery (for AM DRB or AM MRB) triggered by explicit indicators. + - for DAPS bearer: establishment of RLC for target PCell, reconfiguration of PDCP to add the ciphering function, the integrity protection function and ROHC function of the target PCell; + - for SRB: establishment of RLC and PDCP for the target PCell. +- reconfiguration with sync for direct-to-indirect path switch, not involving RA at target side, involving re-establishment of PDCP /PDCP data recovery (for AM DRB) triggered by explicit indicators, and +- reconfiguration with sync for LTM cell switch (without security key refresh), and + - involving or not involving RA to the target LTM candidate SpCell according to a network indication; + - MAC reset; + - depending on a network indication, re-establishment of RLC and PDCP data recovery (for AM DRB). +- reconfiguration with sync for LTM cell switch (without security key refresh), and + - involving or not involving RA to the target LTM candidate SpCell according to a network indication; + - MAC reset; + - depending on a network indication, no re-establishment of RLC. + +In (NG)EN-DC and NR-DC, SRB3 can be used for measurement configuration and reporting, for UE assistance (re-)configuration and reporting for power savings, for IP address (re-)configuration and reporting for IAB-nodes, to (re-)configure MAC, RLC, BAP, physical layer and RLF timers and constants of the SCG configuration, to reconfigure PDCP for DRBs associated with the $S-K_{\text{gNB}}$ or SRB3, to reconfigure SDAP for DRBs associated with $S-K_{\text{gNB}}$ in NGEN-DC and NR-DC, to add/modify/release conditional PSCell change configuration, and (re-)configure the LTM configuration associated with the SCG (only in NR-DC), provided that the (re-)configuration does not require any MN involvement, and to transmit RRC messages between the MN and the UE during fast MCG link recovery. In (NG)EN-DC and NR-DC, only *measConfig*, *radioBearerConfig*, *conditionalReconfiguration*, *ltm-Config* (only in NR-DC), *bap-Config*, *iab-IP-AddressConfigurationList*, *otherConfig*, *appLayerMeasConfig* and/or *secondaryCellGroup* are included in *RRCReconfiguration* received via SRB3, except when *RRCReconfiguration* is received within *DLInformationTransferMRDC*. + +When a clause of 5.3.5 is executed due to an LTM cell switch execution (i.e., as specified in 5.3.5.18.6) or due to a conditional reconfiguration execution for subsequent CPAC (i.e., as specified in 5.3.5.13.8), every appearance of "the received" before *RRCReconfiguration*, before a field name, or before an IE name, refers to the *RRCReconfiguration*, to the field name or to the IE, respectively, that was generated and stored by the UE as specified in 5.3.5.18.6 or 5.3.5.13.8. + +### 5.3.5.2 Initiation + +The Network may initiate the RRC reconfiguration procedure to a UE in RRC\_CONNECTED. The Network applies the procedure as follows: + +- the establishment of RBs (other than SRB1, that is established during RRC connection establishment) is performed only when AS security has been activated; +- the establishment of BH RLC Channels for IAB is performed only when AS security has been activated; +- the configuration of NCR-Fwd is performed only when AS security has been activated; +- the establishment of Uu Relay RLC channels and PC5 Relay RLC channels (other than SL-RLC0 and SL-RLC1) for L2 U2N Relay UE is performed only when AS security has been activated, and the establishment of PC5 Relay RLC channels for L2 U2N Remote UE (other than SL-RLC0 and SL-RLC1) is performed only when AS security has been activated; +- the establishment of PC5 Relay RLC channels for L2 U2U Relay UE and L2 U2U Remote UE is performed only when AS security has been activated; +- the addition of Secondary Cell Group and SCells is performed only when AS security has been activated; +- the *reconfigurationWithSync* is included in *secondaryCellGroup* only when at least one RLC bearer or BH RLC channel is setup in SCG; +- the *reconfigurationWithSync* is included in *masterCellGroup* only when AS security has been activated, and SRB2 with at least one DRB or multicast MRB or, for IAB and NCR, SRB2, are setup and not suspended; +- the *conditionalReconfiguration* for CPC is included only when at least one RLC bearer is setup in SCG; +- the *conditionalReconfiguration* for CHO or CPA is included only when AS security has been activated, and SRB2 with at least one DRB or multicast MRB or, for IAB, SRB2, are setup and not suspended; +- the addition of indirect path for MP is performed only when AS security has been activated; +- the *ltm-Config* for LTM on the MCG is included only when AS security has been activated, and SRB2 with at least one DRB are setup and not suspended; +- the *ltm-Config* for LTM on the SCG is included only when at least one RLC bearer is setup in SCG. + +*Editor's Note: Coexistence of LTM with other features is addressed during the ASN.1 review or maintainance.* + +### 5.3.5.3 Reception of an *RRCREconfiguration* by the UE + +The UE shall perform the following actions upon reception of the *RRCREconfiguration*, upon execution of the conditional reconfiguration (CHO, CPA or CPC), or upon execution of an LTM cell switch: + +- 1> if the *RRCREconfiguration* is applied due to a conditional reconfiguration execution upon cell selection performed while timer T311 was running, as defined in 5.3.7.3: + - 2> remove all the entries within the MCG and the SCG *VarConditionalReconfig*, if any; +- 1> if the *RRCREconfiguration* includes the *daps-SourceRelease*: + - 2> reset the source MAC and release the source MAC configuration; + - 2> for each DAPS bearer: + - 3> release the RLC entity or entities as specified in TS 38.322 [4], clause 5.1.3, and the associated logical channel for the source SpCell; + - 3> reconfigure the PDCP entity to release DAPS as specified in TS 38.323 [5]; + - 2> for each SRB: + - 3> release the PDCP entity for the source SpCell; + - 3> release the RLC entity as specified in TS 38.322 [4], clause 5.1.3, and the associated logical channel for the source SpCell; + - 2> release the physical channel configuration for the source SpCell; + - 2> discard the keys used in the source SpCell (the $K_{\text{gNB}}$ key, the $K_{\text{RRCenc}}$ key, the $K_{\text{RRCint}}$ key, the $K_{\text{UPint}}$ key and the $K_{\text{UPenc}}$ key), if any; +- 1> if the *RRCREconfiguration* is received via other RAT (i.e., inter-RAT handover to NR): + - 2> if the *RRCREconfiguration* does not include the *fullConfig* and the UE is connected to 5GC (i.e., delta signalling during intra 5GC handover): + - 3> re-use the source RAT SDAP and PDCP configurations if available (i.e., current SDAP/PDCP configurations for all RBs from source E-UTRA RAT prior to the reception of the inter-RAT HO *RRCREconfiguration* message); +- 1> else: + - 2> if the *RRCREconfiguration* includes the *fullConfig*: + - 3> perform the full configuration procedure as specified in 5.3.5.11; +- 1> if the *RRCREconfiguration* includes the *masterCellGroup*: + +- 2> perform the cell group configuration for the received *masterCellGroup* according to 5.3.5.5; +- 1> if the *RRCReconfiguration* includes the *masterKeyUpdate*: + - 2> perform AS security key update procedure as specified in 5.3.5.7; +- 1> if the *RRCReconfiguration* includes the *sk-Counter*: + - 2> perform security key update procedure as specified in 5.3.5.7; +- 1> if the *RRCReconfiguration* includes the *secondaryCellGroup*: + - 2> perform the cell group configuration for the SCG according to 5.3.5.5; +- 1> if the *RRCReconfiguration* includes the *mrdc-SecondaryCellGroupConfig*: + - 2> if the *mrdc-SecondaryCellGroupConfig* is set to *setup*: + - 3> if the *mrdc-SecondaryCellGroupConfig* includes *mrdc-ReleaseAndAdd*: + - 4> perform MR-DC release as specified in clause 5.3.5.10; + - 3> if the received *mrdc-SecondaryCellGroup* is set to *nr-SCG*: + - 4> perform the RRC reconfiguration according to 5.3.5.3 for the *RRCReconfiguration* message included in *nr-SCG*; + - 3> if the received *mrdc-SecondaryCellGroup* is set to *eutra-SCG*: + - 4> perform the RRC connection reconfiguration as specified in TS 36.331 [10], clause 5.3.5.3 for the *RRCConnectionReconfiguration* message included in *eutra-SCG*; + - 2> else (*mrdc-SecondaryCellGroupConfig* is set to *release*): + - 3> perform MR-DC release as specified in clause 5.3.5.10; +- 1> if the *RRCReconfiguration* message includes the *radioBearerConfig*: + - 2> perform the radio bearer configuration according to 5.3.5.6; +- 1> if the *RRCReconfiguration* message includes the *radioBearerConfig2*: + - 2> perform the radio bearer configuration according to 5.3.5.6; +- 1> if the *RRCReconfiguration* message includes the *measConfig*: + +2> perform the measurement configuration procedure as specified in 5.5.2; + +1> if the *RRReconfiguration* message includes the *dedicatedNAS-MessageList*: + +2> forward each element of the *dedicatedNAS-MessageList* to upper layers in the same order as listed; + +1> if the *RRReconfiguration* message includes the *dedicatedSIB1-Delivery*: + +2> perform the action upon reception of *SIB1* as specified in 5.2.2.4.2; + +NOTE 0: If this *RRReconfiguration* is associated to the MCG and includes *reconfigurationWithSync* in *spCellConfig* and *dedicatedSIB1-Delivery*, the UE initiates (if needed) the request to acquire required SIBs, according to clause 5.2.2.3.5, only after the random access procedure or the LTM cell switch execution towards the target SpCell is completed. + +1> if the *RRReconfiguration* message includes the *dedicatedSystemInformationDelivery*: + +2> perform the action upon reception of System Information as specified in 5.2.2.4; + +2> if all the SIB(s) and/or posSIB(s) requested in *DedicatedSIBRequest* message have been acquired: + +3> stop timer T350, if running; + +1> if the *RRReconfiguration* message includes the *dedicatedPosSysInfoDelivery*: + +2> perform the action upon reception of the contained posSIB(s), as specified in clause 5.2.2.4.16; + +2> if all the SIB(s) and/or posSIB(s) requested in *DedicatedSIBRequest* message have been acquired: + +3> stop timer T350, if running; + +1> if the *RRReconfiguration* message includes the *otherConfig*: + +2> perform the other configuration procedure as specified in 5.3.5.9; + +1> if the *RRReconfiguration* message includes the *bap-Config*: + +2> perform the BAP configuration procedure as specified in 5.3.5.12; + +1> if the *RRReconfiguration* message includes the *iab-IP-AddressConfigurationList*: + +2> if *iab-IP-AddressToReleaseList* is included: + +3> perform release of IP address as specified in 5.3.5.12a.1.1; + +- 2> if *iab-IP-AddressToAddModList* is included: + - 3> perform IAB IP address addition/update as specified in 5.3.5.12a.1.2; +- 1> if the *RRCREconfiguration* message includes the *conditionalReconfiguration*: + - 2> perform conditional reconfiguration as specified in 5.3.5.13; +- 1> if the *RRCREconfiguration* message includes the *needForGapsConfigNR*: + - 2> if *needForGapsConfigNR* is set to *setup*: + - 3> consider itself to be configured to provide the measurement gap requirement information of NR target bands; + - 2> else: + - 3> consider itself not to be configured to provide the measurement gap requirement information of NR target bands; +- 1> if the *RRCREconfiguration* message includes the *needForGapNCSG-ConfigNR*: + - 2> if *needForGapNCSG-ConfigNR* is set to *setup*: + - 3> consider itself to be configured to provide the measurement gap and NCSG requirement information of NR target bands; + - 2> else: + - 3> consider itself not to be configured to provide the measurement gap and NCSG requirement information of NR target bands; +- 1> if the *RRCREconfiguration* message includes the *needForGapNCSG-ConfigEUTRA*: + - 2> if *needForGapNCSG-ConfigEUTRA* is set to *setup*: + - 3> consider itself to be configured to provide the measurement gap and NCSG requirement information of E-UTRA target bands; + - 2> else: + - 3> consider itself not to be configured to provide the measurement gap and NCSG requirement information of E-UTRA target bands; +- 1> if the *RRCREconfiguration* message includes the *onDemandSIB-Request*: + - 2> if *onDemandSIB-Request* is set to *setup*: + - 3> consider itself to be configured to request SIB(s) or posSIB(s) in RRC\_CONNECTED in accordance with clause 5.2.2.3.5; + - 2> else: + +3> consider itself not to be configured to request SIB(s) or posSIB(s) in RRC\_CONNECTED in accordance with clause 5.2.2.3.5; + +3> stop timer T350, if running; + +1> if the *RRCReconfiguration* message includes the *sl-ConfigDedicatedNR*: + +2> perform the sidelink dedicated configuration procedure as specified in 5.3.5.14; + +NOTE 0a: If the *sl-ConfigDedicatedNR* was received embedded within an E-UTRA *RRCConnectionReconfiguration* message, the UE does not build an NR *RRCReconfigurationComplete* message for the received *sl-ConfigDedicatedNR*. + +1> if the *RRCReconfiguration* message includes the *sl-L2RelayUE-Config*: + +2> perform the L2 U2N or U2U Relay UE configuration procedure as specified in 5.3.5.15; + +1> if the *RRCReconfiguration* message includes the *sl-L2RemoteUE-Config*: + +2> perform the L2 U2N or U2U Remote UE configuration procedure as specified in 5.3.5.16; + +1> if the *RRCReconfiguration* message includes the *dedicatedPagingDelivery*: + +2> perform the *Paging* message reception procedure as specified in 5.3.2.3; + +1> if the *RRCReconfiguration* message includes the *sl-ConfigDedicatedEUTRA-Info*: + +2> perform related procedures for V2X sidelink communication in accordance with TS 36.331 [10], clause 5.3.10 and clause 5.5.2; + +1> if the *RRCReconfiguration* message includes the *ul-GapFR2-Config*: + +2> perform the FR2 UL gap configuration procedure as specified in 5.3.5.13c; + +1> if the *RRCReconfiguration* message includes the *musim-GapConfig*: + +2> perform the MUSIM gap configuration procedure as specified in 5.3.5.9a; + +1> if *idleInactiveReportAllowed* is not included in the *RRCReconfiguration* message: + +2> for each application layer measurement configuration with *configforRRC-IdleInactive* set to *true*: + +3> forward the *measConfigAppLayerId* and inform upper layers about the release of the application layer measurement configuration; + +3> discard any application layer measurement reports which were not yet submitted to lower layers for transmission; + +3> if stored, release the application layer measurement configuration in UE variables *VarAppLayerIdleConfig* and *VarAppLayerPLMN-ListConfig*; + +- 3> consider itself not to be configured to send application layer measurement report for the *measConfigAppLayerId*; +- 1> if the *RRCReconfiguration* message includes the *appLayerMeasConfig*: + - 2> perform the application layer measurement configuration procedure as specified in 5.3.5.13d; +- 1> if the *RRCReconfiguration* message includes the *ue-TxTEG-RequestUL-TDOA-Config*: + - 2> if *ue-TxTEG-RequestUL-TDOA-Config* is set to *setup*: + - 3> perform the UE positioning assistance information procedure as specified in 5.7.14; + - 2> else: + - 3> release the configuration of UE positioning assistance information; +- 1> if the *RRCReconfiguration* message includes the *uav-Config*: + - 2> (re)configure the UAV parameters in accordance with the included *uav-Config*; +- 1> if the *RRCReconfiguration* message includes the *sl-IndirectPathAddChange*: + - 2> perform the SL indirect path specific configuration procedure as specified in 5.3.5.17.2.2; +- 1> if the *RRCReconfiguration* message includes the *n3c-IndirectPathAddChange*: + - 2> perform configuration procedure for the remote UE part of N3C indirect path as specified in 5.3.5.17.3.2; +- 1> if the *RRCReconfiguration* message includes the *n3c-IndirectPathConfigRelay*: + - 2> perform the configuration procedure for the relay UE part of N3C indirect path as specified in 5.3.5.17.3.3; +- 1> if the *RRCReconfiguration* message includes the *ltm-Config*: + - 2> if the *ltm-Config* is set to *setup*: + - 3> perform the LTM configuration procedure as specified in 5.3.5.18.1; + - 2> else: + - 3> perform the LTM configuration release procedure as specified in clause 5.3.5.18.7; +- 1> set the content of the *RRCReconfigurationComplete* message as follows: + - 2> if the *RRCReconfiguration* includes the *masterCellGroup* containing the *reportUplinkTxDirectCurrent*: + +- 3> include the *uplinkTxDirectCurrentList* for each MCG serving cell with UL; +- 3> include *uplinkDirectCurrentBWP-SUL* for each MCG serving cell configured with SUL carrier, if any, within the *uplinkTxDirectCurrentList*; +- 2> if the *RRReconfiguration* includes the *masterCellGroup* containing the *reportUplinkTxDirectCurrentTwoCarrier*: + - 3> include in the *uplinkTxDirectCurrentTwoCarrierList* the list of uplink Tx DC locations for the configured intra-band uplink carrier aggregation in the MCG; +- 2> if the *RRReconfiguration* includes the *masterCellGroup* containing the *reportUplinkTxDirectCurrentMoreCarrier*: + - 3> include in the *uplinkTxDirectCurrentMoreCarrierList* the list of uplink Tx DC locations for the configured intra-band uplink carrier aggregation in the MCG; +- 2> if the *RRReconfiguration* includes the *secondaryCellGroup* containing the *reportUplinkTxDirectCurrent*: + - 3> include the *uplinkTxDirectCurrentList* for each SCG serving cell with UL; + - 3> include *uplinkDirectCurrentBWP-SUL* for each SCG serving cell configured with SUL carrier, if any, within the *uplinkTxDirectCurrentList*; +- 2> if the *RRReconfiguration* includes the *secondaryCellGroup* containing the *reportUplinkTxDirectCurrentTwoCarrier*: + - 3> include in the *uplinkTxDirectCurrentTwoCarrierList* the list of uplink Tx DC locations for the configured intra-band uplink carrier aggregation in the SCG; +- 2> if the *RRReconfiguration* includes the *secondaryCellGroup* containing the *reportUplinkTxDirectCurrentMoreCarrier*: + - 3> include in the *uplinkTxDirectCurrentMoreCarrierList* the list of uplink Tx DC locations for the configured intra-band uplink carrier aggregation in the SCG; + +NOTE 0b: The UE does not expect that the *reportUplinkTxDirectCurrentTwoCarrier* or *reportUplinkTxDirectCurrentMoreCarrier* is received in both *masterCellGroup* and in *secondaryCellGroup*. Network only configures at most one of *reportUplinkTxDirectCurrent*, *reportUplinkTxDirectCurrentTwoCarrier* or *reportUplinkTxDirectCurrentMoreCarrier* in one RRC message. + +- 2> if the *RRReconfiguration* message includes the *mrdc-SecondaryCellGroupConfig* with *mrdc-SecondaryCellGroup* set to *eutra-SCG*: + - 3> include in the *eutra-SCG-Response* the E-UTRA *RRConnectionReconfigurationComplete* message in accordance with TS 36.331 [10] clause 5.3.5.3; +- 2> if the *RRReconfiguration* message includes the *mrdc-SecondaryCellGroupConfig* with *mrdc-SecondaryCellGroup* set to *nr-SCG*: + - 3> include in the *nr-SCG-Response* the SCG *RRReconfigurationComplete* message; + - 3> if the *RRReconfiguration* message is applied due to conditional reconfiguration execution and the *RRReconfiguration* message does not include the *reconfigurationWithSync* in the *masterCellGroup*: + - 4> include in the *selectedCondRRReconfig* the *condReconfigId* for the selected cell of conditional reconfiguration execution; + - 4> if a new *sk-Counter* value has been selected due to the conditional reconfiguration execution for subsequent CPAC: + +- 5> include *selectedSK-Counter* and set its value to the selected *sk-Counter* value; +- 3> if the *RRReconfiguration* message is applied due to conditional reconfiguration execution and *condExecutionCondPSCell* is configured for the selected PSCell: + - 4> include in the *selectedPSCellForCHO-WithSCG* and set it to the information of the selected PSCell; +- 2> if the *RRReconfiguration* includes the *reconfigurationWithSync* in *spCellConfig* of an MCG: + - 3> if the UE has logged measurements available for NR and if the RPLMN is included in *plmn-IdentityList* stored in *VarLogMeasReport*; or + - 3> if the UE has logged measurements available for NR and if the current registered SNPN is included in *snpn-ConfigIDList* stored in the *VarLogMeasReport*: + - 4> include the *logMeasAvailable* in the *RRReconfigurationComplete* message; + - 4> if Bluetooth measurement results are included in the logged measurements the UE has available for NR: + - 5> include the *logMeasAvailableBT* in the *RRReconfigurationComplete* message; + - 4> if WLAN measurement results are included in the logged measurements the UE has available for NR: + - 5> include the *logMeasAvailableWLAN* in the *RRReconfigurationComplete* message; + - 3> if the *sigLoggedMeasType* in *VarLogMeasReport* is included; or + - 3> if the UE is capable of reporting availability of signalling based logged MDT for inter-RAT (i.e. LTE to NR), and if the *sigLoggedMeasType* in *VarLogMeasReport* of TS 36.331 [10] is included: + - 4> if T330 timer is running (associated to the logged measurement configuration for NR or for LTE): + - 5> set *sigLogMeasConfigAvailable* to *true* in the *RRReconfigurationComplete* message; + - 4> else: + - 5> if the UE has logged measurements: + - 6> set *sigLogMeasConfigAvailable* to *false* in the *RRReconfigurationComplete* message; +- 3> if the UE has connection establishment failure or connection resume failure information available in *VarConnEstFailReport* or *VarConnEstFailReportList* and if the RPLMN is equal to *plmn-Identity* stored in *VarConnEstFailReport* or in at least one of the entries of *VarConnEstFailReportList*; or +- 3> if the UE has connection establishment failure information or connection resume failure information available in *VarConnEstFailReport* or *VarConnEstFailReportList* and if the registered SNPN identity is equal to *snpn-identity* stored in *VarConnEstFailReport* or any entry of *VarConnEstFailReportList*: + +- 4> include *connEstFailInfoAvailable* in the *RRReconfigurationComplete* message; +- 3> if the UE has radio link failure or handover failure information available in *VarRLF-Report* and if the RPLMN is included in *plmn-IdentityList* stored in *VarRLF-Report*; or +- 3> if the UE has radio link failure or handover failure information available in *VarRLF-Report* of TS 36.331 [10] and if the UE is capable of cross-RAT RLF reporting and if the RPLMN is included in *plmn-IdentityList* stored in *VarRLF-Report* of TS 36.331 [10]; or +- 3> if the UE has radio link failure or handover failure information available in *VarRLF-Report* and if the current registered SNPN is included in *snpn-IdentityList* stored in *VarRLF-Report*: + - 4> include *rlf-InfoAvailable* in the *RRReconfigurationComplete* message; +- 3> if the UE was configured with *successHO-Config* when connected to the source PCell; and +- 3> if the applied *RRReconfiguration* is not due to a conditional reconfiguration execution upon cell selection performed while timer T311 was running, as defined in 5.3.7.3: + - 4> perform the actions for the successful handover report determination as specified in clause 5.7.10.6, upon successfully completing the Random Access procedure triggered for the *reconfigurationWithSync* in *spCellConfig* of the MCG; +- 3> if the UE has successful handover information available in *VarSuccessHO-Report* and if the RPLMN is included in *plmn-IdentityList* stored in *VarSuccessHO-Report*; or +- 3> if the UE has successful handover information available in *VarSuccessHO-Report* and if the current registered SNPN is included in *snpn-IdentityList* stored in the *VarSuccessHO-Report*: + - 4> include *successHO-InfoAvailable* in the *RRReconfigurationComplete* message; +- 3> if the UE supports logging the successful PSCell change or addition information, release *successPSCell-Config* configured by the source PCell, if available; +- 3> if the UE has successful PSCell change or addition information available in *VarSuccessPSCell-Report* and if the RPLMN is included in *plmn-IdentityList* stored in *VarSuccessPSCell-Report*; or +- 3> if the UE has successful PSCell change or addition information available in *VarSuccessPSCell-Report* and if the current registered SNPN is included in *snpn-IdentityList* stored in the *VarSuccessPSCell-Report*: + - 4> include *successPSCell-InfoAvailable* in the *RRReconfigurationComplete* message; +- 2> if the *RRReconfiguration* message was received via SRB1, but not within *mrdc-SecondaryCellGroup* or E-UTRA *RRConnectionReconfiguration* or E-UTRA *RRConnectionResume*: + - 3> if the UE is configured to provide the measurement gap requirement information of NR target bands: + +- 4> if the *RRReconfiguration* message includes the *needForGapsConfigNR*; or +- 4> if the *NeedForGapsInfoNR* information is changed compared to last time the UE reported this information; or +- 4> if the *RRReconfiguration* message includes the *needForInterruptionConfigNR* and set it to *enabled*; or +- 4> if the *needForInterruptionConfigNR* is enabled and the *NeedForInterruptionInfoNR* information is changed compared to last time the UE reported this information: + - 5> include the *NeedForGapsInfoNR* and set the contents as follows: + - 6> include *intraFreq-needForGap* and set the gap requirement information of intra-frequency measurement for each NR serving cell; + - 6> if *requestedTargetBandFilterNR* is configured: + - 7> for each supported NR band that is also included in *requestedTargetBandFilterNR*, include an entry in *interFreq-needForGap* and set the gap requirement information for that band; + - 6> else: + - 7> include an entry in *interFreq-needForGap* and set the corresponding gap requirement information for each supported NR band; + - 5> if the *needForInterruptionConfigNR* is enabled: + - 6> include the *needForInterruptionInfoNR* and set the contents as follows: + - 7> include *intraFreq-needForInterruption* with the same number of entries, and listed in the same order, as in *intraFreq-needForGap*; + - 7> for each entry in *intraFreq-needForInterruption*, include *interruptionIndication* and set the interruption requirement information if the corresponding entry in *intraFreq-needForGap* is set to *no-gap*; + - 7> include *interFreq-needForInterruption* with the same number of entries, and listed in the same order, as in *interFreq-needForGap*; + - 7> for each entry in *interFreq-needForInterruption*, include *interruptionIndication* and set the interruption requirement information if the corresponding entry in *interFreq-needForGap* is set to *no-gap*; +- 3> if the UE is configured to provide the measurement gap and NCSG requirement information of NR target bands: + - 4> if the *RRReconfiguration* message includes the *needForGapNCSG-ConfigNR*; or + - 4> if the *needForGapNCSG-InfoNR* information is changed compared to last time the UE reported this information: + - 5> include the *NeedForGapNCSG-InfoNR* and set the contents as follows: + +- 6> include *intraFreq-needForNCSG* and set the gap and NCSG requirement information of intra-frequency measurement for each NR serving cell; + - 6> if *requestedTargetBandFilterNCSG-NR* is configured: + - 7> for each supported NR band included in *requestedTargetBandFilterNCSG-NR*, include an entry in *interFreq-needForNCSG* and set the NCSG requirement information for that band; + - 6> else: + - 7> include an entry for each supported NR band in *interFreq-needForNCSG* and set the corresponding NCSG requirement information; + - 3> if the UE is configured to provide the measurement gap and NCSG requirement information of E-UTRA target bands: + - 4> if the *RRCReconfiguration* message includes the *needForGapNCSG-ConfigEUTRA*; or + - 4> if the *needForGapNCSG-InfoEUTRA* information is changed compared to last time the UE reported this information: + - 5> include the *NeedForGapNCSG-InfoEUTRA* and set the contents as follows: + - 6> if *requestedTargetBandFilterNCSG-EUTRA* is configured, for each supported E-UTRA band included in *requestedTargetBandFilterNCSG-EUTRA*, include an entry in *needForNCSG-EUTRA* and set the NCSG requirement information for that band; otherwise, include an entry for each supported E-UTRA band in *needForNCSG-EUTRA* and set the corresponding NCSG requirement information; + - 2> if the UE has flight path information available: + - 3> if the UE had not previously provided a flight path information since last entering RRC\_CONNECTED state; or + - 3> if at least one waypoint was not previously provided; or + - 3> if at least one upcoming waypoint that was previously provided is being removed; or + - 3> if *flightPathUpdateDistanceThr* is configured and for at least one waypoint, the 3D distance between the previously provided location and the new location is more than or equal to the distance threshold configured by *flightPathUpdateDistanceThr*; or + - 3> if *flightPathUpdateTimeThr* is configured and for at least one waypoint, the timestamp was not previously provided but is now available, or the time between the previously provided timestamp and the new timestamp, if available, is more than or equal to the time threshold configured by *flightPathUpdateTimeThr*: + - 4> include *flightPathInfoAvailable*; +- NOTE 0c: If neither *flightPathUpdateDistanceThr* nor *flightPathUpdateTimeThr* is configured, it is up to UE implementation whether to include *flightPathInfoAvailable* when updated flight path information is available. +- 1> if the UE is configured with E-UTRA *nr-SecondaryCellGroupConfig* (UE in (NG)EN-DC): + +- 2> if the *RRReconfiguration* message was received via E-UTRA SRB1 as specified in TS 36.331 [10]; or +- 2> if the *RRReconfiguration* message was received via E-UTRA RRC message *RRConnectionReconfiguration* within *MobilityFromNRCommand* (handover from NR standalone to (NG)EN-DC); + - 3> if the *RRReconfiguration* is applied due to a conditional reconfiguration execution for CPC which is configured via *conditionalReconfiguration* contained in *nr-SecondaryCellGroupConfig* specified in TS 36.331 [10]: + - 4> submit the *RRReconfigurationComplete* message via the E-UTRA MCG embedded in E-UTRA RRC message *ULInformationTransferMRDC* as specified in TS 36.331 [10], clause 5.6.2a. + - 3> else if the *RRReconfiguration* message was included in E-UTRA *RRConnectionResume* message: + - 4> submit the *RRReconfigurationComplete* message via E-UTRA embedded in E-UTRA RRC message *RRConnectionResumeComplete* as specified in TS 36.331 [10], clause 5.3.3.4a; + - 3> else: + - 4> submit the *RRReconfigurationComplete* via E-UTRA embedded in E-UTRA RRC message *RRConnectionReconfigurationComplete* as specified in TS 36.331 [10], clause 5.3.5.3/5.3.5.4/5.4.2.3; + - 3> if the *scg-State* is not included in the E-UTRA message (*RRConnectionReconfiguration* or *RRConnectionResume*) containing the *RRReconfiguration* message: + - 4> perform SCG activation as specified in 5.3.5.13a; + - 4> if *reconfigurationWithSync* was included in *spCellConfig* of an SCG: + - 5> initiate the Random Access procedure on the PSCell, as specified in TS 38.321 [3]; + - 4> else if the SCG was deactivated before the reception of the E-UTRA RRC message containing the *RRReconfiguration* message: + - 5> if *bfd-and-RLM* was not configured to *true* before the reception of the E-UTRA *RRConnectionReconfiguration* or *RRConnectionResume* message containing the *RRReconfiguration* message or if lower layers indicate that a Random Access procedure is needed for SCG activation: + - 6> initiate the Random Access procedure on the SpCell, as specified in TS 38.321 [3]; + - 5> else the procedure ends; + - 4> else the procedure ends; + - 3> else: + - 4> perform SCG deactivation as specified in 5.3.5.13b; + +4> the procedure ends; + +2> if the *RRCREconfiguration* message was received within *nr-SecondaryCellGroupConfig* in *RRRConnectionReconfiguration* message received via SRB3 within *DLInformationTransferMRDC*: + +3> submit the *RRCREconfigurationComplete* via E-UTRA embedded in E-UTRA RRC message *RRRConnectionReconfigurationComplete* as specified in TS 36.331 [10], clause 5.3.5.3/5.3.5.4; + +3> if the *scg-State* is not included in the *RRRConnectionReconfiguration*: + +4> if *reconfigurationWithSync* was included in *spCellConfig* of an SCG: + +5> initiate the Random Access procedure on the SpCell, as specified in TS 38.321 [3]; + +4> else the procedure ends; + +3> else: + +4> perform SCG deactivation as specified in 5.3.5.13b; + +4> the procedure ends; + +NOTE 1: The order the UE sends the *RRRConnectionReconfigurationComplete* message and performs the Random Access procedure towards the SCG is left to UE implementation. + +2> else (*RRCREconfiguration* was received via SRB3) but not within *DLInformationTransferMRDC*: + +3> submit the *RRCREconfigurationComplete* message via SRB3 to lower layers for transmission using the new configuration; + +NOTE 2: In (NG)EN-DC and NR-DC, in the case *RRCREconfiguration* is received via SRB1 or within *DLInformationTransferMRDC* via SRB3, the random access is triggered by RRC layer itself as there is not necessarily other UL transmission. In the case *RRCREconfiguration* is received via SRB3 but not within *DLInformationTransferMRDC*, the random access is triggered by the MAC layer due to arrival of *RRCREconfigurationComplete*. + +1> else if the *RRCREconfiguration* message was received via SRB1 within the *nr-SCG* within *mrdc-SecondaryCellGroup* (UE in NR-DC, *mrdc-SecondaryCellGroup* was received in *RRCREconfiguration* or *RRRResume* via SRB1): + +2> if the *RRCREconfiguration* is applied due to a conditional reconfiguration execution for CPC which is configured via *conditionalReconfiguration* contained in *nr-SCG* within *mrdc-SecondaryCellGroup*; or + +2> if the *RRCREconfiguration* is applied due to an LTM cell switch execution: + +3> submit the *RRCREconfigurationComplete* message via the NR MCG embedded in NR RRC message *ULInformationTransferMRDC* as specified in clause 5.7.2a.3. + +2> if the *scg-State* is not included in the *RRCREconfiguration* or *RRRResume* message containing the *RRCREconfiguration* message: + +- 3> perform SCG activation as specified in 5.3.5.13a; +- 3> if *reconfigurationWithSync* was included in *spCellConfig* in nr-SCG: + - 4> if the *RRReconfiguration* message is not applied due to an LTM cell switch execution for which lower layer indicate to skip the Random Access procedure: + - 5> initiate the Random Access procedure on the PSCell, as specified in TS 38.321 [3]; + - 4> if the UE was configured with *successPSCell-Config* when connected to the source PSCell (for PSCell change) or to the PCell (for PSCell addition or change): + - 5> perform the actions for the successful PSCell change or addition report determination as specified in clause 5.7.10.7, upon successfully completing the Random Access procedure triggered for the *reconfigurationWithSync* in *spCellConfig* of the SCG; +- 3> else if the SCG was deactivated before the reception of the NR RRC message containing the *RRReconfiguration* message: + - 4> if *bfd-and-RLM* was not configured to *true* before the reception of the *RRReconfiguration* or *RRResume* message containing the *RRReconfiguration* message; or + - 4> if lower layers indicate that a Random Access procedure is needed for SCG activation: + - 5> initiate the Random Access procedure on the PSCell, as specified in TS 38.321 [3]; + - 4> else the procedure ends; +- 3> else the procedure ends; +- 2> else + - 3> perform SCG deactivation as specified in 5.3.5.13b; + - 3> the procedure ends; + +NOTE 2a: The order in which the UE sends the *RRReconfigurationComplete* message and performs the Random Access procedure towards the SCG is left to UE implementation. + +- 1> else if the *RRReconfiguration* message was received via SRB3 (UE in NR-DC): + - 2> if the *RRReconfiguration* message was received within *DLInformationTransferMRDC*: + - 3> if the *RRReconfiguration* message was received within the *nr-SCG* within *mrdc-SecondaryCellGroup* (NR SCG RRC Reconfiguration): + - 4> if the *scg-State* is not included in the *RRReconfiguration* message containing the *RRReconfiguration* message: + - 5> if *reconfigurationWithSync* was included in *spCellConfig* in nr-SCG: + +- 6> initiate the Random Access procedure on the PSCell, as specified in TS 38.321 [3]; +- 6> if the UE was configured with *successPSCell-Config* by the PCell or by the source PSCell: + - 7> perform the actions for the successful PSCell change report determination as specified in clause 5.7.10.7, upon successfully completing the Random Access procedure triggered for the *reconfigurationWithSync* in *spCellConfig* of the SCG; +- 5> else: + - 6> the procedure ends; +- 4> else: + - 5> perform SCG deactivation as specified in 5.3.5.13b; + - 5> the procedure ends; +- 3> else: + - 4> if the *RRCREconfiguration* does not include the *mrdc-SecondaryCellGroupConfig*: + - 5> if the *RRCREconfiguration* includes the *scg-State*: + - 6> perform SCG deactivation as specified in 5.3.5.13b; + - 4> submit the *RRCREconfigurationComplete* message via SRB1 to lower layers for transmission using the new configuration; + - 2> else: + - 3> if the *RRCREconfiguration* includes the *reconfigurationWithSync* in *spCellConfig* for the SCG; and + - 3> if the UE was configured with *successPSCell-Config*: + - 4> perform the actions for the successful PSCell change report determination as specified in clause 5.7.10.7, upon successfully completing the Random Access procedure triggered for the *reconfigurationWithSync* in *spCellConfig* of the SCG; + - 3> if the UE has successful PSCell change or addition information available in *VarSuccessPSCell-Report* and if the RPLMN is included in *plmn-IdentityList* stored in *VarSuccessPSCell-Report*; or + - 3> if the UE has successful PSCell change or addition information available in *VarSuccessPSCell-Report* and if the current registered SNPN is included in *snpn-IdentityList* stored in the *VarSuccessPSCell-Report*: + - 4> include *successPSCell-InfoAvailable* in the *RRCREconfigurationComplete* message; + +- 3> submit the *RRCReconfigurationComplete* message via SRB3 to lower layers for transmission using the new configuration; +- 1> else (*RRCReconfiguration* was received via SRB1): + - 2> if the UE is in NR-DC and; + - 2> if the *RRCReconfiguration* does not include the *mrdc-SecondaryCellGroupConfig*: + - 3> if the *RRCReconfiguration* includes the *scg-State*: + - 4> perform SCG deactivation as specified in 5.3.5.13b; + - 3> else: + - 4> perform SCG activation without SN message as specified in 5.3.5.13b1; + - 2> if the *reconfigurationWithSync* was included in *spCellConfig* of an MCG: + - 3> if *ta-Report* or *ta-ReportATG* is configured with value *enabled* and the UE supports TA reporting: + - 4> indicate TA report initiation to lower layers; + - 2> submit the *RRCReconfigurationComplete* message via SRB1 to lower layers for transmission using the new configuration; + - 2> if this is the first *RRCReconfiguration* message after successful completion of the RRC re-establishment procedure: + - 3> resume SRB2, SRB4, DRBs, multicast MRB, and BH RLC channels for IAB-MT, and Uu Relay RLC channels for L2 U2N Relay UE, that are suspended; +- 1> if *sl-IndirectPathAddChange* was included in *RRCReconfiguration* message and if SRB1 is configured as split SRB and *pdcp-Duplication* is configured: + - 2> when successfully sending *RRCReconfigurationComplete* message via SL indirect path (i.e., PC5 RLC acknowledgement is received from target L2 U2N Relay UE): + - 3> stop timer T421; +- 1> if *reconfigurationWithSync* was included in *spCellConfig* of an MCG or SCG and when MAC of an NR cell group successfully completes a Random Access procedure triggered above; or, +- 1> if *sl-PathSwitchConfig* was included in *reconfigurationWithSync* included in *spCellConfig* of an MCG, and when successfully sending *RRCReconfigurationComplete* message (i.e., PC5 RLC acknowledgement is received from target L2 U2N Relay UE); or, +- 1> if *rach-LessHO* was included in *reconfigurationWithSync* included in *spCellConfig* of an MCG, and upon indication from lower layers that the RACH-less handover has been successfully completed; or, + +1> if *reconfigurationWithSync* was included in *spCellConfig* of an MCG or SCG and the *RRCREconfiguration* message is applied due to an LTM cell switch execution and upon an indication from lower layer that the LTM cell switch execution has been successfully completed: + +2> stop timer T304 for that cell group if running; + +2> if *sl-PathSwitchConfig* was included in *reconfigurationWithSync*: + +3> stop timer T420; + +3> release all radio resources, including release of the RLC entities and the MAC configuration at the source side; + +3> reset MAC used in the source cell; + +2> if *rach-LessHO* was included in *reconfigurationWithSync* and *cg-NTN-RACH-Less-Configuration* was configured: + +3> release the uplink grant configured for RACH-less handover in *cg-NTN-RACH-Less-Configuration*; + +NOTE 2b: PDCP and SDAP configured by the source prior to the path switch that are reconfigured and re-used by target when delta signalling is used, are not released as part of this procedure. + +2> stop timer T310 for source SpCell if running; + +2> apply the parts of the CSI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the respective target SpCell, if any; + +2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the respective target SpCell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of that target SpCell; + +2> for each DRB configured as DAPS bearer, request uplink data switching to the PDCP entity, as specified in TS 38.323 [5]; + +2> if the *reconfigurationWithSync* was included in *spCellConfig* of an MCG: + +3> if T390 is running: + +4> stop timer T390 for all access categories; + +4> perform the actions as specified in 5.3.14.4. + +3> if T350 is running: + +4> stop timer T350; + +3> if *RRCREconfiguration* does not include *dedicatedSIB1-Delivery* and + +- 3> if the active downlink BWP, which is indicated by the *firstActiveDownlinkBWP-Id* for the target SpCell of the MCG, has a common search space configured by *searchSpaceSIB1*: + - 4> acquire the *SIB1*, which is scheduled as specified in TS 38.213 [13], of the target SpCell of the MCG; + - 4> upon acquiring *SIB1*, perform the actions specified in clause 5.2.2.4.2; +- 2> if the *RRCREconfiguration* message is applied due to a conditional reconfiguration execution and the *subsequentCondReconfig* is included in the entry in *VarConditionalReconfig* containing the *RRCREconfiguration* message: + - 3> for each *condReconfigId* included in *condExecutionCondToAddModList* within *subsequentCondReconfig*: + - 4> replace within *VarConditionalReconfig* the entry in *condExecutionCond* or *condExecutionCondSCG* with the matching *condReconfigId* value; +- 2> if the *reconfigurationWithSync* was included in *spCellConfig* of an MCG; or +- 2> if the *reconfigurationWithSync* was included in *spCellConfig* of an SCG and the CPA, CPC, or subsequent CPAC was configured: + - 3> remove all the entries in the *condReconfigList* within the MCG and the SCG *VarConditionalReconfig* except for the entries in which *subsequentCondReconfig* is present, if any; + - 3> remove all the entries within *VarConditionalReconfiguration* as specified in TS 36.331 [10], clause 5.3.5.9.6, if any; + - 3> for each *measId* of the MCG *measConfig*, if configured, and for each *measId* of the SCG *measConfig*, if configured, if the associated *reportConfig* has a *reportType* set to *condTriggerConfig*: + - 4> if the *reportConfigId* is not associated with any *measId* indicated by the *condExecutionCond* or the *condExecutionCondSCG* in an entry of *condReconfigList* in *VarConditionalReconfig* in which *subsequentCondReconfig* is included: + - 5> remove the entry with the matching *reportConfigId* from the *reportConfigList* within the *VarMeasConfig*; + - 4> if the associated *measObjectId* is only associated to a *reportConfig* with *reportType* set to *condTriggerConfig*; and + - 4> if the *measObjectId* is not associated with any *measId* indicated by the *condExecutionCond* or the *condExecutionCondSCG* in an entry of *condReconfigList* in *VarConditionalReconfig* in which *subsequentCondReconfig* is included: + - 5> remove the entry with the matching *measObjectId* from the *measObjectList* within the *VarMeasConfig*; + - 4> remove the entry with the matching *measId* from the *measIdList* within the *VarMeasConfig*; +- 2> if *reconfigurationWithSync* was included in *masterCellGroup* or *secondaryCellGroup*: + - 3> if the UE initiated transmission of a *UEAssistanceInformation* message for the corresponding cell group during the last 1 second, and the UE is still configured to provide the concerned UE assistance information for the corresponding cell group; or + +- 3> if the *RRCREconfiguration* message is applied due to a conditional reconfiguration execution or an LTM cell switch procedure, and the UE is configured to provide UE assistance information for the corresponding cell group, and the UE has initiated transmission of a *UEAssistanceInformation* message for the corresponding cell group since it was configured to do so in accordance with 5.7.4.2: + - 4> initiate transmission of a *UEAssistanceInformation* message for the corresponding cell group in accordance with clause 5.7.4.3 to provide the concerned UE assistance information; + - 4> start or restart the prohibit timer (if exists) or the leave without response timer for the MUSIM associated with the concerned UE assistance information with the timer value set to the value in corresponding configuration; +- 3> if *SIB12* is provided by the target PCell, and the UE initiated transmission of a *SidelinkUEInformationNR* message indicating a change of NR sidelink communication/discovery related parameters relevant in target PCell (i.e. change of *sl-RxInterestedFreqList* or *sl-TxResourceReqList*) during the last 1 second preceding reception of the *RRCREconfiguration* message including *reconfigurationWithSync* in *spCellConfig* of an MCG; or +- 3> if the *RRCREconfiguration* message is applied due to a conditional reconfiguration execution and the UE is capable of NR sidelink communication/discovery and *SIB12* is provided by the target PCell, and the UE has initiated transmission of a *SidelinkUEInformationNR* message since it was configured to do so in accordance with 5.8.3.2: + - 4> initiate transmission of the *SidelinkUEInformationNR* message in accordance with 5.8.3.3; +- 2> if *reconfigurationWithSync* was included in *masterCellGroup*: + - 3> if configured with application layer measurements and if application layer measurement report container has been received from upper layers for which the successful transmission of the message or at least one segment of the message has not been confirmed by lower layers: + - 4> re-submit the *MeasurementReportAppLayer* message or all segments of the *MeasurementReportAppLayer* message to lower layers for transmission via SRB4; +- 2> if *reconfigurationWithSync* was included in *masterCellGroup* and the target cell provides *SIB21*: + - 3> if the UE initiated transmission of an *MBSInterestIndication* message during the last 1 second preceding reception of this *RRCREconfiguration* message; or + - 3> if the *RRCREconfiguration* message is applied due to a conditional reconfiguration execution, and the UE has initiated transmission of an *MBSInterestIndication* message after having received this *RRCREconfiguration* message: + - 4> initiate transmission of an *MBSInterestIndication* message in accordance with clause 5.9.4; +- 2> the procedure ends. + +NOTE 3: The UE is only required to acquire broadcasted *SIB1* if the UE can acquire it without disrupting unicast or MBS multicast data reception, i.e. the broadcast and unicast/MBS multicast beams are quasi co-located. + +NOTE 4: The UE sets the content of *UEAssistanceInformation* according to latest configuration (i.e. the configuration after applying the *RRCREconfiguration* message) and latest UE preference. The UE may include more than the concerned UE assistance information within the *UEAssistanceInformation* according to 5.7.4.2. Therefore, the content of *UEAssistanceInformation* message might not be the same as the content of the previous *UEAssistanceInformation* message. + +### 5.3.5.4 Secondary cell group release + +The UE shall: + +- 1> as a result of SCG release triggered by E-UTRA (i.e. (NG)EN-DC case) or NR (i.e. NR-DC case): + - 2> reset SCG MAC, if configured; + - 2> for each RLC bearer that is part of the SCG configuration: + - 3> perform RLC bearer release procedure as specified in 5.3.5.5.3; + - 2> for each BH RLC channel that is part of the SCG configuration: + - 3> perform BH RLC channel release procedure as specified in 5.3.5.5.10; + - 2> release the SCG configuration; + - 2> for all application layer measurement configurations that are part of the SCG configuration: + - 3> inform upper layers about the release of the application layer measurement configurations; + - 3> discard any application layer measurement reports which were not yet submitted to lower layers for transmission; + - 2> remove all the entries within the SCG *VarConditionalReconfig*, if any; + - 2> if SCG release was triggered by NR (i.e. NR-DC case): + - 3> remove all the entries in the *condReconfigList* within the MCG *VarConditionalReconfig* for which the *RRCREconfiguration* within *condRRCREconfig* does not include the *masterCellGroup* with *reconfigurationWithSync* and for which *subsequentCondReconfig* is not present, if any; + - 2> else (i.e. EN-DC case): + - 3> perform *VarConditionalReconfiguration* CPC removal as specified in TS 36.331 [10] clause 5.3.5.9.7; + - 2> stop timer T310 for the corresponding SpCell, if running; + - 2> stop timer T312 for the corresponding SpCell, if running; + - 2> stop timer T304 for the corresponding SpCell, if running. + +NOTE: Release of cell group means only release of the lower layer configuration of the cell group but the *RadioBearerConfig* may not be released. + +### 5.3.5.5 Cell Group configuration + +#### 5.3.5.5.1 General + +The network configures the UE with Master Cell Group (MCG), and zero or one Secondary Cell Group (SCG). In (NG)EN-DC, the MCG is configured as specified in TS 36.331 [10], and for NE-DC, the SCG is configured as specified in TS 36.331 [10]. The network provides the configuration parameters for a cell group in the *CellGroupConfig* IE. + +The UE performs the following actions based on a received *CellGroupConfig* IE: + +- 1> if the *CellGroupConfig* contains the *spCellConfig* with *reconfigurationWithSync*: + - 2> perform Reconfiguration with sync according to 5.3.5.5.2; + - 2> resume all suspended radio bearers except the SRBs for the source cell group, and resume SCG transmission for all radio bearers, and resume BH RLC channels and resume SCG transmission for BH RLC channels for IAB-MT, if suspended; + +NOTE 1: If the SCG is deactivated, resuming SCG transmission for all radio bearers does not imply that PDCP PDUs can be transmitted or received on SCG RLC bearers. + +- 1> if the *CellGroupConfig* contains the *rlc-BearerToReleaseList* or *rlc-BearerToReleaseListExt*: + - 2> perform RLC bearer release as specified in 5.3.5.5.3; +- 1> if the *CellGroupConfig* contains the *rlc-BearerToAddModList*: + - 2> perform the RLC bearer addition/modification as specified in 5.3.5.5.4; +- 1> if the *CellGroupConfig* contains the *mac-CellGroupConfig*: + - 2> configure the MAC entity of this cell group as specified in 5.3.5.5.5; +- 1> if the *CellGroupConfig* contains the *sCellToReleaseList*: + - 2> perform SCell release as specified in 5.3.5.5.8; +- 1> if the *CellGroupConfig* contains the *spCellConfig*: + - 2> configure the SpCell as specified in 5.3.5.5.7; +- 1> if the *CellGroupConfig* contains the *sCellToAddModList*: + - 2> perform SCell addition/modification as specified in 5.3.5.5.9; + +- 1> if the *CellGroupConfig* contains the *bh-RLC-ChannelToReleaseList*: + - 2> perform BH RLC channel release as specified in 5.3.5.5.10; +- 1> if the *CellGroupConfig* contains the *bh-RLC-ChannelToAddModList*: + - 2> perform the BH RLC channel addition/modification as specified in 5.3.5.5.11; +- 1> if the *CellGroupConfig* contains the *uu-RelayRLC-ChannelToReleaseList*: + - 2> perform Uu Relay RLC channel release as specified in 5.3.5.5.12; +- 1> if the *CellGroupConfig* contains the *uu-RelayRLC-ChannelToAddModList*: + - 2> perform the Uu Relay RLC channel addition/modification as specified in 5.3.5.5.13; +- 1> if the *CellGroupConfig* contains the *ncr-FwdConfig*: + - 2> perform the NCR-Fwd configuration as specified in 5.3.5.5.14; +- 1> if the *CellGroupConfig* contains the *autonomousDenialParameters*: + - 2> consider itself to be allowed to deny any transmission in a particular UL slot if during the number of slots indicated by *autonomousDenialValidity*, preceding and including this particular slot, it autonomously denied fewer UL slots than indicated by *autonomousDenialSlots* within the same cell group; + +NOTE 2: When counting the number of denied UL slots, the UE sums up the denied UL slots across all serving cells within the same cell group. When counting the number of slots indicated by *autonomousDenialValidity*, the UE sums up the UL slots across all serving cells within the same cell group. + +NOTE 3: When multiple denied UL slots across all serving cells partially or fully overlap in the time domain, the number of denied UL slots across all serving cells is counted as one denied UL slot, based on the longest slot. + +#### 5.3.5.5.2 Reconfiguration with sync + +The UE shall perform the following actions to execute a reconfiguration with sync. + +- 1> if the AS security is not activated, perform the actions upon going to RRC\_IDLE as specified in 5.3.11 with the release cause 'other' upon which the procedure ends; +- 1> stop timer T430 if running; +- 1> if no DAPS bearer is configured: + - 2> stop timer T310 for the corresponding SpCell, if running; +- 1> if this procedure is executed for the MCG: + +- 2> if timer T316 is running; + - 3> stop timer T316; + - 3> if the UE supports RLF-Report for fast MCG recovery procedure: + - 4> set the *elapsedTimeT316* in the *VarRLF-Report* to the value of the elapsed time of the timer T316; + - 4> set the *pSCellId* to the global cell identity of the PSCell, if available, otherwise to the physical cell identity and carrier frequency of the PSCell; + - 3> else: + - 4> clear the information included in *VarRLF-Report*, if any; +- 2> resume MCG transmission, if suspended. +- 1> stop timer T312 for the corresponding SpCell, if running; +- 1> if *sl-PathSwitchConfig* is included: + - 2> consider the target L2 U2N Relay UE to be the one indicated by the *targetRelayUE-Identity* in the *sl-PathSwitchConfig*; + - 2> start timer T420 for the corresponding target L2 U2N Relay UE with the timer value set to *t420*, as included in the *sl-PathSwitchConfig*; + - 2> apply the value of the *newUE-Identity* as the C-RNTI; + - 2> indicate to upper layer (to trigger the PC5 unicast link establishment) with the target L2 U2N Relay UE indicated by the *targetRelayUE-Identity*; + - 2> apply the default configuration of SL-RLC1 as defined in 9.2.4 for SRB1; +- 1> else (*sl-PathSwitchConfig* is not included): + - 2> if this procedure is executed for the MCG or if this procedure is executed for an SCG not indicated as deactivated in the E-UTRA or NR RRC message in which the *RRCReconfiguration* message is embedded: + - 3> start timer T304 for the corresponding SpCell with the timer value set to *t304*, as included in the *reconfigurationWithSync*; + - 2> if the *frequencyInfoDL* is included: + - 3> consider the target SpCell to be one on the SSB frequency indicated by the *frequencyInfoDL* with a physical cell identity indicated by the *physCellId*; + - 2> else: + - 3> consider the target SpCell to be one on the SSB frequency of the source SpCell with a physical cell identity indicated by the *physCellId*; + +- 2> start synchronising to the DL of the target SpCell; +- 2> apply the specified BCCH configuration defined in 9.1.1.1 for the target SpCell; +- 2> acquire the *MIB* of the target SpCell, which is scheduled as specified in TS 38.213 [13]; +- 2> if *NTN-Config* is configured for the target cell: + - 3> start timer T430 with the timer value set to *ntn-UISyncValidityDuration* from the subframe indicated by *epochTime*, according to the target cell *NTN-Config*; + +NOTE 1: The UE should perform the reconfiguration with sync as soon as possible following the reception of the RRC message triggering the reconfiguration with sync, which could be before confirming successful reception (HARQ and ARQ) of this message. + +NOTE 2: The UE may omit reading the *MIB* if the UE already has the required timing information, or the timing information is not needed for random access. + +NOTE 2a: A UE with DAPS bearer does not monitor for system information updates in the source PCell. + +- 2> If any DAPS bearer is configured: + - 3> create a MAC entity for the target cell group with the same configuration as the MAC entity for the source cell group; + - 3> for each DAPS bearer: + - 4> establish an RLC entity or entities for the target cell group, with the same configurations as for the source cell group; + - 4> establish the logical channel for the target cell group, with the same configurations as for the source cell group; + +NOTE 2b: In order to understand if a DAPS bearer is configured, the UE needs to check the presence of the field *daps-Config* within the *RadioBearerConfig* IE received in *radioBearerConfig* or *radioBearerConfig2*. + +- 3> for each SRB: + - 4> establish an RLC entity for the target cell group, with the same configurations as for the source cell group; + - 4> establish the logical channel for the target cell group, with the same configurations as for the source cell group; +- 3> suspend SRBs for the source cell group; + +NOTE 3: Void + +- 3> apply the value of the *newUE-Identity* as the C-RNTI in the target cell group; +- 3> configure lower layers for the target SpCell in accordance with the received *spCellConfigCommon*; + +- 3> configure lower layers for the target SpCell in accordance with any additional fields, not covered in the previous, if included in the received *reconfigurationWithSync*. +- 2> else: + - 3> reset the MAC entity of this cell group; + - 3> consider the SCell(s) of this cell group, if configured, that are not included in the *SCellToAddModList* in the *RRCReconfiguration* message, to be in deactivated state; + - 3> apply the value of the *newUE-Identity* as the C-RNTI for this cell group; + - 3> configure lower layers in accordance with the received *spCellConfigCommon*; + - 3> if *rach-LessHO* is included: + - 4> configure lower layers in accordance with *rach-LessHO* for the target SpCell; + - 3> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the received *reconfigurationWithSync*. +- 2> if the UE is acting as L2 U2N Remote UE at the source side: + - 3> indicate upper layer to trigger PC5 unicast link release. + +Upon L2 U2N Relay UE receiving *reconfigurationWithSync*, it either indicates to upper layers (to trigger PC5 unicast link release) or sends *NotificationMessageSidelink* message to the connected L2 U2N Remote UE(s) in accordance with 5.8.9.10. + +### 5.3.5.5.3 RLC bearer release + +The UE shall: + +- 1> for each *logicalChannelIdentity/LogicalChannelIdentityExt* value included in the *rlc-BearerToReleaseList/rlc-BearerToReleaseListExt* that is part of the current UE configuration within the same cell group (LCH release); or +- 1> for each *logicalChannelIdentity* value that is to be released as the result of an SCG release according to 5.3.5.4: + - 2> release the RLC entity or entities as specified in TS 38.322 [4], clause 5.1.3; + - 2> release the corresponding logical channel. + +### 5.3.5.5.4 RLC bearer addition/modification + +For each *RLC-BearerConfig* received in the *rlc-BearerToAddModList* IE the UE shall: + +- 1> if the UE's current configuration contains an RLC bearer with the received *logicalChannelIdentity/LogicalChannelIdentityExt* within the same cell group: + - 2> if the RLC bearer is associated with an DAPS bearer, or + - 2> if any DAPS bearer is configured and the RLC bearer is associated with an SRB: + - 3> reconfigure the RLC entity or entities for the target cell group in accordance with the received *rlc-Config*; + - 3> reconfigure the logical channel for the target cell group in accordance with the received *mac-LogicalChannelConfig*; + - 2> else: + - 3> if *reestablishRLC* is received: + - 4> re-establish the RLC entity as specified in TS 38.322 [4]; + - 3> reconfigure the RLC entity or entities in accordance with the received *rlc-Config*; + - 3> reconfigure the logical channel in accordance with the received *mac-LogicalChannelConfig*; + - 3> if *servedMBS-RadioBearer* is received: + - 4> associate this logical channel with the PDCP entity identified by *servedMBS-RadioBearer*; + +NOTE 1: For DRB and SRB, the network does not re-associate an already configured logical channel with another radio bearer. Hence, *servedRadioBearer* is not present in this case. For MRB, the network does not re-associate an already configured logical channel with DRB or SRB or another MRB (i.e. MRB with another PDCP entity). Hence *multicastRLC-BearerConfig* is not present in this case. If a radio bearer is released and another is added with the same radio bearer identity, it is considered as a new (different) radio bearer. Hence, the network also releases the RLC bearer(s) associated with the released radio bearer. + +NOTE 2: In DAPS handover, the UE may perform RLC entity re-establishment (if *reestablishRLC* is set) for an RLC bearer associated with a non-DAPS bearer when indication of successful completion of random access towards target cell is received from lower layers as specified in TS 38.321 [3]. + +- 1> else (a logical channel with the given *logicalChannelIdentity/LogicalChannelIdentityExt* is not configured within the same cell group, including the case when full configuration option is used): + - 2> if the *servedRadioBearer* associates the logical channel with an SRB and *rlc-Config* is not included: + - 3> establish an RLC entity in accordance with the default configuration defined in 9.2 for the corresponding SRB; + - 2> else: + - 3> establish an RLC entity in accordance with the received *rlc-Config*; + - 2> if the *servedRadioBearer* associates the logical channel with an SRB and if *mac-LogicalChannelConfig* is not included: + +3> configure this MAC entity with a logical channel in accordance to the default configuration defined in 9.2 for the corresponding SRB; + +2> else: + +3> configure this MAC entity with a logical channel in accordance to the received *mac-LogicalChannelConfig*; + +2> associate this logical channel with the PDCP entity identified by *servedRadioBearer* or *servedMBS-RadioBearer*. + +#### 5.3.5.5.5 MAC entity configuration + +The UE shall: + +1> if SCG MAC is not part of the current UE configuration (i.e. SCG establishment): + +2> create an SCG MAC entity; + +1> if any DAPS bearer is configured: + +2> reconfigure the MAC main configuration for the target cell group in accordance with the received *mac-CellGroupConfig* excluding *tag-ToReleaseList* and *tag-ToAddModList*; + +1> else: + +2> reconfigure the MAC main configuration of the cell group in accordance with the received *mac-CellGroupConfig* excluding *tag-ToReleaseList* and *tag-ToAddModList*; + +1> if the received *mac-CellGroupConfig* includes the *tag-ToReleaseList*: + +2> for each *TAG-Id* value included in the *tag-ToReleaseList* that is part of the current UE configuration: + +3> release the TAG indicated by *TAG-Id*; + +1> if the received *mac-CellGroupConfig* includes the *tag-ToAddModList*: + +2> for each *tag-Id* value included in *tag-ToAddModList* that is not part of the current UE configuration (TAG addition): + +3> add the TAG, corresponding to the *tag-Id*, in accordance with the received *timeAlignmentTimer*; + +2> for each *tag-Id* value included in *tag-ToAddModList* that is part of the current UE configuration (TAG modification): + +3> reconfigure the TAG, corresponding to the *tag-Id*, in accordance with the received *timeAlignmentTimer*. + +#### 5.3.5.5.6 RLF Timers & Constants configuration + +The UE shall: + +- 1> if the received *rlf-TimersAndConstants* is set to *release*: + - 2> if any DAPS bearer is configured: + - 3> use values for timers T301, T310, T311 and constants N310, N311 for the target cell group, as included in *ue-TimersAndConstants* received in *SIB1*; + - 2> else: + - 3> use values for timers T301, T310, T311 and constants N310, N311, as included in *ue-TimersAndConstants* received in *SIB1*; +- 1> else: + - 2> if any DAPS bearer is configured: + - 3> configure the value of timers and constants for the target cell group in accordance with received *rlf-TimersAndConstants*; + - 2> else: + - 3> (re-)configure the value of timers and constants in accordance with received *rlf-TimersAndConstants*; + - 3> stop timer T310 for this cell group, if running; + - 3> stop timer T312 for this cell group, if running; + - 3> reset the counters N310 and N311. + +#### 5.3.5.5.7 SpCell Configuration + +The UE shall: + +- 1> if the UE is acting as L2 U2N Remote UE and is not configured with MP: + - 2> if the *SpCellConfig* contains the *rlf-TimersAndConstants* which is set to *setup*: + - 3> use value for timers T311 as received in *rlf-TimersAndConstants*; + - 2> else if *rlf-TimersAndConstants* is not configured for this cell group or *SpCellConfig* contains the *rlf-TimersAndConstants* which is set to *release*: + - 3> use value for timers T311, as included in *ue-TimersAndConstants* received in *SIB1*; +- 1> else + - 2> if the *SpCellConfig* contains the *rlf-TimersAndConstants*: + - 3> configure the RLF timers and constants for this cell group as specified in 5.3.5.5.6; + +- 2> else if *rlf-TimersAndConstants* is not configured for this cell group: + - 3> if any DAPS bearer is configured: + - 4> use values for timers T301, T310, T311 and constants N310, N311 for the target cell group, as included in *ue-TimersAndConstants* received in *SIB1*; + - 3> else + - 4> use values for timers T301, T310, T311 and constants N310, N311, as included in *ue-TimersAndConstants* received in *SIB1*; +- 2> if the *SpCellConfig* contains *spCellConfigDedicated*: + - 3> configure the SpCell in accordance with the *spCellConfigDedicated*; + - 3> consider the bandwidth part indicated in *firstActiveUplinkBWP-Id*, if included in the *spCellConfigDedicated*, to be the active uplink bandwidth part; + - 3> if the *firstActiveDownlinkBWP-Id* is included in the *spCellConfigDedicated*: + - 4> if the *SpCellConfig* is included in an *RRCREconfiguration* message contained in an NR or E-UTRA RRC message indicating that the SCG is deactivated: + - 5> consider the bandwidth part indicated in *firstActiveDownlinkBWP-Id* to be the bandwidth part for Radio Link Monitoring, Beam Failure Detection and measurements; + - 4> else: + - 5> consider the bandwidth part indicated in *firstActiveDownlinkBWP-Id* to be the active downlink bandwidth part; + - 3> if any of the reference signal(s) that are used for radio link monitoring are reconfigured by the received *spCellConfigDedicated*: + - 4> stop timer T310 for the corresponding SpCell, if running; + - 4> stop timer T312 for the corresponding SpCell, if running; + - 4> reset the counters N310 and N311. +- 1> if the *SpCellConfig* contains the *lowMobilityEvaluationConnected*: + - 2> the UE may perform the evaluation of the low mobility criterion for this cell group as specified in 5.7.13.1; +- 1> if the *SpCellConfig* contains the *goodServingCellEvaluationRLM*: + - 2> the UE may perform the evaluation of the good serving cell quality criterion for this SpCell as specified in 5.7.13.2; +- 1> if the *SpCellConfig* contains the *goodServingCellEvaluationBFD*: + +2> the UE may perform the evaluation of the good serving cell quality criterion for this serving cell as specified in 5.7.13.2; + +#### 5.3.5.5.8 SCell Release + +The UE shall: + +- 1> if the release is triggered by reception of the *sCellToReleaseList*: +- 2> for each *sCellIndex* value included in the *sCellToReleaseList*: +- 3> if the current UE configuration includes an SCell with value *sCellIndex*: +- 4> release the SCell. + +#### 5.3.5.5.9 SCell Addition/Modification + +The UE shall: + +- 1> for each *sCellIndex* value included in the *sCellToAddModList* that is not part of the current UE configuration (SCell addition): + - 2> add the SCell, corresponding to the *sCellIndex*, in accordance with the *sCellConfigCommon* and *sCellConfigDedicated*; + - 2> if the *sCellState* is included: + - 3> configure lower layers to consider the SCell to be in activated state; + - 2> else: + - 3> configure lower layers to consider the SCell to be in deactivated state; + - 2> for each *measId* included in the *measIdList* within *VarMeasConfig*: + - 3> if SCells are not applicable for the associated measurement; and + - 3> if the concerned SCell is included in *cellsTriggeredList* defined within the *VarMeasReportList* for this *measId*: + - 4> remove the concerned SCell from *cellsTriggeredList* defined within the *VarMeasReportList* for this *measId*; + - 2> if the *SCellConfig* contains the *goodServingCellEvaluationBFD*: + - 3> the UE may perform the evaluation of the good serving cell quality criterion for this serving cell as specified in 5.7.13.2. +- 1> for each *sCellIndex* value included in the *sCellToAddModList* that is part of the current UE configuration (SCell modification): + +- 2> modify the SCell configuration in accordance with the *sCellConfigDedicated*; +- 2> if the *sCellToAddModList* was received in an *RRReconfiguration* message including *reconfigurationWithSync*, or received in an *RRResume* message, or received in an *RRReconfiguration* message including *reconfigurationWithSync* embedded in an *RRResume* message or embedded in an *RRReconfiguration* message or embedded in an E-UTRA *RRConnectionReconfiguration* message or embedded in an E-UTRA *RRConnectionResume* message, or received in an *RRReconfiguration* message embedded in an *RRReconfiguration* message or embedded in an E-UTRA *RRConnectionReconfiguration* message activating deactivated SCG: + - 3> if the *sCellState* is included: + - 4> configure lower layers to consider the SCell to be in activated state; + - 3> else: + - 4> configure lower layers to consider the SCell to be in deactivated state. +- 2> if the *SCellConfig* contains the *goodServingCellEvaluationBFD*: + - 3> the UE may perform the evaluation of the good serving cell quality criterion for this serving cell as specified in 5.7.13.2. + +#### 5.3.5.5.10 BH RLC channel release + +The IAB-node shall: + +- 1> for each *BH-RLC-ChannelID* value included in the *bh-RLC-ChannelToReleaseList* that is part of the current IAB-node configuration within the same cell group (LCH release); or +- 1> for each *BH-RLC-ChannelID* value that is to be released as the result of an SCG release according to 5.3.5.4: + - 2> release the RLC entity or entities as specified in TS 38.322 [4], clause 5.1.3; + - 2> release the corresponding logical channel. + +#### 5.3.5.5.11 BH RLC channel addition/modification + +For each *BH-RLC-ChannelConfig* received in the *bh-RLC-ChannelToAddModList* IE the IAB-node shall: + +- 1> if the current configuration contains a BH RLC Channel with the received *bh-RLC-ChannelID* within the same cell group: + - 2> if *reestablishRLC* is received: + - 3> re-establish the RLC entity as specified in TS 38.322 [4]; + - 2> reconfigure the RLC entity or entities in accordance with the received *rlc-Config*; + +- 2> reconfigure the logical channel in accordance with the received *mac-LogicalChannelConfig*; +- 1> else (a backhaul logical channel with the given *BH-RLC-ChannelID* was not configured before within the same cell group): + - 2> establish an RLC entity in accordance with the received *rlc-Config*; + - 2> configure this MAC entity with a logical channel in accordance to the received *mac-LogicalChannelConfig*. + +#### 5.3.5.5.12 Uu Relay RLC channel release + +The L2 U2N Relay UE or N3C relay UE shall: + +- 1> for each *Uu-RelayRLC-ChannelID* value included in the *uu-RelayRLC-ChannelToReleaseList* that is part of the current configuration within the same cell group (LCH release): + - 2> release the RLC entity as specified in TS 38.322 [4], clause 5.1.3; + - 2> release the corresponding logical channel. + +#### 5.3.5.5.13 Uu Relay RLC channel addition/modification + +For each *Uu-RelayRLC-ChannelConfig* received in the *uu-RelayRLC-ChannelToAddModList* the L2 U2N Relay UE or N3C relay UE shall: + +- 1> if the current configuration contains a Uu Relay RLC channel with the same *uu-RelayRLC-ChannelID* within the same cell group: + - 2> if *reestablishRLC* is received: + - 3> re-establish the RLC entity as specified in TS 38.322 [4]; + - 2> reconfigure the RLC entity in accordance with the received *rlc-Config*; + - 2> reconfigure the logical channel in accordance with the received *mac-LogicalChannelConfig*; +- 1> else (a logical channel with the given *uu-RelayRLC-ChannelID* was not configured before within the same cell group): + - 2> establish an RLC entity in accordance with the received *rlc-Config*; + - 2> configure this MAC entity with a logical channel in accordance to the received *mac-LogicalChannelConfig*. + +#### 5.3.5.5.14 NCR-Fwd configuration + +The NCR-MT shall: + +- 1> if *NCR-FwdConfig* is set to *setup*: + +- 2> if *NCR-FwdConfig* includes periodic forwarding resource configuration: + - 3> indicate to NCR-Fwd to forward in accordance with the configured periodic forwarding resource set(s); +- 1> else (*NCR-FwdConfig* is set to *release*): + - 2> release NCR-Fwd configuration; + - 2> indicate to NCR-Fwd to cease forwarding. + +### 5.3.5.6 Radio Bearer configuration + +#### 5.3.5.6.1 General + +The UE shall perform the following actions based on a received *RadioBearerConfig* IE: + +- 1> if the *RadioBearerConfig* includes the *srb3-ToRelease*, *srb4-ToRelease* or *srb5-ToRelease*: + - 2> perform the SRB release as specified in 5.3.5.6.2; +- 1> if the *RadioBearerConfig* includes the *srb-ToAddModList* or if any DAPS bearer is configured: + - 2> perform the SRB addition or reconfiguration as specified in 5.3.5.6.3; +- 1> if the *RadioBearerConfig* includes the *drb-ToReleaseList*: + - 2> perform DRB release as specified in 5.3.5.6.4; +- 1> if the *RadioBearerConfig* includes the *drb-ToAddModList*: + - 2> perform DRB addition or reconfiguration as specified in 5.3.5.6.5; +- 1> if the *RadioBearerConfig* includes the *mrb-ToReleaseList*: + - 2> perform multicast MRB release as specified in 5.3.5.6.6; +- 1> if the *RadioBearerConfig* includes the *mrb-ToAddModList*: + - 2> perform multicast MRB addition or reconfiguration as specified in 5.3.5.6.7; +- 1> release all SDAP entities established for the PDU sessions, if any, that have no associated DRB as specified in TS 37.324 [24] clause 5.1.2, and indicate the release of the user plane resources for PDU Sessions associated with the released SDAP entities to upper layers; + +- 1> release all SDAP entities established for the MBS multicast sessions, if any, that have no associated multicast MRB as specified in TS 37.324 [24] clause 5.1.2, and indicate the release of user plane resources for these MBS multicast sessions to upper layers. + +#### 5.3.5.6.2 SRB release + +The UE shall: + +- 1> if *srb3-ToRelease* is included: + - 2> release the PDCP entity and the *srb-Identity* of the SRB3; +- 1> if *srb4-ToRelease* is included + - 2> release the PDCP entity and the *srb-Identity* of the SRB4; +- 1> if *srb5-ToRelease* is included: + - 2> release the PDCP entity and the *srb-Identity* of the SRB5. + +#### 5.3.5.6.3 SRB addition/modification + +The UE shall: + +- 1> If any DAPS bearer is configured, for each SRB: + - 2> establish a PDCP entity for the target cell group as specified in TS 38.323 [5], with the same configuration as the PDCP entity for the source cell group; + - 2> if the *masterKeyUpdate* is received: + - 3> configure the PDCP entity with the security algorithms according to *securityConfig* and apply the keys ( $K_{RRCenc}$ and $K_{RRCint}$ ) associated with the master key ( $K_{gNB}$ ); + - 2> else: + - 3> configure the PDCP entity for the target cell group with state variables continuation as specified in TS 38.323 [5], and with the same security configuration as the PDCP entity for the source cell group; +- 1> for each *srb-Identity* value included in the *srb-ToAddModList* that is not part of the current UE configuration (SRB establishment or reconfiguration from E-UTRA PDCP to NR PDCP): + - 2> establish a PDCP entity; + - 2> if AS security has been activated: + - 3> if target RAT of handover is E-UTRA/5GC; or + +- 3> if the UE is connected to E-UTRA/5GC: + - 4> if the UE is capable of E-UTRA/5GC, but not capable of NGEN-DC: + - 5> configure the PDCP entity with the security algorithms and keys ( $K_{RRCenc}$ and $K_{RRCint}$ ) configured/derived as specified in TS 36.331 [10]; + - 4> else (i.e., UE capable of NGEN-DC): + - 5> configure the PDCP entity with the security algorithms according to *securityConfig* and apply the keys ( $K_{RRCenc}$ and $K_{RRCint}$ ) associated with the master key ( $K_{eNB}$ ) or secondary key ( $S-K_{gNB}$ ) as indicated in *keyToUse*, if applicable; +- 3> else (i.e., UE connected to NR or UE connected to E-UTRA/EPC): + - 4> configure the PDCP entity with the security algorithms according to *securityConfig* and apply the keys ( $K_{RRCenc}$ and $K_{RRCint}$ ) associated with the master key ( $K_{eNB}/K_{gNB}$ ) or secondary key ( $S-K_{gNB}$ ) as indicated in *keyToUse*, if applicable; +- 2> if the current UE configuration as configured by E-UTRA in TS 36.331 [10] includes an SRB identified with the same *srb-Identity* value: + - 3> associate the E-UTRA RLC entity and DCCH of this SRB with the NR PDCP entity; + - 3> release the E-UTRA PDCP entity of this SRB; +- 2> if the *pdcp-Config* is included: + - 3> configure the PDCP entity in accordance with the received *pdcp-Config*; +- 2> else: + - 3> configure the PDCP entity in accordance with the default configuration defined in 9.2.1 for the corresponding SRB; +- 1> if any DAPS bearer is configured, for each *srb-Identity* value included in the *srb-ToAddModList* that is part of the current UE configuration: + - 2> if the *pdcp-Config* is included: + - 3> reconfigure the PDCP entity for the target cell group in accordance with the received *pdcp-Config*; +- 1> else, for each *srb-Identity* value included in the *srb-ToAddModList* that is part of the current UE configuration: + - 2> if the *reestablishPDCP* is set: + - 3> if target RAT of handover is E-UTRA/5GC; or + - 3> if the UE is connected to E-UTRA/5GC: + +4> if the UE is capable of E-UTRA/5GC, but not capable of NGEN-DC: + +5> configure the PDCP entity to apply the integrity protection algorithm and $K_{RRCint}$ key configured/derived as specified in TS 36.331 [10], i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure; + +5> configure the PDCP entity to apply the ciphering algorithm and $K_{RRCenc}$ key configured/derived as specified in TS 36.331 [10], i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure; + +4> else (i.e., a UE capable of NGEN-DC): + +5> configure the PDCP entity to apply the integrity protection algorithm and $K_{RRCint}$ key associated with the master key ( $K_{eNB}$ ) or secondary key ( $S-K_{gNB}$ ), as indicated in *keyToUse*, i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure; + +5> configure the PDCP entity to apply the ciphering algorithm and $K_{RRCenc}$ key associated with the master key ( $K_{eNB}$ ) or secondary key ( $S-K_{gNB}$ ) as indicated in *keyToUse*, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure; + +3> else (i.e., UE connected to NR or UE in EN-DC): + +4> configure the PDCP entity to apply the integrity protection algorithm and $K_{RRCint}$ key associated with the master key ( $K_{eNB}/K_{gNB}$ ) or secondary key ( $S-K_{gNB}$ ), as indicated in *keyToUse*, i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure; + +4> configure the PDCP entity to apply the ciphering algorithm and $K_{RRCenc}$ key associated with the master key ( $K_{eNB}/K_{gNB}$ ) or secondary key ( $S-K_{gNB}$ ) as indicated in *keyToUse*, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure; + +3> re-establish the PDCP entity of this SRB as specified in TS 38.323 [5]; + +2> else, if the *discardOnPDCP* is set: + +3> trigger the PDCP entity to perform SDU discard as specified in TS 38.323 [5]; + +2> if the *pdcp-Config* is included: + +3> reconfigure the PDCP entity in accordance with the received *pdcp-Config*. + +#### 5.3.5.6.4 DRB release + +The UE shall: + +- 1> for each *drb-Identity* value included in the *drb-ToReleaseList* that is part of the current UE configuration; or +- 1> for each *drb-Identity* value that is to be released as the result of full configuration according to 5.3.5.11: + - 2> release the PDCP entity and the *drb-Identity*; + - 2> if SDAP entity associated with this DRB is configured: + - 3> indicate the release of the DRB to SDAP entity associated with this DRB (TS 37.324 [24], clause 5.3.3); + - 2> if the DRB is associated with an *eps-BearerIdentity*: + - 3> if a new bearer is not added either with NR or E-UTRA with same *eps-BearerIdentity*: + - 4> indicate the release of the DRB and the *eps-BearerIdentity* of the released DRB to upper layers. + +NOTE 1: The UE does not consider the message as erroneous if the *drb-ToReleaseList* includes any *drb-Identity* value that is not part of the current UE configuration. + +NOTE 2: Whether or not the RLC and MAC entities associated with this PDCP entity are reset or released is determined by the *CellGroupConfig*. + +#### 5.3.5.6.5 DRB addition/modification + +The UE shall: + +- 1> for each *drb-Identity* value included in the *drb-ToAddModList* that is not part of the current UE configuration (DRB establishment including the case when full configuration option is used): + - 2> establish a PDCP entity and configure it in accordance with the received *pdcp-Config*; + - 2> if the PDCP entity of this DRB is not configured with *cipheringDisabled*: + - 3> if target RAT of handover is E-UTRA/5GC; or + - 3> if the UE is connected to E-UTRA/5GC: + - 4> if the UE is capable of E-UTRA/5GC but not capable of NGEN-DC: + - 5> configure the PDCP entity with the ciphering algorithm and $K_{UPenc}$ key configured/derived as specified in TS 36.331 [10]; + - 4> else (i.e., a UE capable of NGEN-DC): + - 5> configure the PDCP entity with the ciphering algorithms according to *securityConfig* and apply the key ( $K_{UPenc}$ ) associated with the master key ( $K_{eNB}$ ) or secondary key ( $S-K_{eNB}$ ) as indicated in *keyToUse*, if applicable; + +- 3> else (i.e., UE connected to NR or UE connected to E-UTRA/EPC): + - 4> configure the PDCP entity with the ciphering algorithms according to *securityConfig* and apply the $K_{UPenc}$ key associated with the master key ( $K_{eNB}/K_{gNB}$ ) or the secondary key ( $S-K_{gNB}/S-K_{eNB}$ ) as indicated in *keyToUse*; +- 2> if the PDCP entity of this DRB is configured with *integrityProtection*: + - 3> configure the PDCP entity with the integrity protection algorithms according to *securityConfig* and apply the $K_{UPint}$ key associated with the master ( $K_{eNB}/K_{gNB}$ ) or the secondary key ( $S-K_{gNB}$ ) as indicated in *keyToUse*; +- 2> if an *sdap-Config* is included: + - 3> if an SDAP entity with the received *pdu-Session* does not exist: + - 4> establish an SDAP entity as specified in TS 37.324 [24] clause 5.1.1; + - 4> if an SDAP entity with the received *pdu-Session* did not exist prior to receiving this reconfiguration: + - 5> indicate the establishment of the user plane resources for the *pdu-Session* to upper layers; + - 3> configure the SDAP entity in accordance with the received *sdap-Config* as specified in TS 37.324 [24] and associate the DRB with the SDAP entity; + - 3> for each QFI value added in *mappedQoS-FlowsToAdd*, if the QFI value is previously configured, the QFI value is released from the old DRB; +- 2> if the DRB is associated with an *eps-BearerIdentity*: + - 3> if the DRB was configured with the same *eps-BearerIdentity* either by NR or E-UTRA prior to receiving this reconfiguration: + - 4> associate the established DRB with the corresponding *eps-BearerIdentity*; + - 3> else: + - 4> indicate the establishment of the DRB(s) and the *eps-BearerIdentity* of the established DRB(s) to upper layers; +- 1> for each *drb-Identity* value included in the *drb-ToAddModList* that is part of the current UE configuration and configured as DAPS bearer: + - 2> reconfigure the PDCP entity to configure DAPS with the ciphering function, integrity protection function and ROHC function of the target cell group as specified in TS 38.323 [5] and configure it in accordance with the received *pdcp-Config*; + - 2> if the *masterKeyUpdate* is received: + - 3> if the ciphering function of the target cell group PDCP entity is not configured with *cipheringDisabled*: + +- 4> configure the ciphering function of the target cell group PDCP entity with the ciphering algorithm according to *securityConfig* and apply the KUPenc key associated with the master key (KgNB), as indicated in *keyToUse*, i.e. the ciphering configuration shall be applied to all subsequent PDCP PDUs received from the target cell group and sent to the target cell group by the UE; + - 3> if the integrity protection function of the target cell group PDCP entity is configured with *integrityProtection*: + - 4> configure the integrity protection function of the target cell group PDCP entity with the integrity protection algorithms according to *securityConfig* and apply the KUPint key associated with the master key (KgNB) as indicated in *keyToUse*; + - 2> else: + - 3> configure the ciphering function and the integrity protection function of the target cell group PDCP entity with the same security configuration as the PDCP entity for the source cell group; + - 2> if the *sdap-Config* is included and when indication of successful completion of random access towards target cell is received from lower layers as specified in [3]: + - 3> reconfigure the SDAP entity in accordance with the received *sdap-Config* as specified in TS 37.324 [24]; + - 3> for each QFI value added in *mappedQoS-FlowsToAdd*, if the QFI value is previously configured, the QFI value is released from the old DRB; +- 1> for each *drb-Identity* value included in the *drb-ToAddModList* that is part of the current UE configuration and not configured as DAPS bearer: +- 2> if the *reestablishPDCP* is set: + - 3> if target RAT of handover is E-UTRA/5GC; or + - 3> if the UE is connected to E-UTRA/5GC: + - 4> if the UE is capable of E-UTRA/5GC but not capable of NGEN-DC: + - 5> if the PDCP entity of this DRB is not configured with *cipheringDisabled*: + - 6> configure the PDCP entity with the ciphering algorithm and KUPenc key configured/derived as specified in TS 36.331 [10], clause 5.4.2.3, i.e. the ciphering configuration shall be applied to all subsequent PDCP PDUs received and sent by the UE; + - 4> else (i.e., a UE capable of NGEN-DC): + - 5> if the PDCP entity of this DRB is not configured with *cipheringDisabled*: + - 6> configure the PDCP entity with the ciphering algorithm and KUPenc key associated with the master key (KeNB) or the secondary key (S-KgNB), as indicated in *keyToUse*, i.e. the ciphering configuration shall be applied to all subsequent PDCP PDUs received and sent by the UE; + - 3> else (i.e., UE connected to NR or UE connected to E-UTRA/EPC (in EN-DC or capable of EN-DC)): + +- 4> if the PDCP entity of this DRB is not configured with *cipheringDisabled*: + - 5> configure the PDCP entity with the ciphering algorithm and $K_{UPenc}$ key associated with the master key ( $K_{eNB}/K_{gNB}$ ) or the secondary key ( $S-K_{gNB}/S-K_{eNB}$ ), as indicated in *keyToUse*, i.e. the ciphering configuration shall be applied to all subsequent PDCP PDUs received and sent by the UE; +- 4> if the PDCP entity of this DRB is configured with *integrityProtection*: + - 5> configure the PDCP entity with the integrity protection algorithms according to *securityConfig* and apply the $K_{UPint}$ key associated with the master key ( $K_{eNB}/K_{gNB}$ ) or the secondary key ( $S-K_{gNB}$ ) as indicated in *keyToUse*; +- 3> if *drb-ContinueROHC* is included in *pdcp-Config*: + - 4> indicate to lower layer that *drb-ContinueROHC* is configured; +- 3> if *drb-ContinueEHC-DL* is included in *pdcp-Config*: + - 4> indicate to lower layer that *drb-ContinueEHC-DL* is configured; +- 3> if *drb-ContinueEHC-UL* is included in *pdcp-Config*: + - 4> indicate to lower layer that *drb-ContinueEHC-UL* is configured; +- 3> if *drb-ContinueUDC* is included in *pdcp-Config*: + - 4> indicate to lower layer that *drb-ContinueUDC* is configured; +- 3> re-establish the PDCP entity of this DRB as specified in TS 38.323 [5], clause 5.1.2; +- 2> else, if the *recoverPDCP* is set: + - 3> trigger the PDCP entity of this DRB to perform data recovery as specified in TS 38.323 [5]; +- 2> if the *pdcp-Config* is included: + - 3> reconfigure the PDCP entity in accordance with the received *pdcp-Config*. +- 2> if the *sdap-Config* is included: + - 3> reconfigure the SDAP entity in accordance with the received *sdap-Config* as specified in TS37.324 [24]; + - 3> for each QFI value added in *mappedQoS-FlowsToAdd*, if the QFI value is previously configured, the QFI value is released from the old DRB; + +NOTE 1: Void. + +- NOTE 2: When determining whether a *drb-Identity* value is part of the current UE configuration, the UE does not distinguish which *RadioBearerConfig* and *DRB-ToAddModList* that DRB was originally configured in. To re-associate a DRB with a different key ( $K_{eNB}$ to $S-K_{gNB}$ , $K_{gNB}$ to $S-K_{eNB}$ , $K_{gNB}$ to $S-K_{gNB}$ , or vice versa), the network provides the *drb-Identity* value in the (target) *drb-ToAddModList* and sets the *reestablishPDCP* flag. The network does not list the *drb-Identity* in the (source) *drb-ToReleaseList*. +- NOTE 3: When setting the *reestablishPDCP* flag for a radio bearer, the network ensures that the RLC receiver entities do not deliver old PDCP PDUs to the re-established PDCP entity. It does that e.g. by triggering a reconfiguration with sync of the cell group hosting the old RLC entity or by releasing the old RLC entity. +- NOTE 4: In this specification, UE configuration refers to the parameters configured by NR RRC unless otherwise stated. +- NOTE 5: Ciphering and integrity protection can be enabled or disabled for a DRB. The enabling/disabling of ciphering or integrity protection can be changed only by releasing and adding the DRB. +- NOTE 6: In DAPS handover, the UE may perform PDCP entity re-establishment (if *reestablishPDCP* is set) or the PDCP data recovery (if *recoverPDCP* is set) for a non-DAPS bearer when indication of successful completion of random access towards target cell is received from lower layers as specified in TS 38.321 [3]. In this case, the UE suspends data transmission and reception for all non-DAPS bearers in the source MCG for duration of the DAPS handover. + +#### 5.3.5.6.6 Multicast MRB release + +The UE shall: + +- 1> for each *mrp-Identity* value included in the *mrp-ToReleaseList* that is part of the current UE configuration; or +- 1> for each *mrp-Identity* value that is to be released as the result of full configuration according to 5.3.5.11: + - 2> release the PDCP entity and the *mrp-Identity*; + +NOTE 1: The UE does not consider the message as erroneous if the *mrp-ToReleaseList* includes any *mrp-Identity* value that is not part of the current UE configuration. + +NOTE 2: Whether or not the RLC and MAC entities associated with this PDCP entity are reset or released is determined by the *CellGroupConfig*. + +#### 5.3.5.6.7 Multicast MRB addition/modification + +The UE shall for each element in the order of entry in the list *mrp-ToAddModList*: + +- 1> if *mrp-Identity* value included in the *mrp-ToAddModList* is part of the UE configuration: + - 2> if *mrp-Identity* value included in the *mrp-ToAddModList* for which *mrp-IdentityNew* is included (i.e., multicast MRB ID change): + - 3> update the *mrp-Identity* to the value *mrp-IdentityNew*; + - 2> if the *reestablishPDCP* is set: + - 3> if *drb-ContinueROHC* is included in *pdcp-Config*: + +- 4> indicate to lower layer that *drb-ContinueROHC* is configured; +- 3> if *drb-ContinueEHC-DL* is included in *pdcp-Config*: + - 4> indicate to lower layer that *drb-ContinueEHC-DL* is configured; +- 3> re-establish the PDCP entity of this multicast MRB as specified in TS 38.323 [5], clause 5.1.2; +- 2> else, if the *recoverPDCP* is set: + - 3> trigger the PDCP entity of this MRB to perform data recovery as specified in TS 38.323 [5]; +- 2> if the *pdcp-Config* is included: + - 3> reconfigure the PDCP entity in accordance with the received *pdcp-Config*; +- 1> else if *mrb-Identity* value included in the *mrb-ToAddModList* is not part of the UE configuration (i.e., multicast MRB establishment including the case when full configuration option is used): + - 2> establish a PDCP entity and configure it in accordance with the received *pdcp-Config*; + - 2> associate the established multicast MRB with the corresponding *mbs-SessionId*; + - 2> if an SDAP entity with the received *mbs-SessionId* does not exist: + - 3> establish an SDAP entity as specified in TS 37.324 [24] clause 5.1.1; + - 3> if an SDAP entity with the received *mbs-SessionId* did not exist prior to receiving this reconfiguration: + - 4> indicate the establishment of the user plane resources for the *mbs-SessionId* to upper layers. + +NOTE 1: When setting the *reestablishPDCP* flag for a radio bearer, the network ensures that the RLC receiver entities do not deliver old PDCP PDUs to the re-established PDCP entity. The network does that e.g. by triggering a reconfiguration with sync of the cell group hosting the old RLC entity or by releasing the old RLC entity. + +NOTE 2: In this specification, UE configuration refers to the parameters configured by NR RRC unless otherwise stated. + +NOTE 3: When updating the *mrb-Identity*, the network ensures new MRBs are listed at the end of the *mrb-ToAddModList* if they have the same MRB ID as in the existing UE configuration. + +### 5.3.5.7 AS Security key update + +The UE shall: + +- 1> if UE is connected to E-UTRA/EPC or E-UTRA/5GC: + +2> upon reception of *sk-Counter* as specified in TS 36.331 [10]: + +3> update the S- $K_{gNB}$ key based on the $K_{eNB}$ key and using the received *sk-Counter* value, as specified in TS 33.401 [30] for EN-DC, or TS 33.501 [11] for NGEN-DC; + +3> derive the $K_{RRCenc}$ and $K_{UPenc}$ keys as specified in TS 33.401 [30] for EN-DC, or TS 33.501 [11] for NGEN-DC; + +3> derive the $K_{RRCint}$ and $K_{UPint}$ keys as specified in TS 33.401 [30] for EN-DC or TS 33.501 [11] for NGEN-DC. + +1> else if this procedure was initiated due to reception of the *masterKeyUpdate*: + +2> if the *nas-Container* is included in the received *masterKeyUpdate*: + +3> forward the *nas-Container* to the upper layers; + +2> if the *keySetChangeIndicator* is set to *true*: + +3> derive or update the $K_{gNB}$ key based on the $K_{AMF}$ key, as specified in TS 33.501 [11]; + +2> else: + +3> derive or update the $K_{gNB}$ key based on the current $K_{gNB}$ key or the NH, using the *nextHopChainingCount* value indicated in the received *masterKeyUpdate*, as specified in TS 33.501 [11]; + +2> store the *nextHopChainingCount* value; + +2> derive the keys associated with the $K_{gNB}$ key as follows: + +3> if the *securityAlgorithmConfig* is included in *SecurityConfig*: + +4> derive the $K_{RRCenc}$ and $K_{UPenc}$ keys associated with the *cipheringAlgorithm* indicated in the *securityAlgorithmConfig*, as specified in TS 33.501 [11]; + +4> derive the $K_{RRCint}$ and $K_{UPint}$ keys associated with the *integrityProtAlgorithm* indicated in the *securityAlgorithmConfig*, as specified in TS 33.501 [11]; + +3> else: + +4> derive the $K_{RRCenc}$ and $K_{UPenc}$ keys associated with the current *cipheringAlgorithm*, as specified in TS 33.501 [11]; + +4> derive the $K_{RRCint}$ and $K_{UPint}$ keys associated with the current *integrityProtAlgorithm*, as specified in TS 33.501 [11]. + +NOTE 1: Ciphering and integrity protection are optional to configure for the DRBs. + +1> else if this procedure was initiated due to reception of the *sk-Counter* (UE is in NE-DC, or NR-DC, or is configured with SN terminated bearer(s)) or if the procedure was initiated due to selection of an *sk-Counter* for conditional reconfiguration execution for subsequent CPAC (UE is in NR-DC): + +- 2> derive or update the secondary key (S-KgNB or S-KeNB) based on the KgNB key and using the received or selected *sk-Counter* value, as specified in TS 33.501 [11]; +- 2> derive the KRRCEnc key and the KUPEnc key as specified in TS 33.501 [11] using the ciphering algorithms indicated in the *RadioBearerConfig* associated with the secondary key (S-KgNB or S-KeNB) as indicated by *keyToUse*; +- 2> derive the KRRCInt key and the KUPInt key as specified in TS 33.501 [11] using the integrity protection algorithms indicated in the *RadioBearerConfig* associated with the secondary key (S-KgNB or S-KeNB) as indicated by *keyToUse*; + +NOTE 2: If the UE has no radio bearer configured with *keyToUse* set to *secondary* and receives the *sk-Counter* without any *RadioBearerConfig* with *keyToUse* set to *secondary*, the UE does not consider it as an invalid reconfiguration. + +### 5.3.5.8 Reconfiguration failure + +#### 5.3.5.8.1 Void + +#### 5.3.5.8.2 Inability to comply with *RRCREconfiguration* + +NOTE 00: The UE behaviour specified in this clause does not apply to the following, and the UE ignores, i.e. does not take an action on and does not store, the fields that it does not support or does not comprehend: + +- The fields in *ServingCellConfigCommon* that are defined in Rel-16 and later. +- The fields of *searchSpaceMCCH* and *searchSpaceMTCH* in *PDCCH-ConfigCommon* that are defined in Rel-17 and later. + +The UE shall: + +- 1> if the UE is in (NG)EN-DC: + - 2> if the UE is unable to comply with (part of) the configuration included in the *RRCREconfiguration* message received over SRB3; + - 3> if the *RRCREconfiguration* message was received as part of *ConditionalReconfiguration*: + - 4> continue using the configuration used prior to when the inability to comply with the *RRCREconfiguration* message was detected; + - 3> else: + - 4> continue using the configuration used prior to the reception of *RRCREconfiguration* message; + - 3> if MCG transmission is not suspended: + - 4> initiate the SCG failure information procedure as specified in clause 5.7.3 to report SCG reconfiguration error, upon which the connection reconfiguration procedure ends; + - 3> else: + +- 4> initiate the connection re-establishment procedure as specified in TS 36.331 [10], clause 5.3.7, upon which the connection reconfiguration procedure ends; +- 2> else, if the UE is unable to comply with (part of) the configuration included in the *RRCREconfiguration* message received over SRB1; + - 3> if the *RRCREconfiguration* message was received as part of *ConditionalReconfiguration*: + - 4> continue using the configuration used prior to when the inability to comply with the *RRCREconfiguration* message was detected; + - 3> else: + - 4> continue using the configuration used prior to the reception of *RRCREconfiguration* message; + - 3> initiate the connection re-establishment procedure as specified in TS 36.331 [10], clause 5.3.7, upon which the connection reconfiguration procedure ends. +- 1> else if *RRCREconfiguration* is received via NR (i.e., NR standalone, NE-DC, or NR-DC): + - 2> if the UE is unable to comply with (part of) the configuration included in the *RRCREconfiguration* message received over SRB3; + +NOTE 0: This case does not apply in NE-DC. + +- 3> if the *RRCREconfiguration* message was received as part of *ConditionalReconfiguration*; or, + - 3> if the *RRCREconfiguration* message was received as part of *ltn-Config*: + - 4> continue using the configuration used prior to when the inability to comply with the *RRCREconfiguration* message was detected; + - 3> else: + - 4> continue using the configuration used prior to the reception of *RRCREconfiguration* message; + - 3> if MCG transmission is not suspended: + - 4> initiate the SCG failure information procedure as specified in clause 5.7.3 to report SCG reconfiguration error, upon which the connection reconfiguration procedure ends; + - 3> else: + - 4> initiate the connection re-establishment procedure as specified in clause 5.3.7, upon which the connection reconfiguration procedure ends; +- 2> else if the UE is unable to comply with (part of) the configuration included in the *RRCREconfiguration* message received over the SRB1 or if the upper layers indicate that the *nas-Container* is invalid: + +NOTE 0a: The compliance also covers the SCG configuration carried within octet strings e.g. field *mrdc-SecondaryCellGroupConfig*. I.e. the failure behaviour defined also applies in case the UE cannot comply with the embedded SCG configuration or with the combination of (parts of) the MCG and SCG configurations. + +NOTE 0b: The compliance also covers the V2X sidelink configuration carried within an octet string, e.g. field *sl-ConfigDedicatedEUTRA*. I.e. the failure behaviour defined also applies in case the UE cannot comply with the embedded V2X sidelink configuration. + +3> if the *RRCREconfiguration* message was received as part of *ConditionalReconfiguration*; or, + +3> if the *RRCREconfiguration* message was received as part of *ltm-Config*: + +4> continue using the configuration used prior to when the inability to comply with the *RRCREconfiguration* message was detected; + +3> else: + +4> continue using the configuration used prior to the reception of *RRCREconfiguration* message; + +3> if AS security has not been activated: + +4> perform the actions upon going to RRC\_IDLE as specified in 5.3.11, with release cause 'other' + +3> else if AS security has been activated but SRB2 and at least one DRB or multicast MRB or, for IAB and NCR, SRB2, have not been setup: + +4> perform the actions upon going to RRC\_IDLE as specified in 5.3.11, with release cause 'RRC connection failure'; + +3> else: + +4> initiate the connection re-establishment procedure as specified in 5.3.7, upon which the reconfiguration procedure ends; + +1> else if *RRCREconfiguration* is received via other RAT (Handover to NR failure): + +2> if the UE is unable to comply with any part of the configuration included in the *RRCREconfiguration* message or if the upper layers indicate that the *nas-Container* is invalid: + +3> perform the actions defined for this failure case as defined in the specifications applicable for the other RAT. + +NOTE 1: The UE may apply above failure handling also in case the *RRCREconfiguration* message causes a protocol error for which the generic error handling as defined in clause 10 specifies that the UE shall ignore the message. + +NOTE 2: If the UE is unable to comply with part of the configuration, it does not apply any part of the configuration, i.e. there is no partial success/failure. + +NOTE 3: It is up to UE implementation whether the compliance check for an *RRCREconfiguration* received as part of *ConditionalReconfiguration* is performed upon the reception of the message or upon CHO, CPA, CPC, and subsequent CPAC execution (when the message is required to be applied). + +NOTE 4: It is up to UE implementation whether the compliance check for an *RRCREconfiguration* message received as part of an *LTM-Config* IE is performed upon the reception of the message or during an LTM cell switch procedure (when the message is required to be applied). + +### 5.3.5.8.3 T304 expiry (Reconfiguration with sync Failure) or T420 expiry (Path switch failure) + +The UE shall: + +- 1> if T304 of the MCG expires; or +- 1> if T420 expires; or, +- 1> if the target L2 U2N Relay UE (i.e., the UE indicated by *targetRelayUE-Identity* in the received *RRCReconfiguration* message containing *reconfigurationWithSync* indicating path switch as specified in 5.3.5.5.2) changes its serving PCell before path switch: + - 2> release dedicated preambles provided in *rach-ConfigDedicated* if configured; + - 2> release dedicated msgA PUSCH resources provided in *rach-ConfigDedicated* if configured; + - 2> if any DAPS bearer is configured, and radio link failure is not detected in the source PCell, according to clause 5.3.10.3: + - 3> reset MAC for the target PCell and release the MAC configuration for the target PCell; + - 3> for each DAPS bearer: + - 4> release the RLC entity or entities as specified in TS 38.322 [4], clause 5.1.3, and the associated logical channel for the target PCell; + - 4> reconfigure the PDCP entity to release DAPS as specified in TS 38.323 [5]; + - 3> for each SRB: + - 4> if the *masterKeyUpdate* was not received: + - 5> configure the PDCP entity for the source PCell with state variables continuation as specified in TS 38.323 [5]; + - 4> release the PDCP entity for the target PCell; + - 4> release the RLC entity as specified in TS 38.322 [4], clause 5.1.3, and the associated logical channel for the target PCell; + - 4> trigger the PDCP entity for the source PCell to perform SDU discard as specified in TS 38.323 [5]; + - 4> re-establish the RLC entity for the source PCell; + - 3> release the physical channel configuration for the target PCell; + - 3> discard the keys used in target PCell (the $K_{\text{gNB}}$ key, the $K_{\text{RRCenc}}$ key, the $K_{\text{RRCint}}$ key, the $K_{\text{UPint}}$ key and the $K_{\text{UPenc}}$ key), if any; + - 3> resume suspended SRBs in the source PCell; + +3> for each non-DAPS bearer: + +4> revert back to the UE configuration used for the DRB or multicast MRB in the source PCell, includes PDCP, RLC states variables, the security configuration and the data stored in transmission and reception buffers in PDCP and RLC entities ; + +3> revert back to the UE measurement configuration used in the source PCell; + +3> store the handover failure information in *VarRLF-Report* as described in the clause 5.3.10.5; + +3> initiate the failure information procedure as specified in clause 5.7.5 to report DAPS handover failure. + +2> else: + +3> revert back to the UE configuration used in the source PCell; + +3> if the associated T304 was not initiated upon cell selection performed while timer T311 was running, as defined in clause 5.3.7.3: + +4> store the handover failure information in *VarRLF-Report* as described in the clause 5.3.10.5; + +3> initiate the connection re-establishment procedure as specified in clause 5.3.7. + +NOTE 1: In the context above, "the UE configuration" includes state variables and parameters of each radio bearer. + +1> else if T304 of a secondary cell group expires: + +2> if MCG transmission is not suspended: + +3> release dedicated preambles provided in *rach-ConfigDedicated*, if configured; + +3> release dedicated msgA PUSCH resources provided in *rach-ConfigDedicated*, if configured; + +3> initiate the SCG failure information procedure as specified in clause 5.7.3 to report SCG reconfiguration with sync failure, upon which the RRC reconfiguration procedure ends; + +2> else: + +3> if the UE is in NR-DC: + +4> initiate the connection re-establishment procedure as specified in clause 5.3.7; + +3> else (the UE is in (NG) EN-DC): + +4> initiate the connection re-establishment procedure as specified in TS 36.331 [10], clause 5.3.7; + +- 1> else if T304 expires when *RRCREconfiguration* is received via other RAT (HO to NR failure): + - 2> reset MAC; + - 2> perform the actions defined for this failure case as defined in the specifications applicable for the other RAT. + +NOTE 2: In this clause, the term 'handover failure' has been used to refer to 'reconfiguration with sync failure'. + +### 5.3.5.9 Other configuration + +The UE shall: + +- 1> if the received *otherConfig* includes the *delayBudgetReportingConfig*: + - 2> if *delayBudgetReportingConfig* is set to *setup*: + - 3> consider itself to be configured to send delay budget reports in accordance with 5.7.4; + - 2> else: + - 3> consider itself not to be configured to send delay budget reports and stop timer T342, if running. +- 1> if the received *otherConfig* includes the *overheatingAssistanceConfig*: + - 2> if *overheatingAssistanceConfig* is set to *setup*: + - 3> consider itself to be configured to provide overheating assistance information in accordance with 5.7.4; + - 2> else: + - 3> consider itself not to be configured to provide overheating assistance information and stop timer T345, if running; +- 1> if the received *otherConfig* includes the *idc-AssistanceConfig*: + - 2> if *idc-AssistanceConfig* is set to *setup*: + - 3> consider itself to be configured to provide IDC assistance information in accordance with 5.7.4; + - 2> else: + - 3> consider itself not to be configured to provide IDC assistance information; +- 1> if the received *otherConfig* includes the *drx-PreferenceConfig*: + +- 2> if *drx-PreferenceConfig* is set to *setup*: + - 3> consider itself to be configured to provide its preference on DRX parameters for power saving for the cell group in accordance with 5.7.4; +- 2> else: + - 3> consider itself not to be configured to provide its preference on DRX parameters for power saving for the cell group and stop timer T346a associated with the cell group, if running; +- 1> if the received *otherConfig* includes the *maxBW-PreferenceConfig*: + - 2> if *maxBW-PreferenceConfig* is set to *setup*: + - 3> consider itself to be configured to provide its preference on the maximum aggregated bandwidth for power saving for the cell group in accordance with 5.7.4; + - 3> if *otherConfig* includes *maxBW-PreferenceConfigFR2-2*: + - 4> consider itself to be configured to provide its preference on the maximum aggregated bandwidth for FR2-2 for power saving for the cell group in accordance with 5.7.4; + - 2> else: + - 3> consider itself not to be configured to provide its preference on the maximum aggregated bandwidth for power saving for the cell group and stop timer T346b associated with the cell group, if running; +- 1> if the received *otherConfig* includes the *maxCC-PreferenceConfig*: + - 2> if *maxCC-PreferenceConfig* is set to *setup*: + - 3> consider itself to be configured to provide its preference on the maximum number of secondary component carriers for power saving for the cell group in accordance with 5.7.4; + - 2> else: + - 3> consider itself not to be configured to provide its preference on the maximum number of secondary component carriers for power saving for the cell group and stop timer T346c associated with the cell group, if running; +- 1> if the received *otherConfig* includes the *maxMIMO-LayerPreferenceConfig*: + - 2> if *maxMIMO-LayerPreferenceConfig* is set to *setup*: + - 3> consider itself to be configured to provide its preference on the maximum number of MIMO layers for power saving for the cell group in accordance with 5.7.4; + - 3> if *otherConfig* includes *maxMIMO-LayerPreferenceConfigFR2-2*: + - 4> consider itself to be configured to provide its preference on the maximum number of MIMO layers for FR2-2 for power saving for the cell group in accordance with 5.7.4; + - 2> else: + - 3> consider itself not to be configured to provide its preference on the maximum number of MIMO layers for power saving for the cell group and stop timer T346d associated with the cell group, if running; + +4> consider itself to be configured to provide its preference on the maximum number of MIMO layers for FR2-2 for power saving for the cell group in accordance with 5.7.4; + +2> else: + +3> consider itself not to be configured to provide its preference on the maximum number of MIMO layers for power saving for the cell group and stop timer T346d associated with the cell group, if running; + +1> if the received *otherConfig* includes the *minSchedulingOffsetPreferenceConfig*: + +2> if *minSchedulingOffsetPreferenceConfig* is set to *setup*: + +3> consider itself to be configured to provide its preference on the minimum scheduling offset for cross-slot scheduling for power saving for the cell group in accordance with 5.7.4; + +3> if *otherConfig* includes *minSchedulingOffsetPreferenceConfigExt*: + +4> consider itself to be configured to provide its preference on the minimum scheduling offset for 480 kHz SCS and/or 960 kHz SCS for cross-slot scheduling for power saving for the cell group in accordance with 5.7.4; + +2> else: + +3> consider itself not to be configured to provide its preference on the minimum scheduling offset for cross-slot scheduling for power saving for the cell group and stop timer T346e associated with the cell group, if running; + +1> if the received *otherConfig* includes the *releasePreferenceConfig*: + +2> if *releasePreferenceConfig* is set to *setup*: + +3> consider itself to be configured to provide assistance information to transition out of RRC\_CONNECTED in accordance with 5.7.4; + +2> else: + +3> consider itself not to be configured to provide assistance information to transition out of RRC\_CONNECTED and stop timer T346f, if running. + +1> if the received *otherConfig* includes the *obtainCommonLocation*: + +2> include available detailed location information for any subsequent measurement report or any subsequent RLF report, *SCGFailureInformation* and successful handover report; + +NOTE 1: The UE is requested to attempt to have valid detailed location information available whenever sending a measurement report for which it is configured to include available detailed location information. The UE may not succeed e.g. because the user manually disabled the GPS hardware, due to no/poor satellite coverage. Further details, e.g. regarding when to activate GNSS, are up to UE implementation. + +- 1> if the received *otherConfig* includes the *btNameList*: + - 2> if *btNameList* is set to *setup*, include available Bluetooth measurement results for any subsequent measurement report or any subsequent RLF report and SCGFailureInformation; +- 1> if the received *otherConfig* includes the *wlanNameList*: + - 2> if *wlanNameList* is set to *setup*, include available WLAN measurement results for any subsequent measurement report or any subsequent RLF report and SCGFailureInformation; +- 1> if the received *otherConfig* includes the *sensorNameList*: + - 2> if *sensorNameList* is set to *setup*, include available Sensor measurement results for any subsequent measurement report or any subsequent RLF report and SCGFailureInformation; + +NOTE 2: The UE is requested to attempt to have valid Bluetooth measurements, WLAN measurements and Sensor measurements whenever sending a measurement report for which it is configured to include these measurements. The UE may not succeed e.g. because the user manually disabled the WLAN or Bluetooth or Sensor hardware. Further details, e.g. regarding when to activate WLAN or Bluetooth or Sensor, are up to UE implementation. + +- 1> if the received *otherConfig* includes the *sl-AssistanceConfigNR*: + - 2> consider itself to be configured to provide configured grant assistance information for NR sidelink communication in accordance with 5.7.4; +- 1> if the received *otherConfig* includes the *referenceTimePreferenceReporting*: + - 2> consider itself to be configured to provide UE reference time assistance information in accordance with 5.7.4; +- 1> else: + - 2> consider itself not to be configured to provide UE reference time assistance information; +- 1> if the received *otherConfig* includes the *successHO-Config*: + - 2> consider itself to be configured to provide the successful handover information in accordance with 5.7.10.6; +- 1> else: + - 2> consider itself not to be configured to provide the successful handover information. +- 1> if the received *otherConfig* includes the *successPSCell-Config*: + - 2> if *thresholdPercentageT304-SCG* is included: + - 3> consider itself to be configured by the target PSCell to provide the successful PSCell change or addition information in accordance with 5.7.10.7; + +2> else if *sn-InitiatedPSCellChange* is included: + +3> consider itself to be configured by the source PSCell to provide the successful PSCell change or addition information in accordance with 5.7.10.7; + +2> else: + +3> consider itself to be configured by the PCell to provide the successful PSCell change or addition information in accordance with 5.7.10.7; + +1> else: + +2> consider itself not to be configured to provide the successful PSCell change or addition information. + +1> if the received *otherConfig* includes the *ul-GapFR2-PreferenceConfig*: + +2> consider itself to be configured to provide its preference on FR2 UL gap in accordance with 5.7.4; + +1> else: + +2> consider itself not to be configured to provide its preference on FR2 UL gap; + +1> if the received *otherConfig* includes the *musim-GapAssistanceConfig*: + +2> if *musim-GapAssistanceConfig* is set to *setup*: + +3> consider itself to be configured to provide MUSIM assistance information for gap preference in accordance with 5.7.4; + +2> else: + +3> consider itself not to be configured to provide MUSIM assistance information for gap preference and stop timer T346h, if running; + +1> if the received *otherConfig* includes the *musim-LeaveAssistanceConfig*: + +2> if *musim-LeaveAssistanceConfig* is set to *setup*: + +3> consider itself to be configured to provide MUSIM assistance information for leaving RRC\_CONNECTED in accordance with 5.7.4; + +2> else: + +3> consider itself not to be configured to provide MUSIM assistance information for leaving RRC\_CONNECTED and stop timer T346g, if running. + +1> if the received *otherConfig* includes the *musim-GapPriorityAssistanceConfig*: + +2> consider itself to be configured to provide MUSIM assistance information for gap(s) priority in accordance with 5.7.4; + +1> else: + +- 2> consider itself not to be configured to provide MUSIM assistance information for gap(s) priority; +- 1> if the received *otherConfig* includes the *musim-CapabilityRestrictionConfig*: + - 2> if *musim-CapabilityRestrictionConfig* is set to *setup*: + - 3> consider itself to be configured to provide MUSIM assistance information for capability restriction in accordance with 5.7.4; + - 2> else: + - 3> consider itself not to be configured to provide MUSIM assistance information for capability restriction and stop timer T348 and T346n, if running; +- 1> if the received *otherConfig* includes the *rlm-RelaxationReportingConfig*: + - 2> if *rlm-RelaxationReportingConfig* is set to *setup*: + - 3> consider itself to be configured to report the relaxation state of RLM measurements in accordance with 5.7.4; + - 2> else: + - 3> consider itself not to be configured to report the relaxation state of RLM measurements and stop timer T346j associated with the cell group, if running; +- 1> if the received *otherConfig* includes the *bfd-RelaxationReportingConfig*: + - 2> if *bfd-RelaxationReportingConfig* is set to *setup*: + - 3> consider itself to be configured to report the relaxation state of BFD measurements in accordance with 5.7.4; + - 2> else: + - 3> consider itself not to be configured to report the relaxation state of BFD measurements and stop timer T346k associated with the cell group, if running; +- 1> if the received *otherConfig* includes the *scg-DeactivationPreferenceConfig*: + - 2> if the *scg-DeactivationPreferenceConfig* is set to *setup*: + - 3> consider itself to be configured to provide its SCG deactivation preference in accordance with 5.7.4; + - 2> else: + - 3> consider itself not to be configured to provide its SCG deactivation preference and stop timer T346i, if running. +- 1> if the received *otherConfig* includes the *propDelayDiffReportConfig*: + - 2> if the *propDelayDiffReportConfig* is set to *setup*: + +3> consider itself to be configured to provide service link propagation delay difference between serving cell and neighbour cell(s) in accordance with 5.7.4; + +2> else: + +3> consider itself not to be configured to provide service link propagation delay difference between serving cell and neighbour cell(s). + +1> if the received *otherConfig* includes the *rrm-MeasRelaxationReportingConfig*: + +2> if the *rrm-MeasRelaxationReportingConfig* is set to *setup*: + +3> consider itself to be configured to report the fulfilment of the criterion for relaxing RRM measurements in accordance with 5.7.4; + +2> else: + +3> consider itself not to be configured to report the fulfilment of the criterion for relaxing RRM measurements. + +1> if the received *otherConfig* includes the *multiRx-PreferenceReportingConfigFR2*: + +2> if the *multiRx-PreferenceReportingConfigFR2* is set to *setup*: + +3> consider itself to be configured to provide its preference on multi-Rx operation for FR2 in accordance with 5.7.4; + +2> else: + +3> consider itself not to be configured to provide its preference on multi-Rx operation for FR2 and stop timer T346m, if running. + +1> if the received *otherConfig* includes the *uav-FlightPathAvailabilityConfig*: + +2> consider itself to be configured to indicate the availability of flight path information in accordance with 5.7.4; + +1> if the received *otherConfig* includes the *ul-TrafficInfoReportingConfig*: + +2> if *ul-TrafficInfoReportingConfig* is set to *setup*: + +3> consider itself to be configured to provide UL traffic information in accordance with 5.7.4; + +2> else: + +3> consider itself not to be configured to provide UL traffic information and stop all instances of timer T346x, if running. + +### 5.3.5.9a MUSIM gap configuration + +The UE shall: + +1> if *musim-GapConfig* is set to *setup*: + +2> for each *musim-GapId* included in the received *musim-GapToReleaseList*: + +3> release the periodic MUSIM gap configuration associated with the *musim-GapId*, + +2> for each *MUSIM-Gap* included in the received *musim-GapToAddModList*: + +3> setup periodic MUSIM gap configuration indicated by the *MUSIM-Gap* in accordance with the received *musim-GapRepetitionAndOffset* (providing *musim-GapRepetition* and *Offset* value for the following condition) i.e. the first subframe of each periodic MUSIM gap occurs at an SFN and subframe of the NR PCell meeting the following condition: + +SFN mod $T = \text{FLOOR}(\text{Offset}/10)$ ; + +subframe = *Offset* mod 10; + +with $T = \text{musim-GapRepetition}/10$ ; + +3> set the MUSIM gap priority configuration indicated by *musim-GapPriorityToAddModList*, if configured, for each periodic MUSIM gap; + +3> set the *musim-GapKeep*, if all collided MUSIM gaps are configured to be kept; + +NOTE: If network does not retain the relative priorities among MUSIM gaps, UE behaviour is not specified. + +2> if *musim-AperiodicGap* is included: + +3> setup aperiodic MUSIM gap configuration indicated by the *musim-AperiodicGap* in accordance with the received *musim-Starting-SFN-AndSubframe*, i.e. the first subframe of aperiodic MUSIM gap occurs at an SFN and subframe of the NR PCell meeting the following condition: + +SFN = *starting-SFN*; + +subframe = *startingSubframe*; + +1> else if *musim-GapConfig* is set to *release*: + +2> release the MUSIM gap configuration. + +### 5.3.5.10 MR-DC release + +The UE shall: + +1> as a result of MR-DC release triggered by E-UTRA or NR: + +2> release SRB3, if established, as specified in 5.3.5.6.2; + +- 2> release SRB5, if established, as specified in 5.3.5.6.2; +- 2> release *measConfig* associated with SCG; +- 2> if the UE is configured with NR SCG: + - 3> release the SCG configuration as specified in clause 5.3.5.4; + - 3> release *otherConfig* associated with the SCG, if configured; + - 3> release *successPSCell-Config* configured by the PCell in the *otherConfig*, if configured; + - 3> stop timers T346a, T346b, T346c, T346d, T346e, T346j and T346k associated with the SCG, if running; + - 3> release *bap-Config* associated with the SCG, if configured; + - 3> release the BAP entity as specified in TS 38.340 [47], if there is no configured *bap-Config*; + - 3> release *iab-IP-AddressConfigurationList* associated with the SCG, if configured; +- 2> else if the UE is configured with E-UTRA SCG: + - 3> release the SCG configuration as specified in TS 36.331 [10], clause 5.3.10.19 to release the E-UTRA SCG; + +### 5.3.5.11 Full configuration + +The UE shall: + +- 1> release/ clear all current dedicated radio configurations except for the following: + - the MCG C-RNTI; + - the AS security configurations associated with the master key; + - the SRB1/SRB2 configurations and DRB/multicast MRB configurations as configured by *radioBearerConfig* or *radioBearerConfig2*. + +NOTE 1: Radio configuration is not just the resource configuration but includes other configurations like *MeasConfig*. Radio configuration also includes the RLC bearer configurations as configured by *RLC-BearerConfig*, PC5 Relay RLC channel as configured by *SL-RLC-ChannelConfig*, and Uu Relay RLC channel as configured by *Uu-RelayRLC-ChannelConfig*. In case NR-DC or NE-DC is configured, this also includes the entire NR or E-UTRA SCG configuration which are released according to the MR-DC release procedure as specified in 5.3.5.10. + +NOTE 1a: For NR sidelink communication/discovery, the radio configuration includes the sidelink RRC configuration received from the network, but does not include the sidelink RRC reconfiguration and sidelink UE capability received from other UEs via PC5-RRC. In addition, the UE considers the new NR sidelink configurations as full configuration, in case of state transition and change of system information used for NR sidelink communication/discovery. + +NOTE 1b: To establish the RLC bearer of SRB(s) after release due to *fullConfig*, the network can include the *srb-Identity* within *srb-ToAddModList* (i.e. the UE applies RLC default configuration) and/or provide *rlc-BearerToAddModList* of concerned SRB(s) explicitly. + +- the logged measurement configuration; +- 1> if the *spCellConfig* in the *masterCellGroup* includes the *reconfigurationWithSync*: +- 2> release/ clear all current common radio configurations; + - 2> if *sl-PathSwitchConfig* was included in *reconfigurationWithSync*: + - 3> use the default values specified in 9.2.3 for timer T311; + - 2> else: + - 3> use the default values specified in 9.2.3 for timers T310, T311 and constants N310, N311; +- 1> else (full configuration after re-establishment or during RRC resume): +- 2> if the UE is acting as L2 U2N Remote UE: + - 3> use value for timer T311, as included in *ue-TimersAndConstants* received in *SIB1* + - 2> else: + - 3> use values for timers T301, T310, T311 and constants N310, N311, as included in *ue-TimersAndConstants* received in *SIB1*; +- 1> if no *measConfigAppLayerId* is included: +- 2> inform upper layers about the release of all application layer measurement configurations; + - 2> discard any received application layer measurement report from upper layers; + - 2> consider itself not to be configured to send application layer measurement report. +- 1> if the UE is acting as L2 U2N Remote UE at the target side during reconfiguration with sync, or after re-establishment, or during RRC resume: +- 2> apply the default configuration of SL-RLC1 as specified in clause 9.2.4 and associate it with the SRB1; +- 1> else: +- 2> apply the default L1 parameter values as specified in corresponding physical layer specifications except for the following: + - parameters for which values are provided in *SIB1*; + +- 2> apply the default MAC Cell Group configuration as specified in 9.2.2; +- 2> for each *srb-Identity* value included in the *srb-ToAddModList* (SRB reconfiguration): + - 3> establish an RLC entity for the corresponding SRB; + - 3> apply the default SRB configuration defined in 9.2.1 for the corresponding SRB; + +NOTE 2: This is to get the SRBs (SRB1 and SRB2 for reconfiguration with sync and SRB2 for resume and reconfiguration after re-establishment) to a known state from which the reconfiguration message can do further configuration. + +- 1> for each *pdu-Session* that is part of the current UE configuration: + - 2> release the SDAP entity (clause 5.1.2 in TS 37.324 [24]); + - 2> release each DRB associated to the *pdu-Session* as specified in 5.3.5.6.4; + +NOTE 3: This will retain the *pdu-Session* but remove the DRBs including *drb-identity* of these bearers from the current UE configuration. Setup of the DRBs within the AS is described in clause 5.3.5.6.5 using the new configuration. The *pdu-Session* acts as the anchor for associating the released and re-setup DRB. In the AS the DRB re-setup is equivalent with a new DRB setup (including new PDCP and logical channel configurations). + +- 1> for each *mbs-SessionId* that is part of the current UE configuration and associated to a multicast MRB: + - 2> release the SDAP entity (clause 5.1.2 in TS 37.324 [24]); + - 2> release each multicast MRB associated to the *mbs-SessionId* as specified in 5.3.5.6.6; + +NOTE 4: This will retain the *mbs-SessionId* but remove the multicast MRBs including *mrb-identity* of these bearers from the current UE configuration. Setup of the multicast MRBs within the AS is described in clause 5.3.5.6.7 using the new configuration. The *mbs-SessionId* acts as the anchor for associating the released and re-setup multicast MRB. In the AS the multicast MRB re-setup is equivalent with a new multicast MRB setup (including new PDCP and logical channel configurations). + +- 1> for each *pdu-Session* that is part of the current UE configuration but not added with same *pdu-Session* in the *drb-ToAddModList*: + - 2> if the procedure was triggered due to reconfiguration with sync: + - 3> indicate the release of the user plane resources for the *pdu-Session* to upper layers after successful reconfiguration with sync; + - 2> else: + - 3> indicate the release of the user plane resources for the *pdu-Session* to upper layers immediately; +- 1> for each *mbs-SessionId* that is part of the current UE configuration but not added with the same *mbs-SessionId* in the *mrb-ToAddModList*: + - 2> if the procedure was triggered due to reconfiguration with sync: + +3> indicate the release of the user plane resources for the *mbs-SessionId* to upper layers after successful reconfiguration with sync; + +2> else: + +3> indicate the release of the user plane resources for the *mbs-SessionId* to upper layers immediately. + +### 5.3.5.12 BAP configuration + +The IAB-MT shall: + +1> if the *bap-Config* is set to *setup*: + +2> if no BAP entity is established: + +3> establish a BAP entity as specified in TS 38.340 [47]; + +2> if *bap-Address* is included: + +3> configure the BAP entity to use the *bap-Address* as this node's BAP address; + +2> if *defaultUL-BAP-RoutingID* is included: + +3> configure the BAP entity to apply the default UL BAP routing ID according to the configuration; + +2> if *defaultUL-BH-RLC-Channel* is included + +3> configure the BAP entity to apply the default UL BH RLC channel according to the configuration; + +2> if *flowControlFeedbackType* is included: + +3> configure the BAP entity to apply the flow control feedback according to the configuration; + +1> if the *bap-Config* is set to *release*: + +2> release the concerned *bap-Config*; + +2> if there is no other configured *bap-Config* for the MCG or for the SCG + +3> release the BAP entity as specified in TS 38.340 [47]. + +### 5.3.5.12a IAB Other Configuration + +#### 5.3.5.12a.1 IP address management + +##### 5.3.5.12a.1.1 IP Address Release + +The IAB-MT shall: + +- 1> if the release is triggered by reception of the *iab-IP-AddressToReleaseList*: + - 2> for each *iab-IP-AddressIndex* value included in *iab-IP-AddressToReleaseList*: + - 3> release the corresponding *IAB-IP-AddressConfiguration*. + +##### 5.3.5.12a.1.2 IP Address Addition/Modification + +The IAB-MT shall: + +- 1> for each *iab-IP-AddressIndex* value included in the *iab-IP-AddressToAddModList* that is not part of the current IAB-MT configuration: + - 2> add the IP address indicated in *iab-IP-Address*, corresponding to the *iab-IP-AddressIndex*. + - 2> if added IP address is *iPv4-Address*: + - 3> if *iab-IP-Usage* is set to *f1-C*: + - 4> store the received IPv4 address for F1-C traffic together with the IAB-donor-DU BAP address corresponding to the *iab-IP-AddressIndex*. + - 3> else if *iab-IP-Usage* is set to *f1-U*: + - 4> store the received IPv4 address for F1-U traffic together with the IAB-donor-DU BAP address corresponding to the *iab-IP-AddressIndex*. + - 3> else if *iab-IP-Usage* is set to *non-F1*: + - 4> store the received IPv4 address for non-F1 traffic together with the IAB-donor-DU BAP address corresponding to the *iab-IP-AddressIndex*. + - 3> else: + - 4> store the received IPv4 address for all traffic together with the IAB-donor-DU BAP address corresponding to the *iab-IP-AddressIndex*. + - 2> else if *iPv6-Address* is included: + - 3> if *iab-IP-Usage* is set to *f1-C*: + +- 4> store the received IPv6 address for F1-C traffic together with the IAB-donor-DU BAP address corresponding to the *iab-IP-AddressIndex*. + - 3> else if *iab-IP-Usage* is set to *fl-U*: + - 4> store the received IPv6 address for F1-U traffic together with the IAB-donor-DU BAP address corresponding to the *iab-IP-AddressIndex*. + - 3> else if *iab-IP-Usage* is set to *non-F1*: + - 4> store the received IPv6 address for non-F1 traffic together with the IAB-donor-DU BAP address corresponding to the *iab-IP-AddressIndex*. + - 3> else: + - 4> store the received IPv6 address for all traffic together with the IAB-donor-DU BAP address corresponding to the *iab-IP-AddressIndex*. +- 2> else if *iPv6-Prefix* is included in *iab-IP-AddressToAddModList*: + - 3> if *iab-IP-Usage* is set to *fl-C*: + - 4> store the received IPv6 address prefix for F1-C traffic together with the IAB-donor-DU BAP address corresponding to the *iab-IP-AddressIndex*. + - 3> else if *iab-IP-Usage* is set to *fl-U*: + - 4> store the received IPv6 address prefix for F1-U traffic together with the IAB-donor-DU BAP address corresponding to the *iab-IP-AddressIndex*. + - 3> else if *iab-IP-Usage* is set to *non-F1*: + - 4> store the received IPv6 address prefix for non-F1 traffic together with the IAB-donor-DU BAP address corresponding to the *iab-IP-AddressIndex*. + - 3> else: + - 4> store the received IPv6 address prefix for all traffic together with the IAB-donor-DU BAP address corresponding to the *iab-IP-AddressIndex*. + - 1> for each *iab-IP-AddressIndex* value included in the *iab-IP-AddressToAddModList* that is part of the current IAB-MT configuration: + - 2> modify the IP address configuration(s) in accordance with the *IAB-IP-AddressConfiguration* corresponding to the *iab-IP-AddressIndex*. + +### 5.3.5.13 Conditional Reconfiguration + +#### 5.3.5.13.1 General + +The network configures the UE with one or more candidate target SpCells in the conditional reconfiguration. The UE evaluates the condition of each configured candidate target SpCell. The UE applies the conditional reconfiguration associated with one of the target SpCells which fulfils associated execution condition. + +The network can also configure the UE with one or more candidate target PCells associated with one or more candidate target PSCells. The UE evaluates the conditions for the candidate target PCells and the associated candidate target PSCells in parallel and applies a target configuration that include PCell and PSCell for which the associated execution conditions are fulfilled. If there are multiple candidate PSCells associated with one candidate target PCell, the network provides multiple conditional configurations for the same candidate target PCell, i.e., each configuration contains one MCG configuration (for the same candidate target PCell) and one SCG configuration (for one of the multiple associated candidate PSCells). For this case, the network may also provide a complementary CHO only configuration, i.e., there is execution condition only for candidate PCell. + +The network provides the configuration parameters for the target SpCell(s) in the *condRRCReconfig*. + +In NR-DC, the UE may receive two independent *conditionalReconfiguration*: + +- a *conditionalReconfiguration* associated with MCG, that is included in the *RRCReconfiguration* message received via SRB1; and +- a *conditionalReconfiguration*, associated with SCG, that is included in the *RRCReconfiguration* message received via SRB3, or, alternatively, included within a *RRCReconfiguration* message embedded in a *RRCReconfiguration* message received via SRB1. + +In this case: + +- the UE maintains two independent *VarConditionalReconfig*, one associated with each *conditionalReconfiguration*; +- the UE independently performs all the procedures in clause 5.3.5.13 for each *conditionalReconfiguration* and the associated *VarConditionalReconfig*, unless explicitly stated otherwise; +- the UE performs the procedures in clause 5.5 for the *VarConditionalReconfig* associated with the same cell group like the *measConfig*. + +In EN-DC, the *VarConditionalReconfig* is associated with the SCG. + +In NE-DC and when no SCG is configured, the *VarConditionalReconfig* is associated with the MCG. + +The UE performs the following actions based on a received *ConditionalReconfiguration* IE: + +- 1> if the *ConditionalReconfiguration* contains the *condReconfigToRemoveList*: + - 2> perform conditional reconfiguration removal procedure as specified in 5.3.5.13.2; +- 1> if the *ConditionalReconfiguration* contains the *condReconfigToAddModList*: + - 2> perform conditional reconfiguration addition/modification as specified in 5.3.5.13.3; +- 1> if the *ConditionalReconfiguration* contains the *scpac-ReferenceConfiguration*: + - 2> perform subsequent CPAC reference configuration addition/removal as specified in 5.3.5.13.6; +- 1> if the *ConditionalReconfiguration* contains the *sk-CounterConfiguration*: + +- 2> perform *sk-CounterList* addition/modification/removal as specified in 5.3.5.13.7; +- 1> if the *ConditionalReconfiguration* contains the *servingSecurityCellSetId*: + - 2> if the current *VarServingSecurityCellSetID* includes *servingSecurityCellSetId*: + - 3> replace the *servingSecurityCellSetId* value within *VarServingSecurityCellSetID* with the received *servingSecurityCellSetID*; + - 2> else: + - 3> store the received *servingSecurityCellSetId* within *VarServingSecurityCellSetID*. + +### 5.3.5.13.2 Conditional reconfiguration removal + +The UE shall: + +- 1> for each *condReconfigId* value included in the *condReconfigToRemoveList* that is part of the current UE conditional reconfiguration in *VarConditionalReconfig*: + - 2> remove the entry with the matching *condReconfigId* from the *VarConditionalReconfig*; + +NOTE 1: The UE does not consider the message as erroneous if the *condReconfigToRemoveList* includes any *condReconfigId* value that is not part of the current UE configuration. + +NOTE 2: The UE does not consider the message as erroneous if the *condExecutionCondToReleaseList* includes any *condReconfigId* value that is not part of the current UE configuration. + +### 5.3.5.13.3 Conditional reconfiguration addition/modification + +For each *condReconfigId* received in the *condReconfigToAddModList* IE the UE shall: + +- 1> if an entry with the matching *condReconfigId* exists in the *condReconfigToAddModList* within the *VarConditionalReconfig*: + - 2> if the entry in *condReconfigToAddModList* includes an *condExecutionCond*, *condExecutionCondSCG*, or *condExecutionCondPSCell*: + - 3> replace *condExecutionCond*, *condExecutionCondSCG*, or *condExecutionCondPSCell* within the *VarConditionalReconfig* with the value received for this *condReconfigId*; + - 2> if the entry in *condReconfigToAddModList* includes *subsequentCondReconfig* containing *condExecutionCondToAddModList*: + - 3> for each *condReconfigId* received in *condExecutionCondToAddModList*: + - 4> if an entry with the matching *condReconfigId* exists in the *condExecutionCondToAddModList* within *VarConditionalReconfig*: + - 5> replace the entry in *condExecutionCondToAddModList* within *VarConditionalReconfig* with the value received for this *condReconfigId*; + +4> else: + +5> add a new entry in *condExecutionCondToAddModList* within *VarConditionalReconfig* with the value received for this *condReconfigId*; + +2> if the entry in *condReconfigToAddModList* includes *subsequentCondReconfig* containing *condExecutionCondToReleaseList*: + +3> for each *condReconfigId* received in *condExecutionCondToReleaseList* that is part of current stored *condExecutionCondToAddModList* within *VarConditionalReconfig*: + +4> remove the entry in *condExecutionCondToAddModList* within *VarConditionalReconfig* with the value received for this *condReconfigId*; + +2> if the entry in *condReconfigToAddModList* includes an *securityCellSetId*: + +3> replace *securityCellSetId* within the *VarConditionalReconfig* with the value received for this *condReconfigId*; + +NOTE: The UE should release the entry within *VarServingSecurityCellSetID* in case all the subsequent CPAC configurations are released. + +2> if the entry in *condReconfigToAddModList* includes an *condRRCReconfig*: + +3> replace *condRRCReconfig* within the *VarConditionalReconfig* with the value received for this *condReconfigId*; + +1> else: + +2> add a new entry for this *condReconfigId* within the *VarConditionalReconfig*; + +1> perform conditional reconfiguration evaluation as specified in 5.3.5.13.4; + +#### 5.3.5.13.4 Conditional reconfiguration evaluation + +The UE shall: + +1> for each *condReconfigId* within the *VarConditionalReconfig*: + +2> if the *RRCReconfiguration* within *condRRCReconfig* includes the *masterCellGroup* including the *reconfigurationWithSync*: + +3> if the associated *condExecutionCondPSCell* is configured: + +4> consider the cell which has a physical cell identity matching the value indicated in the *ServingCellConfigCommon* included in the *reconfigurationWithSync* within the *masterCellGroup* in the received *condRRCReconfig* to be applicable cell; and + +4> consider the cell which has a physical cell identity matching the value indicated in the *ServingCellConfigCommon* included in the *reconfigurationWithSync* within the *secondaryCellGroup* within the *nr-SCG* within the received *condRRCReconfig* to be applicable cell; + +3> else: + +- 4> consider the cell which has a physical cell identity matching the value indicated in the *ServingCellConfigCommon* included in the *reconfigurationWithSync* within the *masterCellGroup* in the received *condRRReconfig* to be applicable cell; +- 2> else if the *RRReconfiguration* within *condRRReconfig* includes the *secondaryCellGroup* including the *reconfigurationWithSync*: + - 3> if the cell which has a physical cell identity matching the value indicated in the *ServingCellConfigCommon* included in the *reconfigurationWithSync* within the *secondaryCellGroup* within the received *condRRReconfig* is not the PSCell: + - 4> consider the cell to be applicable cell; +- 2> if *condExecutionCondSCG* is configured: + - 3> in the remainder of the procedure, consider each *measId* indicated in the *condExecutionCondSCG* as a *measId* in the *VarMeasConfig* associated with the SCG *measConfig*; +- 2> if the *condExecutionCondPSCell* is configured: + - 3> in the remainder of the procedure, consider each *measId* indicated in the *condExecutionCondPSCell* as a *measId* in the *VarMeasConfig* associated with the MCG *measConfig*; +- 2> if *condExecutionCond* is configured: + - 3> if it is configured via SRB3 or configured within *nr-SCG* or within *nr-SecondaryCellGroupConfig* (specified in TS 36.331[10]) via SRB1: + - 4> in the remainder of the procedure, consider each *measId* indicated in the *condExecutionCond* as a *measId* in the *VarMeasConfig* associated with the SCG *measConfig*; + - 3> else: + - 4> in the remainder of the procedure, consider each *measId* indicated in the *condExecutionCond* as a *measId* in the *VarMeasConfig* associated with the MCG *measConfig*; +- 2> for each *measId* included in the *measIdList* within *VarMeasConfig* indicated in the *condExecutionCond*, *condExecutionCondSCG*, or *condExecutionCondPSCell* associated to *condReconfigId*: + - 3> if the *condTriggerConfig* is not configured with *nesEvent*: + - 4> if the *condEventId* is associated with *condEventT1*, and if the entry condition applicable for this event associated with the *condReconfigId*, i.e. the event corresponding with the *condEventId(s)* of the corresponding *condTriggerConfig* within *VarConditionalReconfig*, is fulfilled for the applicable cell; or + - 4> if the *condEventId* is associated with *condEventD1*, and if the entry conditions applicable for this event associated with the *condReconfigId*, i.e. the event corresponding with the *condEventId(s)* of the corresponding *condTriggerConfig* within *VarConditionalReconfig*, is fulfilled for the applicable cell during the corresponding *timeToTrigger* defined for this event within the *VarConditionalReconfig*; or + +- 4> if the *condEventId* is associated with *condEventD2*, and if the entry conditions applicable for this event associated with the *condReconfigId*, i.e., the event corresponding with the *condEventId(s)* of the corresponding *condTriggerConfig* within *VarConditionalReconfig*, is fulfilled for the applicable cell during the corresponding *timeToTrigger* defined for this event within the *VarConditionalReconfig*; or + - 4> if the *condEventId* is associated with *condEventA3*, *condEventA4* or *condEventA5*, and if the entry condition(s) applicable for this event associated with the *condReconfigId*, i.e. the event corresponding with the *condEventId(s)* of the corresponding *condTriggerConfig* within *VarConditionalReconfig*, is fulfilled for the applicable cells for all measurements after layer 3 filtering taken during the corresponding *timeToTrigger* defined for this event within the *VarConditionalReconfig*: + - 5> consider the event associated to that *measId* to be fulfilled; + - 4> if the *measId* for this event associated with the *condReconfigId* has been modified; or + - 4> if the *condEventId* is associated with *condEventT1*, and if the leaving condition applicable for this event associated with the *condReconfigId*, i.e. the event corresponding with the *condEventId(s)* of the corresponding *condTriggerConfig* within *VarConditionalReconfig*, is fulfilled for the applicable cell; or + - 4> if the *condEventId* is associated with *condEventD1*, and if the leaving condition(s) applicable for this event associated with the *condReconfigId*, i.e. the event corresponding with the *condEventId(s)* of the corresponding *condTriggerConfig* within *VarConditionalReconfig*, is fulfilled for the applicable cell during the corresponding *timeToTrigger* defined for this event within the *VarConditionalReconfig*; or + - 4> if the *condEventId* is associated with *condEventD2*, and if the leaving condition(s) applicable for this event associated with the *condReconfigId*, i.e., the event corresponding with the *condEventId(s)* of the corresponding *condTriggerConfig* within *VarConditionalReconfig*, is fulfilled for the applicable cell during the corresponding *timeToTrigger* defined for this event within the *VarConditionalReconfig*; or + - 4> if the *condEventId* is associated with *condEventA3*, *condEventA4* or *condEventA5*, and if the leaving condition(s) applicable for this event associated with the *condReconfigId*, i.e. the event corresponding with the *condEventId(s)* of the corresponding *condTriggerConfig* within *VarConditionalReconfig*, is fulfilled for the applicable cells for all measurements after layer 3 filtering taken during the corresponding *timeToTrigger* defined for this event within the *VarConditionalReconfig*: + - 5> consider the event associated to that *measId* to be not fulfilled; +- 3> else: +- 4> if NES mode indication is received from lower layers, indicating that the NES-specific CHO execution condition is enabled; and + - 4> if the entry condition(s) applicable for this event associated with the *condReconfigId*, i.e. the event corresponding with the *condEventId(s)* of the corresponding *condTriggerConfig* within *VarConditionalReconfig*, is fulfilled for the applicable cells for all measurements after layer 3 filtering taken during the corresponding *timeToTrigger* defined for this event within the *VarConditionalReconfig*: + - 5> consider the event associated to that *measId* to be fulfilled; + - 4> if the *measId* for this event associated with the *condReconfigId* has been modified; or + +- 4> if NES mode indication is received from lower layers, indicating that the NES-specific CHO execution condition is disabled; or +- 4> if the leaving condition(s) applicable for this event associated with the *condReconfigId*, i.e. the event corresponding with the *condEventId(s)* of the corresponding *condTriggerConfig* within *VarConditionalReconfig*, is fulfilled for the applicable cells for all measurements after layer 3 filtering taken during the corresponding *timeToTrigger* defined for this event within the *VarConditionalReconfig*: + - 5> consider the event associated to that *measId* to be not fulfilled; + +2> if *condExecutionCondPSCell* is not configured: + +- 3> if event(s) associated to all *measId(s)* within *condTriggerConfig* for the applicable cell are fulfilled: + - 4> consider the applicable cell, associated to that *condReconfigId*, as a triggered cell; + - 4> initiate the conditional reconfiguration execution, as specified in 5.3.5.13.5; + +2> else: + +- 3> if event(s) associated to all *measId(s)*, as indicated in the *condExecutionCond* and *condExecutionCondPSCell*, within *condTriggerConfig* for a target candidate cell within the stored *condRRReconfig* are fulfilled: + - 4> consider the target candidate PCell within the stored *condRRReconfig*, associated to that *condReconfigId*, as a triggered PCell; + - 4> consider the target candidate PSCell within the stored *condRRReconfig*, associated to that *condReconfigId*, as a triggered PSCell; + - 4> initiate the conditional reconfiguration execution, as specified in 5.3.5.13.5. + +2> if one of the events associated to the *measIds* within *condTriggerConfig* for the applicable cell within the stored *condRRReconfig* is not configured with *nesEvent*, and the other event associated to the *measIds* within *condTriggerConfig* for the applicable cell within the stored *condRRReconfig* is configured with *nesEvent*, and at least one of them is fulfilled: + +- 3> consider the applicable cell within the stored *condRRReconfig*, associated to that *condReconfigId*, as a triggered cell; +- 3> initiate the conditional reconfiguration execution, as specified in 5.3.5.13.5; + +NOTE 1: Up to 2 *MeasId* can be configured for each *condReconfigId*, if *condExecutionCondPSCell* is not configured. The conditional reconfiguration event of the 2 *MeasId* may have the same or different event conditions, triggering quantity, time to trigger, and triggering threshold. + +NOTE 2: Void. + +NOTE 3: For CHO with candidate SCGs, up to 2 *MeasId* can be configured for *condExecutionCond* and up to 2 *MeasId* can be configured for *condExecutionCondPSCell* for each *condReconfigId*. + +#### 5.3.5.13.4a Conditional reconfiguration evaluation of SN initiated inter-SN CPC for EN-DC + +The UE shall: + +- 1> for each *condReconfigurationId* within the *VarConditionalReconfiguration* specified in TS 36.331[10]: + - 2> for each *measId* included in the *measIdList* within *VarMeasConfig* indicated in the *CondReconfigExecCondSCG* contained in the *triggerConditionSN* associated to the *condReconfigurationId* as specified in TS 36.331[10]: + - 3> if the entry condition(s) applicable for the event associated with that *measId*, is fulfilled for the applicable cells for all measurements after layer 3 filtering taken during the corresponding *timeToTrigger* defined for this event associated with that *measId*: + - 4> consider this event to be fulfilled; + - 3> if the *measId* for this event has been modified; or + - 3> if the leaving condition(s) applicable for this event associated with that *measId*, is fulfilled for the applicable cells for all measurements after layer 3 filtering taken during the corresponding *timeToTrigger* defined for this event associated with that *measId*: + - 4> consider this event associated to that *measId* to be not fulfilled; + +- 2> if trigger conditions for all events associated with the *measId(s)* indicated in the *CondReconfigExecCondSCG* contained in the *triggerConditionSN* as specified in TS 36.331[10]), are fulfilled: + - 3> consider the target cell candidate within the *RRRCReconfiguration* message contained in *nr-SecondaryCellGroupConfig* in the *RRRConnectionReconfiguration* message, as specified in TS 36.331[10], contained in the stored *condReconfigurationToApply*, associated to that *condReconfigurationId* as specified in TS 36.331[10]), clause 5.3.5.9.4, as a triggered cell; + - 3> initiate the conditional reconfiguration execution, as specified in TS 36.331[10]), clause 5.3.5.9.5; + +NOTE: Void. + +##### 5.3.5.13.5 Conditional reconfiguration execution + +The UE shall: + +- 1> if more than one pair of triggered PCell and associated triggered PSCell exist: + - 2> select one of the triggered PCell(s) and the associated triggered PSCell(s) as the selected cells for conditional reconfiguration execution; +- 1> else if only one pair of triggered PCell and associated triggered PSCell exists: + - 2> consider the triggered PCell and the associated triggered PSCell as the selected cells for conditional reconfiguration execution; +- 1> else if more than one triggered cell exists: + - 2> select one of the triggered cells as the selected cell for conditional reconfiguration execution; +- 1> else: + - 2> consider the triggered cell as the selected cell for conditional reconfiguration execution; +- 1> for the selected cell(s) of conditional reconfiguration execution: + - 2> if the *subsequentCondReconfig* is included in the entry in *VarConditionalReconfig* containing the *RRRCReconfiguration* message for the selected cell: + - 3> perform the actions as specified in 5.3.5.13.8; + - 2> else: + - 3> apply the stored *condRRRCReconfig* of the selected cell and perform the actions as specified in 5.3.5.3; + +NOTE: If multiple NR cells are triggered in conditional reconfiguration execution, it is up to UE implementation which one to select, e.g. the UE considers beams and beam quality to select one of the triggered cells for execution. + +##### 5.3.5.13.6 Subsequent CPAC reference configuration addition/removal + +The UE shall: + +- 1> if the *scpac-ReferenceConfiguration* is set to *setup*: + - 2> if *scpac-ReferenceConfiguration* exists within the *VarConditionalReconfig*: + - 3> replace the *scpac-ReferenceConfiguration* within the *VarConditionalReconfig*; + - 2> else: + - 3> store the *scpac-ReferenceConfiguration* within the *VarConditionalReconfig*; +- 1> else (if *scpac-ReferenceConfiguration* is set to *release*): + - 2> remove the *scpac-ReferenceConfiguration* within the *VarConditionalReconfig*; + +##### 5.3.5.13.7 sk-Counter configuration addition/modification/removal + +The UE shall: + +- 1> for each *securityCellSetId* received in the *sk-CounterConfigToAddModList* IE: + - 2> if an entry with the matching *securityCellSetId* exists in the *sk-CounterConfigToAddModList* within the *VarConditionalReconfig*: + - 3> replace the *sk-CounterList* within the *VarConditionalReconfig* with the *sk-CounterList* according to the received *securityCellSetId*; + - 2> else: + - 3> add a new entry for this *securityCellSetId* within the *VarConditionalReconfig*; +- 1> for each *securityCellSetId* value included in the *sk-CounterConfigToRemoveList* that is part of the current *sk-CounterConfigToAddModList* in *VarConditionalReconfig*: + - 2> remove the entry with the matching *securityCellSetId* from the *sk-CounterConfigToAddModList*; + +##### 5.3.5.13.8 Subsequent CPAC execution + +Upon the conditional reconfiguration execution for subsequent CPAC, the UE shall: + +- 1> if the selected subsequent CPAC candidate configuration is stored in MCG *VarConditionalReconfig*: + - 2> release/clear all current dedicated radio configuration except for the following: + +- the MCG C-RNTI; +- the AS security configurations associated with the master key and the secondary key; +- for each SRB/DRB in current UE configuration: + - keep the associated RLC, PDCP and SDAP entities, their state variables, buffers and timers; + - release all fields related to the SRB/DRB configuration except for *srb-Identity* and *drb-Identity*; +- the UE variables *VarConditionalReconfig* and *VarServingSecurityCellSetID*. + +2> release/clear all current common radio configuration; + +1> else: + +2> release/clear all current dedicated radio configuration associated with the SCG except for the following: + +- the AS security configurations associated with the secondary key; +- for each SRB/DRB in current UE configuration which is using the secondary key: + - keep the associated RLC, PDCP and SDAP entities, their state variables, buffers and timers; + - release all fields related to the SRB/DRB configuration except for *srb-Identity* and *drb-Identity*; +- the UE variables *VarConditionalReconfig*. + +2> release/clear all current common radio configuration associated with the SCG; + +1> use the default values specified in 9.2.3 for timers T310, T311 and constants N310, N311 for the cell group for which the subsequent CPAC cell switch procedure is triggered; + +1> if the *securityCellSetId* is included in the entry in *VarConditionalReconfig* containing the *RRCReconfiguration* message: + +2> if *servingSecurityCellSetId* is not included within *VarServingSecurityCellSetID*; or + +2> if the value of the *securityCellSetId* is not equal to the value of *servingSecurityCellSetId* within *VarServingSecurityCellSetID*: + +3> consider the first *sk-Counter* value in the *sk-CounterList* associated with the *securityCellSetId* within the *VarConditionalReconfig* as the selected *sk-Counter* value, and perform security key update procedure as specified in 5.3.5.7; + +3> remove the selected *sk-Counter* value from the *sk-CounterList* associated with the *securityCellSetId* within the *VarConditionalReconfig*; + +3> if the current *VarServingSecurityCellSetID* includes *servingSecurityCellSetId*: + +4> replace the value of *servingSecurityCellSetId* within *VarServingSecurityCellSetID* with the value of *securityCellSetId* associated with the selected cell; + +3> else: + +4> store the *servingSecurityCellSetId* within *VarServingSecurityCellSetID* with the value of *securityCellSetId* associated with the selected cell; + +1> if the selected subsequent CPAC candidate configuration is stored in the SCG *VarConditionalReconfig*: + +2> for each *drb-Identity* value included in *RadioBearerConfig* associated with the secondary key ( $S-K_{\text{gNB}}$ ) as indicated by *keyToUse* that is part of the current UE configuration: + +3> trigger the PDCP entity of the AM DRB to perform PDCP data recovery as specified in TS 38.323 [5]; + +3> re-establish the corresponding RLC entity as specified in TS 38.322 [4]; + +*Editor's Note: FFS how the L2 reset (PDCP re-establishment, PDCP recovery, and RLC re-establishment) is indicated by the network in case of subsequent CPAC.* + +1> else: + +2> for each *drb-Identity* value included in *RadioBearerConfig* that is part of the current UE configuration: + +3> if a different *keyToUse* value is configured; or + +3> if a new *sk-Counter* value has been selected due to the conditional reconfiguration execution for subsequent CPAC: + +4> trigger the PDCP entity of the bearer to perform PDCP reestablishment as specified in TS 38.323 [5]; + +3> else: + +4> trigger the PDCP entity of the AM DRB to perform PDCP data recovery as specified in TS 38.323 [5]; + +4> re-establish the corresponding RLC entity as specified in TS 38.322 [4]; + +1> if *scpac-ConfigComplete* is not included within the *VarConditionalReconfig* for the selected cell: + +2> if the subsequent CPAC candidate cell configuration is stored in MCG *VarConditionalReconfig*: + +3> consider *scpac-ReferenceConfiguration* in MCG *VarConditionalReconfig* to be the current UE configuration; + +2> else: + +3> consider *scpac-ReferenceConfiguration* in SCG *VarConditionalReconfig* to be the current SCG configuration; + +NOTE 1: When the UE considers the reference configuration to be the current UE configuration, the UE should store fields and configurations that are part of the reference configuration but should not execute any actions or procedures triggered by the reception of an *RRCReconfiguration* message which are described in clause 5.3.5.3. + +- 1> apply the stored *condRRCReconfig* of the selected cell(s) and perform the actions as specified in 5.3.5.3; +- 1> release the radio bearer(s) and the associated logical channel(s) that are part of the current UE configuration but not part of the subsequent CPAC candidate configuration for the selected cell, or the subsequent CPAC reference configuration (in case the subsequent CPAC candidate configuration does not include *scpac-ConfigComplete*). + +NOTE 2: When *scpac-ConfigComplete* is not included for the selected cell, before a subsequent CPAC execution, a UE implementation may generate and store an RRC reconfiguration message by applying the received subsequent CPAC candidate configuration on top of the subsequent CPAC reference configuration, and the stored RRC reconfiguration message is applied for subsequent CPAC execution. + +#### 5.3.5.13a SCG activation + +Upon initiating the procedure, the UE shall: + +- 1> if the UE is configured with an SCG after receiving the message for which this procedure is initiated: + - 2> if the UE was configured with a deactivated SCG before receiving the message for which this procedure is initiated: + - 3> consider the SCG to be activated; + - 3> resume performing radio link monitoring on the SCG, if previously stopped; + - 3> indicate to lower layers to resume beam failure detection on the PSCell, if previously stopped; + - 3> indicate to lower layers that the SCG is activated. + +#### 5.3.5.13b SCG deactivation + +Upon initiating the procedure, the UE shall: + +- 1> consider the SCG to be deactivated; +- 1> indicate to lower layers that the SCG is deactivated; +- 1> if *bfd-and-RLM* is configured to *true*: + - 2> perform radio link monitoring on the SCG; + - 2> indicate to lower layers to perform beam failure detection on the PSCell; +- 1> else: + +- 2> stop radio link monitoring on the SCG; + - 2> indicate to lower layers to stop beam failure detection on the PSCell; + - 2> stop timer T310 for this cell group, if running; + - 2> stop timer T312 for this cell group, if running; + - 2> reset the counters N310 and N311; +- 1> if the UE was in RRC\_CONNECTED and the SCG was activated before receiving the message for which this procedure is initiated: + - 2> if SRB3 was configured before the reception of the *RRCREconfiguration* or of the *RRRConnectionReconfiguration* and SRB3 is not to be released according to any *RadioBearerConfig* included in the *RRCREconfiguration* or in the *RRRConnectionReconfiguration* as specified in TS 36.331[10]: + - 3> trigger the PDCP entity of SRB3 to perform SDU discard as specified in TS 38.323 [5]; + - 3> re-establish the RLC entity of SRB3 as specified in TS 38.322 [4]. + +##### 5.3.5.13b1 SCG activation without SN message + +Upon initiating the procedure, the UE shall: + +- 1> if the SCG was deactivated before the reception of the *RRCREconfiguration* message or the E-UTRA *RRRConnectionReconfiguration* message for which the procedure invoking this clause is executed: + - 2> consider the SCG to be activated; + - 2> indicate to lower layers that the SCG is activated; + - 2> resume performing radio link monitoring on the SCG, if previously stopped; + - 2> indicate to lower layers to resume beam failure detection on the PSCell, if previously stopped; + - 2> if *bfd-and-RLM* was not configured to true before the reception of the *RRCREconfiguration* message or the E-UTRA *RRRConnectionReconfiguration* message for which the procedure invoking this clause is executed; or + - 2> if lower layers indicate that a Random Access procedure is needed for SCG activation: + - 3> initiate the Random Access procedure on the PSCell, as specified in TS 38.321 [3]. + +#### 5.3.5.13c FR2 UL gap configuration + +The UE shall: + +1> if *ul-GapFR2-Config* is set to setup: + +2> if an FR2 UL gap configuration is already setup, release the FR2 UL gap configuration; + +2> setup the FR2 UL gap configuration indicated by the *ul-GapFR2-Config* in accordance with the received *gapOffset*, i.e., the first subframe of each gap occurs at an SFN and subframe meeting the following condition: + +SFN mod T = FLOOR (*gapOffset*/10); + +if the UGRP is larger than 5ms: + +subframe = *gapOffset* mod 10; + +else: + +subframe = *gapOffset* or (*gapOffset* +5); + +with T = CEIL(UGRP/10). + +1> else if *ul-GapFR2-Config* is set to release: + +2> release the FR2 UL gap configuration. + +NOTE 1: For *ul-GapFR2-Config* configuration with synchronous CA, the SFN and subframe of a serving cell on FR2 frequency is used in the gap calculation. For *ul-GapFR2-Config* configuration with asynchronous CA, the SFN and subframe of a serving cell on FR2 frequency indicated by the *refFR2-ServCellAsyncCA* in *ul-GapFR2-Config* is used in the gap calculation. + +#### 5.3.5.13d Application layer measurement configuration + +The UE shall: + +1> if *measConfigAppLayerToReleaseList* is included in *appLayerMeasConfig* within *RRCReconfiguration* or *RRCResume*: + +2> for each *measConfigAppLayerId* value included in the *measConfigAppLayerToReleaseList*: + +3> forward the *measConfigAppLayerId* and inform upper layers about the release of the application layer measurement configuration including any RAN visible application layer measurement configuration; + +3> discard any application layer measurement report received from upper layers; + +3> if stored, release the application layer measurement configuration in UE variables *VarAppLayerIdleConfig* and *VarAppLayerPLMN-ListConfig*; + +3> consider itself not to be configured to send application layer measurement report for the *measConfigAppLayerId*. + +- 1> if *measConfigAppLayerToAddModList* is included in *appLayerMeasConfig* within *RRReconfiguration* or *RRResume*: + - 2> for each *measConfigAppLayerId* value included in the *measConfigAppLayerToAddModList*: + - 3> if *measConfigAppLayerContainer* is included for the corresponding *MeasConfigAppLayer* configuration: + - 4> forward the *measConfigAppLayerContainer*, the *measConfigAppLayerId* and the *serviceType* to upper layers considering the *serviceType*; + - 3> consider itself to be configured to send application layer measurement report for the *measConfigAppLayerId* in accordance with 5.7.16; + - 3> forward the *transmissionOfSessionStartStop*, if configured, and *measConfigAppLayerId* to upper layers considering the *serviceType*; + - 3> if *ran-VisibleParameters* is set to setup and the parameters have been received: + - 4> forward the *measConfigAppLayerId*, the *ran-VisiblePeriodicity*, if configured, the *numberOfBufferLevelEntries*, if configured, and the *reportPlayoutDelayForMediaStartup*, if configured, to upper layers considering the *serviceType*; + - 3> else if *ran-VisibleParameters* is set to release: + - 4> forward the *measConfigAppLayerId* and inform upper layers about the release of the RAN visible application layer measurement configuration; + - 3> if *pauseReporting* is set to *true*: + - 4> if at least one segment, but not all segments, of a segmented *MeasurementReportAppLayer* message containing an application layer measurement report associated with the *measConfigAppLayerId* has been submitted to lower layers for transmission: + - 5> submit the remaining segments of the *MeasurementReportAppLayer* message to lower layers for transmission; + - 4> suspend submitting application layer measurement report containers to lower layers for the application layer measurement configuration associated with the *measConfigAppLayerId*; + - 4> store any previously or subsequently received application layer measurement report containers associated with the *measConfigAppLayerId* for which no segment, or full message, has been submitted to lower layers for transmission; + - 4> if the memory reserved for storing application layer measurement report containers becomes full while the reporting is paused and if the UE is configured with *appLayerMeasPriority*: + - 5> discard reports in priority order where reports with the lowest priority are discarded first; + - 3> else if *pauseReporting* is set to *false* and if transmission of application layer measurement report containers has previously been suspended for the application layer measurement configuration associated with the *measConfigAppLayerId*: + - 4> submit stored application layer measurement report containers to lower layers, if any, for the application layer measurements configuration associated with the *measConfigAppLayerId*; + +- 4> resume submitting application layer measurement report containers to lower layers for the application layer measurement configuration associated with the *measConfigAppLayerId*; +- 3> if *configForRRC-IdleInactive* is set to *true*: + - 4> store the received *qoe-Reference*, *measConfigAppLayerId*, *serviceType*, *qoe-MeasurementType*, *qoe-AeaScope*, *mce-Id*, *configForRRC-IdleInactive*, *appLayerMeasPriority*, if included, in *VarAppLayerIdleConfig*; + - 4> if the *qoe-AreaScope* includes *plmn-IdentityList*: + - 5> set *plmn-IdentityList* in *VarAppLayerPLMN-ListConfig* to include the RPLMN as well as the PLMNs included in *plmn-IdentityList*; + - 4> else: + - 5> set *plmn-IdentityList* in *VarAppLayerPLMN-ListConfig* to include the RPLMN; + +NOTE 1: The UE may discard reports when the memory reserved for storing application layer measurement report containers becomes full. If no *appLayerMeasPriority* is configured, older reports may be discarded first. + +NOTE 2: The transmission of RAN visible application layer measurement reports and *appLayerSessionStatus* is not paused when *pauseReporting* is set to *true*. + +NOTE 3: The UE may discard an application layer measurement configuration and associated unsent reports after 48 hours. + +Editor's Note: FFS on when the 48 hours start for when the UE may discard application layer measurement configuration and reports. + +#### 5.3.5.14 Sidelink dedicated configuration + +Upon initiating the procedure, the UE shall: + +- 1> if *sl-FreqInfoToReleaseList* is included in *sl-ConfigDedicatedNR* within *RRReconfiguration*: + - 2> for each entry included in the received *sl-FreqInfoToReleaseList* that is part of the current UE configuration: + - 3> release the related configurations from the stored NR sidelink communication/discovery configurations; +- 1> if *sl-FreqInfoToAddModList/sl-FreqInfoToAddModListExt* is included in *sl-ConfigDedicatedNR* within *RRReconfiguration*: + - 2> if configured to receive NR sidelink communication: + - 3> use the resource pool(s) indicated by *sl-RxPool* for NR sidelink communication reception, as specified in 5.8.7; + - 2> if configured to transmit NR sidelink communication: + +- 3> use the resource pool(s) indicated by *sl-TxPoolSelectedNormal*, *sl-TxPoolScheduling* or *sl-TxPoolExceptional* for NR sidelink communication transmission, as specified in 5.8.8; + - 2> if configured to receive NR sidelink discovery: + - 3> use the resource pool(s) indicated by *sl-DiscRxPool* or *sl-RxPool* for NR sidelink discovery reception, as specified in 5.8.13.2; + - 2> if configured to transmit NR sidelink discovery: + - 3> use the resource pool(s) indicated by *sl-DiscTxPoolSelected*, *sl-DiscTxPoolScheduling*, *sl-TxPoolSelectedNormal*, *sl-TxPoolScheduling* or *sl-TxPoolExceptional* for NR sidelink discovery transmission, as specified in 5.8.13.3; + - 2> if configured to receive sidelink control information for SL-PRS measurement: + - 3> use the resource pool(s) indicated by *sl-RxPool* and/or *sl-PRS-RxPool* for SL-PRS reception, as specified in 5.8.18.2; + - 2> if configured to transmit SL-PRS: + - 3> use the resource pool(s) indicated by *sl-PRS-TxPoolSelectedNormal*, *sl-PRS-TxPoolScheduling*, *sl-BWP-PRS-PoolConfig* or *sl-PRS-TxPoolExceptional* for SL-PRS transmission, as specified in 5.8.18.3; + - 2> perform CBR measurement on the transmission resource pool(s) indicated by *sl-TxPoolSelectedNormal*, *sl-TxPoolScheduling*, *sl-PRS-TxPoolSelectedNormal*, *sl-PRS-TxPoolScheduling*, *sl-DiscTxPoolSelected*, *sl-DiscTxPoolScheduling*, *sl-TxPoolExceptional* or *sl-PRS-TxPoolExceptional* for NR sidelink communication/discovery/positioning transmission, as specified in 5.5.3; + - 2> use the synchronization configuration parameters for NR sidelink communication/discovery/positioning on frequencies included in *sl-FreqInfoToAddModList/sl-FreqInfoToAddModListExt*, as specified in 5.8.5; +- 1> if *sl-RadioBearerToReleaseList* or *sl-RLC-BearerToReleaseList* is included in *sl-ConfigDedicatedNR* within *RRCReconfiguration*: + - 2> perform sidelink DRB release as specified in 5.8.9.1a.1; + - 1> if *sl-RLC-BearerToReleaseListSizeExt* is included in *sl-ConfigDedicatedNR* within *RRCReconfiguration*: + - 2> perform additional sidelink RLC bearer release as specified in 5.8.9.1a.5; + - 1> if *sl-RadioBearerToAddModList* or *sl-RLC-BearerToAddModList* is included in *sl-ConfigDedicatedNR* within *RRCReconfiguration*: + - 2> perform sidelink DRB addition/modification as specified in 5.8.9.1a.2; + - 1> if *sl-RLC-BearerToAddModListSizeExt* is included in *sl-ConfigDedicatedNR* within *RRCReconfiguration*: + - 2> perform additional sidelink RLC bearer addition/modification as specified in 5.8.9.1a.6; + +- 1> if *sl-ScheduledConfig* is included in *sl-ConfigDedicatedNR* within *RRReconfiguration*: + - 2> configure the MAC entity parameters, which are to be used for NR sidelink communication/discovery, in accordance with the received *sl-ScheduledConfig*; +- 1> if *sl-UE-SelectedConfig* is included in *sl-ConfigDedicatedNR* within *RRReconfiguration*: + - 2> configure the parameters, which are to be used for NR sidelink communication/discovery, in accordance with the received *sl-UE-SelectedConfig*; +- 1> if *sl-MeasConfigInfoToReleaseList* is included in *sl-ConfigDedicatedNR* within *RRReconfiguration*: + - 2> for each *SL-DestinationIndex* included in the received *sl-MeasConfigInfoToReleaseList* that is part of the current UE configuration: + - 3> remove the entry with the matching *SL-DestinationIndex* from the stored NR sidelink measurement configuration information; +- 1> if *sl-MeasConfigInfoToAddModList* is included in *sl-ConfigDedicatedNR* within *RRReconfiguration*: + - 2> for each *sl-DestinationIndex* included in the received *sl-MeasConfigInfoToAddModList* that is part of the current stored NR sidelink measurement configuration: + - 3> reconfigure the entry according to the value received for this *sl-DestinationIndex* from the stored NR sidelink measurement configuration information; + - 2> for each *sl-DestinationIndex* included in the received *sl-MeasConfigInfoToAddModList* that is not part of the current stored NR sidelink measurement configuration: + - 3> add a new entry for this *sl-DestinationIndex* to the stored NR sidelink measurement configuration. + +NOTE 1: The UE is expected to update the mapping between the Destination Layer-2 ID and the destination index for the stored NR sidelink measurement configuration after the UE updates the destination list and reports to the gNB. + +- 1> if *sl-DRX-ConfigUC-ToReleaseList* is included in *sl-ConfigDedicatedNR* within *RRReconfiguration*: + - 2> for each *SL-DestinationIndex* included in the received *sl-DRX-ConfigUC-ToReleaseList* that is part of the current UE configuration: + - 3> remove the entry with the matching *SL-DestinationIndex* from the stored NR sidelink DRX configuration information; +- 1> if *sl-DRX-ConfigUC-ToAddModList* is included in *sl-ConfigDedicatedNR* within *RRReconfiguration*: + - 2> for each *sl-DestinationIndex* included in the received *sl-DRX-ConfigUC-ToAddModList* that is part of the current stored NR sidelink DRX configuration: + - 3> reconfigure the entry according to the value received for this *sl-DestinationIndex* from the stored NR sidelink DRX configuration information; + - 2> for each *sl-DestinationIndex* included in the received *sl-DRX-ConfigUC-ToAddModList* that is not part of the current stored NR sidelink DRX configuration: + - 3> add a new entry for this *sl-DestinationIndex* to the stored NR sidelink DRX configuration. + +NOTE 2: The UE is expected to update the mapping between the Destination Layer-2 ID and the destination index for the stored NR sidelink DRX configuration after the UE updates the destination list and reports to the gNB. + +- 1> if *sl-RLC-ChannelToReleaseList* is included in *sl-ConfigDedicatedNR* within *RRReconfiguration*: + - 2> perform PC5 Relay RLC channel release as specified in 5.8.9.7.1; +- 1> if *sl-RLC-ChannelToAddModList* is included in *sl-ConfigDedicatedNR* within *RRReconfiguration* or *RRSetup*: + - 2> perform PC5 Relay RLC channel addition/modification as specified in 5.8.9.7.2; + +#### 5.3.5.15 L2 U2N or U2U Relay UE configuration + +##### 5.3.5.15.1 General + +The network configures the L2 U2N or U2U Relay UE with relay operation related configurations. For each connected L2 U2N or U2U Remote UE indicated in *sl-L2IdentityRemote*, the network provides the configuration parameters used for relaying. + +The L2 U2N Relay UE shall: + +- 1> if *sl-L2RelayUE-Config* is set to *setup*: + - 2> if the *sl-L2RelayUE-Config* contains the *sl-RemoteUE-ToReleaseList*: + - 3> perform the L2 U2N Remote UE release as specified in 5.3.5.15.2; + - 2> if the *sl-L2RelayUE-Config* contains the *sl-RemoteUE-ToAddModList*: + - 3> perform the L2 U2N Remote UE addition/modification as specified in 5.3.5.15.3; +- 1> else if *sl-L2RelayUE-Config* is set to *release*: + - 2> release the relay operation related configurations. + +The L2 U2U Relay UE shall: + +- 1> if *sl-L2RelayUE-Config* is set to *setup*: + - 2> if the *sl-L2RelayUE-Config* contains the *sl-U2U-RemoteUE-ToReleaseList*: + - 3> perform the L2 U2U Remote UE release as specified in 5.3.5.15.2; + - 2> if the *sl-L2RelayUE-Config* contains the *sl-U2U-RemoteUE-ToAddModList*: + - 3> perform the L2 U2U Remote UE addition/modification as specified in 5.3.5.15.3; + +3> perform the L2 U2U Remote UE addition/modification as specified in 5.3.5.15.3; + +1> else if *sl-L2RelayUE-Config* is set to release: + +2> release the related configurations. + +##### 5.3.5.15.2 L2 U2N or U2U Remote UE Release + +The L2 U2N Relay UE shall: + +1> if the release is triggered by reception of the *sl-RemoteUE-ToReleaseList*: + +2> for each *SL-DestinationIdentity* value included in the *sl-RemoteUE-ToReleaseList*: + +3> if the current UE has a PC5 RRC connection to a L2 U2N Remote UE with *SL-DestinationIdentity*: + +4> indicate upper layers to trigger PC5 unicast link release. + +The L2 U2U Relay UE shall: + +1> if the release is triggered by reception of the *sl-U2U-RemoteUE-ToReleaseList*: + +2> for each *SL-DestinationIdentity* value included in the *sl-U2U-RemoteUE-ToReleaseList*: + +3> release the configuration associated with the L2 U2U Remote UE. + +##### 5.3.5.15.3 L2 U2N or U2U Remote UE Addition/Modification + +The L2 U2N Relay UE shall: + +1> if no SRAP entity has been established: + +2> establish a SRAP entity as specified in TS 38.351 [66]; + +1> for each *sl-L2IdentityRemote* value included in the *sl-RemoteUE-ToAddModList* that is not part of the current UE configuration (L2 U2N Remote UE Addition): + +2> configure the parameters to SRAP entity in accordance with the *sl-SRAP-ConfigRelay*; + +2> if SRB1 is included in *sl-MappingToAddModList*, and *sl-EgressRLC-ChannelPC5* is configured: + +3> release SL-RLC1, if established; + +3> associate the PC5 Relay RLC channel as indicated by *sl-EgressRLC-ChannelPC5* with SRB1; + +2> else: (i.e. SRB1 is not included in *sl-MappingToAddModList*, or SRB1 is included in *sl-MappingToAddModList*, but *sl-EgressRLC-ChannelPC5* is not configured) + +3> if SL-RLC1 is not established: + +4> apply the default configuration of SL-RLC1 as specified in clause 9.2.4 and associate it with the SRB1; + +1> for each *sl-L2IdentityRemote* value included in the *sl-RemoteUE-ToAddModList* that is part of the current UE configuration (L2 U2N Remote UE modification): + +2> modify the configuration in accordance with the *sl-SRAP-ConfigRelay*; + +The L2 U2U Relay UE shall: + +1> if no SRAP entity has been established: + +2> establish a SRAP entity as specified in TS 38.351 [66]; + +1> for each target L2 U2U Remote UE indicated in *sl-L2IdentityRemote* value included in the *sl-U2U-RemoteUE-ToAddModList* that is not part of the current UE configuration (target L2 U2U Remote UE Addition): + +2> for each source L2 U2U Remote UE indicated in *sl-SourceUE-Identity* in accordance with one entry of the *sl-SourceRemoteUE-ToAddModList*, configure the parameters to SRAP entity in accordance with the *sl-SRAP-ConfigU2U*; + +1> for each target L2 U2U Remote UE indicated in *sl-L2IdentityRemote* value included in the *sl-U2U-RemoteUE-ToAddModList* that is part of the current UE configuration (target L2 U2U Remote UE modification): + +2> for each source L2 U2U Remote UE indicated in *sl-SourceUE-Identity* included in the *sl-SourceRemoteUE-ToReleaseList* (source L2 U2U Remote UE Release): + +3> release the configuration associated with the source L2 U2U Remote UE; + +2> for the source L2 U2U Remote UE indicated in *sl-SourceUE-Identity* included in the *sl-SourceRemoteUE-ToAddModList* that is not part of the current UE configuration (source L2 U2U Remote UE Addition): + +3> configure the parameters to SRAP entity in accordance with the *sl-SRAP-ConfigU2U*; + +2> for the source L2 U2U Remote UE indicated in *sl-SourceUE-Identity* included in the *sl-SourceRemoteUE-ToAddModList* that is part of the current UE configuration (source L2 U2U Remote UE modification): + +3> modify the configuration in accordance with the *sl-SRAP-ConfigU2U*; + +#### 5.3.5.16 L2 U2N or U2U Remote UE configuration + +The network configures the L2 U2N or U2U Remote UE with relay operation related configurations, e.g. SRAP configuration. + +The L2 U2N Remote UE shall: + +- 1> if *sl-L2RemoteUE-Config* is set to *setup* or received from *RRCSetup* message: + - 2> if the *sl-L2RemoteUE-Config* contains the *sl-SRAP-ConfigRemote*: + - 3> if no SRAP entity has been established: + - 4> establish a SRAP entity as specified in TS 38.351 [66]; + - 3> configure the parameters to SRAP entity in accordance with the *sl-SRAP-ConfigRemote*; + - 3> if SRB1 is included in *sl-MappingToAddModList*, and *sl-EgressRLC-ChannelPC5* is configured: + - 4> release SL-RLC1, if established; + - 4> associate the PC5 Relay RLC channel as indicated by *sl-EgressRLC-ChannelPC5* with SRB1; + - 3> else: (i.e. SRB1 is not included in *sl-MappingToAddModList*, or SRB1 is included in *sl-MappingToAddModList*, but *sl-EgressRLC-ChannelPC5* is not configured) + - 4> if SL-RLC1 is not established: + - 5> apply the default configuration of SL-RLC1 as specified in clause 9.2.4 and associate it with the SRB1; + - 2> if the *sl-L2RemoteUE-Config* contains the *sl-UEIdentityRemote*: + - 3> use the value of the *sl-UEIdentityRemote* as the C-RNTI in the PCell. +- 1> else if *sl-L2RemoteUE-Config* is set to *release*: + - 2> release the relay operation related configurations. + +The L2 U2U Remote UE shall: + +- 1> if *sl-L2RemoteUE-Config* is set to *setup*: + - 2> if the *sl-L2RemoteUE-Config* contains the *sl-U2U-RelayUE-ToReleaseList*: + - 3> perform the L2 U2U Relay UE release as specified in 5.3.5.16.1; + - 2> if the *sl-L2RemoteUE-Config* contains the *sl-U2U-RelayUE-ToAddModList*: + - 3> perform the L2 U2U Relay UE addition/modification as specified in 5.3.5.16.2; +- 1> else if *sl-L2RemoteUE-Config* is set to *release*: + - 2> release the related configurations. + +##### 5.3.5.16.1 L2 U2U Relay UE Release + +The L2 U2U Relay UE shall: + +- 1> if the release is triggered by reception of the *sl-U2U-RelayUE-ToReleaseList*: + - 2> for each SL-DestinationIdentity value included in the *sl-U2U-RelayUE-ToReleaseList*: + - 3> release the configuration associated with the L2 U2U Relay UE. + +##### 5.3.5.16.2 L2 U2U Relay UE Addition/Modification + +The L2 U2U Remote UE shall: + +- 1> if no SRAP entity has been established: + - 2> establish a SRAP entity as specified in TS 38.351 [66]; +- 1> for each L2 U2U Relay UE indicated in *sl-L2IdentityRelay* value included in the *sl-U2U-RelayUE-ToAddModList* that is not part of the current UE configuration (L2 U2U Relay UE Addition): + - 2> for peer target L2 U2U Remote UE indicated in *sl-TargetUE-Identity* in accordance with one entry of the *SL-PeerRemoteUE-ToAddModList*, configure the parameters to SRAP entity in accordance with the *sl-SRAP-ConfigU2U*; +- 1> for each L2 U2U Relay UE indicated in *sl-L2IdentityRelay* value included in the *sl-U2U-RelayUE-ToAddModList* that is part of the current UE configuration (L2 U2U Relay UE modification): + - 2> for each peer target L2 U2U Remote UE included in the *sl-PeerRemoteUE-ToReleaseList* (peer target L2 U2U Remote UE Release): + - 3> release the configuration associated with the peer target L2 U2U Remote UE; + - 2> for the peer target L2 U2U Remote UE indicated in *sl-TargetUE-Identity* included in the *sl-PeerTargetRemoteUE-ToAddModList* that is not part of the current UE configuration (peer target L2 U2U Remote UE Addition): + - 3> configure the parameters to SRAP entity in accordance with the *sl-SRAP-ConfigU2U*; + - 2> for the peer target L2 U2U Remote UE indicated in *sl-TargetUE-Identity* included in the *sl-PeerTargetRemoteUE-ToAddModList* that is part of the current UE configuration (peer target L2 U2U Remote UE modification): + - 3> modify the configuration in accordance with the *sl-SRAP-ConfigU2U*; + +#### 5.3.5.17 MP configuration + +##### 5.3.5.17.1 Introduction + +In case of MP, a MP remote UE is configured with one direct path (i.e. MCG) and one indirect path. The MP remote UE connects to network on the direct path using NR Uu, and connects to network on the indirect path via a MP relay UE. + +On indirect path, for the hop between the MP remote UE and the MP relay UE, when the MP remote UE connects to a L2 U2N Relay UE, i.e. the MP remote UE is acting as a L2 U2N Remote UE, the network provides the configuration of SL indirect path to the MP remote UE and the L2 U2N Relay UE as specified in 5.3.5.17.2; when the MP remote UE connects to a N3C relay UE using non-3GPP connection, the network provides the configuration of N3C indirect path to the MP remote UE and the N3C relay UE as specified in 5.3.5.17.3. + +##### 5.3.5.17.2 Configuration of SL indirect path + +###### 5.3.5.17.2.1 General + +For SL indirect path: + +- the L2 U2N Remote UE is provided with sidelink dedicated configuration as specified in 5.3.5.14, L2 U2N Remote UE configuration as specified in 5.3.5.16, and SL indirect path specific configuration as specified in 5.3.5.17.2.2; +- the L2 U2N Relay UE is provided with sidelink dedicated configuration as specified in 5.3.5.14, L2 U2N Relay UE configuration as specified in 5.3.5.15, as well as Uu Relay RLC channel configuration as specified in 5.3.5.5.12 and 5.3.5.5.13. + +###### 5.3.5.17.2.2 SL indirect path specific configuration + +The L2 U2N Remote UE shall: + +- 1> if *sl-IndirectPathAddChange* is set to setup: + - 2> consider the UE indicated by the *sl-IndirectPathRelayUE-Identity* to be the (target) L2 U2N Relay UE and indicate to upper layer to trigger the PC5 unicast link establishment with the L2 U2N Relay UE; + - 2> start timer T421 for the corresponding L2 U2N Relay UE with the timer value set to T421; + - 2> indicate to upper layer (to trigger the PC5 unicast link release) with the source L2 U2N Relay UE in case of SL indirect path change (i.e. a new L2 U2N Relay UE is indicated via *sl-IndirectPathRelayUE-Identity*); +- 1> else if *sl-IndirectPathAddChange* is set to release: + - 2> consider the SL indirect path is released and release the corresponding configurations; + - 2> indicate to upper layer (to trigger the PC5 unicast link release) with the L2 U2N Relay UE. + +###### 5.3.5.17.2.3 T421 expiry (Indirect path addition/change failure) + +The UE shall: + +- 1> if T421 expires; or +- 1> if the (target) L2 U2N Relay UE (i.e., the UE indicated by *sl-IndirectPathRelayUE-Identity* in the received *sl-IndirectPathAddChange*) changes its serving PCell to a different cell from the target cell (i.e. the cell indicated by *sl-IndirectPathCellIdentity* in the received *sl-IndirectPathAddChange*) before path addition or change: + - 2> if MCG transmission is not suspended: + - 3> initiate the indirect path failure information procedure as specified in clause 5.7.3c to report indirect path addition/change failure; + - 2> else: + - 3> initiate the connection re-establishment procedure as specified in clause 5.3.7; + +##### 5.3.5.17.3 Configuration of N3C indirect path + +###### 5.3.5.17.3.1 General + +For N3C indirect path, + +- the N3C remote UE is provided with N3C indirect path configuration including relay UE identification as specified in 5.3.5.17.3.2; +- the N3C relay UE is provided with N3C indirect path configuration including bearer mapping configurations as specified in 5.3.5.17.3.4, as well as Uu Relay RLC channel configuration as specified in 5.3.5.5.12 and 5.3.5.5.13. + +NOTE: The data transmission/reception between the N3C remote UE and the N3C relay UE via the non-3GPP connection is outside the scope of 3GPP. + +###### 5.3.5.17.3.2 N3C remote UE configuration + +The N3C remote UE shall: + +- 1> if *n3c-IndirectPathAddChange* is set to setup: + - 2> consider the non-3GPP connection with the relay UE indicated by the *n3c-RelayIdentification* to be used for the N3C indirect path; + - 2> consider the source non-3GPP connection is not to be used in case of N3C indirect path change (i.e. a new relay UE is indicated by the *n3c-RelayIdentification*); +- 1> else if *n3c-IndirectPathAddChange* is set to release: + - 2> consider the indirect path is not to be used and release the corresponding configuration. + +Editor's Note: whether T421 is applicable to scenario 2. + +###### 5.3.5.17.3.3 N3C relay UE configuration + +The N3C relay UE shall: + +- 1> if *n3c-IndirectPathConfigRelay* is set to setup: + - 2> if *n3c-MappingToReleaseList* is included: + - 3> perform N3C bearer mapping release as specified in 5.3.5.17.3.4.1; + - 2> if *n3c-MappingToAddModList* is included: + - 3> perform N3C bearer mapping addition/modification as specified in 5.3.5.17.3.4.2; +- 1> else if *n3c-IndirectPathConfigRelay* is set to release: + - 2> consider the indirect path with the remote UE is released and release the corresponding configuration. + +###### 5.3.5.17.3.4 Bearer mapping management on N3C indirect path + +###### 5.3.5.17.3.4.1 Bearer mapping release + +The UE shall: + +- 1> if the release is triggered by reception of *n3c-IndirectPathConfigRelay* set to *release*: + - 2> for all configured *SL-RemoteUE-RB-Identity* value: + - 3> release *n3c-RLC-ChannelUu* and *n3c-RemoteUE-RB-Identity*; +- 1> else if the release is triggered by reception of the *n3c-MappingToReleaseList*: + - 2> for each *SL-RemoteUE-RB-Identity* value included in *n3c-MappingToReleaseList*: + - 3> release the corresponding *n3c-RLC-ChannelUu* and *n3c-RemoteUE-RB-Identity*; + +###### 5.3.5.17.3.4.2 Bearer mapping addition and modification + +The UE shall: + +- 1> for each *n3c-RemoteUE-RB-Identity* value included in the *n3c-MappingToAddModList* that is not part of the current UE configuration: + - 2> associate the remote UE's RB indicated in *n3c-RemoteUE-RB-Identity* to the Uu RLC channel indicated in *n3c-RLC-ChannelUu*; + +1> for the *n3c-RemoteUE-RB-Identity* value included in the *n3c-MappingToAddModList* that is part of the current UE configuration: + +2> update the associated Uu RLC channel to the one indicated in *n3c-RLC-ChannelUu*. + +#### 5.3.5.18 LTM configuration and execution + +##### 5.3.5.18.1 LTM configuration + +The network configures the UE with one or more LTM candidate configurations within the *LTM-Config* IE. + +In NR-DC, the UE may receive two independent *ltm-Config*: + +- an *ltm-Config* associated with the MCG that is included within an *RRCReconfiguration* message received via SRB1; and +- an *ltm-Config* associated with the SCG that is included within an *RRCReconfiguration* message either received via SRB3, or, alternatively, embedded in an *RRCReconfiguration* message received via SRB1. + +In case the UE receives two independent *ltm-Config*: + +- the UE maintains two independent *VarLTM-Config*, one associated with each *ltm-Config*; +- the UE maintains two independent *VarLTM-ServingCellNoResetID*, one associated with each *ltm-Config*; +- the UE maintains two independent *VarLTM-ServingCellUE-MeasuredTA-ID*, one associated with each *ltm-Config*; +- the UE independently performs all the procedures in clause 5.3.5.18 for each *ltm-Config* and the associated *VarLTM-Config*, *VarLTM-ServingCellNoResetID*, and *VarLTM-ServingCellUE-MeasuredTA-ID* unless explicitly stated otherwise. + +The UE shall perform the following actions based on the received *LTM-Config* IE: + +1> if the received *LTM-Config* includes *ltm-ReferenceConfiguration* set to *setup*: + +2> if the current *VarLTM-Config* includes an *ltm-ReferenceConfiguration*: + +3> replace the *ltm-ReferenceConfiguration* value within *VarLTM-Config* with the received *ltm-ReferenceConfiguration*; + +2> else: + +3> store the received *ltm-ReferenceConfiguration* in *VarLTM-Config*; + +1> else (the received *LTM-Config* includes *ltm-ReferenceConfiguration* set to *release*): + +2> remove *ltm-ReferenceConfiguration* in *VarLTM-Config*; + +- 1> if the received *LTM-Config* includes *Itm-ServingCellNoResetID*: + - 2> if the current *VarLTM-ServingCellNoResetID* includes an *Itm-ServingCellNoResetID*: + - 3> replace the *Itm-ServingCellNoResetID* value within *VarLTM-ServingCellNoResetID* with the received *Itm-ServingCellNoResetID*; + - 2> else: + - 3> store the received *Itm-ServingCellNoResetID* in *VarLTM-ServingCellNoResetID*; +- 1> if the received *LTM-Config* includes *Itm-ServingCellUE-MeasuredTA-ID*: + - 2> if the current *VarLTM-ServingCellUE-MeasuredTA-ID* includes an *Itm-ServingCellUE-MeasuredTA-ID*: + - 3> replace the *Itm-ServingCellUE-MeasuredTA-ID* value within *VarLTM-ServingCellUE-MeasuredTA-ID* with the received *Itm-ServingCellUE-MeasuredTA-ID*; + - 2> else: + - 3> store the received *Itm-ServingCellUE-MeasuredTA-ID* in *VarLTM-ServingCellUE-MeasuredTA-ID*; +- 1> if the received *LTM-Config* includes *Itm-CSI-ResourceConfigToReleaseList*: + - 2> perform the LTM CSI resource configuration release as specified in 5.3.5.18.4; +- 1> if the received *LTM-Config* includes *Itm-CSI-ResourceConfigToAddModList*: + - 2> perform the LTM CSI resource configuration addition or modification as specified in 5.3.5.18.5; +- 1> if the received *LTM-Config* includes the *Itm-CandidateToReleaseList*: + - 2> perform the LTM candidate configuration release as specified in 5.3.5.18.2; +- 1> if the received *LTM-Config* includes the *Itm-CandidateToAddModList*: + - 2> perform the LTM candidate configuration addition or modification as specified in 5.3.5.18.3. + +##### 5.3.5.18.2 LTM candidate configuration release + +The UE shall: + +- 1> for each *Itm-CandidateId* value included in the *Itm-CandidateToReleaseList* for which there is an entry in *Itm-CandidateList* in *VarLTM-Config*: + - 2> remove the entry related to *LTM-Candidate* from *VarLTM-Config*. + +##### 5.3.5.18.3 LTM candidate configuration addition/modification + +The UE shall: + +- 1> for each *ltm-CandidateId* value in the *ltm-CandidateToAddModList*: + - 2> if the current *VarLTM-Config* includes an *LTM-Candidate* with the *ltm-CandidateId* value: + - 3> replace the *LTM-Candidate* within *VarLTM-Config* in accordance with the received *LTM-Candidate*; + - 2> else: + - 3> add the received *LTM-Candidate* to *VarLTM-Config*; + - 2> if the received *LTM-Candidate* includes *ltm-DL-OrJointTCI-StateToReleaseList*: + - 3> for each *tcI-StateId* in the *ltm-DL-OrJointTCI-StateToReleaseList*: + - 4> if the current *VarLTM-Config* includes a *CandidateTCI-State* within an *LTM-Candidate* with the *ltm-CandidateId* value that is associated with the *tcI-StateId* value: + - 5> remove the entry related to *CandidateTCI-State* within the *LTM-Candidate* from *VarLTM-Config*. + - 2> if the received *LTM-Candidate* includes *ltm-DL-OrJointTCI-StateToAddModList*: + - 3> for each *tcI-StateId* in the *ltm-DL-OrJointTCI-StateToAddModList*: + - 4> if the current *VarLTM-Config* includes a *CandidateTCI-State* within an *LTM-Candidate* with the *ltm-CandidateId* value that is associated with the *tcI-StateId* value: + - 5> replace the entry related to *CandidateTCI-State* within the *LTM-Candidate* from *VarLTM-Config*. + - 4> else: + - 5> add the received *CandidateTCI-State* within *LTM-Candidate* to *VarLTM-Config*; + - 2> if the received *LTM-Candidate* includes *ltm-UL-TCI-StatesToReleaseList*: + - 3> for each *tcI-StateId* in the *ltm-UL-TCI-StatesToReleaseList*: + - 4> if the current *VarLTM-Config* includes an *CandidateTCI-UL-State* within an *LTM-Candidate* with the *ltm-CandidateId* value that is associated with the *tcI-StateId* value: + - 5> remove the entry related to *CandidateTCI-UL-State* within the *LTM-Candidate* from *VarLTM-Config*. + +- 2> if the received *LTM-Candidate* includes *ltm-UL-TCI-StatesToAddModList*: + - 3> for each *tci-StateId* in the *ltm-UL-TCI-StatesToAddModList*: + - 4> if the current *VarLTM-Config* includes an *CandidateTCI-UL-State* within an *LTM-Candidate* with the *ltm-CandidateId* value that is associated with the *tci-StateId* value: + - 5> replace the entry related to *CandidateTCI-UL-State* within the *LTM-Candidate* from *VarLTM-Config*. + - 4> else: + - 5> add the received *CandidateTCI-UL-State* within *LTM-Candidate* to *VarLTM-Config*. +- 2> if the received *LTM-Candidate* includes *ltm-nzp-CSI-RS-ResourceToReleaseList*: + - 3> for each *nzp-CSI-RS-ResourceId* in the *ltm-nzp-CSI-RS-ResourceToReleaseList*: + - 4> if the current *VarLTM-Config* includes an *NZP-CSI-RS-Resource* within an *LTM-Candidate* with the *ltm-CandidateId* value that is associated with the *nzp-CSI-RS-ResourceId* value: + - 5> remove the entry related to *NZP-CSI-RS-Resource* within the *LTM-Candidate* from *VarLTM-Config*. +- 2> if the received *LTM-Candidate* includes *ltm-nzp-CSI-RS-ResourceToAddModList*: + - 3> for each *nzp-CSI-RS-ResourceId* in the *ltm-nzp-CSI-RS-ResourceToReleaseList*: + - 4> if the current *VarLTM-Config* includes an *NZP-CSI-RS-Resource* within an *LTM-Candidate* with the *ltm-CandidateId* value that is associated with the *nzp-CSI-RS-ResourceId* value: + - 5> replace the entry related to *NZP-CSI-RS-Resource* within the *LTM-Candidate* from *VarLTM-Config*. + - 4> else: + - 5> add the received *NZP-CSI-RS-Resource* within *LTM-Candidate* to *VarLTM-Config*. +- 2> if the received *LTM-Candidate* includes *ltm-nzp-CSI-RS-ResourceSetToReleaseList*: + - 3> for each *nzp-CSI-RS-ResourceSetId* in the *ltm-nzp-CSI-RS-ResourceSetToReleaseList*: + - 4> if the current *VarLTM-Config* includes an *NZP-CSI-RS-ResourceSet* within an *LTM-Candidate* with the *ltm-CandidateId* value that is associated with the *nzp-CSI-RS-ResourceSetId* value: + - 5> remove the entry related to *NZP-CSI-RS-ResourceSet* within the *LTM-Candidate* from *VarLTM-Config*. + +- 2> if the received *LTM-Candidate* includes *ltm-nzp-CSI-RS-ResourceSetToAddModList*: + - 3> for each *nzp-CSI-RS-ResourceSetId* in the *ltm-nzp-CSI-RS-ResourceSetToReleaseList*: + - 4> if the current *VarLTM-Config* includes an *NZP-CSI-RS-ResourceSet* within an *LTM-Candidate* with the *ltm-CandidateId* value that is associated with the *nzp-CSI-RS-ResourceSetId* value: + - 5> replace the entry related to *NZP-CSI-RS-ResourceSet* within the *LTM-Candidate* from *VarLTM-Config*. + - 4> else: + - 5> add the received *NZP-CSI-RS-ResourceSet* within *LTM-Candidate* to *VarLTM-Config*. +- 2> if the received *LTM-Candidate* includes *pathlossReferenceRS-ToReleaseList*: + - 3> for each *pathlossReferenceRS-Id* in the *pathlossReferenceRS-ToReleaseList*: + - 4> if the current *VarLTM-Config* includes an *PathlossReferenceRS* within an *LTM-Candidate* with the *ltm-CandidateId* value that is associated with the *pathlossReferenceRS-Id* value: + - 5> remove the entry related to *PathlossReferenceRS* within the *LTM-Candidate* from *VarLTM-Config*. +- 2> if the received *LTM-Candidate* includes *pathlossReferenceRS-ToAddModList*: + - 3> for each *pathlossReferenceRS-Id* in the *pathlossReferenceRS-ToAddModList*: + - 4> if the current *VarLTM-Config* includes an *PathlossReferenceRS* within an *LTM-Candidate* with the *ltm-CandidateId* value that is associated with the *pathlossReferenceRS-Id* value: + - 5> replace the entry related to *PathlossReferenceRS* within the *LTM-Candidate* from *VarLTM-Config*. + - 4> else: + - 5> add the received *PathlossReferenceRS* within *LTM-Candidate* to *VarLTM-Config*. +- 2> if the *LTM-Candidate* with the received *ltm-CandidateId* value includes *ltm-UE-MeasuredTA-ID*: + - 3> if the value of *ltm-UE-MeasuredTA-ID* is equal to the value of *ltm-ServingCellUE-MeasuredTA-ID* within *VarLTM-ServingCellUE-MeasuredTA-ID*: + - 4> inform lower layers that UE is configured with UE-based TA measurements if an LTM cell switch is executed for this LTM candidate configuration; + +##### 5.3.5.18.4 LTM CSI resource configuration release + +The UE shall: + +1> for each *ltm-CSI-ResourceConfigId* value included in the *ltm-CSI-ResourceConfigToReleaseList* for which there is an entry in *ltm-CSI-ResourceConfigList* in *VarLTM-Config*: + +2> remove the entry related to the *LTM-CSI-ResourceConfig* from *VarLTM-Config*. + +##### 5.3.5.18.5 LTM CSI resource configuration addition/modification + +The UE shall: + +1> for each *ltm-CSI-ResourceConfigId* value in the *ltm-CSI-ResourceConfigToAddModList*: + +2> if the current *VarLTM-Config* includes an *LTM-CSI-ResourceConfig* with the *ltm-CSI-ResourceConfigId* value: + +3> replace the *LTM-CSI-ResourceConfig* within *VarLTM-Config* in accordance with the received *LTM-CSI-ResourceConfig*; + +2> else: + +3> add the received *LTM-CSI-ResourceConfig* to *VarLTM-Config*. + +##### 5.3.5.18.6 LTM cell switch execution + +Upon the indication by lower layers that an LTM cell switch procedure is triggered, or upon performing LTM cell switch following cell selection performed while timer T311 was running, as specified in 5.3.7.3, the UE shall: + +1> release/clear all current dedicated radio configuration associated with the cell group for which the LTM cell switch procedure is triggered except for the following: + +- the *logicalChannelIdentity* and *logicalChannelIdentityExt* of RLC bearers configured in *RLC-BearerConfig* and the associated RLC entities, their state variables, buffers, and timers; +- the UE variables *VarLTM-Config*, *VarLTM-ServingCellNoResetID*, and *VarLTM-ServingCellUE-MeasuredTA-ID*. + +2> if the LTM cell switch is triggered on the MCG: + +- the MCG C-RNTI; +- the AS security configurations associated with the master key; +- for each SRB/DRB in current UE configuration which is using the master key: + - keep the associated PDCP and SDAP entities, their state variables, buffers and timers; + - release all fields related to the SRB/DRB configuration except for *srb-Identity* and *drb-Identity*; + +2> else, if the LTM cell switch is triggered on the SCG: + +- the AS security configurations associated with the secondary key; +- for each SRB/DRB in current UE configuration which is using the secondary key: + - keep the associated PDCP and SDAP entities, their state variables, buffers and timers; + - release all fields related to the SRB/DRB configuration except for *srb-Identity* and *drb-Identity*; + +1> release/clear all current common radio configuration associated with the cell group for which the LTM cell switch procedure is triggered; + +1> use the default values specified in 9.2.3 for timers T310, T311 and constants N310, N311 associate to cell group for which the LTM cell switch procedure is triggered; + +1> if the value of field *ltm-NoResetID* contained within the *LTM-Candidate IE* in *VarLTM-Config* indicated by lower layers or for the selected cell in accordance with 5.3.7.3 is not equal to the value of *ltm-ServingCellNoResetID* within *VarLTM-ServingCellNoResetID*: + +2> for each *logicalChannelId* and *logicalChannelIdExt* that is part of the current UE configuration for the cell group for which the LTM cell switch procedure is triggered: + +3> after the end of this procedure, re-establish the corresponding RLC entity as specified in TS 38.322 [4], after applying the LTM configuration in *ltm-CandidateConfig* within *LTM-Candidate IE* in *VarLTM-Config*; + +2> for each *drb-Identity* value that is part of the current UE configuration: + +3> if this DRB is an AM DRB: + +4> after the end of this procedure, trigger the PDCP entity of this DRB to perform data recovery as specified in TS 38.323 [5], after applying the LTM configuration in *ltm-CandidateConfig* within *LTM-Candidate IE* in *VarLTM-Config*; + +2> replace the value of *ltm-ServingCellNoResetID* in *VarLTM-ServingCellNoResetID* with the value of *ltm-NoResetID* in the *LTM-Candidate* in *VarLTM-Config* indicated by lower layers or for the selected cell in accordance with 5.3.7.3; 1> if the *LTM-Candidate IE* in *VarLTM-Config* indicated by lower layers or for the selected cell in accordance with 5.3.7.3 contains the field *ltm-UE-MeasuredTA-ID*: + +2> replace the value of *ltm-ServingCellUE-MeasuredTA-ID* in *VarLTM-ServingCellUE-MeasuredTA-ID* with the value received within *ltm-UE-MeasuredTA-ID*; + +1> if *ltm-ConfigComplete* is not included within the *LTM-Candidate IE* in *VarLTM-Config* indicated by lower layers or for the selected cell in accordance with 5.3.7.3: + +2> consider *ltm-ReferenceConfiguration* in *VarLTM-Config*, associated with the cell group for which the LTM cell switch procedure is triggered, to be the current UE configuration for the fields and configurations which have been released and to be released by the actions above in this procedure; + +NOTE 1: When the UE considers the reference configuration to be the current UE configuration, the UE should store fields and configurations that are part of the reference configuration but should not execute any actions or procedures triggered by the reception of an *RRCREconfiguration* message which are described in clause 5.3.5.3. + +1> if the LTM cell switch is triggered by an indication from lower layers: + +2> apply the *RRReconfiguration* message in *ltm-CandidateConfig* within *LTM-Candidate IE* in *VarLTM-Config* identified by the LTM candidate configuration identity received from lower layers according to clause 5.3.5.3; + +1> else (LTM cell switch triggered upon cell selection performed while timer T311 was running): + +2> apply the *RRReconfiguration* message in *ltm-CandidateConfig* within *LTM-Candidate IE* in *VarLTM-Config* related to the LTM candidate configuration identity for the selected cell (i.e., in accordance with 5.3.7.3) according to clause 5.3.5.3; + +1> release the radio bearer(s) and the logical channel(s) that are part of the current UE configuration but not part of the LTM candidate configuration either indicated by lower layers or for the selected cell in accordance with 5.3.7.3, or the LTM reference configuration (in case the LTM candidate configuration does not include *ltm-ConfigComplete*). + +NOTE 2: When *ltm-ConfigComplete* is not included for an LTM candidate configuration, before an LTM cell switch is triggered a UE implementation may generate and store an RRC reconfiguration message by applying the received LTM candidate configuration on top of the LTM reference configuration, and the stored RRC reconfiguration message is applied when the LTM cell switch is triggered. + +##### 5.3.5.18.7 LTM configuration release + +For the cell group for which the LTM configuration release procedure is triggered, the UE shall: + +1> remove all entries within *VarLTM-ServingCellNoResetID*; + +1> remove the entry within *VarLTM-ServingCellUE-MeasuredTA-ID*; + +1> release from current UE configuration all entries of *ltm-CSI-ReportConfigToAddModList*. + +1> release *ltm-Config*; + +#### 5.3.5.19 T348 expiry + +The UE can apply the temporary UE capability restriction in accordance with the one indicated in the last transmission of the *UEAssistanceInformation* message including *musim-CapRestriction*, as specified in 5.7.4.3. + +### 5.3.6 Counter check + +#### 5.3.6.1 General + +![Sequence diagram of the Counter check procedure between UE and Network.](759c7d62402f0b4651ddce292be5bdef_img.jpg) + +``` +sequenceDiagram + participant UE + participant Network + Note left of UE: Counter check procedure + Network->>UE: CounterCheck + UE-->>Network: CounterCheckResponse +``` + +The diagram illustrates the interaction between a User Equipment (UE) and a Network for the Counter check procedure. It is a sequence diagram with two lifelines: UE and Network. The Network sends a *CounterCheck* message to the UE. The UE responds with a *CounterCheckResponse* message back to the Network. + +Sequence diagram of the Counter check procedure between UE and Network. + +Figure 5.3.6.1-1: Counter check procedure + +The counter check procedure is used by the network to request the UE to verify the amount of data sent/ received on each DRB. More specifically, the UE is requested to check if, for each DRB, the most significant bits of the COUNT match with the values indicated by the network. + +NOTE: The procedure enables the network to detect packet insertion by an intruder (a 'man in the middle'). + +#### 5.3.6.2 Initiation + +The network initiates the procedure by sending a *CounterCheck* message. + +NOTE: The network may initiate the procedure when any of the COUNT values reaches a specific value. + +#### 5.3.6.3 Reception of the *CounterCheck* message by the UE + +Upon receiving the *CounterCheck* message, the UE shall: + +- 1> for each DRB that is established: + - 2> if no COUNT exists for a given direction (uplink or downlink) because it is a uni-directional bearer configured only for the other direction: + - 3> assume the COUNT value to be 0 for the unused direction; + - 2> if the *drb-Identity* is not included in the *drb-CountMSB-InfoList*: + - 3> include the DRB in the *drb-CountInfoList* in the *CounterCheckResponse* message by including the *drb-Identity*, the *count-Uplink* and the *count-Downlink* set to the value of TX\_NEXT – 1 and RX\_NEXT – 1 (specified in TS 38.323 [5]), respectively; + +2> else if, for at least one direction, the most significant bits of the COUNT are different from the value indicated in the *drb-CountMSB-InfoList*: + +3> include the DRB in the *drb-CountInfoList* in the *CounterCheckResponse* message by including the *drb-Identity*, the *count-Uplink* and the *count-Downlink* set to the value of TX\_NEXT – 1 and RX\_NEXT – 1 (specified in TS 38.323 [5]), respectively; + +1> for each DRB that is included in the *drb-CountMSB-InfoList* in the *CounterCheck* message that is not established: + +2> include the DRB in the *drb-CountInfoList* in the *CounterCheckResponse* message by including the *drb-Identity*, the *count-Uplink* and the *count-Downlink* with the most significant bits set identical to the corresponding values in the *drb-CountMSB-InfoList* and the least significant bits set to zero; + +1> submit the *CounterCheckResponse* message to lower layers for transmission upon which the procedure ends. + +### 5.3.7 RRC connection re-establishment + +#### 5.3.7.1 General + +![Sequence diagram of RRC connection re-establishment between UE and Network.](84e5b251aa38db522f76f5cc3afcb853_img.jpg) + +``` +sequenceDiagram + participant UE + participant Network + Note left of UE: + UE->>Network: RRCReestablishmentRequest + Note right of Network: + Network-->>UE: RRCReestablishment + Note left of UE: + UE->>Network: RRCReestablishmentComplete + Note right of Network: +``` + +The diagram illustrates the RRC connection re-establishment procedure between a User Equipment (UE) and a Network. It consists of three message exchanges: 1. The UE sends an *RRCReestablishmentRequest* to the Network. 2. The Network responds with an *RRCReestablishment* message. 3. The UE completes the procedure with an *RRCReestablishmentComplete* message. Vertical lifelines for the UE and Network are shown, with horizontal arrows representing the messages between them. + +Sequence diagram of RRC connection re-establishment between UE and Network. + +Figure 5.3.7.1-1: RRC connection re-establishment, successful + +![Sequence diagram showing RRC re-establishment, fallback to RRC establishment, successful. The diagram shows three messages between a UE and a Network: RRCReestablishmentRequest from UE to Network, RRCSetup from Network to UE, and RRCSetupComplete from UE to Network.](dd5771673aececa53d42ece89218299d_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Network + Note left of UE: + UE->>Network: RRCReestablishmentRequest + Note right of Network: + Network->>UE: RRCSetup + Note left of UE: + UE->>Network: RRCSetupComplete + +``` + +Sequence diagram showing RRC re-establishment, fallback to RRC establishment, successful. The diagram shows three messages between a UE and a Network: RRCReestablishmentRequest from UE to Network, RRCSetup from Network to UE, and RRCSetupComplete from UE to Network. + +**Figure 5.3.7.1-2: RRC re-establishment, fallback to RRC establishment, successful** + +The purpose of this procedure is to re-establish the RRC connection. A UE in RRC\_CONNECTED, for which AS security has been activated with SRB2 and at least one DRB/multicast MRB setup or, for IAB and NCR, SRB2, may initiate the procedure in order to continue the RRC connection. The connection re-establishment succeeds if the network is able to find and verify a valid UE context or, if the UE context cannot be retrieved, and the network responds with an *RRCSetup* according to clause 5.3.3.4. + +The network applies the procedure e.g as follows: + +- When AS security has been activated and the network retrieves or verifies the UE context: + - to re-activate AS security without changing algorithms; + - to re-establish and resume the SRB1; +- When UE is re-establishing an RRC connection, and the network is not able to retrieve or verify the UE context: + - to discard the stored AS Context and release all RBs and BH RLC channels and Uu Relay RLC channels; + - to fallback to establish a new RRC connection. + +If AS security has not been activated, the UE shall not initiate the procedure but instead moves to RRC\_IDLE directly, with release cause 'other'. If AS security has been activated, but SRB2 and at least one DRB or multicast MRB or, for IAB and NCR, SRB2, are not setup, the UE does not initiate the procedure but instead moves to RRC\_IDLE directly, with release cause 'RRC connection failure'. + +#### 5.3.7.2 Initiation + +The UE initiates the procedure when one of the following conditions is met: + +- 1> upon detecting radio link failure of the MCG and *t316* is not configured, in accordance with 5.3.10; or +- 1> upon detecting radio link failure of the MCG while SCG transmission is suspended, in accordance with 5.3.10; or + +- 1> upon detecting radio link failure of the MCG while PSCell change or PSCell addition is ongoing, in accordance with 5.3.10; or +- 1> upon detecting radio link failure of the MCG while the SCG is deactivated, in accordance with 5.3.10; or +- 1> upon re-configuration with sync failure of the MCG, in accordance with clause 5.3.5.8.3; or +- 1> upon mobility from NR failure, in accordance with clause 5.4.3.5; or +- 1> upon integrity check failure indication from lower layers concerning SRB1 or SRB2, except if the integrity check failure is detected on the *RRCReestablishment* message; or +- 1> upon an RRC connection reconfiguration failure, in accordance with clause 5.3.5.8.2; or +- 1> upon detecting radio link failure for the SCG while MCG transmission is suspended, in accordance with clause 5.3.10.3 in NR-DC or in accordance with TS 36.331 [10] clause 5.3.11.3 in NE-DC; or +- 1> upon reconfiguration with sync failure of the SCG while MCG transmission is suspended in accordance with clause 5.3.5.8.3; or +- 1> upon SCG change failure while MCG transmission is suspended in accordance with TS 36.331 [10] clause 5.3.5.7a; or +- 1> upon SCG configuration failure while MCG transmission is suspended in accordance with clause 5.3.5.8.2 in NR-DC or in accordance with TS 36.331 [10] clause 5.3.5.5 in NE-DC; or +- 1> upon integrity check failure indication from SCG lower layers concerning SRB3 while MCG is suspended; or +- 1> upon T316 expiry, in accordance with clause 5.7.3b.5; or +- 1> upon detecting sidelink radio link failure by L2 U2N Remote UE in RRC\_CONNECTED which is not configured with MP, in accordance with clause 5.8.9.3; or +- 1> upon reception of *NotificationMessageSidelink* including *indicationType* by L2 U2N Remote UE in RRC\_CONNECTED which is not configured with MP, in accordance with clause 5.8.9.10; or +- 1> upon PC5 unicast link release for the serving L2 U2N Relay UE indicated by upper layer at L2 U2N Remote UE in RRC\_CONNECTED which is not configured with MP while T301 is not running; or +- 1> if MP is configured, upon detecting radio link failure of the MCG (i.e. direct path) in accordance with clause 5.3.10 while the transmission of indirect path is suspended as specified in 5.3.5.17; or +- 1> if MP is configured, upon detecting sidelink radio link failure of SL indirect path by L2 U2N Remote UE, in accordance with clause 5.8.9.3, while MCG transmission (i.e. direct path) is suspended as specified in clause 5.7.3b; or +- 1> if MP is configured, upon reception of *NotificationMessageSidelink* including *indicationType* in accordance with clause 5.8.9.10, while MCG transmission (i.e. direct path) is suspended as specified in clause 5.7.3b; or + +- 1> if MP is configured, upon PC5 unicast link release indicated by upper layer at L2 U2N Remote UE, while MCG transmission (i.e. direct path) is suspended as specified in clause 5.7.3b; or +- 1> if MP is configured, upon detecting the failure of N3C indirect path by N3C remote UE in accordance with clause 5.7.3c, while MCG transmission (i.e. direct path) is suspended. + +NOTE 0: It is up to UE implementation whether to initiate the procedure while T346g is running. + +Upon initiation of the procedure, the UE shall: + +- 1> stop timer T310, if running; +- 1> stop timer T312, if running; +- 1> stop timer T304, if running; +- 1> start timer T311; +- 1> stop timer T316, if running; +- 1> if UE is not configured with *attemptCondReconfig*; and +- 1> if UE is not configured with *attemptLTM-Switch*: + - 2> reset MAC; + - 2> release *spCellConfig*, if configured; + - 2> suspend all RBs, and BH RLC channels for IAB-MT, and Uu Relay RLC channels for L2 U2N Relay UE, except SRB0 and broadcast MRBs; + - 2> release the MCG SCell(s), if configured; + - 2> if MR-DC is configured: + - 3> perform MR-DC release, as specified in clause 5.3.5.10; + - 2> perform the LTM configuration release procedure for the MCG and the SCG as specified in clause 5.3.5.18.7; + - 2> release *delayBudgetReportingConfig*, if configured and stop timer T342, if running; + - 2> release *overheatingAssistanceConfig*, if configured and stop timer T345, if running; + - 2> release *idc-AssistanceConfig*, if configured; + +2> release *btNameList*, if configured; +2> release *wlanNameList*, if configured; +2> release *sensorNameList*, if configured; +2> release *drx-PreferenceConfig* for the MCG, if configured and stop timer T346a associated with the MCG, if running; +2> release *maxBW-PreferenceConfig* for the MCG, if configured and stop timer T346b associated with the MCG, if running; +2> release *maxCC-PreferenceConfig* for the MCG, if configured and stop timer T346c associated with the MCG, if running; +2> release *maxMIMO-LayerPreferenceConfig* for the MCG, if configured and stop timer T346d associated with the MCG, if running; +2> release *minSchedulingOffsetPreferenceConfig* for the MCG, if configured stop timer T346e associated with the MCG, if running; +2> release *rlm-RelaxationReportingConfig* for the MCG, if configured and stop timer T346j associated with the MCG, if running; +2> release *bfd-RelaxationReportingConfig* for the MCG, if configured and stop timer T346k associated with the MCG, if running; +2> release *releasePreferenceConfig*, if configured stop timer T346f, if running; +2> release *onDemandSIB-Request* if configured, and stop timer T350, if running; +2> release *referenceTimePreferenceReporting*, if configured; +2> release *sl-AssistanceConfigNR*, if configured; +2> release *obtainCommonLocation*, if configured; +2> release *musim-GapAssistanceConfig*, if configured and stop timer T346h, if running; +2> release *musim-GapPriorityAssistanceConfig*, if configured; +2> release *musim-LeaveAssistanceConfig*, if configured; +2> release *musim-CapabilityRestrictionConfig*, if configured and stop timer T346n, if running; +2> release *ul-GapFR2-PreferenceConfig*, if configured; +2> release *scg-DeactivationPreferenceConfig*, if configured, and stop timer T346i, if running; +2> release *propDelayDiffReportConfig*, if configured; +2> release *rrm-MeasRelaxationReportingConfig*, if configured; + +- 2> release *maxBW-PreferenceConfigFR2-2*, if configured; +- 2> release *maxMIMO-LayerPreferenceConfigFR2-2*, if configured; +- 2> release *minSchedulingOffsetPreferenceConfigExt*, if configured; +- 2> release *multiRx-PreferenceReportingConfigFR2*, if configured, and stop timer T440, if running; +- 2> release *uav-FlightPathAvailabilityConfig*, if configured; +- 2> release *ul-TrafficInfoReportingConfig*, if configured, and stop all instances of timer T346x, if running; +- 1> release *successHO-Config*, if configured; +- 1> release *successPSCell-Config* configured by the PCell, if configured; +- 1> release *successPSCell-Config* configured by the PSCell, if configured; +- 1> if any DAPS bearer is configured: + - 2> reset the source MAC and release the source MAC configuration; + - 2> for each DAPS bearer: + - 3> release the RLC entity or entities as specified in TS 38.322 [4], clause 5.1.3, and the associated logical channel for the source SpCell; + - 3> reconfigure the PDCP entity to release DAPS as specified in TS 38.323 [5]; + - 2> for each SRB: + - 3> release the PDCP entity for the source SpCell; + - 3> release the RLC entity as specified in TS 38.322 [4], clause 5.1.3, and the associated logical channel for the source SpCell; + - 2> release the physical channel configuration for the source SpCell; + - 2> discard the keys used in the source SpCell (the $K_{gNB}$ key, the $K_{RRCEnc}$ key, the $K_{RRInt}$ key, the $K_{UPint}$ key and the $K_{UPenc}$ key), if any; +- 1> release *sl-L2RelayUE-Config*, if configured; +- 1> release *sl-L2RemoteUE-Config*, if configured; +- 1> release the SRAP entity, if configured; + +- 1> release *NCR-FwdConfig*, if configured; + - 1> if the UE is NCR-MT: + - 2> indicate to NCR-Fwd to cease forwarding; + - 1> if SL indirect path is configured: + - 2> release cell identity and relay UE ID configured in *sl-IndirectPathAddChange*; + - 2> indicate upper layers to trigger PC5 unicast link release of the SL indirect path; + - 1> if N3C indirect path is configured: + - 2> release *n3c-IndirectPathAddChange*; + - 2> consider the non-3GPP connection is not used; + - 1> if the UE is acting as a N3C relay UE: + - 2> release *n3c-IndirectPathConfigRelay*; + - 2> consider the non-3GPP connection is not used; + - 1> if the UE is acting as L2 U2N Remote UE and MP via L2 U2N Relay UE is not configured: + - 2> if the PC5-RRC connection with the U2N Relay UE is determined to be released: + - 3> indicate upper layers to trigger PC5 unicast link release; + - 3> perform either cell selection in accordance with the cell selection process as specified in TS 38.304 [20], or relay selection as specified in clause 5.8.15.3, or both; + - 2> else (i.e., maintain the PC5 RRC connection): + - 3> consider the connected L2 U2N Relay UE as suitable and perform actions as specified in clause 5.3.7.3a; +- NOTE 1: It is up to Remote UE implementation whether to release or keep the current PC5 unicast link. +- 1> else: + - 2> if the UE is capable of L2 U2N Remote UE: + - 3> perform either cell selection as specified in TS 38.304 [20], or relay selection as specified in clause 5.8.15.3, or both; + - 2> else: + +3> perform cell selection in accordance with the cell selection process as specified in TS 38.304 [20]. + +NOTE 2: For L2 U2N Remote UE, if both a suitable cell and a suitable relay are available, the UE can select either one based on its implementation. + +#### 5.3.7.3 Actions following cell selection while T311 is running + +Upon selecting a suitable NR cell, the UE shall: + +- 1> ensure having valid and up to date essential system information as specified in clause 5.2.2.2; +- 1> stop timer T311; +- 1> if T390 is running: + - 2> stop timer T390 for all access categories; + - 2> perform the actions as specified in 5.3.14.4; +- 1> stop the relay (re)selection procedure, if ongoing; +- 1> if the cell selection is triggered by detecting radio link failure of the MCG or re-configuration with sync failure of the MCG or mobility from NR failure, and +- 1> if *attemptCondReconfig* is configured; and +- 1> if the selected cell is not configured with *CondEventT1*, or the selected cell is configured with *CondEventT1* and leaving condition has not been fulfilled; and +- 1> if the selected cell is one of the candidate cells for which the *reconfigurationWithSync* is included in the *masterCellGroup* in the MCG *VarConditionalReconfig* and the *condExecutionCondPSCell* is not configured for the corresponding *condReconfigId* in the MCG *VarConditionalReconfig*: + - 2> if the UE supports RLF-Report for conditional handover, set the *choCellId* in the *VarRLF-Report* to the global cell identity, if available, otherwise to the physical cell identity and carrier frequency of the selected cell; + - 2> apply the stored *condRRReconfig* associated to the selected cell and perform actions as specified in 5.3.5.3; + +NOTE 1: It is left to network implementation to how to avoid keystream reuse in case of CHO based recovery after a failed handover without key change. + +- 1> if the cell selection is triggered by detecting radio link failure of the MCG or re-configuration with sync failure of the MCG or mobility from NR failure; and +- 1> if *attemptLTM-Switch* is configured; and +- 1> if the selected cell is one of the LTM candidate cells in the *LTM-Candidate* IE within *VarLTM-Config* associated with the MCG: + - 2> perform the LTM cell switch procedure for the selected LTM candidate cell according to the actions specified in 5.3.5.18.6; + +``` +1> else: +2> if UE is configured with attemptCondReconfig; or +2> if UE is configured with attemptLTM-Switch: +3> reset MAC; +3> release spCellConfig, if configured; +3> release the MCG SCell(s), if configured; +3> release delayBudgetReportingConfig, if configured and stop timer T342, if running; +3> release overheatingAssistanceConfig, if configured and stop timer T345, if running; +3> if MR-DC is configured: +4> perform MR-DC release, as specified in clause 5.3.5.10; +3> release idc-AssistanceConfig, if configured; +3> release btNameList, if configured; +3> release wlanNameList, if configured; +3> release sensorNameList, if configured; +3> release drx-PreferenceConfig for the MCG, if configured and stop timer T346a associated with the MCG, if running; +3> release maxBW-PreferenceConfig for the MCG, if configured and stop timer T346b associated with the MCG, if running; +3> release maxCC-PreferenceConfig for the MCG, if configured and stop timer T346c associated with the MCG, if running; +3> release maxMIMO-LayerPreferenceConfig for the MCG, if configured and stop timer T346d associated with the MCG, if running; +3> release minSchedulingOffsetPreferenceConfig for the MCG, if configured and stop timer T346e associated with the MCG, if running; +3> release rlm-RelaxationReportingConfig for the MCG, if configured and stop timer T346j associated with the MCG, if running; +3> release bfd-RelaxationReportingConfig for the MCG, if configured and stop timer T346k associated with the MCG, if running; +3> release releasePreferenceConfig, if configured and stop timer T346f, if running; +3> release onDemandSIB-Request if configured, and stop timer T350, if running; +``` + +- 3> release referenceTimePreferenceReporting, if configured; +- 3> release *sl-AssistanceConfigNR*, if configured; +- 3> release *obtainCommonLocation*, if configured; +- 3> release *scg-DeactivationPreferenceConfig*, if configured, and stop timer T346i, if running; +- 3> release *musim-GapAssistanceConfig*, if configured and stop timer T346h, if running; +- 3> release *musim-GapPriorityAssistanceConfig*, if configured; +- 3> release *musim-LeaveAssistanceConfig*, if configured; +- 3> release *musim-CapabilityRestrictionConfig*, if configured and stop timer T346n, if running; +- 3> release *propDelayDiffReportConfig*, if configured; +- 3> release *ul-GapFR2-PreferenceConfig*, if configured; +- 3> release *rrm-MeasRelaxationReportingConfig*, if configured; +- 3> release *maxBW-PreferenceConfigFR2-2*, if configured; +- 3> release *maxMIMO-LayerPreferenceConfigFR2-2*, if configured; +- 3> release *minSchedulingOffsetPreferenceConfigExt*, if configured; +- 3> release *uav-FlightPathAvailabilityConfig*, if configured; +- 3> release *ul-TrafficInfoReportingConfig*, if configured, and stop all instances of timer T346x, if running; +- 3> suspend all RBs, and BH RLC channels for the IAB-MT, except SRB0 and broadcast MRBs; + +- 2> remove all the entries within the MCG *VarConditionalReconfig*, if any; +- 2> perform the LTM configuration release procedure for the MCG and the SCG as specified in clause 5.3.5.18.7; +- 2> for each *measId*, if the associated *reportConfig* has a *reportType* set to *condTriggerConfig*: + - 3> for the associated *reportConfigId*: + - 4> remove the entry with the matching *reportConfigId* from the *reportConfigList* within the *VarMeasConfig*; + +3> if the associated *measObjectId* is only associated to a *reportConfig* with *reportType* set to *condTriggerConfig*: + +4> remove the entry with the matching *measObjectId* from the *measObjectList* within the *VarMeasConfig*; + +3> remove the entry with the matching *measId* from the *measIdList* within the *VarMeasConfig*; + +2> remove the *servingSecurityCellSetId* within the *VarServingSecurityCellSetID*, if any; + +2> release the PC5 RLC entity for SL-RLC0, if any; + +2> start timer T301; + +2> apply the default L1 parameter values as specified in corresponding physical layer specifications except for the parameters for which values are provided in *SIB1*; + +2> apply the default MAC Cell Group configuration as specified in 9.2.2; + +2> apply the CCCH configuration as specified in 9.1.1.2; + +2> apply the *timeAlignmentTimerCommon* included in *SIB1*; + +2> initiate transmission of the *RRCReestablishmentRequest* message in accordance with 5.3.7.4; + +NOTE 2: This procedure applies also if the UE returns to the source PCell. + +NOTE 3: A L2 U2N Relay UE may re-establish (e.g. via release and establish) the SL-RLC0 and SL-RLC1 of the connected L2 Remote UE(s). + +Upon selecting an inter-RAT cell, the UE shall: + +1> perform the actions upon going to RRC\_IDLE as specified in 5.3.11, with release cause 'RRC connection failure'. + +#### 5.3.7.3a Actions following relay selection while T311 is running + +Upon selecting a suitable L2 U2N Relay UE, the L2 U2N Remote UE shall: + +1> indicate to upper layer to trigger the PC5 unicast link establishment with the selected L2 U2N Relay UE, if a new L2 U2N Relay UE is selected; + +1> ensure having valid and up to date essential system information as specified in clause 5.2.2.2; + +1> stop timer T311; + +1> if T390 is running: + +2> stop timer T390 for all access categories; + +- 2> perform the actions as specified in 5.3.14.4; +- 1> stop the cell selection procedure, if ongoing; +- 1> start timer T301; +- 1> release the RLC entity for SRB0, if any; +- 1> establish a SRAP entity as specified in TS 38.351 [66], if no SRAP entity has been established; +- 1> apply the specified configuration of SL-RLC0 as specified in 9.1.1.4; +- 1> apply the SDAP configuration and PDCP configuration as specified in 9.1.1.2 for SRB0; +- 1> initiate transmission of the *RRCREestablishmentRequest* message in accordance with 5.3.7.4. + +#### 5.3.7.4 Actions related to transmission of *RRCREestablishmentRequest* message + +The UE shall set the contents of *RRCREestablishmentRequest* message as follows: + +- 1> if the procedure was initiated due to radio link failure as specified in 5.3.10.3 or reconfiguration with sync failure as specified in 5.3.5.8.3; or +- 1> if the procedure was initiated due to mobility from NR failure as specified in 5.4.3.5 and if *voiceFallbackIndication* is included in the *MobilityFromNRCommand* message: + - 2> set the *reestablishmentCellId* in the *VarRLF-Report* to the global cell identity of the selected cell; +- 1> set the *ue-Identity* as follows: + - 2> set the *c-RNTI* to the C-RNTI used in the source PCell (reconfiguration with sync or mobility from NR failure) or used in the PCell in which the trigger for the re-establishment occurred (other cases); + - 2> set the *physCellId* to the physical cell identity of the source PCell (reconfiguration with sync or mobility from NR failure) or of the PCell in which the trigger for the re-establishment occurred (other cases); + - 2> set the *shortMAC-I* to the 16 least significant bits of the MAC-I calculated: + - 3> over the ASN.1 encoded as per clause 8 (i.e., a multiple of 8 bits) *VarShortMAC-Input*; + - 3> with the $K_{RRCMac}$ key and integrity protection algorithm that was used in the source PCell (reconfiguration with sync or mobility from NR failure) or of the PCell in which the trigger for the re-establishment occurred (other cases); and + - 3> with all input bits for COUNT, BEARER and DIRECTION set to binary ones; +- 1> set the *reestablishmentCause* as follows: + +- 2> if the re-establishment procedure was initiated due to reconfiguration failure as specified in 5.3.5.8.2: + - 3> set the *reestablishmentCause* to the value *reconfigurationFailure*; +- 2> else if the re-establishment procedure was initiated due to reconfiguration with sync failure as specified in 5.3.5.8.3 (intra-NR handover failure) or 5.4.3.5 (inter-RAT mobility from NR failure): + - 3> set the *reestablishmentCause* to the value *handoverFailure*; +- 2> else: + - 3> set the *reestablishmentCause* to the value *otherFailure*; + +1> re-establish PDCP for SRB1; + +1> if the UE is acting as L2 U2N Remote UE: + +- 2> establish or re-establish (e.g. via release and add) SL RLC entity for SRB1; +- 2> apply the default configuration of SL-RLC1 as defined in 9.2.4 for SRB1; +- 2> apply the default configuration of PDCP as defined in 9.2.1 for SRB1; +- 2> apply the default configuration of SRAP as defined in 9.2.5 for SRB1; + +1> else: + +- 2> re-establish RLC for SRB1; +- 2> apply the default configuration defined in 9.2.1 for SRB1; + +1> configure lower layers to suspend integrity protection and ciphering for SRB1; + +NOTE: Ciphering is not applied for the subsequent *RRCREestablishment* message used to resume the connection. An integrity check is performed by lower layers, but merely upon request from RRC. + +1> resume SRB1; + +1> if *ta-Report* or *ta-ReportATG* is configured with value *enabled* and the UE supports TA reporting: + +- 2> indicate TA report initiation to lower layers; + +1> submit the *RRCREestablishmentRequest* message to lower layers for transmission. + +#### 5.3.7.5 Reception of the *RRCREestablishment* by the UE + +The UE shall: + +- 1> stop timer T301; +- 1> consider the current cell to be the PCell; +- 1> update the $K_{gNB}$ key based on the current $K_{gNB}$ key or the NH, using the received *nextHopChainingCount* value, as specified in TS 33.501 [11]; +- 1> store the *nextHopChainingCount* value indicated in the *RRCREestablishment* message; +- 1> derive the $K_{RRCEnc}$ and $K_{UPEnc}$ keys associated with the previously configured *cipheringAlgorithm*, as specified in TS 33.501 [11]; +- 1> derive the $K_{RRCInt}$ and $K_{UPInt}$ keys associated with the previously configured *integrityProtAlgorithm*, as specified in TS 33.501 [11]. +- 1> request lower layers to verify the integrity protection of the *RRCREestablishment* message, using the previously configured algorithm and the $K_{RRCInt}$ key; +- 1> if the integrity protection check of the *RRCREestablishment* message fails: + - 2> perform the actions upon going to RRC\_IDLE as specified in 5.3.11, with release cause 'RRC connection failure', upon which the procedure ends; +- 1> configure lower layers to resume integrity protection for SRB1 using the previously configured algorithm and the $K_{RRCInt}$ key immediately, i.e., integrity protection shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure; +- 1> configure lower layers to resume ciphering for SRB1 using the previously configured algorithm and, the $K_{RRCEnc}$ key immediately, i.e., ciphering shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure; +- 1> release the measurement gap configuration indicated by the *measGapConfig*, if configured; +- 1> release the MUSIM gap configuration indicated by the *musim-GapConfig*, if configured; +- 1> release the FR2 UL gap configuration indicated by the *ul-GapFR2-Config*, if configured; +- 1> perform the L2 U2N Remote UE configuration procedure in accordance with the received *sl-L2RemoteUE-Config* as specified in 5.3.5.16; +- 1> set the content of *RRCREestablishmentComplete* message as follows: + - 2> if the UE has logged measurements available for NR and if the RPLMN is included in *plmn-IdentityList* stored in *VarLogMeasReport*; or + - 2> if the UE has logged measurements available for NR and if the current registered SNPN are included in *snpn-ConfigIDList* stored in *VarLogMeasReport*: + - 3> include the *logMeasAvailable* in the *RRCREestablishmentComplete* message; + +- 3> if Bluetooth measurement results are included in the logged measurements the UE has available for NR: + - 4> include the *logMeasAvailableBT* in the *RRCReestablishmentComplete* message; +- 3> if WLAN measurement results are included in the logged measurements the UE has available for NR: + - 4> include the *logMeasAvailableWLAN* in the *RRCReestablishmentComplete* message; +- 2> if the *sigLoggedMeasType* in *VarLogMeasReport* is included; or +- 2> if the UE is capable of reporting availability of signalling based logged MDT for inter-RAT (i.e. LTE to NR), and if the *sigLoggedMeasType* in *VarLogMeasReport* of TS 36.331 [10] is included: + - 3> if T330 timer is running (associated to the logged measurement configuration for NR or for LTE): + - 4> set *sigLogMeasConfigAvailable* to *true* in the *RRCReestablishmentComplete* message; + - 3> else: + - 4> if the UE has logged measurements: + - 5> set *sigLogMeasConfigAvailable* to *false* in the *RRCReestablishmentComplete* message; +- 2> if the UE has connection establishment failure or connection resume failure information available in *VarConnEstFailReport* or *VarConnEstFailReportList* and if the RPLMN is equal to *plmn-Identity* stored in *VarConnEstFailReport* or in at least one of the entries of *VarConnEstFailReportList*; or +- 2> if the UE supports multiple CEF report and if the UE has connection establishment failure information or connection resume failure information available in *VarConnEstFailReport* or *VarConnEstFailReportList* and if the registered SNPN identity is equal to *snpn-identity* stored in *VarConnEstFailReport* or any entry of *VarConnEstFailReportList*: + - 3> include *connEstFailInfoAvailable* in the *RRCReestablishmentComplete* message; +- 2> if the UE has radio link failure or handover failure information available in *VarRLF-Report* and if the RPLMN is included in *plmn-IdentityList* stored in *VarRLF-Report*; or +- 2> if the UE has radio link failure or handover failure information available in *VarRLF-Report* of TS 36.331 [10] and if the UE is capable of cross-RAT RLF reporting and if the RPLMN is included in *plmn-IdentityList* stored in *VarRLF-Report* of TS 36.331 [10]; or +- 2> if the UE has radio link failure or handover failure information available in *VarRLF-Report* and if the current registered SNPN is included in *snpn-IdentityList* stored in *VarRLF-Report*: + - 3> include *rlf-InfoAvailable* in the *RRCReestablishmentComplete* message; + +- 2> if the UE has successful handover information available in *VarSuccessHO-Report* and if the RPLMN is included in *plmn-IdentityList* stored in *VarSuccessHO-Report*; or +- 2> if the UE has successful handover information available in *VarSuccessHO-Report* and if the current registered SNPN is included in *snpn-IdentityList* stored in the *VarSuccessHO-Report*: + - 3> include *successHO-InfoAvailable* in the *RRCReestablishmentComplete* message; +- 2> if the UE has successful PSCell change or addition information available in *VarSuccessPSCell-Report* and if the RPLMN is included in *plmn-IdentityList* stored in *VarSuccessPSCell-Report*; or +- 2> if the UE has successful PSCell change or addition information available in *VarSuccessPSCell-Report* and if the current registered SNPN is included in *snpn-IdentityList* stored in the *VarSuccessPSCell-Report*: + - 3> include *successPSCell-InfoAvailable* in the *RRCReestablishmentComplete* message; +- 2> if the UE has flight path information available: + - 3> if the UE had not previously provided a flight path information since last entering RRC\_CONNECTED state; or + - 3> if at least one waypoint was not previously provided; or + - 3> if at least one upcoming waypoint that was previously provided is being removed; or + - 3> if *flightPathUpdateDistanceThr* is configured and for at least one waypoint, the 3D distance between the previously provided location and the new location is more than or equal to the distance threshold configured by *flightPathUpdateDistanceThr*; or + - 3> if *flightPathUpdateTimeThr* is configured and for at least one waypoint, the timestamp was not previously provided but is now available, or the time between the previously provided timestamp and the new timestamp, if available, is more than or equal to the time threshold configured by *flightPathUpdateTimeThr*: + - 4> include *flightPathInfoAvailable*; + +NOTE: If neither *flightPathUpdateDistanceThr* nor *flightPathUpdateTimeThr* is configured, it is up to UE implementation whether to include *flightPathInfoAvailable* when updated flight path information is available. + +- 1> submit the *RRCReestablishmentComplete* message to lower layers for transmission; +- 1> if *SIB21* is provided by the PCell: + - 2> if the UE initiated transmission of an *MBSInterestIndication* message during the last 1 second preceding detection of radio link failure: + - 3> initiate transmission of an *MBSInterestIndication* message in accordance with 5.9.4; +- 1> the procedure ends. + +#### 5.3.7.6 T311 expiry + +Upon T311 expiry, the UE shall: + +- 1> if the procedure was initiated due to radio link failure or handover failure: + - 2> set the *noSuitableCellFound* in the *VarRLF-Report* to *true*; +- 1> perform the actions upon going to RRC\_IDLE as specified in 5.3.11, with release cause 'RRC connection failure'. + +#### 5.3.7.7 T301 expiry or selected cell/L2 U2N Relay UE no longer suitable + +The UE shall: + +- 1> if timer T301 expires; or +- 1> if the selected cell becomes no longer suitable according to the cell selection criteria as specified in TS 38.304 [20]; or +- 1> if the (re)selected L2 U2N Relay UE becomes unsuitable; or +- 1> upon reception of *NotificationMessageSidelink* indicating *relayUE-HO* or *relayUE-CellReselection*; or +- 1> upon PC5 unicast link release indicated by upper layer at L2 U2N Remote UE: + - 2> perform the actions upon going to RRC\_IDLE as specified in 5.3.11, with release cause 'RRC connection failure'. + +#### 5.3.7.8 Reception of the *RRCSsetup* by the UE + +The UE shall: + +- 1> perform the RRC connection establishment procedure as specified in 5.3.3.4. + +### 5.3.8 RRC connection release + +#### 5.3.8.1 General + +![Sequence diagram showing a successful RRC connection release. A UE sends an RRCRelease message to a Network.](b44f89b176c971c7dd264c07bfef2c2a_img.jpg) + +``` +sequenceDiagram + participant UE + participant Network + Note left of UE: + UE->>Network: RRCRelease + Note right of Network: + +``` + +Sequence diagram showing a successful RRC connection release. A UE sends an RRCRelease message to a Network. + +Figure 5.3.8.1-1: RRC connection release, successful + +The purpose of this procedure is: + +- to release the RRC connection, which includes the release of the established radio bearers (except for broadcast MRBs), BH RLC channels, Uu Relay RLC channels, PC5 Relay RLC channels as well as all radio resources; or +- to suspend the RRC connection only if SRB2 and at least one DRB or multicast MRB or, for IAB and NCR, SRB2, are setup, which includes the suspension of the established radio bearers (except for broadcast MRBs). + +#### 5.3.8.2 Initiation + +The network initiates the RRC connection release procedure to transit a UE in RRC\_CONNECTED to RRC\_IDLE; or to transit a UE in RRC\_CONNECTED to RRC\_INACTIVE only if SRB2 and at least one DRB or multicast MRB or, for IAB and NCR, SRB2, is setup in RRC\_CONNECTED; or to transit a UE in RRC\_INACTIVE back to RRC\_INACTIVE when the UE tries to resume (for resuming a suspended RRC connection or for initiating SDT); or to transit a UE in RRC\_INACTIVE to RRC\_IDLE when the UE tries to resume (for resuming of a suspended RRC connection or for initiating SDT). The procedure can also be used to release and redirect a UE to another frequency. + +#### 5.3.8.3 Reception of the *RRCRelease* by the UE + +The UE shall: + +- 1) delay the following actions defined in this clause 60 ms from the moment the *RRCRelease* message was received or optionally when lower layers indicate that the receipt of the *RRCRelease* message has been successfully acknowledged, whichever is earlier; + +NOTE 0: When the *RRCRelease* message is received on a HARQ process with disabled HARQ feedback, and when STATUS reporting, as defined in TS 38.322 [4], has not been triggered for a logical channel associated with the SRB1, the lower layers can be considered to have indicated that the receipt of the *RRCRelease* message has been successfully acknowledged. + +``` +1> stop timer T380, if running; +1> stop timer T320, if running; +1> if timer T316 is running; +2> stop timer T316; +2> if the UE supports RLF-Report for fast MCG recovery procedure: +3> set the elapsedTimeT316 in the VarRLF-Report to the value of the elapsed time of the timer T316; +3> set the pSCellId to the global cell identity of the PSCell, if available, otherwise to the physical cell identity and carrier frequency of the PSCell; +2> else: +3> clear the information included in VarRLF-Report, if any; +1> stop timer T350, if running; +1> stop timer T346g, if running; +1> if the AS security is not activated: +2> ignore any field included in RRRelease message except waitTime; +2> perform the actions upon going to RRC_IDLE as specified in 5.3.11 with the release cause 'other' upon which the procedure ends; +1> if the RRRelease message includes redirectedCarrierInfo indicating redirection to eutra: +2> if cnType is included: +3> after the cell selection, indicate the available CN Type(s) and the received cnType to upper layers; +NOTE 1: Handling the case if the E-UTRA cell selected after the redirection does not support the core network type specified by the cnType, is up to UE implementation. +2> if voiceFallbackIndication is included: +3> consider the RRC connection release was for EPS fallback for IMS voice (see TS 23.502 [43]); +1> if the RRRelease message includes the cellReselectionPriorities: +2> store the cell reselection priority information provided by the cellReselectionPriorities; +2> if the t320 is included: +``` + +3> start timer T320, with the timer value set according to the value of *t320*; + +1> else: + +2> apply the cell reselection priority information broadcast in the system information; + +1> if *deprioritisationReq* is included and the UE supports RRC connection release with deprioritisation: + +2> start or restart timer T325 with the timer value set to the *deprioritisationTimer* signalled; + +2> store the *deprioritisationReq* until T325 expiry; + +NOTE 1a: The UE stores the deprioritisation request irrespective of any cell reselection absolute priority assignments (by dedicated or common signalling) and regardless of RRC connections in NR or other RATs unless specified otherwise. + +1> if the *RRCRelease* includes the *measIdleConfig*: + +2> if T331 is running: + +3> stop timer T331; + +3> perform the actions as specified in 5.7.8.3; + +2> if the *measIdleConfig* is set to *setup*: + +3> store the received *measIdleDuration* in *VarMeasIdleConfig*; + +3> start timer T331 with the value set to *measIdleDuration*; + +3> if the *measIdleConfig* contains *measIdleCarrierListNR*: + +4> store the received *measIdleCarrierListNR* in *VarMeasIdleConfig*; + +3> if the *measIdleConfig* contains *measIdleCarrierListEUTRA*: + +4> store the received *measIdleCarrierListEUTRA* in *VarMeasIdleConfig*; + +3> if the *measIdleConfig* contains *validityAreaList*: + +4> store the received *validityAreaList* in *VarMeasIdleConfig*; + +1> if the *RRCRelease* includes *suspendConfig*: + +2> reset MAC and release the default MAC Cell Group configuration, if any; + +- 2> apply the received *suspendConfig* except the received *nextHopChainingCount*; +- 2> if the *sdt-Config* is configured: + - 3> for each of the DRB in the *sdt-DRB-List*: + - 4> consider the DRB to be configured for SDT; + - 3> if *sdt-SRB2-Indication* is configured: + - 4> consider the SRB2 to be configured for SDT; + - 3> for each RLC bearer (except those associated with broadcast MRBs) that is not suspended: + - 4> re-establish the RLC entity as specified in TS 38.322 [4]; + - 3> for SRB2 (if it is resumed) and for SRB1: + - 4> trigger the PDCP entity to perform SDU discard as specified in TS 38.323 [5]; + - 3> if *sdt-MAC-PHY-CG-Config* is configured: + - 4> configure the PCell with the configured grant resources for SDT and instruct the MAC entity to start the *cg-SDT-TimeAlignmentTimer*; +- 2> if *srs-PosRRC-Inactive* is configured: + - 3> apply the configuration and instruct MAC to start the *inactivePosSRS-TimeAlignmentTimer*; +- 2> if *srs-PosRRC-InactiveValidityAreaConfig* is configured: + - 3> apply the configuration and instruct MAC to start the *inactivePosSRS-ValidityAreaTAT*; + +NOTE 1b: The Network should provide full configuration to UE for SRS for Positioning in RRC\_INACTIVE. + +- 2> perform the LTM configuration release procedure for the MCG and the SCG as specified in clause 5.3.5.18.7; +- 2> remove all the entries within the MCG and the SCG *VarConditionalReconfig*, if any; +- 2> remove the *servingSecurityCellSetId* within the *VarServingSecurityCellSetID*, if any; +- 2> for each *measId* of the MCG *measConfig* and for each *measId* of the SCG *measConfig*, if configured, if the associated *reportConfig* has a *reportType* set to *condTriggerConfig*: + - 3> for the associated *reportConfigId*: + +- 4> remove the entry with the matching *reportConfigId* from the *reportConfigList* within the *VarMeasConfig*; + - 3> if the associated *measObjectId* is only associated to a *reportConfig* with *reportType* set to *condTriggerConfig*: + - 4> remove the entry with the matching *measObjectId* from the *measObjectList* within the *VarMeasConfig*; + - 3> remove the entry with the matching *measId* from the *measIdList* within the *VarMeasConfig*; +- 2> for NCR-MT, if *NCR-FwdConfig* is configured: + - 3> if the *NCR-FwdConfig* includes periodic forwarding resource configuration: + - 4> indicate to NCR-Fwd to continue forwarding only in accordance with the configured periodic forwarding resource set(s); + - 3> else: + - 4> indicate to NCR-Fwd to cease forwarding; +- 2> if the UE is acting as L2 U2N Remote UE and is not configured with MP: + - 3> if the PC5-RRC connection with the U2N Relay UE is determined to be released: + - 4> indicate upper layers to trigger PC5 unicast link release; + - 3> else (i.e., maintain the PC5 RRC connection): + - 4> establish or re-establish (e.g. via release and add) SL RLC entity for SRB1; +- 2> else: + - 3> re-establish RLC entities for SRB1; +- 2> if the *RRRelease* message with *suspendConfig* was received in response to an *RRResumeRequest* or an *RRResumeRequest1*: + - 3> stop the timer T319 if running; + - 3> in the stored UE Inactive AS context: + - 4> replace the $K_{gNB}$ and $K_{RRCint}$ keys with the current $K_{gNB}$ and $K_{RRCint}$ keys; + - 4> replace the *nextHopChainingCount* with the value of *nextHopChainingCount* received in the *RRRelease* message; + - 4> replace the *cellIdentity* with the *cellIdentity* of the cell the UE has received the *RRRelease* message; + - 4> if the *suspendConfig* contains the *sl-UEIdentityRemote* (i.e. the UE is a L2 U2N Remote UE): + +5> replace the C-RNTI with the value of the *sl-UEIdentityRemote*; + +5> replace the physical cell identity with the value of the *sl-PhysCellId* in *sl-ServingCellInfo* contained in the discovery message received from the connected L2 U2N Relay UE; + +4> else: + +5> replace the C-RNTI with the C-RNTI used in the cell (see TS 38.321 [3]) the UE has received the *RRCRelease* message; + +5> replace the physical cell identity with the physical cell identity of the cell the UE has received the *RRCRelease* message; + +3> replace the *nextHopChainingCount* with the value associated with the current $K_{gNB}$ ; + +3> stop the timer T319a if running and consider SDT procedure is not ongoing; + +2> else: + +3> store in the UE Inactive AS Context the *nextHopChainingCount* received in the *RRCRelease* message, the current $K_{gNB}$ and $K_{RRCint}$ keys, the ROHC state, the EHC context(s), the UDC state, the stored QoS flow to DRB mapping rules, the application layer measurement configuration, the C-RNTI used in the source PCell, the *cellIdentity* and the physical cell identity of the source PCell, the *NCR-FwdConfig* (if configured), the *spCellConfigCommon* within *ReconfigurationWithSync* of the NR PSCell (if configured) and all other parameters configured except for: + +- parameters within *ReconfigurationWithSync* of the PCell; +- parameters within *ReconfigurationWithSync* of the NR PSCell, if configured; +- parameters within *MobilityControlInfoSCG* of the E-UTRA PSCell, if configured; +- *servingCellConfigCommonSIB*; +- *sl-L2RelayUE-Config*, if configured; +- *sl-L2RemoteUE-Config*, if configured; +- *uav-Config*, if configured; + +NOTE 1c: *suspendConfig* is not stored as part of UE Inactive AS Context, except for the fields explicitly specified. + +3> store any previously or subsequently received application layer measurement report containers for which no segment, or full message, has been submitted to lower layers for transmission; + +3> for each application layer measurement configuration for which *configForRRC-IdleInactive* is set to *true*: + +4> initiate the procedure in 5.5b.1.2; + +NOTE 2: NR sidelink communication/discovery related configurations and logged measurement configuration are not stored as UE Inactive AS Context, when UE enters RRC\_INACTIVE. + +- 2> suspend all SRB(s) and DRB(s), except SRB0 and broadcast MRBs; +- 2> suspend all multicast MRB(s) associated with multicast session(s) not configured to receive in RRC\_INACTIVE; +- 2> indicate PDCP suspend to lower layers of all DRBs and multicast MRBs associated with multicast session(s) not configured to receive in RRC\_INACTIVE; +- 2> release Uu Relay RLC channel(s), if configured; +- 2> release PC5 Relay RLC channel(s), if configured; +- 2> release the SRAP entity, if configured; + +NOTE 2a: A L2 U2N Relay UE may re-establish the SL-RLC0, SL-RLC1 and SRAP entity after release. + +- 2> if SL indirect path is configured: + - 3> release cell identity and relay UE ID configured in *sl-IndirectPathAddChange*; + - 3> indicate upper layers to trigger PC5 unicast link release of the SL indirect path; +- 2> if N3C indirect path is configured: + - 3> release *n3c-IndirectPathAddChange*; + - 3> consider the non-3GPP connection is not used; +- 2> if the UE is acting as a N3C relay UE: + - 3> release *n3c-IndirectPathConfigRelay*; + - 3> consider the non-3GPP connection is not used; +- 2> if the *t380* is included: + - 3> start timer T380, with the timer value set to *t380*; +- 2> if the *RRRelease* message is including the *waitTime*: + - 3> start timer T302 with the value set to the *waitTime*; + - 3> inform upper layers that access barring is applicable for all access categories '0' and '2'; + +- 2> if T390 is running: + - 3> stop timer T390 for all access categories; + - 3> perform the actions as specified in 5.3.14.4; +- 2> indicate the suspension of the RRC connection to upper layers; +- 2> if the UE is capable of L2 U2N Remote UE: + - 3> enter RRC\_INACTIVE, and perform either cell selection as specified in TS 38.304 [20], or relay selection as specified in clause 5.8.15.3, or both; +- 2> else: + - 3> enter RRC\_INACTIVE and perform cell selection as specified in TS 38.304 [20]; +- 2> if the *suspendConfig* includes *resumeIndication*: + - 3> perform the actions as if the UE received *Paging* message with the *ue-Identity* included in the *PagingRecord* matching the UE's stored *fullI-RNTI*, as specified in clause 5.3.2.3; +- 2> if the *multicastConfigInactive* is configured: + - 3> if the multicast PTM configuration is provided for a multicast session for which the UE is not indicated to stop monitoring the G-RNTI and the UE selects the same cell as the one on which it received *RRCRelease*: + - 4> apply the multicast PTM configuration as specified in 5.10.3; + - 4> monitor the Multicast MCCH-RNTI as specified in 5.10.2; +- 1> else: + - 2> perform the actions upon going to RRC\_IDLE as specified in 5.3.11, with the release cause 'other'. + +NOTE 3: Whether to release the PC5 unicast link is left to L2 U2N Remote UE's implementation. + +NOTE 4: It is left to UE implementation whether to stop T430, if running, when going to RRC\_INACTIVE. + +#### 5.3.8.4 T320 expiry + +The UE shall: + +- 1> if T320 expires: + +- 2> if stored, discard the cell reselection priority information provided by the *cellReselectionPriorities* or inherited from another RAT; +- 2> apply the cell reselection priority information broadcast in the system information. + +#### 5.3.8.5 UE actions upon the expiry of *DataInactivityTimer* + +Upon receiving the expiry of *DataInactivityTimer* from lower layers while in RRC\_CONNECTED, the UE shall: + +- 1> perform the actions upon going to RRC\_IDLE as specified in 5.3.11, with release cause 'RRC connection failure'. + +#### 5.3.8.6 T346g expiry + +The UE shall: + +- 1> if T346g expires: +- 2> perform the actions upon going to RRC\_IDLE as specified in 5.3.11, with release cause 'other'. + +### 5.3.9 RRC connection release requested by upper layers + +#### 5.3.9.1 General + +The purpose of this procedure is to release the RRC connection. Access to the current PCell may be barred as a result of this procedure. + +#### 5.3.9.2 Initiation + +The UE initiates the procedure when upper layers request the release of the RRC connection as specified in TS 24.501 [23]. The UE shall not initiate the procedure for power saving purposes. + +The UE shall: + +- 1> if the upper layers indicate barring of the PCell: + - 2> treat the PCell used prior to entering RRC\_IDLE as barred according to TS 38.304 [20]; +- 1> perform the actions upon going to RRC\_IDLE as specified in 5.3.11, with release cause 'other'. + +### 5.3.10 Radio link failure related actions + +#### 5.3.10.1 Detection of physical layer problems in RRC\_CONNECTED + +The UE shall: + +- 1> if any DAPS bearer is configured, upon receiving N310 consecutive "out-of-sync" indications for the source SpCell from lower layers and T304 is running: + - 2> start timer T310 for the source SpCell. +- 1> upon receiving N310 consecutive "out-of-sync" indications for the SpCell from lower layers while neither T300, T301, T304, T311, T316 nor T319 are running: + - 2> start timer T310 for the corresponding SpCell. + +#### 5.3.10.2 Recovery of physical layer problems + +Upon receiving N311 consecutive "in-sync" indications for the SpCell from lower layers while T310 is running, the UE shall: + +- 1> stop timer T310 for the corresponding SpCell. +- 1> stop timer T312 for the corresponding SpCell, if running. + +NOTE 1: In this case, the UE maintains the RRC connection without explicit signalling, i.e. the UE maintains the entire radio resource configuration. + +NOTE 2: Periods in time where neither "in-sync" nor "out-of-sync" is reported by L1 do not affect the evaluation of the number of consecutive "in-sync" or "out-of-sync" indications. + +#### 5.3.10.3 Detection of radio link failure + +The UE shall: + +- 1> if any DAPS bearer is configured and T304 is running: + - 2> upon T310 expiry in source SpCell; or + - 2> upon random access problem indication from source MCG MAC; or + - 2> upon indication from source MCG RLC that the maximum number of retransmissions has been reached; or + - 2> upon consistent uplink LBT failure indication from source MCG MAC: + - 3> consider radio link failure to be detected for the source MCG i.e. source RLF; + - 3> suspend the transmission and reception of all DRBs and multicast MRBs in the source MCG; + - 3> reset MAC for the source MCG; + - 3> release the source connection. +- 1> else: + +- 2> during a DAPS handover: the following only applies for the target PCell; +- 2> upon T310 expiry in PCell; or +- 2> upon T312 expiry in PCell; or +- 2> upon random access problem indication from MCG MAC while neither T300, T301, T304, T311 nor T319 are running and SDT procedure is not ongoing; or +- 2> upon indication from MCG RLC that the maximum number of retransmissions has been reached while SDT procedure is not ongoing; or +- 2> if connected as an IAB-node, upon BH RLF indication received on BAP entity from the MCG; or +- 2> upon consistent uplink LBT failure indication from MCG MAC while T304 is not running: + - 3> if the indication is from MCG RLC and CA duplication is configured and activated for MCG, and for the corresponding logical channel *allowedServingCells* only includes SCell(s): + - 4> initiate the failure information procedure as specified in 5.7.5 to report RLC failure. + - 3> else: + - 4> consider radio link failure to be detected for the MCG, i.e. MCG RLF; + - 4> discard any segments of segmented RRC messages stored according to 5.7.6.3; + +NOTE: Void. + +- 4> if AS security has not been activated: + - 5> perform the actions upon going to RRC\_IDLE as specified in 5.3.11, with release cause 'other';- +- 4> else if AS security has been activated but SRB2 and at least one DRB or multicast MRB or, for IAB and NCR, SRB2, have not been setup: + - 5> store the radio link failure information in the *VarRLF-Report* as described in clause 5.3.10.5; + - 5> perform the actions upon going to RRC\_IDLE as specified in 5.3.11, with release cause 'RRC connection failure'; +- 4> else: + - 5> store the radio link failure information in the *VarRLF-Report* as described in clause 5.3.10.5; + - 5> if T316 is configured; and + - 5> if SCG transmission is not suspended; and + +- 5> if the SCG is not deactivated; and +- 5> if neither PSCell change nor PSCell addition is ongoing (i.e. timer T304 for the NR PSCell is not running in case of NR-DC or timer T307 of the E-UTRA PSCell is not running as specified in TS 36.331 [10], clause 5.3.10.10, in NE-DC): + - 6> initiate the MCG failure information procedure as specified in 5.7.3b to report MCG radio link failure. +- 5> else: + - 6> initiate the connection re-establishment procedure as specified in 5.3.7. + +A L2/L3 U2N Relay UE shall: + +- 1> upon detecting radio link failure: + - 2> either indicate to upper layers (to trigger PC5 unicast link release) or send *NotificationMessageSidelink* to the connected L2/L3 U2N Remote UE(s) in accordance with 5.8.9.10. + +The UE shall: + +- 1> upon T310 expiry in PSCell; or +- 1> upon T312 expiry in PSCell; or +- 1> upon random access problem indication from SCG MAC; or +- 1> upon indication from SCG RLC that the maximum number of retransmissions has been reached; or +- 1> if connected as an IAB-node, upon BH RLF indication received on BAP entity from the SCG; or +- 1> upon consistent uplink LBT failure indication from SCG MAC: + - 2> if the indication is from SCG RLC and CA duplication is configured and activated for SCG, and for the corresponding logical channel *allowedServingCells* only includes SCell(s): + - 3> initiate the failure information procedure as specified in 5.7.5 to report RLC failure. + - 2> else: + - 3> consider radio link failure to be detected for the SCG, i.e. SCG RLF; + - 3> if the SCG is deactivated: + - 4> stop radio link monitoring on the SCG; + +- 4> indicate to lower layers to stop beam failure detection on the PSCell; +- 3> if MCG transmission is not suspended: + - 4> initiate the SCG failure information procedure as specified in 5.7.3 to report SCG radio link failure. +- 3> else: + - 4> if the UE is in NR-DC: + - 5> initiate the connection re-establishment procedure as specified in 5.3.7; + - 4> else (the UE is in (NG)EN-DC): + - 5> initiate the connection re-establishment procedure as specified in TS 36.331 [10], clause 5.3.7; + +#### 5.3.10.4 RLF cause determination + +The UE shall set the *rlf-Cause* in the *VarRLF-Report* as follows: + +- 1> if the UE declares radio link failure due to T310 expiry: + - 2> set the *rlf-Cause* as *t310-Expiry*; +- 1> else if the UE declares radio link failure due to the random access problem indication from MCG MAC: + - 2> if the random access procedure was initiated for beam failure recovery: + - 3> set the *rlf-Cause* as *beamFailureRecoveryFailure*; + - 2> else: + - 3> set the *rlf-Cause* as *randomAccessProblem*; +- 1> else if the UE declares radio link failure due to the reaching of maximum number of retransmissions from the MCG RLC: + - 2> set the *rlf-Cause* as *rlc-MaxNumRetx*; +- 1> else if the UE declares radio link failure due to consistent uplink LBT failures: + - 2> set the *rlf-Cause* as *lbtFailure*; +- 1> else if the IAB-MT declares radio link failure due to the reception of a BH RLF indication on BAP entity: + - 2> set the *rlf-Cause* as *bh-rlfRecoveryFailure*. + +1> else if the UE declares radio link failure due to T312 expiry: + +2> set the *rlf-Cause* as *t312-Expiry*; + +#### 5.3.10.5 RLF report content determination + +The UE shall determine the content in the *VarRLF-Report* as follows: + +1> clear the information included in *VarRLF-Report*, if any; + +1> if the UE is not in SNPN access mode, set the *plmn-IdentityList* to include the list of EPLMNs stored by the UE (i.e. includes the RPLMN); + +1> else if the UE is in SNPN access mode, set the *snpn-IdentityList* to include the list of equivalent SNPNs stored by the UE (i.e., registered SNPN); + +1> set the *measResultLastServCell* to include the cell level RSRP, RSRQ and the available SINR, of the source PCell (in case HO failure) or PCell (in case RLF) based on the available SSB and CSI-RS measurements collected up to the moment the UE detected failure; + +1> if *measRSSI-ReportConfig* is configured for the frequency of the source PCell (in case HO failure) or PCell (in case of RLF), set the *measResultLastServCell-RSSI* to the linear average of the available RSSI sample value(s) provided by lower layers for the frequency of the source PCell (in case HO failure) or PCell (in case of RLF) up to the moment the UE detected the failure; + +1> if the SS/PBCH block-based measurement quantities are available: + +2> set the *rsIndexResults* in *measResultLastServCell* to include all the available measurement quantities of the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the highest SS/PBCH block RSRP is listed first if SS/PBCH block RSRP measurement results are available, otherwise the highest SS/PBCH block RSRQ is listed first if SS/PBCH block RSRQ measurement results are available, otherwise the highest SS/PBCH block SINR is listed first, based on the available SS/PBCH block based measurements collected up to the moment the UE detected failure; + +1> if the CSI-RS based measurement quantities are available: + +2> set the *rsIndexResults* in *measResultLastServCell* to include all the available measurement quantities of the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE detected failure; + +1> for each of the configured *measObjectNR* in which measurements are available: + +2> if the SS/PBCH block-based measurement quantities are available: + +3> set the *measResultListNR* in *measResultNeighCells* to include all the available measurement quantities of the best measured cells, other than the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the cell with highest SS/PBCH block RSRP is listed first if SS/PBCH block RSRP measurement results are available, otherwise the cell with highest SS/PBCH block RSRQ is listed first if SS/PBCH block RSRQ measurement results are available, otherwise the cell with highest SS/PBCH block SINR is listed first, based on the available SS/PBCH block based measurements collected up to the moment the UE detected failure; + +4> for each neighbour cell included, include the optional fields that are available; + +NOTE 0a: For the neighboring cells included in *measResultListNR* in *measResultNeighCells* ordered based on the SS/PBCH block measurement quantities, UE also includes the CSI-RS based measurement quantities, if available. + +2> if the CSI-RS based measurement quantities are available: + +3> set the *measResultListNR* in *measResultNeighCells* to include all the available measurement quantities of the best measured cells, other than the source PCell (in case HO failure) or PCell (in case RLF), ordered such that the cell with highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the cell with highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the cell with highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE detected radio link failure; + +4> for each neighbour cell included, include the optional fields that are available; + +NOTE 0b: For ordering the neighboring cells based on the CSI-RS measurement quantities, UE includes measurements only for the cells not yet included in *measResultListNR* in *measResultNeighCells* to avoid overriding SS/PBCH block-based ordered measurements. + +2> for each neighbour cell, if any, included in *measResultListNR* in *measResultNeighCells*: + +3> if the UE supports RLF-Report for conditional handover and if the neighbour cell is one of the candidate cells for which the *reconfigurationWithSync* is included in the *masterCellGroup* in the MCG *VarConditionalReconfig* at the moment of the detected failure: + +4> set *choConfig* in *MeasResult2NR* to the execution condition for each *measId* within *condTriggerConfig* associated to the neighbour cell within the MCG *VarConditionalReconfig*; + +4> if the first entry of *choConfig* corresponds to a fulfilled execution condition at the moment of handover failure, or radio link failure; or + +4> if the second entry of *choConfig*, if available, corresponds to a fulfilled execution condition at the moment of handover failure, or radio link failure: + +5> set *firstTriggeredEvent* to the execution condition *condFirstEvent* corresponding to the first entry of *choConfig* or to the execution condition *condSecondEvent* corresponding to the second entry of *choConfig*, whichever execution condition was fulfilled first in time; + +5> set *timeBetweenEvents* to the elapsed time between the point in time of fulfilling the condition in *choConfig* that was fulfilled first in time, and the point in time of fulfilling the condition in *choConfig* that was fulfilled second in time, if both the first execution condition corresponding to the first entry and the second execution condition corresponding to the second entry in the *choConfig* were fulfilled; + +1> for each of the configured *measObjectNR* if *measRSSI-ReportConfig* is configured for the configured frequency: + +2> set the *measResultNeighFreq-RSSI* in the *measResultNeighFreqList-RSSI* to the linear average of the available RSSI sample value(s) provided by lower layers for the frequencies other than the frequency of the source PCell (in case HO failure) or of the PCell (in case RLF), up to the moment the UE detected failure; + +1> for each of the configured EUTRA frequencies in which measurements are available; + +2> set the *measResultListEUTRA* in *measResultNeighCells* to include the best measured cells ordered such that the cell with highest RSRP measurement results are available, otherwise the cell with highest RSRQ is listed first, and based on measurements collected up to the moment the UE detected failure; + +3> for each neighbour cell included, include the optional fields that are available; + +NOTE 1: The measured quantities are filtered by the L3 filter as configured in the mobility measurement configuration. The measurements are based on the time domain measurement resource restriction, if configured. Exclude-listed cells are not required to be reported. + +1> set the *c-RNTI* to the C-RNTI used in the source PCell (in case HO failure) or PCell (in case RLF); + +1> if the failure is detected due to reconfiguration with sync failure as described in 5.3.5.8.3, set the fields in *VarRLF-report* as follows: + +2> set the *connectionFailureType* to *hof*; + +2> if the UE supports RLF-Report for DAPS handover and if any DAPS bearer was configured while T304 was running: + +3> set *lastHO-Type* to *daps*; + +3> if radio link failure was detected in the source PCell, according to clause 5.3.10.3: + +4> set *timeConnSourceDAPS-Failure* to the time between the initiation of the DAPS handover execution and the radio link failure detected in the source PCell while T304 was running; + +4> set the *rlf-Cause* to the trigger for detecting the source radio link failure in accordance with clause 5.3.10.4; + +2> if the UE supports RLF-Report for conditional handover and if configuration of the conditional handover is available in the MCG *VarConditionalReconfig* at the moment of the handover failure: + +3> if the UE executed a conditional handover toward target PCell according to the *condRRCReconfig* of the target PCell: + +4> set *timeSinceCHO-Reconfig* to the time elapsed between the execution of the last *RRCReconfiguration* message including *reconfigurationWithSync* for the target PCell of the failed conditional handover, and the reception in the source PCell of the last *conditionalReconfiguration* including the *condRRCReconfig* of the target PCell of the failed conditional handover; + +3> else: + +4> set *timeSinceCHO-Reconfig* to the time elapsed between the execution of the last *RRCReconfiguration* message including *reconfigurationWithSync* for the target PCell of the failed handover, and the reception in the source PCell of the last *conditionalReconfiguration* including the *condRRCReconfig*; + +3> set *choCandidateCellList* to include the global cell identity, if available, and otherwise to the physical cell identity and carrier frequency of each of the candidate target cells for conditional handover included in *condRRCReconfig* within the MCG *VarConditionalReconfig* at the time of the failed handover, excluding the candidate target cells included in *measResultNeighCells*; + +- 2> if the UE supports RLF-Report for conditional handover and if the last executed *RRReconfiguration* message including *reconfigurationWithSync* was concerning a conditional handover: + - 3> set *lastHO-Type* to *cho*; + - 2> set the *nrFailedPCellId* in *failedPCellId* to the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the target PCell of the failed handover; + - 2> include *nrPreviousCell* in *previousPCellId* and set it to the global cell identity and tracking area code of the PCell where the last *RRReconfiguration* message including *reconfigurationWithSync* was received; + - 2> set the *timeConnFailure* to the elapsed time since the execution of the last *RRReconfiguration* message including the *reconfigurationWithSync*; +- 1> else if the failure is detected due to Mobility from NR failure as described in 5.4.3.5, set the fields in *VarRLF-report* as follows: + - 2> set the *connectionFailureType* to *hof*; + - 2> if last *MobilityFromNRCommand* concerned a failed inter-RAT handover from NR to E-UTRA and if the UE supports Radio Link Failure Report for Inter-RAT MRO EUTRA (NR to EUTRA): + - 3> set the *eutraFailedPCellId* in *failedPCellId* to the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the target PCell of the failed handover; + - 2> include *nrPreviousCell* in *previousPCellId* and set it to the global cell identity and tracking area code of the PCell where the last *MobilityFromNRCommand* message was received; + - 2> set the *timeConnFailure* to the elapsed time since the initialization of the handover associated to the last *MobilityFromNRCommand* message; + - 2> if *voiceFallbackIndication* is included in the last *MobilityFromNRCommand*: + - 3> include the *voiceFallbackHO*; + - 1> else if the failure is detected due to radio link failure as described in 5.3.10.3, set the fields in *VarRLF-report* as follows: + - 2> set the *connectionFailureType* to *rlf*; + - 2> set the *rlf-Cause* to the trigger for detecting radio link failure in accordance with clause 5.3.10.4; + - 2> set the *nrFailedPCellId* in *failedPCellId* to the global cell identity and the tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the PCell where radio link failure is detected; + - 2> if an *RRReconfiguration* message including the *reconfigurationWithSync* was received before the connection failure: + +- 3> if the last successfully executed *RRCReconfiguration* message including the *reconfigurationWithSync* concerned an intra NR handover and it was received while connected to the previous PCell to which the UE was connected before connecting to the PCell where radio link failure is detected; and +- 3> if T311 was not running before entering the PCell in which the radio link failure was detected: + - 4> include the *nrPreviousCell* in *previousPCellId* and set it to the global cell identity and the tracking area code of the PCell where the last executed *RRCReconfiguration* message including *reconfigurationWithSync* was received; + - 4> if the last executed *RRCReconfiguration* message including *reconfigurationWithSync* was concerning a DAPS handover: + - 5> set *lastHO-Type* to *daps*; + - 4> else if the last executed *RRCReconfiguration* message including *reconfigurationWithSync* was concerning a conditional handover: + - 5> set *lastHO-Type* to *cho*; + - 4> set the *timeConnFailure* to the elapsed time since the execution of the last *RRCReconfiguration* message including the *reconfigurationWithSync*; +- 3> else if the last *RRCReconfiguration* message including the *reconfigurationWithSync* concerned a handover to NR from E-UTRA and if the UE supports Radio Link Failure Report for Inter-RAT MRO EUTRA: + - 4> include the *eutraPreviousCell* in *previousPCellId* and set it to the global cell identity and the tracking area code of the E-UTRA PCell where the last *RRCReconfiguration* message including *reconfigurationWithSync* was received embedded in E-UTRA RRC message *MobilityFromEUTRACommand* message as specified in TS 36.331 [10] clause 5.4.3.3; + - 4> set the *timeConnFailure* to the elapsed time since reception of the last *RRCReconfiguration* message including the *reconfigurationWithSync* embedded in E-UTRA RRC message *MobilityFromEUTRACommand* message as specified in TS 36.331 [10] clause 5.4.3.3; +- 2> if configuration of the conditional handover is available in the MCG *VarConditionalReconfig* at the moment of declaring the radio link failure: + - 3> set *timeSinceCHO-Reconfig* to the time elapsed between the detection of the radio link failure, and the reception, in the source PCell, of the last *conditionalReconfiguration* including the *condRRCReconfig* message; + - 3> set *choCandidateCellList* to include the global cell identity if available, and otherwise to the physical cell identity and carrier frequency of each of all the candidate target cells for conditional handover included in *condRRCReconfig* within the MCG *VarConditionalReconfig* at the time of radio link failure, excluding the candidate target cells included in *measResultNeighCells*; +- 1> if *connectionFailureType* is *rlf* and the *rlf-Cause* is set to *randomAccessProblem* or *beamFailureRecoveryFailure*; or +- 1> if *connectionFailureType* is *rlf* and the *rlf-Cause* is set to *lbtFailure* and the radio link failure is detected during the random access procedure; or +- 1> if *connectionFailureType* is *hof* and if the failed handover is an intra-RAT handover: + - 2> set the *ra-InformationCommon* to include the random-access related information as described in clause 5.7.10.5; + +- 1> if *connectionFailureType* is *rlf* and the *rlf-Cause* is set to *lbtFailure*, and the radio link failure is not detected during the random access procedure: + - 2> set the *locationAndBandwidth* and *subcarrierSpacing* in *bwp-Info* associated to the UL BWP in which the consistent uplink LBT failure was detected; + - 1> if the *rlf-Cause* is set to *t310-Expiry* or *t312-Expiry*: + - 2> set the *ssbRLMConfigBitmap* and/or *csi-rsRLMConfigBitmap* in *measResultLastServCell* to include the radio link monitoring configuration of the last serving cell, if available; + - 1> if the UE supports RLF-Report for fast MCG recovery procedure: + - 2> if the fast MCG recovery procedure fails due to expiry of timer T316: + - 3> set the *mcgRecoveryFailureCause* to *t316-expiry*; + - 2> else if the SCG was deactivated before initiation of the fast MCG recovery procedure: + - 3> set the *mcgRecoveryFailureCause* to *scgDeactivated*; +- Editor's note: The use of *scgDeactivated* cause. +- 2> else if the UE detected SCG failure while the timer T316 was running or before initiation of the fast MCG recovery procedure: + - 3> set the *pSCellId* to the global cell identity of the PSCell, if available, otherwise to the physical cell identity and carrier frequency of the PSCell; + - 3> set the *scgFailureCause* value according to 5.7.3.5; + - 3> set the *elapsedTimeSCGFailure* to the time elapsed between SCG failure and the MCG failure; + - 1> if available, set the *locationInfo* as in 5.3.3.7. + +The UE may discard the radio link failure information or handover failure information, i.e. release the UE variable *VarRLF-Report*, 48 hours after the radio link failure/handover failure is detected. + +NOTE 2: In this clause, the term 'handover failure' has been used to refer to 'reconfiguration with sync failure'. + +### 5.3.11 UE actions upon going to RRC\_IDLE + +The UE shall: + +- 1> reset MAC; +- 1> if the UE is NCR-MT: + +``` +2> indicate to NCR-Fwd to cease forwarding; +1> set the variable pendingRNA-Update to false, if that is set to true; +1> if going to RRC_IDLE was triggered by reception of the RRCRelease message including a waitTime: +2> if T302 is running: +3> stop timer T302; +2> start timer T302 with the value set to the waitTime; +2> inform upper layers that access barring is applicable for all access categories except categories '0' and '2'. +1> else: +2> if T302 is running: +3> stop timer T302; +3> perform the actions as specified in 5.3.14.4; +1> if T390 is running: +2> stop timer T390 for all access categories; +2> perform the actions as specified in 5.3.14.4; +1> if the UE is leaving RRC_INACTIVE: +2> if going to RRC_IDLE was not triggered by reception of the RRCRelease message: +3> if stored, discard the cell reselection priority information provided by the cellReselectionPriorities; +3> stop the timer T320, if running; +2> if T319a is running: +3> stop timer T319a; +3> consider SDT procedure is not ongoing; +1> stop all timers that are running except T302, T320, T325, T330, T331, T400 and T430; +1> discard the UE Inactive AS context, if any; +``` + +- 1> release the *suspendConfig*, if configured; +- 1> release the *uav-Config*, if configured; +- 1> perform LTM configuration release procedure for the MCG and SCG as specified in clause 5.3.5.18.7; +- 1> remove all the entries within the MCG and the SCG *VarConditionalReconfig*, if any; +- 1> remove the *servingSecurityCellSetId* within the *VarServingSecurityCellSetID*, if any; +- 1> for each *measId*, if the associated *reportConfig* has a *reportType* set to *condTriggerConfig*: + - 2> for the associated *reportConfigId*: + - 3> remove the entry with the matching *reportConfigId* from the *reportConfigList* within the *VarMeasConfig*; + - 2> if the associated *measObjectId* is only associated to a *reportConfig* with *reportType* set to *condTriggerConfig*: + - 3> remove the entry with the matching *measObjectId* from the *measObjectList* within the *VarMeasConfig*; + - 2> remove the entry with the matching *measId* from the *measIdList* within the *VarMeasConfig*; +- 1> discard the $K_{gNB}$ key, the $S-K_{gNB}$ key, the $S-K_{eNB}$ key, the $K_{RRCEnc}$ key, the $K_{RRCCint}$ key, the $K_{UPint}$ key and the $K_{UPenc}$ key, if any; +- 1> release all radio resources, including release of the RLC entity, the BAP entity, the MAC configuration and the associated PDCP entity and SDAP for all established RBs (except for broadcast MRBs), BH RLC channels, Uu Relay RLC channels, PC5 Relay RLC channels and SRAP entity; + +NOTE 0: A L2 U2N Relay UE may re-establish the SL-RLC0, SL-RLC1 and SRAP entity after release. + +- 1> indicate the release of the RRC connection to upper layers together with the release cause; +- 1> for each application layer measurement configuration for which *configForRRC-IdleInactive* is not set to *true*: + - 2> inform upper layers about the release of all application layer measurement configurations; + - 2> discard any application layer measurement reports which were not yet submitted to lower layers for transmission; +- 1> for each application layer measurement configuration for which *configForRRC-IdleInactive* is set to *true*: + - 2> initiate the procedure in 5.5b.1.2; +- 1> discard any segments of segmented RRC messages stored according to 5.7.6.3; + +1> except if going to RRC\_IDLE was triggered by inter-RAT cell reselection while the UE is in RRC\_INACTIVE or RRC\_IDLE or when selecting an inter-RAT cell while T311 was running or when selecting an E-UTRA cell for EPS fallback for IMS voice as specified in 5.4.3.5: + +2> if the UE is capable of L2 U2N Remote UE: + +3> enter RRC\_IDLE, and perform either cell selection as specified in TS 38.304 [20], or relay selection as specified in clause 5.8.15.3, or both; + +2> else: + +3> enter RRC\_IDLE and perform cell selection as specified in TS 38.304 [20]; + +NOTE 1: Whether to release the PC5 unicast link is left to L2 U2N Remote UE's implementation. + +NOTE 2: It is left to UE implementation whether to stop T430, if running, when going to RRC\_IDLE. + +### 5.3.12 UE actions upon PUCCH/SRS release request + +Upon receiving a PUCCH release request from lower layers, for all bandwidth parts of an indicated serving cell the UE shall: + +1> release PUCCH-CSI-Resources configured in *CSI-ReportConfig*; + +1> release *SchedulingRequestResourceConfig* instances configured in *PUCCH-Config*. + +Upon receiving an SRS release request from lower layers, for all bandwidth parts of an indicated serving cell the UE shall: + +1> release *SRS-Resource* instances configured in *SRS-Config*. + +Upon receiving a positioning SRS configuration for RRC\_INACTIVE release request from lower layers, the UE shall: + +1> release the configured *srs-PosRRC-Inactive*. + +### 5.3.13 RRC connection resume + +#### 5.3.13.1 General + +![Sequence diagram for successful RRC connection resume](bfca6639dd4b8480f2d96d2b61c806d9_img.jpg) + +``` +sequenceDiagram + participant UE + participant Network + Note left of UE: + UE->>Network: RRCResumeRequest/RRCResumeRequest1 + Network-->>UE: RRCResume + Note right of Network: + UE->>Network: RRCResumeComplete +``` + +A sequence diagram illustrating a successful RRC connection resume. It features two lifelines: UE (User Equipment) on the left and Network on the right. The interaction begins with the UE sending an *RRCResumeRequest/RRCResumeRequest1* message to the Network. The Network responds with an *RRCResume* message. Finally, the UE sends an *RRCResumeComplete* message to the Network, completing the resume procedure. + +Sequence diagram for successful RRC connection resume + +Figure 5.3.13.1-1: RRC connection resume, successful + +![Sequence diagram for RRC connection resume fallback to RRC connection establishment](ada2aa7cce9cff9cf116d9ae2b8b7c27_img.jpg) + +``` +sequenceDiagram + participant UE + participant Network + Note left of UE: + UE->>Network: RRCResumeRequest/RRCResumeRequest1 + Network-->>UE: RRCSetup + Note right of Network: + UE->>Network: RRCSetupComplete +``` + +A sequence diagram illustrating an RRC connection resume fallback to RRC connection establishment. It features two lifelines: UE (User Equipment) on the left and Network on the right. The interaction begins with the UE sending an *RRCResumeRequest/RRCResumeRequest1* message to the Network. Instead of resuming, the Network responds with an *RRCSetup* message, initiating a new connection establishment. The UE then responds with an *RRCSetupComplete* message, completing the establishment procedure. + +Sequence diagram for RRC connection resume fallback to RRC connection establishment + +Figure 5.3.13.1-2: RRC connection resume fallback to RRC connection establishment, successful + +![Sequence diagram for RRC connection resume followed by network release, successful](e2c120be98ede6deb60dd341f5a9803b_img.jpg) + +``` +sequenceDiagram + participant UE + participant Network + Note left of UE: + UE->>Network: RRCResumeRequest/RRCResumeRequest1 + Network-->>UE: RRCHRelease +``` + +A sequence diagram showing the interaction between a User Equipment (UE) and a Network. The UE sends an *RRCResumeRequest/RRCResumeRequest1* message to the Network. The Network responds with an *RRCHRelease* message. The lifelines for UE and Network are shown as vertical lines with rectangular boxes at the top. + +Sequence diagram for RRC connection resume followed by network release, successful + +Figure 5.3.13.1-3: RRC connection resume followed by network release, successful + +![Sequence diagram for RRC connection resume followed by network suspend, successful](76d19e4271bf243b20d55a98efd51483_img.jpg) + +``` +sequenceDiagram + participant UE + participant Network + Note left of UE: + UE->>Network: RRCResumeRequest/RRCResumeRequest1 + Network-->>UE: RRCRelease with suspend configuration +``` + +A sequence diagram showing the interaction between a User Equipment (UE) and a Network. The UE sends an *RRCResumeRequest/RRCResumeRequest1* message to the Network. The Network responds with an *RRCRelease with suspend configuration* message. The lifelines for UE and Network are shown as vertical lines with rectangular boxes at the top. + +Sequence diagram for RRC connection resume followed by network suspend, successful + +Figure 5.3.13.1-4: RRC connection resume followed by network suspend, successful + +![Sequence diagram for RRC connection resume, network reject](23cb65390082ab306c15bd3d8196135e_img.jpg) + +``` +sequenceDiagram + participant UE + participant Network + Note left of UE: + UE->>Network: RRCResumeRequest/RRCResumeRequest1 + Network-->>UE: RRCReject +``` + +A sequence diagram showing the interaction between a User Equipment (UE) and a Network. The UE sends an *RRCResumeRequest/RRCResumeRequest1* message to the Network. The Network responds with an *RRCReject* message. The lifelines for UE and Network are shown as vertical lines with rectangular boxes at the top. + +Sequence diagram for RRC connection resume, network reject + +Figure 5.3.13.1-5: RRC connection resume, network reject + +The purpose of this procedure is to resume a suspended RRC connection, including resuming SRB(s), DRB(s) and multicast MRB(s) or perform an RNA update. This procedure is also used to initiate SDT in RRC\_INACTIVE. + +#### 5.3.13.1a Conditions for resuming RRC Connection for NR sidelink communication/discovery/V2X sidelink communication + +For NR sidelink communication/discovery an RRC connection is resumed only in the following cases: + +- 1> if configured by upper layers to transmit NR sidelink communication and related data is available for transmission: + - 2> if the frequency on which the UE is configured to transmit NR sidelink communication is included in *sl-FreqInfoList/sl-FreqInfoListSizeExt* within *SIB12* provided by the cell on which the UE camps; and if the valid version of *SIB12* does not include *sl-TxPoolSelectedNormal* for the concerned frequency; +- 1> if configured by upper layers to transmit NR sidelink discovery and related data is available for transmission: + - 2> if the UE is configured by upper layers to transmit NR sidelink L2 U2N relay discovery messages and *sl-L2U2N-Relay* is included in *SIB12*; or + - 2> if the UE is configured by upper layers to transmit NR sidelink L3 U2N relay discovery messages and *sl-L3U2N-RelayDiscovery* is included in *SIB12*; or + - 2> if the UE is configured by upper layers to transmit NR sidelink non-relay discovery messages and *sl-NonRelayDiscovery* is included in *SIB12*: + - 3> if the frequency on which the UE is configured to transmit NR sidelink discovery is included in *sl-FreqInfoList/sl-FreqInfoListSizeExt* within *SIB12* provided by the cell on which the UE camps; and if the valid version of *SIB12* does not include *sl-DiscTxPoolSelected* or *sl-TxPoolSelectedNormal* for the concerned frequency; + +For L2 U2N Relay UE in RRC\_INACTIVE, an RRC connection establishment is resumed in the following cases: + +- 1> if any message is received from the L2 U2N Remote UE via SL-RLC0 as specified in 9.1.1.4 or SL-RLC1 as specified in 9.2.4; or +- 1> if *RemoteUEInformationSidelink* containing the *connectionForMP* is received from a L2 U2N Remote UE as specified in 5.8.9.8.3; + +For V2X sidelink communication an RRC connection resume is initiated only when the conditions specified for V2X sidelink communication in clause 5.3.3.1a of TS 36.331 [10] are met. + +NOTE: Upper layers initiate an RRC connection resume (except if the RRC connection resume is initiated at the L2 U2N Relay UE upon reception of a message from a L2 U2N Remote UE via SL-RLC0 or SL-RLC1). The interaction with NAS is left to UE implementation. + +#### 5.3.13.1b Conditions for initiating SDT + +A UE in RRC\_INACTIVE initiates the resume procedure for SDT when all of the following conditions are fulfilled: + +- 1> for the resume procedure initiated by the upper layers (i.e. mobile originated case): + - 2> SIB1 includes *sdt-ConfigCommon*; and + - 2> *sdt-Config* is configured; and + - 2> all the pending data in UL is mapped to the radio bearers configured for SDT; and + +- 2> for an (e)RedCap UE when (e)RedCap-specific initial downlink BWP includes no CD-SSB, *ncd-SSB-RedCapInitialBWP-SDT* is configured; and +- 2> lower layers indicate that conditions for initiating MO-SDT as specified in TS 38.321 [3] are fulfilled. +- 1> for the resume procedure initiated in response to RAN paging (i.e. mobile terminated case): + - 2> *mt-SDT* indication was included in the paging message for the UE's stored *fullI-RNTI*; and + - 2> lower layers indicate that conditions for initiating MT-SDT as specified in TS 38.321 [3] are fulfilled. + +NOTE: How the UE determines that all pending data in UL is mapped to radio bearers configured for SDT is left to UE implementation. + +#### 5.3.13.1c Conditions for resuming RRC Connection for NR sidelink Positioning + +For NR sidelink positioning an RRC connection is resumed only in the following cases: + +- 1> if SL-PRS transmission is triggered: + - 2> if the frequency on which the UE is configured to transmit NR sidelink positioning is included in *sl-FreqInfoList* within *SIB25* provided by the cell on which the UE camps; and if the valid version of *SIB25* does not include *sl-PRS-TxPoolSelectedNormal* for the concerned frequency; + +##### 5.3.13.1d RRC connection resume for multicast reception + +In RRC\_INACTIVE state, if configured with MBS multicast reception in RRC\_INACTIVE, the UE shall: + +- 1> if the RRC connection resume procedure is triggered for multicast reception at reception of *SIB1*, as specified in 5.2.2.4.2; or +- 1> if the PTM configuration is not available in the cell after cell selection or reselection for a multicast session that the UE has joined for which the UE is not indicated to stop monitoring the G-RNTI; or +- 1> if *mbs-NeighbourCellList* acquired in the previous cell indicates that a multicast session that the UE has joined for which the UE is not indicated to stop monitoring the G-RNTI is not provided for RRC\_INACTIVE in the current serving cell; or +- 1> if the measured RSRP or RSRQ for serving cell as specified in TS 38.304 [20] is below the threshold indicated by *thresholdIndex* for a multicast session that the UE has joined: + - 2> initiate RRC connection resume procedure in 5.3.13.2 with *resumeCause* set to *mt-Access*. + +#### 5.3.13.2 Initiation + +The UE initiates the procedure when upper layers or AS (when responding to RAN paging, upon triggering RNA updates while the UE is in RRC\_INACTIVE, upon requesting multicast reception as specified in clause 5.3.13.1d, for NR sidelink communication/discovery/V2X sidelink communication as specified in clause 5.3.13.1a, for NR sidelink positioning as specified in clause 5.3.13.1c, for requesting configuration for SRS for positioning, for activation of preconfigured Positioning SRS in RRC\_INACTIVE, upon + +receiving *RRRelease* message including *resumeIndication*) requests the resume of a suspended RRC connection or requests the resume for initiating SDT as specified in clause 5.3.13.1b. + +The UE shall ensure having valid and up to date essential system information as specified in clause 5.2.2.2 before initiating this procedure. + +Upon initiation of the procedure, the UE shall: + +- 1> if the resumption of the RRC connection is triggered by response to NG-RAN paging; or +- 1> if the resumption of the RRC connection is triggered by receiving *RRRelease* message including *resumeIndication*; or +- 1> if the resumption of the RRC connection is triggered by multicast reception request as specified in clause 5.3.13.1d: + - 2> select '0' as the Access Category; + - 2> perform the unified access control procedure as specified in 5.3.14 using the selected Access Category and one or more Access Identities provided by upper layers; + - 3> if the access attempt is barred, the procedure ends; +- 1> else if the resumption of the RRC connection is triggered by upper layers: + - 2> if the upper layers provide an Access Category and one or more Access Identities: + - 3> perform the unified access control procedure as specified in 5.3.14 using the Access Category and Access Identities provided by upper layers; + - 4> if the access attempt is barred, the procedure ends; + - 2> if the upper layers provide NSAG information and one or more S-NSSAI(s) triggering the access attempt (TS 23.501 [32] and TS 24.501 [23]): + - 3> apply the NSAG with highest NSAG priority among the NSAGs that are included in *SIB1* (i.e., in *FeatureCombination* and/or in *RA-PrioritizationSliceInfo*), and that are associated with the S-NSSAI(s) triggering the access attempt, in the Random Access procedure (TS 38.321 [3], clause 5.1); + +NOTE: If there are multiple NSAGs with the same highest NAS-provided NSAG priority identified for access attempt as above, it is left to UE implementation to select the NSAG to be applied in the Random Access procedure. + +- 2> if the resumption occurs after release with redirect with *mpsPriorityIndication*: + - 3> set the *resumeCause* to *mps-PriorityAccess*; +- 2> else: + - 3> set the *resumeCause* in accordance with the information received from upper layers; +- 1> else if the resumption of the RRC connection is triggered due to an RNA update as specified in 5.3.13.8: + +2> if an emergency service is ongoing: + +NOTE 1: How the RRC layer in the UE is aware of an ongoing emergency service is up to UE implementation. + +3> select '2' as the Access Category; + +3> set the *resumeCause* to *emergency*; + +2> else: + +3> select '8' as the Access Category; + +2> perform the unified access control procedure as specified in 5.3.14 using the selected Access Category and one or more Access Identities to be applied as specified in TS 24.501 [23]; + +3> if the access attempt is barred: + +4> set the variable *pendingRNA-Update* to *true*; + +4> the procedure ends; + +1> else if *srs-PosRRC-InactiveValidityAreaConfig* is configured and the resumption of the RRC connection is triggered due to cell reselection to a cell that is not included in *srs-PosConfigValidityArea* and there is an on-going SRS for positioning transmission: + +2> select '8' as the Access Category; + +2> set the *resumeCause* to *srs-PosConfigOrActivationReq*; + +1> else if *srs-PosRRC-InactiveValidityAreaConfig* is configured and the resumption of the RRC connection is triggered due to upper layers request for configuration or activation of preconfigured SRS for positioning when the UE is camped in one of the cells indicated in *srs-PosConfigValidityArea*: + +2> select '8' as the Access Category; + +2> set the *resumeCause* to *srs-PosConfigOrActivationReq*; + +NOTE 2: In case the L2 U2N Relay UE initiates RRC connection resume triggered by reception of message from a L2 U2N Remote UE via SL-RLC0 or SL-RLC1 as specified in 5.3.13.1a, the L2 U2N Relay UE sets the *resumeCause* by implementation, but it can only set the *emergency*, *mps-PriorityAccess*, or *mcs-PriorityAccess* as *resumeCause*, if the same cause value in the message received from the L2 U2N Remote UE via SL-RLC0. + +1> if the UE is in NE-DC or NR-DC: + +2> if the UE does not support maintaining SCG configuration upon connection resumption: + +3> release the MR-DC related configurations (i.e., as specified in 5.3.5.10) from the UE Inactive AS context, if stored; + +- 1> if the UE does not support maintaining the MCG SCell configurations upon connection resumption: + - 2> release the MCG SCell(s) from the UE Inactive AS context, if stored; +- 1> if the UE is acting as L2 U2N Remote UE: + - 2> establish a SRAP entity as specified in TS 38.351 [66], if no SRAP entity has been established; + - 2> apply the default configuration of SL-RLC1 as defined in 9.2.4 for SRB1; + - 2> apply the default PDCP configuration as defined in 9.2.1 for SRB1; + - 2> apply the default configuration of SRAP as defined in 9.2.5 for SRB1; +- 1> else: + - 2> apply the default L1 parameter values as specified in corresponding physical layer specifications, except for the parameters for which values are provided in *SIB1*; + - 2> apply the default SRB1 configuration as specified in 9.2.1; + - 2> apply the default MAC Cell Group configuration as specified in 9.2.2; +- 1> release *delayBudgetReportingConfig* from the UE Inactive AS context, if stored; +- 1> stop timer T342, if running; +- 1> release *overheatingAssistanceConfig* from the UE Inactive AS context, if stored; +- 1> stop timer T345, if running; +- 1> release *idc-AssistanceConfig* from the UE Inactive AS context, if stored; +- 1> release *drx-PreferenceConfig* for all configured cell groups from the UE Inactive AS context, if stored; +- 1> stop all instances of timer T346a, if running; +- 1> release *maxBW-PreferenceConfig* and *maxBW-PreferenceConfigFR2-2* for all configured cell groups from the UE Inactive AS context, if stored; +- 1> stop all instances of timer T346b, if running; +- 1> release *maxCC-PreferenceConfig* for all configured cell groups from the UE Inactive AS context, if stored; +- 1> stop all instances of timer T346c, if running; +- 1> release *maxMIMO-LayerPreferenceConfig* and *maxMIMO-LayerPreferenceConfigFR2-2* for all configured cell groups from the UE Inactive AS context, if stored; + +1> stop all instances of timer T346d, if running; + +1> release *minSchedulingOffsetPreferenceConfig* and *minSchedulingOffsetPreferenceConfigExt* for all configured cell groups from the UE Inactive AS context, if stored; + +1> stop all instances of timer T346e, if running; + +1> release *rlm-RelaxationReportingConfig* for all configured cell groups from the UE Inactive AS context, if stored; + +1> stop all instances of timer T346j, if running; + +1> release *bfd-RelaxationReportingConfig* for all configured cell groups from the UE Inactive AS context, if stored; + +1> stop all instances of timer T346k, if running; + +1> release *releasePreferenceConfig* from the UE Inactive AS context, if stored; + +1> release *wlanNameList* from the UE Inactive AS context, if stored; + +1> release *btNameList* from the UE Inactive AS context, if stored; + +1> release *sensorNameList* from the UE Inactive AS context, if stored; + +1> release *obtainCommonLocation* from the UE Inactive AS context, if stored; + +1> stop timer T346f, if running; + +1> stop timer T346i, if running; + +1> release *referenceTimePreferenceReporting* from the UE Inactive AS context, if stored; + +1> release *sl-AssistanceConfigNR* from the UE Inactive AS context, if stored; + +1> release *musim-GapAssistanceConfig* from the UE Inactive AS context, if stored and stop timer T346h, if running; + +1> release *musim-GapConfig* from the UE Inactive AS context, if stored; + +1> release *musim-GapPriorityAssistanceConfig* from the UE Inactive AS context, if stored; + +1> release *musim-LeaveAssistanceConfig* from the UE Inactive AS context, if stored; + +1> release *musim-CapabilityRestrictionConfig* from the UE Inactive AS context, if stored and stop timer T346n, if running; + +1> release *propDelayDiffReportConfig* from the UE Inactive AS context, if stored; + +1> release *ul-GapFR2-PreferenceConfig*, if configured; + +- 1> release *rrm-MeasRelaxationReportingConfig* from the UE Inactive AS context, if stored; +- 1> release *multiRx-PreferenceReportingConfigFR2* if configured, and stop timer T440, if running; +- 1> release *uav-FlightPathAvailabilityConfig* from the UE Inactive AS context, if stored; +- 1> release *ul-TrafficInfoReportingConfig* from the UE Inactive AS context, if stored; +- 1> stop all instances of timer T346x, if running; +- 1> if the UE is acting as L2 U2N Remote UE: + - 2> apply the specified configuration of SL-RLC0 used for the delivery of RRC message over SRB0 as specified in 9.1.1.4; + - 2> apply the SDAP configuration and PDCP configuration as specified in 9.1.1.2 for SRB0; +- 1> else: + - 2> apply the CCCH configuration as specified in 9.1.1.2; + - 2> apply the *timeAlignmentTimerCommon* included in *SIB1*; +- 1> if *sdt-MAC-PHY-CG-Config* is configured: + - 2> if the resume procedure is initiated in a cell that is different to the PCell in which the UE received the stored *sdt-MAC-PHY-CG-Config*: + - 3> release the stored *sdt-MAC-PHY-CG-Config*; + - 3> instruct the MAC entity to stop the *cg-SDT-TimeAlignmentTimer*, if it is running; +- 1> if *ncd-SSB-RedCapInitialBWP-SDT* is configured: + - 2> if the resume procedure is initiated in a cell that is different to the PCell in which the UE received the stored *ncd-SSB-RedCapInitialBWP-SDT*: + - 3> release the stored *ncd-SSB-RedCapInitialBWP-SDT*; +- 1> if conditions for initiating SDT in accordance with 5.3.13.1b are fulfilled: + - 2> consider the resume procedure is initiated for SDT; + - 2> start timer T319a when the lower layers first transmit the CCCH message; + - 2> consider SDT procedure is ongoing; + +- 1> else: + - 2> start timer T319; + - 2> instruct the MAC entity to stop the *cг-SDT-TimeAlignmentTimer*, if it is running; +- 1> if *ta-Report* or *ta-ReportATG* is configured with value *enabled* and the UE supports TA reporting: + - 2> indicate TA report initiation to lower layers; +- 1> set the variable *pendingRNA-Update* to *false*; +- 1> release *successHO-Config* from the UE Inactive AS context, if stored; +- 1> release *successPSCell-Config* configured by the PCell from the UE Inactive AS context, if stored; +- 1> release *successPSCell-Config* configured by the PSCell from the UE Inactive AS context, if stored; +- 1> initiate transmission of the *RRCResumeRequest* message or *RRCResumeRequest1* in accordance with 5.3.13.3. + +#### 5.3.13.3 Actions related to transmission of *RRCResumeRequest* or *RRCResumeRequest1* message + +The UE shall set the contents of *RRCResumeRequest* or *RRCResumeRequest1* message as follows: + +- 1> if field *useFullResumeID* is signalled in *SIB1*: + - 2> select *RRCResumeRequest1* as the message to use; + - 2> set the *resumeIdentity* to the stored *fullI-RNTI* value; +- 1> else: + - 2> select *RRCResumeRequest* as the message to use; + - 2> set the *resumeIdentity* to the stored *shortI-RNTI* value; +- 1> restore the RRC configuration, RoHC state, the EHC context(s), the UDC state, the stored QoS flow to DRB mapping rules and the $K_{gNB}$ and $K_{RRCint}$ keys from the stored UE Inactive AS context except for the following: + - masterCellGroup; + - mrdc-SecondaryCellGroup, if stored; and + - pdcp-Config; + +- 1> set the *resumeMAC-I* to the 16 least significant bits of the MAC-I calculated: + - 2> over the ASN.1 encoded as per clause 8 (i.e., a multiple of 8 bits) *VarResumeMAC-Input*; + - 2> with the $K_{RRCint}$ key in the UE Inactive AS Context and the previously configured integrity protection algorithm; and + - 2> with all input bits for COUNT, BEARER and DIRECTION set to binary ones; + - 1> derive the $K_{gNB}$ key based on the current $K_{gNB}$ key or the NH, using the *nextHopChainingCount* value received in the previous *RRRelease* message and stored in the UE Inactive AS Context, as specified in TS 33.501 [11]; + - 1> derive the $K_{RRCenc}$ key, the $K_{RRCint}$ key, the $K_{UPint}$ key and the $K_{UPenc}$ key; + - 1> configure lower layers to apply integrity protection for all radio bearers except SRB0 and MRBs using the configured algorithm and the $K_{RRCint}$ key and $K_{UPint}$ key derived in this clause immediately, i.e., integrity protection shall be applied to all subsequent messages received and sent by the UE; +- NOTE 1: Only DRBs with previously configured UP integrity protection shall resume integrity protection. +- 1> configure lower layers to apply ciphering for all radio bearers except SRB0 and MRBs and to apply the configured ciphering algorithm, the $K_{RRCenc}$ key and the $K_{UPenc}$ key derived in this clause, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE; + - 1> re-establish PDCP entities for SRB1; + - 1> resume SRB1; + - 1> if the resume procedure is initiated for SDT: + - 2> for each radio bearer that is configured for SDT and for SRB1: + - 3> restore the *RLC-BearerConfig* associated with the RLC bearers of *masterCellGroup* and *pdcp-Config* from the UE Inactive AS context; + - 3> if the radio bearer is a DRB configured with Ethernet Header Compression: + - 4> indicate to lower layer that *ethernetHeaderCompression* is not configured; + - 3> if the radio bearer is a DRB configured with UDC: + - 4> indicate to lower layer that *uplinkDataCompression* is not configured; + - 3> if the radio bearer is a DRB configured with ROHC function: + - 4> if *sdt-DRB-ContinueROHC* is set to *cell* and the resume procedure is initiated in a cell that is the same as the PCell in which the UE received the previous *RRRelease* message; or + +4> if *sdt-DRB-ContinueROHC* is set to *rna* and the resume procedure is initiated in a cell belonging to the same RNA as the PCell in which the UE received the previous *RRRelease* message: + +5> indicate to lower layer that *drb-continueROHC* is configured; + +4> else: + +5> indicate to lower layer that *drb-continueROHC* is not configured; + +3> re-establish PDCP entity for the radio bearer that is configured for SDT without triggering PDCP status report; + +2> resume all the radio bearers that are configured for SDT; + +1> submit the selected message *RRResumeRequest* or *RRResumeRequest1* for transmission to lower layers. + +NOTE 2: Only DRBs with previously configured UP ciphering shall resume ciphering. + +NOTE 2a: Before the lower layers first transmit the *RRResumeRequest* or *RRResumeRequest1*, the UE may initiate a new resume procedure if other conditions for initiation of the resume procedure as specified in 5.3.13.2 are satisfied. + +If lower layers indicate an integrity check failure while T319 is running or SDT procedure is ongoing, perform actions specified in 5.3.13.5. + +If the UE is an (e)RedCap UE and the (e)RedCap-specific initial downlink BWP is not associated with CD-SSB, the UE may continue cell re-selection related measurements as well as cell re-selection evaluation, otherwise the UE shall continue cell re-selection related measurements as well as cell re-selection evaluation. If the conditions for cell re-selection are fulfilled, the UE shall perform cell re-selection as specified in 5.3.13.6. + +NOTE 3: For L2 U2N Remote UE in *RRC\_INACTIVE*, the cell (re)selection procedure as specified in TS 38.304 [20] and relay (re)selection procedure as specified in 5.8.15.3 are performed independently and it is up to UE implementation to select either a cell or a L2 U2N Relay UE. + +#### 5.3.13.4 Reception of the *RRResume* by the UE + +The UE shall: + +1> stop timer T319, if running; + +1> stop timer T319a, if running and consider SDT procedure is not ongoing; + +1> stop timer T380, if running; + +1> if T331 is running: + +2> stop timer T331; + +2> perform the actions as specified in 5.7.8.3; + +- 1> if the *RRCResume* includes the *fullConfig*: + - 2> perform the full configuration procedure as specified in 5.3.5.11; +- 1> else: + - 2> if the *RRCResume* does not include the *restoreMCG-SCells*: + - 3> release the MCG SCell(s) from the UE Inactive AS context, if stored; + - 2> if the *RRCResume* does not include the *restoreSCG*: + - 3> release the MR-DC related configurations (i.e., as specified in 5.3.5.10) from the UE Inactive AS context, if stored; + - 2> restore the *masterCellGroup*, *mrdc-SecondaryCellGroup*, if stored, and *pdcp-Config* from the UE Inactive AS context; + - 2> configure lower layers to consider the restored MCG and SCG SCell(s) (if any) to be in deactivated state; +- 1> discard the UE Inactive AS context; +- 1> store the used *nextHopChainingCount* value associated to the current $K_{gNB}$ ; +- 1> if *sdt-MAC-PHY-CG-Config* is configured: + - 2> instruct the MAC entity to stop the *cg-SDT-TimeAlignmentTimer*, if it is running; + - 2> instruct the MAC entity to start the *timeAlignmentTimer* associated with the PTAG, if it is not running; +- 1> if *srs-PosRRC-Inactive* is configured: + - 2> instruct the MAC entity to stop *inactivePosSRS-TimeAlignmentTimer*, if it is running; +- 1> if *srs-PosRRC-InactiveValidityAreaConfig* is configured: + - 2> instruct the MAC entity to stop *inactivePosSRS-ValidityAreaTAT*, if it is running; +- 1> release the *suspendConfig* except the *ran-NotificationAreaInfo*; +- 1> if the *RRCResume* includes the *masterCellGroup*: + - 2> perform the cell group configuration for the received *masterCellGroup* according to 5.3.5.5; +- 1> if the *RRCResume* includes the *mrdc-SecondaryCellGroup*: + - 2> if the received *mrdc-SecondaryCellGroup* is set to *nr-SCG*: + +- 3> perform the RRC reconfiguration according to 5.3.5.3 for the *RRCReconfiguration* message included in *nr-SCG*; +- 2> if the received *mrdc-SecondaryCellGroup* is set to *eutra-SCG*: + - 3> perform the RRC connection reconfiguration as specified in TS 36.331 [10], clause 5.3.5.3 for the *RRCConnectionReconfiguration* message included in *eutra-SCG*; +- 1> if the *RRCResume* includes the *radioBearerConfig*: + - 2> perform the radio bearer configuration according to 5.3.5.6; +- 1> if the *RRCResume* message includes the *sk-Counter*: + - 2> perform security key update procedure as specified in 5.3.5.7; +- 1> if the *RRCResume* message includes the *radioBearerConfig2*: + - 2> perform the radio bearer configuration according to 5.3.5.6; +- 1> if the *RRCResume* message includes the *needForGapsConfigNR*: + - 2> if *needForGapsConfigNR* is set to *setup*: + - 3> consider itself to be configured to provide the measurement gap requirement information of NR target bands; + - 2> else: + - 3> consider itself not to be configured to provide the measurement gap requirement information of NR target bands; +- 1> if the *RRCResume* message includes the *needForGapNCSG-ConfigNR*: + - 2> if *needForGapNCSG-ConfigNR* is set to *setup*: + - 3> consider itself to be configured to provide the measurement gap and NCSG requirement information of NR target bands; + - 2> else: + - 3> consider itself not to be configured to provide the measurement gap and NCSG requirement information of NR target bands; +- 1> if the *RRCResume* message includes the *needForGapNCSG-ConfigEUTRA*: + - 2> if *needForGapNCSG-ConfigEUTRA* is set to *setup*: + - 3> consider itself to be configured to provide the measurement gap and NCSG requirement information of E-UTRA target bands; + - 2> else: + +- 3> consider itself not to be configured to provide the measurement gap and NCSG requirement information of E-UTRA target bands; + - 1> if *idleInactiveReportAllowed* is not included in the *RRCResume* message: + - 2> for each application layer measurement configuration with *configforRRC-IdleInactive* set to *true*: + - 3> forward the *measConfigAppLayerId* and inform upper layers about the release of the application layer measurement configuration; + - 3> discard any application layer measurement reports which were not yet submitted to lower layers for transmission; + - 3> release the application layer measurement configuration in UE variables *VarAppLayerIdleConfig* and *VarAppLayerPLMN-ListConfig*; + - 3> consider itself not to be configured to send application layer measurement report for the *measConfigAppLayerId*; + - 1> if the *RRCResume* message includes the *appLayerMeasConfig*: + - 2> perform the application layer measurement configuration procedure as specified in 5.3.5.13d; + - 1> if the *RRCResume* message includes the *sl-L2RemoteUE-Config* (i.e. the UE is a L2 U2N Remote UE): + - 2> perform the L2 U2N Remote UE configuration procedure as specified in 5.3.5.16; + - 1> if the *RRCResume* message includes the *sl-ConfigDedicatedNR*: + - 2> perform the sidelink dedicated configuration procedure as specified in 5.3.5.14; + - 1> resume SRB2 (if suspended), SRB3 (if configured), SRB4 (if configured), all DRBs (that are suspended) and multicast MRBs (that are suspended); +- NOTE 1: If the SCG is deactivated, resuming SRB3 and all DRBs does not imply that PDCP or RRC PDUs can be transmitted or received on SCG RLC bearers. +- 1> if stored, discard the cell reselection priority information provided by the *cellReselectionPriorities* or inherited from another RAT; + - 1> stop timer T320, if running; + - 1> if the *RRCResume* message includes the *measConfig*: + - 2> perform the measurement configuration procedure as specified in 5.5.2; + - 1> resume measurements if suspended; + - 1> if T390 is running: + - 2> stop timer T390 for all access categories; + - 2> perform the actions as specified in 5.3.14.4; + +``` +1> if T302 is running: +2> stop timer T302; +2> perform the actions as specified in 5.3.14.4; +1> enter RRC_CONNECTED; +1> indicate to upper layers that the suspended RRC connection has been resumed; +1> stop the cell re-selection procedure; +1> stop relay reselection procedure if any for L2 U2N Remote UE; +1> consider the current cell to be the PCell; +1> set the content of the of RRCResumeComplete message as follows: +2> if the upper layer provides NAS PDU, set the dedicatedNAS-Message to include the information received from upper layers; +2> if upper layers provides a PLMN: +3> if the UE is either allowed or instructed to access the PLMN via a cell for which at least one CAG ID is broadcast: +4> set the selectedPLMN-Identity from the npn-IdentityInfoList; +3> else: +4> set the selectedPLMN-Identity to the PLMN selected by upper layers from the plmn-IdentityInfoList; +2> if the masterCellGroup contains the reportUplinkTxDirectCurrent: +3> include the uplinkTxDirectCurrentList for each MCG serving cell with UL; +3> include uplinkDirectCurrentBWP-SUL for each MCG serving cell configured with SUL carrier, if any, within the uplinkTxDirectCurrentList; +2> if the masterCellGroup contains the reportUplinkTxDirectCurrentTwoCarrier: +3> include in the uplinkTxDirectCurrentTwoCarrierList the list of uplink Tx DC locations for the configured uplink carrier aggregation in the MCG; +2> if the masterCellGroup contains the reportUplinkTxDirectCurrentMoreCarrier: +3> include in the uplinkTxDirectCurrentMoreCarrierList the list of uplink Tx DC locations for the configured uplink carrier aggregation in the MCG; +2> if the UE has idle/inactive measurement information concerning cells other than the PCell available in VarMeasIdleReport: +``` + +- 3> if the *idleModeMeasurementReq* is included in the *RRResume* message: + - 4> set the *measResultIdleEUTRA* in the *RRResumeComplete* message to the value of *measReportIdleEUTRA* in the *VarMeasIdleReport*, if available; + - 4> set the *measResultIdleNR* in the *RRResumeComplete* message to the value of *measReportIdleNR* in the *VarMeasIdleReport*, if available; + - 4> discard the *VarMeasIdleReport* upon successful delivery of the *RRResumeComplete* message is confirmed by lower layers; +- 3> else: + - 4> if the SIB1 contains *idleModeMeasurementsNR* and the UE has NR idle/inactive measurement information concerning cells other than the PCell available in *VarMeasIdleReport*; or + - 4> if the SIB1 contains *idleModeMeasurementsEUTRA* and the UE has E-UTRA idle/inactive measurement information available in *VarMeasIdleReport*: + - 5> include the *idleMeasAvailable*; +- 2> if the *RRResume* message includes *mrdc-SecondaryCellGroup* set to *eutra-SCG*: + - 3> include in the *eutra-SCG-Response* the E-UTRA *RRConnectionReconfigurationComplete* message in accordance with TS 36.331 [10] clause 5.3.5.3; +- 2> if the *RRResume* message includes *mrdc-SecondaryCellGroup* set to *nr-SCG*: + - 3> include in the *nr-SCG-Response* the SCG *RRReconfigurationComplete* message; +- 2> if the UE has logged measurements available for NR and if the RPLMN is included in *plmn-IdentityList* stored in *VarLogMeasReport*; or +- 2> if the UE has logged measurements available for NR and if the current registered SNPN is included in *snpn-ConfigIDList* stored in *VarLogMeasReport*: + - 3> include the *logMeasAvailable* in the *RRResumeComplete* message; + - 3> if Bluetooth measurement results are included in the logged measurements the UE has available for NR: + - 4> include the *logMeasAvailableBT* in the *RRResumeComplete* message; + - 3> if WLAN measurement results are included in the logged measurements the UE has available for NR: + - 4> include the *logMeasAvailableWLAN* in the *RRResumeComplete* message; +- 2> if the *sigLoggedMeasType* in *VarLogMeasReport* is included; or +- 2> if the UE is capable of reporting availability of signalling based logged MDT for inter-RAT (i.e. LTE to NR), and if the *sigLoggedMeasType* in *VarLogMeasReport* of TS 36.331 [10] is included: + +- 3> if T330 timer is running (associated to the logged measurement configuration for NR or for LTE): + - 4> set *sigLogMeasConfigAvailable* to *true* in the *RRCResumeComplete* message; +- 3> else: + - 4> if the UE has logged measurements: + - 5> set *sigLogMeasConfigAvailable* to *false* in the *RRCResumeComplete* message; +- 2> if the UE has connection establishment failure or connection resume failure information available in *VarConnEstFailReport* or *VarConnEstFailReportList* and if the RPLMN is equal to *plmn-Identity* stored in *VarConnEstFailReport* or in at least one of the entries of *VarConnEstFailReportList*; or +- 2> if the UE has connection establishment failure information or connection resume failure information available in *VarConnEstFailReport* or *VarConnEstFailReportList* and if the registered SNPN identity is equal to *snpn-identity* stored in *VarConnEstFailReport* or any entry of *VarConnEstFailReportList*: + - 3> include *connEstFailInfoAvailable* in the *RRCResumeComplete* message; +- 2> if the UE has radio link failure or handover failure information available in *VarRLF-Report* and if the RPLMN is included in *plmn-IdentityList* stored in *VarRLF-Report*; or +- 2> if the UE has radio link failure or handover failure information available in *VarRLF-Report* of TS 36.331 [10] and if the UE is capable of cross-RAT RLF reporting and if the RPLMN is included in *plmn-IdentityList* stored in *VarRLF-Report* of TS 36.331 [10]; or +- 2> if the UE has radio link failure or handover failure information available in *VarRLF-Report* and if the current registered SNPN are included in *snpn-IdentityList* stored in *VarRLF-Report*; or + - 3> include *rlf-InfoAvailable* in the *RRCResumeComplete* message; +- 2> if the UE has successful PSCell change or addition related information available in *VarSuccessPSCell-Report* and if the RPLMN is included in *plmn-IdentityList* stored in *VarSuccessPSCell-Report*; or +- 2> if the UE has successful PSCell change or addition information available in *VarSuccessPSCell-Report* and if the current registered SNPN is included in *snpn-IdentityList* stored in the *VarSuccessPSCell-Report*: + - 3> include *successPSCell-InfoAvailable* in the *RRCResumeComplete* message; +- 2> if the UE has successful handover information available in *VarSuccessHO-Report* and if the RPLMN is included in *plmn-IdentityList* stored in *VarSuccessHO-Report*; or +- 2> if the UE has successful handover information available in *VarSuccessHO-Report* and if the current registered SNPN is included in *snpn-IdentityList* stored in the *VarSuccessHO-Report*: + - 3> include *successHO-InfoAvailable* in the *RRCResumeComplete* message; + +- 2> if the UE supports storage of mobility history information and the UE has mobility history information available in *VarMobilityHistoryReport*: + - 3> include the *mobilityHistoryAvail* in the *RRResumeComplete* message; +- 2> if *speedStateReselectionPars* is configured in the *SIB2*: + - 3> include the *mobilityState* in the *RRResumeComplete* message and set it to the mobility state (as specified in TS 38.304 [20]) of the UE just prior to entering *RRC\_CONNECTED* state; +- 2> if the UE is configured with at least one application layer measurement with *configForRR-IdleInactive* set to *true*: + - 3> for each application layer measurement configuration with *configForRR-IdleInactive* set to *true*: + - 4> if the RPLMN is not included in *plmn-IdentityList* in *VarAppLayerPLMN-ListConfig*: + - 5> forward the *measConfigAppLayerId* and inform upper layers about the release of the application layer measurement configuration; + - 5> discard any application layer measurement reports which were not yet submitted to lower layers for transmission; + - 5> release the application layer measurement configuration in UE variables *VarAppLayerIdleConfig* and *VarAppLayerPLMN-ListConfig*; + - 5> consider itself not to be configured to send application layer measurement report for the *measConfigAppLayerId*; + - 3> if at least one stored application layer measurement configuration or application layer measurement report container has not been released: + - 4> include *measConfigReportAppLayerAvailable* in the *RRResumeComplete* message; +- 2> if the UE is configured to provide the measurement gap requirement information of NR target bands: + - 3> include the *NeedForGapsInfoNR* and set the contents as follows: + - 4> include *intraFreq-needForGap* and set the gap requirement information of intra-frequency measurement for each NR serving cell; + - 4> if *requestedTargetBandFilterNR* is configured, for each supported NR band that is also included in *requestedTargetBandFilterNR*, include an entry in *interFreq-needForGap* and set the gap requirement information for that band; otherwise, include an entry in *interFreq-needForGap* and set the corresponding gap requirement information for each supported NR band; + - 3> if the *needForInterruptionConfigNR* is enabled: + - 4> include the *needForInterruptionInfoNR* and set the contents as follows: + - 5> include *intraFreq-needForInterruption* with the same number of entries, and listed in the same order, as in *intraFreq-needForGap*; + +- 5> for each entry in *intraFreq-needForInterruption*, include *interruptionIndication* and set the interruption requirement information if the corresponding entry in *intraFreq-needForGap* is set to *no-gap*; + - 5> include *interFreq-needForInterruption* with the same number of entries, and listed in the same order, as in *interFreq-needForGap*; + - 5> for each entry in *interFreq-needForInterruption*, include *interruptionIndication* and set the interruption requirement information if the corresponding entry in *interFreq-needForGap* is set to *no-gap*; +- 2> if the UE is configured to provide the measurement gap and NCSG requirement information of NR target bands: + - 3> include the *NeedForGapNCSG-InfoNR* and set the contents as follows: + - 4> include *intraFreq-needForNCSG* and set the gap and NCSG requirement information of intra-frequency measurement for each NR serving cell; + - 4> if *requestedTargetBandFilterNCSG-NR* is configured: + - 5> for each supported NR band included in *requestedTargetBandFilterNCSG-NR*, include an entry in *interFreq-needForNCSG* and set the NCSG requirement information for that band; + - 4> else: + - 5> include an entry for each supported NR band in *interFreq-needForNCSG* and set the corresponding NCSG requirement information; +- 2> if the UE is configured to provide the measurement gap and NCSG requirement information of E-UTRA target bands: + - 3> include the *NeedForGapNCSG-InfoEUTRA* and set the contents as follows: + - 4> if *requestedTargetBandFilterNCSG-EUTRA* is configured: + - 5> for each supported E-UTRA band included in *requestedTargetBandFilterNCSG-EUTRA*, include an entry in *needForNCSG-EUTRA* and set the NCSG requirement information for that band; + - 4> else: + - 5> include an entry for each supported E-UTRA band in *needForNCSG-EUTRA* and set the corresponding NCSG requirement information; +- 2> if the SIB1 contains *musim-CapRestrictionAllowed* and the UE capability is restricted for MUSIM operation: + - 3> if supported, include the *musim-CapRestrictionInd* in the *RRCResumeComplete* message upon determining it has temporary capability restriction; +- 2> if the UE has flight path information available: + - 3> include *flightPathInfoAvailable*; + +1> submit the *RRCResumeComplete* message to lower layers for transmission; + +1> the procedure ends. + +NOTE 2: Network only configures at most one of *reportUplinkTxDirectCurrent*, *reportUplinkTxDirectCurrentTwoCarrier* or *reportUplinkTxDirectCurrentMoreCarrier* in one RRC message. + +#### 5.3.13.5 Handling of failure to resume RRC Connection + +The UE shall: + +1> if timer T319 expires: + +2> if the UE supports multiple CEF report: + +3> if the UE has connection establishment failure information or connection resume failure information available in *VarConnEstFailReport* and if the RPLMN is equal to *plmn-identity* stored in *VarConnEstFailReport*; and + +3> if the cell identity of current cell is not equal to the cell identity stored in *measResultFailedCell* in *VarConnEstFailReport* and if the *maxCEFReport-r17* has not been reached: + +4> append the *VarConnEstFailReport* as a new entry in the *VarConnEstFailReportList*; + +2> if the UE has connection establishment failure information or connection resume failure information available in *VarConnEstFailReport* and if the RPLMN is not equal to *plmn-identity* stored in *VarConnEstFailReport*; or + +2> if the cell identity of current cell is not equal to the cell identity stored in *measResultFailedCell* in *VarConnEstFailReport*: + +3> reset the *numberOfConnFail* to 0; + +2> if the UE has connection establishment failure information or connection resume failure information available in *VarConnEstFailReportList* and if the RPLMN is not equal to *plmn-identity* stored in any entry of *VarConnEstFailReportList*: + +3> clear the content included in *VarConnEstFailReportList*; + +2> clear the content included in *VarConnEstFailReport* except for the *numberOfConnFail*, if any; + +2> store the following connection resume failure information in the *VarConnEstFailReport* by setting its fields as follows: + +3> set the *plmn-Identity* to the PLMN selected by upper layers (see TS 24.501 [23]) from the PLMN(s) included in the *plmn-IdentityInfoList* in *SIB1*; + +3> set the *measResultFailedCell* to include the global cell identity, tracking area code, the cell level and SS/PBCH block level RSRP, and RSRQ, and SS/PBCH block indexes, of the failed cell based on the available SSB measurements collected up to the moment the UE detected connection resume failure; + +3> if available, set the *measResultNeighCells*, in order of decreasing ranking-criterion as used for cell re-selection, to include neighbouring cell measurements for at most the following number of neighbouring cells: 6 intra-frequency and 3 inter-frequency neighbours per frequency as well as 3 inter-RAT neighbours, per frequency/ set of frequencies per RAT and according to the following: + +4> for each neighbour cell included, include the optional fields that are available; + +NOTE: The UE includes the latest results of the available measurements as used for cell reselection evaluation, which are performed in accordance with the performance requirements as specified in TS 38.133 [14]. + +3> if available, set the *locationInfo* as in 5.3.3.7; + +3> set *perRAInfoList* to indicate the performed random access procedure related information as specified in 5.7.10.5; + +3> if *numberOfConnFail* is smaller than 8: + +4> increment the *numberOfConnFail* by 1; + +2> perform the actions upon going to RRC\_IDLE as specified in 5.3.11 with release cause 'RRC Resume failure'. + +1> else if upon receiving integrity check failure indication from lower layers while T319 is running: + +2> perform the actions upon going to RRC\_IDLE as specified in 5.3.11 with release cause 'RRC Resume failure'. + +1> else if indication from the MCG RLC that the maximum number of retransmissions has been reached is received while SDT procedure is ongoing; or + +1> if random access problem indication is received from MCG MAC while SDT procedure is ongoing; or + +1> if the lower layers indicate that *cg-SDT-TimeAlignmentTimer* or the *configuredGrantTimer* expired before receiving network response for the UL CG-SDT transmission with CCCH message while SDT procedure is ongoing; or + +1> if integrity check failure indication is received from lower layers while SDT procedure is ongoing; or + +1> if T319a expires: + +2> consider SDT procedure is not ongoing; + +2> perform the actions upon going to RRC\_IDLE as specified in 5.3.11 with release cause 'RRC Resume failure'. + +The UE may discard the connection resume failure or connection establishment failure information, i.e. release the UE variable *VarConnEstFailReport* and the UE variable *VarConnEstFailReportList*, 48 hours after the last connection resume failure is detected. + +The L2 U2N Relay UE either indicates to upper layers (to trigger PC5 unicast link release) or sends *NotificationMessageSidelink* message to the connected L2 U2N Remote UE(s) in accordance with 5.8.9.10. + +#### 5.3.13.6 Cell re-selection or cell selection or L2 U2N relay (re)selection while T390, T319 or T302 is running or SDT procedure is ongoing (UE in RRC\_INACTIVE) or SRS transmission in RRC\_INACTIVE is configured + +The UE shall: + +- 1> if cell reselection occurs while T319 or T302 is running or while SDT procedure is ongoing; or +- 1> if relay reselection occurs while T319 is running; or +- 1> if cell changes due to relay reselection while T302 is running: + - 2> perform the actions upon going to RRC\_IDLE as specified in 5.3.11 with release cause 'RRC Resume failure'; +- 1> else if cell selection or reselection occurs while T390 is running, or cell change due to relay selection or reselection occurs while T390 is running: + - 2> stop T390 for all access categories; + - 2> perform the actions as specified in 5.3.14.4. +- 1> else if cell reselection occurs when *srs-PosRRC-Inactive* is configured: + - 2> indicate to the lower layer to stop *inactivePosSRS-TimeAlignmentTimer*; + - 2> release the *srs-PosRRC-Inactive*. +- 1> else if cell reselection occurs when *srs-PosRRC-InactiveValidityAreaConfig* is configured and if the cell is not included in the *srs-PosConfigValidityArea*: + - 2> indicate to the lower layer to stop *inactivePosSRS-ValidityAreaTAT*; +- 1> else if cell reselection occurs when *srs-PosRRC-InactiveValidityAreaConfig* is configured and if the cell is included in the *srs-PosRRC-InactiveValidityAreaConfig*: + - 2> if *autonomousTA-AdjustmentEnabled* is configured; + - 3> indicate to the lower layer to update Timing Advance and stored RSRP. + +#### 5.3.13.7 Reception of the *RRCSsetup* by the UE + +The UE shall: + +- 1> perform the RRC connection setup procedure as specified in 5.3.3.4. + +#### 5.3.13.8 RNA update + +In RRC\_INACTIVE state, the UE shall: + +- 1> if T380 expires; or +- 1> if RNA Update is triggered at reception of SIB1, as specified in 5.2.2.4.2: + - 2> if T319 is not running and SDT procedure is not ongoing: + - 3> initiate RRC connection resume procedure in 5.3.13.2 with *resumeCause* set to *rna-Update*; +- 1> if barring is alleviated for Access Category '8' or Access Category '2', as specified in 5.3.14.4: + - 2> if upper layers do not request RRC the resumption of an RRC connection, and + - 2> if the variable *pendingRNA-Update* is set to *true*: + - 3> initiate RRC connection resume procedure in 5.3.13.2 with *resumeCause* value set to *rna-Update*. + +If the UE in RRC\_INACTIVE state fails to find a suitable cell and camps on the acceptable cell to obtain limited service as defined in TS 38.304 [20], the UE shall: + +- 1> perform the actions upon going to RRC\_IDLE as specified in 5.3.11 with release cause 'other'. + +NOTE: It is left to UE implementation how to behave when T380 expires while the UE is camped neither on a suitable nor on an acceptable cell. + +#### 5.3.13.9 Reception of the *RRRelease* by the UE + +The UE shall: + +- 1> perform the actions as specified in 5.3.8. + +#### 5.3.13.10 Reception of the *RRReject* by the UE + +The UE shall: + +- 1> perform the actions as specified in 5.3.15. + +#### 5.3.13.11 Inability to comply with *RRResume* + +The UE shall: + +- 1> if the UE is unable to comply with (part of) the configuration included in the *RRResume* message; + - 2> perform the actions upon going to RRC\_IDLE as specified in 5.3.11 with release cause 'RRC Resume failure'. + +NOTE 1: The UE may apply above failure handling also in case the *RRResume* message causes a protocol error for which the generic error handling as defined in 10 specifies that the UE shall ignore the message. + +NOTE 2: If the UE is configured (i.e., via SIB1) to send MUSIM temporary capability restriction indication, and if the UE supports MUSIM temporary capability restriction, the UE does not apply above failure handling in case the UE is unable to apply part of the configuration included in *RRResume* message due to UE temporary capability restriction for MUSIM operation. It is up to UE implementation how to apply *RRResume* message. If UE does not go to RRC\_IDLE in this case, UE still considers the received configuration in *RRResume* message as the current configuration as the baseline for delta configuration for future reconfigurations. For other cases, if the UE is unable to comply with part of the configuration, it does not apply any part of the configuration, i.e. there is no partial success/failure. + +#### 5.3.13.12 Inter RAT cell reselection + +Upon reselecting to an inter-RAT cell, the UE shall: + +1> perform the actions upon going to RRC\_IDLE as specified in 5.3.11, with release cause 'other'. + +### 5.3.14 Unified Access Control + +#### 5.3.14.1 General + +The purpose of this procedure is to perform access barring check for an access attempt associated with a given Access Category and one or more Access Identities upon request from upper layers according to TS 24.501 [23] or the RRC layer. This procedure does not apply to IAB-MT and NCR-MT. This procedure does not apply to L2 U2N Relay UE initiating RRC connection establishment or RRC connection resume upon reception of any message from a L2 U2N remote UE via SL-RLC0 or SL-RLC1 in accordance to 5.3.3.1a or 5.3.13.1a. + +After a PCell change in RRC\_CONNECTED the UE shall defer access barring checks until it has obtained *SIB1* (as specified in 5.2.2.2) from the target cell. + +#### 5.3.14.2 Initiation + +Upon initiation of the procedure, the UE shall: + +- 1> if timer T390 is running for the Access Category: + - 2> consider the access attempt as barred; +- 1> else if timer T302 is running and the Access Category is neither '2' nor '0': + - 2> consider the access attempt as barred; +- 1> else: + - 2> if the Access Category is '0': + - 3> consider the access attempt as allowed; + - 2> else: + +- 3> if *SIB1* includes *uac-BarringPerPLMN-List* that contains a *UAC-BarringPerPLMN* for the selected PLMN or SNPN: + - 4> if the procedure in 5.2.2.4.2 for a selected PLMN resulted in use of information in *npn-IdentityInfoList* and *UAC-BarringPerPLMN* has an entry with the *plmn-IdentityIndex* corresponding to used information in this list: + - 5> select the *UAC-BarringPerPLMN* entry with the *plmn-IdentityIndex* corresponding to used information in the *npn-IdentityInfoList*; + - 4> else: + - 5> select the *UAC-BarringPerPLMN* entry with the *plmn-IdentityIndex* corresponding to the selected PLMN and the *PLMN-IdentityInfo*, if any, or the selected SNPN and the *npn-IdentityInfoList*; +- 3> if any *UAC-BarringPerPLMN* entry is selected: + - 4> in the remainder of this procedure, use the selected *UAC-BarringPerPLMN* entry (i.e. presence or absence of access barring parameters in this entry) irrespective of the *uac-BarringForCommon* included in *SIB1*; +- 3> else if *SIB1* includes *uac-BarringForCommon*: + - 4> in the remainder of this procedure use the *uac-BarringForCommon* (i.e. presence or absence of these parameters) included in *SIB1*; +- 3> else: + - 4> consider the access attempt as allowed; +- 3> if *uac-BarringForCommon* is applicable or the *uac-ACBarringListType* indicates that *uac-ExplicitACBarringList* is used: + - 4> if the corresponding *UAC-BarringPerCatList* contains a *UAC-BarringPerCat* entry corresponding to the Access Category: + - 5> select the *UAC-BarringPerCat* entry; + - 5> if the *uac-BarringInfoSetList* contains a *UAC-BarringInfoSet* entry corresponding to the selected *uac-barringInfoSetIndex* in the *UAC-BarringPerCat*: + - 6> select the *UAC-BarringInfoSet* entry; + - 6> perform access barring check for the Access Category as specified in 5.3.14.5, using the selected *UAC-BarringInfoSet* as "UAC barring parameter"; + - 5> else: + - 6> consider the access attempt as allowed; + - 4> else: + - 5> consider the access attempt as allowed; + +``` +3> else if the uac-ACBarringListType indicates that uac-ImplicitACBarringList is used: +4> select the uac-BarringInfoSetIndex corresponding to the Access Category in the uac-ImplicitACBarringList; +4> if the uac-BarringInfoSetList contains the UAC-BarringInfoSet entry corresponding to the selected uac-BarringInfoSetIndex: +5> select the UAC-BarringInfoSet entry; +5> perform access barring check for the Access Category as specified in 5.3.14.5, using the selected UAC-BarringInfoSet as "UAC barring parameter"; +4> else: +5> consider the access attempt as allowed; +3> else: +4> consider the access attempt as allowed; +1> if the access barring check was requested by upper layers: +2> if the access attempt is considered as barred: +3> if timer T302 is running: +4> if timer T390 is running for Access Category '2': +5> inform the upper layer that access barring is applicable for all access categories except categories '0', upon which the procedure ends; +4> else +5> inform the upper layer that access barring is applicable for all access categories except categories '0' and '2', upon which the procedure ends; +3> else: +4> inform upper layers that the access attempt for the Access Category is barred, upon which the procedure ends; +2> else: +3> inform upper layers that the access attempt for the Access Category is allowed, upon which the procedure ends; +1> else: +2> the procedure ends. +``` + +#### 5.3.14.3 Void + +#### 5.3.14.4 T302, T390 expiry or stop (Barring alleviation) + +The UE shall: + +- 1> if timer T302 expires or is stopped: + - 2> for each Access Category for which T390 is not running: + - 3> consider the barring for this Access Category to be alleviated; +- 1> else if timer T390 corresponding to an Access Category other than '2' expires or is stopped, and if timer T302 is not running: + - 2> consider the barring for this Access Category to be alleviated; +- 1> else if timer T390 corresponding to the Access Category '2' expires or is stopped: + - 2> consider the barring for this Access Category to be alleviated; +- 1> when barring for an Access Category is considered being alleviated: + - 2> if the Access Category was informed to upper layers as barred: + - 3> inform upper layers about barring alleviation for the Access Category. + - 2> else if the Access Category is Access Category '0': + - 3> perform actions specified in 5.3.13.1d; + - 2> if barring is alleviated for Access Category '8'; or + - 2> if barring is alleviated for Access Category '2': + - 3> perform actions specified in 5.3.13.8; + +#### 5.3.14.5 Access barring check + +The UE shall: + +- 1> if one or more Access Identities equal to 1, 2, 11, 12, 13, 14, or 15 are indicated according to TS 24.501 [23], and +- 1> if for at least one of these Access Identities the corresponding bit in the *uac-BarringForAccessIdentity* contained in "UAC barring parameter" is set to *zero*: + +``` +2> consider the access attempt as allowed; +1> else: +2> if the establishment of the RRC connection is the result of release with redirect with mpsPriorityIndication (either in NR or E-UTRAN); and +2> if the bit corresponding to Access Identity 1 in the uac-BarringForAccessIdentity contained in the "UAC barring parameter" is set to zero: +3> consider the access attempt as allowed; +2> else if Access Identity 3 is indicated: +3> draw a random number 'rand' uniformly distributed in the range: $0 \leq \text{rand} < 1$ ; +3> if 'rand' is lower than the value indicated by uac-BarringFactorForAI3 included in "UAC barring parameter": +4> consider the access attempt as allowed; +3> else: +4> consider the access attempt as barred; +2> else: +3> draw a random number 'rand' uniformly distributed in the range: $0 \leq \text{rand} < 1$ ; +3> if 'rand' is lower than the value indicated by uac-BarringFactor included in "UAC barring parameter": +4> consider the access attempt as allowed; +3> else: +4> consider the access attempt as barred; +1> if the access attempt is considered as barred: +2> draw a random number 'rand' that is uniformly distributed in the range $0 \leq \text{rand} < 1$ ; +2> start timer T390 for the Access Category with the timer value calculated as follows, using the uac-BarringTime included in "UAC barring parameter": + +$$T390 = (0.7 + 0.6 * \text{rand}) * \text{uac-BarringTime}.$$ + +``` + +### 5.3.15 RRC connection reject + +#### 5.3.15.1 Initiation + +The UE initiates the procedure upon the reception of *RRReject* when the UE tries to establish or resume an RRC connection. + +#### 5.3.15.2 Reception of the *RRReject* by the UE + +The UE shall: + +- 1> stop timer T300, if running; +- 1> stop timer T319, if running; +- 1> stop timer T319a, if running and consider SDT procedure is not ongoing; +- 1> stop timer T302, if running; +- 1> reset MAC and release the default MAC Cell Group configuration; +- 1> if *waitTime* is configured in the *RRReject*: + - 2> start timer T302, with the timer value set to the *waitTime*; +- 1> if *RRReject* is received in response to a request from upper layers: + - 2> inform the upper layer that access barring is applicable for all access categories except categories '0' and '2'; +- 1> if *RRReject* is received in response to an *RRSetupRequest*: + - 2> inform upper layers about the failure to setup the RRC connection, upon which the procedure ends; +- 1> else if *RRReject* is received in response to an *RRResumeRequest* or an *RRResumeRequest1*: + - 2> if resume is triggered by upper layers: + - 3> inform upper layers about the failure to resume the RRC connection; + - 2> if resume is triggered due to an RNA update; or + - 2> if resume is triggered for SDT and T380 has expired: + - 3> set the variable *pendingRNA-Update* to *true*; + +- 2> discard the current $K_{\text{gNB}}$ key, the $K_{\text{RRCenc}}$ key, the $K_{\text{RRCint}}$ key, the $K_{\text{UPint}}$ key and the $K_{\text{UPenc}}$ key derived in accordance with 5.3.13.3; +- 2> if resume is triggered for SDT: + - 3> for SRB2, if it is resumed and for SRB1: + - 4> trigger the PDCP entity to perform SDU discard as specified in TS 38.323 [5]; + - 4> re-establish the RLC entity as specified in TS 38.322 [4]; + - 3> for each DRB that is not suspended: + - 4> indicate PDCP suspend to lower layers; + - 4> re-establish the RLC entity as specified in TS 38.322 [4]; +- 2> suspend SRB1 and the radio bearers configured for SDT, if any; +- 2> the procedure ends. + +Upon L2 U2N Relay UE receives *RRReject*, it either indicates to upper layers (to trigger PC5 unicast link release) or sends *NotificationMessageSidelink* message to the connected L2 U2N Remote UE(s) in accordance with 5.8.9.10. + +The RRC\_INACTIVE UE shall continue to monitor paging while the timer T302 is running. + +NOTE: If timer T331 is running, the UE continues to perform idle/inactive measurements according to 5.7.8. + +## 5.4 Inter-RAT mobility + +### 5.4.1 Introduction + +Network controlled inter-RAT mobility between NR and E-UTRA, where E-UTRA can be connected to either EPC or 5GC, and from NR to UTRA-FDD is supported. + +### 5.4.2 Handover to NR + +#### 5.4.2.1 General + +![Sequence diagram showing a successful handover to NR. The UE sends an RRCReconfiguration (sent via other RAT) message to the Network, and the Network responds with an RRCReconfigurationComplete message.](67c5b121b58d497a6de5addf4e7bd555_img.jpg) + +``` +sequenceDiagram + participant UE + participant Network + Note left of UE: + UE->>Network: RRCReconfiguration (sent via other RAT) + Network-->>UE: RRCReconfigurationComplete + Note right of Network: +``` + +Sequence diagram showing a successful handover to NR. The UE sends an RRCReconfiguration (sent via other RAT) message to the Network, and the Network responds with an RRCReconfigurationComplete message. + +Figure 5.4.2.1-1: Handover to NR, successful + +The purpose of this procedure is to, under the control of the network, transfer a connection between the UE and another Radio Access Network (e.g. E-UTRAN) to NR. + +The handover to NR procedure applies when SRBs, possibly in combination with DRBs, are established in another RAT. Handover from E-UTRA to NR applies only after integrity has been activated in E-UTRA. + +#### 5.4.2.2 Initiation + +The RAN using another RAT initiates the handover to NR procedure, in accordance with the specifications applicable for the other RAT, by sending the *RRCReconfiguration* message via the radio access technology from which the inter-RAT handover is performed. + +The network applies the procedure as follows: + +- to activate ciphering, possibly using NULL algorithm, if not yet activated in the other RAT; +- to re-establish SRBs and one or more DRBs; + +#### 5.4.2.3 Reception of the *RRCReconfiguration* by the UE + +The UE shall: + +- 1> apply the default L1 parameter values as specified in corresponding physical layer specifications except for the parameters for which values are provided in *SIB1*; +- 1> apply the default MAC Cell Group configuration as specified in 9.2.2; +- 1> perform RRC reconfiguration procedure as specified in 5.3.5; + +NOTE: If the UE is connected to 5GC of the source E-UTRA cell, the delta configuration for PDCP and SDAP can be used for intra-system inter-RAT handover. For other cases, source RAT configuration is not considered when the UE applies the reconfiguration message of target RAT. + +Editor's Note: FFS whether to capture the agreement that all LTE QoS configurations are released at handover to NR in LTE specification or NR specification. + +### 5.4.3 Mobility from NR + +#### 5.4.3.1 General + +![Sequence diagram for successful mobility from NR](df935fc9efbd024af4ba77e46bb0bb19_img.jpg) + +A sequence diagram showing the interaction between a UE and a Network for a successful mobility from NR. The UE sends a *MobilityFromNRCommand* message to the Network. The Network then responds with an *RRC connection re-establishment* message, indicated by a double line. + +Sequence diagram for successful mobility from NR + +Figure 5.4.3.1-1: Mobility from NR, successful + +![Sequence diagram for failed mobility from NR](985267cff5b5d65ce5c180ff2ef37118_img.jpg) + +A sequence diagram showing the interaction between a UE and a Network for a failed mobility from NR. The UE sends a *MobilityFromNRCommand* message to the Network. The Network then responds with an *RRC connection re-establishment* message, indicated by a double line. + +Sequence diagram for failed mobility from NR + +Figure 5.4.3.1-2: Mobility from NR, failure + +The purpose of this procedure is to move a UE in RRC\_CONNECTED to a cell using other RAT, e.g. E-UTRA, UTRA-FDD. The mobility from NR procedure covers the following type of mobility: + +- handover, i.e. the *MobilityFromNRCommand* message includes radio resources that have been allocated for the UE in the target cell; + +#### 5.4.3.2 Initiation + +The network initiates the mobility from NR procedure to a UE in RRC\_CONNECTED, possibly in response to a *MeasurementReport* or an *MCGFailureInformation* message, by sending a *MobilityFromNRCommand* message. The network applies the procedure as follows: + +- the procedure is initiated only when AS security has been activated, and SRB2 with at least one DRB or multicast MRB are setup and not suspended; +- the procedure is not initiated if any DAPS bearer is configured; + +#### 5.4.3.3 Reception of the *MobilityFromNRCommand* by the UE + +The UE shall: + +- 1> stop timer T310, if running; +- 1> stop timer T312, if running; +- 1> if T316 is running: + - 2> stop timer T316; + - 2> if the UE supports RLF-Report for fast MCG recovery procedure: + - 3> set the *elapsedTimeT316* in the *VarRLF-Report* to the value of the elapsed time of the timer T316; + - 3> set the *pSCellId* to the global cell identity of the PSCell, if available, otherwise to the physical cell identity and carrier frequency of the PSCell; + - 2> else: + - 3> clear the information included in *VarRLF-Report*, if any; +- 1> if T390 is running: + - 2> stop timer T390 for all access categories; + - 2> perform the actions as specified in 5.3.14.4; +- 1> inform upper layers about the release of all application layer measurement configurations; +- 1> discard any application layer measurement reports which were not yet submitted to lower layers for transmission; +- 1> if the *targetRAT-Type* is set to *eutra*: + - 2> consider inter-RAT mobility as initiated towards E-UTRA; + - 2> forward the *nas-SecurityParamFromNR* to the upper layers, if included; +- 1> else if the *targetRAT-Type* is set to *utra-fdd*: + - 2> consider inter-RAT mobility as initiated towards UTRA-FDD; + +- 2> forward the *nas-SecurityParamFromNR* to the upper layers, if included; +- 1> if *successHO-Config* is configured: + - 2> consider itself to be configured to provide the successful handover information for inter-RAT handover in accordance with 5.7.10.6; +- 1> else: + - 2> consider itself not to be configured to provide the successful handover information for inter-RAT handover. +- 1> access the target cell indicated in the inter-RAT message in accordance with the specifications of the target RAT. + +#### 5.4.3.4 Successful completion of the mobility from NR + +Upon successfully completing the handover, at the source side the UE shall: + +- 1> reset MAC; +- 1> stop all timers that are running except T325, T330 and T400; +- 1> release *ran-NotificationAreaInfo*, if stored; +- 1> release the AS security context including the $K_{RRCenc}$ key, the $K_{RRCint}$ key, the $K_{UPint}$ key and the $K_{UPenc}$ key, if stored; +- 1> release all radio resources, including release of the RLC entity and the MAC configuration; +- 1> release the associated PDCP entity and SDAP entity for all established RBs; + +NOTE : PDCP and SDAP configured by the source RAT prior to the handover that are reconfigured and re-used by target RAT when delta signalling (i.e., during inter-RAT intra-system handover when *fullConfig* is not present) is used, are not released as part of this procedure. + +- 1> if the UE was configured with *successHO-Config* when connected to the source PCell and the *targetRAT-Type* is set to *eutra*: + - 2> perform the actions for the successful handover report determination as specified in clause 5.7.10.6. +- 1> if the *targetRAT-Type* is set to *eutra* and the *nas-SecurityParamFromNR* is included: or +- 1> if the *targetRAT-Type* is set to *utra-fdd*: + - 2> indicate the release of the RRC connection to upper layers together with the release cause 'other'. + +#### 5.4.3.5 Mobility from NR failure + +The UE shall: + +- 1> if the UE does not succeed in establishing the connection to the target radio access technology: + - 2> if the *targetRAT-Type* in the received *MobilityFromNRCommand* is set to *eutra* and the UE supports Radio Link Failure Report for Inter-RAT MRO EUTRA: + - 3> store handover failure information in *VarRLF-Report* according to 5.3.10.5; + - 2> if *voiceFallbackIndication* is included in the *MobilityFromNRCommand* message; or + - 2> if the mobility from NR procedure is for emergency services fallback as specified in TS 23.502 [43]: + - 3> attempt to select an E-UTRA cell: + - 4> if a suitable E-UTRA cell is selected; or + - 4> if no suitable E-UTRA cell is available and an acceptable E-UTRA cell supporting emergency call is selected when the UE has an ongoing emergency call: + - 5> perform the actions upon going to RRC\_IDLE as specified in 5.3.11, with release cause 'RRC connection failure'; + - 4> else: + - 5> revert back to the configuration used in the source PCell; + - 5> initiate the connection re-establishment procedure as specified in clause 5.3.7; + +NOTE: It is left to UE implementation to determine whether the mobility from NR procedure is for emergency services fallback as specified in TS 23.502 [43]. + +- 2> else: + - 3> revert back to the configuration used in the source PCell; + - 3> initiate the connection re-establishment procedure as specified in clause 5.3.7; +- 1> else if the UE is unable to comply with any part of the configuration included in the *MobilityFromNRCommand* message; or +- 1> if there is a protocol error in the inter RAT information included in the *MobilityFromNRCommand* message, causing the UE to fail the procedure according to the specifications applicable for the target RAT: + - 2> if the *targetRAT-Type* in the received *MobilityFromNRCommand* is set to *eutra* and the UE supports Radio Link Failure Report for Inter-RAT MRO EUTRA: + - 3> store handover failure information in *VarRLF-Report* according to 5.3.10.5; + - 2> revert back to the configuration used in the source PCell; + - 2> initiate the connection re-establishment procedure as specified in clause 5.3.7. + +## 5.5 Measurements + +### 5.5.1 Introduction + +The network may configure an RRC\_CONNECTED UE to perform measurements. The network may configure the UE to report them in accordance with the measurement configuration or perform conditional reconfiguration evaluation in accordance with the conditional reconfiguration. The measurement configuration is provided by means of dedicated signalling i.e. using the *RRCReconfiguration* or *RRRCResume*. + +The network may configure the UE to perform the following types of measurements: + +- NR measurements; +- Inter-RAT measurements of E-UTRA frequencies; +- Inter-RAT measurements of UTRA-FDD frequencies; +- NR sidelink measurements of L2 U2N Relay UEs. + +The network may configure the UE to report the following measurement information based on SS/PBCH block(s): + +- Measurement results per SS/PBCH block; +- Measurement results per cell based on SS/PBCH block(s); +- SS/PBCH block(s) indexes. + +The network may configure the UE to report the following measurement information based on CSI-RS resources: + +- Measurement results per CSI-RS resource; +- Measurement results per cell based on CSI-RS resource(s); +- CSI-RS resource measurement identifiers. + +The network may configure the UE to perform the following types of measurements for NR sidelink and V2X sidelink: + +- CBR measurements. + +The network may configure the UE to report the following CLI measurement information based on SRS resources: + +- Measurement results per SRS resource; +- SRS resource(s) indexes. + +The network may configure the UE to report the following CLI measurement information based on CLI-RSSI resources: + +- Measurement results per CLI-RSSI resource; +- CLI-RSSI resource(s) indexes. + +The network may configure the UE to report the following Rx-Tx time difference measurement information based on CSI-RS for tracking or PRS: + +- UE Rx-Tx time difference measurement result. + +The measurement configuration includes the following parameters: + +**1. Measurement objects:** A list of objects on which the UE shall perform the measurements. + +- For intra-frequency and inter-frequency measurements a measurement object indicates the frequency/time location and subcarrier spacing of reference signals to be measured. Associated with this measurement object, the network may configure a list of cell specific offsets, a list of 'exclude-listed' cells and a list of 'allow-listed' cells. Exclude-listed cells are not applicable in event evaluation or measurement reporting. Allow-listed cells are the only ones applicable in event evaluation or measurement reporting. +- The *measObjectId* of the MO which corresponds to each serving cell is indicated by *servingCellMO* within the serving cell configuration. +- For inter-RAT E-UTRA measurements a measurement object is a single E-UTRA carrier frequency. Associated with this E-UTRA carrier frequency, the network can configure a list of cell specific offsets and a list of 'exclude-listed' cells. Exclude-listed cells are not applicable in event evaluation or measurement reporting. +- For inter-RAT UTRA-FDD measurements a measurement object is a set of cells on a single UTRA-FDD carrier frequency. +- For NR sidelink measurements of L2 U2N Relay UEs, a measurement object is a single NR sidelink frequency to be measured. +- For CBR measurement of NR sidelink communication, a measurement object is a set of transmission resource pool(s) on a single carrier frequency for NR sidelink communication. +- For CBR measurement of NR sidelink discovery, a measurement object is a set of discovery dedicated resource pool(s) or transmission resource pool(s) also used for NR sidelink discovery on a single carrier frequency for NR sidelink discovery. +- For CBR measurement of NR sidelink positioning, a measurement object is a set of positioning dedicated resource pool(s) or transmission resource pool(s) also used for NR sidelink positioning on a single carrier frequency for NR sidelink positioning. +- For CLI measurements a measurement object indicates the frequency/time location of SRS resources and/or CLI-RSSI resources, and subcarrier spacing of SRS resources to be measured. + +**2. Reporting configurations:** A list of reporting configurations where there can be one or multiple reporting configurations per measurement object. Each measurement reporting configuration consists of the following: + +- Reporting criterion: The criterion that triggers the UE to send a measurement report. This can either be periodical or a single event description. + +- RS type: The RS that the UE uses for beam and cell measurement results (SS/PBCH block or CSI-RS). +- Reporting format: The quantities per cell and per beam that the UE includes in the measurement report (e.g. RSRP) and other associated information such as the maximum number of cells and the maximum number beams per cell to report. + +In case of conditional reconfiguration, each configuration consists of the following: + +- Execution criteria: The criteria the UE uses for conditional reconfiguration execution. +- RS type: The RS that the UE uses for obtaining beam and cell measurement results (SS/PBCH block-based or CSI-RS-based), used for evaluating conditional reconfiguration execution condition. + +- 3. Measurement identities:** For measurement reporting, a list of measurement identities where each measurement identity links one measurement object with one reporting configuration. By configuring multiple measurement identities, it is possible to link more than one measurement object to the same reporting configuration, as well as to link more than one reporting configuration to the same measurement object. The measurement identity is also included in the measurement report that triggered the reporting, serving as a reference to the network. For conditional reconfiguration triggering, one measurement identity links to exactly one conditional reconfiguration trigger configuration. And up to 2 measurement identities can be linked to one conditional reconfiguration execution condition. +- 4. Quantity configurations:** The quantity configuration defines the measurement filtering configuration used for all event evaluation and related reporting, and for periodical reporting of that measurement. For NR measurements, the network may configure up to 2 quantity configurations with a reference in the NR measurement object to the configuration that is to be used. In each configuration, different filter coefficients can be configured for different measurement quantities, for different RS types, and for measurements per cell and per beam. +- 5. Measurement gaps:** Periods that the UE may use to perform measurements. +- 6. Effective measurement window:** Periods that the UE may use to perform inter RAT measurements. + +A UE in RRC\_CONNECTED maintains a measurement object list, a reporting configuration list, and a measurement identities list according to signalling and procedures in this specification. The measurement object list possibly includes NR measurement object(s), CLI measurement object(s), inter-RAT objects, and L2 U2N Relay objects. Similarly, the reporting configuration list includes NR, inter-RAT, and L2 U2N Relay reporting configurations. Any measurement object can be linked to any reporting configuration of the same RAT type. Some reporting configurations may not be linked to a measurement object. Likewise, some measurement objects may not be linked to a reporting configuration. + +The measurement procedures distinguish the following types of cells: + +1. The NR serving cell(s) – these are the SpCell and one or more SCells. +2. Listed cells – these are cells listed within the measurement object(s). +3. Detected cells – these are cells that are not listed within the measurement object(s) but are detected by the UE on the SSB frequency(ies) and subcarrier spacing(s) indicated by the measurement object(s). + +For NR measurement object(s), the UE measures and reports on the serving cell(s)/serving Relay UE (for L2 U2N Remote UE), listed cells and/or detected cells. For inter-RAT measurements object(s) of E-UTRA, the UE measures and reports on listed cells and detected cells and, for RSSI and channel occupancy measurements, the UE measures and + +reports on the configured resources on the indicated frequency. For inter-RAT measurements object(s) of UTRA-FDD, the UE measures and reports on listed cells. For CLI measurement object(s), the UE measures and reports on configured measurement resources (i.e. SRS resources and/or CLI-RSSI resources). For L2 U2N Relay object(s), the UE measures and reports on the serving NR cell(s), as well as the discovered L2 U2N Relay UEs. + +Whenever the procedural specification, other than contained in clause 5.5.2, refers to a field it concerns a field included in the *VarMeasConfig* unless explicitly stated otherwise i.e. only the measurement configuration procedure covers the direct UE action related to the received *measConfig*. + +In NR-DC, the UE may receive two independent *measConfig*: + +- a *measConfig*, associated with MCG, that is included in the *RRCReconfiguration* message received via SRB1; and +- a *measConfig*, associated with SCG, that is included in the *RRCReconfiguration* message received via SRB3, or, alternatively, included within a *RRCReconfiguration* message embedded in a *RRCReconfiguration* message received via SRB1. + +In this case, the UE maintains two independent *VarMeasConfig* and *VarMeasReportList*, one associated with each *measConfig*, and independently performs all the procedures in clause 5.5 for each *measConfig* and the associated *VarMeasConfig* and *VarMeasReportList*, unless explicitly stated otherwise. + +The configurations related to CBR measurements are only included in the *measConfig* associated with MCG. + +The configurations related to Rx-Tx time difference measurement are only included in the *measConfig* associated with MCG. + +### 5.5.2 Measurement configuration + +#### 5.5.2.1 General + +The network applies the procedure as follows: + +- to ensure that, whenever the UE has a *measConfig* associated with a CG, it includes a *measObject* for the SpCell and for each NR SCell of the CG to be measured; +- to configure at most one measurement identity across all CGs using a reporting configuration with the *reportType* set to *reportCGI*; +- to configure at most one measurement identity per the node hosting PDCP entity using a reporting configuration with the *ul-DelayValueConfig*; +- to configure at most one measurement identity per the node hosting PDCP entity using a reporting configuration with the *ul-ExcessDelayConfig*; +- to ensure that, in the *measConfig* associated with a CG: + - for all SSB based measurements there is at most one measurement object with the same *ssbFrequency*; + - an *smtc1* included in any measurement object with the same *ssbFrequency* has the same value and that an *smtc2* included in any measurement object with the same *ssbFrequency* has the same value and that an *smtc3list* included in any measurement object with the same *ssbFrequency* has the same value and that an *smtc4list* included in any measurement object with the same *ssbFrequency* has the same value; + +- to ensure that all measurement objects configured in this specification and in TS 36.331 [10] with the same *ssbFrequency* have the same *ssbSubcarrierSpacing*; +- to ensure that, if a measurement object associated with the MCG has the same *ssbFrequency* as a measurement object associated with the SCG: + - for that *ssbFrequency*, the measurement window according to the *smtc1* configured by the MCG includes the measurement window according to the *smtc1* configured by the SCG, or vice-versa, with an accuracy of the maximum receive timing difference specified in TS 38.133 [14]. + - if both measurement objects are used for RSSI measurements, bits in *measurementSlots* in both objects corresponding to the same slot are set to the same value. Also, the *endSymbol* is the same in both objects. +- to ensure that, if a measurement object has the same *ssbFrequency* as a measurement object configured in TS 36.331 [10]: + - for that *ssbFrequency*, the measurement window according to the *smtc* configured in TS 36.331 [10] includes the measurement window according to the *smtc1* configured in TS 38.331, or vice-versa, with an accuracy of the maximum receive timing difference specified in TS 38.133 [14]. + - if both measurement objects are used for RSSI measurements, bits in *measurementSlots* in both objects corresponding to the same slot are set to the same value. Also, the *endSymbol* is the same in both objects. +- when the UE is in NE-DC, NR-DC, or NR standalone, to configure at most one measurement identity across all CGs using a reporting configuration with the *reportType* set to *reportSFTD*; + +For CSI-RS resources, the network applies the procedure as follows: + +- to ensure that all CSI-RS resources configured in each measurement object have the same center frequency, $(startPRB + \text{floor}(nrofPRBs/2))$ +- to ensure that the total number of CSI-RS resources configured in each measurement object does not exceed the maximum number specified in TS 38.214 [19]. + +The UE shall: + +- 1> if the received *measConfig* includes the *measObjectToRemoveList*: + - 2> perform the measurement object removal procedure as specified in 5.5.2.4; +- 1> if the received *measConfig* includes the *measObjectToAddModList*: + - 2> perform the measurement object addition/modification procedure as specified in 5.5.2.5; +- 1> if the received *measConfig* includes the *reportConfigToRemoveList*: + - 2> perform the reporting configuration removal procedure as specified in 5.5.2.6; +- 1> if the received *measConfig* includes the *reportConfigToAddModList*: + - 2> perform the reporting configuration addition/modification procedure as specified in 5.5.2.7; + +- 1> if the received *measConfig* includes the *quantityConfig*: + - 2> perform the quantity configuration procedure as specified in 5.5.2.8; +- 1> if the received *measConfig* includes the *measIdToRemoveList*: + - 2> perform the measurement identity removal procedure as specified in 5.5.2.2; +- 1> if the received *measConfig* includes the *measIdToAddModList*: + - 2> perform the measurement identity addition/modification procedure as specified in 5.5.2.3; +- 1> if the received *measConfig* includes the *measGapConfig*: + - 2> perform the measurement gap configuration procedure as specified in 5.5.2.9; +- 1> if the received *measConfig* includes the *measGapSharingConfig*: + - 2> perform the measurement gap sharing configuration procedure as specified in 5.5.2.11; +- 1> if the received *measConfig* includes the *s-MeasureConfig*: + - 2> if *s-MeasureConfig* is set to *ssb-RSRP*, set parameter *ssb-RSRP* of *s-MeasureConfig* within *VarMeasConfig* to the threshold value of the RSRP indicated by the received value of *s-MeasureConfig* which is derived as specified in 6.3.2; + - 2> else, set parameter *csi-RSRP* of *s-MeasureConfig* within *VarMeasConfig* to the threshold value of the RSRP indicated by the received value of *s-MeasureConfig* which is derived as specified in 6.3.2. +- 1> if the received *measConfig* includes the *effectiveMeasWindowConfig*: + - 2> perform the effective measurement window configuration as specified in 5.5.2.12; + +#### 5.5.2.2 Measurement identity removal + +The UE shall: + +- 1> for each *measId* included in the received *measIdToRemoveList* that is part of the current UE configuration in *VarMeasConfig*: + - 2> remove the entry with the matching *measId* from the *measIdList* within the *VarMeasConfig*; + - 2> remove the measurement reporting entry for this *measId* from the *VarMeasReportList*, if included; + - 2> stop the periodical reporting timer or timer T321 or timer T322, whichever one is running, and reset the associated information (e.g. *timeToTrigger*) for this *measId*. + +2> if the *reportType* is set to *reportOnActivation* in the *reportConfig* associated with this *measId*: + +3> indicate to lower layer to disable the measurement reporting for fast unknown SCell activation. + +NOTE: The UE does not consider the message as erroneous if the *measIdToRemoveList* includes any *measId* value that is not part of the current UE configuration. + +#### 5.5.2.3 Measurement identity addition/modification + +The network applies the procedure as follows: + +- configure a *measId* only if the corresponding measurement object, the corresponding reporting configuration and the corresponding quantity configuration, are configured. + +The UE shall: + +1> for each *measId* included in the received *measIdToAddModList*: + +2> if an entry with the matching *measId* exists in the *measIdList* within the *VarMeasConfig*: + +3> replace the entry with the value received for this *measId*; + +2> else: + +3> add a new entry for this *measId* to the *measIdList* within the *VarMeasConfig*; + +2> remove the measurement reporting entry for this *measId* from the *VarMeasReportList*, if included; + +2> stop the periodical reporting timer or timer T321 or timer T322, whichever one is running, and reset the associated information (e.g. *timeToTrigger*) for this *measId*; + +NOTE 1: If the *measId* associated with *reportConfig* for conditional reconfiguration is modified, the conditions are considered to be not fulfilled as specified in 5.3.5.13.4. + +2> if the *reportType* is set to *reportCGI* in the *reportConfig* associated with this *measId*: + +3> if the *measObject* associated with this *measId* concerns E-UTRA: + +4> if the *useAutonomousGaps* is included in the *reportConfig* associated with this *measId*: + +5> start timer T321 with the timer value set to 200 ms for this *measId*; + +4> else: + +5> start timer T321 with the timer value set to 1 second for this *measId*; + +3> if the *measObject* associated with this *measId* concerns NR: + +4> if the *measObject* associated with this *measId* concerns FR1: + +5> if the *useAutonomousGaps* is included in the *reportConfig* associated with this *measId*: + +6> if the UE is an (e)RedCap UE with 1 Rx branch + +7> start timer T321 with the timer value set to 3 seconds for this *measId*; + +6> else + +7> start timer T321 with the timer value set to 2 seconds for this *measId*; + +5> else: + +6> start timer T321 with the timer value set to 2 seconds for this *measId*; + +4> if the *measObject* associated with this *measId* concerns FR2: + +5> if the *useAutonomousGaps* is included in the *reportConfig* associated with this *measId*: + +6> if the UE is a RedCap UE with 1 Rx branch + +7> start timer T321 with the timer value set to 6 seconds for this *measId*; + +6> else + +7> start timer T321 with the timer value set to 5 seconds for this *measId*; + +5> else: + +6> start timer T321 with the timer value set to 16 seconds for this *measId*. + +2> if the *reportType* is set to *reportSFTD* in the *reportConfigNR* associated with this *measId* and the *drx-SFTD-NeighMeas* is included: + +3> if the *measObject* associated with this *measId* concerns FR1: + +4> start timer T322 with the timer value set to 3 seconds for this *measId*; + +3> if the *measObject* associated with this *measId* concerns FR2: + +4> start timer T322 with the timer value set to 24 seconds for this *measId*. + +2> if the *reportType* is set to *reportOnActivation* in the *reportConfig* associated with this *measId*: + +3> indicate to lower layer to enable the measurement reporting for fast unknown SCell activation. + +#### 5.5.2.4 Measurement object removal + +The UE shall: + +- 1> for each *measObjectId* included in the received *measObjectToRemoveList* that is part of *measObjectList* in *VarMeasConfig*: + - 2> remove the entry with the matching *measObjectId* from the *measObjectList* within the *VarMeasConfig*; + - 2> remove all *measId* associated with this *measObjectId* from the *measIdList* within the *VarMeasConfig*, if any; + - 2> if a *measId* is removed from the *measIdList*: + - 3> remove the measurement reporting entry for this *measId* from the *VarMeasReportList*, if included; + - 3> stop the periodical reporting timer or timer T321 or timer T322, whichever is running, and reset the associated information (e.g. *timeToTrigger*) for this *measId*. + +NOTE: The UE does not consider the message as erroneous if the *measObjectToRemoveList* includes any *measObjectId* value that is not part of the current UE configuration. + +#### 5.5.2.5 Measurement object addition/modification + +The UE shall: + +- 1> for each *measObjectId* included in the received *measObjectToAddModList*: + - 2> if an entry with the matching *measObjectId* exists in the *measObjectList* within the *VarMeasConfig*, for this entry: + - 3> reconfigure the entry with the value received for this *measObject*, except for the fields *cellsToAddModList*, *excludedCellsToAddModList*, *allowedCellsToAddModList*, *cellsToRemoveList*, *excludedCellsToRemoveList*, *allowedCellsToRemoveList*, *tx-PoolMeasToRemoveList*, *tx-PoolMeasToAddModList*, *ssb-PositionQCL-CellsToRemoveList*, *ssb-PositionQCL-CellsToAddModList*, *cca-CellsToRemoveList*, and *cca-CellsToAddModList*; + - 3> if the received *measObject* includes the *cellsToRemoveList*: + - 4> for each *physCellId* included in the *cellsToRemoveList*: + - 5> remove the entry with the matching *physCellId* from the *cellsToAddModList*; + - 3> if the received *measObject* includes the *cellsToAddModList*: + - 4> for each *physCellId* value included in the *cellsToAddModList*: + - 5> if an entry with the matching *physCellId* exists in the *cellsToAddModList*: + - 6> replace the entry with the value received for this *physCellId*; + +5> else: + +6> add a new entry for the received *physCellId* to the *cellsToAddModList*; + +3> if the received *measObject* includes the *excludedCellsToRemoveList*: + +4> for each *pci-RangeIndex* included in the *excludedCellsToRemoveList*: + +5> remove the entry with the matching *pci-RangeIndex* from the *excludedCellsToAddModList*; + +NOTE 1: For each *pci-RangeIndex* included in the *excludedCellsToRemoveList* that concerns overlapping ranges of cells, a cell is removed from the exclude-list of cells only if all PCI ranges containing it are removed. + +3> if the received *measObject* includes the *excludedCellsToAddModList*: + +4> for each *pci-RangeIndex* included in the *excludedCellsToAddModList*: + +5> if an entry with the matching *pci-RangeIndex* is included in the *excludedCellsToAddModList*: + +6> replace the entry with the value received for this *pci-RangeIndex*; + +5> else: + +6> add a new entry for the received *pci-RangeIndex* to the *excludedCellsToAddModList*; + +3> if the received *measObject* includes the *allowedCellsToRemoveList*: + +4> for each *pci-RangeIndex* included in the *allowedCellsToRemoveList*: + +5> remove the entry with the matching *pci-RangeIndex* from the *allowedCellsToAddModList*; + +NOTE 2: For each *pci-RangeIndex* included in the *allowedCellsToRemoveList* that concerns overlapping ranges of cells, a cell is removed from the allow-list of cells only if all PCI ranges containing it are removed. + +3> if the received *measObject* includes the *allowedCellsToAddModList*: + +4> for each *pci-RangeIndex* included in the *allowedCellsToAddModList*: + +5> if an entry with the matching *pci-RangeIndex* is included in the *allowedCellsToAddModList*: + +6> replace the entry with the value received for this *pci-RangeIndex*; + +5> else: + +- 6> add a new entry for the received *pci-RangeIndex* to the *allowedCellsToAddModList* +- 3> for each *measId* associated with this *measObjectId* in the *measIdList* within the *VarMeasConfig*, if any: + - 4> if the UE does not support Uplink PDCP delay measurements upon MO update; or + - 4> if the UE supports Uplink PDCP delay measurements upon MO update and if *ul-DelayValueConfig* or *ul-ExcessDelayConfig* is not configured for the associated *reportConfig*: + - 5> remove the measurement reporting entry for this *measId* from the *VarMeasReportList*, if included; + - 5> stop the periodical reporting timer or timer T321 or timer T322, whichever one is running, and reset the associated information (e.g. *timeToTrigger*) for this *measId*; +- 3> if the received *measObject* includes the *tx-PoolMeasToRemoveList*: + - 4> for each transmission resource pool indicated in *tx-PoolMeasToRemoveList*: + - 5> remove the entry with the matching identity of the transmission resource pool from the *tx-PoolMeasToAddModList*; +- 3> if the received *measObject* includes the *tx-PoolMeasToAddModList*: + - 4> for each transmission resource pool indicated in *tx-PoolMeasToAddModList*: + - 5> if an entry with the matching identity of the transmission resource pool exists in the *tx-PoolMeasToAddModList*: + - 6> replace the entry with the value received for this transmission resource pool; + - 5> else: + - 6> add a new entry for the received identity of the transmission resource pool to the *tx-PoolMeasToAddModList*; +- 3> if the received *measObject* includes the *ssb-PositionQCL-CellsToRemoveList*: + - 4> for each *physCellId* included in the *ssb-PositionQCL-CellsToRemoveList*: + - 5> remove the entry with the matching *physCellId* from the *ssb-PositionQCL-CellsToAddModList*; +- 3> if the received *measObject* includes the *ssb-PositionQCL-CellsToAddModList*: + - 4> for each *physCellId* included in the *ssb-PositionQCL-CellsToAddModList*: + - 5> if an entry with the matching *physCellId* exists in the *ssb-PositionQCL-CellsToAddModList*: + +- 6> replace the entry with the value received for this *physCellId*; +- 5> else: + - 6> add a new entry for the received *physCellId* to the *ssb-PositionQCL-CellsToAddModList*; +- 3> if the received *measObject* includes the *cca-CellsToRemoveList*: + - 4> for each *physCellId* included in the *cca-CellsToRemoveList*: + - 5> remove the entry with the matching *physCellId* from the *cca-CellsToAddModList*; +- 3> if the received *measObject* includes the *cca-CellsToAddModList*: + - 4> for each *physCellId* included in the *cca-CellsToAddModList*: + - 5> if an entry with the matching *physCellId* exists in the *cca-CellsToAddModList*: + - 6> replace the entry with the value received for this *physCellId*; + - 5> else: + - 6> add a new entry for the received *physCellId* to the *cca-CellsToAddModList*; +- 2> else: + - 3> add a new entry for the received *measObject* to the *measObjectList* within *VarMeasConfig*. + +#### 5.5.2.6 Reporting configuration removal + +The UE shall: + +- 1> for each *reportConfigId* included in the received *reportConfigToRemoveList* that is part of the current UE configuration in *VarMeasConfig*: + - 2> remove the entry with the matching *reportConfigId* from the *reportConfigList* within the *VarMeasConfig*; + - 2> remove all *measId* associated with the *reportConfigId* from the *measIdList* within the *VarMeasConfig*, if any; + - 2> if a *measId* is removed from the *measIdList*: + - 3> remove the measurement reporting entry for this *measId* from the *VarMeasReportList*, if included; + - 3> stop the periodical reporting timer or timer T321 or timer T322, whichever one is running, and reset the associated information (e.g. *timeToTrigger*) for this *measId*. + +NOTE: The UE does not consider the message as erroneous if the *reportConfigToRemoveList* includes any *reportConfigId* value that is not part of the current UE configuration. + +#### 5.5.2.7 Reporting configuration addition/modification + +The UE shall: + +- 1> for each *reportConfigId* included in the received *reportConfigToAddModList*: + - 2> if an entry with the matching *reportConfigId* exists in the *reportConfigList* within the *VarMeasConfig*, for this entry: + - 3> reconfigure the entry with the value received for this *reportConfig*; + - 3> for each *measId* associated with this *reportConfigId* included in the *measIdList* within the *VarMeasConfig*, if any: + - 4> remove the measurement reporting entry for this *measId* from the *VarMeasReportList*, if included; + - 4> stop the periodical reporting timer or timer T321 or timer T322, whichever one is running, and reset the associated information (e.g. *timeToTrigger*) for this *measId*; + - 2> else: + - 3> add a new entry for the received *reportConfig* to the *reportConfigList* within the *VarMeasConfig*. + +#### 5.5.2.8 Quantity configuration + +The UE shall: + +- 1> for each RAT for which the received *quantityConfig* includes parameter(s): + - 2> set the corresponding parameter(s) in *quantityConfig* within *VarMeasConfig* to the value of the received *quantityConfig* parameter(s); +- 1> for each *measId* included in the *measIdList* within *VarMeasConfig*: + - 2> remove the measurement reporting entry for this *measId* from the *VarMeasReportList*, if included; + - 2> stop the periodical reporting timer or timer T321 or timer T322, whichever one is running, and reset the associated information (e.g. *timeToTrigger*) for this *measId*. + +#### 5.5.2.9 Measurement gap configuration + +The UE shall: + +- 1> if *gapFR1* is set to *setup*: + +2> if an FR1 measurement gap configuration configured by *gapFR1* is already setup, release the FR1 measurement gap configuration; + +2> setup the FR1 measurement gap configuration indicated by the *gapFR1* in accordance with the received *gapOffset*, i.e., the first subframe of each gap occurs at an SFN and subframe meeting the following condition: + +SFN mod $T = \text{FLOOR}(\text{gapOffset}/10)$ ; + +subframe = *gapOffset* mod 10; + +with $T = \text{MGRP}/10$ as defined in TS 38.133 [14]; + +2> apply the specified timing advance *mgta* to the gap occurrences calculated above (i.e. the UE starts the measurement *mgta* ms before the gap subframe occurrences); + +1> else if *gapFR1* is set to *release*: + +2> release the FR1 measurement gap configuration configured by *gapFR1*; + +1> if *gapFR2* is set to *setup*: + +2> if an FR2 measurement gap configuration configured by *gapFR2* is already setup, release the FR2 measurement gap configuration; + +2> setup the FR2 measurement gap configuration indicated by the *gapFR2* in accordance with the received *gapOffset*, i.e., the first subframe of each gap occurs at an SFN and subframe meeting the following condition: + +SFN mod $T = \text{FLOOR}(\text{gapOffset}/10)$ ; + +subframe = *gapOffset* mod 10; + +with $T = \text{MGRP}/10$ as defined in TS 38.133 [14]; + +2> apply the specified timing advance *mgta* to the gap occurrences calculated above (i.e. the UE starts the measurement *mgta* ms before the gap subframe occurrences); + +1> else if *gapFR2* is set to *release*: + +2> release the FR2 measurement gap configuration configured by *gapFR2*; + +1> if *gapUE* is set to *setup*: + +2> if a per UE measurement gap configuration configured by *gapUE* is already setup, release the per UE measurement gap configuration; + +2> setup the per UE measurement gap configuration indicated by the *gapUE* in accordance with the received *gapOffset*, i.e., the first subframe of each gap occurs at an SFN and subframe meeting the following condition: + +SFN mod $T = \text{FLOOR}(\text{gapOffset}/10)$ ; + +subframe = *gapOffset* mod 10; + +with $T = \text{MGRP}/10$ as defined in TS 38.133 [14]; + +2> apply the specified timing advance *mgta* to the gap occurrences calculated above (i.e. the UE starts the measurement *mgta* ms before the gap subframe occurrences); + +1> else if *gapUE* is set to *release*: + +2> release the per UE measurement gap configuration configured by *gapUE*. + +1> for each *measGapId* included in the received *gapToReleaseList*: + +2> release the measurement gap configuration associated with the *measGapId*; + +1> for each *measPosPreConfigGapId* included in the received *posMeasGapPreConfigToReleaseList*: + +2> release the measurement gap configuration associated with the *measPosPreConfigGapId*; + +1> for each *GapConfig* received in *gapToAddModList*: + +2> setup measurement gap configuration indicated by the *GapConfig* in accordance with the received *gapOffset*, i.e., the first subframe of each gap occurs at an SFN and subframe meeting the following condition: + +SFN mod $T = \text{FLOOR}(\text{gapOffset}/10)$ ; + +subframe = *gapOffset* mod 10; + +with $T = \text{MGRP}/10$ as defined in TS 38.133 [14]; + +2> apply the specified timing advance *mgta* to the gap occurrences calculated above (i.e. the UE starts the measurement *mgta* ms before the gap subframe occurrences); + +2> apply the measurement gap as per UE measurement gap, FR1 measurement gap, or FR2 measurement gap according to the *gapType* indicated by the *GapConfig*; + +2> associate the measurement gap with the *measGapId* indicated by the *GapConfig*; + +2> if *gapSharing* in the *GapConfig* is present: + +3> setup the gap sharing configuration for the measurement gap in accordance with the received *gapSharing* as defined in TS 38.133 [14]; + +2> else: + +3> release the gap sharing configuration (if configured) for the measurement gap; + +1> for each *PosGapConfig* received in *PosMeasGapPreConfigToAddModList*: + +- 2> if a measurement gap configuration associated with the *measPosPreConfigGapId* indicated by the *PosGapConfig* is already setup: + - 3> release the measurement gap configuration; +- 2> setup measurement gap configuration indicated by the *PosGapConfig* in accordance with the received *gapOffset*, i.e., the first subframe of each gap occurs at an SFN and subframe meeting the following condition: + - SFN mod $T = \text{FLOOR}(\text{gapOffset}/10)$ ; + - subframe = $\text{gapOffset} \bmod 10$ ; + - with $T = \text{MGRP}/10$ as defined in TS 38.133 [14]; +- 2> apply the specified timing advance *mgta* to the gap occurrences calculated above (i.e. the UE starts the measurement *mgta* ms before the gap subframe occurrences); +- 2> configure the measurement gap as indicated by *gapType*; +- 1> for each FR1, FR2, and per UE measurement gap that is setup: + - 2> if the measurement gap is configured by *GapConfig* and *preConfigInd-r17* in the corresponding *GapConfig* is present: + - 3> determine whether the measurement gap is activated or not according to TS 38.133 [14]; + - 2> else if the measurement gap is configured by *PosGapConfig*: + - 3> consider the measurement gap to be deactivated; + - 2> else: + - 3> consider the measurement gap to be activated. + +NOTE 1: For FR2 gap configuration with synchronous CA, for the UE in NE-DC or NR-DC, the SFN and subframe of the serving cell indicated by the *refServCellIndicator* is used in the gap calculation. Otherwise, the SFN and subframe of a serving cell on FR2 frequency is used in the gap calculation + +NOTE 2: For FR1 gap or per UE gap configuration, for the UE in NE-DC or NR-DC, the SFN and subframe of the serving cell indicated by the *refServCellIndicator* is used in the gap calculation. Otherwise, the SFN and subframe of the PCell is used in the gap calculation. + +NOTE 3: For FR2 gap configuration with asynchronous CA, for the UE in NE-DC or NR-DC, the SFN and subframe of the serving cell indicated by the *refServCellIndicator* and *refFR2ServCellAsyncCA* is used in the gap calculation. Otherwise, the SFN and subframe of a serving cell on FR2 frequency indicated by the *refFR2ServCellAsyncCA* is used in the gap calculation + +#### 5.5.2.10 Reference signal measurement timing configuration + +The UE shall setup the first SS/PBCH block measurement timing configuration (SMTC) in accordance with the received *periodicityAndOffset* parameter (providing *Periodicity* and *Offset* value for the following condition) in the *smtc1* configuration. The first subframe of each SMTC occasion occurs at an SFN and subframe of the NR SpCell meeting the following condition: + +SFN mod $T = (\text{FLOOR}(\text{Offset}/10));$ + +if the *Periodicity* is larger than *sf5*: + +subframe = *Offset* mod 10; + +else: + +subframe = *Offset* or (*Offset* +5); + +with $T = \text{CEIL}(\text{Periodicity}/10).$ + +If *smtc2* is present, for cells indicated in the *pci-List* parameter in *smtc2* in the same *MeasObjectNR*, the UE shall setup an additional SS/PBCH block measurement timing configuration (SMTC) in accordance with the received *periodicity* parameter in the *smtc2* configuration and use the *Offset* (derived from parameter *periodicityAndOffset*) and *duration* parameter from the *smtc1* configuration. The first subframe of each SMTC occasion occurs at an SFN and subframe of the NR SpCell meeting the above condition. + +If *smtc2-LP* is present, for cells indicated in the *pci-List* parameter in *smtc2-LP* in the same frequency (for intra frequency cell reselection) or different frequency (for inter frequency cell reselection), the UE shall setup an additional SS/PBCH block measurement timing configuration (SMTC) in accordance with the received *periodicity* parameter in the *smtc2-LP* configuration and use the *Offset* (derived from parameter *periodicityAndOffset*) and *duration* parameter from the *smtc* configuration for that frequency. The first subframe of each SMTC occasion occurs at an SFN and subframe of the NR SpCell or serving cell (for cell reselection) meeting the above condition. + +If *smtc3list* is present, for cells indicated in the *pci-List* parameter in each *SSB-MTC3* element of the list in the same *MeasObjectNR*, the IAB-MT shall setup an additional SS block measurement timing configuration in accordance with the received *periodicityAndOffset* parameter (using same condition as *smtc1* to identify the SFN and the subframe for SMTC occasion) in each *SSB-MTC3* configuration and use the *duration* and *ssb-ToMeasure* parameters from each *SSB-MTC3* configuration. + +If *smtc4list* is present, for cells indicated in the *pci-List* parameter in each *SSB-MTC4* element of the list in the same *MeasObjectNR*, the UE shall setup an additional SS/PBCH block measurement timing configuration (SMTC) in accordance with the received *offset* parameter in each *SSB-MTC4* configuration and use the *duration* parameter and *periodicity* (derived from parameter *periodicityAndOffset*) from the *smtc1* configuration. The first subframe of each SMTC occasion occurs at an SFN and subframe of the NR SpCell meeting the above condition. + +On the indicated *ssbFrequency*, the UE shall not consider SS/PBCH block transmission in subframes outside the SMTC occasion for RRM measurements based on SS/PBCH blocks and for RRM measurements based on CSI-RS except for SFTD measurement (see TS 38.133 [14], clause 9.3.8). + +##### 5.5.2.10a RSSI measurement timing configuration + +The UE shall setup the RSSI measurement timing configuration (RMTC) in accordance with the received *rmtc-Periodicity* and, if configured, with *rmtc-SubframeOffset* i.e. the first symbol of each RMTC occasion occurs at first symbol of an SFN and subframe of the NR SpCell meeting the following condition: + +$SFN \bmod T = \text{FLOOR}(rmtc-SubframeOffset/10);$ + +$subframe = rmtc-SubframeOffset \bmod 10;$ + +with $T = rmtc-Periodicity/10;$ + +On the frequency configured by *rmtc-Frequency*, the UE shall not consider RSSI measurements outside the configured RMTC occasion which lasts for *measDurationSymbols* for RSSI and channel occupancy measurements. + +The UE derives the RSSI measurement duration from a combination of *measDurationSymbols* and *ref-SCS-CP*. At least for RSSI measurement confined within the active DL BWP, the UE performs RSSI measurement using the numerology of the active DL BWP during the derived measurement duration. Otherwise, the numerology used by the UE for measurements is up to UE implementation. If configured, the UE performs RSSI measurements on a bandwidth in accordance with the received *rmtc-Bandwidth*. If configured, the UE performs RSSI measurements according to the TCI state configured by *tci-StateId* in the reference BWP configured by *ref-BWPId* of the reference serving cell configured by *ref-ServCellId* (see TS 38.133 [14], clause 9.2A.7 and clause 9.3A.8). If the UE has no serving cell in FR2-2 and configured with inter-frequency RSSI measurement in FR2-2, it is up to the UE implementation how to determine the spatial domain filter for the inter-frequency RSSI measurement in FR2-2. + +#### 5.5.2.11 Measurement gap sharing configuration + +The UE shall: + +- 1> if *gapSharingFR1* is set to *setup*: + - 2> if an FR1 measurement gap sharing configuration configured by *gapSharingFR1* is already setup: + - 3> release the FR1 measurement gap sharing configuration configured by *gapSharingFR1*; + - 2> setup the FR1 measurement gap sharing configuration indicated by the *measGapSharingConfig* in accordance with the received *gapSharingFR1* as defined in TS 38.133 [14]; +- 1> else if *gapSharingFR1* is set to *release*: + - 2> release the FR1 measurement gap sharing configuration configured by *gapSharingFR1*; +- 1> if *gapSharingFR2* is set to *setup*: + - 2> if an FR2 measurement gap sharing configuration configured by *gapSharingFR2* is already setup: + - 3> release the FR2 measurement gap sharing configuration configured by *gapSharingFR2*; + +- 2> setup the FR2 measurement gap sharing configuration indicated by the *measGapSharingConfig* in accordance with the received *gapSharingFR2* as defined in TS 38.133 [14]; +- 1> else if *gapSharingFR2* is set to *release*: + - 2> release the FR2 measurement gap sharing configuration configured by *gapSharingFR2*. +- 1> if *gapSharingUE* is set to *setup*: + - 2> if a per UE measurement gap sharing configuration configured by *gapSharingUE* is already setup: + - 3> release the per UE measurement gap sharing configuration configured by *gapSharingUE*; + - 2> setup the per UE measurement gap sharing configuration indicated by the *measGapSharingConfig* in accordance with the received *gapSharingUE* as defined in TS 38.133 [14]; +- 1> else if *gapSharingUE* is set to *release*: + - 2> release the per UE measurement gap sharing configuration configured by *gapSharingUE*. + +#### 5.5.2.12 Effective measurement window configuration + +The UE shall: + +- 1> if *effectiveMeasWindowConfig* is set to *setup*: + - 2> if an effective measurement window configuration is already setup: + - 3> release the effective measurement window configuration; + - 2> setup an effective measurement window configuration indicated by the *effectiveMeasWindowConfig* in accordance with the received *windowOffsetPeriodicity* (providing *periodicity* and *offset* for the following condition), i.e., the first subframe of each window occurs at an SFN and subframe meeting the following condition: +SFN mod $T = \text{FLOOR}(\text{offset}/10)$ ; +subframe = *offset* mod 10; +with $T = \text{periodicity}/10$ ; +- 1> else if *effectiveMeasWindowConfig* is set to *release*: + - 2> release the effective measurement window configuration; + +NOTE: The SFN and subframe of the PCell is used in the effective measurement window calculation. + +### 5.5.3 Performing measurements + +#### 5.5.3.1 General + +An RRC\_CONNECTED UE shall derive cell measurement results by measuring one or multiple beams associated per cell as configured by the network, as described in 5.5.3.3. For all cell measurement results, except for RSSI, and CLI measurement results in RRC\_CONNECTED, the UE applies the layer 3 filtering as specified in 5.5.3.2, before using the measured results for evaluation of reporting criteria, measurement reporting or the criteria to trigger conditional reconfiguration execution. For cell measurements, the network can configure RSRP, RSRQ, SINR, RSCP or EcN0 as trigger quantity. For CLI measurements, the network can configure SRS-RSRP or CLI-RSSI as trigger quantity. For cell and beam measurements, reporting quantities can be any combination of quantities (i.e. only RSRP; only RSRQ; only SINR; RSRP and RSRQ; RSRP and SINR; RSRQ and SINR; RSRP, RSRQ and SINR; only RSCP; only EcN0; RSCP and EcN0), irrespective of the trigger quantity, and for CLI measurements, reporting quantities can be either SRS-RSRP or CLI-RSSI. For conditional reconfiguration execution, the network can configure up to 2 quantities, both using same RS type. The UE does not apply the layer 3 filtering as specified in 5.5.3.2 to derive the CBR measurements. The UE does not apply the layer 3 filtering as specified in 5.5.3.2 to derive the Rx-Tx time difference measurements. + +The network may also configure the UE to report measurement information per beam (which can either be measurement results per beam with respective beam identifier(s) or only beam identifier(s)), derived as described in 5.5.3.3a. If beam measurement information is configured to be included in measurement reports, the UE applies the layer 3 beam filtering as specified in 5.5.3.2. On the other hand, the exact L1 filtering of beam measurements used to derive cell measurement results is implementation dependent. + +The UE shall: + +- 1> whenever the UE has a *measConfig*, perform RSRP and RSRQ measurements for each serving cell for which *servingCellMO* is configured as follows: + - 2> if the *reportConfig* associated with at least one *measId* included in the *measIdList* within *VarMeasConfig* contains an *rsType* set to *ssb* and *ssb-ConfigMobility* is configured in the *measObject* indicated by the *servingCellMO*: + - 3> if the *reportConfig* associated with at least one *measId* included in the *measIdList* within *VarMeasConfig* contains a *reportQuantityRS-Indexes* and *maxNrofRS-IndexesToReport* and contains an *rsType* set to *ssb*: + - 4> derive layer 3 filtered RSRP and RSRQ per beam for the serving cell based on SS/PBCH block, as described in 5.5.3.3a; + - 3> derive serving cell measurement results based on SS/PBCH block, as described in 5.5.3.3; + - 2> if the *reportConfig* associated with at least one *measId* included in the *measIdList* within *VarMeasConfig* contains an *rsType* set to *csi-rs* and *CSI-RS-ResourceConfigMobility* is configured in the *measObject* indicated by the *servingCellMO*: + - 3> if the *reportConfig* associated with at least one *measId* included in the *measIdList* within *VarMeasConfig* contains a *reportQuantityRS-Indexes* and *maxNrofRS-IndexesToReport* and contains an *rsType* set to *csi-rs*: + - 4> derive layer 3 filtered RSRP and RSRQ per beam for the serving cell based on CSI-RS, as described in 5.5.3.3a; + - 3> derive serving cell measurement results based on CSI-RS, as described in 5.5.3.3; + +- 1> for each serving cell for which *servingCellMO* is configured, if the *reportConfig* associated with at least one *measId* included in the *measIdList* within *VarMeasConfig* contains SINR as trigger quantity and/or reporting quantity: + - 2> if the *reportConfig* contains *rsType* set to *ssb* and *ssb-ConfigMobility* is configured in the *servingCellMO*: + - 3> if the *reportConfig* contains a *reportQuantityRS-Indexes* and *maxNrofRS-IndexesToReport*: + - 4> derive layer 3 filtered SINR per beam for the serving cell based on SS/PBCH block, as described in 5.5.3.3a; + - 3> derive serving cell SINR based on SS/PBCH block, as described in 5.5.3.3; + - 2> if the *reportConfig* contains *rsType* set to *csi-rs* and *CSI-RS-ResourceConfigMobility* is configured in the *servingCellMO*: + - 3> if the *reportConfig* contains a *reportQuantityRS-Indexes* and *maxNrofRS-IndexesToReport*: + - 4> derive layer 3 filtered SINR per beam for the serving cell based on CSI-RS, as described in 5.5.3.3a; + - 3> derive serving cell SINR based on CSI-RS, as described in 5.5.3.3; +- 1> for each *measId* included in the *measIdList* within *VarMeasConfig*: + - 2> if the *reportType* for the associated *reportConfig* is set to *reportCGI* and timer T321 is running: + - 3> if *useAutonomousGaps* is configured for the associated *reportConfig*: + - 4> perform the corresponding measurements on the frequency and RAT indicated in the associated *measObject* using autonomous gaps as necessary; + - 3> else: + - 4> perform the corresponding measurements on the frequency and RAT indicated in the associated *measObject* using available idle periods; + - 3> if the cell indicated by *reportCGI* field for the associated *measObject* is an NR cell and that indicated cell is broadcasting *SIB1* (see TS 38.213 [13], clause 13): + - 4> try to acquire *SIB1* in the concerned cell; + - 3> if the cell indicated by *reportCGI* field is an E-UTRA cell: + - 4> try to acquire *SystemInformationBlockType1* in the concerned cell; + - 2> if the *ul-DelayValueConfig* is configured for the associated *reportConfig*: + - 3> ignore the *measObject*; + - 3> for each of the configured DRBs, configure the PDCP layer to perform corresponding average UL PDCP packet delay measurement per DRB; + +- 2> if the *ul-ExcessDelayConfig* is configured for the associated *reportConfig*: + - 3> ignore the *measObject*; + - 3> for each of the configured DRBs, configure the PDCP layer to perform corresponding UL PDCP Excess Packet Delay delay measurement according to the configured threshold per DRB; +- 2> if the *reportType* for the associated *reportConfig* is *periodical*, *eventTriggered*; or +- 2> if the *reportType* for the associated *reportConfig* is *condTriggerConfig*, the *measId* is within the MCG *VarMeasConfig* and is indicated in the *condExecutionCond* or in the *condExecutionCondPSCell* associated to a *condReconfigId* in the MCG *VarConditionalReconfig* (for CHO, CPA or MN-initiated inter-SN CPC in NR-DC); or +- 2> if the *reportType* for the associated *reportConfig* is *condTriggerConfig*, the *measId* is within the SCG *VarMeasConfig* and is indicated in the *condExecutionCond* associated to a *condReconfigId* in the SCG *VarConditionalReconfig* (for intra-SN CPC); or +- 2> if the *reportType* for the associated *reportConfig* is *condTriggerConfig*, the *measId* is within the SCG *VarMeasConfig* and is indicated in the *condExecutionCondSCG* associated to a *condReconfigId* in the MCG *VarConditionalReconfig* (for SN-initiated inter-SN CPC in NR-DC); or +- 2> if the *reportType* for the associated *reportConfig* is *condTriggerConfig*, the *measId* is within the SCG *VarMeasConfig* and is indicated in the *triggerConditionSN* associated to a *condReconfigurationId* in *VarConditionalReconfiguration* as specified in TS 36.331 [10] (for SN-initiated inter-SN CPC in EN-DC): + - 3> if a measurement gap configuration is setup, or + - 3> if the UE does not require measurement gaps to perform the concerned measurements: + - 4> if *s-MeasureConfig* is not configured, or + - 4> if *s-MeasureConfig* is set to *ssb-RSRP* and the NR SpCell RSRP based on SS/PBCH block, after layer 3 filtering, is lower than *ssb-RSRP*, or + - 4> if *s-MeasureConfig* is set to *csi-RSRP* and the NR SpCell RSRP based on CSI-RS, after layer 3 filtering, is lower than *csi-RSRP*: + - 5> if the *measObject* is associated to NR and the *rsType* is set to *csi-rs*: + - 6> if *reportQuantityRS-Indexes* and *maxNrofRS-IndexesToReport* for the associated *reportConfig* are configured: + - 7> derive layer 3 filtered beam measurements only based on CSI-RS for each measurement quantity indicated in *reportQuantityRS-Indexes*, as described in 5.5.3.3a; + - 6> derive cell measurement results based on CSI-RS for the trigger quantity and each measurement quantity indicated in *reportQuantityCell* using parameters from the associated *measObject*, as described in 5.5.3.3; + - 5> if the *measObject* is associated to NR and the *rsType* is set to *ssb*: + - 6> if *reportQuantityRS-Indexes* and *maxNrofRS-IndexesToReport* for the associated *reportConfig* are configured: + +7> derive layer 3 beam measurements only based on SS/PBCH block for each measurement quantity indicated in *reportQuantityRS-Indexes*, as described in 5.5.3.3a; + +6> derive cell measurement results based on SS/PBCH block for the trigger quantity and each measurement quantity indicated in *reportQuantityCell* using parameters from the associated *measObject*, as described in 5.5.3.3; + +5> if the *measObject* is associated to E-UTRA: + +6> perform the corresponding measurements associated to neighbouring cells on the frequencies indicated in the concerned *measObject*, as described in 5.5.3.2; + +5> if the *measObject* is associated to UTRA-FDD: + +6> perform the corresponding measurements associated to neighbouring cells on the frequencies indicated in the concerned *measObject*, as described in 5.5.3.2; + +5> if the *measObject* is associated to L2 U2N Relay UE: + +6> perform the corresponding measurements associated to candidate Relay UEs on the frequencies indicated in the concerned *measObject*, as described in 5.5.3.4; + +4> if the *measRSSI-ReportConfig* is configured in the associated *reportConfig*: + +5> perform the RSSI and channel occupancy measurements on the frequency configured by *rmtc-Frequency* in the associated *measObject*; + +NOTE 0: The network avoids configuring UEs supporting only CHO and/or Rel-16 CPC with measurements not referred to by any execution condition. + +2> if the *reportType* for the associated *reportConfig* is set to *reportSFTD* and the *numberOfReportsSent* as defined within the *VarMeasReportList* for this *measId* is less than one: + +3> if the *reportSFTD-Meas* is set to *true*: + +4> if the *measObject* is associated to E-UTRA: + +5> perform SFTD measurements between the PCell and the E-UTRA PSCell; + +5> if the *reportRSRP* is set to *true*: + +6> perform RSRP measurements for the E-UTRA PSCell; + +4> else if the *measObject* is associated to NR: + +5> perform SFTD measurements between the PCell and the NR PSCell; + +- 5> if the *reportRSRP* is set to *true*; + - 6> perform RSRP measurements for the NR PSCell based on SSB; +- 3> else if the *reportSFTD-NeighMeas* is included: + - 4> if the *measObject* is associated to NR: + - 5> if the *drx-SFTD-NeighMeas* is included: + - 6> perform SFTD measurements between the PCell and the NR neighbouring cell(s) detected based on parameters in the associated *measObject* using available idle periods; + - 5> else: + - 6> perform SFTD measurements between the PCell and the NR neighbouring cell(s) detected based on parameters in the associated *measObject*; + - 5> if the *reportRSRP* is set to *true*: + - 6> perform RSRP measurements based on SSB for the NR neighbouring cell(s) detected based on parameters in the associated *measObject*; + - 2> if the *reportType* for the associated *reportConfig* is *cli-Periodical* or *cli-EventTriggered*: + - 3> perform the corresponding measurements associated to CLI measurement resources indicated in the concerned *measObjectCLI*; + - 2> perform the evaluation of reporting criteria as specified in 5.5.4, except if *reportConfig* is *condTriggerConfig*. + +The UE acting as a L2 U2N Remote UE whenever configured with *measConfig* shall: + +- 1> perform the corresponding measurements associated to the serving L2 U2N Relay UE, as described in 5.5.3.4; + +NOTE 1: The evaluation of conditional reconfiguration execution criteria is specified in 5.3.5.13. + +The UE capable of Rx-Tx time difference measurement when configured with *measObjectRXTxDiff* shall: + +- 1> perform the corresponding Rx-Tx time difference measurements associated with downlink reference signals indicated in the concerned *measObjectRXTxDiff*. + +The UE capable of CBR measurement when configured to transmit NR sidelink communication/discovery/positioning shall: + +- 1> If the frequency used for NR sidelink communication/discovery/positioning is included in *sl-FreqInfoToAddModList/sl-FreqInfoToAddModListExt* in *sl-ConfigDedicatedNR* within *RRCReconfiguration* message or included in *sl-ConfigCommonNR* within *SIB12* or included in *sl-PosConfigCommonNR* within *SIB23*: +- 2> if the UE is in *RRC\_IDLE* or in *RRC\_INACTIVE*: + +- 3> if configured with NR sidelink communication and the cell chosen for NR sidelink communication provides *SIB12* which includes *sl-TxPoolSelectedNormal* or *sl-TxPoolExceptional* for the concerned frequency; or +- 3> if configured with NR sidelink discovery and the cell chosen for NR sidelink discovery provides *SIB12* which includes *sl-TxPoolSelectedNormal* or *sl-TxPoolExceptional* but does not include *sl-DiscTxPoolSelected* for the concerned frequency: + - 4> perform CBR measurement on pool(s) in *sl-TxPoolSelectedNormal* or *sl-TxPoolExceptional* for the concerned frequency in *SIB12*; +- 3> if configured with NR sidelink discovery and the cell chosen for NR sidelink discovery provides *SIB12* which includes *sl-DiscTxPoolSelected* for the concerned frequency: + - 4> perform CBR measurement on pools in *sl-DiscTxPoolSelected* and *sl-TxPoolExceptional* for the concerned frequency in *SIB12*; +- 3> if configured with NR sidelink positioning and the cell chosen for NR sidelink positioning provides *SIB23* which includes *sl-PRS-TxPoolSelectedNormal* or *sl-PRS-TxPoolExceptional* for the concerned frequency: + - 4> perform CBR measurement on pool(s) in *sl-TxPoolSelectedNormal* or *sl-TxPoolExceptional* for the concerned frequency in *SIB23*; +- 2> if the UE is in *RRC\_CONNECTED*: + - 3> if *tx-PoolMeasToAddModList* is included in *VarMeasConfig*: + - 4> perform CBR measurements on each transmission resource pool indicated in the *tx-PoolMeasToAddModList*; + - 3> if *sl-DiscTxPoolSelected*, *sl-TxPoolSelectedNormal*, *sl-TxPoolScheduling* or *sl-TxPoolExceptional* is included in *sl-ConfigDedicatedNR* for the concerned frequency within *RRCReconfiguration*: + - 4> perform CBR measurement on pool(s) in *sl-DiscTxPoolSelected*, *sl-TxPoolSelectedNormal*, *sl-TxPoolScheduling* and *sl-TxPoolExceptional* if included in *sl-ConfigDedicatedNR* for the concerned frequency within *RRCReconfiguration*; + - 3> else: + - 4> if configured with NR sidelink communication and the cell chosen for NR sidelink communication provides *SIB12* which includes *sl-TxPoolSelectedNormal* or *sl-TxPoolExceptional* for the concerned frequency; or + - 4> if configured with NR sidelink discovery and the cell chosen for NR sidelink discovery provides *SIB12* which includes *sl-TxPoolSelectedNormal* or *sl-TxPoolExceptional* but does not provide *sl-DiscTxPoolSelected* for the concerned frequency: + - 5> perform CBR measurement on pool(s) in *sl-TxPoolSelectedNormal* or *sl-TxPoolExceptional* for the concerned frequency in *SIB12*; + - 4> if configured with NR sidelink discovery and the cell chosen for NR sidelink discovery provides *SIB12* which includes *sl-DiscTxPoolSelected* for the concerned frequency: + - 5> perform CBR measurement on pools in *sl-DiscTxPoolSelected* and *sl-TxPoolExceptional* for the concerned frequency in *SIB12*; + +4> if configured with NR sidelink positioning and the cell chosen for NR sidelink positioning provides *SIB23* which includes *sl-PRS-TxPoolSelectedNormal* or *sl-PRS-TxPoolExceptional* for the concerned frequency: + +5> perform CBR measurement on pool(s) in *sl-PRS-TxPoolSelectedNormal* or *sl-PRS-TxPoolExceptional* for the concerned frequency in *SIB23* + +1> else: + +2> if configured with NR sidelink communication and *sl-TxPoolSelectedNormal* is included in *SidelinkPreconfigNR* for the concerned frequency; or + +2> if configured with NR sidelink discovery and *sl-TxPoolSelectedNormal* is included in *SidelinkPreconfigNR* but *sl-DiscTxPoolSelected* is not included in *SidelinkPreconfigNR* for the concerned frequency: + +3> perform CBR measurement on pool(s) in *sl-TxPoolSelectedNormal* in *SidelinkPreconfigNR* for the concerned frequency. + +2> if configured with NR sidelink discovery and *sl-DiscTxPoolSelected* is included in *SidelinkPreconfigNR* for the concerned frequency: + +3> perform CBR measurement on pools in *sl-DiscTxPoolSelected* if included in *SidelinkPreconfigNR*. + +2> if configured with NR sidelink communication/positioning and *sl-PRS-TxPoolSelectedNormal* is included in *SL-PosPreconfigurationNR* for the concerned frequency: + +3> perform CBR measurement on pool(s) in *sl-PRS-TxPoolSelectedNormal* in *SidelinkPreconfigNR* for the concerned frequency. + +NOTE 2: In case the configurations for NR sidelink communication and CBR measurement are acquired via the E-UTRA, configurations for NR sidelink communication in *SIB12*, *sl-ConfigDedicatedNR* within *RRCReconfiguration* used in this clause are provided by the configurations in *SystemInformationBlockType28*, *sl-ConfigDedicatedForNR* within *RRCConnectionReconfiguration* as specified in TS 36.331[10], respectively. + +NOTE 3: If a UE that is configured by upper layers to transmit V2X sidelink communication is configured by NR with transmission resource pool(s) and the measurement objects concerning V2X sidelink communication (i.e. by *sl-ConfigDedicatedEUTRA-Info*), it shall perform CBR measurement as specified in clause 5.5.3 of TS 36.331 [10], based on the transmission resource pool(s) and the measurement object(s) concerning V2X sidelink communication configured by NR. + +NOTE 4: For V2X sidelink communication, each of the CBR measurement results is associated with a resource pool, as indicated by the *poolReportId* (see TS 36.331 [10]), that refers to a pool as included in *sl-ConfigDedicatedEUTRA-Info* or *SIB13*. + +#### 5.5.3.2 Layer 3 filtering + +The UE shall: + +1> for each cell measurement quantity, each beam measurement quantity, each sidelink measurement quantity as needed in clause 5.8.10, for each CLI measurement quantity that the UE performs measurements according to 5.5.3.1, for each candidate L2 U2N Relay UE measurement quantity according to 5.5.3.4, for evaluating the detected NR sidelink U2N Relay UEs according to 5.8.15.3, for evaluating the SyncRef UE according to 5.8.5 and 5.8.6, and for evaluating the detected NR sidelink U2U Relay UEs according to 5.8.17.4: + +- 2> filter the measured result, before using for evaluation of reporting criteria, for measurement reporting, for U2N/U2U Relay (re)selection evaluation or for evaluating the SyncRef UE, by the following formula: + +$$F_n = (1 - a)^k F_{n-1} + a^k M_n$$ + +where + +$M_n$ is the latest received measurement result from the physical layer; + +$F_n$ is the updated filtered measurement result, that is used for evaluation of reporting criteria, for measurement reporting, for U2N/U2U Relay (re)selection evaluation or for evaluating the SyncRef UE; + +$F_{n-1}$ is the old filtered measurement result, where $F_0$ is set to $M_1$ when the first measurement result from the physical layer is received; and for *MeasObjectNR*, $a = 1/2^{(k_i/4)}$ , where $k_i$ is the *filterCoefficient* for the corresponding measurement quantity of the i:th *QuantityConfigNR* in *quantityConfigNR-List*, and i is indicated by *quantityConfigIndex* in *MeasObjectNR*; for other measurements, $a = 1/2^{(k/4)}$ , where $k$ is the *filterCoefficient* for the corresponding measurement quantity received by the *quantityConfig*; for UTRA-FDD, $a = 1/2^{(k/4)}$ , where $k$ is the *filterCoefficient* for the corresponding measurement quantity received by *quantityConfigUTRA-FDD* in the *QuantityConfig*; + +- 2> adapt the filter such that the time characteristics of the filter are preserved at different input rates, observing that the *filterCoefficient* $k$ assumes a sample rate equal to X ms; The value of X is equivalent to one intra-frequency L1 measurement period as defined in TS 38.133 [14] assuming non-DRX operation, and depends on frequency range. + +NOTE 1: If $k$ is set to 0, no layer 3 filtering is applicable. + +NOTE 2: The filtering is performed in the same domain as used for evaluation of reporting criteria, for measurement reporting, for U2N Relay (re)selection evaluation or for evaluating the SyncRef UE, i.e., logarithmic filtering for logarithmic measurements. + +NOTE 3: The filter input rate is implementation dependent, to fulfil the performance requirements set in TS 38.133 [14]. For further details about the physical layer measurements, see TS 38.133 [14]. + +NOTE 4: For CLI-RSSI measurement, it is up to UE implementation whether to reset filtering upon BWP switch. + +NOTE 5: For SSB measurements when multiple altitude range-based *ssb-ToMeasure* are configured, it is up to UE implementation whether to reset filtering upon entering a different altitude range. + +#### 5.5.3.3 Derivation of cell measurement results + +The network may configure the UE in RRC\_CONNECTED to derive RSRP, RSRQ and SINR measurement results per cell associated to NR measurement objects based on parameters configured in the *measObject* (e.g. maximum number of beams to be averaged and beam consolidation thresholds) and in the *reportConfig* (*rsType* to be measured, SS/PBCH block or CSI-RS). + +The network may configure the UE in RRC\_IDLE or in RRC\_INACTIVE to derive RSRP and RSRQ measurement results per cell associated to NR carriers based on parameters configured in *measIdleCarrierListNR* within *VarMeasIdleConfig* for measurements performed according to 5.7.8.2a. + +The UE shall: + +- 1> for each cell measurement quantity to be derived based on SS/PBCH block: + - 2> if *nrofSS-BlocksToAverage* is not configured in the associated *measObject* in RRC\_CONNECTED or in the associated entry in *measIdleCarrierListNR* within *VarMeasIdleConfig* in RRC\_IDLE/RRC\_INACTIVE; or + - 2> if *absThreshSS-BlocksConsolidation* is not configured in the associated *measObject* in RRC\_CONNECTED or in the associated entry in *measIdleCarrierListNR* within *VarMeasIdleConfig* in RRC\_IDLE/RRC\_INACTIVE; or + - 2> if the highest beam measurement quantity value is below or equal to *absThreshSS-BlocksConsolidation*: + - 3> derive each cell measurement quantity based on SS/PBCH block as the highest beam measurement quantity value, where each beam measurement quantity is described in TS 38.215 [9]; + - 2> else: + - 3> derive each cell measurement quantity based on SS/PBCH block as the linear power scale average of the highest beam measurement quantity values above *absThreshSS-BlocksConsolidation* where the total number of averaged beams shall not exceed *nrofSS-BlocksToAverage*, and where each beam measurement quantity is described in TS 38.215 [9]; + - 2> if in RRC\_CONNECTED, apply layer 3 cell filtering as described in 5.5.3.2; +- 1> for each cell measurement quantity to be derived based on CSI-RS: + - 2> consider a CSI-RS resource to be applicable for deriving cell measurements when the concerned CSI-RS resource is included in the *csi-rs-CellMobility* including the *physCellId* of the cell in the *CSI-RS-ResourceConfigMobility* in the associated *measObject*; + - 2> if *nrofCSI-RS-ResourcesToAverage* in the associated *measObject* is not configured; or + - 2> if *absThreshCSI-RS-Consolidation* in the associated *measObject* is not configured; or + - 2> if the highest beam measurement quantity value is below or equal to *absThreshCSI-RS-Consolidation*: + - 3> derive each cell measurement quantity based on applicable CSI-RS resources for the cell as the highest beam measurement quantity value, where each beam measurement quantity is described in TS 38.215 [9]; + - 2> else: + - 3> derive each cell measurement quantity based on CSI-RS as the linear power scale average of the highest beam measurement quantity values above *absThreshCSI-RS-Consolidation* where the total number of averaged beams shall not exceed *nrofCSI-RS-ResourcesToAverage*; + +2> apply layer 3 cell filtering as described in 5.5.3.2. + +#### 5.5.3.3a Derivation of layer 3 beam filtered measurement + +The UE shall: + +1> for each layer 3 beam filtered measurement quantity to be derived based on SS/PBCH block; + +2> derive each configured beam measurement quantity based on SS/PBCH block as described in TS 38.215[9], and apply layer 3 beam filtering as described in 5.5.3.2; + +1> for each layer 3 beam filtered measurement quantity to be derived based on CSI-RS; + +2> derive each configured beam measurement quantity based on CSI-RS as described in TS 38.215 [9], and apply layer 3 beam filtering as described in 5.5.3.2. + +#### 5.5.3.4 Derivation of L2 U2N Relay UE measurement results + +A UE may be configured by network to derive NR sidelink measurement results of serving L2 U2N Relay UE or candidate L2 U2N Relay UEs associated to the measurement objects configured in the *measObjectRelay*. + +The UE shall: + +1> for each L2 U2N Relay UE measurement quantity to be derived: + +2> derive the corresponding measurement quantity based on PSSCH/PSCCH DMRS as described in TS 38.215 [9]; + +2> apply layer 3 filtering as described in 5.5.3.2; + +### 5.5.4 Measurement report triggering + +#### 5.5.4.1 General + +If AS security has been activated successfully, the UE shall: + +1> for each *measId* included in the *measIdList* within *VarMeasConfig*: + +2> if the corresponding *reportConfig* includes a *reportType* set to *eventTriggered* or *periodical*: + +3> if the corresponding *measObject* concerns NR: + +4> if the corresponding *reportConfig* includes *measRS-ReportConfig*: + +5> consider the resource indicated by the *rmtc-Config* on the associated frequency to be applicable; + +- 4> if the *eventA1* or *eventA2* is configured in the corresponding *reportConfig*: + - 5> consider only the serving cell to be applicable; +- 4> if the *eventA3* or *eventA5* or *eventA3H1* or *eventA3H2* or *eventA5H1* or *eventA5H2* is configured in the corresponding *reportConfig*: + - 5> if a serving cell is associated with a *measObjectNR* and neighbours are associated with another *measObjectNR*, consider any serving cell associated with the other *measObjectNR* to be a neighbouring cell as well; +- 4> if the *eventX2* is configured in the corresponding *reportConfig*: + - 5> consider only the serving L2 U2N Relay UE to be applicable; +- 4> if corresponding *reportConfig* includes *reportType* set to *periodical*; or +- 4> for measurement events other than *eventA1*, *eventA2*, *eventD1*, *eventX2*, *eventH1* or *eventH2*: + - 5> if *useAllowedCellList* is set to *true*: + - 6> consider any neighbouring cell detected based on parameters in the associated *measObjectNR* to be applicable when the concerned cell is included in the *allowedCellsToAddModList* defined within the *VarMeasConfig* for this *measId*; + - 5> else: + - 6> consider any neighbouring cell detected based on parameters in the associated *measObjectNR* to be applicable when the concerned cell is not included in the *excludedCellsToAddModList* defined within the *VarMeasConfig* for this *measId*; +- 4> if the *eventH1* or *eventH2* is configured in the corresponding *reportConfig*: + - 5> for all the events of the same type for which *simulMultiTriggerSingleMeasReport* is set to *true* and the entry condition applicable for the event has been satisfied: + - 6> consider only the event with the smallest value between the altitude of the UE and the corresponding altitude threshold to be applicable; +- 4> else if the *eventA3H1* or *eventA3H2* or *eventA4H1* or *eventA4H2* or *eventA5H1* or *eventA5H2* is configured in the corresponding *reportConfig*: + - 5> for all the events of the same type associated with the same *measObjectNR* for which *simulMultiTriggerSingleMeasReport* is set to *true* and the entry conditions applicable for the event has been satisfied: + - 6> consider only the event with the smallest value between the altitude of the UE and the corresponding altitude threshold to be applicable; +- 3> else if the corresponding *measObject* concerns E-UTRA: + - 4> if *eventB1* or *eventB2* is configured in the corresponding *reportConfig*: + +- 5> consider a serving cell, if any, on the associated E-UTRA frequency as neighbour cell; +- 4> consider any neighbouring cell detected on the associated frequency to be applicable when the concerned cell is not included in the *excludedCellsToAddModListEUTRAN* defined within the *VarMeasConfig* for this *measId*; +- 3> else if the corresponding *measObject* concerns UTRA-FDD: + - 4> if *eventB1-UTRA-FDD* or *eventB2-UTRA-FDD* is configured in the corresponding *reportConfig*; or + - 4> if corresponding *reportConfig* includes *reportType* set to *periodical*: + - 5> consider a neighbouring cell on the associated frequency to be applicable when the concerned cell is included in the *cellsToAddModList* defined within the *VarMeasConfig* for this *measId*; +- 3> else if the corresponding *measObject* concerns L2 U2N Relay UE: + - 4> if *eventY1-Relay* or *eventY2-Relay* or *eventZ1-Relay* is configured in the corresponding *reportConfig*; or + - 4> if corresponding *reportConfig* includes *reportType* set to *periodical*: + - 5> consider any L2 U2N Relay UE fulfilling upper layer criteria detected on the associated frequency to be applicable for this *measId*; +- 2> else if the corresponding *reportConfig* includes a *reportType* set to *reportCGI*: + - 3> consider the cell detected on the associated *measObject* which has a physical cell identity matching the value of the *cellForWhichToReportCGI* included in the corresponding *reportConfig* within the *VarMeasConfig* to be applicable; +- 2> else if the corresponding *reportConfig* includes a *reportType* set to *reportSFTD*: + - 3> if the corresponding *measObject* concerns NR: + - 4> if the *reportSFTD-Meas* is set to *true*: + - 5> consider the NR PSCell to be applicable; + - 4> else if the *reportSFTD-NeighMeas* is included: + - 5> if *cellsForWhichToReportSFTD* is configured in the corresponding *reportConfig*: + - 6> consider any NR neighbouring cell detected on the associated *measObjectNR* which has a physical cell identity that is included in the *cellsForWhichToReportSFTD* to be applicable; + - 5> else: + +- 6> consider up to 3 strongest NR neighbouring cells detected based on parameters in the associated *measObjectNR* to be applicable when the concerned cells are not included in the *excludedCellsToAddModList* defined within the *VarMeasConfig* for this *measId*; +- 3> else if the corresponding *measObject* concerns E-UTRA: + - 4> if the *reportSFTD-Meas* is set to *true*: + - 5> consider the E-UTRA PSCell to be applicable; +- 2> else if the corresponding *reportConfig* includes a *reportType* set to *cli-Periodical* or *cli-EventTriggered*: + - 3> consider all CLI measurement resources included in the corresponding *measObject* to be applicable; +- 2> else if the corresponding *reportConfig* includes a *reportType* set to *rxTxPeriodical*: + - 3> consider all Rx-Tx time difference measurement resources included in the corresponding *measObject* to be applicable; +- 2> if the corresponding *reportConfig* concerns the reporting for NR sidelink communication/discovery (i.e. *reportConfigNR-SL*): + - 3> consider the transmission resource pools indicated by the *tx-PoolMeasToAddModList* defined within the *VarMeasConfig* for this *measId* to be applicable; +- 2> if the *reportType* is set to *eventTriggered*, and if the corresponding *reportConfig* does not include *numberOfTriggeringCells*, and if the entry condition applicable for this event, i.e. the event corresponding with the *eventId* of the corresponding *reportConfig* within *VarMeasConfig*, is fulfilled for one or more applicable cells for all measurements after layer 3 filtering taken during *timeToTrigger* defined for this event within the *VarMeasConfig*, while the *VarMeasReportList* does not include a measurement reporting entry for this *measId* (a first cell triggers the event): + - 3> include a measurement reporting entry within the *VarMeasReportList* for this *measId*; + - 3> set the *numberOfReportsSent* defined within the *VarMeasReportList* for this *measId* to 0; + - 3> include the concerned cell(s) in the *cellsTriggeredList* defined within the *VarMeasReportList* for this *measId*; + - 3> if *useT312* is set to *true* in *reportConfig* for this event: + - 4> if T310 for the corresponding SpCell is running; and + - 4> if T312 is not running for corresponding SpCell: + - 5> start timer T312 for the corresponding SpCell with the value of T312 configured in the corresponding *measObjectNR*; + - 3> initiate the measurement reporting procedure, as specified in 5.5.5; +- 2> else if the *reportType* is set to *eventTriggered*, and if the corresponding *reportConfig* does not include *numberOfTriggeringCells*, and if the entry condition applicable for this event, i.e. the event corresponding with the *eventId* of the corresponding *reportConfig* within *VarMeasConfig*, is fulfilled for one or more applicable cells not + +included in the *cellsTriggeredList* for all measurements after layer 3 filtering taken during *timeToTrigger* defined for this event within the *VarMeasConfig* (a subsequent cell triggers the event): + +3> set the *numberOfReportsSent* defined within the *VarMeasReportList* for this *measId* to 0; + +3> include the concerned cell(s) in the *cellsTriggeredList* defined within the *VarMeasReportList* for this *measId*; + +3> if *useT312* is set to *true* in *reportConfig* for this event: + +4> if T310 for the corresponding SpCell is running; and + +4> if T312 is not running for corresponding SpCell: + +5> start timer T312 for the corresponding SpCell with the value of T312 configured in the corresponding *measObjectNR*; + +3> initiate the measurement reporting procedure, as specified in 5.5.5; + +2> if the *reportType* is set to *eventTriggered*, and if the corresponding *reportConfig* includes *numberOfTriggeringCells*, and if the entry condition applicable for this event, i.e. the event corresponding with the *eventId* of the corresponding *reportConfig* within *VarMeasConfig*, is fulfilled for one or more applicable cells for all measurements after layer 3 filtering taken during *timeToTrigger* defined for this event within the *VarMeasConfig*: + +3> if the *VarMeasReportList* does not include a measurement reporting entry for this *measId* (a first cell triggers the event): + +4> include a measurement reporting entry within the *VarMeasReportList* for this *measId*; + +3> if the number of cell(s) in the *cellsTriggeredList* is larger than or equal to *numberOfTriggeringCells*: + +4> include the concerned cell(s) in the *cellsTriggeredList* defined within the *VarMeasReportList* for this *measId*; + +3> else: + +4> include the concerned cell(s) in the *cellsTriggeredList* defined within the *VarMeasReportList* for this *measId*; + +4> if the number of cell(s) in the *cellsTriggeredList* is larger than or equal to *numberOfTriggeringCells*: + +5> set the *numberOfReportsSent* defined within the *VarMeasReportList* for this *measId* to 0; + +5> initiate the measurement reporting procedure, as specified in 5.5.5; + +2> if the *reportType* is set to *eventTriggered* and if the leaving condition applicable for this event is fulfilled for one or more of the cells included in the *cellsTriggeredList* defined within the *VarMeasReportList* for this *measId* for all measurements after layer 3 filtering taken during *timeToTrigger* defined within the *VarMeasConfig* for this event: + +3> remove the concerned cell(s) in the *cellsTriggeredList* defined within the *VarMeasReportList* for this *measId*; + +- 3> if *reportOnLeave* is set to *true* for the corresponding reporting configuration: + - 4> if the corresponding *reportConfig* does not include *numberOfTriggeringCells*; or + - 4> if the corresponding *reportConfig* includes *numberOfTriggeringCells* and a measurement report was previously sent to the network for at least one of the concerned cell(s): + - 5> initiate the measurement reporting procedure, as specified in 5.5.5; +- 3> if the *cellsTriggeredList* defined within the *VarMeasReportList* for this *measId* is empty: + - 4> remove the measurement reporting entry within the *VarMeasReportList* for this *measId*; + - 4> stop the periodical reporting timer for this *measId*, if running; +- 2> if the *reportType* is set to *eventTriggered* and if the entry condition applicable for this event, i.e. the event corresponding with the *eventId* of the corresponding *reportConfig* within *VarMeasConfig*, is fulfilled for one or more applicable L2 U2N Relay UEs for all measurements after layer 3 filtering taken during *timeToTrigger* defined for this event within the *VarMeasConfig*, while the *VarMeasReportList* does not include a measurement reporting entry for this *measId* (a first L2 U2N Relay UE triggers the event): + - 3> include a measurement reporting entry within the *VarMeasReportList* for this *measId*; + - 3> set the *numberOfReportsSent* defined within the *VarMeasReportList* for this *measId* to 0; + - 3> include the concerned L2 U2N Relay UE(s) in the *relaysTriggeredList* defined within the *VarMeasReportList* for this *measId*; + - 3> initiate the measurement reporting procedure, as specified in 5.5.5; +- 2> else if the *reportType* is set to *eventTriggered* and if the entry condition applicable for this event, i.e. the event corresponding with the *eventId* of the corresponding *reportConfig* within *VarMeasConfig*, is fulfilled for one or more applicable L2 U2N Relay UEs not included in the *relaysTriggeredList* for all measurements after layer 3 filtering taken during *timeToTrigger* defined for this event within the *VarMeasConfig* (a subsequent L2 U2N Relay UE triggers the event): + - 3> set the *numberOfReportsSent* defined within the *VarMeasReportList* for this *measId* to 0; + - 3> include the concerned L2 U2N Relay UE(s) in the *relaysTriggeredList* defined within the *VarMeasReportList* for this *measId*; + - 3> initiate the measurement reporting procedure, as specified in 5.5.5; +- 2> else if the *reportType* is set to *eventTriggered* and if the leaving condition applicable for this event is fulfilled for one or more of the L2 U2N Relay UEs included in the *relaysTriggeredList* defined within the *VarMeasReportList* for this *measId* for all measurements after layer 3 filtering taken during *timeToTrigger* defined within the *VarMeasConfig* for this event: + - 3> remove the concerned L2 U2N Relay UE(s) in the *relaysTriggeredList* defined within the *VarMeasReportList* for this *measId*; + +- 3> if *reportOnLeave* is set to *true* for the corresponding reporting configuration: + - 4> initiate the measurement reporting procedure, as specified in 5.5.5; +- 3> if the *relaysTriggeredList* defined within the *VarMeasReportList* for this *measId* is empty: + - 4> remove the measurement reporting entry within the *VarMeasReportList* for this *measId*; + - 4> stop the periodical reporting timer for this *measId*, if running; +- 2> else if the *reportType* is set to *eventTriggered* and if the entry condition applicable for this event, i.e. the event corresponding with the *eventId* of the corresponding *reportConfig* within *VarMeasConfig*, is fulfilled for one or more applicable transmission resource pools for all measurements taken during *timeToTrigger* defined for this event within the *VarMeasConfig*, while the *VarMeasReportList* does not include an measurement reporting entry for this *measId* (a first transmission resource pool triggers the event): + - 3> include a measurement reporting entry within the *VarMeasReportList* for this *measId*; + - 3> set the *numberOfReportsSent* defined within the *VarMeasReportList* for this *measId* to 0; + - 3> include the concerned transmission resource pool(s) in the *poolsTriggeredList* defined within the *VarMeasReportList* for this *measId*; + - 3> initiate the measurement reporting procedure, as specified in 5.5.5; +- 2> else if the *reportType* is set to *eventTriggered* and if the entry condition applicable for this event, i.e. the event corresponding with the *eventId* of the corresponding *reportConfig* within *VarMeasConfig*, is fulfilled for one or more applicable transmission resource pools not included in the *poolsTriggeredList* for all measurements taken during *timeToTrigger* defined for this event within the *VarMeasConfig* (a subsequent transmission resource pool triggers the event): + - 3> set the *numberOfReportsSent* defined within the *VarMeasReportList* for this *measId* to 0; + - 3> include the concerned transmission resource pool(s) in the *poolsTriggeredList* defined within the *VarMeasReportList* for this *measId*; + - 3> initiate the measurement reporting procedure, as specified in 5.5.5; +- 2> if the *reportType* is set to *eventTriggered* and if the leaving condition applicable for this event is fulfilled for one or more applicable transmission resource pools included in the *poolsTriggeredList* defined within the *VarMeasReportList* for this *measId* for all measurements taken during *timeToTrigger* defined within the *VarMeasConfig* for this event: + - 3> remove the concerned transmission resource pool(s) in the *poolsTriggeredList* defined within the *VarMeasReportList* for this *measId*; + - 3> if the *poolsTriggeredList* defined within the *VarMeasReportList* for this *measId* is empty: + - 4> remove the measurement reporting entry within the *VarMeasReportList* for this *measId*; + - 4> stop the periodical reporting timer for this *measId*, if running + +- 2> else if the *reportType* is set to *eventTriggered* and if the *eventId* is set to *eventD1* or *eventH1* or *eventH2* and if the entering condition applicable for this event, i.e. the event corresponding with the *eventId* of the corresponding *reportConfig* within *VarMeasConfig*, is fulfilled during *timeToTrigger* defined for this event within the *VarMeasConfig*, while the *VarMeasReportList* does not include a measurement reporting entry for this *measId*: + - 3> include a measurement reporting entry within the *VarMeasReportList* for this *measId*; + - 3> set the *numberOfReportsSent* defined within the *VarMeasReportList* for this *measId* to 0; + - 3> initiate the measurement reporting procedure, as specified in 5.5.5; +- 2> else if the *reportType* is set to *eventTriggered* and if the *eventId* is set to *eventD1* or *eventH1* or *eventH2* and if the leaving condition applicable for this event is fulfilled for the associated *VarMeasReport* within the *VarMeasReportList* for this *measId* during *timeToTrigger* defined within the *VarMeasConfig* for this event: + - 3> if *reportOnLeave* is set to *true* for the corresponding reporting configuration: + - 4> initiate the measurement reporting procedure, as specified in 5.5.5; + - 3> remove the measurement reporting entry within the *VarMeasReportList* for this *measId*; + - 3> stop the periodical reporting timer for this *measId*, if running; + +NOTE 1: Void. + +- 2> if *reportType* is set to *periodical* and if a (first) measurement result is available: + - 3> include a measurement reporting entry within the *VarMeasReportList* for this *measId*; + - 3> set the *numberOfReportsSent* defined within the *VarMeasReportList* for this *measId* to 0; + - 3> if the corresponding *reportConfig* includes *measRSSI-ReportConfig*: + - 4> initiate the measurement reporting procedure as specified in 5.5.5 immediately when RSSI sample values are reported by the physical layer after the first L1 measurement duration; + - 3> else if the corresponding *reportConfig* includes the *ul-DelayValueConfig*: + - 4> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after a first measurement result is provided from lower layers of the associated DRB identity; + - 3> else if the corresponding *reportConfig* includes the *ul-ExcessDelayConfig*: + - 4> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after a first measurement result is provided from lower layers of the associated DRB identity(ies) according to the configured threshold per DRB identity(ies); + +- 3> else if the *reportAmount* exceeds 1: + - 4> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity to be reported becomes available for the NR SpCell or for the serving L2 U2N Relay UE (if the UE is a L2 U2N Remote UE); +- 3> else (i.e. the *reportAmount* is equal to 1): + - 4> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity to be reported becomes available for the NR SpCell and for the strongest cell among the applicable cells, or for the NR SpCell and for the strongest L2 U2N Relay UEs among the applicable L2 U2N Relay UEs; or initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity to be reported becomes available for the serving L2 U2N Relay UE and for the strongest cell among the applicable cells, or for the serving L2 U2N Relay UE and for the strongest L2 U2N Relay UEs among the applicable L2 U2N Relay UEs (if the UE is a L2 U2N Remote UE); +- 2> if, in case the corresponding *reportConfig* concerns the reporting for NR sidelink communication/discovery, *reportType* is set to *periodical* and if a (first) measurement result is available: + - 3> include a measurement reporting entry within the *VarMeasReportList* for this *measId*; + - 3> set the *numberOfReportsSent* defined within the *VarMeasReportList* for this *measId* to 0; + - 3> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity to be reported becomes available for the NR SpCell and CBR measurement results become available; +- 2> if the *reportType* is set to *cli-EventTriggered* and if the entry condition applicable for this event, i.e. the event corresponding with the *eventId* of the corresponding *reportConfig* within *VarMeasConfig*, is fulfilled for one or more applicable CLI measurement resources for all measurements after layer 3 filtering taken during *timeToTrigger* defined for this event within the *VarMeasConfig*, while the *VarMeasReportList* does not include a measurement reporting entry for this *measId* (a first CLI measurement resource triggers the event): + - 3> include a measurement reporting entry within the *VarMeasReportList* for this *measId*; + - 3> set the *numberOfReportsSent* defined within the *VarMeasReportList* for this *measId* to 0; + - 3> include the concerned CLI measurement resource(s) in the *cli-TriggeredList* defined within the *VarMeasReportList* for this *measId*; + - 3> initiate the measurement reporting procedure, as specified in 5.5.5; +- 2> else if the *reportType* is set to *cli-EventTriggered* and if the entry condition applicable for this event, i.e. the event corresponding with the *eventId* of the corresponding *reportConfig* within *VarMeasConfig*, is fulfilled for one or more CLI measurement resources not included in the *cli-TriggeredList* for all measurements after layer 3 filtering taken during *timeToTrigger* defined for this event within the *VarMeasConfig* (a subsequent CLI measurement resource triggers the event): + - 3> set the *numberOfReportsSent* defined within the *VarMeasReportList* for this *measId* to 0; + - 3> include the concerned CLI measurement resource(s) in the *cli-TriggeredList* defined within the *VarMeasReportList* for this *measId*; + +- 3> initiate the measurement reporting procedure, as specified in 5.5.5; +- 2> if the *reportType* is set to *cli-EventTriggered* and if the leaving condition applicable for this event is fulfilled for one or more of the CLI measurement resources included in the *cli-TriggeredList* defined within the *VarMeasReportList* for this *measId* for all measurements after layer 3 filtering taken during *timeToTrigger* defined within the *VarMeasConfig* for this event: + - 3> remove the concerned CLI measurement resource(s) in the *cli-TriggeredList* defined within the *VarMeasReportList* for this *measId*; + - 3> if *reportOnLeave* is set to *true* for the corresponding reporting configuration: + - 4> initiate the measurement reporting procedure, as specified in 5.5.5; + - 3> if the *cli-TriggeredList* defined within the *VarMeasReportList* for this *measId* is empty: + - 4> remove the measurement reporting entry within the *VarMeasReportList* for this *measId*; + - 4> stop the periodical reporting timer for this *measId*, if running; +- 2> if *reportType* is set to *cli-Periodical* and if a (first) measurement result is available: + - 3> include a measurement reporting entry within the *VarMeasReportList* for this *measId*; + - 3> set the *numberOfReportsSent* defined within the *VarMeasReportList* for this *measId* to 0; + - 3> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity to be reported becomes available for at least one CLI measurement resource; +- 2> if *reportType* is set to *rxTxPeriodical* and if a (first) measurement result is available: + - 3> include a measurement reporting entry within the *VarMeasReportList* for this *measId*; + - 3> set the *numberOfReportsSent* defined within the *VarMeasReportList* for this *measId* to 0; + - 3> initiate the measurement reporting procedure, as specified in 5.5.5; +- 2> upon expiry of the periodical reporting timer for this *measId*: + - 3> initiate the measurement reporting procedure, as specified in 5.5.5. +- 2> if the corresponding *reportConfig* includes a *reportType* is set to *reportSFTD*: + - 3> if the corresponding *measObject* concerns NR: + - 4> if the *drx-SFTD-NeighMeas* is included: + +- 5> if the quantity to be reported becomes available for each requested pair of PCell and NR cell: + - 6> stop timer T322; + - 6> initiate the measurement reporting procedure, as specified in 5.5.5; +- 4> else + - 5> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity to be reported becomes available for each requested pair of PCell and NR cell or the maximal measurement reporting delay as specified in TS 38.133 [14]; +- 3> else if the corresponding *measObject* concerns E-UTRA: + - 4> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity to be reported becomes available for the pair of PCell and E-UTRA PSCell or the maximal measurement reporting delay as specified in TS 38.133 [14]; +- 2> if *reportType* is set to *reportCGI*: + - 3> if the UE acquired the *SIB1* or *SystemInformationBlockType1* for the requested cell; or + - 3> if the UE detects that the requested NR cell is not transmitting *SIB1* (see TS 38.213 [13], clause 13): + - 4> stop timer T321; + - 4> include a measurement reporting entry within the *VarMeasReportList* for this *measId*; + - 4> set the *numberOfReportsSent* defined within the *VarMeasReportList* for this *measId* to 0; + - 4> initiate the measurement reporting procedure, as specified in 5.5.5; +- 2> upon the expiry of T321 for this *measId*: + - 3> include a measurement reporting entry within the *VarMeasReportList* for this *measId*; + - 3> set the *numberOfReportsSent* defined within the *VarMeasReportList* for this *measId* to 0; + - 3> initiate the measurement reporting procedure, as specified in 5.5.5. +- 2> upon the expiry of T322 for this *measId*: + - 3> initiate the measurement reporting procedure, as specified in 5.5.5. + +If AS security has been activated successfully and if SCell activation(s) indication is received from lower layer, the UE shall: + +- 1> if *reportType* is set to *reportOnActivation* for any *measId* included in the *measIdList* within *VarMeasConfig*: +- 2> if the activated SCell(s) fulfills the measurement requirement as specified in TS 38.133 [14]: + - 3> include a measurement reporting entry within the *VarMeasReportList* for this *measId*: + - 3> set the *numberOfReportsSent* defined within the *VarMeasReportList* for this *measId* to 0; + - 4> initiate the measurement reporting procedure, as specified in 5.5.5. + +#### 5.5.4.2 Event A1 (Serving becomes better than threshold) + +The UE shall: + +- 1> consider the entering condition for this event to be satisfied when condition A1-1, as specified below, is fulfilled; +- 1> consider the leaving condition for this event to be satisfied when condition A1-2, as specified below, is fulfilled; +- 1> for this measurement, consider the NR serving cell corresponding to the associated *measObjectNR* associated with this event. + +Inequality A1-1 (Entering condition) + +$$Ms - Hys > Thresh$$ + +Inequality A1-2 (Leaving condition) + +$$Ms + Hys < Thresh$$ + +The variables in the formula are defined as follows: + +*Ms* is the measurement result of the serving cell, not taking into account any offsets. + +*Hys* is the hysteresis parameter for this event (i.e. *hysteresis* as defined within *reportConfigNR* for this event). + +*Thresh* is the threshold parameter for this event (i.e. *a1-Threshold* as defined within *reportConfigNR* for this event). + +*Ms* is expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR. + +*Hys* is expressed in dB. + +*Thresh* is expressed in the same unit as *Ms*. + +#### 5.5.4.3 Event A2 (Serving becomes worse than threshold) + +The UE shall: + +- 1> consider the entering condition for this event to be satisfied when condition A2-1, as specified below, is fulfilled; +- 1> consider the leaving condition for this event to be satisfied when condition A2-2, as specified below, is fulfilled; +- 1> for this measurement, consider the serving cell indicated by the *measObjectNR* associated to this event. + +NOTE: If the serving cell indicated by the *measObjectNR* associated to this event is not detectable, then the UE should consider for the value of *Ms* the lowest value of the value range of the measurement quantity as the serving cell measurement. + +Inequality A2-1 (Entering condition) + +$$Ms + Hys < Thresh$$ + +Inequality A2-2 (Leaving condition) + +$$Ms - Hys > Thresh$$ + +The variables in the formula are defined as follows: + +*Ms* is the measurement result of the serving cell, not taking into account any offsets. + +*Hys* is the hysteresis parameter for this event (i.e. *hysteresis* as defined within *reportConfigNR* for this event). + +*Thresh* is the threshold parameter for this event (i.e. *a2-Threshold* as defined within *reportConfigNR* for this event). + +*Ms* is expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR. + +*Hys* is expressed in dB. + +*Thresh* is expressed in the same unit as *Ms*. + +#### 5.5.4.4 Event A3 (Neighbour becomes offset better than SpCell) + +The UE shall: + +- 1> consider the entering condition for this event to be satisfied when condition A3-1, as specified below, is fulfilled; +- 1> consider the leaving condition for this event to be satisfied when condition A3-2, as specified below, is fulfilled; +- 1> use the SpCell for *Mp*, *Ofp* and *Ocp*. + +NOTE 1: The cell(s) that triggers the event has reference signals indicated in the *measObjectNR* associated to this event which may be different from the NR SpCell *measObjectNR*. + +Inequality A3-1 (Entering condition) + +$$Mn + Ofn + Ocn - Hys > Mp + Ofp + Ocp + Off$$ + +Inequality A3-2 (Leaving condition) + +$$Mn + Ofn + Ocn + Hys < Mp + Ofp + Ocp + Off$$ + +The variables in the formula are defined as follows: + +***Mn*** is the measurement result of the neighbouring cell, not taking into account any offsets. + +***Ofn*** is the measurement object specific offset of the reference signal of the neighbour cell (i.e. *offsetMO* as defined within *measObjectNR* corresponding to the neighbour cell). + +***Ocn*** is the cell specific offset of the neighbour cell (i.e. *cellIndividualOffset* as defined within *measObjectNR* corresponding to the frequency of the neighbour cell, or *cellIndividualOffset* as defined within *reportConfigNR*), and set to zero if not configured for the neighbour cell. + +***Mp*** is the measurement result of the SpCell, not taking into account any offsets. + +***Ofp*** is the measurement object specific offset of the SpCell (i.e. *offsetMO* as defined within *measObjectNR* corresponding to the SpCell). + +***Ocp*** is the cell specific offset of the SpCell (i.e. *cellIndividualOffset* as defined within *measObjectNR* corresponding to the SpCell), and is set to zero if not configured for the SpCell. + +***Hys*** is the hysteresis parameter for this event (i.e. *hysteresis* as defined within *reportConfigNR* for this event). + +***Off*** is the offset parameter for this event (i.e. *a3-Offset* as defined within *reportConfigNR* for this event). + +***Mn***, ***Mp*** are expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR. + +***Ofn***, ***Ocn***, ***Ofp***, ***Ocp***, ***Hys***, ***Off*** are expressed in dB. + +NOTE 2: The definition of Event A3 also applies to CondEvent A3. + +#### 5.5.4.5 Event A4 (Neighbour becomes better than threshold) + +The UE shall: + +1> consider the entering condition for this event to be satisfied when condition A4-1, as specified below, is fulfilled; + +1> consider the leaving condition for this event to be satisfied when condition A4-2, as specified below, is fulfilled. + +Inequality A4-1 (Entering condition) + +$$Mn + Ofn + Ocn - Hys > Thresh$$ + +Inequality A4-2 (Leaving condition) + +$$Mn + Ofn + Ocn + Hys < Thresh$$ + +The variables in the formula are defined as follows: + +***Mn*** is the measurement result of the neighbouring cell or the measurement result of serving PSCell (i.e., in case it is configured as candidate PSCell for CondEvent A4 evaluation) for CHO with candidate SCG(s) case, not taking into account any offsets. + +***Ofn*** is the measurement object specific offset of the neighbour cell (i.e. *offsetMO* as defined within *measObjectNR* corresponding to the neighbour cell). + +***Ocn*** is the measurement object specific offset of the neighbour cell (i.e. *cellIndividualOffset* as defined within *measObjectNR* corresponding to the neighbour cell, or *cellIndividualOffset* as defined within *reportConfigNR*), and set to zero if not configured for the neighbour cell. + +***Hys*** is the hysteresis parameter for this event (i.e. *hysteresis* as defined within *reportConfigNR* for this event). + +***Thresh*** is the threshold parameter for this event (i.e. *a4-Threshold* as defined within *reportConfigNR* for this event). + +***Mn*** is expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR. + +***Ofn***, ***Ocn***, ***Hys*** are expressed in dB. + +***Thresh*** is expressed in the same unit as ***Mn***. + +NOTE: The definition of Event A4 also applies to CondEvent A4. + +#### 5.5.4.6 Event A5 (SpCell becomes worse than threshold1 and neighbour becomes better than threshold2) + +The UE shall: + +1> consider the entering condition for this event to be satisfied when both condition A5-1 and condition A5-2, as specified below, are fulfilled; + +1> consider the leaving condition for this event to be satisfied when condition A5-3 or condition A5-4, i.e. at least one of the two, as specified below, is fulfilled; + +1> use the SpCell for *Mp*. + +NOTE 1: The parameters of the reference signal(s) of the cell(s) that triggers the event are indicated in the *measObjectNR* associated to the event which may be different from the *measObjectNR* of the NR SpCell. + +Inequality A5-1 (Entering condition 1) + +$$M_p + H_{ys} < Thresh1$$ + +Inequality A5-2 (Entering condition 2) + +$$M_n + O_{fn} + O_{cn} - H_{ys} > Thresh2$$ + +Inequality A5-3 (Leaving condition 1) + +$$M_p - H_{ys} > Thresh1$$ + +Inequality A5-4 (Leaving condition 2) + +$$M_n + O_{fn} + O_{cn} + H_{ys} < Thresh2$$ + +The variables in the formula are defined as follows: + +**$M_p$** is the measurement result of the NR SpCell, not taking into account any offsets. + +**$M_n$** is the measurement result of the neighbouring cell, not taking into account any offsets. + +**$O_{fn}$** is the measurement object specific offset of the neighbour cell (i.e. *offsetMO* as defined within *measObjectNR* corresponding to the neighbour cell). + +**$O_{cn}$** is the cell specific offset of the neighbour cell (i.e. *cellIndividualOffset* as defined within *measObjectNR* corresponding to the neighbour cell, or *cellIndividualOffset* as defined within *reportConfigNR*), and set to zero if not configured for the neighbour cell. + +**$H_{ys}$** is the hysteresis parameter for this event (i.e. *hysteresis* as defined within *reportConfigNR* for this event). + +**$Thresh1$** is the threshold parameter for this event (i.e. *a5-Threshold1* as defined within *reportConfigNR* for this event). + +**$Thresh2$** is the threshold parameter for this event (i.e. *a5-Threshold2* as defined within *reportConfigNR* for this event). + +**$M_n, M_p$** are expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR. + +**$O_{fn}, O_{cn}, H_{ys}$** are expressed in dB. + +**$Thresh1$** is expressed in the same unit as **$M_p$** . + +**$Thresh2$** is expressed in the same unit as **$M_n$** . + +NOTE 2: The definition of Event A5 also applies to CondEvent A5. + +#### 5.5.4.7 Event A6 (Neighbour becomes offset better than SCell) + +The UE shall: + +- 1> consider the entering condition for this event to be satisfied when condition A6-1, as specified below, is fulfilled; +- 1> consider the leaving condition for this event to be satisfied when condition A6-2, as specified below, is fulfilled; +- 1> for this measurement, consider the (secondary) cell corresponding to the *measObjectNR* associated to this event to be the serving cell. + +NOTE: The reference signal(s) of the neighbour(s) and the reference signal(s) of the SCell are both indicated in the associated *measObjectNR*. + +Inequality A6-1 (Entering condition) + +$$Mn + Ocn - Hys > Ms + Ocs + Off$$ + +Inequality A6-2 (Leaving condition) + +$$Mn + Ocn + Hys < Ms + Ocs + Off$$ + +The variables in the formula are defined as follows: + +***Mn*** is the measurement result of the neighbouring cell, not taking into account any offsets. + +***Ocn*** is the cell specific offset of the neighbour cell (i.e. *cellIndividualOffset* as defined within the associated *measObjectNR*), and set to zero if not configured for the neighbour cell. + +***Ms*** is the measurement result of the serving cell, not taking into account any offsets. + +***Ocs*** is the cell specific offset of the serving cell (i.e. *cellIndividualOffset* as defined within the associated *measObjectNR*, or *cellIndividualOffset* as defined within *reportConfigNR*), and is set to zero if not configured for the serving cell. + +***Hys*** is the hysteresis parameter for this event (i.e. *hysteresis* as defined within *reportConfigNR* for this event). + +***Off*** is the offset parameter for this event (i.e. *a6-Offset* as defined within *reportConfigNR* for this event). + +***Mn***, ***Ms*** are expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR. + +***Ocn***, ***Ocs***, ***Hys***, ***Off*** are expressed in dB. + +#### 5.5.4.8 Event B1 (Inter RAT neighbour becomes better than threshold) + +The UE shall: + +1> consider the entering condition for this event to be satisfied when condition B1-1, as specified below, is fulfilled; + +1> consider the leaving condition for this event to be satisfied when condition B1-2, as specified below, is fulfilled. + +Inequality B1-1 (Entering condition) + +$$Mn + Ofn + Ocn - Hys > Thresh$$ + +Inequality B1-2 (Leaving condition) + +$$Mn + Ofn + Ocn + Hys < Thresh$$ + +The variables in the formula are defined as follows: + +***Mn*** is the measurement result of the inter-RAT neighbour cell, not taking into account any offsets. + +***Ofn*** is the measurement object specific offset of the frequency of the inter-RAT neighbour cell (i.e. *eutra-Q-OffsetRange* as defined within the *measObjectEUTRA* corresponding to the frequency of the neighbour inter-RAT cell, *utra-FDD-Q-OffsetRange* as defined within the *measObjectUTRA-FDD* corresponding to the frequency of the neighbour inter-RAT cell). + +***Ocn*** is the cell specific offset of the inter-RAT neighbour cell (i.e. *cellIndividualOffset* as defined within the *measObjectEUTRA* corresponding to the neighbour inter-RAT cell, or *cellIndividualOffset* as defined within *reportConfigInterRAT*), and set to zero if not configured for the neighbour cell. + +***Hys*** is the hysteresis parameter for this event (i.e. *hysteresis* as defined within *reportConfigInterRAT* for this event). + +***Thresh*** is the threshold parameter for this event (i.e. *b1-ThresholdEUTRA* as defined within *reportConfigInterRAT* for this event, *b1-ThresholdUTRA-FDD* as defined for UTRA-FDD within *reportConfigInterRAT* for this event). + +***Mn*** is expressed in dBm or in dB, depending on the measurement quantity of the inter-RAT neighbour cell. + +***Ofn***, ***Ocn***, ***Hys*** are expressed in dB. + +***Thresh*** is expressed in the same unit as ***Mn***. + +#### 5.5.4.9 Event B2 (PCell becomes worse than threshold1 and inter RAT neighbour becomes better than threshold2) + +The UE shall: + +1> consider the entering condition for this event to be satisfied when both condition B2-1 and condition B2-2, as specified below, are fulfilled; + +1> consider the leaving condition for this event to be satisfied when condition B2-3 or condition B2-4, i.e. at least one of the two, as specified below, is fulfilled; + +Inequality B2-1 (Entering condition 1) + +$$M_p + Hys < Thresh1$$ + +Inequality B2-2 (Entering condition 2) + +$$M_n + O_{fn} + O_{cn} - Hys > Thresh2$$ + +Inequality B2-3 (Leaving condition 1) + +$$M_p - Hys > Thresh1$$ + +Inequality B2-4 (Leaving condition 2) + +$$M_n + O_{fn} + O_{cn} + Hys < Thresh2$$ + +The variables in the formula are defined as follows: + +**$M_p$** is the measurement result of the PCell, not taking into account any offsets. + +**$M_n$** is the measurement result of the inter-RAT neighbour cell, not taking into account any offsets. + +**$O_{fn}$** is the measurement object specific offset of the frequency of the inter-RAT neighbour cell (i.e. *eutra-Q-OffsetRange* as defined within the *measObjectEUTRA* corresponding to the frequency of the inter-RAT neighbour cell, *utra-FDD-Q-OffsetRange* as defined within the *measObjectUTRA-FDD* corresponding to the frequency of the neighbour inter-RAT cell). + +**$O_{cn}$** is the cell specific offset of the inter-RAT neighbour cell (i.e. *cellIndividualOffset* as defined within the *measObjectEUTRA* corresponding to the neighbour inter-RAT cell, or *cellIndividualOffset* as defined within *reportConfigInterRAT*), and set to zero if not configured for the neighbour cell. + +**$Hys$** is the hysteresis parameter for this event (i.e. *hysteresis* as defined within *reportConfigInterRAT* for this event). + +**$Thresh1$** is the threshold parameter for this event (i.e. *b2-Threshold1* as defined within *reportConfigInterRAT* for this event). + +**$Thresh2$** is the threshold parameter for this event (i.e. *b2-Threshold2EUTRA* as defined within *reportConfigInterRAT* for this event, *b2-Threshold2UTRA-FDD* as defined for UTRA-FDD within *reportConfigInterRAT* for this event). + +**$M_p$** is expressed in dBm in case of RSRP, or in dB in case of RSRQ and SINR. + +**$M_n$** is expressed in dBm or dB, depending on the measurement quantity of the inter-RAT neighbour cell. + +**$O_{fn}$ , $O_{cn}$ , $Hys$** are expressed in dB. + +**$Thresh1$** is expressed in the same unit as **$M_p$** . + +**$Thresh2$** is expressed in the same unit as **$M_n$** . + +#### 5.5.4.10 Event I1 (Interference becomes higher than threshold) + +The UE shall: + +- 1> consider the entering condition for this event to be satisfied when condition I1-1, as specified below, is fulfilled; +- 1> consider the leaving condition for this event to be satisfied when condition I1-2, as specified below, is fulfilled. + +Inequality I1-1 (Entering condition) + +$$Mi - Hys > Thresh$$ + +Inequality I1-2 (Leaving condition) + +$$Mi + Hys < Thresh$$ + +The variables in the formula are defined as follows: + +***Mi*** is the measurement result of the interference, not taking into account any offsets. + +***Hys*** is the hysteresis parameter for this event (i.e. *hysteresis* as defined within *reportConfigNR* for this event). + +***Thresh*** is the threshold parameter for this event (i.e. *i1-Threshold* as defined within *reportConfigNR* for this event). + +***Mi***, ***Thresh*** are expressed in dBm. + +***Hys*** is expressed in dB. + +#### 5.5.4.11 Event C1 (The NR sidelink channel busy ratio is above a threshold) + +The UE shall: + +- 1> consider the entering condition for this event to be satisfied when condition C1-1, as specified below, is fulfilled; +- 1> consider the leaving condition for this event to be satisfied when condition C1-2, as specified below, is fulfilled; + +Inequality C1-1 (Entering condition) + +Inequality C1-2 (Leaving condition) + +The variables in the formula are defined as follows: + +***Ms*** is the measurement result of channel busy ratio of the transmission resource pool, not taking into account any offsets. + +***Hys*** is the hysteresis parameter for this event (i.e. *hysteresis* as defined within *reportConfigNR-SL* for this event). + +***Thresh*** is the threshold parameter for this event (i.e. *c1-Threshold* as defined within *reportConfigNR-SL* for this event). + +***Ms*** is expressed in decimal from 0 to 1 in steps of 0.01. + +***Hys*** is expressed is in the same unit as ***Ms***. + +***Thresh*** is expressed in the same unit as ***Ms***. + +#### 5.5.4.12 Event C2 (The NR sidelink channel busy ratio is below a threshold) + +The UE shall: + +1> consider the entering condition for this event to be satisfied when condition C2-1, as specified below, is fulfilled; + +1> consider the leaving condition for this event to be satisfied when condition C2-2, as specified below, is fulfilled; + +Inequality C2-1 (Entering condition) + +Inequality C2-2 (Leaving condition) + +The variables in the formula are defined as follows: + +***Ms*** is the measurement result of channel busy ratio of the transmission resource pool, not taking into account any offsets. + +***Hys*** is the hysteresis parameter for this event (i.e. *hysteresis* as defined within *reportConfigNR-SL* for this event). + +***Thresh*** is the threshold parameter for this event (i.e. *c2-Threshold* as defined within *reportConfigNR-SL* for this event). + +***Ms*** is expressed in decimal from 0 to 1 in steps of 0.01. + +***Hys*** is expressed is in the same unit as ***Ms***. + +***Thresh*** is expressed in the same unit as ***Ms***. + +5.5.4.13 Void + +5.5.4.14 Void + +5.5.4.15 Event D1 (Distance between UE and referenceLocation1 is above threshold1 and distance between UE and referenceLocation2 is below threshold2) + +The UE shall: + +1> consider the entering condition for this event to be satisfied when both condition D1-1 and condition D1-2, as specified below, are fulfilled; + +1> consider the leaving condition for this event to be satisfied when condition D1-3 or condition D1-4, i.e. at least one of the two, as specified below, are fulfilled; + +Inequality D1-1 (Entering condition 1) + +Inequality D1-2 (Entering condition 2) + +Inequality D1-3 (Leaving condition 1) + +Inequality D1-4 (Leaving condition 2) + +The variables in the formula are defined as follows: + +**MI1** is the distance between UE and a reference location for this event (i.e. *referenceLocation1* as defined within *reportConfigNR* for this event), not taking into account any offsets. + +**MI2** is the distance between UE and a reference location for this event (i.e. *referenceLocation2* as defined within *reportConfigNR* for this event), not taking into account any offsets. + +**Hys** is the hysteresis parameter for this event (i.e. *hysteresisLocation* as defined within *reportConfigNR* for this event). + +**Thresh1** is the threshold for this event defined as a distance, configured with parameter *distanceThreshFromReference1*, from a reference location configured with parameter *referenceLocation1* within *reportConfigNR* for this event. + +**Thresh2** is the threshold for this event defined as a distance, configured with parameter *distanceThreshFromReference2*, from a reference location configured with parameter *referenceLocation2* within *reportConfigNR* for this event. + +**M11** is expressed in meters. + +**M12** is expressed in the same unit as **M11**. + +**Hys** is expressed in the same unit as **M11**. + +**Thresh1** is expressed in the same unit as **M11**. + +**Thresh2** is expressed in the same unit as **M11**. + +NOTE: The definition of Event D1 also applies to CondEvent D1. + +#### 5.5.4.15a CondEvent D2 (Distance between UE and a moving referenceLocation1 is above threshold1 and distance between UE and a moving referenceLocation2 is below threshold2) + +The UE shall: + +- 1> consider the entering condition for this event to be satisfied when both condition D2-1 and condition D2-2, as specified below, are fulfilled; +- 1> consider the leaving condition for this event to be satisfied when condition D2-3 or condition D2-4, i.e. at least one of the two, as specified below, are fulfilled; + +Inequality D2-1 (Entering condition 1) + +Inequality D2-2 (Entering condition 2) + +Inequality D2-3 (Leaving condition 1) + +Inequality D2-4 (Leaving condition 2) + +The variables in the formula are defined as follows: + +**M11** is the distance between UE and a moving reference location for this event, not taking into account any offsets. The moving reference location is determined based on *referenceLocation1* as defined within *reportConfigNR* for this event and the corresponding epoch time and satellite ephemeris. + +**MI2** is the distance between UE and a moving reference location for this event, not taking into account any offsets. The moving reference location is determined based on *referenceLocation2* as defined within *reportConfigNR* for this event and the corresponding epoch time and satellite ephemeris + +**Hys** is the hysteresis parameter for this event (i.e. *hysteresisLocation* as defined within *reportConfigNR* for this event). + +**Thresh1** is the threshold for this event defined as a distance, configured with parameter *distanceThreshFromReference1*, from a moving reference location configured with parameter *referenceLocation1* within *reportConfigNR* for this event. + +**Thresh2** is the threshold for this event defined as a distance, configured with parameter *distanceThreshFromReference2*, from a moving reference location configured with parameter *referenceLocation2* within *reportConfigNR* for this event. + +**MI1** is expressed in meters. + +**MI2** is expressed in the same unit as **MI1**. + +**Hys** is expressed in the same unit as **MI1**. + +**Thresh1** is expressed in the same unit as **MI1**. + +**Thresh2** is expressed in the same unit as **MI1**. + +Editor's Note: FFS whether location-based conditional handover (*condEventD2*) applies only to moving cells or a combination of moving and quasi-Earth fixed cells for the choice of source and target cells. + +#### 5.5.4.16 CondEvent T1 (Time measured at UE is within a duration from threshold) + +The UE shall: + +- 1> consider the entering condition for this event to be satisfied when condition T1-1, as specified below, is fulfilled; +- 1> consider the leaving condition for this event to be satisfied when condition T1-2, as specified below, is fulfilled; + +Inequality T1-1 (Entering condition) + +Inequality T1-2 (Leaving condition) + +The variables in the formula are defined as follows: + +**Mt** is the time measured at UE. + +**Thresh1** is the threshold parameter for this event (i.e. *t1-Threshold* as defined within *reportConfigNR* for this event). + +**Duration** is the duration parameter for this event (i.e. *duration* as defined within *reportConfigNR* for this event). + +**Mt** is expressed in *ms*. + +**Thresh1** is expressed in the same unit as **Mt**. + +**Duration** is expressed in the same unit as **Mt**. + +#### 5.5.4.17 Event X1 (Serving L2 U2N Relay UE becomes worse than threshold1 and NR Cell becomes better than threshold2) + +The UE shall: + +1> consider the entering condition for this event to be satisfied when both condition X1-1 and condition X1-2, as specified below, are fulfilled; + +1> consider the leaving condition for this event to be satisfied when condition X1-3 or condition X1-4, i.e. at least one of the two, as specified below, is fulfilled; + +Inequality X1-1 (Entering condition 1) + +$$Mr + Hys < Thresh1$$ + +Inequality X1-2 (Entering condition 2) + +$$Mn + Ofn + Ocn - Hys > Thresh2$$ + +Inequality X1-3 (Leaving condition 1) + +$$Mr - Hys > Thresh1$$ + +Inequality X1-4 (Leaving condition 2) + +$$Mn + Ofn + Ocn + Hys < Thresh2$$ + +The variables in the formula are defined as follows: + +**Mr** is the measurement result of the serving L2 U2N Relay UE, not taking into account any offsets. + +**Mn** is the measurement result of the NR cell, not taking into account any offsets. + +**Ofn** is the measurement object specific offset of the reference signal of the NR cell (i.e. *offsetMO* as defined within *measObjectNR* corresponding to the NR cell). + +**Ocn** is the cell specific offset of the NR cell (i.e. *cellIndividualOffset* as defined within *measObjectNR* corresponding to the frequency of the NR cell, or *cellIndividualOffset* as defined within *reportConfigNR*), and set to zero if not configured for the cell. + +*Hys* is the hysteresis parameter for this event. + +*Thresh1* is the threshold parameter for this event (i.e. *x1-Threshold1-Relay* as defined within *reportConfigNR* for this event). + +*Thresh2* is the threshold parameter for this event (i.e. *x1-Threshold2* as defined within *reportConfigNR* for this event). + +*Mr* is expressed in dBm. + +*Mn* is expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR. + +*Ofn*, *Ocn*, *Hys* are expressed in dB. + +*Thresh1* is expressed in the same unit as *Mr*. + +*Thresh2* is expressed in the same unit as *Mn*. + +#### 5.5.4.18 Event X2 (Serving L2 U2N Relay UE becomes worse than threshold) + +The UE shall: + +1> consider the entering condition for this event to be satisfied when condition X2-1, as specified below, is fulfilled; + +1> consider the leaving condition for this event to be satisfied when condition X2-2, as specified below, is fulfilled; + +Inequality X2-1 (Entering condition) + +$$Mr + Hys < Thresh$$ + +Inequality X2-2 (Leaving condition) + +$$Mr - Hys > Thresh$$ + +The variables in the formula are defined as follows: + +*Mr* is the measurement result of the serving L2 U2N Relay UE, not taking into account any offsets. + +*Hys* is the hysteresis parameter for this event. + +*Thresh* is the threshold parameter for this event (i.e. *x2-Threshold-Relay* as defined within *reportConfigNR* for this event). + +*Mr* is expressed in dBm. + +*Hys* are expressed in dB. + +*Thresh* is expressed in the same unit as *Mr*. + +#### 5.5.4.19 Event Y1 (PCell becomes worse than threshold1 and candidate L2 U2N Relay UE becomes better than threshold2) + +The UE shall: + +1> consider the entering condition for this event to be satisfied when both condition Y1-1 and condition Y1-2, as specified below, are fulfilled; + +1> consider the leaving condition for this event to be satisfied when condition Y1-3 or condition Y1-4, i.e. at least one of the two, as specified below, is fulfilled; + +Inequality Y1-1 (Entering condition 1) + +$$M_p + Hys < Thresh1$$ + +Inequality Y1-2 (Entering condition 2) + +$$M_r - Hys > Thresh2$$ + +Inequality Y1-3 (Leaving condition 1) + +$$M_p - Hys > Thresh1$$ + +Inequality Y1-4 (Leaving condition 2) + +$$M_r + Hys < Thresh2$$ + +The variables in the formula are defined as follows: + +*Mp* is the measurement result of the PCell, not taking into account any offsets. + +*Mr* is the measurement result of the candidate L2 U2N Relay UE, not taking into account any offsets. + +*Hys* is the hysteresis parameter for this event (i.e. *hysteresis* as defined within *reportConfigInterRAT* for this event). + +*Thresh1* is the threshold parameter for this event (i.e. *y1-Threshold1* as defined within *reportConfigInterRAT* for this event). + +*Thresh2* is the threshold parameter for this event (i.e. *y1-Threshold2-Relay* as defined within *reportConfigInterRAT* for this event). + +*Mp* is expressed in dBm in case of RSRP, or in dB in case of RSRQ and SINR. + +*Mr* is expressed in dBm or dB, depending on the measurement quantity of candidate L2 U2N Relay UE. + +*Hys* are expressed in dB. + +*Thresh1* is expressed in the same unit as *Mp*. + +*Thresh2* is expressed in the same unit as *Mr*. + +#### 5.5.4.20 Event Y2 (Candidate L2 U2N Relay UE becomes better than threshold) + +The UE shall: + +1> consider the entering condition for this event to be satisfied when condition Y2-1, as specified below, is fulfilled; + +1> consider the leaving condition for this event to be satisfied when condition Y2-2, as specified below, is fulfilled; + +Inequality Y2-1 (Entering condition) + +$$Mr - Hys > Thresh$$ + +Inequality Y2-2 (Leaving condition) + +$$Mr + Hys < Thresh$$ + +The variables in the formula are defined as follows: + +*Mr* is the measurement result of the candidate L2 U2N Relay UE, not taking into account any offsets. + +*Hys* is the hysteresis parameter for this event (i.e. *hysteresis* as defined within *reportConfigInterRAT* for this event). + +*Thresh* is the threshold parameter for this event (i.e. *y2-Threshold-Relay* as defined within *reportConfigInterRAT* for this event). + +*Mr* is expressed in dBm or dB, depending on the measurement quantity of candidate L2 U2N Relay UE. + +*Hys* are expressed in dB. + +*Thresh* is expressed in the same unit as *Mr*. + +##### 5.5.4.20b Event Z1 (Serving L2 U2N Relay UE becomes worse than threshold1 and Candidate L2 U2N Relay UE becomes better than threshold2) + +The UE shall: + +1> consider the entering condition for this event to be satisfied when both condition Z1-1 and condition Z1-2, as specified below, are fulfilled; + +1> consider the leaving condition for this event to be satisfied when condition Z1-3 or condition Z1-4, i.e. at least one of the two, as specified below, is fulfilled; + +Inequality Z1-1 (Entering condition 1) + +$M_r + Hys < Thresh1$ + +Inequality Z1-2 (Entering condition 2) + +$M_n - Hys > Thresh2$ + +Inequality Z1-3 (Leaving condition 1) + +$M_r - Hys > Thresh1$ + +Inequality Z1-4 (Leaving condition 2) + +$M_n + Hys < Thresh2$ + +The variables in the formula are defined as follows: + +**$M_r$** is the measurement result of the serving L2 U2N Relay UE, not taking into account any offsets. + +**$M_n$** is the measurement result of the candidate L2 U2N Relay UE, not taking into account any offsets. + +**$Hys$** is the hysteresis parameter for this event (i.e. *hysteresis* as defined within *reportConfigInterRAT* for this event). + +**$Thresh1$** is the threshold parameter for this event (i.e. *sl-rsrp* in *z1-Threshold1-Relay* as defined within *reportConfigInterRAT* if the UE measures SL-RSRP, or *sd-rsrp* in *z1-Threshold1-Relay* as defined within *reportConfigInterRAT* if the UE measures SD-RSRP for this event). + +**$Thresh2$** is the threshold parameter for this event (i.e. *z1-Threshold2-Relay* as defined within *reportConfigInterRAT* for this event). + +**$M_r$** is expressed in dBm or dB, depending on the measurement quantity of serving L2 U2N Relay UE. + +**$M_n$** is expressed in dBm or dB, depending on the measurement quantity of candidate L2 U2N Relay UE. + +**$Hys$** are expressed in dB. + +**$Thresh1$** is expressed in the same unit as **$M_r$** . + +**$Thresh2$** is expressed in the same unit as **$M_n$** . + +#### 5.5.4.21 Event H1 (The Aerial UE altitude becomes higher than a threshold) + +The UE shall: + +- 1> consider the entering condition for this event to be satisfied when condition H1-1, as specified below, is fulfilled; +- 1> consider the leaving condition for this event to be satisfied when condition H1-2, as specified below, is fulfilled; + +Inequality H1-1 (Entering condition) + +$$M_s - H_{ys} > T_{hresh}$$ + +Inequality H1-2 (Leaving condition) + +$$M_s + H_{ys} < T_{hresh}$$ + +The variables in the formula are defined as follows: + +***Ms*** is the Aerial UE altitude relative to the sea level. + +***Hys*** is the hysteresis parameter for this event (i.e. *h1-Hysteresis* as defined within *reportConfigNR* for this event). + +***Thresh*** is the threshold parameter for this event (i.e. *h1-Threshold* as defined within *reportConfigNR* for this event). + +***Ms, Hys, Thresh*** are expressed in meters. + +#### 5.5.4.22 Event H2 (The Aerial UE altitude becomes lower than a threshold) + +The UE shall: + +1> consider the entering condition for this event to be satisfied when condition H2-1, as specified below, is fulfilled; + +1> consider the leaving condition for this event to be satisfied when condition H2-2, as specified below, is fulfilled; + +Inequality H2-1 (Entering condition) + +$$M_s + H_{ys} < T_{hresh}$$ + +Inequality H2-2 (Leaving condition) + +$$M_s - H_{ys} > T_{hresh}$$ + +The variables in the formula are defined as follows: + +***Ms*** is the Aerial UE altitude relative to the sea level. + +***Hys*** is the hysteresis parameter for this event (i.e. *h2-Hysteresis* as defined within *reportConfigNR* for this event). + +***Thresh*** is the threshold parameter for this event (i.e. *h2-Threshold* as defined within *reportConfigNR* for this event). + +***Ms, Hys, Thresh*** are expressed in meters. + +#### 5.5.4.23 Event A3H1 (Neighbour becomes offset better than SpCell and the Aerial UE altitude becomes higher than a threshold) + +The UE shall: + +- 1> consider the entering condition for this event to be satisfied when both condition A3H1-1 and condition A3H1-2, as specified below, are fulfilled; +- 1> consider the leaving condition for this event to be satisfied when condition A3H1-3 or condition A3H1-4, i.e. at least one of the two, as specified below, is fulfilled; +- 1> use the SpCell for $M_p$ , $O_{fp}$ and $O_{cp}$ . + +NOTE 1: The cell(s) that triggers the event has reference signals indicated in the *measObjectNR* associated to this event which may be different from the NR SpCell *measObjectNR*. + +Inequality A3H1-1 (Entering condition 1) + +$$M_n + O_{fn} + O_{cn} - Hys1 > M_p + O_{fp} + O_{cp} + Off$$ + +Inequality A3H1-2 (Entering condition 2) + +$$M_s - Hys2 > Thresh$$ + +Inequality A3H1-3 (Leaving condition 1) + +$$M_n + O_{fn} + O_{cn} + Hys1 < M_p + O_{fp} + O_{cp} + Off$$ + +Inequality A3H1-4 (Leaving condition 2) + +$$M_s + Hys2 < Thresh$$ + +The variables in the formula are defined as follows: + +$M_n$ is the measurement result of the neighbouring cell, not taking into account any offsets. + +$O_{fn}$ is the measurement object specific offset of the reference signal of the neighbour cell (i.e. *offsetMO* as defined within *measObjectNR* corresponding to the neighbour cell). + +$O_{cn}$ is the cell specific offset of the neighbour cell (i.e. *cellIndividualOffset* as defined within *measObjectNR* corresponding to the frequency of the neighbour cell), and set to zero if not configured for the neighbour cell. + +$M_p$ is the measurement result of the SpCell, not taking into account any offsets. + +$O_{fp}$ is the measurement object specific offset of the SpCell (i.e. *offsetMO* as defined within *measObjectNR* corresponding to the SpCell). + +**Ocp** is the cell specific offset of the SpCell (i.e. *cellIndividualOffset* as defined within *measObjectNR* corresponding to the SpCell), and is set to zero if not configured for the SpCell. + +**Hys1** is the hysteresis parameter for this event (i.e. *a3-Hysteresis* as defined within *reportConfigNR* for this event). + +**Off** is the offset parameter for this event (i.e. *a3-Offset* as defined within *reportConfigNR* for this event). + +**Ms** is the Aerial UE altitude relative to the sea level. + +**Hys2** is the hysteresis parameter for this event (i.e. *h1-Hysteresis* as defined within *reportConfigNR* for this event). + +**Thresh** is the threshold parameter for this event (i.e. *h1-Threshold* as defined within *reportConfigNR* for this event). + +**Mn, Mp** are expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR. + +**Ofn, Ocn, Hys1, Ofp, Ocp, Off** are expressed in dB. + +**Ms, Hys2, Thresh** are expressed in meters. + +#### 5.5.4.24 Event A3H2 (Neighbour becomes offset better than SpCell and the Aerial UE altitude becomes lower than a threshold) + +The UE shall: + +- 1> consider the entering condition for this event to be satisfied when both condition A3H2-1 and condition A3H2-2, as specified below, are fulfilled; +- 1> consider the leaving condition for this event to be satisfied when condition A3H2-3 or condition A3H2-4, i.e. at least one of the two, as specified below, is fulfilled; +- 1> use the SpCell for *Mp, Ofp and Ocp*. + +NOTE: The cell(s) that triggers the event has reference signals indicated in the *measObjectNR* associated to this event which may be different from the NR SpCell *measObjectNR*. + +Inequality A3H2-1 (Entering condition 1) + +$$Mn + Ofn + Ocn - Hys1 > Mp + Ofp + Ocp + Off$$ + +Inequality A3H2-2 (Entering condition 2) + +$$Ms + Hys2 < Thresh$$ + +Inequality A3H2-3 (Leaving condition 1) + +$$Mn + Ofn + Ocn + Hys1 < Mp + Ofp + Ocp + Off$$ + +Inequality A3H1-4 (Leaving condition 2) + +$$M_s - Hys > Thresh$$ + +The variables in the formula are defined as follows: + +***Mn*** is the measurement result of the neighbouring cell, not taking into account any offsets. + +***Ofn*** is the measurement object specific offset of the reference signal of the neighbour cell (i.e. *offsetMO* as defined within *measObjectNR* corresponding to the neighbour cell). + +***Ocn*** is the cell specific offset of the neighbour cell (i.e. *cellIndividualOffset* as defined within *measObjectNR* corresponding to the frequency of the neighbour cell), and set to zero if not configured for the neighbour cell. + +***Mp*** is the measurement result of the SpCell, not taking into account any offsets. + +***Ofp*** is the measurement object specific offset of the SpCell (i.e. *offsetMO* as defined within *measObjectNR* corresponding to the SpCell). + +***Ocp*** is the cell specific offset of the SpCell (i.e. *cellIndividualOffset* as defined within *measObjectNR* corresponding to the SpCell), and is set to zero if not configured for the SpCell. + +***Hys1*** is the hysteresis parameter for this event (i.e. *a3-Hysteresis* as defined within *reportConfigNR* for this event). + +***Off*** is the offset parameter for this event (i.e. *a3-Offset* as defined within *reportConfigNR* for this event). + +***Ms*** is the Aerial UE altitude relative to the sea level. + +***Hys2*** is the hysteresis parameter for this event (i.e. *h2-Hysteresis* as defined within *reportConfigNR* for this event). + +***Thresh*** is the threshold parameter for this event (i.e. *h2-Threshold* as defined within *reportConfigNR* for this event). + +***Mn***, ***Mp*** are expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR. + +***Ofn***, ***Ocn***, ***Hys1***, ***Ofp***, ***Ocp***, ***Off*** are expressed in dB. + +***Ms***, ***Hys2***, ***Thresh*** are expressed in meters. + +#### 5.5.4.25 Event A4H1 (Neighbour becomes better than threshold1 and the Aerial UE altitude becomes higher than a threshold2) + +The UE shall: + +- 1> consider the entering condition for this event to be satisfied when both condition A4H1-1 and condition A4H1-2, as specified below, are fulfilled; +- 1> consider the leaving condition for this event to be satisfied when condition A4H1-3 or condition A4H1-4, i.e. at least one of the two, as specified below, is fulfilled. + +Inequality A4H1-1 (Entering condition 1) + +$$Mn + Ofn + Ocn - Hys1 > Thresh1$$ + +Inequality A4H1-2 (Entering condition 2) + +$$Ms - Hys2 > Thresh2$$ + +Inequality A4H1-3 (Leaving condition 1) + +$$Mn + Ofn + Ocn + Hys1 < Thresh1$$ + +Inequality A4H1-4 (Leaving condition 2) + +$$Ms + Hys2 < Thresh2$$ + +The variables in the formula are defined as follows: + +***Mn*** is the measurement result of the neighbouring cell, not taking into account any offsets. + +***Ofn*** is the measurement object specific offset of the neighbour cell (i.e. *offsetMO* as defined within *measObjectNR* corresponding to the neighbour cell). + +***Ocn*** is the measurement object specific offset of the neighbour cell (i.e. *cellIndividualOffset* as defined within *measObjectNR* corresponding to the neighbour cell), and set to zero if not configured for the neighbour cell. + +***Hys1*** is the hysteresis parameter for this event (i.e. *a4-Hysteresis* as defined within *reportConfigNR* for this event). + +***Thresh1*** is the threshold parameter for this event (i.e. *a4-Threshold* as defined within *reportConfigNR* for this event). + +***Ms*** is the Aerial UE altitude relative to the sea level. + +***Hys2*** is the hysteresis parameter for this event (i.e. *h1-Hysteresis* as defined within *reportConfigNR* for this event). + +***Thresh2*** is the threshold parameter for this event (i.e. *h1-Threshold* as defined within *reportConfigNR* for this event). + +***Mn*** is expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR. + +***Ofn***, ***Ocn***, ***Hys*** are expressed in dB. + +***Thresh1*** is expressed in the same unit as ***Mn***. + +***Ms***, ***Hys2***, ***Thresh2*** are expressed in meters. + +#### 5.5.4.26 Event A4H2 (Neighbour becomes better than threshold1 and the Aerial UE altitude becomes lower than a threshold2) + +The UE shall: + +1> consider the entering condition for this event to be satisfied when both condition A4H2-1 and condition A4H2-2, as specified below, are fulfilled; + +1> consider the leaving condition for this event to be satisfied when condition A4H2-3 or condition A4H2-4, i.e. at least one of the two, as specified below, is fulfilled. + +Inequality A4H2-1 (Entering condition 1) + +$$Mn + Ofn + Ocn - Hys1 > Thresh1$$ + +Inequality A4H2-2 (Entering condition 2) + +$$Ms + Hys2 < Thresh2$$ + +Inequality A4H2-3 (Leaving condition 1) + +$$Mn + Ofn + Ocn + Hys1 < Thresh1$$ + +Inequality A4H2-4 (Leaving condition 2) + +$$Ms - Hys2 > Thresh2$$ + +The variables in the formula are defined as follows: + +***Mn*** is the measurement result of the neighbouring cell, not taking into account any offsets. + +***Ofn*** is the measurement object specific offset of the neighbour cell (i.e. *offsetMO* as defined within *measObjectNR* corresponding to the neighbour cell). + +***Ocn*** is the measurement object specific offset of the neighbour cell (i.e. *cellIndividualOffset* as defined within *measObjectNR* corresponding to the neighbour cell), and set to zero if not configured for the neighbour cell. + +***Hys1*** is the hysteresis parameter for this event (i.e. *a4-Hysteresis* as defined within *reportConfigNR* for this event). + +***Thresh1*** is the threshold parameter for this event (i.e. *a4-Threshold* as defined within *reportConfigNR* for this event). + +***Ms*** is the Aerial UE altitude relative to the sea level. + +***Hys2*** is the hysteresis parameter for this event (i.e. *h2-Hysteresis* as defined within *reportConfigNR* for this event). + +***Thresh2*** is the threshold parameter for this event (i.e. *h2-Threshold* as defined within *reportConfigNR* for this event). + +***Mn*** is expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR. + +*Ofn, Ocn, Hys* are expressed in dB. + +*Thresh1* is expressed in the same unit as *Mn*. + +*Ms, Hys2, Thresh2* are expressed in meters. + +#### 5.5.4.27 Event A5H1 (SpCell becomes worse than threshold1 and neighbour becomes better than threshold2 and the Aerial UE altitude becomes higher than a threshold3) + +The UE shall: + +- 1> consider the entering condition for this event to be satisfied when all of condition A5H1-1 and condition A5H1-2 and condition A5H1-3, as specified below, are fulfilled; +- 1> consider the leaving condition for this event to be satisfied when condition A5H1-4 or condition A5H1-5 or condition A5H1-6, i.e. at least one of the three, as specified below, is fulfilled; +- 1> use the SpCell for *Mp*. + +NOTE: The parameters of the reference signal(s) of the cell(s) that triggers the event are indicated in the *measObjectNR* associated to the event which may be different from the *measObjectNR* of the NR SpCell. + +Inequality A5H1-1 (Entering condition 1) + +$$Mp + Hys1 < Thresh1$$ + +Inequality A5H1-2 (Entering condition 2) + +$$Mn + Ofn + Ocn - Hys1 > Thresh2$$ + +Inequality A5H1-3 (Entering condition 3) + +$$Ms - Hys2 > Thresh3$$ + +Inequality A5H1-4 (Leaving condition 1) + +$$Mp - Hys1 > Thresh1$$ + +Inequality A5H1-5 (Leaving condition 2) + +$$Mn + Ofn + Ocn + Hys1 < Thresh2$$ + +Inequality A5H1-6 (Leaving condition 3) + +$$Ms + Hys2 < Thresh3$$ + +The variables in the formula are defined as follows: + +***Mp*** is the measurement result of the NR SpCell, not taking into account any offsets. + +***Mn*** is the measurement result of the neighbouring cell, not taking into account any offsets. + +***Ofn*** is the measurement object specific offset of the neighbour cell (i.e. *offsetMO* as defined within *measObjectNR* corresponding to the neighbour cell). + +***Ocn*** is the cell specific offset of the neighbour cell (i.e. *cellIndividualOffset* as defined within *measObjectNR* corresponding to the neighbour cell), and set to zero if not configured for the neighbour cell. + +***Hys1*** is the hysteresis parameter for this event (i.e. *a5-Hysteresis* as defined within *reportConfigNR* for this event). + +***Thresh1*** is the threshold parameter for this event (i.e. *a5-Threshold1* as defined within *reportConfigNR* for this event). + +***Thresh2*** is the threshold parameter for this event (i.e. *a5-Threshold2* as defined within *reportConfigNR* for this event). + +***Ms*** is the Aerial UE altitude relative to the sea level. + +***Hys2*** is the hysteresis parameter for this event (i.e. *h1-Hysteresis* as defined within *reportConfigNR* for this event). + +***Thresh3*** is the threshold parameter for this event (i.e. *h1-Threshold* as defined within *reportConfigNR* for this event). + +***Mn***, ***Mp*** are expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR. + +***Ofn***, ***Ocn***, ***Hys*** are expressed in dB. + +***Thresh1*** is expressed in the same unit as ***Mp***. + +***Thresh2*** is expressed in the same unit as ***Mn***. + +***Ms***, ***Hys2***, ***Thresh3*** are expressed in meters. + +#### 5.5.4.28 Event A5H2 (SpCell becomes worse than threshold1 and neighbour becomes better than threshold2 and the Aerial UE altitude becomes lower than a threshold3) + +The UE shall: + +- 1> consider the entering condition for this event to be satisfied when all of condition A5H2-1 and condition A5H2-2 and condition A5H2-3, as specified below, are fulfilled; +- 1> consider the leaving condition for this event to be satisfied when condition A5H2-4 or condition A5H2-5 or condition A5H2-6, i.e. at least one of the three, as specified below, is fulfilled; +- 1> use the SpCell for ***Mp***. + +NOTE: The parameters of the reference signal(s) of the cell(s) that triggers the event are indicated in the *measObjectNR* associated to the event which may be different from the *measObjectNR* of the NR SpCell. + +Inequality A5H2-1 (Entering condition 1) + +$$Mp + Hys1 < Thresh1$$ + +Inequality A5H2-2 (Entering condition 2) + +$$Mn + Ofn + Ocn - Hys1 > Thresh2$$ + +Inequality A5H2-3 (Entering condition 3) + +$$Ms + Hys2 < Thresh3$$ + +Inequality A5H2-4 (Leaving condition 1) + +$$Mp - Hys1 > Thresh1$$ + +Inequality A5H2-5 (Leaving condition 2) + +$$Mn + Ofn + Ocn + Hys1 < Thresh2$$ + +Inequality A5H2-6 (Leaving condition 3) + +$$Ms - Hys2 > Thresh3$$ + +The variables in the formula are defined as follows: + +***Mp*** is the measurement result of the NR SpCell, not taking into account any offsets. + +***Mn*** is the measurement result of the neighbouring cell, not taking into account any offsets. + +***Ofn*** is the measurement object specific offset of the neighbour cell (i.e. *offsetMO* as defined within *measObjectNR* corresponding to the neighbour cell). + +***Ocn*** is the cell specific offset of the neighbour cell (i.e. *cellIndividualOffset* as defined within *measObjectNR* corresponding to the neighbour cell), and set to zero if not configured for the neighbour cell. + +***Hys1*** is the hysteresis parameter for this event (i.e. *a5-Hysteresis* as defined within *reportConfigNR* for this event). + +***Thresh1*** is the threshold parameter for this event (i.e. *a5-Threshold1* as defined within *reportConfigNR* for this event). + +***Thresh2*** is the threshold parameter for this event (i.e. *a5-Threshold2* as defined within *reportConfigNR* for this event). + +*Ms* is the Aerial UE altitude relative to the sea level. + +*Hys2* is the hysteresis parameter for this event (i.e. *h2-Hysteresis* as defined within *reportConfigNR* for this event). + +*Thresh3* is the threshold parameter for this event (i.e. *h2-Threshold* as defined within *reportConfigNR* for this event). + +*Mn*, *Mp* are expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR. + +*Ofn*, *Ocn*, *Hys* are expressed in dB. + +*Thresh1* is expressed in the same unit as *Mp*. + +*Thresh2* is expressed in the same unit as *Mn*. + +*Ms*, *Hys2*, *Thresh3* are expressed in meters. + +### 5.5.5 Measurement reporting + +#### 5.5.5.1 General + +![Sequence diagram showing a UE sending a MeasurementReport message to a Network.](f806f2cd3ad03aea066cdb9a93f5bf56_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Network + Note left of UE: + UE->>Network: MeasurementReport + Note right of Network: + +``` + +The diagram illustrates a sequence of interactions between a User Equipment (UE) and a Network. The UE is represented by a box on the left, and the Network by a box on the right. A horizontal arrow labeled *MeasurementReport* points from the UE to the Network, indicating the transfer of measurement results. + +Sequence diagram showing a UE sending a MeasurementReport message to a Network. + +Figure 5.5.5.1-1: Measurement reporting + +The purpose of this procedure is to transfer measurement results from the UE to the network. The UE shall initiate this procedure only after successful AS security activation. + +For the *measId* for which the measurement reporting procedure was triggered, the UE shall set the *measResults* within the *MeasurementReport* message as follows: + +- 1> set the *measId* to the measurement identity that triggered the measurement reporting; +- 1> for each serving cell configured with *servingCellMO*: + - 2> if the *reportConfig* associated with the *measId* that triggered the measurement reporting includes *rsType*: + - 3> if the serving cell measurements based on the *rsType* included in the *reportConfig* that triggered the measurement report are available: + +- 4> set the *measResultServingCell* within *measResultServingMOList* to include RSRP, RSRQ and the available SINR of the serving cell, derived based on the *rsType* included in the *reportConfig* that triggered the measurement report; + - 2> else: + - 3> if SSB based serving cell measurements are available: + - 4> set the *measResultServingCell* within *measResultServingMOList* to include RSRP, RSRQ and the available SINR of the serving cell, derived based on SSB; + - 3> else if CSI-RS based serving cell measurements are available: + - 4> set the *measResultServingCell* within *measResultServingMOList* to include RSRP, RSRQ and the available SINR of the serving cell, derived based on CSI-RS; + - 1> set the *servCellId* within *measResultServingMOList* to include each NR serving cell that is configured with *servingCellMO*, if any; + - 1> if the *reportConfig* associated with the *measId* that triggered the measurement reporting includes *reportQuantityRS-Indexes* and *maxNrofRS-IndexesToReport*: + - 2> for each serving cell configured with *servingCellMO*, include beam measurement information according to the associated *reportConfig* as described in 5.5.5.2; + - 1> if the *reportConfig* associated with the *measId* that triggered the measurement reporting includes *reportAddNeighMeas*: + - 2> for each *measObjectId* referenced in the *measIdList* which is also referenced with *servingCellMO*, other than the *measObjectId* corresponding with the *measId* that triggered the measurement reporting: + - 3> if the *measObjectNR* indicated by the *servingCellMO* includes the RS resource configuration corresponding to the *rsType* indicated in the *reportConfig*: + - 4> set the *measResultBestNeighCell* within *measResultServingMOList* to include the *physCellId* and the available measurement quantities based on the *reportQuantityCell* and *rsType* indicated in *reportConfig* of the non-serving cell corresponding to the concerned *measObjectNR* with the highest measured RSRP if RSRP measurement results are available for cells corresponding to this *measObjectNR*, otherwise with the highest measured RSRQ if RSRQ measurement results are available for cells corresponding to this *measObjectNR*, otherwise with the highest measured SINR; + - 4> if the *reportConfig* associated with the *measId* that triggered the measurement reporting includes *reportQuantityRS-Indexes* and *maxNrofRS-IndexesToReport*: + - 5> for each best non-serving cell included in the measurement report: + - 6> include beam measurement information according to the associated *reportConfig* as described in 5.5.5.2; +- 1> if the *reportConfig* associated with the *measId* that triggered the measurement reporting is set to *eventTriggered* and *eventID* is set to *eventA3*, or *eventA4*, or *eventA5*, or *eventB1*, or *eventB2*, or *eventA3H1*, or *eventA3H2*, or *eventA4H1*, or *eventA4H2*, or *eventA5H1*, or *eventA5H2*: + - 2> if the UE is in NE-DC and the measurement configuration that triggered this measurement report is associated with the MCG: + - 3> set the *measResultServFreqListEUTRA-SCG* to include an entry for each E-UTRA SCG serving frequency with the following: + +- 4> include *carrierFreq* of the E-UTRA serving frequency; +- 4> set the *measResultServingCell* to include the available measurement quantities that the UE is configured to measure by the measurement configuration associated with the SCG; +- 4> if *reportConfig* associated with the *measId* that triggered the measurement reporting includes *reportAddNeighMeas*: + - 5> set the *measResultServFreqListEUTRA-SCG* to include within *measResultBestNeighCell* the quantities of the best non-serving cell, based on RSRP, on the concerned serving frequency; +- 1> if *reportConfig* associated with the *measId* that triggered the measurement reporting is set to *eventTriggered* and *eventID* is set to *eventA3*, or *eventA4*, or *eventA5*, or *eventA3H1*, or *eventA3H2*, or *eventA4H1*, or *eventA4H2*, or *eventA5H1*, or *eventA5H2*: + - 2> if the UE is in NR-DC and the measurement configuration that triggered this measurement report is associated with the MCG: + - 3> set the *measResultServFreqListNR-SCG* to include for each NR SCG serving cell that is configured with *servingCellMO*, if any, the following: + - 4> if the *reportConfig* associated with the *measId* that triggered the measurement reporting includes *rsType*: + - 5> if the serving cell measurements based on the *rsType* included in the *reportConfig* that triggered the measurement report are available according to the measurement configuration associated with the SCG: + - 6> set the *measResultServingCell* within *measResultServFreqListNR-SCG* to include RSRP, RSRQ and the available SINR of the serving cell, derived based on the *rsType* included in the *reportConfig* that triggered the measurement report; + - 4> else: + - 5> if SSB based serving cell measurements are available according to the measurement configuration associated with the SCG: + - 6> set the *measResultServingCell* within *measResultServFreqListNR-SCG* to include RSRP, RSRQ and the available SINR of the serving cell, derived based on SSB; + - 5> else if CSI-RS based serving cell measurements are available according to the measurement configuration associated with the SCG: + - 6> set the *measResultServingCell* within *measResultServFreqListNR-SCG* to include RSRP, RSRQ and the available SINR of the serving cell, derived based on CSI-RS; + - 4> if results for the serving cell derived based on SSB are included: + - 5> include the *ssbFrequency* to the value indicated by ssbFrequency as included in the *MeasObjectNR* of the serving cell; + - 4> if results for the serving cell derived based on CSI-RS are included: + - 5> include the *refFreqCSI-RS* to the value indicated by *refFreqCSI-RS* as included in the *MeasObjectNR* of the serving cell; + +4> if the *reportConfig* associated with the *measId* that triggered the measurement reporting includes *reportQuantityRS-Indexes* and *maxNrofRS-IndexesToReport*: + +5> for each serving cell configured with *servingCellMO*, include beam measurement information according to the associated *reportConfig* as described in 5.5.5.2, where availability is considered according to the measurement configuration associated with the SCG; + +4> if *reportConfig* associated with the *measId* that triggered the measurement reporting includes *reportAddNeighMeas*: + +5> if the *measObjectNR* indicated by the *servingCellMO* includes the RS resource configuration corresponding to the *rsType* indicated in the *reportConfig*: + +6> set the *measResultNeighCellListNR* within *measResultServFreqListNR-SCG* to include one entry with the *physCellId* and the available measurement quantities based on the *reportQuantityCell* and *rsType* indicated in *reportConfig* of the non-serving cell corresponding to the concerned *measObjectNR* with the highest measured RSRP if RSRP measurement results are available for cells corresponding to this *measObjectNR*, otherwise with the highest measured RSRQ if RSRQ measurement results are available for cells corresponding to this *measObjectNR*, otherwise with the highest measured SINR, where availability is considered according to the measurement configuration associated with the SCG; + +7> if the *reportConfig* associated with the *measId* that triggered the measurement reporting includes *reportQuantityRS-Indexes* and *maxNrofRS-IndexesToReport*: + +8> for each best non-serving cell included in the measurement report: + +9> include beam measurement information according to the associated *reportConfig* as described in 5.5.5.2, where availability is considered according to the measurement configuration associated with the SCG; + +1> if the *measRSST-ReportConfig* is configured within the corresponding *reportConfig* for this *measId*: + +2> set the *rssi-Result* to the linear average of sample value(s) provided by lower layers in the *reportInterval*; + +2> set the *channelOccupancy* to the rounded percentage of sample values which are beyond the *channelOccupancyThreshold* within all the sample values in the *reportInterval*; + +1> if the UE is acting as L2 U2N Remote UE: + +2> set the *sl-MeasResultServingRelay* in accordance with the following: + +3> set the *cellIdentity* to include the *cellAccessRelatedInfo* contained in the discovery message received from the serving L2 U2N Relay UE; + +3> set the *sl-RelayUE-Identity* to include the Source L2 ID of the serving L2 U2N Relay; + +3> if the measurement of serving L2 U2N Relay UE is based on SL-RSRP: + +4> set the *sl-MeasResult* to include the SL-RSRP of the serving L2 U2N Relay UE; + +4> set the *sl-MeasQuantity* to SL-RSRP, if supported by the UE; + +3> else: + +4> set the *sl-MeasResult* to include the SD-RSRP of the serving L2 U2N Relay UE; + +4> set the *sl-MeasQuantity* to SD-RSRP, if supported by the UE; + +NOTE 1: In case of no data transmission from L2 U2N Relay UE to L2 U2N Remote UE, it is left to UE implementation whether to use SL-RSRP or SD-RSRP when setting the *sl-MeasResultServingRelay* of the serving L2 U2N Relay UE. + +1> if there is at least one applicable neighbouring cell or candidate L2 U2N Relay UE to report: + +2> if the *reportType* is set to *eventTriggered* or *periodical*: + +3> if the measurement report concerns the candidate L2 U2N Relay UE: + +4> set the *sl-MeasResultsCandRelay* in *measResultNeighCells* to include the best candidate L2 U2N Relay UEs up to *maxNrofRelayMeas* in accordance with the following: + +5> if the *reportType* is set to *eventTriggered*: + +6> include the L2 U2N Relay UEs included in the *relaysTriggeredList* as defined within the *VarMeasReportList* for this *measId*; + +5> else: + +6> include the applicable L2 U2N Relay UEs for which the new measurement results became available since the last periodical reporting or since the measurement was initiated or reset; + +5> for each L2 U2N Relay UE that is included in the *sl-MeasResultsCandRelay*: + +6> set the *cellIdentity* to include the *cellAccessRelatedInfo* contained in the discovery message received from the concerned L2 U2N Relay UE; + +6> set the *sl-RelayUE-Identity* to include the Source L2 ID of the concerned L2 U2N Relay UE; + +6> set the *sl-MeasResult* to include the SD-RSRP of the concerned L2 U2N Relay UE; + +5> for each included L2 U2N Relay UE, include the layer 3 filtered measured results in accordance with the *reportConfig* for this *measId*, ordered as follows: + +6> set the *sl-MeasResult* to include the quantity(ies) indicated in the *reportQuantityRelay* within the concerned *reportConfigRelay* in decreasing order of the sorting quantity, determined as specified in 5.5.5.3, i.e. the best L2 U2N Relay UE is included first; + +3> else: + +4> set the *measResultNeighCells* to include the best neighbouring cells up to *maxReportCells* in accordance with the following: + +- 5> if the *reportType* is set to *eventTriggered* and *eventId* is not set to *eventD1* or *eventH1* or *eventH2*: + - 6> include the cells included in the *cellsTriggeredList* as defined within the *VarMeasReportList* for this *measId*; + - 5> else: + - 6> include the applicable cells for which the new measurement results became available since the last periodical reporting or since the measurement was initiated or reset; + - 5> for each cell that is included in the *measResultNeighCells*, include the *physCellId*; + - 5> if the *reportType* is set to *eventTriggered* or *periodical*: + - 6> for each included cell, include the layer 3 filtered measured results in accordance with the *reportConfig* for this *measId*, ordered as follows: + - 7> if the *measObject* associated with this *measId* concerns NR: + - 8> if *rsType* in the associated *reportConfig* is set to *ssb*: + - 9> set *resultsSSB-Cell* within the *measResult* to include the SS/PBCH block based quantity(ies) indicated in the *reportQuantityCell* within the concerned *reportConfig*, in decreasing order of the sorting quantity, determined as specified in 5.5.5.3, i.e. the best cell is included first; + - 9> if *reportQuantityRS-Indexes* and *maxNrofRS-IndexesToReport* are configured, include beam measurement information as described in 5.5.5.2; + - 8> else if *rsType* in the associated *reportConfig* is set to *csi-rs*: + - 9> set *resultsCSI-RS-Cell* within the *measResult* to include the CSI-RS based quantity(ies) indicated in the *reportQuantityCell* within the concerned *reportConfig*, in decreasing order of the sorting quantity, determined as specified in 5.5.5.3, i.e. the best cell is included first; + - 9> if *reportQuantityRS-Indexes* and *maxNrofRS-IndexesToReport* are configured, include beam measurement information as described in 5.5.5.2; + - 7> if the *measObject* associated with this *measId* concerns E-UTRA: + - 8> set the *measResult* to include the quantity(ies) indicated in the *reportQuantity* within the concerned *reportConfigInterRAT* in decreasing order of the sorting quantity, determined as specified in 5.5.5.3, i.e. the best cell is included first; + - 7> if the *measObject* associated with this *measId* concerns UTRA-FDD and if *ReportConfigInterRAT* includes the *reportQuantityUTRA-FDD*: + - 8> set the *measResult* to include the quantity(ies) indicated in the *reportQuantityUTRA-FDD* within the concerned *reportConfigInterRAT* in decreasing order of the sorting quantity, determined as specified in 5.5.5.3, i.e. the best cell is included first; +- 2> else: + - 3> if the cell indicated by *cellForWhichToReportCGI* is an NR cell: + +- 4> if *plmn-IdentityInfoList* of the *cgi-Info* for the concerned cell has been obtained: + - 5> include the *plmn-IdentityInfoList* including *plmn-IdentityList*, *trackingAreaCode* (if available), *trackingAreaList* (if available), *ranac* (if available), *cellIdentity* and *cellReservedForOperatorUse* for each entry of the *plmn-IdentityInfoList*; + - 5> include *frequencyBandList* if available; + - 5> for each *PLMN-IdentityInfo* in *plmn-IdentityInfoList*: + - 6> if the *gNB-ID-Length* is broadcast: + - 7> include *gNB-ID-Length*; +- 4> if *nr-CGI-Reporting-NPN* is supported by the UE and *npn-IdentityInfoList* of the *cgi-Info* for the concerned cell has been obtained: + - 5> include the *npn-IdentityInfoList* including *npn-IdentityList*, *trackingAreaCode*, *ranac* (if available), *cellIdentity* and *cellReservedForOperatorUse* for each entry of the *npn-IdentityInfoList*; + - 5> for each *NPN-IdentityInfo* in *NPN-IdentityInfoList*: + - 6> if the *gNB-ID-Length* is broadcast: + - 7> include *gNB-ID-Length*; + - 5> include *cellReservedForOtherUse* if available; +- 4> else if *MIB* indicates the *SIB1* is not broadcast: + - 5> include the *noSIB1* including the *ssb-SubcarrierOffset* and *pdch-ConfigSIB1* obtained from *MIB* of the concerned cell; +- 3> if the cell indicated by *cellForWhichToReportCGI* is an E-UTRA cell: + - 4> if all mandatory fields of the *cgi-Info-EPC* for the concerned cell have been obtained: + - 5> include in the *cgi-Info-EPC* the fields broadcasted in E-UTRA *SystemInformationBlockType1* associated to EPC; + - 4> if the UE is E-UTRA/5GC capable and all mandatory fields of the *cgi-Info-5GC* for the concerned cell have been obtained: + - 5> include in the *cgi-Info-5GC* the fields broadcasted in E-UTRA *SystemInformationBlockType1* associated to 5GC; + - 4> if the mandatory present fields of the *cgi-Info* for the cell indicated by the *cellForWhichToReportCGI* in the associated *measObject* have been obtained: + - 5> include the *freqBandIndicator*; + +5> if the cell broadcasts the *multiBandInfoList*, include the *multiBandInfoList*; + +5> if the cell broadcasts the *freqBandIndicatorPriority*, include the *freqBandIndicatorPriority*; + +1> if the corresponding *measObject* concerns NR: + +2> if the *reportSFTD-Meas* is set to *true* within the corresponding *reportConfigNR* for this *measId*: + +3> set the *measResultSFTD-NR* in accordance with the following: + +4> set *sfn-OffsetResult* and *frameBoundaryOffsetResult* to the measurement results provided by lower layers; + +4> if the *reportRSRP* is set to *true*; + +5> set *rsrp-Result* to the RSRP of the NR PSCell derived based on SSB; + +2> else if the *reportSFTD-NeighMeas* is included within the corresponding *reportConfigNR* for this *measId*: + +3> for each applicable cell which measurement results are available, include an entry in the *measResultCellListSFTD-NR* and set the contents as follows: + +4> set *physCellId* to the physical cell identity of the concerned NR neighbour cell. + +4> set *sfn-OffsetResult* and *frameBoundaryOffsetResult* to the measurement results provided by lower layers; + +4> if the *reportRSRP* is set to *true*: + +5> set *rsrp-Result* to the RSRP of the concerned cell derived based on SSB; + +1> else if the corresponding *measObject* concerns E-UTRA: + +2> if the *reportSFTD-Meas* is set to *true* within the corresponding *reportConfigInterRAT* for this *measId*: + +3> set the *measResultSFTD-EUTRA* in accordance with the following: + +4> set *sfn-OffsetResult* and *frameBoundaryOffsetResult* to the measurement results provided by lower layers; + +4> if the *reportRSRP* is set to *true*; + +5> set *rsrpResult-EUTRA* to the RSRP of the EUTRA PSCell; + +1> if average uplink PDCP delay values are available: + +2> set the *ul-PDCP-DelayValueResultList* to include the corresponding average uplink PDCP delay values; + +1> if PDCP excess delay measurements are available: + +- 2> set the *ul-PDCP-ExcessDelayResultList* to include the corresponding PDCP excess delay measurements; +- 1> if the *includeCommonLocationInfo* is configured in the corresponding *reportConfig* for this *measId* and detailed location information that has not been reported is available, set the content of *commonLocationInfo* of the *locationInfo* as follows: + - 2> include the *locationTimestamp*; + - 2> include the *locationCoordinate*, if available; + - 2> include the *velocityEstimate*, if available; + - 2> include the *locationError*, if available; + - 2> include the *locationSource*, if available; + - 2> if available, include the *gnss-TOD-msec*, +- 1> if the *coarseLocationRequest* is set to *true* in the corresponding *reportConfig* for this *measId*: + - 2> include *coarseLocationInfo*, if available; +- 1> if the *includeWLAN-Meas* is configured in the corresponding *reportConfig* for this *measId*, set the *wlan-LocationInfo* of the *locationInfo* in the *measResults* as follows: + - 2> if available, include the *LogMeasResultWLAN*, in order of decreasing RSSI for WLAN APs; +- 1> if the *includeBT-Meas* is configured in the corresponding *reportConfig* for this *measId*, set the *BT-LocationInfo* of the *locationInfo* in the *measResults* as follows: + - 2> if available, include the *LogMeasResultBT*, in order of decreasing RSSI for Bluetooth beacons; +- 1> if the *includeSensor-Meas* is configured in the corresponding *reportConfig* for this *measId*, set the *sensor-LocationInfo* of the *locationInfo* in the *measResults* as follows: + - 2> if available, include the *sensor-MeasurementInformation*; + - 2> if available, include the *sensor-MotionInformation*; +- 1> if the *includeAltitudeUE* is configured in the corresponding *reportConfig* for this *measId*: + - 2> set the *altitudeUE* to include the altitude of the UE; +- 1> if there is at least one applicable transmission resource pool for NR sidelink communication/discovery (for *measResultsSL*): + - 2> set the *measResultsListSL* to include the CBR measurement results in accordance with the following: + - 3> if the *reportType* is set to *eventTriggered*: + +- 4> include the transmission resource pools included in the *poolsTriggeredList* as defined within the *VarMeasReportList* for this *measId*; +- 3> else: + - 4> include the applicable transmission resource pools for which the new measurement results became available since the last periodical reporting or since the measurement was initiated or reset; +- 3> if the corresponding *measObject* concerns NR sidelink communication/discovery, then for each transmission resource pool to be reported: + - 4> set the *sl-poolReportIdentity* to the identity of this transmission resource pool; + - 4> set the *sl-CBR-ResultsNR* to the CBR measurement results on PSSCH and PSCCH of this transmission resource pool provided by lower layers, if available; + +NOTE 1: Void. + +- 1> if there is at least one applicable CLI measurement resource to report: + - 2> if the *reportType* is set to *cli-EventTriggered* or *cli-Periodical*: + - 3> set the *measResultCLI* to include the most interfering SRS resources or most interfering CLI-RSSI resources up to *maxReportCLI* in accordance with the following: + - 4> if the *reportType* is set to *cli-EventTriggered*: + - 5> if trigger quantity is set to *srs-RSRP* i.e. *i1-Threshold* is set to *srs-RSRP*: + - 6> include the SRS resource included in the *cli-TriggeredList* as defined within the *VarMeasReportList* for this *measId*; + - 5> if trigger quantity is set to *cli-RSSI* i.e. *i1-Threshold* is set to *cli-RSSI*: + - 6> include the CLI-RSSI resource included in the *cli-TriggeredList* as defined within the *VarMeasReportList* for this *measId*; + - 4> else: + - 5> if *reportQuantityCLI* is set to *srs-rsrp*: + - 6> include the applicable SRS resources for which the new measurement results became available since the last periodical reporting or since the measurement was initiated or reset; + - 5> else: + - 6> include the applicable CLI-RSSI resources for which the new measurement results became available since the last periodical reporting or since the measurement was initiated or reset; + - 4> for each SRS resource that is included in the *measResultCLI*: + +- 5> include the *srs-ResourceId*; + - 5> set *srs-RSRP-Result* to include the layer 3 filtered measured results in decreasing order, i.e. the most interfering SRS resource is included first; +- 4> for each CLI-RSSI resource that is included in the *measResultCLI*: + - 5> include the *rssi-ResourceId*; + - 5> set *cli-RSSI-Result* to include the layer 3 filtered measured results in decreasing order, i.e. the most interfering CLI-RSSI resource is included first; +- 1> if there is at least one applicable UE Rx-Tx time difference measurement to report: + - 2> set *measResultRxTxTimeDiff* to the latest measurement result; +- 1> increment the *numberOfReportsSent* as defined within the *VarMeasReportList* for this *measId* by 1; +- 1> stop the periodical reporting timer, if running; +- 1> if the *numberOfReportsSent* as defined within the *VarMeasReportList* for this *measId* is less than the *reportAmount* as defined within the corresponding *reportConfig* for this *measId*: + - 2> start the periodical reporting timer with the value of *reportInterval* as defined within the corresponding *reportConfig* for this *measId*; +- 1> else: + - 2> if the *reportType* is set to *periodical* or *cli-Periodical* or *rxTxPeriodical*: + - 3> remove the entry within the *VarMeasReportList* for this *measId*; + - 3> remove this *measId* from the *measIdList* within *VarMeasConfig*; +- 1> if the measurement reporting was configured by a *sl-ConfigDedicatedNR* received within the *RRCConnectionReconfiguration*: + - 2> submit the *MeasurementReport* message to lower layers for transmission via SRB1, embedded in E-UTRA RRC message *ULInformationTransferIRAT* as specified TS 36.331 [10], clause 5.6.28; +- 1> else if the UE is in (NG)EN-DC: + - 2> if SRB3 is configured and the SCG is not deactivated: + - 3> submit the *MeasurementReport* message via SRB3 to lower layers for transmission, upon which the procedure ends; + - 2> else: + +3> submit the *MeasurementReport* message via E-UTRA embedded in E-UTRA RRC message *ULInformationTransferMRDC* as specified in TS 36.331 [10]. + +1> else if the UE is in NR-DC: + +2> if the measurement configuration that triggered this measurement report is associated with the SCG: + +3> if SRB3 is configured and the SCG is not deactivated: + +4> submit the *MeasurementReport* message via SRB3 to lower layers for transmission, upon which the procedure ends; + +3> else: + +4> submit the *MeasurementReport* message via SRB1 embedded in NR RRC message *ULInformationTransferMRDC* as specified in 5.7.2a.3; + +2> else: + +3> submit the *MeasurementReport* message via SRB1 to lower layers for transmission, upon which the procedure ends; + +1> else: + +2> submit the *MeasurementReport* message to lower layers for transmission, upon which the procedure ends. + +#### 5.5.5.2 Reporting of beam measurement information + +For beam measurement information to be included in a measurement report the UE shall: + +1> if *reportType* is set to *eventTriggered* or *reportOnScellActivation*: + +2> consider the trigger quantity as the sorting quantity if available, otherwise RSRP as sorting quantity if available, otherwise RSRQ as sorting quantity if available, otherwise SINR as sorting quantity; + +1> if *reportType* is set to *periodical*: + +2> if a single reporting quantity is set to *true* in *reportQuantityRS-Indexes*: + +3> consider the configured single quantity as the sorting quantity; + +2> else: + +3> if *rsrp* is set to *true*: + +4> consider RSRP as the sorting quantity; + +3> else: + +- 4> consider RSRQ as the sorting quantity; +- 1> set *rsIndexResults* to include up to *maxNrofRS-IndexesToReport* SS/PBCH block indexes or CSI-RS indexes in order of decreasing sorting quantity as follows: + - 2> if the measurement information to be included is based on SS/PBCH block: + - 3> include within *resultsSSB-Indexes* the index associated to the best beam for that SS/PBCH block sorting quantity and if *absThreshSS-BlocksConsolidation* is included in the *VarMeasConfig* for the *measObject* associated to the cell for which beams are to be reported, the remaining beams whose sorting quantity is above *absThreshSS-BlocksConsolidation*; + - 3> if *includeBeamMeasurements* is set to *true*, include the SS/PBCH based measurement results for the quantities in *reportQuantityRS-Indexes* for each SS/PBCH block index; + - 2> else if the beam measurement information to be included is based on CSI-RS: + - 3> include within *resultsCSI-RS-Indexes* the index associated to the best beam for that CSI-RS sorting quantity and, if *absThreshCSI-RS-Consolidation* is included in the *VarMeasConfig* for the *measObject* associated to the cell for which beams are to be reported, the remaining beams whose sorting quantity is above *absThreshCSI-RS-Consolidation*; + - 3> if *includeBeamMeasurements* is set to *true*, include the CSI-RS based measurement results for the quantities in *reportQuantityRS-Indexes* for each CSI-RS index. + +#### 5.5.5.3 Sorting of cell measurement results + +The UE shall determine the sorting quantity according to parameters of the *reportConfig* associated with the *measId* that triggered the reporting: + +- 1> if the *reportType* is set to *eventTriggered*: + - 2> for an NR cell, consider the quantity used in the *aN-Threshold* (for *eventA1*, *eventA2*, *eventA4*, *eventA4H1* and *eventA4H2*) or in the *a5-Threshold2* (for *eventA5*, *eventA5H1* and *eventA5H2*) or in the *aN-Offset* (for *eventA3*, *eventA3H1*, *eventA3H2* and *eventA6*) or in the *x1-Threshold2* (for *eventX1*) as the sorting quantity; + - 2> for an E-UTRA cell, consider the quantity used in the *bN-ThresholdEUTRA* as the sorting quantity; + - 2> for an UTRA-FDD cell, consider the quantity used in the *bN-ThresholdUTRA-FDD* as the sorting quantity; + - 2> for a candidate L2 U2N Relay UE, consider the *y1-Threshold2-Relay* (for *eventY1-Relay*) or *y2-Threshold-Relay* (for *eventY2-Relay*) or *z1-Threshold2-Relay* (for *eventZ1*) as the sorting quantity; +- 1> if the *reportType* is set to *periodical*: + - 2> determine the sorting quantity according to *reportQuantityCell* for an NR cell, and according to *reportQuantity* for an E-UTRA cell, as below: + - 3> if a single quantity is set to *true*: + - 4> consider this quantity as the sorting quantity; + +- 3> else: + - 4> if *rsrp* is set to *true*: + - 5> consider RSRP as the sorting quantity; + - 4> else: + - 5> consider RSRQ as the sorting quantity; +- 2> determine the sorting quantity according to *reportQuantityUTRA-FDD* for UTRA-FDD cell, as below: + - 3> if a single quantity is set to *true*: + - 4> consider this quantity as the sorting quantity; + - 3> else: + - 4> consider RSCP as the sorting quantity. +- 2> for a candidate L2 U2N Relay UE, consider the *reportQuantityRelay* as the sorting quantity; + +### 5.5.6 Location measurement indication + +#### 5.5.6.1 General + +![Sequence diagram showing the Location measurement indication procedure between a UE and a Network.](902baf7323e91b89aba4ea27d9c3d13d_img.jpg) + +``` +sequenceDiagram + participant UE + participant Network + Note left of UE: + UE->>Network: LocationMeasurementIndication + Note right of Network: +``` + +The diagram illustrates a sequence of messages between a User Equipment (UE) and a Network. The UE sends a message labeled *LocationMeasurementIndication* to the Network. The message is represented by a horizontal line with an arrow pointing from the UE to the Network. Vertical lines extend from the UE and Network boxes down to the start and end of the message line, respectively. + +Sequence diagram showing the Location measurement indication procedure between a UE and a Network. + +Figure 5.5.6.1-1: Location measurement indication + +The purpose of this procedure is to indicate to the network that the UE is going to start/stop location related measurements towards E-UTRA or NR which require measurement gaps or start/stop detection of subframe and slot timing towards E-UTRA (*eutra-FineTimingDetection*) which requires measurement gaps. UE shall initiate this procedure only after successful AS security activation. + +NOTE: It is a network decision to configure the measurement gap. + +#### 5.5.6.2 Initiation + +The UE shall: + +- 1> if and only if upper layers indicate to start performing location measurements towards E-UTRA or NR or start subframe and slot timing detection towards E-UTRA, and the UE requires measurement gaps for these operations while measurement gaps are either not configured or not sufficient: + - 2> if preconfigured measurement gaps for positioning and *posMG-Request* are configured and the UE considers that at least one of the preconfigured measurement gaps for positioning is sufficient for the location measurement when activated: + - 3> trigger the lower layers to initiate the measurement gap activation request using UL MAC CE as specified in TS 38.321 [3]; + - 2> else: + - 3> initiate the procedure to indicate start as specified in clause 5.5.6.3; + +NOTE 1: The UE verifies the measurement gap situation only upon receiving the indication from upper layers. If at this point in time sufficient gaps are available, the UE does not initiate the procedure. Unless it receives a new indication from upper layers, the UE is only allowed to further repeat the procedure in the same PCell once per frequency of the target RAT if the provided measurement gaps are insufficient. + +NOTE 1a: When indication is received from upper layers for performing location measurement and there is pre-configured measurement gap configured (not preconfigured measurement gap for positioning), the UE considers this preconfigured measurement gap to be not sufficient if the measurement gap is not considered to be always activated according to clause 9.1.7.2 of TS 38.133 [14]. + +- 1> if and only if upper layers indicate to stop performing location measurements towards E-UTRA or NR or stop subframe and slot timing detection towards E-UTRA: + - 2> if there is no activated preconfigured measurement gap for positioning: + - 3> if there is previously triggered UL MAC CE transmission for the measurement gap activation for positioning: + - 4> indicate to the lower layers to cancel the triggered UL MAC CE transmission for the measurement gap activation as specified in TS 38.321 [3]; + - 2> else if there is activated preconfigured measurement gap for positioning: + - 3> trigger the lower layers to deactivate all the activated measurement gap(s) for positioning as specified in TS 38.321 [3]. + - 2> if there is configured measurement gap used for positioning and the measurement gap is not the activated preconfigured measurement gap for positioning: + - 3> initiate the procedure to indicate stop as specified in 5.5.6.3. + +NOTE 2: The UE may initiate the procedure to indicate stop even if it did not previously initiate the procedure to indicate start. + +#### 5.5.6.3 Actions related to transmission of *LocationMeasurementIndication* message + +The UE shall set the contents of *LocationMeasurementIndication* message as follows: + +- 1> if the procedure is initiated to indicate start of location related measurements: + - 2> if the procedure is initiated for RSTD measurements towards E-UTRA: + - 3> set the *measurementIndication* to the *eutra-RSTD* according to the information received from upper layers; + - 2> else if the procedure is initiated for positioning measurement towards NR: + - 3> set the *measurementIndication* to the *nr-PRS-Measurement* according to the information received from upper layers; +- 1> else if the procedure is initiated to indicate stop of location related measurements: + - 2> set the *measurementIndication* to the value *release*; +- 1> if the procedure is initiated to indicate start of subframe and slot timing detection towards E-UTRA: + - 2> set the *measurementIndication* to the value *eutra-FineTimingDetection*; +- 1> else if the procedure is initiated to indicate stop of subframe and slot timing detection towards E-UTRA: + - 2> set the *measurementIndication* to the value *release*; +- 1> submit the *LocationMeasurementIndication* message to lower layers for transmission, upon which the procedure ends. + +## 5.5a Logged Measurements + +### 5.5a.1 Logged Measurement Configuration + +#### 5.5a.1.1 General + +![Sequence diagram showing the LoggedMeasurementConfiguration message flow from Network to UE.](909e1cd5419742a8ea8a95a16a40d849_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Network + Note right of Network: LoggedMeasurementConfiguration + Network->>UE: LoggedMeasurementConfiguration + +``` + +The diagram illustrates a sequence of interactions between a User Equipment (UE) and a Network. The UE is represented by a box on the left, and the Network by a box on the right. A vertical line (lifeline) extends downwards from each box. A horizontal arrow points from the Network's lifeline to the UE's lifeline, labeled with the message name *LoggedMeasurementConfiguration*. + +Sequence diagram showing the LoggedMeasurementConfiguration message flow from Network to UE. + +**Figure 5.5a.1.1-1: Logged measurement configuration** + +The purpose of this procedure is to configure the UE to perform logging of measurement results while in RRC\_IDLE and RRC\_INACTIVE. The procedure applies to logged measurements capable UEs that are in RRC\_CONNECTED. + +NOTE: NG-RAN may retrieve stored logged measurement information by means of the UE information procedure. + +#### 5.5a.1.2 Initiation + +NG-RAN initiates the logged measurement configuration procedure to UE in RRC\_CONNECTED by sending the *LoggedMeasurementConfiguration* message. + +#### 5.5a.1.3 Reception of the *LoggedMeasurementConfiguration* by the UE + +Upon receiving the *LoggedMeasurementConfiguration* message the UE shall: + +- 1> discard the logged measurement configuration as well as the logged measurement information as specified in 5.5a.2; +- 1> store the received *loggingDuration*, *reportType* and *areaConfiguration*, if included, in *VarLogMeasConfig*; +- 1> If the UE is registered in SNPN: + - 2> if the *LoggedMeasurementConfiguration* message includes *snpn-ConfigList*: + - 3> set the *snpn-ConfigIDList* in *VarLogMeasReport* to include the current registered SNPN ID as well as SNPN IDs in *snpn-ConfigList*; + - 2> else: + - 3> set the *snpn-ConfigIDList* in *VarLogMeasReport* to include the current registered SNPN ID; +- 1> else if the *LoggedMeasurementConfiguration* message includes *plmn-IdentityList*: + +2> set *plmn-IdentityList* in *VarLogMeasReport* to include the RPLMN as well as the PLMNs included in *plmn-IdentityList*; + +1> else: + +2> set *plmn-IdentityList* in *VarLogMeasReport* to include the RPLMN; + +1> store the received *absoluteTimeInfo*, *traceReference*, *traceRecordingSessionRef*, and *tce-Id* in *VarLogMeasReport*; + +1> store the received *bt-NameList*, if included, in *VarLogMeasConfig*; + +1> store the received *wlan-NameList*, if included, in *VarLogMeasConfig*; + +1> store the received *sensor-NameList*, if included, in *VarLogMeasConfig*; + +1> start timer T330 with the timer value set to the *loggingDuration*; + +1> store the received *sigLoggedMeasType*, if included, in *VarLogMeasReport*; + +1> store the received *earlyMeasIndication*, if included, in *VarLogMeasConfig*; + +#### 5.5a.1.4 T330 expiry + +Upon expiry of T330 the UE shall: + +1> release *VarLogMeasConfig*; + +The UE is allowed to discard stored logged measurements, i.e. to release *VarLogMeasReport*, 48 hours after T330 expiry. + +#### 5.5a.2 Release of Logged Measurement Configuration + +##### 5.5a.2.1 General + +The purpose of this procedure is to release the logged measurement configuration as well as the logged measurement information. + +##### 5.5a.2.2 Initiation + +The UE shall initiate the procedure upon receiving a logged measurement configuration in same or another RAT. The UE shall also initiate the procedure upon power off or upon deregistration. + +The UE shall: + +1> stop timer T330, if running; + +1> if stored, discard the logged measurement configuration as well as the logged measurement information, i.e. release the UE variables *VarLogMeasConfig* and *VarLogMeasReport*. + +#### 5.5a.3 Measurements logging + +#### 5.5a.3.1 General + +This procedure specifies the logging of available measurements by a UE in RRC\_IDLE and RRC\_INACTIVE that has a logged measurement configuration. The actual process of logging within the UE, takes place in RRC\_IDLE state could continue in RRC\_INACTIVE state or vice versa. + +##### 5.5a.3.2 Initiation + +While T330 is running and SDT procedure is not ongoing, the UE shall: + +- 1> if measurement logging is suspended: + - 2> if during the last logging interval the IDC problems detected by the UE is resolved, resume measurement logging; +- 1> if not suspended, perform the logging in accordance with the following: + - 2> if the *reportType* is set to *periodical* in the *VarLogMeasConfig*: + - 3> if the UE is in any cell selection state (as specified in TS 38.304 [20]): + - 4> perform the logging at regular time intervals, as defined by the *loggingInterval* in the *VarLogMeasConfig*; + - 3> if the UE is in camped normally state on an NR cell and if the RPLMN is included in *plmn-IdentityList* stored in *VarLogMeasReport*; or + - 3> if the UE is in camped normally state on an NR cell and if the registered SNPN is included in *snpn-ConfigIDList* stored in *VarLogMeasReport*: + - 4> if *areaConfiguration* is not included in *VarLogMeasConfig*; or + - 4> if the serving cell is part of the area indicated by *areaConfig* in *areaConfiguration* in *VarLogMeasConfig*; or + - 4> if the serving cell is part of the area indicated by *cag-ConfigList* in *areaConfiguration* in *VarLogMeasConfig*; or + - 4> if the serving cell is part of the area indicated by *snpn-ConfigList* in *areaConfiguration* in *VarLogMeasConfig*: + - 5> perform the logging at regular time intervals, as defined by the *loggingInterval* in the *VarLogMeasConfig*; + - 2> else if the *reportType* is set to *eventTriggered*, and *eventType* is set to *outOfCoverage*: + - 3> perform the logging at regular time intervals as defined by the *loggingInterval* in *VarLogMeasConfig* only when the UE is in any cell selection state; + +- 3> upon transition from any cell selection state to camped normally state in NR: + - 4> if the RPLMN is included in *plmn-IdentityList* stored in *VarLogMeasReport*, or if the registered SNPN is included in *snpn-ConfigIDList* stored in *VarLogMeasReport*; and + - 4> if *areaConfiguration* is not included in *VarLogMeasConfig* or if the current camping cell is part of the area indicated by *areaConfig* of *areaConfiguration* in *VarLogMeasConfig*, or if the current camping cell is part of the area indicated by *cag-ConfigList* of *areaConfiguration* in *VarLogMeasConfig*, or if the current camping cell is part of the area indicated by *snpn-ConfigList* of *areaConfiguration* in *VarLogMeasConfig*: + - 5> perform the logging; +- 2> else if the *reportType* is set to *eventTriggered* and *eventType* is set to *eventL1*: + - 3> if the UE is in camped normally state on an NR cell and if the RPLMN is included in *plmn-IdentityList* stored in *VarLogMeasReport*; or + - 3> if the UE is in camped normally state on an NR cell and if the registered SNPN is included in *snpn-ConfigIDList* stored in *VarLogMeasReport*: + - 4> if *areaConfiguration* is not included in *VarLogMeasConfig*; or + - 4> if the serving cell is part of the area indicated by *areaConfig* in *areaConfiguration* in *VarLogMeasConfig*; or + - 4> if the current serving cell is part of the area indicated by *cag-ConfigList* of *areaConfiguration* in *VarLogMeasConfig*, or if the current camping cell is part of the area indicated by *snpn-ConfigList* of *areaConfiguration* in *VarLogMeasConfig*: + - 5> perform the logging at regular time intervals as defined by the *loggingInterval* in *VarLogMeasConfig* only when the conditions indicated by the *eventL1* are met; +- 2> when performing the logging: + - 3> if *InterFreqTargetInfo* is configured and if the UE detected IDC problems on at least one of the frequencies included in *InterFreqTargetInfo* or any inter-RAT frequency during the last logging interval, or + - 3> if *InterFreqTargetInfo* is not configured and if the UE detected IDC problems during the last logging interval: + - 4> if *measResultServingCell* in the *VarLogMeasReport* is not empty: + - 5> include *inDeviceCoexDetected*; + - 5> suspend measurement logging from the next logging interval; + - 4> else: + - 5> suspend measurement logging; + +- 3> set the *relativeTimeStamp* to indicate the elapsed time since the moment at which the logged measurement configuration was received; +- 3> if location information became available during the last logging interval, set the content of the *locationInfo* as in 5.3.3.7: +- 3> if the UE is in any cell selection state (as specified in TS 38.304 [20]): + - 4> set *anyCellSelectionDetected* to indicate the detection of no suitable or no acceptable cell found; + - 4> if the *reportType* is set to *eventTriggered* in the *VarLogMeasConfig*; and + - 4> if the RPLMN at the time of entering the any cell selection state is included in *plmn-IdentityList* stored in *VarLogMeasReport*; and + - 4> if *areaConfiguration* is not included in *VarLogMeasConfig* or if the last suitable cell that the UE was camping on is part of the area indicated by *areaConfig* of *areaConfiguration* in *VarLogMeasConfig*, or if last suitable cell that the UE was camping on is part of the area indicated by *cag-ConfigList* of *areaConfiguration* in *VarLogMeasConfig*, or if last suitable cell that the UE was camping on is part of the area indicated by *snpn-ConfigList* of *areaConfiguration* in *VarLogMeasConfig*: + - 5> set the *servCellIdentity* to indicate global cell identity of the last suitable cell that the UE was camping on; + - 5> set the *measResultServingCell* to include the quantities of the last suitable cell the UE was camping on; + - 4> else if the *reportType* is set to *periodical* in the *VarLogMeasConfig*: + - 5> set the *servCellIdentity* to indicate global cell identity of the last logged cell that the UE was camping on; + - 5> set the *measResultServingCell* to include the quantities of the last logged cell the UE was camping on; +- 3> else: + - 4> set the *servCellIdentity* to indicate global cell identity of the cell the UE is camping on; + +Editor's note: Including list of equivalent SNPN IDs in MDT report is FFS. + +- 4> set the *measResultServingCell* to include the quantities of the cell the UE is camping on; +- 3> if available, set the *measResultNeighCells*, in order of decreasing ranking-criterion as used for cell re-selection, to include measurements of neighbouring cell that became available during the last logging interval and according to the following: + - 4> include measurement results for at most 6 neighbouring cells on the NR serving frequency and for at most 3 cells per NR neighbouring frequency and for the NR neighbouring frequencies in accordance with the following: + - 5> if *interFreqTargetInfo* is included in *VarLogMeasConfig*: + - 6> if *earlyMeasIndication* is included in *VarLogMeasConfig*; + +- 7> include measurement results for NR neighbouring frequencies that are included in both *interFreqTargetInfo* and either in *measIdleCarrierListNR* (within the *VarMeasIdleConfig*) or *SIB4*; + - 6> else: + - 7> include measurement results for NR neighbouring frequencies that are included in both *interFreqTargetInfo* and *SIB4*; + - 5> else: + - 6> if *earlyMeasIndication* is included in *VarLogMeasConfig*: + - 7> include measurement results for NR neighbouring frequencies that are included in either *measIdleCarrierListNR* (within the *VarMeasIdleConfig*) or *SIB4*; + - 6> else: + - 7> include measurement results for NR neighbouring frequencies that are included in *SIB4*; + - 4> include measurement results for at most 3 neighbours per inter-RAT frequency in accordance with the following: + - 5> if *earlyMeasIndication* is included in *VarLogMeasConfig*: + - 6> include measurement results for inter-RAT neighbouring frequencies that are included in either *measIdleCarrierListEUTRA* (within the *VarMeasIdleConfig*) or *SIB5*; + - 5> else: + - 6> include measurement results for inter-RAT frequencies that are included in *SIB5*; + - 4> for each neighbour cell included, include the optional fields that are available; +- NOTE 1: The UE includes the latest results of the available measurements as used for cell reselection evaluation in RRC\_IDLE or RRC\_INACTIVE, which are performed in accordance with the performance requirements as specified in TS 38.133 [14]. +- NOTE 2: For logging the measurements on frequencies (indicated in *measIdleCarrierListNR*/ *measIdleCarrierListEUTRA*) in the logged measurement, the *qualityThreshold* in *measIdleConfig* should not be applied, and how the UE logs the measurements on the frequencies is left to the UE implementation. +- 2> when the memory reserved for the logged measurement information becomes full, stop timer T330 and perform the same actions as performed upon expiry of T330, as specified in 5.5a.1.4. + +## 5.5b Application Layer Measurements in RRC\_IDLE/RRC\_INACTIVE + +### 5.5b.1 Area handling and storing of Application Layer Measurement reports in RRC\_IDLE/RRC\_INACTIVE + +#### 5.5b.1.1 General + +This procedure specifies the area handling and storing of application layer measurement report containers by a UE in RRC\_IDLE and RRC\_INACTIVE that has a configuration for application layer measurements in RRC\_IDLE and/or RRC\_INACTIVE. + +#### 5.5b.1.2 Initiation + +While in RRC\_INACTIVE and RRC\_IDLE state, the UE shall: + +- 1> store any previously or subsequently received application layer measurement report containers associated with the *measConfigAppLayerId* for which no segment, or full message, has been submitted to lower layers for transmission; +- 1> if the memory reserved for storing application layer measurement report containers becomes full: + - 2> if the UE is configured with *appLayerMeasPriority*: + - 3> discard reports in priority order where reports with the lowest priority are discarded first; + - 2> else if no *appLayerMeasPriority* is configured: + - 3> discard reports in the order they were received, where older reports may be discarded first; +- 1> if the current cell when the UE transits from RRC\_CONNECTED state to RRC\_INACTIVE or RRC\_IDLE state is part of the area indicated by *qoe-AreaScope*: + - 2> inform upper layers of being inside the area; +- 1> if the current cell when the UE transits from RRC\_CONNECTED state to RRC\_INACTIVE or RRC\_IDLE state is not part of the area indicated by *qoe-AreaScope*: + - 2> inform upper layers of being outside the area. +- 1> if a new current cell is part of the area indicated by *qoe-AreaScope* and the previous cell was not part of the area indicated by *qoe-AreaScope*: + - 2> inform upper layers of being inside the area; +- 1> if a new current cell is not part of the area indicated by *qoe-AreaScope* and the previous cell was part of the area indicated by *qoe-AreaScope*: + - 2> inform upper layers of being outside the area. + +## 5.6 UE capabilities + +### 5.6.1 UE capability transfer + +#### 5.6.1.1 General + +This clause describes how the UE compiles and transfers its UE capability information upon receiving a *UECapabilityEnquiry* from the network. + +![Sequence diagram of UE capability transfer](aa0ca8b71d46db8787e0e4b249325750_img.jpg) + +A sequence diagram illustrating the UE capability transfer procedure. It features two vertical lifelines: 'UE' on the left and 'Network' on the right. The interaction begins with a horizontal arrow labeled *UECapabilityEnquiry* pointing from the Network to the UE. Following this, a horizontal arrow labeled *UECapabilityInformation* points from the UE back to the Network. + +Sequence diagram of UE capability transfer + +Figure 5.6.1.1-1: UE capability transfer + +#### 5.6.1.2 Initiation + +The network initiates the procedure to a UE in RRC\_CONNECTED when it needs (additional) UE radio access capability information. The network should retrieve UE capabilities only after AS security activation. Network does not forward UE capabilities that were retrieved before AS security activation to the CN. + +#### 5.6.1.3 Reception of the *UECapabilityEnquiry* by the UE + +The UE shall set the contents of *UECapabilityInformation* message as follows: + +- 1> if the *ue-CapabilityRAT-RequestList* contains a *UE-CapabilityRAT-Request* with *rat-Type* set to *nr*: + - 2> include in the *ue-CapabilityRAT-ContainerList* a *UE-CapabilityRAT-Container* of the type *UE-NR-Capability* and with the *rat-Type* set to *nr*; + - 2> include the *supportedBandCombinationList*, *featureSets* and *featureSetCombinations* as specified in clause 5.6.1.4; +- 1> if the *ue-CapabilityRAT-RequestList* contains a *UE-CapabilityRAT-Request* with *rat-Type* set to *eutra-nr*: + - 2> if the UE supports (NG)EN-DC or NE-DC: + - 3> include in the *ue-CapabilityRAT-ContainerList* a *UE-CapabilityRAT-Container* of the type *UE-MRDC-Capability* and with the *rat-Type* set to *eutra-nr*; + - 3> include the *supportedBandCombinationList* and *featureSetCombinations* as specified in clause 5.6.1.4; + +- 1) if the *ue-CapabilityRAT-RequestList* contains a *UE-CapabilityRAT-Request* with *rat-Type* set to *eutra*: + - 2) if the UE supports E-UTRA: + - 3) include in the *ue-CapabilityRAT-ContainerList* a *ue-CapabilityRAT-Container* of the type *UE-EUTRA-Capability* associated with the terrestrial network and with the *rat-Type* set to *eutra* as specified in TS 36.331 [10], clause 5.6.3.3, according to the *capabilityRequestFilter*, if received; +- 1) if the *ue-CapabilityRAT-RequestList* contains a *UE-CapabilityRAT-Request* with *rat-Type* set to *utra-fdd*: + - 2) if the UE supports UTRA-FDD: + - 3) include the UE radio access capabilities for UTRA-FDD within a *ue-CapabilityRAT-Container* and with the *rat-Type* set to *utra-fdd*; +- 1) if the RRC message segmentation is enabled based on the field *rrc-SegAllowed* received, and the encoded RRC message is larger than the maximum supported size of a PDCP SDU specified in TS 38.323 [5]: + - 2) initiate the UL message segment transfer procedure as specified in clause 5.7.7; +- 1) else: + - 2) submit the *UECapabilityInformation* message to lower layers for transmission, upon which the procedure ends. + +#### 5.6.1.4 Setting band combinations, feature set combinations and feature sets supported by the UE + +The UE invokes the procedures in this clause if the NR or E-UTRA network requests UE capabilities for *nr*, *eutra-nr* or *eutra*. This procedure is invoked once per requested *rat-Type* (see clause 5.6.1.3 for capability enquiry by the NR network; see TS 36.331 [10], clause 5.6.3.3 for capability enquiry by the E-UTRA network). The UE shall ensure that the feature set IDs are consistent across feature sets, feature set combinations and band combinations in all three UE capability containers that the network queries with the same fields with the same values, i.e. *UE-CapabilityRequestFilterNR*, *UE-CapabilityRequestFilterCommon* and fields in *UECapabilityEnquiry* message (i.e. *requestedFreqBandsNR-MRDC*, *requestedCapabilityNR*, *eutra-nr-only* flag, and *requestedCapabilityCommon*) as defined in TS 36.331, where applicable. + +NOTE 1: Capability enquiry without *frequencyBandListFilter* is not supported. + +NOTE 2: In (NG)EN-DC, the gNB needs the capabilities for RAT types *nr* and *eutra-nr* and it uses the *featureSets* in the *UE-NR-Capability* together with the *featureSetCombinations* in the *UE-MRDC-Capability* to determine the NR UE capabilities for the supported MRDC band combinations. Similarly, the eNB needs the capabilities for RAT types *eutra* and *eutra-nr* and it uses the *featureSetsEUTRA* in the *UE-EUTRA-Capability* together with the *featureSetCombinations* in the *UE-MRDC-Capability* to determine the E-UTRA UE capabilities for the supported MRDC band combinations. Hence, the IDs used in the *featureSets* must match the IDs referred to in *featureSetCombinations* across all three containers. The requirement on consistency implies that there are no undefined feature sets and feature set combinations. + +NOTE 3: If the UE cannot include all feature sets and feature set combinations due to message size or list size constraints, it is up to UE implementation which feature sets and feature set combinations it prioritizes. + +The UE shall: + +1> if the UE is an eRedCap UE, the UE may in the remainder of this procedure assume *frequencyBandListFilter* to be the filter containing all the supported bands of the UE; + +1> compile a list of "candidate band combinations" according to the filter criteria in *capabilityRequestFilterCommon* (if included), only consisting of bands included in *frequencyBandListFilter*, and prioritized in the order of *frequencyBandListFilter* (i.e. first include band combinations containing the first-listed band, then include remaining band combinations containing the second-listed band, and so on), where for each band in the band combination, the parameters of the band do not exceed *maxBandwidthRequestedDL*, *maxBandwidthRequestedUL*, *maxCarriersRequestedDL*, *maxCarriersRequestedUL*, *ca-BandwidthClassDL-EUTRA* or *ca-BandwidthClassUL-EUTRA*, whichever are received; + +1> for each band combination included in the list of "candidate band combinations": + +2> if the network (E-UTRA) included the *eutra-nr-only* field, or + +2> if the requested *rat-Type* is *eutra*: + +3> remove the NR-only band combination from the list of "candidate band combinations"; + +NOTE 4: The (E-UTRA) network may request capabilities for *nr* but indicate with the *eutra-nr-only* flag that the UE shall not include any NR band combinations in the *UE-NR-Capability*. In this case the procedural text above removes all NR-only band combinations from the candidate list and thereby also avoids inclusion of corresponding feature set combinations and feature sets below. + +2> if it is regarded as a fallback band combination with the same capabilities of another band combination included in the list of "candidate band combinations", and + +2> if this fallback band combination is generated by releasing at least one SCell or uplink configuration of SCell or SUL according to TS 38.306 [26]: + +3> remove the band combination from the list of "candidate band combinations"; + +NOTE 5: Even if the network requests (only) capabilities for *nr*, it may include E-UTRA band numbers in the *frequencyBandListFilter* to ensure that the UE includes all necessary feature sets needed for subsequently requested *eutra-nr* capabilities. At this point of the procedure the list of "candidate band combinations" contains all NR- and/or E-UTRA-NR band combinations that match the filter (*frequencyBandListFilter*) provided by the NW and that match the *eutra-nr-only* flag (if RAT-Type *nr* is requested by E-UTRA). In the following, this candidate list is used to derive the band combinations, feature set combinations and feature sets to be reported in the requested capability container. + +1> if the requested *rat-Type* is *nr*: + +2> include into *supportedBandCombinationList* as many NR-only band combinations as possible from the list of "candidate band combinations", starting from the first entry; + +3> if *srs-SwitchingTimeRequest* is received: + +4> if SRS carrier switching is supported; + +5> include *srs-SwitchingTimesListNR* and *srs-SwitchingAffectedBandsListNR* for each band combination; + +4> set *srs-SwitchingTimeRequested* to *true*; + +2> include, into *featureSetCombinations*, the feature set combinations referenced from the supported band combinations as included in *supportedBandCombinationList* according to the previous; + +2> compile a list of "candidate feature set combinations" referenced from the list of "candidate band combinations" excluding entries (rows in feature set combinations) with same or lower capabilities; + +2> if *uplinkTxSwitchRequest* is received: + +3> include into *supportedBandCombinationList-UplinkTxSwitch* as many NR-only band combinations that supported UL TX switching as possible from the list of "candidate band combinations", starting from the first entry; + +4> if *srs-SwitchingTimeRequest* is received: + +5> if SRS carrier switching is supported; + +6> include *srs-SwitchingTimesListNR* and *srs-SwitchingAffectedBandsListNR* for each band combination; + +5> set *srs-SwitchingTimeRequested* to *true*; + +3> include, into *featureSetCombinations*, the feature set combinations referenced from the supported band combinations as included in *supportedBandCombinationList-UplinkTxSwitch* according to the previous; + +NOTE 6: This list of "candidate feature set combinations" contains the feature set combinations used for NR-only as well as E-UTRA-NR band combinations. It is used to derive a list of NR feature sets referred to from the feature set combinations in the *UE-NR-Capability* and from the feature set combinations in a *UE-MRDC-Capability* container. + +2> if *sidelinkRequest* is received: + +3> for a sidelink band combination the UE included in *supportedBandCombinationListSidelinkEUTRA-NR*, *supportedBandCombinationListSL-RelayDiscovery*, *supportedBandCombinationListSL-U2U-RelayDiscovery* or *supportedBandCombinationListSL-NonRelayDiscovery*: + +4> if the UE supports partial sensing for a band of the sidelink band combination, include the partial sensing capabilities for the band using the *sl-TransmissionMode2-PartialSensing-r17*; + +3> set *sidelinkRequested* to *true*; + +2> include into *featureSets* the feature sets referenced from the "candidate feature set combinations" and may exclude the feature sets with the parameters that exceed any of *maxBandwidthRequestedDL*, *maxBandwidthRequestedUL*, *maxCarriersRequestedDL* or *maxCarriersRequestedUL*, whichever are received; + +1> else, if the requested *rat-Type* is *eutra-nr*: + +- 2> include into *supportedBandCombinationList* and/or *supportedBandCombinationListNEDC-Only* as many E-UTRA-NR band combinations as possible from the list of "candidate band combinations", starting from the first entry; + - 3> if *srs-SwitchingTimeRequest* is received: + - 4> if SRS carrier switching is supported; + - 5> include *srs-SwitchingTimesListNR*, *srs-SwitchingTimesListEUTRA* and *srs-SwitchingAffectedBandsListNR* for each band combination; + - 4> set *srs-SwitchingTimeRequested* to *true*; + - 2> include, into *featureSetCombinations*, the feature set combinations referenced from the supported band combinations as included in *supportedBandCombinationList* according to the previous; + - 2> if *uplinkTxSwitchRequest* is received: + - 3> include into *supportedBandCombinationList-UplinkTxSwitch* as many E-UTRA-NR band combinations that supported UL TX switching as possible from the list of "candidate band combinations", starting from the first entry; + - 4> if *srs-SwitchingTimeRequest* is received: + - 5> if SRS carrier switching is supported; + - 6> include *srs-SwitchingTimesListNR*, *srs-SwitchingTimesListEUTRA* and *srs-SwitchingAffectedBandsListNR* for each band combination; + - 5> set *srs-SwitchingTimeRequested* to *true*; + - 3> include, into *featureSetCombinations*, the feature set combinations referenced from the supported band combinations as included in *supportedBandCombinationList-UplinkTxSwitch* according to the previous; + - 1> else (if the requested *rat-Type* is *eutra*): + - 2> compile a list of "candidate feature set combinations" referenced from the list of "candidate band combinations" excluding entries (rows in feature set combinations) with same or lower capabilities; + +NOTE 7: This list of "candidate feature set combinations" contains the feature set combinations used for E-UTRA-NR band combinations. It is used to derive a list of E-UTRA feature sets referred to from the feature set combinations in a *UE-MRDC-Capability* container. + +- 2> include into *featureSetsEUTRA* (in the *UE-EUTRA-Capability*) the feature sets referenced from the "candidate feature set combinations" and may exclude the feature sets with the parameters that exceed *ca-BandwidthClassDL-EUTRA* or *ca-BandwidthClassUL-EUTRA*, whichever are received; + +- 1> if the UE is an eRedCap UE and the UE assumes *frequencyBandListFilter* to be the filter containing all the supported bands of the UE: + - 2> include all the supported bands of the UE in the field *appliedFreqBandListFilter*; + +1> else: + +2> include the received *frequencyBandListFilter* in the field *appliedFreqBandListFilter* of the requested UE capability, except if the requested *rat-Type* is *nr* and the network included the *eutra-nr-only* field; + +1> if the network included *ue-CapabilityEnquiryExt*: + +2> include the received *ue-CapabilityEnquiryExt* in the field *receivedFilters*; + +5.6.1.5 Void + +## 5.7 Other + +### 5.7.1 DL information transfer + +#### 5.7.1.1 General + +![Sequence diagram showing DL information transfer from Network to UE.](1d44bdd1863e06a905f90ab64d0daaa7_img.jpg) + +A sequence diagram illustrating the DL information transfer procedure. It features two vertical lifelines: 'UE' on the left and 'Network' on the right. A horizontal arrow points from the Network lifeline to the UE lifeline, labeled with the message name *DLInformationTransfer*. + +Sequence diagram showing DL information transfer from Network to UE. + +Figure 5.7.1.1-1: DL information transfer + +The purpose of this procedure is to transfer NAS dedicated information from NG-RAN to a UE in RRC\_CONNECTED or to a UE in RRC\_INACTIVE during SDT, or to transfer F1-C related information from IAB Donor-CU to IAB-DU via the collocated IAB-MT in RRC\_CONNECTED. + +#### 5.7.1.2 Initiation + +The network initiates the DL information transfer procedure whenever there is a need to transfer NAS dedicated information, or F1-C related information to an IAB-node. The network initiates the DL information transfer procedure by sending the *DLInformationTransfer* message. + +#### 5.7.1.3 Reception of the *DLInformationTransfer* by the UE + +Upon receiving *DLInformationTransfer* message, the UE shall: + +1> if *dedicatedNAS-Message* is included: + +- 2> forward *dedicatedNAS-Message* to upper layers. +- 1> if *referenceTimeInfo* is included: + - 2> calculate the reference time based on the *time*, *referenceSFN* and *timeInfoType* if it is included; + - 2> calculate the uncertainty of the reference time based on the *uncertainty*, if *uncertainty* is included; + - 2> inform upper layers of the reference time and, if *uncertainty* is included, of the uncertainty; + - 2> ignore all further *referenceTimeInfo* received in *SIB9*, if any. +- 1> if *sib9Fallback* is included: + - 2> apply *referenceTimeInfo* in *SIB9*. +- 1> if *rxTxTimeDiff-gNB* is included: + - 2> calculate the propagation delay based on the UE Rx-Tx time difference measurement and the received Rx-Tx time difference measurement at the gNB; + - 2> inform upper layers of the propagation delay. +- 1> if *ta-PDC* is set to *activate*: + - 2> inform upper layers of the propagation delay determined by the accumulated Timing Advance commands. +- 1> if *clockQualityDetailsLevel* is included: + - 2> if *eventID-TSS* is included: + - 3> if *VarEventID* has an entry with a *storedEventID* value: + - 4> replace the *storedEventID* value within *VarEventID* with the *eventID-TSS* value received with *clockQualityDetailsLevel*; + - 3> else: + - 4> add a new entry of *storedEventID* within the *VarEventID* with a value set as the one of *eventID-TSS* value received with *clockQualityDetailsLevel*; + - 2> if the *VarGnbID* has an entry with a *storedGnbID* value: + - 3> replace the *storedGnbID* value within *VarGnbID* with the gNB identity value received within *SIB1*; + - 2> else: + - 3> add a new entry of *storedGnbID* within the *VarGnbID* with the gNB identity value received within *SIB1*. + +2> forward *clockQualityDetailsLevel* to upper layers. + +Upon receiving *DLInformationTransfer* message, the IAB-MT shall: + +1> if *dedicatedInfoFlc* is included: + +2> forward *dedicatedInfoFlc* to the collocated IAB-DU. + +### 5.7.1a DL information transfer for MR-DC + +#### 5.7.1a.1 General + +![Sequence diagram showing DL information transfer MR-DC from Network to UE.](d1ad67cff357f77c9114c037e193f585_img.jpg) + +A sequence diagram illustrating the DL information transfer MR-DC procedure. It features two vertical lifelines: 'UE' on the left and 'Network' on the right. A horizontal arrow points from the Network lifeline to the UE lifeline, labeled with the message name *DLInformationTransferMRDC*. + +Sequence diagram showing DL information transfer MR-DC from Network to UE. + +Figure 5.7.1a.1-1: DL information transfer MR-DC + +The purpose of this procedure is to transfer RRC messages from the network to the UE over SRB3 (e.g. an NR RRC reconfiguration message including *reconfigurationWithSync*, an E-UTRA RRC connection reconfiguration message including *mobilityControlInfo*, an RRC connection release message, a *MobilityFromNRCommand* message, or a *MobilityFromEUTRACommand* message) during fast MCG link recovery. + +#### 5.7.1a.2 Initiation + +The network initiates this procedure whenever there is a need to transfer an RRC message during fast MCG link recovery. + +#### 5.7.1a.3 Actions related to reception of *DLInformationTransferMRDC* message + +Upon receiving the *DLInformationTransferMRDC*, the UE shall: + +1> if the *RRCRreconfiguration* message is included in *dl-DCCH-MessageNR*: + +2> perform the RRC reconfiguration procedure according to 5.3.5.3; + +1> else if the *RRCRrelease* message is included in *dl-DCCH-MessageNR*: + +2> perform the RRC release procedure according to 5.3.8; + +- 1> else if the *MobilityFromNRCommand* message is included in the *dl-DCCH-MessageNR*: + - 2> perform the mobility from NR procedure according to 5.4.3.3; +- 1> else if the E-UTRA *RRConnectionReconfiguration* message is included in *dl-DCCH-MessageEUTRA*: + - 2> perform the RRC connection reconfiguration procedure as specified in TS 36.331 [10], clause 5.3.5.4; +- 1> else if the E-UTRA *RRConnectionRelease* message is included in *dl-DCCH-MessageEUTRA*: + - 2> perform the RRC connection release as specified in TS 36.331 [10], clause 5.3.8; +- 1> else if the *MobilityFromEUTRACommand* message is included in the *dl-DCCH-MessageEUTRA*: + - 2> perform the mobility from E-UTRA procedure as specified in TS 36.331 [10], clause 5.4.3.3; + +### 5.7.2 UL information transfer + +#### 5.7.2.1 General + +![Sequence diagram showing UL information transfer from UE to Network.](be385895e822fc377a2163dc96fd7eee_img.jpg) + +A sequence diagram illustrating the UL information transfer procedure. It features two vertical lifelines: 'UE' on the left and 'Network' on the right. A horizontal arrow points from the UE lifeline to the Network lifeline, with the label *ULInformationTransfer* positioned above the arrow. + +Sequence diagram showing UL information transfer from UE to Network. + +Figure 5.7.2.1-1: UL information transfer + +The purpose of this procedure is to transfer NAS dedicated information from the UE to the network in RRC\_CONNECTED or in RRC\_INACTIVE during SDT, or to transfer F1-C related information from IAB-DU to IAB Donor-CU via the collocated IAB-MT in RRC\_CONNECTED. + +#### 5.7.2.2 Initiation + +A UE in RRC\_CONNECTED or a UE in RRC\_INACTIVE during SDT initiates the UL information transfer procedure whenever there is a need to transfer NAS dedicated information. The UE initiates the UL information transfer procedure by sending the *ULInformationTransfer* message. In addition, an IAB-MT in RRC\_CONNECTED initiates the UL information transfer procedure whenever there is a need to transfer F1-C related information. When F1-C related information has to be transferred, the IAB-MT shall initiate the procedure only if SRB2 or split SRB2 is established. + +#### 5.7.2.3 Actions related to transmission of *ULInformationTransfer* message + +The UE shall set the contents of the *ULInformationTransfer* message as follows: + +- 1> if the upper layer provides NAS PDU: + - 2> set the *dedicatedNAS-Message* to include the information received from upper layers; +- 1> for the IAB-MT, if there is a need to transfer F1-C related information: + - 2> include the *dedicatedInfoF1c*; +- 1> submit the *ULInformationTransfer* message to lower layers for transmission, upon which the procedure ends. + +#### 5.7.2.4 Failure to deliver *ULInformationTransfer* message + +The UE shall: + +- 1> if AS security is not started and radio link failure occurs before the successful delivery of *ULInformationTransfer* messages has been confirmed by lower layers; or +- 1> if PDCP re-establishment or release/addition (e.g due to key refresh upon PCell or PSCell change, or RRC connection re-establishment, or failure of resume procedure initiated for SDT) occurs on an SRB on which *ULInformationTransfer* messages were submitted for transmission but successful delivery of these messages was not confirmed by lower layers: + - 2> inform upper layers about the possible failure to deliver the information contained in the concerned *ULInformationTransfer* messages, unless the messages only include *dedicatedInfoF1c*. + +### 5.7.2a UL information transfer for MR-DC + +#### 5.7.2a.1 General + +![Sequence diagram showing UL information transfer for MR-DC between UE and Network.](29100fce6dce19cea57712363976bf2c_img.jpg) + +A sequence diagram illustrating the interaction between a User Equipment (UE) and a Network. The UE is represented by a box on the left, and the Network by a box on the right. A horizontal arrow points from the UE to the Network, labeled with the message name *ULInformationTransferMRDC*. Vertical lines extend downwards from both the UE and Network boxes, representing their respective lifelines. + +Sequence diagram showing UL information transfer for MR-DC between UE and Network. + +Figure 5.7.2a.1-1: UL information transfer MR-DC + +The purpose of this procedure is to transfer MR-DC dedicated information from the UE to the network e.g. the NR or E-UTRA RRC *MeasurementReport*, *FailureInformation*, *UEAssistanceInformation*, *RRRCReconfigurationComplete*, *MCGFailureInformation*, or *IABOtherInformation* message. + +#### 5.7.2a.2 Initiation + +A UE in RRC\_CONNECTED initiates the UL information transfer for MR-DC procedure whenever there is a need to transfer MR-DC dedicated information. I.e. the procedure is not used during an RRC connection reconfiguration involving NR or E-UTRA connection reconfiguration, in which case the MR DC information is piggybacked to the *RRRCReconfigurationComplete* message, except in the case the UE executes an intra-SN CPC. + +#### 5.7.2a.3 Actions related to transmission of *ULInformationTransferMRDC* message + +The UE shall set the contents of the *ULInformationTransferMRDC* message as follows: + +- 1> if there is a need to transfer MR-DC dedicated information related to NR: + - 2> set the *ul-DCCH-MessageNR* to include the NR MR-DC dedicated information to be transferred (e.g., NR RRC *MeasurementReport*, *UEAssistanceInformation*, *FailureInformation*, *RRRCReconfigurationComplete*, *MCGFailureInformation*, or *IABOtherInformation* message); +- 1> else if there is a need to transfer MR-DC dedicated information related to E-UTRA: + - 2> set the *ul-DCCH-MessageEUTRA* to include the E-UTRA MR-DC dedicated information to be transferred (e.g., E-UTRA RRC *MeasurementReport*, or *MCGFailureInformation* message); +- 1> submit the *ULInformationTransferMRDC* message to lower layers for transmission, upon which the procedure ends. + +#### 5.7.2b UL transfer of IRAT information + +#### 5.7.2b.1 General + +![Sequence diagram showing the UL transfer of IRAT information from UE to NR.](600d42b593738a8e023082e291628eaf_img.jpg) + +``` +sequenceDiagram + participant UE + participant NR + Note right of UE: ULInformationTransferIRAT + UE->>NR: ULInformationTransferIRAT +``` + +The diagram illustrates a sequence of events between a User Equipment (UE) and a Network Radio (NR). The UE is shown on the left and the NR on the right. A horizontal arrow points from the UE to the NR, labeled with the message name *ULInformationTransferIRAT*. Vertical lines extend from the boxes representing the UE and NR, indicating the timeline of the interaction. + +Sequence diagram showing the UL transfer of IRAT information from UE to NR. + +Figure 5.7.2b.1-1: UL transfer of IRAT information + +The purpose of this procedure is to transfer from the UE to NR MCG dedicated information terminated at the NR MCG but specified by another RAT e.g. the E-UTRA *MeasurementReport* message, the E-UTRA *SidelinkUEInformation* message or the E-UTRA *UEAssistanceInformation* message. The specific information transferred in this message is set in accordance with: + +- the procedure specified in 5.6.10 of TS 36.331 [10] for E-UTRA *UEAssistanceInformation* message; +- the procedure specified in 5.10.2 of TS 36.331 [10] for E-UTRA *SidelinkUEInformation* message; +- the procedure specified in 5.5.5 of TS 36.331 [10] for E-UTRA *MeasurementReport* Message. + +#### 5.7.2b.2 Initiation + +A UE in RRC\_CONNECTED initiates the UL information transfer procedure whenever there is a need to transfer dedicated inter-RAT information as specified in TS 36.331 [10]. + +#### 5.7.2b.3 Actions related to transmission of *ULInformationTransferIRAT* message + +The UE shall set the contents of the *ULInformationTransferIRAT* message as follows: + +- 1> if there is a need to transfer dedicated LTE information related to V2X sidelink communications: + - 2> set the *ul-DCCH-MessageEUTRA* to include the V2X sidelink communication information to be transferred (e.g. the E-UTRA RRC *MeasurementReport* message, the E-UTRA RRC *SidelinkUEInformation* message, or the E-UTRA RRC *UEAssistanceInformation* message); +- 1> submit the *ULInformationTransferIRAT* message to lower layers for transmission, upon which the procedure ends; + +### 5.7.3 SCG failure information + +#### 5.7.3.1 General + +![Sequence diagram showing SCG failure information exchange between UE and Network.](487046a4bbc8c18c86fed4cd5a698fcc_img.jpg) + +``` +sequenceDiagram + participant UE + participant Network + Note left of UE: SCG failure + UE->>Network: RRC reconfiguration + Note right of Network: SCG failure information + Network->>UE: SCGFailureInformation +``` + +The diagram illustrates a sequence of messages between a User Equipment (UE) and a Network. The UE sends an 'RRC reconfiguration' message to the Network. Upon receiving this, the Network identifies an 'SCG failure' and responds with an 'SCGFailureInformation' message back to the UE. + +Sequence diagram showing SCG failure information exchange between UE and Network. + +Figure 5.7.3.1-1: SCG failure information + +The purpose of this procedure is to inform E-UTRAN or NR MN about an SCG failure the UE has experienced i.e. SCG radio link failure, beam failure of the PSCell while the SCG is deactivated, failure of SCG reconfiguration with sync, SCG configuration failure for RRC message on SRB3, SCG integrity check failure, and consistent uplink LBT failures on PSCell for operation with shared spectrum channel access. + +#### 5.7.3.2 Initiation + +A UE initiates the procedure to report SCG failures when neither MCG nor SCG transmission is suspended and when one of the following conditions is met: + +- 1> upon detecting radio link failure for the SCG, in accordance with clause 5.3.10.3; +- 1> upon detecting beam failure of the PSCell while the SCG is deactivated, in accordance with TS 38.321[3]; +- 1> upon reconfiguration with sync failure of the SCG, in accordance with clause 5.3.5.8.3; +- 1> upon SCG configuration failure, in accordance with clause 5.3.5.8.2; +- 1> upon integrity check failure indication from SCG lower layers concerning SRB3. + +Upon initiating the procedure, the UE shall: + +- 1> if the procedure was not initiated due to beam failure of the PSCell while the SCG is deactivated: + - 2> suspend SCG transmission for all SRBs, DRBs and, if any, BH RLC channels; + - 2> reset SCG MAC; +- 1> stop T304 for the SCG, if running; +- 1> stop conditional reconfiguration evaluation for CPC, CPA, or subsequent CPAC, if configured; +- 1> stop conditional reconfiguration evaluation for each CHO configuration that includes *condExecutionCondPSCell*, if configured; +- 1> if the UE is in (NG)EN-DC: + - 2> initiate transmission of the *SCGFailureInformationNR* message as specified in TS 36.331 [10], clause 5.6.13a. +- 1> else: + - 2> initiate transmission of the *SCGFailureInformation* message in accordance with 5.7.3.5. + +#### 5.7.3.3 Failure type determination for (NG)EN-DC + +The UE shall set the SCG failure type as follows: + +- 1> if the UE initiates transmission of the *SCGFailureInformationNR* message due to T310 expiry: + - 2> set the *failureType* as t310-Expiry; +- 1> else if the UE initiates transmission of the *SCGFailureInformationNR* message due to T312 expiry: + - 2> set the *failureType* as any value and set the *failureType-v1610* as t312-Expiry; +- 1> else if the UE initiates transmission of the *SCGFailureInformationNR* message to provide reconfiguration with sync failure information for an SCG: + - 2> set the *failureType* as *synchReconfigFailureSCG*; +- 1> else if the UE initiates transmission of the *SCGFailureInformationNR* message to provide random access problem indication from SCG MAC: + - 2> if the random access procedure was initiated for beam failure recovery: + - 3> set the *failureType* as *randomAccessProblem* and set the *failureType-v1610* as *beamFailureRecoveryFailure*; + - 2> else: + - 3> set the *failureType* as *randomAccessProblem*; +- 1> else if the UE initiates transmission of the *SCGFailureInformationNR* message to provide indication from SCG RLC that the maximum number of retransmissions has been reached: + - 2> set the *failureType* as *rlc-MaxNumRetx*; +- 1> else if the UE initiates transmission of the *SCGFailureInformationNR* message due to SRB3 integrity check failure: + - 2> set the *failureType* as *srb3-IntegrityFailure*; +- 1> else if the UE initiates transmission of the *SCGFailureInformationNR* message due to Reconfiguration failure of NR RRC reconfiguration message: + - 2> set the *failureType* as *scg-reconfigFailure*; +- 1> else if the UE initiates transmission of the *SCGFailureInformationNR* message due to consistent uplink LBT failures: + - 2> set the *failureType* as any value and set the *failureType-v1610* as *scg-lbtFailure*; +- 1> else if connected as an IAB-node and the *SCGFailureInformationNR* is initiated due to the reception of a BH RLF indication on BAP entity from the SCG: + - 2> set the *failureType* as any value and set *failureType-v1610* as *bh-RLF*. +- 1> else if the UE initiates transmission of the *SCGFailureInformationNR* message due to beam failure of the PSCell while the SCG is deactivated: + +2> set the *failureType* as any value and set *failureType-v1610* as *beamFailure*. + +#### 5.7.3.4 Setting the contents of *MeasResultSCG-Failure* + +The UE shall set the contents of the *MeasResultSCG-Failure* as follows: + +- 1> for each *MeasObjectNR* configured on NR SCG for which a *measId* is configured and measurement results are available: + - 2> include an entry in *measResultPerMOList*; + - 2> if there is a *measId* configured with the *MeasObjectNR* and a *reportConfig* which has *rsType* set to *ssb*: + - 3> set *ssbFrequency* to the value indicated by *ssbFrequency* as included in the *MeasObjectNR*; + - 2> if there is a *measId* configured with the *MeasObjectNR* and a *reportConfig* which has *rsType* set to *csi-rs*: + - 3> set *refFreqCSI-RS* to the value indicated by *refFreqCSI-RS* as included in the associated measurement object; + - 2> if a serving cell is associated with the *MeasObjectNR*: + - 3> set *measResultServingCell* to include the available quantities of the concerned cell and in accordance with the performance requirements in TS 38.133 [14]; + - 2> set the *measResultNeighCellList* to include the best measured cells, ordered such that the best cell is listed first, and based on measurements collected up to the moment the UE detected the failure, and set its fields as follows: + - 3> ordering the cells with sorting as follows: + - 4> based on SS/PBCH block if SS/PBCH block measurement results are available and otherwise based on CSI-RS; + - 4> using RSRP if RSRP measurement results are available, otherwise using RSRQ if RSRQ measurement results are available, otherwise using SINR; + - 3> for each neighbour cell included: + - 4> include the optional fields that are available. + +NOTE: The measured quantities are filtered by the L3 filter as configured in the mobility measurement configuration. The measurements are based on the time domain measurement resource restriction, if configured. Exclude-listed cells are not required to be reported. + +- 1> if available, set the *locationInfo* as in 5.3.3.7 according to the *otherConfig* associated with the NR SCG. + +#### 5.7.3.5 Actions related to transmission of *SCGFailureInformation* message + +The UE shall set the contents of the *SCGFailureInformation* message as follows: + +- 1> if the UE initiates transmission of the *SCGFailureInformation* message due to T310 expiry: + - 2> set the *failureType* as *t310-Expiry*; +- 1> else if the UE initiates transmission of the *SCGFailureInformation* message due to T312 expiry: + - 2> set the *failureType* as *other* and set the *failureType-v1610* as *t312-Expiry*; +- 1> else if the UE initiates transmission of the *SCGFailureInformation* message to provide reconfiguration with sync failure information for an SCG: + - 2> set the *failureType* as *synchReconfigFailureSCG*; +- 1> else if the UE initiates transmission of the *SCGFailureInformation* message to provide random access problem indication from SCG MAC: + - 2> if the random access procedure was initiated for beam failure recovery: + - 3> set the *failureType* as *other* and set the *failureType-v1610* as *beamFailureRecoveryFailure*; + - 2> else: + - 3> set the *failureType* as *randomAccessProblem*; +- 1> else if the UE initiates transmission of the *SCGFailureInformation* message to provide indication from SCG RLC that the maximum number of retransmissions has been reached: + - 2> set the *failureType* as *rlc-MaxNumRetx*; +- 1> else if the UE initiates transmission of the *SCGFailureInformation* message due to SRB3 IP check failure: + - 2> set the *failureType* as *srb3-IntegrityFailure*; +- 1> else if the UE initiates transmission of the *SCGFailureInformation* message due to Reconfiguration failure of NR RRC reconfiguration message: + - 2> set the *failureType* as *scg-reconfigFailure*; +- 1> else if the UE initiates transmission of the *SCGFailureInformation* message due to consistent uplink LBT failures: + - 2> set the *failureType* as *other* and set the *failureType-v1610* as *scg-lbtFailure*; +- 1> else if connected as an IAB-node and the *SCGFailureInformation* is initiated due to the reception of a BH RLF indication on BAP entity from the SCG: + - 2> set the *failureType* as *other* and set *failureType-v1610* as *bh-RLF*; +- 1> else if the UE initiates transmission of the *SCGFailureInformation* message due to beam failure of the PSCell while the SCG is deactivated: + +- 2> set the *failureType* as *other* and set *failureType-v1610* as *beamFailure*; +- 1> include and set *MeasResultSCG-Failure* in accordance with 5.7.3.4; +- 1> for each *MeasObjectNR* configured by a *MeasConfig* associated with the MCG, and for which measurement results are available: + - 2> include an entry in *measResultFreqList*; + - 2> if there is a *measId* configured with the *MeasObjectNR* and a *reportConfig* which has *rsType* set to *ssb*: + - 3> set *ssbFrequency* in *measResultFreqList* to the value indicated by *ssbFrequency* as included in the *MeasObjectNR*; + - 2> if there is a *measId* configured with the *MeasObjectNR* and a *reportConfig* which has *rsType* set to *csi-rs*: + - 3> set *refFreqCSI-RS* in *measResultFreqList* to the value indicated by *refFreqCSI-RS* as included in the associated measurement object; + - 2> if a serving cell is associated with the *MeasObjectNR*: + - 3> set *measResultServingCell* in *measResultFreqList* to include the available quantities of the concerned cell and in accordance with the performance requirements in TS 38.133 [14]; + - 2> set the *measResultNeighCellList* in *measResultFreqList* to include the best measured cells, ordered such that the best cell is listed first, and based on measurements collected up to the moment the UE detected the failure, and set its fields as follows; + - 3> ordering the cells with sorting as follows: + - 4> based on SS/PBCH block if SS/PBCH block measurement results are available and otherwise based on CSI-RS; + - 4> using RSRP if RSRP measurement results are available, otherwise using RSRQ if RSRQ measurement results are available, otherwise using SINR; + - 3> if the UE supports SCG failure information for mobility robustness optimization for conditional PSCell change or addition, for each neighbour cell, if any, included in *measResultListNR* in *measResultFreqList*: + - 4> if the neighbour cell is one of the candidate cells for which the *reconfigurationWithSync* is included in the *secondaryCellGroup* in the MCG *VarConditionalReconfig* (for CPA or inter-SN CPC in NR-DC) or SCG *VarConditionalReconfig* (for intra-SN CPC) at the moment of the detected SCG failure (radio link failure at PSCell or PSCell change or addition failure): + - 5> if the first entry of *choConfig* corresponds to a fulfilled execution condition at the moment of SCG failure; or + - 5> if the second entry of *choConfig*, if available, corresponds to a fulfilled execution condition at the moment of SCG failure: + - 6> set *firstTriggeredEvent* to the execution condition *condFirstEvent* corresponding to the first entry of *choConfig* or to the execution condition *condSecondEvent* corresponding to the second entry of *choConfig*, whichever execution condition was fulfilled first in time; + +6> set *timeBetweenEvents* to the elapsed time between the point in time of fulfilling the condition in *choConfig* that was fulfilled first in time, and the point in time of fulfilling the condition in *choConfig* that was fulfilled second in time, if both the first execution condition corresponding to the first entry and the second execution condition corresponding to the second entry in the *choConfig* were fulfilled; + +3> for each neighbour cell included: + +4> include the optional fields that are available. + +NOTE 1: The measured quantities are filtered by the L3 filter as configured in the mobility measurement configuration. The measurements are based on the time domain measurement resource restriction, if configured. Exclude-listed cells are not required to be reported. + +NOTE 2: Field *measResultSCG-Failure* is used to report available results for NR frequencies the UE is configured to measure by SCG RRC signalling. + +1> if available, set the *locationInfo* as in 5.3.3.7 according to the *otherConfig* associated with the NR MCG. + +1> if the UE supports SCG failure for mobility robustness optimization: + +2> if the *failureType* is set to *synchReconfigFailureSCG*; or + +2> if the *failureType* is set to *randomAccessProblem* and the SCG failure was declared while T304 was running: + +3> set *perRAInfoList* to indicate the performed random access procedure related information as specified in 5.7.10.5. + +3> set the *failedPSCellId* to the physical cell identity and carrier frequency of the target PSCell of the failed PSCell change; + +3> set the *previousPSCellId* to the physical cell identity and carrier frequency of the source PSCell associated to the last received *RRReconfiguration* message including *reconfigurationWithSync* for the SCG, if available; + +3> set the *timeSCGFailure* to the elapsed time since the last execution of *RRReconfiguration* message including the *reconfigurationWithSync* for the SCG until declaring the SCG failure; + +2> else: + +3> set the *failedPSCellId* to the physical cell identity and carrier frequency of the PSCell in which the SCG failure was declared; + +3> if the last *RRReconfiguration* message including the *reconfigurationWithSync* for the SCG was received to enter the PSCell in which the SCG failure was declared: + +4> set the *timeSCGFailure* to the elapsed time since the last execution of *RRReconfiguration* message including the *reconfigurationWithSync* for the SCG until declaring the SCG failure; + +4> set the *previousPSCellId* to the physical cell identity and carrier frequency of the source PSCell associated to the last received *RRReconfiguration* message including *reconfigurationWithSync* for the SCG; + +1> release *successPSCell-Config* configured by the source PSCell, if available. + +The UE shall submit the *SCGFailureInformation* message to lower layers for transmission. + +### 5.7.3a EUTRA SCG failure information + +#### 5.7.3a.1 General + +![Sequence diagram showing the interaction between a UE and a Network for EUTRA SCG failure information. The UE sends an RRC reconfiguration message to the Network, and the Network responds with an SCGFailureInformationEUTRA message.](ff08f7fb49327c692a7e63a670ad0433_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Network + Note left of UE: + UE->>Network: RRC reconfiguration + Network-->>UE: SCGFailureInformationEUTRA + +``` + +Sequence diagram showing the interaction between a UE and a Network for EUTRA SCG failure information. The UE sends an RRC reconfiguration message to the Network, and the Network responds with an SCGFailureInformationEUTRA message. + +Figure 5.7.3a.1-1: EUTRA SCG failure information + +The purpose of this procedure is to inform NR MN about an SCG failure on E-UTRA SN the UE has experienced (e.g. SCG radio link failure, SCG change failure), as specified in TS 36.331 [10] clause 5.6.13.2. + +#### 5.7.3a.2 Initiation + +A UE initiates the procedure to report EUTRA SCG failures when neither NR MCG nor EUTRA SCG transmission is suspended and in accordance with TS 36.331 [10] clause 5.6.13.2. Actions the UE shall perform upon initiating the procedure, other than related to the transmission of the *SCGFailureInformationEUTRA* message are specified in TS 36.331 [10] clause 5.6.13.2. + +#### 5.7.3a.3 Actions related to transmission of *SCGFailureInformationEUTRA* message + +The UE shall set the contents of the *SCGFailureInformationEUTRA* message as follows: + +1> include *failureType* within *failureReportSCG-EUTRA* and set it to indicate the SCG failure in accordance with TS 36.331 [10] clause 5.6.13.4; + +1> include and set *measResultSCG-FailureMRDC* in accordance with TS 36.331 [10] clause 5.6.13.5; + +1> for each EUTRA frequency the UE is configured to measure by *measConfig* for which measurement results are available: + +2> set the *measResultFreqListMRDC* to include the best measured cells, ordered such that the best cell is listed first using RSRP to order if RSRP measurement results are available for cells on this frequency, otherwise using RSRQ to order if RSRQ measurement results are available for cells on this frequency, otherwise using SINR to + +order, and based on measurements collected up to the moment the UE detected the failure, and for each cell that is included, include the optional fields that are available; + +NOTE: Field *measResultSCG-FailureMRDC* is used to report available results for E-UTRAN frequencies the UE is configured to measure by E-UTRA RRC signalling. + +1> if available, set the *locationInfo* as in 5.3.3.7.: + +The UE shall submit the *SCGFailureInformationEUTRA* message to lower layers for transmission. + +### 5.7.3b MCG failure information + +#### 5.7.3b.1 General + +![Sequence diagram showing the interaction between a UE and a Network for MCG failure information. The UE sends an RRC reconfiguration message to the Network, and the Network responds with an MCGFailureInformation message.](8294325c2b0ef386b6f50eb1d6226b64_img.jpg) + +``` +sequenceDiagram + participant UE + participant Network + Note right of UE: MCG failure detected + UE->>Network: RRC reconfiguration + Network-->>UE: MCGFailureInformation +``` + +Sequence diagram showing the interaction between a UE and a Network for MCG failure information. The UE sends an RRC reconfiguration message to the Network, and the Network responds with an MCGFailureInformation message. + +Figure 5.7.3b.1-1: MCG failure information + +The purpose of this procedure is to inform the network about an MCG failure the UE has experienced i.e. MCG radio link failure. A UE in RRC\_CONNECTED, for which AS security has been activated with SRB2 and at least one DRB or multicast MRB setup or, for IAB, SRB2, may initiate the fast MCG link recovery procedure in order to continue the RRC connection without re-establishment. + +#### 5.7.3b.2 Initiation + +In case of MR-DC, a UE configured with split SRB1 or SRB3 initiates the procedure to report MCG failures when neither MCG nor SCG transmission is suspended, the SCG is not deactivated, *t316* is configured, and when the following condition is met; or + +In case of MP, a MP remote UE configured with split SRB1 initiates the procedure to report direct path failures when neither MCG (i.e. direct path) nor indirect path transmission is suspended, *t316* is configured, and when the following condition is met: + +1> upon detecting radio link failure of the MCG, in accordance with 5.3.10.3, while T316 is not running. + +Upon initiating the procedure, the UE shall: + +- 1> stop timer T310 for the PCell, if running; +- 1> stop timer T312 for the PCell, if running; +- 1> suspend MCG transmission for all SRBs, DRBs, multicast MRBs, except SRB0, and, if any, BH RLC channels; +- 1> reset MCG MAC; +- 1> stop conditional reconfiguration evaluation for CHO, if configured; +- 1> stop conditional reconfiguration evaluation for CPC or subsequent CPAC, if configured; +- 1> initiate transmission of the *MCGFailureInformation* message in accordance with 5.7.3b.4. + +NOTE: The handling of any outstanding UL RRC messages during the initiation of the fast MCG link recovery is left to UE implementation. + +#### 5.7.3b.3 Failure type determination + +The UE shall set the MCG failure type as follows: + +- 1> if the UE initiates transmission of the *MCGFailureInformation* message due to T310 expiry: + - 2> set the *failureType* as *t310-Expiry*; +- 1> else if the UE initiates transmission of the *MCGFailureInformation* message due to T312 expiry: + - 2> set the *failureType* as *t312-Expiry*; +- 1> else if the UE initiates transmission of the *MCGFailureInformation* message to provide random access problem indication from MCG MAC: + - 2> if the random access procedure was initiated for beam failure recovery: + - 3> set the *failureType* as *beamFailureRecoveryFailure*; + - 2> else: + - 3> set the *failureType* as *randomAccessProblem*; +- 1> else if the UE initiates transmission of the *MCGFailureInformation* message to provide indication from MCG RLC that the maximum number of retransmissions has been reached: + - 2> set the *failureType* as *rlc-MaxNumRetx*; +- 1> else if the UE initiates transmission of the *MCGFailureInformation* message due to consistent uplink LBT failures on the MCG: + +2> set the *failureType* as *lbt-Failure*; + +1> else if connected as an IAB-node and the *MCGFailureInformation* message is initiated due to the reception of a BH RLF indication on BAP entity from the MCG: + +2> set the *failureType* as *bh-RLF*. + +#### 5.7.3b.4 Actions related to transmission of *MCGFailureInformation* message + +The UE shall set the contents of the *MCGFailureInformation* message as follows: + +1> include and set *failureType* in accordance with 5.7.3b.3; + +1> for each *MeasObjectNR* configured by a *measConfig* associated with the MCG, and for which measurement results are available: + +2> include an entry in *measResultFreqList*; + +2> if there is a *measId* configured with the *MeasObjectNR* and a *reportConfig* which has *rsType* set to *ssb*: + +3> set *ssbFrequency* in *measResultFreqList* to the value indicated by *ssbFrequency* as included in the *MeasObjectNR*; + +2> if there is a *measId* configured with the *MeasObjectNR* and a *reportConfig* which has *rsType* set to *csi-rs*: + +3> set *refFreqCSI-RS* in *measResultFreqList* to the value indicated by *refFreqCSI-RS* as included in the associated measurement object; + +2> if a serving cell is associated with the *MeasObjectNR*: + +3> set *measResultServingCell* in *measResultFreqList* to include the available quantities of the concerned cell and in accordance with the performance requirements in TS 38.133 [14]; + +2> set the *measResultNeighCellList* in *measResultFreqList* to include the best measured cells, ordered such that the best cell is listed first, and based on measurements collected up to the moment the UE detected the failure, and set its fields as follows; + +3> ordering the cells with sorting as follows: + +4> based on SS/PBCH block if SS/PBCH block measurement results are available and otherwise based on CSI-RS; + +4> using RSRP if RSRP measurement results are available, otherwise using RSRQ if RSRQ measurement results are available, otherwise using SINR; + +3> for each neighbour cell included: + +4> include the optional fields that are available. + +1> for each EUTRA frequency the UE is configured to measure by *measConfig* for which measurement results are available: + +2> set the *measResultFreqListEUTRA* to include the best measured cells, ordered such that the best cell is listed first using RSRP to order the cells if RSRP measurement results are available for cells on this frequency, otherwise using RSRQ to order the cells if RSRQ measurement results are available for cells on this frequency, otherwise using SINR to order the cells, based on measurements collected up to the moment the UE detected the failure, and for each cell that is included, include the optional fields that are available; + +1> for each UTRA-FDD frequency the UE is configured to measure by *measConfig* for which measurement results are available: + +2> set the *measResultFreqListUTRA-FDD* to include the best measured cells, ordered such that the best cell is listed first using RSCP to order the cells if RSCP measurement results are available for cells on this frequency, otherwise using EcN0 to order the cells, based on measurements collected up to the moment the UE detected the failure, and for each cell that is included, include the optional fields that are available; + +1> if the UE is in NR-DC: + +2> include and set *measResultSCG* in accordance with 5.7.3.4; + +1> if the UE is in NE-DC: + +2> include and set *measResultSCG-EUTRA* in accordance with TS 36.331 [10] clause 5.6.13.5; + +NOTE 1: The measured quantities are filtered by the L3 filter as configured in the mobility measurement configuration. The measurements are based on the time domain measurement resource restriction, if configured. Exclude-listed cells are not required to be reported. + +NOTE 2: Field *measResultSCG-Failure* is used to report available results for NR frequencies the UE is configured to measure by SCG RRC signalling. + +NOTE 3: Field *measResultSCG-EUTRA* is used to report available results for E-UTRAN frequencies the UE is configured to measure by E-UTRA RRC signalling. + +1> if SRB1 is configured as split SRB and *pdcp-Duplication* is not configured: + +2> if the *primaryPath* for the PDCP entity of SRB1 refers to the MCG: + +3> set the *primaryPath* to refer to the SCG. + +The UE shall: + +1> start timer T316; + +1> if SRB1 is configured as split SRB: + +2> submit the *MCGFailureInformation* message to lower layers for transmission via SRB1, upon which the procedure ends; + +1> else (i.e. SRB3 configured): + +2> submit the *MCGFailureInformation* message to lower layers for transmission embedded in NR RRC message *ULInformationTransferMRDC* via SRB3 as specified in 5.7.2a.3. + +#### 5.7.3b.5 T316 expiry + +The UE shall: + +1> if T316 expires: + +2> initiate the connection re-establishment procedure as specified in 5.3.7. + +### 5.7.3c Indirect path failure information + +#### 5.7.3c.1 General + +![Sequence diagram showing the interaction between a UE and a Network for indirect path failure information. The UE sends an RRC reconfiguration message to the Network, and then the Network sends an IndirectPathFailureInformation message back to the UE.](3c88e5ce372025db2b065940e4a4391b_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Network + Note right of UE: RRC reconfiguration + UE->>Network: RRC reconfiguration + Note left of Network: IndirectPathFailureInformation + Network-->>UE: IndirectPathFailureInformation + +``` + +Sequence diagram showing the interaction between a UE and a Network for indirect path failure information. The UE sends an RRC reconfiguration message to the Network, and then the Network sends an IndirectPathFailureInformation message back to the UE. + +Figure 5.7.3c.1-1: Indirect path failure information + +The purpose of this procedure is to inform NR RAN about an indirect path failure the MP remote UE has experienced. + +#### 5.7.3c.2 Initiation + +In case of MP, a MP remote UE initiates the procedure to report indirect path failures when neither MCG nor indirect path transmission is suspended and when one of the following conditions is met: + +1> upon detecting a SL indirect path failure resulting from sidelink radio link failure on the PC5 unicast link or reception of *NotificationMessageSidelink* from the L2 U2N Relay UE indicating Uu failure, or indirect path addition/change failure in accordance with 5.3.5.17.2.3; or + +1> upon detecting a N3C indirect path failure, including N3C connection failure or Uu failure of the relay UE with N3C indirect path; + +Upon initiating the procedure, the UE shall: + +1> if the procedure was initiated to report SL indirect path failure: + +- 2> reset the sidelink specific MAC of this destination; +- 2> stop T421 if running; +- 1> suspend indirect path transmission for all SRBs and DRBs; +- 1> initiate transmission of the *IndirectPathFailureInformation* message in accordance with 5.7.3c.4; + +#### 5.7.3c.3 Failure type determination + +The L2 U2N Remote UE configured with SL indirect path shall set the indirect path failure type as follows: + +- 1> if the UE initiates transmission of the *IndirectPathFailureInformation* message due to T421 expiry in accordance with clause 5.3.5.16.1.3: + - 2> set the *failureTypeIndirectPath* as *t421-Expiry*; +- 1> else if the UE initiates transmission of the *IndirectPathFailureInformation* message due to reception of the *NotificationMessageSidelink* including *indicationType*, in accordance with clause 5.8.9.10.4: + - 2> set the *failureTypeIndirectPath* as the value in *indicationType* received from *NotificationMessageSidelink*; +- 1> else if the UE initiates transmission of the *IndirectPathFailureInformation* message due to sidelink radio link failure in accordance with clause 5.8.9.3: + - 2> set the *failureTypeIndirectPath* as *sl-Failure*; +- 1> if the target L2 U2N Relay UE (i.e., the UE indicated by *sl-IndirectPathRelayUE-Identity* in the received *sl-IndirectPathAddChange*) changes its serving PCell to a different cell from the target cell (i.e. the cell indicated by *sl-IndirectPathCellIdentity* in the received *sl-IndirectPathAddChange*) before path addition or change: + - 2> set the *failureTypeIndirectPath* as *indirectPathAddChangeFailure*; + +The N3C remote UE shall set the indirect path failure type as follows: + +- 1> if the UE initiates transmission of the *IndirectPathFailureInformation* message due to N3C connection failure: + - 2> set the *failureTypeIndirectPath* as *n3c-Failure*; +- 1> else if the UE initiates transmission of the *IndirectPathFailureInformation* message due to Uu radio link failure on N3C indirect path: + - 2> set the *failureTypeIndirectPath* as *relayUE-Uu-RLF*; + +NOTE: it is out of 3GPP scope how the remote UE detects N3C connection failure, or how the relay UE indicates Uu RLF to the remote UE on the N3C connection. + +#### 5.7.3c.4 Actions related to transmission of *IndirectPathFailureInformation* message + +The UE shall set the contents of the *IndirectPathFailureInformation* message as follows: + +- 1> set the *failureTypeIndirectPath* in accordance with 5.7.3c.3; +- 1> if the procedure was initiated to report SL indirect path failure: + - 2> set the *sl-MeasResultServingRelay* to include the measurement result for serving L2 U2N Relay UE if available; + - 2> for each *measObjectRelay* included *MeasConfig*, and for which measurement results are available: + - 3> include an entry in *sl-MeasResultsCandRelay*; +- 1> else if the procedure was initiated to report N3C indirect path failure; + - 2> include *n3c-relayUE-InfoList* to report relay UE information with non-3GPP connection(s) if available; +- 1> submit the *IndirectPathFailureInformation* message to lower layers for transmission. + +### 5.7.4 UE Assistance Information + +#### 5.7.4.1 General + +![Sequence diagram showing UE sending RRC Reconfiguration and UEAssistanceInformation to the Network.](180f1fb534ad2c1d918ede57612b3fb0_img.jpg) + +A sequence diagram illustrating the interaction between a User Equipment (UE) and a Network. The UE is represented by a vertical line on the left, and the Network by a vertical line on the right. Two messages are shown being sent from the UE to the Network: 'RRC Reconfiguration' and 'UEAssistanceInformation'. The 'RRC Reconfiguration' message is shown as a double line, while the 'UEAssistanceInformation' message is shown as a single line. Both messages are sent from the UE to the Network. + +Sequence diagram showing UE sending RRC Reconfiguration and UEAssistanceInformation to the Network. + +Figure 5.7.4.1-1: UE Assistance Information + +The purpose of this procedure is for the UE to inform the network of: + +- its delay budget report carrying desired increment/decrement in the connected mode DRX cycle length, or; +- its overheating assistance information, or; + +- its IDC assistance information, or; +- its preference on DRX parameters for power saving, or; +- its preference on the maximum aggregated bandwidth for power saving, or; +- its preference on the maximum number of secondary component carriers for power saving, or; +- its preference on the maximum number of MIMO layers for power saving, or; +- its preference on the minimum scheduling offset for cross-slot scheduling for power saving, or; +- its preference on the RRC state, or; +- configured grant assistance information for NR sidelink communication, or; +- its preference in being provisioned with reference time information, or; +- its preference for FR2 UL gap, or; +- its preference to transition out of RRC\_CONNECTED state for MUSIM operation, or; +- its preference on the MUSIM gaps, or; +- its preference on the MUSIM gap priority, or; +- its preference on the MUSIM temporary capability restriction, or; +- its relaxation state for RLM measurements, or; +- its relaxation state for BFD measurements, or; +- availability of data and/or signalling mapped to radio bearers which are not configured for SDT, or; +- its preference for the SCG to be deactivated, or; +- availability of uplink data to transmit for a DRB for which there is no MCG RLC bearer while the SCG is deactivated, or; +- change of its fulfilment status for RRM measurement relaxation criterion, or; +- service link (specified in TS 38.300 [2]) propagation delay difference between serving cell and neighbour cell(s); or +- its preference on multi-Rx operation for FR2; or +- availability of flight path information for Aerial UE operation; or + +- UL traffic information, or; +- the information of the relay UE(s) with which it connects via a non-3GPP connection for MP, or; +- configured grant assistance information for NR sidelink positioning. + +#### 5.7.4.2 Initiation + +A UE capable of providing delay budget report in RRC\_CONNECTED may initiate the procedure in several cases, including upon being configured to provide delay budget report and upon change of delay budget preference. + +A UE capable of providing overheating assistance information in RRC\_CONNECTED may initiate the procedure if it was configured to do so, upon detecting internal overheating, or upon detecting that it is no longer experiencing an overheating condition. + +A UE capable of providing IDC assistance information in RRC\_CONNECTED may initiate the procedure if it was configured to do so, upon detecting IDC problem if the UE did not transmit an IDC assistance information since it was configured to provide IDC indications, or upon change of IDC problem information. + +A UE capable of providing its preference on DRX parameters of a cell group for power saving in RRC\_CONNECTED may initiate the procedure in several cases, if it was configured to do so, including upon having a preference on DRX parameters and upon change of its preference on DRX parameters. + +A UE capable of providing its preference on the maximum aggregated bandwidth of a cell group for power saving in RRC\_CONNECTED may initiate the procedure in several cases, if it was configured to do so, including upon having a maximum aggregated bandwidth preference and upon change of its maximum aggregated bandwidth preference. + +A UE capable of providing its preference on the maximum number of secondary component carriers of a cell group for power saving in RRC\_CONNECTED may initiate the procedure in several cases, if it was configured to do so, including upon having a maximum number of secondary component carriers preference and upon change of its maximum number of secondary component carriers preference. + +A UE capable of providing its preference on the maximum number of MIMO layers of a cell group for power saving in RRC\_CONNECTED may initiate the procedure in several cases, if it was configured to do so, including upon having a maximum number of MIMO layers preference and upon change of its maximum number of MIMO layers preference. + +A UE capable of providing its preference on the minimum scheduling offset for cross-slot scheduling of a cell group for power saving in RRC\_CONNECTED may initiate the procedure in several cases, if it was configured to do so, including upon having a minimum scheduling offset preference and upon change of its minimum scheduling offset preference. + +A UE capable of providing assistance information to transition out of RRC\_CONNECTED state may initiate the procedure if it was configured to do so, upon determining that it prefers to transition out of RRC\_CONNECTED state, or upon change of its preferred RRC state. + +A UE capable of providing configured grant assistance information for NR sidelink communication in RRC\_CONNECTED may initiate the procedure in several cases, including upon being configured to provide traffic pattern information and upon change of traffic patterns. + +A UE capable of providing an indication of its preference in being provisioned with reference time information may initiate the procedure upon being configured to provide this indication, or if it was configured to provide this indication and upon change of its preference. + +A UE capable of providing an indication of its preference in FR2 UL gap may initiate the procedure if it was configured to do so, upon detecting the need of FR2 UL gap activation/deactivation. + +A UE capable of providing MUSIM assistance information for gap preference may initiate the procedure if it was configured to do so, upon determining it needs the gaps, or upon change of the gap preference information. + +A UE capable of providing MUSIM assistance information for gap priority preference may initiate the procedure if it was configured to do so, upon determining it has gap priority preference information. + +A UE capable of providing MUSIM assistance information for leave indication may initiate the procedure if it was configured to do so upon determining that it needs to leave RRC\_CONNECTED state. + +A UE capable of providing MUSIM assistance information for temporary capability restriction may initiate the procedure if it was configured to do so, upon determining it has temporary capability restriction or upon determining the removal of the capability restriction. + +A UE capable of relaxing its RLM measurements of a cell group in RRC\_CONNECTED state shall initiate the procedure for providing an indication of its relaxation state for RLM measurements upon being configured to do so, and upon change of its relaxation state for RLM measurements in RRC\_CONNECTED state. + +A UE capable of relaxing its BFD measurements in serving cells of a cell group in RRC\_CONNECTED shall initiate the procedure for providing an indication of its relaxation state for BFD measurements upon being configured to do so, and upon change of its relaxation state for BFD measurements in RRC\_CONNECTED state. + +A UE capable of SDT initiates this procedure when data and/or signalling mapped to radio bearers that are not configured for SDT becomes available during SDT (i.e. while SDT procedure is ongoing). + +A UE capable of providing its preference for SCG deactivation may initiate the procedure if it was configured to do so, upon determining that it prefers or does no more prefer the SCG to be deactivated. + +A UE that has uplink data to transmit for a DRB for which there is no MCG RLC bearer while the SCG is deactivated shall initiate the procedure. + +A UE capable of providing an indication of fulfilment of the RRM measurement relaxation criterion in connected mode may initiate the procedure if it was configured to do so, upon change of its fulfilment status for RRM measurement relaxation criterion for connected mode. + +A UE capable of providing service link propagation delay difference between serving cell and neighbour cell(s) shall initiate the procedure upon being configured to do so, and upon determining that service link propagation delay difference between serving cell and a neighbour cell has changed more than *threshPropDelayDiff* compared with the last reported value. + +A UE capable of providing an indication of its preference on multi-Rx operation for FR2 may initiate the procedure if it was configured to do so, upon detecting having a preference on multi-Rx operation for FR2 and upon change of its preference on multi-Rx operation for FR2. + +A UE capable of indicating the availability of flight path information may initiate the procedure, if it was configured to do so, upon determining that an initial or updated flight path information is available. + +A UE capable of providing UL traffic information shall initiate the procedure when the information is available upon being configured to do so, and upon change of UL traffic information. + +A UE capable of N3C remote UE operation initiates the procedure upon being configured to report relay UE information on the available non-3GPP connection(s), and upon change of its available non-3GPP connection(s). + +A UE capable of providing configured grant assistance information including SL-PRS transmission periodicity and priority for NR sidelink positioning in RRC\_CONNECTED may initiate the procedure. + +*Editor's Note: FFS the details of configured grant assistance information.* + +Upon initiating the procedure, the UE shall: + +- 1> if configured to provide delay budget report: + - 2> if the UE did not transmit a *UEAssistanceInformation* message with *delayBudgetReport* since it was configured to provide delay budget report; or + - 2> if the current delay budget is different from the one indicated in the last transmission of the *UEAssistanceInformation* message including *delayBudgetReport* and timer T342 is not running: + - 3> start or restart timer T342 with the timer value set to the *delayBudgetReportingProhibitTimer*; + - 3> initiate transmission of the *UEAssistanceInformation* message in accordance with 5.7.4.3 to provide a delay budget report; +- 1> if configured to provide overheating assistance information: + - 2> if the overheating condition has been detected and T345 is not running; or + - 2> if the current overheating assistance information is different from the one indicated in the last transmission of the *UEAssistanceInformation* message including *overheatingAssistance* and timer T345 is not running: + - 3> start timer T345 with the timer value set to the *overheatingIndicationProhibitTimer*; + - 3> initiate transmission of the *UEAssistanceInformation* message in accordance with 5.7.4.3 to provide overheating assistance information; +- 1> if configured to provide IDC assistance information based on *candidateServingFreqListNR* included in *idc-AssistanceConfig* of a cell group: + - 2> if the UE did not transmit a *UEAssistanceInformation* message with *idc-Assistance* since it was configured to provide IDC assistance information: + - 3> if on one or more frequencies included in *candidateServingFreqListNR*, the UE is experiencing IDC problems that it cannot solve by itself; or + - 3> if on one or more supported UL CA or NR-DC combination comprising of carrier frequencies included in *candidateServingFreqListNR*, the UE is experiencing IDC problems that it cannot solve by itself; + +- 4> initiate transmission of the *UEAssistanceInformation* message in accordance with 5.7.4.3 to provide IDC assistance information; +- 2> else if the current *idc-Assistance* information for the cell group is different from the one indicated in the last transmission of the *UEAssistanceInformation* message: + - 3> initiate transmission of the *UEAssistanceInformation* message in accordance with 5.7.4.3 to provide IDC assistance information; +- 1> if configured to provide IDC assistance information based on *idc-FDM-AssistanceConfig* included in *idc-AssistanceConfig* of a cell group: + - 2> if the UE did not transmit a *UEAssistanceInformation* message with *idc-FDM-Assistance* since it was configured to provide IDC assistance information: + - 3> if on one or more frequency ranges included in *candidateServingFreqRangeListNR*, the UE is experiencing IDC problems that it cannot solve by itself; or + - 3> if on one or more supported UL CA or NR-DC combination comprising of frequency ranges included in *candidateServingFreqRangeListNR*, the UE is experiencing IDC problems that it cannot solve by itself: + - 4> initiate transmission of the *UEAssistanceInformation* message in accordance with 5.7.4.3 to provide IDC assistance information; + - 2> else if the current *idc-FDM-Assistance* information for the cell group is different from the one indicated in the last transmission of the *UEAssistanceInformation* message: + - 3> initiate transmission of the *UEAssistanceInformation* message in accordance with 5.7.4.3 to provide IDC assistance information; +- 1> if configured to provide IDC assistance information based on *idc-TDM-AssistanceConfig* included in *idc-AssistanceConfig* of a cell group: + - 2> if the UE did not transmit a *UEAssistanceInformation* message with *idc-TDM-Assistance* since it was configured to provide IDC assistance information: + - 3> if on one or more frequencies included in *candidateServingFreqListNR* or frequency ranges included in *candidateServingFreqRangeListNR*, the UE is experiencing IDC problems that it cannot solve by itself; or + - 3> if on one or more supported UL CA or NR-DC combination comprising of carrier frequencies included in *candidateServingFreqListNR* or frequency ranges included in *candidateServingFreqRangeListNR*, the UE is experiencing IDC problems that it cannot solve by itself: + - 4> initiate transmission of the *UEAssistanceInformation* message in accordance with 5.7.4.3 to provide IDC assistance information; + - 2> else if the current *idc-TDM-Assistance* information for the cell group is different from the one indicated in the last transmission of the *UEAssistanceInformation* message: + - 3> initiate transmission of the *UEAssistanceInformation* message in accordance with 5.7.4.3 to provide IDC assistance information; + +NOTE 1: The term "IDC problems" refers to interference issues applicable across several subframes/slots where not necessarily all the subframes/slots are affected. + +NOTE 2: For the frequencies on which a serving cell or serving cells is configured that is activated, IDC problems consist of interference issues that the UE cannot solve by itself, during either active data exchange or upcoming data activity which is expected in up to a few hundred milliseconds. + +For frequencies on which a SCell or SCells is configured that is deactivated, reporting IDC problems indicates an anticipation that the activation of the SCell or SCells would result in interference issues that the UE would not be able to solve by itself. + +For a non-serving frequency, reporting IDC problems indicates an anticipation that if the non-serving frequency or frequencies became a serving frequency or serving frequencies then this would result in interference issues that the UE would not be able to solve by itself. + +1> if configured to provide its preference on DRX parameters of a cell group for power saving: + +2> if the UE has a preference on DRX parameters of the cell group and the UE did not transmit a *UEAssistanceInformation* message with *drx-Preference* for the cell group since it was configured to provide its preference on DRX parameters of the cell group for power saving; or + +2> if the current *drx-Preference* information for the cell group is different from the one indicated in the last transmission of the *UEAssistanceInformation* message including *drx-Preference* for the cell group and timer T346a associated with the cell group is not running: + +3> start the timer T346a with the timer value set to the *drx-PreferenceProhibitTimer* of the cell group; + +3> initiate transmission of the *UEAssistanceInformation* message in accordance with 5.7.4.3 to provide the current *drx-Preference*; + +1> if configured to provide its preference on the maximum aggregated bandwidth of a cell group for power saving: + +2> if the UE has a preference on the maximum aggregated bandwidth of the cell group and the UE did not transmit a *UEAssistanceInformation* message with *maxBW-Preference* and/or *maxBW-PreferenceFR2-2* for the cell group since it was configured to provide its preference on the maximum aggregated bandwidth of the cell group for power saving; or + +2> if the current *maxBW-Preference* information for the cell group is different from the one indicated in the last transmission of the *UEAssistanceInformation* message including *maxBW-Preference* and/or *maxBW-PreferenceFR2-2* for the cell group and timer T346b associated with the cell group is not running: + +3> start the timer T346b with the timer value set to the *maxBW-PreferenceProhibitTimer* of the cell group; + +3> initiate transmission of the *UEAssistanceInformation* message in accordance with 5.7.4.3 to provide the current *maxBW-Preference* and/or *maxBW-PreferenceFR2-2*; + +1> if configured to provide its preference on the maximum number of secondary component carriers of a cell group for power saving: + +2> if the UE has a preference on the maximum number of secondary component carriers of the cell group and the UE did not transmit a *UEAssistanceInformation* message with *maxCC-Preference* for the cell group since it was configured to provide its preference on the maximum number of secondary component carriers of the cell group for power saving; or + +2> if the current *maxCC-Preference* information for the cell group is different from the one indicated in the last transmission of the *UEAssistanceInformation* message including *maxCC-Preference* for the cell group and timer T346c associated with the cell group is not running: + +3> start the timer T346c with the timer value set to the *maxCC-PreferenceProhibitTimer* of the cell group; + +3> initiate transmission of the *UEAssistanceInformation* message in accordance with 5.7.4.3 to provide the current *maxCC-Preference*; + +1> if configured to provide its preference on the maximum number of MIMO layers of a cell group for power saving: + +2> if the UE has a preference on the maximum number of MIMO layers of the cell group and the UE did not transmit a *UEAssistanceInformation* message with *maxMIMO-LayerPreference* and/or *maxMIMO-LayerPreferenceFR2-2* for the cell group since it was configured to provide its preference on the maximum number of MIMO layers of the cell group for power saving; or + +2> if the current *maxMIMO-LayerPreference* information for the cell group is different from the one indicated in the last transmission of the *UEAssistanceInformation* message including *maxMIMO-LayerPreference* and/or *maxMIMO-LayerPreferenceFR2-2* for the cell group and timer T346d associated with the cell group is not running: + +3> start the timer T346d with the timer value set to the *maxMIMO-LayerPreferenceProhibitTimer* of the cell group; + +3> initiate transmission of the *UEAssistanceInformation* message in accordance with 5.7.4.3 to provide the current *maxMIMO-LayerPreference* and/or *maxMIMO-LayerPreferenceFR2-2*; + +1> if configured to provide its preference on the minimum scheduling offset for cross-slot scheduling of a cell group for power saving: + +2> if the UE has a preference on the minimum scheduling offset for cross-slot scheduling of the cell group and the UE did not transmit a *UEAssistanceInformation* message with *minSchedulingOffsetPreference* and/or *minSchedulingOffsetPreferenceExt* for the cell group since it was configured to provide its preference on the minimum scheduling offset for cross-slot scheduling of the cell group for power saving; or + +2> if the current *minSchedulingOffsetPreference* and/or *minSchedulingOffsetPreferenceExt* information for the cell group is different from the one indicated in the last transmission of the *UEAssistanceInformation* message including *minSchedulingOffsetPreference* and/or *minSchedulingOffsetPreferenceExt* for the cell group and timer T346e associated with the cell group is not running: + +3> start the timer T346e with the timer value set to the *minSchedulingOffsetPreferenceProhibitTimer* of the cell group; + +3> initiate transmission of the *UEAssistanceInformation* message in accordance with 5.7.4.3 to provide the current *minSchedulingOffsetPreference* and/or *minSchedulingOffsetPreferenceExt*; + +1> if configured to provide its release preference and timer T346f is not running: + +2> if the UE determines that it would prefer to transition out of RRC\_CONNECTED state; or + +2> if the UE is configured with *connectedReporting* and the UE determines that it would prefer to revert an earlier indication to transition out of RRC\_CONNECTED state: + +3> start timer T346f with the timer value set to the *releasePreferenceProhibitTimer*; + +3> initiate transmission of the *UEAssistanceInformation* message in accordance with 5.7.4.3 to provide the release preference; + +- 1> if configured to provide configured grant assistance information for NR sidelink communication: + - 2> initiate transmission of the *UEAssistanceInformation* message in accordance with 5.7.4.3 to provide configured grant assistance information for NR sidelink communication; +- 1> if configured to provide preference in being provisioned with reference time information: + - 2> if the UE did not transmit a *UEAssistanceInformation* message with *referenceTimeInfoPreference* since it was configured to provide preference; or + - 2> if the UE's preference changed from the last time UE initiated transmission of the *UEAssistanceInformation* message including *referenceTimeInfoPreference*: + - 3> initiate transmission of the *UEAssistanceInformation* message in accordance with 5.7.4.3 to provide preference in being provisioned with reference time information. +- 1> if configured to provide its preference on FR2 UL gap: + - 2> if the UE did not transmit a *UEAssistanceInformation* message with *ul-GapFR2-Preference* since it was configured to provide its preference on FR2 UL gap information: + - 3> if the UE has a preference on FR2 UL gap activation/deactivation: + - 4> initiate transmission of the *UEAssistanceInformation* message in accordance with 5.7.4.3 to provide FR2 UL gap preference; + - 2> else if the current FR2 UL gap preference is different from the one indicated in the last transmission of the *UEAssistanceInformation* message: + - 3> initiate transmission of the *UEAssistanceInformation* message in accordance with 5.7.4.3 to provide FR2 UL gap preference. +- 1> if configured to provide MUSIM assistance information for leaving RRC\_CONNECTED: + - 2> if the UE needs to leave RRC\_CONNECTED state and the timer T346g is not running: + - 3> initiate transmission of the *UEAssistanceInformation* message in accordance with 5.7.4.3 to provide MUSIM assistance information for leaving RRC\_CONNECTED; + - 3> start the timer T346g with the timer value set to the *musim-LeaveWithoutResponseTimer*; +- 1> if configured to provide MUSIM assistance information for gap preference: + - 2> if the UE has a preference on the MUSIM gap(s) and the UE did not transmit a *UEAssistanceInformation* message with *musim-GapPreferenceList* since it was configured to provide MUSIM assistance information for gap preference; or + - 2> if the current *musim-GapPreferenceList* is different from the one indicated in the last transmission of the *UEAssistanceInformation* message including *musim-GapPreferenceList* and the timer T346h is not running: + +3> initiate transmission of the *UEAssistanceInformation* message in accordance with 5.7.4.3 to provide the current *musim-GapPreferenceList*; + +3> start or restart the timer T346h with the timer value set to the *musim-GapProhibitTimer*. + +NOTE 3: The UE does not need to initiate transmission of the *UEAssistanceInformation* message if the difference between the current *musim-GapPreferenceList* and the last transmission of the *UEAssistanceInformation* message including *musim-GapPreferenceList* is only due to removal of an ended aperiodic gap. + +1> if configured to provide MUSIM assistance information for gap priority preference: + +2> if the UE has a preference on the MUSIM gap(s) priority and the UE did not transmit a *UEAssistanceInformation* message with *musim-GapPriorityPreferenceList* since it was configured to provide MUSIM assistance information for gap priority preference; or + +2> if the current *musim-GapPriorityPreferenceList* is different from the one indicated in the last transmission of the *UEAssistanceInformation* message including *musim-GapPriorityPreferenceList* and the timer T346h is not running: + +3> initiate transmission of the *UEAssistanceInformation* message in accordance with 5.7.4.3 to provide the *musim-GapPriorityPreferenceList*; + +3> start or restart the timer T346h with the timer value set to the *musim-GapProhibitTimer*. + +1> if configured to provide MUSIM assistance information for temporary capability restriction: + +2> if the UE has temporary capability restriction on the current configuration and timer T348 is not running: + +3> initiate transmission of the *UEAssistanceInformation* message in accordance with 5.7.4.3 to provide the current *musim-Cell-SCG-ToRelease and/or musim-CellToAffectList*; + +3> start the timer T348 with the timer value set to the *musim-WaitTimer*. + +2> if the UE has temporary capability restriction on the current band(s) or combination(s) of bands and the UE did not transmit a *UEAssistanceInformation* message with *musim-AffectedBandsList and/or musim-AvoidedBandsList* since it was configured to provide MUSIM assistance information for temporary capability restriction; or + +2> if the current *musim-AffectedBandsList and/or musim-AvoidedBandsList* is different from the one indicated in the last transmission of the *UEAssistanceInformation* message including *musim-CapRestriction* and timer T346n is not running: + +3> initiate transmission of the *UEAssistanceInformation* message in accordance with 5.7.4.3 to provide the current *musim-AffectedBandsList and/or musim-AvoidedBandsList*; + +3> start the timer T346n with the timer value set to the *musim-ProhibitTimer*. + +2> if the UE has a preference on the measurement gap requirement information and the UE did not transmit a *UEAssistanceInformation* message with measurement gap requirement information or *RRRCReconfigurationComplete* message or *RRRCResumeComplete* message with measurement gap requirement information since it was configured to provide its preference on the measurement gap requirement information for MUSIM; or + +2> if the current *musim-NeedForGapsInfoNR* is different from the one indicated in the last transmission of the *UEAssistanceInformation* message or *RRCReconfigurationComplete* message or *RRCResumeComplete* message including *musim-CapRestriction* to provide the *needForGapsInfoNR* for the measurement gap requirement of NR target bands: + +3> initiate transmission of the *UEAssistanceInformation* message in accordance with 5.7.4.3 to provide the current *musim-NeedForGapsInfoNR*; + +Editor's Note: FFS whether UE should start a timer, e.g., Timer T348. + +1> if configured to provide the relaxation state of RLM measurements of a cell group and RLM measurement of the cell group is not stopped: + +2> if the UE did not transmit a *UEAssistanceInformation* message with *rlm-MeasRelaxationState* since it was configured to provide the relaxation state of RLM measurements for the cell group; or + +- 2> if the relaxation state of RLM measurements for the cell group is currently different from the relaxation state reported in the last transmission of the *UEAssistanceInformation* message including *rlm-MeasRelaxationState* of the cell group and timer T346j associated with the cell group is not running: + - 3> start timer T346j with the timer value set to the *rlm-RelaxationReportingProhibitTimer*; + - 3> initiate transmission of the *UEAssistanceInformation* message in accordance with 5.7.4.3 to provide the relaxation state of RLM measurements of the cell group; +- 1> if configured to provide the relaxation state of BFD measurements of serving cells of a cell group and BFD measurement of the cell group is not stopped: + - 2> if the UE did not transmit a *UEAssistanceInformation* message with *bfd-MeasRelaxationState* since it was configured to provide the relaxation state of BFD measurements for the cell group; or + - 2> if the relaxation state of BFD measurements in any serving cell of the cell group is currently different from the relaxation state reported in the last transmission of the *UEAssistanceInformation* message including *bfd-MeasRelaxationState* of the cell group and timer T346k associated with the cell group is not running: + - 3> start timer T346k with the timer value set to the *bfd-RelaxationReportingProhibitTimer*; + - 3> initiate transmission of the *UEAssistanceInformation* message in accordance with 5.7.4.3 to provide the relaxation state of BFD measurements of serving cells of the cell group. +- 1> if data and/or signalling mapped to radio bearers not configured for SDT becomes available during SDT (i.e. while SDT procedure is ongoing): + - 2> if the UE did not transmit a *UEAssistanceInformation* message with *nonSDT-DataIndication* since the initiation of the current resume procedure for SDT: + - 3> initiate transmission of the *UEAssistanceInformation* message in accordance with 5.7.4.3 to provide *nonSDT-DataIndication*. +- 1> if configured to provide its preference for SCG deactivation and timer T346i is not running: + - 2> if the UE prefers the SCG to be deactivated and did not transmit a *UEAssistanceInformation* message with *scg-DeactivationPreference* since it was configured to provide its SCG deactivation preference; or + - 2> if the UE preference for SCG deactivation is different from the last indicated *scg-DeactivationPreference*: + - 3> start timer T346i with the timer value set to the *scg-DeactivationPreferenceProhibitTimer*; + - 3> initiate transmission of the *UEAssistanceInformation* message in accordance with 5.7.4.3 to provide the UE preference for SCG deactivation; +- 1> if the SCG is deactivated, and, +- 1> the UE has uplink data to send for an SCG RLC entity while the UE previously did not have any uplink data to send for any SCG RLC entity: + - 2> initiate transmission of the *UEAssistanceInformation* message in accordance with 5.7.4.3 to indicate that the UE has uplink data to send for a DRB whose *DRB-Identity* is not included in any *RLC-BearerConfig* in the *CellGroupConfig* associated with the MCG. +- 1> if configured to send indications of RRM measurement relaxation criterion fulfilment: + - 2> if the criterion in 5.7.4.4 is met for a period of $T_{\text{SearchDeltaP-StationaryConnected}}$ : + - 3> if the UE did not transmit a *UEAssistanceInformation* message with *rrm-MeasRelaxationFulfilment* as *true* since it was configured to provide indications of RRM measurement relaxation criterion fulfilment; or + - 3> the last *UEAssistanceInformation* message indicated the criterion in 5.7.4.4 is not fulfilled with *rrm-MeasRelaxationFulfilment* as *false*: + +- 4> initiate transmission of the *UEAssistanceInformation* message in accordance with 5.7.4.3 to indicate that the criterion for RRM measurement relaxation for connected mode is fulfilled; + - 2> else: + - 3> if the last *UEAssistanceInformation* message indicated fulfilment of the criterion in 5.7.4.4 with *rrm-MeasRelaxationFulfilment* as true: + - 4> initiate transmission of the *UEAssistanceInformation* message in accordance with 5.7.4.3 to indicate that the criterion for RRM measurement relaxation for connected mode is not fulfilled. + - 1> if configured to provide service link propagation delay difference between serving cell and neighbour cell(s); + - 2> if the UE did not transmit a *UEAssistanceInformation* message with *propagationDelayDifference* since it was configured to provide service link propagation delay difference between serving cell and neighbour cell(s); or + - 2> for any neighbour cell in *neighCellInfoList*, if the service link propagation delay difference between serving cell and the neighbour cell has changed more than *threshPropDelayDiff* since the last transmission of the *UEAssistanceInformation* message including *propagationDelayDifference*: + - 3> initiate transmission of the *UEAssistanceInformation* message in accordance with 5.7.4.3 to provide service link propagation delay difference between serving cell and each neighbour cell included in the *neighCellInfoList*; + - 1> if configured to provide its preference for multi-Rx operation and timer T440 is not running; + - 2> if the UE has a preference on multi-Rx operation for FR2 and did not transmit a *UEAssistanceInformation* message with *multiRx-PreferenceFR2* since it was configured to provide its preference on multi-Rx operation; or + - 2> if the UE has a different preference on multi-Rx operation for FR2 from the last indicated *multiRx-PreferenceFR2*: + - 3> start timer T440 with the timer value set to the *multiRx-PreferenceReportingConfigFR2ProhibitTimer*; + - 3> initiate transmission of the *UEAssistanceInformation* message in accordance with 5.7.4.3 to provide the UE preference for multi-Rx operation for FR2. + - 1> if configured to indicate the availability of flight path information and the UE has flight path information available: + - 2> if the UE had not previously provided a flight path information since last entering RRC\_CONNECTED state; or + - 2> if at least one waypoint was not previously provided; or + - 2> if at least one upcoming waypoint that was previously provided is being removed; or + - 2> if *flightPathUpdateDistanceThr* is configured and for at least one waypoint, the 3D distance between the previously provided location and the new location is more than or equal to the distance threshold configured by *flightPathUpdateDistanceThr*; or + - 2> if *flightPathUpdateTimeThr* is configured and for at least one waypoint, the timestamp was not previously provided but is now available, or the time between the previously provided timestamp and the new timestamp, if available, is more than or equal to the time threshold configured by *flightPathUpdateTimeThr*: + - 3> initiate transmission of the *UEAssistanceInformation* message in accordance with 5.7.4.3 to indicate the availability of flight path information; +- NOTE 4: If neither *flightPathUpdateDistanceThr* nor *flightPathUpdateTimeThr* is configured, it is up to UE implementation whether to initiate transmission of the *UEAssistanceInformation* message when updated flight path information is available. +- 1> if configured to provide UL traffic information: + +- 2> if the UE did not transmit a *UEAssistanceInformation* message with *ul-TrafficInfo* since it was configured to provide UL traffic information; or +- 2> if UL traffic information included in the previous *UEAssistanceInformation* has changed since the last transmission of the *UEAssistanceInformation* message containing *ul-TrafficInfo* for at least one QoS flow for which timer T346x is not running: +- 3> initiate transmission of the *UEAssistanceInformation* message in accordance with 5.7.4.3 to provide UL traffic information. + +NOTE 5: The UE only considers *burstArrivalTime* to have changed when it changes relative to the periodicity of the Data Burst arrival. + +- 1> if configured to report relay UE information with non-3GPP connection(s); + - 2> if the UE did not transmit a *UEAssistanceInformation* message with *n3c-relayUE-InfoList* since it was configured to report available relay UE information with non-3GPP connection(s); or + - 2> if the UE has new available non-3GPP connection(s); or + - 2> if the non-3GPP connection(s) with the reported relay UE(s) is not available: + - 3> initiate transmission of the *UEAssistanceInformation* message in accordance with 5.7.4.3 to report relay UE information with non-3GPP connection(s) included in the *n3c-relayUE-InfoList*; +- 1> if configured to provide configured grant assistance information for NR sidelink positioning: + - 2> initiate transmission of the *UEAssistanceInformation* message in accordance with 5.7.4.3 to provide configured grant assistance information for NR sidelink positioning; + +#### 5.7.4.3 Actions related to transmission of *UEAssistanceInformation* message + +The UE shall set the contents of the *UEAssistanceInformation* message as follows: + +- 1> if transmission of the *UEAssistanceInformation* message is initiated to provide a delay budget report according to 5.7.4.2 or 5.3.5.3; + - 2> set *delayBudgetReport* to *type1* according to a desired value; +- 1> if transmission of the *UEAssistanceInformation* message is initiated to provide overheating assistance information according to 5.7.4.2 or 5.3.5.3; + - 2> if the UE experiences internal overheating: + - 3> if the UE prefers to temporarily reduce the number of maximum secondary component carriers: + - 4> include *reducedMaxCCs* in the *OverheatingAssistance* IE; + - 4> set *reducedCCsDL* to the number of maximum SCells the UE prefers to be temporarily configured in downlink; + - 4> set *reducedCCsUL* to the number of maximum SCells the UE prefers to be temporarily configured in uplink; + - 3> if the UE prefers to temporarily reduce maximum aggregated bandwidth of FR1: + - 4> include *reducedMaxBW-FR1* in the *OverheatingAssistance* IE; + - 4> set *reducedBW-DL* to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all downlink carriers of FR1; + - 4> set *reducedBW-UL* to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all uplink carriers of FR1; + - 3> if the UE prefers to temporarily reduce maximum aggregated bandwidth of FR2-1: + - 4> include *reducedMaxBW-FR2* in the *OverheatingAssistance* IE; + +- 4> set *reducedBW-DL* to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all downlink carriers of FR2-1; + - 4> set *reducedBW-UL* to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all uplink carriers of FR2-1; + - 3> if the UE prefers to temporarily reduce maximum aggregated bandwidth of FR2-2: + - 4> include *reducedMaxBW-FR2-2* in the *OverheatingAssistance IE*; + - 4> set *reducedBW-FR2-2-DL* to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all downlink carriers of FR2-2; + - 4> set *reducedBW-FR2-2-UL* to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all uplink carriers of FR2-2; + - 3> if the UE prefers to temporarily reduce the number of maximum MIMO layers of each serving cell operating on FR1: + - 4> include *reducedMaxMIMO-LayersFR1* in the *OverheatingAssistance IE*; + - 4> set *reducedMIMO-LayersFR1-DL* to the number of maximum MIMO layers of each serving cell operating on FR1 the UE prefers to be temporarily configured in downlink; + - 4> set *reducedMIMO-LayersFR1-UL* to the number of maximum MIMO layers of each serving cell operating on FR1 the UE prefers to be temporarily configured in uplink; + - 3> if the UE prefers to temporarily reduce the number of maximum MIMO layers of each serving cell operating on FR2-1: + - 4> include *reducedMaxMIMO-LayersFR2* in the *OverheatingAssistance IE*; + - 4> set *reducedMIMO-LayersFR2-DL* to the number of maximum MIMO layers of each serving cell operating on FR2-1 the UE prefers to be temporarily configured in downlink; + - 4> set *reducedMIMO-LayersFR2-UL* to the number of maximum MIMO layers of each serving cell operating on FR2-1 the UE prefers to be temporarily configured in uplink; + - 3> if the UE prefers to temporarily reduce the number of maximum MIMO layers of each serving cell operating on FR2-2: + - 4> include *reducedMaxMIMO-LayersFR2-2* in the *OverheatingAssistance IE*; + - 4> set *reducedMIMO-LayersFR2-2-DL* to the number of maximum MIMO layers of each serving cell operating on FR2 the UE prefers to be temporarily configured in downlink; + - 4> set *reducedMIMO-LayersFR2-2-UL* to the number of maximum MIMO layers of each serving cell operating on FR2 the UE prefers to be temporarily configured in uplink; + - 2> else (if the UE no longer experiences an overheating condition): + - 3> do not include *reducedMaxCCs*, *reducedMaxBW-FR1*, *reducedMaxBW-FR2*, *reducedMaxBW-FR2-2*, *reducedMaxMIMO-LayersFR1*, *reducedMaxMIMO-LayersFR2* or *reducedMaxMIMO-LayersFR2-2* in *OverheatingAssistance IE*; +- 1> if transmission of the *UEAssistanceInformation* message is initiated to provide IDC assistance information according to 5.7.4.2 or 5.3.5.3: + - 2> if there is at least one carrier frequency included in *candidateServingFreqListNR*, the UE is experiencing IDC problems that it cannot solve by itself: + - 3> include the field *affectedCarrierFreqList* with an entry for each affected carrier frequency included in *candidateServingFreqListNR*; + - 3> for each carrier frequency included in the field *affectedCarrierFreqList*, include *interferenceDirection* and set it accordingly; + +- 2> if there is at least one supported UL CA or NR-DC combination comprising of carrier frequencies included in *candidateServingFreqListNR*, the UE is experiencing IDC problems that it cannot solve by itself: + - 3> include *victimSystemType* for each UL CA or NR-DC combination included in *affectedCarrierFreqCombList*; + - 3> if the UE sets *victimSystemType* to *wlan* or *bluetooth*: + - 4> include *affectedCarrierFreqCombList* with an entry for each supported UL CA combination comprising of carrier frequencies included in *candidateServingFreqListNR*, that is affected by IDC problems; + - 3> else: + - 4> optionally include *affectedCarrierFreqCombList* with an entry for each supported UL CA or NR-DC combination comprising of carrier frequencies included in *candidateServingFreqListNR*, that is affected by IDC problems; +- 2> if there is at least one affected frequency range overlapping with one candidate frequency range included in *candidateServingFreqRangeListNR*, and the center frequency of the affected frequency range is within the candidate frequency range included in *candidateServingFreqRangeListNR*, the UE is experiencing IDC problems that it cannot solve by itself: + - 3> include the field *affectedCarrierFreqRangeList* with an entry for each affected frequency range; + - 3> for each affected frequency range included in the field *affectedCarrierFreqRangeList*, include *centerFreq* and *affectedBandwidth*; + - 3> for each affected frequency range included in the field *affectedCarrierFreqRangeList*, include *interferenceDirection* and optionally *victimSystemType*, and set it accordingly; +- 2> if there is at least one supported UL CA or NR-DC combinations comprising of candidate frequency ranges included in *candidateServingFreqRangeListNR*, and each affected frequency range in the UL CA or NR-DC combination overlapping with one candidate frequency range included in *candidateServingFreqRangeListNR*, and the center frequency of the affected frequency range is within the candidate frequency range included in *candidateServingFreqRangeListNR*, the UE is experiencing IDC problems that it cannot solve by itself: + - 3> include the field *affectedCarrierFreqRangeCombList* with an entry for each supported UL CA or NR-DC combination comprising of frequency ranges that is affected by IDC problems; + - 3> for each affected frequency range included in the field *affectedCarrierFreqRangeCombList*, include *centerFreq* and *affectedBandwidth*; + - 3> for each UL CA or NR-DC combination included in the field *affectedCarrierFreqRangeCombList*, include *interferenceDirection* and optionally *victimSystemType*, and set it accordingly; +- 2> if there is at least one candidate carrier frequency included in *candidateServingFreqListNR* or candidate frequency range included in *candidateServingFreqRangeListNR* or one supported UL CA or NR-DC combination comprising of candidate carrier frequencies included in *candidateServingFreqListNR* or candidate frequency ranges included in *candidateServingFreqRangeListNR*, the UE is experiencing IDC problems that it cannot solve by itself, and *affectedCarrierFreqList* or *affectedCarrierFreqCombList* or *affectedCarrierFreqRangeList* or *affectedCarrierFreqRangeCombList* is included, and *idc-TDM-AssistanceConfig* is set to *setup*: + - 3> include Time Domain Multiplexing (TDM) based assistance information as indicated by *idc-TDM-Assistance* that could be used to resolve the IDC problems; + +NOTE 1: When sending an *UEAssistanceInformation* message to inform the IDC problems, the UE includes all IDC assistance information (rather than providing e.g. the changed part(s) of the IDC assistance information). + +NOTE 2: Upon not anymore experiencing a particular IDC problem that the UE previously reported, the UE provides an IDC indication with the modified contents of the *UEAssistanceInformation* message (e.g. by not including the IDC assistance information in the *idc-Assistance*, *idc-FDM-Assistance* and *idc-TDM-Assistance* fields). + +- 1> if transmission of the *UEAssistanceInformation* message is initiated to provide *drx-Preference* of a cell group for power saving according to 5.7.4.2 or 5.3.5.3: + - 2> include *drx-Preference* in the *UEAssistanceInformation* message; + - 2> if the UE has a preference on DRX parameters for the cell group: + - 3> if the UE has a preference for the long DRX cycle: + - 4> include *preferredDRX-LongCycle* in the *DRX-Preference* IE and set it to the preferred value; + - 3> if the UE has a preference for the DRX inactivity timer: + - 4> include *preferredDRX-InactivityTimer* in the *DRX-Preference* IE and set it to the preferred value; + - 3> if the UE has a preference for the short DRX cycle: + - 4> include *preferredDRX-ShortCycle* in the *DRX-Preference* IE and set it to the preferred value; + - 3> if the UE has a preference for the short DRX timer: + - 4> include *preferredDRX-ShortCycleTimer* in the *DRX-Preference* IE and set it to the preferred value; + - 2> else (if the UE has no preference on DRX parameters for the cell group): + - 3> do not include *preferredDRX-LongCycle*, *preferredDRX-InactivityTimer*, *preferredDRX-ShortCycle* and *preferredDRX-ShortCycleTimer* in the *DRX-Preference* IE; +- 1> if transmission of the *UEAssistanceInformation* message is initiated to provide *maxBW-Preference* of a cell group for power saving according to 5.7.4.2 or 5.3.5.3: + - 2> include *maxBW-Preference* in the *UEAssistanceInformation* message; + - 2> if the UE has a preference on the maximum aggregated bandwidth for the cell group: + - 3> if the UE prefers to reduce the maximum aggregated bandwidth of FR1: + - 4> include *reducedMaxBW-FR1* in the *MaxBW-Preference* IE; + - 4> set *reducedBW-DL* to the maximum aggregated bandwidth the UE desires to have configured across all downlink carriers of FR1 in the cell group; + - 4> set *reducedBW-UL* to the maximum aggregated bandwidth the UE desires to have configured across all uplink carriers of FR1 in the cell group; + - 3> if the UE prefers to reduce the maximum aggregated bandwidth of FR2-1: + - 4> include *reducedMaxBW-FR2* in the *MaxBW-Preference* IE; + - 4> set *reducedBW-DL* to the maximum aggregated bandwidth the UE desires to have configured across all downlink carriers of FR2-1 in the cell group; + - 4> set *reducedBW-UL* to the maximum aggregated bandwidth the UE desires to have configured across all uplink carriers of FR2-1 in the cell group; + - 2> else (if the UE has no preference on the maximum aggregated bandwidth for the cell group): + - 3> do not include *reducedMaxBW-FR1* and *reducedMaxBW-FR2* in the *MaxBW-Preference* IE; +- 1> if transmission of the *UEAssistanceInformation* message is initiated to provide *maxBW-PreferenceFR2-2* of a cell group for power saving according to 5.7.4.2 or 5.3.5.3: + - 2> include *maxBW-PreferenceFR2-2* in the *UEAssistanceInformation* message; + +- 3> if the UE prefers to reduce the maximum aggregated bandwidth of FR2-2: + - 4> include *reducedMaxBW-FR2-2* in the *MaxBW-PreferenceFR2-2* IE; + - 4> set *reducedBW-FR2-2-DL* to the maximum aggregated bandwidth the UE desires to have configured across all downlink carriers of FR2-2 in the cell group; + - 4> set *reducedBW-FR2-2-UL* to the maximum aggregated bandwidth the UE desires to have configured across all uplink carriers of FR2-2 in the cell group; +- 2> else (if the UE has no preference on the maximum aggregated bandwidth for the cell group): + - 3> do not include *reducedMaxBW-FR2-2* in the *MaxBW-PreferenceFR2-2* IE; +- 1> if transmission of the *UEAssistanceInformation* message is initiated to provide *maxCC-Preference* of a cell group for power saving according to 5.7.4.2 or 5.3.5.3: + - 2> include *maxCC-Preference* in the *UEAssistanceInformation* message; + - 2> if the UE has a preference on the maximum number of secondary component carriers for the cell group: + - 3> include *reducedMaxCCs* in the *MaxCC-Preference* IE; + - 3> set *reducedCCsDL* to the number of maximum SCells the UE desires to have configured in downlink in the cell group; + - 3> set *reducedCCsUL* to the number of maximum SCells the UE desires to have configured in uplink in the cell group; + - 2> else (if the UE has no preference on the maximum number of secondary component carriers for the cell group): + - 3> do not include *reducedMaxCCs* in the *MaxCC-Preference* IE; + +NOTE 3: The UE can implicitly indicate a preference for NR SCG release by reporting the maximum aggregated bandwidth preference for power saving of the cell group, if configured, as zero for both FR1 and FR2, and by reporting the maximum number of secondary component carriers for power saving of the cell group, if configured, as zero for both uplink and downlink. + +- 1> if transmission of the *UEAssistanceInformation* message is initiated to provide *maxMIMO-LayerPreference* of a cell group for power saving according to 5.7.4.2 or 5.3.5.3: + - 2> include *maxMIMO-LayerPreference* in the *UEAssistanceInformation* message; + - 2> if the UE has a preference on the maximum number of MIMO layers for the cell group: + - 3> if the UE prefers to reduce the number of maximum MIMO layers of each serving cell operating on FR1: + - 4> include *reducedMaxMIMO-LayersFR1* in the *MaxMIMO-LayerPreference* IE; + - 4> set *reducedMIMO-LayersFR1-DL* to the preferred maximum number of downlink MIMO layers of each BWP of each FR1 serving cell that the UE operates on in the cell group; + - 4> set *reducedMIMO-LayersFR1-UL* to the preferred maximum number of uplink MIMO layers of each FR1 serving cell that the UE operates on in the cell group; + - 3> if the UE prefers to reduce the number of maximum MIMO layers of each serving cell operating on FR2-1: + - 4> include *reducedMaxMIMO-LayersFR2* in the *MaxMIMO-LayerPreference* IE; + - 4> set *reducedMIMO-LayersFR2-DL* to the preferred maximum number of downlink MIMO layers of each BWP of each FR2-1 serving cell that the UE operates on in the cell group; + - 4> set *reducedMIMO-LayersFR2-UL* to the preferred maximum number of uplink MIMO layers of each FR2-1 serving cell that the UE operates on in the cell group; + +- 2> else (if the UE has no preference on the maximum number of MIMO layers for the cell group): + - 3> do not include *reducedMaxMIMO-LayersFR1* and *reducedMaxMIMO-LayersFR2* in the *MaxMIMO-LayerPreference* IE; +- 1> if transmission of the *UEAssistanceInformation* message is initiated to provide *maxMIMO LayerPreferenceFR2* 2 of a cell group for power saving according to 5.7.4.2 or 5.3.5.3: + - 2> include *maxMIMO-LayerPreferenceFR2-2* in the *UEAssistanceInformation* message; + - 2> if the UE has a preference on the maximum number of MIMO layers for the cell group for FR2-2: + - 3> if the UE prefers to reduce the number of maximum MIMO layers of each serving cell operating on FR2 2: + - 4> include *reducedMaxMIMO-LayersFR2-2* in the *MaxMIMO-LayerPreferenceFR2 2* IE; + - 4> set *reducedMIMO-LayersFR2-2-DL* to the preferred maximum number of downlink MIMO layers of each BWP of each FR2-2 serving cell that the UE operates on in the cell group; + - 4> set *reducedMIMO-LayersFR2-2-UL* to the preferred maximum number of uplink MIMO layers of each FR2-2 serving cell that the UE operates on in the cell group; + - 2> else (if the UE has no preference on the maximum number of MIMO layers for the cell group): + - 3> do not include *reducedMaxMIMO-LayersFR2-2* in the *MaxMIMO-LayerPreferenceFR2-2* IE; +- 1> if transmission of the *UEAssistanceInformation* message is initiated to provide *minSchedulingOffsetPreference* of a cell group for power saving according to 5.7.4.2 or 5.3.5.3: + - 2> include *minSchedulingOffsetPreference* in the *UEAssistanceInformation* message; + - 2> if the UE has a preference on the minimum scheduling offset for cross-slot scheduling for the cell group: + - 3> if the UE has a preference for the value of $K_0$ (TS 38.214 [19], clause 5.1.2.1) for cross-slot scheduling with 15 kHz SCS: + - 4> include *preferredK0-SCS-15kHz* in the *MinSchedulingOffsetPreference* IE and set it to the desired value of $K_0$ ; + - 3> if the UE has a preference for the value of $K_0$ for cross-slot scheduling with 30 kHz SCS: + - 4> include *preferredK0-SCS-30kHz* in the *MinSchedulingOffsetPreference* IE and set it to the desired value of $K_0$ ; + - 3> if the UE has a preference for the value of $K_0$ for cross-slot scheduling with 60 kHz SCS: + - 4> include *preferredK0-SCS-60kHz* in the *MinSchedulingOffsetPreference* IE and set it to the desired value of $K_0$ ; + - 3> if the UE has a preference for the value of $K_0$ for cross-slot scheduling with 120 kHz SCS: + - 4> include *preferredK0-SCS-120kHz* in the *MinSchedulingOffsetPreference* IE and set it to the desired value of $K_0$ ; + - 3> if the UE has a preference for the value of $K_2$ (TS 38.214 [19], clause 6.1.2.1) for cross-slot scheduling with 15 kHz SCS: + - 4> include *preferredK2-SCS-15kHz* in the *MinSchedulingOffsetPreference* IE and set it to the desired value of $K_2$ ; + - 3> if the UE has a preference for the value of $K_2$ for cross-slot scheduling with 30 kHz SCS: + - 4> include *preferredK2-SCS-30kHz* in the *MinSchedulingOffsetPreference* IE and set it to the desired value of $K_2$ ; + - 3> if the UE has a preference for the value of $K_2$ for cross-slot scheduling with 60 kHz SCS: + +- 4> include *preferredK2-SCS-60kHz* in the *MinSchedulingOffsetPreference* IE and set it to the desired value of $K_2$ ; + - 3> if the UE has a preference for the value of $K_2$ for cross-slot scheduling with 120 kHz SCS: + - 4> include *preferredK2-SCS-120kHz* in the *MinSchedulingOffsetPreference* IE and set it to the desired value of $K_2$ ; + - 2> else (if the UE has no preference on the minimum scheduling offset for cross-slot scheduling for the cell group): + - 3> do not include *preferredK0* and *preferredK2* in the *MinSchedulingOffsetPreference* IE; +- 1> if transmission of the *UEAssistanceInformation* message is initiated to provide *minSchedulingOffsetPreferenceExt* of a cell group for power saving according to 5.7.4.2 or 5.3.5.3: + - 2> include *minSchedulingOffsetPreferenceExt* in the *UEAssistanceInformation* message; + - 2> if the UE has a preference on the minimum scheduling offset for cross-slot scheduling for the cell group for FR2-2: + - 3> include *minSchedulingOffsetPreferenceExt* in the *UEAssistanceInformation* message; + - 4> if the UE has a preference for the value of $K_0$ (TS 38.214 [19], clause 5.1.2.1) for cross-slot scheduling with 480 kHz SCS: + - 5> include *preferredK0-SCS-480kHz* in the *minSchedulingOffsetPreferenceExt* IE and set it to the desired value of $K_0$ ; + - 4> if the UE has a preference for the value of $K_0$ for cross-slot scheduling with 960 kHz SCS: + - 5> include *preferredK0-SCS-960kHz* in the *minSchedulingOffsetPreferenceExt* IE and set it to the desired value of $K_0$ ; + - 4> if the UE has a preference for the value of $K_2$ for cross-slot scheduling with 480 kHz SCS: + - 5> include *preferredK2-SCS-480kHz* in the *minSchedulingOffsetPreferenceExt* IE and set it to the desired value of $K_2$ ; + - 4> if the UE has a preference for the value of $K_2$ for cross-slot scheduling with 960 kHz SCS: + - 5> include *preferredK2-SCS-960kHz* in the *minSchedulingOffsetPreferenceExt* IE and set it to the desired value of $K_2$ ; + - 3> else (if the UE has no preference on the minimum scheduling offset for cross-slot scheduling for the cell group): + - 4> do not include *preferredK0* and *preferredK2* in the *minSchedulingOffsetPreferenceExt* IE; +- 1> if transmission of the *UEAssistanceInformation* message is initiated to provide a release preference according to 5.7.4.2 or 5.3.5.3: + - 2> include *releasePreference* in the *UEAssistanceInformation* message; + - 2> set *preferredRRC-State* to the desired RRC state on transmission of the *UEAssistanceInformation* message; +- 1> if transmission of the *UEAssistanceInformation* message is initiated to provide an indication of preference in being provisioned with reference time information according to 5.7.4.2 or 5.3.5.3: + - 2> if the UE has a preference in being provisioned with reference time information: + - 3> set *referenceTimeInfoPreference* to *true*; + - 2> else: + - 3> set *referenceTimeInfoPreference* to *false*. + +- 1> if transmission of the *UEAssistanceInformation* message is initiated to provide preference on FR2 UL gap according to 5.7.4.2 or 5.3.5.3: + - 2> if the UE has a preference for FR2 UL gap configuration: + - 3> set *ul-GapFR2-PatternPreference* to the preferred FR2 UL gap pattern; + - 2> else (if the UE has no preference for the FR2 UL gap configuration): + - 3> do not include *ul-GapFR2-PatternPreference* in the *UL-GapFR2-Preference* IE. +- 1> if transmission of the *UEAssistanceInformation* message is initiated to provide MUSIM assistance information according to 5.7.4.2 or 5.3.5.3: + - 2> if the UE has a preference for MUSIM periodic gap(s): + - 3> include *musim-GapPreferenceList* with an entry for each periodic gap the UE prefers to be configured; + - 4> set *musim-GapLength* and *musim-GapRepetitionAndOffset* in the *musim-GapInfo* IE to the values of the length and the repetition/offset of the gap(s), respectively, the UE prefers to be configured with; + - 2> if the UE has a preference for MUSIM aperiodic gap: + - 3> include the field *musim-GapPreferenceList*, with one entry for the aperiodic gap the UE prefers to be configured; + - 4> include *musim-GapLength* in the *musim-GapInfo* IE and set it to the values of the length of the gap the UE prefers to be configured with; + - 4> optionally include *musim-Starting-SFN-AndSubframe* in the *musim-GapInfo* IE and set it to the starting SFN/subframe of the gap the UE prefers to be configured with; + - 2> if the UE has no longer preference for the periodic/aperiodic gaps: + - 3> do not include *musim-GapPreferenceList* in the *musim-Assistance* IE; + - 2> if UE has a preference to leave RRC\_CONNECTED state: + - 3> set *musim-PreferredRRC-State* to the preferred RRC state. + - 2> if UE has a preference for MUSIM gap priority: + - 3> include the *musim-GapPriorityPreferenceList* the UE prefers to be configured; + - 3> if the UE has preference to keep all collided MUSIM gaps for periodic MUSIM gap(s): + - 4> include the *musim-GapKeep*; + - 2> if UE has a preference for temporary capability restriction: + - 3> if UE has a preference for serving cell(s) and/or SCG to be released: + - 4> include the *musim-Cell-SCG-ToRelease*; + - 5> set *musim-CellToRelease* to include the serving cell(s) the UE prefers to be released; + - 5> set *scg-ReleasePreference* to *scgReleasePreferred* if the UE prefers the SCG to be released; + - 3> if UE has a preference to indicate the serving cells: + - 4> include the *musim-CellToAffectList* the UE prefers to be configured; + - 5> include the *musim-ServCellIndex* and the *musim-MIMO-Layers-DL/ musim-MIMO-Layers-UL/ musim-SupportedBandwidth-DL/ musim-SupportedBandwidth-UL* for the corresponding serving cell; + - 3> if UE has a preference to indicate the maximum number of CCs: + +- 4> include the *musim-capabilityRestricted* for the corresponding *musim-MaxCC* the UE prefers to be configured; + - 5> include the the *musim-MaxCC-DL/ musim-MaxCC-UL* for the corresponding maximum number of CCs; + - 3> if UE has a preference to indicate band(s) and/or combination(s) of bands with capabilities restricted which comprise of the band(s) that is/are indicated in *musim-CandidateBandList*: + - 4> include the *musim-AffectedBandCombList* the UE prefer to be configured with capabilities restricted; + - 5> include the *bandEntryIndex* for each band for each band or each band of the combination(s) for which capabilities are restricted; + - 5> include the *musim-CapabilityRestricted* for the corresponding band(s) or bands of the combination(s); + - 3> if UE has a preference to indicate band(s) and/or combination(s) of bands to be avoided which comprise of band(s) that is indicated in *musim-CandidateBandList*: + - 4> include the *musim-AvoidedBandsList* the UE prefers not to be configured; + - 5> include the *bandEntryIndex* for each band or each band of the combination(s) to be avoided; + - 3> if UE has a preference for measurement gap requirement: + - 4> include the *musim-NeedForGapsInfoNR* to provide the measurement gap requirement information from the *requestedTargetBandFilterNR-r16* of *NeedForGapsConfigNR* configuration in RRCResume message or *RRCReconfiguration* message of NR target bands the UE prefer to be configured; +- 2> if the UE has no longer preference for temporary capability restriction: +- 3> do not include the corresponding temporary capability restriction preference in the *musim-CapRestriction* in the *musim-Assistance IE*; +- 1> if transmission of the *UEAssistanceInformation* message is initiated to provide the relaxation state of RLM measurements of a cell group according to 5.7.4.2: +- 2> if the UE performs RLM measurement relaxation on the cell group according to TS 38.133 [14]: + - 3> set the *rlm-MeasRelaxationState* to *true*; + - 2> else: + - 3> set the *rlm-MeasRelaxationState* to *false*; +- 1> if transmission of the *UEAssistanceInformation* message is initiated to provide the relaxation state of BFD measurements of a cell group: +- 2> for each serving cell of the cell group: + - 3> if the UE performs BFD measurement relaxation on this serving cell according to TS 38.133 [14]: + - 4> set the n-th bit of *bfd-MeasRelaxationState* to '1', where n is equal to the *servCellIndex* value + 1 of the serving cell; + - 3> else: + - 4> set the n-th bit of *bfd-MeasRelaxationState* to '0', where n is equal to the *servCellIndex* value + 1 of the serving cell. +- 1> if transmission of the *UEAssistanceInformation* message is initiated to indicate availability of data mapped to radio bearers not configured for SDT according to 5.7.4.2: +- 2> include the *nonSDT-DataIndication* in the *UEAssistanceInformation* message; + +- 2> include and set the *resumeCause* according to the information received from the upper layers, if provided. +- 1> if transmission of the *UEAssistanceInformation* message is initiated to provide an indication of preference for SCG deactivation according to 5.7.4.2: + - 2> include *scg-DeactivationPreference* in the *UEAssistanceInformation* message; + - 2> set the *scg-DeactivationPreference* to *scgDeactivationPreferred* if the UE prefers the SCG to be deactivated, otherwise set it to *noPreference*; +- 1> if transmission of the *UEAssistanceInformation* message is initiated to provide an indication that the UE has uplink data related to a deactivated SCG according to 5.7.4.2: + - 2> include *uplinkData* in the *UEAssistanceInformation* message. +- 1> if transmission of the *UEAssistanceInformation* message is initiated to provide an indication about whether the criterion for RRM relaxation for connected mode is fulfilled or not fulfilled: + - 2> if the criterion for RRM measurement relaxation for connected mode is fulfilled: + - 3> set the *rrm-MeasRelaxationFulfilment* to *true*; + - 2> else: + - 3> set the *rrm-MeasRelaxationFulfilment* to *false*. +- 1> if transmission of the *UEAssistanceInformation* message is initiated to provide the service link propagation delay difference between serving cell and neighbour cell(s) according to 5.7.4.2; + - 2> include the *propagationDelayDifference* for each neighbour cell in the *neighCellInfoList*; +- 1> if transmission of the *UEAssistanceInformation* message is initiated to provide preference on multi-Rx operation for FR2 according to 5.7.4.2: + - 2> if the UE has a preference for not operating on multi-Rx (i.e. not supporting simultaneous reception with different QCL-typeD) for FR2: + - 3> set *multiRx-PreferenceFR2* to the preferred multi-Rx operation for FR2; + - 2> else (if the UE has the preference for operating on multi-Rx for FR2): + - 3> not include *multiRx-PreferenceFR2*. +- 1> if transmission of the *UEAssistanceInformation* message is initiated to indicate the availability of flight path information according to 5.7.4.2 or 5.3.5.3; + - 2> include the *flightPathInfoAvailable*; +- 1> if transmission of the *UEAssistanceInformation* message is initiated to provide UL traffic information according to 5.7.4.2: + - 2> for each PDU session for which the UE intends to provide UL traffic information in this *UEAssistanceInformation* message: + - 3> set *pdu-SessionID* to the value of the concerned PDU session ID; + - 3> for each QoS flow of this PDU session for which timer T346x is not running and for which the UE intends to provide UL traffic information in this *UEAssistanceInformation* message: + - 4> start timer T346x associated to this QoS flow with the timer value set to the value of *ul-TrafficInfoProhibitTimer*; + - 4> set *qfi* to the value of the concerned QFI; + - 4> if the jitter range measurement is available; and + +- 4> if the UE did not provide jitter range since it was configured to provide UL traffic information, or if the measured jitter range has changed since the last transmission of the *UEAssistanceInformation* message containing *jitterRange*: + - 5> set *jitterRange* to the latest measured value of the jitter range; + - 4> if the burst arrival time measurement is available; and + - 4> if the UE did not provide burst arrival time since it was configured to provide UL traffic information, or if the measured burst arrival time has changed since the last transmission of the *UEAssistanceInformation* message containing *burstArrivalTime*: + - 5> set *burstArrivalTime* to the latest measured value of the burst arrival time; + - 4> if the traffic periodicity measurement is available; and + - 4> if the UE did not provide traffic periodicity since it was configured to provide UL traffic information, or if the measured traffic periodicity has changed since the last transmission of the *UEAssistanceInformation* message containing *trafficPeriodicity*: + - 5> set *trafficPeriodicity* to the latest measured value of the traffic periodicity; + - 4> if the UE did not provide *pduSetIdentification* since it was configured to provide UL traffic information, or if the information previously provided in *pduSetIdentification* has changed since the last transmission of the *UEAssistanceInformation* message containing *pduSetIdentification*: + - 5> if the UE is able to identify PDU Set related information for the QoS flow: + - 6> set *pduSetIdentification* to *true*; + - 5> else: + - 6> set *pduSetIdentification* to *false*. +- 1> if transmission of the *UEAssistanceInformation* message is initiated to report relay UE information with non-3GPP connection(s) according to 5.7.4.2: +- 2> include *n3c-relayUE-InfoList* in the *UEAssistanceInformation* message; + +The UE shall set the contents of the *UEAssistanceInformation* message for configured grant assistance information for NR sidelink communication or NR sidelink positioning: + +- 1> if configured to provide configured grant assistance information for NR sidelink communication or NR sidelink positioning: + - 2> include the *sl-UE-AssistanceInformationNR*; + +NOTE 4: It is up to UE implementation when and how to trigger configured grant assistance information for NR sidelink communication. + +The UE shall: + +- 1> if the procedure was triggered to provide configured grant assistance information for NR sidelink communication by an NR *RRCReconfiguration* message that was embedded within an E-UTRA *RRCConnectionReconfiguration*: + - 2> submit the *UEAssistanceInformation* to lower layers via SRB1, embedded in E-UTRA RRC message *ULInformationTransferIRAT* as specified in TS 36.331 [10], clause 5.6.28; +- 1> else if the procedure was triggered to provide UE preference for SCG deactivation or to indicate that the UE with a deactivate SCG has uplink data to send on a DRB for which there is no MCG RLC bearer: + - 2> submit the *UEAssistanceInformation* via SRB1 to lower layers for transmission; +- 1> else if the UE is in (NG)EN-DC: + - 2> if SRB3 is configured and the SCG is not deactivated: + +Error: Reference source not found 14 Error: Reference source not found + +- 3> submit the *UEAssistanceInformation* message via SRB3 to lower layers for transmission; +- 2> else: + - 3> submit the *UEAssistanceInformation* message via the E-UTRA MCG embedded in E-UTRA RRC message *ULInformationTransferMRDC* as specified in TS 36.331 [10]. +- 1> else if the UE is in NR-DC: + - 2> if the UE assistance configuration that triggered this UE assistance information is associated with the SCG: + - 3> if SRB3 is configured and the SCG is not deactivated: + - 4> submit the *UEAssistanceInformation* message via SRB3 to lower layers for transmission; + - 3> else: + - 4> submit the *UEAssistanceInformation* message via the NR MCG embedded in NR RRC message *ULInformationTransferMRDC* as specified in 5.7.2a.3; + - 2> else: + - 3> submit the *UEAssistanceInformation* message via SRB1 to lower layers for transmission; +- 1> else: + - 2> submit the *UEAssistanceInformation* message to lower layers for transmission. +- 1> if the procedure was triggered to provide configured grant assistance information for NR sidelink positioning: + - 2> submit the *UEAssistanceInformation* to lower layers via SRB1. + +#### 5.7.4.3a Setting the contents of *OverheatingAssistance* IE + +The UE shall set the contents of *OverheatingAssistance* IE if initiated to provide overheating assistance indication for SCG in (NG)EN-DC according to clause 5.6.10.3 as specified in TS 36.331 [10]: + +- 1> if the UE prefers to temporarily reduce the number of maximum secondary component carriers for SCG: + - 2> include *reducedMaxCCs* in the *OverheatingAssistance* IE; + - 2> set *reducedCCsDL* to the number of maximum SCells of the SCG the UE prefers to be temporarily configured in downlink; + - 2> set *reducedCCsUL* to the number of maximum SCells of the SCG the UE prefers to be temporarily configured in uplink; +- 1> if the UE prefers to temporarily reduce maximum aggregated bandwidth of FR1 for SCG: + - 2> include *reducedMaxBW-FR1* in the *OverheatingAssistance* IE; + - 2> set *reducedBW-FR1-DL* to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all downlink carriers of FR1 of the SCG; + - 2> set *reducedBW-FR1-UL* to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all uplink carriers of FR1 of the SCG; +- 1> if the UE prefers to temporarily reduce maximum aggregated bandwidth of FR2-1 for SCG: + - 2> include *reducedMaxBW-FR2* in the *OverheatingAssistance* IE; + - 2> set *reducedBW-FR2-DL* to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all downlink carriers of FR2-1 of the SCG; + - 2> set *reducedBW-FR2-UL* to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all uplink carriers of FR2-1 of the SCG; +- 1> if the UE prefers to temporarily reduce maximum aggregated bandwidth of FR2-2 for SCG: + +- 2> include *reducedMaxBW-FR2-2* in the *OverheatingAssistance* IE; + - 2> set *reducedBW-FR2-2-DL* to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all downlink carriers of FR2-2 of the SCG; + - 2> set *reducedBW-FR2-2-UL* to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all uplink carriers of FR2-2 of the SCG; +- 1> if the UE prefers to temporarily reduce the number of maximum MIMO layers of each serving cell operating on FR1 for SCG: + - 2> include *reducedMaxMIMO-LayersFR1* in the *OverheatingAssistance* IE; + - 2> set *reducedMIMO-LayersFR1-DL* to the number of maximum MIMO layers of each serving cell operating on FR1 of the SCG the UE prefers to be temporarily configured in downlink; + - 2> set *reducedMIMO-LayersFR1-UL* to the number of maximum MIMO layers of each serving cell operating on FR1 of the SCG the UE prefers to be temporarily configured in uplink; + - 1> if the UE prefers to temporarily reduce the number of maximum MIMO layers of each serving cell operating on FR2-1 for SCG: + - 2> include *reducedMaxMIMO-LayersFR2* in the *OverheatingAssistance* IE; + - 2> set *reducedMIMO-LayersFR2-DL* to the number of maximum MIMO layers of each serving cell operating on FR2-1 of the SCG the UE prefers to be temporarily configured in downlink; + - 2> set *reducedMIMO-LayersFR2-UL* to the number of maximum MIMO layers of each serving cell operating on FR2-1 of the SCG the UE prefers to be temporarily configured in uplink; + - 1> if the UE prefers to temporarily reduce the number of maximum MIMO layers of each serving cell operating on FR2-2 for SCG: + - 2> include *reducedMaxMIMO-LayersFR2-2* in the *OverheatingAssistance* IE; + - 2> set *reducedMIMO-LayersFR2-2-DL* to the number of maximum MIMO layers of each serving cell operating on FR2-2 of the SCG the UE prefers to be temporarily configured in downlink; + - 2> set *reducedMIMO-LayersFR2-2-UL* to the number of maximum MIMO layers of each serving cell operating on FR2-2 of the SCG the UE prefers to be temporarily configured in uplink; + +#### 5.7.4.4 Relaxed measurement criterion for a stationary (e)RedCap UE + +The relaxed measurement criterion for a stationary UE is met when: + +- $(\text{SS-RSRP}_{\text{RefStationaryConnected}} - \text{SS-RSRP}) < S_{\text{SearchDeltaP-StationaryConnected}}$ , + +Where: + +- SS-RSRP = current L3 RSRP measurement of the PCell based on SSB (dB). +- $\text{SS-RSRP}_{\text{RefStationaryConnected}}$ = reference SS-RSRP value of the PCell (dB), set as follows: + - at the end of RRC reconfiguration procedure as specified in 5.3.5.3, when *rrm-MeasRelaxationReportingConfig* is included in the *RRCReconfiguration* message; or + - after MAC successfully completes a Random Access procedure after applying a *reconfigurationWithSync* in *spCellConfig* while stationary criterion is configured; or + - if $(\text{SS-RSRP} - \text{SS-RSRP}_{\text{RefStationaryConnected}}) > 0$ ; or + - if the relaxed measurement criterion has not been met for $T_{\text{SearchDeltaP-StationaryConnected}}$ : + - UE shall set the value of $\text{SS-RSRP}_{\text{RefStationaryConnected}}$ to the current SS-RSRP value of the serving cell. + +### 5.7.4a Void + +### 5.7.5 Failure information + +#### 5.7.5.1 General + +![Sequence diagram showing the transmission of FailureInformation from UE to Network.](16152cf1d84aea10848758f51a91ff6a_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Network + Note left of UE: + UE->>Network: FailureInformation + Note right of Network: + +``` + +The diagram illustrates a sequence of interactions between a User Equipment (UE) and a Network. The UE is shown on the left and the Network on the right. A horizontal arrow labeled *FailureInformation* points from the UE to the Network, indicating the transmission of this message. + +Sequence diagram showing the transmission of FailureInformation from UE to Network. + +Figure 5.7.5.1-1: Failure information + +The purpose of this procedure is to inform the network about a failure detected by the UE. + +#### 5.7.5.2 Initiation + +A UE initiates the procedure when there is a need to inform the network about a failure detected by the UE. In particular, the UE initiates the procedure when the following condition is met: + +- 1) upon detecting failure for an RLC bearer, in accordance with 5.3.10.3; +- 1) upon detecting DAPS handover failure, in accordance with 5.3.5.8.3; + +Upon initiating the procedure, the UE shall: + +- 1) initiate transmission of the *FailureInformation* message as specified in 5.7.5.3; + +#### 5.7.5.3 Actions related to transmission of *FailureInformation* message + +The UE shall: + +- 1) if initiated to provide RLC failure information, set *FailureInfoRLC-Bearer* as follows: + - 2) set *logicalChannelIdentity* to the logical channel identity of the failing RLC bearer; + - 2) set *cellGroupId* to the cell group identity of the failing RLC bearer; + - 2) set the *failureType* as *rlc-failure*; +- 1) if initiated to provide DAPS failure information, set *FailureInfoDAPS* as follows: + - 2) set the *failureType* as *daps-failure*; +- 1) if used to inform the network about a failure for an MCG RLC bearer or DAPS failure information: + - 2) submit the *FailureInformation* message to lower layers for transmission via SRB1; +- 1) else if used to inform the network about a failure for an SCG RLC bearer: + - 2) if SRB3 is configured; + - 3) submit the *FailureInformation* message to lower layers for transmission via SRB3; + - 2) else; + - 3) if the UE is in (NG)EN-DC: + - 4) submit the *FailureInformation* message via E-UTRA SRB1 embedded in E-UTRA RRC message *ULInformationTransferMRDC* as specified in TS 36.331 [10]. + - 3) else if the UE is in NR-DC: + +4> submit the *FailureInformation* message via SRB1 embedded in NR RRC message *ULInformationTransferMRDC* as specified in clause 5.7.2a.3. + +### 5.7.6 DL message segment transfer + +#### 5.7.6.1 General + +![Sequence diagram for DL message segment transfer. A 'UE' box is on the left and a 'Network' box is on the right. A horizontal arrow labeled 'DLDedicatedMessageSegment' points from the Network to the UE.](df82d77a0d2637cbf2da9ea920a554fa_img.jpg) + +``` + +sequenceDiagram + participant Network + participant UE + Note left of Network: DL message segment transfer + Network->>UE: DLDedicatedMessageSegment + +``` + +Sequence diagram for DL message segment transfer. A 'UE' box is on the left and a 'Network' box is on the right. A horizontal arrow labeled 'DLDedicatedMessageSegment' points from the Network to the UE. + +Figure 5.7.6.1-1: DL message segment transfer + +The purpose of this procedure is to transfer segments of DL DCCH messages from the network to the UE. + +NOTE: The segmentation of DL DCCH message is only applicable to *RRCReconfiguration* and *RRCResume* messages in this release. + +#### 5.7.6.2 Initiation + +The network initiates the DL Dedicated Message Segment transfer procedure whenever the encoded RRC message PDU exceeds the maximum PDCP SDU size. The network initiates the DL Dedicated Message Segment transfer procedure by sending the *DLDedicatedMessageSegment* message. + +#### 5.7.6.3 Reception of *DLDedicatedMessageSegment* by the UE + +Upon receiving *DLDedicatedMessageSegment* message, the UE shall: + +- 1> store the segment included in *rrc-MessageSegmentContainer*; +- 1> if all segments of the message have been received: + - 2> assemble the message from the received segments and process the message according to 5.3.5.3 for the *RRCReconfiguration* message or 5.3.13.4 for the *RRCResume* message; +- 2> discard all segments. + +### 5.7.7 UL message segment transfer + +#### 5.7.7.1 General + +![Sequence diagram for UL message segment transfer. A 'UE' box is on the left and a 'Network' box is on the right. A horizontal arrow labeled 'ULDedicatedMessageSegment' points from the UE to the Network.](16da2d7b436c26f2efc4b51b2aae0fed_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Network + Note left of UE: UL message segment transfer + UE->>Network: ULDedicatedMessageSegment + +``` + +Sequence diagram for UL message segment transfer. A 'UE' box is on the left and a 'Network' box is on the right. A horizontal arrow labeled 'ULDedicatedMessageSegment' points from the UE to the Network. + +Figure 5.7.7.1-1: UL message segment transfer + +The purpose of this procedure is to transfer segments of UL DCCH messages from UE to a NG-RAN in RRC\_CONNECTED. + +NOTE: The segmentation of UL DCCH message is only applicable to *UECapabilityInformation* and *MeasurementReportAppLayer* in this release. + +#### 5.7.7.2 Initiation + +A UE capable of UL RRC message segmentation in RRC\_CONNECTED will initiate the procedure when the following conditions are met: + +**Error: Reference source not found 18 Error: Reference source not found** + +- 1> if the RRC message segmentation is enabled based on the field *rrc-SegAllowed*, *rrc-SegAllowedSRB4* or *rrc-SegAllowedSRB5* received, and +- 1> if the encoded RRC message is larger than the maximum supported size of a PDCP SDU specified in TS 38.323 [5]; + +Upon initiating the procedure, the UE shall: + +- 1> initiate transmission of the *ULDedicatedMessageSegment* message as specified in 5.7.7.3; + +#### 5.7.7.3 Actions related to transmission of *ULDedicatedMessageSegment* message + +The UE shall segment the encoded RRC PDU based on the maximum supported size of a PDCP SDU specified in TS 38.323 [5]. UE shall minimize the number of segments and set the contents of the *ULDedicatedMessageSegment* messages as follows: + +- 1> For each new UL DCCH message, set the *segmentNumber* to 0 for the first message segment and increment the *segmentNumber* for each subsequent RRC message segment; +- 1> set *rrc-MessageSegmentContainer* to include the segment of the UL DCCH message corresponding to the *segmentNumber*; +- 1> if the segment included in the *rrc-MessageSegmentContainer* is the last segment of the UL DCCH message: + - 2> set the *rrc-MessageSegmentType* to *lastSegment*; +- 1> else: + - 2> set the *rrc-MessageSegmentType* to *notLastSegment*; +- 1> submit all the *ULDedicatedMessageSegment* messages generated for the segmented RRC message to lower layers for transmission in ascending order based on the *segmentNumber*, upon which the procedure ends. + +### 5.7.8 Idle/inactive Measurements + +#### 5.7.8.1 General + +This procedure specifies the measurements to be performed and stored by a UE in RRC\_IDLE and RRC\_INACTIVE when it has an idle/inactive measurement configuration. + +#### 5.7.8.1a Measurement configuration + +The purpose of this procedure is to update the idle/inactive measurement configuration. + +The UE initiates this procedure while T331 is running and SDT procedure is not ongoing and one of the following conditions is met: + +- 1> upon selecting a cell when entering RRC\_IDLE or RRC\_INACTIVE from RRC\_CONNECTED or RRC\_INACTIVE; or +- 1> upon update of system information (*SIB4*, or *SIB11*), e.g. due to intra-RAT cell (re)selection; + +While in RRC\_IDLE or RRC\_INACTIVE, and T331 is running, the UE shall: + +- 1> if *VarMeasIdleConfig* includes neither a *measIdleCarrierListEUTRA* nor a *measIdleCarrierListNR* received from the *RRRelease* message: + - 2> if the UE supports *idleInactiveEUTRA-MeasReport*: + - 3> if the SIB11 includes the *measIdleConfigSIB* and contains *measIdleCarrierListEUTRA*: + - 4> store or replace the *measIdleCarrierListEUTRA* of *measIdleConfigSIB* of SIB11 within *VarMeasIdleConfig*; + - 3> else: + +- 4> remove the *measIdleCarrierListEUTRA* in *VarMeasIdleConfig*, if stored; +- 2> if the UE supports *idleInactiveNR-MeasReport*: + - 3> if *SIB11* includes the *measIdleConfigSIB* and contains *measIdleCarrierListNR*: + - 4> store or replace the *measIdleCarrierListNR* of *measIdleConfigSIB* of *SIB11* within *VarMeasIdleConfig*; + - 3> else: + - 4> remove the *measIdleCarrierListNR* in *VarMeasIdleConfig*, if stored; +- 1> for each entry in the *measIdleCarrierListNR* within *VarMeasIdleConfig* that does not contain an *ssb-MeasConfig* received from the *RRRelease* message: + - 2> if there is an entry in *measIdleCarrierListNR* in *measIdleConfigSIB* of *SIB11* that has the same carrier frequency and subcarrier spacing as the entry in the *measIdleCarrierListNR* within *VarMeasIdleConfig* and that contains *ssb-MeasConfig*: + - 3> delete the *ssb-MeasConfig* of the corresponding entry in the *measIdleCarrierListNR* within *VarMeasIdleConfig*; + - 3> store the SSB measurement configuration from *SIB11* into *nrofSS-BlocksToAverage*, *absThreshSS-BlocksConsolidation*, *smtc*, *ssb-ToMeasure*, *deriveSSB-IndexFromCell*, and *ss-RSSI-Measurement* within *ssb-MeasConfig* of the corresponding entry in the *measIdleCarrierListNR* within *VarMeasIdleConfig*; + - 2> else if there is an entry in *interFreqCarrierFreqList* of *SIB4* with the same carrier frequency and subcarrier spacing as the entry in *measIdleCarrierListNR* within *VarMeasIdleConfig*: + - 3> delete the *ssb-MeasConfig* of the corresponding entry in the *measIdleCarrierListNR* within *VarMeasIdleConfig*; + - 3> store the SSB measurement configuration from *SIB4* into *nrofSS-BlocksToAverage*, *absThreshSS-BlocksConsolidation*, *smtc*, *ssb-ToMeasure*, *deriveSSB-IndexFromCell*, and *ss-RSSI-Measurement* within *ssb-MeasConfig* of the corresponding entry in the *measIdleCarrierListNR* within *VarMeasIdleConfig*; + - 2> else: + - 3> remove the *ssb-MeasConfig* of the corresponding entry in the *measIdleCarrierListNR* within *VarMeasIdleConfig*, if stored; +- 1> perform measurements according to 5.7.8.2a. + +#### 5.7.8.2 Void + +#### 5.7.8.2a Performing measurements + +When performing measurements on NR carriers according to this clause, the UE shall derive the cell quality as specified in 5.5.3.3 and consider the beam quality to be the value of the measurement results of the concerned beam, where each result is averaged as described in TS 38.215 [9]. + +While in *RR\_IDLE* or *RR\_INACTIVE*, and *T331* is running and *SDT* procedure is not ongoing, the UE shall: + +- 1> perform the measurements in accordance with the following: + - 2> if the *VarMeasIdleConfig* includes the *measIdleCarrierListEUTRA* and the *SIB1* contains *idleModeMeasurementsEUTRA*: + - 3> for each entry in *measIdleCarrierListEUTRA* within *VarMeasIdleConfig*: + - 4> if UE supports NE-DC between the serving carrier and the carrier frequency indicated by *carrierFreqEUTRA* within the corresponding entry: + - 5> perform measurements in the carrier frequency and bandwidth indicated by *carrierFreqEUTRA* and *allowedMeasBandwidth* within the corresponding entry; + +- 5> if the *reportQuantitiesEUTRA* is set to *rsrq*: + - 6> consider RSRQ as the sorting quantity; +- 5> else: + - 6> consider RSRP as the sorting quantity; +- 5> if the *measCellListEUTRA* is included: + - 6> consider cells identified by each entry within the *measCellListEUTRA* to be applicable for idle/inactive mode measurement reporting; +- 5> else: + - 6> consider up to *maxCellMeasIdle* strongest identified cells, according to the sorting quantity, to be applicable for idle/inactive measurement reporting; +- 5> for all cells applicable for idle/inactive measurement reporting, derive measurement results for the measurement quantities indicated by *reportQuantitiesEUTRA*; +- 5> store the derived measurement results as indicated by *reportQuantitiesEUTRA* within the *measReportIdleEUTRA* in *VarMeasIdleReport* in decreasing order of the sorting quantity, i.e. the best cell is included first, as follows: + - 6> if *qualityThresholdEUTRA* is configured: + - 7> include the measurement results from the cells applicable for idle/inactive measurement reporting whose RSRP/RSRQ measurement results are above the value(s) provided in *qualityThresholdEUTRA*; + - 6> else: + - 7> include the measurement results from all cells applicable for idle/inactive measurement reporting; +- 2> if the *VarMeasIdleConfig* includes the *measIdleCarrierListNR* and the SIB1 contains *idleModeMeasurementsNR*: + - 3> for each entry in *measIdleCarrierListNR* within *VarMeasIdleConfig* that contains *ssb-MeasConfig*: + - 4> if UE supports carrier aggregation or NR-DC between serving carrier and the carrier frequency and subcarrier spacing indicated by *carrierFreq* and *ssbSubCarrierSpacing* within the corresponding entry: + - 5> perform measurements in the carrier frequency and subcarrier spacing indicated by *carrierFreq* and *ssbSubCarrierSpacing* within the corresponding entry; + - 5> if the *reportQuantities* is set to *rsrq*: + - 6> consider RSRQ as the cell sorting quantity; + - 5> else: + - 6> consider RSRP as the cell sorting quantity; + - 5> if the *measCellListNR* is included: + - 6> consider cells identified by each entry within the *measCellListNR* to be applicable for idle/inactive measurement reporting; + - 5> else: + - 6> consider up to *maxCellMeasIdle* strongest identified cells, according to the sorting quantity, to be applicable for idle/inactive measurement reporting; + +- 5> for all cells applicable for idle/inactive measurement reporting, derive cell measurement results for the measurement quantities indicated by *reportQuantities*; +- 5> store the derived cell measurement results as indicated by *reportQuantities* for cells applicable for idle/inactive measurement reporting within *measResultsPerCarrierListIdleNR* in the *measReportIdleNR* in *VarMeasIdleReport* in decreasing order of the cell sorting quantity, i.e. the best cell is included first, as follows: + - 6> if *qualityThreshold* is configured: + - 7> include the measurement results from the cells applicable for idle/inactive measurement reporting whose RSRP/RSRQ measurement results are above the value(s) provided in *qualityThreshold*; + - 6> else: + - 7> include the measurement results from all cells applicable for idle/inactive measurement reporting; +- 5> if *beamMeasConfigIdle* is included in the associated entry in *measIdleCarrierListNR* and if UE supports *idleInactiveNR-MeasBeamReport* for the FR of the carrier frequency indicated by *carrierFreq* within the associated entry, for each cell in the measurement results: + - 6> derive beam measurements based on SS/PBCH block for each measurement quantity indicated in *reportQuantityRS-Indexes*, as described in TS 38.215 [9]; + - 6> if the *reportQuantityRS-Indexes* is set to *rsrq*: + - 7> consider RSRQ as the beam sorting quantity; + - 6> else: + - 7> consider RSRP as the beam sorting quantity; + - 6> set *resultsSSB-Indexes* to include up to *maxNrofRS-IndexesToReport* SS/PBCH block indexes in order of decreasing beam sorting quantity as follows: + - 7> include the index associated to the best beam for the sorting quantity and if *absThreshSS-BlocksConsolidation* is included, the remaining beams whose sorting quantity is above *absThreshSS-BlocksConsolidation*; + - 6> if the *includeBeamMeasurements* is set to *true*: + - 7> include the beam measurement results as indicated by *reportQuantityRS-Indexes*; +- 2> if, as a result of the procedure in this clause, the UE performs measurements in one or more carrier frequency indicated by *measIdleCarrierListNR* or *measIdleCarrierListEUTRA*: + - 3> store the cell measurement results for RSRP and RSRQ for the serving cell within *measResultServingCell* in the *measReportIdleNR* in *VarMeasIdleReport*. + - 3> if the *VarMeasIdleConfig* includes the *measIdleCarrierListNR* and it contains an entry with *carrierFreq* set to the value of the serving frequency: + - 4> if *beamMeasConfigIdle* is included in that entry, and if the UE supports *idleInactiveNR-MeasBeamReport* for the FR of the serving cell: + - 5> derive beam measurements based on SS/PBCH block for each measurement quantity indicated in *reportQuantityRS-Indexes*, as described in TS 38.215 [9]; + - 5> if the *reportQuantityRS-Indexes* is set to *rsrq*: + - 6> consider RSRQ as the beam sorting quantity; + - 5> else: + - 6> consider RSRP as the beam sorting quantity; + +5> set *resultsSSB-Indexes* to include up to *maxNrofRS-IndexesToReport* SS/PBCH block indexes in order of decreasing beam sorting quantity as follows: + +6> include the index associated to the best beam for the sorting quantity and if *absThreshSS-BlocksConsolidation* is included in *SIB2* of serving cell, the remaining beams whose sorting quantity is above *absThreshSS-BlocksConsolidation*; + +5> if the *includeBeamMeasurements* is set to true: + +6> include the beam measurement results as indicated by *reportQuantityRS-Indexes*; + +NOTE 1: How the UE performs idle/inactive measurements is up to UE implementation as long as the requirements in TS 38.133 [14] are met for measurement reporting. + +NOTE 2: The UE is not required to perform idle/inactive measurements on a given carrier if the SSB configuration of that carrier provided via dedicated signaling is different from the SSB configuration broadcasted in the serving cell, if any. + +NOTE 3: How the UE prioritizes which frequencies to measure or report (in case it is configured with more frequencies than it can measure or report) is left to UE implementation. + +NOTE 4: When *idleModeMeasVoiceFallback* is included in *SIB5*, UE may decide to measure and report idle/inactive measurements for EUTRA carrier frequencies included in *SIB5* even if it does not support NE-DC between the serving carrier and the EUTRA carrier frequencies. + +#### 5.7.8.3 T331 expiry or stop + +The UE shall: + +1> if T331 expires or is stopped: + +2> release the *VarMeasIdleConfig*. + +NOTE: It is up to UE implementation whether to continue idle/inactive measurements according to *SIB11* and *SIB4* configurations or according to E-UTRA *SIB5* and E-UTRA *SIB24* configurations as specified in TS 36.331 [10] upon inter-RAT cell reselection to E-UTRA, after T331 has expired or stopped. + +#### 5.7.8.4 Cell re-selection or cell selection while T331 is running + +The UE shall: + +1> if intra-RAT cell selection or reselection occurs while T331 is running: + +2> if *validityAreaList* is configured in *VarMeasIdleConfig*: + +3> if the serving frequency does not match with the *carrierFreq* of an entry in the *validityAreaList*; or + +3> if the serving frequency matches with the *carrierFreq* of an entry in the *validityAreaList*, the *validityCellList* is included in that entry, and the physical cell identity of the serving cell does not match with any entry in *validityCellList*: + +4> stop timer T331; + +4> perform the actions as specified in 5.7.8.3, upon which the procedure ends. + +1> else if inter-RAT cell selection or reselection occurs while T331 is running: + +2> stop timer T331; + +2> perform the actions as specified in 5.7.8.3; + +### 5.7.9 Mobility history information + +#### 5.7.9.1 General + +This procedure specifies how the mobility history information is stored by the UE, covering RRC\_IDLE, RRC\_INACTIVE and RRC\_CONNECTED and released by the UE upon deregistration. + +#### 5.7.9.2 Initiation + +If the UE supports storage of mobility history information, the UE shall: + +- 1> If the UE supports PSCell mobility history information and upon addition of a PSCell: + - 2> include an entry in *visitedPSCellInfoList* in variable *VarMobilityHistoryReport* possibly after performing the following, if necessary: + - 3> if *visitedPSCellInfoListReport* is available in the *visitedCellInfoList* in variable *VarMobilityHistoryReport*: + - 4> for the oldest PCell entry in *visitedCellInfoList* including *visitedPSCellInfoListReport*; + - 5> remove the oldest entry in the *visitedPSCellInfoListReport*; + - 3> else: + - 4> remove the oldest entry in *visitedPSCellInfoList* in variable *VarMobilityHistoryReport*; + - 2> for the included entry: + - 3> set the field *timeSpent* of the entry according to following: + - 4> if this is the first PSCell entry for the current PCell since entering the current PCell in RRC\_CONNECTED: + - 5> include the entry as the time spent with no PSCell since entering the current PCell in RRC\_CONNECTED; + - 4> else: + - 5> include the time spent with no PSCell since last PSCell release since entering the current PCell in RRC\_CONNECTED; +- 1> If the UE supports PSCell mobility history information and upon change, or release of a PSCell while being connected to the current PCell: + - 2> include an entry in *visitedPSCellInfoList* of the variable *VarMobilityHistoryReport* possibly after performing the following, if necessary: + - 3> if *visitedPSCellInfoListReport* is available in the *visitedCellInfoList* in variable *VarMobilityHistoryReport*: + - 4> for the oldest PCell entry in *visitedCellInfoList* including *visitedPSCellInfoListReport*; + - 5> remove the oldest entry in the *visitedPSCellInfoListReport*; + - 3> else: + - 4> remove the oldest entry in *visitedPSCellInfoList* in variable *VarMobilityHistoryReport*; + - 2> for the included entry: + - 3> if the global cell identity of the previous PSCell is available: + - 4> include the global cell identity of that cell in the field *visitedCellId* of the entry; + - 3> else: + +- 4> include the physical cell identity and carrier frequency of that cell in the field *visitedCellId* of the entry; +- 3> set the field *timeSpent* of the entry as the time spent in the previous PSCell while being connected to the current PCell; +- 1> Upon change of suitable cell, consisting of PCell in RRC\_CONNECTED (for NR or E-UTRA cell) or serving cell in RRC\_INACTIVE (for NR cell) or in RRC\_IDLE (for NR or E-UTRA cell), to another NR or E-UTRA cell, or when entering any cell selection' state from 'camped normally' state in NR or LTE or when entering 'any cell selection' state from a suitable cell in RRC\_CONNECTED state in NR or LTE: + - 2> include an entry in *visitedCellInfoList* of the variable *VarMobilityHistoryReport* possibly after removing the oldest entry, if necessary, according to following: + - 3> if the global cell identity of the previous PCell/serving cell is available: + - 4> include the global cell identity of that cell in the field *visitedCellId* of the entry; + - 3> else: + - 4> include the physical cell identity and carrier frequency of that cell in the field *visitedCellId* of the entry; + - 3> set the field *timeSpent* of the entry as the time spent in the previous PCell/serving cell; + - 3> if the UE supports PSCell mobility history information and if the UE continues to be connected to the same PSCell during the change of the PCell in RRC\_CONNECTED; or + - 3> if the UE supports PSCell mobility history information and if the UE changes PSCell at the same time as the change of the PCell in RRC\_CONNECTED; or + - 3> if the UE supports PSCell mobility history information and if the PSCell is released at the same time as the change of the PCell in RRC\_CONNECTED: + - 4> include an entry in *visitedPSCellInfoList* of the variable *VarMobilityHistoryReport* possibly after performing the following, if necessary: + - 5> if *visitedPSCellInfoListReport* is available in the *visitedCellInfoList* in variable *VarMobilityHistoryReport*: + - 6> for the oldest PCell entry in *visitedCellInfoList* including *visitedPSCellInfoListReport*: + - 7> remove the oldest entry in the *visitedPSCellInfoListReport*; + - 5> else: + - 6> remove the oldest entry in *visitedPSCellInfoList* in variable *VarMobilityHistoryReport*; + - 4> for the included entry: + - 5> if the global cell identity of the PSCell (in case the UE continues to be connected to the same PSCell) or the previous PSCell (in case the UE changes PSCell, or in case PSCell is released) is available: + - 6> include the global cell identity of that cell in the field *visitedCellId* of the entry; + - 5> else: + - 6> include the physical cell identity and carrier frequency of that cell in the field *visitedCellId* of the entry; + - 5> set the field *timeSpent* of the entry as the time spent in the PSCell, while being connected to previous PCell; + +- 4> include an entry in *visitedPSCellInfoList* after performing the following, if necessary; + - 5> if *visitedPSCellInfoListReport* is available in the *visitedCellInfoList* in variable *VarMobilityHistoryReport*: + - 6> for the oldest PCell entry in *visitedCellInfoList* including *visitedPSCellInfoListReport*: + - 7> remove the oldest entry in the *visitedPSCellInfoListReport*; + - 5> else: + - 6> remove the oldest entry in *visitedPSCellInfoList* in variable *VarMobilityHistoryReport*; +- 4> for the included entry: + - 5> set the field *timeSpent* of the entry as the time without PSCell according to the following: + - 6> if the UE experienced a PSCell release since entering the previous PCell in RRC\_CONNECTED: + - 7> include the time spent with no PSCell since last PSCell release since entering the previous PCell in RRC\_CONNECTED; + - 6> else: + - 7> include the time spent with no PSCell since entering the previous PCell in RRC\_CONNECTED; +- 3> if the UE supports PSCell mobility history information and if *visitedPSCellInfoList* exists in *VarMobilityHistoryReport*: + - 4> include *visitedPSCellInfoList* in *VarMobilityHistoryReport* in the *visitedPSCellInfoListReport* within the entry of the *visitedCellInfoList* associated to the latest PCell entry; + - 4> remove *visitedPSCellInfoList* from the variable *VarMobilityHistoryReport*; +- 1> if the UE supports PSCell mobility history information and upon entering 'camped normally' state in NR (in RRC\_IDLE or RRC\_INACTIVE) or E-UTRA (in RRC\_IDLE) while previously in RRC\_CONNECTED state NR or LTE while not connected to a PSCell: + - 2> include an entry in *visitedPSCellInfoList* after performing the following, if necessary; + - 3> if *visitedPSCellInfoListReport* is available in the *visitedCellInfoList* in variable *VarMobilityHistoryReport*: + - 4> for the oldest PCell entry in *visitedCellInfoList* including *visitedPSCellInfoListReport*: + - 5> remove the oldest entry in the *visitedPSCellInfoListReport*; + - 3> else: + - 4> remove the oldest entry in *visitedPSCellInfoList* in variable *VarMobilityHistoryReport*; + - 2> for the included entry: + - 3> set the field *timeSpent* of the entry as the time without PSCell according to the following: + - 4> if the UE experienced a PSCell release since entering the current PCell in RRC\_CONNECTED: + - 5> include the time spent with no PSCell since last PSCell release after entering the current PCell in RRC\_CONNECTED; + - 4> else: + - 5> include the time spent with no PSCell since entering the current PCell in RRC\_CONNECTED; +- 1> upon entering 'camped normally' state in NR (in RRC\_IDLE or RRC\_INACTIVE) or E-UTRA (in RRC\_IDLE) while previously in 'any cell selection' state or 'camped on any cell' state in NR or LTE: + +- 2> include an entry in variable *VarMobilityHistoryReport* possibly after removing the oldest entry, if necessary, according to following: + - 3> set the field *timeSpent* of the entry as the time spent in 'any cell selection' state and/or 'camped on any cell' state in NR or LTE. + +#### 5.7.9.3 Release of Mobility History Information + +If the UE supports storage of mobility history information, the UE shall: + +- 1> if stored, discard the mobility history information, i.e. release the UE variable *VarMobilityHistoryReport* upon deregistration from the network. + +### 5.7.10 UE Information + +#### 5.7.10.1 General + +![Sequence diagram illustrating the UE information procedure. The diagram shows two lifelines: UE and Network. The Network sends a UEInformationRequest message to the UE, and the UE responds with a UEInformationResponse message.](20136850feb70fd71c7d41cdae203ebb_img.jpg) + +``` + +sequenceDiagram + participant Network + participant UE + Note right of Network: UEInformationRequest + Network->>UE: UEInformationRequest + Note left of UE: UEInformationResponse + UE->>Network: UEInformationResponse + +``` + +Sequence diagram illustrating the UE information procedure. The diagram shows two lifelines: UE and Network. The Network sends a UEInformationRequest message to the UE, and the UE responds with a UEInformationResponse message. + +Figure 5.7.10.1-1: UE information procedure + +The UE information procedure is used by the network to request the UE to report information. + +#### 5.7.10.2 Initiation + +The network initiates the procedure by sending the *UEInformationRequest* message. The network should initiate this procedure only after successful security activation. + +#### 5.7.10.3 Reception of the *UEInformationRequest* message + +Upon receiving the *UEInformationRequest* message, the UE shall, only after successful security activation: + +- 1> if the *idleModeMeasurementReq* is included in the *UEInformationRequest* and the UE has stored *VarMeasIdleReport* that contains measurement information concerning cells other than the PCell: + - 2> set the *measResultIdleEUTRA* in the *UEInformationResponse* message to the value of *measReportIdleEUTRA* in the *VarMeasIdleReport*, if available; + - 2> set the *measResultIdleNR* in the *UEInformationResponse* message to the value of *measReportIdleNR* in the *VarMeasIdleReport*, if available; + - 2> discard the *VarMeasIdleReport* upon successful delivery of the *UEInformationResponse* message confirmed by lower layers; +- 1> if the *logMeasReportReq* is present and if the RPLMN is included in *plmn-IdentityList* stored in *VarLogMeasReport*, or if the current registered SNPN is included in *snpn-ConfigIDList* stored in *VarLogMeasReport*: + - 2> if *VarLogMeasReport* includes one or more logged measurement entries, set the contents of the *logMeasReport* in the *UEInformationResponse* message as follows: + - 3> include the *absoluteTimeStamp* and set it to the value of *absoluteTimeInfo* in the *VarLogMeasReport*; + - 3> include the *traceReference* and set it to the value of *traceReference* in the *VarLogMeasReport*; + +- 3> include the *traceRecordingSessionRef* and set it to the value of *traceRecordingSessionRef* in the *VarLogMeasReport*; +- 3> include the *tce-Id* and set it to the value of *tce-Id* in the *VarLogMeasReport*; +- 3> include the *logMeasInfoList* and set it to include one or more entries from the *VarLogMeasReport* starting from the entries logged first, and for each entry of the *logMeasInfoList* that is included, include all information stored in the corresponding *logMeasInfoList* entry in *VarLogMeasReport*; +- 3> if the *VarLogMeasReport* includes one or more additional logged measurement entries that are not included in the *logMeasInfoList* within the *UEInformationResponse* message: + - 4> include the *logMeasAvailable*; + - 4> if *bt-LocationInfo* is included in *locationInfo* of one or more of the additional logged measurement entries in *VarLogMeasReport* that are not included in the *logMeasInfoList* within the *UEInformationResponse* message: + - 5> include the *logMeasAvailableBT*; + - 4> if *wlan-LocationInfo* is included in *locationInfo* of one or more of the additional logged measurement entries in *VarLogMeasReport* that are not included in the *logMeasInfoList* within the *UEInformationResponse* message: + - 5> include the *logMeasAvailableWLAN*; +- 1> if *ra-ReportReq* is set to *true* and the UE has random access related information available in *VarRA-Report* and if the RPLMN is included in *plmn-IdentityList* stored in *VarRA-Report*; or +- 1> if *ra-ReportReq* is set to *true* and the UE has random access related information available in *VarRA-Report* and if the registered SNPN is included in *snpn-IdentityList* stored in *VarRA-Report*: + - 2> set the *ra-ReportList* in the *UEInformationResponse* message to the value of *ra-ReportList* in *VarRA-Report*; + - 2> discard the *ra-ReportList* from *VarRA-Report* upon successful delivery of the *UEInformationResponse* message confirmed by lower layers; +- 1> if *rlf-ReportReq* is set to *true*: + - 2> if the UE has radio link failure information or handover failure information available in *VarRLF-Report* and if the RPLMN is included in *plmn-IdentityList* stored in *VarRLF-Report*; or + - 2> if the UE has radio link failure information or handover failure information available in *VarRLF-Report* and if the current registered SNPN is included in *snpn-IdentityList* stored in *VarRLF-Report*: + - 3> set *timeSinceFailure* in *VarRLF-Report* to the time that elapsed since the last radio link failure or handover failure in NR; + - 3> set the *rlf-Report* in the *UEInformationResponse* message to the value of *rlf-Report* in *VarRLF-Report*; + - 3> discard the *rlf-Report* from *VarRLF-Report* upon successful delivery of the *UEInformationResponse* message confirmed by lower layers; + - 2> else if the UE is capable of cross-RAT RLF reporting as defined in TS 38.306 [26] and has radio link failure information or handover failure information available in *VarRLF-Report* of TS 36.331 [10] and if the RPLMN is included in *plmn-IdentityList* stored in *VarRLF-Report* of TS 36.331 [10]: + - 3> set *timeSinceFailure* in *VarRLF-Report* of TS 36.331 [10] to the time that elapsed since the last radio link failure or handover failure in EUTRA; + - 3> set *failedPCellId-EUTRA* in the *rlf-Report* in the *UEInformationResponse* message to indicate the PCell in which RLF was detected or the source PCell of the failed handover in the *VarRLF-Report* of TS 36.331 [10]; + - 3> set the *measResult-RLF-Report-EUTRA* in the *rlf-Report* in the *UEInformationResponse* message to the value of *rlf-Report* in *VarRLF-Report* of TS 36.331 [10]; + +- 3> discard the *rlf-Report* from *VarRLF-Report* of TS 36.331 [10] upon successful delivery of the *UEInformationResponse* message confirmed by lower layers; +- 1> if *connEstFailReportReq* is set to *true* and the UE has connection establishment failure or connection resume failure information in *VarConnEstFailReport* or *VarConnEstFailReportList* and if the RPLMN is equal to *plmn-Identity* stored in *VarConnEstFailReport* or in at least one of the entries of *VarConnEstFailReportList*: +- 1> if *connEstFailReportReq* is set to *true* and if the UE has connection establishment failure information or connection resume failure information available in *VarConnEstFailReport* or *VarConnEstFailReportList* and if the registered SNPN identity is equal to *snpn-identity* stored in *VarConnEstFailReport* or any entry of *VarConnEstFailReportList*: +- 2> set *timeSinceFailure* in *VarConnEstFailReport* to the time that elapsed since the last connection establishment failure or connection resume failure in NR; +- 2> set the *connEstFailReport* in the *UEInformationResponse* message to the value of *connEstFailReport* in *VarConnEstFailReport*; +- 2> if the UE supports multiple CEF report: +- 3> for each *connEstFailReport* in the *connEstFailReportList* in *VarConnEstFailReportList*: +- 4> set *timeSinceFailure* to the time that elapsed since the associated connection establishment failure or connection resume failure in NR; +- 2> for each *connEstFailReport* in the *connEstFailReportList* in the *UEInformationResponse* message, set the value to the value of *connEstFailReport* in *VarConnEstFailReport* in *VarConnEstFailReportList*; +- 2> discard the *connEstFailReport* from *VarConnEstFailReport* and *VarConnEstFailReportList* upon successful delivery of the *UEInformationResponse* message confirmed by lower layers; +- 1> if the *mobilityHistoryReportReq* is set to *true*: +- 2> include the *mobilityHistoryReport* and set it to include *visitedCellInfoList* from *VarMobilityHistoryReport*; +- 2> include in the *mobilityHistoryReport* an entry for the current PCell, possibly after removing the oldest entry if required, and set its fields as follows: +- 3> set *visitedCellId* to the global cell identity or the physical cell identity and carrier frequency of the current PCell; +- 3> set field *timeSpent* to the time spent in the current PCell; +- 3> if the UE supports PSCell mobility history information and if *visitedPSCellInfoList* is present in *VarMobilityHistoryReport*: +- 4> for the newest entry of the PCell in the *mobilityHistoryReport*, include *visitedPSCellInfoList* from *VarMobilityHistoryReport*; +- 4> if the UE is configured with a PSCell: +- 5> for the newest entry of the PCell in the *mobilityHistoryReport*, include the current PSCell information in the *visitedPSCellInfoListReport*, possibly after removing the oldest PSCell entry of a PCell in the *mobilityHistoryReport*, if required, and set its fields as follows: +- 6> set *visitedCellId* to the global cell identity or the physical cell identity and carrier frequency of the current PSCell; +- 6> set field *timeSpent* to the time spent in the current PSCell while being connected to the current PCell; +- 4> else: +- 5> for the newest entry of the PCell in the *mobilityHistoryReport*, include a new entry in the *visitedPSCellInfoListReport*, possibly after removing the oldest PSCell entry of a PCell in the *mobilityHistoryReport*, if required, and set its fields as follows: + +- 6> set field *timeSpent* to the time spent without PSCell in the current PCell since last PSCell release since connected to the current PCell in RRC\_CONNECTED; + - 3> else if the UE supports PSCell mobility history information: + - 4> if the UE is configured with a PSCell: + - 5> for the newest entry of the PCell in the *mobilityHistoryReport*, include the current PSCell information in the *visitedPSCellInfoListReport*, possibly after removing the oldest PSCell entry of a PCell in the *mobilityHistoryReport*, if required, and set its fields as follows: + - 6> set *visitedCellId* to the global cell identity or the physical cell identity and carrier frequency of the current PSCell; + - 6> set field *timeSpent* to the time spent in the current PSCell while being connected to the current PCell; + - 4> else: + - 5> for the newest entry of the PCell in the *mobilityHistoryReport*, include a new entry in the *visitedPSCellInfoListReport*, possibly after removing the oldest PSCell entry of a PCell in the *mobilityHistoryReport*, if required, and set its fields as follows: + - 6> set field *timeSpent* to the time spent without PSCell in the current PCell since connected to the current PCell in RRC\_CONNECTED; +- 1> if the *successHO-ReportReq* is set to *true* and if the UE has successful handover related information available in *VarSuccessHO-Report* and if the RPLMN is included in the *plmn-IdentityList* stored in *VarSuccessHO-Report*; or +- 1> if the *successHO-ReportReq* is set to *true* and if the UE has successful handover related information available in *VarSuccessHO-Report* and if the current registered SNPN is included in *snpn-IdentityList* if stored in the *VarSuccessHO-Report*: + - 2> if the *successHO-Report* in the *VarSuccessHO-Report* concerns a DAPS handover and if a PDCP PDU has been received from the source cell of the concerned HO and a non-duplicated PDCP PDU has been received from the target cell of the concerned HO: + - 3> set *upInterruptionTimeAtHO* in *VarSuccessHO-Report* to include the time elapsed between the time of arrival of the last PDCP PDU received from the source cell of the concerned handover and the time of arrival of the first non-duplicate PDCP PDU received from the target cell of the concerned handover, as measured at the time of arrival of the first non-duplicate PDCP PDU received from the target cell; + - 2> if the *successHO-Report* in the *VarSuccessHO-Report* concerns a *mobilityFromNRCommand*: + - 3> set *timeSinceSHR* in *VarSuccessHO-Report* to the time that elapsed since the execution of the associated *mobilityFromNRCommand*; + - 2> set the *successHO-Report* in the *UEInformationResponse* message to the value of *successHO-Report* in the *VarSuccessHO-Report*, if available; + - 2> discard the *VarSuccessHO-Report* upon successful delivery of the *UEInformationResponse* message confirmed by lower layers; +- 1> if the *successPSCell-ReportReq* is set to *true* and if the UE has successful PSCell change or addition information available in *VarSuccessPSCell-Report* and if the RPLMN is included in *plmn-IdentityList* stored in *VarSuccessPSCell-Report*; or +- 1> if the *successPSCell-ReportReq* is set to *true* and if the UE has successful PSCell change or addition information available in *VarSuccessPSCell-Report* and if the current registered SNPN is included in *snpn-IdentityList* if stored in the *VarSuccessPSCell-Report*: + - 2> set the *successPSCell-Report* in the *UEInformationResponse* message to the value of *successPSCell-Report* in the *VarSuccessPSCell-Report*; + +- 2> discard the *VarSuccessPSCell-Report* upon successful delivery of the *UEInformationResponse* message confirmed by lower layers; +- 1> if the *coarseLocationRequest* is set to *true*: + - 2> include *coarseLocationInfo*, if available; +- 1> if the *flightPathInfoReq* is included in the *UEInformationRequest* and the UE has flight path information available, set the *flightPathInfoReport* in the *UEInformationResponse* message as follows: + - 2> include the list of up to *maxWayPointNumber* waypoints along the flight path; + - 2> if the *includeTimeStamp* is set to *true*, for each included waypoint: + - 3> if available, set the field *timestamp* to the time when UE intends to arrive at the waypoint; +- 1> if the *logMeasReport* is included in the *UEInformationResponse*: + - 2> submit the *UEInformationResponse* message to lower layers for transmission via SRB2; + - 2> discard the logged measurement entries included in the *logMeasInfoList* from *VarLogMeasReport* upon successful delivery of the *UEInformationResponse* message confirmed by lower layers; +- 1> else: + - 2> submit the *UEInformationResponse* message to lower layers for transmission via SRB1. + +#### 5.7.10.4 Actions for the Random Access report determination + +Upon successfully performing random-access procedure initialized with 4-step or 2-step RA type, or upon failed or successfully completed on-demand system information acquisition procedure in RRC\_IDLE or RRC\_INACTIVE state, or upon failed or successfully completed RA-SDT operation as specified in clause 5.3.13.5, the UE shall: + +- 1> if the RPLMN or the PLMN selected by upper layers (see TS24.501 [23]) from the PLMN(s) included in the *plmn-IdentityList* in *SIB1* is not included in *plmn-IdentityList* stored in a non-empty *VarRA-Report*; or +- 1> if the registered SNPN or the SNPN selected by upper layers (see TS24.501 [23]) from the list of SNPN(s) included in the *NPN-IdentityInfoList* in *SIB1* is not included in *plmn-IdentityList* stored in a non-empty *VarRA-Report*: + - 2> clear the information included in *VarRA-Report*; +- 1> if the UE is not in SNPN access mode and if the number of *RA-Report* entries stored in the *ra-ReportList* in *VarRA-Report* is less than *maxRAReport*: + - 2> if the number of PLMN entries in *plmn-IdentityList* stored in *VarRA-Report* is less than *maxPLMN*; or + - 2> if the number of PLMN entries in *plmn-IdentityList* stored in *VarRA-Report* is equal to *maxPLMN* and the list of EPLMNs is subset of or equal to the *plmn-IdentityList* stored in *VarRA-Report*: + - 3> append the following contents associated to the successfully completed random-access procedure or the failed or successfully completed on-demand system information acquisition procedure as a new entry in the *VarRA-Report*: + - 4> if the list of EPLMNs has been stored by the UE: + - 5> set the *plmn-IdentityList* to include the list of EPLMNs stored by the UE (i.e. includes the RPLMN) without exceeding the limit of *maxPLMN*; + - 4> else: + - 5> set the *plmn-Identity*, in *plmn-IdentityList*, to the PLMN selected by upper layers (see TS 24.501 [23]) from the PLMN(s) included in the *plmn-IdentityInfoList* in *SIB1*; + - 4> set the *cellId* to the global cell identity and the tracking area code, if available, otherwise to the physical cell identity and carrier frequency of the cell in which the corresponding random-access preamble was transmitted; + +- 4> if the UE supports spCell ID indication: + - 5> if the corresponding random-access procedure was performed on an SCell of MCG: + - 6> set the *spCellId* to the global cell identity of the PCell; + - 5> if the corresponding random-access procedure was performed on an SCell of SCG: + - 6> set the *spCellId* to the global cell identity of the PSCell, if available, otherwise, set the *spCellId* to the global cell identity of the PCell; + - 5> if the corresponding random-access procedure was performed on PSCell: + - 6> if the *cellId* is not set to the global cell identity of the PSCell, set the *spCellId* to the global cell identity of the PCell; + - 4> set the *raPurpose* to include the purpose of triggering the random-access procedure; + - 4> set the *ra-InformationCommon* as specified in clause 5.7.10.5. +- 1> if the UE is in SNPN access mode and if the number of *RA-Report* entries stored in the *ra-ReportList* in *VarRA-Report* is less than *maxRAReport*: + - 2> if the number of SNPN identity entries in *snpn-IdentityList* stored in *VarRA-Report* is less than *maxNPN*; or + - 2> if the number of SNPN identity entries in *snpn-IdentityList* stored in *VarRA-Report* is equal to *maxNPN* and the list of equivalent SNPN(s) is subset of or equal to the *snpn-IdentityList* stored in *VarRA-Report*: + - 3> append the following contents associated to the successfully completed random-access procedure or the failed or successfully completed on-demand system information acquisition procedure as a new entry in the *VarRA-Report*: + - 4> if the list of equivalent SNPN(s) has been stored by the UE: + - 5> set the *snpn-IdentityList* to include the list of equivalent SNPN(s) stored by the UE (i.e. includes the registered SNPN) without exceeding the limit of *maxNPN*; + - 4> else: + - 5> set the *snpn-Identity*, in *snpn-IdentityList*, to the SNPN identity selected by upper layers (see TS 24.501 [23]) from the SNPN identities included in the *NPN-IdentityInfoList* in SIB1; + - 4> set the *cellId* to the global cell identity and the tracking area code, if available, otherwise to the physical cell identity and carrier frequency of the cell in which the corresponding random-access preamble was transmitted; + - 4> if the UE supports spCell ID indication: + - 5> if the corresponding random-access procedure was performed on an SCell of MCG: + - 6> set the *spCellId* to the global cell identity of the PCell; + - 5> if the corresponding random-access procedure was performed on an SCell of SCG: + - 6> set the *spCellId* to the global cell identity of the PSCell, if available, otherwise, set the *spCellId* to the global cell identity of the PCell; + - 5> if the corresponding random-access procedure was performed on PSCell: + - 6> if the *cellId* is not set to the global cell identity of the PSCell, set the *spCellId* to the global cell identity of the PCell; + - 4> set the *raPurpose* to include the purpose of triggering the random-access procedure; + - 4> set the *ra-InformationCommon* as specified in clause 5.7.10.5. + +The UE may discard the random access report information, i.e. release the UE variable *VarRA-Report*, 48 hours after the last successful random access procedure or the failed or successfully completed on-demand system information acquisition procedure or the failed or successfully completed RA-SDT procedure related information is added to the *VarRA-Report*. + +NOTE 1: Void. + +#### 5.7.10.5 RA information determination + +The UE shall, for the last successfully completed or last failed random-access procedure, set the content in *ra-InformationCommon* as follows: + +- 1> set the *absoluteFrequencyPointA* to indicate the absolute frequency of the reference resource block associated to the random-access resources used in the random-access procedure; +- 1> set the *locationAndBandwidth* and *subcarrierSpacing* associated to the UL BWP of the random-access resources used in the random-access procedure; +- 1> if contention based random-access resources are used in the random-access procedure: + - 2> set the *msgA\_RO-FrequencyStart* and *msgA-RO-FDM* and *msgA-SubcarrierSpacing* associated to the 2 step random- access resources if used in the random-access procedure; + - 2> if *msgA-SubcarrierSpacing* associated to the 2 step random-access resources used in the random-access procedure is available: + - 3> set the *msgA-SubcarrierSpacing* associated to the 2 step random-access resources used in the random- access procedure; + - 2> else if only 2 step random-access resources are available in the UL BWP used in the random-access procedure: + - 3> set the *msgA-SCS-From-prach-ConfigurationIndex* to the subcarrier spacing as derived from the *msgA-PRACH-ConfigurationIndex* used in the 2-step random-access procedure; + - 2> else: + - 3> set the *msg1-SubcarrierSpacing* associated to the 4 step random-access resources used in the random- access procedure; + - 2> set the *msg1-FrequencyStart* associated to the 4 step random-access resources if used in the random-access procedure, and if its value is different from the value of *msgA-RO-FrequencyStart* if it is included in the *ra-InformationCommon*; + - 2> set the *msg1-FDM* associated to the 4 step random-access resources if used in the random-access procedure, and if its value is different from the value of *msgA-RO-FDMCFRA* if it is included in the *ra-InformationCommon*; + - 2> if *msg1-SubcarrierSpacing* associated to the 4 step random-access resources used in the random-access procedure is available, and if its value is different from the value of *msgA-SubcarrierSpacing* if it is included in the *ra-InformationCommon*: + - 3> set the *msg1-SubcarrierSpacing* associated to the 4 step random-access resources used in the random- access procedure; + - 2> else: + - 3> set the *msg1-SCS-From-prach-ConfigurationIndex* to the subcarrier spacing as derived from the *prach-ConfigurationIndex* used in the 4-step random-access procedure, and if its value is different from the value of *msgA-SCS-From-prach-ConfigurationIndex* if it is included in the *ra-InformationCommon*; +- 1> if contention free random-access resources are used in the random-access procedure: + - 2> set the *msg1-FrequencyStartCFRA* and *msg1-FDMCFRA* associated to the 4 step random-access resources if used in the random-access procedure; + +- 2> if *msg1-SubcarrierSpacing* associated to the 4 step random-access resources used in the random-access procedure is available: + - 3> set the *msg1-SubcarrierSpacingCFRA* associated to the 4 step random-access resources used in the random-access procedure; +- 2> else: + - 3> set the *msg1-SCS-From-prach-ConfigurationIndexCFRA* to the subcarrier spacing as derived from the *prach-ConfigurationIndex* used in the 4 step random-access procedure; +- 2> set the *msgA-RO-FrequencyStartCFRA* and *msgA-RO-FDMCFRA* associated to the 2 step contention free random access resources if used in the random-access procedure; +- 2> set the *msgA-MCS*, the *nrofPRBs-PerMsgA-PO*, the *msgA-PUSCH-TimeDomainAllocation*, the *frequencyStartMsgA-PUSCH*, the *nrofMsgA-PO-FDM* associated to the 2 step random-access resources if used in the random-access procedure; +- 2> if *msgA-SubcarrierSpacing* associated to the 2 step random-access resources used in the random-access procedure is available: + - 3> set the *msgA-SubcarrierSpacing* associated to the 2 step random-access resources used in the random-access procedure; +- 2> else if only 2 step random-access resources are available in the UL BWP used in the random-access procedure: + - 3> set the *msgA-SCS-From-prach-ConfigurationIndex* to the subcarrier spacing as derived from the *msgA-PRACH-ConfigurationIndex* used in the 2-step random-access procedure; +- 2> else: + - 3> set the *msg1-SubcarrierSpacing* associated to the 4 step random-access resources used in the random-access procedure; +- 1> if the random access procedure is initialized with *RA\_TYPE* set to *2-stepRA* as described in TS 38.321 [3]: + - 2> set the *dlPathlossRSRP* to the measured RSRP of the DL pathloss reference obtained at the time of *RA\_Type* selection stage of the initialization of the RA procedure as captured in TS 38.321 [3]; + - 2> if the configuration for the random access *msgA-TransMax* was configured in *RACH-ConfigDedicated* for this random access procedure, and *raPurpose* is set to *reconfigurationWithSync*: + - 3> set *msgA-TransMax* to the value of *msgA-TransMax* in *RACH-ConfigDedicated*; + - 2> else if *msgA-TransMax* was configured in *RACH-ConfigCommonTwoStepRA*: + - 3> set *msgA-TransMax* to the value of *msgA-TransMax* in *RACH-ConfigCommonTwoStepRA*; + - 2> set the *msgA-PUSCH-PayloadSize* to the size of the overall payload available in the UE buffer at the time of initiating the 2 step RA procedure; +- 1> if the purpose of the random access procedure is to request on-demand system information (i.e., if the *raPurpose* is set to *requestForOtherSI* or *msg3RequestForOtherSI*): + - 2> set the *intendedSIBs* to indicate the SIB(s) the UE wanted to receive as a result of the SI request; + - 2> set the *ssbsForSI-Acquisition* to indicate the SSB(s) used to receive the SI message; + - 2> if the on-demand system information acquisition was successful: + - 3> set the *onDemandSISuccess* to *true*; +- 1> if one or more of the features including RedCap and/or Slicing and/or SDT and/or MSG3 repetition are applicable for this random-access procedure as specified in clause 5.1.1b of TS 38.321[3]: + +- 2> set the *triggeredFeatureCombination* to indicate all the features triggering this random-access procedure as below: + - 3> if this random-access procedure is triggered by RedCap, includes *redCap*; + - 3> if this random-access procedure is triggered by SDT, includes *smallData*; + - 3> if this random-access procedure is triggered by Msg3 repetition, includes *msg3-Repetitions*; + - 3> if this random-access procedure is triggered by slicing, set *nsag* to the NSAG ID applied in the random-access procedure and set the *triggered-S-NSSAI-List* to include all the *S-NSSAI(s)* associated to the slices triggering the access attempt in the random-access procedure; +- 2> if the value of used feature or combination of features is different from the *triggeredFeatureCombination*: + - 3> set the *usedFeatureCombination* to indicate one or more features of *FeatureCombination* associated to the random-access resource used in the random-access procedure as below: + - 4> if RedCap is part of the used *FeatureCombination*, include *redCap*; + - 4> if SDT is part of the used *FeatureCombination*, include *smallData*; + - 4> if Msg3 repetition is part of the used *FeatureCombination*, include *msg3-Repetitions*; + - 4> if NSAG(s) is part of the used *FeatureCombination*, set *NSAG-List* to include the *NSAG-ID(s)* configured for the used *FeatureCombination*; +- 1> if the random-access procedure is initiated for SDT and the SDT transmission was failed: + - 3> include the *sdt-Failed*; +- 1> set the parameters associated to the successive random-access attempts associated to the selected beam in the *perRAInfoList* as follows: + - 2> if the random-access resource used is associated to a SS/PBCH block, set the associated random-access parameters for the successive random-access attempts associated to the same SS/PBCH block for one or more random-access attempts as follows: + - 3> set the *ssb-Index* to include the SS/PBCH block index associated to the used random-access resource; + - 3> set the *numberOfPreamblesSentOnSSB* to indicate the number of successive random-access attempts associated to the SS/PBCH block; + - 3> if all preamble transmissions for the successive random-access attempts associated to this SS/PBCH block were blocked by LBT: + - 4> include *allPreamblesBlocked*; + - 3> else: + - 4> if LBT failure indication was received from lower layers for the last random-access preamble transmission attempt in the SS/PBCH block associated to the *ssb-Index*, before changing the SS/PBCH block for random access preamble transmission: + - 5> include *lbt-Detected*; + - 3> for each random-access attempt performed on the random-access resource, except the random-access attempts for which LBT failure indication was received from lower layers, include the following parameters in the chronological order of the random-access attempt: + - 4> if the random-access attempt is performed on the contention based random-access resource and if *raPurpose* is not equal to '*requestForOtherST*', include *contentionDetected* as follows: + - 5> if contention resolution was not successful as specified in TS 38.321 [6] for the transmitted preamble: + - 6> set the *contentionDetected* to *true*; + +- 5> else: + - 6> set the *contentionDetected* to *false*; +- 4> if the random access attempt is a 2-step random access attempt: + - 5> if fallback from 2-step random access to 4-step random access occurred during the random access attempt: + - 6> set *fallbackToFourStepRA* to *true*; + - 4> if the random-access attempt is performed on the contention based random-access resource; or + - 4> if the random-access attempt is performed on the contention free random-access resource and if the random-access procedure was initiated due to the PDCCH ordering: + - 5> if the random access attempt is a 4-step random access attempt and the SS/PBCH block RSRP of the SS/PBCH block corresponding to the random-access resource used in the random-access attempt is above *rsrp-ThresholdSSB*; or + - 5> if the random access attempt is a 2-step random access attempt and the SS/PBCH block RSRP of the SS/PBCH block corresponding to the random-access resource used in the random-access attempt is above *msgA-RSRP-ThresholdSSB*: + - 6> set the *dlRSRPAboveThreshold* to *true*; + - 5> else: + - 6> set the *dlRSRPAboveThreshold* to *false*; +- 2> else if the random-access resource used is associated to a CSI-RS, set the associated random-access parameters for the successive random-access attempts associated to the same CSI-RS for one or more random-access attempts as follows: + - 3> set the *csi-RS-Index* to include the CSI-RS index associated to the used random-access resource; + - 3> set the *numberOfPreamblesSentOnCSI-RS* to indicate the number of successive random-access attempts associated to the CSI-RS; + - 3> if all preamble transmissions for the successive random-access attempts associated to this CSI-RS were blocked by LBT: + - 4> include *allPreamblesBlocked*; + - 3> else: + - 4> if LBT failure indication was received from lower layers for the last random-access preamble transmission attempt in the CSI-RS associated to the *csi-RS-Index*, before changing the CSI-RS for random access preamble transmission: + - 5> include *lbt-Detected*; +- 1> if at least one LBT failure indication has been received from lower layers during the random-access procedure: + - 2> set the *numberOfLBTFailures* to indicate the total number of random-access attempts for which LBT failure indications have been received from lower layers in the random-access procedure. + +The UE shall, for all the BWPs in which consistent LBT failures are triggered and not cancelled at the moment of successful RA completion or for all the BWPs in which consistent LBT failures are detected prior the RLF/HOF, set the below parameters in *attemptedBWP-InfoList* in the chronological order of BWP selection: + +- 1> set the *locationAndBandwidth* and *subcarrierSpacing* associated to the UL BWP. + +NOTE 1: Void. + +NOTE 2: If *allPreamblesBlocked* is included, it is left to UE implementation how to set the *numberOfPreamblesSentOnSSB-r16*, *numberOfPreamblesSentOnCSI-RS-r16* and the *perRAAttemptInfoList-r16*. + +#### 5.7.10.6 Actions for the successful handover report determination + +The UE shall for the PCell: + +- 1> if the procedure is triggered due to successful completion of reconfiguration with sync, and if the ratio between the value of the elapsed time of the timer T304 and the configured value of the timer T304, included in the last applied *RRCReconfiguration* message including the *reconfigurationWithSync*, is greater than *thresholdPercentageT304* if included in the *successHO-Config* received before executing the last reconfiguration with sync; or +- 1> if the procedure is triggered due to successful completion of reconfiguration with sync, and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync, is greater than *thresholdPercentageT310* included in the *successHO-Config* if configured by the source PCell before executing the last reconfiguration with sync; or +- 1> if the procedure is triggered due to successful completion of reconfiguration with sync, and if the T312 associated to the measurement identity of the target cell was running at the time of initiating the execution of the reconfiguration with sync procedure and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync, is greater than *thresholdPercentageT312* included in the *successHO-Config* if configured by the source PCell before executing the last reconfiguration with sync; or +- 1> if the procedure is triggered due to successful completion of reconfiguration with sync, and if *sourceDAPS-FailureReporting* is included in the *successHO-Config* before executing the last reconfiguration with sync and is set to *true* and if the last executed handover was a DAPS handover and if an RLF occurred at the source PCell during the DAPS handover while T304 was running; or +- 1> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PCell before executing the last Mobility from NR to E-UTRA, is greater than *thresholdPercentageT310* included in the *successHO-Config* if configured by the source PCell before executing the last Mobility from NR to E-UTRA; or +- 1> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, and if the T312 associated to the measurement identity of the target cell was running at the time of initiating the execution of the Mobility from NR to E-UTRA and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PCell before executing the last Mobility from NR to E-UTRA, is greater than *thresholdPercentageT312* included in the *successHO-Config* if configured by the source PCell before executing the last Mobility from NR to E-UTRA; +- 2> store the successful handover information in *VarSuccessHO-Report* and determine the content in *VarSuccessHO-Report* as follows: + - 3> clear the information included in *VarSuccessHO-Report*, if any; + - 3> if the UE is not in SNPN access mode, set the *plmn-IdentityList* to include the list of EPLMNs stored by the UE (i.e., includes the RPLMN); + - 3> else if the UE is in SNPN access mode, set the *snpn-IdentityList* to include the list of equivalent SNPNs stored by the UE (i.e., includes the registered SNPN), if available; + - 3> set the *c-RNTI* to the C-RNTI assigned by the target PCell of the handover; + - 3> if the procedure is triggered due to successful completion of reconfiguration with sync, for the source PCell in which the last *RRCReconfiguration* message including *reconfigurationWithSync* was applied; or + - 3> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, for the source PCell in which the last *MobilityFromNRCommand* concerning an inter-RAT handover from NR to E-UTRA was applied; + +- 4> set the *sourcePCellID* in *sourceCellInfo* to the global cell identity and tracking area code, if available, of the source PCell; +- 4> set the *sourceCellMeas* in *sourceCellInfo* to include the cell level RSRP, RSRQ and the available SINR, of the source PCell based on the available SSB and CSI-RS measurements collected up to the moment the UE sends *RRCReconfigurationComplete* message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA *RRCConnectionReconfigurationComplete* message if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA; +- 4> set the *rsIndexResults* in *sourceCellMeas* to include all the available SSB and CSI-RS measurement quantities of the source PCell collected up to the moment the UE sends *RRCReconfigurationComplete* message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA *RRCConnectionReconfigurationComplete* message if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA; +- 4> if the last executed handover was a DAPS handover and if an RLF occurred at the source PCell during the DAPS handover while T304 was running: + - 5> set the *rlf-InSourceDAPS* in *sourceCellInfo* to *true*; +- 3> if the procedure is triggered due to successful completion of reconfiguration with sync, for the target PCell indicated in the last applied *RRCReconfiguration* message including *reconfigurationWithSync*: + - 4> set the *targetPCellID* in *targetCellInfo* to the global cell identity and tracking area code, if available, of the target PCell; + - 4> set the *targetCellMeas* in *targetCellInfo* to include the cell level RSRP, RSRQ and the available SINR, of the target PCell based on the available SSB and CSI-RS measurements collected up to the moment the UE sends *RRCReconfigurationComplete* message; + - 4> set the *rsIndexResults* in *targetCellMeas* to include all the available SSB and CSI-RS measurement quantities of the target PCell collected up to the moment the UE sends *RRCReconfigurationComplete* message; + - 4> if the last applied *RRCReconfiguration* message including *reconfigurationWithSync* was included in the stored *condRRCReconfig*: + - 5> set the *timeSinceCHO-Reconfig* to the time elapsed between the initiation of the execution of conditional reconfiguration for the target PCell and the reception of the last *conditionalReconfiguration* including the *condRRCReconfig* of the target PCell in the source PCell; +- 3> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, for the target PCell indicated in the last applied *MobilityFromNRCommand* concerning an inter-RAT handover from NR to E-UTRA: + - 4> set the *targetPCellId* in *eutraTargetCellInfo* to the global cell identity and tracking area code, if available, of the target PCell; + - 4> set the *targetCellMeas* in *eutraTargetCellInfo* to include the cell level RSRP, RSRQ and the available SINR, of the target PCell based on the available measurements collected up to the moment the UE sends *RRCConnectionReconfigurationComplete* message; +- 3> if the procedure is triggered due to successful completion of reconfiguration with sync and if the ratio between the value of the elapsed time of the timer T304 and the configured value of the T304 timer, included in the last applied *RRCReconfiguration* message including the *reconfigurationWithSync*, is greater than *thresholdPercentageT304* if included in the *successHO-Config* received before executing the last reconfiguration with sync: + - 4> set *t304-cause* in *shr-Cause* to *true*; + - 4> set the *ra-InformationCommon* to include the random-access related information associated to the random access procedure in the target PCell, as specified in clause 5.7.10.5; + +- 3> if the ratio between the value of the elapsed time of the timer T310 and the configured value of the T310 timer, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync or the last Mobility from NR to E-UTRA, is greater than *thresholdPercentageT310* included in the *successHO-Config* if configured by the source PCell before executing the last reconfiguration with sync or Mobility from NR to E-UTRA: + - 4> set *t310-cause* in *shr-Cause* to *true*; +- 3> if the T312 associated to the measurement identity of the target cell was running at the time of initiating the execution of the reconfiguration with sync procedure or Mobility from NR to E-UTRA, and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the T312 timer, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync or Mobility from NR to E-UTRA, is greater than *thresholdPercentageT312* included in the *successHO-Config* if configured by the source PCell before executing the last reconfiguration with sync, or Mobility from NR to E-UTRA: + - 4> set *t312-cause* in *shr-Cause* to *true*; +- 3> if the procedure is triggered due to successful completion of reconfiguration with sync and if *sourceDAPS-FailureReporting* included in the *successHO-Config* if configured by the source PCell before executing the last reconfiguration with sync is set to *true*, and if the last executed handover was a DAPS handover and if an RLF occurred at the source PCell during the DAPS handover while T304 was running: + - 4> set *sourceDAPS-Failure* in *shr-Cause* to *true*; +- 3> if the procedure is triggered due to successful completion of reconfiguration with sync, for each of the *measObjectNR*, configured by the source PCell, in which the last *RRCReconfiguration* message including *reconfigurationWithSync* was applied; or: + - 3> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, for each of the *measObjectNR*, configured by the source PCell, in which the last *MobilityFromNRCommand* concerning an inter-RAT handover from NR to E-UTRA was applied: + - 4> if *measRSSI-ReportConfig* is configured for the frequency of the source PCell: + - 5> if the procedure is triggered due to successful completion of reconfiguration with sync: + - 6> set the *measResultServCell-RSSI* to the linear average of the available RSSI sample value(s) provided by lower layers for the frequency of the source PCell up to the moment the UE sends the *RRCReconfigurationComplete* message + - 5> else if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA: + - 6> set the *measResultServCell-RSSI* to the linear average of the available RSSI sample value(s) provided by lower layers for the frequency of the source PCell up to the moment the UE sends the EUTRA *RRCConnectionReconfigurationComplete* message; + - 4> for each of the configured *measObjectNR* if *measRSSI-ReportConfig* is configured for the configured frequency: + - 5> if the procedure is triggered due to successful completion of reconfiguration with sync: + - 6> set the *measResultNeighFreq-RSSI* in the *measResultNeighFreqList-RSSI* to the linear average of the available RSSI sample value(s) provided by lower layers for the associated neighbouring frequency up to the moment the UE sends the *RRCReconfigurationComplete* message; + - 5> else if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA: + - 6> set the *measResultNeighFreq-RSSI* in the *measResultNeighFreqList-RSSI* to the linear average of the available RSSI sample value(s) provided by lower layers for the associated neighbouring frequency up to the moment the UE sends the EUTRA *RRCConnectionReconfigurationComplete* message; + - 4> if measurements are available for the *measObjectNR*: + +5> if the SS/PBCH block-based measurement quantities are available: + +6> set the *measResultListNR* in *measResultNeighCells* to include all the available measurement quantities of the best measured cells, other than the source PCell or target PCell, ordered such that the cell with highest SS/PBCH block RSRP is listed first if SS/PBCH block RSRP measurement results are available, otherwise the cell with highest SS/PBCH block RSRQ is listed first if SS/PBCH block RSRQ measurement results are available, otherwise the cell with highest SS/PBCH block SINR is listed first, based on the available SS/PBCH block based measurements collected up to the moment the UE sends the *RRCReconfigurationComplete* message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA *RRCConnectionReconfigurationComplete* message if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA; + +6> for each neighbour cell included, include the optional fields that are available; + +NOTE 1: For the neighboring cells set included in *measResultListNR* in *measResultNeighCells* ordered based on the SS/PBCH block measurement quantities, the UE includes also the CSI-RS based measurement quantities, if available. + +5> if the CSI-RS measurement quantities are available: + +6> set the *measResultListNR* in *measResultNeighCells* to include all the available measurement quantities of the best measured cells, other than the source PCell and target PCell, ordered such that the cell with highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the cell with highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the cell with highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE sends the *RRCReconfigurationComplete* message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA *RRCConnectionReconfigurationComplete* message if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA; + +6> for each neighbour cell included, include the optional fields that are available; + +NOTE 2: For the neighboring cells set ordered based on the CSI-RS measurement quantities, the UE includes measurements only for the cells not yet included in *measResultListNR* in *measResultNeighCells* to avoid overriding SS/PBCH block-based ordered measurements. + +3> if the procedure is triggered due to successful completion of reconfiguration with sync, for each of the *measObjectEUTRA*, configured by the source PCell in which the last *RRCReconfiguration* message including *reconfigurationWithSync* was applied; or: + +3> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, for each of the *measObjectEUTRA*, configured by the source PCell in which the last *MobilityFromNRCommand* concerning an inter-RAT handover from NR to E-UTRA was applied: + +4> if measurements are available for the *measObjectEUTRA*: + +5> set the *measResultListEUTRA* in *measResultNeighCells* to include the best measured cells ordered such that the cell with highest RSRP is listed first if RSRP measurement results are available, otherwise the cell with highest RSRQ is listed first, based on measurements collected up to the moment the UE sends the *RRCReconfigurationComplete* message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA *RRCConnectionReconfigurationComplete* message if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA; + +5> for each neighbour cell included, include the optional fields that are available; + +3> for each of the neighbour cells included in *measResultNeighCells*: + +4> if the cell was a candidate target cell included in the *condRRCReconfig* within the *conditionalReconfiguration* configured by the source PCell, in which the last *RRCReconfiguration* message including *reconfigurationWithSync* was applied: + +5> set the *choCandidate* to *true* in *measResultNR*; + +3> if available, set the *locationInfo* as in 5.3.3.7; + +1> release *successHO-Config* configured by the source PCell and *thresholdPercentageT304* if configured by the target PCell. + +The UE may discard the successful handover information, i.e., release the UE variable *VarSuccessHO-Report*, 48 hours after the last successful handover information is added to the *VarSuccessHO-Report*. + +#### 5.7.10.7 Actions for the successful PSCell change or addition report determination + +The UE shall for the PSCell: + +- 1> if the ratio between the value of the elapsed time of the timer T304 and the configured value of the timer T304, included in the last applied *RRCREconfiguration* message for the SCG including the *reconfigurationWithSync*, is greater than *thresholdPercentageT304-SCG* if included in the *successPSCell-Config* received before executing the last reconfiguration with sync for the SCG; or +- 1> if *sn-InitiatedPSCellChange* is configured in the *RRCREconfiguration* including the last applied *RRCREconfiguration* with *reconfigurationWithSync* for the SCG and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync for the SCG, is greater than *thresholdPercentageT310-SCG* included in the *successPSCell-Config* if configured by the source PSCell before executing the last reconfiguration with sync; or +- 1> if *sn-InitiatedPSCellChange* is configured in the *RRCREconfiguration* including the last applied *RRCREconfiguration* with *reconfigurationWithSync* for the SCG and if the T312 associated to the measurement identity of the target PSCell was running at the time of initiating the execution of the reconfiguration with sync procedure for the SCG and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync, is greater than *thresholdPercentageT312-SCG* included in the *successPSCell-Config* if configured by the source PSCell before executing the last reconfiguration with sync; +- 1> if *sn-InitiatedPSCellChange* is not configured in the *RRCREconfiguration* including the last applied *RRCREconfiguration* with *reconfigurationWithSync* for the SCG and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync for the SCG, is greater than *thresholdPercentageT310-SCG* included in the *successPSCell-Config* if configured by the PCell before executing the last reconfiguration with sync; or +- 1> if *sn-InitiatedPSCellChange* is not configured in the *RRCREconfiguration* including the last applied *RRCREconfiguration* with *reconfigurationWithSync* for the SCG and if the T312 associated to the measurement identity of the target PSCell was running at the time of initiating the execution of the reconfiguration with sync procedure for the SCG and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync, is greater than *thresholdPercentageT312-SCG* included in the *successPSCell-Config* if configured by the PCell before executing the last reconfiguration with sync; +- 2> clear the information included in *VarSuccessPSCell-Report*, if any; +- 2> store the successful PSCell change or addition information in *VarSuccessPSCell-Report* and determine the content in *VarSuccessPSCell-Report* as follows: + - 3> if the UE is not in SNPN access mode, set the *plmn-IdentityList* to include the list of EPLMNs stored by the UE (i.e., includes the RPLMN); + - 3> else if the UE is in SNPN access mode, set the *snpn-IdentityList* to include the list of equivalent SNPNs stored by the UE (i.e., includes the registered SNPN), if available; + - 3> set the *pCellId* to the global cell identity and tracking area code, if available, of the PCell; + - 3> for the source PSCell (if available) in which the last *RRCREconfiguration* message for the SCG including *reconfigurationWithSync* was applied: + +- 4> set the *sourcePSCellId* in *sourcePSCellInfo* to the global cell identity and tracking area code, of the source PSCell; +- 4> set the *sourcePSCellMeas* in *sourcePSCellInfo* to include the cell level RSRP, RSRQ and the available SINR, of the source PSCell based on the available SSB and CSI-RS measurements collected up to the moment the UE successfully completed the random access procedure for the SCG; +- 4> set the *rsIndexResults* in *sourceCellMeas* to include all the available SSB and CSI-RS measurement quantities of the source PSCell collected up to the moment the UE successfully completed the random access procedure for the SCG; +- 3> for the target PSCell indicated in the last applied *RRReconfiguration* message for the SCG including *reconfigurationWithSync*: + - 4> set the *targetPSCellID* in *targetPSCellInfo* to the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the target PSCell; + - 4> set the *targetPSCellMeas* in *targetPSCellInfo* to include the cell level RSRP, RSRQ and the available SINR, of the target PSCell based on the available SSB and CSI-RS measurements collected up to the moment the UE successfully completed the random access procedure for the SCG; + - 4> set the *rsIndexResults* in *targetCellMeas* to include all the available SSB and CSI-RS measurement quantities of the target PSCell collected up to the moment the UE successfully completed the random access procedure for the SCG; + - 4> if the last applied *RRReconfiguration* message for the SCG including *reconfigurationWithSync* was included in the stored *condRRReconfig*: + - 5> set the *timeSinceCPAC-Reconfig* to the time elapsed between the initiation of the execution of conditional reconfiguration for the target PSCell and the reception of the last *conditionalReconfiguration* for the SCG including the *condRRReconfig* of the target PSCell; +- 3> if the ratio between the value of the elapsed time of the timer T304 and the configured value of the T304 timer, included in the last applied *RRReconfiguration* message for the SCG including the *reconfigurationWithSync*, is greater than *thresholdPercentageT304-SCG* if included in the *successPSCell-Config* received before executing the last reconfiguration with sync for the SCG: + - 4> set *t304-cause* in *spr-Cause* to *true*; + - 4> set the *ra-InformationCommon* to include the random-access related information associated to the random access procedure in the target PSCell, as specified in clause 5.7.10.5; +- 3> if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync for the SCG, is greater than *thresholdPercentageT310-SCG* included in the *successPSCell-Config* if configured before executing the last reconfiguration with sync: + - 4> set *t310-cause* in *spr-Cause* to *true*; +- 3> if the T312 associated to the measurement identity of the target PSCell was running at the time of initiating the execution of the reconfiguration with sync procedure for the SCG and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync, is greater than *thresholdPercentageT312-SCG* included in the *successPSCell-Config* if configured before executing the last reconfiguration with sync: + - 4> set *t312-cause* in *spr-Cause* to *true*; +- 3> if *sn-InitiatedPSCellChange* is configured in the *RRReconfiguration* including the last applied *RRReconfiguration* with *reconfigurationWithSync* for the SCG: + - 4> consider all *measObjectNR* configured by the the source PSCell; +- 3> else: + - 4> consider all *measObjectNR* configured by the the PCell; + +- 3> for each of the *measObjectNR*: + - 4> if measurements are available for the *measObjectNR*: + - 5> if the SS/PBCH block-based measurement quantities are available: + - 6> include in the *measResultListNR* in *measResultNeighCells* all the available measurement quantities of the best measured cells, other than the source PCell or target PCell, ordered such that the cell with highest SS/PBCH block RSRP is listed first if SS/PBCH block RSRP measurement results are available, otherwise the cell with highest SS/PBCH block RSRQ is listed first if SS/PBCH block RSRQ measurement results are available, otherwise the cell with highest SS/PBCH block SINR is listed first, based on the available SS/PBCH block based measurements collected up to the moment the UE successfully completed the random access procedure; + - 6> for each neighbour cell included, include the optional fields that are available (including the CSI-RS based measurement quantities, if available); + - 5> if the CSI-RS measurement quantities are available for the cells not yet included in *measResultListNR* in *measResultNeighCells*: + - 6> include in the *measResultListNR* in *measResultNeighCells* all the available measurement quantities of the best measured cells, other than the source PCell and target PCell, ordered such that the cell with highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the cell with highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the cell with highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE successfully completed the random access procedure; + - 6> for each neighbour cell included, include the optional fields that are available; + - 3> for each of the neighbour cells included in *measResultNeighCells*: + - 4> if the cell was a candidate target cell included in the *condRRReconfig* within the *conditionalReconfiguration*, in which the last *RRReconfiguration* message for the SCG including *reconfigurationWithSync* was applied: + - 5> set the *choCandidate* to *true* in *measResultNR*; + - 3> include *sn-InitiatedPSCellChange* if *sn-InitiatedPSCellChange* is included in the *RRReconfiguration* including the applied *RRReconfiguration* message with *reconfigurationWithSync* for the SCG; + - 3> if *sn-InitiatedPSCellChange* is configured in the *RRReconfiguration* including the last applied *RRReconfiguration* with *reconfigurationWithSync* for the SCG: + - 4> if available, set the *locationInfo* as in 5.3.3.7 7 according to the *otherConfig* associated with the source PCell; + - 3> else: + - 4> if available, set the *locationInfo* as in 5.3.3.7 7 according to the *otherConfig* associated with the PCell; +- 1> release *successPSCell-Config* configured by the source PCell if available and *thresholdPercentageT304* if configured by the target PCell. + +The UE may discard the successful PCell change or addition information, i.e., release the UE variable *VarSuccessPSCell-Report*, 48 hours after the last successful PCell change or addition information is added to the *VarSuccessPSCell-Report* or upon detaching from the network. + +### 5.7.11 Void + +### 5.7.12 IAB Other Information + +#### 5.7.12.1 General + +![Sequence diagram showing the IAB Other Information procedure. The diagram consists of two lifelines: IAB-MT and Network. A single message arrow labeled IABOtherInformation is shown from the IAB-MT lifeline to the Network lifeline.](ddee3e67e0dfc22e25188fa635a19558_img.jpg) + +``` + +sequenceDiagram + participant IAB-MT + participant Network + Note left of IAB-MT: IAB-MT + Note right of Network: Network + IAB-MT->>Network: IABOtherInformation + +``` + +Sequence diagram showing the IAB Other Information procedure. The diagram consists of two lifelines: IAB-MT and Network. A single message arrow labeled IABOtherInformation is shown from the IAB-MT lifeline to the Network lifeline. + +**Figure 5.7.12.1-1: IAB Other Information procedure** + +The IAB Other Information procedure is used by IAB-MT to request the IAB-donor-CU to allocate IP address or inform the IAB-donor-CU of the IP address for the collocated IAB-DU. + +#### 5.7.12.2 Initiation + +Upon initiation of the procedure, the IAB-MT shall: + +- 1> initiate transmission of the *IABOtherInformation* message in accordance with 5.7.12.3; + +#### 5.7.12.3 Actions related to transmission of *IABOtherInformation* message + +The IAB-MT shall set the contents of *IABOtherInformation* message as follows: + +- 1> if the procedure is used to request IP addresses: + - 2> if IPv4 addresses are requested: + - 3> set the *iab-IPv4-AddressNumReq* to the number of IPv4 addresses requested per specific usage; + - 2> if IPv6 addresses or IPv6 address prefixes are requested: + - 3> if IPv6 addresses are requested: + - 4> set the *iab-IPv6-AddressNumReq* to the number of IPv6 addresses requested per specific usage; + - 3> else if IPv6 address prefixes are requested: + - 4> set the *iab-IPv6-AddressPrefixReq* to *true* per specific usage; +- 1> if the procedure is used to report IP addresses: + - 2> if IPv4 addresses are reported: + - 3> include *iIPv4-Address* in *iab-IPv4-AddressReport*, and for each IP address included: + - 4> if IPv4 addresses are used for F1-C traffic: + - 5> include these addresses in *f1-C-Traffic-IP-Address*. + - 4> if IPv4 addresses are used for F1-U traffic: + - 5> include these addresses in *f1-U-Traffic-IP-Address*. + - 4> if IPv4 address are used for non-F1 traffic: + - 5> include these addresses in *non-f1-Traffic-IP-Address*. + +- 4> if IPv4 addresses are used for all traffic: + - 5> include these addresses in *all-Traffic-IAB-IP-Address*. + - 2> if IPv6 addresses or IPv6 address prefixes are reported: + - 3> if IPv6 addresses are reported: + - 4> include *iPv6-Address* in *iab-IPv6-AddressReport*, and for each IP address included; + - 5> if IPv6 addresses are used for F1-C traffic: + - 6> include these addresses in *f1-C-Traffic-IP-Address*. + - 5> if IPv6 addresses are used for F1-U traffic: + - 6> include these addresses in *f1-U-Traffic-IP-Address*. + - 5> if IPv6 addresses are used for non-F1 traffic: + - 6> include these addresses in *non-f1-Traffic-IP-Address*. + - 5> if IPv6 addresses are used for all traffic: + - 6> include these addresses in *all-Traffic-IAB-IP-Address*. + - 3> else if IPv6 address prefixes are reported: + - 4> include these *iPv6-Prefix* in *iab-IPv6-PrefixReport*, and for each IP address prefix included; + - 5> if this IPv6 address prefix is used for F1-C traffic: + - 6> include this prefix in *f1-C-Traffic-IP-Address*. + - 5> if this IPv6 address prefix is used for F1-U traffic: + - 6> include this prefix in *f1-U-Traffic-IP-Address*. + - 5> if this IPv6 address prefix is used for non-F1 traffic: + - 6> include this prefix in *non-f1-Traffic-IP-Address*. + - 5> if this IPv6 address prefix is used for all traffic: + - 6> include this prefix in *all-Traffic-IAB-IP-Address*. +- 1> if the IAB-MT is in (NG)EN-DC, or +- 1> if the IAB-MT is in NR-DC and the IAB Other Information procedure is towards the IAB-donor-CU in the SN: + - 2> if SRB3 is configured: + - 3> submit the *IABOtherInformation* message via SRB3 to lower layers for transmission; + - 2> else if the IAB-MT is in (NG)EN-DC: + - 3> submit the *IABOtherInformation* message via the E-UTRA MCG embedded in E-UTRA RRC message *ULInformationTransferMRDC* as specified in TS 36.331 [10]; + - 2> else: + - 3> submit the *IABOtherInformation* message via the NR MCG embedded in NR RRC message *ULInformationTransferMRDC* as specified in clause 5.7.2a.3; +- 1> else: + - 2> submit the *IABOtherInformation* message to lower layers for transmission. + +### 5.7.13 RLM/BFD relaxation + +In case both low mobility criterion and good serving cell criterion are configured for RLM/BFD relaxation, the UE is allowed to perform RLM and/or BFD relaxation according to requirements specified in TS 38.133 [14] when both relaxed measurement criterion for low mobility and relaxed measurement criterion for good serving cell quality are met. + +In case only the good serving cell quality criterion is configured for RLM/BFD relaxation, the UE is allowed to perform RLM and/or BFD relaxation according to requirements specified in TS 38.133 [14] when the relaxed measurement criterion for good serving cell quality is met. + +#### 5.7.13.1 Relaxed measurement criterion for low mobility + +The relaxed measurement criterion for UE with low mobility in RRC\_CONNECTED is fulfilled when: + +- $(\text{SS-RSRP}_{\text{Ref}} - \text{SS-RSRP}) < S_{\text{SearchDeltaP-Connected}}$ , + +Where: + +- SS-RSRP = current L3 RSRP measurement of the SpCell based on SSB (dB). +- SS-RSRPRef = reference L3 RSRP measurement of the SpCell based on SSB (dB), set as follows: + - After receiving low mobility criterion configuration, or + - After MAC of the CG successfully completes a Random Access procedure after applying a *reconfigurationWithSync* in *spCellConfig* of the CG while low mobility criterion is configured, or + - If $(\text{SS-RSRP} - \text{SS-RSRP}_{\text{Ref}}) > 0$ , or + - If the relaxed measurement criterion has not been met for $T_{\text{SearchDeltaP-Connected}}$ : + - The UE shall set the value of SS-RSRPRef to the current SS-RSRP value of the SpCell. + +#### 5.7.13.2 Relaxed measurement criterion for good serving cell quality + +The relaxed measurement criterion of good serving cell quality for RLM is fulfilled when the downlink radio link quality on the configured RLM-RS resource is evaluated to be better than the threshold $Q_{\text{in}} + X\text{dB}$ , wherein + +- $Q_{\text{in}}$ is specified in clause 8.1 of TS 38.133 [14]. +- X is the parameter *offset* in *goodServingCellEvaluationRLM* for the evaluated serving cell. + +The relaxed measurement criterion of good serving cell quality for BFD is fulfilled when the downlink radio link quality on the configured BFD-RS resource is evaluated to be better than the threshold $Q_{\text{in}} + X\text{dB}$ , wherein + +- $Q_{\text{in}}$ is specified in clause 8.1 of TS 38.133 [14]. +- X is the parameter *offset* in *goodServingCellEvaluationBFD* for the evaluated serving cell. + +### 5.7.14 UE Positioning Assistance Information + +#### 5.7.14.1 General + +![Sequence diagram showing the UE Positioning Assistance Information procedure. The diagram consists of two vertical lifelines: UE and Network. The UE sends an RRC Reconfiguration message to the Network. The Network responds with a UEPositioningAssistanceInfo message to the UE.](edcb05fc7c8056bf485bf8adeb45e1c8_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Network + Note left of UE: + UE->>Network: RRC Reconfiguration + Network-->>UE: UEPositioningAssistanceInfo + +``` + +Sequence diagram showing the UE Positioning Assistance Information procedure. The diagram consists of two vertical lifelines: UE and Network. The UE sends an RRC Reconfiguration message to the Network. The Network responds with a UEPositioningAssistanceInfo message to the UE. + +Figure 5.7.14.1-1: UE Positioning Assistance Information procedure + +The UE Positioning Assistance Information procedure is used by UE to report the UE Positioning Assistance Information. The UE reports the association between SRS resources for positioning and the UE Tx TEG ID as defined in TS 38.305 [73]. + +#### 5.7.14.2 Initiation + +A UE capable of providing the association between SRS resource for positioning and UE Tx TEG ID in RRC\_CONNECTED may initiate the procedure upon being configured to provide this association information. + +Upon initiation of the procedure, the UE shall: + +- 1> initiate transmission of the *UEPositioningAssistanceInfo* message in accordance with 5.7.14.3 to provide the association. + +#### 5.7.14.3 Actions related to transmission of *UEPositioningAssistanceInfo* message + +The UE shall set the contents of the *UEPositioningAssistanceInfo* message as follows: + +- 1> if *ue-TxTEG-RequestUL-TDOA-Config* in *RRCReconfiguration* message is configured with *periodicReporting*: + - 2> for all the association changes store *ue-TxTEG-Association* corresponding to each *ue-TxTEG-ID* with *nr-TimeStamp*; + - 2> include the results in *ue-TxTEG-AssociationList* in the *UEPositioningAssistanceInfo* message on expiry of each configured period; + - 2> optionally include one *ue-TxTEG-TimingErrorMarginValue* for each *UEPositioningAssistanceInfo* message; +- 1> else if *ue-TxTEG-RequestUL-TDOA-Config* in *RRCReconfiguration* message is configured with *oneShot*: + - 2> identify the *ue-TxTEG-Association* corresponding to each *ue-TxTEG-ID* with *nr-TimeStamp*; + - 2> include the results in *ue-TxTEG-AssociationList* in the *UEPositioningAssistanceInfo* message only one time; + - 2> optionally include one *ue-TxTEG-TimingErrorMarginValue* for each *UEPositioningAssistanceInfo* message. + +The UE shall submit the *UEPositioningAssistanceInfo* message to lower layers for transmission. + +### 5.7.15 Void + +### 5.7.16 Application layer measurement reporting + +#### 5.7.16.1 General + +![Sequence diagram showing application layer measurement reporting between UE and Network. The UE sends an RRC reconfiguration message to the Network, and then the Network sends a MeasurementReportAppLayer message back to the UE.](2beb95006f1933bed737cfe1e6598db8_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Network + Note left of UE: + UE->>Network: RRC reconfiguration + Note right of Network: + Network-->>UE: MeasurementReportAppLayer + +``` + +Sequence diagram showing application layer measurement reporting between UE and Network. The UE sends an RRC reconfiguration message to the Network, and then the Network sends a MeasurementReportAppLayer message back to the UE. + +Figure 5.7.16.1-1: Application layer measurement reporting + +The purpose of this procedure is to send application layer measurement reports to the network. + +#### 5.7.16.2 Initiation + +A UE capable of application layer measurement reporting in RRC\_CONNECTED may initiate the procedure when configured with application layer measurement, i.e. when *appLayerMeasConfig* and SRB4 and/or SRB5 have been configured by the network. + +Upon initiating the procedure, the UE shall: + +- 1> for each *measConfigAppLayerId* received from upper layers: + - 2> if the UE AS has received application layer measurement report container from upper layers which has not been transmitted; and + - 2> if the application layer measurement reporting has not been suspended for the *measConfigAppLayerId* associated with the application layer measurement report container according to clause 5.3.5.13d: + - 3> set the *measReportAppLayerContainer* in the *MeasurementReportAppLayer* message to the received value in the application layer measurement report container; + - 2> set the *measConfigAppLayerId* in the *MeasurementReportAppLayer* message to the value of the *measConfigAppLayerId* received together with application layer measurement report information; + - 2> if session start or stop information has been received from upper layers for the *measConfigAppLayerId*: + - 3> set the *appLayerSessionStatus* in the *MeasurementReportAppLayer* message to the received value of session start or stop information; + - 2> if *reportingSRB* and *ran-VisibleReportingSRB* are different for the *measConfigAppLayerId*: + - 3> include *measReportAppLayerContainer* and *appLayerSessionStatus* in a different *MeasurementReportAppLayer* message than *ran-VisibleMeasurements*; + - 2> if RAN visible application layer measurement report has been received from upper layers: + - 3> for each *appLayerBufferLevel* value in the received RAN visible application layer measurement report: + - 4> set the *appLayerBufferLevel* values in the *appLayerBufferLevelList* in the *MeasurementReportAppLayer* message to the buffer level values received from the upper layer in the order with the first *appLayerBufferLevel* value set to the newest received buffer level value, the second *appLayerBufferLevel* value set to the second newest received buffer level value, and so on until all the buffer level values received from the upper layer have been assigned or the maximum number of values have been set according to *appLayerBufferLevel*, if configured; + - 3> set the *playoutDelayForMediaStartup* in the *MeasurementReportAppLayer* message to the received value of playout delay for media startup in the RAN visible application layer measurement report, if any; + - 3> for each PDU session ID value indicated in the received RAN visible application layer measurement report, if any: + - 4> set the *PDU-SessionID* in the *pdu-SessionIdList* in the *MeasurementReportAppLayer* message to the indicated PDU session ID value; + - 4> for each QoS Flow ID value indicated in the received RAN visible application layer measurement report associated with the PDU Session ID, if any: + - 5> set the *QFI* associated with the PDU session ID to the indicated QoS Flow ID value. +- 1> for each stored application layer measurement configuration with *configforRRC-IdleInactive* set to *true* and for which *appLayerIdleInactiveConfig* has not been transmitted since the UE entered RRC\_CONNECTED: + - 2> set the parameters in *appLayerIdleInactiveConfig* in the *MeasurementReportAppLayer* message to the values stored in the UE variable *VarAppLayerIdleConfig*; +- 1> for each encoded *MeasurementReportAppLayer* message generated above: + - 2> if *reportingSRB* or *ran-VisibleReportingSRB* are not configured: + +- 3> if the encoded RRC message is larger than the maximum supported size of one PDCP SDU specified in TS 38.323 [5]: + - 4> if the RRC message segmentation is enabled based on the field *rrc-SegAllowed* received in *appLayerMeasConfig*: + - 5> initiate the UL message segment transfer procedure as specified in clause 5.7.7; + - 4> else: + - 5> discard the RRC message; +- 3> else: + - 4> submit the *MeasurementReportAppLayer* message to lower layers for transmission. +- 2> else if *reportingSRB* or *ran-VisibleReportingSRB* are configured: + - 3> if the encoded RRC message is larger than the maximum supported size of one PDCP SDU specified in TS 38.323 [5]: + - 4> if the RRC message segmentation is enabled based on the field *rrc-SegAllowedSRB4* received in *appLayerMeasConfig* and the *reportingSRB* is SRB4; or + - 4> if the RRC message segmentation is enabled based on the field *rrc-SegAllowedSRB5* received in *appLayerMeasConfig* and the *reportingSRB* is SRB5: + - 5> initiate the UL message segment transfer procedure as specified in clause 5.7.7 via the SRB indicated in the field *reportingSRB* in *MeasConfigAppLayer*; + - 4> else: + - 5> discard the RRC message; + - 3> else: + - 4> submit the *MeasurementReportAppLayer* message to lower layers for transmission via the SRB indicated in the field *reportingSRB* or, if different from *reportingSRB*, *ran-VisibleReportingSRB* in *MeasConfigAppLayer* upon which the procedure ends. + +Editor's Note: FFS on if it needs to be specified what the UE transmits when returning to RRC\_CONNECTED. + +NOTE 1: If the SRB indicated by *reportingSRB* is not available, the UE may store application layer measurement report containers until the SRB is available. The UE may discard reports when the memory reserved for storing application layer measurement report containers becomes full. Reports with lower *appLayerMeasPriority* are discarded first. If no *appLayerMeasPriority* is configured, older reports may be discarded first. + +NOTE 2: If the SRB indicated by *ran-VisibleReportingSRB* is not available, the UE discards RAN visible application layer measurement reports. + +### 5.7.17 Derivation of pathloss reference for TA validation of SRS for Positioning transmission and CG-SDT in RRC\_INACTIVE + +Upon request from lower layer for pathloss reference derivation for TA validation for SRS for Positioning transmission or CG-SDT in RRC\_INACTIVE, the UE shall: + +- 1> acquire *SIB2*, if stored version is invalid; +- 1> if *nrofSS-BlocksToAverage* or *absThreshSS-BlocksConsolidation* is not present or if *absThreshSS-BlocksConsolidation* is present and the highest beam measurement quantity value is below or equal to *absThreshSS-BlocksConsolidation*: +- 2> derive the downlink pathloss reference RSRP for TA validation as the highest beam measurement quantity value, where each beam measurement quantity is described in TS 38.215 [24]; + +1> else: + +2> derive the downlink pathloss reference RSRP for TA validation as the linear average of the power values of up to *nrofSS-BlocksToAverage* of the highest beam measurement quantity values above *absThreshSS-BlocksConsolidation*, where each beam measurement quantity is described in TS 38.215 [24]. + +### 5.7.18 Actions for SRS for Positioning transmission in RRC\_INACTIVE in a Validity Area + +The UE may be configured or preconfigured with SRS for Positioning in a validity area defined by group of cells. There can be multiple preconfigured SRS for positioning that can be configured to UE where each preconfiguration belongs to different validity area. For each validity area, the UE is preconfigured with only one SRS for positioning configuration. For non-preconfigured SRS for positioning, only one validity area is configured. + +When the UE is (pre)configured to transmit SRS for positioning in a validity area, the UE shall: + +- 1> if the RS in *spatialRelationInfoPos* cannot be accurately measured: + - 2> suspend the transmission of the SRS for positioning resource and monitor the configured RS; +- 2> if the UE determines that RS in *spatialRelationInfoPos* being accurately measured: + - 3> resume the SRS transmission. + +The UE releases the (pre)configured SRS for positioning with validity area upon receiving *RRCRelease* message with the indication to release the (pre)configuration. + +### 5.7.19 Satellite switch with re-synchronization in RRC\_CONNECTED + +The UE shall: + +- 1> stop timer T430 if running; +- 1> inform lower layers that UL synchronisation is lost due to satellite switch with re-synchronization; +- 1> start re-synchronising to the DL of the SpCell served by the satellite indicated by *ntn-Config* in *SatSwitchWithReSync*; +- 1> start timer T430 with the timer value set to *ntn-ULSyncValidityDuration* from the subframe indicated by *epochTime* in *ntn-Config* in *SatSwitchWithReSync*; +- 1> inform lower layers when UL synchronisation is obtained. + +Editor's Note: FFS whether in the soft-switch scenario a UE can obtain DL synchronization from the target satellite without losing UL synchronization to the source satellite. + +## 5.8 Sidelink + +### 5.8.1 General + +NR sidelink communication consists of unicast, groupcast and broadcast. For unicast, the PC5-RRC connection is a logical connection between a pair of a Source Layer-2 ID and a Destination Layer-2 ID in the AS. The PC5-RRC signalling, as specified in clause 5.8.9, can be initiated after its corresponding PC5 unicast link establishment (TS 23.287 [55]). The PC5-RRC connection and the corresponding sidelink SRBs and sidelink DRB(s) are released when the PC5 unicast link is released as indicated by upper layers. + +For each PC5-RRC connection of unicast, one sidelink SRB (i.e. SL-SRB0) is used to transmit the PC5-S message(s) before the PC5-S security has been established. One sidelink SRB (i.e. SL-SRB1) is used to transmit the PC5-S messages to establish the PC5-S security. One sidelink SRB (i.e. SL-SRB2) is used to transmit the PC5-S messages after the PC5-S security has been established, which is protected. One sidelink SRB (i.e. SL-SRB3) is used to transmit the PC5-RRC signalling, which is protected and only sent after the PC5-S security has been established. One sidelink SRB (i.e. SL-SRB4) is used to transmit/receive the NR sidelink discovery messages. + +For unicast of NR sidelink communication, AS security comprises of integrity protection of PC5 signalling (SL-SRB1, SL-SRB2 and SL-SRB3) and user data (SL-DRBs), and it further comprises of ciphering of PC5 signaling (SL-SRB1 only for the Direct Link Security Mode Complete message as specified in TS 24.587 [57] for V2X service or TS 24.554 [72] for Proximity-services, SL-SRB2 and SL-SRB3) and user data (SL-DRBs). The ciphering and integrity protection algorithms and parameters for a PC5 unicast link are exchanged by PC5-S messages in the upper layers as specified in TS 33.536 [60], and applied to the corresponding PC5-RRC connection in the AS. Once AS security is activated for a PC5 unicast link in the upper layers as specified in TS 33.536 [60], all messages on SL-SRB2 and SL-SRB3 and/or user data on SL-DRBs of the corresponding PC5-RRC connection are integrity protected and/or ciphered by the PDCP. + +For unicast of NR sidelink communication, if the change of the key is indicated by the upper layers as specified in TS 24.587 [57] or TS 24.554 [72], UE re-establishes the PDCP entity of the SL-SRB1, SL-SRB2, SL-SRB3 and SL-DRBs on the corresponding PC5-RRC connection. + +- NOTE 1: In case the configurations for NR sidelink communication are acquired via the E-UTRA, the configurations for NR sidelink communication in *SIB12* and *sl-ConfigDedicatedNR* within *RRCReconfiguration* used in clause 5.8 are provided by the configurations in *SystemInformationBlockType28* and *sl-ConfigDedicatedForNR* within *RRCConnectionReconfiguration* as specified in TS 36.331 [10], respectively. +- NOTE 2: In this release, there is one-to-one correspondence between the PC5-RRC connection and the PC5 unicast link as specified in TS 38.300[2]. +- NOTE 3: All SL-DRBs related to the same PC5-RRC connection have the same activation/deactivation setting for ciphering and the same activation/deactivation setting for integrity protection as specified in TS 33.536 [60]. +- NOTE 4: When integrity check failure concerning SL-SRB1 for a specific destination is detected, the UE sends an indication to the upper layers [57]. +- NOTE 5: The selection of NULL algorithms means that the PC5 messages are considered protected for the purposes of being allowed to be sent or received. + +### 5.8.2 Conditions for NR sidelink communication/discovery/positioning operation + +The UE shall perform NR sidelink communication/positioning operation only if the conditions defined in this clause are met: + +- 1> if the UE's serving cell is suitable (RRC\_IDLE or RRC\_INACTIVE or RRC\_CONNECTED); and if either the selected cell on the frequency used for NR sidelink communication/discovery/positioning operation belongs to the registered or equivalent PLMN as specified in TS 24.587 [57] or TS 24.554 [72] or the UE is out of coverage on the frequency used for NR sidelink communication/discovery/positioning operation as defined in TS 38.304 [20] and TS 36.304 [27]; or +- 1> if the UE's serving cell (RRC\_IDLE or RRC\_CONNECTED) fulfils the conditions to support NR sidelink communication/discovery/positioning in limited service state as specified in TS 23.287 [55]; and if either the serving cell is on the frequency used for NR sidelink communication/discovery/positioning operation or the UE is out of coverage on the frequency used for NR sidelink communication/discovery/positioning operation as defined in TS 38.304 [20] and TS 36.304 [27]; or +- 1> if the UE has no serving cell (RRC\_IDLE). + +### 5.8.3 Sidelink UE information for NR sidelink communication/discovery/positioning + +#### 5.8.3.1 General + +![Sequence diagram showing the interaction between a UE and a Network for Sidelink UE information. The UE sends a 'SIB12/XX acquisition' message to the Network, and the Network responds with 'SidelinkUEInformationNR'.](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Network + Note left of UE: + UE->>Network: SIB12/XX acquisition + Network-->>UE: SidelinkUEInformationNR + +``` + +Sequence diagram showing the interaction between a UE and a Network for Sidelink UE information. The UE sends a 'SIB12/XX acquisition' message to the Network, and the Network responds with 'SidelinkUEInformationNR'. + +**Figure 5.8.3.1-1: Sidelink UE information for NR sidelink communication/discovery** + +The purpose of this procedure is to inform the network that the UE: + +- is interested or no longer interested to receive or transmit NR sidelink communication/discovery/positioning, +- is requesting assignment or release of transmission resource for NR sidelink communication/discovery/positioning, +- is reporting QoS parameters and QoS profile(s) related to NR sidelink communication, +- is reporting mapped frequency(ies) for each QoS flow related to NR sidelink communication, +- is reporting associated Tx Profile for each QoS flow related to NR sidelink communication, +- is reporting that a sidelink radio link failure, sidelink RRC reconfiguration failure or a sidelink carrier failure has been detected, +- is reporting the sidelink UE capability information of the associated peer UE for unicast communication, +- is reporting the RLC mode information of the sidelink data radio bearer(s) received from the associated peer UE for unicast communication, +- is reporting the accepted sidelink DRX configuration received from the associated peer UE for NR sidelink unicast reception, +- is reporting the sidelink DRX assistance information received from the associated peer UE for NR sidelink unicast transmission, when the UE is configured with *sl-ScheduledConfig*, +- is reporting, for NR sidelink groupcast transmission, the sidelink DRX on/off indication for the associated Destination Layer-2 ID, when the UE is configured with *sl-ScheduledConfig*, +- is reporting, for NR sidelink groupcast or broadcast reception, the Destination Layer-2 ID and QoS profile(s) associated with its interested services to which sidelink DRX is applied, +- is reporting DRX configuration reject information from its associated peer UE for NR sidelink unicast transmission, when the UE is configured with *sl-ScheduledConfig*, +- is reporting parameters related to U2N relay operation, +- is reporting parameters related to U2U relay operation. + +#### 5.8.3.2 Initiation + +A UE capable of NR sidelink communication or NR sidelink discovery or NR sidelink U2N relay operation or NR sidelink U2U relay operation or NR sidelink positioning that is in *RRc\_CONNECTED* may initiate the procedure to indicate it is (interested in) receiving or transmitting NR sidelink communication or NR sidelink discovery or NR sidelink U2N relay operation or NR sidelink U2U relay operation or SL-PRS transmission/reception in several cases including upon successful connection establishment or resuming, upon change of interest, upon changing QoS + +profile(s), upon receiving *UECapabilityInformationSidelink* from the associated peer UE, upon RLC mode information updated from the associated peer UE or upon change to a PCell providing *SIB12* including *sl-ConfigCommonNR*, or upon change to a PCell providing *SIB23* including *sl-PosConfigCommonNR*. A UE capable of NR sidelink communication may initiate the procedure to request assignment of dedicated sidelink DRB configuration and transmission resources for NR sidelink communication transmission. A UE capable of NR sidelink communication may initiate the procedure to report to the network that a sidelink radio link failure, sidelink RRC reconfiguration failure or sidelink carrier failure has been declared. A UE capable of NR sidelink discovery may initiate the procedure to request assignment of dedicated resources for NR sidelink discovery transmission or NR sidelink discovery reception. A UE capable of U2N relay operation may initiate the procedure to report/update parameters for acting as U2N Relay UE or U2N Remote UE (including L2 Remote UE's source L2 ID). A UE capable of U2U relay operation may initiate the procedure to report/update parameters for acting as U2U Relay UE or U2U Remote UE. A UE capable of NR sidelink positioning may initiate the procedure to request it is interested or no longer interested in either transmitting SL-PRS or receiving sidelink control information for SL-PRS. + +A UE capable of NR sidelink operation that is in RRC\_CONNECTED may initiate the procedure to report the sidelink DRX configuration received from the associated peer UE for NR sidelink unicast reception, upon accepting the sidelink DRX configuration from the associated peer UE. A UE capable of NR sidelink communication that is configured with *sl-ScheduledConfig* and is performing sidelink unicast transmission may initiate the procedure to report the sidelink DRX assistance information or the sidelink DRX configuration reject information received from the associated peer UE, upon receiving either of them from the associated peer UE. A UE capable of NR sidelink communication that is configured with *sl-ScheduledConfig* and is performing sidelink groupcast transmission may initiate the procedure to report the sidelink DRX on/off indication for the associated Destination Layer-2 ID. + +A UE capable of NR sidelink operation that is in RRC\_CONNECTED may initiate the procedure to report the Destination Layer-2 ID and QoS profile(s) associated with its interested service(s) that sidelink DRX is applied, for NR sidelink groupcast or broadcast reception. + +Upon initiating this procedure, the UE shall: + +- 1> if *SIB12* including *sl-ConfigCommonNR* is provided by the PCell: + - 2> ensure having a valid version of *SIB12* for the PCell; + - 2> if configured by upper layers to receive NR sidelink communication on the frequency included in *sl-FreqInfoList/sl-FreqInfoListSizeExt* in *SIB12* of the PCell: + - 3> if the UE did not transmit a *SidelinkUEInformationNR* message since last entering RRC\_CONNECTED state; or + - 3> if since the last time the UE transmitted a *SidelinkUEInformationNR* message the UE connected to a PCell not providing *SIB12* including *sl-ConfigCommonNR*; or + - 3> if the last transmission of the *SidelinkUEInformationNR* message did not include *sl-RxInterestedFreqList*; or if the frequency configured by upper layers to receive NR sidelink communication on has changed since the last transmission of the *SidelinkUEInformationNR* message: + - 4> initiate transmission of the *SidelinkUEInformationNR* message to indicate the NR sidelink communication reception frequency of interest in accordance with 5.8.3.3; + - 2> else: + - 3> if the last transmission of the *SidelinkUEInformationNR* message included *sl-RxInterestedFreqList*: + - 4> initiate transmission of the *SidelinkUEInformationNR* message to indicate it is no longer interested in NR sidelink communication reception in accordance with 5.8.3.3; + - 2> if configured by upper layers to transmit non-relay NR sidelink communication on the frequency included in *sl-FreqInfoList/sl-FreqInfoListSizeExt* in *SIB12* of the PCell; or + - 2> if configured by upper layer to transmit NR sidelink L3 U2U relay communication on the frequency included in *sl-FreqInfoList* in *SIB12* of the PCell including [*FFS gNB capability indication*]: + - 3> if the UE did not transmit a *SidelinkUEInformationNR* message since last entering RRC\_CONNECTED state; or + +- 3> if since the last time the UE transmitted a *SidelinkUEInformationNR* message the UE connected to a PCell not providing *SIB12* including *sl-ConfigCommonNR*; or +- 3> if the last transmission of the *SidelinkUEInformationNR* message did not include *sl-TxResourceReqList*; or if the information carried by the *sl-TxResourceReqList* has changed since the last transmission of the *SidelinkUEInformationNR* message: + - 4> initiate transmission of the *SidelinkUEInformationNR* message to indicate the NR sidelink communication transmission resources required by the UE in accordance with 5.8.3.3; +- 2> else: + - 3> if the last transmission of the *SidelinkUEInformationNR* message included *sl-TxResourceReqList*: + - 4> initiate transmission of the *SidelinkUEInformationNR* message to indicate it no longer requires NR sidelink communication transmission resources in accordance with 5.8.3.3; + - 2> if configured by upper layer to receive NR sidelink non-relay discovery messages on the frequency included in *sl-FreqInfoList* in *SIB12* of the PCell including *sl-NonRelayDiscovery*: + - 3> if the UE did not transmit a *SidelinkUEInformationNR* message since last entering RRC\_CONNECTED state; or + - 3> if since the last time the UE transmitted a *SidelinkUEInformationNR* message the UE connected to a PCell not providing *SIB12* including *sl-ConfigCommonNR* or connected to a PCell providing *SIB12* but not including *sl-NonRelayDiscovery*; or + - 3> if the last transmission of the *SidelinkUEInformationNR* message did not include *sl-RxInterestedFreqListDisc*; or if the frequency configured by upper layers to receive NR sidelink non-relay discovery messages on has changed since the last transmission of the *SidelinkUEInformationNR* message: + - 4> initiate transmission of the *SidelinkUEInformationNR* message to indicate the NR sidelink discovery reception frequency of interest in accordance with 5.8.3.3; + - 2> else: + - 3> if the last transmission of the *SidelinkUEInformationNR* message included *sl-RxInterestedFreqListDisc*: + - 4> initiate transmission of the *SidelinkUEInformationNR* message to indicate it is no longer interested in NR sidelink non-relay discovery messages reception in accordance with 5.8.3.3; + - 2> if configured by upper layer to receive NR sidelink L2 U2N relay discovery messages on the frequency included in *sl-FreqInfoList* in *SIB12* of the PCell including *sl-L2U2N-Relay*; or if configured by upper layer to receive NR sidelink L3 U2N relay discovery messages on the frequency included in *sl-FreqInfoList* in *SIB12* of the PCell including *sl-L3U2N-RelayDiscovery*; + - 2> or if configured by upper layer to receive NR sidelink U2U relay discovery messages on the frequency included in *sl-FreqInfoList* in *SIB12* of the PCell including [*FFS gNB capability indication*]: + - 3> if the UE did not transmit a *SidelinkUEInformationNR* message since last entering RRC\_CONNECTED state; or + - 3> if since the last time the UE transmitted a *SidelinkUEInformationNR* message the UE connected to a PCell not providing *SIB12* including *sl-ConfigCommonNR*; or connected to a PCell providing *SIB12* but not including *sl-L2U2N-Relay* in case of L2 U2N relay operation; or connected to a PCell providing *SIB12* but not including *sl-L3U2N-RelayDiscovery* in case of L3 U2N relay operation; or + - 3> if since the last time the UE transmitted a *SidelinkUEInformationNR* message the UE connected to a PCell providing *SIB12* but not including [*FFS gNB capability indication*] in case of U2U relay operation; or + - 3> if the last transmission of the *SidelinkUEInformationNR* message did not include *sl-RxInterestedFreqListDisc*; or if the frequency configured by upper layers to receive NR sidelink discovery messages on has changed since the last transmission of the *SidelinkUEInformationNR* message: + - 4> initiate transmission of the *SidelinkUEInformationNR* message to indicate it is no longer interested in NR sidelink non-relay discovery messages reception in accordance with 5.8.3.3; + +- 4> if the UE is capable of U2N Relay UE, and if *SIB12* includes *sl-RelayUE-ConfigCommon*; or +- 4> if the UE is selecting a U2N Relay UE / has a selected U2N Relay UE, and if *SIB12* includes *sl-RemoteUE-ConfigCommon*; or +- 4> if the UE is capable of U2U Relay UE, and if *SIB12* includes *sl-RelayUE-ConfigCommonU2U*; or +- 4> if the UE is selecting a U2U Relay UE / has a selected U2U Relay UE, and if *SIB12* includes *sl-RemoteUE-ConfigCommonU2U*: + - 5> initiate transmission of the *SidelinkUEInformationNR* message to indicate the NR relay sidelink discovery reception frequency of interest in accordance with 5.8.3.3; +- 2> else: + - 3> if the last transmission of the *SidelinkUEInformationNR* message included *sl-RxInterestedFreqListDisc*: + - 4> initiate transmission of the *SidelinkUEInformationNR* message to indicate it is no longer interested in NR relay sidelink discovery messages reception in accordance with 5.8.3.3; + - 2> if configured by upper layer to transmit NR sidelink non-relay discovery messages on the frequency included in *sl-FreqInfoList* in *SIB12* of the PCell including *sl-NonRelayDiscovery*: + - 3> if the UE did not transmit a *SidelinkUEInformationNR* message since last entering RRC\_CONNECTED state; or + - 3> if since the last time the UE transmitted a *SidelinkUEInformationNR* message the UE connected to a PCell not providing *SIB12* including *sl-ConfigCommonNR* or connected to a PCell providing *SIB12* but not including *sl-NonRelayDiscovery*; or + - 3> if the last transmission of the *SidelinkUEInformationNR* message did not include *sl-TxResourceReqListDisc*; or if the information carried by the *sl-TxResourceReqListDisc* has changed since the last transmission of the *SidelinkUEInformationNR* message: + - 4> initiate transmission of the *SidelinkUEInformationNR* message to indicate the NR sidelink non-relay discovery messages resources required by the UE in accordance with 5.8.3.3; + - 2> else: + - 3> if the last transmission of the *SidelinkUEInformationNR* message included *sl-TxResourceReqListDisc*: + - 4> initiate transmission of the *SidelinkUEInformationNR* message to indicate it no longer requires NR sidelink non-relay discovery messages resources in accordance with 5.8.3.3; + - 2> if configured by upper layer to transmit NR sidelink L2 U2N relay discovery messages on the frequency included in *sl-FreqInfoList* in *SIB12* of the PCell including *sl-L2U2N-Relay*; or if configured by upper layer to transmit NR sidelink L3 U2N relay discovery messages on the frequency included in *sl-FreqInfoList* in *SIB12* of the PCell including *sl-L3U2N-RelayDiscovery*; or + - 2> if configured by upper layer to transmit NR sidelink U2U relay discovery messages on the frequency included in *sl-FreqInfoList* in *SIB12* of the PCell including [FFS gNB capability indication]: + - 3> if the UE did not transmit a *SidelinkUEInformationNR* message since last entering RRC\_CONNECTED state; or + - 3> if since the last time the UE transmitted a *SidelinkUEInformationNR* message the UE connected to a PCell not providing *SIB12* including *sl-ConfigCommonNR*; or connected to a PCell providing *SIB12* but not including *sl-L2U2N-Relay* in case of L2 U2N relay operation; or connected to a PCell providing *SIB12* but not including *sl-L3U2N-RelayDiscovery* in case of L3 U2N relay operation; or + - 3> if since the last time the UE transmitted a *SidelinkUEInformationNR* message the UE connected to a PCell providing *SIB12* but not including [FFS gNB capability indication] in case of U2U relay operation; or + +- 3> if the last transmission of the *SidelinkUEInformationNR* message did not include *sl-TxResourceReqListDisc*; or if the information carried by the *sl-TxResourceReqListDisc* has changed since the last transmission of the *SidelinkUEInformationNR* message: + - 4> if the UE is capable of U2N Relay UE, and if *SIB12* includes *sl-RelayUE-ConfigCommon*, and if the U2N Relay UE threshold conditions as specified in 5.8.14.2 are met; or + - 4> if the UE is selecting a U2N Relay UE / has a selected U2N Relay UE/ configured with measurement object associated to L2 U2N Relay UEs, and if *SIB12* includes *sl-RemoteUE-ConfigCommon*, and if the U2N Remote UE threshold conditions as specified in 5.8.15.2 are met; or + - 4> if the UE is capable of U2U Relay UE, and if *SIB12* includes *sl-RelayUE-ConfigCommonU2U*, and if the U2U Relay UE threshold conditions as specified in 5.8.16.2 are met; or + - 4> if the UE is selecting a U2U Relay UE / has a selected U2U Relay UE, and if *SIB12* includes *sl-RemoteUE-ConfigCommonU2U*, and if the U2N Remote UE threshold conditions as specified in 5.8.17.2 are met: + - 5> initiate transmission of the *SidelinkUEInformationNR* message to indicate the NR sidelink relay discovery messages resources required by the UE in accordance with 5.8.3.3; +- 2> else: + - 3> if the last transmission of the *SidelinkUEInformationNR* message included *sl-TxResourceReqListDisc*: + - 4> initiate transmission of the *SidelinkUEInformationNR* message to indicate it no longer requires NR sidelink relay discovery messages resources in accordance with 5.8.3.3; + - 2> if configured by upper layer to transmit NR sidelink L2 U2N relay communication on the frequency included in *sl-FreqInfoList* in *SIB12* of the PCell including *sl-L2U2N-Relay*; or if configured by upper layer to transmit NR sidelink L3 U2N relay communication on the frequency included in *sl-FreqInfoList* in *SIB12* of the PCell including *sl-L3U2N-RelayDiscovery*; or + - 2> if configured by upper layer to transmit NR sidelink L2 U2U relay communication on the frequency included in *sl-FreqInfoList* in *SIB12* of the PCell including [*FFS gNB capability indication*]: + - 3> if the UE did not transmit a *SidelinkUEInformationNR* message since last entering RRC\_CONNECTED state; or + - 3> if since the last time the UE transmitted a *SidelinkUEInformationNR* message the UE connected to a PCell not providing *SIB12* including *sl-ConfigCommonNR*; or connected to a PCell providing *SIB12* but not including *sl-L2U2N-Relay* in case of L2 U2N relay operation; or connected to a PCell providing *SIB12* but not including *sl-L3U2N-RelayDiscovery* in case of L3 U2N relay operation; or + - 3> if since the last time the UE transmitted a *SidelinkUEInformationNR* message the UE connected to a PCell providing *SIB12* but not including [*FFS gNB capability indication*] in case of L2 U2U relay operation; or + - 3> if the last transmission of the *SidelinkUEInformationNR* message did not include *sl-TxResourceReqL2U2N-Relay*; or if the information carried by the *sl-TxResourceReqL2U2N-Relay* has changed since the last transmission of the *SidelinkUEInformationNR* message; or if the last transmission of the *SidelinkUEInformationNR* message did not include *sl-TxResourceReqL3U2N-Relay*; or if the information carried by the *sl-TxResourceReqL3U2N-Relay* has changed since the last transmission of the *SidelinkUEInformationNR* message; or + - 3> if the last transmission of the *SidelinkUEInformationNR* message did not include *sl-TxResourceReqL2U2U-Relay*; or if the information carried by the *sl-TxResourceReqL2U2U-Relay* has changed since the last transmission of the *SidelinkUEInformationNR* message; or + - 3> if configured by upper layers not to transmit either NR sidelink L2 U2N relay communication or NR sidelink L3 U2N relay communication, and if the last transmission of the *SidelinkUEInformationNR* message includes both *sl-TxResourceReqL2U2N-Relay* and *sl-TxResourceReqL3U2N-Relay*: + - 4> if the UE is capable of U2N Relay UE, and if *SIB12* includes *sl-RelayUE-ConfigCommon*, and if the U2N Relay UE threshold conditions as specified in 5.8.14.2 are met; or + +- 4> if the UE is selecting a U2N Relay UE / has a selected U2N Relay UE, and if *SIB12* includes *sl-RemoteUE-ConfigCommon*, and if the U2N Remote UE threshold conditions as specified in 5.8.15.2 are met; or + - 4> if the UE is capable of L2 U2U Relay UE, and if *SIB12* includes *sl-RelayUE-ConfigCommonU2U*, and if the U2U Relay UE threshold conditions as specified in 5.8.16.2 are met; or + - 4> if the UE is selecting a L2 U2U Relay UE / has a selected U2U Relay UE, and if *SIB12* includes *sl-RemoteUE-ConfigCommonU2U*, and if the U2N Remote UE threshold conditions as specified in 5.8.17.2 are met: + - 5> initiate transmission of the *SidelinkUEInformationNR* message to indicate the NR sidelink relay communication transmission resources required by the UE in accordance with 5.8.3.3; +- 2> else: +- 3> if the last transmission of the *SidelinkUEInformationNR* message included *sl-TxResourceReqL2U2N-Relay* or *sl-TxResourceReqL3U2N-Relay*: + - 4> initiate transmission of the *SidelinkUEInformationNR* message to indicate it no longer requires NR sidelink relay communication transmission resources in accordance with 5.8.3.3; + - 2> if configured by upper layers to perform NR sidelink reception on the frequency included in *sl-FreqInfoList/sl-FreqInfoListSizeExt* in *SIB12* of the PCell and if *sl-DRX-ConfigCommonGC-BC* is included in *SIB12-IEs*: + - 3> if the UE received a sidelink DRX configuration in the *RRCReconfigurationSidelink* message for NR sidelink unicast reception from the associated peer UE and the UE accepted the sidelink DRX configuration: + - 4> if the UE did not transmit a *SidelinkUEInformationNR* message since last entering RRC\_CONNECTED state; or + - 4> if since the last time the UE transmitted a *SidelinkUEInformationNR* message the UE connected to a PCell not providing *SIB12* including *sl-DRX-ConfigCommonGC-BC*; or + - 4> if the last transmission of the *SidelinkUEInformationNR* message did not include *sl-RxDRX-ReportList*; or if the information carried by *sl-RxDRX-ReportList* has changed since the last transmission of the *SidelinkUEInformationNR* message: + - 5> initiate transmission of the *SidelinkUEInformationNR* message to report the sidelink DRX configuration in accordance with 5.8.3.3; +- 3> else: +- 4> if the last transmission of the *SidelinkUEInformationNR* message included *sl-RxDRX-ReportList*: + - 5> initiate transmission of the *SidelinkUEInformationNR* message to indicate the sidelink DRX configuration is no longer used in accordance with 5.8.3.3; + - 3> if the UE is performing NR sidelink groupcast or broadcast reception and is interested in a service that sidelink DRX is applied: + - 4> if the UE did not transmit a *SidelinkUEInformationNR* message since last entering RRC\_CONNECTED state; or + - 4> if since the last time the UE transmitted a *SidelinkUEInformationNR* message the UE connected to a PCell not providing *SIB12* including *sl-DRX-ConfigCommonGC-BC*; or + - 4> if the last transmission of the *SidelinkUEInformationNR* message did not include *sl-RxInterestedGC-BC-DestList*; or if the information carried by *sl-RxInterestedGC-BC-DestList* has changed since the last transmission of the *SidelinkUEInformationNR* message: + - 5> initiate transmission of the *SidelinkUEInformationNR* message to report the Destination Layer-2 ID and QoS profile(s) associated with the service(s) in accordance with 5.8.3.3; + +3> else: + +4> if the last transmission of the *SidelinkUEInformationNR* message included *sl-RxInterestedGC-BC-DestList*: + +5> initiate transmission of the *SidelinkUEInformationNR* message to indicate it is no longer interested in the service that sidelink DRX is applied in accordance with 5.8.3.3; + +2> if configured by upper layers to perform NR sidelink transmission on the frequency included in *sl-FreqInfoList* in *SIB12* of the PCell and if *sl-DRX-ConfigCommonGC-BC* is included in *SIB12-IEs* and if the UE is configured with *sl-ScheduledConfig*: + +3> if the UE received a sidelink DRX assistance information or a sidelink DRX configuration reject information from the associated peer UE for NR sidelink unicast transmission: + +4> if the UE did not transmit a *SidelinkUEInformationNR* message since last entering *RRC\_CONNECTED* state; or + +4> if since the last time the UE transmitted a *SidelinkUEInformationNR* message the UE connected to a PCell not providing *SIB12* including *sl-DRX-ConfigCommonGC-BC*; or + +4> if the last transmission of the *SidelinkUEInformationNR* message did not include *sl-DRX-InfoFromRxList*, *sl-FailureList* or *sl-CarrierFailureList*; or if the information carried by *sl-DRX-InfoFromRxList*, *sl-FailureList* or *sl-CarrierFailureList* has changed since the last transmission of the *SidelinkUEInformationNR* message: + +5> initiate transmission of the *SidelinkUEInformationNR* message to report the sidelink DRX assistance information or the sidelink DRX configuration reject information in accordance with 5.8.3.3; + +NOTE: After including the SL-DRX reject information in *sl-FailureList* in the last transmission of the *SidelinkUEInformationNR* message, it is up to UE implementation to consider another sidelink DRX rejection of a new SL DRX configuration from the same associated peer UE as "change" of *sl-FailureList*. + +3> if the UE is performing NR sidelink groupcast transmission: + +4> if the UE did not transmit a *SidelinkUEInformationNR* message since last entering *RRC\_CONNECTED* state; or + +4> if since the last time the UE transmitted a *SidelinkUEInformationNR* message the UE connected to a PCell not providing *SIB12* including *sl-DRX-ConfigCommonGC-BC*; or + +4> if the last transmission of the *SidelinkUEInformationNR* message did not include *sl-DRX-Indication*; or if the information carried by *sl-DRX-Indication* has changed since the last transmission of the *SidelinkUEInformationNR* message: + +5> initiate transmission of the *SidelinkUEInformationNR* message to report sidelink DRX on/off indication for the corresponding destination in accordance with 5.8.3.3; + +1> if *SIB23* including *sl-PosConfigCommonNR* is provided by the PCell: + +2> if configured to receive sidelink control information for SL-PRS on the frequency included in *sl-FreqInfoList* in *SIB23* of the PCell: + +3> if the UE did not transmit a *SidelinkUEInformationNR* message since last entering *RRC\_CONNECTED* state; or + +3> if since the last time the UE transmitted a *SidelinkUEInformationNR* message the UE connected to a PCell not providing *SIB23* including *sl-PosConfigCommonNR*; or + +3> if the last transmission of the *SidelinkUEInformationNR* message did not include *sl-PosRxInterestedFreqList*; or if the frequency configured to receive sidelink control information for SL-PRS has changed since the last transmission of the *SidelinkUEInformationNR* message: + +- 4> initiate transmission of the *SidelinkUEInformationNR* message to indicate the frequency of interest for SL-PRS transmission in accordance with 5.8.3.3 and to request configured grant; +- 2> else: + - 3> if the last transmission of the *SidelinkUEInformationNR* message included *sl-PosRxInterestedFreqList*: + - 4> initiate transmission of the *SidelinkUEInformationNR* message to indicate it is no longer interested in SL-PRS reception in accordance with 5.8.3.3; + - 2> if configured to transmit SL-PRS on the frequency included in *sl-FreqInfoList* in *SIB23* of the PCell: + - 3> if the UE did not transmit a *SidelinkUEInformationNR* message since last entering *RRC\_CONNECTED* state; or + - 3> if since the last time the UE transmitted a *SidelinkUEInformationNR* message the UE connected to a PCell not providing *SIB23* including *sl-PosConfigCommonNR*; or + - 3> if the last transmission of the *SidelinkUEInformationNR* message did not include *sl-PosTxResourceReqList*; or if the information carried by the *sl-PosTxResourceReqList* has changed since the last transmission of the *SidelinkUEInformationNR* message: + - 4> initiate transmission of the *SidelinkUEInformationNR* message to indicate the NR sidelink positioning transmission resources required by the UE in accordance with 5.8.3.3; + - 2> else: + - 3> if the last transmission of the *SidelinkUEInformationNR* message included *sl-PosTxResourceReqList*: + - 4> initiate transmission of the *SidelinkUEInformationNR* message to indicate it no longer requires NR sidelink positioning transmission resources in accordance with 5.8.3.3; + +#### 5.8.3.3 Actions related to transmission of *SidelinkUEInformationNR* message + +The UE shall set the contents of the *SidelinkUEInformationNR* message as follows: + +- 1> if the UE initiates the procedure to indicate it is (no more) interested to receive NR sidelink communication/positioning; or +- 1> if the UE initiates the procedure to request (configuration/ release) of NR sidelink communication/positioning transmission resources or to report to the network that a sidelink radio link failure, sidelink RRC reconfiguration failure or sidelink carrier failure has been declared; or +- 1> if the UE initiates the procedure to report to the network the sidelink DRX configuration for NR sidelink unicast reception; or +- 1> if the UE initiates the procedure to report to the network the sidelink DRX assistance information or the sidelink DRX configuration reject information for NR sidelink unicast transmission; or +- 1> if the UE initiates the procedure to report to the network the Destination Layer-2 ID and QoS profile(s) associated with its interested service(s) that sidelink DRX is applied for NR sidelink groupcast or broadcast reception; or +- 1> if the UE initiates the procedure to report to the network the Destination Layer-2 ID and the sidelink DRX on/off indication for the corresponding destination for NR sidelink groupcast transmission; or +- 1> if the UE initiates the procedure to indicate it is (no more) interested to receive NR sidelink discovery messages; or +- 1> if the UE initiates the procedure to request (configuration/ release) of NR sidelink discovery messages transmission resources; or +- 1> if the UE initiates the procedure to request (configuration/ release) of NR sidelink U2N or U2U relay communication transmission resources or report other parameters related to U2N relay operation (i.e. UE includes all concerned information, irrespective of what triggered the procedure): + +- 2> if *SIB12* including *sl-ConfigCommonNR* is provided by the PCell: + - 3> if configured by upper layers to receive NR sidelink communication: + - 4> include *sl-RxInterestedFreqList* and set it to the frequency for NR sidelink communication reception; + - 3> if configured by upper layers to transmit non-relay NR sidelink communication and/or to transmit NR sidelink relay communication; or + - 3> if configured by upper layers to transmit NR sidelink L3 U2U relay communication [and *SIB12* includes *FFS gNB capability indication*]: + - 4> include *sl-TxResourceReqList* and set its fields (if needed) as follows for each destination for which it requests network to assign NR sidelink communication resource: + - 5> set *sl-DestinationIdentity* to the destination identity configured by upper layer for NR sidelink communication transmission; + - 5> set *sl-CastType* to the cast type of the associated destination identity configured by the upper layer for the NR sidelink communication transmission; + - 5> set *sl-RLC-ModeIndication* to include the RLC mode(s) and optionally QoS profile(s) of the sidelink QoS flow(s) of the associated RLC mode(s), if the associated bi-directional sidelink DRB has been established due to the configuration by *RRCReconfigurationSidelink*; + - 5> set *sl-QoS-InfoList* to include QoS profile(s) of the sidelink QoS flow(s) of the associated destination configured by the upper layer for the NR sidelink communication transmission; + - 5> set *sl-InterestedFreqList* to indicate the frequency of the associated destination for NR sidelink communication transmission; + - 5> set *sl-TypeTxSyncList* to the current synchronization reference type used on the associated *sl-InterestedFreqList* for NR sidelink communication transmission; + - 5> set *sl-CapabilityInformationSidelink* to include *UECapabilityInformationSidelink* message, if any, received from the associated peer UE; + - 5> if *sl-FreqInfoListSizeExt* is included in *SIB12-IEs*: + - 6> set *sl-QoS-InfoList* to include the frequency(ies), and Tx Profile mapped to the sidelink QoS flow(s) of the associated destination configured by the upper layer for the NR sidelink communication transmission; + - 4> if a sidelink radio link failure or a sidelink RRC reconfiguration failure has been declared, according to clauses 5.8.9.3 and 5.8.9.1.8, respectively; + - 5> include *sl-FailureList* and set its fields as follows for each destination for which it reports the NR sidelink communication failure: + - 6> set *sl-DestinationIdentity* to the destination identity configured by upper layer for NR sidelink communication transmission; + - 6> if the sidelink RLF is detected as specified in clause 5.8.9.3: + - 7> set *sl-Failure* as *rlf* for the associated destination for the NR sidelink communication transmission; + - 6> else if *RRCReconfigurationFailureSidelink* is received: + - 7> set *sl-Failure* as *configFailure* for the associated destination for the NR sidelink communication transmission; + - 4> if a sidelink carrier failure has been indicated by MAC layer; + - 5> include *sl-CarrierFailureList* and set its fields as follows for each destination for which it reports the sidelink carrier failure: + +- 6> set *sl-DestinationIdentity* to the destination identity for which the concerned sidelink carrier failure is indicated; +- 6> set *sl-CarrierFailure* to include the concerned carrier for which the sidelink carrier failure is indicated; +- 3> if *SIB12* includes *sl-NonRelayDiscovery* and if configured by upper layers to receive NR sidelink non-relay discovery messages, or if *SIB12* includes *sl-L2U2N-Relay* and if configured by upper layers to receive NR sidelink L2 U2N relay discovery messages, or if *SIB12* includes *sl-L3U2N-RelayDiscovery* and if configured by upper layers to receive NR sidelink L3 U2N relay discovery messages; or +- 3> if *SIB12* includes [*FFS gNB capability indication*] and if configured by upper layers to receive NR sidelink U2U relay discovery messages: + - 4> include *sl-RxInterestedFreqListDisc* and set it to the frequency for NR sidelink discovery messages reception; +- 3> if *SIB12* includes *sl-L2U2N-Relay* and the UE is capable of L2 U2N remote UE: + - 4> include *sl-SourceIdentityRemoteUE* and set it to the source identity configured by upper layer for NR sidelink L2 U2N relay communication transmission; +- 3> if *SIB12* includes *sl-NonRelayDiscovery* and if configured by upper layers to transmit NR sidelink non-relay discovery messages, or if *SIB12* includes *sl-L2U2N-Relay* and if configured by upper layers to transmit NR sidelink L2 U2N relay discovery messages, or if *SIB12* includes *sl-L3U2N-RelayDiscovery* and if configured by upper layers to transmit NR sidelink L3 U2N relay discovery messages; or +- 3> if *SIB12* includes [*FFS gNB capability indication*] and if configured by upper layers to transmit NR sidelink U2U relay discovery messages: + - 4> include *sl-TxResourceReqListDisc* and set its fields (if needed) as follows for each destination for which it requests network to assign NR sidelink discovery messages resource: + - 5> set *sl-DestinationIdentityDisc* to the destination identity configured by upper layer for NR sidelink discovery messages transmission; + - 5> if the UE is acting as L2 U2N Relay UE: + - 6> set *sl-SourceIdentityRelayUE* to the source identity configured by upper layer for NR sidelink L2 U2N relay discovery messages transmission; + - 5> set *sl-CastTypeDisc* to the cast type of the associated destination identity for the NR sidelink discovery messages transmission; + - 5> set *sl-TxInterestedFreqListDisc* to indicate the frequency of the associated destination for NR sidelink discovery messages transmission; + - 5> set *sl-TypeTxSyncListDisc* to the current synchronization reference type used on the associated *sl-InterestedFreqList* for NR sidelink discovery messages transmission; + - 5> set *sl-DiscoveryType* to the current discovery type of the associated destination identity configured by the upper layer for NR sidelink discovery messages transmission; +- 3> if *SIB12* includes *sl-L2U2N-Relay* and if configured by upper layers to transmit NR sidelink L2 U2N relay communication and the UE is acting as L2 U2N Relay UE: + - 4> include *sl-TxResourceReqL2U2N-Relay* in *sl-TxResourceReqListCommRelay* and set its fields (if needed) as follows for each destination for which it requests network to assign NR sidelink L2 U2N relay communication resource: + - 5> set *sl-DestinationIdentityL2U2N* to the destination identity configured by upper layer for NR sidelink L2 U2N relay communication transmission; + - 5> set *sl-TxInterestedFreqListL2U2N* to indicate the frequency of the associated destination for NR sidelink L2 U2N relay communication transmission; + +- 5> set *sl-TypeTxSyncListL2U2N* to the current synchronization reference type used on the associated *sl-InterestedFreqListL2U2N* for NR sidelink L2 U2N relay communication transmission; +- 5> set *sl-LocalID-Request* to request local ID for L2 U2N Remote UE transiting to RRC\_CONNECTED or in RRC\_CONNECTED state; +- 5> set *sl-PagingIdentityRemoteUE* to the paging UE ID received from peer L2 U2N Remote UE, if it is not released as in 5.8.9.8.3; +- 5> set *sl-CapabilityInformationSidelink* to include *UECapabilityInformationSidelink* message, if any, received from peer UE; +- 4> include *ue-Type* and set it to *relayUE*; +- 3> if *SIB12* includes *sl-L2U2N-Relay* and if configured by upper layers to transmit NR sidelink L2 U2N relay communication and the UE has a selected L2 U2N Relay UE: + - 4> include *sl-TxResourceReqL2U2N-Relay* in *sl-TxResourceReqListCommRelay* and set its fields (if needed) as follows to request network to assign NR sidelink L2 U2N relay communication resource: + - 5> set *sl-TxInterestedFreqListL2U2N* to indicate the frequency of the associated destination for NR sidelink L2 U2N relay communication transmission; + - 5> set *sl-TypeTxSyncListL2U2N* to the current synchronization reference type used on the associated *sl-InterestedFreqListL2U2N* for NR sidelink L2 U2N relay communication transmission; + - 5> set *sl-CapabilityInformationSidelink* to include *UECapabilityInformationSidelink* message, if any, received from peer UE; + - 4> include *ue-Type* and set it to *remoteUE*; +- 3> if *SIB12* includes *sl-L3U2N-RelayDiscovery* and if configured by upper layers to transmit NR sidelink L3 U2N relay communication: + - 4> include *sl-TxResourceReqL3U2N-Relay* in *sl-TxResourceReqListCommRelay* and set its fields (if needed) as follows for each destination for which it requests network to assign NR sidelink L3 U2N relay communication resource: + - 5> set *sl-DestinationIdentity* to the destination identity configured by upper layer for NR sidelink L3 U2N relay communication transmission; + - 5> set *sl-CastType* to the cast type of the associated destination identity configured by the upper layer for the NR sidelink L3 U2N relay communication transmission; + - 5> set *sl-RLC-ModeIndication* to include the RLC mode(s) and optionally QoS profile(s) of the sidelink QoS flow(s) of the associated RLC mode(s), if the associated bi-directional sidelink DRB has been established due to the configuration by *RRCReconfigurationSidelink*; + - 5> set *sl-QoS-InfoList* to include QoS profile(s) of the sidelink QoS flow(s) of the associated destination configured by the upper layer for the NR sidelink L3 U2N relay communication transmission; + - 5> set *sl-TxInterestedFreqList* to indicate the frequency of the associated destination for NR sidelink L3 U2N relay communication transmission; + - 5> set *sl-TypeTxSyncList* to the current synchronization reference type used on the associated *sl-InterestedFreqList* for NR sidelink L3 U2N relay communication transmission; + - 5> set *sl-CapabilityInformationSidelink* to include *UECapabilityInformationSidelink* message, if any, received from peer UE; + - 4> include *ue-Type* and set it to *relayUE* if the UE is acting as NR sidelink L3 U2N Relay UE or to *remoteUE* otherwise; +- 3> if *SIB12* includes [*FFS gNB capability indication*] and if configured by upper layers to transmit NR sidelink L2 U2U relay communication and the UE is acting as L2 U2U Relay UE: + +- 4> include *sl-TxResourceReqL2-U2U* and set its fields (if needed) as follows for each destination for which it requests network to assign NR sidelink L2 U2U relay communication resource: + - 5> set *sl-DestinationIdentityL2-U2U* to the destination identity configured by upper layer for NR sidelink L2 U2U relay communication transmission to peer L2 U2U Remote UE; + - 5> set *sl-TxInterestedFreqListL2-U2U* to indicate the frequency of the associated destination for NR sidelink L2 U2U relay communication transmission; + - 5> set *sl-TypeTxSyncListL2-U2U* to the current synchronization reference type used on the associated *sl-InterestedFreqListL2-U2U* for NR sidelink L2 U2U relay communication transmission; + - 5> set *sl-CapabilityInformationSidelink* to include *UECapabilityInformationSidelink* message, if any, received from peer L2 U2U Remote UE; + - 5> include *sl-U2U-InfoList* and set its fields (if needed) for each entry as follows, to report the related information of the connected L2 Remote UEs: + - 6> include the source L2 U2U Remote UE's source L2 destination in *sl-TargetUE-Identity*; + - 6> include *sl-PerSLRB-QoS-InfoList*, with each entry including the per-SLRB second-hop QoS profile and the corresponding *sl-RemoteUE-SLRB-Identity* which is set to the same value as the *SLRB-PC5-ConfigIndex* received in *RRRCReconfigurationSidelink* message from the L2 U2U Remote UE for the same end-to-end SLRB; +- 3> if *SIB12* includes [*FFS gNB capability indication*] and if configured by upper layers to transmit NR sidelink L2 U2U relay communication and the UE has a selected L2 U2U Relay UE: + - 4> include *sl-TxResourceReqL2-U2U* and set its fields (if needed) as follows to request network to assign NR sidelink L2 U2U relay communication resource: + - 5> set *sl-DestinationIdentityL2-U2U* to the destination identity configured by upper layer for NR sidelink L2 U2U relay communication transmission to L2 U2U Relay UE; + - 5> set *sl-TxInterestedFreqListL2-U2U* to indicate the frequency of the associated destination for NR sidelink L2 U2U relay communication transmission; + - 5> set *sl-TypeTxSyncListL2-U2U* to the current synchronization reference type used on the associated *sl-InterestedFreqListL2-U2U* for NR sidelink L2 U2U relay communication transmission; + - 5> set *sl-CapabilityInformationSidelink* to include *UECapabilityInformationSidelink* message received from L2 U2U Relay UE and the peer L2 U2U Remote UE, if any; + - 5> include *sl-U2U-InfoList* and set its fields (if needed) for each entry as follows to report the related end-to-end and the first hop information for the end-to-end PC5 connection with each peer L2 U2U Remote UE: + - 6> set *sl-TargetUE-Identity* to the destination identity configured by upper layer for NR sidelink L2 U2U relay communication transmission to peer L2 U2U Remote UE; + - 6> set *sl-E2E-QoS-InfoList* to include end-to-end QoS profile(s) of the sidelink QoS flow(s) of the associated destination configured by the upper layer for the NR sidelink L2 U2U relay communication transmission to peer L2 U2U Remote UE; + - 6> set *sl-PerSLRB-QoS-InfoList* to include the first-hop split PDB of the sidelink QoS flow(s) received from the *sl-SplitQoS-InfoListPC5* in *UEInformationResponseSidelink* message for the associated destination in accordance with the received *sl-TargetUE-Identity*; +- 3> if *sl-DRX-ConfigCommonGC-BC* is included in *SIB12-IEs*: + - 4> if configured by upper layers to perform NR sidelink reception: + - 5> include *sl-RxDRX-ReportList* and set its fields (if needed) as follows for each destination for which it reports to network: + +6> set *sl-DRX-ConfigFromTx* to include the accepted sidelink DRX configuration of the associated destination for NR sidelink unicast communication, if received from the associated peer UE; + +5> include *sl-RxInterestedGC-BC-DestList* and set its fields (if needed) as follows for each Destination Layer-2 ID for which it reports to network: + +6> set *sl-RxInterestedQoS-InfoList* to include the QoS profile of its interested service(s) that sidelink DRX is applied for the associated destination for NR sidelink groupcast or broadcast reception; + +NOTE 1: It is up to UE implementation to set the QoS profile in *sl-RxInterestedQoS-InfoList* for reception of NR sidelink discovery message or ProSe Direct Link Establishment Request message as described in TS 24.554 [72], or for reception of Direct Link Establishment Request message as described in TS 24.587 [57]. + +6> set *sl-DestinationIdentity* to the associated destination identity configured by upper layer for NR sidelink groupcast or broadcast reception; + +4> if configured by upper layers to perform NR sidelink transmission and configured with *sl-ScheduledConfig*: + +5> include *sl-TxResourceReqList* and/or *sl-TxResourceReqListCommRelay* and/or *sl-FailureList* and set its fields (if needed) as follows for each destination for which it reports to network: + +6> set *sl-DRX-InfoFromRxList* to include the sidelink DRX assistance information of the associated destination, if any, received from the associated peer UE; + +6> if the *RRCReconfigurationCompleteSidelink* message includes the *sl-DRX-ConfigReject*: + +7> set *sl-Failure* as *drxReject-v1710* for the associated destination for the NR sidelink communication transmission; + +6> set *sl-DRX-Indication* to include the sidelink DRX on/off indication for the associated destination for NR sidelink groupcast transmission; + +2> if *SIB23* including *sl-PosConfigCommonNR* is provided by the PCell; + +3> if configured to transmit SL-PRS: + +4> include *sl-PosTxResourceReqList* and set its fields (if needed) as follows for each destination for which it requests network to assign NR sidelink positioning resource: + +5> set *sl-DestinationIdentity* to the destination identity configured by upper layer for NR sidelink positioning transmission; + +5> set *sl-CastType* to the cast type of the associated destination identity configured by the upper layer for the NR sidelink positioning transmission; + +5> set *sl-RLC-ModeIndication* to include the RLC mode(s) + +5> set *sl-InterestedFreqList* to indicate the frequency of the associated destination for SL-PRS transmission; + +5> set *sl-TypeTxSyncList* to the current synchronization reference type used on the associated *sl-InterestedFreqList* for NR sidelink positioning transmission; + +3> if configured to receive sidelink control information for SL-PRS measurements; + +4> include *sl-PosRxInterestedFreqList* and set it to the frequency for NR sidelink positioning reception. + +Editor's Note: FFS on *sl-PosTxResourceReqList* + +1> if the UE initiates the procedure while connected to an E-UTRA PCell: + +2> submit the *SidelinkUEInformationNR* to lower layers via SRB1, embedded in E-UTRA RRC message *ULInformationTransferIRAT* as specified in TS 36.331 [10], clause 5.6.28; + +1> else: + +2> submit the *SidelinkUEInformationNR* message to lower layers for transmission. + +NOTE 2: When multiple lists are reported in *SidelinkUEInformationNR*, a UE can report up to *maxNrofSL-Dest-r16* SL destinations in *sl-TxResourceReqList*, *sl-TxResourceReqListDisc* and *sl-TxResourceReqListCommRelay* in total. + +### 5.8.4 Void + +### 5.8.5 Sidelink synchronisation information transmission for NR sidelink communication/discovery/positioning + +#### 5.8.5.1 General + +![Sequence diagram for Figure 5.8.5.1-1: Synchronisation information transmission for NR sidelink communication/discovery/positioning, in (partial) coverage. The diagram shows a UE and a Network. The Network sends a SIB12 acquisition message to the UE. The UE then sends an RRCReconfiguration message to the Network. Finally, the UE sends an SLSS& MasterInformationBlockSidelink message to the Network.](a057800564be3506d2d87b6a4daee25b_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Network + Note left of UE: + Network->>UE: SIB12 acquisition + UE-->>Network: RRCReconfiguration + UE->>Network: SLSS& MasterInformationBlockSidelink + +``` + +Sequence diagram for Figure 5.8.5.1-1: Synchronisation information transmission for NR sidelink communication/discovery/positioning, in (partial) coverage. The diagram shows a UE and a Network. The Network sends a SIB12 acquisition message to the UE. The UE then sends an RRCReconfiguration message to the Network. Finally, the UE sends an SLSS& MasterInformationBlockSidelink message to the Network. + +Figure 5.8.5.1-1: Synchronisation information transmission for NR sidelink communication/discovery/positioning, in (partial) coverage + +![Sequence diagram for Figure 5.8.5.1-2: Synchronisation information transmission for NR sidelink communication/discovery/positioning, out of coverage. The diagram shows two UEs. The first UE sends an SLSS& MasterInformationBlockSidelink message to the second UE. The second UE then sends an SLSS& MasterInformationBlockSidelink message to the first UE.](2dc649aff45a8a0924db45fc3bd6aabb_img.jpg) + +``` + +sequenceDiagram + participant UE1 as UE + participant UE2 as UE + UE1->>UE2: SLSS& MasterInformationBlockSidelink + UE2->>UE1: SLSS& MasterInformationBlockSidelink + +``` + +Sequence diagram for Figure 5.8.5.1-2: Synchronisation information transmission for NR sidelink communication/discovery/positioning, out of coverage. The diagram shows two UEs. The first UE sends an SLSS& MasterInformationBlockSidelink message to the second UE. The second UE then sends an SLSS& MasterInformationBlockSidelink message to the first UE. + +Figure 5.8.5.1-2: Synchronisation information transmission for NR sidelink communication/discovery/positioning, out of coverage + +The purpose of this procedure is to provide synchronisation information to a UE. This procedure also applies to NR sidelink discovery. + +#### 5.8.5.2 Initiation + +A UE capable of NR sidelink communication/discovery and SLSS/PSBCH transmission shall, when transmitting NR sidelink communication/discovery/positioning, and if the conditions for NR sidelink communication/discovery/positioning operation are met and when the following conditions are met: + +- 1> if in coverage on the frequency used for NR sidelink communication/discovery/positioning, as defined in TS 38.304 [20]; and has selected GNSS or the cell as synchronization reference as defined in 5.8.6.3; or +- 1> if out of coverage on the frequency used for NR sidelink communication/discovery/positioning, and the frequency used to transmit NR sidelink communication/discovery is included in *sl-FreqInfoToAddModList/sl-FreqInfoToAddModListExt* in *sl-ConfigDedicatedNR* within *RRCReconfiguration* message or included in *sl-* + +*FreqInfoList/sl-FreqInfoListSizeExt* within *SIB12* or *SIB23* for NR sidelink positioning; and has selected GNSS or the cell as synchronization reference as defined in 5.8.6.3: + +- 2> if *sl-SyncFreqList* is neither included in *RRReconfiguration* nor in *SIB12*; or +- 2> if *sl-SyncFreqList* is included in *RRReconfiguration* or in *SIB12*; and if none of the frequency(ies) selected as specified in TS 38.321 [3] is included in the *sl-SyncFreqList* or the concerned frequency is selected as the synchronisation carrier frequency in accordance with 5.8.6.2; or +- 2> if *sl-SyncFreqList* and *sl-SyncTxMultiFreq* are included in *RRReconfiguration* or in *SIB12*; and if the concerned frequency has been selected for NR sidelink communication transmission as specified in TS 38.321 [3] and is included in *sl-SyncFreqList*; and if the UE has selected a frequency other than the concerned frequency as the synchronisation carrier frequency in accordance with 5.8.6.2; and if *sl-SyncTxDisabled* corresponding to the concerned frequency is not configured in *RRReconfiguration* or in *SIB12*: + - 3> if in *RR\_CONNECTED*; and if *networkControlledSyncTx* is configured and set to *on*; or + - 3> if *networkControlledSyncTx* is not configured; and for the concerned frequency *syncTxThreshIC* is configured; and the RSRP measurement of the reference cell, selected as defined in 5.8.6.3, for NR sidelink communication/discovery transmission is below the value of *syncTxThreshIC*: + - 4> transmit sidelink SSB on the frequency used for NR sidelink communication/discovery in accordance with 5.8.5.3 and TS 38.211 [16], including the transmission of SLSS as specified in 5.8.5.3 and transmission of *MasterInformationBlockSidelink* as specified in 5.8.9.4.3; + +1> else: + +- 2> if *sl-SyncFreqList* is not included in *SL-PreconfigurationNR*; or +- 2> if *sl-SyncFreqList* is included in *SL-PreconfigurationNR*, and if none of the frequency(ies) selected as specified in TS 38.321 [3] is included in the *sl-SyncFreqList* or the concerned frequency is selected as the synchronisation carrier frequency in accordance with 5.8.6.2; or +- 2> if *sl-SyncFreqList* and *sl-SyncTxMultiFreq* are included in *SL-PreconfigurationNR*, and if the concerned frequency has been selected for NR sidelink communication transmission as specified in TS 38.321 [3] and included in *sl-SyncFreqList*; and if the UE has selected a frequency other than the concerned frequency as the synchronisation carrier frequency in accordance with 5.8.6.2; and if *sl-SyncTxDisabled* corresponding to the concerned frequency is not configured in *SL-PreconfigurationNR*: + - 3> for the frequency used for NR sidelink communication/discovery, if *syncTxThreshOoC* is included in *SidelinkPreconfigNR*; and the UE is not directly synchronized to GNSS, and the UE has no selected SyncRef UE or the PSBCH-RSRP measurement result of the selected SyncRef UE is below the value of *syncTxThreshOoC*; or + - 3> for the frequency used for NR sidelink communication/discovery, if the UE selects GNSS as the synchronization reference source: + - 4> transmit sidelink SSB on the frequency used for NR sidelink communication/discovery in accordance with 5.8.5.3 and TS 38.211 [16], including the transmission of SLSS as specified in 5.8.5.3 and transmission of *MasterInformationBlockSidelink* as specified in 5.8.9.4.3; + +#### 5.8.5.3 Transmission of SLSS + +The UE shall select the SLSSID and the slot in which to transmit SLSS as follows: + +- 1> if triggered by NR sidelink communication/discovery/positioning and in coverage on the frequency used for NR sidelink communication/discovery/positioning, as defined in TS 38.304 [20]; or +- 1> if triggered by NR sidelink communication/discovery/positioning, and out of coverage on the frequency used for NR sidelink communication/discovery/positioning, and the concerned frequency is included in *sl-FreqInfoToAddModList/sl-FreqInfoToAddModListExt* in *sl-ConfigDedicatedNR* within *RRReconfiguration* message or included in *sl-FreqInfoList/sl-FreqInfoToAddModListExt* within *SIB12* or *SIB23* for NR sidelink positioning: + +- 2> if the UE has selected GNSS as synchronization reference in accordance with 5.8.6.2: + - 3> select SLSSID 0; + - 3> use *sl-SSB-TimeAllocation1* included in the entry of configured *sl-SyncConfigList* corresponding to the concerned frequency, that includes *txParameters* and *gnss-Sync*; + - 3> select the slot(s) indicated by *sl-SSB-TimeAllocation1*; +- 2> if the UE has selected a cell as synchronization reference in accordance with 5.8.6.2: + - 3> select the SLSSID included in the entry of configured *sl-SyncConfigList* corresponding to the concerned frequency, that includes *txParameters* and does not include *gnss-Sync*; + - 3> select the slot(s) indicated by *sl-SSB-TimeAllocation1*; +- 1> else if triggered by NR sidelink communication/discovery and the UE has GNSS as the synchronization reference: + - 2> select SLSSID 0; + - 2> if *sl-SSB-TimeAllocation3* is configured for the frequency used in *SidelinkPreconfigNR*: + - 3> select the slot(s) indicated by *sl-SSB-TimeAllocation3*; + - 2> else: + - 3> select the slot(s) indicated by *sl-SSB-TimeAllocation1*; +- 1> else: + - 2> select the synchronisation reference UE (i.e. SyncRef UE) as defined in 5.8.6; + - 2> if the UE has a selected SyncRef UE and *inCoverage* in the *MasterInformationBlockSidelink* message received from this UE is set to *true*; or + - 2> if the UE has a selected SyncRef UE and *inCoverage* in the *MasterInformationBlockSidelink* message received from this UE is set to *false* while the SLSS from this UE is part of the set defined for out of coverage, see TS 38.211 [16]: + - 3> select the same SLSSID as the SLSSID of the selected SyncRef UE; + - 3> select the slot in which to transmit the SLSS according to the *sl-SSB-TimeAllocation1* or *sl-SSB-TimeAllocation2* included in the preconfigured sidelink parameters corresponding to the concerned frequency, such that the timing is different from the SLSS of the selected SyncRef UE; + - 2> else if the UE has a selected SyncRef UE and the SLSS from this UE was transmitted on the slot(s) indicated *sl-SSB-TimeAllocation3*, which is configured for the frequency used in *SidelinkPreconfigNR*: + - 3> select SLSSID 337; + - 3> select the slot(s) indicated by *sl-SSB-TimeAllocation2*; + - 2> else if the UE has a selected SyncRef UE: + - 3> select the SLSSID from the set defined for out of coverage having an index that is 336 more than the index of the SLSSID of the selected SyncRef UE, see TS 38.211 [16]; + - 3> select the slot in which to transmit the SLSS according to *sl-SSB-TimeAllocation1* or *sl-SSB-TimeAllocation2* included in the preconfigured sidelink parameters corresponding to the concerned frequency, such that the timing is different from the SLSS of the selected SyncRef UE; + - 2> else (i.e. no SyncRef UE selected): + - 3> if the UE has not randomly selected an SLSSID: + +- 4> randomly select, using a uniform distribution, an SLSSID from the set of sequences defined for out of coverage except SLSSID 336 and 337, see TS 38.211 [16]; +- 4> select the slot in which to transmit the SLSS according to the *sl-SSB-TimeAllocation1* or *sl-SSB-TimeAllocation2* (arbitrary selection between these) included in the preconfigured sidelink parameters in *SidelinkPreconfigNR* corresponding to the concerned frequency; + +### 5.8.5a Sidelink synchronisation information transmission for V2X sidelink communication + +#### 5.8.5a.1 General + +![Sequence diagram for Figure 5.8.5a.1-1: Synchronisation information transmission for V2X sidelink communication, in (partial) coverage. The diagram shows a UE and a Network. The UE sends a message labeled 'SLSS and MasterInformationBlockSidelink' to the Network. The Network responds with 'SIB13/SIB14 acquisition' and 'RRReconfiguration'.](dfafe39c233a62ec8ebd71e42992c14d_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Network + Note left of UE: SLSS and MasterInformationBlockSidelink + UE->>Network: SLSS and MasterInformationBlockSidelink + Network-->>UE: SIB13/SIB14 acquisition + Network-->>UE: RRReconfiguration + +``` + +Sequence diagram for Figure 5.8.5a.1-1: Synchronisation information transmission for V2X sidelink communication, in (partial) coverage. The diagram shows a UE and a Network. The UE sends a message labeled 'SLSS and MasterInformationBlockSidelink' to the Network. The Network responds with 'SIB13/SIB14 acquisition' and 'RRReconfiguration'. + +Figure 5.8.5a.1-1: Synchronisation information transmission for V2X sidelink communication, in (partial) coverage + +![Sequence diagram for Figure 5.8.5a.1-2: Synchronisation information transmission for V2X sidelink communication, out of coverage. The diagram shows two UEs. The first UE sends a message labeled 'SLSS and MasterInformationBlockSidelink' to the second UE. The second UE then sends a message labeled 'SLSS and MasterInformationBlockSidelink' to the first UE.](9e26cd5584f423e1b2155fb341db579f_img.jpg) + +``` + +sequenceDiagram + participant UE1 as UE + participant UE2 as UE + Note left of UE1: SLSS and MasterInformationBlockSidelink + UE1->>UE2: SLSS and MasterInformationBlockSidelink + Note right of UE2: SLSS and MasterInformationBlockSidelink + UE2->>UE1: SLSS and MasterInformationBlockSidelink + +``` + +Sequence diagram for Figure 5.8.5a.1-2: Synchronisation information transmission for V2X sidelink communication, out of coverage. The diagram shows two UEs. The first UE sends a message labeled 'SLSS and MasterInformationBlockSidelink' to the second UE. The second UE then sends a message labeled 'SLSS and MasterInformationBlockSidelink' to the first UE. + +Figure 5.8.5a.1-2: Synchronisation information transmission for V2X sidelink communication, out of coverage + +The purpose of this procedure is to provide synchronisation information to a UE. + +#### 5.8.5a.2 Initiation + +A UE capable of V2X sidelink communication initiates the transmission of SLSS and *MasterInformationBlock-SL-V2X* according to the conditions and the procedures specified for V2X sidelink communication in clause 5.10.7 of TS 36.331 [10]. + +NOTE 1: When applying the procedure in this clause, *SIB13* and *SIB14* correspond to *SystemInformationBlockType21* and *SystemInformationBlockType26* specified in TS 36.331 [10] respectively. + +### 5.8.6 Sidelink synchronisation reference + +#### 5.8.6.1 General + +The purpose of this procedure is to select a synchronisation reference and used when transmitting NR sidelink communication/discovery. This procedure also applies to NR sidelink discovery. + +#### 5.8.6.2 Selection and reselection of synchronisation reference + +The UE shall for frequency(ies) which have been selected for NR sidelink communication/discovery as specified in TS 38.321 [3]: + +- 1) if one frequency is selected for NR sidelink communication/discovery: + - 2) if *sl-SyncFreqList* is not included in *RRCReconfiguration* nor in *SIB12*; or + - 2) if *sl-SyncFreqList* is included in *RRCReconfiguration* or in *SIB12*, and none of the frequency(ies) selected as specified in TS 38.321 [3] is included in the *syncFreqList*: + - 3) if the frequency used for NR sidelink communication/discovery is included in *sl-FreqInfoToAddModList* in *sl-ConfigDedicatedNR* within *RRCReconfiguration* message or included in *sl-ConfigCommonNR* within *SIB12*, and *sl-SyncPriority* is configured for the concerned frequency and set to *gnbEnb*: + - 4) select a cell as the synchronization reference source as defined in 5.8.6.3: + +NOTE 1: When out of coverage L2 U2N Remote UE receives *SIB12* with *sl-SyncPriority* set to *gnbEnb*, the L2 U2N Remote UE continues using the current synchronization source until higher priority synchronization source is found or the current synchronization source becomes unreliable. + +- 3) else if the frequency used for NR sidelink communication/discovery is included in *sl-FreqInfoToAddModList* in *sl-ConfigDedicatedNR* within *RRCReconfiguration* message or included in *sl-ConfigCommonNR* within *SIB12*, and *sl-SyncPriority* for the concerned frequency is not configured or is set to *gnss*, and GNSS is reliable in accordance with TS 38.101-1 [15] and TS 38.133 [14]: + - 4) select GNSS as the synchronization reference source; +- 3) else if the frequency used for NR sidelink communication/discovery is included in *SL-PreconfigurationNR*, and *sl-SyncPriority* in *SidelinkPreconfigNR* is set to *gnss* and GNSS is reliable in accordance with TS 38.101-1 [15] and TS 38.133 [14]: + - 4) select GNSS as the synchronization reference source; +- 3) else: + - 4) perform a full search (i.e. covering all subframes and all possible SLSSIDs) to detect candidate SLSS, in accordance with TS 38.133 [14] + - 4) when evaluating the one or more detected SLSSIDs, apply layer 3 filtering as specified in 5.5.3.2 using the preconfigured *sl-filterCoefficient* in *SL-SyncConfig*, before using the PSBCH-RSRP measurement results; + - 4) if the UE has selected a *SyncRef UE*: + - 5) if the PSBCH-RSRP of the strongest candidate *SyncRef UE* exceeds the minimum requirement TS 38.133 [14] by *sl-SyncRefMinHyst* and the strongest candidate *SyncRef UE* belongs to the same priority group as the current *SyncRef UE* and the PSBCH-RSRP of the strongest candidate *SyncRef UE* exceeds the PSBCH-RSRP of the current *SyncRef UE* by *syncRefDiffHyst*; or + - 5) if the PSBCH-RSRP of the candidate *SyncRef UE* exceeds the minimum requirement TS 38.133 [14] by *sl-SyncRefMinHyst* and the candidate *SyncRef UE* belongs to a higher priority group than the current *SyncRef UE*; or + - 5) if GNSS becomes reliable in accordance with TS 38.101-1 [15] and TS 38.133 [14], and GNSS belongs to a higher priority group than the current *SyncRef UE*; or + - 5) if a cell is detected and gNB/eNB (if *sl-NbAsSync* is set to *true*) belongs to a higher priority group than the current *SyncRef UE*; or + - 5) if the PSBCH-RSRP of the current *SyncRef UE* is less than the minimum requirement defined in TS 38.133 [14]: + - 6) consider no *SyncRef UE* to be selected; + +- 4> if the UE has selected GNSS as the synchronization reference for NR sidelink communication/discovery: + - 5> if the PSBCH-RSRP of the candidate SyncRef UE exceeds the minimum requirement defined in TS 38.133 [14] by *sl-SyncRefMinHyst* and the candidate SyncRef UE belongs to a higher priority group than GNSS; or + - 5> if GNSS becomes not reliable in accordance with TS 38.101-1 [15] and TS 38.133 [14]: + - 6> consider GNSS not to be selected; +- 4> if the UE has selected cell as the synchronization reference for NR sidelink communication/discovery: + - 5> if the PSBCH-RSRP of the candidate SyncRef UE exceeds the minimum requirement defined in TS 38.133 [14] by *sl-SyncRefMinHyst* and the candidate SyncRef UE belongs to a higher priority group than gNB/eNB; or + - 5> if the selected cell is not detected: + - 6> consider the cell not to be selected; +- 4> if the UE has not selected any synchronization reference: + - 5> if the UE detects one or more SLSSIDs for which the PSBCH-RSRP exceeds the minimum requirement defined in TS 38.133 [14] by *sl-SyncRefMinHyst* and for which the UE received the corresponding *MasterInformationBlockSidelink* message (candidate SyncRef UEs), or if the UE detects GNSS that is reliable in accordance with TS 38.101-1 [15] and TS 38.133 [14], or if the UE detects a cell, select a synchronization reference according to the following priority group order: + - 6> if *sl-SyncPriority* corresponding to the concerned frequency is set to *gnbEnb*: + - 7> UEs of which SLSSID is part of the set defined for in coverage, and *inCoverage*, included in the *MasterInformationBlockSidelink* message received from this UE, is set to *true*, starting with the UE with the highest PSBCH-RSRP result (priority group 1); + - 7> UE of which SLSSID is part of the set defined for in coverage, and *inCoverage*, included in the *MasterInformationBlockSidelink* message received from this UE, is set to *false*, starting with the UE with the highest PSBCH-RSRP result (priority group 2); + - 7> GNSS that is reliable in accordance with TS 38.101-1 [15] and TS 38.133 [14] (priority group 3); + - 7> UEs of which SLSSID is 0, and *inCoverage*, included in the *MasterInformationBlockSidelink* message received from this UE, is set to *true*, or of which SLSSID is 0 and SLSS is transmitted on slot(s) indicated by *sl-SSB-TimeAllocation3*, starting with the UE with the highest PSBCH-RSRP result (priority group 4); + - 7> UEs of which SLSSID is 0 and SLSS is not transmitted on slot(s) indicated by *sl-SSB-TimeAllocation3*, and *inCoverage*, included in the *MasterInformationBlockSidelink* message received from this UE, is set to *false*, starting with the UE with the highest PSBCH-RSRP result (priority group 5); + - 7> UEs of which SLSSID is 337 and *inCoverage*, included in the *MasterInformationBlockSidelink* message received from this UE, is set to *false*, starting with the UE with the highest PSBCH-RSRP result (priority group 5); + - 7> Other UEs, starting with the UE with the highest PSBCH-RSRP result (priority group 6); + - 6> if *sl-SyncPriority* corresponding to the concerned frequency is set to *gnss*, and *sl-NbAsSync* is set to *true*: + - 7> UEs of which SLSSID is 0, and *inCoverage*, included in the *MasterInformationBlockSidelink* message received from this UE, is set to *true*, or of which SLSSID is 0 and SLSS is transmitted on slot(s) indicated by *sl-SSB-TimeAllocation3*, starting with the UE with the highest PSBCH-RSRP result (priority group 1); + +- 7> UEs of which SLSSID is 0 and SLSS is not transmitted on slot(s) indicated by *sl-SSB-TimeAllocation3*, and *inCoverage*, included in the *MasterInformationBlockSidelink* message received from this UE, is set to *false*, starting with the UE with the highest PSBCHS-RSRP result (priority group 2); + - 7> UEs of which SLSSID is 337 and *inCoverage*, included in the *MasterInformationBlockSidelink* message received from this UE, is set to *false*, starting with the UE with the highest PSBCH-RSRP result (priority group 2); + - 7> the cell detected by the UE as defined in 5.8.6.3 (priority group 3); + - 7> UEs of which SLSSID is part of the set defined for in coverage, and *inCoverage*, included in the *MasterInformationBlockSidelink* message received from this UE, is set to *true*, starting with the UE with the highest PSBCH-RSRP result (priority group 4); + - 7> UE of which SLSSID is part of the set defined for in coverage, and *inCoverage*, included in the *MasterInformationBlockSidelink* message received from this UE, is set to *false*, starting with the UE with the highest PSBCH-RSRP result (priority group 5); + - 7> Other UEs, starting with the UE with the highest S-RSRP result (priority group 6); +- 6> if *sl-SyncPriority* corresponding to the concerned frequency is set to *gnss*, and *sl-NbAsSync* is set to *false*: +- 7> UEs of which SLSSID is 0, and *inCoverage*, included in the *MasterInformationBlockSidelink* message received from this UE, is set to *true*, or of which SLSSID is 0 and SLSS is transmitted on slot(s) indicated by *sl-SSB-TimeAllocation3*, starting with the UE with the highest PSBCH-RSRP result (priority group 1); + - 7> UEs of which SLSSID is 0 and SLSS is not transmitted on slot(s) indicated by *sl-SSB-TimeAllocation3*, and *inCoverage*, included in the *MasterInformationBlockSidelink* message received from this UE, is set to *false*, starting with the UE with the highest PSBCHS-RSRP result (priority group 2); + - 7> UEs of which SLSSID is 337 and *inCoverage*, included in the *MasterInformationBlockSidelink* message received from this UE, is set to *false*, starting with the UE with the highest PSBCH-RSRP result (priority group 2); + - 7> Other UEs, starting with the UE with the highest PSBCH-RSRP result (priority group 3); +- 1> else if more than one frequency is selected for NR sidelink communication: +- 2> if *sl-SyncFreqList* is included in *RRReconfiguration* or in *SIB12*, and includes at least one of the concerned frequency(ies) + - 3> if the concerned frequency(ies) are included in *sl-FreqInfoToAddModList/sl-FreqInfoToAddModListExt* in *sl-ConfigDedicatedNR* within *RRReconfiguration* message or included in *sl-ConfigCommonNR* within *SIB12*, and *sl-SyncPriority* is configured for the concerned frequency(ies) and set to *gnbEnb*: + - 4> select one frequency from the concerned frequency(ies) which are included in *sl-SyncFreqList* as the synchronisation carrier frequency; + - 4> select a cell in accordance with the synchronisation carrier frequency as the synchronization reference source as defined in 5.8.6.3: + - 3> else if the concerned frequency(ies) are included in *sl-FreqInfoToAddModList/sl-FreqInfoToAddModListExt* in *sl-ConfigDedicatedNR* within *RRReconfiguration* message or included in *sl-ConfigCommonNR* within *SIB12*, and *sl-SyncPriority* for concerned frequency(ies) are not configured or are set to *gnss*, and GNSS is reliable in accordance with TS 38.101-1 [15] and TS 38.133 [14]; or if the concerned frequency(ies) are included in *SL-PreconfigurationNR*, and *sl-SyncPriority* in *SidelinkPreconfigNR* is set to *gnss* and GNSS is reliable in accordance with TS 38.101-1 [15] and TS 38.133 [14]: + - 4> select one frequency from the concerned frequency(ies) which are included in *sl-SyncFreqList* as the synchronisation carrier frequency; + +- 4> select GNSS in accordance with the synchronisation carrier frequency as the synchronization reference source; +- 3> else: + - 4> perform a full search (i.e. covering all subframes and all possible SLSSIDs) to detect candidate SLSS, in accordance with TS 38.133 [14] + - 4> when evaluating the one or more detected SLSSIDs, apply layer 3 filtering as specified in 5.5.3.2 using the preconfigured *sl-filterCoefficient*, before using the PSBCH-RSRP measurement results; + - 4> if the UE has selected a SyncRef UE: + - 5> if the PSBCH-RSRP of the strongest candidate SyncRef UE exceeds the minimum requirement TS 38.133 [14] by *sl-SyncRefMinHyst* and the strongest candidate SyncRef UE belongs to the same priority group as the current SyncRef UE and the PSBCH-RSRP of the strongest candidate SyncRef UE exceeds the PSBCH-RSRP of the current SyncRef UE by *syncRefDiffHyst*; or + - 5> if the PSBCH-RSRP of the candidate SyncRef UE exceeds the minimum requirement TS 38.133 [14] by *sl-SyncRefMinHyst* and the candidate SyncRef UE belongs to a higher priority group than the current SyncRef UE; or + - 5> if GNSS becomes reliable in accordance with TS 38.101-1 [15] and TS 38.133 [14], and GNSS belongs to a higher priority group than the current SyncRef UE; or + - 5> if a cell is detected and gNB/eNB (if *sl-NbAsSync* is set to *true*) belongs to a higher priority group than the current SyncRef UE; or + - 5> if the PSBCH-RSRP of the current SyncRef UE is less than the minimum requirement defined in TS 38.133 [14]: + - 6> consider no SyncRef UE to be selected; + - 4> if the UE has selected GNSS as the synchronization reference for NR sidelink communication/discovery: + - 5> if the PSBCH-RSRP of the candidate SyncRef UE exceeds the minimum requirement defined in TS 38.133 [14] by *sl-SyncRefMinHyst* and the candidate SyncRef UE belongs to a higher priority group than GNSS; or + - 5> if GNSS becomes not reliable in accordance with TS 38.101-1 [15] and TS 38.133 [14]: + - 6> consider GNSS not to be selected; + - 4> if the UE has selected cell as the synchronization reference for NR sidelink communication/discovery: + - 5> if the PSBCH-RSRP of the candidate SyncRef UE exceeds the minimum requirement defined in TS 38.133 [14] by *sl-SyncRefMinHyst* and the candidate SyncRef UE belongs to a higher priority group than gNB/eNB; or + - 5> if the selected cell is not detected: + - 6> consider the cell not to be selected; + - 4> if the UE has not selected any synchronization reference: + - 5> if the UE detects one or more SLSSIDs for which the PSBCH-RSRP exceeds the minimum requirement defined in TS 38.133 [14] by *sl-SyncRefMinHyst* and for which the UE received the corresponding *MasterInformationBlockSidelink* message (candidate SyncRef UEs), or if the UE detects GNSS that is reliable in accordance with TS 38.101-1 [15] and TS 38.133 [14], or if the UE detects a cell, + - 6> select the synchronisation reference source(s) on each concerned frequency which is included in *sl-SyncFreqList* according to the following priority group order; + +- 6> select the frequency with the highest synchronisation reference source priority as the synchronisation carrier frequency, according to the following priority group order, and consider the synchronisation reference source (i.e. eNB/gNB, GNSS or SyncRef UE) that selected on the synchronisation carrier frequency as the synchronization reference: + - 7> if *sl-SyncPriority* corresponding to the concerned frequency is set to *gnbEnb*: + - 8> UEs of which SLSSID is part of the set defined for in coverage, and *inCoverage*, included in the *MasterInformationBlockSidelink* message received from this UE, is set to *true*, starting with the UE with the highest PSBCH-RSRP result (priority group 1); + - 8> UE of which SLSSID is part of the set defined for in coverage, and *inCoverage*, included in the *MasterInformationBlockSidelink* message received from this UE, is set to *false*, starting with the UE with the highest PSBCH-RSRP result (priority group 2); + - 8> GNSS that is reliable in accordance with TS 38.101-1 [15] and TS 38.133 [14] (priority group 3); + - 8> UEs of which SLSSID is 0, and *inCoverage*, included in the *MasterInformationBlockSidelink* message received from this UE, is set to *true*, or of which SLSSID is 0 and SLSS is transmitted on slot(s) indicated by *sl-SSB-TimeAllocation3*, starting with the UE with the highest PSBCH-RSRP result (priority group 4); + - 8> UEs of which SLSSID is 0 and SLSS is not transmitted on slot(s) indicated by *sl-SSB-TimeAllocation3*, and *inCoverage*, included in the *MasterInformationBlockSidelink* message received from this UE, is set to *false*, starting with the UE with the highest PSBCH-RSRP result (priority group 5); + - 8> UEs of which SLSSID is 337 and *inCoverage*, included in the *MasterInformationBlockSidelink* message received from this UE, is set to *false*, starting with the UE with the highest PSBCH-RSRP result (priority group 5); + - 8> Other UEs, starting with the UE with the highest PSBCH-RSRP result (priority group 6); + - 7> if *sl-SyncPriority* corresponding to the concerned frequency is set to *gnss*, and *sl-NbAsSync* is set to *true*: + - 8> UEs of which SLSSID is 0, and *inCoverage*, included in the *MasterInformationBlockSidelink* message received from this UE, is set to *true*, or of which SLSSID is 0 and SLSS is transmitted on slot(s) indicated by *sl-SSB-TimeAllocation3*, starting with the UE with the highest PSBCH-RSRP result (priority group 1); + - 8> UEs of which SLSSID is 0 and SLSS is not transmitted on slot(s) indicated by *sl-SSB-TimeAllocation3*, and *inCoverage*, included in the *MasterInformationBlockSidelink* message received from this UE, is set to *false*, starting with the UE with the highest PSBCH-RSRP result (priority group 2); + - 8> UEs of which SLSSID is 337 and *inCoverage*, included in the *MasterInformationBlockSidelink* message received from this UE, is set to *false*, starting with the UE with the highest PSBCH-RSRP result (priority group 2); + - 8> the cell detected by the UE as defined in 5.8.6.3 (priority group 3); + - 8> UEs of which SLSSID is part of the set defined for in coverage, and *inCoverage*, included in the *MasterInformationBlockSidelink* message received from this UE, is set to *true*, starting with the UE with the highest PSBCH-RSRP result (priority group 4); + - 8> UE of which SLSSID is part of the set defined for in coverage, and *inCoverage*, included in the *MasterInformationBlockSidelink* message received from this UE, is set to *false*, starting with the UE with the highest PSBCH-RSRP result (priority group 5); + - 8> Other UEs, starting with the UE with the highest S-RSRP result (priority group 6); + +- 7> if *sl-SyncPriority* corresponding to the concerned frequency is set to *gnss*, and *sl-NbAsSync* is set to *false*: + - 8> UEs of which SLSSID is 0, and *inCoverage*, included in the *MasterInformationBlockSidelink* message received from this UE, is set to *true*, or of which SLSSID is 0 and SLSS is transmitted on slot(s) indicated by *sl-SSB-TimeAllocation3*, starting with the UE with the highest PSBCH-RSRP result (priority group 1); + - 8> UEs of which SLSSID is 0 and SLSS is not transmitted on slot(s) indicated by *sl-SSB-TimeAllocation3*, and *inCoverage*, included in the *MasterInformationBlockSidelink* message received from this UE, is set to *false*, starting with the UE with the highest PSBCH-RSRP result (priority group 2); + - 8> UEs of which SLSSID is 337 and *inCoverage*, included in the *MasterInformationBlockSidelink* message received from this UE, is set to *false*, starting with the UE with the highest PSBCH-RSRP result (priority group 2); + - 8> Other UEs, starting with the UE with the highest PSBCH-RSRP result (priority group 3); + +NOTE 2: How the UE achieves subframe boundary alignment between V2X sidelink communication and NR sidelink communication/discovery (if both are performed by the UE) is as specified in TS 38.213, clause 16.7. + +#### 5.8.6.3 Sidelink communication transmission reference cell selection + +A UE capable of NR sidelink communication/discovery that is configured by upper layers to transmit NR sidelink communication/discovery shall: + +- 1> for the frequency used to transmit NR sidelink communication/discovery, select a cell to be used as reference for synchronization in accordance with the following: + - 2> if the frequency concerns the primary frequency: + - 3> use the PCell or the serving cell as reference; + - 2> else if the frequency concerns a secondary frequency: + - 3> use the concerned SCell as reference; + - 2> else if the UE is in coverage of the concerned frequency: + - 3> use the DL frequency paired with the one used to transmit NR sidelink communication/discovery as reference; + - 2> else (i.e., out of coverage on the concerned frequency): + - 3> use the PCell or the serving cell as reference, if needed; + +### 5.8.7 Sidelink communication reception + +A UE capable of NR sidelink communication that is configured by upper layers to receive NR sidelink communication shall: + +- 1> if the conditions for NR sidelink communication operation as defined in 5.8.2 are met: + - 2> if the frequency used for NR sidelink communication is included in *sl-FreqInfoToAddModList/sl-FreqInfoToAddModListExt* in *RRReconfiguration* message or *sl-FreqInfoList/sl-FreqInfoListSizeExt* included in *SIB12*: + - 3> if the UE is configured with *sl-RxPool* included in *RRReconfiguration* message with *reconfigurationWithSync* (i.e. handover): + - 4> configure lower layers to monitor sidelink control information and the corresponding data using the pool(s) of resources indicated by *sl-RxPool*; + +- 3> else if the cell chosen for NR sidelink communication provides *SIB12*: + - 4> configure lower layers to monitor sidelink control information and the corresponding data using the pool(s) of resources indicated by *sl-RxPool* in *SIB12*; +- 2> else: + - 3> configure lower layers to monitor sidelink control information and the corresponding data using the pool(s) of resources that were preconfigured by *sl-RxPool* in *SL-PreconfigurationNR*, as defined in clause 9.3. + +### 5.8.8 Sidelink communication transmission + +A UE capable of NR sidelink communication that is configured by upper layers to transmit NR sidelink communication and has related data to be transmitted shall: + +- 1> if the conditions for NR sidelink communication operation as defined in 5.8.2 are met: + - 2> if the frequency used for NR sidelink communication is included in *sl-FreqInfoToAddModList/sl-FreqInfoToAddModListExt* in *sl-ConfigDedicatedNR* within *RRReconfiguration* message or included in *sl-ConfigCommonNR* within *SIB12*: + - 3> if the UE is in *RRC\_CONNECTED* and uses the frequency included in *sl-ConfigDedicatedNR* within *RRReconfiguration* message: + - 4> if the UE acting as U2U Relay UE is performing U2U Relay Communication with integrated Discovery as specified in TS 23.304[65] and *sl-DiscConfig* is included in *RRReconfiguration*, and if the NR sidelink U2U Relay UE threshold conditions as specified in 5.8.16.2 are met based on *sl-RelayUE-ConfigU2U*; or + - 4> if the UE is performing NR sidelink communication other than U2U Relay Communication with integrated Discovery: + +NOTE 0: For U2U Relay UE, it can be up to UE implementation on cross-layer interaction for the AS layer condition check for Direct Communication Request message with integrated discovery forwarding. + +- 5> if the UE is configured with *sl-ScheduledConfig*: + - 6> if T310 for MCG or T311 is running; and if *sl-TxPoolExceptional* is included in *sl-FreqInfoList/sl-FreqInfoListSizeExt* for the concerned frequency in *SIB12* or included in *sl-ConfigDedicatedNR* in *RRReconfiguration*; or + - 6> if T301 is running and the cell on which the UE initiated RRC connection re-establishment provides *SIB12* including *sl-TxPoolExceptional* for the concerned frequency; or + - 6> if T304 for MCG is running and the UE is configured with *sl-TxPoolExceptional* included in *sl-ConfigDedicatedNR* for the concerned frequency in *RRReconfiguration*: + - 7> configure lower layers to perform the sidelink resource allocation mode 2 based on random selection using the pool of resources indicated by *sl-TxPoolExceptional* as defined in TS 38.321 [3]; + - 6> else: + - 7> configure lower layers to perform the sidelink resource allocation mode 1 for NR sidelink communication; + - 6> if T311 is running, configure the lower layers to release the resources indicated by *rrc-ConfiguredSidelinkGrant* (if any); +- 5> if the UE is configured with *sl-UE-SelectedConfig*: + - 6> if a result of full/partial sensing, if selected and is allowed by *sl-AllowedResourceSelectionConfig*, on the resources configured in *sl-TxPoolSelectedNormal* for the concerned frequency included in *sl-ConfigDedicatedNR* within *RRReconfiguration* is not available in accordance with TS 38.214 [19]; + +- 7> if *sl-TxPoolExceptional* for the concerned frequency is included in *RRReconfiguration*; or +- 7> if the PCell provides *SIB12* including *sl-TxPoolExceptional* in *sl-FreqInfoList/sl-FreqInfoListSizeExt* for the concerned frequency: + - 8> configure lower layers to perform the sidelink resource allocation mode 2 based on random selection using the pool of resources indicated by *sl-TxPoolExceptional* as defined in TS 38.321 [3]; +- 6> else, if the *sl-TxPoolSelectedNormal* for the concerned frequency is included in the *sl-ConfigDedicatedNR* within *RRReconfiguration*: + - 7> configure lower layers to perform the sidelink resource allocation mode 2 based on resource selection operation according to *sl-AllowedResourceSelectionConfig* (as defined in TS 38.321 [3] and TS 38.214 [19]) using the pools of resources indicated by *sl-TxPoolSelectedNormal* for the concerned frequency; +- 3> else: + - 4> if the cell chosen for NR sidelink communication transmission provides *SIB12*: + - 5> if the UE acting as U2U Relay UE is performing U2U Relay communication with integrated Discovery as specified in TS 23.304[65], and if the NR sidelink U2U Relay UE threshold conditions as specified in 5.8.16.2 are met based on *sl-RelayUE-ConfigCommonU2U* in *SIB12*; or + - 5> if the UE is performing NR sidelink communication other than U2U Relay Communication with integrated Discovery: + - 6> if *SIB12* includes *sl-TxPoolSelectedNormal* for the concerned frequency, and a result of full/partial sensing, if selected and is allowed by *sl-AllowedResourceSelectionConfig*, on the resources configured in the *sl-TxPoolSelectedNormal* is available in accordance with TS 38.214 [19] or random selection, if allowed by *sl-AllowedResourceSelectionConfig*, is selected: + - 7> configure lower layers to perform the sidelink resource allocation mode 2 based on resource selection operation according to *sl-AllowedResourceSelectionConfig* using the pools of resources indicated by *sl-TxPoolSelectedNormal* for the concerned frequency as defined in TS 38.321 [3]; + - 6> else if *SIB12* includes *sl-TxPoolExceptional* for the concerned frequency: + - 7> from the moment the UE initiates RRC connection establishment or RRC connection resume, until receiving an *RRReconfiguration* including *sl-ConfigDedicatedNR*, or receiving an *RRRelease* or an *RRReject*; or + - 7> if a result of full/partial sensing, if selected and is allowed by *sl-AllowedResourceSelectionConfig*, on the resources configured in *sl-TxPoolSelectedNormal* for the concerned frequency in *SIB12* is not available in accordance with TS 38.214 [19]: + - 8> configure lower layers to perform the sidelink resource allocation mode 2 based on random selection (as defined in TS 38.321 [3]) using the pool of resources indicated by *sl-TxPoolExceptional* for the concerned frequency; + - 3> else: + - 3> if the UE acting as U2U Relay UE is performing U2U Relay communication with integrated Discovery as specified in TS 23.304[65], and if the NR sidelink U2U Relay UE threshold conditions as specified in 5.8.16.2 are met based on *sl-RelayUE-PreconfigU2U* in *SidelinkPreconfigNR*; or + - 3> if the UE is performing NR sidelink communication other than U2U Relay Communication with integrated Discovery: + - 4> configure lower layers to perform the sidelink resource allocation mode 2 based on resource selection operation according to *sl-AllowedResourceSelectionConfig* (as defined in TS 38.321 [3] and TS 38.214 [19]) using the pools of resources indicated by *sl-TxPoolSelectedNormal* in *SidelinkPreconfigNR* for the concerned frequency. + +- NOTE 1: The UE continues to use resources configured in *rrc-ConfiguredSidelinkGrant* (while T310 is running) until it is released (i.e. until T310 has expired). The UE does not use sidelink configured grant type 2 resources while T310 is running. +- NOTE 2: In case of RRC reconfiguration with sync, the UE uses resources configured in *rrc-ConfiguredSidelinkGrant* (while T304 on the MCG is running) if provided by the target cell. +- NOTE 3: It is up to UE implementation to determine, in accordance with TS 38.321[3], which resource pool to use if multiple resource pools are configured, and which resource allocation scheme is used in the AS based on UE capability (for a UE in RRC\_IDLE/RRC\_INACTIVE) and the allowed resource schemes *sl-AllowedResourceSelectionConfig* in the resource pool configuration. +- NOTE 4: In case that the network does not provide resource pools in *SIB12*, a UE which is out of coverage, will be unable to obtain sidelink resources to send the first UL RRC message. + +If configured to perform sidelink resource allocation mode 2, the UE capable of NR sidelink communication that is configured by upper layers to transmit NR sidelink communication shall perform resource selection operation according to *sl-AllowedResourceSelectionConfig* on all pools of resources which may be used for transmission of the sidelink control information and the corresponding data. The pools of resources are indicated by *SidelinkPreconfigNR*, *sl-TxPoolSelectedNormal* in *sl-ConfigDedicatedNR*, or *sl-TxPoolSelectedNormal* in *SIB12* for the concerned frequency, as configured above. + +### 5.8.9 Sidelink RRC procedure + +#### 5.8.9.1 Sidelink RRC reconfiguration + +##### 5.8.9.1.1 General + +![Sequence diagram for successful Sidelink RRC reconfiguration between two UEs.](350dece6293a0ac3d4c9e4bf41eefa5d_img.jpg) + +``` + +sequenceDiagram + participant UE1 as UE + participant UE2 as UE + Note left of UE1: + UE1->>UE2: RRCReconfigurationSidelink + Note right of UE2: + UE2-->>UE1: RRCReconfigurationCompleteSidelink + +``` + +The diagram shows two vertical lifelines labeled 'UE'. A solid horizontal arrow labeled *RRCReconfigurationSidelink* points from the left UE to the right UE. A dashed horizontal arrow labeled *RRCReconfigurationCompleteSidelink* points from the right UE back to the left UE. + +Sequence diagram for successful Sidelink RRC reconfiguration between two UEs. + +Figure 5.8.9.1.1-1: Sidelink RRC reconfiguration, successful + +![Sequence diagram for failed Sidelink RRC reconfiguration between two UEs.](6984a27b2b89e0995d5216ec29b41d1c_img.jpg) + +``` + +sequenceDiagram + participant UE1 as UE + participant UE2 as UE + Note left of UE1: + UE1->>UE2: RRCReconfigurationSidelink + Note right of UE2: + UE2-->>UE1: RRCReconfigurationFailureSidelink + +``` + +The diagram shows two vertical lifelines labeled 'UE'. A solid horizontal arrow labeled *RRCReconfigurationSidelink* points from the left UE to the right UE. A dashed horizontal arrow labeled *RRCReconfigurationFailureSidelink* points from the right UE back to the left UE. + +Sequence diagram for failed Sidelink RRC reconfiguration between two UEs. + +Figure 5.8.9.1.1-2: Sidelink RRC reconfiguration, failure + +The purpose of this procedure is to modify a PC5-RRC connection, e.g. to establish/modify/release sidelink DRBs or additional sidelink RLC bearer or PC5 Relay RLC channels, to add/modify/release sidelink carrier, to (re-)configure NR sidelink measurement and reporting, to (re-)configure sidelink CSI reference signal resources, to (re)configure CSI reporting latency bound, to (re)configure sidelink DRX, to (re-)configure the latency bound of SL Inter-UE coordination report, and to indicate the SFN-DFN offset. + +The UE may initiate the sidelink RRC reconfiguration procedure and perform the operation in clause 5.8.9.1.2 on the corresponding PC5-RRC connection in following cases: + +- the release of sidelink DRBs associated with the peer UE, or L2 U2U Relay UE and peer L2 U2U Remote UE in case of L2 U2U Relay operation, as specified in clause 5.8.9.1a.1; +- the establishment of sidelink DRBs associated with the peer UE, or L2 U2U Relay UE and peer L2 U2U Remote UE in case of L2 U2U Relay operation, as specified in clause 5.8.9.1a.2; +- the modification for the parameters included in *SLRB-Config* of sidelink DRBs associated with the peer UE, as specified in clause 5.8.9.1a.2; +- the release of additional sidelink RLC bearer associated with the peer UE, as specified in clause 5.8.9.1a.5; +- the establishment of additional sidelink RLC bearer associated with the peer UE, as specified in clause 5.8.9.1a.6; +- the modification for the parameters included in *SL-RLC-BearerConfig* of additional sidelink RLC bearer associated with the peer UE, as specified in clause 5.8.9.1a.6; +- the release of PC5 Relay RLC channels for L2 U2N/U2U Relay UE and Remote UE, as specified in clause 5.8.9.7.1; +- the establishment of PC5 Relay RLC channels for L2 U2N/U2U Relay UE and Remote UE, as specified in clause 5.8.9.7.2; +- the modification for the parameters included in *SL-RLC-ChannelConfigPC5* of PC5 Relay RLC channels for L2 U2N/U2U Relay UE and Remote UE, as specified in clause 5.8.9.7.2; +- the release of sidelink carrier associated with the peer UE, as specified in clause 5.8.9.1b.1; +- the addition of sidelink carrier associated with the peer UE, as specified in clause 5.8.9.1b.2; +- the modification of sidelink carrier associated with the peer UE, as specified in clause 5.8.9.1b.2; +- the (re-)configuration of the peer UE to perform NR sidelink measurement and report. +- the (re-)configuration of the sidelink CSI reference signal resources and CSI reporting latency bound; +- the (re-)configuration of the peer UE to perform sidelink DRX; +- the (re-)configuration of the latency bound of SL Inter-UE coordination report; +- the (re-)configuration of the local UE ID for L2 U2U Remote UEs by L2 U2U Relay UE. +- the response to the request in a *RemoteUEInformationSidelink* message for the SFN-DFN offset from the L2 U2N Remote UE; +- the change in the value of the SFN-DFN offset at the L2 U2N Relay UE. + +NOTE: It is up to L2 U2N Relay UE implementation to determine when the SFN-DFN offset has changed in value to a degree requiring an update to be sent to the L2 U2N Remote UE. + +In RRC\_CONNECTED, the UE applies the NR sidelink communications parameters provided in *RRReconfiguration* (if any). In RRC\_IDLE or RRC\_INACTIVE, the UE applies the NR sidelink communications parameters provided in system information (if any). For other cases, UEs apply the NR sidelink communications parameters provided in *SidelinkPreconfigNR* (if any). When UE performs state transition between above three cases, the UE applies the NR sidelink communications parameters provided in the new state, after acquisition of the new configurations. Before acquisition of the new configurations, UE continues applying the NR sidelink communications parameters provided in the old state. + +##### 5.8.9.1.2 Actions related to transmission of *RRReconfigurationSidelink* message + +The UE shall set the contents of *RRReconfigurationSidelink* message as follows: + +- 1> for each sidelink DRB that is to be released, according to clause 5.8.9.1a.1.1, due to configuration by *sl-ConfigDedicatedNR*, *SIB12*, *SidelinkPreconfigNR* or by upper layers: +- 2> set the entry included in the *slrb-ConfigToReleaseList* corresponding to the sidelink DRB; + +- 1> for each sidelink DRB that is to be established or modified, according to clause 5.8.9.1a.2.1, due to receiving *sl-ConfigDedicatedNR*, *SIB12* or *SidelinkPreconfigNR*: + - 2> if the sidelink DRB is a per-hop sidelink DRB (i.e. the UE is not acting as a L2 U2U Remote UE): + - 3> if a sidelink DRB is to be established: + - 4> assign a new logical channel identity for the logical channel to be associated with the sidelink DRB and set *sl-MAC-LogicalChannelConfigPC5* in the *SLRB-Config* to include the new logical channel identity; + - 3> set the *SLRB-Config* included in the *slrb-ConfigToAddModList*, according to the received *sl-RadioBearerConfig* and *sl-RLC-BearerConfig* corresponding to the sidelink DRB; + - 2> else if the sidelink DRB is an end-to-end sidelink DRB (i.e. the UE is acting as a L2 U2U Remote UE, and configure peer L2 U2U Remote UE with end-to-end SDAP and PDCP, or provide the L2 Relay UE with the QoS flow to end-to-end DRB mapping): + - 3> if the UE is in RRC\_CONNECTED: + - 4> set the *SLRB-Config* included in the *slrb-ConfigToAddModList*, according to the received *sl-RadioBearerConfig* in *sl-ConfigDedicatedNR*; + - 3> else if the UE is in RRC\_IDLE/RRC\_INACTIVE: + - 4> set the *SLRB-Config* included in the *slrb-ConfigToAddModList*, which is derived by end-to-end QoS profile, according to the *sl-RadioBearerConfig* in *SIB12*; + - 3> if the UE is out of coverage: + - 4> set the *SLRB-Config* included in the *slrb-ConfigToAddModList*, which is derived by end-to-end QoS profile, according to the *sl-RadioBearerConfig* in *SidelinkPreconfigNR*; +- 1> for each additional sidelink RLC bearer that is to be released, according to clause 5.8.9.1a.5.1, due to configuration by *sl-ConfigDedicatedNR*, *SIB12*, *SidelinkPreconfigNR* or by upper layers: + - 2> set the entry included in the *sl-RLC-BearerToReleaseList* corresponding to the additional sidelink RLC bearer; +- 1> for each additional sidelink RLC bearer that is to be established or modified, according to clause 5.8.9.1a.6.1, due to receiving *sl-ConfigDedicatedNR*, *SIB12* or *SidelinkPreconfigNR*: + - 2> if an additional sidelink RLC bearer is to be established: + - 3> assign a new logical channel identity for the logical channel to be associated with the sidelink DRB and set *sl-MAC-LogicalChannelConfigPC5* in the *SL-RLC-BearerConfig* to include the new logical channel identity; + - 2> set the *SL-RLC-BearerConfig* included in the *sl-RLC-BearerToAddModList*, according to the received *sl-RadioBearerConfig* and *sl-RLC-BearerConfig* corresponding to the additional sidelink RLC bearer; +- 1> set the entry included in the *sl-CarrierToReleaseList* corresponding to the sidelink carrier(s) for which MAC entity indicates that the maximum number of consecutive HARQ DTX for a specific destination has been reached; +- 1> set the entry included in the *sl-CarrierToAddModList* corresponding to the sidelink carrier, taking into account of at least carrier(s) mapped to the sidelink QoS flow(s) configured by the upper layer, carriers configured in *sl-ConfigDedicatedNR*, *SIB12* or *SidelinkPreconfigNR*, and carrier(s) supported by both UEs; +- 1> set the *sl-MeasConfig* as follows: + - 2> If the frequency used for NR sidelink communication is included in *sl-FreqInfoToAddModList/sl-FreqInfoToAddModListExt* in *sl-ConfigDedicatedNR* within *RRCEconfiguration* message or included in *sl-ConfigCommonNR* within *SIB12*: + - 3> if UE is in RRC\_CONNECTED: + +- 4> set the *sl-MeasConfig* according to stored NR sidelink measurement configuration information for this destination; + - 3> if UE is in RRC\_IDLE or RRC\_INACTIVE: + - 4> set the *sl-MeasConfig* according to stored NR sidelink measurement configuration received from *SIB12*; + - 2> else: + - 3> set the *sl-MeasConfig* according to the *sl-MeasPreConfig* in *SidelinkPreconfigNR*; + - 1> set the *sl-LatencyBoundIUC-Report*; + - 1> start timer T400 for the destination; + - 1> set the *sl-CSI-RS-Config*; + - 1> set the *sl-LatencyBoundCSI-Report*; + - 1> set the *sl-ResetConfig*; +- NOTE 1: Whether/how to set the parameters included in *sl-LatencyBoundIUC-Report*, *sl-CSI-RS-Config*, *sl-LatencyBoundCSI-Report* and *sl-ResetConfig* is up to UE implementation. +- 1> set the *sl-DRX-ConfigUC-PC5* as follows: + - 2> If the frequency used for NR sidelink communication is included in *sl-FreqInfoToAddModList/sl-FreqInfoToAddModListExt* in *sl-ConfigDedicatedNR* within *RRCReconfiguration* message or included in *sl-ConfigCommonNR* within *SIB12*: + - 3> if UE is in RRC\_CONNECTED and if *sl-ScheduledConfig* is included in *sl-ConfigDedicatedNR* within *RRCReconfiguration*: + - 4> set the *sl-DRX-ConfigUC-PC5* according to stored NR sidelink DRX configuration information for this destination; +- NOTE 2: If UE is in RRC\_IDLE or in RRC\_INACTIVE or out of coverage, or in RRC\_CONNECTED and *sl-UE-SelectedConfig* is included in *sl-ConfigDedicatedNR* within *RRCReconfiguration*, it is up to UE implementation to set the *sl-DRX-ConfigUC-PC5*. +- 1> for each PC5 Relay RLC channel that is to be released due to configuration by *sl-ConfigDedicatedNR*: + - 2> set the *SL-RLC-ChannelID* corresponding to the PC5 Relay RLC channel in the *sl-RLC-ChannelToReleaseListPC5*; + - 1> for each PC5 Relay RLC channel that is to be established or modified due to receiving *sl-ConfigDedicatedNR*: + - 2> if a PC5 Relay RLC channel is to be established: + - 3> assign a new logical channel identity for the logical channel to be associated with the PC5 Relay RLC channel and set *sl-MAC-LogicalChannelConfigPC5* in the *SL-RLC-ChannelConfigPC5* to include the new logical channel identity; + - 2> set the *SL-RLC-ChannelConfigPC5* included in the *sl-RLC-ChannelToAddModListPC5* according to the received *SL-RLC-ChannelConfig* corresponding to the PC5 Relay RLC channel, including setting *sl-RLC-ChannelID-PC5* to the same value of *sl-RLC-ChannelID* received in *SL-RLC-ChannelConfig*; + - 1> if the UE is operating as a L2 U2N Relay UE: + - 2> if the destination UE is a L2 U2N Remote UE that requested the SFN-DFN offset in a previous *RemoteUEInformationSidelink* message: + - 3> if the SFN-DFN offset has changed since a previous transmission of the *RRCReconfigurationSidelink* message, or no previous transmission of the *RRCReconfigurationSidelink* message has occurred since the reception of the *RemoteUEInformationSidelink* message: + +- 4> set the *sl-SFN-DFN-Offset* according to the relation between the SFN timeline of the PCell and the DFN timeline; +- 1> if the UE is acting as L2 U2U Relay UE, and if the procedure is initiated to configure local ID to the connected L2 U2U Remote UEs: + - 2> if the local ID pair is to be assigned or modified for an end-to-end PC5 connection, and if both the PC5-RRC connection with L2 U2U Remote UE and the PC5-RRC connection with peer L2 U2U Remote UE are successfully established: + - 3> include an entry in *sl-LocalID-PairToAddModList*, and set the fields as below: + - 4> according to association between User Info and L2 ID as specified in TS 23.304 [65], set *sl-RemoteUE-LocalIdentity* to include the new local UE ID, and set *sl-RemoteUE-L2Identity* to include the source L2 ID of L2 U2U Remote UE in the *SL-SRAP-ConfigPC5*, if needed; + - 4> according to association between User Info and L2 ID as specified in TS 23.304 [65], set *sl-PeerRemoteUE-LocalIdentity* to include the new local UE ID, and and set *sl-PeerRemoteUE-L2Identity* to include the destination L2 ID of peer L2 U2U Remote UE in the *SL-SRAP-ConfigPC5*, if needed; + - 2> else if the local ID pair is to be released for an end-to-end PC5 connection: + - 3> include an entry in *sl-LocalID-PairToReleaseList*, with the value of *SL-DestinationIdentity* set to the destination L2 ID of the peer L2 U2U Remote UE; + - 1> if the UE is acting as L2 U2U Remote UE (i.e. Tx UE), and if the procedure is initiated to configure the first hop PC5 Relay RLC channel of an end-to-end sidelink DRB to the connected L2 U2N Relay UE (i.e. Rx UE), based on configuration in *SIB12* or *SidelinkPreconfigNR*; or + - 1> if the UE is acting as L2 U2U Relay UE (i.e. Tx UE) and is in *RRC\_IDLE* or in *RRC\_INACTIVE* or OoC, and if the procedure is initiated to configure the second hop PC5 Relay RLC channel to the connected L2 U2N Remote UE (i.e. Rx UE) based on configuration in *SIB12* or *SidelinkPreconfigNR*: + - 2> if a PC5 Relay RLC channel is to be established: + - 3> assign a new RLC channel ID and set *sl-RLC-ChannelID-PC5* in the *SL-RLC-ChannelConfigPC5* to include the new RLC channel ID; + - 3> assign a new logical channel identity for the logical channel to be associated with the PC5 Relay RLC channel and set *sl-MAC-LogicalChannelConfigPC5* in the *SL-RLC-ChannelConfigPC5* to include the new logical channel identity; + - 3> if the UE is in *RRC\_IDLE* or in *RRC\_INACTIVE*: + - 4> set the *SL-RLC-ChannelConfigPC5* included in the *sl-RLC-ChannelToAddModListPC5* according to the *SL-RLC-BearerConfig* derived based on the per-hop QoS of the end-to-end SLRB according to *SIB12*; + - 3> else if the UE is out of coverage: + - 4> set the *SL-RLC-ChannelConfigPC5* included in the *sl-RLC-ChannelToAddModListPC5* according to the *SL-RLC-BearerConfig* derived based on the per-hop QoS of the SLRB according to *SidelinkPreconfigNR*; + +NOTE 3: IF UE is in *RRC\_IDLE* or in *RRC\_INACTIVE* or out of coverage, how to merge the split per-flow QoS on the first/second hop into a per-SLRB level QoS for RLC channel configuration derivation is up to UE implementation. + +The UE shall submit the *RRCREconfigurationSidelink* message to lower layers for transmission. + +##### 5.8.9.1.3 Reception of an *RRCREconfigurationSidelink* by the UE + +The UE shall perform the following actions upon reception of the *RRCREconfigurationSidelink*: + +- 1> if the *RRCREconfigurationSidelink* includes the *sl-ResetConfig*: + +- 2> perform the sidelink reset configuration procedure as specified in 5.8.9.1.10; +- 1> if the *RRCREconfigurationSidelink* includes the *slrb-ConfigToReleaseList*: + - 2> for each entry value included in the *slrb-ConfigToReleaseList* that is part of the current UE sidelink configuration; + - 3> perform the sidelink DRB release procedure, according to clause 5.8.9.1a.1; +- 1> if the *RRCREconfigurationSidelink* includes the *slrb-ConfigToAddModList*: + - 2> for each *slrb-PC5-ConfigIndex* value included in the *slrb-ConfigToAddModList* that is not part of the current UE sidelink configuration: + - 3> if *sl-MappedQoS-FlowsToAddList* is included: + - 4> apply the *SL-PQFI* included in *sl-MappedQoS-FlowsToAddList*; + - 3> perform the sidelink DRB addition procedure, according to clause 5.8.9.1a.2; + - 2> for each *slrb-PC5-ConfigIndex* value included in the *slrb-ConfigToAddModList* that is part of the current UE sidelink configuration: + - 3> if *sl-MappedQoS-FlowsToAddList* is included: + - 4> add the *SL-PQFI* included in *sl-MappedQoS-FlowsToAddList* to the corresponding sidelink DRB; + - 3> if *sl-MappedQoS-FlowsToReleaseList* is included: + - 4> remove the *SL-PQFI* included in *sl-MappedQoS-FlowsToReleaseList* from the corresponding sidelink DRB; + - 3> if the sidelink DRB release conditions as described in clause 5.8.9.1a.1.1 are met: + - 4> perform the sidelink DRB release procedure according to clause 5.8.9.1a.1.2; + - 3> else if the sidelink DRB modification conditions as described in clause 5.8.9.1a.2.1 are met: + - 4> perform the sidelink DRB modification procedure according to clause 5.8.9.1a.2.2; +- 1> if the *RRCREconfigurationSidelink* includes the *sl-RLC-BearerToReleaseList*: + - 2> for each entry value included in the *sl-RLC-BearerToReleaseList* that is part of the current UE sidelink configuration; + - 3> perform the additional sidelink RLC bearer release procedure, according to clause 5.8.9.1a.5; +- 1> if the *RRCREconfigurationSidelink* includes the *sl-RLC-BearerToAddModList*: + - 2> for each *SL-RLC-BearerConfigIndex* value included in the *sl-RLC-BearerToAddModList* that is not part of the current UE sidelink configuration: + - 3> perform the additional sidelink RLC bearer addition procedure, according to clause 5.8.9.1a.6; + - 2> for each *SL-RLC-BearerConfigIndex* value included in the *sl-RLC-BearerToAddModList* that is part of the current UE sidelink configuration: + - 3> perform the additional sidelink RLC bearer modification procedure, according to clause 5.8.9.1a.6; +- 1> if the *RRCREconfigurationSidelink* includes the *sl-CarrierToReleaseList*: + - 2> for each entry value included in the *sl-CarrierToReleaseList* that is part of the current UE sidelink configuration; + - 3> perform the sidelink carrier release procedure, according to clause 5.8.9.1b.1; +- 1> if the *RRCREconfigurationSidelink* includes the *sl-CarrierToAddModList*: + +- 2> for each *sl-Carrier-Id* value included in the *sl-CarrierToAddModList* that is not part of the current UE sidelink configuration: + - 3> perform the sidelink carrier addition procedure, according to clause 5.8.9.1b.2; +- 2> for each *sl-Carrier-Id* value included in the *sl-CarrierToAddModList* that is part of the current UE sidelink configuration: + - 3> perform the carrier modification procedure, according to clause 5.8.9.1b.2; +- 1> if the *RRCREconfigurationSidelink* message includes the *sl-MeasConfig*: + - 2> perform the sidelink measurement configuration procedure as specified in 5.8.10; +- 1> if the *RRCREconfigurationSidelink* message includes the *sl-CSI-RS-Config*: + - 2> apply the sidelink CSI-RS configuration; +- 1> if the *RRCREconfigurationSidelink* message includes the *sl-LatencyBoundCSI-Report*: + - 2> apply the configured sidelink CSI report latency bound; +- 1> if the *RRCREconfigurationSidelink* includes the *sl-RLC-ChannelToReleaseListPC5*: + - 2> for each *SL-RLC-ChannelID* value included in the *sl-RLC-ChannelToReleaseListPC5* that is part of the current UE sidelink configuration; + - 3> perform the PC5 Relay RLC channel release procedure, according to clause 5.8.9.7.1; +- 1> if the *RRCREconfigurationSidelink* includes the *sl-RLC-ChannelToAddModListPC5*: + - 2> for each *sl-RLC-ChannelID-PC5* value included in the *sl-RLC-ChannelToAddModListPC5* that is not part of the current UE sidelink configuration: + - 3> perform the PC5 Relay RLC channel addition procedure, according to clause 5.8.9.7.2; + - 2> for each *sl-RLC-ChannelID-PC5* value included in the *sl-RLC-ChannelToAddModListPC5* that is part of the current UE sidelink configuration: + - 3> perform the PC5 Relay RLC channel modification procedure according to clause 5.8.9.7.2; +- 1> if the *RRCREconfigurationSidelink* message includes the *sl-DRX-ConfigUC-PC5*; and +- 1> if the UE accepts the *sl-DRX-ConfigUC-PC5*: + - 2> configure lower layers to perform sidelink DRX operation according to *sl-DRX-ConfigUC-PC5* for the associated destination as defined in TS 38.321 [3]; +- 1> if the *RRCREconfigurationSidelink* message includes the *sl-LatencyBoundIUC-Report*: + - 2> apply the configured sidelink IUC report latency bound; +- 1> if the *RRCREconfigurationSidelink* message includes the *sl-LocalID-PairToReleaseList* or *sl-LocalID-PairToAddModList*: + - 2> configure SRAP entity to perform NR sidelink L2 U2U relay operation accordingly for the end-to-end PC5 connection peer L2 U2U Remote UE as defined in TS 38.351 [65]; +- 1> if the *RRCREconfigurationSidelink* message includes the *sl-MappingToAddModListPC5* or *sl-MappingToReleaseListPC5*: + - 2> configure lower layers to perform NR sidelink L2 U2U relay operation according to mapping between end-to-end sidelink bearer of L2 U2U Remote UE and egress PC5 Relay RLC channel as defined in TS 38.351 [65]; +- 1> if the UE is unable to comply with (part of) the configuration included in the *RRCREconfigurationSidelink* (i.e. sidelink RRC reconfiguration failure): + +- 2> continue using the configuration used prior to the reception of the *RRCREconfigurationSidelink* message; +- 2> set the content of the *RRCREconfigurationFailureSidelink* message; +- 3> submit the *RRCREconfigurationFailureSidelink* message to lower layers for transmission; +- 1> if the *RRCREconfigurationSidelink* message includes the *sl-SFN-DFN-Offset*: + - 2> if the *sl-SFN-DFN-Offset* is set to *setup*: + - 3> apply the configured SFN-DFN time offset; + - 2> if the *sl-SFN-DFN-Offset* is set to *release*: + - 3> release the received *sl-SFN-DFN-Offset*; +- 1> else: + - 2> set the content of the *RRCREconfigurationCompleteSidelink* message; + - 3> if the UE rejects the sidelink DRX configuration *sl-DRX-ConfigUC-PC5* received from the peer UE: + - 4> include the *sl-DRX-ConfigReject* in the *RRCREconfigurationCompleteSidelink* message; + - 4> consider no sidelink DRX to be applied for the corresponding sidelink unicast communication; + - 3> submit the *RRCREconfigurationCompleteSidelink* message to lower layers for transmission; + +NOTE 1: When the same logical channel is configured with different RLC mode by another UE, the UE handles the case as sidelink RRC reconfiguration failure. + +NOTE 2: It is up to the UE implementation whether or not to indicate the rejection to the peer UE for a received sidelink DRX configuration. + +5.8.9.1.4 Void + +5.8.9.1.5 Void + +5.8.9.1.6 Void + +5.8.9.1.7 Void + +5.8.9.1.8 Reception of an *RRCREconfigurationFailureSidelink* by the UE + +The UE shall perform the following actions upon reception of the *RRCREconfigurationFailureSidelink*: + +- 1> stop timer T400 for the destination, if running; +- 1> continue using the configuration used prior to corresponding *RRCREconfigurationSidelink* message; +- 1> if UE is in *RRC\_CONNECTED*: + - 2> perform the sidelink UE information for NR sidelink communication procedure, as specified in 5.8.3.3 or clause 5.10.15 in TS 36.331 [10]; + +5.8.9.1.9 Reception of an *RRCREconfigurationCompleteSidelink* by the UE + +The UE shall perform the following actions upon reception of the *RRCREconfigurationCompleteSidelink*: + +- 1> stop timer T400 for the destination, if running; +- 1> consider the configurations in the corresponding *RRCREconfigurationSidelink* message to be applied. +- 2> if the *RRCREconfigurationCompleteSidelink* message includes the *sl-DRX-ConfigReject*: + - 3> consider no sidelink DRX to be applied for the corresponding sidelink unicast communication. + +##### 5.8.9.1.10 Sidelink reset configuration + +The UE shall: + +- 1> release/clear current sidelink radio configuration of this destination received in the *RRCReconfigurationSidelink*; +- 1> release the sidelink DRBs of this destination, in according to clause 5.8.9.1a.1; +- 1> release the additional sidelink RLC bearer of this destination, if configured, in according to clause 5.8.9.1a.5; +- 1> reset the sidelink specific MAC of this destination. + +NOTE 1: Sidelink radio configuration is not just the resource configuration but may include other configurations included in the *RRCReconfigurationSidelink* message except the sidelink DRBs of this destination. + +NOTE 2: After the sidelink DRB release procedure, UE may perform the sidelink DRB addition according to the current sidelink configuration of this destination, received in *sl-ConfigDedicatedNR*, *SIB12* and *SidelinkPreconfigNR*, according to clause 5.8.9.1a.2. + +#### 5.8.9.1a Sidelink radio bearer management + +##### 5.8.9.1a.1 Sidelink DRB release + +###### 5.8.9.1a.1.1 Sidelink DRB release conditions + +For NR sidelink communication, a sidelink DRB release is initiated in the following cases: + +- 1> for groupcast, broadcast and unicast, if *slrb-Uu-ConfigIndex* (if any) of the sidelink DRB is included in *sl-RadioBearerToReleaseList* in *sl-ConfigDedicatedNR*; or +- 1> for groupcast and broadcast, if no sidelink QoS flow with data indicated by upper layers is mapped to the sidelink DRB for transmission, which is (re)configured by receiving *SIB12* or *SidelinkPreconfigNR*; or +- 1> for groupcast, broadcast and unicast, if *SL-RLC-BearerConfigIndex* (if any) of the associated RLC entity(ies) (i.e., including the additional sidelink RLC bearer if applicable) for the sidelink DRB is included in *sl-RLC-BearerToReleaseList/sl-RLC-BearerToReleaseListSizeExt* in *sl-ConfigDedicatedNR*; or +- 1> for unicast, if no sidelink QoS flow with data indicated by upper layers is mapped to the sidelink DRB for transmission, which is (re)configured by receiving *SIB12* or *SidelinkPreconfigNR*, and if no sidelink QoS flow mapped to the sidelink DRB, which is (re)configured by receiving *RRCReconfigurationSidelink*, has data; or +- 1> for unicast, if *SLRB-PC5-ConfigIndex* (if any) of the sidelink DRB is included in *slrb-ConfigToReleaseList* in *RRCReconfigurationSidelink* or if *sl-ResetConfig* is included in *RRCReconfigurationSidelink*; or +- 1> for unicast, when the corresponding PC5-RRC connection is released due to sidelink RLF being detected, according to clause 5.8.9.3; or +- 1> for unicast, when the corresponding PC5-RRC connection is released due to upper layer request according to clause 5.8.9.5. + +###### 5.8.9.1a.1.2 Sidelink DRB release operations + +For each sidelink DRB, whose sidelink DRB release conditions are met as in clause 5.8.9.1a.1.1, the UE capable of NR sidelink communication that is configured by upper layers to perform NR sidelink communication shall: + +- 1> for groupcast and broadcast; or +- 1> for unicast, if the sidelink DRB release was triggered after the reception of the *RRCReconfigurationSidelink* message; or +- 1> for unicast, after receiving the *RRCReconfigurationCompleteSidelink* message, if the sidelink DRB release was triggered due to the configuration received within the *sl-ConfigDedicatedNR*, *SIB12*, *SidelinkPreconfigNR* or indicated by upper layers: + - 2> release the PDCP entity for NR sidelink communication associated with the sidelink DRB; + - 2> if SDAP entity for NR sidelink communication associated with this sidelink DRB is configured: + +- 3> indicate the release of the sidelink DRB to the SDAP entity associated with this sidelink DRB (TS 37.324 [24], clause 5.3.3); +- 2> release SDAP entities for NR sidelink communication, if any, that have no associated sidelink DRB as specified in TS 37.324 [24] clause 5.1.2; +- 1> for groupcast and broadcast; or +- 1> for unicast, after receiving the *RRCReconfigurationCompleteSidelink* message, if the sidelink DRB release was triggered due to the configuration received within the *sl-ConfigDedicatedNR*: + - 2> for each *sl-RLC-BearerConfigIndex* included in the received *sl-RLC-BearerToReleaseList/sl-RLC-BearerToReleaseListSizeExt* that is part of the current UE sidelink configuration: + - 3> release the RLC entity and the corresponding logical channel for NR sidelink communication, associated with the *sl-RLC-BearerConfigIndex*. +- 1> for unicast, if the sidelink DRB release was triggered due to the reception of the *RRCReconfigurationSidelink* message; or +- 1> for unicast, after receiving the *RRCReconfigurationCompleteSidelink* message, if the sidelink DRB release was triggered due to the configuration received within the *SIB12*, *SidelinkPreconfigNR* or indicated by upper layers: + - 2> release the RLC entity and the corresponding logical channel for NR sidelink communication associated with the sidelink DRB; + - 2> perform the sidelink UE information procedure in clause 5.8.3 for unicast if needed. +- 1> if the sidelink radio link failure is detected for a specific destination: + - 2> release the PDCP entity, RLC entity and the logical channel of the sidelink DRB for the specific destination. + +Editor's Note: FFS on how to release SL DRB on E2E and hop configuration for U2U relay. + +##### 5.8.9.1a.2 Sidelink DRB addition/modification + +###### 5.8.9.1a.2.1 Sidelink DRB addition/modification conditions + +For NR sidelink communication, a sidelink DRB addition is initiated only in the following cases: + +- 1> if any sidelink QoS flow is (re)configured by *sl-ConfigDedicatedNR*, *SIB12*, *SidelinkPreconfigNR* and is to be mapped to one sidelink DRB, which is not established; or +- 1> if any sidelink QoS flow is (re)configured by *RRCReconfigurationSidelink* and is to be mapped to a sidelink DRB, which is not established; + +For NR sidelink communication, a sidelink DRB modification is initiated only in the following cases: + +- 1> if any of the sidelink DRB related parameters is changed by *sl-ConfigDedicatedNR*, *SIB12*, *SidelinkPreconfigNR* or *RRCReconfigurationSidelink* for one sidelink DRB, which is established; + +###### 5.8.9.1a.2.2 Sidelink DRB addition/modification operations + +For the sidelink DRB, whose sidelink DRB addition conditions are met as in clause 5.8.9.1a.2.1, the UE capable of NR sidelink communication that is configured by upper layers to perform NR sidelink communication shall: + +- 1> for groupcast and broadcast; or +- 1> for unicast, if the sidelink DRB addition was triggered due to the reception of the *RRCReconfigurationSidelink* message; or +- 1> for unicast, after receiving the *RRCReconfigurationCompleteSidelink* message, if the sidelink DRB addition was triggered due to the configuration received within the *sl-ConfigDedicatedNR*, *SIB12*, *SidelinkPreconfigNR* or indicated by upper layers: + - 2> if an SDAP entity for NR sidelink communication associated with the destination and the cast type of the sidelink DRB does not exist: + +- 3> establish an SDAP entity for NR sidelink communication as specified in TS 37.324 [24] clause 5.1.1; +- 2> (re)configure the SDAP entity in accordance with the *sl-SDAP-ConfigPC5* received in the *RRCREconfigurationSidelink* or *sl-SDAP-Config* received in *sl-ConfigDedicatedNR*, *SIB12*, *SidelinkPreconfigNR*, associated with the sidelink DRB; +- 2> establish a PDCP entity for NR sidelink communication and configure it in accordance with the *sl-PDCP-ConfigPC5* received in the *RRCREconfigurationSidelink* or *sl-PDCP-Config* received in *sl-ConfigDedicatedNR*, *SIB12*, *SidelinkPreconfigNR*, associated with the sidelink DRB; +- 2> for a per-hop sidelink DRB (i.e. the UE is not acting as L2 U2U Remote UE): + - 3> establish a RLC entity for NR sidelink communication and configure it in accordance with the *sl-RLC-ConfigPC5* received in the *RRCREconfigurationSidelink* or *sl-RLC-Config* received in *sl-ConfigDedicatedNR*, *SIB12*, *SidelinkPreconfigNR*, associated with sidelink DRB; + - 3> if this procedure was due to the reception of a *RRCREconfigurationSidelink* message: + - 4> configure the MAC entity with a logical channel in accordance with the *sl-MAC-LogicalChannelConfigPC5* received in the *RRCREconfigurationSidelink* associated with the sidelink DRB, and perform the sidelink UE information procedure in clause 5.8.3 for unicast if need; + - 3> else if this procedure was due to the reception of a *RRCREconfigurationCompleteSidelink* message: + - 4> configure the MAC entity with a logical channel associated with the sidelink DRB, in accordance with the *sl-MAC-LogicalChannelConfig* received in the *sl-ConfigDedicatedNR*, *SIB12*, *SidelinkPreconfigNR*; + - 3> else (i.e. for groupcast/broadcast): + - 4> configure the MAC entity with a logical channel associated with the sidelink DRB, in accordance with the *sl-MAC-LogicalChannelConfig* received in the *sl-ConfigDedicatedNR*, *SIB12*, *SidelinkPreconfigNR* and assign a new LCID to this logical channel. +- 2> for an end-to-end sidelink DRB (i.e. the UE is acting as L2 U2U Remote UE): + - 3> if the UE is in RRC\_CONNECTED: + - 4> associate this end-to-end sidelink DRB with the PC5 RLC channel indicated by *sl-EgressRLC-ChannelPC5* included in *sl-ConfigDedicatedNR*, received from *RRCREconfiguration*; + - 3> else if the UE is in RRC\_IDLE or RRC\_INACTIVE: + - 4> associate this end-to-end sidelink DRB with the PC5 RLC channel derived by per-SLRB QoS profile of this end-to-end sidelink DRB based on the configuration in *SIB12*; + - 3> else if the UE is out of coverage: + - 4> associate this end-to-end sidelink DRB with the PC5 RLC channel derived by per-SLRB QoS profile of this end-to-end sidelink DRB based on the configuration in *SidelinkPreconfigNR*; + +NOTE 1: When a sidelink DRB addition is due to the configuration by *RRCREconfigurationSidelink*, it is up to UE implementation to select the sidelink DRB configuration as necessary transmitting parameters for the sidelink DRB, from the received *sl-ConfigDedicatedNR* (if in RRC\_CONNECTED), *SIB12* (if in RRC\_IDLE/INACTIVE), *SidelinkPreconfigNR* (if out of coverage) with the same RLC mode as the one configured in *RRCREconfigurationSidelink*. + +For the sidelink DRB, whose sidelink DRB modification conditions are met as in clause 5.8.9.1a.2.1, the UE capable of NR sidelink communication that is configured by upper layers to perform NR sidelink communication shall: + +- 1> for groupcast and broadcast; or +- 1> for unicast, if the sidelink DRB modification was triggered due to the reception of the *RRCREconfigurationSidelink* message; or + +- 1> for unicast, after receiving the *RRCReconfigurationCompleteSidelink* message, if the sidelink DRB modification was triggered due to the configuration received within the *sl-ConfigDedicatedNR*, *SIB12* or *SidelinkPreconfigNR*: + - 2> reconfigure the SDAP entity of the sidelink DRB, in accordance with the *sl-SDAP-ConfigPC5* received in the *RRCReconfigurationSidelink* or *sl-SDAP-Config* received in *sl-ConfigDedicatedNR*, *SIB12*, *SidelinkPreconfigNR*, if included; + - 2> reconfigure the PDCP entity of the sidelink DRB, in accordance with the *sl-PDCP-ConfigPC5* received in the *RRCReconfigurationSidelink* or *sl-PDCP-Config* received in *sl-ConfigDedicatedNR*, *SIB12*, *SidelinkPreconfigNR*, if included; + - 2> reconfigure the RLC entity of the sidelink DRB, in accordance with the *sl-RLC-ConfigPC5* received in the *RRCReconfigurationSidelink* or *sl-RLC-Config* received in *sl-ConfigDedicatedNR*, *SIB12*, *SidelinkPreconfigNR*, if included; + - 2> reconfigure the logical channel of the sidelink DRB, in accordance with the *sl-MAC-LogicalChannelConfigPC5* received in the *RRCReconfigurationSidelink* or *sl-MAC-LogicalChannelConfig* received in *sl-ConfigDedicatedNR*, *SIB12*, *SidelinkPreconfigNR*, if included. + +##### 5.8.9.1a.3 Sidelink SRB release + +The UE shall: + +- 1> if a PC5-RRC connection release for a specific destination is requested by upper layers or AS layer; or +- 1> if the sidelink radio link failure is detected for a specific destination: + - 2> release the PDCP entity, RLC entity and the logical channel of the sidelink SRB for PC5-RRC message of the specific destination; + - 2> consider the PC5-RRC connection is released for the destination. +- 1> if PC5-S transmission for a specific destination is terminated in upper layers: + - 2> release the PDCP entity, RLC entity and the logical channel of the sidelink SRB(s) for PC5-S message of the specific destination; +- 1> if discovery transmission for a specific destination is terminated in upper layers: + - 2> release the PDCP entity, RLC entity and the logical channel of the sidelink SRB4 for discovery message of the specific destination; + +Editor's Note: FFS on how to release SL SRB on E2E and hop configuration for U2U relay. + +##### 5.8.9.1a.4 Sidelink SRB addition + +The UE shall: + +- 1> if transmission of PC5-S message for a specific destination is requested by upper layers for sidelink SRB: + - 2> establish PDCP entity, RLC entity and the logical channel of a sidelink SRB for PC5-S message, as specified in clause 9.1.1.4; +- 1> if transmission of discovery message for a specific destination is requested by upper layers for sidelink SRB: + - 2> establish PDCP entity, RLC entity and the logical channel of a sidelink SRB4 for discovery message, as specified in clause 9.1.1.4; +- 1> if a PC5-RRC connection establishment for a specific destination is indicated by upper layers: + - 2> establish PDCP entity, RLC entity and the logical channel of a sidelink SRB for PC5-RRC message of the specific destination, as specified in clause 9.1.1.4; + - 2> consider the PC5-RRC connection is established for the destination. + +##### 5.8.9.1a.5 Additional Sidelink RLC Bearer release + +###### 5.8.9.1a.5.1 Additional Sidelink RLC Bearer release conditions + +For NR sidelink communication, additional sidelink RLC bearer release is initiated in the following cases: + +- 1> for sidelink DRB, the release conditions are met as in clause 5.8.9.1a.1.1 for the associated sidelink DRB; or +- 1> for sidelink SRB, the release conditions are met as in clause 5.8.9.1a.3 for the associated sidelink SRB; or +- 1> for sidelink DRB, if *SL-RLC-BearerConfigIndex* (if any) of the sidelink DRB or SRB is included in *sl-RLC-BearerToReleaseList* in *RRReconfigurationSidelink*; or +- 1> for sidelink DRB, if *SL-RLC-BearerConfigIndex* (if any) of the additional Sidelink RLC Bearer is included in *sl-RLC-BearerToReleaseListSizeExt* in *sl-ConfigDedicatedNR* and if the *SL-TxProfile* of the associated QoS flow(s) for the *sl-ServedRadioBearer* indicates *backwardsIncompatible*; or +- 1> for sidelink DRB, if *SL-RLC-BearerConfig* is received in *sl-RLC-BearerToAddModListSizeExt* in *sl-ConfigDedicatedNR* for a *sl-ServedRadioBearer*, and if the *SL-TxProfile* of the associated QoS flow(s) for the *sl-ServedRadioBearer* indicates *backwardsCompatible* and UE decides not to use PDCP duplication; or +- 1> for sidelink DRB, if *SL-RLC-BearerConfig* is received in *sl-RLC-BearerConfigListSizeExt* in *SIB12* or in *SidelinkPreconfigNR* for a *sl-ServedRadioBearer*, and if the *SL-TxProfile* of the associated QoS flow(s) for the *sl-ServedRadioBearer* indicates *backwardsCompatible* and UE decides not to use PDCP duplication; or +- 1> for sidelink SRB, if UE decides not to use PDCP duplication; + +###### 5.8.9.1a.5.2 Additional Sidelink RLC Bearer release operation + +The UE shall: + +- 1> for groupcast and broadcast; or +- 1> for unicast, after receiving the *RRReconfigurationCompleteSidelink* message, if the additional sidelink RLC bearer release was triggered due to the configuration received within the *sl-ConfigDedicatedNR*: + - 2> for each *SL-RLC-BearerConfigIndex* included in the received *sl-RLC-BearerToReleaseListSizeExt* in *sl-ConfigDedicatedNR* that is part of the current UE sidelink configuration: + - 3> release the RLC entity and the corresponding logical channel of the additional sidelink RLC bearer for NR sidelink communication, associated with the *SL-RLC-BearerConfigIndex*. +- 1> for unicast, if the additional sidelink RLC bearer release was triggered due to the reception of the *RRReconfigurationSidelink* message: + - 2> for each *SL-RLC-BearerConfigIndex* included in received *sl-RLC-BearerToReleaseList* in *RRReconfigurationSidelink* that is part of the current UE sidelink configuration: + - 3> release the RLC entity and the corresponding logical channel of the additional sidelink RLC bearer for NR sidelink communication associated with the *SL-RLC-BearerConfigIndex*; +- 1> for unicast, after receiving the *RRReconfigurationCompleteSidelink* message, if the additional sidelink RLC bearer release was triggered due to the configuration received within the *SIB12*, *SidelinkPreconfigNR* or indicated by upper layers: + - 2> for each *SL-RLC-BearerConfigIndex* included in transmitted *sl-RLC-BearerToReleaseList* in *RRReconfigurationSidelink* that is part of the current UE sidelink configuration: + - 3> release the RLC entity and the corresponding logical channel of the additional sidelink RLC bearer for NR sidelink communication associated with the *SL-RLC-BearerConfigIndex*; + +##### 5.8.9.1a.6 Additional Sidelink RLC Bearer addition/modification + +###### 5.8.9.1a.6.1 Additional Sidelink RLC Bearer addition/modification conditions + +For NR sidelink communication, additional sidelink RLC bearer addition is initiated only in the following cases: + +- 1> for unicast, for sidelink DRB, if *SL-RLC-BearerConfig* is received in *sl-RLC-BearerToAddModList* in the *RRReconfigurationSidelink* for a *slrb-PC5-ConfigIndex*; or +- 1> for groupcast and broadcast, for sidelink DRB, if *SL-RLC-BearerConfig* is received in *sl-RLC-BearerToAddModListSizeExt* in *sl-ConfigDedicatedNR* for a *sl-ServedRadioBearer*, and if the *SL-TxProfile* of all associated QoS flow(s) for the *sl-ServedRadioBearer* indicates *backwardsIncompatible*; or +- 1> for groupcast and broadcast, for sidelink DRB, if *SL-RLC-BearerConfig* is received in *sl-RLC-BearerToAddModListSizeExt* in *sl-ConfigDedicatedNR* for a *sl-ServedRadioBearer*, and if the *SL-TxProfile* of at least one associated QoS flow for the *sl-ServedRadioBearer* indicates *backwardsCompatible* and UE decides to use PDCP duplication; or +- 1> for unicast, for sidelink DRB, if *SL-RLC-BearerConfig* is received in *sl-RLC-BearerToAddModListSizeExt* in *sl-ConfigDedicatedNR* for a *sl-ServedRadioBearer*; or +- 1> for groupcast and broadcast, for sidelink DRB, if *SL-RLC-BearerConfig* is received in *sl-RLC-BearerConfigListSizeExt* in *SIB12* or in *SidelinkPreconfigNR* for a *sl-ServedRadioBearer*, and if the *SL-TxProfile* of all associated QoS flow(s) for the *sl-ServedRadioBearer* indicates *backwardsIncompatible*; or +- 1> for groupcast and broadcast, for sidelink DRB, if *SL-RLC-BearerConfig* is received in *sl-RLC-BearerConfigListSizeExt* in *SIB12* or in *SidelinkPreconfigNR* for a *sl-ServedRadioBearer*, and if the *SL-TxProfile* of at least one QoS flow for the *sl-ServedRadioBearer* indicates *backwardsCompatible* and UE decides to use PDCP duplication; or +- 1> for unicast, for sidelink DRB, if *SL-RLC-BearerConfig* is received in *sl-RLC-BearerConfigListSizeExt* in *SIB12* or in *SidelinkPreconfigNR* for a *sl-ServedRadioBearer*, and if both UEs support PDCP duplication; or +- 1> for unicast, for sidelink SRB, if UE decides to use PDCP duplication; + +For NR sidelink communication, additional sidelink RLC bearer modification is initiated only in the following cases: + +- 1> if any of the additional sidelink RLC bearer related parameters is changed by *sl-ConfigDedicatedNR*, *SIB12*, *SidelinkPreconfigNR* or *RRReconfigurationSidelink* for one additional sidelink RLC bearer, which is established; + +###### 5.8.9.1a.6.2 Additional Sidelink RLC Bearer addition/modification operation + +For the additional Sidelink RLC bearer, whose addition conditions are met as in clause 5.8.9.1a.6.1, the UE capable of NR sidelink communication that is configured by upper layers to perform NR sidelink communication shall: + +- 1> for groupcast and broadcast; or +- 1> for unicast, if the additional Sidelink RLC bearer addition was triggered due to the reception of the *RRReconfigurationSidelink* message; or +- 1> for unicast, for DRB, after receiving the *RRReconfigurationCompleteSidelink* message, if the additional Sidelink RLC bearer addition was triggered due to the configuration received within the *sl-ConfigDedicatedNR*, *SIB12*, *SidelinkPreconfigNR* or indicated by upper layers; or +- 1> for unicast, for SRB, after receiving the *RRReconfigurationCompleteSidelink* message, if the additional Sidelink RLC bearer addition was decided by UE: + - 2> establish an additional RLC entity for NR sidelink communication and configure it in accordance with each *sl-RLC-ConfigPC5* received in the *RRReconfigurationSidelink* or *sl-RLC-Config* received in *sl-ConfigDedicatedNR*, *SIB12*, *SidelinkPreconfigNR* for SL DRB, and as specified in clause 9.1.1.4 for SL SRB; + - 2> if this procedure was for Sidelink DRB: + - 3> if this procedure was due to the reception of a *RRReconfigurationSidelink* message: + - 4> configure the MAC entity with a logical channel in accordance with the *sl-MAC-LogicalChannelConfigPC5* received in the *RRReconfigurationSidelink* associated with the sidelink RLC entity; + - 3> else if this procedure was due to the reception of a *RRReconfigurationCompleteSidelink* message: + +- 4> configure the MAC entity with a logical channel associated with the sidelink RLC entity, in accordance with the *sl-MAC-LogicalChannelConfig* received in the *sl-ConfigDedicatedNR*, *SIB12*, *SidelinkPreconfigNR*; +- 3> else (i.e. for groupcast/broadcast): + - 4> configure the MAC entity with a logical channel associated with the sidelink RLC entity, in accordance with the *sl-MAC-LogicalChannelConfig* received in the *sl-ConfigDedicatedNR*, *SIB12*, *SidelinkPreconfigNR* and assign a new LCID to this logical channel. +- 3> if the UE is in RRC\_CONNECTED: + - 4> indicate the allowed carriers for the two RLC bearers of the DRB, as indicated in *sl-AllowedCarriers*, to lower layer; +- 3> else: + - 4> indicate the allowed carriers for the two RLC bearers of the DRB, decided by UE implementation, to lower layer, where the carrier indicated in *sl-FreqInfoList* is used for the RLC bearer if the *SL-TxProfile* of at least one associated QoS flow for the *sl-ServedRadioBearer* indicates *backwardsCompatible*; +- 2> else (i.e., if this procedure was for Sidelink SRB): + - 3> configure the MAC entity with a logical channel associated with the sidelink RLC entity, as specified in clause 9.1.1.4. + - 3> if the UE is in RRC\_CONNECTED: + - 4> indicate the allowed carriers for the two RLC bearers of the SRB, as indicated in *allowedCarrierFreqSet1/allowedCarrierFreqSet2*, to lower layer; + - 3> else: + - 4> indicate the allowed carriers for the two RLC bearers of the SRB, decided by UE implementation, to lower layer, where the carrier indicated in *sl-FreqInfoList* is used for the RLC bearer if the *SL-TxProfile* of at least one associated QoS flow for the *sl-ServedRadioBearer* indicates *backwardsCompatible*; + +For the additional Sidelink RLC bearer, whose modification conditions are met as in clause 5.8.9.1a.6.1, the UE capable of NR sidelink communication that is configured by upper layers to perform NR sidelink communication shall: + +- 1> for groupcast and broadcast; or +- 1> for unicast, if the additional Sidelink RLC bearer modification was triggered due to the reception of the *RRCReconfigurationSidelink* message; or +- 1> for unicast, after receiving the *RRCReconfigurationCompleteSidelink* message, if the additional Sidelink RLC bearer modification was triggered due to the configuration received within the *sl-ConfigDedicatedNR*, *SIB12* or *SidelinkPreconfigNR*: + - 2> reconfigure the RLC entity of the sidelink DRB, in accordance with the *sl-RLC-ConfigPC5* received in the *RRCReconfigurationSidelink* or *sl-RLC-Config* received in *sl-ConfigDedicatedNR*, *SIB12*, *SidelinkPreconfigNR*, if included; + - 2> reconfigure the logical channel of the sidelink DRB, in accordance with the *sl-MAC-LogicalChannelConfigPC5* received in the *RRCReconfigurationSidelink* or *sl-MAC-LogicalChannelConfig* received in *sl-ConfigDedicatedNR*, *SIB12*, *SidelinkPreconfigNR*, if included. + +#### 5.8.9.1b Sidelink Carrier Configuration + +##### 5.8.9.1b.1 Sidelink Carrier Release + +The UE shall: + +- 1> for unicast, if the sidelink carrier release was triggered due to the reception of the *RRReconfigurationSidelink* message; or +- 1> for unicast, after receiving the *RRReconfigurationCompleteSidelink* message, + - 2> for each *sl-Carrier-Id* value included in the *sl-CarrierToReleaseList*: + - 3> if the current UE configuration includes a sidelink carrier with value *sl-Carrier-Id*: + - 4> release the sidelink carrier for reception. + +##### 5.8.9.1b.2 Sidelink Carrier Addition/Modification + +The UE shall: + +- 1> for unicast, if the sidelink carrier addition was triggered due to the reception of the *RRReconfigurationSidelink* message; or +- 1> for unicast, after receiving the *RRReconfigurationCompleteSidelink* message, + - 2> for each *sl-Carrier-Id* value included in the *sl-CarrierToAddModList* that is not part of the current UE configuration (sidelink carrier addition): + - 3> add the sidelink carrier, corresponding to the *sl-Carrier-Id*, in accordance with the *sl-AbsoluteFrequencyPointA* for reception; +- 1> for unicast, if the sidelink carrier was modified due to the reception of the *RRReconfigurationSidelink* message; or +- 1> for unicast, after receiving the *RRReconfigurationCompleteSidelink* message, + - 2> for each *sl-Carrier-Id* value included in the *sl-CarrierToAddModList* that is part of the current UE configuration (sidelink carrier modification): + - 3> modify the sidelink carrier configuration in accordance with *sl-AbsoluteFrequencyPointA* for reception; + +#### 5.8.9.2 Sidelink UE capability transfer + +##### 5.8.9.2.1 General + +This clause describes how the UE compiles and transfers its sidelink UE capability information for unicast to the initiating UE. + +![Sequence diagram showing Sidelink UE capability transfer between two User Equipment (UE) entities. The first UE sends a UECapabilityEnquirySidelink message to the second UE, and the second UE responds with a UECapabilityInformationSidelink message.](572cf014db14c8234f91c07d5a5a28c6_img.jpg) + +``` + +sequenceDiagram + participant UE1 as UE + participant UE2 as UE + Note left of UE1: Initiating UE + UE1->>UE2: UECapabilityEnquirySidelink + Note right of UE2: Responding UE + UE2-->>UE1: UECapabilityInformationSidelink + +``` + +Sequence diagram showing Sidelink UE capability transfer between two User Equipment (UE) entities. The first UE sends a UECapabilityEnquirySidelink message to the second UE, and the second UE responds with a UECapabilityInformationSidelink message. + +Figure 5.8.9.2.1-1: Sidelink UE capability transfer + +##### 5.8.9.2.2 Initiation + +The UE may initiate the sidelink UE capability transfer procedure upon indication from upper layer when it needs (additional) UE radio access capability information. + +##### 5.8.9.2.3 Actions related to transmission of the *UECapabilityEnquirySidelink* by the UE + +The initiating UE shall set the contents of *UECapabilityEnquirySidelink* message as follows: + +- 1> include in UE radio access capabilities for sidelink within *ue-CapabilityInformationSidelink*, if needed; + +NOTE 1: It is up to initiating UE to decide whether *ue-CapabilityInformationSidelink* should be included. + +1> set *frequencyBandListFilterSidelink* to include frequency bands for which the peer UE is requested to provide supported bands and band combinations; + +NOTE 2: The initiating UE is not allowed to send the *UECapabilityEnquirySidelink* message without including the field *frequencyBandListFilterSidelink*. + +1> submit the *UECapabilityEnquirySidelink* message to lower layers for transmission. + +##### 5.8.9.2.4 Actions related to reception of the *UECapabilityEnquirySidelink* by the UE + +The peer UE shall set the contents of *UECapabilityInformationSidelink* message as follows: + +1> include UE radio access capabilities for sidelink within *ue-CapabilityInformationSidelink*; + +1> compile a list of "candidate band combinations" only consisting of bands included in *frequencyBandListFilterSidelink*, and prioritized in the order of *frequencyBandListFilterSidelink* (i.e. first include band combinations containing the first-listed band, then include remaining band combinations containing the second-listed band, and so on). + +1> include into *supportedBandCombinationListSidelinkNR* as many band combinations as possible from the list of "candidate band combinations", starting from the first entry; + +1> include the received *frequencyBandListFilterSidelink* in the field *appliedFreqBandListFilter* of the requested UE capability; + +1> submit the *UECapabilityInformationSidelink* message to lower layers for transmission. + +NOTE: If the UE cannot include all band combinations due to message size or list size constraints, it is up to UE implementation which band combinations it prioritizes. + +#### 5.8.9.3 Sidelink radio link failure related actions + +The UE shall: + +1> upon indication from sidelink RLC entity that the maximum number of retransmissions for a specific destination has been reached; or + +1> upon T400 expiry for a specific destination; or + +1> upon indication from MAC entity that the maximum number of consecutive HARQ DTX for a specific destination has been reached; or + +1> upon integrity check failure indication from sidelink PDCP entity concerning SL-SRB2 or SL-SRB3 for a specific destination; or + +1> upon indication of consistent sidelink LBT failures for all RB sets for a specific destination from MAC entity; or + +1> upon reception of *NotificationMessageSidelink* indicating PC5 RLF from the L2 U2U Relay UE for a specific destination based on the received *sl-DestinationIdentity*: + +2> consider sidelink radio link failure to be detected for this destination; + +2> release the DRBs of this destination, according to clause 5.8.9.1a.1; + +2> release the SRBs of this destination, according to clause 5.8.9.1a.3; + +2> release the PC5 Relay RLC channels of this destination if configured, in according to clause 5.8.9.7.1; + +2> discard the NR sidelink communication related configuration of this destination; + +2> reset the sidelink specific MAC of this destination, except for L2 U2U Relay operation; + +2> consider the PC5-RRC connection is released for the destination; + +- 2> indicate the release of the PC5-RRC connection to the upper layers for this destination (i.e. PC5 is unavailable); +- 2> if UE is in RRC\_CONNECTED: + - 3> if the UE is acting as L2 U2N Remote UE for the destination: + - 4> initiate the RRC connection re-establishment procedure as specified in 5.3.7. + - 3> else: + - 4> perform the sidelink UE information for NR sidelink communication procedure, as specified in 5.8.3.3; + +Editor's Note: FFS whether additional procedure for L2 U2U PC5 RLF initiation. + +NOTE: It is up to UE implementation on whether and how to indicate to upper layers to maintain the keep-alive procedure [55]. + +#### 5.8.9.4 Sidelink common control information + +##### 5.8.9.4.1 General + +The sidelink common control information is carried by *MasterInformationBlockSidelink*. The sidelink common control information may change at any transmission, i.e. neither a modification period nor a change notification mechanism is used. This procedure also applies to NR sidelink discovery. + +A UE configured to receive or transmit NR sidelink communication/discovery/positioning shall: + +- 1> if the UE has a selected SyncRef UE, as specified in 5.8.6: + - 2> ensure having a valid version of the *MasterInformationBlockSidelink* message of that SyncRef UE; + +##### 5.8.9.4.2 Actions related to reception of *MasterInformationBlockSidelink* message + +Upon receiving *MasterInformationBlockSidelink*, the UE shall: + +- 1> apply the values included in the received *MasterInformationBlockSidelink* message. + +##### 5.8.9.4.3 Transmission of *MasterInformationBlockSidelink* message + +The UE shall set the contents of the *MasterInformationBlockSidelink* message as follows: + +- 1> if in coverage on the frequency used for the NR sidelink communication/positioning as defined in TS 38.304 [20]. + - 2> set *inCoverage* to true; + - 2> if *tdd-UL-DL-ConfigurationCommon* is included in the received *SIB1*: + - 3> set *sl-TDD-Config* to the value representing the same meaning as that is included in *tdd-UL-DL-ConfigurationCommon*, as described in TS 38.213, clause 16.1 [13]; + - 2> else: + - 3> set *sl-TDD-Config* to the value as specified in TS 38.213 [13], clause 16.1; + - 2> if *syncInfoReserved* is included in an entry of configured *sl-SyncConfigList* corresponding to the concerned frequency from the received *SIB12*: + - 3> set *reservedBits* to the value of *syncInfoReserved* in the received *SIB12*; + - 2> else: + - 3> set all bits in *reservedBits* to 0; + +- 1> else if out of coverage on the frequency used for NR sidelink communication/positioning as defined in TS 38.304 [20]; and the concerned frequency is included in *sl-FreqInfoToAddModList/sl-FreqInfoToAddModListExt* in *RRCReconfiguration* or in *sl-FreqInfoList/sl-FreqInfoListSizeExt* within *SIB12*: + - 2> set *inCoverage* to *true*; + - 2> set *reservedBits* to the value of the corresponding field included in the preconfigured sidelink parameters (i.e. *sl-PreconfigGeneral* in *SidelinkPreconfigNR* defined in 9.3); + - 2> set *sl-TDD-Config* to the value representing the same meaning as that is included in the corresponding field included in the preconfigured sidelink parameters (i.e. *sl-PreconfigGeneral* in *SL-PreconfigurationNR* defined in 9.3) as described in TS 38.213, clause 16.1 [13]; +- 1> else if out of coverage on the frequency used for NR sidelink communication/positioning as defined in TS 38.304 [20]; and the UE selects GNSS as the synchronization reference and *sl-SSB-TimeAllocation3* is not configured for the frequency used in *SidelinkPreconfigNR*: + - 2> set *inCoverage* to *true*; + - 2> set *reservedBits* to the value of the corresponding field included in the preconfigured sidelink parameters (i.e. *sl-PreconfigGeneral* in *SidelinkPreconfigNR* defined in 9.3); + - 2> set *sl-TDD-Config* to the value representing the same meaning as that is included in the corresponding field included in the preconfigured sidelink parameters (i.e. *sl-PreconfigGeneral* in *SL-PreconfigurationNR* defined in 9.3) as described in TS 38.213, clause 16.1 [13]; +- 1> else if the UE has a selected SyncRef UE (as defined in 5.8.6): + - 2> set *inCoverage* to *false*; + - 2> set *sl-TDD-Config* and *reservedBits* to the value of the corresponding field included in the received *MasterInformationBlockSidelink*; +- 1> else: + - 2> set *inCoverage* to *false*; + - 2> set *reservedBits* to the value of the corresponding field included in the preconfigured sidelink parameters (i.e. *sl-PreconfigGeneral* in *SidelinkPreconfigNR* defined in 9.3); + - 2> set *sl-TDD-Config* to the value representing the same meaning as that is included in the corresponding field included in the preconfigured sidelink parameters (i.e. *sl-PreconfigGeneral* in *SL-PreconfigurationNR* defined in 9.3) as described in TS 38.213, clause 16.1 [13]; +- 1> set *directFrameNumber* and *slotIndex* according to the slot used to transmit the SLSS, as specified in 5.8.5.3; +- 1> submit the *MasterInformationBlockSidelink* to lower layers for transmission upon which the procedure ends; + +#### 5.8.9.5 Actions related to PC5-RRC connection release requested by upper layers + +The UE initiates the procedure when upper layers request the release of the PC5-RRC connection as specified in TS 24.587 [57] or TS 24.554 [72]. The UE shall not initiate the procedure for power saving purposes. + +The UE shall: + +- 1> if the PC5-RRC connection release for the specific destination is requested by upper layers: + - 2> discard the NR sidelink communication related configuration of this destination; + - 2> release the DRBs of this destination if configured, in according to clause 5.8.9.1a.1; + - 2> release the SRBs of this destination, in according to clause 5.8.9.1a.3; + - 2> release the PC5 Relay RLC channels if configured, in according to clause 5.8.9.7.1; + - 2> reset the sidelink specific MAC of this destination. + +2> consider the PC5-RRC connection is released for the destination; + +#### 5.8.9.6 Sidelink UE assistance information + +##### 5.8.9.6.1 General + +![Sequence diagram showing two User Equipment (UE) blocks. A horizontal line labeled 'UEAssistanceInformationSidelink' is drawn between them, indicating a message exchange. Below the diagram is the URL: http://msc-generator.sourceforge.net v7.2](886963464425186f4a465fa8155d2a3c_img.jpg) + +Sequence diagram showing two User Equipment (UE) blocks. A horizontal line labeled 'UEAssistanceInformationSidelink' is drawn between them, indicating a message exchange. Below the diagram is the URL: http://msc-generator.sourceforge.net v7.2 + +**Figure 5.8.9.6.1-1: Sidelink UE assistance information** + +The purpose of this procedure is for a UE to inform its peer UE of the sidelink DRX assistance information used to determine the sidelink DRX configuration for unicast communication. + +For sidelink unicast, a UE may include its desired sidelink DRX configurations in the *UEAssistanceInformationSidelink* as the sidelink DRX assistance information which is transmitted to its peer UE. + +NOTE: It is up to UE implementation to determine its desired sidelink DRX configurations for unicast communication. When UE transmits SL-PRS in dedicated SL-PRS resource pool, the sidelink DRX configuration is not applied. + +##### 5.8.9.6.2 Initiation + +For sidelink unicast, if both a RX UE and its peer TX UE for a direction of sidelink communication are capable of sidelink DRX, the RX UE that is interested in sending the sidelink DRX assistance information may send the *UEAssistanceInformationSidelink* as the sidelink DRX assistance information to its peer UE when the sidelink DRX assistance information has not been sent previously or when the previously transmitted sidelink DRX assistance information has changed. + +##### 5.8.9.6.3 Actions related to reception of *UEAssistanceInformationSidelink* message + +For sidelink unicast, when a UE is in RRC\_CONNECTED and is performing sidelink operation with resource allocation mode 1, it may report the sidelink DRX assistance information received within the *UEAssistanceInformationSidelink* from its peer UE to the network as specified in 5.8.3. For sidelink unicast, when a UE is in RRC\_CONNECTED and is performing sidelink operation with resource allocation mode 2 or is in RRC\_IDLE or RRC\_INACTIVE or out of coverage, regardless of whether the UE has obtained the sidelink DRX assistance information from the *UEAssistanceInformationSidelink* transmitted from its peer UE or not, it may determine the sidelink DRX configuration *SL-DRX-ConfigUC* for its peer UE. + +NOTE: When UE determines the sidelink DRX configuration for its peer UE, it may take the sidelink DRX assistance information received from its peer UE into account. + +#### 5.8.9.7 PC5 Relay RLC channel management for L2 U2N or U2U relay + +##### 5.8.9.7.1 PC5 Relay RLC channel release + +The UE shall: + +- 1> if the PC5 Relay RLC channel release was triggered after the reception of the *RRReconfigurationSidelink* message; or +- 1> after receiving the *RRReconfigurationCompleteSidelink* message, if the PC5 Relay RLC channel release was triggered due to the configuration received within the *sl-ConfigDedicatedNR*; or +- 1> for unicast in L2 U2U relay operation, if there is no end-to-end sidelink DRB(s) associated with this RLC channel: + - 2> for each *SL-RLC-ChannelID* in *sl-RLC-ChannelToReleaseList* received in *sl-ConfigDedicatedNR* within *RRReconfiguration*, or for each *SL-RLC-ChannelID* included in the received *sl-RLC-* + +*ChannelToReleaseListPC5* that is part of the current UE sidelink configuration, or for the RLC channel to be released: + +- 3> release the RLC entity and the corresponding logical channel associated with the *SL-RLC-ChannelIID*; +- 1> if the PC5 Relay RLC channel release was triggered for a specific destination by upper layers as specified in 5.8.9.5, or for a specific destination corresponding to the received *sl-DestinationIdentityRemoteUE* by upper layers as specified in 5.8.9.10.4, or due to sidelink RLF as specified in 5.8.9.3: +- 2> release the RLC entity and the corresponding logical channel associated with the *SL-RLC-ChannelIID* of the specific destination; + +##### 5.8.9.7.2 PC5 Relay RLC channel addition/modification + +Upon PC5-RR connection establishment between the L2 U2N Relay UE and L2 U2N Remote UE, the L2 U2N Relay UE shall: + +- 1> establish a SRAP entity as specified in TS 38.351 [66], if no SRAP entity has been established; +- 1> apply RLC specified configuration of SL-RLC0 as specified in clause 9.1.1.4: +- 1> apply RLC default configuration of SL-RLC1 as defined in clause 9.2.4 if the L2 U2N Relay UE is in RRC\_IDLE/INACTIVE state; + +Upon PC5-RR connection establishment between the L2 U2U Remote UE and L2 U2U Relay UE, and PC5-RR connection establishment between the L2 U2U Relay UE and peer L2 U2U Remote UE, the L2 U2U Remote UE or L2 U2U Relay UE shall: + +- 1> establish a SRAP entity as specified in TS 38.351 [66], if no SRAP entity has been established; +- 1> apply RLC specified configuration of *SL-U2U-RLC* as specified in clause 9.1.1.4; + +The UE shall: + +- 1> if the PC5 Relay RLC channel addition/modification was triggered due to the reception of the *RRCReconfigurationSidelink* message; or +- 1> after receiving the *RRCReconfigurationCompleteSidelink* message, if the PC5 Relay RLC channel addition/modification was triggered due to the configuration received within the *sl-ConfigDedicatedNR*; or +- 1> after receiving the *RRCReconfigurationCompleteSidelink* message, if the PC5 Relay RLC channel addition/modification was triggered for an end-to-end sidelink DRB based on the configuration in *SIB12* or *SidelinkPreconfigNR*: +- 2> if the current configuration contains a PC5 Relay RLC channel with the received *sl-RLC-ChannelIID* or *sl-RLC-ChannelIID-PC5*; or +- 2> if the configuration in *SIB12* or *SidelinkPreconfigNR* has updated, based on which the PC5 Relay RLC channel is derived: + - 3> reconfigure the sidelink RLC entity in accordance with the received *sl-RLC-Config* or *sl-RLC-ConfigPC5*; + - 3> reconfigure the sidelink MAC entity with a logical channel in accordance with the received *sl-MAC-LogicalChannelConfig* or *sl-MAC-LogicalChannelConfigPC5*; +- 2> else (a PC5 Relay RLC channel with the received *sl-RLC-ChannelIID* or *sl-RLC-ChannelIID-PC5* was not configured before): + - 3> establish a sidelink RLC entity in accordance with the received *sl-RLC-Config* (in *sl-ConfigDedicatedNR*, or *SIB12*, or *SidelinkPreconfigNR*) or *sl-RLC-ConfigPC5*; + - 3> configure the sidelink MAC entity with a logical channel in accordance with the received *sl-MAC-LogicalChannelConfig* or *sl-MAC-LogicalChannelConfigPC5*. + +#### 5.8.9.8 Remote UE information + +##### 5.8.9.8.1 General + +![Diagram showing the interaction between a Remote UE and a Relay UE. The Remote UE sends a RemoteUEInformationSidelink message to the Relay UE.](0dfdff10c725fe9c332b07ade9d23a5e_img.jpg) + +``` + +sequenceDiagram + participant Remote UE + participant Relay UE + Note left of Remote UE: Remote UE + Note right of Relay UE: Relay UE + Remote UE->>Relay UE: RemoteUEInformationSidelink + +``` + +Diagram showing the interaction between a Remote UE and a Relay UE. The Remote UE sends a RemoteUEInformationSidelink message to the Relay UE. + +Figure 5.8.9.8.1-1: Remote UE information + +This procedure is used by the L2 U2N Remote UE in RRC\_IDLE/RRC\_INACTIVE to inform about the required SIB(s)/posSIB(s), provide Paging related information to the connected L2 U2N Relay UE, and request the SFN-DFN offset from the connected L2 U2N Relay UE. + +This procedure is used by the L2 U2N Remote UE in RRC\_CONNECTED to request the SFN-DFN offset from the connected L2 U2N Relay UE. + +NOTE: MIB is not required by a L2 U2N Remote UE. + +##### 5.8.9.8.2 Actions related to transmission of *RemoteUEInformationSidelink* message + +When entering RRC\_IDLE or RRC\_INACTIVE, or upon change in any of the information in the *RemoteUEInformationSidelink* while in RRC\_IDLE or RRC\_INACTIVE, the L2 U2N Remote UE shall: + +- 1> if the UE has SIB request information to provide (e.g. the UE has not stored a valid version of a SIB, in accordance with clause 5.2.2.2.1, of one or several required SIB(s) in accordance with clause 5.2.2.1 and the requested SIB has not been indicated in *RemoteUEInformationSidelink* message to the L2 U2N Relay UE before): + - 2> include *sl-RequestedSIB-List* in the *RemoteUEInformationSidelink* to indicate the requested SIB(s); +- 1> if the UE has not stored a valid version, in accordance with clause 5.2.2.2.1, of one or several posSIB(s) that the UE requires for a positioning operation, and the requested posSIB has not been indicated in *RemoteUEInformationSidelink* message to the L2 U2N Relay UE before, and the connected L2 U2N relay UE set *posSIB-ForwardingSupported* to *supported*: + - 2> include *sl-RequestedPosSIB-List* in the *RemoteUEInformationSidelink* to indicate the requested posSIB(s); +- 1> if the UE needs the SFN-DFN offset based on the request from upper layers and the connected L2 U2N relay UE set *sfN-DFN-OffsetSupported* to *supported*: + - 2> set *sl-SFN-DFN-OffsetRequested* to *true*; +- 1> if the UE has paging related information to provide (e.g. the UE has not sent *sl-PagingInfo-RemoteUE* in the *RemoteUEInformationSidelink* message to the L2 U2N Relay UE before), set *sl-PagingInfo-RemoteUE* as follows: + - 2> if the L2 U2N Remote UE is in RRC\_IDLE: + - 3> include *ng-5G-S-TMSI* in the *sl-PagingIdentityRemoteUE*; + - 3> if the UE specific DRX cycle is configured by upper layer, set *sl-PagingCycleRemoteUE* to the value of UE specific Uu DRX cycle configured by upper layer; + - 2> else if the L2 U2N Remote UE is in RRC\_INACTIVE: + - 3> include *ng-5G-S-TMSI* and *fullI-RNTI* in the *sl-PagingIdentityRemoteUE*; + - 3> if the UE specific DRX cycle is configured by upper layer, + - 4> set *sl-PagingCycleRemoteUE* to the minimum value of UE specific Uu DRX cycles (configured by upper layer and configured by RRC); + +3> else: + +4> set *sl-PagingCycleRemoteUE* to the value of UE specific DRX cycle configured by RRC; + +1> submit the *RemoteUEInformationSidelink* message to lower layers for transmission; + +When entering RRC\_CONNECTED, if L2 U2N remote UE had sent *sl-RequestedSIB-List*, *sl-RequestedPosSIB-List*, and/or *sl-PagingInfo-RemoteUE*, the L2 U2N Remote UE shall: + +1> set the *sl-RequestedSIB-List* to the value *release* if requested before; + +1> set the *sl-RequestedPosSIB-List* to the value *release* if requested before; + +1> set the *sl-PagingInfo-RemoteUE* to the value *release* if sent before; + +1> submit the *RemoteUEInformationSidelink* message to lower layers for transmission; + +Upon any change in the need of SFN-DFN offset while in RRC\_CONNECTED, the L2 U2N Remote UE shall: + +1> if the UE needs the SFN-DFN offset based on the request from upper layers and the connected L2 U2N relay UE set *sfn-DFN-OffsetSupported* to *supported*: + +2> set *sl-SFN-DFN-OffsetRequested* to *true*; + +1> submit the *RemoteUEInformationSidelink* message to lower layers for transmission; + +The L2 U2N Remote UE in RRC\_CONNECTED shall: + +1> if the UE is configured with *sl-IndirectPathAddChange* set to *setup*, and not configured with split SRB1 with duplication: + +2> include *connectionForMP*; + +Editor's Note: FFS whether there is other condition to include the new indication, e.g. explicit NW indication, or RRC state of the L2 U2N Relay UE. + +##### 5.8.9.8.3 Reception of *RemoteUEInformationSidelink* message by the L2 U2N Relay UE + +The L2 U2N Relay UE shall: + +1> if the *RemoteUEInformationSidelink* includes the *sl-PagingInfo-RemoteUE*: + +2> if the UE is in RRC\_CONNECTED on an active BWP with common search space configured including *pagingSearchSpace*; or + +2> if the UE is in RRC\_IDLE or RRC\_INACTIVE: + +3> if the *sl-PagingInfo-RemoteUE* is set to *setup*: + +4> monitor the *Paging* message at the L2 U2N Remote UE's paging occasion calculated according to *sl-PagingIdentityRemoteUE* and *sl-PagingCycleRemoteUE* included in *sl-PagingInfo-RemoteUE*; + +3> else (the *sl-PagingInfo-RemoteUE* is set to *release*): + +4> stop monitoring the *Paging* message at the L2 U2N Remote UE's paging occasion; + +4> release the received paging information in *sl-PagingInfo-RemoteUE*; + +2> else (the UE is in RRC\_CONNECTED on an active BWP without *pagingSearchSpace* configured): + +3> if the *sl-PagingInfo-RemoteUE* is set to *setup*: + +4> include the received *sl-PagingIdentityRemoteUE* in *SidelinkUEInformationNR* message and perform Sidelink UE information transmission in accordance with 5.8.3; + +3> else (the *sl-PagingInfo-RemoteUE* is set to *release*): + +- 4> initiate transmission of the *SidelinkUEInformationNR* message to release the *sl-PagingIdentityRemoteUE* in *SidelinkUEInformationNR* message in accordance with 5.8.3; +- 4> release the received paging information in *sl-PagingInfo-RemoteUE*; +- 1> if the *RemoteUEInformationSidelink* includes the *sl-RequestedSIB-List*: + - 2> if the *sl-RequestedSIB-List* is set to *setup*: + - 3> if the L2 U2N Relay UE has not stored a valid version of SIB(s) indicated in *sl-RequestedSIB-List*: + - 4> perform acquisition of the system information indicated in *sl-RequestedSIB-List* in accordance with 5.2.2; + - 3> perform the Uu message transfer procedure in accordance with 5.8.9.9; + - 2> if the *sl-RequestedSIB-List* is set to *release*: + - 3> release received SIB request in *sl-RequestedSIB-List*; +- 1> if the *RemoteUEInformationSidelink* includes the *sl-RequestedPosSIB-List*: + - 2> if the *sl-RequestedPosSIB-List* is set to *setup*: + - 3> if the L2 U2N Relay UE has not stored a valid version of posSIB(s) indicated in *sl-RequestedPosSIB-List*: + - 4> perform acquisition of the positioning system information indicated in *sl-RequestedPosSIB-List* in accordance with 5.2.2; + - 3> perform the Uu message transfer procedure in accordance with 5.8.9.9; + - 2> if the *sl-RequestedPosSIB-List* is set to *release*: + - 3> release received posSIB request in *sl-RequestedPosSIB-List*. +- 1> if the *RemoteUEInformationSidelink* includes the *connectionForMP*: + - 2> if the L2 U2N Relay UE is in RRC\_IDLE: + - 3> initiate an RRC connection establishment as specified in 5.3.3; + - 2> else if the L2 U2N Relay UE is in RRC\_INACTIVE: + - 3> initiate an RRC connection resume as specified in 5.3.13; + +#### 5.8.9.9 Uu message transfer in sidelink + +##### 5.8.9.9.1 General + +![Sequence diagram showing Uu message transfer in sidelink between a Remote UE and a Relay UE. The Remote UE sends a UuMessageTransferSidelink message to the Relay UE.](d197b6ded14ea918198a280ff07122b8_img.jpg) + +``` + +sequenceDiagram + participant Remote UE + participant Relay UE + Note left of Remote UE: UuMessageTransferSidelink + Remote UE->>Relay UE: UuMessageTransferSidelink + +``` + +Sequence diagram showing Uu message transfer in sidelink between a Remote UE and a Relay UE. The Remote UE sends a UuMessageTransferSidelink message to the Relay UE. + +Figure 5.8.9.9.1-1: Uu message transfer in sidelink + +The purpose of this procedure is to transfer *Paging* message and System Information from the L2 U2N Relay UE to the L2 U2N Remote UE in RRC\_IDLE/RRC\_INACTIVE. + +##### 5.8.9.9.2 Actions related to transmission of *UuMessageTransferSidelink* message + +The L2 U2N Relay UE initiates the Uu message transfer procedure when at least one of the following conditions is met: + +- 1> upon receiving *Paging* message related to the connected L2 U2N Remote UE from network (including *Paging* message within *RRCReconfiguration* message); +- 1> upon acquisition of the SIB(s) requested by the connected L2 U2N Remote UE (as indicated in *sl-RequestedSIB-List* in the *RemoteUEInformationSidelink*) or upon receiving the updated SIB(s) from network which has been requested by the connected L2 U2N Remote UE; +- 1> upon acquisition of the posSIB(s) requested by the connected L2 U2N Remote UE (as indicated in *sl-RequestedPosSIB-List* in the *RemoteUEInformationSidelink*) or upon receiving the updated posSIB(s) from network which have been requested by the connected L2 U2N Remote UE; +- 1> upon unsolicited SIB1 forwarding to the connected L2 U2N Remote UE or upon receiving the updated *SIB1* from network; + +For each associated L2 U2N Remote UE, the L2 U2N Relay UE shall set the contents of *UuMessageTransferSidelink* message as follows: + +- 1> include *sl-PagingDelivery* if the *Paging* message received from network containing the *ue-Identity* of the L2 U2N Remote UE; +- 1> include *sl-SIB1-Delivery* if any of the conditions for initiating Uu message transfer procedure related to SIB1 are met; +- 1> include *sl-SystemInformationDelivery* if any of the conditions for initiating Uu message transfer procedure related to System Information are met; +- 1> submit the *UuMessageTransferSidelink* message to lower layers for transmission. + +NOTE: The L2 U2N Relay UE may perform unsolicited forwarding of SIB1 to the L2 U2N Remote UE based on UE implementation. + +##### 5.8.9.9.3 Reception of the *UuMessageTransferSidelink* + +Upon receiving the *UuMessageTransferSidelink* message, the L2 U2N Remote UE shall: + +- 1> if *sl-PagingDelivery* is included: + - 2> perform the paging reception procedure as specified in clause 5.3.2.3; +- 1> if *sl-SystemInformationDelivery* and/or *sl-SIB1-Delivery* is included: + - 2> perform the actions specified in clause 5.2.2.4. + +#### 5.8.9.10 Notification Message + +##### 5.8.9.10.1 General + +![Sequence diagram showing a Notification message in sidelink between a Remote UE and a Relay UE.](ffd8c2986aabedc8b6db2d8f2ed7a994_img.jpg) + +``` + +sequenceDiagram + participant Remote UE + participant Relay UE + Note left of Remote UE: + Remote UE->>Relay UE: NotificationMessageSidelink + Note right of Relay UE: + +``` + +The diagram illustrates a message exchange between a Remote UE and a Relay UE. The Remote UE is on the left and the Relay UE is on the right. A horizontal line with an arrow points from the Remote UE to the Relay UE, labeled with the message name *NotificationMessageSidelink*. Vertical lines extend from the message exchange point down to the bottom of the diagram. + +Sequence diagram showing a Notification message in sidelink between a Remote UE and a Relay UE. + +Figure 5.8.9.8.1-1: Notification message in sidelink + +This procedure is used by a U2N Relay UE to send notification to the connected U2N Remote UE, or used by a U2U Relay UE to send notification to the peer connected U2U Remote UE when condition(s) as specified in 5.8.9.10.2 is met with the connected U2U Remote UE. + +##### 5.8.9.10.2 Initiation + +The Relay UE may initiate the procedure when one of the following conditions is met: + +- 1> if the UE is acting as U2N Relay UE: + +- 2> upon Uu RLF as specified in 5.3.10; +- 2> upon reception of an *RRCReconfiguration* including the *reconfigurationWithSync*; +- 2> upon cell reselection; +- 2> upon L2 U2N Relay UE's RRC connection failure including RRC connection reject as specified in 5.3.3.5 and 5.3.13.10, and T300 expiry as specified in 5.3.3.7, and RRC resume failure as specified in 5.3.13.5; +- 1> if the UE is acting as L2 U2U Relay UE: + - 2> upon detection of PC5 RLF with L2 U2U Remote UE as specified in 5.8.9.3; + +##### 5.8.9.10.3 Actions related to transmission of *NotificationMessageSidelink* message + +The Relay UE shall set the indication type as follows: + +- 1> if the UE is acting as U2N Relay UE: + - 2> if the UE initiates transmission of the *NotificationMessageSidelink* message due to Uu RLF: + - 3> set the *indicationType* as *relayUE-Uu-RLF*; + - 2> else if the UE initiates transmission of the *NotificationMessageSidelink* message due to reconfiguration with sync: + - 3> set the *indicationType* as *relayUE-HO*; + - 2> else if the UE initiates transmission of the *NotificationMessageSidelink* message due to cell reselection: + - 3> set the *indicationType* as *relayUE-CellReselection*; + - 2> if the UE initiates transmission of the *NotificationMessageSidelink* message due to Uu RRC connection establishment/Resume failure: + - 3> set the *indicationType* as *relayUE-Uu-RRC-Failure*; + - 2> submit the *NotificationMessageSidelink* message to lower layers for transmission. + +- 1> if the UE is acting as L2 U2U Relay UE: + - 2> if the UE initiates transmission of the *NotificationMessageSidelink* message due to PC5 RLF with L2 U2U Remote UE: + - 3> set the *sl-IndicationType* as *relayUE-PC5-RLF*; + - 3> set the *sl-DestinationIdentityRemoteUE* as the associated destination for L2 U2U Remote UE; + - 3> submit the *NotificationMessageSidelink* message to lower layers for transmission; + +##### 5.8.9.10.4 Actions related to reception of *NotificationMessageSidelink* message + +Upon receiving the *NotificationMessageSidelink*, the Remote UE shall: + +- 1> if the UE is acting as U2N Remote UE: + - 2> if the *indicationType* is included: + - 3> if the UE is L2 U2N Remote UE in RRC\_CONNECTED: + - 4> if MP is configured and MCG transmission (i.e. direct path) is not suspended; + - 5> initiate the indirect path failure information procedure as specified in 5. 7. 3c to report indirect path failure; + - 4> else if T301 is not running, initiate the RRC connection re-establishment procedure as specified in 5.3.7; + +- 3> else (the UE is L3 U2N Remote UE, or L2 U2N Remote UE in RRC\_IDLE or RRC\_INACTIVE): + - 4> if the PC5-RRC connection with the U2N Relay UE is determined to be released: + - 5> indicate upper layers to trigger PC5 unicast link release; + - 4> else (i.e., maintain the PC5 RRC connection): + - 5> if the UE is L2 U2N Remote UE and the *indicationType* is *relayUE-HO* or *relayUE-CellReselection*: + - 6> consider cell re-selection occurs; + +NOTE 1: For L3 U2N Remote UE, or L2 U2N Remote UE in RRC\_IDLE or RRC\_INACTIVE, it is up to Remote UE implementation whether to release or keep the PC5 unicast link. + +NOTE 2: The L2 U2N Remote UE may ignore the *NotificationMessageSidelink* if it does not release the PC5 unicast link in source side yet during an indirect-to-direct path switch, i.e. T304 is running. + +- 1> if the UE is acting as L2 U2U Remote UE: + - 2> if *sl-IndicationType* is *relayUE-PC5-RLF*: + - 3> indicate PC5 RLF received from L2 U2U Relay UE to the upper layers for the indicated L2 U2U Remote UE based on the received *sl-DestinationIdentityRemoteUE*; + - 3> perform PC5 RLF related actions as specified in 5.8.9.3, for the indicated L2 U2U Remote UE based on the received *sl-DestinationIdentityRemoteUE*; +- NOTE 3: It is up to the upper layers on whether to trigger U2U Relay reselection and whether to keep or release the PC5 link with the U2U Relay UE after the PC5 RLF indication received from U2U Relay UE. + +#### 5.8.9.11 Sidelink UE information + +##### 5.8.9.11.1 General + +![Sequence diagram showing the Sidelink UE information procedure between a Remote UE and a Relay UE. The Remote UE sends a UEInformationRequestSidelink message to the Relay UE, and the Relay UE responds with a UEInformationResponseSidelink message.](ca5555bb37f54857199d243feff8479e_img.jpg) + +``` + +sequenceDiagram + participant Remote UE + participant Relay UE + Note left of Remote UE: Remote UE + Remote UE->>Relay UE: UEInformationRequestSidelink + Note right of Relay UE: Relay UE + Relay UE-->>Remote UE: UEInformationResponseSidelink + +``` + +Sequence diagram showing the Sidelink UE information procedure between a Remote UE and a Relay UE. The Remote UE sends a UEInformationRequestSidelink message to the Relay UE, and the Relay UE responds with a UEInformationResponseSidelink message. + +Figure 5.8.9.11.1-1: Sidelink UE information procedure + +This purpose of this procedure is to transfer the UE information in sidelink. The L2 U2U Remote UE informs its end-to-end QoS information to its connected L2 U2U Relay UE in the *UEInformationRequestSidelink* message, and the L2 U2U Relay UE delivers the split QoS information of the first-hop to the Remote UE in the *UEInformationResponseSidelink* message. + +Editor's Note: Whether this message arrangement is optimal can be discussed in maintenance. Whether to cover the case the Relay UE updates the QoS split can be discussed in maintenance. + +##### 5.8.9.11.2 Actions related to transmission of the *UEInformationRequestSidelink* by the UE + +For initial information transfer (e.g. for QoS split) or upon change in any of the information in the *UEInformationRequestSidelink*, the UE shall set the contents of *UEInformationRequestSidelink* message as follows: + +- 1> if the UE is acting as L2 U2U Remote UE: + - 2> set *sl-E2E-QoS-ConnectionListPC5* to include the end-to-end QoS profile(s) of the sidelink QoS flow(s) of peer L2 U2U Remote UE if configured by the upper layer, and for each entry: + +- 3> set *sl-DestinationIdentityRemoteUE* to include the associated destination identity for peer L2 U2U Remote UE if configured by the upper layer; +- 2> submit the *UEInformationRequestSidelink* message to lower layers for transmission; + +##### 5.8.9.11.3 Actions related to reception of the *UEInformationRequestSidelink* by the UE + +The UE shall perform the following actions upon reception of the *UEInformationRequestSidelink*: + +- 1> if the UE is acting as L2 U2U Relay UE: + - 2> if the *UEInformationRequestSidelink* includes the *sl-E2E-QoS-ConnectionListPC5*: + - 3> perform QoS split based on the *sl-QoS-InfoList* for each QoS flow to decide the split PDB value for each PC5 hop; + - 3> set the contents of *UEInformationResponseSidelink* message as follows: + - 4> set *sl-SplitQoS-InfoListPC5* to include the split PDB value for each QoS flow on the first PC5 hop between L2 U2U Relay UE and L2 U2U Remote UE; + - 4> set *sl-DestinationIdentityRemoteUE* to include the associated destination identity for peer L2 U2U Remote UE if configured by the upper layer; + - 3> submit the *UEInformationResponseSidelink* message to lower layers for transmission; + +NOTE: It is left to Relay UE implementation on how to split the PDB. + +### 5.8.10 Sidelink measurement + +#### 5.8.10.1 Introduction + +The UE may configure the associated peer UE to perform NR sidelink measurement and report on the corresponding PC5-RRC connection in accordance with the NR sidelink measurement configuration for unicast by *RRCReconfigurationSidelink* message. + +The NR sidelink measurement configuration includes the following parameters for a PC5-RRC connection: + +1. **NR sidelink measurement objects:** Object(s) on which the associated peer UE shall perform the NR sidelink measurements. + - For NR sidelink measurement, a NR sidelink measurement object indicates the NR sidelink frequency of reference signals to be measured. +2. **NR sidelink reporting configurations:** NR sidelink measurement reporting configuration(s) where there can be one or multiple NR sidelink reporting configurations per NR sidelink measurement object. Each NR sidelink reporting configuration consists of the following: + - Reporting criterion: The criterion that triggers the UE to send a NR sidelink measurement report. This can either be periodical or a single event description. + - RS type: The RS that the UE uses for NR sidelink measurement results. In this release, only DMRS is supported for NR sidelink measurement. + - Reporting format: The quantities that the UE includes in the measurement report. In this release, only RSRP measurement is supported. +3. **NR sidelink measurement identities:** A list of NR sidelink measurement identities where each NR sidelink measurement identity links one NR sidelink measurement object with one NR sidelink reporting configuration. By configuring multiple NR sidelink measurement identities, it is possible to link more than one NR sidelink measurement object to the same NR sidelink reporting configuration, as well as to link more than one NR sidelink reporting configuration to the same NR sidelink measurement object. The NR sidelink measurement identity is also included in the NR sidelink measurement report that triggered the reporting, serving as a reference to the network. + +4. **NR sidelink quantity configurations:** The NR sidelink quantity configuration defines the NR sidelink measurement filtering configuration used for all event evaluation and related reporting, and for periodical reporting of that NR sidelink measurement. In each configuration, different filter coefficients can be configured for different NR sidelink measurement quantities. + +Both UEs of the PC5-RRC connection maintains a NR sidelink measurement object list, a NR sidelink reporting configuration list, and a NR sidelink measurement identities list according to signalling and procedures in this specification. + +#### 5.8.10.2 Sidelink measurement configuration + +##### 5.8.10.2.1 General + +The UE shall: + +- 1> if the received *sl-MeasConfig* includes the *sl-MeasObjectToRemoveList* in the *RRReconfigurationSidelink*: + - 2> perform the sidelink measurement object removal procedure as specified in 5.8.10.2.4; +- 1> if the received *sl-MeasConfig* includes the *sl-MeasObjectToAddModList* in the *RRReconfigurationSidelink*: + - 2> perform the sidelink measurement object addition/modification procedure as specified in 5.8.10.2.5; +- 1> if the received *sl-MeasConfig* includes the *sl-ReportConfigToRemoveList* in the *RRReconfigurationSidelink*: + - 2> perform the sidelink reporting configuration removal procedure as specified in 5.8.10.2.6; +- 1> if the received *sl-MeasConfig* includes the *sl-ReportConfigToAddModList* in the *RRReconfigurationSidelink*: + - 2> perform the sidelink reporting configuration addition/modification procedure as specified in 5.8.10.2.7; +- 1> if the received *sl-MeasConfig* includes the *sl-QuantityConfig* in the *RRReconfigurationSidelink*: + - 2> perform the sidelink quantity configuration procedure as specified in 5.8.10.2.8; +- 1> if the received *sl-MeasConfig* includes the *sl-MeasIdToRemoveList* in the *RRReconfigurationSidelink*: + - 2> perform the sidelink measurement identity removal procedure as specified in 5.8.10.2.2; +- 1> if the received *sl-MeasConfig* includes the *sl-MeasIdToAddModList* in the *RRReconfigurationSidelink*: + - 2> perform the sidelink measurement identity addition/modification procedure as specified in 5.8.10.2.3; + +##### 5.8.10.2.2 Sidelink measurement identity removal + +The UE shall: + +- 1> for each *sl-MeasId* included in the received *sl-MeasIdToRemoveList* that is part of the current UE configuration in *VarMeasConfigSL*: + - 2> remove the entry with the matching *sl-MeasId* from the *sl-MeasIdList* within the *VarMeasConfigSL*; + - 2> remove the NR sidelink measurement reporting entry for this *sl-MeasId* from the *VarMeasReportListSL*, if included; + - 2> stop the periodical reporting timer and reset the associated information (e.g. *sl-TimeToTrigger*) for this *sl-MeasId*. + +NOTE: The UE does not consider the message as erroneous if the *sl-MeasIdToRemoveList* includes any *sl-MeasId* value that is not part of the current UE configuration. + +##### 5.8.10.2.3 Sidelink measurement identity addition/modification + +The UE shall: + +- 1> for each *sl-MeasId* included in the received *sl-MeasIdToAddModList*: + +- 2> if an entry with the matching *sl-MeasId* exists in the *sl-MeasIdList* within the *VarMeasConfigSL*: + - 3> replace the entry with the value received for this *sl-MeasId*; +- 2> else: + - 3> add a new entry for this *sl-MeasId* within the *VarMeasConfigSL*; +- 2> remove the measurement reporting entry for this *sl-MeasId* from the *VarMeasReportListSL*, if included; +- 2> stop the periodical reporting timer and reset the associated information (e.g. *sl-TimeToTrigger*) for this *sl-MeasId*; + +##### 5.8.10.2.4 Sidelink measurement object removal + +The UE shall: + +- 1> for each *sl-MeasObjectId* included in the received *sl-MeasObjectToRemoveList* that is part of *sl-MeasObjectList* in *VarMeasConfigSL*: + - 2> remove the entry with the matching *sl-MeasObjectId* from the *sl-MeasObjectList* within the *VarMeasConfigSL*; + - 2> remove all *sl-MeasId* associated with this *sl-MeasObjectId* from the *sl-MeasIdList* within the *VarMeasConfigSL*, if any; + - 2> if a *sl-MeasId* is removed from the *sl-MeasIdList*: + - 3> remove the measurement reporting entry for this *sl-MeasId* from the *VarMeasReportListSL*, if included; + - 3> stop the periodical reporting timer and reset the associated information (e.g. *sl-TimeToTrigger*) for this *sl-MeasId*. + +NOTE: The UE does not consider the message as erroneous if the *sl-MeasObjectToRemoveList* includes any *sl-MeasObjectId* value that is not part of the current UE configuration. + +##### 5.8.10.2.5 Sidelink measurement object addition/modification + +The UE shall: + +- 1> for each *sl-MeasObject* included in the received *sl-MeasObjectToAddModList*: + - 2> if an entry with the matching *sl-MeasObjectId* exists in the *sl-MeasObjectList* within the *VarMeasConfigSL*, for this entry: + - 3> for each *sl-MeasId* associated with this *sl-MeasObjectId* included in the *sl-MeasIdList* within the *VarMeasConfigSL*, if any: + - 4> remove the measurement reporting entry for this *sl-MeasId* from the *VarMeasReportListSL*, if included; + - 4> stop the periodical reporting timer and reset the associated information (e.g. *sl-TimeToTrigger*) for this *sl-MeasId*; + - 3> reconfigure the entry with the value received for this *sl-MeasObject*; + - 2> else: + - 3> add a new entry for the received *sl-MeasObject* to the *sl-MeasObjectList* within *VarMeasConfigSL*. + +##### 5.8.10.2.6 Sidelink reporting configuration removal + +The UE shall: + +- 1> for each *sl-ReportConfigId* included in the received *sl-ReportConfigToRemoveList* that is part of the current UE configuration in *VarMeasConfigSL*: + +- 2> remove the entry with the matching *sl-ReportConfigId* from the *sl-ReportConfigList* within the *VarMeasConfigSL*; +- 2> remove all *sl-MeasId* associated with the *sl-ReportConfigId* from the *sl-MeasIdList* within the *VarMeasConfigSL*, if any; +- 2> if a *sl-MeasId* is removed from the *sl-MeasIdList*: + - 3> remove the measurement reporting entry for this *sl-MeasId* from the *VarMeasReportListSL*, if included; + - 3> stop the periodical reporting timer and reset the associated information (e.g. *sl-TimeToTrigger*) for this *sl-MeasId*. + +NOTE: The UE does not consider the message as erroneous if the *sl-ReportConfigToRemoveList* includes any *sl-ReportConfigId* value that is not part of the current UE configuration. + +##### 5.8.10.2.7 Sidelink reporting configuration addition/modification + +The UE shall: + +- 1> for each *sl-ReportConfigId* included in the received *sl-ReportConfigToAddModList*: + - 2> if an entry with the matching *sl-ReportConfigId* exists in the *sl-ReportConfigList* within the *VarMeasConfigSL*, for this entry: + - 3> reconfigure the entry with the value received for this *sl-ReportConfig*; + - 3> for each *sl-MeasId* associated with this *sl-ReportConfigId* included in the *sl-MeasIdList* within the *VarMeasConfigSL*, if any: + - 4> remove the measurement reporting entry for this *sl-MeasId* from the *VarMeasReportListSL*, if included; + - 4> stop the periodical reporting timer and reset the associated information (e.g. *sl-TimeToTrigger*) for this *sl-MeasId*; + - 2> else: + - 3> add a new entry for the received *sl-ReportConfig* to the *sl-ReportConfigList* within the *VarMeasConfigSL*. + +##### 5.8.10.2.8 Sidelink quantity configuration + +The UE shall: + +- 1> for each received *sl-QuantityConfig*: + - 2> set the corresponding parameter(s) in *sl-QuantityConfig* within *VarMeasConfigSL* to the value of the received *sl-QuantityConfig* parameter(s); +- 1> for each *sl-MeasId* included in the *sl-MeasIdList* within *VarMeasConfigSL*: + - 2> remove the measurement reporting entry for this *sl-MeasId* from the *VarMeasReportListSL*, if included; + - 2> stop the periodical reporting timer and reset the associated information (e.g. *sl-TimeToTrigger*) for this *sl-MeasId*. + +#### 5.8.10.3 Performing NR sidelink measurements + +##### 5.8.10.3.1 General + +A UE shall derive NR sidelink measurement results by measuring one or multiple DMRS associated per PC5-RRC connection as configured by the peer UE associated, as described in 5.8.10.3.2. For all NR sidelink measurement results the UE applies the layer 3 filtering as specified in clause 5.5.3.2, before using the measured results for evaluation of reporting criteria and measurement reporting. In this release, only NR sidelink RSRP can be configured as trigger quantity and reporting quantity. + +The UE shall: + +- 1) for each *sl-MeasId* included in the *sl-MeasIdList* within *VarMeasConfigSL*: + - 2) if the *sl-MeasObject* is associated to NR sidelink and the *sl-RS-Type* is set to *dmrs*: + - 3) derive the layer 3 filtered NR sidelink measurement result based on PSSCH DMRS for the trigger quantity and each measurement quantity indicated in *sl-ReportQuantity* using parameters from the associated *sl-MeasObject*, as described in 5.8.10.3.2. + - 2) perform the evaluation of reporting criteria as specified in 5.8.10.4. + +##### 5.8.10.3.2 Derivation of NR sidelink measurement results + +The UE may be configured by the peer UE associated to derive NR sidelink RSRP measurement results per PC5-RRC connection associated to the NR sidelink measurement objects based on parameters configured in the *sl-MeasObject* and in the *sl-ReportConfig*. + +The UE shall: + +- 1) for each NR sidelink measurement quantity to be derived based on NR sidelink DMRS: + - 2) derive the corresponding measurement of NR sidelink frequency indicated quantity based on PSSCH DMRS as described in TS 38.215 [9] in the concerned *sl-MeasObject*; + - 2) apply layer 3 filtering as described in 5.5.3.2; + +#### 5.8.10.4 Sidelink measurement report triggering + +##### 5.8.10.4.1 General + +The UE shall: + +- 1) for each *sl-MeasId* included in the *sl-MeasIdList* within *VarMeasConfigSL*: + - 2) if the *sl-ReportType* is set to *sl-EventTriggered* and if the entry condition applicable for this event, i.e. the event corresponding with the *sl-EventId* of the corresponding *sl-ReportConfig* within *VarMeasConfigSL*, is fulfilled for NR sidelink frequency for all NR sidelink measurements after layer 3 filtering taken during *sl-TimeToTrigger* defined for this event within the *VarMeasConfigSL*, while the *VarMeasReportListSL* does not include a NR sidelink measurement reporting entry for this *sl-MeasId* (a first NR sidelink frequency triggers the event): + - 3) include a NR sidelink measurement reporting entry within the *VarMeasReportListSL* for this *sl-MeasId*; + - 3) set the *sl-NumberOfReportsSent* defined within the *VarMeasReportListSL* for this *sl-MeasId* to 0; + - 3) include the concerned NR sidelink frequency in the *sl-FrequencyTriggeredList* defined within the *VarMeasReportListSL* for this *sl-MeasId*; + - 3) initiate the NR sidelink measurement reporting procedure, as specified in 5.8.10.5; + - 2) else if the *sl-ReportType* is set to *sl-EventTriggered* and if the entry condition applicable for this event, i.e. the event corresponding with the *sl-EventId* of the corresponding *sl-ReportConfig* within *VarMeasConfigSL*, is fulfilled for NR sidelink frequency not included in the *sl-FrequencyTriggeredList* for all NR sidelink measurements after layer 3 filtering taken during *sl-TimeToTrigger* defined for this event within the *VarMeasConfigSL* (a subsequent NR sidelink frequency triggers the event): + - 3) set the *sl-NumberOfReportsSent* defined within the *VarMeasReportListSL* for this *sl-MeasId* to 0; + - 3) include the concerned NR sidelink frequency in the *sl-FrequencyTriggeredList* defined within the *VarMeasReportListSL* for this *sl-MeasId*; + - 3) initiate the NR sidelink measurement reporting procedure, as specified in 5.8.10.5; + - 2) else if the *sl-ReportType* is set to *sl-EventTriggered* and if the leaving condition applicable for this event is fulfilled for NR sidelink frequency included in the *sl-FrequencyTriggeredList* defined within the *VarMeasReportListSL* for this *sl-MeasId* for all NR sidelink measurements after layer 3 filtering taken during *sl-TimeToTrigger* defined within the *VarMeasConfigSL* for this event: + - 3) set the *sl-NumberOfReportsSent* defined within the *VarMeasReportListSL* for this *sl-MeasId* to 0; + - 3) remove the concerned NR sidelink frequency from the *sl-FrequencyTriggeredList* defined within the *VarMeasReportListSL* for this *sl-MeasId*; + - 3) initiate the NR sidelink measurement reporting procedure, as specified in 5.8.10.5; + +- 3> remove the concerned NR sidelink frequency in the *sl-FrequencyTriggeredList* defined within the *VarMeasReportListSL* for this *sl-MeasId*; +- 3> if *sl-ReportOnLeave* is set to *true* for the corresponding reporting configuration: + - 4> initiate the NR sidelink measurement reporting procedure, as specified in 5.8.10.5; +- 3> if the *sl-FrequencyTriggeredList* defined within the *VarMeasReportListSL* for this *sl-MeasId* is empty: + - 4> remove the NR sidelink measurement reporting entry within the *VarMeasReportListSL* for this *sl-MeasId*; + - 4> stop the periodical reporting timer for this *sl-MeasId*, if running; +- 2> if *sl-ReportType* is set to *sl-Periodical* and if a (first) NR sidelink measurement result is available: + - 3> include a NR sidelink measurement reporting entry within the *VarMeasReportListSL* for this *sl-MeasId*; + - 3> set the *sl-NumberOfReportsSent* defined within the *VarMeasReportListSL* for this *sl-MeasId* to 0; + - 3> initiate the NR sidelink measurement reporting procedure, as specified in 5.8.10.5, immediately after the quantity to be reported becomes available for the NR sidelink frequency; +- 2> upon expiry of the periodical reporting timer for this *sl-MeasId*: + - 3> initiate the NR sidelink measurement reporting procedure, as specified in 5.8.10.5. + +##### 5.8.10.4.2 Event S1 (Serving becomes better than threshold) + +The UE shall: + +- 1> consider the entering condition for this event to be satisfied when condition S1-1, as specified below, is fulfilled; +- 1> consider the leaving condition for this event to be satisfied when condition S1-2, as specified below, is fulfilled; +- 1> for this NR sidelink measurement, consider the NR sidelink frequency corresponding to the associated *sl-MeasObject* associated with this event. + +Inequality S1-1 (Entering condition) + +$$Ms - Hys > Thresh$$ + +Inequality S1-2 (Leaving condition) + +$$Ms + Hys < Thresh$$ + +The variables in the formula are defined as follows: + +*Ms* is the NR sidelink measurement result of the NR sidelink frequency, not taking into account any offsets. + +*Hys* is the hysteresis parameter for this event (i.e. *sl-Hysteresis* as defined within *sl-ReportConfig* for this event). + +*Thresh* is the threshold parameter for this event (i.e. *sl-Threshold* as defined within *sl-ReportConfig* for this event). + +*Ms* is expressed in dBm in case of RSRP. + +*Hys* is expressed in dB. + +*Thresh* is expressed in the same unit as *Ms*. + +##### 5.8.10.4.3 Event S2 (Serving becomes worse than threshold) + +The UE shall: + +- 1> consider the entering condition for this event to be satisfied when condition S2-1, as specified below, is fulfilled; +- 1> consider the leaving condition for this event to be satisfied when condition S2-2, as specified below, is fulfilled; + +1> for this NR sidelink measurement, consider the NR sidelink frequency indicated by the *sl-MeasObject* associated to this event. + +Inequality S2-1 (Entering condition) + +$$Ms + Hys < Thresh$$ + +Inequality S2-2 (Leaving condition) + +$$Ms - Hys > Thresh$$ + +The variables in the formula are defined as follows: + +*Ms* is the NR sidelink measurement result of the NR sidelink frequency, not taking into account any offsets. + +*Hys* is the hysteresis parameter for this event (i.e. *sl-Hysteresis* as defined within *sl-ReportConfig* for this event). + +*Thresh* is the threshold parameter for this event (i.e. *s2-Threshold* as defined within *sl-ReportConfig* for this event). + +*Ms* is expressed in dBm in case of RSRP. + +*Hys* is expressed in dB. + +*Thresh* is expressed in the same unit as *Ms*. + +#### 5.8.10.5 Sidelink measurement reporting + +##### 5.8.10.5.1 General + +![Diagram showing NR sidelink measurement reporting between two User Equipment (UE) blocks. A horizontal line labeled 'MeasurementReportSidelink' connects the two UEs, indicating the direction of the report.](a49e8b30bf89da457ff3ff90d029e4ec_img.jpg) + +``` + +graph LR + UE1[UE] -- "MeasurementReportSidelink" --> UE2[UE] + +``` + +Diagram showing NR sidelink measurement reporting between two User Equipment (UE) blocks. A horizontal line labeled 'MeasurementReportSidelink' connects the two UEs, indicating the direction of the report. + +Figure 5.8.10.5.1-1: NR sidelink measurement reporting + +The purpose of this procedure is to transfer measurement results from the UE to the peer UE associated. + +For the *sl-MeasId* for which the NR sidelink measurement reporting procedure was triggered, the UE shall set the *sl-MeasResults* within the *MeasurementReportSidelink* message as follows: + +- 1> set the *sl-MeasId* to the measurement identity that triggered the NR sidelink measurement reporting; +- 1> if the *sl-ReportConfig* associated with the *sl-MeasId* that triggered the NR sidelink measurement reporting is set to *sl-EventTriggered* or *sl-Periodical*: + - 2> if the *sl-RS-Type* within *sl-ReportConfig* is set to *dmrs*: + - 3> set *sl-ResultDMRS* within *sl-MeasResult* to include the NR sidelink DMRS based quantity indicated in the *sl-ReportQuantity* within the concerned *sl-ReportConfig*; + - 2> if the *sl-RS-Type* within *sl-ReportConfig* is set to *sl-prs*: + - 3> set *sl-ResultSL-PRS* within *sl-MeasResult* to include the NR SL-PRS based quantity indicated in the *sl-ReportQuantity* within the concerned *sl-ReportConfig*; +- 1> increment the *sl-NumberOfReportsSent* as defined within the *VarMeasReportListSL* for this *sl-MeasId* by 1; +- 1> stop the periodical reporting timer, if running; +- 1> if the *sl-NumberOfReportsSent* as defined within the *VarMeasReportListSL* for this *sl-MeasId* is less than the *sl-ReportAmount* as defined within the corresponding *sl-ReportConfig* for this *sl-MeasId*: + +- 2> start the periodical reporting timer with the value of *sl-ReportInterval* as defined within the corresponding *sl-ReportConfig* for this *sl-MeasId*; +- 1> else: + - 2> if the *sl-ReportType* is set to *sl-Periodical*: + - 3> remove the entry within the *VarMeasReportListSL* for this *sl-MeasId*; + - 3> remove this *sl-MeasId* from the *sl-MeasIdList* within *VarMeasConfigSL*; + - 1> submit the *MeasurementReportSidelink* message to lower layers for transmission, upon which the procedure ends. + +### 5.8.11 Zone identity calculation + +The UE shall determine an identity of the zone (i.e. *Zone\_id*) in which it is located using the following formulae, if *sl-ZoneConfig* is configured: + +$$x_1 = \text{Floor } (x / L) \text{ Mod } 64;$$ + +$$y_1 = \text{Floor } (y / L) \text{ Mod } 64;$$ + +$$\text{Zone\_id} = y_1 * 64 + x_1.$$ + +The parameters in the formulae are defined as follows: + +**L** is the value of *sl-ZoneLength* included in *sl-ZoneConfig*; + +**x** is the geodesic distance in longitude between UE's current location and geographical coordinates (0, 0) according to WGS84 model [58] and it is expressed in meters; + +**y** is the geodesic distance in latitude between UE's current location and geographical coordinates (0, 0) according to WGS84 model [58] and it is expressed in meters. + +NOTE: How the calculated *zone\_id* is used is specified in TS 38.321 [3]. + +### 5.8.12 DFN derivation from GNSS + +When the UE selects GNSS as the synchronization reference source, the DFN, the subframe number within a frame and slot number within a frame used for NR sidelink communication/discovery are derived from the current UTC time, by the following formulae: + +$$\text{DFN} = \text{Floor } (0.1 * (T_{\text{current}} - T_{\text{ref}} - \text{OffsetDFN})) \text{ mod } 1024$$ + +$$\text{SubframeNumber} = \text{Floor } (T_{\text{current}} - T_{\text{ref}} - \text{OffsetDFN}) \text{ mod } 10$$ + +$$\text{SlotNumber} = \text{Floor } ((T_{\text{current}} - T_{\text{ref}} - \text{OffsetDFN}) * 2^\mu) \text{ mod } (10 * 2^\mu)$$ + +Where: + +***Tcurrent*** is the current UTC time obtained from GNSS. This value is expressed in milliseconds; + +***Tref*** is the reference UTC time 00:00:00 on Gregorian calendar date 1 January, 1900 (midnight between Thursday, December 31, 1899 and Friday, January 1, 1900). This value is expressed in milliseconds; + +***OffsetDFN*** is the value *sl-OffsetDFN* if configured, otherwise it is zero. This value is expressed in milliseconds. + +$\mu=0/1/2/3$ corresponding to the 15/30/60/120 kHz of SCS for SL, respectively. + +NOTE 1: In case of leap second change event, how UE obtains the scheduled time of leap second change to adjust *Tcurrent* correspondingly is left to UE implementation. How UE handles to avoid the sudden discontinuity of DFN is left to UE implementation. + +NOTE 2: Void. + +### 5.8.13 NR sidelink discovery + +#### 5.8.13.1 General + +The purpose of this procedure is to perform NR sidelink discovery as specified in TS 23.304 [65]. + +#### 5.8.13.2 NR sidelink discovery monitoring + +A UE capable of NR sidelink discovery that is configured by upper layers to monitor NR sidelink discovery messages shall: + +- 1> if the frequency used for NR sidelink discovery is included in *sl-FreqInfoToAddModList* in *RRCREconfiguration* message and *sl-DiscConfig* is included in *RRCREconfiguration*; or if the frequency used for NR sidelink discovery is included in *sl-FreqInfoList* included in *SIB12* and *sl-DiscConfigCommon* is included in *SIB12*: + - 2> if the UE is configured with *sl-DiscRxPool* for NR sidelink discovery reception included in *RRCREconfiguration* message with *reconfigurationWithSync* (i.e. handover): + - 3> configure lower layers to monitor sidelink control information and the corresponding data using the resource pool indicated by *sl-DiscRxPool* for NR sidelink discovery reception in *RRCREconfiguration*; + - 2> else if the UE is configured with *sl-RxPool* for NR sidelink discovery reception included in *RRCREconfiguration* message with *reconfigurationWithSync* (i.e. handover): + - 3> configure lower layers to monitor sidelink control information and the corresponding data using the resource pool indicated by *sl-RxPool* for NR sidelink discovery reception in *RRCREconfiguration*; + - 2> else if the cell chosen for NR sidelink discovery reception provides *SIB12*: + - 3> if *sl-DiscRxPool* for NR sidelink discovery reception is included in *SIB12*: + - 4> configure lower layers to monitor sidelink control information and the corresponding data using the resource pool indicated by *sl-DiscRxPool* for NR sidelink discovery reception in *SIB12*; + - 3> else if *sl-RxPool* for NR sidelink discovery reception is included in *SIB12*: + - 4> configure lower layers to monitor sidelink control information and the corresponding data using the resource pool indicated by *sl-RxPool* for NR sidelink discovery reception in *SIB12*; +- 1> else: + - 2> if out of coverage on the concerned frequency for NR sidelink discovery: + - 3> if *sl-DiscRxPool* was preconfigured: + - 4> configure lower layers to monitor sidelink control information and the corresponding data using the resource pool that was preconfigured by *sl-DiscRxPool* for NR sidelink discovery reception in *SL-PreconfigurationNR*, as defined in clause 9.3; + - 3> else: + - 4> configure lower layers to monitor sidelink control information and the corresponding data using the resource pool that was preconfigured by *sl-RxPool* for NR sidelink discovery reception in *SL-PreconfigurationNR*, as defined in clause 9.3; + +NOTE: If *sl-DiscRxPool* and *sl-RxPool* are both included in *SIB12* or preconfigured, it is up to UE implementation whether to monitor sidelink control information and the corresponding data using the resource pool indicated by *sl-RxPool* for NR sidelink discovery reception. + +#### 5.8.13.3 NR sidelink discovery transmission + +A UE capable of NR sidelink discovery that is configured by upper layer to transmit NR sidelink discovery message shall: + +- 1> if the frequency used for NR sidelink discovery is included in *sl-FreqInfoToAddModList* in *sl-ConfigDedicatedNR* within *RRCReconfiguration* message; or if the frequency used for NR sidelink discovery is included in *sl-FreqInfoList* within *SIB12*: +- 2> if the UE is in *RRC\_CONNECTED* and uses the frequency included in *sl-ConfigDedicatedNR* within *RRCReconfiguration* message: + - 3> if the UE is acting as NR sidelink U2N Relay UE and *sl-DiscConfig* is included in *RRCReconfiguration*, and if the NR sidelink U2N Relay UE threshold conditions as specified in 5.8.14.2 are met based on *sl-RelayUE-Config*; or + - 3> if the UE is selecting NR sidelink U2N Relay UE / has a selected NR sidelink U2N Relay UE/ configured with measurement object associated to L2 U2N Relay UEs and *sl-DiscConfig* is included in *RRCReconfiguration*, and if the NR sidelink U2N Remote UE threshold conditions as specified in 5.8.15.2 are met based on *sl-RemoteUE-Config*; or + - 3> if the UE is selecting NR sidelink U2U Relay UE / has a selected NR sidelink U2U Relay UE and *sl-DiscConfig* is included in *RRCReconfiguration*, and if the NR sidelink U2U Remote UE threshold conditions associated with the peer NR Sidelink U2U Remote UE as specified in 5.8.17.2 are met based on *sl-RemoteUE-ConfigU2U*; or + - 3> if the UE acting as Target Remote UE is performing U2U Relay Discovery with Model B and *sl-DiscConfig* is included in *RRCReconfiguration*, and if the NR sidelink U2U Remote UE threshold conditions associated with the NR sidelink U2U Relay UE as specified in 5.8.17.2 are met based on *sl-RemoteUE-ConfigU2U*; or + - 3> if the UE acting as U2U Relay UE is performing U2U Relay Discovery with Model A or Model B response message as specified in TS 23.304[65]; or + - 3> if the UE acting as U2U Relay UE is performing U2U Relay Discovery with Model B as specified in TS 23.304[65] and *sl-DiscConfig* is included in *RRCReconfiguration*, and if the NR sidelink U2U Relay UE threshold conditions as specified in 5.8.16.2 are met based on *sl-RelayUE-ConfigU2U*; or + +NOTE 1: For U2U Relay UE and Target Remote UE, it can be up to UE implementation on cross-layer interaction for the AS layer condition check for discovery message forwarding. + +- 3> if the UE is performing NR sidelink non-relay discovery: + - 4> if the UE is configured with *sl-ScheduledConfig*: + - 5> if T310 for MCG or T311 is running; and if *sl-TxPoolExceptional* is included in *sl-FreqInfoList* for the concerned frequency in *SIB12* or included in *sl-ConfigDedicatedNR* in *RRCReconfiguration*; or + - 5> if T301 is running and the cell on which the UE initiated RRC connection re-establishment provides *SIB12* including *sl-TxPoolExceptional* for the concerned frequency; or + - 5> if T304 for MCG is running and the UE is configured with *sl-TxPoolExceptional* included in *sl-ConfigDedicatedNR* for the concerned frequency in *RRCReconfiguration*: + - 6> configure lower layers to perform the sidelink resource allocation mode 2 based on random selection using the resource pool indicated by *sl-TxPoolExceptional* as defined in TS 38.321 [3] for NR sidelink discovery transmission; + - 5> else: + - 6> configure lower layers to perform the sidelink resource allocation mode 1 using the resource pool indicated by *sl-DiscTxPoolScheduling* or *sl-TxPoolScheduling* for NR sidelink discovery transmission on the concerned frequency in *RRCReconfiguration*; + - 5> if T311 is running, configure the lower layers to release the resources indicated by *rrc-ConfiguredSidelinkGrant* (if any); + - 4> if the UE is configured with *sl-UE-SelectedConfig*: + +- 5> if the *sl-DiscTxPoolSelected* for NR sidelink discovery transmission on the concerned frequency is included in the *sl-ConfigDedicatedNR* within *RRReconfiguration*, and if a result of full/partial sensing, if selected and is allowed by *sl-AllowedResourceSelectionConfig*, on the resources configured in *sl-DiscTxPoolSelected* for NR sidelink discovery transmission on the concerned frequency included in *sl-ConfigDedicatedNR* within *RRReconfiguration* is not available in accordance with TS 38.214 [19]; or +- 5> if the *sl-DiscTxPoolSelected* for NR sidelink discovery transmission on the concerned frequency is not included in the *sl-ConfigDedicatedNR* within *RRReconfiguration*, and a result of full/partial sensing, if selected and is allowed by *sl-AllowedResourceSelectionConfig*, on the resources configured in *sl-TxPoolSelectedNormal* for NR sidelink discovery transmission on the concerned frequency included in *sl-ConfigDedicatedNR* within *RRReconfiguration* is not available in accordance with TS 38.214 [19]; +- 6> if *sl-TxPoolExceptional* for the concerned frequency is included in *RRReconfiguration*; or +- 6> if the PCell provides *SIB12* including *sl-TxPoolExceptional* in *sl-FreqInfoList* for the concerned frequency: + - 7> configure lower layers to perform the sidelink resource allocation mode 2 based on random selection using the resource pool indicated by *sl-TxPoolExceptional* as defined in TS 38.321 [3] for NR sidelink discovery transmission; +- 5> else, if the *sl-DiscTxPoolSelected* for NR sidelink discovery transmission on the concerned frequency is included in the *sl-ConfigDedicatedNR* within *RRReconfiguration*: + - 6> configure lower layers to perform the sidelink resource allocation mode 2 based on resource selection operation according to *sl-AllowedResourceSelectionConfig* (as defined in TS 38.321 [3] and TS 38.214 [19]) using the pools of resources indicated by *sl-DiscTxPoolSelected* for NR sidelink discovery transmission on the concerned frequency in *RRReconfiguration*; +- 5> else, if the *sl-TxPoolSelectedNormal* for NR sidelink discovery transmission on the concerned frequency is included in the *sl-ConfigDedicatedNR* within *RRReconfiguration*: + - 6> configure lower layers to perform the sidelink resource allocation mode 2 based on resource selection operation according to *sl-AllowedResourceSelectionConfig* (as defined in TS 38.321 [3] and TS 38.214 [19]) using the pools of resources indicated by *sl-TxPoolSelectedNormal* for NR sidelink discovery transmission on the concerned frequency in *RRReconfiguration*; +- 2> else if the cell chosen for NR sidelink discovery transmission provides *SIB12*: + - 3> if the UE is acting as NR sidelink U2N Relay UE and *sl-DiscConfigCommon* is included in *SIB12*, and if the NR sidelink U2N Relay UE threshold conditions as specified in 5.8.14.2 are met based on *sl-RelayUE-ConfigCommon* in *SIB12*; or + - 3> if the UE is selecting NR sidelink U2N Relay UE / has a selected NR sidelink U2N Relay UE and *sl-DiscConfigCommon* is included in *SIB12*, and if the NR sidelink U2N Remote UE threshold conditions as specified in 5.8.15.2 are met based on *sl-RemoteUE-ConfigCommon* in *SIB12*; or + - 3> if the UE is selecting NR sidelink U2U Relay UE / has a selected NR sidelink U2U Relay UE and *sl-DiscConfigCommon* is included in *SIB12*, and if the NR sidelink U2U Remote UE threshold conditions associated with the peer NR Sidelink U2U Remote UE as specified in 5.8.17.2 are met based on *sl-RemoteUE-ConfigCommonU2U* in *SIB12*; or + - 3> if the UE acting as Target Remote UE is performing U2U Relay Discovery with Model B and if the NR sidelink U2U Remote UE threshold conditions associated with the NR sidelink U2U Relay UE as specified in 5.8.17.2 are met based on *sl-RemoteUE-ConfigCommonU2U* in *SIB12*; or + - 3> if the UE acting as U2U Relay UE is performing U2U Relay Discovery with Model A or Model B response message as specified in TS 23.304[65]; or + - 3> if the UE acting as U2U Relay UE is performing U2U Relay Discovery with Model B as specified in TS 23.304[65] and if the NR sidelink U2U Relay UE threshold conditions as specified in 5.8.16.2 are met based on *sl-RelayUE-ConfigCommonU2U* in *SIB12*; or + +- 3> if the UE is performing NR sidelink non-relay discovery: + - 4> if *SIB12* includes *sl-DiscTxPoolSelected* for NR sidelink discovery transmission on the concerned frequency, and a result of full/partial sensing, if selected and is allowed by *sl-AllowedResourceSelectionConfig*, on the resources configured in the *sl-DiscTxPoolSelected* for NR sidelink discovery transmission is available in accordance with TS 38.214 [19] or random selection, if allowed by *sl-AllowedResourceSelectionConfig*, is selected: + - 5> configure lower layers to perform the sidelink resource allocation mode 2 based on resource selection operation according to *sl-AllowedResourceSelectionConfig* using the pools of resources indicated by *sl-DiscTxPoolSelected* for NR sidelink discovery transmission on the concerned frequency in *SIB12* as defined in TS 38.321 [3]; + - 4> else if *SIB12* includes *sl-TxPoolSelectedNormal* for NR sidelink discovery transmission on the concerned frequency, and a result of full/partial sensing, if selected and is allowed by *sl-AllowedResourceSelectionConfig*, on the resources configured in the *sl-TxPoolSelectedNormal* for NR sidelink discovery transmission is available in accordance with TS 38.214 [19] or random selection, if allowed by *sl-AllowedResourceSelectionConfig*, is selected: + - 5> configure lower layers to perform the sidelink resource allocation mode 2 based on resource selection operation according to *sl-AllowedResourceSelectionConfig* using the pools of resources indicated by *sl-TxPoolSelectedNormal* for NR sidelink discovery transmission on the concerned frequency in *SIB12* as defined in TS 38.321 [3]; + - 4> else if *SIB12* includes *sl-TxPoolExceptional* for the concerned frequency: + - 5> from the moment the UE initiates RRC connection establishment or RRC connection resume, until receiving an *RRCReconfiguration* including *sl-ConfigDedicatedNR*, or receiving an *RRRelease* or an *RRReject*; or + - 5> if a result of full/partial sensing, if selected and is allowed by *sl-AllowedResourceSelectionConfig*, on the resources configured in *sl-DiscTxPoolSelected* for NR sidelink discovery transmission on the concerned frequency in *SIB12* is not available in accordance with TS 38.214 [19]; or + - 5> if *sl-DiscTxPoolSelected* for NR sidelink discovery transmission on the concerned frequency is not included in *SIB12* and if a result of full/partial sensing, if selected and is allowed by *sl-AllowedResourceSelectionConfig*, on the resources configured in *sl-TxPoolSelectedNormal* for NR sidelink discovery transmission on the concerned frequency in *SIB12* is not available in accordance with TS 38.214 [19]: + - 6> configure lower layers to perform the sidelink resource allocation mode 2 based on random selection (as defined in TS 38.321 [3]) using one of the pools of resources indicated by *sl-TxPoolExceptional* for NR sidelink discovery transmission on the concerned frequency; +- 1> else if out of coverage on the concerned frequency for NR sidelink discovery: + - 2> if the UE is acting as L3 U2N Relay UE; or + - 2> if the UE is selecting NR sidelink U2N Relay UE / has a selected NR sidelink U2N Relay UE and if the NR sidelink U2N Remote UE threshold conditions as specified in 5.8.15.2 are met based on *sl-PreconfigDiscConfig* in *SidelinkPreconfigNR*; or + - 2> if the UE is selecting NR sidelink U2U Relay UE / has a selected NR sidelink U2U Relay UE and if the NR sidelink U2U Remote UE threshold conditions associated with the peer NR sidelink U2U Remote UE as specified in 5.8.17.2 are met based on *sl-RemoteUE-PreconfigU2U* in *SidelinkPreconfigNR*; or + - 2> if the UE acting as Target Remote UE is performing U2U Relay Discovery with Model B and if the NR sidelink U2U Remote UE threshold conditions associated with the NR sidelink U2U Relay UE as specified in 5.8.17.2 are met based on *sl-RemoteUE-PreconfigU2U* in *SidelinkPreconfigNR*; or + - 2> if the UE acting as U2U Relay UE is performing U2U Relay Discovery with Model A or Model B response message as specified in TS 23.304[65]; or + +- 2> if the UE acting as U2U Relay UE is performing U2U Relay Discovery with Model B as specified in TS 23.304[65] and if the NR sidelink U2U Relay UE threshold conditions as specified in 5.8.16.2 are met based on *sl-RelayUE-PreconfigU2U* in *SidelinkPreconfigNR*; or +- 2> if the UE is performing NR sidelink non-relay discovery: + - 3> configure lower layers to perform the sidelink resource allocation mode 2 based on resource selection operation according to *sl-AllowedResourceSelectionConfig* (as defined in TS 38.321 [3] and TS 38.213 [13]) using the pools of resources indicated in *sl-DiscTxPoolSelected* or *sl-TxPoolSelectedNormal* for NR sidelink discovery transmission on the concerned frequency in *SidelinkPreconfigNR*. + +NOTE 2: It is up to UE implementation to determine, in accordance with TS 38.321[3], which resource pool to use if multiple resource pools are configured, and which resource allocation scheme is used in the AS based on UE capability (for a UE in RRC\_IDLE/RRC\_INACTIVE) and the allowed resource schemes *sl-allowedResourceSelectionConfig* in the resource pool configuration. + +### 5.8.14 NR sidelink U2N Relay UE operation + +#### 5.8.14.1 General + +This procedure is used by a UE supporting NR sidelink U2N Relay UE operation configured by upper layers to transmit NR sidelink discovery messages to evaluate AS layer conditions. + +#### 5.8.14.2 NR sidelink U2N Relay UE threshold conditions + +A UE capable of NR sidelink U2N Relay UE operation shall: + +- 1> if the threshold conditions specified in this clause were previously not met: + - 2> if *threshHighRelay* is not configured; or the RSRP measurement of the PCell, or the cell on which the UE camps, is below *threshHighRelay* by *hystMaxRelay* if configured; and + - 2> if *threshLowRelay* is not configured; or the RSRP measurement of the PCell, or the cell on which the UE camps, is above *threshLowRelay* by *hystMinRelay* if configured: + - 3> consider the threshold conditions to be met (entry); +- 1> else: + - 2> if the RSRP measurement of the PCell, or the cell on which the UE camps, is above *threshHighRelay* if configured; or + - 2> if the RSRP measurement of the PCell, or the cell on which the UE camps, is below *threshLowRelay* if configured; + - 3> consider the threshold conditions not to be met (leave); + +### 5.8.15 NR sidelink U2N Remote UE operation + +#### 5.8.15.1 General + +This procedure is used by a UE supporting NR sidelink U2N Remote UE operation configured by upper layers to transmit NR sidelink discovery message to evaluate AS layer conditions. The procedure is also used to perform selection and reselection of NR sidelink U2N Relay UE. + +#### 5.8.15.2 NR Sidelink U2N Remote UE threshold conditions + +A UE capable of NR sidelink U2N Remote UE operation shall: + +- 1> if the threshold conditions specified in this clause were previously not met: + - 2> if *threshHighRemote* is not configured; or the RSRP measurement of the PCell, or the cell on which the UE camps, is below *threshHighRemote* by *hystMaxRemote* if configured, or + - 2> if the UE has no serving cell: + +- 3> consider the threshold conditions to be met (entry); +- 1> else: + - 2> if the RSRP measurement of the PCell, or the cell on which the UE camps, is above *threshHighRemote* if configured: + - 3> consider the threshold conditions not to be met (leave); + +The L2 U2N Remote UE not configured with MP considers the cell indicated by *sl-ServingCellInfo* in the *SL-AccessInfo-L2U2N-r17* received from the connected L2 U2N Relay UE as the PCell/camping cell. + +#### 5.8.15.3 Selection and reselection of NR sidelink U2N Relay UE + +A UE capable of NR sidelink U2N Remote UE operation that is configured by upper layers to search for a NR sidelink U2N Relay UE shall: + +- 1> if the UE has no serving cell; or +- 1> if the RSRP measurement of the cell on which the UE camps (for L2 and L3 U2N Remote UE in RRC\_IDLE or RRC\_INACTIVE)/ the PCell (for L3 U2N Remote UE in RRC\_CONNECTED) is below *threshHighRemote* within *sl-RemoteUE-Config*: + - 2> if the UE does not have a selected NR sidelink U2N Relay UE; or + - 2> if the UE has a selected NR sidelink U2N Relay UE, and SL-RSRP of the currently selected NR sidelink U2N Relay UE is available and is below *sl-RSRP-Thresh*; or + - 2> if the UE has a selected NR sidelink U2N Relay UE, and SL-RSRP of the currently selected NR sidelink U2N Relay UE is not available, and SD-RSRP of the currently selected U2N Relay UE is below *sl-RSRP-Thresh*; or + +NOTE 1: U2N Remote UE uses SL-RSRP measurements for relay reselection trigger evaluation when there is data transmission from U2N Relay UE to U2N Remote UE, and it is left to UE implementation whether to use SL-RSRP or SD-RSRP for relay reselection trigger evaluation in case of no data transmission from U2N Relay UE to U2N Remote UE. If SD-RSRP is used, the discovery procedure will be performed between the U2N Remote UE and the selected U2N Relay UE. + +- 2> if the UE has a selected NR sidelink U2N Relay UE, and upper layers indicate not to use the currently selected NR sidelink U2N Relay UE; or +- 2> if the UE has a selected NR sidelink U2N Relay UE, and upper layers request the release of the PC5-RRC connection; or +- 2> if the UE has a selected NR sidelink U2N Relay UE, and sidelink radio link failure is detected on the PC5-RRC connection with the current U2N Relay UE as specified in clause 5.8.9.3: + - 3> perform NR sidelink discovery procedure as specified in clause 5.8.13 in order to search for candidate NR sidelink U2N Relay UEs; + - 4> when evaluating the one or more detected NR sidelink U2N Relay UEs, apply layer 3 filtering as specified in 5.5.3.2 across measurements that concern the same U2N Relay UE ID and using the *sl-FilterCoefficientRSRP* in *SIB12* (if in RRC\_IDLE/INACTIVE), the *sl-FilterCoefficientRSRP* in *sl-ConfigDedicatedNR* (if in RRC\_CONNECTED) or the preconfigured *sl-FilterCoefficientRSRP* as defined in 9.3 (out of coverage), before using the SD-RSRP measurement results; + - 4> consider a candidate NR sidelink U2N Relay UE for which SD-RSRP exceeds *sl-RSRP-Thresh* by *sl-HystMin* has met the AS criteria; + - 3> if the UE detects any suitable NR sidelink U2N Relay UE(s): + - 4> consider one of the available suitable NR sidelink U2N relay UE(s) can be selected; + +NOTE 2: A candidate NR sidelink U2N Relay UE which meets all AS layer criteria defined in 5.8.15.3 and higher layer criteria defined in TS 23.304 [65] can be regarded as suitable NR sidelink U2N Relay UE by the NR sidelink U2N Remote UE. If multiple suitable NR sidelink U2N Relay UEs are available, it is up to Remote UE implementation to choose one NR sidelink U2N Relay UE. The details of the interaction with upper layers are up to UE implementation. + +NOTE 3: For L2 U2N Remote UEs in RRC\_IDLE/INACTIVE and L3 U2N Remote UEs, the cell (re)selection procedure and relay (re)selection procedure run independently. If both suitable cells and suitable NR sidelink U2N Relay UEs are available, it is up to NR sidelink U2N Remote UE implementation to select either a cell or a NR sidelink U2N Relay UE. Furthermore, L3 U2N Remote UE's selection on both cell and NR sidelink U2N Relay UE is also based on UE implementation. + +3> else: + +4> consider no NR sidelink U2N Relay UE to be selected. + +### 5.8.16 NR sidelink U2U Relay UE operation + +#### 5.8.16.1 General + +This procedure is used by a UE supporting NR sidelink U2U Relay UE operation configured by upper layers to forward NR sidelink integrated discovery messages or Model B Discovery messages to evaluate AS layer conditions. The procedure is also used to determine whether a NR sidelink UE is in proximity to NR sidelink U2U Relay UE in Model A Discovery messages. + +#### 5.8.16.2 NR sidelink U2U Relay UE threshold conditions + +A UE capable of NR sidelink U2U Relay UE operation shall: + +1> if the threshold conditions for integrated Discovery specified in this clause were previously not met: + +2> if the *sd-RSRP-Thresh-DiscConfig* is not configured, or if the SL-RSRP of the Direct Communication Request message with integrated Discovery received from the Source NR sidelink U2U Remote UE is available and is above *sd-RSRP-Thresh-DiscConfig* if configured: + +3> consider the threshold conditions to be met (entry); + +1> else: + +2> if the SL-RSRP of the Direct Communication Request message with integrated Discovery received from the Source NR sidelink U2U Remote UE is available and is below *sd-RSRP-Thresh-DiscConfig* by *sd-hystMaxRelay* if configured: + +3> consider the threshold conditions not to be met (leave); + +1> if the threshold conditions for Model B Discovery specified in this clause were previously not met: + +2> if the *sd-RSRP-Thresh-DiscConfig* is not configured, or if the SD-RSRP of the Model B Discovery message received from the Source NR sidelink U2U Remote UE is available and is above *sd-RSRP-Thresh-DiscConfig* if configured: + +3> consider the threshold conditions to be met (entry); + +1> else: + +2> if the SD-RSRP of the Model B Discovery message received from the Source NR sidelink U2U Remote UE is available and is below *sd-RSRP-Thresh-DiscConfig* by *sd-hystMaxRelay* if configured: + +3> consider the threshold conditions not to be met (leave); + +#### 5.8.16.3 Neighbor UE(s) in proximity conditions + +A UE capable of NR sidelink U2U Relay UE operation and is performing U2U Relay Discovery with Model A as specified in TS 23.304[65] shall: + +- 1> for each of potential neighbor UE(s): + - 2> if the SL-RSRP of the UE is available and is above *sl-RSRP-Thresh-DiscConfig* if configured; or + - 2> if the SD-RSRP of the UE is available and is above *sd-RSRP-Thresh-DiscConfig* if configured: + - 3> consider the UE as neighbor UE in discovery message to be transmitted as defined in TS 23.304 [65]. + +NOTE: The interaction with upper layers is left to UE implementation. + +### 5.8.17 NR sidelink U2U Remote UE operation + +#### 5.8.17.1 General + +This procedure is used by a UE supporting NR sidelink U2U Remote UE operation configured by upper layers to transmit NR sidelink discovery messages to evaluate AS layer conditions. The procedure is also used to perform selection and reselection of NR sidelink U2U Relay UE. + +#### 5.8.17.2 NR Sidelink U2U Remote UE threshold conditions + +A UE capable of NR sidelink U2U Remote UE operation shall: + +- 1> if the threshold conditions for direct PC5 link specified in this clause were previously not met: + - 2> if *sl-RSRP-ThreshU2U* is not configured, or if the SL-RSRP measurement of the peer NR sidelink U2U Remote UE is available and is below *sl-RSRP-ThreshU2U* by *sl-HystMinU2U* if configured; or + - 2> if *sd-RSRP-ThreshU2U* is not configured, or if the SD-RSRP measurement of the peer NR sidelink U2U Remote UE is available and is below *sd-RSRP-ThreshU2U* by *sd-HystMinU2U* if configured: + - 3> consider the threshold conditions to be met (entry); +- 1> else: + - 2> if the SL-RSRP measurement of the peer NR sidelink U2U Remote UE is available and is above *sl-RSRP-ThreshU2U* if configured; or + - 2> if the SD-RSRP measurement of the peer NR sidelink U2U Remote UE is available and is above *sd-RSRP-ThreshU2U* if configured: + - 3> consider the threshold conditions not to be met (leave); +- 1> if the threshold conditions for U2U relay discovery with Model B specified in this clause were previously not met: + - 2> if the *sd-RSRP-ThreshU2U* is not configured, or if the SD-RSRP of the NR sidelink U2U Relay UE is available and is above *sd-RSRP-ThreshU2U* if configured: + - 3> consider the threshold conditions to be met (entry); +- 1> else: + - 2> if the SD-RSRP of the NR sidelink U2U Relay UE is available and is below *sl-RSRP-ThreshU2U* by *sd-HystMinU2U* if configured: + - 3> consider the threshold conditions not to be met (leave); + +Editor's Note: FFS whether/how to capture if the SL-RSRP/SD-RSRP measurement of the peer NR sidelink U2U Remote UE is not available. + +#### 5.8.17.3 Conditions for Selection and reselection of NR sidelink U2U Relay UE + +A UE capable of NR sidelink U2U Remote UE operation shall initiate NR sidelink U2U Relay (re)slection procedure as specified in 5.8.17.4 when one of the following conditions is met: + +- 1> if configured by upper layers to search for or select a NR sidelink U2U Relay UE; or + +- 1> if the NR sidelink U2U Remote UE threshold conditions for direct PC5 link with the peer NR sidelink U2U Remote UE as specified in 5.8.17.2 are met within *sl-RemoteUE-ConfigU2U* if configured: + - 2> if the UE does not have a selected NR sidelink U2U Relay UE; or + - 2> if the UE has a selected NR sidelink U2U Relay UE, and SL-RSRP of the currently selected NR sidelink U2U Relay UE is available and is below *sl-RSRP-ThreshU2U* by *sl-HystMinU2U* within *sl-RemoteUE-ConfigU2U* if configured; or + - 2> if the UE has a selected NR sidelink U2U Relay UE, and SD-RSRP of the currently selected NR sidelink U2U Relay UE is available, and is below *sd-RSRP-ThreshU2U* by *sd-HystMinU2U* within *sl-RemoteUE-ConfigU2U* if configured; or + +NOTE: For relay selection, U2U Remote UE uses SL-RSRP measurements for relay selection trigger evaluation when there is data transmission from peer U2U Remote UE to U2U Remote UE. For relay reselection, U2U Remote UE uses SL-RSRP measurements for relay reselection trigger evaluation when there is data transmission from U2U Relay UE to U2U Remote UE. And in both cases, it is left to UE implementation whether to use SL-RSRP or SD-RSRP for relay (re)selection trigger evaluation in case of no data transmission. + +- 2> if the UE has a selected NR sidelink U2U Relay UE, and upper layers indicate not to use the currently selected NR sidelink U2U Relay UE; or +- 2> if the UE has a selected NR sidelink U2U Relay UE, and upper layers request the release of the PC5-RRC connection with the current NR sidelink U2U Relay UE; or +- 2> if the UE has a selected NR sidelink U2U Relay UE, and sidelink radio link failure is detected on the PC5-RRC connection with the current NR sidelink U2U Relay UE as specified in clause 5.8.9.3: + +#### 5.8.17.4 Actions related to selection and reselection of NR sidelink U2U Relay UE + +A UE capable of NR sidelink U2U Remote UE operation shall: + +- 1> perform NR sidelink discovery procedure as specified in clause 5.8.13 in order to search for candidate NR sidelink U2U Relay UEs; + - 2> when evaluating the one or more detected NR sidelink U2U Relay UEs, apply layer 3 filtering as specified in 5.5.3.2 across measurements that concern the same U2U Relay UE ID and using the *sd-FilterCoefficientU2U* in *SIB12* (if in *RRC\_IDLE/INACTIVE*), the *sd-FilterCoefficientU2U* in *sl-ConfigDedicatedNR* (if in *RRC\_CONNECTED*) or the preconfigured *sd-FilterCoefficientU2U* as defined in 9.3 (out of coverage), before using the SD-RSRP measurement results; + - 2> consider a candidate NR sidelink U2U Relay UE for which SD-RSRP exceeds *sd-RSRP-ThreshU2U* has met the AS criteria; +- 1> if the UE detects any suitable NR sidelink U2U Relay UE(s): + - 2> consider one of the available suitable NR sidelink U2U Relay UE(s) can be selected; +- 1> else: + - 2> consider no NR sidelink U2U Relay UE to be selected; +- 1> if the UE is performing U2U Relay Communication with integrated Discovery as specified in TS 23.304 [65] and has received Direct Communication Request message(s) from one or multiple NR sidelink U2U Relay UEs: + - 2> when evaluating the NR sidelink U2U Relay UE(s), apply layer 3 filtering as specified in 5.5.3.2 across measurements that concern the same U2U Relay UE ID and using the *sd-FilterCoefficientU2U* in *SIB12* (if in *RRC\_IDLE/INACTIVE*), the *sd-FilterCoefficientU2U* in *sl-ConfigDedicatedNR* (if in *RRC\_CONNECTED*) or the preconfigured *sd-FilterCoefficientU2U* as defined in 9.3 (out of coverage), before using the SD-RSRP measurement results; + - 2> consider a candidate NR sidelink U2U Relay UE for which SL-RSRP exceeds *sd-RSRP-ThreshU2U* has met the AS criteria; + - 2> if the UE detects any suitable NR sidelink U2U Relay UE(s): + +3> consider one of the available suitable NR sidelink U2U Relay UE(s) can be selected; + +2> else: + +3> consider no NR sidelink U2U Relay UE to be selected. + +NOTE: A candidate NR sidelink U2U Relay UE which meets all AS layer criteria defined in 5.8.17.4 and higher layer criteria defined in TS 23.304 [65] can be regarded as suitable NR sidelink U2U Relay UE by the NR sidelink U2U Remote UE. If multiple suitable NR sidelink U2U Relay UEs are available, it is up to Remote UE implementation to choose one NR sidelink U2U Relay UE. The details of the interaction with upper layers are up to UE implementation. + +### 5.8.18 NR sidelink positioning + +#### 5.8.18.1 General + +The purpose of this procedure is to perform NR sidelink positioning as specified in TS 38.305 [73]. + +#### 5.8.18.2 NR sidelink positioning reception + +A UE capable of NR sidelink positioning that is configured by upper layers for reception of SL-PRS: + +1> if the conditions for NR sidelink positioning operation as defined in 5.8.2 are met: + +2> if the frequency used for NR sidelink positioning is included in *sl-FreqInfoToAddModList* in *RRReconfiguration* message or *sl-FreqInfoList* included in *SIB23*: + +3> if the UE is configured with *sl-RxPool* and/or *sl-PRS-RxPool* included in *RRReconfiguration* message with *reconfigurationWithSync* (i.e. handover): + +4> configure lower layers to monitor sidelink control information and the corresponding SL-PRS using the pool(s) of resources indicated by *sl-RxPool* and/or *sl-PRS-RxPool*; + +3> else if the cell chosen for NR sidelink positioning provides *SIB23*: + +4> configure lower layers to monitor sidelink control information and the corresponding SL-PRS using the pool(s) of resources indicated by *sl-RxPool* and/or *sl-PRS-RxPool* in *SIB23*; + +2> else: + +3> configure lower layers to monitor sidelink control information and the corresponding SL-PRS using the pool(s) of resources that were preconfigured by *sl-RxPool* and/or *sl-PRS-RxPool* in *SL-PreconfigurationNR*, as defined in clause 9.3. + +#### 5.8.18.3 NR sidelink positioning transmission + +A UE capable of NR sidelink positioning that is configured by upper layers to transmit SL-PRS shall: + +1> if the conditions for NR sidelink positioning operation as defined in 5.8.2 are met: + +2> if the frequency used for NR sidelink positioning is included in *sl-FreqInfoToAddModList* in *sl-ConfigDedicatedNR* within *RRReconfiguration* message or included in *sl-PosConfigCommonNR* within *SIB23*: + +3> if the UE is in *RR\_CONNECTED* and uses the frequency included in *sl-ConfigDedicatedNR* within *RRReconfiguration* message: + +4> if the UE is configured with *sl-ScheduledConfig*: + +5> if T310 for MCG or T311 is running; and if *sl-PRS-TxPoolExceptional* or *sl-TxPoolExceptional* is included in *sl-FreqInfoList* for the concerned frequency in *SIB23* or included in *sl-ConfigDedicatedNR* in *RRReconfiguration*; or + +5> if T301 is running and the cell on which the UE initiated RRC connection re-establishment provides *SIB23* including *sl-PRS-TxPoolExceptional* or *sl-TxPoolExceptional* for the concerned frequency; or + +- 5> if T304 for MCG is running and the UE is configured with *sl-PRS-TxPoolExceptional* or *sl-TxPoolExceptional* included in *sl-ConfigDedicatedNR* for the concerned frequency in *RRCREconfiguration*: + - 6> configure lower layers to perform the sidelink resource allocation scheme 2 based on random selection using the resource pool indicated by *sl-PRS-TxPoolExceptional* or *sl-TxPoolExceptional* as defined in TS 38.321 [3]; +- 5> else: + - 6> configure lower layers to perform the sidelink resource allocation scheme 1 for NR sidelink positioning; +- 5> if T311 is running, configure the lower layers to release the resources indicated by *rrc-ConfiguredSidelinkGrant* (if any); +- 4> if the UE is configured with *sl-UE-SelectedConfig*: + - 5> if a result of full sensing, if selected and is allowed by *sl-PosAllowedResourceSelectionConfig*, on the resources configured in *sl-PRS-TxPoolSelectedNormal* or by *sl-AllowedResourceSelectionConfig*, on the resources configured in *sl-TxPoolSelectedNormal* for the concerned frequency included in *sl-ConfigDedicatedNR* within *RRCREconfiguration* is not available in accordance with TS 38.214 [19]; + - 6> if *sl-TxPoolExceptional* or *sl-PRS-TxPoolExceptional* for the concerned frequency is included in *RRCREconfiguration*; or + - 6> if the PCell provides SIB25 including *sl-TxPoolExceptional* or *sl-PRS-TxPoolExceptional* in *sl-FreqInfoList* for the concerned frequency: + - 7> configure lower layers to perform the sidelink resource allocation scheme 2 based on random selection using the pool of resources indicated by *sl-TxPoolExceptional* or *sl-PRS-TxPoolExceptional* as defined in TS 38.321 [3]; + - 5> else, if the *sl-PRS-TxPoolSelectedNormal* or *sl-TxPoolSelectedNormal* for the concerned frequency is included in the *sl-ConfigDedicatedNR* within *RRCREconfiguration*: + - 6> configure lower layers to perform the sidelink resource allocation scheme 2 based on resource selection operation according to *sl-PosAllowedResourceSelectionConfig* (as defined in TS 38.321 [3] and TS 38.214 [19]) using the pools of resources indicated by *sl-PRS-TxPoolSelectedNormalNormal* for the concerned frequency, or based on resource selection operation according to *sl-AllowedResourceSelectionConfig* (as defined in TS 38.321 [3] and TS 38.214 [19]) using the pools of resources indicated by *sl-TxPoolSelectedNormal* for the concerned frequency; +- 3> else: + - 4> if the cell chosen for NR sidelink positioning transmission provides *SIB23*: + - 5> if *SIB23* includes *sl-PosTxPoolSelectedNormal* for the concerned frequency, and a result of full sensing, if selected and is allowed by *sl-PosAllowedResourceSelectionConfig*, on the resources configured in the *sl-PRS-TxPoolSelectedNormal* is available in accordance with TS 38.214 [19] or random selection, if allowed by *sl-PosAllowedResourceSelectionConfig*, is selected: + - 6> configure lower layers to perform the sidelink resource allocation scheme 2 based on resource selection operation according to *sl-PosAllowedResourceSelectionConfig* using the pools of resources indicated by *sl-PosTxPoolSelectedNormal* for the concerned frequency as defined in TS 38.321 [3]; + - 5> if *SIB23* includes *sl-TxPoolSelectedNormal* for the concerned frequency, and a result of full sensing, if selected and is allowed by *sl-AllowedResourceSelectionConfig*, on the resources configured in the *sl-TxPoolSelectedNormal* is available in accordance with TS 38.214 [19] or random selection, if allowed by *sl-AllowedResourceSelectionConfig*, is selected: + +- 6> configure lower layers to perform the sidelink resource allocation scheme 2 based on resource selection operation according to *sl-AllowedResourceSelectionConfig* using the pools of resources indicated by *sl-TxPoolSelectedNormal* for the concerned frequency as defined in TS 38.321 [3]; +- 5> else if *SIB23* includes *sl-PRS-TxPoolExceptional* or *sl-TxPoolExceptional* for the concerned frequency: + - 6> from the moment the UE initiates RRC connection establishment or RRC connection resume, until receiving an *RRCReconfiguration* including *sl-ConfigDedicatedNR*, or receiving an *RRCRelease* or an *RRCReject*; or + - 6> if a result of full sensing, if selected and is allowed by *sl-PosAllowedResourceSelectionConfig*, on the resources configured in *sl-PRS-TxPoolSelectedNormal* or if selected and is allowed by *sl-AllowedResourceSelectionConfig*, on the resources configured in *sl-TxPoolSelectedNormal* for the concerned frequency in *SIB23* is not available in accordance with TS 38.214 [19]: + - 7> configure lower layers to perform the sidelink resource allocation scheme 2 based on random selection (as defined in TS 38.321 [3]) using the pool of resources indicated by *sl-PRS-TxPoolExceptional* or *sl-TxPoolExceptional* for the concerned frequency; +- 2> else: + - 3> configure lower layers to perform the sidelink resource allocation scheme 2 based on resource selection operation according to *sl-PosAllowedResourceSelectionConfig* (as defined in TS 38.321 [3] and TS 38.214 [19]) using the pools of resources indicated by *sl-PRS-TxPoolSelectedNormal* in *SL-PosPreconfigurationNR* for the concerned frequency or based on *sl-AllowedResourceSelectionConfig* (as defined in TS 38.321 [3] and TS 38.214 [19]) using the pools of resources indicated by *sl-TxPoolSelectedNormal* in *SidelinkPreconfigNR* for the concerned frequency.. + +NOTE: The same Notes as in clause 5.8.8 are applicable for this clause unless otherwise stated. + +## 5.9 MBS Broadcast + +### 5.9.1 Introduction + +#### 5.9.1.1 General + +UE receiving or interested to receive MBS broadcast service(s) applies MBS broadcast procedures described in this clause as well as the MBS Interest Indication procedure as specified in clause 5.9.4. + +MBS broadcast configuration information, except CFR configuration for MCCH/MTCH, is provided on MCCH logical channel. MCCH carries the *MBSBroadcastConfiguration* message which indicates the MBS broadcast sessions that are provided in the cell as well as the corresponding scheduling related information for these sessions. Optionally, the *MBSBroadcastConfiguration* message may also contain a list of neighbour cells providing the same broadcast MBS service(s) as provided in the current cell. The configuration information required by the UE to receive MCCH is provided in *SIB1* and *SIB20*. Additionally, System Information may provide information related to service continuity of MBS broadcast in *SIB21*. + +#### 5.9.1.2 MCCH scheduling + +The MCCH information (i.e. information transmitted in messages sent over MCCH) is transmitted periodically, using a configurable repetition period and within a configured transmission window. MCCH transmissions (and the associated radio resources and MCS) are indicated via the PDCCH addressed to MCCH-RNTI. PDCCH monitoring occasion(s) for MCCH transmission are determined according to the common search space indicated by *searchspaceMCCH*. If *searchspaceMCCH* is set to zero, PDCCH monitoring occasions for MCCH message reception in the MCCH transmission window are the same as PDCCH monitoring occasions for *SIB1* where the mapping between PDCCH monitoring occasions and SSBs is specified in TS 38.213[13]. If *searchspaceMCCH* is not set to zero, PDCCH monitoring occasions for MCCH message are determined based on search space indicated by *searchspaceMCCH*. PDCCH monitoring occasions for MCCH message which are not overlapping with UL symbols (determined according to *tdd-UL-DL-ConfigurationCommon*) are sequentially numbered from one in the MCCH transmission window. The $[x \times N + K]^{\text{th}}$ PDCCH monitoring occasion for MCCH message in MCCH transmission window corresponds to the $K^{\text{th}}$ transmitted SSB, where $x = 0, 1, \dots, X-1$ , $K = 1, 2, \dots, N$ , $N$ is the number of actual transmitted SSBs determined + +according to *ssb-PositionsInBurst* in *SIB1* and X is equal to CEIL(number of PDCCH monitoring occasions in MCCH transmission window/N). The actual transmitted SSBs are sequentially numbered from one in ascending order of their SSB indexes. The UE assumes that, in the MCCH transmission window, PDCCH for an MCCH message is transmitted in at least one PDCCH monitoring occasion corresponding to each transmitted SSB and thus the selection of SSB for the reception MCCH messages is up to UE implementation. + +#### 5.9.1.3 MCCH information validity and notification of changes + +Change of MCCH information only occurs at specific radio frames, i.e. the concept of a modification period is used. Within a modification period, the same MCCH information may be transmitted a number of times, as defined by its scheduling (which is based on a repetition period). + +When the network changes (some of) the MCCH information, it notifies the UEs about the change starting from the beginning of the MCCH modification period via PDCCH which schedules the MCCH in every repetition in that modification period. + +Upon receiving a change notification, a UE receiving or interested to receive MBS services transmitted using MBS broadcast acquires the new MCCH information starting from the same slot. The UE applies the previously acquired MCCH information until the UE acquires the new MCCH information. The notification is transmitted with a 2-bit bitmap, see TS 38.212 [17] clause 7.3.1.5.1. The MSB in the 2-bit bitmap, when set to '1', indicates the start of new MBS service(s). The LSB in the 2-bit bitmap, when set to '1', indicates modification of MCCH information other than the change caused by start of new MBS service(s), e.g. modification of a configuration of an on-going MBS session(s), MBS session(s) stop or neighbouring cell information modification. + +### 5.9.2 MCCH information acquisition + +#### 5.9.2.1 General + +![Sequence diagram showing MCCH information acquisition. A UE sends a request to the Network, and the Network responds with MBSBroadcastConfiguration.](497d7e14540664a2914557cad79f3791_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Network + Note left of UE: UE requests MCCH information + UE->>Network: Request + Network-->>UE: MBSBroadcastConfiguration + +``` + +Sequence diagram showing MCCH information acquisition. A UE sends a request to the Network, and the Network responds with MBSBroadcastConfiguration. + +Figure 5.9.2.1-1: MCCH information acquisition + +The UE applies the MCCH information acquisition procedure to acquire the MBS broadcast configuration information broadcasted by the network. The procedure applies to MBS capable UEs interested to receive or that are receiving MBS broadcast services that are in RRC\_IDLE, RRC\_INACTIVE or RRC\_CONNECTED with an active BWP with common search space configured by *searchSpaceMCCH*. + +#### 5.9.2.2 Initiation + +A UE shall apply the MCCH information acquisition procedure upon becoming interested to receive MBS broadcast services. A UE interested to receive MBS broadcast services shall apply the MCCH information acquisition procedure upon entering the cell providing *SIB20* (e.g. upon power on, following UE mobility), upon receiving *SIB20* of an SCell via dedicated signalling and upon receiving a notification that the MCCH information has changed due to the start of new MBS service(s). A UE that is receiving data via broadcast MRB shall apply the MCCH information acquisition procedure upon receiving a notification that the MCCH information has changed due to MCCH information modification other than the change caused by the start of new MBS service(s). + +NOTE 1: It is up to UE implementation how to address a possibility of the UE missing an MCCH change notification. + +NOTE 2: It is up to UE implementation to use the cell/tracking area list in the USD to avoid acquiring the MCCH when the UE is outside the MBS service area of the MBS broadcast service. + +Unless explicitly stated otherwise in the procedural specification, the MCCH information acquisition procedure overwrites any stored MCCH information, i.e. delta configuration is not applicable for MCCH information and the UE discontinues using a field if it is absent in MCCH information. + +#### 5.9.2.3 MCCH information acquisition by the UE + +An MBS capable UE interested to receive or receiving an MBS broadcast service shall: + +- 1) if the procedure is triggered by an MCCH information change notification: + - 2) start acquiring the *MBSBroadcastConfiguration* message on MCCH in the concerned cell from the slot in which the change notification was received; +- 1) if the UE enters a cell providing *SIB20*; or +- 1) if the UE receives *sCellSIB20*: + - 2) acquire the *MBSBroadcastConfiguration* message on MCCH in the concerned cell at the next repetition period. + +#### 5.9.2.4 Actions upon reception of the *MBSBroadcastConfiguration* message + +No UE requirements related to the contents of the *MBSBroadcastConfiguration* message apply other than those specified elsewhere e.g. within the corresponding field descriptions. + +### 5.9.3 Broadcast MRB configuration + +#### 5.9.3.1 General + +The broadcast MRB configuration procedure is used by the UE to configure PDCP, RLC, MAC and the physical layer upon starting and/or stopping to receive a broadcast MRB transmitted on MTCH, or upon modification of a configuration of a broadcast MRB received by the UE. The procedure applies to MBS capable UEs that are interested to receive or that are receiving an MBS broadcast service that are in RRC\_IDLE, RRC\_INACTIVE or RRC\_CONNECTED with an active BWP with common search space configured by *searchSpaceMTCH* or *searchSpaceMCCH*. + +NOTE: How to perform a modification of a broadcast MRB which is already configured in the UE is left to UE implementation. + +#### 5.9.3.2 Initiation + +The UE applies the broadcast MRB establishment procedure to start receiving an MBS session of an MBS broadcast service it is interested in. The procedure may be initiated e.g. upon start of the MBS session, upon entering a cell providing an MBS broadcast service the UE is interested in, upon becoming interested in the ongoing MBS broadcast service, upon removal of the UE capability limitations inhibiting reception of the ongoing MBS broadcast service UE is interested in. + +The UE applies the broadcast MRB release procedure to stop receiving a session of an MBS broadcast service. The procedure may be initiated e.g. upon stop of the MBS session, upon leaving the cell broadcasting the MBS service the UE is interested in, upon losing interest in the MBS service, when capability limitations start inhibiting reception of the concerned service. + +#### 5.9.3.3 Broadcast MRB establishment + +Upon a broadcast MRB establishment, the UE shall: + +- 1) establish a PDCP entity and an RLC entity in accordance with *MRB-InfoBroadcast* for this broadcast MRB included in the *MBSBroadcastConfiguration* message and the configuration specified in 9.1.1.7; +- 1) configure the MAC layer in accordance with the *mtch-SchedulingInfo* (if included); +- 1) configure the physical layer in accordance with the *mbs-SessionInfoList*, *searchSpaceMTCH*, and *pdsch-ConfigMTCH*, applicable for the broadcast MRB; +- 1) if an SDAP entity with the received *mbs-SessionId* does not exist: + - 2) establish an SDAP entity as specified in TS 37.324 [24] clause 5.1.1; + - 2) indicate the establishment of the user plane resources for the *mbs-SessionId* to upper layers; + +1> receive DL-SCH on the cell where the *MBSBroadcastConfiguration* message was received for the established broadcast MRB using *g-RNTI* and *mtch-SchedulingInfo* (if included) in this message for this MBS broadcast service. + +#### 5.9.3.4 Broadcast MRB release + +Upon broadcast MRB release for MBS broadcast service, the UE shall: + +- 1> release the PDCP entity, RLC entity as well as the related MAC and physical layer configuration; +- 1> if the SDAP entity associated with the corresponding *mbs-SessionId* has no associated MRB: + - 2> release the SDAP entity, as specified in TS 37.324 [24] clause 5.1.2; + - 2> indicate the release of the user plane resources for the *mbs-SessionId* to upper layers. + +### 5.9.4 MBS Interest Indication + +#### 5.9.4.1 General + +![Sequence diagram showing the MBS Interest Indication procedure. A UE sends an SIB21 acquisition or nonServingCellMII reception message to the Network, and then the Network responds with an MBSInterestIndication message.](a9241101d638c568cd5a84ab7ad39f15_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Network + Note right of UE: SIB21 acquisition or nonServingCellMII reception + UE->>Network: MBSInterestIndication + +``` + +Sequence diagram showing the MBS Interest Indication procedure. A UE sends an SIB21 acquisition or nonServingCellMII reception message to the Network, and then the Network responds with an MBSInterestIndication message. + +Figure 5.9.4.1-1: MBS Interest Indication + +The purpose of this procedure is to inform the network that the UE in RRC\_CONNECTED is receiving or is interested to receive MBS broadcast service(s) and to inform the network about the priority of MBS broadcast versus unicast and multicast MRB reception. MBS Interest Indication can only be sent after AS security activation. + +#### 5.9.4.2 Initiation + +An MBS capable UE in RRC\_CONNECTED may initiate the procedure in several cases including upon successful connection establishment/resume, upon entering or leaving the broadcast service area, upon MBS broadcast session start or stop, upon change of interest, upon change of priority between MBS broadcast reception and unicast/multicast reception, upon change to a PCell providing *SIB21* (i.e. where the *SIB1* scheduling information contains *SIB21*), upon receiving *SIB20* of an SCell via dedicated signalling, upon handover, and upon RRC connection re-establishment, upon change to a PCell providing *nonServingCellMII* in *SIB1*, upon starting or stopping reception of MBS broadcast service on a non-serving cell, upon change of CFR information or subcarrier spacing for MBS broadcast reception on a non-serving cell. If the UE does not have the CFR information and subcarrier spacing for MBS broadcast reception on a non-serving cell at the time it sends the MBS Interest Indication, the UE sends an MBS Interest Indication after it has acquired those information from the non-serving cell. + +Upon initiating the procedure, the UE shall: + +- 1> if *SIB21* is provided by the PCell; or +- 1> if *nonServingCellMII* is provided in *SIB1* by the PCell: + - 2> ensure having a valid version of *SIB21* for the PCell, if present; + - 2> if the UE did not transmit MBS Interest Indication since last entering RRC\_CONNECTED state; or + - 2> if since the last time the UE transmitted an MBS Interest Indication, the UE connected to a PCell, neither providing *SIB21* nor including *nonServingCellMII* in *SIB1*: + - 3> if the set of MBS broadcast frequencies of interest, determined in accordance with 5.9.4.3, is not empty: + +4> set the contents of MBS Interest Indication according to 5.9.4.5 and initiate transmission of the *MBSInterestIndication* message; + +2> else: + +- 3> if the set of MBS broadcast frequencies of interest, determined in accordance with 5.9.4.3, is different from *mbs-FreqList* included in the last transmission of the MBS Interest Indication; or + - 3> if the set of MBS broadcast frequencies of interest for MBS broadcast reception on non-serving cell, determined in accordance with 5.9.4.3, is different from the list of MBS broadcast frequencies of interest for MBS broadcast reception on non-serving cell included in the last transmission of the MBS Interest Indication; or + - 3> if any of the subcarrier spacing and the CFR information for MBS broadcast reception on non-serving cell has changed since the last transmission of the MBS Interest Indication; or + - 3> if the subcarrier spacing and the CFR information for MBS broadcast reception on non-serving cell have been acquired from the non-serving cell which were not reported in the previous MBS Interest Indication; or + - 3> if the prioritisation of reception of all indicated MBS broadcast frequencies compared to reception of any of the established unicast bearers and multicast MRBs has changed since the last transmission of the MBS Interest Indication: +- 4> set the contents of MBS Interest Indication according to 5.9.4.5 and initiate transmission of the *MBSInterestIndication* message; + +NOTE: The UE may send MBS Interest Indication even when it is able to receive the MBS services it is interested in, i.e. to avoid that the network allocates a configuration inhibiting MBS broadcast reception. + +3> else if *SIB20* is provided for the PCell or for the SCell: + +- 4> if since the last time the UE transmitted the MBS Interest Indication, the UE connected to a PCell not providing *SIB20* and the UE was not provided with *SIB20* for an SCell; or + - 4> if the set of MBS broadcast services of interest determined in accordance with 5.9.4.4 is different from *mbs-ServiceList* included in the last transmission of the MBS Interest Indication: +- 5> set the contents of MBS Interest Indication according to 5.9.4.5 and initiate the transmission of *MBSInterestIndication* message. + +#### 5.9.4.3 MBS frequencies of interest determination + +The UE shall: + +1> consider a frequency to be part of the MBS frequencies of interest if the following conditions are met: + +- 2> at least one MBS session the UE is receiving or interested to receive via a broadcast MRB is ongoing or about to start; and + +NOTE 1: The UE may determine whether the session is ongoing from the start and stop time indicated in the User Service Description (USD), see TS 38.300 [2] or TS 23.247 [67]. + +- 2> for at least one of these MBS sessions, *SIB21* acquired from the PCell or a non-serving cell includes mapping between the concerned frequency and one or more MBS FSAIs indicated in the USD for this session, or for at least one of these MBS sessions, the concerned frequency is not included in *SIB21* but is indicated in the USD for this session; and + +NOTE 2: The UE considers a frequency to be part of the MBS frequencies of interest even though NG-RAN may (temporarily) not employ a broadcast MRB for the concerned session, i.e., the UE does not verify if the session is indicated on MCCH. + +- 2> the *supportedBandCombinationList* the UE included in *UE-NR-Capability* contains at least one band combination including the concerned MBS frequency. + +NOTE 3: When evaluating which frequencies the UE is capable of receiving, the UE does not take into account whether they are currently configured as serving frequencies. + +#### 5.9.4.4 MBS services of interest determination + +The UE shall: + +- 1> consider an MBS service to be part of the MBS services of interest if the following conditions are met: + - 2> the UE is receiving or interested to receive this service via a broadcast MRB; and + - 2> the session of this service is ongoing or about to start; and + - 2> one or more MBS FSIs in the USD for this service is included in *SIB21* acquired from the PCell for a frequency belonging to the set of MBS frequencies of interest, determined according to 5.9.4.3 or *SIB21* acquired from the PCell does not provide the frequency mapping for the concerned service but that frequency is included in the USD of this service. + +NOTE: The UE may determine whether the session is ongoing from the start and stop time indicated in the User Service Description (USD), see TS 38.300 [2] or TS 23.247 [67]. + +#### 5.9.4.5 Setting of the contents of MBS Interest Indication + +The UE shall set the contents of the MBS Interest Indication as follows: + +- 1> if the UE has a valid version of *SIB21* for the PCell; and +- 1> if the set of MBS frequencies of interest, determined in accordance with 5.9.4.3, is not empty: + - 2> include *mbs-FreqList* and set it to include the MBS frequencies of interest sorted by decreasing order of interest, using the *absoluteFrequencySSB* for serving frequency, if applicable, and the *ARFCN-ValueNR*(s) as included in *SIB21* or in USD (for neighbouring frequencies); + - 2> include *mbs-Priority* if the UE prioritises reception of all indicated MBS frequencies above reception of any of the unicast bearers and multicast MRBs; + +NOTE 1: If the UE prioritises MBS broadcast reception and unicast/multicast data cannot be supported because of congestion on the MBS carrier(s), NG-RAN may for example initiate release of unicast bearers/multicast MRBs. + +- 2> if *SIB20* is provided for the PCell or for the SCell: + - 3> include *mbs-ServiceList* and set it to indicate the set of MBS services of interest sorted by decreasing order of interest determined in accordance with 5.9.4.4. + +NOTE 2: The *mbs-ServiceList* is not required to be used by the NG-RAN to determine the frequency on which to enable MBS broadcast reception for the UE. + +- 1> if *nonServingCellMII* is included in *SIB1* for the PCell; and +- 1> if the set of MBS frequencies for MBS broadcast reception on non-serving cell, determined in accordance with 5.9.4.3, is not empty: + - 2> include *freqInfoMBS*; + - 2> if the UE has acquired *cfr-InfoMBS* and *subcarrierSpacing* for MBS broadcast reception on the non-serving cell: + - 3> include *cfr-InfoMBS* and *subcarrierSpacing*; + +## 5.10 MBS multicast reception in RRC\_INACTIVE + +### 5.10.1 Introduction + +#### 5.10.1.1 General + +UE configured to receive MBS multicast service(s) in RRC\_INACTIVE that the UE has joined applies MBS multicast procedures described in this clause. + +MBS multicast configuration information is provided in *RRRelease* and on multicast MCCH logical channel. + +When there is temporarily no data for an active multicast session or when the multicast session is deactivated, the network notifies the UE to stop monitoring the corresponding G-RNTI via MBS multicast configuration information. If the UE is notified to stop monitoring the G-RNTI(s) for all the joined multicast sessions, it stops monitoring the Multicast MCCH-RNTI for the cell where it received the notification. + +Multicast MCCH carries the *MBSMulticastConfiguration* message which indicates the MBS multicast sessions that are provided in the cell as well as the corresponding scheduling related information for these sessions. Optionally, the *MBSMulticastConfiguration* message may also contain a list of neighbour cells providing the same MBS multicast service(s) for RRC\_INACTIVE as provided in the current cell. The configuration information required by the UE to receive multicast MCCH is provided in *SIB24*. + +#### 5.10.1.2 Multicast MCCH scheduling + +The multicast MCCH information (i.e. information transmitted in messages sent over multicast MCCH) is transmitted periodically, using a configurable repetition period and within a configured transmission window. MCCH transmissions (and the associated radio resources and MCS) are indicated via the PDCCH addressed to Multicast MCCH-RNTI. PDCCH monitoring occasion(s) for the multicast MCCH transmission are determined according to the common search space indicated by *searchspaceMulticastMCCH*. If *searchspaceMulticastMCCH* is set to zero, PDCCH monitoring occasions for the multicast MCCH message reception in the multicast MCCH transmission window are the same as PDCCH monitoring occasions for *SIB1* where the mapping between PDCCH monitoring occasions and SSBs is specified in TS 38.213 [13]. If *searchspaceMulticastMCCH* is not set to zero, PDCCH monitoring occasions for the multicast MCCH message are determined based on search space indicated by *searchspaceMulticastMCCH*. PDCCH monitoring occasions for the multicast MCCH message which are not overlapping with UL symbols (determined according to *tdd-UL-DL-ConfigurationCommon*) are sequentially numbered from one in the multicast MCCH transmission window. The $[x \times N + K]^{\text{th}}$ PDCCH monitoring occasion for the multicast MCCH message in the multicast MCCH transmission window corresponds to the $K^{\text{th}}$ transmitted SSB, where $x = 0, 1, \dots, X-1$ , $K = 1, 2, \dots, N$ , $N$ is the number of actual transmitted SSBs determined according to *ssb-PositionsInBurst* in *SIB1* and $X$ is equal to $\text{CEIL}(\text{number of PDCCH monitoring occasions in multicast MCCH transmission window}/N)$ . The actual transmitted SSBs are sequentially numbered from one in ascending order of their SSB indexes. The UE assumes that, in the multicast MCCH transmission window, PDCCH for a multicast MCCH message is transmitted in at least one PDCCH monitoring occasion corresponding to each transmitted SSB and thus the selection of SSB for the reception multicast MCCH messages is up to UE implementation. + +#### 5.10.1.3 Multicast MCCH information validity and notification of changes + +Change of multicast MCCH information only occurs at specific radio frames, i.e. the concept of a modification period is used. Within a modification period, the same multicast MCCH information may be transmitted a number of times, as defined by its scheduling (which is based on a repetition period). + +When the network changes (some of) the multicast MCCH information, it notifies the UEs about the change starting from the beginning of the multicast MCCH modification period via PDCCH which schedules the multicast MCCH in every repetition in that modification period. + +Upon receiving a change notification, a UE receiving MBS multicast service(s) in RRC\_INACTIVE acquires the new multicast MCCH information starting from the same slot. The UE applies the previously acquired multicast MCCH information until the UE acquires the new multicast MCCH information. + +### 5.10.2 Multicast MCCH information acquisition + +#### 5.10.2.1 General + +![Sequence diagram showing the Multicast MCCH information acquisition procedure. A UE sends a request to the Network, and the Network responds with the MBSMulticastConfiguration message.](921f8fa0f7ce2c9956f20d33162c13a2_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Network + Note left of UE: Request MCCH information + Network->>UE: MBSMulticastConfiguration + +``` + +Sequence diagram showing the Multicast MCCH information acquisition procedure. A UE sends a request to the Network, and the Network responds with the MBSMulticastConfiguration message. + +Figure 5.10.2.1-1: Multicast MCCH information acquisition + +The UE applies the multicast MCCH information acquisition procedure to acquire the MBS multicast configuration information from the network. The procedure applies to UEs configured to receive MBS multicast services in RRC\_INACTIVE. + +#### 5.10.2.2 Initiation + +If configured to receive MBS multicast services in RRC\_INACTIVE, a UE applies the multicast MCCH information acquisition procedure for PTM configuration update and upon reselection to a new cell providing *SIB24*. A UE that is receiving MBS multicast data in RRC\_INACTIVE shall apply the multicast MCCH information acquisition procedure upon receiving a notification that the multicast MCCH information has changed. + +NOTE: It is up to UE implementation how to address a possibility of the UE missing a multicast MCCH change notification. + +Unless explicitly stated otherwise in the procedural specification, the multicast MCCH information acquisition procedure overwrites any stored multicast MCCH information, i.e. delta configuration is not applicable for multicast MCCH information and the UE discontinues using a field if it is absent in multicast MCCH information. + +#### 5.10.2.3 Multicast MCCH information acquisition by the UE + +A UE configured to receive an MBS multicast service in RRC\_INACTIVE shall: + +- 1> if the procedure is triggered by a multicast MCCH information change notification: + - 2> start acquiring the *MBSMulticastConfiguration* message on multicast MCCH in the concerned cell from the slot in which the change notification was received; +- 1> if the UE moves to a different cell providing *SIB24*; or +- 1> if the UE receives *RRRelease* configuring the UE to receive MBS multicast in RRC\_INACTIVE which doesn't include PTM configuration for at least one multicast session for which the UE is not indicated to stop monitoring the G-RNTI: + - 2> acquire the *MBSMulticastConfiguration* message on multicast MCCH in the concerned cell at the next repetition period. + +#### 5.10.2.4 Actions upon reception of the *MBSMulticastConfiguration* message + +No UE requirements related to the contents of the *MBSMulticastConfiguration* message apply other than those specified elsewhere, e.g., within the corresponding field descriptions. + +### 5.10.3 MRB configuration + +#### 5.10.3.1 General + +The multicast MRB configuration procedure is used by the UE in RRC\_INACTIVE state to configure PDCP, RLC, MAC entities and the physical layer upon PTM configuration update and moving to a cell providing *SIB24*. The UE + +may perform multicast MRB modification or release/establishment when PTM configuration is updated via MCCH or when it moves to a cell where the PDCP COUNT of the corresponding multicast MRB is not synchronized within the RNA. The UE may perform multicast MRB modification when it moves to a cell where the PDCP COUNT of the corresponding multicast MRB is synchronized within the RNA. The UE resets MAC upon cell-reselection. + +NOTE: How to perform modification of a multicast MRB which is already configured in the UE is left to UE implementation. + +Upon moving to a cell where the PDCP COUNT of a multicast MRB is not synchronized, an indication is sent to the lower layer to inform the PDCP COUNT non-synchronization of the corresponding multicast MRB. Upon transition from RRC\_CONNECTED to RRC\_INACTIVE in the same cell, the UE can continue using the multicast MRBs used in RRC\_CONNECTED. + +#### 5.10.3.2 Multicast MRB establishment + +Upon establishment of a multicast MRB, the UE shall: + +- 1> establish a PDCP entity and an RLC entity in accordance with *MRB-InfoBroadcast* for this multicast MRB included in the *MBSMulticastConfiguration* message and the configuration specified in 9.1.1.7; +- 1> configure the MAC layer in accordance with the *mtch-SchedulingInfo* (if included); +- 1> configure the physical layer in accordance with the *mbs-SessionInfoList*, *searchSpaceMulticastMTCH*, and *pdsch-ConfigMTCH*, applicable for the multicast MRB; +- 1> if an SDAP entity with the received *mbs-SessionId* does not exist: + - 2> establish an SDAP entity as specified in TS 37.324 [24] clause 5.1.1; + - 2> indicate the establishment of the user plane resources for the *mbs-SessionId* to upper layers; +- 1> receive DL-SCH on the cell where the *MBSMulticastConfiguration* message was received for the established multicast MRB using *g-RNTI* and *mtch-SchedulingInfo* (if included) in this message for this MBS multicast service. + +#### 5.10.3.3 Multicast MRB release + +Upon release of a multicast MRB, the UE shall: + +- 1> release the PDCP entity, RLC entity as well as the related MAC and physical layer configuration; +- 1> if the SDAP entity associated with the corresponding *mbs-SessionId* has no associated MRB: + - 2> release the SDAP entity, as specified in TS 37.324 [24] clause 5.1.2; + - 2> indicate the release of the user plane resources for the *mbs-SessionId* to upper layers. + +# 6 Protocol data units, formats and parameters (ASN.1) + +## 6.1 General + +### 6.1.1 Introduction + +The contents of each RRC message is specified in clause 6.2 using ASN.1 to specify the message syntax and using tables when needed to provide further detailed information about the fields specified in the message syntax. The syntax of the information elements that are defined as stand-alone abstract types is further specified in a similar manner in clause 6.3. + +Usage of the text "Network always configures the UE with a value for this field" in the field description indicates that the network has to provide a value for the field in this or in a previous message based on delta configuration (for an optional field with Need M). It does not imply a mandatory presence of the field. + +### 6.1.2 Need codes and conditions for optional fields + +The need for fields to be present in a message or an abstract type, i.e., the ASN.1 fields that are specified as OPTIONAL in the abstract notation (ASN.1), is specified by means of comment text tags attached to the OPTIONAL statement in the abstract syntax. All comment text tags are available for use in the downlink direction for RRC message and in the sidelink for PC5 RRC message. The meaning of each tag is specified in table 6.1.2-1. + +If conditions are used, a conditional presence table is provided for the message or information element specifying the need of the field for each condition case. The table also specifies whether UE maintains or releases the value in case the field is absent. The conditions clarify what the UE may expect regarding the setting of the message by the network for the RRC message or by the peer UE in the sidelink RRC message. Violation of conditions is regarded as invalid network behaviour when transmitting downlink RRC message or invalid UE behavior when transmitting PC5 RRC message, which the UE is not required to cope with. Hence the general error handling defined in 10.4 does not apply in case a field is absent although it is mandatory according to the CondC or CondM condition. + +For guidelines on the use of need codes and conditions, see Annex A.6 and A.7. + +Table 6.1.2-1: Meaning of abbreviations used to specify the need for fields to be present + +| Abbreviation | Meaning | +|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Cond conditionTag | Conditionally present
Presence of the field is specified in a tabular form following the ASN.1 segment. | +| CondC conditionTag | Configuration condition
Presence of the field is conditional to other configuration settings. | +| CondM conditionTag | Message condition
Presence of the field is conditional to other fields included in the message. | +| Need S | Specified
Used for (configuration) fields, whose field description or procedure specifies the UE behavior performed upon receiving a message with the field absent (and not if field description or procedure specifies the UE behavior when field is not configured). | +| Need M | Maintain
Used for (configuration) fields that are stored by the UE i.e. not one-shot. Upon receiving a message with the field absent, the UE maintains the current value. | +| Need N | No action (one-shot configuration that is not maintained)
Used for (configuration) fields that are not stored and whose presence causes a one-time action by the UE. Upon receiving message with the field absent, the UE takes no action. | +| Need R | Release
Used for (configuration) fields that are stored by the UE i.e. not one-shot. Upon receiving a message with the field absent, the UE releases the current value. | + +NOTE: In this version of the specification, the condition tags CondC and CondM are not used. + +Any field with Need M or Need N in system information shall be interpreted as Need R. + +The need code used within a CondX definition only applies for the case (part of the condition) where it is defined: A condition may have different need codes for different parts of the condition. In particular, the CondX definition may contain the following "otherwise the field is absent" parts: + +- "Otherwise, the field is absent": The field is not relevant or should not be configured when this part of the condition applies. In particular, the UE behaviour is not defined when the field is configured via another part of the condition and is reconfigured to this part of the condition. A need code is not provided when the transition from another part of the condition to this part of the condition is not supported, when the field clearly is a one-shot or there is no difference whether UE maintains or releases the value (e.g., in case the field is mandatory present according to the other part of the condition). +- "Otherwise, the field is absent, Need R": The field is released if absent when this part of the condition applies. This handles UE behaviour in case the field is configured via another part of the condition and this part of the condition applies (which means that network when transmitting downlink RRC message or peer UE transmitting PC5 RRC message can assume UE releases the field if this part of the condition is valid). +- "Otherwise, the field is absent, Need M": The UE retains the field if it was already configured when this part of the condition applies. This means the network when transmitting downlink RRC message or the peer UE when transmitting PC5 RRC message cannot release the field, but UE retains the previously configured value. + +Use of different Need codes in different parts of a condition should be avoided. + +For downlink RRC message and sidelink PC5 RRC messages, the need codes, conditions and ASN.1 defaults specified for a particular (child) field only apply in case the (parent) field including the particular field is present. Thus, if the parent is absent the UE shall not release the field unless the absence of the parent field implies that. + +For (parent) fields without need codes in downlink RRC messages or sidelink PC5 RRC message, if the parent field is absent, UE shall follow the need codes of the child fields. Thus, if parent field is absent, the need code of each child field is followed (i.e. Need R child fields are released, Need M child fields are not modified and the actions for Need S child fields depend on the specified conditions of each field). Examples of (parent) fields in downlink RRC messages and sidelink PC5 RRC message without need codes where this rule applies are: + +- *nonCriticalExtension* fields at the end of a message using empty *SEQUENCE* extension mechanism, +- groups of non-critical extensions using double brackets (referred to as extension groups), and +- non-critical extensions at the end of a message or at the end of a structure, contained in a *BIT STRING* or *OCTET STRING* (referred to as parent extension fields). + +The handling of need codes as specified in the previous is illustrated by means of an example, as shown in the following ASN.1. + +``` +-- /example/ ASN1START + +RRMessage-IEs := SEQUENCE { + field1 InformationElement1 OPTIONAL, -- Need M + field2 InformationElement2 OPTIONAL, -- Need R + nonCriticalExtension RRMessage-v1570-IEs OPTIONAL +} + +RRMessage-1570-IEs := SEQUENCE { + field3 InformationElement3 OPTIONAL, -- Need M + nonCriticalExtension RRMessage-v1640-IEs OPTIONAL +} + +RRMessage-v1640-IEs := SEQUENCE { + field4 InformationElement4 OPTIONAL, -- Need R + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +InformationElement1 := SEQUENCE { + field10 InformationElement10 OPTIONAL, -- Need N + field11 InformationElement11 OPTIONAL, -- Need M + field12 InformationElement12 OPTIONAL, -- Need R + ... + [[ + field13 InformationElement13 OPTIONAL, -- Need R + field14 InformationElement14 OPTIONAL, -- Need M + ]] +} + +InformationElement2 := SEQUENCE { + field21 InformationElement11 OPTIONAL, -- Need M + ... +} + +-- ASN1STOP +``` + +The handling of need codes as specified in the previous implies that: + +- if *field1* in *RRMessage-IEs* is absent, UE does not modify or take action on any child fields configured within *field1* (regardless of their need codes); +- if *field2* in *RRMessage-IEs* is absent, UE releases the *field2* (and also its child field *field21*); +- if *field1* or *field2* in *RRMessage-IEs* is present, UE retains or releases their child fields according to the child field presence conditions; +- if *field1* in *RRMessage-IEs* is present but the extension group containing *field13* and *field14* is absent, the UE releases *field13* but does not modify *field14*; +- if *nonCriticalExtension* defined by IE *RRMessage-v1570-IEs* is absent, the UE does not modify *field3* but releases *field4*; + +### 6.1.3 General rules + +In the ASN.1 of this specification, the first bit of a bit string refers to the leftmost bit, unless stated otherwise. + +Upon reception of a list not using *ToAddModList* and *ToReleaseList* structure, the UE shall delete all entries of the list currently in the UE configuration before applying the received list and shall consider each entry as newly created. This applies also to lists whose size is extended (i.e. with a second list structure in the ASN.1 comprising additional entries), unless otherwise specified. This implies that Need M should not be used for fields in the entries of these lists; if used, UE will handle such fields equivalent to a Need R. + +## 6.2 RRC messages + +### 6.2.1 General message structure + +#### – *NR-RRC-Definitions* + +This ASN.1 segment is the start of the NR RRC PDU definitions. + +``` +-- ASN1START +-- TAG-NR-RRC-DEFINITIONS-START + +NR-RRC-Definitions DEFINITIONS AUTOMATIC TAGS ::= +BEGIN + +-- TAG-NR-RRC-DEFINITIONS-STOP +-- ASN1STOP +``` + +#### – *BCCH-BCH-Message* + +The *BCCH-BCH-Message* class is the set of RRC messages that may be sent from the network to the UE via BCH on the BCCH logical channel. + +``` +-- ASN1START +-- TAG-BCCH-BCH-MESSAGE-START +``` + +**Error: Reference source not found 135 Error: Reference source not found** + +``` +BCCH-BCH-Message ::= SEQUENCE { + message BCCH-BCH-MessageType +} + +BCCH-BCH-MessageType ::= CHOICE { + mib MIB, + messageClassExtension SEQUENCE {} +} + +-- TAG-BCCH-BCH-MESSAGE-STOP +-- ASN1STOP +``` + +#### – *BCCH-DL-SCH-Message* + +The *BCCH-DL-SCH-Message* class is the set of RRC messages that may be sent from the network to the UE via DL-SCH on the BCCH logical channel. + +``` +-- ASN1START +-- TAG-BCCH-DL-SCH-MESSAGE-START + +BCCH-DL-SCH-Message ::= SEQUENCE { + message BCCH-DL-SCH-MessageType +} + +BCCH-DL-SCH-MessageType ::= CHOICE { + c1 CHOICE { + systemInformation SystemInformation, + systemInformationBlockType1 SIB1 + }, + messageClassExtension SEQUENCE {} +} + +-- TAG-BCCH-DL-SCH-MESSAGE-STOP +-- ASN1STOP +``` + +#### – *DL-CCCH-Message* + +The *DL-CCCH-Message* class is the set of RRC messages that may be sent from the Network to the UE on the downlink CCCH logical channel. + +``` +-- ASN1START +-- TAG-DL-CCCH-MESSAGE-START + +DL-CCCH-Message ::= SEQUENCE { + message DL-CCCH-MessageType +} + +DL-CCCH-MessageType ::= CHOICE { + c1 CHOICE { +``` + +Error: Reference source not found 136 Error: Reference source not found + +``` + rrcReject RRCReject, + rrcSetup RRCSetup, + spare2 NULL, + spare1 NULL + }, + messageClassExtension SEQUENCE {} +} + +-- TAG-DL-CCCH-MESSAGE-STOP +-- ASN1STOP +``` + +#### — *DL-DCCH-Message* + +The *DL-DCCH-Message* class is the set of RRC messages that may be sent from the network to the UE on the downlink DCCH logical channel. + +``` +-- ASN1START +-- TAG-DL-DCCH-MESSAGE-START + +DL-DCCH-Message ::= SEQUENCE { + message DL-DCCH-MessageType +} + +DL-DCCH-MessageType ::= CHOICE { + c1 CHOICE { + rrcReconfiguration RRCReconfiguration, + rrcResume RRCResume, + rrcRelease RRCRelease, + rrcReestablishment RRCReestablishment, + securityModeCommand SecurityModeCommand, + dlInformationTransfer DLInformationTransfer, + ueCapabilityEnquiry UECapabilityEnquiry, + counterCheck CounterCheck, + mobilityFromNRCommand MobilityFromNRCommand, + dlDedicatedMessageSegment-r16 DL-DedicatedMessageSegment-r16, + ueInformationRequest-r16 UEInformationRequest-r16, + dlInformationTransferMRDC-r16 DLInformationTransferMRDC-r16, + loggedMeasurementConfiguration-r16 LoggedMeasurementConfiguration-r16, + spare3 NULL, spare2 NULL, spare1 NULL + }, + messageClassExtension SEQUENCE {} +} + +-- TAG-DL-DCCH-MESSAGE-STOP +-- ASN1STOP +``` + +#### — *MCCH-Message* + +The *MCCH-Message* class is the set of RRC messages that may be sent from the network to the UE on the MCCH logical channel. + +Error: Reference source not found 137 Error: Reference source not found + +``` +-- ASN1START +-- TAG-MCCH-MESSAGE-START + +MCCH-Message-r17 ::= SEQUENCE { + message MCCH-MessageType-r17 +} + +MCCH-MessageType-r17 ::= CHOICE { + c1 CHOICE { + mbsBroadcastConfiguration-r17 MBSBroadcastConfiguration-r17, + spare1 NULL + }, + messageClassExtension SEQUENCE {} +} + +-- TAG-MCCH-MESSAGE-STOP +-- ASN1STOP +``` + +#### – *MulticastMCCH-Message* + +The *MulticastMCCH-Message* class is the set of RRC messages that may be sent from the network to the UE on the Multicast MCCH logical channel. + +``` +-- ASN1START +-- TAG-MULTICASTMCCH-MESSAGE-START + +MulticastMCCH-Message-r18 ::= SEQUENCE { + message MulticastMCCH-MessageType-r18 +} + +MulticastMCCH-MessageType-r18 ::= CHOICE { + c1 CHOICE { + mbsMulticastConfiguration-r18 MBSMulticastConfiguration-r18, + spare1 NULL + }, + messageClassExtension SEQUENCE {} +} + +-- TAG-MULTICASTMCCH-MESSAGE-STOP +-- ASN1STOP +``` + +#### – *PCCH-Message* + +The *PCCH-Message* class is the set of RRC messages that may be sent from the Network to the UE on the PCCH logical channel. + +``` +-- ASN1START +-- TAG-PCCH-PCH-MESSAGE-START + +PCCH-Message ::= SEQUENCE { +``` + +Error: Reference source not found 138 Error: Reference source not found + +``` + message PCCH-MessageType +} + +PCCH-MessageType ::= CHOICE { + c1 CHOICE { + paging Paging, + spare1 NULL + }, + messageClassExtension SEQUENCE {} +} + +-- TAG-PCCH-PCH-MESSAGE-STOP +-- ASN1STOP +``` + +#### — *UL-CCCH-Message* + +The *UL-CCCH-Message* class is the set of 48-bits RRC messages that may be sent from the UE to the Network on the uplink CCCH logical channel. + +``` +-- ASN1START +-- TAG-UL-CCCH-MESSAGE-START + +UL-CCCH-Message ::= SEQUENCE { + message UL-CCCH-MessageType +} + +UL-CCCH-MessageType ::= CHOICE { + c1 CHOICE { + rrcSetupRequest RRCSsetupRequest, + rrcResumeRequest RRCResumeRequest, + rrcReestablishmentRequest RRCReestablishmentRequest, + rrcSystemInfoRequest RRCSsystemInfoRequest + }, + messageClassExtension SEQUENCE {} +} + +-- TAG-UL-CCCH-MESSAGE-STOP +-- ASN1STOP +``` + +#### — *UL-CCCH1-Message* + +The *UL-CCCH1-Message* class is the set of 64-bits RRC messages that may be sent from the UE to the Network on the uplink CCCH1 logical channel. + +``` +-- ASN1START +-- TAG-UL-CCCH1-MESSAGE-START + +UL-CCCH1-Message ::= SEQUENCE { +``` + +``` + + message UL-CCCH1-MessageType +} + +UL-CCCH1-MessageType ::= CHOICE { + c1 CHOICE { + rrcResumeRequest1 RRCResumeRequest1, + spare3 NULL, + spare2 NULL, + spare1 NULL + + }, + messageClassExtension SEQUENCE {} +} + +-- TAG-UL-CCCH1-MESSAGE-STOP +-- ASN1STOP + +``` + +#### UL-DCCH-Message + +The *UL-DCCH-Message* class is the set of RRC messages that may be sent from the UE to the network on the uplink DCCH logical channel. + +``` + +-- ASN1START +-- TAG-UL-DCCH-MESSAGE-START + +UL-DCCH-Message ::= SEQUENCE { + message UL-DCCH-MessageType +} + +UL-DCCH-MessageType ::= CHOICE { + c1 CHOICE { + measurementReport MeasurementReport, + rrcReconfigurationComplete RRCReconfigurationComplete, + rrcSetupComplete RRCSetupComplete, + rrcReestablishmentComplete RRCReestablishmentComplete, + rrcResumeComplete RRCResumeComplete, + securityModeComplete SecurityModeComplete, + securityModeFailure SecurityModeFailure, + ulInformationTransfer ULInformationTransfer, + locationMeasurementIndication LocationMeasurementIndication, + ueCapabilityInformation UECapabilityInformation, + counterCheckResponse CounterCheckResponse, + ueAssistanceInformation UEAssistanceInformation, + failureInformation FailureInformation, + ulInformationTransferMRDC ULInformationTransferMRDC, + scgFailureInformation SCGFailureInformation, + scgFailureInformationEUTRA SCGFailureInformationEUTRA + }, + messageClassExtension CHOICE { + c2 CHOICE { + ulDedicatedMessageSegment-r16 ULDedicatedMessageSegment-r16, + } + } +} + +``` + +**Error: Reference source not found 140 Error: Reference source not found** + +``` + dedicatedSIBRequest-r16 DedicatedSIBRequest-r16, + mcgFailureInformation-r16 MCGFailureInformation-r16, + ueInformationResponse-r16 UEInformationResponse-r16, + sidelinkUEInformationNR-r16 SidelinkUEInformationNR-r16, + ulInformationTransferIRAT-r16 ULInformationTransferIRAT-r16, + iabOtherInformation-r16 IABOtherInformation-r16, + mbsInterestIndication-r17 MBSInterestIndication-r17, + uePositioningAssistanceInfo-r17 UEPositioningAssistanceInfo-r17, + measurementReportAppLayer-r17 MeasurementReportAppLayer-r17, + indirectPathFailureInformation-r18 IndirectPathFailureInformation-r18, spare5 NULL, spare4 NULL, spare3 NULL, spare2 NULL, spare1 NULL + }, + messageClassExtensionFuture-r16 SEQUENCE {} +} + +-- TAG-UL-DCCH-MESSAGE-STOP +-- ASN1STOP +``` + +### 6.2.2 Message definitions + +#### – CounterCheck + +The *CounterCheck* message is used by the network to indicate the current COUNT MSB values associated to each DRB and to request the UE to compare these to its COUNT MSB values and to report the comparison results to the network. + +Signalling radio bearer: SRB1 + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: Network to UE + +#### CounterCheck message + +``` +-- ASN1START +-- TAG-COUNTERCHECK-START + +CounterCheck ::= SEQUENCE { + rrc-TransactionIdentifier RRC-TransactionIdentifier, + criticalExtensions CHOICE { + counterCheck CounterCheck-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +CounterCheck-IEs ::= SEQUENCE { + drb-CountMSB-InfoList DRB-CountMSB-InfoList, + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +DRB-CountMSB-InfoList ::= SEQUENCE (SIZE (1..maxDRB)) OF DRB-CountMSB-Info + +DRB-CountMSB-Info ::= SEQUENCE { + drb-Identity DRB-Identity, + countMSB-Uplink INTEGER(0..33554431), + countMSB-Downlink INTEGER(0..33554431) +} + +-- TAG-COUNTERCHECK-STOP +-- ASN1STOP +``` + +| CounterCheck-IEs field descriptions | +|-------------------------------------------------------------------------------------| +| drb-CountMSB-InfoList
Indicates the MSBs of the COUNT values of the DRBs. | + +| DRB-CountMSB-Info field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------| +| countMSB-Downlink
Indicates the value of 25 MSBs from RX_NEXT – 1 (specified in TS 38.323 [5]) associated to this DRB. | +| countMSB-Uplink
Indicates the value of 25 MSBs from TX_NEXT – 1 (specified in TS 38.323 [5]) associated to this DRB. | + +#### – CounterCheckResponse + +The *CounterCheckResponse* message is used by the UE to respond to a *CounterCheck* message. + +Signalling radio bearer: SRB1 + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: UE to Network + +#### **CounterCheckResponse message** + +``` +-- ASN1START +-- TAG-COUNTERCHECKRESPONSE-START + +CounterCheckResponse ::= SEQUENCE { + rrc-TransactionIdentifier RRC-TransactionIdentifier, + criticalExtensions CHOICE { + counterCheckResponse CounterCheckResponse-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +CounterCheckResponse-IEs ::= SEQUENCE { + drb-CountInfoList DRB-CountInfoList, + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +DRB-CountInfoList ::= SEQUENCE (SIZE (0..maxDRB)) OF DRB-CountInfo + +DRB-CountInfo ::= SEQUENCE { +``` + +``` + + drb-Identity DRB-Identity, + count-Uplink INTEGER(0..4294967295), + count-Downlink INTEGER(0..4294967295) +} + +-- TAG-COUNTERCHECKRESPONSE-STOP +-- ASN1STOP + +``` + +#### CounterCheckResponse-IEs field descriptions + +##### **drb-CountInfoList** + +Indicates the COUNT values of the DRBs. + +##### DRB-CountInfo field descriptions + +##### **count-Downlink** + +Indicates the value of RX\_NEXT – 1 (specified in TS 38.323 [5]) associated to this DRB. + +##### **count-Uplink** + +Indicates the value of TX\_NEXT – 1 (specified in TS 38.323 [5]) associated to this DRB. + +##### – **DedicatedSIBRequest** + +The *DedicatedSIBRequest* message is used to request SIB(s) required by the UE in RRC\_CONNECTED as specified in clause 5.2.2.3.5. + +Signalling radio bearer: SRB1 + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: UE to Network + +##### **DedicatedSIBRequest message** + +``` + +-- ASN1START +-- TAG-DEDICATEDSIBREQUEST-START + +DedicatedSIBRequest-r16 ::= SEQUENCE { + criticalExtensions CHOICE { + dedicatedSIBRequest-r16 DedicatedSIBRequest-r16-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +DedicatedSIBRequest-r16-IEs ::= SEQUENCE { + +``` + +``` + +onDemandSIB-RequestList-r16 SEQUENCE { + requestedSIB-List-r16 SEQUENCE (SIZE (1..maxOnDemandSIB-r16)) OF SIB-ReqInfo-r16 OPTIONAL, + requestedPosSIB-List-r16 SEQUENCE (SIZE (1..maxOnDemandPosSIB-r16)) OF PosSIB-ReqInfo-r16 OPTIONAL +} OPTIONAL, +lateNonCriticalExtension OCTET STRING OPTIONAL, +nonCriticalExtension SEQUENCE {} OPTIONAL +} + +SIB-ReqInfo-r16 ::= ENUMERATED { sib12, sib13, sib14, sib20-v1700, sib21-v1700, spare3, spare2, spare1 } + +PosSIB-ReqInfo-r16 ::= SEQUENCE { + gnss-id-r16 GNSS-ID-r16 OPTIONAL, + sbas-id-r16 SBAS-ID-r16 OPTIONAL, + posSibType-r16 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, posSibType3-1, posSibType4-1, + posSibType5-1, posSibType6-1, posSibType6-2, posSibType6-3, ..., posSibType1-9-v1710, + posSibType1-10-v1710, posSibType2-24-v1710, posSibType2-25-v1710, + posSibType6-4-v1710, posSibType6-5-v1710, posSibType6-6-v1710, posSibType2-17a-v1770, + posSibType2-18a-v1770, posSibType2-20a-v1770, posSibType1-11-v1800, posSibType1-12-v1800, + posSibType2-26-v1800, posSibType2-27-v1800 } +} + +-- TAG-DEDICATEDSIBREQUEST-STOP +-- ASN1STOP + +``` + +##### DedicatedSIBRequest field descriptions + +| | | +|-----------------------------|----------------------------------------------------------------------| +| requestedSIB-List | Contains a list of SIB(s) the UE requests while in RRC_CONNECTED. | +| requestedPosSIB-List | Contains a list of posSIB(s) the UE requests while in RRC_CONNECTED. | + +##### PosSIB-ReqInfo field descriptions + +| | | +|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| gnss-id | The presence of this field indicates that the request positioning SIB type is for a specific GNSS. Indicates a specific GNSS (see also TS 37.355 [49]) | +| sbas-id | The presence of this field indicates that the request positioning SIB type is for a specific SBAS. Indicates a specific SBAS (see also TS 37.355 [49]). If the UE includes this field it shall set gnss-id to sbas . | + +##### DL *DedicatedMessageSegment* + +The *DL DedicatedMessageSegment* message is used to transfer one segment of the *RR CResume* or *RR CReconfiguration* messages. + +Signalling radio bearer: SRB1 + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: Network to UE + +##### *DL DedicatedMessageSegment* message + +``` +-- ASN1START +-- TAG-DLDEDICATEDMESSAGESEGMENT-START + +DL DedicatedMessageSegment-r16 ::= SEQUENCE { + criticalExtensions CHOICE { + dlDedicatedMessageSegment-r16 DL DedicatedMessageSegment-r16-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +DL DedicatedMessageSegment-r16-IEs ::= SEQUENCE { + segmentNumber-r16 INTEGER(0..4), + rrc-MessageSegmentContainer-r16 OCTET STRING, + rrc-MessageSegmentType-r16 ENUMERATED {notLastSegment, lastSegment}, + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +-- TAG-DLDEDICATEDMESSAGESEGMENT-STOP +-- ASN1STOP +``` + +##### *DL DedicatedMessageSegment* field descriptions + +| | | +|-------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| segmentNumber | Identifies the sequence number of a segment within the encoded DL DCCH message. The network transmits the segments with continuously increasing segmentNumber order so that the UE's RRC layer may expect to obtain them from lower layers in the correct order. Hence, the UE is not required to perform segment re-ordering on RRC level. | +| rrc-MessageSegmentContainer | Includes a segment of the encoded DL DCCH message. The size of the included segment in this container should be small enough so the resulting encoded RRC message PDU is less than or equal to the PDCP SDU size limit. | +| rrc-MessageSegmentType | Indicates whether the included DL DCCH message segment is the last segment of the message or not. | + +##### DLInformationTransfer + +The *DLInformationTransfer* message is used for the downlink transfer of NAS dedicated information, timing information for the 5G internal system clock, or IAB-DU specific F1-C related information. + +Signalling radio bearer: SRB2 or SRB1 (only if SRB2 not established yet). If SRB2 is suspended, the network does not send this message until SRB2 is resumed. If only *dedicatedInfoFlc* is included, SRB2 is used. + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: Network to UE + +##### DLInformationTransfer message + +``` +-- ASN1START +-- TAG-DLINFORMATIONTRANSFER-START + +DLInformationTransfer ::= SEQUENCE { + rrc-TransactionIdentifier RRC-TransactionIdentifier, + criticalExtensions CHOICE { + dlInformationTransfer DLInformationTransfer-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +DLInformationTransfer-IEs ::= SEQUENCE { + dedicatedNAS-Message DedicatedNAS-Message OPTIONAL, -- Need N + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension DLInformationTransfer-v1610-IEs OPTIONAL +} + +DLInformationTransfer-v1610-IEs ::= SEQUENCE { + referenceTimeInfo-r16 ReferenceTimeInfo-r16 OPTIONAL, -- Need N + nonCriticalExtension DLInformationTransfer-v1700-IEs OPTIONAL +} + +DLInformationTransfer-v1700-IEs ::= SEQUENCE { + dedicatedInfoFlc-r17 DedicatedInfoFlc-r17 OPTIONAL, -- Need N + rxTxTimeDiff-gNB-r17 RxTxTimeDiff-r17 OPTIONAL, -- Need N + ta-PDC-r17 ENUMERATED {activate, deactivate} OPTIONAL, -- Need N + sib9Fallback-r17 ENUMERATED {true} OPTIONAL, -- Need N + nonCriticalExtension DLInformationTransfer-v1800-IEs OPTIONAL +} + +DLInformationTransfer-v1800-IEs ::= SEQUENCE { + eventID-TSS-r18 INTEGER (0..63) OPTIONAL, -- Cond clockQualityDetailsLevel +} +``` + +``` + +clockQualityDetailsLevel-r18 CHOICE { + clockQualityMetrics-r18 ClockQualityMetrics-r18, + clockQualityAcceptanceStatus-r18 ENUMERATED {acceptable, notAcceptable} +} +nonCriticalExtension SEQUENCE { + OPTIONAL, -- Need N + OPTIONAL +} + +-- TAG-DLINFORMATIONTRANSFER-STOP +-- ASN1STOP + +``` + +| DLInformationTransfer field descriptions | | +|-------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| clockQualityDetailsLevel | This field indicates the clock quality reporting control information as defined in TS 23.501 [32]. | +| eventID-TSS | This field indicates the status of the 5G access stratum time distribution parameter Clock Quality Reporting Control Information as defined in TS 23.501 [32]. | +| rxTxTimeDiff-gNB | Indicates the Rx-Tx time difference measurement at the gNB (see clause 5.2.3, TS 38.215 [9]). Upon receiving this field, the UE calculates the propagation delay based on the RTT-based PDC mechanism method as described in TS 38.300 [2]. The network does not configure this field, if the UE is configured with ta-PDC with value activate . | +| sib9Fallback | Indicates that the UE fallbacks to receive referenceTimeInfo in SIB9. | +| ta-PDC | Indicates whether the UE-side TA-based propagation delay compensation (PDC) is activated or de-activated. The network does not configure this field with activate , if the field rxTxTimeDiff-gNB is configured. | + +| Conditional Presence | Explanation | +|---------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------| +| clockQualityDetailsLevel | If clockQualityDetailsLevel is present, eventID-TSS is mandatory present. Otherwise, the field is optionally present, Need M. | + +##### – DLInformationTransferMRDC + +The *DLInformationTransferMRDC* message is used for the downlink transfer of RRC messages during fast MCG link recovery. + +Signalling radio bearer: SRB3 + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: Network to UE + +##### **DLInformationTransferMRDC message** + +``` +-- ASN1START +``` + +``` + +-- TAG-DLINFORMATIONTRANSFERMRDC-START + +DLInformationTransferMRDC-r16 ::= SEQUENCE { + criticalExtensions CHOICE { + c1 CHOICE { + dlInformationTransferMRDC-r16 DLInformationTransferMRDC-r16-IEs, + spare3 NULL, spare2 NULL, spare1 NULL + }, + criticalExtensionsFuture SEQUENCE {} + } +} + +DLInformationTransferMRDC-r16-IEs ::= SEQUENCE { + dl-DCCH-MessageNR-r16 OCTET STRING OPTIONAL, -- Need N + dl-DCCH-MessageEUTRA-r16 OCTET STRING OPTIONAL, -- Need N + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +-- TAG-DLINFORMATIONTRANSFERMRDC-STOP +-- ASN1STOP + +``` + +##### DLInformationTransferMRDC field descriptions + +##### **dl-DCCH-MessageNR** + +Includes the *DL-DCCH-Message*. In this version of the specification, the field is only used to transfer the NR *RRReconfiguration*, *RRRelease*, and *MobilityFromNRCommand* messages. + +##### **dl-DCCH-MessageEUTRA** + +Includes the *DL-DCCH-Message*. In this version of the specification, the field is only used to transfer the E-UTRA *RRConnectionReconfiguration*, *RRConnectionRelease*, and *MobilityFromEUTRACommand* messages as specified in TS 36.331 [10]. + +##### FailureInformation + +The *FailureInformation* message is used to inform the network about a failure detected by the UE. + +Signalling radio bearer: SRB1 or SRB3 + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: UE to network + +##### *FailureInformation message* + +``` + +-- ASN1START +-- TAG-FAILUREINFORMATION-START + +FailureInformation ::= SEQUENCE { + criticalExtensions CHOICE { + failureInformation FailureInformation-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +FailureInformation-IEs ::= SEQUENCE { + failureInfoRLC-Bearer FailureInfoRLC-Bearer OPTIONAL, + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension FailureInformation-v1610-IEs OPTIONAL +} + +FailureInfoRLC-Bearer ::= SEQUENCE { + cellGroupId CellGroupId, + logicalChannelIdentity LogicalChannelIdentity, + failureType ENUMERATED {rlc-failure, spare3, spare2, spare1} +} + +FailureInformation-v1610-IEs ::= SEQUENCE { + failureInfoDAPS-r16 FailureInfoDAPS-r16 OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +FailureInfoDAPS-r16 ::= SEQUENCE { + failureType-r16 ENUMERATED {daps-failure, spare3, spare2, spare1} +} + +-- TAG-FAILUREINFORMATION-STOP +-- ASN1STOP + +``` + +##### *IABOtherInformation* + +The *IABOtherInformation* message is used by IAB-MT to request the network to allocate IP addresses for the collocated IAB-DU or inform the network about IP addresses allocated to the collocated IAB-DU. + +Signalling radio bearer: SRB1 or SRB3 + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: IAB-MT to Network + +##### **IABOtherInformation message** + +``` + +-- ASN1START +-- TAG-IABOTHERINFORMATION-START + +IABOtherInformation-r16 ::= SEQUENCE { + rrc-TransactionIdentifier RRC-TransactionIdentifier, + criticalExtensions CHOICE { + iabOtherInformation-r16 IABOtherInformation-r16-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +IABOtherInformation-r16-IEs ::= SEQUENCE { + ip-InfoType-r16 CHOICE { + iab-IP-Request-r16 SEQUENCE { + iab-IPv4-AddressNumReq-r16 IAB-IP-AddressNumReq-r16 OPTIONAL, + iab-IPv6-AddressReq-r16 CHOICE { + iab-IPv6-AddressNumReq-r16 IAB-IP-AddressNumReq-r16, + iab-IPv6-AddressPrefixReq-r16 IAB-IP-AddressPrefixReq-r16, + ... + } OPTIONAL + }, + iab-IP-Report-r16 SEQUENCE { + iab-IPv4-AddressReport-r16 IAB-IP-AddressAndTraffic-r16 OPTIONAL, + iab-IPv6-Report-r16 CHOICE { + iab-IPv6-AddressReport-r16 IAB-IP-AddressAndTraffic-r16, + iab-IPv6-PrefixReport-r16 IAB-IP-PrefixAndTraffic-r16, + ... + } OPTIONAL + }, + ... + }, + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +IAB-IP-AddressNumReq-r16 ::= SEQUENCE { + all-Traffic-NumReq-r16 INTEGER (1..8) OPTIONAL, + fl-C-Traffic-NumReq-r16 INTEGER (1..8) OPTIONAL, + fl-U-Traffic-NumReq-r16 INTEGER (1..8) OPTIONAL, + non-Fl-Traffic-NumReq-r16 INTEGER (1..8) OPTIONAL, + ... +} + +IAB-IP-AddressPrefixReq-r16 ::= SEQUENCE { + all-Traffic-PrefixReq-r16 ENUMERATED {true} OPTIONAL, + fl-C-Traffic-PrefixReq-r16 ENUMERATED {true} OPTIONAL, +} + +``` + +``` + + fl-U-Traffic-PrefixReq-r16 ENUMERATED {true} OPTIONAL, + non-F1-Traffic-PrefixReq-r16 ENUMERATED {true} OPTIONAL, + ... +} + +IAB-IP-AddressAndTraffic-r16 ::= SEQUENCE { + all-Traffic-IAB-IP-Address-r16 SEQUENCE (SIZE(1..8)) OF IAB-IP-Address-r16 OPTIONAL, + fl-C-Traffic-IP-Address-r16 SEQUENCE (SIZE(1..8)) OF IAB-IP-Address-r16 OPTIONAL, + fl-U-Traffic-IP-Address-r16 SEQUENCE (SIZE(1..8)) OF IAB-IP-Address-r16 OPTIONAL, + non-F1-Traffic-IP-Address-r16 SEQUENCE (SIZE(1..8)) OF IAB-IP-Address-r16 OPTIONAL +} + +IAB-IP-PrefixAndTraffic-r16 ::= SEQUENCE { + all-Traffic-IAB-IP-Address-r16 IAB-IP-Address-r16 OPTIONAL, + fl-C-Traffic-IP-Address-r16 IAB-IP-Address-r16 OPTIONAL, + fl-U-Traffic-IP-Address-r16 IAB-IP-Address-r16 OPTIONAL, + non-F1-Traffic-IP-Address-r16 IAB-IP-Address-r16 OPTIONAL +} + +-- TAG-IABOTHERINFORMATION-STOP +-- ASN1STOP + +``` + +##### ***IABOtherInformation-IEs field descriptions*** + +| IABOtherInformation-IEs field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| iab-IPv4-AddressNumReq
This field is used to request the numbers of IPv4 address per specific usage. The specific usages include F1-C traffic, F1-U traffic, non-F1 traffic and all traffic. | +| iab-IPv4-AddressReport
This field is used to report the IPv4 address per specific usage assigned by OAM for IAB-DU. The specific usages include F1-C traffic, F1-U traffic, non-F1 traffic and all traffic. | +| iab-IPv6-AddressNumReq
This field is used to request the numbers of IPv6 address per specific usage. The specific usages include F1-C traffic, F1-U traffic, non-F1 traffic and all traffic. | +| iab-IPv6-AddressPrefixReq
This field is used to request the prefix of IPv6 address per specific usage. The specific usages include F1-C traffic, F1-U traffic, non-F1 traffic and all traffic. | +| iab-IPv6-AddressReport
This field is used to report the IPv6 address per specific usage assigned by OAM for IAB-DU. The specific usages include F1-C traffic, F1-U traffic, non-F1 traffic and all traffic. | +| iab-IPv6-PrefixReport
This field is used to report the prefix of IPv6 address per specific usage assigned by OAM for IAB-DU. The specific usages include F1-C traffic, F1-U traffic, non-F1 traffic and all traffic. | + +| IAB-IP-AddressNumReq-IEs field descriptions | +|--------------------------------------------------------------------------------------------------------------------| +| all-Traffic-NumReq
This field is used to request the numbers of IP address for all traffic. | +| f1-C-Traffic-NumReq
This field is used to request the numbers of IP address for F1-C traffic. | +| f1-U-Traffic-NumReq
This field is used to request the numbers of IP address for F1-U traffic. | +| non-F1-Traffic-NumReq
This field is used to request the numbers of IP address for non-F1 traffic. | + +| IAB-IP-AddressPrefixReq-IEs field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| all-Traffic-PrefixReq
This field is used to request the IPv6 address prefix for all traffic. The length of allocated IPv6 prefix is fixed to 64. | +| f1-C-Traffic-PrefixReq
This field is used to request the IPv6 address prefix for F1-C traffic. The length of allocated IPv6 prefix is fixed to 64. | +| f1-U-Traffic-PrefixReq
This field is used to request the IPv6 address prefix for F1-U traffic. The length of allocated IPv6 prefix is fixed to 64. | +| non-F1-Traffic-PrefixReq
This field is used to request the IPv6 address prefix for non-F1 traffic. The length of allocated IPv6 prefix is fixed to 64. | + +| IAB-IP-AddressAndTraffic-IEs field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| all-Traffic-IAB-IP-Address
This field is used to report to IAB-donor-CU the IP address(es) or IPv6 address prefix for all traffic. | +| f1-C-Traffic-IP-Address
This field is used to report to IAB-donor-CU the IP address(es) or IPv6 address prefix for F1-C traffic. | +| f1-U-Traffic-IP-Address
This field is used to report to IAB-donor-CU the IP address(es) or IPv6 address prefix for F1-U traffic. | +| non-F1-Traffic-IP-Address
This field is used to report to IAB-donor-CU the IP address(es) or IPv6 address prefix for non-F1 traffic. | + +##### — *IndirectPathFailureInformation* + +The *IndirectPathFailureInformation* message is used to provide information regarding indirect path failure detected by the MP remote UE. + +Signalling radio bearer: SRB1 + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: UE to Network + +##### IndirectPathFailureInformation message + +``` + +-- ASN1START +-- TAG-INDIRECTPATHFAILUREINFORMATION-START + +IndirectPathFailureInformation-r18 ::= SEQUENCE { + criticalExtensions CHOICE { + indirectPathFailureInformation-r18 IndirectPathFailureInformation-r18-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +IndirectPathFailureInformation-r18-IEs ::= SEQUENCE { + failureReportIndirectPath-r18 FailureReportIndirectPath-r18 OPTIONAL, + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +FailureReportIndirectPath-r18 ::= SEQUENCE { + failureTypeIndirectPath-r18 ENUMERATED {t421-Expiry, sl-Failure, n3c-Failure, relayUE-Uu-RLF, ffsrelayUE-HO, + relayUE-CellReselection, relayUE-Uu-RRC-Failure, indirectPathAddChangeFailure} + OPTIONAL, + sl-MeasResultServingRelay-r18 OCTET STRING OPTIONAL, + -- Contains PC5 SL-MeasResultRelay-r17 + sl-MeasResultsCandRelay-r18 OCTET STRING OPTIONAL, + n3c-RelayUE-InfoList-r18 N3C-RelayUE-InfoList-r18 OPTIONAL, + ... +} + +-- TAG-INDIRECTPATHFAILUREINFORMATION-STOP +-- ASN1STOP + +``` + +Editor's Note: FFS whether the detailed report types other than indirectPathAddChangeFailure, path failure, Uu-RLF, Uu failure, PC5-RLF can be included. + +##### IndirectPathFailureInformation field descriptions + +##### **failureTypeIndirectPath** + +The field indicates the failure type of the indirect path failure. + +##### — **LocationMeasurementIndication** + +The *LocationMeasurementIndication* message is used to indicate that the UE is going to either start or stop location related measurement which requires measurement gaps. + +Signalling radio bearer: SRB1 + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: UE to Network + +##### ***LocationMeasurementIndication message*** + +``` +-- ASN1START +-- TAG-LOCATIONMEASUREMENTINDICATION-START + +LocationMeasurementIndication ::= SEQUENCE { + criticalExtensions CHOICE { + locationMeasurementIndication LocationMeasurementIndication-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +LocationMeasurementIndication-IEs ::= SEQUENCE { + measurementIndication SetupRelease {LocationMeasurementInfo}, + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +-- TAG-LOCATIONMEASUREMENTINDICATION-STOP +-- ASN1STOP +``` + +##### ***LoggedMeasurementConfiguration*** + +The *LoggedMeasurementConfiguration* message is used to perform logging of measurement results while in RRC\_IDLE or RRC\_INACTIVE. It is used to transfer the logged measurement configuration for network performance optimisation. + +Signalling radio bearer: SRB1 + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: Network to UE + +###### ***LoggedMeasurementConfiguration message*** + +``` +-- ASN1START +-- TAG-LOGGEDMEASUREMENTCONFIGURATION-START + +LoggedMeasurementConfiguration-r16 ::= SEQUENCE { +``` + +``` + +criticalExtensions CHOICE { + loggedMeasurementConfiguration-r16 LoggedMeasurementConfiguration-r16-IEs, + criticalExtensionsFuture SEQUENCE {} +} + +LoggedMeasurementConfiguration-r16-IEs ::= SEQUENCE { + traceReference-r16 TraceReference-r16, + traceRecordingSessionRef-r16 OCTET STRING (SIZE (2)), + tce-Id-r16 OCTET STRING (SIZE (1)), + absoluteTimeInfo-r16 AbsoluteTimeInfo-r16, + areaConfiguration-r16 AreaConfiguration-r16 OPTIONAL, --Need R + plmn-IdentityList-r16 PLMN-IdentityList2-r16 OPTIONAL, --Need R + bt-NameList-r16 SetupRelease {BT-NameList-r16} OPTIONAL, --Need M + wlan-NameList-r16 SetupRelease {WLAN-NameList-r16} OPTIONAL, --Need M + sensor-NameList-r16 SetupRelease {Sensor-NameList-r16} OPTIONAL, --Need M + loggingDuration-r16 LoggingDuration-r16, + reportType CHOICE { + periodical LoggedPeriodicalReportConfig-r16, + eventTriggered LoggedEventTriggerConfig-r16, + ... + }, + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension LoggedMeasurementConfiguration-v1700-IEs OPTIONAL +} + +LoggedMeasurementConfiguration-v1700-IEs ::= SEQUENCE { + sigLoggedMeasType-r17 ENUMERATED {true} OPTIONAL, -- Need R + earlyMeasIndication-r17 ENUMERATED {true} OPTIONAL, -- Need R + areaConfiguration-r17 AreaConfiguration-r17 OPTIONAL, --Need R + nonCriticalExtension LoggedMeasurementConfiguration-v1800-IEs OPTIONAL +} + +LoggedMeasurementConfiguration-v1800-IEs ::= SEQUENCE { + areaConfiguration-v1800 AreaConfiguration-v1800 OPTIONAL, --Need R + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +LoggedPeriodicalReportConfig-r16 ::= SEQUENCE { + loggingInterval-r16 LoggingInterval-r16, + ... +} + +LoggedEventTriggerConfig-r16 ::= SEQUENCE { + eventType-r16 EventType-r16, + loggingInterval-r16 LoggingInterval-r16, + ... +} + +EventType-r16 ::= CHOICE { + outOfCoverage NULL, + +``` + +``` + +eventL1 SEQUENCE { + l1-Threshold MeasTriggerQuantity, + hysteresis Hysteresis, + timeToTrigger TimeToTrigger +}, +... +} + +-- TAG-LOGGEDMEASUREMENTCONFIGURATION-STOP +-- ASN1STOP + +``` + +###### LoggedMeasurementConfiguration field descriptions + +| | | +|---------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| absoluteTimeInfo | Indicates the absolute time in the current cell. | +| areaConfiguration | Used to restrict the area in which the UE performs measurement logging to cells broadcasting either one of the included cell identities or one of the included tracking area codes/ frequencies or one of the included PNI-NPN IDs or SNPN IDs. If areaConfiguration-r17 is present, the UE shall ignore areaConfiguration-r16 . | +| earlyMeasIndication | If included, the field indicates the UE is allowed to log measurements on early measurement related frequencies in logged measurements. | +| eventType | The value outOfCoverage indicates the UE to perform logging of measurements when the UE enters any cell selection state, and the value eventL1 indicates the UE to perform logging of measurements when the triggering condition (similar as event A2 as specified in 5.5.4.3) as configured in the event is met for the camping cell in camped normally state. | +| plmn-IdentityList | Indicates a set of PLMNs defining when the UE performs measurement logging as well as the associated status indication and information retrieval i.e. the UE performs these actions when the RPLMN is part of this set of PLMNs. | +| sigLoggedMeasType | If included, the field indicates a signalling based logged measurement configuration (See TS 37.320 [61]). | +| tce-Id | Parameter Trace Collection Entity Id: See TS 32.422 [52]. | +| traceRecordingSessionRef | Parameter Trace Recording Session Reference: See TS 32.422 [52]. | +| reportType | Parameter configures the type of MDT configuration, specifically Periodic MDT configuration or Event Triggered MDT configuration. | + +##### — MBSBroadcastConfiguration + +The *MBSBroadcastConfiguration* message contains the control information applicable for MBS broadcast services transmitted via broadcast MRB. + +Signalling radio bearer: N/A + +RLC-SAP: UM + +Logical channel: MCCH + +Direction: Network to UE + +###### ***MBSBroadcastConfiguration message*** + +``` +-- ASN1START +-- TAG-MBSBROADCASTCONFIGURATION-START + +MBSBroadcastConfiguration-r17 ::= SEQUENCE { + criticalExtensions CHOICE { + mbsBroadcastConfiguration-r17 MBSBroadcastConfiguration-r17-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +MBSBroadcastConfiguration-r17-IEs ::= SEQUENCE { + mbs-SessionInfoList-r17 MBS-SessionInfoList-r17 OPTIONAL, -- Need R + mbs-NeighbourCellList-r17 MBS-NeighbourCellList-r17 OPTIONAL, -- Need S + drx-ConfigPTM-List-r17 SEQUENCE (SIZE (1..maxNrofDRX-ConfigPTM-r17)) OF DRX-ConfigPTM-r17 OPTIONAL, -- Need R + pdsch-ConfigMTCH-r17 PDSCH-ConfigBroadcast-r17 OPTIONAL, -- Need S + mtch-SSB-MappingWindowList-r17 MTCH-SSB-MappingWindowList-r17 OPTIONAL, -- Need R + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +-- TAG-MBSBROADCASTCONFIGURATION-STOP +-- ASN1STOP +``` + +##### ***MBSBroadcastConfiguration field descriptions*** + +##### ***pdsch-ConfigMTCH*** + +Provides parameters for acquiring the PDSCH for MTCH. When this field is absent, the UE shall use parameters in *pdsch-ConfigMCCH* to acquire the PDSCH for MTCH. + +##### ***mbs-SessionInfoList*** + +Provides the configuration of each MBS session provided by MBS broadcast in the current cell. + +##### ***mbs-NeighbourCellList*** + +List of neighbour cells providing one or more MBS broadcast services via broadcast MRB that are provided by the current cell. This field is used by the UE together with *mtch-NeighbourCell* field signalled for each MBS session in the corresponding *MBS-SessionInfo*. When an empty *mbs-NeighbourCellList* list is signalled, the UE shall assume that MBS broadcast services signalled in *mbs-SessionInfoList* in the *MBSBroadcastConfiguration* message are not provided in any neighbour cell. When a non-empty *mbs-NeighbourCellList* is signalled, the current serving cell does not provide information about MBS broadcast services of a neighbour cell that is not included in *mbs-NeighbourCellList*, i.e., the UE cannot determine the presence or absence of an MBS service of a neighbour cell that is absent. When the field *mbs-NeighbourCellList* is absent, the current serving cell does not provide information about MBS broadcast services in the neighbouring cells, i.e. the UE cannot determine the presence or absence of an MBS service in neighbouring cells based on the absence of this field. + +##### — *MBSInterestIndication* + +The *MBSInterestIndication* message is used to inform network that the UE is receiving/ interested to receive or no longer receiving/ interested to receive MBS broadcast service(s) via a broadcast MRB. + +Signalling radio bearer: SRB1 + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: UE to Network + +###### *MBSInterestIndication message* + +``` +-- ASN1START +-- TAG-MBSINTERESTINDICATION-START + +MBSInterestIndication-r17 ::= SEQUENCE { + criticalExtensions CHOICE { + mbsInterestIndication-r17 MBSInterestIndication-r17-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +MBSInterestIndication-r17-IEs ::= SEQUENCE { + mbs-FreqList-r17 CarrierFreqListMBS-r17 OPTIONAL, + mbs-Priority-r17 ENUMERATED {true} OPTIONAL, + mbs-ServiceList-r17 MBS-ServiceList-r17 OPTIONAL, + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension MBSInterestIndication-v1800 OPTIONAL +} + +MBSInterestIndication-v1800 ::= SEQUENCE { + mbs-NonServingInfoList-r18 MBS-NonServingInfoList-r18 OPTIONAL, + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +-- TAG-MBSINTERESTINDICATION-STOP +-- ASN1STOP +``` + +| MBSInterestIndication field descriptions | | +|-------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| mbs-FreqList | List of MBS frequencies on which the UE is receiving or interested to receive MBS broadcast service via a broadcast MRB. | +| mbs-NonServingInfoList | Indicates information for MBS broadcast reception on the non-serving cell. | +| mbs-Priority | Indicates whether the UE prioritises MBS broadcast reception above unicast and MBS multicast reception. The field is present (i.e. value true ), if the UE prioritises reception of broadcast services, on frequencies indicated in mbs-FreqList , above a reception of any of the unicast bearers and multicast MRBs. Otherwise the field is absent. | +| mbs-ServiceList | List of MBS broadcast services which the UE is receiving or interested to receive. | + +###### – ***MBSMulticastConfiguration*** + +The *MBSMulticastConfiguration* message contains the control information applicable for MBS multicast services transmitted via multicast MRBs for RRC\_INACTIVE UEs. + +Signalling radio bearer: N/A + +RLC-SAP: UM + +Logical channel: multicast MCCH + +Direction: Network to UE + +###### ***MBSMulticastConfiguration message*** + +``` +-- ASN1START +-- TAG-MBSMULTICASTCONFIGURATION-START + +MBSMulticastConfiguration-r18 ::= SEQUENCE { + criticalExtensions CHOICE { + mbsMulticastConfiguration-r18 MBSMulticastConfiguration-r18-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +MBSMulticastConfiguration-r18-IEs ::= SEQUENCE { + mbs-SessionInfoList-r18 MBS-SessionInfoListMulticast-r18 OPTIONAL, -- Need R + mbs-NeighbourCellList-r18 MBS-NeighbourCellList-r17 OPTIONAL, -- Need S + drx-ConfigPTM-List-r18 SEQUENCE (SIZE (1..maxNrofDRX-ConfigPTM-r17)) OF DRX-ConfigPTM-r17 OPTIONAL, -- Need R + pdsch-ConfigMTCH-r18 PDSCH-ConfigBroadcast-r17 OPTIONAL, -- Need S + mtch-SSB-MappingWindowList-r18 MTCH-SSB-MappingWindowList-r17 OPTIONAL, -- Need R + thresholdMBS-List-r18 SEQUENCE (SIZE (1..maxNrofThresholdMBS-r18)) OF ThresholdMBS-r18 OPTIONAL, -- Need R + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} +``` + +``` + +ThresholdMBS-r18 ::= CHOICE { + rsrp-r18 RSRP-Range, + rsrq-r18 RSQ-Range +} + +-- TAG-MBSMULTICASTCONFIGURATION-STOP +-- ASN1STOP + +``` + +##### ***MBSMulticastConfiguration field descriptions*** + +###### ***mbs-NeighbourCellList*** + +List of neighbour cells providing one or more MBS multicast services for RRC\_INACTIVE that are provided by the current cell. This field is used by the UE together with *mtch-NeighbourCell* field signalled for each MBS session in the corresponding *MBS-SessionInfo*. When an empty *mbs-NeighbourCellList* list is signalled, the UE shall assume that MBS multicast services signalled in *mbs-SessionInfoList* in the *MBSMulticastConfiguration* message are not provided in any neighbour cell. When a non-empty *mbs-NeighbourCellList* is signalled, the current serving cell does not provide information about MBS multicast services of a neighbour cell that is not included in *mbs-NeighbourCellList*, i.e., the UE cannot determine the presence or absence of an MBS multicast service of a neighbour cell that is absent. When the field *mbs-NeighbourCellList* is absent, the current serving cell does not provide information about MBS multicast services in the neighbouring cells, i.e. the UE cannot determine the presence or absence of an MBS multicast service in neighbouring cells based on the absence of this field. + +##### ***mbs-SessionInfoList*** + +Provides the configuration of each MBS session provided by MBS multicast in the current cell. + +##### ***pdsch-ConfigMTCH*** + +Provides parameters for acquiring the PDSCH for MTCH. When this field is absent, the UE shall use parameters in *pdsch-ConfigMCCH* in *SIB24* to acquire the PDSCH for MTCH. + +##### ***thresholdMBS-List*** + +List of reception quality thresholds for RRC connection resume for a UE receiving multicast in RRC\_INACTIVE. + +##### — ***MCGFailureInformation*** + +The *MCGFailureInformation* message is used to provide information regarding NR MCG failures detected by the UE. + +Signalling radio bearer: SRB1 + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: UE to Network + +##### ***MCGFailureInformation message*** + +``` + +-- ASN1START +-- TAG-MCGFAILUREINFORMATION-START + +MCGFailureInformation-r16 ::= SEQUENCE { + +``` + +``` + + criticalExtensions CHOICE { + mcgFailureInformation-r16 MCGFailureInformation-r16-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +MCGFailureInformation-r16-IEs ::= SEQUENCE { + failureReportMCG-r16 FailureReportMCG-r16 OPTIONAL, + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +FailureReportMCG-r16 ::= SEQUENCE { + failureType-r16 ENUMERATED {t310-Expiry, randomAccessProblem, rlc-MaxNumRetx, + t312-Expiry-r16, lbt-Failure-r16, beamFailureRecoveryFailure-r16, + bh-RLF-r16, spare1} OPTIONAL, + measResultFreqList-r16 MeasResultList2NR OPTIONAL, + measResultFreqListEUTRA-r16 MeasResultList2EUTRA OPTIONAL, + measResultSCG-r16 OCTET STRING (CONTAINING MeasResultSCG-Failure) OPTIONAL, + measResultSCG-EUTRA-r16 OCTET STRING OPTIONAL, + measResultFreqListUTRA-FDD-r16 MeasResultList2UTRA OPTIONAL, + ... +} + +MeasResultList2UTRA ::= SEQUENCE (SIZE (1..maxFreq)) OF MeasResult2UTRA-FDD-r16 + +MeasResult2UTRA-FDD-r16 ::= SEQUENCE { + carrierFreq-r16 ARFCN-ValueUTRA-FDD-r16, + measResultNeighCellList-r16 MeasResultListUTRA-FDD-r16 +} + +MeasResultList2EUTRA ::= SEQUENCE (SIZE (1..maxFreq)) OF MeasResult2EUTRA-r16 + +-- TAG-MCGFAILUREINFORMATION-STOP +-- ASN1STOP + +``` + +| MCGFailureInformation field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| measResultFreqList
The field contains available results of measurements on NR frequencies the UE is configured to measure by the measConfig associated with the MCG. | +| measResultFreqListEUTRA
The field contains available results of measurements on E-UTRA frequencies the UE is configured to measure by measConfig associated with the MCG. | +| measResultFreqListUTRA-FDD
The field contains available results of measurements on UTRA FDD frequencies the UE is configured to measure by measConfig associated with the MCG. | +| measResultSCG
The field contains the MeasResultSCG-Failure IE which includes available measurement results on NR frequencies the UE is configured to measure by the measConfig associated with the SCG. | +| measResultSCG-EUTRA
The field contains the E-UTRA MeasResultSCG-FailureMRDC IE which includes available results of measurements on E-UTRA frequencies the UE is configured to measure by the E-UTRA RRCConnectionReconfiguration message as specified in TS 36.331 [10]. | + +##### — *MeasurementReport* + +The *MeasurementReport* message is used for the indication of measurement results. + +Signalling radio bearer: SRB1, SRB3 + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: UE to Network + +##### ***MeasurementReport message*** + +``` +-- ASN1START +-- TAG-MEASUREMENTREPORT-START + +MeasurementReport ::= + criticalExtensions + measurementReport + criticalExtensionsFuture + } +} + +MeasurementReport-IEs ::= + measResults + lateNonCriticalExtension + nonCriticalExtension + } + +SEQUENCE { + CHOICE { + MeasurementReport-IEs, + SEQUENCE {} + } + +SEQUENCE { + MeasResults, + OCTET STRING + SEQUENCE {} + } +} + +OPTIONAL, +OPTIONAL +``` + +``` +-- TAG-MEASUREMENTREPORT-STOP +-- ASN1STOP +``` + +##### – *MeasurementReportAppLayer* + +The *MeasurementReportAppLayer* message is used for sending application layer measurement report. + +Signalling radio bearer: SRB4, SRB5 + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: UE to Network + +##### *MeasurementReportAppLayer message* + +``` +-- ASN1START +-- TAG-MEASUREMENTREPORTAPPLAYER-START + +MeasurementReportAppLayer-r17 ::= SEQUENCE { + criticalExtensions CHOICE { + measurementReportAppLayer-r17 MeasurementReportAppLayer-r17-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +MeasurementReportAppLayer-r17-IEs ::= SEQUENCE { + measurementReportAppLayerList-r17 MeasurementReportAppLayerList-r17, + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension MeasurementReportAppLayer-v1800-IEs OPTIONAL +} + +MeasurementReportAppLayer-v1800-IEs ::= SEQUENCE { + measurementReportAppLayerList-r18 MeasurementReportAppLayerList-r18 OPTIONAL, + nonCriticalExtension SEQUENCE{} OPTIONAL +} + +MeasurementReportAppLayerList-r17 ::= SEQUENCE (SIZE (1..maxNrofAppLayerMeas-r17)) OF MeasReportAppLayer-r17 +MeasurementReportAppLayerList-r18 ::= SEQUENCE (SIZE (1..maxNrofAppLayerMeas-r17)) OF MeasReportAppLayer-r18 + +MeasReportAppLayer-r17 ::= SEQUENCE { + measConfigAppLayerId-r17 MeasConfigAppLayerId-r17, + measReportAppLayerContainer-r17 OCTET STRING OPTIONAL, + appLayerSessionStatus-r17 ENUMERATED {start, stop} OPTIONAL, + ran-VisibleMeasurements-r17 RAN-VisibleMeasurements-r17 OPTIONAL +} +``` + +``` + +} + +MeasReportAppLayer-r18 ::= SEQUENCE { + idleInactiveConfig-r18 AppLayerIdleInactiveConfig-r18 OPTIONAL, + ... +} + +RAN-VisibleMeasurements-r17 ::= SEQUENCE { + appLayerBufferLevelList-r17 SEQUENCE (SIZE (1..8)) OF AppLayerBufferLevel-r17 OPTIONAL, + playoutDelayForMediaStartup-r17 INTEGER (0..30000) OPTIONAL, + pdu-SessionIdList-r17 SEQUENCE (SIZE (1..maxNrofPDU-Sessions-r17)) OF PDU-SessionID OPTIONAL, + ..., + [[ + pdu-SessionIdList-r18 SEQUENCE (SIZE (1..maxNrofPDU-Sessions-r17)) OF QFI-List-r18 OPTIONAL + ]] +} + +AppLayerBufferLevel-r17 ::= INTEGER (0..30000) + +QFI-List-r18 ::= SEQUENCE (SIZE (1..maxNrofQFIs)) OF QFI + +-- TAG-MEASUREMENTREPORTAPPLAYER-STOP +-- ASN1STOP + +``` + +##### | MeasurementReportAppLayer field descriptions | |-----------------------------------------------------| |-----------------------------------------------------| + +###### | | |--------------------------------------| | measurementReportAppLayerList | |--------------------------------------| + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| The field contains a list of application layer measurement reports. If measurementreportAppLayerList-r18 is present, it contains the same number of entries, listed in the same order as in measurementReportAppLayerList-r17 . | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +##### | MeasReportAppLayer field descriptions | |----------------------------------------------| |----------------------------------------------| + +###### | | |------------------------------| | appLayerSessionStatus | |------------------------------| + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Indicates that an application layer measurement session in the application layer starts or ends. For application layer measurements applicable to RRC_IDLE or RRC_INACTIVE, the UE transmits appLayerSessionStatus upon transfer to RRC_CONNECTED. | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +###### | | |------------------------------------| | measReportAppLayerContainer | |------------------------------------| + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| The field contains the application layer measurement report container, see Annex L (normative) in TS 26.247 [68], clause 16.5 in TS 26.114 [69] and TS 26.118 [70]. | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +##### | | |--------------------------------| | ran-VisibleMeasurements | |--------------------------------| + +| | +|--------------------------------------------------------------------------| +| The field contains the RAN visible application layer measurement report. | +|--------------------------------------------------------------------------| + +| RAN-VisibleMeasurements field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| appLayerBufferLevelList
The field indicates a list of application layer buffer levels, and each AppLayerBufferLevel indicates the application layer buffer level in ms. Value 0 corresponds to 0ms, value 1 corresponds to 10ms, value 2 corresponds to 20 ms and so on. If the buffer level is larger than the maximum value of 30000 (5 minutes), the UE reports 30000. | +| playoutDelayForMediaStartup
Indicates the application layer playout delay for media start-up in ms. Value 0 corresponds to 0ms, value 1 corresponds to 1ms, value 2 corresponds to 2 ms and so on. If the playout delay for media start-up is larger than the maximum value of 30000ms, the UE reports 30000. | +| pdu-SessionIdList
List of PDU session identities and QoS flow identities per PDU session associated with the application data flows subject to the RAN visible application layer measurements. If pdu-SessionIdList-r18 is present, it contains the same number of entries, listed in the same order as in pdu-SessionIdList-r17 . | + +##### — **MIB** + +The *MIB* includes the system information transmitted on BCH. + +Signalling radio bearer: N/A + +RLC-SAP: TM + +Logical channel: BCCH + +Direction: Network to UE + +###### **MIB** + +``` +-- ASN1START +-- TAG-MIB-START + +MIB ::= SEQUENCE { + systemFrameNumber BIT STRING (SIZE (6)), + subCarrierSpacingCommon ENUMERATED {scs15or60, scs30or120}, + ssb-SubcarrierOffset INTEGER (0..15), + dmrs-TypeA-Position ENUMERATED {pos2, pos3}, + pdcch-ConfigSIB1 PDCCH-ConfigSIB1, + cellBarred ENUMERATED {barred, notBarred}, + intraFreqReselection ENUMERATED {allowed, notAllowed}, + spare BIT STRING (SIZE (1)) +} + +-- TAG-MIB-STOP +-- ASN1STOP +``` + +| MIB field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| cellBarred
Value barred means that the cell is barred, as defined in TS 38.304 [20]. This field is ignored by IAB-MT and NCR-MT. This field is ignored for connectivity to NTN or ATG. | +| dmrs-TypeA-Position
Position of (first) DM-RS for downlink (see TS 38.211 [16], clause 7.4.1.1.2) and uplink (see TS 38.211 [16], clause 6.4.1.1.3). | +| intraFreqReselection
Controls cell selection/reselection to intra-frequency cells when the highest ranked cell is barred, or treated as barred by the UE, as specified in TS 38.304 [20]. This field is ignored by IAB-MT and NCR-MT. | +| pdcch-ConfigSIB1
Determines a common ControlResourceSet (CORESET), a common search space and necessary PDCCH parameters. If the field ssb-SubcarrierOffset indicates that SIB1 is absent, the field pdcch-ConfigSIB1 indicates the frequency positions where the UE may find SS/PBCH block with SIB1 or the frequency range where the network does not provide SS/PBCH block with SIB1 (see TS 38.213 [13], clause 13). | +| ssb-SubcarrierOffset
Corresponds to $k_{\text{SSB}}$ (see TS 38.213 [13]), which is the frequency domain offset between SSB and the overall resource block grid in number of subcarriers. (See TS 38.211 [16], clause 7.4.3.1). For operation with shared spectrum channel access in FR1 (see 37.213 [48]), this field corresponds to $k_{\text{SSB}}$ and $k_{\text{SSB}}$ is obtained from (see TS 38.211 [16], clause 7.4.3.1); the LSB of this field is used also for deriving the QCL relation between SS/PBCH blocks as specified in TS 38.213 [13], clause 4.1. The value range of this field may be extended by an additional most significant bit encoded within PBCH as specified in TS 38.213 [13]. This field may indicate that this cell does not provide SIB1 and that there is hence no CORESET#0 configured in MIB (see TS 38.213 [13], clause 13). In this case, the field pdcch-ConfigSIB1 may indicate the frequency positions where the UE may (not) find a SS/PBCH with a control resource set and search space for SIB1 (see TS 38.213 [13], clause 13). | +| subCarrierSpacingCommon
Subcarrier spacing for SIB1 , Msg.2/4 and MsgB for initial access, paging and broadcast SI-messages. If the UE acquires this MIB on an FR1 carrier frequency, the value scs15or60 corresponds to 15 kHz and the value scs30or120 corresponds to 30 kHz. If the UE acquires this MIB on an FR2 carrier frequency, the value scs15or60 corresponds to 60 kHz and the value scs30or120 corresponds to 120 kHz. For operation with shared spectrum channel access in FR1 (see 37.213 [48]) and for operation in FR2-2, the subcarrier spacing for SIB1 , Msg.2/4 and MsgB for initial access, paging and broadcast SI-messages is same as that for the corresponding SSB. For operation with shared spectrum channel access, this field instead is used for deriving the QCL relation between SS/PBCH blocks as specified in TS 38.213 [13], clause 4.1. | +| systemFrameNumber
The 6 most significant bits (MSB) of the 10-bit System Frame Number (SFN). The 4 LSB of the SFN are conveyed in the PBCH transport block as part of channel coding (i.e. outside the MIB encoding), as defined in clause 7.1 in TS 38.212 [17]. | + +##### – *MobilityFromNRCommand* + +The *MobilityFromNRCommand* message is used to command handover from NR to E-UTRA/EPC, E-UTRA/5GC or UTRA-FDD. + +Signalling radio bearer: SRB1 + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: Network to UE + +##### **MobilityFromNRCommand message** + +``` + +-- ASN1START +-- TAG-MOBILITYFROMNRCOMMAND-START + +MobilityFromNRCommand ::= SEQUENCE { + rrc-TransactionIdentifier RRC-TransactionIdentifier, + criticalExtensions CHOICE { + mobilityFromNRCommand MobilityFromNRCommand-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +MobilityFromNRCommand-IEs ::= SEQUENCE { + targetRAT-Type ENUMERATED { eutra, utra-fdd-v1610, spare2, spare1, ...}, + targetRAT-MessageContainer OCTET STRING, + nas-SecurityParamFromNR OCTET STRING OPTIONAL, -- Cond HO-ToEPCUTRAN + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension MobilityFromNRCommand-v1610-IEs OPTIONAL +} + +MobilityFromNRCommand-v1610-IEs ::= SEQUENCE { + voiceFallbackIndication-r16 ENUMERATED {true} OPTIONAL, -- Need N + nonCriticalExtension MobilityFromNRCommand-v1800-IEs OPTIONAL +} + +MobilityFromNRCommand-v1800-IEs ::= SEQUENCE { + successHO-Config-r18 SetupRelease {SuccessHO-Config-r17} OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +-- TAG-MOBILITYFROMNRCOMMAND-STOP +-- ASN1STOP + +``` + +##### **MobilityFromNRCommand-IEs field descriptions** + +| | | +|-----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| nas-SecurityParamFromNR | If targetRAT-Type is eutra , this field is used to deliver the key synchronisation and Key freshness for the NR to LTE/EPC handovers and a part of the downlink NAS COUNT as specified in TS 33.501 [11] and the content of the parameter is defined in TS 24.501 [23]. If targetRAT-Type is utra-fdd , this field is used to deliver the key synchronisation and Key freshness for the NR to FDD UTRAN handover and a part of the downlink NAS COUNT as specified in TS 33.501 [11] and the content of the parameter is defined in TS 24.501 [23]. | +| targetRAT-MessageContainer | The field contains a message specified in another standard, as indicated by the targetRAT-Type , and carries information about the target cell identifier(s) and radio parameters relevant for the target radio access technology. A complete message is included, as specified in the other standard. See NOTE 1 | +| targetRAT-Type | Indicates the target RAT type. | +| voiceFallbackIndication | Indicates the handover is triggered by EPS fallback for IMS voice as specified in TS 23.502 [43]. | + +NOTE 1: The correspondence between the value of the *targetRAT-Type*, the standard to apply, and the message contained within the *targetRAT-MessageContainer* is shown in the table below: + +| targetRAT-Type | Standard to apply | targetRAT-MessageContainer | +|-----------------------|----------------------------------|-------------------------------------------------------------------------| +| eutra | TS 36.331 [10] (clause 5.4.2) | DL-DCCH-Message including the RRConnectionReconfiguration | +| utra-fdd | TS 25.331 [45] (clause 10.2.16a) | Handover TO UTRAN command | + +| Conditional Presence | Explanation | +|-----------------------------|-------------------------------------------------------------------------------------------------------------------| +| HO-ToEPCUTRAN | This field is mandatory present in case of inter system handover to "EPC" or "FDD UTRAN". Otherwise it is absent. | + +##### — *Paging* + +The *Paging* message is used for the notification of one or more UEs. + +Signalling radio bearer: N/A + +RLC-SAP: TM + +Logical channel: PCCH + +Direction: Network to UE + +##### *Paging message* + +``` +-- ASN1START +-- TAG-PAGING-START + +Paging ::= SEQUENCE { + pagingRecordList PagingRecordList OPTIONAL, -- Need N + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension Paging-v1700-IEs OPTIONAL +} + +Paging-v1700-IEs ::= SEQUENCE { + pagingRecordList-v1700 PagingRecordList-v1700 OPTIONAL, -- Need N + pagingGroupList-r17 PagingGroupList-r17 OPTIONAL, -- Need N + nonCriticalExtension Paging-v1800-IEs OPTIONAL +} + +Paging-v1800-IEs ::= SEQUENCE { + pagingRecordList-v1800 PagingRecordList-v1800 OPTIONAL, -- Need N + pagingGroupList-v1800 PagingGroupList-v1800 OPTIONAL, -- Need N +} +``` + +``` + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +PagingRecordList ::= SEQUENCE (SIZE(1..maxNrofPageRec)) OF PagingRecord +PagingRecordList-v1700 ::= SEQUENCE (SIZE(1..maxNrofPageRec)) OF PagingRecord-v1700 +PagingGroupList-r17 ::= SEQUENCE (SIZE(1..maxNrofPageGroup-r17)) OF TMGI-r17 +PagingRecordList-v1800 ::= SEQUENCE (SIZE(1..maxNrofPageRec)) OF PagingRecord-v1800 +PagingGroupList-v1800 ::= SEQUENCE (SIZE(1..maxNrofPageGroup-r17)) OF GroupPaging-r18 + +PagingRecord ::= SEQUENCE { + ue-Identity PagingUE-Identity, + accessType ENUMERATED {non3GPP} OPTIONAL, -- Need N + ... +} + +PagingRecord-v1700 ::= SEQUENCE { + pagingCause-r17 ENUMERATED {voice} OPTIONAL -- Need N +} + +PagingRecord-v1800 ::= SEQUENCE { + mt-SDT ENUMERATED {true} OPTIONAL -- Need N +} + +PagingUE-Identity ::= CHOICE { + ng-5G-S-TMSI NG-5G-S-TMSI, + fullI-RNTI I-RNTI-Value, + ... +} + +GroupPaging-r18 ::= SEQUENCE { + inactiveReceptionAllowed-r18 ENUMERATED {true} OPTIONAL -- Need N +} + +-- TAG-PAGING-STOP +-- ASN1STOP +``` + +| PagingRecord field descriptions | | +|----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| accessType | Indicates whether the Paging message is originated due to the PDU sessions from the non-3GPP access. | +| inactiveReceptionAllowed | Indicates whether the UE with a valid PTM configuration for a TMGI in the PagingGroupList stays in RRC_INACTIVE to receive the corresponding MBS multicast session. | +| mt-SDT | Mobile Terminated SDT indication. The network includes mt-SDT indication in paging message only if the UE's I-RNTI is included in the paging message. | +| pagingRecordList | If the network includes pagingRecordList-v1700 , it includes the same number of entries, and listed in the same order, as in pagingRecordList (i.e. without suffix). If the network includes pagingRecordList-v1800 , it includes the same number of entries, and listed in the same order, as in pagingRecordList (i.e. without suffix). | +| pagingCause | Indicates whether the Paging message is originated due to IMS voice. If this field is present, it implies that the corresponding paging entry is for IMS voice. If upper layers indicate the support of paging cause and if this field is not present but pagingRecordList-v1700 is present, it implies that the corresponding paging entry is for a service other than IMS voice. Otherwise, paging cause is undetermined. | +| pagingGroupList | If the network includes pagingGroupList-v1800 , it includes the same number of elements, and listed in the same order, as in pagingGroupList-r17 . The first element corresponds to the first TMGI in pagingGroupList-r17 . The second element corresponds to the second TMGI in pagingGroupList-r17 , and so on. | + +##### — *RRCREestablishment* + +The *RRCREestablishment* message is used to re-establish SRB1. + +Signalling radio bearer: SRB1 + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: Network to UE + +##### ***RRCREestablishment* message** + +``` +-- ASN1START +-- TAG-RRCREESTABLISHMENT-START + +RRCREestablishment ::= + SEQUENCE { + rrc-TransactionIdentifier RRC-TransactionIdentifier, + criticalExtensions CHOICE { + rrcReestablishment RRCReestablishment-IEs, + criticalExtensionsFuture SEQUENCE {} + } + } + +RRCREestablishment-IEs ::= + SEQUENCE { + nextHopChainingCount NextHopChainingCount, +``` + +``` + + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension RRCReestablishment-v1700-IEs OPTIONAL +} + +RRCReestablishment-v1700-IEs ::= SEQUENCE { + sl-L2RemoteUE-Config-r17 SetupRelease {SL-L2RemoteUE-Config-r17} OPTIONAL, -- Cond L2RemoteUE + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +-- TAG-RRCREESTABLISHMENT-STOP +-- ASN1STOP + +``` + +##### RRCReestablishment-IEs field descriptions + +##### sl-L2RemoteUE-Config + +Contains dedicated configurations used for L2 U2N relay related operation. The network configures only the SRAP configuration for local UE ID. + +| Conditional Presence | Explanation | +|----------------------|------------------------------------------------------------------------------| +| L2RemoteUE | The field is mandatory present for L2 U2N Remote UE; otherwise it is absent. | + +###### – RRCReestablishmentComplete + +The *RRCReestablishmentComplete* message is used to confirm the successful completion of an RRC connection re-establishment. + +Signalling radio bearer: SRB1 + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: UE to Network + +###### RRCReestablishmentComplete message + +``` + +-- ASN1START +-- TAG-RRCREESTABLISHMENTCOMPLETE-START + +RRCReestablishmentComplete ::= SEQUENCE { + rrc-TransactionIdentifier RRC-TransactionIdentifier, + criticalExtensions CHOICE { + rrcReestablishmentComplete RRCReestablishmentComplete-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +``` + +``` + +RRReestablishmentComplete-IEs ::= SEQUENCE { + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension RRReestablishmentComplete-v1610-IEs OPTIONAL +} + +RRReestablishmentComplete-v1610-IEs ::= SEQUENCE { + ue-MeasurementsAvailable-r16 UE-MeasurementsAvailable-r16 OPTIONAL, + nonCriticalExtension RRReestablishmentComplete-v1800-IEs OPTIONAL +} + +RRReestablishmentComplete-v1800-IEs ::= SEQUENCE { + flightPathInfoAvailable-r18 ENUMERATED {true} OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +-- TAG-RRCREESTABLISHMENTCOMPLETE-STOP +-- ASN1STOP + +``` + +##### — *RRReestablishmentRequest* + +The *RRReestablishmentRequest* message is used to request the reestablishment of an RRC connection. + +Signalling radio bearer: SRB0 + +RLC-SAP: TM + +Logical channel: CCCH + +Direction: UE to Network + +###### *RRReestablishmentRequest message* + +``` + +-- ASN1START +-- TAG-RRCREESTABLISHMENTREQUEST-START + +RRReestablishmentRequest ::= SEQUENCE { + rrcReestablishmentRequest RRReestablishmentRequest-IEs +} + +RRReestablishmentRequest-IEs ::= SEQUENCE { + ue-Identity ReestabUE-Identity, + reestablishmentCause ReestablishmentCause, + spare BIT STRING (SIZE (1)) +} + +ReestabUE-Identity ::= SEQUENCE { + +``` + +``` + + c-RNTI RNTI-Value, + physCellId PhysCellId, + shortMAC-I ShortMAC-I + } + + ReestablishmentCause ::= + ENUMERATED {reconfigurationFailure, handoverFailure, otherFailure, spare1} + + -- TAG-RRCREESTABLISHMENTREQUEST-STOP + -- ASN1STOP + +``` + +###### ReestabUE-Identity field descriptions + +| | +|------------------------------------------------------------------------------------------------------------| +| physCellId
The Physical Cell Identity of the PCell the UE was connected to prior to the failure. | +|------------------------------------------------------------------------------------------------------------| + +###### RRCREestablishmentRequest-IEs field descriptions + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| reestablishmentCause
Indicates the failure cause that triggered the re-establishment procedure. gNB is not expected to reject a RRCREestablishmentRequest due to unknown cause value being used by the UE. | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | +|----------------------------------------------------------------------------------------------------------------------------| +| ue-Identity
UE identity included to retrieve UE context and to facilitate contention resolution by lower layers. | +|----------------------------------------------------------------------------------------------------------------------------| + +##### — *RRCREconfiguration* + +The *RRCREconfiguration* message is the command to modify an RRC connection. It may convey information for measurement configuration, mobility control, radio resource configuration (including RBs, MAC main configuration and physical channel configuration) and AS security configuration. + +Signalling radio bearer: SRB1 or SRB3 + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: Network to UE + +##### *RRCREconfiguration message* + +``` + + -- ASN1START + -- TAG-RRCRECONFIGURATION-START + + RRCReconfiguration ::= + SEQUENCE { + rrc-TransactionIdentifier RRC-TransactionIdentifier, + criticalExtensions CHOICE { + rrcReconfiguration RRCReconfiguration-IEs, + } + } + +``` + +``` + + criticalExtensionsFuture SEQUENCE { + } + } +} + +RRcReconfiguration-IEs ::= SEQUENCE { + radioBearerConfig RadioBearerConfig OPTIONAL, -- Need M + secondaryCellGroup OCTET STRING (CONTAINING CellGroupConfig) OPTIONAL, -- Cond SCG + measConfig MeasConfig OPTIONAL, -- Need M + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension RRcReconfiguration-v1530-IEs OPTIONAL +} + +RRcReconfiguration-v1530-IEs ::= SEQUENCE { + masterCellGroup OCTET STRING (CONTAINING CellGroupConfig) OPTIONAL, -- Need M + fullConfig ENUMERATED {true} OPTIONAL, -- Cond FullConfig + dedicatedNAS-MessageList SEQUENCE (SIZE(1..maxDRB)) OF DedicatedNAS-Message OPTIONAL, -- Cond nonHO + masterKeyUpdate MasterKeyUpdate OPTIONAL, -- Cond MasterKeyChange + dedicatedSIB1-Delivery OCTET STRING (CONTAINING SIB1) OPTIONAL, -- Need N + dedicatedSystemInformationDelivery OCTET STRING (CONTAINING SystemInformation) OPTIONAL, -- Need N + otherConfig OtherConfig OPTIONAL, -- Need M + nonCriticalExtension RRcReconfiguration-v1540-IEs OPTIONAL +} + +RRcReconfiguration-v1540-IEs ::= SEQUENCE { + otherConfig-v1540 OtherConfig-v1540 OPTIONAL, -- Need M + nonCriticalExtension RRcReconfiguration-v1560-IEs OPTIONAL +} + +RRcReconfiguration-v1560-IEs ::= SEQUENCE { + mrdc-SecondaryCellGroupConfig SetupRelease { MRDC-SecondaryCellGroupConfig } OPTIONAL, -- Need M + radioBearerConfig2 OCTET STRING (CONTAINING RadioBearerConfig) OPTIONAL, -- Need M + sk-Counter SK-Counter OPTIONAL, -- Need N + nonCriticalExtension RRcReconfiguration-v1610-IEs OPTIONAL +} + +RRcReconfiguration-v1610-IEs ::= SEQUENCE { + otherConfig-v1610 OtherConfig-v1610 OPTIONAL, -- Need M + bap-Config-r16 SetupRelease { BAP-Config-r16 } OPTIONAL, -- Need M + iab-IP-AddressConfigurationList-r16 IAB-IP-AddressConfigurationList-r16 OPTIONAL, -- Need M + conditionalReconfiguration-r16 ConditionalReconfiguration-r16 OPTIONAL, -- Need M + daps-SourceRelease-r16 ENUMERATED{true} OPTIONAL, -- Need N + t316-r16 SetupRelease { T316-r16 } OPTIONAL, -- Need M + needForGapsConfigNR-r16 SetupRelease { NeedForGapsConfigNR-r16 } OPTIONAL, -- Need M + onDemandSIB-Request-r16 SetupRelease { OnDemandSIB-Request-r16 } OPTIONAL, -- Need M + dedicatedPosSysInfoDelivery-r16 OCTET STRING (CONTAINING PosSystemInformation-r16-IEs) OPTIONAL, -- Need N + sl-ConfigDedicatedNR-r16 SetupRelease { SL-ConfigDedicatedNR-r16 } OPTIONAL, -- Need M + sl-ConfigDedicatedEUTRA-Info-r16 SetupRelease { SL-ConfigDedicatedEUTRA-Info-r16 } OPTIONAL, -- Need M + targetCellSMTC-SCG-r16 SSB-MTC OPTIONAL, -- Need S + nonCriticalExtension RRcReconfiguration-v1700-IEs OPTIONAL +} + +RRcReconfiguration-v1700-IEs ::= SEQUENCE { + +``` + +``` + + otherConfig-v1700 OtherConfig-v1700 OPTIONAL, -- Need M + sl-L2RelayUE-Config-r17 SetupRelease { SL-L2RelayUE-Config-r17 } OPTIONAL, -- Need M + sl-L2RemoteUE-Config-r17 SetupRelease { SL-L2RemoteUE-Config-r17 } OPTIONAL, -- Need M + dedicatedPagingDelivery-r17 OCTET STRING (CONTAINING Paging) OPTIONAL, -- Cond PagingRelay + needForGapNCSG-ConfigNR-r17 SetupRelease { NeedForGapNCSG-ConfigNR-r17 } OPTIONAL, -- Need M + needForGapNCSG-ConfigEUTRA-r17 SetupRelease { NeedForGapNCSG-ConfigEUTRA-r17 } OPTIONAL, -- Need M + musim-GapConfig-r17 SetupRelease { MUSIM-GapConfig-r17 } OPTIONAL, -- Need M + ul-GapFR2-Config-r17 SetupRelease { UL-GapFR2-Config-r17 } OPTIONAL, -- Need M + scg-State-r17 ENUMERATED { deactivated } OPTIONAL, -- Need N + appLayerMeasConfig-r17 AppLayerMeasConfig-r17 OPTIONAL, -- Need M + ue-TxTEG-RequestUL-TDOA-Config-r17 SetupRelease { UE-TxTEG-RequestUL-TDOA-Config-r17 } OPTIONAL, -- Need M + nonCriticalExtension RRCReconfiguration-v1800-IEs OPTIONAL +} + +RRCReconfiguration-v1800-IEs ::= SEQUENCE { + needForInterruptionConfigNR-r18 ENUMERATED { enabled, disabled } OPTIONAL, -- Need M + uav-Config-r18 SetupRelease { UAV-Config-r18 } OPTIONAL, -- Need M + sl-IndirectPathAddChange-r18 SetupRelease { SL-IndirectPathAddChange-r18 } OPTIONAL, -- Need M + n3c-IndirectPathAddChange-r18 SetupRelease { N3C-IndirectPathAddChange-r18 } OPTIONAL, -- Need M + n3c-IndirectPathConfigRelay-r18 SetupRelease { N3C-IndirectPathConfigRelay-r18 } OPTIONAL, -- Need M + otherConfig-v1800 OtherConfig-v1800 OPTIONAL, -- Need M + srs-PosResourceSetLinkedForAggBWList-r18 SetupRelease { SRS-PosResourceSetLinkedForAggBWList-r18 } OPTIONAL, -- Need M + ltm-Config-r18 SetupRelease { LTM-Config-r18 } OPTIONAL, -- Need M + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +MRDC-SecondaryCellGroupConfig ::= SEQUENCE { + mrdc-ReleaseAndAdd ENUMERATED { true } OPTIONAL, -- Need N + +``` + +``` + +mrdc-SecondaryCellGroup CHOICE { + nr-SCG OCTET STRING (CONTAINING RRCReconfiguration), + eutra-SCG OCTET STRING +} + +BAP-Config-r16 ::= SEQUENCE { + bap-Address-r16 BIT STRING (SIZE (10)) OPTIONAL, -- Need M + defaultUL-BAP-RoutingID-r16 BAP-RoutingID-r16 OPTIONAL, -- Need M + defaultUL-BH-RLC-Channel-r16 BH-RLC-ChannelID-r16 OPTIONAL, -- Need M + flowControlFeedbackType-r16 ENUMERATED {perBH-RLC-Channel, perRoutingID, both} OPTIONAL, -- Need R + ... +} + +MasterKeyUpdate ::= SEQUENCE { + keySetChangeIndicator BOOLEAN, + nextHopChainingCount NextHopChainingCount, + nas-Container OCTET STRING OPTIONAL, -- Cond securityNASC + ... +} + +OnDemandSIB-Request-r16 ::= SEQUENCE { + onDemandSIB-RequestProhibitTimer-r16 ENUMERATED {s0, s0dot5, s1, s2, s5, s10, s20, s30} +} + +T316-r16 ::= ENUMERATED {ms50, ms100, ms200, ms300, ms400, ms500, ms600, ms1000, ms1500, ms2000} + +IAB-IP-AddressConfigurationList-r16 ::= SEQUENCE { + iab-IP-AddressToAddModList-r16 SEQUENCE (SIZE(1..maxIAB-IP-Address-r16)) OF IAB-IP-AddressConfiguration-r16 OPTIONAL, -- Need N + iab-IP-AddressToReleaseList-r16 SEQUENCE (SIZE(1..maxIAB-IP-Address-r16)) OF IAB-IP-AddressIndex-r16 OPTIONAL, -- Need N + ... +} + +IAB-IP-AddressConfiguration-r16 ::= SEQUENCE { + iab-IP-AddressIndex-r16 IAB-IP-AddressIndex-r16, + iab-IP-Address-r16 IAB-IP-Address-r16 OPTIONAL, -- Need M + iab-IP-Usage-r16 IAB-IP-Usage-r16 OPTIONAL, -- Need M + iab-donor-DU-BAP-Address-r16 BIT STRING (SIZE(10)) OPTIONAL, -- Need M + ... +} + +SL-ConfigDedicatedEUTRA-Info-r16 ::= SEQUENCE { + sl-ConfigDedicatedEUTRA-r16 OCTET STRING OPTIONAL, -- Need M + sl-TimeOffsetEUTRA-List-r16 SEQUENCE (SIZE (8)) OF SL-TimeOffsetEUTRA-r16 OPTIONAL -- Need M +} + +SL-TimeOffsetEUTRA-r16 ::= ENUMERATED {ms0, ms0dot25, ms0dot5, ms0dot625, ms0dot75, ms1, ms1dot25, ms1dot5, ms1dot75, ms2, ms2dot5, ms3, ms4, ms5, ms6, ms8, ms10, ms20} + +UE-TxTEG-RequestUL-TDOA-Config-r17 ::= CHOICE { + oneShot-r17 NULL, +} + +``` + +``` + periodicReporting-r17 ENUMERATED { ms160, ms320, ms1280, ms2560, ms61440, ms81920, ms368640, ms737280 } +} + +SRS-PosResourceSetLinkedForAggBWList-r18 ::= SEQUENCE (SIZE(1..maxNrOfLinkedSRS-PosResourceSet-r18)) OF SRS-PosResourceSetLinkedForAggBW-r18 + +-- TAG-RRCRECONFIGURATION-STOP +-- ASN1STOP +``` + +Editor's Note: FFS whether/how to indicate PC5 release/maintain for indirect path add/modify/release. And for indirect path release, FFS whether to include an explicit "directPathRelease" flag in the reconfiguration procedure so that the UE can apply a simpler behaviour. + +| RRCREconfiguration-IEs field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| appLayerMeasConfig
This field is used to configure application layer measurements. This field is absent when the UE is configured to operate with shared spectrum channel access or if sl-L2RemoteUE-Config-r17 is configured or not released. | +| bap-Config
This field is used to configure the BAP entity for IAB nodes. | +| bap-Address
Indicates the BAP address of an IAB-node. The BAP address of an IAB-node cannot be changed once configured for the cell group to the BAP entity. | +| conditionalReconfiguration
Configuration of candidate target SpCell(s) and execution condition(s) for conditional handover, conditional PSCell addition or conditional PSCell change. The field is absent if any DAPS bearer is configured or if the masterCellGroup includes ReconfigurationWithSync or if the sl-L2RemoteUE-Config or sl-L2RelayUE-Config is configured. For conditional PSCell change, the field is absent if the secondaryCellGroup includes ReconfigurationWithSync . The RRCREconfiguration message contained in DLInformationTransferMRDC cannot contain the field conditionalReconfiguration for conditional PSCell change or for conditional PSCell addition. | +| daps-SourceRelease
Indicates to UE that the source cell part of DAPS operation is to be stopped and the source cell part of DAPS configuration is to be released. | +| dedicatedNAS-MessageList
This field is used to transfer UE specific NAS layer information between the network and the UE. The RRC layer is transparent for each PDU in the list. | +| dedicatedPagingDelivery
This field is used to transfer Paging message for the associated L2 U2N Remote UE to the L2 U2N Relay UE in RRc_CONNECTED . | +| dedicatedPosSysInfoDelivery
This field is used to transfer SIBPos to the UE in RRc_CONNECTED . | +| dedicatedSIB1-Delivery
This field is used to transfer SIB1 to the UE (including L2 U2N Remote UE). The field has the same values as the corresponding configuration in servingCellConfigCommon . | +| dedicatedSystemInformationDelivery
This field is used to transfer SIB6 , SIB7 , SIB8 , SIB19 , SIB20 , SIB21 , SIB25 to the UE with an active BWP with no common search space configured or the L2 U2N Remote UE in RRc_CONNECTED . For UEs in RRc_CONNECTED (including L2 U2N Remote UE), this field is also used to transfer the SIBs requested on-demand. | +| defaultUL-BAP-RoutingID
This field is used for IAB-node to configure the default uplink Routing ID, which is used by IAB-node during IAB-node bootstrapping, migration, IAB-MT RRC resume and IAB-MT RRC re-establishment for F1-C and non-F1 traffic. The defaultUL-BAP-RoutingID can be (re-)configured when IAB-node IP address for F1-C related traffic changes. This field is mandatory only for IAB-node bootstrapping. | +| defaultUL-BH-RLC-Channel
This field is used for IAB-nodes to configure the default uplink BH RLC channel, which is used by IAB-node during IAB-node bootstrapping, migration, IAB-MT RRC resume and IAB-MT RRC re-establishment for F1-C and non-F1 traffic. The defaultUL-BH-RLC-Channel can be (re-)configured when IAB-node IP address for F1-C related traffic changes, and the new IP address is anchored at a different IAB-donor-DU. This field is mandatory for IAB-node bootstrapping. If the IAB-MT is operating in EN-DC, the default uplink BH RLC channel is referring to an RLC channel on the SCG; Otherwise, it is referring to an RLC channel either on the MCG or on the SCG depending on whether the MN or the SN configures this field. | +| flowControlFeedbackType
This field is only used for IAB-node that support hop-by-hop flow control to configure the type of flow control feedback. Value perBH-RLC-Channel indicates that the IAB-node shall provide flow control feedback per BH RLC channel, value perRoutingID indicates that the IAB-node shall provide flow control feedback per routing ID, and value both indicates that the IAB-node shall provide flow control feedback both per BH RLC channel and per routing ID. | +| fullConfig
Indicates that the full configuration option is applicable for the RRCREconfiguration message for intra-system intra-RAT HO. For inter-RAT HO from E-UTRA to NR, fullConfig indicates whether or not delta signalling of SDAP/PDCP from source RAT is applicable. This field is absent if any DAPS bearer is configured or when the RRCREconfiguration message is transmitted on SRB3, and in an RRCREconfiguration message for SCG contained in another RRCREconfiguration message (or RRRConnectionReconfiguration | + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| message, see TS 36.331 [10]) transmitted on SRB1. | +| iab-IP-Address
This field is used to provide the IP address information for IAB-node. | +| iab-IP-AddressIndex
This field is used to identify a configuration of an IP address. | +| iab-IP-AddressToAddModList
List of IP addresses allocated for IAB-node to be added and modified. | +| iab-IP-AddressToReleaseList
List of IP address allocated for IAB-node to be released. | +| iab-IP-Usage
This field is used to indicate the usage of the assigned IP address. If this field is not configured, the assigned IP address is used for all traffic. | +| iab-donor-DU-BAP-Address
This field is used to indicate the BAP address of the IAB-donor-DU where the IP address is anchored. | +| keySetChangeIndicator
Indicates whether UE shall derive a new $K_{gNB}$ . If reconfigurationWithSync is included, value true indicates that a $K_{gNB}$ key is derived from a $K_{AMF}$ key taken into use through the latest successful NAS SMC procedure, or N2 handover procedure with $K_{AMF}$ change, as described in TS 33.501 [11] for $K_{gNB}$ re-keying. Value false indicates that the new $K_{gNB}$ key is obtained from the current $K_{gNB}$ key or from the NH as described in TS 33.501 [11]. | +| ltm-Config
This field includes the configuration related to LTM. | +| masterCellGroup
Configuration of master cell group. | +| mrdc-ReleaseAndAdd
This field indicates that the current SCG configuration is released and a new SCG is added at the same time. | +| mrdc-SecondaryCellGroup
Includes an RRC message for SCG configuration in NR-DC or NE-DC.
For NR-DC (nr-SCG), mrdc-SecondaryCellGroup contains the RRReconfiguration message as generated (entirely) by SN gNB. In this version of the specification, the RRC message can only include fields secondaryCellGroup , otherConfig , conditionalReconfiguration , ltm-Config , measConfig , bap-Config , IAB-IP-AddressConfigurationList and appLayerMeasConfig .
For NE-DC (eutra-SCG), mrdc-SecondaryCellGroup includes the E-UTRA RRConnectionReconfiguration message as specified in TS 36.331 [10]. In this version of the specification, the E-UTRA RRC message can only include the field scg-Configuration . | +| mrdc-SecondaryCellGroupConfig
This field is used to configure and release an SCG in NR-DC and NE-DC. In case the RRReconfiguration message is part of an LTM-Candidate IE associated with the MCG, if this field is present its value can only be set to release . | +| musim-GapConfig
Indicates the MUSIM gap configuration and controls setup/release of MUSIM gaps. In this version of the specification, the network does not configure MUSIM gap together with concurrent measurement gap or preconfigured measurement gap for positioning. | +| nas-Container
This field is used to transfer UE specific NAS layer information between the network and the UE. The RRC layer is transparent for this field, although it affects activation of AS security after inter-system handover to NR. The content is defined in TS 24.501 [23]. | +| needForGapsConfigNR
Configuration for the UE to report measurement gap requirement information of NR target bands in the RRReconfigurationComplete and RRResumeComplete message. | +| needForGapNCSG-ConfigEUTRA
Configuration for the UE to report measurement gap and NCSG requirement information of E-UTRA target bands in the RRReconfigurationComplete and RRResumeComplete message. | + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| needForGapNCSG-ConfigNR
Configuration for the UE to report measurement gap and NCSG requirement information of NR target bands in the RRCReconfigurationComplete and RRCResumeComplete message. | +| needForInterruptionConfigNR
Indicates whether the UE shall report interruption requirement information of NR target bands in the RRCReconfigurationComplete and RRCResumeComplete message. The network sets this field to enabled only if the needForGapsConfigNR is configured. The network sets this field to disabled if the needForGapsConfigNR is released. | +| nextHopChainingCount
Parameter NCC: See TS 33.501 [11] | +| onDemandSIB-Request
If the field is present, the UE is allowed to request SIB(s) on-demand while in RRC_CONNECTED according to clause 5.2.2.3.5. | +| onDemandSIB-RequestProhibitTimer
Prohibit timer for requesting SIB(s) on-demand while in RRC_CONNECTED according to clause 5.2.2.3.5. Value in seconds. Value s0 means prohibit timer is set to 0 seconds, value s0dot5 means prohibit timer is set to 0.5 seconds, value s1 means prohibit timer is set to 1 second and so on. | +| otherConfig
Contains configuration related to other configurations. When configured for the SCG, only fields drx-PreferenceConfig , maxBW-PreferenceConfig , maxBW-PreferenceConfigFR2-2 , maxCC-PreferenceConfig , maxMIMO-LayerPreferenceConfig , maxMIMO-LayerPreferenceConfigFR2-2 , minSchedulingOffsetPreferenceConfig , minSchedulingOffsetPreferenceConfigExt , rlm-RelaxationReportingConfig , bfd-RelaxationReportingConfig , btNameList , wlanNameList , sensorNameList , obtainCommonLocation and uav-FlightPathAvailabilityConfig can be included. | +| radioBearerConfig
Configuration of Radio Bearers (DRBs, SRBs, multicast MRBs) including SDAP/PDCP. In (NG)EN-DC this field may only be present if the RRCReconfiguration is transmitted over SRB3. SRB4 should not be configured if sl-L2RemoteUE-Config-r17 is configured or not released. | +| radioBearerConfig2
Configuration of Radio Bearers (DRBs, SRBs) including SDAP/PDCP. This field can only be used if the UE supports NR-DC or NE-DC. | +| scg-State
Indicates that the SCG is in deactivated state.
This field is not used
  • - in an RRCReconfiguration message received:
    • - within mrdc-SecondaryCellGroup, or
    • - in an E-UTRA RRCConnectionReconfiguration message, or
    • - in an E-UTRA RRCConnectionResume message or
  • - in an RRCReconfiguration message received via SRB3, except if the RRCReconfiguration message is included in DLInformationTransferMRDC.
The field is absent if CPA or CPC is configured for the UE, or if the RRCReconfiguration message is contained in CondRRCReconfig , or PSCell is configured with tag2 . | +| sl-L2RelayUE-Config
Contains L2 U2N relay operation related configurations used by a UE acting as or to be acting as a L2 U2N Relay UE or L2 U2U relay operation related configuration used by a UE acting as a L2 U2U Relay UE. In case of L2 U2N relay operation, the field is absent if conditionalReconfiguration is configured for CHO. | +| sl-L2RemoteUE-Config
Contains L2 U2N relay operation related configurations used by a UE acting as or to be acting as a L2 U2N Remote UE or L2 U2U relay operation related configuration used by a UE acting as a L2 U2U Remote UE. In case of L2 U2N relay operation, the field is absent if conditionalReconfiguration is configured for CHO, or if appLayerMeasConfig or SRB4 is configured/not released. | +| secondaryCellGroup
Configuration of secondary cell group ((NG)EN-DC or NR-DC). | +| sk-Counter
A counter used upon initial configuration of $S-K_{gNB}$ or $S-K_{eNB}$ , as well as upon refresh of $S-K_{gNB}$ or $S-K_{eNB}$ . This field is always included either upon initial configuration of an NR SCG or upon configuration of the first RB with keyToUse set to secondary , whichever happens first. This field is absent if there is neither any NR SCG nor any RB with | + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| keyToUse set to secondary . | +| sl-ConfigDedicatedNR
This field is used to provide the dedicated configurations for NR sidelink communication/discovery/positioning. | +| sl-ConfigDedicatedEUTRA-Info
This field includes the E-UTRA RRConnectionReconfiguration as specified in TS 36.331 [10]. In this version of the specification, the E-UTRA RRConnectionReconfiguration can only includes sidelink related fields for V2X sidelink communication, i.e. sl-V2X-ConfigDedicated , sl-V2X-SPS-Config , measConfig and/or otherConfig . | +| srs-PosResourceSetLinkedForAggBWList
This field indicates the SRS resource sets across carriers which are linked for SRS bandwidth aggregation in RRC_CONNECTED state as defined in clause 6.2.1.4 of TS 38.214 [19]. | +| sl-TimeOffsetEUTRA
This field indicates the possible time offset to (de)activation of V2X sidelink transmission after receiving DCI format 3_1 used for scheduling V2X sidelink communication. Value ms0dpt75 corresponds to 0.75ms, ms1 corresponds to 1ms and so on. The network includes this field only when sl-ConfigDedicatedEUTRA is configured. | +| targetCellSMTC-SCG
The SSB periodicity/offset/duration configuration of target cell for NR PSCell addition and SN change. When UE receives this field, UE applies the configuration based on the timing reference of NR PCell for PSCell addition and PSCell change for the case of no reconfiguration with sync of MCG, and UE applies the configuration based on the timing reference of target NR PCell for the case of reconfiguration with sync of MCG. If both this field and the smtc in secondaryCellGroup -> SpCellConfig -> reconfigurationWithSync are absent, the UE uses the SMTC in the measObjectNR having the same SSB frequency and subcarrier spacing, as configured before the reception of the RRC message. | +| t316
Indicates the value for timer T316 as described in clause 7.1. Value ms50 corresponds to 50 ms, value ms100 corresponds to 100 ms and so on. This field can be configured only if the UE is configured with split SRB1 or SRB3. | +| ue-TxTEG-RequestUL-TDOA-Config
Configures the periodicity of UE reporting for the association between Tx TEG and SRS Positioning resources. When configured with oneShot UE reports the association only one time. When configured with periodicReporting UE reports the association periodically and the periodicReporting indicates the periodicity. Value ms160 corresponds to 160ms, value ms320 corresponds to 320ms and so on. | +| ul-GapFR2-Config
Indicates the FR2 UL gap configuration to UE. In EN-DC and NGEN-DC, the SN decides and configures the FR2 UL gap pattern. In NE-DC, the MN decides and configures the FR2 UL gap pattern. In NR-DC without FR2-FR2 band combination, the network entity which is configured with FR2 serving cell(s) decides and configures the FR2 UL gap pattern. | + +| Conditional Presence | Explanation | +|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| nonHO | The field is absent in case of reconfiguration with sync within NR or to NR; otherwise it is optionally present, need N. | +| securityNASC | This field is mandatory present in case of inter system handover. Otherwise the field is optionally present, need N. | +| MasterKeyChange | This field is mandatory present in case masterCellGroup includes ReconfigurationWithSync and RadioBearerConfig includes SecurityConfig with SecurityAlgorithmConfig , indicating a change of the AS security algorithms associated to the master key. If ReconfigurationWithSync is included for other cases, this field is optionally present, need N. If ReconfigurationWithSync is part of an LTM-Candidate IE associated with the MCG, the field is absent. Otherwise the field is absent. | +| FullConfig | The field is mandatory present in case of inter-system handover from E-UTRA/EPC to NR. It is optionally present, Need N, during a reconfiguration with sync which is not related to an LTM cell switch or subsequent CPAC, and also in first reconfiguration after reestablishment; or for intra-system handover from E-UTRA/5GC to NR. It is absent otherwise. | +| SCG |

The field is mandatory present in:

  • - an RRCReconfiguration message contained in an RRCResume message (or in an RRConnectionResume message, see TS 36.331 [10]),
  • - an RRCReconfiguration message contained in an RRConnectionReconfiguration message, see TS 36.331 [10], which is contained in DLInformationTransferMRDC transmitted on SRB3 (as a response to ULInformationTransferMRDC including an MCGFailureInformation).

The field is optional present, Need M, in:

  • - an RRCReconfiguration message transmitted on SRB3,
  • - an RRCReconfiguration message contained in another RRCReconfiguration message (or in an RRConnectionReconfiguration message, see TS 36.331 [10]) transmitted on SRB1
  • - an RRCReconfiguration message contained in another RRCReconfiguration message which is contained in DLInformationTransferMRDC transmitted on SRB3 (as a response to ULInformationTransferMRDC including an MCGFailureInformation).

Otherwise, the field is absent.

| +| PagingRelay | For L2 U2N Relay UE, the field is optionally present, Need N. Otherwise, it is absent. | + +###### — *RRCReconfigurationComplete* + +The *RRCReconfigurationComplete* message is used to confirm the successful completion of an RRC connection reconfiguration. + +Signalling radio bearer: SRB1 or SRB3 + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: UE to Network + +#### ***RRCReconfigurationComplete message*** + +``` +-- ASN1START +-- TAG-RRCRECONFIGURATIONCOMPLETE-START +``` + +``` + +RRReconfigurationComplete ::= SEQUENCE { + rrc-TransactionIdentifier RRC-TransactionIdentifier, + criticalExtensions CHOICE { + rrcReconfigurationComplete + criticalExtensionsFuture + } +} + +RRReconfigurationComplete-IEs ::= SEQUENCE { + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension RRReconfigurationComplete-v1530-IEs +} + +RRReconfigurationComplete-v1530-IEs ::= SEQUENCE { + uplinkTxDirectCurrentList UplinkTxDirectCurrentList OPTIONAL, + nonCriticalExtension RRReconfigurationComplete-v1560-IEs +} + +RRReconfigurationComplete-v1560-IEs ::= SEQUENCE { + scg-Response CHOICE { + nr-SCG-Response OCTET STRING (CONTAINING RRReconfigurationComplete), + eutra-SCG-Response OCTET STRING + } + nonCriticalExtension RRReconfigurationComplete-v1610-IEs +} + +RRReconfigurationComplete-v1610-IEs ::= SEQUENCE { + ue-MeasurementsAvailable-r16 UE-MeasurementsAvailable-r16 OPTIONAL, + needForGapsInfoNR-r16 NeedForGapsInfoNR-r16 OPTIONAL, + nonCriticalExtension RRReconfigurationComplete-v1640-IEs +} + +RRReconfigurationComplete-v1640-IEs ::= SEQUENCE { + uplinkTxDirectCurrentTwoCarrierList-r16 UplinkTxDirectCurrentTwoCarrierList-r16 + nonCriticalExtension RRReconfigurationComplete-v1700-IEs +} + +RRReconfigurationComplete-v1700-IEs ::= SEQUENCE { + needForGapNCSG-InfoNR-r17 NeedForGapNCSG-InfoNR-r17 OPTIONAL, + needForGapNCSG-InfoEUTRA-r17 NeedForGapNCSG-InfoEUTRA-r17 OPTIONAL, + selectedCondRRReconfig-r17 CondReconfigId-r16 OPTIONAL, + nonCriticalExtension RRReconfigurationComplete-v1720-IEs +} + +RRReconfigurationComplete-v1720-IEs ::= SEQUENCE { + uplinkTxDirectCurrentMoreCarrierList-r17 UplinkTxDirectCurrentMoreCarrierList-r17 + nonCriticalExtension RRReconfigurationComplete-v1800-IEs +} + +RRReconfigurationComplete-v1800-IEs ::= SEQUENCE { + needForInterruptionInfoNR-r18 NeedForInterruptionInfoNR-r18 +} + +``` + +``` + +flightPathInfoAvailable-r18 ENUMERATED {true} OPTIONAL, +selectedPSCellForCHO-WithSCG-r18 SelectedPSCellForCHO-WithSCG-r18 OPTIONAL, +selectedSK-Counter-r18 SK-Counter OPTIONAL, +nonCriticalExtension SEQUENCE {} OPTIONAL +} + +-- TAG-RRCRECONFIGURATIONCOMPLETE-STOP +-- ASN1STOP + +``` + +| RRCREconfigurationComplete-IEs field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| needForGapsInfoNR
This field is used to indicate the measurement gap requirement information of the UE for NR target bands. | +| needForGapNCSG-InfoEUTRA
This field is used to indicate the measurement gap and NCSG requirement information of the UE for E-UTRA target bands. | +| needForGapNCSG-InfoNR
This field is used to indicate the measurement gap and NCSG requirement information of the UE for NR target bands. | +| needForInterruptionInfoNR
This field indicates whether interruption is needed while performing measurement on NR target bands without measurement gap. | +| scg-Response
In case of NR-DC ( nr-SCG-Response ), this field includes the RRCREconfigurationComplete message. In case of NE-DC ( eutra-SCG-Response ), this field includes the E-UTRA RRCConnectionReconfigurationComplete message as specified in TS 36.331 [10]. | +| selectedCondRRRReconfig
This field indicates the ID of the selected conditional reconfiguration the UE applied upon the execution of CPA or inter-SN CPC. | +| selectedPSCellForCHO-WithSCG
This field indicates the information of the selected target PSCell to target MN at execution of a conditional reconfiguration for CHO with candidate SCG(s). | +| selectedSK-Counter
This field includes the selected sk-counter value for security key update upon the execution of subsequent CPAC. | +| uplinkTxDirectCurrentList
The Tx Direct Current locations for the configured serving cells and BWPs if requested by the NW (see reportUplinkTxDirectCurrent in CellGroupConfig ). | +| uplinkTxDirectCurrentMoreCarrierList
The Tx Direct Current locations for the configured intra-band CA requested by reportUplinkTxDirectCurrentMoreCarrier-r17 . | +| uplinkTxDirectCurrentTwoCarrierList
The Tx Direct Current locations for the configured uplink intra-band CA with two carriers if requested by the NW (see reportUplinkTxDirectCurrentTwoCarrier-r16 in CellGroupConfig ). | + +###### — ***RRCREject*** + +The *RRCREject* message is used to reject an RRC connection establishment or an RRC connection resumption. + +Signalling radio bearer: SRB0 + +RLC-SAP: TM + +Logical channel: CCCH + +Direction: Network to UE + +#### ***RRReject message*** + +``` + +-- ASN1START +-- TAG-RRREJECT-START + +RRReject := + SEQUENCE { + criticalExtensions + CHOICE { + rrcReject + RRCReject-IEs, + criticalExtensionsFuture + SEQUENCE {} + } + } + +RRCReject-IEs := + SEQUENCE { + waitTime + RejectWaitTime + OPTIONAL, -- Need N + lateNonCriticalExtension + OCTET STRING + OPTIONAL, + nonCriticalExtension + SEQUENCE {} + OPTIONAL + } + +-- TAG-RRREJECT-STOP +-- ASN1STOP + +``` + +| RRCReject-IEs field descriptions | +|-------------------------------------------------------------------------------------| +| waitTime
Wait time value in seconds. The field is always included. | + +###### — ***RRRelease*** + +The *RRRelease* message is used to command the release of an RRC connection or the suspension of the RRC connection. + +Signalling radio bearer: SRB1 + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: Network to UE + +#### ***RRRelease message*** + +``` + +-- ASN1START +-- TAG-RRRELEASE-START + +``` + +``` + +RRRelease ::= SEQUENCE { + rrc-TransactionIdentifier RRC-TransactionIdentifier, + criticalExtensions CHOICE { + rrcRelease RRCRelease-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +RRRelease-IEs ::= SEQUENCE { + redirectedCarrierInfo RedirectedCarrierInfo OPTIONAL, -- Need N + cellReselectionPriorities CellReselectionPriorities OPTIONAL, -- Need R + suspendConfig SuspendConfig OPTIONAL, -- Need R + deprioritisationReq SEQUENCE { + deprioritisationType ENUMERATED {frequency, nr}, + deprioritisationTimer ENUMERATED {min5, min10, min15, min30} + } + lateNonCriticalExtension OCTET STRING OPTIONAL, -- Need N + nonCriticalExtension RRCRelease-v1540-IEs OPTIONAL, +} + +RRRelease-v1540-IEs ::= SEQUENCE { + waitTime RejectWaitTime OPTIONAL, -- Need N + nonCriticalExtension RRCRelease-v1610-IEs OPTIONAL +} + +RRRelease-v1610-IEs ::= SEQUENCE { + voiceFallbackIndication-r16 ENUMERATED {true} OPTIONAL, -- Need N + measIdleConfig-r16 SetupRelease {MeasIdleConfigDedicated-r16} OPTIONAL, -- Need M + nonCriticalExtension RRCRelease-v1650-IEs OPTIONAL +} + +RRRelease-v1650-IEs ::= SEQUENCE { + mpsPriorityIndication-r16 ENUMERATED {true} OPTIONAL, -- Cond Redirection2 + nonCriticalExtension RRCRelease-v1710-IEs OPTIONAL +} + +RRRelease-v1710-IEs ::= SEQUENCE { + noLastCellUpdate-r17 ENUMERATED {true} OPTIONAL, -- Need S + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +RedirectedCarrierInfo ::= CHOICE { + nr CarrierInfoNR, + eutra RedirectedCarrierInfo-EUTRA, + ... +} + +RedirectedCarrierInfo-EUTRA ::= SEQUENCE { + eutraFrequency ARFCN-ValueEUTRA, + cnType ENUMERATED {epc,fiveGC} OPTIONAL -- Need N +} + +``` + +``` + +} + +CarrierInfoNR ::= SEQUENCE { + carrierFreq ARFCN-ValueNR, + ssbSubcarrierSpacing SubcarrierSpacing, + smtc SSB-MTC + ... +} + +SuspendConfig ::= SEQUENCE { + fullI-RNTI I-RNTI-Value, + shortI-RNTI ShortI-RNTI-Value, + ran-PagingCycle PagingCycle, + ran-NotificationAreaInfo RAN-NotificationAreaInfo + t380 PeriodicRNAU-TimerValue + nextHopChainingCount NextHopChainingCount, + ... + [[ + sl-UEIdentityRemote-r17 RNTI-Value + sdt-Config-r17 SetupRelease { SDT-Config-r17 } + srs-PosRRC-Inactive-r17 SetupRelease { SRS-PosRRC-Inactive-r17 } + ran-ExtendedPagingCycle-r17 ExtendedPagingCycle-r17 + ]], + [[ + ncd-SSB-RedCapInitialBWP-SDT-r17 SetupRelease { NonCellDefiningSSB-r17 } + ]], + [[ + resumeIndication-r18 ENUMERATED { true } + srs-PosRRC-Inactive-v1800 SetupRelease { SRS-PosRRC-Inactive-v1800 } + srs-PosRRC-InactiveValidityAreaConfigList-r18 SetupRelease { SRS-PosRRC-InactiveValidityAreaConfigList-r18 } + ran-ExtendedPagingCycle-r18 ExtendedPagingCycle-Config-r18 + multicastConfigInactive-r18 SetupRelease { MulticastConfigInactive-r18 } + ]] +} + +PeriodicRNAU-TimerValue ::= ENUMERATED { min5, min10, min20, min30, min60, min120, min360, min720 } + +CellReselectionPriorities ::= SEQUENCE { + freqPriorityListEUTRA FreqPriorityListEUTRA + freqPriorityListNR FreqPriorityListNR + t320 ENUMERATED { min5, min10, min20, min30, min60, min120, min180, spare1 } + ... + [[ + freqPriorityListDedicatedSlicing-r17 FreqPriorityListDedicatedSlicing-r17 + ]] +} + +PagingCycle ::= ENUMERATED { rf32, rf64, rf128, rf256 } + +FreqPriorityListEUTRA ::= SEQUENCE (SIZE (1..maxFreq)) OF FreqPriorityEUTRA + +``` + +``` + +FreqPriorityListNR := SEQUENCE (SIZE (1..maxFreq)) OF FreqPriorityNR + +FreqPriorityEUTRA := SEQUENCE { + carrierFreq ARFCN-ValueEUTRA, + cellReselectionPriority CellReselectionPriority, + cellReselectionSubPriority CellReselectionSubPriority +} OPTIONAL -- Need R + +FreqPriorityNR := SEQUENCE { + carrierFreq ARFCN-ValueNR, + cellReselectionPriority CellReselectionPriority, + cellReselectionSubPriority CellReselectionSubPriority +} OPTIONAL -- Need R + +RAN-NotificationAreaInfo := CHOICE { + cellList PLMN-RAN-AreaCellList, + ran-AreaConfigList PLMN-RAN-AreaConfigList, + ... +} + +PLMN-RAN-AreaCellList := SEQUENCE (SIZE (1.. maxPLMNIdentities)) OF PLMN-RAN-AreaCell + +PLMN-RAN-AreaCell := SEQUENCE { + plmn-Identity PLMN-Identity + ran-AreaCells SEQUENCE (SIZE (1..32)) OF CellIdentity +} OPTIONAL, -- Need S + +PLMN-RAN-AreaConfigList := SEQUENCE (SIZE (1..maxPLMNIdentities)) OF PLMN-RAN-AreaConfig + +PLMN-RAN-AreaConfig := SEQUENCE { + plmn-Identity PLMN-Identity + ran-Area SEQUENCE (SIZE (1..16)) OF RAN-AreaConfig +} OPTIONAL, -- Need S + +RAN-AreaConfig := SEQUENCE { + trackingAreaCode TrackingAreaCode, + ran-AreaCodeList SEQUENCE (SIZE (1..32)) OF RAN-AreaCode +} OPTIONAL -- Need R + +SDT-Config-r17 := SEQUENCE { + sdt-DRB-List-r17 SEQUENCE (SIZE (0..maxDRB)) OF DRB-Identity + sdt-SRB2-Indication-r17 ENUMERATED {allowed} + sdt-MAC-PHY-CG-Config-r17 SetupRelease {SDT-CG-Config-r17} + sdt-DRB-ContinueROHC-r17 ENUMERATED { cell, rna } +} OPTIONAL, -- Need M +OPTIONAL, -- Need R +OPTIONAL, -- Need M +OPTIONAL, -- Need S + +SDT-CG-Config-r17 := OCTET STRING (CONTAINING SDT-MAC-PHY-CG-Config-r17) + +SDT-MAC-PHY-CG-Config-r17 := SEQUENCE { + -- CG-SDT specific configuration + cg-SDT-ConfigLCH-RestrictionToAddModList-r17 SEQUENCE (SIZE(1..maxLC-ID)) OF CG-SDT-ConfigLCH-Restriction-r17 OPTIONAL, -- Need N +} + +``` + +``` + +cg-SDT-ConfigLCH-RestrictionToReleaseList-r17 SEQUENCE (SIZE(1..maxLC-ID)) OF LogicalChannelIdentity OPTIONAL, -- Need N +cg-SDT-ConfigInitialBWP-NUL-r17 SetupRelease {BWP-UplinkDedicatedSDT-r17} OPTIONAL, -- Need M +cg-SDT-ConfigInitialBWP-SUL-r17 SetupRelease {BWP-UplinkDedicatedSDT-r17} OPTIONAL, -- Need M +cg-SDT-ConfigInitialBWP-DL-r17 BWP-DownlinkDedicatedSDT-r17 OPTIONAL, -- Need M +cg-SDT-TimeAlignmentTimer-r17 TimeAlignmentTimer OPTIONAL, -- Need M +cg-SDT-RSRP-ThresholdSSB-r17 RSRP-Range OPTIONAL, -- Need M +cg-SDT-TA-ValidationConfig-r17 SetupRelease { CG-SDT-TA-ValidationConfig-r17 } OPTIONAL, -- Need M +cg-SDT-CS-RNTI-r17 RNTI-Value OPTIONAL, -- Need M +... +[[ +cg-SDT-ConfigLCH-RestrictionToAddModListExt-v1800 SEQUENCE (SIZE(1..maxLC-ID)) OF CG-SDT-ConfigLCH-Restriction-v1800 +OPTIONAL, -- Need N +cg-MT-SDT-MaxDurationToNext-CG-Occasion-r18 ENUMERATED { +ms10, ms100, sec1, sec10, sec60, sec100, sec300, sec600, +sec1200, sec1800, sec3600, +spare5, spare4, spare3, spare2, spare1} +OPTIONAL -- Need R +]] +} + +CG-SDT-TA-ValidationConfig-r17 ::= SEQUENCE { +cg-SDT-RSRP-ChangeThreshold-r17 ENUMERATED { dB2, dB4, dB6, dB8, dB10, dB14, dB18, dB22, +dB26, dB30, dB34, spare5, spare4, spare3, spare2, spare1} +} + +BWP-DownlinkDedicatedSDT-r17 ::= SEQUENCE { +pdcch-Config-r17 SetupRelease { PDCCH-Config } OPTIONAL, -- Need M +pdsch-Config-r17 SetupRelease { PDSCH-Config } OPTIONAL, -- Need M +... +} + +BWP-UplinkDedicatedSDT-r17 ::= SEQUENCE { +pusch-Config-r17 SetupRelease { PUSCH-Config } OPTIONAL, -- Need M +configuredGrantConfigToAddModList-r17 ConfiguredGrantConfigToAddModList-r16 OPTIONAL, -- Need N +configuredGrantConfigToReleaseList-r17 ConfiguredGrantConfigToReleaseList-r16 OPTIONAL, -- Need N +... +} + +CG-SDT-ConfigLCH-Restriction-r17 ::= SEQUENCE { +logicalChannelIdentity-r17 LogicalChannelIdentity, +configuredGrantType1Allowed-r17 ENUMERATED {true} OPTIONAL, -- Need R +allowedCG-List-r17 SEQUENCE (SIZE (0.. maxNrofConfiguredGrantConfigMAC-1-r16)) OF ConfiguredGrantConfigIndexMAC-r16 +OPTIONAL -- Need R +} + +CG-SDT-ConfigLCH-Restriction-v1800 ::= SEQUENCE { +cg-SDT-MaxDurationToNext-CG-Occasion-r18 ENUMERATED { +ms10, ms100, sec1, sec10, sec60, sec100, sec300, sec600, +sec1200, sec1800, sec3600, +spare5, spare4, spare3, spare2, spare1} +OPTIONAL -- Need R +} + +``` + +``` + +SRS-PosRRC-Inactive-r17 ::= OCTET STRING (CONTAINING SRS-PosRRC-InactiveConfig-r17) + +SRS-PosRRC-InactiveConfig-r17 ::= SEQUENCE { + srs-PosConfigNUL-r17 SRS-PosConfig-r17 OPTIONAL, -- Need R + srs-PosConfigSUL-r17 SRS-PosConfig-r17 OPTIONAL, -- Need R + bwp-NUL-r17 BWP OPTIONAL, -- Need S + bwp-SUL-r17 BWP OPTIONAL, -- Need S + inactivePosSRS-TimeAlignmentTimer-r17 TimeAlignmentTimer OPTIONAL, -- Need M + inactivePosSRS-RSRP-ChangeThreshold-r17 RSRP-ChangeThreshold-r17 OPTIONAL -- Need M +} + +RSRP-ChangeThreshold-r17 ::= ENUMERATED {dB4, dB6, dB8, dB10, dB14, dB18, dB22, dB26, dB30, dB34, spare6, spare5, spare4, spare3, spare2, spare1} + +SRS-PosConfig-r17 ::= SEQUENCE { + srs-PosResourceSetToReleaseList-r17 SEQUENCE (SIZE(1..maxNrofSRS-PosResourceSets-r16)) OF SRS-PosResourceSetId-r16 OPTIONAL, -- Need N + srs-PosResourceSetToAddModList-r17 SEQUENCE (SIZE(1..maxNrofSRS-PosResourceSets-r16)) OF SRS-PosResourceSetId-r16 OPTIONAL, -- Need N + srs-PosResourceToReleaseList-r17 SEQUENCE (SIZE(1..maxNrofSRS-PosResources-r16)) OF SRS-PosResourceId-r16 OPTIONAL, -- Need N + srs-PosResourceToAddModList-r17 SEQUENCE (SIZE(1..maxNrofSRS-PosResources-r16)) OF SRS-PosResource-r16 OPTIONAL -- Need N +} + +SRS-PosRRC-Inactive-v1800 ::= SEQUENCE { + srs-PosRRC-AggBW-InactiveConfigList-r18 SetupRelease { SRS-PosRRC-AggBW-InactiveConfigList-r18 } OPTIONAL, -- Need M + srs-PosResSetLinkedForAggBWinactiveList-r18 SetupRelease { SRS-PosResSetLinkedForAggBWinactiveList-r18 } OPTIONAL, -- Need M + srs-PosTx-Hopping-r18 SetupRelease { SRS-PosTx-Hopping-r18 } OPTIONAL, -- Need M + ... +} + +SRS-PosRRC-InactiveValidityAreaConfigList-r18 ::= SEQUENCE SIZE(1..maxNrOfVA-r18) OF SRS-PosRRC-InactiveValidityAreaConfig-r18 + +SRS-PosRRC-InactiveValidityAreaConfig-r18 ::= SEQUENCE { + configType-r18 ENUMERATED {preconfig, non-preconfig}, + srs-PosConfigValidityArea-r18 SEQUENCE (SIZE(1..maxNrOfCellsInVA-r18)) OF CellIdentity, + srs-PosConfigNUL-r18 SRS-PosConfig-r17 OPTIONAL, -- Need R + srs-PosConfigSUL-r18 SRS-PosConfig-r17 OPTIONAL, -- Need R + bwp-NUL-r18 BWP OPTIONAL, -- Need S + bwp-SUL-r18 BWP OPTIONAL, -- Need S + areaValidityTA-Config-r18 SetupRelease { AreaValidityTA-Config-r18 } OPTIONAL, -- Need M + srs-PosRRC-AggBW-InactiveConfigList-r18 SetupRelease { SRS-PosRRC-AggBW-InactiveConfigList-r18 } OPTIONAL, -- Need M + srs-PosResSetLinkedForAggBWinactiveList-r18 SetupRelease { SRS-PosResSetLinkedForAggBWinactiveList-r18 } OPTIONAL, -- Need M + srs-PosHyperSFN-Index-r18 ENUMERATED {even0, odd1} OPTIONAL, --Need S + ... +} + +AreaValidityTA-Config-r18 ::= SEQUENCE { + inactivePosSRS-ValidityAreaTAT-r18 ENUMERATED {ms1280, ms1920, ms2560, ms5120, ms10240, ms20480, ms40960, infinity}, + inactivePosSRS-ValidityAreaRSRP-r18 RSRP-ChangeThreshold-r17 OPTIONAL, -- Need M + autonomousTA-AdjustmentEnabled-r18 ENUMERATED {true} OPTIONAL -- Need M +} + +-- Editor's Note: FFS on configType timer value and on optional need codes for area Validity TA Config + +SRS-PosResSetLinkedForAggBWinactiveList-r18 ::= SEQUENCE (SIZE(1..maxNrOfLinkedSRS-PosResourceSet-r18)) OF SRS-PosResourceSetLinkedForAggBW-r18 + +``` + +``` +SRS-PosRRC-AggBW-InactiveConfigList-r18 := SEQUENCE (SIZE (2..3)) OF SRS-PosRRC-AggBW-InactiveConfig-r18 + +SRS-PosRRC-AggBW-InactiveConfig-r18 := SEQUENCE { + srs-PosConfig-r18 SRS-PosConfig-r17, + freqInfoAdditionalCcList-r18 ARFCN-ValueNR +} + +ExtendedPagingCycle-r17 := ENUMERATED {rf256, rf512, rf1024, spare1} + +ExtendedPagingCycle-Config-r18 := SEQUENCE { + extendedPagingCycle-r18 ENUMERATED {hf2, hf4, hf8, hf16, hf32, hf64, hf128, hf256, hf512, hf1024, + spare6, spare5, spare4, spare3, spare2, spare1}, + pagingPTWLength-r18 ENUMERATED {ms1280, ms2560, ms3840, ms5120, ms6400, ms7680, ms8960, ms10240, ms11520, + ms12800, ms14080, ms15360, ms16640, ms17920, ms19200, ms20480, ms21760, + ms23040, ms24320, ms25600, ms26880, ms28160, ms29440, ms30720, ms32000, + ms33280, ms34560, ms35840, ms37120, ms38400, ms39680, ms40960} +} + +MulticastConfigInactive-r18 := SEQUENCE { + inactivePTM-Config-r18 OCTET STRING (CONTAINING MBSMulticastConfiguration-r18) OPTIONAL, -- Need N + inactiveMCCH-Config-r18 OCTET STRING (CONTAINING SystemInformation) OPTIONAL -- Need N +} + +-- TAG-RRCRELEASE-STOP +-- ASN1STOP +``` + +| RRRelease-IEs field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| cellReselectionPriorities
Dedicated priorities to be used for cell reselection as specified in TS 38.304 [20]. The maximum number of NR carrier frequencies that the network can configure through FreqPriorityListNR and FreqPriorityListDedicatedSlicing together is eight. If the same frequency is configured in both FreqPriorityListNR and FreqPriorityListDedicatedSlicing , the frequency is only counted once. | +| cnType
Indicate that the UE is redirected to EPC or 5GC. | +| deprioritisationReq
Indicates whether the current frequency or RAT is to be de-prioritised. | +| deprioritisationTimer
Indicates the period for which either the current carrier frequency or NR is deprioritised. Value minN corresponds to N minutes. | +| measIdleConfig
Indicates measurement configuration to be stored and used by the UE while in RRC_IDLE or RRC_INACTIVE. | +| mpsPriorityIndication
Indicates the UE can set the establishment cause to mps-PriorityAccess for a new connection following a redirect to NR or set the resume cause to mps-PriorityAccess for a resume following a redirect to NR. If the target RAT is E-UTRA, see TS 36.331 [10]. The gNB sets the indication only for UEs authorized to receive MPS treatment as indicated by ARP and/or QoS characteristics at the gNB, and it is applicable only for this instance of release with redirection to carrier/RAT included in the redirectedCarrierInfo field in the RRRelease message. | +| multicastConfigInactive
Indicates the multicast service(s) that can be received in RRC_INACTIVE in the current serving cell and optionally the corresponding configuration. The presence of this field indicates the UE is configured to receive MBS multicast in RRC_INACTIVE. | +| noLastCellUpdate
Presence of the field indicates that the last used cell for PEI shall not be updated. When the field is absent, the PEI-capable UE shall update its last used cell with the current cell. The UE shall not update its last used cell with the current cell if the AS security is not activated. | +| srs-PosRRC-Inactive
SRS for positioning configuration during RRC_INACTIVE state. | +| srs-PosRRC-InactiveValidityAreaConfigList
List of SRS for positioning configuration during RRC_INACTIVE state which is valid across a number of cells comprising a validity area. For each validity area, the UE is preconfigured with only one SRS for positioning configuration.
The Network configures multiple validity area only when configType value is set preconfig .
The below fields for the respective IEs are configured commonly in the validity area when srs-PosRRC-InactiveValidityAreaConfig is configured:
IE SRS-PosResourceSet: srs-PosResourceSetId , srs-PosResourceSetIdList , srs-PosResourceIdList , resourceType , alpha , p0
IE SRS-PosResource: srs-PosResourceId , transmissionComb , resourceMapping , freqDomainShift , freqHopping , resourceType , groupOrSequenceHopping , sequenceID | +| srs-PosTx-Hopping
Contains configuration related to the SRS for Positioning hopping outside the active BWP of the UE. | +| suspendConfig
Indicates configuration for the RRC_INACTIVE state. The network does not configure suspendConfig when the network redirect the UE to an inter-RAT carrier frequency or if the UE is configured with a DAPS bearer. | +| redirectedCarrierInfo
Indicates a carrier frequency (downlink for FDD) and is used to redirect the UE to an NR or an inter-RAT carrier frequency, by means of cell selection at transition to RRC_IDLE or RRC_INACTIVE as specified in TS 38.304 [20]. Based on UE capability, the network may include redirectedCarrierInfo in RRRelease message with suspendConfig if this message is sent in response to an RRResumeRequest or an RRResumeRequest1 which is triggered by the NAS layer (see 5.3.1.4 in TS 24.501 [23]). | +| voiceFallbackIndication
Indicates the RRC release is triggered by EPS fallback for IMS voice as specified in TS 23.502 [43]. | + +| CarrierInfoNR field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| carrierFreq
Indicates the redirected NR frequency. | +| ssbSubcarrierSpacing
Subcarrier spacing of SSB in the redirected SSB frequency.
Only the following values are applicable depending on the used frequency:
FR1: 15 or 30 kHz
FR2-1: 120 or 240 kHz
FR2-2: 120, 480, or 960 kHz | +| smtc
The SSB periodicity/offset/duration configuration for the redirected SSB frequency. It is based on timing reference of PCell. If the field is absent, the UE uses the SMTTC configured in the measObjectNR having the same SSB frequency and subcarrier spacing. | + +| RAN-NotificationAreaInfo field descriptions | +|----------------------------------------------------------------------------------| +| cellList
A list of cells configured as RAN area. | +| ran-AreaConfigList
A list of RAN area codes or RA code(s) as RAN area. | + +| PLMN-RAN-AreaConfig field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| plmn-Identity
PLMN Identity to which the cells in ran-Area belong. If the field is absent the UE not in SNPN access mode uses the ID of the registered PLMN. This field is not included for UE in SNPN access mode (for UE in SNPN access mode the ran-Area always belongs to the registered SNPN). | +| ran-AreaCodeList
The total number of RAN-AreaCodes of all PLMNs does not exceed 32. | +| ran-Area
Indicates whether TA code(s) or RAN area code(s) are used for the RAN notification area. The network uses only TA code(s) or both TA code(s) and RAN area code(s) to configure a UE. The total number of TACs across all PLMNs does not exceed 16. | + +| PLMN-RAN-AreaCell field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| plmn-Identity
PLMN Identity to which the cells in ran-AreaCells belong. If the field is absent the UE not in SNPN access mode uses the ID of the registered PLMN. This field is not included for UE in SNPN access mode (for UE in SNPN access mode the ran-AreaCells always belongs to the registered SNPN). | +| ran-AreaCells
The total number of cells of all PLMNs does not exceed 32. | + +| SDT-Config field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sdt-DRB-ContinueROHC
Indicates whether the PDCP entity of the radio bearers configured for SDT continues or resets the ROHC header compression protocol during PDCP re-establishment during SDT procedure, as specified in TS 38.323 [5]. Value cell indicates that ROHC header compression continues when the UE resumes for SDT in the same cell as the PCell when the RRCRelease message was received. Value rna indicates that ROHC header compression continues when the UE resumes for SDT in a cell belonging to the same RNA as the PCell where the RRCRelease message was received. If the field is absent, the UE releases any stored value for this field and the PDCP entity of the radio bearers configured for SDT always resets the ROHC header compression protocol during PDCP re-establishment when SDT procedure is initiated, as specified in TS 38.323 [5]. | +| sdt-DRB-List
Indicates the ID(s) of the DRB(s) that are configured for SDT. If size of the sequence is zero, then the UE assumes that none of the DRBs are configured for SDT. The network only configures MN terminated MCG bearers for SDT. | +| sdt-SRB2-Indication
Indicates whether SRB2 is configured for SDT or not. | + +| SDT-MAC-PHY-CG-Config field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| cg-MT-SDT-MaxDurationToNext-CG-Occasion
The maximum duration until the next CG-SDT occasion as specified in TS 38.321 [3] for MT-SDT. If configured, the CG-SDT resource can only be used for the initial CG-SDT transmission if the duration between the initiation of the CG-SDT procedure and the next CG-SDT occasion is less than the value configured by this field. | +| cg-SDT-ConfigInitialBWP-DL
Downlink BWP configuration for CG-SDT. If a UE is an (e)RedCap UE and if the initialDownlinkBWP-RedCap is configured in downlinkConfigCommon in SIB1 , this field is configured for initialDownlinkBWP-RedCap , otherwise it is configured for initialDownlinkBWP . | +| cg-SDT-ConfigInitialBWP-NUL
UL BWP configuration for CG-SDT on NUL carrier. If a UE is an (e)RedCap UE and if the initialUplinkBWP-RedCap is configured in uplinkConfigCommon in SIB1 , this field is configured for initialUplinkBWP-RedCap , otherwise it is configured for initialUplinkBWP for NUL. | +| cg-SDT-ConfigInitialBWP-SUL
UL BWP configuration for CG-SDT on SUL carrier configured for the initialUplinkBWP for SUL. | +| cg-SDT-ConfigLCH-RestrictionToAddModList, cg-SDT-ConfigLCH-RestrictionToAddModListExt, cg-SDT-ConfigLCH-RestrictionToReleaseList
Lists for adding and releasing logical channel mapping restrictions for CG-SDT. If the network includes cg-SDT-ConfigLCH-RestrictionToAddModListExt , it includes the same number of entries, and listed in the same order, as in cg-SDT-ConfigLCH-RestrictionToAddModList . | +| cg-SDT-CS-RNTI
The CS-RNTI value for CG-SDT as specified in TS 38.321 [3]. | +| cg-SDT-RSRP-ThresholdSSB
An RSRP threshold configured for SSB selection for CG-SDT as specified in TS 38.321 [3]. | +| cg-SDT-TA-ValidationConfig
Configuration for the RSRP based TA validation. If this field is not configured, then the UE does not perform RSRP based TA validation. | +| cg-SDT-timeAlignmentTimer
TAT value for CG-SDT as specified in TS 38.321 [3]. The network always configures this field when sdt-MAC-PHY-CG-Config is configured. | + +| CG-SDT-ConfigLCH-Restriction field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| allowedCG-List
This restriction applies only when the UL grant is a configured grant for CG-SDT. If present, UL MAC SDUs from this logical channel can only be mapped to the indicated CG-SDT configured grant configuration. If the size of the sequence is zero, then UL MAC SDUs from this logical channel cannot be mapped to any CG-SDT configured grant configurations. If the field is not present, UL MAC SDUs from this logical channel can be mapped to any CG-SDT configured grant configurations. If the field configuredGrantType1Allowed is present, only those CG-SDT configured grant type 1 configurations indicated in this sequence are allowed for use by this logical channel; otherwise, this sequence shall not include any CG-SDT configured grant type 1 configuration. Corresponds to " allowedCG-List " as specified in TS 38.321 [3]. | +| cg-SDT-MaxDurationToNext-CG-Occasion
The maximum duration until the next CG-SDT occasion for the logical channel identified by the logicalChannelIdentity as specified in TS 38.321 [3]. If configured, the CG-SDT resource can only be used for the initial CG-SDT transmission if the duration between the initiation of the CG-SDT procedure and the next CG-SDT occasion is less than the value configured by this field as specified in TS 38.321 [3]. | +| configuredGrantType1Allowed
If present, or if the capability lcp-Restriction as specified in TS 38.306 [26] is not supported, UL MAC SDUs from this logical channel can be transmitted on a configured grant type 1 for CG-SDT. Otherwise, UL MAC SDUs from this logical channel cannot be transmitted on a configured grant type 1 for CG-SDT. Corresponds to " configuredGrantType1Allowed " in TS 38.321 [3]. | +| logicalChannelIdentity
ID used commonly for the MAC logical channel and for the RLC bearer associated with a servedRadioBearer configured for SDT. | + +| CG-SDT-TA-ValidationConfig field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| cg-SDT-RSRP-ChangeThreshold
The RSRP threshold for TA validation for CG-SDT as specified in TS 38.321 [3]. Value dB2 corresponds to 2 dB, value dB4 corresponds to 4 dB and so on. | + +| SRS-PosRRC-InactiveConfig field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| bwp-NUL
BWP configuration for SRS for Positioning during the RRC_INACTIVE state in Normal Uplink Carrier. If the field is absent UE is configured with an SRS for Positioning associated with the initial UL BWP and transmitted, during the RRC_INACTIVE state, inside the initial UL BWP with the same CP and SCS as configured for initial UL BWP. | +| bwp-SUL
BWP configuration for SRS for Positioning during the RRC_INACTIVE state in Supplementary Uplink Carrier. If the field is absent UE is configured with an SRS for Positioning associated with the initial UL BWP and transmitted, during the RRC_INACTIVE state, inside the initial UL BWP with the same CP and SCS as configured for initial UL BWP. | +| inactivePosSRS-RSRP-ChangeThreshold
RSRP threshold for the increase/decrease of RSRP for time alignment validation as specified in TS 38.321 [3]. | +| inactivePosSRS-TimeAlignmentTimer
TAT value for SRS for positioning transmission during RRC_INACTIVE state as specified in TS 38.321 [3]. The network always configures this field when srs-PosRRC-Inactive is configured. | +| srs-PosConfigNUL
SRS for Positioning configuration in RRC_INACTIVE state in Normal Uplink Carrier. | +| srs-PosConfigSUL
SRS for Positioning configuration in RRC_INACTIVE state in Supplementary Uplink Carrier. | +| srs-PosResSetLinkedForAggBWInactiveList
This field indicates the SRS resource sets across carriers which are linked for SRS bandwidth aggregation in RRC_INACTIVE state as defined in clause 6.2.1.4 of TS 38.214 [19]. | + +| SRS-PosRRC-InactiveValidityAreaConfig field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| autonomousTA-AdjustmentEnabled
This field indicates that UE may adjust the TA value and stored RSRP autonomously after cell reselection within a validity area, if configured. | +| bwp-NUL
BWP configuration for SRS for Positioning during the RRC_INACTIVE state in Normal Uplink Carrier. If the field is absent UE is configured with an SRS for Positioning associated with the initial UL BWP and transmitted, during the RRC_INACTIVE state, inside the initial UL BWP with the same CP and SCS as configured for initial UL BWP. | +| bwp-SUL
BWP configuration for SRS for Positioning during the RRC_INACTIVE state in Supplementary Uplink Carrier. If the field is absent UE is configured with an SRS for Positioning associated with the initial UL BWP and transmitted, during the RRC_INACTIVE state, inside the initial UL BWP with the same CP and SCS as configured for initial UL BWP. | +| configType
Indicates whether the SRS for Positioning configuration in the validity area is to be applied immediately or only when a trigger for an event is met. The value preconfig indicates that the SRS for positioning is to be deferred whereas the value non-preconfig indicates that the configuration is to be applied immediately. | +| srs-PosHyperSFN-Index
Indicates whether the current SFN is even or odd SFN for SRS for Positioning transmission. If this field is not configured, the UE assumes that SRS for positioning periodicity longer than one SFN is not configured. | +| srs-PosRRC-InactiveValidityArea
Provides a list of cells where SRS Positioning Configuration in RRC_INACTIVE state is valid. | +| inactivePosSRS-ValidityAreaTAT
Time alignment timer value for SRS for positioning transmission during RRC_INACTIVE state which is applicable in a validity area. | +| inactivePosSRS-ValidityAreaRSRP
RSRP threshold for the increase/decrease of RSRP for validity area time alignment validation as specified in TS 38.321 [3]. | + +| SRS-PosRRC-AggBW-InactiveConfig field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| bwp
BWP configuration for SRS for Positioning during the RRC_INACTIVE for bandwidth aggregation. If the field is absent UE is configured with an SRS for Positioning associated with the initial UL BWP and transmitted, during the RRC_INACTIVE state, inside the initial UL BWP with the same CP and SCS as configured for initial UL BWP. | +| srs-PosConfig
SRS for Positioning configuration in RRC_INACTIVE state configured with linked carrier for bandwidth aggregation. | +| freqInfoAdditionalCcList
Indicates the frequency information offset to carrier of one or two additional carrier(s) with respective SRS configurations where the carrier and the carrier of the initial BWP should be intra-band contiguous carriers. | + +| SuspendConfig field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| extendedPagingCycle
The eDRX cycle longer than 10.24 s for RAN-initiated paging to be applied by the UE. Value hf2 corresponds to 2 hyper frames, value hf4 corresponds to 4 hyper frames and so on. Value of the field is shorter than or equal to the IDLE mode eDRX cycle configured for the UE. | +| ncd-SSB-RedCapInitialBWP-SDT
Indicates that the UE uses the (e)RedCap-specific initial DL BWP associated with the NCD-SSB for SDT. The network configures this field if an (e)RedCap UE is configured with SDT in the (e)RedCap-specific initial DL BWP not associated with CD-SSB. If configured, the NCD-SSB indicated by this field can only be used during the SDT procedure for CG-SDT or RA-SDT. | +| pagingPTWLength
The length of paging transmission window for RAN-initiated paging to be applied by the UE as defined in TS 38.304 [20]. Value ms1280 corresponds to 1280 miliseconds, value ms2560 corresponds to 2560 miliseconds and so on. | +| ran-ExtendedPagingCycle
The extended DRX (eDRX) cycle for RAN-initiated paging to be applied by the UE. Value rf256 corresponds to 256 radio frames, value rf512 corresponds to 512 radio frames and so on. Value of the field indicates an eDRX cycle which is shorter or equal to the IDLE mode eDRX cycle configured for the UE. | +| ran-NotificationAreaInfo
Network ensures that the UE in RRC_INACTIVE always has a valid ran-NotificationAreaInfo . | +| ran-PagingCycle
Refers to the UE specific cycle for RAN-initiated paging. Value rf32 corresponds to 32 radio frames, value rf64 corresponds to 64 radio frames and so on. | +| resumeIndication
Indicates that the UE shall trigger the RRC connection resume procedure after receiving this RRRelease message, as specified in clause 5.3.8.3. The network only includes this field in the RRRelease message used to terminate an ongoing SDT procedure. | +| si-UEIdentityRemote
Indicates the C-RNTI to the L2 U2N Remote UE. | +| t380
Refers to the timer that triggers the periodic RNAU procedure in UE. Value min5 corresponds to 5 minutes, value min10 corresponds to 10 minutes and so on. | + +| MulticastConfigInactive field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| inactivePTM-Config
Indicates PTM configuration for MBS multicast reception in RRC_INACTIVE in the serving cell. | +| inactiveMCCH-Config
Indicates MCCH configuration for MBS multicast reception in RRC_INACTIVE in the serving cell. Only SI/B24 is allowed to be included. | + +| Conditional Presence | Explanation | +|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------| +| L2RemoteUE | The field is mandatory present for L2 U2N Remote UE's RNAU; otherwise it is absent. | +| RANPaging | This field is optionally present, Need R, if the UE is configured with IDLE eDRX, see TS 24.501 [23]; otherwise the field is not present. | +| Redirection2 | The field is optionally present, Need R, if redirectedCarrierInfo is included; otherwise the field is not present. | + +#### — *RRResume* + +The *RRResume* message is used to resume the suspended RRC connection. + +Signalling radio bearer: SRB1 + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: Network to UE + +#### *RRResume message* + +``` +-- ASN1START +-- TAG-RRRESUME-START + +RRResume ::= + rrc-TransactionIdentifier + criticalExtensions + rrcResume + criticalExtensionsFuture + } +} + +RRResume-IEs ::= + radioBearerConfig + masterCellGroup + measConfig + fullConfig + lateNonCriticalExtension + nonCriticalExtension + } + +RRResume-v1560-IEs ::= + radioBearerConfig2 + sk-Counter + nonCriticalExtension + } + +RRResume-v1610-IEs ::= + idleModeMeasurementReq-r16 + restoreMCG-SCells-r16 + restoreSCG-r16 + mrdc-SecondaryCellGroup-r16 + nr-SCG-r16 + eutra-SCG-r16 + } + needForGapsConfigNR-r16 + +SEQUENCE { + RRC-TransactionIdentifier, + CHOICE { + RRCResume-IEs, + SEQUENCE { } + } +} + +SEQUENCE { + RadioBearerConfig + OCTET STRING (CONTAINING CellGroupConfig) + MeasConfig + ENUMERATED {true} + OCTET STRING + RRResume-v1560-IEs + OPTIONAL, -- Need M + OPTIONAL, -- Need M + OPTIONAL, -- Need M + OPTIONAL, -- Need N + OPTIONAL, + OPTIONAL +} + +SEQUENCE { + OCTET STRING (CONTAINING RadioBearerConfig) + SK-Counter + RRResume-v1610-IEs + OPTIONAL, -- Need M + OPTIONAL, -- Need N + OPTIONAL +} + +SEQUENCE { + ENUMERATED {true} + ENUMERATED {true} + ENUMERATED {true} + CHOICE { + OCTET STRING (CONTAINING RRCReconfiguration), + OCTET STRING + } + SetupRelease {NeedForGapsConfigNR-r16} + OPTIONAL, -- Cond RestoreSCG + OPTIONAL, -- Need M +} +``` + +``` + + nonCriticalExtension RRCResume-v1700-IEs OPTIONAL +} + +RRCResume-v1700-IEs ::= SEQUENCE { + sl-ConfigDedicatedNR-r17 SetupRelease {SL-ConfigDedicatedNR-r16} OPTIONAL, -- Cond L2RemoteUE + sl-L2RemoteUE-Config-r17 SetupRelease {SL-L2RemoteUE-Config-r17} OPTIONAL, -- Cond L2RemoteUE + needForGapNCSG-ConfigNR-r17 SetupRelease {NeedForGapNCSG-ConfigNR-r17} OPTIONAL, -- Need M + needForGapNCSG-ConfigEUTRA-r17 SetupRelease {NeedForGapNCSG-ConfigEUTRA-r17} OPTIONAL, -- Need M + scg-State-r17 ENUMERATED {deactivated} OPTIONAL, -- Need N + appLayerMeasConfig-r17 AppLayerMeasConfig-r17 OPTIONAL, -- Need M + nonCriticalExtension RRCResume-v1800-IEs OPTIONAL +} + +RRCResume-v1800-IEs ::= SEQUENCE { + needForInterruptionConfigNR-r18 ENUMERATED { enabled, disabled } OPTIONAL, -- Need M + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +-- TAG-RRCRESUME-STOP +-- ASN1STOP + +``` + +| RRResume-IEs field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| appLayerMeasConfig
This field is used to configure application layer measurements. This field is absent when the UE is configured to operate with shared spectrum channel access. | +| idleModeMeasurementReq
This field indicates that the UE shall report the idle/inactive measurements, if available, to the network in the RRResumeComplete message | +| masterCellGroup
Configuration of the master cell group. | +| mrdc-SecondaryCellGroup
Includes an RRC message for SCG configuration in NR-DC or NE-DC.
For NR-DC ( nr-SCG ), mrdc-SecondaryCellGroup contains the RRReconfiguration message as generated (entirely) by SN gNB. In this version of the specification, the RRC message can only include fields secondaryCellGroup (with at least reconfigurationWithSync ), otherConfig and measConfig .
For NE-DC ( eutra-SCG ), mrdc-SecondaryCellGroup includes the E-UTRA RRConnectionReconfiguration message as specified in TS 36.331 [10]. In this version of the specification, the E-UTRA RRC message only include the field scg-Configuration with at least mobilityControlInfoSCG . | +| needForGapsConfigNR
Configuration for the UE to report measurement gap requirement information of NR target bands in the RRReconfigurationComplete and RRResumeComplete message. | +| needForGapNCSG-ConfigEUTRA
Configuration for the UE to report measurement gap and NCSG requirement information of E-UTRA target bands in the RRReconfigurationComplete and RRResumeComplete message. | +| needForGapNCSG-ConfigNR
Configuration for the UE to report measurement gap and NCSG requirement information of NR target bands in the RRReconfigurationComplete and RRResumeComplete message. | +| needForInterruptionConfigNR
Indicates whether the UE shall report interruption requirement information of NR target bands in the RRReconfigurationComplete and RRResumeComplete message. The network sets this field to enabled only if the needForGapsConfigNR is configured. The network sets this field to disabled if the needForGapsConfigNR is released. | +| radioBearerConfig
Configuration of Radio Bearers (DRBs, SRBs, multicast MRBs) including SDAP/PDCP. | +| radioBearerConfig2
Configuration of Radio Bearers (DRBs, SRBs) including SDAP/PDCP. This field can only be used if the UE supports NR-DC or NE-DC. | +| restoreMCG-SCells
Indicates that the UE shall restore the MCG SCells from the UE Inactive AS Context, if stored. | +| restoreSCG
Indicates that the UE shall restore the SCG configurations from the UE Inactive AS Context, if stored. | +| scg-State
Indicates that the SCG is in deactivated state. | +| sk-Counter
A counter used to derive $S-K_{gNB}$ or $S-K_{eNB}$ based on the newly derived $K_{gNB}$ during RRC Resume. The field is only included when there is one or more RB with keyToUse set to secondary or mrdc-SecondaryCellGroup is included. | +| sl-ConfigDedicatedNR
This field is used to provide the dedicated configurations for NR sidelink communication/discovery used by L2 U2N Remote UE. | +| sl-L2RemoteUE-Config
Contains L2 U2N relay operation related configurations used by L2 U2N Remote UE. The field is absent if appLayerMeasConfig or SRB4 is configured/not released. | + +| Conditional Presence | Explanation | +|----------------------|---------------------------------------------------------------------------------------------------------------| +| L2RemoteUE | The field is mandatory present for L2 U2N Remote UE; otherwise it is absent. | +| RestoreSCG | The field is mandatory present if restoreSCG is included. It is optionally present, Need M, otherwise. | + +###### — *RRResumeComplete* + +The *RRResumeComplete* message is used to confirm the successful completion of an RRC connection resumption. + +Signalling radio bearer: SRB1 + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: UE to Network + +#### *RRResumeComplete* message + +``` +-- ASN1START +-- TAG-RRRESUMECOMPLETE-START + +RRResumeComplete ::= + rrc-TransactionIdentifier + criticalExtensions + rrcResumeComplete + criticalExtensionsFuture + } +} + +RRResumeComplete-IEs ::= + dedicatedNAS-Message + selectedPLMN-Identity + uplinkTxDirectCurrentList + lateNonCriticalExtension + nonCriticalExtension +} + +RRResumeComplete-v1610-IEs ::= + idleMeasAvailable-r16 + measResultIdleEUTRA-r16 + measResultIdleNR-r16 + scg-Response-r16 + nr-SCG-Response + eutra-SCG-Response + } + ue-MeasurementsAvailable-r16 + mobilityHistoryAvail-r16 + } +} + +SEQUENCE { + RRC-TransactionIdentifier, + CHOICE { + RRResumeComplete-IEs, + SEQUENCE { + } + } +} + +SEQUENCE { + DedicatedNAS-Message + INTEGER (1..maxPLMN) + UplinkTxDirectCurrentList + OCTET STRING + RRResumeComplete-v1610-IEs +} + +SEQUENCE { + ENUMERATED {true} + MeasResultIdleEUTRA-r16 + MeasResultIdleNR-r16 + CHOICE { + OCTET STRING (CONTAINING RRReconfigurationComplete), + OCTET STRING + } + UE-MeasurementsAvailable-r16 + ENUMERATED {true} +} + +OPTIONAL, +OPTIONAL, +OPTIONAL, +OPTIONAL, +OPTIONAL + +OPTIONAL, +OPTIONAL, +OPTIONAL, +OPTIONAL, +OPTIONAL +``` + +``` + +mobilityState-r16 ENUMERATED {normal, medium, high, spare} OPTIONAL, +needForGapsInfoNR-r16 NeedForGapsInfoNR-r16 OPTIONAL, +nonCriticalExtension RRCResumeComplete-v1640-IEs OPTIONAL +} + +RRCResumeComplete-v1640-IEs ::= SEQUENCE { + uplinkTxDirectCurrentTwoCarrierList-r16 UplinkTxDirectCurrentTwoCarrierList-r16 OPTIONAL, + nonCriticalExtension RRCResumeComplete-v1700-IEs OPTIONAL +} + +RRCResumeComplete-v1700-IEs ::= SEQUENCE { + needForGapNCSG-InfoNR-r17 NeedForGapNCSG-InfoNR-r17 OPTIONAL, + needForGapNCSG-InfoUTRA-r17 NeedForGapNCSG-InfoUTRA-r17 OPTIONAL, + nonCriticalExtension RRCResumeComplete-v1720-IEs OPTIONAL +} + +RRCResumeComplete-v1720-IEs ::= SEQUENCE { + uplinkTxDirectCurrentMoreCarrierList-r17 UplinkTxDirectCurrentMoreCarrierList-r17 OPTIONAL, + nonCriticalExtension RRCResumeComplete-v1800-IEs OPTIONAL +} + +RRCResumeComplete-v1800-IEs ::= SEQUENCE { + needForInterruptionInfoNR-r18 NeedForInterruptionInfoNR-r18 OPTIONAL, + musim-CapRestrictionInd-r18 ENUMERATED {true} OPTIONAL, + flightPathInfoAvailable-r18 ENUMERATED {true} OPTIONAL, + measConfigReportAppLayerAvailable-r18 ENUMERATED {true} OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +-- TAG-RRCRESUMECOMPLETE-STOP +-- ASN1STOP + +``` + +| RRResumeComplete-IEs field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| idleMeasAvailable
Indication that the UE has idle/inactive measurement report available. | +| measConfigReportAppLayerAvailable
Indication that the UE has stored one or more application layer measurement reports while the UE was in RRC_IDLE/RRC_INACTIVE state and/or that the UE is configured with at least one application layer measurement configuration with configforRRC-IdleInactive set to true . | +| measResultIdleEUTRA
EUTRA measurement results performed during RRC_INACTIVE. | +| measResultIdleNR
NR measurement results performed during RRC_INACTIVE. | +| musim-CapRestrictionInd
This field indicates the UE temporary capability restriction due to MUSIM operation. | +| needForGapsInfoNR
This field is used to indicate the measurement gap requirement information of the UE for NR target bands. | +| needForGapNCSG-InfoEUTRA
This field is used to indicate the measurement gap and NCSG requirement information of the UE for E-UTRA target bands | +| needForGapNCSG-InfoNR
This field is used to indicate the measurement gap and NCSG requirement information of the UE for NR target bands | +| needForInterruptionInfoNR
This field indicates whether interruption is needed while performing measurement on NR target bands without measurement gap. | +| selectedPLMN-Identity
Index of the PLMN selected by the UE from the plmn-IdentityInfoList or npn-IdentityInfoList fields included in SIB1 . | +| uplinkTxDirectCurrentList
The Tx Direct Current locations for the configured serving cells and BWPs if requested by the NW (see reportUplinkTxDirectCurrent in CellGroupConfig ). | +| uplinkTxDirectCurrentMoreCarrierList
The Tx Direct Current locations for the configured intra-band CA requested by reportUplinkTxDirectCurrentMoreCarrier-r17 . | +| uplinkTxDirectCurrentTwoCarrierList
The Tx Direct Current locations for the configured uplink intra-band CA with two carriers if requested by the NW (see reportUplinkTxDirectCurrentTwoCarrier-r16 in CellGroupConfig ). | + +#### — *RRResumeRequest* + +The *RRResumeRequest* message is used to request the resumption of a suspended RRC connection or perform an RNA update. + +Signalling radio bearer: SRB0 + +RLC-SAP: TM + +Logical channel: CCCH + +Direction: UE to Network + +#### ***RRResumRequest message*** + +``` + +-- ASN1START +-- TAG-RRRESUMEREQUEST-START + +RRResumRequest ::= SEQUENCE { + rrcResumRequest RRResumRequest-IEs +} + +RRResumRequest-IEs ::= SEQUENCE { + resumeIdentity ShortI-RNTI-Value, + resumeMAC-I BIT STRING (SIZE (16)), + resumeCause, + spare BIT STRING (SIZE (1)) +} + +-- TAG-RRRESUMEREQUEST-STOP +-- ASN1STOP + +``` + +##### ***RRResumRequest-IEs field descriptions*** + +| | | +|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| resumeCause | Provides the resume cause for the RRC connection resume request as provided by the upper layers or RRC. The network is not expected to reject an RRResumRequest due to unknown cause value being used by the UE. | +| resumeIdentity | UE identity to facilitate UE context retrieval at gNB. | +| resumeMAC-I | Authentication token to facilitate UE authentication at gNB. The 16 least significant bits of the MAC-I calculated using the AS security configuration as specified in 5.3.13.3. | + +##### ***RRResumRequest1*** + +The *RRResumRequest1* message is used to request the resumption of a suspended RRC connection or perform an RNA update. + +Signalling radio bearer: SRB0 + +RLC-SAP: TM + +Logical channel: CCCH1 + +Direction: UE to Network + +#### ***RRResumRequest1 message*** + +``` + +-- ASN1START +-- TAG-RRRESUMEREQUEST1-START + +``` + +``` + +RRCResumeRequest1 ::= SEQUENCE { + rrcResumeRequest1 RRCResumeRequest1-IEs +} + +RRCResumeRequest1-IEs ::= SEQUENCE { + resumeIdentity I-RNTI-Value, + resumeMAC-I BIT STRING (SIZE (16)), + resumeCause ResumeCause, + spare BIT STRING (SIZE (1)) +} + +-- TAG-RRCRESUMEREQUEST1-STOP +-- ASN1STOP + +``` + +##### ***RRCResumeRequest1-IEs* field descriptions** + +| | | +|------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| resumeCause | Provides the resume cause for the RRCResumeRequest1 as provided by the upper layers or RRC. A gNB is not expected to reject an RRCResumeRequest1 due to unknown cause value being used by the UE. | +| resumeIdentity | UE identity to facilitate UE context retrieval at gNB. | +| resumeMAC-I | Authentication token to facilitate UE authentication at gNB. The 16 least significant bits of the MAC-I calculated using the AS security configuration as specified in 5.3.13.3. | + +#### — ***RRCSetup*** + +The *RRCSetup* message is used to establish SRB1. + +Signalling radio bearer: SRB0 + +RLC-SAP: TM + +Logical channel: CCCH + +Direction: Network to UE + +#### ***RRCSetup* message** + +``` + +-- ASN1START +-- TAG-RCSETUP-START + +RRCSetup ::= SEQUENCE { + rrc-TransactionIdentifier RRC-TransactionIdentifier, + criticalExtensions CHOICE { + rrcSetup RRCSetup-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +``` + +``` + + } + } + + RRCSetup-IEs ::= + radioBearerConfig SEQUENCE { + masterCellGroup RadioBearerConfig, + lateNonCriticalExtension OCTET STRING (CONTAINING CellGroupConfig), + nonCriticalExtension OCTET STRING OPTIONAL, + RRCSetup-v1700-IEs OPTIONAL + } + + RRCSetup-v1700-IEs ::= + sl-ConfigDedicatedNR-r17 SEQUENCE { + sl-L2RemoteUE-Config-r17 SL-ConfigDedicatedNR-r16 OPTIONAL, -- Cond L2RemoteUE + nonCriticalExtension SL-L2RemoteUE-Config-r17 OPTIONAL, -- Cond L2RemoteUE + SEQUENCE {} OPTIONAL + } + + -- TAG-RRCSETUP-STOP + -- ASN1STOP + +``` + +| RRCSetup-IEs field descriptions | | +|----------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| masterCellGroup | The network configures only the RLC bearer for the SRB1, mac-CellGroupConfig , physicalCellGroupConfig and spCellConfig . | +| radioBearerConfig | Only SRB1 can be configured in RRC setup. | +| sl-ConfigDedicatedNR | Contains dedicated configurations for NR sidelink communication. The network configures only the PC5 Relay RLC channel and sl-PHY-MAC-RLC-Config used for the SRB1. | +| sl-L2RemoteUE-Config | Contains dedicated configurations used for L2 U2N relay related operation. The network configures only the SRAP configuration used for the SRB1 and local UE ID. | + +| Conditional Presence | Explanation | +|-----------------------------|------------------------------------------------------------------------------| +| L2RemoteUE | The field is mandatory present for L2 U2N Remote UE; otherwise it is absent. | + +#### — ***RRCSetupComplete*** + +The *RRCSetupComplete* message is used to confirm the successful completion of an RRC connection establishment. + +Signalling radio bearer: SRB1 + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: UE to Network + +#### **RRCSetupComplete message** + +``` + +-- ASN1START +-- TAG-RRCSETUPCOMPLETE-START + +RRCSetupComplete ::= SEQUENCE { + rrc-TransactionIdentifier RRC-TransactionIdentifier, + criticalExtensions CHOICE { + rrcSetupComplete RRCSetupComplete-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +RRCSetupComplete-IEs ::= SEQUENCE { + selectedPLMN-Identity INTEGER (1..maxPLMN), + registeredAMF RegisteredAMF OPTIONAL, + guami-Type ENUMERATED {native, mapped} OPTIONAL, + s-NSSAI-List SEQUENCE (SIZE (1..maxNrofS-NSSAI)) OF S-NSSAI OPTIONAL, + dedicatedNAS-Message DedicatedNAS-Message, + ng-5G-S-TMSI-Value CHOICE { + ng-5G-S-TMSI NG-5G-S-TMSI, + ng-5G-S-TMSI-Part2 BIT STRING (SIZE (9)) + } OPTIONAL, + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension RRCSetupComplete-v1610-IEs OPTIONAL +} + +RRCSetupComplete-v1610-IEs ::= SEQUENCE { + iab-NodeIndication-r16 ENUMERATED {true} OPTIONAL, + idleMeasAvailable-r16 ENUMERATED {true} OPTIONAL, + ue-MeasurementsAvailable-r16 UE-MeasurementsAvailable-r16 OPTIONAL, + mobilityHistoryAvail-r16 ENUMERATED {true} OPTIONAL, + mobilityState-r16 ENUMERATED {normal, medium, high, spare} OPTIONAL, + nonCriticalExtension RRCSetupComplete-v1690-IEs OPTIONAL +} + +RRCSetupComplete-v1690-IEs ::= SEQUENCE { + ul-RRC-Segmentation-r16 ENUMERATED {true} OPTIONAL, + nonCriticalExtension RRCSetupComplete-v1700-IEs OPTIONAL +} + +RRCSetupComplete-v1700-IEs ::= SEQUENCE { + onboardingRequest-r17 ENUMERATED {true} OPTIONAL, + nonCriticalExtension RRCSetupComplete-v1800-IEs OPTIONAL +} + +RRCSetupComplete-v1800-IEs ::= SEQUENCE { + ncr-NodeIndication-r18 ENUMERATED {true} OPTIONAL, + musim-CapRestrictionInd-r18 ENUMERATED {true} OPTIONAL, + flightPathInfoAvailable-r18 ENUMERATED {true} OPTIONAL, + measConfigReportAppLayerAvailable-r18 ENUMERATED {true} OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +-- TAG-RRCSETUPCOMPLETE-STOP +-- ASN1STOP + +``` + +``` + + mobileIAB-NodeIndication-r18 ENUMERATED {true} OPTIONAL, + nonCriticalExtension SEQUENCE{} OPTIONAL +} + +RegisteredAMF ::= SEQUENCE { + plmn-Identity PLMN-Identity OPTIONAL, + amf-Identifier AMF-Identifier +} + +-- TAG-RRCSETUPCOMPLETE-STOP +-- ASN1STOP + +``` + +| RRCSsetupComplete-IEs field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| guami-Type
This field is used to indicate whether the GUAMI included is native (derived from native 5G-GUTI) or mapped (from EPS, derived from EPS GUTI) as specified in TS 24.501 [23]. | +| iab-NodeIndication
This field is used to indicate that the connection is being established by an IAB-node as specified in TS 38.300 [2]. If this field is included, the UE shall not include the field mobileIAB-NodeIndication . | +| idleMeasAvailable
Indication that the UE has idle/inactive measurement report available. | +| measConfigReportAppLayerAvailable
Indication that the UE has stored one or more application layer measurement reports while the UE was in RRC_IDLE/RRC_INACTIVE state and/or that the UE is configured with at least one application layer measurement configuration with configforRRc-IdleInactive set to true . | +| mobileIAB-NodeIndication
This field is used to indicate that the connection is being established by a mobile IAB-node as specified in TS 38.300 [2]. If this field is included, the UE shall not include the field iab-NodeIndication . | +| mobilityState
This field indicates the UE mobility state (as defined in TS 38.304 [20], clause 5.2.4.3) just prior to UE going into RRC_CONNECTED state. The UE indicates the value of medium and high when being in Medium-mobility and High-mobility states respectively. Otherwise the UE indicates the value normal . | +| musim-CapRestrictionInd
This field indicates the UE temporary capability restriction due to MUSIM operation. | +| ncr-NodeIndication
This field is used to indicate that the connection is being established by an NCR-node as specified in TS 38.300 [2]. | +| ng-5G-S-TMSI-Part2
The leftmost 9 bits of 5G-S-TMSI. | +| onboardingRequest
This field indicates that the connection is being established for UE onboarding in the selected onboarding SNPN, see TS 23.501 [32]. | +| registeredAMF
This field is used to transfer the GUAMI of the AMF where the UE is registered, as provided by upper layers, see TS 23.003 [21]. | +| selectedPLMN-Identity
Index of the PLMN or SNPN selected by the UE from the plmn-IdentityInfoList or npn-IdentityInfoList fields included in SIB1. | +| ul-RRc-Segmentation
This field indicates the UE supports uplink RRc segmentation of UECapabilityInformation . | + +#### – *RRCSsetupRequest* + +The *RRCSsetupRequest* message is used to request the establishment of an RRC connection. + +Signalling radio bearer: SRB0 + +RLC-SAP: TM + +Logical channel: CCCH + +Direction: UE to Network + +#### *RRCSsetupRequest message* + +``` +-- ASN1START +-- TAG-RRCSSETUPREQUEST-START + +RRCSsetupRequest ::= + rrcSetupRequest +} + +RRCSsetupRequest-IEs ::= + ue-Identity + establishmentCause + spare +} + +InitialUE-Identity ::= + ng-5G-S-TMSI-Part1 + randomValue +} + +EstablishmentCause ::= + SEQUENCE { + RRCSsetupRequest-IEs + } + + SEQUENCE { + InitialUE-Identity, + EstablishmentCause, + BIT STRING (SIZE (1)) + } + + CHOICE { + BIT STRING (SIZE (39)), + BIT STRING (SIZE (39)) + } + + ENUMERATED { + emergency, highPriorityAccess, mt-Access, mo-Signalling, + mo-Data, mo-VoiceCall, mo-VideoCall, mo-SMS, mps-PriorityAccess, mcs-PriorityAccess, + spare6, spare5, spare4, spare3, spare2, spare1 + } + +-- TAG-RRCSSETUPREQUEST-STOP +-- ASN1STOP +``` + +| RRCSSetupRequest-IEs field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| establishmentCause
Provides the establishment cause for the RRCSSetupRequest in accordance with the information received from upper layers. gNB is not expected to reject an RRCSSetupRequest due to unknown cause value being used by the UE. | +| ue-Identity
UE identity included to facilitate contention resolution by lower layers. | + +| InitialUE-Identity field descriptions | +|----------------------------------------------------------------------| +| ng-5G-S-TMSI-Part1
The rightmost 39 bits of 5G-S-TMSI. | +| randomValue
Integer value in the range 0 to $2^{39} - 1$ . | + +#### — *RRCSystemInfoRequest* + +The *RRCSystemInfoRequest* message is used to request SI message(s) required by the UE as specified in clause 5.2.2.3.3 and 5.2.2.3.3a. + +Signalling radio bearer: SRB0 + +RLC-SAP: TM + +Logical channel: CCCH + +Direction: UE to Network + +#### ***RRCSystemInfoRequest* message** + +``` +-- ASN1START +-- TAG-RRCSYSTEMINFOREQUEST-START + +RRCSystemInfoRequest ::= SEQUENCE { + criticalExtensions CHOICE { + rrcSystemInfoRequest RRCSystemInfoRequest-IEs, + criticalExtensionsFuture-r16 CHOICE { + rrcPosSystemInfoRequest-r16 RRC-PosSystemInfoRequest-r16-IEs, + criticalExtensionsFuture SEQUENCE {} + } + } +} + +RRCSystemInfoRequest-IEs ::= SEQUENCE { + requested-SI-List BIT STRING (SIZE (maxSI-Message)), --32bits + spare BIT STRING (SIZE (12)) +} +``` + +``` + +RRCP-PosSystemInfoRequest-r16-IEs ::= SEQUENCE { + requestedPosSI-List BIT STRING (SIZE (maxSI-Message)), --32bits + spare BIT STRING (SIZE (11)) +} + +-- TAG-RRCSYSTEMINFOREQUEST-STOP +-- ASN1STOP + +``` + +##### RRCS-SystemInfoRequest-IEs field descriptions + +###### requested-SI-List + +Contains a list of requested SI messages which are configured by *schedulingInfoList* in *si-SchedulingInfo* and *schedulingInfoList2* in *si-SchedulingInfo-v1700* (if present) in SIB1. + +If *si-SchedulingInfo-v1700* is not present: + +- According to the order of entry in the list of SI messages configured by *schedulingInfoList* in *si-SchedulingInfo* in SIB1, first bit corresponds to first/leftmost listed SI message, second bit corresponds to second listed SI message, and so on. + +If *si-SchedulingInfo-v1700* is present: + +- The UE generates a list of concatenated SI messages by appending the SI messages containing type1 SIB configured by *schedulingInfoList2* in *si-SchedulingInfo-v1700* to the SI messages configured by *schedulingInfoList* in *si-SchedulingInfo*. +- According to the order of entry in the list of concatenated SI messages, first bit corresponds to first/leftmost listed SI message, second bit corresponds to second listed SI message, and so on. + +###### requestedPosSI-List + +Contains a list of requested SI messages which are configured by *posSchedulingInfoList* in *posSI-SchedulingInfo* and *schedulingInfoList2* in *si-SchedulingInfo-v1700* (if present) in SIB1. + +If *si-SchedulingInfo-v1700* is not present: + +- According to the order of entry in the list of SI messages configured by *posSchedulingInfoList* in *posSI-SchedulingInfo* in SIB1, first bit corresponds to first/leftmost listed SI message, second bit corresponds to second listed SI message, and so on. + +If *si-SchedulingInfo-v1700* is present: + +- The UE creates a list of concatenated SI messages by appending the SI messages containing type2 SIB configured by *schedulingInfoList2* in *si-SchedulingInfo-v1700* to the SI messages configured by *posSchedulingInfoList* in *posSI-SchedulingInfo*. +- According to the order of entry in the list of concatenated SI messages, first bit corresponds to first/leftmost listed SI message, second bit corresponds to second listed SI message, and so on. + +#### SCGF-ailureInformation + +The *SCGF-ailureInformation* message is used to provide information regarding NR SCG failures detected by the UE. + +Signalling radio bearer: SRB1 + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: UE to Network + +#### **SCGFailureInformation message** + +``` + +-- ASN1START +-- TAG-SCGFAILUREINFORMATION-START + +SCGFailureInformation ::= + SEQUENCE { + criticalExtensions + CHOICE { + scgFailureInformation + SCGFailureInformation-IEs, + criticalExtensionsFuture + SEQUENCE {} + } + } + +SCGFailureInformation-IEs ::= + SEQUENCE { + failureReportSCG + FailureReportSCG + OPTIONAL, + nonCriticalExtension + SCGFailureInformation-v1590-IEs + OPTIONAL + } + +SCGFailureInformation-v1590-IEs ::= + SEQUENCE { + lateNonCriticalExtension + OCTET STRING + OPTIONAL, + nonCriticalExtension + SEQUENCE {} + OPTIONAL + } + +FailureReportSCG ::= + SEQUENCE { + failureType + ENUMERATED { + t310-Expiry, randomAccessProblem, + rlc-MaxNumRetx, + synchReconfigFailureSCG, scg-ReconfigFailure, + srb3-IntegrityFailure, other-r16, spare1}, + measResultFreqList + MeasResultFreqList + OPTIONAL, + measResultSCG-Failure + OCTET STRING (CONTAINING MeasResultSCG-Failure) + OPTIONAL, + ... + [[ + locationInfo-r16 + LocationInfo-r16 + OPTIONAL, + failureType-v1610 + ENUMERATED {scg-lbtFailure-r16, beamFailureRecoveryFailure-r16, + t312-Expiry-r16, bh-RLF-r16, beamFailure-r17, spare3, spare2, spare1} OPTIONAL + ]], + [[ + previousPSCellId-r17 + SEQUENCE { + physCellId-r17 + PhysCellId, + carrierFreq-r17 + ARFCN-ValueNR + } + OPTIONAL, + failedPSCellId-r17 + SEQUENCE { + physCellId-r17 + PhysCellId, + carrierFreq-r17 + ARFCN-ValueNR + } + OPTIONAL, + timeSCGFailure-r17 + INTEGER (0..1023) + OPTIONAL, + perRAInfoList-r17 + PerRAInfoList-r16 + OPTIONAL + ]] + } + +``` + +``` + +} + +MeasResultFreqList ::= + SEQUENCE (SIZE (1..maxFreq)) OF MeasResult2NR + +-- TAG-SCGFAILUREINFORMATION-STOP +-- ASN1STOP + +``` + +##### SCGFailureInformation field descriptions + +###### **measResultFreqList** + +The field contains available results of measurements on NR frequencies the UE is configured to measure by *measConfig*. + +###### **measResultSCG-Failure** + +The field contains the *MeasResultSCG-Failure* IE which includes available results of measurements on NR frequencies the UE is configured to measure by the NR SCG *RRReconfiguration* message. + +###### **previousPSCellId** + +This field indicates the physical cell id and carrier frequency of the cell that is the source PSCell of the last PSCell change. In case of PSCell addition failure, this field is absent. + +###### **failedPSCellId** + +This field indicates the physical cell id and carrier frequency of the cell in which SCG failure is detected or the target PSCell of the failed PSCell change or failed PSCell addition. + +###### **timeSCGFailure** + +This field is used to indicate the time elapsed since the last execution of *RRReconfiguration* with *reconfigurationWithSync* for the SCG until the SCG failure. Actual value = field value \* 100ms. The maximum value 1023 means 102.3s or longer. + +###### – SCGFailureInformationEUTRA + +The *SCGFailureInformationEUTRA* message is used to provide information regarding E-UTRA SCG failures detected by the UE. + +Signalling radio bearer: SRB1 + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: UE to Network + +#### SCGFailureInformationEUTRA message + +``` + +-- ASN1START +-- TAG-SCGFAILUREINFORMATIONEUTRA-START + +SCGFailureInformationEUTRA ::= + SEQUENCE { + criticalExtensions + CHOICE { + scgFailureInformationEUTRA + SCGFailureInformationEUTRA-IEs, + criticalExtensionsFuture + SEQUENCE {} + +``` + +``` + + } + } + + SCGFailureInformationEUTRA-IEs ::= SEQUENCE { + failureReportSCG-EUTRA FailureReportSCG-EUTRA OPTIONAL, + nonCriticalExtension SCGFailureInformationEUTRA-v1590-IEs OPTIONAL + } + + SCGFailureInformationEUTRA-v1590-IEs ::= SEQUENCE { + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL + } + + FailureReportSCG-EUTRA ::= SEQUENCE { + failureType ENUMERATED { + t313-Expiry, randomAccessProblem, rlc-MaxNumRetx, + scg-ChangeFailure, spare4, + spare3, spare2, spare1}, + measResultFreqListMRDC MeasResultFreqListFailMRDC OPTIONAL, + measResultSCG-FailureMRDC OCTET STRING OPTIONAL, + ... + [[ + locationInfo-r16 LocationInfo-r16 OPTIONAL + ]] + } + + MeasResultFreqListFailMRDC ::= SEQUENCE (SIZE (1.. maxFreq)) OF MeasResult2EUTRA + + -- TAG-SCGFAILUREINFORMATIONEUTRA-STOP + -- ASN1STOP + +``` + +#### SCGFailureInformationEUTRA field descriptions + +###### **measResultFreqListMRDC** + +The field contains available results of measurements on E-UTRA frequencies the UE is configured to measure by *measConfig*. + +###### **measResultSCG-FailureMRDC** + +Includes the E-UTRA *MeasResultSCG-FailureMRDC* IE as specified in TS 36.331 [10]. The field contains available results of measurements on E-UTRA frequencies the UE is configured to measure by the E-UTRA *RRCConnectionReconfiguration* message. + +###### — SecurityModeCommand + +The *SecurityModeCommand* message is used to command the activation of AS security. + +Signalling radio bearer: SRB1 + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: Network to UE + +#### *SecurityModeCommand* message + +``` +-- ASN1START +-- TAG-SECURITYMODECOMMAND-START + +SecurityModeCommand := SEQUENCE { + rrc-TransactionIdentifier RRC-TransactionIdentifier, + criticalExtensions CHOICE { + securityModeCommand SecurityModeCommand-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +SecurityModeCommand-IEs := SEQUENCE { + securityConfigSMC SecurityConfigSMC, + + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension SEQUENCE{} OPTIONAL +} + +SecurityConfigSMC := SEQUENCE { + securityAlgorithmConfig SecurityAlgorithmConfig, + ... +} + +-- TAG-SECURITYMODECOMMAND-STOP +-- ASN1STOP +``` + +###### — *SecurityModeComplete* + +The *SecurityModeComplete* message is used to confirm the successful completion of a security mode command. + +Signalling radio bearer: SRB1 + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: UE to Network + +#### *SecurityModeComplete* message + +``` +-- ASN1START +``` + +``` + +-- TAG-SECURITYMODECOMPLETE-START + +SecurityModeComplete ::= SEQUENCE { + rrc-TransactionIdentifier RRC-TransactionIdentifier, + criticalExtensions CHOICE { + securityModeComplete SecurityModeComplete-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +SecurityModeComplete-IEs ::= SEQUENCE { + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension SEQUENCE{} OPTIONAL +} + +-- TAG-SECURITYMODECOMPLETE-STOP +-- ASN1STOP + +``` + +###### – SecurityModeFailure + +The *SecurityModeFailure* message is used to indicate an unsuccessful completion of a security mode command. + +Signalling radio bearer: SRB1 + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: UE to Network + +#### SecurityModeFailure message + +``` + +-- ASN1START +-- TAG-SECURITYMODEFAILURE-START + +SecurityModeFailure ::= SEQUENCE { + rrc-TransactionIdentifier RRC-TransactionIdentifier, + criticalExtensions CHOICE { + securityModeFailure SecurityModeFailure-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +SecurityModeFailure-IEs ::= SEQUENCE { + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension SEQUENCE{} OPTIONAL +} + +``` + +``` +-- TAG-SECURITYMODEFAILURE-STOP +-- ASN1STOP +``` + +#### SIB1 + +SIB1 contains information relevant when evaluating if a UE is allowed to access a cell and defines the scheduling of other system information. It also contains radio resource configuration information that is common for all UEs and barring information applied to the unified access control. + +Signalling radio bearer: N/A + +RLC-SAP: TM + +Logical channels: BCCH + +Direction: Network to UE + +#### SIB1 message + +``` +-- ASN1START +-- TAG-SIB1-START + +SIB1 ::= SEQUENCE { + cellSelectionInfo SEQUENCE { + q-RxLevMin Q-RxLevMin, + q-RxLevMinOffset INTEGER (1..8) OPTIONAL, -- Need S + q-RxLevMinSUL Q-RxLevMin OPTIONAL, -- Need R + q-QualMin Q-QualMin OPTIONAL, -- Need S + q-QualMinOffset INTEGER (1..8) OPTIONAL, -- Need S + } + cellAccessRelatedInfo CellAccessRelatedInfo, + connEstFailureControl ConnEstFailureControl OPTIONAL, -- Need R + si-SchedulingInfo SI-SchedulingInfo OPTIONAL, -- Need R + servingCellConfigCommon ServingCellConfigCommonSIB OPTIONAL, -- Need R + ims-EmergencySupport ENUMERATED {true} OPTIONAL, -- Need R + eCallOverIMS-Support ENUMERATED {true} OPTIONAL, -- Need R + ue-TimersAndConstants UE-TimersAndConstants OPTIONAL, -- Need R + uac-BarringInfo SEQUENCE { + uac-BarringForCommon UAC-BarringPerCatList OPTIONAL, -- Need S + uac-BarringPerPLMN-List UAC-BarringPerPLMN-List OPTIONAL, -- Need S + uac-BarringInfoSetList UAC-BarringInfoSetList, + uac-AccessCategory1-SelectionAssistanceInfo CHOICE { + plmnCommon UAC-AccessCategory1-SelectionAssistanceInfo, + individualPLMNList SEQUENCE (SIZE (2..maxPLMN)) OF UAC-AccessCategory1-SelectionAssistanceInfo + } + } + useFullResumeID ENUMERATED {true} OPTIONAL, -- Need S + OPTIONAL, -- Need R + OPTIONAL, -- Need R +``` + +``` + + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension SIB1-v1610-IEs OPTIONAL +} + +SIB1-v1610-IEs ::= SEQUENCE { + idleModeMeasurementsEUTRA-r16 ENUMERATED{true} OPTIONAL, -- Need R + idleModeMeasurementsNR-r16 ENUMERATED{true} OPTIONAL, -- Need R + posSI-SchedulingInfo-r16 PosSI-SchedulingInfo-r16 OPTIONAL, -- Need R + nonCriticalExtension SIB1-v1630-IEs OPTIONAL +} + +SIB1-v1630-IEs ::= SEQUENCE { + uac-BarringInfo-v1630 SEQUENCE { + uac-AC1-SelectAssistInfo-r16 SEQUENCE (SIZE (2..maxPLMN)) OF UAC-AC1-SelectAssistInfo-r16 + } + nonCriticalExtension SIB1-v1700-IEs OPTIONAL, -- Need R +} + +SIB1-v1700-IEs ::= SEQUENCE { + hsdn-Cell-r17 ENUMERATED {true} OPTIONAL, -- Need R + uac-BarringInfo-v1700 SEQUENCE { + uac-BarringInfoSetList-v1700 UAC-BarringInfoSetList-v1700 + } + sdt-ConfigCommon-r17 SDT-ConfigCommonSIB-r17 OPTIONAL, -- Cond MINT + redCap-ConfigCommon-r17 RedCap-ConfigCommonSIB-r17 OPTIONAL, -- Need R + featurePriorities-r17 SEQUENCE { + redCapPriority-r17 FeaturePriority-r17 OPTIONAL, -- Need R + slicingPriority-r17 FeaturePriority-r17 OPTIONAL, -- Need R + msg3-Repetitions-Priority-r17 FeaturePriority-r17 OPTIONAL, -- Need R + sdt-Priority-r17 FeaturePriority-r17 OPTIONAL, -- Need R + } + si-SchedulingInfo-v1700 SI-SchedulingInfo-v1700 OPTIONAL, -- Need R + hyperSFN-r17 BIT STRING (SIZE (10)) OPTIONAL, -- Need R + eDRX-AllowedIdle-r17 ENUMERATED {true} OPTIONAL, -- Need R + eDRX-AllowedInactive-r17 ENUMERATED {true} OPTIONAL, -- Cond EDRX-RC + intraFreqReselectionRedCap-r17 ENUMERATED {allowed, notAllowed} OPTIONAL, -- Need S + cellBarredNTN-r17 ENUMERATED {barred, notBarred} OPTIONAL, -- Need S + nonCriticalExtension SIB1-v1740-IEs OPTIONAL +} + +SIB1-v1740-IEs ::= SEQUENCE { + si-SchedulingInfo-v1740 SI-SchedulingInfo-v1740 OPTIONAL, -- Need R + nonCriticalExtension SIB1-v1800-IEs OPTIONAL +} + +SIB1-v1800-IEs ::= SEQUENCE { + ncr-Support-r18 ENUMERATED {true} OPTIONAL, -- Need S + mt-SDT-ConfigCommonSIB-r18 MT-SDT-ConfigCommonSIB-r18 OPTIONAL, -- Need R + musim-CapRestrictionAllowed-r18 ENUMERATED {true} OPTIONAL, -- Need R + featurePriorities-v1800 SEQUENCE { + msg1-Repetitions-Priority-r18 FeaturePriority-r17 OPTIONAL, -- Need R + eRedCapPriority-r18 FeaturePriority-r17 OPTIONAL, -- Need R + } +} + +``` + +``` + + } + si-SchedulingInfo-v1800 SI-SchedulingInfo-v1800 OPTIONAL, -- Need R + cellBarredATG-r18 ENUMERATED {barred, notBarred} OPTIONAL, -- Need R + cellBarredNES-r18 ENUMERATED {notBarred} OPTIONAL, -- Need S + mobileIAB-Cell-r18 ENUMERATED {true} OPTIONAL, -- Need R + eDRX-AllowedInactive-r18 ENUMERATED {true} OPTIONAL, -- Cond EDRX-RC + intraFreqReselection-eRedCap-r18 ENUMERATED {allowed, notAllowed} OPTIONAL, -- Need S + nonServingCellMTI-r18 ENUMERATED {true} OPTIONAL, -- Need R + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +UAC-AccessCategory1-SelectionAssistanceInfo ::= ENUMERATED {a, b, c} + +UAC-AC1-SelectAssistInfo-r16 ::= ENUMERATED {a, b, c, notConfigured} + +SDT-ConfigCommonSIB-r17 ::= SEQUENCE { + sdt-RSRP-Threshold-r17 RSRP-Range OPTIONAL, -- Need R + sdt-LogicalChannelSR-DelayTimer-r17 ENUMERATED { sf20, sf40, sf64, sf128, sf512, sf1024, sf2560, spare1} OPTIONAL, -- Need R + sdt-DataVolumeThreshold-r17 ENUMERATED {byte32, byte100, byte200, byte400, byte600, byte800, byte1000, byte2000, byte4000, + byte8000, byte9000, byte10000, byte12000, byte24000, byte48000, byte96000}, + t319a-r17 ENUMERATED { ms100, ms200, ms300, ms400, ms600, ms1000, ms2000, + ms3000, ms4000, spare7, spare6, spare5, spare4, spare3, spare2, spare1} +} + +RedCap-ConfigCommonSIB-r17 ::= SEQUENCE { + halfDuplexRedCapAllowed-r17 ENUMERATED {true} OPTIONAL, -- Need R + cellBarredRedCap-r17 SEQUENCE { + cellBarredRedCap1Rx-r17 ENUMERATED {barred, notBarred}, + cellBarredRedCap2Rx-r17 ENUMERATED {barred, notBarred} + } OPTIONAL, -- Need R + ... + [[ + cellBarredRedCap-r18 SEQUENCE { + cellBarred-eRedCap1Rx-r18 ENUMERATED {barred, notBarred}, + cellBarred-eRedCap2Rx-r18 ENUMERATED {barred, notBarred} + } + ]] OPTIONAL -- Need R +} + +FeaturePriority-r17 ::= INTEGER (0..7) + +MT-SDT-ConfigCommonSIB-r18 ::= SEQUENCE { + sdt-RSRP-ThresholdMT-r18 RSRP-Range OPTIONAL, -- Need S + sdt-LogicalChannelSR-DelayTimer-r18 ENUMERATED { sf20, sf40, sf64, sf128, sf512, sf1024, sf2560, spare1} OPTIONAL, -- Cond MT-SDT1 + t319a-r18 ENUMERATED { ms100, ms200, ms300, ms400, ms600, ms1000, ms2000, + ms3000, ms4000, spare7, spare6, spare5, spare4, + spare3, spare2, spare1} OPTIONAL -- Cond MT-SDT2 +} + +-- TAG-SIB1-STOP +-- ASN1STOP + +``` + + + +| SIB1 field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| cellBarredATG
Value barred means that the cell is barred for connectivity to ATG, as defined in TS 38.304 [20]. Value notBarred means that the cell is allowed for connectivity to ATG. If not present, the UE considers the cell is not allowed for connectivity to ATG, as defined in TS 38.304 [20]. This field is only applicable to ATG-capable UEs. | +| cellBarred-eRedCap1Rx
Value barred means that the cell is barred for an eRedCap UE with 1 Rx branch, as defined in TS 38.304 [20]. This field is ignored by non-eRedCap UEs. | +| cellBarred-eRedCap2Rx
Value barred means that the cell is barred for an eRedCap UE with 2 Rx branches, as defined in TS 38.304 [20]. This field is ignored by non-eRedCap UEs. | +| cellBarredNES
The presence of this field indicates that the cell is allowed for UEs supporting NES cell DTX/DRX. | +| cellBarredNTN
Value barred means that the cell is barred for connectivity to NTN, as defined in TS 38.304 [20]. Value notBarred means that the cell is allowed for connectivity to NTN. If not present, the UE considers the cell is not allowed for connectivity to NTN, as defined in TS 38.304 [20]. This field is only applicable to NTN-capable UEs. | +| cellBarredRedCap1Rx
Value barred means that the cell is barred for a RedCap UE with 1 Rx branch, as defined in TS 38.304 [20]. This field is ignored by non-RedCap UEs. | +| cellBarredRedCap2Rx
Value barred means that the cell is barred for a RedCap UE with 2 Rx branches, as defined in TS 38.304 [20]. This field is ignored by non-RedCap UEs. | +| cellSelectionInfo
Parameters for cell selection related to the serving cell. | +| eCallOverIMS-Support
Indicates whether the cell supports eCall over IMS services as defined in TS 23.501 [32]. If absent, eCall over IMS is not supported by the network in the cell. | +| eDRX-AllowedIdle
The presence of this field indicates that extended DRX for CN paging is allowed in the cell for UEs in RRC_IDLE or RRC_INACTIVE. The UE shall stop using extended DRX for CN paging in RRC_IDLE or RRC_INACTIVE if eDRX-AllowedIdle is not present. | +| eDRX-AllowedInactive
The presence of eDRX-AllowedInactive-r17 this field indicates that extended DRX cycle equal to or shorter than 10.24 s for RAN paging is allowed in the cell for UEs in RRC_INACTIVE. The UE shall stop using extended DRX cycle equal to or shorter than 10.24 s for RAN paging in RRC_INACTIVE if eDRX-AllowedInactive-r17 is not present. The presence of eDRX-AllowedInactive-r18 indicates that extended DRX cycle longer than 10.24 s for RAN paging is allowed in the cell for UEs in RRC_INACTIVE. The UE shall stop using extended DRX cycle longer than 10.24 s for RAN paging in RRC_INACTIVE if eDRX-AllowedInactive-r18 is not present. | +| featurePriorities
Indicates priorities for features, such as (e)RedCap, Slicing, SDT, MSG1-Repetitions and MSG3-Repetitions for Coverage Enhancements. These priorities are used to determine which FeatureCombinationPreambles the UE shall use when a feature maps to more than one FeatureCombinationPreambles , as specified in TS 38.321 [3]. A lower value means a higher priority. The network does not signal the same priority for more than one feature. The network signals a priority for all feature that map to at least one FeatureCombinationPreambles . | +| halfDuplexRedCap-Allowed
The presence of this field indicates that the cell supports half-duplex FDD (e)RedCap UEs. | +| hsdn-Cell
This field indicates this is a HSDN cell as specified in TS 38.304 [20]. | +| hyperSFN
Indicates hyper SFN which increments by one when the SFN wraps around. This field is excluded when determining changes in system information, i.e. changes of hyper SFN should not result in system information change notifications. | +| idleModeMeasurementsEUTRA
This field indicates that a UE that is configured for EUTRA idle/inactive measurements shall perform the measurements while camping in this cell and report availability of these measurements when establishing or resuming a connection in this cell. If absent, a UE is not required to perform EUTRA idle/inactive measurements. | + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| idleModeMeasurementsNR
This field indicates that a UE that is configured for NR idle/inactive measurements shall perform the measurements while camping in this cell and report availability of these measurements when establishing or resuming a connection in this cell. If absent, a UE is not required to perform NR idle/inactive measurements. | +| ims-EmergencySupport
Indicates whether the cell supports IMS emergency bearer services for UEs in limited service mode. If absent, IMS emergency call is not supported by the network in the cell for UEs in limited service mode. | +| intraFreqReselection-eRedCap
Controls cell selection/reselection to intra-frequency cells for eRedCap UEs when this cell is barred, or treated as barred by the eRedCap UE, as specified in TS 38.304 [20]. If not present, an eRedCap UE treats the cell as barred, i.e., the UE considers that the cell does not support eRedCap. | +| intraFreqReselectionRedCap
Controls cell selection/reselection to intra-frequency cells for RedCap UEs when this cell is barred, or treated as barred by the RedCap UE, as specified in TS 38.304 [20]. If not present, a RedCap UE treats the cell as barred, i.e., the UE considers that the cell does not support RedCap. | +| mobileIAB-Cell
The presence of this field indicates that this is a mobile IAB cell. | +| musim-CapRestrictionAllowed
Indicates the UE is allowed to send the musim-CapRestrictionInd in RRCEstablishmentComplete and RRCEstablishmentResumeComplete messages. | +| ncr-Support
This field combines both the support of NCR and the cell status for NCR. If the field is present, the cell supports NCR and the cell is also considered as a candidate for cell (re)selection for NCR-node; if the field is absent, the cell does not support NCR and/or the cell is barred for NCR-node. | +| nonServingCellMII
Indicates whether the MBSInterestIndication message for MBS broadcast reception on a non-serving cell is allowed to be transmitted to the serving gNB. | +| q-QualMin
Parameter "Q qualmin " in TS 38.304 [20], applicable for serving cell. If the field is absent, the UE applies the (default) value of negative infinity for Q qualmin . | +| q-QualMinOffset
Parameter "Q qualminoffset " in TS 38.304 [20]. Actual value Q qualminoffset = field value [dB]. If the field is absent, the UE applies the (default) value of 0 dB for Q qualminoffset . Affects the minimum required quality level in the cell. | +| q-RxLevMin
Parameter "Q rxlevmin " in TS 38.304 [20], applicable for serving cell. | +| q-RxLevMinOffset
Parameter "Q rxlevminoffset " in TS 38.304 [20]. Actual value Q rxlevminoffset = field value * 2 [dB]. If absent, the UE applies the (default) value of 0 dB for Q rxlevminoffset . Affects the minimum required Rx level in the cell. | +| q-RxLevMinSUL
Parameter "Q rxlevmin " in TS 38.304 [20], applicable for serving cell. | +| sdt-DataVolumeThreshold
Data volume threshold used to determine whether SDT can be initiated, as specified in TS 38.321 [3]. Value byte32 corresponds to 32 bytes, value byte100 corresponds to 100 bytes, and so on. | +| sdt-LogicalChannelSR-DelayTimer
The value of logicalChannelSR-DelayTimer applied during SDT for logical channels configured with SDT, as specified in TS 38.321 [3]. Value in number of subframes. Value sf20 corresponds to 20 subframes, sf40 corresponds to 40 subframes, and so on. If sdt-LogicalChannelSR-DelayTimer-r18 is absent and sdt-LogicalChannelSR-DelayTimer-r17 is present then, the UE applies the value configured in sdt-LogicalChannelSR-DelayTimer-r17 for this field. If this field is not configured, then logicalChannelSR-DelayTimer is not applied for SDT logical channels. | +| sdt-RSRP-Threshold
RSRP threshold used to determine whether SDT procedure can be initiated, as specified in TS 38.321 [3]. | +| sdt-RSRP-ThresholdMT | + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RSRP threshold used to determine whether MT-SDT procedure can be initiated, as specified in TS 38.321 [3]. If the field is absent, and the field sdt-RSRP-Threshold is present, the UE applies the value in the field sdt-RSRP-Threshold . | +| servingCellConfigCommon
Configuration of the serving cell. | +| t319a
Initial value of the timer T319a used for detection of SDT failure. Value ms100 corresponds to 100 milliseconds, value ms200 corresponds to 200 milliseconds and so on. If t319a-r18 is absent, the UE applies the value configured in t319a-r17 . | +| uac-AccessCategory1-SelectionAssistanceInfo
Information used to determine whether Access Category 1 applies to the UE, as defined in TS 22.261 [25]. If plmnCommon is chosen, the UAC-AccessCategory1-SelectionAssistanceInfo is applicable to all the PLMNs and SNPNs in plmn-IdentityInfoList and npn-IdentityInfoList . If individualPLMNList is chosen, the 1 st entry in the list corresponds to the first network within all of the PLMNs and SNPNs across the plmn-IdentityList and the npn-IdentityInfoList , the 2 nd entry in the list corresponds to the second network within all of the PLMNs and SNPNs across the plmn-IdentityList and the npn-IdentityInfoList and so on. If uac-AC1-SelectAssistInfo-r16 is present, the UE shall ignore the uac-AccessCategory1-SelectionAssistanceInfo . | +| uac-AC1-SelectAssistInfo
Information used to determine whether Access Category 1 applies to the UE, as defined in TS 22.261 [25]. The 1 st entry in the list corresponds to the first network within all of the PLMNs and SNPNs across the plmn-IdentityList and npn-IdentityInfoList , the 2 nd entry in the list corresponds to the second network within all of the PLMNs and SNPNs across the plmn-IdentityList and the npn-IdentityInfoList and so on. Value notConfigured indicates that Access Category 1 is not configured for the corresponding PLMN/SNPN. | +| uac-BarringForCommon
Common access control parameters for each access category. Common values are used for all PLMNs/SNPNs, unless overwritten by the PLMN/SNPN specific configuration provided in uac-BarringPerPLMN-List . The parameters are specified by providing an index to the set of configurations ( uac-BarringInfoSetList ). UE behaviour upon absence of this field is specified in clause 5.3.14.2. | +| ue-TimersAndConstants
Timer and constant values to be used by the UE. The cell operating as PCell always provides this field. | +| useFullResumeID
Indicates which resume identifier and Resume request message should be used. UE uses fullI-RNTI and RRCResumeRequest1 if the field is present, or shortI-RNTI and RRCResumeRequest if the field is absent. | + +| Conditional Presence | Explanation | +|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| EDRX-RC | The field is optionally present, Need R, in a cell that enables eDRX-AllowedIdle , otherwise it is absent. | +| MINT | The field is optionally present, Need R, in a cell that provides a configuration for disaster roaming, otherwise it is absent, Need R. | +| MT-SDT1 | This field is optionally present, Need S, in a cell that supports MT-SDT if sdt-ConfigCommon-r17 is not present, otherwise it is absent. | +| MT-SDT2 | This field is mandatory present in a cell that supports MT-SDT if sdt-ConfigCommon-r17 is not present, otherwise it is absent. | +| Standalone | The field is mandatory present in a cell that supports standalone operation, otherwise it is absent. | + +#### — *SidelinkUEInformationNR* + +The *SidelinkUEInformationNR* message is used for the indication of NR sidelink UE information to the network. + +Signalling radio bearer: SRB1 + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: UE to Network + +#### SidelinkUEInformationNR message + +``` +-- ASN1START +-- TAG-SIDELINKUEINFORMATIONNR-START + +SidelinkUEInformationNR-r16 ::= SEQUENCE { + criticalExtensions CHOICE { + sidelinkUEInformationNR-r16 SidelinkUEInformationNR-r16-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +SidelinkUEInformationNR-r16-IEs ::= SEQUENCE { + sl-RxInterestedFreqList-r16 SL-InterestedFreqList-r16 OPTIONAL, + sl-TxResourceReqlist-r16 SL-TxResourceReqlist-r16 OPTIONAL, + sl-FailureList-r16 SL-FailureList-r16 OPTIONAL, + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension SidelinkUEInformationNR-v1700-IEs OPTIONAL +} + +SidelinkUEInformationNR-v1700-IEs ::= SEQUENCE { + sl-TxResourceReqlist-v1700 SL-TxResourceReqlist-v1700 OPTIONAL, + sl-RxD RX-ReportList-v1700 SL-RxD RX-ReportList-v1700 OPTIONAL, + sl-RxInterestedGC-BC-DestList-r17 SL-RxInterestedGC-BC-DestList-r17 OPTIONAL, + sl-RxInterestedFreqListDisc-r17 SL-InterestedFreqList-r16 OPTIONAL, + sl-TxResourceReqlistDisc-r17 SL-TxResourceReqlistDisc-r17 OPTIONAL, + sl-TxResourceReqlistCommRelay-r17 SL-TxResourceReqlistCommRelay-r17 OPTIONAL, + ue-Type-r17 ENUMERATED {relayUE, remoteUE} OPTIONAL, + sl-SourceIdentityRemoteUE-r17 SL-SourceIdentity-r17 OPTIONAL, + nonCriticalExtension SidelinkUEInformationNR-v1800-IEs OPTIONAL +} + +SidelinkUEInformationNR-v1800-IEs ::= SEQUENCE { + sl-CarrierFailureList-r18 SL-CarrierFailureList-r18 OPTIONAL, + sl-TxResourceReql2-U2U-r18 SL-TxResourceReql2-U2U-r18 OPTIONAL, + sl-PosRxInterestedFreqList-r18 SL-InterestedFreqList-r16 OPTIONAL, + sl-PosTxResourceReqlist-r18 SL-TxResourceReqlist-r16 OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +SL-InterestedFreqList-r16 ::= SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF INTEGER (1..maxNrofFreqSL-r16) +``` + +``` + +SL-TxResourceReqList-r16 ::= SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-TxResourceReq-r16 + +SL-TxResourceReq-r16 ::= SEQUENCE { + sl-DestinationIdentity-r16 SL-DestinationIdentity-r16, + sl-CastType-r16 ENUMERATED {broadcast, groupcast, unicast, spare1}, + sl-RLC-ModeIndicationList-r16 SEQUENCE (SIZE (1..maxNrofSLRB-r16)) OF SL-RLC-ModeIndication-r16 OPTIONAL, + sl-QoS-InfoList-r16 SEQUENCE (SIZE (1..maxNrofSL-QFIsPerDest-r16)) OF SL-QoS-Info-r16 OPTIONAL, + sl-TypeTxSyncList-r16 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF SL-TypeTxSync-r16 OPTIONAL, + sl-TxInterestedFreqList-r16 SL-TxInterestedFreqList-r16 OPTIONAL, + sl-CapabilityInformationSidelink-r16 OCTET STRING OPTIONAL +} + +SL-TxResourceReqList-v1700 ::= SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-TxResourceReq-v1700 + +SL-RxDRX-ReportList-v1700 ::= SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-RxDRX-Report-v1700 + +SL-TxResourceReq-v1700 ::= SEQUENCE { + sl-DRX-InfoFromRxList-r17 SEQUENCE (SIZE (1..maxNrofSL-RxInfoSet-r17)) OF SL-DRX-ConfigUC-SemiStatic-r17 OPTIONAL, + sl-DRX-Indication-r17 ENUMERATED {on, off} OPTIONAL, + ..., + [[ + sl-QoS-InfoList-v1800 SEQUENCE (SIZE (1..maxNrofSL-QFIsPerDest-r16)) OF SL-QoS-Info-v1800 OPTIONAL + ]] +} + +SL-RxDRX-Report-v1700 ::= SEQUENCE { + sl-DRX-ConfigFromTx-r17 SL-DRX-ConfigUC-SemiStatic-r17, + ...} + +SL-RxInterestedGC-BC-DestList-r17 ::= SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-RxInterestedGC-BC-Dest-r17 + +SL-RxInterestedGC-BC-Dest-r17 ::= SEQUENCE { + sl-RxInterestedQoS-InfoList-r17 SEQUENCE (SIZE (1..maxNrofSL-QFIsPerDest-r16)) OF SL-QoS-Info-r16, + sl-DestinationIdentity-r16 SL-DestinationIdentity-r16 +} + +SL-TxResourceReqListDisc-r17 ::= SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-TxResourceReqDisc-r17 + +SL-TxResourceReqDisc-r17 ::= SEQUENCE { + sl-DestinationIdentityDisc-r17 SL-DestinationIdentity-r16, + sl-SourceIdentityRelayUE-r17 SL-SourceIdentity-r17 OPTIONAL, + sl-CastTypeDisc-r17 ENUMERATED {broadcast, groupcast, unicast, spare1}, + sl-TxInterestedFreqListDisc-r17 SL-TxInterestedFreqList-r16, + sl-TypeTxSyncListDisc-r17 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF SL-TypeTxSync-r16, + sl-DiscoveryType-r17 ENUMERATED {relay, non-Relay}, + ... +} + +SL-TxResourceReqListCommRelay-r17 ::= SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-TxResourceReqCommRelayInfo-r17 + +SL-TxResourceReqCommRelayInfo-r17 ::= SEQUENCE { + +``` + +``` + + sl-RelayDRXConfig-r17 SL-TxResourceReq-v1700 OPTIONAL, + sl-TxResourceReqCommRelay-r17 SL-TxResourceReqCommRelay-r17 + } + + SL-TxResourceReqCommRelay-r17 ::= CHOICE { + sl-TxResourceReqL2U2N-Relay-r17 SL-TxResourceReqL2U2N-Relay-r17, + sl-TxResourceReqL3U2N-Relay-r17 SL-TxResourceReq-r16 + } + + SL-TxResourceReqL2U2N-Relay-r17 ::= SEQUENCE { + sl-DestinationIdentityL2U2N-r17 SL-DestinationIdentity-r16 OPTIONAL, + sl-TxInterestedFreqListL2U2N-r17 SL-TxInterestedFreqList-r16, + sl-TypeTxSyncListL2U2N-r17 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF SL-TypeTxSync-r16, + sl-LocalID-Request-r17 ENUMERATED {true} OPTIONAL, + sl-PagingIdentityRemoteUE-r17 SL-PagingIdentityRemoteUE-r17 OPTIONAL, + sl-CapabilityInformationSidelink-r17 OCTET STRING OPTIONAL, + ... + } + + SL-TxResourceReqL2-U2U-r18 ::= SEQUENCE { + sl-DestinationIdentityL2-U2U-r18 SL-DestinationIdentity-r16 OPTIONAL, + sl-TxInterestedFreqListL2-U2U-r18 SL-TxInterestedFreqList-r16, + sl-TypeTxSyncListL2-U2U-r18 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF SL-TypeTxSync-r16, + sl-CapabilityInformationSidelink-r18 OCTET STRING OPTIONAL, + sl-U2U-InfoList-r18 SEQUENCE (SIZE (1.. maxNrofRemoteUE-r17)) OF SL-U2U-Info-r18 OPTIONAL, + ... + } + + SL-U2U-Info-r18 ::= SEQUENCE { + sl-U2U-Identity-r18 CHOICE { + sl-TargetUE-Identity-r18 SL-DestinationIdentity-r16, + sl-SourceUE-Identity-r18 SL-SourceIdentity-r17 + }, + sl-E2E-QoS-InfoList-r18 SEQUENCE (SIZE (1.. maxNrofSL-QFIsPerDest-r16)) OF SL-QoS-Info-r16 OPTIONAL, + sl-PerHop-QoS-InfoList-r18 SEQUENCE (SIZE (1.. maxNrofSL-QFIsPerDest-r16)) OF SL-SplitQoS-Info-r18 OPTIONAL, + sl-PerSLRB-QoS-InfoList-r18 SEQUENCE (SIZE (1.. maxNrofSLRB-r16)) OF SL-PerSLRB-QoS-Info-r18 OPTIONAL + } + + SL-TxInterestedFreqList-r16 ::= SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF INTEGER (1..maxNrofFreqSL-r16) + + SL-QoS-Info-r16 ::= SEQUENCE { + sl-QoS-FlowIdentity-r16 SL-QoS-FlowIdentity-r16, + sl-QoS-Profile-r16 SL-QoS-Profile-r16 OPTIONAL + } + + SL-QoS-Info-v1800 ::= SEQUENCE { + sl-QoS-FlowIdentity-r18 SL-QoS-FlowIdentity-r16, + sl-TxInterestedFreqList-v1800 SL-TxInterestedFreqList-r16 OPTIONAL, + sl-TxProfile-v1800 ENUMERATED {backwardsCompatible, backwardsIncompatible} OPTIONAL, + ... + } + +``` + +``` + +SL-RLC-ModeIndication-r16 ::= SEQUENCE { + sl-Mode-r16 CHOICE { + sl-AM-Mode-r16 NULL, + sl-UM-Mode-r16 NULL + }, + sl-QoS-InfoList-r16 SEQUENCE (SIZE (1..maxNrofSL-QFIsPerDest-r16)) OF SL-QoS-Info-r16 +} + +SL-FailureList-r16 ::= SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-Failure-r16 + +SL-Failure-r16 ::= SEQUENCE { + sl-DestinationIdentity-r16, + sl-Failure-r16 ENUMERATED {rlf,configFailure, drxReject-v1710, spare5, spare4, spare3, spare2, spare1} +} + +SL-CarrierFailureList-r18 ::= SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-CarrierFailure-r18 + +SL-CarrierFailure-r18 ::= SEQUENCE { + sl-DestinationIdentity-r18, + sl-CarrierFailure-r18 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF INTEGER (1..maxNrofFreqSL-r16) +} + +SL-SplitQoS-Info-r18 ::= SEQUENCE { + sl-QoS-FlowIdentity-r18, + sl-SplitPacketDelayBudget-r18 INTEGER (0..1023) OPTIONAL, + ... +} + +SL-PerSLRB-QoS-Info-r18 ::= SEQUENCE { + sl-RemoteUE-SLRB-Identity-r18 SLRB-Uu-ConfigIndex-r16, + sl-QoS-ProfilePerSLRB-r18 SL-QoS-Profile-r16 OPTIONAL +} + +-- TAG-SIDELINKUEINFORMATIONNR-STOP +-- ASN1STOP + +``` + +Editor's Note: Whether the per-SLRB QoS is reported in a list of E2E connections or all in one big list can be further checked in maintenance. + +Editor's Note: Whether to differentiate U2U discovery and U2N discovery can be checked in maintenance. + +| SidelinkUEInformationNR field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-PosRxInterestedFreqList
Indicates the index of frequency on which the UE is interested to receive NR sidelink positioning. The value 1 corresponds to the frequency of first entry in sl-FreqInfoList broadcast in SIB23 , the value 2 corresponds to the frequency of second entry in sl-FreqInfoList broadcast in SIB23 and so on. In this release, only value 1 can be included in the interested frequency list. | +| sl-PosTxResourceReqList
List of parameters to request the transmission resources for NR sidelink positioning for the associated destination. | +| sl-RxDRX-ReportList
Indicates the accepted DRX configuration that is received from the peer UE and reported to the network for NR sidelink unicast communication. | +| sl-RxInterestedFreqList
Indicates the index of frequency on which the UE is interested to receive NR sidelink communication. The value 1 corresponds to the frequency of first entry in sl-FreqInfoList broadcast in SIB12 , the value 2 corresponds to the frequency of first entry in sl-FreqInfoListSizeExt broadcast in SIB12 , the value 3 corresponds to the frequency of second entry in sl-FreqInfoListSizeExt broadcast in SIB12 and so on. | +| sl-RxInterestedGC-BC-DestList
Indicates the reported QoS profile and associated destination for which UE is interested in reception to the network for NR sidelink groupcast and broadcast communication, or for NR sidelink discovery or ProSe Direct Link Establishment Request as described in TS 24.554 [72], or for Direct Link Establishment Request (TS 24.587 [57]). | +| sl-SourceIdentityRemoteUE
This field is used to indicate the Source Layer-2 ID to be used to establish PC5 link with the target L2 U2N Relay UE for path switch. | +| sl-TxResourceReq
Parameters to request the transmission resources for NR sidelink communication to the network in the Sidelink UE Information report. | +| sl-TxResourceReqList
List of parameters to request the transmission resources for NR sidelink communication for the associated destination. If sl-TxResourceReqList-v1700 is present, it shall contain the same number of entries, listed in the same order as in sl-TxResourceReqList-r16 . | +| ue-Type
Indicates the UE is acting as U2N Relay UE or U2N Remote UE. | + +Editor's note: The carrier mapping for *sl-RxInterestedFreqList* is pending R2 discussion. + +| SL-TxResourceReq field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-CapabilityInformationSidelink
Includes the UECapabilityInformationSidelink message (which can be also included in ueCapabilityInformationSidelink-r16 in UECapabilityEnquirySidelink from peer UE) received from the peer UE. | +| sl-CastType
Indicates the cast type for the corresponding destination for which to request the resource. | +| sl-DestinationIdentity
Indicates the destination for which the TX resource request and allocation from the network are concerned. | +| sl-DRX-Indication
Indicates the sidelink DRX is applied (value on ) or not applied (value off ) for the associated destination. This field is only valid for NR sidelink groupcast communication. | +| sl-DRX-InfoFromRxList
Indicates list of the sidelink DRX configurations as assistance information received from the peer UE for NR sidelink unicast communication. | +| sl-QoS-InfoList
Includes the QoS profile of the sidelink QoS flow as specified in TS 23.287 [55]. If sl-QoS-InfoList-v1800 is included, shall include the same number of entries, and listed in the same order, as in sl-QoS-InfoList (without suffix) | +| sl-QoS-FlowIdentity
This identity uniquely identifies one sidelink QoS flow between the UE and the network in the scope of UE, which is unique for different destination and cast type. | +| sl-RLC-ModeIndication
This field indicates the RLC mode and optionally the related QoS profiles for the sidelink radio bearer, which has not been configured by the network and is initiated by another UE in unicast. The RLC mode for one sidelink radio bearer is aligned between UE and NW by the sl-QoS-FlowIdentity . | +| sl-TxInterestedFreqList
Each entry of this field indicates the index of frequency on which the UE is interested to transmit NR sidelink communication/positioning, for each destination. The value 1 corresponds to the frequency of first entry in sl-FreqInfoList broadcast in SIB12 , the value 2 corresponds to the frequency of first entry in sl-FreqInfoListSizeExt broadcast in SIB12 , the value 3 corresponds to the frequency of second entry in sl-FreqInfoListSizeExt broadcast in SIB12 and so on. | +| sl-TypeTxSyncList
A list of synchronization reference used by the UE. The UE shall include the same number of entries, listed in the same order, as in sl-TxInterestedFreqList , i.e. one for each carrier frequency included in sl-TxInterestedFreqList . | + +Editor's note: The carrier mapping for *sl-TxInterestedFreqList* is pending R2 discussion. + +| SL-Failure field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-DestinationIdentity
Indicates the destination for which the SL failure is reporting for unicast. | +| sl-Failure
Indicates the sidelink cause for the sidelink RLF (value RLF ), sidelink AS configuration failure (value configFailure ) and the rejection of sidelink DRX configuration (value drxReject-v1710 ) for the associated destination for unicast. | + +| SL-RxDRX-Report field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------| +| sl-DRX-ConfigFromTx
Indicates the sidelink DRX configuration received from the peer UE for NR sidelink unicast communication. | + +| SL-RxInterestedGC-BC-Dest field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-RxInterestedQoS-InfoList
Indicates the QoS profile for which UE reports its interested service to which SL DRX is applied to the network, for NR sidelink groupcast or broadcast reception. | + +| SL-TxResourceReqDisc field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-CastTypeDisc
Indicates the cast type for the NR sidelink discovery messages. Only value broadcast can be set in this release. | +| sl-DestinationIdentityDisc
This field is used to indicate the destination L2 ID for which the TX resource request and allocation from the network are concerned for relay discovery and non-relay discovery. | +| sl-SourceIdentityRelayUE
This field is used to indicate the source L2 ID of relay-related discovery transmission by L2 U2N Relay UE. | +| sl-TxInterestedFreqListDisc
Each entry of this field indicates the index of frequency on which the UE is interested to transmit NR sidelink discovery. The value 1 corresponds to the frequency of first entry in sl-FreqInfoList broadcast in SIB12 , the value 2 corresponds to the frequency of second entry in sl-FreqInfoList broadcast in SIB12 and so on. In this release, only value 1 can be included in the interested frequency list. In this release, only one entry can be included in the list. | + +| SL-TxResourceReqCommRelayInfo field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-RelayDRXConfig
This field is used to indicate the applied sidelink DRX configuration for the relay related communication. | +| sl-DestinationIdentityL2U2N
This field is used to indicate the destination L2 ID for which the TX resource request and allocation from the network are concerned for the established PC5 link for relay by L2 U2N Relay UE. | +| sl-LocalID-Request
This field is used to request local UE ID for the corresponding destination by the L2 U2N Relay UE. | +| sl-TxInterestedFreqListL2U2N
Each entry of this field indicates the index of frequency on which the UE is interested to transmit NR sidelink communication for established PC5 link for relay. The value 1 corresponds to the frequency of first entry in sl-FreqInfoList broadcast in SIB12 , the value 2 corresponds to the frequency of second entry in sl-FreqInfoList broadcast in SIB12 and so on. In this release, only value 1 can be included in the interested frequency list. In this release, only one entry can be included in the list. | +| sl-PagingIdentityRemoteUE
This field is used to indicate the paging UE ID(s) for the corresponding destination(s) by the L2 U2N Relay UE. | + +| SL-Freq-Info field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

sl-TxInterestedFreqList
Each entry of this field indicates the index of frequency on which the UE is interested to transmit NR sidelink communication, for each QoS flow. The value 1 corresponds to the frequency of first entry in sl-FreqInfoList broadcast in SIB12, the value 2 corresponds to the frequency of first entry in sl-FreqInfoListSizeExt broadcast in SIB12, the value 3 corresponds to the frequency of second entry in sl-FreqInfoListSizeExt broadcast in SIB12 and so on.

| + +| SL-CarrierFailure field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

sl-CarrierFailure
Indicate the carrier(s) where the per-carrier RLF has been indicated by lower layer. The value 1 corresponds to the frequency of first entry in sl-FreqInfoList broadcast in SIB12, the value 2 corresponds to the frequency of first entry in sl-FreqInfoListSizeExt broadcast in SIB12, the value 3 corresponds to the frequency of second entry in sl-FreqInfoListSizeExt broadcast in SIB12 and so on.

| +|

sl-DestinationIdentity
This field is used to indicate the destination L2 ID for which the per-carrier RLF report is concerned.

| + +| SL-TxResourceReqL2-U2U field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

sl-DestinationIdentityL2-U2U
This field is used to indicate the destination L2 ID for which the TX resource request and allocation from the network are concerned for the established per-hop PC5 link between the L2 U2U Remote UE and L2 U2U Relay UE.

| +|

sl-TxInterestedFreqListL2-U2U
Each entry of this field indicates the index of frequency on which the UE is interested to transmit NR sidelink communication for established per-hop PC5 link. The value 1 corresponds to the frequency of first entry in sl-FreqInfoList broadcast in SIB12, the value 2 corresponds to the frequency of second entry in sl-FreqInfoList broadcast in SIB12 and so on. In this release, only value 1 can be included in the interested frequency list. In this release, only one entry can be included in the list.

| +|

sl-U2U-InfoList
This field indicates the information related to a list of end-to-end PC5 links.

| + +| SL-U2U-Info field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

sl-U2U-Identity
This field is to identify a the end-to-end PC5 link. When a L2 U2U Remote UE reports info for the first hop, it includes sl-TargetUE-Identity to indicate the peer L2 Remote UE on the second hop, and when a L2 U2U Relay UE reports info for the second hop, it includes sl-SourceUE-Identity to indicate the source L2 U2U Remote UE on the first hop.

| +|

sl-E2E-QoS-InfoList
This field is used by L2 U2U Remote UE to indicate a list of end-to-end QoS info.

| +|

sl-PerHop-QoS-InfoList
This field is used by L2 U2U Remote UE to indicate a list of split QoS info for the first hop.

| +|

sl-PerSLRB-QoS-InfoList
This field is used by L2 U2U Relay UE to indicate a list of split QoS info for the second hop in per-SLRB level, with each entry in accordance with a end-to-end SLRB.

| + +#### SystemInformation + +The *SystemInformation* message is used to convey one or more System Information Blocks or Positioning System Information Blocks. All the SIBs or posSIBs included are transmitted with the same periodicity. + +Signalling radio bearer: N/A + +RLC-SAP: TM + +Logical channels: BCCH + +Direction: Network to UE + +#### SystemInformation message + +``` +-- ASN1START +-- TAG-SYSTEMINFORMATION-START + +SystemInformation ::= + SEQUENCE { + criticalExtensions + CHOICE { + systemInformation + SystemInformation-IEs, + criticalExtensionsFuture-r16 + CHOICE { + posSystemInformation-r16 + PosSystemInformation-r16-IEs, + criticalExtensionsFuture + SEQUENCE {} + } + } + } + +SystemInformation-IEs ::= + SEQUENCE { + sib-TypeAndInfo + SEQUENCE (SIZE (1..maxSIB)) OF CHOICE { + sib2 + SIB2, + sib3 + SIB3, + sib4 + SIB4, + sib5 + SIB5, + sib6 + SIB6, + sib7 + SIB7, + sib8 + SIB8, + sib9 + SIB9, + ... + sib10-v1610 + SIB10-r16, + sib11-v1610 + SIB11-r16, + sib12-v1610 + SIB12-r16, + sib13-v1610 + SIB13-r16, + sib14-v1610 + SIB14-r16, + sib15-v1700 + SIB15-r17, + sib16-v1700 + SIB16-r17, + sib17-v1700 + SIB17-r17, + sib18-v1700 + SIB18-r17, + } + } +``` + +``` + + sib19-v1700 SIB19-r17, + sib20-v1700 SIB20-r17, + sib21-v1700 SIB21-r17, + sib22-v1800 SIB22-r18, + sib23-v1800 SIB23-r18, + sib24-v1800 SIB24-r18, + sib25-v1800 SIB25-r18 + + }, + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +-- TAG-SYSTEMINFORMATION-STOP +-- ASN1STOP + +``` + +#### – *UEAssistanceInformation* + +The *UEAssistanceInformation* message is used for the indication of UE assistance information to the network. + +Signalling radio bearer: SRB1, SRB3 + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: UE to Network + +#### *UEAssistanceInformation message* + +``` + +-- ASN1START +-- TAG-UEASSISTANCEINFORMATION-START + +UEAssistanceInformation ::= SEQUENCE { + criticalExtensions CHOICE { + ueAssistanceInformation UEAssistanceInformation-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +UEAssistanceInformation-IEs ::= SEQUENCE { + delayBudgetReport DelayBudgetReport OPTIONAL, + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension UEAssistanceInformation-v1540-IEs OPTIONAL +} + +DelayBudgetReport ::= CHOICE { + +``` + +``` + +type1 ENUMERATED { + msMinus1280, msMinus640, msMinus320, msMinus160, msMinus80, msMinus60, msMinus40, + msMinus20, ms0, ms20, ms40, ms60, ms80, ms160, ms320, ms640, ms1280}, + ... +} + +UEAssistanceInformation-v1540-IEs ::= SEQUENCE { + overheatingAssistance OverheatingAssistance OPTIONAL, + nonCriticalExtension UEAssistanceInformation-v1610-IEs OPTIONAL +} + +OverheatingAssistance ::= SEQUENCE { + reducedMaxCCs ReducedMaxCCs-r16 OPTIONAL, + reducedMaxBW-FR1 ReducedMaxBW-FRx-r16 OPTIONAL, + reducedMaxBW-FR2 ReducedMaxBW-FRx-r16 OPTIONAL, + reducedMaxMIMO-LayersFR1 SEQUENCE { + reducedMIMO-LayersFR1-DL MIMO-LayersDL, + reducedMIMO-LayersFR1-UL MIMO-LayersUL + } OPTIONAL, + reducedMaxMIMO-LayersFR2 SEQUENCE { + reducedMIMO-LayersFR2-DL MIMO-LayersDL, + reducedMIMO-LayersFR2-UL MIMO-LayersUL + } OPTIONAL +} + +OverheatingAssistance-r17 ::= SEQUENCE { + reducedMaxBW-FR2-2-r17 SEQUENCE { + reducedBW-FR2-2-DL-r17 ReducedAggregatedBandwidth-r17, + reducedBW-FR2-2-UL-r17 ReducedAggregatedBandwidth-r17 + } OPTIONAL, + reducedMaxMIMO-LayersFR2-2 SEQUENCE { + reducedMIMO-LayersFR2-2-DL MIMO-LayersDL, + reducedMIMO-LayersFR2-2-UL MIMO-LayersUL + } OPTIONAL +} + +ReducedAggregatedBandwidth ::= ENUMERATED {mhz0, mhz10, mhz20, mhz30, mhz40, mhz50, mhz60, mhz80, mhz100, mhz200, mhz300, mhz400} + +ReducedAggregatedBandwidth-r17 ::= ENUMERATED {mhz0, mhz100, mhz200, mhz400, mhz800, mhz1200, mhz1600, mhz2000} + +UEAssistanceInformation-v1610-IEs ::= SEQUENCE { + idc-Assistance-r16 IDC-Assistance-r16 OPTIONAL, + drx-Preference-r16 DRX-Preference-r16 OPTIONAL, + maxBW-Preference-r16 MaxBW-Preference-r16 OPTIONAL, + maxCC-Preference-r16 MaxCC-Preference-r16 OPTIONAL, + maxMIMO-LayerPreference-r16 MaxMIMO-LayerPreference-r16 OPTIONAL, + minSchedulingOffsetPreference-r16 MinSchedulingOffsetPreference-r16 OPTIONAL, + releasePreference-r16 ReleasePreference-r16 OPTIONAL, + sl-UE-AssistanceInformationNR-r16 SL-UE-AssistanceInformationNR-r16 OPTIONAL, + referenceTimeInfoPreference-r16 BOOLEAN OPTIONAL, + nonCriticalExtension UEAssistanceInformation-v1700-IEs OPTIONAL +} + +``` + +``` + +UEAssistanceInformation-v1700-IEs ::= SEQUENCE { + ul-GapFR2-Preference-r17 UL-GapFR2-Preference-r17 OPTIONAL, + musim-Assistance-r17 MUSIM-Assistance-r17 OPTIONAL, + overheatingAssistance-r17 OverheatingAssistance-r17 OPTIONAL, + maxBW-PreferenceFR2-2-r17 MaxBW-PreferenceFR2-2-r17 OPTIONAL, + maxMIMO-LayerPreferenceFR2-2-r17 MaxMIMO-LayerPreferenceFR2-2-r17 OPTIONAL, + minSchedulingOffsetPreferenceExt-r17 MinSchedulingOffsetPreferenceExt-r17 OPTIONAL, + rlm-MeasRelaxationState-r17 BOOLEAN OPTIONAL, + bfd-MeasRelaxationState-r17 BIT STRING (SIZE (1..maxNrofServingCells)) OPTIONAL, + nonSDT-DataIndication-r17 SEQUENCE { + resumeCause-r17 ResumeCause OPTIONAL + } OPTIONAL, + scg-DeactivationPreference-r17 ENUMERATED { scgDeactivationPreferred, noPreference } OPTIONAL, + uplinkData-r17 ENUMERATED { true } OPTIONAL, + rrm-MeasRelaxationFulfilment-r17 BOOLEAN OPTIONAL, + propagationDelayDifference-r17 PropagationDelayDifference-r17 OPTIONAL, + nonCriticalExtension UEAssistanceInformation-v1800-IEs OPTIONAL +} + +UEAssistanceInformation-v1800-IEs ::= SEQUENCE { + idc-FDM-Assistance-r18 IDC-FDM-Assistance-r18 OPTIONAL, + idc-TDM-Assistance-r18 IDC-TDM-Assistance-r18 OPTIONAL, + multiRx-PreferenceFR2-r18 ENUMERATED {single} OPTIONAL, + musim-Assistance-v1800 MUSIM-Assistance-v1800 OPTIONAL, + flightPathInfoAvailable-r18 ENUMERATED {true} OPTIONAL, + ul-TrafficInfo-r18 UL-TrafficInfo-r18 OPTIONAL, + n3c-RelayUE-InfoList-r18 N3C-RelayUE-InfoList-r18 OPTIONAL, + sl-PRS-UE-AssistanceInformationNR-r18 SL-PRS-UE-AssistanceInformationNR-r18 OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +IDC-Assistance-r16 ::= SEQUENCE { + affectedCarrierFreqList-r16 AffectedCarrierFreqList-r16 OPTIONAL, + affectedCarrierFreqCombList-r16 AffectedCarrierFreqCombList-r16 OPTIONAL, + ... +} + +AffectedCarrierFreqList-r16 ::= SEQUENCE (SIZE (1.. maxFreqIDC-r16)) OF AffectedCarrierFreq-r16 + +AffectedCarrierFreq-r16 ::= SEQUENCE { + carrierFreq-r16 ARFCN-ValueNR, + interferenceDirection-r16 ENUMERATED {nr, other, both, spare} +} + +AffectedCarrierFreqCombList-r16 ::= SEQUENCE (SIZE (1..maxCombIDC-r16)) OF AffectedCarrierFreqComb-r16 + +AffectedCarrierFreqComb-r16 ::= SEQUENCE { + affectedCarrierFreqComb-r16 SEQUENCE (SIZE (2..maxNrofServingCells)) OF ARFCN-ValueNR OPTIONAL, + victimSystemType-r16 VictimSystemType-r16 +} + +``` + +``` + +VictimSystemType-r16 ::= SEQUENCE { + gps-r16 ENUMERATED {true} OPTIONAL, + glonass-r16 ENUMERATED {true} OPTIONAL, + bds-r16 ENUMERATED {true} OPTIONAL, + galileo-r16 ENUMERATED {true} OPTIONAL, + navIC-r16 ENUMERATED {true} OPTIONAL, + wlan-r16 ENUMERATED {true} OPTIONAL, + bluetooth-r16 ENUMERATED {true} OPTIONAL, + ..., + [[ + uwb-r18 ENUMERATED {true} OPTIONAL + ]] +} + +DRX-Preference-r16 ::= SEQUENCE { + preferredDRX-InactivityTimer-r16 ENUMERATED { + ms0, ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, ms80, + ms100, ms200, ms300, ms500, ms750, ms1280, ms1920, ms2560, spare9, spare8, + spare7, spare6, spare5, spare4, spare3, spare2, spare1} OPTIONAL, + preferredDRX-LongCycle-r16 ENUMERATED { + ms10, ms20, ms32, ms40, ms60, ms64, ms70, ms80, ms128, ms160, ms256, ms320, ms512, + ms640, ms1024, ms1280, ms2048, ms2560, ms5120, ms10240, spare12, spare11, spare10, + spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 } OPTIONAL, + preferredDRX-ShortCycle-r16 ENUMERATED { + ms2, ms3, ms4, ms5, ms6, ms7, ms8, ms10, ms14, ms16, ms20, ms30, ms32, + ms35, ms40, ms64, ms80, ms128, ms160, ms256, ms320, ms512, ms640, spare9, + spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 } OPTIONAL, + preferredDRX-ShortCycleTimer-r16 INTEGER (1..16) OPTIONAL +} + +MaxBW-Preference-r16 ::= SEQUENCE { + reducedMaxBW-FR1-r16 ReducedMaxBW-FRx-r16 OPTIONAL, + reducedMaxBW-FR2-r16 ReducedMaxBW-FRx-r16 OPTIONAL +} + +MaxBW-PreferenceFR2-2-r17 ::= SEQUENCE { + reducedMaxBW-FR2-2-r17 SEQUENCE { + reducedBW-FR2-2-DL-r17 ReducedAggregatedBandwidth-r17 OPTIONAL, + reducedBW-FR2-2-UL-r17 ReducedAggregatedBandwidth-r17 OPTIONAL + } OPTIONAL +} + +MaxCC-Preference-r16 ::= SEQUENCE { + reducedMaxCCs-r16 ReducedMaxCCs-r16 OPTIONAL +} + +MaxMIMO-LayerPreference-r16 ::= SEQUENCE { + reducedMaxMIMO-LayersFR1-r16 SEQUENCE { + reducedMIMO-LayersFR1-DL-r16 INTEGER (1..8), + reducedMIMO-LayersFR1-UL-r16 INTEGER (1..4) + } +} + +``` + +``` + + } OPTIONAL, + reducedMaxMIMO-LayersFR2-r16 SEQUENCE { + reducedMIMO-LayersFR2-DL-r16 INTEGER (1..8), + reducedMIMO-LayersFR2-UL-r16 INTEGER (1..4) + } OPTIONAL +} + +MaxMIMO-LayerPreferenceFR2-2-r17 ::= SEQUENCE { + reducedMaxMIMO-LayersFR2-2-r17 SEQUENCE { + reducedMIMO-LayersFR2-2-DL-r17 INTEGER (1..8), + reducedMIMO-LayersFR2-2-UL-r17 INTEGER (1..4) + } OPTIONAL +} + +MinSchedulingOffsetPreference-r16 ::= SEQUENCE { + preferredK0-r16 SEQUENCE { + preferredK0-SCS-15kHz-r16 ENUMERATED {sl1, sl2, sl4, sl6} OPTIONAL, + preferredK0-SCS-30kHz-r16 ENUMERATED {sl1, sl2, sl4, sl6} OPTIONAL, + preferredK0-SCS-60kHz-r16 ENUMERATED {sl2, sl4, sl8, sl12} OPTIONAL, + preferredK0-SCS-120kHz-r16 ENUMERATED {sl2, sl4, sl8, sl12} OPTIONAL + } OPTIONAL, + preferredK2-r16 SEQUENCE { + preferredK2-SCS-15kHz-r16 ENUMERATED {sl1, sl2, sl4, sl6} OPTIONAL, + preferredK2-SCS-30kHz-r16 ENUMERATED {sl1, sl2, sl4, sl6} OPTIONAL, + preferredK2-SCS-60kHz-r16 ENUMERATED {sl2, sl4, sl8, sl12} OPTIONAL, + preferredK2-SCS-120kHz-r16 ENUMERATED {sl2, sl4, sl8, sl12} OPTIONAL + } OPTIONAL +} + +MinSchedulingOffsetPreferenceExt-r17 ::= SEQUENCE { + preferredK0-r17 SEQUENCE { + preferredK0-SCS-480kHz-r17 ENUMERATED {sl8, sl16, sl32, sl48} OPTIONAL, + preferredK0-SCS-960kHz-r17 ENUMERATED {sl8, sl16, sl32, sl48} OPTIONAL + } OPTIONAL, + preferredK2-r17 SEQUENCE { + preferredK2-SCS-480kHz-r17 ENUMERATED {sl8, sl16, sl32, sl48} OPTIONAL, + preferredK2-SCS-960kHz-r17 ENUMERATED {sl8, sl16, sl32, sl48} OPTIONAL + } OPTIONAL +} + +MUSIM-Assistance-r17 ::= SEQUENCE { + musim-PreferredRRC-State-r17 ENUMERATED {idle, inactive, outOfConnected} OPTIONAL, + musim-GapPreferenceList-r17 MUSIM-GapPreferenceList-r17 OPTIONAL +} + +MUSIM-GapPreferenceList-r17 ::= SEQUENCE (SIZE (1..4)) OF MUSIM-GapInfo-r17 + +MUSIM-Assistance-v1800 ::= SEQUENCE { + musim-GapPriorityPreferenceList-r18 MUSIM-GapPriorityPreferenceList-r18 OPTIONAL, + musim-GapKeepPreference-r18 ENUMERATED {true} OPTIONAL, + +``` + +``` + + musim-CapRestriction-r18 MUSIM-CapRestriction-r18 OPTIONAL, + musim-NeedForGapsInfoNR-r18 NeedForGapsInfoNR-r16 OPTIONAL +} + +MUSIM-GapPriorityPreferenceList-r18 ::= SEQUENCE (SIZE (1..3)) OF GapPriority-r17 +MUSIM-CapRestriction-r18 ::= SEQUENCE { + musim-Cell-SCG-ToRelease-r18 MUSIM-Cell-SCG-ToRelease-r18 OPTIONAL, + musim-CellToAffectList-r18 MUSIM-CellToAffectList-r18 OPTIONAL, + musim-AffectedBandsList-r18 MUSIM-AffectedBandsList-r18 OPTIONAL, + musim-AvoidedBandsList-r18 MUSIM-AvoidedBandsList-r18 OPTIONAL, + musim-MaxCC-r18 MUSIM-MaxCC-r18 OPTIONAL +} + +MUSIM-Cell-SCG-ToRelease-r18 ::= SEQUENCE { + musim-CellToRelease-r18 MUSIM-CellToRelease-r18 OPTIONAL, + scg-ReleasePreference-r18 ENUMERATED { scgReleasePreferred } OPTIONAL +} + +MUSIM-CellToRelease-r18 ::= SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellIndex + +MUSIM-CellToAffectList-r18 ::= SEQUENCE (SIZE (1..maxNrofServingCells)) OF MUSIM-CellToAffect-r18 + +MUSIM-CellToAffect-r18 ::= SEQUENCE { + musim-SCellIndex-r18 ServCellIndex, + musim-MIMO-Layers-DL-r18 INTEGER (1..8) OPTIONAL, + musim-MIMO-Layers-UL-r18 INTEGER (1..4) OPTIONAL, + musim-SupportedBandwidth-DL-r18 SupportedBandwidth OPTIONAL, + musim-SupportedBandwidth-UL-r18 SupportedBandwidth OPTIONAL +} + +MUSIM-AffectedBandsList-r18 ::= SEQUENCE (SIZE (1..maxBandComb)) OF MUSIM-AffectedBands-r18 + +MUSIM-AffectedBands-r18 ::= SEQUENCE (SIZE (1..maxSimultaneousBands)) OF MUSIM-CapabilityRestrictedBandParameters + +MUSIM-CapabilityRestrictedBandParameters ::= SEQUENCE { + bandEntryIndex BandEntryIndex, + musim-CapabilityRestricted-r18 SEQUENCE { + musim-MIMO-Layers-DL-r18 INTEGER (1..8) OPTIONAL, + musim-MIMO-Layers-UL-r18 INTEGER (1..4) OPTIONAL, + musim-SupportedBandwidth-DL-r18 SupportedBandwidth OPTIONAL, + musim-SupportedBandwidth-UL-r18 SupportedBandwidth OPTIONAL + } +} + +MUSIM-AvoidedBandsList-r18 ::= SEQUENCE (SIZE (1..maxBandComb)) OF MUSIM-AvoidedBands-r18 + +MUSIM-AvoidedBands-r18 ::= SEQUENCE (SIZE (1..maxSimultaneousBands)) OF BandEntryIndex + +BandEntryIndex ::= INTEGER(1.. maxCandidateBandIndex-r18) + +MUSIM-MaxCC-r18 ::= SEQUENCE { + +``` + +``` + + musim-MaxCC-DL-r18 INTEGER (1..32) OPTIONAL, + musim-MaxCC-UL-r18 INTEGER (1..32) OPTIONAL +} + +ReleasePreference-r16 ::= SEQUENCE { + preferredRRC-State-r16 ENUMERATED {idle, inactive, connected, outOfConnected} +} + +ReducedMaxBW-FRx-r16 ::= SEQUENCE { + reducedBW-DL-r16 ReducedAggregatedBandwidth, + reducedBW-UL-r16 ReducedAggregatedBandwidth +} + +ReducedMaxCCs-r16 ::= SEQUENCE { + reducedCCsDL-r16 INTEGER (0..31), + reducedCCsUL-r16 INTEGER (0..31) +} + +SL-UE-AssistanceInformationNR-r16 ::= SEQUENCE (SIZE (1..maxNrofTrafficPattern-r16)) OF SL-TrafficPatternInfo-r16 + +SL-TrafficPatternInfo-r16 ::= SEQUENCE { + trafficPeriodicity-r16 ENUMERATED {ms20, ms50, ms100, ms200, ms300, ms400, ms500, ms600, ms700, ms800, ms900, ms1000}, + timingOffset-r16 INTEGER (0..10239), + messageSize-r16 BIT STRING (SIZE (8)), + sl-QoS-FlowIdentity-r16 SL-QoS-FlowIdentity-r16 +} + +UL-GapFR2-Preference-r17 ::= SEQUENCE { + ul-GapFR2-PatternPreference-r17 INTEGER (0..3) OPTIONAL +} + +PropagationDelayDifference-r17 ::= SEQUENCE (SIZE (1..4)) OF INTEGER (-270..270) + +IDC-FDM-Assistance-r18 ::= SEQUENCE { + affectedCarrierFreqRangeList-r18 AffectedCarrierFreqRangeList-r18 OPTIONAL, + affectedCarrierFreqRangeCombList-r18 AffectedCarrierFreqRangeCombList-r18 OPTIONAL, + ... +} + +IDC-TDM-Assistance-r18 ::= SEQUENCE { + cycleLength-r18 ENUMERATED {ms2, ms3, ms4, ms5, ms6, ms7, ms8, ms10, ms14, ms16, ms20, ms30, + ms32, ms35, ms40, ms60, ms64, ms70, ms80, ms96, ms100, ms128, ms160, + ms256, ms320, ms512, ms640, ms1024, ms1280, ms2048, ms2560, ms5120, ms10240}, + startOffset-r18 INTEGER (0..10239), + slotOffset-r18 INTEGER (0..31), + activeDuration-r18 CHOICE { + subMilliSeconds INTEGER (1..31), + milliSeconds ENUMERATED { + ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, + ms80, ms100, ms200, ms300, ms400, ms500, ms600, ms800, ms1000, ms1200, + ms1600, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 } + } +} + +``` + +``` + + } +} + +AffectedCarrierFreqRangeList-r18 ::= SEQUENCE (SIZE (1..maxFreqIDC-r16)) OF AffectedCarrierFreqRange-r18 + +AffectedCarrierFreqRange-r18 ::= SEQUENCE { + affectedFreqRange-r18 AffectedFreqRange-r18, interferenceDirection-r18 ENUMERATED {nr, other, both, spare}, + victimSystemType-r18 VictimSystemType-r16 OPTIONAL +} + +AffectedCarrierFreqRangeCombList-r18 ::= SEQUENCE (SIZE (1..maxCombIDC-r16)) OF AffectedCarrierFreqRangeComb-r18 + +AffectedCarrierFreqRangeComb-r18 ::= SEQUENCE { + affectedCarrierFreqRangeComb-r18 SEQUENCE (SIZE (2..maxNrofServingCells)) OF AffectedFreqRange-r18, + interferenceDirection-r18 ENUMERATED {nr, other, both, spare}, + victimSystemType-r18 VictimSystemType-r16 OPTIONAL +} + +AffectedFreqRange-r18 ::= SEQUENCE { + centerFreq-r18 ARFCN-ValueNR, + affectedBandwidth-r18 ENUMERATED {khz200, khz400, khz600, khz800, mhz1, mhz2, mhz3, mhz4, mhz5, mhz6, + mhz8, mhz10, mhz20, mhz30, mhz40, mhz50, mhz60, mhz80, mhz100, mhz200, + mhz300, mhz400} +} + +UL-TrafficInfo-r18 ::= SEQUENCE (SIZE (1..maxNrofPDU-Sessions-r17)) OF PDU-SessionUL-TrafficInfo-r18 + +PDU-SessionUL-TrafficInfo-r18 ::= SEQUENCE { + pdu-SessionID-r18 PDU-SessionID, + qos-FlowUL-TrafficInfoList-r18 SEQUENCE (SIZE (1..maxNrofQFIs)) OF QOS-FlowUL-TrafficInfo-r18 +} + +QOS-FlowUL-TrafficInfo-r18 ::= SEQUENCE { + qfi-r18 INTEGER (0..maxQFI), + jitterRange-r18 SEQUENCE { + lowerBound-r18 JitterBound-r18, + upperBound-r18 JitterBound-r18 + } OPTIONAL, + burstArrivalTime-r18 CHOICE { + referenceTime ReferenceTime-r16, + referenceSFN-AndSlot ReferenceSFN-AndSlot-r18 + } OPTIONAL, + trafficPeriodicity-r18 INTEGER (1..640000) OPTIONAL, + pduSetIdentification-r18 BOOLEAN OPTIONAL, + ... +} + +ReferenceSFN-AndSlot-r18 ::= SEQUENCE { + referenceSFN-r18 INTEGER (0..1023), + referenceSlot-r18 INTEGER (0..639) +} + +``` + +``` +JitterBound-r18 ::= ENUMERATED {ms0, ms0dot5, ms1, ms1dot5, ms2, ms2dot5, ms3, ms3dot5, ms4, ms4dot5, ms5, ms5dot5, ms6, ms6dot5, ms7, beyondMs7} + +N3C-RelayUE-InfoList-r18 ::= SEQUENCE (SIZE (0..8)) OF N3C-RelayUE-Info-r18 -- Editor's note: Upper limit 8 is FFS. + +N3C-RelayUE-Info-r18 ::= SEQUENCE { + n3c-RelayIdentification-r18 SEQUENCE { + n3c-CellGlobalId-r18 SEQUENCE { + n3c-PLMN-Id-r18 PLMN-Identity, + n3c-CellIdentity-r18 CellIdentity + }, + n3c-C-RNTI-r18 RNTI-Value + } +} + +SL-PRS-UE-AssistanceInformationNR-r18 ::= SEQUENCE (SIZE (1..maxNrofSL-PRS-TxConfig-r18)) OF SL-PRS-TxInfo-r18 + +SL-PRS-TxInfo-r18 ::= SEQUENCE { + sl-PRS-Periodicity-r18 ENUMERATED {ms100, ms200, ms300, ms400, ms500, ms600, ms700, ms800, ms900, ms1000, spare6, + spare5, spare4, spare3, spare2, spare1}, + sl-PRS-Priority-r18 INTEGER (1..8) OPTIONAL, + sl-PRS-DelayBudget-r18 INTEGER (0..1023) OPTIONAL +} + +--Editor's Note: sl-PRS-Priority and sl-PRS-DelayBudgetis FFS. + +-- TAG-UEASSISTANCEINFORMATION-STOP +-- ASN1STOP +``` + +| UEAssistanceInformation field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| activeDuration
Indicates the UE's preferred active duration due to the IDC problem. Value in multiples of 1/32 ms (subMilliSeconds) or in ms (milliSecond). For the latter, value ms1 corresponds to 1 ms, value ms2 corresponds to 2 ms, and so on. | +| affectedBandwidth
Indicates the bandwidth around the center frequency of the carrier frequency range which is affected by the IDC problem. Value mhz5 corresponds to 5 MHz, value mhz10 corresponds to 10 MHz and so on. If candidateBandwidth is not configured, the UE is allowed to report the frequency range for any bandwidth as indicated by affectedBandwidth , within the frequency band limitation as defined in TS 38.101-1 [15], TS 38.101-2 [39], TS 38.101-3 [34] and TS 38.101-5 [75]. | +| affectedCarrierFreqList
Indicates a list of NR carrier frequencies that are affected by IDC problem. | +| affectedCarrierFreqRangeList
Indicates a list of NR carrier frequency ranges that are affected by IDC problem. | +| affectedCarrierFreqCombList
Indicates a list of NR carrier frequency combinations that are affected by IDC problems due to Inter-Modulation Distortion and harmonics from NR when configured with UL CA or NR-DC. | +| affectedCarrierFreqRangeCombList
Indicates a list of NR carrier frequency range combinations that are affected by IDC problems due to Inter-Modulation Distortion and harmonics from NR when configured with UL CA or NR-DC | +| bfd-MeasRelaxationState
Indicates the relaxation state of BFD measurements. Each bit corresponds to a serving cell of the cell group. A serving cell is mapped to the ( servCellIndex+1 )-th bit, starting from MSB. A bit that is set to 1 indicates that the UE is performing BFD measurements relaxation on the serving cell mapped on the bit. A bit that is set to 0 indicates that the UE is not performing BFD measurements relaxation on the serving cell mapped on the bit. If a serving cell is not configured to the UE, the corresponding bit is set to 0. | +| centerFreq
Indicates the center frequency of the carrier frequency range which is affected by the IDC problem. | +| cycleLength
Indicates the UE's preferred cycle length due to the IDC problem. Value in ms. Value ms2 corresponds to 2 ms, value ms3 corresponds to 3 ms, and so on. | +| delayBudgetReport
Indicates the UE-preferred adjustment to connected mode DRX. | +| interferenceDirection
Indicates the direction of IDC interference. Value nr indicates that only NR is victim of IDC interference, value other indicates that only another radio is victim of IDC interference and value both indicates that both NR and another radio are victims of IDC interference. The other radio refers to either the ISM radio or GNSS (see TR 36.816 [44]). | +| maxCandidateBandIndex
Indicate the maximum number of band entry index for MUSIM capability restriction reporting. | +| minSchedulingOffsetPreference
Indicates the UE's preferences on minimumSchedulingOffset of cross-slot scheduling for power saving. | +| minSchedulingOffsetPreferenceExt
Indicates the UE's preferences on minimumSchedulingOffset of cross-slot scheduling for power saving for SCS 480 kHz and/or 960 kHz. | +| multiRx-PreferenceFR2
Indicates the UE's preference on single FR2 Rx operation to address overheating or power saving. This field is allowed to be reported only when UE is configured with serving cells operating on FR2. | +| musim-AffectedBandsList
Indicates the UE's preference on the band(s) and/or combination(s) of bands with restricted capability for MUSIM operation. | + +| UEAssistanceInformation field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| activeDuration
Indicates the UE's preferred active duration due to the IDC problem. Value in multiples of 1/32 ms (subMilliSeconds) or in ms (milliSecond). For the latter, value ms1 corresponds to 1 ms, value ms2 corresponds to 2 ms, and so on. | +| affectedBandwidth
Indicates the bandwidth around the center frequency of the carrier frequency range which is affected by the IDC problem. Value mhz5 corresponds to 5 MHz, value mhz10 corresponds to 10 MHz and so on. If candidateBandwidth is not configured, the UE is allowed to report the frequency range for any bandwidth as indicated by affectedBandwidth , within the frequency band limitation as defined in TS 38.101-1 [15], TS 38.101-2 [39], TS 38.101-3 [34] and TS 38.101-5 [75]. | +| musim-AvoidedBandsList
Indicates the UE's preference on band(s) and/or combination(s) of bands to be avoided or MUSIM purpose. | +| musim-capabilityRestricted
Indicates the UE's preference on the temporary capability restriction on the band(s) and/or combination(s) of bands for MUSIM operation. | +| musim-Cell-SCG-ToReleasedList
Indicates the UE's preference on serving cell(s) and/or SCG to be released for MUSIM operation. | +| musim-CellToAffectList-r18
Indicates the UE's preference on the temporary capability restriction on the serving cell(s) for MUSIM operation. | +| musim-GapKeepPreference
Indicates the UE's preference to keep all collided gaps for requested MUSIM gap(s). If the field is absent, the collided MUSIM gaps with lower priority shall be dropped. | +| musim-GapPreferenceList
Indicates the UE's MUSIM gap preference and related MUSIM gap configuration, as defined in TS 38.133 [14] clause 9.1.10. | +| musim-GapPriorityPreferenceList
Indicates the UE's MUSIM gap priority preference for periodic MUSIM gaps as specified in TS 38.133[14].
If the UE includes musim-GapPriorityPreferenceList-r18 , it includes the same number of entries, and listed in the same order for periodic gaps, as in musim-GapPreferenceList-r17 . | +| musim-MaxCC
Indicates the UE maximum number of CCs per DL/UL. | +| musim-NeedForGapsInfoNR
This field is used to indicate the measurement gap requirement information of the UE for NR target bands when in MUSIM operation. The field is not included in NR-DC. | +| musim-PreferredRRC-State
Indicates the UE's preferred RRC state when leaving RRC_CONNECTED. | +| nonSDT-DataIndication
Informs the network about the arrival of data and/or signaling mapped to radio bearers not configured for SDT while SDT procedure is ongoing. | +| preferredDRX-InactivityTimer
Indicates the UE's preferred DRX inactivity timer length for power saving. Value in ms (milliSecond). ms0 corresponds to 0, ms1 corresponds to 1 ms, ms2 corresponds to 2 ms, and so on. If the field is absent from the DRX-Preference IE, it is interpreted as the UE having no preference for the DRX inactivity timer. If secondary DRX group is configured, the preferredDRX-InactivityTimer only applies to the default DRX group. | +| preferredDRX-LongCycle
Indicates the UE's preferred long DRX cycle length for power saving. Value in ms. ms10 corresponds to 10ms, ms20 corresponds to 20 ms, ms32 corresponds to 32 ms, and so on. If preferredDRX-ShortCycle is provided, the value of preferredDRX-LongCycle shall be a multiple of the preferredDRX-ShortCycle value. If the field is absent from the DRX-Preference IE, it is interpreted as the UE having no preference for the long DRX cycle. | +| preferredDRX-ShortCycle
Indicates the UE's preferred short DRX cycle length for power saving. Value in ms. ms2 corresponds to 2ms, ms3 corresponds to 3 ms, ms4 corresponds to 4 ms, and so on. If the field is absent from the DRX-Preference IE, it is interpreted as the UE having no preference for the short DRX cycle. | + +| UEAssistanceInformation field descriptions | | +|---------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| activeDuration | Indicates the UE's preferred active duration due to the IDC problem. Value in multiples of 1/32 ms (subMilliSeconds) or in ms (milliSecond). For the latter, value ms1 corresponds to 1 ms, value ms2 corresponds to 2 ms, and so on. | +| affectedBandwidth | Indicates the bandwidth around the center frequency of the carrier frequency range which is affected by the IDC problem. Value mhz5 corresponds to 5 MHz, value mhz10 corresponds to 10 MHz and so on. If candidateBandwidth is not configured, the UE is allowed to report the frequency range for any bandwidth as indicated by affectedBandwidth , within the frequency band limitation as defined in TS 38.101-1 [15], TS 38.101-2 [39], TS 38.101-3 [34] and TS 38.101-5 [75]. | +| preferredDRX-ShortCycleTimer | Indicates the UE's preferred short DRX cycle timer for power saving. Value in multiples of preferredDRX-ShortCycle . A value of 1 corresponds to preferredDRX-ShortCycle , a value of 2 corresponds to 2 * preferredDRX-ShortCycle and so on. If the field is absent from the DRX-Preference IE, it is interpreted as the UE having no preference for the short DRX cycle timer. A preference for the short DRX cycle is indicated when a preference for the short DRX cycle timer is indicated. | +| preferredK0 | Indicates the UE's preferred value of k0 (slot offset between DCI and its scheduled PDSCH - see TS 38.214 [19], clause 5.1.2.1) for cross-slot scheduling for power saving. Value is defined for each subcarrier spacing (numerology) in units of slots. s1 corresponds to 1 slot, s2 corresponds to 2 slots, s4 corresponds to 4 slots, and so on. If a value for a subcarrier spacing is absent, it is interpreted as the UE having no preference on k0 for cross-slot scheduling for that subcarrier spacing. If the field is absent from the MinSchedulingOffsetPreference IE, it is interpreted as the UE having no preference on k0 for cross-slot scheduling. | +| preferredK2 | Indicates the UE's preferred value of k2 (slot offset between DCI and its scheduled PUSCH - see TS 38.214 [19], clause 6.1.2.1) for cross-slot scheduling for power saving. Value is defined for each subcarrier spacing (numerology) in units of slots. s1 corresponds to 1 slot, s2 corresponds to 2 slots, s4 corresponds to 4 slots, and so on. If a value for a subcarrier spacing is absent, it is interpreted as the UE having no preference on k2 for cross-slot scheduling for that subcarrier spacing. If the field is absent from the MinSchedulingOffsetPreference IE, it is interpreted as the UE having no preference on k2 for cross-slot scheduling. | +| preferredRRC-State | Indicates the UE's preferred RRC state. The value idle is indicated if the UE prefers to be released from RRC_CONNECTED and transition to RRC_IDLE. The value inactive is indicated if the UE prefers to be released from RRC_CONNECTED and transition to RRC_INACTIVE. The value connected is indicated if the UE prefers to revert an earlier indication to leave RRC_CONNECTED state. The value outOfConnected is indicated if the UE prefers to be released from RRC_CONNECTED and has no preferred RRC state to transition to. The value connected can only be indicated if the UE is configured with connectedReporting . | +| propagationDelayDifference | Indicates the one-way service link propagation delay difference between serving cell and each neighbour cell included in neighCellInfoList , defined as neighbour cell's service link propagation delay minus serving cell's service link propagation delay, in number of ms. First entry in propagationDelayDifference corresponds to first entry in neighCellInfoList , second entry in propagationDelayDifference corresponds to second entry in neighCellInfoList , and so on. | +| reducedMaxBW-FR1 | Indicates the UE's preference on reduced configuration corresponding to the maximum aggregated bandwidth across all downlink carrier(s) and across all uplink carrier(s) of FR1, to address overheating or power saving. This field is allowed to be reported only when UE is configured with serving cell(s) operating on FR1. The aggregated bandwidth across all downlink carrier(s) of FR1 is the sum of bandwidth of active downlink BWP(s) across all activated downlink carrier(s) of FR1. The aggregated bandwidth across all uplink carrier(s) of FR1 is the sum of bandwidth of active uplink BWP(s) across all activated uplink carrier(s) of FR1. If the field is absent from the MaxBW-Preference IE or the OverheatingAssistance IE, it is interpreted as the UE having no preference on the maximum aggregated bandwidth of FR1. When indicated to address overheating, this maximum aggregated bandwidth includes carrier(s) of FR1 of both the NR MCG and the SCG. This maximum aggregated bandwidth only includes carriers of FR1 of the SCG in (NG)EN-DC. Value mhz0 is not used when indicated to address overheating. When indicated to address power saving, this maximum aggregated bandwidth includes carrier(s) of FR1 of the cell group that this UE assistance information is associated with. The aggregated bandwidth can only range up to the current active configuration when indicated to address power savings. | + +| UEAssistanceInformation field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

activeDuration
Indicates the UE's preferred active duration due to the IDC problem. Value in multiples of 1/32 ms (subMilliSeconds) or in ms (milliSecond). For the latter, value ms1 corresponds to 1 ms, value ms2 corresponds to 2 ms, and so on.

| +|

affectedBandwidth
Indicates the bandwidth around the center frequency of the carrier frequency range which is affected by the IDC problem. Value mhz5 corresponds to 5 MHz, value mhz10 corresponds to 10 MHz and so on. If candidateBandwidth is not configured, the UE is allowed to report the frequency range for any bandwidth as indicated by affectedBandwidth, within the frequency band limitation as defined in TS 38.101-1 [15], TS 38.101-2 [39], TS 38.101-3 [34] and TS 38.101-5 [75].

| +|

reducedMaxBW-FR2
Indicates the UE's preference on reduced configuration corresponding to the maximum aggregated bandwidth across all downlink carrier(s) and across all uplink carrier(s) of FR2-1, to address overheating or power saving. This field is allowed to be reported only when UE is configured with serving cell(s) operating on FR2-1. The aggregated bandwidth across all downlink carrier(s) of FR2-1 is the sum of bandwidth of active downlink BWP(s) across all activated downlink carrier(s) of FR2-1. The aggregated bandwidth across all uplink carrier(s) of FR2-1 is the sum of bandwidth of active uplink BWP(s) across all activated uplink carrier(s) of FR2-1. If the field is absent from the MaxBW-Preference IE or the OverheatingAssistance IE, it is interpreted as the UE having no preference on the maximum aggregated bandwidth of FR2-1. When indicated to address overheating, this maximum aggregated bandwidth includes carrier(s) of FR2-1 of both the NR MCG and the NR SCG. This maximum aggregated bandwidth only includes carriers of FR2-1 of the SCG in (NG)EN-DC. When indicated to address power saving, this maximum aggregated bandwidth includes carrier(s) of FR2-1 of the cell group that this UE assistance information is associated with. The aggregated bandwidth can only range up to the current active configuration when indicated to address power savings.

| +|

reducedMaxBW-FR2-2
Indicates the UE's preference on reduced configuration corresponding to the maximum aggregated bandwidth across all downlink carrier(s) and across all uplink carrier(s) of FR2-2, to address overheating or power saving. This field is allowed to be reported only when UE is configured with serving cell(s) operating on FR2-2. The aggregated bandwidth across all downlink carrier(s) of FR2-2 is the sum of bandwidth of active downlink BWP(s) across all activated downlink carrier(s) of FR2-2. The aggregated bandwidth across all uplink carrier(s) of FR2-2 is the sum of bandwidth of active uplink BWP(s) across all activated uplink carrier(s) of FR2-2. If the field is absent from the MaxBW-PreferenceFR2-2 IE or the OverheatingAssistance IE, it is interpreted as the UE having no preference on the maximum aggregated bandwidth of FR2-2. When indicated to address overheating, this maximum aggregated bandwidth includes carrier(s) of FR2-2 of both the NR MCG and the NR SCG. This maximum aggregated bandwidth only includes carriers of FR2-2 of the SCG in (NG)EN-DC. When indicated to address power saving, this maximum aggregated bandwidth includes carrier(s) of FR2-2 of the cell group that this UE assistance information is associated with. The aggregated bandwidth can only range up to the current active configuration when indicated to address power savings.

| +|

reducedCCsDL
Indicates the UE's preference on reduced configuration corresponding to the maximum number of downlink SCells indicated by the field, to address overheating or power saving. When indicated to address overheating, this maximum number includes both SCells of the NR MCG and PSCell/SCells of the SCG. This maximum number only includes PSCell/SCells of the SCG in (NG)EN-DC. When indicated to address power saving, this maximum number includes PSCell/SCells of the cell group that this UE assistance information is associated with. The maximum number of downlink SCells can only range up to the current active configuration when indicated to address power savings.

| +|

reducedCCsUL
Indicates the UE's preference on reduced configuration corresponding to the maximum number of uplink SCells indicated by the field, to address overheating or power saving. When indicated to address overheating, this maximum number includes both SCells of the NR MCG and PSCell/SCells of the SCG. This maximum number only includes PSCell/SCells of the SCG in (NG)EN-DC. When indicated to address power saving, this maximum number includes PSCell/SCells of the cell group that this UE assistance information is associated with. The maximum number of uplink SCells can only range up to the current active configuration when indicated to address power savings.

| + +| UEAssistanceInformation field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| activeDuration
Indicates the UE's preferred active duration due to the IDC problem. Value in multiples of 1/32 ms (subMilliSeconds) or in ms (milliSecond). For the latter, value ms1 corresponds to 1 ms, value ms2 corresponds to 2 ms, and so on. | +| affectedBandwidth
Indicates the bandwidth around the center frequency of the carrier frequency range which is affected by the IDC problem. Value mhz5 corresponds to 5 MHz, value mhz10 corresponds to 10 MHz and so on. If candidateBandwidth is not configured, the UE is allowed to report the frequency range for any bandwidth as indicated by affectedBandwidth , within the frequency band limitation as defined in TS 38.101-1 [15], TS 38.101-2 [39], TS 38.101-3 [34] and TS 38.101-5 [75]. | +| reducedMIMO-LayersFR1-DL
Indicates the UE's preference on reduced configuration corresponding to the maximum number of downlink MIMO layers of each serving cell operating on FR1 indicated by the field, to address overheating or power saving. This field is allowed to be reported only when UE is configured with serving cells operating on FR1. The maximum number of downlink MIMO layers can only range up to the maximum number of MIMO layers configured across all activated downlink carrier(s) of FR1 in the cell group when indicated to address power savings. | +| reducedMIMO-LayersFR1-UL
Indicates the UE's preference on reduced configuration corresponding to the maximum number of uplink MIMO layers of each serving cell operating on FR1 indicated by the field, to address overheating or power saving (see NOTE 1). This field is allowed to be reported only when UE is configured with serving cells operating on FR1. The maximum number of uplink MIMO layers can only range up to the maximum number of MIMO layers configured across all activated uplink carrier(s) of FR1 in the cell group when indicated to address power savings. | +| reducedMIMO-LayersFR2-DL
Indicates the UE's preference on reduced configuration corresponding to the maximum number of downlink MIMO layers of each serving cell operating on FR2-1 indicated by the field, to address overheating or power saving. This field is allowed to be reported only when UE is configured with serving cells operating on FR2-1. The maximum number of downlink MIMO layers can only range up to the maximum number of MIMO layers configured across all activated downlink carrier(s) of FR2-1 in the cell group when indicated to address power savings. | +| reducedMIMO-LayersFR2-UL
Indicates the UE's preference on reduced configuration corresponding to the maximum number of uplink MIMO layers of each serving cell operating on FR2-1 indicated by the field, to address overheating or power saving (see NOTE 1). This field is allowed to be reported only when UE is configured with serving cells operating on FR2-1. The maximum number of uplink MIMO layers can only range up to the maximum number of MIMO layers configured across all activated uplink carrier(s) of FR2-1 in the cell group when indicated to address power savings. | +| reducedMIMO-LayersFR2-2-DL
Indicates the UE's preference on reduced configuration corresponding to the maximum number of downlink MIMO layers of each serving cell operating on FR2-2 indicated by the field, to address overheating or power saving. This field is allowed to be reported only when UE is configured with serving cells operating on FR2-2. The maximum number of downlink MIMO layers can only range up to the maximum number of MIMO layers configured across all activated downlink carrier(s) of FR2-2 in the cell group when indicated to address power savings. | +| reducedMIMO-LayersFR2-2-UL
Indicates the UE's preference on reduced configuration corresponding to the maximum number of uplink MIMO layers of each serving cell operating on FR2-2 indicated by the field, to address overheating or power saving (see NOTE 1). This field is allowed to be reported only when UE is configured with serving cells operating on FR2-2. The maximum number of uplink MIMO layers can only range up to the maximum number of MIMO layers configured across all activated uplink carrier(s) of FR2-2 in the cell group when indicated to address power savings. | +| referenceTimeInfoPreference
Indicates whether the UE prefers being provisioned with the timing information specified in the IE ReferenceTimeInfo . | +| resumeCause
Provides the resume cause based on the information received from the upper layers. | + +| UEAssistanceInformation field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| activeDuration
Indicates the UE's preferred active duration due to the IDC problem. Value in multiples of 1/32 ms (subMilliSeconds) or in ms (milliSecond). For the latter, value ms1 corresponds to 1 ms, value ms2 corresponds to 2 ms, and so on. | +| affectedBandwidth
Indicates the bandwidth around the center frequency of the carrier frequency range which is affected by the IDC problem. Value mhz5 corresponds to 5 MHz, value mhz10 corresponds to 10 MHz and so on. If candidateBandwidth is not configured, the UE is allowed to report the frequency range for any bandwidth as indicated by affectedBandwidth , within the frequency band limitation as defined in TS 38.101-1 [15], TS 38.101-2 [39], TS 38.101-3 [34] and TS 38.101-5 [75]. | +| rlm-MeasRelaxationState
Indicates the relaxation state of RLM measurements. Value true indicates that the UE is performing relaxation of RLM measurements, and value false indicates that the UE is not performing relaxation of RLM measurements. | +| rrm-MeasRelaxationFulfilment
Indicates whether the UE fulfils the relaxed measurement criterion for stationary UE in 5.7.4.4. Value true indicates that the UE fulfils the criterion, and value false indicates that the UE does not fulfil the criterion. | +| sl-QoS-FlowIdentity
This identity uniquely identifies one sidelink QoS flow between the UE and the network in the scope of UE, which is unique for different destination and cast type. | +| sl-PRS-DelayBudget
Indicates the SL-PRS delay budget. Upper bound value for the associated response time provided by upper layers (see TS 38.355 [77]). | +| sl-PRS-Periodicity
Indicates the periodicity of SL-PRS transmission. | +| sl-PRS-Priority
Indicates the priority of SL-PRS. Value 1 is the highest priority whereas value 8 is the lowest priority. | +| sl-UE-AssistanceInformationNR
Indicates the traffic characteristic of sidelink logical channel(s), specified in the IE SL-TrafficPatternInfo , that are setup for NR sidelink communication. | +| slotOffset
Indicates the UE's preferred slot offset due to the IDC problem, in multiples of 1/32 ms. | +| startOffset
Indicates the UE's preferred start offset due to the IDC problem, in multiples of 1 ms. | +| type1
Indicates the preferred amount of increment/decrement to the long DRX cycle length with respect to the current configuration. Value in number of milliseconds. Value ms40 corresponds to 40 milliseconds, msMinus40 corresponds to -40 milliseconds and so on. | +| ul-GapFR2-PatternPreference
Indicates the UE's preference on FR2 UL gap pattern as defined in TS 38.133 [14]. | +| victimSystemType
Indicate the list of victim system types to which IDC interference is caused from NR. Value gps , glonass , bds , galileo and navIC indicates the type of GNSS. Value wlan indicates WLAN and value bluetooth indicates Bluetooth. Value uwb indicates Ultra Wide Band. | + +NOTE 1: The field may also indicate the UE's preference on reduced configuration corresponding to the maximum number of SRS ports (i.e. *nrofSRS-Ports*) of each serving cell operating on the associated frequency range. + +| SL-TrafficPatternInfo field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| messageSize
Indicates the maximum TB size based on the observed traffic pattern. The value refers to the index of TS 38.321 [3], table 6.1.3.1-2. | +| timingOffset
This field indicates the estimated timing for a packet arrival in a sidelink logical channel. Specifically, the value indicates the timing offset with respect to subframe#0 of SFN#0 in milliseconds. | +| trafficPeriodicity
This field indicates the estimated data arrival periodicity in a sidelink logical channel. Value ms20 corresponds to 20 ms, ms50 corresponds to 50 ms and so on. | + +| UL-TrafficInfo field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| burstArrivalTime
Indicates the average value of the arrival time of the first packet of the Data Burst for the concerned QoS flow. When indicated together with jitterRange , burstArrivalTime is used as a reference time for the indicated jitter range.
If burstArrivalTime is indicated as referenceTime , the indicated time in 10ns unit from the origin is $refDays * 86400 * 1000 * 100000 + refSeconds * 1000 * 100000 + refMilliSeconds * 100000 + refTenNanoSeconds$ . The refDays field specifies the sequential number of days (with day count starting at 0) from 00:00:00 on Gregorian calendar date 6 January, 1980 (start of GPS time).
If burstArrivalTime is indicated as referenceSFN-AndSlot , it refers to the UL timing of the closest SFN and slot of the PCell with the indicated number. | +| jitterRange
Indicates the maximum deviation of the arrival time of the first packet of a Data Burst compared to the time indicated with burstArrivalTime and the periodicity of the Data Bursts. lowerBound indicates the negative deviation while upperBound indicates the positive deviation. This field shall only be reported together with the burstArrivalTime or after the burstArrivalTime has been already reported. Value ms0 corresponds to 0 ms, value 0dot5 to 0.5 ms, value ms1 to 1 ms and so on. Value beyondMs7 indicates the jitter bound is higher than 7 ms. Value 0 ms means there is no Data Burst arrival time deviation from the indicated burstArrivalTime . | +| pduSetIdentification
Indicates whether the UE is able to identify PDU Set related information for the QoS flow. If set to true , the UE is able to identify PDU set related information, otherwise, the UE is not able to do so. | +| qfi
Identity of the QoS flow to which this UL traffic information refers. | +| trafficPeriodicity
Indicates the average time period between the start times of two data bursts, expressed in the number of microseconds. | + +#### – *UECapabilityEnquiry* + +The *UECapabilityEnquiry* message is used to request UE radio access capabilities for NR as well as for other RATs. + +Signalling radio bearer: SRB1 + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: Network to UE + +#### **UECapabilityEnquiry message** + +``` + +-- ASN1START +-- TAG-UECAPABILITYENQUIRY-START + +UECapabilityEnquiry ::= SEQUENCE { + rrc-TransactionIdentifier RRC-TransactionIdentifier, + criticalExtensions CHOICE { + ueCapabilityEnquiry UECapabilityEnquiry-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +UECapabilityEnquiry-IEs ::= SEQUENCE { + ue-CapabilityRAT-RequestList UE-CapabilityRAT-RequestList, + lateNonCriticalExtension OCTET STRING OPTIONAL, + ue-CapabilityEnquiryExt OCTET STRING (CONTAINING UECapabilityEnquiry-v1560-IEs) OPTIONAL -- Need N +} + +UECapabilityEnquiry-v1560-IEs ::= SEQUENCE { + capabilityRequestFilterCommon UE-CapabilityRequestFilterCommon OPTIONAL, -- Need N + nonCriticalExtension UECapabilityEnquiry-v1610-IEs OPTIONAL +} + +UECapabilityEnquiry-v1610-IEs ::= SEQUENCE { + rrc-SegAllowed-r16 ENUMERATED {enabled} OPTIONAL, -- Need N + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +-- TAG-UECAPABILITYENQUIRY-STOP +-- ASN1STOP + +``` + +#### — **UECapabilityInformation** + +The IE *UECapabilityInformation* message is used to transfer UE radio access capabilities requested by the network. + +Signalling radio bearer: SRB1 + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: UE to Network + +#### **UECapabilityInformation message** + +``` + +-- ASN1START + +``` + +``` + +-- TAG-UECAPABILITYINFORMATION-START + +UECapabilityInformation ::= SEQUENCE { + rrc-TransactionIdentifier RRC-TransactionIdentifier, + criticalExtensions CHOICE { + ueCapabilityInformation UECapabilityInformation-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +UECapabilityInformation-IEs ::= SEQUENCE { + ue-CapabilityRAT-ContainerList UE-CapabilityRAT-ContainerList OPTIONAL, + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension SEQUENCE{} OPTIONAL +} + +-- TAG-UECAPABILITYINFORMATION-STOP +-- ASN1STOP + +``` + +#### — *UEInformationRequest* + +The *UEInformationRequest* message is used by the network to retrieve information from the UE. + +Signalling radio bearer: SRB1 + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: Network to UE + +#### *UEInformationRequest message* + +``` + +-- ASN1START +-- TAG-UEINFORMATIONREQUEST-START + +UEInformationRequest-r16 ::= SEQUENCE { + rrc-TransactionIdentifier RRC-TransactionIdentifier, + criticalExtensions CHOICE { + ueInformationRequest-r16 UEInformationRequest-r16-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +UEInformationRequest-r16-IEs ::= SEQUENCE { + idleModeMeasurementReq-r16 ENUMERATED{true} OPTIONAL, -- Need N + logMeasReportReq-r16 ENUMERATED {true} OPTIONAL, -- Need N +} + +``` + +``` + connEstFailReportReq-r16 ENUMERATED {true} OPTIONAL, -- Need N + ra-ReportReq-r16 ENUMERATED {true} OPTIONAL, -- Need N + rlf-ReportReq-r16 ENUMERATED {true} OPTIONAL, -- Need N + mobilityHistoryReportReq-r16 ENUMERATED {true} OPTIONAL, -- Need N + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension UEInformationRequest-v1700-IEs OPTIONAL +} + +UEInformationRequest-v1700-IEs ::= SEQUENCE { + successHO-ReportReq-r17 ENUMERATED {true} OPTIONAL, -- Need N + coarseLocationRequest-r17 ENUMERATED {true} OPTIONAL, -- Need N + nonCriticalExtension UEInformationRequest-v1800-IEs OPTIONAL +} + +UEInformationRequest-v1800-IEs ::= SEQUENCE { + flightPathInfoReq-r18 FlightPathInfoReportConfig-r18 OPTIONAL, -- Need N + successPSCell-ReportReq-r18 ENUMERATED {true} OPTIONAL, -- Need N + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +FlightPathInfoReportConfig-r18 ::= SEQUENCE { + maxWayPointNumber-r18 INTEGER (1..maxWayPoint-r18), + includeTimeStamp-r18 ENUMERATED {true} OPTIONAL +} + +-- TAG-UEINFORMATIONREQUEST-STOP +-- ASN1STOP +``` + +| UEInformationRequest-IEs field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| coarseLocationRequest
This field is used to request UE to report coarse location information. | +| connEstFailReportReq
This field is used to indicate whether the UE shall report information about the connection failure. | +| flightPathInfoReq
This field is used to indicate whether the UE can report information about the flight path information, if available, and to specify the flight path information report configuration. | +| idleModeMeasurementReq
This field indicates that the UE shall report the idle/inactive measurement information, if available, to the network in the UEInformationResponse message. | +| logMeasReportReq
This field is used to indicate whether the UE shall report information about logged measurements. | +| mobilityHistoryReportReq
This field is used to indicate whether the UE shall report information about mobility history information. | +| ra-ReportReq
This field is used to indicate whether the UE shall report information about the random access procedure. | +| rlf-ReportReq
This field is used to indicate whether the UE shall report information about the radio link failure. | +| successHO-ReportReq
This field is used to indicate whether the UE shall report information about the successful handover report. | +| successPSCell-ReportReq
This field is used to indicate whether the UE shall report information about the successful PSCell change or addition report. | + +| FlightPathInfoReportConfig field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| includeTimeStamp
Indicates whether time stamp of each way point can be reported in the flight path information report if time stamp information is available at the UE. | +| maxWayPointNumber
Indicates the maximum number of way points UE can include in the flight path information report if this information is available at the UE. | + +#### — *UEInformationResponse* + +The *UEInformationResponse* message is used by the UE to transfer information requested by the network. + +Signalling radio bearer: SRB1 or SRB2 (when logged measurement information is included) + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: UE to network + +#### **UEInformationResponse message** + +``` + +-- ASN1START +-- TAG-UEINFORMATIONRESPONSE-START + +UEInformationResponse-r16 ::= + SEQUENCE { + rrc-TransactionIdentifier RRC-TransactionIdentifier, + criticalExtensions CHOICE { + ueInformationResponse-r16 UEInformationResponse-r16-IEs, + criticalExtensionsFuture SEQUENCE {} + } + } + +UEInformationResponse-r16-IEs ::= + SEQUENCE { + measResultIdleEUTRA-r16 MeasResultIdleEUTRA-r16 OPTIONAL, + measResultIdleNR-r16 MeasResultIdleNR-r16 OPTIONAL, + logMeasReport-r16 LogMeasReport-r16 OPTIONAL, + connEstFailReport-r16 ConnEstFailReport-r16 OPTIONAL, + ra-ReportList-r16 RA-ReportList-r16 OPTIONAL, + rlf-Report-r16 RLF-Report-r16 OPTIONAL, + mobilityHistoryReport-r16 MobilityHistoryReport-r16 OPTIONAL, + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension UEInformationResponse-v1700-IEs OPTIONAL + } + +UEInformationResponse-v1700-IEs ::= + SEQUENCE { + successHO-Report-r17 SuccessHO-Report-r17 OPTIONAL, + connEstFailReportList-r17 ConnEstFailReportList-r17 OPTIONAL, + coarseLocationInfo-r17 OCTET STRING OPTIONAL, + nonCriticalExtension UEInformationResponse-v1800-IEs OPTIONAL + } + +UEInformationResponse-v1800-IEs ::= + SEQUENCE { + flightPathInfoReport-r18 FlightPathInfoReport-r18 OPTIONAL, + successPSCell-Report-r18 SuccessPSCell-Report-r18 OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL + } + +FlightPathInfoReport-r18 ::= + SEQUENCE (SIZE (0..maxWayPoint-r18)) OF WayPoint-r18 + +WayPoint-r18 ::= + SEQUENCE { + wayPointLocation-r18 OCTET STRING, + timeStamp-r18 AbsoluteTimeInfo-r16 OPTIONAL + } + +LogMeasReport-r16 ::= + SEQUENCE { + absoluteTimeStamp-r16 AbsoluteTimeInfo-r16, + traceReference-r16 TraceReference-r16, + traceRecordingSessionRef-r16 OCTET STRING (SIZE (2)), + tce-Id-r16 OCTET STRING (SIZE (1)), + logMeasInfoList-r16 LogMeasInfoList-r16, + } + +``` + +``` + +logMeasAvailable-r16 ENUMERATED {true} OPTIONAL, +logMeasAvailableBT-r16 ENUMERATED {true} OPTIONAL, +logMeasAvailableWLAN-r16 ENUMERATED {true} OPTIONAL, +... +} + +LogMeasInfoList-r16 := SEQUENCE (SIZE (1..maxLogMeasReport-r16)) OF LogMeasInfo-r16 + +LogMeasInfo-r16 := SEQUENCE { + locationInfo-r16 LocationInfo-r16 OPTIONAL, + relativeTimeStamp-r16 INTEGER (0..7200), + servCellIdentity-r16 CGI-Info-Logging-r16 OPTIONAL, + measResultServingCell-r16 MeasResultServingCell-r16 OPTIONAL, + measResultNeighCells-r16 SEQUENCE { + measResultNeighCellListNR MeasResultListLogging2NR-r16 OPTIONAL, + measResultNeighCellListEUTRA MeasResultList2EUTRA-r16 OPTIONAL + }, + anyCellSelectionDetected-r16 ENUMERATED {true} OPTIONAL, + ... + [[ + inDeviceCoexDetected-r17 ENUMERATED {true} OPTIONAL + ]] +} + +ConnEstFailReport-r16 := SEQUENCE { + measResultFailedCell-r16 MeasResultFailedCell-r16, + locationInfo-r16 LocationInfo-r16 OPTIONAL, + measResultNeighCells-r16 SEQUENCE { + measResultNeighCellListNR MeasResultList2NR-r16 OPTIONAL, + measResultNeighCellListEUTRA MeasResultList2EUTRA-r16 OPTIONAL + }, + numberOfConnFail-r16 INTEGER (1..8), + perRAInfoList-r16 PerRAInfoList-r16, + timeSinceFailure-r16 TimeSinceFailure-r16, + ... +} + +ConnEstFailReportList-r17 := SEQUENCE (SIZE (1..maxCEFReport-r17)) OF ConnEstFailReport-r16 + +MeasResultServingCell-r16 := SEQUENCE { + resultsSSB-Cell MeasQuantityResults, + resultsSSB SEQUENCE{ + best-ssb-Index SSB-Index, + best-ssb-Results MeasQuantityResults, + numberOfGoodSSB INTEGER (1..maxNrofSSBs-r16) + } +} + +MeasResultFailedCell-r16 := SEQUENCE { + cgi-Info CGI-Info-Logging-r16, + measResult-r16 SEQUENCE { + +``` + +``` + + cellResults-r16 SEQUENCE{ + resultsSSB-Cell-r16 MeasQuantityResults + }, + rsIndexResults-r16 SEQUENCE{ + resultsSSB-Indexes-r16 ResultsPerSSB-IndexList + } + } +} + +RA-ReportList-r16 ::= SEQUENCE (SIZE (1..maxRAReport-r16)) OF RA-Report-r16 + +RA-Report-r16 ::= SEQUENCE { + cellId-r16 CHOICE { + cellGlobalId-r16 CGI-Info-Logging-r16, + pci-arfcn-r16 PCI-ARFCN-NR-r16 + }, + ra-InformationCommon-r16 RA-InformationCommon-r16 OPTIONAL, + raPurpose-r16 ENUMERATED {accessRelated, beamFailureRecovery, reconfigurationWithSync, ulUnSynchronized, + schedulingRequestFailure, noPUCCHResourceAvailable, requestForOtherSI, + msg3RequestForOtherSI-r17, lbtFailure-r18, spare7, spare6, spare5, spare4, spare3, + spare2, spare1}, + ... + [[ + spCellID-r17 CGI-Info-Logging-r16 OPTIONAL + ]] +} + +RA-InformationCommon-r16 ::= SEQUENCE { + absoluteFrequencyPointA-r16 ARFCN-ValueNR, + locationAndBandwidth-r16 INTEGER (0..37949), + subcarrierSpacing-r16 SubcarrierSpacing, + msg1-FrequencyStart-r16 INTEGER (0..maxNrofPhysicalResourceBlocks-1) OPTIONAL, + msg1-FrequencyStartCFRA-r16 INTEGER (0..maxNrofPhysicalResourceBlocks-1) OPTIONAL, + msg1-SubcarrierSpacing-r16 SubcarrierSpacing OPTIONAL, + msg1-SubcarrierSpacingCFRA-r16 SubcarrierSpacing OPTIONAL, + msg1-FDM-r16 ENUMERATED {one, two, four, eight} OPTIONAL, + msg1-FDMCFRA-r16 ENUMERATED {one, two, four, eight} OPTIONAL, + perRAInfoList-r16 PerRAInfoList-r16, + ... + [[ + perRAInfoList-v1660 PerRAInfoList-v1660 OPTIONAL + ]], + [[ + msg1-SCS-From-prach-ConfigurationIndex-r16 ENUMERATED {kHz1dot25, kHz5, spare2, spare1} OPTIONAL + ]], + [[ + msg1-SCS-From-prach-ConfigurationIndexCFRA-r16 ENUMERATED {kHz1dot25, kHz5, spare2, spare1} OPTIONAL + ]], + [[ + msgA-RO-FrequencyStart-r17 INTEGER (0..maxNrofPhysicalResourceBlocks-1) OPTIONAL, + msgA-RO-FrequencyStartCFRA-r17 INTEGER (0..maxNrofPhysicalResourceBlocks-1) OPTIONAL, + ]], +} + +``` + +``` + +msgA-SubcarrierSpacing-r17 SubcarrierSpacing OPTIONAL, +msgA-RO-FDM-r17 ENUMERATED {one, two, four, eight} OPTIONAL, +msgA-RO-FDMCFRA-r17 ENUMERATED {one, two, four, eight} OPTIONAL, +msgA-SCS-From-prach-ConfigurationIndex-r17 ENUMERATED {kHz1dot25, kHz5, spare2, spare1} OPTIONAL, +msgA-TransMax-r17 ENUMERATED {n1, n2, n4, n6, n8, n10, n20, n50, n100, n200} OPTIONAL, +msgA-MCS-r17 INTEGER (0..15) OPTIONAL, +nrofPRBs-PerMsgA-PO-r17 INTEGER (1..32) OPTIONAL, +msgA-PUSCH-TimeDomainAllocation-r17 INTEGER (1..maxNrofUL-Allocations) OPTIONAL, +frequencyStartMsgA-PUSCH-r17 INTEGER (0..maxNrofPhysicalResourceBlocks-1) OPTIONAL, +nrofMsgA-PO-FDM-r17 ENUMERATED {one, two, four, eight} OPTIONAL, +dlPathlossRSRP-r17 RSRP-Range OPTIONAL, +intendedSIBs-r17 SEQUENCE (SIZE (1..maxSIB)) OF SIB-Type-r17 OPTIONAL, +ssbsForSI-Acquisition-r17 SEQUENCE (SIZE (1..maxNrofSSBs-r16)) OF SSB-Index OPTIONAL, +msgA-PUSCH-PayloadSize-r17 BIT STRING (SIZE (5)) OPTIONAL, +onDemandSISuccess-r17 ENUMERATED {true} OPTIONAL +]], +[[ +usedFeatureCombination-r18 ReportedFeatureCombination-r18 OPTIONAL, +triggeredFeatureCombination-r18 ReportedFeatureCombination-r18 OPTIONAL, +attemptedBWP-InfoList-r18 SEQUENCE (SIZE (1..maxNrofBWPs)) OF AttemptedBWP-Info-r18 OPTIONAL, +numberOfLBTFailures-r18 INTEGER (1..128) OPTIONAL, +perRAInfoList-v1800 PerRAInfoList-v1800 OPTIONAL, +sdt-Failed-r18 ENUMERATED {true} OPTIONAL +]] +} + +AttemptedBWP-Info-r18 ::= SEQUENCE { + locationAndBandwidth-r18 INTEGER (0..37949), + subcarrierSpacing-r18 SubcarrierSpacing +} + +ReportedFeatureCombination-r18 ::= SEQUENCE { + redCap-r18 ENUMERATED {true} OPTIONAL, + smallData-r18 ENUMERATED {true} OPTIONAL, + nsag-r18 NSAG-List-r17 OPTIONAL, + msg3-Repetitions-r18 ENUMERATED {true} OPTIONAL, + triggered-S-NSSAI-List-r18 SEQUENCE (SIZE (1..maxNrofS-NSSAI)) OF S-NSSAI OPTIONAL +} + +PerRAInfoList-r16 ::= SEQUENCE (SIZE (1..200)) OF PerRAInfo-r16 + +PerRAInfoList-v1660 ::= SEQUENCE (SIZE (1..200)) OF PerRACSI-RSInfo-v1660 + +PerRAInfo-r16 ::= CHOICE { + perRASSBInfoList-r16 PerRASSBInfo-r16, + perRACSI-RSInfoList-r16 PerRACSI-RSInfo-r16 +} + +PerRAInfoList-v1800 ::= SEQUENCE (SIZE (1..200)) OF PerRAInfo-v1800 + +PerRAInfo-v1800 ::= CHOICE { + +``` + +``` + + perRASSBInfoList-v1800 PerRASSBInfo-v1800, + perRACSI-RSInfoList-v1800 PerRACSI-RSInfo-v1800 +} + +PerRASSBInfo-r16 ::= SEQUENCE { + ssb-Index-r16 SSB-Index, + numberOfPreamblesSentOnSSB-r16 INTEGER (1..200), + perRAAttemptInfoList-r16 PerRAAttemptInfoList-r16 +} + +PerRASSBInfo-v1800 ::= SEQUENCE { + allPreamblesBlocked ENUMERATED {true} OPTIONAL, + lbt-Detected-r18 ENUMERATED {true} OPTIONAL, + ... +} + +PerRACSI-RSInfo-r16 ::= SEQUENCE { + csi-RS-Index-r16 CSI-RS-Index, + numberOfPreamblesSentOnCSI-RS-r16 INTEGER (1..200) +} + +PerRACSI-RSInfo-v1660 ::= SEQUENCE { + csi-RS-Index-v1660 INTEGER (1..96) OPTIONAL +} + +PerRACSI-RSInfo-v1800 ::= SEQUENCE { + allPreamblesBlocked ENUMERATED {true} OPTIONAL, + lbt-Detected-r18 ENUMERATED {true} OPTIONAL, + ... +} + +PerRAAttemptInfoList-r16 ::= SEQUENCE (SIZE (1..200)) OF PerRAAttemptInfo-r16 + +PerRAAttemptInfo-r16 ::= SEQUENCE { + contentionDetected-r16 BOOLEAN OPTIONAL, + dlRSRPAboveThreshold-r16 BOOLEAN OPTIONAL, + ... + [[ + fallbackToFourStepRA-r17 ENUMERATED {true} OPTIONAL + ]] +} + +SIB-Type-r17 ::= ENUMERATED {sibType2, sibType3, sibType4, sibType5, sibType9, sibType10-v1610, sibType11-v1610, sibType12-v1610, + sibType13-v1610, sibType14-v1610, spare6, spare5, spare4, spare3, spare2, spare1} + +RLF-Report-r16 ::= CHOICE { + nr-RLF-Report-r16 SEQUENCE { + measResultLastServCell-r16 MeasResultRLFNR-r16, + measResultNeighCells-r16 SEQUENCE { + measResultListNR-r16 MeasResultList2NR-r16 OPTIONAL, + measResultListEUTRA-r16 MeasResultList2EUTRA-r16 OPTIONAL + } + } +} + +``` + +``` + + } OPTIONAL, + c-RNTI-r16 RNTI-Value, + previousPCellId-r16 CHOICE { + nrPreviousCell-r16 CGI-Info-Logging-r16, + eutraPreviousCell-r16 CGI-InfoEUTRALogging + } OPTIONAL, + failedPCellId-r16 CHOICE { + nrFailedPCellId-r16 CHOICE { + cellGlobalId-r16 CGI-Info-Logging-r16, + pci-arfcn-r16 PCI-ARFCN-NR-r16 + }, + eutraFailedPCellId-r16 CHOICE { + cellGlobalId-r16 CGI-InfoEUTRALogging, + pci-arfcn-r16 PCI-ARFCN-EUTRA-r16 + } + }, + reconnectCellId-r16 CHOICE { + nrReconnectCellId-r16 CGI-Info-Logging-r16, + eutraReconnectCellId-r16 CGI-InfoEUTRALogging + } OPTIONAL, + timeUntilReconnection-r16 TimeUntilReconnection-r16 OPTIONAL, + reestablishmentCellId-r16 CGI-Info-Logging-r16 OPTIONAL, + timeConnFailure-r16 INTEGER (0..1023) OPTIONAL, + timeSinceFailure-r16 TimeSinceFailure-r16, + connectionFailureType-r16 ENUMERATED {rlf, hof}, + rlf-Cause-r16 ENUMERATED {t310-Expiry, randomAccessProblem, rlc-MaxNumRetx, + beamFailureRecoveryFailure, lbtFailure-r16, + bh-rlfRecoveryFailure, t312-expiry-r17, spare1}, + locationInfo-r16 LocationInfo-r16 OPTIONAL, + noSuitableCellFound-r16 ENUMERATED {true} OPTIONAL, + ra-InformationCommon-r16 RA-InformationCommon-r16 OPTIONAL, + ... + [[ + csi-rsRLMConfigBitmap-v1650 BIT STRING (SIZE (96)) OPTIONAL + ]], + [[ + lastHO-Type-r17 ENUMERATED {cho, daps, spare2, spare1} OPTIONAL, + timeConnSourceDAPS-Failure-r17 TimeConnSourceDAPS-Failure-r17 OPTIONAL, + timeSinceCHO-Reconfig-r17 TimeSinceCHO-Reconfig-r17 OPTIONAL, + choCellId-r17 CHOICE { + cellGlobalId-r17 CGI-Info-Logging-r16, + pci-arfcn-r17 PCI-ARFCN-NR-r16 + } OPTIONAL, + choCandidateCellList-r17 ChoCandidateCellList-r17 OPTIONAL + ]], + [[ + pSCellId-r18 CHOICE { + cellGlobalId-r18 CGI-Info-Logging-r16, + pci-arfcn-r18 PCI-ARFCN-NR-r16 + } OPTIONAL, + mcgRecoveryFailureCause-r18 ENUMERATED {t316-Expiry, scgDeactivated, spare2, spare1} OPTIONAL, + +``` + +``` + + scgFailureCause-r18 ENUMERATED {t310-Expiry, randomAccessProblem, rlc-MaxNumRetx, + synchReconfigFailureSCG, scg-ReconfigFailure, + srb3-IntegrityFailure, scg-lbtFailure-r16, beamFailureRecoveryFailure-r16, + t312-Expiry-r16, bh-RLF-r16, beamFailure-r17, spare3, spare2, spare1 } + OPTIONAL, + elapsedTimeSCGFailure-r18 ElapsedTimeSCGFailure-r18 OPTIONAL, + voiceFallbackHO-r18 ENUMERATED {true} OPTIONAL, + measResultLastServCell-RSSI-r18 RSSI-Range-r16 OPTIONAL, + measResultNeighFreqList-RSSI-r18 MeasResultNeighFreqList-RSSI-r18 OPTIONAL, + bwp-Info-r18 AttemptedBWP-Info-r18 OPTIONAL, + elapsedTimeT316-r18 ElapsedTimeT316-r18 OPTIONAL + ]] + }, + eutra-RLF-Report-r16 SEQUENCE { + failedPCellId-EUTRA CGI-InfoEUTRALogging, + measResult-RLF-Report-EUTRA-r16 OCTET STRING, + ... + [[ + measResult-RLF-Report-EUTRA-v1690 OCTET STRING OPTIONAL + ]] + } +} + +SuccessHO-Report-r17 ::= SEQUENCE { + sourceCellInfo-r17 SEQUENCE { + sourcePCellId-r17 CGI-Info-Logging-r16, + sourceCellMeas-r17 MeasResultSuccessHONR-r17 OPTIONAL, + rlf-InSourceDAPS-r17 ENUMERATED {true} OPTIONAL + }, + targetCellInfo-r17 SEQUENCE { + targetPCellId-r17 CGI-Info-Logging-r16, + targetCellMeas-r17 MeasResultSuccessHONR-r17 OPTIONAL + }, + measResultNeighCells-r17 SEQUENCE { + measResultListNR-r17 MeasResultList2NR-r16 OPTIONAL, + measResultListEUTRA-r17 MeasResultList2EUTRA-r16 OPTIONAL + } + locationInfo-r17 LocationInfo-r16 OPTIONAL, + timeSinceCHO-Reconfig-r17 TimeSinceCHO-Reconfig-r17 OPTIONAL, + shr-Cause-r17 SHR-Cause-r17 OPTIONAL, + ra-InformationCommon-r17 RA-InformationCommon-r16 OPTIONAL, + upInterruptionTimeAtHO-r17 UPInterruptionTimeAtHO-r17 OPTIONAL, + c-RNTI-r17 RNTI-Value OPTIONAL, + ... + [[ + eutraTargetCellInfo-r18 SEQUENCE { + targetPCellId-r18 CGI-InfoEUTRALogging, + targetCellMeas-r18 MeasQuantityResultsEUTRA OPTIONAL + } + measResultServCell-RSSI-r18 RSSI-Range-r16 OPTIONAL, + measResultNeighFreqList-RSSI-r18 MeasResultNeighFreqList-RSSI-r18 OPTIONAL, + +``` + +``` + + eutra-C-RNTI-r18 EUTRA-C-RNTI OPTIONAL, + timeSinceSHR-r18 TimeSinceSHR-r18 OPTIONAL + ]] +} + +SuccessPSCell-Report-r18 := + pCellId-r18 SEQUENCE { + sourcePSCellInfo-r18 CGI-Info-Logging-r16, + sourcePSCellId-r18 SEQUENCE { + sourcePSCellMeas-r18 CGI-Info-Logging-r16, + } MeasResultSuccessHONR-r17 OPTIONAL + targetPSCellInfo-r18 OPTIONAL, + targetPSCellId-r18 SEQUENCE { + cellGlobalId-r18 CHOICE { + pci-arfcn-r18 CGI-Info-Logging-r16, + }, PCI-ARFCN-NR-r16 + targetPSCellMeas-r18 MeasResultSuccessHONR-r17 OPTIONAL +}, +measResultNeighCells-r18 SEQUENCE { + measResultListNR-r18 MeasResultList2NR-r16 OPTIONAL, + measResultListEUTRA-r18 MeasResultList2EUTRA-r16 OPTIONAL +} OPTIONAL, +spr-Cause-r18 SPR-Cause-r18 OPTIONAL, +timeSinceCPAC-Reconfig-r18 TimeSinceCPAC-Reconfig-r18 OPTIONAL, +locationInfo-r18 LocationInfo-r16 OPTIONAL, +ra-InformationCommon-r18 RA-InformationCommon-r16 OPTIONAL, +sn-InitiatedPSCellChange-r18 ENUMERATED {true} OPTIONAL +... +} + +MeasResultNeighFreqList-RSSI-r18 := + SEQUENCE (SIZE (1..maxFreq)) OF MeasResultNeighFreq-RSSI-r18 + +MeasResultNeighFreq-RSSI-r18 := + SEQUENCE { + ssbFrequency-r18 ARFCN-ValueNR OPTIONAL, + refFreqCSI-RS-r18 ARFCN-ValueNR OPTIONAL, + measResult-RSSI-r18 RSSI-Range-r16 OPTIONAL +} + +MeasResultList2NR-r16 := + SEQUENCE (SIZE (1..maxFreq)) OF MeasResult2NR-r16 +MeasResultList2EUTRA-r16 := + SEQUENCE (SIZE (1..maxFreq)) OF MeasResult2EUTRA-r16 + +MeasResult2NR-r16 := + SEQUENCE { + ssbFrequency-r16 ARFCN-ValueNR OPTIONAL, + refFreqCSI-RS-r16 ARFCN-ValueNR OPTIONAL, + measResultList-r16 MeasResultListNR +} + +MeasResultListLogging2NR-r16 := + SEQUENCE (SIZE (1..maxFreq)) OF MeasResultLogging2NR-r16 + +MeasResultLogging2NR-r16 := + SEQUENCE { + carrierFreq-r16 ARFCN-ValueNR, + +``` + +``` + + measResultListLoggingNR-r16 MeasResultListLoggingNR-r16 +} + +MeasResultListLoggingNR-r16 ::= SEQUENCE (SIZE (1..maxCellReport)) OF MeasResultLoggingNR-r16 + +MeasResultLoggingNR-r16 ::= SEQUENCE { + physCellId-r16 PhysCellId, + resultsSSB-Cell-r16 MeasQuantityResults, + numberOfGoodSSB-r16 INTEGER (1..maxNrofSSBs-r16) OPTIONAL +} + +MeasResult2EUTRA-r16 ::= SEQUENCE { + carrierFreq-r16 ARFCN-ValueEUTRA, + measResultList-r16 MeasResultListEUTRA +} + +MeasResultRLFNR-r16 ::= SEQUENCE { + measResult-r16 SEQUENCE { + cellResults-r16 SEQUENCE{ + resultsSSB-Cell-r16 MeasQuantityResults OPTIONAL, + resultsCSI-RS-Cell-r16 MeasQuantityResults OPTIONAL + }, + rsIndexResults-r16 SEQUENCE{ + resultsSSB-Indexes-r16 ResultsPerSSB-IndexList OPTIONAL, + ssbRLMConfigBitmap-r16 BIT STRING (SIZE (64)) OPTIONAL, + resultsCSI-RS-Indexes-r16 ResultsPerCSI-RS-IndexList OPTIONAL, + csi-rsRLMConfigBitmap-r16 BIT STRING (SIZE (96)) OPTIONAL + } + } +} + +MeasResultSuccessHONR-r17 ::= SEQUENCE { + measResult-r17 SEQUENCE { + cellResults-r17 SEQUENCE{ + resultsSSB-Cell-r17 MeasQuantityResults OPTIONAL, + resultsCSI-RS-Cell-r17 MeasQuantityResults OPTIONAL + }, + rsIndexResults-r17 SEQUENCE{ + resultsSSB-Indexes-r17 ResultsPerSSB-IndexList OPTIONAL, + resultsCSI-RS-Indexes-r17 ResultsPerCSI-RS-IndexList OPTIONAL + } + } +} + +ChoCandidateCellList-r17 ::= SEQUENCE (SIZE (1..maxNrofCondCells-r16)) OF ChoCandidateCell-r17 + +ChoCandidateCell-r17 ::= CHOICE { + cellGlobalId-r17 CGI-Info-Logging-r16, + pci-arfcn-r17 PCI-ARFCN-NR-r16 +} + +``` + +``` +SHR-Cause-r17 ::= SEQUENCE { + t304-cause-r17 ENUMERATED {true} OPTIONAL, + t310-cause-r17 ENUMERATED {true} OPTIONAL, + t312-cause-r17 ENUMERATED {true} OPTIONAL, + sourceDAPS-Failure-r17 ENUMERATED {true} OPTIONAL, + ... +} + +SPR-Cause-r18 ::= SEQUENCE { + t304-cause-r18 ENUMERATED {true} OPTIONAL, + t310-cause-r18 ENUMERATED {true} OPTIONAL, + t312-cause-r18 ENUMERATED {true} OPTIONAL, + ... +} + +TimeSinceFailure-r16 ::= INTEGER (0..172800) +MobilityHistoryReport-r16 ::= VisitedCellInfoList-r16 +TimeUntilReconnection-r16 ::= INTEGER (0..172800) +TimeSinceCHO-Reconfig-r17 ::= INTEGER (0..1023) +TimeSinceCPAC-Reconfig-r18 ::= INTEGER (0.. 1023) +TimeConnSourceDAPS-Failure-r17 ::= INTEGER (0..1023) +UPInterruptionTimeAtHO-r17 ::= INTEGER (0..1023) +ElapsedTimeT316-r18 ::= INTEGER (0..2000) +ElapsedTimeSCGFailure-r18 ::= INTEGER (0..1023) +TimeSinceSHR-r18 ::= INTEGER (0..172800) + +-- TAG-UEINFORMATIONRESPONSE-STOP +-- ASN1STOP +``` + +| UEInformationResponse-IEs field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| coarseLocationInfo
Parameter type Ellipsoid-Point defined in TS 37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit. The least significant bits of degreesLatitude and degreesLongitude are set to 0 to meet the accuracy requirement corresponds to a granularity of approximately 2 km.
It is up to UE implementation how many LSBs are set to 0 to meet the accuracy requirement. | +| connEstFailReport
This field is used to provide connection establishment failure or connection resume failure information. | +| connEstFailReportList
This field is used to provide the list of connEstFailReport that are stored by the UE for the past up to maxCEFReport-r17 . | +| flightPathInfoReport
This field is used to provide the flight path information as list of waypoints and, if available, corresponding timestamps. List of size zero indicates the previously provided flight path information is no longer valid. | +| logMeasReport
This field is used to provide the measurement results stored by the UE associated to logged MDT. | +| measResultIdleEUTRA
EUTRA measurement results performed during RRC_INACTIVE or RRC_IDLE. | +| measResultIdleNR
NR measurement results performed during RRC_INACTIVE or RRC_IDLE. | +| ra-ReportList
This field is used to provide the list of RA reports that is stored by the UE for the past upto maxRAReport-r16 number of successful random access procedures, or failed or successful completion of on-demand system information request procedure. | +| rlf-Report
This field is used to indicate the RLF report related contents. | +| successHO-Report
This field is used to provide the successful handover report if triggered based on the successful handover configuration. | +| successPSCell-Report
This field is used to provide the successful PSCell change or addition report if triggered based on the successful PSCell change or addition report configuration. | + +| LogMeasReport field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| absoluteTimeStamp
Indicates the absolute time when the logged measurement configuration logging is provided, as indicated by NR within absoluteTimeInfo . | +| anyCellSelectionDetected
This field is used to indicate the detection of any cell selection state, as defined in TS 38.304 [20]. The UE sets this field when performing the logging of measurement results in RRC_IDLE or RRC_INACTIVE and there is no suitable cell or no acceptable cell. | +| inDeviceCoexDetected
Indicates that measurement logging is suspended due to IDC problem detection. | +| measResultServingCell
This field refers to the log measurement results taken in the Serving cell. | +| numberOfGoodSSB
Indicates the number of good beams (beams that are above absThreshSS-BlocksConsolidation , if configured by the network) associated to the cells within the R value range (which is configured by network for cell reselection) of the highest ranked cell as part of the beam level measurements. If the UE has no SSB of a neighbour cell whose measurement quantity is above the absThreshSS-BlocksConsolidation or if the network has not configured the absThreshSS-BlocksConsolidation , then the UE does not include numberOfGoodSSB for the corresponding neighbour cell. If the UE has no SSB of the serving cell whose measurement quantity is above the absThreshSS-BlocksConsolidation or if the network has not configured the absThreshSS-BlocksConsolidation , then the UE shall set the numberOfGoodSSB for the serving cell to one. | +| relativeTimeStamp
Indicates the time of logging measurement results, measured relative to the absoluteTimeStamp . Value in seconds. | +| tce-Id
Parameter Trace Collection Entity Id: See TS 32.422 [52]. | +| traceRecordingSessionRef
Parameter Trace Recording Session Reference: See TS 32.422 [52]. | + +| ConnEstFailReport field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| measResultFailedCell
This field refers to the last measurement results taken in the cell, where connection establishment failure or connection resume failure happened. | +| measResultNeighCells
This field refers to the neighbour cell measurements when connection establishment failure or connection resume failure happened. | +| numberOfConnFail
This field is used to indicate the latest number of consecutive failed RRCSetup or RRCResume procedures in the same cell independent of RRC state transition. | +| timeSinceFailure
This field is used to indicate the time that elapsed since the connection (establishment or resume) failure. Value in seconds. The maximum value 172800 means 172800s or longer. | + +| RA-InformationCommon field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| absoluteFrequencyPointA
This field indicates the absolute frequency position of the reference resource block (Common RB 0). | +| allPreamblesBlocked
This field is included when the all the preamble transmission attempts in the corresponding beam (SSB or CSI-RS) are blocked by failed LBT. Otherwise, the field is absent. | +| attemptedBWP-InfoList
This field indicates locationAndBandwidth and subcarrierSpacing of all the BWPs in which the consistent LBT failures are triggered at the moment of successful RA completion. | +| locationAndBandwidth
Frequency domain location and bandwidth of the bandwidth part associated to the random-access resources used by the UE. | +| numberOfLBTFailures
This field is used to indicate the total number of preamble transmission attempts for which LBT failure indication is received in the RA procedure. If the number of LBT failure indications received from lower layers during the RA procedure exceeds or equals to 128, UE sets the field to 128. This field is optional present when there is at least one preamble transmission attempt for which LBT failure indication is received during the RA procedure, otherwise it is absent. | +| perRAInfoList, perRAInfoList-v1660
This field provides detailed information about each of the random access attempts in the chronological order of the random access attempts. If perRAInfoList-v1660 is present, it shall contain the same number of entries, listed in the same order as in perRAInfoList-r16 . | +| sdtd-Failed
This field is included when the RA report entry is included because of SDT and if the SDT transmission failed. Otherwise, the field is absent. | +| subcarrierSpacing
Subcarrier spacing used in the BWP associated to the random-access resources used by the UE. | +| triggeredFeatureCombination
One or more features (e.g., RedCap , Slicing , SDT and MSG3 repetition ) that triggers the random-access procedure. When triggered feature is Slicing , UE includes all the S-NSSAIs associated to the slices triggering the access attempt in the random-access procedure. | +| usedFeatureCombination
The feature or combination of features (e.g., redCap , smallData , nsag and msg3-Repetitions ) associated to the used random-access resources as specified in TS 38.321[3]. | + +| RA-Report field descriptions | | +|---------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| cellID | This field indicates the CGI of the cell in which the associated random access procedure was performed. | +| contentionDetected | This field is used to indicate that contention was detected for the transmitted preamble in the given random access attempt or not. This field is not included when the UE performs random access attempt using contention free random-access resources or when the raPurpose is set to requestForOtherSI or when the RA attempt is a 2-step RA attempt and fallback to 4-step RA did not occur (i.e. fallbackToFourStepRA is not included). | +| csi-RS-Index, csi-RS-Index-v1660 | This field is used to indicate the CSI-RS index corresponding to the random access attempt.
If the random access procedure is for beam failure recovery, the field indicates the NZP-CSI-RS-ResourceId. For CSI-RS index larger than maxNrofCSI-RS-ResourcesRRM-1, the index value is the sum of csi-RS-Index (without suffix) and csi-RS-Index-v1660. | +| dlPathlossRSRP | Measured RSRP of the DL pathloss reference obtained at the time of RA_Type selection stage of the RA procedure as captured in TS 38.321 [3]. | +| dlRSRPaboveThreshold | In 4 step random access procedure, this field is used to indicate whether the DL beam (SSB) quality associated to the random access attempt was above or below the threshold rsrp-ThresholdSSB in beamFailureRecoveryConfig in UL BWP configuration of UL BWP selected for random access procedure initiated for beam failure recovery; Otherwise, if the UE has received rsrp-ThresholdSSB in FeatureCombinationPreambles used for the feature specific random access, the field is used to indicate whether DL beam (SSB) quality associated to the random access attempt was above or below this rsrp-ThresholdSSB-r17 , else rsrp-ThresholdSSB in rach-ConfigCommon in UL BWP configuration of UL BWP selected for random access procedure.
In 2 step random access procedure, if the UE has received msgA-RSRP-ThresholdSSB in FeatureCombinationPreambles used for the feature specific random access, the field is used to indicate whether DL beam (SSB) quality associated to the random access attempt was above or below this rsrp-ThresholdSSB-r17 , else this field is used to indicate whether the DL beam (SSB) quality associated to the random access attempt was above or below the threshold msgA-RSRP-ThresholdSSB in rach-ConfigCommonTwoStepRA in UL BWP configuration of UL BWP selected for random access procedure. | +| fallbackToFourStepRA | This field indicates if a fallback indication in MsgB is received (according to TS 38.321 [3]) for the 2-step random access attempt. | +| intendedSIBs | This field indicates the SIB(s) the UE wanted to receive as a result of the on demand SI request (when the RA procedure is used as a SI request) initiated by the UE. That is, it indicates the one(s) of the SIB(s) in the SI message(s) requested to be broadcast that the UE was interested in. | +| lbt-Detected | This field is included when there is at least one LBT failure indication received prior to change of beam for preamble transmission during RA procedure, otherwise this field is absent. | +| msg1-SCS-From-prach-ConfigurationIndex | This field is set by the UE with the corresponding SCS for CBRA as derived from the prach-ConfigurationIndex in RACH-ConfigGeneric when the msg1-SubcarrierSpacing is absent; otherwise, this field is absent. | +| msg1-SCS-From-prach-ConfigurationIndexCFRA | This field is set by the UE with the corresponding SCS for CFRA as derived from the prach-ConfigurationIndex in RACH-ConfigGeneric when the msg1-SubcarrierSpacing is absent; otherwise, this field is absent. | +| msgA-PUSCH-PayloadSize | This field indicates the size of the overall payload available in the UE buffer at the time of initiating the 2 step RA procedure. The value refers to the index of TS 38.321 [3], table 6.1.3.1-1, corresponding to the UE buffer size. | +| msgA-RO-FDM | This field indicates the number of msgA PRACH transmission occasions Frequency-Division Multiplexed in one time instance for the PRACH resources configured for 2-step CBRA.. | +| msgA-RO-FDMCFRA | | + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| This field indicates the number of msgA PRACH transmission occasions Frequency-Division Multiplexed in one time instance for the PRACH resources configured for 2-step CFRA. | +| msgA-RO-FrequencyStart
This field indicates the lowest resource block of the contention based random-access resources for 2-step CBRA in the random-access procedure. The indication has the form of the offset of the lowest PRACH transmissions occasion with respect to PRB 0 in the frequency domain. | +| msgA-RO-FrequencyStartCFRA
This field indicates the lowest resource block of the contention free random-access resources for the 2-step CFRA in the random-access procedure. The indication has the form of the offset of the lowest PRACH transmissions occasion with respect to PRB 0 in the frequency domain. | +| msgA-SCS-From-prach-ConfigurationIndex
This field is set by the UE with the corresponding SCS as derived from the msgA-PRACH-ConfigurationIndex in RACH-ConfigGenericTwoStepRA (see tables Table 6.3.3.1-1, Table 6.3.3.1-2, Table 6.3.3.2-2 and Table 6.3.3.2-3, TS 38.211 [16]) when the msgA-SubcarrierSpacing is absent and when only 2-step random-access resources are available in the UL BWP used in the random-access procedure; otherwise, this field is absent. | +| numberOfPreamblesSentOnCSI-RS
This field is used to indicate the total number of successive RA preambles that were transmitted on the corresponding CSI-RS. | +| numberOfPreamblesSentOnSSB
This field is used to indicate the total number of successive RA preambles that were transmitted on the corresponding SS/PBCH block. | +| onDemandSISuccess
This field is set to true when the RA report entry is included because of either msg1 based on demand SI request or msg3 based on demand SI request and if the on-demand SI request is successful. Otherwise, the field is absent. | +| perRAAttemptInfoList
This field provides detailed information about a random access attempt. | +| perRACSI-RSInfoList
This field provides detailed information about the successive random access attempts associated to the same CSI-RS. | +| perRASSBInfoList
This field provides detailed information about the successive random access attempts associated to the same SS/PBCH block. | +| ra-InformationCommon
This field is used to provide information on random access attempts. This field is mandatory present. | +| raPurpose
This field is used to indicate the RA scenario for which the RA report entry is triggered. The RA accesses associated to Initial access from RRC_IDLE, RRC re-establishment procedure, transition from RRC_INACTIVE. The indicator beamFailureRecovery is used in case of successful beam failure recovery related RA procedure in the SpCell [3]. The indicator reconfigurationWithSync is used if the UE executes a reconfiguration with sync. The indicator ulUnSynchronized is used if the random access procedure is initiated in a SpCell by DL or UL data arrival during RRC_CONNECTED when the timeAlignmentTimer is not running in the PTAG or if the RA procedure is initiated in a serving cell by a PDCCH order [3]. The indicator schedulingRequestFailure is used in case of SR failures [3]. The indicator noPUCCHResourceAvailable is used when the UE has no valid SR PUCCH resources configured [3]. The indicator requestForOtherSI is used for MSG1 based on demand SI request. The indicator msg3RequestForOtherSI is used in case of MSG3 based SI request. The indication lbtFailure is used when the UE initiates RACH in SpCell due to consistent uplink LBT failures [3]. The field can also be used for the SCG-related RA-Report when the raPurpose is set to beamFailureRecovery , reconfigurationWithSync , ulUnSynchronized , schedulingRequestFailure and noPUCCHResourceAvailable . | +| spCellID
This field is used to indicate the CGI of the SpCell of the cell group associated to the SCell in which the associated random access procedure was performed. If the UE performs RA procedure on a SCell associated to the MCG, then this field is set to the CGI of the PCell and if the UE performs RA procedure on a SCell associated to the SCG, then this field is set to the CGI of the PSCell. If the CGI of the PSCell is not available at the UE for the RA procedure performed on a SCell associated to the SCG or for the RA procedure on the PSCell, this field is set to the CGI of the PCell. Otherwise, the field is absent. | +| ssb-Index
This field is used to indicate the SS/PBCH index of the SS/PBCH block corresponding to the random access attempt. | + +#### ***ssbsForSI-Acquisition*** + +This field indicates the SSB(s) (in the form of SSB index(es)) that the UE used to receive the requested SI message(s). The field is present if the purpose of the random access procedure was to request on-demand SI (i.e. if the *raPurpose* is set to *requestForOtherSI* or *msg3RequestForOtherSI*). Otherwise, the field is absent. + +| RLF-Report field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| bwp-Info
This field is used to indicate the BWP information in which the UE detected consistent uplink LBT failure. This field is set only when the detected consistent uplink LBT failure did not trigger the random access procedure. | +| choCandidateCellList
This field is used to indicate the list of candidate target cells for conditional handover included in condRRCReconfig at the time of connection failure. The field does not include the candidate target cells included in measResultNeighCells . | +| choCellId
This field is used to indicate the candidate target cell for conditional handover included in condRRCReconfig that the UE selected for CHO based recovery while T311 is running. | +| connectionFailureType
This field is used to indicate whether the connection failure is due to radio link failure or handover failure. | +| csi-rsRLMConfigBitmap, csi-rsRLMConfigBitmap-v1650
These fields are used to indicate the CSI-RS indexes configured in the RLM configurations for the active BWP when the UE declares RLF or HOF. The UE first fills in the csi-rsRLMConfigBitmap-r16 to indicate the first 96 CSI-RS indexes and then csi-rsRLMConfigBitmap-v1650 to indicate the latter 96 CSI-RS indexes. The first/leftmost bit in csi-rsRLMConfigBitmap-r16 corresponds to CSI-RS index 0, the second bit corresponds to CSI-RS index 1. The first/leftmost bit in csi-rsRLMConfigBitmap-v1650 corresponds to CSI-RS index 96, the second bit corresponds to CSI-RS index 97. These fields are included only if the RadioLinkMonitoringConfig for the respective BWP is configured. | +| c-RNTI
This field indicates the C-RNTI used in the PCell upon detecting radio link failure or the C-RNTI used in the source PCell upon handover failure. | +| elapsedTimeSCGFailure
This field is used to indicate the time elapsed between the SCG failure and the MCG failure. The maximum value 1023 means 1023ms or longer. | +| elapsedTimeT316
This field is used to indicate the time elapsed between the initiation of the MCGFailureInformation and the reception of the RRReconfiguration or RRRelease or MobilityFromNRCommand messages. | +| failedPCellId
This field is used to indicate the PCell in which RLF is detected or the target PCell of the failed handover. For intra-NR handover nrFailedPCellId is included and for the handover from NR to EUTRA eutraFailedPCellId is included. The UE sets the ARFCN according to the frequency band used for transmission/ reception when the failure occurred. | +| failedPCellId-EUTRA
This field is used to indicate the PCell in which RLF is detected or the source PCell of the failed handover in an E-UTRA RLF report. | +| lastHO-Type
This field is used to indicate the type of the last executed handover before the last detected connection failure. The field is set to cho if the last executed handover was initiated by a conditional reconfiguration execution. The field is set to daps if the last executed handover was a DAPS handover. | +| mcgRecoveryFailureCause
This field is used to indicate the cause of the fast MCG recovery failure. | +| measResultListEUTRA
This field refers to the last measurement results taken in the neighboring EUTRA Cells, when the radio link failure or handover failure happened. | +| measResultListNR
This field refers to the last measurement results taken in the neighboring NR Cells, when the radio link failure or handover failure happened. | +| measResultLastServCell
This field refers to the log measurement results taken in the PCell upon detecting radio link failure or the source PCell upon handover failure. | +| measResultLastServCell-RSSI
This field refers to the log RSSI measurement results in dBm (see TS 38.215 [9]) taken for the frequency of the PCell upon detecting radio link failure or handover failure. | + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| measResultNeighFreqList-RSSI
This field is used to log the RSSI measurement results in dBm (see TS 38.215 [9]) taken for the neighbouring frequencies upon detecting radio link failure or handover failure, when UE operates in unlicensed spectrum. | +| measResult-RLF-Report-EUTRA
Includes the E-UTRA RLF-Report-r9 IE as specified in TS 36.331 [10]. | +| measResult-RLF-Report-EUTRA-v1690
Includes the E-UTRA RLF-Report-v9e0 IE as specified in TS 36.331 [10]. | +| noSuitableCellFound
This field is set by the UE when the T311 expires. | +| previousPCellId
This field is used to indicate the source PCell of the last handover (source PCell when the last executed RRCREconfiguration message including reconfigurationWithSync was received). For intra-NR handover nrPreviousCell is included and for the handover from EUTRA to NR eutraPreviousCell is included. | +| pSCellId
This field is used to indicate the PSCell in which the UE failed to perform fast MCG recovery procedure or the UE successfully performed fast MCG recovery procedure. | +| ra-InformationCommon
This field is optionally included when connectionFailureType is set to 'hof' or when connectionFailureType is set to 'rlf' and the rlf-Cause equals to 'randomAccessProblem' or 'beamRecoveryFailure'; otherwise this field is absent. | +| reconnectCellId
This field is used to indicate the cell in which the UE comes back to connected after connection failure and after failing to perform reestablishment. If the UE comes back to RRC CONNECTED in an NR cell then nrReconnectCellID is included and if the UE comes back to RRC CONNECTED in an LTE cell then eutraReconnectCellID is included | +| reestablishmentCellId
If the UE was not configured with conditionalReconfiguration at the time of re-establishment attempt, or if the cell selected for the re-establishment attempt is not a candidate target cell for conditional reconfiguration, this field is used to indicate the cell in which the re-establishment attempt was made after connection failure. | +| rlf-Cause
This field is used to indicate the cause of the last radio link failure that was detected. In case of handover failure information reporting (i.e., the connectionFailureType is set to 'hof'), the UE is allowed to set this field to any value, except for the case in which a radio link failure was detected in the source PCell while performing a DAPS handover.. | +| ssbRLMConfigBitmap
This field is used to indicate the SS/PBCH block indexes configured in the RLM configurations for the active BWP when the UE declares RLF or HOF. The first/leftmost bit corresponds to SSB index 0, the second bit corresponds to SSB index 1. This field is included only if the RadioLinkMonitoringConfig for the respective BWP is configured. | +| timeConnFailure
This field is used to indicate the time elapsed since the last HO execution until connection failure. Actual value = field value * 100ms. The maximum value 1023 means 102.3s or longer. | +| timeConnSourceDAPS-Failure
This field is used to indicate the time that elapsed between the last DAPS handover execution and the radio link failure detected in the source cell while T304 is running. Value in milliseconds. The maximum value 1023 means 1023ms or longer. | +| timeSinceFailure
This field is used to indicate the time that elapsed since the connection (radio link or handover) failure. Value in seconds. The maximum value 172800 means 172800s or longer. In the case of failure(s) (either at source or at target or at both) associated to DAPS handover, this field indicates the time elapsed since the latest connection (radio link or handover) failure. | +| timeSinceCHO-Reconfig
In case of handover failure, this field is used to indicate the time elapsed between the initiation of the last handover execution towards the target cell and the reception of the latest conditional reconfiguration. In case of radio link failure, this field is used to indicate the time elapsed between the radio link failure and the reception of the latest conditional reconfiguration while connected to the source PCell. Actual value = field value * 100ms. The maximum value 1023 means 102.3s or longer. | +| timeUntilReconnection | + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| This field is used to indicate the time that elapsed between the connection (radio link or handover) failure and the next time the UE comes to RRC CONNECTED in an NR or EUTRA cell, after failing to perform reestablishment. Value in seconds. The maximum value 172800 means 172800s or longer. | +| voiceFallbackHO
This field is set if for the failed mobility from NR, the voiceFallbackIndication was included in the MobilityFromNRCommand message. | + +| SuccessHO-Report field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| c-RNTI
This field indicates the C-RNTI assigned by the target PCell of the handover for which the successful HO report was generated. | +| eutraTargetCellInfo
This field is used to indicate the target EUTRA PCell and the last measurement results of the target PCell of a handover in which the successful handover triggers the SuccessHO-Report . | +| eutra-C-RNTI
This field indicates the C-RNTI assigned by the E-UTRA target PCell of the mobility from NR command for which the successful HO report was generated. | +| measResultListNR
This field refers to the last measurement results taken in the neighboring NR Cells when a successful handover is executed. | +| measResultNeighFreqList-RSSI
This field is used to log the RSSI measurement results in dBm (see TS 38.215 [9]) taken for the neighbouring frequencies upon successful handover execution. | +| measResultServCell-RSSI
This field refers to the log RSSI measurement results in dBm (see TS 38.215 [9]) taken for the frequency of the source PCell upon successful handover execution. | +| rlf-InSourceDAPS
This field indicates whether a radio link failure occurred at the source cell while T304 was running. | +| shr-Cause
This field is used to indicate the cause of the successful HO report. | +| sourceCellMeas
This field refers to the last measurement results taken in the source PCell of a handover in which the successful handover triggers the SuccessHO-Report . | +| sourcePCellId
This field is used to indicate the source PCell of a handover in which the successful handover triggers the SuccessHO-Report . | +| targetPCellId
This field is used to indicate the target PCell of a handover in which the successful handover triggers the SuccessHO-Report . | +| targetCellMeas
This field refers to the last measurement results taken in the target PCell of a handover in which the successful handover triggers the SuccessHO-Report . | +| timeSinceCHO-Reconfig
This field is used to indicate the time elapsed between the initiation of the last conditional reconfiguration execution towards the target cell and the reception of the latest conditional reconfiguration for this target cell. Actual value = field value * 100ms. The maximum value 1023 means 102.3s or longer. | +| timeSinceSHR
This field is used to indicate the time elapsed since the execution of the last MobilityFromNRCommand towards the target EUTRA cell. Value in seconds. The maximum value 172800 means 172800s or longer. | +| upInterruptionTimeAtHO
This field is used to indicate the time elapsed between the time of arrival of the last PDCP PDU received from the source cell for any data radio bearer and the time of arrival of the first non-duplicate PDCP PDU received from the target cell for any data radio bearer, and it is measured at the time of arrival of the first non-duplicate PDCP PDU received from the target cell for any data radio bearer. The field is set only in case of DAPS handover. Value in milliseconds. The maximum value 1023 means 1023ms or longer. | + +| FlightPathInfoReport field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| timeStamp
Time stamp that describes estimated time of arrival, if available, of the Aerial UE at the corresponding wayPointLocation. | +| wayPointLocation
Location coordinates of the planned waypoint. Parameter type LocationCoordinates defined in TS 37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit. | + +| SuccessPSCell-Report field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| measResultListNR
This field refers to the last measurement results according to the initiating node configuration taken in the neighboring NR Cells when a successful PSCell change/addition is executed. | +| pCellId
This field is used to indicate the PCell to which the UE was connected when the successful PSCell change or addition triggers the SuccessPSCell-Report . | +| sn-InitiatedPSCellChange
This field indicates whether the PSCell change procedure for which the successful PSCell change report is logged is SN initiated or not. | +| spr-Cause
This field is used to indicate the cause of the successful PSCell change or addition report. | +| sourcePSCellId
This field is used to indicate the source PSCell of a PSCell change in which the successful PSCell change triggers the SuccessPSCell-Report . | +| sourcePSCellMeas
This field refers to the last measurement results taken in the source PSCell of a PSCell change in which the successful PSCell change triggers the SuccessPSCell-Report . | +| targetPSCellId
This field is used to indicate the target PSCell of a PSCell change/addition in which the successful PSCell change or addition triggers the SuccessPSCell-Report . | +| targetPSCellMeas
This field refers to the last measurement results taken in the target PSCell of a PSCell change/addition in which the successful PSCell change or addition triggers the SuccessPSCell-Report . | +| timeSinceCPAC-Reconfig
This field is used to indicate the time elapsed between the initiation of the last conditional reconfiguration execution towards the target PSCell and the reception of the latest conditional reconfiguration for this target PSCell. Actual value = field value * 100ms. The maximum value 1023 means 102.3s or longer. | + +#### – UEPositioningAssistanceInfo + +The *UEPositioningAssistanceInfo* message is used to provide positioning assistance information as requested by the Network. + +Signalling radio bearer: SRB1 + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: UE to Network + +#### **UEPositioningAssistanceInfo message** + +``` + +-- ASN1START +-- TAG-UEPOSITIONINGASSISTANCEINFO-START + +UEPositioningAssistanceInfo-r17 ::= SEQUENCE { + criticalExtensions CHOICE { + uePositioningAssistanceInfo-r17 UEPositioningAssistanceInfo-r17-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +UEPositioningAssistanceInfo-r17-IEs ::= SEQUENCE { + ue-TxTEG-AssociationList-r17 UE-TxTEG-AssociationList-r17 OPTIONAL, + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension UEPositioningAssistanceInfo-v1720-IEs OPTIONAL +} + +UEPositioningAssistanceInfo-v1720-IEs ::= SEQUENCE { + ue-TxTEG-TimingErrorMarginValue-r17 ENUMERATED {tc0, tc2, tc4, tc6, tc8, tc12, tc16, tc20, tc24, tc32, tc40, tc48, tc56, + tc64, tc72, tc80} OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +UE-TxTEG-AssociationList-r17 ::= SEQUENCE (SIZE (1..maxNrOfTxTEGReport-r17)) OF UE-TxTEG-Association-r17 + +UE-TxTEG-Association-r17 ::= SEQUENCE { + ue-TxTEG-ID-r17 INTEGER (0..maxNrOfTxTEG-ID-1-r17), + nr-TimeStamp-r17 NR-TimeStamp-r17, + associatedSRS-PosResourceIdList-r17 SEQUENCE (SIZE (1..maxNrOfSRS-PosResources-r16)) OF SRS-PosResourceId-r16, + servCellId-r17 ServCellIndex OPTIONAL +} + +NR-TimeStamp-r17 ::= SEQUENCE { + nr-SFN-r17 INTEGER (0..1023), + nr-Slot-r17 CHOICE { + scs15-r17 INTEGER (0..9), + scs30-r17 INTEGER (0..19), + scs60-r17 INTEGER (0..39), + scs120-r17 INTEGER (0..79) + }, + ... +} + +-- TAG-UEPOSITIONINGASSISTANCEINFO-STOP +-- ASN1STOP + +``` + +| UEPositioningAssistanceInfo field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| nr-Timestamp
This field specifies the latest time instance at which the association is valid prior to the reporting. | +| servCellID
This field indicates the serving cell information of SRS for positioning resources associated to the UE Tx TEG report. | +| ue-TxTEG-ID
Identifies the ID of UE Tx TEG. | +| ue-TxTEG-TimingErrorMarginValue
This field specifies the UE Tx TEG timing error margin value of all the UE Tx TEGs within one UEPositioningAssistanceInfo . Value tc0 corresponds to 0 Tc, tc2 corresponds to 2 Tc and so on (see TS 37.355 [49]). | + +#### – **ULDedicatedMessageSegment** + +The *ULDedicatedMessageSegment* message is used to transfer segments of the *UECapabilityInformation* or *MeasurementReportAppLayer* message. SRB1 is used at transfer of segments of *UECapabilityInformation* and SRB4 or SRB5 is used at transfer of segments of *MeasurementReportAppLayer*. + +Signalling radio bearer: SRB1, SRB4 or SRB5 + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: UE to Network + +#### **ULDedicatedMessageSegment message** + +``` +-- ASN1START +-- TAG-ULDEDICATEDMESSAGESEGMENT-START + +ULDedicatedMessageSegment-r16 ::= SEQUENCE { + criticalExtensions CHOICE { + ulDedicatedMessageSegment-r16 ULDedicatedMessageSegment-r16-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +ULDedicatedMessageSegment-r16-IEs ::= SEQUENCE { + segmentNumber-r16 INTEGER (0..15), + rrc-MessageSegmentContainer-r16 OCTET STRING, + rrc-MessageSegmentType-r16 ENUMERATED {notLastSegment, lastSegment}, + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +-- TAG-ULDEDICATEDMESSAGESEGMENT-STOP +``` + +-- ASN1STOP + +| ULDedicatedMessageSegment field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| segmentNumber
Identifies the sequence number of a segment within the encoded UL DCCH message. | +| rrc-MessageSegmentContainer
Includes a segment of the encoded UL DCCH message. The size of the included segment in this container should be small enough that the resulting encoded RRC message PDU is less than or equal to the PDCP SDU size limit. | +| rrc-MessageSegmentType
Indicates whether the included UL DCCH message segment is the last segment or not. | + +#### – ***ULInformationTransfer*** + +The *ULInformationTransfer* message is used for the uplink transfer of NAS or non-3GPP dedicated information, or IAB-DU specific F1-C related information. + +Signalling radio bearer: SRB2 or SRB1 (only if SRB2 not established yet). If SRB2 is suspended, the UE does not send this message until SRB2 is resumed. If only *dedicatedInfoF1c* is included, SRB2 is used. + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: UE to network + +#### ***ULInformationTransfer* message** + +``` +-- ASN1START +-- TAG-ULINFORMATIONTRANSFER-START + +ULInformationTransfer ::= SEQUENCE { + criticalExtensions CHOICE { + ulInformationTransfer ULInformationTransfer-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +ULInformationTransfer-IEs ::= SEQUENCE { + dedicatedNAS-Message DedicatedNAS-Message OPTIONAL, + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension ULInformationTransfer-v1700-IEs OPTIONAL +} + +ULInformationTransfer-v1700-IEs ::= SEQUENCE { + dedicatedInfoF1c-r17 DedicatedInfoF1c-r17 OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} +``` + +``` + +} +-- TAG-ULINFORMATIONTRANSFER-STOP +-- ASN1STOP + +``` + +#### – *ULInformationTransferIRAT* + +The *ULInformationTransferIRAT* message is used for the uplink transfer of information terminated at NR MCG but specified by another RAT. In this version of the specification, the message is used for V2X sidelink communication messages specified in TS 36.331 [10]. + +Signalling radio bearer: SRB1 + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: UE to network + +#### *ULInformationTransferIRAT* message + +``` + +-- ASN1START +-- TAG-ULINFORMATIONTRANSFERIRAT-START + +ULInformationTransferIRAT-r16 ::= + SEQUENCE { + criticalExtensions + CHOICE { + c1 + CHOICE { + ulInformationTransferIRAT-r16 + ULInformationTransferIRAT-r16-IEs, + spare3 NULL, spare2 NULL, spare1 NULL + }, + criticalExtensionsFuture + SEQUENCE {} + } + } + +ULInformationTransferIRAT-r16-IEs ::= + SEQUENCE { + ul-DCCH-MessageEUTRA-r16 + OCTET STRING + OPTIONAL, + lateNonCriticalExtension + OCTET STRING + OPTIONAL, + nonCriticalExtension + SEQUENCE {} + OPTIONAL + } + +-- TAG-ULINFORMATIONTRANSFERIRAT-STOP +-- ASN1STOP + +``` + +##### | | |----------------------------------------------------| | ULInformationTransferRAT field descriptions | |----------------------------------------------------| + +###### | | |-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | ul-DCCH-MessageEUTRA
Includes the UL-DCCH-Message as defined in TS 36.331 [10]. In this version of the specification, the field is only used to transfer the E-UTRA RRC MeasurementReport , E-UTRA RRC SidelinkUEInformation and the E-UTRA RRC UEAssistanceInformation messages. | |-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +#### – ULInformationTransferMRDC + +The *ULInformationTransferMRDC* message is used for the uplink transfer of MR-DC dedicated information (e.g. for transferring the NR or E-UTRA RRC *MeasurementReport* message, the *FailureInformation* message, the *UEAssistanceInformation* message, the *RRCReconfigurationComplete* message, the *IABOtherInformation* message or the NR or E-UTRA RRC *MCGFailureInformation* message). + +Signalling radio bearer: SRB1, SRB3 + +RLC-SAP: AM + +Logical channel: DCCH + +Direction: UE to Network + +##### ULInformationTransferMRDC message + +``` +-- ASN1START +-- TAG-ULINFORMATIONTRANSFERMRDC-START + +ULInformationTransferMRDC ::= + SEQUENCE { + criticalExtensions + CHOICE { + c1 + CHOICE { + ulInformationTransferMRDC + spare3 NULL, spare2 NULL, spare1 NULL + }, + ULInformationTransferMRDC-IEs, + criticalExtensionsFuture + SEQUENCE {} + } + } + +ULInformationTransferMRDC-IEs ::= + SEQUENCE { + ul-DCCH-MessageNR + OCTET STRING + OPTIONAL, + ul-DCCH-MessageEUTRA + OCTET STRING + OPTIONAL, + lateNonCriticalExtension + OCTET STRING + OPTIONAL, + nonCriticalExtension + SEQUENCE {} + OPTIONAL + } + +-- TAG-ULINFORMATIONTRANSFERMRDC-STOP +-- ASN1STOP +``` + +| ULInformationTransferMRDC field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ul-DCCH-MessageNR
Includes the UL-DCCH-Message . In this version of the specification, the field is only used to transfer the NR RRC MeasurementReport , RRCReconfigurationComplete , UEAssistanceInformation , FailureInformation , and IABOtherInformation messages when sent via SRB1 and to transfer the NR MCGFailureInformation message when sent via SRB3. | +| ul-DCCH-MessageEUTRA
Includes the UL-DCCH-Message . In this version of the specification, the field is only used to transfer the E-UTRA RRC MeasurementReport message when sent via SRB1 and to transfer the E-UTRA MCGFailureInformation message when sent via SRB3. | + +## 6.3 RRC information elements + +### 6.3.0 Parameterized types + +#### – *SetupRelease* + +*SetupRelease* allows the *ElementTypeParam* to be used as the referenced data type for the setup and release entries. See A.3.8 for guidelines. + +``` +-- ASN1START +-- TAG-SETUPRELEASE-START + +SetupRelease { ElementTypeParam } ::= CHOICE { + release NULL, + setup ElementTypeParam +} + +-- TAG-SETUPRELEASE-STOP +-- ASN1STOP +``` + +### 6.3.1 System information blocks + +#### – *SIB2* + +*SIB2* contains cell re-selection information common for intra-frequency, inter-frequency and/or inter-RAT cell re-selection (i.e. applicable for more than one type of cell re-selection but not necessarily all) as well as intra-frequency cell re-selection information other than neighbouring cell related. + +#### **SIB2 information element** + +``` +-- ASN1START +-- TAG-SIB2-START + +SIB2 ::= SEQUENCE { + cellReselectionInfoCommon SEQUENCE { +``` + +``` + +nrofSS-BlocksToAverage INTEGER (2..maxNrofSS-BlocksToAverage) OPTIONAL, -- Need S +absThreshSS-BlocksConsolidation ThresholdNR OPTIONAL, -- Need S +rangeToBestCell RangeToBestCell OPTIONAL, -- Need R +q-Hyst ENUMERATED { + dB0, dB1, dB2, dB3, dB4, dB5, dB6, dB8, dB10, + dB12, dB14, dB16, dB18, dB20, dB22, dB24}, +speedStateReselectionPars SEQUENCE { + mobilityStateParameters + q-HystSF SEQUENCE { + sf-Medium ENUMERATED {dB-6, dB-4, dB-2, dB0}, + sf-High ENUMERATED {dB-6, dB-4, dB-2, dB0} + } +} OPTIONAL, -- Need R +... +}, +cellReselectionServingFreqInfo SEQUENCE { + s-NonIntraSearchP ReselectionThreshold OPTIONAL, -- Need S + s-NonIntraSearchQ ReselectionThresholdQ OPTIONAL, -- Need S + threshServingLowP ReselectionThreshold, + threshServingLowQ ReselectionThresholdQ OPTIONAL, -- Need R + cellReselectionPriority CellReselectionPriority, + cellReselectionSubPriority CellReselectionSubPriority OPTIONAL, -- Need R + ... +}, +intraFreqCellReselectionInfo SEQUENCE { + q-RxLevMin Q-RxLevMin, + q-RxLevMinSUL Q-RxLevMin OPTIONAL, -- Need R + q-QualMin Q-QualMin OPTIONAL, -- Need S + s-IntraSearchP ReselectionThreshold, + s-IntraSearchQ ReselectionThresholdQ OPTIONAL, -- Need S + t-ReselectionNR T-Reselection, + frequencyBandList MultiFrequencyBandListNR-SIB OPTIONAL, -- Need S + frequencyBandListSUL MultiFrequencyBandListNR-SIB OPTIONAL, -- Need R + p-Max P-Max OPTIONAL, -- Need S + smtc SSB-MTC OPTIONAL, -- Need S + ss-RSSI-Measurement SS-RSSI-Measurement OPTIONAL, -- Need R + ssb-ToMeasure SSB-ToMeasure OPTIONAL, -- Need S + deriveSSB-IndexFromCell BOOLEAN, + ..., + [[ + t-ReselectionNR-SF SpeedStateScaleFactors OPTIONAL -- Need N + ]], + [[ + smtc2-LP-r16 SSB-MTC2-LP-r16 OPTIONAL, -- Need R + ssb-PositionQCL-Common-r16 SSB-PositionQCL-Relation-r16 OPTIONAL -- Cond SharedSpectrum + ]], + [[ + ssb-PositionQCL-Common-r17 SSB-PositionQCL-Relation-r17 OPTIONAL -- Cond SharedSpectrum2 + ]], + [[ + smtc4list-r17 SSB-MTC4List-r17 OPTIONAL -- Need R + ]]] + +``` + +``` + + ]], + [[ + frequencyBandList-v1760 MultiFrequencyBandListNR-SIB-v1760 OPTIONAL, -- Need R + frequencyBandListSUL-v1760 MultiFrequencyBandListNR-SIB-v1760 OPTIONAL -- Need R + ]], + [[ + frequencyBandListAerial-r18 MultiFrequencyBandListNR-Aerial-SIB-r18 OPTIONAL -- Need S + ]] + ], + ... + [[ + relaxedMeasurement-r16 SEQUENCE { + lowMobilityEvaluation-r16 SEQUENCE { + s-SearchDeltaP-r16 ENUMERATED { + dB3, dB6, dB9, dB12, dB15, + spare3, spare2, spare1}, + t-SearchDeltaP-r16 ENUMERATED { + s5, s10, s20, s30, s60, s120, s180, + s240, s300, spare7, spare6, spare5, + spare4, spare3, spare2, spare1} + } + cellEdgeEvaluation-r16 SEQUENCE { + s-SearchThresholdP-r16 ReselectionThreshold, + s-SearchThresholdQ-r16 ReselectionThresholdQ + } + combineRelaxedMeasCondition-r16 ENUMERATED {true} + highPriorityMeasRelax-r16 ENUMERATED {true} + } + ], + [[ + cellEquivalentSize-r17 INTEGER(2..16) + relaxedMeasurement-r17 SEQUENCE { + stationaryMobilityEvaluation-r17 SEQUENCE { + s-SearchDeltaP-Stationary-r17 ENUMERATED {dB2, dB3, dB6, dB9, dB12, dB15, spare2, spare1}, + t-SearchDeltaP-Stationary-r17 ENUMERATED {s5, s10, s20, s30, s60, s120, s180, s240, s300, spare7, spare6, spare5, + spare4, spare3, spare2, spare1} + }, + cellEdgeEvaluationWhileStationary-r17 SEQUENCE { + s-SearchThresholdP2-r17 ReselectionThreshold, + s-SearchThresholdQ2-r17 ReselectionThresholdQ + } + combineRelaxedMeasCondition2-r17 ENUMERATED {true} + } + ]] +} + +RangeToBestCell := Q-OffsetRange + +-- TAG-SIB2-STOP +-- ASN1STOP + +``` + +| SIB2 field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| absThreshSS-BlocksConsolidation
Threshold for consolidation of L1 measurements per RS index. If the field is absent, the UE uses the measurement quantity as specified in TS 38.304 [20]. | +| cellEdgeEvaluation
Indicates the criteria for a UE to detect that it is not at cell edge, in order to relax measurement requirements for cell reselection (see TS 38.304 [20], clause 5.2.4.9.2). | +| cellEdgeEvaluationWhileStationary
Indicates the criteria for a UE to detect that it is not at cell edge while stationary, in order to relax measurement requirements for cell reselection (see TS 38.304 [20], clause 5.2.4.9.4). | +| cellEquivalentSize
The number of cell count used for mobility state estimation for this cell as specified in TS 38.304 [20]. | +| cellReselectionInfoCommon
Cell re-selection information common for intra-frequency, inter-frequency and/ or inter-RAT cell re-selection. | +| cellReselectionServingFreqInfo
Information common for non-intra-frequency cell re-selection i.e. cell re-selection to inter-frequency and inter-RAT cells. | +| combineRelaxedMeasCondition
When both lowMobilityEvaluation and cellEdgeEvaluation criteria are present in SIB2, this parameter configures the UE to fulfil both criteria in order to relax measurement requirements for cell reselection. If the field is absent, the UE is allowed to relax measurement requirements for cell reselection when either or both of the criteria are met. (See TS 38.304 [20], clause 5.2.4.9.0) | +| combineRelaxedMeasCondition2
When both stationaryMobilityEvaluation and cellEdgeEvaluationWhileStationary criteria are present in SIB2, this parameter configures the UE to fulfil both criteria in order to relax measurement requirements for cell reselection. If the field is absent, the UE is allowed to relax measurement requirements for cell reselection when only the stationary criteria is met. (See TS 38.304 [20], clause 5.2.4.9.0) | +| deriveSSB-IndexFromCell
This field indicates whether the UE can utilize serving cell timing to derive the index of SS block transmitted by neighbour cell. If this field is set to true , the UE assumes SFN and frame boundary alignment across cells on the serving frequency as specified in TS 38.133 [14]. | +| frequencyBandList
Indicates the list of frequency bands for which the NR cell reselection parameters apply. The UE behaviour in case the field is absent is described in clause 5.2.2.4.3. | +| frequencyBandListAerial
Indicates the list of frequency bands for aerial operation for which the NR cell reselection parameters apply. The UE behaviour in case the field is absent is described in clause 5.2.2.4.3. | +| highPriorityMeasRelax
Indicates whether measurements can be relaxed on high priority frequencies. If the field is absent, the UE shall not relax measurements on high priority frequencies beyond "T higher_priority_search " unless both low mobility and not at cell edge criteria are fulfilled (see TS 38.133 [14], clauses 4.2.2.7, 4.2.2.10 and 4.2.2.11). | +| intraFreqCellReselectionInfo
Cell re-selection information common for intra-frequency cells. | +| lowMobilityEvaluation
Indicates the criteria for a UE to detect low mobility, in order to relax measurement requirements for cell reselection (see TS 38.304 [20], clause 5.2.4.9.1). | +| nrofSS-BlocksToAverage
Number of SS blocks to average for cell measurement derivation. If the field is absent the UE uses the measurement quantity as specified in TS 38.304 [20]. | +| p-Max
Value in dBm applicable for the intra-frequency neighbouring NR cells. If absent the UE applies the maximum power according to TS 38.101-1 [15] in case of an FR1 cell, TS 38.101-2 [39] in case of an FR2 cell or TS 38.101-5 [75] in case of an NTN cell. In this release of the specification, if p-Max is present on a carrier frequency in FR2, the UE shall ignore the field and applies the maximum power according to TS 38.101-2 [39]. This field is ignored by IAB-MT. The IAB-MT applies output power and emissions requirements, as specified in TS 38.174 [63]. | + +| SIB2 field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| q-Hyst
Parameter "Q hyst " in TS 38.304 [20], Value in dB. Value dB1 corresponds to 1 dB, dB2 corresponds to 2 dB and so on. | +| q-HystSF
Parameter "Speed dependent ScalingFactor for Qhyst" in TS 38.304 [20]. The sf-Medium and sf-High concern the additional hysteresis to be applied, in Medium and High Mobility state respectively, to Qhyst as defined in TS 38.304 [20]. In dB. Value dB-6 corresponds to -6dB, dB-4 corresponds to -4dB and so on. | +| q-QualMin
Parameter "Q qualmin " in TS 38.304 [20], applicable for intra-frequency neighbour cells. If the field is absent, the UE applies the (default) value of negative infinity for Q qualmin . | +| q-RxLevMin
Parameter "Q rxlevmin " in TS 38.304 [20], applicable for intra-frequency neighbour cells. | +| q-RxLevMinSUL
Parameter "Q rxlevmin " in TS 38.304 [20], applicable for intra-frequency neighbour cells. | +| rangeToBestCell
Parameter "rangeToBestCell" in TS 38.304 [20]. The network configures only non-negative (in dB) values. | +| relaxedMeasurement
Configuration to allow relaxation of RRM measurement requirements for cell reselection (see TS 38.304 [20], clause 5.2.4.9). In NTN, this field is only applicable for GSO neighbour cells. | +| s-IntraSearchP
Parameter "S IntraSearchP " in TS 38.304 [20]. | +| s-IntraSearchQ
Parameter "S IntraSearchQ " in TS 38.304 [20]. If the field is absent, the UE applies the (default) value of 0 dB for S IntraSearchQ . | +| s-NonIntraSearchP
Parameter "S NonIntraSearchP " in TS 38.304 [20]. If this field is absent, the UE applies the (default) value of infinity for S NonIntraSearchP . | +| s-NonIntraSearchQ
Parameter "S NonIntraSearchQ " in TS 38.304 [20]. If the field is absent, the UE applies the (default) value of 0 dB for S NonIntraSearchQ . | +| s-SearchDeltaP
Parameter "S SearchDeltaP " in TS 38.304 [20]. Value dB3 corresponds to 3 dB, dB6 corresponds to 6 dB and so on. | +| s-SearchDeltaP-Stationary
Parameter "S SearchDeltaP-Stationary " in TS 38.304 [20]. Value dB2 corresponds to 2 dB, dB3 corresponds to 3 dB and so on. | +| s-SearchThresholdP, s-SearchThresholdP2
Parameters "S SearchThresholdP " and "S SearchThresholdP2 " in TS 38.304 [20]. The network configures s-SearchThresholdP and s-SearchThresholdP2 to be less than or equal to s-IntraSearchP and s-NonIntraSearchP . | +| s-SearchThresholdQ, s-SearchThresholdQ2
Parameters "S SearchThresholdQ " and "S SearchThresholdQ2 " in TS 38.304 [20]. The network configures s-SearchThresholdQ and s-SearchThresholdQ2 to be less than or equal to s-IntraSearchQ and s-NonIntraSearchQ . | +| smtc
Measurement timing configuration for intra-frequency measurement. If this field is absent, the UE assumes that SSB periodicity is 5 ms for the intra-frequency cells. If the field is broadcast by an NTN cell, the offset (derived from parameter periodicityAndOffset ) is based on the assumption that the gNB-UE propagation delay difference between the serving cell and neighbour cells equals to 0 ms, and UE can adjust the actual offset based on the actual propagation delay difference. | + +| SIB2 field descriptions | | +|--------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| smtc2-LP | Measurement timing configuration for intra-frequency neighbour cells with a Long Periodicity (LP) indicated by periodicity in smtc2-LP . The timing offset and duration are equal to the offset and duration indicated in smtc in intraFreqCellReselectionInfo . The periodicity in smtc2-LP can only be set to a value strictly larger than the periodicity in smtc in intraFreqCellReselectionInfo (e.g. if smtc indicates sf20 the Long Periodicity can only be set to sf40, sf80 or sf160, if smtc indicates sf160, smtc2-LP cannot be configured). The pci-List , if present, includes the physical cell identities of the intra-frequency neighbour cells with Long Periodicity. If smtc2-LP is absent, the UE assumes that there are no intra-frequency neighbour cells with a Long Periodicity. | +| smtc4list | Measurement timing configuration list for NTN deployments, see clause 5.5.2.10. The offset of each SSB-MTC4 in smtc4list is based on the assumption that the gNB-UE propagation delay difference between the serving cell and neighbour cells equals to 0 ms, and UE can adjust the actual offset based on the actual propagation delay difference. For a UE that supports less SMTCs than what is included in this list, it is up to the UE to select which SMTCs to consider. | +| ssb-PositionQCL-Common | Indicates the QCL relation between SS/PBCH blocks for intra-frequency neighbor cells as specified in TS 38.213 [13], clause 4.1. | +| ssb-ToMeasure | The set of SS blocks to be measured within the SMTC measurement duration (see TS 38.215 [9]). When the field is absent the UE measures on all SS-blocks. | +| stationaryMobilityEvaluation | Indicates the criteria for a UE to detect stationary mobility, in order to relax measurement requirements for cell reselection (see TS 38.304 [20], clause 5.2.4.9.0). | +| t-ReselectionNR | Parameter "T reselectionNR " in TS 38.304 [20]. | +| t-ReselectionNR-SF | Parameter "Speed dependent ScalingFactor for T reselectionNR " in TS 38.304 [20]. If the field is absent, the UE behaviour is specified in TS 38.304 [20]. | +| threshServingLowP | Parameter "Thresh Serving, LowP " in TS 38.304 [20]. | +| threshServingLowQ | Parameter "Thresh Serving, LowQ " in TS 38.304 [20]. | +| t-SearchDeltaP | Parameter "T SearchDeltaP " in TS 38.304 [20]. Value in seconds. Value s5 means 5 seconds, value s10 means 10 seconds and so on. | +| t-SearchDeltaP-Stationary | Parameter "T SearchDeltaP-Stationary " in TS 38.304 [20]. Value in seconds. Value s5 means 5 seconds, value s10 means 10 seconds and so on. | + +| Conditional Presence | Explanation | +|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| HSDN | The field is optionally present, Need R, if speedStateReselectionPars is present; otherwise the field is not present. | +| SharedSpectrum | This field is mandatory present if this intra-frequency operates with shared spectrum channel access in FR1. Otherwise, it is absent, Need R. | +| SharedSpectrum2 | This field is optionally present if this intra-frequency operates with shared spectrum channel access in FR2-2, Need R. Otherwise, it is absent, Need R. | + +##### – SIB3 + +*SIB3* contains neighbouring cell related information relevant only for intra-frequency cell re-selection. The IE includes cells with specific re-selection parameters as well as exclude-listed cells. + +#### SIB3 information element + +``` + +-- ASN1START +-- TAG-SIB3-START + +SIB3 ::= SEQUENCE { + intraFreqNeighCellList IntraFreqNeighCellList OPTIONAL, -- Need R + intraFreqExcludedCellList IntraFreqExcludedCellList OPTIONAL, -- Need R + lateNonCriticalExtension OCTET STRING OPTIONAL, + ... + [[ + intraFreqNeighCellList-v1610 IntraFreqNeighCellList-v1610 OPTIONAL, -- Need R + intraFreqAllowedCellList-r16 IntraFreqAllowedCellList-r16 OPTIONAL, -- Cond SharedSpectrum2 + intraFreqCAG-CellList-r16 SEQUENCE (SIZE (1..maxPLMN)) OF IntraFreqCAG-CellListPerPLMN-r16 OPTIONAL -- Need R + ]], + [[ + intraFreqNeighHSDN-CellList-r17 IntraFreqNeighHSDN-CellList-r17 OPTIONAL, -- Need R + intraFreqNeighCellList-v1710 IntraFreqNeighCellList-v1710 OPTIONAL -- Need R + ]], + [[ + channelAccessMode2-r17 ENUMERATED {enabled} OPTIONAL -- Need R + ]] +} + +IntraFreqNeighCellList ::= SEQUENCE (SIZE (1..maxCellIntra)) OF IntraFreqNeighCellInfo + +IntraFreqNeighCellList-v1610 ::= SEQUENCE (SIZE (1..maxCellIntra)) OF IntraFreqNeighCellInfo-v1610 + +IntraFreqNeighCellList-v1710 ::= SEQUENCE (SIZE (1..maxCellIntra)) OF IntraFreqNeighCellInfo-v1710 + +IntraFreqNeighCellInfo ::= SEQUENCE { + physCellId PhysCellId, + q-OffsetCell Q-OffsetRange, + q-RxLevMinOffsetCell INTEGER (1..8) OPTIONAL, -- Need R + q-RxLevMinOffsetCellSUL INTEGER (1..8) OPTIONAL, -- Need R + q-QualMinOffsetCell INTEGER (1..8) OPTIONAL, -- Need R + ... +} + +IntraFreqNeighCellInfo-v1610 ::= SEQUENCE { + ssb-PositionQCL-r16 SSB-PositionQCL-Relation-r16 OPTIONAL -- Cond SharedSpectrum2 +} + +IntraFreqNeighCellInfo-v1710 ::= SEQUENCE { + ssb-PositionQCL-r17 SSB-PositionQCL-Relation-r17 OPTIONAL -- Cond SharedSpectrum2 +} + +IntraFreqExcludedCellList ::= SEQUENCE (SIZE (1..maxCellExcluded)) OF PCI-Range + +IntraFreqAllowedCellList-r16 ::= SEQUENCE (SIZE (1..maxCellAllowed)) OF PCI-Range + +``` + +``` + +IntraFreqCAG-CellListPerPLMN-r16 ::= SEQUENCE { + plmn-IdentityIndex-r16 INTEGER (1..maxPLMN), + cag-CellList-r16 SEQUENCE (SIZE (1..maxCAG-Cell-r16)) OF PCI-Range +} + +IntraFreqNeighHSDN-CellList-r17 ::= SEQUENCE (SIZE (1..maxCellIntra)) OF PCI-Range + +-- TAG-SIB3-STOP +-- ASN1STOP + +``` + +| SIB3 field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| channelAccessMode2
If present, this field indicates that intra-frequency neighbor cells apply channel access mode procedures for operation with shared spectrum channel access in accordance with TS 37.213 [48], clause 4.4 for FR2-2. If absent, the intra-frequency neighbor cells do not apply any channel access procedure. | +| intraFreqAllowedCellList
List of allow-listed intra-frequency neighbouring cells, see TS 38.304 [20], clause 5.2.4. | +| intraFreqCAG-CellList
List of intra-frequency neighbouring CAG cells (as defined in TS 38.304 [20]) per PLMN. | +| intraFreqExcludedCellList
List of exclude-listed intra-frequency neighbouring cells. | +| intraFreqNeighCellList
List of intra-frequency neighbouring cells with specific cell re-selection parameters. If intraFreqNeighCellList-v1610 is present, it shall contain the same number of entries, listed in the same order as in intraFreqNeighCellList (without suffix). | +| intraFreqNeighHSDN-CellList
List of intra-frequency neighbouring HSDN cells as specified in TS 38.304 [20]. | +| q-OffsetCell
Parameter "Qoffset s,n " in TS 38.304 [20]. | +| q-QualMinOffsetCell
Parameter "Qqualminoffsetcell" in TS 38.304 [20]. Actual value $Q_{qualminoffsetcell} = \text{field value [dB]}$ . | +| q-RxLevMinOffsetCell
Parameter "Qrxlevminoffsetcell" in TS 38.304 [20]. Actual value $Q_{rxlevminoffsetcell} = \text{field value} * 2 \text{ [dB]}$ . | +| q-RxLevMinOffsetCellSUL
Parameter "QrxlevminoffsetcellSUL" in TS 38.304 [20]. Actual value $Q_{rxlevminoffsetcellSUL} = \text{field value} * 2 \text{ [dB]}$ . | +| ssb-PositionQCL
Indicates the QCL relation between SS/PBCH blocks for a specific intra-frequency neighbor cell as specified in TS 38.213 [13], clause 4.1. If provided, the cell specific value overwrites the value signalled by ssb-PositionQCL-Common in SIB2 for the indicated cell. | + +| Conditional Presence | Explanation | +|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SharedSpectrum2 | The field is optional present, Need R, if this intra-frequency or neighbor cell operates with shared spectrum channel access. Otherwise, it is absent, Need R. | + +#### SIB4 + +SIB4 contains information relevant for inter-frequency cell re-selection (i.e. information about other NR frequencies and inter-frequency neighbouring cells relevant for cell re-selection), which can also be used for NR idle/inactive measurements. The IE includes cell re-selection parameters common for a frequency as well as cell specific re-selection parameters. + +#### SIB4 information element + +``` +-- ASN1START +-- TAG-SIB4-START + +SIB4 ::= SEQUENCE { + interFreqCarrierFreqList + lateNonCriticalExtension OCTET STRING OPTIONAL, + ..., + [[ + interFreqCarrierFreqList-v1610 InterFreqCarrierFreqList-v1610 OPTIONAL -- Need R + ]], + [[ + interFreqCarrierFreqList-v1700 InterFreqCarrierFreqList-v1700 OPTIONAL -- Need R + ]], + [[ + interFreqCarrierFreqList-v1720 InterFreqCarrierFreqList-v1720 OPTIONAL -- Need R + ]], + [[ + interFreqCarrierFreqList-v1730 InterFreqCarrierFreqList-v1730 OPTIONAL -- Need R + ]], + [[ + interFreqCarrierFreqList-v1760 InterFreqCarrierFreqList-v1760 OPTIONAL -- Need R + ]], + [[ + interFreqCarrierFreqList-v1800 InterFreqCarrierFreqList-v1800 OPTIONAL -- Need R + ]] +} + +InterFreqCarrierFreqList ::= SEQUENCE (SIZE (1..maxFreq)) OF InterFreqCarrierFreqInfo +InterFreqCarrierFreqList-v1610 ::= SEQUENCE (SIZE (1..maxFreq)) OF InterFreqCarrierFreqInfo-v1610 +InterFreqCarrierFreqList-v1700 ::= SEQUENCE (SIZE (1..maxFreq)) OF InterFreqCarrierFreqInfo-v1700 +InterFreqCarrierFreqList-v1720 ::= SEQUENCE (SIZE (1..maxFreq)) OF InterFreqCarrierFreqInfo-v1720 +InterFreqCarrierFreqList-v1730 ::= SEQUENCE (SIZE (1..maxFreq)) OF InterFreqCarrierFreqInfo-v1730 +InterFreqCarrierFreqList-v1760 ::= SEQUENCE (SIZE (1..maxFreq)) OF InterFreqCarrierFreqInfo-v1760 +InterFreqCarrierFreqList-v1800 ::= SEQUENCE (SIZE (1..maxFreq)) OF InterFreqCarrierFreqInfo-v1800 +``` + +``` + +InterFreqCarrierFreqInfo ::= SEQUENCE { + dl-CarrierFreq ARFCN-ValueNR, + frequencyBandList MultiFrequencyBandListNR-SIB OPTIONAL, -- Cond Mandatory + frequencyBandListSUL MultiFrequencyBandListNR-SIB OPTIONAL, -- Need R + nrofSS-BlocksToAverage INTEGER (2..maxNrofSS-BlocksToAverage) OPTIONAL, -- Need S + absThreshSS-BlocksConsolidation ThresholdNR OPTIONAL, -- Need S + smtc SSB-MTC OPTIONAL, -- Need S + ssbSubcarrierSpacing SubcarrierSpacing, + ssb-ToMeasure SSB-ToMeasure OPTIONAL, -- Need S + deriveSSB-IndexFromCell BOOLEAN, + ss-RSSI-Measurement SS-RSSI-Measurement OPTIONAL, -- Need R + q-RxLevMin Q-RxLevMin, + q-RxLevMinSUL Q-RxLevMin OPTIONAL, -- Need R + q-QualMin Q-QualMin OPTIONAL, -- Need S + p-Max P-Max OPTIONAL, -- Need S + t-ReselectionNR T-Reselection, + t-ReselectionNR-SF SpeedStateScaleFactors OPTIONAL, -- Need S + threshX-HighP ReselectionThreshold, + threshX-LowP ReselectionThreshold, + threshX-Q SEQUENCE { + threshX-HighQ ReselectionThresholdQ, + threshX-LowQ ReselectionThresholdQ + } OPTIONAL, -- Cond RSRQ + cellReselectionPriority CellReselectionPriority OPTIONAL, -- Need R + cellReselectionSubPriority CellReselectionSubPriority OPTIONAL, -- Need R + q-OffsetFreq Q-OffsetRange DEFAULT dB0, + interFreqNeighCellList InterFreqNeighCellList OPTIONAL, -- Need R + interFreqExcludedCellList InterFreqExcludedCellList OPTIONAL, -- Need R + ..., + [[ + mobileIAB-Freq ENUMERATED {true} OPTIONAL -- Need R + ]] +} + +InterFreqCarrierFreqInfo-v1610 ::= SEQUENCE { + interFreqNeighCellList-v1610 InterFreqNeighCellList-v1610 OPTIONAL, -- Need R + smtc2-LP-r16 SSB-MTC2-LP-r16 OPTIONAL, -- Need R + interFreqAllowedCellList-r16 InterFreqAllowedCellList-r16 OPTIONAL, -- Cond SharedSpectrum2 + ssb-PositionQCL-Common-r16 SSB-PositionQCL-Relation-r16 OPTIONAL, -- Cond SharedSpectrum + interFreqCAG-CellList-r16 SEQUENCE (SIZE (1..maxPLMN)) OF InterFreqCAG-CellListPerPLMN-r16 OPTIONAL -- Need R +} + +InterFreqCarrierFreqInfo-v1700 ::= SEQUENCE { + interFreqNeighHSDN-CellList-r17 InterFreqNeighHSDN-CellList-r17 OPTIONAL, -- Need R + highSpeedMeasInterFreq-r17 ENUMERATED {true} OPTIONAL, -- Need R + redCapAccessAllowed-r17 ENUMERATED {true} OPTIONAL, -- Need R + ssb-PositionQCL-Common-r17 SSB-PositionQCL-Relation-r17 OPTIONAL, -- Cond SharedSpectrum + interFreqNeighCellList-v1710 InterFreqNeighCellList-v1710 OPTIONAL, -- Cond SharedSpectrum2 +} + +``` + +``` + +InterFreqCarrierFreqInfo-v1720 ::= SEQUENCE { + smtc4List-r17 SSB-MTC4List-r17 +} OPTIONAL -- Need R + +InterFreqCarrierFreqInfo-v1730 ::= SEQUENCE { + channelAccessMode2-r17 ENUMERATED {enabled} +} OPTIONAL -- Need R + +InterFreqCarrierFreqInfo-v1760 ::= SEQUENCE { + frequencyBandList-v1760 MultiFrequencyBandListNR-SIB-v1760 + frequencyBandListSUL-v1760 MultiFrequencyBandListNR-SIB-v1760 +} OPTIONAL, -- Need R + OPTIONAL -- Need R + +InterFreqCarrierFreqInfo-v1800 ::= SEQUENCE { + frequencyBandListAerial-r18 MultiFrequencyBandListNR-Aerial-SIB-r18 + mobileIAB-CellList-r18 PCI-Range + eRedCapAccessAllowed-r18 ENUMERATED {true} + tn-AreaIdList-r18 SEQUENCE (SIZE (1..maxTN-AreaInfo-r18)) OF TN-AreaId-r18 +} OPTIONAL, -- Need S + OPTIONAL, -- Need R + OPTIONAL, -- Need R + OPTIONAL -- Need R + +InterFreqNeighHSDN-CellList-r17 ::= SEQUENCE (SIZE (1..maxCellInter)) OF PCI-Range + +InterFreqNeighCellList ::= SEQUENCE (SIZE (1..maxCellInter)) OF InterFreqNeighCellInfo + +InterFreqNeighCellList-v1610 ::= SEQUENCE (SIZE (1..maxCellInter)) OF InterFreqNeighCellInfo-v1610 + +InterFreqNeighCellList-v1710 ::= SEQUENCE (SIZE (1..maxCellInter)) OF InterFreqNeighCellInfo-v1710 + +InterFreqNeighCellInfo ::= SEQUENCE { + physCellId PhysCellId, + q-OffsetCell Q-OffsetRange, + q-RxLevMinOffsetCell INTEGER (1..8) + q-RxLevMinOffsetCellSUL INTEGER (1..8) + q-QualMinOffsetCell INTEGER (1..8) + ... +} OPTIONAL, -- Need R + OPTIONAL, -- Need R + OPTIONAL, -- Need R + +InterFreqNeighCellInfo-v1610 ::= SEQUENCE { + ssb-PositionQCL-r16 SSB-PositionQCL-Relation-r16 +} OPTIONAL -- Cond SharedSpectrum2 + +InterFreqNeighCellInfo-v1710 ::= SEQUENCE { + ssb-PositionQCL-r17 SSB-PositionQCL-Relation-r17 +} OPTIONAL -- Cond SharedSpectrum2 + +InterFreqExcludedCellList ::= SEQUENCE (SIZE (1..maxCellExcluded)) OF PCI-Range + +InterFreqAllowedCellList-r16 ::= SEQUENCE (SIZE (1..maxCellAllowed)) OF PCI-Range + +InterFreqCAG-CellListPerPLMN-r16 ::= SEQUENCE { + plmn-IdentityIndex-r16 INTEGER (1..maxPLMN), +} + +``` + +``` +cag-CellList-r16 SEQUENCE (SIZE (1..maxCAG-Cell-r16)) OF PCI-Range +} + +-- TAG-SIB4-STOP +-- ASN1STOP +``` + +| SIB4 field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| absThreshSS-BlocksConsolidation
Threshold for consolidation of L1 measurements per RS index. If the field is absent, the UE uses the measurement quantity as specified in TS 38.304 [20]. | +| channelAccessMode2
If present, this field indicates that the neighbor cells on the inter-frequency apply channel access mode procedures for operation with shared spectrum channel access in accordance with TS 37.213 [48], clause 4.4 for FR2-2. If absent, the neighbor cells on the inter-frequency do not apply any channel access procedure. | +| deriveSSB-IndexFromCell
This field indicates whether the UE may use the timing of any detected cell on that frequency to derive the SSB index of all neighbour cells on that frequency. If this field is set to true , the UE assumes SFN and frame boundary alignment across cells on the neighbor frequency as specified in TS 38.133 [14]. | +| dl-CarrierFreq
This field indicates center frequency of the SS block of the neighbour cells, where the frequency corresponds to a GSCN value as specified in TS 38.101-1 [15] or TS 38.101-5 [75]. | +| eRedCapAccessAllowed
Indicates whether eRedCap UEs are allowed to access cells on the frequency. | +| frequencyBandList
Indicates the list of frequency bands for which the NR cell reselection parameters apply. | +| frequencyBandListAerial
Indicates the list of frequency bands for aerial operation for which the NR cell reselection parameters apply. The UE behaviour in case the field is absent is described in clause 5.2.2.4.5. | +| highSpeedMeasInterFreq
If the field is set to true and UE supports high speed inter-frequency IDLE/INACTIVE measurements, the UE shall apply the enhanced inter-frequency RRM requirements on the inter-frequency carrier to support high speed up to 500 km/h in RRC_IDLE/RRC_INACTIVE as specified in TS 38.133 [14]. | +| interFreqAllowedCellList
List of allow-listed inter-frequency neighbouring cells, see TS 38.304 [20], clause 5.2.4. | +| interFreqCAG-CellList
List of inter-frequency neighbouring CAG cells (as defined in TS 38.304 [20] per PLMN). | +| interFreqCarrierFreqList
List of neighbouring carrier frequencies and frequency specific cell re-selection information. If interFreqCarrierFreqList-v1610 , interFreqCarrierFreqList-v1700 , interFreqCarrierFreqList-v1720 , interFreqCarrierFreqList-v1730 , interFreqCarrierFreqList-v1760 or InterFreqCarrierFreqInfo-v1800 are present, they shall contain the same number of entries, listed in the same order as in interFreqCarrierFreqList (without suffix). | +| interFreqExcludedCellList
List of exclude-listed inter-frequency neighbouring cells. | +| interFreqNeighCellList
List of inter-frequency neighbouring cells with specific cell re-selection parameters. If interFreqNeighCellList-v1610 is present, it shall contain the same number of entries, listed in the same order as in interFreqNeighCellList (without suffix). | +| interFreqNeighHSDN-CellList
List of inter-frequency neighbouring HSDN cells as specified in TS 38.304 [20]. | +| mobileIAB-CellList
Contains a PCI range on which mobile IAB cells may be deployed. | +| mobileIAB-Freq
If present, it indicates that a mobile IAB node may be deployed on the inter-frequency carrier. | +| nrofSS-BlocksToAverage
Number of SS blocks to average for cell measurement derivation. If the field is absent, the UE uses the measurement quantity as specified in TS 38.304 [20]. | + +| SIB4 field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| p-Max
Value in dBm applicable for the neighbouring NR cells on this carrier frequency. If absent the UE applies the maximum power according to TS 38.101-1 [15] in case of an FR1 cell, TS 38.101-2 [39] in case of an FR2 cell or TS 38.101-5 [75] in case of an NTN cell. In this release of the specification, if p-Max is present on a carrier frequency in FR2, the UE shall ignore the field and applies the maximum power according to TS 38.101-2 [39]. This field is ignored by IAB-MT. The IAB-MT applies output power and emissions requirements, as specified in TS 38.174 [63]. | +| q-OffsetCell
Parameter "Offset s,n " in TS 38.304 [20]. | +| q-OffsetFreq
Parameter "Offset frequency " in TS 38.304 [20]. | +| q-QualMin
Parameter "Q qualmin " in TS 38.304 [20]. If the field is absent, the UE applies the (default) value of negative infinity for Q qualmin . | +| q-QualMinOffsetCell
Parameter "Q qualminoffsetcell " in TS 38.304 [20]. Actual value Q qualminoffsetcell = field value [dB]. | +| q-RxLevMin
Parameter "Q rxlevmin " in TS 38.304 [20]. | +| q-RxLevMinOffsetCell
Parameter "Q rxlevminoffsetcell " in TS 38.304 [20]. Actual value Q rxlevminoffsetcell = field value * 2 [dB]. | +| q-RxLevMinOffsetCellSUL
Parameter "Q rxlevminoffsetcellsul " in TS 38.304 [20]. Actual value Q rxlevminoffsetcellsul = field value * 2 [dB]. | +| q-RxLevMinSUL
Parameter "Q rxlevmin " in TS 38.304 [20]. | +| redCapAccessAllowed
Indicates whether RedCap UEs are allowed to access cells on the frequency. | +| smtc
Measurement timing configuration for inter-frequency measurement. If this field is absent, the UE assumes that SSB periodicity is 5 ms in this frequency. If the field is broadcast by an NTN cell, the offset (derived from parameter periodicityAndOffset ) is based on the assumption that the gNB-UE propagation delay difference between the serving cell and neighbour cells equals to 0 ms, and UE can adjust the actual offset based on the actual propagation delay difference. | +| smtc2-LP
Measurement timing configuration for inter-frequency neighbour cells with a Long Periodicity (LP) indicated by periodicity in smtc2-LP . The timing offset and duration are equal to the offset and duration indicated in smtc in InterFreqCarrierFreqInfo . The periodicity in smtc2-LP can only be set to a value strictly larger than the periodicity in smtc in InterFreqCarrierFreqInfo (e.g. if smtc indicates sf20 the Long Periodicity can only be set to sf40, sf80 or sf160, if smtc indicates sf160, smtc2-LP cannot be configured). The pci-List , if present, includes the physical cell identities of the inter-frequency neighbour cells with Long Periodicity. If smtc2-LP is absent, the UE assumes that there are no inter-frequency neighbour cells with a Long Periodicity. | +| smtc4list
Measurement timing configuration list for NTN deployments, see clause 5.5.2.10. The offset of each SSB-MTC4 in smtc4list is based on the assumption that the gNB-UE propagation delay difference between the serving cell and neighbour cells equals to 0 ms, and UE can adjust the actual offset based on the actual propagation delay difference. For a UE that supports less SMTCs than what is included in this list, it is up to the UE to select which SMTCs to consider. | +| ssb-PositionQCL
Indicates the QCL relation between SS/PBCH blocks for a specific neighbor cell as specified in TS 38.213 [13], clause 4.1. If provided, the cell specific value overwrites the common value signalled by ssb-PositionQCL-Common in SIB4 for the indicated cell. | +| ssb-PositionQCL-Common
Indicates the QCL relation between SS/PBCH blocks for inter-frequency neighbor cells as specified in TS 38.213 [13], clause 4.1. | + +| SIB4 field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ssb-ToMeasure
The set of SS blocks to be measured within the SMTC measurement duration (see TS 38.215 [9]). When the field is absent the UE measures on all SS-blocks. | +| ssbSubcarrierSpacing
Subcarrier spacing of SSB.
Only the following values are applicable depending on the used frequency:
FR1: 15 or 30 kHz
FR2-1: 120 or 240 kHz
FR2-2: 120, 480, or 960 kHz | +| threshX-HighP
Parameter "Thresh X, HighP " in TS 38.304 [20]. | +| threshX-HighQ
Parameter "Thresh X, HighQ " in TS 38.304 [20]. | +| threshX-LowP
Parameter "Thresh X, LowP " in TS 38.304 [20]. | +| threshX-LowQ
Parameter "Thresh X, LowQ " in TS 38.304 [20]. | +| t-ReselectionNR
Parameter "Treselection NR " in TS 38.304 [20]. | +| t-ReselectionNR-SF
Parameter "Speed dependent ScalingFactor for Treselection NR " in TS 38.304 [20]. If the field is absent, the UE behaviour is specified in TS 38.304 [20]. | + +| Conditional Presence | Explanation | +|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Mandatory | The field is mandatory present in SIB4. | +| RSRQ | The field is mandatory present if threshServingLowQ is present in SIB2 ; otherwise it is absent. | +| SharedSpectrum | This field is mandatory present if this inter-frequency operates with shared spectrum channel access. Otherwise, it is absent, Need R. | +| SharedSpectrum2 | The field is optional present, Need R, if this inter-frequency or neighbor cell operates with shared spectrum channel access. Otherwise, it is absent, Need R. | + +##### — SIB5 + +*SIB5* contains information relevant only for inter-RAT cell re-selection i.e. information about E-UTRA frequencies and E-UTRAs neighbouring cells relevant for cell re-selection. The IE includes cell re-selection parameters common for a frequency. + +#### **SIB5 information element** + +``` +-- ASN1START +-- TAG-SIB5-START + +SIB5 ::= SEQUENCE { + carrierFreqListEUTRA CarrierFreqListEUTRA OPTIONAL, -- Need R +``` + +``` + +t-ReselectionEUTRA T-Reselection, +t-ReselectionEUTRA-SF SpeedStateScaleFactors OPTIONAL, -- Need S +lateNonCriticalExtension OCTET STRING OPTIONAL, +... +[[ +carrierFreqListEUTRA-v1610 CarrierFreqListEUTRA-v1610 OPTIONAL -- Need R +]], +[[ +carrierFreqListEUTRA-v1700 CarrierFreqListEUTRA-v1700 OPTIONAL, -- Need R +idleModeMeasVoiceFallback-r17 ENUMERATED{true} OPTIONAL -- Need R +]], +[[ +carrierFreqListEUTRA-v1800 CarrierFreqListEUTRA-v1800 OPTIONAL -- Need R +]] +} + +CarrierFreqListEUTRA ::= SEQUENCE (SIZE (1..maxEUTRA-Carrier)) OF CarrierFreqEUTRA + +CarrierFreqListEUTRA-v1610 ::= SEQUENCE (SIZE (1..maxEUTRA-Carrier)) OF CarrierFreqEUTRA-v1610 + +CarrierFreqListEUTRA-v1700 ::= SEQUENCE (SIZE (1..maxEUTRA-Carrier)) OF CarrierFreqEUTRA-v1700 + +CarrierFreqListEUTRA-v1800 ::= SEQUENCE (SIZE (1..maxEUTRA-Carrier)) OF CarrierFreqEUTRA-v1800 + +CarrierFreqEUTRA ::= SEQUENCE { + carrierFreq ARFCN-ValueEUTRA, + eutra-multiBandInfoList EUTRA-MultiBandInfoList OPTIONAL, -- Need R + eutra-FreqNeighCellList EUTRA-FreqNeighCellList OPTIONAL, -- Need R + eutra-ExcludedCellList EUTRA-FreqExcludedCellList OPTIONAL, -- Need R + allowedMeasBandwidth EUTRA-AllowedMeasBandwidth, + presenceAntennaPort1 EUTRA-PresenceAntennaPort1, + cellReselectionPriority CellReselectionPriority OPTIONAL, -- Need R + cellReselectionSubPriority CellReselectionSubPriority OPTIONAL, -- Need R + threshX-High ReselectionThreshold, + threshX-Low ReselectionThreshold, + q-RxLevMin INTEGER (-70..-22), + q-QualMin INTEGER (-34..-3), + p-MaxEUTRA INTEGER (-30..33), + threshX-Q SEQUENCE { + threshX-HighQ ReselectionThresholdQ, + threshX-LowQ ReselectionThresholdQ + } +} +OPTIONAL -- Cond RSQ + +CarrierFreqEUTRA-v1610 ::= SEQUENCE { + highSpeedEUTRACarrier-r16 ENUMERATED {true} OPTIONAL -- Need R +} + +CarrierFreqEUTRA-v1700 ::= SEQUENCE { + eutra-FreqNeighHSDN-CellList-r17 EUTRA-FreqNeighHSDN-CellList-r17 OPTIONAL -- Need R +} + +``` + +``` +CarrierFreqEUTRA-v1800 ::= SEQUENCE { + eutra-MultiBandInfoListAerial-r18 EUTRA-MultiBandInfoListAerial-r18 OPTIONAL, -- Need R + tn-AreaIdList-r18 SEQUENCE (SIZE (1..maxTN-AreaInfo-r18)) OF TN-AreaId-r18 OPTIONAL -- Need R +} + +EUTRA-FreqNeighHSDN-CellList-r17 ::= SEQUENCE (SIZE (1..maxCellEUTRA)) OF EUTRA-PhysCellIdRange + +EUTRA-FreqExcludedCellList ::= SEQUENCE (SIZE (1..maxEUTRA-CellExcluded)) OF EUTRA-PhysCellIdRange + +EUTRA-FreqNeighCellList ::= SEQUENCE (SIZE (1..maxCellEUTRA)) OF EUTRA-FreqNeighCellInfo + +EUTRA-FreqNeighCellInfo ::= SEQUENCE { + physCellId EUTRA-PhysCellId, + dummy EUTRA-Q-OffsetRange, + q-RxLevMinOffsetCell INTEGER (1..8) OPTIONAL, -- Need R + q-QualMinOffsetCell INTEGER (1..8) OPTIONAL -- Need R +} + +-- TAG-SIB5-STOP +-- ASN1STOP +``` + +| SIB5 field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| carrierFreqListEUTRA
List of carrier frequencies of E-UTRA. If the carrierFreqListEUTRA-v1610/ carrierFreqListEUTRA-v1700/ carrierFreqListEUTRA-v1800 is present, it shall contain the same number of entries, listed in the same order as in the carrierFreqListEUTRA (without suffix). | +| dummy
This field is not used in the specification. If received it shall be ignored by the UE. | +| eutra-ExcludedCellList
List of exclude-listed E-UTRA neighbouring cells. | +| eutra-FreqNeighHSDN-CellList
List of neighbouring EUTRA HSDN cells as specified in TS 36.304 [27]. | +| eutra-multiBandInfoList
Indicates the list of frequency bands in addition to the band represented by carrierFreq for which cell reselection parameters are common, and a list of additionalPmax and additionalSpectrumEmission values, as defined in TS 36.101 [22], table 6.2.4-1, for the frequency bands in eutra-multiBandInfoList | +| highSpeedEUTRACarrier
If the field is present, the UE shall apply the enhanced NR-EUTRA inter-RAT measurement requirements to support high speed up to 500 km/h as specified in TS 38.133 [14] to the E-UTRA carrier. | +| idleModeMeasVoiceFallback
Indicates whether E-UTRA idle/inactive measurements and reporting for EPS fallback can be used. | +| p-MaxEUTRA
The maximum allowed transmission power in dBm on the (uplink) carrier frequency, see TS 36.304 [27]. | +| q-QualMin
Parameter " Qqualmin " in TS 36.304 [27]. Actual value Qqualmin = field value [dB]. | +| q-QualMinOffsetCell
Parameter " Qqualminoffsetcell " in TS 36.304 [27]. Actual value Qqualminoffsetcell = field value [dB]. | +| q-RxLevMin
Parameter " Qrxlevmin " in TS 36.304 [27]. Actual value Qrxlevmin = field value * 2 [dBm]. | +| q-RxLevMinOffsetCell
Parameter " Qrxlevminoffsetcell " in TS 36.304 [27]. Actual value Qrxlevminoffsetcell = field value * 2 [dB]. | +| t-ReselectionEUTRA
Parameter " TreselectionEUTRA " in TS 38.304 [20]. | +| threshX-High
Parameter " ThreshX, HighP " in TS 38.304 [20]. | +| threshX-HighQ
Parameter " ThreshX, HighQ " in TS 38.304 [20]. | +| threshX-Low
Parameter " ThreshX, LowP " in TS 38.304 [20]. | +| threshX-LowQ
Parameter " ThreshX, LowQ " in TS 38.304 [20]. | +| t-ReselectionEUTRA-SF
Parameter " Speed dependent ScalingFactor for TreselectionEUTRA " in TS 38.304 [20]. If the field is absent, the UE behaviour is specified in TS 38.304 [20]. | + +| Conditional Presence | Explanation | +|----------------------|--------------------------------------------------------------------------------------------------------------------| +| RSRQ | The field is mandatory present if the threshServingLowQ is present in SIB2 ; otherwise it is absent. | + +#### — SIB6 + +*SIB6* contains an ETWS primary notification. + +#### SIB6 information element + +``` +-- ASN1START +-- TAG-SIB6-START + +SIB6 ::= SEQUENCE { + messageIdentifier BIT STRING (SIZE (16)), + serialNumber BIT STRING (SIZE (16)), + warningType OCTET STRING (SIZE (2)), + lateNonCriticalExtension OCTET STRING OPTIONAL, + ... +} + +-- TAG-SIB6-STOP +-- ASN1STOP +``` + +| SIB6 field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| messageIdentifier
Identifies the source and type of ETWS notification. | +| serialNumber
Identifies variations of an ETWS notification. | +| warningType
Identifies the warning type of the ETWS primary notification and provides information on emergency user alert and UE popup. | + +##### — SIB7 + +*SIB7* contains an ETWS secondary notification. + +#### SIB7 information element + +``` +-- ASN1START +-- TAG-SIB7-START + +SIB7 ::= SEQUENCE { + messageIdentifier BIT STRING (SIZE (16)), + serialNumber BIT STRING (SIZE (16)), + ... +} +``` + +``` + +warningMessageSegmentType ENUMERATED {notLastSegment, lastSegment}, +warningMessageSegmentNumber INTEGER (0..63), +warningMessageSegment OCTET STRING, +dataCodingScheme OCTET STRING (SIZE (1)) OPTIONAL, -- Cond Segment1 +lateNonCriticalExtension OCTET STRING OPTIONAL, +... +} + +-- TAG-SIB7-STOP +-- ASN1STOP + +``` + +#### SIB7 field descriptions + +| | | +|------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| dataCodingScheme | Identifies the alphabet/coding and the language applied variations of an ETWS notification. | +| messageIdentifier | Identifies the source and type of ETWS notification. | +| serialNumber | Identifies variations of an ETWS notification. | +| warningMessageSegment | Carries a segment of the Warning Message Contents IE. | +| warningMessageSegmentNumber | Segment number of the ETWS warning message segment contained in the SIB. A segment number of zero corresponds to the first segment, A segment number of one corresponds to the second segment, and so on. | +| warningMessageType | Indicates whether the included ETWS warning message segment is the last segment or not. | + +| Conditional Presence | Explanation | +|----------------------|----------------------------------------------------------------------------------------------| +| Segment1 | The field is mandatory present in the first segment of SIB7 , otherwise it is absent. | + +##### – SIB8 + +*SIB8* contains a CMAS notification. + +#### SIB8 information element + +``` + +-- ASN1START +-- TAG-SIB8-START + +SIB8 ::= SEQUENCE { + messageIdentifier BIT STRING (SIZE (16)), + serialNumber BIT STRING (SIZE (16)), + warningMessageSegmentType ENUMERATED {notLastSegment, lastSegment}, + warningMessageSegmentNumber INTEGER (0..63), +} + +``` + +``` + +warningMessageSegment OCTET STRING, +dataCodingScheme OCTET STRING (SIZE (1)) OPTIONAL, -- Cond Segment1 +warningAreaCoordinatesSegment OCTET STRING OPTIONAL, -- Need R +lateNonCriticalExtension OCTET STRING OPTIONAL, +... +} + +-- TAG-SIB8-STOP +-- ASN1STOP + +``` + +| SIB8 field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| dataCodingScheme
Identifies the alphabet/coding and the language applied variations of a CMAS notification. | +| messageIdentifier
Identifies the source and type of CMAS notification. | +| serialNumber
Identifies variations of a CMAS notification. | +| warningAreaCoordinatesSegment
If present, carries a segment, with one or more octets, of the geographical area where the CMAS warning message is valid as defined in [28]. The first octet of the first warningAreaCoordinatesSegment is equivalent to the first octet of Warning Area Coordinates IE defined in and encoded according to TS 23.041 [29] and so on. | +| warningMessageSegment
Carries a segment, with one or more octets, of the Warning Message Contents IE defined in TS 38.413 [42]. The first octet of the Warning Message Contents IE is equivalent to the first octet of the CB data IE defined in and encoded according to TS 23.041 [29], clause 9.4.2.2.5, and so on. | +| warningMessageSegmentNumber
Segment number of the CMAS warning message segment contained in the SIB. A segment number of zero corresponds to the first segment, one corresponds to the second segment, and so on. If warning area coordinates are provided for the warning message, then this field applies to both warning message segment and warning area coordinates segment. | +| warningMessageSegmentType
Indicates whether the included CMAS warning message segment is the last segment or not. If warning area coordinates are provided for the warning message, then this field applies to both warning message segment and warning area coordinates segment. | + +| Conditional Presence | Explanation | +|-----------------------------|----------------------------------------------------------------------------------------------| +| Segment1 | The field is mandatory present in the first segment of SIB8 , otherwise it is absent. | + +#### SIB9 + +*SIB9* contains information related to GPS time and Coordinated Universal Time (UTC). The UE may use the parameters provided in this system information block to obtain the UTC, the GPS and the local time. + +NOTE: The UE may use the time information for numerous purposes, possibly involving upper layers e.g. to assist GPS initialisation, to synchronise the UE clock. + +#### SIB9 information element + +``` + +-- ASN1START +-- TAG-SIB9-START + +SIB9 ::= SEQUENCE { + timeInfo SEQUENCE { + timeInfoUTC INTEGER (0..549755813887), + dayLightSavingTime BIT STRING (SIZE (2)) OPTIONAL, -- Need R + leapSeconds INTEGER (-127..128) OPTIONAL, -- Need R + localTimeOffset INTEGER (-63..64) OPTIONAL, -- Need R + } OPTIONAL, -- Need R + lateNonCriticalExtension OCTET STRING OPTIONAL, + ..., + [[ + referenceTimeInfo-r16 ReferenceTimeInfo-r16 OPTIONAL -- Need R + ]], + [[ + eventID-TSS-r18 INTEGER (0..63) OPTIONAL -- Need R + ]] +} + +-- TAG-SIB9-STOP +-- ASN1STOP + +``` + +#### SIB9 field descriptions + +##### **dayLightSavingTime** + +Indicates if and how daylight-saving time (DST) is applied to obtain the local time. The semantics are the same as the semantics of the *Daylight Saving Time* IE in TS 24.501 [23] and TS 24.008 [38]. The first/leftmost bit of the bit string contains the b2 of octet 3 and the second bit of the bit string contains b1 of octet 3 in the value part of the *Daylight Saving Time* IE in TS 24.008 [38]. + +###### **eventID-TSS** + +This field indicates the status of the 5G access stratum time distribution parameter Clock Quality Reporting Control Information as defined in TS 23.501 [32]. + +##### **leapSeconds** + +Number of leap seconds offset between GPS Time and UTC. UTC and GPS time are related i.e. GPS time -leapSeconds = UTC time. + +###### **localTimeOffset** + +Offset between UTC and local time in units of 15 minutes. Actual value = field value \* 15 minutes. Local time of the day is calculated as UTC time + localTimeOffset. + +###### **timeInfoUTC** + +Coordinated Universal Time corresponding to the SFN boundary at or immediately after the ending boundary of the SI-window in which SIB9 is transmitted. In an NTN cell, the indicated time is referenced at the uplink time synchronization reference point (RP), i.e., UE should take into account the propagation delay between UE and RP when determining the UTC time at the UE. The field counts the number of UTC seconds in 10 ms units since 00:00:00 on Gregorian calendar date 1 January, 1900 (midnight between Sunday, December 31, 1899 and Monday, January 1, 1900). See NOTE 1. This field is excluded when determining changes in system information, i.e. changes of *timeInfoUTC* should neither result in system information change notifications nor in a modification of *valueTag* in SIB1. + +NOTE 1: The UE may use this field together with the *leapSeconds* field to obtain GPS time as follows: GPS Time (in seconds) = timeInfoUTC (in seconds) - 2,524,953,600 (seconds) + leapSeconds, where 2,524,953,600 is the number of seconds between 00:00:00 on Gregorian calendar date 1 January, 1900 and 00:00:00 on Gregorian calendar date 6 January, 1980 (start of GPS time). + +#### – SIB10 + +*SIB10* contains the HRNNs of the NPNs listed in SIB1. + +#### *SIB10* information element + +``` +-- ASN1START +-- TAG-SIB10-START + +SIB10-r16 ::= SEQUENCE { + hrnn-List-r16 HRNN-List-r16 OPTIONAL, -- Need R + lateNonCriticalExtension OCTET STRING OPTIONAL, + ... +} + +HRNN-List-r16 ::= SEQUENCE (SIZE (1..maxNPN-r16)) OF HRNN-r16 + +HRNN-r16 ::= SEQUENCE { + hrnn-r16 OCTET STRING (SIZE(1.. maxHRNN-Len-r16)) OPTIONAL -- Need R +} + +-- TAG-SIB10-STOP +-- ASN1STOP +``` + +#### *SIB10* field descriptions + +##### ***HRNN-List*** + +The same amount of HRNN (see TS 23.003 [21]) elements as the number of NPNs in SIB 1 are included. The n-th entry of *HRNN-List* contains the human readable network name of the n-th NPN of SIB1. The *hrnn* in the corresponding entry in *HRNN-List* is absent if there is no HRNN associated with the given NPN. + +#### – SIB11 + +*SIB11* contains information related to idle/inactive measurements. + +#### *SIB11* information element + +``` +-- ASN1START +-- TAG-SIB11-START + +SIB11-r16 ::= SEQUENCE { + measIdleConfigSIB-r16 MeasIdleConfigSIB-r16 OPTIONAL, -- Need S + lateNonCriticalExtension OCTET STRING OPTIONAL, + ... +} +``` + +``` + + ... +} + +-- TAG-SIB11-STOP +-- ASN1STOP + +``` + +#### SIB11 field descriptions + +###### **measIdleConfigSIB** + +Indicates measurement configuration to be stored and used by the UE while in RRC\_IDLE or RRC\_INACTIVE. + +#### SIB12 + +SIB12 contains NR sidelink communication/discovery configuration. + +#### SIB12 information element + +``` + +-- ASN1START +-- TAG-SIB12-START + +SIB12-r16 ::= + SEQUENCE { + segmentNumber-r16 INTEGER (0..63), + segmentType-r16 ENUMERATED {notLastSegment, lastSegment}, + segmentContainer-r16 OCTET STRING + } + +SIB12-IEs-r16 ::= + SEQUENCE { + sl-ConfigCommonNR-r16 SL-ConfigCommonNR-r16, + lateNonCriticalExtension OCTET STRING OPTIONAL, + ... + [[ + sl-DRX-ConfigCommonGC-BC-r17 SL-DRX-ConfigGC-BC-r17 OPTIONAL, -- Need R + sl-DiscConfigCommon-r17 SL-DiscConfigCommon-r17 OPTIONAL, -- Need R + sl-L2U2N-Relay-r17 ENUMERATED {enabled} OPTIONAL, -- Need R + sl-NonRelayDiscovery-r17 ENUMERATED {enabled} OPTIONAL, -- Need R + sl-L3U2N-RelayDiscovery-r17 ENUMERATED {enabled} OPTIONAL, -- Need R + sl-TimersAndConstantsRemoteUE-r17 UE-TimersAndConstantsRemoteUE-r17 OPTIONAL -- Need R + ]], + [[ + sl-FreqInfoListSizeExt-v1800 SEQUENCE (SIZE (1..maxNrofFreqSL-1-r18)) OF SL-FreqConfigCommon-r16 OPTIONAL, -- Need R + sl-RLC-BearerConfigListSizeExt-v1800 SEQUENCE (SIZE (1..maxSL-LCID-r16)) OF SL-RLC-BearerConfig-r16 OPTIONAL, -- Need R + sl-SyncFreqList-r18 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF SL-Freq-Id-r16 OPTIONAL, -- Need R + sl-SyncTxMultiFreq-r18 ENUMERATED {true} OPTIONAL, -- Need R + sl-MaxTransPowerCA-r18 P-Max OPTIONAL, -- Need R + sl-DiscConfigCommon-v1800 SL-DiscConfigCommon-v1800 OPTIONAL -- Need R + ]] + } + +``` + +``` + +SL-ConfigCommonNR-r16 ::= SEQUENCE { + sl-FreqInfoList-r16 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF SL-FreqConfigCommon-r16 OPTIONAL, -- Need R + sl-UE-SelectedConfig-r16 SL-UE-SelectedConfig-r16 OPTIONAL, -- Need R + sl-NR-AnchorCarrierFreqList-r16 SL-NR-AnchorCarrierFreqList-r16 OPTIONAL, -- Need R + sl-EUTRA-AnchorCarrierFreqList-r16 SL-EUTRA-AnchorCarrierFreqList-r16 OPTIONAL, -- Need R + sl-RadioBearerConfigList-r16 SEQUENCE (SIZE (1..maxNrofSLRB-r16)) OF SL-RadioBearerConfig-r16 OPTIONAL, -- Need R + sl-RLC-BearerConfigList-r16 SEQUENCE (SIZE (1..maxSL-LCID-r16)) OF SL-RLC-BearerConfig-r16 OPTIONAL, -- Need R + sl-MeasConfigCommon-r16 SL-MeasConfigCommon-r16 OPTIONAL, -- Need R + sl-CSI-Acquisition-r16 ENUMERATED {enabled} OPTIONAL, -- Need R + sl-OffsetDFN-r16 INTEGER (1..1000) OPTIONAL, -- Need R + t400-r16 ENUMERATED {ms100, ms200, ms300, ms400, ms600, ms1000, ms1500, ms2000} OPTIONAL, -- Need R + sl-MaxNumConsecutiveDTX-r16 ENUMERATED {n1, n2, n3, n4, n6, n8, n16, n32} OPTIONAL, -- Need R + sl-SSB-PriorityNR-r16 INTEGER (1..8) OPTIONAL, -- Need R +} + +SL-NR-AnchorCarrierFreqList-r16 ::= SEQUENCE (SIZE (1..maxFreqSL-NR-r16)) OF ARFCN-ValueNR + +SL-EUTRA-AnchorCarrierFreqList-r16 ::= SEQUENCE (SIZE (1..maxFreqSL-EUTRA-r16)) OF ARFCN-ValueEUTRA + +SL-DiscConfigCommon-r17 ::= SEQUENCE { + sl-RelayUE-ConfigCommon-r17 SL-RelayUE-Config-r17, + sl-RemoteUE-ConfigCommon-r17 SL-RemoteUE-Config-r17 +} + +SL-DiscConfigCommon-v1800 ::= SEQUENCE { + sl-RelayUE-ConfigCommonU2U-r18 SL-RelayUE-ConfigU2U-r18, + sl-RemoteUE-ConfigCommonU2U-r18 SL-RemoteUE-ConfigU2U-r18 +} + +-- TAG-SIB12-STOP +-- ASN1STOP + +``` + +Editor's Note: FFS whether the old indication for R17 U2N Relay can be used for R18 U2U Relay or a new U2U Relay-specific indication is needed for gNB capability of supporting U2U Relay. + +Editor's Note: The mapping configuration (from e2e SLRB to RLC channel) is needed in pre-configuration. The existing table format is used as a baseline, subject to discussion during maintenance. + +| SIB12 field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| segmentContainer
This field includes a segment of the encoded SIB12-IEs . The size of the included segment in this container should be small enough that the SIB message size is less than or equal to the maximum size of a NR SI, i.e. 2976 bits when SIB12 is broadcast. | +| segmentNumber
This field identifies the sequence number of a segment of SIB12-IEs . A segment number of zero corresponds to the first segment, A segment number of one corresponds to the second segment, and so on. | +| segmentType
This field indicates whether the included segment is the last segment or not. | +| sl-CSI-Acquisition
This field indicates whether CSI reporting is enabled in sidelink unicast. If not set, SL CSI reporting is disabled. | +| sl-DRX-ConfigCommonGC-BC
This field indicates the sidelink DRX configuration for groupcast and broadcast communication, as specified in TS 38.321 [3]. This field, if present, also indicates the gNB is capable of sidelink DRX. | +| sl-EUTRA-AnchorCarrierFreqList
This field indicates the EUTRA anchor carrier frequency list, which can provide the NR sidelink communication configurations. | +| sl-FreqInfoList, sl-FreqInfoListSizeExt
This field indicates the NR sidelink communication/discovery configuration on some carrier frequency (ies). In this release, only one entry can be configured in sl-FreqInfoList . More entries can be configured in sl-FreqInfoListSizeExt . | +| sl-L2U2N-Relay
This field indicates the support of NR sidelink Layer-2 relay. | +| sl-L3U2N-RelayDiscovery
This field indicates the support of L3 U2N relay AS-layer capability, i.e. NR sidelink relay discovery. | +| sl-MaxNumConsecutiveDTX
This field indicates the maximum number of consecutive HARQ DTX before triggering sidelink RLF. Value n1 corresponds to 1, value n2 corresponds to 2, and so on. | +| sl-MaxTransPowerCA
The maximum total transmit power to be used by the UE across all sidelink carriers. | +| sl-MeasConfigCommon
This field indicates the measurement configurations (e.g. RSRP) for NR sidelink communication. | +| sl-NonRelayDiscovery
This field indicates the support of NR sidelink non-relay discovery. | +| sl-NR-AnchorCarrierFreqList
This field indicates the NR anchor carrier frequency list, which can provide the NR sidelink communication/discovery configurations. | +| sl-OffsetDFN
Indicates the timing offset for the UE to determine DFN timing when GNSS is used for timing reference. Value 1 corresponds to 0.001 milliseconds, value 2 corresponds to 0.002 milliseconds, and so on. | +| sl-RadioBearerConfigList
This field indicates one or multiple sidelink radio bearer configurations. | +| sl-RLC-BearerConfigList, sl-RLC-BearerConfigListSizeExt
This field indicates one or multiple sidelink RLC bearer configurations. | +| sl-SSB-PriorityNR
This field indicates the priority of NR sidelink SSB transmission and reception. | + +| SIB12 field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| segmentContainer
This field includes a segment of the encoded SIB12-IEs . The size of the included segment in this container should be small enough that the SIB message size is less than or equal to the maximum size of a NR SI, i.e. 2976 bits when SIB12 is broadcast. | +| segmentNumber
This field identifies the sequence number of a segment of SIB12-IEs . A segment number of zero corresponds to the first segment, A segment number of one corresponds to the second segment, and so on. | +| segmentType
This field indicates whether the included segment is the last segment or not. | +| sl-CSI-Acquisition
This field indicates whether CSI reporting is enabled in sidelink unicast. If not set, SL CSI reporting is disabled. | +| sl-SyncFreqList
Indicates a list of candidate carrier frequencies that can be used for the synchronisation of NR sidelink communication. For SL-Freq-Id-r16 , the value 1 corresponds to the frequency of first entry in sl-FreqInfoList broadcast in SIB12 , the value 2 corresponds to the frequency of first entry in sl-FreqInfoListSizeExt broadcast in SIB12 , the value 3 corresponds to the frequency of second entry in sl-FreqInfoListSizeExt broadcast in SIB12 and so on. | +| sl-SyncTxMultiFreq
Indicates that the UE transmits S-SSB on multiple carrier frequencies for NR sidelink communication. If this field is absent, the UE transmits S-SSB only on the synchronisation carrier frequency. | +| t400
Indicates the value for timer T400 as described in clause 7.1. Value ms100 corresponds to 100 ms, value ms200 corresponds to 200 ms and so on. | + +##### — SIB13 + +SIB13 contains configurations of V2X sidelink communication defined in TS 36.331 [10]. + +#### SIB13 information element + +``` +-- ASN1START +-- TAG-SIB13-START + +SIB13-r16 ::= SEQUENCE { + sl-V2X-ConfigCommon-r16 OCTET STRING, + dummy OCTET STRING, + tdd-Config-r16 OCTET STRING, + lateNonCriticalExtension OCTET STRING OPTIONAL, + ... +} + +-- TAG-SIB13-STOP +-- ASN1STOP +``` + +| SIB13 field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| dummy
This field is not used in the specification and the UE ignores the received value. | +| sl-V2X-ConfigCommon
This field includes the E-UTRA SystemInformationBlockType21 message as specified in TS 36.331 [10]. | +| tdd-Config
This field includes the tdd-Config in E-UTRA SystemInformationBlockType1 message as specified in TS 36.331 [10]. | + +##### — SIB14 + +SIB14 contains configurations of V2X sidelink communication defined in TS 36.331 [10], which can be used jointly with that included in *SIB13*. + +#### **SIB14 information element** + +``` +-- ASN1START +-- TAG-SIB14-START + +SIB14-r16 ::= SEQUENCE { + sl-V2X-ConfigCommonExt-r16 OCTET STRING, + lateNonCriticalExtension OCTET STRING OPTIONAL, + ... +} + +-- TAG-SIB14-STOP +-- ASN1STOP +``` + +| SIB14 field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------| +| sl-V2X-ConfigCommonExt
This field includes the E-UTRA SystemInformationBlockType26 message as specified in TS 36.331 [10]. | + +##### — SIB15 + +*SIB15* contains configurations of disaster roaming information. + +#### **SIB15 information element** + +``` +-- ASN1START +-- TAG-SIB15-START + +SIB15-r17 ::= SEQUENCE { + commonPLMNsWithDisasterCondition-r17 SEQUENCE (SIZE (1..maxPLMN)) OF PLMN-Identity OPTIONAL, -- Need R + applicableDisasterInfoList-r17 SEQUENCE (SIZE (1..maxPLMN)) OF ApplicableDisasterInfo-r17 OPTIONAL, -- Need R + lateNonCriticalExtension OCTET STRING OPTIONAL, +``` + +``` + + ... +} + +ApplicableDisasterInfo-r17 := CHOICE { + noDisasterRoaming-r17 NULL, + disasterRelatedIndication-r17 NULL, + commonPLMNs-r17 NULL, + dedicatedPLMNs-r17 SEQUENCE (SIZE (1..maxPLMN)) OF PLMN-Identity +} + +-- TAG-SIB15-STOP +-- ASN1STOP + +``` + +#### SIB15 field descriptions + +###### **commonPLMNsWithDisasterCondition** + +A list of PLMN(s) for which disaster condition applies and that disaster inbound roaming is accepted, which can be commonly applicable to the PLMNs sharing the cell. + +###### **applicableDisasterInfoList** + +A list indicating the applicable disaster roaming information for the networks indicated in *plmn-IdentityInfoList* and *npn-IdentityInfoList-r16*. The network indicates in this list one entry for each entry of *plmn-IdentityInfoList*, followed by one entry for each entry of *npn-IdentityInfoList-r16*, meaning that this list will have as many entries as the number of entries of the combination of *plmn-IdentityInfoList* and *npn-IdentityInfoList-r16*. The first entry in this list indicates the disaster roaming information applicable for the network(s) in the first entry of *plmn-IdentityInfoList/npn-IdentityInfoList-r16*, the second entry in this list indicates the disaster roaming information applicable for the network(s) in the second entry of *plmn-IdentityInfoList/npn-IdentityInfoList-r16*, and so on. Each entry in this list can either be having the value *noDisasterRoaming*, *disasterRelatedIndication*, *commonPLMNs*, or *dedicatedPLMNs*. If an entry in this list takes the value *noDisasterRoaming*, disaster inbound roaming is not allowed in this network(s). If an entry in this list takes the value *disasterRelatedIndication*, the meaning of this field for this network(s) is as specified for "disaster related indication" in TS 23.122 [74], clause 4.4.3.1.1. If an entry in this list takes the value *commonPLMNs*, the PLMN(s) with disaster conditions indicated in the field *commonPLMNsWithDisasterCondition* apply for this network(s). If an entry in this list contains the value *dedicatedPLMNs*, the listed PLMN(s) are the PLMN(s) with disaster conditions that the network(s) corresponding to this entry accepts disaster inbound roamers from. For SNPNS, the network indicates the value *noDisasterRoaming*. + +#### SIB16 + +SIB16 contains configurations of slice-based cell reselection information. + +#### SIB16 information element + +``` + +-- ASN1START +-- TAG-SIB16-START + +SIB16-r17 := SEQUENCE { + freqPriorityListSlicing-r17 FreqPriorityListSlicing-r17 OPTIONAL, -- Need R + lateNonCriticalExtension OCTET STRING OPTIONAL, + ... +} + +-- TAG-SIB16-STOP +-- ASN1STOP + +``` + +#### | | |---------------------------------| | SIB16 field descriptions | |---------------------------------| + +###### | | |--------------------------------| | freqPriorityListSlicing | |--------------------------------| + +| | +|---------------------------------------------------------------| +| This field indicates cell reselection priorities for slicing. | +|---------------------------------------------------------------| + +#### SIB17 + +SIB17 contains configurations of TRS resources for idle/inactive UEs. + +#### SIB17 information element + +``` +-- ASN1START +-- TAG-SIB17-START + +SIB17-r17 ::= + SEQUENCE { + segmentNumber-r17 INTEGER (0..63), + segmentType-r17 ENUMERATED {notLastSegment, lastSegment}, + segmentContainer-r17 OCTET STRING + } + +SIB17-IEs-r17 ::= + SEQUENCE { + trs-ResourceSetConfig-r17 SEQUENCE (SIZE (1..maxNrofTRS-ResourceSets-r17)) OF TRS-ResourceSet-r17, + validityDuration-r17 ENUMERATED {t1, t2, t4, t8, t16, t32, t64, t128, t256, t512, infinity, spare5, spare4, spare3, spare2, + spare1} + lateNonCriticalExtension OCTET STRING + ... + } + +TRS-ResourceSet-r17 ::= + SEQUENCE { + powerControlOffsetSS-r17 ENUMERATED {db-3, db0, db3, db6}, + scramblingID-Info-r17 CHOICE { + scramblingIDforCommon-r17 ScramblingId, + scramblingIDperResourceListWith2-r17 SEQUENCE (SIZE (2)) OF ScramblingId, + scramblingIDperResourceListWith4-r17 SEQUENCE (SIZE (4)) OF ScramblingId, + ... + }, + firstOFDMSymbolInTimeDomain-r17 INTEGER (0..9), + startingRB-r17 INTEGER (0..maxNrofPhysicalResourceBlocks-1), + nrofRBs-r17 INTEGER (24..maxNrofPhysicalResourceBlocksPlus1), + ssb-Index-r17 SSB-Index, + periodicityAndOffset-r17 CHOICE { + slots10 INTEGER (0..9), + slots20 INTEGER (0..19), + slots40 INTEGER (0..39), + slots80 INTEGER (0..79) + }, + frequencyDomainAllocation-r17 BIT STRING (SIZE (4)), + } +-- ASN1END +``` + +``` + + indBitID-r17 INTEGER (0..5), + nrofResources-r17 ENUMERATED {n2, n4} +} + +-- TAG-SIB17-STOP +-- ASN1STOP + +``` + +#### **SIB17 field descriptions** + +###### ***segmentContainer*** + +This field includes a segment of the encoded *SIB17-IEs*. The size of the included segment in this container should be small enough that the SIB message size is less than or equal to the maximum size of a NR SI, i.e. 2976 bits when *SIB17* is broadcast. + +###### ***segmentNumber*** + +This field identifies the sequence number of a segment of *SIB17-IEs*. A segment number of zero corresponds to the first segment, a segment number of one corresponds to the second segment, and so on. + +###### ***segmentType*** + +This field indicates whether the included segment is the last segment or not. + +###### ***trs-ResourceSetConfig*** + +RS configuration of TRS occasion(s) for idle/inactive UE(s), in terms of a list of $N \geq 1$ NZP TRS resource set(s). The maximum number of TRS resource sets configured by higher layer is 64. If a TRS resource is configured, the L1 based availability indication is always enabled based on that configuration. A UE which acquired *SIB17* with a TRS configuration but did not yet receive an associated L1-based availability indication considers the configured TRS as unavailable. If SIB scheduling indicates that *SIB17* has changed, the UE considers its configured TRS(s) as unavailable until it receives the associated L1-based availability indication(s). + +###### ***validityDuration*** + +The valid time duration for L1 availability indication, time unit is one default paging cycle. When the field is absent, UE assumes a default time duration to be 2 default paging cycles. The field is only valid while the UE has a valid *SIB17*. + +| TRS-ResourceSet field descriptions | | +|------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| firstOFDMSymbolInTimeDomain | The index of the first OFDM symbol in the PRB used for TRS in a slot. The field indicates the first symbol in a slot for the first TRS resource within the slot, and the symbol for the second TRS resource in the same slot can be derived implicitly with symbol index as firstOFDMSymbolInTimeDomain+4 . | +| frequencyDomainAllocation | Indicates the offset of the first RE to RE#0 in a RB in row1. | +| indBitID | The index of the associated bit in TRS availability indication field in DCI. Each TRS resource set is configured with an ID i for the association with (i+1)-th indication bit in TRS availability indication field in DCI. | +| nrofRBs | Number of PRBs across which corresponding TRS resource spans. | +| nrofResources | The number of TRS resources for a TRS resource set. | +| periodicityAndOffset | The periodicity and slot offset (slot) for periodic TRS. It is used to determine the location of the first slot of TRS resource set. The periodicity value slots10 corresponds to 10 slots, value slots20 corresponds to 20 slots, and so on. | +| powerControlOffsetSS | Power offset (dB) of NZP CSI-RS RE to SSS RE. | +| scramblingID-Info | One or more scrambling IDs are configured for a TRS resource set. If a common scrambling ID is configured, it applies to all the TRS resources within the TRS resource set. Otherwise, each TRS resource within the TRS resource set is provided with a scrambling ID. If the number of TRS resources for the TRS resource set is 2, scramblingIDperResourceListWith2-r17 is configured, while scramblingIDperResourceListWith4-r17 is configured for the case that the number of TRS resources for the TRS resource set is 4. | +| ssb-Index | The index of reference SSB with which quasi-collocation information is provided as specified in TS 38.214 [19] clause 5.1.5. | +| startingRB | The PRB index where corresponding TRS resource starts in relation to common resource block #0 (CRB#0) on the common resource block grid. | + +#### SIB18 + +SIB18 contains Group IDs for Network selection (GINs) to support access using credentials from a Credentials Holder or to support UE onboarding. + +#### SIB18 information element + +``` +-- ASN1START +-- TAG-SIB18-START + +SIB18-r17 ::= + SEQUENCE { + gin-ElementList-r17 SEQUENCE (SIZE (1..maxGIN-r17)) OF GIN-Element-r17 OPTIONAL, -- Need R + gins-PerSNPN-List-r17 SEQUENCE (SIZE (1..maxNPN-r16)) OF GINs-PerSNPN-r17 OPTIONAL, -- Need S + lateNonCriticalExtension OCTET STRING OPTIONAL, + ... + } +} +``` + +``` + +GIN-Element-r17 ::= SEQUENCE { + plmn-Identity-r17 PLMN-Identity, + nid-List-r17 SEQUENCE (SIZE (1..maxGIN-r17)) OF NID-r16 +} + +GINs-PerSNPN-r17 ::= SEQUENCE { + supportedGINs-r17 BIT STRING (SIZE (1..maxGIN-r17)) OPTIONAL -- Need R +} +-- TAG-SIB18-STOP +-- ASN1STOP + +``` + +##### SIB18 field descriptions + +###### *gin-ElementList* + +The *gin-ElementList* contains one or more GIN elements. Each GIN element contains either one GIN, which is identified by a PLMN ID and a NID, or multiple GINs that share the same PLMN ID. The total number of GINs indicated does not exceed maxGIN-r17. The GIN index *m* is defined as $d_1+d_2+\dots+d_{(n-1)}+i$ for the GIN included in the *n*-th entry of the *gin-ElementList* and the *i*-th entry of its corresponding *GIN-Element*, where *d(k)* is the number of GIN index values used in the *k*-th *gin-ElementList* entry. + +###### *gins-PerSNPN-List* + +Indicates the supported GINs for each SNPN. The network includes the same number of entries as the number of SNPNs in *snpn-AccessInfoList* in provided in SIB1, and the *n*-th entry in this list corresponds to the *n*-th SNPN listed in *snpn-AccessInfoList* provided in SIB1. The network configures this field only if the cell broadcasts more than one SNPN in *SIB1*. If this field is absent, as in case of a single SNPN broadcasted in *SIB1*, the UE shall associate all GINs in *gin-ElementList* to that SNPN. + +##### GINs-PerSNPN field descriptions + +###### *supportedGINs* + +Indicates the GINs which are supported by the given SNPN. The first/leftmost bit corresponds to the GIN with GIN index 1, the second bit corresponds to the GIN with GIN index 2 and so on. A bit set to 1 indicates that the GIN is supported by the SNPN. If the field is not present, then the corresponding SNPN does not support any GINs. + +#### SIB19 + +*SIB19* contains satellite assistance information for NTN access. + +#### SIB19 information element + +``` + +-- ASN1START +-- TAG-SIB19-START + +SIB19-r17 ::= SEQUENCE { + ntn-Config-r17 NTN-Config-r17 OPTIONAL, -- Need R + t-Service-r17 INTEGER (0..549755813887) OPTIONAL, -- Need R + referenceLocation-r17 ReferenceLocation-r17 OPTIONAL, -- Need R + distanceThresh-r17 INTEGER (0..65525) OPTIONAL, -- Need R + ntn-NeighCellConfigList-r17 NTN-NeighCellConfigList-r17 OPTIONAL, -- Need R + lateNonCriticalExtension OCTET STRING OPTIONAL, + ... +} + +``` + +``` + +ntn-NeighCellConfigListExt-v1720 NTN-NeighCellConfigList-r17 OPTIONAL -- Need R +]], +[[ +movingReferenceLocation-r18 ReferenceLocation-r17 OPTIONAL, -- Need R +satSwitchWithReSync-r18 SatSwitchWithReSync-r18 OPTIONAL -- Need R +]] +} + +NTN-NeighCellConfigList-r17 ::= SEQUENCE (SIZE(1..maxCellNTN-r17)) OF NTN-NeighCellConfig-r17 + +NTN-NeighCellConfig-r17 ::= SEQUENCE { +ntn-Config-r17 NTN-Config-r17 OPTIONAL, -- Need R +carrierFreq-r17 ARFCN-ValueNR OPTIONAL, -- Need R +physCellId-r17 PhysCellId OPTIONAL -- Need R +} + +SatSwitchWithReSync-r18 ::= SEQUENCE { +ntn-Config-r18 NTN-Config-r17, +t-ServiceStart-r18 INTEGER (0..549755813887) OPTIONAL, -- Need R +ssb-TimeOffset-r18 INTEGER (0..159) OPTIONAL -- Need R +} + +-- TAG-SIB19-STOP +-- ASN1STOP + +``` + +| SIB19 field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| distanceThresh
Distance from the serving cell reference location and is used in location-based measurement initiation in RRC_IDLE and RRC_INACTIVE, as defined in TS 38.304 [20]. Each step represents 50m. This field is only present in an NTN cell. | +| movingReferenceLocation
Reference location of the serving cell of an NTN Earth moving system at a time reference. It is used in location-based measurement initiation in RRC_IDLE and RRC_INACTIVE, as defined in TS 38.304 [20]. The time reference of this field is indicated by epochTime in ntn-Config of the serving cell. This field is excluded when determining changes in system information, i.e., changes to movingReferenceLocation should neither result in system information change notifications nor in a modification of valueTag in SIB1. This field is only present in an NTN cell. | +| ntn-Config
Provides parameters needed for the UE to access NR via NTN access such as Ephemeris data, common TA parameters, k_offset , validity duration for UL sync information and epoch. In a TN cell, this field is only present in ntn-NeighCellConfigList and ntn-NeighCellConfigListExt . | +| ntn-NeighCellConfigList, ntn-NeighCellConfigListExt
Provides a list of NTN neighbour cells including their ntn-Config , carrier frequency and PhysCellId . This set includes all elements of ntn-NeighCellConfigList and all elements of ntn-NeighCellConfigListExt . If ntn-Config is absent for an entry in ntn-NeighCellConfigListExt , the ntn-Config provided in the entry at the same position in ntn-NeighCellConfigList applies. Network provides ntn-Config for the first entry of ntn-NeighCellConfigList . If the ntn-Config is absent for any other entry in ntn-NeighCellConfigList , the ntn-Config provided in the previous entry in ntn-NeighCellConfigList applies. | +| referenceLocation
Reference location of the serving cell provided via NTN quasi-Earth fixed system and is used in location-based measurement initiation in RRC_IDLE and RRC_INACTIVE, as defined in TS 38.304 [20]. This field is only present in an NTN cell. | +| satSwitchWithReSync
Provides parameters for the target satellite required to perform satellite switch with re-synchronization. This field is only present in an NTN cell and its presence indicates that satellite switch without PCI change is supported in the cell. | +| t-Service
Indicates the time information on when a cell provided via NTN system is going to stop serving the area it is currently covering. This field applies for both service link switches in NTN quasi-Earth fixed system and feeder link switches for both NTN quasi-Earth fixed and Earth moving system. The field indicates a time in multiples of 10 ms after 00:00:00 on Gregorian calendar date 1 January, 1900 (midnight between Sunday, December 31, 1899 and Monday, January 1, 1900). The exact stop time is between the time indicated by the value of this field minus 1 and the time indicated by the value of this field. The reference point for t-Service is the uplink time synchronization reference point of the cell. This field is only present in an NTN cell. | + +| satSwitchWithReSync field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ssb-TimeOffset
Indicates the time offset between the SSB from source and target satellite at the uplink time synchronization reference point. It is given in number of subframes. | +| t-ServiceStart
Indicates the time information on when the target satellite is going to start serving the area currently covered by the serving satellite. The field indicates a time in multiples of 10 ms after 00:00:00 on Gregorian calendar date 1 st January 1900 (midnight between Sunday, December 31, 1899, and Monday, January 1, 1900). The exact start time is between the time indicated by the value of this field minus 1 and the time indicated by the value of this field. | + +##### — SIB20 + +SIB20 contains the information required to acquire the MCCH/MTCH configuration for MBS broadcast. + +#### **SIB20 information element** + +``` +-- ASN1START +-- TAG-SIB20-START + +SIB20-r17 ::= SEQUENCE { + mcch-Config-r17 MCCH-Config-r17, + cfr-ConfigMCCH-MTCH-r17 CFR-ConfigMCCH-MTCH-r17 OPTIONAL, -- Need S + lateNonCriticalExtension OCTET STRING OPTIONAL, + ... + [[ + cfr-ConfigMCCH-MTCH-RedCap-r18 CFR-ConfigMCCH-MTCH-r17 OPTIONAL, -- Need S + mcch-ConfigRedCap-r18 MCCH-Config-r17 OPTIONAL -- Cond CFR-RedCap + ]] +} + +MCCH-Config-r17 ::= SEQUENCE { + mcch-RepetitionPeriodAndOffset-r17 MCCH-RepetitionPeriodAndOffset-r17, + mcch-WindowStartSlot-r17 INTEGER (0..79), + mcch-WindowDuration-r17 ENUMERATED {sl2, sl4, sl8, sl10, sl20, sl40,sl80, sl160} OPTIONAL, -- Need S + mcch-ModificationPeriod-r17 ENUMERATED {rf2, rf4, rf8, rf16, rf32, rf64, rf128, rf256, + rf512, rf1024, rf2048, rf4096, rf8192, rf16384, rf32768, rf65536} +} + +MCCH-RepetitionPeriodAndOffset-r17 ::= CHOICE { + rf1-r17 INTEGER (0), + rf2-r17 INTEGER (0..1), + rf4-r17 INTEGER (0..3), + rf8-r17 INTEGER (0..7), + rf16-r17 INTEGER (0..15), + rf32-r17 INTEGER (0..31), + rf64-r17 INTEGER (0..63), + rf128-r17 INTEGER (0..127), + rf256-r17 INTEGER (0..255) +} + +-- TAG-SIB20-STOP +-- ASN1STOP +``` + +| SIB20 field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| cfr-ConfigMCCH-MTCH
Common frequency resource used for MCCH and MTCH reception. If the field is absent, the CFR for broadcast has the same location and size as CORESET#0 and PDSCH configuration of MCCH is the same as PDSCH configuration provided in initialDownlinkBWP in SIB1 . | +| cfr-ConfigMCCH-MTCH-RedCap
Common frequency resource used for MCCH and MTCH reception for RedCap UEs. If the field is absent, the RedCap UE can use cfr-ConfigMCCH-MTCH if the UE supports the configured bandwidth. | +| mcch-WindowDuration
Indicates, starting from the slot indicated by mcch-WindowStartSlot , the duration in slots during which MCCH may be scheduled. Absence of this field means that MCCH is only scheduled in the slot indicated by mcch-WindowStartSlot . The network always configures mcch-WindowDuration to be shorter or equal to the length of MCCH repetition period. | +| mcch-ModificationPeriod
Defines periodically appearing boundaries, i.e. radio frames for which $SFN \bmod \text{mcch-ModificationPeriod} = 0$ . The contents of different transmissions of MCCH information can only be different if there is at least one such boundary in-between them. Value rf2 corresponds to two radio frames, value rf4 corresponds to four radio frames and so on. | +| mcch-RepetitionPeriodAndOffset
Defines the length and the offset of the MCCH repetition period. rf1 corresponds to a repetition period length of one radio frame, rf2 corresponds to a repetition period length of two radio frames and so on. The corresponding integer value indicates the offset of the repetition period in the number of radio frames. MCCH is scheduled in the MCCH transmission window starting from each radio frame for which: $SFN \bmod \text{repetition period length} = \text{offset of the repetition period}$ . | +| mcch-WindowStartSlot
Indicates the slot in which MCCH transmission window starts. | + +| Conditional presence | Explanation | +|-----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CFR-RedCap | The field is optionally present, Need R, if the configured bandwidth in cfr-ConfigMCCH-MTCH exceeds the RedCap UE capability. It is absent otherwise. | + +#### SIB21 + +*SIB21* contains the mapping between the current and/or neighbouring carrier frequencies and MBS Frequency Selection Area Identities (FSAI). + +#### **SIB21 information element** + +``` +-- ASN1START +-- TAG-SIB21-START + +SIB21-r17 ::= SEQUENCE { + mbs-FSAI-IntraFreq-r17 MBS-FSAI-List-r17 OPTIONAL, -- Need R + mbs-FSAI-InterFreqList-r17 MBS-FSAI-InterFreqList-r17 OPTIONAL, -- Need R + lateNonCriticalExtension OCTET STRING OPTIONAL, + ... +} + +MBS-FSAI-List-r17 ::= SEQUENCE (SIZE (1..maxFSAI-MBS-r17)) OF MBS-FSAI-r17 + +MBS-FSAI-InterFreqList-r17 ::= SEQUENCE (SIZE (1..maxFreq)) OF MBS-FSAI-InterFreq-r17 +``` + +``` + +MBS-FSAI-InterFreq-r17 ::= SEQUENCE { + dl-CarrierFreq-r17 ARFCN-ValueNR, + mbs-FSAI-List-r17 MBS-FSAI-List-r17 +} + +MBS-FSAI-r17 ::= OCTET STRING (SIZE (3)) + +-- TAG-SIB21-STOP +-- ASN1STOP + +``` + +#### SIB21 field descriptions + +###### ***mbs-FSAI-InterFreqList*** + +Contains a list of neighboring frequencies including additional bands, if any, that provide MBS services and the corresponding MBS FSAsIs. + +###### ***mbs-FSAI-IntraFreq*** + +Contains the list of MBS FSAsIs for the current frequency. For MBS service continuity, the UE shall use all MBS FSAsIs listed in *mbs-FSAI-IntraFreq* to derive the MBS frequencies of interest. + +#### SIB22 + +SIB22 contains ATG assistant information. + +#### SIB22 information element + +``` + +-- ASN1START +-- TAG-SIB22-START + +SIB22-r18 ::= SEQUENCE { + atg-Config-r18 ATG-Config-r18 OPTIONAL, -- Need R + hs-ATG-cellReselectionSet-r18 ENUMERATED {true} OPTIONAL, -- Need R + atg-NeighCellConfigList-r18 ATG-NeighCellConfigList-r18 OPTIONAL, -- Need R + lateNonCriticalExtension OCTET STRING OPTIONAL, + ... +} + +ATG-NeighCellConfigList-r18 ::= SEQUENCE (SIZE(1..maxCellATG-r18)) OF ATG-NeighCellConfig-r18 + +ATG-NeighCellConfig-r18 ::= SEQUENCE { + atg-gNB-Location-r18 ReferenceLocation-r17 OPTIONAL, -- Need R + heightgNB-r18 INTEGER (-16384..16383) OPTIONAL, -- Need R + carrierFreq-r18 ARFCN-ValueNR OPTIONAL, -- Need R + physCellId-r18 PhysCellId OPTIONAL, -- Need R + ... +} + +-- TAG-SIB22-STOP +-- ASN1STOP + +``` + +#### **SIB22 field descriptions** + +###### **atg-Config** + +Provides parameters needed for the UE to access ATG via NTN access such as atg gNB location information, cell Specific Koffset, TA Report indication. + +###### **atg-NeighCellConfigList** + +Provides a list of ATG neighbour cells including their *reference Location*, carrier frequency and *PhysCellId*. + +###### **hs-ATG-cellReselectionSet** + +Indicates whether the UE applies high speed inter-frequency measurements requirements for inter-frequency cell reselection in RRC\_IDLE and RRC\_INACTIVE states as specified in TS 38.133 [14]. If the field is absent UE applies only the NR cell reselection requirements as specified in TS 38.133 [14]. + +#### — SIB23 + +SIB23 contains NR sidelink Positioning configuration. + +#### **SIB23 information element** + +``` +-- ASN1START +-- TAG-SIB23-START + +SIB23-r18 ::= SEQUENCE { + sl-PosConfigCommonNR-r18 SL-ConfigCommonNR-r16, + lateNonCriticalExtension OCTET STRING OPTIONAL, + ... +} + +-- TAG-SIB23-STOP +-- ASN1STOP +``` + +#### **SIB23 field descriptions** + +###### **sl-PosConfigCommonNR** + +This field indicates the NR sidelink positioning configuration. + +#### — SIB24 + +SIB24 contains the information required to acquire the multicast MCCH/MTCH configuration for MBS multicast reception in RRC\_INACTIVE. + +#### **SIB24 information element** + +``` +-- ASN1START +-- TAG-SIB24-START +``` + +``` + +SIB24-r18 ::= SEQUENCE { + multicastMCCH-Config-r18 MCCH-Config-r17, + cfr-ConfigMCCH-MTCH-r18 CFR-ConfigMCCH-MTCH-r17 OPTIONAL, -- Need S + lateNonCriticalExtension OCTET STRING OPTIONAL, + ... +} + +-- TAG-SIB24-STOP +-- ASN1STOP + +``` + +#### SIB24 field descriptions + +###### ***cfr-ConfigMCCH-MTCH*** + +Common frequency resource used for multicast MCCH and multicast MTCH reception. If the field is absent, the CFR for multicast has the same location and size as CORESET#0 and PDSCH configuration of MCCH is the same as PDSCH configuration provided in *initialDownlinkBWP* in *SIB1*. + +###### ***multicastMCCH-Config*** + +Indicates MCCH configuration for MBS multicast reception in RRC\_INACTIVE. + +#### — SIB25 + +*SIB25* contains TN coverage information to assist neighbour cell measurements for the UEs in an NTN cell. + +#### SIB25 information element + +``` + +-- ASN1START +-- TAG-SIB25-START + +SIB25-r18 ::= SEQUENCE { + coverageAreaInfoList-r18 CoverageAreaInfoList-r18 OPTIONAL, -- Need R + lateNonCriticalExtension OCTET STRING OPTIONAL, + ... +} + +CoverageAreaInfoList-r18 ::= SEQUENCE (SIZE (1..maxTN-AreaInfo-r18)) OF CoverageAreaInfo-r18 + +CoverageAreaInfo-r18 ::= SEQUENCE { + tn-AreaId-r18 TN-AreaId-r18, + tn-ReferenceLocation-r18 ReferenceLocation-r17, + tn-DistanceRadius-r18 INTEGER (0..65536) +} + +-- TAG-SIB25-STOP +-- ASN1STOP + +``` + +| SIB25 field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| coverageAreaInfoList
Contains a list of TN coverage area's information to assist skipping TN measurements for NTN UEs in RRC_IDLE and RRC_INACTIVE, as defined in TS 38.304 [20]. | +| tn-DistanceRadius
Distance from the TN coverage area reference location. It is used for skipping TN measurements in RRC_IDLE and RRC_INACTIVE, as defined in TS 38.304 [20]. Each step represents 1m. | + +### 6.3.1a Positioning System information blocks + +#### – *PosSystemInformation-r16-IEs* + +``` +-- ASN1START +-- TAG-POSSYSTEMINFORMATION-R16-IES-START + +PosSystemInformation-r16-IEs ::= SEQUENCE { + posSIB-TypeAndInfo-r16 SEQUENCE (SIZE (1..maxSIB)) OF CHOICE { + posSib1-1-r16 SIBpos-r16, + posSib1-2-r16 SIBpos-r16, + posSib1-3-r16 SIBpos-r16, + posSib1-4-r16 SIBpos-r16, + posSib1-5-r16 SIBpos-r16, + posSib1-6-r16 SIBpos-r16, + posSib1-7-r16 SIBpos-r16, + posSib1-8-r16 SIBpos-r16, + posSib2-1-r16 SIBpos-r16, + posSib2-2-r16 SIBpos-r16, + posSib2-3-r16 SIBpos-r16, + posSib2-4-r16 SIBpos-r16, + posSib2-5-r16 SIBpos-r16, + posSib2-6-r16 SIBpos-r16, + posSib2-7-r16 SIBpos-r16, + posSib2-8-r16 SIBpos-r16, + posSib2-9-r16 SIBpos-r16, + posSib2-10-r16 SIBpos-r16, + posSib2-11-r16 SIBpos-r16, + posSib2-12-r16 SIBpos-r16, + posSib2-13-r16 SIBpos-r16, + posSib2-14-r16 SIBpos-r16, + posSib2-15-r16 SIBpos-r16, + posSib2-16-r16 SIBpos-r16, + posSib2-17-r16 SIBpos-r16, + posSib2-18-r16 SIBpos-r16, + posSib2-19-r16 SIBpos-r16, + posSib2-20-r16 SIBpos-r16, + posSib2-21-r16 SIBpos-r16, + posSib2-22-r16 SIBpos-r16, + posSib2-23-r16 SIBpos-r16, + } +} +``` + +``` + + posSib3-1-r16 SIBpos-r16, + posSib4-1-r16 SIBpos-r16, + posSib5-1-r16 SIBpos-r16, + posSib6-1-r16 SIBpos-r16, + posSib6-2-r16 SIBpos-r16, + posSib6-3-r16 SIBpos-r16, + ... / + posSib1-9-v1700 SIBpos-r16, + posSib1-10-v1700 SIBpos-r16, + posSib2-24-v1700 SIBpos-r16, + posSib2-25-v1700 SIBpos-r16, + posSib6-4-v1700 SIBpos-r16, + posSib6-5-v1700 SIBpos-r16, + posSib6-6-v1700 SIBpos-r16, + posSib2-17a-v1770 SIBpos-r16, + posSib2-18a-v1770 SIBpos-r16, + posSib2-20a-v1770 SIBpos-r16, + posSib1-11-v1800 SIBpos-r16, + posSib1-12-v1800 SIBpos-r16, + posSib2-26-v1800 SIBpos-r16, + posSib2-27-v1800 SIBpos-r16 + }, + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +-- TAG-POSSYSTEMINFORMATION-R16-IES-STOP +-- ASN1STOP + +``` + +##### — PosSI-SchedulingInfo + +``` + +-- ASN1START +-- TAG-POSSI-SCHEDULINGINFO-START + +PosSI-SchedulingInfo-r16 ::= + SEQUENCE { + posSchedulingInfoList-r16 + SEQUENCE (SIZE (1..maxSI-Message)) OF PosSchedulingInfo-r16, + posSI-RequestConfig-r16 + SI-RequestConfig OPTIONAL, -- Cond MSG-1 + posSI-RequestConfigSUL-r16 + SI-RequestConfig OPTIONAL, -- Cond SUL-MSG-1 + ... / + [[ + posSI-RequestConfigRedCap-r17 + SI-RequestConfig OPTIONAL -- Cond REDCAP-MSG-1 + ]], + [[ + posSI-RequestConfigMSG1-Repetition-r18 + SI-RequestConfigRepetition-r18 + OPTIONAL, -- Cond MSG-1 + posSI-RequestConfigSUL-MSG1-Repetition-r18 + SI-RequestConfigRepetition-r18 + OPTIONAL, -- Cond SUL-MSG-1 + posSI-RequestConfigRedCap-MSG1-Repetition-r18 + SI-RequestConfigRepetition-r18 + OPTIONAL -- Cond REDCAP-MSG-1 + ]] + } +} + +``` + +``` + +PosSchedulingInfo-r16 ::= SEQUENCE { + offsetToSI-Used-r16 ENUMERATED {true} OPTIONAL, -- Need R + posSI-Periodicity-r16 ENUMERATED {rf8, rf16, rf32, rf64, rf128, rf256, rf512}, + posSI-BroadcastStatus-r16 ENUMERATED {broadcasting, notBroadcasting}, + posSIB-MappingInfo-r16 PosSIB-MappingInfo-r16, + ... +} + +PosSIB-MappingInfo-r16 ::= SEQUENCE (SIZE (1..maxSIB)) OF PosSIB-Type-r16 + +PosSIB-Type-r16 ::= SEQUENCE { + encrypted-r16 ENUMERATED { true } OPTIONAL, -- Need R + gnss-id-r16 GNSS-ID-r16 OPTIONAL, -- Need R + sbas-id-r16 SBAS-ID-r16 OPTIONAL, -- Cond GNSS-ID-SBAS + posSibType-r16 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, posSibType3-1, posSibType4-1, + posSibType5-1, posSibType6-1, posSibType6-2, posSibType6-3, ... }, + areaScope-r16 ENUMERATED {true} OPTIONAL -- Need S +} + +GNSS-ID-r16 ::= SEQUENCE { + gnss-id-r16 ENUMERATED{gps, sbas, qzss, galileo, glonass, bds, ..., navic-v1760}, + ... +} + +SBAS-ID-r16 ::= SEQUENCE { + sbas-id-r16 ENUMERATED { waas, egnos, msas, gagan, ...}, + ... +} + +-- TAG-POSSI-SCHEDULINGINFO-STOP +-- ASN1STOP + +``` + +| PosSI-SchedulingInfo field descriptions | | +|--------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| areaScope | Indicates that a posSIB is area specific. If the field is absent, the posSIB is cell specific. | +| encrypted | The presence of this field indicates that the pos-sib-type is encrypted as specified in TS 37.355 [49]. | +| gnss-id | The presence of this field indicates that the positioning SIB type is for a specific GNSS. Indicates a specific GNSS (see also TS 37.355 [49]) | +| posSI-BroadcastStatus | Indicates if the SI message is being broadcasted or not. Change of posSI-BroadcastStatus should not result in system information change notifications in Short Message transmitted with P-RNTI over DCI (see clause 6.5). The value of the indication is valid until the end of the BCCH modification period when set to broadcasting .
If si-SchedulingInfo-v1700 is present, the network ensures that the total number of SI messages with posSI-BroadcastStatus and si-BroadcastStatus set to notBroadcasting in the concatenated list of SI messages configured by posSchedulingInfoList in posSI-SchedulingInfo and SI messages containing type2 SIB configured by schedulingInfoList2 in si-SchedulingInfo-v1700 does not exceed the limit of maxSI-Message when posSI-RequestConfig or posSI-RequestConfigRedCap or posSI-RequestConfigSUL is configured. | +| posSI-RequestConfig | Configuration of Msg1 resources that the UE uses for requesting SI-messages for which posSI-BroadcastStatus is set to notBroadcasting . | +| posSI-RequestConfigMSG1-Repetition | Configuration of Msg1 repetition resources on NUL that the UE uses for requesting SI-messages for which posSI-BroadcastStatus is set to notBroadcasting . This field is only applicable when Msg1 repetition resources can be used for requesting SI-messages. | +| posSI-RequestConfigRedCap | Configuration of Msg1 resources for initialUplinkBWP-RedCap that the (e)RedCap UE uses for requesting SI-messages for which posSI-BroadcastStatus is set to notBroadcasting . | +| posSI-RequestConfigRedCap-MSG1-Repetition | Configuration of Msg1 repetition resources for initialUplinkBWP-RedCap that the RedCap UE uses for requesting SI-messages for which posSI-BroadcastStatus is set to notBroadcasting . This field is only applicable when Msg1 repetition resources can be used for requesting SI-messages. | +| posSI-RequestConfigSUL | Configuration of Msg1 resources that the UE uses for requesting SI-messages for which posSI-BroadcastStatus is set to notBroadcasting . | +| posSI-RequestConfigSUL-MSG1-Repetition | Configuration of Msg1 repetition resources on SUL that the UE uses for requesting SI-messages for which posSI-BroadcastStatus is set to notBroadcasting . This field is only applicable when Msg1 repetition resources can be used for requesting SI-messages. | +| posSIB-MappingInfo | List of the posSIBs mapped to this SystemInformation message. | +| posSibType | The positioning SIB type is defined in TS 37.355 [49]. | +| posSI-Periodicity | Periodicity of the SI-message in radio frames, such that rf8 denotes 8 radio frames, rf16 denotes 16 radio frames, and so on. If the offsetToSI-Used is configured, the posSI-Periodicity of rf8 cannot be used. | +| offsetToSI-Used | This field, if present indicates that all the SI messages in posSchedulingInfoList are scheduled with an offset of 8 radio frames compared to SI messages in schedulingInfoList . offsetToSI-Used may be present only if the shortest configured SI message periodicity for SI messages in schedulingInfoList is 80ms. If SI offset is used, this field is present in each of the SI messages in the posSchedulingInfoList . | +| sbas-id | The presence of this field indicates that the positioning SIB type is for a specific SBAS. Indicates a specific SBAS (see also TS 37.355 [49]). | + +| Conditional presence | Explanation | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GNSS-ID-SBAS | The field is mandatory present if gnss-id is set to sbas . It is absent otherwise. | +| MSG-1 | The field is optionally present, Need R, if posSI-BroadcastStatus is set to notBroadcasting for any SI-message included in posSchedulingInfoList or if si-BroadcastStatus is set to notBroadcasting for any SI-message containing type2 SIB included in schedulingInfoList2 . It is absent otherwise. | +| SUL-MSG-1 | The field is optionally present, Need R, if supplementaryUplink is configured in ServingCellConfigCommonSIB , and if posSI-BroadcastStatus is set to notBroadcasting for any SI-message included in posSchedulingInfoList or if si-BroadcastStatus is set to notBroadcasting for any SI-message containing type2 SIB included in schedulingInfoList2 . It is absent otherwise. | +| REDCAP-MSG-1 | The field is optionally present, Need R, if initialUplinkBWP-RedCap is configured in UplinkConfigCommonSIB , and if posSI-BroadcastStatus is set to notBroadcasting for any SI-message included in posSchedulingInfoList or if si-BroadcastStatus is set to notBroadcasting for any SI-message containing type2 SIB included in schedulingInfoList2 . It is absent otherwise. | + +#### – *SIBpos* + +The IE *SIBpos* contains positioning assistance data as defined in TS 37.355 [49]. + +#### *SIBpos* information element + +``` +-- ASN1START +-- TAG-SIPOS-START + +SIBpos-r16 ::= SEQUENCE { + assistanceDataSIB-Element-r16 OCTET STRING, + lateNonCriticalExtension OCTET STRING OPTIONAL, + ... +} + +-- TAG-SIPOS-STOP +-- ASN1STOP +``` + +##### *SIBpos* field descriptions + +##### *assistanceDataSIB-Element* + +Parameter *AssistanceDataSIBElement* defined in TS 37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit. + +### 6.3.2 Radio resource control information elements + +#### – *AdditionalSpectrumEmission* + +The IE *AdditionalSpectrumEmission* is used to indicate emission requirements to be fulfilled by the UE (see TS 38.101-1 [15], clause 6.2.3/6.2.A.3, TS 38.101-2 [39], clause 6.2.3/6.2.A.3, and TS 38.101-5 [75], clause 6.2.3). If an extension is signalled using the extended value range (as defined by the IE *AdditionalSpectrumEmission-v1760*), the corresponding original field, using the value range as defined by the IE *AdditionalSpectrumEmission* (without suffix) shall be set to value 7. + +#### **AdditionalSpectrumEmission information element** + +``` + +-- ASN1START +-- TAG-ADDITIONALSPECTRUMEMISSION-START + +AdditionalSpectrumEmission ::= INTEGER (0..7) +AdditionalSpectrumEmission-v1760 ::= INTEGER (8..39) +AdditionalSpectrumEmission-r18 ::= INTEGER (0..39) + +-- TAG-ADDITIONALSPECTRUMEMISSION-STOP +-- ASN1STOP + +``` + +##### — **AdvancedReceiver-MU-MIMO** + +The IE *AdvancedReceiver-MU-MIMO* is used to provide a set of assistance information for R-ML (reduced complexity ML) receivers with enhanced inter-user interference suppression for MU-MIMO transmissions. + +#### **AdvancedReceiver-MU-MIMO information element** + +``` + +-- ASN1START +-- TAG-ADVANCEDRECEIVER-MU-MIMO-START + +AdvancedReceiver-MU-MIMO-r18 ::= SEQUENCE { + precodingAndResourceAllocation-r18 BOOLEAN OPTIONAL, -- Need M + dmrsPowerBoosting-r18 BOOLEAN OPTIONAL, -- Need M + pdsch-TimeDomainAllocation-r18 BOOLEAN OPTIONAL, -- Need M + mcs-Table-r18 ENUMERATED {qam1024, qam256, qam64} OPTIONAL, -- Need R + advReceiver-MU-MIMO-DCI-1-1-r18 ENUMERATED {enabled} OPTIONAL -- Need R +} + +-- TAG-ADVANCEDRECEIVER-MU-MIMO-STOP +-- ASN1STOP + +``` + +*Editor's note: whether the IE type BOOLEAN within AdvancedReceiver-MU-MIMO-r18 needs to be changed to ENUMERATED {true} depends on further RAN4 clarification.* + +*Editor's note: whether dmrsPowerBoosting-r18 needs to be removed depends on further RAN4 clarification.* + +| AdvancedReceiver-MU-MIMO field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| advReceiver-MU-MIMO-DCI-1-1
Configure the presence of the co-scheduled UE information filed in DCI format 1_1 (see TS 38.212 [17], clause 7.3.1.2.2). | +| dmrsPowerBoosting
If the field is set to true, the UE can assume the DMRS power boosting configurations (i.e., Number of DMRS CDM groups without data, see TS 38.214 [19], table 4.1-1) of all the co-scheduled UE(s), which has the same DM-RS sequence as the target UE.
If the field is set to false, the UE can not assume the DMRS power boosting configurations (i.e., Number of DMRS CDM groups without data, see TS 38.214 [19], table 4.1-1) of all the co-scheduled UE(s), which has the same DM-RS sequence as the target UE, is the same as the target UE. | +| mcs-Table
Indicates the MCS table with the highest modulation order among all MCS tables configured to the co-scheduled UE(s), which has the same DMRS sequence as the target UE. | +| pdsch-TimeDomainAllocation
If the field is set to true, the UE can assume the time domain resource assignment for PDSCH symbols of all the co-scheduled UE(s), which has the same DMRS sequence as the target UE, is same as the target UE.
If the field is set to false, the UE can not assume the time domain resource assignment for PDSCH symbols of all the co-scheduled UE(s), which has the same DMRS sequence as the target UE, is same as the target UE. | +| precodingAndResourceAllocation
If the field is set to true, the UE can assume 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, when the target UE and any co-scheduled UEs are in different CDM groups and with the same DMRS sequence.
If the field is set to false, the UE can not assume 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, when the target UE and any co-scheduled UEs are in different CDM groups and with the same DMRS sequence. | + +NOTE: the same DMRS sequence represents the same root DMRS sequence $r(n)$ , see TS 38.211 [16], clause 7.4.1.1.1. + +##### – Alpha + +The IE *Alpha* defines possible values of a the pathloss compensation coefficient for uplink power control. Value *alpha0* corresponds to the value 0, Value *alpha04* corresponds to the value 0.4, Value *alpha05* corresponds to the value 0.5 and so on. Value *alpha1* corresponds to value 1. See also clause 7.1 of TS 38.213 [13]. + +``` +-- ASN1START +-- TAG-ALPHA-START + +Alpha ::= ENUMERATED {alpha0, alpha04, alpha05, alpha06, alpha07, alpha08, alpha09, alpha1} + +-- TAG-ALPHA-STOP +-- ASN1STOP +``` + +##### – Altitude + +The IE *Altitude* is used to indicate altitude relative to sea level. The actual value is the field value in meters. + +##### ***Altitude information element*** + +``` +-- ASN1START +-- TAG-ALTITUDE-START + +Altitude-r18 ::= INTEGER (minAltitude-r18..maxAltitude-r18) + +-- TAG-ALTITUDE-STOP +-- ASN1STOP +``` + +##### **— *AMF-Identifier*** + +The IE *AMF-Identifier* (AMFI) comprises of an AMF Region ID, an AMF Set ID and an AMF Pointer as specified in TS 23.003 [21], clause 2.10.1. + +#### ***AMF-Identifier information element*** + +``` +-- ASN1START +-- TAG-AMF-IDENTIFIER-START + +AMF-Identifier ::= BIT STRING (SIZE (24)) + +-- TAG-AMF-IDENTIFIER-STOP +-- ASN1STOP +``` + +##### **— *ARFCN-ValueEUTRA*** + +The IE *ARFCN-ValueEUTRA* is used to indicate the ARFCN applicable for a downlink, uplink or bi-directional (TDD) E-UTRA carrier frequency, as defined in TS 36.101 [22]. + +##### ***ARFCN-ValueEUTRA information element*** + +``` +-- ASN1START +-- TAG-ARFCN-VALUEEUTRA-START + +ARFCN-ValueEUTRA ::= INTEGER (0..maxEARFCN) + +-- TAG-ARFCN-VALUEEUTRA-STOP +-- ASN1STOP +``` + +##### **— *ARFCN-ValueNR*** + +The IE *ARFCN-ValueNR* is used to indicate the ARFCN applicable for a downlink, uplink or bi-directional (TDD) NR global frequency raster, as defined in TS 38.101-1 [15], TS 38.101-2 [39] and TS 38.101-5 [75], clause 5.4.2. + +``` +-- ASN1START +``` + +``` +-- TAG-ARFCN-VALUE NR-START +ARFCN-ValueNR ::= INTEGER (0..maxNARFCN) +-- TAG-ARFCN-VALUE NR-STOP +-- ASN1STOP +``` + +##### — *ARFCN-ValueUTRA-FDD* + +The IE *ARFCN-ValueUTRA-FDD* is used to indicate the ARFCN applicable for a downlink (Nd, FDD) UTRA-FDD carrier frequency, as defined in TS 25.331 [45]. + +##### *ARFCN-ValueUTRA-FDD* information element + +``` +-- ASN1START +-- TAG-ARFCN-ValueUTRA-FDD-START +ARFCN-ValueUTRA-FDD-r16 ::= INTEGER (0..16383) +-- TAG-ARFCN-ValueUTRA-FDD-STOP +-- ASN1STOP +``` + +##### — *ATG-Config* + +The IE *ATG-Config* provides parameters needed for the UE to access NR via ATG access. + +#### *ATG-Config* information element + +``` +-- ASN1START +-- TAG-NTN-CONFIG-START +ATG-Config-r18 ::= SEQUENCE { + atg-gNB-Location-r18 ReferenceLocation-r17 OPTIONAL, -- Need R + heightgNB-r18 INTEGER (-16384..16383) OPTIONAL, -- Need R + cellSpecificKoffset-r18 INTEGER (1..3) OPTIONAL, -- Need R + ta-ReportATG-r18 ENUMERATED {enabled} OPTIONAL, -- Need R + ... +} +-- TAG-NTN-CONFIG-STOP +-- ASN1STOP +``` + +| ATG-Config field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| atg-gNB-Location
Indicates the BS location for ATG access. | +| cellSpecificKoffset
Scheduling offset used for the timing relationships that are modified for ATG. Unit in slot. | +| heightgNB
Indicates the height of the BS for ATG access. Unit in meter. | +| ta-ReportATG
When this field is included in SIB22, it indicates reporting of timing advanced is enabled during Random Access due to RRC connection establishment or RRC connection resume, and during RRC connection reestablishment. When this field is included in ServingCellConfigCommon within dedicated signalling, it indicates TA reporting is enabled during Random Access due to reconfiguration with sync (see TS 38.321 [3], clause 5.4.8). | + +##### – *AvailabilityCombinationsPerCell* + +The IE *AvailabilityCombinationsPerCell* is used to configure the *AvailabilityCombinations* applicable for a cell of the IAB DU (see TS 38.213 [13], clause 14). Note that the IE *AvailabilityCombinationsPerCellIndex* can only be configured up to 511. + +##### *AvailabilityCombinationsPerCell* information element + +``` +-- ASN1START +-- TAG-AVAILABILITYCOMBINATIONSCELL-START + +AvailabilityCombinationsPerCell-r16 ::= SEQUENCE { + availabilityCombinationsPerCellIndex-r16 AvailabilityCombinationsPerCellIndex-r16, + iab-DU-CellIdentity-r16 CellIdentity, + positionInDCI-AI-r16 INTEGER(0..maxAI-DCI-PayloadSize-1-r16) OPTIONAL, -- Need M + availabilityCombinations-r16 SEQUENCE (SIZE (1..maxNrofAvailabilityCombinationsPerSet-r16)) OF AvailabilityCombination-r16, + ... + [[ + availabilityCombinationsRB-Groups-r17 SEQUENCE (SIZE (1..maxNrofAvailabilityCombinationsPerSet-r16)) OF AvailabilityCombinationRB-Groups-r17 + OPTIONAL -- Need M + ]], + [[ + positionInDCI-AI-RBGroups-v1720 INTEGER(0..maxAI-DCI-PayloadSize-1-r16) OPTIONAL -- Need M + ]] +} + +AvailabilityCombinationsPerCellIndex-r16 ::= INTEGER(0..maxNrofDUCells-r16) + +AvailabilityCombination-r16 ::= SEQUENCE { + availabilityCombinationId-r16 AvailabilityCombinationId-r16, + resourceAvailability-r16 SEQUENCE (SIZE (1..maxNrofResourceAvailabilityPerCombination-r16)) OF INTEGER (0..7) +} + +AvailabilityCombinationId-r16 ::= INTEGER (0..maxNrofAvailabilityCombinationsPerSet-1-r16) +``` + +``` + +AvailabilityCombinationRB-Groups-r17 ::= SEQUENCE { + availabilityCombinationId-r17 AvailabilityCombinationId-r16, + rb-SetGroups-r17 SEQUENCE (SIZE (1..maxNrofRB-SetGroups-r17)) OF RB-SetGroup-r17 + resourceAvailability-r17 SEQUENCE (SIZE (1..maxNrofResourceAvailabilityPerCombination-r16)) OF INTEGER (0..7) OPTIONAL, -- Need R +} +OPTIONAL -- Need R + +RB-SetGroup-r17 ::= SEQUENCE { + resourceAvailability-r17 SEQUENCE (SIZE (1..maxNrofResourceAvailabilityPerCombination-r16)) OF INTEGER (0..7) OPTIONAL, -- Need R + rb-Sets-r17 SEQUENCE (SIZE (1..maxNrofRB-Sets-r17)) OF INTEGER (0..7) OPTIONAL -- Need R +} + +-- TAG-AVAILABILITYCOMBINATIONS PER CELL-STOP +-- ASN1STOP + +``` + +##### AvailabilityCombination field descriptions + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| availabilityCombinationId | +| This ID is used in the DCI Format 2_5 payload to dynamically select this AvailabilityCombination , see TS 38.213 [13], clause 14. | +| resourceAvailability | +| Indicates the resource availability of soft symbols for a set of consecutive slots in the time domain. The meaning of this field is described in TS 38.213 [13], Table 14.3. If included in RB-SetGroup within AvailabilityCombinationRB-Groups-r17 , it indicates the availability of soft resources for an RB set group. If included in AvailabilityCombinationRB-Groups-r17 when the rb-SetGroups is not configured, it indicates the availability of soft resources in one or multiple slots for all RB sets of a DU cell. | + +##### AvailabilityCombinationsPerCell field descriptions + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| iab-DU-CellIdentity | +| The ID of the IAB-DU cell for which the availabilityCombinations are applicable. | +| positionInDCI-AI | +| The (starting) position (bit) of the availabilityCombinationId for the indicated IAB-DU cell ( iab-DU-CellIdentity ) within the DCI payload. If positionInDCI-AI-RBGroups is not configured, it applies to the availabilityCombinationId included in availabilityCombinations and in availabilityCombinationsRB-Groups . If positionInDCI-AI-RBGroups is configured, it applies to the availabilityCombinationId included in availabilityCombinations . | +| positionInDCI-AI-RBGroups | +| The (starting) position (bit) of the availabilityCombinationId associated to the availabilityCombinationsRB-Groups for the indicated IAB-DU cell ( iab-DU-CellIdentity ) within the DCI payload. | + +##### AvailabilityCombinationRB-Groups field descriptions + +| | +|-------------------------------------------------------------------------------------------------------------------| +| rb-SetGroups | +| Indicates the RB set groups configured for the availability combination. Each group includes consecutive RB sets. | +| rb-Sets | +| Indicates the one or more RB set indexes associated to one or more RB sets configured for one RB set group. | + +###### AvailabilityIndicator + +The IE *AvailabilityIndicator* is used to configure monitoring a PDCCH for Availability Indicators (AI). + +##### AvailabilityIndicator information element + +``` +-- ASN1START +-- TAG-AVAILABILITYINDICATOR-START + +AvailabilityIndicator-r16 ::= SEQUENCE { + ai-RNTI-r16 AI-RNTI-r16, + dci-PayloadSizeAI-r16 INTEGER (1..maxAI-DCI-PayloadSize-r16), + availableCombToAddModList-r16 SEQUENCE (SIZE(1..maxNrofDUCells-r16)) OF AvailabilityCombinationsPerCell-r16 OPTIONAL, -- Need N + availableCombToReleaseList-r16 SEQUENCE (SIZE(1..maxNrofDUCells-r16)) OF AvailabilityCombinationsPerCellIndex-r16 OPTIONAL, -- Need N + ... +} + +AI-RNTI-r16 ::= RNTI-Value + +-- TAG-AVAILABILITYINDICATOR-STOP +-- ASN1STOP +``` + +##### AvailabilityIndicator field descriptions + +| | | +|-----------------------------------|----------------------------------------------------------------------------------------------------------------------| +| ai-RNTI | Used by an IAB-MT for detection of DCI format 2_5 indicating AvailabilityCombinationId for an IAB-DU's cells. | +| availableCombToAddModList | A list of availabilityCombinations to add for the IAB-DU's cells. (see TS 38.213 [13], clause 14). | +| availableCombToReleaseList | A list of availabilityCombinations to release for the IAB-DU's cells. (see TS 38.213 [13], clause 14). | +| dci-PayloadSizeAI | Total length of the DCI payload scrambled with ai-RNTI (see TS 38.213 [13]). | + +##### BAP-RoutingID + +The IE *BAP-RoutingID* is used for IAB-node to configure the BAP Routing ID. + +##### BAP-RoutingID information element + +``` +-- ASN1START +-- TAG-BAPROUTINGID-START + +BAP-RoutingID-r16 ::= SEQUENCE { + bap-Address-r16 BIT STRING (SIZE (10)), + bap-PathId-r16 BIT STRING (SIZE (10)) +} +``` + +``` +-- TAG-BAPROUTINGID-STOP +-- ASN1STOP +``` + +| BAP-RoutingID field descriptions | +|------------------------------------------------------------------------------------------------| +| bap-Address
The ID of a destination IAB-node or IAB-donor-DU used in the BAP header. | +| bap-PathId
The ID of a path used in the BAP header. | + +##### – **BeamFailureRecoveryConfig** + +The IE *BeamFailureRecoveryConfig* is used to configure the UE with RACH resources and candidate beams for beam failure recovery in case of beam failure detection. See also TS 38.321 [3], clause 5.1.1. + +##### **BeamFailureRecoveryConfig information element** + +``` +-- ASN1START +-- TAG-BEAMFAILURERECOVERYCONFIG-START + +BeamFailureRecoveryConfig ::= SEQUENCE { + rootSequenceIndex-BFR INTEGER (0..137) OPTIONAL, -- Need M + rach-ConfigBFR RACH-ConfigGeneric OPTIONAL, -- Need M + rsrp-ThresholdSSB RSRP-Range OPTIONAL, -- Need M + candidateBeamRSList SEQUENCE (SIZE(1..maxNrofCandidateBeams)) OF PRACH-ResourceDedicatedBFR OPTIONAL, -- Need M + ssb-perRACH-Occasion ENUMERATED {oneEighth, oneFourth, oneHalf, one, two, + four, eight, sixteen} OPTIONAL, -- Need M + ra-ssb-OccasionMaskIndex INTEGER (0..15) OPTIONAL, -- Need M + recoverySearchSpaceId SearchSpaceId OPTIONAL, -- Need R + ra-Prioritization RA-Prioritization OPTIONAL, -- Need R + beamFailureRecoveryTimer ENUMERATED {ms10, ms20, ms40, ms60, ms80, ms100, ms150, ms200} OPTIONAL, -- Need M + ... + [[ + msg1-SubcarrierSpacing SubcarrierSpacing OPTIONAL -- Need M + ]], + [[ + ra-PrioritizationTwoStep-r16 RA-Prioritization OPTIONAL, -- Need R + candidateBeamRSListExt-v1610 SetupRelease{ CandidateBeamRSListExt-r16 } OPTIONAL -- Need M + ]], + [[ + spCell-BFR-CBRA-r16 ENUMERATED {true} OPTIONAL -- Need R + ]] +} + +PRACH-ResourceDedicatedBFR ::= CHOICE { + ssb BFR-SSB-Resource, +``` + +``` + csi-RS BFR-CSIRS-Resource +} + +BFR-SSB-Resource ::= SEQUENCE { + ssb SSB-Index, + ra-PreambleIndex INTEGER (0..63), + ... +} + +BFR-CSIRS-Resource ::= SEQUENCE { + csi-RS NZP-CSI-RS-ResourceId, + ra-OccasionList SEQUENCE (SIZE(1..maxRA-OccasionsPerCSIRS)) OF INTEGER (0..maxRA-Occasions-1) OPTIONAL, -- Need R + ra-PreambleIndex INTEGER (0..63) OPTIONAL, -- Need R + ... +} + +CandidateBeamRSListExt-r16 ::= SEQUENCE (SIZE(1..maxNrofCandidateBeamsExt-r16)) OF PRACH-ResourceDedicatedBFR + +-- TAG-BEAMFAILURERECOVERYCONFIG-STOP +-- ASN1STOP +``` + +| BeamFailureRecoveryConfig field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| beamFailureRecoveryTimer
Timer for beam failure recovery timer. Upon expiration of the timer the UE does not use CFRA for BFR. Value in ms. Value ms10 corresponds to 10 ms, value ms20 corresponds to 20 ms, and so on. | +| candidateBeamRSList, candidateBeamRSListExt-v1610
Set of reference signals (CSI-RS and/or SSB) identifying the candidate beams for recovery and the associated RA parameters. This set includes all elements of candidateBeamRSList (without suffix) and all elements of candidateBeamRSListExt-v1610 . The UE maintains candidateBeamRSList and candidateBeamRSListExt-v1610 separately: Receiving candidateBeamRSListExt-v1610 set to release releases only the entries that were configured by candidateBeamRSListExt-v1610 , and receiving candidateBeamRSListExt-v1610 set to setup replaces only the entries that were configured by candidateBeamRSListExt-v1610 with the newly signalled entries. The network configures these reference signals to be within the linked DL BWP (i.e., within the DL BWP with the same bwp-Id ) of the UL BWP in which the BeamFailureRecoveryConfig is provided. | +| msg1-SubcarrierSpacing
Subcarrier spacing for contention free beam failure recovery (see TS 38.211 [16], clause 5.3.2).
Only the following values are applicable depending on the used frequency:
FR1: 15 or 30 kHz
FR2-1: 60 or 120 kHz
FR2-2: 120, 480, or 960 kHz | +| rsrp-ThresholdSSB
L1-RSRP threshold used for determining whether a candidate beam may be used by the UE to attempt contention free random access to recover from beam failure (see TS 38.213 [13], clause 6). | +| ra-prioritization
Parameters which apply for prioritized random access procedure for BFR (see TS 38.321 [3], clause 5.1.1). | +| ra-PrioritizationTwoStep
Parameters which apply for prioritized 2-step random access procedure for BFR (see TS 38.321 [3], clause 5.1.1). | +| ra-ssb-OccasionMaskIndex
Explicitly signalled PRACH Mask Index for RA Resource selection in TS 38.321 [3]. The mask is valid for all SSB resources. | +| rach-ConfigBFR
Configuration of random access parameters for BFR. | +| recoverySearchSpaceId
Search space to use for BFR RAR. The network configures this search space to be within the linked DL BWP (i.e., within the DL BWP with the same bwp-Id ) of the UL BWP in which the BeamFailureRecoveryConfig is provided. The CORESET associated with the recovery search space cannot be associated with another search space. Network always configures the UE with a value for this field when contention free random access resources for BFR are configured. | +| rootSequenceIndex-BFR
PRACH root sequence index (see TS 38.211 [16], clause 6.3.3.1) for beam failure recovery. | +| spCell-BFR-CBRA
Indicates that UE is configured to send MAC CE for SpCell BFR as specified in TS38.321 [3]. | +| ssb-perRACH-Occasion
Number of SSBs per RACH occasion for CF-BFR, see TS 38.213 [13], clause 8.1. | + +| BFR-CSI-RS-Resource field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| csi-RS
The ID of a NZP-CSI-RS-Resource configured in the CSI-MeasConfig of this serving cell. This reference signal determines a candidate beam for beam failure recovery (BFR). | +| ra-OccasionList
RA occasions that the UE shall use when performing BFR upon selecting the candidate beam identified by this CSI-RS. The network ensures that the RA occasion indexes provided herein are also configured by prach-ConfigurationIndex and msg1-FDM. Each RACH occasion is sequentially numbered, 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 and Third, in increasing order of indexes for PRACH slots.
If the field is absent the UE uses the RA occasion associated with the SSB that is QCled with this CSI-RS. | +| ra-PreambleIndex
The RA preamble index to use in the RA occasions associated with this CSI-RS. If the field is absent, the UE uses the preamble index associated with the SSB that is QCled with this CSI-RS. | + +| BFR-SSB-Resource field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------| +| ra-PreambleIndex
The preamble index that the UE shall use when performing BFR upon selecting the candidate beams identified by this SSB. | +| ssb
The ID of an SSB transmitted by this serving cell. It determines a candidate beam for beam failure recovery (BFR). | + +##### BeamFailureRecoveryRSConfig + +The IE *BeamFailureRecoveryRSConfig* is used to configure the UE with candidate beams for beam failure recovery in case of beam failure detection. See also TS 38.321 [3], clause 5.17. + +##### BeamFailureRecoveryRSConfig information element + +``` +-- ASN1START +-- TAG-BEAMFAILURERECOVERYRSCONFIG-START + +BeamFailureRecoveryRSConfig-r16 ::= SEQUENCE { + rsrp-ThresholdBFR-r16 RSRP-Range OPTIONAL, -- Need M + candidateBeamRS-List-r16 SEQUENCE (SIZE(1..maxNrofCandidateBeams-r16)) OF CandidateBeamRS-r16 OPTIONAL, -- Need M + ... + [[ + candidateBeamRS-List2-r17 SEQUENCE (SIZE(1..maxNrofCandidateBeams-r16)) OF CandidateBeamRS-r16 OPTIONAL -- Need R + ]] +} + +-- TAG-BEAMFAILURERECOVERYRSCONFIG-STOP +-- ASN1STOP +``` + +| BeamFailureRecoveryRSConfig field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| candidateBeamRS-List
A list of reference signals (CSI-RS and/or SSB) identifying the candidate beams for recovery. The network always configures this parameter in every instance of this IE. | +| candidateBeamRS-List2
A list of reference signals (CSI-RS and/or SSB) identifying the candidate beams for recovery. | +| rsrp-ThresholdBFR
L1-RSRP threshold used for determining whether a candidate beam may be included by the UE in MAC CE for BFR (see TS 38.321 [3] and TS 38.213 [13], clause 6). The network always configures this parameter in every instance of this IE. | + +##### — **BetaOffsets** + +The IE *BetaOffsets* is used to configure beta-offset values, see TS 38.213 [13], clause 9.3. + +##### **BetaOffsets information element** + +``` +-- ASN1START +-- TAG-BETAOFFSETS-START + +BetaOffsets ::= SEQUENCE { + betaOffsetACK-Index1 INTEGER(0..31) OPTIONAL, -- Need S + betaOffsetACK-Index2 INTEGER(0..31) OPTIONAL, -- Need S + betaOffsetACK-Index3 INTEGER(0..31) OPTIONAL, -- Need S + betaOffsetCSI-Part1-Index1 INTEGER(0..31) OPTIONAL, -- Need S + betaOffsetCSI-Part1-Index2 INTEGER(0..31) OPTIONAL, -- Need S + betaOffsetCSI-Part2-Index1 INTEGER(0..31) OPTIONAL, -- Need S + betaOffsetCSI-Part2-Index2 INTEGER(0..31) OPTIONAL -- Need S +} + +-- TAG-BETAOFFSETS-STOP +-- ASN1STOP +``` + +| BetaOffsets field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| betaOffsetACK-Index1
Up to 2 bits HARQ-ACK (see TS 38.213 [13], clause 9.3). When the field is absent the UE applies the value 11. | +| betaOffsetACK-Index2
Up to 11 bits HARQ-ACK (see TS 38.213 [13], clause 9.3). When the field is absent the UE applies the value 11. | +| betaOffsetACK-Index3
Above 11 bits HARQ-ACK (see TS 38.213 [13], clause 9.3). When the field is absent the UE applies the value 11. | +| betaOffsetCSI-Part1-Index1
Up to 11 bits of CSI part 1 bits (see TS 38.213 [13], clause 9.3). When the field is absent the UE applies the value 13. | +| betaOffsetCSI-Part1-Index2
Above 11 bits of CSI part 1 bits (see TS 38.213 [13], clause 9.3). When the field is absent the UE applies the value 13. | +| betaOffsetCSI-Part2-Index1
Up to 11 bits of CSI part 2 bits (see TS 38.213 [13], clause 9.3). When the field is absent the UE applies the value 13. | +| betaOffsetCSI-Part2-Index2
Above 11 bits of CSI part 2 bits (see TS 38.213 [13], clause 9.3). When the field is absent the UE applies the value 13. | + +##### – ***BetaOffsetsCrossPri*** + +The IE *BetaOffsetsCrossPri* is used to configure beta-offset values for cross-priority HARQ-ACK multiplexing on PUSCH. + +##### ***BetaOffsetsCrossPri* information element** + +``` +-- ASN1START +-- TAG-BETAOFFSETSCROSSPRI-START + +BetaOffsetsCrossPri-r17 ::= SEQUENCE (SIZE(3)) OF INTEGER(0..31) + +-- TAG-BETAOFFSETSCROSSPRI-STOP +-- ASN1STOP +``` + +#### – ***BH-LogicalChannelIdentity*** + +The IE *BH-LogicalChannelIdentity* is used to identify a logical channel between an IAB-node and its parent IAB-node or IAB-donor-DU. + +##### ***BH-LogicalChannelIdentity* information element** + +``` +-- ASN1START +-- TAG-BHLOGICALCHANNELIDENTITY-START + +BH-LogicalChannelIdentity-r16 ::= CHOICE { + bh-LogicalChannelIdentity-r16 LogicalChannelIdentity, + bh-LogicalChannelIdentityExt-r16 BH-LogicalChannelIdentity-Ext-r16 +} +``` + +``` +-- TAG-BHLOGICALCHANNELIDENTITY-STOP +-- ASN1STOP +``` + +##### ***BH-LogicalChannelIdentity* field descriptions** + +| | +|------------------------------------------------------------------------------------| +| bh-LogicalChannelIdentity
ID used for the MAC logical channel. | +| bh-LogicalChannelIdentityExt
ID used for the MAC logical channel. | + +###### — ***BH-LogicalChannelIdentity-Ext*** + +The IE *BH-LogicalChannelIdentity-Ext* is used to identify a logical channel between an IAB-node and its parent node. + +##### ***BH-LogicalChannelIdentity-Ext* information element** + +``` +-- ASN1START +-- TAG-BHLOGICALCHANNELIDENTITYEXT-START + +BH-LogicalChannelIdentity-Ext-r16 ::= INTEGER (320.. maxLC-ID-Iab-r16) + +-- TAG-BHLOGICALCHANNELIDENTITYEXT-STOP +-- ASN1STOP +``` + +##### — ***BH-RLC-ChannelConfig*** + +The IE *BH-RLC-ChannelConfig* is used to configure an RLC entity, a corresponding logical channel in MAC for BH RLC channel between IAB-node and its parent node. + +#### ***BH-RLC-ChannelConfig* information element** + +``` +-- ASN1START +-- TAG-BHRLCHANNELCONFIG-START + +BH-RLC-ChannelConfig-r16 ::= SEQUENCE { + bh-LogicalChannelIdentity-r16 BH-LogicalChannelIdentity-r16 OPTIONAL, -- Cond LCH-SetupOnly + bh-RLC-ChannelID-r16 BH-RLC-ChannelID-r16, + reestablishRLC-r16 ENUMERATED {true} OPTIONAL, -- Need N + rlc-Config-r16 RLC-Config OPTIONAL, -- Cond LCH-Setup + mac-LogicalChannelConfig-r16 LogicalChannelConfig OPTIONAL, -- Cond LCH-Setup + ... +} + +-- TAG-BHRLCHANNELCONFIG-STOP +-- ASN1STOP +``` + +| BH-RLC-ChannelConfig field descriptions | | +|------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------| +| bh-LogicalChannelIdentity | Indicates the logical channel id for BH RLC channel of the IAB-node. | +| bh-RLC-ChannelID | Indicates the 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. | +| reestablishRLC | Indicates that RLC should be re-established. | +| rlc-Config | Determines the RLC mode (UM, AM) and provides corresponding parameters. | + +| Conditional Presence | Explanation | +|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------| +| LCH-Setup | This field is mandatory present upon creation of a new logical channel for a BH RLC channel. It is optionally present, Need M, otherwise. | +| LCH-SetupOnly | This field is mandatory present upon creation of a new logical channel for a BH RLC channel. It is absent, Need M otherwise. | + +#### – BH-RLC-ChannelID + +The IE *BH-RLC-ChannelID* is used to identify 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. + +##### **BH-RLC-ChannelID information element** + +``` +-- ASN1START +-- TAG-BHRLCCHANNELID-START + +BH-RLC-ChannelID-r16 ::= BIT STRING (SIZE (16)) + +-- TAG-BHRLCCHANNELID-STOP +-- ASN1STOP +``` + +##### – BSR-Config + +The IE *BSR-Config* is used to configure buffer status reporting. + +#### **BSR-Config information element** + +``` +-- ASN1START +-- TAG-BSR-CONFIG-START + +BSR-Config ::= SEQUENCE { + periodicBSR-Timer ENUMERATED { sf1, sf5, sf10, sf16, sf20, sf32, sf40, sf64, + sf80, sf128, sf160, sf320, sf640, sf1280, sf2560, infinity }, + retxBSR-Timer ENUMERATED { sf10, sf20, sf40, sf80, sf160, sf320, sf640, sf1280, sf2560, + sf5120, sf10240, spare5, spare4, spare3, spare2, spare1}, + logicalChannelSR-DelayTimer ENUMERATED { sf20, sf40, sf64, sf128, sf512, sf1024, sf2560, spare1} OPTIONAL, -- Need R +``` + +``` + + ... +} + +-- TAG-BSR-CONFIG-STOP +-- ASN1STOP + +``` + +| BSR-Config field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| logicalChannelSR-DelayTimer
Value in number of subframes. Value sf20 corresponds to 20 subframes, sf40 corresponds to 40 subframes, and so on. | +| periodicBSR-Timer
Value in number of subframes. Value sf1 corresponds to 1 subframe, value sf5 corresponds to 5 subframes and so on. | +| retxBSR-Timer
Value in number of subframes. Value sf10 corresponds to 10 subframes, value sf20 corresponds to 20 subframes and so on. | + +##### — ***BWP*** + +The IE *BWP* is used to configure generic parameters of a bandwidth part as defined in TS 38.211 [16], clause 4.5, and TS 38.213 [13], clause 12. + +For each serving cell the network configures at least an initial downlink bandwidth part and one (if the serving cell is configured with an uplink) or two (if using supplementary uplink (SUL)) initial uplink bandwidth parts. Furthermore, the network may configure additional uplink and downlink bandwidth parts for a serving cell. + +The uplink and downlink bandwidth part configurations are divided into common and dedicated parameters. + +##### ***BWP* information element** + +``` + +-- ASN1START +-- TAG-BWP-START + +BWP ::= SEQUENCE { + locationAndBandwidth INTEGER (0..37949), + subcarrierSpacing SubcarrierSpacing, + cyclicPrefix ENUMERATED { extended } OPTIONAL -- Need R +} + +-- TAG-BWP-STOP +-- ASN1STOP + +``` + +| BWP field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| cyclicPrefix
Indicates whether to use the extended cyclic prefix for this bandwidth part. If not set, the UE uses the normal cyclic prefix. Normal CP is supported for all subcarrier spacings and slot formats. Extended CP is supported only for 60 kHz subcarrier spacing. (see TS 38.211 [16], clause 4.2). Except for SUL, the network ensures the same cyclic prefix length is used in active DL BWP and active UL BWP within a serving cell. | +| locationAndBandwidth
Frequency domain location and bandwidth of this bandwidth part. The value of the field shall be interpreted as resource indicator value (RIV) as defined TS 38.214 [19] with assumptions as described in TS 38.213 [13], clause 12, i.e. setting =275. The first PRB is a PRB determined by subcarrierSpacing of this BWP and offsetToCarrier (configured in SCS-SpecificCarrier contained within FrequencyInfoDL / FrequencyInfoUL / FrequencyInfoUL-SIB / FrequencyInfoDL-SIB within ServingCellConfigCommon / ServingCellConfigCommonSIB ) corresponding to this subcarrier spacing. In case of TDD, a BWP-pair (UL BWP and DL BWP with the same bwp-Id ) must have the same center frequency (see TS 38.213 [13], clause 12) | +| subcarrierSpacing
Subcarrier spacing to be used in this BWP for all channels and reference signals unless explicitly configured elsewhere. Corresponds to subcarrier spacing according to TS 38.211 [16], table 4.2-1. The value kHz15 corresponds to $\mu=0$ , value kHz30 corresponds to $\mu=1$ , and so on.
Only the following values are applicable depending on the used frequency:
FR1: 15, 30, or 60 kHz
FR2-1: 60 or 120 kHz
FR2-2: 120, 480, or 960 kHz
For the initial DL BWP and operation in licensed spectrum this field has the same value as the field subCarrierSpacingCommon in MIB of the same serving cell. Except for SUL, the network ensures the same subcarrier spacing is used in active DL BWP and active UL BWP within a serving cell. For the initial DL BWP and operation with shared spectrum channel access, the value of this field corresponds to the subcarrier spacing of the SSB associated to the initial DL BWP. | + +#### – **BWP-Downlink** + +The IE *BWP-Downlink* is used to configure an additional downlink bandwidth part (not for the initial BWP). + +##### **BWP-Downlink information element** + +``` +-- ASN1START +-- TAG-BWP-DOWNLINK-START + +BWP-Downlink ::= SEQUENCE { + bwp-Id BWP-Id, + bwp-Common BWP-DownlinkCommon OPTIONAL, -- Cond SetupOtherBWP + bwp-Dedicated BWP-DownlinkDedicated OPTIONAL, -- Cond SetupOtherBWP + ... +} + +-- TAG-BWP-DOWNLINK-STOP +-- ASN1STOP +``` + +| BWP-Downlink field descriptions | | +|----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| bwp-Id | An identifier for this bandwidth part. Other parts of the RRC configuration use the BWP-Id to associate themselves with a particular bandwidth part. The network configures the BWPs with consecutive IDs from 1. The Network does not include the value 0, since value 0 is reserved for the initial BWP. | + +| Conditional Presence | Explanation | +|-----------------------------|------------------------------------------------------------------------------------------------------------------------| +| SetupOtherBWP | The field is mandatory present upon configuration of a new DL BWP. The field is optionally present, Need M, otherwise. | + +##### – ***BWP-DownlinkCommon*** + +The IE *BWP-DownlinkCommon* is used to configure the common parameters of a downlink BWP. They are "cell specific" and the network ensures the necessary alignment with corresponding parameters of other UEs. The common parameters of the initial bandwidth part of the PCell are also provided via system information. For all other serving cells, the network provides the common parameters via dedicated signalling. + +#### ***BWP-DownlinkCommon* information element** + +``` +-- ASN1START +-- TAG-BWP-DOWNLINKCOMMON-START + +BWP-DownlinkCommon ::= SEQUENCE { + genericParameters BWP, + pdcch-ConfigCommon SetupRelease { PDCCH-ConfigCommon } OPTIONAL, -- Need M + pdsch-ConfigCommon SetupRelease { PDSCH-ConfigCommon } OPTIONAL, -- Need M + ... +} + +-- TAG-BWP-DOWNLINKCOMMON-STOP +-- ASN1STOP +``` + +| BWP-DownlinkCommon field descriptions | | +|----------------------------------------------|---------------------------------------------------------------------------------------------| +| pdcch-ConfigCommon | Cell specific parameters for the PDCCH of this BWP. This field is absent for a dormant BWP. | +| pdsch-ConfigCommon | Cell specific parameters for the PDSCH of this BWP. | + +##### – ***BWP-DownlinkDedicated*** + +The IE *BWP-DownlinkDedicated* is used to configure the dedicated (UE specific) parameters of a downlink BWP. + +#### **BWP-DownlinkDedicated information element** + +``` + +-- ASN1START +-- TAG-BWP-DOWNLINKDEDICATED-START + +BWP-DownlinkDedicated ::= SEQUENCE { + pdcch-Config SetupRelease { PDCCH-Config } OPTIONAL, -- Need M + pdsch-Config SetupRelease { PDSCH-Config } OPTIONAL, -- Need M + sps-Config SetupRelease { SPS-Config } OPTIONAL, -- Need M + radioLinkMonitoringConfig SetupRelease { RadioLinkMonitoringConfig } OPTIONAL, -- Need M + ... + [[ + sps-ConfigToAddModList-r16 SPS-ConfigToAddModList-r16 OPTIONAL, -- Need N + sps-ConfigToReleaseList-r16 SPS-ConfigToReleaseList-r16 OPTIONAL, -- Need N + sps-ConfigDeactivationStateList-r16 SPS-ConfigDeactivationStateList-r16 OPTIONAL, -- Need R + beamFailureRecoverySCellConfig-r16 SetupRelease { BeamFailureRecoveryRSConfig-r16} OPTIONAL, -- Cond SCellOnly + sl-PDCCH-Config-r16 SetupRelease { PDCCH-Config } OPTIONAL, -- Need M + sl-V2X-PDCCH-Config-r16 SetupRelease { PDCCH-Config } OPTIONAL, -- Need M + ]], + [[ + preConfigGapStatus-r17 BIT STRING (SIZE (maxNrofGapId-r17)) OPTIONAL, -- Cond PreConfigMG + beamFailureRecoverySpCellConfig-r17 SetupRelease { BeamFailureRecoveryRSConfig-r16} OPTIONAL, -- Cond SpCellOnly + harq-FeedbackEnablingforSPSactive-r17 BOOLEAN OPTIONAL, -- Need R + cfr-ConfigMulticast-r17 SetupRelease { CFR-ConfigMulticast-r17 } OPTIONAL, -- Need M + dl-PPW-PreConfigToAddModList-r17 DL-PPW-PreConfigToAddModList-r17 OPTIONAL, -- Need N + dl-PPW-PreConfigToReleaseList-r17 DL-PPW-PreConfigToReleaseList-r17 OPTIONAL, -- Need N + nonCellDefiningSSB-r17 NonCellDefiningSSB-r17 OPTIONAL, -- Need R + servingCellMO-r17 MeasObjectId OPTIONAL -- Cond MeasObject-NCD-SSB + ]], + [[ + tci-SelectionPresentIn-DCI-r18 ENUMERATED { enabled } OPTIONAL, -- Need R + applyIndicatedTCI-StateDCI-1-0-r18 ENUMERATED {first, second, both} OPTIONAL, -- Need R + ]] +} + +SPS-ConfigToAddModList-r16 ::= SEQUENCE (SIZE (1..maxNrofSPS-Config-r16)) OF SPS-Config +SPS-ConfigToReleaseList-r16 ::= SEQUENCE (SIZE (1..maxNrofSPS-Config-r16)) OF SPS-ConfigIndex-r16 +SPS-ConfigDeactivationState-r16 ::= SEQUENCE (SIZE (1..maxNrofSPS-Config-r16)) OF SPS-ConfigIndex-r16 +SPS-ConfigDeactivationStateList-r16 ::= SEQUENCE (SIZE (1..maxNrofSPS-DeactivationState)) OF SPS-ConfigDeactivationState-r16 +DL-PPW-PreConfigToAddModList-r17 ::= SEQUENCE (SIZE (1..maxNrofPPW-Config-r17)) OF DL-PPW-PreConfig-r17 +DL-PPW-PreConfigToReleaseList-r17 ::= SEQUENCE (SIZE (1..maxNrofPPW-Config-r17)) OF DL-PPW-ID-r17 + +-- TAG-BWP-DOWNLINKDEDICATED-STOP +-- ASN1STOP + +``` + +| BWP-DownlinkDedicated field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| applyIndicatedTCI-StateDCI-1-0
This field indicates, for PDSCH reception scheduled by DCI format 1_0, if UE applies the first, the second or both "indicated" DL only TCI or joint TCI as specified in TS 38.214 [19], clause 5.1.5. Only when the UE is configured with PDSCH-CJT( cjt-Scheme-PDSCH in IE ServingCellConfig ) and the UE supports two joint TCI states for PDSCH-CJT or the UE is configured with PDSCH-SFN( sfnSchemePDSCH in IE ServingCellConfig ), the RRC configuration can indicate both indicated joint/DL TCI states are applied. | +| beamFailureRecoverySCellConfig
Configuration of candidate RS for beam failure recovery on SCells. | +| beamFailureRecoverySpCellConfig
Configuration of candidate RS for beam failure recovery on the SpCell. This field can only be configured when beamFailure-r17 is configured in RadioLinkMonitoringConfig . | +| cfr-ConfigMulticast
UE specific common frequency resource configuration for MBS multicast for one dedicated BWP. This field can be configured within at most one serving cell. | +| dl-PPW-PreConfigToAddModList
Indicates a list of DL-PRS processing window configurations to be added or modified for the dedicated DL BWP. | +| dl-PPW-PreConfigToReleaseList
Indicates a list of DL-PRS processing window configurations to be released for the dedicated DL BWP. | +| harq-FeedbackEnablingforSPSactive
If enabled, UE reports ACK/NACK for the first SPS PDSCH after activation, regardless of if HARQ feedback is enabled or disabled corresponding to the first SPS PDSCH after activation. Otherwise, UE follows configuration of HARQ feedback enabled/disabled corresponding to the first SPS PDSCH after activation. | +| nonCellDefiningSSB
If configured, the UE operating in this BWP uses this SSB for the purposes for which it would otherwise have used the CD-SSB of the serving cell (e.g. obtaining sync, measurements, RLM, BFD, beam management). Furthermore, other parts of the BWP configuration that refer to an SSB (e.g. the "SSB" configured in the QCL-Info IE; the "ssb-Index" configured in the RadioLinkMonitoringRS ; CFRA-SSB-Resource ; PRACH-ResourceDedicatedBFR ) refer implicitly to this NCD-SSB. The NCD-SSB has the same values for the properties (e.g., ssb-PositionsInBurst , PCI , ssb-PBCH-BlockPower ) of the corresponding CD-SSB apart from the values of the properties configured in the NonCellDefiningSSB-r17 IE. | +| pdcch-Config
UE specific PDCCH configuration for one BWP. | +| pdsch-Config
UE specific PDSCH configuration for one BWP. | +| preConfGapStatus
Indicates whether the pre-configured measurement gaps (i.e. the gaps configured with preConfigInd ) are activated or deactivated upon the switch to this BWP. If this field is configured, the UE shall apply network-controlled mechanism for activation and deactivation of the pre-configured measurement gaps, otherwise the UE shall apply the autonomous activation/deactivation mechanism, as specified in TS 38.133 [14]. The first/leftmost bit corresponds to the measurement gap with gap ID 1, the second bit corresponds to measurement gap with gap ID 2, and so on. Value 0 indicates that the corresponding pre-configured measurement gap is deactivated while value 1 indicates that the corresponding pre-configured measurement gap is activated. The UE shall ignore the bit if the corresponding measurement gap is not a pre-configured measurement gap. | +| servingCellMO
measObjectId of the MeasObjectNR in MeasConfig which is associated to the serving cell. For this MeasObjectNR , the following relationship applies between this MeasObjectNR and nonCellDefiningSSB in BWP-DownlinkDedicated of the associated downlink BWP: if ssbFrequency is configured, its value is the same as the absoluteFrequencySSB in the nonCellDefiningSSB . If the field is present in a downlink BWP and the BWP is activated, the UE uses this measurement object for serving cell measurements (e.g., including those used in measurement report triggering events), otherwise, the UE uses the servingCellMO in ServingCellConfig IE. | +| sps-Config
UE specific SPS (Semi-Persistent Scheduling) configuration for one BWP. Except for reconfiguration with sync, the NW does not reconfigure sps-Config when there is an active configured downlink assignment (see TS 38.321 [3]). However, the NW may release the sps-Config at any time. Network can only configure SPS in one BWP using either this field or sps-ConfigToAddModList . Network does not configure SPS in one BWP using this field and sps-ConfigMulticastToAddModList-r17 simultaneously. | + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sps-ConfigDeactivationStateList
Indicates a list of the deactivation states in which each state can be mapped to a single or multiple SPS configurations to be deactivated, see clause 10.2 in TS 38.213 [13]. If a state is mapped to multiple SPS configurations, each of these SPS configurations is configured with the same harq-CodebookID . | +| sps-ConfigToAddModList
Indicates a list of one or more DL SPS configurations to be added or modified in one BWP. Except for reconfiguration with sync, the NW does not reconfigure a SPS configuration when it is active (see TS 38.321 [3]). | +| sps-ConfigToReleaseList
Indicates a list of one or more DL SPS configurations to be released. The NW may release a SPS configuration at any time. | +| radioLinkMonitoringConfig
UE specific configuration of radio link monitoring for detecting cell- and beam radio link failure occasions. The maximum number of failure detection resources should be limited up to 8 for both cell and beam radio link failure detection. For SCells, only periodic 1-port CSI-RS can be configured in IE RadioLinkMonitoringConfig . | +| sl-PDCCH-Config
Indicates the UE specific PDCCH configurations for receiving the SL grants (via SL-RNTI or SL-CS-RNTI) for NR sidelink communication/discovery. | +| sl-V2X-PDCCH-Config
Indicates the UE specific PDCCH configurations for receiving SL grants (i.e. sidelink SPS) for V2X sidelink communication. | +| tci-SelectionPresentIn-DCI
Indicates if a [TCI selection field] is present or absent in DCI format 1_1 and DCI format 1_2 for a DL BWP, see reference XXX. | + +| Conditional Presence | Explanation | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MeasObject-NCD-SSB | This field is optionally present, Need S, if nonCellDefiningSSB is configured in this DL BWP. It is absent otherwise. | +| PreConfigMG | The field is optionally present, Need R, if there is at least one per UE gap configured with preConfigInd or there is at least one per FR gap of the same FR which the BWP belongs to and configured with preConfigInd . It is absent, Need R, otherwise. | +| ScellOnly | The field is optionally present, Need M, in the BWP-DownlinkDedicated of an Scell. It is absent otherwise. | +| SpCellOnly | The field is optionally present, Need M, in the BWP-DownlinkDedicated of an Spcell. It is absent otherwise. | + +##### – *BWP-Id* + +The IE *BWP-Id* is used to refer to Bandwidth Parts (BWP). The initial BWP (including (e)RedCap-specific initial BWP, if configured) is referred to by *BWP-Id* 0. The other BWPs are referred to by *BWP-Id* 1 to *maxNrofBWPs*. + +##### *BWP-Id* information element + +``` +-- ASN1START +-- TAG-BWP-ID-START + +BWP-Id ::= INTEGER (0..maxNrofBWPs) + +-- TAG-BWP-ID-STOP +-- ASN1STOP +``` + +#### BWP-Uplink + +The IE *BWP-Uplink* is used to configure an additional uplink bandwidth part (not for the initial BWP). + +##### BWP-Uplink information element + +``` +-- ASN1START +-- TAG-BWP-UPLINK-START + +BWP-Uplink ::= SEQUENCE { + bwp-Id BWP-Id, + bwp-Common BWP-UplinkCommon OPTIONAL, -- Cond SetupOtherBWP + bwp-Dedicated BWP-UplinkDedicated OPTIONAL, -- Cond SetupOtherBWP + ... +} + +-- TAG-BWP-UPLINK-STOP +-- ASN1STOP +``` + +##### BWP-Uplink field descriptions + +###### *bwp-Id* + +An identifier for this bandwidth part. Other parts of the RRC configuration use the *BWP-Id* to associate themselves with a particular bandwidth part. + +The network configures the BWPs with consecutive IDs from 1. The Network does not include the value 0, since value 0 is reserved for the initial BWP. + +| Conditional Presence | Explanation | +|----------------------|------------------------------------------------------------------------------------------------------------------------| +| SetupOtherBWP | The field is mandatory present upon configuration of a new UL BWP. The field is optionally present, Need M, otherwise. | + +##### BWP-UplinkCommon + +The IE *BWP-UplinkCommon* is used to configure the common parameters of an uplink BWP. They are "cell specific" and the network ensures the necessary alignment with corresponding parameters of other UEs. The common parameters of the initial bandwidth part of the PCell are also provided via system information. For all other serving cells, the network provides the common parameters via dedicated signalling. + +#### BWP-UplinkCommon information element + +``` +-- ASN1START +-- TAG-BWP-UPLINKCOMMON-START + +BWP-UplinkCommon ::= SEQUENCE { + genericParameters BWP, + rach-ConfigCommon SetupRelease { RACH-ConfigCommon } OPTIONAL, -- Need M + pusch-ConfigCommon SetupRelease { PUSCH-ConfigCommon } OPTIONAL, -- Need M + pucch-ConfigCommon SetupRelease { PUCCH-ConfigCommon } OPTIONAL, -- Need M +} +``` + +``` + +... +[[ +rach-ConfigCommonIAB-r16 SetupRelease { RACH-ConfigCommon } OPTIONAL, -- Need M +useInterlacePUCCH-PUSCH-r16 ENUMERATED {enabled} OPTIONAL, -- Need R +msgA-ConfigCommon-r16 SetupRelease { MsgA-ConfigCommon-r16 } OPTIONAL -- Cond SpCellOnly2 +]], +[[ +enableRA-PrioritizationForSlicing-r17 BOOLEAN OPTIONAL, -- Cond RA-PrioSliceAI +additionalRACH-ConfigList-r17 SetupRelease { AdditionalRACH-ConfigList-r17 } OPTIONAL, -- Cond SpCellOnly2 +rsrp-ThresholdMsg3-r17 RSRP-Range OPTIONAL, -- Need R +numberOfMsg3-RepetitionsList-r17 SEQUENCE (SIZE (4)) OF NumberOfMsg3-Repetitions-r17 OPTIONAL, -- Cond Msg3Rep +mcs-Msg3-Repetitions-r17 SEQUENCE (SIZE (8)) OF INTEGER (0..31) OPTIONAL -- Cond Msg3Rep +]], +[[ +additionalRACH-perPCI-ToAddModList-r18 SEQUENCE (SIZE (1.. maxNrofAdditionalPRACHConfigs-r18)) OF RACH-ConfigTwoTA-r18 + OPTIONAL, -- Cond 2TA-Only +additionalRACH-perPCI-ToReleaseList-r18 SEQUENCE (SIZE (1.. maxNrofAdditionalPRACHConfigs-r18)) OF RACH-ConfigTwoTAIndex-r18 + OPTIONAL, -- Need N +rsrp-ThresholdMsg1-RepetitionNum2-r18 RSRP-Range OPTIONAL, -- Cond Msg1Repl +rsrp-ThresholdMsg1-RepetitionNum4-r18 RSRP-Range OPTIONAL, -- Cond Msg1Repl +rsrp-ThresholdMsg1-RepetitionNum8-r18 RSRP-Range OPTIONAL, -- Cond Msg1Repl +preambleTransMax-Msg1-Repetition-r18 ENUMERATED {n1, n2, n4, n6, n8, n10, n20, n50, n100, n200} OPTIONAL -- Cond Msg1Repl +]] +} + +AdditionalRACH-ConfigList-r17 ::= SEQUENCE (SIZE (1..maxAdditionalRACH-r17)) OF AdditionalRACH-Config-r17 + +AdditionalRACH-Config-r17 ::= SEQUENCE { + rach-ConfigCommon-r17 RACH-ConfigCommon OPTIONAL, -- Need R + msgA-ConfigCommon-r17 MsgA-ConfigCommon-r16 OPTIONAL, -- Need R + ... +} + +NumberOfMsg3-Repetitions-r17 ::= ENUMERATED {n1, n2, n3, n4, n7, n8, n12, n16} + +-- TAG-BWP-ULINKCOMMON-STOP +-- ASN1STOP + +``` + +| BWP-UplinkCommon field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| additionalRACH-ConfigList
List of feature or feature combination-specific RACH configurations, i.e. the RACH configurations configured in addition to the one configured by rach-ConfigCommon and by msgA-ConfigCommon . The network associates all possible preambles of an additional RACH configuration to one or more feature(s) or feature combination(s). The network does not configure this list to have more than 32 entries. If both rach-ConfigCommon and msgA-ConfigCommon are configured for a specific FeatureCombination , the network always provides them in the same additionalRACH-Config . | +| additionalRACH-perPCI-ToAddModList
List of RACH configurations for the additional PCIs. The RACH configuration for an additional PCI is applied for Random Access procedure initiated by PDCCH order towards to the additional PCI, as specified in TS 38.321 clause 5.1.1b. This configuration may be different for different UEs. | +| enableRA-PrioritizationForSlicing
Indicates whether or not the ra-PrioritizationForSlicing/ra-PrioritizationForSlicingTwoStep should override the ra-PrioritizationForAccessIdentity . The field is applicable only when the UE is configured by upper layers with both NSAG and Access Identity 1 or 2. If value TRUE is configured, the UE should only apply the ra-PrioritizationForSlicing/ra-PrioritizationForSlicingTwoStep . If value FALSE is configured, the UE should only apply ra-PrioritizationForAccessIdentity . If the field is absent, whether to use ra-PrioritizationForSlicing/ra-PrioritizationForSlicingTwoStep or ra-PrioritizationForAccessIdentity is up to UE implementation. | +| mcs-Msg3-Repetitions
Configuration of eight candidate MCS indexes for PUSCH transmission scheduled by RAR UL grant and DCI format 0_0 with CRC scrambled by TC-RNTI. Only the first 4 configured or default MCS indexes are used for PUSCH transmission scheduled by RAR UL grant. This field is only applicable when the UE selects Random Access resources indicating Msg3 repetition in this BWP. If this field is absent when the set(s) of Random Access resources with MSG3 repetition indication are configured in the BWP-UplinkCommon , the UE shall apply the values {0, 1, 2, 3, 4, 5, 6, 7} (see TS 38.214 [19], clause 6.1.4). | +| msgA-ConfigCommon
Configuration of the cell specific PRACH and PUSCH resource parameters for transmission of MsgA in 2-step random access type procedure. The NW can configure msgA-ConfigCommon only for UL BWPs if the linked DL BWPs (same bwp-Id as UL-BWP) are the initial DL BWPs or DL BWPs containing the SSB associated to the initial DL BWP or DL BWPs associated with nonCellDefiningSSB or, for (e)RedCap UEs, the (e)RedCap-specific initial downlink BWP. | +| numberOfMsg3-RepetitionsList
The number of repetitions for PUSCH transmission scheduled by RAR UL grant and DCI format 0_0 with CRC scrambled by TC-RNTI. This field is only applicable when the UE selects Random Access resources indicating Msg3 repetition in this BWP. If this field is absent when the set(s) of Random Access resources with MSG3 repetition indication are configured in the BWP-UplinkCommon , the UE shall apply the values {n1, n2, n3, n4} (see TS 38.214 [19], clause 6.1.2.1). | +| preambleTransMax-Msg1-Repetition
Max number of transmissions of MSG1 repetitions number (2, 4 and 8) performed before switching to higher repetition number (see TS 38.321 [3], clauses 5.1.1). This field is only applicable when more than one repetition numbers are configured in shared RO. If the field is absent, switching from lower repetition number to higher repetition number is not allowed. | +| pucch-ConfigCommon
Cell specific parameters for the PUCCH of this BWP. | +| pusch-ConfigCommon
Cell specific parameters for the PUSCH of this BWP. | +| rach-ConfigCommon
Configuration of cell specific random access parameters which the UE uses for contention based and contention free random access as well as for contention based beam failure recovery in this BWP. The NW configures SSB-based RA (and hence RACH-ConfigCommon ) only for UL BWPs if the linked DL BWPs (same bwp-Id as UL-BWP) are the initial DL BWPs or DL BWPs containing the SSB associated to the initial DL BWP or DL BWPs associated with nonCellDefiningSSB or, for (e)RedCap UEs, the (e)RedCap-specific initial downlink BWP. The network configures rach-ConfigCommon , whenever it configures contention free random access (for reconfiguration with sync or for beam failure recovery). For (e)RedCap-specific initial uplink BWP, rach-ConfigCommon is always configured when msgA-ConfigCommon is configured in this BWP. | +| rach-ConfigCommonIAB
Configuration of cell specific random access parameters for the IAB-MT. The IAB specific IAB RACH configuration is used by IAB-MT, if configured. | +| rsrp-ThresholdMsg1-RepetitionNum2, rsrp-ThresholdMsg1-RepetitionNum4, rsrp-ThresholdMsg1-RepetitionNum8 | + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Threshold used by the UE for determining whether to select resources indicating Msg1 repetition number 2, 4 or 8 in this BWP, as specified in TS 38.321 [3]. The value applies to all the BWPs and all RACH configurations. This field is mandatory if both set(s) of Random Access resources with MSG1 repetition indication and set(s) of Random Access resources without MSG1 repetition indication are configured in the BWP, or if all set(s) of Random Access resources are configured with MSG1 repetition indication but associated with different repetition numbers in the BWP. It is absent otherwise. | +| rsrp-ThresholdMsg3
Threshold used by the UE for determining whether to select resources indicating Msg3 repetition in this BWP, as specified in TS 38.321 [3]. The field is mandatory if both set(s) of Random Access resources with MSG3 repetition indication and set(s) of Random Access resources without MSG3 repetition indication are configured in the BWP. It is absent otherwise. | +| useInterlacePUCCH-PUSCH
If the field is present, the UE uses uplink frequency domain resource allocation Type 2 for cell-specific PUSCH, e.g., PUSCH scheduled by RAR UL grant (see TS 38.213 [13] clause 8.3 and TS 38.214 [19], clause 6.1.2.2) and uses interlaced PUCCH Format 0 and 1 for cell-specific PUCCH (see TS 38.213 [13], clause 9.2.1). | + +| Conditional Presence | Explanation | +|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Msg1Rep1 | This field is optionally present, Need R, if the set(s) of Random Access resources with MSG1 repetition indication are configured in the BWP-UplinkCommon . It is absent otherwise. | +| Msg3Rep | This field is optionally present, Need S, if the set(s) of Random Access resources with MSG3 repetition indication are configured in the BWP-UplinkCommon . It is absent otherwise. | +| RA-PrioSliceAI | The field is optionally present in SIB1 , Need R, if both parameters ra-PrioritizationForAccessIdentity and the ra-PrioritizationForSlicing/ra-PrioritizationForSlicingTwoStep are present in SIB1 . It is absent otherwise. | +| SpCellOnly2 | The field is optionally present, Need M, in the BWP-UplinkCommon of an SpCell . It is absent otherwise. | +| 2TA-Only | The field is optionally present, Need N in the BWP-UplinkCommon if additionalPCI-ToAddModList is present in spCellConfigDedicated or sCellConfigDedicated and it has the same number of entries as the additionalPCI-ToAddModList . It is absent otherwise. | + +##### – *BWP-UplinkDedicated* + +The IE *BWP-UplinkDedicated* is used to configure the dedicated (UE specific) parameters of an uplink BWP. + +#### *BWP-UplinkDedicated* information element + +``` +-- ASN1START +-- TAG-BWP-UPLINKDEDICATED-START + +BWP-UplinkDedicated ::= SEQUENCE { + pucch-Config SetupRelease { PUCCH-Config } OPTIONAL, -- Need M + pusch-Config SetupRelease { PUSCH-Config } OPTIONAL, -- Need M + configuredGrantConfig SetupRelease { ConfiguredGrantConfig } OPTIONAL, -- Need M + srs-Config SetupRelease { SRS-Config } OPTIONAL, -- Need M + beamFailureRecoveryConfig SetupRelease { BeamFailureRecoveryConfig } OPTIONAL, -- Cond SpCellOnly + ... +} +``` + +``` + + sl-PUCCH-Config-r16 SetupRelease { PUCCH-Config } OPTIONAL, -- Need M + cp-ExtensionC2-r16 INTEGER (1..28) OPTIONAL, -- Need R + cp-ExtensionC3-r16 INTEGER (1..28) OPTIONAL, -- Need R + useInterlacePUCCH-PUSCH-r16 ENUMERATED {enabled} OPTIONAL, -- Need R + pucch-ConfigurationList-r16 SetupRelease { PUCCH-ConfigurationList-r16 } OPTIONAL, -- Need M + lbt-FailureRecoveryConfig-r16 SetupRelease { LBT-FailureRecoveryConfig-r16 } OPTIONAL, -- Need M + configuredGrantConfigToAddModList-r16 ConfiguredGrantConfigToAddModList-r16 OPTIONAL, -- Need N + configuredGrantConfigToReleaseList-r16 ConfiguredGrantConfigToReleaseList-r16 OPTIONAL, -- Need N + configuredGrantConfigType2DeactivationStateList-r16 ConfiguredGrantConfigType2DeactivationStateList-r16 OPTIONAL -- Need R + ]], + [[ + ul-TCI-StateList-r17 CHOICE { + explicitlist SEQUENCE { + ul-TCI-ToAddModList-r17 SEQUENCE (SIZE (1..maxUL-TCI-r17)) OF TCI-UL-State-r17 OPTIONAL, -- Need N + ul-TCI-ToReleaseList-r17 SEQUENCE (SIZE (1..maxUL-TCI-r17)) OF TCI-UL-StateId-r17 OPTIONAL -- Need N + }, + unifiedTCI-StateRef-r17 ServingCellAndBWP-Id-r17 + } OPTIONAL, -- Need R + ul-powerControl-r17 Uplink-powerControlId-r17 OPTIONAL, -- Cond NoTCI-PC + pucch-ConfigurationListMulticast1-r17 SetupRelease { PUCCH-ConfigurationList-r16 } OPTIONAL, -- Need M + pucch-ConfigurationListMulticast2-r17 SetupRelease { PUCCH-ConfigurationList-r16 } OPTIONAL -- Need M + ]], + [[ + pucch-ConfigMulticast1-r17 SetupRelease { PUCCH-Config } OPTIONAL, -- Need M + pucch-ConfigMulticast2-r17 SetupRelease { PUCCH-Config } OPTIONAL -- Need M + ]], + [[ + pathlossReferenceRSToAddModList-r17 SEQUENCE (SIZE (1..maxNrofPathlossReferenceRSs-r17)) OF PathlossReferenceRS-r17 + OPTIONAL, -- Need N + pathlossReferenceRSToReleaseList-r17 SEQUENCE (SIZE (1..maxNrofPathlossReferenceRSs-r17)) OF PathlossReferenceRS-Id-r17 + OPTIONAL -- Need N + ]] +} + +ConfiguredGrantConfigToAddModList-r16 ::= SEQUENCE (SIZE (1..maxNrofConfiguredGrantConfig-r16)) OF ConfiguredGrantConfig + +ConfiguredGrantConfigToReleaseList-r16 ::= SEQUENCE (SIZE (1..maxNrofConfiguredGrantConfig-r16)) OF ConfiguredGrantConfigIndex-r16 + +ConfiguredGrantConfigType2DeactivationState-r16 ::= SEQUENCE (SIZE (1..maxNrofConfiguredGrantConfig-r16)) OF ConfiguredGrantConfigIndex-r16 + +ConfiguredGrantConfigType2DeactivationStateList-r16 ::= + SEQUENCE (SIZE (1..maxNrofCG-Type2DeactivationState)) OF ConfiguredGrantConfigType2DeactivationState-r16 + +-- TAG-BWP-UPLINKDEDICATED-STOP +-- ASN1STOP + +``` + +| BWP-UplinkDedicated field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| beamFailureRecoveryConfig
Configuration of beam failure recovery. If supplementaryUplink is present, the field is present only in one of the uplink carriers, either UL or SUL. | +| configuredGrantConfig
A Configured-Grant of type1 or type2 . It may be configured for UL or SUL but in case of type1 not for both at a time. Except for reconfiguration with sync, the NW does not reconfigure configuredGrantConfig when there is an active configured uplink grant Type 2 (see TS 38.321 [3]). However, the NW may release the configuredGrantConfig at any time. Network can only configure configured grant in one BWP using either this field or configuredGrantConfigToAddModList . | +| configuredGrantConfigToAddModList
Indicates a list of one or more configured grant configurations to be added or modified for one BWP. Except for reconfiguration with sync, the NW does not reconfigure a Type 2 configured grant configuration when it is active (see TS 38.321 [3]). The network configures multiple CG configurations for one BWP with either all configurations or no configuration configured with cgr-RetransmissionTimer-r16 . | +| configuredGrantConfigToReleaseList
Indicates a list of one or more UL Configured Grant configurations to be released. The NW may release a configured grant configuration at any time. | +| configuredGrantConfigType2DeactivationStateList
Indicates a list of the deactivation states in which each state can be mapped to a single or multiple Configured Grant type 2 configurations to be deactivated when the corresponding deactivation DCI is received, see clause 7.3.1 in TS 38.212 [17] and clause 10.2 in TS 38.213 [13]. | +| cp-ExtensionC2, cp-ExtensionC3
Configures the cyclic prefix (CP) extension (see TS 38.211 [16], clause 5.3.1). For 15 kHz SCS, {1..28} are valid for both cp-ExtensionC2 and cp-ExtensionC3 . For 30 kHz SCS, {1..28} are valid for cp-ExtensionC2 and {2..28} are valid for cp-ExtensionC3 . For 60 kHz SCS, {2..28} are valid for cp-ExtensionC2 and {3..28} are valid for cp-ExtensionC3 . | +| lbt-FailureRecoveryConfig
Configures parameters used for detection of consistent uplink LBT failures for operation with shared spectrum channel access, as specified in TS 38.321 [3]. | +| pathlossReferenceRSToAddModList
A list of Reference Signals (e.g. a CSI-RS config or a SS block) to be used for path loss estimation for PUSCH, PUCCH and SRS for unified TCI state operation. If unifiedTCI-StateType is not configured for the serving cell, no element in this list is configured. | +| pucch-Config
PUCCH configuration for one BWP of the normal UL or SUL of a serving cell. If the UE is configured with SUL, the network configures PUCCH only on the BWPs of one of the uplinks (normal UL or SUL). The network configures PUCCH-Config at least on non-initial BWP(s) for SpCell and on all BWP(s) for PUCCH SCell. If supported by the UE, the network may configure at most one additional SCell of a cell group with PUCCH-Config (i.e. PUCCH SCell). If PUCCH cell switching is supported by the UE, the network may configure two TDD serving cells with PUCCH-Config within each PUCCH group. For supporting PUCCH cell switching in the PUCCH group with the SpCell, the TDD SpCell and one TDD SCell shall have PUCCH-Config on their normal UL. For supporting PUCCH cell switching in the PUCCH group with only SCells, two TDD SCells shall have PUCCH-Config on their normal UL.
In (NG)EN-DC and NE-DC, the NW configures at most one serving cell per frequency range with PUCCH. In (NG)EN-DC and NE-DC, if two PUCCH groups are configured, the serving cells of the NR PUCCH group in FR2 use the same numerology. For NR-DC, the maximum number of PUCCH groups in each cell group is one, and only the same numerology is supported for the cell group with carriers only in FR2.
The NW may configure PUCCH for a BWP when setting up the BWP. The network may also add/remove the pucch-Config in an RRCEconfiguration with reconfigurationWithSync (for SpCell or PUCCH SCell) or with SCell release and add (for PUCCH SCell) to move the PUCCH between the UL and SUL carrier of one serving cell. In other cases, only modifications of a previously configured pucch-Config are allowed.
If one (S)UL BWP of a serving cell is configured with PUCCH, all other (S)UL BWPs must be configured with PUCCH, too. | +| pucch-ConfigurationList
PUCCH configurations for two simultaneously constructed HARQ-ACK codebooks (see TS 38.213 [13], clause 9.1). Different PUCCH Resource IDs are configured in different PUCCH-Config within the pucch-ConfigurationList if configured. | +| pucch-ConfigurationListMulticast1
PUCCH configurations for two simultaneously constructed HARQ-ACK codebooks for MBS multicast (see TS 38.213, clause 9). | + +| | | +|------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| pucch-ConfigurationListMulticast2 | PUCCH configurations for two simultaneously constructed NACK-only feedback for MBS multicast (see TS 38.213, clause 9). | +| pusch-Config | PUSCH configuration for one BWP of the normal UL or SUL of a serving cell. If the UE is configured with SUL and if it has a PUSCH-Config for both UL and SUL, an UL/SUL indicator field in DCI indicates which of the two to use. See TS 38.212 [17], clause 7.3.1. | +| pucch-ConfigMulticast1 | PUCCH configuration for the HARQ-ACK codebook for MBS multicast when multicast feedback is not configured with a priority value (see TS 38.213 [13], clause 9). If the field is not configured, pucch-Config applies. | +| pucch-ConfigMulticast2 | PUCCH configuration for the NACK-only feedback for MBS multicast when multicast feedback is not configured with a priority value (see TS 38.213 [13], clause 9). If the field is not configured, pucch-Config applies. | +| sl-PUCCH-Config | Indicates the UE specific PUCCH configurations used for the HARQ-ACK feedback reporting for NR sidelink communication. | +| srs-Config | Uplink sounding reference signal configuration. | +| ul-powerControl | Configures power control parameters for PUCCH, PUSCH and SRS when UE is configured with unifiedTCI-StateType for this serving cell. For each serving cell, ul-powerControl is either configured in all BWP-UplinkDedicated or it is not configured in any BWP-UplinkDedicated . When unifiedTCI-StateRef in the BWP-UplinkDedicated or in the PDSCH-Config if the unifiedTCI-StateType is set to joint , of a serving cell refers to another serving cell, ul-powerControl is either configured in all BWP-UplinkDedicated of these two serving cells or it is not configured in any BWP-UplinkDedicated of these two serving cells. | +| ul-TCI-StateList | Indicates the applicable UL TCI states for PUCCH, PUSCH and SRS. | +| ul-TCI-ToAddModList | Indicates a list of UL TCI states. | +| unifiedTCI-StateRef | Provides the serving cell and UL BWP where UL TCI states applicable to this UL BWP are defined. The value of unifiedTCI-StateType of current serving cell is the same in the serving cell indicated by unifiedTCI-StateRef . | +| useInterlacePUCCH-PUSCH | If the field is present, the UE uses uplink frequency domain resource allocation Type 2 for PUSCH (see TS 38.213 [13], clause 8.3 and TS 38.214 [19], clause 6.1.2.2) and uses interlaced PUCCH Format 0, 1, 2, and 3 for PUCCH (see TS 38.213 [13], clause 9.2.1). | + +| Conditional Presence | Explanation | +|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NoTCI-PC | The field is optionally present, Need R, if unifiedTCI-StateType is configured for this serving cell and ul-powerControl is not configured for any UL TCI state or joint TCI state of this serving cell. Otherwise it is absent, Need R | +| SpCellOnly | The field is optionally present, Need M, in the BWP-UplinkDedicated of an SpCell. It is absent otherwise. | + +NOTE 1: In case of *RRCREconfiguration* with *reconfigurationWithSync*, the UE performs a MAC reset, which involves releasing the PUCCH-CSI/SRS/SR configuration in accordance with clause 5.3.12 and TS 38.321 [3], clauses 5.12 and 5.2. Hence, for these parts of the dedicated radio resource configuration, delta signalling is not supported in the message when *reconfigurationWithSync* is included. + +# — *CandidateBeamRS* + +The IE *CandidateBeamRS* includes candidate beams for beam failure recovery in case of beam failure detection. See also TS 38.321 [3], clause 5.17. + +#### *CandidateBeamRS* information element + +``` +-- ASN1START +-- TAG-CANDIDATEBEAMRS-START + +CandidateBeamRS-r16 ::= SEQUENCE { + candidateBeamConfig-r16 CHOICE { + ssb-r16 SSB-Index, + csi-RS-r16 NZP-CSI-RS-ResourceId + }, + servingCellId ServCellIndex OPTIONAL -- Need R +} + +-- TAG-CANDIDATEBEAMRS-STOP +-- ASN1STOP +``` + +#### *CandidateBeamRS* field descriptions + +| | | +|-----------------------------------|-----------------------------------------------------------------------------------------------------------------------| +| candidateBeamConfig | Indicates the resource (i.e. SSB or CSI-RS) defining this beam resource. | +| servingCellId | If the field is absent, the RS belongs to the serving cell in which BeamFailureRecoveryRSConfig is configured. | + +#### — *CandidateTCI-State* + +The IE *CandidateTCI-State* defines a TCI states configuration which associate one or more reference signal with a corresponding quasi-colocation (QCL) type. + +#### *CandidateTCI-State* information element + +``` +-- ASN1START +-- TAG-CANDIDATETCI-STATE-START + +CandidateTCI-State-r18 ::= SEQUENCE { + tci-StateId-r18 TCI-StateId, + qcl-Type1-r18 LTM-QCL-Info-r18, + qcl-Type2-r18 LTM-QCL-Info-r18 OPTIONAL, -- Need R + pathlossReferenceRS-Id-r18 PathlossReferenceRS-Id-r17 OPTIONAL, -- Need R + ... +} + +LTM-QCL-Info-r18 ::= SEQUENCE { +``` + +``` + +referenceSignal-r18 CHOICE { + ssb-Index SSB-Index, + csi-RS-Index NZP-CSI-RS-ResourceId +}, +qcl-Type-r18 ENUMERATED {typeA, typeB, typeC, typeD}, +... +} + +-- TAG-CANDIDATETCI-STATE-STOP +-- ASN1STOP + +``` + +#### CandidateTCI-State field descriptions + +##### **qcl-Type1, qcl-Type2** + +QCL information for the TCI state. + +##### **referenceSignal** + +Reference signal with which quasi-collocation information is provided. + +##### **tci-StateId** + +The ID number of the TCI state. + +#### — **CandidateTCI-UL-State** + +The IE *CandidateTCI-UL-State* defines an uplink TCI states configuration. + +#### **CandidateTCI-UL-State information element** + +``` + +-- ASN1START +-- TAG-CANDIDATETCI-UL-STATE-START + +CandidateTCI-UL-State-r18 ::= SEQUENCE { + tci-UL-StateId-r18 TCI-UL-StateId-r17, + referenceSignal-r18 CHOICE { + ssb-Index SSB-Index, + csi-RS-Index NZP-CSI-RS-ResourceId + }, + pathlossReferenceRS-Id-r18 PathlossReferenceRS-Id-r17 OPTIONAL, -- Need R + ... +} + +-- TAG-CANDIDATETCI-UL-STATE-STOP +-- ASN1STOP + +``` + +| CandidateTCI-UL-State field descriptions | +|--------------------------------------------------------------------------------------------------| +| referenceSignal
Reference signal with which quasi-collocation information is provided. | +| Tci-UL-StateID
The ID number of the uplink TCI state. | + +#### – *CellAccessRelatedInfo* + +The IE *CellAccessRelatedInfo* indicates cell access related information for this cell. + +#### ***CellAccessRelatedInfo* information element** + +``` +-- ASN1START +-- TAG-CELLACCESSRELATEDINFO-START + +CellAccessRelatedInfo ::= SEQUENCE { + plmn-IdentityInfoList PLMN-IdentityInfoList, + cellReservedForOtherUse ENUMERATED {true} OPTIONAL, -- Need R + ..., + [[ + cellReservedForFutureUse-r16 ENUMERATED {true} OPTIONAL, -- Need R + npn-IdentityInfoList-r16 NPN-IdentityInfoList-r16 OPTIONAL -- Need R + ]], + [[ + snpn-AccessInfoList-r17 SEQUENCE (SIZE (1..maxNPN-r16)) OF SNPN-AccessInfo-r17 OPTIONAL -- Need R + ]] +} + +SNPN-AccessInfo-r17 ::= SEQUENCE { + extCH-Supported-r17 ENUMERATED {true} OPTIONAL, -- Need R + extCH-WithoutConfigAllowed-r17 ENUMERATED {true} OPTIONAL, -- Need R + onboardingEnabled-r17 ENUMERATED {true} OPTIONAL, -- Need R + imsEmergencySupportForSNPN-r17 ENUMERATED {true} OPTIONAL -- Need R +} + +-- TAG-CELLACCESSRELATEDINFO-STOP +-- ASN1STOP +``` + +| CellAccessRelatedInfo field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| cellReservedForFutureUse
Indicates whether the cell is reserved, as defined in 38.304 [20] for future use. The field is applicable to all PLMNs and NPNs. This field is ignored by IAB-MT and NCR-MT. | +| cellReservedForOtherUse
Indicates whether the cell is reserved, as defined in 38.304 [20]. The field is applicable to all PLMNs. This field is ignored by IAB-MT and NCR-MT for cell barring determination, but still considered by NPN capable IAB-MT and NPN capable NCR-MT for determination of an NPN-only cell. | +| npn-IdentityInfoList
The npn-IdentityInfoList is used to configure a set of NPN-IdentityInfo elements. Each of those elements contains a list of one or more NPN Identities and additional information associated with those NPNs. The total number of PLMNs (identified by a PLMN identity in plmn-IdentityList ), PNI-NPNs (identified by a PLMN identity and a CAG-ID), and SNPNs (identified by a PLMN identity and a NID) together in the PLMN-IdentityInfoList and NPN-IdentityInfoList does not exceed 12, except for the NPN-only cells. A PNI-NPN and SNPN can be included only once, and in only one entry of the NPN-IdentityInfoList . In case of NPN-only cells the PLMN-IdentityList contains a single element that does not count to the limit of 12 and the cellIdentity of the first entry of the PLMN-IdentityInfoList is set to the same value as the cellIdentity-r16 of the first entry of the NPN-IdentityInfoList . The NPN index is defined as $B + c_1 + c_2 + \dots + c_{(n-1)} + d_1 + d_2 + \dots + d_{(m-1)} + e_{(i)}$ for the NPN identity included in the n -th entry of NPN-IdentityInfoList and in the m -th entry of npn-IdentityList within that NPN-IdentityInfoList entry, and the i -th entry of its corresponding NPN-Identity , where
  • - B is the index used for the last PLMN in the PLMN-IdentityInfoList; in NPN-only cells B is considered 0;
  • - c(j) is the number of NPN index values used in the j-th NPN-IdentityInfoList entry;
  • - d(k) is the number of NPN index values used in the k-th npn-IdentityList entry within the n-th NPN-IdentityInfoList entry;
  • - e(i) is
    • - i if the n-th entry of NPN-IdentityInfoList entry is for SNPN(s);
    • - 1 if the n-th entry of NPN-IdentityInfoList entry is for PNI-NPN(s).
| +| plmn-IdentityInfoList
The plmn-IdentityInfoList is used to configure a set of PLMN-IdentityInfo elements. Each of those elements contains a list of one or more PLMN Identities and additional information associated with those PLMNs. A PLMN-identity can be included only once, and in only one entry of the PLMN-IdentityInfoList . The PLMN index is defined as $b_1 + b_2 + \dots + b_{(n-1)} + i$ for the PLMN included at the n -th entry of PLMN-IdentityInfoList and the i -th entry of its corresponding PLMN-IdentityInfo , where b(j) is the number of PLMN-Identity entries in each PLMN-IdentityInfo , respectively. | +| snpn-AccessInfoList
This list provides access related information for each SNPN in npn-IdentityInfoList , see TS 23.501 [32]. The n -th entry of the list contains the access related information of the n -th SNPN in npn-IdentityInfoList . | + +| SNPN-AccessInfo field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| extCH-Supported
Indicates whether the SNPN supports access using credentials from a Credentials Holder as specified in TS 23.501 [32]. | +| extCH-WithoutConfigAllowed
Indicates whether the SNPN allows registration attempts with credentials from a Credentials Holder from UEs that are not explicitly configured to select the SNPN as specified in TS 23.501 [32]. | +| imsEmergencySupportForSNPN
Indicates whether the SNPN supports IMS emergency bearer services for UEs in limited service mode in the cell. If absent, IMS emergency call is not supported by the SNPN in the cell for UEs in limited service mode. | +| onboardingEnabled
Indicates whether the onboarding SNPN allows registration for onboarding in the cell as specified in TS 23.501 [32]. | + +#### — *CellAccessRelatedInfo-EUTRA-5GC* + +The IE *CellAccessRelatedInfo-EUTRA-5GC* indicates cell access related information for an LTE cell connected to 5GC. + +#### ***CellAccessRelatedInfo-EUTRA-5GC* information element** + +``` +-- ASN1START +-- TAG-CELLACCESSRELATEDINFOEUTRA-5GC-START + +CellAccessRelatedInfo-EUTRA-5GC ::= SEQUENCE { + plmn-IdentityList-eutra-5gc PLMN-IdentityList-EUTRA-5GC, + trackingAreaCode-eutra-5gc TrackingAreaCode, + ranac-5gc RAN-AreaCode OPTIONAL, + cellIdentity-eutra-5gc CellIdentity-EUTRA-5GC +} + +PLMN-IdentityList-EUTRA-5GC ::= SEQUENCE (SIZE (1..maxPLMN)) OF PLMN-Identity-EUTRA-5GC + +PLMN-Identity-EUTRA-5GC ::= CHOICE { + plmn-Identity-EUTRA-5GC PLMN-Identity, + plmn-index INTEGER (1..maxPLMN) +} + +CellIdentity-EUTRA-5GC ::= CHOICE { + cellIdentity-EUTRA BIT STRING (SIZE (28)), + cellId-index INTEGER (1..maxPLMN) +} + +-- TAG-CELLACCESSRELATEDINFOEUTRA-5GC-STOP +-- ASN1STOP +``` + +#### — *CellAccessRelatedInfo-EUTRA-EPC* + +The IE *CellAccessRelatedInfo-EUTRA-EPC* indicates cell access related information for an LTE cell connected to EPC. + +#### ***CellAccessRelatedInfo-EUTRA-EPC* information element** + +``` +-- ASN1START +-- TAG-CELLACCESSRELATEDINFOEUTRA-EPC-START + +CellAccessRelatedInfo-EUTRA-EPC ::= SEQUENCE { + plmn-IdentityList-eutra-epc PLMN-IdentityList-EUTRA-EPC, + trackingAreaCode-eutra-epc BIT STRING (SIZE (16)), + cellIdentity-eutra-epc BIT STRING (SIZE (28)) +} + +PLMN-IdentityList-EUTRA-EPC ::= SEQUENCE (SIZE (1..maxPLMN)) OF PLMN-Identity +``` + +``` +-- TAG-CELLACCESSRELATEDINFOEUTRA-EPC-STOP +-- ASN1STOP +``` + +### CellDTXDRX-Config + +The IE *CellDTXDRX-Config* is used to configure cell DTX/DRX related parameters. Cell DTX is configured only when C-DRX is configured. + +#### CellDTXDRX-Config information element + +``` +-- ASN1START +-- TAG-CELLDTXDRX-CONFIG-START + +CellDTXDRX-Config-r18 ::= + cellDTXDRX-onDurationTimer-r18 SEQUENCE { + subMilliSeconds INTEGER (1..31), + milliSeconds ENUMERATED { + ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, + ms80, ms100, ms200, ms300, ms400, ms500, ms600, ms800, ms1000, ms1200, + ms1600, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 } + OPTIONAL, -- Need M + } + cellDTXDRX-CycleStartOffset-r18 CHOICE { + ms10 INTEGER (0..9), + ms20 INTEGER (0..19), + ms32 INTEGER (0..31), + ms40 INTEGER (0..39), + ms60 INTEGER (0..59), + ms64 INTEGER (0..63), + ms70 INTEGER (0..69), + ms80 INTEGER (0..79), + ms128 INTEGER (0..127), + ms160 INTEGER (0..159), + ms256 INTEGER (0..255), + ms320 INTEGER (0..319), + ms512 INTEGER (0..511), + ms640 INTEGER (0..639), + ms1024 INTEGER (0..1023), + ms1280 INTEGER (0..1279), + ms2048 INTEGER (0..2047), + ms2560 INTEGER (0..2559), + ms5120 INTEGER (0..5119), + ms10240 INTEGER (0..10239) + } + cellDTXDRX-SlotOffset-r18 INTEGER (0..31) OPTIONAL, -- Need M + cellDTXDRXconfigType-r18 ENUMERATED {dtx, drx, dtxdrx} OPTIONAL, -- Need M + cellDTXDRXactivationStatus-r18 ENUMERATED {activated, deactivated} OPTIONAL, -- Need N +} + +-- TAG-CELLDTXDRX-CONFIG-STOP +-- ASN1STOP +``` + +| CellDTXDRX-Config field descriptions | | +|---------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| cellIDTXDRX-CycleStartOffset | cellIDTXDRX-Cycle in ms and cellIDTXDRX-StartOffset in multiples of 1 ms.
The configured cellIDTXDRX-Cycle is an integer multiple of configured drx-longCycle or vice versa. | +| cellIDTXDRX-onDurationTimer | Value in multiples of 1/32 ms (subMilliSeconds) or in ms (milliSecond). For the latter, value ms1 corresponds to 1 ms, value ms2 corresponds to 2 ms, and so on. | +| cellIDTXDRX-SlotOffset | Value in 1/32 ms. Value 0 corresponds to 0 ms, value 1 corresponds to 1/32 ms, value 2 corresponds to 2/32 ms, and so on. | +| cellIDTXDRXactivationStatus | Initial activation status of cell DTX/DRX indicating whether the UE shall activate the configuration according to the received parameters. This field is only used upon setup of a cell DTX/DRX configuration. | +| cellIDTXDRXconfigType | Indicates whether the configuration is for cell DTX only, cell DRX only, or joint cell DTX/DRX configuration. | + +## CellGroupConfig + +The *CellGroupConfig* IE is used to configure a master cell group (MCG) or secondary cell group (SCG). A cell group comprises of one MAC entity, a set of logical channels with associated RLC entities and of a primary cell (SpCell) and one or more secondary cells (SCells). For an NCR-MT, the *CellGroupConfig* IE is also used to provide the configuration of side control information for the NCR-Fwd access link. + +#### CellGroupConfig information element + +``` +-- ASN1START +-- TAG-CELLGROUPCONFIG-START + +-- Configuration of one Cell-Group: +CellGroupConfig ::= + cellGroupId CellGroupId, + rlc-BearerToAddModList SEQUENCE (SIZE(1..maxLC-ID)) OF RLC-BearerConfig OPTIONAL, -- Need N + rlc-BearerToReleaseList SEQUENCE (SIZE(1..maxLC-ID)) OF LogicalChannelIdentity OPTIONAL, -- Need N + mac-CellGroupConfig MAC-CellGroupConfig OPTIONAL, -- Need M + physicalCellGroupConfig PhysicalCellGroupConfig OPTIONAL, -- Need M + spCellConfig SpCellConfig OPTIONAL, -- Need M + sCellToAddModList SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellConfig OPTIONAL, -- Need N + sCellToReleaseList SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellIndex OPTIONAL, -- Need N + ... + [[ + reportUplinkTxDirectCurrent ENUMERATED {true} OPTIONAL -- Cond BWP-Reconfig + ]], + [[ + bap-Address-r16 BIT STRING (SIZE (10)) OPTIONAL, -- Need M + bh-RLC-ChannelToAddModList-r16 SEQUENCE (SIZE(1..maxBH-RLC-ChannelID-r16)) OF BH-RLC-ChannelConfig-r16 OPTIONAL, -- Need N +``` + +``` + + bh-RLC-ChannelToReleaseList-r16 SEQUENCE (SIZE(1..maxBH-RLC-ChannelID-r16)) OF BH-RLC-ChannelID-r16 OPTIONAL, -- Need N + flc-TransferPath-r16 ENUMERATED {lte, nr, both} OPTIONAL, -- Need M + simultaneousTCI-UpdateList1-r16 SEQUENCE (SIZE (1..maxNrofServingCellsTCI-r16)) OF ServCellIndex OPTIONAL, -- Need R + simultaneousTCI-UpdateList2-r16 SEQUENCE (SIZE (1..maxNrofServingCellsTCI-r16)) OF ServCellIndex OPTIONAL, -- Need R + simultaneousSpatial-UpdatedList1-r16 SEQUENCE (SIZE (1..maxNrofServingCellsTCI-r16)) OF ServCellIndex OPTIONAL, -- Need R + simultaneousSpatial-UpdatedList2-r16 SEQUENCE (SIZE (1..maxNrofServingCellsTCI-r16)) OF ServCellIndex OPTIONAL, -- Need R + uplinkTxSwitchingOption-r16 ENUMERATED {switchedUL, dualUL} OPTIONAL, -- Need R + uplinkTxSwitchingPowerBoosting-r16 ENUMERATED {enabled} OPTIONAL, -- Need R + ]], + [[ + reportUplinkTxDirectCurrentTwoCarrier-r16 ENUMERATED {true} OPTIONAL -- Need N + ]], + [[ + flc-TransferPathNRDC-r17 ENUMERATED {mcg, scg, both} OPTIONAL, -- Need M + uplinkTxSwitching-2T-Mode-r17 ENUMERATED {enabled} OPTIONAL, -- Cond 2Tx + uplinkTxSwitching-DualUL-TxState-r17 ENUMERATED {oneT, twoT} OPTIONAL, -- Cond 2Tx + uu-RelayRLC-ChannelToAddModList-r17 SEQUENCE (SIZE(1..maxUu-RelayRLC-ChannelID-r17)) OF Uu-RelayRLC-ChannelConfig-r17 OPTIONAL, + -- Need N + uu-RelayRLC-ChannelToReleaseList-r17 SEQUENCE (SIZE(1..maxUu-RelayRLC-ChannelID-r17)) OF Uu-RelayRLC-ChannelID-r17 OPTIONAL, + -- Need N + simultaneousU-TCI-UpdateList1-r17 SEQUENCE (SIZE (1..maxNrofServingCellsTCI-r16)) OF ServCellIndex OPTIONAL, -- Need R + simultaneousU-TCI-UpdateList2-r17 SEQUENCE (SIZE (1..maxNrofServingCellsTCI-r16)) OF ServCellIndex OPTIONAL, -- Need R + simultaneousU-TCI-UpdateList3-r17 SEQUENCE (SIZE (1..maxNrofServingCellsTCI-r16)) OF ServCellIndex OPTIONAL, -- Need R + simultaneousU-TCI-UpdateList4-r17 SEQUENCE (SIZE (1..maxNrofServingCellsTCI-r16)) OF ServCellIndex OPTIONAL, -- Need R + rlc-BearerToReleaseListExt-r17 SEQUENCE (SIZE(1..maxLC-ID)) OF LogicalChannelIdentityExt-r17 OPTIONAL, -- Need N + iab-ResourceConfigToAddModList-r17 SEQUENCE (SIZE(1..maxNrofIABResourceConfig-r17)) OF IAB-ResourceConfig-r17 OPTIONAL, -- Need N + iab-ResourceConfigToReleaseList-r17 SEQUENCE (SIZE(1..maxNrofIABResourceConfig-r17)) OF IAB-ResourceConfigID-r17 OPTIONAL -- Need N + ]], + [[ + reportUplinkTxDirectCurrentMoreCarrier-r17 ReportUplinkTxDirectCurrentMoreCarrier-r17 OPTIONAL -- Need N + ]], + [[ + prioSCellPRACH-OverSP-PeriodicSRS-r17 ENUMERATED {enabled} OPTIONAL -- Need R + ]], + [[ + ncr-FwdConfig-r18 SetupRelease { NCR-FwdConfig-r18 } OPTIONAL, -- Cond NCR + autonomousDenialParameters-r18 SetupRelease { AutonomousDenialParameters-r18 } OPTIONAL, -- Need M + nonCollocatedTypeMRDC-r18 ENUMERATED { type1 } OPTIONAL, -- Need R + nonCollocatedTypeNR-CA-r18 ENUMERATED { type1 } OPTIONAL, -- Need R + uplinkTxSwitchingMoreBands-r18 SetupRelease { UplinkTxSwitchingMoreBands-r18 } OPTIONAL -- Need M + ]] +} + +-- Serving cell specific MAC and PHY parameters for a SpCell: +SpCellConfig ::= SEQUENCE { + servCellIndex ServCellIndex OPTIONAL, -- Cond SCG + reconfigurationWithSync ReconfigurationWithSync OPTIONAL, -- Cond ReconfWithSync + rlf-TimersAndConstants SetupRelease { RLF-TimersAndConstants } OPTIONAL, -- Need M + rlmInSyncOutOfSyncThreshold ENUMERATED {n1} OPTIONAL, -- Need S + spCellConfigDedicated ServingCellConfig OPTIONAL, -- Need M + ... +} + +``` + +``` + +[[ + lowMobilityEvaluationConnected-r17 SEQUENCE { + s-SearchDeltaP-Connected-r17 ENUMERATED {dB3, dB6, dB9, dB12, dB15, spare3, spare2, spare1}, + t-SearchDeltaP-Connected-r17 ENUMERATED {s5, s10, s20, s30, s60, s120, s180, s240, s300, spare7, spare6, spare5, + spare4, spare3, spare2, spare1} + } OPTIONAL, -- Need R + goodServingCellEvaluationRLM-r17 GoodServingCellEvaluation-r17 OPTIONAL, -- Need R + goodServingCellEvaluationBFD-r17 GoodServingCellEvaluation-r17 OPTIONAL, -- Need R + deactivatedSCG-Config-r17 SetupRelease { DeactivatedSCG-Config-r17 } OPTIONAL, -- Cond SCG-Opt +]] +} + +ReconfigurationWithSync ::= SEQUENCE { + spCellConfigCommon ServingCellConfigCommon OPTIONAL, -- Need M + newUE-Identity RNTI-Value, + t304 ENUMERATED {ms50, ms100, ms150, ms200, ms500, ms1000, ms2000, ms10000}, + rach-ConfigDedicated CHOICE { + uplink RACH-ConfigDedicated, + supplementaryUplink RACH-ConfigDedicated + } OPTIONAL, -- Need N + ..., + [[ + smtc SSB-MTC OPTIONAL, -- Need S + ]], + [[ + daps-UplinkPowerConfig-r16 DAPS-UplinkPowerConfig-r16 OPTIONAL, -- Need N + ]], + [[ + sl-PathSwitchConfig-r17 SL-PathSwitchConfig-r17 OPTIONAL, -- Cond DirectToIndirect-PathSwitch + ]], + [[ + rach-LessHO-r18 RACH-LessHO-r18 OPTIONAL, -- Need N + ]] +} + +DAPS-UplinkPowerConfig-r16 ::= SEQUENCE { + p-DAPS-Source-r16 P-Max, + p-DAPS-Target-r16 P-Max, + uplinkPowerSharingDAPS-Mode-r16 ENUMERATED {semi-static-model, semi-static-mode2, dynamic } +} + +SCellConfig ::= SEQUENCE { + sCellIndex SCellIndex, + sCellConfigCommon ServingCellConfigCommon OPTIONAL, -- Cond SCellAdd + sCellConfigDedicated ServingCellConfig OPTIONAL, -- Cond SCellAddMod + ..., + [[ + smtc SSB-MTC OPTIONAL, -- Need S + ]], + [[ + sCellState-r16 ENUMERATED {activated} OPTIONAL, -- Cond SCellAddSync + ]] +} + +``` + +``` + +secondaryDRX-GroupConfig-r16 ENUMERATED {true} OPTIONAL -- Need S +], +[[ +preConfGapStatus-r17 BIT STRING (SIZE (maxNrofGapId-r17)) OPTIONAL, -- Cond PreConfigMG +goodServingCellEvaluationBFD-r17 GoodServingCellEvaluation-r17 OPTIONAL, -- Need R +sCellSIB20-r17 SetupRelease { SCellSIB20-r17 } OPTIONAL -- Need M +], +[[ +plmn-IdentityInfoList-r17 SetupRelease {PLMN-IdentityInfoList} OPTIONAL, -- Cond SCellSIB20-Opt +npn-IdentityInfoList-r17 SetupRelease {NPN-IdentityInfoList-r16} OPTIONAL -- Cond SCellSIB20-Opt +]] +} + +SCellSIB20-r17 ::= OCTET STRING (CONTAINING SystemInformation) + +DeactivatedSCG-Config-r17 ::= SEQUENCE { + bfd-and-RLM-r17 BOOLEAN, + ... +} + +GoodServingCellEvaluation-r17 ::= SEQUENCE { + offset-r17 ENUMERATED {db2, db4, db6, db8} OPTIONAL -- Need S +} + +SL-PathSwitchConfig-r17 ::= SEQUENCE { + targetRelayUE-Identity-r17 SL-SourceIdentity-r17, + t420-r17 ENUMERATED {ms50, ms100, ms150, ms200, ms500, ms1000, ms2000, ms10000}, + ... +} + +IAB-ResourceConfig-r17 ::= SEQUENCE { + iab-ResourceConfigID-r17 IAB-ResourceConfigID-r17, + slotList-r17 SEQUENCE (SIZE (1..5120)) OF INTEGER (0..5119) OPTIONAL, -- Need M + periodicitySlotList-r17 ENUMERATED {ms0p5, ms0p625, ms1, ms1p25, ms2, ms2p5, ms5, ms10, ms20, ms40, ms80, ms160} OPTIONAL, -- Need M + slotListSubcarrierSpacing-r17 SubcarrierSpacing OPTIONAL, -- Need M + ... +} + +IAB-ResourceConfigID-r17 ::= INTEGER(0..maxNrofIABResourceConfig-1-r17) + +ReportUplinkTxDirectCurrentMoreCarrier-r17 ::= SEQUENCE (SIZE(1.. maxSimultaneousBands)) OF IntraBandCC-CombinationReqList-r17 + +IntraBandCC-CombinationReqList-r17 ::= SEQUENCE { + servCellIndexList-r17 SEQUENCE (SIZE(1.. maxNrofServingCells)) OF ServCellIndex, + cc-CombinationList-r17 SEQUENCE (SIZE(1.. maxNrofReqComDC-Location-r17)) OF IntraBandCC-Combination-r17 +} + +IntraBandCC-Combination-r17 ::= SEQUENCE (SIZE(1.. maxNrofServingCells)) OF CC-State-r17 + +CC-State-r17 ::= SEQUENCE { + dlCarrier-r17 CarrierState-r17 OPTIONAL, -- Need N +} + +``` + +``` + +ulCarrier-r17 CarrierState-r17 OPTIONAL -- Need N +} + +CarrierState-r17 ::= CHOICE { + deActivated-r17 NULL, + activeBWP-r17 INTEGER (0..maxNrofBWPs) +} + +AutonomousDenialParameters-r18 ::= SEQUENCE { + autonomousDenialSlots-r18 ENUMERATED {n2, n5, n10, n15, n20, n30}, + autonomousDenialValidity-r18 ENUMERATED {n200, n500, n1000, n2000} +} + +RACH-LessHO-r18 ::= SEQUENCE { + targetNTA-r18 ENUMERATED {zero, source} OPTIONAL, -- Need R + tci-StateID-r18 TCI-StateId OPTIONAL, -- Cond MobileIAB + dg-beam-r18 SSB-Index OPTIONAL, -- Cond DG-RACH-LessHO + ... +} + +UplinkTxSwitchingMoreBands-r18 ::= SEQUENCE { + uplinkTxSwitchingBandList-r18 SEQUENCE (SIZE (1..maxSimultaneousBands)) OF FreqBandIndicatorNR OPTIONAL, -- Need M + uplinkTxSwitchingBandPairList-r18 UplinkTxSwitchingBandPairList-r18 OPTIONAL, -- Need M + uplinkTxSwitchingAssociatedBandDualUL-List-r18 UplinkTxSwitchingAssociatedBandDualUL-List-r18 OPTIONAL, -- Need M + ... +} + +UplinkTxSwitchingBandPairList-r18 ::= SEQUENCE (SIZE (1.. maxULTxSwitchingBandPairs)) OF UplinkTxSwitchingBandPairConfig-r18 + +UplinkTxSwitchingBandPairConfig-r18 ::= SEQUENCE { + bandInfoUL1-r18 UplinkTxSwitchingBandIndex-r18, + bandInfoUL2-r18 UplinkTxSwitchingBandIndex-r18, + switchingOptionConfigForBandPair-r18 ENUMERATED {switchedUL, dualUL}, + switching2T-Mode-r18 ENUMERATED {enabled} OPTIONAL, -- Need R + ... +} + +UplinkTxSwitchingAssociatedBandDualUL-List-r18 ::= SEQUENCE (SIZE (0..maxSimultaneousBands)) OF UplinkTxSwitchingAssociatedBandDualUL-r18 + +UplinkTxSwitchingAssociatedBandDualUL-r18 ::= SEQUENCE { + transmitBand-r18 UplinkTxSwitchingBandIndex-r18, + associatedBand-r18 UplinkTxSwitchingBandIndex-r18 +} + +UplinkTxSwitchingBandIndex-r18 ::= INTEGER (1..maxSimultaneousBands) + +-- TAG-CELLGROUPCONFIG-STOP +-- ASN1STOP + +``` + +| AutonomousDenialParamters field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| autonomousDenialSlots
Indicates the maximum number of the UL slots for which the UE is allowed to deny any UL transmission. Value n2 corresponds to 2 slots, value n5 to 5 slots and so on. | +| autonomousDenialValidity
Indicates the validity period over which the UL autonomous denial slots shall be counted. Value n200 corresponds to 200 slots, value n500 corresponds to 500 slots and so on. | + +| CC-State field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------| +| dlCarrier
Indicates DL carrier activation state for this carrier and the related active BWP Index, if activated. | +| ulCarrier
Indicates UL carrier activation state for this carrier and the related active BWP Index, if activated. | + +| CellGroupConfig field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| bap-Address
BAP address of the parent node in cell group. | +| bh-RLC-ChannelToAddModList
Configuration of the backhaul RLC entities and the corresponding MAC Logical Channels to be added and modified. | +| bh-RLC-ChannelToReleaseList
List of the backhaul RLC entities and the corresponding MAC Logical Channels to be released. | +| f1c-TransferPath
The F1-C transfer path that an EN-DC IAB-MT should use for transferring F1-C packets to the IAB-donor-CU. If IAB-MT is configured with lte , IAB-MT can only use LTE leg for F1-C transfer. If IAB-MT is configured with nr , IAB-MT can only use NR leg for F1-C transfer. If IAB-MT is configured with both , it is up to IAB-MT to select an LTE leg or a NR leg for F1-C transfer. If the field is not configured, the IAB node uses the NR leg as the default one. | +| f1c-TransferPathNRDC
The F1-C transfer path that an NR-DC IAB-MT should use for transferring F1-C packets to the IAB-donor-CU. If IAB-MT is configured with mcg , IAB-MT can only use the MCG for F1-C transfer. If IAB-MT is configured with scg , IAB-MT can only use the SCG for F1-C transfer. If IAB-MT is configured with both , it is up to IAB-MT to select the MCG or the SCG for F1-C transfer. | +| mac-CellGroupConfig
MAC parameters applicable for the entire cell group. | +| ncr-FwdConfig
Configuration of side control information for the NCR-Fwd access link. | +| nonCollocatedTypeMRDC
This field is only present for a UE configured with maxMIMO-Layers with value less than or equal to 2 for all corresponding serving cells, in case of TDD-TDD inter-band (NG) EN-DC with overlapping or partially overlapping bands. If this field is present, the UE applies (NG)EN-DC MTTD/MRTD according to clause 7.5.3/7.6.3 in TS 38.133 [14] and inter-band RF requirements. If this field is absent, the UE applies (NG)EN-DC MTTD/MRTD according to clause 7.5.2/7.6.2 in TS 38.133 [14] and inter-band RF requirements. | +| nonCollocatedTypeNR-CA
This field is only present for a UE configured with maxMIMO-Layers with value less than or equal to 2 for all corresponding serving cells, in case of TDD-TDD intra-band NR-CA. If this field is present, the UE applies MRTD according to Table 7.6.4-1 in TS 38.133 [14] and UE RF requirements for intra-band NR-CA except for 7.10A in TS 38.101-1 [15]. If this field is absent, the UE applies MTTD/MRTD requirements according to Table 7.5.4-1/Table 7.6.4-2 in TS 38.133 [14] and UE RF requirements for intra-band non-collocated NR-CA including 7.10A in TS 38.101-1 [15]. | +| npn-IdentityInfoList
This field is used to transfer npn-IdentityInfoList in SIB1 of the SCell. The UE uses this field to translate the plmn-Index in MCCH of SCell to SNPn Identity. If this field and plmn-IdentityInfoList are both absent, the UE uses the npn-IdentityInfoList in SIB1 of the PCell. | +| plmn-IdentityInfoList
This field is used to transfer plmn-IdentityInfoList in SIB1 of the SCell. The UE uses this field to translate the plmn-Index in MCCH of SCell to PLMN Identity. If this field and npn-IdentityInfoList are both absent, the UE uses the plmn-IdentityInfoList in SIB1 of the PCell. | +| prioSCellPRACH-OverSP-PeriodicSRS
When configured, the UE applies UL power control prioritization by prioritizing PRACH transmission on SCell over semi-persistent and/or periodic SRS transmission as defined in clause 7.5 of TS 38.213 [13]. | +| rlc-BearerToAddModList
Configuration of the MAC Logical Channel, the corresponding RLC entities and association with radio bearers. | +| reportUplinkTxDirectCurrent
Enables reporting of uplink and supplementary uplink Direct Current location information upon BWP configuration and reconfiguration. This field is only present when the BWP configuration is modified or any serving cell is added or removed. This field is absent in the IE CellGroupConfig when provided as part of RRCSetup message. If UE is configured with SUL carrier, UE reports both UL and SUL Direct Current locations. | +| reportUplinkTxDirectCurrentMoreCarrier | + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Enables reporting of uplink Direct Current location information when the UE is configured with intra-band CA. This field is absent in the IE CellGroupConfig when provided as part of RRCSsetup message. The UE only reports the uplink Direct Current location information that are related to the indicated cc-CombinationList . The network does not include carriers which locate in DL only spectrum described in TS 38.101-2 [39], clause 5.3A.4 and defined by Fsd according to Table 5.3A.4-3 in FR2 in the IntraBandCC-CombinationReqlList . I.e. DL-only carrier in FR2 frequency spectrum is not used to calculate the default DC location. | +| reportUplinkTxDirectCurrentTwoCarrier
Enables reporting of uplink Direct Current location information when the UE is configured with uplink intra-band CA with two carriers. This field is absent in the IE CellGroupConfig when provided as part of RRCSsetup message. | +| rlc-BearerToReleaseListExt
List of the RLC entities and the corresponding MAC Logical Channels to be released for multicast MRBs. | +| rlmInSyncOutOfSyncThreshold
BLER threshold pair index for IS/OOS indication generation, see TS 38.133 [14], table 8.1.1-1. n1 corresponds to the value 1. When the field is absent, the UE applies the value 0. Whenever this is reconfigured, UE resets N310 and N311, and stops T310, if running. Network does not include this field. | +| sCellSIB20
This field is used to transfer SIB20 of the SCell in order to allow the UE for MBS broadcast reception on SCell. The network configures this field only for a single SCell at a time. | +| sCellToAddModList
List of secondary serving cells (SCells) to be added or modified. | +| sCellToReleaseList
List of secondary serving cells (SCells) to be released. | +| simultaneousSpatial-UpdatedList1, simultaneousSpatial-UpdatedList2
List of serving cells which can be updated simultaneously for spatial relation with a MAC CE. The simultaneousSpatial-UpdatedList1 and simultaneousSpatial-UpdatedList2 shall not contain same serving cells. Network should not configure serving cells that are configured with a BWP with two different values for the coresetPoolIndex in these lists. | +| simultaneousTCI-UpdateList1, simultaneousTCI-UpdateList2
List of serving cells which can be updated simultaneously for TCI relation with a MAC CE. The simultaneousTCI-UpdateList1 and simultaneousTCI-UpdateList2 shall not contain same serving cells. Network should not configure serving cells that are configured with a BWP with two different values for the coresetPoolIndex in these lists. | +| simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3, simultaneousU-TCI-UpdateList4
List of serving cells for which the Unified TCI States Activation/Deactivation MAC CE applies simultaneously, as specified in TS 38.321 [3] clause 6.1.3.47. The different lists shall not contain same serving cells. Network only configures in these lists serving cells that are configured with unifiedTCI-StateType . Network should not configure serving cells that are configured with a BWP with different number of coresetPoolIndexes in these lists. | +| spCellConfig
Parameters for the SpCell of this cell group (PCell of MCG or PSCell of SCG). | +| uplinkTxSwitchingOption
Indicates which option is configured for dynamic UL Tx switching for inter-band UL CA or (NG)EN-DC. The field is set to switchedUL if network configures option 1 as specified in TS 38.214 [19], or dualUL if network configures option 2 as specified in TS 38.214 [19]. Network always configures UE with a value for this field in inter-band UL CA case and (NG)EN-DC case where UE supports dynamic UL Tx switching. | +| uplinkTxSwitchingPowerBoosting
Indicates whether the UE is allowed to enable 3dB boosting on the maximum output power for transmission on carrier2 under the operation state in which 2-port transmission can be supported on carrier2 for inter-band UL CA case with dynamic UL Tx switching as defined in TS 38.101-1 [15]. Network can only configure this field for dynamic UL Tx switching in inter-band UL CA case with power Class 3 as defined in TS 38.101-1 [15]. | +| uplinkTxSwitching-2T-Mode
Indicates 2Tx-2Tx switching mode is configured for inter-band UL CA or SUL, in which the switching gap duration for a triggered uplink switching (as specified in TS 38.214 [19]) is equal to the switching time capability value reported for the switching mode.
If this field is absent and uplinkTxSwitching is configured, it is interpreted that 1Tx-2Tx UL Tx switching is configured as specified in TS 38.214 [19]. In this case, there is one uplink (or one uplink band in case of intra-band) configured with uplinkTxSwitching , on which the maximum number of antenna ports among all configured P-SRS/A-SRS and | + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| activated SP-SRS resources should be 1 and non-codebook based UL MIMO is not configured. | +| uplinkTxSwitching-DualUL-TxState
Indicates the state of Tx chains if the state of Tx chains after the UL Tx switching is not unique (as specified in TS 38.214 [19]) in case of 2Tx-2Tx switching is configured and uplinkTxSwitchingOption is set to dualUL . Value oneT indicates 1Tx is assumed to be supported on the carriers on each band, value twoT indicates 2Tx is assumed to be supported on that carrier.
This field applies for all band pairs if uplinkTxSwitchingMoreBands is configured. | +| uplinkTxSwitchingMoreBands
Indicates UL band list, band pair list and other configurations for ULTx switching. | +| uu-RelayRLC-ChannelToAddModList
List of the Uu RLC entities and the corresponding MAC Logical Channels to be added or modified. | +| uu-RelayRLC-ChannelToReleaseList
List of the Uu RLC entities and the corresponding MAC Logical Channels to be released. | + +| DeactivatedSCG-Config field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| bfd-and-RLM
If the field is set to true , the UE shall perform RLM and BFD on the PSCell when the SCG is deactivated and the network ensures that beamFailure-r17 is not configured in the radioLinkMonitoringConfig of the DL BWP of the PSCell in which the UE performs BFD. If set to false , the UE is not required to perform RLM and BFD on the PSCell when the SCG is deactivated. | + +| DAPS-UplinkPowerConfig field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------| +| p-DAPS-Source
The maximum total transmit power to be used by the UE in the source cell group during DAPS handover. | +| p-DAPS-Target
The maximum total transmit power to be used by the UE in the target cell group during DAPS handover. | +| uplinkPowerSharingDAPS-Mode
Indicates the uplink power sharing mode that the UE uses in DAPS handover (see TS 38.213 [13]). | + +| GoodServingCellEvaluation field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| offset
The parameter "X" (dB) for the good serving cell quality criterion in RRC_CONNECTED, for a cell operating in FR1 and FR2, respectively. If this field is absent, the UE applies the (default) value of 0 dB for "X". | + +| IAB-ResourceConfig field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| iab-ResourceConfigID
This ID is used to indicate the specific resource configuration addressed by the MAC CEs specified in TS 38.321 [3]. | +| periodicitySlotList
Indicates the periodicity in ms of the list of slot indexes indicated in slotList . | +| slotList
Indicates the list of slot indexes to which the information indicated in the specific MAC CE applies to, as specified in TS 38.321 [3]. The values of the entries in the slotList are strictly less than the value of the periodicitySlotList . | +| slotListSubcarrierSpacing
Subcarrier spacing used as reference for the slotList configuration.
Only the following values are applicable depending on the used frequency:
FR1: 15 or 30 kHz
FR2-1: 60 or 120 kHz
FR2-2: 120 or 480 kHz | + +| RACH-LessHO field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| dg-beam
This field indicates a beam that the UE should use in the target cell to monitor PDCCH for initial uplink transmission, see TS 38.321 [3]. | +| targetNTA
This field refers to the timing adjustment, see TS 38.213 [13] and TS 38.321 [3], indicating the $N_{TA}$ value which the UE shall use for the target PTAG of handover. Only value source is configured by the network in case source cell is a mobile IAB cell. | +| tc1-StateID
This field indicates a beam that the UE should use in the target cell to monitor PDCCH for initial uplink transmission. This field is always present in case this cell is a mobile IAB cell. | + +| ReconfigurationWithSync field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| rach-ConfigDedicated
Random access configuration to be used for the reconfiguration with sync (e.g. handover). The UE performs the RA according to these parameters in the firstActiveUplinkBWP (see UplinkConfig ). | +| smtc
The SSB periodicity/offset/duration configuration of target cell for NR PSCell change and NR PCell change. The network sets the periodicityAndOffset to indicate the same periodicity as ssb-periodicityServingCell in spCellConfigCommon or sets to the same periodicity as ssb-Periodicity-r17 in nonCellDefiningSSB-r17 if the first active DL BWP included in this RRC message is configured with nonCellDefiningSSB-r17 .
For case of NR PCell change, the smtc is based on the timing reference of (source) PCell. For case of NR PSCell change, it is based on the timing reference of source PSCell. If both this field and targetCellSMTC-SCG are absent, the UE uses the SMTC in the measObjectNR having the same SSB frequency and subcarrier spacing, as configured before the reception of the RRC message. If the first active DL BWP included in this RRC message is configured with nonCellDefiningSSB-r17 , this field corresponds to the NCD-SSB indicated by nonCellDefiningSSB-r17 , otherwise, this field corresponds to the CD-SSB indicated by absoluteFrequencySSB in frequencyInfoDL . | + +| ReportUplinkTxDirectCurrentMoreCarrier field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IntraBandCC-Combination
Indicates the state of the carriers and BWPs indexes of the carriers in a CC combination, each carrier in this combination corresponds to an entry in servCellIndexList with same order. This IE shall have the same size as servCellIndexList . | +| IntraBandCC-CombinationReqList
Indicates the list of the requested carriers/BWPs combinations for an intra-band CA component. | +| servCellIndexList
indicates the list of cell index for an intra-band CA component. | + +| SCellConfig field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| goodServingCellEvaluationBFD
Indicates the criterion for a UE to detect the good serving cell quality for BFD relaxation in an SCell in RRC_CONNECTED. This field is always configured when the network enables BFD relaxation for the UE in this SCell. This field is absent if failureDetectionSetN is present for the SCell. | +| preConfGapStatus
Indicates whether the pre-configured measurement gaps (i.e. the gaps configured with preConfigInd ) are activated or deactivated while this SCell is deactivated. If this field is configured, the UE shall apply network-controlled mechanism for activation and deactivation of the pre-configured measurement gaps, otherwise the UE shall apply the autonomous activation/deactivation mechanism, as specified in TS 38.133 [14]. The first/leftmost bit corresponds to the measurement gap with gap ID 1, the second bit corresponds to measurement gap with gap ID 2, and so on. Value 0 indicates that the corresponding pre-configured measurement gap is deactivated while value 1 indicates that the corresponding pre-configured measurement gap is activated. The UE shall ignore the bit if the corresponding measurement gap is not a pre-configured measurement gap. | +| sCellState
Indicates whether the SCell shall be considered to be in activated state upon SCell configuration. If the field is included for an SCell configured with TRS for fast activation of the SCell, such TRS is not used for the corresponding SCell. | +| secondaryDRX-GroupConfig
The field is used to indicate whether the SCell belongs to the secondary DRX group. All serving cells in the secondary DRX group shall belong to one Frequency Range and all serving cells in the default DRX group shall belong to another Frequency Range. If drx-ConfigSecondaryGroup is configured, the field is optionally present. The network always includes the field if the field was previously configured for this SCell and the SCell remains in the secondary DRX group. Removal of an individual SCell from the secondary DRX group is supported by using an SCell release and addition. Otherwise, if drx-ConfigSecondaryGroup is not configured, the field is absent and the UE shall release the field. The UE shall also release the field if drx-ConfigSecondaryGroup is released without including sCellToAddModList . | +| smtc
The SSB periodicity/offset/duration configuration of target cell for NR SCell addition. The network sets the periodicityAndOffset to indicate the same periodicity as ssb-periodicityServingCell in sCellConfigCommon . The smtc is based on the timing of the SpCell of associated cell group. In case of inter-RAT handover to NR, the timing reference is the NR PCell. In case of intra-NR PCell change (standalone NR) or NR PSCell change (EN-DC), the timing reference is the target SpCell. If the field is absent, the UE uses the SMTC in the measObjectNR having the same SSB frequency and subcarrier spacing, as configured before the reception of the RRC message. | + +| SpCellConfig field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| deactivatedSCG-Config
Configuration applicable when the SCG is deactivated. The network always configures this field before or when indicating that the SCG is deactivated in an RRCReconfiguration , RRCRResume , E-UTRA RRConnectionReconfiguration or E-UTRA RRConnectionResume message. | +| goodServingCellEvaluationBFD
Indicates the criterion for a UE to detect the good serving cell quality for BFD relaxation in the SpCell in RRC_CONNECTED. The field is always configured when the network enables BFD relaxation for the UE in this SpCell. This field is absent if failureDetectionSetN is present for the SpCell. | +| goodServingCellEvaluationRLM
Indicates the criterion for a UE to detect the good serving cell quality for RLM relaxation in the SpCell in RRC_CONNECTED. The field is always configured when the network enables RLM relaxation for the UE in this SpCell. | +| lowMobilityEvaluationConnected
Indicates the criterion for a UE to detect low mobility in RRC_CONNECTED in an SpCell. The s-SearchDeltaP-Connected is the parameter " SSearchDeltaP-connected ". Value dB3 corresponds to 3 dB, dB6 corresponds to 6 dB and so on. The t-SearchDeltaP-Connected is the parameter " TSearchDeltaP-Connected ". Value s5 means 5 seconds, value s10 means 10 seconds and so on. Low mobility criterion is configured in NR PCell for the case of NR SA/ NR CA/ NE-DC/NR-DC, and in the NR PSCell for the case of EN-DC. | +| reconfigurationWithSync
Parameters for the synchronous reconfiguration to the target SpCell. | +| rlf-TimersAndConstants
Timers and constants for detecting and triggering cell-level radio link failure. For the SCG, rlf-TimersAndConstants can only be set to setup and is always included at SCG addition. | +| servCellIndex
Serving cell ID of a PSCell. The PCell of the Master Cell Group uses ID = 0. | + +| SL-PathSwitchConfig field descriptions | +|---------------------------------------------------------------------------------------------------------------| +| targetRelayUE-Identity
Indicates the L2 source ID of the target L2 U2N Relay UE during path switch. | +| t420
Indicates the timer value of T420 to be used during path switch. | + +| UplinkTxSwitchingMoreBands field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| uplinkTxSwitchingBandList
Indicates the NR frequency band number of the UL bands for UL Tx switching. If the UE needs to determine location of switching period as specified in TS 38.101-1 [15], the UE considers that the bands are listed in decreasing order of priority, i.e. the first/leftmost entry corresponds to the band with the highest priority, the next entry corresponds to the band with the second highest priority, and so on. The last entry corresponds the band with the lowest priority. | +| uplinkTxSwitchingBandPairList
Indicates the band pairs involved in UL Tx switching, as well as the per band pair configurations. | +| uplinkTxSwitchingAssociatedBandDualUL-List
Indicates the associated band for transmitting band(s) as specified in TS 38.214 [19], clause 6.16. The network ensures that each band pair of a transmitting band and an associated band supports the dualUL switching option. | +| UplinkTxSwitchingBandIndex
The value n indicates the band included at the n -th entry of uplinkTxSwitchingBandList . | + +| UplinkTxSwitchingBandPairConfig field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| bandInfoUL1, bandInfoUL2
Indicates the band index for a band pair. The value n indicates the band included at the n-th entry of uplinkTxSwitchingBandList . | +| switching2T-Mode
Indicates 2Tx-2Tx switching mode is configured to the band pair, and the switching gap duration for a triggered uplink switching (as specified in TS 38.214 [19]) within the band pair is equal to the value reported in switchingPeriodFor2T (i.e. 2Tx-2Tx switching period).
If this field is absent when uplink Tx switching is configured, it is interpreted that 1Tx-2Tx/1Tx-1Tx UL Tx switching is configured as specified in TS 38.214 [19]. In this case, the value reported in switchingPeriodFor1T (i.e. 1Tx-2Tx/1Tx-1Tx switching period) is applied to the band pair(s). | +| switchingOptionConfigForBandPair
Indicates the switching option for the band pair as specified in TS 38.214 [19], clause 6.16. | + +| Conditional Presence | Explanation | +|------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 2Tx | The field is optionally present, Need R, if uplinkTxSwitching is configured; otherwise it is absent, Need R. | +| BWP-Reconfig | The field is optionally present, Need N, if the BWPs are reconfigured or if serving cells are added or removed. Otherwise it is absent. | +| DG-RACH-LessHO | The field is mandatory present when dynamic grant is used for initial uplink transmission in RACH-less handover in NTN. Otherwise, it is absent, Need R. | +| DirectToIndirect-PathSwitch | The field is mandatory present for the L2 U2N remote UE at path switch to the target L2 U2N Relay UE (including direct to indirect path switch and indirect to indirect path switch). It is absent otherwise.
Note: the target L2 U2N Relay UE should not be the same as serving L2 U2N Relay UE for inter-gNB indirect to indirect path switch. | +| MobileIAB | The field is optionally present in case mobileIAB-Cell is broadcasted in SIB1 . Otherwise, it is absent, Need N. | +| NCR | The field is optionally present, Need M, for NCR-MT. It is absent otherwise. | +| PreConfigMG | The field is optionally present, Need R, if there is at least one per UE gap configured with preConfigInd or there is at least one per FR gap of the same FR which the SCell belongs to and configured with preConfigInd . It is absent, Need R, otherwise. | +| ReconfWithSync | The field is mandatory present in the RRCREconfiguration message:
  • - in each configured CellGroupConfig for which the SpCell changes,
  • - in the masterCellGroup:
    • - at change of AS security key derived from K_{gNB},
    • - in an RRCREconfiguration message contained in a DLInformationTransferMRDC message,
    • - path switch of L2 U2N remote UE to the target PCell,
    • - path switch of L2 U2N remote UE to the target L2 U2N Relay UE,
  • - in the secondaryCellGroup at:
    • - PSCell addition,
    • - SCG resume with NR-DC or (NG)EN-DC,
    • - update of required SI for PSCell,
    • - change of AS security key derived from S-K_{gNB} in NR-DC while the UE is configured with at least one radio bearer with keyToUse set to secondary and that is not released by this RRCREconfiguration message,
    • - MN handover in (NG)EN-DC.
Otherwise, it is optionally present, need M. The field is absent in the masterCellGroup in RRCResume and RRCSsetup messages and is absent in the masterCellGroup in RRCREconfiguration messages if source configuration is not released during DAPS handover. | +| SCellAdd | The field is mandatory present upon SCell addition; otherwise it is absent, Need M. | +| SCellAddMod | The field is mandatory present upon SCell addition; otherwise it is optionally present, need M. | +| SCellAddSync | The field is optionally present, Need N:
  • - in the masterCellGroup at
    • - SCell addition,
    • - reconfiguration with sync,
    • - resume of an RRC connection.
  • - in the secondaryCellGroup, when the SCG is not indicated as deactivated at:
    • - SCG activation while the SCG was previously deactivated,
    • - SCell addition,
    • - reconfiguration with sync.
It is absent otherwise. | + +| | | +|-----------------------|-----------------------------------------------------------------------------------------------------------------| +| SCG | The field is mandatory present in an SpCellConfig for the PSCell. It is absent otherwise. | +| SCellSIB20-Opt | This field is optionally present, Need M, if the field sCellSIB20 is configured. It is absent otherwise. | +| SCG-Opt | The field is optionally present, Need M, in an SpCellConfig for the PSCell. It is absent otherwise. | + +NOTE: In case of change of AS security key derived from $S-K_{\text{gNB}}/S-K_{\text{eNB}}$ , if *reconfigurationWithSync* is not included in the *masterCellGroup*, the network releases all existing MCG RLC bearers associated with a radio bearer with *keyToUse* set to *secondary*. In case of change of AS security key derived from $K_{\text{gNB}}/K_{\text{eNB}}$ , if *reconfigurationWithSync* is not included in the *secondaryCellGroup*, the network releases all existing SCG RLC bearers associated with a radio bearer with *keyToUse* set to *primary*. + +#### — *CellGroupId* + +The IE *CellGroupId* is used to identify a cell group. Value 0 identifies the master cell group. Other values identify secondary cell groups. In this version of the specification only values 0 and 1 are supported. + +#### *CellGroupId* information element + +``` +-- ASN1START +-- TAG-CELLGROUPID-START + +CellGroupId ::= INTEGER (0.. maxSecondaryCellGroups) + +-- TAG-CELLGROUPID-STOP +-- ASN1STOP +``` + +#### — *CellIdentity* + +The IE *CellIdentity* is used to unambiguously identify a cell within a PLMN/SNPN. + +#### *CellIdentity* information element + +``` +-- ASN1START +-- TAG-CELLIDENTITY-START + +CellIdentity ::= BIT STRING (SIZE (36)) + +-- TAG-CELLIDENTITY-STOP +-- ASN1STOP +``` + +#### — *CellReselectionPriority* + +The IE *CellReselectionPriority* concerns the absolute priority of the concerned carrier frequency, as used by the cell reselection procedure. Corresponds to parameter "priority" in TS 38.304 [20]. Value 0 means lowest priority. The UE behaviour for the case the field is absent, if applicable, is specified in TS 38.304 [20]. + +#### *CellReselectionPriority* information element + +``` +-- ASN1START +-- TAG-CELLRESELECTIONPRIORITY-START + +CellReselectionPriority ::= INTEGER (0..7) + +-- TAG-CELLRESELECTIONPRIORITY-STOP +-- ASN1STOP +``` + +#### — *CellReselectionSubPriority* + +The IE *CellReselectionSubPriority* indicates a fractional value to be added to the value of *cellReselectionPriority* to obtain the absolute priority of the concerned carrier frequency for E-UTRA and NR. Value *oDot2* corresponds to 0.2, value *oDot4* corresponds to 0.4 and so on. + +#### *CellReselectionSubPriority* information element + +``` +-- ASN1START +-- TAG-CELLRESELECTIONSUBPRIORITY-START + +CellReselectionSubPriority ::= ENUMERATED {oDot2, oDot4, oDot6, oDot8} + +-- TAG-CELLRESELECTIONSUBPRIORITY-STOP +-- ASN1STOP +``` + +#### — *CFR-ConfigMulticast* + +The IE *CFR-ConfigMulticast* indicates UE specific common frequency resource configuration for multicast for one dedicated BWP. + +#### *CFR-ConfigMulticast* information element + +``` +-- ASN1START +-- TAG-CFR-CONFIGMULTICAST-START + +CFR-ConfigMulticast-r17 ::= SEQUENCE { + locationAndBandwidthMulticast-r17 INTEGER (0..37949) OPTIONAL, -- Need S + pdcch-ConfigMulticast-r17 PDCCH-Config OPTIONAL, -- Need M + pdsch-ConfigMulticast-r17 PDSCH-Config OPTIONAL, -- Need M + sps-ConfigMulticastToAddModList-r17 SPS-ConfigMulticastToAddModList-r17 OPTIONAL, -- Need N + sps-ConfigMulticastToReleaseList-r17 SPS-ConfigMulticastToReleaseList-r17 OPTIONAL, -- Need N +} +``` + +``` + +} + +SPS-ConfigMulticastToAddModList-r17 ::= SEQUENCE (SIZE (1..8)) OF SPS-Config + +SPS-ConfigMulticastToReleaseList-r17 ::= SEQUENCE (SIZE (1..8)) OF SPS-ConfigIndex-r16 + +-- TAG-CFR-CONFIGMULTICAST-STOP +-- ASN1STOP + +``` + +| CFR-ConfigMulticast field descriptions | | +|-----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| locationAndBandwidthMulticast | Frequency domain location and bandwidth for MBS multicast. The value of the field shall be interpreted as resource indicator value (RIV) as defined in TS 38.214 [19] with assumptions as described in TS 38.213 [13], clause 12, i.e. setting $N^{\text{size\_BWP}}=275$ . The first PRB is a PRB determined by subcarrierSpacing of the associated BWP and offsetToCarrier corresponding to this subcarrier spacing. If not configured, the UE applies the value of locationAndBandwidth of the DL BWP in which the cfr-ConfigMulticast is configured. | +| pdcch-ConfigMulticast | UE specific group-common PDCCH configuration for MBS multicast for one CFR. | +| pdsch-ConfigMulticast | UE specific group-common PDSCH configuration for MBS multicast for one CFR. | +| sps-ConfigMulticastToAddModList | Indicates a list of one or more DL SPS configurations for MBS multicast. | +| sps-ConfigMulticastToReleaseList | Indicates a list of one or more DL SPS configurations to be released. The NW may release a SPS configuration at any time. | + +## CGI-InfoEUTRA + +The IE *CGI-InfoEUTRA* indicates EUTRA cell access related information, which is reported by the UE as part of E-UTRA report CGI procedure. + +#### CGI-InfoEUTRA information element + +``` + +-- ASN1START +-- TAG-CGI-INFOEUTRA-START + +CGI-InfoEUTRA ::= SEQUENCE { + cgi-info-EPC SEQUENCE { + cgi-info-EPC-legacy CellAccessRelatedInfo-EUTRA-EPC, + cgi-info-EPC-list SEQUENCE (SIZE (1..maxPLMN)) OF CellAccessRelatedInfo-EUTRA-EPC + } OPTIONAL, + cgi-info-5GC SEQUENCE (SIZE (1..maxPLMN)) OF CellAccessRelatedInfo-EUTRA-5GC + OPTIONAL, + freqBandIndicator FreqBandIndicatorEUTRA OPTIONAL, + multiBandInfoList MultiBandInfoListEUTRA OPTIONAL, + freqBandIndicatorPriority ENUMERATED {true} OPTIONAL +} + +-- TAG-CGI-INFOEUTRA-STOP + +``` + +``` +-- ASN1STOP +``` + +#### — *CGI-InfoEUTRALogging* + +The IE *CGI-InfoEUTRALogging* indicates EUTRA cell related information, which is reported by the UE as part of RLF reporting procedure. + +#### ***CGI-InfoEUTRALogging* information element** + +``` +-- ASN1START +-- TAG-CGI-INFOEUTRALOGGING-START + +CGI-InfoEUTRALogging ::= SEQUENCE { + plmn-Identity-eutra-5gc PLMN-Identity OPTIONAL, + trackingAreaCode-eutra-5gc TrackingAreaCode OPTIONAL, + cellIdentity-eutra-5gc BIT STRING (SIZE (28)) OPTIONAL, + plmn-Identity-eutra-epc PLMN-Identity OPTIONAL, + trackingAreaCode-eutra-epc BIT STRING (SIZE (16)) OPTIONAL, + cellIdentity-eutra-epc BIT STRING (SIZE (28)) OPTIONAL +} + +-- TAG-CGI-INFOEUTRALOGGING-STOP +-- ASN1STOP +``` + +#### ***CGI-InfoEUTRALogging* field descriptions** + +| | | +|----------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| cellIdentity-eutra-epc, cellIdentity-eutra-5GC | Unambiguously identify a cell within the context of the PLMN. It belongs the first PLMN entry of plmn-IdentityList (when connected to EPC) or of plmn-IdentityList-r15 (when connected to 5GC) in SystemInformationBlockType1 . | +| plmn-Identity-eutra-epc, plmn-Identity-eutra-5GC | Identifies the PLMN of the cell for the reported cellIdentity : the first PLMN entry of plmn-IdentityList (when connected to EPC) or of plmn-IdentityList-r15 (when connected to 5GC) in SystemInformationBlockType1 that contained the reported cellIdentity . | +| trackingAreaCode-eutra-epc, trackingAreaCode-eutra-5gc | Indicates Tracking Area Code to which the cell indicated by cellIdentity-eutra-epc, cellIdentity-eutra-5GC belongs. | + +#### — *CGI-InfoNR* + +The IE *CGI-InfoNR* indicates cell access related information, which is reported by the UE as part of report CGI procedure. + +#### ***CGI-InfoNR* information element** + +``` +-- ASN1START +-- TAG-CGI-INFO-NR-START + +CGI-InfoNR ::= SEQUENCE { +``` + +``` + +plmn-IdentityInfoList PLMN-IdentityInfoList OPTIONAL, +frequencyBandList MultiFrequencyBandListNR OPTIONAL, +noSIB1 SEQUENCE { + ssb-SubcarrierOffset INTEGER (0..15), + pdcch-ConfigSIB1 PDCCH-ConfigSIB1 +} OPTIONAL, +... +[[ + npn-IdentityInfoList-r16 NPN-IdentityInfoList-r16 OPTIONAL +]], +[[ + cellReservedForOtherUse-r16 ENUMERATED {true} OPTIONAL +]] +} + +-- TAG-CGI-INFO-NR-STOP +-- ASN1STOP + +``` + +#### CGI-InfoNR field descriptions + +##### **noSIB1** + +Contains *ssb-SubcarrierOffset* and *pdcch-ConfigSIB1* fields acquired by the UE from *MIB* of the cell for which report CGI procedure was requested by the network in case *SIB1* was not broadcast by the cell. + +##### **cellReservedForOtherUse** + +Contains *cellReservedForOtherUse* field acquired by the UE that supports *nr-CGI-Reporting-NPN* from *SIB1* of the cell for which report CGI procedure was requested by the network. + +#### – **CGI-Info-Logging** + +The IE *CGI-Info-Logging* indicates the NR Cell Global Identifier (NCGI) for logging purposes (e.g. RLF report), the globally unique identity, and the TAC information of a cell in NR. + +#### **CGI-Info-Logging information element** + +``` + +-- ASN1START +-- TAG-CGI-INFO-LOGGING-START + +CGI-Info-Logging-r16 ::= SEQUENCE { + plmn-Identity-r16 PLMN-Identity, + cellIdentity-r16 CellIdentity, + trackingAreaCode-r16 TrackingAreaCode OPTIONAL +} + +-- TAG-CGI-INFO-LOGGING-STOP +-- ASN1STOP + +``` + +| CGI-Info-Logging field descriptions | | +|--------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| cellIdentity | Unambiguously identify a cell within the context of the PLMN. It belongs the first PLMN-IdentityInfo IE of PLMN-IdentityInfoList in SIB1 . | +| plmn-Identity | Identifies the PLMN of the cell for the reported cellIdentity : the first PLMN entry of plmn-IdentityList (in SIB1 ) in the instance of PLMN-IdentityInfoList that contained the reported cellIdentity . | +| trackingAreaCode | Indicates Tracking Area Code to which the cell indicated by cellIdentity field belongs. | + +#### — CLI-RSSI-Range + +The IE *CLI-RSSI-Range* specifies the value range used in CLI-RSSI measurements and thresholds. The integer value for CLI-RSSI measurements is according to Table 10.1.22.2.2-1 in TS 38.133 [14]. + +#### CLI-RSSI-Range information element + +``` +-- ASN1START +-- TAG-CLI-RSSI-RANGE-START + +CLI-RSSI-Range-r16 ::= INTEGER(0..76) + +-- TAG-CLI-RSSI-RANGE-STOP +-- ASN1STOP +``` + +#### — ClockQualityMetrics + +The IE *ClockQualityMetrics* is used to configure RAN timing synchronisation status information as specified in TS 38.473 [36] + +#### ClockQualityMetrics information element + +``` +-- ASN1START +-- TAG-CLOCKQUALITYMETRICS-START + +ClockQualityMetrics-r18 ::= SEQUENCE { + synchronisationState-r18 ENUMERATED {locked, holdover, freerun, spare1} OPTIONAL, -- Need N + traceabilityToUTC-r18 ENUMERATED {true, false} OPTIONAL, -- Need N + traceabilityToGNSS-r18 ENUMERATED {true, false} OPTIONAL, -- Need N + clockFrequencyStability-r18 BIT STRING (SIZE(16)) OPTIONAL, -- Need N + clockAccuracy-r18 CHOICE { + value INTEGER (1..40000000), + index INTEGER (32..47) + } OPTIONAL, -- Need N + parentTimeSource-r18 ENUMERATED {syncE, pTP, gNSS,atomicClock, terrestialRadio, + serialTimeCode, nTP, handset, other, spare7, + spare6, spare5, spare4, spare3, spare2, spare1} OPTIONAL, -- Need N +} +``` + +``` + + ... +} + +-- TAG-CLOCKQUALITYMETRICS-STOP +-- ASN1STOP + +``` + +#### — *CodebookConfig* + +The IE *CodebookConfig* is used to configure codebooks of Type-I and Type-II (see TS 38.214 [19], clause 5.2.2.2) + +#### *CodebookConfig* information element + +``` + +-- ASN1START +-- TAG-CODEBOOKCONFIG-START + +CodebookConfig ::= + SEQUENCE { + codebookType + CHOICE { + typeI + SEQUENCE { + subType + CHOICE { + typeI-SinglePanel + SEQUENCE { + nrOfAntennaPorts + CHOICE { + two + SEQUENCE { + twoTX-CodebookSubsetRestriction + BIT STRING (SIZE (6)) + }, + moreThanTwo + SEQUENCE { + n1-n2 + CHOICE { + two-one-TypeI-SinglePanel-Restriction + BIT STRING (SIZE (8)), + two-two-TypeI-SinglePanel-Restriction + BIT STRING (SIZE (64)), + four-one-TypeI-SinglePanel-Restriction + BIT STRING (SIZE (16)), + three-two-TypeI-SinglePanel-Restriction + BIT STRING (SIZE (96)), + six-one-TypeI-SinglePanel-Restriction + BIT STRING (SIZE (24)), + four-two-TypeI-SinglePanel-Restriction + BIT STRING (SIZE (128)), + eight-one-TypeI-SinglePanel-Restriction + BIT STRING (SIZE (32)), + four-three-TypeI-SinglePanel-Restriction + BIT STRING (SIZE (192)), + six-two-TypeI-SinglePanel-Restriction + BIT STRING (SIZE (192)), + twelve-one-TypeI-SinglePanel-Restriction + BIT STRING (SIZE (48)), + four-four-TypeI-SinglePanel-Restriction + BIT STRING (SIZE (256)), + eight-two-TypeI-SinglePanel-Restriction + BIT STRING (SIZE (256)), + sixteen-one-TypeI-SinglePanel-Restriction + BIT STRING (SIZE (64)) + }, + typeI-SinglePanel-codebookSubsetRestriction-i2 + BIT STRING (SIZE (16)) + OPTIONAL -- Need R + } + }, + typeI-SinglePanel-ri-Restriction + BIT STRING (SIZE (8)) + }, + typeI-MultiPanel + SEQUENCE { + ng-n1-n2 + CHOICE { + two-two-one-TypeI-MultiPanel-Restriction + BIT STRING (SIZE (8)), + two-four-one-TypeI-MultiPanel-Restriction + BIT STRING (SIZE (16)), + +``` + +``` + + four-two-one-TypeI-MultiPanel-Restriction BIT STRING (SIZE (8)), + two-two-two-TypeI-MultiPanel-Restriction BIT STRING (SIZE (64)), + two-eight-one-TypeI-MultiPanel-Restriction BIT STRING (SIZE (32)), + four-four-one-TypeI-MultiPanel-Restriction BIT STRING (SIZE (16)), + two-four-two-TypeI-MultiPanel-Restriction BIT STRING (SIZE (128)), + four-two-two-TypeI-MultiPanel-Restriction BIT STRING (SIZE (64)) + }, + ri-Restriction BIT STRING (SIZE (4)) +} +}, +codebookMode INTEGER (1..2) + +}, +type2 SEQUENCE { + subType CHOICE { + typeII SEQUENCE { + n1-n2-codebookSubsetRestriction CHOICE { + two-one BIT STRING (SIZE (16)), + two-two BIT STRING (SIZE (43)), + four-one BIT STRING (SIZE (32)), + three-two BIT STRING (SIZE (59)), + six-one BIT STRING (SIZE (48)), + four-two BIT STRING (SIZE (75)), + eight-one BIT STRING (SIZE (64)), + four-three BIT STRING (SIZE (107)), + six-two BIT STRING (SIZE (107)), + twelve-one BIT STRING (SIZE (96)), + four-four BIT STRING (SIZE (139)), + eight-two BIT STRING (SIZE (139)), + sixteen-one BIT STRING (SIZE (128)) + }, + typeII-RI-Restriction BIT STRING (SIZE (2)) + }, + typeII-PortSelection SEQUENCE { + portSelectionSamplingSize ENUMERATED {n1, n2, n3, n4} OPTIONAL, -- Need R + typeII-PortSelectionRI-Restriction BIT STRING (SIZE (2)) + } + }, + phaseAlphabetSize ENUMERATED {n4, n8}, + subbandAmplitude BOOLEAN, + numberOfBeams ENUMERATED {two, three, four} +} +} + +CodebookConfig-r16 ::= SEQUENCE { + codebookType CHOICE { + type2 SEQUENCE { + subType CHOICE { + typeII-r16 SEQUENCE { + n1-n2-codebookSubsetRestriction-r16 CHOICE { + +``` + +``` + + two-one BIT STRING (SIZE (16)), + two-two BIT STRING (SIZE (43)), + four-one BIT STRING (SIZE (32)), + three-two BIT STRING (SIZE (59)), + six-one BIT STRING (SIZE (48)), + four-two BIT STRING (SIZE (75)), + eight-one BIT STRING (SIZE (64)), + four-three BIT STRING (SIZE (107)), + six-two BIT STRING (SIZE (107)), + twelve-one BIT STRING (SIZE (96)), + four-four BIT STRING (SIZE (139)), + eight-two BIT STRING (SIZE (139)), + sixteen-one BIT STRING (SIZE (128)) + }, + typeII-RI-Restriction-r16 BIT STRING (SIZE(4)) +}, +typeII-PortSelection-r16 SEQUENCE { + portSelectionSamplingSize-r16 ENUMERATED {n1, n2, n3, n4}, + typeII-PortSelectionRI-Restriction-r16 BIT STRING (SIZE (4)) +} +}, +numberOfPMI-SubbandsPerCQI-Subband-r16 INTEGER (1..2), +paramCombination-r16 INTEGER (1..8) +} +} +} + +CodebookConfig-r17 := SEQUENCE { + codebookType CHOICE { + typeI SEQUENCE { + typeI-SinglePanel-Group1-r17 SEQUENCE { + nrOfAntennaPorts CHOICE { + two SEQUENCE { + twoTX-CodebookSubsetRestriction1-r17 BIT STRING (SIZE (6)) + }, + moreThanTwo SEQUENCE { + n1-n2 CHOICE { + two-one-TypeI-SinglePanel-Restriction1-r17 BIT STRING (SIZE (8)), + two-two-TypeI-SinglePanel-Restriction1-r17 BIT STRING (SIZE (64)), + four-one-TypeI-SinglePanel-Restriction1-r17 BIT STRING (SIZE (16)), + three-two-TypeI-SinglePanel-Restriction1-r17 BIT STRING (SIZE (96)), + six-one-TypeI-SinglePanel-Restriction1-r17 BIT STRING (SIZE (24)), + four-two-TypeI-SinglePanel-Restriction1-r17 BIT STRING (SIZE (128)), + eight-one-TypeI-SinglePanel-Restriction1-r17 BIT STRING (SIZE (32)), + four-three-TypeI-SinglePanel-Restriction1-r17 BIT STRING (SIZE (192)), + six-two-TypeI-SinglePanel-Restriction1-r17 BIT STRING (SIZE (192)), + twelve-one-TypeI-SinglePanel-Restriction1-r17 BIT STRING (SIZE (48)), + four-four-TypeI-SinglePanel-Restriction1-r17 BIT STRING (SIZE (256)), + eight-two-TypeI-SinglePanel-Restriction1-r17 BIT STRING (SIZE (256)), + sixteen-one-TypeI-SinglePanel-Restriction1-r17 BIT STRING (SIZE (64)) + } + } + } + } + } + } +} + +``` + +``` + + } + } +} +typeI-SinglePanel-Group2-r17 SEQUENCE { + nrOfAntennaPorts CHOICE { + two SEQUENCE { + twoTX-CodebookSubsetRestriction2-r17 BIT STRING (SIZE (6)) + }, + moreThanTwo SEQUENCE { + n1-n2 CHOICE { + two-one-TypeI-SinglePanel-Restriction2-r17 BIT STRING (SIZE (8)), + two-two-TypeI-SinglePanel-Restriction2-r17 BIT STRING (SIZE (64)), + four-one-TypeI-SinglePanel-Restriction2-r17 BIT STRING (SIZE (16)), + three-two-TypeI-SinglePanel-Restriction2-r17 BIT STRING (SIZE (96)), + six-one-TypeI-SinglePanel-Restriction2-r17 BIT STRING (SIZE (24)), + four-two-TypeI-SinglePanel-Restriction2-r17 BIT STRING (SIZE (128)), + eight-one-TypeI-SinglePanel-Restriction2-r17 BIT STRING (SIZE (32)), + four-three-TypeI-SinglePanel-Restriction2-r17 BIT STRING (SIZE (192)), + six-two-TypeI-SinglePanel-Restriction2-r17 BIT STRING (SIZE (192)), + twelve-one-TypeI-SinglePanel-Restriction2-r17 BIT STRING (SIZE (48)), + four-four-TypeI-SinglePanel-Restriction2-r17 BIT STRING (SIZE (256)), + eight-two-TypeI-SinglePanel-Restriction2-r17 BIT STRING (SIZE (256)), + sixteen-one-TypeI-SinglePanel-Restriction2-r17 BIT STRING (SIZE (64)) + } + } + } +} +typeI-SinglePanel-ri-RestrictionSTRP-r17 BIT STRING (SIZE (8)) OPTIONAL, -- Need R +typeI-SinglePanel-ri-RestrictionSDM-r17 BIT STRING (SIZE (4)) OPTIONAL -- Need R +}, +type2 SEQUENCE { + typeII-PortSelection-r17 SEQUENCE { + paramCombination-r17 INTEGER (1..8), + valueOfN-r17 ENUMERATED {n2, n4} OPTIONAL, -- Need R + numberOfPMI-SubbandsPerCQI-Subband-r17 INTEGER(1..2) OPTIONAL, -- Need R + typeII-PortSelectionRI-Restriction-r17 BIT STRING (SIZE (4)) + } +} +} +} +CodebookConfig-v1730 := SEQUENCE { + codebookType CHOICE { + type1 SEQUENCE { + codebookMode INTEGER (1..2) OPTIONAL -- Need R + } + } +} +CodebookConfig-r18 := SEQUENCE { + codebookType CHOICE { + +``` + +``` + +type2 + typeII-CJT-r18 SEQUENCE { + n1-n2-codebookSubsetRestrictionList-r18 SEQUENCE (SIZE (1..4)) OF CBSR-r18, + paramCombination-CJT-r18 INTEGER (1..7), + paramCombination-CJT-L-r18 SEQUENCE (SIZE (1..4)) OF INTEGER (1..5) OPTIONAL, -- Need R + restrictedCMR-Selection-r18 ENUMERATED {enable} OPTIONAL, -- Need R + valueOfO3-r18 ENUMERATED {n1, n4} OPTIONAL, -- Need R + numberOfPMI-SubbandsPerCQI-Subband-r18 INTEGER (1..2) OPTIONAL, -- Need R + typeII-RI-Restriction-r18 BIT STRING (SIZE (4)), + codebookMode-r18 INTEGER (1..2) OPTIONAL -- Need R + }, + typeII-CJT-PortSelection-r18 SEQUENCE { + paramCombination-CJT-PS-alpha-r18 SEQUENCE (SIZE (1..4)) OF INTEGER (1..8) OPTIONAL, -- Need R + restrictedCMR-Selection-r18 ENUMERATED {enable} OPTIONAL, -- Need R + valueOfO3-r18 ENUMERATED {n1, n4} OPTIONAL, -- Need R + valueOfN-CJT-r18 ENUMERATED {n2, n4} OPTIONAL, -- Need R + numberOfPMI-SubbandsPerCQI-Subband-r18 INTEGER (1..2) OPTIONAL, -- Need R + typeII-PortSelectionRI-Restriction-r18 BIT STRING (SIZE (4)), + codebookMode-r18 INTEGER (1..2) OPTIONAL -- Need R + }, + typeII-Doppler-r18 SEQUENCE { + n1-n2-codebookSubsetRestriction-r18 CBSR-r18, + paramCombination-Doppler-r18 INTEGER (1..9), + td-dd-config-r18 TD-DD-Config-r18 OPTIONAL, -- Need R + numberOfPMI-SubbandsPerCQI-Subband-r18 INTEGER (1..2) OPTIONAL, -- Need R + predictionDelay-r18 ENUMERATED {m0,n0,n1,n2} OPTIONAL, -- Need R + typeII-RI-Restriction-r18 BIT STRING (SIZE (4)) + }, + typeII-DopplerPortSelection-r18 SEQUENCE { + paramCombinationDoppler-PS-r18 INTEGER (1..8), + td-dd-config-r18 TD-DD-Config-r18 OPTIONAL, -- Need R + valueOfN-Doppler-r18 ENUMERATED {n2, n4} OPTIONAL, -- Need R + numberOfPMI-SubbandsPerCQI-Subband-r18 INTEGER (1..2) OPTIONAL, -- Need R + predictionDelay-r18 ENUMERATED {m0,n0,n1,n2} OPTIONAL, -- Need R + typeII-PortSelectionRI-Restriction-r18 BIT STRING (SIZE (4)) + } +} +} +} + +CBSR-r18 ::= CHOICE { + two-one BIT STRING (SIZE (8)), + two-two BIT STRING (SIZE (27)), + four-one BIT STRING (SIZE (16)), + three-two BIT STRING (SIZE (35)), + six-one BIT STRING (SIZE (24)), + four-two BIT STRING (SIZE (43)), + eight-one BIT STRING (SIZE (32)), + four-three BIT STRING (SIZE (59)), + six-two BIT STRING (SIZE (59)), + twelve-one BIT STRING (SIZE (48)), +} + +``` + +``` + four-four BIT STRING (SIZE (75)), + eight-two BIT STRING (SIZE (75)), + sixteen-one BIT STRING (SIZE (64)) +} + +TD-DD-Config-r18 ::= SEQUENCE { + vectorLengthDD-r18 ENUMERATED {n1,n2,n4,n8 }, + unitDurationDD-r18 ENUMERATED {m1,m2} OPTIONAL, -- Need R + aperiodicResourceOffset-r18 INTEGER(1..2) OPTIONAL, -- Need R + tdCQI-r18 ENUMERATED {n11,n12,n2 } OPTIONAL -- Need R +} + +-- TAG-CODEBOOKCONFIG-STOP +-- ASN1STOP +``` + +| CodebookConfig field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| codebookMode
CodebookMode as specified in TS 38.214 [19], clause 5.2.2.2.8 and 5.2.2.9. | +| codebookType
CodebookType including possibly sub-types and the corresponding parameters for each (see TS 38.214 [19], clause 5.2.2.2). | +| n1-n2-codebookSubsetRestriction, n1-n2-codebookSubsetRestrictionList
Number of antenna ports in first (n1) and second (n2) dimension and codebook subset restriction (see TS 38.214 [19] clause 5.2.2.2.3).
Number of bits for codebook subset restriction is $\text{CEIL}(\log_2(\text{nchoosek}(O1*O2,4))) + 8*n1*n2$ where $\text{nchoosek}(a,b) = a!/(b!(a-b)!)$ . Network configures up to numberOfCMR elements in n1-n2-codebookSubsetRestrictionList-r18 and each element in the list has same n1-n2 bitstring. | +| n1-n2
Number of antenna ports in first (n1) and second (n2) dimension and codebook subset restriction (see TS 38.214 [19] clause 5.2.2.2.1). | +| ng-n1-n2
Codebook subset restriction for Type I Multi-panel codebook (see TS 38.214 [19], clause 5.2.2.2.2). | +| numberOfBeams
Number of beams, L, used for linear combination. | +| numberOfPMI-SubbandsPerCQI-Subband
Field indicates how PMI subbands are defined per CQI subband according to TS 38.214 [19], clause 5.2.2.2.5, 5.2.2.2.8 and 5.2.2.9. | +| paramCombination, paramCombination-CJT-r18, paramCombination-CJT-L-r18, paramCombination-CJT-PS-r18, paramCombination-CJT-PS-alpha, paramCombinationDoppler-r18, paramCombinationDoppler-PS-r18
Field describes supported parameter combination ( M , l ) as specified in TS 38.214 [19] Clause 5.2.2. For fields paramCombination-CJT-L-r18 or paramCombination-CJT-PS-alpha network configures maximum of numberOfCMR elements but the number of elements can be 1, 2 or 4, and the values are configured according to numberOfCMR from Tables 5.2.2.2.8-1 and 5.2.2.2.9-1 in TS 38.214 [19], respectively. The allowed configuration combinations for paramCombination-CJT-r18 and paramCombination-CJT-L-r18 are given in Table 5.2.2.2.8-3 in TS 38.214 [19]. The allowed configuration combinations for paramCombination-CJT-PS-r18 and paramCombination-CJT-PS-alpha-r18 are given in Table 5.2.2.2.9-3 in TS 38.214 [19]. | +| phaseAlphabetSize
The size of the PSK alphabet, QPSK or 8-PSK. | +| portSelectionSamplingSize
The size of the port selection codebook (parameter d), see TS 38.214 [19] clause 5.2.2.2.6. | +| predictionDelay
Prediction delay for Doppler and Doppler port selection codebooks see TS 38.214 [19], Clause 5.2.1.4. The first value m0 means that the first slot for which the CSI corresponds to is the slot where the CSI reference resource is located at.
For the other three candidate values ( n0 , n1 , n2 ), then the first slot for which the CSI corresponds to is given by $l = n + \delta$ , where delta can take on values of 0, 1, 2 and n the slot in which CSI is reported. | +| restrictedCMR-Selection-r18
Enabling CSI-RS resource (CMR) restriction, (see TS 38.314 [19], clause 5.2.2.2.8) | +| ri-Restriction
Restriction for RI for TypeI-MultiPanel-RI-Restriction (see TS 38.214 [19], clause 5.2.2.2.2). | +| subbandAmplitude
If subband amplitude reporting is activated ( true ). | +| twoTX-CodebookSubsetRestriction
Codebook subset restriction for 2TX codebook (see TS 38.214 [19] clause 5.2.2.2.1). | +| typeI-SinglePanel-codebookSubsetRestriction-i2
i2 codebook subset restriction for Type I Single-panel codebook used when reportQuantity is CRI/Ri/i1/CQI (see TS 38.214 [19] clause 5.2.2.2.1). | +| typeI-SinglePanel-ri-Restriction | + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Restriction for RI for TypeI-SinglePanel-RI-Restriction (see TS 38.214 [19], clause 5.2.2.2.1). | +| typeI-SinglePanel-Group1, typeI-SinglePanel-Group2
Configures codebooks for CSI calculation when UE is configured with two CMR Groups with CMRGroupingAndPairing in the NZP-CSI-RS-ResourceSet associated with the CSI-ReportConfig . Network configures the same number of ports for both codebooks. | +| typeI-SinglePanel-ri-RestrictionSDM, typeI-SinglePanel-ri-RestrictionSTRP
Restriction for RI for N Resource Pairs when two CMR Groups are configured with CMRGroupingAndPairing in the NZP-CSI-RS-ResourceSet associated with the CSI-ReportConfig (see TS 38.214 [19], clause 5.2.1.4.2). | +| typeII-PortSelectionRI-Restriction
Restriction for RI for TypeII-PortSelection-RI-Restriction (see TS 38.214 [19], clauses 5.2.2.2.4, 5.2.2.2.6 and 5.2.2.2.7). | +| typeII-RI-Restriction
Restriction for RI for TypeII-RI-Restriction (see TS 38.214 [19], clauses 5.2.2.2.3 and 5.2.2.2.5). | +| valueOfN
Field provides the value of parameter N as specified in TS 38.214 [19], clause 5.2.2.2.7. The field is present only when M=2 set by paramCombination , see TS 38.214 [19]. | +| valueOfO3-r18
O3: oversampling factor for frequency-domain basis selection offset
Only applicable when CodebookMode = 'Mode1' . | +| valueOfN-CJT-r18
Field describes the size of the window of FD bases for Rel-18 Type II CJT PS codebook. For M=2, N=2,4 (see TS 38.214 [19], clause 5.2.2.2.9) | +| valueOfN-Doppler-r18
Field describes the size of the window of FD bases for Rel-18 Type II Doppler PS codebook. For M=2, N=2,4 (see TS 38.214 [19], clause 5.2.2.2.9) | + +| TD-DD-Config field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| aperiodicResourceOffset
Offset m between two consecutive aperiodic CSI-RS resources. See TS 38.214 [19], clause 5.2.1.4. | +| tdCQI
Number of TD CQIs ( X ) in each SB and ref slot(s) + ref W2(s).
1-1: 1 TD CQI, ref = 1st slot and 1st W2
1-2: 1 TD CQI, ref = 1st and last slots, and 1st and last W2
2: 2 TC CQIs
(see TS 38.214 [19], clause 5.2.1.4). | +| unitDurationDD
DD/TD unit duration (in slots), for AP-CSI-RS only. Note: For P/SP-CSI-RS, d is set to CSI-RS periodicity (see TS 38.214 [19], clause 5.2.1.4). If the value of aperiodicResourceOffset is '1', network configures value 'm1' for this field. | +| vectorLengthDD
Doppler-/time-domain (DD/TD) basis vector length; See TS 38.214 [19], clause 5.2.1.4. | + +#### — *CommonLocationInfo* + +The IE *CommonLocationInfo* is used to transfer detailed location information available at the UE to correlate measurements and UE position information. + +#### **CommonLocationInfo information element** + +``` + +-- ASN1START +-- TAG-COMMONLOCATIONINFO-START + +CommonLocationInfo-r16 ::= SEQUENCE { + gnss-TOD-msec-r16 OCTET STRING OPTIONAL, + locationTimestamp-r16 OCTET STRING OPTIONAL, + locationCoordinate-r16 OCTET STRING OPTIONAL, + locationError-r16 OCTET STRING OPTIONAL, + locationSource-r16 OCTET STRING OPTIONAL, + velocityEstimate-r16 OCTET STRING OPTIONAL +} + +-- TAG-COMMONLOCATIONINFO-STOP +-- ASN1STOP + +``` + +#### **CommonLocationInfo field descriptions** + +##### ***gnss-TOD-msec*** + +Parameter type *gnss-TOD-msec* defined in TS 37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit. + +##### ***locationTimeStamp*** + +Parameter type *DisplacementTimeStamp* defined in TS 37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit. + +##### ***locationCoordinate*** + +Parameter type *LocationCoordinates* defined in TS 37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit. + +##### ***locationError*** + +Parameter type *LocationError* defined in TS 37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit. + +##### ***locationSource*** + +Parameter type *LocationSource* defined in TS 37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit. + +##### ***velocityEstimate*** + +Parameter type *Velocity* defined in TS 37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit. + +#### **— *CondReconfigId*** + +The IE *CondReconfigId* is used to identify a CHO, CPA or CPC configuration. + +#### **CondReconfigId information element** + +``` + +-- ASN1START +-- TAG-CONDRECONFIGID-START + +CondReconfigId-r16 ::= INTEGER (1.. maxNrofCondCells-r16) + +-- TAG-CONDRECONFIGID-STOP +-- ASN1STOP + +``` + +### CondReconfigToAddModList + +The IE *CondReconfigToAddModList* concerns a list of conditional reconfigurations to add or modify, with for each entry the *condReconfigId* and the associated fields. + +#### CondReconfigToAddModList information element + +``` +-- ASN1START +-- TAG-CONDRECONFIGTOADDMODLIST-START + +CondReconfigToAddModList-r16 ::= SEQUENCE (SIZE (1.. maxNrofCondCells-r16)) OF CondReconfigToAddMod-r16 + +CondReconfigToAddMod-r16 ::= SEQUENCE { + condReconfigId-r16 CondReconfigId-r16, + condExecutionCond-r16 SEQUENCE (SIZE (1..2)) OF MeasId OPTIONAL, -- Need M + condRRRReconfig-r16 OCTET STRING (CONTAINING RRCReconfiguration) OPTIONAL, -- Cond condReconfigAdd + ... + [[ + condExecutionCondSCG-r17 OCTET STRING (CONTAINING CondReconfigExecCondSCG-r17) OPTIONAL -- Need M + ]], + [[ + condExecutionCondPSCell-r18 SEQUENCE (SIZE (1..2)) OF MeasId OPTIONAL, -- Cond condReconfigCHO-WithSCG + subsequentCondReconfig-r18 SubsequentCondReconfig-r18 OPTIONAL, -- Need M + securityCellSetId-r18 SecurityCellSetId-r18 OPTIONAL, -- Need M + scpac-ConfigComplete-r18 ENUMERATED {true} OPTIONAL, -- Cond CPAC + ]] +} + +CondReconfigExecCondSCG-r17 ::= SEQUENCE (SIZE (1..2)) OF MeasId + +SubsequentCondReconfig-r18 ::= SEQUENCE { + condExecutionCondToReleaseList-r18 CondExecutionCondToReleaseList-r18 OPTIONAL, -- Need N + condExecutionCondToAddModList-r18 CondExecutionCondToAddModList-r18 OPTIONAL, -- Need N + ... +} + +CondExecutionCondToAddModList-r18 ::= SEQUENCE (SIZE (1.. maxNrofCondCells-r16)) OF CondExecutionCondToAddMod-r18 + +CondExecutionCondToAddMod-r18 ::= SEQUENCE { + condReconfigId-r18 CondReconfigId-r16, + condExecutionCond-r18 SEQUENCE (SIZE (1..2)) OF MeasId OPTIONAL, -- Need M + condExecutionCondSCG-r18 OCTET STRING (CONTAINING CondReconfigExecCondSCG-r17) OPTIONAL, -- Need M + ... +} + +CondExecutionCondToReleaseList-r18 ::= SEQUENCE (SIZE (1.. maxNrofCondCells-r16)) OF CondReconfigId-r16 + +-- TAG-CONDRECONFIGTOADDMODLIST-STOP +-- ASN1STOP +``` + +| CondReconfigToAddMod field descriptions | | +|------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| condExecutionCond | The execution condition that needs to be fulfilled in order to trigger the execution of a conditional reconfiguration for CHO, CPA, intra-SN CPC without MN involvement, MN initiated inter-SN CPC, or SN initiated intra-SN subsequent CPAC without MN involvement. When configuring 2 triggering events (Meas Ids) for a candidate cell, the network ensures that both refer to the same measObject . The network configures at most one from condEventD1 , condEventD2 or condEventT1 for the same candidate cell. For CPA and for MN-initiated inter-SN CPC, the network only indicates MeasId(s) associated with condEventA4 . For intra-SN CPC and intra-SN subsequent CPAC, the network only indicates MeasId(s) associated with condEventA3 or condEventA5 . | +| condExecutionCondPSCell | The execution condition that needs to be fulfilled for the associated PSCell in order to trigger the execution of a conditional reconfiguration for CHO with candidate SCG(s). The Meas Ids refer to the measConfig associated with the MCG. When configuring 2 triggering events (Meas Ids) for a candidate cell, network ensures that both refer to the same measObject . The network only indicates MeasId(s) associated with condEventA4 . | +| condExecutionCondSCG | Contains execution condition that needs to be fulfilled in order to trigger the execution of a conditional reconfiguration for SN initiated inter-SN CPC, SN initiated inter-SN subsequent CPAC, SN initiated intra-SN subsequent CPAC with MN involvement, or MN initiated inter-SN subsequent CPAC. The Meas Ids refer to the measConfig associated with the SCG. When configuring 2 triggering events (Meas Ids) for a candidate cell, network ensures that both refer to the same measObject . For each condReconfigId , the network always configures either condExecutionCond or condExecutionCondSCG (not both). The network only indicates MeasId(s) associated with condEventA3 or condEventA5 . | +| condRRRReconfig | The RRRReconfiguration message to be applied when the condition(s) are fulfilled. The RRRReconfiguration message contained in condRRRReconfig cannot contain the field conditionalReconfiguration or the field daps-Config . | +| scpac-ConfigComplete | This field indicates whether the configuration contained in condRRRReconfig for subsequent CPAC is a complete configuration. | +| subsequentCondReconfig | Contains the execution conditions that need to be fulfilled in order to trigger the execution of a subsequent CPAC. If the field is configured, the configuration of candidate PSCells for subsequent CPAC is supported. The subsequent execution condition is used for conditional reconfiguration evaluation for other candidate cells when the RRRReconfiguration message contained in condRRRReconfig has been applied. | + +| Conditional Presence | Explanation | +|--------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| condReconfigAdd | The field is mandatory present when a condReconfigId is being added. Otherwise the field is optional, need M. | +| condReconfigCHO-WithSCG | This field is optional present, need M, if the RRRReconfiguration message contained in corresponding condRRRReconfig includes the nr-SCG and condExecutionCond is configured. Otherwise, it is absent. | +| CPAC | The field is optionally present when the conditional reconfiguration includes at least one candidate PSCell supporting subsequent CPAC. Otherwise, the field is absent, need R. | + +#### — *ConditionalReconfiguration* + +The IE *ConditionalReconfiguration* is used to add, modify and release the configuration of conditional reconfiguration. + +#### **ConditionalReconfiguration information element** + +``` + +-- ASN1START +-- TAG-CONDITIONALRECONFIGURATION-START + +ConditionalReconfiguration-r16 ::= SEQUENCE { + attemptCondReconfig-r16 ENUMERATED {true} OPTIONAL, -- Cond CHO + condReconfigToRemoveList-r16 CondReconfigToRemoveList-r16 OPTIONAL, -- Need N + condReconfigToAddModList-r16 CondReconfigToAddModList-r16 OPTIONAL, -- Need N + ... + [[ + scpac-ReferenceConfiguration-r18 SetupRelease {ReferenceConfiguration-r18} OPTIONAL, -- Need M + servingSecurityCellSetId-r18 SecurityCellSetId-r18 OPTIONAL, -- Cond condInitialSCPAC + sk-CounterConfiguration-r18 SK-CounterConfiguration-r18 OPTIONAL -- Need M + ]] +} + +CondReconfigToRemoveList-r16 ::= SEQUENCE (SIZE (1.. maxNrofCondCells-r16)) OF CondReconfigId-r16 + +SK-CounterConfiguration-r18 ::= SEQUENCE { + sk-CounterConfigToReleaseList-r18 SEQUENCE (SIZE (1..maxSecurityCellSet-r18)) OF SecurityCellSetId-r18 OPTIONAL, -- Need N + sk-CounterConfigToAddModList-r18 SEQUENCE (SIZE (1..maxSecurityCellSet-r18)) OF SK-CounterConfig-r18 OPTIONAL -- Need N +} + +SK-CounterConfig-r18 ::= SEQUENCE { + securityCellSetId-r18 SecurityCellSetId-r18, + sk-CounterList-r18 SEQUENCE (SIZE (1..maxSK-Counter-r18)) OF SK-Counter +} + +SecurityCellSetId-r18 ::= INTEGER (1.. maxSecurityCellSet-r18) + +-- TAG-CONDITIONALRECONFIGURATION-STOP +-- ASN1STOP + +``` + +| ConditionalReconfiguration field descriptions | | +|------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| attemptCondReconfig | If present, the UE shall perform conditional reconfiguration if selected cell is a target candidate cell and it is the first cell selection after failure as described in clause 5.3.7.3. | +| condReconfigToAddModList | List of the configuration of candidate SpCells to be added or modified for CHO, CPA or CPC. | +| condReconfigToRemoveList | List of the configuration of candidate SpCells to be removed. | +| scpac-ReferenceConfiguration | Includes the reference configuration for the candidate supporting subsequent CPAC. | +| securityCellSetId | This field is used to determine whether UE should perform security update when conditional reconfiguration containing subsequentCondReconfig is executed. | +| servingSecurityCellSetId | This field identifies the security cell set for serving PSCell. | +| sk-counterConfiguration | Includes a list of sk-Counter used to derive $S-K_{gNB}$ for inter-SN subsequent CPAC. If this field is configured, the network shall not configure the field sk-Counter within the RRCReconfiguration message for conditional reconfiguration execution for subsequent CPAC. | + +| Conditional Presence | Explanation | +|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CHO | The field is optional present, Need R, if the UE is configured with at least a candidate SpCell for CHO. Otherwise the field is not present. | +| condInitialSCPAC | The field is mandatory present upon the initial conditional reconfiguration which includes at least one inter-SN candidate PSCell supporting subsequent CPAC. Otherwise, the field is optional, need M. | + +## ConfiguredGrantConfig + +The IE *ConfiguredGrantConfig* is used to configure uplink transmission without dynamic grant according to two possible schemes. The actual uplink grant may either be configured via RRC (*type1*) or provided via the PDCCH (addressed to CS-RNTI) (*type2*). Multiple Configured Grant configurations may be configured in one BWP of a serving cell. + +#### ConfiguredGrantConfig information element + +``` +-- ASN1START +-- TAG-CONFIGUREDGRANTCONFIG-START + +ConfiguredGrantConfig ::= SEQUENCE { + frequencyHopping ENUMERATED {intraSlot, interSlot} OPTIONAL, -- Need S + cg-DMRS-Configuration DMRS-UplinkConfig, + mcs-Table ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need S + mcs-TableTransformPrecoder ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need S + uci-OnPUSCH SetupRelease { CG-UCI-OnPUSCH } OPTIONAL, -- Need M + resourceAllocation ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch }, + rbg-Size ENUMERATED {config2} OPTIONAL, -- Need S + powerControlLoopToUse ENUMERATED {n0, n1}, +``` + +``` + +p0-PUSCH-Alpha P0-PUSCH-AlphaSetId, +transformPrecoder ENUMERATED {enabled, disabled} OPTIONAL, -- Need S +nrofHARQ-Processes INTEGER(1..16), +repK ENUMERATED {n1, n2, n4, n8}, +repK-RV ENUMERATED {s1-0231, s2-0303, s3-0000} OPTIONAL, -- Need R +periodicity ENUMERATED { + sym2, sym7, sym1x14, sym2x14, sym4x14, sym5x14, sym8x14, sym10x14, sym16x14, sym20x14, + sym32x14, sym40x14, sym64x14, sym80x14, sym128x14, sym160x14, sym256x14, sym320x14, sym512x14, + sym640x14, sym1024x14, sym1280x14, sym2560x14, sym5120x14, + sym6, sym1x12, sym2x12, sym4x12, sym5x12, sym8x12, sym10x12, sym16x12, sym20x12, sym32x12, + sym40x12, sym64x12, sym80x12, sym128x12, sym160x12, sym256x12, sym320x12, sym512x12, sym640x12, + sym1280x12, sym2560x12 + }, +configuredGrantTimer INTEGER (1..64) OPTIONAL, -- Need R +rrc-ConfiguredUplinkGrant SEQUENCE { + timeDomainOffset INTEGER (0..5119), + timeDomainAllocation INTEGER (0..15), + frequencyDomainAllocation BIT STRING (SIZE(18)), + antennaPort INTEGER (0..31), + dmrs-SeqInitialization INTEGER (0..1) OPTIONAL, -- Need R + precodingAndNumberOfLayers INTEGER (0..63), + srs-ResourceIndicator INTEGER (0..15) OPTIONAL, -- Need R + mcsAndTBS INTEGER (0..31), + frequencyHoppingOffset INTEGER (1.. maxNrofPhysicalResourceBlocks-1) OPTIONAL, -- Need R + pathlossReferenceIndex INTEGER (0..maxNrofPUSCH-PathlossReferenceRSs-1), + ... + [[ + pusch-RepTypeIndicator-r16 ENUMERATED {pusch-RepTypeA, pusch-RepTypeB} OPTIONAL, -- Need M + frequencyHoppingPUSCH-RepTypeB-r16 ENUMERATED {interRepetition, interSlot} OPTIONAL, -- Cond RepTypeB + timeReferenceSFN-r16 ENUMERATED {sfn512} OPTIONAL, -- Need S + ]], + [[ + pathlossReferenceIndex2-r17 INTEGER (0..maxNrofPUSCH-PathlossReferenceRSs-1) OPTIONAL, -- Need R + srs-ResourceIndicator2-r17 INTEGER (0..15) OPTIONAL, -- Need R + precodingAndNumberOfLayers2-r17 INTEGER (0..63) OPTIONAL, -- Need R + timeDomainAllocation-v1710 INTEGER (16..63) OPTIONAL, -- Need M + timeDomainOffset-r17 INTEGER (0..40959) OPTIONAL, -- Need R + cg-SDT-Configuration-r17 CG-SDT-Configuration-r17 OPTIONAL, -- Need M + ]], + [[ + srs-ResourceSetId-r18 SRS-ResourceSetId OPTIONAL, -- Need R + cg-mIAB-Configuration-r18 CG-mIAB-Configuration-r18 OPTIONAL, -- Cond RACHlessHO + cg-LTM-Configuration-r18 CG-LTM-Configuration-r18 OPTIONAL, -- Cond LTM + cg-SDT-PeriodicityExt-r18 ENUMERATED { + sym1x14x1280, sym2x14x1280, sym4x14x1280, sym8x14x1280, sym16x14x1280, + sym32x14x1280, sym48x14x1280, sym64x14x1280, sym96x14x1280, sym128x14x1280, + sym192x14x1280, sym240x14x1280, sym256x14x1280, sym384x14x1280, sym472x14x1280, + sym480x14x1280, sym512x14x1280, sym768x14x1280, sym944x14x1280, sym960x14x1280, + sym1408x14x1280, sym1536x14x1280, sym1888x14x1280, sym1920x14x1280, + sym2816x14x1280, sym3072x14x1280, sym3776x14x1280, sym5632x14x1280, + sym6144x14x1280, sym7552x14x1280, sym7680x14x1280, sym11264x14x1280, + } + ]], +]] + +``` + +``` + + sym15104x14x1280, sym15360x14x1280, sym22528x14x1280, sym30208x14x1280, + sym45056x14x1280, sym60416x14x1280, sym90112x14x1280, sym180224x14x1280, + sym4x12x1280, sym8x12x1280, sym16x12x1280, sym32x12x1280, sym192x12x1280, + sym384x12x1280, sym960x12x1280, sym1888x12x1280, sym3776x12x1280, + sym5632x12x1280, sym11264x12x1280 + } + timeReferenceHyperSFN-r18 INTEGER (0..1023) OPTIONAL, -- Need R + cg-NTN-RACH-Less-Configuration-r18 CG-NTN-RACH-Less-Configuration-r18 OPTIONAL, -- Need R + ] ] +} +... +[[ +cg-RetransmissionTimer-r16 INTEGER (1..64) OPTIONAL, -- Need R +cg-minDFI-Delay-r16 ENUMERATED + {sym7, sym1x14, sym2x14, sym3x14, sym4x14, sym5x14, sym6x14, sym7x14, sym8x14, + sym9x14, sym10x14, sym11x14, sym12x14, sym13x14, sym14x14, sym15x14, sym16x14 + } OPTIONAL, -- Need R +cg-nrofPUSCH-InSlot-r16 INTEGER (1..7) OPTIONAL, -- Need R +cg-nrofSlots-r16 INTEGER (1..40) OPTIONAL, -- Need R +cg-StartingOffsets-r16 CG-StartingOffsets-r16 OPTIONAL, -- Need R +cg-UCI-Multiplexing-r16 ENUMERATED {enabled} OPTIONAL, -- Need R +cg-COT-SharingOffset-r16 INTEGER (1..39) OPTIONAL, -- Need R +betaOffsetCG-UCI-r16 INTEGER (0..31) OPTIONAL, -- Need R +cg-COT-SharingList-r16 SEQUENCE (SIZE (1..1709)) OF CG-COT-Sharing-r16 OPTIONAL, -- Need R +harq-ProcID-Offset-r16 INTEGER (0..15) OPTIONAL, -- Need M +harq-ProcID-Offset2-r16 INTEGER (0..15) OPTIONAL, -- Need M +configuredGrantConfigIndex-r16 ConfiguredGrantConfigIndex-r16 OPTIONAL, -- Cond CG-List +configuredGrantConfigIndexMAC-r16 ConfiguredGrantConfigIndexMAC-r16 OPTIONAL, -- Cond CG-IndexMAC +periodicityExt-r16 INTEGER (1..5120) OPTIONAL, -- Need R +startingFromRV0-r16 ENUMERATED {on, off} OPTIONAL, -- Need R +phy-PriorityIndex-r16 ENUMERATED {p0, p1} OPTIONAL, -- Need R +autonomousTx-r16 ENUMERATED {enabled} OPTIONAL, -- Cond LCH-BasedPrioritization +], +[[ +cg-betaOffsetsCrossPri0-r17 SetupRelease { BetaOffsetsCrossPriSelCG-r17 } OPTIONAL, -- Need M +cg-betaOffsetsCrossPri1-r17 SetupRelease { BetaOffsetsCrossPriSelCG-r17 } OPTIONAL, -- Need M +mappingPattern-r17 ENUMERATED {cyclicMapping, sequentialMapping} OPTIONAL, -- Cond SRSsets +sequenceOffsetForRV-r17 INTEGER (0..3) OPTIONAL, -- Need R +p0-PUSCH-Alpha2-r17 P0-PUSCH-AlphaSetId OPTIONAL, -- Need R +powerControlLoopToUse2-r17 ENUMERATED {n0, n1} OPTIONAL, -- Need R +cg-COT-SharingList-r17 SEQUENCE (SIZE (1..50722)) OF CG-COT-Sharing-r17 OPTIONAL, -- Need R +periodicityExt-r17 INTEGER (1..40960) OPTIONAL, -- Need R +repK-v1710 ENUMERATED {n12, n16, n24, n32} OPTIONAL, -- Need R +nrofHARQ-Processes-v1700 INTEGER (17..32) OPTIONAL, -- Need M +harq-ProcID-Offset2-r1700 INTEGER (16..31) OPTIONAL, -- Need R +configuredGrantTimer-v1700 INTEGER (33..288) OPTIONAL, -- Need R +cg-minDFI-Delay-v1710 INTEGER (238..3584) OPTIONAL, -- Need R +], +[[ +harq-ProcID-Offset-v1730 INTEGER (16..31) OPTIONAL, -- Need R +cg-nrofSlots-r17 INTEGER (1..320) OPTIONAL, -- Need R + +``` + +``` + + ]], + [[ + applyIndicatedTCI-State-r18 ENUMERATED {first, second, both} OPTIONAL, -- Need R + disableCG-RetransmissionMonitoring-r18 ENUMERATED {true} OPTIONAL, -- Need R + nrofSlotsInCG-Period-r18 INTEGER (2..32) OPTIONAL, -- Need R + nrofBitsInUTO-UCI-r18 INTEGER (3..8) OPTIONAL, -- Need R + betaOffsetUTO-UCI-r18 INTEGER (0..31) OPTIONAL -- Need R + ]] + } + + CG-UCI-OnPUSCH ::= CHOICE { + dynamic SEQUENCE (SIZE (1..4)) OF BetaOffsets, + semiStatic BetaOffsets + } + + CG-COT-Sharing-r16 ::= CHOICE { + noCOT-Sharing-r16 NULL, + cot-Sharing-r16 SEQUENCE { + duration-r16 INTEGER (1..39), + offset-r16 INTEGER (1..39), + channelAccessPriority-r16 INTEGER (1..4) + } + } + + CG-COT-Sharing-r17 ::= CHOICE { + noCOT-Sharing-r17 NULL, + cot-Sharing-r17 SEQUENCE { + duration-r17 INTEGER (1..319), + offset-r17 INTEGER (1..319) + } + } + + CG-StartingOffsets-r16 ::= SEQUENCE { + cg-StartingFullBW-InsideCOT-r16 SEQUENCE (SIZE (1..7)) OF INTEGER (0..6) OPTIONAL, -- Need R + cg-StartingFullBW-OutsideCOT-r16 SEQUENCE (SIZE (1..7)) OF INTEGER (0..6) OPTIONAL, -- Need R + cg-StartingPartialBW-InsideCOT-r16 INTEGER (0..6) OPTIONAL, -- Need R + cg-StartingPartialBW-OutsideCOT-r16 INTEGER (0..6) OPTIONAL -- Need R + } + + BetaOffsetsCrossPriSelCG-r17 ::= CHOICE { + dynamic-r17 SEQUENCE (SIZE (1..4)) OF BetaOffsetsCrossPri-r17, + semiStatic-r17 BetaOffsetsCrossPri-r17 + } + + CG-SDT-Configuration-r17 ::= SEQUENCE { + cg-SDT-RetransmissionTimer INTEGER (1..64) OPTIONAL, -- Need R + sdt-SSB-Subset-r17 CHOICE { + shortBitmap-r17 BIT STRING (SIZE (4)), + mediumBitmap-r17 BIT STRING (SIZE (8)), + longBitmap-r17 BIT STRING (SIZE (64)) + } + } + OPTIONAL, -- Need S + +``` + +``` + + sdt-SSB-PerCG-PUSCH-r17 ENUMERATED {oneEighth, oneFourth, half, one, two, four, eight, sixteen} OPTIONAL, -- Need M + sdt-P0-PUSCH-r17 INTEGER (-16..15) OPTIONAL, -- Need M + sdt-Alpha-r17 ENUMERATED {alpha0, alpha04, alpha05, alpha06, alpha07, alpha08, alpha09, alpha1} OPTIONAL, -- Need M + sdt-DMRS-Ports-r17 CHOICE { + dmrsType1-r17 BIT STRING (SIZE (8)), + dmrsType2-r17 BIT STRING (SIZE (12)) + } OPTIONAL, -- Need M + sdt-NrofDMRS-Sequences-r17 INTEGER (1..2) OPTIONAL -- Need M +} + +CG-mIAB-Configuration-r18 ::= SEQUENCE { + mIAB-RSRP-ThresholdSSB-r18 RSRP-Range, + mIAB-SSB-PerCG-PUSCH-r18 ENUMERATED {oneEighth, oneFourth, half, one, two, four, eight, sixteen}, + mIAB-SSB-Subset-r18 CHOICE { + shortBitmap-r18 BIT STRING (SIZE (4)), + mediumBitmap-r18 BIT STRING (SIZE (8)), + longBitmap-r18 BIT STRING (SIZE (64)) + }, + mIAB-DMRS-Ports-r18 CHOICE { + dmrsType1-r18 BIT STRING (SIZE (8)), + dmrsType2-r18 BIT STRING (SIZE (12)) + } OPTIONAL, -- Need R + mIAB-NrofDMRS-Sequences-r18 INTEGER (1..2) OPTIONAL -- Need R +} + +CG-LTM-Configuration-r18 ::= SEQUENCE { + cg-LTM-RetransmissionTimer-r18 INTEGER (1..64) OPTIONAL, -- Need R + ltm-SSB-Subset-r18 CHOICE { + shortBitmap-r18 BIT STRING (SIZE (4)), + mediumBitmap-r18 BIT STRING (SIZE (8)), + longBitmap-r18 BIT STRING (SIZE (64)) + } OPTIONAL, -- Need S + ltm-SSB-PerCG-PUSCH-r18 ENUMERATED {oneEighth, oneFourth, half, one, two, four, eight, sixteen} + OPTIONAL, -- Need M + sdt-P0-PUSCH-r18 INTEGER (-16..15) OPTIONAL, -- Need M + sdt-Alpha-r18 ENUMERATED {alpha0, alpha04, alpha05, alpha06, alpha07, alpha08, alpha09, alpha1} + OPTIONAL, -- Need M + ltm-DMRS-Ports-r18 CHOICE { + dmrsType1-r18 BIT STRING (SIZE (8)), + dmrsType2-r18 BIT STRING (SIZE (12)) + } OPTIONAL, -- Need M + ltm-NrofDMRS-Sequences-r18 INTEGER (1..2) OPTIONAL -- Need M +} + +CG-NTN-RACH-Less-Configuration-r18 ::= SEQUENCE { + ntn-cg-RACH-less-RetransmissionTimer INTEGER (1..64) OPTIONAL, -- Need R + ntn-RSRP-ThresholdSSB-r18 RSRP-Range, + ntn-SSB-PerCG-PUSCH-r18 ENUMERATED {oneEighth, oneFourth, half, one, two, four, eight, sixteen}, + ntn-SSB-Subset-r18 CHOICE { + shortBitmap-r18 BIT STRING (SIZE (4)), + mediumBitmap-r18 BIT STRING (SIZE (8)), + +``` + +``` + longBitmap-r18 BIT STRING (SIZE (64)) + } OPTIONAL, -- Need R + ntn-DMRS-Ports-r18 CHOICE { + dmrsType1-r18 BIT STRING (SIZE (8)), + dmrsType2-r18 BIT STRING (SIZE (12)) + } OPTIONAL, -- Need R + ntn-NrofDMRS-Sequences-r18 INTEGER (1..2) OPTIONAL -- Need R +} + +-- TAG-CONFIGUREDGRANTCONFIG-STOP +-- ASN1STOP +``` + +| ConfiguredGrantConfig field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| antennaPort
Indicates the antenna port(s) to be used for this configuration, and the maximum bitwidth is 5. See TS 38.214 [19], clause 6.1.2, and TS 38.212 [17], clause 7.3.1. The UE ignores this field in case of CG-SDT. | +| applyIndicatedTCI-State
This field indicates, for PUSCH transmission(s) corresponding a Type1-CG configuration, if UE applies the first, the second or both "indicated" UL only TCI or joint TCI as specified in TS 38.214 [19], clause 5.1.5. If more than one value for the field coresetPoolIndex is configured in IE controlResourceSet for the BWP, the value 'first' corresponds to the "indicated" joint/UL TCI states specific to coresetPoolIndex value 0 and the value 'second' correspond to the coresetPoolIndex value 1, respectively. In this case, network does not configure the value 'both'. | +| autonomousTx
If this field is present, the Configured Grant configuration is configured with autonomous transmission, see TS 38.321 [3]. | +| betaOffsetCG-UCI
Beta offset for CG-UCI in CG-PUSCH, see TS 38.213 [13], clause 9.3 | +| betaOffsetUTO-UCI
Beta offset value for UTO-UCI multiplexing on CG PUSCH, see TS 38.213 [13], clause 9.3. The network always configures uto-UCI-BetaOffset if nrofBitsInUTO-UCI is configured. | +| cg-betaOffsetsCrossPri0, cg-betaOffsetsCrossPri1
Selection between and configuration of dynamic and semi-static beta-offset for multiplexing HARQ-ACK in CG-PUSCH with different priorities.
The field cg-betaOffsetsCrossPri0 indicates multiplexing LP HARQ-ACK in HP CG-PUSCH. This field is configured only if phy-PriorityIndex-r16 is configured with value p1 .
The field cg-betaOffsetsCrossPri1 indicates multiplexing HP HARQ-ACK in LP CG-PUSCH. This field is configured only if phy-PriorityIndex-r16 is configured with value p0 . | +| cg-COT-SharingList
Indicates a table for COT sharing combinations (see 37.213 [48], clause 4.1.3). One row of the table can be set to noCOT-Sharing to indicate that there is no channel occupancy sharing. If the cg-RetransmissionTimer-r16 is configured and the UE operates as an initiating device in semi-static channel access mode (see TS 37.213 [48], clause 4.3), then cg-COT-SharingList-r16 is configured. | +| cg-COT-SharingOffset
Indicates the offset from the end of the slot where the COT sharing indication in UCI is enabled where the offset in symbols is equal to 14*n, where n is the signaled value for cg-COT-SharingOffset . Applicable when ul-toDL-COT-SharingED-Threshold-r16 is not configured (see 37.213 [48], clause 4.1.3). | +| cg-DMRS-Configuration
DMRS configuration (see TS 38.214 [19], clause 6.1.2.3). | +| cg-minDFI-Delay
Indicates the minimum duration (in unit of symbols) from the ending symbol of the PUSCH to the starting symbol of the PDCCH containing the downlink feedback indication (DFI) carrying HARQ-ACK for this PUSCH. The HARQ-ACK received before this minimum duration is not considered as valid for this PUSCH (see TS 38.213 [13], clause 10.5). The following minimum duration values are supported, depending on the configured subcarrier spacing [symbols]:
15 kHz: 7, m*14, where m = {1, 2, 3, 4}
30 kHz: 7, m*14, where m = {1, 2, 3, 4, 5, 6, 7, 8}
60 kHz: 7, m*14, where m = {1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16}
120 kHz: 7, m*14, where m = {1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32}
480 kHz: m*14, where m = {2, 4, 8, 12, 16, 20, 24, 28, 32, 36, 40, 44, 48, 52, 56, 60, 64, 68, 72, 76, 80, 84, 88, 92, 96, 100, 104, 108, 112, 116, 120, 124, 128}
960 kHz: m*14, where m = {4, 8, 16, 24, 32, 40, 48, 56, 64, 72, 80, 88, 96, 104, 112, 120, 128, 136, 144, 152, 160, 168, 176, 184, 192, 200, 208, 216, 224, 232, 240, 248, 256} | +| cg-nrofPUSCH-InSlot
Indicates the number of consecutive PUSCH configured to CG within a slot where the SLIV indicating the first PUSCH and additional PUSCH appended with the same length (see TS 38.214 [19], clause 6.1.2.3). The network can only configure this field if cg-RetransmissionTimer is configured. | +| cg-nrofSlots | + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Indicates the number of allocated slots in a configured grant periodicity following the time instance of configured grant offset (see TS 38.214 [19], clause 6.1.2.3). cg-nrofSlots-r17 is only applicable for operation with shared spectrum channel access in FR2-2. When cg-nrofSlots-r17 is configured, the UE shall ignore cg-nrofSlots-r16 . The network can only configure this field if cg-RetransmissionTimer is configured. | +| cg-RetransmissionTimer
Indicates the initial value of the configured retransmission timer (see TS 38.321 [3]) in multiples of periodicity . The value of cg-RetransmissionTimer is always less than or equal to the value of configuredGrantTimer . This field is always configured together with harq-ProcID-Offset . This field is not configured for operation in licensed spectrum or simultaneously with harq-ProcID-Offset2 . The network does not configure this field for CG-SDT. | +| cg-SDT-PeriodicityExt
This field is used to calculate the periodicity for UL transmission without UL grant for type 1 and type 2 (see TS 38.321 [3], clause 5.8.2) for extended CG-SDT periodicities. If this field is present, the fields periodicity and periodicityExt are ignored.
The following periodicities are supported depending on the configured subcarrier spacing [symbols]:
15 kHz: n*14*1280, where n={1, 2, 4, 8, 48, 96, 240, 472, 944, 1408, 2816}
30 kHz: n*14*1280, where n={2, 4, 8, 16, 96, 192, 480, 944, 1888, 2816, 5632}
60 kHz with normal CP n*14*1280, where n={4, 8, 16, 32, 192, 384, 960, 1888, 3776, 5632, 11264}
60 kHz with ECP: n*12*1280, where n={4, 8, 16, 32, 192, 384, 960, 1888, 3776, 5632, 11264}
120 kHz: n*14*1280, where n={8, 16, 32, 64, 384, 768, 1920, 3776, 7552, 11264, 22528}
480 kHz: n*14*1280, where n={32, 64, 128, 256, 1536, 3072, 7680, 15104, 30208, 45056, 90112}
960 kHz: n*14*1280, where n={64, 128, 256, 512, 3072, 6144, 15360, 30208, 60416, 90112, 180224} | +| cg-StartingOffsets
This field is not applicable for a UE which is allowed to operate as an initiating device in semi-static channel access mode, i.e., not applicable for a UE configured with UE FFP parameters (e.g. period, offset) regardless whether the UE would initiate its own COT or would share gNB's COT. | +| cg-UCI-Multiplexing
If present, this field indicates that in the case of PUCCH overlapping with CG-PUSCH(s) within a PUCCH group, the CG-UCI and HARQ-ACK are jointly encoded (see TS 38.213 [13], clause 9). | +| configuredGrantConfigIndex
Indicates the index of the Configured Grant configurations within the BWP. | +| configuredGrantConfigIndexMAC
Indicates the index of the Configured Grant configurations within the MAC entity. | +| disableCG-RetransmissionMonitoring
Indicates that the UE shall disable monitoring for retransmissions corresponding to this ConfiguredGrantConfig when DRX is configured. When this field is configured, the UE does not start the drx-HARQ-RTT-TimerUL for PUSCH transmissions using configured uplink grants corresponding to this ConfiguredGrantConfig . See TS 38.321 [3], clause 5.7. | +| configuredGrantTimer
Indicates the initial value of the configured grant timer (see TS 38.321 [3]) in multiples of periodicity . When cg-RetransmissionTimer is configured, if HARQ processes are shared among different configured grants on the same BWP, configuredGrantTimer * periodicity is set to the same value for the configurations that share HARQ processes on this BWP. The value of the extension configuredGrantTimer is 2 times the configured value. | +| dmrs-SeqInitialization
The network configures this field if transformPrecoder is disabled or when the value of sdt-NrofDMRS-Sequences is set to 1. Otherwise, the field is absent. | +| frequencyDomainAllocation
Indicates the frequency domain resource allocation, see TS 38.214 [19], clause 6.1.2, and TS 38.212 [17], clause 7.3.1). | +| frequencyHopping
The value intraSlot enables 'Intra-slot frequency hopping' and the value interSlot enables 'Inter-slot frequency hopping'. If the field is absent, frequency hopping is not configured. The field frequencyHopping applies to configured grant for 'pusch-RepTypeA' (see TS 38.214 [19], clause 6.3.1). | +| frequencyHoppingOffset | + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Frequency hopping offset used when frequency hopping is enabled (see TS 38.214 [19], clause 6.1.2 and clause 6.3). | +| frequencyHoppingPUSCH-RepTypeB
Indicates the frequency hopping scheme for Type 1 CG when pusch-RepTypeIndicator is set to 'pusch-RepTypeB' (see TS 38.214 [19], clause 6.1). The value interRepetition enables 'Inter-repetition frequency hopping', and the value interSlot enables 'Inter-slot frequency hopping'. If the field is absent, the frequency hopping is not enabled for Type 1 CG. | +| harq-ProcID-Offset
For operation with shared spectrum channel access configured with cg-RetransmissionTimer-r16 , this configures the range of HARQ process IDs which can be used for this configured grant where the UE can select a HARQ process ID within $[harq-procID-offset, \dots, (harq-procID-offset + nrofHARQ-Processes - 1)]$ . harq-ProcID-Offset-v1730 is only applicable for operation with shared spectrum channel access in FR2-2. If the field harq-ProcID-Offset-v1730 is present, the UE shall ignore the harq-ProcID-Offset-r16 . The network does not configure this field for CG-SDT. | +| harq-ProcID-Offset2
Indicates the offset used in deriving the HARQ process IDs, see TS 38.321 [3], clause 5.4.1. This field is not configured together with cg-RetransmissionTimer-r16 . If the field harq-ProcID-Offset2-v1700 is present, the UE shall ignore the harq-ProcID-Offset2-r16 . | +| mappingPattern
Indicates whether the UE should follow Cyclical mapping pattern or Sequential mapping pattern when two SRS resource sets are configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 with usage 'codebook' or 'noncodebook' for PUSCH transmission with a Type 1 configured grant and/or a Type 2 configured grant as described in clause 6.1.2.3 of TS 38.214 [19] | +| mcs-Table
Indicates the MCS table the UE shall use for PUSCH without transform precoding. If the field is absent the UE applies the value qam64 . | +| mcs-TableTransformPrecoder
Indicates the MCS table the UE shall use for PUSCH with transform precoding. If the field is absent the UE applies the value qam64 . | +| mcsAndTBS
The modulation order, target code rate and TB size (see TS 38.214 [19], clause 6.1.2). The NW does not configure the values 28~31 in this version of the specification. | +| nrofBitsInUTO-UCI
Indicates the number of bits in the UTO-UCI bitmap (see TS 38.212 [17], clause 6.2.7, 6.3.2, TS 38.213 [13], clause 9.3.1, TS 38.214 [19], clause 5.2.3). When this field is configured, UTO-UCI is enabled for the UE. | +| nrofHARQ-Processes
The number of HARQ processes configured. It applies for both Type 1 and Type 2. See TS 38.321 [3], clause 5.4.1. If the UE is configured with nrofHARQ-Processes-v1700 , the UE shall ignore nrofHARQ-Processes (without suffix). | +| nrofSlotsInCG-Period
Number of consecutive slots for CG PUSCH transmission occasions in a period of a single CG PUSCH configuration, see TS 38.214 [19], clause 6.1. The network does not configure this field for operation on shared spectrum. | +| pathlossReferenceIndex
Indicates the reference signal index used as PUSCH pathloss reference (see TS 38.213 [13], clause 7.1.1). In case of CG-SDT, the UE does not use this field. | +| pathlossReferenceIndex2
Indicates the reference signal used as PUSCH pathloss reference for the second SRS resource set. When this field is present, pathlossReferenceIndex indicates the reference signal used as PUSCH pathloss reference for the first SRS resource set | +| p0-PUSCH-Alpha
Index of the P0-PUSCH-AlphaSet to be used for this configuration. | +| p0-PUSCH-Alpha2
Index of the P0-PUSCH-AlphaSet to be used for second SRS resource set. If this field is present, the p0-PUSCH-Alpha provides index for the P0-PUSCH-AlphaSet to be used for first SRS resource set. | +| periodicity
Periodicity for UL transmission without UL grant for type 1 and type 2 (see TS 38.321 [3], clause 5.8.2). | + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

The following periodicities are supported depending on the configured subcarrier spacing [symbols]:

15 kHz: 2, 7, n*14, where n={1, 2, 4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 128, 160, 320, 640}

30 kHz: 2, 7, n*14, where n={1, 2, 4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 128, 160, 256, 320, 640, 1280}

60 kHz with normal CP 2, 7, n*14, where n={1, 2, 4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 128, 160, 256, 320, 512, 640, 1280, 2560}

60 kHz with ECP: 2, 6, n*12, where n={1, 2, 4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 128, 160, 256, 320, 512, 640, 1280, 2560}

120 kHz: 2, 7, n*14, where n={1, 2, 4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 128, 160, 256, 320, 512, 640, 1024, 1280, 2560, 5120}

480 and 960 kHz: n*14, where n={1, 2, 4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 128, 160, 256, 320, 512, 640, 1024, 1280, 2560, 5120}

In case of SDT, the network does not configure periodicity values less than 5ms.

| +|

periodicityExt

This field is used to calculate the periodicity for UL transmission without UL grant for type 1 and type 2 (see TS 38.321 [3], clause 5.8.2). If this field is present, the UE shall ignore field periodicity (without suffix). Network does not configure periodicityExt-r17 together with periodicityExt-r16.

The following periodicities are supported depending on the configured subcarrier spacing [symbols]:

15 kHz: periodicityExt*14, where periodicityExt has a value between 1 and 640.

30 kHz: periodicityExt*14, where periodicityExt has a value between 1 and 1280.

60 kHz with normal CP: periodicityExt*14, where periodicityExt has a value between 1 and 2560.

60 kHz with ECP: periodicityExt*12, where periodicityExt has a value between 1 and 2560.

120 kHz: periodicityExt*14, where periodicityExt has a value between 1 and 5120.

480 kHz: periodicityExt*14, where periodicityExt has a value between 1 and 20480.

960 kHz: periodicityExt*14, where periodicityExt has a value between 1 and 40960.

In case of SDT, the network does not configure periodicity values less than 5ms.

| +|

phy-PriorityIndex

Indicates the PHY priority of CG PUSCH at least for PHY-layer collision handling. Value p0 indicates low priority and value p1 indicates high priority. The network does not configure this for CG-SDT.

| +|

powerControlLoopToUse

Closed control loop to apply (see TS 38.213 [13], clause 7.1.1).

| +|

powerControlLoopToUse2

Closed control loop to apply to second SRS resource set (see TS 38.213 [13], clause 7.1.1). If this field is present, the powerControlLoopToUse applies to the first SRS resource set.

| +|

precodingAndNumberOfLayers

Indicates the precoding and number of layers (see TS 38.212 [17], clause 7.3.1.1.2, and TS 38.214 [19], clause 6.1.2.3). In case of CG-SDT, network sets this field to 1.

| +|

precodingAndNumberOfLayers2

Indicates the precoding and number of layers for the second SRS resource set. When this field is present, precodingAndNumberOfLayers indicated the precoding and number of layers for the first SRS resource set.

| +|

pusch-RepTypeIndicator

Indicates whether UE follows the behavior for PUSCH repetition type A or the behavior for PUSCH repetition type B for each Type 1 configured grant configuration. The value pusch-RepTypeA enables the 'PUSCH repetition type A' and the value pusch-RepTypeB enables the 'PUSCH repetition type B' (see TS 38.214 [19], clause 6.1.2.3). The value pusch-RepTypeB is not configured simultaneously with cgnrofPUSCH-InSlot-r16 and cgnrofSlots-r16. The network does not configure this field if cg-RetransmissionTimer-r16 is configured for CG operation with shared spectrum channel access.

| +|

rbg-Size

Selection between configuration 1 and configuration 2 for RBG size for PUSCH. The UE does not apply this field if resourceAllocation is set to resourceAllocationType1. Otherwise, the UE applies the value config1 when the field is absent. Note: rbg-Size is used when the transformPrecoder parameter is disabled.

| +|

repK-RV

The redundancy version (RV) sequence to use. See TS 38.214 [19], clause 6.1.2. The network configures this field if repetitions are used, i.e., if repK is set to n2, n4 or n8. This field is not configured when cg-RetransmissionTimer is configured. Otherwise, the field is absent.

| + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| repK
Number of repetitions K, see TS 38.214 [19]. If the field repK-v1710 is present, the UE shall ignore the repK (without suffix). | +| resourceAllocation
Configuration of resource allocation type 0 and resource allocation type 1. For Type 1 UL data transmission without grant, resourceAllocation should be resourceAllocationType0 or resourceAllocationType1 . | +| rrc-ConfiguredUplinkGrant
Configuration for "configured grant" transmission with fully RRC-configured UL grant (Type1). If this field is absent the UE uses UL grant configured by DCI addressed to CS-RNTI (Type2). | +| sequenceOffsetForRV
Configures the RV offset for the starting RV for the first repetition (first actual repetition in PUSCH repetition Type B) towards the second 'SRS resource set' for PUSCH configured in either srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 with usage 'codebook' or 'noncodebook'. | +| srs-ResourceSetId
Indicates the associated SRS resource set for PUSCH+PUSCH simultaneous uplink transmission for CG-type 1 PUSCH. | +| srs-ResourceIndicator
Indicates the SRS resource to be used. The network does not configure this for CG-SDT. | +| srs-ResourceIndicator2
Indicates the SRS resource to be used for the second SRS resource set. When this field is present, the srs-ResourceIndicator is used for the first SRS resource set. | +| startingFromRV0
This field is used to determine the initial transmission occasion of a transport block for a given RV sequence, see TS 38.214 [19], clause 6.1.2.3.1. The network does not configure this field if cq-RetransmissionTimer-r16 is configured for CG operation. | +| timeDomainAllocation, timeDomainAllocation-v1710
Indicates a combination of start symbol and length and PUSCH mapping type, see TS 38.214 [19], clause 6.1.2 and TS 38.212 [17], clause 7.3.1. If the field timeDomainAllocation-v1710 is present, the UE shall ignore timeDomainAllocation field (without suffix). | +| timeDomainOffset
Offset related to the reference SFN indicated by timeReferenceSFN , see TS 38.321 [3], clause 5.8.2. timeDomainOffset-r17 is only applicable to 480 kHz and 960 kHz. If timeDomainOffset-r17 is present, the UE shall ignore timeDomainOffset (without suffix). | +| timeReferenceHyperSFN
Indicates H-SFN used for determination of the offset of a resource in time domain. The UE uses the closest H-SFN with the indicated number preceding the reception of the configured grant configuration, see TS 38.321 [3], clause 5.8.2. | +| timeReferenceSFN
Indicates SFN used for determination of the offset of a resource in time domain. The UE uses the closest SFN with the indicated number preceding the reception of the configured grant configuration, see TS 38.321 [3], clause 5.8.2. If the field timeReferenceSFN is not present, the reference SFN is 0. | +| transformPrecoder
Enables or disables transform precoding for type1 and type2 . If the field is absent, the UE enables or disables transform precoding in accordance with the field msg3-transformPrecoder in RACH-ConfigCommon from rach-ConfigCommon included directly within BWP configuration (i.e., not included in additionalRACH-ConfigList ), see TS 38.214 [19], clause 6.1.3. | +| uci-OnPUSCH
Selection between and configuration of dynamic and semi-static beta-offset. For Type 1 UL data transmission without grant, uci-OnPUSCH should be set to semiStatic . The network does not configure this for CG-SDT. | + +| CG-COT-Sharing field descriptions | | +|------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| channelAccessPriority | Indicates the Channel Access Priority Class that the gNB can assume when sharing the UE initiated COT (see TS 37.213 [48], clause 4.1.3). | +| duration | Indicates the number of DL transmission slots within UE initiated COT (see TS 37.213 [48], clause 4.1.3). | +| offset | Indicates the number of DL transmission slots from the end of the slot where CG-UCI is detected after which COT sharing can be used (see TS 37.213 [48], clause 4.1.3). | + +| CG-StartingOffsets field descriptions | | +|-----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| cg-StartingFullBW-InsideCOT | A set of configured grant PUSCH transmission starting offsets (see TS 38.211[16], Table 5.3.1-2) which indicates the length of a CP extension of the first symbol that is located before the configured resource when frequency domain resource allocation includes all interlaces in the allocated RB set(s) and the CG PUSCH resource is inside gNB COT (see TS 38.214 [19], clause 6.1.2.3). | +| cg-StartingFullBW-OutsideCOT | A set of configured grant PUSCH transmission starting offset indices (see TS 38.211[16], Table 5.3.1-2) which indicates the length of a CP extension of the first symbol that is located before the configured resource when frequency domain resource allocation includes all interlaces in the allocated RB set(s) and the CG PUSCH resource is outside gNB COT (see TS 38.214 [19], clause 6.1.2.3). | +| cg-StartingPartialBW-InsideCOT | A set of configured grant PUSCH transmission starting offset index (see TS 38.211[16], Table 5.3.1-2) which indicates the length of a CP extension of the first symbol that is located before the configured resource when frequency domain resource allocation does not include all interlaces in the allocated RB set(s) and the CG PUSCH resource is inside gNB COT (see TS 38.214 [19], clause 6.1.2.3). | +| cg-StartingPartialBW-OutsideCOT | A set of configured grant PUSCH transmission starting offset index (see TS 38.211[16], Table 5.3.1-2) which indicates the length of a CP extension of the first symbol that is located before the configured resource when frequency domain resource allocation does not include all interlaces in the allocated RB set(s) and the CG PUSCH resource is outside gNB COT (see TS 38.214 [19], clause 6.1.2.3). | + +| CG-NTN-RACH-Less-Configuration field descriptions | | +|----------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ntn-cg-RACH-less-RetransmissionTimer | Indicates the initial value of the configured grant retransmission timer used for the initial uplink transmission of RACH-less handover (see TS 38.321 [3]) in multiples of periodicity . | +| ntn-DMRS-Ports | Indicates the set of DMRS ports for SSB to PUSCH mapping (see TS 38.213 [13]). The first (left-most / most significant) bit corresponds to DMRS port 0, the second most significant bit corresponds to DMRS port 1, and so on. A bit set to 1 indicates that this DMRS port is used for mapping. | +| ntn-NrofDMRS-Sequences | Indicates the number of DMRS sequences for SSB to PUSCH mapping (see TS 38.213 [13]). | +| ntn-RSRP-ThresholdSSB | An RSRP threshold configured for SSB selection for the pre-allocated uplink grant as specified in TS 38.321 [3]. | +| ntn-SSB-PerCG-PUSCH | The number of SSBs per pre-allocated uplink grant PUSCH (see TS 38.213 [13]). Value one corresponds to 1 SSBs per pre-allocated uplink grant PUSCH, value two corresponds to 2 SSBs per pre-allocated uplink grant PUSCH and so on. | +| ntn-SSB-Subset | Indicates SSB subset for SSB to CG PUSCH mapping within one CG configuration. If this field is absent, UE assumes the SSB set includes all actually transmitted SSBs. | + +| CG-SDT-Configuration field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| cg-SDT-RetransmissionTimer
Indicates the initial value of the configured grant retransmission timer used for the initial transmission of CG-SDT with CCCH message (see TS 38.321 [3]) in multiples of periodicity . | +| sdt-DMRS-Ports
Indicates the set of DMRS ports for SSB to PUSCH mapping (see TS 38.213 [13]). The first (left-most / most significant) bit corresponds to DMRS port 0, the second most significant bit corresponds to DMRS port 1, and so on. A bit set to 1 indicates that this DMRS port is used for mapping. In case of an (e)RedCap-specific initial downlink BWP that is associated with NCD-SSB, the SSB is the NCD-SSB. Otherwise, the SSB is the CD-SSB. | +| sdt-NrofDMRS-Sequences
Indicates the number of DMRS sequences for SSB to PUSCH mapping (see TS 38.213 [13]). In case of an (e) RedCap-specific initial downlink BWP that is associated with NCD-SSB, the SSB is the NCD-SSB. Otherwise, the SSB is the CD-SSB. | +| sdt-SSB-Subset
Indicates SSB subset for SSB to CG PUSCH mapping within one CG configuration. 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 included in the SSB subset for SSB to CG PUSCH mapping while value 1 indicates that the corresponding SS/PBCH block is included in SSB subset for SSB to CG PUSCH mapping. If this field is absent, UE assumes the SSB set includes all actually transmitted SSBs. In case of an (e)RedCap-specific initial downlink BWP that is associated with NCD-SSB, the SSB is the NCD-SSB. Otherwise, the SSB is the CD-SSB. | +| sdt-SSB-PerCG-PUSCH
The number of SSBs per CG PUSCH (see TS 38.213 [13]). Value one corresponds to 1 SSBs per CG PUSCH, value two corresponds to 2 SSBs per CG PUSCH and so on. In case of an (e)RedCap-specific initial downlink BWP that is associated with NCD-SSB, the SSB is the NCD-SSB. Otherwise, the SSB is the CD-SSB. | +| sdt-P0-PUSCH
Indicates P0 value for PUSCH for CG SDT in steps of 1dB (see TS 38.213 [13]). When this field is configured, the UE ignores the p0-PUSCH-Alpha . | +| sdt-Alpha
Indicates alpha value for PUSCH for CG SDT. alpha0 indicates value 0 is used alpha04 indicates value 4 is used and so on (see TS 38.213 [13]). When this field is configured, the UE ignores the p0-PUSCH-Alpha . | + +| CG-mIAB-Configuration field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| mIAB-DMRS-Ports
Indicates the set of DMRS ports for SSB to PUSCH mapping (see TS 38.213 [13]). The first (left-most / most significant) bit corresponds to DMRS port 0, the second most significant bit corresponds to DMRS port 1, and so on. A bit set to 1 indicates that this DMRS port is used for mapping. | +| mIAB-NrofDMRS-Sequences
Indicates the number of DMRS sequences for SSB to PUSCH mapping (see TS 38.213 [13]). | +| mIAB-RSRP-ThresholdSSB
An RSRP threshold configured for SSB selection for the pre-allocated uplink grant as specified in TS 38.321 [3]. | +| mIAB-SSB-PerCG-PUSCH
The number of SSBs per CG PUSCH (see TS 38.213 [13]). Value one corresponds to 1 SSBs per CG PUSCH, value two corresponds to 2 SSBs per CG PUSCH and so on. | +| mIAB-SSB-Subset
Indicates SSB subset for SSB to CG PUSCH mapping within one CG configuration. | + +| CG-LTM-Configuration field descriptions | | +|------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| cg-LTM-RetransmissionTimer | Indicates the initial value of the configured grant retransmission timer used for the transmission of CG LTM with DCCH/DTCH message (see TS 38.321 [3]) in multiples of periodicity. | +| ltm-DMRS-Ports | Indicates the set of DMRS ports for SSB to PUSCH mapping (see TS 38.213 [13]). | +| ltm-NrofDMRS-Sequences | Indicates the number of DMRS sequences for SSB to PUSCH mapping (see TS 38.213 [13]). | +| ltm-SSB-PerCG-PUSCH | The number of SSBs per CG PUSCH (see TS 38.213 [13]). Value one corresponds to 1 SSBs per CG PUSCH, value two corresponds to 2 SSBs per CG PUSCH and so on. | +| ltm-SSB-Subset | Indicates SSB subset for SSB to CG PUSCH mapping within one CG configuration. | + +| Conditional Presence | Explanation | +|--------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| LCH-BasedPrioritization | This field is optionally present, Need R, if lch-BasedPrioritization is configured in the MAC entity. It is absent otherwise. | +| RACHlessHO | The field is optionally present, Need N, if rach-LessHO is present in reconfigurationWithSync . It is absent otherwise. | +| RepTypeB | The field is optionally present if pusch-RepTypeIndicator is set to pusch-RepTypeB , Need S, and absent otherwise. | +| CG-List | The field is mandatory present when included in configuredGrantConfigToAddModList-r16 , otherwise the field is absent. | +| CG-IndexMAC | The field is mandatory present if at least one configured grant is configured by configuredGrantConfigToAddModList-r16 in any BWP of this MAC entity, otherwise it is optionally present, need R. | +| LTM | The field is optionally present, Need R, if the UE is configured with at least an LTM candidate configuration. Otherwise, the field is absent. | +| SRSsets | This field is mandatory present when UE is configured with two SRS sets configured in either srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 with usage codebook or non-codebook. Otherwise it is absent, Need R | + +#### — *ConfiguredGrantConfigIndex* + +The IE *ConfiguredGrantConfigIndex* is used to indicate the index of one of multiple UL Configured Grant configurations in one BWP. + +#### ***ConfiguredGrantConfigIndex* information element** + +``` +-- ASN1START +-- TAG-CONFIGUREDGRANTCONFIGINDEX-START + +ConfiguredGrantConfigIndex-r16 ::= INTEGER (0.. maxNrofConfiguredGrantConfig-1-r16) + +-- TAG-CONFIGUREDGRANTCONFIGINDEX-STOP +-- ASN1STOP +``` + +#### — *ConfiguredGrantConfigIndexMAC* + +The IE *ConfiguredGrantConfigIndexMAC* is used to indicate the unique Configured Grant configurations index per MAC entity. + +#### *ConfiguredGrantConfigIndexMAC* information element + +``` +-- ASN1START +-- TAG-CONFIGUREDGRANTCONFIGINDEXMAC-START + +ConfiguredGrantConfigIndexMAC-r16 ::= INTEGER (0.. maxNrofConfiguredGrantConfigMAC-1-r16) + +-- TAG-CONFIGUREDGRANTCONFIGINDEXMAC-STOP +-- ASN1STOP +``` + +#### — *ConnEstFailureControl* + +The IE *ConnEstFailureControl* is used to configure parameters for connection establishment failure control. + +#### *ConnEstFailureControl* information element + +``` +-- ASN1START +-- TAG-CONNESTFAILURECONTROL-START + +ConnEstFailureControl ::= SEQUENCE { + connEstFailCount ENUMERATED {n1, n2, n3, n4}, + connEstFailOffsetValidity ENUMERATED {s30, s60, s120, s240, s300, s420, s600, s900}, + connEstFailOffset INTEGER (0..15) OPTIONAL -- Need S +} + +-- TAG-CONNESTFAILURECONTROL-STOP +-- ASN1STOP +``` + +#### *ConnEstFailureControl* field descriptions + +| connEstFailCount | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Number of times that the UE detects T300 expiry on the same cell before applying connEstFailOffset . | +| connEstFailOffset | +| Parameter "Qoffset temp " in TS 38.304 [20]. If the field is absent, the value of infinity shall be used for "Qoffset temp ". | +| connEstFailOffsetValidity | +| Amount of time that the UE applies connEstFailOffset before removing the offset from evaluation of the cell. Value s30 corresponds to 30 seconds, value s60 corresponds to 60 seconds, and so on. | + +## ControlResourceSet + +The IE *ControlResourceSet* is used to configure a time/frequency control resource set (CORESET) in which to search for downlink control information (see TS 38.213 [13], clause 10.1). For the UE not supporting *multipleCORESET* in FR1, in order to receive MBS multicast in CFR within the UE's active BWP, if a CORESET is not configured within the *PDCCH-ConfigMulticast*, the CORESET other than CORESET#0 configured within the UE's active BWP for scheduling unicast can be used for scheduling MBS multicast, and the CORESET is expected to be included completely within the CFR and the parameters configured in the CORESET are expected to be supported by the UE for MBS multicast. + +### ControlResourceSet information element + +``` +-- ASN1START +-- TAG-CONTROLRESOURCESET-START + +ControlResourceSet ::= + SEQUENCE { + controlResourceSetId ControlResourceSetId, + frequencyDomainResources BIT STRING (SIZE (45)), + duration INTEGER (1..maxCoReSetDuration), + cce-REG-MappingType CHOICE { + interleaved SEQUENCE { + reg-BundleSize ENUMERATED {n2, n3, n6}, + interleaverSize ENUMERATED {n2, n3, n6}, + shiftIndex INTEGER(0..maxNrofPhysicalResourceBlocks-1) OPTIONAL -- Need S + }, + nonInterleaved NULL + }, + precoderGranularity ENUMERATED {sameAsREG-bundle, allContiguousRBs}, + tci-StatesPDCCH-ToAddList SEQUENCE(SIZE (1..maxNrofTCI-StatesPDCCH)) OF TCI-StateId OPTIONAL, -- Cond NotSIB-initialBWP + tci-StatesPDCCH-ToReleaseList SEQUENCE(SIZE (1..maxNrofTCI-StatesPDCCH)) OF TCI-StateId OPTIONAL, -- Cond NotSIB-initialBWP + tci-PresentInDCI ENUMERATED {enabled} OPTIONAL, -- Need S + pdcch-DMRS-ScramblingID INTEGER (0..65535) OPTIONAL, -- Need S + ... + [[ + rb-Offset-r16 INTEGER (0..5) OPTIONAL, -- Need S + tci-PresentDCI-1-2-r16 INTEGER (1..3) OPTIONAL, -- Need S + coresetPoolIndex-r16 INTEGER (0..1) OPTIONAL, -- Need S + controlResourceSetId-v1610 ControlResourceSetId-v1610 OPTIONAL -- Need S + ]], + [[ + followUnifiedTCI-State-r17 ENUMERATED {enabled} OPTIONAL -- Need R + ]], + [[ + applyIndicatedTCI-State-r18 ENUMERATED {first, second, both, none} OPTIONAL -- Cond FollowUTCI + ]] + } + +-- TAG-CONTROLRESOURCESET-STOP +-- ASN1STOP +``` + +| ControlResourceSet field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| applyIndicatedTCI-State
This field indicates, for PDCCH reception on this CORESET, if UE applies the first, the second, both or none "indicated" DL only TCI or joint TCI as specified in TS 38.213 [13], clause 10.1. | +| cce-REG-MappingType
Mapping of Control Channel Elements (CCE) to Resource Element Groups (REG) (see TS 38.211 [16], clauses 7.3.2.2 and 7.4.1.3.2). | +| controlResourceSetId
Identifies the instance of the ControlResourceSet IE. Value 0 identifies the common CORESET configured in MIB and in ServingCellConfigCommon ( controlResourceSetZero ) and is hence not used here in the ControlResourceSet IE. Other values identify CORESETs configured by dedicated signalling or in SIB1 or SIB20 . The controlResourceSetId is unique among the BWPs of a serving cell.
If the field controlResourceSetId-v1610 is present, the UE shall ignore the controlResourceSetId field (without suffix). | +| coresetPoolIndex
The index of the CORESET pool for this CORESET as specified in TS 38.213 [13] (clauses 9 and 10) and TS 38.214 [19] (clauses 5.1 and 6.1). If the field is absent, the UE applies the value 0. | +| duration
Contiguous time duration of the CORESET in number of symbols (see TS 38.211 [16], clause 7.3.2.2). | +| followUnifiedTCI-State
When set to enabled, for PDCCH reception on this CORESET, the UE applies the "indicated" DL only TCI or joint TCI as specified in TS 38.214 [19], clause 5.1.5. | +| frequencyDomainResources
Frequency domain resources for the CORESET. Each bit corresponds a group of 6 RBs, with grouping starting from the first RB group in the BWP or MBS CFR where the CORESET is configured. When at least one search space is configured with freqMonitorLocation-r16 , only the first bits are valid (see TS 38.213 [13], clause 10.1). The first (left-most / most significant) bit corresponds to the first RB group in the BWP or MBS CFR where the CORESET is configured, and so on. A bit that is set to 1 indicates that this RB group belongs to the frequency domain resource of this CORESET. Bits corresponding to a group of RBs not fully contained in the bandwidth part within which the CORESET is configured are set to zero (see TS 38.211 [16], clause 7.3.2.2). | +| interleaverSize
Interleaver-size (see TS 38.211 [16], clause 7.3.2.2). | +| pdcch-DMRS-ScramblingID
PDCCH DMRS scrambling initialization (see TS 38.211 [16], clause 7.4.1.3.1). When the field is absent the UE applies the value of the physCellId configured for this serving cell. | +| precoderGranularity
Precoder granularity in frequency domain (see TS 38.211 [16], clauses 7.3.2.2 and 7.4.1.3.2). | +| rb-Offset
Indicates the RB level offset in units of RB from the first RB of the first 6RB group to the first RB of BWP (see 38.213 [13], clause 10.1). | +| reg-BundleSize
Resource Element Groups (REGs) can be bundled to create REG bundles. This parameter defines the size of such bundles (see TS 38.211 [16], clause 7.3.2.2). | +| shiftIndex
When the field is absent the UE applies the value of the physCellId configured for this serving cell (see TS 38.211 [16], clause 7.3.2.2). | +| tci-PresentInDCI
This field indicates if TCI field is present or absent in DCI format 1_1 and DCI format 4_2. When the field is absent the UE considers the TCI to be absent/disabled. In case of cross carrier scheduling, the network sets this field to enabled for the ControlResourceSet used for cross carrier scheduling in DCI format 1_1 in the scheduling cell if enableDefaultBeamForCCS is not configured (see TS 38.214 [19], clause 5.1.5). | +| tci-PresentDCI-1-2
Configures the number of bits for "Transmission configuration indicator" in DCI format 1_2. When the field is absent the UE applies the value of 0 bit for the "Transmission configuration indicator" in DCI format 1_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.214 [19], clause 5.1.5). In case of cross carrier scheduling, the network configures this | + +field for the *ControlResourceSet* used for cross carrier scheduling in DCI format 1\_2 in the scheduling cell if *enableDefaultBeamForCCS* is not configured (see TS 38.214 [19], clause 5.1.5). + +#### ***tci-StatesPDCCH-ToAddList*** + +A subset of the TCI states defined in *pdsch-Config*, either with *tci-StatesToAddModList* or *dl-OrJointTCI-StateList*, included in the *BWP-DownlinkDedicated* corresponding to the serving cell and to the DL BWP to which the *ControlResourceSet* belong to. They are used for providing QCL relationships between the DL RS(s) in one RS Set (TCI-State) and the PDCCH DMRS ports (see TS 38.213 [13], clause 6.). The network configures at most *maxNrofTCI-StatesPDCCH* entries. The QCL relationships defined herein do not apply to MBS broadcast. + +| Conditional Presence | Explanation | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| FollowUTCI | The field is absent if the field followUnifiedTCI-State is present or if more than one value for the field coresetPoolIndex is configured in controlResourceSet for the same bandwidthpart. Otherwise, it is optionally present, Need R. | +| NotSIB-initialBWP | The field is absent in SIB1/SIB20 and in the PDCCH-ConfigCommon of the initial BWP in ServingCellConfigCommon , if SIB1/SIB20 is broadcasted. Otherwise, it is optionally present, Need N. | + +#### — *ControlResourceSetId* + +The *ControlResourceSetId* IE concerns a short identity, used to identify a control resource set within a serving cell. The *ControlResourceSetId* = 0 identifies the *ControlResourceSet#0* configured via PBCH (*MIB*) and in *controlResourceSetZero* (*ServingCellConfigCommon*). The ID space is used across the BWPs and MBS CFRs of a Serving Cell. + +#### ***ControlResourceSetId* information element** + +``` +-- ASN1START +-- TAG-CONTROLRESOURCESETID-START + +ControlResourceSetId ::= INTEGER (0..maxNrofControlResourceSets-1) + +ControlResourceSetId-r16 ::= INTEGER (0..maxNrofControlResourceSets-1-r16) + +ControlResourceSetId-v1610 ::= INTEGER (maxNrofControlResourceSets..maxNrofControlResourceSets-1-r16) + +-- TAG-CONTROLRESOURCESETID-STOP +-- ASN1STOP +``` + +#### — *ControlResourceSetZero* + +The IE *ControlResourceSetZero* is used to configure CORESET#0 of the initial BWP (see TS 38.213 [13], clause 13). + +#### ***ControlResourceSetZero* information element** + +``` +-- ASN1START +-- TAG-CONTROLRESOURCESETZERO-START +``` + +``` +ControlResourceSetZero ::= INTEGER (0..15) + +-- TAG-CONTROLRESOURCESETZERO-STOP +-- ASN1STOP +``` + +# — *CrossCarrierSchedulingConfig* + +The IE *CrossCarrierSchedulingConfig* is used to specify the configuration when the cross-carrier scheduling is used in a cell. + +#### ***CrossCarrierSchedulingConfig* information element** + +``` +-- ASN1START +-- TAG-CROSSCARRIERSCHEDULINGCONFIG-START + +CrossCarrierSchedulingConfig ::= SEQUENCE { + schedulingCellInfo CHOICE { + own SEQUENCE { -- Cross carrier scheduling: scheduling cell + cif-Presence BOOLEAN + }, + other SEQUENCE { -- Cross carrier scheduling: scheduled cell + schedulingCellId ServCellIndex, + cif-InSchedulingCell INTEGER (1..7) + } + }, + ... + [[ + carrierIndicatorSize-r16 SEQUENCE { + carrierIndicatorSizeDCI-1-2-r16 INTEGER (0..3), + carrierIndicatorSizeDCI-0-2-r16 INTEGER (0..3) + } + enableDefaultBeamForCCS-r16 ENUMERATED {enabled} OPTIONAL, -- Cond CIF-PRESENCE + ]], + [[ + ccs-BlindDetectionSplit-r17 ENUMERATED {oneSeventh, threeFourteenth, twoSeventh, threeSeventh, + oneHalf, fourSeventh, fiveSeventh, spare1} OPTIONAL -- Need R + ]] +} + +-- TAG-CROSSCARRIERSCHEDULINGCONFIG-STOP +-- ASN1STOP +``` + +| CrossCarrierSchedulingConfig field descriptions | | +|-----------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| carrierIndicatorSizeDCI-0-2, carrierIndicatorSizeDCI-1-2 | Configures the number of bits for the field of carrier indicator in PDCCH DCI format 0_2/1_2. The field carrierIndicatorSizeDCI-0-2 refers to DCI format 0_2 and the field carrierIndicatorSizeDCI-1-2 refers to DCI format 1_2, respectively (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 10.1). | +| ccs-BlindDetectionSplit | Indicates the share of blind detection candidates and non-overlapping CCEs for PDCCH monitoring on an SpCell and an SCell when cross-carrier scheduling is configured from the SCell for the SpCell (see TS 38.213 [13], clause 10.1.1). The network only configures this field when it sets the field other for an SpCell, i.e., when it configures cross-carrier scheduling of the SpCell by a PDCCH on an SCell. | +| cif-Presence | The field is used to indicate whether carrier indicator field is present (value true ) or not (value false ) in PDCCH DCI formats, see TS 38.213 [13]. If cif-Presence is set to true , the CIF value indicating a grant or assignment for this cell is 0. | +| cif-InSchedulingCell | The field indicates the CIF value used in the scheduling cell to indicate a grant or assignment applicable for this cell, see TS 38.213 [13]. If configured for an SpCell, the non-fallback DCI formats on the SpCell include same number of CIF bits as the corresponding non-fallback DCI formats on the scheduling cell, and the CIF bits are considered reserved. | +| enableDefaultBeamForCCS | This field indicates whether default beam selection for cross-carrier scheduled PDSCH or aperiodic CSI-RS is enabled, see TS 38.214 [19]. If not present, the default beam selection behaviour is not applied, i.e. Rel-15 behaviour is applied. This field can only be configured in the cross-scheduled SCell or SpCell. | +| other | Parameters for cross-carrier scheduling. If configured for an SpCell, the SpCell can be scheduled by the PDCCH on another SCell as well as by the PDCCH on the SpCell. If configured for an SCell, the SCell is scheduled by a PDCCH on another cell. | +| own | Parameters for self-scheduling, i.e., a serving cell is scheduled by its own PDCCH. | +| schedulingCellId | If configured for an SpCell, this field indicates which SCell, in addition to the SpCell, signals the downlink allocations and uplink grants, if applicable, for the concerned SpCell. If configured for an SCell, this field indicates which cell signals the downlink allocations and uplink grants, if applicable, for the concerned SCell. In case the UE is configured with DC, the scheduling cell is part of the same cell group (i.e. MCG or SCG) as the scheduled cell. In case the UE is configured with two PUCCH groups, the scheduling cell and the scheduled cell are within the same PUCCH group. If drx-ConfigSecondaryGroup is configured in the MAC-CellGroupConfig associated with this serving cell, the scheduling cell and the scheduled cell belong to the same Frequency Range. In addition, the serving cell with an aperiodic CSI trigger and the PUSCH resource scheduled for the report are on the same carrier and serving cell, but the cell for which CSI is reported may belong to the same or a different Frequency Range. The network should not trigger a CSI request for a serving cell in the other Frequency Range when that serving cell is outside Active Time. | + +| Conditional Presence | Explanation | +|-----------------------------|------------------------------------------------------------------------------------------------------------------| +| CIF-PRESENCE | The field is mandatory present if the cif-Presence is set to true . The field is absent otherwise. | + +#### – CSI-AperiodicTriggerStateList + +The *CSI-AperiodicTriggerStateList* IE is used to configure the UE with a list of aperiodic trigger states. Each codepoint of the DCI field "CSI request" is associated with one trigger state (see TS 38.321 [3], clause 6.1.3.13). Upon reception of the value associated with a trigger state, the UE will perform measurement of CSI-RS, CSI-IM and/or SSB (reference signals) and aperiodic reporting on L1 according to all entries in the *associatedReportConfigInfoList* for that trigger state. + +#### CSI-AperiodicTriggerStateList information element + +``` + +-- ASN1START +-- TAG-CSI-APERIODICTRIGGERSTATELIST-START + +CSI-AperiodicTriggerStateList ::= SEQUENCE (SIZE (1..maxNrOfCSI-AperiodicTriggers)) OF CSI-AperiodicTriggerState + +CSI-AperiodicTriggerState ::= SEQUENCE { + associatedReportConfigInfoList SEQUENCE (SIZE (1..maxNrofReportConfigPerAperiodicTrigger)) OF CSI-AssociatedReportConfigInfo, + ..., + [[ + ap-CSI-MultiplexingMode-r17 ENUMERATED {enabled} OPTIONAL, -- Need R + ]], + [[ + ltm-AssociatedReportConfigInfo-r18 LTM-CSI-ReportConfigId-r18 OPTIONAL -- Need R + ]] +} + +CSI-AssociatedReportConfigInfo ::= SEQUENCE { + reportConfigId CSI-ReportConfigId, + resourcesForChannel CHOICE { + nzp-CSI-RS SEQUENCE { + resourceSet INTEGER (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig), + qcl-info SEQUENCE (SIZE (1..maxNrofAP-CSI-RS-ResourcesPerSet)) OF TCI-StateId + OPTIONAL -- Cond Aperiodic + }, + csi-SSB-ResourceSet INTEGER (1..maxNrofCSI-SSB-ResourceSetsPerConfig) + }, + csi-IM-ResourcesForInterference INTEGER (1..maxNrofCSI-IM-ResourceSetsPerConfig) OPTIONAL, -- Cond CSI-IM-ForInterference + nzp-CSI-RS-ResourcesForInterference INTEGER (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig) OPTIONAL, -- Cond NZP-CSI-RS-ForInterference + ..., + [[ + resourcesForChannel2-r17 CHOICE { + nzp-CSI-RS2-r17 SEQUENCE { + resourceSet2-r17 INTEGER (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig), + qcl-info2-r17 SEQUENCE (SIZE (1..maxNrofAP-CSI-RS-ResourcesPerSet)) OF TCI-StateId + OPTIONAL -- Cond Aperiodic + }, + csi-SSB-ResourceSet2-r17 INTEGER (1..maxNrofCSI-SSB-ResourceSetsPerConfigExt) + } OPTIONAL, -- Cond NoUnifiedTCI + csi-SSB-ResourceSetExt INTEGER (1..maxNrofCSI-SSB-ResourceSetsPerConfigExt) OPTIONAL -- Need R + ]], + [[ + resourcesForChannelTDCP-r18 SEQUENCE { + resourceSet2TDCP-r18 INTEGER (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig), + resourceSet3TDCP-r18 INTEGER (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig) OPTIONAL, -- Need R + ... OPTIONAL -- Cond TDCP + }, + applyIndicatedTCI-State-r18 CHOICE { + perSet-r18 ENUMERATED {first, second}, + perResource-r18 SEQUENCE (SIZE (1..maxNrofAP-CSI-RS-ResourcesPerSet)) OF ENUMERATED {first, second} + } OPTIONAL -- Need R + ]] +} + +``` + +``` + +applyIndicatedTCI-State2-r18 CHOICE { + perSet-r18 ENUMERATED {first, second}, + perResource-r18 SEQUENCE (SIZE (1..maxNrofAP-CSI-RS-ResourcesPerSet)) OF ENUMERATED {first, second} +} +csi-ReportSubConfigTriggerList-r18 CSI-ReportSubConfigTriggerList-r18 +]] +} + +-- TAG-CSI-APERIODICTRIGGERSTATELIST-STOP +-- ASN1STOP + +``` + +#### CSI-AperiodicTriggerState field descriptions + +### ***Itm-AssociatedReportConfigInfo*** + +This field configures the aperiodic CSI reports of LTM candidate cells. If *Itm-associatedReportConfigInfo* is configured the UE shall ignore the field *associatedReportConfigInfoList*. + +| CSI-AssociatedReportConfigInfo field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ap-CSI-MultiplexingMode
Indicates if the behavior of transmitting aperiodic CSI on the first PUSCH repetitions corresponding to two SRS resource sets configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 with usage 'codebook' or 'noncodebook' is enabled or not. | +| applyIndicatedTCI-State, applyIndicatedTCI-State2
This field indicates, for an aperiodic CSI-RS resource set (perSet) or for CSI-RS resource (perResource), if UE applies the first or the second "indicated" DL only TCI or joint TCI as specified in TS 38.214 [19], clause 5.1.5. If more than one value for the field coresetPoolIndex is configured in the DL BWP used to trigger the CSI report, the value 'first' corresponds to the "indicated" joint/DL TCI states specific to coresetPoolIndex value 0 and the value 'second' correspond to the value 1, respectively. The applyIndicatedTCI-State is for ResourcesForChannel , and applyIndicatedTCI-State2 is for ResourcesForChannels2 . | +| csi-IM-ResourcesForInterference
CSI-IM-ResourceSet for interference measurement. Entry number in csi-IM-ResourceSetList in the CSI-ResourceConfig indicated by csi-IM-ResourcesForInterference in the CSI-ReportConfig indicated by reportConfigId above (value 1 corresponds to the first entry, value 2 to the second entry, and so on). The indicated CSI-IM-ResourceSet should have exactly the same number of resources like the NZP-CSI-RS-ResourceSet indicated in resourceSet within nzp-CSI-RS . | +| csi-ReportSubConfigTriggerList
A list of sub-configuration ID(s) of N sub-configurations out of L configured sub-configurations within a CSI-ReportConfig associated with a triggering state for aperiodic CSI reporting on PUSCH. | +| csi-SSB-ResourceSet, csi-SSB-ResourceSet2
CSI-SSB-ResourceSet for channel measurements. Entry number in csi-SSB-ResourceSetList in the CSI-ResourceConfig indicated by resourcesForChannelMeasurement in the CSI-ReportConfig indicated by reportConfigId above (value 1 corresponds to the first entry, value 2 to the second entry, and so on). | +| nzp-CSI-RS-ResourcesForInterference
NZP-CSI-RS-ResourceSet for interference measurement. Entry number in nzp-CSI-RS-ResourceSetList in the CSI-ResourceConfig indicated by nzp-CSI-RS-ResourcesForInterference in the CSI-ReportConfig indicated by reportConfigId above (value 1 corresponds to the first entry, value 2 to the second entry, and so on). | +| qcl-info, qcl-info2
List of references to TCI-States for providing the QCL source and QCL type for each NZP-CSI-RS-Resource listed in nzp-CSI-RS-Resources of the NZP-CSI-RS-ResourceSet indicated by resourceSet within nzp-CSI-RS . Each TCI-StateId refers to the TCI-State which has this value for tci-StateId and is defined in tci-StatesToAddModList or in dl-OrJointTCI-StateList in the PDSCH-Config included in the BWP-Downlink corresponding to the serving cell and to the DL BWP to which the resourcesForChannelMeasurement (in the CSI-ReportConfig indicated by reportConfigId above) belong to. First entry in qcl-info corresponds to first entry in nzp-CSI-RS-Resources of that NZP-CSI-RS-ResourceSet , second entry in qcl-info corresponds to second entry in nzp-CSI-RS-Resources , and so on (see TS 38.214 [19], clause 5.2.1.5.1). When this field is absent for aperiodic CSI RS, and applyIndicatedTCI-State is not configured, the UE shall use QCL information included in the "indicated" DL only/Joint TCI state as specified in TS 38.214 [19]. | +| reportConfigId
The reportConfigId of one of the CSI-ReportConfigToAddMod configured in CSI-MeasConfig | +| resourcesForChannel2
Configures reference signals for channel measurement corresponding to the second resource set for L1-RSRP measurement as configured in IE CSI-ResourceConfig when nrofReportedGroups-r17 is configured in IE CSI-ReportConfig . If this is present, network configures csi-SSB-ResourceSetExt instead of csi-SSB-ResourceSet and the UE ignores csi-SSB-ResourceSet in resourcesForChannel , and the resourcesForChannel configures the reference signals for channel measurement corresponding to the first resource set for L1-RSRP measurement (see TS 38.214 [19], clause 5.2.1.4). | +| resourcesForChannelTDCP
Configures reference signals for channel measurement corresponding to the second resource set and third resource set for TDCP reporting. All CSI resources of these two resource sets shall share the same QCL-info with the resource sets indicated by resourcesForChannel as specified in TS 38.214 [19]. | +| resourceSet
NZP-CSI-RS-ResourceSet for channel measurements. Entry number in nzp-CSI-RS-ResourceSetList in the CSI-ResourceConfig indicated by resourcesForChannelMeasurement in the CSI-ReportConfig indicated by reportConfigId above (value 1 corresponds to the first entry, value 2 to the second entry, and so on). | + +| Conditional Presence | Explanation | +|-----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Aperiodic | The field is mandatory present if the NZP-CSI-RS-Resources in the associated resourceSet have the resourceType aperiodic and unifiedTCI-StateType is not configured. The field is optionally present, Need R, if the NZP-CSI-RS-Resources in the associated resourceSet have the resourceType aperiodic. The field is absent otherwise. | +| CSI-IM-ForInterference | This field is mandatory present if the CSI-ReportConfig identified by reportConfigId is configured with csi-IM-ResourcesForInterference ; otherwise it is absent. | +| NZP-CSI-RS-ForInterference | This field is mandatory present if the CSI-ReportConfig identified by reportConfigId is configured with nzp-CSI-RS-ResourcesForInterference ; otherwise it is absent. | +| NoUnifiedTCI | This field is optional, Need R, if unifiedTCI-StateType is configured for the serving cell in which the CSI-AperiodicTriggerStateList is included. It is optionally present, Need R, otherwise. | +| SecondCSI/CMR | This field is optionally present if resourcesForChannel2 is configured with aperiodic CSI-RS. It is absent otherwise. | +| TDCP | This field is absent, Need R, if resourcesForChannel2 is configured. It is optionally present, Need R, otherwise. | + +### CSI-FrequencyOccupation + +The IE *CSI-FrequencyOccupation* is used to configure the frequency domain occupation of a channel state information measurement resource (e.g. *NZP-CSI-RS-Resource*, *CSI-IM-Resource*). + +#### CSI-FrequencyOccupation information element + +``` +-- ASN1START +-- TAG-CSI-FREQUENCYOCCUPATION-START + +CSI-FrequencyOccupation ::= SEQUENCE { + startingRB INTEGER (0..maxNrofPhysicalResourceBlocks-1), + nrofRBs INTEGER (24..maxNrofPhysicalResourceBlocksPlus1), + ... +} + +-- TAG-CSI-FREQUENCYOCCUPATION-STOP +-- ASN1STOP +``` + +| CSI-FrequencyOccupation field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| nrofRBs
Number of PRBs across which this CSI resource spans. Only multiples of 4 are allowed. The smallest configurable number is the minimum of 24 and the width of the associated BWP. If the configured value is larger than the width of the corresponding BWP, the UE shall assume that the actual CSI-RS bandwidth is equal to the width of the BWP. | +| startingRB
PRB where this CSI resource starts in relation to common resource block #0 (CRB#0) on the common resource block grid. Only multiples of 4 are allowed (0, 4, ...) | + +### CSI-IM-Resource + +The IE *CSI-IM-Resource* is used to configure one CSI Interference Management (IM) resource. + +#### CSI-IM-Resource information element + +``` +-- ASN1START +-- TAG-CSI-IM-RESOURCE-START + +CSI-IM-Resource ::= SEQUENCE { + csi-IM-ResourceId CSI-IM-ResourceId, + csi-IM-ResourceElementPattern CHOICE { + pattern0 SEQUENCE { + subcarrierLocation-p0 ENUMERATED { s0, s2, s4, s6, s8, s10 }, + symbolLocation-p0 INTEGER (0..12) + }, + pattern1 SEQUENCE { + subcarrierLocation-p1 ENUMERATED { s0, s4, s8 }, + symbolLocation-p1 INTEGER (0..13) + } + } + freqBand CSI-FrequencyOccupation OPTIONAL, -- Need M + periodicityAndOffset CSI-ResourcePeriodicityAndOffset OPTIONAL, -- Cond PeriodicOrSemiPersistent + ... +} + +-- TAG-CSI-IM-RESOURCE-STOP +-- ASN1STOP +``` + +| CSI-IM-Resource field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| csi-IM-ResourceElementPattern
The resource element pattern (Pattern0 (2,2) or Pattern1 (4,1)) with corresponding parameters (see TS 38.214 [19], clause 5.2.2.4) | +| freqBand
Frequency-occupancy of CSI-IM (see TS 38.214 [19], clause 5.2.2.4) | +| periodicityAndOffset
Periodicity and slot offset for periodic/semi-persistent CSI-IM. Network always configures the UE with a value for this field for periodic and semi-persistent CSI-IM-Resources (as indicated in CSI-ResourceConfig). A change of configuration between periodic or semi-persistent and aperiodic for a CSI-IM-Resource is not supported without a release and add. | +| subcarrierLocation-p0
OFDM subcarrier occupancy of the CSI-IM resource for Pattern0 (see TS 38.214 [19], clause 5.2.2.4) | +| subcarrierLocation-p1
OFDM subcarrier occupancy of the CSI-IM resource for Pattern1 (see TS 38.214 [19], clause 5.2.2.4) | +| symbolLocation-p0
OFDM symbol location of the CSI-IM resource for Pattern0 (see TS 38.214 [19], clause 5.2.2.4) | +| symbolLocation-p1
OFDM symbol location of the CSI-IM resource for Pattern1 (see TS 38.214 [19], clause 5.2.2.4) | + +| Conditional Presence | Explanation | +|---------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PeriodicOrSemiPersistent | The field is optionally present, Need M, for periodic and semi-persistent CSI-IM-Resources (as indicated in CSI-ResourceConfig). The field is absent otherwise. | + +#### – *CSI-IM-ResourceId* + +The IE *CSI-IM-ResourceId* is used to identify one *CSI-IM-Resource*. + +#### *CSI-IM-ResourceId* information element + +``` +-- ASN1START +-- TAG-CSI-IM-RESOURCEID-START + +CSI-IM-ResourceId ::= INTEGER (0..maxNrofCSI-IM-Resources-1) + +-- TAG-CSI-IM-RESOURCEID-STOP +-- ASN1STOP +``` + +#### – *CSI-IM-ResourceSet* + +The IE *CSI-IM-ResourceSet* is used to configure a set of one or more CSI Interference Management (IM) resources (their IDs) and set-specific parameters. + +#### *CSI-IM-ResourceSet* information element + +``` +-- ASN1START +-- TAG-CSI-IM-RESOURCESET-START + +CSI-IM-ResourceSet ::= SEQUENCE { + csi-IM-ResourceSetId CSI-IM-ResourceSetId, + csi-IM-Resources SEQUENCE (SIZE(1..maxNrofCSI-IM-ResourcesPerSet)) OF CSI-IM-ResourceId, + ... +} + +-- TAG-CSI-IM-RESOURCESET-STOP +-- ASN1STOP +``` + +| CSI-IM-ResourceSet field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------| +| csi-IM-Resources
CSI-IM-Resources associated with this CSI-IM-ResourceSet (see TS 38.214 [19], clause 5.2). | + +#### CSI-IM-ResourceSetId + +The IE *CSI-IM-ResourceSetId* is used to identify *CSI-IM-ResourceSets*. + +#### CSI-IM-ResourceSetId information element + +``` +-- ASN1START +-- TAG-CSI-IM-RESOURCESETID-START + +CSI-IM-ResourceSetId ::= INTEGER (0..maxNrofCSI-IM-ResourceSets-1) + +-- TAG-CSI-IM-RESOURCESETID-STOP +-- ASN1STOP +``` + +### CSI-MeasConfig + +The IE *CSI-MeasConfig* is used to configure CSI-RS (reference signals) belonging to the serving cell in which *CSI-MeasConfig* is included, channel state information reports to be transmitted on PUCCH on the serving cell in which *CSI-MeasConfig* is included and channel state information reports on PUSCH triggered by DCI received on the serving cell in which *CSI-MeasConfig* is included. See also TS 38.214 [19], clause 5.2. + +#### CSI-MeasConfig information element + +``` +-- ASN1START +-- TAG-CSI-MEASCONFIG-START + +CSI-MeasConfig ::= SEQUENCE { + nzp-CSI-RS-ResourceToAddModList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-Resources)) OF NZP-CSI-RS-Resource OPTIONAL, -- Need N + nzp-CSI-RS-ResourceToReleaseList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-Resources)) OF NZP-CSI-RS-ResourceId OPTIONAL, -- Need N + nzp-CSI-RS-ResourceSetToAddModList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourceSets)) OF NZP-CSI-RS-ResourceSet OPTIONAL, -- Need N + nzp-CSI-RS-ResourceSetToReleaseList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourceSets)) OF NZP-CSI-RS-ResourceSetId OPTIONAL, -- Need N + csi-IM-ResourceToAddModList SEQUENCE (SIZE (1..maxNrofCSI-IM-Resources)) OF CSI-IM-Resource OPTIONAL, -- Need N + csi-IM-ResourceToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-IM-Resources)) OF CSI-IM-ResourceId OPTIONAL, -- Need N + csi-IM-ResourceSetToAddModList SEQUENCE (SIZE (1..maxNrofCSI-IM-ResourceSets)) OF CSI-IM-ResourceSet OPTIONAL, -- Need N + csi-IM-ResourceSetToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-IM-ResourceSets)) OF CSI-IM-ResourceSetId OPTIONAL, -- Need N + csi-SSB-ResourceSetToAddModList SEQUENCE (SIZE (1..maxNrofCSI-SSB-ResourceSets)) OF CSI-SSB-ResourceSet OPTIONAL, -- Need N + csi-SSB-ResourceSetToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-SSB-ResourceSets)) OF CSI-SSB-ResourceSetId OPTIONAL, -- Need N + csi-ResourceConfigToAddModList SEQUENCE (SIZE (1..maxNrofCSI-ResourceConfigurations)) OF CSI-ResourceConfig OPTIONAL, -- Need N + csi-ResourceConfigToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-ResourceConfigurations)) OF CSI-ResourceConfigId OPTIONAL, -- Need N + csi-ReportConfigToAddModList SEQUENCE (SIZE (1..maxNrofCSI-ReportConfigurations)) OF CSI-ReportConfig OPTIONAL, -- Need N + csi-ReportConfigToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-ReportConfigurations)) OF CSI-ReportConfigId OPTIONAL, -- Need N + reportTriggerSize INTEGER (0..6) OPTIONAL, -- Need M + aperiodicTriggerStateList SetupRelease { CSI-AperiodicTriggerStateList } OPTIONAL, -- Need M +} +``` + +``` + +semiPersistentOnPUSCH-TriggerStateList SetupRelease { CSI-SemiPersistentOnPUSCH-TriggerStateList } OPTIONAL, -- Need M +... +[[ +reportTriggerSizeDCI-0-2-r16 INTEGER (0..6) OPTIONAL -- Need R +]], +[[ +sCellActivationRS-ConfigToAddModList-r17 SEQUENCE (SIZE (1..maxNrofSCellActRS-r17)) OF SCellActivationRS-Config-r17 OPTIONAL, -- Need N +sCellActivationRS-ConfigToReleaseList-r17 SEQUENCE (SIZE (1..maxNrofSCellActRS-r17)) OF SCellActivationRS-ConfigId-r17 OPTIONAL -- Need N +]], +[[ +ltm-CSI-ReportConfigToAddModList-r18 SEQUENCE (SIZE (1..maxNrofLTM-CSI-ReportConfigurations-r18)) OF LTM-CSI-ReportConfig-r18 +OPTIONAL, -- Need N +ltm-CSI-ReportConfigToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofLTM-CSI-ReportConfigurations-r18)) OF LTM-CSI-ReportConfigId-r18 +OPTIONAL -- Need N +]] +} + +-- TAG-CSI-MEASCONFIG-STOP +-- ASN1STOP + +``` + +| CSI-MeasConfig field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| aperiodicTriggerStateList
Contains trigger states for dynamically selecting one or more aperiodic and semi-persistent reporting configurations and/or triggering one or more aperiodic CSI-RS resource sets for channel and/or interference measurement (see TS 38.214 [19], clause 5.2.1). | +| csi-IM-ResourceSetToAddModList
Pool of CSI-IM-ResourceSet which can be referred to from CSI-ResourceConfig or from MAC CEs. | +| csi-IM-ResourceToAddModList
Pool of CSI-IM-Resource which can be referred to from CSI-IM-ResourceSet . | +| csi-ReportConfigToAddModList
Configured CSI report settings as specified in TS 38.214 [19] clause 5.2.1.1. | +| csi-ResourceConfigToAddModList
Configured CSI resource settings as specified in TS 38.214 [19] clause 5.2.1.2. | +| csi-SSB-ResourceSetToAddModList
Pool of CSI-SSB-ResourceSet which can be referred to from CSI-ResourceConfig . | +| ltm-CSI-ReportConfigToAddModList
Configured CSI report settings for LTM as specified in TS 38.214 [19]. | +| nzp-CSI-RS-ResourceSetToAddModList
Pool of NZP-CSI-RS-ResourceSet which can be referred to from CSI-ResourceConfig or from MAC CEs. | +| nzp-CSI-RS-ResourceToAddModList
Pool of NZP-CSI-RS-Resource which can be referred to from NZP-CSI-RS-ResourceSet . | +| reportTriggerSize, reportTriggerSizeDCI-0-2
Size of CSI request field in DCI (bits) (see TS 38.214 [19], clause 5.2.1.5.1). The field reportTriggerSize applies to DCI format 0_1 and the field reportTriggerSizeDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 5.2.1.5.1). | +| sCellActivationRS-ConfigToAddModList
Configured RS for fast SCell activation as specified in TS 38.214 [19] clause 5.2.1.5.3. | + +### CSI-ReportConfig + +The IE *CSI-ReportConfig* is used to configure a periodic or semi-persistent report sent on PUCCH on the cell in which the *CSI-ReportConfig* is included, or to configure a semi-persistent or aperiodic report sent on PUSCH triggered by DCI received on the cell in which the *CSI-ReportConfig* is included (in this case, the cell on which the report is sent is determined by the received DCI). See TS 38.214 [19], clause 5.2.1. + +#### CSI-ReportConfig information element + +``` +-- ASN1START +-- TAG-CSI-REPORTCONFIG-START + +CSI-ReportConfig ::= SEQUENCE { + reportConfigId CSI-ReportConfigId, + carrier ServCellIndex OPTIONAL, -- Need S + resourcesForChannelMeasurement CSI-ResourceConfigId, + csi-IM-ResourcesForInterference CSI-ResourceConfigId OPTIONAL, -- Need R + nzp-CSI-RS-ResourcesForInterference CSI-ResourceConfigId OPTIONAL, -- Need R + reportConfigType CHOICE { + periodic SEQUENCE { + reportSlotConfig CSI-ReportPeriodicityAndOffset, + pucch-CSI-ResourceList SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource + }, + semiPersistentOnPUCCH SEQUENCE { + reportSlotConfig CSI-ReportPeriodicityAndOffset, + pucch-CSI-ResourceList SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource + }, + semiPersistentOnPUSCH SEQUENCE { + reportSlotConfig ENUMERATED {s15, s110, s120, s140, s180, s1160, s1320}, + reportSlotOffsetList SEQUENCE (SIZE (1.. maxNrofUL-Allocations)) OF INTEGER(0..32), + p0alpha P0-PUSCH-AlphaSetId + }, + aperiodic SEQUENCE { + reportSlotOffsetList SEQUENCE (SIZE (1..maxNrofUL-Allocations)) OF INTEGER(0..32) + } + }, + reportQuantity CHOICE { + none NULL, + cri-RI-PMI-CQI NULL, + cri-RI-i1 NULL, + cri-RI-i1-CQI SEQUENCE { + pdsch-BundleSizeForCSI ENUMERATED {n2, n4} OPTIONAL -- Need S + }, + cri-RI-CQI NULL, + cri-RSRP NULL, + ssb-Index-RSRP NULL, + cri-RI-LI-PMI-CQI NULL + }, +} +``` + +``` + + reportFreqConfiguration SEQUENCE { + cqi-FormatIndicator ENUMERATED { widebandCQI, subbandCQI } OPTIONAL, -- Need R + pmi-FormatIndicator ENUMERATED { widebandPMI, subbandPMI } OPTIONAL, -- Need R + csi-ReportingBand CHOICE { + subbands3 BIT STRING(SIZE(3)), + subbands4 BIT STRING(SIZE(4)), + subbands5 BIT STRING(SIZE(5)), + subbands6 BIT STRING(SIZE(6)), + subbands7 BIT STRING(SIZE(7)), + subbands8 BIT STRING(SIZE(8)), + subbands9 BIT STRING(SIZE(9)), + subbands10 BIT STRING(SIZE(10)), + subbands11 BIT STRING(SIZE(11)), + subbands12 BIT STRING(SIZE(12)), + subbands13 BIT STRING(SIZE(13)), + subbands14 BIT STRING(SIZE(14)), + subbands15 BIT STRING(SIZE(15)), + subbands16 BIT STRING(SIZE(16)), + subbands17 BIT STRING(SIZE(17)), + subbands18 BIT STRING(SIZE(18)), + ..., + subbands19-v1530 BIT STRING(SIZE(19)) + } OPTIONAL -- Need S + } OPTIONAL, -- Need R + timeRestrictionForChannelMeasurements ENUMERATED {configured, notConfigured}, OPTIONAL, -- Need R + timeRestrictionForInterferenceMeasurements ENUMERATED {configured, notConfigured}, OPTIONAL, -- Need R + codebookConfig CodebookConfig OPTIONAL, -- Need R + dummy ENUMERATED {n1, n2} OPTIONAL, -- Need R + groupBasedBeamReporting CHOICE { + enabled NULL, + disabled SEQUENCE { + nrofReportedRS ENUMERATED {n1, n2, n3, n4} OPTIONAL -- Need S + } + }, + cqi-Table ENUMERATED {table1, table2, table3, table4-r17} OPTIONAL, -- Need R + subbandSize ENUMERATED {value1, value2}, + non-PMI-PortIndication SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourcesPerConfig)) OF PortIndexFor8Ranks OPTIONAL, -- Need R + ..., + [[ + semiPersistentOnPUSCH-v1530 SEQUENCE { + reportSlotConfig-v1530 ENUMERATED {sl4, sl8, sl16} + } OPTIONAL -- Need R + ]], + [[ + semiPersistentOnPUSCH-v1610 SEQUENCE { + reportSlotOffsetListDCI-0-2-r16 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..32) OPTIONAL, -- Need R + reportSlotOffsetListDCI-0-1-r16 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..32) OPTIONAL, -- Need R + } OPTIONAL, -- Need R + aperiodic-v1610 SEQUENCE { + reportSlotOffsetListDCI-0-2-r16 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..32) OPTIONAL -- Need R + } OPTIONAL -- Need R + ]] + +``` + +``` + + reportSlotOffsetListDCI-0-1-r16 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..32) OPTIONAL -- Need R +} OPTIONAL, -- Need R +reportQuantity-r16 CHOICE { + cri-SINR-r16 NULL, + ssb-Index-SINR-r16 NULL +} OPTIONAL, -- Need R +codebookConfig-r16 CodebookConfig-r16 OPTIONAL -- Need R +]], +[[ +cqi-BitsPerSubband-r17 ENUMERATED {bits4} OPTIONAL, -- Need R +groupBasedBeamReporting-v1710 SEQUENCE { + nrofReportedGroups-r17 ENUMERATED {n1, n2, n3, n4} +} OPTIONAL, -- Need R +codebookConfig-r17 CodebookConfig-r17 OPTIONAL, -- Need R +sharedCMR-r17 ENUMERATED {enable} OPTIONAL, -- Need R +csi-ReportMode-r17 ENUMERATED {model1, mode2} OPTIONAL, -- Need R +numberOfSingleTRP-CSI-Model-r17 ENUMERATED {n0, n1, n2} OPTIONAL, -- Need R +reportQuantity-r17 CHOICE { + cri-RSRP-Index-r17 NULL, + ssb-Index-RSRP-Index-r17 NULL, + cri-SINR-Index-r17 NULL, + ssb-Index-SINR-Index-r17 NULL +} OPTIONAL -- Need R +]], +[[ +semiPersistentOnPUSCH-v1720 SEQUENCE { + reportSlotOffsetList-r17 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..128) OPTIONAL, -- Need R + reportSlotOffsetListDCI-0-2-r17 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..128) OPTIONAL, -- Need R + reportSlotOffsetListDCI-0-1-r17 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..128) OPTIONAL, -- Need R +} OPTIONAL, -- Need R +aperiodic-v1720 SEQUENCE { + reportSlotOffsetList-r17 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..128) OPTIONAL, -- Need R + reportSlotOffsetListDCI-0-2-r17 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..128) OPTIONAL, -- Need R + reportSlotOffsetListDCI-0-1-r17 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..128) OPTIONAL, -- Need R +} OPTIONAL -- Need R +]], +[[ +codebookConfig-v1730 CodebookConfig-v1730 OPTIONAL -- Need R +]], +[[ +groupBasedBeamReporting-v1800 SEQUENCE { + reportingMode-r18 ENUMERATED {jointULDL, onlyUL} +} OPTIONAL, -- Need R +reportQuantity-r18 TDCP-r18 OPTIONAL, -- Need R +codebookConfig-r18 CodebookConfig-r18 OPTIONAL, -- Need R +csi-ReportSubConfigToAddModList-r18 SEQUENCE (SIZE (2..maxNrofCSI-ReportSubconfigPerCSI-ReportConfig-r18)) OF CSI-ReportSubConfig-r18 OPTIONAL, -- Need N +csi-ReportSubConfigToReleaseList-r18 SEQUENCE (SIZE (2..maxNrofCSI-ReportSubconfigPerCSI-ReportConfig-r18)) OF CSI-ReportSubConfigId-r18 OPTIONAL -- Need N +]] +} + +``` + +``` + +CSI-ReportPeriodicityAndOffset ::= CHOICE { + slots4 INTEGER (0..3), + slots5 INTEGER (0..4), + slots8 INTEGER (0..7), + slots10 INTEGER (0..9), + slots16 INTEGER (0..15), + slots20 INTEGER (0..19), + slots40 INTEGER (0..39), + slots80 INTEGER (0..79), + slots160 INTEGER (0..159), + slots320 INTEGER (0..319) +} + +PortIndexFor8Ranks ::= CHOICE { + portIndex8 SEQUENCE { + rank1-8 PortIndex8 OPTIONAL, -- Need R + rank2-8 SEQUENCE (SIZE (2)) OF PortIndex8 OPTIONAL, -- Need R + rank3-8 SEQUENCE (SIZE (3)) OF PortIndex8 OPTIONAL, -- Need R + rank4-8 SEQUENCE (SIZE (4)) OF PortIndex8 OPTIONAL, -- Need R + rank5-8 SEQUENCE (SIZE (5)) OF PortIndex8 OPTIONAL, -- Need R + rank6-8 SEQUENCE (SIZE (6)) OF PortIndex8 OPTIONAL, -- Need R + rank7-8 SEQUENCE (SIZE (7)) OF PortIndex8 OPTIONAL, -- Need R + rank8-8 SEQUENCE (SIZE (8)) OF PortIndex8 OPTIONAL, -- Need R + }, + portIndex4 SEQUENCE { + rank1-4 PortIndex4 OPTIONAL, -- Need R + rank2-4 SEQUENCE (SIZE (2)) OF PortIndex4 OPTIONAL, -- Need R + rank3-4 SEQUENCE (SIZE (3)) OF PortIndex4 OPTIONAL, -- Need R + rank4-4 SEQUENCE (SIZE (4)) OF PortIndex4 OPTIONAL, -- Need R + }, + portIndex2 SEQUENCE { + rank1-2 PortIndex2 OPTIONAL, -- Need R + rank2-2 SEQUENCE (SIZE (2)) OF PortIndex2 OPTIONAL, -- Need R + }, + portIndex1 NULL +} + +PortIndex8 ::= INTEGER (0..7) +PortIndex4 ::= INTEGER (0..3) +PortIndex2 ::= INTEGER (0..1) + +TDCP-r18 ::= SEQUENCE { + delayDSetOfLengthY-r18 SEQUENCE (SIZE (1.. maxNrofDelayD-r18)) OF DelayD, + phaseReporting-r18 ENUMERATED {enable} OPTIONAL, -- Need R +} + +DelayD ::= ENUMERATED { symb4, slot1, slot2, slot3, slot4, slot5, slot6, slot10 } + +-- TAG-CSI-REPORTCONFIG-STOP +-- ASN1STOP + +``` + + + +| CSI-ReportConfig field descriptions | | +|--------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| carrier | Indicates in which serving cell the CSI-ResourceConfig indicated below are to be found. If the field is absent, the resources are on the same serving cell as this report configuration. | +| codebookConfig | Codebook configuration for Type-1 or Type-2 including codebook subset restriction. Network can only configure one of codebookConfig , codebookConfig-r16 or codebookConfig-r17 or codebookConfig-r18 to a UE. The network includes codebookConfig-v1730 only if codebookConfig-r17 is configured. | +| cqi-BitsPerSubband | This field can only be present if cqi-FormatIndicator is set to subbandCQI . If the field is configured with bits4 , the UE uses 4-bit sub-band CQI. If the field is not present and cqi-FormatIndicator is set to subbandCQI , the UE uses 2-bit sub-band differential CQI. | +| cqi-FormatIndicator | Indicates whether the UE shall report a single (wideband) or multiple (subband) CQI (see TS 38.214 [19], clause 5.2.1.4). | +| cqi-Table | Which CQI table to use for CQI calculation (see TS 38.214 [19], clause 5.2.2.1). For an (e)RedCap UE, CQI table 2 is only supported if the UE indicates support of 256QAM for PD SCH. | +| csi-IM-ResourcesForInterference | CSI IM resources for interference measurement. csi-ResourceConfigId of a CSI-ResourceConfig included in the configuration of the serving cell indicated with the field "carrier" above. The CSI-ResourceConfig indicated here contains only CSI-IM resources. The bwp-Id in that CSI-ResourceConfig is the same value as the bwp-Id in the CSI-ResourceConfig indicated by resourcesForChannelMeasurement . | +| csi-ReportingBand | Indicates a contiguous or non-contiguous subset of subbands in the bandwidth part which CSI shall be reported for. Each bit in the bit-string represents one subband. The right-most bit in the bit string represents the lowest subband in the BWP. The choice determines the number of subbands (subbands3 for 3 subbands, subbands4 for 4 subbands, and so on) (see TS 38.214 [19], clause 5.2.1.4). This field is absent if there are less than 24 PRBs (no sub band) and present otherwise (see TS 38.214 [19], clause 5.2.1.4). | +| csi-ReportMode | Configures the CSI report modes Mode1 or Mode 2 (see TS 38.214 [19], clause 5.2.1.4.2) | +| csi-ReportSubConfigToAddModList | List of CSI-ReportSubConfiguration(s) in a CSI report configuration to add or modify. No simultaneous configuration of portSubsetIndicator and a list of nzp-CSI-RS-resources in a same CSI report configuration. | +| csi-ReportSubConfigToReleaseList | List of CSI-ReportSubConfiguration(s) in a CSI report configuration to release. | +| dummy | This field is not used in the specification. If received it shall be ignored by the UE. | +| groupBasedBeamReporting | Turning on/off group beam based reporting (see TS 38.214 [19], clause 5.2.1.4). If groupBasedBeamReporting (without suffix) is set to disabled, groupBasedBeamReporting-v1710 and groupBasedBeamReporting-v1800 is absent. | +| non-PMI-PortIndication | Port indication for RI/CQI calculation. For each CSI-RS resource in the linked ResourceConfig for channel measurement, a port indication for each rank R, indicating which R ports to use. Applicable only for non-PMI feedback (see TS 38.214 [19], clause 5.2.1.4.2).
The first entry in non-PMI-PortIndication corresponds to the NZP-CSI-RS-Resource indicated by the first entry in nzp-CSI-RS-Resources in the NZP-CSI-RS-ResourceSet indicated in the first entry of nzp-CSI-RS-ResourceSetList of the CSI-ResourceConfig whose CSI-ResourceConfigId is indicated in a CSI-MeasId together with the above CSI-ReportConfigId ; the second entry in non-PMI-PortIndication corresponds to the NZP-CSI-RS-Resource indicated by the second entry in nzp-CSI-RS-Resources in the NZP-CSI-RS-ResourceSet indicated in the first entry of nzp-CSI-RS-ResourceSetList of the same CSI-ResourceConfig , and so on until the NZP-CSI-RS-Resource indicated by the last entry in nzp-CSI-RS-Resources in the in the NZP-CSI-RS-ResourceSet indicated in the first entry of nzp-CSI-RS-ResourceSetList of the same CSI-ResourceConfig . Then | + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| the next entry corresponds to the NZP-CSI-RS-Resource indicated by the first entry in nzp-CSI-RS-Resources in the NZP-CSI-RS-ResourceSet indicated in the second entry of nzp-CSI-RS-ResourceSetList of the same CSI-ResourceConfig and so on. | +| nrofReportedGroups
Number of reported resource groups per CSI-report. Value n1 means one resource group, n2 means 2 resource groups, and so on. If nrofReportedGroups is configured, the UE ignores groupBasedBeamReporting (without suffix). | +| nrofReportedRS
The number (N) of measured RS resources to be reported per report setting in a non-group-based report. $N \leq N\_max$ , where $N\_max$ is either 2 or 4 depending on UE capability.
(see TS 38.214 [19], clause 5.2.1.4) When the field is absent the UE applies the value 1. | +| numberOfSingleTRP-CSI-Mode1
Configures the number of reported X CSIs when csi-ReportMode is set to 'Mode 1' as described in TS 38.214 [19], clause 5.2.1.4.2. The field is present only if csi-ReportMode configures Mode 1. | +| nzp-CSI-RS-ResourcesForInterference
NZP CSI RS resources for interference measurement. csi-ResourceConfigId of a CSI-ResourceConfig included in the configuration of the serving cell indicated with the field "carrier" above. The CSI-ResourceConfig indicated here contains only NZP-CSI-RS resources. The bwp-Id in that CSI-ResourceConfig is the same value as the bwp-Id in the CSI-ResourceConfig indicated by resourcesForChannelMeasurement . | +| p0alpha
Index of the p0-alpha set determining the power control for this CSI report transmission (see TS 38.214 [19], clause 6.2.1.2). | +| pdsch-BundleSizeForCSI
PRB bundling size to assume for CQI calculation when reportQuantity is CRI/RI/i1/CQI. If the field is absent, the UE assumes that no PRB bundling is applied (see TS 38.214 [19], clause 5.2.1.4.2). | +| pmi-FormatIndicator
Indicates whether the UE shall report a single (wideband) or multiple (subband) PMI. (see TS 38.214 [19], clause 5.2.1.4). | +| pucch-CSI-ResourceList
Indicates which PUCCH resource to use for reporting on PUCCH. | +| reportConfigType
Time domain behavior of reporting configuration. | +| reportFreqConfiguration
Reporting configuration in the frequency domain. (see TS 38.214 [19], clause 5.2.1.4). | +| reportQuantity
The CSI related quantities to report. see TS 38.214 [19], clause 5.2.1. If the field reportQuantity-r16 , reportQuantity-r17 or reportQuantity-r18 is present, UE shall ignore reportQuantity (without suffix). Network does not configure reportQuantity-r17 or reportQuantity-r18 together with reportQuantity-r16 . | +| reportingMode
Configures the UE with reporting mode for group based reporting.(see TS XXXXX) | +| reportSlotConfig
Periodicity and slot offset (see TS 38.214 [19], clause 5.2.1.4). If the field reportSlotConfig-v1530 is present, the UE shall ignore the value provided in reportSlotConfig (without suffix). | +| reportSlotOffsetList, reportSlotOffsetListDCI-0-1, reportSlotOffsetListDCI-0-2
Timing offset Y for semi persistent reporting using PUSCH. This field lists the allowed offset values. This list must have the same number of entries as the pusch-TimeDomainAllocationList in PUSCH-Config . A particular value is indicated in DCI. The network indicates in the DCI field of the UL grant, which of the configured report slot offsets the UE shall apply. The DCI value 0 corresponds to the first report slot offset in this list, the DCI value 1 corresponds to the second report slot offset in this list, and so on. The first report is transmitted in slot $n+Y$ , second report in $n+Y+P$ , where P is the configured periodicity.
Timing offset Y for aperiodic reporting using PUSCH. This field lists the allowed offset values. This list must have the same number of entries as the pusch-TimeDomainAllocationList in PUSCH-Config . A particular value is indicated in DCI. The network indicates in the DCI field of the UL grant, which of the configured report slot | + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

offsets the UE shall apply. The DCI value 0 corresponds to the first report slot offset in this list, the DCI value 1 corresponds to the second report slot offset in this list, and so on (see TS 38.214 [19], clause 6.1.2.1).

The field reportSlotOffsetListDCI-0-1 applies to DCI format 0_1 and the field reportSlotOffsetListDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.2.1).

The fields reportSlotOffsetList-r17, reportSlotOffsetListDCI-0-1-r17 and reportSlotOffsetListDCI-0-2-r17 are only applicable for SCS 480 kHz and 960 kHz and if they are configured, the UE shall ignore the fields reportSlotOffsetList (without suffix), reportSlotOffsetListDCI-0-1 (without suffix) and reportSlotOffsetListDCI-0-2 (without suffix) for SCS 480 kHz and 960 kHz.

| +|

resourcesForChannelMeasurement

Resources for channel measurement. csi-ResourceConfigId of a CSI-ResourceConfig included in the configuration of the serving cell indicated with the field "carrier" above. The CSI-ResourceConfig indicated here contains only NZP-CSI-RS resources and/or SSB resources. This CSI-ReportConfig is associated with the DL BWP indicated by bwp-Id in that CSI-ResourceConfig.

| +|

sharedCMR

Enables sharing of channel measurement resources between different CSI measurement hypotheses when (1) csi-ReportMode is set to 'Mode1' and numberOfSingleTRP-CSI-Mode1 is set to 1 or 2; or (2) csi-ReportMode is set to 'Mode2' (see TS 38.214 [19], clause 5.2.1.4.2).

| +|

subbandSize

Indicates one out of two possible BWP-dependent values for the subband size as indicated in TS 38.214 [19], table 5.2.1.4-2 . If csi-ReportingBand is absent, the UE shall ignore this field.

| +|

timeRestrictionForChannelMeasurements

Time domain measurement restriction for the channel (signal) measurements (see TS 38.214 [19], clause 5.2.1.1).

| +|

timeRestrictionForInterferenceMeasurements

Time domain measurement restriction for interference measurements (see TS 38.214 [19], clause 5.2.1.1).

| + +| PortIndexFor8Ranks field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

portIndex8

Port-Index configuration for up to rank 8. If present, the network configures port indexes for at least one of the ranks.

| +|

portIndex4

Port-Index configuration for up to rank 4. If present, the network configures port indexes for at least one of the ranks.

| +|

portIndex2

Port-Index configuration for up to rank 2. If present, the network configures port indexes for at least one of the ranks.

| +|

portIndex1

Port-Index configuration for rank 1.

| + +| TDCP field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

delayDSetOfLengthY

Configures a set of Y delay values for TDCP reporting, see reference TS 38.214 clause 5.2.1.4. The symb4 denotes 4 symbols, the slot1 denotes 1 slot, the slot2 denotes 2 slots and so on. The value slot10 is applicable only to SCS >=30kHz. The parameter Y, see reference TS38.214 clause 5.2.1.4, is given by the length of the set of D values.

| +|

phaseReporting

Configures the UE for phase reporting for TDCP reporting see reference TS 38.214 clause 5.2.1.4

| + +#### CSI-ReportConfigId + +The IE *CSI-ReportConfigId* is used to identify one *CSI-ReportConfig*. + +#### CSI-ReportConfigId information element + +``` +-- ASN1START +-- TAG-CSI-REPORTCONFIGID-START + +CSI-ReportConfigId ::= INTEGER (0..maxNrofCSI-ReportConfigurations-1) + +-- TAG-CSI-REPORTCONFIGID-STOP +-- ASN1STOP +``` + +### CSI-ReportSubConfig + +The IE *CSI-ReportSubConfig* is used to configure parameters in one sub-configuration within a CSI report configuration. + +#### CSI-ReportSubConfig information element + +``` +-- ASN1START +-- TAG-CSI-REPORTSUBCONFIG-START + +CSI-ReportSubConfig-r18 ::= SEQUENCE { + reportSubConfigId-r18 CSI-ReportSubConfigId-r18, + portSubsetIndicator-r18 CHOICE { + p2 BIT STRING (SIZE (2)), + p4 BIT STRING (SIZE (4)), + p8 BIT STRING (SIZE (8)), + p12 BIT STRING (SIZE (12)), + p16 BIT STRING (SIZE (16)), + p24 BIT STRING (SIZE (24)), + p32 BIT STRING (SIZE (32)) + } + nzp-CSI-RS-ResourceList-r18 SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourcesPerSet)) OF NZP-CSI-RS-ResourceIndex + powerOffset-r18 INTEGER (0..23) +} + +NZP-CSI-RS-ResourceIndex ::= INTEGER (0..maxNrofNZP-CSI-RS-ResourcesPerSet-1-r18) + +-- TAG-CSI-REPORTSUBCONFIG-STOP +-- ASN1STOP +``` + +| CSI-ReportSubConfig field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| port-subsetIndicator
Indicates the number of ports of the NZP CSI-RS resources indicated in nzp-CSI-RS-resourceList (the value is the same like portNumber of these NZP CSI-RS resources) and the (sub)set of CSI-RS antenna ports used for CSI calculation of the sub-configuration. In the bit string, each bit corresponds to an antenna port. When a bit is set to 1, the corresponding port is enabled for CSI calculation corresponding to the sub-configuration. When the bit is set to zero, the corresponding port is not enabled for CSI calculation corresponding to the sub-configuration. | +| nzp-CSI-RS-resourceList
List of NZP CSI RS resources for the sub-configuration that is a (sub)set of NZP CSI-RS resource(s) of the CSI-RS resource set for channel measurement associated with the sub-configuration in the CSI report configuration. Value 0 refers to the first NZP CSI RS resource of the CSI-RS resource set, value 1 refers to the second NZP CSI RS resource of the CSI-RS resource set, and so on. | +| powerOffset
When powerControlOffset is configured in a NZP CSI-RS resources indicated by nzp-CSI-RS-Resources , the power offset of PDSCH RE to NZP CSI-RS RE is equal to powerControlOffset - powerOffset . | + +#### – CSI-ReportSubConfigId + +The IE *CSI-ReportSubConfigId* is used to indicate the index of one *CSI-ReportSubConfig* within a CSI report configuration. + +#### **CSI-ReportSubConfigId information element** + +``` +-- ASN1START +-- TAG-CSI-REPORTSUBCONFIGID-START + +CSI-ReportSubConfigId-r18 ::= INTEGER (0..maxNrofCSI-ReportSubconfigPerCSI-ReportConfig-1-r18) + +-- TAG-CSI-REPORTSUBCONFIGID-STOP +-- ASN1STOP +``` + +#### – CSI-ReportSubConfigTriggerList + +The IE *CSI-ReportSubConfigTriggerList* is used to configure a list of sub-configuration ID(s) of N sub-configurations out of L configured sub-configurations within a CSI-ReportConfig associated with a triggering state for semi-persistent CSI reporting on PUSCH and aperiodic CSI reporting. + +#### **CSI-ReportSubConfigTriggerList information element** + +``` +-- ASN1START +-- TAG-CSI-REPORTSUBCONFIGTRIGGERLIST-START + +CSI-ReportSubConfigTriggerList-r18 ::= SEQUENCE (SIZE(1..maxNrofCSI-ReportSubconfigPerCSI-ReportConfig-r18)) OF CSI-ReportSubConfigId-r18 + +-- TAG-CSI-REPORTSUBCONFIGTRIGGERLIST-STOP +-- ASN1STOP +``` + +### CSI-ResourceConfig + +The IE *CSI-ResourceConfig* defines a group of one or more *NZP-CSI-RS-ResourceSet*, *CSI-IM-ResourceSet* and/or *CSI-SSB-ResourceSet*. + +#### CSI-ResourceConfig information element + +``` +-- ASN1START +-- TAG-CSI-RESOURCECONFIG-START + +CSI-ResourceConfig ::= SEQUENCE { + csi-ResourceConfigId CSI-ResourceConfigId, + csi-RS-ResourceSetList CHOICE { + nzp-CSI-RS-SSB SEQUENCE { + nzp-CSI-RS-ResourceSetList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig)) OF NZP-CSI-RS-ResourceSetId + csi-SSB-ResourceSetList SEQUENCE (SIZE (1..maxNrofCSI-SSB-ResourceSetsPerConfig)) OF CSI-SSB-ResourceSetId OPTIONAL, -- Need R + }, + csi-IM-ResourceSetList SEQUENCE (SIZE (1..maxNrofCSI-IM-ResourceSetsPerConfig)) OF CSI-IM-ResourceSetId OPTIONAL, -- Need R + }, + bwp-Id BWP-Id, + resourceType ENUMERATED { aperiodic, semiPersistent, periodic }, + ... + [[ + csi-SSB-ResourceSetListExt-r17 CSI-SSB-ResourceSetId OPTIONAL -- Need R + ]] +} + +-- TAG-CSI-RESOURCECONFIG-STOP +-- ASN1STOP +``` + +| CSI-ResourceConfig field descriptions | | +|------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| bwp-Id | The DL BWP which the CSI-RS associated with this CSI-ResourceConfig are located in (see TS 38.214 [19], clause 5.2.1.2). | +| csi-IM-ResourceSetList | List of references to CSI-IM resources used for CSI measurement and reporting in a CSI-RS resource set. Contains up to maxNrofCSI-IM-ResourceSetsPerConfig resource sets if resourceType is 'aperiodic' and 1 otherwise (see TS 38.214 [19], clause 5.2.1.2). | +| csi-ResourceConfigId | Used in CSI-ReportConfig to refer to an instance of CSI-ResourceConfig . | +| csi-SSB-ResourceSetList, csi-SSB-ResourceSetListExt | List of references to SSB resources used for CSI measurement and reporting in a CSI-RS resource set (see TS 38.214 [19], clause 5.2.1.2). The csi-SSB-ResourceSetListExt provides additional references and can only be configured if csi-SSB-ResourceSetList is configured and groupBasedBeamReporting-v1710 is configured in the CSI-ReportConfig that indicates this CSI-ResourceConfig as resourcesForChannelMeasurement . If groupBasedBeamReporting-v1710 is configured in the IE CSI-ReportConfig that indicates this CSI-ResourceConfig as resourceForChannelMeasurement , the network configures 2 resource sets, which may be two CSI SSB resource sets (see TS 38.214 [19], clause 5.2.1.2 and 5.2.1.4.2). In this case, in TS 38.212 [17] Table 6.3.1.1.2-8B, the first resource set is indicated by a resource set indicator set to 0 and the second resource set by a resource set indicator set to 1. | +| nzp-CSI-RS-ResourceSetList | List of references to NZP CSI-RS resources used for beam measurement and reporting in a CSI-RS resource set.
If resourceType is set to 'aperiodic', the network configures up to maxNrofNZP-CSI-RS-ResourceSetsPerConfig resource sets. If resourceType is set to 'periodic' or 'semiPersistent' and groupBasedBeamReporting-v1710 is not configured in IE CSI-ReportConfig , the network configures 1 resource set. If resourceType is set to 'periodic' or 'semiPersistent' and groupBasedBeamReporting-v1710 is configured, the network configures 2 resource sets, which may be two NZP CSI-RS resource sets (see TS 38.214 [19], clause 5.2.1.2 and 5.2.1.4.2). In this case, in TS 38.212 [17] Table 6.3.1.1.2-8B, the first resource set is indicated by a resource set indicator set to 0 and the second resource set by a resource set indicator set to 1. If resourceType is set to 'periodic' and reportQuantity is set to 'TDCP', the network configures up to 3 resource sets, see TS 38.3xx. | +| resourceType | Time domain behavior of resource configuration (see TS 38.214 [19], clause 5.2.1.2). It does not apply to resources provided in the csi-SSB-ResourceSetList . | + +#### CSI-ResourceConfigId + +The IE *CSI-ResourceConfigId* is used to identify a *CSI-ResourceConfig*. + +#### CSI-ResourceConfigId information element + +``` +-- ASN1START +-- TAG-CSI-RESOURCECONFIGID-START + +CSI-ResourceConfigId ::= INTEGER (0..maxNrofCSI-ResourceConfigurations-1) + +-- TAG-CSI-RESOURCECONFIGID-STOP +-- ASN1STOP +``` + +#### CSI-ResourcePeriodicityAndOffset + +The IE *CSI-ResourcePeriodicityAndOffset* is used to configure a periodicity and a corresponding offset for periodic and semi-persistent CSI resources, and for periodic and semi-persistent reporting on PUCCH. both, the periodicity and the offset are given in number of slots. The periodicity value *slots4* corresponds to 4 slots, value *slots5* corresponds to 5 slots, and so on. + +#### CSI-ResourcePeriodicityAndOffset information element + +``` +-- ASN1START +-- TAG-CSI-RESOURCEPERIODICITYANDOFFSET-START + +CSI-ResourcePeriodicityAndOffset ::= CHOICE { + slots4 INTEGER (0..3), + slots5 INTEGER (0..4), + slots8 INTEGER (0..7), + slots10 INTEGER (0..9), + slots16 INTEGER (0..15), + slots20 INTEGER (0..19), + slots32 INTEGER (0..31), + slots40 INTEGER (0..39), + slots64 INTEGER (0..63), + slots80 INTEGER (0..79), + slots160 INTEGER (0..159), + slots320 INTEGER (0..319), + slots640 INTEGER (0..639) +} + +-- TAG-CSI-RESOURCEPERIODICITYANDOFFSET-STOP +-- ASN1STOP +``` + +#### CSI-RS-ResourceConfigMobility + +The IE *CSI-RS-ResourceConfigMobility* is used to configure CSI-RS based RRM measurements. + +#### CSI-RS-ResourceConfigMobility information element + +``` +-- ASN1START +-- TAG-CSI-RS-RESOURCECONFIGMOBILITY-START + +CSI-RS-ResourceConfigMobility ::= SEQUENCE { + subcarrierSpacing SubcarrierSpacing, + csi-RS-CellList-Mobility SEQUENCE (SIZE (1..maxNrofCSI-RS-CellsRRM)) OF CSI-RS-CellMobility, + ... + [[ + refServCellIndex ServCellIndex + ]] +} +-- TAG-CSI-RS-RESOURCECONFIGMOBILITY-STOP +-- ASN1STOP +``` + +``` + +} + +CSI-RS-CellMobility := SEQUENCE { + cellId PhysCellId, + csi-rs-MeasurementBW SEQUENCE { + nrofPRBs ENUMERATED { size24, size48, size96, size192, size264}, + startPRB INTEGER(0..2169) + }, + density ENUMERATED {d1,d3} OPTIONAL, -- Need R + csi-rs-ResourceList-Mobility SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesRRM)) OF CSI-RS-Resource-Mobility +} + +CSI-RS-Resource-Mobility := SEQUENCE { + csi-RS-Index CSI-RS-Index, + slotConfig CHOICE { + ms4 INTEGER (0..31), + ms5 INTEGER (0..39), + ms10 INTEGER (0..79), + ms20 INTEGER (0..159), + ms40 INTEGER (0..319) + }, + associatedSSB SEQUENCE { + ssb-Index SSB-Index, + isQuasiColocated BOOLEAN + } + OPTIONAL, -- Need R + frequencyDomainAllocation CHOICE { + row1 BIT STRING (SIZE (4)), + row2 BIT STRING (SIZE (12)) + }, + firstOFDMSymbolInTimeDomain INTEGER (0..13), + sequenceGenerationConfig INTEGER (0..1023), + ..., + [[ + slotConfig-r17 CHOICE { + ms4 INTEGER (0..255), + ms5 INTEGER (0..319), + ms10 INTEGER (0..639), + ms20 INTEGER (0..1279), + ms40 INTEGER (0..2559) + } + ]] + OPTIONAL -- Need R +} + +CSI-RS-Index := INTEGER (0..maxNrofCSI-RS-ResourcesRRM-1) + +-- TAG-CSI-RS-RESOURCECONFIGMOBILITY-STOP +-- ASN1STOP + +``` + +| CSI-RS-CellMobility field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| csi-rs-ResourceList-Mobility
List of CSI-RS resources for mobility. The maximum number of CSI-RS resources that can be configured per measObjectNR depends on the configuration of associatedSSB and the support of increasedNumberOfCSIRSPerMO capability (see TS 38.214 [19], clause 5.1.6.1.3). | +| density
Frequency domain density for the 1-port CSI-RS for L3 mobility. See TS 38.211 [16], clause 7.4.1. | +| nrofPRBs
Allowed size of the measurement BW in PRBs. See TS 38.211 [16], clause 7.4.1. | +| startPRB
Starting PRB index of the measurement bandwidth. See TS 38.211 [16], clause 7.4.1. | + +| CSI-RS-ResourceConfigMobility field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| csi-RS-CellList-Mobility
List of cells for CSI-RS based RRM measurements. | +| refServCellIndex
Indicates the serving cell providing the timing reference for CSI-RS resources without associatedSSB . The field may be present only if there is at least one CSI-RS resource configured without associatedSSB . If this field is absent, the UE shall use the timing of the PCell for measurements on the CSI-RS resources without associatedSSB . The CSI-RS resources and the serving cell indicated by refServCellIndex for timing reference should be located in the same band. | +| subcarrierSpacing
Subcarrier spacing of CSI-RS.
Only the following values are applicable depending on the used frequency:
FR1: 15, 30, or 60 kHz
FR2-1: 60 or 120 kHz
FR2-2: 120, 480, or 960 kHz | + +| CSI-RS-Resource-Mobility field descriptions | | +|----------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| associatedSSB | If this field is present, the UE may base the timing of the CSI-RS resource indicated in CSI-RS-Resource-Mobility on the timing of the cell indicated by the cellId in the CSI-RS-CellMobility . In this case, the UE is not required to monitor that CSI-RS resource if the UE cannot detect the SS/PBCH block indicated by this associatedSSB and cellId . If this field is absent, the UE shall base the timing of the CSI-RS resource indicated in CSI-RS-Resource-Mobility on the timing of the serving cell indicated by refServCellIndex . In this case, the UE is required to measure the CSI-RS resource even if SS/PBCH block(s) with cellId in the CSI-RS-CellMobility are not detected. CSI-RS resources with and without associatedSSB may be configured in accordance with the rules in TS 38.214 [19], clause 5.1.6.1.3. | +| csi-RS-Index | CSI-RS resource index associated to the CSI-RS resource to be measured (and used for reporting). | +| firstOFDMSymbolInTimeDomain | Time domain allocation within a physical resource block. The field indicates the first OFDM symbol in the PRB used for CSI-RS, see TS 38.211 [16], clause 7.4.1.5.3. | +| frequencyDomainAllocation | Frequency domain allocation within a physical resource block in accordance with TS 38.211 [16], clause 7.4.1.5.3 including table 7.4.1.5.2-1. The number of bits that may be set to one depend on the chosen row in that table. | +| isQuasiColocated | Indicates that the CSI-RS resource is quasi co-located with the associated SS/PBCH block, see TS 38.214 [19], clause 5.1.6.1.3. | +| sequenceGenerationConfig | Scrambling ID for CSI-RS (see TS 38.211 [16], clause 7.4.1.5.2). | +| slotConfig | Indicates the CSI-RS periodicity (in milliseconds) and for each periodicity the offset (in number of slots). When subcarrierSpacing is set to kHz15 , the maximum offset values for periodicities ms4/ms5/ms10/ms20/ms40 are 3/4/9/19/39 slots. When subcarrierSpacing is set to kHz30 , the maximum offset values for periodicities ms4/ms5/ms10/ms20/ms40 are 7/9/19/39/79 slots. When subcarrierSpacing is set to kHz60 , the maximum offset values for periodicities ms4/ms5/ms10/ms20/ms40 are 15/19/39/79/159 slots. When subcarrierSpacing is set to kHz120 , the maximum offset values for periodicities ms4/ms5/ms10/ms20/ms40 are 31/39/79/159/319 slots. When subcarrierSpacing is set to kHz480 , the maximum offset values for periodicities ms4/ms5/ms10/ms20/ms40 are 127/159/319/639/1279 slots. When subcarrierSpacing is set to kHz960 , the maximum offset values for periodicities ms4/ms5/ms10/ms20/ms40 are 255/319/639/1279/2559 slots. If slotConfig-r17 is present, UE shall ignore the slotConfig (without suffix). | + +#### – CSI-RS-ResourceMapping + +The IE *CSI-RS-ResourceMapping* is used to configure the resource element mapping of a CSI-RS resource in time- and frequency domain. + +#### *CSI-RS-ResourceMapping* information element + +``` +-- ASN1START +-- TAG-CSI-RS-RESOURCEMAPPING-START + +CSI-RS-ResourceMapping ::= SEQUENCE { + frequencyDomainAllocation CHOICE { + row1 BIT STRING (SIZE (4)), + row2 BIT STRING (SIZE (12)), + row4 BIT STRING (SIZE (3)), + other BIT STRING (SIZE (6)) + }, + nrofPorts ENUMERATED {p1,p2,p4,p8,p12,p16,p24,p32}, + ... +``` + +``` + +firstOFDMSymbolInTimeDomain INTEGER (0..13), +firstOFDMSymbolInTimeDomain2 INTEGER (2..12) OPTIONAL, -- Need R +cdm-Type ENUMERATED {noCDM, fd-CDM2, cdm4-FD2-TD2, cdm8-FD2-TD4}, +density CHOICE { + dot5 ENUMERATED {evenPRBs, oddPRBs}, + one NULL, + three NULL, + spare NULL +}, +freqBand CSI-FrequencyOccupation, +... +} + +-- TAG-CSI-RS-RESOURCEMAPPING-STOP +-- ASN1STOP + +``` + +| CSI-RS-ResourceMapping field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| cdm-Type
CDM type (see TS 38.214 [19], clause 5.2.2.3.1). | +| density
Density of CSI-RS resource measured in RE/port/PRB (see TS 38.211 [16], clause 7.4.1.5.3).
Values 0.5 ( dot5 ), 1 ( one ) and 3 ( three ) are allowed for X=1, values 0.5 ( dot5 ) and 1 ( one ) are allowed for X=2, 16, 24 and 32, value 1 ( one ) is allowed for X=4, 8, 12.
For density = 1/2, includes 1-bit indication for RB level comb offset indicating whether odd or even RBs are occupied by CSI-RS. | +| firstOFDMSymbolInTimeDomain2
Time domain allocation within a physical resource block. See TS 38.211 [16], clause 7.4.1.5.3. | +| firstOFDMSymbolInTimeDomain
Time domain allocation within a physical resource block. The field indicates the first OFDM symbol in the PRB used for CSI-RS. See TS 38.211 [16], clause 7.4.1.5.3. | +| freqBand
Wideband or partial band CSI-RS, (see TS 38.214 [19], clause 5.2.2.3.1). | +| frequencyDomainAllocation
Frequency domain allocation within a physical resource block in accordance with TS 38.211 [16], clause 7.4.1.5.3. The applicable row number in table 7.4.1.5.3-1 is determined by the frequencyDomainAllocation for rows 1, 2 and 4, and for other rows by matching the values in the column Ports, Density and CDMtype in table 7.4.1.5.3-1 with the values of nrofPorts , cdm-Type and density below and, when more than one row has the 3 values matching, by selecting the row where the column (k bar, l bar) in table 7.4.1.5.3-1 has indexes for k ranging from 0 to 2*n-1 where n is the number of bits set to 1 in frequencyDomainAllocation . | +| nrofPorts
Number of ports (see TS 38.214 [19], clause 5.2.2.3.1). | + +#### CSI-SemiPersistentOnPUSCH-TriggerStateList + +The *CSI-SemiPersistentOnPUSCH-TriggerStateList* IE is used to configure the UE with list of trigger states for semi-persistent reporting of channel state information on L1. See also TS 38.214 [19], clause 5.2. + +#### CSI-SemiPersistentOnPUSCH-TriggerStateList information element + +``` + +-- ASN1START +-- TAG-CSI-SEMIPERSISTENTONPUSCHTRIGGERSTATELIST-START + +CSI-SemiPersistentOnPUSCH-TriggerStateList ::= SEQUENCE (SIZE (1..maxNrOfSemiPersistentPUSCH-Triggers)) OF CSI-SemiPersistentOnPUSCH-TriggerState + +CSI-SemiPersistentOnPUSCH-TriggerState ::= SEQUENCE { + associatedReportConfigInfo CSI-ReportConfigId, + ... + [[ + sp-CSI-MultiplexingMode-r17 ENUMERATED {enabled} OPTIONAL -- Need R + ]], + [[ + csi-ReportSubConfigTriggerList-r18 CSI-ReportSubConfigTriggerList-r18 OPTIONAL, -- Need R + ltm-AssociatedReportConfigInfo-r18 LTM-CSI-ReportConfigId-r18 OPTIONAL -- Need R + ]] +} + +-- TAG-CSI-SEMIPERSISTENTONPUSCHTRIGGERSTATELIST-STOP +-- ASN1STOP + +``` + +#### CSI-SemiPersistentOnPUSCH-TriggerStateList field descriptions + +| | | +|---------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| csi-ReportSubConfigTriggerList | A list of sub-configuration ID(s) of N sub-configurations out of L configured sub-configurations within a CSI-ReportConfig associated with a triggering state for semi-persistent CSI reporting on PUSCH. | +| ltm-AssociatedReportConfigInfo | This field configures the aperiodic CSI reports of LTM candidate cells. If ltm-associatedReportConfigInfo is configured the UE shall ignore the field associatedReportConfigInfo . | +| sp-CSI-MultiplexingMode | Indicates if the behavior of transmitting SP-CSI on the first PUSCH repetitions corresponding to two SRS resource sets configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 with usage 'codebook' or 'noncodebook' is enabled or not. | + +### CSI-SSB-ResourceSet + +The IE *CSI-SSB-ResourceSet* is used to configure one SS/PBCH block resource set which refers to SS/PBCH as indicated in *ServingCellConfigCommon* and *ServingCellConfig*. + +#### CSI-SSB-ResourceSet information element + +``` + +-- ASN1START +-- TAG-CSI-SSB-RESOURCESET-START + +CSI-SSB-ResourceSet ::= SEQUENCE { + csi-SSB-ResourceSetId CSI-SSB-ResourceSetId, + csi-SSB-ResourceList SEQUENCE (SIZE (1..maxNrOfCSI-SSB-ResourcePerSet)) OF SSB-Index, + ... +} + +``` + +``` + +[[ + servingAdditionalPCIList-r17 SEQUENCE (SIZE(1..maxNrofCSI-SSB-ResourcePerSet)) OF ServingAdditionalPCIIndex-r17 OPTIONAL -- Need R +]] +} + +ServingAdditionalPCIIndex-r17 := INTEGER(0..maxNrofAdditionalPCI-r17) + +-- TAG-CSI-SSB-RESOURCESET-STOP +-- ASN1STOP + +``` + +#### CSI-SSB-ResourceSet field descriptions + +##### **servingAdditionalPCIList** + +Indicates the physical cell IDs (PCI) of the SSBs in the *csi-SSB-ResourceList*. If present, the list has the same number of entries as *csi-SSB-ResourceList*. The first entry of the list indicates the value of the PCI for the first entry of *csi-SSB-ResourceList*, the second entry of this list indicates the value of the PCI for the second entry of *csi-SSB-ResourceList*, and so on. For each entry, the following applies: + +- If the value is zero, the PCI is the PCI of the serving cell in which this *CSI-SSB-ResourceSet* is defined; +- otherwise, the value is *additionalPCIIndex-r17* of an *SSB-MTC-AdditionalPCI-r17* configured using the *additionalPCI-ToAddModList-r17* in *ServingCellConfig*, and the PCI is the *additionalPCI-r17* in this *SSB-MTC-AdditionalPCI-r17*. + +#### — **CSI-SSB-ResourceSetId** + +The IE *CSI-SSB-ResourceSetId* is used to identify one SS/PBCH block resource set. + +#### CSI-SSB-ResourceId information element + +``` + +-- ASN1START +-- TAG-CSI-SSB-RESOURCESETID-START + +CSI-SSB-ResourceSetId := INTEGER (0..maxNrofCSI-SSB-ResourceSets-1) + +-- TAG-CSI-SSB-RESOURCESETID-STOP +-- ASN1STOP + +``` + +# — **DedicatedNAS-Message** + +The IE *DedicatedNAS-Message* is used to transfer UE specific NAS layer information between the 5GC CN and the UE. The RRC layer is transparent for this information. + +### DedicatedNAS-Message information element + +``` + +-- ASN1START +-- TAG-DEDICATED-NAS-MESSAGE-START + +DedicatedNAS-Message := OCTET STRING + +``` + +``` +-- TAG-DEDICATED-NAS-MESSAGE-STOP +-- ASN1STOP +``` + +### DL-PPW-PreConfig + +The IE *DL-PPW-PreConfig* provides configuration for a measurement window where a UE is expected to measure the DL PRS, if it is inside the active DL BWP and with the same numerology as the active DL BWP. Based upon the indication received in the configuration, the UE identifies whether the DL PRS priority is higher than that of the other DL signals or channels and accordingly determines, for example, the UE is expected to measure the DL PRS and is not expected to receive other DL signals and channels. + +#### DL-PPW-PreConfig information element + +``` +-- ASN1START +-- TAG-DL-PPW-PRECONFIG-START + +DL-PPW-PreConfig-r17 ::= SEQUENCE { + dl-PPW-ID-r17 DL-PPW-ID-r17, + dl-PPW-PeriodicityAndStartSlot-r17 DL-PPW-PeriodicityAndStartSlot-r17, + length-r17 INTEGER (1..160), + type-r17 ENUMERATED {type1A, type1B, type2} OPTIONAL, -- Cond MultiType + priority-r17 ENUMERATED {st1, st2, st3} OPTIONAL -- Cond MultiState +} + +DL-PPW-ID-r17 ::= INTEGER (0..maxNrofPPW-ID-1-r17) + +DL-PPW-PeriodicityAndStartSlot-r17 ::= CHOICE { + scs15 CHOICE { + n4 INTEGER (0..3), + n5 INTEGER (0..4), + n8 INTEGER (0..7), + n10 INTEGER (0..9), + n16 INTEGER (0..15), + n20 INTEGER (0..19), + n32 INTEGER (0..31), + n40 INTEGER (0..39), + n64 INTEGER (0..63), + n80 INTEGER (0..79), + n160 INTEGER (0..159), + n320 INTEGER (0..319), + n640 INTEGER (0..639), + n1280 INTEGER (0..1279), + n2560 INTEGER (0..2559), + n5120 INTEGER (0..5119), + n10240 INTEGER (0..10239), + ... + }, + scs30 CHOICE { + n8 INTEGER (0..7), + n10 INTEGER (0..9), + } +} +``` + +``` + n16 INTEGER (0..15), + n20 INTEGER (0..19), + n32 INTEGER (0..31), + n40 INTEGER (0..39), + n64 INTEGER (0..63), + n80 INTEGER (0..79), + n128 INTEGER (0..127), + n160 INTEGER (0..159), + n320 INTEGER (0..319), + n640 INTEGER (0..639), + n1280 INTEGER (0..1279), + n2560 INTEGER (0..2559), + n5120 INTEGER (0..5119), + n10240 INTEGER (0..10239), + n20480 INTEGER (0..20479), + ... +}, +scs60 CHOICE { + n16 INTEGER (0..15), + n20 INTEGER (0..19), + n32 INTEGER (0..31), + n40 INTEGER (0..39), + n64 INTEGER (0..63), + n80 INTEGER (0..79), + n128 INTEGER (0..127), + n160 INTEGER (0..159), + n256 INTEGER (0..255), + n320 INTEGER (0..319), + n640 INTEGER (0..639), + n1280 INTEGER (0..1279), + n2560 INTEGER (0..2559), + n5120 INTEGER (0..5119), + n10240 INTEGER (0..10239), + n20480 INTEGER (0..20479), + n40960 INTEGER (0..40959), + ... +}, +scs120 CHOICE { + n32 INTEGER (0..31), + n40 INTEGER (0..39), + n64 INTEGER (0..63), + n80 INTEGER (0..79), + n128 INTEGER (0..127), + n160 INTEGER (0..159), + n256 INTEGER (0..255), + n320 INTEGER (0..319), + n512 INTEGER (0..511), + n640 INTEGER (0..639), + n1280 INTEGER (0..1279), + n2560 INTEGER (0..2559), + n5120 INTEGER (0..5119), +``` + +``` + + n10240 INTEGER (0..10239), + n20480 INTEGER (0..20479), + n40960 INTEGER (0..40959), + n81920 INTEGER (0..81919), + ... + }, + ... +} + +-- TAG-DL-PPW-PRECONFIG-STOP +-- ASN1STOP + +``` + +#### DL-PPW-PreConfig field descriptions + +| | | +|---------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| dl-PPW-ID | Indicates the pre-configured ID for DL-PRS processing window configuration. | +| dl-PPW-PeriodicityAndStartSlot | Indicates the periodicity in slots and the offset of the starting slot with respect to SFN #0 slot #0 of the serving cell where the DL-PRS processing window is configured. | +| length | Indicates the length of DL-PRS processing window in slots. Value 1 indicates length of one slot, value 2 indicates length of two slots and so on. | +| priority | Indicates the priority between PDCCH/PDSCH/CSI-RS and PRS as specified in TS 38.214 [19]. | +| type | Indicates the DL-PRS processing window type as specified in TS 38.214 [19]. | + +| Conditional Presence | Explanation | +|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| MultiType | The field is mandatory present when the UE reports its capability on supporting multiple processing types, otherwise it is absent. | +| MultiState | The field is mandatory present when the UE reports its capability on supporting option 1 or option 2 for the configured type, otherwise it is absent. | + +## DMRS-BundlingPUCCH-Config + +The IE *DMRS-BundlingPUCCH-Config-r17* is used to configure DMRS bundling for PUCCH. + +### DMRS-BundlingPUCCH-Config information element + +``` + +-- ASN1START +-- TAG-DMRS-BUNDLINGPUCCH-CONFIG-START + +DMRS-BundlingPUCCH-Config-r17 ::= SEQUENCE { + pucch-DMRS-Bundling-r17 ENUMERATED {enabled} OPTIONAL, -- Need R + pucch-TimeDomainWindowLength-r17 INTEGER (2..8) OPTIONAL, -- Need S + pucch-WindowRestart-r17 ENUMERATED {enabled} OPTIONAL, -- Need R + pucch-FrequencyHoppingInterval-r17 ENUMERATED {s2, s4, s5, s10} OPTIONAL, -- Need S +} + +``` + +``` + + ... +} + +-- TAG-DMRS-BUNDLINGPUCCH-CONFIG-STOP +-- ASN1STOP + +``` + +#### DMRS-BundlingPUCCH-Config field descriptions + +##### **pucch-DMRS-Bundling** + +Indicates whether DMRS bundling and time domain window for PUCCH are jointly enabled. + +##### **pucch-FrequencyHoppingInterval** + +Configures the number of consecutive slots for the UE to perform inter-slot frequency hopping with inter-slot bundling for PUCCH. When both inter-frequency hopping and DMRS bundling are enabled for PUCCH repetitions, the UE is expected to be configured with at least one *pucch-FrequencyHoppingInterval-r17* and *pucch-TimeDomainWindowLength-r17*. When DMRS bundling for PUCCH is enabled by *pucch-DMRS-Bundling-r17*, PUCCH frequency hopping interval is only determined by the configuration of PUCCH hopping interval if PUCCH hopping interval is configured. If the field is absent, the number of consecutive slots for the UE to perform inter-slot PUCCH frequency hopping is indicated by *pucch-TimeDomainWindowLength-r17*. + +##### **pucch-TimeDomainWindowLength** + +Configures the length of a nominal time domain window in slots for DMRS bundling for PUCCH. The value shall not exceed the maximum duration for DMRS bundling for PUCCH as specified in TS 38.306 [26]. If this field is absent, the UE shall apply the default value that is the minimum value in the unit of consecutive slots of the time duration for the transmission of all PUCCH repetitions and the maximum duration for DMRS bundling for PUCCH as specified in TS 38.306 [26]. + +##### **pucch-WindowRestart** + +Indicates whether UE bundles PUCCH DMRS remaining in a nominal time domain window after event(s) triggered by DCI or MAC CE that violate power consistency and phase continuity requirements is enabled (see TS 38.214 [19], clause 6.1.7). + +NOTE: Events, which are triggered by DCI or MAC CE, but do not require UE capability to resume maintaining power consistency and/or phase continuity as specified in clause 6.1.7 of TS 38.214 [19], are excluded. + +#### — **DMRS-BundlingPUSCH-Config** + +The IE *DMRS-BundlingPUSCH-Config-r17* is used to configure DMRS bundling for PUSCH. + +#### DMRS-BundlingPUSCH-Config information element + +``` + +-- ASN1START +-- TAG-DMRS-BUNDLINGPUSCH-CONFIG-START + +DMRS-BundlingPUSCH-Config-r17 ::= + SEQUENCE { + pusch-DMRS-Bundling-r17 ENUMERATED {enabled} OPTIONAL, -- Need R + pusch-TimeDomainWindowLength-r17 INTEGER (2..32) OPTIONAL, -- Need S + pusch-WindowRestart-r17 ENUMERATED {enabled} OPTIONAL, -- Need R + pusch-FrequencyHoppingInterval-r17 ENUMERATED {s2, s4, s5, s6, s8, s10, s12, s14, s16, s20} OPTIONAL, -- Need S + ... + } + +-- TAG-DMRS-BUNDLINGPUSCH-CONFIG-STOP +-- ASN1STOP + +``` + +| DMRS-BundlingPUSCH-Config field descriptions | | +|-----------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| pusch-DMRS-Bundling | Indicates whether DMRS bundling and time domain window for PUSCH are jointly enabled. | +| pusch-FrequencyHoppingInterval | Configures the number of consecutive slots for the UE to perform inter-slot frequency hopping with inter-slot bundling for PUSCH. When both inter-frequency hopping and DMRS bundling are enabled for PUSCH repetitions, the UE is expected to be configured with at least one pusch-FrequencyHoppingInterval-r17 and pusch-TimeDomainWindowLength-r17 . This parameter is shared for both DG-PUSCH and CG-PUSCH. When DMRS bundling for PUSCH is enabled by pusch-DMRS-Bundling-r17 , PUSCH frequency hopping interval is only determined by the configuration of PUSCH hopping interval if PUSCH hopping interval is configured. If the field is absent, the number of consecutive slots for the UE to perform inter-slot PUSCH frequency hopping is indicated by pusch-TimeDomainWindowLength-r17 .
Note: For unpaired spectrum, the UE is not expected to be configured the value of s6, s8, s12, s14 and s16. | +| pusch-TimeDomainWindowLength | Configures the length of a nominal time domain window in number of consecutive slots for DMRS bundling for PUSCH. The value shall not exceed the maximum duration for DMRS bundling for PUSCH as specified in TS 38.306 [26]. For PUSCH repetition type A/B, if this field is absent, the UE shall apply the default value that is the minimum value in the unit of consecutive slots of the time duration for the transmission of all PUSCH repetitions and the maximum duration for DMRS bundling for PUSCH as specified in TS 38.306 [26]. For TBoMS, if this field is absent, the UE shall apply the default value that is the minimum value in the unit of consecutive slots of the duration of TBoMS transmission (including repetition of TBoMS) and the maximum duration for DMRS bundling for PUSCH as specified in TS 38.306 [26]. | +| pusch-WindowRestart | Indicates whether UE bundles PUSCH DMRS remaining in a nominal time domain window after event(s) triggered by DCI or MAC CE that violate power consistency and phase continuity requirements is enabled (see TS 38.214 [19], clause 6.1.7).
NOTE: Events, which are triggered by DCI or MAC CE, but do not require UE capability to resume maintaining power consistency and/or phase continuity as specified in clause 6.1.7 of TS 38.214 [19], are excluded. | + +### DMRS-DownlinkConfig + +The IE *DMRS-DownlinkConfig* is used to configure downlink demodulation reference signals for PDSCH. + +#### DMRS-DownlinkConfig information element + +``` +-- ASN1START +-- TAG-DMRS-DOWNLINKCONFIG-START + +DMRS-DownlinkConfig ::= SEQUENCE { + dmrs-Type ENUMERATED {type2} OPTIONAL, -- Need S + dmrs-AdditionalPosition ENUMERATED {pos0, pos1, pos3} OPTIONAL, -- Need S + maxLength ENUMERATED {len2} OPTIONAL, -- Need S + scramblingID0 INTEGER (0..65535) OPTIONAL, -- Need S + scramblingID1 INTEGER (0..65535) OPTIONAL, -- Need S + phaseTrackingRS SetupRelease { PTRS-DownlinkConfig } OPTIONAL, -- Need M + ... + [[ + dmrs-Downlink-r16 ENUMERATED {enabled} OPTIONAL -- Need R + ]], + [[ +``` + +``` + +dmrs-TypeEnh-r18 ENUMERATED {enabled} OPTIONAL -- Need R + ] ] +} + +-- TAG-DMRS-DOWNLINKCONFIG-STOP +-- ASN1STOP + +``` + +#### DMRS-DownlinkConfig field descriptions + +| | | +|--------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| dmrs-AdditionalPosition | Position for additional DMRS in DL, see Tables 7.4.1.1.2-3 and 7.4.1.1.2-4 in TS 38.211 [16]. If the field is absent, the UE applies the value pos2. See also clause 7.4.1.1.2 for additional constraints on how the network may set this field depending on the setting of other fields. | +| dmrs-Downlink | This field indicates whether low PAPR DMRS is used, as specified in TS38.211 [16], clause 7.4.1.1.1. | +| dmrs-Type | Selection of the DMRS type to be used for DL (see TS 38.211 [16], clause 7.4.1.1.1). If the field is absent, the UE uses DMRS type 1. | +| dmrs-TypeEnh | Enables the use of enhanced DMRS type1 or enhanced DMRS type2 with field dmrs-Type (see TS 38.211 [16], clause 7.4.1.1.1). If the field is present and dmrs-Type is absent, the UE uses DMRS eType 1. If the field is present and dmrs-Type is present, the UE uses DMRS eType 2. | +| maxLength | The maximum number of OFDM symbols for DL front loaded DMRS. len1 corresponds to value 1. len2 corresponds to value 2. If the field is absent, the UE applies value len1 . If set to len2 , the UE determines the actual number of DM-RS symbols by the associated DCI. (see TS 38.211 [16], clause 7.4.1.1.2). | +| phaseTrackingRS | Configures downlink PTRS. If the field is not configured, the UE assumes that downlink PTRS are absent. See TS 38.214 [19] clause 5.1.6.3. | +| scramblingID0 | DL DMRS scrambling initialization (see TS 38.211 [16], clause 7.4.1.1.1). When the field is absent the UE applies the value physCellId configured for this serving cell. | +| scramblingID1 | DL DMRS scrambling initialization (see TS 38.211 [16], clause 7.4.1.1.1). When the field is absent the UE applies the value physCellId configured for this serving cell. | + +### DMRS-UplinkConfig + +The IE *DMRS-UplinkConfig* is used to configure uplink demodulation reference signals for PUSCH. + +#### DMRS-UplinkConfig information element + +``` + +-- ASN1START +-- TAG-DMRS-UPLINKCONFIG-START + +DMRS-UplinkConfig ::= SEQUENCE { + dmrs-Type ENUMERATED {type2} OPTIONAL, -- Need S + dmrs-AdditionalPosition ENUMERATED {pos0, pos1, pos3} OPTIONAL, -- Need S + phaseTrackingRS SetupRelease { PTRS-UplinkConfig } OPTIONAL, -- Need M + maxLength ENUMERATED {len2} OPTIONAL, -- Need S + transformPrecodingDisabled + SEQUENCE { + scramblingID0 INTEGER (0..65535) OPTIONAL, -- Need S + } +} + +``` + +``` + + scramblingID1 INTEGER (0..65535) OPTIONAL, -- Need S + ... + [[ + dmrs-Uplink-r16 ENUMERATED {enabled} OPTIONAL -- Need R + ]] + } OPTIONAL, -- Need R + transformPrecodingEnabled SEQUENCE { + nPUSCH-Identity INTEGER(0..1007) OPTIONAL, -- Need S + sequenceGroupHopping ENUMERATED {disabled} OPTIONAL, -- Need S + sequenceHopping ENUMERATED {enabled} OPTIONAL, -- Need S + ... + [[ + dmrs-UplinkTransformPrecoding-r16 SetupRelease {DMRS-UplinkTransformPrecoding-r16} + ]] + } OPTIONAL, -- Need R + ... + [[ + dmrs-TypeEnh-r18 ENUMERATED {enabled} OPTIONAL -- Need R + ]] +} + +DMRS-UplinkTransformPrecoding-r16 ::= SEQUENCE { + pi2BPSK-ScramblingID0 INTEGER(0..65535) OPTIONAL, -- Need S + pi2BPSK-ScramblingID1 INTEGER(0..65535) OPTIONAL -- Need S +} + +-- TAG-DMRS-UPLINKCONFIG-STOP +-- ASN1STOP + +``` + +| DMRS-UplinkConfig field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| dmrs-AdditionalPosition
Position for additional DM-RS in UL (see TS 38.211 [16], clause 6.4.1.1.3). If the field is absent, the UE applies the value pos2. See also clause 6.4.1.1.3 for additional constraints on how the network may set this field depending on the setting of other fields. | +| dmrs-Type
Selection of the DMRS type to be used for UL (see TS 38.211 [16], clause 6.4.1.1.3) If the field is absent, the UE uses DMRS type 1. | +| dmrs-TypeEnh
Enables the use of enhanced DMRS type1 or enhanced DMRS type2 with field dmrs-Type (see TS 38.211 [16], clause 6.4.1.1.3). If the field is present and dmrs-Type is absent, the UE uses DMRS eType 1. If the field is present and dmrs-Type is present, the UE uses DMRS eType 2 | +| dmrs-Uplink
This field indicates whether low PAPR DMRS is used, as specified in TS38.211 [16], clause 6.4.1.1.1.1. | +| dmrs-UplinkTransformPrecoding
This field indicates whether low PAPR DMRS is used for PUSCH with pi/2 BPSK modulation, as specified in TS38.211 [16], clause 6.4.1.1.1.2. The network configures this field only if tp-pi2BPSK is configured in PUSCH-Config . | +| maxLength
The maximum number of OFDM symbols for UL front loaded DMRS. len1 corresponds to value 1. len2 corresponds to value 2. If the field is absent, the UE applies value len1 . If set to len2 , the UE determines the actual number of DM-RS symbols by the associated DCI. (see TS 38.211 [16], clause 6.4.1.1.3). | +| nPUSCH-Identity
Parameter: N_ID^(PUSCH) for DFT-s-OFDM DMRS. If the value is absent or released, the UE uses the value Physical cell ID ( physCellId ). See TS 38.211 [16]. | +| phaseTrackingRS
Configures uplink PTRS (see TS 38.211 [16]). | +| pi2BPSK-ScramblingID0, pi2BPSK-ScramblingID1
UL DMRS scrambling initialization for pi/2 BPSK DMRS for PUSCH (see TS 38.211 [16], Clause 6.4.1.1.2). When the field is absent the UE applies the value Physical cell ID ( physCellId ) of the serving cell. | +| scramblingID0
UL DMRS scrambling initialization for CP-OFDM (see TS 38.211 [16], clause 6.4.1.1.1.1). When the field is absent the UE applies the value Physical cell ID ( physCellId ). | +| scramblingID1
UL DMRS scrambling initialization for CP-OFDM. (see TS 38.211 [16], clause 6.4.1.1.1.1). When the field is absent the UE applies the value Physical cell ID ( physCellId ). | +| sequenceGroupHopping
For DMRS transmission with transform precoder the NW may configure group hopping by the cell-specific parameter groupHoppingEnabledTransformPrecoding in PUSCH-ConfigCommon . In this case, the NW may include this UE specific field to disable group hopping for PUSCH transmission except for Msg3, i.e., to override the configuration in PUSCH-ConfigCommon (see TS 38.211 [16]). If the field is absent, the UE uses the same hopping mode as for Msg3. | +| sequenceHopping
Determines if sequence hopping is enabled for DMRS transmission with transform precoder for PUSCH transmission other than Msg3 (sequence hopping is always disabled for Msg3). If the field is absent, the UE uses the same hopping mode as for msg3. The network does not configure simultaneous group hopping and sequence hopping. See TS 38.211 [16], clause 6.4.1.1.1.2. | +| transformPrecodingDisabled
DMRS related parameters for Cyclic Prefix OFDM. | +| transformPrecodingEnabled
DMRS related parameters for DFT-s-OFDM (Transform Precoding). | + +### DownlinkConfigCommon + +The IE *DownlinkConfigCommon* provides common downlink parameters of a cell. + +#### DownlinkConfigCommon information element + +``` +-- ASN1START +-- TAG-DOWNLINKCONFIGCOMMON-START + +DownlinkConfigCommon ::= SEQUENCE { + frequencyInfoDL FrequencyInfoDL OPTIONAL, -- Cond InterFreqHOAndServCellAdd + initialDownlinkBWP BWP-DownlinkCommon OPTIONAL, -- Cond ServCellAdd + ... + [[ + initialDownlinkBWP-RedCap-r17 BWP-DownlinkCommon OPTIONAL -- Need R + ]] +} + +-- TAG-DOWNLINKCONFIGCOMMON-STOP +-- ASN1STOP +``` + +#### DownlinkConfigCommon field descriptions + +| DownlinkConfigCommon field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| frequencyInfoDL
Basic parameters of a downlink carrier and transmission thereon. | +| initialDownlinkBWP
The initial downlink BWP configuration for a serving cell. The network configures the locationAndBandwidth so that the initial downlink BWP contains the entire CORESET#0 of this serving cell in the frequency domain. | +| initialDownlinkBWP-RedCap
If present, (e)RedCap UEs use this DL BWP instead of initialDownlinkBWP .
If absent, (e)RedCap UEs use initialDownlinkBWP provided that it does not exceed the (e)RedCap UE maximum bandwidth (see also clause 5.2.2.4.2). | + +| Conditional Presence | Explanation | +|----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| InterFreqHOAndServCellAdd | This field is mandatory present for inter-frequency handover, and upon serving cell (PSCell/SCell) addition. Otherwise, the field is optionally present, Need M. | +| ServCellAdd | This field is mandatory present upon serving cell addition (for PSCell and SCell) and upon handover from E-UTRA to NR. It is optionally present, Need M otherwise. | + +#### DownlinkConfigCommonSIB + +The IE *DownlinkConfigCommonSIB* provides common downlink parameters of a cell. + +#### **DownlinkConfigCommonSIB information element** + +``` + +-- ASN1START +-- TAG-DOWNLINKCONFIGCOMMONSIB-START + +DownlinkConfigCommonSIB ::= SEQUENCE { + frequencyInfoDL FrequencyInfoDL-SIB, + initialDownlinkBWP BWP-DownlinkCommon, + bcch-Config BCCH-Config, + pcch-Config PCCH-Config, + ... + [[ + pei-Config-r17 PEI-Config-r17 OPTIONAL, -- Need R + initialDownlinkBWP-RedCap-r17 BWP-DownlinkCommon OPTIONAL -- Need R + ]], + [[ + frequencyInfoDL-v1800 FrequencyInfoDL-SIB-v1800 OPTIONAL -- Need R + ]] +} + +DownlinkConfigCommonSIB-v1760 ::= SEQUENCE { + frequencyInfoDL-v1760 FrequencyInfoDL-SIB-v1760 +} + +BCCH-Config ::= SEQUENCE { + modificationPeriodCoeff ENUMERATED {n2, n4, n8, n16}, + ... +} + +PCCH-Config ::= SEQUENCE { + defaultPagingCycle PagingCycle, + nAndPagingFrameOffset CHOICE { + oneT NULL, + halfT INTEGER (0..1), + quarterT INTEGER (0..3), + oneEighthT INTEGER (0..7), + oneSixteenthT INTEGER (0..15) + }, + ns ENUMERATED {four, two, one}, + firstPDCCH-MonitoringOccasionOfPO CHOICE { + sCS15KHZoneT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..139), + sCS30KHZoneT-sCS15KHZhalft SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..279), + sCS60KHZoneT-sCS30KHZhalft-sCS15KHZquarterT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..559), + sCS120KHZoneT-sCS60KHZhalft-sCS30KHZquarterT-sCS15KHZoneEighthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..1119), + sCS120KHZhalft-sCS60KHZquarterT-sCS30KHZoneEighthT-sCS15KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..2239), + sCS480KHZoneT-sCS120KHZquarterT-sCS60KHZoneEighthT-sCS30KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..4479), + sCS480KHZhalft-sCS120KHZoneEighthT-sCS60KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..8959), + sCS480KHZquarterT-sCS120KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..17919) + } + OPTIONAL, -- Need R + ... +} + +``` + +``` +[[ + nrofPDCH-MonitoringOccasionPerSSB-InPO-r16 INTEGER (2..4) OPTIONAL -- Cond SharedSpectrum2 +]], +[[ + ranPagingInIdlePO-r17 ENUMERATED {true} OPTIONAL, -- Need R + + firstPDCH-MonitoringOccasionOfPO-v1710 CHOICE { + sCS480KHZoneEighthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..35839), + sCS480KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..71679) + } OPTIONAL -- Need R +]] +} + +PEI-Config-r17 ::= SEQUENCE { + po-NumPerPEI-r17 ENUMERATED {po1, po2, po4, po8}, + payloadSizeDCI-2-7-r17 INTEGER (1..maxDCI-2-7-Size-r17), + pei-FrameOffset-r17 INTEGER (0..16), + subgroupConfig-r17 SubgroupConfig-r17, + lastUsedCellOnly-r17 ENUMERATED {true} OPTIONAL, -- Need R + ... +} + +SubgroupConfig-r17 ::= SEQUENCE { + subgroupsNumPerPO-r17 INTEGER (1.. maxNrofPagingSubgroups-r17), + subgroupsNumForUEID-r17 INTEGER (1.. maxNrofPagingSubgroups-r17) + ... +} + +-- TAG-DOWNLINKCONFIGCOMMONSIB-STOP +-- ASN1STOP +``` + +| DownlinkConfigCommonSIB field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| bcch-Config
The modification period related configuration. | +| frequencyInfoDL-SIB
Basic parameters of a downlink carrier and transmission thereon. | +| initialDownlinkBWP
The initial downlink BWP configuration for a PCell. The network configures the locationAndBandwidth so that the initial downlink BWP contains the entire CORESET#0 of this serving cell in the frequency domain. The UE applies the locationAndBandwidth upon reception of this field (e.g. to determine the frequency position of signals described in relation to this locationAndBandwidth ) but it keeps CORESET#0 until after reception of RRCSsetup/RRCSresume/RRCREestablishment . | +| initialDownlinkBWP-RedCap
If present, (e)RedCap UEs use this DL BWP instead of initialDownlinkBWP . If the locationAndBandwidth of this BWP contains the entire CORESET#0, the UE applies the locationAndBandwidth upon reception of this field (e.g. to determine the frequency position of signals described in relation to this locationAndBandwidth ) but it keeps CORESET#0 until after reception of RRCSsetup/RRCSresume/RRCREestablishment . Otherwise, i.e., if the locationAndBandwidth of this BWP does not contain the entire CORESET#0, the UE uses this BWP for receiving DL messages during initial access (Msg2, MsgB, Msg4) and after initial access.
If absent, (e)RedCap UEs use initialDownlinkBWP provided that it does not exceed the (e)RedCap UE maximum bandwidth (see also clause 5.2.2.4.2). | +| lastUsedCellOnly
When present, the field indicates that the UE monitors PEI only if the latest received RRCRelease without noLastCellUpdate is from this cell. A PEI-capable UE stores its last used cell information. | +| nrofPDCCCH-MonitoringOccasionPerSSB-InPO
The number of PDCCCH monitoring occasions corresponding to an SSB within a Paging Occasion, see TS 38.304 [20], clause 7.1. | +| pcch-Config
The paging related configuration. | +| pei-Config
The PEI related configuration. | +| subgroupConfig
The paging subgroup related configuration. | + +| BCCH-Config field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| modificationPeriodCoeff
Actual modification period, expressed in number of radio frames $m = \text{modificationPeriodCoeff} * \text{defaultPagingCycle}$ , see clause 5.2.2.2.2. n2 corresponds to value 2, n4 corresponds to value 4, and so on. | + +| PCCH-Config field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| defaultPagingCycle
Default paging cycle, used to derive 'T' in TS 38.304 [20]. Value rf32 corresponds to 32 radio frames, value rf64 corresponds to 64 radio frames and so on. | +| firstPDCCH-MonitoringOccasionOfPO
Points out the first PDCCH monitoring occasion for paging of each PO of the PF, see TS 38.304 [20]. | +| nAndPagingFrameOffset
Used to derive the number of total paging frames in T (corresponding to parameter N in TS 38.304 [20]) and paging frame offset (corresponding to parameter PF_offset in TS 38.304 [20]). A value of oneSixteenthT corresponds to T / 16, a value of oneEighthT corresponds to T / 8, and so on.
If pagingSearchSpace is set to zero and if SS/PBCH block and CORESET multiplexing pattern is 2 or 3 (as specified in TS 38.213 [13]):
  • - for ssb-periodicityServingCell of 5 or 10 ms, N can be set to one of {oneT, halfT, quarterT, oneEighthT, oneSixteenthT}
  • - for ssb-periodicityServingCell of 20 ms, N can be set to one of {halfT, quarterT, oneEighthT, oneSixteenthT}
  • - for ssb-periodicityServingCell of 40 ms, N can be set to one of {quarterT, oneEighthT, oneSixteenthT}
  • - for ssb-periodicityServingCell of 80 ms, N can be set to one of {oneEighthT, oneSixteenthT}
  • - for ssb-periodicityServingCell of 160 ms, N can be set to oneSixteenthT
If pagingSearchSpace is set to zero and if SS/PBCH block and CORESET multiplexing pattern is 1 (as specified in TS 38.213 [13]), N can be set to one of { halfT , quarterT , oneEighthT , oneSixteenthT }
If pagingSearchSpace is not set to zero, N can be configured to one of { oneT , halfT , quarterT , oneEighthT , oneSixteenthT } | +| ns
Number of paging occasions per paging frame. | +| ranPagingIdlePO
Indicates that the network supports to send RAN paging in PO that corresponds to the i_s as determined by UE in RRC_IDLE state, see TS38.304 [20]. | + +| PEI-Config field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| payloadSizeDCI-2-7
Payload size of PEI DCI, i.e., DCI format 2_7. The size is no larger than the payload size of paging DCI which has maximum of 41 bits and 43 bits for licensed and unlicensed spectrums, respectively. | +| pei-FrameOffset
Offset, in number of frames from the start of a reference frame for PEI-O to the start of a first paging frame of the paging frames associated with the PEI-O, see TS 38.213 [13], clause 10.4A. | +| po-NumPerPEI
The number of PO(s) associated with one PEI monitoring occasion. It is a factor of the total PO number in a paging cycle, i.e N x Ns, as specified in TS 38.304 [20]. The maximum number of PF associated with one PEI monitoring occasion is 2. The number of PO mapping to one PEI should be multiple of Ns when po-NumPerPEI is larger than Ns. | + +| SubgroupConfig field descriptions | | +|------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| subgroupsNumPerPO | Total number of subgroups per Paging Occasion (PO) for UE to read subgroups indication from physical-layer signaling. The field represents the sum of CN-assigned and UEID-based subgroups supported by the network. When PEI-Config is configured, there is always at least one subgroup (UEID-based subgroup or CN-assigned subgroup) configured. | +| subgroupsNumForUEID | Number of subgroups per Paging Occasion (PO) for UE to read subgroups indication from physical-layer signaling, for UEID-based subgrouping method. When present, the field is set to an integer smaller than or equal to subgroupsNumPerPO . subgroupsNumPerPO equals to subgroupsNumForUEID when the network does not configure CN-assigned subgrouping. When pei-Config is configured, the field is absent when the network only configures CN-assigned subgrouping. Both this field and subgroupsNumPerPO are equal to 1 when the network does not configure subgrouping. When pei-Config is configured, if the field is absent, the UE uses subgrouping according to TS 38.304 [20], clause 7.3.0. | + +| Conditional Presence | Explanation | +|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------| +| SharedSpectrum2 | The field is optional present, Need R, if this cell operates with shared spectrum channel access. Otherwise, it is absent, Need R. | + +#### — *DownlinkPreemption* + +The IE *DownlinkPreemption* is used to configure the UE to monitor PDCCH for the INT-RNTI (interruption). + +#### ***DownlinkPreemption* information element** + +``` +-- ASN1START +-- TAG-DOWNLINKPREEMPTION-START + +DownlinkPreemption ::= SEQUENCE { + int-RNTI RNTI-Value, + timeFrequencySet ENUMERATED {set0, set1}, + dci-PayloadSize INTEGER (0..maxINT-DCI-PayloadSize), + int-ConfigurationPerServingCell SEQUENCE (SIZE (1..maxNrofServingCells)) OF INT-ConfigurationPerServingCell, + ... +} + +INT-ConfigurationPerServingCell ::= SEQUENCE { + servingCellId ServCellIndex, + positionInDCI INTEGER (0..maxINT-DCI-PayloadSize-1) +} + +-- TAG-DOWNLINKPREEMPTION-STOP +-- ASN1STOP +``` + +| DownlinkPreemption field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| dci-PayloadSize
Total length of the DCI payload scrambled with INT-RNTI (see TS 38.213 [13], clause 11.2). | +| int-ConfigurationPerServingCell
Indicates (per serving cell) the position of the 14 bit INT values inside the DCI payload (see TS 38.213 [13], clause 11.2). | +| int-RNTI
RNTI used for indication pre-emption in DL (see TS 38.213 [13], clause 10). | +| timeFrequencySet
Set selection for DL-preemption indication (see TS 38.213 [13], clause 11.2) The set determines how the UE interprets the DL preemption DCI payload. | + +| INT-ConfigurationPerServingCell field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| positionInDCI
Starting position (in number of bit) of the 14 bit INT value applicable for this serving cell ( servingCellId ) within the DCI payload (see TS 38.213 [13], clause 11.2). Must be multiples of 14 (bit). | + +#### — ***DRB-Identity*** + +The IE *DRB-Identity* is used to identify a DRB used by a UE. + +#### ***DRB-Identity* information element** + +``` +-- ASN1START +-- TAG-DRB-IDENTITY-START + +DRB-Identity ::= INTEGER (1..32) + +-- TAG-DRB-IDENTITY-STOP +-- ASN1STOP +``` + +#### — ***DRX-Config*** + +The IE *DRX-Config* is used to configure DRX related parameters. + +#### ***DRX-Config* information element** + +``` +-- ASN1START +-- TAG-DRX-CONFIG-START + +DRX-Config ::= SEQUENCE { + drx-onDurationTimer CHOICE { + subMilliSeconds INTEGER (1..31), + milliSeconds ENUMERATED { + ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, +``` + +``` + + ms80, ms100, ms200, ms300, ms400, ms500, ms600, ms800, ms1000, ms1200, + ms1600, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 } + }, + drx-InactivityTimer ENUMERATED { + ms0, ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, ms80, + ms100, ms200, ms300, ms500, ms750, ms1280, ms1920, ms2560, spare9, spare8, + spare7, spare6, spare5, spare4, spare3, spare2, spare1}, + drx-HARQ-RTT-TimerDL INTEGER (0..56), + drx-HARQ-RTT-TimerUL INTEGER (0..56), + drx-RetransmissionTimerDL ENUMERATED { + sl0, sl1, sl2, sl4, sl6, sl8, sl16, sl24, sl33, sl40, sl64, sl80, sl96, sl112, sl128, + sl160, sl320, spare15, spare14, spare13, spare12, spare11, spare10, spare9, + spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1}, + drx-RetransmissionTimerUL ENUMERATED { + sl0, sl1, sl2, sl4, sl6, sl8, sl16, sl24, sl33, sl40, sl64, sl80, sl96, sl112, sl128, + sl160, sl320, spare15, spare14, spare13, spare12, spare11, spare10, spare9, + spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 }, + drx-LongCycleStartOffset CHOICE { + ms10 INTEGER(0..9), + ms20 INTEGER(0..19), + ms32 INTEGER(0..31), + ms40 INTEGER(0..39), + ms60 INTEGER(0..59), + ms64 INTEGER(0..63), + ms70 INTEGER(0..69), + ms80 INTEGER(0..79), + ms128 INTEGER(0..127), + ms160 INTEGER(0..159), + ms256 INTEGER(0..255), + ms320 INTEGER(0..319), + ms512 INTEGER(0..511), + ms640 INTEGER(0..639), + ms1024 INTEGER(0..1023), + ms1280 INTEGER(0..1279), + ms2048 INTEGER(0..2047), + ms2560 INTEGER(0..2559), + ms5120 INTEGER(0..5119), + ms10240 INTEGER(0..10239) + }, + shortDRX SEQUENCE { + drx-ShortCycle ENUMERATED { + ms2, ms3, ms4, ms5, ms6, ms7, ms8, ms10, ms14, ms16, ms20, ms30, ms32, + ms35, ms40, ms64, ms80, ms128, ms160, ms256, ms320, ms512, ms640, spare9, + spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 }, + drx-ShortCycleTimer INTEGER (1..16) + } + drx-SlotOffset INTEGER (0..31) OPTIONAL, -- Need R +} + +DRX-ConfigExt-v1700 ::= + drx-HARQ-RTT-TimerDL-r17 INTEGER (0..448), + +``` + +``` + + drx-HARQ-RTT-TimerUL-r17 INTEGER (0..448) +} + +DRX-ConfigExt2-v1800 ::= SEQUENCE { + drx-NonIntegerLongCycleStartOffset-r18 CHOICE { + ms1001over240 INTEGER (0..3), + ms25over6 INTEGER (0..3), + ms25over3 INTEGER (0..7), + ms1001over120 INTEGER (0..7), + ms100over9 INTEGER (0..10), + ms25over2 INTEGER (0..11), + ms40over3 INTEGER (0..12), + ms125over9 INTEGER (0..12), + ms50over3 INTEGER (0..15), + ms1001over60 INTEGER (0..15), + ms125over6 INTEGER (0..19), + ms200over9 INTEGER (0..21), + ms250over9 INTEGER (0..26), + ms100over3 INTEGER (0..32), + ms1001over30 INTEGER (0..32), + ms125over3 INTEGER (0..40), + ms1001over24 INTEGER (0..40), + ms200over3 INTEGER (0..65), + ms1001over15 INTEGER (0..65), + ms250over3 INTEGER (0..82), + ms1001over12 INTEGER (0..82), + ms400over3 INTEGER (0..132) + }, + shortDRX-r18 SEQUENCE { + drx-NonIntegerShortCycle-r18 ENUMERATED {ms1001over240, ms25over6, ms25over3, ms1001over120, ms100over9, ms25over2, + ms40over3, ms125over9, ms50over3, ms1001over60, ms125over6, ms200over9, + ms100over3, ms1001over30, ms125over3, ms1001over24, ms200over3, spare15, + spare14, spare13, spare12, spare11, spare10, spare9, spare8, spare7, spare6, + spare5, spare4, spare3, spare2, spare1}, + drx-ShortCycleTimer-r18 INTEGER (1..16) + } + drx-TimeReferenceSFN-r18 ENUMERATED {sfn512} OPTIONAL, -- Need R +} OPTIONAL -- Need S + +-- TAG-DRX-CONFIG-STOP +-- ASN1STOP + +``` + +| DRX-Config field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| drx-HARQ-RTT-TimerDL
Value in number of symbols of the BWP where the transport block was received. drx-HARQ-RTT-TimerDL-r17 is only applicable for SCS 480 kHz and 960 kHz. If configured, the UE shall ignore drx-HARQ-RTT-TimerDL (without suffix) for SCS 480 kHz and 960 kHz. | +| drx-HARQ-RTT-TimerUL
Value in number of symbols of the BWP where the transport block was transmitted. drx-HARQ-RTT-TimerUL-r17 is only applicable for SCS 480 kHz and 960 kHz. If configured, the UE shall ignore drx-HARQ-RTT-TimerUL (without suffix) for SCS 480 kHz and 960 kHz. | +| drx-InactivityTimer
Value in multiple integers of 1 ms. ms0 corresponds to 0, ms1 corresponds to 1 ms, ms2 corresponds to 2 ms, and so on. | +| drx-LongCycleStartOffset
drx-LongCycle in ms and drx-StartOffset in multiples of 1 ms. If drx-ShortCycle is configured, the value of drx-LongCycle shall be a multiple of the drx-ShortCycle value. | +| drx-NonIntegerLongCycleStartOffset
drx-NonIntegerLongCycle in non-integer number of ms (e.g. ms25over3 corresponds to 25/3 ms, ms100over9 corresponds to 100/9 ms and so on) and drx-StartOffset in multiples of 1 ms. If drx-NonIntegerShortCycle is configured, the value of drx-NonIntegerLongCycle shall be a multiple of the drx-NonIntegerShortCycle value. If drx-NonIntegerLongCycleStartOffset-r18 is configured, the UE shall ignore drx-LongCycleStartOffset . | +| drx-NonIntegerShortCycle
Value in non-integer number of ms, e.g. ms25over3 corresponds to 25/3 ms, ms100over9 corresponds to 100/9 ms and so on). | +| drx-onDurationTimer
Value in multiples of 1/32 ms (subMilliSeconds) or in ms (milliSecond). For the latter, value ms1 corresponds to 1 ms, value ms2 corresponds to 2 ms, and so on. | +| drx-RetransmissionTimerDL
Value in number of slot lengths of the BWP where the transport block was received. value s0 corresponds to 0 slots, s1 corresponds to 1 slot, s2 corresponds to 2 slots, and so on. | +| drx-RetransmissionTimerUL
Value in number of slot lengths of the BWP where the transport block was transmitted. s0 corresponds to 0 slots, s1 corresponds to 1 slot, s2 corresponds to 2 slots, and so on. | +| drx-ShortCycleTimer
Value in multiples of drx-ShortCycle . A value of 1 corresponds to drx-ShortCycle , a value of 2 corresponds to 2 * drx-ShortCycle and so on. | +| drx-ShortCycle
Value in ms. ms1 corresponds to 1 ms, ms2 corresponds to 2 ms, and so on. | +| drx-SlotOffset
Value in 1/32 ms. Value 0 corresponds to 0 ms, value 1 corresponds to 1/32 ms, value 2 corresponds to 2/32 ms, and so on. | +| drx-TimeReferenceSFN
Indicates SFN used for determination of the offset of DRX cycle. The UE uses the closest SFN with the indicated number preceding the reception of DRX-Config , see TS 38.321 [3], clause 5.7. If the field drx-TimeReferenceSFN is not present, the reference SFN is 0. | + +#### — *DRX-ConfigSecondaryGroup* + +The IE *DRX-ConfigSecondaryGroup* is used to configure DRX related parameters for the second DRX group as specified in TS 38.321 [3]. + +#### ***DRX-ConfigSecondaryGroup* information element** + +``` +-- ASN1START +-- TAG-DRX-CONFIGSECONDARYGROUP-START +``` + +``` + +DRX-ConfigSecondaryGroup-r16 ::= SEQUENCE { + drx-onDurationTimer-r16 CHOICE { + subMilliSeconds INTEGER (1..31), + milliSeconds ENUMERATED { + ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, + ms80, ms100, ms200, ms300, ms400, ms500, ms600, ms800, ms1000, ms1200, + ms1600, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 } + }, + drx-InactivityTimer-r16 ENUMERATED { + ms0, ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, ms80, + ms100, ms200, ms300, ms500, ms750, ms1280, ms1920, ms2560, spare9, spare8, + spare7, spare6, spare5, spare4, spare3, spare2, spare1} + } +} + +-- TAG-DRX-CONFIGSECONDARYGROUP-STOP +-- ASN1STOP + +``` + +#### DRX-ConfigSecondaryGroup field descriptions + +##### *drx-InactivityTimer* + +Value in multiple integers of 1 ms. *ms0* corresponds to 0 ms, *ms1* corresponds to 1 ms, *ms2* corresponds to 2 ms, and so on, as specified in TS 38.321 [3]. The network configures a *drx-InactivityTimer* value for the second DRX group that is smaller than the *drx-InactivityTimer* configured for the default DRX group in IE *DRX-Config*. + +##### *drx-onDurationTimer* + +Value in multiples of 1/32 ms (subMilliSeconds) or in ms (milliSeconds). For the latter, value *ms1* corresponds to 1 ms, value *ms2* corresponds to 2 ms, and so on, as specified in TS 38.321 [3]. The network configures a *drx-onDurationTimer* value for the second DRX group that is smaller than the *drx-onDurationTimer* configured for the default DRX group in IE *DRX-Config*. + +### DRX-ConfigSL + +The IE *DRX-ConfigSL* is used to configure additional DRX parameters for the UE performing sidelink operation with resource allocation mode 1, as specified in TS 38.321 [3]. + +#### DRX-ConfigSL information element + +``` + +-- ASN1START +-- TAG-DRX-CONFIGSL-START + +DRX-ConfigSL-r17 ::= SEQUENCE { + drx-HARQ-RTT-TimerSL-r17 INTEGER (0..56), + drx-RetransmissionTimerSL-r17 ENUMERATED {s10, s11, s12, s14, s16, s18, s116, s124, s133, s140, s164, s180, s196, s1112, s1128, + s1160, s1320, spare15, spare14, spare13, spare12, spare11, spare10, spare9, spare8, + spare7, spare6, spare5, spare4, spare3, spare2, spare1} +} + +-- TAG-DRX-CONFIGSL-STOP +-- ASN1STOP + +``` + +| DRX-ConfigSL field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| drx-HARQ-RTT-TimerSL
For sidelink configured grant Type 1, value in number of symbols of the activated DL BWP of PCell. For other cases, value in number of symbols of the BWP where the PDCCH was transmitted. Value 0 is used in case sl-PUCCH-Config is not configured and the corresponding resource pool is not configured with PSFCH. | +| drx-RetransmissionTimerSL
For sidelink configured grant Type 1, value in number of slot lengths of the activated DL BWP of PCell. For other cases, value in number of slot lengths of the BWP where the PDCCH was transmitted. s10 corresponds to 0 slots, s1 corresponds to 1 slot, s2 corresponds to 2 slots, and so on. | + +#### — *EarlyUL-SyncConfig* + +The IE *EarlyUL-SyncConfig* is used to configure random access resources for the early UL synchronization procedure. + +#### *EarlyUL-SyncConfig* information element + +``` +-- ASN1START +-- TAG-EARLYUL-SYNCCONFIG-START + +EarlyUL-SyncConfig-r18 ::= SEQUENCE { + frequencyInfoUL-r18 FrequencyInfoUL, + rach-ConfigGeneric-r18 RACH-ConfigGeneric, + bwp-GenericParameters-r18 BWP, + ssb-PerRACH-Occasion-r18 ENUMERATED {oneEighth, oneFourth, oneHalf, one, two, four, eight, sixteen} OPTIONAL, -- Need M + prach-RootSequenceIndex-r18 CHOICE { + 1839 INTEGER (0..837), + 1139 INTEGER (0..137) + }, + ltm-prach-SubcarrierSpacing-r18 SubcarrierSpacing, + n-TimingAdvanceOffset-r18 ENUMERATED { n0, n25600, n39936 } OPTIONAL, -- Need R + ... +} + +-- TAG-EARLYUL-SYNCCONFIG-STOP +-- ASN1STOP +``` + +| EarlyUL-SyncConfig field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| frequencyInfoUL
This field provides basic parameters of an uplink carrier for PRACH transmission on a candidate cell. | +| ltm-prach-SubcarrierSpacing
Indicates subcarrier spacing of PRACH for LTM (see TS 38.211 [16], clause 5.3.2).
Only the following values are applicable depending on the used frequency:
FR1: 15 or 30 kHz
FR2-1: 60 or 120 kHz
FR2-2: 120, 480, or 960 kHz | +| n-TimingAdvanceOffset
The N_TA-Offset to be applied for all uplink transmissions on a candidate cell. | +| rach-ConfigGeneric
RACH parameters for performing a random access procedure on a candidate cell. | +| ssb-PerRACH-Occasion
This field indicated the number of SSBs for RACH occasion. | + +#### — *EphemerisInfo* + +The IE *EphemerisInfo* provides satellite ephemeris. Ephemeris may be expressed either in format of position and velocity state vector in ECEF or in format of orbital parameters in ECI. Note: The ECI and ECEF coincide at *epochTime*, i.e., x,y,z axis in ECEF are aligned with x,y,z axis in ECI at *epochTime*. + +#### **EphemerisInfo information element** + +``` +-- ASN1START +-- TAG-EPHEMERISINFO-START + +EphemerisInfo-r17 ::= CHOICE { + positionVelocity-r17 PositionVelocity-r17, + orbital-r17 Orbital-r17 +} + +PositionVelocity-r17 ::= SEQUENCE { + positionX-r17 PositionStateVector-r17, + positionY-r17 PositionStateVector-r17, + positionZ-r17 PositionStateVector-r17, + velocityVX-r17 VelocityStateVector-r17, + velocityVY-r17 VelocityStateVector-r17, + velocityVZ-r17 VelocityStateVector-r17 +} + +Orbital-r17 ::= SEQUENCE { + semiMajorAxis-r17 INTEGER (0..8589934591), + eccentricity-r17 INTEGER (0..1048575), + periapsis-r17 INTEGER (0..268435455), + longitude-r17 INTEGER (0..268435455), + inclination-r17 INTEGER (-67108864..67108863), +``` + +``` + +meanAnomaly-r17 INTEGER (0..268435455) +} + +PositionStateVector-r17 ::= INTEGER (-33554432..33554431) + +VelocityStateVector-r17 ::= INTEGER (-131072..131071) + +-- TAG-EPHEMERISINFO-STOP +-- ASN1STOP + +``` + +| EphemerisInfo field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| eccentricity
Satellite orbital parameter: eccentricity $e$ , see NIMA TR 8350.2 [71]. Unit is radian.
Step of $1.431 \cdot 10^{-8}$ . Actual value = field value $\cdot (1.431 \cdot 10^{-8})$ . | +| inclination
Satellite orbital parameter: inclination $i$ , see NIMA TR 8350.2 [71]. Unit is radian.
Step of $2.341 \cdot 10^{-8}$ rad. Actual value = field value $\cdot (2.341 \cdot 10^{-8})$ . | +| longitude
Satellite orbital parameter: longitude of ascending node $\Omega$ , see NIMA TR 8350.2 [71]. Unit is radian.
Step of $2.341 \cdot 10^{-8}$ rad. Actual value = field value $\cdot (2.341 \cdot 10^{-8})$ . | +| meanAnomaly
Satellite orbital parameter: Mean anomaly $M$ at epoch time, see NIMA TR 8350.2 [71]. Unit is radian.
Step of $2.341 \cdot 10^{-8}$ rad. Actual value = field value $\cdot (2.341 \cdot 10^{-8})$ . | +| periapsis
Satellite orbital parameter: argument of periapsis $\omega$ , see NIMA TR 8350.2 [71]. Unit is radian.
Step of $2.341 \cdot 10^{-8}$ rad. Actual value = field value $\cdot (2.341 \cdot 10^{-8})$ . | +| positionX, positionY, positionZ
X, Y, Z coordinate of satellite position state vector in ECEF. Unit is meter.
Step of 1.3 m. Actual value = field value $\cdot 1.3$ . | +| semiMajorAxis
Satellite orbital parameter: semi major axis $a$ , see NIMA TR 8350.2 [71]. Unit is meter.
Step of $4.249 \cdot 10^{-3}$ m. Actual value = $6500000 + \text{field value} \cdot (4.249 \cdot 10^{-3})$ . | +| velocityVX, velocityVY, velocityVZ
X, Y, Z coordinate of satellite velocity state vector in ECEF. Unit is meter/second.
Step of 0.06 m/s. Actual value = field value $\cdot 0.06$ . | + +#### — EUTRA-C-RNTI + +The IE *EUTRA-C-RNTI* identifies a UE having a RRC connection within an E-UTRA cell. + +#### *EUTRA-C-RNTI* information element + +``` +-- ASN1START +``` + +``` +-- TAG-EUTRACRNTI-START + +EUTRA-C-RNTI ::= BIT STRING (SIZE (16)) + +-- TAG-EUTRACRNTI-STOP +-- ASN1STOP +``` + +#### — *FeatureCombination* + +The IE *FeatureCombination* indicates a feature or a combination of features to be associated with a set of Random Access resources (i.e. an instance of *FeatureCombinationPreambles*). + +#### *FeatureCombination* information element + +``` +-- ASN1START +-- TAG-FEATURECOMBINATION-START + +FeatureCombination-r17 ::= SEQUENCE { + redCap-r17 ENUMERATED {true} OPTIONAL, -- Need R + smallData-r17 ENUMERATED {true} OPTIONAL, -- Need R + nsag-r17 NSAG-List-r17 OPTIONAL, -- Need R + msg3-Repetitions-r17 ENUMERATED {true} OPTIONAL, -- Need R + msg1-Repetitions-r18 ENUMERATED {true} OPTIONAL, -- Need R + eRedCap-r18 ENUMERATED {true} OPTIONAL, -- Need R + spare2 ENUMERATED {true} OPTIONAL, -- Need R + spare1 ENUMERATED {true} OPTIONAL -- Need R +} + +NSAG-List-r17 ::= SEQUENCE (SIZE (1.. maxSliceInfo-r17)) OF NSAG-ID-r17 + +-- TAG-FEATURECOMBINATION-STOP +-- ASN1STOP +``` + +| FeatureCombination field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| eRedCap
If present, this field indicates that eRedCap is part of this feature combination. The fields redCap and eRedCap shall not be both set to true . If the UE is an eRedCap UE and there is no set of configured RA resources with eRedCap set to true among all sets of configured RA resources, the UE considers redCap to be applicable for random access procedure. This field is not configured in a set of preambles that is configured with 2-step random-access type. | +| msg1-Repetitions
If present, this field indicates that signalling of msg1 repetition is part of this feature combination. This field is not configured in a set of preambles that is configured with 2-step random-access type. | +| msg3-Repetitions
If present, this field indicates that signalling of msg3 repetition is part of this feature combination. This field is not configured in a set of preambles that is configured with 2-step random-access type. | +| nsag
If present, this field indicates NSAG(s) that are part of this feature combination. | +| redCap
If present, this field indicates that RedCap is part of this feature combination. | +| smallData
If present, this field indicates that Small Data is part of this feature combination. | + +#### FeatureCombinationPreambles + +The IE *FeatureCombinationPreambles* associates a set of preambles with a feature combination. For parameters which can be provided in this IE, the UE applies this field value when performing Random Access using a preamble in this *featureCombinationPreambles*, otherwise the UE applies the corresponding value as determined by applicable Need Code, e.g. Need S. On a specific BWP, there can be at most one set of preambles associated with a given feature combination per RA Type (i.e. 4-step RACH or 2-step RACH) per MSG1 repetition number. + +#### FeatureCombinationPreambles information element + +``` +-- ASN1START +-- TAG-FEATURECOMBINATIONPREAMBLES-START + +FeatureCombinationPreambles-r17 ::= SEQUENCE { + featureCombination-r17 FeatureCombination-r17, + startPreambleForThisPartition-r17 INTEGER (0..63), + numberOfPreamblesPerSSB-ForThisPartition-r17 INTEGER (1..64), + ssb-SharedRO-MaskIndex-r17 INTEGER (1..15) OPTIONAL, -- Need S + groupBConfigured-r17 SEQUENCE { + ra-SizeGroupA-r17 ENUMERATED {b56, b144, b208, b256, b282, b480, b640, + b800, b1000, b72, spare6, spare5, spare4, spare3, spare2, spare1}, + messagePowerOffsetGroupB-r17 ENUMERATED { minusinfinity, dB0, dB5, dB8, dB10, dB12, dB15, dB18}, + numberOfRA-PreamblesGroupA-r17 INTEGER (1..64) + } + separateMsgA-PUSCH-Config-r17 MsgA-PUSCH-Config-r16 OPTIONAL, -- Cond MsgAConfigCommon + msgA-RSRP-Threshold-r17 RSRP-Range OPTIONAL, -- Need R + rsrp-ThresholdSSB-r17 RSRP-Range OPTIONAL, -- Need R + deltaPreamble-r17 INTEGER (-1..6) OPTIONAL, -- Need R +} +``` + +``` +... +[[ + msg1-RepetitionNum-r18 ENUMERATED {n2, n4, n8} OPTIONAL, -- Cond Msg1Rep2 + msg1-RepetitionTimeOffsetROGroup-r18 ENUMERATED {n4, n8, n16, n32} OPTIONAL -- Cond Msg1Rep3 +]] +} + +-- TAG-FEATURECOMBINATIONPREAMBLES-STOP +-- ASN1STOP +``` + +| FeatureCombinationPreambles field descriptions | | +|-------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| deltaPreamble | Power offset between msg3 or msgA-PUSCH and RACH preamble transmission. If configured, this parameter overrides msg3-DeltaPreamble or msgA-DeltaPreamble , Actual value = field value * 2 [dB] (see TS 38.213 [13], clause 7.1). If msgA-DeltaPreamble is configured in separateMsgA-PUSCH-Config-r17 , this field is absent. This field is set to the same value for all FeatureCombinationPreambles for MSG1 repetitions. | +| featureCombination | Indicates which combination of features that the preambles indicated by this IE are associated with. The UE ignores a RACH resource defined by this FeatureCombinationPreambles if any feature within the featureCombination is not supported by the UE or if any of the spare fields within the featureCombination is set to true . | +| messagePowerOffsetGroupB | Threshold for preamble selection. Value is in dB. Value minusinfinity corresponds to $-\infty$ . Value dB0 corresponds to 0 dB, dB5 corresponds to 5 dB and so on (see TS 38.321 [3], clause 5.1.2). | +| msg1-RepetitionNum | Indicates which MSG1-repetition number that this FeatureCombinationPreambles is associated with. | +| msg1-RepetitionTimeOffsetROGroup | Indicates a time offset of the starting ROs between two successive RO groups for a given repetition number (2, 4 or 8) associated with this FeatureCombinationPreambles for each frequency resource index within a time period (see TS 38.213 [13]). If this field is absent, the time offset is implicitly determined (see TS 38.213 [13]).

For each MSG1 repetition number, the following values are applicable.
  • • {n16}, for RO groups for MSG1 repetition number 8
  • • {n8, n16}, for RO groups for MSG1 repetition number 4
  • • {n4, n8, n16}, for RO groups for MSG1 repetition number 2
| +| msgA-RSRP-Threshold | The UE selects 2-step random access type to perform random access based on this threshold (see TS 38.321 [3], clause 5.1.1). This field is only present if both 2-step and 4-step RA type are configured for the concerned feature combination in the BWP. If configured, this parameter overrides msgA-RSRP-Threshold-r16 . If absent, the UE applies msgA-RSRP-Threshold-r16 , if configured | +| numberOfPreamblesPerSSB-ForThisPartition | It determines how many consecutive preambles are associated to the Feature Combination starting from the starting preamble(s) per SSB. | +| numberOfRA-PreamblesGroupA | It determines how many consecutive preambles per SSB are associated to Group A starting from the starting preamble(s). The remaining preambles associated to the Feature Combination are associated to Group B | +| ra-SizeGroupA | Transport Blocks size threshold in bits below which the UE shall use a contention-based RA preamble of group A. (see TS 38.321 [3], clause 5.1.2). If this feature combination preambles are associated to a RACH-ConfigCommon-twostepRA , this field correspond to ra-MsgA-SizeGroupA , otherwise it corresponds to ra-Msg3SizeGroupA . | +| rsrp-ThresholdSSB | UE may select the SS block and corresponding PRACH resource for path-loss estimation and (re)transmission based on SS blocks that satisfy the threshold (see TS 38.213 [13]). If this parameter is included in FeatureCombinationPreambles which is included in RACH-ConfigCommonTwoStepRA , it corresponds to msgA-RSRP-ThresholdSSB , as defined in TS 38.321 [3]. If this parameter is included in FeatureCombinationPreambles which is included in RACH-ConfigCommon , it corresponds to rsrp-ThresholdSSB , as defined in TS 38.321 [3]. | +| separateMsgA-PUSCH-Config | If present it specifies how the 2-step RACH preambles identified by this FeatureCombinationPreambles are mapped to a PUSCH slot separate from the one defined in MsgA-ConfigCommon-r16 . If the field is absent, the UE should apply the corresponding parameter in the RACH-ConfigCommonTwoStepRA of the BWP which includes the FeatureCombinationPreambles IE. | +| ssb-SharedRO-MaskIndex | Mask index (see TS 38.321 [3]). | + +Indicates a subset of ROs where preambles are allocated for this feature combination. + +If this field is configured within *FeatureCombinationPreambles* which is included in *RACH-ConfigCommonTwoStepRA*: + +- in case of separate ROs are configured for 4-step and 2-step random access, this field indicates a subset of ROs configured within this *RACH-ConfigCommonTwoStepRA*; +- in case shared ROs are used for 4-step and 2-step random access, it indicates the subset of ROs configured within *RACH-ConfigCommon*, which are the subset of ROs configured for 2-step random access. + +This field is configured when there is more than one RO per SSB. If the field is absent, all ROs configured in *RACH-ConfigCommon* or *RACH-ConfigCommonTwoStepRA* containing this *FeatureCombinationPreambles* are shared. + +#### **startPreambleForThisPartition** + +It defines the first preamble associated with the Feature Combination. If the UE is provided with a number N of SSB block indexes associated with one PRACH occasion, and $N < 1$ , the first preamble in each PRACH occasion is the one having the same index as indicated by this field. If $N \geq 1$ , N blocks of preambles associated with the Feature + +Combination are defined, each having start index $n \cdot N_{\text{preamble}}^{\text{total}} / N + \text{startPreambleForThisPartition}$ , where n refers to SSB block index (see TS 38.213 [13], clause 8.1). + +| Conditional Presence | Explanation | +|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MsgAConfigCommon | The field is optionally present, Need S, if FeatureCombinationPreambles is included in RACH-ConfigCommonTwoStepRA . Otherwise, it is absent. If the field is absent in FeatureCombinationPreambles included in RACH-ConfigCommonTwoStepRA , the UE applies MsgA-PUSCH-Config included in the corresponding MsgA-ConfigCommon . | +| Msg1Rep2 | The field is mandatory present, Need R, if msg1-Repetitions is included in FeatureCombinationPreambles for this concerned. Otherwise, it is absent. | +| Msg1Rep3 | The field is optionally present, Need S, if msg1-Repetitions is included in FeatureCombinationPreambles for this concerned. Otherwise, it is absent. | + +#### – FilterCoefficient + +The IE *FilterCoefficient* specifies the measurement filtering coefficient. Value *fc0* corresponds to $k = 0$ , *fc1* corresponds to $k = 1$ , and so on. + +#### FilterCoefficient information element + +``` +-- ASN1START +-- TAG-FILTERCOEFFICIENT-START + +FilterCoefficient ::= ENUMERATED { fc0, fc1, fc2, fc3, fc4, fc5, fc6, fc7, fc8, fc9, fc11, fc13, fc15, fc17, fc19, spare1, ... } + +-- TAG-FILTERCOEFFICIENT-STOP +-- ASN1STOP +``` + +#### – FreqBandIndicatorNR + +The IE *FreqBandIndicatorNR* is used to convey an NR frequency band number as defined in TS 38.101-1 [15], TS 38.101-2 [39] and TS 38.101-5 [75]. + +#### **FreqBandIndicatorNR information element** + +``` + +-- ASN1START +-- TAG-FREQBANDINDICATORNR-START + +FreqBandIndicatorNR := INTEGER (1..1024) + +-- TAG-FREQBANDINDICATORNR-STOP +-- ASN1STOP + +``` + +#### – FreqPriorityListDedicatedSlicing + +The IE *FreqPriorityListDedicatedSlicing* provides dedicated cell reselection priorities for slicing in *RRCRelease*. + +#### **FreqPriorityListDedicatedSlicing information element** + +``` + +-- ASN1START +-- TAG-FREQPRIORITYLISTDEDICATEDSLICING-START + +FreqPriorityListDedicatedSlicing-r17 := SEQUENCE (SIZE (1.. maxFreq)) OF FreqPriorityDedicatedSlicing-r17 + +FreqPriorityDedicatedSlicing-r17 := SEQUENCE { + dl-ExplicitCarrierFreq-r17 ARFCN-ValueNR, + sliceInfoListDedicated-r17 SliceInfoListDedicated-r17 +} OPTIONAL -- Cond Mandatory + +SliceInfoListDedicated-r17 := SEQUENCE (SIZE (1..maxSliceInfo-r17)) OF SliceInfoDedicated-r17 + +SliceInfoDedicated-r17 := SEQUENCE { + nsag-IdentityInfo-r17 NSAG-IdentityInfo-r17, + nsag-CellReselectionPriority-r17 CellReselectionPriority + nsag-CellReselectionSubPriority-r17 CellReselectionSubPriority +} OPTIONAL, -- Need R + OPTIONAL -- Need R + +-- TAG-FREQPRIORITYLISTDEDICATEDSLICING-STOP +-- ASN1STOP + +``` + +#### **FreqPriorityDedicatedSlicing field descriptions** + +| | +|---------------------------------------------------------------------------------------------------------------------------------| +| dl-ExplicitCarrierFreq
Indicates the downlink carrier frequency to which SliceInfoListDedicated is associated. | +|---------------------------------------------------------------------------------------------------------------------------------| + +| Conditional Presence | Explanation | +|----------------------|---------------------------------| +| Mandatory | The field is mandatory present. | + +#### – *FreqPriorityListSlicing* + +The IE *FreqPriorityListSlicing* indicates cell reselection priorities for slicing in SIB16. + +#### *FreqPriorityListSlicing* information element + +``` +-- ASN1START +-- TAG-FREQPRIORITYLISTSLICING-START + +FreqPriorityListSlicing-r17 ::= SEQUENCE (SIZE (1..maxFreqPlus1)) OF FreqPrioritySlicing-r17 + +FreqPrioritySlicing-r17 ::= SEQUENCE { + dl-ImplicitCarrierFreq-r17 INTEGER (0..maxFreq), + sliceInfoList-r17 SliceInfoList-r17 OPTIONAL -- Cond Mandatory +} + +SliceInfoList-r17 ::= SEQUENCE (SIZE (1..maxSliceInfo-r17)) OF SliceInfo-r17 + +SliceInfo-r17 ::= SEQUENCE { + nsag-IdentityInfo-r17 NSAG-IdentityInfo-r17, + nsag-CellReselectionPriority-r17 CellReselectionPriority OPTIONAL, -- Need R + nsag-CellReselectionSubPriority-r17 CellReselectionSubPriority OPTIONAL, -- Need R + sliceCellListNR-r17 CHOICE { + sliceAllowedCellListNR-r17 SliceCellListNR-r17, + sliceExcludedCellListNR-r17 SliceCellListNR-r17 + } +} +OPTIONAL -- Need R + +SliceCellListNR-r17 ::= SEQUENCE (SIZE (1..maxCellSlice-r17)) OF PCI-Range + +-- TAG-FREQPRIORITYLISTSLICING-STOP +-- ASN1STOP +``` + +#### *FreqPriorityListSlicing* field descriptions + +##### ***dl-ImplicitCarrierFreq*** + +Indicates the downlink carrier frequency to which *sliceInfoList* is associated with. The frequency is signalled implicitly, value 0 corresponds to the serving frequency, value 1 corresponds to the first frequency indicated by the *InterFreqCarrierFreqList* in SIB4, and value 2 corresponds to the second frequency indicated by the *InterFreqCarrierFreqList* in SIB4, and so on. + +| SliceInfo field descriptions | | +|--------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sliceAllowedCellListNR | List of allow-listed cells for slicing. If present, the cells listed in this list support the corresponding nsag-frequency pair, and the cells not listed in this list do not support the corresponding nsag-frequency pair, according to TS 38.304 [20], clause 5.2.4.11. | +| sliceCellListNR | Contains either the list of allow-listed or exclude-listed cells for slicing. If absent, it implies all the cells support the corresponding nsag-frequency pair, according to 38.304 [20], clause 5.2.4.11. | +| sliceExcludedCellListNR | List of exclude-listed cells for slicing. If present, the cells listed in this list do not support the corresponding nsag-frequency pair, and the cells not listed in this list support the corresponding nsag-frequency pair, according to TS 38.304 [20], clause 5.2.4.11. | + +| Conditional Presence | Explanation | +|-----------------------------|---------------------------------| +| Mandatory | The field is mandatory present. | + +#### – *FrequencyInfoDL* + +The IE *FrequencyInfoDL* provides basic parameters of a downlink carrier and transmission thereon. + +#### ***FrequencyInfoDL* information element** + +``` +-- ASN1START +-- TAG-FREQUENCYINFODL-START + +FrequencyInfoDL ::= SEQUENCE { + absoluteFrequencySSB ARFCN-ValueNR OPTIONAL, -- Cond SpCellAdd + frequencyBandList MultiFrequencyBandListNR, + absoluteFrequencyPointA ARFCN-ValueNR, + scs-SpecificCarrierList SEQUENCE (SIZE (1..maxSCSs)) OF SCS-SpecificCarrier, + ... + [[ + referenceCell-r18 ServCellIndex OPTIONAL -- Cond SSBlessSCell + ]] +} + +-- TAG-FREQUENCYINFODL-STOP +-- ASN1STOP +``` + +| FrequencyInfoDL field descriptions | | +|-------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| absoluteFrequencyPointA | Absolute frequency position of the reference resource block (Common RB 0). Its lowest subcarrier is also known as Point A (see TS 38.211 [16], clause 4.4.4.2). Note that the lower edge of the actual carrier is not defined by this field but rather in the scs-SpecificCarrierList . | +| absoluteFrequencySSB | Frequency of the SSB to be used for this serving cell. SSB related parameters (e.g. SSB index) provided for a serving cell refer to this SSB frequency unless mentioned otherwise. The CD-SSB of the PCell is always on the sync raster. Frequencies are considered to be on the sync raster if they are also identifiable with a GSCN value (see TS 38.101-1 [15] or TS 38.101-5 [75]). If the field is absent, the SSB related parameters should be absent, e.g. ssb-PositionsInBurst , ssb-periodicityServingCell and subcarrierSpacing in ServingCellConfigCommon IE. If the field is absent, the UE obtains timing reference from the SpCell or an SCell if applicable as described in TS 38.213 [13], clause 4.1, or from the SpCell or an SCell indicated by referenceCell , or from the "default cell" defined in TS [xx]. This is supported in case the SCell for which the UE obtains the timing reference is in the same or different frequency band as the cell (i.e. the SpCell or the SCell, respectively) from which the UE obtains the timing reference. For cells supporting (e)RedCap, this field corresponds to the CD-SSB. | +| frequencyBandList | List containing only one frequency band to which this carrier(s) belongs. Multiple values are not supported. | +| referenceCell | Indicates the reference cell, i.e. the cell which provides the timing reference and AGC source for the SSB-less SCell. If the reference cell is an SCell or PSCell, it should be an activated SCell or activated PSCell.
If this field is absent a "default cell" is the reference cell as defined in TS [xx] | +| scs-SpecificCarrierList | A set of carriers for different subcarrier spacings (numerologies). Defined in relation to Point A. The network configures a scs-SpecificCarrier at least for each numerology (SCS) that is used e.g. in a BWP (see TS 38.211 [16], clause 5.3). | + +| Conditional Presence | Explanation | +|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SpCellAdd | The field is mandatory present if this FrequencyInfoDL is for SpCell. Otherwise the field is optionally present, Need S. | +| SSBlessSCell | The field is optionally present, Need S, if the SSB-less SCell is configured for this cell and absoluteFrequencySSB is absent. It is absent otherwise. | + +#### – *FrequencyInfoDL-SIB* + +The IE *FrequencyInfoDL-SIB* provides basic parameters of a downlink carrier and transmission thereon. + +#### *FrequencyInfoDL-SIB* information element + +``` +-- ASN1START +-- TAG-FREQUENCYINFODL-SIB-START + +FrequencyInfoDL-SIB ::= SEQUENCE { + frequencyBandList MultiFrequencyBandListNR-SIB, + offsetToPointA INTEGER (0..2199), + scs-SpecificCarrierList SEQUENCE (SIZE (1..maxSCSs)) OF SCS-SpecificCarrier +} + +FrequencyInfoDL-SIB-v1760 ::= SEQUENCE { +``` + +``` + + frequencyBandList-v1760 MultiFrequencyBandListNR-SIB-v1760 + } + + FrequencyInfoDL-SIB-v1800 ::= SEQUENCE { + frequencyBandListAerial-r18 MultiFrequencyBandListNR-Aerial-SIB-r18 + } + + -- TAG-FREQUENCYINFODL-SIB-STOP + -- ASN1STOP + +``` + +| FrequencyInfoDL-SIB field descriptions | | +|------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| offsetToPointA | Represents the offset to Point A as defined in TS 38.211 [16], clause 4.4.4.2. | +| frequencyBandList | List of one or multiple frequency bands to which this carrier(s) belongs. If frequencyBandList-v1760 is present, it shall contain the same number of entries, listed in the same order as in frequencyBandList (without suffix). | +| scs-SpecificCarrierList | A set of carriers for different subcarrier spacings (numerologies). Defined in relation to Point A (see TS 38.211 [16], clause 5.3). The network configures this for all SCSs that are used in DL BWPs in this serving cell. | + +#### — *FrequencyInfoUL* + +The IE *FrequencyInfoUL* provides basic parameters of an uplink carrier and transmission thereon. + +#### ***FrequencyInfoUL* information element** + +``` + +-- ASN1START +-- TAG-FREQUENCYINFOUL-START + +FrequencyInfoUL ::= SEQUENCE { + frequencyBandList MultiFrequencyBandListNR OPTIONAL, -- Cond FDD-OrSUL + absoluteFrequencyPointA ARFCN-ValueNR OPTIONAL, -- Cond FDD-OrSUL + scs-SpecificCarrierList SEQUENCE (SIZE (1..maxSCSs)) OF SCS-SpecificCarrier, + additionalSpectrumEmission AdditionalSpectrumEmission OPTIONAL, -- Need S + p-Max P-Max OPTIONAL, -- Need S + frequencyShift7p5khz ENUMERATED {true} OPTIONAL, -- Cond FDD-TDD-OrSUL-Optional + ..., + [[ + additionalSpectrumEmission-v1760 AdditionalSpectrumEmission-v1760 OPTIONAL -- Need S + ]], + [[ + additionalSpectrumEmissionAerial-r18 AdditionalSpectrumEmission-r18 OPTIONAL -- Need S + ]] +} + +-- TAG-FREQUENCYINFOUL-STOP + +``` + +-- ASN1STOP + +| FrequencyInfoUL field descriptions | | +|-------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| absoluteFrequencyPointA | Absolute frequency of the reference resource block (Common RB 0). Its lowest subcarrier is also known as Point A. Note that the lower edge of the actual carrier is not defined by this field but rather in the scs-SpecificCarrierList (see TS 38.211 [16], clause 4.4.4.2). | +| additionalSpectrumEmission | The additional spectrum emission requirements to be applied by the UE on this uplink. If both additionalSpectrumEmission (without suffix) and additionalSpectrumEmission-v1760 are absent, the UE uses value 0 for the additionalSpectrumEmission (see TS 38.101-1 [15], tables 6.2.3.1-1A, 6.2A.3.1.1-2 and 6.2A.3.1.2-2, TS 38.101-2 [39], tables 6.2.3.1-2 and 6.2A.3.1-2, and TS 38.101-5 [75], table 6.2.3.1-1A). Network configures the same value in additionalSpectrumEmission for all uplink carrier(s) of the same band with UL configured and if signalled, the same value in additionalSpectrumEmission-v1760 for all uplink carrier(s) of the same band with UL configured, except for additionalSpectrumEmission value corresponding to NS_55/NS_57. If NS_55/NS_57 (see TS 38.101-1 [15], table 6.2.3.1-1) is applicable for at least one uplink carrier, the network may configure either NS_55/NS_57 or NS_01 for these uplink carriers, and NS_01 for the remaining uplink carrier(s) of band n77. The additionalSpectrumEmission is applicable for all uplink carriers of the same band with UL configured. | +| additionalSpectrumEmissionAerial | The additional spectrum emission requirements to be applied by the aerial UE on this uplink (see TS 38.101-1 [15], tables TBD, TS 38.101-2 [39], tables TBD, and TS 38.101-5 [75], table TBD). If the field is absent, the aerial UE uses value indicated by the field additionalSpectrumEmission/ additionalSpectrumEmission-v1760 . | +| frequencyBandList | List containing only one frequency band to which this carrier(s) belongs. Multiple values are not supported. | +| frequencyShift7p5khz | Enable the NR UL transmission with a 7.5 kHz shift to the LTE raster. If the field is absent, the frequency shift is disabled. | +| p-Max | Maximum transmit power allowed in this serving cell. The maximum transmit power that the UE may use on this serving cell may be additionally limited by p-NR-FR1 (configured for the cell group) and by p-UE-FR1 (configured total for all serving cells operating on FR1). If absent, the UE applies the maximum power according to TS 38.101-1 [15] in case of an FR1 cell, TS 38.101-2 [39] in case of an FR2 cell or TS 38.101-5 [75] in case of an NTN cell. In this release of the specification, if p-Max is present on a carrier frequency in FR2, the UE shall ignore the field and applies the maximum power according to TS 38.101-2 [39]. Value in dBm. This field is ignored by IAB-MT, the IAB-MT applies output power and emissions requirements, as specified in TS 38.174 [63]. | +| scs-SpecificCarrierList | A set of carriers for different subcarrier spacings (numerologies). Defined in relation to Point A. The network configures a scs-SpecificCarrier at least for each numerology (SCS) that is used e.g. in a BWP (see TS 38.211 [16], clause 5.3). | + +| Conditional Presence | Explanation | +|-------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| FDD-OrSUL | The field is mandatory present if this FrequencyInfoUL is for the paired UL for a DL (defined in a FrequencyInfoDL ) or if this FrequencyInfoUL is for a supplementary uplink (SUL). It is absent, Need R, otherwise (if this FrequencyInfoUL is for an unpaired UL (TDD)). | +| FDD-TDD-OrSUL-Optional | The field is optionally present, Need R, if this FrequencyInfoUL is for the paired UL for a DL (defined in a FrequencyInfoDL ), or if this FrequencyInfoUL is for an unpaired UL (TDD) in certain bands (as defined in clause 5.4.2.1 of TS 38.101-1 and in clause 5.4.2.1 of TS 38.104 [12]), or if this FrequencyInfoUL is for a supplementary uplink (SUL). It is absent, Need R, otherwise. | + +#### FrequencyInfoUL-SIB + +The IE *FrequencyInfoUL-SIB* provides basic parameters of an uplink carrier and transmission thereon. + +#### FrequencyInfoUL-SIB information element + +``` +-- ASN1START +-- TAG-FREQUENCYINFOUL-SIB-START + +FrequencyInfoUL-SIB ::= + SEQUENCE { + frequencyBandList MultiFrequencyBandListNR-SIB OPTIONAL, -- Cond FDD-OrSUL + absoluteFrequencyPointA ARFCN-ValueNR OPTIONAL, -- Cond FDD-OrSUL + scs-SpecificCarrierList SEQUENCE (SIZE (1..maxSCSs)) OF SCS-SpecificCarrier, + p-Max P-Max OPTIONAL, -- Need S + frequencyShift7p5khz ENUMERATED {true} OPTIONAL, -- Cond FDD-TDD-OrSUL-Optional + ... + [[ + frequencyBandListAerial-r18 MultiFrequencyBandListNR-Aerial-SIB-r18 OPTIONAL -- Need S + ]] + } + +FrequencyInfoUL-SIB-v1760 ::= + SEQUENCE { + frequencyBandList-v1760 MultiFrequencyBandListNR-SIB-v1760 + } + +-- TAG-FREQUENCYINFOUL-SIB-STOP +-- ASN1STOP +``` + +| FrequencyInfoUL-SIB field descriptions | | +|-----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| absoluteFrequencyPointA | Absolute frequency of the reference resource block (Common RB 0). Its lowest subcarrier is also known as Point A. Note that the lower edge of the actual carrier is not defined by this field but rather in the scs-SpecificCarrierList (see TS 38.211 [16], clause 4.4.4.2). | +| frequencyBandList | Provides the frequency band indicator and a list of additionalPmax and additionalSpectrumEmission values as defined in TS 38.101-1 [15], table 6.2.3.1-1, TS 38.101-2 [39], table 6.2.3.1-2, and TS 38.101-5 [75], table 6.2.3.1-1. The UE shall apply the first listed band which it supports in the frequencyBandList field. If frequencyBandList-v1760 is present, it shall contain the same number of entries, listed in the same order as in frequencyBandList (without suffix). | +| frequencyBandListAerial | Provides the frequency band indicator and a list of additionalPmax and additionalSpectrumEmission values for aerial UE as defined in TS 38.101-1 [15], table TBD, TS 38.101-2 [39], table TBD, and TS 38.101-5 [75], table TBD. If the field is present, the aerial UE shall apply the first listed band which it supports in the frequencyBandListAerial field. If the field is absent, frequencyBandList applies. | +| frequencyShift7p5khz | Enable the NR UL transmission with a 7.5 kHz shift to the LTE raster. If the field is absent, the frequency shift is disabled. | +| p-Max | Value in dBm applicable for the cell. If absent the UE applies the maximum power according to TS 38.101-1 [15] in case of an FR1 cell, TS 38.101-2 [39] in case of an FR2 cell or TS 38.101-5 [75] in case of an NTN cell. In this release of the specification, if p-Max is present on a carrier frequency in FR2, the UE shall ignore the field and applies the maximum power according to TS 38.101-2 [39]. This field is ignored by IAB-MT, the IAB-MT applies output power and emissions requirements, as specified in TS 38.174 [63]. | +| scs-SpecificCarrierList | A set of carriers for different subcarrier spacings (numerologies). Defined in relation to Point A (see TS 38.211 [16], clause 5.3). The network configures this for all SCSs that are used in UL BWPs configured in this serving cell. | + +| Conditional Presence | Explanation | +|-------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| FDD-OrSUL | The field is mandatory present if this FrequencyInfoUL-SIB is for the paired UL for a DL (defined in a FrequencyInfoDL-SIB ) or if this FrequencyInfoUL-SIB is for a supplementary uplink (SUL). It is absent otherwise (if this FrequencyInfoUL-SIB is for an unpaired UL (TDD)). | +| FDD-TDD-OrSUL-Optional | The field is optionally present, Need R, if this FrequencyInfoUL-SIB is for the paired UL for a DL (defined in a FrequencyInfoDL-SIB ), or if this FrequencyInfoUL-SIB is for an unpaired UL (TDD) in certain bands (as defined in clause 5.4.2.1 of TS 38.101-1 and in clause 5.4.2.1 of TS 38.104 [12]), or if this FrequencyInfoUL-SIB is for a supplementary uplink (SUL). It is absent otherwise. | + +## GapPriority + +The IE *GapPriority* is used to identify the priority of a gap configuration. + +#### GapPriority information element + +``` +-- ASN1START +-- TAG-GAPPRIORITY-START + +GapPriority-r17 ::= + INTEGER (1..maxNrOfGapPri-r17) +``` + +``` +-- TAG-GAPPRIORITY-STOP +-- ASN1STOP +``` + +# — *HighSpeedConfig* + +The IE *HighSpeedConfig* is used to configure parameters for high speed scenarios. + +### *HighSpeedConfig* information element + +``` +-- ASN1START +-- TAG-HIGHSPEEDCONFIG-START + +HighSpeedConfig-r16 ::= SEQUENCE { + highSpeedMeasFlag-r16 ENUMERATED {true} OPTIONAL, -- Cond SpCellOnly + highSpeedDemodFlag-r16 ENUMERATED {true} OPTIONAL, -- Need R + ... +} + +HighSpeedConfig-v1700 ::= SEQUENCE { + highSpeedMeasCA-Scell-r17 ENUMERATED {true} OPTIONAL, -- Cond SCellOnly + highSpeedMeasInterFreq-r17 ENUMERATED {true} OPTIONAL, -- Cond SpCellOnly2 + highSpeedDemodCA-Scell-r17 ENUMERATED {true} OPTIONAL, -- Need R + ... +} + +HighSpeedConfigFR2-r17 ::= SEQUENCE { + highSpeedMeasFlagFR2-r17 ENUMERATED {set1, set2} OPTIONAL, -- Need R + highSpeedDeploymentTypeFR2-r17 ENUMERATED {unidirectional, bidirectional} OPTIONAL, -- Need R + highSpeedLargeOneStepUL-TimingFR2-r17 ENUMERATED {true} OPTIONAL, -- Need R + ... +} + +-- TAG-HIGHSPEEDCONFIG-STOP +-- ASN1STOP +``` + +| HighSpeedConfig field descriptions | | +|-------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| HighSpeedDemodCA-SCell | If the field is present and UE supports demodulationEnhancementCA-r17 , the UE shall apply the enhanced demodulation processing for HST-SFN joint transmission scheme with velocity up to 500km/h as specified in TS 38.101-4 [59]. This parameter only applies to SCell. | +| highSpeedDemodFlag | If the field is present and UE supports demodulationEnhancement-r16 , the UE shall apply the enhanced demodulation processing for HST-SFN joint transmission scheme with velocity up to 500km/h as specified in TS 38.101-4 [59]. This parameter only applies to SpCell. | +| highSpeedDeploymentTypeFR2 | If the field is present, and field value is unidirectional , the UE shall assume uni-directional deployment or if field value is bidirectional the UE shall assume bidirectional deployment for FR2 up to 350km/h as specified in TS 38.133 [14]. | +| highSpeedLargeOneStepUL-TimingFR2 | If the field is present, large one step UE autonomous uplink transmit timing adjustment for FR2 up to 350km/h as specified in TS 38.133 [14] is enabled. | +| highSpeedMeasCA-SCell | If the field is present and UE supports measurementEnhancementCA-r17 , the UE shall apply the enhanced RRM requirements to the serving frequency of SCell for carrier aggregation to support high speed up to 500 km/h as specified in TS 38.133 [14]. | +| highSpeedMeasFlag |

If the field is present and UE supports measurementEnhancement-r16, the UE shall apply the enhanced intra-NR and inter-RAT EUTRAN RRM requirements to support high speed up to 500 km/h as specified in TS 38.133 [14].

If the field is present and UE supports intraNR-MeasurementEnhancement-r16, the UE shall apply enhanced intra-NR RRM requirement to support high speed up to 500 km/h as specified in TS 38.133 [14].

If the field is present and UE supports interRAT-MeasurementEnhancement-r16, the UE shall apply enhanced inter-RAT EUTRAN RRM requirement to support high speed up to 500 km/h as specified in TS 38.133 [14].

This parameter only applies to the serving frequency of SpCell.

| +| highSpeedMeasFlagFR2 | If the field is present, the UE shall apply enhanced intra-NR RRM requirement set one to support high speed up to 350 km/h for FR2 as specified in TS 38.133 [14], if the field value is set1 or RRM requirement set two if the field value is set2. | +| highSpeedMeasInterFreq | If the field is present and UE supports measurementEnhancementInterFreq-r17 , the UE shall apply the enhanced RRM requirements for inter-frequency measurement in RRC_CONNECTED to support high speed up to 500 km/h as specified in TS 38.133 [14]. | + +| Conditional Presence | Explanation | +|-----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SCellOnly | The field is optionally present, Need R, in ServingCellConfigCommon of an SCell. It is absent otherwise. | +| SpCellOnly | The field is optionally present, Need R, in ServingCellConfigCommonSIB or in the ServingCellConfigCommon of an SpCell. It is absent otherwise. | +| SpCellOnly2 | The field is optionally present, Need R, in ServingCellConfigCommon of an SpCell. It is absent otherwise. | + +#### – Hysteresis + +The IE *Hysteresis* is a parameter used within the entry and leave condition of an event triggered reporting condition. The actual value is field value \* 0.5 dB. + +#### *Hysteresis* information element + +``` +-- ASN1START +-- TAG-HYSTERESIS-START + +Hysteresis ::= INTEGER (0..30) + +-- TAG-HYSTERESIS-STOP +-- ASN1STOP +``` + +#### – *HysteresisAltitude* + +The IE *HysteresisAltitude* is a parameter used within the entry and leave condition of an altitude-based event triggered reporting condition and within altitude range based parameter configuration. The actual value is field value in meters. + +#### *HysteresisAltitude* information element + +``` +-- ASN1START +-- TAG-HYSTERESISALTITUDE-START + +HysteresisAltitude-r18 ::= INTEGER (0..64) + +-- TAG-HYSTERESISALTITUDE-STOP +-- ASN1STOP +``` + +#### – *HysteresisLocation* + +The IE *HysteresisLocation* is a parameter used within entry and leave condition of a location based event triggered reporting condition. The actual value is field value \* 10 meters. + +#### *HysteresisLocation* information element + +``` +-- ASN1START +-- TAG-HYSTERESISLOCATION-START + +HysteresisLocation-r17 ::= INTEGER (0..32768) + +-- TAG-HYSTERESISLOCATION-STOP +-- ASN1STOP +``` + +#### – *InvalidSymbolPattern* + +The IE *InvalidSymbolPattern* is used to configure one invalid symbol pattern for PUSCH transmission repetition type B applicable for both DCI format 0\_1 and 0\_2, see TS 38.214 [19], clause 6.1. + +#### *InvalidSymbolPattern* information element + +``` +-- ASN1START +-- TAG-INVALIDSYMBOLPATTERN-START + +InvalidSymbolPattern-r16 ::= SEQUENCE { + symbols-r16 CHOICE { + oneSlot BIT STRING (SIZE (14)), + twoSlots BIT STRING (SIZE (28)) + }, + periodicityAndPattern-r16 CHOICE { + n2 BIT STRING (SIZE (2)), + n4 BIT STRING (SIZE (4)), + n5 BIT STRING (SIZE (5)), + n8 BIT STRING (SIZE (8)), + n10 BIT STRING (SIZE (10)), + n20 BIT STRING (SIZE (20)), + n40 BIT STRING (SIZE (40)) + } OPTIONAL, -- Need M + ... +} + +-- TAG-INVALIDSYMBOLPATTERN-STOP +-- ASN1STOP +``` + +| InvalidSymbolPattern field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

periodicityAndPattern
A time domain repetition pattern at which the pattern defined by symbols recurs. This slot pattern repeats itself continuously. When the field is not configured, the UE uses the value n1 (see TS 38.214 [19], clause 6.1).

| +|

symbols
A symbol level bitmap in time domain (see TS 38.214[19], clause 6.1).
For oneSlot, if ECP is configured, the first 12 bits represent the symbols within the slot and the last two bits within the bitstring are ignored by the UE; Otherwise, the 14 bits represent the symbols within the slot.
For twoSlots, if ECP is configured, the first 12 bits represent the symbols within the first slot and the next 12 bits represent the symbols in the second slot and the last four bits within the bit string are ignored by the UE; Otherwise, the first 14 bits represent the symbols within the first slot and the next 14 bits represent the symbols in the second slot.
For the bits representing symbols in a slot, the most significant bit of the bit string represents the first symbol in the slot and the second most significant bit represents the second symbol in the slot and so on.
This pattern recurs (in time domain) with the configured periodicityAndPattern.

| + +#### — *I-RNTI-Value* + +The IE *I-RNTI-Value* is used to identify the suspended UE context of a UE in RRC\_INACTIVE. + +#### *I-RNTI-Value* information element + +``` +-- ASN1START +-- TAG-I-RNTI-VALUE-START + +I-RNTI-Value ::= BIT STRING (SIZE(40)) + +-- TAG-I-RNTI-VALUE-STOP +-- ASN1STOP +``` + +#### — *LBT-FailureRecoveryConfig* + +The IE *LBT-FailureRecoveryConfig-r16* is used to configure the parameters used for detection of consistent uplink LBT failures for operation with shared spectrum channel access, as specified in TS 38.321 [3]. + +#### *LBT-FailureRecoveryConfig* information element + +``` +-- ASN1START +-- TAG-LBT-FAILURERECOVERYCONFIG-START + +LBT-FailureRecoveryConfig-r16 ::= SEQUENCE { + lbt-FailureInstanceMaxCount-r16 ENUMERATED {n4, n8, n16, n32, n64, n128}, + lbt-FailureDetectionTimer-r16 ENUMERATED {ms10, ms20, ms40, ms80, ms160, ms320}, + ... +} + +-- TAG-LBT-FAILURERECOVERYCONFIG-STOP +-- ASN1STOP +``` + +#### *LBT-FailureRecoveryConfig* field descriptions + +| | | +|-------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| lbt-FailureDetectionTimer | Timer for consistent uplink LBT failure detection (see TS 38.321 [3]). Value ms10 corresponds to 10 ms, value ms20 corresponds to 20 ms, and so on. | +| lbt-FailureInstanceMaxCount | This field determines after how many LBT failure indications received from the physical layer the UE triggers uplink LBT failure recovery (see TS 38.321 [3]). Value n4 corresponds to 4, value n8 corresponds to 8, and so on. | + +#### — *LocationInfo* + +The IE *LocationInfo* is used to transfer available detailed location information, Bluetooth, WLAN and sensor available measurement results at the UE. + +#### LocationInfo information element + +``` +-- ASN1START +-- TAG-LOCATIONINFO-START + +LocationInfo-r16 ::= SEQUENCE { + commonLocationInfo-r16 CommonLocationInfo-r16 OPTIONAL, + bt-LocationInfo-r16 LogMeasResultListBT-r16 OPTIONAL, + wlan-LocationInfo-r16 LogMeasResultListWLAN-r16 OPTIONAL, + sensor-LocationInfo-r16 Sensor-LocationInfo-r16 OPTIONAL, + ... +} + +-- TAG-LOCATIONINFO-STOP +-- ASN1STOP +``` + +#### LocationMeasurementInfo + +The IE *LocationMeasurementInfo* defines the information sent by the UE to the network to assist with the configuration of measurement gaps for location related measurements. + +#### LocationMeasurementInfo information element + +``` +-- ASN1START +-- TAG-LOCATIONMEASUREMENTINFO-START + +LocationMeasurementInfo ::= CHOICE { + eutra-RSTD EUTRA-RSTD-InfoList, + ..., + eutra-FineTimingDetection NULL, + nr-PRS-Measurement-r16 NR-PRS-MeasurementInfoList-r16 +} + +EUTRA-RSTD-InfoList ::= SEQUENCE (SIZE (1..maxInterRAT-RSTD-Freq)) OF EUTRA-RSTD-Info + +EUTRA-RSTD-Info ::= SEQUENCE { + carrierFreq ARFCN-ValueEUTRA, + measPRS-Offset INTEGER (0..39), + ... +} + +NR-PRS-MeasurementInfoList-r16 ::= SEQUENCE (SIZE (1..maxFreqLayers)) OF NR-PRS-MeasurementInfo-r16 + +NR-PRS-MeasurementInfo-r16 ::= SEQUENCE { + dl-PRS-PointA-r16 ARFCN-ValueNR, + nr-MeasPRS-RepetitionAndOffset-r16 CHOICE { + ms20-r16 INTEGER (0..19), + ms40-r16 INTEGER (0..39), + ms80-r16 INTEGER (0..79), + } +} +``` + +``` + + ms160-r16 INTEGER (0..159), + ... + }, + nr-MeasPRS-length-r16 ENUMERATED {ms1dot5, ms3, ms3dot5, ms4, ms5dot5, ms6, ms10, ms20}, + ... +} + +-- TAG-LOCATIONMEASUREMENTINFO-STOP +-- ASN1STOP + +``` + +#### LocationMeasurementInfo field descriptions + +##### **carrierFreq** + +The EARFCN value of the carrier received from upper layers for which the UE needs to perform the inter-RAT RSTD measurements. + +##### **measPRS-Offset** + +Indicates the requested gap offset for performing RSTD measurements towards E-UTRA. It is the smallest subframe offset from the beginning of subframe 0 of SFN=0 of the serving cell of the requested gap for measuring PRS positioning occasions in the carrier frequency *carrierFreq* for which the UE needs to perform the inter-RAT RSTD measurements. The PRS positioning occasion information is received from upper layers. The value of *measPRS-Offset* is obtained by mapping the starting subframe of the PRS positioning occasion in the measured cell onto the corresponding subframe in the serving cell and is calculated as the serving cell's number of subframes from SFN=0 mod 40. + +The UE shall take into account any additional time required by the UE to start PRS measurements on the other carrier when it does this mapping for determining the *measPRS-Offset*. + +NOTE: Figure 6.2.2-1 in TS 36.331[10] illustrates the *measPRS-Offset* field. + +##### **dl-PRS-PointA** + +The ARFCN value of the carrier received from upper layers for which the UE needs to perform the NR DL-PRS measurements. + +##### **nr-MeasPRS-RepetitionAndOffset** + +Indicates the gap periodicity in ms and offset in number of subframes of the requested measurement gap for performing NR DL-PRS measurements. + +##### **nr-MeasPRS-length** + +Indicates measurement gap length in ms of the requested measurement gap for performing NR DL-PRS measurements. The measurement gap length is according to in Table 9.1.2-1 in TS 38.133 [14]. + +#### — *LogicalChannelConfig* + +The IE *LogicalChannelConfig* is used to configure the logical channel parameters. + +#### *LogicalChannelConfig* information element + +``` + +-- ASN1START +-- TAG-LOGICALCHANNELCONFIG-START + +LogicalChannelConfig ::= SEQUENCE { + ul-SpecificParameters SEQUENCE { + priority INTEGER (1..16), + prioritisedBitRate ENUMERATED {kBps0, kBps8, kBps16, kBps32, kBps64, kBps128, kBps256, kBps512, + kBps1024, kBps2048, kBps4096, kBps8192, kBps16384, kBps32768, kBps65536, infinity}, + } +} + +``` + +``` + +bucketSizeDuration ENUMERATED {ms5, ms10, ms20, ms50, ms100, ms150, ms300, ms500, ms1000, + spare7, spare6, spare5, spare4, spare3, spare2, spare1}, +allowedServingCells SEQUENCE (SIZE (1..maxNrofServingCells-1)) OF ServCellIndex + OPTIONAL, -- Cond PDCP-CADuplication +allowedSCS-List SEQUENCE (SIZE (1..maxSCSs)) OF SubcarrierSpacing + OPTIONAL, -- Need R +maxPUSCH-Duration ENUMERATED {ms0p02, ms0p04, ms0p0625, ms0p125, ms0p25, ms0p5, ms0p01-v1700, spare1} + OPTIONAL, -- Need R +configuredGrantType1Allowed ENUMERATED {true} + OPTIONAL, -- Need R +logicalChannelGroup INTEGER (0..maxLCG-ID) + OPTIONAL, -- Need R +schedulingRequestID SchedulingRequestId + OPTIONAL, -- Need R +logicalChannelSR-Mask BOOLEAN, +logicalChannelSR-DelayTimerApplied BOOLEAN, +.... +bitRateQueryProhibitTimer ENUMERATED {s0, s0dot4, s0dot8, s1dot6, s3, s6, s12, s30} + OPTIONAL, -- Need R +[[ +allowedCG-List-r16 SEQUENCE (SIZE (0.. maxNrofConfiguredGrantConfigMAC-1-r16)) OF ConfiguredGrantConfigIndexMAC-r16 + OPTIONAL, -- Need S +allowedPHY-PriorityIndex-r16 ENUMERATED {p0, p1} + OPTIONAL -- Need S +]], +[[ +logicalChannelGroupIAB-Ext-r17 INTEGER (0..maxLCG-ID-IAB-r17) + OPTIONAL, -- Need R +allowedHARQ-mode-r17 ENUMERATED {harqModeA, harqModeB} + OPTIONAL -- Need R +]] +} + OPTIONAL, -- Cond UL +.... +[[ +channelAccessPriority-r16 INTEGER (1..4) + OPTIONAL, -- Need R +bitRateMultiplier-r16 ENUMERATED {x40, x70, x100, x200} + OPTIONAL -- Need R +]] +} + +-- TAG-LOGICALCHANNELCONFIG-STOP +-- ASN1STOP + +``` + +| LogicalChannelConfig field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| allowedCG-List
This restriction applies only when the UL grant is a configured grant. If present, UL MAC SDUs from this logical channel can only be mapped to the indicated configured grant configuration. If the size of the sequence is zero, then UL MAC SDUs from this logical channel cannot be mapped to any configured grant configurations. If the field is not present, UL MAC SDUs from this logical channel can be mapped to any configured grant configurations. If the field configuredGrantType1Allowed is present, only those configured grant type 1 configuration indicated in this sequence are allowed for use by this logical channel; otherwise, this sequence shall not include any configured grant type 1 configuration. Corresponds to "allowedCG-List" as specified in TS 38.321 [3]. This field is ignored when SDT procedure is ongoing. | +| allowedHARQ-mode
Indicates the allowed HARQ mode of a HARQ process mapped to this logical channel. If the parameter is absent, there is no restriction for HARQ mode for the mapping. This field applies to SRB1, SRB2 and DRBs. | +| allowedPHY-PriorityIndex
This restriction applies only when the UL grant is a dynamic grant. If the field is present and the dynamic grant has a PHY-priority index, UL MAC SDUs from this logical channel can only be mapped to the dynamic grants indicating PHY-priority index equal to the values configured by this field. If the field is present and the dynamic grant does not have a PHY-priority index, UL MAC SDUs from this logical channel can only be mapped to this dynamic grant if the value of the field is p0 , see TS 38.213 [13], clause 9. If the field is not present, UL MAC SDUs from this logical channel can be mapped to any dynamic grants. Corresponds to "allowedPHY-PriorityIndex" as specified in TS 38.321 [3]. | +| allowedSCS-List
If present, UL MAC SDUs from this logical channel can only be mapped to the indicated numerology. Otherwise, UL MAC SDUs from this logical channel can be mapped to any configured numerology. Corresponds to 'allowedSCS-List' as specified in TS 38.321 [3].
Only the following values are applicable depending on the used frequency:
FR1: 15, 30, or 60 kHz
FR2-1: 60 or 120 kHz
FR2-2: 120, 480, or 960 kHz | +| allowedServingCells
If present, UL MAC SDUs from this logical channel can only be mapped to the serving cells indicated in this list. Otherwise, UL MAC SDUs from this logical channel can be mapped to any configured serving cell of this cell group. Corresponds to 'allowedServingCells' in TS 38.321 [3]. | +| bitRateMultiplier
Bit rate multiplier for recommended bit rate MAC CE as specified in TS 38.321 [3]. Value x40 indicates bit rate multiplier 40, value x70 indicates bit rate multiplier 70 and so on. | +| bitRateQueryProhibitTimer
The timer is used for bit rate recommendation query in TS 38.321 [3], in seconds. Value s0 means 0 s, s0dot4 means 0.4 s and so on. | +| bucketSizeDuration
Value in ms. ms5 corresponds to 5 ms, value ms10 corresponds to 10 ms, and so on. | +| channelAccessPriority
Indicates the Channel Access Priority Class (CAPC), as specified in TS 38.300 [2], to be used on uplink transmissions for operation with shared spectrum channel access in FR1. The network configures this field only for SRB2 and DRBs. | +| configuredGrantType1Allowed
If present, or if the capability lcp-Restriction as specified in TS 38.306 [26] is not supported, UL MAC SDUs from this logical channel can be transmitted on a configured grant type 1. Otherwise, UL MAC SDUs from this logical channel cannot be transmitted on a configured grant type 1. Corresponds to 'configuredGrantType1Allowed' in TS 38.321 [3]. This field is ignored when SDT procedure is ongoing. | +| logicalChannelGroup, logicalChannelGroupIAB-Ext
ID of the logical channel group, as specified in TS 38.321 [3], which the logical channel belongs to. The logicalChannelGroupIAB-Ext is only applicable to the IAB-MT. When logicalChannelGroupIAB-Ext is configured, logicalChannelGroup shall be ignored. | +| logicalChannelSR-Mask
Controls SR triggering when a configured uplink grant of type1 or type2 is configured. true indicates that SR masking is configured for this logical channel as specified in TS | + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 38.321 [3]. | +| logicalChannelSR-DelayTimerApplied
Indicates whether to apply the delay timer for SR transmission for this logical channel. Set to false if logicalChannelSR-DelayTimer is not included in BSR-Config . | +| maxPUSCH-Duration
If present, UL MAC SDUs from this logical channel can only be transmitted using uplink grants that result in a PUSCH duration shorter than or equal to the duration indicated by this field. Otherwise, UL MAC SDUs from this logical channel can be transmitted using an uplink grant resulting in any PUSCH duration. Corresponds to "maxPUSCH-Duration" in TS 38.321 [3]. The PUSCH duration is calculated based on the same length of all symbols, and the shortest length applies if the symbol lengths are different. | +| priority
Logical channel priority, as specified in TS 38.321 [3]. | +| prioritisedBitRate
Value in kiloBytes/s. Value kBps0 corresponds to 0 kiloBytes/s, value kBps8 corresponds to 8 kiloBytes/s, value kBps16 corresponds to 16 kiloBytes/s, and so on. For SRBs, the value can only be set to infinity . | +| schedulingRequestId
If present, it indicates the scheduling request configuration applicable for this logical channel, as specified in TS 38.321 [3]. | + +| Conditional Presence | Explanation | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PDCP-CADuplication | The field is mandatory present if the DRB/SRB associated with this logical channel is configured with PDCP CA duplication in UL in the cell group in which this IE is included (i.e. the PDCP entity is associated with multiple RLC entities belonging to this cell group). Otherwise the field is optionally present, need R. | +| UL | The field is mandatory present for a logical channel with uplink if it serves DRB or multicast MRB. It is optionally present, Need R, for a logical channel with uplink if it serves an SRB. Otherwise it is absent. | + +#### – *LogicalChannelIdentity* + +The IE *LogicalChannelIdentity* is used to identify one logical channel (*LogicalChannelConfig*) and the corresponding RLC bearer (*RLC-BearerConfig*) or BH RLC channel (*BH-RLC-ChannelConfig*) or Uu Relay RLC channel (*Uu-RelayRLC-ChannelConfig*) or PC5 Relay RLC channel (*SL-RLC-ChannelConfig*). + +#### *LogicalChannelIdentity* information element + +``` +-- ASN1START +-- TAG-LOGICALCHANNELIDENTITY-START + +LogicalChannelIdentity ::= INTEGER (1..maxLC-ID) + +-- TAG-LOGICALCHANNELIDENTITY-STOP +-- ASN1STOP +``` + +#### – *LTE-NeighCellsCRS-AssistInfoList* + +The IE *LTE-NeighCellsCRS-AssistInfoList-r17* is used to provide configuration information of neighbour LTE cells to assist the UE to perform CRS interference mitigation (CRS-IM) in scenarios with overlapping spectrum for LTE and NR. + +#### LTE-NeighCellsCRS-AssistInfoList information element + +``` + +-- ASN1START +-- TAG-LTE-NEIGHCELLSCRS-ASSISTINFOLIST-START + +LTE-NeighCellsCRS-AssistInfoList-r17 ::= SEQUENCE (SIZE (1..maxNrofCRS-IM-InterfCell-r17)) OF LTE-NeighCellsCRS-AssistInfo-r17 + +LTE-NeighCellsCRS-AssistInfo-r17 ::= SEQUENCE { + neighCarrierBandwidthDL-r17 ENUMERATED {n6, n15, n25, n50, n75, n100, spare2, spare1} OPTIONAL, -- Cond CRS-IM + neighCarrierFreqDL-r17 INTEGER (0..16383) OPTIONAL, -- Need S + neighCellId-r17 EUTRA-PhysCellId OPTIONAL, -- Need S + neighCRS-muting-r17 ENUMERATED {enabled} OPTIONAL, -- Need R + neighMBSFN-SubframeConfigList-r17 EUTRA-MBSFN-SubframeConfigList OPTIONAL, -- Need S + neighNrofCRS-Ports-r17 ENUMERATED {n1, n2, n4} OPTIONAL, -- Need S + neighV-Shift-r17 ENUMERATED {n0, n1, n2, n3, n4, n5} OPTIONAL -- Cond NotCellID +} + +-- TAG-LTE-NEIGHCELLSCRS-ASSISTINFOLIST-STOP +-- ASN1STOP + +``` + +#### LTE-NeighCellsCRS-AssistInfo field descriptions + +| | | +|--------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| neighCarrierBandwidthDL | Indicates the channel bandwidth of the neighbour LTE cell in number of PRBs. If the field is absent, the UE applies the value of carrierBandwidthDL indicated in RateMatchPatternLTE-CRS for this serving cell, if configured. | +| neighCarrierFreqDL | Indicates the downlink centre frequency of the neighbour LTE cell. If the field is absent, the UE applies the value of carrierFreqDL indicated in RateMatchPatternLTE-CRS for this serving cell, if configured. | +| neighCellId | Indicates the physical cell ID of the neighbour LTE cell for which the other fields within the same LTE-NeighCellsCRS-AssistInfo apply.
If the IE LTE-NeighCellsCRS-AssistInfoList contains multiple list entries, either this field or neighV-Shift is included in each instance.
If the IE LTE-NeighCellsCRS-AssistInfoList contains multiple list entries, the entry with neighV-Shift is only used for neighbour LTE cells for which neighCellId is not provided (i.e. the entry with neighCellId takes precedence over the entry with neighV-Shift , if provided).
If the IE LTE-NeighCellsCRS-AssistInfoList contains one list entry with neither this field nor neighV-Shift , the information within the entry applies to all neighbour LTE cells. | +| neighCRS-muting | Indicates whether the CRS interference mitigation is enabled in the neighbour LTE cell, as specified in TS 36.133 [40], clause 3.6.1.1. | +| neighMBSFN-SubframeConfigList | Indicates the MBSFN subframe configuration of the neighbour LTE cell. If RateMatchPatternLTE-CRS is configured for this serving cell and the field is absent, the UE applies the value of mbsfn-SubframeConfigList indicated in RateMatchPatternLTE-CRS for this serving cell if configured; otherwise, if the field is absent, the UE assumes MBSFN is not configured in the neighbour LTE cell. | +| neighNrofCRS-Ports | Indicates the CRS antenna ports number of the neighbour LTE cell. If the field is absent, the UE applies the value of nrofCRS-Ports indicated in RateMatchPatternLTE-CRS for this serving cell, if configured. If RateMatchPatternLTE-CRS is not configured for this serving cell and the field is absent, the UE applies the default value n4. | +| neighV-Shift | Indicates the shifting value v-shift of neighbour LTE cells for which the other fields within the same LTE-NeighCellsCRS-AssistInfo apply. | + +| Conditional Presence | Explanation | +|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CRS-IM |

For the serving cell with 15kHz SCS, this field is mandatory present for the UE supporting the capability of crs-IM-nonDSS-NWA-15kHzSCS-r17, but not supporting crs-IM-nonDSS-15kHzSCS-r17, if RateMatchPatternLTE-CRS is not configured for this serving cell. Otherwise it is optionally present, Need S if RateMatchPatternLTE-CRS is configured for this serving cell; Need M otherwise.

For the serving cell with 30kHz SCS, this field is mandatory present for the UE supporting the capability of crs-IM-nonDSS-NWA-30kHzSCS-r17, but not supporting crs-IM-nonDSS-30kHzSCS-r17, if RateMatchPatternLTE-CRS is not configured for this serving cell. Otherwise it is optionally present, Need S if RateMatchPatternLTE-CRS is configured for this serving cell; Need M otherwise.

| +| NotCellID |

If the field neighCellId is present, this field shall be absent; otherwise, it is optionally present if the IE LTE-NeighCellsCRS-AssistInfoList contains one list entry, Need S, or it is mandatory present if the IE LTE-NeighCellsCRS-AssistInfoList contains multiple list entries.

| + +#### – *LTM-CandidateId* + +The IE *LTM-CandidateId* is used to identify an LTM candidate configuration. + +#### *LTM-CandidateId* information element + +``` +-- ASN1START +-- TAG-LTM-CANDIDATEID-START + +LTM-CandidateId-r18 ::= INTEGER (1..maxNrofLTM-Configs-r18) + +-- TAG-LTM-CANDIDATEID-STOP +-- ASN1STOP +``` + +#### – *LTM-Candidate* + +The IE *LTM-Candidate* concerns a LTM candidate configuration to add or modify. + +#### *LTM-Candidate* information element + +``` +-- ASN1START +-- TAG-LTM-CANDIDATE-START + +LTM-Candidate-r18 ::= SEQUENCE { + ltm-CandidateId-r18 LTM-CandidateId-r18, + ltm-CandidatePCI-r18 PhysCellId, + ltm-SSB-Config-r18 LTM-SSB-Config-r18 OPTIONAL, -- Need M + ltm-CandidateConfig-r18 OCTET STRING (CONTAINING RRCReconfiguration) OPTIONAL, -- Need M + ltm-ConfigComplete-r18 ENUMERATED {true} OPTIONAL, -- Need R + ltm-EarlyUL-SyncConfig-r18 SetupRelease { EarlyUL-SyncConfig-r18 } OPTIONAL, -- Need M + ltm-EarlyUL-SyncConfigSUL-r18 SetupRelease { EarlyUL-SyncConfig-r18 } OPTIONAL, -- Need M +} +``` + +``` + +ltm-NoResetID-r18 INTEGER (1..maxNrofLTM-Configs-r18-plus-1) OPTIONAL, -- Need M +ltm-DL-OrJointTCI-StateToAddModList-r18 SEQUENCE (SIZE (1..maxNrofCandidateTCI-State-r18)) OF CandidateTCI-State-r18 + OPTIONAL, -- Need N +ltm-DL-OrJointTCI-StateToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofCandidateTCI-State-r18)) OF TCI-StateId + OPTIONAL, -- Need N +ltm-UL-TCI-StatesToAddModList-r18 SEQUENCE (SIZE (1..maxNrofCandidateUL-TCI-r18)) OF CandidateTCI-UL-State-r18 + OPTIONAL, -- Need N +ltm-UL-TCI-StatesToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofCandidateUL-TCI-r18)) OF TCI-UL-StateId-r17 + OPTIONAL, -- Need N +ltm-nzp-CSI-RS-ResourceToAddModList-r18 SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-Resources)) OF NZP-CSI-RS-Resource + OPTIONAL, -- Need N +ltm-nzp-CSI-RS-ResourceToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-Resources)) OF NZP-CSI-RS-ResourceId + OPTIONAL, -- Need N +ltm-nzp-CSI-RS-ResourceSetToAddModList-r18 SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourceSets)) OF NZP-CSI-RS-ResourceSet + OPTIONAL, -- Need N +ltm-nzp-CSI-RS-ResourceSetToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourceSets)) OF NZP-CSI-RS-ResourceSetId + OPTIONAL, -- Need N +pathlossReferenceRS-ToAddModList-r18 SEQUENCE (SIZE (1..maxNrofPathlossReferenceRSs-r17)) OF PathlossReferenceRS-r17 + OPTIONAL, -- Need N +pathlossReferenceRS-ToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofPathlossReferenceRSs-r17)) OF PathlossReferenceRS-Id-r17 + OPTIONAL, -- Need N +ltm-UE-MeasuredTA-ID-r18 INTEGER (1..maxNrofLTM-Configs-r18-plus-1) OPTIONAL, -- Need M +... +} + +LTM-SSB-Config-r18 ::= SEQUENCE { + ssbFrequency-r18 ARFCN-ValueNR, + subcarrierSpacing-r18 SubcarrierSpacing, + ssb-Periodicity-r18 ENUMERATED {ms5, ms10, ms20, ms40, ms80, ms160, spare2, spare1} OPTIONAL, -- Need R + ssb-PositionsInBurst-r18 CHOICE { + shortBitmap BIT STRING (SIZE (4)), + mediumBitmap BIT STRING (SIZE (8)), + longBitmap BIT STRING (SIZE (64)) + } + ss-PBCH-BlockPower-r18 INTEGER (-60..50) + ... +} + +-- TAG-LTM-CANDIDATE-STOP +-- ASN1STOP + +``` + +| LTM-Candidate field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Itm-CandidateConfig
This field includes an RRCReconfiguration message used to configure an LTM candidate cell. | +| Itm-CandidateId
This field indicates an LTM candidate configuration. | +| Itm-CandidatePCI
This field identifies the PCI of the SpCell of the configuration contained in Itm-CandidateConfig . | +| Itm-ConfigComplete
This field indicates whether the LTM candidate configuration within Itm-CandidateConfig is a complete configuration. | +| Itm-DL-OrJointTCI-StateToAddModList
A list of TCI states for LTM to add and/or modify. | +| Itm-DL-OrJointTCI-StateToReleaseList
A list of TCI states for LTM to remove. | +| Itm-EarlyUL-SyncConfig, Itm-EarlyUL-SyncConfigSUL
A configuration used to perform the early UL synchronization procedure over an UL or SUL carrier. | +| Itm-nzp-CSI-RS-ResourceSetToAddModList
A list of nzp-CSI-RS-Resources set for LTM to add and/or modify. | +| Itm-nzp-CSI-RS-ResourceSetToReleaseList
A list of nzp-CSI-RS-Resources set for LTM to remove. | +| Itm-nzp-CSI-RS-ResourceToAddModList
A list of nzp-CSI-RS-Resources for LTM to add and/or modify. | +| Itm-nzp-CSI-RS-ResourceToReleaseList
A list of nzp-CSI-RS-Resources for LTM to remove. | +| Itm-SSB-Config
This field indicates the configuration of SS/PBCH blocks to be used for L1 measurements configured with Itm-CSI-ReportConfigToAddModList in CSI-MeasConfig and for TCI states configured in other fields in LTM-Candidate . | +| Itm-UE-MeasuredTA-ID
This field indicates whether the UE should perform UE-based TA measurements towards an LTM candidate. | +| Itm-UL-TCI-StatesToAddModList
A list of uplink TCI states for LTM to add and/or modify. | +| Itm-UL-TCI-StatesToReleaseList
A list of uplink TCI states for LTM to remove. | +| pathlossReferenceRS-ToAddModList
A list of Reference Signals to be used for path loss estimation for unified TCI state for LTM to add and/or modify. | +| pathlossReferenceRS-ToReleaseList
A list of Reference Signals to be used for path loss estimation for unified TCI state for LTM to add and/or modify. | + +| LTM-SSB-Config field descriptions | | +|------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ssbFrequency | Indicates the frequency of the SS/PBCH block associated with the LTM candidate cell. | +| ssb-Periodicity | Indicates the periodicity of the SS/PBCH block. | +| ssb-PositionsInBurst | Indicates the time domain positions of the transmitted SS-blocks in a half frame with SS/PBCH blocks as defined in TS 38.213. 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. | +| ss-PBCH-BlockPower | Indicates the average EPRE of the resources elements that carry secondary synchronization signals in dBm that the network uses for SSB transmission on the LTM candidate cell. | +| subCarrierSpacing | Indicates the subcarrier spacing of the SSB. | + +## — LTM-Config + +The IE *LTM-Config* is used to provide LTM candidate configurations. + +### **LTM-Config information element** + +``` +-- ASN1START +-- TAG-LTM-CONFIG-START + +LTM-Config-r18 ::= SEQUENCE { + ltm-ReferenceConfiguration-r18 SetupRelease {ReferenceConfiguration-r18} OPTIONAL, -- Need M + ltm-CandidateToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofLTM-Configs-r18)) OF LTM-CandidateId-r18 OPTIONAL, -- Need N + ltm-CandidateToAddModList-r18 SEQUENCE (SIZE (1..maxNrofLTM-Configs-r18)) OF LTM-Candidate-r18 OPTIONAL, -- Need N + ltm-ServingCellNoResetID-r18 INTEGER (1..maxNrofLTM-Configs-r18-plus-1) OPTIONAL, -- Cond FirstLTM-Only + ltm-CSI-ResourceConfigToAddModList-r18 SEQUENCE (SIZE (1..maxNrofLTM-CSI-ResourceConfigurations-r18)) OF LTM-CSI-ResourceConfig-r18 OPTIONAL, -- Need N + ltm-CSI-ResourceConfigToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofLTM-CSI-ResourceConfigurations-r18)) OF LTM-CSI-ResourceConfigId-r18 OPTIONAL, -- Need N + attemptLTM-Switch-r18 ENUMERATED {true} OPTIONAL, -- Cond LTM-MCG + ltm-ServingCellUE-MeasuredTA-ID-r18 INTEGER (1..maxNrofLTM-Configs-r18-plus-1) OPTIONAL, -- Cond LTM + ... +} + +-- TAG-LTM-CONFIG-STOP +-- ASN1STOP +``` + +| LTM-Config field descriptions | | +|---------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| attemptLTM-Switch | If present, the UE shall execute an LTM cell switch if selected cell is a LTM candidate cell and it is the first cell selection after failure as described in clause 5.3.7.3. | +| Itm-CandidateToAddModList | List of LTM candidate configurations to add and/or modify. | +| Itm-CandidateToReleaseList | List of LTM candidate configurations to remove. | +| Itm-CSI-ResourceConfigToAddModList | List of LTM CSI resource configurations to add and/or modify. | +| Itm-CSI-ResourceConfigToReleaseList | List of LTM CSI resource configurations to remove. | +| Itm-ReferenceConfiguration | This field includes an RRCReconfiguration message used to configure a reference configuration for LTM. | +| Itm-ServingCellNoResetID | This field is used by the UE to determine on whether L2 reset should be performed when an LTM cell switch procedure is triggered towards an LTM candidate cell. | +| Itm-ServingCellUE-MeasuredTA-ID | This field is used by the UE to determine whether UE-based TA measurements should be performed towards an LTM candidate cell. | + +| Conditional Presence | Explanation | +|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| FirstLTM-Only | This field is mandatory present in the first RRCReconfiguration message which include LTM-Config with at least one LTM candidate configuration. Otherwise, the field is absent, Need M. | +| LTM | This field is optional present, Need M, if the UE is configured with at least an LTM candidate configuration. Otherwise, the field is absent. | +| LTM-MCG | This field is optional present for the MCG, Need R, if the UE is configured with at least an LTM candidate configuration associated to the MCG. Otherwise, the field absent. | + +#### – *LTM-CSI-ReportConfig* + +The IE *LTM-CSI-ReportConfig* is used to configure report on the cell in which the *LTM-CSI-ReportConfig* is included. + +#### *LTM-CSI-ReportConfig* information element + +``` +-- ASN1START +-- TAG-LTM-CSI-REPORTCONFIG-START + +LTM-CSI-ReportConfig-r18 ::= SEQUENCE { + ltm-CSI-ReportConfigId-r18 LTM-CSI-ReportConfigId-r18, + ltm-ResourcesForChannelMeasurement-r18 LTM-CSI-ResourceConfigId-r18, + ltm-ReportConfigType-r18 CHOICE { + periodic-r18 SEQUENCE { + reportSlotConfig-r18 CSI-ReportPeriodicityAndOffset, + pucch-CSI-ResourceList-r18 SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource + }, + }, +} +``` + +``` + + semiPersistentOnPUCCH-r18 SEQUENCE { + reportSlotConfig-r18 CSI-ReportPeriodicityAndOffset, + pucch-CSI-ResourceList-r18 SEQUENCE (SIZE (1..maxNrofBWP)) OF PUCCH-CSI-Resource + }, + semiPersistentOnPUSCH-r18 SEQUENCE { + reportSlotConfig-r18 CSI-ReportPeriodicityAndOffset, + reportSlotOffsetList-r18 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER (0..128), + reportSlotOffsetListDCI-0-2-r18 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER (0..128), + reportSlotOffsetListDCI-0-1-r18 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER (0..128), + p0alpha P0-PUSCH-AlphaSetId + }, + aperiodic-r18 SEQUENCE { + reportSlotOffsetList-r18 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER (0..128), + reportSlotOffsetListDCI-0-2-r18 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER (0..128), + reportSlotOffsetListDCI-0-1-r18 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER (0..128) + } +}, +ltm-ReportContent-r18 LTM-ReportContent-r18, +... +} + +LTM-ReportContent-r18 ::= SEQUENCE { + nrOfReportedCells-r18 ENUMERATED {n1,n2,n3,n4}, + nrOfReportedRS-PerCell-r18 ENUMERATED {n1,n2,n3,n4}, + spCellInclusion-r18 ENUMERATED {true} OPTIONAL -- Need R +} + +-- TAG-LTM-CSI-REPORTCONFIG-STOP +-- ASN1STOP + +``` + +| LTM-CSI-ReportConfig field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ltm-CSI-ReportConfigId
This field is used to identify an LTM-CSI-ReportConfig . | +| ltm-ReportContent
This field defines the content of the LTM L1 measurement report. | +| ltm-ResourcesForChannelMeasurement
This field indicates the resources used for LTM L1 measurements. | +| pucch-CSI-ResourceList
Indicates which PUCCH resource to use for reporting on PUCCH. | +| reportConfigType
This field describes the time domain behaviour of how the L1 measurements for LTM are reported. | +| reportSlotConfig
Periodicity and slot offset (see TS 38.214 [19], clause 5.2.1.4). | +| reportSlotOffsetList, reportSlotOffsetListDCI-0-1, reportSlotOffsetListDCI-0-2
Timing offset Y for semi persistent reporting using PUSCH and aperiodic reporting. | + +| LTM-ReportContent field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| nrOfReportedCells
This field defines how many cells are reported within a single L1 measurement report instance. | +| nrOfReportedRS-PerCell
This field defines how many RSs per cell are reported within a single L1 measurement report instance. | +| spCellInclusion
This field indicates whether the UE shall include a L1 measurement report associated to the current SpCell. This field can only be configured if the current SpCell is configured as an LTM candidate cell. | + +#### – ***LTM-CSI-ReportConfigId*** + +The IE *LTM-CSI-ReportConfigId* is used to identify an *LTM-CSI-ReportConfig*. + +#### ***LTM-CSI-ReportConfigId* information element** + +``` +-- ASN1START +-- TAG-LTM-CSI-REPORTCONFIGID-START + +LTM-CSI-ReportConfigId-r18 ::= INTEGER (0..maxNrofLTM-CSI-ReportConfigurations-1-r18) + +-- TAG-LTM-CSI-REPORTCONFIGID-STOP +-- ASN1STOP +``` + +#### – ***LTM-CSI-ResourceConfig*** + +The IE *LTM-CSI-ResourceConfig* defines a group of one or more CSI resources for one or more LTM candidate configurations. + +#### ***LTM-CSI-ResourceConfig* information element** + +``` +-- ASN1START +-- TAG-LTM-CSI-RESOURCECONFIG-START + +LTM-CSI-ResourceConfig-r18 ::= SEQUENCE { + ltm-CSI-ResourceConfigId-r18 LTM-CSI-ResourceConfigId-r18, + ltm-CSI-SSB-ResourceSet-r18 LTM-CSI-SSB-ResourceSet-r18, + ... +} + +LTM-CSI-SSB-ResourceSet-r18 ::= SEQUENCE { + ltm-CSI-SSB-ResourceList-r18 SEQUENCE (SIZE (1..maxNrofLTM-CSI-SSB-ResourcesPerSet-r18)) OF SSB-Index, + ltm-CandidateIdList-r18 SEQUENCE (SIZE (1..maxNrofLTM-CSI-SSB-ResourcesPerSet-r18)) OF LTM-CandidateId-r18, + ... +} + +-- TAG-LTM-CSI-RESOURCECONFIG-STOP +``` + +``` +-- ASN1STOP +``` + +| LTM-CSI-ResourceConfig field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------| +| Itm-CSI-ResourceConfigId
This field is used to identify an instance of LTM-CSI-ResourceConfig IE. | +| Itm-CSI-SSB-ResourceSet
This field defines one SS/PBCH block resource set from one or more LTM candidate cells. | + +| LTM-CSI-SSB-ResourceSet field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Itm-CandidateIdList
This field Indicates the LTM candidate cell IDs related to the SSBs in the Itm-CSI-SSB-ResourceList . The list has the same number of entries as Itm-CSI-SSB-ResourceList . | +| Itm-CSI-SSB-ResourceList
This field is used to indicate on SS/PBCH block resources from one or more LTM candidate cells. | +| Itm-CSI-SSB-ResourceSetId
This field is used to identify on SS/PBCH block resource set. | + +#### – ***LTM-CSI-ResourceConfigId*** + +The IE *LTM-CSI-ResourceConfigId* is used to identify an *LTM-CSI-ResourceConfig*. + +#### ***LTM-CSI-ResourceConfigId* information element** + +``` +-- ASN1START +-- TAG-LTM-CSI-RESOURCECONFIGID-START + +LTM-CSI-ResourceConfigId-r18 ::= INTEGER (0..maxNrofLTM-CSI-ResourceConfigurations-r18-1) + +-- TAG-LTM-CSI-RESOURCECONFIGID-STOP +-- ASN1STOP +``` + +#### – ***MAC-CellGroupConfig*** + +The IE *MAC-CellGroupConfig* is used to configure MAC parameters for a cell group, including DRX. + +#### ***MAC-CellGroupConfig* information element** + +``` +-- ASN1START +-- TAG-MAC-CELLGROUPCONFIG-START + +MAC-CellGroupConfig ::= SEQUENCE { + drx-Config SetupRelease { DRX-Config } OPTIONAL, -- Need M +``` + +``` + + schedulingRequestConfig SchedulingRequestConfig OPTIONAL, -- Need M + bsr-Config BSR-Config OPTIONAL, -- Need M + tag-Config TAG-Config OPTIONAL, -- Need M + phr-Config SetupRelease { PHR-Config } OPTIONAL, -- Need M + skipUplinkTxDynamic BOOLEAN, + ..., + [[ + csi-Mask BOOLEAN OPTIONAL, -- Need M + dataInactivityTimer SetupRelease { DataInactivityTimer } OPTIONAL -- Cond MCG-Only + ]], + [[ + usePreBSR-r16 ENUMERATED {true} OPTIONAL, -- Need R + schedulingRequestID-LBT-SCell-r16 SchedulingRequestId OPTIONAL, -- Need R + lch-BasedPrioritization-r16 ENUMERATED {enabled} OPTIONAL, -- Need R + schedulingRequestID-BFR-SCell-r16 SchedulingRequestId OPTIONAL, -- Need R + drx-ConfigSecondaryGroup-r16 SetupRelease { DRX-ConfigSecondaryGroup-r16 } OPTIONAL -- Need M + ]], + [[ + enhancedSkipUplinkTxDynamic-r16 ENUMERATED {true} OPTIONAL, -- Need R + enhancedSkipUplinkTxConfigured-r16 ENUMERATED {true} OPTIONAL -- Need R + ]], + [[ + intraCG-Prioritization-r17 ENUMERATED {enabled} OPTIONAL, -- Cond LCH-PrioWithReTxTimer + drx-ConfigSL-r17 SetupRelease { DRX-ConfigSL-r17 } OPTIONAL, -- Need M + drx-ConfigExt-v1700 SetupRelease { DRX-ConfigExt-v1700 } OPTIONAL, -- Need M + schedulingRequestID-BFR-r17 SchedulingRequestId OPTIONAL, -- Need R + schedulingRequestID-BFR2-r17 SchedulingRequestId OPTIONAL, -- Need R + schedulingRequestConfig-v1700 SchedulingRequestConfig-v1700 OPTIONAL, -- Need M + tar-Config-r17 SetupRelease { TAR-Config-r17 } OPTIONAL, -- Need M + g-RNTI-ConfigToAddModList-r17 SEQUENCE (SIZE (1..maxG-RNTI-r17)) OF MBS-RNTI-SpecificConfig-r17 OPTIONAL, -- Need N + g-RNTI-ConfigToReleaseList-r17 SEQUENCE (SIZE (1..maxG-RNTI-r17)) OF MBS-RNTI-SpecificConfigId-r17 OPTIONAL, -- Need N + g-CS-RNTI-ConfigToAddModList-r17 SEQUENCE (SIZE (1..maxG-CS-RNTI-r17)) OF MBS-RNTI-SpecificConfig-r17 OPTIONAL, -- Need N + g-CS-RNTI-ConfigToReleaseList-r17 SEQUENCE (SIZE (1..maxG-CS-RNTI-r17)) OF MBS-RNTI-SpecificConfigId-r17 OPTIONAL, -- Need N + allowCSI-SRS-Tx-MulticastDRX-Active-r17 BOOLEAN OPTIONAL -- Need M + ]], + [[ + schedulingRequestID-PosMG-Request-r17 SchedulingRequestId OPTIONAL, -- Need R + drx-LastTransmissionUL-r17 ENUMERATED {enabled} OPTIONAL -- Need R + ]], + [[ + posMG-Request-r17 ENUMERATED {enabled} OPTIONAL -- Need R + ]], + [[ + drx-ConfigExt2-v1800 SetupRelease { DRX-ConfigExt2-v1800 } OPTIONAL, -- Need M + additionalBSR-TableAllowed-r18 BIT STRING (SIZE (maxNrofLCGs-r18)) OPTIONAL, -- Need R + dsr-ConfigToAddModList-r18 SEQUENCE (SIZE (1..maxNrofLCGs-r18)) OF LCG-DSR-Config-r18 OPTIONAL, -- Need N + dsr-ConfigToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofLCGs-r18)) OF LCG-Id-r18 OPTIONAL, -- Need N + tar-Config-r18 SetupRelease { TAR-Config-r18 } OPTIONAL -- Need M + ]] +} + +``` + +``` +DataInactivityTimer ::= ENUMERATED {s1, s2, s3, s5, s7, s10, s15, s20, s40, s50, s60, s80, s100, s120, s150, s180} + +MBS-RNTI-SpecificConfig-r17 ::= SEQUENCE { + mbs-RNTI-SpecificConfigId-r17 MBS-RNTI-SpecificConfigId-r17, + groupCommon-RNTI-r17 CHOICE { + g-RNTI RNTI-Value, + g-CS-RNTI RNTI-Value + }, + drx-ConfigPTM-r17 SetupRelease { DRX-ConfigPTM-r17 } OPTIONAL, -- Need M + harq-FeedbackEnablerMulticast-r17 ENUMERATED {dci-enabler, enabled} OPTIONAL, -- Need S + harq-FeedbackOptionMulticast-r17 ENUMERATED {ack-nack, nack-only} OPTIONAL, -- Cond HARQFeedback + pdsch-AggregationFactor-r17 ENUMERATED {n2, n4, n8} OPTIONAL, -- Cond G-RNTI +} + +MBS-RNTI-SpecificConfigId-r17 ::= INTEGER (0..maxG-RNTI-1-r17) + +LCG-DSR-Config-r18 ::= SEQUENCE { + lcg-Id-r18 LCG-Id-r18, + remainingTimeThreshold-r18 INTEGER (1..64) +} + +LCG-Id-r18 ::= INTEGER (0..maxLCG-ID) + +-- TAG-MAC-CELLGROUPCONFIG-STOP +-- ASN1STOP +``` + +| MAC-CellGroupConfig field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| additionalBSR-TableAllowed
Indicates whether a UE is allowed to utilize the additional BSR table, as specified in TS 38.321 [3], for a certain Logical Channel Group. The leftmost bit corresponds to LCG ID=0, second leftmost bit to LCG ID=1 and so on. The UE is allowed to utilize the additional BSR table for a Logical Channel Group only when the corresponding bit is set to 1. | +| allowCSI-SRS-Tx-MulticastDRX-Active
Used to control the CSI/SRS transmission during MBS multicast DRX ActiveTime, see TS 38.321 [3]. | +| csi-Mask
If set to true, the UE limits CSI reports to the on-duration period of the DRX cycle, see TS 38.321 [3]. | +| dataInactivityTimer
Releases the RRC connection upon data inactivity as specified in clause 5.3.8.5 and in TS 38.321 [3]. Value s1 corresponds to 1 second, value s2 corresponds to 2 seconds, and so on. | +| drx-Config, drx-ConfigExt, drx-ConfigExt2
Used to configure DRX as specified in TS 38.321 [3]. Network only configures drx-ConfigExt or drx-ConfigExt2 when drx-Config is configured. | +| drx-ConfigSecondaryGroup
Used to configure DRX related parameters for the second DRX group as specified in TS 38.321 [3]. The network does not configure secondary DRX group with DCP simultaneously nor secondary DRX group with a dormant BWP simultaneously. | +| drx-ConfigSL
Used to configure additional DRX parameters for the UE performing sidelink operation with resource allocation mode 1, as specified in TS 38.321 [3]. Network only configures this field if sl-ScheduledConfig is configured and drx-Config is configured. | +| drx-LastTransmissionUL
If this field is present, the start of the drx-HARQ-RTT-TimerUL is after the last transmission within a bundle, see TS 38.321 [3]. | +| dsr-ConfigToAddModList
List of LCG-specific DSR configurations to add or modify. | +| dsr-ConfigToReleaseList
List of LCG-specific DSR configurations to release. | +| g-RNTI-ConfigToAddModList
List of G-RNTI configurations to add or modify. Up to 8 G-RNTIs can be configured in total in this release based on the UE capability. | +| g-RNTI-ConfigToReleaseList
List of G-RNTI configurations to release. | +| g-CS-RNTI-ConfigToAddModList
List of G-CS-RNTI configurations to add or modify. Up to 8 G-CS-RNTIs can be configured in total in this release based on the UE capability. | +| g-CS-RNTI-ConfigToReleaseList
List of G-CS-RNTI configurations to release. | +| intraCG-Prioritization
Used to enable HARQ process ID selection based on LCH-priority for one CG as specified in TS 38.321 [3]. | +| lch-BasedPrioritization
If this field is present, the corresponding MAC entity of the UE is configured with prioritization between overlapping grants and between scheduling request and overlapping grants based on LCH priority, see TS 38.321 [3]. The network does not configure lch-BasedPrioritization with enhancedSkipUplinkTxDynamic simultaneously nor lch-BasedPrioritization with enhancedSkipUplinkTxConfigured simultaneously. | +| posMG-Request
Indicates whether UE is configured to send UL MAC CE for Positioning Measurement Gap Activation/Deactivation Request, as specified in TS 38.321 [3]. | +| schedulingRequestID-BFR-SCell
Indicates the scheduling request configuration applicable for BFR on SCell, as specified in TS 38.321 [3]. | + +| | | +|------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| schedulingRequestID-BFR | Indicates the scheduling request configuration (SchedulingRequestConfig) that the UE shall use upon detecting a beam failure on the detection resources configured in failureDetectionSet1 of a serving cell while beam failure is not detected on resources configured in failureDetectionSet2 of the same serving cell. | +| schedulingRequestID-BFR2 | Indicates the scheduling request configuration (SchedulingRequestConfig) that the UE shall use upon detecting a beam failure on the detection resources configured in failureDetectionSet2 of a serving cell while beam failure is not detected on resources configured in failureDetectionSet1 of the same serving cell. | +| schedulingRequestID-LBT-SCell | Indicates the scheduling request configuration applicable for consistent uplink LBT recovery on SCell, as specified in TS 38.321 [3]. | +| schedulingRequestID-PosMG-Request | Indicates the scheduling request configuration applicable for Positioning Measurement Gap Activation/Deactivation Request, as specified in TS 38.321 [3]. | +| skipUplinkTxDynamic, enhancedSkipUplinkTxDynamic, enhancedSkipUplinkTxConfigured | If set to true , the UE skips UL transmissions as described in TS 38.321 [3]. If the UE is configured with enhancedSkipUplinkTxDynamic or enhancedSkipUplinkTxConfigured with value true , REPETITION_NUMBER (as specified in TS 38.321 [3], clause 5.4.2.1) of the corresponding PUSCH transmission of the uplink grant shall be equal to 1. | +| tag-Config | The field is used to configure parameters for a time-alignment group. The field is not present if any DAPS bearer is configured. | +| usePreBSR | If set to true, the MAC entity of the IAB-MT may use the Pre-emptive BSR, see TS 38.321 [3]. | + +| MBS-RNTI-SpecificConfig field descriptions | | +|----------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| drx-ConfigPTM | Used to configure DRX for PTM transmission as specified in TS 38.321 [3]. | +| g-CS-RNTI | Used to scramble the SPS group-common PDSCH and activation/deactivation of SPS group-common PDSCH for one or more MBS multicast services. | +| g-RNTI | Used to scramble the scheduling and transmission of PTM for one or more MBS multicast services. | +| groupCommon-RNTI | Used to configure g-RNTI or g-CS-RNTI. | +| harq-FeedbackEnablerMulticast | Indicates whether the UE shall provide HARQ feedback for MBS multicast. Value dci-enabler means that whether the UE shall provide HARQ feedback for MBS multicast is indicated by DCI as specified in TS 38.213 [13]. Value enabled means the UE shall always provide HARQ feedback for MBS multicast. When the field is absent, the UE behavior is specified in TS 38.213 [13]. | +| harq-FeedbackOptionMulticast | Indicates the feedback mode for MBS multicast dynamically scheduled PDSCH or SPS PDSCH. | +| mbs-RNTI-SpecificConfigId | An identifier of the RNTI specific configuration for MBS multicast. | +| pdsch-AggregationFactor | Number of repetitions for dynamically scheduled MBS multicast data (see TS 38.214 [19], clause 5.1.2.1). When the field is absent and groupCommon-RNTI is set to g-RNTI , the UE applies the value 1. | + +| LCG-DSR-Config field descriptions | | +|------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| lcg-Id | Identifier of the Logical Channel Group which the DSR configuration refers to. | +| remainingTimeThreshold | Remaining time threshold used for triggering DSR for the Logical Channel Group, as specified in TS 38.321 [3]. Value in number of miliseconds. | + +| Conditional Presence | Explanation | +|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| G-RNTI | This field is optionally present, Need S, if groupCommon-RNTI is set to g-RNTI . The field is absent when groupCommon-RNTI is set to g-CS-RNTI . | +| HARQFeedback | The field is mandatory present when harq-FeedbackEnablerMulticast is present. It is absent otherwise. | +| MCG-Only | This field is optionally present, Need M, for the MAC-CellGroupConfig of the MCG. It is absent otherwise. | +| LCH-PrioWithReTxTimer | This field is optionally present, Need R, if Ich-BasedPrioritization-r16 is configured in this MAC entity and cg-RetransmissionTimer-r16 is configured for any configured grant configuration associated with this MAC entity. It is absent otherwise, Need R. | + +### MeasConfig + +The IE *MeasConfig* specifies measurements to be performed by the UE, and covers intra-frequency, inter-frequency and inter-RAT mobility as well as configuration of measurement gaps. + +#### MeasConfig information element + +``` +-- ASN1START +-- TAG-MEASCONFIG-START + +MeasConfig ::= + SEQUENCE { + measObjectToRemoveList MeasObjectToRemoveList OPTIONAL, -- Need N + measObjectToAddModList MeasObjectToAddModList OPTIONAL, -- Need N + reportConfigToRemoveList ReportConfigToRemoveList OPTIONAL, -- Need N + reportConfigToAddModList ReportConfigToAddModList OPTIONAL, -- Need N + measIdToRemoveList MeasIdToRemoveList OPTIONAL, -- Need N + measIdToAddModList MeasIdToAddModList OPTIONAL, -- Need N + s-MeasureConfig CHOICE { + ssb-RSRP RSRP-Range, + csi-RSRP RSRP-Range + } + quantityConfig QuantityConfig OPTIONAL, -- Need M + measGapConfig MeasGapConfig OPTIONAL, -- Need M + measGapSharingConfig MeasGapSharingConfig OPTIONAL, -- Need M + ... + [[ + interFrequencyConfig-NoGap-r16 ENUMERATED {true} OPTIONAL -- Need R + ]], + [[ +``` + +``` + + effectiveMeasWindowConfig-r18 SetupRelease {MeasWindowConfig-r18} OPTIONAL -- Need M + ]] +} + +MeasObjectToRemoveList := SEQUENCE (SIZE (1..maxNrofObjectId)) OF MeasObjectId +MeasIdToRemoveList := SEQUENCE (SIZE (1..maxNrofMeasId)) OF MeasId +ReportConfigToRemoveList := SEQUENCE (SIZE (1..maxReportConfigId)) OF ReportConfigId + +-- TAG-MEASCONFIG-STOP +-- ASN1STOP + +``` + +| MeasConfig field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| effectiveMeasWindowConfig
Used to setup and release effective measurement window in NR for E-UTRA measurements. | +| interFrequencyConfig-NoGap-r16
If the field is set to true, UE is configured to perform SSB based inter-frequency measurement without measurement gaps when the inter-frequency SSB is completely contained in the active DL BWP of the UE, as specified in TS 38.133 [14], clause 9.3. Otherwise, the SSB based inter-frequency measurement is performed within measurement gaps. In NR-DC, the field can only be configured in the measConfig associated with MCG, and when configured, it applies to all the inter-frequency measurements configured by MN and SN. | +| measGapConfig
Used to setup and release measurement gaps in NR. | +| measIdToAddModList
List of measurement identities to add and/or modify. | +| measIdToRemoveList
List of measurement identities to remove. | +| measObjectToAddModList
List of measurement objects to add and/or modify. | +| measObjectToRemoveList
List of measurement objects to remove. | +| reportConfigToAddModList
List of measurement reporting configurations to add and/or modify. | +| reportConfigToRemoveList
List of measurement reporting configurations to remove. | +| s-MeasureConfig
Threshold for NR SpCell RSRP measurement controlling when the UE is required to perform measurements on non-serving cells. Choice of ssb-RSRP corresponds to cell RSRP based on SS/PBCH block and choice of csi-RSRP corresponds to cell RSRP of CSI-RS. | +| measGapSharingConfig
Specifies the measurement gap sharing scheme and controls setup/ release of measurement gap sharing. | + +### MeasGapConfig + +The IE *MeasGapConfig* specifies the measurement gap configuration and controls setup/release of measurement gaps. + +#### MeasGapConfig information element + +``` + +-- ASN1START +-- TAG-MEASGAPCONFIG-START + +MeasGapConfig ::= + SEQUENCE { + gapFR2 SetupRelease { GapConfig } OPTIONAL, -- Need M + ... + [[ + gapFR1 SetupRelease { GapConfig } OPTIONAL, -- Need M + gapUE SetupRelease { GapConfig } OPTIONAL, -- Need M + ]], + [[ + gapToAddModList-r17 SEQUENCE (SIZE (1..maxNrofGapId-r17)) OF GapConfig-r17 OPTIONAL, -- Need N + gapToReleaseList-r17 SEQUENCE (SIZE (1..maxNrofGapId-r17)) OF MeasGapId-r17 OPTIONAL, -- Need N + posMeasGapPreConfigToAddModList-r17 PosMeasGapPreConfigToAddModList-r17 OPTIONAL, -- Need N + posMeasGapPreConfigToReleaseList-r17 PosMeasGapPreConfigToReleaseList-r17 OPTIONAL, -- Need N + ]] + } + +GapConfig ::= + SEQUENCE { + gapOffset INTEGER (0..159), + mgl ENUMERATED {ms1dot5, ms3, ms3dot5, ms4, ms5dot5, ms6}, + mgrp ENUMERATED {ms20, ms40, ms80, ms160}, + mgta ENUMERATED {ms0, ms0dot25, ms0dot5}, + ... + [[ + refServCellIndicator ENUMERATED {pCell, pSCell, mcg-FR2} OPTIONAL -- Cond NEDCorNRDC + ]], + [[ + refFR2ServCellAsyncCA-r16 ServCellIndex OPTIONAL, -- Cond AsyncCA + mgl-r16 ENUMERATED {ms10, ms20} OPTIONAL, -- Cond PRS + ]] + } + +GapConfig-r17 ::= + SEQUENCE { + measGapId-r17 MeasGapId-r17, + gapType-r17 ENUMERATED {perUE, perFR1, perFR2}, + gapOffset-r17 INTEGER (0..159), + mgl-r17 ENUMERATED {ms1, ms1dot5, ms2, ms3, ms3dot5, ms4, ms5, ms5dot5, ms6, ms10, ms20}, + mgrp-r17 ENUMERATED {ms20, ms40, ms80, ms160}, + mgta-r17 ENUMERATED {ms0, ms0dot25, ms0dot5, ms0dot75}, + refServCellIndicator-r17 ENUMERATED {pCell, pSCell, mcg-FR2} OPTIONAL, -- Cond NEDCorNRDC + refFR2-ServCellAsyncCA-r17 ServCellIndex OPTIONAL, -- Cond AsyncCA + preConfigInd-r17 ENUMERATED {true} OPTIONAL, -- Need R + } + +``` + +``` + ncsInd-r17 ENUMERATED {true} OPTIONAL, -- Need R + gapAssociationPRS-r17 ENUMERATED {true} OPTIONAL, -- Need R + gapSharing-r17 MeasGapSharingScheme OPTIONAL, -- Need R + gapPriority-r17 GapPriority-r17 OPTIONAL, -- Need R + ... +} + +PosMeasGapPreConfigToAddModList-r17 ::= SEQUENCE (SIZE (1..maxNrofPreConfigPosGapId-r17)) OF PosGapConfig-r17 + +PosMeasGapPreConfigToReleaseList-r17 ::= SEQUENCE (SIZE (1..maxNrofPreConfigPosGapId-r17)) OF MeasPosPreConfigGapId-r17 + +PosGapConfig-r17 ::= SEQUENCE { + measPosPreConfigGapId-r17 MeasPosPreConfigGapId-r17, + gapOffset-r17 INTEGER (0..159), + mgl-r17 ENUMERATED {ms1dot5, ms3, ms3dot5, ms4, ms5dot5, ms6, ms10, ms20}, + mgrp-r17 ENUMERATED {ms20, ms40, ms80, ms160}, + mgta-r17 ENUMERATED {ms0, ms0dot25, ms0dot5}, + gapType-r17 ENUMERATED {perUE, perFR1, perFR2}, + ... +} + +MeasPosPreConfigGapId-r17 ::= INTEGER (1..maxNrofPreConfigPosGapId-r17) + +-- TAG-MEASGAPCONFIG-STOP +-- ASN1STOP +``` + +| MeasGapConfig field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| gapAssociationPRS
Indicates that PRS measurement is associated with this measurement gap. The network only includes this field for one per-UE gap or for one per-FR gap. If concurrent gap (i.e. one of the gap combination as defined in Table 9.1.8-1 in TS 38.133 [14]) is configured and no gap is configured with this field, the PRS measurement is associated with the gap configured via GapConfig (without suffix), if available. If both per-UE gap and per-FR gap are configured via GapConfig and/or GapConfig-r17 , the PRS measurement is always associated with the per-UE gap. | +| gapFR1
Indicates measurement gap configuration that applies to FR1 only. In (NG)EN-DC, gapFR1 cannot be set up by NR RRC (i.e. only LTE RRC can configure FR1 measurement gap). In NE-DC, gapFR1 can only be set up by NR RRC (i.e. LTE RRC cannot configure FR1 gap). In NR-DC, gapFR1 can only be set up in the measConfig associated with MCG. gapFR1 can not be configured together with gapUE . The applicability of the FR1 measurement gap is according to Table 9.1.2-2 and Table 9.1.2-3 in TS 38.133 [14]. | +| gapFR2
Indicates measurement gap configuration applies to FR2 only. In (NG)EN-DC or NE-DC, gapFR2 can only be set up by NR RRC (i.e. LTE RRC cannot configure FR2 gap). In NR-DC, gapFR2 can only be set up in the measConfig associated with MCG. gapFR2 cannot be configured together with gapUE . The applicability of the FR2 measurement gap is according to Table 9.1.2-2 and Table 9.1.2-3 in TS 38.133 [14]. | +| gapOffset
Value gapOffset is the gap offset of the gap pattern with MGRP indicated in the field mgrp . The value range is from 0 to mgrp -1. If ncsgInd-r17 is present, this offset value refers to the starting point of VIL1 (the visible interruption length before the ML). | +| gapPriority
Indicates the priority of this measurement gap (see TS 38.133 [14], clause 9.1.8.3). Value 1 indicates highest priority, value 2 indicates second level priority, and so on. | +| gapSharing
Indicates the measurement gap sharing scheme that applies to this GapConfig . For applicability of the different gap sharing schemes, see TS 38.133 [14]. Value scheme00 corresponds to scheme "00", value scheme01 corresponds to scheme "01", and so on. | +| gapToAddModList
A list of measurement gap configuration to be added or modified. If more than one measurement gap is configured (i.e. concurrent measurement gap as specified in TS 38.133[14], clause 9.1.8), the maximum number of configured measurement gap is limited by the gap combinations defined in Table 9.1.8-1 in TS 38.133 [14]. The network configures at most one NCSG or pre-configured measurement gap for a given gap type. In this version of the specification, the network configures this field only in NR standalone. This field is used only for a UE that supports pre-configured measurement gap, concurrent measurement gap, or NCSG. In this version of the specification, the network does not configure concurrent measurement gap together with MUSIM gap or preconfigured measurement gap for positioning. | +| gapToReleaseList
A list of measurement gap configuration to be released. | +| gapType
Indicates the type of this measurement gap. Value perUE indicates that it is a per UE measurement gap, value perFR1 indicates that it is an FR1 measurement gap, and value perFR2 indicates that it is an FR2 measurement gap. | +| gapUE
Indicates measurement gap configuration that applies to all frequencies (FR1 and FR2). In (NG)EN-DC, gapUE cannot be set up by NR RRC (i.e. only LTE RRC can configure per UE measurement gap). In NE-DC, gapUE can only be set up by NR RRC (i.e. LTE RRC cannot configure per UE gap). In NR-DC, gapUE can only be set up in the measConfig associated with MCG. If gapUE is configured, then neither gapFR1 nor gapFR2 can be configured. The applicability of the per UE measurement gap is according to Table 9.1.2-2 and Table 9.1.2-3 in TS 38.133 [14]. | +| measGapId
The ID of this measurement gap configuration. | + +| | | +|------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| mgl | Value mgl is the measurement gap length in ms of the measurement gap. If ncsgInd-r17 is not present, the measurement gap length is according to in Table 9.1.2-1 in TS 38.133 [14]. If ncsgInd-r17 is present, this field indicates the measurement length (ML) in NCSG pattern and is configured according to Table 9.1.9.3-1 in TS 38.133 [14]. Value ms1dot5 corresponds to 1.5 ms, ms3 corresponds to 3 ms and so on. If mgl-r16 is present, UE shall ignore the mgl (without suffix). Value ms1 , ms2 , and ms5 can only be configured if ncsgInd is present. | +| mgrp | If ncsgInd-r17 is not present, the mgrp field indicates the measurement gap repetition period in (ms) of the measurement gap according to Table 9.1.2-1 in TS 38.133 [14]. If ncsgInd-r17 is present, the mgrp field indicates the Visible Interruption Repetition Period (VIRP) of NCSG pattern and is configured according to Table 9.1.9.3-1 in TS 38.133 [14]. | +| mgta | Value mgta is the measurement gap timing advance in ms. The applicability of the measurement gap timing advance is according to clause 9.1.2 of TS 38.133 [14], or according to clause 9.1.9 of TS 38.133 [14] if ncsgInd is present. Value ms0 corresponds to 0 ms, ms0dot25 corresponds to 0.25 ms, ms0dot5 corresponds to 0.5 ms and ms0dot75 corresponds to 0.75 ms. For FR2, the network only configures 0 ms and 0.25 ms if ncsgInd is not present. If ncsgInd is present, the network only configures 0ms for per-UE NCSG and FR1 NCSG and only configures 0ms or 0.75ms for FR2 NCSG. Value ms0dot75 can only be configured if ncsgInd is present. | +| ncsgInd | Indicates that the measurement gap is a NCSG as specified in 38.133 [14]. | +| posMeasGapPreConfigToAddModList | List of preconfigured measurement gap for positioning to add and/or modify. All the gaps configured are associated with the measurement of PRS for RSTD, UE-RxTx Time Difference, PRS-RSRP and PRS-RSRPP as defined in TS 38.215 [9]. In this version of the specification, the network does not configure preconfigured measurement gap for positioning together with concurrent measurement gap or MUSIM gap. | +| posMeasGapPreConfigToReleaseList | List of preconfigured measurement gap for positioning to release. | +| preConfigInd | Indicates whether the measurement gap is a pre-configured measurement gap. | +| refFR2ServCellAsyncCA | Indicates the FR2 serving cell identifier whose SFN and subframe is used for FR2 gap calculation for this gap pattern with asynchronous CA involving FR2 carrier(s). | +| refServCellIndicator | Indicates the serving cell whose SFN and subframe are used for gap calculation for this gap pattern. Value pCell corresponds to the PCell, pSCell corresponds to the PSCell, and mcg-FR2 corresponds to a serving cell on FR2 frequency in MCG. | + +| Conditional Presence | Explanation | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AsyncCA | This field is mandatory present when configuring and reconfiguring FR2 gap pattern to UE in:
- (NG)EN-DC or NR SA with asynchronous CA involving FR2 carrier(s);
- NE-DC or NR-DC with asynchronous CA involving FR2 carrier(s), if the field refServCellIndicator is set to mcg-FR2 .
Otherwise, it is absent, Need R. | +| NEDCorNRDC | This field is mandatory present when configuring and reconfiguring gap pattern to UE in NE-DC or NR-DC. Otherwise, it is absent, Need R. | +| PRS | This field is optionally present, Need R, when configuring gap pattern to UE for measurements of DL-PRS configured via LPP (TS 37.355 [49]). Otherwise, it is absent. | + +#### — *MeasGapId* + +The IE *MeasGapId* used to identify a per UE or per FR measurement gap configuration. + +#### *MeasGapId* information element + +``` +-- ASN1START +-- TAG-MEASGAPID-START + +MeasGapId-r17 ::= INTEGER (1..maxNrofGapId-r17) + +-- TAG-MEASGAPID-STOP +-- ASN1STOP +``` + +#### — *MeasGapSharingConfig* + +The IE *MeasGapSharingConfig* specifies the measurement gap sharing scheme and controls setup/ release of measurement gap sharing. + +#### *MeasGapSharingConfig* information element + +``` +-- ASN1START +-- TAG-MEASGAPSHARINGCONFIG-START + +MeasGapSharingConfig ::= SEQUENCE { + gapSharingFR2 SetupRelease { MeasGapSharingScheme } OPTIONAL, -- Need M + ... + [[ + gapSharingFR1 SetupRelease { MeasGapSharingScheme } OPTIONAL, --Need M + gapSharingUE SetupRelease { MeasGapSharingScheme } OPTIONAL --Need M + ]] +} + +MeasGapSharingScheme ::= ENUMERATED {scheme00, scheme01, scheme10, scheme11} + +-- TAG-MEASGAPSHARINGCONFIG-STOP +-- ASN1STOP +``` + +| MeasGapSharingConfig field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| gapSharingFR1
Indicates the measurement gap sharing scheme that applies to the gap set via gapFR1 . In (NG)EN-DC, gapSharingFR1 cannot be set up by NR RRC (i.e. only LTE RRC can configure FR1 gap sharing). In NE-DC, gapSharingFR1 can only be set up by NR RRC (i.e. LTE RRC cannot configure FR1 gap sharing). In NR-DC, gapSharingFR1 can only be set up in the measConfig associated with MCG. gapSharingFR1 can not be configured together with gapSharingUE . For the applicability of the different gap sharing schemes, see TS 38.133 [14]. Value scheme00 corresponds to scheme "00", value scheme01 corresponds to scheme "01", and so on. | +| gapSharingFR2
Indicates the measurement gap sharing scheme that applies to the gap set via gapFR2 . In (NG)EN-DC or NE-DC, gapSharingFR2 can only be set up by NR RRC (i.e. LTE RRC cannot configure FR2 gap sharing). In NR-DC, gapSharingFR2 can only be set up by MCG in the measConfig associated with MCG. gapSharingFR2 cannot be configured together with gapSharingUE . For applicability of the different gap sharing schemes, see TS 38.133 [14]. Value scheme00 corresponds to scheme "00", value scheme01 corresponds to scheme "01", and so on. | +| gapSharingUE
Indicates the measurement gap sharing scheme that applies to the gap set via gapUE . In (NG)EN-DC, gapSharingUE cannot be set up by NR RRC (i.e. only LTE RRC can configure per UE gap sharing). In NE-DC, gapSharingUE can only be set up by NR RRC (i.e. LTE RRC cannot configure per UE gap sharing). In NR-DC, gapSharingUE can only be set up in the measConfig associated with MCG. If gapSharingUE is configured, then neither gapSharingFR1 nor gapSharingFR2 can be configured. For the applicability of the different gap sharing schemes, see TS 38.133 [14]. Value scheme00 corresponds to scheme "00", value scheme01 corresponds to scheme "01", and so on. | + +#### — *MeasId* + +The IE *MeasId* is used to identify a measurement configuration, i.e., linking of a measurement object and a reporting configuration. + +#### ***MeasId* information element** + +``` +-- ASN1START +-- TAG-MEASID-START + +MeasId ::= INTEGER (1..maxNrofMeasId) + +-- TAG-MEASID-STOP +-- ASN1STOP +``` + +#### — *MeasIdleConfig* + +The IE *MeasIdleConfig* is used to convey information to UE about measurements requested to be done while in RRC\_IDLE or RRC\_INACTIVE. + +#### ***MeasIdleConfig* information element** + +``` +-- ASN1START +-- TAG-MEASIDLECONFIG-START + +MeasIdleConfigSIB-r16 ::= SEQUENCE { + measIdleCarrierListNR-r16 SEQUENCE (SIZE (1..maxFreqIdle-r16)) OF MeasIdleCarrierNR-r16 OPTIONAL, -- Need S + measIdleCarrierListEUTRA-r16 SEQUENCE (SIZE (1..maxFreqIdle-r16)) OF MeasIdleCarrierEUTRA-r16 OPTIONAL, -- Need S + ... +} +``` + +``` + +} + +MeasIdleConfigDedicated-r16 ::= SEQUENCE { + measIdleCarrierListNR-r16 SEQUENCE (SIZE (1..maxFreqIdle-r16)) OF MeasIdleCarrierNR-r16 OPTIONAL, -- Need N + measIdleCarrierListEUTRA-r16 SEQUENCE (SIZE (1..maxFreqIdle-r16)) OF MeasIdleCarrierEUTRA-r16 OPTIONAL, -- Need N + measIdleDuration-r16 ENUMERATED{sec10, sec30, sec60, sec120, sec180, sec240, sec300, spare}, + validityAreaList-r16 ValidityAreaList-r16 OPTIONAL, -- Need N + ... +} + +ValidityAreaList-r16 ::= SEQUENCE (SIZE (1..maxFreqIdle-r16)) OF ValidityArea-r16 + +ValidityArea-r16 ::= SEQUENCE { + carrierFreq-r16 ARFCN-ValueNR, + validityCellList-r16 ValidityCellList OPTIONAL -- Need N +} + +ValidityCellList ::= SEQUENCE (SIZE (1.. maxCellMeasIdle-r16)) OF PCI-Range + +MeasIdleCarrierNR-r16 ::= SEQUENCE { + carrierFreq-r16 ARFCN-ValueNR, + ssbSubcarrierSpacing-r16 SubcarrierSpacing, + frequencyBandList MultiFrequencyBandListNR OPTIONAL, -- Need R + measCellListNR-r16 CellListNR-r16 OPTIONAL, -- Need R + reportQuantities-r16 ENUMERATED {rsrp, rsrq, both}, + qualityThreshold-r16 SEQUENCE { + idleRSRP-Threshold-NR-r16 RSRP-Range OPTIONAL, -- Need R + idleRSRQ-Threshold-NR-r16 RSRQ-Range OPTIONAL -- Need R + } OPTIONAL, -- Need R + ssb-MeasConfig-r16 SEQUENCE { + nrofSS-BlocksToAverage-r16 INTEGER (2..maxNrofSS-BlocksToAverage) OPTIONAL, -- Need S + absThreshSS-BlocksConsolidation-r16 ThresholdNR OPTIONAL, -- Need S + smtc-r16 SSB-MTC OPTIONAL, -- Need S + ssb-ToMeasure-r16 SSB-ToMeasure OPTIONAL, -- Need S + deriveSSB-IndexFromCell-r16 BOOLEAN, + ss-RSSI-Measurement-r16 SS-RSSI-Measurement OPTIONAL -- Need S + } OPTIONAL, -- Need S + beamMeasConfigIdle-r16 BeamMeasConfigIdle-NR-r16 OPTIONAL, -- Need R + ... +} + +MeasIdleCarrierEUTRA-r16 ::= SEQUENCE { + carrierFreqEUTRA-r16 ARFCN-ValueEUTRA, + allowedMeasBandwidth-r16 EUTRA-AllowedMeasBandwidth, + measCellListEUTRA-r16 CellListEUTRA-r16 OPTIONAL, -- Need R + reportQuantitiesEUTRA-r16 ENUMERATED {rsrp, rsrq, both}, + qualityThresholdEUTRA-r16 SEQUENCE { + idleRSRP-Threshold-EUTRA-r16 RSRP-RangeEUTRA OPTIONAL, -- Need R + idleRSRQ-Threshold-EUTRA-r16 RSRQ-RangeEUTRA OPTIONAL -- Need R + } OPTIONAL, -- Need S + ... +} + +``` + +``` +} + +CellListNR-r16 := SEQUENCE (SIZE (1..maxCellMeasIdle-r16)) OF PCI-Range +CellListEUTRA-r16 := SEQUENCE (SIZE (1..maxCellMeasIdle-r16)) OF EUTRA-PhysCellIdRange + +BeamMeasConfigIdle-NR-r16 := SEQUENCE { + reportQuantityRS-Indexes-r16 ENUMERATED {rsrp, rsrq, both}, + maxNrofRS-IndexesToReport-r16 INTEGER (1.. maxNrofIndexesToReport), + includeBeamMeasurements-r16 BOOLEAN +} + +RSRQ-RangeEUTRA-r16 := INTEGER (-30..46) + +-- TAG-MEASIDLECONFIG-STOP +-- ASN1STOP +``` + +| MeasIdleConfig field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| absThreshSS-BlocksConsolidation
Threshold for consolidation of L1 measurements per RS index. | +| beamMeasConfigIdle
Indicates the beam level measurement configuration. | +| carrierFreq
Indicates the NR carrier frequency to be used for measurements during RRC_IDLE or RRC_INACTIVE. | +| carrierFreqEUTRA
Indicates the E-UTRA carrier frequency to be used for measurements during RRC_IDLE or RRC_INACTIVE. | +| deriveSSB-IndexFromCell
This field indicates whether the UE may use the timing of any detected cell on that frequency to derive the SSB index of all neighbour cells on that frequency. If this field is set to true, the UE assumes SFN and frame boundary alignment across cells on the neighbor frequency as specified in TS 38.133 [14]. | +| frequencyBandList
Indicates the list of frequency bands for which the NR idle/inactive measurement parameters apply. The UE shall select the first listed band which it supports in the frequencyBandList field to represent the NR neighbour carrier frequency. | +| includeBeamMeasurements
Indicates whether or not the UE shall include beam measurements in the NR idle/inactive measurement results. | +| maxNrofRS-IndexesToReport
Max number of beam indices to include in the idle/inactive measurement result. | +| measCellListEUTRA
Indicates the list of E-UTRA cells which the UE is requested to measure and report for idle/inactive measurements. | +| measCellListNR
Indicates the list of NR cells which the UE is requested to measure and report for idle/inactive measurements. | +| measIdleCarrierListEUTRA
Indicates the E-UTRA carriers to be measured during RRC_IDLE or RRC_INACTIVE. | +| measIdleCarrierListNR
Indicates the NR carriers to be measured during RRC_IDLE or RRC_INACTIVE. | +| measIdleDuration
Indicates the duration for performing idle/inactive measurements while in RRC_IDLE or RRC_INACTIVE. Value sec10 correspond to 10 seconds, value sec30 to 30 seconds and so on. | +| nrofSS-BlocksToAverage
Number of SS blocks to average for cell measurement derivation. | +| qualityThreshold
Indicates the quality thresholds for reporting the measured cells for idle/inactive NR measurements. | +| qualityThresholdEUTRA
Indicates the quality thresholds for reporting the measured cells for idle/inactive E-UTRA measurements. | +| reportQuantities
Indicates which measurement quantities UE is requested to report in the idle/inactive measurement report. | +| reportQuantitiesEUTRA
Indicates which E-UTRA measurement quantities the UE is requested to report in the idle/inactive measurement report. | +| reportQuantityRS-Indexes
Indicates which measurement information per beam index the UE shall include in the NR idle/inactive measurement results. | +| smtc | + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Indicates the measurement timing configuration for inter-frequency measurement. If this field is absent in VarMeasIdleConfig , the UE assumes that SSB periodicity is 5 ms in this frequency. | +| ssbSubcarrierSpacing
Indicates subcarrier spacing of SSB.
Only the following values are applicable depending on the used frequency:
FR1: 15 or 30 kHz
FR2-1: 120 or 240 kHz
FR2-2: 120, 480, or 960 kHz | +| ssb-ToMeasure
The set of SS blocks to be measured within the SMTC measurement duration (see TS 38.215 [9]). When the field is absent in VarMeasIdleConfig , the UE measures on all SS-blocks. | +| ss-RSSI-Measurement
Indicates the SSB-based RSSI measurement configuration. If the field is absent in VarMeasIdleConfig , the UE behaviour is defined in TS 38.215 [89], clause 5.1.3. | +| validityAreaList
Indicates the list of frequencies and optionally, for each frequency, a list of cells within which the UE is required to perform measurements while in RRC_IDLE and RRC_INACTIVE. | + +#### – *MeasIdToAddModList* + +The IE *MeasIdToAddModList* concerns a list of measurement identities to add or modify, with for each entry the *measId*, the associated *measObjectId* and the associated *reportConfigId*. + +#### *MeasIdToAddModList* information element + +``` +-- ASN1START +-- TAG-MEASIDTOADDMODLIST-START + +MeasIdToAddModList ::= SEQUENCE (SIZE (1..maxNrofMeasId)) OF MeasIdToAddMod + +MeasIdToAddMod ::= SEQUENCE { + measId MeasId, + measObjectId MeasObjectId, + reportConfigId ReportConfigId +} + +-- TAG-MEASIDTOADDMODLIST-STOP +-- ASN1STOP +``` + +#### – *MeasObjectCLI* + +The IE *MeasObjectCLI* specifies information applicable for SRS-RSRP measurements and/or CLI-RSSI measurements. + +#### *MeasObjectCLI* information element + +``` + +-- ASN1START +-- TAG-MEASOBJECTCLI-START + +MeasObjectCLI-r16 ::= + cli-ResourceConfig-r16 + ... +} + +CLI-ResourceConfig-r16 ::= + srs-ResourceConfig-r16 + rssi-ResourceConfig-r16 +} + +SRS-ResourceListConfigCLI-r16 ::= + RSSI-ResourceListConfigCLI-r16 + +RSSI-ResourceListConfigCLI-r16 ::= + SRS-ResourceConfigCLI-r16 + +RSSI-ResourceConfigCLI-r16 ::= + rssi-ResourceId-r16 + rssi-SCS-r16 + startPRB-r16 + nrofPRBs-r16 + startPosition-r16 + nrofSymbols-r16 + rssi-PeriodicityAndOffset-r16 + refServCellIndex-r16 + ... +} + +RSSI-ResourceId-r16 ::= + INTEGER (0.. maxNrofCLI-RSSI-Resources-1-r16) + +RSSI-PeriodicityAndOffset-r16 ::= + sl10 + sl20 + sl40 + sl80 + sl160 + sl320 + sl640 + ... +} + +``` + +``` +-- TAG-MEASOBJECTCLI-STOP +-- ASN1STOP +``` + +| CLI-ResourceConfig field descriptions | +|------------------------------------------------------------------------------------------| +| srs-ResourceConfig
SRS resources to be used for CLI measurements. | +| rssi-ResourceConfig
CLI-RSSI resources to be used for CLI measurements. | + +| MeasObjectCLI field descriptions | +|-----------------------------------------------------------------------------------------------------| +| cli-ResourceConfig
SRS and/or CLI-RSSI resource configuration for CLI measurement. | + +| SRS-ResourceConfigCLI field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| refBWP
DL BWP id that is used to derive the reference point of the SRS resource (see TS 38.211[16], clause 6.4.1.4.3) | +| refServCellIndex
The index of the reference serving cell that the refBWP belongs to. If this field is absent, the reference serving cell is PCell. | +| srs-SCS
Subcarrier spacing for SRS.
Only the following values are applicable depending on the used frequency:
FR1: 15, 30, or 60 kHz
FR2-1: 60 or 120 kHz
FR2-2: 120, 480, or 960 kHz | + +| RSSI-ResourceConfigCLI field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| nrofPRBs
Allowed size of the measurement BW. Only multiples of 4 are allowed. The smallest configurable number is the minimum of 4 and the width of the active DL BWP. If the configured value is larger than the width of the active DL BWP, the UE shall assume that the actual CLI-RSSI resource bandwidth is within the active DL BWP. | +| nrofSymbols
Within a slot that is configured for CLI-RSSI measurement (see slotConfiguration), the UE measures the RSSI from startPosition to startPosition + nrofSymbols - 1. The configured CLI-RSSI resource does not exceed the slot boundary of the reference SCS. If the SCS of configured DL BWP(s) is larger than the reference SCS, network configures startPosition and nrofSymbols such that the configured CLI-RSSI resource not to exceed the slot boundary corresponding to the configured BWP SCS. If the reference SCS is larger than SCS of configured DL BWP(s), network ensures startPosition and nrofSymbols are integer multiple of reference SCS divided by configured BWP SCS. | +| refServCellIndex
The index of the reference serving cell. Frequency reference point of the RSSI resource is subcarrier 0 of CRB0 of the reference serving cell. If this field is absent, the reference serving cell is PCell. | +| rssi-PeriodicityAndOffset
Periodicity and slot offset for this CLI-RSSI resource. All values are in "number of slots". Value s1 corresponds to a periodicity of 1 slot, value s2 corresponds to a periodicity of 2 slots, and so on. For each periodicity the corresponding offset is given in number of slots. | +| rssi-SCS
Reference subcarrier spacing for CLI-RSSI measurement.
Only the following values are applicable depending on the used frequency:
FR1: 15, 30, or 60 kHz
FR2-1: 60 or 120 kHz
FR2-2: 120, 480, or 960 kHz
UE performs CLI-RSSI measurement with the SCS of the active bandwidth part within the configured CLI-RSSI resource in the active BWP regardless of the reference SCS of the measurement resource. | +| startPosition
OFDM symbol location of the CLI-RSSI resource within a slot. | +| startPRB
Starting PRB index of the measurement bandwidth. For the case where the reference subcarrier spacing is smaller than subcarrier spacing of active DL BWP(s), network configures startPRB and nrofPRBs are as a multiple of active BW SCS divided by reference SCS. | + +#### – *MeasObjectEUTRA* + +The IE *MeasObjectEUTRA* specifies information applicable for E-UTRA cells. + +### ***MeasObjectEUTRA* information element** + +``` +-- ASN1START +-- TAG-MEASOBJECTEUTRA-START + +MeasObjectEUTRA ::= + SEQUENCE { + carrierFreq ARFCN-ValueEUTRA, + allowedMeasBandwidth EUTRA-AllowedMeasBandwidth, + cellsToRemoveListEUTRAN EUTRA-CellIndexList OPTIONAL, -- Need N + cellsToAddModListEUTRAN SEQUENCE (SIZE (1..maxCellMeasEUTRA)) OF EUTRA-Cell OPTIONAL, -- Need N + } + +``` + +``` + + excludedCellsToRemoveListEUTRAN EUTRA-CellIndexList OPTIONAL, -- Need N + excludedCellsToAddModListEUTRAN SEQUENCE (SIZE (1..maxCellMeasEUTRA)) OF EUTRA-ExcludedCell OPTIONAL, -- Need N + eutra-PresenceAntennaPort1 EUTRA-PresenceAntennaPort1, + eutra-Q-OffsetRange EUTRA-Q-OffsetRange OPTIONAL, -- Need R + widebandRSRQ-Meas BOOLEAN, + ... + [[ + associatedMeasGap-r17 MeasGapId-r17 OPTIONAL -- Need R + ]], + [[ + measSequence-r18 MeasSequence-r18 OPTIONAL -- Need R + ]] + } + + EUTRA-CellIndexList := SEQUENCE (SIZE (1..maxCellMeasEUTRA)) OF EUTRA-CellIndex + + EUTRA-CellIndex := INTEGER (1..maxCellMeasEUTRA) + + EUTRA-Cell := SEQUENCE { + cellIndexEUTRA EUTRA-CellIndex, + physCellId EUTRA-PhysCellId, + cellIndividualOffset EUTRA-Q-OffsetRange + } + + EUTRA-ExcludedCell := SEQUENCE { + cellIndexEUTRA EUTRA-CellIndex, + physCellIdRange EUTRA-PhysCellIdRange + } + + -- TAG-MEASOBJECTEUTRA-STOP + -- ASN1STOP + +``` + +### ***EUTRAN-ExcludedCell* field descriptions** + +| | +|----------------------------------------------------------------| +| cellIndexEUTRA | +| Entry index in the cell list. | +| physicalCellIdRange | +| Physical cell identity or a range of physical cell identities. | + +#### ***EUTRAN-Cell* field descriptions** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------| +| physicalCellId | +| Physical cell identity of a cell in the cell list. | +| cellIndividualOffset | +| Cell individual offset applicable to a specific cell. Value dB-24 corresponds to -24 dB, dB-22 corresponds to -22 dB and so on. | + +| MeasObjectEUTRA field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| allowedMeasBandwidth
The maximum allowed measurement bandwidth on a carrier frequency as defined by the parameter Transmission Bandwidth Configuration "N RB " TS 36.104 [33]. | +| associatedMeasGap
Indicates the associated measurement gap for measuring this EUTRA frequency. If this field is absent, the associated measurement gap is the gap configured via gapFR1 or gapUE . | +| carrierFreq
Identifies E-UTRA carrier frequency for which this configuration is valid. Network does not configure more than one MeasObjectEUTRA for the same physical frequency, regardless of the E-ARFCN used to indicate this. | +| cellsToAddModListEUTRAN
List of cells to add/ modify in the cell list. | +| cellsToRemoveListEUTRAN
List of cells to remove from the cell list. | +| eutra-PresenceAntennaPort1
When set to true , the UE may assume that at least two cell-specific antenna ports are used in all neighbouring cells. | +| eutra-Q-OffsetRange
Used to indicate a cell, or frequency specific offset to be applied when evaluating triggering conditions for measurement reporting. The value is in dB. Value dB-24 corresponds to -24 dB, value dB-22 corresponds to -22 dB and so on. | +| excludedCellsToAddModListEUTRAN
List of cells to add/ modify in the exclude-list of cells. | +| excludedCellsToRemoveListEUTRAN
List of cells to remove from the exclude-list of cells. | +| measSequence
Indicates the recommended sequence for intra/inter-RAT intra/inter-frequency measurement. Value 1 means the corresponding frequency is measured firstly. Value 2 means the corresponding frequency is measured secondly and so on. If more than one frequency is configured with the same value, it means no recommended sequence among these frequencies. If not configured, it means there is no recommended sequence for the corresponding frequency. This field is only configured for NR standalone or if the measObject is associated to the MCG. | +| widebandRSRQ-Meas
If set to true , the UE shall, when performing RSRQ measurements, use a wider bandwidth in accordance with TS 36.133 [40]. The network may set the field to true if the measurement bandwidth indicated by allowedMeasBandwidth is 50 resource blocks or larger; otherwise the network sets this field to false . | + +#### — MeasObjectId + +The IE *MeasObjectId* used to identify a measurement object configuration. + +#### **MeasObjectId information element** + +``` +-- ASN1START +-- TAG-MEASOBJECTID-START + +MeasObjectId ::= INTEGER (1..maxNrofObjectId) + +-- TAG-MEASOBJECTID-STOP +-- ASN1STOP +``` + +#### MeasObjectNR + +The IE *MeasObjectNR* specifies information applicable for SS/PBCH block(s) intra/inter-frequency measurements and/or CSI-RS intra/inter-frequency measurements. + +#### MeasObjectNR information element + +``` +-- ASN1START +-- TAG-MEASOBJECTNR-START + +MeasObjectNR ::= SEQUENCE { + ssbFrequency ARFCN-ValueNR OPTIONAL, -- Cond SSBorAssociatedSSB + ssbSubcarrierSpacing SubcarrierSpacing OPTIONAL, -- Cond SSBorAssociatedSSB + smtc1 SSB-MTC OPTIONAL, -- Cond SSBorAssociatedSSB + smtc2 SSB-MTC2 OPTIONAL, -- Cond IntraFreqConnected + refFreqCSI-RS ARFCN-ValueNR OPTIONAL, -- Cond CSI-RS + referenceSignalConfig ReferenceSignalConfig, + absThreshSS-BlocksConsolidation ThresholdNR OPTIONAL, -- Need R + absThreshCSI-RS-Consolidation ThresholdNR OPTIONAL, -- Need R + nrofSS-BlocksToAverage INTEGER (2..maxNrofSS-BlocksToAverage) OPTIONAL, -- Need R + nrofCSI-RS-ResourcesToAverage INTEGER (2..maxNrofCSI-RS-ResourcesToAverage) OPTIONAL, -- Need R + quantityConfigIndex INTEGER (1..maxNrofQuantityConfig), + offsetMO Q-OffsetRangeList, + cellsToRemoveList PCI-List OPTIONAL, -- Need N + cellsToAddModList CellsToAddModList OPTIONAL, -- Need N + excludedCellsToRemoveList PCI-RangeIndexList OPTIONAL, -- Need N + excludedCellsToAddModList SEQUENCE (SIZE (1..maxNrofPCI-Ranges)) OF PCI-RangeElement OPTIONAL, -- Need N + allowedCellsToRemoveList PCI-RangeIndexList OPTIONAL, -- Need N + allowedCellsToAddModList SEQUENCE (SIZE (1..maxNrofPCI-Ranges)) OF PCI-RangeElement OPTIONAL, -- Need N + ..., + [[ + freqBandIndicatorNR FreqBandIndicatorNR OPTIONAL, -- Need R + measCycleSCell ENUMERATED {sf160, sf256, sf320, sf512, sf640, sf1024, sf1280} OPTIONAL -- Need R + ]], + [[ + smtc3list-r16 SSB-MTC3List-r16 OPTIONAL, -- Need R + rmtc-Config-r16 SetupRelease {RMTC-Config-r16} OPTIONAL, -- Need M + t312-r16 SetupRelease { T312-r16 } OPTIONAL -- Need M + ]], + [[ + associatedMeasGapSSB-r17 MeasGapId-r17 OPTIONAL, -- Need R + associatedMeasGapCSI-RS-r17 MeasGapId-r17 OPTIONAL, -- Need R + smtc4list-r17 SSB-MTC4List-r17 OPTIONAL, -- Need R + measCyclePSCell-r17 ENUMERATED {ms160, ms256, ms320, ms512, ms640, ms1024, ms1280, spare1} + OPTIONAL, -- Cond SCG + cellsToAddModListExt-v1710 CellsToAddModListExt-v1710 OPTIONAL -- Need N + ]], + [[ + associatedMeasGapSSB2-v1720 MeasGapId-r17 OPTIONAL, -- Cond AssociatedGapSSB + ]]] +``` + +``` + +associatedMeasGapCSIRS2-v1720 MeasGapId-r17 OPTIONAL -- Cond AssociatedGapCSIRS +]], +[[ +measSequence-r18 MeasSequence-r18 OPTIONAL, -- Need R +cellsToAddModListExt-v1800 CellsToAddModListExt-v1800 OPTIONAL -- Cond ServingCell +]] +} + +SSB-MTC3List-r16 ::= SEQUENCE (SIZE(1..4)) OF SSB-MTC3-r16 +SSB-MTC4List-r17 ::= SEQUENCE (SIZE(1..3)) OF SSB-MTC4-r17 +T312-r16 ::= ENUMERATED { ms0, ms50, ms100, ms200, ms300, ms400, ms500, ms1000} + +ReferenceSignalConfig ::= SEQUENCE { + ssb-ConfigMobility SSB-ConfigMobility OPTIONAL, -- Need M + csi-rs-ResourceConfigMobility SetupRelease { CSI-RS-ResourceConfigMobility } OPTIONAL -- Need M +} + +SSB-ConfigMobility ::= SEQUENCE { + ssb-ToMeasure SetupRelease { SSB-ToMeasure } OPTIONAL, -- Need M + deriveSSB-IndexFromCell BOOLEAN, + ss-RSSI-Measurement SS-RSSI-Measurement OPTIONAL, -- Need M + ... + [[ + ssb-PositionQCL-Common-r16 SSB-PositionQCL-Relation-r16 OPTIONAL, -- Cond SharedSpectrum + ssb-PositionQCL-CellsToAddModList-r16 SSB-PositionQCL-CellsToAddModList-r16 OPTIONAL, -- Need N + ssb-PositionQCL-CellsToRemoveList-r16 PCI-List OPTIONAL, -- Need N + ]], + [[ + deriveSSB-IndexFromCellInter-r17 ServCellIndex OPTIONAL, -- Need R + ssb-PositionQCL-Common-r17 SSB-PositionQCL-Relation-r17 OPTIONAL, -- Cond SharedSpectrum2 + ssb-PositionQCL-Cells-r17 SetupRelease { SSB-PositionQCL-CellList-r17} OPTIONAL -- Need M + ]], + [[ + cca-CellsToAddModList-r17 PCI-List OPTIONAL, -- Need N + cca-CellsToRemoveList-r17 PCI-List OPTIONAL, -- Need N + ]], + [[ + ssb-ToMeasureAltitudeBasedList-r18 SetupRelease { SSB-ToMeasureAltitudeBasedList-r18 } OPTIONAL -- Need M + ]] +} + +Q-OffsetRangeList ::= SEQUENCE { + rsrpOffsetSSB Q-OffsetRange DEFAULT dB0, + rsrqOffsetSSB Q-OffsetRange DEFAULT dB0, + sinrOffsetSSB Q-OffsetRange DEFAULT dB0, + rsrpOffsetCSI-RS Q-OffsetRange DEFAULT dB0, + rsrqOffsetCSI-RS Q-OffsetRange DEFAULT dB0, + sinrOffsetCSI-RS Q-OffsetRange DEFAULT dB0 +} + +``` + +``` + +ThresholdNR ::= + thresholdRSRP + thresholdRSRQ + thresholdSINR +} + +CellsToAddModList ::= + SEQUENCE { + RSRP-Range + RSRQ-Range + SINR-Range + } + +CellsToAddModListExt-v1710 ::= + SEQUENCE (SIZE (1..maxNrofCellMeas)) OF CellsToAddMod + +CellsToAddModListExt-v1800 ::= + SEQUENCE (SIZE (1..maxNrofCellMeas)) OF CellsToAddModExt-v1800 + +CellsToAddMod ::= + SEQUENCE { + physCellId + cellIndividualOffset + } + +CellsToAddModExt-v1710 ::= + SEQUENCE { + ntn-PolarizationDL-r17 + ntn-PolarizationUL-r17 + } + +CellsToAddModExt-v1800 ::= + SEQUENCE { + ntn-NeighbourCellInfo-r18 + } + +RMTC-Config-r16 ::= + SEQUENCE { + rmtc-Periodicity-r16 + rmtc-SubframeOffset-r16 + measDurationSymbols-r16 + rmtc-Frequency-r16 + ref-SCS-CP-r16 + ..., + [[ + rmtc-Bandwidth-r17 + measDurationSymbols-v1700 + ref-SCS-CP-v1700 + tci-StateInfo-r17 + tci-StateId-r17 + ref-ServCellId-r17 + } OPTIONAL -- Need R + ], + [[ + ref-BWPId-r17 + ] + ] +} + +SSB-PositionQCL-CellsToAddModList-r16 ::= SEQUENCE (SIZE (1..maxNrofCellMeas)) OF SSB-PositionQCL-CellsToAddMod-r16 + +``` + +``` + +SSB-PositionQCL-CellsToAddMod-r16 ::= SEQUENCE { + physCellId-r16 PhysCellId, + ssb-PositionQCL-r16 SSB-PositionQCL-Relation-r16 +} + +SSB-PositionQCL-CellList-r17 ::= SEQUENCE (SIZE (1..maxNrofCellMeas)) OF SSB-PositionQCL-Cell-r17 + +SSB-PositionQCL-Cell-r17 ::= SEQUENCE { + physCellId-r17 PhysCellId, + ssb-PositionQCL-r17 SSB-PositionQCL-Relation-r17 +} + +SSB-ToMeasureAltitudeBasedList-r18 ::= SEQUENCE (SIZE (1..maxNrofAltitudeRanges-r18)) OF SSB-ToMeasureAltitudeBased-r18 + +SSB-ToMeasureAltitudeBased-r18 ::= SEQUENCE { + altitudeRange-r18 SEQUENCE { + altitudeMin-r18 Altitude-r18 OPTIONAL, -- Need S + altitudeMax-r18 Altitude-r18 OPTIONAL, -- Need S + altitudeHyst-r18 HysteresisAltitude-r18 OPTIONAL -- Need S + }, + ssb-ToMeasure-r18 SSB-ToMeasure OPTIONAL -- Need S +} + +NTN-NeighbourCellInfo-r18 ::= SEQUENCE { + epochTime-r18 EpochTime-r17, + ephemerisInfo-r18 EphemerisInfo-r17 +} + +-- TAG-MEASOBJECTNR-STOP +-- ASN1STOP + +``` + +| CellsToAddMod field descriptions | +|---------------------------------------------------------------------------------------| +| cellIndividualOffset
Cell individual offsets applicable to a specific cell. | +| physCellId
Physical cell identity of a cell in the cell list. | + +| MeasObjectNR field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| absThreshCSI-RS-Consolidation
Absolute threshold for the consolidation of measurement results per CSI-RS resource(s) from L1 filter(s). The field is used for the derivation of cell measurement results as described in 5.5.3.3 and the reporting of beam measurement information per CSI-RS resource as described in 5.5.5.2. | +| absThreshSS-BlocksConsolidation
Absolute threshold for the consolidation of measurement results per SS/PBCH block(s) from L1 filter(s). The field is used for the derivation of cell measurement results as described in 5.5.3.3 and the reporting of beam measurement information per SS/PBCH block index as described in 5.5.5.2. | +| allowedCellsToAddModList
List of cells to add/modify in the allow-list of cells. It applies only to SSB resources. | +| allowedCellsToRemoveList
List of cells to remove from the allow-list of cells. | +| associatedMeasGapSSB
Indicates the associated measurement gap for SSB measuring identified by ssb-ConfigMobility in this measurement object. When multiple MeasObjectNR with the same SSB frequency are configured, the network configures the same measurement gap ID in this field for each MeasObjectNR . If this field is absent, the associated measurement gap is the gap configured via gapFR1 , gapFR2 , or gapUE . | +| associatedMeasGapSSB2
Indicates the associated additional measurement gap for SSB measuring identified by ssb-ConfigMobility in this measurement object for NTN deployments. When multiple MeasObjectNR with the same SSB frequency are configured, the network configures the same measurement gap ID in this field for each MeasObjectNR . If this field is absent, the associated measurement gap is the gap indicated by associatedMeasGapSSB . | +| associatedMeasGapCSI-RS
Indicates the associated measurement gap for CSI-RS measuring identified by csi-rs-ResourceConfigMobility in this measurement object. If this field is absent, the associated measurement gap is the gap configured via gapFR1 , gapFR2 , or gapUE . | +| associatedMeasGapCSI-RS2
Indicates the associated additional measurement gap for CSI-RS measuring identified by csi-rs-ResourceConfigMobility in this measurement object for NTN deployments. If this field is absent, the associated measurement gap is the gap indicated by associatedMeasGapCSI-RS . In this release of the specification, this field is not configured for NTN deployments. | +| cellsToAddModList
List of cells to add/modify in the cell list. | +| cellsToRemoveList
List of cells to remove from the cell list. | +| excludedCellsToAddModList
List of cells to add/modify in the exclude-list of cells. It applies only to SSB resources. | +| excludedCellsToRemoveList
List of cells to remove from the exclude-list of cells. | +| freqBandIndicatorNR
The frequency band in which the SSB and/or CSI-RS indicated in this MeasObjectNR are located and according to which the UE shall perform the RRM measurements. This field is always provided when the network configures measurements with this MeasObjectNR . | +| measCyclePSCell
The parameter is used only when the PSCell is configured on the frequency indicated by the measObjectNR and the SCG is deactivated, see TS 38.133 [14]. The field may also be configured when the PSCell is not configured on that frequency. The network always configures measCyclePSCell for the measObjectNR associated with the PSCell if bfd-and-RLM is set to true and the SCG is deactivated. Value ms160 corresponds to 160 ms, value ms256 corresponds to 256 ms and so on. | +| measCycleSCell
The parameter is used only when an SCell is configured on the frequency indicated by the measObjectNR and is in deactivated state, see TS 38.133 [14]. gNB configures the parameter whenever an SCell is configured on the frequency indicated by the measObjectNR , but the field may also be signalled when an SCell is not configured. Value sf160 | + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| corresponds to 160 sub-frames, value sf256 corresponds to 256 sub-frames and so on. | +| measSequence
Indicates the recommended sequence for intra/inter-RAT intra/inter-frequency measurement. Value 1 means the corresponding frequency is measured firstly. Value 2 means the corresponding frequency is measured secondly and so on. If more than one frequency is configured with the same value, it means no recommended sequence among these frequencies. If not provided, it means there is no recommended sequence for the corresponding frequency. This field is only configured for NR standalone or if the measObject is associated to the MCG. | +| nrofCSIinrofCSI-RS-ResourcesToAverage
Indicates the maximum number of measurement results per beam based on CSI-RS resources to be averaged. The same value applies for each detected cell associated with this MeasObjectNR . | +| nrofSS-BlocksToAverage
Indicates the maximum number of measurement results per beam based on SS/PBCH blocks to be averaged. The same value applies for each detected cell associated with this MeasObject . | +| ntn-NeighbourCellInfo
Includes satellite assistance information of an NTN neighbour cell. | +| ntn-PolarizationDL
If present, this parameter indicates polarization information for downlink transmission on service link: including Right hand, Left hand circular polarizations (RHCP, LHCP) and Linear polarization. | +| ntn-PolarizationUL
If present, this parameter indicates polarization information for uplink transmission on service link. If not present and ntn-PolarizationDL is present, UE assumes the same polarization for UL and DL. | +| offsetMO
Offset values applicable to all measured cells with reference signal(s) indicated in this MeasObjectNR . | +| quantityConfigIndex
Indicates the n-th element of quantityConfigNR-List provided in MeasConfig . | +| referenceSignalConfig
RS configuration for SS/PBCH block and CSI-RS. | +| refFreqCSI-RS
Point A which is used for mapping of CSI-RS to physical resources according to TS 38.211 [16] clause 7.4.1.5.3. | +| smtc1
Primary measurement timing configuration. (see clause 5.5.2.10). | +| smtc2
Secondary measurement timing configuration for SS corresponding to this MeasObjectNR with PCI listed in pci-List . For these SS, the periodicity is indicated by periodicity in smtc2 and the timing offset is equal to the offset indicated in periodicityAndOffset modulo periodicity . periodicity in smtc2 can only be set to a value strictly shorter than the periodicity indicated by periodicityAndOffset in smtc1 (e.g. if periodicityAndOffset indicates sf10 , periodicity can only be set of sf5 , if periodicityAndOffset indicates sf5 , smtc2 cannot be configured). | +| smtc3list
Measurement timing configuration list for SS corresponding to IAB-MT. This is used for the IAB-node's discovery of other IAB-nodes and the IAB-Donor-DUs. | +| smtc4list
Measurement timing configuration list for NTN deployments, see clause 5.5.2.10. | +| ssbFrequency
Indicates the frequency of the SS associated to this MeasObjectNR . For operation with shared spectrum channel access, this field is a k*30 kHz shift from the sync raster where k = 0,1,2, and so on if the reportType within the corresponding ReportConfigNR is set to reportCGI (see TS 38.211 [16], clause 7.4.3.1). Frequencies are considered to be on the sync raster if they are also identifiable with a GSCN value (see TS 38.101-1 [15], or TS 38.101-5 [75]). | +| ssb-PositionQCL-Common | + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Indicates the QCL relationship between SS/PBCH blocks for all measured cells as specified in TS 38.213 [13], clause 4.1. | +| ssbSubcarrierSpacing
Subcarrier spacing of SSB.
Only the following values are applicable depending on the used frequency:
FR1: 15 or 30 kHz
FR2-1: 120 or 240 kHz
FR2-2: 120, 480, or 960 kHz | +| t312
The value of timer T312. Value ms0 represents 0 ms, ms50 represents 50 ms and so on. | + +| ReferenceSignalConfig field descriptions | +|---------------------------------------------------------------------------------------------------------------| +| csi-rs-ResourceConfigMobility
CSI-RS resources to be used for CSI-RS based RRM measurements. | +| ssb-ConfigMobility
SSB configuration for mobility (nominal SSBs, timing configuration). | + +| RMTC-Config field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| measDurationSymbols
Number of consecutive symbols for which the Physical Layer reports samples of RSSI (see TS 38.215 [9], clause 5.1.21). Value sym1 corresponds to one symbol, sym14or12 corresponds to 14 symbols of the reference numerology for NCP and 12 symbols for ECP, and so on.
If measDurationSymbols-v1700 is signalled, the UE ignores measDurationSymbols-r16 . | +| ref-BWPId
Indicates the reference BWP for the TCI state indicated in tc-StateInfo . Network includes this field if tc-StateInfo is present. This field is only applicable for operation with shared spectrum channel access in FR2-2 and network does not configure this if the UE does not have any serving cells in FR2-2. | +| ref-SCS-CP
Indicates a reference subcarrier spacing and cyclic prefix to be used for RSSI measurements (see TS 38.215 [9]). Value kHz15 corresponds to 15kHz, kHz30 corresponds to 30 kHz, value kHz60-NCP corresponds to 60 kHz using normal cyclic prefix (NCP), and kHz60-ECP corresponds to 60 kHz using extended cyclic prefix (ECP).
If ref-SCS-CP-v1700 is signalled, the UE ignores ref-SCS-CP-r16 . | +| ref-ServCellId
Indicates the FR2-2 reference serving cell index for the TCI state. Network includes this field if tc-StateInfo is present. This field is only applicable for operation with shared spectrum channel access in FR2-2 and network does not configure this if the UE does not have any serving cells in FR2-2. | +| rmtc-Bandwidth
Indicates the bandwidth for the RSSI measurement (see TS 38. 215 [9], clause 5.1.21). | +| rmtc-Frequency
Indicates the center frequency of the measured bandwidth for a frequency which operates with shared spectrum channel access (see TS 38. 215 [9], clause 5.1.21). | +| rmtc-Periodicity
Indicates the RSSI measurement timing configuration (RMTC) periodicity (see TS 38.215 [9], clause 5.1.21). | +| rmtc-SubframeOffset
Indicates the RSSI measurement timing configuration (RMTC) subframe offset for this frequency (see TS 38.215 [9], clause 5.1.21). For inter-frequency measurements, this field is optional present and if it is not configured, the UE chooses a random value as rmtc-SubframeOffset for measDurationSymbols which shall be selected to be between 0 and the configured rmtc-Periodicity with equal probability. | +| tc-StateId
Indicates the TCI state to be used for RSSI measurements. This field is only applicable for shared spectrum channel access in FR2-2. Network does not configure this if the UE does not have any serving cells in FR2-2 and in such a case, it is up to UE implementation how to determine the spatial domain filter for the inter-frequency RSSI measurement in FR2-2. | + +| SSB-ConfigMobility field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| cca-CellsToAddModList, cca-CellsToRemoveList
Lists of cells to be added or removed from the list of neighbor cells that apply channel access mode procedures for operation with shared spectrum channel access in accordance with TS 37.213 [48], clause 4.4 for FR2-2. | +| deriveSSB-IndexFromCell
If this field is set to true , UE assumes SFN and frame boundary alignment across cells on the same frequency carrier as specified in TS 38.133 [14]. Hence, if the UE is configured with a serving cell for which ( absoluteFrequencySSB, subcarrierSpacing ) in ServingCellConfigCommon is equal to ( ssbFrequency, ssbSubcarrierSpacing ) in this MeasObjectNR , this field indicates whether the UE can utilize the timing of this serving cell to derive the index of SS block transmitted by neighbour cell. Otherwise, this field indicates whether the UE may use the timing of any detected cell on that target frequency to derive the SSB index of all neighbour cells on that frequency. | +| deriveSSB-IndexFromCellInter
If this field is present, UE assumes SFN and frame boundary alignment between the reference serving cell indicated by ServCellIndex and all neighbour cells in this MeasObjectNR as specified in TS 38.133 [14]. This field also indicates that the UE can utilize the timing of the reference serving cell indicated by ServCellIndex to derive the index of SS block transmitted by all inter-frequency neighbour cells on the frequency indicated by the MeasObjectNR . When this field is included, the network should set deriveSSB-IndexFromCell to true . | +| ssb-ToMeasure
The set of SS blocks to be measured within the SMTC measurement duration. 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 to be measured while value 1 indicates that the corresponding SS/PBCH block is to be measured (see TS 38.215 [9]). When the field is not configured the UE measures on all SS blocks. Regardless of the value of this field, SS/PBCH blocks outside of the applicable smtc are not to be measured. See TS 38.215 [9] clause 5.1.1. | +| ssb-ToMeasureAltitudeBasedList
List of altitude-dependent ssb-ToMeasure . When the UE is within an altitude range indicated by altitudeRange , it ignores the ssb-ToMeasure (without suffix), and applies the corresponding ssb-ToMeasure-r18 if present, otherwise measures on all SS-blocks if ssb-ToMeasure-r18 is absent. When the UE is outside all the altitude ranges indicated by altitudeRange (if any), ssb-ToMeasure (without suffix) applies.
For each altitude range, altitudeMin indicates the minimum altitude in meters, altitudeMax indicates the maximum altitude in meters relative to sea level, and if included, altitudeHyst indicates hysteresis in meters for determination of the altitude range. I.e., when altitudeHyst is configured for an altitude range, the UE considers itself to have entered the range if $altitudeMin \leq \text{UE altitude} \leq altitudeMax$ and after entering the range considers itself to be in the range while $(altitudeMin - altitudeHyst) \leq \text{UE altitude} \leq (altitudeMax + altitudeHyst)$ .
For each altitudeRange , if altitudeMin is absent, value minAltitude-r18 is used and if altitudeMax is absent, value maxAltitude-r18 is used. | + +| SSB-PositionQCL-CellsToAddMod field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| physCellId
Physical cell identity of a cell in the cell list. | +| ssb-PositionQCL
Indicates the QCL relation between SS/PBCH blocks for a specific cell as specified in TS 38.213 [13], clause 4.1. If provided, the cell specific value overwrites the value signalled by ssb-PositionQCL-Common . | + +| Conditional Presence | Explanation | +|----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AssociatedGapCSI/RS | This field is optionally present, Need R if associatedMeasGapCSI/RS is configured, otherwise, it is absent. | +| AssociatedGapSSB | This field is optionally present, Need R if associatedMeasGapSSB is configured, otherwise, it is absent. | +| CSI-RS | This field is mandatory present if csi-rs-ResourceConfigMobility is configured, otherwise, it is absent. | +| IntraFreqConnected | This field is optionally present, Need R if the UE is configured with a serving cell for which (absoluteFrequencySSB, subcarrierSpacing) in ServingCellConfigCommon is equal to ( ssbFrequency , ssbSubcarrierSpacing ) in this MeasObjectNR , otherwise, it is absent. | +| SCG | This field is optionally present, Need R, in the measConfig associated with the SCG. It is absent in the measConfig associated with the MCG. | +| ServingCell | This field is optionally present, Need N, if this MeasObject is configured by the serving cell for a conditional reconfiguration with sync . Otherwise, it is absent. | +| SharedSpectrum | This field is mandatory present if this MeasObject is for a frequency which operates with shared spectrum channel access in FR1. Otherwise, it is absent, Need R. | +| SharedSpectrum2 | This field is optionally present if this MeasObject is for a frequency which operates with shared spectrum channel access in FR2-2, Need R. Otherwise, it is absent, Need R. | +| SSBorAssociatedSSB | This field is mandatory present if ssb-ConfigMobility is configured or associatedSSB is configured in at least one cell. Otherwise, it is absent, Need R. | + +#### MeasObjectNR-SL + +The IE *MeasObjectNR-SL* concerns a measurement object including a list of transmission resource pool(s) for which CBR measurement is performed for NR sidelink communication/discovery. + +#### MeasObjectNR-SL information element + +``` +-- ASN1START +-- TAG-MEASOBJECTNR-SL-START + +MeasObjectNR-SL-r16 ::= SEQUENCE { + tx-PoolMeasToRemoveList-r16 Tx-PoolMeasList-r16 OPTIONAL, -- Need N + tx-PoolMeasToAddModList-r16 Tx-PoolMeasList-r16 OPTIONAL -- Need N +} + +MeasObjectNR-SL-v1800 ::= SEQUENCE { + sl-Frequency INTEGER (1..maxNrofFreqSL-r16), + tx-PoolMeasToRemoveList-r16 Tx-PoolMeasList-r16 OPTIONAL, -- Need N + tx-PoolMeasToAddModList-r16 Tx-PoolMeasList-r16 OPTIONAL -- Need N +} + +Tx-PoolMeasList-r16 ::= SEQUENCE (SIZE (1..maxNrofSL-PoolToMeasureNR-r16)) OF SL-ResourcePoolID-r16 + +-- TAG-MEASOBJECTNR-SL-STOP +-- ASN1STOP +``` + +| MeasObjectNR-SL field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-Frequency
Indicates the sidelink frequency associated to this MeasObjectNR-SL . The value 1 corresponds to the frequency of first entry in sl-FreqInfoList broadcast in SIB12 , the value 2 corresponds to the frequency of first entry in sl-FreqInfoListSizeExt broadcast in SIB12 , the value 3 corresponds to the frequency of second entry in sl-FreqInfoListSizeExt broadcast in SIB12 and so on. | + +#### – *MeasObjectRxTxDiff* + +The IE *MeasObjectRxTxDiff* is used to configure the measurement object for UE Rx-Tx time difference measurement. + +#### ***MeasObjectRxTxDiff* information element** + +``` +-- ASN1START +-- TAG-MEASOBJECTRXTXDIFF-START + +MeasObjectRxTxDiff-r17 ::= SEQUENCE { + dl-Ref-r17 CHOICE { + prs-Ref-r17 NULL, + csi-RS-Ref-r17 NULL, + ... + } OPTIONAL, -- Need R + ... +} + +-- TAG-MEASOBJECTRXTXDIFF-STOP +-- ASN1STOP +``` + +| MeasObjectRxTxDiff field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| dl-Ref
configures the DL references signals to measure Rx-Tx time difference. prs-Ref-r17 indicates PRS is chosen, and csi-RS-Ref-r17 indicates that CSI-RS for tracking is chosen. Only one PRS resource set is configured by the network. Only one NZP-CSI-RS-ResourceSet can be configured with pdc-Info-r17 set to true and it is used for UE Rx-Tx time difference measurement. Only reference signals from the PCell of the MCG can be configured by the network. | + +#### – *MeasObjectToAddModList* + +The IE *MeasObjectToAddModList* concerns a list of measurement objects to add or modify. + +#### ***MeasObjectToAddModList* information element** + +``` +-- ASN1START +-- TAG-MEASOBJECTTOADDMODLIST-START +``` + +``` + +MeasObjectToAddModList ::= +MeasObjectToAddMod ::= + measObjectId + measObject + measObjectNR + .../ + measObjectEUTRA + measObjectUTRA-FDD-r16 + measObjectNR-SL-r16 + measObjectCLI-r16 + measObjectRxDiff-r17 + measObjectRelay-r17 + measObjectNR-SL-v1800 +} +} + +-- TAG-MEASOBJECTTOADDMODLIST-STOP +-- ASN1STOP + +``` + +``` + +SEQUENCE (SIZE (1..maxNrofObjectId)) OF MeasObjectToAddMod +SEQUENCE { + MeasObjectId, + CHOICE { + MeasObjectNR, + MeasObjectEUTRA, + MeasObjectUTRA-FDD-r16, + MeasObjectNR-SL-r16, + MeasObjectCLI-r16, + MeasObjectRxDiff-r17, + SL-MeasObject-r16, + MeasObjectNR-SL-v1800 + } +} + +``` + +#### MeasObjectUTRA-FDD + +The IE *MeasObjectUTRA-FDD* specifies information applicable for inter-RAT UTRA-FDD neighbouring cells. + +#### MeasObjectUTRA-FDD information element + +``` + +-- ASN1START +-- TAG-MEASOBJECTUTRA-FDD-START + +MeasObjectUTRA-FDD-r16 ::= + carrierFreq-r16 + utra-FDD-Q-OffsetRange-r16 + cellsToRemoveList-r16 + cellsToAddModList-r16 + ... +} + +CellsToAddModListUTRA-FDD-r16 ::= +CellsToAddModUTRA-FDD-r16 ::= + cellIndexUTRA-FDD-r16 + physCellId-r16 +} + +UTRA-FDD-CellIndexList-r16 ::= +UTRA-FDD-CellIndex-r16 ::= +-- TAG-MEASOBJECTUTRA-FDD-STOP + +``` + +``` + +SEQUENCE { + ARFCN-ValueUTRA-FDD-r16, + UTRA-FDD-Q-OffsetRange-r16 OPTIONAL, -- Need R + UTRA-FDD-CellIndexList-r16 OPTIONAL, -- Need N + CellsToAddModListUTRA-FDD-r16 OPTIONAL, -- Need N +} + +``` + +``` + +SEQUENCE (SIZE (1..maxCellMeasUTRA-FDD-r16)) OF CellsToAddModUTRA-FDD-r16 + +``` + +``` + +SEQUENCE { + UTRA-FDD-CellIndex-r16, + PhysCellIdUTRA-FDD-r16 +} + +``` + +``` + +SEQUENCE (SIZE (1..maxCellMeasUTRA-FDD-r16)) OF UTRA-FDD-CellIndex-r16 + +``` + +``` + +INTEGER (1..maxCellMeasUTRA-FDD-r16) + +``` + +``` +-- ASN1STOP +``` + +#### MeasObjectUTRA-FDD field descriptions + +| | | +|-------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| carrierFreq | Identifies UTRA-FDD carrier frequency for which this configuration is valid. NR does not configure more than one measurement object for the same physical frequency regardless of the ARFCN used to indicate this. | +| cellIndexUTRA-FDD | Entry index in the neighbouring cell list. | +| cellsToAddModList | List of UTRA-FDD cells to add/modify in the neighbouring cell list. | +| cellsToRemoveList | List of cells to remove from the neighbouring cell list. | +| utra-FDD-Q-OffsetRange | Used to indicate a frequency specific offset to be applied when evaluating triggering conditions for measurement reporting. The value is in dB. | + +#### MeasResultCellListSFTD-NR + +The IE *MeasResultCellListSFTD-NR* consists of SFN and radio frame boundary difference between the PCell and an NR cell as specified in TS 38.215 [9] and TS 38.133 [14]. + +#### MeasResultCellListSFTD-NR information element + +``` +-- ASN1START +-- TAG-MEASRESULTCELLISTSFTD-NR-START + +MeasResultCellListSFTD-NR ::= + SEQUENCE (SIZE (1..maxCellSFTD)) OF MeasResultCellSFTD-NR + +MeasResultCellSFTD-NR ::= + SEQUENCE { + physCellId PhysCellId, + sfn-OffsetResult INTEGER (0..1023), + frameBoundaryOffsetResult INTEGER (-30720..30719), + rsrp-Result RSRP-Range OPTIONAL + } + +-- TAG-MEASRESULTCELLISTSFTD-NR-STOP +-- ASN1STOP +``` + +#### MeasResultCellSFTD-NR field descriptions + +| | | +|----------------------------------|---------------------------------------------------------------------------------------------------------------------------| +| sfn-OffsetResult | Indicates the SFN difference between the PCell and the NR cell as an integer value according to TS 38.215 [9]. | +| frameBoundaryOffsetResult | Indicates the frame boundary difference between the PCell and the NR cell as an integer value according to TS 38.215 [9]. | + +#### MeasResultCellListSFTD-EUTRA + +The IE *MeasResultCellListSFTD-EUTRA* consists of SFN and radio frame boundary difference between the PCell and an E-UTRA PSCell. + +#### MeasResultCellListSFTD-EUTRA information element + +``` +-- ASN1START +-- TAG-MEASRESULTCELLLISTSFTD-EUTRA-START + +MeasResultCellListSFTD-EUTRA ::= SEQUENCE (SIZE (1..maxCellSFTD)) OF MeasResultSFTD-EUTRA + +MeasResultSFTD-EUTRA ::= SEQUENCE { + eutra-PhysCellId EUTRA-PhysCellId, + sfn-OffsetResult INTEGER (0..1023), + frameBoundaryOffsetResult INTEGER (-30720..30719), + rsrp-Result RSRP-Range OPTIONAL +} + +-- TAG-MEASRESULTCELLLISTSFTD-EUTRA-STOP +-- ASN1STOP +``` + +#### MeasResultSFTD-EUTRA field descriptions + +##### *eutra-PhysCellId* + +Identifies the physical cell identity of the E-UTRA cell for which the reporting is being performed. + +##### *sfn-OffsetResult* + +Indicates the SFN difference between the PCell and the E-UTRA cell as an integer value according to TS 38.215 [9]. + +##### *frameBoundaryOffsetResult* + +Indicates the frame boundary difference between the PCell and the E-UTRA cell as an integer value according to TS 38.215 [9]. + +### MeasResults + +The IE *MeasResults* covers measured results for intra-frequency, inter-frequency, inter-RAT mobility and measured results for NR sidelink communication/discovery. + +#### MeasResults information element + +``` +-- ASN1START +-- TAG-MEASRESULTS-START + +MeasResults ::= SEQUENCE { + measId MeasId, + measResultServingMOList MeasResultServMOList, + measResultNeighCells CHOICE { + measResultListNR MeasResultListNR, + ... + measResultListEUTRA MeasResultListEUTRA, + } +} +``` + +``` + + measResultListUTRA-FDD-r16 MeasResultListUTRA-FDD-r16, + sl-MeasResultsCandRelay-r17 OCTET STRING -- Contains PC5 SL-MeasResultListRelay-r17 + } OPTIONAL, + ..., + [[ + measResultServFreqListEUTRA-SCG MeasResultServFreqListEUTRA-SCG OPTIONAL, + measResultServFreqListNR-SCG MeasResultServFreqListNR-SCG OPTIONAL, + measResultSFTD-EUTRA MeasResultSFTD-EUTRA OPTIONAL, + measResultSFTD-NR MeasResultCellSFTD-NR OPTIONAL + ]], + [[ + measResultCellListSFTD-NR MeasResultCellListSFTD-NR OPTIONAL + ]], + [[ + measResultForRSSI-r16 MeasResultForRSSI-r16 OPTIONAL, + locationInfo-r16 LocationInfo-r16 OPTIONAL, + ul-PDCP-DelayValueResultList-r16 UL-PDCP-DelayValueResultList-r16 OPTIONAL, + measResultsSL-r16 MeasResultsSL-r16 OPTIONAL, + measResultCLI-r16 MeasResultCLI-r16 OPTIONAL + ]], + [[ + measResultRxBTxTimeDiff-r17 MeasResultRxBTxTimeDiff-r17 OPTIONAL, + sl-MeasResultServingRelay-r17 OCTET STRING OPTIONAL, + -- Contains PC5 SL-MeasResultRelay-r17 + ul-PDCP-ExcessDelayResultList-r17 UL-PDCP-ExcessDelayResultList-r17 OPTIONAL, + coarseLocationInfo-r17 OCTET STRING OPTIONAL + ]], + [[ + altitudeUE-r18 Altitude-r18 OPTIONAL + ]] +} + +MeasResultServMOList ::= SEQUENCE (SIZE (1..maxNrofServingCells)) OF MeasResultServMO + +MeasResultServMO ::= SEQUENCE { + servCellId ServCellIndex, + measResultServingCell MeasResultNR, + measResultBestNeighCell MeasResultNR OPTIONAL, + ... +} + +MeasResultListNR ::= SEQUENCE (SIZE (1..maxCellReport)) OF MeasResultNR + +MeasResultNR ::= SEQUENCE { + physCellId PhysCellId OPTIONAL, + measResult SEQUENCE { + cellResults SEQUENCE{ + resultsSSB-Cell MeasQuantityResults OPTIONAL, + resultsCSI-RS-Cell MeasQuantityResults OPTIONAL + }, + rsIndexResults SEQUENCE{ + +``` + +``` + + resultsSSB-Indexes ResultsPerSSB-IndexList OPTIONAL, + resultsCSI-RS-Indexes ResultsPerCSI-RS-IndexList OPTIONAL + } +}, +... +[[ +cgi-Info CGI-InfoNR OPTIONAL +]] , +[[ +choCandidate-r17 ENUMERATED {true} OPTIONAL, +choConfig-r17 SEQUENCE (SIZE (1..2)) OF CondTriggerConfig-r16 OPTIONAL, +triggeredEvent-r17 SEQUENCE { + timeBetweenEvents-r17 TimeBetweenEvent-r17 OPTIONAL, + firstTriggeredEvent ENUMERATED {condFirstEvent, condSecondEvent} OPTIONAL +} OPTIONAL +]] +} + +MeasResultListEUTRA ::= SEQUENCE (SIZE (1..maxCellReport)) OF MeasResultEUTRA + +MeasResultEUTRA ::= SEQUENCE { + eutra-PhysCellId PhysCellId, + measResult MeasQuantityResultsEUTRA, + + cgi-Info CGI-InfoEUTRA OPTIONAL, + ... +} + +MultiBandInfoListEUTRA ::= SEQUENCE (SIZE (1..maxMultiBands)) OF FreqBandIndicatorEUTRA + +MeasQuantityResults ::= SEQUENCE { + rsrp RSRP-Range OPTIONAL, + rsrq RSRQ-Range OPTIONAL, + sinr SINR-Range OPTIONAL +} + +MeasQuantityResultsEUTRA ::= SEQUENCE { + rsrp RSRP-RangeEUTRA OPTIONAL, + rsrq RSRQ-RangeEUTRA OPTIONAL, + sinr SINR-RangeEUTRA OPTIONAL +} + +ResultsPerSSB-IndexList ::= SEQUENCE (SIZE (1..maxNrofIndexesToReport2)) OF ResultsPerSSB-Index + +ResultsPerSSB-Index ::= SEQUENCE { + ssb-Index SSB-Index, + ssb-Results MeasQuantityResults OPTIONAL +} + +ResultsPerCSI-RS-IndexList ::= SEQUENCE (SIZE (1..maxNrofIndexesToReport2)) OF ResultsPerCSI-RS-Index + +``` + +``` +ResultsPerCSI-RS-Index ::= SEQUENCE { + csi-RS-Index CSI-RS-Index, + csi-RS-Results MeasQuantityResults +} OPTIONAL +MeasResultServFreqListEUTRA-SCG ::= SEQUENCE (SIZE (1..maxNrofServingCellsEUTRA)) OF MeasResult2EUTRA +MeasResultServFreqListNR-SCG ::= SEQUENCE (SIZE (1..maxNrofServingCells)) OF MeasResult2NR +MeasResultListUTRA-FDD-r16 ::= SEQUENCE (SIZE (1..maxCellReport)) OF MeasResultUTRA-FDD-r16 +MeasResultUTRA-FDD-r16 ::= SEQUENCE { + physCellId-r16 PhysCellIdUTRA-FDD-r16, + measResult-r16 SEQUENCE { + utra-FDD-RSCP-r16 INTEGER (-5..91) OPTIONAL, + utra-FDD-EcN0-r16 INTEGER (0..49) OPTIONAL + } +} +MeasResultForRSSI-r16 ::= SEQUENCE { + rssi-Result-r16 RSSI-Range-r16, + channelOccupancy-r16 INTEGER (0..100) +} +MeasResultCLI-r16 ::= SEQUENCE { + measResultListSRS-RSRP-r16 MeasResultListSRS-RSRP-r16 + measResultListCLI-RSSI-r16 MeasResultListCLI-RSSI-r16 +} OPTIONAL, + OPTIONAL +MeasResultListSRS-RSRP-r16 ::= SEQUENCE (SIZE (1.. maxCLI-Report-r16)) OF MeasResultSRS-RSRP-r16 +MeasResultSRS-RSRP-r16 ::= SEQUENCE { + srs-ResourceId-r16 SRS-ResourceId, + srs-RSRP-Result-r16 SRS-RSRP-Range-r16 +} +MeasResultListCLI-RSSI-r16 ::= SEQUENCE (SIZE (1.. maxCLI-Report-r16)) OF MeasResultCLI-RSSI-r16 +MeasResultCLI-RSSI-r16 ::= SEQUENCE { + rssi-ResourceId-r16 RSSI-ResourceId-r16, + cli-RSSI-Result-r16 CLI-RSSI-Range-r16 +} +``` + +``` +UL-PDCP-DelayValueResultList-r16 ::= SEQUENCE (SIZE (1..maxDRB)) OF UL-PDCP-DelayValueResult-r16 + +UL-PDCP-DelayValueResult-r16 ::= SEQUENCE { + drb-Id-r16 DRB-Identity, + averageDelay-r16 INTEGER (0..10000), + ... +} + +UL-PDCP-ExcessDelayResultList-r17 ::= SEQUENCE (SIZE (1..maxDRB)) OF UL-PDCP-ExcessDelayResult-r17 + +UL-PDCP-ExcessDelayResult-r17 ::= SEQUENCE { + drb-Id-r17 DRB-Identity, + excessDelay-r17 INTEGER (0..31), + ... +} + +TimeBetweenEvent-r17 ::= INTEGER (0..1023) + +-- TAG-MEASRESULTS-STOP +-- ASN1STOP +``` + +#### | | |-------------------------------------------| | MeasResultEUTRA field descriptions | |-------------------------------------------| + +##### | | |--------------------------------| | eutra-PhysCellId | |--------------------------------| + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Identifies the physical cell identity of the E-UTRA cell for which the reporting is being performed. The UE reports a value in the range 0..503, other values are reserved. | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| MeasResultNR field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| averageDelay
Indicates average delay for the packets during the reporting period, as specified in TS 38.314 [53]. Value 0 corresponds to 0 millisecond, value 1 corresponds to 0.1 millisecond, value 2 corresponds to 0.2 millisecond, and so on. | +| cellResults
Cell level measurement results. | +| choCandidate
This field indicates whether the associated cell is a candidate target cell for conditional handover or conditional PSCell change or addition. This field may be included only in the SuccessHO-Report or SuccessPSCell-Report within UEInformationResponse message. | +| choConfig
If the associated cell is a candidate target cell for conditional handover, this field indicates the conditional handover execution condition for each measId within condTriggerConfig associated to the cell. This field may be included only in the rlf-report within UEInformationResponse message. | +| drb-Id
Indicates DRB value for which uplink PDCP delay ratio or value is provided, according to TS 38.314 [53]. | +| firstTriggeredEvent
This field is set to condFirstEvent if the execution condition associated to the first entry of choConfig was fulfilled first in time. This field is set to condSecondEvent if the execution condition associated to the second entry of choConfig was fulfilled first in time. This field may be included in rlf-report within UEInformationResponse message or in SCGFailureInformation message. | +| locationInfo
Positioning related information and measurements. | +| physCellId
The physical cell identity of the NR cell for which the reporting is being performed. | +| resultsSSB-Cell
Cell level measurement results based on SS/PBCH related measurements. | +| resultsSSB-Indexes
Beam level measurement results based on SS/PBCH related measurements. | +| resultsCSI-RS-Cell
Cell level measurement results based on CSI-RS related measurements. | +| resultsCSI-RS-Indexes
Beam level measurement results based on CSI-RS related measurements. | +| rsIndexResults
Beam level measurement results. | +| timeBetweenEvents
Indicates the time elapsed between fulfilling the conditional execution conditions included in choConfig . Value in milliseconds. The maximum value 1023 means 1023ms or longer. This field may be included in the reports associated to UEInformationResponse message, e.g., rlf-Report or in the SCGFailureInformation message. | + +| MeasResultUTRA-FDD field descriptions | +|-------------------------------------------------------------------------------------------------------------------------| +| physCellId
The physical cell identity of the UTRA-FDD cell for which the reporting is being performed. | +| utra-FDD-EcN0
According to CPICH_Ec/No in TS 25.133 [46] for FDD. | +| utra-FDD-RSCP
According to CPICH_RSCP in TS 25.133 [46] for FDD. | + +| MeasResults field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| coarseLocationInfo
This field indicates the coarse location information reported by the UE. This field is coded as the Ellipsoid-Point defined in TS 37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit. The least significant bits of degreesLatitude and degreesLongitude are set to 0 to meet the accuracy requirement corresponds to a granularity of approximately 2 km.
It is up to UE implementation how many LSBs are set to 0 to meet the accuracy requirement | +| excessDelay
Indicates the ratio of packets in UL per DRB exceeding the configured delay threshold among the UL PDCP SDUs, according to the UL PDCP Excess Packet Delay per DRB mapping table, as defined in TS 38.314 [53], Table 4.3.1.e-1. | +| measId
Identifies the measurement identity for which the reporting is being performed. | +| measQuantityResults
The value sinr is not included when it is used for LogMeasReport-r16 . | +| measResultCellListSFTD-NR
SFTD measurement results between the PCell and the NR neighbour cell(s) in NR standalone. | +| measResultCLI
CLI measurement results. | +| measResultEUTRA
Measured results of an E-UTRA cell. | +| measResultForRSSI
Includes measured RSSI result in dBm (see TS 38.215 [9]) and channelOccupancy which is the percentage of samples when the RSSI was above the configured channelOccupancyThreshold for the associated reportConfig . | +| measResultListEUTRA
List of measured results for the maximum number of reported best cells for an E-UTRA measurement identity. | +| measResultListNR
List of measured results for the maximum number of reported best cells for an NR measurement identity. | +| measResultListUTRA-FDD
List of measured results for the maximum number of reported best cells for a UTRA-FDD measurement identity. | +| measResultNR
Measured results of an NR cell. | +| measResultServFreqListEUTRA-SCG
Measured results of the E-UTRA SCG serving frequencies: the measurement result of PSCell and each SCell, if any, and of the best neighbouring cell on each E-UTRA SCG serving frequency. | +| measResultServFreqListNR-SCG
Measured results of the NR SCG serving frequencies: the measurement result of PSCell and each SCell, if any, and of the best neighbouring cell on each NR SCG serving frequency. | +| measResultServingMOList
Measured results of measured cells with reference signals indicated in the serving cell measurement objects including measurement results of SpCell, configured SCell(s) and best neighbouring cell within measured cells with reference signals indicated in on each serving cell measurement object. If the sending of the MeasurementReport message is triggered by a measurement configured by the field sl-ConfigDedicatedForNR received within an E-UTRA RRCConnectionReconfiguration message (i.e. CBR measurements), this field is not applicable and its contents is ignored by the network. | +| measResultSFTD-EUTRA
SFTD measurement results between the PCell and the E-UTRA PSCell in NE-DC. | + +| MeasResults field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| coarseLocationInfo
This field indicates the coarse location information reported by the UE. This field is coded as the Ellipsoid-Point defined in TS 37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit. The least significant bits of degreesLatitude and degreesLongitude are set to 0 to meet the accuracy requirement corresponds to a granularity of approximately 2 km.
It is up to UE implementation how many LSBs are set to 0 to meet the accuracy requirement | +| excessDelay
Indicates the ratio of packets in UL per DRB exceeding the configured delay threshold among the UL PDCP SDUs, according to the UL PDCP Excess Packet Delay per DRB mapping table, as defined in TS 38.314 [53], Table 4.3.1.e-1. | +| measResultSFTD-NR
SFTD measurement results between the PCell and the NR PScell in NR-DC. | +| measResultsSL
CBR measurements results for NR sidelink communication/discovery. | +| measResultUTRA-FDD
Measured result of a UTRA-FDD cell. | +| sl-MeasResultsCandRelay
Measurement result(s) of candidate L2 U2N relay UE(s). | +| sl-MeasResultServingRelay
Measurement result of serving L2 U2N relay UE. | + +#### — MeasResult2EUTRA + +The IE *MeasResult2EUTRA* contains measurements on E-UTRA frequencies. + +#### **MeasResult2EUTRA information element** + +``` +-- ASN1START +-- TAG-MEASRESULT2EUTRA-START + +MeasResult2EUTRA ::= SEQUENCE { + carrierFreq ARFCN-ValueEUTRA, + measResultServingCell MeasResultEUTRA OPTIONAL, + measResultBestNeighCell MeasResultEUTRA OPTIONAL, + ... +} + +-- TAG-MEASRESULT2EUTRA-STOP +-- ASN1STOP +``` + +#### — MeasResult2NR + +The IE *MeasResult2NR* contains measurements on NR frequencies. + +#### **MeasResult2NR information element** + +``` + +-- ASN1START +-- TAG-MEASRESULT2NR-START + +MeasResult2NR ::= SEQUENCE { + ssbFrequency ARFCN-ValueNR OPTIONAL, + refFreqCSI-RS ARFCN-ValueNR OPTIONAL, + measResultServingCell MeasResultNR OPTIONAL, + measResultNeighCellListNR MeasResultListNR OPTIONAL, + ... +} + +-- TAG-MEASRESULT2NR-STOP +-- ASN1STOP + +``` + +#### **MeasResultIdleEUTRA** + +The IE *MeasResultIdleEUTRA* covers the E-UTRA measurement results performed in RRC\_IDLE and RRC\_INACTIVE. + +#### **MeasResultIdleEUTRA information element** + +``` + +-- ASN1START +-- TAG-MEASRESULTIDLEEUTRA-START + +MeasResultIdleEUTRA-r16 ::= SEQUENCE { + measResultsPerCarrierListIdleEUTRA-r16 SEQUENCE (SIZE (1.. maxFreqIdle-r16)) OF MeasResultsPerCarrierIdleEUTRA-r16, + ... +} + +MeasResultsPerCarrierIdleEUTRA-r16 ::= SEQUENCE { + carrierFreqEUTRA-r16 ARFCN-ValueEUTRA, + measResultsPerCellListIdleEUTRA-r16 SEQUENCE (SIZE (1..maxCellMeasIdle-r16)) OF MeasResultsPerCellIdleEUTRA-r16, + ... +} + +MeasResultsPerCellIdleEUTRA-r16 ::= SEQUENCE { + eutra-PhysCellId-r16 EUTRA-PhysCellId, + measIdleResultEUTRA-r16 SEQUENCE { + rsrp-ResultEUTRA-r16 RSRP-RangeEUTRA OPTIONAL, + rsrq-ResultEUTRA-r16 RSQ-RangeEUTRA-r16 OPTIONAL + }, + ... +} + +-- TAG-MEASRESULTIDLEEUTRA-STOP +-- ASN1STOP + +``` + +| MeasResultIdleEUTRA field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------| +| carrierFreqEUTRA
Indicates the E-UTRA carrier frequency. | +| eutra-PhysCellId
Indicates the physical cell identity of an E-UTRA cell. | +| measIdleResultEUTRA
Idle/inactive measurement results for an E-UTRA cell. | +| measResultsPerCarrierListIdleEUTRA
List of idle/inactive measured results for the maximum number of reported E-UTRA carriers. | +| measResultsPerCellListIdleEUTRA
List of idle/inactive measured results for the maximum number of reported best cells for a given E-UTRA carrier. | + +#### — *MeasResultIdleNR* + +The IE *MeasResultIdleNR* covers the NR measurement results performed in RRC\_IDLE and RRC\_INACTIVE. + +#### *MeasResultIdleNR* information element + +``` +-- ASN1START +-- TAG-MEASRESULTIDLENR-START + +MeasResultIdleNR-r16 ::= SEQUENCE { + measResultServingCell-r16 SEQUENCE { + rsrp-Result-r16 RSRP-Range OPTIONAL, + rsrq-Result-r16 RSRQ-Range OPTIONAL, + resultsSSB-Indexes-r16 ResultsPerSSB-IndexList-r16 OPTIONAL + }, + measResultsPerCarrierListIdleNR-r16 SEQUENCE (SIZE (1.. maxFreqIdle-r16)) OF MeasResultsPerCarrierIdleNR-r16 OPTIONAL, + ... +} + +MeasResultsPerCarrierIdleNR-r16 ::= SEQUENCE { + carrierFreq-r16 ARFCN-ValueNR, + measResultsPerCellListIdleNR-r16 SEQUENCE (SIZE (1..maxCellMeasIdle-r16)) OF MeasResultsPerCellIdleNR-r16, + ... +} + +MeasResultsPerCellIdleNR-r16 ::= SEQUENCE { + physCellId-r16 PhysCellId, + measIdleResultNR-r16 SEQUENCE { + rsrp-Result-r16 RSRP-Range OPTIONAL, + rsrq-Result-r16 RSRQ-Range OPTIONAL, + resultsSSB-Indexes-r16 ResultsPerSSB-IndexList-r16 OPTIONAL + }, + ... +} +``` + +``` + +ResultsPerSSB-IndexList-r16 ::= SEQUENCE (SIZE (1.. maxNrofIndexesToReport)) OF ResultsPerSSB-IndexIdle-r16 +ResultsPerSSB-IndexIdle-r16 ::= SEQUENCE { + ssb-Index-r16 SSB-Index, + ssb-Results-r16 SEQUENCE { + ssb-RSRP-Result-r16 RSRP-Range + ssb-RSRQ-Result-r16 RSRQ-Range + } +} +-- TAG-MEASRESULTIDLENR-STOP +-- ASN1STOP + +``` + +| MeasResultIdleNR field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------| +| carrierFreq
Indicates the NR carrier frequency. | +| measIdleResultNR
Idle/inactive measurement results for an NR cell (optionally including beam level measurements). | +| measResultServingCell
Measured results of the serving cell (i.e., PCell) from idle/inactive measurements. | +| measResultsPerCellListIdleNR
List of idle/inactive measured results for the maximum number of reported best cells for a given NR carrier. | +| resultsSSB-Indexes
Beam level measurement results (indexes and optionally, beam measurements). | + +#### — ***MeasResultRxBTimeDiff*** + +The IE *MeasResultRxBTimeDiff* is used to provide Rx-Tx time difference measurement result. + +#### ***MeasResultRxBTimeDiff* information element** + +``` + +-- ASN1START +-- TAG-MEASRESULTRXBTIMEDIFF-START + +MeasResultRxBTimeDiff-r17 ::= SEQUENCE { + rxBTimeDiff-ue-r17 RxBTimeDiff-r17 OPTIONAL, + ... +} + +-- TAG-MEASRESULTRXBTIMEDIFF-STOP +-- ASN1STOP + +``` + +#### | | |---------------------------------------------------------| | MeasResultRxTxTimeDiff field descriptions | |---------------------------------------------------------| + +##### | | |-------------------------------| | rxTxTimeDiff-ue | |-------------------------------| + +| | +|-----------------------------------------------------------------------------------------------| +| indicates the Rx-Tx Time difference measurement at the UE (see clause 5.1.30, TS 38.215 [9]). | +|-----------------------------------------------------------------------------------------------| + +#### — ***MeasResultSCG-Failure*** + +The IE *MeasResultSCG-Failure* is used to provide information regarding failures detected by the UE in (NG)EN-DC and NR-DC. + +#### ***MeasResultSCG-Failure information element*** + +``` +-- ASN1START +-- TAG-MEASRESULTSCG-FAILURE-START + +MeasResultSCG-Failure ::= SEQUENCE { + measResultPerMOList MeasResultList2NR, + ... + [[ + locationInfo-r16 LocationInfo-r16 OPTIONAL + ]] +} + +MeasResultList2NR ::= SEQUENCE (SIZE (1..maxFreq)) OF MeasResult2NR + +-- TAG-MEASRESULTSCG-FAILURE-STOP +-- ASN1STOP +``` + +#### — ***MeasResultsSL*** + +The IE *MeasResultsSL* covers measured results for NR sidelink communication/discovery. + +#### ***MeasResultsSL information element*** + +``` +-- ASN1START +-- TAG-MEASRESULTSSL-START + +MeasResultsSL-r16 ::= SEQUENCE { + measResultsListSL-r16 CHOICE { + measResultNR-SL-r16 MeasResultNR-SL-r16, + ... + }, + ... +} + +MeasResultNR-SL-r16 ::= SEQUENCE { + measResultListCBR-NR-r16 SEQUENCE (SIZE (1.. maxNrofSL-PoolToMeasureNR-r16)) OF MeasResultCBR-NR-r16, + ... +} +``` + +``` + +} + +MeasResultCBR-NR-r16 ::= SEQUENCE { + sl-poolReportIdentity-r16 SL-ResourcePoolID-r16, + sl-CBR-ResultsNR-r16 SL-CBR-r16, + ... +} + +-- TAG-MEASRESULTSSL-STOP +-- ASN1STOP + +``` + +#### | | |------------------------------------------------| | MeasResultsSL field descriptions | |------------------------------------------------| + +##### | | |-------------------------------| | measResultNR-SL | |-------------------------------| + +| | +|-----------------------------------------------------------------------| +| Include the measured results for NR sidelink communication/discovery. | +|-----------------------------------------------------------------------| + +#### | | |--------------------------------------------------| | MeasResultNR-SL field descriptions | |--------------------------------------------------| + +##### | | |------------------------------------| | measResultListCBR-NR | |------------------------------------| + +| | +|------------------------------------------------------------------| +| CBR measurement results for NR sidelink communication/discovery. | +|------------------------------------------------------------------| + +##### | | |-------------------------------------| | sl-poolReportIdentity | |-------------------------------------| + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| The identity of the transmission resource pool which is corresponding to the sl-ResourcePoolID configured in a resource pool for NR sidelink communication/discovery. | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +## — *MeasSequence* + +The IE *MeasSequence* is used to configure a recommended sequence for intra/inter-RAT intra/inter-frequency measurement. + +#### ***MeasSequence information element*** + +``` + +-- ASN1START +-- TAG-MEASSEQUENCE-START + +MeasSequence-r18 ::= INTEGER (1..maxMeasSequence-r18) + +-- TAG-MEASSEQUENCE-STOP +-- ASN1STOP + +``` + +#### — *MeasTriggerQuantityEUTRA* + +The IE *MeasTriggerQuantityEUTRA* is used to configure the trigger quantity and reporting range for E-UTRA measurements. The RSRP, RSRQ and SINR ranges correspond to *RSRP-Range*, *RSRQ-Range* and *RS-SINR-Range* in TS 36.331 [10], respectively. + +#### ***MeasTriggerQuantityEUTRA* information element** + +``` + +-- ASN1START +-- TAG-MEASTRIGGERQUANTITYEUTRA-START + +MeasTriggerQuantityEUTRA ::= CHOICE { + rsrp RSRP-RangeEUTRA, + rsrq RSRQ-RangeEUTRA, + sinr SINR-RangeEUTRA +} + +RSRP-RangeEUTRA ::= INTEGER (0..97) +RSRQ-RangeEUTRA ::= INTEGER (0..34) +SINR-RangeEUTRA ::= INTEGER (0..127) + +-- TAG-MEASTRIGGERQUANTITYEUTRA-STOP +-- ASN1STOP + +``` + +#### — ***MeasWindowConfig*** + +The IE *MeasWindowConfig* specifies the effective measurement window configuration for inter-RAT E-UTRA measurement. + +#### ***MeasWindowConfig* information element** + +``` + +-- ASN1START +-- TAG-MEASWINDOWCONFIG-START + +MeasWindowConfig-r18 ::= SEQUENCE { + windowOffsetPeriodicity CHOICE { + periodicityMs40 INTEGER (0..39), + periodicityMs80 INTEGER (0..79), + ... + }, + windowDuration ENUMERATED {ms2, ms5, ms5dot5, spare1}, + ... +} + +-- TAG-MEASWINDOWCONFIG-STOP +-- ASN1STOP + +``` + +| MeasWindowConfig field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| windowDuration
Value windowDuration is the measurement window length in ms of effective measurement window. Value ms2 corresponds to 2 ms, value ms5 corresponds to 5 ms, and Value ms5dot5 corresponds to 5.5 ms. | +| windowOffsetPeriodicity
Indicates the periodicity and offset of effective measurement window. The choice determines the periodicity (periodicityMs40 for 40ms and periodicityMs80 for 80 ms). The field value indicates the offset in ms. | + +#### — *MobilityStateParameters* + +The IE *MobilityStateParameters* contains parameters to determine UE mobility state. + +#### ***MobilityStateParameters* information element** + +``` +-- ASN1START +-- TAG-MOBILITYSTATEPARAMETERS-START + +MobilityStateParameters ::= SEQUENCE{ + t-Evaluation ENUMERATED { + s30, s60, s120, s180, s240, spare3, spare2, spare1}, + t-HystNormal ENUMERATED { + s30, s60, s120, s180, s240, spare3, spare2, spare1}, + n-CellChangeMedium INTEGER (1..16), + n-CellChangeHigh INTEGER (1..16) +} + +-- TAG-MOBILITYSTATEPARAMETERS-STOP +-- ASN1STOP +``` + +| MobilityStateParameters field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| n-CellChangeHigh
The number of cell changes to enter high mobility state. Corresponds to $N_{CR\_H}$ in TS 38.304 [20]. | +| n-CellChangeMedium
The number of cell changes to enter medium mobility state. Corresponds to $N_{CR\_M}$ in TS 38.304 [20]. | +| t-Evaluation
The duration for evaluating criteria to enter mobility states. Corresponds to $T_{CRmax}$ in TS 38.304 [20]. Value in seconds, s30 corresponds to 30 s and so on. | +| t-HystNormal
The additional duration for evaluating criteria to enter normal mobility state. Corresponds to $T_{CRmaxHyst}$ in TS 38.304 [20]. Value in seconds, value s30 corresponds to 30 seconds and so on. | + +#### — *MRB-Identity* + +The IE *MRB-Identity* is used to identify a multicast MRB used by a UE. + +#### *MRB-Identity* information element + +``` +-- ASN1START +-- TAG-MRB-IDENTITY-START + +MRB-Identity-r17 ::= INTEGER (1..512) + +-- TAG-MRB-IDENTITY-STOP +-- ASN1STOP +``` + +#### — *MsgA-ConfigCommon* + +The IE *MsgA-ConfigCommon* is used to configure the PRACH and PUSCH resource for transmission of MsgA in 2-step random access type procedure. + +``` +-- ASN1START +-- TAG-MSGACONFIGCOMMON-START + +MsgA-ConfigCommon-r16 ::= SEQUENCE { + rach-ConfigCommonTwoStepRA-r16 RACH-ConfigCommonTwoStepRA-r16, + msgA-PUSCH-Config-r16 MsgA-PUSCH-Config-r16 OPTIONAL --Cond InitialBWPConfig +} + +-- TAG-MSGACONFIGCOMMON-STOP +-- ASN1STOP +``` + +#### *MsgA-ConfigCommon* field descriptions + +##### ***msgA-PUSCH-Config*** + +Configuration of cell-specific MsgA PUSCH parameters which the UE uses for contention-based MsgA PUSCH transmission of this BWP. If the field is not configured for the selected UL BWP, the UE shall use the MsgA PUSCH configuration of initial UL BWP. + +##### ***rach-ConfigCommonTwoStepRA*** + +Configuration of cell specific random access parameters which the UE uses for contention based and contention free 2-step random access type procedure as well as for 2-step RA type contention based beam failure recovery in this BWP. + +| Conditional Presence | Explanation | +|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| InitialBWPConfig | The field is mandatory present when MsgA-ConfigCommon is configured for the initial uplink BWP, or when MsgA-ConfigCommon is configured for a non-initial uplink BWP and MsgA-ConfigCommon is not configured for the initial uplink BWP, otherwise the field is optionally present, Need S. | + +#### – MsgA-PUSCH-Config + +The IE *MsgA-PUSCH-Config* is used to specify the PUSCH allocation for MsgA in 2-step random access type procedure. + +#### *MsgA-PUSCH-Config* information element + +``` + +-- ASN1START +-- TAG-MSGA-PUSCH-CONFIG-START + +MsgA-PUSCH-Config-r16 ::= + SEQUENCE { + msgA-PUSCH-ResourceGroupA-r16 MsgA-PUSCH-Resource-r16 OPTIONAL, -- Cond InitialBWConfig + msgA-PUSCH-ResourceGroupB-r16 MsgA-PUSCH-Resource-r16 OPTIONAL, -- Cond GroupBConfigured + msgA-TransformPrecoder-r16 ENUMERATED {enabled, disabled} OPTIONAL, -- Need R + msgA-DataScramblingIndex-r16 INTEGER (0..1023) OPTIONAL, -- Need S + msgA-DeltaPreamble-r16 INTEGER (-1..6) OPTIONAL -- Need R + } + +MsgA-PUSCH-Resource-r16 ::= + SEQUENCE { + msgA-MCS-r16 INTEGER (0..15), + nrofSlotsMsgA-PUSCH-r16 INTEGER (1..4), + nrofMsgA-PO-PerSlot-r16 ENUMERATED {one, two, three, six}, + msgA-PUSCH-TimeDomainOffset-r16 INTEGER (1..32), + msgA-PUSCH-TimeDomainAllocation-r16 INTEGER (1..maxNrofUL-Allocations) OPTIONAL, -- Need S + startSymbolAndLengthMsgA-PO-r16 INTEGER (0..127) OPTIONAL, -- Need S + mappingTypeMsgA-PUSCH-r16 ENUMERATED {typeA, typeB} OPTIONAL, -- Need S + guardPeriodMsgA-PUSCH-r16 INTEGER (0..3) OPTIONAL, -- Need R + guardBandMsgA-PUSCH-r16 INTEGER (0..1), + frequencyStartMsgA-PUSCH-r16 INTEGER (0..maxNrofPhysicalResourceBlocks-1), + nrofPRBs-PerMsgA-PO-r16 INTEGER (1..32), + nrofMsgA-PO-FDM-r16 ENUMERATED {one, two, four, eight}, + msgA-IntraSlotFrequencyHopping-r16 ENUMERATED {enabled} OPTIONAL, -- Need R + msgA-HoppingBits-r16 BIT STRING (SIZE(2)) OPTIONAL, -- Cond FreqHopConfigured + msgA-DMRS-Config-r16 MsgA-DMRS-Config-r16, + nrofDMRS-Sequences-r16 INTEGER (1..2), + msgA-Alpha-r16 ENUMERATED {alpha0, alpha04, alpha05, alpha06, + alpha07, alpha08, alpha09, alpha1} OPTIONAL, -- Need S + interlaceIndexFirstPO-MsgA-PUSCH-r16 INTEGER (1..10) OPTIONAL, -- Need R + nrofInterlacesPerMsgA-PO-r16 INTEGER (1..10) OPTIONAL, -- Need R + ... + } + +MsgA-DMRS-Config-r16 ::= + SEQUENCE { + msgA-DMRS-AdditionalPosition-r16 ENUMERATED {pos0, pos1, pos3} OPTIONAL, -- Need S + msgA-MaxLength-r16 ENUMERATED {len2} OPTIONAL, -- Need S + msgA-PUSCH-DMRS-CDM-Group-r16 INTEGER (0..1) OPTIONAL, -- Need S + msgA-PUSCH-NrofPorts-r16 INTEGER (0..1) OPTIONAL, -- Need S + msgA-ScramblingID0-r16 INTEGER (0..65535) OPTIONAL, -- Need S + msgA-ScramblingID1-r16 INTEGER (0..65535) OPTIONAL -- Need S + } + +``` + +``` +-- TAG-MSGA-PUSCH-CONFIG-STOP +-- ASN1STOP +``` + +| MsgA-PUSCH-Config field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| msgA-DataScramblingIndex
Identifier used to initiate data scrambling ( c_init ) for msgA PUSCH. If the field is absent the UE applies the value Physical cell ID ( physCellID ). | +| msgA-DeltaPreamble
Power offset of msgA PUSCH relative to the preamble received target power. Actual value = field value * 2 [dB] (see TS 38.213 [13], clause 7.1). | +| msgA-PUSCH-ResourceGroupA
MsgA PUSCH resources that the UE shall use when performing MsgA transmission using preambles group A. If field is not configured for the selected UL BWP, the UE shall use the MsgA PUSCH configuration for group A of initial UL BWP or (e)RedCap-specific initial UL BWP (if configured) for (e)RedCap UEs. | +| msgA-PUSCH-ResourceGroupB
MsgA PUSCH resources that the UE shall use when performing MsgA transmission using preambles group B. | +| msgA-TransformPrecoder
Enables or disables the transform precoder for MsgA transmission (see clause 6.1.3 of TS 38.214 [19]). | + +| MsgA-PUSCH-Resource field descriptions | | +|-----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| guardBandMsgA-PUSCH | PRB-level guard band between FDMed PUSCH occasions (see TS 38.213 [13], clause 8.1A). If interlaced PUSCH is configured, value 0 is applied. | +| guardPeriodMsgA-PUSCH | Guard period between PUSCH occasions in the unit of symbols (see TS 38.213 [13], clause 8.1A). | +| frequencyStartMsgA-PUSCH | Offset of lowest PUSCH occasion in frequency domain with respect to PRB 0 (see TS 38.213 [13], clause 8.1A). | +| interlaceIndexFirstPO-MsgA-PUSCH | Interlace index of the first PUSCH occasion in frequency domain if interlaced PUSCH is configured. For 30kHz SCS only the integers 1, 2, 3, 4, 5 are applicable (see TS 38.213 [13], clause 8.1A). | +| mappingTypeMsgA-PUSCH | PUSCH mapping type A or B. If the field is absent, the UE shall use the parameter msgA-PUSCH-TimeDomainAllocation (see TS 38.213 [13], clause 8.1A). | +| msgA-Alpha | Dedicated alpha value for MsgA PUSCH. If the field is absent, the UE shall use the value of msg3-Alpha if configured, else UE applies value 1 (see TS 38.213 [13], clause 7.1.1). | +| msgA-DMRS-Config | DMRS configuration for msgA PUSCH (see TS 38.213 [13], clause 8.1A and TS 38.214 [19] clause 6.2.2). | +| msgA-HoppingBits | Value of hopping bits to indicate which frequency offset to be used for second hop. See Table 8.3-1 in TS 38.213 [13]. | +| msgA-IntraSlotFrequencyHopping | Intra-slot frequency hopping per PUSCH occasion (see TS 38.213 [13], clause 8.1A). | +| msgA-MCS | Indicates the MCS index for msgA PUSCH from the Table 6.1.4.1-1 for DFT-s-OFDM and Table 5.1.3.1-1 for CP-OFDM in TS 38.214 [19]. | +| msgA-PUSCH-TimeDomainAllocation | Indicates a combination of start symbol and length and PUSCH mapping type from the TDRA table ( PUSCH-TimeDomainResourceAllocationList if provided in PUSCH-ConfigCommon , or else the default Table 6.1.2.1.1-2 in 38.214 [19] is used if pusch-TimeDomainAllocationList is not provided in PUSCH-ConfigCommon ). The parameter K2 in the table is not used for msgA PUSCH. The network configures one of msgA-PUSCH-TimeDomainAllocation and startSymbolAndLengthMsgA-PO , but not both. If the field is absent, the UE shall use the value of startSymbolAndLengthMsgA-PO . | +| msgA-PUSCH-TimeDomainOffset | A single time offset with respect to the start of each PRACH slot (with at least one valid RO), counted as the number of slots (based on the numerology of active UL BWP). See TS 38.213 [13], clause 8.1A. | +| nrofDMRS-Sequences | Number of DMRS sequences for MsgA PUSCH for CP-OFDM. In case of single PUSCH configuration or if the DMRS symbols of multiple configurations are not overlapped, if the DMRS resources configured in one PUSCH occasion is no larger than 8 (for len2 ) or 4 (for len1 ), then only DMRS port is configured. | +| nrofInterlacesPerMsgA-PO | Number of consecutive interlaces per PUSCH occasion if interlaced PUSCH is configured. For 30kHz SCS only the integers 1, 2, 3, 4, 5 are applicable (see TS 38.213 [13], clause 8.1A). | +| nrofMsgA-PO-FDM | The number of msgA PUSCH occasions FDMed in one time instance (see TS 38.213 [13], clause 8.1A). | +| nrofMsgA-PO-PerSlot | Number of time domain PUSCH occasions in each slot. PUSCH occasions including guard period are contiguous in time domain within a slot (see TS 38.213 [13], clause 8.1A). | +| nrofPRBs-PerMsgA-PO | Number of PRBs per PUSCH occasion (see TS 38.213 [13], clause 8.1A). | + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| nrofSlotsMsgA-PUSCH
Number of slots (in active UL BWP numerology) containing one or multiple PUSCH occasions, each slot has the same time domain resource allocation (see TS 38.213 [13], clause 8.1A). | +| startSymbolAndLengthMsgA-PO
An index giving valid combinations of start symbol, length and mapping type as start and length indicator (SLIV) for the first msgA PUSCH occasion, for RRC_CONNECTED UEs in non-initial BWP as described in TS 38.214 [19] clause 6.1.2. The network configures the field so that the allocation does not cross the slot boundary. The number of occupied symbols excludes the guard period. If the field is absent, the UE shall use the value in msgA-PUSCH-TimeDomainAllocation (see TS 38.213 [13], clause 8.1A). The network configures one of msgA-PUSCH-TimeDomainAllocation and startSymbolAndLengthMsgA-PO , but not both. If the field is absent, the UE shall use the value of msgA-PUSCH-TimeDomainAllocation . | + +| MsgA-DMRS-Config field descriptions | | +|--------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| msgA-DMRS-AdditionalPosition | Indicates the position for additional DM-RS. If the field is absent, the UE applies value pos2 . | +| msgA-MaxLength | indicates single-symbol or double-symbol DMRS. If the field is absent, the UE applies value len1 . | +| msgA-PUSCH-DMRS-CDM-Group | 1-bit indication of indices of CDM group(s). If the field is absent, then both CDM groups are used. | +| msgA-PUSCH-NrofPorts | 0 indicates 1 port per CDM group, 1 indicates 2 ports per CDM group. If the field is absent then 4 ports per CDM group are used (see TS 38.213 [13], clause 8.1A). | +| msgA-ScramblingID0 | UL DMRS scrambling initialization for CP-OFDM. If the field is absent the UE applies the value Physical cell ID ( physCellID ). | +| msgA-ScramblingID1 | UL DMRS scrambling initialization for CP-OFDM. If the field is absent the UE applies the value Physical cell ID ( physCellID ). | + +| Conditional Presence | Explanation | +|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| FreqHopConfigured | This field is mandatory present when the field msgA-IntraSlotFrequencyHopping is configured. Otherwise, the field is absent. | +| GroupBConfigured | The field is mandatory present if groupB-ConfiguredTwoStepRA is configured in RACH-ConfigCommonTwoStepRA , otherwise the field is absent. | +| InitialBWPConfig | The field is mandatory present when MsgA-ConfigCommon is configured for the initial uplink BWP, or when MsgA-ConfigCommon is configured for a non-initial uplink BWP and MsgA-ConfigCommon is not configured for the initial uplink BWP, otherwise the field is optionally present, Need S. | + +#### MultiFrequencyBandListNR + +The IE *MultiFrequencyBandListNR* is used to configure a list of one or multiple NR frequency bands. + +#### MultiFrequencyBandListNR information element + +``` +-- ASN1START +-- TAG-MULTIFREQUENCYBANDLISTNR-START +``` + +``` +MultiFrequencyBandListNR ::= SEQUENCE (SIZE (1..maxNrofMultiBands)) OF FreqBandIndicatorNR +-- TAG-MULTIFREQUENCYBANDLISTNR-STOP +-- ASN1STOP +``` + +##### MultiFrequencyBandListNR-SIB + +The IE *MultiFrequencyBandListNR-SIB* indicates the list of frequency bands, for which cell (re-)selection parameters are common, and a list of *additionalPmax* and *additionalSpectrumEmission*. + +##### MultiFrequencyBandListNR-SIB information element + +``` +-- ASN1START +-- TAG-MULTIFREQUENCYBANDLISTNR-SIB-START + +MultiFrequencyBandListNR-SIB ::= SEQUENCE (SIZE (1.. maxNrofMultiBands)) OF NR-MultiBandInfo +NR-MultiBandInfo ::= SEQUENCE { + freqBandIndicatorNR FreqBandIndicatorNR OPTIONAL, -- Cond OptULNotSIB2 + nr-NS-PmaxList NR-NS-PmaxList OPTIONAL -- Need S +} + +MultiFrequencyBandListNR-SIB-v1760 ::= SEQUENCE (SIZE (1.. maxNrofMultiBands)) OF NR-MultiBandInfo-v1760 +NR-MultiBandInfo-v1760 ::= SEQUENCE { + nr-NS-PmaxList-v1760 NR-NS-PmaxList-v1760 OPTIONAL -- Need S +} + +MultiFrequencyBandListNR-Aerial-SIB-r18 ::= SEQUENCE (SIZE (1.. maxNrofMultiBands)) OF NR-MultiBandInfoAerial-r18 +NR-MultiBandInfoAerial-r18 ::= SEQUENCE { + freqBandIndicatorNR-Aerial-r18 FreqBandIndicatorNR OPTIONAL, -- Cond OptULNotSIB2 + nr-NS-PmaxListAerial-r18 NR-NS-PmaxListAerial-r18 OPTIONAL -- Need S +} + +-- TAG-MULTIFREQUENCYBANDLISTNR-SIB-STOP +-- ASN1STOP +``` + +| NR-MultiBandInfo field descriptions | | +|--------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| freqBandIndicatorNR | Provides an NR frequency band number as defined in TS 38.101-1 [15], TS 38.101-2 [39], table 5.2-1, and TS 38.101-5 [75], table 5.2.2-1. | +| freqBandIndicatorNR-Aerial | Provides an NR frequency band number for aerial UE(s), as defined in TS 38.101-1 [15], TS 38.101-2 [39], table 5.2-1, and TS 38.101-5 [75], table 5.2.2-1. | +| nr-NS-PmaxList | Provides a list of additionalPmax and additionalSpectrumEmission values. If the field is absent the UE uses value 0 for the additionalSpectrumEmission (see TS 38.101-1 [15] table 6.2.3.1-1A, TS 38.101-2 [39], table 6.2.3.1-2, and TS 38.101-5 [75], table 6.2.3.1-1A). This field is ignored by IAB-MT, the IAB-MT applies output power and emissions requirements, as specified in TS 38.174 [63]. If nr-NS-PmaxList-v1760 is present, it shall contain the same number of entries, listed in the same order as in nr-NS-PmaxList (without suffix). | +| nr-NS-PmaxListAerial | Provides a list of additionalPmax and additionalSpectrumEmission values for aerial UE(s). If the field is absent, the value indicated by the corresponding field within frequencyBandList for the corresponding NR frequency band number applies, if present. Otherwise (i.e. the field is not present for the corresponding NR frequency band number in any of the nr-NS-PmaxList , nr-NS-PmaxList-v1760 or nr-NS-PmaxListAerial ), the UE uses value 0 for the additionalSpectrumEmission (see TS 38.101-1 [15] table 6.2.3.1-1A, TS 38.101-2 [39], table 6.2.3.1-2, and TS 38.101-5 [75], table 6.2.3.1-1A). This field is ignored by IAB-MT, the IAB-MT applies output power and emissions requirements, as specified in TS 38.174 [63]. | + +| Conditional Presence | Explanation | +|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| OptULNotSIB2 | The field is absent for SIB2 and is mandatory present in SIB4 and frequencyInfoDL-SIB . Otherwise, if the field is absent in frequencyInfoUL-SIB in UplinkConfigCommonSIB , the UE will use the frequency band indicated in frequencyInfoDL-SIB in DownlinkConfigCommonSIB . | + +#### — MUSIM-GapConfig + +The IE *MUSIM-GapConfig* specifies the MUSIM gap configuration and controls setup/release of MUSIM gaps. + +#### ***MUSIM-GapConfig* information element** + +``` +-- ASN1START +-- TAG-MUSIM-GAPCONFIG-START + +MUSIM-GapConfig-r17 ::= + musim-GapToReleaseList-r17 SEQUENCE { + musim-GapToAddModList-r17 SEQUENCE (SIZE (1..3)) OF MUSIM-GapId-r17 OPTIONAL, -- Need N + musim-AperiodicGap-r17 SEQUENCE (SIZE (1..3)) OF MUSIM-Gap-r17 OPTIONAL, -- Need N + .... MUSIM-GapInfo-r17 OPTIONAL, -- Need N + [[ + musim-GapPriorityToAddModList-r18 SEQUENCE (SIZE (1..3)) OF GapPriority-r17 OPTIONAL, -- Need N + musim-GapKeep-r18 ENUMERATED {true} OPTIONAL -- Need R + ]] +} +MUSIM-Gap-r17 ::= SEQUENCE { + musim-GapId-r17 MUSIM-GapId-r17, + musim-GapInfo-r17 MUSIM-GapInfo-r17 +``` + +``` + +} + +-- TAG-MUSIM-GAPCONFIG-STOP +-- ASN1STOP + +``` + +#### ***MUSIM-GapConfig* field descriptions** + +##### ***musim-AperiodicGap*** + +Indicates the MUSIM aperiodic gap as specified in TS 38.133 [14] clause 9.1.10. If UE indicates the *musim-Starting-SFN-AndSubframe* when requesting aperiodic gap the network can only configure the aperiodic gap with the same start point or no aperiodic gap. If the field *musim-Starting-SFN-AndSubframe* is absent for aperiodic gap, network can configure any timing as the starting point for aperiodic gap or configure no aperiodic gap. + +##### ***musim-GapInfo*** + +Indicates the values for *musim-GapLength* and *musim-GapRepetitionAndOffset*. When network provides periodic gap, network always signals the *musim-GapLength* and *musim-GapRepetitionAndOffset* as indicated by the UE's preferred MUSIM gap configuration. + +##### ***musim-GapKeep*** + +Indicates the UE is allowed to use "keep solution" for collided MUSIM periodic gaps. If "keep solution" is not granted, priority based solution is used as fallback solution) as specified in TS 38.133[14]. + +##### ***musim-GapPriorityToAddModList*** + +Indicates the priority of MUSIM periodic gap(s). + +If the network includes *musim-GapPriorityToAddModList-r18*, it includes the same number of entries, and listed in the same order, as in *musim-GapToAddModList-r17*. + +For the priority of MUSIM aperiodic gap, the MUSIM aperiodic gap is always kept (not dropped) from UE perspective in case of collisions with other gaps (i.e. all gaps including MUSIM gaps, etc). + +##### ***musim-GapToAddModList*** + +List of MUSIM periodic gap patterns to add or modify. + +##### ***musim-GapToReleaseList*** + +List of MUSIM periodic gap patterns to release. + +#### — ***MUSIM-GapId*** + +The IE *MUSIM-GapId* is used to identify UE periodic MUSIM gap(s) to add, modify or release. + +#### ***MUSIM-GapId* information element** + +``` + +-- ASN1START +-- TAG-MUSIM-GAPID-START + +MUSIM-GapId-r17 ::= INTEGER (0..2) + +-- TAG-MUSIM-GAPID-STOP +-- ASN1STOP + +``` + +#### — *MUSIM-GapInfo* + +The IE *MUSIM-GapInfo* is used to indicate MUSIM gap parameters. + +#### *MUSIM-GapInfo* information element + +``` +-- ASN1START +-- TAG-MUSIM-GAPINFO-START + +MUSIM-GapInfo-r17 ::= SEQUENCE { + musim-Starting-SFN-AndSubframe-r17 MUSIM-Starting-SFN-AndSubframe-r17 OPTIONAL, -- Cond aperiodic + musim-GapLength-r17 ENUMERATED {ms3, ms4, ms6, ms10, ms20} OPTIONAL, -- Cond gapSetup + musim-GapRepetitionAndOffset-r17 CHOICE { + ms20-r17 INTEGER (0..19), + ms40-r17 INTEGER (0..39), + ms80-r17 INTEGER (0..79), + ms160-r17 INTEGER (0..159), + ms320-r17 INTEGER (0..319), + ms640-r17 INTEGER (0..639), + ms1280-r17 INTEGER (0..1279), + ms2560-r17 INTEGER (0..2559), + ms5120-r17 INTEGER (0..5119), + ... + } +} +OPTIONAL -- Cond periodic + +MUSIM-Starting-SFN-AndSubframe-r17 ::= SEQUENCE { + starting-SFN-r17 INTEGER (0..1023), + startingSubframe-r17 INTEGER (0..9) +} + +-- TAG-MUSIM-GAPINFO-STOP +-- ASN1STOP +``` + +| MUSIM-GapInfo field descriptions | | +|----------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| musim-GapLength | Indicates the length of the UE's MUSIM gap as specified in TS 38.133 [14] clause 9.1.10. This field is mandatory present for both periodic gap and aperiodic gap preference indication. | +| musim-GapRepetitionAndOffset | Indicates the gap repetition period in ms and gap offset in number of subframes for the periodic MUSIM gap as specified in TS 38.133 [14] clause 9.1.10. This field is mandatory present for the periodic MUSIM gap preference indication. | +| musim-Starting-SFN-AndSubframe | Indicates gap starting position for the aperiodic MUSIM gap. This field is optionally present for the aperiodic MUSIM gap preference indication. | +| starting-SFN | Indicates gap starting SFN number for the aperiodic MUSIM gap. | +| startingSubframe | Indicates gap starting subframe number for the aperiodic MUSIM gap. | + +| Conditional Presence | Explanation | +|-----------------------------|---------------------------------------------------------------------------------------------------------------------------| +| aperiodic | This field is mandatory present in case of aperiodic MUSIM gap configuration. Otherwise it is absent. | +| gapSetup | The field is mandatory present upon configuration of a new MUSIM gap. The field is optionally present, Need M, otherwise. | +| periodic | This field is mandatory present in case of periodic MUSIM gap configuration. Otherwise it is absent. | + +#### — *N3C-IndirectPathConfigRelay* + +The IE *N3C-IndirectPathConfigRelay* indicates the N3C indirect path related configuration used by N3C relay UE in MP. + +#### ***N3C-IndirectPathConfigRelay* information element** + +``` +-- ASN1START +-- TAG-N3C-INDIRECTPATHCONFIGRELAY-START + +N3C-IndirectPathConfigRelay-r18 ::= SEQUENCE { + n3c-MappingToReleaseList-r18 SEQUENCE (SIZE (1..maxLC-ID)) OF SL-RemoteUE-RB-Identity-r17 OPTIONAL, -- Need N + n3c-MappingToAddModList-r18 SEQUENCE (SIZE (1..maxLC-ID)) OF N3C-MappingToAddMod-r18 OPTIONAL, -- Need N + ... +} + +N3C-MappingToAddMod-r18 ::= SEQUENCE { + n3c-RemoteUE-RB-Identity-r18 SL-RemoteUE-RB-Identity-r17, + n3c-RLC-ChannelUu-r18 Uu-RelayRLC-ChannelID-r17 + ... +} + +-- TAG-N3C-INDIRECTPATHCONFIGRELAY-STOP +-- ASN1STOP +``` + +| N3C-IndirectPathConfigRelay field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| n3c-MappingToAddModList
Indicates the list of mappings between the bearer identity of the N3C remote UE and the Uu RLC channel to be added or modified. The Uu RLC channel is associated to only one N3C remote UE's end-to-end bearer. | +| n3c-MappingToReleaseList
Indicates the list of mappings between the bearer identity of the N3C remote UE and the Uu RLC channel to be released. | + +#### – ***N3C-IndirectPathAddChange*** + +The IE *N3C-IndirectPathAddChange* indicates the N3C indirect path related configuration used by N3C remote UE. + +#### ***N3C-IndirectPathAddChange* information element** + +``` +-- ASN1START +-- TAG-N3C-INDIRECTPATHADDCHANGE-START + +N3C-IndirectPathAddChange-r18 ::= SEQUENCE { + n3c-RelayIdentification-r18 SEQUENCE { + n3c-CellGlobalId-r18 SEQUENCE { + n3c-PLMN-Id-r18 PLMN-Identity, + n3c-CellIdentity-r18 CellIdentity + }, + n3c-C-RNTI-r18 RNTI-Value + } + ... +} +OPTIONAL, -- Cond N3CIndirectPathAddChange + +-- TAG-N3C-INDIRECTPATHADDCHANGE-STOP +-- ASN1STOP +``` + +| N3C-IndirectPathAddChange field descriptions | +|-----------------------------------------------------------------------------------------| +| n3c-RelayIdentification
Indicates the NCGI and C-RNTI of N3C relay UE. | + +| Conditional Presence | Explanation | +|---------------------------------|-------------------------------------------------------------------------------------------------------| +| N3CIndirectPathAddChange | The field is mandatory present in case of N3C indirect path addition/change. Otherwise, it is absent. | + +#### – ***NCR-AperiodicFwdConfig*** + +The IE *NCR-AperiodicFwdConfig* is used to configure a list of aperiodic forwarding time resources for NCR-Fwd access link. + +#### **NCR-AperiodicFwdConfig information element** + +``` + +-- ASN1START +-- TAG-NCR-APERIODICFWDCONFIG-START + +NCR-AperiodicFwdConfig-r18 ::= SEQUENCE { + aperiodicFwdTimeRsrcToAddModList-r18 SEQUENCE (SIZE (1..maxNrofAperiodicFwdTimeResource-r18)) OF NCR-AperiodicFwdTimeResource-r18 + OPTIONAL, -- Need N + aperiodicFwdTimeRsrcToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofAperiodicFwdTimeResource-r18)) OF NCR-AperiodicFwdTimeResourceId-r18 + OPTIONAL, -- Need N + referenceSCS-r18 SubcarrierSpacing + OPTIONAL, -- Need M + aperiodicBeamFieldWidth-r18 INTEGER (1..6) + OPTIONAL, -- Need M + numberOfFields-r18 INTEGER (1..32) + OPTIONAL, -- Need M + ... +} + +NCR-AperiodicFwdTimeResource-r18 ::= SEQUENCE { + aperiodicFwdTimeRsrcId-r18 NCR-AperiodicFwdTimeResourceId-r18, + slotOffsetAperiodic-r18 INTEGER (0..14), + symbolOffset-r18 INTEGER (0..maxNrofSymbols-1), + durationInSymbols-r18 INTEGER (1..28) +} + +NCR-AperiodicFwdTimeResourceId-r18 ::= INTEGER (0..maxNrofAperiodicFwdTimeResource-1-r18) + +-- TAG-NCR-APERIODICFWDCONFIG-STOP +-- ASN1STOP + +``` + +#### **NCR-AperiodicFwdConfig field descriptions** + +| | | +|------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| aperiodicBeamFieldWidth | Indicates the bitwidth of each beam index field in DCI carrying aperiodic beam indication. | +| aperiodicFwdTimeRsrcToAddModList | List of aperiodic forwarding time resources to be added or modified. | +| aperiodicFwdTimeRsrcToReleaseList | List of aperiodic forwarding time resources to be released. | +| durationInSymbols | Indicates the time duration in number of symbols. | +| numberOfFields | Indicates the number of time resource fields in DCI carrying aperiodic beam indication. | +| referenceSCS | Indicates the reference subcarrier spacing for all the time resources in the list. Only values kHz15 , kHz30 , kHz60 , kHz120 and kHz240 are applicable. | +| slotOffsetAperiodic | Indicates the slot offset used to define the start slot of aperiodic time resource. | +| symbolOffset | Indicates the symbol offset in one slot. | + +#### — *NCR-FwdConfig* + +The IE *NCR-FwdConfig* contains configuration related to periodic, aperiodic and semi-persistent beam indication for NCR-Fwd access link. + +#### *NCR-FwdConfig* information element + +``` +-- ASN1START +-- TAG-NCR-FWDCONFIG-START + +NCR-FwdConfig-r18 ::= + SEQUENCE { + periodicFwdRsrcSetToAddModList-r18 SEQUENCE (SIZE (1..maxNrofPeriodicFwdResourceSet-r18)) OF NCR-PeriodicFwdResourceSet-r18 + OPTIONAL, -- Need N + periodicFwdRsrcSetToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofPeriodicFwdResourceSet-r18)) OF NCR-PeriodicFwdResourceSetId-r18 + OPTIONAL, -- Need N + aperiodicFwdConfig-r18 NCR-AperiodicFwdConfig-r18 + OPTIONAL, -- Need N + semiPersistentFwdRsrcSetToAddModList-r18 SEQUENCE (SIZE (1..maxNrofSemiPersistentFwdResourceSet-r18)) OF + NCR-SemiPersistentFwdResourceSet-r18 + OPTIONAL, -- Need N + semiPersistentFwdRsrcSetToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofSemiPersistentFwdResourceSet-r18)) OF + NCR-SemiPersistentFwdResourceSetId-r18 + OPTIONAL, -- Need N + ... + } + +-- TAG-NCR-FWDCONFIG-STOP +-- ASN1STOP +``` + +#### *NCR-FwdConfig* field descriptions + +| | | +|-----------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| aperiodicFwdConfig | Aperiodic time resource configuration for beam indication for NCR. The configuration includes a list of time domain resources that can be selected for aperiodic forwarding. | +| periodicFwdRsrcSetToAddModList | List of periodic forwarding resource configurations to be added or modified. | +| periodicFwdRsrcSetToReleaseList | List of periodic forwarding resource configurations to be released. | +| semiPersistentFwdRsrcSetToAddModList | List of semi-persistent forwarding resource configurations to be added or modified. | +| semiPersistentFwdRsrcSetToReleaseList | List of semi-persistent forwarding resource configurations to be released. | + +#### — *NCR-PeriodicityAndOffset* + +The IE *NCR-PeriodicityAndOffset* is used to indicate the periodicity (in slot or ms) and offset (in slot) for periodic forwarding resource and semi-persistent forwarding resource. + +#### *NCR-PeriodicityAndOffset* information element + +``` +-- ASN1START +``` + +``` +-- TAG-NCR-PERIODICITYANDOFFSET-START + +NCR-PeriodicityAndOffset-r18 ::= CHOICE { + slot NCR-SlotPeriodicityAndSlotOffset-r18, + ms NCR-MsPeriodicityAndSlotOffset-r18 +} + +NCR-SlotPeriodicityAndSlotOffset-r18 ::= CHOICE { + sl1 NULL, + sl2 INTEGER (0..1), + sl4 INTEGER (0..3), + sl5 INTEGER (0..4), + sl8 INTEGER (0..7), + sl10 INTEGER (0..9), + sl16 INTEGER (0..15), + sl20 INTEGER (0..19), + sl32 INTEGER (0..31), + sl40 INTEGER (0..39), + sl64 INTEGER (0..63), + sl80 INTEGER (0..79), + sl128 INTEGER (0..127), + sl160 INTEGER (0..159), + sl256 INTEGER (0..255), + sl320 INTEGER (0..319), + sl512 INTEGER (0..511), + sl640 INTEGER (0..639), + sl1024 INTEGER (0..1023), + sl1280 INTEGER (0..1279), + sl2560 INTEGER (0..2559), + sl5120 INTEGER (0..5119), + sl10240 INTEGER (0..10239), + ... +} + +NCR-MsPeriodicityAndSlotOffset-r18 ::= CHOICE { + ms1 INTEGER (0..15), + ms2 INTEGER (0..31), + ms4 INTEGER (0..63), + ms5 INTEGER (0..79), + ms8 INTEGER (0..127), + ms10 INTEGER (0..159), + ms16 INTEGER (0..255), + ms20 INTEGER (0..319), + ms32 INTEGER (0..511), + ms40 INTEGER (0..639), + ms64 INTEGER (0..1023), + ms80 INTEGER (0..1279), + ms128 INTEGER (0..2047), + ms160 INTEGER (0..2559), + ms256 INTEGER (0..4095), + ms320 INTEGER (0..5119), +} +``` + +``` + +ms512 INTEGER(0..8191), +ms640 INTEGER(0..10239), +ms1024 INTEGER(0..16383), +ms1280 INTEGER(0..20479), +ms2560 INTEGER(0..40959), +ms5120 INTEGER(0..81919), +ms10240 INTEGER(0..163839), +... +} + +-- TAG-NCR-PERIODICITYANDOFFSET-STOP +-- ASN1STOP + +``` + +#### – *NCR-PeriodicFwdResourceSet* + +The IE *NCR-PeriodicFwdResourceSet* is used to configure a list of periodic forwarding resources for NCR-Fwd access link. Each periodic forwarding configuration includes a list of periodic forwarding resources, a common periodicity and a common reference SCS. + +#### *NCR-PeriodicFwdResourceSet* information element + +``` + +-- ASN1START +-- TAG-NCR-PERIODICFWDRESOURCESET-START + +NCR-PeriodicFwdResourceSet-r18 ::= SEQUENCE { + periodicFwdRsrcSetId-r18 NCR-PeriodicFwdResourceSetId-r18, + periodicFwdRsrcToAddModList-r18 SEQUENCE (SIZE (1..maxNrofPeriodicFwdResource-r18)) OF NCR-PeriodicFwdResource-r18 + OPTIONAL, -- Need N + periodicFwdRsrcToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofPeriodicFwdResource-r18)) OF NCR-PeriodicFwdResourceId-r18 + OPTIONAL, -- Need N + referenceSCS-r18 SubcarrierSpacing + OPTIONAL, -- Need M + priorityFlag-r18 ENUMERATED {true} + OPTIONAL, -- Need R + ... +} + +NCR-PeriodicFwdResource-r18 ::= SEQUENCE { + periodicFwdRsrcId-r18 NCR-PeriodicFwdResourceId-r18, + beamIndex-r18 INTEGER (0..63), + periodicTimeRsrc-r18 SEQUENCE { + periodicityAndOffset-r18 NCR-PeriodicityAndOffset-r18, + symbolOffset-r18 INTEGER (0..maxNrofSymbols-1), + durationInSymbols-r18 INTEGER (1..112) + } +} + +NCR-PeriodicFwdResourceId-r18 ::= INTEGER (0..maxNrofPeriodicFwdResource-1-r18) + +-- TAG-NCR-PERIODICFWDRESOURCESET-STOP +-- ASN1STOP + +``` + +| NCR-PeriodicFwdResourceSet field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| beamIndex
Indicates the logical beam index for NCR-Fwd access link. NCR-Fwd is assumed to be ON over the indicated time domain resource if there is beam indication. | +| durationInSymbols
Indicates the time duration in number of symbols. | +| periodicFwdRsrcToAddModList
List of periodic forwarding resources to be added or modified. | +| periodicFwdRsrcToReleaseList
List of periodic forwarding resources to be released. | +| periodicityAndOffset
Indicates the periodicity and slot offset for the periodic forwarding resource. All the periodic forwarding resources configured within the same resource set should have the same periodicity. If the periodicity is expressed in [ms], the value range of slot offset is from 0 to Periodicity[ms] * referenceSCS[kHz]/15 -1. | +| priorityFlag
Indicates the priority for the list of periodic forwarding resources, as specified in TS 38.213 [13], clause 20. | +| referenceSCS
Indicates the reference subcarrier spacing for all the time resources in the list. Only values kHz15 , kHz30 , kHz60 , kHz120 and kHz240 are applicable. | +| symbolOffset
Indicates the symbol offset in one slot. | + +#### — ***NCR-PeriodicFwdResourceSetId*** + +The IE *NCR-PeriodicFwdResourceSetId* is used to identify one *NCR-PeriodicFwdResourceSet*. + +#### ***NCR-PeriodicFwdResourceSetId* information element** + +``` +-- ASN1START +-- TAG-NCR-PERIODICFWDRESOURCESETID-START + +NCR-PeriodicFwdResourceSetId-r18 ::= INTEGER (0..maxNrofPeriodicFwdResourceSet-1-r18) + +-- TAG-NCR-PERIODICFWDRESOURCESETID-STOP +-- ASN1STOP +``` + +#### — ***NCR-SemiPersistentFwdResourceSet*** + +The IE *NCR-SemiPersistentFwdResourceSet* is used to configure a list of semi-persistent forwarding resources for NCR-Fwd access link. Each semi-persistent forwarding resource configuration includes a list of semi-persistent forwarding resources, a common periodicity and a common reference SCS. + +#### ***NCR-SemiPersistentFwdResourceSet information element*** + +``` + +-- ASN1START +-- TAG-NCR-SEMI PERSISTENT FWD RESOURCE SET-START + +NCR-SemiPersistentFwdResourceSet-r18 ::= SEQUENCE { + semiPersistentFwdRsrcSetId-r18 NCR-SemiPersistentFwdResourceSetId-r18, + semiPersistentFwdRsrcToAddModList-r18 SEQUENCE (SIZE (1..maxNrofSemiPersistentFwdResource-r18)) OF + NCR-SemiPersistentFwdResource-r18 OPTIONAL, -- Need N + semiPersistentFwdRsrcToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofSemiPersistentFwdResource-r18)) OF + NCR-SemiPersistentFwdResourceId-r18 OPTIONAL, -- Need N + referenceSCS-r18 SubcarrierSpacing OPTIONAL, -- Need M + priorityFlag-r18 ENUMERATED {true} OPTIONAL, -- Need R + ... +} + +NCR-SemiPersistentFwdResource-r18 ::= SEQUENCE { + semiPersistentFwdRsrcId-r18 NCR-SemiPersistentFwdResourceId-r18, + beamIndex-r18 INTEGER (0..63), + semiPersistentTimeRsrc-r18 SEQUENCE { + periodicityAndOffset-r18 NCR-PeriodicityAndOffset-r18, + symbolOffset-r18 INTEGER (0..maxNrofSymbols-1), + durationInSymbols-r18 INTEGER (1..112) + } +} + +NCR-SemiPersistentFwdResourceId-r18 ::= INTEGER (0..maxNrofSemiPersistentFwdResource-1-r18) + +-- TAG-NCR-SEMI PERSISTENT FWD RESOURCE SET-STOP +-- ASN1STOP + +``` + +| NCR-SemiPersistentFwdResourceSet field descriptions | | +|-------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| beamIndex | Indicates logical beam index for NCR-Fwd access link. NCR-Fwd is assumed to be ON over the indicated time domain resource if there is beam indication. | +| durationInSymbols | Indicates the time duration in number of symbols. | +| periodicityAndOffset | Indicates the periodicity and slot offset for the semi-persistent forwarding resource. All the semi-persistent forwarding resources configured within the same resource set should have the same periodicity. If the periodicity is expressed in [ms], the value range of slot offset is from 0 to Periodicity[ms] * referenceSCS[kHz]/15 - 1. | +| priorityFlag | Indicates the priority for the list of semi-persistent forwarding resources, as specified in TS 38.213 [13], clause 20. | +| referenceSCS | Indicates the reference subcarrier spacing for all the time resources in the list. Only values kHz15 , kHz30 , kHz60 , kHz120 and kHz240 are applicable. | +| semiPersistentFwdRsrcToAddModList | List of semi-persistent forwarding resources to be added or modified. | +| semiPersistentFwdRsrcToReleaseList | List of semi-persistent forwarding resources to be released. | +| symbolOffset | Indicates the symbol offset in one slot. | + +#### – ***NCR-SemiPersistentFwdResourceSetId*** + +The IE *NCR-SemiPersistentFwdResourceSetId* is used to identify one *NCR-SemiPersistentFwdResourceSet*. + +#### ***NCR-SemiPersistentFwdResourceSetId* information element** + +``` +-- ASN1START +-- TAG-NCR-SEMIPERSISTENTFWDRESOURCESETID-START + +NCR-SemiPersistentFwdResourceSetId-r18 ::= INTEGER (0..maxNrofSemiPersistentFwdResourceSet-1-r18) + +-- TAG-NCR-SEMIPERSISTENTFWDRESOURCESETID-STOP +-- ASN1STOP +``` + +#### – ***NeedForGapsConfigNR*** + +The IE *NeedForGapsConfigNR* contains configuration related to the reporting of measurement gap requirement information. + +#### ***NeedForGapsConfigNR* information element** + +``` +-- ASN1START +-- TAG-NeedForGapsConfigNR-START + +NeedForGapsConfigNR-r16 ::= SEQUENCE { +``` + +``` + + requestedTargetBandFilterNR-r16 SEQUENCE (SIZE (1..maxBands)) OF FreqBandIndicatorNR OPTIONAL -- Need R +} + +-- TAG-NeedForGapsConfigNR-STOP +-- ASN1STOP + +``` + +#### NeedForGapsConfigNR field descriptions + +**requestedTargetBandFilterNR** +Indicates the target NR bands that the UE is requested to report the gap requirement information. + +#### — NeedForGapsInfoNR + +The IE *NeedForGapsInfoNR* indicates whether measurement gap is required for the UE to perform SSB based measurements on an NR target band while NR-DC or NE-DC is not configured. + +#### NeedForGapsInfoNR information element + +``` + +-- ASN1START +-- TAG-NeedForGapsInfoNR-START + +NeedForGapsInfoNR-r16 ::= SEQUENCE { + intraFreq-needForGap-r16 NeedForGapsIntraFreqList-r16, + interFreq-needForGap-r16 NeedForGapsBandListNR-r16 +} + +NeedForGapsIntraFreqList-r16 ::= SEQUENCE (SIZE (1.. maxNrofServingCells)) OF NeedForGapsIntraFreq-r16 + +NeedForGapsBandListNR-r16 ::= SEQUENCE (SIZE (1..maxBands)) OF NeedForGapsNR-r16 + +NeedForGapsIntraFreq-r16 ::= SEQUENCE { + servCellId-r16 ServCellIndex, + gapIndicationIntra-r16 ENUMERATED {gap, no-gap} +} + +NeedForGapsNR-r16 ::= SEQUENCE { + bandNR-r16 FreqBandIndicatorNR, + gapIndication-r16 ENUMERATED {gap, no-gap} +} + +-- TAG-NeedForGapsInfoNR-STOP +-- ASN1STOP + +``` + +| NeedForGapsInfoNR field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------| +| intraFreq-needForGap
Indicates the measurement gap requirement information for NR intra-frequency measurement. | +| interFreq-needForGap
Indicates the measurement gap requirement information for NR inter-frequency measurement. | + +| NeedForGapsIntraFreq field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| servCellId
Indicates the serving cell which contains the target SSB (associated with the initial DL BWP) to be measured. | +| gapIndicationIntra
Indicates whether measurement gap is required for the UE to perform intra-frequency SSB based measurements on the concerned serving cell. Value gap indicates that a measurement gap is needed if any of the UE configured BWPs (except the BWP(s) configured with servingCellIMO associated with NCD-SSB) do not contain the frequency domain resources of the SSB associated to the initial DL BWP (CD-SSB). Value no-gap indicates a measurement gap is not needed to measure the SSB associated to the initial DL BWP (CD-SSB) for all configured BWPs (except the BWP(s) configured with servingCellIMO associated with NCD-SSB), no matter the SSB is within the configured BWP or not. This field shall be set to 'no-gap' for the corresponding band(s) where bwpOperationMeasWithoutInterrupt-r18 is supported by the UE. | + +| NeedForGapsNR field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| bandNR
Indicates the NR target band to be measured. | +| gapIndication
Indicates whether measurement gap is required for the UE to perform SSB based measurements on the concerned NR target band while NR-DC or NE-DC is not configured. The UE determines this information based on the resultant configuration of the RRReconfiguration or RRResume message that triggers this response. Value gap indicates that a measurement gap is needed, value no-gap indicates a measurement gap is not needed. | + +#### — *NeedForGapNCSG-ConfigEUTRA* + +The IE *NeedForGapNCSG-ConfigEUTRA* contains configuration related to the reporting of measurement gap and NCSG requirement information. + +#### ***NeedForGapNCSG-ConfigEUTRA* information element** + +``` +-- ASN1START +-- TAG-NeedForGapNCSG-ConfigEUTRA-START + +NeedForGapNCSG-ConfigEUTRA-r17 ::= SEQUENCE { + requestedTargetBandFilterNCSG-EUTRA-r17 SEQUENCE (SIZE (1..maxBandsEUTRA)) OF FreqBandIndicatorEUTRA OPTIONAL -- Need R +} + +-- TAG-NeedForGapNCSG-ConfigEUTRA-STOP +-- ASN1STOP +``` + +#### | | |------------------------------------------------------| | NeedForGapNCSG-ConfigEUTRA field descriptions | |------------------------------------------------------| + +##### | | |--------------------------------------------| | requestedTargetBandFilterNCSG-EUTRA | |--------------------------------------------| + +| | +|----------------------------------------------------------------------------------------------------------------------------| +| Indicates the target E-UTRA bands that the UE is requested to report the measurement gap and NCSG requirement information. | +|----------------------------------------------------------------------------------------------------------------------------| + +#### — NeedForGapNCSG-ConfigNR + +The IE *NeedForGapNCSG-ConfigNR* contains configuration related to the reporting of measurement gap and NCSG requirement information. + +#### NeedForGapNCSG-ConfigNR information element + +``` +-- ASN1START +-- TAG-NEEDFORGAPNCSG-CONFIGNR-START + +NeedForGapNCSG-ConfigNR-r17 ::= SEQUENCE { + requestedTargetBandFilterNCSG-NR-r17 SEQUENCE (SIZE (1..maxBands)) OF FreqBandIndicatorNR OPTIONAL -- Need R +} + +-- TAG-NEEDFORGAPNCSG-CONFIGNR-STOP +-- ASN1STOP +``` + +#### | | |---------------------------------------------------| | NeedForGapNCSG-ConfigNR field descriptions | |---------------------------------------------------| + +##### | | |-----------------------------------------| | requestedTargetBandFilterNCSG-NR | |-----------------------------------------| + +| | +|------------------------------------------------------------------------------------------------------------------------| +| Indicates the target NR bands that the UE is requested to report the measurement gap and NCSG requirement information. | +|------------------------------------------------------------------------------------------------------------------------| + +#### — NeedForGapNCSG-InfoEUTRA + +The IE *NeedForGapNCSG-InfoEUTRA* indicates whether measurement gap or NCSG is required for the UE to perform measurements on an E-UTRA target band while NR-DC or NE-DC is not configured. + +#### NeedForGapNCSG-InfoEUTRA information element + +``` +-- ASN1START +-- TAG-NEEDFORGAPNCSG-INFOEUTRA-START + +NeedForGapNCSG-InfoEUTRA-r17 ::= SEQUENCE { + needForNCSG-EUTRA-r17 SEQUENCE (SIZE (1..maxBandsEUTRA)) OF NeedForNCSG-EUTRA-r17 +} + +NeedForNCSG-EUTRA-r17 ::= SEQUENCE { + bandEUTRA-r17 FreqBandIndicatorEUTRA, + gapIndication-r17 ENUMERATED {gap, ncsg, nogap-noncsng} +} + +-- TAG-NEEDFORGAPNCSG-INFOEUTRA-STOP +``` + +``` +-- ASN1STOP +``` + +#### NeedForGapNCSG-InfoEUTRA field descriptions + +##### needForNCSG-EUTRA + +Indicates the measurement gap and NCSG requirement information for E-UTRA measurement. + +#### NeedForNCSG-EUTRA field descriptions + +##### bandEUTRA + +Indicates the E-UTRA target band to be measured. + +##### gapIndication + +Indicates whether measurement gap or NCSG is required for the UE to perform measurements on the concerned E-UTRA target band while NR-DC or NE-DC is not configured. The UE determines this information based on the resultant configuration of the *RRCReconfiguration* message or *RRCResume* message that triggers this response. Value *gap* indicates that a measurement gap is needed, value *ncsg* indicates that NCSG is needed, value *nogap-noncsg* indicates neither a measurement gap nor a NCSG is needed. Value *nogap-noncsg* also indicates interruption is not needed. + +#### — NeedForGapNCSG-InfoNR + +The IE *NeedForGapNCSG-InfoNR* indicates whether measurement gap or NCSG is required for the UE to perform SSB based measurements on an NR target band while NR-DC or NE-DC is not configured. + +#### NeedForGapNCSG-InfoNR information element + +``` +-- ASN1START +-- TAG-NEEDFORGAPNCSG-INFO NR-START + +NeedForGapNCSG-InfoNR-r17 ::= SEQUENCE { + intraFreq-needForNCSG-r17 NeedForNCSG-IntraFreqList-r17, + interFreq-needForNCSG-r17 NeedForNCSG-BandListNR-r17 +} + +NeedForNCSG-IntraFreqList-r17 ::= SEQUENCE (SIZE (1.. maxNrofServingCells)) OF NeedForNCSG-IntraFreq-r17 + +NeedForNCSG-BandListNR-r17 ::= SEQUENCE (SIZE (1..maxBands)) OF NeedForNCSG-NR-r17 + +NeedForNCSG-IntraFreq-r17 ::= SEQUENCE { + servCellId-r17 ServCellIndex, + gapIndicationIntra-r17 ENUMERATED {gap, ncsg, nogap-noncsg} +} + +NeedForNCSG-NR-r17 ::= SEQUENCE { + bandNR-r17 FreqBandIndicatorNR, + gapIndication-r17 ENUMERATED {gap, ncsg, nogap-noncsg} +} +``` + +``` +-- TAG-NEEDFORGAPNCSG-INFO NR-STOP +-- ASN1STOP +``` + +| NeedForGapNCSG-InfoNR field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------| +| intraFreq-needForNCSG
Indicates the measurement gap and NCSG requirement information for NR intra-frequency measurement. | +| interFreq-needForNCSG
Indicates the measurement gap and NCSG requirement information for NR inter-frequency measurement. | + +| NeedForNCSG-IntraFreq field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| servCellId
Indicates the serving cell which contains the target SSB (associated with the initial DL BWP) to be measured. | +| gapIndicationIntra
Indicates whether measurement gap or NCSG is required for the UE to perform intra-frequency SSB based measurements on the concerned serving cell. Value gap indicates that a measurement gap is needed if any of the UE configured BWPs (except the BWP(s) configured with servingCellMO associated with NCD-SSB) do not contain the frequency domain resources of the SSB associated to the initial DL BWP (CD-SSB). Value ncsg indicates that a NCSG is needed if any of the UE configured BWPs do not contain the frequency domain resources of the SSB associated to the initial DL BWP. Value nogap-noncsg indicates that neither a measurement gap nor a NCSG is needed to measure the SSB associated to the initial DL BWP (CD-SSB) for all configured BWPs (except the BWP(s) configured with servingCellMO associated with NCD-SSB), no matter the SSB is within the configured BWP or not. This field shall be set to ' nogap-noncsg ' for the corresponding band(s) where bwpOperationMeasWithoutInterrupt-r18 is supported by the UE. Value nogap-noncsg also indicates interruption is not needed. | + +| NeedForNCSG-NR field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| bandNR
Indicates the NR target band to be measured. | +| gapIndication
Indicates whether measurement gap or NCSG is required for the UE to perform SSB based measurements on the concerned NR target band while NR-DC or NE-DC is not configured. The UE determines this information based on the resultant configuration of the RRCReconfiguration or RRCResume message that triggers this response. Value gap indicates that a measurement gap is needed, value ncsg indicates that a NCSG is needed, and value nogap-noncsg indicates neither a measurement gap nor a NCSG is needed. Value nogap-noncsg also indicates interruption is not needed. | + +#### — *NeedForInterruptionInfoNR* + +The IE *NeedForInterruptionInfoNR* indicates whether interruption is needed for the UE to perform SSB based measurements on an NR target band without measurement gap while NR-DC or NE-DC is not configured. + +#### ***NeedForInterruptionInfoNR* information element** + +``` +-- ASN1START +-- TAG-NeedForInterruptionInfoNR-START +``` + +``` + +NeedForInterruptionInfoNR-r18 ::= SEQUENCE { + intraFreq-needForInterruption-r18 NeedForInterruptionIntraFreqList-r18, + interFreq-needForInterruption-r18 NeedForInterruptionBandListNR-r18 +} + +NeedForInterruptionIntraFreqList-r18 ::= SEQUENCE (SIZE (1.. maxNrofServingCells)) OF NeedForInterruptionNR-r18 + +NeedForInterruptionBandListNR-r18 ::= SEQUENCE (SIZE (1..maxBands)) OF NeedForInterruptionNR-r18 + +NeedForInterruptionNR-r18 ::= SEQUENCE { + interruptionIndication-r18 ENUMERATED {no-gap-with-interruption, no-gap-no-interruption} OPTIONAL +} + +-- TAG-NeedForInterruptionInfoNR-STOP +-- ASN1STOP + +``` + +#### NeedForInterruptionInfoNR field descriptions + +##### *intraFreq-needForInterruption* + +Indicates the interruption requirement information for NR intra-frequency measurement. Each entry in the list is associated to the entry in list *intraFreq-needForGap-r16* with the same index. This field shall be set to *no-gap-no-interruption* for the corresponding band(s) where *bwpOperationMeasWithoutInterrupt-r18* is supported by the UE. + +##### *interFreq-needForInterruption* + +Indicates the interruption requirement information for NR inter-frequency measurement. Each entry in the list is associated to the entry in list *interFreq-needForGap-r16* with the same index. + +#### NeedForInterruptionNR field descriptions + +##### *interruptionIndication* + +Indicates whether interruption is needed for the UE to perform SSB based measurements without measurement gap. Value *no-gap-with-interruption* indicates that interruption is needed. Value *no-gap-no-interruption* indicates interruption is not needed. + +#### — *NextHopChainingCount* + +The IE *NextHopChainingCount* is used to update the $K_{\text{gnb}}$ key and corresponds to parameter NCC: See TS 33.501 [11]. + +#### NextHopChainingCount information element + +``` + +-- ASN1START +-- TAG-NEXTHOPCHAININGCOUNT-START + +NextHopChainingCount ::= INTEGER (0..7) + +-- TAG-NEXTHOPCHAININGCOUNT-STOP +-- ASN1STOP + +``` + +#### — *NG-5G-S-TMSI* + +The IE *NG-5G-S-TMSI* contains a 5G S-Temporary Mobile Subscription Identifier (5G-S-TMSI), a temporary UE identity provided by the 5GC which uniquely identifies the UE within the tracking area, see TS 23.003 [21]. + +#### *NG-5G-S-TMSI* information element + +``` +-- ASN1START +-- TAG-NG-5G-S-TMSI-START + +NG-5G-S-TMSI ::= BIT STRING (SIZE (48)) + +-- TAG-NG-5G-S-TMSI-STOP +-- ASN1STOP +``` + +#### — *NonCellDefiningSSB* + +The IE *NonCellDefiningSSB* is used to configure a NCD-SSB to be used while the UE operates in an (e)RedCap-specific initial BWP or a dedicated BWP that does not contain the CD-SSB. + +#### *NonCellDefiningSSB* information element + +``` +-- ASN1START +-- TAG-NONCELLDEFININGSSB-START + +NonCellDefiningSSB-r17 ::= SEQUENCE { + absoluteFrequencySSB-r17 ARFCN-ValueNR, + ssb-Periodicity-r17 ENUMERATED { ms5, ms10, ms20, ms40, ms80, ms160, spare2, spare1 } OPTIONAL, -- Need S + ssb-TimeOffset-r17 ENUMERATED { ms5, ms10, ms15, ms20, ms40, ms80, spare2, spare1 } OPTIONAL, -- Need S + ... +} + +-- TAG-NONCELLDEFININGSSB-STOP +-- ASN1STOP +``` + +| NonCellDefiningSSB field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| absoluteFrequencySSB
Frequency of the NCD-SSB. The network configures this field so that the SSB is within the bandwidth of the BWP configured in BWP-DownlinkCommon . | +| ssb-Periodicity
The periodicity of this NCD-SSB. The network configures only periodicities that are larger than the periodicity of serving cell's CD-SSB. If the field is absent, the UE applies the SSB periodicity of the CD-SSB ( ssb-periodicityServingCell configured in ServingCellConfigCommon or ServingCellConfigCommonSIB ). | +| ssb-TimeOffset
The time offset between CD-SSB of the serving cell and this NCD-SSB. Value ms5 means the first burst of NCD-SSB is transmitted 5ms later than the first burst of CD-SSB transmitted after the first symbol of SFN=0 of the serving cell, value ms10 means the first burst of NCD-SSB is transmitted 10ms later than the first burst of CD-SSB transmitted after the first symbol in SFN=0 of the serving cell, and so on. If the field is absent, UE considers that the time offset between the first burst of CD-SSB transmitted in the serving cell and the first burst of this NCD-SSB transmitted is zero. For RedCap UEs in TDD cells, the network configures this time offset to be an integer multiple of the periodicity of the serving cell's CD-SSB. | + +#### — *NPN-Identity* + +The IE *NPN-Identity* includes either a list of CAG-IDs or a list of NIDs per PLMN Identity. Further information regarding how to set the IE is specified in TS 23.003 [21]. + +#### ***NPN-Identity* information element** + +``` +-- ASN1START +-- TAG-NPN-IDENTITY-START + +NPN-Identity-r16 ::= CHOICE { + pni-npn-r16 SEQUENCE { + plmn-Identity-r16 PLMN-Identity, + cag-IdentityList-r16 SEQUENCE (SIZE (1..maxNPN-r16)) OF CAG-IdentityInfo-r16 + }, + snpn-r16 SEQUENCE { + plmn-Identity-r16 PLMN-Identity, + nid-List-r16 SEQUENCE (SIZE (1..maxNPN-r16)) OF NID-r16 + } +} + +CAG-IdentityInfo-r16 ::= SEQUENCE { + cag-Identity-r16 BIT STRING (SIZE (32)), + manualCAGselectionAllowed-r16 ENUMERATED {true} OPTIONAL -- Need R +} + +NID-r16 ::= BIT STRING (SIZE (44)) + +-- TAG-NPN-IDENTITY-STOP +-- ASN1STOP +``` + +| NPN-Identity field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| cag-Identity
A CAG-ID as specified in TS 23.003 [21]. The PLMN ID and a CAG ID in the NPN-Identity identifies a PNI-NPN. | +| cag-IdentityList
The cag-IdentityList contains one or more CAG IDs. All CAG IDs associated to the same PLMN ID are listed in the same cag-IdentityList entry. | +| manualCAGselectionAllowed
The manualCAGselectionAllowed indicates that the CAG ID can be selected manually even if it is outside the UE's allowed CAG list. | +| NID
A NID as specified in TS 23.003 [21]. The PLMN ID and a NID in the NPN-Identity identifies a SNPN. | +| nid-List
The nid-List contains one or more NID . | + +#### — *NPN-IdentityInfoList* + +The IE *NPN-IdentityInfoList* includes a list of NPN identity information. + +#### ***NPN-IdentityInfoList* information element** + +``` +-- ASN1START +-- TAG-NPN-IDENTITYINFOLIST-START + +NPN-IdentityInfoList-r16 ::= SEQUENCE (SIZE (1..maxNPN-r16)) OF NPN-IdentityInfo-r16 + +NPN-IdentityInfo-r16 ::= SEQUENCE { + npn-IdentityList-r16 SEQUENCE (SIZE (1..maxNPN-r16)) OF NPN-Identity-r16, + trackingAreaCode-r16 TrackingAreaCode, + ranac-r16 RAN-AreaCode OPTIONAL, -- Need R + cellIdentity-r16 CellIdentity, + cellReservedForOperatorUse-r16 ENUMERATED {reserved, notReserved}, + iab-Support-r16 ENUMERATED {true} OPTIONAL, -- Need S + ..., + [[ + gNB-ID-Length-r17 INTEGER (22..32) OPTIONAL -- Need R + ]], + [[ + mobileIAB-Support-r18 ENUMERATED {true} OPTIONAL -- Need S + ]] +} + +-- TAG-NPN-IDENTITYINFOLIST-STOP +-- ASN1STOP +``` + +| NPN-IdentityInfoList field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| iab-Support
This field combines both the support of IAB and the cell status for IAB. If the field is present, the cell supports IAB and the cell is also considered as a candidate for cell (re)selection for IAB-nodes; if the field is absent, the cell does not support IAB and/or the cell is barred for IAB-node. | +| gNB-ID-Length
Indicates the length of the gNB ID out of the 36-bit long cellIdentity . This field is always present if the mobileIAB-Support is broadcasted in a cell. | +| mobileIAB-Support
This field indicates the support of mobile IAB. If the field is absent, the cell is barred for mobile IAB-node. | +| NPN-IdentityInfo
The NPN-IdentityInfo contains one or more NPN identities and additional information associated with those NPNs. Only the same type of NPNs (either SNPNS or PNI-NPNs) can be listed in a NPN-IdentityInfo element. | +| npn-IdentityList
The npn-IdentityList contains one or more NPN Identity elements. | +| trackingAreaCode
Indicates the Tracking Area Code to which the cell indicated by cellIdentity field belongs. | +| ranac
Indicates the RAN Area Code to which the cell indicated by cellIdentity field belongs. | +| cellReservedForOperatorUse
Indicates whether the cell is reserved for operator use (for the NPN(s) identified in the npn-IdentityList ) as defined in TS 38.304 [20]. This field is ignored by NPN capable IAB-MT and NPN capable NCR-MT. | + +#### NR-DL-PRS-PDC-Info + +The IE *NR-DL-PRS-PDC-Info* defines downlink PRS configuration for PDC. + +#### NR-DL-PRS-PDC-Info information element + +``` +-- ASN1START +-- TAG-NR-DL-PRS-PDC-INFO-START + +NR-DL-PRS-PDC-Info-r17 ::= SEQUENCE { + nr-DL-PRS-PDC-ResourceSet-r17 NR-DL-PRS-PDC-ResourceSet-r17 OPTIONAL, -- Need R + ... +} + +NR-DL-PRS-PDC-ResourceSet-r17 ::= SEQUENCE { + periodicityAndOffset-r17 NR-DL-PRS-Periodicity-and-ResourceSetSlotOffset-r17, + numSymbols-r17 ENUMERATED {n2, n4, n6, n12, n1-v1800, spare3, spare2, spare1}, + dl-PRS-ResourceBandwidth-r17 INTEGER (1..63), + dl-PRS-StartPRB-r17 INTEGER (0..2176), + resourceList-r17 SEQUENCE (SIZE (1..maxNrofPRS-ResourcesPerSet-r17)) OF NR-DL-PRS-Resource-r17, + repFactorAndTimeGap-r17 RepFactorAndTimeGap-r17 OPTIONAL, -- Need S + ... +} +``` + +``` +NR-DL-PRS-Periodicity-and-ResourceSetSlotOffset-r17 ::= CHOICE { + scs15-r17 CHOICE { + n4-r17 INTEGER (0..3), + n5-r17 INTEGER (0..4), + n8-r17 INTEGER (0..7), + n10-r17 INTEGER (0..9), + n16-r17 INTEGER (0..15), + n20-r17 INTEGER (0..19), + n32-r17 INTEGER (0..31), + n40-r17 INTEGER (0..39), + n64-r17 INTEGER (0..63), + n80-r17 INTEGER (0..79), + n160-r17 INTEGER (0..159), + n320-r17 INTEGER (0..319), + n640-r17 INTEGER (0..639), + n1280-r17 INTEGER (0..1279), + n2560-r17 INTEGER (0..2559), + n5120-r17 INTEGER (0..5119), + n10240-r17 INTEGER (0..10239), + ... + }, + scs30-r17 CHOICE { + n8-r17 INTEGER (0..7), + n10-r17 INTEGER (0..9), + n16-r17 INTEGER (0..15), + n20-r17 INTEGER (0..19), + n32-r17 INTEGER (0..31), + n40-r17 INTEGER (0..39), + n64-r17 INTEGER (0..63), + n80-r17 INTEGER (0..79), + n128-r17 INTEGER (0..127), + n160-r17 INTEGER (0..159), + n320-r17 INTEGER (0..319), + n640-r17 INTEGER (0..639), + n1280-r17 INTEGER (0..1279), + n2560-r17 INTEGER (0..2559), + n5120-r17 INTEGER (0..5119), + n10240-r17 INTEGER (0..10239), + n20480-r17 INTEGER (0..20479), + ... + }, + scs60-r17 CHOICE { + n16-r17 INTEGER (0..15), + n20-r17 INTEGER (0..19), + n32-r17 INTEGER (0..31), + n40-r17 INTEGER (0..39), + n64-r17 INTEGER (0..63), + n80-r17 INTEGER (0..79), + n128-r17 INTEGER (0..127), + n160-r17 INTEGER (0..159), + n256-r17 INTEGER (0..255), + } +} +``` + +``` + + n320-r17 INTEGER (0..319), + n640-r17 INTEGER (0..639), + n1280-r17 INTEGER (0..1279), + n2560-r17 INTEGER (0..2559), + n5120-r17 INTEGER (0..5119), + n10240-r17 INTEGER (0..10239), + n20480-r17 INTEGER (0..20479), + n40960-r17 INTEGER (0..40959), + ... + }, + scs120-r17 CHOICE { + n32-r17 INTEGER (0..31), + n40-r17 INTEGER (0..39), + n64-r17 INTEGER (0..63), + n80-r17 INTEGER (0..79), + n128-r17 INTEGER (0..127), + n160-r17 INTEGER (0..159), + n256-r17 INTEGER (0..255), + n320-r17 INTEGER (0..319), + n512-r17 INTEGER (0..511), + n640-r17 INTEGER (0..639), + n1280-r17 INTEGER (0..1279), + n2560-r17 INTEGER (0..2559), + n5120-r17 INTEGER (0..5119), + n10240-r17 INTEGER (0..10239), + n20480-r17 INTEGER (0..20479), + n40960-r17 INTEGER (0..40959), + n81920-r17 INTEGER (0..81919), + ... + }, + ... +} + +NR-DL-PRS-Resource-r17 ::= SEQUENCE { + nr-DL-PRS-ResourceID-r17 NR-DL-PRS-ResourceID-r17, + dl-PRS-SequenceID-r17 INTEGER (0..4095), + dl-PRS-CombSizeN-AndReOffset-r17 CHOICE { + n2-r17 INTEGER (0..1), + n4-r17 INTEGER (0..3), + n6-r17 INTEGER (0..5), + n12-r17 INTEGER (0..11), + ... + }, + dl-PRS-ResourceSlotOffset-r17 INTEGER (0..maxNrofPRS-ResourceOffsetValue-1-r17), + dl-PRS-ResourceSymbolOffset-r17 INTEGER (0..12), + dl-PRS-QCL-Info-r17 DL-PRS-QCL-Info-r17 OPTIONAL, -- Need N + ... + [[ + dl-PRS-ResourceSymbolOffset-v1800 INTEGER (13) OPTIONAL -- Need R + ]] +} + +``` + +``` + +DL-PRS-QCL-Info-r17 ::= CHOICE { + ssb-r17 SEQUENCE { + ssb-Index-r17 INTEGER (0..63), + rs-Type-r17 ENUMERATED {typeC, typeD, typeC-plus-typeD}, + ... + }, + dl-PRS-r17 SEQUENCE { + qcl-DL-PRS-ResourceID-r17 NR-DL-PRS-ResourceID-r17, + ... + }, + ... +} + +NR-DL-PRS-ResourceID-r17 ::= INTEGER (0..maxNrofPRS-ResourcesPerSet-1-r17) + +RepFactorAndTimeGap-r17 ::= SEQUENCE { + repetitionFactor-r17 ENUMERATED {n2, n4, n6, n8, n16, n32, spare2, spare1}, + timeGap-r17 ENUMERATED {s1, s2, s4, s8, s16, s32, spare2, spare1} +} + +-- TAG-NR-DL-PRS-PDC-INFO-STOP +-- ASN1STOP + +``` + +#### NR-DL-PRS-PDC-ResourceSet field descriptions + +| | | +|---------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| dl-PRS-ResourceBandwidth | This field specifies the number of PRBs allocated for all the DL-PRS Resource (allocated DL-PRS bandwidth) in multiples of 4 PRBs in this resource set. All DL-PRS Resources of the DL-PRS-PDC Resource Set have the same bandwidth. Integer value 1 corresponds to 24 PRBs, value 2 corresponds to 28 PRBs, value 3 corresponds to 32 PRBs and so on. | +| dl-PRS-StartPRB | This field specifies the start PRB index defined as offset with respect to subcarrier 0 in common resource block 0 for the DL-PRS Resource. All DL-PRS Resources of the DL-PRS-PDC Resource Set have the same value of dl-PRS-StartPRB. | +| numSymbols | This field specifies the number of symbols per DL-PRS Resource within a slot. The UE does not expect to be configured for PDC with a PRS with numSymbols equals to n1 unless an SSB index is provided as a typeC or typeC-plus-typeD QCL source, or another PRS resource with numSymbols more than n1 is provided as QCL source. | +| periodicityAndOffset | This field specifies the periodicity of DL-PRS allocation in slots and the slot offset with respect to SFN #0 slot #0 in the PCell where the DL-PRS-PDC Resource Set is configured (i.e., slot where the first DL-PRS Resource of DL-PRS-PDC Resource Set occurs). | +| repFactorAndTimeGap | If this field is absent, the value for repetitionFactor is 1 (i.e., no resource repetition). | + +| RepFactorAndTimeGap field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| repetitionFactor
This field specifies how many times each DL-PRS Resource is repeated for a single instance of the DL-PRS Resource Set. It is applied to all resources of the DL-PRS Resource Set. Enumerated values n2, n4, n6, n8, n16, n32 correspond to 2, 4, 6, 8, 16, 32 resource repetitions, respectively. | +| timeGap
This field specifies the offset in units of slots between two repeated instances of a DL-PRS Resource corresponding to the same DL-PRS Resource ID within a single instance of the DL-PRS Resource Set. The time duration spanned by one DL-PRS Resource Set containing repeated DL-PRS Resources should not exceed the periodicity configured by periodicityAndOffset . | + +| NR-DL-PRS-Resource field description | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| dl-PRS-ResourceSymbolOffset
This field specifies the starting symbol of the DL-PRS Resource within a slot. If dl-PRS-ResourceSymbolOffset-v1800 is present, the UE shall ignore dl-PRS-ResourceSymbolOffset-r17 . | + +#### NR-NS-PmaxList + +The IE *NR-NS-PmaxList* is used to configure a list of *additionalPmax* and *additionalSpectrumEmission*, as defined in TS 38.101-1 [15], table 6.2.3.1-1A, TS 38.101-2 [39], table 6.2.3.1-2, and TS 38.101-5 [75], table 6.2.3.1-1A for a given frequency band. + +#### NR-NS-PmaxList information element + +``` +-- ASN1START +-- TAG-NR-NS-PMAXLIST-START + +NR-NS-PmaxList ::= + SEQUENCE (SIZE (1..maxNR-NS-Pmax)) OF NR-NS-PmaxValue + +NR-NS-PmaxValue ::= + SEQUENCE { + additionalPmax P-Max OPTIONAL, -- Need N + additionalSpectrumEmission AdditionalSpectrumEmission + } + +NR-NS-PmaxList-v1760 ::= + SEQUENCE (SIZE (1.. maxNR-NS-Pmax)) OF NR-NS-PmaxValue-v1760 + +NR-NS-PmaxValue-v1760 ::= + SEQUENCE { + additionalSpectrumEmission-v1760 AdditionalSpectrumEmission-v1760 OPTIONAL -- Need N + } + +NR-NS-PmaxListAerial-r18 ::= + SEQUENCE (SIZE (1..maxNR-NS-Pmax)) OF NR-NS-PmaxValueAerial-r18 + +NR-NS-PmaxValueAerial-r18 ::= + SEQUENCE { + additionalPmax-r18 P-Max OPTIONAL, -- Need N + additionalSpectrumEmission-r18 AdditionalSpectrumEmission-r18 + } +``` + +``` +-- TAG-NR-NS-PMAXLIST-STOP +-- ASN1STOP +``` + +#### – NSAG-ID + +The IE *NSAG-ID* is used to identify an NSAG (TS 23.501 [32]) for slice-based cell reselection or slice-based random access. + +#### NSAG-ID information element + +``` +-- ASN1START +-- TAG-NSAG-ID-START + +NSAG-ID-r17 ::= BIT STRING (SIZE (8)) + +-- TAG-NSAG-ID-STOP +-- ASN1STOP +``` + +#### – NSAG-IdentityInfo + +The IE *NSAG-IdentityInfo* is used to identify an NSAG (TS 23.501 [32]) for slice-based cell reselection. + +#### NSAG-IdentityInfo information element + +``` +-- ASN1START +-- TAG-NSAG-IDENTITYINFO-START + +NSAG-IdentityInfo-r17 ::= SEQUENCE { + nsag-ID-r17 NSAG-ID-r17, + trackingAreaCode-r17 TrackingAreaCode OPTIONAL -- Need R +} + +-- TAG-NSAG-IDENTITYINFO-STOP +-- ASN1STOP +``` + +#### NSAG-IdentityInfo field descriptions + +| | +|-----------------------------------------------------------------------------------------------------------| +|

trackingAreaCode
If absent, UE assumes the trackingAreaCode of the serving cell.

| +|-----------------------------------------------------------------------------------------------------------| + +#### – NTN-Config + +The IE *NTN-Config* provides parameters needed for the UE to access NR via NTN access. + +#### **NTN-Config information element** + +``` + +-- ASN1START +-- TAG-NTN-CONFIG-START + +NTN-Config-r17 ::= + SEQUENCE { + epochTime-r17 EpochTime-r17 OPTIONAL, -- Need R + ntn-ULSyncValidityDuration-r17 ENUMERATED{ s5, s10, s15, s20, s25, s30, s35, + s40, s45, s50, s55, s60, s120, s180, s240, s900} OPTIONAL, -- Cond SIB19 + cellSpecificKoffset-r17 INTEGER(1..1023) OPTIONAL, -- Need R + kmac-r17 INTEGER(1..512) OPTIONAL, -- Need R + ta-Info-r17 TA-Info-r17 OPTIONAL, -- Need R + ntn-PolarizationDL-r17 ENUMERATED {rhcp,lhcp,linear} OPTIONAL, -- Need R + ntn-PolarizationUL-r17 ENUMERATED {rhcp,lhcp,linear} OPTIONAL, -- Need R + ephemerisInfo-r17 EphemerisInfo-r17 OPTIONAL, -- Need R + ta-Report-r17 ENUMERATED {enabled} OPTIONAL, -- Need R + ... + } + +EpochTime-r17 ::= + SEQUENCE { + sfn-r17 INTEGER(0..1023), + subFrameNR-r17 INTEGER(0..9) + } + +TA-Info-r17 ::= + SEQUENCE { + ta-Common-r17 INTEGER(0..66485757), + ta-CommonDrift-r17 INTEGER(-257303..257303) OPTIONAL, -- Need R + ta-CommonDriftVariant-r17 INTEGER(0..28949) OPTIONAL -- Need R + } + +-- TAG-NTN-CONFIG-STOP +-- ASN1STOP + +``` + +| NTN-Config field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| EphemerisInfo
This field provides satellite ephemeris either in format of position and velocity state vector or in format of orbital parameters. This field is excluded when determining changes in system information, i.e. changes to ephemerisInfo should neither result in system information change notifications nor in a modification of valueTag in SIB1. | +| epochTime
Indicate the epoch time for the NTN assistance information. When explicitly provided through SIB, or through dedicated signaling, the EpochTime is the starting time of a DL sub-frame, indicated by a SFN and a sub-frame number signaled together with the assistance information. For serving cell, the field sfn indicates the current SFN or the next upcoming SFN after the frame where the message indicating the epochTime is received. For neighbour cell, the sfn indicates the SFN nearest to the frame where the message indicating the epochTime is received. The reference point for epoch time of the serving or neighbour NTN payload ephemeris and Common TA parameters is the uplink time synchronization reference point when this field is provided in an NTN cell and the gNB when this field is provided in a TN cell. If this field is absent for the serving cell, the epoch time is the end of SI window where this SIB19 is scheduled. This field is mandatory present when ntn-Config is provided in dedicated configuration. If this field is absent in ntn-Config provided via NTN-NeighCellConfig the UE uses epoch time of the serving cell, otherwise the field is based on the timing of the serving cell, i.e. the SFN and sub-frame number indicated in this field refers to the SFN and sub-frame of the serving cell. In case of handover or conditional handover, this field is based on the timing of the target cell, i.e. the SFN and sub-frame number indicated in this field refers to the SFN and sub-frame of the target cell. For the target cell the UE considers epoch time, indicated by the SFN and sub-frame number in this field, to be the frame nearest to the frame in which the message indicating the epoch time is received. This field is excluded when determining changes in system information, i.e. changes to epochTime should neither result in system information change notifications nor in a modification of valueTag in SIB1. | +| cellSpecificKoffset
Scheduling offset used for the timing relationships that are modified for NTN (see TS 38.213 [13]). The unit of the field K_offset is number of slots for a given subcarrier spacing of 15 kHz. If the field is absent UE assumes value 0. | +| kmac
Scheduling offset provided by network if downlink and uplink frame timing are not aligned at gNB. If the field is absent UE assumes value 0. In FR1, the unit of kmac is number of slots for a given subcarrier spacing of 15 kHz. | +| ntn-PolarizationDL
If present, this parameter indicates polarization information for downlink transmission on service link: including Right hand, Left hand circular polarizations (RHCP, LHCP) and Linear polarization. | +| ntn-PolarizationUL
If present, this parameter indicates Polarization information for uplink service link.
If not present and ntn-PolarizationDL is present, UE assumes the same polarization for UL and DL. | +| ntn-UISyncValidityDuration
A validity duration configured by the network for assistance information (i.e. Serving and/or neighbour satellite ephemeris and Common TA parameters) which indicates the maximum time duration (from epochTime ) during which the UE can apply assistance information without having acquired new assistance information.
The unit of ntn-UISyncValidityDuration is second. Value s5 corresponds to 5 s, value s10 indicate 10 s and so on. This parameter applies to both connected and idle mode UEs. If this field is absent in ntn-Config provided via NTN-NeighCellConfig , the UE uses validity duration from the serving cell assistance information. This field is excluded when determining changes in system information, i.e. changes of ntn-UISyncValidityDuration should neither result in system information change notifications nor in a modification of valueTag in SIB1. ntn-UISyncValidityDuration is only updated when at least one of epochTime , ta-Info , ephemerisInfo is updated. | +| ta-Common
Network-controlled common timing advanced value and it may include any timing offset considered necessary by the network. ta-Common with value of 0 is supported. The granularity of ta-Common is $4.072 \times 10^{-(3)}$ $\mu\text{s}$ . Values are given in unit of corresponding granularity. This field is excluded when determining changes in system information, i.e. changes of ta-Common should neither result in system information change notifications nor in a modification of valueTag in SIB1. | +| ta-CommonDrift
Indicate drift rate of the common TA. The granularity of ta-CommonDrift is $0.2 \times 10^{-(3)}$ $\mu\text{s/s}$ . Values are given in unit of corresponding granularity. This field is excluded when determining changes in system information, i.e. changes of ta-CommonDrift should neither result in system information change notifications nor in a modification of valueTag in SIB1. | + +##### **ta-CommonDriftVariant** + +Indicate drift rate variation of the common TA. The granularity of *ta-CommonDriftVariant* is $0.2 \times 10^{-4}$ $\mu\text{s/s}^2$ . Values are given in unit of corresponding granularity. This field is excluded when determining changes in system information, i.e. changes of *ta-CommonDriftVariant* should neither result in system information change notifications nor in a modification of *valueTag* in SIB1. + +##### **ta-Report** + +When this field is included in SIB19, it indicates reporting of timing advanced is enabled during Random Access due to RRC connection establishment or RRC connection resume, and during RRC connection reestablishment. When this field is included in *ServingCellConfigCommon* within dedicated signalling, it indicates TA reporting is enabled during Random Access due to reconfiguration with sync (see TS 38.321 [3], clause 5.4.8). + +| Conditional Presence | Explanation | +|----------------------|-------------------------------------------------------------------------------------------------------------------| +| SIB19 | The field is mandatory present for the serving cell in SIB19. The field is optionally present, Need R, otherwise. | + +#### — NZP-CSI-RS-Resource + +The IE *NZP-CSI-RS-Resource* is used to configure Non-Zero-Power (NZP) CSI-RS transmitted in the cell where the IE is included, which the UE may be configured to measure on (see TS 38.214 [19], clause 5.2.2.3.1). A change of configuration between periodic, semi-persistent or aperiodic for an *NZP-CSI-RS-Resource* is not supported without a release and add. + +#### NZP-CSI-RS-Resource information element + +``` +-- ASN1START +-- TAG-NZP-CSI-RS-RESOURCE-START + +NZP-CSI-RS-Resource ::= SEQUENCE { + nzp-CSI-RS-ResourceId NZP-CSI-RS-ResourceId, + resourceMapping CSI-RS-ResourceMapping, + powerControlOffset INTEGER (-8..15), + powerControlOffsetSS ENUMERATED{db-3, db0, db3, db6} OPTIONAL, -- Need R + scramblingID ScramblingId, + periodicityAndOffset CSI-RS-ResourcePeriodicityAndOffset OPTIONAL, -- Cond PeriodicOrSemiPersistent + qcl-InfoPeriodicCSI-RS TCI-StateId OPTIONAL, -- Cond Periodic + ... + [[ + subcarrierSpacing-r18 SubcarrierSpacing OPTIONAL, -- Cond LTM + absoluteFrequencyPointA-r18 ARFCN-ValueNR OPTIONAL, -- Cond LTM + cyclicPrefix-r18 ENUMERATED {extended} OPTIONAL, -- Cond LTM + ]] +} + +-- TAG-NZP-CSI-RS-RESOURCE-STOP +-- ASN1STOP +``` + +| NZP-CSI-RS-Resource field descriptions | | +|-----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| periodicityAndOffset | Periodicity and slot offset s1 corresponds to a periodicity of 1 slot, s2 to a periodicity of two slots, and so on. The corresponding offset is also given in number of slots (see TS 38.214 [19], clause 5.2.2.3.1). Network always configures the UE with a value for this field for periodic and semi-persistent NZP-CSI-RS-Resource (as indicated in CSI-ResourceConfig ). | +| powerControlOffset | Power offset of PDSCH RE to NZP CSI-RS RE. Value in dB (see TS 38.214 [19], clauses 5.2.2.3.1 and 4.1). The UE shall ignore this field in case NZP-CSI-RS-Resources is received as part of an LTM-Candidate IE. | +| powerControlOffsetSS | Power offset of NZP CSI-RS RE to SSS RE. Value in dB (see TS 38.214 [19], clause 5.2.2.3.1). | +| qcl-InfoPeriodicCSI-RS | For a target periodic CSI-RS, contains a reference to one TCI-State in TCI-States for providing the QCL source and QCL type. For periodic CSI-RS, the source can be SSB or another periodic-CSI-RS. Refers to the TCI-State or dl-OrJoint-TCI-State which has this value for tci-StateId and is defined in tci-StatesToAddModList or in dl-OrJointTCI-StateList in the PDSCH-Config included in the BWP-Downlink corresponding to the serving cell and to the DL BWP to which the resource belongs to (see TS 38.214 [19], clause 5.2.2.3.1). In case NZP-CSI-RS-Resources is received as part of an LTM-Candidate IE, it refers to the TCI state identifier in CandidateTCI-State and is defined in ltm-DL-OrJointTCI-StateToAddModList within the LTM-Candidate IE. | +| resourceMapping | OFDM symbol location(s) in a slot and subcarrier occupancy in a PRB of the CSI-RS resource. | +| scramblingID | Scrambling ID (see TS 38.214 [19], clause 5.2.2.3.1). | + +| Conditional Presence | Explanation | +|---------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| LTM | The field is optionally present in case NZP-CSI-RS-Resources is part of an LTM-Candidate IE. Otherwise, the field is absent, Need R. | +| Periodic | The field is optionally present, Need M, for periodic NZP-CSI-RS-Resources (as indicated in CSI-ResourceConfig ). The field is absent otherwise. | +| PeriodicOrSemiPersistent | The field is optionally present, Need M, for periodic and semi-persistent NZP-CSI-RS-Resources (as indicated in CSI-ResourceConfig ). The field is absent otherwise. | + +#### — NZP-CSI-RS-ResourceId + +The IE *NZP-CSI-RS-ResourceId* is used to identify one NZP-CSI-RS-Resource. + +#### NZP-CSI-RS-ResourceId information element + +``` +-- ASN1START +-- TAG-NZP-CSI-RS-RESOURCEID-START + +NZP-CSI-RS-ResourceId ::= INTEGER (0..maxNrofNZP-CSI-RS-Resources-1) + +-- TAG-NZP-CSI-RS-RESOURCEID-STOP +-- ASN1STOP +``` + +#### – NZP-CSI-RS-ResourceSet + +The IE *NZP-CSI-RS-ResourceSet* is a set of Non-Zero-Power (NZP) CSI-RS resources (their IDs) and set-specific parameters. + +#### NZP-CSI-RS-ResourceSet information element + +``` +-- ASN1START +-- TAG-NZP-CSI-RS-RESOURCESET-START + +NZP-CSI-RS-ResourceSet ::= SEQUENCE { + nzp-CSI-RS-ResourceSetId NZP-CSI-RS-ResourceSetId, + nzp-CSI-RS-Resources SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourcesPerSet)) OF NZP-CSI-RS-ResourceId, + repetition ENUMERATED { on, off } OPTIONAL, -- Need S + aperiodicTriggeringOffset INTEGER (0..6) OPTIONAL, -- Need S + trs-Info ENUMERATED {true} OPTIONAL, -- Need R + ..., + [[ + aperiodicTriggeringOffset-r16 INTEGER (0..31) OPTIONAL -- Need S + ]], + [[ + pdc-Info-r17 ENUMERATED {true} OPTIONAL, -- Need R + cmrGroupingAndPairing-r17 CMRGroupingAndPairing-r17 OPTIONAL, -- Need R + aperiodicTriggeringOffset-r17 INTEGER (0..124) OPTIONAL, -- Need S + aperiodicTriggeringOffsetL2-r17 INTEGER (0..31) OPTIONAL -- Need R + ]], + [[ + resourceType-r18 ENUMERATED {periodic} OPTIONAL -- Cond LTM + ]] +} + +CMRGroupingAndPairing-r17 ::= SEQUENCE { + nrofResourcesGroup1-r17 INTEGER (1..7), + pair1OfNZP-CSI-RS-r17 NZP-CSI-RS-Pairing-r17 OPTIONAL, -- Need R + pair2OfNZP-CSI-RS-r17 NZP-CSI-RS-Pairing-r17 OPTIONAL -- Need R +} + +NZP-CSI-RS-Pairing-r17 ::= SEQUENCE { + nzp-CSI-RS-ResourceId1-r17 INTEGER (1..7), + nzp-CSI-RS-ResourceId2-r17 INTEGER (1..7) +} + +-- TAG-NZP-CSI-RS-RESOURCESET-STOP +-- ASN1STOP +``` + +| NZP-CSI-RS-ResourceSet field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| aperiodicTriggeringOffset, aperiodicTriggeringOffset-r16, aperiodicTriggeringOffset-r17
Offset X between the slot containing the DCI that triggers a set of aperiodic NZP CSI-RS resources and the slot in which the CSI-RS resource set is transmitted. For aperiodicTriggeringOffset , the value 0 corresponds to 0 slots, value 1 corresponds to 1 slot, value 2 corresponds to 2 slots, value 3 corresponds to 3 slots, value 4 corresponds to 4 slots, value 5 corresponds to 16 slots, value 6 corresponds to 24 slots. For aperiodicTriggeringOffset-r16 and aperiodicTriggeringOffset-r17 , the value indicates the number of slots. aperiodicTriggeringOffset-r17 is applicable to SCS 480 kHz and 960 kHz, and only the values of integer multiples of 4 are valid, i.e. 0, 4, 8, and so on. The network configures only one of the fields. When neither field is included, the UE applies the value 0. This field is not present in case NZP-CSI-RS-ResourcesSet is received as part of an LTM-Candidate IE. | +| aperiodicTriggeringOffsetL2
Indicates triggering offset of aperiodic NZP CSI-RS resources used for fast activation of the SCell (see clause 5.2.1.5.3 of TS 38.214 [19]), when the NZP CSI-RS resources are activated by the MAC CE (see clause 5.9 of TS 38.321 [3]). The value indicates the number of slots. This field is not present in case NZP-CSI-RS-ResourcesSet is received as part of an LTM-Candidate IE. | +| cmrGroupingAndPairing
Configures CMR groups and pairs. The first nrofResourcesGroup1 resources in the NZP-CSI-RS resource set belong to Group 1 and the remaining resources in the NZP-CSI-RS resource set belong to Group 2. nrofResourcesGroup1 is and the number of remaining resources in the NZP-CSI-RS resource set belonging to Group 2 is as specified in TS 38.214 clause 5.2.1.4.1. Maximum total number in Group 1 and Group 2 is 8 (see TS 38.214 [19], clauses 5.2.1.4.1 and 5.2.1.4.2). This field is not present in case NZP-CSI-RS-ResourcesSet is received as part of an LTM-Candidate IE. | +| pair1OfNZP-CSI-RS, pair2OfNZP-CSI-RS
A pair of NZP CSI-RS resources. In one pair, one resource shall belong to group 1 and the other resource shall belong to group 2 (see TS 38.214 [19], clause 5.2.1.4.1). | +| nzp-CSI-RS-Resources
NZP-CSI-RS-Resources associated with this NZP-CSI-RS resource set (see TS 38.214 [19], clause 5.2). For CSI, there are at most 8 NZP CSI RS resources per resource set. For Doppler or Doppler-PS codebook operation there are at most 1 P/SP NZP CSI-RS resource and 4, 8 or 12 AP NZP CSI-RS resources and for CJT or CJT-PS, there are 1, 2, 3, or 4 AP/P/SP NZP-CSI-RS resources, see TS 38.214 5.2.1.4. | +| nzp-CSI-RS-ResourceId1, nzp-CSI-RS-ResourceId2
The nzp-CSI-RS-ResourceId1-r17 represents the index of the NZP CSI-RS resource in Resource Group 1, and nzp-CSI-RS-ResourceId2-r17 represents the index of the NZP CSI-RS resource in Resource Group 2. | +| pdc-Info
Indicates that this NZP-CSI-RS-ResourceSet, if configured also with trs-Info , is used for propagation delay compensation. The field can be present only if trs-info is present. The field can be present in only one NZP-CSI-RS-ResourceSet . If network configures this field for an NZP-CSI-RS-ResourceSet , the UE measures the UE Rx-Tx time difference based on resources configured in this resource set. This field is not present in case NZP-CSI-RS-ResourcesSet is received as part of an LTM-Candidate IE. | +| repetition
Indicates whether repetition is on/off. If the field is set to off or if the field is absent, the UE may not assume that the NZP-CSI-RS resources within the resource set are transmitted with the same downlink spatial domain transmission filter (see TS 38.214 [19], clauses 5.2.2.3.1 and 5.1.6.1.2). It can only be configured for CSI-RS resource sets which are associated with CSI-ReportConfig with report of L1 RSRP, L1 SINR or "no report". This field is not present in case NZP-CSI-RS-ResourcesSet is received as part of an LTM-Candidate IE. | +| resourceType
Time domain behavior of resource configuration (see TS 38.214 [19], clause 5.2.1.2). | +| trs-Info
Indicates that the antenna port for all NZP-CSI-RS resources in the CSI-RS resource set is same. If the field is absent or released the UE applies the value false (see TS 38.214 [19], clause 5.2.2.3.1). | + +| Conditional Presence | Explanation | +|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| LTM | The field is optionally present in case NZP-CSI-RS-ResourcesSet is part of an LTM-Candidate IE. Otherwise, the field is absent, Need R. | + +#### – *NZP-CSI-RS-ResourceSetId* + +The IE *NZP-CSI-RS-ResourceSetId* is used to identify one *NZP-CSI-RS-ResourceSet*. + +#### *NZP-CSI-RS-ResourceSetId* information element + +``` +-- ASN1START +-- TAG-NZP-CSI-RS-RESOURCESETID-START + +NZP-CSI-RS-ResourceSetId ::= INTEGER (0..maxNrofNZP-CSI-RS-ResourceSets-1) + +-- TAG-NZP-CSI-RS-RESOURCESETID-STOP +-- ASN1STOP +``` + +#### – *P-Max* + +The IE *P-Max* is used to limit the UE's uplink transmission power on a carrier frequency, in TS 38.101-1 [15] and in TS 38.101-5 [75], and is used to calculate the parameter *Pcompensation* defined in TS 38.304 [20]. In ATG cell, actual value of P-Max = 9 + field value [dBm]. + +#### *P-Max* information element + +``` +-- ASN1START +-- TAG-P-MAX-START + +P-Max ::= INTEGER (-30..33) + +-- TAG-P-MAX-STOP +-- ASN1STOP +``` + +#### – *PathlossReferenceRS* + +The IE *PathlossReferenceRS* is used to configure a Reference Signal (e.g. a CSI-RS config or a SS block) to be used for path loss estimation for PUSCH, PUCCH and SRS for unified TCI state operation. + +#### *PathlossReferenceRS* information element + +``` +-- ASN1START +-- TAG-PATHLOSSREFERENCERS-START +``` + +``` + +PathlossReferenceRS-r17 ::= SEQUENCE { + pathlossReferenceRS-Id-r17 PathlossReferenceRS-Id-r17, + referenceSignal-r17 CHOICE { + ssb-Index SSB-Index, + csi-RS-Index NZP-CSI-RS-ResourceId + }, + additionalPCI-r17 AdditionalPCIIndex-r17 OPTIONAL -- Cond RS-SSB +} + +-- TAG-PATHLOSSREFERENCESRS-STOP +-- ASN1STOP + +``` + +#### PathlossReferenceRS field descriptions + +##### additionalPCI + +Indicates the physical cell ID (PCI) of the SSB for the referenceSignal. + +| Conditional Presence | Explanation | +|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------| +| RS-SSB | The field is optionally present, Need R, if ssb-Index is configured for referenceSignal . Otherwise it is absent, Need R. | + +#### — PathlossReferenceRS-Id + +The IE *PathlossReferenceRS-Id* is an ID for a reference signal (RS) configured as PUSCH, PUCCH and SRS pathloss reference RS for unified TCI state operation. + +#### PathlossReferenceRS-Id information element + +``` + +-- ASN1START +-- TAG-PATHLOSSREFERENCESRS-ID-START + +PathlossReferenceRS-Id-r17 ::= INTEGER (0..maxNrofPathlossReferenceRSs-1-r17) + +-- TAG-PATHLOSSREFERENCESRS-ID-STOP +-- ASN1STOP + +``` + +#### — PCI-ARFCN-EUTRA + +The IE *PCI-ARFCN-EUTRA* is used to encode EUTRA PCI and ARFCN. + +#### PCI-ARFCN-EUTRA information element + +``` + +-- ASN1START +-- TAG-PCIARFCNEUTRA-START + +``` + +``` +PCI-ARFCN-EUTRA-r16 ::= SEQUENCE { + physCellId-r16 EUTRA-PhysCellId, + carrierFreq-r16 ARFCN-ValueEUTRA +} + +-- TAG-PCIARFCNEUTRA-STOP +-- ASN1STOP +``` + +#### – *PCI-ARFCN-NR* + +The IE *PCI-ARFCN-NR* is used to encode NR PCI and ARFCN. + +#### *PCI-ARFCN-NR* information element + +``` +-- ASN1START +-- TAG-PCIARFCNNR-START + +PCI-ARFCN-NR-r16 ::= SEQUENCE { + physCellId-r16 PhysCellId, + carrierFreq-r16 ARFCN-ValueNR +} + +-- TAG-PCIARFCNNR-STOP +-- ASN1STOP +``` + +#### – *PCI-List* + +The IE *PCI-List* concerns a list of physical cell identities, which may be used for different purposes. + +#### *PCI-List* information element + +``` +-- ASN1START +-- TAG-PCI-LIST-START + +PCI-List ::= SEQUENCE (SIZE (1..maxNrofCellMeas)) OF PhysCellId + +-- TAG-PCI-LIST-STOP +-- ASN1STOP +``` + +#### — *PCI-Range* + +The IE *PCI-Range* is used to encode either a single or a range of physical cell identities. The range is encoded by using a *start* value and by indicating the number of consecutive physical cell identities (including *start*) in the range. For fields comprising multiple occurrences of *PCI-Range*, the Network may configure overlapping ranges of physical cell identities. + +#### *PCI-Range* information element + +``` +-- ASN1START +-- TAG-PCI-RANGE-START + +PCI-Range ::= SEQUENCE { + start PhysCellId, + range ENUMERATED {n4, n8, n12, n16, n24, n32, n48, n64, n84, + n96, n128, n168, n252, n504, n1008,spare1} +} OPTIONAL -- Need S + +-- TAG-PCI-RANGE-STOP +-- ASN1STOP +``` + +#### *PCI-Range* field descriptions + +| | | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| range | Indicates the number of physical cell identities in the range (including start ). Value n4 corresponds with 4, value n8 corresponds with 8 and so on. The UE shall apply value 1 in case the field is absent, in which case only the physical cell identity value indicated by start applies. | +| start | Indicates the lowest physical cell identity in the range. | + +#### — *PCI-RangeElement* + +The IE *PCI-RangeElement* is used to define a *PCI-Range* as part of a list (e.g. AddMod list). + +#### *PCI-RangeElement* information element + +``` +-- ASN1START +-- TAG-PCI-RANGEELEMENT-START + +PCI-RangeElement ::= SEQUENCE { + pci-RangeIndex PCI-RangeIndex, + pci-Range PCI-Range +} + +-- TAG-PCI-RANGEELEMENT-STOP +-- ASN1STOP +``` + +| PCI-RangeElement field descriptions | +|-------------------------------------------------------------------------------------------| +| pci-Range
Physical cell identity or a range of physical cell identities. | + +#### — ***PCI-RangeIndex*** + +The IE *PCI-RangeIndex* identifies a physical cell id range, which may be used for different purposes. + +#### ***PCI-RangeIndex* information element** + +``` +-- ASN1START +-- TAG-PCI-RANGEINDEX-START + +PCI-RangeIndex ::= INTEGER (1..maxNrofPCI-Ranges) + +-- TAG-PCI-RANGEINDEX-STOP +-- ASN1STOP +``` + +#### — ***PCI-RangeIndexList*** + +The IE *PCI-RangeIndexList* concerns a list of indexes of physical cell id ranges, which may be used for different purposes. + +#### ***PCI-RangeIndexList* information element** + +``` +-- ASN1START +-- TAG-PCI-RANGEINDEXLIST-START + +PCI-RangeIndexList ::= SEQUENCE (SIZE (1..maxNrofPCI-Ranges)) OF PCI-RangeIndex + +-- TAG-PCI-RANGEINDEXLIST-STOP +-- ASN1STOP +``` + +#### — ***PDCCH-Config*** + +The IE *PDCCH-Config* is used to configure UE specific PDCCH parameters or MBS multicast PDCCH parameters such as control resource sets (CORESET), search spaces and additional parameters for acquiring the PDCCH. If this IE is used for the scheduled SCell in case of cross carrier scheduling, the fields other than *searchSpacesToAddModList* and *searchSpacesToReleaseList* are absent. If the IE is used for a dormant BWP, the fields other than *controlResourceSetToAddModList* and *controlResourceSetToReleaseList* are absent. If this IE is used for MBS CFR, the field *downlinkPreemption, tpc-PUSCH, tpc-SRS, uplinkCancellation, monitoringCapabilityConfig*, and *searchSpaceSwitchConfig* are absent. + +#### PDCCH-Config information element + +``` + +-- ASN1START +-- TAG-PDCCH-CONFIG-START + +PDCCH-Config ::= SEQUENCE { + controlResourceSetToAddModList SEQUENCE (SIZE (1..3)) OF ControlResourceSet OPTIONAL, -- Need N + controlResourceSetToReleaseList SEQUENCE (SIZE (1..3)) OF ControlResourceSetId OPTIONAL, -- Need N + searchSpacesToAddModList SEQUENCE (SIZE (1..10)) OF SearchSpace OPTIONAL, -- Need N + searchSpacesToReleaseList SEQUENCE (SIZE (1..10)) OF SearchSpaceId OPTIONAL, -- Need N + downlinkPreemption SetupRelease { DownlinkPreemption } OPTIONAL, -- Need M + tpc-PUSCH SetupRelease { PUSCH-TPC-CommandConfig } OPTIONAL, -- Need M + tpc-PUCCH SetupRelease { PUCCH-TPC-CommandConfig } OPTIONAL, -- Need M + tpc-SRS SetupRelease { SRS-TPC-CommandConfig } OPTIONAL, -- Need M + ..., + [[ + controlResourceSetToAddModListSizeExt-v1610 SEQUENCE (SIZE (1..2)) OF ControlResourceSet OPTIONAL, -- Need N + controlResourceSetToReleaseListSizeExt-r16 SEQUENCE (SIZE (1..5)) OF ControlResourceSetId-r16 OPTIONAL, -- Need N + searchSpacesToAddModListExt-r16 SEQUENCE (SIZE (1..10)) OF SearchSpaceExt-r16 OPTIONAL, -- Need N + uplinkCancellation-r16 SetupRelease { UplinkCancellation-r16 } OPTIONAL, -- Need M + monitoringCapabilityConfig-r16 ENUMERATED { r15monitoringcapability, r16monitoringcapability } OPTIONAL, -- Need M + searchSpaceSwitchConfig-r16 SearchSpaceSwitchConfig-r16 OPTIONAL, -- Need R + ]], + [[ + searchSpacesToAddModListExt-v1700 SEQUENCE (SIZE (1..10)) OF SearchSpaceExt-v1700 OPTIONAL, -- Need N + monitoringCapabilityConfig-v1710 ENUMERATED { r17monitoringcapability } OPTIONAL, -- Need M + searchSpaceSwitchConfig-r17 SearchSpaceSwitchConfig-r17 OPTIONAL, -- Need R + pdcch-SkippingDurationList-r17 SEQUENCE (SIZE (1..3)) OF SCS-SpecificDuration-r17 OPTIONAL, -- Need R + ]], + [[ + pdcch-MonitoringResumptionAfterNack-r18 ENUMERATED {true} OPTIONAL, -- Need R + searchSpacesToAddModListExt-v1800 SEQUENCE (SIZE (1..10)) OF SearchSpaceExt-v1800 OPTIONAL, -- Need N + ]] +} + +SearchSpaceSwitchConfig-r16 ::= SEQUENCE { + cellGroupsForSwitchList-r16 SEQUENCE (SIZE (1..4)) OF CellGroupForSwitch-r16 OPTIONAL, -- Need R + searchSpaceSwitchDelay-r16 INTEGER (10..52) OPTIONAL, -- Need R +} + +SearchSpaceSwitchConfig-r17 ::= SEQUENCE { + searchSpaceSwitchTimer-r17 SCS-SpecificDuration-r17 OPTIONAL, -- Need R + searchSpaceSwitchDelay-r17 INTEGER (10..52) OPTIONAL, -- Need R +} + +CellGroupForSwitch-r16 ::= SEQUENCE (SIZE (1..16)) OF ServCellIndex + +SCS-SpecificDuration-r17 ::= INTEGER (1..166) + +-- TAG-PDCCH-CONFIG-STOP +-- ASN1STOP + +``` + + + +| PDCCH-Config field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| controlResourceSetToAddModList, controlResourceSetToAddModListSizeExt
List of UE specifically configured Control Resource Sets (CORESETs) to be used by the UE. The network restrictions on configuration of CORESETs per DL BWP are specified in TS 38.213 [13], clause 10.1 and TS 38.306 [26]. The UE shall consider entries in controlResourceSetToAddModList and in controlResourceSetToAddModListSizeExt as a single list, i.e. an entry created using controlResourceSetToAddModList can be modified using controlResourceSetToAddModListSizeExt (or deleted using controlResourceSetToReleaseListSizeExt ) and vice-versa. In case network reconfigures control resource set with the same ControlResourceSetId as used for commonControlResourceSet or commonControlResourceSetExt configured via PDCCH-ConfigCommon or via SIB20 , the configuration from PDCCH-Config always takes precedence and should not be updated by the UE based on servingCellConfigCommon or based on SIB20 . | +| controlResourceSetToReleaseList, controlResourceSetToReleaseListSizeExt
List of UE specifically configured Control Resource Sets (CORESETs) to be released by the UE. This field only applies to CORESETs configured by controlResourceSetToAddModList or controlResourceSetToAddModListSizeExt and does not release the field commonControlResourceSet configured by PDCCH-ConfigCommon and commonControlResourceSetExt configured by SIB20 . | +| downlinkPreemption
Configuration of downlink preemption indications to be monitored in this cell (see TS 38.213 [13], clause 11.2). | +| monitoringCapabilityConfig
Configures either Rel-15 PDCCH monitoring capability, Rel-16 PDCCH monitoring capability or Rel-17 PDCCH monitoring capability for PDCCH monitoring on a serving cell (see TS 38.213 [13], clause 10.1). Value r15monitoringcapability enables the Rel-15 monitoring capability, and value r16monitoringcapability enables the Rel-16 PDCCH monitoring capability. r17monitoringcapability enables the Rel-17 PDCCH multi-slot monitoring capability. For 480 and 960 kHz SCS, only value r17monitoringcapability is applicable. | +| pdcch-MonitoringResumptionAfterNack
This field is used to enable UE PDCCH monitoring resumption after PDCCH skipping has started, if the UE transmits a NACK due to incorrectly decoding a PDSCH scheduled by a DCI format received from the serving cell (see TS 38.213 [13], clause 10.4). | +| pdcch-SkippingDurationList
Provides one or more values to derive the skipping duration in unit of slots, as specified in TS 38.213 [13], clause 10.4. The DCI which schedules data indicates which of the values is to be applied (see TS 38.213 [13], clause 10.4). For the 15kHz SCS, for each entry, only the first 26 values are valid and correspond to {1, 2, 3, ..., 20, 30, 40, 50, 60, 80, 100}. For the 30kHz SCS, for each entry, only the first 46 values are valid and correspond to {1, 2, 3, ..., 40, 60, 80, 100, 120, 160, 200}. For the 60kHz SCS, for each entry, only the first 86 values are valid and correspond to {1, 2, 3, ..., 80, 120, 160, 200, 240, 320, 400}. For the 120kHz SCS, for each entry, the 166 values correspond to {1, 2, 3, ..., 160, 240, 320, 400, 480, 640, 800}. For the 480kHz SCS, for each entry, the 166 values correspond to {4, 8, 12, ..., 640, 960, 1280, 1600, 1920, 2560, 3200}. For the 960kHz SCS, for each entry, the 166 values correspond to {8, 16, 24, ..., 1280, 1920, 2560, 3200, 3840, 5120, 6400}. | +| searchSpacesToAddModList, searchSpacesToAddModListExt
List of UE specifically configured Search Spaces or MBS multicast Search Spaces. The network configures at most 10 Search Spaces per BWP per cell (including UE-specific and common Search Spaces). If the network includes searchSpacesToAddModListExt , it includes the same number of entries, and listed in the same order, as in searchSpacesToAddModList in each of them. | +| searchSpaceSwitchConfig
Configuration to control the UE behavior to switch from search space group X back to search space group 0, as specified in clause 10 of TS 38.213 [13]. The network only configures either searchSpaceSwitchConfig-r16 or searchSpaceSwitchConfig-r17 for a UE. | +| tpc-PUCCH
Enable and configure reception of group TPC commands for PUCCH. | +| tpc-PUSCH
Enable and configure reception of group TPC commands for PUSCH. | +| tpc-SRS
Enable and configure reception of group TPC commands for SRS. | +| uplinkCancellation
Configuration of uplink cancellation indications to be monitored in this cell (see TS 38.213 [13], clause 11.2A). | + +| SearchSpaceSwitchConfig field descriptions | | +|---------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| cellGroupsForSwitchList | The list of serving cells which are bundled for the search space group switching purpose (see TS 38.213 [13], clause 10.4). A serving cell can belong to only one CellGroupForSwitch . The network configures the same list for all BWPs of serving cells in the same CellGroupForSwitch . | +| searchSpaceSwitchDelay | Indicates the value to be applied by a UE for Search Space Set Group switching; corresponds to the P value in TS 38.213 [13], clause 10.4. The network configures the same value for all BWPs of serving cells in the same CellGroupForSwitch . For 120/480/960 kHz SCS, only values 40, 41, ... 52 are valid and the actual value = field value * SCS/120 kHz i.e. field value 40 corresponds to 40 with 120 kHz SCS, 160 with 480 kHz SCS and 320 with 960 kHz SCS, and so on. | +| searchSpaceSwitchTimer | Timer (in unit of slots) to control the UE behavior to switch from search space group X back to search space group 0, as specified in clause 10 of TS 38.213 [13]. For the 15kHz SCS, only the first 26 values are valid and correspond to {1, 2, 3, ..., 20, 30, 40, 50, 60, 80, 100}. For the 30kHz SCS, only the first 46 values are valid and correspond to {1, 2, 3, ..., 40, 60, 80, 100, 120, 160, 200}. For the 60kHz SCS, only the first 86 values are valid and correspond to {1, 2, 3, ..., 80, 120, 160, 200, 240, 320, 400}. For the 120kHz SCS, the 166 values correspond to {1, 2, 3, ..., 160, 240, 320, 400, 480, 640, 800}. For the 480kHz SCS, the 166 values correspond to {4, 8, 12, ..., 640, 960, 1280, 1600, 1920, 2560, 3200}. For the 960kHz SCS, the 166 values correspond to {8, 16, 24, ..., 1280, 1920, 2560, 3200, 3840, 5120, 6400}. | + +#### – PDCCH-ConfigCommon + +The IE *PDCCH-ConfigCommon* is used to configure cell specific PDCCH parameters provided in SIB as well as in dedicated signalling. + +#### **PDCCH-ConfigCommon information element** + +``` +-- ASN1START +-- TAG-PDCCH-CONFIGCOMMON-START + +PDCCH-ConfigCommon ::= + SEQUENCE { + controlResourceSetZero ControlResourceSetZero OPTIONAL, -- Cond InitialBWP-Only + commonControlResourceSet ControlResourceSet OPTIONAL, -- Need R + searchSpaceZero SearchSpaceZero OPTIONAL, -- Cond InitialBWP-Only + commonSearchSpaceList SEQUENCE (SIZE (1..4)) OF SearchSpace OPTIONAL, -- Need R + searchSpaceSIB1 SearchSpaceId OPTIONAL, -- Need S + searchSpaceOtherSystemInformation SearchSpaceId OPTIONAL, -- Need S + pagingSearchSpace SearchSpaceId OPTIONAL, -- Need S + ra-SearchSpace SearchSpaceId OPTIONAL, -- Need S + ..., + [[ + firstPDCCH-MonitoringOccasionOfPO CHOICE { + sCS15KHZoneT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..139), + sCS30KHZoneT-sCS15KHZhalft SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..279), + sCS60KHZoneT-sCS30KHZhalft-sCS15KHZquarterT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..559), + sCS120KHZoneT-sCS60KHZhalft-sCS30KHZquarterT-sCS15KHZoneEighthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..1119), + sCS120KHZhalft-sCS60KHZquarterT-sCS30KHZoneEighthT-sCS15KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..2239), + sCS120KHZquarterT-sCS60KHZoneEighthT-sCS30KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..4479), + sCS120KHZoneEighthT-sCS60KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..8959), + sCS120KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..17919) + } + } +-- TAG-PDCCH-CONFIGCOMMON-END +-- ASN1END +``` + +``` + + } + ],, + [[ + commonSearchSpaceListExt-r16 + ],, + [[ + sdt-SearchSpace-r17 CHOICE { + newSearchSpace SearchSpace, + existingSearchSpace SearchSpaceId + } + searchSpaceMCCH-r17 SearchSpaceId + searchSpaceMTCH-r17 SearchSpaceId + commonSearchSpaceListExt2-r17 SEQUENCE (SIZE(1..4)) OF SearchSpaceExt-v1700 + firstPDCCH-MonitoringOccasionOfPO-v1710 CHOICE { + sCS480KHZoneEighthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..35839), + sCS480KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..71679) + } + pei-ConfigBWP-r17 SEQUENCE { + pei-SearchSpace-r17 SearchSpaceId, + firstPDCCH-MonitoringOccasionOfPEI-O-r17 CHOICE { + sCS15KHZoneT SEQUENCE (SIZE (1..maxPEI-perPF-r17)) OF INTEGER (0..139), + sCS30KHZoneT-sCS15KHZhalft SEQUENCE (SIZE (1..maxPEI-perPF-r17)) OF INTEGER (0..279), + sCS60KHZoneT-sCS30KHZhalft-sCS15KHZquarterT SEQUENCE (SIZE (1..maxPEI-perPF-r17)) OF INTEGER (0..559), + sCS120KHZoneT-sCS60KHZhalft-sCS30KHZquarterT-sCS15KHZoneEighthT SEQUENCE (SIZE (1..maxPEI-perPF-r17)) OF INTEGER (0..1119), + sCS120KHZhalft-sCS60KHZquarterT-sCS30KHZoneEighthT-sCS15KHZoneSixteenthT SEQUENCE (SIZE (1..maxPEI-perPF-r17)) OF INTEGER (0..2239), + sCS480KHZoneT-sCS120KHZquarterT-sCS60KHZoneEighthT-sCS30KHZoneSixteenthT SEQUENCE (SIZE (1..maxPEI-perPF-r17)) OF INTEGER (0..4479), + sCS480KHZhalft-sCS120KHZoneEighthT-sCS60KHZoneSixteenthT SEQUENCE (SIZE (1..maxPEI-perPF-r17)) OF INTEGER (0..8959), + sCS480KHZquarterT-sCS120KHZoneSixteenthT SEQUENCE (SIZE (1..maxPEI-perPF-r17)) OF INTEGER (0..17919), + sCS480KHZoneEighthT SEQUENCE (SIZE (1..maxPEI-perPF-r17)) OF INTEGER (0..35839), + sCS480KHZoneSixteenthT SEQUENCE (SIZE (1..maxPEI-perPF-r17)) OF INTEGER (0..71679) + } + } + ],, + [[ + followUnifiedTCI-State-v1720 ENUMERATED {enabled} + ],, + [[ + applyIndicatedTCI-State-r18 ENUMERATED {first, second, both, none} + commonSearchSpaceListExt-r18 SEQUENCE (SIZE(1..4)) OF SearchSpaceExt-v1800 + searchSpaceMulticastMCCH-r18 SearchSpaceId + searchSpaceMulticastMTCH-r18 SearchSpaceId + ]] +} + +-- TAG-PDCCH-CONFIGCOMMON-STOP +-- ASN1STOP + +``` + +| PDCCH-ConfigCommon field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| applyIndicatedTCI-State
This field indicates, for PDCCH reception in CORESET #0, if UE applies the first, the second, both or none of the "indicated" DL only TCI or joint TCI as specified in TS 38.213 [13], clause 10.1. | +| commonControlResourceSet
An additional common control resource set which may be configured and used for any common or UE-specific search space. If the network configures this field, it uses a ControlResourceSetId other than 0 for this ControlResourceSet . The network configures the commonControlResourceSet in SIB1 so that it is contained in the bandwidth of CORESET#0. If the (e)RedCap-specific initial downlink BWP does not contain the entire CORESET#0, the network configures the commonControlResourceSet in the (e)RedCap-specific initial downlink BWP in SIB1 for (e)RedCap such that it does not have to be contained in the bandwidth of CORESET#0. | +| commonSearchSpaceList, commonSearchSpaceListExt, commonSearchSpaceListExt2
A list of additional common search spaces. If the network configures this field, it uses the SearchSpaceIds other than 0. If the field is included, it replaces any previous list, i.e. all the entries of the list are replaced and each of the SearchSpace entries is considered to be newly created and the conditions and Need codes for setup of the entry apply. If the network includes commonSearchSpaceListExt/commonSearchSpaceListExt2 , it includes the same number of entries, and listed in the same order, as in commonSearchSpaceList . | +| controlResourceSetZero
Parameters of the common CORESET#0 which can be used in any common or UE-specific search spaces. The values are interpreted like the corresponding bits in MIB pdcch-ConfigSIB1 . Even though this field is only configured in the initial BWP (BWP#0) controlResourceSetZero can be used in search spaces configured in other DL BWP(s) than the initial DL BWP if the conditions defined in TS 38.213 [13], clause 10 are satisfied. | +| firstPDCCH-MonitoringOccasionOfPEI-O
Offset, in number of symbols, from the start of the reference frame for PEI-O to the start of the first PDCCH monitoring occasion of PEI-O on this BWP, see TS 38.213 [13], clause 10.4A. For the case po-NumPerPEI is smaller than Ns , UE applies the $(\text{floor}(i\_s/\text{po-NumPerPEI})+1)$ -th value out of $(N\_s/\text{po-NumPerPEI})$ configured values in firstPDCCH-MonitoringOccasionOfPEI-O for the symbol-level offset. When po-NumPerPEI is one or multiple of Ns , UE applies the first configured value in firstPDCCH-MonitoringOccasionOfPEI-O for the symbol-level offset. | +| firstPDCCH-MonitoringOccasionOfPO
Indicates the first PDCCH monitoring occasion of each PO of the PF on this BWP, see TS 38.304 [20]. The field sCS120KHZquarterT-SCS60KHZoneEighthT-SCS30KHZoneSixteenthT , sCS120KHZoneEighthT-SCS60KHZoneSixteenthT and sCS120KHZoneSixteenthT can be applied for SCS 480kHz, corresponding to sCS480KHZoneT-SCS120KHZquarterT-SCS60KHZoneEighthT-SCS30KHZoneSixteenthT , sCS480KHZhalfT-SCS120KHZoneEighthT-SCS60KHZoneSixteenthT and sCS480KHZquarterT-SCS120KHZoneSixteenthT in IE DownlinkConfigCommonSIB respectively. | +| followUnifiedTCI-State
When set to enabled, for PDCCH reception in CORESET #0, the UE applies the "indicated" DL only TCI or joint TCI as specified in TS 38.214 [19], clause 5.1.5. | +| pagingSearchSpace
ID of the search space for paging (see TS 38.213 [13], clause 10.1). If the field is absent, the UE does not receive paging in this BWP (see TS 38.213 [13], clause 10). This field is absent for the (e)RedCap-specific initial downlink BWP, if it does not include CD-SSB and the entire CORESET#0. In that case, an (e)RedCap UE in RRC_IDLE or RRC_INACTIVE while SDT procedure is not ongoing, shall monitor paging in the initial DL BWP that includes CORESET#0. | +| pei-ConfigBWP
Provides the configuration for PEI reception in this BWP. If the field is absent, the UE does not receive PEI in this BWP. For the initialDownlinkBWP-RedCap not including CD-SSB and the entire CORESET#0, a RedCap UE in RRC_IDLE or RRC_INACTIVE while SDT procedure is not ongoing monitors PEI in the initialDownlinkBWP that includes CORESET#0, if the initialDownlinkBWP is configured with pei-ConfigBWP . | +| pei-SearchSpace
ID of dedicated search space for PEI. It can be configured to one of up to 4 common SS sets configured by commonSearchSpaceList with SearchSpaceId > 0. The CCE aggregation levels and maximum number of PDCCH candidates per CCE aggregation level follows Table 10.1-1 of TS38.213 [13]. SearchSpaceId = 0 can be configured for the case of SS/PBCH block and CORESET multiplexing pattern 2 or 3. | +| ra-SearchSpace
ID of the Search space for random access procedure (see TS 38.213 [13], clause 10.1). If the field is absent, the UE does not receive RAR in this BWP. This field is mandatory | + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| present in the DL BWP(s) if the conditions described in TS 38.321 [3], clause 5.15 are met. | +| sdlt-SearchSpace
Common search space for CG-SDT and RA-SDT (see TS 38.213 [13]). If an existingSearchSpace is used, the network only signals the search space ID of the ra-SearchSpace . | +| searchSpaceMCCH
ID of the search space for MCCH. If the field is absent, the UE does not receive MCCH in this BWP (see TS 38.213 [13], clause 10). This field is absent for the (e)RedCap-specific initial downlink BWP, if it does not include CD-SSB and the entire CORESET#0. | +| searchSpaceMTCH
ID of the search space for MTCH of MBS broadcast. If the field is absent, the UE applies searchSpaceMCCH also for MTCH, (see TS 38.213 [13], clause 10). This field is absent for the (e)RedCap-specific initial downlink BWP, if it does not include CD-SSB and the entire CORESET#0. | +| searchSpaceMulticastMCCH
ID of the search space for multicast MCCH. If the field is absent, the UE does not receive multicast MCCH in this BWP (see TS 38.213 [13], clause 10). This field is absent for the RedCap-specific initial downlink BWP, if it does not include CD-SSB and the entire CORESET#0. | +| searchSpaceMulticastMTCH
ID of the search space for multicast MTCH. If the field is absent, the UE applies searchSpaceMulticastMCCH also for multicast MTCH, (see TS 38.213 [13], clause 10). This field is absent for the RedCap-specific initial downlink BWP, if it does not include CD-SSB and the entire CORESET#0. | +| searchSpaceOtherSystemInformation
ID of the Search space for other system information, i.e., SIB2 and beyond (see TS 38.213 [13], clause 10.1). If the field is absent, the UE does not receive other system information in this BWP. This field is absent for the (e)RedCap-specific initial DL BWP, if it does not include CD-SSB and the entire CORESET#0. In that case, an (e)RedCap UE in RRC_IDLE or RRC_INACTIVE shall monitor PDCCH to receive other system information using searchSpaceOtherSystemInformation in the initial DL BWP that includes CD-SSB and the entire CORESET#0. | +| searchSpaceSIB1
ID of the search space for SIB1 message. In the initial DL BWP of the UE's PCell, the network sets this field to 0. If the field is absent, the UE does not receive SIB1 in this BWP. (see TS 38.213 [13], clause 10). This field is absent for the (e)RedCap-specific initial DL BWP, if it does not include CD-SSB and the entire CORESET#0. In that case, an (e)RedCap UE in RRC_IDLE or RRC_INACTIVE shall monitor PDCCH to receive SIB1 using searchSpaceSIB1 in the initial DL BWP that includes CD-SSB and the entire CORESET#0. | +| searchSpaceZero
Parameters of the common SearchSpace#0. The values are interpreted like the corresponding bits in MIB pdcch-ConfigSIB1 . Even though this field is only configured in the initial BWP (BWP#0), searchSpaceZero can be used in search spaces configured in other DL BWP(s) than the initial DL BWP if the conditions described in TS 38.213 [13], clause 10, are satisfied. | + +| Conditional Presence | Explanation | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| FollowUTCI | The field is absent if the field followUnifiedTCI-State is present. Otherwise, it is optionally present, Need R. | +| InitialBWP-Only | If SIB1 is broadcast the field is mandatory present in the PDCCH-ConfigCommon of the initial BWP (BWP#0) in ServingCellConfigCommon except it is the (e)RedCap-specific initial BWP not including CD-SSB and the entire CORESET#0; it is absent in other BWPs and when sent in system information. If SIB1 is not broadcast and there is an SSB associated to the cell, the field is optionally present, Need M, in the PDCCH-ConfigCommon of the initial BWP (BWP#0) in ServingCellConfigCommon (still with the same setting for all UEs). In other cases, the field is absent. | +| InitialBWP-Paging | This field is optionally present, Need R, if this BWP is the initialDownlinkBWP or initialDownlinkBWP-RedCap including CD-SSB and the entire CORESET#0, and pei-Config is configured in DownlinkConfigCommonSIB . Otherwise, this field is absent. | +| OtherBWP | This field is optionally present, Need R, if this BWP is not the initialDownlinkBWP and pagingSearchSpace is configured in this BWP. Otherwise this field is absent. | + +#### – *PDCCH-ConfigSIB1* + +The IE *PDCCH-ConfigSIB1* is used to configure CORESET#0 and search space#0. + +#### *PDCCH-ConfigSIB1* information element + +``` +-- ASN1START +-- TAG-PDCCH-CONFIGSIB1-START + +PDCCH-ConfigSIB1 ::= SEQUENCE { + controlResourceSetZero ControlResourceSetZero, + searchSpaceZero SearchSpaceZero +} + +-- TAG-PDCCH-CONFIGSIB1-STOP +-- ASN1STOP +``` + +#### *PDCCH-ConfigSIB1* field descriptions + +| | | +|--------------------------------------|---------------------------------------------------------------------------------------------| +| controlResourceSetZero | Determines a common ControlResourceSet (CORESET) with ID #0, see TS 38.213 [13], clause 13. | +| searchSpaceZero | Determines a common search space with ID #0, see TS 38.213 [13], clause 13. | + +#### – *PDCCH-ServingCellConfig* + +The IE *PDCCH-ServingCellConfig* is used to configure UE specific PDCCH parameters applicable across all bandwidth parts of a serving cell. + +#### *PDCCH-ServingCellConfig* information element + +``` +-- ASN1START +-- TAG-PDCCH-SERVINGCELLCONFIG-START + +PDCCH-ServingCellConfig ::= SEQUENCE { + slotFormatIndicator SetupRelease { SlotFormatIndicator } OPTIONAL, -- Need M + ... + [[ + availabilityIndicator-r16 SetupRelease {AvailabilityIndicator-r16} OPTIONAL, -- Need M + searchSpaceSwitchTimer-r16 INTEGER (1..80) OPTIONAL -- Need R + ]], + [[ + searchSpaceSwitchTimer-v1710 INTEGER (81..1280) OPTIONAL -- Need R + ]] +} + +-- TAG-PDCCH-SERVINGCELLCONFIG-STOP +``` + +-- ASN1STOP + +| PDCCH-ServingCellConfig field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| availabilityIndicator
Use to configure monitoring a PDCCH for Availability Indicators (AI). | +| searchSpaceSwitchTimer
The value of the timer in slots for monitoring PDCCH in the active DL BWP of the serving cell before moving to the default search space group (see TS 38.213 [13], clause 10.4).
For 15 kHz SCS, {1..20} are valid.
For 30 kHz SCS, {1..40} are valid.
For 60 kHz SCS, {1..80} are valid.
For 120 kHz SCS, {1..160} are valid.
For 480 kHz SCS, {1..640} are valid.
For 960 kHz SCS, {1..1280} are valid.
The network configures the same value for all serving cells in the same CellGroupForSwitch . | +| slotFormatIndicator
Configuration of Slot-Format-Indicators to be monitored in the correspondingly configured PDCCHs of this serving cell. | + +#### — PDCP-Config + +The IE *PDCP-Config* is used to set the configurable PDCP parameters for signalling, MBS multicast and data radio bearers. + +#### **PDCP-Config information element** + +``` +-- ASN1START +-- TAG-PDCP-CONFIG-START + +PDCP-Config ::= SEQUENCE { + drb SEQUENCE { + discardTimer ENUMERATED {ms10, ms20, ms30, ms40, ms50, ms60, ms75, ms100, ms150, ms200, + ms250, ms300, ms500, ms750, ms1500, infinity} OPTIONAL, -- Cond Setup + pdcp-SN-SizeUL ENUMERATED {len12bits, len18bits} OPTIONAL, -- Cond Setup1 + pdcp-SN-SizeDL ENUMERATED {len12bits, len18bits} OPTIONAL, -- Cond Setup2 + headerCompression CHOICE { + notUsed NULL, + rohc SEQUENCE { + maxCID INTEGER (1..16383) DEFAULT 15, + profiles SEQUENCE { + profile0x0001 BOOLEAN, + profile0x0002 BOOLEAN, + profile0x0003 BOOLEAN, + profile0x0004 BOOLEAN, + profile0x0006 BOOLEAN, + profile0x0101 BOOLEAN, + profile0x0102 BOOLEAN, + } + } + } + } +} +``` + +``` + + profile0x0103 BOOLEAN, + profile0x0104 BOOLEAN + }, + drb-ContinueROHC ENUMERATED { true } OPTIONAL -- Need N + }, + uplinkOnlyROHC SEQUENCE { + maxCID INTEGER (1..16383) DEFAULT 15, + profiles SEQUENCE { + profile0x0006 BOOLEAN + }, + drb-ContinueROHC ENUMERATED { true } OPTIONAL -- Need N + }, + ... + }, + integrityProtection ENUMERATED { enabled } OPTIONAL, -- Cond ConnectedTo5GC1 + statusReportRequired ENUMERATED { true } OPTIONAL, -- Cond Rlc-AM-UM + outOfOrderDelivery ENUMERATED { true } OPTIONAL, -- Need R +} OPTIONAL, -- Cond DRB +moreThanOneRLC SEQUENCE { + primaryPath SEQUENCE { + cellGroup CellGroupId OPTIONAL, -- Need R + logicalChannel LogicalChannelIdentity OPTIONAL -- Need R + }, + ul-DataSplitThreshold UL-DataSplitThreshold OPTIONAL, -- Cond SplitBearer + pdcp-Duplication BOOLEAN OPTIONAL -- Need R +} OPTIONAL, -- Cond MoreThanOneRLC + +t-Reordering ENUMERATED { + ms0, ms1, ms2, ms4, ms5, ms8, ms10, ms15, ms20, ms30, ms40, + ms50, ms60, ms80, ms100, ms120, ms140, ms160, ms180, ms200, ms220, + ms240, ms260, ms280, ms300, ms500, ms750, ms1000, ms1250, + ms1500, ms1750, ms2000, ms2250, ms2500, ms2750, + ms3000, spare28, spare27, spare26, spare25, spare24, + spare23, spare22, spare21, spare20, + spare19, spare18, spare17, spare16, spare15, spare14, + spare13, spare12, spare11, spare10, spare09, + spare08, spare07, spare06, spare05, spare04, spare03, + spare02, spare01 } OPTIONAL, -- Need S +..., +[[ +cipheringDisabled ENUMERATED {true} OPTIONAL -- Cond ConnectedTo5GC +]], +[[ +discardTimerExt-r16 SetupRelease { DiscardTimerExt-r16 } OPTIONAL, -- Cond DRB2 +moreThanTwoRLC-DRB-r16 SEQUENCE { + splitSecondaryPath-r16 LogicalChannelIdentity OPTIONAL, -- Cond SplitBearer2 + duplicationState-r16 SEQUENCE (SIZE (3)) OF BOOLEAN OPTIONAL -- Need S +} OPTIONAL, -- Cond MoreThanTwoRLC-DRB +ethernetHeaderCompression-r16 SetupRelease { EthernetHeaderCompression-r16 } OPTIONAL -- Need M +]], +[[ + +``` + +``` + +survivalTimeStateSupport-r17 ENUMERATED {true} OPTIONAL, -- Cond Drb-Duplication +uplinkDataCompression-r17 SetupRelease { UplinkDataCompression-r17 } OPTIONAL, -- Cond Rlc-AM +discardTimerExt2-r17 SetupRelease { DiscardTimerExt2-r17 } OPTIONAL, -- Need M +initialRX-DELIV-r17 BIT STRING (SIZE (32)) OPTIONAL, -- Cond MRB-Initialization +]], +[[ +pdu-SetDiscard-r18 ENUMERATED {true} OPTIONAL, -- Need R +discardTimerForLowImportance-r18 SetupRelease { DiscardTimerForLowImportance-r18 } OPTIONAL, -- Cond DRB2 +primaryPathOnIndirectPath-r18 ENUMERATED {true} OPTIONAL, -- Cond SplitBearerMP +]] +} + +EthernetHeaderCompression-r16 ::= SEQUENCE { + ehc-Common-r16 SEQUENCE { + ehc-CID-Length-r16 ENUMERATED { bits7, bits15 }, + ... + }, + ehc-Downlink-r16 SEQUENCE { + drb-ContinueEHC-DL-r16 ENUMERATED { true } OPTIONAL, -- Need N + ... + } OPTIONAL, -- Need M + ehc-Uplink-r16 SEQUENCE { + maxCID-EHC-UL-r16 INTEGER (1..32767), + drb-ContinueEHC-UL-r16 ENUMERATED { true } OPTIONAL, -- Need N + ... + } OPTIONAL, -- Need M +} + +UL-DataSplitThreshold ::= ENUMERATED { + b0, b100, b200, b400, b800, b1600, b3200, b6400, b12800, b25600, b51200, b102400, b204800, + b409600, b819200, b1228800, b1638400, b2457600, b3276800, b4096000, b4915200, b5734400, + b6553600, infinity, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1} + +DiscardTimerExt-r16 ::= ENUMERATED {ms0dot5, ms1, ms2, ms4, ms6, ms8, spare2, spare1} + +DiscardTimerExt2-r17 ::= ENUMERATED {ms2000, spare3, spare2, spare1} + +UplinkDataCompression-r17 ::= CHOICE { + newSetup SEQUENCE { + bufferSize-r17 ENUMERATED {kbyte2, kbyte4, kbyte8, spare1}, + dictionary-r17 ENUMERATED {sip-SDP, operator} OPTIONAL, -- Need N + }, + drb-ContinueUDC NULL +} + +DiscardTimerForLowImportance-r18 ::= ENUMERATED {ms0, ms2, ms4, ms6, ms8, ms10, ms12, ms14, ms18, ms22, ms26, ms30, ms40, ms50, ms75, ms100} + +-- TAG-PDCP-CONFIG-STOP +-- ASN1STOP + +``` + +| PDCP-Config field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| cipheringDisabled
If included, ciphering is disabled for this DRB regardless of which ciphering algorithm is configured for the SRB/DRBs. The field may only be included if the UE is connected to 5GC. Otherwise the field is absent. The network configures all DRBs with the same PDU-session ID with same value for this field. The value for this field cannot be changed after the DRB is set up. | +| discardTimer
Value in ms of discardTimer specified in TS 38.323 [5]. Value ms10 corresponds to 10 ms, value ms20 corresponds to 20 ms and so on. The value for this field cannot be changed in case of reconfiguration with sync, if the bearer is configured as DAPS bearer. | +| discardTimerExt
Value in ms of discardTimer specified in TS 38.323 [5]. Value ms0dot5 corresponds to 0.5 ms, value ms1 corresponds to 1ms and so on. If this field is present, the field discardTimer is ignored and discardTimerExt is used instead. | +| discardTimerExt2
Value in ms of discardTimerExt specified in TS 38.323 [5]. Value ms2000 corresponds to 2000 ms. If this field is present, the field discardTimer and discardTimerExt are ignored and discardTimerExt2 is used instead. | +| discardTimerForLowImportance
Value in ms of discardTimerForLowImportance specified in TS 38.323 [5]. Value ms0 corresponds to 0 ms, value ms2 corresponds to 2 ms and so on. The value of this timer for a PDCP entity is always configured shorter than discardTimer , discardTimerExt or discardTimerExt2 , whichever is used for the PDCP entity. | +| drb-ContinueROHC
Indicates whether the PDCP entity continues or resets the ROHC header compression protocol during PDCP re-establishment, as specified in TS 38.323 [5]. This field is configured only in case of resuming an RRC connection or reconfiguration with sync, where the PDCP termination point is not changed and the fullConfig is not indicated. The network does not include the field if the bearer is configured as DAPS bearer. This field can be configured for both DRB and multicast MRB. | +| duplicationState
This field indicates the uplink PDCP duplication state for the associated RLC entities at the time of receiving this IE. If set to true , the PDCP duplication state is activated for the associated RLC entity. The index for the indication is determined by ascending order of logical channel ID of all RLC entities other than the primary RLC entity indicated by primaryPath in the order of MCG and SCG, as in clause 6.1.3.32 of TS 38.321 [3]. If the number of associated RLC entities other than the primary RLC entity is two, UE ignores the value in the largest index of this field. If the field is absent, the PDCP duplication states are deactivated for all associated RLC entities. | +| ethernetHeaderCompression
This field configures Ethernet Header Compression. This field can only be configured for a bi-directional DRB or a bi-directional multicast MRB. The network reconfigures ethernetHeaderCompression only upon reconfiguration involving PDCP re-establishment and with neither drb-ContinueEHC-DL nor drb-ContinueEHC-UL configured. Network only configures this field when uplinkDataCompression is not configured. | +| headerCompression
If rohc is configured, the UE shall apply the configured ROHC profile(s) in both uplink and downlink. If uplinkOnlyROHC is configured, the UE shall apply the configured ROHC profile(s) in uplink (there is no header compression in downlink). ROHC can be configured for any bearer type. ROHC and EHC can be both configured simultaneously for a DRB or a multicast MRB. The network reconfigures headerCompression only upon reconfiguration involving PDCP re-establishment or involving PDCP entity reconfiguration to configure DAPS bearer(s), and without any drb-ContinueROHC . Network configures headerCompression to notUsed when outOfOrderDelivery is configured. Network only configures this field when uplinkDataCompression is not configured. | +| initialRX-DELIV
Indicates the initial value of RX_DELIV during PDCP window initialization for multicast MRB as specified in TS 38.323 [5]. | +| integrityProtection
Indicates whether or not integrity protection is configured for this radio bearer. The network configures all DRBs with the same PDU-session ID with same value for this field. The value for this field cannot be changed after the DRB is set up. | + +| PDCP-Config field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| maxCID
Indicates the value of the MAX_CID parameter as specified in TS 38.323 [5].
The total value of MAX_CIDs across all bearers for the UE should be less than or equal to the value of maxNumberROHC-ContextSessions parameter as indicated by the UE. | +| moreThanOneRLC
This field configures UL data transmission when more than one RLC entity is associated with the PDCP entity. This field is not present if the bearer is configured as DAPS bearer. | +| moreThanTwoRLC-DRB
This field configures UL data transmission when more than two RLC entities are associated with the PDCP entity for DRBs. | +| outOfOrderDelivery
Indicates whether or not outOfOrderDelivery specified in TS 38.323 [5] is configured. This field should be either always present or always absent, after the radio bearer is established. | +| pdcp-Duplication
Indicates whether or not uplink duplication status at the time of receiving this IE is configured and activated as specified in TS 38.323 [5]. The presence of this field indicates that duplication is configured. PDCP duplication is not configured for CA packet duplication of LTE RLC bearer. The value of this field, when the field is present, indicates the state of the duplication at the time of receiving this IE. If set to true , duplication is activated. The value of this field is always true , when configured for a SRB. For PDCP entity with more than two associated RLC entities for UL transmission, this field is always present. If the field moreThanTwoRLC-DRB is present, the value of this field is ignored and the state of the duplication is indicated by duplicationState . For PDCP entity with more than two associated RLC entities, only NR RLC bearer is supported. | +| pdcp-SN-SizeDL
PDCP sequence number size for downlink, 12 or 18 bits, as specified in TS 38.323 [5]. For SRBs only the value len12bits is applicable. The value for this field cannot be changed in case of reconfiguration with sync, if the bearer is configured as DAPS bearer. | +| pdcp-SN-SizeUL
PDCP sequence number size for uplink, 12 or 18 bits, as specified in TS 38.323 [5]. For SRBs only the value len12bits is applicable. The value for this field cannot be changed in case of reconfiguration with sync, if the bearer is configured as DAPS bearer. | +| pdu-SetDiscard
If set to true, the UE shall perform PDU set based discarding for this PDCP entity, as specified in TS 38.323 [5]. | +| primaryPath
Indicates the cell group ID and LCID of the primary RLC entity as specified in TS 38.323 [5], clause 5.2.1 for UL data transmission when more than one RLC entity is associated with the PDCP entity. In this version of the specification, only cell group ID corresponding to MCG is supported for SRBs, except for the split SRB2 of the IAB-MT, and except when the UE is required to set the primaryPath to refer to the SCG as specified in clause 5.7.3b.4. In this last case, if the network sends an RRCReconfiguration message (in NR-DC) or an EUTRA RRCConnectionReconfiguration message (in (NG)EN-DC) keeping SRB1 as split SRB, the network explicitly configures the primaryPath for the PDCP entity of SRB1 to refer to the MCG. In this version of the specification, only cell group ID corresponding to MCG is supported for DRBs when the SCG is deactivated. In MR-DC, the NW indicates cellGroup for split bearers using logical channels in different cell groups. The NW always indicates logicalChannel if CA based PDCP duplication is configured in the cell group indicated by cellGroup of this field. In MP, when the primary path is set to indirect path, the field cellGroup and logicalChannel are absent, and the field primaryPathOnIndirectPath is set to true. | +| primaryPathOnIndirectPath
Indicates that the primary RLC entity is on indirect path for DRB when MP is configured. | +| splitSecondaryPath
Indicates the LCID of the split secondary RLC entity as specified in TS 38.323 [5] for fallback to split bearer operation when UL data transmission with more than two RLC entities is associated with the PDCP entity. This RLC entity belongs to a cell group that is different from the cell group indicated by cellGroup in the field primaryPath . | +| statusReportRequired
For AM DRBs, AM MRBs and DAPS UM DRBs, indicates whether the DRB or the multicast MRB is configured to send a PDCP status report in the uplink, as specified in TS 38.323 [5]. For DAPS AM DRBs, it also indicates whether the DRB is configured to send a second PDCP status report in the uplink, as specified in TS 38.323 [5]. | + +| PDCP-Config field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| survivalTimeStateSupport
Indicates whether the DRB associated with this PDCP entity has survival time state support. If this field is configured to be true, all associated RLC entities are activated for PDCP duplication upon reception of a retransmission grant addressed to CS-RNTI, as specified in TS 38.321 [3]. | +| t-Reordering
Value in ms of t-Reordering specified in TS 38.323 [5]. Value ms0 corresponds to 0 ms, value ms20 corresponds to 20 ms, value ms40 corresponds to 40 ms, and so on. When the field is absent the UE applies the value infinity . The value for this field cannot be changed in case of reconfiguration with sync, if the bearer is configured as DAPS bearer. | +| ul-DataSplitThreshold
Parameter specified in TS 38.323 [5]. Value b0 corresponds to 0 bytes, value b100 corresponds to 100 bytes, value b200 corresponds to 200 bytes, and so on. The network sets this field to infinity for UEs not supporting splitDRB-withUL-Both-MCG-SCG and when the SCG is deactivated. If the field is absent when the split bearer is configured for the radio bearer first time, then the default value infinity is applied. | +| uplinkDataCompression
Indicates the UDC configuration that the UE shall apply. Network does not configure uplinkDataCompression for a DRB, if headerCompression or ethernetHeaderCompression is already configured or outOfOrderDelivery or DAPS is configured for the DRB. The maximum number of DRBs where uplinkDataCompression can be applied is two. The network reconfigures uplinkDataCompression only upon reconfiguration involving PDCP re-establishment. If the field is set to drb-ContinueUDC , the PDCP entity continues the uplink data compression protocol during PDCP re-establishment, as specified in TS 38.323 [5]. The field is set to drb-ContinueUDC only in case of resuming an RRC connection or reconfiguration with sync, where the PDCP termination point is not changed and the fullConfig is not indicated. | + +| EthernetHeaderCompression field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| drb-ContinueEHC-DL
Indicates whether the PDCP entity continues or resets the downlink EHC header compression protocol during PDCP re-establishment, as specified in TS 38.323 [5]. The field is configured only in case of resuming an RRC connection or reconfiguration with sync, where the PDCP termination point is not changed and the fullConfig is not indicated. | +| drb-ContinueEHC-UL
Indicates whether the PDCP entity continues or resets the uplink EHC header compression protocol during PDCP re-establishment, as specified in TS 38.323 [5]. The field is configured only in case of resuming an RRC connection or reconfiguration with sync, where the PDCP termination point is not changed and the fullConfig is not indicated. | +| ehc-CID-Length
Indicates the length of the CID field for EHC packet. The value bits7 indicates the length is 7 bits, and the value bits15 indicates the length is 15 bits. Once the field ethernetHeaderCompression-r16 is configured for a DRB or a multicast MRB, the value of the field ehc-CID-Length for this DRB or multicast MRB is not reconfigured to a different value. | +| ehc-Common
Indicates the configurations that apply for both downlink and uplink. | +| ehc-Downlink
Indicates the configurations that apply for only downlink. If the field is configured, then Ethernet header compression is configured for downlink. Otherwise, it is not configured for downlink. | +| ehc-Uplink
Indicates the configurations that apply for only uplink. If the field is configured, then Ethernet header compression is configured for uplink. Otherwise, it is not configured for uplink. | +| maxCID-EHC-UL
Indicates the value of the MAX_CID_EHC_UL parameter as specified in TS 38.323 [5]. The total value of MAX_CID_EHC_UL across all bearers for the UE should be less than or equal to the value of maxNumberEHC-Contexts parameter as indicated by the UE. | + +| UplinkDataCompression field descriptions | | +|-------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| bufferSize | This field indicates the buffer size applied for UDC as specified in TS 38.323 [5]. Value kbyte2 means 2048 bytes, kbyte4 means 4096 bytes and so on. | +| dictionary | This field indicates which pre-defined dictionary is used for UDC as specified in TS 38.323 [5]. The value sip-SDP means that UE shall prefill the buffer with standard dictionary for SIP and SDP defined in TS 38.323 [5], and the value operator means that UE shall prefill the buffer with operator-defined dictionary. | + +| Conditional presence | Explanation | +|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DRB | This field is mandatory present when the corresponding DRB/multicast MRB is being set up, absent for SRBs. Otherwise this field is optionally present, need M. | +| DRB2 | This field is optionally present in case of DRB, need M. Otherwise, it is absent for SRBs and MRBs. | +| Drb-Duplication | For SRBs, this field is absent. For DRBs, this field is absent if duplication is not configured. Otherwise, this field is optional, need R. | +| MoreThanOneRLC | This field is mandatory present upon RRC reconfiguration with setup of a PDCP entity for a radio bearer (except for multicast MRB) with more than one associated logical channel and upon RRC reconfiguration with the association of additional logical channels to the PDCP entity.
The field is also mandatory present in case the field moreThanTwoRLC-DRB is included in PDCP-Config .
Upon RRC reconfiguration when a PDCP entity is associated with multiple logical channels, this field is optionally present need M.
Otherwise, this field is absent. Need R. | +| MoreThanTwoRLC-DRB | For SRBs, this field is absent.
For DRBs, this field is mandatory present upon RRC reconfiguration with setup of a PDCP entity for a radio bearer with more than two associated logical channels and upon RRC reconfiguration with the association of one or more additional logical channel(s) to the PDCP entity so that the PDCP entity has more than two associated logical channels.
Upon RRC reconfiguration when a PDCP entity is associated with more than two logical channels, this field is optionally present, Need M.
Otherwise, the field is absent, Need R. | +| Rlc-AM | For RLC AM, the field is optionally present, need M. Otherwise, the field is absent. | +| Rlc-AM-UM | In case of DRB, for RLC UM (if the UE supports DAPS handover) or RLC AM, the field is optionally present, need R. In case of multicast MRB, if multicast MRB is associated with at least one RLC AM entity, the field is optionally present, need R. Otherwise, the field is absent. | +| Setup | The field is mandatory present in case of DRB setup. Otherwise the field is optionally present, need M. | +| SplitBearer | The field is absent for SRBs. Otherwise, the field is optional present, need M, in case of radio bearer with more than one associated RLC mapped to different cell groups. | +| SplitBearer2 | The field is mandatory present, in case of a split bearer. Otherwise the field is absent. | +| SplitBearerMP | The field is absent for SRBs. Otherwise, the field is optional present, need M, when MP is configured. | +| ConnectedTo5GC | The field is optionally present, need R, if the UE is connected to 5GC. Otherwise the field is absent. | +| ConnectedTo5GC1 | The field is optionally present, need R, if the UE is connected to NR/5GC or if the UE supports user plane integrity protection when connected to E-UTRA/EPC (as specified in TS 33.401 [30]). Otherwise the field is absent. | +| Setup1 | This field is mandatory present in case of DRB setup for RLC-AM and RLC-UM. Otherwise, this field is absent, Need M. | +| Setup2 | This field is mandatory present in case for radio bearer setup for RLC-AM and RLC-UM. Otherwise, this field is absent, Need M. | +| MRB-Initialization | This field is mandatory present in case of multicast MRB setup. In case of PDCP re-establishment for multicast MRB, this field is optionally present, Need N. Otherwise, this field is absent, Need N. | + +#### — PDSCH-Config + +The *PDSCH-Config* IE is used to configure the UE specific PDSCH parameters. If this IE is used for MBS CFR, the following fields shall be absent: *tci-StatesToAddModList*, *tci-StatesToReleaseList*, *zp-CSI-RS-ResourceToAddModList*, *minimumSchedulingOffsetK0*, *antennaPortsFieldPresenceDCI-1-2*, *aperiodicZP-CSI-RS-ResourceSetsToAddModListDCI-1-2*, *aperiodicZP-CSI-RS-ResourceSetsToReleaseListDCI-1-2*, *dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2*, *dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2*, *dmrs-SequenceInitializationDCI-1-2*, *harq-ProcessNumberSizeDCI-1-2*, *mcs-TableDCI-1-2*, *numberOfBitsForRV-DCI-1-2*, *pdsch-AggregationFactor*, *pdsch-TimeDomainAllocationListDCI-1-2*, *prb-BundlingTypeDCI-1-2*, *priorityIndicatorDCI-1-2*, *rateMatchPatternGroup1DCI-1-2*, *rateMatchPatternGroup2DCI-1-2*, *resourceAllocationType1GranularityDCI-1-2*, *vrb-ToPRB-InterleaverDCI-1-2*, *referenceOfSLIVDCI-1-2*, *resourceAllocationDCI-1-2*, *dataScramblingIdentityPDSCH2-r16*, *repetitionSchemeConfig*, *pdsch-ConfigDCI-1-3*. + +#### PDSCH-Config information element + +``` +-- ASN1START +-- TAG-PDSCH-CONFIG-START + +PDSCH-Config ::= + SEQUENCE { + dataScramblingIdentityPDSCH INTEGER (0..1023) OPTIONAL, -- Need S + dmrs-DownlinkForPDSCH-MappingTypeA SetupRelease { DMRS-DownlinkConfig } OPTIONAL, -- Need M + dmrs-DownlinkForPDSCH-MappingTypeB SetupRelease { DMRS-DownlinkConfig } OPTIONAL, -- Need M + + tci-StatesToAddModList SEQUENCE (SIZE(1..maxNrofTCI-States)) OF TCI-State OPTIONAL, -- Need N + tci-StatesToReleaseList SEQUENCE (SIZE(1..maxNrofTCI-States)) OF TCI-StateId OPTIONAL, -- Need N + vrb-ToPRB-Interleaver ENUMERATED {n2, n4} OPTIONAL, -- Need S + resourceAllocation ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch}, OPTIONAL, -- Need M + pdsch-TimeDomainAllocationList SetupRelease { PDSCH-TimeDomainResourceAllocationList } OPTIONAL, -- Need S + pdsch-AggregationFactor ENUMERATED { n2, n4, n8 } OPTIONAL, -- Need S + rateMatchPatternToAddModList SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF RateMatchPattern OPTIONAL, -- Need N + rateMatchPatternToReleaseList SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF RateMatchPatternId OPTIONAL, -- Need N + rateMatchPatternGroup1 RateMatchPatternGroup OPTIONAL, -- Need R + rateMatchPatternGroup2 RateMatchPatternGroup OPTIONAL, -- Need R + + rbg-Size ENUMERATED {config1, config2}, OPTIONAL, -- Need S + mcs-Table ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need R + maxNrofCodeWordsScheduledByDCI ENUMERATED {n1, n2} OPTIONAL, -- Need R + + prb-BundlingType CHOICE { + staticBundling + SEQUENCE { + bundleSize + ENUMERATED { n4, wideband } OPTIONAL -- Need S + }, + dynamicBundling + SEQUENCE { + bundleSizeSet1 + ENUMERATED { n4, wideband, n2-wideband, n4-wideband } OPTIONAL, -- Need S + bundleSizeSet2 + ENUMERATED { n4, wideband } OPTIONAL -- Need S + } + }, + zp-CSI-RS-ResourceToAddModList SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-Resources)) OF ZP-CSI-RS-Resource OPTIONAL, -- Need N + zp-CSI-RS-ResourceToReleaseList SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-Resources)) OF ZP-CSI-RS-ResourceId OPTIONAL, -- Need N + } +-- ASN1END +``` + +``` + +aperiodic-ZP-CSI-RS-ResourceSetsToAddModList SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSet + OPTIONAL, -- Need N +aperiodic-ZP-CSI-RS-ResourceSetsToReleaseList SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSetId + OPTIONAL, -- Need N +sp-ZP-CSI-RS-ResourceSetsToAddModList SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSet + OPTIONAL, -- Need N +sp-ZP-CSI-RS-ResourceSetsToReleaseList SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSetId + OPTIONAL, -- Need N +p-ZP-CSI-RS-ResourceSet SetupRelease { ZP-CSI-RS-ResourceSet } + OPTIONAL, -- Need M +... +[[ +maxMIMO-Layers-r16 SetupRelease { MaxMIMO-LayersDL-r16 } + OPTIONAL, -- Need M +minimumSchedulingOffsetK0-r16 SetupRelease { MinSchedulingOffsetK0-Values-r16 } + OPTIONAL, -- Need M + +-- Start of the parameters for DCI format 1_2 introduced in V16.1.0 +antennaPortsFieldPresenceDCI-1-2-r16 ENUMERATED {enabled} + OPTIONAL, -- Need S +aperiodicZP-CSI-RS-ResourceSetsToAddModListDCI-1-2-r16 SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSet + OPTIONAL, -- Need N +aperiodicZP-CSI-RS-ResourceSetsToReleaseListDCI-1-2-r16 SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSetId + OPTIONAL, -- Need N +dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2-r16 SetupRelease { DMRS-DownlinkConfig } + OPTIONAL, -- Need M +dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2-r16 SetupRelease { DMRS-DownlinkConfig } + OPTIONAL, -- Need M +dmrs-SequenceInitializationDCI-1-2-r16 ENUMERATED {enabled} + OPTIONAL, -- Need S +harq-ProcessNumberSizeDCI-1-2-r16 INTEGER (0..4) + OPTIONAL, -- Need R +mcs-TableDCI-1-2-r16 ENUMERATED {qam256, qam64LowSE} + OPTIONAL, -- Need S +numberOfBitsForRV-DCI-1-2-r16 INTEGER (0..2) + OPTIONAL, -- Need R +pdsch-TimeDomainAllocationListDCI-1-2-r16 SetupRelease { PDSCH-TimeDomainResourceAllocationList-r16 } + OPTIONAL, -- Need M + +prb-BundlingTypeDCI-1-2-r16 CHOICE { + staticBundling-r16 SEQUENCE { + bundleSize-r16 ENUMERATED { n4, wideband } + OPTIONAL -- Need S + }, + dynamicBundling-r16 SEQUENCE { + bundleSizeSet1-r16 ENUMERATED { n4, wideband, n2-wideband, n4-wideband } + OPTIONAL, -- Need S + bundleSizeSet2-r16 ENUMERATED { n4, wideband } + OPTIONAL -- Need S + } +} + OPTIONAL, -- Need R +priorityIndicatorDCI-1-2-r16 ENUMERATED {enabled} + OPTIONAL, -- Need S +rateMatchPatternGroup1DCI-1-2-r16 RateMatchPatternGroup + OPTIONAL, -- Need R +rateMatchPatternGroup2DCI-1-2-r16 RateMatchPatternGroup + OPTIONAL, -- Need R +resourceAllocationType1GranularityDCI-1-2-r16 ENUMERATED {n2, n4, n8, n16} + OPTIONAL, -- Need S +vrb-ToPRB-InterleaverDCI-1-2-r16 ENUMERATED {n2, n4} + OPTIONAL, -- Need S +referenceOfSLIVDCI-1-2-r16 ENUMERATED {enabled} + OPTIONAL, -- Need S +resourceAllocationDCI-1-2-r16 ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch} + OPTIONAL, -- Need M + +-- End of the parameters for DCI format 1_2 introduced in V16.1.0 + +priorityIndicatorDCI-1-1-r16 ENUMERATED {enabled} + OPTIONAL, -- Need S +dataScramblingIdentityPDSCH2-r16 INTEGER (0..1023) + OPTIONAL, -- Need R +pdsch-TimeDomainAllocationList-r16 SetupRelease { PDSCH-TimeDomainResourceAllocationList-r16 } + OPTIONAL, -- Need M + +``` + +``` + +repetitionSchemeConfig-r16 SetupRelease { RepetitionSchemeConfig-r16 } OPTIONAL -- Need M +]], +[[ +repetitionSchemeConfig-v1630 SetupRelease { RepetitionSchemeConfig-v1630 } OPTIONAL -- Need M +]], +[[ +pdsch-HARQ-ACK-OneShotFeedbackDCI-1-2-r17 ENUMERATED {enabled} OPTIONAL, -- Need R +pdsch-HARQ-ACK-EnhType3DCI-1-2-r17 ENUMERATED {enabled} OPTIONAL, -- Need R +pdsch-HARQ-ACK-EnhType3DCI-Field-1-2-r17 ENUMERATED {enabled} OPTIONAL, -- Need R +pdsch-HARQ-ACK-RetxDci-1-2-r17 ENUMERATED {enabled} OPTIONAL, -- Need R +pucch-sSCellDynDCI-1-2-r17 ENUMERATED {enabled} OPTIONAL, -- Need R +dl-OrJointTCI-StateList-r17 CHOICE { + explicitList SEQUENCE { + dl-OrJointTCI-StateToAddModList-r17 SEQUENCE (SIZE (1..maxNrofTCI-States)) OF TCI-State + dl-OrJointTCI-StateToReleaseList-r17 SEQUENCE (SIZE (1..maxNrofTCI-States)) OF TCI-StateId + }, + unifiedTCI-StateRef-r17 ServingCellAndBWP-Id-r17 +} +beamAppTime-r17 ENUMERATED {n1, n2, n4, n7, n14, n28, n42, n56, n70, n84, n98, n112, n224, n336, spare2, + spare1} +dummy SetupRelease { Dummy-TDRA-List } +dmrs-FD-OCC-DisabledForRank1-PDSCH-r17 ENUMERATED {true} +minimumSchedulingOffsetK0-r17 SetupRelease { MinSchedulingOffsetK0-Values-r17 } +harq-ProcessNumberSizeDCI-1-2-v1700 INTEGER (0..5) +harq-ProcessNumberSizeDCI-1-1-r17 INTEGER (5) +mcs-Table-r17 ENUMERATED {qam1024} +mcs-TableDCI-1-2-r17 ENUMERATED {qam1024} +xOverheadMulticast-r17 ENUMERATED {xOh6, xOh12, xOh18} +priorityIndicatorDCI-4-2-r17 ENUMERATED {enabled} +sizeDCI-4-2-r17 INTEGER (20..maxDCI-4-2-Size-r17) +]], +[[ +pdsch-TimeDomainAllocationListForMultiPDSCH-r17 SetupRelease { MultiPDSCH-TDRA-List-r17 } OPTIONAL -- Need M +]], +[[ +advancedReceiver-MU-MIMO-r18 SetupRelease { AdvancedReceiver-MU-MIMO-r18 } OPTIONAL, -- Need M +pdsch-ConfigDCI-1-3-r18 SetupRelease { PDSCH-ConfigDCI-1-3-r18 } OPTIONAL -- Need M +]] +} + +RateMatchPatternGroup ::= SEQUENCE (SIZE (1..maxNrofRateMatchPatternsPerGroup)) OF CHOICE { + cellLevel RateMatchPatternId, + bwpLevel RateMatchPatternId +} + +MinSchedulingOffsetK0-Values-r16 ::= SEQUENCE (SIZE (1..maxNrOfMinSchedulingOffsetValues-r16)) OF INTEGER (0..maxK0-SchedulingOffset-r16) + +MinSchedulingOffsetK0-Values-r17 ::= SEQUENCE (SIZE (1..maxNrOfMinSchedulingOffsetValues-r16)) OF INTEGER (0..maxK0-SchedulingOffset-r17) + +``` + +``` +MaxMIMO-LayersDL-r16 ::= INTEGER (1..8) + +PDSCH-ConfigDCI-1-3-r18 ::= SEQUENCE { + resourceAllocationDCI-1-3-r18 ENUMERATED {resourceAllocationType0, resourceAllocationType1, dynamicSwitch} + OPTIONAL, -- Need M + rbg-SizeDCI-1-3-r18 ENUMERATED {config1, config2, config3} OPTIONAL, -- Cond DCI-1-3 + resourceAllocationType1GranularityDCI-1-3-r18 ENUMERATED {n2,n4,n8,n16} OPTIONAL, -- Need S + numberOfBitsForRV-DCI-1-3-r18 INTEGER (0..2) OPTIONAL, -- Need R + harq-ProcessNumberSizeDCI-1-3-r18 INTEGER (0..5) OPTIONAL -- Need R +} + +-- TAG-PDSCH-CONFIG-STOP +-- ASN1STOP +``` + +| PDSCH-Config field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| advancedReceiver-MU-MIMO
A set of assistance information for R-ML (reduced complexity ML) receivers with enhanced inter-user interference suppression for MU-MIMO transmissions. | +| antennaPortsFieldPresenceDCI-1-2
Configure the presence of "Antenna ports" field in DCI format 1_2. When the field is configured, then the "Antenna ports" field is present in DCI format 1_2. Otherwise, the field size is set to 0 for DCI format 1_2 (See TS 38.212 [17], clause 7.3.1.1.3). If neither dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2 nor dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2 is configured, this field is absent. | +| aperiodic-ZP-CSI-RS-ResourceSetsToAddModList, aperiodic-ZP-CSI-RS-ResourceSetsToAddModListDCI-1-2
AddMod/Release lists for configuring aperiodically triggered zero-power CSI-RS resource sets. Each set contains a ZP-CSI-RS-ResourceSetId and the IDs of one or more ZP-CSI-RS-Resources (the actual resources are defined in the zp-CSI-RS-ResourceToAddModList ). The network configures the UE with at most 3 aperiodic ZP-CSI-RS-ResourceSets and it uses only the ZP-CSI-RS-ResourceSetId 1 to 3. The network triggers a set by indicating its ZP-CSI-RS-ResourceSetId in the DCI payload. The DCI codepoint '01' triggers the resource set with ZP-CSI-RS-ResourceSetId 1, the DCI codepoint '10' triggers the resource set with ZP-CSI-RS-ResourceSetId 2, and the DCI codepoint '11' triggers the resource set with ZP-CSI-RS-ResourceSetId 3 (see TS 38.214 [19], clause 5.1.4.2). The field aperiodic-ZP-CSI-RS-ResourceSetsToAddModList applies to DCI format 1_1 and the field aperiodic-ZP-CSI-RS-ResourceSetsToAddModListDCI-1-2 applies to DCI format 1_2 (see TS 38.214 [19], clause 5.1.4.2 and TS 38.212 [17] clause 7.3.1). | +| beamAppTime
Indicates the first slot to apply the unified TCI indicated by DCI as specified in TS 38.214 Clause 5.1.5. The value n1 means 1 symbol, n2 two symbols and so on. The first slot is at least Y symbols indicated by beamAppTime parameter after the last symbol of the acknowledgment of the joint or separate DL/UL beam indication. The same value shall be configured for all serving cells in any one of the simultaneousU-TCI-UpdateListN configured in IE CellGroupConfig based on the smallest SCS of the active BWP. | +| dataScramblingIdentityPDSCH, dataScramblingIdentityPDSCH2
Identifier(s) used to initialize data scrambling ( c_init ) for PDSCH as specified in TS 38.211 [16], clause 7.3.1.1. The dataScramblingIdentityPDSCH2 is configured if coresetPoolIndex is configured with 1 for at least one CORESET in the same BWP. | +| dl-OrJointTCI-StateToAddModList
A list of Transmission Configuration Indicator (TCI) states indicating a transmission configuration which includes QCL-relationships between the DL RSs in one RS set and the PDSCH DMRS ports, PDCCH DMRS ports, and CSI-RS, and in case of join mode, also the PUSCH, PUCCH and SRS (see TS 38.214 [19], clause 5.1.5). | +| dmrs-DownlinkForPDSCH-MappingTypeA, dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2
DMRS configuration for PDSCH transmissions using PDSCH mapping type A (chosen dynamically via PDSCH-TimeDomainResourceAllocation ). Only the fields dmrs-Type , dmrs-AdditionalPosition and maxLength may be set differently for mapping type A and B. The field dmrs-DownlinkForPDSCH-MappingTypeA applies to DCI format 1_1 and the field dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2 applies to DCI format 1_2 (see TS 38.212 [17], clause 7.3.1). | +| dmrs-DownlinkForPDSCH-MappingTypeB, dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2
DMRS configuration for PDSCH transmissions using PDSCH mapping type B (chosen dynamically via PDSCH-TimeDomainResourceAllocation ). Only the fields dmrs-Type , dmrs-AdditionalPosition and maxLength may be set differently for mapping type A and B. The field dmrs-DownlinkForPDSCH-MappingTypeB applies to DCI format 1_1 and the field dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2 applies to DCI format 1_2 (see TS 38.212 [17], clause 7.3.1). | +| dmrs-FD-OCC-DisabledForRank1-PDSCH
If configured, the UE may assume that the set of remaining orthogonal antenna ports, which are within the same code division multiplexing (CDM) group and have different frequency domain orthogonal cover codes (FD-OCC), are not associated with the PDSCH of another UE (see TS 38.214 [19], clause 5.1.6.2). It is applicable for PDSCH SCS of 480 and 960 kHz when rank 1 PDSCH with type-1 or type-2 DMRS is scheduled. If dmrs-TypeEnh-r18 is configured, this field is not configured. | +| dmrs-SequenceInitializationDCI-1_2
Configure whether the field "DMRS Sequence Initialization" is present or not in DCI format 1_2. If the field is absent, then the UE applies the value of 0 bit for the field "DMRS Sequence Initialization" in DCI format 1_2. If the field is present, then the UE applies the value of 1 bit as in DCI format 1_2 (see TS 38.212 [17], clause 7.3.1). | +| dummy
This field is not used in the specification. If received it shall be ignored by the UE. | +| harq-ProcessNumberSizeDCI-1-2
Configure the number of bits for the field "HARQ process number" in DCI format 1_2 (see TS 38.212 [17], clause 7.3.1). | + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| maxMIMO-Layers
Indicates the maximum number of MIMO layers to be used for PDSCH in this DL BWP. If not configured, the UE uses the maxMIMO-Layers configuration in IE PDSCH-ServingCellConfig of the serving cell to which this BWP belongs, when the UE operates in this BWP. The value of maxMIMO-Layers for a DL BWP shall be smaller than or equal to the value of maxMIMO-Layers configured in IE PDSCH-ServingCellConfig of the serving cell to which this BWP belongs.
For MBS multicast, indicates the maximum number of MIMO layers to be used for group-common PDSCH of MBS multicast in this CFR. If not configured for CFR, the UE applies value 1. The value of maxMIMO-Layers for a CFR shall be smaller than or equal to the value of maxMIMO-Layers configured in PDSCH-ServingCellConfig IE of the serving cell to which this CFR belongs. | +| maxNrofCodeWordsScheduledByDCI
Maximum number of code words that a single DCI may schedule. This changes the number of MCS/RV/NDI bits in the DCI message from 1 to 2. | +| mcs-Table
Indicates which MCS table the UE shall use for PDSCH for DCI formats 1_0 and 1_1 (see TS 38.214 [19], clause 5.1.3.1). If all fields are absent the UE applies the value 64QAM. If the field mcs-Table-r17 is present for DCI format 1_1, the network does not configure the field mcs-Table (without suffix). For an (e)RedCap UE, the 256QAM MCS table for PDSCH is only supported if the UE indicates support of 256QAM for PDSCH. | +| mcs-TableDCI-1-2
Indicates which MCS table the UE shall use for PDSCH for DCI format 1_2 (see TS 38.214 [19], clause 5.1.3.1). If all fields are absent the UE applies the value 64QAM. If the field mcs-TableDCI-1-2-r17 is present, the network does not configure the field mcs-TableDCI-1-2-r16 . For an (e)RedCap UE, the 256QAM MCS table for PDSCH is only supported if the UE indicates support of 256QAM for PDSCH. | +| minimumSchedulingOffsetK0
List of minimum K0 values. Minimum K0 parameter denotes minimum applicable value(s) for the TDRA table for PDSCH and for A-CSI RS triggering Offset(s) (see TS 38.214 [19], clause 5.3.1). | +| numberOfBitsForRV-DCI-1-2
Configures the number of bits for "Redundancy version" in the DCI format 1_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.214 [19], clause 5.1.2.1). | +| pdsch-AggregationFactor
Number of repetitions for data (see TS 38.214 [19], clause 5.1.2.1). When the field is absent in PDSCH-Config which is not used for MBS CFR, the UE applies the value 1. | +| pdsch-HARQ-ACK-EnhType3DCI-1-2
When configured, enhanced Type 3 HARQ-ACK codebook triggering by DCI format 1_2 is enabled. | +| pdsch-HARQ-ACK-EnhType3DCI-Field-1-2
Enables the enhanced Type 3 codebook through a new DCI field to indicate the enhanced Type 3 HARQ-ACK codebook in DCI format 1_2 if the more than one enhanced Type 3 HARQ-ACK codebook is configured for the primary PUCCH cell group. | +| pdsch-HARQ-ACK-OneShotFeedbackDCI-1-2
When configured, DCI format 1_2 can request the UE to report A/N for all HARQ processes and all component carriers configured in the PUCCH group (see TS 38.212 [17], clause 7.3.1). | +| pdsch-HARQ-ACK-RetxDCI-1-2
When configured, DCI format 1_2 can request the UE to perform a HARQ-ACK re-transmission on a PUCCH resource (see TS 38.213 [13], clause 9.1.5). | +| pdsch-TimeDomainAllocationList, pdsch-TimeDomainAllocationListDCI-1-2, pdsch-TimeDomainAllocationListForMultiPDSCH
List of time-domain configurations for timing of DL assignment to DL data.
The field pdsch-TimeDomainAllocationList (with or without suffix) applies to DCI format 1_0 and DCI format 1_1 (see table 5.1.2.1.1-1 in TS 38.214 [19]), and if the field pdsch-TimeDomainAllocationListDCI-1-2 is not configured, to DCI format 1_2. If the field pdsch-TimeDomainAllocationListDCI-1-2 is configured, it applies to DCI format 1_2 (see table 5.1.2.1.1-1A in TS 38.214 [19]). The field pdsch-TimeDomainAllocationListForMultiPDSCH applies to DCI format 1_1.
The network does not configure the pdsch-TimeDomainAllocationList-r16 simultaneously with the pdsch-TimeDomainAllocationList (without suffix) in the same PDSCH-Config . | +| prb-BundlingType, prb-BundlingTypeDCI-1-2
Indicates the PRB bundle type and bundle size(s) (see TS 38.214 [19], clause 5.1.2.3). If dynamic is chosen, the actual bundleSizeSet1 or bundleSizeSet2 to use is indicated via DCI. Constraints on bundleSize(Set) setting depending on vrB-ToPRB-Interleaver and rbg-Size settings are described in TS 38.214 [19], clause 5.1.2.3. If a bundleSize(Set) value is absent, the UE applies the value n2 . The field prb-BundlingType applies to DCI format 1_1, and the field prb-BundlingTypeDCI-1-2 applies to DCI | + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| format 1_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.214 [19], clause 5.1.2.3). | +| priorityIndicatorDCI-1-1, priorityIndicatorDCI-1-2, priorityIndicatorDCI-4-2
Configure the presence of "priority indicator" in DCI format 1_1/1_2/4_2. When the field is absent in the IE, then 0 bit for "priority indicator" in DCI format 1_1/1_2/4_2. The field priorityIndicatorDCI-1-1 applies to DCI format 1_1, the field priorityIndicatorDCI-1-2 applies to DCI format 1_2 and the field priorityIndicatorDCI-4-2 applies to DCI format 4_2, respectively (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13] clause 9). | +| pucch-sSCellDynDCI-1-2
When configured, PUCCH cell switching based on dynamic indication in DCI format 1_2 is enabled (see TS 38.213 [13], clause 9.A). | +| p-ZP-CSI-RS-ResourceSet
A set of periodically occurring ZP-CSI-RS-Resources (the actual resources are defined in the zp-CSI-RS-ResourceToAddModList ). The network uses the ZP-CSI-RS-ResourceSetId=0 for this set.
If p-ZP-CSI-RS-ResourceSet is configured in both PDSCH-Config for MBS CFR and PDSCH-Config for the associated BWP, it is subject to UE capability whether the p-ZP-CSI-RS-ResourceSet configured in PDSCH-Config for MBS CFR can be different from the p-ZP-CSI-RS-ResourceSet configured in PDSCH-Config for the associated BWP. | +| rateMatchPatternGroup1, rateMatchPatternGroup1DCI-1-2
The IDs of a first group of RateMatchPatterns defined in PDSCH-Config->rateMatchPatternToAddModList (BWP level) or in ServingCellConfig->rateMatchPatternToAddModList (cell level). These patterns can be activated dynamically by DCI (see TS 38.214 [19], clause 5.1.4.1). The field rateMatchPatternGroup1 applies to DCI format 1_1, and the field rateMatchPatternGroup1DCI-1-2 applies to DCI format 1_2 (see TS 38.214 [19], clause 5.1.4.1). | +| rateMatchPatternGroup2, rateMatchPatternGroup2DCI-1-2
The IDs of a second group of RateMatchPatterns defined in PDSCH-Config->rateMatchPatternToAddModList (BWP level) or in ServingCellConfig->rateMatchPatternToAddModList (cell level). These patterns can be activated dynamically by DCI (see TS 38.214 [19], clause 5.1.4.1). The field rateMatchPatternGroup2 applies to DCI format 1_1, and the field rateMatchPatternGroup2DCI-1-2 applies to DCI format 1_2 (see TS 38.214 [19], clause 5.1.4.1). | +| rateMatchPatternToAddModList
Resources patterns which the UE should rate match PDSCH around. The UE rate matches around the union of all resources indicated in the rate match patterns (see TS 38.214 [19], clause 5.1.4.1). If a RateMatchPattern with the same RateMatchPatternId is configured in both MBS CFR and its associated BWP, the entire RateMatchPattern configuration, including the set of RBs/REs indicated by the patterns for the rate matching around, shall be the same and they are counted as a single rate match pattern in the total configured rate match patterns as defined in TS 38.214 [19]. | +| rbg-Size
Selection between config 1 and config 2 for RBG size for PDSCH. The UE ignores this field if resourceAllocation is set to resourceAllocationType1 (see TS 38.214 [19], clause 5.1.2.2.1). | +| referenceOfSLIVDCI-1-2
Enable using the starting symbol of the PDCCH monitoring occasion in which the DL assignment is detected as the reference of the SLIV for DCI format 1_2. When the RRC parameter enables the utilization of the new reference, the new reference is applied for TDRA entries with K0=0. For other entries (if any) in the same TDRA table, the reference is slot boundary as in Rel-15. PDSCH mapping type A is not supported with the new reference. The new reference of SLIV is not configured for a serving cell configured to be scheduled by cross-carrier scheduling on a scheduling cell with different numerology (see TS 38.212 [17] clause 7.3.1 and TS 38.214 [19] clause 5.1.2.1). | +| repetitionSchemeConfig
Configure the UE with repetition schemes. The network does not configure repetitionSchemeConfig-r16 and repetitionSchemeConfig-v1630 simultaneously to setup in the same PDSCH-Config . The network does not configure this parameter and sfnSchemePDSCH in MIMOParam-r17 simultaneously in the same serving cell. | +| resourceAllocation, resourceAllocationDCI-1-2
Configuration of resource allocation type 0 and resource allocation type 1 for non-fallback DCI (see TS 38.214 [19], clause 5.1.2.2). The field resourceAllocation applies to DCI format 1_1, and the field resourceAllocationDCI-1-2 applies to DCI format 1_2 (see TS 38.214 [19], clause 5.1.2.2). | +| resourceAllocationType1GranularityDCI-1-2
Configure the scheduling granularity applicable for both the starting point and length indication for resource allocation type 1 in DCI format 1_2. If this field is absent, the granularity is 1 PRB (see TS 38.214 [19], clause 5.1.2.2.2). | +| sizeDCI-4-2
Indicates the size of DCI format 4-2 (see TS 38.213 [13], clause 10.1). | + +| | | +|------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sp-ZP-CSI-RS-ResourceSetsToAddModList | AddMod/Release lists for configuring semi-persistent zero-power CSI-RS resource sets. Each set contains a ZP-CSI-RS-ResourceSetId and the IDs of one or more ZP-CSI-RS-Resources (the actual resources are defined in the zp-CSI-RS-ResourceToAddModList ) (see TS 38.214 [19], clause 5.1.4.2). | +| tci-StatesToAddModList | A list of Transmission Configuration Indicator (TCI) states indicating a transmission configuration which includes QCL-relationships between the DL RSs in one RS set and the PDSCH DMRS ports (see TS 38.214 [19], clause 5.1.5). If unifiedTCI-StateType is configured for the serving cell, no element in this list is configured. | +| unifiedTCI-StateRef | Provides the serving cell and BWP where the configuration for dl-OrJointTCI-StateToAddModList-r17 are defined. When this field is present, dl-OrJointTCI-StateToAddModList and dl-OrJointTCI-StateToReleaseList are not present. The value of unifiedTCI-StateType of current serving cell is the same in the serving cell indicated by unifiedTCI-StateRef . | +| vrb-ToPRB-Interleaver, vrb-ToPRB-InterleaverDCI-1-2 | Interleaving unit configurable between 2 and 4 PRBs (see TS 38.211 [16], clause 7.3.1.6). When the field is absent, the UE performs non-interleaved VRB-to-PRB mapping. | +| xOverheadMulticast | Accounts for an overhead from CSI-RS, CORESET etc. If the field is absent, the UE applies value xOh0 (see TS 38.214 [19]). | +| zp-CSI-RS-ResourceToAddModList | A list of Zero-Power (ZP) CSI-RS resources used for PDSCH rate-matching. Each resource in this list may be referred to from only one type of resource set, i.e., aperiodic, semi-persistent or periodic (see TS 38.214 [19]). | + +| PDSCH-ConfigDCI-1-3 field descriptions | | +|--------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| harq-ProcessNumberSizeDCI-1-3 | Configure the number of bits for the field "HARQ process number" in DCI format 1_3 (see TS 38.212 [17], clause 7.3.1). | +| numberOfBitsForRV-DCI-1-3 | Configures the number of bits for "Redundancy version" in the DCI format 1_3 (see TS 38.212 [17], clause 7.3.1 and TS 38.214 [19], clause 5.1.2.1). | +| rbg-SizeDCI-1-3 | Selection among config 1, config 2 and config 3 for RBG size for PDSCH. The UE ignores this field if resourceAllocationDCI-1-3 is set to resourceAllocationType1. (see TS 38.214 [19], clause 5.1.2.2.1). | +| resourceAllocationDCI-1-3 | Configuration of resource allocation type 0 and resource allocation type 1 for non-fallback DCI (see TS 38.214 [19], clause 5.1.2.2). | +| resourceAllocationType1GranularityDCI-1-3 | Configure the scheduling granularity applicable for both the starting point and length indication for resource allocation type 1 in DCI format 1_3. If this field is absent, the granularity is 1 PRB (see TS 38.214 [19], clause 5.1.2.2.2). | + +| Conditional Presence | Explanation | +|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------| +| DCI-1-3 | This field is mandatory present when ScheduledCellListDCI-1-3 is configured to the serving cell. It is absent otherwise. | + +#### – PDSCH-ConfigCommon + +The IE *PDSCH-ConfigCommon* is used to configure cell specific PDSCH parameters. + +#### **PDSCH-ConfigCommon information element** + +-- ASN1START + +``` + +-- TAG-PDSCH-CONFIGCOMMON-START + +PDSCH-ConfigCommon ::= SEQUENCE { + pdsch-TimeDomainAllocationList PDSCH-TimeDomainResourceAllocationList OPTIONAL, -- Need R + ... +} + +-- TAG-PDSCH-CONFIGCOMMON-STOP +-- ASN1STOP + +``` + +#### PDSCH-ConfigCommon field descriptions + +##### **pdsch-TimeDomainAllocationList** + +List of time-domain configurations for timing of DL assignment to DL data (see table 5.1.2.1.1-1 in TS 38.214 [19]). + +#### – PDSCH-ServingCellConfig + +The IE *PDSCH-ServingCellConfig* is used to configure UE specific PDSCH parameters that are common across the UE's BWPs of one serving cell. + +#### PDSCH-ServingCellConfig information element + +``` + +-- ASN1START +-- TAG-PDSCH-SERVINGCELLCONFIG-START + +PDSCH-ServingCellConfig ::= SEQUENCE { + codeBlockGroupTransmission SetupRelease { PDSCH-CodeBlockGroupTransmission } OPTIONAL, -- Need M + xOverhead ENUMERATED { xOh6, xOh12, xOh18 } OPTIONAL, -- Need S + nrofHARQ-ProcessesForPDSCH ENUMERATED { n2, n4, n6, n10, n12, n16 } OPTIONAL, -- Need S + pucch-Cell ServCellIndex OPTIONAL, -- Cond SCellAddOnly + ... + [[ + maxMIMO-Layers INTEGER (1..8) OPTIONAL, -- Need M + processingType2Enabled BOOLEAN OPTIONAL -- Need M + ]], + [[ + pdsch-CodeBlockGroupTransmissionList-r16 SetupRelease { PDSCH-CodeBlockGroupTransmissionList-r16 } OPTIONAL -- Need M + ]], + [[ + downlinkHARQ-FeedbackDisabled-r17 SetupRelease { DownlinkHARQ-FeedbackDisabled-r17 } OPTIONAL, -- Need M + nrofHARQ-ProcessesForPDSCH-v1700 ENUMERATED { n32 } OPTIONAL -- Need R + ]] +} + +PDSCH-CodeBlockGroupTransmission ::= SEQUENCE { + maxCodeBlockGroupsPerTransportBlock ENUMERATED { n2, n4, n6, n8 }, + codeBlockGroupFlushIndicator BOOLEAN, + ... +} + +``` + +``` + +PDSCH-CodeBlockGroupTransmissionList-r16 ::= SEQUENCE (SIZE (1..2)) OF PDSCH-CodeBlockGroupTransmission + +DownlinkHARQ-FeedbackDisabled-r17 ::= BIT STRING (SIZE (32)) + +-- TAG-PDSCH-SERVINGCELLCONFIG-STOP +-- ASN1STOP + +``` + +#### ***PDSCH-CodeBlockGroupTransmission* field descriptions** + +| | | +|---------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------| +| codeBlockGroupFlushIndicator | Indicates whether CBGFI for CBG based (re)transmission in DL is enabled (true). (see TS 38.212 [17], clause 7.3.1.2.2). | +| maxCodeBlockGroupsPerTransportBlock | Maximum number of code-block-groups (CBGs) per TB. In case of multiple CW, the maximum CBG is 4 (see TS 38.213 [13], clause 9.1.1). | + +#### ***PDSCH-ServingCellConfig* field descriptions** + +| | | +|----------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| codeBlockGroupTransmission |

Enables and configures code-block-group (CBG) based transmission (see TS 38.213 [13], clause 9.1.1). Network does not configure for a UE both spatial bundling of HARQ ACKs and codeBlockGroupTransmission within the same cell group.

The network does not configure this field if

  • - the SCS of at least one DL BWP configured in the cell is 480 or 960 kHz
  • - Type-1 HARQ-ACK codebook is configured and pdsch-TimeDomainAllocationListForMultiPDSCH-r17 for this serving cell contains pdsch-AllocationList with multiple entries (multiple PDSCH)
  • - Type-2 HARQ-ACK codebook is configured and pdsch-TimeDomainAllocationListForMultiPDSCH-r17 for any cell in the same PUCCH cell group associated with this serving cell contains pdsch-AllocationList with multiple entries (multiple PDSCH)
| +| downlinkHARQ-FeedbackDisabled | Used to disable the DL HARQ feedback, sent in the uplink, per HARQ process ID. The first/leftmost bit corresponds to HARQ process ID 0, the next bit to HARQ process ID 1 and so on. Bits corresponding to HARQ process IDs that are not configured shall be ignored. The bit(s) set to one identify HARQ processes with disabled DL HARQ feedback and the bit(s) set to zero identify HARQ processes with enabled DL HARQ feedback. | +| maxMIMO-Layers | Indicates the maximum number of MIMO layers to be used for PDSCH in all BWPs of this serving cell. (see TS 38.212 [17], clause 5.4.2.1). | +| nrofHARQ-ProcessesForPDSCH | The number of HARQ processes to be used on the PDSCH of a serving cell. Value n2 corresponds to 2 HARQ processes, value n4 to 4 HARQ processes, and so on. If both nrofHARQ-ProcessesForPDSCH and nrofHARQ-ProcessesForPDSCH-v1700 are absent, the UE uses 8 HARQ processes (see TS 38.214 [19], clause 5.1). | +| pdsch-CodeBlockGroupTransmissionList | A list of configurations for up to two simultaneously constructed HARQ-ACK codebooks (see TS 38.213 [13], clause 9.3). | +| processingType2Enabled | Enables configuration of advanced processing time capability 2 for PDSCH (see 38.214 [19], clause 5.3). | +| pucch-Cell | The ID of the serving cell (of the same cell group) to use for PUCCH. If the field is absent, the UE sends the HARQ feedback on the PUCCH of the SpCell of this cell group, or on this serving cell if it is a PUCCH SCell. | +| xOverhead | Accounts for overhead from CSI-RS, CORESET, etc. If the field is absent, the UE applies value xOh0 (see TS 38.214 [19], clause 5.1.3.2). | + +| Conditional Presence | Explanation | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SCellAddOnly | It is optionally present, Need S, for (non-PUCCH) SCells when adding a new SCell. The field is absent, Need M, when reconfiguring SCells. The field is also absent for the SpCells as well as for a PUCCH SCell. | + +#### – *PDSCH-TimeDomainResourceAllocationList* + +The IE *PDSCH-TimeDomainResourceAllocation* is used to configure a time domain relation between PDCCH and PDSCH. The *PDSCH-TimeDomainResourceAllocationList* contains one or more of such *PDSCH-TimeDomainResourceAllocations*. The network indicates in the DL assignment which of the configured time domain allocations the UE shall apply for that DL assignment. The UE determines the bit width of the DCI field based on the number of entries in the *PDSCH-TimeDomainResourceAllocationList*. Value 0 in the DCI field refers to the first element in this list, value 1 in the DCI field refers to the second element in this list, and so on. + +#### *PDSCH-TimeDomainResourceAllocationList* information element + +``` +-- ASN1START +-- TAG-PDSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-START + +PDSCH-TimeDomainResourceAllocationList ::= SEQUENCE (SIZE(1..maxNrofDL-Allocations)) OF PDSCH-TimeDomainResourceAllocation + +PDSCH-TimeDomainResourceAllocation ::= SEQUENCE { + k0 INTEGER(0..32) OPTIONAL, -- Need S + mappingType ENUMERATED {typeA, typeB}, + startSymbolAndLength INTEGER (0..127) +} + +PDSCH-TimeDomainResourceAllocationList-r16 ::= SEQUENCE (SIZE(1..maxNrofDL-Allocations)) OF PDSCH-TimeDomainResourceAllocation-r16 + +PDSCH-TimeDomainResourceAllocation-r16 ::= SEQUENCE { + k0-r16 INTEGER(0..32) OPTIONAL, -- Need S + mappingType-r16 ENUMERATED {typeA, typeB}, + startSymbolAndLength-r16 INTEGER (0..127), + repetitionNumber-r16 ENUMERATED {n2, n3, n4, n5, n6, n7, n8, n16} OPTIONAL, -- Cond Formats1-0_1-1_4-0_4-1_4-2 + ..., + [[ + k0-v1710 INTEGER(33..128) OPTIONAL -- Need S + ]], + [[ + repetitionNumber-v1730 ENUMERATED {n2, n3, n4, n5, n6, n7, n8, n16} OPTIONAL -- Cond Format1-2 + ]] +} + +Dummy-TDRA-List ::= SEQUENCE (SIZE(1.. maxNrofDL-Allocations)) OF MultiPDSCH-TDRA-r17 + +MultiPDSCH-TDRA-List-r17 ::= SEQUENCE (SIZE(1.. maxNrofDL-AllocationsExt-r17)) OF MultiPDSCH-TDRA-r17 + +MultiPDSCH-TDRA-r17 ::= SEQUENCE { + pdsch-TDRA-List-r17 SEQUENCE (SIZE(1..maxNrofMultiplePDSCHs-r17)) OF PDSCH-TimeDomainResourceAllocation-r16, +} +``` + +``` + + ... +} + +-- TAG-PDSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STOP +-- ASN1STOP + +``` + +#### PDSCH-TimeDomainResourceAllocation field descriptions + +| | | +|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| k0 | Slot offset between DCI and its scheduled PDSCH (see TS 38.214 [19], clause 5.1.2.1). k0-v1710 is only applicable for PDSCH SCS of 480 kHz and 960 kHz. If multiple PDSCHs are configured per PDCCH, the network always configures this field. Otherwise, when the field is absent and only one PDSCH is configured per PDCCH, the UE applies the value 0. | +| mappingType | PDSCH mapping type (see TS 38.214 [19], clause 5.3). | +| repetitionNumber | Indicates the number of PDSCH transmission occasions for slot-based repetition scheme in IE RepetitionSchemeConfig . The parameter is used as specified in 38.214 [19]. | +| startSymbolAndLength | An index giving valid combinations of start symbol and length (jointly encoded) as start and length indicator (SLIV). The network configures the field so that the allocation does not cross the slot boundary (see TS 38.214 [19], clause 5.1.2.1). | + +#### MultiPDSCH-TimeDomainResourceAllocation field descriptions + +| | | +|------------------------|-------------------------------------------------------------------------------------------------------------------| +| pdsch-TDRA-List | One or multiple PDSCHs which can be in consecutive or non-consecutive slots (see TS 38.214 [19], clause 5.1.2.1). | +|------------------------|-------------------------------------------------------------------------------------------------------------------| + +| Conditional Presence | Explanation | +|-----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Format1-2 | In pdsch-TimeDomainAllocationListDCI-1-2 , this field is optionally present, Need R. It is absent, Need R, otherwise. | +| Formats1-0_1-1_4-0_4-1_4-2 | In pdsch-TimeDomainAllocationListDCI-1-2 , pdsch-TimeDomainAllocationListForMultiPDSCH , and SIB20 , this field is absent.
Otherwise, in pdsch-TimeDomainResourceAllocationList-r16 , this field is optionally present, Need R. | + +#### — PDU-SessionID + +The IE *PDU-SessionID* identifies the PDU Session. + +#### PDU-SessionID information element + +``` + +-- ASN1START +-- TAG-PDU-SESSIONID-START + +PDU-SessionID ::= INTEGER (0..255) + +-- TAG-PDU-SESSIONID-STOP + +``` + +``` +-- ASN1STOP +``` + +## PHR-Config + +The IE *PHR-Config* is used to configure parameters for power headroom reporting. + +#### PHR-Config information element + +``` +-- ASN1START +-- TAG-PHR-CONFIG-START + +PHR-Config ::= + SEQUENCE { + phr-PeriodicTimer ENUMERATED {sf10, sf20, sf50, sf100, sf200, sf500, sf1000, infinity}, + phr-ProhibitTimer ENUMERATED {sf0, sf10, sf20, sf50, sf100, sf200, sf500, sf1000}, + phr-Tx-PowerFactorChange ENUMERATED {dB1, dB3, dB6, infinity}, + multiplePHR BOOLEAN, + dummy BOOLEAN, + phr-Type2OtherCell BOOLEAN, + phr-ModeOtherCG ENUMERATED {real, virtual}, + ... + [[ + mpe-Reporting-FR2-r16 SetupRelease { MPE-Config-FR2-r16 } OPTIONAL -- Need M + ]], + [[ + mpe-Reporting-FR2-r17 SetupRelease { MPE-Config-FR2-r17 } OPTIONAL, -- Need M + twoPHRMode-r17 ENUMERATED {enabled} OPTIONAL -- Need R + ]], + [[ + phr-AssumedPUSCH-Reporting-r18 ENUMERATED {enabled} OPTIONAL, -- Need R + dpc-Reporting-FR1-r18 ENUMERATED {enabled} OPTIONAL -- Need R + ]] + } + +MPE-Config-FR2-r16 ::= + SEQUENCE { + mpe-ProhibitTimer-r16 ENUMERATED {sf0, sf10, sf20, sf50, sf100, sf200, sf500, sf1000}, + mpe-Threshold-r16 ENUMERATED {dB3, dB6, dB9, dB12} + } + +MPE-Config-FR2-r17 ::= + SEQUENCE { + mpe-ProhibitTimer-r17 ENUMERATED {sf0, sf10, sf20, sf50, sf100, sf200, sf500, sf1000}, + mpe-Threshold-r17 ENUMERATED {dB3, dB6, dB9, dB12}, + numberOfN-r17 INTEGER(1..4), + ... + } + +-- TAG-PHR-CONFIG-STOP +-- ASN1STOP +``` + +| PHR-Config field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| dpc-Reporting-FR1
Indicates if the delta power class (DPC) is reported, as specified in TS 38.321 [3]. | +| dummy
This field is not used in this version of the specification and the UE ignores the received value. | +| mpe-ProhibitTimer
Value in number of subframes for MPE reporting, as specified in TS 38.321 [3]. Value sf10 corresponds to 10 subframes, and so on. | +| mpe-Reporting-FR2
Indicates whether the UE shall report MPE P-MPR in the PHR MAC control element, as specified in TS 38.321 [3]. | +| mpe-Threshold
Value of the P-MPR threshold in dB for reporting MPE P-MPR when FR2 is configured, as specified in TS 38.321 [3]. The same value applies for each serving cell (although the associated functionality is performed independently for each cell). | +| multiplePHR
Indicates if power headroom shall be reported using the Single Entry PHR MAC control element or Multiple Entry PHR MAC control element defined in TS 38.321 [3]. True means to use Multiple Entry PHR MAC control element and False means to use the Single Entry PHR MAC control element defined in TS 38.321 [3]. The network configures this field to true for MR-DC and UL CA for NR, and to false in all other cases. | +| numberOfN
Number of reported P-MPR values in a PHR MAC CE. | +| phr-AssumedPUSCH-Reporting
Indicates if the PHR with an assumed PUSCH is reported, as specified in TS 38.321 [3]. | +| phr-ModeOtherCG
Indicates the mode (i.e. real or virtual) used for the PHR of the activated cells that are part of the other Cell Group (i.e. MCG or SCG), when DC is configured. If the UE is configured with only one cell group (no DC), it ignores the field. | +| phr-PeriodicTimer
Value in number of subframes for PHR reporting as specified in TS 38.321 [3]. Value sf10 corresponds to 10 subframes, value sf20 corresponds to 20 subframes, and so on. | +| phr-ProhibitTimer
Value in number of subframes for PHR reporting as specified in TS 38.321 [3]. Value sf0 corresponds to 0 subframe, value sf10 corresponds to 10 subframes, value sf20 corresponds to 20 subframes, and so on. | +| phr-Tx-PowerFactorChange
Value in dB for PHR reporting as specified in TS 38.321 [3]. Value dB1 corresponds to 1 dB, dB3 corresponds to 3 dB and so on. The same value applies for each serving cell (although the associated functionality is performed independently for each cell). | +| phr-Type2OtherCell
If set to true, the UE shall report a PHR type 2 for the SpCell of the other MAC entity. See TS 38.321 [3], clause 5.4.6. Network sets this field to false if the UE is not configured with an E-UTRA MAC entity. | +| twoPHRMode
Indicates if the power headroom shall be reported as two PHRs (each PHR associated with a SRS resource set) is enabled or not. | + +#### — *PhysCellId* + +The *PhysCellId* identifies the physical cell identity (PCI). + +#### **PhysCellId information element** + +``` + +-- ASN1START +-- TAG-PHYCELLID-START + +PhysCellId ::= INTEGER (0..1007) + +-- TAG-PHYCELLID-STOP +-- ASN1STOP + +``` + +#### **PhysicalCellGroupConfig** + +The IE *PhysicalCellGroupConfig* is used to configure cell-group specific L1 parameters. + +#### **PhysicalCellGroupConfig information element** + +``` + +-- ASN1START +-- TAG-PHYSICALCELLGROUPCONFIG-START + +PhysicalCellGroupConfig ::= SEQUENCE { + harq-ACK-SpatialBundlingPUCCH ENUMERATED {true} OPTIONAL, -- Need S + harq-ACK-SpatialBundlingPUSCH ENUMERATED {true} OPTIONAL, -- Need S + p-NR-FR1 P-Max OPTIONAL, -- Need R + pdsch-HARQ-ACK-Codebook ENUMERATED {semiStatic, dynamic}, + tpc-SRS-RNTI RNTI-Value OPTIONAL, -- Need R + tpc-PUCCH-RNTI RNTI-Value OPTIONAL, -- Need R + tpc-PUSCH-RNTI RNTI-Value OPTIONAL, -- Need R + sp-CSI-RNTI RNTI-Value OPTIONAL, -- Need R + cs-RNTI SetupRelease { RNTI-Value } OPTIONAL, -- Need M + ..., + [[ + mcs-C-RNTI RNTI-Value OPTIONAL, -- Need R + p-UE-FR1 P-Max OPTIONAL -- Cond MCG-Only + ]], + [[ + xScale ENUMERATED {dB0, dB6, spare2, spare1} OPTIONAL -- Cond SCG-Only + ]], + [[ + pdcch-BlindDetection SetupRelease { PDCCH-BlindDetection } OPTIONAL -- Need M + ]], + [[ + dcp-Config-r16 SetupRelease { DCP-Config-r16 } OPTIONAL, -- Need M + harq-ACK-SpatialBundlingPUCCH-secondaryPUCCHgroup-r16 ENUMERATED {enabled, disabled} OPTIONAL, -- Cond twoPUCCHgroup + harq-ACK-SpatialBundlingPUSCH-secondaryPUCCHgroup-r16 ENUMERATED {enabled, disabled} OPTIONAL, -- Cond twoPUCCHgroup + pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup-r16 ENUMERATED {semiStatic, dynamic} OPTIONAL, -- Cond twoPUCCHgroup + p-NR-FR2-r16 P-Max OPTIONAL, -- Need R + p-UE-FR2-r16 P-Max OPTIONAL, -- Cond MCG-Only + nrdc-PCmode-FR1-r16 ENUMERATED {semi-static-model, semi-static-mode2, dynamic} OPTIONAL, -- Cond MCG-Only + +``` + +``` + +nrdc-PCmode-FR2-r16 ENUMERATED {semi-static-model, semi-static-mode2, dynamic} OPTIONAL, -- Cond MCG-Only +pdsch-HARQ-ACK-Codebook-r16 ENUMERATED {enhancedDynamic} OPTIONAL, -- Need R +nfi-TotalDAI-Included-r16 ENUMERATED {true} OPTIONAL, -- Need R +ul-TotalDAI-Included-r16 ENUMERATED {true} OPTIONAL, -- Need R +pdsch-HARQ-ACK-OneShotFeedback-r16 ENUMERATED {true} OPTIONAL, -- Need R +pdsch-HARQ-ACK-OneShotFeedbackNDI-r16 ENUMERATED {true} OPTIONAL, -- Need R +pdsch-HARQ-ACK-OneShotFeedbackCBG-r16 ENUMERATED {true} OPTIONAL, -- Need R +downlinkAssignmentIndexDCI-0-2-r16 ENUMERATED { enabled } OPTIONAL, -- Need S +downlinkAssignmentIndexDCI-1-2-r16 ENUMERATED {n1, n2, n4} OPTIONAL, -- Need S +pdsch-HARQ-ACK-CodebookList-r16 SetupRelease { PDSCH-HARQ-ACK-CodebookList-r16 } OPTIONAL, -- Need M +ackNackFeedbackMode-r16 ENUMERATED {joint, separate} OPTIONAL, -- Need R +pdcch-BlindDetectionCA-CombIndicator-r16 SetupRelease { PDCCH-BlindDetectionCA-CombIndicator-r16 } OPTIONAL, -- Need M +pdcch-BlindDetection2-r16 SetupRelease { PDCCH-BlindDetection2-r16 } OPTIONAL, -- Need M +pdcch-BlindDetection3-r16 SetupRelease { PDCCH-BlindDetection3-r16 } OPTIONAL, -- Need M +bdFactorR-r16 ENUMERATED {n1} OPTIONAL, -- Need R +]], +[[ +-- start of enhanced Type3 feedback +pdsch-HARQ-ACK-EnhType3ToAddModList-r17 SEQUENCE (SIZE(1..maxNrofEnhType3HARQ-ACK-r17)) OF PDSCH-HARQ-ACK-EnhType3-r17 OPTIONAL, -- Need N +pdsch-HARQ-ACK-EnhType3ToReleaseList-r17 SEQUENCE (SIZE(1..maxNrofEnhType3HARQ-ACK-r17)) OF PDSCH-HARQ-ACK-EnhType3Index-r17 OPTIONAL, -- Need N +pdsch-HARQ-ACK-EnhType3SecondaryToAddModList-r17 SEQUENCE (SIZE(1..maxNrofEnhType3HARQ-ACK-r17)) OF PDSCH-HARQ-ACK-EnhType3-r17 OPTIONAL, -- Need N +pdsch-HARQ-ACK-EnhType3SecondaryToReleaseList-r17 SEQUENCE (SIZE(1..maxNrofEnhType3HARQ-ACK-r17)) OF PDSCH-HARQ-ACK-EnhType3Index-r17 OPTIONAL, -- Need N +pdsch-HARQ-ACK-EnhType3DCI-FieldSecondaryPUCCHgroup-r17 ENUMERATED {enabled} OPTIONAL, -- Cond twoPUCCHgroup +pdsch-HARQ-ACK-EnhType3DCI-Field-r17 ENUMERATED {enabled} OPTIONAL, -- Need R +-- end of enhanced Type3 feedback + +-- start of triggering of HARQ-ACK re-transmission on a PUCCH resource +pdsch-HARQ-ACK-Retx-r17 ENUMERATED {enabled} OPTIONAL, -- Need R +pdsch-HARQ-ACK-RetxSecondaryPUCCHgroup-r17 ENUMERATED {enabled} OPTIONAL, -- Cond twoPUCCHgroup +-- end of triggering of HARQ-ACK re-transmission on a PUCCH resource + +-- start of PUCCH Cell switching +pucch-sSCell-r17 SCellIndex OPTIONAL, -- Need R +pucch-sSCellSecondaryPUCCHgroup-r17 SCellIndex OPTIONAL, -- Cond twoPUCCHgroup +pucch-sSCellDyn-r17 ENUMERATED {enabled} OPTIONAL, -- Need R +pucch-sSCellDynSecondaryPUCCHgroup-r17 ENUMERATED {enabled} OPTIONAL, -- Cond twoPUCCHgroup +pucch-sSCellPattern-r17 SEQUENCE (SIZE(1..maxNrofSlots)) OF INTEGER (0..1) OPTIONAL, -- Need R +pucch-sSCellPatternSecondaryPUCCHgroup-r17 SEQUENCE (SIZE(1..maxNrofSlots)) OF INTEGER (0..1) OPTIONAL, -- Cond twoPUCCHgroup +-- end of PUCCH Cell switching + +uci-MuxWithDiffPrio-r17 ENUMERATED {enabled} OPTIONAL, -- Need R +uci-MuxWithDiffPrioSecondaryPUCCHgroup-r17 ENUMERATED {enabled} OPTIONAL, -- Cond twoPUCCHgroup +simultaneousPUCCH-PUSCH-r17 ENUMERATED {enabled} OPTIONAL, -- Need R +simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup-r17 ENUMERATED {enabled} OPTIONAL, -- Cond twoPUCCHgroup + +prioLowDG-HighCG-r17 ENUMERATED {enabled} OPTIONAL, -- Need R +prioHighDG-LowCG-r17 ENUMERATED {enabled} OPTIONAL, -- Need R + +``` + +``` + +twoQCLTypeDforPDCCHRepetition-r17 ENUMERATED {enabled} OPTIONAL, -- Need R +multicastConfig-r17 SetupRelease { MulticastConfig-r17 } OPTIONAL, -- Need M +pdcch-BlindDetectionCA-CombIndicator-r17 SetupRelease { PDCCH-BlindDetectionCA-CombIndicator-r17 } OPTIONAL -- Need M +]], +[[ +simultaneousSR-PUSCH-diffPUCCH-Groups-r17 ENUMERATED {enabled} OPTIONAL -- Cond twoPUCCHgroup +]], +[[ +intraBandNC-PRACH-simulTx-r17 ENUMERATED {enabled} OPTIONAL -- Need R +]], +[[ +pdcch-BlindDetection4-r17 SetupRelease { PDCCH-BlindDetection4-r17 } OPTIONAL -- Need M +]], +[[ +simultaneousPUCCH-PUSCH-SamePriority-r17 ENUMERATED {enabled} OPTIONAL, -- Need R +simultaneousPUCCH-PUSCH-SamePriority-SecondaryPUCCHgroup-r17 ENUMERATED {enabled} OPTIONAL -- Cond twoPUCCHgroup +]], +[[ +ncr-RNTI-r18 RNTI-Value OPTIONAL, -- Cond NCR +cellDTRX-DCI-config-r18 SetupRelease { CellDTRX-DCI-config-r18 } OPTIONAL -- Need M +]] +} + +PDSCH-HARQ-ACK-EnhType3-r17 ::= SEQUENCE { + pdsch-HARQ-ACK-EnhType3Index-r17 PDSCH-HARQ-ACK-EnhType3Index-r17, + applicable-r17 CHOICE { + perCC SEQUENCE (SIZE (1..maxNrofServingCells)) OF INTEGER (0..1), + perHARQ SEQUENCE (SIZE (1..maxNrofServingCells)) OF BIT STRING (SIZE (16)) + }, + pdsch-HARQ-ACK-EnhType3NDI-r17 ENUMERATED {true} OPTIONAL, -- Need R + pdsch-HARQ-ACK-EnhType3CBG-r17 ENUMERATED {true} OPTIONAL, -- Need S + ... + [[ + perHARQ-Ext-r17 SEQUENCE (SIZE (1..maxNrofServingCells)) OF BIT STRING (SIZE (32)) OPTIONAL -- Need R + ]] +} + +PDSCH-HARQ-ACK-EnhType3Index-r17 ::= INTEGER (0..maxNrofEnhType3HARQ-ACK-1-r17) + +PDCCH-BlindDetection ::= INTEGER (1..15) + +DCP-Config-r16 ::= SEQUENCE { + ps-RNTI-r16 RNTI-Value, + ps-Offset-r16 INTEGER (1..120), + sizeDCI-2-6-r16 INTEGER (1..maxDCI-2-6-Size-r16), + ps-PositionDCI-2-6-r16 INTEGER (0..maxDCI-2-6-Size-1-r16), + ps-WakeUp-r16 ENUMERATED {true} OPTIONAL, -- Need S + ps-TransmitPeriodicL1-RSRP-r16 ENUMERATED {true} OPTIONAL, -- Need S + ps-TransmitOtherPeriodicCSI-r16 ENUMERATED {true} OPTIONAL -- Need S +} + +``` + +``` + +PDSCH-HARQ-ACK-CodebookList-r16 ::= SEQUENCE (SIZE (1..2)) OF ENUMERATED {semiStatic, dynamic} + +PDCCH-BlindDetectionCA-CombIndicator-r16 ::= SEQUENCE { + pdcch-BlindDetectionCA1-r16 INTEGER (1..15), + pdcch-BlindDetectionCA2-r16 INTEGER (1..15) +} + +PDCCH-BlindDetection2-r16 ::= INTEGER (1..15) +PDCCH-BlindDetection3-r16 ::= INTEGER (1..15) +PDCCH-BlindDetection4-r17 ::= INTEGER (1..15) + +MulticastConfig-r17 ::= SEQUENCE { + pdsch-HARQ-ACK-CodebookListMulticast-r17 SetupRelease { PDSCH-HARQ-ACK-CodebookList-r16} OPTIONAL, -- Need M + type1CodebookGenerationMode-r17 ENUMERATED { mode1, mode2} OPTIONAL, -- Need M +} + +PDCCH-BlindDetectionCA-CombIndicator-r17 ::= SEQUENCE { + pdcch-BlindDetectionCA1-r17 INTEGER (1..15) OPTIONAL, -- Need R + pdcch-BlindDetectionCA2-r17 INTEGER (1..15) OPTIONAL, -- Need R + pdcch-BlindDetectionCA3-r17 INTEGER (1..15) +} + +CellDTRX-DCI-config-r18 ::= SEQUENCE { + cellDTRX-RNTI-r18 RNTI-Value, + sizeDCI-2-9-r18 INTEGER (1..140) +} + +-- TAG-PHYSICALCELLGROUPCONFIG-STOP +-- ASN1STOP + +``` + +| PhysicalCellGroupConfig field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ackNackFeedbackMode
Indicates which among the joint and separate ACK/NACK feedback modes to use within a slot as specified in TS 38.213 [13] (clause 9). | +| bdFactorR
Parameter for determining and distributing the maximum numbers of BD/CCE for mPDCCH based mPD SCH transmission as specified in TS 38.213 [13] Clause 10.1. | +| cs-RNTI
RNTI value for downlink SPS (see SPS-Config ) and uplink configured grant (see ConfiguredGrantConfig ). | +| downlinkAssignmentIndexDCI-0-2
Indicates if "Downlink assignment index" is present or absent in DCI format 0_2. If the field "downlinkAssignmentIndexDCI-0-2" is absent, then 0 bit for "Downlink assignment index" in DCI format 0_2. If the field "downlinkAssignmentIndexDCI-0-2" is present, then the bitwidth of "Downlink assignment index" in DCI format 0_2 is defined in the same was as that in DCI format 0_1 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 9.1). | +| downlinkAssignmentIndexDCI-1-2
Configures the number of bits for "Downlink assignment index" in DCI format 1_2. If the field is absent, then 0 bit is applied for "Downlink assignment index" in DCI format 1_2. Note that 1 bit and 2 bits are applied if only one serving cell is configured in the DL and pdsch-HARQ-ACK-Codebook is set to dynamic . 4 bits is applied if more than one serving cell are configured in the DL and pdsch-HARQ-ACK-Codebook is set to dynamic (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 9.1). | +| harq-ACK-SpatialBundlingPUCCH
Enables spatial bundling of HARQ ACKs. It is configured per cell group (i.e. for all the cells within the cell group) for PUCCH reporting of HARQ-ACK. It is only applicable when more than 4 layers are possible to schedule. When the field is absent, the spatial bundling of PUCCH HARQ ACKs for the primary PUCCH group is disabled (see TS 38.213 [13], clause 9.1.2.1). If the field harq-ACK-SpatialBundlingPUCCH-secondaryPUCCHgroup is present, harq-ACK-SpatialBundlingPUCCH is only applied to primary PUCCH group. Network does not configure for a UE both spatial bundling of HARQ ACKs and codeBlockGroupTransmission within the same cell group. | +| harq-ACK-SpatialBundlingPUCCH-secondaryPUCCHgroup
Indicates whether spatial bundling of PUCCH HARQ ACKs for the secondary PUCCH group is enabled or disabled. The field is only applicable when more than 4 layers are possible to schedule (see TS 38.213 [13], clause 9.1.2.1). When the field is absent, the use of spatial bundling of PUCCH HARQ ACKs for the secondary PUCCH group is indicated by harq-ACK-SpatialBundlingPUCCH . See TS 38.213 [13], clause 9.1.2.1. Network does not configure for a UE both spatial bundling of HARQ ACKs and codeBlockGroupTransmission within the same cell group. | +| harq-ACK-SpatialBundlingPUSCH
Enables spatial bundling of HARQ ACKs. It is configured per cell group (i.e. for all the cells within the cell group) for PUSCH reporting of HARQ-ACK. It is only applicable when more than 4 layers are possible to schedule. When the field is absent, the spatial bundling of PUSCH HARQ ACKs for the primary PUCCH group is disabled (see TS 38.213 [13], clauses 9.1.2.2 and 9.1.3.2). If the field harq-ACK-SpatialBundlingPUSCH-secondaryPUCCHgroup is present, harq-ACK-SpatialBundlingPUSCH is only applied to primary PUCCH group. Network does not configure for a UE both spatial bundling of HARQ ACKs and codeBlockGroupTransmission within the same cell group. | +| harq-ACK-SpatialBundlingPUSCH-secondaryPUCCHgroup
Indicates whether spatial bundling of PUSCH HARQ ACKs for the secondary PUCCH group is enabled or disabled. The field is only applicable when more than 4 layers are possible to schedule (see TS 38.213 [13], clauses 9.1.2.2 and 9.1.3.2). When the field is absent, the use of spatial bundling of PUSCH HARQ ACKs for the secondary PUCCH group is indicated by harq-ACK-SpatialBundlingPUSCH . See TS 38.213 [13], clauses 9.1.2.2 and 9.1.3.2. Network does not configure for a UE both spatial bundling of HARQ ACKs and codeBlockGroupTransmission within the same cell group. | +| intraBandNC-PRACH-simulTx
Enables parallel PRACH and SRS/PUCCH/PUSCH transmissions across CCs in intra-band non-contiguous CA (see TS 38.213 [13], clause 8.1 and TS 38.214 [19], clause 6.2.1). This field is absent in the IE CellGroupConfig when provided as part of RRCSetup message. | +| mcs-C-RNTI
RNTI to indicate use of qam64LowSE for grant-based transmissions. When the mcs-C-RNTI is configured, RNTI scrambling of DCI CRC is used to choose the corresponding MCS table. | +| ncr-RNTI
RNTI value for NCR-MT, used to scramble the PDCCHs carrying side control information (see TS 38.213 [13], clause 10.1). | + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| nfi-TotalDAI-Included
Indicates whether the NFI and total DAI fields of the non-scheduled PDSCH group is included in the non-fallback DL grant DCI (see TS 38.212 [17], clause 7.3.1). The network configures this only when enhanced dynamic codebook is configured ( pdsch-HARQ-ACK-Codebook is set to enhancedDynamic ). | +| nrdc-PCmode-FR1
Indicates the uplink power sharing mode that the UE uses in NR-DC in frequency range 1 (FR1) (see TS 38.213 [13], clause 7.6). | +| nrdc-PCmode-FR2
Indicates the uplink power sharing mode that the UE uses in NR-DC in frequency range 2 (FR2) (see TS 38.213 [13], clause 7.6). | +| pdcch-BlindDetection, pdcch-BlindDetection2, pdcch-BlindDetection3, pdcch-BlindDetection4
Indicates the reference number of cells for PDCCH blind detection for the CG. Network configures the field for each CG when the UE is in NR DC and sets the value in accordance with the constraints specified in TS 38.213 [13]. The network configures pdcch-BlindDetection only if the UE is in NR-DC. The network configures pdcch-BlindDetection2 only if the UE is in NR-DC with at least one downlink cell using Rel-16 PDCCH monitoring capability. The network configures pdcch-BlindDetection3 only if the UE is in NR-DC with at least one downlink cell using Rel-15 PDCCH monitoring capability. The network configures pdcch-BlindDetection4 only if the UE is in NR-DC with at least one downlink cell using Rel-17 PDCCH monitoring capability. | +| pdcch-BlindDetectionCA-CombIndicator
Configure one combination of pdcch-BlindDetectionCA1 (for R15) and pdcch-BlindDetectionCA2 (for R16) for UE to use for scaling PDCCH monitoring capability if the number of serving cells configured to a UE is larger than the reported capability, and if UE reports more than one combination of pdcch-BlindDetectionCA1 and pdcch-BlindDetectionCA2 as UE capability. The combination of pdcch-BlindDetectionCA1 and pdcch-BlindDetectionCA2 configured by pdcch-BlindDetectionCA-CombIndicator is from the more than one combination of pdcch-BlindDetectionCA1 and pdcch-BlindDetectionCA2 reported by UE (see TS 38.213 [13], clause 10). pdcch-BlindDetectionCA-CombIndicator-r17 is used to configure one combination of pdcch-BlindDetectionCA1 (for R15), pdcch-BlindDetectionCA2 (for R16) and pdcch-BlindDetectionCA3 (for R17) for UE to use for scaling PDCCH monitoring capability if the number of serving cells configured to a UE is larger than the reported capability, and if UE reports more than one combination of pdcch-BlindDetectionCA1 , pdcch-BlindDetectionCA2 and pdcch-BlindDetectionCA3 as UE capability. The combination of pdcch-BlindDetectionCA1 , pdcch-BlindDetectionCA2 and pdcch-BlindDetectionCA3 configured by pdcch-BlindDetectionCA-CombIndicator-r17 is from the more than one combination of pdcch-BlindDetectionCA1 , pdcch-BlindDetectionCA2 and pdcch-BlindDetectionCA3 reported by UE (see TS 38.213 [13], clause 10). pdcch-BlindDetectionCA-CombIndicator-r16 and pdcch-BlindDetectionCA-CombIndicator-r17 are not configured simultaneously. | +| p-NR-FR1
The maximum total transmit power to be used by the UE in this NR cell group across all serving cells in frequency range 1 (FR1). The maximum transmit power that the UE may use may be additionally limited by p-Max (configured in FrequencyInfoUL ) and by p-UE-FR1 (configured total for all serving cells operating on FR1). | +| p-NR-FR2
The maximum total transmit power to be used by the UE in this NR cell group across all serving cells in frequency range 2 (FR2). The maximum transmit power that the UE may use may be additionally limited by p-Max (configured in FrequencyInfoUL ) and by p-UE-FR2 (configured total for all serving cells operating on FR2). This field is only used in NR-DC. A UE does not expect to be configured with this parameter in this release of the specification. | +| prioLowDG-HighCG
Enable PHY prioritization for the case where low-priority dynamic grant-PUSCH collides with high-priority configured grant-PUSCH on a BWP of a serving cell (see TS 38.213 [13], clause 9), when the UE has generated transport blocks for both DG-PUSCH and CG-PUSCH as described in TS 38.321 [3]. | +| prioHighDG-LowCG
Enable PHY prioritization for the case where high-priority dynamic grant PUSCH collides with low-priority configured grant PUSCH on a BWP of a serving cell (see TS 38.213 [13], clause 9), when the UE has generated transport blocks for both DG-PUSCH and CG-PUSCH as described in TS 38.321 [3]. | +| ps-RNTI
RNTI value for scrambling CRC of DCI format 2-6 used for power saving (see TS 38.213 [13], clause 10.1). | +| ps-Offset
The start of the search-time of DCI format 2-6 with CRC scrambled by PS-RNTI relative to the start of the drx-onDurationTimer of Long DRX (see TS 38.213 [13], clause 10.3). Value in multiples of 0.125ms (milliseconds). 1 corresponds to 0.125 ms, 2 corresponds to 0.25 ms, 3 corresponds to 0.375 ms and so on. | +| ps-WakeUp | + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Indicates the UE to wake-up if DCI format 2-6 is not detected outside active time (see TS 38.321 [3], clause 5.7). If the field is absent, the UE does not wake-up if DCI format 2-6 is not detected outside active time. | +| ps-PositionDCI-2-6
Starting position of UE wakeup and SCell dormancy indication in DCI format 2-6 (see TS 38.213 [13], clause 10.3). | +| ps-TransmitPeriodicL1-RSRP
Indicates the UE to transmit periodic L1-RSRP report(s) when the drx-onDurationTimer does not start (see TS 38.321 [3], clause 5.7). If the field is absent, the UE does not transmit periodic L1-RSRP report(s) when the drx-onDurationTimer does not start. | +| ps-TransmitOtherPeriodicCSI
Indicates the UE to transmit periodic CSI report(s) other than L1-RSRP reports when the drx-onDurationTimer does not start (see TS 38.321 [3], clause 5.7). If the field is absent, the UE does not transmit periodic CSI report(s) other than L1-RSRP reports when the drx-onDurationTimer does not start. | +| p-UE-FR1
The maximum total transmit power to be used by the UE across all serving cells in frequency range 1 (FR1) across all cell groups. The maximum transmit power that the UE may use may be additionally limited by p-Max (configured in FrequencyInfoUL ) and by p-NR-FR1 (configured for the cell group). | +| p-UE-FR2
The maximum total transmit power to be used by the UE across all serving cells in frequency range 2 (FR2) across all cell groups. The maximum transmit power that the UE may use may be additionally limited by p-Max (configured in FrequencyInfoUL ) and by p-NR-FR2 (configured for the cell group). A UE does not expect to be configured with this parameter in this release of the specification. | +| pdsch-HARQ-ACK-Codebook
The PDSCH HARQ-ACK codebook is either semi-static or dynamic. This is applicable to both CA and non-CA operation (see TS 38.213 [13], clauses 9.1.2 and 9.1.3). If pdsch-HARQ-ACK-Codebook-r16 is signalled, UE shall ignore the pdsch-HARQ-ACK-Codebook (without suffix). For the HARQ-ACK for sidelink, if pdsch-HARQ-ACK-Codebook-r16 is signalled, the UE uses pdsch-HARQ-ACK-Codebook (without suffix) and ignores pdsch-HARQ-ACK-Codebook-r16 . If the field pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup is present, pdsch-HARQ-ACK-Codebook is applied to primary PUCCH group. Otherwise, this field is applied to the cell group (i.e. for all the cells within the cell group). For the HARQ-ACK for sidelink, if the field pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup is present, pdsch-HARQ-ACK-Codebook is applied to primary and secondary PUCCH group and the UE ignores pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup . | +| pdsch-HARQ-ACK-CodebookList
A list of configurations for one or two HARQ-ACK codebooks. Each configuration in the list is defined in the same way as pdsch-HARQ-ACK-Codebook (see TS 38.212 [17], clause 7.3.1.2.2 and TS 38.213 [13], clauses 7.2.1, 9.1.2, 9.1.3 and 9.2.1). If this field is present, the field pdsch-HARQ-ACK-Codebook is ignored. If this field is present, the value of this field is applied for primary PUCCH group and for secondary PUCCH group (if configured). For the HARQ-ACK for sidelink, the UE uses pdsch-HARQ-ACK-Codebook and ignores pdsch-HARQ-ACK-CodebookList if this field is present. | +| pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup
The PDSCH HARQ-ACK codebook is either semi-static or dynamic. This is applicable to CA operation (see TS 38.213 [13], clauses 9.1.2 and 9.1.3). It is configured for secondary PUCCH group. | +| pdsch-HARQ-ACK-EnhType3DCI-Field, pdsch-HARQ-ACK-EnhType3DCI-FieldSecondaryPUCCHgroup
Indicates the enhanced Type 3 codebook through a new DCI field to indicate the enhanced Type 3 HARQ-ACK codebook in the primary PUCCH group if the more than one enhanced Type 3 HARQ-ACK codebook is configured for the primary PUCCH group, or in the secondary PUCCH group if the more than one enhanced Type 3 HARQ-ACK code is configured for the secondary PUCCH group, respectively. | +| pdsch-HARQ-ACK-EnhType3ToAddModList, pdsch-HARQ-ACK-EnhType3SecondaryToAddModList
Configure the list of enhanced Type 3 HARQ-ACK codebooks for the primary PUCCH group and the secondary PUCCH group, respectively. When configured, DCI format 1_1 can request the UE to report A/N for one of the configured enhanced Type 3 HARQ-ACK codebooks in the corresponding PUCCH group (see TS 38.213 [13], clause 9.1.4). The network can configure pdsch-HARQ-ACK-EnhType3SecondaryToAddModList only if secondary PUCCH group is configured. | +| pdsch-HARQ-ACK-OneShotFeedback
When configured, the DCI format 1_1 can request the UE to report A/N for all HARQ processes and all CCs configured in the PUCCH group (see TS 38.212 [17], clause 7.3.1). | +| pdsch-HARQ-ACK-OneShotFeedbackCBG | + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| When configured, the DCI format 1_1 can request the UE to include CBG level A/N for each CC with CBG level transmission configured. When not configured, the UE will report TB level A/N even if CBG level transmission is configured for a CC. The network configures this only when pdsch-HARQ-ACK-OneShotFeedback is configured. | +| pdsch-HARQ-ACK-OneShotFeedbackNDI
When configured, the DCI format 1_1 can request the UE to include NDI for each A/N reported. The network configures this only when pdsch-HARQ-ACK-OneShotFeedback is configured. | +| pdsch-HARQ-ACK-Retx, pdsch-HARQ-ACK-RetxSecondaryPUCCHgroup
When configured, the DCI format 1_1 can request the UE to perform a HARQ-ACK re-transmission on a PUCCH resource in the primary PUCCH group and the secondary PUCCH group, respectively (see TS 38.213 [13], clause 9.1.5). | +| pucch-sSCell, pucch-sSCellSecondaryPUCCHgroup
indicates the alternative PUCCH cells for PUCCH cell switching in the primary and the secondary PUCCH group, respectively. For the primary PUCCH group, it is configured for cells on top of SpCell. For the secondary PUCCH group, it is configured for cell on top of the PUCCH SCell. | +| pucch-sSCellDyn, pucch-sSCellDynsecondaryPUCCHgroup
When configured, PUCCH cell switching based on dynamic indication in DCI format 1_1 is enabled (see TS 38.213 [13], clause 9.A, clause 9.1.5), respectively for the primary PUCCH group and the secondary PUCCH group. | +| pucch-sSCellPattern, pucch-sSCellPatternSecondaryPUCCHgroup
When configured, the UE applies the semi-static PUCCH cell switching (see TS 38.213 [13], clause 9.A) using the time domain pattern of applicable PUCCH cells indicated by this field, respectively for the primary PUCCH group and the secondary PUCCH group. | +| simultaneousPUCCH-PUSCH, simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup
Enables simultaneous PUCCH and PUSCH transmissions with different priorities for the primary PUCCH group and the secondary PUCCH group, respectively. | +| simultaneousPUCCH-PUSCH-SamePriority, simultaneousPUCCH-PUSCH-SamePriority-SecondaryPUCCHgroup
Enables simultaneous PUCCH and PUSCH transmissions on different cells in different bands with same priority for the primary PUCCH group and the secondary PUCCH group, respectively, as specified in clause 9 of TS 38.213 [13]. | +| simultaneousSR-PUSCH-diffPUCCH-Groups
Enables simultaneous SR and PUSCH transmissions in different PUCCH groups (see TS 38.321 [3], clause 5.4.1, clause 5.4.4). | +| sizeDCI-2-6
Size of DCI format 2-6 (see TS 38.213 [13], clause 10.3). | +| sp-CSI-RNTI
RNTI for Semi-Persistent CSI reporting on PUSCH (see CSI-ReportConfig ) (see TS 38.214 [19], clause 5.2.1.5.2). Network always configures the UE with a value for this field when at least one CSI-ReportConfig with reportConfigType set to semiPersistentOnPUSCH is configured. | +| tpc-PUCCH-RNTI
RNTI used for PUCCH TPC commands on DCI (see TS 38.213 [13], clause 10.1). | +| tpc-PUSCH-RNTI
RNTI used for PUSCH TPC commands on DCI (see TS 38.213 [13], clause 10.1). | +| tpc-SRS-RNTI
RNTI used for SRS TPC commands on DCI (see TS 38.213 [13], clause 10.1). | +| twoQCLTypeDforPDCCHRepetition
Indicates whether a UE is expected UE to identify and monitor two QCL-TypeD properties for multiple overlapping CORESETs in the case of PDCCH repetition. | +| uci-MuxWithDiffPrio, uci-MuxWithDiffPrio-secondaryPUCCHgroup
When configured, enables multiplexing a high-priority (HP) HARQ-ACK UCI and a low-priority (LP) HARQ-ACK UCI into a PUCCH or PUSCH for the primary PUCCH group and the secondary PUCCH group, respectively. | +| ul-TotalDAI-Included
Indicates whether the total DAI fields of the additional PDSCH group is included in the non-fallback UL grant DCI (see TS 38.212 [17], clause 7.3.1). The network configures this only when enhanced dynamic codebook is configured ( pdsch-HARQ-ACK-Codebook is set to enhancedDynamic ). | +| xScale | + +The UE is allowed to drop NR only if the power scaling applied to NR results in a difference between scaled and unscaled NR UL of more than *xScale* dB (see TS 38.213 [13]). If the value is not configured for dynamic power sharing, the UE assumes default value of 6 dB. + +| MulticastConfig field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| pdsch-HARQ-ACK-CodebookListMulticast
A list of configurations for one or two HARQ-ACK codebooks for MBS multicast. Each configuration in the list is defined in the same way as pdsch-HARQ-ACK-Codebook (see TS 38.212 [17], clause 7.3.1.2.2 and TS 38.213 [13], clauses 7.2.1, 9.1.2, 9.1.3 and 9.2.1). If this field is present, the field pdsch-HARQ-ACK-Codebook is ignored. If this field is present, the value of this field is applied for primary PUCCH group and for secondary PUCCH group (if configured). | +| type1CodebookGenerationMode
Indicates the mode of Type-1 HARQ-ACK codebook generation, as specified in TS 38.213 [13]. Mode 1 is based on the k1 values that are in the intersection of K1 set for unicast and K1 set for multicast. Mode 2 is based on the k1 values that are in the union of K1 set for unicast and K1 set for multicast. | + +| PDSCH-HARQ-ACK-EnhType3 field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| pdsch-HARQ-ACK-EnhType3CBG
When configured, the DCI format 1_1 or DCI format 1_2 can request the UE to include CBG level A/N for each CC with CBG level transmission configured of the enhanced Type 3 HARQ-ACK codebook. When not configured, the UE will report TB level A/N even if CBG level transmission is configured for a CC. | +| pdsch-HARQ-ACK-EnhType3NDI
When configured, the DCI format 1_1 or DCI format 1_2 can request the UE to include NDI for each A/N reported of the enhanced Type 3 HARQ-ACK codebook. | +| perCC
Configures enhanced Type 3 HARQ-ACK codebook using per CC configuration. | +| perHARQ, perHARQ-Ext
Configures enhanced Type 3 HARQ-ACK codebook using per HARQ process and CC configuration. perHARQ-Ext is present only when nrofHARQ-ProcessesForPDSCH-v1700 is present in pdsch-ServingCellConfig of at least one serving cell in the PUCCH group. If perHARQ-Ext is present, the UE ignores perHARQ . | + +| CellDTRX-DCI-config field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| cellIDTRX-RNTI
The RNTI value for scrambling CRC of DCI format 2_9 for activating and/or deactivating Cell DTX/DRX and/or NES mode for CHO indication. | +| sizeDCI-2-9
The size of DCI format 2_9. | + +| Conditional Presence | Explanation | +|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCG-Only | This field is optionally present, Need R, in the PhysicalCellGroupConfig of the MCG. It is absent otherwise. | +| NCR | This field is optionally present, Need M for NCR-MT. It is absent otherwise. | +| SCG-Only | This field is optionally present, Need S, in the PhysicalCellGroupConfig of the SCG in (NG)EN-DC as defined in TS 38.213 [13]. It is absent otherwise. | +| twoPUCCHgroup | This field is optionally present, Need R, if secondary PUCCH group is configured. It is absent otherwise, Need R. | + +#### — *PLMN-Identity* + +The IE *PLMN-Identity* identifies a Public Land Mobile Network. Further information regarding how to set the IE is specified in TS 23.003 [21]. + +#### *PLMN-Identity* information element + +``` +-- ASN1START +-- TAG-PLMN-IDENTITY-START + +PLMN-Identity ::= + SEQUENCE { + mcc MCC OPTIONAL, -- Cond MCC + mnc MNC + } + +MCC ::= + SEQUENCE (SIZE (3)) OF MCC-MNC-Digit + +MNC ::= + SEQUENCE (SIZE (2..3)) OF MCC-MNC-Digit + +MCC-MNC-Digit ::= + INTEGER (0..9) + +-- TAG-PLMN-IDENTITY-STOP +-- ASN1STOP +``` + +#### *PLMN-Identity* field descriptions + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| mcc
The first element contains the first MCC digit, the second element the second MCC digit and so on. If the field is absent, it takes the same value as the mcc of the immediately preceding IE PLMN-Identity . See TS 23.003 [21]. | +| mnc
The first element contains the first MNC digit, the second element the second MNC digit and so on. See TS 23.003 [21]. | + +| Conditional Presence | Explanation | +|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCC | This field is mandatory present when PLMN-Identity is not used in a list or if it is the first entry of PLMN-Identity in a list. Otherwise it is optionally present, Need S. | + +#### — *PLMN-IdentityInfoList* + +The IE *PLMN-IdentityInfoList* includes a list of PLMN identity information. + +#### *PLMN-IdentityInfoList* information element + +``` +-- ASN1START +-- TAG-PLMN-IDENTITYINFOLIST-START +``` + +``` + +PLMN-IdentityInfoList ::= SEQUENCE (SIZE (1..maxPLMN)) OF PLMN-IdentityInfo + +PLMN-IdentityInfo ::= SEQUENCE { + plmn-IdentityList SEQUENCE (SIZE (1..maxPLMN)) OF PLMN-Identity, + trackingAreaCode TrackingAreaCode OPTIONAL, -- Need R + ranac RAN-AreaCode OPTIONAL, -- Need R + cellIdentity CellIdentity, + cellReservedForOperatorUse ENUMERATED {reserved, notReserved}, + ..., + [[ + iab-Support-r16 ENUMERATED {true} OPTIONAL -- Need S + ]], + [[ + trackingAreaList-r17 SEQUENCE (SIZE (1..maxTAC-r17)) OF TrackingAreaCode OPTIONAL, -- Need R + gNB-ID-Length-r17 INTEGER (22..32) OPTIONAL -- Cond eventID-TSS + ]], + [[ + mobileIAB-Support-r18 ENUMERATED {true} OPTIONAL -- Need S + ]] +} + +-- TAG-PLMN-IDENTITYINFOLIST-STOP +-- ASN1STOP + +``` + +| PLMN-IdentityInfo field descriptions | | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| cellReservedForOperatorUse | Indicates whether the cell is reserved for operator use (per PLMN), as defined in TS 38.304 [20]. This field is ignored by IAB-MT and NCR-MT. | +| gNB-ID-Length | Indicates the length of the gNB ID out of the 36-bit long cellIdentity . This field is always present if the mobileIAB-Support is broadcasted in a cell. | +| iab-Support | This field combines both the support of IAB and the cell status for IAB. If the field is present, the cell supports IAB and the cell is also considered as a candidate for cell (re)selection for IAB-node; if the field is absent, the cell does not support IAB and/or the cell is barred for IAB-node. | +| mobileIAB-Support | This field indicates the support of mobile IAB. If the field is absent, the cell is barred for mobile IAB-node. | +| trackingAreaCode | Indicates Tracking Area Code to which the cell indicated by cellIdentity field belongs. The absence of the field indicates that the cell only supports PSCell/SCell functionality (per PLMN) or is an NTN cell. | +| trackingAreaList | List of Tracking Areas to which the cell indicated by cellIdentity field belongs. If this field is present, network does not configure trackingAreaCode . Total number of different TACs across different PLMN-IdentityInfos shall not exceed maxTAC . This field is only present in an NTN cell. | + +| Conditional Presence | Explanation | +|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| eventID-TSS | If eventID-TSS is present in SIB9, this field is mandatory present in the PLMN-IdentityInfo IE of PLMN-IdentityInfoList in SIB1. Otherwise, the field is optionally present, Need R. | + +#### — *PLMN-IdentityList2* + +Includes a list of PLMN identities. + +#### *PLMN-IdentityList2* information element + +``` +-- ASN1START +-- TAG-PLMNIDENTITYLIST2-START + +PLMN-IdentityList2-r16 ::= SEQUENCE (SIZE (1..16)) OF PLMN-Identity + +-- TAG-PLMNIDENTITYLIST2-STOP +-- ASN1STOP +``` + +#### — *PRB-Id* + +The IE *PRB-Id* identifies a Physical Resource Block (PRB) position within a carrier. + +#### *PRB-Id* information element + +``` +-- ASN1START +-- TAG-PRB-ID-START + +PRB-Id ::= INTEGER (0..maxNrofPhysicalResourceBlocks-1) + +-- TAG-PRB-ID-STOP +-- ASN1STOP +``` + +#### — *PTRS-DownlinkConfig* + +The IE *PTRS-DownlinkConfig* is used to configure downlink phase tracking reference signals (PTRS) (see TS 38.214 [19] clause 5.1.6.3) + +#### *PTRS-DownlinkConfig* information element + +``` +-- ASN1START +-- TAG-PTRS-DOWNLINKCONFIG-START + +PTRS-DownlinkConfig ::= SEQUENCE { + frequencyDensity SEQUENCE (SIZE (2)) OF INTEGER (1..276) OPTIONAL, -- Need S + timeDensity SEQUENCE (SIZE (3)) OF INTEGER (0..29) OPTIONAL, -- Need S + epre-Ratio INTEGER (0..3) OPTIONAL, -- Need S + resourceElementOffset ENUMERATED { offset01, offset10, offset11 } OPTIONAL, -- Need S + ... + [[ + maxNrofPorts-r16 ENUMERATED {n1, n2} OPTIONAL -- Need R + ]] +``` + +``` + + ] ] +} + +-- TAG-PTRS-DOWNLINKCONFIG-STOP +-- ASN1STOP + +``` + +#### PTRS-DownlinkConfig field descriptions + +| | | +|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| epre-Ratio | EPRE ratio between PTRS and PDSCH. Value 0 corresponds to the codepoint "00" in table 4.1-2. Value 1 corresponds to codepoint "01", and so on. If the field is not provided, the UE applies value 0 (see TS 38.214 [19], clause 4.1). | +| frequencyDensity | Presence and frequency density of DL PT-RS as a function of Scheduled BW. If the field is absent, the UE uses K_PT-RS = 2 (see TS 38.214 [19], clause 5.1.6.3, table 5.1.6.3-2). | +| maxNrofPorts | The maximum number of DL PTRS ports specified in TS 38.214 [19] (clause 5.1.6.3). 2 PT-RS ports can only be configured for a DL BWP that is configured, as specified in TS 38.214 [19] clause 5.1, with a mode where a single PDSCH has association between the DM-RS ports and the TCI states as defined in TS 38.214 [19] clause 5.1.6.2. | +| resourceElementOffset | Indicates the subcarrier offset for DL PTRS. If the field is absent, the UE applies the value offset00 (see TS 38.211 [16], clause 7.4.1.2.2). | +| timeDensity | Presence and time density of DL PT-RS as a function of MCS. The value 29 is only applicable for MCS Table 5.1.3.1-1 (TS 38.214 [19]). If the field is absent, the UE uses L_PT-RS = 1 (see TS 38.214 [19], clause 5.1.6.3, table 5.1.6.3-1). | + +#### — PTRS-UplinkConfig + +The IE *PTRS-UplinkConfig* is used to configure uplink Phase-Tracking-Reference-Signals (PTRS). + +#### PTRS-UplinkConfig information element + +``` + +-- ASN1START +-- TAG-PTRS-UPLINKCONFIG-START + +PTRS-UplinkConfig ::= + transformPrecoderDisabled + frequencyDensity + timeDensity + maxNrofPorts + resourceElementOffset + ptrs-Power + } + transformPrecoderEnabled + sampleDensity + timeDensityTransformPrecoding + } + ... + SEQUENCE { + SEQUENCE { + SEQUENCE (SIZE (2)) OF INTEGER (1..276) + SEQUENCE (SIZE (3)) OF INTEGER (0..29) + ENUMERATED {n1, n2}, + ENUMERATED {offset01, offset10, offset11 } + ENUMERATED {p00, p01, p10, p11} + } + SEQUENCE { + SEQUENCE (SIZE (5)) OF INTEGER (1..276), + ENUMERATED {d2} + } + } + +``` + +OPTIONAL, -- Need S +OPTIONAL, -- Need S +OPTIONAL, -- Need S +OPTIONAL, -- Need R +OPTIONAL -- Need S +OPTIONAL, -- Need R + +``` + +[[ + maxNrofPorts-SDM-r18 ENUMERATED {n1, n2} OPTIONAL -- Need R +]] +} + +-- TAG-PTRS-ULINKCONFIG-STOP +-- ASN1STOP + +``` + +| PTRS-UplinkConfig field descriptions | | +|----------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| frequencyDensity | Presence and frequency density of UL PT-RS for CP-OFDM waveform as a function of scheduled BW If the field is absent, the UE uses $K\_PT-RS = 2$ (see TS 38.214 [19], clause 6.1). | +| maxNrofPorts, maxNrofPorts-SDM | The maximum number of UL PTRS ports for CP-OFDM (see TS 38.214 [19], clause 6.2.3.1). | +| ptrs-Power | UL PTRS power boosting factor per PTRS port (see TS 38.214 [19], clause 6.1, table 6.2.3.1.3). | +| resourceElementOffset | Indicates the subcarrier offset for UL PTRS for CP-OFDM. If the field is absent, the UE applies the value offset00 (see TS 38.211 [16], clause 6.4.1.2.2). | +| sampleDensity | Sample density of PT-RS for DFT-s-OFDM, pre-DFT, indicating a set of thresholds $T=\{NRBn, n=0,1,2,3,4\}$ , that indicates dependency between presence of PT-RS and scheduled BW and the values of X and K the UE should use depending on the scheduled BW, see TS 38.214 [19], clause 6.1, table 6.2.3.2-1. | +| timeDensity | Presence and time density of UL PT-RS for CP-OFDM waveform as a function of MCS If the field is absent, the UE uses $L\_PT-RS = 1$ (see TS 38.214 [19], clause 6.1). | +| timeDensityTransformPrecoding | Time density (OFDM symbol level) of PT-RS for DFT-s-OFDM. If the field is absent, the UE applies value d1 (see TS 38.214 [19], clause 6.1). | +| transformPrecoderDisabled | Configuration of UL PTRS without transform precoder (with CP-OFDM). | +| transformPrecoderEnabled | Configuration of UL PTRS with transform precoder (DFT-S-OFDM). | + +#### — *PUCCH-Config* + +The IE *PUCCH-Config* is used to configure UE specific PUCCH parameters (per BWP). + +#### ***PUCCH-Config* information element** + +``` + +-- ASN1START +-- TAG-PUCCH-CONFIG-START + +PUCCH-Config ::= SEQUENCE { + resourceSetToAddModList SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceSets)) OF PUCCH-ResourceSet OPTIONAL, -- Need N + resourceSetToReleaseList SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceSets)) OF PUCCH-ResourceSetId OPTIONAL, -- Need N + resourceToAddModList SEQUENCE (SIZE (1..maxNrofPUCCH-Resources)) OF PUCCH-Resource OPTIONAL, -- Need N + resourceToReleaseList SEQUENCE (SIZE (1..maxNrofPUCCH-Resources)) OF PUCCH-ResourceId OPTIONAL, -- Need N +} + +``` + +``` + +format1 SetupRelease { PUCCH-FormatConfig } OPTIONAL, -- Need M +format2 SetupRelease { PUCCH-FormatConfig } OPTIONAL, -- Need M +format3 SetupRelease { PUCCH-FormatConfig } OPTIONAL, -- Need M +format4 SetupRelease { PUCCH-FormatConfig } OPTIONAL, -- Need M +schedulingRequestResourceToAddModList SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF SchedulingRequestResourceConfig + OPTIONAL, -- Need N +schedulingRequestResourceToReleaseList SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF SchedulingRequestResourceId + OPTIONAL, -- Need N +multi-CSI-PUCCH-ResourceList SEQUENCE (SIZE (1..2)) OF PUCCH-ResourceId OPTIONAL, -- Need M +dl-DataToUL-ACK SEQUENCE (SIZE (1..8)) OF INTEGER (0..15) OPTIONAL, -- Need M +spatialRelationInfoToAddModList SEQUENCE (SIZE (1..maxNrofSpatialRelationInfos)) OF PUCCH-SpatialRelationInfo + OPTIONAL, -- Need N +spatialRelationInfoToReleaseList SEQUENCE (SIZE (1..maxNrofSpatialRelationInfos)) OF PUCCH-SpatialRelationInfoId + OPTIONAL, -- Need N +pucch-PowerControl PUCCH-PowerControl OPTIONAL, -- Need M +..., +[[ +resourceToAddModListExt-v1610 SEQUENCE (SIZE (1..maxNrofPUCCH-Resources)) OF PUCCH-ResourceExt-v1610 OPTIONAL, -- Need N +dl-DataToUL-ACK-r16 SetupRelease { DL-DataToUL-ACK-r16 } OPTIONAL, -- Need M +ul-AccessConfigListDCI-1-1-r16 SetupRelease { UL-AccessConfigListDCI-1-1-r16 } OPTIONAL, -- Need M +subslotLengthForPUCCH-r16 CHOICE { + normalCP-r16 ENUMERATED {n2,n7}, + extendedCP-r16 ENUMERATED {n2,n6} +} + OPTIONAL, -- Need R +dl-DataToUL-ACK-DCI-1-2-r16 SetupRelease { DL-DataToUL-ACK-DCI-1-2-r16 } OPTIONAL, -- Need M +numberOfBitsForPUCCH-ResourceIndicatorDCI-1-2-r16 INTEGER (0..3) OPTIONAL, -- Need R +dmrs-UplinkTransformPrecodingPUCCH-r16 ENUMERATED {enabled} OPTIONAL, -- Cond PI2-BPSK +spatialRelationInfoToAddModListSizeExt-v1610 SEQUENCE (SIZE (1..maxNrofSpatialRelationInfosDiff-r16)) OF PUCCH-SpatialRelationInfo + OPTIONAL, -- Need N +spatialRelationInfoToReleaseListSizeExt-v1610 SEQUENCE (SIZE (1..maxNrofSpatialRelationInfosDiff-r16)) OF PUCCH-SpatialRelationInfoId + OPTIONAL, -- Need N +spatialRelationInfoToAddModListExt-v1610 SEQUENCE (SIZE (1..maxNrofSpatialRelationInfos-r16)) OF PUCCH-SpatialRelationInfoExt-r16 + OPTIONAL, -- Need N +spatialRelationInfoToReleaseListExt-v1610 SEQUENCE (SIZE (1..maxNrofSpatialRelationInfos-r16)) OF + PUCCH-SpatialRelationInfoId-r16 OPTIONAL, -- Need N +resourceGroupToAddModList-r16 SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceGroups-r16)) OF PUCCH-ResourceGroup-r16 + OPTIONAL, -- Need N +resourceGroupToReleaseList-r16 SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceGroups-r16)) OF PUCCH-ResourceGroupId-r16 + OPTIONAL, -- Need N +sps-PUCCH-AN-List-r16 SetupRelease { SPS-PUCCH-AN-List-r16 } OPTIONAL, -- Need M +schedulingRequestResourceToAddModListExt-v1610 SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF SchedulingRequestResourceConfigExt-v1610 + OPTIONAL -- Need N +]], +[[ +format0-r17 SetupRelease { PUCCH-FormatConfig } OPTIONAL, -- Need M +format2Ext-r17 SetupRelease { PUCCH-FormatConfigExt-r17 } OPTIONAL, -- Need M +format3Ext-r17 SetupRelease { PUCCH-FormatConfigExt-r17 } OPTIONAL, -- Need M +format4Ext-r17 SetupRelease { PUCCH-FormatConfigExt-r17 } OPTIONAL, -- Need M +ul-AccessConfigListDCI-1-2-r17 SetupRelease { UL-AccessConfigListDCI-1-2-r17 } OPTIONAL, -- Need M +mappingPattern-r17 ENUMERATED {cyclicMapping, sequentialMapping} OPTIONAL, -- Need R +powerControlSetInfoToAddModList-r17 SEQUENCE (SIZE (1..maxNrofPowerControlSetInfos-r17)) OF PUCCH-PowerControlSetInfo-r17 + +``` + +``` + +powerControlSetInfoToReleaseList-r17 SEQUENCE (SIZE (1..maxNrofPowerControlSetInfos-r17)) OF PUCCH-PowerControlSetInfoId-r17 OPTIONAL, -- Need N +secondTPCFieldDCI-1-1-r17 ENUMERATED {enabled} OPTIONAL, -- Need N +secondTPCFieldDCI-1-2-r17 ENUMERATED {enabled} OPTIONAL, -- Need R +dl-DataToUL-ACK-r17 SetupRelease { DL-DataToUL-ACK-r17 } OPTIONAL, -- Need R +dl-DataToUL-ACK-DCI-1-2-r17 SetupRelease { DL-DataToUL-ACK-DCI-1-2-r17 } OPTIONAL, -- Need M +ul-AccessConfigListDCI-1-1-r17 SetupRelease { UL-AccessConfigListDCI-1-1-r17 } OPTIONAL, -- Need M +schedulingRequestResourceToAddModListExt-v1700 SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF SchedulingRequestResourceConfigExt-v1700 OPTIONAL, -- Need N +dmrs-BundlingPUCCH-Config-r17 SetupRelease { DMRS-BundlingPUCCH-Config-r17 } OPTIONAL, -- Need M +dl-DataToUL-ACK-v1700 SetupRelease { DL-DataToUL-ACK-v1700 } OPTIONAL, -- Need M +dl-DataToUL-ACK-MulticastDCI-Format4-1-r17 SetupRelease { DL-DataToUL-ACK-MulticastDCI-Format4-1-r17 } OPTIONAL, -- Need M +sps-PUCCH-AN-ListMulticast-r17 SetupRelease { SPS-PUCCH-AN-List-r16 } OPTIONAL, -- Need M +]] +} + +PUCCH-FormatConfig ::= SEQUENCE { + interslotFrequencyHopping ENUMERATED {enabled} OPTIONAL, -- Need R + additionalDMRS ENUMERATED {true} OPTIONAL, -- Need R + maxCodeRate PUCCH-MaxCodeRate OPTIONAL, -- Need R + nrofSlots ENUMERATED {n2,n4,n8} OPTIONAL, -- Need S + pi2BPSK ENUMERATED {enabled} OPTIONAL, -- Need R + simultaneousHARQ-ACK-CSI ENUMERATED {true} OPTIONAL, -- Need R +} + +PUCCH-FormatConfigExt-r17 ::= SEQUENCE { + maxCodeRateLP-r17 PUCCH-MaxCodeRate OPTIONAL, -- Need R + ... +} + +PUCCH-MaxCodeRate ::= ENUMERATED {zeroDot08, zeroDot15, zeroDot25, zeroDot35, zeroDot45, zeroDot60, zeroDot80} + +-- A set with one or more PUCCH resources +PUCCH-ResourceSet ::= SEQUENCE { + pucch-ResourceSetId PUCCH-ResourceSetId, + resourceList SEQUENCE (SIZE (1..maxNrofPUCCH-ResourcesPerSet)) OF PUCCH-ResourceId, + maxPayloadSize INTEGER (4..256) OPTIONAL, -- Need R +} + +PUCCH-ResourceSetId ::= INTEGER (0..maxNrofPUCCH-ResourceSets-1) + +PUCCH-Resource ::= SEQUENCE { + pucch-ResourceId PUCCH-ResourceId, + startingPRB PRB-Id, + intraSlotFrequencyHopping ENUMERATED { enabled } OPTIONAL, -- Need R + secondHopPRB PRB-Id OPTIONAL, -- Need R + format CHOICE { + format0 PUCCH-format0, + format1 PUCCH-format1, + format2 PUCCH-format2, + } +} + +``` + +``` + + format3 PUCCH-format3, + format4 PUCCH-format4 + } +} + +PUCCH-ResourceExt-v1610 ::= + interlaceAllocation-r16 + rb-SetIndex-r16 + interlace0-r16 + scs15 + scs30 + } +} +format-v1610 + interlace1-v1610 + occ-v1610 + occ-Length-v1610 + occ-Index-v1610 + } +} +... +[[ +format-v1700 + nrofPRBs-r17 +} +pucch-RepetitionNrofSlots-r17 +]], +[[ +applyIndicatedTCI-State-r18 +multipanelSFN-Scheme-r18 +]] +} + +PUCCH-ResourceId ::= + INTEGER (0..maxNrofPUCCH-Resources-1) + +PUCCH-format0 ::= + initialCyclicShift + nrofSymbols + startingSymbolIndex +} + +PUCCH-format1 ::= + initialCyclicShift + nrofSymbols + startingSymbolIndex + timeDomainOCC +} + +PUCCH-format2 ::= + nrofPRBs + +``` + +``` + +SEQUENCE { + SEQUENCE { + INTEGER (0..4), + CHOICE { + INTEGER (0..9), + INTEGER (0..4) + } + } +} +OPTIONAL, --Need R + +CHOICE { + INTEGER (0..9), + SEQUENCE { + ENUMERATED {n2,n4} + ENUMERATED {n0,n1,n2,n3} + } +} +OPTIONAL, -- Need M +OPTIONAL -- Need M + +OPTIONAL, -- Need R + +SEQUENCE { + INTEGER (1..16) +} +OPTIONAL, -- Need R +OPTIONAL -- Need R + +ENUMERATED { n1,n2,n4,n8 } +OPTIONAL, -- Need R +OPTIONAL -- Need R + +ENUMERATED {first, second, both} +ENUMERATED {enabled} +OPTIONAL, -- Need R +OPTIONAL -- Need R + +INTEGER (0..maxNrofPUCCH-Resources-1) + +SEQUENCE { + INTEGER (0..11), + INTEGER (1..2), + INTEGER (0..13) +} + +SEQUENCE { + INTEGER (0..11), + INTEGER (4..14), + INTEGER (0..10), + INTEGER (0..6) +} + +SEQUENCE { + INTEGER (1..16), + +``` + +``` + nrofSymbols INTEGER (1..2), + startingSymbolIndex INTEGER (0..13) + } + + PUCCH-format3 ::= SEQUENCE { + nrofPRBs INTEGER (1..16), + nrofSymbols INTEGER (4..14), + startingSymbolIndex INTEGER (0..10) + } + + PUCCH-format4 ::= SEQUENCE { + nrofSymbols INTEGER (4..14), + occ-Length ENUMERATED {n2,n4}, + occ-Index ENUMERATED {n0,n1,n2,n3}, + startingSymbolIndex INTEGER (0..10) + } + + PUCCH-ResourceGroup-r16 ::= SEQUENCE { + pucch-ResourceGroupId-r16, + resourcePerGroupList-r16 SEQUENCE (SIZE (1..maxNrofPUCCH-ResourcesPerGroup-r16)) OF PUCCH-ResourceId + } + + PUCCH-ResourceGroupId-r16 ::= INTEGER (0..maxNrofPUCCH-ResourceGroups-1-r16) + + DL-DataToUL-ACK-r16 ::= SEQUENCE (SIZE (1..8)) OF INTEGER (-1..15) + + DL-DataToUL-ACK-r17 ::= SEQUENCE (SIZE (1..8)) OF INTEGER (-1..127) + + DL-DataToUL-ACK-v1700 ::= SEQUENCE (SIZE (1..8)) OF INTEGER (16..31) + + DL-DataToUL-ACK-DCI-1-2-r16 ::= SEQUENCE (SIZE (1..8)) OF INTEGER (0..15) + + DL-DataToUL-ACK-DCI-1-2-r17 ::= SEQUENCE (SIZE (1..8)) OF INTEGER (0..127) + + UL-AccessConfigListDCI-1-1-r16 ::= SEQUENCE (SIZE (1..16)) OF INTEGER (0..15) + + UL-AccessConfigListDCI-1-2-r17 ::= SEQUENCE (SIZE (1..16)) OF INTEGER (0..15) + + UL-AccessConfigListDCI-1-1-r17 ::= SEQUENCE (SIZE (1..3)) OF INTEGER (0..2) + + DL-DataToUL-ACK-MulticastDCI-Format4-1-r17 ::= SEQUENCE (SIZE (1..8)) OF INTEGER (0..15) + + -- TAG-PUCCH-CONFIG-STOP + -- ASN1STOP +``` + +| PUCCH-Config field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| dl-DataToUL-ACK, dl-DataToUL-ACK-DCI-1-2
List of timing for given PDSCH to the DL ACK (see TS 38.213 [13], clause 9.1.2). The field dl-DataToUL-ACK applies to DCI format 1_1 and the field dl-DataToUL-ACK-DCI-1-2 applies to DCI format 1_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 9.2.3). The dl-DataToUL-ACK-v1700 is applicable for NTN and dl-DataToUL-ACK-r17 is applicable for up to 71 GHz. If dl-DataToUL-ACK-r16 or dl-DataToUL-ACK-r17 or dl-DataToUL-ACK-v1700 is signalled, UE shall ignore the dl-DataToUL-ACK (without suffix). The value -1 corresponds to "inapplicable value" for the case where the A/N feedback timing is not explicitly included at the time of scheduling PDSCH. The fields dl-DataToUL-ACK-r17 and dl-DataToUL-ACK-DCI-1-2-r17 are only applicable for SCS of 480 kHz or 960 kHz. | +| dl-DataToUL-ACK-MulticastDCI-Format4-1
List of timing for given group-common PDSCH to the DL ACK (see TS 38.213 [13], clause 9.1.2). The field dl-DataToUL-ACK-MulticastDciFormat4-1 applies to DCI format 4_1 for MBS multicast (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 9.2.3). | +| dmrs-BundlingPUCCH-Config
Configuration of the parameters for DMRS bundling for PUCCH (see TS 38.214 [19], clause 6.1.7). DMRS bundling for PUCCH is not supported for PUCCH format 0/2. In this release, this is not applicable to FR2-2. | +| dmrs-UplinkTransformPrecodingPUCCH
This field is used for PUCCH formats 3 and 4 according to TS 38.211, Clause 6.4.1.3.3.1. | +| format0
Parameters that are common for all PUCCH resources of format 0. | +| format1
Parameters that are common for all PUCCH resources of format 1. | +| format2
Parameters that are common for all PUCCH resources of format 2. | +| format3
Parameters that are common for all PUCCH resources of format 3. | +| format4
Parameters that are common for all PUCCH resources of format 4. | +| mappingPattern
Indicates whether the UE should follow Cyclical mapping pattern or Sequential mapping pattern for when a PUCCH resource used for repetitions of a PUCCH transmission includes first and second spatial settings for FR2, or first and second sets of power control parameters for FR1 (see TS 38.213 [13], clause 9.2.6). | +| numberOfBitsForPUCCH-ResourceIndicatorDCI-1-2
Configuration of the number of bits for "PUCCH resource indicator" in DCI format 1_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 9.2.3). | +| powerControlSetInfoToAddModList
Configures power control sets for repetition of a PUCCH transmission in FR1. This field is not configured if ul-powerControl is configured in the BWP-UplinkDedicated in which the PUCCH-Config is included. | +| pucch-PowerControl
Configures power control parameters PUCCH transmission. This field is not configured if unifiedTCI-StateType is configured for the serving cell. | +| resourceGroupToAddModList, resourceGroupToReleaseList
Lists for adding and releasing groups of PUCCH resources that can be updated simultaneously for spatial relations with a MAC CE. | +| resourceSetToAddModList, resourceSetToReleaseList
Lists for adding and releasing PUCCH resource sets (see TS 38.213 [13], clause 9.2). | +| resourceToAddModList, resourceToAddModListExt, resourceToReleaseList
Lists for adding and releasing PUCCH resources applicable for the UL BWP and serving cell in which the PUCCH-Config is defined. The resources defined herein are referred to from other parts of the configuration to determine which resource the UE shall use for which report. If the network includes of resourceToAddModListExt , it includes the same number of entries, and listed in the same order, as in resourceToAddModList . | +| secondTPCFieldDCI-1-1, secondTPCFieldDCI-1-2 | + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| A second TPC field can be configured via RRC for DCI-1-1 and DCI-1-2. Each TPC field is for each closed-loop index value respectively (i.e., 1st /2nd TPC fields correspond to "closedLoopIndex" value = 0 and 1. | +| spatialRelationInfoToAddModList, spatialRelationInfoToAddModListSizeExt, spatialRelationInfoToAddModListExt
Configuration of the spatial relation between a reference RS and PUCCH. Reference RS can be SSB/CSI-RS/SRS. If the list has more than one element, MAC-CE selects a single element (see TS 38.321 [3], clause 5.18.8 and TS 38.213 [13], clause 9.2.2). The UE shall consider entries in spatialRelationInfoToAddModList and in spatialRelationInfoToAddModListSizeExt as a single list, i.e. an entry created using spatialRelationInfoToAddModList can be modified using spatialRelationInfoToAddModListSizeExt (or deleted using spatialRelationInfoToReleaseListSizeExt ) and vice-versa. If the network includes spatialRelationInfoToAddModListExt , it includes the same number of entries, and listed in the same order, as in the concatenation of spatialRelationInfoToAddModList and of spatialRelationInfoToAddModListSizeExt . If unifiedTCI-StateType is configured for the serving cell, no element in this list is configured. | +| spatialRelationInfoToReleaseList, spatialRelationInfoToReleaseListSizeExt, spatialRelationInfoToReleaseListExt
Lists of spatial relation configurations between a reference RS and PUCCH to be released by the UE. | +| sps-PUCCH-AN-List
Indicates a list of PUCCH resources for DL SPS HARQ ACK. The field maxPayloadSize is absent for the first and the last SPS-PUCCH-AN in the list. If configured, this overrides n1PUCCH-AN in SPS-config . | +| sps-PUCCH-AN-ListMulticast
The field is used to configure the list of PUCCH resources per HARQ ACK codebook for MBS multicast. | +| subslotLengthForPUCCH
Indicates the sub-slot length for sub-slot based PUCCH feedback in number of symbols (see TS 38.213 [13], clause 9). Value n2 corresponds to 2 symbols, value n6 corresponds to 6 symbols, value n7 corresponds to 7 symbols. For normal CP, the value is either n2 or n7 . For extended CP, the value is either n2 or n6 . | +| ul-AccessConfigListDCI-1-1, ul-AccessConfigListDCI-1-2
List of the combinations of cyclic prefix extension and UL channel access type (see TS 38.212 [17], clause 7.3.1) applicable, respectively, to DCI format 1_1 and DCI format 1_2. The fields ul-AccessConfigListDCI-1-1-r16 and ul-AccessConfigListDCI-1-2-r17 are only applicable for FR1 (see TS 38.212 [17], Table 7.3.1.2.2-6). The field ul-AccessConfigListDCI-1-1-r17 indicates a list which only contains UL channel access types and is only applicable for FR2-2 (see TS 38.212 [17], Table 7.3.1.2.2-6A). | + +| PUCCH-format3 field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------| +| nrofPRBs
The supported values are 1,2,3,4,5,6,8,9,10,12,15 and 16. The UE shall ignore this field when format-v1610 is configured. | + +| PUCCH-FormatConfig, PUCCH-FormatConfigExt field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| additionalDMRS
If the field is present, the UE enables 2 DMRS symbols per hop of a PUCCH Format 3 or 4 if both hops are more than X symbols when FH is enabled (X=4). And it enables 4 DMRS symbols for a PUCCH Format 3 or 4 with more than 2X+1 symbols when FH is disabled (X=4). The field is not applicable for format 0, 1 and 2. See TS 38.213 [13], clause 9.2.2. | +| interslotFrequencyHopping
If the field is present, the UE enables inter-slot frequency hopping when PUCCH Format 0, 1, 2, 3 or 4 is repeated over multiple slots. For a PUCCH over multiple slots, the intra and inter slot frequency hopping cannot be enabled at the same time for a UE. See TS 38.213 [13], clause 9.2.6. | +| maxCodeRate
Max coding rate to determine how to feedback UCI on PUCCH for format 2, 3 or 4. The field is not applicable for format 0 and 1. See TS 38.213 [13], clause 9.2.5. | +| maxCodeRateLP
Max coding rate to determine how to feedback UCI on PUCCH for format 2, 3 or 4. The field is not applicable for format 0 and 1. This field configures additional max code rate in the second entry of PUCCH-ConfigurationList-r16 for multiplexing low-priority (LP) HARQ-ACK and high-priority (HP) UCI in a PUCCH as described Clause 9.2.5.3 of TS 38.213 [13]. The field is absent for the first entry of PUCCH-ConfigurationList-r16 . | +| nrofSlots
Number of slots with the same PUCCH. When the field is absent the UE applies the value n1 . See TS 38.213 [13], clause 9.2.6. | +| pi2BPSK
If the field is present, the UE uses pi/2 BPSK for UCI symbols instead of QPSK for PUCCH. The field is not applicable for format 0, 1 and 2. See TS 38.213 [13], clause 9.2.5. | +| rb-SetIndex
Indicates the RB set where PUCCH resource is allocated. | +| simultaneousHARQ-ACK-CSI
If the field is present, the UE uses simultaneous transmission of CSI and HARQ-ACK feedback with or without SR with PUCCH Format 2, 3 or 4. See TS 38.213 [13], clause 9.2.5. When the field is absent the UE applies the value off . The field is not applicable for format 0 and 1. | + +| PUCCH-Resource, PUCCH-ResourceExt field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| applyIndicatedTCI-State
This field indicates, for PUCCH transmission(s) corresponding to this PUCCH resource, if UE applies the first, the second or both "indicated" UL only TCI or joint TCI as specified in TS 38.213 9.2.2. For PUCCH resources belonging to a PUCCH group, network configures same value. If more than one value for the field coresetPoolIndex is configured in IE controlResourceSet for the BWP, the value 'first' corresponds to the "indicated" joint/UL TCI states specific to coresetPoolIndex value 0 and the value 'second' corresponds to the value 1, respectively. In this case, network does not configure the value 'both'. | +| format
Selection of the PUCCH format (format 0 – 4) and format-specific parameters, see TS 38.213 [13], clause 9.2. format0 and format1 are only allowed for a resource in a first PUCCH resource set. format2 , format3 and format4 are only allowed for a resource in non-first PUCCH resource set. The network can only configure format-v1610 when format is set to format2 or format3 . The network only configures format-v1700 when format is set to format0 , format1 or format4 . | +| interlace0
This is the only interlace of interlaced PUCCH Format 0 and 1 and the first interlace for interlaced PUCCH Format 2 and 3. | +| interlace1
A second interlace, in addition to interlace 0, as specified in TS 38.213 [13], clause 9.2.1. For 15kHz SCS, values {0..9} are applicable; for 30kHz SCS, values {0..4} are applicable. For 15kHz SCS, the values of interlace1 shall satisfy interlace1 =mod( interlace0 +X,10) where X=1, -1, or 5. | +| intraSlotFrequencyHopping
Enabling intra-slot frequency hopping, applicable for all types of PUCCH formats. For long PUCCH over multiple slots, the intra and inter slot frequency hopping cannot be enabled at the same time for a UE. See TS 38.213 [13], clause 9.2.1. | +| nrofPRBs
Indicates the number of PRBs used per PUCCH resource for the PUCCH format, see TS 38.213 [13], clause 9.2.1. This field is applicable for PUCCH format0 , format1 , and format4 in FR2-2. The supported values for format4 are 1,2,3,4,5,6,8,9,10,12,15 and 16. | +| multipanelSFN-Scheme
Parameter to configure multiple panel simultaneous uplink transmission SFN scheme for PUCCH resources Ref XXX. | +| occ-Index
Indicates the orthogonal cover code index (see TS 38.213 [13], clause 9.2.1). This field is applicable when useInterlacePUCCH-PUSCH-16 is configured. | +| occ-Length
Indicates the orthogonal cover code length (see TS 38.213 [13], clause 9.2.1). This field is applicable when useInterlacePUCCH-PUSCH-16 is configured. | +| pucch-RepetitionNrofSlots
Configuration of PUCCH repetition factor per PUCCH resource with associated scheduling DCI corresponding to Rel-17 dynamic PUCCH repetition. For a PUCCH resource, if both the field pucch-RepetitionNrofSlots and the field nrofSlots are present, the field nrofSlots is ignored and apply the value of pucch-RepetitionNrofSlots corresponding to Rel-17 dynamic PUCCH repetition. If this field is absent in a PUCCH resource with associated scheduling DCI, the UE applies the value of field nrofSlots . | +| pucch-ResourceId
Identifier of the PUCCH resource. | +| secondHopPRB
Index of first PRB after frequency hopping of PUCCH. This value is applicable for intra-slot frequency hopping (see TS 38.213 [13], clause 9.2.1) or inter-slot frequency hopping (see TS 38.213 [13], clause 9.2.6). | + +| PUCCH-ResourceSet field descriptions | | +|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| maxPayloadSize | Maximum number of UCI information bits that the UE may transmit using this PUCCH resource set (see TS 38.213 [13], clause 9.2.1). In a PUCCH occurrence, the UE chooses the first of its PUCCH-ResourceSet which supports the number of bits that the UE wants to transmit. The field is absent in the first set (Set0) and in the last configured set since the UE derives the maximum number of UCI information bits as specified in TS 38.213 [13], clause 9.2.1. This field can take integer values that are multiples of 4. | +| resourceList | PUCCH resources of format0 and format1 are only allowed in the first PUCCH resource set, i.e., in a PUCCH-ResourceSet with pucch-ResourceSetId = 0. This set may contain between 1 and 32 resources. PUCCH resources of format2 , format3 and format4 are only allowed in a PUCCH-ResourceSet with pucch-ResourceSetId > 0. If present, these sets contain between 1 and 8 resources each. The UE chooses a PUCCH-Resource from this list as specified in TS 38.213 [13], clause 9.2.3. Note that this list contains only a list of resource IDs. The actual resources are configured in PUCCH-Config . | + +| Conditional Presence | Explanation | +|-----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PI2-BPSK | The field is optionally present, Need R, if format3 and/or format4 are configured and pi2BPSK is configured in each of them. It is absent, Need R otherwise. | + +#### – *PUCCH-ConfigCommon* + +The IE *PUCCH-ConfigCommon* is used to configure the cell specific PUCCH parameters. + +#### *PUCCH-ConfigCommon* information element + +``` +-- ASN1START +-- TAG-PUCCH-CONFIGCOMMON-START + +PUCCH-ConfigCommon ::= + SEQUENCE { + pucch-ResourceCommon INTEGER (0..15) OPTIONAL, -- Cond InitialBWP-Only + pucch-GroupHopping ENUMERATED { neither, enable, disable }, + hoppingId INTEGER (0..1023) OPTIONAL, -- Need R + p0-nominal INTEGER (-202..24) OPTIONAL, -- Need R + ... + [[ + nrofPRBs INTEGER (1..16) OPTIONAL, -- Need R + intra-SlotFH-r17 ENUMERATED {fromLowerEdge, fromUpperEdge} OPTIONAL, -- Cond InitialBWP-RedCapOnly + pucch-ResourceCommonRedCap-r17 INTEGER (0..15) OPTIONAL, -- Cond InitialBWP-RedCap + additionalPRBOffset-r17 ENUMERATED {n2, n3, n4, n6, n8, n9, n10, n12} OPTIONAL -- Cond InitialBWP-RedCapOnly + ]] + } + +-- TAG-PUCCH-CONFIGCOMMON-STOP +-- ASN1STOP +``` + +| PUCCH-ConfigCommon field descriptions | | +|----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| additionalPRBOffset | When intra-slot PUCCH frequency hopping within (e)RedCap-specific initial UL BWP is disabled, each common PUCCH resource is mapped to a single PRB on one side of the UL BWP. This parameter determines an additional PRB offset in the PRB mapping for the PUCCH resource. If the field is not configured, the UE shall assume an additional PRB offset of zero. | +| hoppingId | Cell-specific scrambling ID for group hopping and sequence hopping if enabled, see TS 38.211 [16], clause 6.3.2.2. | +| intra-SlotFH-r17 | In case a separate initial UL BWP is configured for (e)RedCap UEs, the presence of this parameter indicates whether intra-slot PUCCH frequency hopping within the separate initial UL BWP in the common PUCCH resource is enabled for (e)RedCap UEs. If this field is absent, intra-slot PUCCH frequency hopping within (e)RedCap-specific initial UL BWP is enabled. If this field is present, intra-slot PUCCH frequency hopping within (e)RedCap-specific initial UL BWP is disabled and each PUCCH resource is mapped to a single PRB on one side of the UL BWP and this parameter determines whether the PRB index in the PRB mapping is counted in increasing order from the lower edge or in decreasing order from the upper edge of the UL BWP. | +| nrofPRBs | Indicates the number of PRBs used per PUCCH resource for PUCCH format 0 and format 1 in FR2-2, see TS 38.213 [13], clause 9.2.1. | +| p0-nominal | Power control parameter P0 for PUCCH transmissions. Value in dBm. Only even values (step size 2) allowed (see TS 38.213 [13], clause 7.2). | +| pucch-GroupHopping | Configuration of group- and sequence hopping for all the PUCCH formats 0, 1, 3 and 4. Value neither implies neither group or sequence hopping is enabled. Value enable enables group hopping and disables sequence hopping. Value disable disables group hopping and enables sequence hopping (see TS 38.211 [16], clause 6.3.2.2). | +| pucch-ResourceCommon | An entry into a 16-row table where each row configures a set of cell-specific PUCCH resources/parameters. The UE uses those PUCCH resources until it is provided with a dedicated PUCCH-Config (e.g. during initial access) on the initial uplink BWP. Once the network provides a dedicated PUCCH-Config for that bandwidth part the UE applies that one instead of the one provided in this field (see TS 38.213 [13], clause 9.2). | +| pucch-ResourceCommonRedCap | An entry into a 16-row table where each row configures a set of cell-specific PUCCH resources/parameters for (e)RedCap UEs. The UE uses those PUCCH resources until it is provided with a dedicated PUCCH-Config (e.g. during initial access) on the initial uplink BWP. Once the network provides a dedicated PUCCH-Config for that bandwidth part the UE applies that one instead of the one provided in this field (see TS 38.213 [13], clause 9.2). | + +| Conditional Presence | Explanation | +|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| InitialBWP-Only | The field is mandatory present in the PUCCH-ConfigCommon of the initial BWP (BWP#0) in SIB1. It is absent in other BWPs including the (e)RedCap-specific initial uplink BWP, if configured. | +| InitialBWP-RedCap | The field is mandatory present in the PUCCH-ConfigCommon of the (e)RedCap-specific initial BWP. It is optional present, Need R, in the PUCCH-ConfigCommon of the initial BWP configured by initialUplinkBWP . It is absent in other BWPs. | +| InitialBWP-RedCapOnly | The field is optional present, Need S, in the PUCCH-ConfigCommon of the (e)RedCap-specific initial BWP. It is absent in other BWPs. | + +#### — *PUCCH-ConfigurationList* + +The IE *PUCCH-ConfigurationList* is used to configure UE specific PUCCH parameters (per BWP) for two simultaneously constructed HARQ-ACK codebooks. See TS 38.213 [13], clause 9.1. + +#### PUCCH-ConfigurationList information element + +``` +-- ASN1START +-- TAG-PUCCH-CONFIGURATIONLIST-START + +PUCCH-ConfigurationList-r16 ::= SEQUENCE (SIZE (1..2)) OF PUCCH-Config + +-- TAG-PUCCH-CONFIGURATIONLIST-STOP +-- ASN1STOP +``` + +#### – PUCCH-CSI-Resource + +The IE *PUCCH-CSI-Resource* is used to indicate a PUCCH resource to use for reporting on PUCCH. + +#### PUCCH-CSI-Resource information element + +``` +-- ASN1START +-- TAG-PUCCH-CSI-RESOURCE-START + +PUCCH-CSI-Resource ::= SEQUENCE { + uplinkBandwidthPartId BWP-Id, + pucch-Resource PUCCH-ResourceId +} + +-- TAG-PUCCH-CSI-RESOURCE-STOP +-- ASN1STOP +``` + +#### PUCCH-CSI-Resource field descriptions + +##### **pucch-Resource** + +PUCCH resource for the associated uplink BWP. Only PUCCH-Resource of format 2, 3 and 4 is supported. The actual PUCCH-Resource is configured in *PUCCH-Config* and referred to by its ID. When two *PUCCH-Config* are configured within *PUCCH-ConfigurationList*, *PUCCH-ResourceId* in a *PUCCH-CSI-Resource* refers to a PUCCH-Resource in the *PUCCH-Config* used for HARQ-ACK with low priority. + +#### – PUCCH-PathlossReferenceRS-Id + +The IE *PUCCH-PathlossReferenceRS-Id* is an ID for a reference signal (RS) configured as PUCCH pathloss reference (see TS 38.213 [13], clause 7.2). + +#### PUCCH-PathlossReferenceRS-Id information element + +``` +-- ASN1START +-- TAG-PUCCH-PATHLOSSREFERENCERS-ID-START + +PUCCH-PathlossReferenceRS-Id ::= INTEGER (0..maxNrofPUCCH-PathlossReferenceRSs-1) +``` + +``` + +PUCCH-PathlossReferenceRS-Id-v1610 ::= INTEGER (maxNrofPUCCH-PathlossReferenceRSs..maxNrofPUCCH-PathlossReferenceRSs-1-r16) +PUCCH-PathlossReferenceRS-Id-r17 ::= INTEGER (0..maxNrofPUCCH-PathlossReferenceRSs-1-r17) + +-- TAG-PUCCH-PATHLOSSREFERENCEID-STOP +-- ASN1STOP + +``` + +#### — *PUCCH-PowerControl* + +The IE *PUCCH-PowerControl* is used to configure UE-specific parameters for the power control of PUCCH. + +#### *PUCCH-PowerControl* information element + +``` + +-- ASN1START +-- TAG-PUCCH-POWERCONTROL-START +PUCCH-PowerControl ::= SEQUENCE { + deltaF-PUCCH-f0 INTEGER (-16..15) OPTIONAL, -- Need R + deltaF-PUCCH-f1 INTEGER (-16..15) OPTIONAL, -- Need R + deltaF-PUCCH-f2 INTEGER (-16..15) OPTIONAL, -- Need R + deltaF-PUCCH-f3 INTEGER (-16..15) OPTIONAL, -- Need R + deltaF-PUCCH-f4 INTEGER (-16..15) OPTIONAL, -- Need R + p0-Set SEQUENCE (SIZE (1..maxNrofPUCCH-P0-PerSet)) OF P0-PUCCH OPTIONAL, -- Need M + pathlossReferenceRSs SEQUENCE (SIZE (1..maxNrofPUCCH-PathlossReferenceRSs)) OF PUCCH-PathlossReferenceRS + OPTIONAL, -- Need M + twoPUCCH-PC-AdjustmentStates + ENUMERATED {twoStates} OPTIONAL, -- Need S + ... + [[ + pathlossReferenceRSs-v1610 SetupRelease { PathlossReferenceRSs-v1610 } OPTIONAL -- Need M + ]] +} + +P0-PUCCH ::= SEQUENCE { + p0-PUCCH-Id P0-PUCCH-Id, + p0-PUCCH-Value INTEGER (-16..15) +} + +P0-PUCCH-Id ::= INTEGER (1..8) + +PathlossReferenceRSs-v1610 ::= SEQUENCE (SIZE (1..maxNrofPUCCH-PathlossReferenceRSsDiff-r16)) OF PUCCH-PathlossReferenceRS-r16 + +PUCCH-PathlossReferenceRS ::= SEQUENCE { + pucch-PathlossReferenceRS-Id PUCCH-PathlossReferenceRS-Id, + referenceSignal CHOICE { + ssb-Index SSB-Index, + csi-RS-Index NZP-CSI-RS-ResourceId + } +} + +PUCCH-PathlossReferenceRS-r16 ::= SEQUENCE { + +``` + +``` + + pucch-PathlossReferenceRS-Id-r16 PUCCH-PathlossReferenceRS-Id-v1610, + referenceSignal-r16 CHOICE { + ssb-Index-r16 SSB-Index, + csi-RS-Index-r16 NZP-CSI-RS-ResourceId + } +} + +PUCCH-PowerControlSetInfo-r17 ::= SEQUENCE { + pucch-PowerControlSetInfoId-r17 PUCCH-PowerControlSetInfoId-r17, + p0-PUCCH-Id-r17 P0-PUCCH-Id, + pucch-ClosedLoopIndex-r17 ENUMERATED { i0, i1 }, + pucch-PathlossReferenceRS-Id-r17 PUCCH-PathlossReferenceRS-Id-r17 +} + +PUCCH-PowerControlSetInfoId-r17 ::= INTEGER (1.. maxNrofPowerControlSetInfos-r17) + +-- TAG-PUCCH-POWERCONTROL-STOP +-- ASN1STOP + +``` + +#### | P0-PUCCH field descriptions | |------------------------------------------------------------------------| | p0-PUCCH-Value
P0 value for PUCCH with 1dB step size. | + +| PUCCH-PowerControl field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| deltaF-PUCCH-f0
deltaF for PUCCH format 0 with 1dB step size (see TS 38.213 [13], clause 7.2). | +| deltaF-PUCCH-f1
deltaF for PUCCH format 1 with 1dB step size (see TS 38.213 [13], clause 7.2). | +| deltaF-PUCCH-f2
deltaF for PUCCH format 2 with 1dB step size (see TS 38.213 [13], clause 7.2). | +| deltaF-PUCCH-f3
deltaF for PUCCH format 3 with 1dB step size (see TS 38.213 [13], clause 7.2). | +| deltaF-PUCCH-f4
deltaF for PUCCH format 4 with 1dB step size (see TS 38.213 [13], clause 7.2). | +| p0-Set
A set with dedicated P0 values for PUCCH, i.e., {P01, P02,... } (see TS 38.213 [13], clause 7.2). | +| pathlossReferenceRSs, pathlossReferenceRSs-v1610
A set of Reference Signals (e.g. a CSI-RS config or a SS block) to be used for PUCCH pathloss estimation. Up to maxNrofPUCCH-PathlossReference-RSs may be configured. If the field is not configured, the UE uses the SSB as reference signal (see TS 38.213 [13], clause 7.2). The set includes Reference Signals indicated in pathlossReferenceRSs (without suffix) and in pathlossReferenceRSs-v1610 . The UE maintains pathlossReferenceRSs and pathlossReferenceRSs-v1610 separately: Receiving pathlossReferenceRSs-v1610 set to release releases only the entries that were configured by pathlossReferenceRSs-v1610 , and receiving pathlossReferenceRSs-v1610 set to setup replaces only the entries that were configured by pathlossReferenceRSs-v1610 with the newly signalled entries. | +| twoPUCCH-PC-AdjustmentStates
Number of PUCCH power control adjustment states maintained by the UE (i.e., g(i) ). If the field is present ( n2 ) the UE maintains two power control states (i.e., g(i,0) and g(i,1) ). If the field is absent, it maintains one power control state (i.e., g(i,0) ) (see TS 38.213 [13], clause 7.2). | + +#### – PUCCH-SpatialRelationInfo + +The IE *PUCCH-SpatialRelationInfo* is used to configure the spatial setting for PUCCH transmission and the parameters for PUCCH power control, see TS 38.213, [13], clause 9.2.2. + +#### PUCCH-SpatialRelationInfo information element + +``` +-- ASN1START +-- TAG-PUCCH-SPATIALRELATIONINFO-START + +PUCCH-SpatialRelationInfo ::= + SEQUENCE { + pucch-SpatialRelationInfoId + servingCellId + referenceSignal + ssb-Index + csi-RS-Index + srs + , + pucch-PathlossReferenceRS-Id + p0-PUCCH-Id + closedLoopIndex + } + + SEQUENCE { + PUCCH-SpatialRelationInfoId, + ServCellIndex + CHOICE { + SSB-Index, + NZP-CSI-RS-ResourceId, + PUCCH-SRS + }, + PUCCH-PathlossReferenceRS-Id, + P0-PUCCH-Id, + ENUMERATED { i0, i1 } + } +} + +OPTIONAL, -- Need S +``` + +``` + +PUCCH-SpatialRelationInfoExt-r16 ::= SEQUENCE { + pucch-SpatialRelationInfoId-v1610 PUCCH-SpatialRelationInfoId-v1610 OPTIONAL, -- Need S + pucch-PathlossReferenceRS-Id-v1610 PUCCH-PathlossReferenceRS-Id-v1610 OPTIONAL, --Need R + ... +} + +PUCCH-SRS ::= SEQUENCE { + resource SRS-ResourceId, + uplinkBWP BWP-Id +} + +-- TAG-PUCCH-SPATIALRELATIONINFO-STOP +-- ASN1STOP + +``` + +#### ***PUCCH-SpatialRelationInfo* field descriptions** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| pucch-PathLossReferenceRS-Id | +| When pucch-PathLossReferenceRS-Id-v1610 is configured, the UE shall ignore pucch-PathLossReferenceRS-Id (without suffix). | +| pucch-SpatialRelationInfoId | +| When pucch-SpatialRelationInfoId-v1610 is configured, the UE shall ignore pucch-SpatialRelationInfoId (without suffix). If pucch-SpatialRelationInfoId-v1610 is absent, the UE shall use the pucch-SpatialRelationInfoId (without suffix). | +| servingCellId | +| If the field is absent, the UE applies the ServCellId of the serving cell in which this PUCCH-SpatialRelationInfo is configured | + +##### – ***PUCCH-SpatialRelationInfo-Id*** + +The IE *PUCCH-SpatialRelationInfo-Id* is used to identify a *PUCCH-SpatialRelationInfo* + +#### ***PUCCH-SpatialRelationInfo-Id* information element** + +``` + +-- ASN1START +-- TAG-PUCCH-SPATIALRELATIONINFO-START + +PUCCH-SpatialRelationInfoId ::= INTEGER (1..maxNrofSpatialRelationInfos) +PUCCH-SpatialRelationInfoId-r16 ::= INTEGER (1..maxNrofSpatialRelationInfos-r16) +PUCCH-SpatialRelationInfoId-v1610 ::= INTEGER (maxNrofSpatialRelationInfos-plus-1..maxNrofSpatialRelationInfos-r16) + +-- TAG-PUCCH-SPATIALRELATIONINFO-STOP +-- ASN1STOP + +``` + +### PUCCH-TPC-CommandConfig + +The IE *PUCCH-TPC-CommandConfig* is used to configure the UE for extracting TPC commands for PUCCH from a group-TPC messages on DCI. + +#### PUCCH-TPC-CommandConfig information element + +``` +-- ASN1START +-- TAG-PUCCH-TPC-COMMANDCONFIG-START + +PUCCH-TPC-CommandConfig ::= SEQUENCE { + tpc-IndexPCell INTEGER (1..15) OPTIONAL, -- Cond PDCCH-OfSpcell + tpc-IndexPUCCH-SCell INTEGER (1..15) OPTIONAL, -- Cond PDCCH-ofSpCellOrPUCCH-SCell + ... + [[ + tpc-IndexPUCCH-sSCell-r17 INTEGER (1..15) OPTIONAL, -- Need R + tpc-IndexPUCCH-sSCellSecondaryPUCCHgroup-r17 INTEGER (1..15) OPTIONAL -- Cond twoPUCCHgroup + ]] +} + +-- TAG-PUCCH-TPC-COMMANDCONFIG-STOP +-- ASN1STOP +``` + +#### PUCCH-TPC-CommandConfig field descriptions + +| | | +|-------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| tpc-IndexPCell | An index determining the position of the first bit of TPC command (applicable to the SpCell) inside the DCI format 2-2 payload. | +| tpc-IndexPUCCH-SCell | An index determining the position of the first bit of TPC command (applicable to the PUCCH SCell) inside the DCI format 2-2 payload. | +| tpc-IndexPUCCH-sSCell, tpc-IndexPUCCH-sSCellSecondaryPUCCHgroup | An index determining the position of the first bit of TPC command (applicable to the alternative PUCCH cell for PUCCH cell switching) inside the DCI format 2-2 payload, for the primary PUCCH group and the secondary PUCCH group respectively. | + +| Conditional Presence | Explanation | +|------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PDCCH-OfSpcell | The field is mandatory present if the PUCCH-TPC-CommandConfig is provided in the PDCCH-Config for the SpCell. Otherwise, the field is absent, Need R. | +| PDCCH-ofSpCellOrPUCCH-SCell | The field is mandatory present if the PUCCH-TPC-CommandConfig is provided in the PDCCH-Config for the PUCCH-SCell. The field is optionally present, need R, if the UE is configured with a PUCCH SCell in this cell group and if the PUCCH-TPC-CommandConfig is provided in the PDCCH-Config for the SpCell. Otherwise, the field is absent, Need R. | +| twoPUCCHgroup | This field is optionally present, Need R, if secondary PUCCH group is configured. It is absent otherwise. | + +### PUSCH-Config + +The IE *PUSCH-Config* is used to configure the UE specific PUSCH parameters applicable to a particular BWP. + +#### PUSCH-Config information element + +``` + +-- ASN1START +-- TAG-PUSCH-CONFIG-START + +PUSCH-Config ::= SEQUENCE { + dataScramblingIdentityPUSCH INTEGER (0..1023) OPTIONAL, -- Need S + txConfig ENUMERATED {codebook, nonCodebook} OPTIONAL, -- Need S + dmrs-UplinkForPUSCH-MappingTypeA SetupRelease { DMRS-UplinkConfig } OPTIONAL, -- Need M + dmrs-UplinkForPUSCH-MappingTypeB SetupRelease { DMRS-UplinkConfig } OPTIONAL, -- Need M + pusCH-PowerControl PUSCH-PowerControl OPTIONAL, -- Need M + frequencyHopping ENUMERATED {intraSlot, interSlot} OPTIONAL, -- Need S + frequencyHoppingOffsetLists SEQUENCE (SIZE (1..4)) OF INTEGER (1.. maxNrofPhysicalResourceBlocks-1) + OPTIONAL, -- Need M + resourceAllocation ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch}, + OPTIONAL, -- Need M + pusCH-TimeDomainAllocationList SetupRelease { PUSCH-TimeDomainResourceAllocationList } OPTIONAL, -- Need M + pusCH-AggregationFactor ENUMERATED { n2, n4, n8 } OPTIONAL, -- Need S + mcs-Table ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need S + mcs-TableTransformPrecoder ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need S + transformPrecoder ENUMERATED {enabled, disabled} OPTIONAL, -- Need S + codebookSubset ENUMERATED {fullyAndPartialAndNonCoherent, partialAndNonCoherent,nonCoherent} + OPTIONAL, -- Cond codebookBased + maxRank INTEGER (1..4) OPTIONAL, -- Cond codebookBased + rbg-Size ENUMERATED { config2} OPTIONAL, -- Need S + uci-OnPUSCH SetupRelease { UCI-OnPUSCH} OPTIONAL, -- Need M + tp-pi2BPSK ENUMERATED {enabled} OPTIONAL, -- Need S + ... + [[ + minimumSchedulingOffsetK2-r16 SetupRelease { MinSchedulingOffsetK2-Values-r16 } OPTIONAL, -- Need M + ul-AccessConfigListDCI-0-1-r16 SetupRelease { UL-AccessConfigListDCI-0-1-r16 } OPTIONAL, -- Need M + -- Start of the parameters for DCI format 0_2 introduced in V16.1.0 + harq-ProcessNumberSizeDCI-0-2-r16 INTEGER (0..4) OPTIONAL, -- Need R + dmrs-SequenceInitializationDCI-0-2-r16 ENUMERATED {enabled} OPTIONAL, -- Need S + numberOfBitsForRV-DCI-0-2-r16 INTEGER (0..2) OPTIONAL, -- Need R + antennaPortsFieldPresenceDCI-0-2-r16 ENUMERATED {enabled} OPTIONAL, -- Need S + dmrs-UplinkForPUSCH-MappingTypeA-DCI-0-2-r16 SetupRelease { DMRS-UplinkConfig } OPTIONAL, -- Need M + dmrs-UplinkForPUSCH-MappingTypeB-DCI-0-2-r16 SetupRelease { DMRS-UplinkConfig } OPTIONAL, -- Need M + frequencyHoppingDCI-0-2-r16 CHOICE { + pusCH-RepTypeA ENUMERATED {intraSlot, interSlot}, + pusCH-RepTypeB ENUMERATED {interRepetition, interSlot} + } + OPTIONAL, -- Need S + frequencyHoppingOffsetListsDCI-0-2-r16 SetupRelease { FrequencyHoppingOffsetListsDCI-0-2-r16} OPTIONAL, -- Need M + codebookSubsetDCI-0-2-r16 ENUMERATED {fullyAndPartialAndNonCoherent, partialAndNonCoherent,nonCoherent} + OPTIONAL, -- Cond codebookBased + invalidSymbolPatternIndicatorDCI-0-2-r16 ENUMERATED {enabled} OPTIONAL, -- Need S + maxRankDCI-0-2-r16 INTEGER (1..4) OPTIONAL, -- Cond codebookBased + +``` + +``` + +mcs-TableDCI-0-2-r16 ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need S +mcs-TableTransformPrecoderDCI-0-2-r16 ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need S +priorityIndicatorDCI-0-2-r16 ENUMERATED {enabled} OPTIONAL, -- Need S +pusch-RepTypeIndicatorDCI-0-2-r16 ENUMERATED { pusch-RepTypeA, pusch-RepTypeB} OPTIONAL, -- Need R +resourceAllocationDCI-0-2-r16 ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch} + OPTIONAL, -- Need M +resourceAllocationType1GranularityDCI-0-2-r16 ENUMERATED { n2,n4,n8,n16 } OPTIONAL, -- Need S +uci-OnPUSCH-ListDCI-0-2-r16 SetupRelease { UCI-OnPUSCH-ListDCI-0-2-r16} OPTIONAL, -- Need M +pusch-TimeDomainAllocationListDCI-0-2-r16 SetupRelease { PUSCH-TimeDomainResourceAllocationList-r16 } + OPTIONAL, -- Need M + +-- End of the parameters for DCI format 0_2 introduced in V16.1.0 +-- Start of the parameters for DCI format 0_1 introduced in V16.1.0 +pusch-TimeDomainAllocationListDCI-0-1-r16 SetupRelease { PUSCH-TimeDomainResourceAllocationList-r16 } + OPTIONAL, -- Need M +invalidSymbolPatternIndicatorDCI-0-1-r16 ENUMERATED {enabled} OPTIONAL, -- Need S +priorityIndicatorDCI-0-1-r16 ENUMERATED {enabled} OPTIONAL, -- Need S +pusch-RepTypeIndicatorDCI-0-1-r16 ENUMERATED { pusch-RepTypeA, pusch-RepTypeB} OPTIONAL, -- Need R +frequencyHoppingDCI-0-1-r16 ENUMERATED {interRepetition, interSlot} OPTIONAL, -- Cond RepTypeB +uci-OnPUSCH-ListDCI-0-1-r16 SetupRelease { UCI-OnPUSCH-ListDCI-0-1-r16 } OPTIONAL, -- Need M +-- End of the parameters for DCI format 0_1 introduced in V16.1.0 +invalidSymbolPattern-r16 InvalidSymbolPattern-r16 OPTIONAL, -- Need S +pusch-PowerControl-v1610 SetupRelease {PUSCH-PowerControl-v1610} OPTIONAL, -- Need M +ul-FullPowerTransmission-r16 ENUMERATED {fullpower, fullpowerModel, fullpowerMode2} OPTIONAL, -- Need R +pusch-TimeDomainAllocationListForMultiPUSCH-r16 SetupRelease { PUSCH-TimeDomainResourceAllocationList-r16 } + OPTIONAL, -- Need M +numberOfInvalidSymbolsForDL-UL-Switching-r16 INTEGER (1..4) OPTIONAL, -- Cond RepTypeB2 +]], +[[ +ul-AccessConfigListDCI-0-2-r17 SetupRelease { UL-AccessConfigListDCI-0-2-r17 } OPTIONAL, -- Need M +betaOffsetsCrossPri0-r17 SetupRelease { BetaOffsetsCrossPriSel-r17 } OPTIONAL, -- Need M +betaOffsetsCrossPri1-r17 SetupRelease { BetaOffsetsCrossPriSel-r17 } OPTIONAL, -- Need M +betaOffsetsCrossPri0DCI-0-2-r17 SetupRelease { BetaOffsetsCrossPriSelDCI-0-2-r17 } OPTIONAL, -- Need M +betaOffsetsCrossPri1DCI-0-2-r17 SetupRelease { BetaOffsetsCrossPriSelDCI-0-2-r17 } OPTIONAL, -- Need M +mappingPattern-r17 ENUMERATED {cyclicMapping, sequentialMapping} OPTIONAL, -- Cond SRsets +secondTPCFieldDCI-0-1-r17 ENUMERATED {enabled} OPTIONAL, -- Need R +secondTPCFieldDCI-0-2-r17 ENUMERATED {enabled} OPTIONAL, -- Need R +sequenceOffsetForRV-r17 INTEGER (0..3) OPTIONAL, -- Need R +ul-AccessConfigListDCI-0-1-r17 SetupRelease { UL-AccessConfigListDCI-0-1-r17 } OPTIONAL, -- Need M +minimumSchedulingOffsetK2-r17 SetupRelease { MinSchedulingOffsetK2-Values-r17 } OPTIONAL, -- Need M +availableSlotCounting-r17 ENUMERATED { enabled } OPTIONAL, -- Need S +dmrs-BundlingPUSCH-Config-r17 SetupRelease { DMRS-BundlingPUSCH-Config-r17 } OPTIONAL, -- Need M +harq-ProcessNumberSizeDCI-0-2-v1700 INTEGER (5) OPTIONAL, -- Need R +harq-ProcessNumberSizeDCI-0-1-r17 INTEGER (5) OPTIONAL, -- Need R +mpe-ResourcePoolToAddModList-r17 SEQUENCE (SIZE(1..maxMPE-Resources-r17)) OF MPE-Resource-r17 OPTIONAL, -- Need N +mpe-ResourcePoolToReleaseList-r17 SEQUENCE (SIZE(1..maxMPE-Resources-r17)) OF MPE-ResourceId-r17 OPTIONAL, -- Need N +]], +[[ +maxRank-n8-r18 INTEGER (5..8) OPTIONAL, -- Cond codebookBased +sTx-2Panel-r18 ENUMERATED {enabled} OPTIONAL, -- Need R +multipanelScheme-r18 CHOICE { + sdm-r18 SetupRelease { SDM-Scheme-r18 }, + +``` + +``` + + sfn-r18 SetupRelease { SFN-Scheme-r18 } + } + codebookTypeUL-r18 SetupRelease { CodebookTypeUL-r18 } OPTIONAL, -- Cond SRSsets + applyIndicatedTCI-State-r18 ENUMERATED {first, second} OPTIONAL, -- Need M + dynamicTransformPrecoderFieldPresenceDCI-0-1-r18 ENUMERATED {enabled} OPTIONAL, -- Need R + dynamicTransformPrecoderFieldPresenceDCI-0-2-r18 ENUMERATED {enabled} OPTIONAL, -- Need R + pusch-ConfigDCI-0-3-r18 SetupRelease { PUSCH-ConfigDCI-0-3-r18 } OPTIONAL, -- Need M + ]] +} + +UCI-OnPUSCH ::= SEQUENCE { + betaOffsets CHOICE { + dynamic SEQUENCE (SIZE (4)) OF BetaOffsets, + semiStatic BetaOffsets + } OPTIONAL, -- Need M + scaling ENUMERATED { f0p5, f0p65, f0p8, f1 } +} + +MinSchedulingOffsetK2-Values-r16 ::= SEQUENCE (SIZE (1..maxNrOfMinSchedulingOffsetValues-r16)) OF INTEGER (0..maxK2-SchedulingOffset-r16) +MinSchedulingOffsetK2-Values-r17 ::= SEQUENCE (SIZE (1..maxNrOfMinSchedulingOffsetValues-r16)) OF INTEGER (0..maxK2-SchedulingOffset-r17) + +UCI-OnPUSCH-DCI-0-2-r16 ::= SEQUENCE { + betaOffsetsDCI-0-2-r16 CHOICE { + dynamicDCI-0-2-r16 CHOICE { + oneBit-r16 SEQUENCE (SIZE (2)) OF BetaOffsets, + twoBits-r16 SEQUENCE (SIZE (4)) OF BetaOffsets + }, + semiStaticDCI-0-2-r16 BetaOffsets + } OPTIONAL, -- Need M + scalingDCI-0-2-r16 ENUMERATED { f0p5, f0p65, f0p8, f1 } +} + +FrequencyHoppingOffsetListsDCI-0-2-r16 ::= SEQUENCE (SIZE (1..4)) OF INTEGER (1.. maxNrOfPhysicalResourceBlocks-1) +UCI-OnPUSCH-ListDCI-0-2-r16 ::= SEQUENCE (SIZE (1..2)) OF UCI-OnPUSCH-DCI-0-2-r16 +UCI-OnPUSCH-ListDCI-0-1-r16 ::= SEQUENCE (SIZE (1..2)) OF UCI-OnPUSCH +UL-AccessConfigListDCI-0-1-r16 ::= SEQUENCE (SIZE (1..64)) OF INTEGER (0..63) +UL-AccessConfigListDCI-0-1-r17 ::= SEQUENCE (SIZE (1..3)) OF INTEGER (0..2) +UL-AccessConfigListDCI-0-2-r17 ::= SEQUENCE (SIZE (1..64)) OF INTEGER (0..63) + +BetaOffsetsCrossPriSel-r17 ::= CHOICE { + dynamic-r17 SEQUENCE (SIZE (4)) OF BetaOffsetsCrossPri-r17, + semiStatic-r17 BetaOffsetsCrossPri-r17 +} + +BetaOffsetsCrossPriSelDCI-0-2-r17 ::= CHOICE { + +``` + +``` + + dynamicDCI-0-2-r17 CHOICE { + oneBit-r17 SEQUENCE (SIZE (2)) OF BetaOffsetsCrossPri-r17, + twoBits-r17 SEQUENCE (SIZE (4)) OF BetaOffsetsCrossPri-r17 + }, + semiStaticDCI-0-2-r17 BetaOffsetsCrossPri-r17 +} + +MPE-Resource-r17 ::= SEQUENCE { + mpe-ResourceId-r17 MPE-ResourceId-r17, + cell-r17 ServCellIndex OPTIONAL, -- Need R + additionalPCI-r17 AdditionalPCIIndex-r17 OPTIONAL, -- Need R + mpe-ReferenceSignal-r17 CHOICE { + csi-RS-Resource-r17 NZP-CSI-RS-ResourceId, + ssb-Resource-r17 SSB-Index + } +} + +MPE-ResourceId-r17 ::= INTEGER (1..maxMPE-Resources-r17) + +SDM-Scheme-r18 ::= SEQUENCE { + maxRankSDM-r18 INTEGER (1..2) OPTIONAL, -- Need R + maxRankSDM-DCI-0-2-r18 INTEGER (1..2) OPTIONAL -- Need R +} + +SFN-Scheme-r18 ::= SEQUENCE { + maxRankSFN-r18 INTEGER (1..2) OPTIONAL, -- Need R + maxRankSFN-DCI-0-2-r18 INTEGER (1..2) OPTIONAL -- Need R +} + +CodebookTypeUL-r18 ::= CHOICE { + codebook1-r18 ENUMERATED {ng1n4n1, ng1n2n2}, + codebook2-r18 ENUMERATED {ng2}, + codebook3-r18 ENUMERATED {ng4}, + codebook4-r18 ENUMERATED {ng8} +} + +PUSCH-ConfigDCI-0-3-r18 ::= SEQUENCE { + resourceAllocationDCI-0-3-r18 ENUMERATED {resourceAllocationType0, resourceAllocationType1, dynamicSwitch} + OPTIONAL, -- Need M + rbg-SizeDCI-0-3-r18 ENUMERATED {config2, config3} OPTIONAL, -- Need S + resourceAllocationType1GranularityDCI-0-3-r18 ENUMERATED {n2,n4,n8,n16} OPTIONAL, -- Need S + numberOfBitsForRV-DCI-0-3-r18 INTEGER (0..2) OPTIONAL, -- Need R + harq-ProcessNumberSizeDCI-0-3-r18 INTEGER (0..5) OPTIONAL, -- Need R + uci-OnPUSCH-ListDCI-0-3-r18 SetupRelease { UCI-OnPUSCH-ListDCI-0-1-r16 } OPTIONAL -- Need M +} + +-- TAG-PUSCH-CONFIG-STOP +-- ASN1STOP + +``` + +| PUSCH-Config field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| antennaPortsFieldPresenceDCI-0-2
Configure the presence of "Antenna ports" field in DCI format 0_2. When the field is configured, then the "Antenna ports" field is present in DCI format 0_2. Otherwise, the field size is set to 0 for DCI format 0_2 (See TS 38.212 [17], clause 7.3.1.1.3). If neither dmrs-UplinkForPUSCH-MappingTypeA-DCI-0-2 nor dmrs-UplinkForPUSCH-MappingTypeB-DCI-0-2 is configured, this field is absent. | +| applyIndicatedTCI-State
This field indicates, for a PUSCH transmission, if UE applies the first or the second "indicated" UL only TCI or joint TCI as specified in TS 38.214 [19], clause 6.2.1. | +| availableSlotCounting
Indicate whether PUSCH repetitions counted on the basis of available slots is enabled. If the field is absent, PUSCH repetitions counted on the basis of available slots is disabled. | +| betaOffsetsCrossPrio0, betaOffsetsCrossPrio1, betaOffsetsCrossPrio0DCI-0-2, betaOffsetsCrossPrio1DCI-0-2
Selection between and configuration of dynamic and semi-static beta-offset for multiplexing HARQ-ACK on dynamically scheduled PUSCH with different priorities, see TS 38.213 [13], clause 9.3.
The field betaOffsetsCrossPrio0 indicates multiplexing low priority (LP) HARQ-ACK on dynamically scheduled high priority (HP) PUSCH.
The field betaOffsetsCrossPrio1 indicates multiplexing HP HARQ-ACK on dynamically scheduled LP PUSCH.
The field betaOffsetsCrossPrio0DCI-0-2 indicates multiplexing LP HARQ-ACK on dynamically scheduled HP PUSCH by DCI format 0_2.
The field betaOffsetsCrossPrio1DCI-0-2 indicates multiplexing HP HARQ-ACK on dynamically scheduled LP PUSCH by DCI format 0_2. | +| codebookSubset, codebookSubsetDCI-0-2
Subset of PMIs addressed by TPMI, where PMIs are those supported by UEs with maximum coherence capabilities (see TS 38.214 [19], clause 6.1.1.1). The field codebookSubset applies to DCI format 0_1 and the field codebookSubsetDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.1.1). | +| codebookTypeUL
Configures codebooktype for PUSCH, see Reference XXX. | +| dataScramblingIdentityPUSCH
Identifier used to initialise data scrambling ( c_init ) for PUSCH. If the field is absent, the UE applies the physical cell ID. (see TS 38.211 [16], clause 6.3.1.1). | +| dmrs-BundlingPUSCH-Config
Configure the parameters for DMRS bundling for PUSCH (see TS 38.214 [19], clause 6.1.7). In this release, this is not applicable to FR2-2. | +| dmrs-SequenceInitializationDCI-0-2
Configure whether the field "DMRS Sequence Initialization" is present or not in DCI format 0_2. If the field is absent, then 0 bit for the field "DMRS Sequence Initialization" in DCI format 0_2. If the field is present, then the number of bits is determined in the same way as DCI format 0_1 (see TS 38.212 [17], clause 7.3.1). | +| dmrs-UplinkForPUSCH-MappingTypeA, dmrs-UplinkForPUSCH-MappingTypeA-DCI-0-2
DMRS configuration for PUSCH transmissions using PUSCH mapping type A (chosen dynamically via PUSCH-TimeDomainResourceAllocation ). Only the fields dmrs-Type , dmrs-AdditionalPosition and maxLength may be set differently for mapping type A and B. The field dmrs-UplinkForPUSCH-MappingTypeA applies to DCI format 0_1 and the field dmrs-UplinkForPUSCH-MappingTypeA-DCI-0-2 applies to DCI format 0_2 (see TS 38.212 [17], clause 7.3.1). | +| dmrs-UplinkForPUSCH-MappingTypeB, dmrs-UplinkForPUSCH-MappingTypeB-DCI-0-2
DMRS configuration for PUSCH transmissions using PUSCH mapping type B (chosen dynamically via PUSCH-TimeDomainResourceAllocation ). Only the fields dmrs-Type , dmrs-AdditionalPosition and maxLength may be set differently for mapping type A and B. The field dmrs-UplinkForPUSCH-MappingTypeB applies to DCI format 0_1 and the field dmrs-UplinkForPUSCH-MappingTypeB-DCI-0-2 applies to DCI format 0_2 (see TS 38.212 [17], clause 7.3.1). | +| dynamicTransformPrecoderFieldPresenceDCI-0-1
Configure the presence of "Dynamic Transform Precoder" field in DCI format 0_1. When the field is configured, then the "Dynamic Transform Precoder" field is present in DCI format 0_1. Otherwise, the field size is set to 0 for DCI format 0_1 (See TS 38.212 [17]). | +| dynamicTransformPrecoderFieldPresenceDCI-0-2
Configure the presence of "Dynamic Transform Precoder" field in DCI format 0_2. When the field is configured, then the "Dynamic Transform Precoder" field is present in DCI format 0_2. Otherwise, the field size is set to 0 for DCI format 0_2 (See TS 38.212 [17]). | +| frequencyHopping | + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| The value intraSlot enables 'Intra-slot frequency hopping' and the value interSlot enables 'Inter-slot frequency hopping'. If the field is absent, frequency hopping is not configured for 'pusch-RepTypeA' (see TS 38.214 [19], clause 6.3). The field frequencyHopping applies to DCI format 0_0 and 0_1 for 'pusch-RepTypeA'. | +| frequencyHoppingDCI-0-1
Indicates the frequency hopping scheme for DCI format 0_1 when pusch-RepTypeIndicatorDCI-0-1 is set to 'pusch-RepTypeB'. The value interRepetition enables 'Inter-repetition frequency hopping', and the value interSlot enables 'Inter-slot frequency hopping'. If the field is absent, frequency hopping is not configured for DCI format 0_1 for 'pusch-RepTypeB' (see TS 38.214 [19], clause 6.1). | +| frequencyHoppingDCI-0-2
Indicate the frequency hopping scheme for DCI format 0_2. The value intraSlot enables 'intra-slot frequency hopping', and the value interRepetition enables 'Inter-repetition frequency hopping', and the value interSlot enables 'Inter-slot frequency hopping'. When pusch-RepTypeIndicatorDCI-0-2 is not set to 'pusch-RepTypeB', the frequency hopping scheme can be chosen between 'intra-slot frequency hopping' and 'inter-slot frequency hopping' if enabled. When pusch-RepTypeIndicatorDCI-0-2 is set to 'pusch-RepTypeB', the frequency hopping scheme can be chosen between 'inter-repetition frequency hopping' and 'inter-slot frequency hopping' if enabled. If the field is absent, frequency hopping is not configured for DCI format 0_2 (see TS 38.214 [19], clause 6.3). | +| frequencyHoppingOffsetLists, frequencyHoppingOffsetListsDCI-0-2
Set of frequency hopping offsets used when frequency hopping is enabled for granted transmission (not msg3) and type 2 configured grant activation (see TS 38.214 [19], clause 6.3). The field frequencyHoppingOffsetLists applies to DCI format 0_0 and DCI format 0_1 and the field frequencyHoppingOffsetListsDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.3). | +| harq-ProcessNumberSizeDCI-0-2
Configure the number of bits for the field "HARQ process number" in DCI format 0_2 (see TS 38.212 [17], clause 7.3.1). | +| invalidSymbolPattern
Indicates one pattern for invalid symbols for PUSCH transmission repetition type B applicable to both DCI format 0_1 and 0_2. If InvalidSymbolPattern is not configured, semi-static flexible symbols are used for PUSCH. Segmentation occurs only around semi-static DL symbols (see TS 38.214 [19] clause 6.1). | +| invalidSymbolPatternIndicatorDCI-0-1, invalidSymbolPatternIndicatorDCI-0-2
Indicates the presence of an additional bit in the DCI format 0_1/0_2. If invalidSymbolPattern is absent, then both invalidSymbolPatternIndicatorDCI-0-1 and invalidSymbolPatternIndicatorDCI-0-2 are absent. The field invalidSymbolPatternIndicatorDCI-0-1 applies to the DCI format 0_1 and the field invalidSymbolPatternIndicatorDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19] clause 6.1). If the field is absent, the UE behaviour is specified in TS 38.214 [19], clause 6.1.2.1. | +| mappingPattern
Indicates whether the UE should follow Cyclical mapping pattern or Sequential mapping pattern for when two SRS resource sets are configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 with usage 'codebook' or 'noncodebook' for PUSCH transmission and the PUSCH transmission occasions are associated with both SRS resource sets. | +| maxRank, maxRankDCI-0-2, maxRank-n8
Subset of PMIs addressed by TRIs from 1 to ULmaxRank (see TS 38.214 [19], clause 6.1.1.1). The fields maxRank and maxRank-n8 apply to DCI format 0_1, and the field maxRankDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.1.1). | +| mcs-Table, mcs-TableFormat0-2
Indicates which MCS table the UE shall use for PUSCH without transform precoder (see TS 38.214 [19], clause 6.1.4.1). If the field is absent the UE applies the value 64QAM. The field mcs-Table applies to DCI format 0_0 and DCI format 0_1 and the field mcs-TableDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.4.1). | +| mcs-TableTransformPrecoder, mcs-TableTransformPrecoderDCI-0-2
Indicates which MCS table the UE shall use for PUSCH with transform precoding (see TS 38.214 [19], clause 6.1.4.1). If the field is absent the UE applies the value 64QAM. The field mcs-TableTransformPrecoder applies to DCI format 0_0 and DCI format 0_1 and the field mcs-TableTransformPrecoderDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.4.1). | +| minimumSchedulingOffsetK2
List of minimum K2 values. Minimum K2 parameter denotes minimum applicable value(s) for the Time domain resource assignment table for PUSCH (see TS 38.214 [19], clause 6.1.2.1). | +| mpe-ResourcePoolToAddModList | + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| List of SSB/CSI-RS resources for P-MPR reporting. Each resource is configured with serving cell index where the resource is configured for the UE. The additionalPCI is configured only if the resource is SSB. For each resource, if neither cell nor additionalPCI is present, the SSB/CSI-RS resource is from the serving cell where the PUSCH-Config is configured. | +| multiPanelScheme
Configures UE with a multiple panel simultaneous uplink transmission SDM or SFN scheme for PUSCH. | +| numberOfBitsForRV-DCI-0-2
Configures the number of bits for "Redundancy version" in the DCI format 0_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.214 [19], clause 6.1.2.1). | +| numberOfInvalidSymbolsForDL-UL-Switching
Indicates the number of symbols after the last semi-static DL symbol that are invalid symbols for PUSCH repetition Type B. If it is absent, no symbol is explicitly defined for DL-to-UL switching (see TS 38.214 [19], clause 6.1). | +| priorityIndicatorDCI-0-1, priorityIndicatorDCI-0-2
Configures the presence of "priority indicator" in DCI format 0_1/0_2. When the field is absent in the IE, then the UE shall apply 0 bit for "Priority indicator" in DCI format 0_1/0_2. The field priorityIndicatorDCI-0-1 applies to DCI format 0_1 and the field priorityIndicatorDCI-0-2 applies to DCI format 0_2 (see TS 38.212 [17] clause 7.3.1 and TS 38.213 [13] clause 9). | +| pusch-AggregationFactor
Number of repetitions for data (see TS 38.214 [19], clause 6.1.2.1). If the field is absent the UE applies the value 1. | +| pusch-PowerControl
Configures power control parameters PUSCH transmission. This field is not configured if unifiedTCI-StateType is configured for the serving cell. | +| pusch-RepTypeIndicatorDCI-0-1, pusch-RepTypeIndicatorDCI-0-2
Indicates whether UE follows the behavior for "PUSCH repetition type A" or the behavior for "PUSCH repetition type B" for the PUSCH scheduled by DCI format 0_1/0_2 and for Type 2 CG associated with the activating DCI format 0_1/0_2. The value pusch-RepTypeA enables the 'PUSCH repetition type A' and the value pusch-RepTypeB enables the 'PUSCH repetition type B'. The field pusch-RepTypeIndicatorDCI-0-1 applies to DCI format 0_1 and the field pusch-RepTypeIndicatorDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.2.1). | +| pusch-TimeDomainAllocationList
List of time domain allocations for timing of UL assignment to UL data (see TS 38.214 [19], table 6.1.2.1.1-1). The field pusch-TimeDomainAllocationList applies to DCI formats 0_0 or DCI format 0_1 when the field pusch-TimeDomainAllocationListDCI-0-1 is not configured (see TS 38.214 [19], table 6.1.2.1.1-1 and table 6.1.2.1.1-1A). The network does not configure the pusch-TimeDomainAllocationList (without suffix) simultaneously with the pusch-TimeDomainAllocationListDCI-0-2-r16 or pusch-TimeDomainAllocationListDCI-0-1-r16 or pusch-TimeDomainAllocationListForMultiPUSCH-r16 . | +| pusch-TimeDomainAllocationListDCI-0-1
Configuration of the time domain resource allocation (TDRA) table for DCI format 0_1 (see TS 38.214 [19], clause 6.1, table 6.1.2.1.1-1A). | +| pusch-TimeDomainAllocationListDCI-0-2
Configuration of the time domain resource allocation (TDRA) table for DCI format 0_2 (see TS 38.214 [19], clause 6.1.2, table 6.1.2.1.1-1B). | +| pusch-TimeDomainAllocationListForMultiPUSCH
Configuration of the time domain resource allocation (TDRA) table for multiple PUSCH (see TS 38.214 [19], clause 6.1.2). The network configures at most 64 rows in this TDRA table in PUSCH-TimeDomainResourceAllocationList-r16 configured by this field. This field is not configured simultaneously with pusch-AggregationFactor . The network does not configure the pusch-TimeDomainAllocationListForMultiPUSCH-r16 simultaneously with the pusch-TimeDomainAllocationListDCI-0-1-r16 . The network does not configure the pusch-TimeDomainAllocationListForMultiPUSCH-r16 simultaneously with the numberOfSlotsTBoMS-r17 . | +| rbg-Size
Selection between configuration 1 and configuration 2 for RBG size for PUSCH. The UE does not apply this field if resourceAllocation is set to resourceAllocationType1 . Otherwise, the UE applies the value config1 when the field is absent (see TS 38.214 [19], clause 6.1.2.2.1). | +| resourceAllocation, resourceAllocationDCI-0-2
Configuration of resource allocation type 0 and resource allocation type 1 for non-fallback DCI (see TS 38.214 [19], clause 6.1.2). The field resourceAllocation applies to DCI format 0_1 and the field resourceAllocationDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.2). | +| resourceAllocationType1GranularityDCI-0-2 | + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Configures the scheduling granularity applicable for both the starting point and length indication for resource allocation type 1 in DCI format 0_2. If this field is absent, the granularity is 1 PRB (see TS 38.214 [19], clause 6.1.2.2.2). | +| secondTPCFieldDCI-0-1, secondTPCFieldDCI-0-2
A second TPC field can be configured via RRC for DCI-0-1 and DCI-0-2. Each TPC field is for each closed-loop index value respectively (i.e., 1st /2nd TPC fields correspond to "closedLoopIndex" value = 0 and 1, | +| sequenceOffsetForRV
Configures the RV offset for the starting RV for the first repetition (first actual repetition in PUSCH repetition Type B) towards the second 'SRS resource set' for PUSCH configured in either srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 with usage 'codebook' or 'noncodebook'. | +| stx2-Panel
Parameter to enable PUSCH+PUSCH multiple panel simultaneous uplink transmission in multi-DCI based mTRP system. When this parameter is configured, two coresetPoolindex values are configured and two SRS resource sets for CB or NCB are configured, the multi-DCI based STxMP PUSCH+PUSCH is configured. | +| tp-pi2BPSK
Enables pi/2-BPSK modulation with transform precoding if the field is present and disables it otherwise. | +| transformPrecoder
The UE specific selection of transformer precoder for PUSCH (see TS 38.214 [19], clause 6.1.3). When the field is absent the UE applies the value of the field msg3-transformPrecoder from rach-ConfigCommon included directly within BWP configuration (i.e., not included in additionalRACH-ConfigList ). | +| txConfig
Whether UE uses codebook based or non-codebook based transmission (see TS 38.214 [19], clause 6.1.1). If the field is absent, the UE transmits PUSCH on one antenna port, see TS 38.214 [19], clause 6.1.1. | +| uci-OnPUSCH-ListDCI-0-1, uci-OnPUSCH-ListDCI-0-2
Configuration for up to 2 HARQ-ACK codebooks specific to DCI format 0_1/0_2. The field uci-OnPUSCH-ListDCI-0-1 applies to DCI format 0_1 and the field uci-OnPUSCH-ListDCI-0-2 applies to DCI format 0_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13] clause 9.3). | +| ul-AccessConfigListDCI-0-1, ul-AccessConfigListDCI-0-2
List of the combinations of cyclic prefix extension, channel access priority class (CAPC), and UL channel access type (see TS 38.212 [17], clause 7.3.1) applicable for DCI format 0_1 and DCI format 0_2, respectively. The fields ul-AccessConfigListDCI-0-1-r16 and ul-AccessConfigListDCI-0-2-r17 are only applicable for FR1 (see TS 38.212 [17], Table 7.3.1.1.2-35). The field ul-AccessConfigListDCI-0-1-r17 only contains a list of UL channel access types and is only applicable for FR2-2 (see TS 38.212 [17], Table 7.3.1.1.2-35A). | +| ul-FullPowerTransmission
Configures the UE with UL full power transmission mode as specified in TS 38.213 [13]. This field is not configured if ul-powerControl is configured in the BWP-UplinkDedicated in which the PUCCH-Config is included. | + +| PUSCH-ConfigDCI-0-3 field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| harq-ProcessNumberSizeDCI-0-3
Configure the number of bits for the field "HARQ process number" in DCI format 0_3 (see TS 38.212 [17], clause 7.3.1). | +| numberOfBitsForRV-DCI-0-3
Configures the number of bits for "Redundancy version" in the DCI format 0_3 (see TS 38.212 [17], clause 7.3.1 and TS 38.214 [19], clause 6.1.2.1). | +| rbg-SizeDCI-0-3
Selection among configuration 1, configuration 2 and configuration 3 for RBG size for PUSCH. The UE does not apply this field if resourceAllocationDCI-0-3 is set to resourceAllocationType1. Otherwise, the UE applies the value config1 when the field is absent (see TS 38.214 [19], clause 6.1.2.2.1). | +| resourceAllocationDCI-0-3
Configuration of resource allocation type 0 and resource allocation type 1 for non-fallback DCI (see TS 38.214 [19], clause 6.1.2). | +| resourceAllocationType1GranularityDCI-0-3
Configures the scheduling granularity applicable for both the starting point and length indication for resource allocation type 1 in DCI format 0_3. If this field is absent, the granularity is 1 PRB (see TS 38.214 [19], clause 6.1.2.2.2). | +| uci-OnPUSCH-ListDCI-0-3
Selection between and configuration of dynamic and semi-static beta-offset for DCI format 0_3. | + +| SDM-Scheme field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| maxRankSDM, maxRankSDM-DCI-0-2
configure maximal number of MIMO layers of each panel in SDM scheme for codebook based PUSCH or for DCI 0_2 for codebook based PUSCH. | +| maxMIMO-LayersforSDM
Indicates the maximal number of MIMO layers of each panel for PUSCH with SDM scheme for non-codebook based PUSCH. | + +| SFN-Scheme field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| maxRankSFN, maxRankSFN-DCI-0-2
configure maximal number of MIMO layers of each panel in SFN scheme for codebook based PUSCH or for DCI 0_2 for codebook based PUSCH. | +| maxMIMO-LayersforSFN
Indicates the maximal number of MIMO layers of each panel for PUSCH with SFN scheme for non-codebook based PUSCH. | + +| UCI-OnPUSCH field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| betaOffsets
Selection between and configuration of dynamic and semi-static beta-offset for DCI formats other than DCI format 0_2. If the field is not configured, the UE applies the value 'semiStatic' (see TS 38.213 [13], clause 9.3). | +| scaling
Indicates a scaling factor to limit the number of resource elements assigned to UCI on PUSCH for DCI formats other than DCI format 0_2. Value f0p5 corresponds to 0.5, value f0p65 corresponds to 0.65, and so on. The value configured herein is applicable for PUSCH with configured grant (see TS 38.212 [17], clause 6.3). | + +| UCI-OnPUSCH-DCI-0-2 field descriptions | | +|-----------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| betaOffsetsDCI-0-2 | Configuration of beta-offset for DCI format 0_2. If semiStaticDCI-0-2 is chosen, the UE shall apply the value of 0 bit for the field of beta offset indicator in DCI format 0_2. If dynamicDCI-0-2 is chosen, the UE shall apply the value of 1 bit or 2 bits for the field of beta offset indicator in DCI format 0_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13] clause 9.3). | +| dynamicDCI-0-2 | Indicates the UE applies the value 'dynamic' for DCI format 0_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 9.3). | +| semiStaticDCI-0-2 | Indicates the UE applies the value 'semiStatic' for DCI format 0_2. (see TS 38.212 [17], clause 7.3.1 and see TS 38.213 [13], clause 9.3). | +| scalingDCI-0-2 | Indicates a scaling factor to limit the number of resource elements assigned to UCI on PUSCH for DCI format 0_2. Value f0p5 corresponds to 0.5, value f0p65 corresponds to 0.65, and so on (see TS 38.212 [17], clause 6.3). | + +| Conditional Presence | Explanation | +|-----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| codebookBased | The field is mandatory present if txConfig is set to codebook and absent otherwise. | +| RepTypeB | The field is optionally present, Need S, if pusch-RepTypeIndicatorDCI-0-1 is set to pusch-RepTypeB . It is absent otherwise. | +| RepTypeB2 | The field is optionally present, Need S, if pusch-RepTypeIndicatorDCI-0-1 or pusch-RepTypeIndicatorDCI-0-2 is set to pusch-RepTypeB . It is absent otherwise. | +| SRSsets | This field is mandatory present when UE is configured with two SRS sets in either srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 with usage codebook or non-codebook. | + +#### — *PUSCH-ConfigCommon* + +The IE *PUSCH-ConfigCommon* is used to configure the cell specific PUSCH parameters. + +#### ***PUSCH-ConfigCommon* information element** + +``` +-- ASN1START +-- TAG-PUSCH-CONFIGCOMMON-START + +PUSCH-ConfigCommon ::= SEQUENCE { + groupHoppingEnabledTransformPrecoding ENUMERATED {enabled} OPTIONAL, -- Need R + pusch-TimeDomainAllocationList PUSCH-TimeDomainResourceAllocationList OPTIONAL, -- Need R + msg3-DeltaPreamble INTEGER (-1..6) OPTIONAL, -- Need R + p0-NominalWithGrant INTEGER (-202..24) OPTIONAL, -- Need R + ... +} + +-- TAG-PUSCH-CONFIGCOMMON-STOP +-- ASN1STOP +``` + +| PUSCH-ConfigCommon field descriptions | | +|----------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| groupHoppingEnabledTransformPrecoding | For DMRS transmission with transform precoder, the NW may configure group hopping by this cell-specific parameter, see TS 38.211 [16], clause 6.4.1.1.1.2. | +| msg3-DeltaPreamble | Power offset between msg3 and RACH preamble transmission. Actual value = field value * 2 [dB] (see TS 38.213 [13], clause 7.1) | +| p0-NominalWithGrant | P0 value for PUSCH with grant (except msg3). Value in dBm. Only even values (step size 2) allowed (see TS 38.213 [13], clause 7.1) This field is cell specific | +| pusch-TimeDomainAllocationList | List of time domain allocations for timing of UL assignment to UL data (see TS 38.214 [19], table 6.1.2.1.1-1). | + +#### – **PUSCH-PowerControl** + +The IE **PUSCH-PowerControl** is used to configure UE specific power control parameter for PUSCH. + +#### **PUSCH-PowerControl information element** + +``` +-- ASN1START +-- TAG-PUSCH-POWERCONTROL-START + +PUSCH-PowerControl ::= SEQUENCE { + tpc-Accumulation ENUMERATED { disabled } OPTIONAL, -- Need S + msg3-Alpha Alpha OPTIONAL, -- Need S + p0-NominalWithoutGrant INTEGER (-202..24) OPTIONAL, -- Need M + p0-AlphaSets SEQUENCE (SIZE (1..maxNrofP0-PUSCH-AlphaSets)) OF P0-PUSCH-AlphaSet OPTIONAL, -- Need M + pathlossReferenceRSToAddModList SEQUENCE (SIZE (1..maxNrofPUSCH-PathlossReferenceRSs)) OF PUSCH-PathlossReferenceRS OPTIONAL, -- Need N + pathlossReferenceRSToReleaseList SEQUENCE (SIZE (1..maxNrofPUSCH-PathlossReferenceRSs)) OF PUSCH-PathlossReferenceRS-Id OPTIONAL, -- Need N + twoPUSCH-PC-AdjustmentStates ENUMERATED {twoStates} OPTIONAL, -- Need S + deltaMCS ENUMERATED {enabled} OPTIONAL, -- Need S + sri-PUSCH-MappingToAddModList SEQUENCE (SIZE (1..maxNrofSRI-PUSCH-Mappings)) OF SRI-PUSCH-PowerControl OPTIONAL, -- Need N + sri-PUSCH-MappingToReleaseList SEQUENCE (SIZE (1..maxNrofSRI-PUSCH-Mappings)) OF SRI-PUSCH-PowerControlId OPTIONAL -- Need N +} + +P0-PUSCH-AlphaSet ::= SEQUENCE { + p0-PUSCH-AlphaSetId P0-PUSCH-AlphaSetId, + p0 INTEGER (-16..15) OPTIONAL, -- Need S + alpha Alpha OPTIONAL -- Need S +} + +P0-PUSCH-AlphaSetId ::= INTEGER (0..maxNrofP0-PUSCH-AlphaSets-1) + +PUSCH-PathlossReferenceRS ::= SEQUENCE { + pusch-PathlossReferenceRS-Id PUSCH-PathlossReferenceRS-Id, + referenceSignal CHOICE { +``` + +``` + + ssb-Index SSB-Index, + csi-RS-Index NZP-CSI-RS-ResourceId + } +} + +PUSCH-PathlossReferenceRS-r16 ::= SEQUENCE { + pusch-PathlossReferenceRS-Id-r16 PUSCH-PathlossReferenceRS-Id-v1610, + referenceSignal-r16 CHOICE { + ssb-Index-r16 SSB-Index, + csi-RS-Index-r16 NZP-CSI-RS-ResourceId + } +} + +DummyPathlossReferenceRS-v1710 ::= SEQUENCE { + pusch-PathlossReferenceRS-Id-r17 PUSCH-PathlossReferenceRS-Id-r17, + additionalPCI-r17 AdditionalPCIIndex-r17 OPTIONAL -- Need R +} + +PUSCH-PathlossReferenceRS-Id ::= INTEGER (0..maxNrofPUSCH-PathlossReferenceRSs-1) + +PUSCH-PathlossReferenceRS-Id-v1610 ::= INTEGER (maxNrofPUSCH-PathlossReferenceRSs..maxNrofPUSCH-PathlossReferenceRSs-1-r16) + +PUSCH-PathlossReferenceRS-Id-r17 ::= INTEGER (0..maxNrofPUSCH-PathlossReferenceRSs-1-r16) + +SRI-PUSCH-PowerControl ::= SEQUENCE { + sri-PUSCH-PowerControlId SRI-PUSCH-PowerControlId, + sri-PUSCH-PathlossReferenceRS-Id PUSCH-PathlossReferenceRS-Id, + sri-P0-PUSCH-AlphaSetId P0-PUSCH-AlphaSetId, + sri-PUSCH-ClosedLoopIndex ENUMERATED { i0, i1 } +} + +SRI-PUSCH-PowerControlId ::= INTEGER (0..maxNrofSRI-PUSCH-Mappings-1) + +PUSCH-PowerControl-v1610 ::= SEQUENCE { + pathlossReferenceRSToAddModListSizeExt-v1610 SEQUENCE (SIZE (1..maxNrofPUSCH-PathlossReferenceRSsDiff-r16)) OF PUSCH-PathlossReferenceRS-r16 + OPTIONAL, -- Need N + pathlossReferenceRSToReleaseListSizeExt-v1610 SEQUENCE (SIZE (1..maxNrofPUSCH-PathlossReferenceRSsDiff-r16)) OF PUSCH-PathlossReferenceRS-Id-v1610 + OPTIONAL, -- Need N + p0-PUSCH-SetList-r16 SEQUENCE (SIZE (1..maxNrofSRI-PUSCH-Mappings)) OF P0-PUSCH-Set-r16 + OPTIONAL, -- Need R + olpc-ParameterSet SEQUENCE { + olpc-ParameterSetDCI-0-1-r16 INTEGER (1..2) OPTIONAL, -- Need R + olpc-ParameterSetDCI-0-2-r16 INTEGER (1..2) OPTIONAL, -- Need R + } OPTIONAL, -- Need M + ..., + [[ + sri-PUSCH-MappingToAddModList2-r17 SEQUENCE (SIZE (1..maxNrofSRI-PUSCH-Mappings)) OF SRI-PUSCH-PowerControl + OPTIONAL, -- Need N + sri-PUSCH-MappingToReleaseList2-r17 SEQUENCE (SIZE (1..maxNrofSRI-PUSCH-Mappings)) OF SRI-PUSCH-PowerControlId OPTIONAL, -- Need N + p0-PUSCH-SetList2-r17 SEQUENCE (SIZE (1..maxNrofSRI-PUSCH-Mappings)) OF P0-PUSCH-Set-r16 + OPTIONAL, -- Need R + dummy SEQUENCE (SIZE (1..maxNrofPUSCH-PathlossReferenceRSs-r16)) OF DummyPathlossReferenceRS-v1710 + OPTIONAL -- Need N + ]] +} +``` + +``` + + ]] +} + +P0-PUSCH-Set-r16 ::= + p0-PUSCH-SetId-r16 + p0-List-r16 + ... +} + +P0-PUSCH-SetId-r16 ::= + INTEGER (0..maxNrofPUSCH-Mappings-1) + +P0-PUSCH-r16 ::= + INTEGER (-16..15) + +-- TAG-PUSCH-POWERCONTROL-STOP +-- ASN1STOP + +``` + +#### P0-PUSCH-AlphaSet field descriptions + +| | | +|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| alpha | alpha value for PUSCH with grant (except msg3) (see TS 38.213 [13], clause 7.1). When the field is absent the UE applies the value 1. | +| p0 | P0 value for PUSCH with grant (except msg3) in steps of 1dB (see TS 38.213 [13], clause 7.1). When the field is absent the UE applies the value 0. | + +#### P0-PUSCH-Set field descriptions + +| | | +|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| p0-List | Configuration of {p0-PUSCH, p0-PUSCH} sets for PUSCH. If SRI is present in the DCI, then one p0-PUSCH can be configured in P0-PUSCH-Set. If SRI is not present in the DCI, and both olpc-ParameterSetDCI-0-1 and olpc-ParameterSetDCI-0-2 are configured to be 1 bit, then one p0-PUSCH can be configured in P0-PUSCH-Set. If SRI is not present in the DCI, and if any of olpc-ParameterSetDCI-0-1 and olpc-ParameterSetDCI-0-2 is configured to be 2 bits, then two p0-PUSCH values can be configured in P0-PUSCH-Set (see TS 38.213 [13] clause 7 and TS 38.212 [17] clause 7.3.1). | +| p0-PUSCH-SetId | Configure the index of a p0-PUSCH-Set (see TS 38.213 [13] clause 7 and TS 38.212 [17] clause 7.3.1). | + +| PUSCH-PowerControl field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| deltaMCS
Indicates whether to apply delta MCS. When the field is absent, the UE applies $K_s = 0$ in delta_TFC formula for PUSCH (see TS 38.213 [13], clause 7.1). | +| dummy
This field is not used in the specification. If received it shall be ignored by the UE. | +| msg3-Alpha
Dedicated alpha value for msg3 PUSCH (see TS 38.213 [13], clause 7.1). When the field is absent the UE applies the value 1. | +| olpc-ParameterSetDCI-0-1, olpc-ParameterSetDCI-0-2
Configures the number of bits for Open-loop power control parameter set indication for DCI format 0_1/0_2 in case SRI is not configured in the DCI. 2 bits is applicable only if SRI is not present in the DCI format 0_1. The field olpc-ParameterSetDCI-0-1 applies to DCI format 0_1 and the field olpc-ParameterSetDCI-0-2 applies to DCI format 0_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 11). | +| p0-AlphaSets
Configuration { p0-pusch , alpha } sets for PUSCH (except msg3 and msgA PUSCH), i.e., { { p0.alpha.index1 }, { p0.alpha.index2 }, ... } (see TS 38.213 [13], clause 7.1). When no set is configured, the UE uses the P0-nominal for msg3/msgA PUSCH, P0-UE is set to 0 and alpha is set according to either msg3-Alpha or msgA-Alpha (see TS 38.213 [13], clause 7.1). | +| p0-NominalWithoutGrant
P0 value for UL grant-free/SPS based PUSCH. Value in dBm. Only even values (step size 2) allowed (see TS 38.213 [13], clause 7.1). | +| p0-PUSCH-SetList
Configure one additional P0-PUSCH-Set per SRI. If present, the one bit or 2 bits in the DCI is used to dynamically indicate among the P0 value from the existing P0-PUSCH-AlphaSet and the P0 value(s) from the P0-PUSCH-Set (See TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 17). | +| p0-PUSCH-SetList2
For indicating per-TRP OLPC set in DCI format 0_1/0_2 with the open-loop power control parameter set indication field, a second p0-PUSCH-SetList-r16 is used. When this field is present the p0-PUSCH-SetList-r16 corresponds to the first SRS resource set (see TS 38.213 [13]). | +| pathlossReferenceRSToAddModList, pathlossReferenceRSToAddModListSizeExt
A set of Reference Signals (e.g. a CSI-RS config or a SS block) to be used for PUSCH path loss estimation. The set consists of Reference Signals configured using pathLossReferenceRSToAddModList and Reference Signals configured using pathlossReferenceRSToAddModListSizeExt . Up to maxNrofPUSCH-PathlossReferenceRSs may be configured (see TS 38.213 [13], clause 7.1). | +| pathlossReferenceRSToReleaseList, pathlossReferenceRSToReleaseListSizeExt
Lists of reference signals for PUSCH path loss estimation to be released by the UE. | +| sri-PUSCH-MappingToAddModList
A list of SRI-PUSCH-PowerControl elements among which one is selected by the SRI field in DCI (see TS 38.213 [13], clause 7.1). | +| sri-PUSCH-MappingToAddModList2
A list of SRI-PUSCH-PowerControl elements for second SRS-resource set, among which one is selected by the SRI field in DCI (see TS 38.213 [13], clause 7.1). When this field is present the sri-PUSCH-MappingToAddModList corresponds to the first SRS resource set for PUSCH. | +| tpc-Accumulation
If enabled, UE applies TPC commands via accumulation. If not enabled, UE applies the TPC command without accumulation. If the field is absent, TPC accumulation is enabled (see TS 38.213 [13], clause 7.1). | +| twoPUSCH-PC-AdjustmentStates
Number of PUSCH power control adjustment states maintained by the UE (i.e., $fc(i)$ ). If the field is present ( $n2$ ) the UE maintains two power control states (i.e., $fc(i,0)$ and $fc(i,1)$ ). If the field is absent, it maintains one power control state (i.e., $fc(i,0)$ ) (see TS 38.213 [13], clause 7.1). | + +| SRI-PUSCH-PowerControl field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sri-P0-PUSCH-AlphaSetId
The ID of a P0-PUSCH-AlphaSet as configured in p0-AlphaSets in PUSCH-PowerControl . | +| sri-PUSCH-ClosedLoopIndex
The index of the closed power control loop associated with this SRI-PUSCH-PowerControl . | +| sri-PUSCH-PathlossReferenceRS-Id
The ID of PUSCH-PathlossReferenceRS as configured in the pathlossReferenceRSToAddModList in PUSCH-PowerControl . | +| sri-PUSCH-PowerControlId
The ID of this SRI-PUSCH-PowerControl configuration. It is used as the codepoint (payload) in the SRI DCI field. | + +#### — *PUSCH-ServingCellConfig* + +The IE *PUSCH-ServingCellConfig* is used to configure UE specific PUSCH parameters that are common across the UE's BWPs of one serving cell. + +#### ***PUSCH-ServingCellConfig* information element** + +``` +-- ASN1START +-- TAG-PUSCH-SERVINGCELLCONFIG-START + +PUSCH-ServingCellConfig ::= SEQUENCE { + codeBlockGroupTransmission SetupRelease { PUSCH-CodeBlockGroupTransmission } OPTIONAL, -- Need M + rateMatching ENUMERATED {limitedBufferRM} OPTIONAL, -- Need S + xOverhead ENUMERATED {xoh6, xoh12, xoh18} OPTIONAL, -- Need S + ..., + [[ + maxMIMO-Layers INTEGER (1..4) OPTIONAL, -- Need M + processingType2Enabled BOOLEAN OPTIONAL -- Need M + ]], + [[ + maxMIMO-LayersDCI-0-2-r16 SetupRelease { MaxMIMO-LayersDCI-0-2-r16} OPTIONAL -- Need M + ]], + [[ + nrofHARQ-ProcessesForPUSCH-r17 ENUMERATED {n32} OPTIONAL, -- Need R + uplinkHARQ-mode-r17 SetupRelease { UplinkHARQ-mode-r17} OPTIONAL -- Need M + ]], + [[ + maxMIMO-Layers-n8-r18 SetupRelease { MaxMIMO-LayersDCI-n8-r18} OPTIONAL, -- Need M + maxMIMO-LayersforSDM-r18 INTEGER (1..2) OPTIONAL, -- Need R + maxMIMO-LayersforSDM-DCI-0-2-r18 INTEGER (1..2) OPTIONAL, -- Need R + maxMIMO-LayersforSFN-r18 INTEGER (1..2) OPTIONAL, -- Need R + maxMIMO-LayersforSFN-DCI-0-2-r18 INTEGER (1..2) OPTIONAL -- Need R + ]] +} + +PUSCH-CodeBlockGroupTransmission ::= SEQUENCE { + maxCodeBlockGroupsPerTransportBlock ENUMERATED {n2, n4, n6, n8}, + ... +} +``` + +``` +} +MaxMIMO-LayersDCI-0-2-r16 ::= INTEGER (1..4) +MaxMIMO-LayersDCI-n8-r18 ::= INTEGER (5..8) + +UplinkHARQ-mode-r17 ::= BIT STRING (SIZE (32)) + +-- TAG-PUSCH-SERVINGCELLCONFIG-STOP +-- ASN1STOP +``` + +#### | | |-------------------------------------------------------------------| | PUSCH-CodeBlockGroupTransmission field descriptions | |-------------------------------------------------------------------| + +##### | | |---------------------------------------------------| | maxCodeBlockGroupsPerTransportBlock | |---------------------------------------------------| + +| | +|-------------------------------------------------------------------------------------| +| Maximum number of code-block-groups (CBGs) per TB (see TS 38.213 [13], clause 9.1). | +|-------------------------------------------------------------------------------------| + +| PUSCH-ServingCellConfig field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| codeBlockGroupTransmission
Enables and configures code-block-group (CBG) based transmission (see TS 38.214 [19], clause 5.1.5).
The network does not configure this field if the SCS of at least one UL BWP configured in the cell is 480 or 960 kHz. | +| maxMIMO-Layers, maxMIMO-Layers-n8
Indicates the maximum MIMO layer to be used for PUSCH in all BWPs of the corresponding UL of this serving cell (see TS 38.212 [17], clause 5.4.2.1). If present, the network sets maxRank to the same value. The field maxMIMO-Layers refers to DCI format 0_1. | +| maxMIMO-LayersforSDM
Parameter to indicate maximal number of MIMO layers of each panel for PUSCH with SDM scheme for NCB PUSCH | +| maxMIMO-LayersforSDM-DCI-0-2
Parameter to indicate maximal number of MIMO layers of each panel for PUSCH with SDM scheme for DCI format 0_2 for NCB PUSCH | +| maxMIMO-LayersforSFN
Parameter to indicate maximal number of MIMO layers of each panel for PUSCH with SFN scheme for NCB PUSCH | +| maxMIMO-LayersforSFN-DCI-0-2
Parameter to indicate maximal number of MIMO layers of each panel for PUSCH with SFN scheme for DCI format 0_2 for NCB PUSCH | +| nrofHARQ-ProcessesForPUSCH
The number of HARQ processes to be used on the PUSCH of a serving cell. Value n32 corresponds to 32 HARQ processes. If the field is absent, the UE uses 16 HARQ processes (see TS 38.214 [19], clause 6.1). | +| processingType2Enabled
Enables configuration of advanced processing time capability 2 for PUSCH (see 38.214 [19], clause 6.4). | +| rateMatching
Enables LBRM (Limited buffer rate-matching). When the field is absent the UE applies FBRM (Full buffer rate-matchingLBRM) (see TS 38.212 [17], clause 5.4.2). | +| xOverhead
If the field is absent, the UE applies the value 'xoh0' (see TS 38.214 [19], clause 5.1.3.2). | +| maxMIMO-LayersDCI-0-2
Indicates the maximum MIMO layer to be used for PUSCH for DCI format 0_2 in all BWPs of the corresponding UL of this serving cell (see TS 38.212 [17], clause 5.4.2.1). If present, the network sets maxRankDCI-0-2 to the same value. | +| uplinkHARQ-mode
Used to set the HARQ mode per HARQ process ID, see TS 38.321 [3]. The first/leftmost bit corresponds to HARQ process ID 0, the next bit to HARQ process ID 1 and so on. Bits corresponding to HARQ process IDs that are not configured shall be ignored. A bit set to one identifies a HARQ process with HARQmodeA and a bit set to zero identifies a HARQ process with HARQ modeB . This field applies for SRBs and DRBs. | + +#### – *PUSCH-TimeDomainResourceAllocationList* + +The IE *PUSCH-TimeDomainResourceAllocation* is used to configure a time domain relation between PDCCH and PUSCH. *PUSCH-TimeDomainResourceAllocationList* contains one or more of such *PUSCH-TimeDomainResourceAllocations*. The network indicates in the UL grant which of the configured time domain allocations the UE shall apply for that UL grant. The UE determines the bit width of the DCI field based on the number of entries in the *PUSCH-TimeDomainResourceAllocationList*. Value 0 in the DCI field refers to the first element in this list, value 1 in the DCI field refers to the second element in this list, and so on. + +#### ***PUSCH-TimeDomainResourceAllocation* information element** + +``` +-- ASN1START +-- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-START +``` + +``` + +PUSCH-TimeDomainResourceAllocationList ::= SEQUENCE (SIZE(1..maxNrofUL-Allocations)) OF PUSCH-TimeDomainResourceAllocation + +PUSCH-TimeDomainResourceAllocation ::= SEQUENCE { + k2 INTEGER(0..32) OPTIONAL, -- Need S + mappingType ENUMERATED {typeA, typeB}, + startSymbolAndLength INTEGER (0..127) +} + +PUSCH-TimeDomainResourceAllocationList-r16 ::= SEQUENCE (SIZE(1..maxNrofUL-Allocations-r16)) OF PUSCH-TimeDomainResourceAllocation-r16 + +PUSCH-TimeDomainResourceAllocation-r16 ::= SEQUENCE { + k2-r16 INTEGER(0..32) OPTIONAL, -- Need S + pusAllocationList-r16 SEQUENCE (SIZE(1..maxNrofMultiplePUSCHs-r16)) OF PUSCH-Allocation-r16, + ... +} + +PUSCH-Allocation-r16 ::= SEQUENCE { + mappingType-r16 ENUMERATED {typeA, typeB} OPTIONAL, -- Cond NotFormat01-02-Or-TypeA + startSymbolAndLength-r16 INTEGER (0..127) OPTIONAL, -- Cond NotFormat01-02-Or-TypeA + startSymbol-r16 INTEGER (0..13) OPTIONAL, -- Cond RepTypeB + length-r16 INTEGER (1..14) OPTIONAL, -- Cond RepTypeB + numberOfRepetitions-r16 ENUMERATED {n1, n2, n3, n4, n7, n8, n12, n16} OPTIONAL, -- Cond Format01-02 + ..., + [[ + numberOfRepetitionsExt-r17 ENUMERATED {n1, n2, n3, n4, n7, n8, n12, n16, n20, n24, n28, n32, spare4, spare3, spare2, + spare1} OPTIONAL, -- Cond Format01-02-For-TypeA + numberOfSlotsTBoMS-r17 ENUMERATED {n1, n2, n4, n8, spare4, spare3, spare2, spare1} OPTIONAL, -- Need R + extendedK2-r17 INTEGER (0..128) OPTIONAL -- Cond MultiPUSCH + ]] +} + +-- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STOP +-- ASN1STOP + +``` + +| PUSCH-TimeDomainResourceAllocationList field descriptions | | +|------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| extendedK2 | Corresponds to L1 parameter 'K2' (see TS 38.214 [19], clause 6.1.2.1) configurable per PUSCH allocation. Only values {0..32} are applicable for PUSCH SCS of 120 kHz. When the field is absent for the first PUSCH if multiple PUSCH are configured per PDCCH and k2-r16 is absent, or when the field is absent and only one PUSCH is configured per PDCCH and k2-r16 is absent, the UE applies the value 1 when PUSCH SCS is 15/30 kHz; the value 2 when PUSCH SCS is 60 kHz, the value 3 when PUSCH SCS is 120 kHz, the value 11 when PUSCH SCS is 480 kHz, and the value 21 when PUSCH SCS is 960 kHz. If multiple contiguous PUSCHs are configured per PDCCH, when the field extendedK2(n) corresponding to k2 of the PUSCH(s) in the n-th slot ( $n > 1$ ), or of the PUSCH(s) except the first PUSCH in the first slot ( $n = 1$ ), is absent, the UE applies k2 of the first PUSCH plus n-1. | +| k2 | Corresponds to L1 parameter 'K2' (see TS 38.214 [19], clause 6.1.2.1). When the field is absent the UE applies the value 1 when PUSCH SCS is 15/30 kHz; the value 2 when PUSCH SCS is 60 kHz, and the value 3 when PUSCH SCS is 120 kHz. k2 is absent/ignored if extendedK2 is present. | +| length | Indicates the length allocated for PUSCH for DCI format 0_1/0_2 (see TS 38.214 [19], clause 6.1.2.1). | +| mappingType | Mapping type (see TS 38.214 [19], clause 6.1.2.1). | +| numberOfRepetitions | Number of repetitions for DCI format 0_1/0_2 (see TS 38.214 [19], clause 6.1.2.1). When numberOfSlotsTBoMS-r17 is set to 2, 4 or 8 (i.e. TB processing over multi-slot (TBoMS) PUSCH is enabled), it indicates the number of repetitions of a single TBoMS. | +| numberOfRepetitionsExt | Number of repetitions for DCI format 0_1/0_2 if pusch-RepTypeIndicatorDCI-0-1/pusch-RepTypeIndicatorDCI-0-2 is not set to pusch-RepTypeB (see TS 38.214 [19], clause 6.1.2.1). If this field is present, the field numberOfRepetitions-r16 is ignored for PUSCH repetition Type A. | +| numberOfSlotsTBoMS | Number of slots allocated for TB processing over multi-slot PUSCH for DCI format 0_1/0_2. If a number of repetitions K is configured by numberOfRepetitions or numberOfRepetitionsExt , the network configures numberOfSlotsTBoMS (N) and K such that $N * K \leq 32$ (see TS 38.214 [19], clause 6.1.2.1). The network does not configure the numberOfSlotsTBoMS-r17 simultaneously with the pusch-TimeDomainAllocationListForMultiPUSCH-r16 . | +| puschAllocationList | The field puschAllocationList-r16 indicates one or multiple PUSCH continuous in time domain which share a common k2 (see TS 38.214 [19], clause 6.1.2.1). In this release, this field configures one or multiple PUSCH that may be in consecutive or non-consecutive slots (see TS 38.214 [19], clause 6.1.2.1). The puschAllocationList-r16 only has one element in pusch-TimeDomainAllocationListDCI-0-1-r16 and in pusch-TimeDomainAllocationListDCI-0-2-r16 . | +| startSymbol | Indicates the index of start symbol for PUSCH for DCI format 0_1/0_2 (see TS 38.214 [19], clause 6.1.2.1). | +| startSymbolAndLength | An index giving valid combinations of start symbol and length (jointly encoded) as start and length indicator (SLIV). The network configures the field so that the allocation does not cross the slot boundary. (see TS 38.214 [19], clause 6.1.2.1). | + +| Conditional Presence | Explanation | +|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Format01-02 | In pusch-TimeDomainAllocationListForMultiPUSCH-r16 , the field is absent.
In pusch-TimeDomainAllocationListDCI-0-1 and in pusch-TimeDomainAllocationListDCI-0-2 , the field is mandatory present. | +| Format01-02-For-TypeA | In pusch-TimeDomainAllocationListForMultiPUSCH-r16 , the field is absent.
In pusch-TimeDomainAllocationListDCI-0-1 , the field is optionally present if pusch-RepTypeIndicatorDCI-0-1 is not set to pusch-RepTypeB , Need R. It is absent otherwise, Need R.
In pusch-TimeDomainAllocationListDCI-0-2 , the field is optionally present if pusch-RepTypeIndicatorDCI-0-2 is not set to pusch-RepTypeB , Need R. It is absent otherwise, Need R. | +| NotFormat01-02-Or-TypeA | In pusch-TimeDomainAllocationListForMultiPUSCH-r16 , the field is mandatory present.
In pusch-TimeDomainAllocationListDCI-0-1 , the field is mandatory present if pusch-RepTypeIndicatorDCI-0-1 is not set to pusch-RepTypeB . It is absent otherwise, Need R.
In pusch-TimeDomainAllocationListDCI-0-2 , the field is mandatory present if pusch-RepTypeIndicatorDCI-0-2 is not set to pusch-RepTypeB . It is absent otherwise, Need R. | +| RepTypeB | In pusch-TimeDomainAllocationListForMultiPUSCH-r16 , the field is absent.
In pusch-TimeDomainAllocationListDCI-0-1 , the field is mandatory present if pusch-RepTypeIndicatorDCI-0-1 is set to pusch-RepTypeB . It is absent otherwise, Need R.
In pusch-TimeDomainAllocationListDCI-0-2 , the field is mandatory present if pusch-RepTypeIndicatorDCI-0-2 is set to pusch-RepTypeB . It is absent otherwise, Need R. | +| MultiPUSCH | In case size of puschAllocationList is higher than 1, the field extendedK2(n) corresponding to k2 of the n -th PUSCH, n>1 , is mandatory present for all n , if any two consecutive PUSCHs are non-contiguous. Otherwise, it is optionally present, Need S. | + +#### — *PUSCH-TPC-CommandConfig* + +The IE *PUSCH-TPC-CommandConfig* is used to configure the UE for extracting TPC commands for PUSCH from a group-TPC messages on DCI. + +#### *PUSCH-TPC-CommandConfig* information element + +``` +-- ASN1START +-- TAG-PUSCH-TPC-COMMANDCONFIG-START + +PUSCH-TPC-CommandConfig ::= SEQUENCE { + tpc-Index INTEGER (1..15) OPTIONAL, -- Cond SUL + tpc-IndexSUL INTEGER (1..15) OPTIONAL, -- Cond SUL-Only + targetCell ServCellIndex OPTIONAL, -- Need S + ... +} + +-- TAG-PUSCH-TPC-COMMANDCONFIG-STOP +-- ASN1STOP +``` + +| PUSCH-TPC-CommandConfig field descriptions | | +|---------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| targetCell | The serving cell to which the acquired power control commands are applicable. If the value is absent, the UE applies the TPC commands to the serving cell on which the command has been received. | +| tpc-Index | An index determining the position of the first bit of TPC command inside the DCI format 2-2 payload. | +| tpc-IndexSUL | An index determining the position of the first bit of TPC command inside the DCI format 2-2 payload. | + +| Conditional Presence | Explanation | +|-----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| SUL-Only | The field is optionally present, Need R, if supplementaryUplink is configured within ServingCellConfig . It is absent otherwise. | +| SUL | The field is optionally present, Need R, if supplementaryUplink is configured within ServingCellConfig . It is mandatory present otherwise. | + +#### — Q-OffsetRange + +The IE *Q-OffsetRange* is used to indicate a cell, beam or measurement object specific offset to be applied when evaluating candidates for cell re-selection or when evaluating triggering conditions for measurement reporting. The value is in dB. Value *dB-24* corresponds to -24 dB, *dB-22* corresponds to -22 dB and so on. + +#### **Q-OffsetRange information element** + +``` +-- ASN1START +-- TAG-Q-OFFSETRANGE-START + +Q-OffsetRange ::= + ENUMERATED { + dB-24, dB-22, dB-20, dB-18, dB-16, dB-14, + dB-12, dB-10, dB-8, dB-6, dB-5, dB-4, dB-3, + dB-2, dB-1, dB0, dB1, dB2, dB3, dB4, dB5, + dB6, dB8, dB10, dB12, dB14, dB16, dB18, + dB20, dB22, dB24} + +-- TAG-Q-OFFSETRANGE-STOP +-- ASN1STOP +``` + +#### — Q-QualMin + +The IE *Q-QualMin* is used to indicate for cell selection/ re-selection the required minimum received RSRQ level in the (NR) cell. Corresponds to parameter *Qqualmin* in TS 38.304 [20]. Actual value *Qqualmin* = field value [dB]. + +#### **Q-QualMin information element** + +``` +-- ASN1START +``` + +``` +-- TAG-Q-QUALMIN-START + +Q-QualMin ::= INTEGER (-43..-12) + +-- TAG-Q-QUALMIN-STOP +-- ASN1STOP +``` + +#### – *Q-RxLevMin* + +The IE *Q-RxLevMin* is used to indicate for cell selection/ re-selection the required minimum received RSRP level in the (NR) cell. Corresponds to parameter $Q_{rxlevmin}$ in TS 38.304 [20]. Actual value $Q_{rxlevmin} = \text{field value} * 2$ [dBm]. + +#### *Q-RxLevMin* information element + +``` +-- ASN1START +-- TAG-Q-RXLEVMIN-START + +Q-RxLevMin ::= INTEGER (-70..-22) + +-- TAG-Q-RXLEVMIN-STOP +-- ASN1STOP +``` + +#### – *QuantityConfig* + +The IE *QuantityConfig* specifies the measurement quantities and layer 3 filtering coefficients for NR and inter-RAT measurements. + +#### *QuantityConfig* information element + +``` +-- ASN1START +-- TAG-QUANTITYCONFIG-START + +QuantityConfig ::= SEQUENCE { + quantityConfigNR-List SEQUENCE (SIZE (1..maxNrofQuantityConfig)) OF QuantityConfigNR OPTIONAL, -- Need M + ..., + [[ + quantityConfigEUTRA FilterConfig OPTIONAL -- Need M + ]], + [[ + quantityConfigUTRA-FDD-r16 QuantityConfigUTRA-FDD-r16 OPTIONAL, -- Need M + quantityConfigCLI-r16 FilterConfigCLI-r16 OPTIONAL -- Need M + ]] +} + +QuantityConfigNR ::= SEQUENCE { + quantityConfigCell QuantityConfigRS, +``` + +``` + + quantityConfigRS-Index QuantityConfigRS OPTIONAL -- Need M +} + +QuantityConfigRS ::= SEQUENCE { + ssb-FilterConfig FilterConfig, + csi-RS-FilterConfig FilterConfig +} + +FilterConfig ::= SEQUENCE { + filterCoefficientRSRP FilterCoefficient DEFAULT fc4, + filterCoefficientRSRQ FilterCoefficient DEFAULT fc4, + filterCoefficientRS-SINR FilterCoefficient DEFAULT fc4 +} + +FilterConfigCLI-r16 ::= SEQUENCE { + filterCoefficientSRS-RSRP-r16 FilterCoefficient DEFAULT fc4, + filterCoefficientCLI-RSSI-r16 FilterCoefficient DEFAULT fc4 +} + +QuantityConfigUTRA-FDD-r16 ::= SEQUENCE { + filterCoefficientRSCP-r16 FilterCoefficient DEFAULT fc4, + filterCoefficientEcNO-r16 FilterCoefficient DEFAULT fc4 +} + +-- TAG-QUANTITYCONFIG-STOP +-- ASN1STOP + +``` + +#### QuantityConfigNR field descriptions + +##### **quantityConfigCell** + +Specifies L3 filter configurations for cell measurement results for the configurable RS Types (e.g. SS/PBCH block and CSI-RS) and the configurable measurement quantities (e.g. RSRP, RSRQ and SINR). + +##### **quantityConfigRS-Index** + +Specifies L3 filter configurations for measurement results per RS index for the configurable RS Types (e.g. SS/PBCH block and CSI-RS) and the configurable measurement quantities (e.g. RSRP, RSRQ and SINR). + +#### QuantityConfigRS field descriptions + +##### **csi-RS-FilterConfig** + +CSI-RS based L3 filter configurations: + +Specifies L3 filter configurations for CSI-RSRP, CSI-RSRQ and CSI-SINR measurement results from the L1 filter(s), as defined in TS 38.215 [9]. + +##### **ssb-FilterConfig** + +SS Block based L3 filter configurations: + +Specifies L3 filter configurations for SS-RSRP, SS-RSRQ and SS-SINR measurement results from the L1 filter(s), as defined in TS 38.215 [9]. + +| QuantityConfigUTRA-FDD field descriptions | +|------------------------------------------------------------------------------------------------------------------------------| +| filterCoefficientRSCP
Specifies L3 filter coefficient for FDD UTRAN CPICH_RSCP measurement results from L1 filter. | +| filterCoefficientEcN0
Specifies L3 filter coefficient for FDD UTRAN CPICH_EcN0 measurement results from L1 filter. | + +#### — *RACH-ConfigCommon* + +The IE *RACH-ConfigCommon* is used to specify the cell specific random-access parameters. + +#### *RACH-ConfigCommon* information element + +``` +-- ASN1START +-- TAG-RACH-CONFIGCOMMON-START + +RACH-ConfigCommon ::= + SEQUENCE { + rach-ConfigGeneric RACH-ConfigGeneric, + totalNumberOfRA-Preambles INTEGER (1..63) OPTIONAL, -- Need S + ssb-perRACH-OccasionAndCB-PreamblesPerSSB CHOICE { + oneEighth ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64}, + oneFourth ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64}, + oneHalf ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64}, + one ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64}, + two ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32}, + four INTEGER (1..16), + eight INTEGER (1..8), + sixteen INTEGER (1..4) + } OPTIONAL, -- Need M + + groupBConfigured SEQUENCE { + ra-Msg3SizeGroupA ENUMERATED {b56, b144, b208, b256, b282, b480, b640, + b800, b1000, b72, spare6, spare5, spare4, spare3, spare2, spare1}, + messagePowerOffsetGroupB ENUMERATED { minusinfinity, dB0, dB5, dB8, dB10, dB12, dB15, dB18}, + numberOfRA-PreamblesGroupA INTEGER (1..64) + } OPTIONAL, -- Need R + + ra-ContentionResolutionTimer ENUMERATED { sf8, sf16, sf24, sf32, sf40, sf48, sf56, sf64}, + rsrp-ThresholdSSB RSRP-Range OPTIONAL, -- Need R + rsrp-ThresholdSSB-SUL RSRP-Range OPTIONAL, -- Cond SUL + prach-RootSequenceIndex CHOICE { + 1839 INTEGER (0..837), + 1139 INTEGER (0..137) + }, + msg1-SubcarrierSpacing SubcarrierSpacing OPTIONAL, -- Cond L139 + restrictedSetConfig ENUMERATED {unrestrictedSet, restrictedSetTypeA, restrictedSetTypeB}, + msg3-transformPrecoder ENUMERATED {enabled} OPTIONAL, -- Need R + ... + [[ + ra-PrioritizationForAccessIdentity-r16 SEQUENCE { +``` + +``` + ra-Prioritization-r16 RA-Prioritization, + ra-PrioritizationForAI-r16 BIT STRING (SIZE (2)) + } OPTIONAL, -- Cond InitialBWP-Only + prach-RootSequenceIndex-r16 CHOICE { + 1571 INTEGER (0..569), + 11151 INTEGER (0..1149) + } OPTIONAL -- Need R +], [ + ra-PrioritizationForSlicing-r17 RA-PrioritizationForSlicing-r17 OPTIONAL, -- Cond InitialBWP-Only + featureCombinationPreamblesList-r17 SEQUENCE (SIZE(1..maxFeatureCombPreamblesPerRACHResource-r17)) OF FeatureCombinationPreambles-r17 +OPTIONAL -- Cond AdditionalRACH +]] +} + +-- TAG-RACH-CONFIGCOMMON-STOP +-- ASN1STOP +``` + +| RACH-ConfigCommon field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| featureCombinationPreamblesList
Specifies a series of preamble partitions each associated to a combination of features and 4-step RA. The network does not configure this list to have more than 32 entries. | +| messagePowerOffsetGroupB
Threshold for preamble selection. Value is in dB. Value minusinfinity corresponds to $-\infty$ . Value dB0 corresponds to 0 dB, dB5 corresponds to 5 dB and so on (see TS 38.321 [3], clause 5.1.2). This field is set to the same value for different repetition numbers associated with a specific FeatureCombination . | +| msg1-SubcarrierSpacing
Subcarrier spacing of PRACH (see TS 38.211 [16], clause 5.3.2).
Only the following values are applicable depending on the used frequency:
FR1: 15 or 30 kHz
FR2-1: 60 or 120 kHz
FR2-2: 120, 480, or 960 kHz
If absent, the UE applies the SCS as derived from the prach-ConfigurationIndex in RACH-ConfigGeneric (see tables Table 6.3.3.1-1, Table 6.3.3.1-2, Table 6.3.3.2-2 and Table 6.3.3.2-3, TS 38.211 [16]). The value also applies to contention free random access ( RACH-ConfigDedicated ), to SI-request and to contention-based beam failure recovery (CB-BFR). But it does not apply for contention free beam failure recovery (CF-BFR) (see BeamFailureRecoveryConfig ). | +| msg3-transformPrecoder
Enables the transform precoder for Msg3 transmission according to clause 6.1.3 of TS 38.214 [19]. If the field is absent, the UE disables the transformer precoder (see TS 38.213 [13], clause 8.3). | +| numberOfRA-PreamblesGroupA
The number of CB preambles per SSB in group A. This determines implicitly the number of CB preambles per SSB available in group B. (see TS 38.321 [3], clause 5.1.1). The setting should be consistent with the setting of ssb-perRACH-OccasionAndCB-PreamblesPerSSB . | +| prach-RootSequenceIndex
PRACH root sequence index (see TS 38.211 [16], clause 6.3.3.1). The value range depends on whether $L=839$ or $L=139$ or $L=571$ or $L=1151$ . The length of the root sequence corresponding with the index indicated in this IE should be consistent with the one indicated in prach-ConfigurationIndex in the RACH-ConfigDedicated (if configured). If prach-RootSequenceIndex-r16 is signalled, UE shall ignore the prach-RootSequenceIndex (without suffix).
For FR2-2, only the following values are applicable depending on the used subcarrier spacing:
120 kHz: $L=139$ , $L=571$ , and $L=1151$
480 kHz: $L=139$ , and $L=571$
960 kHz: $L=139$ | +| ra-ContentionResolutionTimer
The initial value for the contention resolution timer (see TS 38.321 [3], clause 5.1.5). Value sf8 corresponds to 8 subframes, value sf16 corresponds to 16 subframes, and so on. | +| ra-Msg3SizeGroupA
Transport Blocks size threshold in bits below which the UE shall use a contention-based RA preamble of group A (see TS 38.321 [3], clause 5.1.2). This field is set to the same value for different repetition numbers associated with a specific FeatureCombination . | +| ra-Prioritization
Parameters which apply for prioritized random access procedure on any UL BWP of SpCell for specific Access Identities (see TS 38.321 [3], clause 5.1.1a). | +| ra-PrioritizationForAI
Indicates whether the field ra-Prioritization-r16 applies for Access Identities. The first/leftmost bit corresponds to Access Identity 1, the next bit corresponds to Access Identity 2. Value 1 indicates that the field ra-Prioritization-r16 applies otherwise the field does not apply (see TS 23.501 [32]). | +| ra-PrioritizationForSlicing
Parameters which apply to configure prioritized CBRA 4-step random access type for slicing. | +| rach-ConfigGeneric
RACH parameters for both regular random access and beam failure recovery. | + +| | | +|--------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| restrictedSetConfig | Configuration of an unrestricted set or one of two types of restricted sets, see TS 38.211 [16], clause 6.3.3.1. | +| rsrp-ThresholdSSB | UE may select the SS block and corresponding PRACH resource for path-loss estimation and (re)transmission based on SS blocks that satisfy the threshold (see TS 38.213 [13]). | +| rsrp-ThresholdSSB-SUL | The UE selects SUL carrier to perform random access based on this threshold (see TS 38.321 [3], clause 5.1.1). The value applies to all the BWPs and all RACH configurations. | +| ssb-perRACH-OccasionAndCB-PreamblesPerSSB | The meaning of this field is twofold: the CHOICE conveys the information about the number of SSBs per RACH occasion. Value oneEighth corresponds to one SSB associated with 8 RACH occasions, value oneFourth corresponds to one SSB associated with 4 RACH occasions, and so on. The ENUMERATED part indicates the number of Contention Based preambles per SSB. Value n4 corresponds to 4 Contention Based preambles per SSB, value n8 corresponds to 8 Contention Based preambles per SSB, and so on. The total number of CB preambles in a RACH occasion is given by CB-preambles-per-SSB * max(1, SSB-per-rach-occasion) . See TS 38.213 [13]. | +| totalNumberOfRA-Preambles | Total number of preambles used for contention based and contention free 4-step or 2-step random access in the RACH resources defined in RACH-ConfigCommon , excluding preambles used for other purposes (e.g. for SI request). If the field is absent, all 64 preambles are available for RA. The setting should be consistent with the setting of ssb-perRACH-OccasionAndCB-PreamblesPerSSB , i.e. it should be a multiple of the number of SSBs per RACH occasion. | + +| Conditional Presence | Explanation | +|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AdditionalRACH | The field is mandatory present if the RACH-ConfigCommon is included in an AdditionalRACH-Config . When included in initialUplinkBWP-RedCap to indicate other feature(s) than redcap and eRedCap , this field is mandatory present with at least FeatureCombinationPreambles list entries: the list entry/entries indicating only redcap or eRedCap and the other(s) indicating both redcap or eRedCap and one or multiple other feature(s) (e.g., smallData , nsag or msg3-Repetitions ). Otherwise, it is optional, Need R. | +| InitialBWP-Only | This field is optionally present, Need R, if this BWP is the initial BWP of SpCell. Otherwise, the field is absent. | +| L139 | The field is mandatory present if prach-RootSequenceIndex L=139, otherwise the field is absent, Need S. | +| SUL | The field is mandatory present in rach-ConfigCommon in initialUplinkBWP if supplementaryUplink is configured in ServingCellConfigCommonSIB or if supplementaryUplinkConfig is configured in ServingCellConfigCommon ; otherwise, the field is absent. This field is not configured in additionalRACH-Config . | + +#### – *RACH-ConfigCommonTwoStepRA* + +The IE *RACH-ConfigCommonTwoStepRA* is used to specify cell specific 2-step random-access type parameters. + +#### *RACH-ConfigCommonTwoStepRA* information element + +``` +-- ASN1START +-- TAG-RACH-CONFIGCOMMONTWOSTEPRA-START + +RACH-ConfigCommonTwoStepRA-r16 ::= + SEQUENCE { + rach-ConfigGenericTwoStepRA-r16 RACH-ConfigGenericTwoStepRA-r16, + msgA-TotalNumberOfRA-Preambles-r16 INTEGER (1..63) OPTIONAL, -- Need S + msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB-r16 CHOICE { +``` + +``` + + oneEighth ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64}, + oneFourth ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64}, + oneHalf ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64}, + one ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64}, + two ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32}, + four INTEGER (1..16), + eight INTEGER (1..8), + sixteen INTEGER (1..4) +} +msgA-CB-PreamblesPerSSB-PerSharedRO-r16 INTEGER (1..60) OPTIONAL, -- Cond 2StepOnly +msgA-SSB-SharedRO-MaskIndex-r16 INTEGER (1..15) OPTIONAL, -- Cond SharedRO +groupB-ConfiguredTwoStepRA-r16 GroupB-ConfiguredTwoStepRA-r16 OPTIONAL, -- Need S +msgA-PRACH-RootSequenceIndex-r16 CHOICE { + 1839 INTEGER (0..837), + 1139 INTEGER (0..137), + 1571 INTEGER (0..569), + 11151 INTEGER (0..1149) +} +msgA-TransMax-r16 ENUMERATED {n1, n2, n4, n6, n8, n10, n20, n50, n100, n200} OPTIONAL, -- Cond 2StepOnly +msgA-RSRP-Threshold-r16 RSRP-Range OPTIONAL, -- Need R +msgA-RSRP-ThresholdSSB-r16 RSRP-Range OPTIONAL, -- Cond 2Step4Step +msgA-SubcarrierSpacing-r16 SubcarrierSpacing OPTIONAL, -- Need R +2StepOnlyL139 +msgA-RestrictedSetConfig-r16 ENUMERATED {unrestrictedSet, restrictedSetTypeA, + restrictedSetTypeB} OPTIONAL, -- Cond 2StepOnly +ra-PrioritizationForAccessIdentityTwoStep-r16 SEQUENCE { + ra-Prioritization-r16 + ra-PrioritizationForAI-r16 +} +InitialBWP-Only +ra-ContentionResolutionTimer-r16 ENUMERATED {sf8, sf16, sf24, sf32, sf40, sf48, sf56, sf64} OPTIONAL, -- Cond 2StepOnly +... +[[ +ra-PrioritizationForSlicingTwoStep-r17 RA-PrioritizationForSlicing-r17 OPTIONAL, -- Cond InitialBWP-Only +featureCombinationPreamblesList-r17 SEQUENCE (SIZE(1..maxFeatureCombPreamblesPerRACHResource-r17)) OF FeatureCombinationPreambles-r17 OPTIONAL +-- Cond AdditionalRACH +]] +} +GroupB-ConfiguredTwoStepRA-r16 ::= +ra-MsgA-SizeGroupA-r16 SEQUENCE { + messagePowerOffsetGroupB-r16 ENUMERATED {b56, b144, b208, b256, b282, b480, b640, b800, + b1000, b72, spare6, spare5, spare4, spare3, spare2, spare1}, + numberOfRA-PreamblesGroupA-r16 INTEGER (1..64) +} +-- TAG-RACH-CONFIGCOMMONTWOSTEPRA-STOP +-- ASN1STOP + +``` + +| RACH-ConfigCommonTwoStepRA field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| featureCombinationPreamblesList
Specifies a series of preamble partitions each associated to a combination of features and 2-step RA. The network does not configure this list to have more than 16 entries. | +| groupB-ConfiguredTwoStepRA
Preamble grouping for 2-step random access type. If the field is absent then there is only one preamble group configured and only one msgA PUSCH configuration. | +| msgA-CB-PreamblesPerSSB-PerSharedRO
Number of contention-based preambles used for 2-step RA type from the non-CBRA 4-step type preambles associated with each SSB for RO shared with 4-step type RA. The number of preambles for 2-step RA type shall not exceed the number of preambles per SSB minus the number of contention-based preambles per SSB for 4-step type RA. The possible value range for this parameter needs to be aligned with value range for the configured SSBs per RACH occasion in ssb-perRACH-OccasionAndCB-PreamblesPerSSB in RACH-ConfigCommon . The field is only applicable for the case of shared ROs with 4-step type random access. | +| msgA-PRACH-RootSequenceIndex
PRACH root sequence index. If the field is not configured in RACH-ConfigCommonTwoStepRA which is configured directly within a BWP (i.e., not within AdditionalRACH-Config ), the UE applies the value in field prach-RootSequenceIndex in RACH-ConfigCommon in the configured BWP. If the field is absent in RACH-ConfigCommonTwoStepRA in AdditionalRACH-Config , the UE applies the corresponding value of prach-RootSequenceIndex in RACH-ConfigCommon in the same AdditionalRACH-Config . When both 2-step and 4-step type random access is configured, this field is only configured for the case of separate ROs between 2-step and 4-step type random access.
For FR2-2, only the following values are applicable depending on the used subcarrier spacing:
120 kHz: L=139, L=571, and L=1151
480 kHz: L=139, and L=571
960 kHz: L=139 | +| msgA-RestrictedSetConfig
Configuration of an unrestricted set or one of two types of restricted sets for 2-step random access type preamble. If the field is not configured in RACH-ConfigCommonTwoStepRA which is configured directly within a BWP (i.e. not within AdditionalRACH-Config ), the UE applies the value in field restrictedSetConfig in RACH-ConfigCommon in the configured BWP. If the field is absent in RACH-ConfigCommonTwoStepRA in AdditionalRACH-Config , the UE applies the value of restrictedSetConfig in RACH-ConfigCommon in the same AdditionalRACH-Config . When both 2-step and 4-step type random access is configured, this field is only configured for the case of separate ROs between 2-step and 4-step type random access. | +| msgA-RSRP-Threshold
The UE selects 2-step random access type to perform random access based on this threshold (see TS 38.321 [3], clause 5.1.1). This field is only present if both 2-step and 4-step RA type are configured for the BWP. | +| msgA-RSRP-ThresholdSSB
UE may select the SS block and corresponding PRACH resource for path-loss estimation and (re)transmission based on SS blocks that satisfy the threshold (see TS 38.213 [13]). | +| msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB
The meaning of this field is twofold: the CHOICE conveys the information about the number of SSBs per RACH occasion. Value oneEight corresponds to one SSB associated with 8 RACH occasions, value oneFourth corresponds to one SSB associated with 4 RACH occasions, and so on. The ENUMERATED part indicates the number of Contention Based preambles per SSB. Value n4 corresponds to 4 Contention Based preambles per SSB, value n8 corresponds to 8 Contention Based preambles per SSB, and so on. The total number of CB preambles in a RACH occasion is given by CB-preambles-per-SSB * max(1, SSB-per-rach-occasion ). If the field is not configured in RACH-ConfigCommonTwoStepRA which is configured directly within a BWP (i.e. not within AdditionalRACH-Config ) and both 2-step and 4-step are configured for the BWP, the UE applies the value in the field ssb-perRACH-OccasionAndCB-PreamblesPerSSB in RACH-ConfigCommon . If the field is not configured in AdditionalRACH-Config and both 2-step and 4-step are configured in AdditionalRACH-Config , the UE applies the value in the field ssb-perRACH-OccasionAndCB-PreamblesPerSSB in RACH-ConfigCommon in the same AdditionalRACH-Config . The field is not present when RACH occasions are shared between 2-step and 4-step type random access in the BWP. | +| msgA-SSB-SharedRO-MaskIndex
Indicates the subset of 4-step type ROs shared with 2-step random access type for each SSB. This field is configured when there is more than one RO per SSB. If the field is absent, and 4-step and 2-step has shared ROs, then all ROs are shared. | + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

msgA-SubcarrierSpacing
Subcarrier spacing of PRACH (see TS 38.211 [16], clause 5.3.2).
Only the following values are applicable depending on the used frequency:
FR1: 15 or 30 kHz
FR2-1: 60 or 120 kHz
FR2-2: 120, 480, or 960 kHz.
If the field is absent, the UE applies the SCS as derived from the msgA-PRACH-ConfigurationIndex in RACH-ConfigGenericTwoStepRA (see tables Table 6.3.3.1-1, Table 6.3.3.1-2, Table 6.3.3.2-2 and Table 6.3.3.2-3, TS 38.211 [16]) in case of 2-step only BWP, otherwise the UE applies the same SCS as Msg1 derived from RACH-ConfigCommon. The value also applies to contention free 2-step random access type (RACH-ConfigDedicated).

| +|

msgA-TotalNumberOfRA-Preambles
Indicates the total number of preambles used for contention-based and contention-free 2-step random access type when ROs for 2-step are not shared with 4-step. If the field is absent, and 2-step and 4-step does not have shared ROs, all 64 preambles are available for 2-step random access type.

| +|

msgA-TransMax
Max number of MsgA preamble transmissions performed before switching to 4-step random access (see TS 38.321 [3], clauses 5.1.1). This field is only applicable when 2-step and 4-step RA type are configured and switching to 4-step type RA is supported. If the field is absent, switching from 2-step RA type to 4-step RA type is not allowed.

| +|

ra-ContentionResolutionTimer
The initial value for the contention resolution timer for fallback RAR in case no 4-step random access type is configured (see TS 38.321 [3], clause 5.1.5). Value sf8 corresponds to 8 subframes, value sf16 corresponds to 16 subframes, and so on. If both 2-step and 4-step random access type resources are configured on the BWP, then this field is absent. If the field is absent in RACH-ConfigCommonTwoStepRA in AdditionalRACH-Config, the UE shall apply the corresponding value in RACH-ConfigCommon in the same AdditionalRACH-Config.

| +|

ra-Prioritization
Parameters which apply for prioritized random access procedure on any UL BWP of SpCell for specific Access Identities (see TS 38.321 [3], clause 5.1.1a).

| +|

ra-PrioritizationForAI
Indicates whether the field ra-Prioritization-r16 applies for Access Identities. The first/leftmost bit corresponds to Access Identity 1, the next bit corresponds to Access Identity 2. Value 1 for an Access Identity indicates that the field ra-Prioritization-r16 applies, otherwise the field does not apply.

| +|

ra-PrioritizationForSlicingTwoStep
Parameters which apply to configure prioritized CBRA 2-step random access type for slicing.

| +|

rach-ConfigGenericTwoStepRA
2-step random access type parameters for both regular random access and beam failure recovery.

| + +| GroupB-ConfiguredTwoStepRA field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

messagePowerOffsetGroupB
Threshold for preamble selection. Value is in dB. Value minusinfinity corresponds to -\infty. Value dB0 corresponds to 0 dB, dB5 corresponds to 5 dB and so on. (see TS 38.321 [3], clause 5.1.1).

| +|

numberOfRA-PreamblesGroupA
The number of CB preambles per SSB in group A for idle/inactive or connected mode. The setting of the number of preambles for each group should be consistent with msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB or msgA-CB-PreamblesPerSSB-PerSharedRO if configured.

| +|

ra-MsgA-SizeGroupA
Transport block size threshold in bits below which the UE shall use a contention-based RA preamble of group A. (see TS 38.321 [3], clause 5.1.1).

| + +| Conditional Presence | Explanation | +|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 2Step4Step | The field is mandatory present if both 2-step random access type and 4-step random access type are configured in the BWP, otherwise the field is not present.
The field is mandatory present in msgA-ConfigCommon field in AdditionalRACH-Config if both 2-step random access type and 4-step random access type are configured for the same feature combination in the BWP. | +| 2StepOnlyL139 | The field is mandatory present if msgA-PRACH-RootSequenceIndex L=139 and no 4-step random access type is configured, otherwise the field is absent, Need S. | +| 2StepOnly | The field is mandatory present in msgA-ConfigCommon field in BWP-UplinkCommon if rach-ConfigCommon field is absent in this BWP-UplinkCommon , otherwise the field is optionally present in msgA-ConfigCommon field in BWP-UplinkCommon , Need S.
The field is mandatory present in msgA-ConfigCommon field in AdditionalRACH-Config if rach-ConfigCommon field is absent in this AdditionalRACH-Config , otherwise the field is optionally present in msgA-ConfigCommon field in AdditionalRACH-Config , Need S. | +| AdditionalRACH | The field is mandatory present if the msgA-ConfigCommon is included in an AdditionalRACH-Config . When included in initialUplinkBWP-RedCap to indicate other feature(s) than redcap , this field is mandatory present with at least two FeatureCombinationPreambles list entries: one list entry indicating only redcap and the other(s) indicating both redcap and one or multiple other feature(s) (e.g. smallData , nsag or msg3-Repetitions ).
Otherwise, it is optional, Need R. | +| InitialBWP-Only | This field is optionally present, Need R, if this BWP is the initial BWP of SpCell. Otherwise, the field is absent. | +| SharedRO | The field is mandatory present if the 2-step random access type occasions are shared with 4-step random access type, otherwise the field is not present. | + +#### – *RACH-ConfigDedicated* + +The IE *RACH-ConfigDedicated* is used to specify the dedicated random access parameters. + +#### *RACH-ConfigDedicated* information element + +``` +-- ASN1START +-- TAG-RACH-CONFIGDEDICATED-START + +RACH-ConfigDedicated ::= SEQUENCE { + cfra CFRA OPTIONAL, -- Need S + ra-Prioritization RA-Prioritization OPTIONAL, -- Need N + ... + [[ + ra-PrioritizationTwoStep-r16 RA-Prioritization + cfra-TwoStep-r16 CFRA-TwoStep-r16 + ]] +} + +CFRA ::= SEQUENCE { + occasions SEQUENCE { + rach-ConfigGeneric RACH-ConfigGeneric, +``` + +``` + + ssb-perRACH-Occasion ENUMERATED {oneEighth, oneFourth, oneHalf, one, two, four, eight, sixteen} + OPTIONAL -- Cond Mandatory + } OPTIONAL, -- Need S + resources CHOICE { + ssb SEQUENCE { + ssb-ResourceList SEQUENCE (SIZE(1..maxRA-SSB-Resources)) OF CFRA-SSB-Resource, + ra-ssb-OccasionMaskIndex INTEGER (0..15) + }, + csirs SEQUENCE { + csirs-ResourceList SEQUENCE (SIZE(1..maxRA-CSIRS-Resources)) OF CFRA-CSIRS-Resource, + rsrp-ThresholdCSI-RS RSRP-Range + } + }, + ... + [[ + totalNumberOfRA-Preambles INTEGER (1..63) + OPTIONAL -- Cond Occasions + ]], + [[ + msg1-RepetitionNum-r18 ENUMERATED {n2, n4, n8} + OPTIONAL -- Cond 4StepCFRArep + ]] +} + +CFRA-TwoStep-r16 ::= SEQUENCE { + occasionsTwoStepRA-r16 SEQUENCE { + rach-ConfigGenericTwoStepRA-r16 RACH-ConfigGenericTwoStepRA-r16, + ssb-PerRACH-OccasionTwoStepRA-r16 ENUMERATED {oneEighth, oneFourth, oneHalf, one, + two, four, eight, sixteen} + } + OPTIONAL, -- Need S + msgA-CFRA-PUSCH-r16 MsgA-PUSCH-Resource-r16, + msgA-TransMax-r16 ENUMERATED {n1, n2, n4, n6, n8, n10, n20, n50, n100, n200} OPTIONAL, -- Need S + resourcesTwoStep-r16 SEQUENCE { + ssb-ResourceList SEQUENCE (SIZE(1..maxRA-SSB-Resources)) OF CFRA-SSB-Resource, + ra-ssb-OccasionMaskIndex INTEGER (0..15) + }, + ... +} + +CFRA-SSB-Resource ::= SEQUENCE { + ssb SSB-Index, + ra-PreambleIndex INTEGER (0..63), + ... + [[ + msgA-PUSCH-Resource-Index-r16 INTEGER (0..3071) OPTIONAL -- Cond 2StepCFRA + ]] +} + +CFRA-CSIRS-Resource ::= SEQUENCE { + csi-RS CSI-RS-Index, + ra-OccasionList SEQUENCE (SIZE(1..maxRA-OccasionsPerCSIRS)) OF INTEGER (0..maxRA-Occasions-1), + ra-PreambleIndex INTEGER (0..63), + +``` + +``` + + ... +} + +-- TAG-RACH-CONFIGDEDICATED-STOP +-- ASN1STOP + +``` + +| CFRA-CSI-RS-Resource field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| csi-RS
The ID of a CSI-RS resource defined in the measurement object associated with this serving cell. | +| ra-OccasionList
RA occasions that the UE shall use when performing CF-RA upon selecting the candidate beam identified by this CSI-RS. The network ensures that the RA occasion indexes provided herein are also configured by prach-ConfigurationIndex and msg1-FDM. Each RACH occasion is sequentially numbered, 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 and Third, in increasing order of indexes for PRACH slots. | +| ra-PreambleIndex
The RA preamble index to use in the RA occasions associated with this CSI-RS. | + +| CFRA field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| msg1-RepetitionNum
Indicates the MSG1 repetition number used for contention free 4-step random access type in TS 38.321 [3]. If this field is absent, the UE performs contention free 4-step random access without MSG1-Repetitions. | +| occasions
RA occasions for contention free random access. If the field is absent, the UE uses the RA occasions configured in RACH-ConfigCommon in the first active UL BWP. | +| ra-ssb-OccasionMaskIndex
Explicitly signalled PRACH Mask Index for RA Resource selection in TS 38.321 [3]. The mask is valid for all SSB resources signalled in ssb-ResourceList . | +| rach-ConfigGeneric
Configuration of contention free random access occasions for CFRA. The UE shall ignore preambleReceivedTargetPower , preambleTransMax , powerRampingStep , ra-ResponseWindow signaled within this field and use the corresponding values provided in RACH-ConfigCommon . | +| ssb-perRACH-Occasion
Number of SSBs per RACH occasion. | +| totalNumberOfRA-Preambles
Total number of preambles used for contention free random access in the RACH resources defined in CFRA, excluding preambles used for other purposes (e.g. for SI request). If the field is absent but the field occasions is present, the UE may assume all the 64 preambles are for RA. The setting should be consistent with the setting of ssb-perRACH-Occasion , if present, i.e. it should be a multiple of the number of SSBs per RACH occasion. | + +| CFRA-SSB-Resource field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| msgA-PUSCH-Resource-Index
Identifies the index of the PUSCH resource used for MSGA CFRA. The PUSCH resource index indicates a valid PUSCH occasion (as specified in TS 38.213 [13], clause 8.1A) and the associated DMRS resources corresponding to a PRACH slot. The PUSCH resource indexes are sequentially numbered and are mapped to valid PUSCH occasions corresponding to a PRACH slot which are ordered, 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 DMR resource index is determined first in an ascending order of a DMRS port index and then in an ascending order of a DMRS sequence index, third in increasing order of time resource indexes for time multiplexed PUSCH occasions within a PUSCH slot and fourth, in increasing order of indexes for PUSCH slots. For the case of contention free 2-step random access type, if this field is absent, the UE shall use the value 0. | +| ra-PreambleIndex
The preamble index that the UE shall use when performing CF-RA upon selecting the candidate beams identified by this SSB. | +| ssb
The ID of an SSB transmitted by this serving cell. | + +| CFRA-TwoStep field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| msgA-CFRA-PUSCH
PUSCH resource configuration(s) for msgA CFRA. | +| msgA-TransMax
Max number of MsgA preamble transmissions performed before switching to 4-step type random access (see TS 38.321 [3], clauses 5.1.1). This field is only applicable when 2-step and 4-step RA type are configured and switching to 4-step type RA is supported. If the field is absent in cfra-TwoStep , switching from 2-step RA type to 4-step RA type is not allowed. | +| occasionsTwoStepRA
RA occasions for contention free random access. If the field is absent, the UE uses the RA occasions configured in RACH-ConfigCommonTwoStepRA in the first active UL BWP. | +| ra-SSB-OccasionMaskIndex
Explicitly signalled PRACH Mask Index for RA Resource selection in TS 38.321 [3]. The mask is valid for all SSB resources signalled in ssb-ResourceList . | +| rach-ConfigGenericTwoStepRA
Configuration of contention free random access occasions for CFRA 2-step random access type. | +| ssb-PerRACH-OccasionTwoStep
Number of SSBs per RACH occasion for 2-step random access type. | + +| RACH-ConfigDedicated field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| cfra
Parameters for contention free random access to a given target cell. If this field and cfra-TwoStep are absent, the UE performs contention based random access. | +| cfra-TwoStep
Parameters for contention free 2-step random access type to a given target cell. Network ensures that cfra and cfra-TwoStep are not configured at the same time. If this field and cfra are absent, the UE performs contention based random access. This field may only be present if msgA-ConfigCommon is configured on the BWP. | +| ra-prioritization
Parameters which apply for prioritized random access procedure to a given target cell (see TS 38.321 [3], clause 5.1.1). | +| ra-PrioritizationTwoStep
Parameters which apply for prioritized 2-step random access type procedure to a given target cell (see TS 38.321 [3], clause 5.1.1). | + +| Conditional Presence | Explanation | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Mandatory | The field is mandatory present. | +| Occasions | The field is optionally present, Need S, if the field occasions is present, otherwise it is absent. | +| 2StepCFRA | The field is optionally present for the case of 2-step RA type contention free random access, Need S, otherwise it is absent. | +| 4StepCFRArep | For non-RedCap UEs, the field is optionally present, Need S, if resources is set to ssb and there is one FeatureCombinationPreambles entry indicating only msg1-Repetitions which is associated with the same Msg1 repetition number.
For RedCap UEs, the field is optionally present, Need S, if resources is set to ssb and there is one FeatureCombinationPreambles entry indicating only redCap and msg1-Repetitions which is associated with the same Msg1 repetition number.
Otherwise, it is absent. | + +#### – *RACH-ConfigGeneric* + +The IE *RACH-ConfigGeneric* is used to specify the random-access parameters both for regular random access as well as for beam failure recovery. + +#### *RACH-ConfigGeneric* information element + +``` +-- ASN1START +-- TAG-RACH-CONFIGGENERIC-START + +RACH-ConfigGeneric ::= SEQUENCE { + prach-ConfigurationIndex INTEGER (0..255), + msg1-FDM ENUMERATED {one, two, four, eight}, + msg1-FrequencyStart INTEGER (0..maxNrofPhysicalResourceBlocks-1), + zeroCorrelationZoneConfig INTEGER (0..15), + preambleReceivedTargetPower INTEGER (-202..-60), + preambleTransMax ENUMERATED {n3, n4, n5, n6, n7, n8, n10, n20, n50, n100, n200}, + powerRampingStep ENUMERATED {dB0, dB2, dB4, dB6}, + ra-ResponseWindow ENUMERATED {sl1, sl2, sl4, sl8, sl10, sl12, sl14, sl16, sl18}, + ... + [[ + prach-ConfigurationPeriodScaling-IAB-r16 ENUMERATED {scf1, scf2, scf4, scf8, scf16, scf32, scf64} OPTIONAL, -- Need R + prach-ConfigurationFrameOffset-IAB-r16 INTEGER (0..63) OPTIONAL, -- Need R + prach-ConfigurationSOffset-IAB-r16 INTEGER (0..39) OPTIONAL, -- Need R + ra-ResponseWindow-v1610 ENUMERATED { sl160, sl160} OPTIONAL, -- Need R + prach-ConfigurationIndex-v1610 INTEGER (256..262) OPTIONAL -- Need R + ]], + [[ + ra-ResponseWindow-v1700 ENUMERATED {sl1240, sl1320, sl1640, sl1960, sl1280, sl1920, sl2560} OPTIONAL -- Need R + ]] +} + +-- TAG-RACH-CONFIGGENERIC-STOP +-- ASN1STOP +``` + +| RACH-ConfigGeneric field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| msg1-FDM
The number of PRACH transmission occasions FDMed in one time instance. (see TS 38.211 [16], clause 6.3.3.2). | +| msg1-FrequencyStart
Offset of lowest PRACH transmission occasion in frequency domain with respective to PRB 0. The value is configured so that the corresponding RACH resource is entirely within the bandwidth of the UL BWP. (see TS 38.211 [16], clause 6.3.3.2). | +| powerRampingStep
Power ramping steps for PRACH (see TS 38.321 [3], 5.1.3). This field is set to the same value for different repetition numbers associated with a specific FeatureCombination . | +| prach-ConfigurationFrameOffset-IAB
Frame offset for ROs defined in the baseline configuration indicated by prach-ConfigurationIndex and is used only by the IAB-MT. (see TS 38.211 [16], clause 6.3.3.2). | +| prach-ConfigurationIndex
PRACH configuration index. For prach-ConfigurationIndex configured under beamFailureRecoveryConfig , the prach-ConfigurationIndex can only correspond to the short preamble format, (see TS 38.211 [16], clause 6.3.3.2). If the field prach-ConfigurationIndex-v1610 is present, the UE shall ignore the value provided in prach-ConfigurationIndex (without suffix). | +| prach-ConfigurationPeriodScaling-IAB
Scaling factor to extend the periodicity of the baseline configuration indicated by prach-ConfigurationIndex and is used only by the IAB-MT. Value scf1 corresponds to scaling factor of 1 and so on. (see TS 38.211 [16], clause 6.3.3.2). | +| prach-ConfigurationSOffset-IAB
Subframe/Slot offset for ROs defined in the baseline configuration indicated by prach-ConfigurationIndex and is used only by the IAB-MT. (see TS 38.211 [16], clause 6.3.3.2). | +| preambleReceivedTargetPower
The target power level at the network receiver side (see TS 38.213 [13], clause 7.4, TS 38.321 [3], clauses 5.1.2, 5.1.3). Only multiples of 2 dBm may be chosen (e.g. -202, -200, -198, ...). This field is set to the same value for different repetition numbers associated with a specific FeatureCombination . | +| preambleTransMax
Max number of RA preamble transmission performed before declaring a failure (see TS 38.321 [3], clauses 5.1.4, 5.1.5). | +| ra-ResponseWindow
Msg2 (RAR) window length in number of slots. The network configures a value lower than or equal to 10 ms when Msg2 is transmitted in licensed spectrum and a value lower than or equal to 40 ms when Msg2 is transmitted with shared spectrum channel access (see TS 38.321 [3], clause 5.1.4). UE ignores the field if included in SCellConfig . If ra-ResponseWindow-v1610 or ra-ResponseWindow-v1700 is signalled, UE shall ignore the ra-ResponseWindow (without suffix). The field ra-ResponseWindow-v1700 is applicable to SCS 480 kHz and SCS 960 kHz. | +| zeroCorrelationZoneConfig
N-CS configuration, see Table 6.3.3.1-5 in TS 38.211 [16]. | + +#### – RACH-ConfigGenericTwoStepRA + +The IE *RACH-ConfigGenericTwoStepRA* is used to specify the 2-step random access type parameters. + +#### RACH-ConfigGenericTwoStepRA information element + +``` +-- ASN1START +-- TAG-RACH-CONFIGGENERICTWOSTEPRA-START + +RACH-ConfigGenericTwoStepRA-r16 ::= SEQUENCE { + msgA-PRACH-ConfigurationIndex-r16 INTEGER (0..262) OPTIONAL, -- Cond 2StepOnly +``` + +``` + +msgA-RO-FDM-r16 ENUMERATED {one, two, four, eight} OPTIONAL, -- Cond 2StepOnly +msgA-RO-FrequencyStart-r16 INTEGER (0..maxNrofPhysicalResourceBlocks-1) OPTIONAL, -- Cond 2StepOnly +msgA-ZeroCorrelationZoneConfig-r16 INTEGER (0..15) OPTIONAL, -- Cond 2StepOnly +msgA-PreamblePowerRampingStep-r16 ENUMERATED {dB0, dB2, dB4, dB6} OPTIONAL, -- Cond 2StepOnlyNoCFRA +msgA-PreambleReceivedTargetPower-r16 INTEGER (-202..-60) OPTIONAL, -- Cond 2StepOnlyNoCFRA +msgB-ResponseWindow-r16 ENUMERATED {sl1, sl2, sl4, sl8, sl10, sl20, sl40, sl80, sl160, sl320} + OPTIONAL, -- Cond NoCFRA +preambleTransMax-r16 ENUMERATED {n3, n4, n5, n6, n7, n8, n10, n20, n50, n100, n200} OPTIONAL, -- Cond 2StepOnlyNoCFRA +... +[[ +msgB-ResponseWindow-v1700 ENUMERATED {sl240, sl640, sl960, sl1280, sl1920, sl2560} OPTIONAL -- Cond NoCFRA2 +]] +} + +-- TAG-RACH-CONFIGGENERIC2STEPRA-STOP +-- ASN1STOP + +``` + +| RACH-ConfigGenericTwoStepRA field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

msgA-PreamblePowerRampingStep
Power ramping steps for msgA PRACH. If the field is absent in RACH-ConfigCommonTwoStepRA in AdditionalRACH-Config, the UE shall apply the corresponding value in RACH-ConfigCommon in the same AdditionalRACH-Config. If the field is absent in other cases, UE shall use the value of powerRampingStep in RACH-ConfigGeneric in the configured BWP (see TS 38.321 [3], 5.1.3). This field may only be present if no 4-step type RA is configured in the BWP or in the case of separate ROs with 4-step type RA. The field is absent if RACH-ConfigGenericTwoStepRA is included in CFRA-TwoStep in RACH-ConfigDedicated and then the UE uses the value of msgA-PreamblePowerRampingStep in RACH-ConfigGenericTwoStepRA configured for CBRA.

| +|

msgA-PreambleReceivedTargetPower
The target power level at the network receiver side (see TS 38.213 [13], clause 7.1.1 and TS 38.321 [3], clause 5.1.1). Only multiples of 2 dBm may be chosen (e.g -202, -200, -198, ...). If the field is absent, UE shall use the value of preambleReceivedTargetPower in RACH-ConfigGeneric in the configured BWP. This field may only be present if no 4-step type RA is configured in the BWP. The field is absent if RACH-ConfigGenericTwoStepRA is included in CFRA-TwoStep in RACH-ConfigDedicated and then the UE uses the value of msgA-PreambleReceivedTargetPower in RACH-ConfigGenericTwoStepRA configured for CBRA.

| +|

msgA-PRACH-ConfigurationIndex
Cell-specific PRACH configuration index for 2-step RA type. If the field is absent in RACH-ConfigCommonTwoStepRA which is configured directly within a BWP (i.e. not within AdditionalRACH-Config), the UE shall use the value of corresponding 4-step random access parameter in the configured BWP. If the field is absent in RACH-ConfigCommonTwoStepRA in AdditionalRACH-Config, the UE shall apply the corresponding value in RACH-ConfigCommon in the same AdditionalRACH-Config. If the value is in the range of 256 to 262, the field prach-ConfigurationIndex-v1610 should be considered configured (see TS 38.211 [16], clause 6.3.3.2). This field may only be present if no 4-step type RA is configured in the BWP or in the case of separate ROs with 4-step type RA.

| +|

msgA-RO-FDM
The number of msgA PRACH transmission occasions Frequency-Division Multiplexed in one time instance. If the field is absent in RACH-ConfigCommonTwoStepRA which is configured directly within a BWP (i.e. not within AdditionalRACH-Config), UE shall use value of msg1-FDM in RACH-ConfigGeneric in the configured BWP. If the field is absent in RACH-ConfigCommonTwoStepRA in AdditionalRACH-Config, the UE shall apply the value of msg1-FDM in RACH-ConfigCommon in the same AdditionalRACH-Config (see TS 38.211 [16], clause 6.3.3.2). This field may only be present if no 4-step type RA is configured in the BWP or in the case of separate ROs with 4-step type RA.

| +|

msgA-RO-FrequencyStart
Offset of lowest PRACH transmissions occasion in frequency domain with respect to PRB 0. If the field is absent in RACH-ConfigCommonTwoStepRA which is configured directly within a BWP (i.e. not within AdditionalRACH-Config), UE shall use value of msg1-FrequencyStart in RACH-ConfigGeneric in the configured BWP. If the field is absent in RACH-ConfigCommonTwoStepRA in AdditionalRACH-Config, the UE shall apply the value of msg1-FrequencyStart in RACH-ConfigCommon in the same AdditionalRACH-Config (see TS 38.211 [16], clauses 5.3.2 and 6.3.3.2). This field may only be present if no 4-step type RA is configured in the BWP or in the case of separate ROs with 4-step type RA.

| +|

msgA-ZeroCorrelationZoneConfig
N-CS configuration for msgA preamble, see Table 6.3.3.1-5 in TS 38.211 [16]. If the field is absent in RACH-ConfigCommonTwoStepRA in AdditionalRACH-Config, the UE shall apply the corresponding value in RACH-ConfigCommon in the same AdditionalRACH-Config. If the field is absent in other cases, UE shall use value zeroCorrelationZoneConfig in RACH-ConfigGeneric in the configured BWP. This field may only be present if no 4-step type RA is configured in the BWP or in the case of separate ROs with 4-step type RA.

| +|

msgB-ResponseWindow
MsgB monitoring window length in number of slots. The network configures a value lower than or equal to 40ms (see TS 38.321 [3], clause 5.1.1). The network does not configure msgB-ResponseWindow-r16 simultaneously with msgB-ResponseWindow-v1700, and if both fields are absent, the UE uses the value of msgB-ResponseWindow in RACH-ConfigGenericTwoStepRA configured for CBRA.

| +|

preambleTransMax
Max number of RA preamble transmission performed before declaring a failure (see TS 38.321 [3], clauses 5.1.4, 5.1.5). If the field is absent in RACH-ConfigCommonTwoStepRA in AdditionalRACH-Config, the UE shall apply the corresponding value in RACH-ConfigCommon in the same AdditionalRACH-Config. If the field is absent in other cases, UE shall use the value of preambleTransMax in RACH-ConfigGeneric in the configured BWP. The field is absent if RACH-ConfigGenericTwoStepRA is included in CFRA-TwoStep in RACH-ConfigDedicated and then the UE uses the value of preambleTransMax in RACH-ConfigGenericTwoStepRA configured for CBRA.

| + +| Conditional Presence | Explanation | +|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 2StepOnly | The field is mandatory present in msgA-ConfigCommon field in BWP-UplinkCommon if rach-ConfigCommon field is absent in this BWP-UplinkCommon , otherwise the field is optionally present in msgA-ConfigCommon field in BWP-UplinkCommon , Need S.
The field is mandatory present in msgA-ConfigCommon in AdditionalRACH-Config if rach-ConfigCommon field is absent in this AdditionalRACH-Config , otherwise the field is optionally present in msgA-ConfigCommon field in AdditionalRACH-Config , Need S. | +| 2StepOnlyNoCFRA | The field is mandatory present if RACH-ConfigGenericTwoStepRA is included in the RACH-ConfigCommonTwoStepRA and there are no 4-step random access configurations configured in the BWP (i.e only 2-step random access type configured in the BWP), otherwise (i.e. 4-step random access configuration also exists in the BWP) the field is optionally present, Need S. When RACH-ConfigGenericTwoStepRA is included in the RACH-ConfigDedicated , this field is absent. | +| NoCFRA | The field is mandatory present if msgB-ResponseWindow-r17 is absent and RACH-ConfigGenericTwoStepRA is not included in CFRA-TwoStep in RACH-ConfigDedicated , otherwise the field is absent, Need S. | +| NoCFRA2 | The field is mandatory present if msgB-ResponseWindow-r16 is absent and RACH-ConfigGenericTwoStepRA is not included in CFRA-TwoStep in RACH-ConfigDedicated , otherwise the field is absent, Need S. | + +#### – *RACH-ConfigTwoTA* + +The IE *RACH-ConfigTwoTA* is used to specify random access parameters for each additional PCI configured for the serving cell. + +#### *RACH-ConfigTwoTA* information element + +``` +-- ASN1START +-- TAG-RACH-CONFIGTWOTA-START + +RACH-ConfigTwoTA-r18 ::= SEQUENCE { + rach-ConfigTwoTAIndex-r18 RACH-ConfigTwoTAIndex-r18, + additionalPCIIndex-r18 AdditionalPCIIndex-r17, + rach-ConfigGeneric-r18 RACH-ConfigGeneric, + ssb-perRACH-Occasion-r18 ENUMERATED {oneEighth, oneFourth, oneHalf, one, two, four, eight, sixteen} OPTIONAL, -- Need R + prach-RootSequenceIndex-r18 CHOICE { + 1839 INTEGER (0..837), + 1139 INTEGER (0..137) + } + msg1-SubcarrierSpacing-r18 SubcarrierSpacing + ... +} + +RACH-ConfigTwoTAIndex-r18 ::= INTEGER (1.. maxNrofAdditionalPRACHConfigs-r18) + +-- TAG-RACH-CONFIGTWOTA-STOP +-- ASN1STOP +``` + +| RACH-ConfigTwoTA field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| msg1-SubcarrierSpacing
Subcarrier spacing of PRACH when prach-RootSequenceIndex has value set to 1139 (see TS 38.211 [16], clause 5.3.2). | +| prach-RootSequenceIndex
PRACH root sequence index (see TS 38.211 [16], clause 6.3.3.1). The value range depends on whether L=839 or L=139. If prach-RootSequenceIndex-r18 is signalled, UE shall ignore the prach-RootSequenceIndex (without suffix).
For FR2-2, only the following values are applicable depending on the used subcarrier spacing:
120 kHz: L=139, L=571, and L=1151
480 kHz: L=139, and L=571
960 kHz: L=139 | +| rach-ConfigGeneric
RACH parameters for for contention free random access occasions for CFRA. | +| ssb-perRACH-Occasion
Number of SSBs per RACH occasion. | + +#### — ***RA-Prioritization*** + +The IE *RA-Prioritization* is used to configure prioritized random access. + +#### ***RA-Prioritization* information element** + +``` +-- ASN1START +-- TAG-RA-PRIORITIZATION-START + +RA-Prioritization ::= SEQUENCE { + powerRampingStepHighPriority ENUMERATED {dB0, dB2, dB4, dB6}, + scalingFactorBI ENUMERATED {zero, dot25, dot5, dot75} OPTIONAL, -- Need R + ... +} + +-- TAG-RA-PRIORITIZATION-STOP +-- ASN1STOP +``` + +| RA-Prioritization field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| powerRampingStepHighPriority
Power ramping step applied for prioritized random access procedure. | +| scalingFactorBI
Scaling factor for the backoff indicator (BI) for the prioritized random access procedure. (see TS 38.321 [3], clause 5.1.4). Value zero corresponds to 0, value dot25 corresponds to 0.25 and so on. | + +#### — *RA-PrioritizationForSlicing* + +The IE *RA-PrioritizationForSlicing* is used to configure prioritized random access for slicing. + +#### *RA-PrioritizationForSlicing* information element + +``` +-- ASN1START +-- TAG-RA-PRIORITIZATIONFORSLICING-START + +RA-PrioritizationForSlicing-r17 ::= SEQUENCE { + ra-PrioritizationSliceInfoList-r17 RA-PrioritizationSliceInfoList-r17, + ... +} + +RA-PrioritizationSliceInfoList-r17 ::= SEQUENCE (SIZE (1..maxSliceInfo-r17)) OF RA-PrioritizationSliceInfo-r17 + +RA-PrioritizationSliceInfo-r17 ::= SEQUENCE { + nsag-ID-List-r17 SEQUENCE (SIZE (1..maxSliceInfo-r17)) OF NSAG-ID-r17, + ra-Prioritization-r17 RA-Prioritization, + ... +} + +-- TAG-RA-PRIORITIZATIONFORSLICING-STOP +-- ASN1STOP +``` + +#### — *RadioBearerConfig* + +The IE *RadioBearerConfig* is used to add, modify and release signalling, multicast MRBs and/or data radio bearers. Specifically, this IE carries the parameters for PDCP and, if applicable, SDAP entities for the radio bearers. + +#### *RadioBearerConfig* information element + +``` +-- ASN1START +-- TAG-RADIOBEARERCONFIG-START + +RadioBearerConfig ::= SEQUENCE { + srb-ToAddModList SRB-ToAddModList OPTIONAL, -- Cond HO-Conn + srb3-ToRelease ENUMERATED{true} OPTIONAL, -- Need N + drb-ToAddModList DRB-ToAddModList OPTIONAL, -- Cond HO-toNR + drb-ToReleaseList DRB-ToReleaseList OPTIONAL, -- Need N + securityConfig SecurityConfig OPTIONAL, -- Need M + ... + [[ + mrb-ToAddModList-r17 MRB-ToAddModList-r17 OPTIONAL, -- Need N + mrb-ToReleaseList-r17 MRB-ToReleaseList-r17 OPTIONAL, -- Need N + srb4-ToAddMod-r17 SRB-ToAddMod OPTIONAL, -- Need N + srb4-ToRelease-r17 ENUMERATED{true} OPTIONAL, -- Need N + ]] +``` + +``` + + ]], + [[ + srb5-ToAddMod-r18 SRB-ToAddMod OPTIONAL, -- Need N + srb5-ToRelease-r18 ENUMERATED{true} OPTIONAL, -- Need N + ]] +} + +SRB-ToAddModList ::= SEQUENCE (SIZE (1..2)) OF SRB-ToAddMod + +SRB-ToAddMod ::= SEQUENCE { + srb-Identity SRB-Identity, + reestablishPDCP ENUMERATED{true} OPTIONAL, -- Need N + discardOnPDCP ENUMERATED{true} OPTIONAL, -- Need N + pdcp-Config PDCP-Config OPTIONAL, -- Cond PDCP + ..., + [[ + srb-Identity-v1700 SRB-Identity-v1700 OPTIONAL -- Need M + ]], + [[ + srb-Identity-v1800 SRB-Identity-v1800 OPTIONAL -- Need M + ]] +} + +DRB-ToAddModList ::= SEQUENCE (SIZE (1..maxDRB)) OF DRB-ToAddMod + +DRB-ToAddMod ::= SEQUENCE { + cnAssociation CHOICE { + eps-BearerIdentity INTEGER (0..15), + sdap-Config SDAP-Config + } + drb-Identity DRB-Identity, + reestablishPDCP ENUMERATED{true} OPTIONAL, -- Need N + recoverPDCP ENUMERATED{true} OPTIONAL, -- Need N + pdcp-Config PDCP-Config OPTIONAL, -- Cond PDCP + ..., + [[ + daps-Config-r16 ENUMERATED{true} OPTIONAL -- Cond DAPS + ]] +} + +DRB-ToReleaseList ::= SEQUENCE (SIZE (1..maxDRB)) OF DRB-Identity + +SecurityConfig ::= SEQUENCE { + securityAlgorithmConfig SecurityAlgorithmConfig OPTIONAL, -- Cond RBTermChange1 + keyToUse ENUMERATED{master, secondary} OPTIONAL, -- Cond RBTermChange + ... +} + +MRB-ToAddModList-r17 ::= SEQUENCE (SIZE (1..maxMRB-r17)) OF MRB-ToAddMod-r17 + +MRB-ToAddMod-r17 ::= SEQUENCE { + mbs-SessionId-r17 TMGI-r17 OPTIONAL, -- Cond MRBSetup + +``` + +``` + + mrb-Identity-r17 MRB-Identity-r17, + mrb-IdentityNew-r17 MRB-Identity-r17 OPTIONAL, -- Need N + reestablishPDCP-r17 ENUMERATED{true} OPTIONAL, -- Need N + recoverPDCP-r17 ENUMERATED{true} OPTIONAL, -- Need N + pdcp-Config-r17 PDCP-Config OPTIONAL, -- Cond PDCP + ... +} + +MRB-ToReleaseList-r17 ::= SEQUENCE (SIZE (1..maxMRB-r17)) OF MRB-Identity-r17 + +-- TAG-RADIOBEARERCONFIG-STOP +-- ASN1STOP + +``` + +#### ***DRB-ToAddMod and MRB-ToAddMod field descriptions*** + +| | | +|----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| cnAssociation | Indicates if the bearer is associated with the eps-bearerIdentity (when connected to EPC) or sdap-Config (when connected to 5GC). | +| daps-Config | Indicates that the bearer is configured as DAPS bearer. | +| drb-Identity | In case of DC, the DRB identity is unique within the scope of the UE, i.e. an MCG DRB cannot use the same value as a split DRB. For a split DRB the same identity is used for the MCG and SCG parts/indirect path of the configuration. | +| eps-BearerIdentity | The EPS bearer ID determines the EPS bearer. | +| mbs-SessionId | Indicates which multicast MBS session the bearer is associated with. | +| mrb-Identity | Identification of the multicast MRB. | +| mrb-IdentityNew | New identity of the multicast MRB when mrb-Identity needs to be changed, e.g. as a result of a handover. | +| reestablishPDCP | Indicates that PDCP should be re-established. Network sets this to true whenever the security key used for this radio bearer changes. Key change could for example be due to termination point change for the bearer, reconfiguration with sync, resuming an RRC connection, or the first reconfiguration after reestablishment. It is also applicable for LTE procedures when NR PDCP is configured. Network doesn't include this field for DRB if the bearer is configured as DAPS bearer or if the RadioBearerConfig IE is part of an RRCReconfiguration message within the LTM-Config IE. | +| recoverPDCP | Indicates that PDCP should perform recovery according to TS 38.323 [5]. Network doesn't include this field if the bearer is configured as DAPS bearer or if the RadioBearerConfig IE is part of an RRCReconfiguration message within the LTM-Config IE. | +| sdap-Config | The SDAP configuration determines how to map QoS flows to DRBs when NR or E-UTRA connects to the 5GC and presence/absence of UL/DL SDAP headers. | + +| RadioBearerConfig field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| securityConfig
Indicates the security algorithm and key to use for the signalling and data radio bearers configured with the list in this IE RadioBearerConfig . When the field is not included after AS security has been activated, the UE shall continue to use the currently configured keyToUse and security algorithm for the radio bearers reconfigured with the lists in this IE RadioBearerConfig . The field is not included when configuring SRB1 before AS security is activated. | +| srb3-ToRelease
Release SRB3. SRB3 release can only be done over SRB1 and only at SCG release and reconfiguration with sync. | + +| SecurityConfig field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| keyToUse
Indicates if the bearers configured with the list in this IE RadioBearerConfig are using the master key or the secondary key for deriving ciphering and/or integrity protection keys. For MR-DC, network should not configure SRB1 and SRB2 with secondary key and SRB3 with the master key. When the field is not included, the UE shall continue to use the currently configured keyToUse for the radio bearers reconfigured with the lists in this IE RadioBearerConfig . | +| securityAlgorithmConfig
Indicates the security algorithm for the signalling and data radio bearers configured with the list in this IE RadioBearerConfig . When the field is not included, the UE shall continue to use the currently configured security algorithm for the radio bearers reconfigured with the lists in this IE RadioBearerConfig . | + +| SRB-ToAddMod field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| discardOnPDCP
Indicates that PDCP should discard stored SDU and PDU according to TS 38.323 [5]. | +| reestablishPDCP
Indicates that PDCP should be re-established. Network sets this to true whenever the security key used for this radio bearer changes. Key change could for example be due to reconfiguration with sync, for SRB2 when resuming an RRC connection, or at the first reconfiguration after RRC connection reestablishment in NR. For SRB1, when resuming an RRC connection, or at the first reconfiguration after RRC connection reestablishment in NR, the network does not set this field to true . For LTE SRBs using NR PDCP, it could be for handover, RRC connection reestablishment or resume. Network doesn't include this field if any DAPS bearer is configured or if the RadioBearerConfig IE is part of an RRCReconfiguration message within the LTM-Config IE. | +| srb-Identity, srb-Identity-v1700, srb-Identity-v1800
Value 1 is applicable for SRB1 only. Value 2 is applicable for SRB2 only. Value 3 is applicable for SRB3 only. Value 4 is applicable for SRB4 only. Value 5 is applicable for SRB5 only. If srb-Identity-v1700 or srb-Identity-v1800 is received for an SRB, the UE shall ignore srb-Identity (i.e. without suffix) for this SRB. | + +| Conditional Presence | Explanation | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RBTermChange | The field is mandatory present in case of:
  • - set up of signalling and data radio bearer,
  • - change of termination point for the radio bearer between MN and SN.
It is optionally present otherwise, Need S. | +| RBTermChange1 | The field is mandatory present in case of:
  • - set up of signalling and data radio bearer,
  • - change of termination point for the radio bearer between MN and SN,
  • - handover from E-UTRA/EPC or E-UTRA/5GC to NR,
  • - handover from NR or E-UTRA/EPC to E-UTRA/5GC if the UE supports NGEN-DC.
It is optionally present otherwise, Need S. | +| PDCP | The field is mandatory present if the corresponding DRB/multicast MRB is being setup or corresponding DRB/multicast MRB is reconfigured with NR PDCP or corresponding SRB associated with two RLC entities is being setup or if the number of RLC bearers associated with the DRB/multicast MRB or SRB is changed. The field is optionally present, Need S, if the corresponding SRB associated with one RLC entity is being setup or corresponding SRB is reconfigured with NR PDCP; otherwise the field is optionally present, need M. | +| DRBSetup | The field is mandatory present if the corresponding DRB is being setup; otherwise the field is optionally present, need M. | +| HO-Conn | The field is mandatory present
  • - in case of inter-system handover from E-UTRA/EPC to E-UTRA/5GC or NR,
  • - or when the fullConfig is included in the RRCREconfiguration message and NE-DC/NR-DC is not configured,
  • - or in case of RRCSetup.
Otherwise the field is optionally present, need N.
Upon RRCSetup , only SRB1 can be present. | +| HO-toNR | If mrnToAddModList is not included, the field is mandatory present for UEs other than NCR-MT
  • - in case of inter-system handover from E-UTRA/EPC to E-UTRA/5GC or NR,
  • - or when the fullConfig is included in the RRCREconfiguration message and NE-DC/NR-DC is not configured.
In case of RRCSetup , the field is absent; otherwise the field is optionally present, need N. | +| DAPS | The field is optionally present, need N, in case masterCellGroup includes ReconfigurationWithSync , SCell(s) and SCG are not configured, multi-DCI/single-DCI based multi-TRP are not configured in any DL BWP, supplementaryUplink is not configured, ethernetHeaderCompression is not configured for the DRB, conditionalReconfiguration is not configured, and NR sidelink and V2X sidelink are not configured. Otherwise the field is absent. | +| MRBSetup | The field is mandatory present if the corresponding multicast MRB is being setup; otherwise the field is optionally present, need M. | + +### RadioLinkMonitoringConfig + +The IE *RadioLinkMonitoringConfig* is used to configure radio link monitoring for detection of beam- and/or cell radio link failure. See also TS 38.321 [3], clause 5.1.1. + +### RadioLinkMonitoringConfig information element + +``` +-- ASN1START +-- TAG-RADIOLINKMONITORINGCONFIG-START +``` + +``` + +RadioLinkMonitoringConfig ::= SEQUENCE { + failureDetectionResourcesToAddModList SEQUENCE (SIZE(1..maxNrofFailureDetectionResources)) OF RadioLinkMonitoringRS + OPTIONAL, -- Need N + failureDetectionResourcesToReleaseList SEQUENCE (SIZE(1..maxNrofFailureDetectionResources)) OF RadioLinkMonitoringRS-Id + OPTIONAL, -- Need N + beamFailureInstanceMaxCount ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10} OPTIONAL, -- Need R + beamFailureDetectionTimer ENUMERATED {pbfd1, pbfd2, pbfd3, pbfd4, pbfd5, pbfd6, pbfd8, pbfd10} OPTIONAL, -- Need R + ... + [[ + beamFailure-r17 BeamFailureDetection-r17 OPTIONAL -- Need R + ]] +} + +BeamFailureDetection-r17 ::= SEQUENCE { + failureDetectionSet1-r17 BeamFailureDetectionSet-r17 OPTIONAL, -- Need R + failureDetectionSet2-r17 BeamFailureDetectionSet-r17 OPTIONAL, -- Need R + additionalPCI-r17 AdditionalPCIIndex-r17 OPTIONAL -- Need R +} + +RadioLinkMonitoringRS ::= SEQUENCE { + radioLinkMonitoringRS-Id RadioLinkMonitoringRS-Id, + purpose ENUMERATED {beamFailure, rlf, both}, + detectionResource CHOICE { + ssb-Index SSB-Index, + csi-RS-Index NZP-CSI-RS-ResourceId + }, + ... +} + +BeamFailureDetectionSet-r17 ::= SEQUENCE { + bfdResourcesToAddModList-r17 SEQUENCE (SIZE(1..maxNrofBFDResourcePerSet-r17)) OF BeamLinkMonitoringRS-r17 + OPTIONAL, -- Need N + bfdResourcesToReleaseList-r17 SEQUENCE (SIZE(1..maxNrofBFDResourcePerSet-r17)) OF BeamLinkMonitoringRS-Id-r17 + OPTIONAL, -- Need N + beamFailureInstanceMaxCount-r17 ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10} OPTIONAL, -- Need R + beamFailureDetectionTimer-r17 ENUMERATED {pbfd1, pbfd2, pbfd3, pbfd4, pbfd5, pbfd6, pbfd8, pbfd10} OPTIONAL, -- Need R + ... +} + +BeamLinkMonitoringRS-r17 ::= SEQUENCE { + beamLinkMonitoringRS-Id-r17 BeamLinkMonitoringRS-Id-r17, + detectionResource-r17 CHOICE { + ssb-Index SSB-Index, + csi-RS-Index NZP-CSI-RS-ResourceId + }, + ... +} + +BeamLinkMonitoringRS-Id-r17 ::= INTEGER (0..maxNrofFailureDetectionResources-1-r17) + +-- TAG-RADIOLINKMONITORINGCONFIG-STOP + +``` + +-- ASN1STOP + +| RadioLinkMonitoringConfig field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| additionalPCI
Indicates the physical cell IDs (PCI) of the SSBs in the failureDetectionSet2 . If candidateBeamRS-List2 is configured in IE BeamFailureRecoveryRSConfig the field indicates the physical cell IDs (PCI) of the SSBs in the candidateBeamRS-List2 . | +| beamFailureDetectionTimer
Timer for beam failure detection (see TS 38.321 [3], clause 5.17). See also the BeamFailureRecoveryConfig IE. Value in number of "Q out,LR reporting periods of Beam Failure Detection" Reference Signal (see TS 38.213 [13], clause 6). Value pbfd1 corresponds to 1 Q out,LR reporting period of Beam Failure Detection Reference Signal, value pbfd2 corresponds to 2 Q out,LR reporting periods of Beam Failure Detection Reference Signal and so on. | +| beamFailureInstanceMaxCount
This field determines after how many beam failure events the UE triggers beam failure recovery (see TS 38.321 [3], clause 5.17). Value n1 corresponds to 1 beam failure instance, value n2 corresponds to 2 beam failure instances and so on. | +| failureDetectionResourcesToAddModList
A list of reference signals for detecting beam failure and/or cell level radio link failure (RLF). The limits of the reference signals that the network can configure are specified in TS 38.213 [13], table 5-1. The network configures at most two detectionResources per BWP for the purpose beamFailure or both . If no RSs are provided for the purpose of beam failure detection, the UE performs beam monitoring based on the activated TCI-State for PDCCH as described in TS 38.213 [13], clause 6. If no RSs are provided in this list for the purpose of RLF detection, the UE performs Cell-RLM based on the activated TCI-State of PDCCH as described in TS 38.213 [13], clause 5. The network ensures that the UE has a suitable set of reference signals for performing cell-RLM. If failureDetectionSet1-r17 and failureDetectionSet2-r17 are present, the purpose of RadioLinkMonitoringRS in failureDetectionResourcesToAddModList only can be set to rlf . | +| failureDetectionSet1, failureDetectionSet2
Configures parameters for beamfailure detection towards beam failure detection resources configured in the set. If additional PCIs are configured using additionalPCI-ToAddModList for the serving cell, each RS in one set can be associated only with one PCI. Network always configures the failureDetectionSet1 and failureDetectionSet2 together. failureDetectionSetN is present if and only if candidateBeamRS-List2-r17 is configured. When a failureDetectionSetN is present, after the reconfiguration, the UE shall consider all the reference signals for this failure detection set as activated if at most maxBFD-RS-resourcesPerSetPerBWP-r17 reference signals are configured for each failure detection set, otherwise the UE shall consider all the reference signals in this failure detection set as deactivated. If bfdResourcesToAddModList-r17 in failureDetectionSetN is not present, the UE determines the RS(es) in each failureDetectionSetN as described in TS 38.213 [13], clause 6. | + +| RadioLinkMonitoringRS field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| detectionResource
A reference signal that the UE shall use for radio link monitoring or beam failure detection (depending on the indicated purpose ). Only periodic 1-port CSI-RS can be configured on SCell for beam failure detection purpose. | +| purpose
Determines whether the UE shall monitor the associated reference signal for the purpose of cell- and/or beam failure detection. For SCell, network only configures the value to beamFailure . | + +#### — *RadioLinkMonitoringRS-Id* + +The IE *RadioLinkMonitoringRS-Id* is used to identify one *RadioLinkMonitoringRS*. + +#### **RadioLinkMonitoringRS-Id information element** + +``` +-- ASN1START +-- TAG-RADIOLINKMONITORINGRS-ID-START + +RadioLinkMonitoringRS-Id ::= INTEGER (0..maxNrofFailureDetectionResources-1) + +-- TAG-RADIOLINKMONITORINGRS-ID-STOP +-- ASN1STOP +``` + +#### — *RAN-AreaCode* + +The IE *RAN-AreaCode* is used to identify a RAN area within the scope of a tracking area. + +#### ***RAN-AreaCode* information element** + +``` +-- ASN1START +-- TAG-RAN-AREACODE-START + +RAN-AreaCode ::= INTEGER (0..255) + +-- TAG-RAN-AREACODE-STOP +-- ASN1STOP +``` + +#### — *RateMatchPattern* + +The IE *RateMatchPattern* is used to configure one rate matching pattern for PDSCH, see TS 38.214 [19], clause 5.1.4.1. + +#### ***RateMatchPattern* information element** + +``` +-- ASN1START +-- TAG-RATEMATCHPATTERN-START + +RateMatchPattern ::= SEQUENCE { + rateMatchPatternId RateMatchPatternId, + + patternType CHOICE { + bitmaps SEQUENCE { + resourceBlocks BIT STRING (SIZE (275)), + symbolsInResourceBlock CHOICE { + oneSlot BIT STRING (SIZE (14)), + twoSlots BIT STRING (SIZE (28)) + }, + periodicityAndPattern CHOICE { + n2 BIT STRING (SIZE (2)), + n4 BIT STRING (SIZE (4)), + } + } + } +} +``` + +``` + n5 BIT STRING (SIZE (5)), + n8 BIT STRING (SIZE (8)), + n10 BIT STRING (SIZE (10)), + n20 BIT STRING (SIZE (20)), + n40 BIT STRING (SIZE (40)) + } + ... +}, +controlResourceSet ControlResourceSetId +}, +subcarrierSpacing SubcarrierSpacing +dummy ENUMERATED { dynamic, semiStatic }, +... +[[ +controlResourceSet-r16 ControlResourceSetId-r16 +]] +} + +-- TAG-RATEMATCHPATTERN-STOP +-- ASN1STOP +``` + +| RateMatchPattern field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

bitmaps
Indicates rate matching pattern by a pair of bitmaps resourceBlocks and symbolsInResourceBlock to define the rate match pattern within one or two slots, and a third bitmap periodicityAndPattern to define the repetition pattern with which the pattern defined by the above bitmap pair occurs.

| +|

controlResourceSet
This ControlResourceSet is used as a PDSCH rate matching pattern, i.e., PDSCH reception rate matches around it. In frequency domain, the resource is determined by the frequency domain resource of the CORESET with the corresponding CORESET ID. Time domain resource is determined by the parameters of the associated search space of the CORESET.
If the field controlResourceSetId-r16 is present, UE shall ignore the controlResourceSetId (without suffix).

| +|

periodicityAndPattern
A time domain repetition pattern at which the pattern defined by symbolsInResourceBlock and resourceBlocks recurs. This slot pattern repeats itself continuously. Absence of this field indicates the value n1 (see TS 38.214 [19], clause 5.1.4.1).

| +|

resourceBlocks
A resource block level bitmap in the frequency domain. A bit in the bitmap set to 1 indicates that the UE shall apply rate matching in the corresponding resource block in accordance with the symbolsInResourceBlock bitmap. If used as cell-level rate matching pattern, the bitmap identifies "common resource blocks (CRB)". If used for MBS broadcast CFR, the bitmap identifies "physical resource blocks" inside the MBS broadcast CFR. If used as BWP-level rate matching pattern, the bitmap identifies "physical resource blocks" inside the BWP or MBS multicast CFR. The first/ leftmost bit corresponds to resource block 0, and so on (see TS 38.214 [19], clause 5.1.4.1).

| +|

subcarrierSpacing
The SubcarrierSpacing for this resource pattern. If the field is absent, the UE applies the SCS of the associated BWP. The value kHz15 corresponds to \mu=0, the value kHz30 corresponds to \mu=1, and so on.
Only the following values are applicable depending on the used frequency (see TS 38.214 [19], clause 5.1.4.1):
FR1: 15, 30 or 60 kHz
FR2-1: 60 or 120 kHz
FR2-2: 120, 480, or 960 kHz

| +|

symbolsInResourceBlock
A symbol level bitmap in time domain. It indicates with a bit set to true that the UE shall rate match around the corresponding symbol. This pattern recurs (in time domain) with the configured periodicityAndPattern (see TS 38.214 [19], clause 5.1.4.1).
For oneSlot, if ECP is configured, the first 12 bits represent the symbols within the slot and the last two bits within the bitstring are ignored by the UE; Otherwise, the 14 bits represent the symbols within the slot.
For twoSlots, if ECP is configured, the first 12 bits represent the symbols within the first slot and the next 12 bits represent the symbols in the second slot and the last four bits within the bit string are ignored by the UE; Otherwise, the first 14 bits represent the symbols within the first slot and the next 14 bits represent the symbols in the second slot.
For the bits representing symbols in a slot, the most significant bit of the bit string represents the first symbol in the slot and the second most significant bit represents the second symbol in the slot and so on.

| + +| Conditional Presence | Explanation | +|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CellLevel | The field is mandatory present if the RateMatchPattern is defined on cell level. The field is absent when the RateMatchPattern is defined on BWP level or defined for MBS broadcast CFR. If the RateMatchPattern is defined on BWP level, the UE applies the SCS of the BWP and if RateMatchPattern is defined for MBS broadcast CFR, the UE applies the SCS of the initial BWP or (e)RedCap-specific initial BWP (if configured) for (e)RedCap UEs. | + +#### — *RateMatchPatternId* + +The IE *RateMatchPatternId* identifies one *RateMatchPattern* (see TS 38.214 [19], clause 5.1.4.1). + +#### *RateMatchPatternId* information element + +``` +-- ASN1START +-- TAG-RATEMATCHPATTERNID-START + +RateMatchPatternId ::= INTEGER (0..maxNrofRateMatchPatterns-1) + +-- TAG-RATEMATCHPATTERNID-STOP +-- ASN1STOP +``` + +#### — *RateMatchPatternLTE-CRS* + +The IE *RateMatchPatternLTE-CRS* is used to configure a pattern to rate match around LTE CRS. See TS 38.214 [19], clause 5.1.4.2. + +#### *RateMatchPatternLTE-CRS* information element + +``` +-- ASN1START +-- TAG-RATEMATCHPATTERNLTE-CRS-START + +RateMatchPatternLTE-CRS ::= SEQUENCE { + carrierFreqDL INTEGER (0..16383), + carrierBandwidthDL ENUMERATED {n6, n15, n25, n50, n75, n100, spare2, spare1}, + mbsfn-SubframeConfigList EUTRA-MBSFN-SubframeConfigList OPTIONAL, -- Need M + nrofCRS-Ports ENUMERATED {n1, n2, n4}, + v-Shift ENUMERATED {n0, n1, n2, n3, n4, n5} +} + +LTE-CRS-PatternList-r16 ::= SEQUENCE (SIZE (1..maxLTE-CRS-Patterns-r16)) OF RateMatchPatternLTE-CRS + +-- TAG-RATEMATCHPATTERNLTE-CRS-STOP +-- ASN1STOP +``` + +| RateMatchPatternLTE-CRS field descriptions | +|--------------------------------------------------------------------------------------------------------------------| +| carrierBandwidthDL
BW of the LTE carrier in number of PRBs (see TS 38.214 [19], clause 5.1.4.2). | +| carrierFreqDL
Center of the LTE carrier (see TS 38.214 [19], clause 5.1.4.2). | +| mbsfn-SubframeConfigList
LTE MBSFN subframe configuration (see TS 38.214 [19], clause 5.1.4.2). | +| nrofCRS-Ports
Number of LTE CRS antenna port to rate-match around (see TS 38.214 [19], clause 5.1.4.2). | +| v-Shift
Shifting value v-shift in LTE to rate match around LTE CRS (see TS 38.214 [19], clause 5.1.4.2). | + +#### — *ReferenceConfiguration* + +The IE *ReferenceConfiguration* is used provide a configuration that is common, within the same cell group, to all configured non-complete candidate configurations. + +### ***ReferenceConfiguration* information element** + +``` +-- ASN1START +-- TAG-REFERENCECONFIGURATION-START + +ReferenceConfiguration-r18 ::= OCTET STRING (CONTAINING RRCReconfiguration) + +-- TAG-REFERENCECONFIGURATION-STOP +-- ASN1STOP +``` + +#### — *ReferenceLocation* + +The IE *ReferenceLocation* contains location information used as a reference location. The value of the field is same as *Ellipsoid-Point* defined in TS37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit. + +#### ***ReferenceLocation* information element** + +``` +-- ASN1START +-- TAG-REFERENCELOCATION-START + +ReferenceLocation-r17 ::= OCTET STRING + +-- TAG-REFERENCELOCATION-STOP +-- ASN1STOP +``` + +### ReferenceTimeInfo + +The IE *ReferenceTimeInfo* contains timing information for 5G internal system clock used for, e.g., time stamping, see TS 23.501 [32], clause 5.27.1.2. + +#### ReferenceTimeInfo information element + +``` +-- ASN1START +-- TAG-REFERENCETIMEINFO-START + +ReferenceTimeInfo-r16 ::= SEQUENCE { + time-r16 ReferenceTime-r16, + uncertainty-r16 INTEGER (0..32767) OPTIONAL, -- Need S + timeInfoType-r16 ENUMERATED {localClock} OPTIONAL, -- Need S + referenceSFN-r16 INTEGER (0..1023) OPTIONAL -- Cond RefTime +} + +ReferenceTime-r16 ::= SEQUENCE { + refDays-r16 INTEGER (0..72999), + refSeconds-r16 INTEGER (0..86399), + refMilliSeconds-r16 INTEGER (0..999), + refTenNanoSeconds-r16 INTEGER (0..99999) +} + +-- TAG-REFERENCETIMEINFO-STOP +-- ASN1STOP +``` + +| ReferenceTimeInfo field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

referenceSFN
This field indicates the reference SFN corresponding to the reference time information. If referenceTimeInfo field is received in DLInformationTransfer message, this field indicates the SFN of PCell.

| +|

time
This field indicates time reference with 10ns granularity. If included in DLInformationTransfer and if UE-side TA PDC is de-activated, the indicated time may not be referenced at the network, i.e., gNB may pre-compensate for RF propagation delay. If included in DLInformationTransfer and if UE is requested to transmit UE Rx-Tx time difference measurement, the indicated time may not be referenced at the network, i.e., gNB may pre-compensate for RF propagation delay. Otherwise, the indicated time is referenced at the network, i.e., without compensating for RF propagation delay. In an NTN cell, the indicated time is referenced at the uplink time synchronization reference point (RP), i.e., UE should take into account the propagation delay between UE and RP when determining the UTC time at the UE.
The indicated time in 10ns unit from the origin is refDays * 86400 * 1000 * 100000 + refSeconds * 1000 * 100000 + refMilliSeconds * 100000 + refTenNanoSeconds. The refDays field specifies the sequential number of days (with day count starting at 0) from the origin of the time field.
If the referenceTimeInfo field is received in DLInformationTransfer message, the time field indicates the time at the ending boundary of the system frame indicated by referenceSFN. The UE considers this frame (indicated by referenceSFN) to be the frame which is nearest to the frame where the message is received (which can be either in the past or in the future).
If the referenceTimeInfo field is received in SIB9, the time field indicates the time at the SFN boundary at or immediately after the ending boundary of the SI-window in which SIB9 is transmitted.
If referenceTimeInfo field is received in SIB9, this field is excluded when determining changes in system information, i.e. changes of time should neither result in system information change notifications nor in a modification of valueTag in SIB1.

NOTE: The estimated time in an NTN-cell may be less accurate than the estimated time in a TN-cell.

| +|

timeInfoType
If timeInfoType is not included, the time indicates the GPS time and the origin of the time field is 00:00:00 on Gregorian calendar date 6 January, 1980 (start of GPS time). If timeInfoType is set to localClock, the origin of the time is unspecified.

| +|

uncertainty
This field indicates the uncertainty of the reference time information provided by the time field. The uncertainty is 25ns multiplied by this field. If this field is absent, the uncertainty is unspecified.

| + +| Conditional Presence | Explanation | +|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| RefTime | The field is mandatory present if referenceTimeInfo is included in DLInformationTransfer message; otherwise the field is absent. | + +### RejectWaitTime + +The IE *RejectWaitTime* is used to provide the value in seconds for timer T302. + +#### RejectWaitTime information element + +``` +-- ASN1START +-- TAG-REJECTWAITTIME-START + +RejectWaitTime ::= + INTEGER (1..16) +``` + +``` +-- TAG-REJECTWAITTIME-STOP +-- ASN1STOP +``` + +## RepetitionSchemeConfig + +The IE *RepetitionSchemeConfig* is used to configure the UE with repetition schemes as specified in TS 38.214 [19] clause 5.1. + +### RepetitionSchemeConfig information element + +``` +-- ASN1START +-- TAG-REPETITIONSCHEMECONFIG-START + +RepetitionSchemeConfig-r16 ::= CHOICE { + fdm-TDM-r16 SetupRelease { FDM-TDM-r16 }, + slotBased-r16 SetupRelease { SlotBased-r16 } +} + +RepetitionSchemeConfig-v1630 ::= SEQUENCE { + slotBased-v1630 SetupRelease { SlotBased-v1630 } +} + +FDM-TDM-r16 ::= SEQUENCE { + repetitionScheme-r16 ENUMERATED {fdmSchemeA, fdmSchemeB,tdmSchemeA }, + startingSymbolOffsetK-r16 INTEGER (0..7) OPTIONAL -- Need R +} + +SlotBased-r16 ::= SEQUENCE { + tciMapping-r16 ENUMERATED {cyclicMapping, sequentialMapping}, + sequenceOffsetForRV-r16 INTEGER (1..3) +} + +SlotBased-v1630 ::= SEQUENCE { + tciMapping-r16 ENUMERATED {cyclicMapping, sequentialMapping}, + sequenceOffsetForRV-r16 INTEGER (0) +} + +-- TAG-REPETITIONSCHEMECONFIG-STOP +-- ASN1STOP +``` + +| RepetitionSchemeConfig field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| fdm-TDM
Configures UE with a repetition scheme among fdmSchemeA, fdmSchemeB and tdmSchemeA as specified in clause 5.1 of TS 38.214 [19]. The network does not set this field to release . Upon reception of this field in RepetitionSchemeConfig-r16 , the UE shall release slotBased if previously configured in the same instance of RepetitionSchemeConfig-r16 . | +| sequenceOffsetForRV
For slot-based repetition scheme, selected RV sequence is applied to transmission occasions associated to the first TCI state. The RV sequence associated to the second TCI state is determined by a RV offset from that selected RV sequence. | +| slotBased
Configures UE with slot-based repetition scheme. Network always configures this field when the parameter repetitionNumber is present in IE PDSCH-TimeDomainResourceAllocationList . The network does not set this field to release . Upon reception of this field in RepetitionSchemeConfig-r16 , the UE shall release fdm-TDM if previously configured in the same instance of RepetitionSchemeConfig-r16 . | +| startingSymbolOffsetK
The starting symbol of the second transmission occasion has K symbol offset relative to the last symbol of the first transmission occasion. When UE is configured with tdmSchemeA , the parameter startingSymbolOffsetK is present, otherwise absent. | +| tcMapping
Enables TCI state mapping method to PDSCH transmission occasions. | + +#### — *ReportConfigId* + +The IE *ReportConfigId* is used to identify a measurement reporting configuration. + +#### ***ReportConfigId* information element** + +``` +-- ASN1START +-- TAG-REPORTCONFIGID-START + +ReportConfigId ::= INTEGER (1..maxReportConfigId) + +-- TAG-REPORTCONFIGID-STOP +-- ASN1STOP +``` + +#### — *ReportConfigInterRAT* + +The IE *ReportConfigInterRAT* specifies criteria for triggering of an inter-RAT measurement reporting event, or an L2 U2N relay measurement reporting event. The inter-RAT measurement reporting events for E-UTRA and UTRA-FDD are labelled *BN* with *N* equal to 1, 2 and so on. The measurement reporting events for L2 U2N relay UE are labelled *YN* with *N* equal to 1, 2 and so on. The measurement reporting events for L2 U2N relay UE are labelled *Z1*. + +Event B1: Neighbour becomes better than absolute threshold; + +Event B2: PCell becomes worse than absolute threshold1 AND Neighbour becomes better than another absolute threshold2; + +Event Y1: PCell becomes worse than absolute threshold1 AND candidate L2 U2N Relay UE becomes better than another absolute threshold2; + +Event Y2: Candidate L2 U2N Relay UE becomes better than absolute threshold; + +Event Z1: Serving L2 U2N Relay UE becomes worse than absolute threshold1 AND candidate L2 U2N Relay UE becomes better than another absolute threshold2; + +#### ***ReportConfigInterRAT information element*** + +``` +-- ASN1START +-- TAG-REPORTCONFIGINTERRAT-START + +ReportConfigInterRAT ::= + SEQUENCE { + reportType + CHOICE { + periodical + eventTriggered + reportCGI + ..., + reportSFTD + } + } + +ReportCGI-EUTRA ::= + SEQUENCE { + cellForWhichToReportCGI + EUTRA-PhysCellId, + ..., + [[ + useAutonomousGaps-r16 + ENUMERATED {setup} + OPTIONAL -- Need R + ]] + } + +ReportSFTD-EUTRA ::= + SEQUENCE { + reportSFTD-Meas + BOOLEAN, + reportRSRP + BOOLEAN, + ... + } + +EventTriggerConfigInterRAT ::= + SEQUENCE { + eventId + CHOICE { + eventB1 + SEQUENCE { + b1-ThresholdEUTRA + MeasTriggerQuantityEUTRA, + reportOnLeave + BOOLEAN, + hysteresis + Hysteresis, + timeToTrigger + TimeToTrigger, + ... + }, + eventB2 + SEQUENCE { + b2-Threshold1 + MeasTriggerQuantity, + b2-Threshold2EUTRA + MeasTriggerQuantityEUTRA, + reportOnLeave + BOOLEAN, + hysteresis + Hysteresis, + timeToTrigger + TimeToTrigger, + } + } + } +``` + +``` + + ... + }, + ... + [[ + eventB1-UTRA-FDD-r16 + b1-ThresholdUTRA-FDD-r16 + reportOnLeave-r16 + hysteresis-r16 + timeToTrigger-r16 + ... + }, + eventB2-UTRA-FDD-r16 + b2-Threshold1-r16 + b2-Threshold2UTRA-FDD-r16 + reportOnLeave-r16 + hysteresis-r16 + timeToTrigger-r16 + ... + } + ]], + [[ + eventY1-Relay-r17 + y1-Threshold1-r17 + y1-Threshold2-Relay-r17 + reportOnLeave-r17 + hysteresis-r17 + timeToTrigger-r17 + ... + }, + eventY2-Relay-r17 + y2-Threshold-Relay-r17 + reportOnLeave-r17 + hysteresis-r17 + timeToTrigger-r17 + ... + } + ]], + [[ + eventZ1-Relay-r18 + z1-Threshold1-Relay-r18 + sl-RSRP-r18 + sd-RSRP-r18 + ... + }, + z1-Threshold2-Relay-r18 + reportOnLeave-r18 + hysteresis-r18 + timeToTrigger-r18 + ... + } + ]] + +``` + +``` + +SEQUENCE { + MeasTriggerQuantityUTRA-FDD-r16, + BOOLEAN, + Hysteresis, + TimeToTrigger, +} + +SEQUENCE { + MeasTriggerQuantity, + MeasTriggerQuantityUTRA-FDD-r16, + BOOLEAN, + Hysteresis, + TimeToTrigger, +} + +SEQUENCE { + MeasTriggerQuantity, + SL-MeasTriggerQuantity-r16, + BOOLEAN, + Hysteresis, + TimeToTrigger, +} + +SEQUENCE { + SL-MeasTriggerQuantity-r16, + BOOLEAN, + Hysteresis, + TimeToTrigger, +} + +SEQUENCE { + SEQUENCE { + SL-MeasTriggerQuantity-r16, + SL-MeasTriggerQuantity-r16 + OPTIONAL, -- Need S + }, + SL-MeasTriggerQuantity-r16, + BOOLEAN, + Hysteresis, + TimeToTrigger, +} + +``` + +``` + + }, + rsType NR-RS-Type, + + reportInterval ReportInterval, + reportAmount ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity}, + reportQuantity MeasReportQuantity, + maxReportCells INTEGER (1..maxCellReport), + ..., + [[ + reportQuantityUTRA-FDD-r16 MeasReportQuantityUTRA-FDD-r16 OPTIONAL -- Need R + ]], + [[ + includeCommonLocationInfo-r16 ENUMERATED {true} OPTIONAL, -- Need R + includeBT-Meas-r16 SetupRelease {BT-NameList-r16} OPTIONAL, -- Need M + includeWLAN-Meas-r16 SetupRelease {WLAN-NameList-r16} OPTIONAL, -- Need M + includeSensor-Meas-r16 SetupRelease {Sensor-NameList-r16} OPTIONAL -- Need M + ]], + [[ + reportQuantityRelay-r17 SL-MeasReportQuantity-r16 OPTIONAL -- Need R + ]] + } + + PeriodicalReportConfigInterRAT ::= + SEQUENCE { + reportInterval ReportInterval, + reportAmount ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity}, + reportQuantity MeasReportQuantity, + maxReportCells INTEGER (1..maxCellReport), + ..., + [[ + reportQuantityUTRA-FDD-r16 MeasReportQuantityUTRA-FDD-r16 OPTIONAL -- Need R + ]], + [[ + includeCommonLocationInfo-r16 ENUMERATED {true} OPTIONAL, -- Need R + includeBT-Meas-r16 SetupRelease {BT-NameList-r16} OPTIONAL, -- Need M + includeWLAN-Meas-r16 SetupRelease {WLAN-NameList-r16} OPTIONAL, -- Need M + includeSensor-Meas-r16 SetupRelease {Sensor-NameList-r16} OPTIONAL -- Need M + ]], + [[ + reportQuantityRelay-r17 SL-MeasReportQuantity-r16 OPTIONAL -- Need R + ]], + [[ + cellIndividualOffsetList-r18 SEQUENCE (SIZE (1..maxCellMeasEUTRA)) OF CellIndividualOffsetList-EUTRA-r18 OPTIONAL -- Need R + ]] + } + + MeasTriggerQuantityUTRA-FDD-r16 ::= + CHOICE{ + utra-FDD-RSCP-r16 INTEGER (-5..91), + utra-FDD-EcN0-r16 INTEGER (0..49) + } + +``` + +``` +MeasReportQuantityUTRA-FDD-r16 ::= SEQUENCE { + cpich-RSCP BOOLEAN, + cpich-EcN0 BOOLEAN +} + +CellIndividualOffsetList-EUTRA-r18 ::= SEQUENCE { + physCellId-r18 EUTRA-PhysCellId, + cellIndividualOffset-r18 EUTRA-Q-OffsetRange +} + +-- TAG-REPORTCONFIGINTERRAT-STOP +-- ASN1STOP +``` + +Editor's Note: FFS how to include two thresholds for SL-RSRP and SD-RSRP in event X1, X2, Y2. + +#### | | |-------------------------------------------------------| | ReportConfigInterRAT field descriptions | |-------------------------------------------------------| + +#### | | |--------------------------| | reportType | |--------------------------| + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------| +| Type of the configured measurement report. In (NG)EN-DC, and NR-DC, network does not configure report of type ReportCGI-EUTRA for SCG. | +|-----------------------------------------------------------------------------------------------------------------------------------------------| + +#### | | |--------------------------------------------------| | ReportCGI-EUTRA field descriptions | |--------------------------------------------------| + +##### | | |---------------------------------| | useAutonomousGaps | |---------------------------------| + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Indicates whether or not the UE is allowed to use autonomous gaps in acquiring system information from the E-UTRAN neighbour cell. When the field is included, the UE applies the corresponding value for T321. | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| EventTriggerConfigInterRAT field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| b2-Threshold1
NR threshold to be used in inter RAT measurement report triggering condition for event B2. | +| bN-ThresholdEUTRA
E-UTRA threshold value associated with the selected trigger quantity (RSRP, RSRQ, SINR) to be used in inter RAT measurement report triggering condition for event number bN. In the same eventB2 , the network configures the same CHOICE name ( rsrp , rsrq or sinn ) for the MeasTriggerQuantity of the b2-Threshold1 and for the MeasTriggerQuantityEUTRA of the b2-Threshold2EUTRA . | +| eventId
Choice of inter RAT event triggered reporting criteria. | +| maxReportCells
Max number of non-serving cells/candidate L2 U2N Relay UEs to include in the measurement report. | +| reportAmount
Number of measurement reports applicable for eventTriggered as well as for periodical report types | +| reportOnLeave
Indicates whether or not the UE shall initiate the measurement reporting procedure when the leaving condition is met for a cell in cellsTriggeredList , as specified in 5.5.4.1. | +| reportQuantity, reportQuantityUTRA-FDD
The cell measurement quantities to be included in the measurement report. If the field eventB1-UTRA-FDD or eventB2-UTRA-FDD is present, the UE shall ignore the value(s) provided in reportQuantity . | +| reportQuantityRelay
The L2 U2N Relay UE measurement quantity to be included in measurement report. | +| timeToTrigger
Time during which specific criteria for the event needs to be met in order to trigger a measurement report. | +| bN-ThresholdUTRA-FDD
UTRA-FDD threshold value associated with the selected trigger quantity (RSCP, EcN0) to be used in inter RAT measurement report triggering condition for event number bN. utra-FDD-RSCP corresponds to CPICH_RSCP in TS 25.133 [46] for FDD. utra-FDD-EcN0 corresponds to CPICH_Ec/No in TS 25.133 [46] for FDD.
For utra-FDD-RSCP : The actual value is field value – 115 dBm.
For utra-FDD-EcN0 : The actual value is (field value – 49)/2 dB. | +| y1-Threshold1
NR threshold to be used in measurement report triggering condition for event Y1. | +| y1-Threshold2-Relay
L2 U2N Relay threshold value associated with the selected trigger quantity (i.e. RSRP) to be used in measurement report triggering condition for event Y1. | +| y2-Threshold-Relay
L2 U2N Relay threshold value associated with the selected trigger quantity (i.e. RSRP) to be used in measurement report triggering condition for event Y2. | +| z1-Threshold1-Relay
L2 U2N Relay threshold value associated with the selected trigger quantity (i.e. SL-RSRP and/or SD-RSRP) to be used in measurement report triggering condition for serving Relay UE in event Z1. If the field sd-RSRP is not included, the UE considers it to be equal to sl-RSRP . | +| z1-Threshold2-Relay
L2 U2N Relay threshold value associated with the selected trigger quantity (i.e. SD-RSRP) to be used in measurement report triggering condition for candidate Relay UE in event Z1. | + +| PeriodicalReportConfigInterRAT field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| maxReportCells
Max number of non-serving cells/candidate L2 U2N Relay UEs to include in the measurement report. | +| reportAmount
Number of measurement reports applicable for eventTriggered as well as for periodical report types | +| reportQuantity, reportQuantityUTRA-FDD
The cell measurement quantities to be included in the measurement report. If the field reportQuantityUTRA-FDD is present, the UE shall ignore the value(s) provided in reportQuantity . | + +| CellIndividualOffsetList-EUTRA field descriptions | +|-----------------------------------------------------------------------------------------------------------| +| cellIndividualOffset
Cell individual offsets applicable to a specific measurement event. | +| physCellId
Physical cell identity of a cell in the cell list. | + +#### – ***ReportConfigNR*** + +The IE *ReportConfigNR* specifies criteria for triggering of an NR measurement reporting event or of a CHO, CPA or CPC event or of an L2 U2N relay measurement reporting event. For events labelled AN with N equal to 1, 2 and so on, measurement reporting events and CHO, CPA or CPC events are based on cell measurement results, which can either be derived based on SS/PBCH block or CSI-RS. + +Event A1: Serving becomes better than absolute threshold; + +Event A2: Serving becomes worse than absolute threshold; + +Event A3: Neighbour becomes amount of offset better than PCell/PSCell; + +Event A4: Neighbour becomes better than absolute threshold; + +Event A5: PCell/PSCell becomes worse than absolute threshold1 AND Neighbour/SCell becomes better than another absolute threshold2; + +Event A6: Neighbour becomes amount of offset better than SCell; + +Event D1: Distance between UE and a reference location *referenceLocation1* becomes larger than configured threshold *distanceThreshFromReference1* and distance between UE and a reference location *referenceLocation2* becomes shorter than configured threshold *distanceThreshFromReference2*; + +CondEvent A3: Conditional reconfiguration candidate becomes amount of offset better than PCell/PSCell; + +CondEvent A4: Conditional reconfiguration candidate becomes better than absolute threshold where *condEventA4* can also be used for current PSCell (i.e., in case it is configured as candidate PSCell for CondEvent A4 evaluation) for CHO with candidate SCG(s) case; + +CondEvent A5: PCell/PSCell becomes worse than absolute threshold1 AND Conditional reconfiguration candidate becomes better than another absolute threshold2; + +CondEvent D1: Distance between UE and a reference location *referenceLocation1* becomes larger than configured threshold *distanceThreshFromReference1* and distance between UE and a reference location *referenceLocation2* of conditional reconfiguration candidate becomes shorter than configured threshold *distanceThreshFromReference2*; + +CondEvent D2: Distance between UE and a moving reference location determined based on *referenceLocation1* becomes larger than configured threshold *distanceThreshFromReference1* and distance between UE and a moving reference location determined based on *referenceLocation2* of conditional reconfiguration candidate becomes shorter than configured threshold *distanceThreshFromReference2*; + +CondEvent T1: Time measured at UE becomes more than configured threshold *t1-Threshold* but is less than *t1-Threshold + duration*; + +Event X1: Serving L2 U2N Relay UE becomes worse than absolute threshold1 AND NR Cell becomes better than another absolute threshold2; + +Event X2: Serving L2 U2N Relay UE becomes worse than absolute threshold; + +For event I1, measurement reporting event is based on CLI measurement results, which can either be derived based on SRS-RSRP or CLI-RSSI. + +Event I1: Interference becomes higher than absolute threshold. + +The reporting events concerning Aerial UE altitude are labelled HN with *N* equal to 1 and 2. Additionally, the reporting events concerning Aerial UE altitude and the neighboring cell measurements simultaneously are labelled AMHN with *M* equal to 3, 4, 5 and *N* equal to 1, 2. + +Event H1: Aerial UE altitude becomes higher than a threshold; + +Event H2: Aerial UE altitude becomes lower than a threshold. + +Event A3H1: Neighbour becomes offset better than SpCell and the Aerial UE altitude becomes higher than a threshold. + +Event A3H2: Neighbour becomes offset better than SpCell and the Aerial UE altitude becomes lower than a threshold. + +Event A4H1: Neighbour becomes better than threshold1 and the Aerial UE altitude becomes higher than a threshold2. + +Event A4H2: Neighbour becomes better than threshold1 and the Aerial UE altitude becomes lower than a threshold2. + +Event A5H1: SpCell becomes worse than threshold1 and neighbour becomes better than threshold2 and the Aerial UE altitude becomes higher than a threshold3. + +Event A5H2: SpCell becomes worse than threshold1 and neighbour becomes better than threshold2 and the Aerial UE altitude becomes lower than a threshold3. + +### ReportConfigNR information element + +``` +-- ASN1START +-- TAG-REPORTCONFIGNR-START +``` + +``` +ReportConfigNR ::= SEQUENCE { +``` + +``` + +reportType CHOICE { + periodical PeriodicalReportConfig, + eventTriggered EventTriggerConfig, + ... + reportCGI ReportCGI, + reportSFTD ReportSFTD-NR, + condTriggerConfig-r16 CondTriggerConfig-r16, + cli-Periodical-r16 CLI-PeriodicalReportConfig-r16, + cli-EventTriggered-r16 CLI-EventTriggerConfig-r16, + rxTxPeriodical-r17 RxTxPeriodical-r17, + reportOnScellActivation-r18 ReportOnScellActivation-r18 +} + +ReportCGI ::= SEQUENCE { + cellForWhichToReportCGI PhysCellId, + ... + [[ + useAutonomousGaps-r16 ENUMERATED {setup} OPTIONAL -- Need R + ]] +} + +ReportSFTD-NR ::= SEQUENCE { + reportSFTD-Meas BOOLEAN, + reportRSRP BOOLEAN, + ... + [[ + reportSFTD-NeighMeas ENUMERATED {true} OPTIONAL, -- Need R + drx-SFTD-NeighMeas ENUMERATED {true} OPTIONAL, -- Need R + cellsForWhichToReportSFTD SEQUENCE (SIZE (1..maxCellSFTD)) OF PhysCellId OPTIONAL -- Need R + ]] +} + +CondTriggerConfig-r16 ::= SEQUENCE { + condEventId CHOICE { + condEventA3 SEQUENCE { + a3-Offset MeasTriggerQuantityOffset, + hysteresis Hysteresis, + timeToTrigger TimeToTrigger + }, + condEventA5 SEQUENCE { + a5-Threshold1 MeasTriggerQuantity, + a5-Threshold2 MeasTriggerQuantity, + hysteresis Hysteresis, + timeToTrigger TimeToTrigger + }, + ... + condEventA4-r17 SEQUENCE { + a4-Threshold-r17 MeasTriggerQuantity, + hysteresis-r17 Hysteresis, + } + } +} + +``` + +``` + + timeToTrigger-r17 TimeToTrigger + }, + condEventD1-r17 SEQUENCE { + distanceThreshFromReference1-r17 INTEGER(0.. 65525), + distanceThreshFromReference2-r17 INTEGER(0.. 65525), + referenceLocation1-r17 ReferenceLocation-r17, + referenceLocation2-r17 ReferenceLocation-r17, + hysteresisLocation-r17 HysteresisLocation-r17, + timeToTrigger-r17 TimeToTrigger + }, + condEventT1-r17 SEQUENCE { + t1-Threshold-r17 INTEGER (0..549755813887), + duration-r17 INTEGER (1..6000) + }, + condEventD2-r18 SEQUENCE { + distanceThreshFromReference1-r18 INTEGER(0.. 65525), + distanceThreshFromReference2-r18 INTEGER(0.. 65525), + referenceLocation1-r18 ReferenceLocation-r17, + referenceLocation2-r18 ReferenceLocation-r17, + hysteresisLocation-r18 HysteresisLocation-r17, + timeToTrigger-r18 TimeToTrigger + } +}, +rsType-r16 NR-RS-Type, +... +[[ +nesEvent-r18 ENUMERATED {true} OPTIONAL -- Need R +]] +} + +EventTriggerConfig ::= + eventId SEQUENCE { + CHOICE { + eventA1 SEQUENCE { + a1-Threshold MeasTriggerQuantity, + reportOnLeave BOOLEAN, + hysteresis Hysteresis, + timeToTrigger TimeToTrigger + }, + eventA2 SEQUENCE { + a2-Threshold MeasTriggerQuantity, + reportOnLeave BOOLEAN, + hysteresis Hysteresis, + timeToTrigger TimeToTrigger + }, + eventA3 SEQUENCE { + a3-Offset MeasTriggerQuantityOffset, + reportOnLeave BOOLEAN, + hysteresis Hysteresis, + timeToTrigger TimeToTrigger, + useAllowedCellList BOOLEAN + } + } + } + +``` + +``` + }, + eventA4 SEQUENCE { + a4-Threshold MeasTriggerQuantity, + reportOnLeave BOOLEAN, + hysteresis Hysteresis, + timeToTrigger TimeToTrigger, + useAllowedCellList BOOLEAN + }, + eventA5 SEQUENCE { + a5-Threshold1 MeasTriggerQuantity, + a5-Threshold2 MeasTriggerQuantity, + reportOnLeave BOOLEAN, + hysteresis Hysteresis, + timeToTrigger TimeToTrigger, + useAllowedCellList BOOLEAN + }, + eventA6 SEQUENCE { + a6-Offset MeasTriggerQuantityOffset, + reportOnLeave BOOLEAN, + hysteresis Hysteresis, + timeToTrigger TimeToTrigger, + useAllowedCellList BOOLEAN + }, + ..., + [[ + eventX1-r17 SEQUENCE { + x1-Threshold1-Relay-r17 SL-MeasTriggerQuantity-r16, + x1-Threshold2-r17 MeasTriggerQuantity, + reportOnLeave-r17 BOOLEAN, + hysteresis-r17 Hysteresis, + timeToTrigger-r17 TimeToTrigger, +``` + +``` + useAllowedCellList-r17 BOOLEAN + }, + eventX2-r17 SEQUENCE { + x2-Threshold-Relay-r17 SL-MeasTriggerQuantity-r16, + reportOnLeave-r17 BOOLEAN, + hysteresis-r17 Hysteresis, + timeToTrigger-r17 TimeToTrigger + }, + eventDl-r17 SEQUENCE { + distanceThreshFromReference1-r17 INTEGER(1.. 65525), + distanceThreshFromReference2-r17 INTEGER(1.. 65525), + referenceLocation1-r17 ReferenceLocation-r17, + referenceLocation2-r17 ReferenceLocation-r17, + reportOnLeave-r17 BOOLEAN, + hysteresisLocation-r17 HysteresisLocation-r17, + timeToTrigger-r17 TimeToTrigger + } +], +[[ + eventH1-r18 SEQUENCE { + h1-Threshold-r18 Altitude-r18, + h1-Hysteresis-r18 HysteresisAltitude-r18, + reportOnLeave-r18 BOOLEAN, + timeToTrigger-r18 TimeToTrigger, + includeAltitudeUE-r18 BOOLEAN, + simulMultiTriggerSingleMeasReport-r18 BOOLEAN + }, + eventH2-r18 SEQUENCE { + h2-Threshold-r18 Altitude-r18, + h2-Hysteresis-r18 HysteresisAltitude-r18, + reportOnLeave-r18 BOOLEAN, + timeToTrigger-r18 TimeToTrigger, + includeAltitudeUE-r18 BOOLEAN, + simulMultiTriggerSingleMeasReport-r18 BOOLEAN + }, + eventA3H1-r18 SEQUENCE { + a3-Offset-r18 MeasTriggerQuantityOffset, + reportOnLeave-r18 BOOLEAN, + a3-Hysteresis-r18 Hysteresis, + timeToTrigger-r18 TimeToTrigger, + useAllowedCellList-r18 BOOLEAN, + h1-Threshold-r18 Altitude-r18, + h1-Hysteresis-r18 HysteresisAltitude-r18, + includeAltitudeUE-r18 BOOLEAN, + simulMultiTriggerSingleMeasReport-r18 BOOLEAN + }, + eventA3H2-r18 SEQUENCE { + a3-Offset-r18 MeasTriggerQuantityOffset, + reportOnLeave-r18 BOOLEAN, + a3-Hysteresis-r18 Hysteresis, + timeToTrigger-r18 TimeToTrigger, +``` + +``` + + useAllowedCellList-r18 BOOLEAN, + h2-Threshold-r18 Altitude-r18, + h2-Hysteresis-r18 HysteresisAltitude-r18, + includeAltitudeUE-r18 BOOLEAN, + simulMultiTriggerSingleMeasReport-r18 BOOLEAN + }, + eventA4H1-r18 SEQUENCE { + a4-Threshold-r18 MeasTriggerQuantity, + reportOnLeave-r18 BOOLEAN, + a4-Hysteresis-r18 Hysteresis, + timeToTrigger-r18 TimeToTrigger, + useAllowedCellList-r18 BOOLEAN, + h1-Threshold-r18 Altitude-r18, + h1-Hysteresis-r18 HysteresisAltitude-r18, + includeAltitudeUE-r18 BOOLEAN, + simulMultiTriggerSingleMeasReport-r18 BOOLEAN + }, + eventA4H2-r18 SEQUENCE { + a4-Threshold-r18 MeasTriggerQuantity, + reportOnLeave-r18 BOOLEAN, + a4-Hysteresis-r18 Hysteresis, + timeToTrigger-r18 TimeToTrigger, + useAllowedCellList-r18 BOOLEAN, + h2-Threshold-r18 Altitude-r18, + h2-Hysteresis-r18 HysteresisAltitude-r18, + includeAltitudeUE-r18 BOOLEAN, + simulMultiTriggerSingleMeasReport-r18 BOOLEAN + }, + eventA5H1-r18 SEQUENCE { + a5-Threshold1-r18 MeasTriggerQuantity, + a5-Threshold2-r18 MeasTriggerQuantity, + reportOnLeave-r18 BOOLEAN, + a5-Hysteresis-r18 Hysteresis, + timeToTrigger-r18 TimeToTrigger, + useAllowedCellList-r18 BOOLEAN, + h1-Threshold-r18 Altitude-r18, + h1-Hysteresis-r18 HysteresisAltitude-r18, + includeAltitudeUE-r18 BOOLEAN, + simulMultiTriggerSingleMeasReport-r18 BOOLEAN + }, + eventA5H2-r18 SEQUENCE { + a5-Threshold1-r18 MeasTriggerQuantity, + a5-Threshold2-r18 MeasTriggerQuantity, + reportOnLeave-r18 BOOLEAN, + a5-Hysteresis-r18 Hysteresis, + timeToTrigger-r18 TimeToTrigger, + useAllowedCellList-r18 BOOLEAN, + h2-Threshold-r18 Altitude-r18, + h2-Hysteresis-r18 HysteresisAltitude-r18, + includeAltitudeUE-r18 BOOLEAN, + simulMultiTriggerSingleMeasReport-r18 BOOLEAN + } + +``` + +``` + + } + ]] +}, +rsType NR-RS-Type, +reportInterval ReportInterval, +reportAmount ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity}, +reportQuantityCell MeasReportQuantity, +maxReportCells INTEGER (1..maxCellReport), +reportQuantityRS-Indexes + MeasReportQuantity + OPTIONAL, -- Need R +maxNrofRS-IndexesToReport + INTEGER (1..maxNrofIndexesToReport) + OPTIONAL, -- Need R +includeBeamMeasurements + BOOLEAN, +reportAddNeighMeas ENUMERATED {setup} + OPTIONAL, -- Need R +... +[[ +measRSSI-ReportConfig-r16 + MeasRSSI-ReportConfig-r16 + OPTIONAL, -- Need R +useT312-r16 BOOLEAN + OPTIONAL, -- Need M +includeCommonLocationInfo-r16 + ENUMERATED {true} + OPTIONAL, -- Need R +includeBT-Meas-r16 SetupRelease {BT-NameList-r16} + OPTIONAL, -- Need M +includeWLAN-Meas-r16 SetupRelease {WLAN-NameList-r16} + OPTIONAL, -- Need M +includeSensor-Meas-r16 SetupRelease {Sensor-NameList-r16} + OPTIONAL, -- Need M +]], +[[ +coarseLocationRequest-r17 + ENUMERATED {true} + OPTIONAL, -- Need R +reportQuantityRelay-r17 + SL-MeasReportQuantity-r16 + OPTIONAL, -- Need R +]], +[[ +numberOfTriggeringCells-r18 + INTEGER (2..maxCellReport) + OPTIONAL, -- Need R +cellIndividualOffsetList-r18 + SEQUENCE (SIZE (1..maxNrofCellMeas)) OF CellIndividualOffsetList-r18 OPTIONAL -- Need R +]] +} + +PeriodicalReportConfig ::= + SEQUENCE { + rsType NR-RS-Type, + reportInterval ReportInterval, + reportAmount ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity}, + reportQuantityCell MeasReportQuantity, + maxReportCells INTEGER (1..maxCellReport), + reportQuantityRS-Indexes + MeasReportQuantity + OPTIONAL, -- Need R + maxNrofRS-IndexesToReport + INTEGER (1..maxNrofIndexesToReport) + OPTIONAL, -- Need R + includeBeamMeasurements + BOOLEAN, + useAllowedCellList BOOLEAN, + ... + [[ + measRSSI-ReportConfig-r16 + MeasRSSI-ReportConfig-r16 + OPTIONAL, -- Need R + includeCommonLocationInfo-r16 + ENUMERATED {true} + OPTIONAL, -- Need R + includeBT-Meas-r16 SetupRelease {BT-NameList-r16} + OPTIONAL, -- Need M + includeWLAN-Meas-r16 SetupRelease {WLAN-NameList-r16} + OPTIONAL, -- Need M + includeSensor-Meas-r16 SetupRelease {Sensor-NameList-r16} + OPTIONAL, -- Need M + ul-DelayValueConfig-r16 + SetupRelease { UL-DelayValueConfig-r16 } + OPTIONAL, -- Need M + reportAddNeighMeas-r16 ENUMERATED {setup} + OPTIONAL, -- Need R + ]], + +``` + +``` + +[[ + ul-ExcessDelayConfig-r17 SetupRelease { UL-ExcessDelayConfig-r17 } OPTIONAL, -- Need M + coarseLocationRequest-r17 ENUMERATED {true} OPTIONAL, -- Need R + reportQuantityRelay-r17 SL-MeasReportQuantity-r16 OPTIONAL, -- Need R +]] +} + +NR-RS-Type ::= ENUMERATED {ssb, csi-rs} + +MeasTriggerQuantity ::= CHOICE { + rsrp RSRP-Range, + rsrq RSQ-Range, + sinr SINR-Range +} + +MeasTriggerQuantityOffset ::= CHOICE { + rsrp INTEGER (-30..30), + rsrq INTEGER (-30..30), + sinr INTEGER (-30..30) +} + +MeasReportQuantity ::= SEQUENCE { + rsrp BOOLEAN, + rsrq BOOLEAN, + sinr BOOLEAN +} + +MeasRSSI-ReportConfig-r16 ::= SEQUENCE { + channelOccupancyThreshold-r16 RSSI-Range-r16 OPTIONAL -- Need R +} + +CLI-EventTriggerConfig-r16 ::= SEQUENCE { + eventId-r16 CHOICE { + eventI1-r16 SEQUENCE { + i1-Threshold-r16 MeasTriggerQuantityCLI-r16, + reportOnLeave-r16 BOOLEAN, + hysteresis-r16 Hysteresis, + timeToTrigger-r16 TimeToTrigger + }, + ... + }, + reportInterval-r16 ReportInterval, + reportAmount-r16 ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity}, + maxReportCLI-r16 INTEGER (1..maxCLI-Report-r16), + ... +} + +CLI-PeriodicalReportConfig-r16 ::= SEQUENCE { + reportInterval-r16 ReportInterval, + reportAmount-r16 ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity}, +} + +``` + +``` + reportQuantityCLI-r16 MeasReportQuantityCLI-r16, + maxReportCLI-r16 INTEGER (1..maxCLI-Report-r16), + ... +} + +RxTxPeriodical-r17 := SEQUENCE { + rxTxReportInterval-r17 OPTIONAL, -- Need R + reportAmount-r17 ENUMERATED {r1, infinity, spare6, spare5, spare4, spare3, spare2, spare1}, + ... +} + +RxTxReportInterval-r17 ::= ENUMERATED {ms80,ms120,ms160,ms240,ms320,ms480,ms640,ms1024,ms1280,ms2048,ms2560,ms5120,spare4,spare3,spare2,spare1} + +MeasTriggerQuantityCLI-r16 ::= CHOICE { + srs-RSRP-r16 SRS-RSRP-Range-r16, + cli-RSSI-r16 CLI-RSSI-Range-r16 +} + +MeasReportQuantityCLI-r16 ::= ENUMERATED {srs-rsrp, cli-rssi} + +ReportOnScellActivation-r18 ::= SEQUENCE { + rsType NR-RS-Type, + reportQuantityRS-Indexes MeasReportQuantity, + maxNrofRS-IndexesToReport INTEGER (1..maxNrofIndexesToReport), + includeBeamMeasurements BOOLEAN +} + +CellIndividualOffsetList-r18 ::= SEQUENCE { + physCellId-r18 PhysCellId, + cellIndividualOffset-r18 Q-OffsetRangeList +} + +-- TAG-REPORTCONFIGNR-STOP +-- ASN1STOP +``` + +| CondTriggerConfig field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| a3-Offset
Offset value(s) to be used in NR conditional reconfiguration triggering condition for cond event a3. The actual value is field value * 0.5 dB. | +| a4-Threshold
Threshold value associated to the selected trigger quantity (e.g. RSRP, RSRQ, SINR) per RS Type (e.g. SS/PBCH block, CSI-RS) to be used in NR conditional reconfiguration triggering condition for cond event a4. | +| a5-Threshold1/ a5-Threshold2
Threshold value associated to the selected trigger quantity (e.g. RSRP, RSRQ, SINR) per RS Type (e.g. SS/PBCH block, CSI-RS) to be used in NR conditional reconfiguration triggering condition for cond event a5. In the same condeventA5 , the network configures the same quantity for the MeasTriggerQuantity of the a5-Threshold1 and for the MeasTriggerQuantity of the a5-Threshold2 . | +| condEventId
Choice of NR conditional reconfiguration event triggered criteria. | +| distanceThreshFromReference1, distanceThreshFromReference2
Distance from a fixed reference location configured with referenceLocation1 or referenceLocation2 or a moving reference location determined by the UE based on referenceLocation1 or referenceLocation2 . Each step represents 50m. | +| duration
This field is used for defining the leaving condition T1-2 for conditional HO event condEventT1 . Each step represents 100ms. | +| nesEvent
Indicates the event is a NES-specific CHO event and the event is only considered to be satisfied if indication from lower layers is received indicating the applicability of NES-specific CHO event and the related entry condition(s) is fulfilled. This field can only be configured for condEventA3 , condEventA4 or condEventA5 . | +| referenceLocation1, referenceLocation2
Reference locations used for condEventD1 and condEventD2 . The referenceLocation1 is associated to serving cell and referenceLocation2 is associated to candidate target cell. | +| t1-Threshold
The field counts the number of UTC seconds in 10 ms units since 00:00:00 on Gregorian calendar date 1 January, 1900 (midnight between Sunday, December 31, 1899 and Monday, January 1, 1900). | +| timeToTrigger
Time during which specific criteria for the event needs to be met in order to execute the conditional reconfiguration evaluation. | + +| ReportConfigNR field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| reportType
Type of the configured measurement report. In MR-DC, network does not configure report of type reportCGI using SRB3. The condTriggerConfig is used for CHO, CPA or CPC configuration. | + +| ReportCGI field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| useAutonomousGaps
Indicates whether or not the UE is allowed to use autonomous gaps in acquiring system information from the NR neighbour cell. When the field is included, the UE applies the corresponding value for T321. | + +| EventTriggerConfig field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| a3-Offset/a6-Offset
Offset value(s) to be used in NR measurement report triggering condition for event a3/a6. The actual value is field value * 0.5 dB. | +| aN-ThresholdM
Threshold value associated to the selected trigger quantity (e.g. RSRP, RSRQ, SINR) per RS Type (e.g. SS/PBCH block, CSI-RS) to be used in NR measurement report triggering condition for event number aN. If multiple thresholds are defined for event number aN, the thresholds are differentiated by M. In the same eventA5 , eventA5H1 , eventA5H2 , the network configures the same quantity for the MeasTriggerQuantity of the a5-Threshold1 and for the MeasTriggerQuantity of the a5-Threshold2 . | +| channelOccupancyThreshold
RSSI threshold which is used for channel occupancy evaluation. | +| coarseLocationRequest
This field is used to request UE to report coarse location information. | +| distanceThreshFromReference1, distanceThreshFromReference2
Threshold value associated to the distance from a reference location configured with referenceLocation1 or referenceLocation2 . Each step represents 50m. | +| eventId
Choice of NR event triggered reporting criteria. | +| includeAltitudeUE
This field is used to request UE to report altitude information. | +| maxNrofRS-IndexesToReport
Max number of RS indexes to include in the measurement report for A1-A6 events. | +| maxReportCells
Max number of non-serving cells to include in the measurement report. | +| numberOfTriggeringCells
Indicates the number of cells detected that are required to fulfill an event for a measurement report to be triggered. This field is applicable only for the events concerning neighbor cells, i.e. eventA3 , eventA4 , eventA5 , eventA3H1 , eventA3H2 , eventA4H1 , eventA4H2 , eventA5H1 , eventA5H2 . | +| referenceLocation1, referenceLocation2
Reference locations used for eventD1 . The referenceLocation1 is associated to serving cell and referenceLocation2 is associated to neighbour cell. | +| reportAddNeighMeas
Indicates that the UE shall include the best neighbour cells per serving frequency. | +| reportAmount
Number of measurement reports applicable for eventTriggered as well as for periodical report types. | +| reportOnLeave
Indicates whether or not the UE shall initiate the measurement reporting procedure when the leaving condition is met for a cell in cellsTriggeredList , as specified in 5.5.4.1.
Indicates whether or not the UE shall initiate the measurement reporting procedure when the leaving condition is met if configured in eventD1 , eventH1 , eventH2 as specified in 5.5.4.1. | +| reportQuantityCell
The cell measurement quantities to be included in the measurement report. | +| reportQuantityRS-Indexes
Indicates which measurement information per RS index the UE shall include in the measurement report. | +| simulMultiTriggerSingleMeasReport
Indicates when multiple events of the same type satisfy the entering condition(s), whether to consider only the event with the smallest value between the altitude of the UE and the configured altitude threshold. | +| timeToTrigger
Time during which specific criteria for the event needs to be met in order to trigger a measurement report. | + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| useAllowedCellList | Indicates whether only the cells included in the allow-list of the associated measObject are applicable as specified in 5.5.4.1. | +| useT312 | If value TRUE is configured, the UE shall use the timer T312 with the value t312 as specified in the corresponding measObjectNR . If value FALSE is configured, the timer T312 is considered as disabled. Network configures value TRUE only if reportType is set to eventTriggered . | +| xN-ThresholdM | Threshold value associated to the selected trigger quantity (e.g. RSRP, RSRQ, SINR) per RS Type (e.g. SS/PBCH block, CSI-RS) to be used in NR measurement report triggering condition for event xN. If multiple thresholds are defined for event number xN, the thresholds are differentiated by M. x1-Threshold1 and x2-Threshold indicates the threshold value for the serving L2 U2N Relay UE, x1-Threshold2 indicates the threshold value for the NR Cells. | + +| CLI-EventTriggerConfig field descriptions | | +|--------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| i1-Threshold | Threshold value associated to the selected trigger quantity (e.g. SRS-RSRP, CLI-RSSI) to be used in CLI measurement report triggering condition for event i1. | +| eventId | Choice of CLI event triggered reporting criteria. | +| maxReportCLI | Max number of CLI measurement resource to include in the measurement report. | +| reportAmount | Number of measurement reports. | +| reportOnLeave | Indicates whether or not the UE shall initiate the measurement reporting procedure when the leaving condition is met for a CLI measurement resource in srsTriggeredList or rssiTriggeredList , as specified in 5.5.4.1. | +| timeToTrigger | Time during which specific criteria for the event needs to be met in order to trigger a measurement report. | + +| CLI-PeriodicalReportConfig field descriptions | | +|------------------------------------------------------|------------------------------------------------------------------------------| +| maxReportCLI | Max number of CLI measurement resource to include in the measurement report. | +| reportAmount | Number of measurement reports. | +| reportQuantityCLI | The CLI measurement quantities to be included in the measurement report. | + +| PeriodicalReportConfig field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| coarseLocationRequest
This field is used to request UE to report coarse location information. | +| maxNrofRS-IndexesToReport
Max number of RS indexes to include in the measurement report. | +| maxReportCells
Max number of non-serving cells to include in the measurement report. | +| reportAddNeighMeas
Indicates that the UE shall include the best neighbour cells per serving frequency. | +| reportAmount
Number of measurement reports applicable for eventTriggered as well as for periodical report types | +| reportQuantityCell
The cell measurement quantities to be included in the measurement report. | +| reportQuantityRS-Indexes
Indicates which measurement information per RS index the UE shall include in the measurement report. | +| ul-DelayValueConfig
If the field is present, the UE shall perform the actual UL PDCP Packet Average Delay measurement per DRB as specified in TS 38.314 [53] and the UE shall ignore the fields reportQuantityCell and maxReportCells . The applicable values for the corresponding reportInterval are (one of the) {ms120, ms240, ms480, ms640, ms1024, ms2048, ms5120, ms10240, ms20480, ms40960, min1,min6, min12, min30}. The reportInterval indicates the periodicity for performing and reporting of UL PDCP Packet Average Delay per DRB measurement as specified in TS 38.314 [53]. | +| ul-ExcessDelayConfig
If the field is present, the UE shall perform the actual UL PDCP Excess Packet Delay per DRB measurement as specified in TS 38.314 [53] and the UE shall ignore the fields reportQuantityCell and maxReportCells . The applicable values for the corresponding reportInterval are (one of the) {ms120, ms240, ms480, ms640, ms1024, ms2048, ms5120, ms10240, ms20480, ms40960, min1,min6, min12, min30}. The reportInterval indicates the periodicity for performing and reporting of UL PDCP Excess Packet Delay per DRB measurement as specified in TS 38.314 [53]. | +| useAllowedCellList
Indicates whether only the cells included in the allow-list of the associated measObject are applicable as specified in 5.5.4.1. | + +| ReportSFTD-NR field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| cellForWhichToReportSFTD
Indicates the target NR neighbour cells for SFTD measurement between PCell and NR neighbour cells. | +| drx-SFTD-NeighMeas
Indicates that the UE shall use available idle periods (i.e. DRX off periods) for the SFTD measurement in NR standalone. The network only includes drx-SFTD-NeighMeas field when reportSFTD-NeighMeas is set to true. | +| reportSFTD-Meas
Indicates whether UE is required to perform SFTD measurement between PCell and NR PCell in NR-DC. | +| reportSFTD-NeighMeas
Indicates whether UE is required to perform SFTD measurement between PCell and NR neighbour cells in NR standalone. The network does not include this field if reportSFTD-Meas is set to true . | +| reportRSRP
Indicates whether UE is required to include RSRP result of NR PCell or NR neighbour cells in SFTD measurement result, derived based on SSB. If it is set to true, the network should ensure that ssb-ConfigMobility is included in the measurement object for NR PCell or NR neighbour cells. | + +| RxTxPeriodical field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| reportAmount
This field indicates the number of UE Rx-Tx time difference measurement reports. If configured to r1 , the network does not configure rxTxReportInterval and only one measurement is reported. If configured to infinity , UE periodically reports measurements according to the periodicity configured by rxTxReportInterval . | +| rxTxReportInterval
This field indicates the measurement reporting periodicity of UE Rx-Tx time difference. | + +| other field descriptions | +|-----------------------------------------------------------------------------------------| +| MeasTriggerQuantity
SINR is applicable only for CONNECTED mode events. | + +| ReportOnScellActivation field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| rsType
Indicates which RS is used to provide the measurement result. Only value ssb can be set in this release. | +| reportQuantityRS-Indexes
Indicates which measurement information per RS index is used to sort the reported measurement results and is included in the measurement report. | +| maxNrofRS-IndexesToReport
Max number of RS indexes to include in the measurement report. | +| includeBeamMeasurements
Indicates whether to include the measurement result per RS index in the measurement report. | + +| CellIndividualOffsetList field descriptions | +|-----------------------------------------------------------------------------------------------------------| +| cellIndividualOffset
Cell individual offsets applicable to a specific measurement event. | +| physCellId
Physical cell identity of a cell in the cell list. | + +## — ***ReportConfigNR-SL*** + +The IE *ReportConfigNR-SL* specifies criteria for triggering of a CBR measurement reporting event for NR sidelink communication/discovery. Measurement reporting events are based on CBR measurement results on the corresponding transmission resource pools. These events are labelled CN with N equal to 1 and 2. + +Event C1: CBR of NR sidelink communication/discovery is above a threshold; + +Event C2: CBR of NR sidelink communication/discovery is below a threshold; + +#### **ReportConfigNR-SL information element** + +``` +-- ASN1START +-- TAG-REPORTCONFIGNR-SL-START + +ReportConfigNR-SL-r16 ::= + reportType-r16 + periodical-r16 + eventTriggered-r16 + } +} + +EventTriggerConfigNR-SL-r16 ::= + eventId-r16 + eventC1 + c1-Threshold-r16 + hysteresis-r16 + timeToTrigger-r16 + }, + eventC2-r16 + c2-Threshold-r16 + hysteresis-r16 + timeToTrigger-r16 + }, + ... +}, + reportInterval-r16 + reportAmount-r16 + reportQuantity-r16 + ... +} + +PeriodicalReportConfigNR-SL-r16 ::= + reportInterval-r16 + reportAmount-r16 + reportQuantity-r16 + ... +} + +MeasReportQuantity-r16 ::= + cbr-r16 + ... +} + +-- TAG-REPORTCONFIGNR-SL-STOP +-- ASN1STOP +``` + +| ReportConfigNR-SL field descriptions | +|-------------------------------------------------------------------------------------------------------------| +| reportType
Type of the configured CBR measurement report for NR sidelink communication/discovery. | + +| EventTriggerConfigNR-SL field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| cN-Threshold
Threshold used for events C1 and C2 specified in clauses 5.5.4.11 and 5.5.4.12, respectively. | +| eventId
Choice of NR event triggered reporting criteria. | +| reportAmount
Number of measurement reports applicable for eventTriggered as well as for periodical report types. | +| reportQuantity
The sidelink measurement quantities to be included in the measurement report. In this release, this is set as the CBR measurement result. | +| timeToTrigger
Time during which specific criteria for the event needs to be met in order to trigger a measurement report. | + +| PeriodicalReportConfigNR-SL field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| reportAmount
Number of measurement reports applicable for eventTriggered as well as for periodical report types. | +| reportQuantity
The sidelink measurement quantities to be included in the measurement report. In this release, this is set as the CBR measurement result. | + +### — *ReportConfigToAddModList* + +The IE *ReportConfigToAddModList* concerns a list of reporting configurations to add or modify. + +#### ReportConfigToAddModList information element + +``` +-- ASN1START +-- TAG-REPORTCONFIGTOADDMODLIST-START + +ReportConfigToAddModList ::= SEQUENCE (SIZE (1..maxReportConfigId)) OF ReportConfigToAddMod +ReportConfigToAddMod ::= SEQUENCE { + reportConfigId ReportConfigId, + reportConfig CHOICE { + reportConfigNR ReportConfigNR, + ... + reportConfigInterRAT ReportConfigInterRAT, + reportConfigNR-SL-r16 ReportConfigNR-SL-r16 + } +} +``` + +``` +-- TAG-REPORTCONFIGADDMODLIST-STOP +-- ASN1STOP +``` + +### – *ReportInterval* + +The IE *ReportInterval* indicates the interval between periodical reports. The *ReportInterval* is applicable if the UE performs periodical reporting (i.e. when *reportAmount* exceeds 1) when *reportType* is set to either *eventTriggered*, *periodical*, *cli-EventTriggered* or *cli-Periodical*. Value *ms120* corresponds to 120 ms, value *ms240* corresponds to 240 ms and so on, while value *min1* corresponds to 1 min, *min6* corresponds to 6 min and so on. + +#### ***ReportInterval* information element** + +``` +-- ASN1START +-- TAG-REPORTINTERVAL-START + +ReportInterval ::= ENUMERATED {ms120, ms240, ms480, ms640, ms1024, ms2048, ms5120, ms10240, ms20480, ms40960, + min1,min6, min12, min30 } + +-- TAG-REPORTINTERVAL-STOP +-- ASN1STOP +``` + +#### – *ReselectionThreshold* + +The IE *ReselectionThreshold* is used to indicate an Rx level threshold for cell reselection. Actual value of threshold = field value \* 2 [dB]. + +#### ***ReselectionThreshold* information element** + +``` +-- ASN1START +-- TAG-RESELECTIONTHRESHOLD-START + +ReselectionThreshold ::= INTEGER (0..31) + +-- TAG-RESELECTIONTHRESHOLD-STOP +-- ASN1STOP +``` + +#### – *ReselectionThresholdQ* + +The IE *ReselectionThresholdQ* is used to indicate a quality level threshold for cell reselection. Actual value of threshold = field value [dB]. + +#### ***ReselectionThresholdQ* information element** + +``` +-- ASN1START +-- TAG-RESELECTIONTHRESHOLDQ-START +``` + +``` + +ReselectionThresholdQ ::= INTEGER (0..31) + +-- TAG-RESELECTIONTHRESHOLDQ-STOP +-- ASN1STOP + +``` + +### – *ResumeCause* + +The IE *ResumeCause* is used to indicate the resume cause in *RRResumeRequest*, *RRResumeRequest1* and *UEAssistanceInformation*. + +#### ***ResumeCause* information element** + +``` + +-- ASN1START +-- TAG-RESUMECAUSE-START + +ResumeCause ::= ENUMERATED {emergency, highPriorityAccess, mt-Access, mo-Signalling, + mo-Data, mo-VoiceCall, mo-VideoCall, mo-SMS, rna-Update, mps-PriorityAccess, + mcs-PriorityAccess, mt-SDT, srs-PosConfigOrActivationReq-v1800, spare3, spare2, spare1 } + +-- TAG-RESUMECAUSE-STOP +-- ASN1STOP + +``` + +### – *RLC-BearerConfig* + +The IE *RLC-BearerConfig* is used to configure an RLC entity, a corresponding logical channel in MAC and the linking to a PDCP entity (served radio bearer). + +#### ***RLC-BearerConfig* information element** + +``` + +-- ASN1START +-- TAG-RLC-BEARERCONFIG-START + +RLC-BearerConfig ::= SEQUENCE { + logicalChannelIdentity LogicalChannelIdentity, + servedRadioBearer CHOICE { + srb-Identity SRB-Identity, + drb-Identity DRB-Identity + } + reestablishRLC ENUMERATED {true} + rlc-Config RLC-Config + mac-LogicalChannelConfig LogicalChannelConfig + ... + [[ + rlc-Config-v1610 RLC-Config-v1610 + ]], + [[ + rlc-Config-v1700 RLC-Config-v1700 + logicalChannelIdentityExt-r17 LogicalChannelIdentityExt-r17 + ]], + OPTIONAL, -- Cond LCH-SetupOnly + OPTIONAL, -- Need N + OPTIONAL, -- Cond LCH-Setup + OPTIONAL, -- Cond LCH-Setup + OPTIONAL, -- Need R + OPTIONAL, -- Need R + OPTIONAL, -- Cond LCH-SetupModMRB +} + +``` + +``` + + multicastRLC-BearerConfig-r17 MulticastRLC-BearerConfig-r17 OPTIONAL, -- Cond LCH-SetupOnlyMRB + servedRadioBearerSRB4-r17 SRB-Identity-v1700 OPTIONAL -- Need N + ]] + } + + MulticastRLC-BearerConfig-r17 ::= SEQUENCE { + servedMBS-RadioBearer-r17 MRB-Identity-r17, + isPTM-Entity-r17 ENUMERATED {true} OPTIONAL -- Need S + } + + LogicalChannelIdentityExt-r17 ::= INTEGER (320..65855) + + -- TAG-RLC-BEARERCONFIG-STOP + -- ASN1STOP + +``` + +#### RLC-BearerConfig field descriptions + +| | | +|-------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| isPTM-Entity | If configured, indicates that the RLC entity is used for PTM reception. When the field is absent the RLC entity is used for PTP transmission/reception. | +| logicalChannelIdentity | ID used commonly for the MAC logical channel and for the RLC bearer. Value 4 is not configured for DRBs if SRB4 is configured. | +| logicalChannelIdentityExt | Extended logical channel ID used commonly for the MAC logical channel and for the RLC bearer for PTM reception. If this field is configured, the UE shall ignore logicalChannelIdentity . | +| reestablishRLC | Indicates that RLC should be re-established. Network sets this to true at least whenever the security key used for the radio bearer associated with this RLC entity changes. For SRB2, multicast MRBs and DRBs, unless full configuration is used, it is also set to true during the resumption of the RRC connection or the first reconfiguration after reestablishment. For SRB1, when resuming an RRC connection, or at the first reconfiguration after RRC connection reestablishment, the network does not set this field to true . The network does not include this field if the RLC-BearerConfig IE is part of an RRCREconfiguration message within the LTM-Config IE | +| rlc-Config | Determines the RLC mode (UM, AM) and provides corresponding parameters. RLC mode reconfiguration can only be performed by DRB/multicast MRB release/addition or full configuration. The network may configure rlc-Config-v1610 only when rlc-Config (without suffix) is set to am . | +| servedMBS-RadioBearer | Associates the RLC Bearer with a multicast MRB. The UE shall deliver DL RLC SDUs received via the RLC entity of this RLC bearer to the PDCP entity of the servedMBS-RadioBearer . | +| servedRadioBearer, servedRadioBearerSRB4 | Associates the RLC Bearer with an SRB or a DRB. The UE shall deliver DL RLC SDUs received via the RLC entity of this RLC bearer to the PDCP entity of the servedRadioBearer . Furthermore, the UE shall advertise and deliver uplink PDCP PDUs of the uplink PDCP entity of the servedRadioBearer to the uplink RLC entity of this RLC bearer unless the uplink scheduling restrictions ( moreThanOneRLC in PDCP-Config and the restrictions in LogicalChannelConfig ) forbid it to do so. | + +| Conditional Presence | Explanation | +|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| LCH-Setup | This field is mandatory present upon creation of a new logical channel for a DRB or a multicast MRB or SRB4. This field is optionally present, Need S, upon creation of a new logical channel for an SRB except SRB4. It is optionally present, Need M, otherwise. | +| LCH-SetupModMRB | This field is optionally present upon creation of a new logical channel for PTM reception for a multicast MRB. If this field is included upon creation of a new logical channel for PTM reception for a multicast MRB, it shall be present when modifying this logical channel. The field is absent for logical channels configured for an SRB and a DRB. | +| LCH-SetupOnly | This field is mandatory present upon creation of a new logical channel for a DRB or an SRB ( servedRadioBearer ). It is absent, Need M otherwise. | +| LCH-SetupOnlyMRB | This field is mandatory present upon creation of a new logical channel for a multicast MRB and upon modification of MRB-Identity of the served MRB. It is absent, Need M otherwise. | + +### — *RLC-Config* + +The IE *RLC-Config* is used to specify the RLC configuration of SRBs, multicast MRBs and DRBs. + +#### *RLC-Config* information element + +``` +-- ASN1START +-- TAG-RLC-CONFIG-START + +RLC-Config ::= + am + ul-AM-RLC + dl-AM-RLC + }, + um-Bi-Directional + ul-UM-RLC + dl-UM-RLC + }, + um-Uni-Directional-UL + ul-UM-RLC + }, + um-Uni-Directional-DL + dl-UM-RLC + }, + ... +} + +UL-AM-RLC ::= + sn-FieldLength + t-PollRetransmit + pollPDU + pollByte + maxRetxThreshold + CHOICE { + SEQUENCE { + UL-AM-RLC, + DL-AM-RLC + } + SEQUENCE { + UL-UM-RLC, + DL-UM-RLC + } + SEQUENCE { + UL-UM-RLC + } + SEQUENCE { + DL-UM-RLC + } + } + + SEQUENCE { + SN-FieldLengthAM + T-PollRetransmit + PollPDU, + PollByte, + ENUMERATED { t1, t2, t3, t4, t6, t8, t16, t32 } + } + +DL-AM-RLC ::= + SEQUENCE { +``` + +``` + +sn-FieldLength SN-FieldLengthAM OPTIONAL, -- Cond Reestab +t-Reassembly T-Reassembly, +t-StatusProhibit T-StatusProhibit +} + +UL-UM-RLC ::= SEQUENCE { + sn-FieldLength SN-FieldLengthUM OPTIONAL -- Cond Reestab +} + +DL-UM-RLC ::= SEQUENCE { + sn-FieldLength SN-FieldLengthUM OPTIONAL, -- Cond Reestab + t-Reassembly T-Reassembly +} + +T-PollRetransmit ::= ENUMERATED { + ms5, ms10, ms15, ms20, ms25, ms30, ms35, + ms40, ms45, ms50, ms55, ms60, ms65, ms70, + ms75, ms80, ms85, ms90, ms95, ms100, ms105, + ms110, ms115, ms120, ms125, ms130, ms135, + ms140, ms145, ms150, ms155, ms160, ms165, + ms170, ms175, ms180, ms185, ms190, ms195, + ms200, ms205, ms210, ms215, ms220, ms225, + ms230, ms235, ms240, ms245, ms250, ms300, + ms350, ms400, ms450, ms500, ms800, ms1000, + ms2000, ms4000, ms1-v1610, ms2-v1610, ms3-v1610, + ms4-v1610, spare1} + +PollPDU ::= ENUMERATED { + p4, p8, p16, p32, p64, p128, p256, p512, p1024, p2048, p4096, p6144, p8192, p12288, p16384, p20480, + p24576, p28672, p32768, p40960, p49152, p57344, p65536, infinity, spare8, spare7, spare6, spare5, spare4, + spare3, spare2, spare1} + +PollByte ::= ENUMERATED { + kB1, kB2, kB5, kB8, kB10, kB15, kB25, kB50, kB75, + kB100, kB125, kB250, kB375, kB500, kB750, kB1000, + kB1250, kB1500, kB2000, kB3000, kB4000, kB4500, + kB5000, kB5500, kB6000, kB6500, kB7000, kB7500, + mB8, mB9, mB10, mB11, mB12, mB13, mB14, mB15, + mB16, mB17, mB18, mB20, mB25, mB30, mB40, infinity, + spare20, spare19, spare18, spare17, spare16, + spare15, spare14, spare13, spare12, spare11, + spare10, spare9, spare8, spare7, spare6, spare5, + spare4, spare3, spare2, spare1} + +T-Reassembly ::= ENUMERATED { + ms0, ms5, ms10, ms15, ms20, ms25, ms30, ms35, + ms40, ms45, ms50, ms55, ms60, ms65, ms70, + ms75, ms80, ms85, ms90, ms95, ms100, ms110, + ms120, ms130, ms140, ms150, ms160, ms170, + ms180, ms190, ms200, spare1} + +``` + +``` + +T-StatusProhibit := ENUMERATED { + ms0, ms5, ms10, ms15, ms20, ms25, ms30, ms35, + ms40, ms45, ms50, ms55, ms60, ms65, ms70, + ms75, ms80, ms85, ms90, ms95, ms100, ms105, + ms110, ms115, ms120, ms125, ms130, ms135, + ms140, ms145, ms150, ms155, ms160, ms165, + ms170, ms175, ms180, ms185, ms190, ms195, + ms200, ms205, ms210, ms215, ms220, ms225, + ms230, ms235, ms240, ms245, ms250, ms300, + ms350, ms400, ms450, ms500, ms800, ms1000, + ms1200, ms1600, ms2000, ms2400, spare2, spare1} + +SN-FieldLengthUM := ENUMERATED {size6, size12} +SN-FieldLengthAM := ENUMERATED {size12, size18} + +RLC-Config-v1610 := SEQUENCE { + dl-AM-RLC-v1610 + } + +RLC-Config-v1700 := SEQUENCE { + dl-AM-RLC-v1700, + dl-UM-RLC-v1700 + } + +DL-AM-RLC-v1610 := SEQUENCE { + t-StatusProhibit-v1610 OPTIONAL, -- Need R + ... + } + +DL-AM-RLC-v1700 := SEQUENCE { + t-ReassemblyExt-r17 OPTIONAL -- Need R + } + +DL-UM-RLC-v1700 := SEQUENCE { + t-ReassemblyExt-r17 OPTIONAL -- Need R + } + +T-StatusProhibit-v1610 := ENUMERATED { ms1, ms2, ms3, ms4, spare4, spare3, spare2, spare1} + +T-ReassemblyExt-r17 := ENUMERATED {ms210, ms220, ms340, ms350, ms550, ms1100, ms1650, ms2200} + +-- TAG-RLC-CONFIG-STOP +-- ASN1STOP + +``` + +| RLC-Config field descriptions | | +|--------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| maxRetxThreshold | Parameter for RLC AM in TS 38.322 [4]. Value t1 corresponds to 1 retransmission, value t2 corresponds to 2 retransmissions and so on. | +| pollByte | Parameter for RLC AM in TS 38.322 [4]. Value kB25 corresponds to 25 kBytes, value kB50 corresponds to 50 kBytes and so on. infinity corresponds to an infinite amount of kBytes. | +| pollPDU | Parameter for RLC AM in TS 38.322 [4]. Value p4 corresponds to 4 PDUs, value p8 corresponds to 8 PDUs and so on. infinity corresponds to an infinite number of PDUs. | +| sn-FieldLength | Indicates the RLC SN field size, see TS 38.322 [4], in bits. Value size6 means 6 bits, value size12 means 12 bits, value size18 means 18 bits. The value of sn-FieldLength of an RLC entity for the DRB/multicast MRB shall be changed only using reconfiguration with sync. The network configures only value size12 in SN-FieldLengthAM for SRB. | +| t-PollRetransmit | Timer for RLC AM in TS 38.322 [4], in milliseconds. Value ms5 means 5 ms, value ms10 means 10 ms and so on. | +| t-Reassembly, t-ReassemblyExt | Timer for reassembly in TS 38.322 [4], in milliseconds. Value ms0 means 0 ms, value ms5 means 5 ms and so on. If t-ReassemblyExt-r17 is configured, the UE shall ignore t-Reassembly (without suffix). | +| t-StatusProhibit | Timer for status reporting in TS 38.322 [4], in milliseconds. Value ms0 means 0 ms, value ms5 means 5 ms and so on. If t-StatusProhibit-v1610 is present, the UE shall ignore t-StatusProhibit (without suffix). | + +| Conditional Presence | Explanation | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| Reestab | The field is mandatory present at RLC bearer setup. It is optionally present, need M, at RLC re-establishment. Otherwise it is absent. Need M. | + +### – *RLF-TimersAndConstants* + +The IE *RLF-TimersAndConstants* is used to configure UE specific timers and constants. + +#### ***RLF-TimersAndConstants* information element** + +``` +-- ASN1START +-- TAG-RLF-TIMERSANDCONSTANTS-START + +RLF-TimersAndConstants ::= SEQUENCE { + t310 ENUMERATED {ms0, ms50, ms100, ms200, ms500, ms1000, ms2000, ms4000, ms6000}, + n310 ENUMERATED {n1, n2, n3, n4, n6, n8, n10, n20}, + n311 ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10}, + ... + [[ + t311 ENUMERATED {ms1000, ms3000, ms5000, ms10000, ms15000, ms20000, ms30000} + ]] +} +``` + +``` +-- TAG-RLF-TIMERSANDCONSTANTS-STOP +-- ASN1STOP +``` + +#### | RLF-TimersAndConstants field descriptions | |---------------------------------------------------------------------------------------------------------------------------------------------------| | n3xy
Constants are described in clause 7.3. Value n1 corresponds to 1, value n2 corresponds to 2 and so on. | | t3xy
Timers are described in clause 7.1. Value ms0 corresponds to 0 ms, value ms50 corresponds to 50 ms and so on. | + +## — ***RNTI-Value*** + +The IE *RNTI-Value* represents a Radio Network Temporary Identity. + +#### ***RNTI-Value* information element** + +``` +-- ASN1START +-- TAG-RNTI-VALUE-START + +RNTI-Value ::= INTEGER (0..65535) + +-- TAG-RNTI-VALUE-STOP +-- ASN1STOP +``` + +### — ***RSRP-Range*** + +The IE *RSRP-Range* specifies the value range used in RSRP measurements and thresholds. For measurements, integer value for RSRP measurements is according to Table 10.1.6.1-1 in TS 38.133 [14]. For thresholds, the actual value is (IE value – 156) dBm, except for the IE value 127, in which case the actual value is infinity. + +#### ***RSRP-Range* information element** + +``` +-- ASN1START +-- TAG-RSRP-RANGE-START + +RSRP-Range ::= INTEGER (0..127) + +-- TAG-RSRP-RANGE-STOP +-- ASN1STOP +``` + +### — *RSRQ-Range* + +The IE *RSRQ-Range* specifies the value range used in RSRQ measurements and thresholds. For measurements, integer value for RSRQ measurements is according to Table 10.1.11.1-1 in TS 38.133 [14]. For thresholds, the actual value is (IE value – 87) / 2 dB. + +#### *RSRQ-Range* information element + +``` +-- ASN1START +-- TAG-RSRQ-RANGE-START + +RSRQ-Range ::= INTEGER(0..127) + +-- TAG-RSRQ-RANGE-STOP +-- ASN1STOP +``` + +### — *RSSI-Range* + +The IE *RSSI-Range* specifies the value range used in RSSI measurements and thresholds for NR operation with shared spectrum channel access. The integer value for RSSI measurements is according to Table 10.1.34.3-1 in TS 38.133 [14]. + +#### *RSSI-Range* information element + +``` +-- ASN1START +-- TAG-RSSI-RANGE-START + +RSSI-Range-r16 ::= INTEGER(0..76) + +-- TAG-RSSI-RANGE-STOP +-- ASN1STOP +``` + +### — *RxTxTimeDiff* + +The IE *RxTxTimeDiff* contains the Rx-Tx time difference measurement at either the UE or the gNB. + +#### *RxTxTimeDiff* information element + +``` +-- ASN1START +-- TAG-RXTXTIMEDIFF-START + +RxTxTimeDiff-r17 ::= SEQUENCE { + result-k5-r17 INTEGER (0..61565) OPTIONAL, -- Need N + ... +} + +-- TAG-RXTXTIMEDIFF-STOP +``` + +``` +-- ASN1STOP +``` + +#### | RxTxTimeDiff field descriptions | |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| |

result-k5
This field indicates the Rx-Tx time difference measurement, see TS 38.215 [9], clause 10.1.25.3.1 of TS 38.133 [14] for UE Rx-Tx time difference and clause 13.2.1 of TS 38.133 [14] for gNB Rx-Tx time difference.

| + +### – ***SCellActivationRS-Config*** + +The IE ***SCellActivationRS-Config*** is used to configure a Reference Signal for fast activation of the SCell where the IE is included (see TS 38.214 [19], clause 5.2.1.5.3. Usage of an ***SCellActivationRS-Config*** is indicated by including its ***scellActivationRS-Id*** in the Enhanced SCell activation MAC CE (see TS 38.321 [3] clause 6.1.3.55). + +#### ***SCellActivationRS-Config* information element** + +``` +-- ASN1START +``` + +``` +-- TAG-CELLACTIVATIONRS-CONFIG-START +``` + +``` +SCellActivationRS-Config-r17 ::= SEQUENCE { + scellActivationRS-Id-r17 SCellActivationRS-ConfigId-r17, + resourceSet-r17 NZP-CSI-RS-ResourceSetId, + gapBetweenBursts-r17 INTEGER (2..31) OPTIONAL, -- Need R + qcl-Info-r17 TCI-StateId, + ... +} +``` + +``` +-- TAG-CELLACTIVATIONRS-CONFIG-STOP +``` + +``` +-- ASN1STOP +``` + +#### | SCellActivationRS-Config field descriptions | |-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| |

gapBetweenBursts
When this field is present, there are two bursts and it indicates the gap between the two bursts in number of slots. When this field is absent, there is a single burst.

| |

qcl-Info
Reference to TCI-State for providing the QCL source and QCL type for each NZP-CSI-RS-Resource listed in nzp-CSI-RS-Resources of the NZP-CSI-RS-ResourceSet indicated by resourceSet (see TS 38.214 [19], clause 5.1.6.1.1.1). TCI-StateId refers to the TCI-State which has this value for tci-StateId and is defined in tci-StatesToAddModList or dl-OrJointTCI-StateList in the PDSCH-Config included in the BWP-Downlink of this serving cell indicated by firstActiveDownlinkBWP-Id in the ServingCellConfig in which this IE is included.

| |

resourceSet
nzp-CSI-ResourceSetId of the NZP-CSI-RS-ResourceSet of this serving cell used as resource configuration for one or two bursts for SCell activation. This NZP-CSI-RS-ResourceSet consists of four NZP CSI-RS resources in two consecutive slots with two NZP CSI-RS resources in each slot (see TS 38.214 [19], clause 5.1.6.1.1.1). The CSI-RS associated with this NZP-CSI-RS-ResourceSet are located in the BWP addressed by firstActiveDownlinkBWP-Id.

| + +## — *SCellActivationRS-ConfigId* + +The IE *SCellActivationRS-ConfigId* is used to identify one *SCellActivationRS-Config*. + +#### ***SCellActivationRS-ConfigId* information element** + +``` +-- ASN1START +-- TAG-SCELLACTIVATIONRS-CONFIGID-START + +SCellActivationRS-ConfigId-r17 ::= INTEGER (1.. maxNrofSCellActRS-r17) + +-- TAG-SCELLACTIVATIONRS-CONFIGID-STOP +-- ASN1STOP +``` + +## — *SCellIndex* + +The IE *SCellIndex* concerns a short identity, used to identify an SCell. The value range is shared across the Cell Groups. + +#### ***SCellIndex* information element** + +``` +-- ASN1START +-- TAG-SCELLINDEX-START + +SCellIndex ::= INTEGER (1..31) + +-- TAG-SCELLINDEX-STOP +-- ASN1STOP +``` + +## — *SchedulingRequestConfig* + +The IE *SchedulingRequestConfig* is used to configure the parameters, for the dedicated scheduling request (SR) resources. + +#### ***SchedulingRequestConfig* information element** + +``` +-- ASN1START +-- TAG-SCHEDULINGREQUESTCONFIG-START + +SchedulingRequestConfig ::= SEQUENCE { + schedulingRequestToAddModList SEQUENCE (SIZE (1..maxNrofSR-ConfigPerCellGroup)) OF SchedulingRequestToAddMod + OPTIONAL, -- Need N + schedulingRequestToReleaseList SEQUENCE (SIZE (1..maxNrofSR-ConfigPerCellGroup)) OF SchedulingRequestId + OPTIONAL -- Need N +} + +SchedulingRequestToAddMod ::= SEQUENCE { +``` + +``` + + schedulingRequestId SchedulingRequestId, + sr-ProhibitTimer ENUMERATED {ms1, ms2, ms4, ms8, ms16, ms32, ms64, ms128} OPTIONAL, -- Need S + sr-TransMax ENUMERATED { n4, n8, n16, n32, n64, spare3, spare2, spare1} +} + +SchedulingRequestConfig-v1700 ::= SEQUENCE { + schedulingRequestToAddModListExt-v1700 SEQUENCE (SIZE (1..maxNrofSR-ConfigPerCellGroup)) OF SchedulingRequestToAddModExt-v1700 + OPTIONAL -- Need N +} + +SchedulingRequestToAddModExt-v1700 ::= SEQUENCE { + sr-ProhibitTimer-v1700 ENUMERATED { ms192, ms256, ms320, ms384, ms448, ms512, ms576, ms640, ms1082, spare7, spare6, spare5, + spare4, spare3, spare2, spare1} + OPTIONAL -- Need R +} + +-- TAG-SCHEDULINGREQUESTCONFIG-STOP +-- ASN1STOP + +``` + +#### ***SchedulingRequestConfig* field descriptions** + +| | | +|-------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| schedulingRequestToAddModList, schedulingRequestToAddModListExt | List of Scheduling Request configurations to add or modify. If schedulingRequestToAddModListExt is configured, it contains the same number of entries, and in the same order, as schedulingRequestToAddModList . | +| schedulingRequestToReleaseList | List of Scheduling Request configurations to release. | + +#### ***SchedulingRequestToAddMod* field descriptions** + +| | | +|-----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| schedulingRequestId | Used to modify a SR configuration and to indicate, in LogicalChannelConfig , the SR configuration to which a logical channel is mapped and to indicate, in SchedulingRequestresourceConfig , the SR configuration for which a scheduling request resource is used. | +| sr-ProhibitTimer | Timer for SR transmission on PUCCH in TS 38.321 [3]. Value is in ms. Value ms1 corresponds to 1ms, value ms2 corresponds to 2ms, and so on. If sr-ProhibitTimer-v1700 is configured, UE shall ignore sr-ProhibitTimer (without suffix). If both sr-ProhibitTimer (without suffix) and sr-ProhibitTimer-v1700 are absent, the UE applies the value 0. | +| sr-TransMax | Maximum number of SR transmissions as described in TS 38.321 [3]. Value n4 corresponds to 4, value n8 corresponds to 8, and so on. | + +#### — ***SchedulingRequestId*** + +The IE *SchedulingRequestId* is used to identify a Scheduling Request instance in the MAC layer. + +#### ***SchedulingRequestId* information element** + +``` +-- ASN1START +``` + +``` +-- TAG-SCHEDULINGREQUESTID-START + +SchedulingRequestId ::= INTEGER (0..7) + +-- TAG-SCHEDULINGREQUESTID-STOP +-- ASN1STOP +``` + +### — *SchedulingRequestResourceConfig* + +The IE *SchedulingRequestResourceConfig* determines physical layer resources on PUCCH where the UE may send the dedicated scheduling request (D-SR) (see TS 38.213 [13], clause 9.2.4). + +#### *SchedulingRequestResourceConfig* information element + +``` +-- ASN1START +-- TAG-SCHEDULINGREQUESTRESOURCECONFIG-START + +SchedulingRequestResourceConfig ::= SEQUENCE { + schedulingRequestResourceId SchedulingRequestResourceId, + schedulingRequestId SchedulingRequestId, + periodicityAndOffset CHOICE { + sym2 NULL, + sym6or7 NULL, + sl1 NULL, -- Recurs in every slot + sl2 INTEGER (0..1), + sl4 INTEGER (0..3), + sl5 INTEGER (0..4), + sl8 INTEGER (0..7), + sl10 INTEGER (0..9), + sl16 INTEGER (0..15), + sl20 INTEGER (0..19), + sl40 INTEGER (0..39), + sl80 INTEGER (0..79), + sl160 INTEGER (0..159), + sl320 INTEGER (0..319), + sl640 INTEGER (0..639) + } + resource PUCCH-ResourceId OPTIONAL, -- Need M +} OPTIONAL -- Need M + +SchedulingRequestResourceConfigExt-v1610 ::= SEQUENCE { + phy-PriorityIndex-r16 ENUMERATED {p0, p1} OPTIONAL, -- Need M + ... +} + +SchedulingRequestResourceConfigExt-v1700 ::= SEQUENCE { + periodicityAndOffset-r17 CHOICE { + sl1280 INTEGER (0..1279), +``` + +``` + + s12560 INTEGER (0..2559), + s15120 INTEGER (0..5119) + } +} +-- TAG-SCHEDULINGREQUESTRESOURCECONFIG-STOP +-- ASN1STOP + +``` + +OPTIONAL -- Need M + +#### SchedulingRequestResourceConfig field descriptions + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

periodicityAndOffset
SR periodicity and offset in number of symbols or slots (see TS 38.213 [13], clause 9.2.4) The following periodicities may be configured depending on the chosen subcarrier spacing:
SCS = 15 kHz: 2sym, 7sym, 1sl, 2sl, 4sl, 5sl, 8sl, 10sl, 16sl, 20sl, 40sl, 80sl
SCS = 30 kHz: 2sym, 7sym, 1sl, 2sl, 4sl, 5sl, 8sl, 10sl, 16sl, 20sl, 40sl, 80sl, 160sl
SCS = 60 kHz: 2sym, 7sym/6sym, 1sl, 2sl, 4sl, 8sl, 16sl, 20sl, 40sl, 80sl, 160sl, 320sl
SCS = 120 kHz: 2sym, 7sym, 1sl, 2sl, 4sl, 5sl, 8sl, 10sl, 16sl, 40sl, 80sl, 160sl, 320sl, 640sl
SCS = 480 kHz: 1sl, 2sl, 4sl, 8sl, 16sl, 40sl, 80sl, 160sl, 320sl, 640sl, 1280sl, 2560sl
SCS = 960 kHz: 1sl, 2sl, 4sl, 8sl, 16sl, 40sl, 80sl, 160sl, 320sl, 640sl, 1280sl, 2560sl, 5120sl

sym6or7 corresponds to 6 symbols if extended cyclic prefix and a SCS of 60 kHz are configured, otherwise it corresponds to 7 symbols.
For periodicities 2sym, 7sym and sl1 the UE assumes an offset of 0 slots.
If periodicityAndOffset-r17 is present, any previously configured periodicityAndOffset (without suffix) is released, and vice versa.
UE indicates support of the following SR periodicities in additionalSR-Periodicities (see TS 38.306, clause 4.2.6):
SCS = 30 kHz: 5sl
SCS = 120 kHz: 5sl, 10sl

| +|

phy-PriorityIndex
Indicates whether this scheduling request resource is high or low priority in PHY prioritization/multiplexing handling (see TS 38.213 [13], clause 9.2.4). Value p0 indicates low priority and value p1 indicates high priority.

| +|

resource
ID of the PUCCH resource in which the UE shall send the scheduling request. The actual PUCCH-Resource is configured in PUCCH-Config of the same UL BWP and serving cell as this SchedulingRequestResourceConfig. The network configures a PUCCH-Resource of PUCCH-format0 or PUCCH-format1 (other formats not supported) (see TS 38.213 [13], clause 9.2.4)

| +|

schedulingRequestID
The ID of the SchedulingRequestConfig that uses this scheduling request resource.

| + +#### SchedulingRequestResourceId + +The IE *SchedulingRequestResourceId* is used to identify scheduling request resources on PUCCH. + +#### SchedulingRequestResourceId information element + +``` + +-- ASN1START +-- TAG-SCHEDULINGREQUESTRESOURCEID-START + +``` + +``` +SchedulingRequestResourceId ::= INTEGER (1..maxNrofSR-Resources) +-- TAG-SCHEDULINGREQUESTRESOURCEID-STOP +-- ASN1STOP +``` + +### — *ScramblingId* + +The IE *ScramblingID* is used for scrambling channels and reference signals. + +#### *ScramblingId* information element + +``` +-- ASN1START +-- TAG-SCRAMBLINGID-START + +ScramblingId ::= INTEGER(0..1023) + +-- TAG-SCRAMBLINGID-STOP +-- ASN1STOP +``` + +### — *SCS-SpecificCarrier* + +The IE *SCS-SpecificCarrier* provides parameters determining the location and width of the actual carrier or the carrier bandwidth. It is defined specifically for a numerology (subcarrier spacing (SCS)) and in relation (frequency offset) to Point A. + +#### *SCS-SpecificCarrier* information element + +``` +-- ASN1START +-- TAG-SCS-SPECIFICCARRIER-START + +SCS-SpecificCarrier ::= SEQUENCE { + offsetToCarrier INTEGER (0..2199), + subcarrierSpacing SubcarrierSpacing, + carrierBandwidth INTEGER (1..maxNrofPhysicalResourceBlocks), + ... + [[ + txDirectCurrentLocation INTEGER (0..4095) OPTIONAL -- Need S + ]] +} + +-- TAG-SCS-SPECIFICCARRIER-STOP +-- ASN1STOP +``` + +| SCS-SpecificCarrier field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| carrierBandwidth
Width of this carrier in number of PRBs (using the subcarrierSpacing defined for this carrier) (see TS 38.211 [16], clause 4.4.2). | +| offsetToCarrier
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 subcarrierSpacing defined for this carrier). The maximum value corresponds to $275 \cdot 8 - 1$ . See TS 38.211 [16], clause 4.4.2. | +| txDirectCurrentLocation
Indicates the downlink Tx Direct Current location for the carrier. A value in the range 0..3299 indicates the subcarrier index within the carrier. The values in the value range 3301..4095 are reserved and ignored by the UE. If this field is absent for downlink within ServingCellConfigCommon and ServingCellConfigCommonSIB , the UE assumes the default value of 3300 (i.e. "Outside the carrier"). (see TS 38.211 [16], clause 4.4.2). Network does not configure this field via ServingCellConfig or for uplink carriers. | +| subcarrierSpacing
Subcarrier spacing of this carrier. It is used to convert the offsetToCarrier into an actual frequency.
Only the following values are applicable depending on the used frequency:
FR1: 15 or 30 kHz
FR2-1: 60 or 120 kHz
FR2-2: 120, 480, or 960 kHz | + +### SDAP-Config + +The IE *SDAP-Config* is used to set the configurable SDAP parameters for a data radio bearer. All configured instances of *SDAP-Config* with the same value of *pdu-Session* correspond to the same SDAP entity as specified in TS 37.324 [24]. + +#### SDAP-Config information element + +``` +-- ASN1START +-- TAG-SDAP-CONFIG-START + +SDAP-Config ::= SEQUENCE { + pdu-Session PDU-SessionID, + sdap-HeaderDL ENUMERATED {present, absent}, + sdap-HeaderUL ENUMERATED {present, absent}, + defaultDRB BOOLEAN, + mappedQoS-FlowsToAdd SEQUENCE (SIZE (1..maxNrofQFIs)) OF QFI OPTIONAL, -- Need N + mappedQoS-FlowsToRelease SEQUENCE (SIZE (1..maxNrofQFIs)) OF QFI OPTIONAL, -- Need N + ... +} + +QFI ::= INTEGER (0..maxQFI) + +-- TAG-SDAP-CONFIG-STOP +-- ASN1STOP +``` + +| SDAP-Config field descriptions | | +|---------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| defaultDRB | Indicates whether or not this is the default DRB for this PDU session. Among all configured instances of SDAP-Config with the same value of pdu-Session , this field shall be set to true in at most one instance of SDAP-Config and to false in all other instances. | +| mappedQoS-FlowsToAdd | Indicates the list of QFIs of UL QoS flows of the PDU session to be additionally mapped to this DRB. A QFI value can be included at most once in all configured instances of SDAP-Config with the same value of pdu-Session . For QoS flow remapping, the QFI value of the remapped QoS flow is only included in mappedQoS-FlowsToAdd in sdap-Config corresponding to the new DRB and not included in mappedQoS-FlowsToRelease in sdap-Config corresponding to the old DRB. | +| mappedQoS-FlowsToRelease | Indicates the list of QFIs of QoS flows of the PDU session to be released from existing QoS flow to DRB mapping of this DRB. | +| pdu-Session | Identity of the PDU session whose QoS flows are mapped to the DRB. | +| sdap-HeaderUL | Indicates whether or not a SDAP header is present for UL data on this DRB. The field cannot be changed after a DRB is established. The network sets this field to present if the field defaultDRB is set to true . | +| sdap-HeaderDL | Indicates whether or not a SDAP header is present for DL data on this DRB. The field cannot be changed after a DRB is established. | + +### — SearchSpace + +The IE *SearchSpace* defines how/where to search for PDCCH candidates. Each search space is associated with one *ControlResourceSet*. For a scheduled SCell in the case of cross carrier scheduling, except for *nrofCandidates*, all the optional fields are absent (regardless of their presence conditions). For a scheduled SpCell in the case of the cross carrier scheduling, if the search space is linked to another search space in the scheduling SCell, all the optional fields of this search space in the scheduled SpCell are absent (regardless of their presence conditions) except for *nrofCandidates*. + +#### SearchSpace information element + +``` +-- ASN1START +-- TAG-SEARCHSPACE-START + +SearchSpace ::= + searchSpaceId + controlResourceSetId + monitoringSlotPeriodicityAndOffset + SEQUENCE { + SearchSpaceId, + ControlResourceSetId + CHOICE { + NULL, + INTEGER (0..1), + INTEGER (0..3), + INTEGER (0..4), + INTEGER (0..7), + INTEGER (0..9), + INTEGER (0..15), + INTEGER (0..19), + INTEGER (0..39), + INTEGER (0..79), + INTEGER (0..159), + } + } + OPTIONAL, -- Cond SetupOnly +``` + +``` + + sl1320 INTEGER (0..319), + sl1640 INTEGER (0..639), + sl1280 INTEGER (0..1279), + sl2560 INTEGER (0..2559) + } + duration INTEGER (2..2559) OPTIONAL, -- Cond Setup4 + monitoringSymbolsWithinSlot BIT STRING (SIZE (14)) OPTIONAL, -- Need S + nrofCandidates SEQUENCE { OPTIONAL, -- Cond Setup + aggregationLevel1 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8}, + aggregationLevel2 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8}, + aggregationLevel4 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8}, + aggregationLevel8 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8}, + aggregationLevel16 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8} + } + searchSpaceType CHOICE { OPTIONAL, -- Cond Setup + common SEQUENCE { + dci-Format0-0-AndFormat1-0 + SEQUENCE { + ... + } + dci-Format2-0 + SEQUENCE { + nrofCandidates-SFI + SEQUENCE { + aggregationLevel1 ENUMERATED {n1, n2} OPTIONAL, -- Need R + aggregationLevel2 ENUMERATED {n1, n2} OPTIONAL, -- Need R + aggregationLevel4 ENUMERATED {n1, n2} OPTIONAL, -- Need R + aggregationLevel8 ENUMERATED {n1, n2} OPTIONAL, -- Need R + aggregationLevel16 ENUMERATED {n1, n2} OPTIONAL, -- Need R + }, + ... + } + dci-Format2-1 + SEQUENCE { + ... + } + dci-Format2-2 + SEQUENCE { + ... + } + dci-Format2-3 + SEQUENCE { + dummy1 ENUMERATED {sl1, sl2, sl4, sl5, sl8, sl10, sl16, sl20} OPTIONAL, -- Cond Setup + dummy2 ENUMERATED {n1, n2}, + ... + } + } + }, + ue-Specific SEQUENCE { + dci-Formats ENUMERATED {formats0-0-And-1-0, formats0-1-And-1-1}, + ... + [[ + dci-Formats-MT-r16 + ENUMERATED {formats2-5} OPTIONAL, -- Need R + dci-FormatsSL-r16 + ENUMERATED {formats0-0-And-1-0, formats0-1-And-1-1, formats3-0, formats3-1, + formats3-0-And-3-1} OPTIONAL, -- Need R + dci-FormatsExt-r16 + ENUMERATED {formats0-2-And-1-2, formats0-1-And-1-1And-0-2-And-1-2} + OPTIONAL -- Need R + ]], + +``` + +``` + + [[ + dci-FormatsMC ENUMERATED {formats0-3, formats1-3, formats0-3-And-1-3} OPTIONAL, -- Need R + dci-FormatsNCR-r18 ENUMERATED {formats2-8} OPTIONAL -- Need R + ]] + } +} + OPTIONAL -- Cond Setup2 +} + +SearchSpaceExt-r16 ::= SEQUENCE { + controlResourceSetId-r16 ControlResourceSetId-r16 OPTIONAL, -- Cond SetupOnly2 + searchSpaceType-r16 SEQUENCE { + common-r16 SEQUENCE { + dci-Format2-4-r16 SEQUENCE { + nrofCandidates-CI-r16 SEQUENCE { + aggregationLevel1-r16 ENUMERATED {n1, n2} OPTIONAL, -- Need R + aggregationLevel2-r16 ENUMERATED {n1, n2} OPTIONAL, -- Need R + aggregationLevel4-r16 ENUMERATED {n1, n2} OPTIONAL, -- Need R + aggregationLevel8-r16 ENUMERATED {n1, n2} OPTIONAL, -- Need R + aggregationLevel16-r16 ENUMERATED {n1, n2} OPTIONAL -- Need R + }, + ... + } OPTIONAL, -- Need R + }, + dci-Format2-5-r16 SEQUENCE { + nrofCandidates-IAB-r16 SEQUENCE { + aggregationLevel1-r16 ENUMERATED {n1, n2} OPTIONAL, -- Need R + aggregationLevel2-r16 ENUMERATED {n1, n2} OPTIONAL, -- Need R + aggregationLevel4-r16 ENUMERATED {n1, n2} OPTIONAL, -- Need R + aggregationLevel8-r16 ENUMERATED {n1, n2} OPTIONAL, -- Need R + aggregationLevel16-r16 ENUMERATED {n1, n2} OPTIONAL -- Need R + }, + ... + } OPTIONAL, -- Need R + dci-Format2-6-r16 SEQUENCE { + ... + } OPTIONAL, -- Need R + ... + } OPTIONAL, -- Cond Setup3 + searchSpaceGroupIdList-r16 SEQUENCE (SIZE (1.. 2)) OF INTEGER (0..1) OPTIONAL, -- Need R + freqMonitorLocations-r16 BIT STRING (SIZE (5)) OPTIONAL -- Need R +} + +SearchSpaceExt-v1700 ::= SEQUENCE { + monitoringSlotPeriodicityAndOffset-v1710 CHOICE { + s132 INTEGER (0..31), + s164 INTEGER (0..63), + s1128 INTEGER (0..127), + s15120 INTEGER (0..5119), + s110240 INTEGER (0..10239), + s120480 INTEGER (0..20479) + } OPTIONAL -- Cond Setup5 +} + +``` + +``` + +monitoringSlotsWithinSlotGroup-r17 CHOICE { + slotGroupLength4-r17 BIT STRING (SIZE (4)), + slotGroupLength8-r17 BIT STRING (SIZE (8)) +} +duration-r17 INTEGER (4..20476) +searchSpaceType-r17 SEQUENCE{ + common-r17 SEQUENCE { + dci-Format4-0-r17 SEQUENCE { + ... + } + dci-Format4-1-r17 SEQUENCE { + ... + } + dci-Format4-2-r17 SEQUENCE { + ... + } + dci-Format4-1-AndFormat4-2-r17 SEQUENCE { + ... + } + dci-Format2-7-r17 SEQUENCE { + nrofCandidates-PEI-r17 SEQUENCE { + aggregationLevel4-r17 ENUMERATED {n0, n1, n2, n3, n4} + aggregationLevel8-r17 ENUMERATED {n0, n1, n2} + aggregationLevel16-r17 ENUMERATED {n0, n1} + }, + ... + } + } +} +searchSpaceGroupIdList-r17 SEQUENCE (SIZE (1.. 3)) OF INTEGER (0.. maxNrofSearchSpaceGroups-1-r17) +searchSpaceLinkingId-r17 INTEGER (0..maxNrofSearchSpacesLinks-1-r17) +} + +SearchSpaceExt-v1800 ::= SEQUENCE { + searchSpaceType-r18 SEQUENCE { + common-r18 SEQUENCE { + dci-Format2-9-r18 SEQUENCE { + ... + } + ... + } + } +} +... +-- TAG-SEARCHSPACE-STOP +-- ASN1STOP + +``` + +| SearchSpace field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| common
Configures this search space as common search space (CSS) and DCI formats to monitor. | +| controlResourceSetId
The CORESET applicable for this SearchSpace. Value 0 identifies the common CORESET#0 configured in MIB and in ServingCellConfigCommon . Values 1..maxNrofControlResourceSets-1 identify CORESETs configured in System Information or by dedicated signalling. The CORESETs with non-zero controlResourceSetId are configured in the same BWP as this SearchSpace except commonControlResourceSetExt which is configured by SIB20. If the field controlResourceSetId-r16 is present, UE shall ignore the controlResourceSetId (without suffix). | +| dummy1, dummy2
This field is not used in the specification. If received it shall be ignored by the UE. | +| dci-Format0-0-AndFormat1-0
If configured, the UE monitors the DCI formats 0_0 and 1_0 according to TS 38.213 [13], clause 10.1. | +| dci-Format2-0
If configured, UE monitors the DCI format 2_0 according to TS 38.213 [13], clause 10.1, 11.1.1. | +| dci-Format2-1
If configured, UE monitors the DCI format 2_1 according to TS 38.213 [13], clause 10.1, 11.2. | +| dci-Format2-2
If configured, UE monitors the DCI format 2_2 according to TS 38.213 [13], clause 10.1, 11.3. | +| dci-Format2-3
If configured, UE monitors the DCI format 2_3 according to TS 38.213 [13], clause 10.1, 11.4. | +| dci-Format2-4
If configured, UE monitors the DCI format 2_4 according to TS 38.213 [13], clause 11.2A. | +| dci-Format2-5
If configured, IAB-MT monitors the DCI format 2_5 according to TS 38.213 [13], clause 14. | +| dci-Format2-6
If configured, UE monitors the DCI format 2_6 according to TS 38.213 [13], clause 10.1, 10.3. DCI format 2_6 can only be configured on the SpCell. | +| dci-Format2-7
If configured, UE monitors the DCI format 2_7 according to TS 38.213 [13], clause 10.1, 10.4A. | +| dci-Format2-9
If configured, UE monitors the DCI format 2_9 according to TS 38.213 [13], clause 10.1, 11.5. | +| dci-Format4-0
If configured, the UE monitors the DCI format 4_0 with CRC scrambled by MCCH-RNTI/G-RNTI according to TS 38.213 [13], clause [10.1]. | +| dci-Format4-1-AndFormat4-2
If configured, the UE monitors the DCI format 4_1 and 4_2 with CRC scrambled by G-RNTI/G-CS-RNTI according to TS 38.213 [13], clause [11.1]. | +| dci-Format4-1
If configured, the UE monitors the DCI format 4_1 with CRC scrambled by G-RNTI/G-CS-RNTI according to TS 38.213 [13], clause [10.1]. | +| dci-Format4-2
If configured, the UE monitors the DCI format 4_2 with CRC scrambled by G-RNTI/G-CS-RNTI according to TS 38.213 [13], clause [10.1]. | +| dci-Formats
Indicates whether the UE monitors in this USS for DCI formats 0-0 and 1-0 or for formats 0-1 and 1-1. | +| dci-FormatsExt
If this field is present, the field dci-Formats is ignored and dci-FormatsExt is used instead to indicate whether the UE monitors in this USS for DCI format 0_2 and 1_2 or formats 0_1 and 1_1 and 0_2 and 1_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 10.1). This field is not configured for operation with shared spectrum | + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| channel access in this release. | +| dci-FormatsMC
Indicate whether the UE monitors in this USS for DCI format 0_3 or for format 1_3 or for formats 0_3 and 1_3. Separate search space sets for DCI format 0_3/1_3 and legacy DCI formats are independently configured. If this field is present, the field dci-Formats is ignored.
NOTE: This parameter is used only for SearchSpace configured to the scheduling cell, while another SearchSpace configured to the reference scheduled cell (if any) configures only nrofCandidates (i.e., all other optional fields are absent) with same serachSpaceld with that for scheduling cell. | +| dci-Formats-MT
Indicates whether the IAB-MT monitors the DCI formats 2-5 according to TS 38.213 [13], clause 14. | +| dci-FormatsNCR
Indicates whether the NCR-MT monitors the DCI formats 2-8 according to TS 38.213 [13], clause 20. | +| dci-FormatsSL
Indicates whether the UE monitors in this USS for DCI formats 0-0 and 1-0 or for formats 0-1 and 1-1 or for format 3-0 or for format 3-1 or for formats 3-0 and 3-1. If this field is present, the field dci-Formats is ignored and dci-FormatsSL is used. | +| duration
Number of consecutive slots that a SearchSpace lasts in every occasion, i.e., upon every period as given in the periodicityAndOffset . If the field is absent, the UE applies the value 1 slot, except for DCI format 2_0. The UE ignores this field for DCI format 2_0. The maximum valid duration is periodicity-1 (periodicity as given in the monitoringSlotPeriodicityAndOffset ).
For SCS 480 kHz and SCS 960 kHz, duration-r17 is used, and the configured duration is restricted to be an integer multiple of L slots and smaller than periodicity, where L is the configured length of the bitmap monitoringSlotsWithinSlotGroup-r17 . If duration-r17 is absent, the UE assumes the duration in slots is equal to L. The maximum valid duration is periodicity-L.

For IAB-MT, duration indicates number of consecutive slots that a SearchSpace lasts in every occasion, i.e., upon every period as given in the periodicityAndOffset . If the field is absent, the IAB-MT applies the value 1 slot, except for DCI format 2_0 and DCI format 2_5. The IAB-MT ignores this field for DCI format 2_0 and DCI format 2_5. The maximum valid duration is periodicity-1 (periodicity as given in the monitoringSlotPeriodicityAndOffset ). | +| freqMonitorLocations
Defines an association of the search space to multiple monitoring locations in the frequency domain and indicates whether the pattern configured in the associated CORESET is replicated to a specific RB set, see TS 38.213, clause 10.1. Each bit in the bitmap corresponds to one RB set, and the leftmost (most significant) bit corresponds to RB set 0 in the BWP. A bit set to 1 indicates that a frequency domain resource allocation replicated from the pattern configured in the associated CORESET is mapped to the RB set. | +| monitoringSlotPeriodicityAndOffset
Slots for PDCCH Monitoring configured as periodicity and offset.
For SCS 15, 30, 60, and 120 kHz and if the UE is configured to monitor:
- DCI format 2_1, only the values 'sl1', 'sl2' or 'sl4' are applicable.
- DCI format 2_0, only the values 'sl1', 'sl2', 'sl4', 'sl5', 'sl8', 'sl10', 'sl16', and 'sl20' are applicable (see TS 38.213 [13], clause 10).
- DCI format 2_4, only the values 'sl1', 'sl2', 'sl4', 'sl5', 'sl8' and 'sl10' are applicable.
For SCS 480 kHz and if the UE is configured to monitor:
- DCI format 2_0, only the values 'sl4', 'sl8', 'sl16', 'sl20', 'sl32', 'sl40', 'sl64', and 'sl80' are applicable.
- DCI format 2_1, only the values 'sl4', 'sl8', and 'sl16' are applicable.
- DCI format 2_4, only the values 'sl4', 'sl8', 'sl16', 'sl20', 'sl32', 'sl40' are applicable.
For SCS 960 kHz and if the UE is configured to monitor:
- DCI format 2_0, only the values 'sl8', 'sl16', 'sl32', 'sl40', 'sl64', 'sl80', 'sl128', and 'sl160' are applicable.
- DCI format 2_1, only the values 'sl8', 'sl16', and 'sl32' are applicable.
- DCI format 2_4, only the values 'sl8', 'sl16', 'sl32', 'sl40', 'sl64', 'sl80' are applicable.

For SCS 480 kHz and SCS 960 kHz, and the configured periodicity and offset are restricted to be an integer multiple of L slots, where L is the configured length of the bitmap | + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

provided by monitoringSlotsWithinSlotGroup-r17, i.e. for a given periodicity, the offset has a range of {0, L, 2*L, ..., L*FLOOR(1/L*(periodicity-1))}.

For IAB-MT, If the IAB-MT is configured to monitor DCI format 2_1, only the values 'sl1', 'sl2' or 'sl4' are applicable. If the IAB-MT is configured to monitor DCI format 2_0 or DCI format 2_5, only the values 'sl1', 'sl2', 'sl4', 'sl5', 'sl8', 'sl10', 'sl16', and 'sl20' are applicable (see TS 38.213, clause 10). If monitoringSlotPeriodicityAndOffset-v1710 is present, any previously configured monitoringSlotPeriodicityAndOffset is released, and if monitoringSlotPeriodicityAndOffset is present, any previously configured monitoringSlotPeriodicityAndOffset-v1710 is released.

| +|

monitoringSlotsWithinSlotGroup
Indicates which slot(s) within a slot group are configured for multi-slot PDCCH monitoring. The first (leftmost, most significant) bit represents the first slot in the slot group, the second bit represents the second slot in the slot group, and so on. A bit set to '1' indicates that the corresponding slot is configured for multi-slot PDCCH monitoring (see TS 38.213 [13], clause 10). The number of slots for multi-slot PDCCH monitoring is configured according to clause 10 in TS 38.213 [13].

| +|

monitoringSymbolsWithinSlot
The first symbol(s) for PDCCH monitoring in the slots configured for (multi-slot) PDCCH monitoring (see monitoringSlotPeriodicityAndOffset and duration). The most significant (left) bit represents the first OFDM in a slot, and the second most significant (left) bit represents the second OFDM symbol in a slot and so on. The bit(s) set to one identify the first OFDM symbol(s) of the control resource set within a slot. If the cyclic prefix of the BWP is set to extended CP, the last two bits within the bit string shall be ignored by the UE or IAB-MT.
For DCI format 2_0, the first one symbol applies if the duration of CORESET (in the IE ControlResourceSet) identified by controlResourceSetId indicates 3 symbols, the first two symbols apply if the duration of CORESET identified by controlResourceSetId indicates 2 symbols, and the first three symbols apply if the duration of CORESET identified by controlResourceSetId indicates 1 symbol.
See TS 38.213 [13], clause 10.
For IAB-MT: For DCI format 2_0 or DCI format 2_5, the first one symbol applies if the duration of CORESET (in the IE ControlResourceSet) identified by controlResourceSetId indicates 3 symbols, the first two symbols apply if the duration of CORESET identified by controlResourceSetId indicates 2 symbols, and the first three symbols apply if the duration of CORESET identified by controlResourceSetId indicates 1 symbol.
See TS 38.213 [13], clause 10.

| +|

nrofCandidates-CI
The number of PDCCH candidates specifically for format 2-4 for the configured aggregation level. If an aggregation level is absent, the UE does not search for any candidates with that aggregation level. The network configures only one aggregationLevel and the corresponding number of candidates (see TS 38.213 [13], clause 10.1).

| +|

nrofCandidates-PEI
The number of PDCCH candidates specifically for format 2-7 for the configured aggregation level.

| +|

nrofCandidates-SFI
The number of PDCCH candidates specifically for format 2-0 for the configured aggregation level. If an aggregation level is absent, the UE does not search for any candidates with that aggregation level. The network configures only one aggregationLevel and the corresponding number of candidates (see TS 38.213 [13], clause 11.1.1). For a search space configured with freqMonitorLocations-r16, only value 'n1' is valid.

| +|

nrofCandidates
Number of PDCCH candidates per aggregation level. The number of candidates and aggregation levels configured here applies to all formats unless a particular value is specified or a format-specific value is provided (see inside searchSpaceType). If configured in the SearchSpace of a cross carrier scheduled cell, this field determines the number of candidates and aggregation levels to be used on the linked scheduling cell (see TS 38.213 [13], clause 10).

| +|

searchSpaceGroupIdList-r16, searchSpaceGroupIdList-r17
List of search space group IDs which the search space is associated with. The network configures at most 2 search space groups per BWP where the group ID is either 0 or 1 if searchSpaceGroupIdList-r16 is included. The network configures at most 3 search space groups per BWP where the group ID is either 0, 1 or 2 if searchSpaceGroupIdList-r17 is included. And if searchSpaceGroupIdList-r17 is included, searchSpaceGroupIdList-r16 is ignored.

| +|

searchSpaceId
Identity of the search space. SearchSpaceId = 0 identifies the searchSpaceZero configured via PBCH (MIB) or ServingCellConfigCommon and may hence not be used in the SearchSpace IE. The searchSpaceId is unique among the BWPs of a Serving Cell. In case of cross carrier scheduling, search spaces with the same searchSpaceId in scheduled cell and scheduling cell are linked to each other. The UE applies the search space for the scheduled cell only if the DL BWPs in which the linked search spaces are

| + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

configured in scheduling cell and scheduled cell are both active.
For an IAB-MT, the search space defines how/where to search for PDCCH candidates for an IAB-MT where each search space is associated with one ControlResourceSet and for a scheduled cell in the case of cross carrier scheduling, except for nrofCandidates, all the optional fields are absent.

SearchSpaceLinkingId
This parameter is used to link two search spaces of same type in the same BWP. If two search spaces have the same SearchSpaceLinkingId UE assumes these search spaces are linked to PDCCH repetition REF. When PDCCH repetition is monitored in two linked search space (SS) sets, the UE does not expect a third monitored SS set to be linked with any of the two linked SS sets. The two linked SS sets have the same SS set type (USS/CSS). The two linked SS sets have the same DCI formats to monitor. For intra-slot PDCCH repetition: The two SS sets should have the same periodicity and offset (monitoringSlotPeriodicityAndOffset), and the same duration. For linking monitoring occasions across the two SS sets that exist in the same slot: The two SS sets have the same number of monitoring occasions within a slot and n-th monitoring occasion of one SS set is linked to n-th monitoring occasion of the other SS set. The following SS sets cannot be linked with another SS set for PDCCH repetition: SS set 0, searchSpaceSIB1, searchSpaceOtherSystemInformation, pagingSearchSpace, ra-SearchSpace, searchSpaceMCCH, searchSpaceMTCH, peiSearchSpace, and sdt-SearchSpace. SS set configured by recoverySearchSpaceId cannot be linked to another SS set for PDCCH repetition. When a scheduled serving cell is configured to be cross-carrier scheduled by a scheduling serving cell, two PDCCH candidates (with the same AL and candidate index associated with the scheduled serving cell) are linked only if the corresponding two SS sets in the scheduling serving cell are linked and two SS sets in the scheduled serving cell with the same SS set IDs are also linked.
This parameter is not applicable to search space configured with dci-FormatsSL for monitoring format 3-0 or format 3-1 or for monitoring formats 3-0 and format 3-1.

searchSpaceType
Indicates whether this is a common search space (present) or a UE specific search space as well as DCI formats to monitor for.

ue-Specific
Configures this search space as UE specific search space (USS). The UE monitors the DCI format with CRC scrambled by C-RNTI, CS-RNTI (if configured), and SP-CSI-RNTI (if configured)

| +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| Conditional Presence | Explanation | +|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DedicatedOnly | In PDCCH-Config, the field is optionally present, Need R. Otherwise it is absent, Need R. | +| Setup | This field is mandatory present upon creation of a new SearchSpace . It is optionally present, Need M, otherwise. | +| Setup2 | This field is mandatory present when a new SearchSpace is set up, if the same SearchSpace ID is not included in searchSpacesToAddModListExt-r16 of the parent IE with the field searchSpaceType-r16 or searchSpaceType-r17 included. Otherwise it is optionally present, Need M. | +| Setup3 | This field is mandatory present when a new SearchSpace is set up, if the same SearchSpace ID is not included in searchSpacesToAddModListExt (without suffix) of the parent IE with the field searchSpaceType (without suffix) included. Otherwise it is optionally present, Need M. | +| Setup4 | This field is mandatory present upon creation of a new SearchSpace if monitoringSlotPeriodicityAndOffset-v1710 is not included. It is optionally present, Need M, otherwise. | +| Setup5 | This field is mandatory present upon creation of a new SearchSpace if monitoringSlotPeriodicityAndOffset (without suffix) is not included. It is optionally present, Need M, otherwise. | +| SetupOnly | This field is mandatory present upon creation of a new SearchSpace . It is absent, Need M, otherwise. | +| SetupOnly2 | In PDCCH-Config, the field is optionally present upon creation of a new SearchSpace and absent, Need M upon reconfiguration of an existing SearchSpace .
In PDCCH-ConfigCommon, the field is absent. | + +### — *SearchSpaceId* + +The IE *SearchSpaceId* is used to identify Search Spaces. The ID space is used across the BWPs of a Serving Cell. The search space with the *SearchSpaceId* = 0 identifies the search space configured via PBCH (MIB) and in *ServingCellConfigCommon* (*searchSpaceZero*). The number of Search Spaces per BWP is limited to 10 including the common and UE specific Search Spaces. + +#### *SearchSpaceId* information element + +``` +-- ASN1START +-- TAG-SEARCHSPACEID-START + +SearchSpaceId ::= INTEGER (0..maxNrofSearchSpaces-1) + +-- TAG-SEARCHSPACEID-STOP +-- ASN1STOP +``` + +### — *SearchSpaceZero* + +The IE *SearchSpaceZero* is used to configure SearchSpace#0 of the initial BWP (see TS 38.213 [13], clause 13). + +#### *SearchSpaceZero* information element + +``` +-- ASN1START +-- TAG-SEARCHSPACEZERO-START + +SearchSpaceZero ::= INTEGER (0..15) + +-- TAG-SEARCHSPACEZERO-STOP +-- ASN1STOP +``` + +### — *SecurityAlgorithmConfig* + +The IE *SecurityAlgorithmConfig* is used to configure AS integrity protection algorithm and AS ciphering algorithm for SRBs and DRBs. + +#### *SecurityAlgorithmConfig* information element + +``` +-- ASN1START +-- TAG-SECURITYALGORITHMCONFIG-START + +SecurityAlgorithmConfig ::= SEQUENCE { + cipheringAlgorithm CipheringAlgorithm, + integrityProtAlgorithm IntegrityProtAlgorithm OPTIONAL, -- Need R + ... +} +``` + +``` + +IntegrityProtAlgorithm ::= ENUMERATED { + nia0, nia1, nia2, nia3, spare4, spare3, + spare2, spare1, ...} + +CipheringAlgorithm ::= ENUMERATED { + nea0, nea1, nea2, nea3, spare4, spare3, + spare2, spare1, ...} + +-- TAG-SECURITYALGORITHMCONFIG-STOP +-- ASN1STOP + +``` + +#### SecurityAlgorithmConfig field descriptions + +##### ***cipheringAlgorithm*** + +Indicates the ciphering algorithm to be used for SRBs and DRBs, as specified in TS 33.501 [11]. The algorithms *nea0-nea3* are identical to the LTE algorithms *eea0-3*. The algorithms configured for all bearers using master key shall be the same, and the algorithms configured for all bearers using secondary key, if any, shall be the same. If UE is connected to E-UTRA/EPC, this field indicates the ciphering algorithm to be used for RBs configured with NR PDCP, as specified in TS 33.501 [11]. + +##### ***integrityProtAlgorithm*** + +Indicates the integrity protection algorithm to be used for SRBs and DRBs, as specified in TS 33.501 [11]. The algorithms *nia0-nia3* are identical to the E-UTRA algorithms *eia0-3*. The algorithms configured for all bearers using master key shall be the same and the algorithms configured for all bearers using secondary key, if any, shall be the same. The network does not configure *nia0* except for unauthenticated emergency sessions for unauthenticated UEs in LSM (limited service mode). If UE is connected to E-UTRA/EPC, this field indicates the integrity protection algorithm to be used for SRBs configured with NR PDCP as specified in TS 33.501 [11], and DRBs configured with integrity protection as specified in TS 33.401 [30]. The network does not configure *nia0* for SRB3. + +### — ***SelectedPSCellForCHO-WithSCG*** + +The IE *SelectedPSCellForCHO-WithSCG* is used to indicate the information of the selected target PSCell to target MN at execution of a conditional reconfiguration for CHO with candidate SCG(s). + +#### ***SelectedPSCellForCHO-WithSCG* information element** + +``` + +-- ASN1START +-- TAG-SELECTEDPSCELLFORCHO-WITHSCG-START + +SelectedPSCellForCHO-WithSCG-r18 ::= SEQUENCE { + ssbFrequency-r18 ARFCN-ValueNR, + physCellId-r18 PhysCellId +} + +-- TAG-SELECTEDPSCELLFORCHO-WITHSCG-STOP +-- ASN1STOP + +``` + +### — *SemiStaticChannelAccessConfig* + +The IE *SemiStaticChannelAccessConfig* is used to configure channel access parameters when the network is operating in semi-static channel access mode (see clause 4.3 in TS 37.213 [48]). + +#### *SemiStaticChannelAccessConfig* information element + +``` +-- ASN1START +-- TAG-SEMISTATICCHANNELACCESSCONFIG-START + +SemiStaticChannelAccessConfig-r16 ::= SEQUENCE { + period-r16 ENUMERATED {ms1, ms2, ms2dot5, ms4, ms5, ms10} +} + +-- TAG-SEMISTATICCHANNELACCESSCONFIG-STOP +-- ASN1STOP +``` + +#### *SemiStaticChannelAccessConfig* field descriptions + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

period
Indicates the periodicity of the semi-static channel access mode (see TS 37.213 [48], clause 4.3). Value ms1 corresponds to 1 ms, value ms2 corresponds to 2 ms, value ms2dot5 corresponds to 2.5 ms, and so on.

| +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### — *SemiStaticChannelAccessConfigUE* + +The IE *SemiStaticChannelAccessConfigUE* is used to configure channel access parameters for UE initiated semi-static channel access. + +#### *SemiStaticChannelAccessConfigUE* information element + +``` +-- ASN1START +-- TAG-SEMISTATICCHANNELACCESSCONFIGUE-START + +SemiStaticChannelAccessConfigUE-r17 ::= SEQUENCE { + periodUE-r17 ENUMERATED {ms1, ms2, ms2dot5, ms4, ms5, ms10, spare2, spare1}, + offsetUE-r17 INTEGER (0..559) +} + +-- TAG-SEMISTATICCHANNELACCESSCONFIGUE-STOP +-- ASN1STOP +``` + +| SemiStaticChannelAccessConfigUE field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| periodUE
Indicates the period of a channel occupancy that the UE can initiate as described in TS 37.213 [48], clause 4.3. Value ms1 corresponds to 1 ms, value ms2 corresponds to 2 ms, value ms2dot5 corresponds to 2.5 ms, and so on. | +| offsetUE
Indicates the number of symbols from the beginning of the even indexed radio frame to the start of the first period within that radio frame that the UE can initiate a channel occupancy (see TS 37.213 [48], clause 4.3), based on the smallest SCS among the configured SCSs in the serving cell. The offset duration indicated by this field is less than the period duration indicated by periodUE . The maximum value is 139, 279 and 559 for 15, 30 and 60 kHz subcarrier spacing, respectively. | + +### — *Sensor-LocationInfo* + +The IE *Sensor-LocationInfo* is used by the UE to provide sensor information. + +#### ***Sensor-LocationInfo* information element** + +``` +-- ASN1START +-- TAG-SENSORLOCATIONINFO-START + +Sensor-LocationInfo-r16 ::= SEQUENCE { + sensor-MeasurementInformation-r16 OCTET STRING OPTIONAL, + sensor-MotionInformation-r16 OCTET STRING OPTIONAL, + ... +} + +-- TAG-SENSORLOCATIONINFO-STOP +-- ASN1STOP +``` + +| Sensor-LocationInfo field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sensor-MeasurementInformation
This field provides barometric pressure measurements as Sensor-MeasurementInformation defined in TS 37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit. | +| sensor-MotionInformation
This field provides motion sensor measurements as Sensor-MotionInformation defined in TS 37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit. | + +### — *ServingCellAndBWP-Id* + +The IE *ServingCellAndBWP-Id* is used to indicate a serving cell and an uplink or a downlink BWP. + +#### ***ServingCellAndBWP-Id* information element** + +``` +-- ASN1START +-- TAG-SERVINGCELLANDBWP-ID-START +``` + +``` + +ServingCellAndBWP-Id-r17 ::= SEQUENCE { + servingCell-r17 ServCellIndex, + bwp-r17 BWP-Id +} + +-- TAG-SERVINGCELLANDBWP-ID-STOP +-- ASN1STOP + +``` + +### — *ServCellIndex* + +The IE *ServCellIndex* concerns a short identity, used to uniquely identify a serving cell (i.e. the PCell, the PSCell or an SCell) across the cell groups. Value 0 applies for the PCell, while the *SCellIndex* that has previously been assigned applies for SCells. + +#### *ServCellIndex* information element + +``` + +-- ASN1START +-- TAG-SERVCELLINDEX-START + +ServCellIndex ::= INTEGER (0..maxNrofServingCells-1) + +-- TAG-SERVCELLINDEX-STOP +-- ASN1STOP + +``` + +## — *ServingCellConfig* + +The IE *ServingCellConfig* is used to configure (add or modify) the UE with a serving cell, which may be the SpCell or an SCell of an MCG or SCG. The parameters herein are mostly UE specific but partly also cell specific (e.g. in additionally configured bandwidth parts). Reconfiguration between a PUCCH and PUCCHless SCell is only supported using an SCell release and add. + +#### *ServingCellConfig* information element + +``` + +-- ASN1START +-- TAG-SERVINGCELLCONFIG-START + +ServingCellConfig ::= SEQUENCE { + tdd-UL-DL-ConfigurationDedicated TDD-UL-DL-ConfigDedicated OPTIONAL, -- Cond TDD + initialDownlinkBWP BWP-DownlinkDedicated OPTIONAL, -- Need M + downlinkBWP-ToReleaseList SEQUENCE (SIZE (1..maxNrofBWPs)) OF BWP-Id + OPTIONAL, -- Need N + downlinkBWP-ToAddModList SEQUENCE (SIZE (1..maxNrofBWPs)) OF BWP-Downlink + OPTIONAL, -- Need N + firstActiveDownlinkBWP-Id BWP-Id OPTIONAL, -- Cond SyncAndCellAdd + bwp-InactivityTimer ENUMERATED {ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, + ms40, ms50, ms60, ms80, ms100, ms200, ms300, ms500, + ms750, ms1280, ms1920, ms2560, spare10, spare9, spare8, + spare7, spare6, spare5, spare4, spare3, spare2, spare1 } + OPTIONAL, -- Need R + defaultDownlinkBWP-Id BWP-Id OPTIONAL, -- Need S + ... +} + +``` + +``` + +uplinkConfig UplinkConfig OPTIONAL, -- Need M +supplementaryUplink UplinkConfig OPTIONAL, -- Need M +pdcch-ServingCellConfig SetupRelease { PDCCH-ServingCellConfig } OPTIONAL, -- Need M +pdsch-ServingCellConfig SetupRelease { PDSCH-ServingCellConfig } OPTIONAL, -- Need M +csi-MeasConfig SetupRelease { CSI-MeasConfig } OPTIONAL, -- Need M +sCellDeactivationTimer ENUMERATED {ms20, ms40, ms80, ms160, ms200, ms240, + ms320, ms400, ms480, ms520, ms640, ms720, + ms840, ms1280, spare2,spare1} OPTIONAL, -- Cond ServingCellWithoutPUCCH +crossCarrierSchedulingConfig CrossCarrierSchedulingConfig OPTIONAL, -- Need M +tag-Id TAG-Id, +dummy1 ENUMERATED {enabled} OPTIONAL, -- Need R +pathlossReferenceLinking ENUMERATED {spCell, sCell} OPTIONAL, -- Cond SCellOnly +servingCellMO MeasObjectId OPTIONAL, -- Cond MeasObject +..., +[[ +lte-CRS-ToMatchAround SetupRelease { RateMatchPatternLTE-CRS } OPTIONAL, -- Need M +rateMatchPatternToAddModList SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF RateMatchPattern OPTIONAL, -- Need N +rateMatchPatternToReleaseList SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF RateMatchPatternId OPTIONAL, -- Need N +downlinkChannelBW-PerSCS-List SEQUENCE (SIZE (1..maxSCSs)) OF SCS-SpecificCarrier OPTIONAL -- Need S +]], +[[ +supplementaryUplinkRelease-r16 ENUMERATED {true} OPTIONAL, -- Need N +tdd-UL-DL-ConfigurationDedicated-IAB-MT-r16 TDD-UL-DL-ConfigDedicated-IAB-MT-r16 OPTIONAL, -- Cond TDD_IAB +dormantBWP-Config-r16 SetupRelease { DormantBWP-Config-r16 } OPTIONAL, -- Need M +ca-SlotOffset-r16 CHOICE { + refSCS15kHz INTEGER (-2..2), + refSCS30KHz INTEGER (-5..5), + refSCS60KHz INTEGER (-10..10), + refSCS120KHz INTEGER (-20..20) +} OPTIONAL, -- Cond AsyncCA +dummy2 SetupRelease { DummyJ } OPTIONAL, -- Need M +intraCellGuardBandsDL-List-r16 SEQUENCE (SIZE (1..maxSCSs)) OF IntraCellGuardBandsPerSCS-r16 OPTIONAL, -- Need S +intraCellGuardBandsUL-List-r16 SEQUENCE (SIZE (1..maxSCSs)) OF IntraCellGuardBandsPerSCS-r16 OPTIONAL, -- Need S +csi-RS-ValidationWithDCI-r16 ENUMERATED {enabled} OPTIONAL, -- Need R +lte-CRS-PatternList1-r16 SetupRelease { LTE-CRS-PatternList-r16 } OPTIONAL, -- Need M +lte-CRS-PatternList2-r16 SetupRelease { LTE-CRS-PatternList-r16 } OPTIONAL, -- Need M +crs-RateMatch-PerCORESETPoolIndex-r16 ENUMERATED {enabled} OPTIONAL, -- Need R +enableTwoDefaultTCI-States-r16 ENUMERATED {enabled} OPTIONAL, -- Need R +enableDefaultTCI-StatePerCoresetPoolIndex-r16 ENUMERATED {enabled} OPTIONAL, -- Need R +enableBeamSwitchTiming-r16 ENUMERATED {true} OPTIONAL, -- Need R +cbg-TxDiffTBsProcessingType1-r16 ENUMERATED {enabled} OPTIONAL, -- Need R +cbg-TxDiffTBsProcessingType2-r16 ENUMERATED {enabled} OPTIONAL, -- Need R +]], +[[ +directionalCollisionHandling-r16 ENUMERATED {enabled} OPTIONAL, -- Need R +channelAccessConfig-r16 SetupRelease { ChannelAccessConfig-r16 } OPTIONAL, -- Need M +]], +[[ +nr-dl-PRS-PDC-Info-r17 SetupRelease {NR-DL-PRS-PDC-Info-r17} OPTIONAL, -- Need M +semiStaticChannelAccessConfigUE-r17 SetupRelease {SemiStaticChannelAccessConfigUE-r17} OPTIONAL, -- Need M +mimoParam-r17 SetupRelease {MIMOParam-r17} OPTIONAL, -- Need M + +``` + +``` + + channelAccessMode2-r17 ENUMERATED {enabled} OPTIONAL, -- Need R + timeDomainHARQ-BundlingType1-r17 ENUMERATED {enabled} OPTIONAL, -- Need R + nrofHARQ-BundlingGroups-r17 ENUMERATED {n1, n2, n4} OPTIONAL, -- Need R + fdmed-ReceptionMulticast-r17 ENUMERATED {true} OPTIONAL, -- Need R + moreThanOneNackOnlyMode-r17 ENUMERATED {mode2} OPTIONAL, -- Need S + tci-ActivatedConfig-r17 TCI-ActivatedConfig-r17 OPTIONAL, -- Cond +TCI_ActivatedConfig + directionalCollisionHandling-DC-r17 ENUMERATED {enabled} OPTIONAL, -- Need R + lte-NeighCellsCRS-AssistInfoList-r17 SetupRelease { LTE-NeighCellsCRS-AssistInfoList-r17 } OPTIONAL, -- Need M + ]], + [[ + lte-NeighCellsCRS-Assumptions-r17 ENUMERATED {false} OPTIONAL -- Need R + ]], + [[ + crossCarrierSchedulingConfigRelease-r17 ENUMERATED {true} OPTIONAL -- Need N + ]], + [[ + multiPDSCH-PerSlotType1-CB-r17 ENUMERATED {enabled, disabled} OPTIONAL -- Need R + ]], + [[ + lte-CRS-PatternList3-r18 SetupRelease { LTE-CRS-PatternList-r16 } OPTIONAL, -- Need M + lte-CRS-PatternList4-r18 SetupRelease { LTE-CRS-PatternList-r16 } OPTIONAL, -- Need M + pdcch-CandidateReceptionWith-CRS-Overlap-r18 ENUMERATED {enabled} OPTIONAL, -- Need R + cjt-Scheme-PDSCH-r18 ENUMERATED {cjtSchemeA, cjtSchemeB} OPTIONAL, -- Need R + tag2-r18 SEQUENCE { + tag2-Id TAG-Id, + tag2-flag BOOLEAN + } OPTIONAL, -- Need R + n-TimingAdvanceOffset2-r18 ENUMERATED { n0, n25600, n39936 } OPTIONAL, -- Cond Tag2 + cellDTXDRX-Config-r18 SetupRelease { CellDTXDRX-Config-r18 } OPTIONAL, -- Need M + positionInDCI-cellDTXDRX-r18 INTEGER (0..maxDCI-2-9-Size-1-r18) OPTIONAL, -- Need R + mc-DCI-SetOfCellsToAddModList-r18 SEQUENCE (SIZE (1..maxNrofSetsOfCells-r18)) OF MC-DCI-SetOfCells-r18 OPTIONAL, -- Need N + mc-DCI-SetOfCellsToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofSetsOfCells-r18)) OF SetOfCellsId-r18 OPTIONAL -- Need N + ]] +} + +UplinkConfig ::= SEQUENCE { + initialUplinkBWP BWP-UplinkDedicated OPTIONAL, -- Need M + uplinkBWP-ToReleaseList SEQUENCE (SIZE (1..maxNrofBWPs)) OF BWP-Id OPTIONAL, -- Need N + uplinkBWP-ToAddModList SEQUENCE (SIZE (1..maxNrofBWPs)) OF BWP-Uplink OPTIONAL, -- Need N + firstActiveUplinkBWP-Id BWP-Id OPTIONAL, -- Cond SyncAndCellAdd + pusch-ServingCellConfig SetupRelease { PUSCH-ServingCellConfig } OPTIONAL, -- Need M + carrierSwitching SetupRelease { SRS-CarrierSwitching } OPTIONAL, -- Need M + ..., + [[ + powerBoostPi2BPSK BOOLEAN OPTIONAL, -- Need M + uplinkChannelBW-PerSCS-List SEQUENCE (SIZE (1..maxSCSs)) OF SCS-SpecificCarrier OPTIONAL -- Need S + ]], + [[ + enablePL-RS-UpdateForPUSCH-SRS-r16 ENUMERATED {enabled} OPTIONAL, -- Need R + enableDefaultBeamPL-ForPUSCH0-0-r16 ENUMERATED {enabled} OPTIONAL -- Need R + ]] +} + +``` + +``` + +enableDefaultBeamPL-ForPUCCH-r16 ENUMERATED {enabled} OPTIONAL, -- Need R +enableDefaultBeamPL-ForSRS-r16 ENUMERATED {enabled} OPTIONAL, -- Need R +uplinkTxSwitching-r16 SetupRelease { UplinkTxSwitching-r16 } OPTIONAL, -- Need M +mpr-PowerBoost-FR2-r16 ENUMERATED {true} OPTIONAL -- Need R +], +[[ +srs-PosTx-Hopping-r18 SetupRelease { SRS-PosTx-Hopping-r18 } OPTIONAL -- Need M +]] +} + +DummyJ ::= SEQUENCE { + maxEnergyDetectionThreshold-r16 INTEGER (-85..-52), + energyDetectionThresholdOffset-r16 INTEGER (-20..-13), + ul-toDL-COT-SharingED-Threshold-r16 INTEGER (-85..-52) OPTIONAL, -- Need R + absenceOfAnyOtherTechnology-r16 ENUMERATED {true} OPTIONAL -- Need R +} + +ChannelAccessConfig-r16 ::= SEQUENCE { + energyDetectionConfig-r16 CHOICE { + maxEnergyDetectionThreshold-r16 INTEGER (-85..-52), + energyDetectionThresholdOffset-r16 INTEGER (-13..20) + } OPTIONAL, -- Need R + ul-toDL-COT-SharingED-Threshold-r16 INTEGER (-85..-52) OPTIONAL, -- Need R + absenceOfAnyOtherTechnology-r16 ENUMERATED {true} OPTIONAL -- Need R +} + +IntraCellGuardBandsPerSCS-r16 ::= SEQUENCE { + guardBandSCS-r16 SubcarrierSpacing, + intraCellGuardBands-r16 SEQUENCE (SIZE (1..4)) OF GuardBand-r16 +} + +GuardBand-r16 ::= SEQUENCE { + startCRB-r16 INTEGER (0..274), + nrofCRBs-r16 INTEGER (0..15) +} + +DormancyGroupID-r16 ::= INTEGER (0..4) + +DormantBWP-Config-r16 ::= SEQUENCE { + dormantBWP-Id-r16 BWP-Id OPTIONAL, -- Need M + withinActiveTimeConfig-r16 SetupRelease { WithinActiveTimeConfig-r16 } OPTIONAL, -- Need M + outsideActiveTimeConfig-r16 SetupRelease { OutsideActiveTimeConfig-r16 } OPTIONAL, -- Need M +} + +WithinActiveTimeConfig-r16 ::= SEQUENCE { + firstWithinActiveTimeBWP-Id-r16 BWP-Id OPTIONAL, -- Need M + dormancyGroupWithinActiveTime-r16 DormancyGroupID-r16 OPTIONAL -- Need R +} + +OutsideActiveTimeConfig-r16 ::= SEQUENCE { + firstOutsideActiveTimeBWP-Id-r16 BWP-Id OPTIONAL, -- Need M +} + +``` + +``` + + dormancyGroupOutsideActiveTime-r16 DormancyGroupID-r16 OPTIONAL -- Need R +} + +UplinkTxSwitching-r16 ::= SEQUENCE { + uplinkTxSwitchingPeriodLocation-r16 BOOLEAN, + uplinkTxSwitchingCarrier-r16 ENUMERATED {carrier1, carrier2} +} + +MIMOParam-r17 ::= SEQUENCE { + additionalPCI-ToAddModList-r17 SEQUENCE (SIZE (1..maxNrofAdditionalPCI-r17)) OF SSB-MTC-AdditionalPCI-r17 OPTIONAL, -- Need N + additionalPCI-ToReleaseList-r17 SEQUENCE (SIZE (1..maxNrofAdditionalPCI-r17)) OF AdditionalPCIIndex-r17 OPTIONAL, -- Need N + unifiedTCI-StateType-r17 ENUMERATED {separate, joint} OPTIONAL, -- Need R + uplink-PowerControlToAddModList-r17 SEQUENCE (SIZE (1..maxUL-TCI-r17)) OF Uplink-powerControl-r17 OPTIONAL, -- Need N + uplink-PowerControlToReleaseList-r17 SEQUENCE (SIZE (1..maxUL-TCI-r17)) OF Uplink-powerControlId-r17 OPTIONAL, -- Need N + sfnSchemePDCH-r17 ENUMERATED {sfnSchemeA, sfnSchemeB} OPTIONAL, -- Need R + sfnSchemePD SCH-r17 ENUMERATED {sfnSchemeA, sfnSchemeB} OPTIONAL -- Need R +} + +MC-DCI-SetOfCells-r18 ::= SEQUENCE { + setOfCellsId-r18 SetOfCellsId-r18, + nCI-Value-r18 INTEGER (0..7), + scheduledCellListDCI-1-3-r18 SEQUENCE (SIZE (2..maxNrofCellsInSet-r18)) OF ServCellIndex OPTIONAL, -- Need R + scheduledCellListDCI-0-3-r18 SEQUENCE (SIZE (2..maxNrofCellsInSet-r18)) OF ServCellIndex OPTIONAL, -- Need R + scheduledCellComboListDCI-1-3-r18 SEQUENCE (SIZE (1..maxNrofCellCombos-r18)) OF ScheduledCellCombo-r18 OPTIONAL, -- Need R + scheduledCellComboListDCI-0-3-r18 SEQUENCE (SIZE (1..maxNrofCellCombos-r18)) OF ScheduledCellCombo-r18 OPTIONAL, -- Need R + antennaPortsDCI1-3-r18 ENUMERATED {typela, type2} OPTIONAL, -- Cond TypeDCI1-3 + antennaPortsDCI0-3-r18 ENUMERATED {typela, type2} OPTIONAL, -- Cond TypeDCI0-3 + tpmi-DCI0-3-r18 ENUMERATED {typela, type2} OPTIONAL, -- Cond TypeDCI0-3 + sri-DCI0-3-r18 ENUMERATED {typela, type2} OPTIONAL, -- Cond TypeDCI0-3 + priorityIndicatorDCI-1-3-r18 ENUMERATED {enabled} OPTIONAL, -- Need R + priorityIndicatorDCI-0-3-r18 ENUMERATED {enabled} OPTIONAL, -- Need R + dormancyDCI-1-3-r18 ENUMERATED {enabled} OPTIONAL, -- Need R + dormancyDCI-0-3-r18 ENUMERATED {enabled} OPTIONAL, -- Need R + pdcchMonAdaptDCI-1-3-r18 ENUMERATED {enabled} OPTIONAL, -- Need R + pdcchMonAdaptDCI-0-3-r18 ENUMERATED {enabled} OPTIONAL, -- Need R + minimumSchedulingOffsetK0DCI-1-3-r18 ENUMERATED {enabled} OPTIONAL, -- Need R + minimumSchedulingOffsetK0DCI-0-3-r18 ENUMERATED {enabled} OPTIONAL, -- Need R + pdsch-HARQ-ACK-OneShotFeedbackDCI-1-3-r18 ENUMERATED {enabled} OPTIONAL, -- Need R + pdsch-HARQ-ACK-enhType3DCI-1-3-r18 ENUMERATED {enabled} OPTIONAL, -- Need R + pdsch-HARQ-ACK-enhType3DCIfieldDCI-1-3-r18 ENUMERATED {enabled} OPTIONAL, -- Need R + pdsch-HARQ-ACK-retxD CI-1-3-r18 ENUMERATED {enabled} OPTIONAL, -- Need R + pucch-sSCellDynDCI-1-3-r18 ENUMERATED {enabled} OPTIONAL, -- Need R + tdra-FieldIndexListDCI-1-3-r18 SEQUENCE (SIZE (1..32)) OF TDRA-FieldIndexDCI-1-3-r18 OPTIONAL, -- Need R + tdra-FieldIndexListDCI-0-3-r18 SEQUENCE (SIZE (1..64)) OF TDRA-FieldIndexDCI-0-3-r18 OPTIONAL, -- Need R + rateMatchListDCI-1-3-r18 SEQUENCE (SIZE (1..16)) OF RateMatchDCI-1-3-r18 OPTIONAL, -- Need R + zp-CSI-RSListDCI-1-3-r18 SEQUENCE (SIZE (1..8)) OF ZP-CSI-DCI-1-3-r18 OPTIONAL, -- Need R + tci-ListDCI-1-3-r18 SEQUENCE (SIZE (1..16)) OF TCI-DCI-1-3-r18 OPTIONAL, -- Need R + srs-RequestListDCI-1-3-r18 SEQUENCE (SIZE (1..16)) OF SRS-RequestCombo-r18 OPTIONAL, -- Need R + srs-OffsetListDCI-1-3-r18 SEQUENCE (SIZE (1..8)) OF SRS-OffsetCombo-r18 OPTIONAL, -- Need R + srs-RequestListDCI-0-3-r18 SEQUENCE (SIZE (1..16)) OF SRS-RequestCombo-r18 OPTIONAL, -- Need R + srs-OffsetListDCI-0-3-r18 SEQUENCE (SIZE (1..8)) OF SRS-OffsetCombo-r18 OPTIONAL -- Need R +} + +``` + +``` + +} + +SetOfCellsId-r18 := INTEGER (0..maxNrofSetsOfCells-1-r18) +ScheduledCellCombo-r18 := SEQUENCE (SIZE (1..maxNrofCellsInSet-r18)) OF INTEGER (0..maxNrofCellsInSet-1-r18) +RateMatchDCI-1-3-r18 := SEQUENCE (SIZE (1..maxNrofCellsInSet-r18)) OF BIT STRING (SIZE (1..2)) +ZP-CSI-DCI-1-3-r18 := SEQUENCE (SIZE (1.. maxNrofCellsInSet-r18)) OF BIT STRING (SIZE (1..2)) +TCI-DCI-1-3-r18 := SEQUENCE (SIZE (2.. maxNrofCellsInSet-r18)) OF BIT STRING (SIZE (3)) +SRS-RequestCombo-r18 := SEQUENCE (SIZE (1.. maxNrofCellsInSet-r18)) OF BIT STRING (SIZE (2..3)) +SRS-OffsetCombo-r18 := SEQUENCE (SIZE (1.. maxNrofCellsInSet-r18)) OF INTEGER (0..3) +TDRA-FieldIndexDCI-1-3-r18 := SEQUENCE (SIZE (2.. maxNrofBWPsInSetOfCells-r18)) OF INTEGER (0..maxNrofDL-Allocations-1-r18) +TDRA-FieldIndexDCI-0-3-r18 := SEQUENCE (SIZE (2.. maxNrofBWPsInSetOfCells-r18)) OF INTEGER (0..maxNrofUL-Allocations-1-r18) + +-- TAG-SERVINGCELLCONFIG-STOP +-- ASN1STOP + +``` + +#### ChannelAccessConfig field descriptions + +| | | +|----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| absenceOfAnyOtherTechnology | Presence of this field indicates absence on a long term basis (e.g. by level of regulation) of any other technology sharing the carrier; absence of this field indicates the potential presence of any other technology sharing the carrier, as specified in TS 37.213 [48] clauses 4.2.1 and 4.2.3. | +| energyDetectionConfig | Indicates whether to use the maxEnergyDetectionThreshold or the energyDetectionThresholdOffset (see TS 37.213 [48], clause 4.2.3). | +| energyDetectionThresholdOffset | Indicates the offset to the default maximum energy detection threshold value. Unit in dB. Value -13 corresponds to -13dB, value -12 corresponds to -12dB, and so on (i.e. in steps of 1dB) as specified in TS 37.213 [48], clause 4.2.3. | +| maxEnergyDetectionThreshold | Indicates the absolute maximum energy detection threshold value. Unit in dBm. Value -85 corresponds to -85 dBm, value -84 corresponds to -84 dBm, and so on (i.e. in steps of 1dBm) as specified in TS 37.213 [48], clause 4.2.3. | +| n-TimingAdvanceOffset2 | The N_TA-Offset2 to be applied for all uplink transmissions on this serving cell associated to tag2 . If absent, n-TimingAdvanceOffset is applied for all uplink transmissions on this serving cell associated to tag2 . | +| ul-toDL-COT-SharingED-Threshold | Maximum energy detection threshold that the UE should use to share channel occupancy with gNB for DL transmission as specified in TS 37.213 [48], clause 4.1.3 for downlink channel access and clause 4.2.3 for uplink channel access. This field is not applicable in semi-static channel access mode. | + +| ServingCellConfig field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| additionalPCI-ToAddModList
List of information for the additional SSB with different PCI than the serving cell PCI. The additional SSBs with different PCIs are not used for serving cell quality derivation. | +| bwp-InactivityTimer
The duration in ms after which the UE falls back to the default Bandwidth Part (see TS 38.321 [3], clause 5.15). When the network releases the timer configuration, the UE stops the timer without switching to the default BWP. | +| ca-SlotOffset
Slot offset between the primary cell (PCell/PSCell) and the SCell in unaligned frame boundary with slot alignment and partial SFN alignment inter-band CA. Based on this field, the UE determines the time offset of the SCell as specified in clause 4.5 of TS 38.211 [16]. The granularity of this field is determined by the reference SCS for the slot offset (i.e. the maximum of PCell/PSCell lowest SCS among all the configured SCSs in DL/UL SCS-SpecificCarrierList in ServingCellConfigCommon or ServingCellConfigCommonSIB and this serving cell's lowest SCS among all the configured SCSs in DL/UL SCS-SpecificCarrierList in ServingCellConfigCommon or ServingCellConfigCommonSIB ).
The Network configures at most single non-zero offset duration in ms (independent on SCS) among CCs in the unaligned CA configuration. If the field is absent, the UE applies the value of 0. The slot offset value can only be changed with SCell release and add. | +| cbg-TxDiffTBsProcessingType1, cbg-TxDiffTBsProcessingType2
Indicates whether processing types 1 and 2 based CBG based operation is enabled according to Rel-16 UE capabilities. | +| cellDTXDRX-Config
Used to configure cell DTX/DRX for the serving cell, as specified in TS 38.321 [3]. A maximum of two cell DTX/DRX patterns can be configured per MAC entity for different serving cells. The two configured patterns are aligned, that the start and slot offset are common and the periodicity of one pattern is an integer multiple of the other. | +| cjt-Scheme-PDSCH
This field is used to configure CJT Tx scheme cjtSchemeA or cjtSchemeB for PDSCH reception, see Reference XXX. | +| channelAccessConfig
List of parameters used for access procedures of operation with shared spectrum channel access (see TS 37.213 [48]). | +| channelAccessMode2
If present, this field indicates that the UE shall apply channel access procedures for operation with shared spectrum channel access in accordance with TS 37.213 [48], clause 4.4 for FR2-2. If absent, the UE does not apply these channel access procedures. The network always configures this field if channel access procedures are required for the serving cell within this region by regulations.
Overwrites the corresponding field in ServingCellConfigCommon or ServingCellConfigCommonSIB for this serving cell. | +| crossCarrierSchedulingConfig
Indicates whether this serving cell is cross-carrier scheduled by another serving cell or whether it cross-carrier schedules another serving cell. If the field other is configured for an SpCell (i.e., the SpCell is cross-carrier scheduled by another serving cell), the SpCell can be additionally scheduled by the PDCCH on the SpCell. | +| crossCarrierSchedulingConfigRelease
If this field is included, the UE shall release the cross carrier scheduling configuration configured by crossCarrierSchedulingConfig . The network may only include either crossCarrierSchedulingConfigRelease or crossCarrierSchedulingConfig at a time. | +| crs-RateMatch-PerCORESETPoolIndex
Indicates how UE performs rate matching when both lte-CRS-PatternList1-r16 and lte-CRS-PatternList2-r16 are configured or when both lte-CRS-PatternList3-r18 and lte-CRS-PatternList4-r18 are configured as specified in TS 38.214 [19], clause 5.1.4.2. | +| csi-RS-ValidationWithDCI
Indicates how the UE performs periodic and semi-persistent CSI-RS reception in a slot. The presence of this field indicates that the UE uses DCI detection to validate whether to receive CSI-RS (see TS 38.213 [13], clause 11.1). | +| defaultDownlinkBWP-Id
The initial bandwidth part is referred to by BWP-Id = 0. ID of the downlink bandwidth part to be used upon expiry of the BWP inactivity timer. This field is UE specific. When the field is absent the UE uses the initial BWP as default BWP. (see TS 38.213 [13], clause 12 and TS 38.321 [3], clause 5.15). | +| directionalCollisionHandling | + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Indicates that this serving cell is using directional collision handling between a reference and other cell(s) for half-duplex operation in TDD CA with same SCS as specified in TS 38.213 [13], clause 11.1. The half-duplex operation only applies within the same frequency range and cell group. | +| The network only configures this field for TDD serving cells that are using the same SCS. | +| directionalCollisionHandling-DC
For the IAB-MT, it indicates that this serving cell is using directional collision handling between a reference and other cell(s) for half-duplex operation in TDD NR-DC with same SCS within same cell group or cross different cell groups. | +| dormantBWP-Config
The dormant BWP configuration for an SCell. This field can be configured only for a (non-PUCCH) SCell. | +| downlinkBWP-ToAddModList
List of additional downlink bandwidth parts to be added or modified. (see TS 38.213 [13], clause 12). | +| downlinkBWP-ToReleaseList
List of additional downlink bandwidth parts to be released. (see TS 38.213 [13], clause 12). | +| downlinkChannelBW-PerSCS-List
A set of UE specific channel bandwidth and location configurations for different subcarrier spacings (numerologies). Defined in relation to Point A. The UE uses the configuration provided in this field only for the purpose of channel bandwidth and location determination. If absent, UE uses the configuration indicated in scs-SpecificCarrierList in DownlinkConfigCommon / DownlinkConfigCommonSIB . Network only configures channel bandwidth that corresponds to the channel bandwidth values defined in TS 38.101-1 [15], TS 38.101-2 [39], and TS 38.101-5 [75]. If the UE is a RedCap UE and needs to autonomously switch to its initial downlink bandwidth part to perform a random access procedure but its current UE specific channel bandwidth does not cover the initial downlink bandwidth part, the UE autonomously changes its UE specific channel bandwidth to cover the initial downlink bandwidth part. In that case, after completion of the random access procedure, the network ensures that the UE specific channel bandwidth fully covers the UE's active downlink bandwidth part in subsequent bandwidth part switch operations. | +| dummy1, dummy 2
This field is not used in the specification. If received it shall be ignored by the UE. | +| enableBeamSwitchTiming
Indicates the aperiodic CSI-RS triggering with beam switching triggering behaviour as defined in clause 5.2.1.5.1 of TS 38.214 [19]. | +| enableDefaultTCI-StatePerCoresetPoolIndex
Presence of this field indicates the UE shall follow the release 16 behavior of default TCI state per CORESETPoolIndex when the UE is configured by higher layer parameter PDCCH-Config that contains two different values of CORESETPoolIndex in ControlResourceSet is enabled. | +| enableTwoDefaultTCI-States
Presence of this field indicates the UE shall follow the release 16 behavior of two default TCI states for PDSCH when at least one TCI codepoint is mapped to two TCI states is enabled | +| fdmed-ReceptionMulticast
Indicates the Type-1 HARQ codebook generation as specified in TS 38.213 [13], clause 9.1.2.1. | +| firstActiveDownlinkBWP-Id
If configured for an SpCell, this field contains the ID of the DL BWP to be activated or to be used for RLM, BFD and measurements if included in an RRCReconfiguration message contained in an NR or E-UTRA RRC message indicating that the SCG is deactivated, upon performing the RRC (re-)configuration. If the field is absent, the RRC (re-)configuration does not impose a BWP switch. If the field is absent for the PSCell at SCG deactivation, the UE considers the previously activated DL BWP as the BWP to be used for RLM, BFD and measurements. If the field is absent for the PSCell at SCG activation, the DL BWP to be activated is the DL BWP previously to be used for RLM, BFD and measurements.
If configured for an SCell, this field contains the ID of the downlink bandwidth part to be used upon activation of an SCell. The initial bandwidth part is referred to by BWP-Id = 0.
Upon reconfiguration with reconfigurationWithSync , the network sets the firstActiveDownlinkBWP-Id and firstActiveUplinkBWP-Id to the same value. | +| initialDownlinkBWP
The dedicated (UE-specific) configuration for the initial downlink bandwidth-part (i.e., DL BWP#0). If any of the optional IEs are configured within this IE, the UE considers the | + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| BWP#0 to be an RRC configured BWP (from UE capability viewpoint). Otherwise, the UE does not consider the BWP#0 as an RRC configured BWP (from UE capability viewpoint). Network always configures the UE with a value for this field if no other BWPs are configured. NOTE1 | +| intraCellGuardBandsDL-List, intraCellGuardBandsUL-List
List of intra-cell guard bands in a serving cell for operation with shared spectrum channel access in FR1. If not configured, the guard bands are defined according to 38.101-1 [15], see TS 38.214 [19], clause 7. For operation in licensed spectrum, this field is absent, and no UE action is required. | +| lte-CRS-PatternList1
A list of LTE CRS patterns around which the UE shall do rate matching for PDSCH. The LTE CRS patterns in this list shall be non-overlapping in frequency. The network does not configure this field and lte-CRS-ToMatchAround simultaneously. | +| lte-CRS-PatternList2
A list of LTE CRS patterns around which the UE shall do rate matching for PDSCH scheduled with a DCI detected on a CORESET with CORESETPoolIndex configured with 1. This list is configured only if CORESETPoolIndex configured with 1. The first LTE CRS pattern in this list shall be fully overlapping in frequency with the first LTE CRS pattern in lte-CRS-PatternList1 , The second LTE CRS pattern in this list shall be fully overlapping in frequency with the second LTE CRS pattern in lte-CRS-PatternList1 , and so on. Network configures this field only if the field lte-CRS-ToMatchAround is not configured and there is at least one ControlResourceSet in one DL BWP of this serving cell with coresetPoolIndex set to 1. | +| lte-CRS-PatternList3
A list of LTE CRS patterns around which the UE shall do rate matching for PDSCH. The LTE CRS patterns in this list shall be non-overlapping in frequency. The network does not configure this field and lte-CRS-ToMatchAround , or this field and lte-CRS-PatternList1 , or this field and lte-CRS-PatternList2 simultaneously. | +| lte-CRS-PatternList4
A list of LTE CRS patterns around which the UE shall do rate matching for PDSCH. The LTE CRS patterns in this list shall be non-overlapping in frequency. The first LTE CRS pattern in this list shall be fully overlapping in frequency with the first LTE CRS pattern in lte-CRS-PatternList3 . The second LTE CRS pattern in this list shall be fully overlapping in frequency with the second LTE CRS pattern in lte-CRS-PatternList3 , and so on. Network configures this field only if the field lte-CRS-ToMatchAround is not configured and the field lte-CRS-PatternList3 is configured. | +| lte-CRS-ToMatchAround
Parameters to determine an LTE CRS pattern that the UE shall rate match around. | +| lte-NeighCellsCRS-AssistInfoList
A list of LTE neighbour cells configuration information which is used to assist the UE to perform CRS interference mitigation (CRS-IM) in scenarios with overlapping spectrum for LTE and NR (see TS 38.101-4 [59]). If the field is included, it replaces any previous list, i.e. all the entries of the list are replaced and each of the LTE-NeighCellsCRS-AssistInfo entries is considered to be newly created and the conditions and Need codes for setup of the entry apply. | +| lte-NeighCellsCRS-Assumptions
If the field is not configured, the following default network configuration assumptions are valid for all LTE neighbour cells for the purpose of CRS interference mitigation (CRS-IM) in scenarios with overlapping spectrum for LTE and NR (see TS 38.101-4 [59]).
  • - The CRS port number is the same as the one indicated in RateMatchPatternLTE-CRS if configured for the serving cell.
  • - The CRS port number is 4 if RateMatchPatternLTE-CRS is not configured for the serving cell.
  • - The channel bandwidth and centre frequency are the same as the ones indicated in RateMatchPatternLTE-CRS if configured for the serving cell.
  • - The MBSFN configuration is the same as the one indicated in RateMatchPatternLTE-CRS if configured for the serving cell. If RateMatchPatternLTE-CRS is not configured for the serving cell, MBSFN subframe is not configured.
  • - Network-based CRS interference mitigation (i.e., CRS muting), as in crs-IntfMitigConfig specified in TS 36.331 [10], is not enabled.
If the field is configured (i.e. false) and LTE-NeighCellsCRS-AssistInfoList is configured, the configuration provided in LTE-NeighCellsCRS-AssistInfoList overrides the default network configuration assumptions.
If the field is configured (i.e. false) and LTE-NeighCellsCRS-AssistInfoList is not configured, it is up to the UE implementation whether to apply CRS-IM operation. | +| mc-DCI-SetOfCellsToAddModList
List of up to N (N<=4) configurations of set(s) of cells for multi-cell PDSCH/PUSCH scheduling from the serving cell, where N is reported as UE capability and up to 4 sets of cells can be configured per PUCCH group. When this field is configured to a SCell, PCell cannot be included in either ScheduledCellListDCI-1-3 or ScheduledCellListDCI-0-3 . | +| multiPDSCH-PerSlotType1-CB | + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Configures the UE behaviour for Type1 codebook HARQ ACK generation regarding the number of PDSCHs per slot on a serving cell as specified in TS 38.213 [13], clause 9.1.2.1.

When this parameter is configured and set to disabled for a serving cell, the network does not schedule UE with more than one PDSCH in a slot on the serving cell if HARQ-ACKs of any two PDSCHs in the slot on the serving cell are supposed to be reported on one PUCCH resource in the same PUCCH slot. If two coresetPoolIndex values are configured, the number of received PDSCHs is per coresetPoolIndex value per slot for a serving cell. If the UE generates two HARQ-ACK codebooks for two priorities, the number of received PDSCHs is per priority per slot for a serving cell. If fdmed-ReceptionMulticast is configured, the number of received PDSCHs is per traffic type (unicast / multicast) per slot for a serving cell.

| +|

nr-dl-PRS-PDC-Info

Configures the DL PRS for propagation delay compensation. When configured, the UE measures the UE Rx-Tx time difference based on the reference signals configured in this field.

| +|

nrofHARQ-BundlingGroups

Indicates the number of HARQ bundling groups for type2 HARQ-ACK codebook.

| +|

pathlossReferenceLinking

Indicates whether UE shall apply as pathloss reference either the downlink of SpCell (PCell for MCG or PSCell for SCG) or of SCell that corresponds with this uplink (see TS 38.213 [13], clause 7).

| +|

pdcch-CandidateReceptionWith-CRS-Overlap

Presence of this field indicates the UE shall monitor PDCCH candidates that overlap with LTE CRS RE(s).

| +|

pdsch-ServingCellConfig

PDSCH related parameters that are not BWP-specific.

| +|

positionInDCI-cellDTRX

The starting bit position of an information block of DCI format 2_9 for this serving cell (see TS 38.212 [17], clause 7.3.1.3.10).

| +|

rateMatchPatternToAddModList

Resources patterns which the UE should rate match PDSCH around. The UE rate matches around the union of all resources indicated in the rate match patterns. Rate match patterns defined here on cell level apply only to PDSCH of the same numerology. See TS 38.214 [19], clause 5.1.4.1. If a RateMatchPattern with the same RateMatchPatternId is configured in both ServingCellConfig/ServingCellConfigCommon and in SIB20/MCCH, the entire RateMatchPattern configuration shall be the same, including the set of RBs/REs indicated by the patterns for the rate matching around, and they are counted as a single rate match pattern in the total configured rate match patterns as defined in TS 38.214 [19].

| +|

sCellDeactivationTimer

SCell deactivation timer in TS 38.321 [3]. If the field is absent, the UE applies the value infinity.

| +|

sfnSchemePDCCH

This parameter is used to configure single frequency network scheme for PDCCH: sfnSchemeA or sfnSchemeB as specified (see TS 38.214 [19], clause 5.1). If network includes both sfnSchemePDCCH and sfnSchemePDSCH, same value shall be configured.

| +|

sfnSchemePDSCH

This parameter is used to configure single frequency network scheme for PDSCH: sfnSchemeA or sfnSchemeB as specified (see TS 38.214 [19], clause 5.1). If network includes both sfnSchemePDCCH and sfnSchemePDSCH, same value shall be configured. The network does not configure this parameter and repetitionSchemeConfig in PDSCH-Config simultaneously in the same serving cell.

| +|

semiStaticChannelAccessConfigUE

When this field is configured and when channelAccessMode-r16 (see IE ServingCellConfigCommon and IE ServingCellConfigCommonSIB) is configured to semiStatic, the UE operates in semi-static channel access mode and can initiate a channel occupancy periodically (see TS 37.213 [48], Clause 4.3). The period can be configured independently from period configured in SemiStaticChannelAccessConfig-r16 if the UE indicates the corresponding capability. Otherwise, the periodicity configured by periodUE-r17 is an integer multiple of or an integer factor of the periodicity indicated by period in SemiStaticChannelAccessConfig-r16.

| +|

servingCellMO

measObjectId of the MeasObjectNR in MeasConfig which is associated to the serving cell. For this MeasObjectNR, the following relationship applies between this MeasObjectNR and frequencyInfoDL in ServingCellConfigCommon/ServingCellConfigCommonSIB of the serving cell: if ssbFrequency is configured, its value is the same as

| + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| the absoluteFrequencySSB and if csi-rs-ResourceConfigMobility is configured, the value of its subcarrierSpacing is present in one entry of the scs-SpecificCarrierList , csi-RS-CellListMobility includes an entry corresponding to the serving cell (with cellId equal to physCellId in ServingCellConfigCommon ) and the frequency range indicated by the csi-rs-MeasurementBW of the entry in csi-RS-CellListMobility is included in the frequency range indicated by in the entry of the scs-SpecificCarrierList . | +| supplementaryUplink
Network may configure this field only when supplementaryUplinkConfig is configured in ServingCellConfigCommon or supplementaryUplink is configured in ServingCellConfigCommonSIB . | +| supplementaryUplinkRelease
If this field is included, the UE shall release the uplink configuration configured by supplementaryUplink . The network only includes either supplementaryUplinkRelease or supplementaryUplink at a time. | +| tag-Id, tag2-Id
Timing Advance Group ID, as specified in TS 38.321 [3], which this cell or set of TCI-States of this cell belongs to. The tag2-Id is optionally configured in a serving cell if and only if the serving cell is configured with more than one value for the coresetPoolIndex | +| tag2-flag
If this field is set to true , the tag2-Id is associated to value 0 and tag-Id is associated to value 1 of field TI bit in RAR , fallbackRAR and in the absolute TAC MAC CE, see TS 38.321 [3]. Otherwise, the tag2-Id is associated to value 1 and tag-Id is associated to value 0 of field R bit in RAR, fallbackRAR and in the absolute TAC MAC CE, see TS 38.321 [3]. | +| tci-ActivatedConfig
If configured for an SCell, or if configured for the PSCell when the SCG is being activated upon the reception of the containing message, the UE shall consider the TCI states provided in this field as the activated TCI states for PDCCH/PDSCH reception on this serving cell.
If configured for the PSCell when the SCG is indicated as deactivated in the containing message:
- the UE shall consider the TCI states provided in this field as the TCI states to be activated for PDCCH/PDSCH reception upon a later SCG activation in which tci-ActivatedConfig is absent
- if bfd-and-RLM is configured and no RS is configured in RadioLinkMonitoringConfig for RLM, respectively for BFD, the UE shall use the TCI states provided in this field for PDCCH as RS for RLM, respectively for BFD.
When this field is absent for the PSCell and the SCG is being deactivated:
- the UE shall consider the previously activated TCI states as the TCI states to be activated for PDCCH/PDSCH reception upon a later SCG activation in which tci-ActivatedConfig is absent
- if bfd-and-RLM is configured and no RS is configured in RadioLinkMonitoringConfig for RLM, respectively for BFD, the UE shall use the previously activated TCI states for PDCCH as RS for RLM, respectively for BFD. | +| tdd-UL-DL-ConfigurationDedicated-IAB-MT
Resource configuration per IAB-MT D/U/F overrides all symbols (with a limitation that effectively only flexible symbols can be overwritten in Rel-16) per slot over the number of slots as provided by TDD-UL-DL ConfigurationCommon . | +| unifiedTCI-StateType
Indicates the unified TCI state type the UE is configured for this serving cell. The value separate means this serving cell is configured with dl-OrJointTCI-StateList for DL TCI state and ul-TCI-ToAddModList for UL TCI state. The value joint means this serving cell is configured with dl-OrJointTCI-StateList for joint TCI state for UL and DL operation. | +| uplinkConfig
Network may configure this field only when uplinkConfigCommon is configured in ServingCellConfigCommon or ServingCellConfigCommonSIB . Addition or release of this field can only be done upon SCell addition or release (respectively). | +| uplink-PowerControlToAddModList
Configures UL power control parameters for PUSCH, PUCCH and SRS when field unifiedTCI-StateType is configured for this serving cell. | + +| UplinkConfig field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| carrierSwitching
Includes parameters for configuration of carrier based SRS switching (see TS 38.214 [19], clause 6.2.1.3. | +| enableDefaultBeamPL-ForPUSCH0-0, enableDefaultBeamPL-ForPUCCH, enableDefaultBeamPL-ForSRS
When the parameter is present, UE derives the spatial relation and the corresponding pathloss reference Rs as specified in 38.213, clauses 7.1.1, 7.2.1, 7.3.1 and 9.2.2. The network only configures these parameters for FR2. | +| enablePL-RS-UpdateForPUSCH-SRS
When this parameter is present, the Rel-16 feature of MAC CE based pathloss RS updates for PUSCH/SRS is enabled. Network only configures this parameter when the UE is configured with sri-PUSCH-PowerControl . If this field is not configured, network configures at most 4 pathloss RS resources for PUSCH/PUCCH/SRS transmissions per BWP, not including pathloss RS resources for SRS transmissions for positioning. (See TS 38.213 [13], clause 7). | +| firstActiveUplinkBWP-Id
If configured for an SpCell, this field contains the ID of the UL BWP to be activated upon performing the RRC (re-)configuration. If the field is absent, the RRC (re-)configuration does not impose a BWP switch.
If configured for an SCell, this field contains the ID of the uplink bandwidth part to be used upon activation of an SCell. The initial bandwidth part is referred to by BandwidthPartId = 0. | +| initialUplinkBWP
The dedicated (UE-specific) configuration for the initial uplink bandwidth-part (i.e. UL BWP#0). If any of the optional IEs are configured within this IE as part of the IE uplinkConfig , the UE considers the BWP#0 to be an RRC configured BWP (from UE capability viewpoint). Otherwise, the UE does not consider the BWP#0 as an RRC configured BWP (from UE capability viewpoint). Network always configures the UE with a value for this field if no other BWPs are configured. NOTE1 | +| moreThanOneNackOnlyMode
Indicates the mode of NACK-only feedback in the PUCCH transmission, as specified in TS 38.213 [13], clause 18. If multicast CFR is not configured, this field is not included. Otherwise, if the field is absent, UE uses mode 1 for multicast CFR. | +| mpr-PowerBoost-FR2
Indicates whether UE is allowed to boost uplink transmission power by suspending in-band emission (IBE) requirements as specified in TS 38.101-2 [39]. Network only configures this field for FR2 serving cells. | +| powerBoostPi2BPSK
If this field is set to true , the UE determines the maximum output power for PUCCH/PUSCH transmissions that use pi/2 BPSK modulation according to TS 38.101-1 [15], clause 6.2.4. | +| pusch-ServingCellConfig
PUSCH related parameters that are not BWP-specific. | +| srs-PosTx-Hopping
Contains configuration related to the SRS for Positioning hopping outside the active BWP of the UE. | +| uplinkBWP-ToAddModList
The additional bandwidth parts for uplink to be added or modified. In case of TDD uplink- and downlink BWP with the same bandwidthPartId are considered as a BWP pair and must have the same center frequency. | +| uplinkBWP-ToReleaseList
The additional bandwidth parts for uplink to be released. | +| uplinkChannelBW-PerSCS-List
A set of UE specific channel bandwidth and location configurations for different subcarrier spacings (numerologies). Defined in relation to Point A. The UE uses the configuration provided in this field only for the purpose of channel bandwidth and location determination. If absent, UE uses the configuration indicated in scs-SpecificCarrierList in UplinkConfigCommon / UplinkConfigCommonSIB . Network only configures channel bandwidth that corresponds to the channel bandwidth values defined in TS 38.101-1 [15], TS 38.101-2 [39], and TS 38.101-5 [75]. If the UE is a RedCap UE and needs to autonomously switch to its initial uplink bandwidth part to perform a random access procedure but its current UE specific channel bandwidth does not cover the initial uplink bandwidth part, the UE autonomously changes its UE specific channel bandwidth to cover the initial uplink bandwidth part. In that case, after completion of the random access procedure, the network ensures that the UE specific channel bandwidth | + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| fully covers the UE's active uplink bandwidth part in subsequent bandwidth part switch operations. | +| uplinkTxSwitchingPeriodLocation
Indicates whether the location of UL Tx switching period is configured in this uplink carrier in case of inter-band UL CA, SUL, or (NG)EN-DC, as specified in TS 38.101-1 [15] and TS 38.101-3 [34].
In case of (NG)EN-DC, network always configures this field to TRUE for NR carrier (i.e. with (NG)EN-DC, the UL switching period always occurs on the NR carrier).
In case of inter-band UL CA or SUL, for dynamic uplink Tx switching between 2 bands with 2 uplink carriers or 3 uplink carriers as defined in TS 38.101-1 [15], network configures this field to TRUE for the uplink carrier(s) on one band and configures this field to FALSE for the uplink carrier(s) on the other band. This field is set to the same value for the carriers on the same band. | +| uplinkTxSwitchingCarrier
Indicates that the configured carrier is carrier1 or carrier2 for dynamic uplink Tx switching, as defined in TS 38.101-1 [15] and TS 38.101-3 [34]. In case of (NG)EN-DC, network always configures the NR carrier as carrier 2.
In case of inter-band UL CA or SUL, for dynamic uplink Tx switching between 2 bands with 2 uplink carriers or 3 uplink carriers as defined in TS 38.101-1 [15], network configures the uplink carrier(s) on one band as carrier1 and the uplink carrier(s) on the other band as carrier2. This field is set to the same value for the carriers on the same band. | + +| DormantBWP-Config field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| dormancyGroupWithinActiveTime
This field contains the ID of an SCell group for Dormancy within active time, to which this SCell belongs. The use of the Dormancy within active time for SCell groups is specified in TS 38.213 [13]. | +| dormancyGroupOutsideActiveTime
This field contains the ID of an SCell group for Dormancy outside active time, to which this SCell belongs. The use of the Dormancy outside active time for SCell groups is specified in TS 38.213 [13]. | +| dormantBWP-Id
This field contains the ID of the downlink bandwidth part to be used as dormant BWP. If this field is configured, its value is different from defaultDownlinkBWP-Id , and at least one of the withinActiveTimeConfig and outsideActiveTimeConfig should be configured. | +| firstOutsideActiveTimeBWP-Id
This field contains the ID of the downlink bandwidth part to be activated when receiving a DCI indication for SCell dormancy outside active time. | +| firstWithinActiveTimeBWP-Id
This field contains the ID of the downlink bandwidth part to be activated when receiving a DCI indication for SCell dormancy within active time. | +| outsideActiveTimeConfig
This field contains the configuration to be used for SCell dormancy outside active time, as specified in TS 38.213 [13]. The field can only be configured when the cell group the SCell belongs to is configured with dcp-Config . | +| withinActiveTimeConfig
This field contains the configuration to be used for SCell dormancy within active time, as specified in TS 38.213 [13]. | + +| GuardBand field descriptions | +|---------------------------------------------------------------------------------------------------------------| +| startCRB
Indicates the starting RB of the guard band. | +| nrofCRB
Indicates the length of the guard band in RBs. When set to 0, zero-size guard band is used. | + +| MC-DCI-SetOfCells field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| antennaPortsDCI1-3, antennaPortsDCI0-3
Configure the indication type for antenna port(s) field in DCI format 1_3 and DCI format 0_3, respectively (See TS 38.212, clause 7.3.1.2.4). | +| dormancyDCI-1-3, dormancyDCI-0-3
Configure the presence of Scell dormancy indication field in DCI format 1_3 and DCI format 0_3, respectively. | +| minimumSchedulingOffsetK0DCI-1-3, minimumSchedulingOffsetK0DCI-0-3
Configure the presence of minimum applicable scheduling offset indicator field in DCI format 1_3 and DCI format 0_3, respectively. | +| nCI-Value
Configure n_CI value used for the set of cells, where unique n_CI value is configured for each set of cells. | +| pdcchMonAdaptDCI-1-3, pdcchMonAdaptDCI-0-3
Configure the presence of PDCCH monitoring adaptation indication field in DCI format 1_3 and DCI format 0_3, respectively. | +| pdsch-HARQ-ACK-enhType3DCI-1-3
Enable the enhanced Type 3 HARQ-ACK codebook triggering using DCI format 1_3. | +| pdsch-HARQ-ACK-enhType3DCIfieldDCI-1-3
Enables the enhanced Type 3 CB through a new DCI field to indicate the enhanced Type 3 HARQ-ACK codebook in DCI format 1_3 if the more than one enhanced Type HARQ-ACK codebook is configured for the primary PUCCH cell group. | +| pdsch-HARQ-ACK-OneShotFeedbackDCI-1-3
When configured, the DCI format 1_3 can request the UE to report A/N for all HARQ processes and all CCs configured in the PUCCH group. | +| pdsch-HARQ-ACK-retxDCI-1-3
When configured, the DCI format 1_3 can request the UE to perform a HARQ-ACK re-transmission on a PUCCH resource. | +| priorityIndicatorDCI-1-3, priorityIndicatorDCI-0-3
Configure the presence of priority indicator field in DCI format 1_3 and DCI format 0_3, respectively. | +| pucch-sSCellDynDCI-1-3
Configure the UE with PUCCH cell switching based on dynamic indication in DCI format 1_3. | +| RateMatchDCI-1-3
Configure each row of the joint rate matching indication table for DL scheduling via DCI format 1_3, where bitmap for a cell points to a corresponding rate matching indication applicable for DCI format 1-1 (i.e., MSB and LSB of bitmap refer rateMatchPatternGroup1 and rateMatchPatternGroup2 for a cell, respectively), the order of rate matching indication bitmap in each row refers the order of cells in ScheduledCell-ListDCI-1-3 , that are configured with rateMatchPatternGroup1 or rateMatchPatternGroup2 on at least one DL BWP (i.e., first bitmap is for the first cell in ScheduledCell-ListDCI-1-X , that are configured with rateMatchPatternGroup1 or rateMatchPatternGroup2 on at least one DL BWP and so on), the number of entries in a row of rateMatchDCI-1-3 should be the same as the number of cells, that are configured with rateMatchPatternGroup1 or rateMatchPatternGroup2 on at least one DL BWP, included in ScheduledCell-ListDCI-1-3 , and entries for co-scheduled cells in a row of rateMatchDCI-1-3 are interpreted based on the BWPs of co-scheduled cells that is determined by the BWP indicator field of DCI format 1_3. | +| rateMatchListDCI-1-3
Configure joint rate matching indication table for DL scheduling via DCI format 1_3. | +| ScheduledCellCombo
Configure each row of the table for combinations of co-scheduled cells for DL scheduling via DCI format 1_3 and for UL scheduling via DCI format 0_3, where index with value INTEGER (0...3) of co-scheduled cell refers to ScheduledCell-ListDCI-1-3 for DL and ScheduledCell-ListDCI-0-3 for UL. | +| scheduledCellComboListDCI-1-3, scheduledCellComboListDCI-0-3
Configure the table for combinations of co-scheduled cells for DL scheduling via DCI format 1_3 and DCI format 0_3, respectively. | +| scheduledCellListDCI-1-3, scheduledCellListDCI-0-3
Configure the list of possible co-scheduled cells in the set for DL scheduling via DCI format 1_3 and DCI format 0_3 respectively, where the serving cells in the list are in ascending order of serving cell indices and are mapped to index {0, 1, 2, 3} in the set. Total number of cells within the same set of cells i.e., in ScheduledCell-ListDCI-1-3 and ScheduledCell-ListDCI-0-3 , is up to 4.
When a cell is included in either or both of ScheduledCell-ListDCI-1-3 or ScheduledCell-ListDCI-0-3 for one set of cells MC-DCI-SetOfCells , the cell cannot be included in any | + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| of ScheduledCell-ListDCI-1-3 or ScheduledCell-ListDCI-0-3 for any other set of cells. | +| setOfCellsId
Configure index of the set of cells to be indicated in DCI format 0_3/1_3. | +| sri-DCI0-3
Configure the indication type for SRS resource indicator field in DCI format 0_3 (See TS 38.212, clause 7.3.1.1.4). | +| SRS-OffsetCombo
Configure each row of the joint SRS offset indicator table for DL scheduling via DCI format 1_3 and for UL scheduling via DCI format 0_3, where index for a cell points to a corresponding SRS offset indicator applicable for DCI format 1-1 and 0-1, and the order of SRS offset indicator index in each row refers the order of cells in ScheduledCell-ListDCI-1-3 (i.e., first index is for the first cell in ScheduledCell-ListDCI-1-3 , that are configured with more than one entry in availableSlotOffsetList for at least one aperiodic SRS resource set on at least one UL BWP and so on) for DL and ScheduledCell-ListDCI-0-3 for UL, included in ScheduledCell-ListDCI-1-3 for srs-OffsetListDCI-1-3 and ScheduledCell-ListDCI-0-3 for srs-OffsetListDCI-0-3 , and entries for co-scheduled cells in a row of SRS-OffsetCombo are interpreted based on the BWPs of co-scheduled cells that is determined by the BWP indicator field of DCI format 1_3/0_3. | +| srs-OffsetListDCI-1-3, srs-OffsetListDCI-0-3
Configure joint SRS offset indicator table for DL scheduling via DCI format 1_3 and DCI format 0_3, respectively. | +| SRS-RequestCombo
Configure each row of the joint SRS request table for DL scheduling via DCI format 1_3 and for UL scheduling via DCI format 0_3, where index for a cell points to a corresponding SRS request applicable for DCI format 1-1 and 0-1, and the order of SRS request index in each row refers the order of cells in ScheduledCell-ListDCI-1-3 (i.e., first index is for the first cell in ScheduledCell-ListDCI-1-3 and so on) for DL and ScheduledCell-ListDCI-0-3 for UL. The number of entries in a row of SRS-RequestCombo should be the same as the number of cells included in ScheduledCell-ListDCI-1-3 for srs-RequestListDCI-1-3 and ScheduledCell-ListDCI-0-3 for srs-RequestListDCI-0-3 , and entries for co-scheduled cells in a row of SRS-RequestCombo are interpreted based on the BWPs of co-scheduled cells that is determined by the BWP indicator field of DCI format 1_3/0_3. | +| srs-RequestListDCI-1-3, srs-RequestListDCI-0-3
Configure joint SRS request table for DL scheduling via DCI format 1_3 and DCI format 0_3, respectively. | +| TCI-DCI-1-3
Configure each row of the joint TCI table for DL scheduling via DCI format 1_3, where index for a cell points to a corresponding TCI applicable for DCI format 1-1, and the order of TCI index in each row refers the order of cells in ScheduledCell-ListDCI-1-3 (i.e., first index is for the first cell in ScheduledCell-ListDCI-1-3 that configured with tci-StatesToAddModList and so on), the number of entries in a row of TCI-DCI-1-3 should be the same as the number of cells that configured with tci-StatesToAddModList on at least one DL BWP, included in ScheduledCell-ListDCI-1-3 , and entries for co-scheduled cells in a row of TCI-DCI-1-3 are interpreted based on the BWPs of co-scheduled cells that is determined by the BWP indicator field of DCI format 1_3. | +| tci-ListDCI-1-3
Configure joint TCI table for DL scheduling via DCI format 1_3 | +| TDRA-FieldIndexDC-0-3
Configure each row of the joint TDRA field table for UL scheduling via DCI format 0_3 containing the applicable TDRA field indexes for multiple BWPs/cells, where the TDRA index for a BWP of a cell points to a corresponding TDRA in the TDRA table applicable for DCI format 0-1, the order of TDRA index in each row refers the BWP-Id for a cell and the order of cells in ScheduledCell-ListDCI-0-3 (i.e., first TDRA index in a row is for the smallest BWP-Id that can be scheduled by the DCI format 0-3, as specified in 38.212, of the first cell in ScheduledCell-ListDCI-0-3 , second TDRA index in a row is for the second smallest BWP-Id that can be scheduled by the DCI format 0-3, as specified in 38.212, of the first cell and so on), and the number of TDRA indices in a row of TDRA-FieldIndexDCI-0-3 should be the same as the total number of BWPs that can be scheduled by the DCI format 0-3, as specified in 38.212, across cells included in ScheduledCell-ListDCI-0-3 . | +| TDRA-FieldIndexDCI-1-3
Configure each row of the joint TDRA field table for DL scheduling via DCI format 1_3 containing the applicable TDRA field indexes for multiple BWPs/cells, where the TDRA index for a BWP of a cell points to a corresponding TDRA in the TDRA table applicable for DCI format 1-1, the order of TDRA index in each row refers the BWP-Id for a cell and the order of cells in ScheduledCell-ListDCI-1-3 (i.e., first TDRA index in a row is for the smallest BWP-Id that can be scheduled by the DCI format 1-3, as specified in 38.212, of the first cell in ScheduledCell-ListDCI-1-3 , second TDRA index in a row is for the second smallest BWP-Id that can be scheduled by the DCI format 1-3, as specified in 38.212, of the first cell and so on ), and the number of TDRA indices in a row of TDRA-FieldIndexDCI-1-3 should be the same as the total number of BWPs that can be | + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| scheduled by the DCI format 1-3, as specified in 38.212, across cells included in ScheduledCell-ListDCI-1-3 . | +| tdra-FieldIndexListDCI-1-3, tdra-FieldIndexListDC-0-3
Configure joint TDRA table for UL scheduling via DCI format 1_3 and DCI format 0_3, respectively. | +| tpmi-DCI0-3
Configure the indication type for precoding information and number of layers field in DCI format 0_3 (See TS 38.212, clause 7.3.1.1.4). | +| ZP-CSI-DCI-1-3
Configure each row of the joint ZP-CSI-RS trigger table for DL scheduling via DCI format 1_3, where index for a cell points to a corresponding ZP-CSI-RS trigger applicable for DCI format 1-1, and the order of ZP-CSI-RS trigger index in each row refers the order of cells in ScheduledCell-ListDCI-1-3 (i.e., first index is for the first cell in ScheduledCell-ListDCI-1-3 , that are configured with aperiodic-ZP-CSI-RS-ResourceSetsToAddModList on at least one DL BWP and so on), the number of entries in a row of ZP-CSI-DCI-1-3 should be the same as the number of cells, that are configured with aperiodic-ZP-CSI-RS-ResourceSetsToAddModList on at least one DL BWP, included in ScheduledCell-ListDCI-1-3 , and entries for co-scheduled cells in a row of ZP-CSI-DCI-1-3 are interpreted based on the BWPs of co-scheduled cells that is determined by the BWP indicator field of DCI format 1_3. | +| zp-CSI-RSListDCI-1-3
Configure joint ZP-CSI-RS trigger table for DL scheduling via DCI format 1_3. | + +NOTE 1: If the dedicated part of initial UL/DL BWP configuration is absent, the initial BWP can be used but with some limitations. For example, changing to another BWP requires *RRCReconfiguration* since DCI format 1\_0 doesn't support DCI-based switching. + +| Conditional Presence | Explanation | +|--------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AsyncCA | This field is mandatory present for SCells whose slot offset between the SpCell is not 0. Otherwise it is absent, Need S. | +| MeasObject | This field is mandatory present for the SpCell if the UE has a measConfig , and it is optionally present, Need M, for SCells. For (e)RedCap UEs, this field is optionally present, Need M. | +| SCellOnly | This field is optionally present, Need R, for SCells. It is absent otherwise. | +| ServingCellWithoutPUCCH | This field is optionally present, Need S, for SCells except PUCCH SCells. It is absent otherwise. | +| SyncAndCellAdd | This field is mandatory present for a SpCell upon reconfiguration with reconfigurationWithSync and upon RRCSsetup/RRCSresume .
The field is optionally present for an SpCell, Need N, upon reconfiguration without reconfigurationWithSync .
The field is mandatory present for an SCell upon addition, and absent for SCell in other cases, Need M. | +| Tag2 | This field is optional present, Need R, if tag2 is present. Otherwise it shall be absent. | +| TCI_ActivatedConfig | This field is optional Need N for SCells if sCellState is configured, otherwise it is absent.
This field is optional Need S for the PCell when the SCG is indicated as deactivated or is being activated, otherwise it is absent.
This field is absent for the PCell. | +| TDD | This field is optionally present, Need R, for TDD cells. It is absent otherwise. | +| TDD_IAB | For IAB-MT, this field is optionally present, Need R, for TDD cells. It is absent otherwise. | +| TypeDCI0-3 | This field is mandatory present if ScheduledCellListDCI-0-3 is configured, otherwise it is absent. | +| TypeDCI1-3 | This field is mandatory present if ScheduledCellListDCI-1-3 is configured, otherwise it is absent. | + +#### ServingCellConfigCommon + +The IE *ServingCellConfigCommon* is used to configure cell specific parameters of a UE's serving cell. The IE contains parameters which a UE would typically acquire from SSB, MIB or SIBs when accessing the cell from IDLE. With this IE, the network provides this information in dedicated signalling when configuring a UE with a SCells or with an additional cell group (SCG). It also provides it for SpCells (MCG and SCG) upon reconfiguration with sync. + +#### ServingCellConfigCommon information element + +``` +-- ASN1START +-- TAG-SERVINGCELLCONFIGCOMMON-START + +ServingCellConfigCommon ::= SEQUENCE { + physCellId PhysCellId OPTIONAL, -- Cond HOAndServCellAdd, + downlinkConfigCommon DownlinkConfigCommon OPTIONAL, -- Cond HOAndServCellAdd + uplinkConfigCommon UplinkConfigCommon OPTIONAL, -- Need M + supplementaryUplinkConfig UplinkConfigCommon OPTIONAL, -- Need S + n-TimingAdvanceOffset ENUMERATED { n0, n25600, n39936 } OPTIONAL, -- Need S + ssb-PositionsInBurst CHOICE { + shortBitmap BIT STRING (SIZE (4)), + mediumBitmap BIT STRING (SIZE (8)), + longBitmap BIT STRING (SIZE (64)) + } OPTIONAL, -- Cond AbsFreqSSB + ssb-periodicityServingCell ENUMERATED { ms5, ms10, ms20, ms40, ms80, ms160, spare2, spare1 } OPTIONAL, -- Need S + dmrs-TypeA-Position ENUMERATED {pos2, pos3}, + lte-CRS-ToMatchAround SetupRelease { RateMatchPatternLTE-CRS } OPTIONAL, -- Need M + rateMatchPatternToAddModList SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF RateMatchPattern OPTIONAL, -- Need N + rateMatchPatternToReleaseList SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF RateMatchPatternId OPTIONAL, -- Need N + ssbSubcarrierSpacing SubcarrierSpacing OPTIONAL, -- Cond HOAndServCellWithSSB + tdd-UL-DL-ConfigurationCommon TDD-UL-DL-ConfigCommon OPTIONAL, -- Cond TDD + ss-PBCH-BlockPower INTEGER (-60..50), + ... + [[ + channelAccessMode-r16 CHOICE { + dynamic NULL, + semiStatic SemiStaticChannelAccessConfig-r16 + } OPTIONAL, -- Cond SharedSpectrum + discoveryBurstWindowLength-r16 ENUMERATED {ms0dot5, ms1, ms2, ms3, ms4, ms5} OPTIONAL, -- Need R + ssb-PositionQCL-r16 SSB-PositionQCL-Relation-r16 OPTIONAL, -- Cond SharedSpectrum + highSpeedConfig-r16 HighSpeedConfig-r16 OPTIONAL -- Need R + ]], + [[ + highSpeedConfig-v1700 HighSpeedConfig-v1700 OPTIONAL, -- Need R + channelAccessMode2-r17 ENUMERATED {enabled} OPTIONAL, -- Cond SharedSpectrum2 + discoveryBurstWindowLength-r17 ENUMERATED {ms0dot125, ms0dot25, ms0dot5, ms0dot75, ms1, ms1dot25} OPTIONAL, -- Need R + ssb-PositionQCL-r17 SSB-PositionQCL-Relation-r17 OPTIONAL, -- Cond SharedSpectrum2 + highSpeedConfigFR2-r17 HighSpeedConfigFR2-r17 OPTIONAL, -- Need R + uplinkConfigCommon-v1700 UplinkConfigCommon-v1700 OPTIONAL, -- Need R + ntn-Config-r17 NTN-Config-r17 OPTIONAL -- Need R + ]], +} +``` + +``` +[[ + featurePriorities-r17 SEQUENCE { + redCapPriority-r17 FeaturePriority-r17 OPTIONAL, -- Need R + slicingPriority-r17 FeaturePriority-r17 OPTIONAL, -- Need R + msg3-Repetitions-Priority-r17 FeaturePriority-r17 OPTIONAL, -- Need R + sdt-Priority-r17 FeaturePriority-r17 OPTIONAL -- Need R + } +], [ + ra-ChannelAccess-r17 ENUMERATED {enabled} OPTIONAL -- Cond SharedSpectrum2 +], [ + featurePriorities-v1800 SEQUENCE { + msg1-Repetitions-Priority-r18 FeaturePriority-r17 OPTIONAL, + eRedCapPriority-r18 FeaturePriority-r17 OPTIONAL -- Need R + } + atg-Config-r18 ATG-Config-r18 OPTIONAL, -- Need R +]] +} + +-- TAG-SERVINGCELLCONFIGCOMMON-STOP +-- ASN1STOP +``` + +| ServingCellConfigCommon field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| channelAccessMode
If present, this field indicates which channel access procedures to apply for operation with shared spectrum channel access as defined in TS 37.213 [48]. If the field is configured as "semiStatic", the UE shall apply the channel access procedures for semi-static channel occupancy as described in clause 4.3 in TS 37.213. If the field is configured as "dynamic", the UE shall apply the channel access procedures as defined in TS 37.213, clause 4.1 and 4.2. | +| channelAccessMode2
If present, the UE shall apply channel access procedures for operation with shared spectrum channel access in accordance with TS 37.213 [48], clause 4.4 for FR2-2. If absent, the UE shall not apply any channel access procedure. The network always configures this field if channel access procedures are required for the serving cell within this region by regulations. | +| dmrs-TypeA-Position
Position of (first) DM-RS for downlink (see TS 38.211 [16], clause 7.4.1.1.1) and uplink (TS 38.211 [16], clause 6.4.1.1.3). | +| downlinkConfigCommon
The common downlink configuration of the serving cell, including the frequency information configuration and the initial downlink BWP common configuration. The parameters provided herein should match the parameters configured by MIB and SIB1 (if provided) of the serving cell, with the exception of controlResourceSetZero and searchSpaceZero which can be configured in ServingCellConfigCommon even if MIB indicates that they are absent. | +| discoveryBurstWindowLength
Indicates the window length of the discovery burst in ms (see TS 37.213 [48]). The field discoveryBurstWindowLength-r17 is applicable to SCS 480 kHz and SCS 960 kHz. | +| featurePriorities
Indicates priorities for features, such as (e)RedCap, Slicing, SDT, MSG1-Repetitions, and MSG3-Repetitions for Coverage Enhancements. These priorities are used to determine which FeatureCombinationPreambles the UE shall use when a feature maps to more than one FeatureCombinationPreambles , as specified in TS 38.321 [3]. A lower value means a higher priority. The network does not signal the same priority for more than one feature. The network signals a priority for all feature that map to at least one FeatureCombinationPreambles . | +| longBitmap
Bitmap when maximum number of SS/PBCH blocks per half frame equals to 64 as defined in TS 38.213 [13], clause 4.1. | +| lte-CRS-ToMatchAround
Parameters to determine an LTE CRS pattern that the UE shall rate match around. | +| mediumBitmap
Bitmap when maximum number of SS/PBCH blocks per half frame equals to 8 as defined in TS 38.213 [13], clause 4.1. | +| n-TimingAdvanceOffset
The N_TA-Offset to be applied for all uplink transmissions on this serving cell if n-TimingAdvanceOffset is not configured. If tag2 is configured for this serving cell, this field is to be applied to all uplink transmissions associated to tag-id configured for this serving cell. If the field is absent, the UE applies the value defined for the duplex mode and frequency range of this serving cell. See TS 38.133 [14], table 7.1.2-2. | +| ra-ChannelAccess
If present, this field indicates that the UE shall apply channel access procedures before msg1/msgA transmission for operation with shared spectrum channel access in accordance with TS 37.213 [48], clause 4.4.5 for FR2-2. | +| rateMatchPatternToAddModList
Resources patterns which the UE should rate match PDSCH around. The UE rate matches around the union of all resources indicated in the rate match patterns. Rate match patterns defined here on cell level apply only to PDSCH of the same numerology (see TS 38.214 [19], clause 5.1.4.1). If a RateMatchPattern with the same RateMatchPatternId is configured in both ServingCellConfig/ServingCellConfigCommon and in SIB20/MCCH, the entire RateMatchPattern configuration, including the set of RBs/REs indicated by the patterns for the rate matching around, shall be the same and they are counted as a single rate match pattern in the total configured rate match patterns as defined in TS 38.214 [19]. | +| shortBitmap
Bitmap when maximum number of SS/PBCH blocks per half frame equals to 4 as defined in TS 38.213 [13], clause 4.1. | +| ss-PBCH-BlockPower | + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Average EPRE of the resources elements that carry secondary synchronization signals in dBm that the NW used for SSB transmission, see TS 38.213 [13], clause 7. | +| ssb-periodicityServingCell
The SSB periodicity in ms for the rate matching purpose. If the field is absent, the UE applies the value ms5. (see TS 38.213 [13], clause 4.1) | +| ssb-PositionQCL
Indicates the QCL relation between SSB positions for this serving cell as specified in TS 38.213 [13], clause 4.1. | +| ssb-PositionsInBurst
For operation in licensed spectrum, indicates the time domain positions of the transmitted SS-blocks in a half frame with SS/PBCH blocks as defined in TS 38.213 [13], clause 4.1. The first/leftmost bit corresponds to SS/PBCH block index 0, the second bit corresponds to SS/PBCH block index 1, and so on. Value 0 in the bitmap indicates that the corresponding SS/PBCH block is not transmitted while value 1 indicates that the corresponding SS/PBCH block is transmitted. The network configures the same pattern in this field as in the corresponding field in ServingCellConfigCommonSIB .
For operation with shared spectrum channel access, 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 (see TS 38.213 [13], clause 4.1). If the k-th bit of ssb-PositionsInBurst is set to 1, the UE assumes that one or more SS/PBCH blocks within the discovery burst transmission window with candidate SS/PBCH block indexes corresponding to SS/PBCH block index equal to k - 1 may be transmitted; if the kt-th bit is set to 0, the UE assumes that the corresponding SS/PBCH block(s) are not transmitted. The k-th bit is set to 0, where k > ssb-PositionQCL and the number of actually transmitted SS/PBCH blocks is not larger than the number of 1's in the bitmap. The network configures the same pattern in this field as in the corresponding field in ServingCellConfigCommonSIB . For operation with shared spectrum channel access in FR1, only mediumBitmap is used, and for FR2-2, longBitmap is used. | +| ssbSubcarrierSpacing
Subcarrier spacing of SSB.
Only the following values are applicable depending on the used frequency:
FR1: 15 or 30 kHz
FR2-1: 120 or 240 kHz
FR2-2: 120, 480, or 960 kHz | +| supplementaryUplinkConfig
The network configures this field only if uplinkConfigCommon is configured. If this field is absent, the UE shall release the supplementaryUplinkConfig and the supplementaryUplink configured in ServingCellConfig of this serving cell, if configured. | +| tdd-UL-DL-ConfigurationCommon
A cell-specific TDD UL/DL configuration, see TS 38.213 [13], clause 11.1. | + +| Conditional Presence | Explanation | +|-----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AbsFreqSSB | The field is absent when absoluteFrequencySSB in frequencyInfoDL is absent, otherwise the field is mandatory present. | +| HOAndServCellAdd | This field is mandatory present upon SpCell change (including path switch between a serving cell and a L2 U2N Relay UE) and upon serving cell (PSCell/SCell) addition. Otherwise, the field is absent. | +| HOAndServCellWithSSB | This field is mandatory present upon SpCell change and upon serving cell (SCell with SSB or PSCell) addition. Otherwise, the field is absent. | +| SharedSpectrum | This field is mandatory present if this cell operates with shared spectrum channel access in FR1. Otherwise, it is absent, Need R. | +| SharedSpectrum2 | This field is optionally present if this cell operates with shared spectrum channel access in FR2-2, Need R. Otherwise, it is absent, Need R. | +| TDD | The field is optionally present, Need R, for TDD cells; otherwise it is absent. | + +#### ServingCellConfigCommonSIB + +The IE *ServingCellConfigCommonSIB* is used to configure cell specific parameters of a UE's serving cell in SIB1. + +#### ServingCellConfigCommonSIB information element + +``` +-- ASN1START +-- TAG-SERVINGCELLCONFIGCOMMONSIB-START + +ServingCellConfigCommonSIB ::= SEQUENCE { + downlinkConfigCommon DownlinkConfigCommonSIB, + uplinkConfigCommon UplinkConfigCommonSIB OPTIONAL, -- Need R + supplementaryUplink UplinkConfigCommonSIB OPTIONAL, -- Need R + n-TimingAdvanceOffset ENUMERATED { n0, n25600, n39936 } OPTIONAL, -- Need S + ssb-PositionsInBurst SEQUENCE { + inOneGroup BIT STRING (SIZE (8)), + groupPresence BIT STRING (SIZE (8)) OPTIONAL -- Cond FR2-Only + }, + ssb-PeriodicityServingCell ENUMERATED {ms5, ms10, ms20, ms40, ms80, ms160}, + tdd-UL-DL-ConfigurationCommon TDD-UL-DL-ConfigCommon OPTIONAL, -- Cond TDD + ss-PBCH-BlockPower INTEGER (-60..50), + ... + [[ + channelAccessMode-r16 CHOICE { + dynamic NULL, + semiStatic SemiStaticChannelAccessConfig-r16 + } + discoveryBurstWindowLength-r16 ENUMERATED {ms0dot5, ms1, ms2, ms3, ms4, ms5} OPTIONAL, -- Cond SharedSpectrum + highSpeedConfig-r16 HighSpeedConfig-r16 OPTIONAL, -- Need R + ]], + [[ + channelAccessMode2-r17 ENUMERATED {enabled} OPTIONAL, -- Cond SharedSpectrum2 + discoveryBurstWindowLength-v1700 ENUMERATED {ms0dot125, ms0dot25, ms0dot5, ms0dot75, ms1, ms1dot25} OPTIONAL, -- Need R + highSpeedConfigFR2-r17 HighSpeedConfigFR2-r17 OPTIONAL, -- Need R + uplinkConfigCommon-v1700 UplinkConfigCommonSIB-v1700 OPTIONAL, -- Need R + ]], + [[ + enhancedMeasurementLEO-r17 ENUMERATED {true} OPTIONAL -- Need R + ]], + [[ + ra-ChannelAccess-r17 ENUMERATED {enabled} OPTIONAL -- Cond SharedSpectrum2 + ]], + [[ + downlinkConfigCommon-v1760 DownlinkConfigCommonSIB-v1760 OPTIONAL, -- Need R + uplinkConfigCommon-v1760 UplinkConfigCommonSIB-v1760 OPTIONAL, -- Need R + ]] +} + +-- TAG-SERVINGCELLCONFIGCOMMONSIB-STOP +-- ASN1STOP +``` + +| ServingCellConfigCommonSIB field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| channelAccessMode
If present, this field indicates which channel access procedures to apply for operation with shared spectrum channel access as defined in TS 37.213 [48]. If the field is configured as "semiStatic", the UE shall apply the channel access procedures for semi-static channel occupancy as described in clause 4.3 in TS 37.213. If the field is configured as "dynamic", the UE shall apply the channel access procedures as defined in TS 37.213, clause 4.1 and 4.2. | +| channelAccessMode2
If present, this field indicates that the UE shall apply channel access procedures for operation with shared spectrum channel access in accordance with TS 37.213 [48], clause 4.4 for FR2-2. If absent, the UE shall not apply any channel access procedure. The network always configures this field if channel access procedures are required for the serving cell within this region by regulations. | +| discoveryBurstWindowLength
Indicates the window length of the discovery burst in ms (see TS 37.213 [48]). The field discoveryBurstWindowLength-v1700 is applicable to SCS 480 kHz and SCS 960 kHz. | +| enhancedMeasurementLEO
If the field is present and UE supports the enhanced cell reselection requirements for NTN LEO in RRC_IDLE/RRC_INACTIVE, the UE shall apply the enhanced cell reselection requirements for NTN LEO as specified in TS 38.133 [14], clauses 4.2C.2.3 and 4.2C.2.4. | +| groupPresence
This field is present when maximum number of SS/PBCH blocks per half frame equals to 64 as defined in TS 38.213 [13], clause 4.1. The first/leftmost bit corresponds to the SS/PBCH index 0-7, the second bit corresponds to SS/PBCH block 8-15, and so on. Value 0 in the bitmap indicates that the SSBs according to inOneGroup are absent. Value 1 indicates that the SS/PBCH blocks are transmitted in accordance with inOneGroup . | +| inOneGroup
When maximum number of SS/PBCH blocks per half frame equals to 4 as defined in TS 38.213 [13], clause 4.1, only the 4 leftmost bits are valid; the UE ignores the 4 rightmost bits. When maximum number of SS/PBCH blocks per half frame equals to 8 as defined in TS 38.213 [13], clause 4.1, all 8 bits are valid. The first/leftmost bit corresponds to SS/PBCH block index 0, the second bit corresponds to SS/PBCH block index 1, and so on. When maximum number of SS/PBCH blocks per half frame equals to 64 as defined in TS 38.213 [13], clause 4.1, all 8 bits are valid; The first/leftmost bit corresponds to the first SS/PBCH block index in the group (i.e., to SSB index 0, 8, and so on); the second bit corresponds to the second SS/PBCH block index in the group (i.e., to SSB index 1, 9, and so on), 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. | +| n-TimingAdvanceOffset
The N_TA-Offset to be applied for random access on this serving cell. If the field is absent, the UE applies the value defined for the duplex mode and frequency range of this serving cell. See TS 38.133 [14], table 7.1.2-2. | +| ra-ChannelAccess
If present, this field indicates that the UE shall apply channel access procedures before msg1/msgA transmission for operation with shared spectrum channel access in accordance with TS 37.213 [48], clause 4.4.5 for FR2-2. | +| ssb-PositionsInBurst
Time domain positions of the transmitted SS-blocks in an SS-burst as defined in TS 38.213 [13], clause 4.1.
For operation with shared spectrum channel access in FR1, only inOneGroup is used and the UE interprets this field same as mediumBitmap in ServingCellConfigCommon . The UE assumes that a bit in inOneGroup at position $k >$ is 0, where $k$ is obtained from MIB as specified in TS 38.213 [13], clause 4.1. For operation with shared spectrum channel access in FR2-2, the m-th bit in groupPresence is set to 0 for $m > /8$ , where $m$ is obtained from MIB as specified in TS 38.213 [13], clause 4.1. | +| ss-PBCH-BlockPower
Average EPRE of the resources elements that carry secondary synchronization signals in dBm that the NW used for SSB transmission, see TS 38.213 [13], clause 7. | + +| Conditional Presence | Explanation | +|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| FR2-Only | This field is mandatory present for an FR2 carrier frequency. It is absent otherwise and UE releases any configured value. | +| SharedSpectrum | This field is mandatory present if this cell operates with shared spectrum channel access in FR1. Otherwise, it is absent, Need R. | +| SharedSpectrum2 | This field is optionally present if this cell operates with shared spectrum channel access in FR2-2, Need R. Otherwise, it is absent, Need R. | +| TDD | The field is optionally present, Need R, for TDD cells; otherwise it is absent. | + +### ShortI-RNTI-Value + +The IE *ShortI-RNTI-Value* is used to identify the suspended UE context of a UE in RRC\_INACTIVE using fewer bits compared to I-RNTI-Value. + +#### ShortI-RNTI-Value information element + +``` +-- ASN1START +-- TAG-SHORTI-RNTI-VALUE-START + +ShortI-RNTI-Value ::= BIT STRING (SIZE(24)) + +-- TAG-SHORTI-RNTI-VALUE-STOP +-- ASN1STOP +``` + +#### ShortMAC-I + +The IE *ShortMAC-I* is used to identify and verify the UE at RRC connection re-establishment. The 16 least significant bits of the MAC-I calculated using the AS security configuration of the source PCell, as specified in 5.3.7.4. + +#### ShortMAC-I information element + +``` +-- ASN1START +-- TAG-SHORTMAC-I-START + +ShortMAC-I ::= BIT STRING (SIZE (16)) + +-- TAG-SHORTMAC-I-STOP +-- ASN1STOP +``` + +### SINR-Range + +The IE *SINR-Range* specifies the value range used in SINR measurements and thresholds. For measurements, integer value for SINR measurements is according to Table 10.1.16.1-1 in TS 38.133 [14]. For thresholds, the actual value is (IE value – 46) / 2 dB. + +#### ***SINR-Range* information element** + +``` + +-- ASN1START +-- TAG-SINR-RANGE-START + +SINR-Range ::= INTEGER(0..127) + +-- TAG-SINR-RANGE-STOP +-- ASN1STOP + +``` + +### — ***SI-RequestConfig*** + +The IE *SI-RequestConfig* contains configuration for Msg1 based SI request without Msg1 repetition. + +#### ***SI-RequestConfig* information element** + +``` + +-- ASN1START +-- TAG-SI-REQUESTCONFIG-START + +SI-RequestConfig ::= SEQUENCE { + rach-OccasionsSI SEQUENCE { + rach-ConfigSI RACH-ConfigGeneric, + ssb-perRACH-Occasion ENUMERATED {oneEighth, oneFourth, oneHalf, one, two, four, eight, sixteen} + } OPTIONAL, -- Need R + si-RequestPeriod ENUMERATED {one, two, four, six, eight, ten, twelve, sixteen} OPTIONAL, -- Need R + si-RequestResources SEQUENCE (SIZE (1..maxSI-Message)) OF SI-RequestResources +} + +SI-RequestResources ::= SEQUENCE { + ra-PreambleStartIndex INTEGER (0..63), + ra-AssociationPeriodIndex INTEGER (0..15) OPTIONAL, -- Need R + ra-ssb-OccasionMaskIndex INTEGER (0..15) OPTIONAL, -- Need R +} + +-- TAG-SI-REQUESTCONFIG-STOP +-- ASN1STOP + +``` + +| SI-RequestConfig field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| rach-OccasionsSI
Configuration of dedicated RACH Occasions for SI. If the field is absent, the UE uses the corresponding parameters configured in rach-ConfigCommon of the initial uplink BWP. | +| si-RequestPeriod
Periodicity of the SI-Request configuration in number of association periods. | +| si-RequestResources
If there is only one entry in the list, the configuration is used for all SI messages for which si-BroadcastStatus or posSI-BroadcastStatus is set to notBroadcasting . Otherwise:
  • - If si-SchedulingInfo-v1700 is not present and the SI-RequestConfig is used for on-demand SI request in SI-SchedulingInfo or PosSI-SchedulingInfo, the 1st entry in the list corresponds to the first SI message in schedulingInfoList or posSchedulingInfoList for which si-BroadcastStatus or posSI-BroadcastStatus is set to notBroadcasting, 2nd entry in the list corresponds to the second SI message in schedulingInfoList or posSchedulingInfoList for which si-BroadcastStatus or posSI-BroadcastStatus is set to notBroadcasting and so on.
  • - If si-SchedulingInfo-v1700 is present and SI-RequestConfig is configured in SI-SchedulingInfo for on-demand SI request, the UE generates a list of concatenated SI messages by appending the SI messages containing type1 SIB configured by schedulingInfoList2 in si-SchedulingInfo-v1700 to the SI messages configured by schedulingInfoList in si-SchedulingInfo. The 1st entry in the list corresponds to the first SI message for which si-BroadcastStatus is set to notBroadcasting, 2nd entry in the list corresponds to the second SI message for which si-BroadcastStatus is set to notBroadcasting and so on.
  • - If si-SchedulingInfo-v1700 is present and SI-RequestConfig is configured in PosSI-SchedulingInfo for on-demand SI request, the UE generates a list of concatenated SI messages by appending the SI messages containing type2 SIB configured by schedulingInfoList2 in si-SchedulingInfo-v1700 to the SI messages configured by posSchedulingInfoList in posSI-SchedulingInfo. The 1st entry in the list corresponds to the first SI message for which posSI-BroadcastStatus or si-BroadcastStatus is set to notBroadcasting, 2nd entry in the list corresponds to the second SI message for which posSI-BroadcastStatus or si-BroadcastStatus is set to notBroadcasting and so on.
Change of si-RequestResources should not result in system information change notification. | + +| SI-RequestResources field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ra-AssociationPeriodIndex
Index of the association period in the si-RequestPeriod in which the UE can send the SI request for SI message(s) corresponding to this SI-RequestResources , using the preambles indicated by ra-PreambleStartIndex and rach occasions indicated by ra-ssb-OccasionMaskIndex . | +| ra-PreambleStartIndex
If N SSBs are associated with a RACH occasion, where N >= 1, for the i-th SSB (i=0, ..., N-1) the preamble with preamble index = ra-PreambleStartIndex + i is used for SI request; For N < 1, the preamble with preamble index = ra-PreambleStartIndex is used for SI request. | + +### – SI-RequestConfigRepetition + +The IE *SI-RequestConfigRepetition* contains configuration for Msg1 based SI request with Msg1 repetition. + +#### SI-RequestConfigRepetition information element + +``` +-- ASN1START +-- TAG-SI-REQUESTCONFIGREPETITION-START + +SI-RequestConfigRepetition-r18 ::= SEQUENCE { + rach-OccasionsSI-r18 SEQUENCE { + rach-ConfigSI-r18 RACH-ConfigGeneric, + ssb-perRACH-Occasion-r18 ENUMERATED {oneEighth, oneFourth, oneHalf, one, two, four, eight, sixteen} + } +} +``` + +``` + + } + si-RequestResourcesRepetitionNum2-r18 SEQUENCE (SIZE (1..maxSI-Message)) OF SI-RequestResourcesRepetition-r18 OPTIONAL, -- Need R + si-RequestResourcesRepetitionNum4-r18 SEQUENCE (SIZE (1..maxSI-Message)) OF SI-RequestResourcesRepetition-r18 OPTIONAL, -- Need R + si-RequestResourcesRepetitionNum8-r18 SEQUENCE (SIZE (1..maxSI-Message)) OF SI-RequestResourcesRepetition-r18 OPTIONAL, -- Need R + ... +} + +SI-RequestResourcesRepetition-r18 ::= SEQUENCE { + ra-PreambleStartIndex-r18 INTEGER (0..63), + ra-ssb-OccasionMaskIndex-r18 INTEGER (0..15) +} +OPTIONAL -- Need R + +-- TAG-SI-REQUESTCONFIGREPETITION-STOP +-- ASN1STOP + +``` + +#### SI-RequestConfigRepetition field descriptions + +##### **si-RequestResourcesRepetitionNum2, si-RequestResourcesRepetitionNum4, si-RequestResourcesRepetitionNum8** + +Indicates the configurations for Msg1-based SI request with Msg1 repetition for repetition number 2, 4 and 8, respectively. + +If there is only one entry in the list, the configuration is used for all SI messages for which *si-BroadcastStatus* or *posSI-BroadcastStatus* is set to *notBroadcasting*. Otherwise: + +- If *si-SchedulingInfo-v1700* is not present and the *SI-RequestConfigRepetitionNum2/ SI-RequestConfigRepetitionNum4/ SI-RequestConfigRepetitionNum8* is used for on-demand SI request in *SI-SchedulingInfo* or *PosSI-SchedulingInfo*, the 1st entry in the list corresponds to the first SI message in *schedulingInfoList* or *posSchedulingInfoList* for which *si-BroadcastStatus* or *posSI-BroadcastStatus* is set to *notBroadcasting*, 2nd entry in the list corresponds to the second SI message in *schedulingInfoList* or *posSchedulingInfoList* for which *si-BroadcastStatus* or *posSI-BroadcastStatus* is set to *notBroadcasting* and so on. +- If *si-SchedulingInfo-v1700* is present and *SI-RequestConfigRepetitionNum2/ SI-RequestConfigRepetitionNum4/ SI-RequestConfigRepetitionNum8* is configured in *SI-SchedulingInfo* for on-demand SI request, the UE generates a list of concatenated SI messages by appending the SI messages containing type1 SIB configured by *schedulingInfoList2* in *si-SchedulingInfo-v1700* to the SI messages configured by *schedulingInfoList* in *si-SchedulingInfo*. The 1st entry in the list corresponds to the first SI message for which *si-BroadcastStatus* is set to *notBroadcasting*, 2nd entry in the list corresponds to the second SI message for which *si-BroadcastStatus* is set to *notBroadcasting* and so on. +- If *si-SchedulingInfo-v1700* is present and *SI-RequestConfigRepetitionNum2/ SI-RequestConfigRepetitionNum4/ SI-RequestConfigRepetitionNum8* is configured in *PosSI-SchedulingInfo* for on-demand SI request, the UE generates a list of concatenated SI messages by appending the SI messages containing type2 SIB configured by *schedulingInfoList2* in *si-SchedulingInfo-v1700* to the SI messages configured by *posSchedulingInfoList* in *posSI-SchedulingInfo*. The 1st entry in the list corresponds to the first SI message for which *posSI-BroadcastStatus* or *si-BroadcastStatus* is set to *notBroadcasting*, 2nd entry in the list corresponds to the second SI message for which *posSI-BroadcastStatus* or *si-BroadcastStatus* is set to *notBroadcasting* and so on. + +Change of *si-RequestResourcesRepetitionNum2/ SI-RequestConfigRepetitionNum4/ SI-RequestConfigRepetitionNum8* should not result in system information change notification. + +### SI-SchedulingInfo + +The IE *SI-SchedulingInfo* contains information needed for acquisition of SI messages. + +#### **SI-SchedulingInfo information element** + +``` + +-- ASN1START +-- TAG-SI-SCHEDULINGINFO-START + +SI-SchedulingInfo ::= + SEQUENCE { + schedulingInfoList SEQUENCE (SIZE (1..maxSI-Message)) OF SchedulingInfo, + si-WindowLength ENUMERATED {s5, s10, s20, s40, s80, s160, s320, s640, s1280, s2560-v1710, s5120-v1710 }, + si-RequestConfig SI-RequestConfig OPTIONAL, -- Cond MSG-1 + si-RequestConfigSUL SI-RequestConfig OPTIONAL, -- Cond SUL-MSG-1 + systemInformationAreaID BIT STRING (SIZE (24)) OPTIONAL, -- Need R + ... + } + +SchedulingInfo ::= + SEQUENCE { + si-BroadcastStatus ENUMERATED {broadcasting, notBroadcasting}, + si-Periodicity ENUMERATED {rf8, rf16, rf32, rf64, rf128, rf256, rf512}, + sib-MappingInfo SIB-Mapping + } + +SI-SchedulingInfo-v1700 ::= + SEQUENCE { + schedulingInfoList2-r17 SEQUENCE (SIZE (1..maxSI-Message)) OF SchedulingInfo2-r17, + dummy SI-RequestConfig OPTIONAL + } + +SI-SchedulingInfo-v1740 ::= + SEQUENCE { + si-RequestConfigRedCap-r17 SI-RequestConfig OPTIONAL -- Cond REDCAP-MSG-1 + } + +SI-SchedulingInfo-v1800 ::= + SEQUENCE { + si-RequestConfigMSG1-Repetition-r18 SI-RequestConfigRepetition-r18 OPTIONAL, -- Cond MSG-1 + si-RequestConfigRedCap-MSG1-Repetition-r18 SI-RequestConfigRepetition-r18 OPTIONAL, -- Cond SUL-MSG-1 + si-RequestConfigSUL-MSG1-Repetition-r18 SI-RequestConfigRepetition-r18 OPTIONAL -- Cond REDCAP-MSG-1 + } + +SchedulingInfo2-r17 ::= + SEQUENCE { + si-BroadcastStatus-r17 ENUMERATED {broadcasting, notBroadcasting}, + si-WindowPosition-r17 INTEGER (1..256), + si-Periodicity-r17 ENUMERATED {rf8, rf16, rf32, rf64, rf128, rf256, rf512}, + sib-MappingInfo-r17 SIB-Mapping-v1700 + } + +SIB-Mapping ::= + SEQUENCE (SIZE (1..maxSIB)) OF SIB-TypeInfo + +SIB-Mapping-v1700 ::= + SEQUENCE (SIZE (1..maxSIB)) OF SIB-TypeInfo-v1700 + +SIB-TypeInfo ::= + SEQUENCE { + type ENUMERATED {sibType2, sibType3, sibType4, sibType5, sibType6, sibType7, sibType8, sibType9, + sibType10-v1610, sibType11-v1610, sibType12-v1610, sibType13-v1610, + sibType14-v1610, spare3, spare2, spare1, ... }, + valueTag INTEGER (0..31) OPTIONAL, -- Cond SIB-TYPE + } + +``` + +``` + + areaScope ENUMERATED {true} OPTIONAL -- Need S +} + +SIB-TypeInfo-v1700 ::= + sibType-r17 SEQUENCE { + type1-r17 CHOICE { + type2-r17 ENUMERATED {sibType15, sibType16, sibType17, sibType18, sibType19, sibType20, sibType21, + posSibType-r17 sibType22-v1800, sibType23-v1800 ,sibType24-v1800, sibType25-v1800, + encrypted-r17 spare5, spare4, spare3, spare2, spare1,...}, + gnss-id-r17 SEQUENCE { + sbas-id-r17 ENUMERATED {posSibType1-9, posSibType1-10, posSibType2-24, posSibType2-25, + }, posSibType6-4, posSibType6-5, posSibType6-6, posSibType2-17a-v1770, + valueTag-r17 posSibType2-18a-v1770, posSibType2-20a-v1770, posSibType1-11-v1800, + areaScope-r17 posSibType1-12-v1800, posSibType2-26-v1800, posSibType2-27-v1800, + }, spare2, spare1,...}, + INTEGER (0..31) ENUMERATED { true } OPTIONAL, -- Need R + ENUMERATED {true} GNSS-ID-r16 OPTIONAL, -- Need R + SBAS-ID-r16 OPTIONAL, -- Cond GNSS-ID-SBAS +} + +-- TAG-SI-SCHEDULINGINFO-STOP +-- ASN1STOP + +``` + +#### SchedulingInfo field descriptions + +| | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| areaScope | Indicates that a SIB is area specific. If the field is absent, the SIB is cell specific. | +| si-BroadcastStatus | Indicates if the SI message is being broadcasted or not. Change of si-BroadcastStatus should not result in system information change notifications in Short Message transmitted with P-RNTI over DCI (see clause 6.5). The value of the indication is valid until the end of the BCCH modification period when set to broadcasting . When SIB19 is scheduled in an NTN cell, the si-BroadcastStatus for the mapped SIB19 is set to broadcasting .
If si-SchedulingInfo-v1700 is present, the network ensures that the total number of SI messages with si-BroadcastStatus set to notBroadcasting in the list of concatenated SI messages configured by schedulingInfoList in si-SchedulingInfo and SI messages containing type1 SIB configured by schedulingInfoList2 in si-SchedulingInfo-v1700 does not exceed the limit of maxSI-Message when si-RequestConfig , si-RequestConfigRedCap or si-RequestConfigSUL is configured. | +| si-Periodicity | Periodicity of the SI-message in radio frames. Value rf8 corresponds to 8 radio frames, value rf16 corresponds to 16 radio frames, and so on. | + +| SI-SchedulingInfo field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| dummy
This field is not used in this specification. If received, it is ignored by the UE. | +| si-RequestConfig
Configuration of Msg1 resources that the UE uses for requesting SI-messages for which si-BroadcastStatus is set to notBroadcasting . | +| si-RequestConfigMSG1-Repetition
Configuration of Msg1 repetition resources on NUL that the UE uses for requesting SI-messages for which si-BroadcastStatus is set to notBroadcasting . This field is only applicable when Msg1 repetition resources can be used for requesting SI-messages. | +| si-RequestConfigRedCap
Configuration of Msg1 resources for initialUplinkBWP-RedCap that the (e)RedCap UE uses for requesting SI-messages for which si-BroadcastStatus is set to notBroadcasting . | +| si-RequestConfigRedCap-MSG1-Repetition
Configuration of Msg1 repetition resources for initialUplinkBWP-RedCap that the RedCap UE uses for requesting SI-messages for which si-BroadcastStatus is set to notBroadcasting . This field is only applicable when Msg1 repetition resources can be used for requesting SI-messages. | +| si-RequestConfigSUL
Configuration of Msg1 resources that the UE uses for requesting SI-messages for which si-BroadcastStatus is set to notBroadcasting . | +| si-RequestConfigSUL-MSG1-Repetition
Configuration of Msg1 repetition resources on SUL that the UE uses for requesting SI-messages for which si-BroadcastStatus is set to notBroadcasting . This field is only applicable when Msg1 repetition resources can be used for requesting SI-messages. | +| si-WindowLength
The length of the SI scheduling window. Value s5 corresponds to 5 slots, value s10 corresponds to 10 slots and so on. The network always configures si-WindowLength to be shorter than or equal to the si-Periodicity . The values s2560-v1710 and s5120-v1710 are only applicable for SCS 480 kHz. | +| systemInformationAreaID
Indicates the system information area that the cell belongs to, if any. Any SIB with areaScope within the SI is considered to belong to this systemInformationAreaID . The systemInformationAreaID is unique within a PLMN/SNPN. | + +| SchedulingInfo2 field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| encrypted
The presence of this field indicates that the pos-sib-type is encrypted as specified in TS 37.355 [49]. | +| gnss-id
The presence of this field indicates that the positioning SIB type is for a specific GNSS. Indicates a specific GNSS (see also TS 37.355 [49]). | +| posSibType
The posSIBs as defined in TS 37.355 [49] mapped to SI for scheduling using schedulingInfoList2 . | +| sbas-id
The presence of this field indicates that the positioning SIB type is for a specific SBAS. Indicates a specific SBAS (see also TS 37.355 [49]). | +| si-WindowPosition
This field indicates the SI window position of the associated SI-message. The network provides si-WindowPosition in an ascending order, i.e. si-WindowPosition in the subsequent entry in schedulingInfoList2 has always value higher than in the previous entry of schedulingInfoList2 . The network configures this field in a way that ensures that SI messages scheduled by schedulingInfoList and/or posSchedulingInfoList do not overlap with SI messages scheduled by schedulingInfoList2 . | +| sib-MappingInfo
Indicates which SIBs or posSIBs are contained in the SI message. | +| sibType
The type of SIB(s) mapped to SI for scheduling using schedulingInfoList2 . Value type1 indicates SIBs and value type2 indicates posSIBs. | + +| Conditional presence | Explanation | +|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GNSS-ID-SBAS | The field is mandatory present if gnss-id is set to sbas . It is absent otherwise. | +| MSG-1 | The field is optionally present, Need R, if si-BroadcastStatus is set to notBroadcasting for any SI-message included in schedulingInfoList or any SI-message containing type1 SIB included in schedulingInfoList2 . It is absent otherwise. | +| SIB-TYPE | The field is mandatory present if the SIB type is different from SIB6 , SIB7 or SIB8 . For SIB6 , SIB7 and SIB8 it is absent. | +| NonPosSIB | The field is mandatory present if the SIB type is type1 . For type2 it is absent. | +| SUL-MSG-1 | The field is optionally present, Need R, if supplementaryUplink is configured in ServingCellConfigCommonSIB and if si-BroadcastStatus is set to notBroadcasting for any SI-message included in schedulingInfoList or any SI-message containing type1 SIB included in schedulingInfoList2 . It is absent otherwise. | +| REDCAP-MSG-1 | The field is optionally present, Need R, if initialUplinkBWP-RedCap is configured in UplinkConfigCommonSIB and if si-BroadcastStatus is set to notBroadcasting for any SI-message included in schedulingInfoList or any SI-message containing type1 SIB included in schedulingInfoList2 . It is absent otherwise. | + +### – SK-Counter + +The IE *SK-Counter* is a counter used upon initial configuration of SN security for NR-DC and NE-DC, as well as upon refresh of $S-K_{\text{gNB}}$ or $S-K_{\text{eNB}}$ based on the current or newly derived $K_{\text{gNB}}$ during RRC Resume or RRC Reconfiguration, as defined in TS 33.501 [11]. + +``` +-- ASN1START +-- TAG-SK COUNTER-START + +SK-Counter ::= INTEGER (0..65535) + +-- TAG-SK COUNTER-STOP +-- ASN1STOP +``` + +### – SlotFormatCombinationsPerCell + +The IE *SlotFormatCombinationsPerCell* is used to configure the SlotFormatCombinations applicable for one serving cell (see TS 38.213 [13], clause 11.1.1). + +#### SlotFormatCombinationsPerCell information element + +``` +-- ASN1START +-- TAG-SLOT FORMAT COMBINATIONS PER CELL-START + +SlotFormatCombinationsPerCell ::= SEQUENCE { + servingCellId ServCellIndex, + subcarrierSpacing SubcarrierSpacing, + subcarrierSpacing2 SubcarrierSpacing OPTIONAL, -- Need R + slotFormatCombinations SEQUENCE (SIZE (1..maxNrofSlotFormatCombinationsPerSet)) OF SlotFormatCombination + OPTIONAL, -- Need M + positionInDCI INTEGER (0..maxSFI-DCI-PayloadSize-1) OPTIONAL, -- Need M +} +``` + +``` + + ... + [[ + enableConfiguredUL-r16 ENUMERATED {enabled} OPTIONAL -- Need R + ]] + } + + SlotFormatCombination ::= SEQUENCE { + slotFormatCombinationId SlotFormatCombinationId, + slotFormats SEQUENCE (SIZE (1..maxNrofSlotFormatsPerCombination)) OF INTEGER (0..255) + } + + SlotFormatCombinationId ::= INTEGER (0..maxNrofSlotFormatCombinationsPerSet-1) + + -- TAG-SLOTFORMATCOMBINATIONS PER CELL-STOP + -- ASN1STOP + +``` + +#### SlotFormatCombination field descriptions + +| | | +|--------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| slotFormatCombinationId | This ID is used in the DCI payload to dynamically select this SlotFormatCombination (see TS 38.213 [13], clause 11.1.1). | +| slotFormats | Slot formats that occur in consecutive slots in time domain order as listed here (see TS 38.213 [13], clause 11.1.1 and TS 38.213 [13], clause 14 for IAB-MT). | + +#### SlotFormatCombinationsPerCell field descriptions + +| | | +|-------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| enableConfiguredUL | If configured, the UE is allowed to transmit uplink signals/channels (SRS, PUCCH, CG-PUSCH) in the set of symbols of the slot when the UE does not detect a DCI format 2_0 providing a slot format for the set of symbols (see TS 38.213 [13], 11.1.1). This field is applicable only if cgr-RetransmissionTimer-r16 is configured. | +| positionInDCI | The (starting) position (bit) of the slotFormatCombinationId (SFI-Index) for this serving cell (servingCellId) within the DCI payload (see TS 38.213 [13], clause 11.1.1). | +| servingCellId | The ID of the serving cell for which the slotFormatCombinations are applicable. | +| slotFormatCombinations | A list with SlotFormatCombinations . Each SlotFormatCombination comprises of one or more SlotFormats (see TS 38.211 [16], clause 4.3.2). The total number of slotFormats in the slotFormatCombinations list does not exceed 512. | +| subcarrierSpacing2 | Reference subcarrier spacing for a Slot Format Combination on an FDD or SUL cell (see TS 38.213 [13], clause 11.1.1). For FDD, subcarrierSpacing (SFI-scs) is the reference SCS for DL BWP and subcarrierSpacing2 (SFI-scs2) is the reference SCS for UL BWP. For SUL, subcarrierSpacing (SFI-scs) is the reference SCS for non-SUL carrier and subcarrierSpacing2 (SFI-scs2) is the reference SCS for SUL carrier. The network configures a value that is smaller than or equal to any SCS of configured BWPs of the serving cell that the command applies to. And the network configures a value that is smaller than or equal to the SCS of the serving cell which the UE monitors for SFI indications. | +| subcarrierSpacing | Reference subcarrier spacing for this Slot Format Combination. The network configures a value that is smaller than or equal to any SCS of configured BWPs of the serving cell that the command applies to. And the network configures a value that is smaller than or equal to the SCS of the serving cell which the UE monitors for SFI indications (see TS 38.213 [13], clause 11.1.1). | + +#### SlotFormatIndicator + +The IE *SlotFormatIndicator* is used to configure monitoring a Group-Common-PDCCH for Slot-Format-Indicators (SFI). + +#### SlotFormatIndicator information element + +``` + +-- ASN1START +-- TAG-SLOTFORMATINDICATOR-START + +SlotFormatIndicator ::= SEQUENCE { + sfi-RNTI RNTI-Value, + dci-PayloadSize INTEGER (1..maxSFI-DCI-PayloadSize), + slotFormatCombToAddModList SEQUENCE (SIZE(1..maxNrofAggregatedCellsPerCellGroup)) OF SlotFormatCombinationsPerCell + slotFormatCombToReleaseList SEQUENCE (SIZE(1..maxNrofAggregatedCellsPerCellGroup)) OF ServCellIndex + ... + [[ + availableRB-SetsToAddModList-r16 SEQUENCE (SIZE(1..maxNrofAggregatedCellsPerCellGroup)) OF AvailableRB-SetsPerCell-r16 OPTIONAL, -- Need N + availableRB-SetsToReleaseList-r16 SEQUENCE (SIZE(1..maxNrofAggregatedCellsPerCellGroup)) OF ServCellIndex OPTIONAL, -- Need N + switchTriggerToAddModList-r16 SEQUENCE (SIZE(1..4)) OF SearchSpaceSwitchTrigger-r16 OPTIONAL, -- Need N + switchTriggerToReleaseList-r16 SEQUENCE (SIZE(1..4)) OF ServCellIndex OPTIONAL, -- Need N + co-DurationsPerCellToAddModList-r16 SEQUENCE (SIZE(1..maxNrofAggregatedCellsPerCellGroup)) OF CO-DurationsPerCell-r16 OPTIONAL, -- Need N + co-DurationsPerCellToReleaseList-r16 SEQUENCE (SIZE(1..maxNrofAggregatedCellsPerCellGroup)) OF ServCellIndex OPTIONAL -- Need N + ]], + [[ + switchTriggerToAddModListSizeExt-r16 SEQUENCE (SIZE(1..maxNrofAggregatedCellsPerCellGroupMinus4-r16)) OF + SearchSpaceSwitchTrigger-r16 OPTIONAL, -- Need N + switchTriggerToReleaseListSizeExt-r16 SEQUENCE (SIZE(1..maxNrofAggregatedCellsPerCellGroupMinus4-r16)) OF + ServCellIndex OPTIONAL -- Need N + ]], + [[ + co-DurationsPerCellToAddModList-r17 SEQUENCE (SIZE(1..maxNrofAggregatedCellsPerCellGroup)) OF CO-DurationsPerCell-r17 OPTIONAL -- Need N + ]] +} + +CO-DurationsPerCell-r16 ::= SEQUENCE { + servingCellId-r16 ServCellIndex, + positionInDCI-r16 INTEGER(0..maxSFI-DCI-PayloadSize-1), + subcarrierSpacing-r16 SubcarrierSpacing, + co-DurationList-r16 SEQUENCE (SIZE(1..64)) OF CO-Duration-r16 +} + +CO-DurationsPerCell-r17 ::= SEQUENCE { + servingCellId-r17 ServCellIndex, + positionInDCI-r17 INTEGER(0..maxSFI-DCI-PayloadSize-1), + subcarrierSpacing-r17 SubcarrierSpacing, + co-DurationList-r17 SEQUENCE (SIZE(1..64)) OF CO-Duration-r17 +} + +CO-Duration-r16 ::= INTEGER (0..1120) + +``` + +``` + +CO-Duration-r17 ::= INTEGER (0..4480) + +AvailableRB-SetsPerCell-r16 ::= SEQUENCE { + servingCellId-r16 ServCellIndex, + positionInDCI-r16 INTEGER (0..maxSFI-DCI-PayloadSize-1) +} + +SearchSpaceSwitchTrigger-r16 ::= SEQUENCE { + servingCellId-r16 ServCellIndex, + positionInDCI-r16 INTEGER (0..maxSFI-DCI-PayloadSize-1) +} + +-- TAG-SLOTFORMATINDICATOR-STOP +-- ASN1STOP + +``` + +| SlotFormatIndicator field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| availableRB-SetsToAddModList
A list of AvailableRB-SetsPerCell objects (see TS 38.213 [13], clause 11.1.1). | +| co-DurationsPerCellToAddModList
A list of CO-DurationsPerCell objects. If not configured, the UE uses the slot format indicator (SFI), if available, to determine the channel occupancy duration (see TS 38.213 [13], clause 11.1.1). | +| co-DurationsPerCellToReleaseList
A list of CO-DurationsPerCell objects to be released. An entry created using co-DurationsPerCellToAddModList-r16 or co-DurationsPerCellToAddModList-r17 can be deleted using co-DurationsPerCellToReleaseList . | +| dci-PayloadSize
Total length of the DCI payload scrambled with SFI-RNTI (see TS 38.213 [13], clause 11.1.1). | +| sfi-RNTI
RNTI used for SFI on the given cell (see TS 38.213 [13], clause 11.1.1). | +| slotFormatCombToAddModList
A list of SlotFormatCombinations for the UE's serving cells (see TS 38.213 [13], clause 11.1.1). | +| switchTriggerToAddModList, switchTriggerToAddModListSizeExt
A list of SearchSpaceSwitchTrigger objects. Each SearchSpaceSwitchTrigger object provides position in DCI of the bit field indicating search space switching flag for a serving cell or, if cellGroupsForSwitchList is configured, group of serving cells (see TS 38.213 [13], clause 10.4). If cellGroupsForSwitchList is configured, only one of the cells belonging to the same cell group is added/modified, and the configuration applies to all cells belonging to the cellGroupsForSwitchList (see TS 38.213 [13], clause 10.4). The network configures more than 4 SearchSpaceSwitchTrigger objects only if cellGroupsForSwitchList is not configured. The UE shall consider entries in switchTriggerToAddModList and in switchTriggerToAddModListSizeExt as a single list, i.e. an entry created using switchTriggerToAddModList can be modified using switchTriggerToAddModListSizeExt and vice-versa. | +| switchTriggerToReleaseModList, switchTriggerToReleaseListSizeExt
A list of SearchSpaceSwitchTriggers to be released. If cellGroupsForSwitchList is configured, the SearchSpaceSwitchTrigger is released for all serving cells belonging to the same CellGroupForSwitch . The UE shall consider entries in switchTriggerToReleaseList and in switchTriggerToReleaseListSizeExt as a single list, i.e. an entry created using switchTriggerToAddModList or switchTriggerToAddModListSizeExt can be deleted using switchTriggerToReleaseList or switchTriggerToReleaseListSizeExt . | + +| AvailableRB-SetsPerCell field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| positionInDCI
The (starting) position of the bits within DCI payload indicating the availability of the RB sets of a serving cell (see TS 38.213 [13], clause 11.1.1). | +| servingCellId
The ID of the serving cell for which the configuration is applicable. | + +| CO-DurationsPerCell field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| co-DurationList
A list of Channel Occupancy duration in symbols.
The maximum duration that can be configured for the following SCS:
  • - 15 kHz: 280.
  • - 30 kHz: 560.
  • - 60 kHz: 1120.
  • - 120 kHz: 560.
  • - 480 kHz: 2240.
  • - 960 kHz: 4480.
| +| positionInDCI
Position in DCI of the bit field indicating Channel Occupancy duration for UE's serving cells (see TS 38.213 [13], clause 11.1.1). | +| servingCellId
The ID of the serving cell for which the configuration is applicable. | +| subcarrierSpacing
Reference subcarrier spacing for the list of Channel Occupancy durations (see TS 38.213 [13], clause 11.1.1).
Only the following values are applicable depending on the used frequency range:
FR1: 15, 30, or 60 kHz
FR2-2: 120, 480, or 960 kHz | + +| SearchSpaceSwitchTrigger field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| positionInDCI
The position of the bit within DCI payload containing a search space switching flag (see TS 38.213 [13], clause 11.1.1). | +| servingCellId
The ID of the serving cell for which the configuration is applicable or the group of serving cells as indicated by CellGroupsForSwitch-r16 containing this servingCellId . | + +### — S-NSSAI + +The IE *S-NSSAI* (*Single Network Slice Selection Assistance Information*) identifies a Network Slice end to end and comprises a slice/service type and a slice differentiator, see TS 23.003 [21]. + +#### **S-NSSAI information element** + +``` +-- ASN1START +-- TAG-S-NSSAI-START +``` + +``` + +S-NSSAI ::= CHOICE{ + sst BIT STRING (SIZE (8)), + sst-SD BIT STRING (SIZE (32)) +} + +-- TAG-S-NSSAI-STOP +-- ASN1STOP + +``` + +| S-NSSAI field descriptions | +|-----------------------------------------------------------------------------------------------------------------------| +| sst
Indicates the S-NSSAI consisting of Slice/Service Type, see TS 23.003 [21]. | +| sst-SD
Indicates the S-NSSAI consisting of Slice/Service Type and Slice Differentiator, see TS 23.003 [21]. | + +### — *SpeedStateScaleFactors* + +The IE *SpeedStateScaleFactors* concerns factors, to be applied when the UE is in medium or high speed state, used for scaling a mobility control related parameter. + +#### ***SpeedStateScaleFactors* information element** + +``` + +-- ASN1START +-- TAG-SPEEDSTATESCALEFACTORS-START + +SpeedStateScaleFactors ::= SEQUENCE { + sf-Medium ENUMERATED {oDot25, oDot5, oDot75, lDot0}, + sf-High ENUMERATED {oDot25, oDot5, oDot75, lDot0} +} + +-- TAG-SPEEDSTATESCALEFACTORS-STOP +-- ASN1STOP + +``` + +| SpeedStateScaleFactors field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sf-High
The concerned mobility control related parameter is multiplied with this factor if the UE is in High Mobility state as defined in TS 38.304 [20]. Value oDot25 corresponds to 0.25, value oDot5 corresponds to 0.5, oDot75 corresponds to 0.75 and so on. | +| sf-Medium
The concerned mobility control related parameter is multiplied with this factor if the UE is in Medium Mobility state as defined in TS 38.304 [20]. Value oDot25 corresponds to 0.25, value oDot5 corresponds to 0.5, value oDot75 corresponds to 0.75, and so on. | + +### — *SPS-Config* + +The IE *SPS-Config* is used to configure downlink semi-persistent transmission. Multiple Downlink SPS configurations may be configured in one BWP of a serving cell. + +#### **SPS-Config information element** + +``` + +-- ASN1START +-- TAG-SPS-CONFIG-START + +SPS-Config ::= + SEQUENCE { + periodicity ENUMERATED {ms10, ms20, ms32, ms40, ms64, ms80, ms128, ms160, ms320, ms640, + spare6, spare5, spare4, spare3, spare2, spare1}, + nrofHARQ-Processes INTEGER (1..8), + n1PUCCH-AN PUCCH-ResourceId OPTIONAL, -- Need M + mcs-Table ENUMERATED {qam64LowSE} OPTIONAL, -- Need S + ... + [[ + sps-ConfigIndex-r16 SPS-ConfigIndex-r16 OPTIONAL, -- Cond SPS-List + harq-ProcID-Offset-r16 INTEGER (0..15) OPTIONAL, -- Need R + periodicityExt-r16 INTEGER (1..5120) OPTIONAL, -- Need R + harq-CodebookID-r16 INTEGER (1..2) OPTIONAL, -- Need R + pdsch-AggregationFactor-r16 ENUMERATED {n1, n2, n4, n8 } OPTIONAL -- Need S + ]], + [[ + sps-HARQ-Deferral-r17 INTEGER (1..32) OPTIONAL, -- Need R + n1PUCCH-AN-PUCCHsSCell-r17 PUCCH-ResourceId OPTIONAL, -- Need R + periodicityExt-r17 INTEGER (1..40960) OPTIONAL, -- Need R + nrofHARQ-Processes-v1710 INTEGER (9..32) OPTIONAL, -- Need R + harq-ProcID-Offset-v1700 INTEGER (16..31) OPTIONAL -- Need R + ]] + } + +-- TAG-SPS-CONFIG-STOP +-- ASN1STOP + +``` + +| SPS-Config field descriptions | | +|--------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| harq-CodebookID | Indicates the HARQ-ACK codebook index for the corresponding HARQ-ACK codebook for SPS PDSCH and ACK for SPS PDSCH release. | +| harq-ProcID-Offset | Indicates the offset used in deriving the HARQ process IDs, see TS 38.321 [3], clause 5.3.1. | +| mcs-Table | Indicates the MCS table the UE shall use for DL SPS (see TS 38.214 [19], clause 5.1.3.1. If present, the UE shall use the MCS table of low-SE 64QAM table indicated in Table 5.1.3.1-3 of TS 38.214 [19]. If this field is absent and field mcs-table in PDSCH-Config is set to 'qam256' and the activating DCI is of format 1_1, the UE applies the 256QAM table indicated in Table 5.1.3.1-2 of TS 38.214 [19]. If this field is absent and the field mcs-Table-r17 in PDSCH-Config is set to 'qam1024' and the activating DCI is format 1_1, the UE applies the 1024QAM table indicated in Table 5.1.3.1-4 of TS 38.214 [19]. Otherwise, the UE applies the non-low-SE 64QAM table indicated in Table 5.1.3.1-1 of TS 38.214 [19]. | +| n1PUCCH-AN | HARQ resource for PUCCH for DL SPS. The network configures the resource either as format0 or format1. The actual PUCCH-Resource is configured in PUCCH-Config and referred to by its ID. See TS 38.213 [13], clause 9.2.3. | +| n1PUCCH-AN-PUCCHsSCell | HARQ resource for PUCCH on PUCCH switching SCell (sSCell) for DL SPS. The network configures the resource either as format 0 or format 1. The actual PUCCH-Resource is configured in PUCCH-Config of the PUCCH sSCell and referred to by its ID. See TS 38.213 [13], clause 9.2.3. | +| nrofHARQ-Processes | Number of configured HARQ processes for SPS DL (see TS 38.321 [3], clause 5.8.1). If UE is configured with nrofHARQ-Processes-v1710 UE shall ignore nrofHARQ-Processes (without suffix) . | +| pdsch-AggregationFactor | Number of repetitions for SPS PDSCH (see TS 38.214 [19], clause 5.1.2.1). When the field is absent, the UE applies the value 1 for MBS multicast data and the pdsch-AggregationFactor in pdsch-Config for other data. | +| periodicity | Periodicity for DL SPS (see TS 38.214 [19] and TS 38.321 [3], clause 5.8.1). | +| periodicityExt | This field is used to calculate the periodicity for DL SPS (see TS 38.214 [19] and see TS 38.321 [3], clause 5.8.1). If this field is present, the field periodicity is ignored. The following periodicities are supported depending on the configured subcarrier spacing [ms]:
15 kHz: periodicityExt , where periodicityExt has a value between 1 and 640.
30 kHz: 0.5 x periodicityExt , where periodicityExt has a value between 1 and 1280.
60 kHz with normal CP. 0.25 x periodicityExt , where periodicityExt has a value between 1 and 2560.
60 kHz with ECP: 0.25 x periodicityExt , where periodicityExt has a value between 1 and 2560.
120 kHz: 0.125 x periodicityExt , where periodicityExt has a value between 1 and 5120.
480 kHz: 0.03125 x periodicityExt , where periodicityExt has a value between 1 and 20480.
960 kHz: 0.015625 x periodicityExt , where periodicityExt has a value between 1 and 40960.
periodicityExt-r17 is only applicable for SCS 480 kHz and 960 kHz. | +| sps-ConfigIndex | Indicates the index of one of multiple SPS configurations. | +| sps-HARQ-Deferral | Indicates the maximum number of slots or subslots the transmission of DL SPS HARQ-ACK in a slot or subslot can be deferred (see TS 38.213 [13], clause 9.2.5.4). | + +| Conditional Presence | Explanation | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SPS-List | The field is mandatory present when included in sps-ConfigToAddModList-r16 or sps-ConfigMulticastToAddModList-r17 , otherwise the field is absent. | + +### – *SPS-ConfigIndex* + +The IE *SPS-ConfigIndex* is used to indicate the index of one of multiple DL SPS configurations in one BWP. + +#### *SPS-ConfigIndex* information element + +``` +-- ASN1START +-- TAG-SPS-CONFIGINDEX-START + +SPS-ConfigIndex-r16 ::= INTEGER (0.. maxNrofSPS-Config-1-r16) + +-- TAG-SPS-CONFIGINDEX-STOP +-- ASN1STOP +``` + +### – *SPS-PUCCH-AN* + +The IE *SPS-PUCCH-AN* is used to indicate a PUCCH resource for HARQ ACK and configure the corresponding maximum payload size for the PUCCH resource. + +#### *SPS-PUCCH-AN* information element + +``` +-- ASN1START +-- TAG-SPS-PUCCH-AN-START + +SPS-PUCCH-AN-r16 ::= SEQUENCE { + sps-PUCCH-AN-ResourceID-r16 PUCCH-ResourceId, + maxPayloadSize-r16 INTEGER (4..256) OPTIONAL -- Need R +} + +-- TAG-SPS-PUCCH-AN-STOP +-- ASN1STOP +``` + +| SPS-PUCCH-AN field descriptions | +|-------------------------------------------------------------------------------------------------------------| +| maxPayloadSize
Indicates the maximum payload size for the corresponding PUCCH resource ID. | +| sps-PUCCH-AN-ResourceID
Indicates the PUCCH resource ID | + +#### — *SPS-PUCCH-AN-List* + +The IE *SPS-PUCCH-AN-List* is used to configure the list of PUCCH resources per HARQ ACK codebook + +#### ***SPS-PUCCH-AN-List* information element** + +``` +-- ASN1START +-- TAG-SPS-PUCCH-AN-LIST-START + +SPS-PUCCH-AN-List-r16 ::= SEQUENCE (SIZE(1..4)) OF SPS-PUCCH-AN-r16 + +-- TAG-SPS-PUCCH-AN-LIST-STOP +-- ASN1STOP +``` + +### — *SRB-Identity* + +The IE *SRB-Identity* is used to identify a Signalling Radio Bearer (SRB) used by a UE. + +#### ***SRB-Identity* information element** + +``` +-- ASN1START +-- TAG-SRB-IDENTITY-START + +SRB-Identity ::= INTEGER (1..3) +SRB-Identity-v1700 ::= INTEGER (4) +SRB-Identity-v1800 ::= INTEGER (5) + +-- TAG-SRB-IDENTITY-STOP +-- ASN1STOP +``` + +### — *SRS-CarrierSwitching* + +The IE *SRS-CarrierSwitching* is used to configure for SRS carrier switching when PUSCH is not configured and independent SRS power control from that of PUSCH. + +#### ***SRS-CarrierSwitching* information element** + +``` +-- ASN1START +-- TAG-SRS-CARRIERSWITCHING-START + +SRS-CarrierSwitching ::= SEQUENCE { + srs-SwitchFromServCellIndex INTEGER (0..31) OPTIONAL, -- Need M + srs-SwitchFromCarrier ENUMERATED {sUL, nUL}, +``` + +``` + +srs-TPC-PDCCH-Group CHOICE { + typeA SEQUENCE (SIZE (1..32)) OF SRS-TPC-PDCCH-Config, + typeB SRS-TPC-PDCCH-Config +} +monitoringCells SEQUENCE (SIZE (1..maxNrofServingCells)) OF ServCellIndex +... +} + +SRS-TPC-PDCCH-Config ::= SEQUENCE { + srs-CC-SetIndexList SEQUENCE (SIZE (1..4)) OF SRS-CC-SetIndex +} + +SRS-CC-SetIndex ::= SEQUENCE { + cc-SetIndex INTEGER (0..3) + cc-IndexInOneCC-Set INTEGER (0..7) +} + +-- TAG-SRS-CARRIERSWITCHING-STOP +-- ASN1STOP + +``` + +OPTIONAL, -- Need M + OPTIONAL, -- Need M + + OPTIONAL -- Need M + + OPTIONAL, -- Need M + OPTIONAL -- Need M + +#### SRS-CC-SetIndex field descriptions + +| | | +|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| cc-IndexInOneCC-Set | Indicates the CC index in one CC set for Type A (see TS 38.212 [17], TS 38.213 [13], clause 7.3.1, 11.4). The network always includes this field when the srs-TPC-PDCCH-Group is set to typeA . | +| cc-SetIndex | Indicates the CC set index for Type A associated (see TS 38.212 [17], TS 38.213 [13], clause 7.3.1, 11.4). The network always includes this field when the srs-TPC-PDCCH-Group is set to typeA . The network does not configure this field to 3 in this release of specification. | + +#### SRS-CarrierSwitching field descriptions + +| | | +|------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| monitoringCells | A set of serving cells for monitoring PDCCH conveying SRS DCI format with CRC scrambled by TPC-SRS-RNTI (see TS 38.212 [17], TS 38.213 [13], clause 7.3.1, 11.3). | +| srs-SwitchFromServCellIndex | Indicates the serving cell whose UL transmission may be interrupted during SRS transmission on a PUSCH-less SCell. During SRS transmission on a PUSCH-less SCell, the UE may temporarily suspend the UL transmission on a serving cell with PUSCH in the same CG to allow the PUSCH-less SCell to transmit SRS. (see TS 38.214 [19], clause 6.2.1.3). | +| srs-TPC-PDCCH-Group | Network configures the UE with either typeA-SRS-TPC-PDCCH-Group or typeB-SRS-TPC-PDCCH-Group , if any. | +| typeA | Type A trigger configuration for SRS transmission on a PUSCH-less SCell (see TS 38.213 [13], clause 11.4). In this release, the network configures at most one entry (the first entry) of typeA , and the first entry corresponds to the serving cell in which the SRS-CarrierSwitching field is configured. SRS carrier switching to SUL carrier is not supported in this version of the specification. | +| typeB | Type B trigger configuration for SRS transmission on a PUSCH-less SCell (see TS 38.213 [13], clause 11.4). | + +#### | | |------------------------------------------------| | SRS-TPC-PDCCH-Config field descriptions | |------------------------------------------------| + +#### | | |----------------------------| | srs-CC-SetIndexList | |----------------------------| + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| A list of pairs of [cc-SetIndex; cc-IndexInOneCC-Set] (see TS 38.212 [17], TS 38.213 [13], clause 7.3.1, 11.4). The network does not configure this field for typeB . | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +#### SRS-Config + +The IE *SRS-Config* is used to configure sounding reference signal transmissions. The configuration defines a list of SRS-Resources, a list of SRS-PosResources, a list of SRS-PosResourceSets and a list of SRS-ResourceSets. Each resource set defines a set of SRS-Resources or SRS-PosResources. The network triggers the transmission of the set of SRS-Resources or SRS-PosResources using a configured aperiodicSRS-ResourceTrigger (L1 DCI). The network does not configure SRS specific power control parameters, *alpha* (without suffix), *p0* (without suffix) or *pathlossReferenceRS* if *unifiedTCI-StateType* is configured for the serving cell. + +#### SRS-Config information element + +``` +-- ASN1START +-- TAG-SRS-CONFIG-START + +SRS-Config ::= + SEQUENCE { + srs-ResourceSetToReleaseList SEQUENCE (SIZE(1..maxNrofSRS-ResourceSets)) OF SRS-ResourceSetId OPTIONAL, -- Need N + srs-ResourceSetToAddModList SEQUENCE (SIZE(1..maxNrofSRS-ResourceSets)) OF SRS-ResourceSet OPTIONAL, -- Need N + srs-ResourceToReleaseList SEQUENCE (SIZE(1..maxNrofSRS-Resources)) OF SRS-ResourceId OPTIONAL, -- Need N + srs-ResourceToAddModList SEQUENCE (SIZE(1..maxNrofSRS-Resources)) OF SRS-Resource OPTIONAL, -- Need N + tpc-Accumulation ENUMERATED {disabled} OPTIONAL, -- Need S + ... + [[ + srs-RequestDCI-1-2-r16 INTEGER (1..2) OPTIONAL, -- Need S + srs-RequestDCI-0-2-r16 INTEGER (1..2) OPTIONAL, -- Need S + srs-ResourceSetToAddModListDCI-0-2-r16 SEQUENCE (SIZE(1..maxNrofSRS-ResourceSets)) OF SRS-ResourceSet OPTIONAL, -- Need N + srs-ResourceSetToReleaseListDCI-0-2-r16 SEQUENCE (SIZE(1..maxNrofSRS-ResourceSets)) OF SRS-ResourceSetId OPTIONAL, -- Need N + srs-PosResourceSetToReleaseList-r16 SEQUENCE (SIZE(1..maxNrofSRS-PosResourceSets-r16)) OF SRS-PosResourceSetId-r16 OPTIONAL, -- Need N + srs-PosResourceSetToAddModList-r16 SEQUENCE (SIZE(1..maxNrofSRS-PosResourceSets-r16)) OF SRS-PosResourceSet-r16 OPTIONAL, -- Need N + srs-PosResourceToReleaseList-r16 SEQUENCE (SIZE(1..maxNrofSRS-PosResources-r16)) OF SRS-PosResourceId-r16 OPTIONAL, -- Need N + srs-PosResourceToAddModList-r16 SEQUENCE (SIZE(1..maxNrofSRS-PosResources-r16)) OF SRS-PosResource-r16 OPTIONAL, -- Need N + ]], + [[ + dci-TriggeringPosResourceSetLink-r18 ENUMERATED { enabled } OPTIONAL -- Need R + ]] + } + +SRS-ResourceSet ::= + SEQUENCE { + srs-ResourceSetId SRS-ResourceSetId, + srs-ResourceIdList SEQUENCE (SIZE(1..maxNrofSRS-ResourcesPerSet)) OF SRS-ResourceId OPTIONAL, -- Cond Setup + resourceType CHOICE { + aperiodic SEQUENCE { + aperiodicSRS-ResourceTrigger INTEGER (1..maxNrofSRS-TriggerStates-1), + csi-RS NZP-CSI-RS-ResourceId OPTIONAL, -- Cond NonCodebook + slotOffset INTEGER (1..32) OPTIONAL, -- Need S + } + } + } +``` + +``` + + ... + [[ + aperiodicSRS-ResourceTriggerList SEQUENCE (SIZE(1..maxNrofSRS-TriggerStates-2)) + OF INTEGER (1..maxNrofSRS-TriggerStates-1) OPTIONAL -- Need M + ]] + }, + semi-persistent SEQUENCE { + associatedCSI-RS NZP-CSI-RS-ResourceId OPTIONAL, -- Cond NonCodebook + ... + }, + periodic SEQUENCE { + associatedCSI-RS NZP-CSI-RS-ResourceId OPTIONAL, -- Cond NonCodebook + ... + } +}, +usage ENUMERATED {beamManagement, codebook, nonCodebook, antennaSwitching}, +alpha Alpha OPTIONAL, -- Need S +p0 INTEGER (-202..24) OPTIONAL, -- Cond Setup +pathlossReferenceRS PathlossReferenceRS-Config OPTIONAL, -- Need M +srs-PowerControlAdjustmentStates ENUMERATED { sameAsFci2, separateClosedLoop} OPTIONAL, -- Need S +... +[[ +pathlossReferenceRSList-r16 SetupRelease { PathlossReferenceRSList-r16} OPTIONAL -- Need M +]], +[[ +usagePDC-r17 ENUMERATED {true} OPTIONAL, -- Need R +availableSlotOffsetList-r17 SEQUENCE (SIZE(1..4)) OF AvailableSlotOffset-r17 OPTIONAL, -- Need R +followUnifiedTCI-StateSRS-r17 ENUMERATED {enabled} OPTIONAL, -- Need R +]], +[[ +applyIndicatedTCI-State-r18 ENUMERATED {first, second} OPTIONAL -- Cond FollowUTCI +]] +} + +AvailableSlotOffset-r17 ::= INTEGER (0..7) + +PathlossReferenceRS-Config ::= CHOICE { + ssb-Index SSB-Index, + csi-RS-Index NZP-CSI-RS-ResourceId +} + +PathlossReferenceRSList-r16 ::= SEQUENCE (SIZE (1..maxNrofSRS-PathlossReferenceRS-r16)) OF PathlossReferenceRS-r16 + +PathlossReferenceRS-r16 ::= SEQUENCE { + srs-PathlossReferenceRS-Id-r16 SRS-PathlossReferenceRS-Id-r16, + pathlossReferenceRS-r16 PathlossReferenceRS-Config +} + +SRS-PathlossReferenceRS-Id-r16 ::= INTEGER (0..maxNrofSRS-PathlossReferenceRS-1-r16) + +SRS-PosResourceSet-r16 ::= SEQUENCE { + +``` + +``` + +srs-PosResourceSetId-r16 SRS-PosResourceSetId-r16, +srs-PosResourceIdList-r16 SEQUENCE (SIZE(1..maxNrofSRS-ResourcesPerSet)) OF SRS-PosResourceId-r16 + OPTIONAL, -- Cond Setup +resourceType-r16 CHOICE { + aperiodic-r16 SEQUENCE { + aperiodicSRS-ResourceTriggerList-r16 + SEQUENCE (SIZE(1..maxNrofSRS-TriggerStates-1)) + OF INTEGER (1..maxNrofSRS-TriggerStates-1) + OPTIONAL, -- Need M + ... + }, + semi-persistent-r16 SEQUENCE { + ... + }, + periodic-r16 SEQUENCE { + ... + } +}, +alpha-r16 Alpha + OPTIONAL, -- Need S +p0-r16 INTEGER (-202..24) + OPTIONAL, -- Cond Setup +pathlossReferenceRS-Pos-r16 CHOICE { + ssb-IndexServing-r16 SSB-Index, + ssb-Ncell-r16 SSB-InfoNcell-r16, + dl-PRS-r16 DL-PRS-Info-r16 +} + OPTIONAL, -- Need M +... +[[ +srs-PosHyperSFN-Index-r18 ENUMERATED {even0, odd1} + OPTIONAL -- Need S +]] +} + +SRS-ResourceSetId ::= INTEGER (0..maxNrofSRS-ResourceSets-1) + +SRS-PosResourceSetId-r16 ::= INTEGER (0..maxNrofSRS-PosResourceSets-1-r16) + +SRS-Resource ::= SEQUENCE { + srs-ResourceId SRS-ResourceId, + nrofSRS-Ports ENUMERATED {port1, ports2, ports4}, + ptrs-PortIndex ENUMERATED {n0, n1} + OPTIONAL, -- Need R + 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) + } + }, + resourceMapping SEQUENCE { + startPosition INTEGER (0..5), + nrofSymbols ENUMERATED {n1, n2, n4}, + } +} + +``` + +``` + +repetitionFactor ENUMERATED {n1, n2, n4} +}, +freqDomainPosition INTEGER (0..67), +freqDomainShift INTEGER (0..268), +freqHopping SEQUENCE { + c-SRS INTEGER (0..63), + b-SRS INTEGER (0..3), + b-hop INTEGER (0..3) +}, +groupOrSequenceHopping ENUMERATED { neither, groupHopping, sequenceHopping }, +resourceType CHOICE { + aperiodic SEQUENCE { + ... + }, + semi-persistent SEQUENCE { + periodicityAndOffset-sp SRS-PeriodicityAndOffset, + ... + }, + periodic SEQUENCE { + periodicityAndOffset-p SRS-PeriodicityAndOffset, + ... + } +}, +sequenceId INTEGER (0..1023), +spatialRelationInfo SRS-SpatialRelationInfo OPTIONAL, -- Need R +... +[[ +resourceMapping-r16 SEQUENCE { + startPosition-r16 INTEGER (0..13), + nrofSymbols-r16 ENUMERATED {n1, n2, n4}, + repetitionFactor-r16 ENUMERATED {n1, n2, n4} +} +]], +[[ +spatialRelationInfo-PDC-r17 SetupRelease { SpatialRelationInfo-PDC-r17 } OPTIONAL, -- Need M +resourceMapping-r17 SEQUENCE { + startPosition-r17 INTEGER (0..13), + nrofSymbols-r17 ENUMERATED {n1, n2, n4, n8, n10, n12, n14}, + repetitionFactor-r17 ENUMERATED {n1, n2, n4, n5, n6, n7, n8, n10, n12, n14} +} +partialFreqSounding-r17 SEQUENCE { + startRBIndexFScaling-r17 CHOICE{ + startRBIndexAndFreqScalingFactor2-r17 INTEGER (0..1), + startRBIndexAndFreqScalingFactor4-r17 INTEGER (0..3) + }, + enableStartRBHopping-r17 ENUMERATED {enable} +} +transmissionComb-n8-r17 SEQUENCE { + combOffset-n8-r17 INTEGER (0..7), + cyclicShift-n8-r17 INTEGER (0..5) +} + +``` + +``` + +srs-TCI-State-r17 CHOICE { + srs-UL-TCI-State TCI-UL-StateId-r17, + srs-DLorJointTCI-State TCI-StateId +} OPTIONAL, -- Need R +]], +[[ +repetitionFactor-v1730 ENUMERATED {n3} OPTIONAL, -- Need R +srs-DLorJointTCI-State-v1730 SEQUENCE { + cellAndBWP-r17 ServingCellAndBWP-Id-r17 +} OPTIONAL -- Cond DLorJointTCI-SRS +]], +[[ +nrofSRS-Ports-n8-r18 ENUMERATED {ports8, ports8tdm} OPTIONAL, -- Need R +combOffsetHopping-r18 SEQUENCE { + hoppingId-r18 INTEGER (0..1023) OPTIONAL, -- Need R + hoppingSubset-r18 CHOICE { + transmissionComb-n4 BIT STRING (SIZE (4)), + transmissionComb-n8 BIT STRING (SIZE (8)) + } OPTIONAL, + hoppingWithRepetition-r18 ENUMERATED {symbol, repetition} OPTIONAL, +} OPTIONAL, -- Need R +cyclicShiftHopping-r18 SEQUENCE { + hoppingId-r18 INTEGER (0..1023) OPTIONAL, -- Need R + hoppingSubset-r18 CHOICE { + transmissionComb-n2 BIT STRING (SIZE (8)), + transmissionComb-n4 BIT STRING (SIZE (12)), + transmissionComb-n8 BIT STRING (SIZE (6)) + } OPTIONAL, + hoppingFinerGranularity-r18 ENUMERATED {enable} OPTIONAL, +} OPTIONAL, -- Need R +]] +} + +SRS-PosResource-r16::= SEQUENCE { + srs-PosResourceId-r16 SRS-PosResourceId-r16, + transmissionComb-r16 CHOICE { + n2-r16 SEQUENCE { + combOffset-n2-r16 INTEGER (0..1), + cyclicShift-n2-r16 INTEGER (0..7) + }, + n4-r16 SEQUENCE { + combOffset-n4-r16 INTEGER (0..3), + cyclicShift-n4-r16 INTEGER (0..11) + }, + n8-r16 SEQUENCE { + combOffset-n8-r16 INTEGER (0..7), + cyclicShift-n8-r16 INTEGER (0..5) + }, + ... + }, + resourceMapping-r16 SEQUENCE { + +``` + +``` + + startPosition-r16 INTEGER (0..13), + nrofSymbols-r16 ENUMERATED {n1, n2, n4, n8, n12} + }, + freqDomainShift-r16 INTEGER (0..268), + freqHopping-r16 SEQUENCE { + c-SRS-r16 INTEGER (0..63), + ... + }, + groupOrSequenceHopping-r16 ENUMERATED { neither, groupHopping, sequenceHopping }, + resourceType-r16 CHOICE { + aperiodic-r16 SEQUENCE { + slotOffset-r16 INTEGER (1..32) OPTIONAL, -- Need S + ... + }, + semi-persistent-r16 SEQUENCE { + periodicityAndOffset-sp-r16 SRS-PeriodicityAndOffset-r16, + ... + [[ + periodicityAndOffset-sp-Ext-r16 SRS-PeriodicityAndOffsetExt-r16 OPTIONAL -- Need R + ]] + }, + periodic-r16 SEQUENCE { + periodicityAndOffset-p-r16 SRS-PeriodicityAndOffset-r16, + ... + [[ + periodicityAndOffset-p-Ext-r16 SRS-PeriodicityAndOffsetExt-r16 OPTIONAL -- Need R + ]] + } + }, + sequenceId-r16 INTEGER (0..65535), + spatialRelationInfoPos-r16 SRS-SpatialRelationInfoPos-r16 OPTIONAL, -- Need R + ... + [[ + srs-PosHyperSFN-Index-r18 ENUMERATED {even0, odd1} OPTIONAL, --Need S + txHoppingConfig-r18 TxHoppingConfig-r18 OPTIONAL --Need R + ]] +} + +SRS-SpatialRelationInfo ::= SEQUENCE { + servingCellId ServCellIndex + referenceSignal CHOICE { + ssb-Index SSB-Index, + csi-RS-Index NZP-CSI-RS-ResourceId, + srs SEQUENCE { + resourceId SRS-ResourceId, + uplinkBWP BWP-Id + } + } +} + +SRS-SpatialRelationInfoPos-r16 ::= CHOICE { + +``` + +``` + +servingRS-r16 SEQUENCE { + servingCellId ServCellIndex + referenceSignal-r16 CHOICE { + ssb-IndexServing-r16 SSB-Index, + csi-RS-IndexServing-r16 NZP-CSI-RS-ResourceId, + srs-SpatialRelation-r16 SEQUENCE { + resourceSelection-r16 CHOICE { + srs-ResourceId-r16 SRS-ResourceId, + srs-PosResourceId-r16 SRS-PosResourceId-r16 + }, + uplinkBWP-r16 BWP-Id + } + }, + ssb-Ncell-r16 SSB-InfoNcell-r16, + dl-PRS-r16 DL-PRS-Info-r16 +} + +SSB-Configuration-r16 ::= SEQUENCE { + ssb-Freq-r16 ARFCN-ValueNR, + halfFrameIndex-r16 ENUMERATED {zero, one}, + ssbSubcarrierSpacing-r16 SubcarrierSpacing, + ssb-Periodicity-r16 ENUMERATED { ms5, ms10, ms20, ms40, ms80, ms160, spare2,spare1 } OPTIONAL, -- Need S + sfn0-Offset-r16 SEQUENCE { + sfn-Offset-r16 INTEGER (0..1023), + integerSubframeOffset-r16 INTEGER (0..9) OPTIONAL, -- Need R + } OPTIONAL, -- Need R + sfn-SSB-Offset-r16 INTEGER (0..15), + ssb-PBCH-BlockPower-r16 INTEGER (-60..50) OPTIONAL, -- Cond Pathloss +} + +SSB-InfoNcell-r16 ::= SEQUENCE { + physicalCellId-r16 PhysCellId, + ssb-IndexNcell-r16 SSB-Index OPTIONAL, -- Need S + ssb-Configuration-r16 SSB-Configuration-r16 OPTIONAL, -- Need S +} + +DL-PRS-Info-r16 ::= SEQUENCE { + dl-PRS-ID-r16 INTEGER (0..255), + dl-PRS-ResourceSetId-r16 INTEGER (0..7), + dl-PRS-ResourceId-r16 INTEGER (0..63) OPTIONAL, -- Need S +} + +SRS-ResourceId ::= INTEGER (0..maxNrofSRS-Resources-1) +SRS-PosResourceId-r16 ::= INTEGER (0..maxNrofSRS-PosResources-1-r16) + +SRS-PeriodicityAndOffset ::= CHOICE { + sl1 NULL, + sl2 INTEGER(0..1), + sl4 INTEGER(0..3), + sl5 INTEGER(0..4), +} + +``` + +``` +sl8 INTEGER(0..7), +sl10 INTEGER(0..9), +sl16 INTEGER(0..15), +sl20 INTEGER(0..19), +sl32 INTEGER(0..31), +sl40 INTEGER(0..39), +sl64 INTEGER(0..63), +sl80 INTEGER(0..79), +sl160 INTEGER(0..159), +sl320 INTEGER(0..319), +sl640 INTEGER(0..639), +sl1280 INTEGER(0..1279), +sl2560 INTEGER(0..2559) +} + +SRS-PeriodicityAndOffset-r16 ::= CHOICE { +sl1 NULL, +sl2 INTEGER(0..1), +sl4 INTEGER(0..3), +sl5 INTEGER(0..4), +sl8 INTEGER(0..7), +sl10 INTEGER(0..9), +sl16 INTEGER(0..15), +sl20 INTEGER(0..19), +sl32 INTEGER(0..31), +sl40 INTEGER(0..39), +sl64 INTEGER(0..63), +sl80 INTEGER(0..79), +sl160 INTEGER(0..159), +sl320 INTEGER(0..319), +sl640 INTEGER(0..639), +sl1280 INTEGER(0..1279), +sl2560 INTEGER(0..2559), +sl5120 INTEGER(0..5119), +sl10240 INTEGER(0..10239), +sl40960 INTEGER(0..40959), +sl81920 INTEGER(0..81919), +... +} + +SRS-PeriodicityAndOffsetExt-r16 ::= CHOICE { +sl128 INTEGER(0..127), +sl256 INTEGER(0..255), +sl512 INTEGER(0..511), +sl20480 INTEGER(0..20479) +} + +SpatialRelationInfo-PDC-r17 ::= SEQUENCE { +referenceSignal CHOICE { +ssb-Index SSB-Index, +csi-RS-Index NZP-CSI-RS-ResourceId, +``` + +``` + +dl-PRS-PDC NR-DL-PRS-ResourceID-r17, +srs SEQUENCE { + resourceId SRS-ResourceId, + uplinkBWP BWP-Id +}, +... +}, +... +} + +TxHoppingConfig-r18 ::= SEQUENCE { + overlapValue-r18 ENUMERATED {zeroRB, oneRB, twoRB, fourRB}, + numberOfHops INTEGER(1..6), + slotOffsetForRemainingHopsList-r18 SEQUENCE (SIZE (1..maxNrofHops-r18-1) ) OF SlotOffsetForRemainingHops-r18, + ... +} + +SlotOffsetForRemainingHops-r18 ::= SEQUENCE { + slotOffsetRemainingHops-r18 CHOICE { + aperiodic-r18 SEQUENCE { + slotOffset-r18 INTEGER (1..32) OPTIONAL, -- Need S + startPosition-r18 INTEGER (0..13) OPTIONAL, -- Need S + ... + }, + semi-persistent-r18 SEQUENCE { + periodicityAndOffset-sp-r18 SRS-PeriodicityAndOffset-r16 OPTIONAL, -- Need R + periodicityAndOffset-sp-Ext-r18 SRS-PeriodicityAndOffsetExt-r16 OPTIONAL, -- Need R + ... + }, + periodic-r18 SEQUENCE { + periodicityAndOffset-p-r18 SRS-PeriodicityAndOffset-r16 OPTIONAL, -- Need R + periodicityAndOffset-p-Ext-r18 SRS-PeriodicityAndOffsetExt-r16 OPTIONAL, -- Need R + ... + }, + ... + } +} + +-- TAG-SRS-CONFIG-STOP +-- ASN1STOP + +``` + +Editor's Note: The ASN.1 SRS periodicity covering 2048 ms is FFS. + +| SRS-Config field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| dci-TriggeringPosResourceSetLink
Indicates whether the single DCI-triggering SRS positioning resource sets across the linked carriers is enabled or not for bandwidth aggregation. | +| tpc-Accumulation
If the field is absent, UE applies TPC commands via accumulation. If disabled, UE applies the TPC command without accumulation (this applies to SRS when a separate closed loop is configured for SRS) (see TS 38.213 [13], clause 7.3). | + +| SRS-Resource, SRS-PosResource field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| cyclicShift-n2
Cyclic shift configuration (see TS 38.214 [19], clause 6.2.1). | +| cyclicShift-n4
Cyclic shift configuration (see TS 38.214 [19], clause 6.2.1). | +| cyclicShift-n8
Cyclic shift configuration (see TS 38.214 [19], clause 6.2.1). | +| combOffsetHopping
Configures UE with comb offset hopping. The hoppingId is used to initialize pseudo random comb offset hopping. If UE is configured with both comb offset and cyclic shift hopping, only one hoppingId is configured. The hoppingWithRepetition configures time-domain hopping behavior for repetition factor $R > 1$ . | +| cyclicShiftHopping
Configures UE with cyclic shift hopping. The hoppingId is used to initialize pseudo random cyclic shift hopping. If UE is configured with both comb offset and cyclic shift hopping, only one hoppingId is configured. The hoppingFinerGranularity enables finer granular hopping, see TSxxxx. If hoppingSubset is configured, hoppingFinerGranularity is not configured. | +| enableStartRBHopping
When this RRC parameter is configured, start RB location hopping is enabled for partial frequency sounding in different SRS frequency hopping periods for periodic/semi-persistent/aperiodic SRS as described in clause 6.4.1.4 in TS 38.211. | +| freqHopping
Includes parameters capturing SRS frequency hopping (see TS 38.214 [19], clause 6.2.1). For CLI SRS-RSRP measurement, the network always configures this field such that b-hop > b-SRS . For SRS for positioning configuration in multiple cells this field is commonly configured across cells within the validity area. c-SRS Indicates the maximum bandwidth. When TxHoppingConfig is configured the valid values for c-SRS are such that the maximum bandwidth is: 104 PRBs, 48 PRBs, 132 PRBs, 64 PRBs, for 15,30,60,120 KHz respectively. The same value for c-SRS is configured for all the hops when TxHoppingConfig is configured. | +| groupOrSequenceHopping
Parameter(s) for configuring group or sequence hopping (see TS 38.211 [16], clause 6.4.1.4.2). For CLI SRS-RSRP measurement, the network always configures this parameter to 'neither'. For SRS for positioning configuration in multiple cells this field is commonly configured across cells within the validity area. | +| nrofSRS-Ports
Number of ports. For CLI SRS-RSRP measurement, the network always configures this parameter to 'port1'. | +| nrofSRS-Ports-n8
Number of ports if the number of antenna ports is 8. The value 'ports8' configures UE with 8 antenna ports and the value 'ports8tdm' configures the UE with 8 antenna ports which are partitioned into 2 subsets with each subset having 4 different ports, and the subsets are mapped to different OFDM symbols, see Reference XXX. If combOffsetHopping-r18 or cyclicShiftHopping-r18 is configured, this field is not set to ports8tdm . If this field is present UE ignores the field nrofSRS-Ports . | +| periodicityAndOffset-p, periodicityAndOffset-p-Ext
Periodicity and slot offset for this SRS resource. All values are in "number of slots". Value s1 corresponds to a periodicity of 1 slot, value s2 corresponds to a periodicity of 2 slots, and so on. For each periodicity the corresponding offset is given in number of slots. For periodicity s1 the offset is 0 slots (see TS 38.214 [19], clause 6.2.1). For CLI SRS-RSRP measurement, s1280 and s2560 cannot be configured. For SRS-PosResource , values s120480 , s140960 and s181920 cannot be configured for SCS=15kHz, values s140960 and s181920 cannot be configured for SCS=30kHz, and value s181920 cannot be configured for SCS=60kHz. When periodicityAndOffset-p-Ext is present, periodicityAndOffset-p shall be ignored by the UE. | +| periodicityAndOffset-sp, periodicityAndOffset-sp-Ext
Periodicity and slot offset for this SRS resource. All values are in "number of slots". Value s1 corresponds to a periodicity of 1 slot, value s2 corresponds to a periodicity of 2 slots, and so on. For each periodicity the corresponding offset is given in number of slots. For periodicity s1 the offset is 0 slots (see TS 38.214 [19], clause 6.2.1). For SRS-PosResource , values s120480 , s140960 and s181920 cannot be configured for SCS=15kHz, values s140960 and s181920 cannot be configured for SCS=30kHz, and value s181920 cannot be configured for SCS=60kHz. When periodicityAndOffset-sp-Ext is present, periodicityAndOffset-sp shall be ignored by the UE. | +| ptrs-PortIndex | + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

The PTRS port index for this SRS resource for non-codebook based UL MIMO. This is only applicable when the corresponding PTRS-UplinkConfig is set to CP-OFDM. The ptrs-PortIndex configured here must be smaller than the maxNrofPorts configured in the PTRS-UplinkConfig (see TS 38.214 [19], clause 6.2.3.1). This parameter is not applicable to CLI SRS-RSRP measurement.

| +|

resourceMapping
OFDM symbol location of the SRS resource within a slot including nrofSymbols (number of OFDM symbols), startPosition (value 0 refers to the last symbol, value 1 refers to the second last symbol, and so on) and repetitionFactor (see TS 38.214 [19], clause 6.2.1 and TS 38.211 [16], clause 6.4.1.4). The configured SRS resource does not exceed the slot boundary. If resourceMapping-r16 is signalled, UE shall ignore the resourceMapping (without suffix). If resourceMapping-r17 is signalled, resourceMapping-r16 is not signalled and the UE shall ignore the resourceMapping (without suffix) and only the values of nrofSymbols which are integer multiples of the configured repetitionFactor can be configured. The network can only signal repetitionFactor-v1730 if resourceMapping-r17 is signalled. When repetitionFactor-v1730 is signalled, the UE shall ignore repetitionFactor-r17. For CLI SRS-RSRP measurement, the network always configures nrofSymbols and repetitionFactor to 'n1'. For SRS for positioning configuration in multiple cells this field is commonly configured across cells within the validity area.

| +|

resourceType
Periodicity and offset for semi-persistent and periodic SRS resource, or slot offset for aperiodic SRS resource for positioning (see TS 38.214 [19], clause 6.2.1). For CLI SRS-RSRP measurement, only 'periodic' is applicable for resourceType. For SRS for positioning configuration in multiple cells this field is commonly configured across cells within the validity area.

| +|

sequenceId
Sequence ID used to initialize pseudo random group and sequence hopping (see TS 38.214 [19], clause 6.2.1). For SRS for positioning configuration in multiple cells this field is commonly configured across cells within the validity area.

| +|

spatialRelationInfo
Configuration of the spatial relation between a reference RS and the target SRS. Reference RS can be SSB/CSI-RS/SRS (see TS 38.214 [19], clause 6.2.1). This parameter is not applicable to CLI SRS-RSRP measurement. This field is not configured if unifiedTCI-StateType is configured for the serving cell.

| +|

spatialRelationInfo-PDC
Configuration of the spatial relation between a reference RS and the target SRS. Reference RS can be SSB/CSI-RS/SRS/DL-PRS-PDC (see TS 38.214 [19], clause 6.2.1). The field is present in case of resourceType=periodic and usagePDC-r17=true in the SRS-ResourceSet, otherwise the field is absent.

| +|

spatialRelationInfoPos
Configuration of the spatial relation between a reference RS and the target SRS. Reference RS can be SSB/CSI-RS/SRS/DL-PRS (see TS 38.214 [19], clause 6.2.1). If the IE srs-ResourceId-Ext is present, the IE srs-ResourceId in spatialRelationInfoPos represents the index from 0 to 63. Otherwise the IE srs-ResourceId in spatialRelationInfoPos represents the index from 0 to 31.

| +|

srs-PosHyperSFN-Index
Indicates whether the current SFN is even or odd SFN for SRS for Positioning transmission. If this field is not configured, the UE assumes that SRS for positioning periodicity longer than one SFN is not configured.

| +|

srs-RequestDCI-0-2
Indicate the number of bits for "SRS request" in DCI format 0_2. When the field is absent, then the value of 0 bit for "SRS request" in DCI format 0_2 is applied. If the parameter srs-RequestDCI-0-2 is configured to value 1, 1 bit is used to indicate one of the first two rows of Table 7.3.1.1.2-24 in TS 38.212 [17] for triggered aperiodic SRS resource set. If the value 2 is configured, 2 bits are used to indicate one of the rows of Table 7.3.1.1.2-24 in TS 38.212 [17]. When UE is configured with supplementaryUplink, an extra bit (the first bit of the SRS request field) is used for the non-SUL/SUL indication.

| +|

srs-RequestDCI-1-2
Indicate the number of bits for "SRS request" in DCI format 1_2. When the field is absent, then the value of 0 bit for "SRS request" in DCI format 1_2 is applied. When the UE is configured with supplementaryUplink, an extra bit (the first bit of the SRS request field) is used for the non-SUL/SUL indication (see TS 38.214 [19], clause 6.1.1.2).

| +|

srs-ResourceSetToAddModListDCI-0-2
List of SRS resource set to be added or modified for DCI format 0_2 (see TS 38.212 [17], clause 7.3.1).

| +|

srs-ResourceSetToReleaseListDCI-0-2
List of SRS resource set to be released for DCI format 0_2 (see TS 38.212 [17], clause 7.3.1).

| +|

srs-TCI-State

| + +Configuration of either a UL TCI state or a joint TCI state for the SRS resource. In case of *UL TCI-State*, refers to the TCI state defined in *ul-TCI-StateList* in the *BWP-UplinkDedicated* where the *SRS-Config* is configured. In case of joint TCI state, refers to a TCI state defined in *dl-OrJointTCI-StateList* in *pdsch-Config* of the *BWP-DownlinkDedicated* and serving cell indicated by *cellAndBWP*. This field is absent when the SRS resource is in an *SRS-ResourceSet* configured with *followUnifiedTCI-StateSRS-r17* or *applyIndicatedTCI-State*, or when the field *unifiedTCI-StateType* is not configured to the serving cell which the SRS resource is located in. + +##### ***startRBIndexAndFreqScalingFactor*** + +Configures the UE with the startRBIndex and freqScalingFactor for partial frequency sounding as described in Clause 6.4.1.4 in TS 38.211. The startRBIndexForFScaling2 gives the startRBIndex when freqScalingFactor is 2 and the startRBIndexForFScaling4 gives the startRBIndex when FreqScalingFactor is 4 + +##### ***transmissionComb, transmissionComb-n2, transmissionComb-n4, transmissionComb-n8*** + +Comb value (2 or 4 or 8) and comb offset (0..combValue-1) (see TS 38.214 [19], clause 6.2.1). If network configures field *transmissionComb-n8*, the UE ignores *transmissionComb*. For SRS for positioning configuration in multiple cells this field is commonly configured across cells within the validity area. + +| SRS-ResourceSet, SRS-PosResourceSet field descriptions | | +|---------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| alpha | alpha value for SRS power control (see TS 38.213 [13], clause 7.3). When the field is absent the UE applies the value 1. For SRS for positioning configuration in multiple cells this field is commonly configured across cells within the validity area. | +| aperiodicSRS-ResourceTriggerList | An additional list of DCI "code points" upon which the UE shall transmit SRS according to this SRS resource set configuration (see TS 38.214 [19], clause 6). When the field is not included during a reconfiguration of SRS-ResourceSet of resourceType set to aperiodic , UE maintains this value based on the Need M; that is, this list is not considered as an extension of aperiodicSRS-ResourceTrigger for purpose of applying the general rule for extended list in clause 6.1.3. | +| aperiodicSRS-ResourceTrigger | The DCI "code point" upon which the UE shall transmit SRS according to this SRS resource set configuration (see TS 38.214 [19], clause 6). | +| applyIndicatedTCI-State | This field indicates, for an SRS-ResourceSet, if UE applies the first or the second "indicated" UL only TCI or joint TCI as specified in TS 38.214 [19], clause 6.2.1. If more than one value for the field coresetPoolIndex is configured in IE controlResourceSet for the BWP, the value 'first' corresponds to the "indicated" joint/UL TCI states specific to coresetPoolIndex value 0 and the value 'second' correspond to the value 1, respectively. When UE is configured with two SRS resource sets with usage set to Codebook or nonCodebook , network does not configure the first set with value 'second' or second set with value 'first'. | +| associatedCSI-RS | ID of CSI-RS resource associated with this SRS resource set in non-codebook based operation (see TS 38.214 [19], clause 6.1.1.2). | +| availableSlotOffsetList | Indicates a list of up to four different available slot offset values from slot n+k to the slot where the aperiodic SRS resource set is transmitted, where slot n is the slot with the triggering DCI, and k is the slotOffset (without suffix) as described in clause 6.2.1 of TS 38.214 [19]. | +| csi-RS | ID of CSI-RS resource associated with this SRS resource set (see TS 38.214 [19], clause 6.1.1.2). | +| dl-PRS | This field indicates a PRS configuration. | +| followUnifiedTCI-StateSRS | When set to enabled, for SRS resource Set, the UE applies the "indicated" UL only TCI or joint TCI as specified in TS 38.214 [19], clause 5.1.5. This parameter may be configured for aperiodic SRS for BM or SRS of any time-domain behavior for codebook, non-codebook, and antenna switching. | +| p0 | P0 value for SRS power control. The value is in dBm. Only even values (step size 2) are allowed (see TS 38.213 [13], clause 7.3). For SRS for positioning configuration in multiple cells this field is commonly configured across cells within the validity area. | +| pathlossReferenceRS | A reference signal (e.g. a CSI-RS config or a SS block) to be used for SRS path loss estimation (see TS 38.213 [13], clause 7.3). | +| pathlossReferenceRS-Pos | A reference signal (e.g. a SS block or a DL-PRS config) to be used for SRS path loss estimation (see TS 38.213 [13], clause 7.3). | +| pathlossReferenceRSList | Multiple candidate pathloss reference RS(s) for SRS power control, where one candidate RS can be mapped to SRS Resource Set via MAC CE (clause 6.1.3.27 in TS 38.321 [3]). The network can only configure this field if pathlossReferenceRS is not configured in the same SRS-ResourceSet . | +| resourceType | Time domain behavior of SRS resource configuration, see TS 38.214 [19], clause 6.2.1. The network configures SRS resources in the same resource set with the same time domain behavior on periodic, aperiodic and semi-persistent SRS. The aperiodic SRS is not applicable for the UE in RRC_INACTIVE. For SRS for positioning configuration in multiple cells this field is commonly configured across cells within the validity area. | +| slotOffset | An offset in number of slots between the triggering DCI and the actual transmission of this SRS-ResourceSet . If the field is absent the UE applies no offset (value 0). | +| srs-PosHyperSFN-index | | + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Indicates whether the current SFN is even or odd SFN for SRS for Positioning transmission. If this field is not configured, the UE assumes that SRS for positioning periodicity longer than one SFN is not configured. | +| srs-PowerControlAdjustmentStates
Indicates whether $h_{srs,c(i)} = f_c(i, 1)$ or $h_{srs,c(i)} = f_c(i, 2)$ (if twoPUSCH-PC-AdjustmentStates are configured) or separate close loop is configured for SRS. This parameter is applicable only for UIs on which UE also transmits PUSCH. If absent or release, the UE applies the value sameAs-Fci1 (see TS 38.213 [13], clause 7.3). | +| srs-ResourceIdList, srs-PosResourceIdList
The IDs of the SRS-Resources/SRS-PosResource used in this SRS-ResourceSet/SRS-PosResourceSet . If this SRS-ResourceSet is configured with usage set to codebook, the srs-ResourceIdList contains at most 2 entries. If this SRS-ResourceSet is configured with usage set to nonCodebook , the srs-ResourceIdList contains at most 4 entries. For SRS for positioning configuration in multiple cells srs-PosResourceIdList is commonly configured across cells within the validity area. | +| srs-ResourceSetId, srs-PosResourceSetId
The ID of this resource set. It is unique in the context of the BWP in which the parent SRS-Config is defined. For SRS for positioning configuration in multiple cells srs-PosResourceSetId is commonly configured across cells within the validity area. | +| ssb-IndexServing
Indicates SSB index belonging to a serving cell where the SRS is configured. | +| ssb-Ncell
This field indicates a SSB configuration from neighboring cell. | +| usage
Indicates if the SRS resource set is used for beam management, codebook based or non-codebook based transmission or antenna switching. See TS 38.214 [19], clause 6.2.1. Reconfiguration between codebook based and non-codebook based transmission is not supported. | +| usagePDC
If configured, it indicates that this SRS resource set is used for propagation delay compensation. The field can be present in only one SRS-ResourceSet . | + +| SRS-SpatialRelationInfoPos field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| csi-RS-IndexServing
Indicates CSI-RS index belonging to a serving cell. | +| dl-PRS
This field indicates a PRS configuration. | +| resourceSelection
Indicates whether the configured SRS spatial relation resource is a SRS-Resource or SRS-PosResource . | +| servingCellId
The serving Cell ID of the source SSB, CSI-RS, or SRS for the spatial relation of the target SRS resource. If this field is absent the SSB, the CSI-RS, or the SRS is from the same serving cell where the SRS is configured. | +| ssb-IndexServing
Indicates SSB index belonging to a serving cell. | +| ssb-Ncell
This field indicates a SSB configuration from neighboring cell. | + +| SSB-InfoNCell field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| physicalCellId
This field specifies the physical cell ID of the neighbour cell or NCD-SSB of the serving cell for which SSB configuration is provided. | +| ssb-IndexNcell
This field specifies the index of the SSB for a neighbour cell or NCD-SSB of the serving cell. See TS 38.213 [13]. If this field is absent, the UE determines the ssb-IndexNcell of the physicalCellId based on its SSB measurement from the cell. | +| ssb-Configuration
This field specifies the full configuration of the SSB. If this field is absent, the UE obtains the configuration for the SSB from nr-SSB-Config received as part of DL-PRS assistance data in LPP, see TS 37.355 [49], by looking up the corresponding SSB configuration using the field physicalCellId . | + +| DL-PRS-Info field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| dl-PRS-ID
This field specifies the UE specific TRP ID (see TS 37.355 [49]) for which PRS configuration is provided. | +| dl-PRS-ResourceSetId
This field specifies the PRS-ResourceSet ID of a PRS resourceSet. | +| dl-PRS-ResourceId
This field specifies the PRS-Resource ID of a PRS resource. If this field is absent, the UE determines the dl-PRS-ResourceID based on its PRS measurement from the TRP (see TS 37.355 [49]) and DL-PRS Resource Set. | + +| SSB-Configuration field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| halfFrameIndex
Indicates whether SSB is in the first half or the second half of the frame. Value zero indicates the first half and value 1 indicates the second half. | +| integerSubframeOffset
Indicates the subframe boundary offset of the cell in which SSB is transmitted. | +| sfn0-Offset
Indicates the time offset of the SFN0 slot 0 for the cell with respect to SFN0 slot 0 of serving cell. | + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sfn-Offset
Specifies the SFN offset between the cell in which SSB is transmitted and serving cell. The offset corresponds to the number of full radio frames counted from the beginning of a radio frame #0 of serving cell to the beginning of the closest subsequent radio frame #0 of the cell in which SSB is transmitted. | +| sfn-SSB-Offset
Indicates the SFN offset of the transmitted SSB relative to the start of the SSB period. Value 0 indicates that the SSB is transmitted in the first system frame, value 1 indicates that SSB is transmitted in the second system frame and so on. The network configures this field according to the field ssb-Periodicity such that the indicated system frame does not exceed the configured SSB periodicity. | +| ssb-Freq
Indicates the frequency of the SSB. | +| ss-PBCH-BlockPower
Average EPRE of the resources elements that carry secondary synchronization signals in dBm that the NW used for SSB transmission, see TS 38.213 [13], clause 7. | +| ssb-Periodicity
Indicates the periodicity of the SSB. If the field is absent, the UE applies the value ms5. (see TS 38.213 [13], clause 4.1) | +| ssbSubcarrierSpacing
Subcarrier spacing of SSB.
Only the following values are applicable depending on the used frequency:
FR1: 15 or 30 kHz
FR2-1: 120 or 240 kHz
FR2-2: 120, 480, or 960 kHz | + +| TxHoppingConfig field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| numberOfHops
This field specifies the number of hops. The configured values are 2,3,4,5,6. | +| overlapValue
This field specifies the overlap during SRS transmission in terms of number of resource blocks . Value zeroRB implies 0 PRB, value oneRB corresponds to 1 PRB, value twoRB corresponds to 2 PRBs and so on. The same value for the overlapValue is configured to all the hops. | +| slotOffsetForRemainingHopsList
This field specifies the starting slot offset and starting symbol for the SRS resource with tx hopping for different resource types (aperiodic, semi-persistent or periodic SRS transmission). Each hop is configured with the same periodicity. | + +| Conditional Presence | Explanation | +|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| DLorJointTCI-SRS | The field is mandatory present if srs-DLorJointTCI-State is configured, otherwise it is absent Need R. | +| FollowUTCI | The field is absent if the field followUnifiedTCI-State is present. Otherwise, it is optionally present, Need R. | +| NonCodebook | This field is optionally present, Need M, in case of non-codebook based transmission, otherwise the field is absent. | +| Pathloss | The field is mandatory present if the IE SSB-InfoNcell is included in pathlossReferenceRS-Pos ; otherwise it is optionally present, Need R | +| Setup | This field is mandatory present upon configuration of SRS-ResourceSet or SRS-Resource and optionally present, Need M, otherwise. | + +### – *SRS-PosTx-Hopping* + +The IE *SRS-PosTx-Hopping* specifies the frequency hopping configuration for SRS for Positioning transmission. + +#### *SRS-PosTx-Hopping* information element + +``` +-- ASN1START +-- TAG- SRS-PosTx-Hopping-START + +SRS-PosTx-Hopping-r18 ::= SEQUENCE { + srs-PosConfig-r18 SRS-PosConfig-r17, + bwp-r18 BWP, + srs-PosUplinkTransmissionWindowConfig-r18 SetupRelease { SRS-PosUplinkTransmissionWindowConfig-r18 } OPTIONAL -- Need M +} + +SRS-PosUplinkTransmissionWindowConfig-r18 ::= SEQUENCE { + windowPeriodicityAndOffset-r18 CHOICE { + periodicityAndOffset-r16 SRS-PeriodicityAndOffset-r16, + periodicityAndOffset-Ext-r16 SRS-PeriodicityAndOffset-Ext-r16 + }, + duration-r18 ENUMERATED {s1,s2,s4,s6}, + ... +} + +-- TAG-SRS-PosTx-Hopping-STOP +-- ASN1STOP +``` + +#### *SRS-PosUplinkTransmissionWindowConfig* field descriptions + +| | | +|------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------| +| duration | Indicates the duration of the uplink transmission window. Value s1 indicates 1 slot, s2 indicates 2 slot and so on. | +| periodicityAndOffset | Indicates the Periodicity and slot offset for uplink transmission window occurrence. | + +#### – *SRS-PosResourceSetLinkedForAggBW* + +The IE *SRS-PosResourceSetLinkedForAggBW* provides the SRS Positioning Resource Sets that are linked for bandwidth aggregation. + +#### *SRS-PosResourceSetLinkedForAggBW* information element + +``` +-- ASN1START +-- TAG- SRS-POSRESOURCESETLINKEDFORAGGBW-START + +SRS-PosResourceSetLinkedForAggBW-r18 ::= SEQUENCE { + srs-PosResourceSetLinked-r18 SRS-PosResourceSetId-r16, + freqInfo-r18 ARFCN-ValueNR OPTIONAL, -- Need R +} +``` + +``` + + ul-bwp-ID BWP-Id OPTIONAL -- Need R + } + + -- TAG- SRS-POSRESOURCESETLINKEDFORAGGBW-STOP + -- ASN1STOP + +``` + +#### ***SRS-PosResourceSetLinkedForAggBW field descriptions*** + +| | | +|----------------------------------------|----------------------------------------------------------------------------------------------------------| +| freqInfo | Indicates the SRS Positioning Resource set carrier frequency that is linked for bandwidth aggregation. | +| srs-PosResourceSetLinked | Indicates the SRS Positioning Resource set that is linked for bandwidth aggregation. | +| ul-bwp-ID | Indicates the SRS Positioning Resource set uplink bandwidth ID that is linked for bandwidth aggregation. | + +### — ***SRS-RSRP-Range*** + +The IE *SRS-RSRP-Range* specifies the value range used in SRS-RSRP measurements and thresholds. The integer value for SRS-RSRP measurements is according to Table 10.1.22.1.2-1 in TS 38.133 [14]. For thresholds, the actual value is (IE value –140) dBm, except for the IE value 98, in which case the actual value is infinity. + +#### ***SRS-RSRP-Range information element*** + +``` + +-- ASN1START +-- TAG-SRS-RSRP-RANGE-START + +SRS-RSRP-Range-r16 ::= INTEGER (0..98) + +-- TAG-SRS-RSRP-RANGE-STOP +-- ASN1STOP + +``` + +### — ***SRS-TPC-CommandConfig*** + +The IE *SRS-TPC-CommandConfig* is used to configure the UE for extracting TPC commands for SRS from a group-TPC messages on DCI + +#### ***SRS-TPC-CommandConfig information element*** + +``` + +-- ASN1START +-- TAG-SRS-TPC-COMMANDCONFIG-START + +SRS-TPC-CommandConfig ::= SEQUENCE { + startingBitOfFormat2-3 INTEGER (1..31) OPTIONAL, -- Need R + fieldTypeFormat2-3 INTEGER (0..1) OPTIONAL, -- Need R + ... +} + +``` + +``` + +startingBitOfFormat2-3SUL INTEGER (1..31) OPTIONAL -- Need R +]] +} + +-- TAG-SRS-TPC-COMMANDCONFIG-STOP +-- ASN1STOP + +``` + +#### ***SRS-TPC-CommandConfig* field descriptions** + +##### ***fieldTypeFormat2-3*** + +The type of a field within the group DCI with SRS request fields (optional), which indicates how many bits in the field are for SRS request (0 or 2). + +Note that for Type A, there is a common SRS request field for all SCells in the set, but each SCell has its own TPC command bits. See TS 38.212 [17] clause 7.3.1 and , TS 38.213 [13], clause 11.3. + +##### ***startingBitOfFormat2-3*** + +The starting bit position of a block within the group DCI with SRS request fields (optional) and TPC commands. The value 1 of the field corresponds to the first/left most bit of format2-3. The value 2 of the field corresponds to the second bit format2-3, and so on (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 11.3). + +##### ***startingBitOfFormat2-3SUL*** + +The starting bit position of a block within the group DCI with SRS request fields (optional) and TPC commands for SUL carrier (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 11.3). + +### — ***SSB-Index*** + +The IE *SSB-Index* identifies an SS-Block within an SS-Burst. See TS 38.213 [13], clause 4.1. + +#### ***SSB-Index* information element** + +``` + +-- ASN1START +-- TAG-SSB-INDEX-START + +SSB-Index ::= INTEGER (0..maxNrofSSBs-1) + +-- TAG-SSB-INDEX-STOP +-- ASN1STOP + +``` + +### — ***SSB-MTC*** + +The IE *SSB-MTC* is used to configure measurement timing configurations, i.e., timing occasions at which the UE measures SSBs. + +#### ***SSB-MTC* information element** + +``` + +-- ASN1START +-- TAG-SSB-MTC-START + +SSB-MTC ::= SEQUENCE { + +``` + +``` + +periodicityAndOffset CHOICE { + sf5 INTEGER (0..4), + sf10 INTEGER (0..9), + sf20 INTEGER (0..19), + sf40 INTEGER (0..39), + sf80 INTEGER (0..79), + sf160 INTEGER (0..159) +}, +duration ENUMERATED { sf1, sf2, sf3, sf4, sf5 } +} + +SSB-MTC2 ::= SEQUENCE { + pci-List SEQUENCE (SIZE (1..maxNrofPCIsPerSMTC)) OF PhysCellId OPTIONAL, -- Need M + periodicity ENUMERATED {sf5, sf10, sf20, sf40, sf80, spare3, spare2, spare1} +} + +SSB-MTC2-LP-r16 ::= SEQUENCE { + pci-List SEQUENCE (SIZE (1..maxNrofPCIsPerSMTC)) OF PhysCellId OPTIONAL, -- Need R + periodicity ENUMERATED {sf10, sf20, sf40, sf80, sf160, spare3, spare2, spare1} +} + +SSB-MTC3-r16 ::= SEQUENCE { + periodicityAndOffset-r16 CHOICE { + sf5-r16 INTEGER (0..4), + sf10-r16 INTEGER (0..9), + sf20-r16 INTEGER (0..19), + sf40-r16 INTEGER (0..39), + sf80-r16 INTEGER (0..79), + sf160-r16 INTEGER (0..159), + sf320-r16 INTEGER (0..319), + sf640-r16 INTEGER (0..639), + sf1280-r16 INTEGER (0..1279) + }, + duration-r16 ENUMERATED {sf1, sf2, sf3, sf4, sf5}, + pci-List-r16 SEQUENCE (SIZE (1..maxNrofPCIsPerSMTC)) OF PhysCellId OPTIONAL, -- Need M + ssb-ToMeasure-r16 SetupRelease { SSB-ToMeasure } OPTIONAL -- Need M +} + +SSB-MTC4-r17 ::= SEQUENCE { + pci-List-r17 SEQUENCE (SIZE (1..maxNrofPCIsPerSMTC)) OF PhysCellId OPTIONAL, -- Need M + offset-r17 INTEGER (0..159) +} + +SSB-MTC-AdditionalPCI-r17 ::= SEQUENCE { + additionalPCIIndex-r17 AdditionalPCIIndex-r17, + additionalPCI-r17 PhysCellId, + periodicity-r17 ENUMERATED { ms5, ms10, ms20, ms40, ms80, ms160, spare2, spare1 }, + ssb-PositionsInBurst-r17 CHOICE { + shortBitmap BIT STRING (SIZE (4)), + mediumBitmap BIT STRING (SIZE (8)), + longBitmap BIT STRING (SIZE (64)) + } +} + +``` + +``` + + }, + ss-PBCH-BlockPower-r17 INTEGER (-60..50) +} + +AdditionalPCIIndex-r17 ::= INTEGER(1..maxNrofAdditionalPCI-r17) + +-- TAG-SSB-MTC-STOP +-- ASN1STOP + +``` + +#### | SSB-MTC field descriptions | |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | duration
Duration of the measurement window in which to receive SS/PBCH blocks. It is given in number of subframes (see TS 38.213 [13], clause 4.1). | | periodicityAndOffset
Periodicity and offset of the measurement window in which to receive SS/PBCH blocks, see 5.5.2.10. Periodicity and offset are given in number of subframes. | + +#### | SSB-MTC2 field descriptions | |-------------------------------------------------------| | pci-List
PCIs that follow this SMTC. | + +#### | SSB-MTC3 field descriptions | |----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | duration
Duration of the measurement window in which to receive SS/PBCH blocks. It is given in number of subframes (see TS 38.213 [13], clause 4.1). | | pci-List
PCIs that follow this SMTC, used for IAB-node discovery. | | periodicityAndOffset
Periodicity and offset of the measurement window in which to receive SS/PBCH blocks, see 5.5.2.10. Periodicity and offset are given in number of subframes. | | ssb-ToMeasure
The set of SS blocks to be measured within the SMTC measurement duration. The first/leftmost bit corresponds to SS block index 0, the second bit corresponds to SS block index 1, and so on. Value 0 in the bitmap indicates that the corresponding SS block is not to be measured while value 1 indicates that the corresponding SS block is to be measured (see TS 38.215 [9]). When the field is not configured the IAB-MT measures on all SS blocks. Regardless of the value of this field, SS blocks outside of the applicable smtc are not to be measured. See TS 38.215 [9] clause 5.1.1. | + +#### | SSB-MTC4 field descriptions | |----------------------------------------------------------------------------------------------------------------------------------------------------| | pci-List
PCIs that follow this SMTC. | | offset
Offset of the measurement window in which to receive SS/PBCH blocks, see 5.5.2.10. Offset is given in number of subframes. | + +| SSB-MTC-AdditionalPCI field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| additionalPCI
PCI of the additional SSB different from serving cell PCI. | +| periodicity
Periodicity of the SS/PBCH blocks, see 5.5.2.10. Periodicity is given in number of subframes. | +| ssb-PositionsInBurst
Indicates the time domain positions of the transmitted SS-blocks in a half frame with SS/PBCH blocks as defined in TS 38.213 [13], clause 4.1. The first/leftmost bit corresponds to SS/PBCH block index 0, the second bit corresponds to SS/PBCH block index 1, and so on. Value 0 in the bitmap indicates that the corresponding SS/PBCH block is not transmitted while value 1 indicates that the corresponding SS/PBCH block is transmitted. | +| ss-PBCH-BlockPower
Average EPRE of the resources elements that carry secondary synchronization signals in dBm that the NW used for SSB transmission, see TS 38.213 [13], clause 7. | + +### — ***SSB-PositionQCL-Relation*** + +The IE *SSB-PositionQCL-Relation* is used to indicate the QCL relationship between SSB positions on the frequency indicated by *ssbFrequency* (see TS 38.213 [13], clause 4.1) for operation with shared spectrum channel access. Value n1 corresponds to 1, value n2 corresponds to 2 and so on. + +#### ***SSB-PositionQCL-Relation* information element** + +``` +-- ASN1START +-- TAG-SSB-POSITIONQCL-RELATION-START + +SSB-PositionQCL-Relation-r16 ::= ENUMERATED {n1,n2,n4,n8} + +SSB-PositionQCL-Relation-r17 ::= ENUMERATED {n32, n64} + +-- TAG-SSB-POSITIONQCL-RELATION-STOP +-- ASN1STOP +``` + +### — ***SSB-ToMeasure*** + +The IE *SSB-ToMeasure* is used to configure a pattern of SSBs. For operation with shared spectrum channel access in FR1, only *mediumBitmap* is used, and for FR2-2, *longBitmap* is used. + +#### ***SSB-ToMeasure* information element** + +``` +-- ASN1START +-- TAG-SSB-TOMEASURE-START + +SSB-ToMeasure ::= CHOICE { + shortBitmap BIT STRING (SIZE (4)), + mediumBitmap BIT STRING (SIZE (8)), + longBitmap BIT STRING (SIZE (64)) +} +``` + +``` +-- TAG-SSB-TOMEASURE-STOP +-- ASN1STOP +``` + +#### SSB-ToMeasure field descriptions + +##### **longBitmap** + +Bitmap when maximum number of SS/PBCH blocks per half frame equals to 64 as defined in TS 38.213 [13], clause 4.1. For operation with shared spectrum channel access in FR2-2, if the k-th bit is set to 1, the UE assumes that one or more SS/PBCH blocks within the SMTC measurement duration with candidate SS/PBCH block indexes corresponding to SS/PBCH block index equal to $(k-1)$ may be transmitted; if the k-th bit is set to 0, the UE assumes that the corresponding SS/PBCH block(s) are not transmitted. + +##### **mediumBitmap** + +Bitmap when maximum number of SS/PBCH blocks per half frame equals to 8 as defined in TS 38.213 [13], clause 4.1. For operation with shared spectrum channel access, if the k-th bit is set to 1, the UE assumes that one or more SS/PBCH blocks within the SMTC measurement duration with candidate SS/PBCH block indexes corresponding to SS/PBCH block index equal to $k-1$ may be transmitted; if the k-th bit is set to 0, the UE assumes that the corresponding SS/PBCH block(s) are not transmitted. The k-th bit is set to 0, where $k > \text{ssb-PositionQCL-Common}$ and the number of actually transmitted SS/PBCH blocks is not larger than the number of 1's in the bitmap. If *ssb-PositionQCL* is configured with a value smaller than *ssb-PositionQCL-Common*, only the leftmost K bits ( $K = \text{ssb-PositionQCL}$ ) are applicable for the corresponding cell. + +##### **shortBitmap** + +Bitmap when maximum number of SS/PBCH blocks per half frame equals to 4 as defined in TS 38.213 [13], clause 4.1. + +### SS-RSSI-Measurement + +The IE *SS-RSSI-Measurement* is used to configure RSSI measurements based on synchronization reference signals. + +#### SS-RSSI-Measurement information element + +``` +-- ASN1START +-- TAG-SS-RSSI-MEASUREMENT-START + +SS-RSSI-Measurement ::= SEQUENCE { + measurementSlots BIT STRING (SIZE (1..80)), + endSymbol INTEGER (0..3) +} + +-- TAG-SS-RSSI-MEASUREMENT-STOP +-- ASN1STOP +``` + +| SS-RSSI-Measurement field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| endSymbol
Within a slot that is configured for RSSI measurements (see measurementSlots ) the UE measures the RSSI from symbol 0 to symbol endSymbol . This field identifies the entry in Table 5.1.3-1 in TS 38.215 [9], which determines the actual end symbol. | +| measurementSlots
Indicates the slots in which the UE can perform RSSI measurements. The length of the BIT STRING is equal to the number of slots in the configured SMTC window (determined by the duration and by the subcarrierSpacing). The first (left-most / most significant) bit in the bitmap corresponds to the first slot in the SMTC window, the second bit in the bitmap corresponds to the second slot in the SMTC window, and so on. The UE measures in slots for which the corresponding bit in the bitmap is set to 1. In case this field is configured for a SCell with ca-SlotOffset-r16 , the bits in the bitmap corresponds to the slots that are fully contained in the SMTC window. | + +#### SubcarrierSpacing + +The IE *SubcarrierSpacing* determines the subcarrier spacing. Restrictions applicable for certain frequencies, channels or signals are clarified in the fields that use this IE. + +#### SubcarrierSpacing information element + +``` +-- ASN1START +-- TAG-SUBCARRIERSPACING-START + +SubcarrierSpacing ::= + ENUMERATED {kHz15, kHz30, kHz60, kHz120, kHz240, kHz480-v1700, kHz960-v1700, spare1} + +-- TAG-SUBCARRIERSPACING-STOP +-- ASN1STOP +``` + +### TAG-Config + +The IE *TAG-Config* is used to configure parameters for a time-alignment group. + +#### TAG-Config information element + +``` +-- ASN1START +-- TAG-TAG-CONFIG-START + +TAG-Config ::= + SEQUENCE { + tag-ToReleaseList + SEQUENCE (SIZE (1..maxNrofTAGs)) OF TAG-Id + OPTIONAL, -- Need N + tag-ToAddModList + SEQUENCE (SIZE (1..maxNrofTAGs)) OF TAG + OPTIONAL, -- Need N + } + +TAG ::= + SEQUENCE { + tag-Id + TAG-Id, + timeAlignmentTimer + TimeAlignmentTimer, + ... + } + +TAG-Id ::= + INTEGER (0..maxNrofTAGs-1) +``` + +``` +-- TAG-TAG-CONFIG-STOP +-- ASN1STOP +``` + +| TAG field descriptions | | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| tag-Id | Indicates the TAG of the SpCell or an SCell, see TS 38.321 [3]. Uniquely identifies the TAG within the scope of a Cell Group (i.e. MCG or SCG). | +| timeAlignmentTimer | The timeAlignmentTimer for TAG with ID tag-Id , as specified in TS 38.321 [3]. | + +### – TAR-Config + +The IE *TAR-Config* is used to configure Timing Advance reporting in non-terrestrial networks and ATG network. + +#### TAR-Config information element + +``` +-- ASN1START +-- TAG-TAR-CONFIG-START + +TAR-Config-r17 ::= + SEQUENCE { + offsetThresholdTA-r17 ENUMERATED {ms0dot5, ms1, ms2, ms3, ms4, ms5, ms6 ,ms7, ms8, ms9, ms10, ms11, ms12, + ms13, ms14, ms15, spare13, spare12, spare11, spare10, spare9, spare8, spare7, + spare6, spare5, spare4, spare3, spare2, spare1} OPTIONAL, -- Need R + timingAdvanceSR-r17 ENUMERATED {enabled} OPTIONAL, -- Need R + ... + } + +TAR-Config-r18 ::= + SEQUENCE { + offsetThresholdTA-r18 INTEGER (1..56) OPTIONAL, -- Need R + timingAdvanceSR-r18 ENUMERATED {enabled} OPTIONAL, -- Need R + ... + } + +-- TAG-TAR-CONFIG-STOP +-- ASN1STOP +``` + +| TAR-Config field descriptions | | +|-------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| offsetThresholdTA | Offset for TA reporting as specified in TS 38.321 [3]. Network only configures this parameter for MCG. For ATG, network only configures offsetThresholdTA-r18 in unit of symbols | +| timingAdvanceSR | Used to configure whether a Timing Advance report may trigger a Scheduling Request as specified in TS 38.321 [3]. | + +### – *TCI-ActivatedConfig* + +The IE *TCI-ActivatedConfig* is used to provide activated TCI states for PDSCH and/or PDCCH of the PSCell or of an SCell. + +#### *TCI-ActivatedConfig* information element + +``` +-- ASN1START +-- TAG-TCI-ACTIVATEDCONFIG-START + +TCI-ActivatedConfig-r17 ::= SEQUENCE { + pdcch-TCI-r17 SEQUENCE (SIZE (1..5)) OF TCI-StateId, + pdsch-TCI-r17 BIT STRING (SIZE (1..maxNrofTCI-States)) +} + +-- TAG-TCI-ACTIVATEDCONFIG-STOP +-- ASN1STOP +``` + +#### *TCI-ActivatedConfig* field descriptions + +##### ***pdcch-TCI*** + +Indicates the TCI state for PDCCH for each configured CORESET of the DL BWP to be activated at SCell activation, to be activated for the PSCell at SCG activation and/or to be used for BFD, RLM and measurements while the SCG is deactivated. The list includes exactly as many entries as CORESETs configured in this BWP, ordered by increasing values of *ControlResourceSet-Id*, i.e. the first entry indicates the TCI state for the configured CORESET with the lowest *ControlResourceSet-Id* value, the second value indicates the TCI states for the configured CORESET with the second lowest *ControlResourceSet-Id* value, and so on. + +##### ***pdsch-TCI*** + +Indicates TCI states for PDSCH reception at SCell addition/activation or of the PSCell at SCG activation. This field indicates activated TCI state(s) for this BWP ordered by increasing values of *TCI-StateId*, i.e. the first bit indicates the activation state of the TCI state with the lowest *TCI-StateId* value, the second value indicates the activation status of the TCI state with the second lowest *TCI-StateId* value, and so on. A bit set to 0 indicates that the corresponding TCI state is deactivated, a bit set to 1 indicates that the TCI state is activated. + +### – *TCI-State* + +The IE *TCI-State* associates one or two DL reference signals with a corresponding quasi-co-location (QCL) type. + +#### *TCI-State* information element + +``` +-- ASN1START +-- TAG-TCI-STATE-START + +TCI-State ::= SEQUENCE { + tci-StateId TCI-StateId, + qcl-Type1 QCL-Info, + qcl-Type2 QCL-Info OPTIONAL, -- Need R + ... +} +``` + +``` + + additionalPCI-r17 AdditionalPCIIndex-r17 OPTIONAL, -- Need R + pathlossReferenceRS-Id-r17 PathlossReferenceRS-Id-r17 OPTIONAL, -- Cond JointTCI1 + ul-powerControl-r17 Uplink-powerControlId-r17 OPTIONAL -- Cond JointTCI + ], + [[ + tag-Id-ptr-r18 ENUMERATED {n0,n1} OPTIONAL -- Cond 2TA + ]] +} + +QCL-Info ::= SEQUENCE { + cell ServCellIndex OPTIONAL, -- Need R + bwp-Id BWP-Id OPTIONAL, -- Cond CSI-RS-Indicated + referenceSignal CHOICE { + csi-rs NZP-CSI-RS-ResourceId, + ssb SSB-Index + }, + qcl-Type ENUMERATED {typeA, typeB, typeC, typeD}, + ... +} + +-- TAG-TCI-STATE-STOP +-- ASN1STOP + +``` + +| QCL-Info field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| bwp-Id
The DL BWP which the RS is located in. If the field is absent, the RS is located in the DL BWP in which the TCI-State is applied by the UE. | +| cell
The UE's serving cell in which the referenceSignal is configured. If the field is absent, the referenceSignal is configured in the serving cell in which the TCI-State is applied by the UE. The RS can be located on a serving cell other than the serving cell for which the TCI-State is applied by the UE only if the qcl-Type is configured as typeC or typeD . If the referenceSignal is set to csi-rs and unifiedTCI-StateType is configured, either both cell and bwp-Id are present or both cell and bwp-Id are absent. See TS 38.214 [19] clause 5.1.5. | +| referenceSignal
Reference signal with which quasi-collocation information is provided as specified in TS 38.214 [19] clause 5.1.5. | +| qcl-Type
QCL type as specified in TS 38.214 [19] clause 5.1.5. | + +| TCI-State field descriptions | | +|-------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| additionalPCI | Indicates the physical cell IDs (PCI) of the SSBs when referenceSignal is configured as SSB for both QCL-Type1 and QCL-Type2. In case the cell is present, the additionalPCI refers to a PCI value configured in the list configured using additionalPCI-ToAddModList in the serving cell indicated by the field cell . Otherwise, it refers to a PCI value configured in a list additionalPCI-ToAddModList configured in the serving cell where the TCI-State is applied by the UE. When this field is present the cell for qcl-Type1 and qcl-Type2 is configured with same value, if present. | +| pathlossReferenceRS-id | The ID of the reference signal (e.g. a CSI-RS or an SS block) used for PUSCH, PUCCH and SRS path loss estimation. This field refers to an element in the list configured using pathlossReferenceRSToAddModList in the serving cell and UL BWP where the TCI State is applied by the UE. | +| qcl-Type1, qcl-Type2 | QCL information for the TCI state as specified in TS 38.214 [19] clause 5.1.5. | +| tag-ld-ptr | It indicates the TAG that is associated with this TCI state, value n0 means the TCI state associate with the TAG indicated by tag-ld , value n1 means this TCI state associated with the TAG indicated by tag2-ld . The tag_id_ptr refers to the TAG of the serving cell where the TCI state is applied. | +| tci-StateId | ID number of the TCI state. | +| ul-PowerControl | Configures power control parameters for PUCCH, PUSCH and SRS for this TCI state. The field is present here only if ul-powerControl is not configured in any BWP-Uplink-Dedicated of this serving cell. This field refers to an element in the list configured using uplink-PowerControlToAddModList in the serving cell where the dl-OrJointTCI-StateToAddModList is configured. | + +| Conditional Presence | Explanation | +|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 2TA | This field is mandatory present if tag2 is present for the serving cell. It is absent, Need R, otherwise. | +| CSI-RS-Indicated | This field is mandatory present if csi-rs is included and unifiedTCI-StateType is not configured. This field is optionally present, Need R, if csi-rs is included and unifiedTCI-StateType is configured. Otherwise, it is absent, Need R. | +| JointTCI | This field is optionally present, Need R, if this serving cell is configured with unifiedTCI-StateType set to 'joint'. It is absent, Need R, otherwise. | +| JointTCI1 | This field is mandatory present, if this serving cell is configured with unifiedTCI-StateType set to 'joint'. It is absent, Need R, otherwise. | + +#### TCI-StateId + +The IE *TCI-StateId* is used to identify one *TCI-State* configuration. + +#### TCI-StateId information element + +``` +-- ASN1START +-- TAG-TCI-STATEID-START + +TCI-StateId ::= + INTEGER (0..maxNrofTCI-States-1) + +-- TAG-TCI-STATEID-STOP +-- ASN1STOP +``` + +### – *TCI-UL-State* + +The IE *TCI-UL-State* indicates the TCI state information for UL transmission. + +#### *TCI-UL-State* information element + +``` +-- ASN1START +-- TAG-TCI-UL-STATE-START + +TCI-UL-State-r17 ::= SEQUENCE { + tci-UL-StateId-r17 TCI-UL-StateId-r17, + servingCellId-r17 ServCellIndex OPTIONAL, -- Need R + bwp-Id-r17 BWP-Id OPTIONAL, -- Cond CSI-RSorSRS-Indicated + referenceSignal-r17 CHOICE { + ssb-Index-r17 SSB-Index, + csi-RS-Index-r17 NZP-CSI-RS-ResourceId, + srs-r17 SRS-ResourceId + }, + additionalPCI-r17 AdditionalPCIIndex-r17 OPTIONAL, -- Need R + ul-powerControl-r17 Uplink-powerControlId-r17 OPTIONAL, -- Need R + pathlossReferenceRS-Id-r17 PathlossReferenceRS-Id-r17 OPTIONAL, -- Cond Mandatory + ... + [[ + tag-Id-ptr-r18 ENUMERATED {n0,n1} OPTIONAL -- Cond 2TA + ]] +} + +-- TAG-TCI-UL-STATE-STOP +-- ASN1STOP +``` + +| TCI-UL-State field descriptions | | +|----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| additionalPCI | Indicates the physical cell IDs (PCI) of the SSBs when referenceSignal is configured as SSB. In case the servingCellId is present, the additionalPCI refers to a PCI value configured in the list configured using additionalPCI-ToAddModList in the serving cell indicated by the field servingCellId . Otherwise, it refers to a PCI value configured in the list configured using additionalPCI-ToAddModList in the serving cell where the ul-TCI-StateList is applied by the UE. | +| bwp-Id | The DL BWP which the CSI-RS is located in or UL BWP where the SRS is located in. | +| servingCellId | The UE's serving cell in which the referenceSignal is configured. If the field is absent, the referenceSignal is configured in the serving cell in which the TCI-UL-State is applied by the UE. | +| pathlossReferenceRS-Id | The ID of the reference Signal (e.g. a CSI-RS or a SS block) used for PUSCH, PUCCH and SRS path loss estimation. This field refers to an element in the list configured using pathlossReferenceRSToAddModList in the serving cell and UL BWP where the UL TCI State is applied by the UE. | +| tag-Id-ptr | It indicates the TAG that is associated with this TCI state, value n0 means the TCI state associate with the TAG indicated by tag-Id , value n1 means this TCI state associated with the TAG indicated by tag2-Id . The tag_id_ptr refers to the TAG of the serving cell where the TCI state is applied. | +| ul-powerControl | Configures power control parameters for PUCCH, PUSCH and SRS for this TCI state. The field is present here only if ul-powerControl is not configured in any BWP-Uplink-Dedicated of this serving cell. This field refers to an element in the list configured using uplink-PowerControlToAddModList in the serving cell where the ul-TCI-ToAddModList is configured. | + +| Conditional Presence | Explanation | +|------------------------------|-----------------------------------------------------------------------------------------------------------------------------| +| 2TA | This field is mandatory present if tag2 is present for the serving cell. It is absent, Need R, otherwise. | +| CSI-RSorSRS-Indicated | This field is mandatory present if referenceSignal is set to csi-RS-index or to srs , absent otherwise | +| Mandatory | The field is mandatory present. | + +### — *TCI-UL-StateId* + +The IE *TCI-UL-StateId* is used to identify one *TCI-UL-State* configuration. + +#### ***TCI-UL-StateId* information element** + +``` +-- ASN1START +-- TAG-TCI-UL-STATEID-START + +TCI-UL-StateId-r17 ::= INTEGER (0..maxUL-TCI-1-r17) + +-- TAG-TCI-UL-STATEID-STOP +-- ASN1STOP +``` + +#### TDD-UL-DL-ConfigCommon + +The IE *TDD-UL-DL-ConfigCommon* determines the cell specific Uplink/Downlink TDD configuration. + +#### TDD-UL-DL-ConfigCommon information element + +``` +-- ASN1START +-- TAG-TDD-UL-DL-CONFIGCOMMON-START + +TDD-UL-DL-ConfigCommon ::= SEQUENCE { + referenceSubcarrierSpacing SubcarrierSpacing, + pattern1 TDD-UL-DL-Pattern, + pattern2 TDD-UL-DL-Pattern, + ... OPTIONAL, -- Need R +} + +TDD-UL-DL-Pattern ::= SEQUENCE { + dl-UL-TransmissionPeriodicity ENUMERATED {ms0p5, ms0p625, ms1, ms1p25, ms2, ms2p5, ms5, ms10}, + nrofDownlinkSlots INTEGER (0..maxNrofSlots), + nrofDownlinkSymbols INTEGER (0..maxNrofSymbols-1), + nrofUplinkSlots INTEGER (0..maxNrofSlots), + nrofUplinkSymbols INTEGER (0..maxNrofSymbols-1), + ... + [[ + dl-UL-TransmissionPeriodicity-v1530 ENUMERATED {ms3, ms4} OPTIONAL -- Need R + ]] +} + +-- TAG-TDD-UL-DL-CONFIGCOMMON-STOP +-- ASN1STOP +``` + +#### TDD-UL-DL-ConfigCommon field descriptions + +##### ***referenceSubcarrierSpacing*** + +Reference SCS used to determine the time domain boundaries in the UL-DL pattern which must be common across all subcarrier specific carriers, i.e., independent of the actual subcarrier spacing using for data transmission. + +Only the following values are applicable depending on the used frequency: + +FR1: 15, 30, or 60 kHz + +FR2-1: 60 or 120 kHz + +FR2-2: 120, 480, or 960 kHz + +The network configures a not larger than any SCS of configured BWPs for the serving cell. The network or *SL-PreconfigGeneral* configures a not larger than the SCS of (pre-)configured SL BWP. See TS 38.213 [13], clause 11.1. + +| TDD-UL-DL-Pattern field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| dl-UL-TransmissionPeriodicity
Periodicity of the DL-UL pattern, see TS 38.213 [13], clause 11.1. If the dl-UL-TransmissionPeriodicity-v1530 is signalled, UE shall ignore the dl-UL-TransmissionPeriodicity (without suffix). | +| nrofDownlinkSlots
Number of consecutive full DL slots at the beginning of each DL-UL pattern, see TS 38.213 [13], clause 11.1. In this release, the maximum value for this field is 320. | +| nrofDownlinkSymbols
Number of consecutive DL symbols in the beginning of the slot following the last full DL slot (as derived from nrofDownlinkSlots ). The value 0 indicates that there is no partial-downlink slot. (see TS 38.213 [13], clause 11.1). | +| nrofUplinkSlots
Number of consecutive full UL slots at the end of each DL-UL pattern, see TS 38.213 [13], clause 11.1. In this release, the maximum value for this field is 320. | +| nrofUplinkSymbols
Number of consecutive UL symbols in the end of the slot preceding the first full UL slot (as derived from nrofUplinkSlots ). The value 0 indicates that there is no partial-uplink slot. (see TS 38.213 [13], clause 11.1). | + +#### – TDD-UL-DL-ConfigDedicated + +The IE *TDD-UL-DL-ConfigDedicated* determines the UE-specific Uplink/Downlink TDD configuration. + +#### TDD-UL-DL-ConfigDedicated information element + +``` +-- ASN1START +-- TAG-TDD-UL-DL-CONFIGDEDICATED-START + +TDD-UL-DL-ConfigDedicated ::= SEQUENCE { + slotSpecificConfigurationsToAddModList SEQUENCE (SIZE (1..maxNrofSlots)) OF TDD-UL-DL-SlotConfig OPTIONAL, -- Need N + slotSpecificConfigurationsToReleaseList SEQUENCE (SIZE (1..maxNrofSlots)) OF TDD-UL-DL-SlotIndex OPTIONAL, -- Need N + ... +} + +TDD-UL-DL-ConfigDedicated-IAB-MT-r16 ::= SEQUENCE { + slotSpecificConfigurationsToAddModList-IAB-MT-r16 SEQUENCE (SIZE (1..maxNrofSlots)) OF TDD-UL-DL-SlotConfig-IAB-MT-r16 OPTIONAL, -- Need N + slotSpecificConfigurationsToReleaseList-IAB-MT-r16 SEQUENCE (SIZE (1..maxNrofSlots)) OF TDD-UL-DL-SlotIndex OPTIONAL, -- Need N + ... +} + +TDD-UL-DL-SlotConfig ::= SEQUENCE { + slotIndex TDD-UL-DL-SlotIndex, + symbols CHOICE { + allDownlink NULL, + allUplink NULL, + explicit SEQUENCE { + nrofDownlinkSymbols INTEGER (1..maxNrofSymbols-1) OPTIONAL, -- Need S + nrofUplinkSymbols INTEGER (1..maxNrofSymbols-1) OPTIONAL, -- Need S + } + } +} +``` + +``` + +} + +TDD-UL-DL-SlotConfig-IAB-MT-r16 ::= SEQUENCE { + slotIndex-r16 TDD-UL-DL-SlotIndex, + symbols-IAB-MT-r16 CHOICE { + allDownlink-r16 NULL, + allUplink-r16 NULL, + explicit-r16 SEQUENCE { + nrofDownlinkSymbols-r16 INTEGER (1..maxNrofSymbols-1) OPTIONAL, -- Need S + nrofUplinkSymbols-r16 INTEGER (1..maxNrofSymbols-1) OPTIONAL, -- Need S + }, + explicit-IAB-MT-r16 SEQUENCE { + nrofDownlinkSymbols-r16 INTEGER (1..maxNrofSymbols-1) OPTIONAL, -- Need S + nrofUplinkSymbols-r16 INTEGER (1..maxNrofSymbols-1) OPTIONAL, -- Need S + } + } +} + +TDD-UL-DL-SlotIndex ::= INTEGER (0..maxNrofSlots-1) + +-- TAG-TDD-UL-DL-CONFIGDEDICATED-STOP +-- ASN1STOP + +``` + +#### | TDD-UL-DL-ConfigDedicated field descriptions | |-----------------------------------------------------| |-----------------------------------------------------| + +##### | | |-----------------------------------------------| | slotSpecificConfigurationsToAddModList | |-----------------------------------------------| + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| The slotSpecificConfigurationToAddModList allows overriding UL/DL allocations provided in tdd-UL-DL-configurationCommon , see TS 38.213 [13], clause 11.1. | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +#### | TDD-UL-DL-ConfigDedicated-IAB-MT field descriptions | |------------------------------------------------------------| |------------------------------------------------------------| + +##### | | |------------------------------------------------------| | slotSpecificConfigurationsToAddModList-IAB-MT | |------------------------------------------------------| + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| The slotSpecificConfigurationToAddModList-IAB-MT allows overriding UL/DL allocations provided in tdd-UL-DL-configurationCommon with a limitation that effectively only flexible symbols can be overwritten in Rel-16. | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +##### | | |-------------------------------------------------------| | slotSpecificConfigurationsToReleaseList-IAB-MT | |-------------------------------------------------------| + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| The slotSpecificConfigurationsToReleaseList-IAB-MT allows release of a set of slot configuration previously add with slotSpecificConfigurationToAddModList-IAB-MT . | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| TDD-UL-DL-SlotConfig field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| nrofDownlinkSymbols
Number of consecutive DL symbols in the beginning of the slot identified by slotIndex . If the field is absent the UE assumes that there are no leading DL symbols. (see TS 38.213 [13], clause 11.1). | +| nrofUplinkSymbols
Number of consecutive UL symbols in the end of the slot identified by slotIndex . If the field is absent the UE assumes that there are no trailing UL symbols. (see TS 38.213 [13], clause 11.1). | +| slotIndex
Identifies a slot within a slot configuration period given in tdd-UL-DL-configurationCommon , see TS 38.213 [13], clause 11.1. | +| symbols
The direction (downlink or uplink) for the symbols in this slot. Value allDownlink indicates that all symbols in this slot are used for downlink; value allUplink indicates that all symbols in this slot are used for uplink; value explicit indicates explicitly how many symbols in the beginning and end of this slot are allocated to downlink and uplink, respectively. | + +| TDD-UL-DL-SlotConfig-IAB-MT field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| symbols-IAB-MT
The symbols-IAB-MT is used to configure an IAB-MT with the SlotConfig applicable for one serving cell. Value allDownlink indicates that all symbols in this slot are used for downlink; value allUplink indicates that all symbols in this slot are used for uplink; value explicit indicates explicitly how many symbols in the beginning and end of this slot are allocated to downlink and uplink, respectively; value explicit-IAB-MT indicates explicitly how many symbols in the beginning and end of this slot are allocated to uplink and downlink, respectively. | + +### — *TrackingAreaCode* + +The IE *TrackingAreaCode* is used to identify a tracking area within the scope of a PLMN/SNPN, see TS 24.501 [23]. + +#### ***TrackingAreaCode* information element** + +``` +-- ASN1START +-- TAG-TRACKINGAREACODE-START + +TrackingAreaCode ::= BIT STRING (SIZE (24)) + +-- TAG-TRACKINGAREACODE-STOP +-- ASN1STOP +``` + +### — *T-Reselection* + +The IE *T-Reselection* concerns the cell reselection timer *TreselectionRAT* for NR and E-UTRA. Value in seconds. For value 0, behaviour as specified in 7.1.2 applies. + +#### ***T-Reselection* information element** + +``` +-- ASN1START +``` + +``` +-- TAG-TRESELECTION-START + +T-Reselection ::= INTEGER (0..7) + +-- TAG-TRESELECTION-STOP +-- ASN1STOP +``` + +### — *TimeAlignmentTimer* + +The IE *TimeAlignmentTimer* is used to configure the time alignment timer as specified in TS 38.321 [3]. The values are in ms. + +#### ***TimeAlignmentTimer* information element** + +``` +-- ASN1START +-- TAG-TIMEALIGNMENTTIMER-START + +TimeAlignmentTimer ::= ENUMERATED {ms500, ms750, ms1280, ms1920, ms2560, ms5120, ms10240, infinity} + +-- TAG-TIMEALIGNMENTTIMER-STOP +-- ASN1STOP +``` + +### — *TimeToTrigger* + +The IE *TimeToTrigger* specifies the value range used for time to trigger parameter, which concerns the time during which specific criteria for the event needs to be met in order to trigger a measurement report. Value *ms0* corresponds to 0 ms and behaviour as specified in 7.1.2 applies, value *ms40* corresponds to 40 ms, and so on. + +#### ***TimeToTrigger* information element** + +``` +-- ASN1START +-- TAG-TIMETOTRIGGER-START + +TimeToTrigger ::= ENUMERATED { + ms0, ms40, ms64, ms80, ms100, ms128, ms160, ms256, + ms320, ms480, ms512, ms640, ms1024, ms1280, ms2560, + ms5120} + +-- TAG-TIMETOTRIGGER-STOP +-- ASN1STOP +``` + +### — *TN-AreaId* + +The IE *TN-AreaId* is used to identify a TN coverage area in an NTN system. + +#### TN-AreaId information element + +``` +-- ASN1START +-- TAG-TN-AREAID-START + +TN-AreaId-r18 ::= INTEGER (1..maxTN-AreaInfo-r18) + +-- TAG-TN-AREAID-STOP +-- ASN1STOP +``` + +### – UAC-BarringInfoSetIndex + +The IE *UAC-BarringInfoSetIndex* provides the index of the entry in *uac-BarringInfoSetList*. Value 1 corresponds to the first entry in *uac-BarringInfoSetList*, value 2 corresponds to the second entry in this list and so on. An index value referring to an entry not included in *uac-BarringInfoSetList* indicates no barring. + +#### UAC-BarringInfoSetIndex information element + +``` +-- ASN1START +-- TAG-UAC-BARRINGINFOSETINDEX-START + +UAC-BarringInfoSetIndex ::= INTEGER (1..maxBarringInfoSet) + +-- TAG-UAC-BARRINGINFOSETINDEX-STOP +-- ASN1STOP +``` + +### – UAC-BarringInfoSetList + +The IE *UAC-BarringInfoSetList* provides a list of access control parameter sets. An access category can be configured with access parameters according to one of the sets. + +#### UAC-BarringInfoSetList information element + +``` +-- ASN1START +-- TAG-UAC-BARRINGINFOSETLIST-START + +UAC-BarringInfoSetList ::= SEQUENCE (SIZE(1..maxBarringInfoSet)) OF UAC-BarringInfoSet +UAC-BarringInfoSetList-v1700 ::= SEQUENCE (SIZE(1..maxBarringInfoSet)) OF UAC-BarringInfoSet-v1700 +UAC-BarringInfoSet ::= SEQUENCE { + uac-BarringFactor ENUMERATED {p00, p05, p10, p15, p20, p25, p30, p40, + p50, p60, p70, p75, p80, p85, p90, p95}, + uac-BarringTime ENUMERATED {s4, s8, s16, s32, s64, s128, s256, s512}, + uac-BarringForAccessIdentity BIT STRING (SIZE(7)) +} +UAC-BarringInfoSet-v1700 ::= SEQUENCE { +``` + +``` + + uac-BarringFactorForAI3-r17 ENUMERATED {p00, p05, p10, p15, p20, p25, p30, p40, p50, p60, p70, p75, p80, p85, p90, p95} + OPTIONAL -- Need S +} + +-- TAG-UAC-BARRINGINFOSETLIST-STOP +-- ASN1STOP + +``` + +#### UAC-BarringInfoSetList field descriptions + +| | | +|-------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| uac-BarringInfoSetList | List of access control parameter sets. Each access category can be configured with access parameters corresponding to a particular set by uac-barringInfoSetIndex . Association of an access category with an index that has no corresponding entry in the uac-BarringInfoSetList is valid configuration and indicates no barring. | +| uac-BarringForAccessIdentity | Indicates whether access attempt is allowed for each Access Identity. The leftmost bit, bit 0 in the bit string corresponds to Access Identity 1, bit 1 in the bit string corresponds to Access Identity 2, bit 2 in the bit string corresponds to Access Identity 11, bit 3 in the bit string corresponds to Access Identity 12, bit 4 in the bit string corresponds to Access Identity 13, bit 5 in the bit string corresponds to Access Identity 14, and bit 6 in the bit string corresponds to Access Identity 15. Value 0 means that access attempt is allowed for the corresponding access identity. | +| uac-BarringFactor | Represents the probability that access attempt would be allowed during access barring check. | +| uac-BarringFactorForAI3 | Barring factor applicable for Access Identity 3. Represents the probability that access attempt would be allowed during access barring check. If absent, the UE considers the access attempt as allowed. | +| uac-BarringTime | The average time in seconds before a new access attempt is to be performed after an access attempt was barred at access barring check for the same access category, see 5.3.14.5. | + +### – UAC-BarringPerCatList + +The IE *UAC-BarringPerCatList* provides access control parameters for a list of access categories. + +#### UAC-BarringPerCatList information element + +``` + +-- ASN1START +-- TAG-UAC-BARRINGPERCATLIST-START + +UAC-BarringPerCatList ::= SEQUENCE (SIZE (1..maxAccessCat-1)) OF UAC-BarringPerCat + +UAC-BarringPerCat ::= SEQUENCE { + accessCategory INTEGER (1..maxAccessCat-1), + uac-barringInfoSetIndex UAC-BarringInfoSetIndex +} + +-- TAG-UAC-BARRINGPERCATLIST-STOP +-- ASN1STOP + +``` + +| UAC-BarringPerCatList field descriptions | +|----------------------------------------------------------------------------------| +| accessCategory
The Access Category according to TS 22.261 [25]. | + +### – ***UAC-BarringPerPLMN-List*** + +The IE *UAC-BarringPerPLMN-List* provides access category specific access control parameters, which are configured per PLMN/SNPN. + +#### ***UAC-BarringPerPLMN-List* information element** + +``` +-- ASN1START +-- TAG-UAC-BARRINGPERPLMN-LIST-START + +UAC-BarringPerPLMN-List ::= SEQUENCE (SIZE (1.. maxPLMN)) OF UAC-BarringPerPLMN + +UAC-BarringPerPLMN ::= SEQUENCE { + plmn-IdentityIndex INTEGER (1..maxPLMN), + uac-ACBarringListType CHOICE{ + uac-ImplicitACBarringList SEQUENCE (SIZE(maxAccessCat-1)) OF UAC-BarringInfoSetIndex, + uac-ExplicitACBarringList UAC-BarringPerCatList + } +} +OPTIONAL -- Need S + +-- TAG-UAC-BARRINGPERPLMN-LIST-STOP +-- ASN1STOP +``` + +| UAC-BarringPerPLMN-List field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| uac-ACBarringListType
Access control parameters for each access category valid only for a specific PLMN or SNPN. UE behaviour upon absence of this field is specified in clause 5.3.14.2. | +| plmn-IdentityIndex
Index of the PLMN or SNPN across the plmn-IdentityInfoList and npn-IdentityInfoList fields included in SIB1. | + +### – ***UAV-Config*** + +The IE *UAV-Config* provides configuration parameters for UAV UE. + +#### ***UAV-Config* information element** + +``` +-- ASN1START +-- TAG-UAV-CONFIG-START + +UAV-Config-r18 ::= SEQUENCE { + flightPathUpdateThrConfig-r18 SEQUENCE { +``` + +``` + + flightPathUpdateDistanceThr-r18 SetupRelease { FlightPathUpdateDistanceThr-r18 } OPTIONAL, -- Need M + flightPathUpdateTimeThr-r18 SetupRelease { FlightPathUpdateTimeThr-r18 } OPTIONAL -- Need M + } + ... +} + +FlightPathUpdateDistanceThr-r18 ::= INTEGER (0..1023) + +FlightPathUpdateTimeThr-r18 ::= INTEGER (0..16383) + +-- TAG-UAV-CONFIG-STOP +-- ASN1STOP + +``` + +#### ***UAV-Config* field descriptions** + +##### ***flightPathUpdateDistanceThr*** + +Distance threshold for triggering flight path update indication. Actual value is 5 x field value in meters. + +##### ***flightPathUpdateTimeThr*** + +Time threshold for triggering flight path update indication. Value in seconds. + +## ***UE-TimersAndConstants*** + +The IE *UE-TimersAndConstants* contains timers and constants used by the UE in RRC\_CONNECTED, RRC\_INACTIVE and RRC\_IDLE. + +#### ***UE-TimersAndConstants* information element** + +``` + +-- ASN1START +-- TAG-UE-TIMERSANDCONSTANTS-START + +UE-TimersAndConstants ::= SEQUENCE { + t300 ENUMERATED {ms100, ms200, ms300, ms400, ms600, ms1000, ms1500, ms2000}, + t301 ENUMERATED {ms100, ms200, ms300, ms400, ms600, ms1000, ms1500, ms2000}, + t310 ENUMERATED {ms0, ms50, ms100, ms200, ms500, ms1000, ms2000}, + n310 ENUMERATED {n1, n2, n3, n4, n6, n8, n10, n20}, + t311 ENUMERATED {ms1000, ms3000, ms5000, ms10000, ms15000, ms20000, ms30000}, + n311 ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10}, + t319 ENUMERATED {ms100, ms200, ms300, ms400, ms600, ms1000, ms1500, ms2000}, + ... +} + +-- TAG-UE-TIMERSANDCONSTANTS-STOP +-- ASN1STOP + +``` + +### – **UE-TimersAndConstantsRemoteUE** + +The IE *UE-TimersAndConstantsRemoteUE* contains timers and constants used by the L2 U2N Remote UE in RRC\_CONNECTED, RRC\_INACTIVE and RRC\_IDLE. + +#### **UE-TimersAndConstantsRemoteUE information element** + +``` +-- ASN1START +-- TAG-UE-TIMERSANDCONSTANTSREMOTEUE-START + +UE-TimersAndConstantsRemoteUE-r17 ::= SEQUENCE { + t300-RemoteUE-r17 ENUMERATED {ms100, ms200, ms300, ms400, ms600, ms1000, ms1500, ms2000} OPTIONAL, -- Need S + t301-RemoteUE-r17 ENUMERATED {ms100, ms200, ms300, ms400, ms600, ms1000, ms1500, ms2000} OPTIONAL, -- Need S + t319-RemoteUE-r17 ENUMERATED {ms100, ms200, ms300, ms400, ms600, ms1000, ms1500, ms2000} OPTIONAL, -- Need S + ... +} + +-- TAG-UE-TIMERSANDCONSTANTSREMOTEUE-STOP +-- ASN1STOP +``` + +#### **UE-TimersAndConstantsRemoteUE field descriptions** + +| | | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| t300-RemoteUE | Indicates the timer value of T300 used by L2 U2N Remote UE. If the field is absent, the timer value indicated in t300 applies to L2 U2N Remote UE. | +| t301-RemoteUE | Indicates the timer value of T301 used by L2 U2N Remote UE. If the field is absent, the timer value indicated in t301 applies to L2 U2N Remote UE. | +| t319-RemoteUE | Indicates the timer value of T319 used by L2 U2N Remote UE. If the field is absent, the timer value indicated in t319 applies to L2 U2N Remote UE. | + +### – **UL-DelayValueConfig** + +The IE *UL-DelayValueConfig* specifies the configuration of the UL PDCP Packet Delay value per DRB measurement specified in TS 38.314 [53]. + +#### **UL-DelayValueConfig information element** + +``` +-- ASN1START +-- TAG-ULDELAYVALUECONFIG-START + +UL-DelayValueConfig-r16 ::= SEQUENCE { + delay-DRBList-r16 SEQUENCE (SIZE(1..maxDRB)) OF DRB-Identity +} + +-- TAG-ULDELAYVALUECONFIG-STOP +-- ASN1STOP +``` + +#### | UL-DelayValueConfig field descriptions | |----------------------------------------------------------------------------------------------------------------------------------------------------------------------| | delay-DRBList
Indicates the DRB IDs used by UE to provide results of UL PDCP Packet Delay value per DRB measurement as specified in TS 38.314 [53]. | + +### — ***UL-ExcessDelayConfig*** + +The IE *UL-ExcessDelayConfig* IE specifies the configuration of the UL PDCP Excess Packet Delay per DRB measurement specified in TS 38.314 [53]. + +#### ***UL-ExcessDelayConfig* information element** + +``` +-- ASN1START +-- TAG-ULEXCESSDELAYCONFIG-START + +UL-ExcessDelayConfig-r17 ::= SEQUENCE { + excessDelay-DRBList-r17 SEQUENCE (SIZE(1..maxDRB)) OF ExcessDelay-DRB-IdentityInfo-r17 +} + +ExcessDelay-DRB-IdentityInfo-r17 ::= SEQUENCE { + drb-IdentityList SEQUENCE (SIZE(1..maxDRB)) OF DRB-Identity, + delayThreshold ENUMERATED {ms0dot25, ms0dot5, ms1, ms2, ms4, ms5, ms10, ms20, ms30, ms40, ms50, ms60, ms70, + ms80, ms90, ms100, ms150, ms300, ms500} +} + +-- TAG-ULEXCESSDELAYCONFIG-STOP +-- ASN1STOP +``` + +#### | UL-ExcessDelayConfig field descriptions | |--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | drb-IdentityList
Indicates the DRB IDs used by UE to provide results of UL PDCP Excess Packet Delay per DRB measurement as specified in TS 38.314 [53]. | | delayThreshold
Indicates the delay threshold for the DRB IDs indicated in DRB-IdentityList. Value ms0dot25 corresponds to 0.25ms, ms0dot5 corresponds to 0.5ms, ms1 corresponds to 1ms and so on. | + +## — ***UL-GapFR2-Config*** + +The IE *UL-GapFR2-Config* specifies the FR2 uplink gap configuration. + +#### ***UL-GapFR2-Config* information element** + +``` +-- ASN1START +-- TAG-UL-GAPFR2-CONFIG-START + +UL-GapFR2-Config-r17 ::= SEQUENCE { +``` + +``` + +gapOffset-r17 INTEGER (0..159), +ugl-r17 ENUMERATED {ms0dot125, ms0dot25, ms0dot5, ms1}, +ugrp-r17 ENUMERATED {ms5, ms20, ms40, ms160}, +refFR2-ServCellAsyncCA-r17 ServCellIndex OPTIONAL -- Cond AsyncCA +} + +-- TAG-UL-GAPFR2-CONFIG-STOP +-- ASN1STOP + +``` + +#### UL-GapFR2-Config field descriptions + +| | | +|-------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| gapOffset | Value gapOffset is the gap offset of the FR2 UL gap pattern with UGRP indicated in the field ugrp . The value range is from 0 to ugrp -1. | +| refFR2-ServCellAsyncCA | Indicates the FR2 serving cell identifier whose SFN and subframe is used for FR2 UL gap calculation for this gap pattern with asynchronous CA involving FR2 carrier(s). | +| ugl | Value ugl is the gap length in ms of the FR2 UL gap. The FR2 UL gap length is according to Table 9.1.11-1 in TS 38.133 [14]. Value ms0dot125 corresponds to 0.125 ms, ms0dot25 corresponds to 0.25 ms and so on. | +| ugrp | Value ugrp is the gap repetition period in (ms) of the FR2 UL gap. The FR2 UL gap repetition period is according to Table 9.1.11-1 in TS 38.133 [14]. | + +| Conditional Presence | Explanation | +|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AsyncCA | This field is mandatory present when configuring FR2 UL gap pattern to UE in:
- (NG)EN-DC, NR SA, NE-DC or NR-DC without FR2-FR2 band combination, with asynchronous CA involving FR2 carriers. Otherwise, it is absent. | + +### — UplinkCancellation + +The IE *UplinkCancellation* is used to configure the UE to monitor PDCCH for the CI-RNTI. + +#### UplinkCancellation information element + +``` + +-- ASN1START +-- TAG-UPLINKCANCELLATION-START + +UplinkCancellation-r16 ::= SEQUENCE { + ci-RNTI-r16 RNTI-Value, + dci-PayloadSizeForCI-r16 INTEGER (0..maxCI-DCI-PayloadSize-r16), + ci-ConfigurationPerServingCell-r16 SEQUENCE (SIZE (1..maxNrofServingCells)) OF CI-ConfigurationPerServingCell-r16, + ... +} + +CI-ConfigurationPerServingCell-r16 ::= SEQUENCE { + servingCellId ServCellIndex, + positionInDCI-r16 INTEGER (0..maxCI-DCI-PayloadSize-1-r16), +} + +``` + +``` + +positionInDCI-ForSUL-r16 INTEGER (0..maxCI-DCI-PayloadSize-1-r16) OPTIONAL, -- Cond SUL-Only +ci-PayloadSize-r16 ENUMERATED {n1, n2, n4, n5, n7, n8, n10, n14, n16, n20, n28, n32, n35, n42, n56, n112}, +timeFrequencyRegion-r16 SEQUENCE { + timeDurationForCI-r16 ENUMERATED {n2, n4, n7, n14} OPTIONAL, -- Cond +SymbolPeriodicity + timeGranularityForCI-r16 ENUMERATED {n1, n2, n4, n7, n14, n28}, + frequencyRegionForCI-r16 INTEGER (0..37949), + deltaOffset-r16 INTEGER (0..2), + ... +}, +uplinkCancellationPriority-v1610 ENUMERATED {enabled} OPTIONAL -- Need S +} + +-- TAG-UPLINKCANCELLATION-STOP +-- ASN1STOP + +``` + +| UplinkCancellation field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ci-ConfigurationPerServingCell
Indicates (per serving cell) the position of the ci-PayloadSize bit CI values inside the DCI payload (see TS 38.213 [13], clause 11.2A). | +| ci-RNTI
RNTI used for indication cancellation in UL (see TS 38.212 [17] clause 7.3.1 and TS 38.213 [13], clause 11.2A). | +| dcI-PayloadSizeForCI
Total length of the DCI payload scrambled with CI-RNTI (see TS 38.213 [13], clause 11.2A). | + +| CI-ConfigurationPerServingCell field descriptions | | +|----------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ci-PayloadSize | Configures the field size for each UL cancellation indicator of this serving cell (servingCellId) (see TS 38.213 [13], clause 11.2A). | +| deltaOffset | Configures the additional offset from the end of a PDCCH reception where the UE detects the DCI format 2_4 and the first symbol of the T_"CI" symbols, in the unit of OFDM symbols (see TS 38.213 [13], clause 11.2A). | +| frequencyRegionForCI | Configures the reference frequency region where a detected UL CI is applicable (see TS 38.213 [13], clause 11.2A). It is defined in the same way as locationAndBandwidth . | +| positionInDCI | Starting position (in number of bit) of the ci-PayloadSize bit CI value applicable for this serving cell (servingCellId) within the DCI payload (see TS 38.213 [13], clause 11.2A). | +| positionInDCI-ForSUL | Starting position (in number of bit) of the ci-PayloadSize bit CI value applicable for SUL of this serving cell (servingCellId) within the DCI payload (see TS 38.213 [13], clause 11.2A). | +| timeDurationForCI | Configures the duration of the reference time region in symbols where a detected UL CI is applicable of this serving cell (servingCellId) (see TS 38.213 [13], clause 11.2A). If the field is absent, i.e., the configured UL CI monitoring periodicity indicated by monitoringSlotPeriodicityAndOffset for DCI format 2_4 is larger than 1 slot or 1 slot with only one monitoring occasion, the UE applies the value of the configured UL CI monitoring periodicity. | +| timeFrequencyRegion | Configures the reference time and frequency region where a detected UL CI is applicable of this serving cell (servingCellId) (see TS 38.213 [13], clause 11.2A). | +| timeGranularityForCI | Configures the number of partitions within the time region of this serving cell (servingCellId) (see TS 38.213 [13], clause 11.2A). | +| uplinkCancellationPriority | Configures uplink cancellation behavior if both UL CI and intra-UE priority indicator are configured for a given UE. If the field is present, then UL CI is only applicable to the UL transmissions indicated/configured as low priority level. If the field is absent, UL CI is applicable to UL transmission irrespective of its priority level (see TS 38.213 [13], clause 11.2A). | + +| Conditional Presence | Explanation | +|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SUL-Only | The field is optionally present, Need R, if supplementaryUplink is configured in ServingCellConfig . It is absent otherwise. | +| SymbolPeriodicity | This field is mandatory present if the configured UL CI monitoring periodicity indicated by monitoringSlotPeriodicityAndOffset for DCI format 2_4 is 1 slot with more than one monitoring occasion, otherwise absent. | + +### — UplinkConfigCommon + +The IE *UplinkConfigCommon* provides common uplink parameters of a cell. + +#### **UplinkConfigCommon information element** + +``` +-- ASN1START +-- TAG-UPLINKCONFIGCOMMON-START + +UplinkConfigCommon ::= SEQUENCE { + frequencyInfoUL FrequencyInfoUL OPTIONAL, -- Cond InterFreqHOAndServCellAdd +``` + +``` + + initialUplinkBWP BWP-UplinkCommon OPTIONAL, -- Cond ServCellAdd + dummy TimeAlignmentTimer +} + +UplinkConfigCommon-v1700 ::= SEQUENCE { + initialUplinkBWP-RedCap-r17 BWP-UplinkCommon OPTIONAL -- Need R +} + +-- TAG-UPLINKCONFIGCOMMON-STOP +-- ASN1STOP + +``` + +#### UplinkConfigCommon field descriptions + +| | | +|--------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| frequencyInfoUL | Absolute uplink frequency configuration and subcarrier specific virtual carriers. | +| initialUplinkBWP | The initial uplink BWP configuration for a serving cell (see TS 38.213 [13], clause 12). | +| initialUplinkBWP-RedCap | If present, (e)RedCap UEs use this UL BWP instead of initialUplinkBWP .
If absent, (e)RedCap UEs use initialUplinkBWP provided that it does not exceed the (e)RedCap UE maximum bandwidth (see also clause 5.2.2.4.2). | + +| Conditional Presence | Explanation | +|----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| InterFreqHOAndServCellAdd | This field is mandatory present for inter-frequency handover and upon serving cell (PCell/SCell) addition. Otherwise, the field is optionally present, Need M. | +| ServCellAdd | This field is mandatory present upon serving cell addition (for PCell and SCell) and upon handover from E-UTRA to NR. It is optionally present, Need M otherwise. | + +### — UplinkConfigCommonSIB + +The IE *UplinkConfigCommonSIB* provides common uplink parameters of a cell. + +#### UplinkConfigCommonSIB information element + +``` + +-- ASN1START +-- TAG-UPLINKCONFIGCOMMONSIB-START + +UplinkConfigCommonSIB ::= SEQUENCE { + frequencyInfoUL FrequencyInfoUL-SIB, + initialUplinkBWP BWP-UplinkCommon, + timeAlignmentTimerCommon TimeAlignmentTimer +} + +UplinkConfigCommonSIB-v1700 ::= SEQUENCE { + initialUplinkBWP-RedCap-r17 BWP-UplinkCommon OPTIONAL -- Need R +} + +``` + +``` + +UplinkConfigCommonSIB-v1760 ::= SEQUENCE { + frequencyInfoUL-v1760 FrequencyInfoUL-SIB-v1760 +} + +-- TAG-UPLINKCONFIGCOMMONSIB-STOP +-- ASN1STOP + +``` + +#### ***UplinkConfigCommonSIB* field descriptions** + +| | | +|---------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| frequencyInfoUL | Absolute uplink frequency configuration and subcarrier specific virtual carriers. | +| InitialUplinkBWP | The initial uplink BWP configuration for a PCell (see TS 38.213 [13], clause 12). | +| initialUplinkBWP-RedCap | If present, (e)RedCap UEs use this UL BWP instead of initialUplinkBWP .
If absent, (e)RedCap UEs use initialUplinkBWP provided that it does not exceed the (e)RedCap UE maximum bandwidth (see also clause 5.2.2.4.2). | + +### — ***Uplink-PowerControl*** + +The IE *Uplink-PowerControl* is used to configure UE specific power control parameter for PUSCH, PUCCH and SRS. + +#### ***Uplink-PowerControl* information element** + +``` + +-- ASN1START +-- TAG-UPLINK-POWERCONTROL-START + +Uplink-powerControl-r17 ::= SEQUENCE { + ul-powercontrolId-r17 Uplink-powerControlId-r17, + p0AlphaSetforPUSCH-r17 P0AlphaSet-r17 OPTIONAL, -- Need R + p0AlphaSetforPUCCH-r17 P0AlphaSet-r17 OPTIONAL, -- Need R + p0AlphaSetforSRS-r17 P0AlphaSet-r17 OPTIONAL -- Need R +} + +P0AlphaSet-r17 ::= SEQUENCE { + p0-r17 INTEGER (-16..15) OPTIONAL, -- Need R + alpha-r17 Alpha OPTIONAL, -- Need S + closedLoopIndex-r17 ENUMERATED { i0, i1 } +} + +Uplink-powerControlId-r17 ::= INTEGER(1.. maxUL-TCI-r17) + +-- TAG-UPLINK-POWERCONTROL-STOP +-- ASN1STOP + +``` + +| Uplink-PowerControl field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| p0AlphaSetforPUSCH, p0AlphaSetforPUCCH, p0AlphaSetforSRS
Configures power control parameters for PUSCH, PUCCH and SRS (see TS 38.213 [13], clause 7.2). When the field alpha is absent in p0AlphaSetforPUSCH , the UE applies the value 1 for PUSCH power control. When the field alpha is absent in p0AlphaSetforSRS , the UE applies the value 1 for SRS power control. In p0AlphaSetForPUCCH , the field alpha is absent (not used). | + +### – *Uu-RelayRLC-ChannelConfig* + +The IE *Uu-RelayRLC-ChannelConfig* is used to configure an RLC entity, a corresponding logical channel in MAC for Uu Relay RLC channel between L2 U2N Relay UE and network, or between a N3C relay UE and network in case of MP. + +#### *Uu-RelayRLC-ChannelConfig* information element + +``` +-- ASN1START +-- TAG-UU-RELAYRLC-CHANNELCONFIG-START + +Uu-RelayRLC-ChannelConfig-r17 ::= SEQUENCE { + uu-LogicalChannelIdentity-r17 LogicalChannelIdentity OPTIONAL, -- Cond RelayLCH-SetupOnly + uu-RelayRLC-ChannelID-r17 Uu-RelayRLC-ChannelID-r17, + reestablishRLC-r17 ENUMERATED {true} OPTIONAL, -- Need N + rlc-Config-r17 RLC-Config OPTIONAL, -- Cond RelayLCH-Setup + mac-LogicalChannelConfig-r17 LogicalChannelConfig OPTIONAL, -- Cond RelayLCH-Setup + ... +} + +-- TAG-UU-RELAYRLC-CHANNELCONFIG-STOP +-- ASN1STOP +``` + +| Uu-RelayRLC-ChannelConfig field descriptions | +|------------------------------------------------------------------------------------------------------------------------------| +| uu-LogicalChannelIdentity
Indicates the logical channel id for Uu Relay RLC channel of the L2 U2N Relay UE. | +| uu-RelayRLC-ChannelID
Indicates the Uu Relay RLC channel in the link between L2 U2N Relay UE and network. | +| reestablishRLC
Indicates that RLC should be re-established. | +| rlc-Config
Determines the RLC mode (UM, AM) and provides corresponding parameters. | + +| Conditional Presence | Explanation | +|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| RelayLCH-Setup | This field is mandatory present upon creation of a new logical channel for a Uu Relay RLC channel. It is optionally present, Need M, otherwise. | +| RelayLCH-SetupOnly | This field is mandatory present upon creation of a new logical channel for a Uu Relay RLC channel. It is absent otherwise. | + +### – *Uu-RelayRLC-ChannelID* + +The IE *Uu-RelayRLC-ChannelID* is used to identify a Uu Relay RLC channel in the link between L2 U2N Relay UE and network. + +#### *Uu-RelayRLC-ChannelID* information element + +``` +-- ASN1START +-- TAG-UU-RELAYRLC-CHANNELID-START + +Uu-RelayRLC-ChannelID-r17 ::= INTEGER (1..maxLC-ID) + +-- TAG-UU-RELAYRLC-CHANNELID-STOP +-- ASN1STOP +``` + +### – *UplinkTxDirectCurrentList* + +The IE *UplinkTxDirectCurrentList* indicates the Tx Direct Current locations per serving cell for each configured UL BWP in the serving cell, based on the BWP numerology and the associated carrier bandwidth. + +#### *UplinkTxDirectCurrentList* information element + +``` +-- ASN1START +-- TAG-UPLINKTXDIRECTCURRENTLIST-START + +UplinkTxDirectCurrentList ::= SEQUENCE (SIZE (1..maxNrofServingCells)) OF UplinkTxDirectCurrentCell + +UplinkTxDirectCurrentCell ::= SEQUENCE { + servCellIndex ServCellIndex, + uplinkDirectCurrentBWP SEQUENCE (SIZE (1..maxNrofBWPs)) OF UplinkTxDirectCurrentBWP, + ... + [[ + uplinkDirectCurrentBWP-SUL SEQUENCE (SIZE (1..maxNrofBWPs)) OF UplinkTxDirectCurrentBWP OPTIONAL + ]] +} + +UplinkTxDirectCurrentBWP ::= SEQUENCE { + bwp-Id BWP-Id, + shift7dot5kHz BOOLEAN, + txDirectCurrentLocation INTEGER (0..3301) +} + +-- TAG-UPLINKTXDIRECTCURRENTLIST-STOP +-- ASN1STOP +``` + +| UplinkTxDirectCurrentBWP field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| bwp-Id
The BWP-Id of the corresponding uplink BWP. | +| shift7dot5kHz
Indicates whether there is 7.5 kHz shift or not. 7.5 kHz shift is applied if the field is set to true . Otherwise 7.5 kHz shift is not applied. | +| txDirectCurrentLocation
The uplink Tx Direct Current location for the carrier. Only values in the value range of this field between 0 and 3299, which indicate the subcarrier index within the carrier corresponding to the numerology of the corresponding uplink BWP and value 3300, which indicates "Outside the carrier" and value 3301, which indicates "Undetermined position within the carrier" are used in this version of the specification. | + +| UplinkTxDirectCurrentCell field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| servCellIndex
The serving cell ID of the serving cell corresponding to the uplinkDirectCurrentBWP . | +| uplinkDirectCurrentBWP
The Tx Direct Current locations for all the uplink BWPs configured at the corresponding serving cell. | +| uplinkDirectCurrentBWP-SUL
The Tx Direct Current locations for all the supplementary uplink BWPs configured at the corresponding serving cell. | + +### — *UplinkTxDirectCurrentMoreCarrierList* + +The IE *UplinkTxDirectCurrentMoreCarrierList* indicates the Tx Direct Current locations for intra-band CA including one, two or more uplink carriers. The UE does not report the uplink Direct Current location information for SUL carrier(s). + +#### ***UplinkTxDirectCurrentMoreCarrierList* information element** + +``` +-- ASN1START +-- TAG-UPLINKTXDIRECTCURRENTMORECARRIERLIST-START + +UplinkTxDirectCurrentMoreCarrierList-r17 ::= SEQUENCE (SIZE (1..maxNrofCC-Group-r17)) OF CC-Group-r17 + +CC-Group-r17 ::= SEQUENCE { + servCellIndexLower-r17 ServCellIndex, + servCellIndexHigher-r17 ServCellIndex OPTIONAL, + defaultDC-Location-r17 DefaultDC-Location-r17, + offsetToDefault-r17 CHOICE{ + offsetValue OffsetValue-r17, + offsetList SEQUENCE (SIZE(1..maxNrofReqComDC-Location-r17)) OF OffsetValue-r17 + } OPTIONAL +} + +OffsetValue-r17 ::= SEQUENCE { + offsetValue-r17 INTEGER (-20000.. 20000), + shift7dot5kHz-r17 BOOLEAN +``` + +``` + +} + +DefaultDC-Location-r17 ::= CHOICE { + ul FrequencyComponent-r17, + dl FrequencyComponent-r17, + ulAndDL FrequencyComponent-r17 +} + +FrequencyComponent-r17 ::= ENUMERATED {activeCarrier, configuredCarrier, activeBWP, configuredBWP} + +-- TAG-ULINKTXDIRECTCURRENTMORECARRIERLIST-STOP +-- ASN1STOP + +``` + +| UplinkTxDirectCurrentMoreCarrierList and CC-Group field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CC-Group
The contiguous carriers sharing the same PA in an intra-band UL CA configuration. The UE shall report only one DC location for an intra-band CC combination with one active uplink carrier in case DefaultDC-Location is set to activeCarrier or activeBWP . | +| defaultDC-Location
Indicates the default DC location derivation option. The default Tx Direct Current is located at the mathematical center of the UE bandwidth, i.e. between the lower edge of the lowest subcarrier of the lowest frequency component and the upper edge of the highest subcarrier of the highest frequency component, rounded to the subcarrier grid of the lowest SCS defined for the component carrier on which the default Direct Current is located. The lowest and highest frequency components used for derivation of mathematical center are indicated by FrequencyComponent in the associated CC-Group , where the lowest frequency component and the highest frequency component may be the same. If the mathematical center of the UE bandwidth lands on frequencies where there is no subcarrier grid defined, the subcarrier grid of the lowest SCS of the nearest lower frequency component carrier shall be extended to cover the frequency of the mathematical default Direct Current location. | +| offsetToDefault
Indicates the DC location offset to the default DC location derived from defaultDC-Location . The lowest SCS in the CC group is used as the offset granularity. Value 0 represents no offset.
offsetValue is used in case DefaultDC-Location is set to configuredCarrier or configuredBWP . offsetList is used in case DefaultDC-Location is set to activeCarrier or activeBWP . Each entity in this list corresponds to the entry in carriers combination in IntraBandCC-CombinationReqlList of the intra-band CA component. For each CC group, the UE shall include the same number of entries, and listed in the same order as in CC-CombinationList . If DefaultDC-Location is set the activeCarrier , same offsetValue is signalled for all requested carriers combinations with same active carriers states(regardless of the active BWP index). | +| servCellIndexHigher
Indicates the serving cell index of the highest edge of the CC-Group . If absent, there is only one carrier in this group indicated by servCellIndexLower . | +| servCellIndexLower
Indicates the serving cell index of the lowest edge of the CC-Group . | +| shift7dot5kHz
Indicates whether there is 7.5 kHz shift or not. 7.5 kHz shift is applied if the field is set to true, otherwise 7.5 kHz shift is not applied. | + +| DefaultDC-Location field descriptions | | +|----------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------| +| dl | Indicates that the default DC location is derived based on the DL frequencies of the frequency component. | +| ul | Indicates that the default DC location is derived based on the UL frequencies of the frequency component. | +| ulAndDL | Indicates that the default DC location is derived based on the edge most frequencies among any DL and UL frequency components. | + +### – *UplinkTxDirectCurrentTwoCarrierList* + +The IE *UplinkTxDirectCurrentTwoCarrierList* indicates the Tx Direct Current locations when uplink intra-band CA with two carriers is configured, based on the configured carriers and BWP numerology and the associated carrier bandwidth of the carriers. The UE does not report the uplink Direct Current location information for SUL carrier(s). + +#### ***UplinkTxDirectCurrentTwoCarrierList* information element** + +``` +-- ASN1START +-- TAG-UPLINKTXDIRECTCURRENTTWOCARRIERLIST-START + +UplinkTxDirectCurrentTwoCarrierList-r16 ::= SEQUENCE (SIZE (1..maxNrofTxDC-TwoCarrier-r16)) OF UplinkTxDirectCurrentTwoCarrier-r16 + +UplinkTxDirectCurrentTwoCarrier-r16 ::= SEQUENCE { + carrierOneInfo-r16 UplinkTxDirectCurrentCarrierInfo-r16, + carrierTwoInfo-r16 UplinkTxDirectCurrentCarrierInfo-r16, + singlePA-TxDirectCurrent-r16 UplinkTxDirectCurrentTwoCarrierInfo-r16, + secondPA-TxDirectCurrent-r16 UplinkTxDirectCurrentTwoCarrierInfo-r16 OPTIONAL +} + +UplinkTxDirectCurrentCarrierInfo-r16 ::= SEQUENCE { + servCellIndex-r16 ServCellIndex, + servCellInfo-r16 CHOICE { + bwp-Id-r16 BWP-Id, + deactivatedCarrier-r16 ENUMERATED {deactivated} + } +} + +UplinkTxDirectCurrentTwoCarrierInfo-r16 ::= SEQUENCE { + referenceCarrierIndex-r16 ServCellIndex, + shift7dot5kHz-r16 BOOLEAN, + txDirectCurrentLocation-r16 INTEGER (0..3301) +} + +-- TAG-UPLINKTXDIRECTCURRENTTWOCARRIERLIST-STOP +-- ASN1STOP +``` + +| UplinkTxDirectCurrentTwoCarrierInfo field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| referenceCarrierIndex
The serving cell ID of the carrier which is to be used as the reference for interpreting the Tx Direction Current location as reported using txDirectCurrentLocation-r16 . The numerology of the uplink BWP ID reported with bwp-Id-r16 for this serving cell is the numerology used for interpreting the reported subcarrier location. | +| shift7dot5kHz
Indicates whether there is 7.5 kHz shift or not. 7.5 kHz shift is applied if the field is set to true . Otherwise 7.5 kHz shift is not applied. | +| txDirectCurrentLocation
The uplink Tx Direct Current location for the two carrier uplink CA with the serving cells reported using carrierOneInfo-r16 and carrierTwoInfo-r16 . Values in the range of this field between 0 and 3299 indicate the subcarrier index of the uplink Tx Direct Current location with the subcarrier taken from the serving cell with ID referenceCarrierIndex and the numerology of the corresponding uplink BWP reported for this serving cell. Value 3300 indicates "Outside the carrier" and value 3301 indicates "Undetermined position within the carrier". | + +| UplinkTxDirectCurrentCarrierInfo field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| bwp-Id
The BWP ID of the serving cell which is part of the two carrier uplink carrier aggregation. The UE shall not report this field if the serving cell is reported as deactivated using deactivatedCarrier-r16 . | +| deactivatedCarrier
For the reported uplink Tx Direct Current location(s) corresponding to singlePA-TxDirectCurrent-r16 , indicates whether the carrier is deactivated or not for this serving cell. If the carrier refers to the PCell, the UE shall not set this field to deactivated . | +| servCellIndex
The serving cell ID of the serving cell which is part of the two carrier uplink carrier aggregation. | + +| UplinkTxDirectCurrentTwoCarrier field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| carrierOneInfo
The serving cell ID and BWP ID of the first carrier of the uplink carrier aggregation for which the uplink Tx Direct Current location(s) are being reported. | +| carrierTwoInfo
The serving cell ID and BWP ID of the second carrier of the uplink carrier aggregation for which the uplink Tx Direct Current location(s) are being reported. | +| singlePA-TxDirectCurrent
The uplink Tx Direct Current location for the UE which support single PA for this uplink carrier aggregation. For the UEs which support dual PA for this uplink carrier aggregation, this field is for reporting the uplink Tx Direct Current location of the first PA. | +| secondPA-TxDirectCurrent
The uplink Tx Direct Current location used by the UE with the second PA for the UEs which support dual PA for this uplink carrier aggregation. This field shall be absent for the UplinkTxDirectCurrentTwoCarrier entity where deactivatedCarrier of carrierOneInfo or carrierTwoInfo is set to deactivated . | + +### — *ZP-CSI-RS-Resource* + +The IE *ZP-CSI-RS-Resource* is used to configure a Zero-Power (ZP) CSI-RS resource (see TS 38.214 [19], clause 5.1.4.2). Reconfiguration of a *ZP-CSI-RS-Resource* between periodic or semi-persistent and aperiodic is not supported. + +#### **ZP-CSI-RS-Resource information element** + +``` + +-- ASN1START +-- TAG-ZP-CSI-RS-RESOURCE-START + +ZP-CSI-RS-Resource ::= SEQUENCE { + zp-CSI-RS-ResourceId ZP-CSI-RS-ResourceId, + resourceMapping CSI-RS-ResourceMapping, + periodicityAndOffset CSI-ResourcePeriodicityAndOffset OPTIONAL, --Cond PeriodicOrSemiPersistent + ... +} + +ZP-CSI-RS-ResourceId ::= INTEGER (0..maxNrofZP-CSI-RS-Resources-1) + +-- TAG-ZP-CSI-RS-RESOURCE-STOP +-- ASN1STOP + +``` + +#### **ZP-CSI-RS-Resource field descriptions** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| periodicityAndOffset
Periodicity and slot offset for periodic/semi-persistent ZP-CSI-RS (see TS 38.214 [19], clause 5.1.4.2). Network always configures the UE with a value for this field for periodic and semi-persistent ZP-CSI-RS resource (as indicated in PDSCH-Config). | +| resourceMapping
OFDM symbol and subcarrier occupancy of the ZP-CSI-RS resource within a slot. | +| zp-CSI-RS-ResourceId
ZP CSI-RS resource configuration ID (see TS 38.214 [19], clause 5.1.4.2). | + +| Conditional Presence | Explanation | +|---------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PeriodicOrSemiPersistent | The field is optionally present, Need M, for periodic and semi-persistent ZP-CSI-RS-Resources (as indicated in PDSCH-Config). The field is absent otherwise. | + +#### **ZP-CSI-RS-ResourceSet** + +The IE *ZP-CSI-RS-ResourceSet* refers to a set of *ZP-CSI-RS-Resources* using their *ZP-CSI-RS-ResourceIds*. + +#### **ZP-CSI-RS-ResourceSet information element** + +``` + +-- ASN1START +-- TAG-ZP-CSI-RS-RESOURCESET-START + +ZP-CSI-RS-ResourceSet ::= SEQUENCE { + zp-CSI-RS-ResourceSetId ZP-CSI-RS-ResourceSetId, + zp-CSI-RS-ResourceIdList SEQUENCE (SIZE(1..maxNrofZP-CSI-RS-ResourcesPerSet)) OF ZP-CSI-RS-ResourceId, + ... +} + +``` + +``` +-- TAG-ZP-CSI-RS-RESOURCESET-STOP +-- ASN1STOP +``` + +#### | ZP-CSI-RS-ResourceSet field descriptions | |----------------------------------------------------------------------------------------------------------------------------------------| | zp-CSI-RS-ResourceIdList
The list of ZP-CSI-RS-ResourceId identifying the ZP-CSI-RS-Resource elements belonging to this set. | + +#### – **ZP-CSI-RS-ResourceSetId** + +The IE ZP-CSI-RS-ResourceSetId identifies a ZP-CSI-RS-ResourceSet. + +#### **ZP-CSI-RS-ResourceSetId information element** + +``` +-- ASN1START +-- TAG-ZP-CSI-RS-RESOURCESETID-START +``` + +``` +ZP-CSI-RS-ResourceSetId ::= INTEGER (0..maxNrofZP-CSI-RS-ResourceSets-1) +``` + +``` +-- TAG-ZP-CSI-RS-RESOURCESETID-STOP +-- ASN1STOP +``` + +### 6.3.3 UE capability information elements + +### – **AccessStratumRelease** + +The IE AccessStratumRelease indicates the release supported by the UE. + +#### **AccessStratumRelease information element** + +``` +-- ASN1START +-- TAG-ACCESSSTRATUMRELEASE-START +``` + +``` +AccessStratumRelease ::= ENUMERATED { + rel15, rel16, rel17, rel18, spare4, spare3, spare2, spare1, ... } +``` + +``` +-- TAG-ACCESSSTRATUMRELEASE-STOP +-- ASN1STOP +``` + +### – **AerialParameters** + +The IE AerialParameters is used to convey the capabilities supported by the UE for aerial operation. + +#### AerialParameters information element + +``` + +-- ASN1START +-- TAG-AERIALPARAMETERS-START + +AerialParameters-r18 ::= + SEQUENCE { + -- Support of Aerial UE features + aerialUE-Capability-r18 ENUMERATED {supported} OPTIONAL, + -- Support of altitude measurement and event H1/H2-triggered reporting + altitudeMeas-r18 ENUMERATED {supported} OPTIONAL, + -- Support of altitude based measurement configuration of SSB-ToMeasure + altitudeBasedSSB-ToMeasure-r18 ENUMERATED {supported} OPTIONAL, + -- Support of events A3H1, A3H2, A4H1, A4H2, A5H1, A5H2 + eventAxHy-r18 ENUMERATED {supported} OPTIONAL, + -- Support of flight path reporting + flightPathReporting-r18 ENUMERATED {supported} OPTIONAL, + -- Support of flight path availability indication via UAI + flightPathAvailabilityIndicationUAI-r18 ENUMERATED {supported} OPTIONAL, + -- Support of numberOfTriggeringCells for eventA3, eventA4, and eventA5, and additionally, if the UE supports eventAxHy-r18, + -- support of numberOfTriggeringCells for eventA3H1, eventA3H2, eventA4H1, eventA4H2, eventA5H1, and eventA5H2 + multipleCellsMeasExtension-r18 ENUMERATED {supported} OPTIONAL, + -- Support aerial-specific Ns and Pmax list broadcasted by the cell + nr-NS-PmaxListAerial-r18 ENUMERATED {supported} OPTIONAL, -- Editor's Note: + -- Understanding is that a UE that doesn't support any frequency band that requires an aerial specific NS value doesn't need to + -- implement the procedure for aerial specific NS value. Whether indication is needed is still FFS. This is only shown as + -- placeholder. Support of reporting only the measurement report corresponding to the event with the smallest value between the + -- altitude of the UAV and the altitude threshold for which the altitude-related entering condition e.g. A3H1-2 is satisfied, when + -- multiple events of the same type (Hx or AxHy) for the same MO (for AxHy) are triggered simultaneously. + simulMultiTriggerSingleMeasReport-r18 ENUMERATED {supported} OPTIONAL, + -- Support of A2X service(s) using PC5 Sidelink and dedicated resource pool for A2X service(s) + sl-A2X-Service-r18 ENUMERATED {brid, daa, bridAndDAA} OPTIONAL, + -- Editor's Note: Granularity of this capability, e.g. per UE/band/FS is still FFS. Depending on the conclusion, this may need to + -- be moved. + ... + } + +-- TAG-AERIALPARAMETERS-STOP +-- ASN1STOP + +``` + +### AppLayerMeasParameters + +The IE *AppLayerMeasParameters* is used to convey the capabilities supported by the UE for application layer measurements. + +#### AppLayerMeasParameters information element + +``` + +-- ASN1START +-- TAG-APPLAYERMEASPARAMETERS-START + +``` + +``` + +AppLayerMeasParameters-r17 := SEQUENCE { + qoe-Streaming-MeasReport-r17 ENUMERATED {supported} OPTIONAL, + qoe-MTSI-MeasReport-r17 ENUMERATED {supported} OPTIONAL, + qoe-VR-MeasReport-r17 ENUMERATED {supported} OPTIONAL, + ran-VisibleQoE-Streaming-MeasReport-r17 ENUMERATED {supported} OPTIONAL, + ran-VisibleQoE-VR-MeasReport-r17 ENUMERATED {supported} OPTIONAL, + ul-MeasurementReportAppLayer-Seg-r17 ENUMERATED {supported} OPTIONAL, + ..., + [[ + qoe-IdleInactiveMeasReport-r18 ENUMERATED {supported} OPTIONAL, + qoe-NRDC-MeasReport-r18 ENUMERATED {supported} OPTIONAL, + qoe-AdditionalMemoryMeasReport-r18 ENUMERATED {kB128, kB256, kB512, kB1024} OPTIONAL, + qoe-PriorityBasedDiscarding-r18 ENUMERATED {supported} OPTIONAL, + srb5-r18 ENUMERATED {supported} OPTIONAL, + ]] +} + +-- TAG-APPLAYERMEASPARAMETERS-STOP +-- ASN1STOP + +``` + +### – *BandCombinationList* + +The IE *BandCombinationList* contains a list of NR CA, NR non-CA and/or MR-DC band combinations (also including DL only or UL only band). + +#### *BandCombinationList* information element + +``` + +-- ASN1START +-- TAG-BANDCOMBINATIONLIST-START + +BandCombinationList := SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination +BandCombinationList-v1540 := SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1540 +BandCombinationList-v1550 := SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1550 +BandCombinationList-v1560 := SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1560 +BandCombinationList-v1570 := SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1570 +BandCombinationList-v1580 := SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1580 +BandCombinationList-v1590 := SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1590 +BandCombinationList-v15g0 := SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v15g0 +BandCombinationList-v15n0 := SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v15n0 +BandCombinationList-v1610 := SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1610 + +``` + +``` +BandCombinationList-v1630 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1630 +BandCombinationList-v1640 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1640 +BandCombinationList-v1650 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1650 +BandCombinationList-v1680 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1680 +BandCombinationList-v1690 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1690 +BandCombinationList-v16a0 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v16a0 +BandCombinationList-v1700 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1700 +BandCombinationList-v1720 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1720 +BandCombinationList-v1730 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1730 +BandCombinationList-v1740 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1740 +BandCombinationList-v1760 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1760 +BandCombinationList-v1770 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1770 +BandCombinationList-v1800 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1800 +BandCombinationList-UplinkTxSwitch-r16 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-UplinkTxSwitch-r16 +BandCombinationList-UplinkTxSwitch-v1630 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-UplinkTxSwitch-v1630 +BandCombinationList-UplinkTxSwitch-v1640 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-UplinkTxSwitch-v1640 +BandCombinationList-UplinkTxSwitch-v1650 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-UplinkTxSwitch-v1650 +BandCombinationList-UplinkTxSwitch-v1670 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-UplinkTxSwitch-v1670 +BandCombinationList-UplinkTxSwitch-v1690 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-UplinkTxSwitch-v1690 +BandCombinationList-UplinkTxSwitch-v16a0 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-UplinkTxSwitch-v16a0 +BandCombinationList-UplinkTxSwitch-v16e0 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-UplinkTxSwitch-v16e0 +BandCombinationList-UplinkTxSwitch-v1700 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-UplinkTxSwitch-v1700 +BandCombinationList-UplinkTxSwitch-v1720 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-UplinkTxSwitch-v1720 +BandCombinationList-UplinkTxSwitch-v1730 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-UplinkTxSwitch-v1730 +BandCombinationList-UplinkTxSwitch-v1740 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-UplinkTxSwitch-v1740 +BandCombinationList-UplinkTxSwitch-v1760 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-UplinkTxSwitch-v1760 +``` + +``` + +BandCombinationList-UplinkTxSwitch-v1770 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-UplinkTxSwitch-v1770 +BandCombinationList-UplinkTxSwitch-v1800 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-UplinkTxSwitch-v1800 + +BandCombination ::= + SEQUENCE { + bandList SEQUENCE (SIZE (1..maxSimultaneousBands)) OF BandParameters, + featureSetCombination + FeatureSetCombinationId, + ca-ParametersEUTRA + CA-ParametersEUTRA OPTIONAL, + ca-ParametersNR + CA-ParametersNR OPTIONAL, + mrdc-Parameters + MRDC-Parameters OPTIONAL, + supportedBandwidthCombinationSet + BIT STRING (SIZE (1..32)) OPTIONAL, + powerClass-v1530 + ENUMERATED {pc2} OPTIONAL + } + +BandCombination-v1540 ::= + SEQUENCE { + bandList-v1540 SEQUENCE (SIZE (1..maxSimultaneousBands)) OF BandParameters-v1540, + ca-ParametersNR-v1540 + CA-ParametersNR-v1540 OPTIONAL + } + +BandCombination-v1550 ::= + SEQUENCE { + ca-ParametersNR-v1550 + CA-ParametersNR-v1550 + } + +BandCombination-v1560 ::= + SEQUENCE { + ne-DC-BC ENUMERATED {supported} OPTIONAL, + ca-ParametersNRDC + CA-ParametersNRDC OPTIONAL, + ca-ParametersEUTRA-v1560 + CA-ParametersEUTRA-v1560 OPTIONAL, + ca-ParametersNR-v1560 + CA-ParametersNR-v1560 OPTIONAL + } + +BandCombination-v1570 ::= + SEQUENCE { + ca-ParametersEUTRA-v1570 + CA-ParametersEUTRA-v1570 + } + +BandCombination-v1580 ::= + SEQUENCE { + mrdc-Parameters-v1580 + MRDC-Parameters-v1580 + } + +BandCombination-v1590 ::= + SEQUENCE { + supportedBandwidthCombinationSetIntraENDC + BIT STRING (SIZE (1..32)) OPTIONAL, + mrdc-Parameters-v1590 + MRDC-Parameters-v1590 + } + +BandCombination-v15g0 ::= + SEQUENCE { + ca-ParametersNR-v15g0 + CA-ParametersNR-v15g0 OPTIONAL, + ca-ParametersNRDC-v15g0 + CA-ParametersNRDC-v15g0 OPTIONAL, + mrdc-Parameters-v15g0 + MRDC-Parameters-v15g0 OPTIONAL + } + +BandCombination-v15n0 ::= + SEQUENCE { + mrdc-Parameters-v15n0 + MRDC-Parameters-v15n0 + } + +``` + +``` + +} + +BandCombination-v1610 ::= + SEQUENCE { + bandList-v1610 SEQUENCE (SIZE (1..maxSimultaneousBands)) OF BandParameters-v1610 OPTIONAL, + ca-ParametersNR-v1610 CA-ParametersNR-v1610 OPTIONAL, + ca-ParametersNRDC-v1610 CA-ParametersNRDC-v1610 OPTIONAL, + powerClass-v1610 ENUMERATED {pc1dot5} OPTIONAL, + powerClassNRPart-r16 ENUMERATED {pc1, pc2, pc3, pc5} OPTIONAL, + featureSetCombinationDAPS-r16 FeatureSetCombinationId OPTIONAL, + mrdc-Parameters-v1620 MRDC-Parameters-v1620 OPTIONAL + } + +BandCombination-v1630 ::= + SEQUENCE { + ca-ParametersNR-v1630 CA-ParametersNR-v1630 OPTIONAL, + ca-ParametersNRDC-v1630 CA-ParametersNRDC-v1630 OPTIONAL, + mrdc-Parameters-v1630 MRDC-Parameters-v1630 OPTIONAL, + supportedTxBandCombListPerBC-Sidelink-r16 BIT STRING (SIZE (1..maxBandComb)) OPTIONAL, + supportedRxBandCombListPerBC-Sidelink-r16 BIT STRING (SIZE (1..maxBandComb)) OPTIONAL, + scalingFactorTxSidelink-r16 SEQUENCE (SIZE (1..maxBandComb)) OF ScalingFactorSidelink-r16 OPTIONAL, + scalingFactorRxSidelink-r16 SEQUENCE (SIZE (1..maxBandComb)) OF ScalingFactorSidelink-r16 OPTIONAL + } + +BandCombination-v1640 ::= + SEQUENCE { + ca-ParametersNR-v1640 CA-ParametersNR-v1640 OPTIONAL, + ca-ParametersNRDC-v1640 CA-ParametersNRDC-v1640 OPTIONAL + } + +BandCombination-v1650 ::= + SEQUENCE { + ca-ParametersNRDC-v1650 CA-ParametersNRDC-v1650 OPTIONAL + } + +BandCombination-v1680 ::= + SEQUENCE { + intrabandConcurrentOperationPowerClass-r16 SEQUENCE (SIZE (1..maxBandComb)) OF IntraBandPowerClass-r16 OPTIONAL + } + +BandCombination-v1690 ::= + SEQUENCE { + ca-ParametersNR-v1690 CA-ParametersNR-v1690 OPTIONAL + } + +BandCombination-v16a0 ::= + SEQUENCE { + ca-ParametersNR-v16a0 CA-ParametersNR-v16a0 OPTIONAL, + ca-ParametersNRDC-v16a0 CA-ParametersNRDC-v16a0 OPTIONAL + } + +BandCombination-v1700 ::= + SEQUENCE { + ca-ParametersNR-v1700 CA-ParametersNR-v1700 OPTIONAL, + ca-ParametersNRDC-v1700 CA-ParametersNRDC-v1700 OPTIONAL, + mrdc-Parameters-v1700 MRDC-Parameters-v1700 OPTIONAL, + bandList-v1710 SEQUENCE (SIZE (1..maxSimultaneousBands)) OF BandParameters-v1710 OPTIONAL, + supportedBandCombListPerBC-SL-RelayDiscovery-r17 BIT STRING (SIZE (1..maxBandComb)) OPTIONAL, + supportedBandCombListPerBC-SL-NonRelayDiscovery-r17 BIT STRING (SIZE (1..maxBandComb)) OPTIONAL + } + +``` + +``` + +BandCombination-v1720 := SEQUENCE { + ca-ParametersNR-v1720 CA-ParametersNR-v1720 OPTIONAL, + ca-ParametersNRDC-v1720 CA-ParametersNRDC-v1720 OPTIONAL +} + +BandCombination-v1730 := SEQUENCE { + ca-ParametersNR-v1730 CA-ParametersNR-v1730 OPTIONAL, + ca-ParametersNRDC-v1730 CA-ParametersNRDC-v1730 OPTIONAL, + bandList-v1730 SEQUENCE (SIZE (1..maxSimultaneousBands)) OF BandParameters-v1730 OPTIONAL +} + +BandCombination-v1740 := SEQUENCE { + ca-ParametersNR-v1740 CA-ParametersNR-v1740 OPTIONAL +} + +BandCombination-v1760 := SEQUENCE { + ca-ParametersNR-v1760 CA-ParametersNR-v1760, + ca-ParametersNRDC-v1760 CA-ParametersNRDC-v1760 +} + +BandCombination-v1770 := SEQUENCE { + bandList-v1770 SEQUENCE (SIZE (1..maxSimultaneousBands)) OF BandParameters-v1770, + mrdc-Parameters-v1770 MRDC-Parameters-v1770 OPTIONAL, + ca-ParametersNR-v1770 CA-ParametersNR-v1770 OPTIONAL +} + +BandCombination-v1800 := SEQUENCE { + ca-ParametersNR-v1800 CA-ParametersNR-v1800 OPTIONAL, + ca-ParametersNRDC-v1800 CA-ParametersNRDC-v1800 OPTIONAL, + supportedBandCombListPerBC-SL-U2U-RelayDiscovery-r18 BIT STRING (SIZE (1..maxBandComb)) OPTIONAL +} + +BandCombination-UplinkTxSwitch-r16 := SEQUENCE { + bandCombination-r16 BandCombination, + bandCombination-v1540 BandCombination-v1540 OPTIONAL, + bandCombination-v1560 BandCombination-v1560 OPTIONAL, + bandCombination-v1570 BandCombination-v1570 OPTIONAL, + bandCombination-v1580 BandCombination-v1580 OPTIONAL, + bandCombination-v1590 BandCombination-v1590 OPTIONAL, + bandCombination-v1610 BandCombination-v1610 OPTIONAL, + supportedBandPairListNR-r16 SEQUENCE (SIZE (1..maxULTxSwitchingBandPairs)) OF ULTxSwitchingBandPair-r16, + uplinkTxSwitching-OptionSupport-r16 ENUMERATED {switchedUL, dualUL, both} OPTIONAL, + uplinkTxSwitching-PowerBoosting-r16 ENUMERATED {supported} OPTIONAL, + ... + [[ + -- R4 16-5 UL-MIMO coherence capability for dynamic Tx switching between 3CC 1Tx-2Tx switching + uplinkTxSwitching-PUSCH-TransCoherence-r16 ENUMERATED {nonCoherent, fullCoherent} OPTIONAL + ]] +} + +``` + +``` +BandCombination-UplinkTxSwitch-v1630 := SEQUENCE { + bandCombination-v1630 BandCombination-v1630 OPTIONAL +} + +BandCombination-UplinkTxSwitch-v1640 := SEQUENCE { + bandCombination-v1640 BandCombination-v1640 OPTIONAL +} + +BandCombination-UplinkTxSwitch-v1650 := SEQUENCE { + bandCombination-v1650 BandCombination-v1650 OPTIONAL +} + +BandCombination-UplinkTxSwitch-v1670 := SEQUENCE { + bandCombination-v15g0 BandCombination-v15g0 OPTIONAL +} + +BandCombination-UplinkTxSwitch-v1690 := SEQUENCE { + bandCombination-v1690 BandCombination-v1690 OPTIONAL +} + +BandCombination-UplinkTxSwitch-v16a0 := SEQUENCE { + bandCombination-v16a0 BandCombination-v16a0 OPTIONAL +} + +BandCombination-UplinkTxSwitch-v16e0 := SEQUENCE { + bandCombination-v15n0 BandCombination-v15n0 OPTIONAL +} + +BandCombination-UplinkTxSwitch-v1700 := SEQUENCE { + bandCombination-v1700 BandCombination-v1700 OPTIONAL, + -- R4 16-1/16-2/16-3 Dynamic Tx switching between 2CC/3CC 2Tx-2Tx/1Tx-2Tx switching + supportedBandPairListNR-v1700 SEQUENCE (SIZE (1..maxULTxSwitchingBandPairs)) OF ULTxSwitchingBandPair-v1700 OPTIONAL, + -- R4 16-6: UL-MIMO coherence capability for dynamic Tx switching between 2Tx-2Tx switching + uplinkTxSwitchingBandParametersList-v1700 SEQUENCE (SIZE (1.. maxSimultaneousBands)) OF UplinkTxSwitchingBandParameters-v1700 OPTIONAL +} + +BandCombination-UplinkTxSwitch-v1720 := SEQUENCE { + bandCombination-v1720 BandCombination-v1720 OPTIONAL, + uplinkTxSwitching-OptionSupport2T2T-r17 ENUMERATED {switchedUL, dualUL, both} OPTIONAL +} + +BandCombination-UplinkTxSwitch-v1730 := SEQUENCE { + bandCombination-v1730 BandCombination-v1730 OPTIONAL +} + +BandCombination-UplinkTxSwitch-v1740 := SEQUENCE { + bandCombination-v1740 BandCombination-v1740 OPTIONAL +} + +BandCombination-UplinkTxSwitch-v1760 := SEQUENCE { + bandCombination-v1760 BandCombination-v1760 OPTIONAL +} +``` + +``` + +} + +BandCombination-UplinkTxSwitch-v1770 ::= SEQUENCE { + bandCombination-v1770 BandCombination-v1770 OPTIONAL +} + +BandCombination-UplinkTxSwitch-v1800 ::= SEQUENCE { + supportedBandPairListNR-r18 SEQUENCE (SIZE (1..maxULTxSwitchingBandPairs)) OF ULTxSwitchingBandPair-r18 OPTIONAL, + -- R1 49-Y: Minimum separation time for two uplink switching on more than 2 bands within any two consecutive reference slots + uplinkTxSwitchingMinimumSeparationTime-r18 ENUMERATED {n0us, n500us} OPTIONAL, + uplinkTxSwitchingAdditionalPeriodDualUL-List-r18 SEQUENCE (SIZE (1..maxULTxSwitchingBetweenBandPairs-r18)) OF + UplinkTxSwitchingAdditionalPeriodDualUL-r18 OPTIONAL +} + +ULTxSwitchingBandPair-r16 ::= SEQUENCE { + bandIndexUL1-r16 INTEGER(1..maxSimultaneousBands), + bandIndexUL2-r16 INTEGER(1..maxSimultaneousBands), + uplinkTxSwitchingPeriod-r16 ENUMERATED {n35us, n140us, n210us}, + uplinkTxSwitching-DL-Interruption-r16 BIT STRING (SIZE(1..maxSimultaneousBands)) OPTIONAL +} + +ULTxSwitchingBandPair-v1700 ::= SEQUENCE { + uplinkTxSwitchingPeriod2T2T-r17 ENUMERATED {n35us, n140us, n210us} OPTIONAL +} + +ULTxSwitchingBandPair-r18 ::= SEQUENCE { + bandCombination-v1800 BandCombination-v1800 OPTIONAL, + bandIndexUL1-r18 INTEGER(1..maxSimultaneousBands), + bandIndexUL2-r18 INTEGER(1..maxSimultaneousBands), + uplinkTxSwitchingOptionForBandPair-r18 ENUMERATED {switchedUL, dualUL, both}, + -- R1 49-X: Supported switching option for each band pair in the band combination for UL Tx switching across more than 2 bands + uplinkTxSwitchingPeriodForBandPair-r18 SEQUENCE { + switchingPeriodFor2T-r18 ENUMERATED {n35us, n140us, n210us} OPTIONAL, + switchingPeriodFor1T-r18 ENUMERATED {n35us, n140us, n210us} + }, + uplinkTxSwitching-DL-Interruption-r18 BIT STRING (SIZE(1..maxSimultaneousBands)) OPTIONAL, + uplinkTxSwitchingPeriodUnaffectedBandDualUL-List-r18 SEQUENCE (SIZE (1..maxSimultaneousBands-2-r18)) OF + SwitchingPeriodUnaffectedBandDualUL-r18 OPTIONAL +} + +UplinkTxSwitchingBandParameters-v1700 ::= SEQUENCE { + bandIndex-r17 INTEGER(1..maxSimultaneousBands), + uplinkTxSwitching2T2T-PUSCH-TransCoherence-r17 ENUMERATED {nonCoherent, fullCoherent} OPTIONAL +} + +UplinkTxSwitchingAdditionalPeriodDualUL-r18 ::= SEQUENCE { + uplinkTxSwitchingBetweenBandPairs-r18 SEQUENCE { + bandPairIndex1-r18 INTEGER(1.. maxULTxSwitchingBandPairs), + anotherBandPairOrBand-r18 CHOICE { + bandPairIndex2-r18 INTEGER(1.. maxULTxSwitchingBandPairs), + bandIndex-r18 INTEGER(1..maxSimultaneousBands) + } + } +} + +``` + +``` + + } + }, + switchingAdditionalPeriodDualUL-r18 ENUMERATED {n35us, n140us, n210us} +} + +SwitchingPeriodUnaffectedBandDualUL-r18 := + bandIndexUnaffected-r18 INTEGER (1..maxSimultaneousBands), + periodUnaffectedBandDualUL-r18 CHOICE { + maintainedUL-Trans-r18 NULL, + periodOnULBands-r18 ENUMERATED {n35us, n140us, n210us} + } +} + +CombinationCarrierType-r18 := + schedulingCellCarrierType-r18 ENUMERATED {licensed-fdd-fr1, licensed-tdd-fr1, unlicensed-tdd-fr1, fr2-1, fr2-2}, + scheduledCellCarrierType-r18 ENUMERATED {licensed-fdd-fr1, licensed-tdd-fr1, unlicensed-tdd-fr1, fr2-1, fr2-2} +} + +BandParameters := + eutra CHOICE { + bandEUTRA SEQUENCE { + ca-BandwidthClassDL-EUTRA FreqBandIndicatorEUTRA, + ca-BandwidthClassUL-EUTRA CA-BandwidthClassEUTRA OPTIONAL, + }, + nr SEQUENCE { + bandNR FreqBandIndicatorNR, + ca-BandwidthClassDL-NR CA-BandwidthClassNR OPTIONAL, + ca-BandwidthClassUL-NR CA-BandwidthClassNR OPTIONAL + } + } +} + +BandParameters-v1540 := + srs-CarrierSwitch SEQUENCE { + nr CHOICE { + srs-SwitchingTimesListNR SEQUENCE { + }, + eutra SEQUENCE { + srs-SwitchingTimesListEUTRA SEQUENCE (SIZE (1..maxSimultaneousBands)) OF SRS-SwitchingTimeNR + } + } + } + srs-TxSwitch OPTIONAL, + supportedSRS-TxPortSwitch SEQUENCE { + txSwitchImpactToRx ENUMERATED {tlr2, tlr4, t2r4, tlr4-t2r4, tlr1, t2r2, t4r4, notSupported}, + txSwitchWithAnotherBand INTEGER (1..32) OPTIONAL, + } + } +} + +BandParameters-v1610 := + srs-TxSwitch-v1610 SEQUENCE { + supportedSRS-TxPortSwitch-v1610 SEQUENCE { + ENUMERATED {tlr1-tlr2, tlr1-tlr2-tlr4, tlr1-tlr2-t2r2-t2r4, tlr1-tlr2-t2r2-tlr4-t2r4, + tlr1-t2r2, tlr1-t2r2-t4r4} + } + } +} + +``` + +``` + } OPTIONAL + } + + BandParameters-v1710 ::= SEQUENCE { + -- R1 23-8-3 SRS Antenna switching for >4Rx + srs-AntennaSwitchingBeyond4RX-r17 SEQUENCE { + -- 1. Support of SRS antenna switching xTyR with y>4 + supportedSRS-TxPortSwitchBeyond4Rx-r17 BIT STRING (SIZE (11)), + -- 2. Report the entry number of the first-listed band with UL in the band combination that affects this DL + entryNumberAffectBeyond4Rx-r17 INTEGER (1..32) OPTIONAL, + -- 3. Report the entry number of the first-listed band with UL in the band combination that switches together with this UL + entryNumberSwitchBeyond4Rx-r17 INTEGER (1..32) OPTIONAL + } OPTIONAL + } + + BandParameters-v1730 ::= SEQUENCE { + -- R1 39-3-2 Affected bands for inter-band CA during SRS carrier switching + srs-SwitchingAffectedBandsListNR-r17 SEQUENCE (SIZE (1..maxSimultaneousBands)) OF SRS-SwitchingAffectedBandsNR-r17 + } + + BandParameters-v1770 ::= SEQUENCE { + ca-BandwidthClassDL-NR-r17 CA-BandwidthClassNR-r17 OPTIONAL, + ca-BandwidthClassUL-NR-r17 CA-BandwidthClassNR-r17 OPTIONAL + } + + ScalingFactorSidelink-r16 ::= ENUMERATED {f0p4, f0p75, f0p8, f1} + + IntraBandPowerClass-r16 ::= ENUMERATED {pc2, pc3, spare6, spare5, spare4, spare3, spare2, spare1} + + SRS-SwitchingAffectedBandsNR-r17 ::= BIT STRING (SIZE (1..maxSimultaneousBands)) + + -- TAG-BANDCOMBINATIONLIST-STOP + -- ASN1STOP +``` + +| BandCombination field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

BandCombinationList-v1540, BandCombinationList-v1550, BandCombinationList-v1560, BandCombinationList-v1570, BandCombinationList-v1580, BandCombinationList-v1590, BandCombinationList-v15g0, BandCombinationList-v15n0, BandCombinationList-v1610, BandCombinationList-v1630, BandCombinationList-v1640, BandCombinationList-v1650, BandCombinationList-v1680, BandCombinationList-v1690, BandCombinationList-v16a0, BandCombinationList-v1700, BandCombinationList-v1720, BandCombinationList-v1730, BandCombinationList-v1760, BandCombinationList-v1770, BandCombinationList-v1800

The UE shall include the same number of entries, and listed in the same order, as in BandCombinationList (without suffix). If the field is included in supportedBandCombinationListNEDC-Only-v1610, the UE shall include the same number of entries, and listed in the same order, as in BandCombinationList of supportedBandCombinationListNEDC-Only (without suffix) field.

If the field is included in supportedBandCombinationListNEDC-Only-v15a0, the UE shall include the same number of entries, and listed in the same order, as in BandCombinationList (without suffix) of supportedBandCombinationListNEDC-Only (without suffix) field.

| +|

BandCombinationList-UplinkTxSwitch-r16, BandCombinationList-UplinkTxSwitch-v1630, BandCombinationList-UplinkTxSwitch-v1640, BandCombinationList-UplinkTxSwitch-v1650, BandCombinationList-UplinkTxSwitch-v1690, BandCombinationList-UplinkTxSwitch-v16a0, BandCombinationList-UplinkTxSwitch-v16e0, BandCombinationList-UplinkTxSwitch-v1700, BandCombinationList-UplinkTxSwitch-v1720, BandCombinationList-UplinkTxSwitch-v1730, BandCombinationList-UplinkTxSwitch-v1760, BandCombinationList-UplinkTxSwitch-v1770, BandCombinationList-UplinkTxSwitch-v1800

The UE shall include the same number of entries, and listed in the same order, as in BandCombinationList-UplinkTxSwitch-r16.

For the field of supportedBandCombinationList-UplinkTxSwitch-v1700, if the UE does not support 2Tx-2Tx switching for a given band combination, the field of supportedBandPairListNR-v1700 in the corresponding entry is absent.

| +|

ca-ParametersNRDC

If the field is included for a band combination in the NR capability container, the field indicates support of NR-DC. Otherwise, the field is absent.

| +|

featureSetCombinationDAPS

If this field is present for a band combination, it reports the feature set combination supported for the band combination when any DAPS bearer is configured.

| +|

ne-DC-BC

If the field is included for a band combination in the MR-DC capability container, the field indicates support of NE-DC. Otherwise, the field is absent.

| +|

supportedBandPairListNR-r16, supportedBandPairListNR-v1700

Indicates a list of band pair supporting UL Tx switching as defined in TS 38.101-1 [15] for a given band combination.

A UE supporting 2Tx-2Tx switching should include both of supportedBandPairListNR-r16 and supportedBandPairListNR-v1700. And the UE shall include the same number of entries listed in the same order as in supportedBandPairListNR-r16.

If the UE does not support 2Tx-2Tx switching for a given band pair, the field of uplinkTxSwitchingPeriod2T2T in the corresponding entry is absent.

| +|

supportedBandPairListNR-r18

Indicates a list of band pair supporting UL Tx switching up to 4 bands as defined in TS 38.101-1 [15] for a given band combination. The UE shall include all the possible band pairs.

For a band pair only supporting 1Tx-1Tx switching, the UE should include switchingPeriodFor1T in ULTxSwitchingBandPair-r18.

For a band pair supporting 1Tx-2Tx switching, the UE always supports 1Tx-1Tx switching, and the UE should include switchingPeriodFor1T in ULTxSwitchingBandPair-r18.

For a band pair supporting 2Tx-2Tx switching, the UE always supports 1Tx-2Tx switching and 1Tx-1Tx switching, the UE should include switchingPeriodFor2T as well as switchingPeriodFor1T in ULTxSwitchingBandPair-r18.

| +|

srs-SwitchingTimesListNR

Indicates, for a particular pair of NR bands, the RF retuning time when switching between a NR carrier corresponding to this band entry and another (PUSCH-less) NR carrier corresponding to the band entry in the order indicated below:

  • - For the first NR band, the UE shall include the same number of entries for NR bands as in bandList, i.e. first entry corresponds to first NR band in bandList and so on,
  • - For the second NR band, the UE shall include one entry less, i.e. first entry corresponds to the second NR band in bandList and so on
  • - And so on
| +|

srs-SwitchingTimesListEUTRA

Indicates, for a particular pair of E-UTRA bands, the RF retuning time when switching between an E-UTRA carrier corresponding to this band entry and another (PUSCH-less)

| + +E-UTRA carrier corresponding to the band entry in the order indicated below: + +- For the first E-UTRA band, the UE shall include the same number of entries for E-UTRA bands as in *bandList*, i.e. first entry corresponds to first E-UTRA band in *bandList* and so on, +- For the second E-UTRA band, the UE shall include one entry less, i.e. first entry corresponds to the second E-UTRA band in *bandList* and so on +- And so on + +#### **srs-TxSwitch** + +Indicates supported SRS antenna switch capability for the associated band. If the UE indicates support of *SRS-SwitchingTimeNR*, the UE is allowed to set this field for a band with associated *FeatureSetUplinkId* set to 0 for SRS carrier switching. + +##### **uplinkTxSwitchingBandParametersList-v1700** + +Indicates a list of per band per band combination capabilities for UL Tx switching. + +### — *BandCombinationListSidelinkEUTRA-NR* + +The IE *BandCombinationListSidelinkEUTRA-NR* contains a list of V2X sidelink and NR sidelink band combinations. + +#### BandCombinationListSidelinkEUTRA-NR information element + +``` +-- ASN1START +-- TAG-BANDCOMBINATIONLISTSIDELINKEUTRANR-START + +BandCombinationListSidelinkEUTRA-NR-r16 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombinationParametersSidelinkEUTRA-NR-r16 +BandCombinationListSidelinkEUTRA-NR-v1630 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombinationParametersSidelinkEUTRA-NR-v1630 +BandCombinationListSidelinkEUTRA-NR-v1710 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombinationParametersSidelinkEUTRA-NR-v1710 +BandCombinationParametersSidelinkEUTRA-NR-r16 ::= SEQUENCE (SIZE (1..maxSimultaneousBands)) OF BandParametersSidelinkEUTRA-NR-r16 +BandCombinationParametersSidelinkEUTRA-NR-v1630 ::= SEQUENCE (SIZE (1..maxSimultaneousBands)) OF BandParametersSidelinkEUTRA-NR-v1630 +BandCombinationParametersSidelinkEUTRA-NR-v1710 ::= SEQUENCE (SIZE (1..maxSimultaneousBands)) OF BandParametersSidelinkEUTRA-NR-v1710 + +BandParametersSidelinkEUTRA-NR-r16 ::= CHOICE { + eutra SEQUENCE { + bandParametersSidelinkEUTRA1-r16 OCTET STRING OPTIONAL, + bandParametersSidelinkEUTRA2-r16 OCTET STRING OPTIONAL + }, + nr SEQUENCE { + bandParametersSidelinkNR-r16 BandParametersSidelink-r16 + } +} + +BandParametersSidelinkEUTRA-NR-v1630 ::= CHOICE { + eutra NULL, + nr SEQUENCE { + tx-Sidelink-r16 ENUMERATED {supported} OPTIONAL, + rx-Sidelink-r16 ENUMERATED {supported} OPTIONAL, + } +} +``` + +``` + + sl-CrossCarrierScheduling-r16 ENUMERATED {supported} OPTIONAL + } +} + +BandParametersSidelinkEUTRA-NR-v1710 ::= CHOICE { + eutra NULL, + nr SEQUENCE { + --32-4 + sl-TransmissionMode2-PartialSensing-r17 SEQUENCE { + harq-TxProcessModeTwoSidelink-r17 ENUMERATED {n8, n16}, + scs-CP-PatternTxSidelinkModeTwo-r17 CHOICE { + fr1-r17 SEQUENCE { + scs-15kHz-r17 BIT STRING (SIZE (16)) OPTIONAL, + scs-30kHz-r17 BIT STRING (SIZE (16)) OPTIONAL, + scs-60kHz-r17 BIT STRING (SIZE (16)) OPTIONAL + }, + fr2-r17 SEQUENCE { + scs-60kHz-r17 BIT STRING (SIZE (16)) OPTIONAL, + scs-120kHz-r17 BIT STRING (SIZE (16)) OPTIONAL + } + } OPTIONAL, + extendedCP-Mode2PartialSensing-r17 ENUMERATED {supported} OPTIONAL, + dl-openLoopPC-Sidelink-r17 ENUMERATED {supported} OPTIONAL, + } OPTIONAL, + --32-2a: Receiving NR sidelink of PSFCH + rx-sidelinkPSFCH-r17 ENUMERATED {n5, n15, n25, n32, n35, n45, n50, n64} OPTIONAL, + --32-5a-1 + tx-IUC-Scheme1-Mode2Sidelink-r17 ENUMERATED {supported} OPTIONAL, + --32-5b-1 + tx-IUC-Scheme2-Mode2Sidelink-r17 ENUMERATED {n4, n8, n16} OPTIONAL + } +} + +BandParametersSidelink-r16 ::= SEQUENCE { + freqBandSidelink-r16 FreqBandIndicatorNR +} + +-- TAG-BANDCOMBINATIONLISTSIDELINKEUTRANR-STOP +-- ASN1STOP + +``` + +#### **BandParametersSidelinkEUTRA-NR field descriptions** + +##### **bandParametersSidelinkEUTRA1, bandParametersSidelinkEUTRA2** + +This field includes the *V2X-BandParameters-r14* and *V2X-BandParameters-v1530* IE as specified in 36.331 [10]. It is used for reporting the per-band capability for V2X sidelink communication. + +### — *BandCombinationListSL-Discovery* + +The IE *BandCombinationListSL-Discovery* contains a list of NR Sidelink discovery band combinations. + +#### ***BandCombinationListSidelinkSL-Discovery* information element** + +``` +-- ASN1START +-- TAG-BANDCOMBINATIONLISTSLDISCOVERY-START + +BandCombinationListSL-Discovery-r17 ::= SEQUENCE (SIZE (1..maxSimultaneousBands)) OF BandParametersSidelinkDiscovery-r17 + +BandParametersSidelinkDiscovery-r17 ::= SEQUENCE { + sl-CrossCarrierScheduling-r17 ENUMERATED {supported} OPTIONAL, + --R1 32-4: Transmitting NR sidelink mode 2 with partial sensing + sl-TransmissionMode2-PartialSensing-r17 SEQUENCE { + harq-TxProcessModeTwoSidelink-r17 ENUMERATED {n8, n16}, + scs-CP-PatternTxSidelinkModeTwo-r17 CHOICE { + fr1-r17 SEQUENCE { + scs-15kHz-r17 BIT STRING (SIZE (16)) OPTIONAL, + scs-30kHz-r17 BIT STRING (SIZE (16)) OPTIONAL, + scs-60kHz-r17 BIT STRING (SIZE (16)) OPTIONAL + }, + fr2-r17 SEQUENCE { + scs-60kHz-r17 BIT STRING (SIZE (16)) OPTIONAL, + scs-120kHz-r17 BIT STRING (SIZE (16)) OPTIONAL + } + } + } + extendedCP-Mode2PartialSensing-r17 ENUMERATED {supported} OPTIONAL, + dl-openLoopPC-Sidelink-r17 ENUMERATED {supported} OPTIONAL, + --R1 32-5a-1: Transmitting Inter-UE coordination scheme 1 in NR sidelink mode 2 + tx-IUC-Scheme1-Mode2Sidelink-r17 ENUMERATED {supported} OPTIONAL +} + +-- TAG-BANDCOMBINATIONLISTSLDISCOVERY-STOP +-- ASN1STOP +``` + +### — *CA-BandwidthClassEUTRA* + +The IE *CA-BandwidthClassEUTRA* indicates the E-UTRA CA bandwidth class as defined in TS 36.101 [22], table 5.6A-1. + +#### ***CA-BandwidthClassEUTRA* information element** + +``` +-- ASN1START +-- TAG-CA-BANDWIDTHCLASSEUTRA-START +``` + +``` +CA-BandwidthClassEUTRA ::= ENUMERATED {a, b, c, d, e, f, ...} + +-- TAG-CA-BANDWIDTHCLASSEUTRA-STOP +-- ASN1STOP +``` + +### — *CA-BandwidthClassNR* + +The IE *CA-BandwidthClassNR* indicates the NR CA bandwidth class as defined in TS 38.101-1 [15], table 5.3A.5-1 and TS 38.101-2 [39], table 5.3A.4-1. + +#### ***CA-BandwidthClassNR* information element** + +``` +-- ASN1START +-- TAG-CA-BANDWIDTHCLASSNR-START + +-- R4 17-6: new CA BW Classes R2-R12 +-- R4 17-7: new CA BW Classes V, W + +CA-BandwidthClassNR ::= ENUMERATED {a, b, c, d, e, f, g, h, i, j, k, l, m, n, o, p, q, ..., r2-v1730, r3-v1730, r4-v1730, r5-v1730, r6-v1730, r7-v1730, r8-v1730, r9-v1730, r10-v1730, r11-v1730, r12-v1730, v-v1770, w-v1770 } + +CA-BandwidthClassNR-r17 ::= ENUMERATED {r, s, t, u, ...} + +-- TAG-CA-BANDWIDTHCLASSNR-STOP +-- ASN1STOP +``` + +### — *CA-ParametersEUTRA* + +The IE *CA-ParametersEUTRA* contains the E-UTRA part of band combination parameters for a given MR-DC band combination. + +NOTE: If additional E-UTRA band combination parameters are defined in TS 36.331 [10], which are supported for MR-DC, they will be defined here as well. + +#### ***CA-ParametersEUTRA* information element** + +``` +-- ASN1START +-- TAG-CA-PARAMETERSEUTRA-START + +CA-ParametersEUTRA ::= SEQUENCE { + multipleTimingAdvance ENUMERATED {supported} OPTIONAL, + simultaneousRx-Tx ENUMERATED {supported} OPTIONAL, + supportedNAICS-2CRS-AP BIT STRING (SIZE (1..8)) OPTIONAL, + additionalRx-Tx-PerformanceReq ENUMERATED {supported} OPTIONAL, + ue-CA-PowerClass-N ENUMERATED {class2} OPTIONAL, + supportedBandwidthCombinationSetEUTRA-v1530 BIT STRING (SIZE (1..32)) OPTIONAL, + ... +} +``` + +``` + +CA-ParametersEUTRA-v1560 ::= SEQUENCE { + fd-MIMO-TotalWeightedLayers INTEGER (2..128) OPTIONAL +} + +CA-ParametersEUTRA-v1570 ::= SEQUENCE { + dl-1024QAM-TotalWeightedLayers INTEGER (0..10) OPTIONAL +} + +-- TAG-CA-PARAMETERSEUTRA-STOP +-- ASN1STOP + +``` + +#### CA-ParametersNR + +The IE *CA-ParametersNR* contains carrier aggregation and inter-frequency DAPS handover related capabilities that are defined per band combination. + +#### CA-ParametersNR information element + +``` + +-- ASN1START +-- TAG-CA-PARAMETERSNR-START + +CA-ParametersNR ::= SEQUENCE { + dummy ENUMERATED {supported} OPTIONAL, + parallelTxSRS-PUCCH-PUSCH ENUMERATED {supported} OPTIONAL, + parallelTxPRACH-SRS-PUCCH-PUSCH ENUMERATED {supported} OPTIONAL, + simultaneousRxBTxInterBandCA ENUMERATED {supported} OPTIONAL, + simultaneousRxBTxSUL ENUMERATED {supported} OPTIONAL, + diffNumerologyAcrossPUCCH-Group ENUMERATED {supported} OPTIONAL, + diffNumerologyWithinPUCCH-GroupSmallerSCS ENUMERATED {supported} OPTIONAL, + supportedNumberTAG ENUMERATED {n2, n3, n4} OPTIONAL, + ... +} + +CA-ParametersNR-v1540 ::= SEQUENCE { + simultaneousSRS-AssocCSI-RS-AllCC INTEGER (5..32) OPTIONAL, + csi-RS-IM-ReceptionForFeedbackPerBandComb SEQUENCE { + maxNumberSimultaneousNZP-CSI-RS-ActBWP-AllCC INTEGER (1..64) OPTIONAL, + totalNumberPortsSimultaneousNZP-CSI-RS-ActBWP-AllCC INTEGER (2..256) OPTIONAL, + } OPTIONAL, + simultaneousCSI-ReportsAllCC INTEGER (5..32) OPTIONAL, + dualPA-Architecture ENUMERATED {supported} OPTIONAL +} + +CA-ParametersNR-v1550 ::= SEQUENCE { + dummy ENUMERATED {supported} OPTIONAL +} + +CA-ParametersNR-v1560 ::= SEQUENCE { + diffNumerologyWithinPUCCH-GroupLargerSCS ENUMERATED {supported} OPTIONAL +} + +``` + +``` + +} + +CA-ParametersNR-v15g0 ::= SEQUENCE { + simultaneousRxBTxInterBandCAPerBandPair SimultaneousRxBTxPerBandPair OPTIONAL, + simultaneousRxBTxSULPerBandPair SimultaneousRxBTxPerBandPair OPTIONAL +} + +CA-ParametersNR-v1610 ::= SEQUENCE { + -- R1 9-3: Parallel MsgA and SRS/PUCCH/PUSCH transmissions across CCs in inter-band CA + parallelTxMsgA-SRS-PUCCH-PUSCH-r16 ENUMERATED {supported} OPTIONAL, + -- R1 9-4: MsgA operation in a band combination including SUL + msgA-SUL-r16 ENUMERATED {supported} OPTIONAL, + -- R1 10-9c: Joint search space group switching across multiple cells + jointSearchSpaceSwitchAcrossCells-r16 ENUMERATED {supported} OPTIONAL, + -- R1 14-5: Half-duplex UE behaviour in TDD CA for same SCS + half-DuplexTDD-CA-SameSCS-r16 ENUMERATED {supported} OPTIONAL, + -- R1 18-4: SCell dormancy within active time + scellDormancyWithinActiveTime-r16 ENUMERATED {supported} OPTIONAL, + -- R1 18-4a: SCell dormancy outside active time + scellDormancyOutsideActiveTime-r16 ENUMERATED {supported} OPTIONAL, + -- R1 18-6: Cross-carrier A-CSI RS triggering with different SCS + crossCarrierA-CSI-trigDiffSCS-r16 ENUMERATED {higherA-CSI-SCS, lowerA-CSI-SCS, both} OPTIONAL, + -- R1 18-6a: Default QCL assumption for cross-carrier A-CSI-RS triggering + defaultQCL-CrossCarrierA-CSI-Trig-r16 ENUMERATED {diffOnly, both} OPTIONAL, + -- R1 18-7: CA with non-aligned frame boundaries for inter-band CA + interCA-NonAlignedFrame-r16 ENUMERATED {supported} OPTIONAL, + simul-SRS-Trans-BC-r16 ENUMERATED {n2} OPTIONAL, + interFreqDAPS-r16 SEQUENCE { + interFreqAsyncDAPS-r16 ENUMERATED {supported} OPTIONAL, + interFreqDiffSCS-DAPS-r16 ENUMERATED {supported} OPTIONAL, + interFreqMultiUL-TransmissionDAPS-r16 ENUMERATED {supported} OPTIONAL, + interFreqSemiStaticPowerSharingDAPS-Model-r16 ENUMERATED {supported} OPTIONAL, + interFreqSemiStaticPowerSharingDAPS-Mode2-r16 ENUMERATED {supported} OPTIONAL, + interFreqDynamicPowerSharingDAPS-r16 ENUMERATED {short, long} OPTIONAL, + interFreqUL-TransCancellationDAPS-r16 ENUMERATED {supported} OPTIONAL + } + codebookParametersPerBC-r16 CodebookParameters-v1610 OPTIONAL, + -- R1 16-2a-10 Value of R for BD/CCE + blindDetectFactor-r16 INTEGER (1..2) OPTIONAL, + -- R1 11-2a: Capability on the number of CCs for monitoring a maximum number of BDs and non-overlapped CCEs per span when configured + -- with DL CA with Rel-16 PDCCH monitoring capability on all the serving cells + pdcch-MonitoringCA-r16 SEQUENCE { + maxNumberOfMonitoringCC-r16 INTEGER (2..16), + supportedSpanArrangement-r16 ENUMERATED {alignedOnly, alignedAndNonAligned} + } + -- R1 11-2c: Number of carriers for CCE/BD scaling with DL CA with mix of Rel. 16 and Rel. 15 PDCCH monitoring capabilities on + -- different carriers + pdcch-BlindDetectionCA-Mixed-r16 SEQUENCE { + pdcch-BlindDetectionCA1-r16 INTEGER (1..15), + pdcch-BlindDetectionCA2-r16 INTEGER (1..15), + supportedSpanArrangement-r16 ENUMERATED {alignedOnly, alignedAndNonAligned} + } +} + +``` + +``` + + } + -- R1 11-2d: Capability on the number of CCs for monitoring a maximum number of BDs and non-overlapped CCEs per span for MCG and for + -- SCG when configured for NR-DC operation with Rel-16 PDCCH monitoring capability on all the serving cells + pdcch-BlindDetectionMCG-UE-r16 INTEGER (1..14) OPTIONAL, + pdcch-BlindDetectionSCG-UE-r16 INTEGER (1..14) OPTIONAL, + -- R1 11-2e: Number of carriers for CCE/BD scaling for MCG and for SCG when configured for NR-DC operation with mix of Rel. 16 and + -- Rel. 15 PDCCH monitoring capabilities on different carriers + pdcch-BlindDetectionMCG-UE-Mixed-r16 SEQUENCE { + pdcch-BlindDetectionMCG-UE1-r16 INTEGER (0..15), + pdcch-BlindDetectionMCG-UE2-r16 INTEGER (0..15) + } + pdcch-BlindDetectionSCG-UE-Mixed-r16 SEQUENCE { + pdcch-BlindDetectionSCG-UE1-r16 INTEGER (0..15), + pdcch-BlindDetectionSCG-UE2-r16 INTEGER (0..15) + } + -- R1 18-5 cross-carrier scheduling with different SCS in DL CA + crossCarrierSchedulingDL-DiffSCS-r16 ENUMERATED {low-to-high, high-to-low, both} OPTIONAL, + -- R1 18-5a Default QCL assumption for cross-carrier scheduling + crossCarrierSchedulingDefaultQCL-r16 ENUMERATED {diff-only, both} OPTIONAL, + -- R1 18-5b cross-carrier scheduling with different SCS in UL CA + crossCarrierSchedulingUL-DiffSCS-r16 ENUMERATED {low-to-high, high-to-low, both} OPTIONAL, + -- R1 13.19a Simultaneous positioning SRS and MIMO SRS transmission for a given BC + simul-SRS-MIMO-Trans-BC-r16 ENUMERATED {n2} OPTIONAL, + -- R1 16-3a, 16-3a-1, 16-3b, 16-3b-1: New Individual Codebook + codebookParametersAdditionPerBC-r16 CodebookParametersAdditionPerBC-r16 OPTIONAL, + -- R1 16-8: Mixed codebook + codebookComboParametersAdditionPerBC-r16 CodebookComboParametersAdditionPerBC-r16 OPTIONAL +} + +CA-ParametersNR-v1630 ::= SEQUENCE { + -- R1 22-5b: Simultaneous transmission of SRS for antenna switching and SRS for CB/NCB /BM for inter-band UL CA + -- R1 22-5d: Simultaneous transmission of SRS for antenna switching for inter-band UL CA + simulTX-SRS-AntSwitchingInterBandUL-CA-r16 SimulSRS-ForAntennaSwitching-r16 OPTIONAL, + -- R4 8-5: supported beam management type for inter-band CA + beamManagementType-r16 ENUMERATED {ibm, dummy} OPTIONAL, + -- R4 7-3a: UL frequency separation class with aggregate BW and Gap BW + intraBandFreqSeparationUL-AggBW-GapBW-r16 ENUMERATED {classI, classII, classIII} OPTIONAL, + -- RAN 89: Case B in case of inter-band CA with non-aligned frame boundaries + interCA-NonAlignedFrame-B-r16 ENUMERATED {supported} OPTIONAL +} + +CA-ParametersNR-v1640 ::= SEQUENCE { + -- R4 7-5: Support of reporting UL Tx DC locations for uplink intra-band CA. + uplinkTxDC-TwoCarrierReport-r16 ENUMERATED {supported} OPTIONAL, + -- RAN 22-6: Support of up to 3 different numerologies in the same NR PUCCH group for NR part of EN-DC, NGEN-DC, NE-DC and NR-CA + -- where UE is not configured with two NR PUCCH groups + maxUpTo3Diff-NumerologiesConfigSinglePUCCH-grp-r16 PUCCH-Grp-CarrierTypes-r16 OPTIONAL, + -- RAN 22-6a: Support of up to 4 different numerologies in the same NR PUCCH group for NR part of EN-DC, NGEN-DC, NE-DC and NR-CA + -- where UE is not configured with two NR PUCCH groups + maxUpTo4Diff-NumerologiesConfigSinglePUCCH-grp-r16 PUCCH-Grp-CarrierTypes-r16 OPTIONAL, + -- RAN 22-7: Support two PUCCH groups for NR-CA with 3 or more bands with at least two carrier types + +``` + +``` + +twoPUCCH-Grp-ConfigurationsList-r16 SEQUENCE (SIZE (1..maxTwoPUCCH-Grp-ConfigList-r16)) OF TwoPUCCH-Grp-Configurations-r16 OPTIONAL, +-- R1 22-7a: Different numerology across NR PUCCH groups +diffNumerologyAcrossPUCCH-Group-CarrierTypes-r16 ENUMERATED {supported} OPTIONAL, +-- R1 22-7b: Different numerologies across NR carriers within the same NR PUCCH group, with PUCCH on a carrier of smaller SCS +diffNumerologyWithinPUCCH-GroupSmallerSCS-CarrierTypes-r16 ENUMERATED {supported} OPTIONAL, +-- R1 22-7c: Different numerologies across NR carriers within the same NR PUCCH group, with PUCCH on a carrier of larger SCS +diffNumerologyWithinPUCCH-GroupLargerSCS-CarrierTypes-r16 ENUMERATED {supported} OPTIONAL, +-- R1 11-2f: add the replicated FGs of 11-2a/c with restriction for non-aligned span case +-- with DL CA with Rel-16 PDCCH monitoring capability on all the serving cells +pdcch-MonitoringCA-NonAlignedSpan-r16 INTEGER (2..16) OPTIONAL, +-- R1 11-2g: add the replicated FGs of 11-2a/c with restriction for non-aligned span case +pdcch-BlindDetectionCA-Mixed-NonAlignedSpan-r16 SEQUENCE { + pdcch-BlindDetectionCA1-r16 INTEGER (1..15), + pdcch-BlindDetectionCA2-r16 INTEGER (1..15) +} OPTIONAL +} + +CA-ParametersNR-v1690 ::= SEQUENCE { + csi-ReportingCrossPUCCH-Grp-r16 SEQUENCE { + computationTimeForA-CSI-r16 ENUMERATED {sameAsNoCross, relaxed}, + additionalSymbols-r16 SEQUENCE { + scs-15kHz-additionalSymbols-r16 ENUMERATED {s14, s28} OPTIONAL, + scs-30kHz-additionalSymbols-r16 ENUMERATED {s14, s28} OPTIONAL, + scs-60kHz-additionalSymbols-r16 ENUMERATED {s14, s28, s56} OPTIONAL, + scs-120kHz-additionalSymbols-r16 ENUMERATED {s14, s28, s56} OPTIONAL + } OPTIONAL, + sp-CSI-ReportingOnPUCCH-r16 ENUMERATED {supported} OPTIONAL, + sp-CSI-ReportingOnPUSCH-r16 ENUMERATED {supported} OPTIONAL, + carrierTypePairList-r16 SEQUENCE (SIZE (1..maxCarrierTypePairList-r16)) OF CarrierTypePair-r16 + } OPTIONAL +} + +CA-ParametersNR-v16a0 ::= SEQUENCE { + pdcch-BlindDetectionMixedList-r16 SEQUENCE (SIZE (1..maxNrofPdcch-BlindDetectionMixed-1-r16)) OF PDCCH-BlindDetectionMixedList-r16 +} + +CA-ParametersNR-v1700 ::= SEQUENCE { + -- R1 23-9-1: Basic Features of Further Enhanced Port-Selection Type II Codebook (FeType-II) per band combination information + codebookParametersfetype2PerBC-r17 CodebookParametersfetype2PerBC-r17 OPTIONAL, + -- R4 18-4: Support of enhanced Demodulation requirements for CA in HST SFN FR1 + demodulationEnhancementCA-r17 ENUMERATED {supported} OPTIONAL, + -- R4 20-1: Maximum uplink duty cycle for NR inter-band CA power class 2 + maxUplinkDutyCycle-interBandCA-PC2-r17 ENUMERATED {n50, n60, n70, n80, n90, n100} OPTIONAL, + -- R4 20-2: Maximum uplink duty cycle for NR SUL combination power class 2 + maxUplinkDutyCycle-SULcombination-PC2-r17 ENUMERATED {n50, n60, n70, n80, n90, n100} OPTIONAL, + beamManagementType-CBM-r17 ENUMERATED {supported} OPTIONAL, + -- R1 25-18: Parallel PUCCH and PUSCH transmission across CCs in inter-band CA + parallelTxPUCCH-PUSCH-r17 ENUMERATED {supported} OPTIONAL, + -- R1 23-9-5 Active CSI-RS resources and ports for mixed codebook types in any slot per band combination + codebookComboParameterMixedTypePerBC-r17 CodebookComboParameterMixedTypePerBC-r17 OPTIONAL, + -- R1 23-7-1 Basic Features of CSI Enhancement for Multi-TRP + +``` + +``` + +mTRP-CSI-EnhancementPerBC-r17 SEQUENCE { + maxNumNZP-CSI-RS-r17 INTEGER (2..8), + cSI-Report-mode-r17 ENUMERATED {model, mode2, both}, + supportedComboAcrossCCs-r17 SEQUENCE (SIZE (1..16)) OF CSI-MultiTRP-SupportedCombinations-r17, + codebookMode-NCJT-r17 ENUMERATED{model,modelAnd2} +} OPTIONAL, +-- R1 23-7-1b Active CSI-RS resources and ports in the presence of multi-TRP CSI +codebookComboParameterMultiTRP-PerBC-r17 CodebookComboParameterMultiTRP-PerBC-r17 OPTIONAL, +-- R1 24-8b: 32 DL HARQ processes for FR 2-2 - maximum number of component carriers +maxCC-32-DL-HARQ-ProcessFR2-2-r17 ENUMERATED {n1, n2, n3, n4, n6, n8, n16, n32} OPTIONAL, +-- R1 24-9b: 32 UL HARQ processes for FR 2-2 - maximum number of component carriers +maxCC-32-UL-HARQ-ProcessFR2-2-r17 ENUMERATED {n1, n2, n3, n4, n5, n8, n16, n32} OPTIONAL, +-- R1 34-2: Cross-carrier scheduling from SCell to PCell/PSCell (Type B) +crossCarrierSchedulingSCell-SpCellTypeB-r17 CrossCarrierSchedulingSCell-SpCell-r17 OPTIONAL, +-- R1 34-1: Cross-carrier scheduling from SCell to PCell/PSCell with search space restrictions (Type A) +crossCarrierSchedulingSCell-SpCellTypeA-r17 CrossCarrierSchedulingSCell-SpCell-r17 OPTIONAL, +-- R1 34-1a: DCI formats on PCell/PSCell USS set(s) support +dci-FormatsPCellPSCellUSS-Sets-r17 ENUMERATED {supported} OPTIONAL, +-- R1 34-3: Disabling scaling factor alpha when sSCell is deactivated +disablingScalingFactorDeactSCell-r17 ENUMERATED {supported} OPTIONAL, +-- R1 34-4: Disabling scaling factor alpha when sSCell is deactivated +disablingScalingFactorDormantSCell-r17 ENUMERATED {supported} OPTIONAL, +-- R1 34-5: Non-aligned frame boundaries between PCell/PSCell and sSCell +non-AlignedFrameBoundaries-r17 SEQUENCE { + scs15kHz-15kHz-r17 BIT STRING (SIZE (1..496)) OPTIONAL, + scs15kHz-30kHz-r17 BIT STRING (SIZE (1..496)) OPTIONAL, + scs15kHz-60kHz-r17 BIT STRING (SIZE (1..496)) OPTIONAL, + scs30kHz-30kHz-r17 BIT STRING (SIZE (1..496)) OPTIONAL, + scs30kHz-60kHz-r17 BIT STRING (SIZE (1..496)) OPTIONAL, + scs60kHz-60kHz-r17 BIT STRING (SIZE (1..496)) OPTIONAL +} OPTIONAL +} + +CA-ParametersNR-v1720 ::= SEQUENCE { +-- R1 39-1: Parallel SRS and PUCCH/PUSCH transmission across CCs in intra-band non-contiguous CA +parallelTxSRS-PUCCH-PUSCH-intraBand-r17 ENUMERATED {supported} OPTIONAL, +-- R1 39-2: Parallel PRACH and SRS/PUCCH/PUSCH transmissions across CCs in intra-band non-contiguous CA +parallelTxPRACH-SRS-PUCCH-PUSCH-intraBand-r17 ENUMERATED {supported} OPTIONAL, +-- R1 25-9: Semi-static PUCCH cell switching for a single PUCCH group only +semiStaticPUCCH-CellSwitchSingleGroup-r17 SEQUENCE { + pucch-Group-r17 ENUMERATED {primaryGroupOnly, secondaryGroupOnly, eitherPrimaryOrSecondaryGroup}, + pucch-Group-Config-r17 PUCCH-Group-Config-r17 +} OPTIONAL, +-- R1 25-9a: Semi-static PUCCH cell switching for two PUCCH groups +semiStaticPUCCH-CellSwitchTwoGroups-r17 SEQUENCE (SIZE (1..maxTwoPUCCH-Grp-ConfigList-r17)) OF TwoPUCCH-Grp-Configurations-r17 OPTIONAL, +-- R1 25-10: PUCCH cell switching based on dynamic indication for same length of overlapping PUCCH slots/sub-slots for a single +-- PUCCH group only +dynamicPUCCH-CellSwitchSameLengthSingleGroup-r17 SEQUENCE { + pucch-Group-r17 ENUMERATED {primaryGroupOnly, secondaryGroupOnly, eitherPrimaryOrSecondaryGroup}, + pucch-Group-Config-r17 PUCCH-Group-Config-r17 +} OPTIONAL, +} + +``` + +``` + +-- R1 25-10a: PUCCH cell switching based on dynamic indication for different length of overlapping PUCCH slots/sub-slots +-- for a single PUCCH group only +dynamicPUCCH-CellSwitchDiffLengthSingleGroup-r17 SEQUENCE { + pucch-Group-r17 ENUMERATED {primaryGroupOnly, secondaryGroupOnly, eitherPrimaryOrSecondaryGroup}, + pucch-Group-Config-r17 PUCCH-Group-Config-r17 +} OPTIONAL, +-- R1 25-10b: PUCCH cell switching based on dynamic indication for same length of overlapping PUCCH slots/sub-slots for two PUCCH +-- groups +dynamicPUCCH-CellSwitchSameLengthTwoGroups-r17 SEQUENCE (SIZE (1..maxTwoPUCCH-Grp-ConfigList-r17)) OF TwoPUCCH-Grp-Configurations-r17 + OPTIONAL, +-- R1 25-10c: PUCCH cell switching based on dynamic indication for different length of overlapping PUCCH slots/sub-slots for two +-- PUCCH groups +dynamicPUCCH-CellSwitchDiffLengthTwoGroups-r17 SEQUENCE (SIZE (1..maxTwoPUCCH-Grp-ConfigList-r17)) OF TwoPUCCH-Grp-Configurations-r17 + OPTIONAL, +-- R1 33-2a: ACK/NACK based HARQ-ACK feedback and RRC-based enabling/disabling ACK/NACK-based +-- feedback for dynamic scheduling for multicast +ack-NACK-FeedbackForMulticast-r17 ENUMERATED {supported} OPTIONAL, +-- R1 33-2d: PTP retransmission for multicast dynamic scheduling +ptp-Retx-Multicast-r17 ENUMERATED {supported} OPTIONAL, +-- R1 33-4: NACK-only based HARQ-ACK feedback for RRC-based enabling/disabling multicast with ACK/NACK transforming +nack-OnlyFeedbackForMulticast-r17 ENUMERATED {supported} OPTIONAL, +-- R1 33-4a: NACK-only based HARQ-ACK feedback for multicast corresponding to a specific sequence or a PUCCH transmission +nack-OnlyFeedbackSpecificResourceForMulticast-r17 ENUMERATED {supported} OPTIONAL, +-- R1 33-5-1a: ACK/NACK based HARQ-ACK feedback and RRC-based enabling/disabling ACK/NACK-based feedback +-- for SPS group-common PDSCH for multicast +ack-NACK-FeedbackForSPS-Multicast-r17 ENUMERATED {supported} OPTIONAL, +-- R1 33-5-1d: PTP retransmission for SPS group-common PDSCH for multicast +ptp-Retx-SPS-Multicast-r17 ENUMERATED {supported} OPTIONAL, +-- R4 26-1: Higher Power Limit CA DC +higherPowerLimit-r17 ENUMERATED {supported} OPTIONAL, +-- R1 39-4: Parallel MsgA and SRS/PUCCH/PUSCH transmissions across CCs in intra-band non-contiguous CA +parallelTxMsgA-SRS-PUCCH-PUSCH-intraBand-r17 ENUMERATED {supported} OPTIONAL, +-- R1 24-11a: Capability on the number of CCs for monitoring a maximum number of BDs and non-overlapped CCEs per span when +-- configured with DL CA with Rel-17 PDCCH monitoring capability on all the serving cells +pdcch-MonitoringCA-r17 INTEGER (4..16) OPTIONAL, +-- R1 24-11f: Capability on the number of CCs for monitoring a maximum number of BDs and non-overlapped CCEs for MCG and for SCG +-- when configured for NR-DC operation with Rel-17 PDCCH monitoring capability on all the serving cells +pdcch-BlindDetectionMCG-SCG-List-r17 SEQUENCE (SIZE (1..maxNrofPdcch-BlindDetection-r17)) OF PDCCH-BlindDetectionMCG-SCG-r17 + OPTIONAL, +-- R1 24-11c: Number of carriers for CCE/BD scaling with DL CA with mix of Rel. 17 and Rel. 15 PDCCH monitoring capabilities on +-- different Carriers +-- R1 24-11g: Number of carriers for CCE/BD scaling for MCG and for SCG when configured for NR-DC operation with mix of Rel. 17 and +-- Rel. 15 PDCCH monitoring capabilities on different carriers +pdcch-BlindDetectionMixedList1-r17 SEQUENCE (SIZE (1..maxNrofPdcch-BlindDetection-r17)) OF PDCCH-BlindDetectionMixed-r17 + OPTIONAL, +-- R1 24-11d: Number of carriers for CCE/BD scaling with DL CA with mix of Rel. 17 and Rel. 16 PDCCH monitoring capabilities on +-- different Carriers +-- R1 24-11h: Number of carriers for CCE/BD scaling for MCG and for SCG when configured for NR-DC operation with mix of Rel. 17 and +-- Rel. 16 PDCCH monitoring capabilities on different carriers +pdcch-BlindDetectionMixedList2-r17 SEQUENCE (SIZE (1..maxNrofPdcch-BlindDetection-r17)) OF PDCCH-BlindDetectionMixed-r17 + OPTIONAL, + +``` + +``` + +-- R1 24-11e: Number of carriers for CCE/BD scaling with DL CA with mix of Rel. 17, Rel. 16 and Rel. 15 PDCCH monitoring +-- capabilities on different carriers +-- R1 24-11i: Number of carriers for CCE/BD scaling for MCG and for SCG when configured for NR-DC operation with mix of Rel. 17, +-- Rel. 16 and Rel. 15 PDCCH monitoring capabilities on different carriers +pdcch-BlindDetectionMixedList3-r17 SEQUENCE (SIZE (1..maxNrofPdcch-BlindDetection-r17)) OF PDCCCH-BlindDetectionMixed1-r17 + OPTIONAL +} + +CA-ParametersNR-v1730 ::= SEQUENCE { +-- R1 30-4a: DM-RS bundling for PUSCH repetition type A (per BC) +dmrs-BundlingPUSCH-RepTypeAPerBC-r17 ENUMERATED {supported} OPTIONAL, +-- R1 30-4b: DM-RS bundling for PUSCH repetition type B (per BC) +dmrs-BundlingPUSCH-RepTypeBPerBC-r17 ENUMERATED {supported} OPTIONAL, +-- R1 30-4c: DM-RS bundling for TB processing over multi-slot PUSCH (per BC) +dmrs-BundlingPUSCH-multiSlotPerBC-r17 ENUMERATED {supported} OPTIONAL, +-- R1 30-4d: DMRS bundling for PUCCH repetitions (per BC) +dmrs-BundlingPUCCH-RepPerBC-r17 ENUMERATED {supported} OPTIONAL, +-- R1 30-4g: Restart DM-RS bundling (per BC) +dmrs-BundlingRestartPerBC-r17 ENUMERATED {supported} OPTIONAL, +-- R1 30-4h: DM-RS bundling for non-back-to-back transmission (per BC) +dmrs-BundlingNonBackToBackTX-PerBC-r17 ENUMERATED {supported} OPTIONAL, +-- R1 39-3-1: Stay on the target CC for SRS carrier switching +stayOnTargetCC-SRS-CarrierSwitch-r17 ENUMERATED {supported} OPTIONAL, +-- R1 33-3-3a: FDM-ed Type-1 and Type-2 HARQ-ACK codebooks for multiplexing HARQ-ACK for unicast and HARQ-ACK for multicast +fdm-CodebookForMux-UnicastMulticastHARQ-ACK-r17 ENUMERATED {supported} OPTIONAL, +-- R1 33-3-3b: Mode 2 TDM-ed Type-1 and Type-2 HARQ-ACK codebook for multiplexing HARQ-ACK for unicast and HARQ-ACK for multicast +mode2-TDM-CodebookForMux-UnicastMulticastHARQ-ACK-r17 ENUMERATED {supported} OPTIONAL, +-- R1 33-3-4: Mode 1 for type1 codebook generation +model-ForType1-CodebookGeneration-r17 ENUMERATED {supported} OPTIONAL, +-- R1 33-5-1j: NACK-only based HARQ-ACK feedback for multicast corresponding to a specific sequence or a PUCCH transmission +-- for SPS group-common PDSCH for multicast +nack-OnlyFeedbackSpecificResourceForSPS-Multicast-r17 ENUMERATED {supported} OPTIONAL, +-- R1 33-8-2: Up to 2 PUCCH resources configuration for multicast feedback for dynamically scheduled multicast +multiPUCCH-ConfigForMulticast-r17 ENUMERATED {supported} OPTIONAL, +-- R1 33-8-3: PUCCH resource configuration for multicast feedback for SPS GC-PDSCH +pucch-ConfigForSPS-Multicast-r17 ENUMERATED {supported} OPTIONAL, +-- The following parameter is associated with R1 33-2a, R1 33-3-3a, and R1 33-3-3b, and is not a RAN1 FG. +maxNumberG-RNTI-HARQ-ACK-Codebook-r17 INTEGER (1..4) OPTIONAL, +-- R1 33-3-5: Feedback multiplexing for unicast PDSCH and group-common PDSCH for multicast with same priority and different codebook +-- type +mux-HARQ-ACK-UnicastMulticast-r17 ENUMERATED {supported} OPTIONAL +} + +CA-ParametersNR-v1740 ::= SEQUENCE { +-- R1 33-5-1f: NACK-only based HARQ-ACK feedback for multicast RRC-based enabling/disabling NACK-only based feedback +-- for SPS group-common PDSCH for multicast +nack-OnlyFeedbackForSPS-Multicast-r17 ENUMERATED {supported} OPTIONAL, +-- R1 33-8-1: PUCCH resource configuration for multicast feedback for dynamically scheduled multicast + +``` + +``` + +singlePUCCH-ConfigForMulticast-r17 ENUMERATED {supported} OPTIONAL +} + +CA-ParametersNR-v1760 ::= SEQUENCE { + prioSCellPRACH-OverSP-PeriodicSRS-Support-r17 ENUMERATED {supported} OPTIONAL +} + +CA-ParametersNR-v1770 ::= SEQUENCE { + parallelTxPUCCH-PUSCH-SamePriority-r17 ENUMERATED {supported} OPTIONAL +} + +CA-ParametersNR-v1800 ::= SEQUENCE { + codebookParametersetype2DopplerCSI-PerBC-r18 CodebookParametersetype2DopplerCSI-r18 OPTIONAL, + codebookParametersfetype2DopplerCSI-PerBC-r18 CodebookParametersfetype2DopplerCSI-r18 OPTIONAL, + -- R1 49-1b: Multi-cell PDSCH scheduling by DCI format 1_3 on a scheduling cell not included in a set of cells with different + -- SCS/carrier type between scheduling cell and cells in the set + multiCell-PDSCH-DCI-1-3-DiffSCS-r18 SEQUENCE { + coScheduledCellSCS-r18 ENUMERATED {lowScheduling-highScheduled, highScheduling-lowScheduled, both}, + combinationCarrierType-r18 SEQUENCE (SIZE(1..maxSchedulingBandCombination-r18)) OF + CombinationCarrierType-r18, + maxNumberCoScheduledCell-r18 INTEGER (2..4), + maxNumberSetsOfCellAcrossPUCCH-Group-r18 INTEGER (1..8), + maxNumberSetsOfCellScheduling-r18 INTEGER (1..4), + harqFeedbackType-r18 ENUMERATED {type1, type2, type1And2}, + coScheduledCellIndicationScheme-r18 ENUMERATED {fdra, cellInd, both} + } OPTIONAL, + -- R1 55-6a: Capability on the number of CCs for monitoring a maximum number of BDs and non-overlapped CCEs per span when configured + -- with DL CA with Rel-16 PDCCH monitoring capability on all the serving cells + pdcch-MonitoringCA-r18 SEQUENCE { + maxNumberOfMonitoringCC-r18 INTEGER (2..16), + supportedSpanArrangement-r18 ENUMERATED {alignedOnly, alignedAndNonAligned} + } OPTIONAL, + -- R1 55-6c: Number of carriers for CCE/BD scaling with DL CA with mix of Rel. 16 and Rel. 15 PDCCH monitoring capabilities on + -- different carriers + pdcch-BlindDetectionCA-Mixed-r18 SEQUENCE { + blindDetectionCA-Mixed-r18 SEQUENCE(SIZE (1..maxNrofPdcch-BlindDetection-r17)) OF + PDCCH-BlindDetectionCA-Mixed-r18, + supportedSpanArrangement-r18 ENUMERATED{ alignedOnly, alignedAndNonAligned } + } OPTIONAL, + -- R1 55-6e: Number of carriers for CCE/BD scaling for MCG and for SCG when configured for NR-DC operation with mix of Rel. 16 + -- and Rel. 15 PDCCH monitoring capabilities on different carriers + pdcch-BlindDetectionMCG-SCG-List-r18 SEQUENCE(SIZE (1..maxNrofPdcch-BlindDetection-r17)) OF PDCCH-BlindDetectionMCG-SCG-r18 + OPTIONAL, + -- R1 55-6g: Number of carriers for CCE/BD scaling with DL CA with mix of Rel. 16 and Rel. 15 PDCCH monitoring capabilities on + -- different carriers with restriction for non-aligned span case + pdcch-BlindDetectionCA-Mixed-NonAlignedSpan-r18 SEQUENCE(SIZE (1..maxNrofPdcch-BlindDetection-r17)) OF + PDCCH-BlindDetectionCA-Mixed-r18 OPTIONAL, + -- R1 55-6f: Capability on the number of CCs for monitoring a maximum number of BDs and non-overlapped CCEs per span when configured + -- with DL CA with Rel-16 PDCCH monitoring capability on all the serving cells with restriction for non-aligned span case + pdcch-MonitoringCA-NonAlignedSpan-r18 INTEGER (2..16) OPTIONAL, + -- R4 33-1: Support of intra-band non-collocated NR CA operation + +``` + +``` + + intraBandNR-CA-non-collocated-r18 ENUMERATED {supported} OPTIONAL + } + + CrossCarrierSchedulingSCell-SpCell-r17 ::= SEQUENCE { + supportedSCS-Combinations-r17 SEQUENCE { + scs15kHz-15kHz-r17 ENUMERATED {supported} OPTIONAL, + scs15kHz-30kHz-r17 ENUMERATED {supported} OPTIONAL, + scs15kHz-60kHz-r17 ENUMERATED {supported} OPTIONAL, + scs30kHz-30kHz-r17 BIT STRING (SIZE (1..496)) OPTIONAL, + scs30kHz-60kHz-r17 BIT STRING (SIZE (1..496)) OPTIONAL, + scs60kHz-60kHz-r17 BIT STRING (SIZE (1..496)) OPTIONAL + }, + pdcch-MonitoringOccasion-r17 ENUMERATED {val1, val2} + } + + PDCCH-BlindDetectionMixedList-r16 ::= SEQUENCE { + pdcch-BlindDetectionCA-MixedExt-r16 CHOICE { + pdcch-BlindDetectionCA-Mixed-v16a0 PDCCH-BlindDetectionCA-MixedExt-r16, + pdcch-BlindDetectionCA-Mixed-NonAlignedSpan-v16a0 PDCCH-BlindDetectionCA-MixedExt-r16 + } OPTIONAL, + pdcch-BlindDetectionCG-UE-MixedExt-r16 SEQUENCE { + pdcch-BlindDetectionMCG-UE-Mixed-v16a0 PDCCH-BlindDetectionCG-UE-MixedExt-r16, + pdcch-BlindDetectionSCG-UE-Mixed-v16a0 PDCCH-BlindDetectionCG-UE-MixedExt-r16 + } OPTIONAL + } + + PDCCH-BlindDetectionCA-MixedExt-r16 ::= SEQUENCE { + pdcch-BlindDetectionCA1-r16 INTEGER (1..15), + pdcch-BlindDetectionCA2-r16 INTEGER (1..15) + } + + PDCCH-BlindDetectionCG-UE-MixedExt-r16 ::= SEQUENCE { + pdcch-BlindDetectionCG-UE1-r16 INTEGER (0..15), + pdcch-BlindDetectionCG-UE2-r16 INTEGER (0..15) + } + + PDCCH-BlindDetectionMCG-SCG-r17 ::= SEQUENCE { + pdcch-BlindDetectionMCG-UE-r17 INTEGER (1..15), + pdcch-BlindDetectionSCG-UE-r17 INTEGER (1..15) + } + + PDCCH-BlindDetectionMixed-r17 ::= SEQUENCE { + pdcch-BlindDetectionCA-Mixed-r17 PDCCH-BlindDetectionCA-Mixed-r17 OPTIONAL, + pdcch-BlindDetectionCG-UE-Mixed-r17 SEQUENCE { + pdcch-BlindDetectionMCG-UE-Mixed-v17 PDCCH-BlindDetectionCG-UE-Mixed-r17, + pdcch-BlindDetectionSCG-UE-Mixed-v17 PDCCH-BlindDetectionCG-UE-Mixed-r17 + } OPTIONAL + } + + PDCCH-BlindDetectionCG-UE-Mixed-r17 ::= SEQUENCE { + pdcch-BlindDetectionCG-UE1-r17 INTEGER (0..15), + +``` + +``` + + pdcch-BlindDetectionCG-UE2-r17 INTEGER (0..15) + } + + PDCCH-BlindDetectionCA-Mixed-r17 ::= SEQUENCE { + pdcch-BlindDetectionCA1-r17 INTEGER (1..15) OPTIONAL, + pdcch-BlindDetectionCA2-r17 INTEGER (1..15) OPTIONAL + } + + PDCCH-BlindDetectionMixed1-r17 ::= SEQUENCE { + pdcch-BlindDetectionCA-Mixed1-r17 PDCCH-BlindDetectionCA-Mixed1-r17 OPTIONAL, + pdcch-BlindDetectionCG-UE-Mixed1-r17 SEQUENCE { + pdcch-BlindDetectionMCG-UE-Mixed1-v17 PDCCH-BlindDetectionCG-UE-Mixed1-r17, + pdcch-BlindDetectionSCG-UE-Mixed1-v17 PDCCH-BlindDetectionCG-UE-Mixed1-r17 + } OPTIONAL + } + + PDCCH-BlindDetectionCG-UE-Mixed1-r17 ::= SEQUENCE { + pdcch-BlindDetectionCG-UE1-r17 INTEGER (0..15), + pdcch-BlindDetectionCG-UE2-r17 INTEGER (0..15), + pdcch-BlindDetectionCG-UE3-r17 INTEGER (0..15) + } + + PDCCH-BlindDetectionCA-Mixed1-r17 ::= SEQUENCE { + pdcch-BlindDetectionCA1-r17 INTEGER (1..15) OPTIONAL, + pdcch-BlindDetectionCA2-r17 INTEGER (1..15) OPTIONAL, + pdcch-BlindDetectionCA3-r17 INTEGER (1..15) OPTIONAL + } + + PDCCH-BlindDetectionMCG-SCG-r18 ::= SEQUENCE { + pdcch-BlindDetectionMCG-UE-Mixed-r18 PDCCH-BlindDetectionCG-UE-Mixed-r18, + pdcch-BlindDetectionSCG-UE-Mixed-r18 PDCCH-BlindDetectionCG-UE-Mixed-r18 + } + + PDCCH-BlindDetectionCA-Mixed-r18 ::= SEQUENCE { + pdcch-BlindDetectionCA1-r18 INTEGER (1..15), + pdcch-BlindDetectionCA2-r18 INTEGER (1..15) + } + + PDCCH-BlindDetectionCG-UE-Mixed-r18 ::= SEQUENCE { + pdcch-BlindDetectionCG-UE1-r18 INTEGER (0..15), + pdcch-BlindDetectionCG-UE2-r18 INTEGER (0..15) + } + + SimulSRS-ForAntennaSwitching-r16 ::= SEQUENCE { + supportSRS-xTyR-xLessThanY-r16 ENUMERATED {supported} OPTIONAL, + supportSRS-xTyR-xEqualToY-r16 ENUMERATED {supported} OPTIONAL, + supportSRS-AntennaSwitching-r16 ENUMERATED {supported} OPTIONAL + } + + TwoPUCCH-Grp-Configurations-r16 ::= SEQUENCE { + pucch-PrimaryGroupMapping-r16 TwoPUCCH-Grp-ConfigParams-r16, + pucch-SecondaryGroupMapping-r16 TwoPUCCH-Grp-ConfigParams-r16 + } + +``` + +``` + +} + +TwoPUCCH-Grp-Configurations-r17 := SEQUENCE { + primaryPUCCH-GroupConfig-r17 PUCCH-Group-Config-r17, + secondaryPUCCH-GroupConfig-r17 PUCCH-Group-Config-r17 +} + +TwoPUCCH-Grp-ConfigParams-r16 := SEQUENCE { + pucch-GroupMapping-r16 PUCCH-Grp-CarrierTypes-r16, + pucch-TX-r16 PUCCH-Grp-CarrierTypes-r16 +} + +CarrierTypePair-r16 := SEQUENCE { + carrierForCSI-Measurement-r16 PUCCH-Grp-CarrierTypes-r16, + carrierForCSI-Reporting-r16 PUCCH-Grp-CarrierTypes-r16 +} + +PUCCH-Grp-CarrierTypes-r16 := SEQUENCE { + fr1-NonSharedTDD-r16 ENUMERATED {supported} OPTIONAL, + fr1-SharedTDD-r16 ENUMERATED {supported} OPTIONAL, + fr1-NonSharedFDD-r16 ENUMERATED {supported} OPTIONAL, + fr2-r16 ENUMERATED {supported} OPTIONAL +} + +PUCCH-Group-Config-r17 := SEQUENCE { + fr1-FR1-NonSharedTDD-r17 ENUMERATED {supported} OPTIONAL, + fr2-FR2-NonSharedTDD-r17 ENUMERATED {supported} OPTIONAL, + fr1-FR2-NonSharedTDD-r17 ENUMERATED {supported} OPTIONAL +} + +-- TAG-CA-PARAMETERSNR-STOP +-- ASN1STOP + +``` + +#### | CA-ParametersNR field description | |------------------------------------------| |------------------------------------------| + +### | | |--------------------------------| | codebookParametersPerBC | |--------------------------------| + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| For a given supported band combination, this field indicates the alternative list of SupportedCSI-RS-Resource supported for each codebook type, amongst the supported CSI-RS resources included in codebookParametersPerBand in MIMO-ParametersPerBand . | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +#### — CA-ParametersNRDC + +The IE *CA-ParametersNRDC* contains dual connectivity related capabilities that are defined per band combination. + +#### CA-ParametersNRDC information element + +``` + +-- ASN1START +-- TAG-CA-PARAMETERS-NRDC-START + +``` + +``` + +CA-ParametersNRDC ::= + ca-ParametersNR-ForDC + ca-ParametersNR-ForDC-v1540 + ca-ParametersNR-ForDC-v1550 + ca-ParametersNR-ForDC-v1560 + featureSetCombinationDC +} + +CA-ParametersNRDC-v15g0 ::= + ca-ParametersNR-ForDC-v15g0 +} + +CA-ParametersNRDC-v1610 ::= SEQUENCE { + -- R1 18-1: Semi-static power sharing model between MCG and SCG cells of same FR for NR dual connectivity + intraFR-NR-DC-PwrSharingModel1-r16 ENUMERATED {supported} OPTIONAL, + -- R1 18-1a: Semi-static power sharing mode 2 between MCG and SCG cells of same FR for NR dual connectivity + intraFR-NR-DC-PwrSharingMode2-r16 ENUMERATED {supported} OPTIONAL, + -- R1 18-1b: Dynamic power sharing between MCG and SCG cells of same FR for NR dual connectivity + intraFR-NR-DC-DynamicPwrSharing-r16 ENUMERATED {short, long} OPTIONAL, + asynNRDC-r16 ENUMERATED {supported} OPTIONAL +} + +CA-ParametersNRDC-v1630 ::= + ca-ParametersNR-ForDC-v1610 + ca-ParametersNR-ForDC-v1630 +} + +CA-ParametersNRDC-v1640 ::= + ca-ParametersNR-ForDC-v1640 +} + +CA-ParametersNRDC-v1650 ::= + supportedCellGrouping-r16 +} + +CA-ParametersNRDC-v16a0 ::= + ca-ParametersNR-ForDC-v16a0 +} + +CA-ParametersNRDC-v1700 ::= SEQUENCE { + -- R1 31-9: Indicates the support of simultaneous transmission and reception of an IAB-node from multiple parent nodes + simultaneousRxBTx-IAB-MultipleParents-r17 ENUMERATED {supported} OPTIONAL, + condPSCellAdditionNRDC-r17 ENUMERATED {supported} OPTIONAL, + scg-ActivationDeactivationNRDC-r17 ENUMERATED {supported} OPTIONAL, + scg-ActivationDeactivationResumeNRDC-r17 ENUMERATED {supported} OPTIONAL, + beamManagementType-CBM-r17 ENUMERATED {supported} OPTIONAL +} + +CA-ParametersNRDC-v1720 ::= + ca-ParametersNR-ForDC-v1700 +} + +``` + +``` + +ca-ParametersNR-ForDC-v1720 CA-ParametersNR-v1720 OPTIONAL +} + +CA-ParametersNRDC-v1730 ::= SEQUENCE { + ca-ParametersNR-ForDC-v1730 CA-ParametersNR-v1730 OPTIONAL +} + +CA-ParametersNRDC-v1760 ::= SEQUENCE { + ca-ParametersNR-ForDC-v1760 CA-ParametersNR-v1760 +} + +CA-ParametersNRDC-v1800 ::= SEQUENCE { + ca-ParametersNR-ForDC-v1800 CA-ParametersNR-v1800 OPTIONAL, + -- R1 55-6d: Capability on the number of CCs for monitoring a maximum number of BDs and non-overlapped CCEs per span for MCG and for + -- SCG when configured for NR-DC operation with Rel-16 PDCCH monitoring on all the serving cells + pdcch-BlindDetectionNRDC-r18 SEQUENCE (SIZE (1..maxNrofPdcch-BlindDetection-r17)) OF PDCCH-BlindDetectionMixed1-r18 + OPTIONAL +} + +PDCCH-BlindDetectionMixed1-r18 ::= SEQUENCE { + pdcch-BlindDetectionCG-UE-Mixed-r18 SEQUENCE{ + pdcch-BlindDetectionMCG-UE-Mixed-r18 PDCCH-BlindDetectionCG-UE-Mixed-r18, + pdcch-BlindDetectionSCG-UE-Mixed-r18 PDCCH-BlindDetectionCG-UE-Mixed-r18 + } +} + +-- TAG-CA-PARAMETERS-NRDC-STOP +-- ASN1STOP + +``` + +#### CA-ParametersNRDC field descriptions + +##### **ca-ParametersNR-forDC (with and without suffix)** + +If this field is present for a band combination, it reports the UE capabilities when NR-DC is configured with the band combination. If a version of this field (i.e., with or without suffix) is absent for a band combination, the corresponding *ca-ParametersNR* field version in *BandCombination* is applicable to the UE configured with NR-DC for the band combination. If a version of this field (i.e., with or without suffix) is present for a band combination but does not contain any parameters, the UE does not support the corresponding field version when configured with NR-DC for the band combination. + +##### **featureSetCombinationDC** + +If this field is present for a band combination, it reports the feature set combination supported for the band combination when NR-DC is configured. If this field is absent for a band combination, the *featureSetCombination* in *BandCombination* (without suffix) is applicable to the UE configured with NR-DC for the band combination. + +#### — *CarrierAggregationVariant* + +The IE *CarrierAggregationVariant* informs the network about supported "placement" of the SpCell in an NR cell group. + +#### ***CarrierAggregationVariant* information element** + +``` +-- ASN1START +``` + +``` + +-- TAG-CARRIERAGGREGATIONVARIANT-START + +CarrierAggregationVariant ::= SEQUENCE { + fr1fdd-FR1TDD-CA-SpCellOnFR1FDD ENUMERATED {supported} OPTIONAL, + fr1fdd-FR1TDD-CA-SpCellOnFR1TDD ENUMERATED {supported} OPTIONAL, + fr1fdd-FR2TDD-CA-SpCellOnFR1FDD ENUMERATED {supported} OPTIONAL, + fr1fdd-FR2TDD-CA-SpCellOnFR2TDD ENUMERATED {supported} OPTIONAL, + fr1tdd-FR2TDD-CA-SpCellOnFR1TDD ENUMERATED {supported} OPTIONAL, + fr1tdd-FR2TDD-CA-SpCellOnFR2TDD ENUMERATED {supported} OPTIONAL, + fr1fdd-FR1TDD-FR2TDD-CA-SpCellOnFR1FDD ENUMERATED {supported} OPTIONAL, + fr1fdd-FR1TDD-FR2TDD-CA-SpCellOnFR1TDD ENUMERATED {supported} OPTIONAL, + fr1fdd-FR1TDD-FR2TDD-CA-SpCellOnFR2TDD ENUMERATED {supported} OPTIONAL +} + +-- TAG-CARRIERAGGREGATIONVARIANT-STOP +-- ASN1STOP + +``` + +### CodebookParameters + +The IE *CodebookParameters* is used to convey codebook related parameters. + +#### CodebookParameters information element + +``` + +-- ASN1START +-- TAG-CODEBOOKPARAMETERS-START + +CodebookParameters ::= SEQUENCE { + type1 SEQUENCE { + singlePanel SEQUENCE { + supportedCSI-RS-ResourceList SEQUENCE (SIZE (1.. maxNrofCSI-RS-Resources)) OF SupportedCSI-RS-Resource, + modes ENUMERATED {model, modelandMode2}, + maxNumberCSI-RS-PerResourceSet INTEGER (1..8) + }, + multiPanel SEQUENCE { + supportedCSI-RS-ResourceList SEQUENCE (SIZE (1.. maxNrofCSI-RS-Resources)) OF SupportedCSI-RS-Resource, + modes ENUMERATED {model, mode2, both}, + nrofPanels ENUMERATED {n2, n4}, + maxNumberCSI-RS-PerResourceSet INTEGER (1..8) + } + }, + type2 SEQUENCE { + supportedCSI-RS-ResourceList SEQUENCE (SIZE (1.. maxNrofCSI-RS-Resources)) OF SupportedCSI-RS-Resource, + parameterLx INTEGER (2..4), + amplitudeScalingType ENUMERATED {wideband, widebandAndSubband}, + amplitudeSubsetRestriction ENUMERATED {supported} OPTIONAL + }, + type2-PortSelection SEQUENCE { + supportedCSI-RS-ResourceList SEQUENCE (SIZE (1.. maxNrofCSI-RS-Resources)) OF SupportedCSI-RS-Resource, + parameterLx INTEGER (2..4), + } +} + +``` + +``` + + amplitudeScalingType ENUMERATED {wideband, widebandAndSubband} + } +} +OPTIONAL + +CodebookParameters-v1610 ::= SEQUENCE { + supportedCSI-RS-ResourceListAlt-r16 SEQUENCE { + type1-SinglePanel-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-Resources)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + }, + OPTIONAL, + type1-MultiPanel-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-Resources)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, + type2-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-Resources)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, + type2-PortSelection-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-Resources)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + } +} +OPTIONAL +OPTIONAL + +CodebookParametersAddition-r16 ::= SEQUENCE { + etype2-r16 SEQUENCE { + -- R1 16-3a Regular eType 2 R=1 + etype2R1-r16 SEQUENCE { + supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF + INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + }, + -- R1 16-3a-1 Regular eType 2 R=2 + etype2R2-r16 SEQUENCE { + supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF + INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + } + }, + OPTIONAL, + -- R1 16-3a-2: Support of parameter combinations 7-8 + paramComb7-8-r16 ENUMERATED {supported} + OPTIONAL, + -- R1 16-3a-3: Support of rank 3,4 + rank3-4-r16 ENUMERATED {supported} + OPTIONAL, + -- R1 16-3a-4: CBSR with soft amplitude restriction + amplitudeSubsetRestriction-r16 ENUMERATED {supported} + OPTIONAL, + OPTIONAL, + etype2-PS-r16 SEQUENCE { + -- R1 16-3b Regular eType 2 R=1 PortSelection + etype2R1-PortSelection-r16 SEQUENCE { + supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF + INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + }, + -- R1 16-3b-1 Regular eType 2 R=2 PortSelection + etype2R2-PortSelection-r16 SEQUENCE { + supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF + INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + } + }, + OPTIONAL, + -- R1 16-3b-2: Support of rank 3,4 + rank3-4-r16 ENUMERATED {supported} + OPTIONAL, + OPTIONAL +} +} + +``` + +``` + +CodebookComboParametersAddition-r16 ::= SEQUENCE { + -- R1 16-8 Mixed codebook types + type1SP-Type2-null-r16 SEQUENCE { + supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + } + type1SP-Type2PS-null-r16 SEQUENCE { + supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + } + type1SP-eType2R1-null-r16 SEQUENCE { + supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + } + type1SP-eType2R2-null-r16 SEQUENCE { + supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + } + type1SP-eType2R1PS-null-r16 SEQUENCE { + supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + } + type1SP-eType2R2PS-null-r16 SEQUENCE { + supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + } + type1SP-Type2-Type2PS-r16 SEQUENCE { + supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + } + type1MP-Type2-null-r16 SEQUENCE { + supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + } + type1MP-Type2PS-null-r16 SEQUENCE { + supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + } + type1MP-eType2R1-null-r16 SEQUENCE { + supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + } + type1MP-eType2R2-null-r16 SEQUENCE { + supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + } + type1MP-eType2R1PS-null-r16 SEQUENCE { + supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + } + type1MP-eType2R2PS-null-r16 SEQUENCE { + supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + } + type1MP-Type2-Type2PS-r16 SEQUENCE { + supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + } +} + +CodebookParametersfetype2-r17 ::= SEQUENCE { + -- R1 23-9-1 Basic Features of Further Enhanced Port-Selection Type II Codebook (FeType-II) + fetype2basic-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16), + -- R1 23-9-2 Support of M=2 and R=1 for FeType-II + fetype2R1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r17)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) +} + +``` + +``` + + OPTIONAL, +-- R1 23-9-4 Support of R = 2 for FeType-II +fetype2R2-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r17)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +-- R1 23-9-3 Support of rank 3, 4 for FeType-II +fetype2Rank3Rank4-r17 ENUMERATED {supported} OPTIONAL +} + +CodebookComboParameterMixedType-r17 ::= SEQUENCE { +-- R1 23-9-5 Active CSI-RS resources and ports for mixed codebook types in any slot +type1SP-fetype2PS-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +type1SP-fetype2PS-M2R1-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +type1SP-fetype2PS-M2R2-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +type1SP-Type2-fetype2-PS-M1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +type1SP-Type2-fetype2-PS-M2R1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +type1SP-eType2R1-fetype2-PS-M1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +type1SP-eType2R1-fetype2-PS-M2R1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +type1MP-fetype2PS-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +type1MP-fetype2PS-M2R1-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +type1MP-fetype2PS-M2R2-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +type1MP-Type2-fetype2-PS-M1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +type1MP-Type2-fetype2-PS-M2R1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +type1MP-eType2R1-fetype2-PS-M1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +type1MP-eType2R1-fetype2-PS-M2R1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL +} + +CodebookComboParameterMultiTRP-r17 ::= SEQUENCE { +-- R1 23-7-1b Active CSI-RS resources and ports in the presence of multi-TRP CSI +-- {Codebook 2, Codebook 3} = (NULL, NULL) +nCJT-null-null SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT1SP-null-null SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +-- {Codebook 2, Codebook 3} = { ( "Rel 16 combinations in FG 16-8" ) } +nCJT-Type2-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT-Type2PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + +``` + +``` + +nCJT-eType2R1-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT-eType2R2-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT-eType2R1PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT-eType2R2PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT-Type2-Type2PS-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT1SP-Type2-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT1SP-Type2PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT1SP-eType2R1-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT1SP-eType2R2-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT1SP-eType2R1PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT1SP-eType2R2PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT1SP-Type2-Type2PS-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +-- {Codebook 2, Codebook 3} = {"New Rel7 combinations in FG 23-9-5"} +nCJT-feType2PS-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT-feType2PS-M2R1-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT-feType2PS-M2R2-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT-Type2-feType2-PS-M1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT-Type2-feType2-PS-M2R1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT-eType2R1-feType2-PS-M1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT-eType2R1-feType2-PS-M2R1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT1SP-feType2PS-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT1SP-feType2PS-M2R1-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT1SP-feType2PS-M2R2-null-r1 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT1SP-Type2-feType2-PS-M1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT1SP-Type2-feType2-PS-M2R1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT1SP-eType2R1-feType2-PS-M1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + +``` + +``` + + OPTIONAL, +nCJT1SP-eType2R1-feType2-PS-M2R1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL +} + +CodebookParametersAdditionPerBC-r16:= SEQUENCE { + -- R1 16-3a Regular eType 2 R=1 + eType2R1-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, + -- R1 16-3a-1 Regular eType 2 R=2 + eType2R2-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, + -- R1 16-3b Regular eType 2 R=1 PortSelection + eType2R1-PortSelection-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, + -- R1 16-3b-1 Regular eType 2 R=2 PortSelection + eType2R2-PortSelection-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL +} + +CodebookComboParametersAdditionPerBC-r16:= SEQUENCE { + -- R1 16-8 Mixed codebook types + type1SP-Type2-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, + type1SP-Type2PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, + type1SP-eType2R1-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, + type1SP-eType2R2-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, + type1SP-eType2R1PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, + type1SP-eType2R2PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, + type1SP-Type2-Type2PS-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, + type1MP-Type2-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, + type1MP-Type2PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, + type1MP-eType2R1-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, + type1MP-eType2R2-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, + type1MP-eType2R1PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, + type1MP-eType2R2PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, + type1MP-Type2-Type2PS-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL +} + +``` + +``` + +CodebookParametersFeType2PerBC-r17 ::= SEQUENCE { + -- R1 23-9-1 Basic Features of Further Enhanced Port-Selection Type II Codebook (FeType-II) + feType2Basic-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16), + -- R1 23-9-2 Support of M=2 and R=1 for FeType-II + feType2R1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r17)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, + -- R1 23-9-4 Support of R = 2 for FeType-II + feType2R2-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r17)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL +} + +CodebookComboParameterMixedTypePerBC-r17 ::= SEQUENCE { + -- R1 23-9-5 Active CSI-RS resources and ports for mixed codebook types in any slot + type1SP-feType2PS-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, + type1SP-feType2PS-M2R1-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, + type1SP-feType2PS-M2R2-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, + type1SP-Type2-feType2-PS-M1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, + type1SP-Type2-feType2-PS-M2R1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, + type1SP-eType2R1-feType2-PS-M1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, + type1SP-eType2R1-feType2-PS-M2R1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, + type1MP-feType2PS-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, + type1MP-feType2PS-M2R1-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, + type1MP-feType2PS-M2R2-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, + type1MP-Type2-feType2-PS-M1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, + type1MP-Type2-feType2-PS-M2R1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, + type1MP-eType2R1-feType2-PS-M1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, + type1MP-eType2R1-feType2-PS-M2R1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL +} + +CodebookComboParameterMultiTRP-PerBC-r17 ::= SEQUENCE { + -- R1 23-7-1b Active CSI-RS resources and ports in the presence of multi-TRP CSI + -- {Codebook 2, Codebook 3} =(NULL, NULL) + nCJT-null-null SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, + nCJT1SP-null-null SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +} + +``` + +``` + +-- {Codebook 2, Codebook 3} = { { "Rel 16 combinations in FG 16-8" } +nCJT-Type2-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT-Type2PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT-eType2R1-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT-eType2R2-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT-eType2R1PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT-eType2R2PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT-Type2-Type2PS-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT1SP-Type2-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT1SP-Type2PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT1SP-eType2R1-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT1SP-eType2R2-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT1SP-eType2R1PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT1SP-eType2R2PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT1SP-Type2-Type2PS-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +-- {Codebook 2, Codebook 3} = { "New Rel17 combinations in FG 23-9-5" } +nCJT-feType2PS-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT-feType2PS-M2R1-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT-feType2PS-M2R2-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT-Type2-feType2-PS-M1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT-Type2-feType2-PS-M2R1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT-eType2R1-feType2-PS-M1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT-eType2R1-feType2-PS-M2R1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT1SP-feType2PS-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT1SP-feType2PS-M2R1-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT1SP-feType2PS-M2R2-null-r1 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT1SP-Type2-feType2-PS-M1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + +``` + +``` + + OPTIONAL, +nCJT1SP-Type2-feType2-PS-M2R1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT1SP-eType2R1-feType2-PS-M1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +nCJT1SP-eType2R1-feType2-PS-M2R1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL +} + +CodebookParametersetype2DopplerCSI-r18 ::= SEQUENCE { + -- R1 40-3-2-1: Support of Rel-16-based doppler CSI + eType2Doppler-r18 SEQUENCE { + supportedCSI-RS-ResourceList-r18 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER + (0..maxNrofCSI-RS-ResourcesAlt-1-r16), + valueY-P-SP-CSI-RS-r18 INTEGER (1..3), + valueY-A-CSI-RS-r18 INTEGER (1..3), + scalingfactor-r18 ENUMERATED {n1, n2, n4} + }, + -- R1 40-3-2-1a: Support of Rel-16-based doppler measurement with N4>1 + eType2DopplerN4-r18 SEQUENCE { + supportedCSI-RS-ReportSettingList1-r18 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF + INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16), + supportedCSI-RS-ReportSettingList2-r18 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF + INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + } + OPTIONAL, + -- R1 40-3-2-1a-1: DD unit size when A-CSI-RS is configured for CMR N4>1 + ddUnitSize-A-CSI-RS-CMR-r18 ENUMERATED {supported} + OPTIONAL, + -- R1 40-3-2-2: Support R=2 for Rel-16-based doppler codebook + eType2DopplerR2-r18 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, + -- R1 40-3-2-3: Support X=1 based on first and last slot of WCSI, for Rel-16-based doppler codebook + eType2DopplerX1-r18 ENUMERATED {supported} + OPTIONAL, + -- R1 40-3-2-3a: Support X=2 CQI based on 2 slots for Rel-16-based doppler codebook + eType2DopplerX2-r18 ENUMERATED {supported} + OPTIONAL, + --R1 40-3-2-7: support of l = (n - nCSI,ref ) for CSI reference slot for Rel-16 based doppler codebook + eType2DopplerL-N4D1-r18 ENUMERATED {supported} + OPTIONAL +} + +CodebookParametersfetype2DopplerCSI-r18 ::= SEQUENCE { + -- R1 40-3-2-4: Support of Rel-17-based doppler CSI + feType2Doppler-r18 SEQUENCE { + supportedCSI-RS-ResourceList-r18 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER + (0..maxNrofCSI-RS-ResourcesAlt-1-r16), + valueY-A-CSI-RS-r18 INTEGER (1..3), + scalingfactor-r18 ENUMERATED {n1, n2, n4} + }, + -- R1 40-3-2-5: Support of M=2 and R=1 for Rel-17-based doppler codebook + feType2DopplerM2R1-r18 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER + (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, + -- R1 40-3-2-6: Support R=2 for Rel-17-based doppler codebook + +``` + +``` + +feType2DopplerR2-r18 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) + OPTIONAL, +--R1 40-3-2-7a: Support of l = (n - nCSI,ref) for CSI reference slot for Rel-17 based doppler codebook +feType2DopplerL-N4D1-r18 ENUMERATED {supported} OPTIONAL +} + +CodebookVariantsList-r16 ::= SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesAlt-r16)) OF SupportedCSI-RS-Resource + +SupportedCSI-RS-Resource ::= SEQUENCE { + maxNumberTxPortsPerResource ENUMERATED {p2, p4, p8, p12, p16, p24, p32}, + maxNumberResourcesPerBand INTEGER (1..64), + totalNumberTxPortsPerBand INTEGER (2..256) +} + +SupportedCSI-RS-ReportSettingList-r18 ::= SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesAlt-r16)) OF SupportedCSI-RS-ReportSetting-r18 + +SupportedCSI-RS-ReportSetting-r18 ::= SEQUENCE { + maxN4-r18 ENUMERATED {n1, n2, n4, n8}, + maxNumberTxPortsPerResource-r18 ENUMERATED {p2, p4, p8, p12, p16, p24, p32}, + maxNumberResourcesPerBand-r18 INTEGER (1..64), + totalNumberTxPortsPerBand-r18 INTEGER (2..256) +} + +-- TAG-CODEBOOKPARAMETERS-STOP +-- ASN1STOP + +``` + +#### CodebookParameters field descriptions + +##### ***supportedCSI-RS-ResourceListAlt*** + +This field indicates the alternative list of *SupportedCSI-RS-Resource* supported for each codebook type. The supported CSI-RS resource is indicated by an integer value which pinpoints *SupportedCSI-RS-Resource* defined in *CodebookVariantsList*. The value 0 corresponds to the first entry of *CodebookVariantsList*. The value 1 corresponds to the second entry of *CodebookVariantsList*, and so on. For each codebook type, the field shall be included in both *codebookParametersPerBC* (but optional for single CC) and *codebookParametersPerBand*. + +### ERedCapParameters + +The IE *ERedCapParameters* is used to indicate the UE capabilities supported by eRedCap UEs. + +#### ERedCapParameters information element + +``` + +-- ASN1START +-- TAG-EREDCAPPARAMETERS-START + +ERedCapParameters-r18 ::= SEQUENCE { + -- R1 48-1: eRedCap UE with reduced peak data rate and reduced baseband bandwidth in FR1 + supportOfERedCap-r18 ENUMERATED {supported}, + -- R1 48-2: eRedCap UE with reduced peak data rate without reduced baseband bandwidth in FR1 +} + +``` + +``` + + eRedCapNotReducedBB-BW-r18 ENUMERATED {supported} OPTIONAL, + eRedCapIgnoreCapabilityFiltering-r18 ENUMERATED {supported} OPTIONAL + } + + -- TAG-EREDCAPPARAMETERS-STOP + -- ASN1STOP + +``` + +### FeatureSetCombination + +The IE *FeatureSetCombination* is a two-dimensional matrix of *FeatureSet* entries. + +Each *FeatureSetsPerBand* contains a list of feature sets applicable to the carrier(s) of one band entry of the associated band combination. Across the associated bands, the UE shall support the combination of *FeatureSets* at the same position in the *FeatureSetsPerBand*. All *FeatureSetsPerBand* in one *FeatureSetCombination* must have the same number of entries. + +The number of *FeatureSetsPerBand* in the *FeatureSetCombination* must be equal to the number of band entries in an associated band combination. The first *FeatureSetPerBand* applies to the first band entry of the band combination, and so on. + +Each *FeatureSet* contains either a pair of NR or E-UTRA feature set IDs for UL and DL. + +In case of NR, the actual feature sets for UL and DL are defined in the *FeatureSets* IE and referred to from here by their ID, i.e., their position in the *featureSetsUplink* / *featureSetsDownlink* list in the *FeatureSet* IE. + +In case of E-UTRA, the feature sets referred to from this list are defined in TS 36.331 [10] and conveyed as part of the *UE-EUTRA-Capability* container. + +The *FeatureSetUplink* and *FeatureSetDownlink* referred to from the *FeatureSet* comprise, among other information, a set of *FeatureSetUplinkPerCC-Ids* and *FeatureSetDownlinkPerCC-Ids*. The number of these per-CC IDs determines the number of carriers that the UE is able to aggregate contiguously in frequency domain in the corresponding band. The number of carriers supported by the UE is also restricted by the bandwidth class indicated in the associated *BandCombination*, if present. + +In feature set combinations the UE shall exclude entries with same or lower capabilities, since the network may anyway assume that the UE supports those. + +NOTE 1: The UE may advertise fallback band-combinations in which it supports additional functionality explicitly in two ways: Either by setting *FeatureSet* IDs to zero (inter-band and intra-band non-contiguous fallback) and by reducing the number of *FeatureSet-PerCC* IDs in a *Feature Set* (intra-band contiguous fallback). Or by separate *BandCombination* entries with associated *FeatureSetCombinations*. + +NOTE 2: The UE may advertise a *FeatureSetCombination* containing only fallback band combinations. That means, in a *FeatureSetCombination*, each group of *FeatureSets* across the bands may contain at least one pair of *FeatureSetUplinkId* and *FeatureSetDownlinkId* which is set to 0/0. + +NOTE 3: The Network configures serving cell(s) and BWP(s) configuration to comply with capabilities derived from the combination of *FeatureSets* at the same position in the *FeatureSetsPerBand*, regardless of activated/deactivated serving cell(s) and BWP(s). + +#### FeatureSetCombination information element + +``` +-- ASN1START +-- TAG-FEATURESETCOMBINATION-START + +FeatureSetCombination ::= SEQUENCE (SIZE (1..maxSimultaneousBands)) OF FeatureSetsPerBand +FeatureSetsPerBand ::= SEQUENCE (SIZE (1..maxFeatureSetsPerBand)) OF FeatureSet +FeatureSet ::= CHOICE { + eutra SEQUENCE { + downlinkSetEUTRA FeatureSetEUTRA-DownlinkId, + uplinkSetEUTRA FeatureSetEUTRA-UplinkId + }, + nr SEQUENCE { + downlinkSetNR FeatureSetDownlinkId, + uplinkSetNR FeatureSetUplinkId + } +} + +-- TAG-FEATURESETCOMBINATION-STOP +-- ASN1STOP +``` + +##### – FeatureSetCombinationId + +The IE *FeatureSetCombinationId* identifies a *FeatureSetCombination*. The *FeatureSetCombinationId* of a *FeatureSetCombination* is the position of the *FeatureSetCombination* in the *featureSetCombinations* list (in *UE-NR-Capability* or *UE-MRDC-Capability*). The *FeatureSetCombinationId* = 0 refers to the first entry in the *featureSetCombinations* list (in *UE-NR-Capability* or *UE-MRDC-Capability*). + +NOTE: The *FeatureSetCombinationId* = 1024 is not used due to the maximum entry number of *featureSetCombinations*. + +##### FeatureSetCombinationId information element + +``` +-- ASN1START +-- TAG-FEATURESETCOMBINATIONID-START + +FeatureSetCombinationId ::= INTEGER (0.. maxFeatureSetCombinations) + +-- TAG-FEATURESETCOMBINATIONID-STOP +-- ASN1STOP +``` + +##### – FeatureSetDownlink + +The IE *FeatureSetDownlink* indicates a set of features that the UE supports on the carriers corresponding to one band entry in a band combination. + +#### **FeatureSetDownlink information element** + +``` + +-- ASN1START +-- TAG-FEATURESETDOWNLINK-START + +FeatureSetDownlink ::= + featureSetListPerDownlinkCC + intraBandFreqSeparationDL + scalingFactor + dummy8 + scellWithoutSSB + csi-RS-MeasSCellWithoutSSB + dummy1 + type1-3-CSS + pdcch-MonitoringAnyOccasions + dummy2 + ue-SpecificUL-DL-Assignment + searchSpaceSharingCA-DL + timeDurationForQCL + scs-60kHz + scs-120kHz + } + pdsch-ProcessingType1-DifferentTB-PerSlot + scs-15kHz + scs-30kHz + scs-60kHz + scs-120kHz + } + dummy3 + dummy4 + dummy5 + dummy6 + dummy7 +} + +FeatureSetDownlink-v1540 ::= + oneFL-DMRS-TwoAdditionalDMRS-DL + additionalDMRS-DL-Alt + twoFL-DMRS-TwoAdditionalDMRS-DL + oneFL-DMRS-ThreeAdditionalDMRS-DL + pdcch-MonitoringAnyOccasionsWithSpanGap + scs-15kHz + scs-30kHz + scs-60kHz + scs-120kHz + } + pdsch-SeparationWithGap + pdsch-ProcessingType2 + scs-15kHz + scs-30kHz + } + +SEQUENCE { + SEQUENCE (SIZE (1..maxNrofServingCells)) OF FeatureSetDownlinkPerCC-Id, + FreqSeparationClass + ENUMERATED {f0p4, f0p75, f0p8} + ENUMERATED {supported} + ENUMERATED {supported} + ENUMERATED {supported} + ENUMERATED {supported} + ENUMERATED {supported} + ENUMERATED {withoutDCI-Gap, withDCI-Gap} + ENUMERATED {supported} + ENUMERATED {supported} + ENUMERATED {supported} + SEQUENCE { + ENUMERATED {s7, s14, s28} + ENUMERATED {s14, s28} + } + SEQUENCE { + ENUMERATED {upto2, upto4, upto7} + ENUMERATED {upto2, upto4, upto7} + ENUMERATED {upto2, upto4, upto7} + ENUMERATED {upto2, upto4, upto7} + } + DummyA + SEQUENCE (SIZE (1.. maxNrofCodebooks)) OF DummyB + SEQUENCE (SIZE (1.. maxNrofCodebooks)) OF DummyC + SEQUENCE (SIZE (1.. maxNrofCodebooks)) OF DummyD + SEQUENCE (SIZE (1.. maxNrofCodebooks)) OF DummyE +} + +SEQUENCE { + ENUMERATED {supported} + ENUMERATED {supported} + ENUMERATED {supported} + ENUMERATED {supported} + SEQUENCE { + ENUMERATED {set1, set2, set3} + ENUMERATED {set1, set2, set3} + ENUMERATED {set1, set2, set3} + ENUMERATED {set1, set2, set3} + } + ENUMERATED {supported} + SEQUENCE { + ProcessingParameters + ProcessingParameters + } +} + +``` + +``` + + scs-60kHz ProcessingParameters OPTIONAL + } OPTIONAL, + pdsch-ProcessingType2-Limited SEQUENCE { + differentTB-PerSlot-SCS-30kHz ENUMERATED {upto1, upto2, upto4, upto7} + } OPTIONAL, + dl-MCS-TableAlt-DynamicIndication ENUMERATED {supported} OPTIONAL +} + +FeatureSetDownlink-v15a0 ::= SEQUENCE { + supportedSRS-Resources SRS-Resources OPTIONAL +} + +FeatureSetDownlink-v1610 ::= SEQUENCE { + -- R1 22-4e/4f/4g/4h: CBG based reception for DL with unicast PDSCH(s) per slot per CC with UE processing time Capability 1 + cbgPDSCH-ProcessingType1-DifferentTB-PerSlot-r16 SEQUENCE { + scs-15kHz-r16 ENUMERATED {one, upto2, upto4, upto7} OPTIONAL, + scs-30kHz-r16 ENUMERATED {one, upto2, upto4, upto7} OPTIONAL, + scs-60kHz-r16 ENUMERATED {one, upto2, upto4, upto7} OPTIONAL, + scs-120kHz-r16 ENUMERATED {one, upto2, upto4, upto7} OPTIONAL + } OPTIONAL, + + -- R1 22-3e/3f/3g/3h: CBG based reception for DL with unicast PDSCH(s) per slot per CC with UE processing time Capability 2 + cbgPDSCH-ProcessingType2-DifferentTB-PerSlot-r16 SEQUENCE { + scs-15kHz-r16 ENUMERATED {one, upto2, upto4, upto7} OPTIONAL, + scs-30kHz-r16 ENUMERATED {one, upto2, upto4, upto7} OPTIONAL, + scs-60kHz-r16 ENUMERATED {one, upto2, upto4, upto7} OPTIONAL, + scs-120kHz-r16 ENUMERATED {one, upto2, upto4, upto7} OPTIONAL + } OPTIONAL, + intraFreqDAPS-r16 SEQUENCE { + intraFreqDiffSCS-DAPS-r16 ENUMERATED {supported} OPTIONAL, + intraFreqAsyncDAPS-r16 ENUMERATED {supported} OPTIONAL + } OPTIONAL, + intraBandFreqSeparationDL-v1620 FreqSeparationClassDL-v1620 OPTIONAL, + intraBandFreqSeparationDL-Only-r16 FreqSeparationClassDL-Only-r16 OPTIONAL, + + -- R1 11-2: Rel-16 PDCCH monitoring capability + pdcch-Monitoring-r16 SEQUENCE { + pdsch-ProcessingType1-r16 SEQUENCE { + scs-15kHz-r16 PDCCH-MonitoringOccasions-r16 OPTIONAL, + scs-30kHz-r16 PDCCH-MonitoringOccasions-r16 OPTIONAL + } OPTIONAL, + pdsch-ProcessingType2-r16 SEQUENCE { + scs-15kHz-r16 PDCCH-MonitoringOccasions-r16 OPTIONAL, + scs-30kHz-r16 PDCCH-MonitoringOccasions-r16 OPTIONAL + } OPTIONAL, + } OPTIONAL, + + -- R1 11-2b: Mix of Rel. 16 PDCCH monitoring capability and Rel. 15 PDCCH monitoring capability on different carriers + pdcch-MonitoringMixed-r16 ENUMERATED {supported} OPTIONAL, + + -- R1 18-5c: Processing up to X unicast DCI scheduling for DL per scheduled CC + +``` + +``` + +crossCarrierSchedulingProcessing-DiffSCS-r16 SEQUENCE { + scs-15kHz-120kHz-r16 ENUMERATED {n1,n2,n4} OPTIONAL, + scs-15kHz-60kHz-r16 ENUMERATED {n1,n2,n4} OPTIONAL, + scs-30kHz-120kHz-r16 ENUMERATED {n1,n2,n4} OPTIONAL, + scs-15kHz-30kHz-r16 ENUMERATED {n2} OPTIONAL, + scs-30kHz-60kHz-r16 ENUMERATED {n2} OPTIONAL, + scs-60kHz-120kHz-r16 ENUMERATED {n2} OPTIONAL, +} +OPTIONAL, + +-- R1 16-2b-1: Support of single-DCI based SDM scheme +singleDCI-SDM-scheme-r16 ENUMERATED {supported} OPTIONAL +} + +FeatureSetDownlink-v1700 ::= SEQUENCE { + -- R1 36-2: Scaling factor to be applied to 1024QAM for FR1 + scalingFactor-1024QAM-FR1-r17 ENUMERATED {f0p4, f0p75, f0p8} OPTIONAL, + -- R1 24 feature for existing UE cap to include new SCS + timeDurationForQCL-v1710 SEQUENCE { + scs-480kHz ENUMERATED {s56, s112} OPTIONAL, + scs-960kHz ENUMERATED {s112, s224} OPTIONAL, + } + OPTIONAL, + -- R1 23-6-1 SFN scheme A (scheme 1) for PDSCH and PDCCH + sfn-SchemeA-r17 ENUMERATED {supported} OPTIONAL, + -- R1 23-6-1-1 SFN scheme A (scheme 1) for PDCCH only + sfn-SchemeA-PDCCH-only-r17 ENUMERATED {supported} OPTIONAL, + -- R1 23-6-1a Dynamic switching - scheme A + sfn-SchemeA-DynamicSwitching-r17 ENUMERATED {supported} OPTIONAL, + -- R1 23-6-1b SFN scheme A (scheme 1) for PDSCH only + sfn-SchemeA-PDSCH-only-r17 ENUMERATED {supported} OPTIONAL, + -- R1 23-6-2 SFN scheme B (TRP based pre-compensation) for PDSCH and PDCCH + sfn-SchemeB-r17 ENUMERATED {supported} OPTIONAL, + -- R1 23-6-2a Dynamic switching - scheme B + sfn-SchemeB-DynamicSwitching-r17 ENUMERATED {supported} OPTIONAL, + -- R1 23-6-2b SFN scheme B (TRP based pre-compensation) for PDSCH only + sfn-SchemeB-PDSCH-only-r17 ENUMERATED {supported} OPTIONAL, + -- R1 23-2-1d PDCCH repetition for Case 2 PDCCH monitoring with a span gap + mTRP-PDCCH-Case2-1SpanGap-r17 SEQUENCE { + scs-15kHz-r17 PDCCH-RepetitionParameters-r17 OPTIONAL, + scs-30kHz-r17 PDCCH-RepetitionParameters-r17 OPTIONAL, + scs-60kHz-r17 PDCCH-RepetitionParameters-r17 OPTIONAL, + scs-120kHz-r17 PDCCH-RepetitionParameters-r17 OPTIONAL, + } + OPTIONAL, + -- R1 23-2-1e PDCCH repetition for Rel-16 PDCCH monitoring + mTRP-PDCCH-legacyMonitoring-r17 SEQUENCE { + scs-15kHz-r17 PDCCH-RepetitionParameters-r17 OPTIONAL, + scs-30kHz-r17 PDCCH-RepetitionParameters-r17 OPTIONAL, + } + OPTIONAL, + -- R1 23-2-4 Simultaneous configuration of PDCCH repetition and multi-DCI based multi-TRP + mTRP-PDCCH-multiDCI-multiTRP-r17 ENUMERATED {supported} OPTIONAL, + -- R1 33-2: Dynamic scheduling for multicast for PCell + dynamicMulticastPCell-r17 ENUMERATED {supported} OPTIONAL, +} + +``` + +``` + + -- R1 23-2-1 PDCCH repetition + mTRP-PDCCH-Repetition-r17 SEQUENCE { + numBD-twoPDCCH-r17 INTEGER (2..3), + maxNumOverlaps-r17 ENUMERATED {n1,n2,n3,n5,n10,n20,n40} + } OPTIONAL +} + +FeatureSetDownlink-v1720 ::= SEQUENCE { + -- R1 25-19: RTT-based Propagation delay compensation based on CSI-RS for tracking and SRS + rtt-BasedPDC-CSI-RS-ForTracking-r17 ENUMERATED {supported} OPTIONAL, + -- R1 25-19a: RTT-based Propagation delay compensation based on DL PRS for RTT-based PDC and SRS + rtt-BasedPDC-PRS-r17 SEQUENCE { + maxNumberPRS-Resource-r17 ENUMERATED {n1, n2, n4, n8, n16, n32, n64}, + maxNumberPRS-ResourceProcessedPerSlot-r17 SEQUENCE { + scs-15kHz-r17 ENUMERATED {n1, n2, n4, n6, n8, n12, n16, n24, n32, n48, n64} OPTIONAL, + scs-30kHz-r17 ENUMERATED {n1, n2, n4, n6, n8, n12, n16, n24, n32, n48, n64} OPTIONAL, + scs-60kHz-r17 ENUMERATED {n1, n2, n4, n6, n8, n12, n16, n24, n32, n48, n64} OPTIONAL, + scs-120kHz-r17 ENUMERATED {n1, n2, n4, n6, n8, n12, n16, n24, n32, n48, n64} OPTIONAL + } OPTIONAL + } OPTIONAL, + -- R1 33-5-1: SPS group-common PDSCH for multicast on PCell + sps-Multicast-r17 ENUMERATED {supported} OPTIONAL +} + +FeatureSetDownlink-v1730 ::= SEQUENCE { + -- R1 25-19b: Support of PRS as spatial relation RS for SRS + prs-AsSpatialRelationRS-For-SRS-r17 ENUMERATED {supported} OPTIONAL +} + +FeatureSetDownlink-v1800 ::= SEQUENCE { + -- R1 40-3-3-6: Maximum number of TRS resource sets in a report configuration + maxNumberTRS-ResourceSet-r18 INTEGER (2..3) OPTIONAL, + -- R1 40-4-1b: 1 symbol FL DMRS and 2 additional DMRS symbols for more than one port for Rel.18 enhanced DMRS ports for PDSCH + pdsch-1SymbolFL-DMRS-Addition2Symbol-r18 ENUMERATED {supported} OPTIONAL, + -- R1 40-4-1c: Alternative additional DMRS position for co-existence with LTE CRS for Rel.18 enhanced DMRS ports for PDSCH + pdsch-AlternativeDMRS-Coexistence-r18 ENUMERATED {supported} OPTIONAL, + -- R1 40-4-1d: 2 symbols FL-DMRS for Rel.18 enhanced DMRS ports for PDSCH + pdsch-2SymbolFL-DMRS-r18 ENUMERATED {supported} OPTIONAL, + -- R1 40-4-1e: 2-symbol FL DMRS + one additional 2-symbols DMRS for Rel.18 enhanced DMRS ports for PDSCH + pdsch-2SymbolFL-DMRS-Addition2Symbol-r18 ENUMERATED {supported} OPTIONAL, + -- R1 40-4-1f: 1 symbol FL DMRS and 3 additional DMRS symbols for Rel.18 enhanced DMRS ports for PDSCH + pdsch-1SymbolFL-DMRS-Addition3Symbol-r18 ENUMERATED {supported} OPTIONAL, + -- R1 40-4-1g: DMRS type for Rel.18 enhanced DMRS ports for PDSCH + pdsch-DMRS-Type-r18 ENUMERATED {etype1, etype1And2} OPTIONAL, + -- R1 40-4-1h: 1 port DL PTRS for Rel.18 enhanced DMRS ports for PDSCH with rank 1-8 + pdsch-1PortDL-PTRS-r18 ENUMERATED {supported} OPTIONAL, + -- R1 40-4-1j: Support 1 symbol FL DMRS and 2 additional DMRS symbols for at least one port for mapping type A + mappingTypeA-1SymbolFL-DMRS-Addition2Symbol-r18 ENUMERATED {supported} OPTIONAL, + + -- R1 40-4-4: Reception of PDSCH without the scheduling restriction for Rel.18 eType1 DMRS ports + pdsch-ReceptionWithoutSchedulingRestriction-r18 ENUMERATED {supported} OPTIONAL +} + +``` + +``` + +-- R1 40-4-5a: Additional row(s) for antenna ports (0,2,3) for Rel.18 DMRS ports for single-DCI based M-TRP +dmrs-MultiTRP-AdditionRows-r18 ENUMERATED {supported} OPTIONAL, +-- R1 40-4-12: Support of Rel-18 DMRS and PDSCH processing capability 2 simultaneously +simulDMRS-PDSCH-r18 SEQUENCE { + scs-15kHz-r18 INTEGER (0..4) OPTIONAL, + scs-30kHz-r18 INTEGER (0..5) OPTIONAL, + scs-60kHz-r18 INTEGER (0..7) OPTIONAL, +} OPTIONAL, + +-- R1 53-1: Support RLM/BM/BFD and gapless L3 intra-frequency measurements based on CD-SSB outside active BWP without interruptions +bwpOperationMeasWithoutInterrupt-r18 ENUMERATED {supported} OPTIONAL, +-- R1 53-2: Support RLM/BM/BFD measurements based on CD-SSB outside active BWP with interruptions +bwpOperationMeasWithInterrupt-r18 ENUMERATED {supported} OPTIONAL, + +-- R1 55-6: (2, 2) span-based PDCCH monitoring with additional restriction(s) +pdcch-MonitoringSpan2-2-r18 SEQUENCE{ + pdsch-ProcessingType1-r18 SEQUENCE{ + scs-15kHz-r18 ENUMERATED {supported} OPTIONAL, + scs-30kHz-r18 ENUMERATED {supported} OPTIONAL, + }, + pdsch-ProcessingType2-r18 SEQUENCE{ + scs-15kHz-r18 ENUMERATED {supported} OPTIONAL, + scs-30kHz-r18 ENUMERATED {supported} OPTIONAL, + } +} OPTIONAL, +-- R1 55-6b: Mix of Rel-16 PDCCH monitoring capability and Rel. 15 PDCCH monitoring capability on different carriers +pdcch-MonitoringMixed-r18 ENUMERATED {supported} OPTIONAL, +multicastInactive-r18 ENUMERATED {supported} OPTIONAL, +} + +PDCCH-MonitoringOccasions-r16 ::= SEQUENCE { + period7span3-r16 ENUMERATED {supported} OPTIONAL, + period4span3-r16 ENUMERATED {supported} OPTIONAL, + period2span2-r16 ENUMERATED {supported} OPTIONAL, +} + +PDCCH-RepetitionParameters-r17 ::= SEQUENCE { + supportedMode-r17 ENUMERATED {intra-span, inter-span, both}, + limitX-PerCC-r17 ENUMERATED {n4, n8, n16, n32, n44, n64, nolimit} OPTIONAL, + limitX-AcrossCC-r17 ENUMERATED {n4, n8, n16, n32, n44, n64, n128, n256, n512, nolimit} OPTIONAL, +} + +DummyA ::= SEQUENCE { + maxNumberNZP-CSI-RS-PerCC INTEGER (1..32), + maxNumberPortsAcrossNZP-CSI-RS-PerCC ENUMERATED {p2, p4, p8, p12, p16, p24, p32, p40, p48, p56, p64, p72, p80, + p88, p96, p104, p112, p120, p128, p136, p144, p152, p160, p168, + p176, p184, p192, p200, p208, p216, p224, p232, p240, p248, p256}, + maxNumberCS-IM-PerCC ENUMERATED {n1, n2, n4, n8, n16, n32}, + maxNumberSimultaneousCSI-RS-ActBWP-AllCC ENUMERATED {n5, n6, n7, n8, n9, n10, n12, n14, n16, n18, n20, n22, n24, n26, + n28, n30, n32, n34, n36, n38, n40, n42, n44, n46, n48, n50, n52}, +} + +``` + +``` + + n54, n56, n58, n60, n62, n64), + totalNumberPortsSimultaneousCSI-RS-ActBWP-AllCC ENUMERATED {p8, p12, p16, p24, p32, p40, p48, p56, p64, p72, p80, + p88, p96, p104, p112, p120, p128, p136, p144, p152, p160, p168, + p176, p184, p192, p200, p208, p216, p224, p232, p240, p248, p256} + } + + DummyB ::= SEQUENCE { + maxNumberTxPortsPerResource ENUMERATED {p2, p4, p8, p12, p16, p24, p32}, + maxNumberResources INTEGER (1..64), + totalNumberTxPorts INTEGER (2..256), + supportedCodebookMode ENUMERATED {model1, modelAndMode2}, + maxNumberCSI-RS-PerResourceSet INTEGER (1..8) + } + + DummyC ::= SEQUENCE { + maxNumberTxPortsPerResource ENUMERATED {p8, p16, p32}, + maxNumberResources INTEGER (1..64), + totalNumberTxPorts INTEGER (2..256), + supportedCodebookMode ENUMERATED {model1, mode2, both}, + supportedNumberPanels ENUMERATED {n2, n4}, + maxNumberCSI-RS-PerResourceSet INTEGER (1..8) + } + + DummyD ::= SEQUENCE { + maxNumberTxPortsPerResource ENUMERATED {p4, p8, p12, p16, p24, p32}, + maxNumberResources INTEGER (1..64), + totalNumberTxPorts INTEGER (2..256), + parameterLx INTEGER (2..4), + amplitudeScalingType ENUMERATED {wideband, widebandAndSubband}, + amplitudeSubsetRestriction ENUMERATED {supported} OPTIONAL, + maxNumberCSI-RS-PerResourceSet INTEGER (1..8) + } + + DummyE ::= SEQUENCE { + maxNumberTxPortsPerResource ENUMERATED {p4, p8, p12, p16, p24, p32}, + maxNumberResources INTEGER (1..64), + totalNumberTxPorts INTEGER (2..256), + parameterLx INTEGER (2..4), + amplitudeScalingType ENUMERATED {wideband, widebandAndSubband}, + maxNumberCSI-RS-PerResourceSet INTEGER (1..8) + } + +-- TAG-FEATURESETDOWNLINK-STOP +-- ASN1STOP + +``` + +| FeatureSetDownlink field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| featureSetListPerDownlinkCC
Indicates which features the UE supports on the individual DL carriers of the feature set (and hence of a band entry that refer to the feature set). The UE shall hence include at least as many FeatureSetDownlinkPerCC-Id in this list as the number of carriers it supports according to the ca-BandwidthClassDL , except if indicating additional functionality by reducing the number of FeatureSetDownlinkPerCC-Id in the feature set (see NOTE 1 in FeatureSetCombination IE description). The order of the elements in this list is not relevant, i.e., the network may configure any of the carriers in accordance with any of the FeatureSetDownlinkPerCC-Id in this list. | +| supportedSRS-Resources
Indicates supported SRS resources for SRS carrier switching to the band associated with this FeatureSetDownlink . The UE is only allowed to set this field for a band with associated FeatureSetUplinkId set to 0. | + +##### – **FeatureSetDownlinkId** + +The IE *FeatureSetDownlinkId* identifies a downlink feature set. The *FeatureSetDownlinkId* of a *FeatureSetDownlink* is the index position of the *FeatureSetDownlink* in the *featureSetsDownlink* list in the *FeatureSets* IE. The first element in that list is referred to by *FeatureSetDownlinkId* = 1. The *FeatureSetDownlinkId*=0 is not used by an actual *FeatureSetDownlink* but means that the UE does not support a carrier in this band of a band combination. + +#### **FeatureSetDownlinkId information element** + +``` +-- ASN1START +-- TAG-FEATURESETDOWNLINKID-START + +FeatureSetDownlinkId ::= INTEGER (0..maxDownlinkFeatureSets) + +-- TAG-FEATURESETDOWNLINKID-STOP +-- ASN1STOP +``` + +##### – **FeatureSetDownlinkPerCC** + +The IE *FeatureSetDownlinkPerCC* indicates a set of features that the UE supports on the corresponding carrier of one band entry of a band combination. + +#### **FeatureSetDownlinkPerCC information element** + +``` +-- ASN1START +-- TAG-FEATURESETDOWNLINKPERCC-START + +FeatureSetDownlinkPerCC ::= SEQUENCE { + supportedSubcarrierSpacingDL SubcarrierSpacing, + supportedBandwidthDL SupportedBandwidth, + channelBW-90mhz ENUMERATED {supported} OPTIONAL, + maxNumberMIMO-LayersPDSCH MIMO-LayersDL OPTIONAL, + supportedModulationOrderDL ModulationOrder OPTIONAL +} + +FeatureSetDownlinkPerCC-v1620 ::= SEQUENCE { +``` + +``` + +-- R1 16-2a: Multit-DCI based multi-TRP +multiDCI-MultiTRP-r16 MultiDCI-MultiTRP-r16 OPTIONAL, +-- R1 16-2b-3: Support of single-DCI based FDMSchemeB +supportFDM-SchemeB-r16 ENUMERATED {supported} OPTIONAL +} + +FeatureSetDownlinkPerCC-v1700 ::= SEQUENCE { + supportedMinBandwidthDL-r17 SupportedBandwidth-v1700 OPTIONAL, + broadcastSCell-r17 ENUMERATED {supported} OPTIONAL, + -- R1 33-2g: MIMO layers for multicast PDSCH + maxNumberMIMO-LayersMulticastPDSCH-r17 ENUMERATED {n2, n4, n8} OPTIONAL, + -- R1 33-2h: Dynamic scheduling for multicast for SCell + dynamicMulticastSCell-r17 ENUMERATED {supported} OPTIONAL, + supportedBandwidthDL-v1710 SupportedBandwidth-v1700 OPTIONAL, + -- R4 24-1/24-2/24-3/24-4/24-5 + supportedCRS-InterfMitigation-r17 CRS-InterfMitigation-r17 OPTIONAL +} + +FeatureSetDownlinkPerCC-v1720 ::= SEQUENCE { + -- R1 33-2j: Supported maximum modulation order used for maximum data rate calculation for multicast PDSCH + maxModulationOrderForMulticastDataRateCalculation-r17 ENUMERATED {qam64, qam256, qam1024} OPTIONAL, + -- R1 33-1-2: FDM-ed unicast PDSCH and group-common PDSCH for broadcast + fdm-BroadcastUnicast-r17 ENUMERATED {supported} OPTIONAL, + -- R1 33-3-2: FDM-ed unicast PDSCH and one group-common PDSCH for multicast + fdm-MulticastUnicast-r17 ENUMERATED {supported} OPTIONAL +} + +FeatureSetDownlinkPerCC-v1730 ::= SEQUENCE { + -- R1 33-3-3: Intra-slot TDM-ed unicast PDSCH and group-common PDSCH + intraSlotTDM-UnicastGroupCommonPDSCH-r17 ENUMERATED {yes, no} OPTIONAL, + -- R1 33-5-3: One SPS group-common PDSCH configuration for multicast for SCell + sps-MulticastSCell-r17 ENUMERATED {supported} OPTIONAL, + -- R1 33-5-4: Up to 8 SPS group-common PDSCH configurations per CFR for multicast for SCell + sps-MulticastSCellMultiConfig-r17 INTEGER (1..8) OPTIONAL, + -- R1 33-1-1: Dynamic slot-level repetition for broadcast MTCH + dci-BroadcastWith16Repetitions-r17 ENUMERATED {supported} OPTIONAL +} + +FeatureSetDownlinkPerCC-v1800 ::= SEQUENCE { + -- R1 40-2-1: Basic feature for multi-DCI based intra-cell Multi-TRP operation with two TA enhancement + multiDCI-IntraCellMultiTRP-TwoTA-r18 ENUMERATED {supported} OPTIONAL, + -- R1 40-2-2: Basic feature for multi-DCI based inter-cell Multi-TRP operation with two TA enhancement + multiDCI-InterCellMultiTRP-TwoTA-r18 INTEGER (1..2) OPTIONAL, + -- R1 40-2-6: Rx timing difference larger than CP length + rxTimingDiff-r18 ENUMERATED {supported} OPTIONAL, + + -- R1 55-7: Two QCL TypeD for CORESET monitoring in multi-DCI based multi-TRP + multiDCI-MultiTRP-CORESET-Monitoring-r18 ENUMERATED {supported} OPTIONAL, + broadcastNonServingCell-r18 ENUMERATED {supported} OPTIONAL +} + +``` + +``` + +MultiDCI-MultiTRP-r16 ::= SEQUENCE { + maxNumberCORESET-r16 ENUMERATED {n2, n3, n4, n5}, + maxNumberCORESETPerPoolIndex-r16 INTEGER (1..3), + maxNumberUnicastPDSCH-PerPool-r16 ENUMERATED {n1, n2, n3, n4, n7} +} + +CRS-InterfMitigation-r17 ::= SEQUENCE { + -- R4 24-1 CRS-IM (Interference Mitigation) in DSS scenario + crs-IM-DSS-15kHzSCS-r17 ENUMERATED {supported} OPTIONAL, + -- R4 24-2 CRS-IM in non-DSS and 15 kHz NR SCS scenario, without the assistance of network signaling on LTE channel bandwidth + crs-IM-nonDSS-15kHzSCS-r17 ENUMERATED {supported} OPTIONAL, + -- R4 24-3 CRS-IM in non-DSS and 15 kHz NR SCS scenario, with the assistance of network signaling on LTE channel bandwidth + crs-IM-nonDSS-NWA-15kHzSCS-r17 ENUMERATED {supported} OPTIONAL, + -- R4 24-4 CRS-IM in non-DSS and 30 kHz NR SCS scenario, without the assistance of network signaling on LTE channel bandwidth + crs-IM-nonDSS-30kHzSCS-r17 ENUMERATED {supported} OPTIONAL, + -- R4 24-5 CRS-IM in non-DSS and 30 kHz NR SCS scenario, with the assistance of network signaling on LTE channel bandwidth + crs-IM-nonDSS-NWA-30kHzSCS-r17 ENUMERATED {supported} OPTIONAL +} + +-- TAG-FEATURESETDOWNLINKPERCC-STOP +-- ASN1STOP + +``` + +#### FeatureSetDownlinkPerCC-Id + +The IE *FeatureSetDownlinkPerCC-Id* identifies a set of features applicable to one carrier of a feature set. The *FeatureSetDownlinkPerCC-Id* of a *FeatureSetDownlinkPerCC* is the index position of the *FeatureSetDownlinkPerCC* in the *featureSetsDownlinkPerCC*. The first element in the list is referred to by *FeatureSetDownlinkPerCC-Id* = 1, and so on. + +#### FeatureSetDownlinkPerCC-Id information element + +``` + +-- ASN1START +-- TAG-FEATURESETDOWNLINKPERCC-ID-START + +FeatureSetDownlinkPerCC-Id ::= INTEGER (1..maxPerCC-FeatureSets) + +-- TAG-FEATURESETDOWNLINKPERCC-ID-STOP +-- ASN1STOP + +``` + +#### FeatureSetEUTRA-DownlinkId + +The IE *FeatureSetEUTRA-DownlinkId* identifies a downlink feature set in E-UTRA list (see TS 36.331 [10]). The first element in that list is referred to by *FeatureSetEUTRA-DownlinkId* = 1. The *FeatureSetEUTRA-DownlinkId*=0 is used when the UE does not support a carrier in this band of a band combination. + +##### FeatureSetEUTRA-DownlinkId information element + +``` + +-- ASN1START +-- TAG-FEATURESETEUTRADOWNLINKID-START + +``` + +``` +FeatureSetEUTRA-DownlinkId ::= INTEGER (0..maxEUTRA-DL-FeatureSets) + +-- TAG-FEATURESETEUTRADOWNLINKID-STOP +-- ASN1STOP +``` + +##### — **FeatureSetEUTRA-UplinkId** + +The IE *FeatureSetEUTRA-UplinkId* identifies an uplink feature set in E-UTRA list (see TS 36.331 [10]. The first element in that list is referred to by *FeatureSetEUTRA-UplinkId* = 1. The *FeatureSetEUTRA-UplinkId* = 0 is used when the UE does not support a carrier in this band of a band combination. + +#### **FeatureSetEUTRA-UplinkId information element** + +``` +-- ASN1START +-- TAG-FEATURESETEUTRAUPLINKID-START + +FeatureSetEUTRA-UplinkId ::= INTEGER (0..maxEUTRA-UL-FeatureSets) + +-- TAG-FEATURESETEUTRAUPLINKID-STOP +-- ASN1STOP +``` + +#### — **FeatureSets** + +The IE *FeatureSets* is used to provide pools of downlink and uplink features sets. A *FeatureSetCombination* refers to the IDs of the feature set(s) that the UE supports in that *FeatureSetCombination*. The *BandCombination* entries in the *BandCombinationList* then indicate the ID of the *FeatureSetCombination* that the UE supports for that band combination. + +The entries in the lists in this IE are identified by their index position. For example, the *FeatureSetUplinkPerCC-Id* = 4 identifies the 4th element in the *featureSetsUplinkPerCC* list. + +**NOTE:** When feature sets (per CC) IEs require extension in future versions of the specification, new versions of the *FeatureSetDownlink*, *FeatureSetUplink*, *FeatureSets*, *FeatureSetDownlinkPerCC* and/or *FeatureSetUplinkPerCC* will be created and instantiated in corresponding new lists in the *FeatureSets* IE. For example, if new capability bits are to be added to the *FeatureSetDownlink*, they will instead be defined in a new *FeatureSetDownlink-rxy* which will be instantiated in a new *featureSetDownlinkList-rxy* list. If a UE indicates in a *FeatureSetCombination* that it supports the *FeatureSetDownlink* with ID #5, it implies that it supports both the features in *FeatureSetDownlink* #5 and *FeatureSetDownlink-rxy* #5 (if present). The number of entries in the new list(s) shall be the same as in the original list(s). + +#### **FeatureSets information element** + +``` +-- ASN1START +-- TAG-FEATURESETS-START + +FeatureSets ::= SEQUENCE { +``` + +``` + +featureSetsDownlink SEQUENCE (SIZE (1..maxDownlinkFeatureSets)) OF FeatureSetDownlink OPTIONAL, +featureSetsDownlinkPerCC SEQUENCE (SIZE (1..maxPerCC-FeatureSets)) OF FeatureSetDownlinkPerCC OPTIONAL, +featureSetsUplink SEQUENCE (SIZE (1..maxUplinkFeatureSets)) OF FeatureSetUplink OPTIONAL, +featureSetsUplinkPerCC SEQUENCE (SIZE (1..maxPerCC-FeatureSets)) OF FeatureSetUplinkPerCC OPTIONAL, +... +[[ +featureSetsDownlink-v1540 SEQUENCE (SIZE (1..maxDownlinkFeatureSets)) OF FeatureSetDownlink-v1540 OPTIONAL, +featureSetsUplink-v1540 SEQUENCE (SIZE (1..maxUplinkFeatureSets)) OF FeatureSetUplink-v1540 OPTIONAL, +featureSetsUplinkPerCC-v1540 SEQUENCE (SIZE (1..maxPerCC-FeatureSets)) OF FeatureSetUplinkPerCC-v1540 OPTIONAL +]], +[[ +featureSetsDownlink-v15a0 SEQUENCE (SIZE (1..maxDownlinkFeatureSets)) OF FeatureSetDownlink-v15a0 OPTIONAL +]], +[[ +featureSetsDownlink-v1610 SEQUENCE (SIZE (1..maxDownlinkFeatureSets)) OF FeatureSetDownlink-v1610 OPTIONAL, +featureSetsUplink-v1610 SEQUENCE (SIZE (1..maxUplinkFeatureSets)) OF FeatureSetUplink-v1610 OPTIONAL, +featureSetsDownlinkPerCC-v1620 SEQUENCE (SIZE (1..maxPerCC-FeatureSets)) OF FeatureSetDownlinkPerCC-v1620 OPTIONAL +]], +[[ +featureSetsUplink-v1630 SEQUENCE (SIZE (1..maxUplinkFeatureSets)) OF FeatureSetUplink-v1630 OPTIONAL +]], +[[ +featureSetsUplink-v1640 SEQUENCE (SIZE (1..maxUplinkFeatureSets)) OF FeatureSetUplink-v1640 OPTIONAL +]], +[[ +featureSetsDownlink-v1700 SEQUENCE (SIZE (1..maxDownlinkFeatureSets)) OF FeatureSetDownlink-v1700 OPTIONAL, +featureSetsDownlinkPerCC-v1700 SEQUENCE (SIZE (1..maxPerCC-FeatureSets)) OF FeatureSetDownlinkPerCC-v1700 OPTIONAL, +featureSetsUplink-v1710 SEQUENCE (SIZE (1..maxUplinkFeatureSets)) OF FeatureSetUplink-v1710 OPTIONAL, +featureSetsUplinkPerCC-v1700 SEQUENCE (SIZE (1..maxPerCC-FeatureSets)) OF FeatureSetUplinkPerCC-v1700 OPTIONAL +]], +[[ +featureSetsDownlink-v1720 SEQUENCE (SIZE (1..maxDownlinkFeatureSets)) OF FeatureSetDownlink-v1720 OPTIONAL, +featureSetsDownlinkPerCC-v1720 SEQUENCE (SIZE (1..maxPerCC-FeatureSets)) OF FeatureSetDownlinkPerCC-v1720 OPTIONAL, +featureSetsUplink-v1720 SEQUENCE (SIZE (1..maxUplinkFeatureSets)) OF FeatureSetUplink-v1720 OPTIONAL +]], +[[ +featureSetsDownlink-v1730 SEQUENCE (SIZE (1..maxDownlinkFeatureSets)) OF FeatureSetDownlink-v1730 OPTIONAL, +featureSetsDownlinkPerCC-v1730 SEQUENCE (SIZE (1..maxPerCC-FeatureSets)) OF FeatureSetDownlinkPerCC-v1730 OPTIONAL +]], +[[ +featureSetsDownlink-v1800 SEQUENCE (SIZE (1..maxDownlinkFeatureSets)) OF FeatureSetDownlink-v1800 OPTIONAL, +featureSetsDownlinkPerCC-v1800 SEQUENCE (SIZE (1..maxPerCC-FeatureSets)) OF FeatureSetDownlinkPerCC-v1800 OPTIONAL, +featureSetsUplink-v1800 SEQUENCE (SIZE (1..maxUplinkFeatureSets)) OF FeatureSetUplink-v1800 OPTIONAL, +featureSetsUplinkPerCC-v1800 SEQUENCE (SIZE (1..maxPerCC-FeatureSets)) OF FeatureSetUplinkPerCC-v1800 OPTIONAL +]] +} + +FeatureSets-v16d0 ::= SEQUENCE { + featureSetsUplink-v16d0 SEQUENCE (SIZE (1..maxUplinkFeatureSets)) OF FeatureSetUplink-v16d0 OPTIONAL +} + +``` + +``` +-- TAG-FEATURESETS-STOP +-- ASN1STOP +``` + +#### FeatureSetUplink + +The IE *FeatureSetUplink* is used to indicate the features that the UE supports on the carriers corresponding to one band entry in a band combination. + +#### FeatureSetUplink information element + +``` +-- ASN1START +-- TAG-FEATURESETUPLINK-START + +FeatureSetUplink ::= SEQUENCE { + featureSetListPerUplinkCC SEQUENCE (SIZE (1.. maxNrofServingCells)) OF FeatureSetUplinkPerCC-Id, + scalingFactor ENUMERATED {f0p4, f0p75, f0p8} OPTIONAL, + dummy3 ENUMERATED {supported} OPTIONAL, + intraBandFreqSeparationUL FreqSeparationClass OPTIONAL, + searchSpaceSharingCA-UL ENUMERATED {supported} OPTIONAL, + dummy1 DummyI OPTIONAL, + supportedSRS-Resources SRS-Resources OPTIONAL, + twoPUCCH-Group ENUMERATED {supported} OPTIONAL, + dynamicSwitchSUL ENUMERATED {supported} OPTIONAL, + simultaneousTxSUL-NonSUL ENUMERATED {supported} OPTIONAL, + pusch-ProcessingType1-DifferentTB-PerSlot SEQUENCE { + scs-15kHz ENUMERATED {upto2, upto4, upto7} OPTIONAL, + scs-30kHz ENUMERATED {upto2, upto4, upto7} OPTIONAL, + scs-60kHz ENUMERATED {upto2, upto4, upto7} OPTIONAL, + scs-120kHz ENUMERATED {upto2, upto4, upto7} OPTIONAL + } OPTIONAL, + dummy2 DummyF OPTIONAL +} + +FeatureSetUplink-v1540 ::= SEQUENCE { + zeroSlotOffsetAperiodicSRS ENUMERATED {supported} OPTIONAL, + pa-PhaseDiscontinuityImpacts ENUMERATED {supported} OPTIONAL, + pusch-SeparationWithGap ENUMERATED {supported} OPTIONAL, + pusch-ProcessingType2 SEQUENCE { + scs-15kHz ProcessingParameters OPTIONAL, + scs-30kHz ProcessingParameters OPTIONAL, + scs-60kHz ProcessingParameters OPTIONAL + } OPTIONAL, + ul-MCS-TableAlt-DynamicIndication ENUMERATED {supported} OPTIONAL +} + +FeatureSetUplink-v1610 ::= SEQUENCE { + -- R1 11-5: PUSCH repetition Type B + pusch-RepetitionTypeB-r16 SEQUENCE { + maxNumberPUSCH-Tx-r16 ENUMERATED {n2, n3, n4, n7, n8, n12}, + hoppingScheme-r16 ENUMERATED {interSlotHopping, interRepetitionHopping, both} +``` + +``` + + } OPTIONAL, + -- R1 11-7: UL cancelation scheme for self-carrier + ul-CancellationSelfCarrier-r16 ENUMERATED {supported} OPTIONAL, + -- R1 11-7a: UL cancelation scheme for cross-carrier + ul-CancellationCrossCarrier-r16 ENUMERATED {supported} OPTIONAL, + -- R1 16-5c: The maximum number of SRS resources in one SRS resource set with usage set to 'codebook' for Mode 2 + ul-FullPwrMode2-MaxSRS-ResInSet-r16 ENUMERATED {n1, n2, n4} OPTIONAL, + + -- R1 22-4a/4b/4c/4d: CBG based transmission for UL with unicast PUSCH(s) per slot per CC with UE processing time Capability 1 + cbgPUSCH-ProcessingType1-DifferentTB-PerSlot-r16 SEQUENCE { + scs-15kHz-r16 ENUMERATED {one-pusch, upto2, upto4, upto7} OPTIONAL, + scs-30kHz-r16 ENUMERATED {one-pusch, upto2, upto4, upto7} OPTIONAL, + scs-60kHz-r16 ENUMERATED {one-pusch, upto2, upto4, upto7} OPTIONAL, + scs-120kHz-r16 ENUMERATED {one-pusch, upto2, upto4, upto7} OPTIONAL, + } OPTIONAL, + + -- R1 22-3a/3b/3c/3d: CBG based transmission for UL with unicast PUSCH(s) per slot per CC with UE processing time Capability 2 + cbgPUSCH-ProcessingType2-DifferentTB-PerSlot-r16 SEQUENCE { + scs-15kHz-r16 ENUMERATED {one-pusch, upto2, upto4, upto7} OPTIONAL, + scs-30kHz-r16 ENUMERATED {one-pusch, upto2, upto4, upto7} OPTIONAL, + scs-60kHz-r16 ENUMERATED {one-pusch, upto2, upto4, upto7} OPTIONAL, + scs-120kHz-r16 ENUMERATED {one-pusch, upto2, upto4, upto7} OPTIONAL, + } OPTIONAL, + supportedSRS-PosResources-r16 SRS-AllPosResources-r16 OPTIONAL, + intraFreqDAPS-UL-r16 SEQUENCE { + dummy ENUMERATED {supported} OPTIONAL, + intraFreqTwoTAGs-DAPS-r16 ENUMERATED {supported} OPTIONAL, + dummy1 ENUMERATED {supported} OPTIONAL, + dummy2 ENUMERATED {supported} OPTIONAL, + dummy3 ENUMERATED {short, long} OPTIONAL, + } OPTIONAL, + intraBandFreqSeparationUL-v1620 FreqSeparationClassUL-v1620 OPTIONAL, + + -- R1 11-3: More than one PUCCH for HARQ-ACK transmission within a slot + multiPUCCH-r16 SEQUENCE { + sub-SlotConfig-NCP-r16 ENUMERATED {set1, set2} OPTIONAL, + sub-SlotConfig-ECP-r16 ENUMERATED {set1, set2} OPTIONAL, + } OPTIONAL, + -- R1 11-3c: 2 PUCCH of format 0 or 2 for a single 7*2-symbol subslot based HARQ-ACK codebook + twoPUCCH-Type1-r16 ENUMERATED {supported} OPTIONAL, + -- R1 11-3d: 2 PUCCH of format 0 or 2 for a single 2*7-symbol subslot based HARQ-ACK codebook + twoPUCCH-Type2-r16 ENUMERATED {supported} OPTIONAL, + -- R1 11-3e: 1 PUCCH format 0 or 2 and 1 PUCCH format 1, 3 or 4 in the same subslot for a single 2*7-symbol HARQ-ACK codebooks + twoPUCCH-Type3-r16 ENUMERATED {supported} OPTIONAL, + -- R1 11-3f: 2 PUCCH transmissions in the same subslot for a single 2*7-symbol HARQ-ACK codebooks which are not covered by 11-3d and + -- 11-3e + twoPUCCH-Type4-r16 ENUMERATED {supported} OPTIONAL, + -- R1 11-3g: SR/HARQ-ACK multiplexing once per subslot using a PUCCH (or HARQ-ACK piggybacked on a PUSCH) when SR/HARQ-ACK + -- are supposed to be sent with different starting symbols in a subslot + mux-SR-HARQ-ACK-r16 ENUMERATED {supported} OPTIONAL, + dummy1 ENUMERATED {supported} OPTIONAL, + +``` + +``` + +dummy2 ENUMERATED {supported} OPTIONAL, +-- R1 11-4c: 2 PUCCH of format 0 or 2 for two HARQ-ACK codebooks with one 7*2-symbol sub-slot based HARQ-ACK codebook +twoPUCCH-Type5-r16 ENUMERATED {supported} OPTIONAL, +-- R1 11-4d: 2 PUCCH of format 0 or 2 in consecutive symbols for two HARQ-ACK codebooks with one 2*7-symbol sub-slot based HARQ-ACK +-- codebook +twoPUCCH-Type6-r16 ENUMERATED {supported} OPTIONAL, +-- R1 11-4e: 2 PUCCH of format 0 or 2 for two subslot based HARQ-ACK codebooks +twoPUCCH-Type7-r16 ENUMERATED {supported} OPTIONAL, +-- R1 11-4f: 1 PUCCH format 0 or 2 and 1 PUCCH format 1, 3 or 4 in the same subslot for HARQ-ACK codebooks with one 2*7-symbol +-- subslot based HARQ-ACK codebook +twoPUCCH-Type8-r16 ENUMERATED {supported} OPTIONAL, +-- R1 11-4g: 1 PUCCH format 0 or 2 and 1 PUCCH format 1, 3 or 4 in the same subslot for two subslot based HARQ-ACK codebooks +twoPUCCH-Type9-r16 ENUMERATED {supported} OPTIONAL, +-- R1 11-4h: 2 PUCCH transmissions in the same subslot for two HARQ-ACK codebooks with one 2*7-symbol subslot which are not covered +-- by 11-4c and 11-4e +twoPUCCH-Type10-r16 ENUMERATED {supported} OPTIONAL, +-- R1 11-4i: 2 PUCCH transmissions in the same subslot for two subslot based HARQ-ACK codebooks which are not covered by 11-4d and +-- 11-4f +twoPUCCH-Type11-r16 ENUMERATED {supported} OPTIONAL, +-- R1 12-1: UL intra-UE multiplexing/prioritization of overlapping channel/signals with two priority levels in physical layer +ul-IntraUE-Mux-r16 SEQUENCE { + pusch-PreparationLowPriority-r16 ENUMERATED {sym0, sym1, sym2}, + pusch-PreparationHighPriority-r16 ENUMERATED {sym0, sym1, sym2} +} OPTIONAL, +-- R1 16-5a: Supported UL full power transmission mode of fullpower +ul-FullPwrMode-r16 ENUMERATED {supported} OPTIONAL, +-- R1 18-5d: Processing up to X unicast DCI scheduling for UL per scheduled CC +crossCarrierSchedulingProcessing-DiffSCS-r16 SEQUENCE { + scs-15kHz-120kHz-r16 ENUMERATED {n1,n2,n4} OPTIONAL, + scs-15kHz-60kHz-r16 ENUMERATED {n1,n2,n4} OPTIONAL, + scs-30kHz-120kHz-r16 ENUMERATED {n1,n2,n4} OPTIONAL, + scs-15kHz-30kHz-r16 ENUMERATED {n2} OPTIONAL, + scs-30kHz-60kHz-r16 ENUMERATED {n2} OPTIONAL, + scs-60kHz-120kHz-r16 ENUMERATED {n2} OPTIONAL, +} OPTIONAL, +-- R1 16-5b: Supported UL full power transmission mode of fullpowerModel +ul-FullPwrModel-r16 ENUMERATED {supported} OPTIONAL, +-- R1 16-5c-2: Ports configuration for Mode 2 +ul-FullPwrMode2-SRSConfig-diffNumSRSPorts-r16 ENUMERATED {p1-2, p1-4, p1-2-4} OPTIONAL, +-- R1 16-5c-3: TPMI group for Mode 2 +ul-FullPwrMode2-TPMIGroup-r16 SEQUENCE { + twoPorts-r16 BIT STRING(SIZE(2)) OPTIONAL, + fourPortsNonCoherent-r16 ENUMERATED{g0, g1, g2, g3} OPTIONAL, + fourPortsPartialCoherent-r16 ENUMERATED{g0, g1, g2, g3, g4, g5, g6} OPTIONAL +} OPTIONAL +} + +FeatureSetUplink-v1630 ::= SEQUENCE { +-- R1 22-8: For SRS for CB PUSCH and antenna switching on FR1 with symbol level offset for aperiodic SRS transmission +offsetSRS-CB-PUSCH-Ant-Switch-fr1-r16 ENUMERATED {supported} OPTIONAL, +-- R1 22-8a: PDCCH monitoring on any span of up to 3 consecutive OFDM symbols of a slot and constrained timeline for SRS for CB + +``` + +``` + + -- PUSCH and antenna switching on FR1 + offsetSRS-CB-PUSCH-PDCCH-MonitorSingleOcc-fr1-r16 ENUMERATED {supported} OPTIONAL, + -- R1 22-8b: For type 1 CSS with dedicated RRC configuration, type 3 CSS, and UE-SS, monitoring occasion can be any OFDM symbol(s) + -- of a slot for Case 2 and constrained timeline for SRS for CB PUSCH and antenna switching on FR1 + offsetSRS-CB-PUSCH-PDCCH-MonitorAnyOccWithoutGap-fr1-r16 ENUMERATED {supported} OPTIONAL, + -- R1 22-8c: For type 1 CSS with dedicated RRC configuration, type 3 CSS, and UE-SS, monitoring occasion can be any OFDM symbol(s) + -- of a slot for Case 2 with a DCI gap and constrained timeline for SRS for CB PUSCH and antenna switching on FR1 + offsetSRS-CB-PUSCH-PDCCH-MonitorAnyOccWithGap-fr1-r16 ENUMERATED {supported} OPTIONAL, + dummy ENUMERATED {supported} OPTIONAL, + -- R1 22-9: Cancellation of PUCCH, PUSCH or PRACH with a DCI scheduling a PDSCH or CSI-RS or a DCI format 2-0 for SFI + partialCancellationPUCCH-PUSCH-PRACH-TX-r16 ENUMERATED {supported} OPTIONAL +} + +FeatureSetUplink-v1640 ::= SEQUENCE { + -- R1 11-4: Two HARQ-ACK codebooks with up to one sub-slot based HARQ-ACK codebook (i.e. slot-based + slot-based, or slot-based + + -- sub-slot based) simultaneously constructed for supporting HARQ-ACK codebooks with different priorities at a UE + twoHARQ-ACK-Codebook-type1-r16 SubSlot-Config-r16 OPTIONAL, + -- R1 11-4a: Two sub-slot based HARQ-ACK codebooks simultaneously constructed for supporting HARQ-ACK codebooks with different + -- priorities at a UE + twoHARQ-ACK-Codebook-type2-r16 SubSlot-Config-r16 OPTIONAL, + -- R1 22-8d: All PDCCH monitoring occasion can be any OFDM symbol(s) of a slot for Case 2 with a span gap and constrained timeline + -- for SRS for CB PUSCH and antenna switching on FR1 + offsetSRS-CB-PUSCH-PDCCH-MonitorAnyOccWithSpanGap-fr1-r16 SEQUENCE { + scs-15kHz-r16 ENUMERATED {set1, set2, set3} OPTIONAL, + scs-30kHz-r16 ENUMERATED {set1, set2, set3} OPTIONAL, + scs-60kHz-r16 ENUMERATED {set1, set2, set3} OPTIONAL + } OPTIONAL +} + +FeatureSetUplink-v16d0 ::= SEQUENCE { + pusch-RepetitionTypeB-v16d0 SEQUENCE { + maxNumberPUSCH-Tx-Cap1-r16 ENUMERATED {n2, n3, n4, n7, n8, n12}, + maxNumberPUSCH-Tx-Cap2-r16 ENUMERATED {n2, n3, n4, n7, n8, n12} + } OPTIONAL +} + +FeatureSetUplink-v1710 ::= SEQUENCE { + -- R1 23-3-1 Multi-TRP PUSCH repetition (type A) -codebook based + mTRP-PUSCH-TypeA-CB-r17 ENUMERATED {n1,n2,n4} OPTIONAL, + -- R1 23-3-1-2 Multi-TRP PUSCH repetition (type A) - non-codebook based + mTRP-PUSCH-RepetitionTypeA-r17 ENUMERATED {n1,n2,n3,n4} OPTIONAL, + -- R1 23-3-3 Multi-TRP PUCCH repetition-intra-slot + mTRP-PUCCH-IntraSlot-r17 ENUMERATED {pf0-2, pf1-3-4, pf0-4} OPTIONAL, + -- R1 23-8-4 Maximum 2 SP and 1 periodic SRS sets for antenna switching + srs-AntennaSwitching2SP-1Periodic-r17 ENUMERATED {supported} OPTIONAL, + -- R1 23-8-9 Extension of aperiodic SRS configuration for 1T4R, 1T2R and 2T4R + srs-ExtensionAperiodicSRS-r17 ENUMERATED {supported} OPTIONAL, + -- R1 23-8-10 1 aperiodic SRS resource set for 1T4R + srs-OneAP-SRS-r17 ENUMERATED {supported} OPTIONAL, + -- R4 16-8 UE power class per band per band combination + ue-PowerClassPerBandPerBC-r17 ENUMERATED {pc1dot5, pc2, pc3} OPTIONAL +} + +``` + +``` + +-- R4 17-8 UL transmission in FR2 bands within an UL gap when the UL gap is activated +tx-Support-UL-GapFR2-r17 ENUMERATED {supported} OPTIONAL +} + +FeatureSetUplink-v1720 ::= SEQUENCE { + -- R1 25-3: Repetitions for PUCCH format 0, 1, 2, 3 and 4 over multiple PUCCH subslots with configured K = 2, 4, 8 + pucch-Repetition-F0-1-2-3-4-RRConfig-r17 ENUMERATED {supported} OPTIONAL, + -- R1 25-3a: Repetitions for PUCCH format 0, 1, 2, 3 and 4 over multiple PUCCH subslots using dynamic repetition indication + pucch-Repetition-F0-1-2-3-4-DynamicIndication-r17 ENUMERATED {supported} OPTIONAL, + -- R1 25-3b: Inter-subslot frequency hopping for PUCCH repetitions + interSubslotFreqHopping-PUCCH-r17 ENUMERATED {supported} OPTIONAL, + -- R1 25-8: Semi-static HARQ-ACK codebook for sub-slot PUCCH + semiStaticHARQ-ACK-CodebookSub-SlotPUCCH-r17 ENUMERATED {supported} OPTIONAL, + -- R1 25-14: PHY prioritization of overlapping low-priority DG-PUSCH and high-priority CG-PUSCH + phy-PrioritizationLowPriorityDG-HighPriorityCG-r17 INTEGER(1..16) OPTIONAL, + -- R1 25-15: PHY prioritization of overlapping high-priority DG-PUSCH and low-priority CG-PUSCH + phy-PrioritizationHighPriorityDG-LowPriorityCG-r17 SEQUENCE { + pusch-PreparationLowPriority-r17 ENUMERATED{sym0, sym1, sym2}, + additionalCancellationTime-r17 SEQUENCE { + scs-15kHz-r17 ENUMERATED{sym0, sym1, sym2} OPTIONAL, + scs-30kHz-r17 ENUMERATED{sym0, sym1, sym2, sym3, sym4} OPTIONAL, + scs-60kHz-r17 ENUMERATED{sym0, sym1, sym2, sym3, sym4, sym5, sym6, sym7, sym8} OPTIONAL, + scs-120kHz-r17 ENUMERATED{sym0, sym1, sym2, sym3, sym4, sym5, sym6, sym7, sym8, sym9, + sym10, sym11, sym12, sym13, sym14, sym15, sym16} OPTIONAL + }, + maxNumberCarriers-r17 INTEGER(1..16) + } OPTIONAL, + -- R4 17-5 Support of UL DC location(s) report + extendedDC-LocationReport-r17 ENUMERATED {supported} OPTIONAL +} + +FeatureSetUplink-v1800 ::= SEQUENCE { + -- R1 40-3-3-2: Number of delay values + tdcpNumberDelayValue-r18 INTEGER (2..4) OPTIONAL, + -- R1 40-3-3-4: Phase report + phaseReportMoreThanOne-r18 ENUMERATED {supported} OPTIONAL, + -- R1 40-4-6d: 2 symbols front-loaded DMRS (uplink) for Rel.18 enhanced DMRS ports for PUSCH + pusch-2SymbolFL-DMRS-r18 ENUMERATED {supported} OPTIONAL, + -- R1 40-4-6e: 2-symbol FL DMRS + one additional 2-symbols DMRS for Rel.18 enhanced DMRS ports for PUSCH + pusch-2SymbolFL-DMRS-Addition2Symbol-r18 ENUMERATED {supported} OPTIONAL, + -- R1 40-4-6f: 1 symbol FL DMRS and 3 additional DMRS symbols for Rel.18 enhanced DMRS ports for PUSCH + pusch-1SymbolFL-DMRS-Addition3Symbol-r18 ENUMERATED {supported} OPTIONAL, + -- R1 40-4-12: Support Rel.18 UL DMRS with single-DCI based M-TRP + ul-DMRS-SingleDCI-M-TRP-r18 ENUMERATED {supported} OPTIONAL, + -- R1 40-4-13: Support Rel.18 UL DMRS with M-DCI based M-TRP + ul-DMRS-M-DCI-M-TRP-r18 ENUMERATED {supported} OPTIONAL, + -- R1 40-5-5: Maximum 2 SP and 1 periodic SRS sets for 8T8R antenna switching + max2SP1SRS8T8R-AntennaSwitch-r18 ENUMERATED {supported} OPTIONAL, + + -- R1 40-6-4: Single-DCI based STx2P SFN scheme for PUCCH + pucch-SingleDCI-STx2P-SFN-r18 ENUMERATED {pf0-2, pf1-3-4, pf0-4} OPTIONAL, + +``` + +``` + +-- R4 27-1 TxDiversity for 4Tx +txDiversity4Tx-r18 ENUMERATED {supported} OPTIONAL, + +-- R4 44-1 TxDiversity for 2Tx +txDiversity2Tx-r18 ENUMERATED {supported} OPTIONAL +} + +SubSlot-Config-r16 ::= SEQUENCE { + sub-SlotConfig-NCP-r16 ENUMERATED {n4,n5,n6,n7} OPTIONAL, + sub-SlotConfig-ECP-r16 ENUMERATED {n4,n5,n6} OPTIONAL +} + +SRS-AllPosResources-r16 ::= SEQUENCE { + srs-PosResources-r16 SRS-PosResources-r16, + srs-PosResourceAP-r16 SRS-PosResourceAP-r16 OPTIONAL, + srs-PosResourceSP-r16 SRS-PosResourceSP-r16 OPTIONAL +} + +SRS-PosResources-r16 ::= SEQUENCE { + maxNumberSRS-PosResourceSetPerBWP-r16 ENUMERATED {n1, n2, n4, n8, n12, n16}, + maxNumberSRS-PosResourcesPerBWP-r16 ENUMERATED {n1, n2, n4, n8, n16, n32, n64}, + maxNumberSRS-ResourcesPerBWP-PerSlot-r16 ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10, n12, n14}, + maxNumberPeriodicSRS-PosResourcesPerBWP-r16 ENUMERATED {n1, n2, n4, n8, n16, n32, n64}, + maxNumberPeriodicSRS-PosResourcesPerBWP-PerSlot-r16 ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10, n12, n14} +} + +SRS-PosResourceAP-r16 ::= SEQUENCE { + maxNumberAP-SRS-PosResourcesPerBWP-r16 ENUMERATED {n1, n2, n4, n8, n16, n32, n64}, + maxNumberAP-SRS-PosResourcesPerBWP-PerSlot-r16 ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10, n12, n14} +} + +SRS-PosResourceSP-r16 ::= SEQUENCE { + maxNumberSP-SRS-PosResourcesPerBWP-r16 ENUMERATED {n1, n2, n4, n8, n16, n32, n64}, + maxNumberSP-SRS-PosResourcesPerBWP-PerSlot-r16 ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10, n12, n14} +} + +SRS-Resources ::= SEQUENCE { + maxNumberAperiodicSRS-PerBWP ENUMERATED {n1, n2, n4, n8, n16}, + maxNumberAperiodicSRS-PerBWP-PerSlot INTEGER (1..6), + maxNumberPeriodicSRS-PerBWP ENUMERATED {n1, n2, n4, n8, n16}, + maxNumberPeriodicSRS-PerBWP-PerSlot INTEGER (1..6), + maxNumberSemiPersistentSRS-PerBWP ENUMERATED {n1, n2, n4, n8, n16}, + maxNumberSemiPersistentSRS-PerBWP-PerSlot INTEGER (1..6), + maxNumberSRS-Ports-PerResource ENUMERATED {n1, n2, n4} +} + +DummyF ::= SEQUENCE { + maxNumberPeriodicCSI-ReportPerBWP INTEGER (1..4), + maxNumberAperiodicCSI-ReportPerBWP INTEGER (1..4), + maxNumberSemiPersistentCSI-ReportPerBWP INTEGER (0..4), +} + +``` + +``` + +simultaneousCSI-ReportsAllCC INTEGER (5..32) +} + +-- TAG-FEATURESETUPLINK-STOP +-- ASN1STOP + +``` + +##### FeatureSetUplink field descriptions + +##### **featureSetListPerUplinkCC** + +Indicates which features the UE supports on the individual UL carriers of the feature set (and hence of a band entry that refers to the feature set). The UE shall hence include at least as many *FeatureSetUplinkPerCC-Id* in this list as the number of carriers it supports according to the *ca-BandwidthClassUL*, except if indicating additional functionality by reducing the number of *FeatureSetUplinkPerCC-Id* in the feature set (see NOTE 1 in *FeatureSetCombination* IE description). The order of the elements in this list is not relevant, i.e., the network may configure any of the carriers in accordance with any of the *FeatureSetUplinkPerCC-Id* in this list. + +#### — **FeatureSetUplinkId** + +The IE *FeatureSetUplinkId* identifies an uplink feature set. The *FeatureSetUplinkId* of a *FeatureSetUplink* is the index position of the *FeatureSetUplink* in the *featureSetsUplink* list in the *FeatureSets* IE. The first element in the list is referred to by *FeatureSetUplinkId* = 1, and so on. The *FeatureSetUplinkId* = 0 is not used by an actual *FeatureSetUplink* but means that the UE does not support a carrier in this band of a band combination. + +#### **FeatureSetUplinkId information element** + +``` + +-- ASN1START +-- TAG-FEATURESETUPLINKID-START + +FeatureSetUplinkId ::= INTEGER (0..maxUplinkFeatureSets) + +-- TAG-FEATURESETUPLINKID-STOP +-- ASN1STOP + +``` + +#### — **FeatureSetUplinkPerCC** + +The IE *FeatureSetUplinkPerCC* indicates a set of features that the UE supports on the corresponding carrier of one band entry of a band combination. + +##### **FeatureSetUplinkPerCC information element** + +``` + +-- ASN1START +-- TAG-FEATURESETUPLINKPERCC-START + +FeatureSetUplinkPerCC ::= SEQUENCE { + supportedSubcarrierSpacingUL SubcarrierSpacing, + supportedBandwidthUL SupportedBandwidth, + channelBW-90mhz ENUMERATED {supported} OPTIONAL, + mimo-CB-PUSCH SEQUENCE { + +``` + +``` + + maxNumberMIMO-LayersCB-PUSCH MIMO-LayersUL OPTIONAL, + maxNumberSRS-ResourcePerSet INTEGER (1..2) + } + maxNumberMIMO-LayersNonCB-PUSCH MIMO-LayersUL OPTIONAL, + supportedModulationOrderUL ModulationOrder OPTIONAL, +} + +FeatureSetUplinkPerCC-v1540 ::= SEQUENCE { + mimo-NonCB-PUSCH SEQUENCE { + maxNumberSRS-ResourcePerSet INTEGER (1..4), + maxNumberSimultaneousSRS-ResourceTx INTEGER (1..4) + } OPTIONAL +} + +FeatureSetUplinkPerCC-v1700 ::= SEQUENCE { + supportedMinBandwidthUL-r17 SupportedBandwidth-v1700 OPTIONAL, + -- R1 23-3-1-3 FeMIMO: Multi-TRP PUSCH repetition (type B) - non-codebook based + mTRP-PUSCH-RepetitionTypeB-r17 ENUMERATED {n1,n2,n3,n4} OPTIONAL, + -- R1 23-3-1-1 -codebook based Multi-TRP PUSCH repetition (type B) + mTRP-PUSCH-TypeB-CB-r17 ENUMERATED {n1,n2,n4} OPTIONAL, + supportedBandwidthUL-v1710 SupportedBandwidth-v1700 OPTIONAL +} + +FeatureSetUplinkPerCC-v1800 ::= SEQUENCE { + -- R1 40-6-1: Single-DCI based STx2P SDM scheme for PUSCH-codebook + puscb-CB-SingleDCI-STx2P-SDM-r18 SEQUENCE { + maxNumberSRS-ResourcePerSet-r18 ENUMERATED {n1,n2,n4}, + maxNumberLayerPerPanel-r18 INTEGER (1..2), + maxNumberNZP-PUSCH-PortsPerSet-r18 ENUMERATED {n1,n2,n4}, + maxNumberSRS-AntennaPortsPerSet-r18 ENUMERATED {n1,n2,n4} + } + -- R1 40-6-1a: Single-DCI based STx2P SDM scheme for PUSCH-noncodebook + puscb-NonCB-SingleDCI-STx2P-SDM-r18 SEQUENCE { + maxNumberSRS-ResourcePerSet-r18 INTEGER (1..4), + maxNumberLayerPerPanel-r18 INTEGER (1..2), + maxNumberSimulSRS-ResourcePerSet-r18 INTEGER (1..4) + } + -- R1 40-6-2: Single-DCI based STx2P SFN scheme for PUSCH-codebook + puscb-CB-SingleDCI-STx2P-SFN-r18 SEQUENCE { + maxNumberSRS-ResourcePerSet-r18 ENUMERATED {n1,n2,n4}, + maxNumberLayerPerSet-r18 INTEGER (1..2), + maxNumberSRS-AntennaPortsPerSet-r18 ENUMERATED {n1,n2,n4}, + maxNumberNZP-PUSCH-PortsPerSet-r18 ENUMERATED {n1,n2,n4} + } + -- R1 40-6-2a: Single-DCI based STx2P SFN scheme for PUSCH-noncodebook + puscb-NonCB-SingleDCI-STx2P-SFN-r18 SEQUENCE { + maxNumberSRS-ResourcePerSet-r18 INTEGER (1..4), + maxNumberLayerPerSet-r18 INTEGER (1..2), + maxNumberSimulSRS-ResourcePerSet-r18 INTEGER (1..4) + } + -- R1 40-6-3a: codebook multi-DCI based STx2P PUSCH+PUSCH for DG+DG + twoPUSCH-CB-MultiDCI-STx2P-DG-DG-r18 SEQUENCE { + +``` + +``` + +maxNumberSRS-ResourcePerSet-r18 ENUMERATED {n1, n2, n4}, +maxNumberLayerOverlapping-r18 INTEGER (1..2), +maxNumberNZP-PUSCH-Overlapping-r18 ENUMERATED {n1, n2, n4}, +maxNumberPUSCH-PerCORESET-PerSlot-r18 SEQUENCE { + scs-60kHz-r18 ENUMERATED {n1,n2,n3,n4,n7} OPTIONAL, + scs-120kHz-r18 ENUMERATED {n1,n2,n3,n4,n7} OPTIONAL, +} OPTIONAL, +maxNumberTotalLayerOverlapping-r18 INTEGER (2..4), +maxNumberSRS-AntennaPortsPerSet-r18 ENUMERATED {n1,n2,n4} +} OPTIONAL, +-- R1 40-6-3b: Noncodebook multi-DCI based STx2P PUSCH+PUSCH for DG+DG +twoPUSCH-NonCB-MultiDCI-STx2P-DG-DG-r18 SEQUENCE { + maxNumberSRS-ResourcePerSet-r18 INTEGER (1..4), + maxNumberLayerOverlapping-r18 INTEGER (1..2), + maxNumberSimulSRS-ResourcePerSet-r18 INTEGER (1..4), + maxNumberPUSCH-PerCORESET-PerSlot-r18 SEQUENCE { + scs-60kHz-r18 ENUMERATED {n1,n2,n3,n4,n7} OPTIONAL, + scs-120kHz-r18 ENUMERATED {n1,n2,n3,n4,n7} OPTIONAL, + } OPTIONAL, + maxNumberTotalLayerOverlapping-r18 INTEGER (2..4) +} OPTIONAL, +-- R1 40-6-6: Out-of-order operation for multi-DCI based STx2P PUSCH+PUSCH +twoPUSCH-MultiDCI-STx2P-OutOfOrder-r18 ENUMERATED {supported} OPTIONAL, + +-- R1 40-7-1a: Codebook-based 8Tx PUSCH-codebook1 +codebook1-8TxPUSCH-r18 ENUMERATED {n4-1,n2-2,both} OPTIONAL, +-- R1 40-7-1b: Codebook-based 8Tx PUSCH-codebook2 +codebook2-8TxPUSCH-r18 ENUMERATED {supported} OPTIONAL, +-- R1 40-7-1c: Codebook-based 8Tx PUSCH-codebook3 +codebook3-8TxPUSCH-r18 ENUMERATED {supported} OPTIONAL, +-- R1 40-7-1d: Codebook-based 8Tx PUSCH-codebook4 +codebook4-8TxPUSCH-r18 ENUMERATED {supported} OPTIONAL, +} + +-- TAG-FEATURESETUPLINKPERCC-STOP +-- ASN1STOP + +``` + +##### – **FeatureSetUplinkPerCC-Id** + +The IE *FeatureSetUplinkPerCC-Id* identifies a set of features applicable to one carrier of a feature set. The *FeatureSetUplinkPerCC-Id* of a *FeatureSetUplinkPerCC* is the index position of the *FeatureSetUplinkPerCC* in the *featureSetsUplinkPerCC*. The first element in the list is referred to by *FeatureSetUplinkPerCC-Id* = 1, and so on. + +#### **FeatureSetUplinkPerCC-Id information element** + +``` + +-- ASN1START +-- TAG-FEATURESETUPLINKPERCC-ID-START + +FeatureSetUplinkPerCC-Id := INTEGER (1..maxPerCC-FeatureSets) + +``` + +``` +-- TAG-FEATURESETUPLINKPERCC-ID-STOP +-- ASN1STOP +``` + +##### – *FreqBandIndicatorEUTRA* + +``` +-- ASN1START +-- TAG-FREQBANDINDICATOREUTRA-START + +FreqBandIndicatorEUTRA ::= INTEGER (1..maxBandsEUTRA) + +-- TAG-FREQBANDINDICATOREUTRA-STOP +-- ASN1STOP +``` + +##### – *FreqBandList* + +The IE *FreqBandList* is used by the network to request NR CA, NR non-CA and/or MR-DC band combinations for specific NR and/or E-UTRA frequency bands and/or up to a specific number of carriers and/or up to specific aggregated bandwidth. This is also used to request feature sets (for NR) and feature set combinations (for NR and MR-DC). For NR sidelink communication, this is used by the initiating UE to request sidelink UE radio access capabilities from the peer UE. This is also used to request lower MSD capability for specific NR frequency bands for the UE supporting lower MSD. + +#### *FreqBandList* information element + +``` +-- ASN1START +-- TAG-FREQBANDLIST-START + +FreqBandList ::= SEQUENCE (SIZE (1..maxBandsMRDC)) OF FreqBandInformation + +FreqBandInformation ::= CHOICE { + bandInformationEUTRA FreqBandInformationEUTRA, + bandInformationNR FreqBandInformationNR +} + +FreqBandInformationEUTRA ::= SEQUENCE { + bandEUTRA FreqBandIndicatorEUTRA, + ca-BandwidthClassDL-EUTRA CA-BandwidthClassEUTRA OPTIONAL, -- Need N + ca-BandwidthClassUL-EUTRA CA-BandwidthClassEUTRA OPTIONAL, -- Need N +} + +FreqBandInformationNR ::= SEQUENCE { + bandNR FreqBandIndicatorNR, + maxBandwidthRequestedDL AggregatedBandwidth OPTIONAL, -- Need N + maxBandwidthRequestedUL AggregatedBandwidth OPTIONAL, -- Need N + maxCarriersRequestedDL INTEGER (1..maxNrofServingCells) OPTIONAL, -- Need N + maxCarriersRequestedUL INTEGER (1..maxNrofServingCells) OPTIONAL, -- Need N +} +``` + +``` +AggregatedBandwidth ::= ENUMERATED {mhz50, mhz100, mhz150, mhz200, mhz250, mhz300, mhz350, + mhz400, mhz450, mhz500, mhz550, mhz600, mhz650, mhz700, mhz750, mhz800} + +-- TAG-FREQBANDLIST-STOP +-- ASN1STOP +``` + +#### – *FreqSeparationClass* + +The IE *FreqSeparationClass* is used for an intra-band non-contiguous CA band combination to indicate frequency separation between lower edge of lowest CC and upper edge of highest CC in a frequency band. + +#### *FreqSeparationClass* information element + +``` +-- ASN1START +-- TAG-FREQSEPARATIONCLASS-START + +FreqSeparationClass ::= ENUMERATED { mhz800, mhz1200, mhz1400, ..., mhz400-v1650, mhz600-v1650} + +FreqSeparationClassDL-v1620 ::= ENUMERATED {mhz1000, mhz1600, mhz1800, mhz2000, mhz2200, mhz2400} + +FreqSeparationClassUL-v1620 ::= ENUMERATED {mhz1000} + +-- TAG-FREQSEPARATIONCLASS-STOP +-- ASN1STOP +``` + +##### – *FreqSeparationClassDL-Only* + +The IE *FreqSeparationClassDL-Only* is used to indicate the frequency separation between lower edge of lowest CC and upper edge of highest CC of DL only frequency spectrum in a frequency band. + +#### *FreqSeparationClassDL-Only* information element + +``` +-- ASN1START +-- TAG-FREQSEPARATIONCLASSDL-Only-START + +FreqSeparationClassDL-Only-r16 ::= ENUMERATED {mhz200, mhz400, mhz600, mhz800, mhz1000, mhz1200} + +-- TAG-FREQSEPARATIONCLASSDL-Only-STOP +-- ASN1STOP +``` + +#### – *FR2-2-AccessParamsPerBand* + +The IE *FR2-2-AccessParamsPerBand* is used to convey FR2-2 related parameters specific for a certain frequency band (not per feature set or band combination). + +#### FR2-2-AccessParamsPerBand information element + +``` + +-- ASN1START +-- TAG-FR2-2-ACCESSPARAMSPERBAND-START + +FR2-2-AccessParamsPerBand-r17 ::= SEQUENCE { + -- R1 24-1: Basic FR2-2 DL support + dl-FR2-2-SCS-120kHz-r17 ENUMERATED {supported} OPTIONAL, + -- R1 24-1a: Basic FR2-2 UL support + ul-FR2-2-SCS-120kHz-r17 ENUMERATED {supported} OPTIONAL, + -- R1 24-2: 120KHz SSB support for initial access in FR2-2 + initialAccessSSB-120kHz-r17 ENUMERATED {supported} OPTIONAL, + -- R1 24-1b: Wideband PRACH for 120 kHz in FR2-2 + widebandPRACH-SCS-120kHz-r17 ENUMERATED {supported} OPTIONAL, + -- R1 24-1c: Multi-RB support PUCCH format 0/1/4 for 120 kHz in FR2-2 + multiRB-PUCCH-SCS-120kHz-r17 ENUMERATED {supported} OPTIONAL, + -- R1 24-1d: Multiple PDSCH scheduling by single DCI for 120kHz in FR2-2 + multiPDSCH-SingleDCI-FR2-2-SCS-120kHz-r17 ENUMERATED {supported} OPTIONAL, + -- R1 24-1e: Multiple PUSCH scheduling by single DCI for 120kHz in FR2-2 + multiPUSCH-SingleDCI-FR2-2-SCS-120kHz-r17 ENUMERATED {supported} OPTIONAL, + -- R1 24-4: 480KHz SCS support for DL + dl-FR2-2-SCS-480kHz-r17 ENUMERATED {supported} OPTIONAL, + -- R1 24-4a: 480KHz SCS support for UL + ul-FR2-2-SCS-480kHz-r17 ENUMERATED {supported} OPTIONAL, + -- R1 24-3: 480KHz SSB support for initial access in FR2-2 + initialAccessSSB-480kHz-r17 ENUMERATED {supported} OPTIONAL, + -- R1 24-4b: Wideband PRACH for 480 kHz in FR2-2 + widebandPRACH-SCS-480kHz-r17 ENUMERATED {supported} OPTIONAL, + -- R1 24-4c: Multi-RB support PUCCH format 0/1/4 for 480 kHz in FR2-2 + multiRB-PUCCH-SCS-480kHz-r17 ENUMERATED {supported} OPTIONAL, + -- R1 24-4f: Enhanced PDCCH monitoring for 480KHz in FR2-2 + enhancedPDCCH-monitoringSCS-480kHz-r17 ENUMERATED {supported} OPTIONAL, + -- R1 24-5: 960KHz SCS support for DL + dl-FR2-2-SCS-960kHz-r17 ENUMERATED {supported} OPTIONAL, + -- R1 24-5a: 960KHz SCS support for UL + ul-FR2-2-SCS-960kHz-r17 ENUMERATED {supported} OPTIONAL, + -- R1 24-5c: Multi-RB support PUCCH format 0/1/4 for 960 kHz in FR2-2 + multiRB-PUCCH-SCS-960kHz-r17 ENUMERATED {supported} OPTIONAL, + -- R1 24-5f: Enhanced PDCCH monitoring for 960KHz in FR2-2 + enhancedPDCCH-monitoringSCS-960kHz-r17 SEQUENCE { + pdcch-monitoring4-1-r17 ENUMERATED {supported} OPTIONAL, + pdcch-monitoring4-2-r17 ENUMERATED {supported} OPTIONAL, + pdcch-monitoring8-4-r17 ENUMERATED {supported} OPTIONAL, + } + -- R1 24-6: Type 1 channel access procedure in uplink for FR2-2 with shared spectrum channel access + type1-ChannelAccess-FR2-2-r17 ENUMERATED {supported} OPTIONAL, + -- R1 24-7: Type 2 channel access procedure in uplink for FR2-2 with shared spectrum channel access + type2-ChannelAccess-FR2-2-r17 ENUMERATED {supported} OPTIONAL, + -- R1 24-10: Reduced beam switching time delay + reduced-BeamSwitchTiming-FR2-2-r17 ENUMERATED {supported} OPTIONAL, + -- R1 24-8: 32 DL HARQ processes for FR 2-2 +} + +``` + +``` + +support32-DL-HARQ-ProcessPerSCS-r17 SEQUENCE { + scs-120kHz-r17 ENUMERATED {supported} OPTIONAL, + scs-480kHz-r17 ENUMERATED {supported} OPTIONAL, + scs-960kHz-r17 ENUMERATED {supported} OPTIONAL +} OPTIONAL, +-- R1 24-9: 32 UL HARQ processes for FR 2-2 +support32-UL-HARQ-ProcessPerSCS-r17 SEQUENCE { + scs-120kHz-r17 ENUMERATED {supported} OPTIONAL, + scs-480kHz-r17 ENUMERATED {supported} OPTIONAL, + scs-960kHz-r17 ENUMERATED {supported} OPTIONAL +} OPTIONAL, +... +[[ +-- R4 15-1: 64QAM for PUSCH for FR2-2 +modulation64-QAM-PUSCH-FR2-2-r17 ENUMERATED {supported} OPTIONAL +]] +} + +-- TAG-FR2-2-ACCESSPARAMSPERBAND-STOP +-- ASN1STOP + +``` + +### HighSpeedParameters + +The IE *HighSpeedParameters* is used to convey capabilities related to high speed scenarios. + +#### HighSpeedParameters information element + +``` + +-- ASN1START +-- TAG-HIGHSPEEDPARAMETERS-START + +HighSpeedParameters-r16 ::= SEQUENCE { + measurementEnhancement-r16 ENUMERATED {supported} OPTIONAL, + demodulationEnhancement-r16 ENUMERATED {supported} OPTIONAL +} + +HighSpeedParameters-v1650 ::= CHOICE { + intraNR-MeasurementEnhancement-r16 ENUMERATED {supported}, + interRAT-MeasurementEnhancement-r16 ENUMERATED {supported} +} + +HighSpeedParameters-v1700 ::= SEQUENCE { + -- R4 18-1: Enhanced RRM requirements specified for CA for FR1 HST + measurementEnhancementCA-r17 ENUMERATED {supported} OPTIONAL, + -- R4 18-2: Enhanced RRM requirements specified for inter-frequency measurement in connected mode for FR1 HST + measurementEnhancementInterFreq-r17 ENUMERATED {supported} OPTIONAL +} + +-- TAG-HIGHSPEEDPARAMETERS-STOP +-- ASN1STOP + +``` + +### IMS-Parameters + +The IE *IMS-Parameters* is used to convey capabilities related to IMS. + +#### IMS-Parameters information element + +``` +-- ASN1START +-- TAG-IMS-PARAMETERS-START + +IMS-Parameters ::= SEQUENCE { + ims-ParametersCommon IMS-ParametersCommon OPTIONAL, + ims-ParametersFRX-Diff IMS-ParametersFRX-Diff OPTIONAL, + ... +} + +IMS-Parameters-v1700 ::= SEQUENCE { + ims-ParametersFR2-2-r17 IMS-ParametersFR2-2-r17 OPTIONAL +} + +IMS-ParametersCommon ::= SEQUENCE { + voiceOverEUTRA-5GC ENUMERATED {supported} OPTIONAL, + .../ + [[ + voiceOverSCG-BearerEUTRA-5GC ENUMERATED {supported} OPTIONAL + ]], + [[ + voiceFallbackIndicationEPS-r16 ENUMERATED {supported} OPTIONAL + ]] +} + +IMS-ParametersFRX-Diff ::= SEQUENCE { + voiceOverNR ENUMERATED {supported} OPTIONAL, + ... +} + +IMS-ParametersFR2-2-r17 ::= SEQUENCE { + voiceOverNR-r17 ENUMERATED {supported} OPTIONAL, + ... +} + +-- TAG-IMS-PARAMETERS-STOP +-- ASN1STOP +``` + +#### — *InterRAT-Parameters* + +The IE *InterRAT-Parameters* is used convey UE capabilities related to the other RATs. + +#### *InterRAT-Parameters* information element + +``` + +-- ASN1START +-- TAG-INTERRAT-PARAMETERS-START + +InterRAT-Parameters ::= SEQUENCE { + eutra EUTRA-Parameters OPTIONAL, + ... + [[ + utra-FDD-r16 UTRA-FDD-Parameters-r16 OPTIONAL + ]] +} + +EUTRA-Parameters ::= SEQUENCE { + supportedBandListEUTRA SEQUENCE (SIZE (1..maxBandsEUTRA)) OF FreqBandIndicatorEUTRA, + eutra-ParametersCommon EUTRA-ParametersCommon OPTIONAL, + eutra-ParametersXDD-Diff EUTRA-ParametersXDD-Diff OPTIONAL, + ... +} + +EUTRA-ParametersCommon ::= SEQUENCE { + mfbi-EUTRA ENUMERATED {supported} OPTIONAL, + modifiedMPR-BehaviorEUTRA BIT STRING (SIZE (32)) OPTIONAL, + multiNS-Pmax-EUTRA ENUMERATED {supported} OPTIONAL, + rs-SINR-MeasEUTRA ENUMERATED {supported} OPTIONAL, + ... + [[ + ne-DC ENUMERATED {supported} OPTIONAL + ]], + [[ + nr-HO-ToEN-DC-r16 ENUMERATED {supported} OPTIONAL + ]] +} + +EUTRA-ParametersXDD-Diff ::= SEQUENCE { + rsrqMeasWidebandEUTRA ENUMERATED {supported} OPTIONAL, + ... +} + +UTRA-FDD-Parameters-r16 ::= SEQUENCE { + supportedBandListUTRA-FDD-r16 SEQUENCE (SIZE (1..maxBandsUTRA-FDD-r16)) OF SupportedBandUTRA-FDD-r16, + ... +} + +SupportedBandUTRA-FDD-r16 ::= ENUMERATED { + +``` + +``` + +bandI, bandII, bandIII, bandIV, bandV, bandVI, +bandVII, bandVIII, bandIX, bandX, bandXI, +bandXII, bandXIII, bandXIV, bandXV, bandXVI, +bandXVII, bandXVIII, bandXIX, bandXX, +bandXXI, bandXXII, bandXXIII, bandXXIV, +bandXXV, bandXXVI, bandXXVII, bandXXVIII, +bandXXIX, bandXXX, bandXXXI, bandXXXII} + +-- TAG-INTERRAT-PARAMETERS-STOP +-- ASN1STOP + +``` + +#### — *MAC-Parameters* + +The IE *MAC-Parameters* is used to convey capabilities related to MAC. + +#### ***MAC-Parameters* information element** + +``` + +-- ASN1START +-- TAG-MAC-PARAMETERS-START + +MAC-Parameters ::= SEQUENCE { + mac-ParametersCommon MAC-ParametersCommon OPTIONAL, + mac-ParametersXDD-Diff MAC-ParametersXDD-Diff OPTIONAL +} + +MAC-Parameters-v1610 ::= SEQUENCE { + mac-ParametersFRX-Diff-r16 MAC-ParametersFRX-Diff-r16 OPTIONAL +} + +MAC-Parameters-v1700 ::= SEQUENCE { + mac-ParametersFR2-2-r17 MAC-ParametersFR2-2-r17 OPTIONAL +} + +MAC-ParametersCommon ::= SEQUENCE { + lcp-Restriction ENUMERATED {supported} OPTIONAL, + dummy ENUMERATED {supported} OPTIONAL, + lch-ToSCellRestriction ENUMERATED {supported} OPTIONAL, + ..., + [[ + recommendedBitRate ENUMERATED {supported} OPTIONAL, + recommendedBitRateQuery ENUMERATED {supported} OPTIONAL + ]], + [[ + recommendedBitRateMultiplier-r16 ENUMERATED {supported} OPTIONAL, + preEmptiveBSR-r16 ENUMERATED {supported} OPTIONAL, + autonomousTransmission-r16 ENUMERATED {supported} OPTIONAL, + lch-PriorityBasedPrioritization-r16 ENUMERATED {supported} OPTIONAL, + lch-ToConfiguredGrantMapping-r16 ENUMERATED {supported} OPTIONAL, + lch-ToGrantPriorityRestriction-r16 ENUMERATED {supported} OPTIONAL, + ]], +} + +``` + +``` + + singlePHR-P-r16 ENUMERATED {supported} OPTIONAL, + ul-LBT-FailureDetectionRecovery-r16 ENUMERATED {supported} OPTIONAL, + -- R4 8-1: MPE + tdd-MPE-P-MPR-Reporting-r16 ENUMERATED {supported} OPTIONAL, + lcid-ExtensionIAB-r16 ENUMERATED {supported} OPTIONAL + ]], + [[ + spCell-BFR-CBRA-r16 ENUMERATED {supported} OPTIONAL + ]], + [[ + srs-ResourceId-Ext-r16 ENUMERATED {supported} OPTIONAL + ]], + [[ + enhancedUuDRX-forSidelink-r17 ENUMERATED {supported} OPTIONAL, + --27-10: Support of UL MAC CE based MG activation request for PRS measurements + mg-ActivationRequestPRS-Meas-r17 ENUMERATED {supported} OPTIONAL, + --27-11: Support of DL MAC CE based MG activation request for PRS measurements + mg-ActivationCommPRS-Meas-r17 ENUMERATED {supported} OPTIONAL, + intraCG-Prioritization-r17 ENUMERATED {supported} OPTIONAL, + jointPrioritizationCG-Retx-Timer-r17 ENUMERATED {supported} OPTIONAL, + survivalTime-r17 ENUMERATED {supported} OPTIONAL, + lcg-ExtensionIAB-r17 ENUMERATED {supported} OPTIONAL, + harq-FeedbackDisabled-r17 ENUMERATED {supported} OPTIONAL, + uplink-Harq-ModeB-r17 ENUMERATED {supported} OPTIONAL, + sr-TriggeredBy-TA-Report-r17 ENUMERATED {supported} OPTIONAL, + extendedDRX-CycleInactive-r17 ENUMERATED {supported} OPTIONAL, + simultaneousSR-PUSCH-DiffPUCCH-groups-r17 ENUMERATED {supported} OPTIONAL, + lastTransmissionUL-r17 ENUMERATED {supported} OPTIONAL + ]], + [[ + sr-TriggeredByTA-ReportATG-r18 ENUMERATED {supported} OPTIONAL, + -- similar to R1 26-4: UE reporting of information related to TA pre-compensation defined for ATG + uplinkTA-ReportingATG-r18 ENUMERATED {supported} OPTIONAL, + extendedDRX-CycleInactive-r18 ENUMERATED {supported} OPTIONAL + ]] +} + +MAC-ParametersFRX-Diff-r16 ::= SEQUENCE { + directMCG-SCellActivation-r16 ENUMERATED {supported} OPTIONAL, + directMCG-SCellActivationResume-r16 ENUMERATED {supported} OPTIONAL, + directSCG-SCellActivation-r16 ENUMERATED {supported} OPTIONAL, + directSCG-SCellActivationResume-r16 ENUMERATED {supported} OPTIONAL, + -- R1 19-1: DRX Adaptation + drx-Adaptation-r16 SEQUENCE { + non-SharedSpectrumChAccess-r16 MinTimeGap-r16 OPTIONAL, + sharedSpectrumChAccess-r16 MinTimeGap-r16 OPTIONAL + } OPTIONAL, + ... +} + +MAC-ParametersFR2-2-r17 ::= SEQUENCE { + +``` + +``` + +directMCG-SCellActivation-r17 ENUMERATED {supported} OPTIONAL, +directMCG-SCellActivationResume-r17 ENUMERATED {supported} OPTIONAL, +directSCG-SCellActivation-r17 ENUMERATED {supported} OPTIONAL, +directSCG-SCellActivationResume-r17 ENUMERATED {supported} OPTIONAL, +drx-Adaptation-r17 SEQUENCE { + non-SharedSpectrumChAccess-r17 MinTimeGapFR2-2-r17 OPTIONAL, + sharedSpectrumChAccess-r17 MinTimeGapFR2-2-r17 OPTIONAL +} +... +} + +MAC-ParametersXDD-Diff ::= SEQUENCE { + skipUplinkTxDynamic ENUMERATED {supported} OPTIONAL, + logicalChannelSR-DelayTimer ENUMERATED {supported} OPTIONAL, + longDRX-Cycle ENUMERATED {supported} OPTIONAL, + shortDRX-Cycle ENUMERATED {supported} OPTIONAL, + multipleSR-Configurations ENUMERATED {supported} OPTIONAL, + multipleConfiguredGrants ENUMERATED {supported} OPTIONAL, + ... + [[ + secondaryDRX-Group-r16 ENUMERATED {supported} OPTIONAL + ]], + [[ + enhancedSkipUplinkTxDynamic-r16 ENUMERATED {supported} OPTIONAL, + enhancedSkipUplinkTxConfigured-r16 ENUMERATED {supported} OPTIONAL + ]], + [[ + ptm-Retransmission-r18 ENUMERATED {supported} OPTIONAL, + ptm-RetransmissionInactive-r18 ENUMERATED {supported} OPTIONAL + ]] +} + +MinTimeGap-r16 ::= SEQUENCE { + scs-15kHz-r16 ENUMERATED {sl1, sl3} OPTIONAL, + scs-30kHz-r16 ENUMERATED {sl1, sl6} OPTIONAL, + scs-60kHz-r16 ENUMERATED {sl1, sl12} OPTIONAL, + scs-120kHz-r16 ENUMERATED {sl2, sl24} OPTIONAL +} + +MinTimeGapFR2-2-r17 ::= SEQUENCE { + scs-120kHz-r17 ENUMERATED {sl2, sl24} OPTIONAL, + scs-480kHz-r17 ENUMERATED {sl8, sl96} OPTIONAL, + scs-960kHz-r17 ENUMERATED {sl16, sl192} OPTIONAL +} + +-- TAG-MAC-PARAMETERS-STOP +-- ASN1STOP + +``` + +### MeasAndMobParameters + +The IE *MeasAndMobParameters* is used to convey UE capabilities related to measurements for radio resource management (RRM), radio link monitoring (RLM) and mobility (e.g. handover). + +#### MeasAndMobParameters information element + +``` +-- ASN1START +-- TAG-MEASANDMOBPARAMETERS-START + +MeasAndMobParameters ::= + SEQUENCE { + measAndMobParametersCommon OPTIONAL, + measAndMobParametersXDD-Diff OPTIONAL, + measAndMobParametersFRX-Diff OPTIONAL + } + +MeasAndMobParameters-v1700 ::= + SEQUENCE { + measAndMobParametersFR2-2-r17 OPTIONAL + } + +MeasAndMobParametersCommon ::= + SEQUENCE { + supportedGapPattern OPTIONAL, + ssb-RLM OPTIONAL, + ssb-AndCSI-RS-RLM OPTIONAL, + ..., + [[ + eventB-MeasAndReport OPTIONAL, + handoverFDD-TDD OPTIONAL, + eutra-CGI-Reporting OPTIONAL, + nr-CGI-Reporting OPTIONAL + ]], + [[ + independentGapConfig OPTIONAL, + periodicEUTRA-MeasAndReport OPTIONAL, + handoverFR1-FR2 OPTIONAL, + maxNumberCSI-RS-RRM-RS-SINR OPTIONAL + ]], + [[ + nr-CGI-Reporting-ENDC OPTIONAL + ]], + [[ + eutra-CGI-Reporting-NEDC OPTIONAL, + eutra-CGI-Reporting-NRDC OPTIONAL, + nr-CGI-Reporting-NEDC OPTIONAL, + nr-CGI-Reporting-NRDC OPTIONAL + ]], + [[ + reportAddNeighMeasForPeriodic-r16 OPTIONAL, + condHandoverParametersCommon-r16 + SEQUENCE { + condHandoverFDD-TDD-r16 OPTIONAL, + } + ]]] +``` + +``` + + condHandoverFR1-FR2-r16 ENUMERATED {supported} OPTIONAL + } OPTIONAL, + nr-NeedForGap-Reporting-r16 ENUMERATED {supported} OPTIONAL, + supportedGapPattern-NRonly-r16 BIT STRING (SIZE (10)) OPTIONAL, + supportedGapPattern-NRonly-NEDC-r16 ENUMERATED {supported} OPTIONAL, + maxNumberCLI-RSSI-r16 ENUMERATED {n8, n16, n32, n64} OPTIONAL, + maxNumberCLI-SRS-RSRP-r16 ENUMERATED {n4, n8, n16, n32} OPTIONAL, + maxNumberPerSlotCLI-SRS-RSRP-r16 ENUMERATED {n2, n4, n8} OPTIONAL, + mfbi-IAB-r16 ENUMERATED {supported} OPTIONAL, + dummy ENUMERATED {supported} OPTIONAL, + nr-CGI-Reporting-NPN-r16 ENUMERATED {supported} OPTIONAL, + idleInactiveEUTRA-MeasReport-r16 ENUMERATED {supported} OPTIONAL, + idleInactive-ValidityArea-r16 ENUMERATED {supported} OPTIONAL, + eutra-AutonomousGaps-r16 ENUMERATED {supported} OPTIONAL, + eutra-AutonomousGaps-NEDC-r16 ENUMERATED {supported} OPTIONAL, + eutra-AutonomousGaps-NRDC-r16 ENUMERATED {supported} OPTIONAL, + pcellT312-r16 ENUMERATED {supported} OPTIONAL, + supportedGapPattern-r16 BIT STRING (SIZE (2)) OPTIONAL +], +[[ +-- R4 19-2 Concurrent measurement gaps +concurrentMeasGap-r17 CHOICE { + concurrentPerUE-OnlyMeasGap-r17 ENUMERATED {supported}, + concurrentPerUE-PerFRCombMeasGap-r17 ENUMERATED {supported} +} OPTIONAL, +-- R4 19-1 Network controlled small gap (NCSG) +nr-NeedForGapNCSG-Reporting-r17 ENUMERATED {supported} OPTIONAL, +eutra-NeedForGapNCSG-Reporting-r17 ENUMERATED {supported} OPTIONAL, +-- R4 19-1-1 per FR Network controlled small gap (NCSG) +ncsg-MeasGapPerFR-r17 ENUMERATED {supported} OPTIONAL, +-- R4 19-1-2 Network controlled small gap (NCSG) supported patterns +ncsg-MeasGapPatterns-r17 BIT STRING (SIZE(24)) OPTIONAL, +-- R4 19-1-3 Network controlled small gap (NCSG) supported NR-only patterns +ncsg-MeasGapNR-Patterns-r17 BIT STRING (SIZE(24)) OPTIONAL, +-- R4 19-3-2 pre-configured measurement gap +preconfiguredUE-AutonomousMeasGap-r17 ENUMERATED {supported} OPTIONAL, +-- R4 19-3-1 pre-configured measurement gap +preconfiguredNW-ControlledMeasGap-r17 ENUMERATED {supported} OPTIONAL, +handoverFR1-FR2-2-r17 ENUMERATED {supported} OPTIONAL, +handoverFR2-1-FR2-2-r17 ENUMERATED {supported} OPTIONAL, +-- RAN4 14-1: per-FR MG for PRS measurement +independentGapConfigPRS-r17 ENUMERATED {supported} OPTIONAL, +rrm-RelaxationRRC-ConnectedRedCap-r17 ENUMERATED {supported} OPTIONAL, +-- R4 25-3: Parallel measurements with multiple measurement gaps +parallelMeasurementGap-r17 ENUMERATED {n2} OPTIONAL, +condHandoverWithSCG-NRDC-r17 ENUMERATED {supported} OPTIONAL, +gNB-ID-LengthReporting-r17 ENUMERATED {supported} OPTIONAL, +gNB-ID-LengthReporting-ENDC-r17 ENUMERATED {supported} OPTIONAL, +gNB-ID-LengthReporting-NEDC-r17 ENUMERATED {supported} OPTIONAL, +gNB-ID-LengthReporting-NRDC-r17 ENUMERATED {supported} OPTIONAL, +gNB-ID-LengthReporting-NPN-r17 ENUMERATED {supported} OPTIONAL + +``` + +``` + +]], +[[ +-- R4 25-1: Parallel measurements on multiple SMTC-s for a single frequency carrier +parallelSMTC-r17 ENUMERATED {n4} OPTIONAL, +-- R4 19-2-1 Concurrent measurement gaps for EUTRA +concurrentMeasGapEUTRA-r17 ENUMERATED {supported} OPTIONAL, +serviceLinkPropDelayDiffReporting-r17 ENUMERATED {supported} OPTIONAL, +-- R4 19-1-4 Network controlled small gap (NCSG) performing measurement based on flag deriveSSB-IndexFromCellInter +ncsg-SymbolLevelScheduleRestrictionInter-r17 ENUMERATED {supported} OPTIONAL +]], +[[ +eventDl-MeasReportTrigger-r17 ENUMERATED {supported} OPTIONAL, +independentGapConfig-maxCC-r17 SEQUENCE { + fr1-Only-r17 INTEGER (1..32) OPTIONAL, + fr2-Only-r17 INTEGER (1..32) OPTIONAL, + fr1-AndFR2-r17 INTEGER (1..32) OPTIONAL, +} OPTIONAL +]], +[[ +interSatMeas-r17 ENUMERATED {supported} OPTIONAL, +deriveSSB-IndexFromCellInterNon-NCSG-r17 ENUMERATED {supported} OPTIONAL +]], +[[ +-- R4 31-1 Enhanced L3 measurement reporting for unknown SCell activation if the valid L3 measurement results are available +l3-MeasUnknownSCellActivation-r18 ENUMERATED {supported} OPTIONAL, +-- R4 31-3 Shorter measurement interval for unknown SCell activation +shortMeasInterval-r18 ENUMERATED {supported} OPTIONAL, +nr-NeedForInterruptionReport-r18 ENUMERATED {supported} OPTIONAL, +measSequenceConfig-r18 ENUMERATED {supported} OPTIONAL, +cellIndividualOffsetPerMeasEvent-r18 ENUMERATED {supported} OPTIONAL +]] +} + +MeasAndMobParametersXDD-Diff ::= SEQUENCE { + intraAndInterF-MeasAndReport ENUMERATED {supported} OPTIONAL, + eventA-MeasAndReport ENUMERATED {supported} OPTIONAL, + ..., + [[ + handoverInterF ENUMERATED {supported} OPTIONAL, + handoverLTE-EPC ENUMERATED {supported} OPTIONAL, + handoverLTE-5GC ENUMERATED {supported} OPTIONAL + ]], + [[ + sftd-MeasNR-Neigh ENUMERATED {supported} OPTIONAL, + sftd-MeasNR-Neigh-DRX ENUMERATED {supported} OPTIONAL + ]], + [[ + dummy ENUMERATED {supported} OPTIONAL + ]] +} + +``` + +``` + +MeasAndMobParametersFRX-Diff ::= SEQUENCE { + ss-SINR-Meas ENUMERATED {supported} OPTIONAL, + csi-RSRP-AndRSRQ-MeasWithSSB ENUMERATED {supported} OPTIONAL, + csi-RSRP-AndRSRQ-MeasWithoutSSB ENUMERATED {supported} OPTIONAL, + csi-SINR-Meas ENUMERATED {supported} OPTIONAL, + csi-RS-RLM ENUMERATED {supported} OPTIONAL, + ..., + [[ + handoverInterF ENUMERATED {supported} OPTIONAL, + handoverLTE-EPC ENUMERATED {supported} OPTIONAL, + handoverLTE-5GC ENUMERATED {supported} OPTIONAL + ]], + [[ + maxNumberResource-CSI-RS-RLM ENUMERATED {n2, n4, n6, n8} OPTIONAL + ]], + [[ + simultaneousRxDataSSB-DiffNumerology ENUMERATED {supported} OPTIONAL + ]], + [[ + nr-AutonomousGaps-r16 ENUMERATED {supported} OPTIONAL, + nr-AutonomousGaps-ENDC-r16 ENUMERATED {supported} OPTIONAL, + nr-AutonomousGaps-NEDC-r16 ENUMERATED {supported} OPTIONAL, + nr-AutonomousGaps-NRDC-r16 ENUMERATED {supported} OPTIONAL, + dummy ENUMERATED {supported} OPTIONAL, + cli-RSSI-Meas-r16 ENUMERATED {supported} OPTIONAL, + cli-SRS-RSRP-Meas-r16 ENUMERATED {supported} OPTIONAL, + interFrequencyMeas-NoGap-r16 ENUMERATED {supported} OPTIONAL, + simultaneousRxDataSSB-DiffNumerology-Inter-r16 ENUMERATED {supported} OPTIONAL, + idleInactiveNR-MeasReport-r16 ENUMERATED {supported} OPTIONAL, + -- R4 6-2: Support of beam level Early Measurement Reporting + idleInactiveNR-MeasBeamReport-r16 ENUMERATED {supported} OPTIONAL + ]], + [[ + increasedNumberOfCSIRSPerMO-r16 ENUMERATED {supported} OPTIONAL + ]] +} + +MeasAndMobParametersFR2-2-r17 ::= SEQUENCE { + handoverInterF-r17 ENUMERATED {supported} OPTIONAL, + handoverLTE-EPC-r17 ENUMERATED {supported} OPTIONAL, + handoverLTE-5GC-r17 ENUMERATED {supported} OPTIONAL, + idleInactiveNR-MeasReport-r17 ENUMERATED {supported} OPTIONAL, + ... +} + +-- TAG-MEASANDMOB PARAMETERS-STOP +-- ASN1STOP + +``` + +#### MeasAndMobParametersMRDC + +The IE *MeasAndMobParametersMRDC* is used to convey capability parameters related to RRM measurements and RRC mobility. + +#### MeasAndMobParametersMRDC information element + +``` +-- ASN1START +-- TAG-MEASANDMOBPARAMETERSMRDC-START + +MeasAndMobParametersMRDC ::= SEQUENCE { + measAndMobParametersMRDC-Common MeasAndMobParametersMRDC-Common OPTIONAL, + measAndMobParametersMRDC-XDD-Diff MeasAndMobParametersMRDC-XDD-Diff OPTIONAL, + measAndMobParametersMRDC-FRX-Diff MeasAndMobParametersMRDC-FRX-Diff OPTIONAL +} + +MeasAndMobParametersMRDC-v1560 ::= SEQUENCE { + measAndMobParametersMRDC-XDD-Diff-v1560 MeasAndMobParametersMRDC-XDD-Diff-v1560 OPTIONAL +} + +MeasAndMobParametersMRDC-v1610 ::= SEQUENCE { + measAndMobParametersMRDC-Common-v1610 MeasAndMobParametersMRDC-Common-v1610 OPTIONAL, + interNR-MeasEUTRA-IAB-r16 ENUMERATED {supported} OPTIONAL +} + +MeasAndMobParametersMRDC-v1700 ::= SEQUENCE { + measAndMobParametersMRDC-Common-v1700 MeasAndMobParametersMRDC-Common-v1700 OPTIONAL +} + +MeasAndMobParametersMRDC-v1730 ::= SEQUENCE { + measAndMobParametersMRDC-Common-v1730 MeasAndMobParametersMRDC-Common-v1730 OPTIONAL +} + +MeasAndMobParametersMRDC-Common ::= SEQUENCE { + independentGapConfig ENUMERATED {supported} OPTIONAL +} + +MeasAndMobParametersMRDC-Common-v1610 ::= SEQUENCE { + condPSCellChangeParametersCommon-r16 SEQUENCE { + condPSCellChangeFDD-TDD-r16 ENUMERATED {supported} OPTIONAL, + condPSCellChangeFR1-FR2-r16 ENUMERATED {supported} OPTIONAL, + } OPTIONAL, + pscellT312-r16 ENUMERATED {supported} OPTIONAL +} + +MeasAndMobParametersMRDC-Common-v1700 ::= SEQUENCE { + condPSCellChangeParameters-r17 SEQUENCE { + inter-SN-condPSCellChangeFDD-TDD-NRDC-r17 ENUMERATED {supported} OPTIONAL, + inter-SN-condPSCellChangeFR1-FR2-NRDC-r17 ENUMERATED {supported} OPTIONAL, + inter-SN-condPSCellChangeFDD-TDD-ENDC-r17 ENUMERATED {supported} OPTIONAL, + inter-SN-condPSCellChangeFR1-FR2-ENDC-r17 ENUMERATED {supported} OPTIONAL, + } +} +``` + +``` + + mn-InitiatedCondPSCellChange-FR1FDD-ENDC-r17 ENUMERATED {supported} OPTIONAL, + mn-InitiatedCondPSCellChange-FR1TDD-ENDC-r17 ENUMERATED {supported} OPTIONAL, + mn-InitiatedCondPSCellChange-FR2TDD-ENDC-r17 ENUMERATED {supported} OPTIONAL, + sn-InitiatedCondPSCellChange-FR1FDD-ENDC-r17 ENUMERATED {supported} OPTIONAL, + sn-InitiatedCondPSCellChange-FR1TDD-ENDC-r17 ENUMERATED {supported} OPTIONAL, + sn-InitiatedCondPSCellChange-FR2TDD-ENDC-r17 ENUMERATED {supported} OPTIONAL + } + condHandoverWithSCG-ENDC-r17 ENUMERATED {supported} OPTIONAL, + condHandoverWithSCG-NEDC-r17 ENUMERATED {supported} OPTIONAL +} + +MeasAndMobParametersMRDC-Common-v1730 ::= SEQUENCE { + independentGapConfig-maxCC-r17 SEQUENCE { + fr1-Only-r17 INTEGER (1..32) OPTIONAL, + fr2-Only-r17 INTEGER (1..32) OPTIONAL, + fr1-AndFR2-r17 INTEGER (1..32) OPTIONAL + } +} + +MeasAndMobParametersMRDC-XDD-Diff ::= SEQUENCE { + sftd-MeasPSCell ENUMERATED {supported} OPTIONAL, + sftd-MeasNR-Cell ENUMERATED {supported} OPTIONAL +} + +MeasAndMobParametersMRDC-XDD-Diff-v1560 ::= SEQUENCE { + sftd-MeasPSCell-NEDC ENUMERATED {supported} OPTIONAL +} + +MeasAndMobParametersMRDC-FRX-Diff ::= SEQUENCE { + simultaneousRxDataSSB-DiffNumerology ENUMERATED {supported} OPTIONAL +} + +-- TAG-MEASANDMOBPARAMETERSMRDC-STOP +-- ASN1STOP + +``` + +#### — *MIMO-Layers* + +The IE *MIMO-Layers* is used to convey the number of supported MIMO layers. + +#### ***MIMO-Layers* information element** + +``` + +-- ASN1START +-- TAG-MIMO-LAYERS-START + +MIMO-LayersDL ::= ENUMERATED {twoLayers, fourLayers, eightLayers} + +MIMO-LayersUL ::= ENUMERATED {oneLayer, twoLayers, fourLayers} + +-- TAG-MIMO-LAYERS-STOP + +``` + +-- ASN1STOP + +#### MIMO-ParametersPerBand + +The IE *MIMO-ParametersPerBand* is used to convey MIMO related parameters specific for a certain band (not per feature set or band combination). + +#### MIMO-ParametersPerBand information element + +``` +-- ASN1START +-- TAG-MIMO-PARAMETERSPERBAND-START + +MIMO-ParametersPerBand ::= SEQUENCE { + tci-StatePDSCHEncoded SEQUENCE { + maxNumberConfiguredTCI-StatesPerCC ENUMERATED {n4, n8, n16, n32, n64, n128} OPTIONAL, + maxNumberActiveTCI-PerBWP ENUMERATED {n1, n2, n4, n8} OPTIONAL + } OPTIONAL, + additionalActiveTCI-StatePDCCH ENUMERATED {supported} OPTIONAL, + pusch-TransCoherence ENUMERATED {nonCoherent, partialCoherent, fullCoherent} OPTIONAL, + beamCorrespondenceWithoutUL-BeamSweeping ENUMERATED {supported} OPTIONAL, + periodicBeamReport ENUMERATED {supported} OPTIONAL, + aperiodicBeamReport ENUMERATED {supported} OPTIONAL, + sp-BeamReportPUCCH ENUMERATED {supported} OPTIONAL, + sp-BeamReportPUSCH ENUMERATED {supported} OPTIONAL, + dummy1 DummyG OPTIONAL, + maxNumberRxBBeam INTEGER (2..8) OPTIONAL, + maxNumberRxBBeamSwitchDL SEQUENCE { + scs-15kHz ENUMERATED {n4, n7, n14} OPTIONAL, + scs-30kHz ENUMERATED {n4, n7, n14} OPTIONAL, + scs-60kHz ENUMERATED {n4, n7, n14} OPTIONAL, + scs-120kHz ENUMERATED {n4, n7, n14} OPTIONAL, + scs-240kHz ENUMERATED {n4, n7, n14} OPTIONAL + } OPTIONAL, + maxNumberNonGroupBeamReporting ENUMERATED {n1, n2, n4} OPTIONAL, + groupBeamReporting ENUMERATED {supported} OPTIONAL, + uplinkBeamManagement SEQUENCE { + maxNumberSRS-ResourcePerSet-BM ENUMERATED {n2, n4, n8, n16}, + maxNumberSRS-ResourceSet INTEGER (1..8) + } OPTIONAL, + maxNumberCSI-RS-BFD INTEGER (1..64) OPTIONAL, + maxNumberSSB-BFD INTEGER (1..64) OPTIONAL, + maxNumberCSI-RS-SSB-CBD INTEGER (1..256) OPTIONAL, + dummy2 ENUMERATED {supported} OPTIONAL, + twoPortsPTRS-UL ENUMERATED {supported} OPTIONAL, + dummy5 SRS-Resources OPTIONAL, + dummy3 INTEGER (1..4) OPTIONAL, + beamReportTiming SEQUENCE { + scs-15kHz ENUMERATED {sym2, sym4, sym8} OPTIONAL, + scs-30kHz ENUMERATED {sym4, sym8, sym14, sym28} OPTIONAL, + scs-60kHz ENUMERATED {sym8, sym14, sym28} OPTIONAL + } +} +``` + +``` + + scs-120kHz ENUMERATED {sym14, sym28, sym56} OPTIONAL + } + ptrs-DensityRecommendationSetDL SEQUENCE { + scs-15kHz PTRS-DensityRecommendationDL OPTIONAL, + scs-30kHz PTRS-DensityRecommendationDL OPTIONAL, + scs-60kHz PTRS-DensityRecommendationDL OPTIONAL, + scs-120kHz PTRS-DensityRecommendationDL OPTIONAL + } + ptrs-DensityRecommendationSetUL SEQUENCE { + scs-15kHz PTRS-DensityRecommendationUL OPTIONAL, + scs-30kHz PTRS-DensityRecommendationUL OPTIONAL, + scs-60kHz PTRS-DensityRecommendationUL OPTIONAL, + scs-120kHz PTRS-DensityRecommendationUL OPTIONAL + } + dummy4 DummyH OPTIONAL, + aperiodicTRS ENUMERATED {supported} OPTIONAL, + ..., + [[ + dummy6 ENUMERATED {true} OPTIONAL, + beamManagementSSB-CSI-RS BeamManagementSSB-CSI-RS OPTIONAL, + beamSwitchTiming SEQUENCE { + scs-60kHz ENUMERATED {sym14, sym28, sym48, sym224, sym336} OPTIONAL, + scs-120kHz ENUMERATED {sym14, sym28, sym48, sym224, sym336} OPTIONAL + } + codebookParameters CodebookParameters OPTIONAL, + csi-RS-IM-ReceptionForFeedback CSI-RS-IM-ReceptionForFeedback OPTIONAL, + csi-RS-ProcFrameworkForSRS CSI-RS-ProcFrameworkForSRS OPTIONAL, + csi-ReportFramework CSI-ReportFramework OPTIONAL, + csi-RS-ForTracking CSI-RS-ForTracking OPTIONAL, + srs-AssocCSI-RS SEQUENCE (SIZE (1.. maxNrofCSI-RS-Resources)) OF SupportedCSI-RS-Resource OPTIONAL, + spatialRelations SpatialRelations OPTIONAL + ]], + [[ + -- R1 16-2b-0: Support of default QCL assumption with two TCI states + defaultQCL-TwoTCI-r16 ENUMERATED {supported} OPTIONAL, + codebookParametersPerBand-r16 CodebookParameters-v1610 OPTIONAL, + -- R1 16-1b-3: Support of PUCCH resource groups per BWP for simultaneous spatial relation update + simul-SpatialRelationUpdatePUCCHResGroup-r16 ENUMERATED {supported} OPTIONAL, + + -- R1 16-1f: Maximum number of SCells configured for SCell beam failure recovery simultaneously + maxNumberSCellBFR-r16 ENUMERATED {n1,n2,n4,n8} OPTIONAL, + + -- R1 16-2c: Supports simultaneous reception with different Type-D for FR2 only + simultaneousReceptionDiffTypeD-r16 ENUMERATED {supported} OPTIONAL, + -- R1 16-1a-1: SSB/CSI-RS for L1-SINR measurement + ssb-csirs-SINR-measurement-r16 SEQUENCE { + maxNumberSSB-CSIRS-OneTx-CMR-r16 ENUMERATED {n8, n16, n32, n64}, + maxNumberCSI-IM-NZP-IMR-res-r16 ENUMERATED {n8, n16, n32, n64}, + maxNumberCSIRS-2Tx-res-r16 ENUMERATED {n0, n4, n8, n16, n32, n64}, + maxNumberSSB-CSIRS-res-r16 ENUMERATED {n8, n16, n32, n64, n128}, + maxNumberCSI-IM-NZP-IMR-res-mem-r16 ENUMERATED {n8, n16, n32, n64, n128}, + } + ]], + +``` + +``` + +supportedCSI-RS-Density-CMR-r16 ENUMERATED {one, three, oneAndThree}, +maxNumberAperiodicCSI-RS-Res-r16 ENUMERATED {n2, n4, n8, n16, n32, n64}, +supportedSINR-meas-r16 ENUMERATED {ssbWithCSI-IM, ssbWithNZP-IMR, csirsWithNZP-IMR, csi-RSWithoutIMR} OPTIONAL +} OPTIONAL, +-- R1 16-1a-2: Non-group based L1-SINR reporting +nonGroupSINR-reporting-r16 ENUMERATED {n1, n2, n4} OPTIONAL, +-- R1 16-1a-3: Non-group based L1-SINR reporting +groupSINR-reporting-r16 ENUMERATED {supported} OPTIONAL, +multiDCI-multiTRP-Parameters-r16 SEQUENCE { + -- R1 16-2a-0: Overlapping PDSCHs in time and fully overlapping in frequency and time + overlapPDSCHsFullyFreqTime-r16 INTEGER (1..2) OPTIONAL, + -- R1 16-2a-1: Overlapping PDSCHs in time and partially overlapping in frequency and time + overlapPDSCHsInTimePartiallyFreq-r16 ENUMERATED {supported} OPTIONAL, + -- R1 16-2a-2: Out of order operation for DL + outOfOrderOperationDL-r16 SEQUENCE { + supportPDCCH-ToPDSCH-r16 ENUMERATED {supported} OPTIONAL, + supportPDSCH-ToHARQ-ACK-r16 ENUMERATED {supported} OPTIONAL, + } OPTIONAL, + -- R1 16-2a-3: Out of order operation for UL + outOfOrderOperationUL-r16 ENUMERATED {supported} OPTIONAL, + -- R1 16-2a-5: Separate CRS rate matching + separateCRS-RateMatching-r16 ENUMERATED {supported} OPTIONAL, + -- R1 16-2a-6: Default QCL enhancement for multi-DCI based multi-TRP + defaultQCL-PerCORESETPoolIndex-r16 ENUMERATED {supported} OPTIONAL, + -- R1 16-2a-7: Maximum number of activated TCI states + maxNumberActivatedTCI-States-r16 SEQUENCE { + maxNumberPerCORESET-Pool-r16 ENUMERATED {n1, n2, n4, n8}, + maxTotalNumberAcrossCORESET-Pool-r16 ENUMERATED {n2, n4, n8, n16} + } OPTIONAL, +} OPTIONAL, +singleDCI-SDM-scheme-Parameters-r16 SEQUENCE { + -- R1 16-2b-1b: Single-DCI based SDM scheme - Support of new DMRS port entry + supportNewDMRS-Port-r16 ENUMERATED {supported1, supported2, supported3} OPTIONAL, + -- R1 16-2b-1a: Support of s-port DL PTRS + supportTwoPortDL-PTRS-r16 ENUMERATED {supported} OPTIONAL, +} OPTIONAL, +-- R1 16-2b-2: Support of single-DCI based FDMSchemeA +supportFDM-SchemeA-r16 ENUMERATED {supported} OPTIONAL, +-- R1 16-2b-3a: Single-DCI based FDMSchemeB CW soft combining +supportCodeWordSoftCombining-r16 ENUMERATED {supported} OPTIONAL, +-- R1 16-2b-4: Single-DCI based TDMSchemeA +supportTDM-SchemeA-r16 ENUMERATED {kb3, kb5, kb10, kb20, noRestriction} OPTIONAL, +-- R1 16-2b-5: Single-DCI based inter-slot TDM +supportInter-slotTDM-r16 SEQUENCE { + supportRepNumPDSCH-TDRA-r16 ENUMERATED {n2, n3, n4, n5, n6, n7, n8, n16}, + maxTBS-Size-r16 ENUMERATED {kb3, kb5, kb10, kb20, noRestriction}, + maxNumberTCI-states-r16 INTEGER (1..2) +} OPTIONAL, +-- R1 16-4: Low PAPR DMRS for PDSCH +lowPAPR-DMRS-PDSCH-r16 ENUMERATED {supported} OPTIONAL, + +``` + +``` + +-- R1 16-6a: Low PAPR DMRS for PUSCH without transform precoding +lowPAPR-DMRS-PUSCHwithoutPrecoding-r16 ENUMERATED {supported} OPTIONAL, +-- R1 16-6b: Low PAPR DMRS for PUCCH +lowPAPR-DMRS-PUCCH-r16 ENUMERATED {supported} OPTIONAL, +-- R1 16-6c: Low PAPR DMRS for PUSCH with transform precoding & pi/2 BPSK +lowPAPR-DMRS-PUSCHwithPrecoding-r16 ENUMERATED {supported} OPTIONAL, +-- R1 16-7: Extension of the maximum number of configured aperiodic CSI report settings +csi-ReportFrameworkExt-r16 CSI-ReportFrameworkExt-r16 OPTIONAL, +-- R1 16-3a, 16-3a-1, 16-3b, 16-3b-1, 16-8: Individual new codebook types +codebookParametersAddition-r16 CodebookParametersAddition-r16 OPTIONAL, +-- R1 16-8: Mixed codebook types +codebookComboParametersAddition-r16 CodebookComboParametersAddition-r16 OPTIONAL, +-- R4 8-2: SSB based beam correspondence +beamCorrespondenceSSB-based-r16 ENUMERATED {supported} OPTIONAL, +-- R4 8-3: CSI-RS based beam correspondence +beamCorrespondenceCSI-RS-based-r16 ENUMERATED {supported} OPTIONAL, +beamSwitchTiming-r16 SEQUENCE { + scs-60kHz-r16 ENUMERATED {sym224, sym336} OPTIONAL, + scs-120kHz-r16 ENUMERATED {sym224, sym336} OPTIONAL +} OPTIONAL +],, +[[ +-- R1 16-1a-4: Semi-persistent L1-SINR report on PUCCH +semi-PersistentL1-SINR-Report-PUCCH-r16 SEQUENCE { + supportReportFormat1-2OFDM-syms-r16 ENUMERATED {supported} OPTIONAL, + supportReportFormat4-14OFDM-syms-r16 ENUMERATED {supported} OPTIONAL +} OPTIONAL, +-- R1 16-1a-5: Semi-persistent L1-SINR report on PUSCH +semi-PersistentL1-SINR-Report-PUSCH-r16 ENUMERATED {supported} OPTIONAL +],, +[[ +-- R1 16-1h: Support of 64 configured PUCCH spatial relations +spatialRelations-v1640 SEQUENCE { + maxNumberConfiguredSpatialRelations-v1640 ENUMERATED {n96, n128, n160, n192, n224, n256, n288, n320} +} OPTIONAL, +-- R1 16-1i: Support of 64 configured candidate beam RSs for BFR +support64CandidateBeamRS-BFR-r16 ENUMERATED {supported} OPTIONAL +],, +[[ +-- R1 16-2a-9: Interpretation of maxNumberMIMO-LayersPDSCH for multi-DCI based mTRP +maxMIMO-LayersForMulti-DCI-mTRP-r16 ENUMERATED {supported} OPTIONAL +],, +[[ +supportedSINR-meas-v1670 BIT STRING (SIZE (4)) OPTIONAL +],, +[[ +-- R1 23-8-5 Increased repetition for SRS +srs-increasedRepetition-r17 ENUMERATED {supported} OPTIONAL, +-- R1 23-8-6 Partial frequency sounding of SRS +srs-partialFrequencySounding-r17 ENUMERATED {supported} OPTIONAL, +-- R1 23-8-7 Start RB location hopping for partial frequency SRS + +``` + +``` + +srs-startRB-locationHoppingPartial-r17 ENUMERATED {supported} OPTIONAL, +-- R1 23-8-8 Comb-8 SRS +srs-combEight-r17 ENUMERATED {supported} OPTIONAL, +-- R1 23-9-1 Basic Features of Further Enhanced Port-Selection Type II Codebook (FeType-II) per band information +codebookParametersfetype2-r17 CodebookParametersfetype2-r17 OPTIONAL, +-- R1 23-3-1-2a Two associated CSI-RS resources +mTRP-PUSCH-twoCSI-RS-r17 ENUMERATED {supported} OPTIONAL, +-- R1 23-3-2 Multi-TRP PUCCH repetition scheme 1 (inter-slot) +mTRP-PUCCH-InterSlot-r17 ENUMERATED {pf0-2, pf1-3-4, pf0-4} OPTIONAL, +-- R1 23-3-2b Cyclic mapping for multi-TRP PUCCH repetition +mTRP-PUCCH-CyclicMapping-r17 ENUMERATED {supported} OPTIONAL, +-- R1 23-3-2c Second TPC field for multi-TRP PUCCH repetition +mTRP-PUCCH-SecondTPC-r17 ENUMERATED {supported} OPTIONAL, +-- R1 23-5-2 MTRP BFR based on two BFD-RS set +mTRP-BFR-twoBFD-RS-Set-r17 SEQUENCE { + maxBFD-RS-resourcesPerSetPerBWP-r17 ENUMERATED {n1, n2}, + maxBFR-r17 INTEGER (1..9), + maxBFD-RS-resourcesAcrossSetsPerBWP-r17 ENUMERATED {n2, n3, n4} +} OPTIONAL, +-- R1 23-5-2a PUCCH-SR resources for MTRP BFRQ - Max number of PUCCH-SR resources for MTRP BFRQ per cell group +mTRP-BFR-PUCCH-SR-perCG-r17 ENUMERATED{n1, n2} OPTIONAL, +-- R1 23-5-2b Association between a BFD-RS resource set on SpCell and a PUCCH SR resource +mTRP-BFR-association-PUCCH-SR-r17 ENUMERATED {supported} OPTIONAL, +-- R1 23-6-3 Simultaneous activation of two TCI states for PDCCH across multiple CCs (HST/URLLC) +sfn-SimulTwoTCI-AcrossMultiCC-r17 ENUMERATED {supported} OPTIONAL, +-- R1 23-6-4 Default DL beam setup for SFN +sfn-DefaultDL-BeamSetup-r17 ENUMERATED {supported} OPTIONAL, +-- R1 23-6-4a Default UL beam setup for SFN PDCCH(FR2 only) +sfn-DefaultUL-BeamSetup-r17 ENUMERATED {supported} OPTIONAL, +-- R1 23-8-1 SRS triggering offset enhancement +srs-TriggeringOffset-r17 ENUMERATED {n1, n2, n4} OPTIONAL, +-- R1 23-8-2 Triggering SRS only in DCI 0_1/0_2 +srs-TriggeringDCI-r17 ENUMERATED {supported} OPTIONAL, +-- R1 23-9-5 Active CSI-RS resources and ports for mixed codebook types in any slot per band information +codebookComboParameterMixedType-r17 CodebookComboParameterMixedType-r17 OPTIONAL, +-- R1 23-1-1 Unified TCI [with joint DL/UL TCI update] for intra-cell beam management +unifiedJointTCI-r17 SEQUENCE{ + maxConfiguredJointTCI-r17 ENUMERATED {n8, n12, n16, n24, n32, n48, n64, n128}, + maxActivatedTCIAcrossCC-r17 ENUMERATED {n1, n2, n4, n8, n16} +} OPTIONAL, +-- R1 23-1-1b Unified TCI with joint DL/UL TCI update for intra- and inter-cell beam management with more than one MAC-CE +unifiedJointTCI-multiMAC-CE-r17 SEQUENCE{ + minBeamApplicationTime-r17 ENUMERATED {n1, n2, n4, n7, n14, n28, n42, n56, n70, n84, n98, n112, n224, n336} +} OPTIONAL, +maxNumMAC-CE-PerCC ENUMERATED {n2, n3, n4, n5, n6, n7, n8} +} OPTIONAL, +-- R1 23-1-1d Per BWP TCI state pool configuration for CA mode +unifiedJointTCI-perBWP-CA-r17 ENUMERATED {supported} OPTIONAL, +-- R1 23-1-1e TCI state pool configuration with TCI pool sharing for CA mode +unifiedJointTCI-ListSharingCA-r17 ENUMERATED {n1,n2,n4,n8} OPTIONAL, +-- R1 23-1-1f Common multi-CC TCI state ID update and activation + +``` + +``` + +unifiedJointTCI-commonMultiCC-r17 ENUMERATED {supported} OPTIONAL, +-- R1 23-1-1g Beam misalignment between the DL source RS in the TCI state +unifiedJointTCI-BeamAlignDLRS-r17 ENUMERATED {supported} OPTIONAL, +-- R1 23-1-1h Association between TCI state and UL PC settings for PUCCH, PUSCH, and SRS +unifiedJointTCI-PC-association-r17 ENUMERATED {supported} OPTIONAL, +-- R1 23-1-1i Indication/configuration of R17 TCI states for aperiodic CSI-RS, PDCCH, PDSCH +unifiedJointTCI-Legacy-r17 ENUMERATED {supported} OPTIONAL, +-- 23-1-1m Indication/configuration of R17 TCI states for SRS +unifiedJointTCI-Legacy-SRS-r17 ENUMERATED {supported} OPTIONAL, +-- R1 23-1-1j Indication/configuration of R17 TCI states for CORESET #0 +unifiedJointTCI-Legacy-CORESET0-r17 ENUMERATED {supported} OPTIONAL, +-- R1 23-1-1c SCell BFR with unified TCI framework (NOTE; pre-requisite is empty) +unifiedJointTCI-SCellBFR-r17 ENUMERATED {supported} OPTIONAL, +-- R1 23-1-1a Unified TCI with joint DL/UL TCI update for inter-cell beam management +unifiedJointTCI-InterCell-r17 SEQUENCE{ + additionalMAC-CE-PerCC-r17 ENUMERATED {n0, n1, n2, n4}, + additionalMAC-CE-AcrossCC-r17 ENUMERATED {n0, n1, n2, n4} +} OPTIONAL, +-- R1 23-10-1 Unified TCI with separate DL/UL TCI update for intra-cell beam management +unifiedSeparateTCI-r17 SEQUENCE{ + maxConfiguredDL-TCI-r17 ENUMERATED {n4, n8, n12, n16, n24, n32, n48, n64, n128}, + maxConfiguredUL-TCI-r17 ENUMERATED {n4, n8, n12, n16, n24, n32, n48, n64}, + maxActivatedDL-TCIAcrossCC-r17 ENUMERATED {n1, n2, n4, n8, n16}, + maxActivatedUL-TCIAcrossCC-r17 ENUMERATED {n1, n2, n4, n8, n16} +} OPTIONAL, +-- R1 23-10-1b Unified TCI with separate DL/UL TCI update for intra-cell beam management with more than one MAC-CE +unifiedSeparateTCI-multiMAC-CE-r17 SEQUENCE{ + minBeamApplicationTime-r17 ENUMERATED {n1, n2, n4, n7, n14, n28, n42, n56, n70, n84, n98, n112, n224, n336}, + maxActivatedDL-TCIPerCC-r17 INTEGER (2..8), + maxActivatedUL-TCIPerCC-r17 INTEGER (2..8) +} OPTIONAL, +-- R1 23-10-1d Per BWP DL/UL-TCI state pool configuration for CA mode +unifiedSeparateTCI-perBWP-CA-r17 ENUMERATED {supported} OPTIONAL, +-- R1 23-10-1e TCI state pool configuration with DL/UL-TCI pool sharing for CA mode +unifiedSeparateTCI-ListSharingCA-r17 SEQUENCE { + maxNumListDL-TCI-r17 ENUMERATED {n1,n2,n4,n8} OPTIONAL, + maxNumListUL-TCI-r17 ENUMERATED {n1,n2,n4,n8} OPTIONAL +} OPTIONAL, +-- R1 23-10-1f Common multi-CC DL/UL-TCI state ID update and activation with separate DL/UL TCI update +unifiedSeparateTCI-commonMultiCC-r17 ENUMERATED {supported} OPTIONAL, +-- 23-10-1m Unified TCI with separate DL/UL TCI update for inter-cell beam management with more than one MAC-CE +unifiedSeparateTCI-InterCell-r17 SEQUENCE { + k-DL-PerCC-r17 ENUMERATED {n0, n1, n2, n4}, + k-UL-PerCC-r17 ENUMERATED {n0, n1, n2, n4}, + k-DL-AcrossCC-r17 ENUMERATED {n0, n1, n2, n4}, + k-UL-AcrossCC-r17 ENUMERATED {n0, n1, n2, n4} +} OPTIONAL, +-- R1 23-1-2 Inter-cell beam measurement and reporting (for inter-cell BM and mTRP) +unifiedJointTCI-mTRP-InterCell-BM-r17 SEQUENCE { + maxNumAdditionalPCI-L1-RSRP-r17 INTEGER (1..7), + maxNumSSB-ResourceL1-RSRP-AcrossCC-r17 ENUMERATED {n1,n2,n4,n8} +} + +``` + +``` + + } OPTIONAL, + -- R1 23-1-3 MPE mitigation + mpe-Mitigation-r17 SEQUENCE { + maxNumP-MPR-RI-pairs-r17 INTEGER (1..4), + maxNumConfRS-r17 ENUMERATED {n1, n2, n4, n8, n12, n16, n28, n32, n48, n64} + } OPTIONAL, + -- R1 23-1-4 UE capability value reporting + srs-PortReport-r17 SEQUENCE { + capVal1-r17 ENUMERATED {n1, n2, n4} OPTIONAL, + capVal2-r17 ENUMERATED {n1, n2, n4} OPTIONAL, + capVal3-r17 ENUMERATED {n1, n2, n4} OPTIONAL, + capVal4-r17 ENUMERATED {n1, n2, n4} OPTIONAL + } OPTIONAL, + -- R1 23-2-1a Monitoring of individual candidates + mTRP-PDCCH-individual-r17 ENUMERATED {supported} OPTIONAL, + -- R1 23-2-1b PDCCH repetition with PDCCH monitoring on any span of up to 3 consecutive OFDM symbols of a slot + mTRP-PDCCH-anySpan-3Symbols-r17 ENUMERATED {supported} OPTIONAL, + -- R1 23-2-2 Two QCL TypeD for CORESET monitoring in PDCCH repetition + mTRP-PDCCH-TwoQCL-TypeD-r17 ENUMERATED {supported} OPTIONAL, + -- R1 23-3-1-2b CSI-RS processing framework for SRS with two associated CSI-RS resources + mTRP-PUSCH-CSI-RS-r17 SEQUENCE { + maxNumPeriodicSRS-r17 INTEGER (1..8), + maxNumAperiodicSRS-r17 INTEGER (1..8), + maxNumSP-SRS-r17 INTEGER (0..8), + numSRS-ResourcePerCC-r17 INTEGER (1..16), + numSRS-ResourceNonCodebook-r17 INTEGER (1..2) + } OPTIONAL, + -- R1 23-3-1a Cyclic mapping for Multi-TRP PUSCH repetition + mTRP-PUSCH-cyclicMapping-r17 ENUMERATED {typeA,typeB,both} OPTIONAL, + -- R1 23-3-1b Second TPC field for Multi-TRP PUSCH repetition + mTRP-PUSCH-secondTPC-r17 ENUMERATED {supported} OPTIONAL, + -- R1 23-3-1c Two PHR reporting + mTRP-PUSCH-twoPHR-Reporting-r17 ENUMERATED {supported} OPTIONAL, + -- R1 23-3-1e A-CSI report + mTRP-PUSCH-A-CSI-r17 ENUMERATED {supported} OPTIONAL, + -- R1 23-3-1f SP-CSI report + mTRP-PUSCH-SP-CSI-r17 ENUMERATED {supported} OPTIONAL, + -- R1 23-3-1g CG PUSCH transmission + mTRP-PUSCH-CG-r17 ENUMERATED {supported} OPTIONAL, + -- R1 23-3-2d Updating two Spatial relation or two sets of power control parameters for PUCCH group + mTRP-PUCCH-MAC-CE-r17 ENUMERATED {supported} OPTIONAL, + -- R1 23-3-2e Maximum number of power control parameter sets configured for multi-TRP PUCCH repetition in FR1 + mTRP-PUCCH-maxNum-PC-FR1-r17 INTEGER (3..8) OPTIONAL, + -- R1 23-4 IntCell-mTRP + mTRP-inter-Cell-r17 SEQUENCE { + maxNumAdditionalPCI-Case1-r17 INTEGER (1..7), + maxNumAdditionalPCI-Case2-r17 INTEGER (0..7) + } OPTIONAL, + -- R1 23-5-1 Group based L1-RSRP reporting enhancements + mTRP-GroupBasedL1-RSRP-r17 SEQUENCE { + maxNumBeamGroups-r17 INTEGER (1..4), + +``` + +``` + + maxNumRS-WithinSlot-r17 ENUMERATED {n2,n3,n4,n8,n16,n32,n64}, + maxNumRS-AcrossSlot-r17 ENUMERATED {n8, n16, n32, n64, n128} + } + -- R1 23-5-2c MAC-CE based update of explicit BFD-RS mTRP-PUCCH-IntraSlot-r17 => per band + mTRP-BFD-RS-MAC-CE-r17 ENUMERATED {n4, n8, n12, n16, n32, n48, n64 } + -- R1 23-7-1 Basic Features of CSI Enhancement for Multi-TRP + mTRP-CSI-EnhancementPerBand-r17 SEQUENCE { + maxNumNZP-CSI-RS-r17 INTEGER (2..8), + cSI-Report-mode-r17 ENUMERATED {model, mode2, both}, + supportedComboAcrossCCs-r17 SEQUENCE (SIZE (1..16)) OF CSI-MultiTRP-SupportedCombinations-r17, + codebookModeNCJT-r17 ENUMERATED{model,modelAnd2} + } + -- R1 23-7-1b Active CSI-RS resources and ports in the presence of multi-TRP CSI + codebookComboParameterMultiTRP-r17 CodebookComboParameterMultiTRP-r17 + -- R1 23-7-1a Additional CSI report mode 1 + mTRP-CSI-additionalCSI-r17 ENUMERATED{x1,x2} + -- R1 23-7-4 Support of Nmax=2 for Multi-TRP CSI + mTRP-CSI-N-Max2-r17 ENUMERATED {supported} + -- R1 23-7-5 CMR sharing + mTRP-CSI-CMR-r17 ENUMERATED {supported} + -- R1 23-8-11 Partial frequency sounding of SRS for non-frequency hopping case + srs-partialFreqSounding-r17 ENUMERATED {supported} + -- R1-24 feature: Extend beamSwitchTiming for FR2-2 + beamSwitchTiming-v1710 SEQUENCE { + scs-480kHz ENUMERATED {sym56, sym112, sym192, sym896, sym1344} + scs-960kHz ENUMERATED {sym112, sym224, sym384, sym1792, sym2688} + } + -- R1-24 feature: Extend beamSwitchTiming-r16 for FR2-2 + beamSwitchTiming-r17 SEQUENCE { + scs-480kHz-r17 ENUMERATED {sym896, sym1344} + scs-960kHz-r17 ENUMERATED {sym1792, sym2688} + } + -- R1-24 feature: Extend beamReportTiming for FR2-2 + beamReportTiming-v1710 SEQUENCE { + scs-480kHz-r17 ENUMERATED {sym56, sym112, sym224} + scs-960kHz-r17 ENUMERATED {sym112, sym224, sym448} + } + -- R1-24 feature: Extend maximum number of RX/TX beam switch DL for FR2-2 + maxNumberRxBTxBBeamSwitchDL-v1710 SEQUENCE { + scs-480kHz-r17 ENUMERATED {n2, n4, n7} + scs-960kHz-r17 ENUMERATED {n1, n2, n4, n7} + } +], +[[ + -- R1-23-1-4a: Semi-persistent/aperiodic capability value report + srs-PortReportSP-AP-r17 ENUMERATED {supported} + maxNumberRxBBeam-v1720 INTEGER (9..12) + -- R1-23-6-5 Support implicit configuration of RS(s) with two TCI states for beam failure detection + sfn-ImplicitRS-twoTCI-r17 ENUMERATED {supported} + -- R1-23-6-6 QCL-TypeD collision handling with CORESET with 2 TCI states + sfn-QCL-TypeD-Collision-twoTCI-r17 ENUMERATED {supported} +]] + +``` + +``` + +-- R1-23-7-1c Basic Features of CSI Enhancement for Multi-TRP - number of CPUs +mTRP-CSI-numCPU-r17 ENUMERATED {n2, n3, n4} OPTIONAL +]], +[[ +supportRepNumPDSCH-TDRA-DCI-1-2-r17 ENUMERATED {n2, n3, n4, n5, n6, n7, n8, n16} OPTIONAL +]], +[[ +codebookParametersetype2DopplerCSI-r18 CodebookParametersetype2DopplerCSI-r18 OPTIONAL, +codebookParametersfetype2DopplerCSI-r18 CodebookParametersfetype2DopplerCSI-r18 OPTIONAL, +-- R1 40-1-1a: Unified TCI with joint DL/UL TCI update for single-DCI based intra-cell multi-TRP with multiple activated TCI +-- codepoints per CC +tci-JointTCI-UpdateMultiActiveTCI-PerCC-r18 SEQUENCE { + tci-StateInd-r18 ENUMERATED {withAssignment, withoutAssignment}, + maxNumberActiveJointTCI-PerCC-r18 INTEGER (2..8) +} +-- R1 40-1-1c: DCI format 1_1 and if supported 1_2 configured with TCI selection field +tci-SelectionDCI-r18 ENUMERATED {supported} OPTIONAL, +-- R1 40-1-2: Unified TCI with separate DL/UL TCI update for single-DCI based intra-cell multi-TRP with single activated TCI +-- codepoint per CC +tci-SeperateTCI-UpdateSingleActiveTCI-PerCC-r18 SEQUENCE { + maxNumConfigDL-TCI-PerCC-PerBWP-r18 ENUMERATED {n4, n8, n12, n16, n24, n32, n48, n64, n128}, + maxNumConfigUL-TCI-PerCC-PerBWP-r18 ENUMERATED {n4, n8, n12, n16, n24, n32, n48, n64}, + maxNumActiveDL-TCI-AcrossCC-r18 ENUMERATED {n2, n4, n8, n16}, + maxNumActiveUL-TCI-AcrossCC-r18 ENUMERATED {n2, n4, n8, n16} +} +-- R1 40-1-3: Per aperiodic CSI-RS resource/resource set configuration for TCI selection in S-DCI based MTRP +tci-SelectionAperiodicCSI-RS-r18 ENUMERATED {perResource, perResourceSet, both} OPTIONAL, +-- R1 40-1-4: Two TCI states for CJT Tx scheme for PDSCH +twoTCI-StatePDSCH-CJT-TxScheme-r18 ENUMERATED {cjtSchemeA, cjtSchemeB, both} OPTIONAL, + +-- R1 40-2-3: TAG ID indication via absolute TA command MAC CE +spCell-TAG-Ind-r18 ENUMERATED {supported} OPTIONAL, +-- R1 40-2-4: PDCCH order sent by one TRP triggers RACH procedure (specifically PRACH) towards a different TRP based on CFRA for +-- inter-cell +interCellCrossTRP-PDCCH-OrderCFRA-r18 ENUMERATED {supported} OPTIONAL, +-- R1 40-2-4a: PDCCH order sent by one TRP triggers RACH procedure (specifically PRACH) towards a different TRP based on CFRA for +-- intra-cell +intraCellCrossTRP-PDCCH-OrderCFRA-r18 ENUMERATED {supported} OPTIONAL, +-- R1 40-2-9: Overlapping UL transmission reduction +overlapUL-TransReduction-r18 ENUMERATED {supported} OPTIONAL, + +-- R1 40-4-11: Joint configuration of Rel.18 DMRS ports and Rel.18 dynamic switching between DFT-S-OFDM and CP-OFDM for PUSCH +jointConfigDMRSPortDynamicSwitching-r18 ENUMERATED {supported} OPTIONAL, + +-- R1 40-5-1a: Comb offset hopping time-domain behavior when repetition factor R>1 +srs-combOffsetInTime-r18 ENUMERATED {srs, rsrs, both} OPTIONAL, +-- R1 40-5-1b: SRS comb offset hopping combined with legacy group/sequence hopping +srs-combOffsetCombinedGroupSequence-r18 ENUMERATED {supported} OPTIONAL, +-- R1 40-5-1c: Comb offset hopping within a subset +srs-combOffsetHoppingWithinSubset-r18 ENUMERATED {supported} OPTIONAL, +-- R1 40-5-2a: Smaller cyclic shift granularity for cyclic shift hopping + +``` + +``` + +srs-cyclicShiftHoppingSmallGranularity-r18 ENUMERATED {supported} OPTIONAL, +-- R1 40-5-2b: SRS cyclic shift hopping combined with legacy group/sequence hopping +srs-cyclicShiftCombinedGroupSequence-r18 ENUMERATED {supported} OPTIONAL, +-- R1 40-5-2c: Cyclic shift hopping within a subset +cyclicShiftHoppingWithinSubset-r18 ENUMERATED {supported} OPTIONAL, +-- R1 40-5-3: SRS cyclic shift hopping combined with SRS comb offset hopping +srs-cyclicShiftCombinedCombOffset-r18 ENUMERATED {supported} OPTIONAL, + +-- R1 40-6-1-1: 2 PTRS ports for single-DCI based STx2P SDM scheme for PUSCH-codebook +pusch-CB-2PTRS-SingleDCI-STx2P-SDM-r18 ENUMERATED {supported} OPTIONAL, +-- R1 40-6-1a-1: 2 PTRS ports for single-DCI based STx2P SDM scheme for PUSCH-noncodebook +pusch-NonCB-2PTRS-SingleDCI-STx2P-SDM-r18 ENUMERATED {supported} OPTIONAL, +-- R1 40-6-1b: Association between CSI-RS and SRS for noncodebook single-DCI based STx2P SDM scheme for PUSCH +pusch-NonCB-SingleDCI-STx2P-SDM-CSI-RS-SRS-r18 SEQUENCE { + maxNumberPeriodicSRS-Resource-PerBWP-r18 INTEGER (1..8), + maxNumberAperiodicSRS-Resource-PerBWP-r18 INTEGER (1..8), + maxNumberSemiPersistentSRS-ResourcePerBWP-r18 INTEGER (0..8), + valueY-SRS-ResourceAssociate-r18 INTEGER (1..16), + valueX-CSI-RS-ResourceAssociate-r18 INTEGER (1..2) +} OPTIONAL, +-- R1 40-6-1-2: New DMRS port entry for single-DCI based SDM scheme +dmrs-PortEntrySingleDCI-SDM-r18 ENUMERATED {supported} OPTIONAL, +-- R1 40-6-2-1: 2 PTRS ports for single-DCI based STx2P SFN scheme for PUSCH-codebook +pusch-CB-2PTRS-SingleDCI-STx2P-SFN-r18 ENUMERATED {supported} OPTIONAL, +-- R1 40-6-2a-1: 2 PTRS ports for single-DCI based STx2P SFN scheme for PUSCH-codebook +pusch-NonCB-2PTRS-SingleDCI-STx2P-SFN-r18 ENUMERATED {supported} OPTIONAL, +-- R1 40-6-2b: Association between CSI-RS and SRS for noncodebook single-DCI based STx2P SFN scheme for PUSCH +pusch-NonCB-SingleDCI-STx2P-SFN-CSI-RS-SRS-r18 SEQUENCE { + maxNumberPeriodicSRS-Resource-PerBWP-r18 INTEGER (1..8), + maxNumberAperiodicSRS-Resource-PerBWP-r18 INTEGER (1..8), + maxNumberSemiPersistentSRS-ResourcePerBWP-r18 INTEGER (0..8), + valueY-SRS-ResourceAssociate-r18 INTEGER (1..16), + valueX-CSI-RS-ResourceAssociate-r18 INTEGER (1..2) +} OPTIONAL, +-- R1 40-6-3c: Codebook multi-DCI based STx2P PUSCH+PUSCH - Fully overlapping PUSCHs in time and fully overlapping in frequency +twoPUSCH-CB-MultiDCI-STx2P-FullTimeFullFreqOverlap-r18 ENUMERATED {supported} OPTIONAL, +-- R1 40-6-3d: Codebook multi-DCI based STx2P PUSCH+PUSCH - Fully overlapping PUSCHs in time and partially overlapping in frequency +twoPUSCH-CB-MultiDCI-STx2P-FullTimePartialFreqOverlap-r18 ENUMERATED {supported} OPTIONAL, +-- R1 40-6-3e: Codebook multi-DCI based STx2P PUSCH+PUSCH - Partially overlapping PUSCHs in time and fully overlapping in frequency +twoPUSCH-CB-MultiDCI-STx2P-PartialTimeFullFreqOverlap-r18 ENUMERATED {supported} OPTIONAL, +-- R1 40-6-3f: Codebook multi-DCI based STx2P PUSCH+PUSCH - Partially overlapping PUSCHs in time, partially overlapping in frequency +twoPUSCH-CB-MultiDCI-STx2P-PartialTimePartialFreqOverlap-r18 ENUMERATED {supported} OPTIONAL, +-- R1 40-6-3g: Codebook multi-DCI based STx2P PUSCH+PUSCH - Partially overlapping PUSCHs in time, partially or non-overlapping +-- in frequency +twoPUSCH-CB-MultiDCI-STx2P-PartialTimeNonFreqOverlap-r18 ENUMERATED {supported} OPTIONAL, +-- R1 40-6-4a: Dynamic indication of repetition number for SFN scheme for PUCCH +pucch-RepetitionDynamicIndicationSFN-r18 ENUMERATED {supported} OPTIONAL +]] +} + +``` + +``` + +DummyG ::= SEQUENCE { + +``` + +``` + +maxNumberSSB-CSI-RS-ResourceOneTx ENUMERATED {n8, n16, n32, n64}, +maxNumberSSB-CSI-RS-ResourceTwoTx ENUMERATED {n0, n4, n8, n16, n32, n64}, +supportedCSI-RS-Density ENUMERATED {one, three, oneAndThree} +} + +BeamManagementSSB-CSI-RS ::= SEQUENCE { + maxNumberSSB-CSI-RS-ResourceOneTx ENUMERATED {n0, n8, n16, n32, n64}, + maxNumberCSI-RS-Resource ENUMERATED {n0, n4, n8, n16, n32, n64}, + maxNumberCSI-RS-ResourceTwoTx ENUMERATED {n0, n4, n8, n16, n32, n64}, + supportedCSI-RS-Density ENUMERATED {one, three, oneAndThree} OPTIONAL, + maxNumberAperiodicCSI-RS-Resource ENUMERATED {n0, n1, n4, n8, n16, n32, n64} +} + +DummyH ::= SEQUENCE { + burstLength INTEGER (1..2), + maxSimultaneousResourceSetsPerCC INTEGER (1..8), + maxConfiguredResourceSetsPerCC INTEGER (1..64), + maxConfiguredResourceSetsAllCC INTEGER (1..128) +} + +CSI-RS-ForTracking ::= SEQUENCE { + maxBurstLength INTEGER (1..2), + maxSimultaneousResourceSetsPerCC INTEGER (1..8), + maxConfiguredResourceSetsPerCC INTEGER (1..64), + maxConfiguredResourceSetsAllCC INTEGER (1..256) +} + +CSI-RS-IM-ReceptionForFeedback ::= SEQUENCE { + maxConfigNumberNZP-CSI-RS-PerCC INTEGER (1..64), + maxConfigNumberPortsAcrossNZP-CSI-RS-PerCC INTEGER (2..256), + maxConfigNumberCSI-IM-PerCC ENUMERATED {n1, n2, n4, n8, n16, n32}, + maxNumberSimultaneousNZP-CSI-RS-PerCC INTEGER (1..64), + totalNumberPortsSimultaneousNZP-CSI-RS-PerCC INTEGER (2..256) +} + +CSI-RS-ProcFrameworkForSRS ::= SEQUENCE { + maxNumberPeriodicSRS-AssocCSI-RS-PerBWP INTEGER (1..4), + maxNumberAperiodicSRS-AssocCSI-RS-PerBWP INTEGER (1..4), + maxNumberSP-SRS-AssocCSI-RS-PerBWP INTEGER (0..4), + simultaneousSRS-AssocCSI-RS-PerCC INTEGER (1..8) +} + +CSI-ReportFramework ::= SEQUENCE { + maxNumberPeriodicCSI-PerBWP-ForCSI-Report INTEGER (1..4), + maxNumberAperiodicCSI-PerBWP-ForCSI-Report INTEGER (1..4), + maxNumberSemiPersistentCSI-PerBWP-ForCSI-Report INTEGER (0..4), + maxNumberPeriodicCSI-PerBWP-ForBeamReport INTEGER (1..4), + maxNumberAperiodicCSI-PerBWP-ForBeamReport INTEGER (1..4), + maxNumberAperiodicCSI-triggeringStatePerCC ENUMERATED {n3, n7, n15, n31, n63, n128}, + maxNumberSemiPersistentCSI-PerBWP-ForBeamReport INTEGER (0..4), + simultaneousCSI-ReportsPerCC INTEGER (1..8) +} + +``` + +``` + +} + +CSI-ReportFrameworkExt-r16 ::= SEQUENCE { + maxNumberAperiodicCSI-PerBWP-ForCSI-ReportExt-r16 INTEGER (5..8) +} + +PTRS-DensityRecommendationDL ::= SEQUENCE { + frequencyDensity1 INTEGER (1..276), + frequencyDensity2 INTEGER (1..276), + timeDensity1 INTEGER (0..29), + timeDensity2 INTEGER (0..29), + timeDensity3 INTEGER (0..29) +} + +PTRS-DensityRecommendationUL ::= SEQUENCE { + frequencyDensity1 INTEGER (1..276), + frequencyDensity2 INTEGER (1..276), + timeDensity1 INTEGER (0..29), + timeDensity2 INTEGER (0..29), + timeDensity3 INTEGER (0..29), + sampleDensity1 INTEGER (1..276), + sampleDensity2 INTEGER (1..276), + sampleDensity3 INTEGER (1..276), + sampleDensity4 INTEGER (1..276), + sampleDensity5 INTEGER (1..276) +} + +SpatialRelations ::= SEQUENCE { + maxNumberConfiguredSpatialRelations ENUMERATED {n4, n8, n16, n32, n64, n96}, + maxNumberActiveSpatialRelations ENUMERATED {n1, n2, n4, n8, n14}, + additionalActiveSpatialRelationPUCCH ENUMERATED {supported} OPTIONAL, + maxNumberDL-RS-QCL-TypeD ENUMERATED {n1, n2, n4, n8, n14} +} + +DummyI ::= SEQUENCE { + supportedSRS-TxPortSwitch ENUMERATED {t1r2, t1r4, t2r4, t1r4-t2r4, tr-equal}, + txSwitchImpactToRx ENUMERATED {true} OPTIONAL +} + +CSI-MultiTRP-SupportedCombinations-r17 ::= SEQUENCE { + maxNumTx-Ports-r17 ENUMERATED {n2, n4, n8, n12, n16, n24, n32}, + maxTotalNumCMR-r17 INTEGER (2..64), + maxTotalNumTx-PortsNZP-CSI-RS-r17 INTEGER (2..256) +} + +-- TAG-MIMO-PARAMETERSPERBAND-STOP +-- ASN1STOP + +``` + +| MIMO-ParametersPerBand field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| codebookParametersPerBand
For a given frequency band, this field this field indicates the alternative list of SupportedCSI-RS-Resource supported for each codebook type. The supported CSI-RS resources indicated by this field are referred by codebookParametersperBC in CA-ParametersNR to indicate the supported CSI-RS resource per band combination. | +| csi-RS-IM-ReceptionForFeedback/ csi-RS-ProcFrameworkForSRS/ csi-ReportFramework
CSI related capabilities which the UE supports on each of the carriers operated on this band. If the network configures the UE with serving cells on both FR1 and FR2 bands these values may be further limited by the corresponding fields in fr1-fr2-Add-UE-NR-Capabilities . | +| supportNewDMRS-Port
Presence of this field set to supported1 , supported2 or supported3 indicates that the UE supports the new DMRS port entry {0,2,3}. | + +#### – *ModulationOrder* + +The IE *ModulationOrder* is used to convey the maximum supported modulation order. + +#### ***ModulationOrder* information element** + +``` +-- ASN1START +-- TAG-MODULATIONORDER-START + +ModulationOrder ::= ENUMERATED {bpsk-halfpi, bpsk, qpsk, qam16, qam64, qam256} + +-- TAG-MODULATIONORDER-STOP +-- ASN1STOP +``` + +#### – *MRDC-Parameters* + +The IE *MRDC-Parameters* contains the band combination parameters specific to MR-DC for a given MR-DC band combination. + +#### ***MRDC-Parameters* information element** + +``` +-- ASN1START +-- TAG-MRDC-PARAMETERS-START + +MRDC-Parameters ::= SEQUENCE { + singleUL-Transmission ENUMERATED {supported} OPTIONAL, + dynamicPowerSharingENDC ENUMERATED {supported} OPTIONAL, + tdm-Pattern ENUMERATED {supported} OPTIONAL, + ul-SharingEUTRA-NR ENUMERATED {tdm, fdm, both} OPTIONAL, + ul-SwitchingTimeEUTRA-NR ENUMERATED {type1, type2} OPTIONAL, + simultaneousRxTxInterBandENDC ENUMERATED {supported} OPTIONAL, + asyncIntraBandENDC ENUMERATED {supported} OPTIONAL, + ... + [[ + dualPA-Architecture ENUMERATED {supported} OPTIONAL, + intraBandENDC-Support ENUMERATED {non-contiguous, both} OPTIONAL, + ]] +``` + +``` + + ul-TimingAlignmentEUTRA-NR ENUMERATED {required} OPTIONAL + ]] +} + +MRDC-Parameters-v1580 ::= SEQUENCE { + dynamicPowerSharingNEDC ENUMERATED {supported} OPTIONAL +} + +MRDC-Parameters-v1590 ::= SEQUENCE { + interBandContiguousMRDC ENUMERATED {supported} OPTIONAL +} + +MRDC-Parameters-v15g0 ::= SEQUENCE { + simultaneousRxBTxInterBandENDCPerBandPair SimultaneousRxBTxPerBandPair OPTIONAL +} + +MRDC-Parameters-v15n0 ::= SEQUENCE { + intraBandENDC-Support-UL ENUMERATED {non-contiguous, both} OPTIONAL +} + +MRDC-Parameters-v1620 ::= SEQUENCE { + maxUplinkDutyCycle-interBandENDC-TDD-PC2-r16 SEQUENCE{ + eutra-TDD-Config0-r16 ENUMERATED {n20, n40, n50, n60, n70, n80, n90, n100} OPTIONAL, + eutra-TDD-Config1-r16 ENUMERATED {n20, n40, n50, n60, n70, n80, n90, n100} OPTIONAL, + eutra-TDD-Config2-r16 ENUMERATED {n20, n40, n50, n60, n70, n80, n90, n100} OPTIONAL, + eutra-TDD-Config3-r16 ENUMERATED {n20, n40, n50, n60, n70, n80, n90, n100} OPTIONAL, + eutra-TDD-Config4-r16 ENUMERATED {n20, n40, n50, n60, n70, n80, n90, n100} OPTIONAL, + eutra-TDD-Config5-r16 ENUMERATED {n20, n40, n50, n60, n70, n80, n90, n100} OPTIONAL, + eutra-TDD-Config6-r16 ENUMERATED {n20, n40, n50, n60, n70, n80, n90, n100} OPTIONAL, + } OPTIONAL, + -- R1 18-2 Single UL TX operation for TDD PCell in EN-DC + tdm-restrictionTDD-endc-r16 ENUMERATED {supported} OPTIONAL, + -- R1 18-2a Single UL TX operation for FDD PCell in EN-DC + tdm-restrictionFDD-endc-r16 ENUMERATED {supported} OPTIONAL, + -- R1 18-2b Support of HARQ-offset for SUO case1 in EN-DC with LTE TDD PCell for type 1 UE + singleUL-HARQ-offsetTDD-PCell-r16 ENUMERATED {supported} OPTIONAL, + -- R1 18-3 Dual Tx transmission for EN-DC with FDD PCell(TDM pattern for dual Tx UE) + tdm-restrictionDualTX-FDD-endc-r16 ENUMERATED {supported} OPTIONAL +} + +MRDC-Parameters-v1630 ::= SEQUENCE { + -- R4 2-20 Maximum uplink duty cycle for FDD+TDD EN-DC power class 2 + maxUplinkDutyCycle-interBandENDC-FDD-TDD-PC2-r16 SEQUENCE { + maxUplinkDutyCycle-FDD-TDD-EN-DC1-r16 ENUMERATED {n30, n40, n50, n60, n70, n80, n90, n100} OPTIONAL, + maxUplinkDutyCycle-FDD-TDD-EN-DC2-r16 ENUMERATED {n30, n40, n50, n60, n70, n80, n90, n100} OPTIONAL, + } OPTIONAL, + + -- R4 2-19 FDD-FDD or TDD-TDD inter-band MR-DC with overlapping or partially overlapping DL spectrum + interBandMRDC-WithOverlapDL-Bands-r16 ENUMERATED {supported} OPTIONAL +} + +``` + +``` + +MRDC-Parameters-v1700 ::= SEQUENCE { + condPSCellAdditionENDC-r17 ENUMERATED {supported} OPTIONAL, + scg-ActivationDeactivationENDC-r17 ENUMERATED {supported} OPTIONAL, + scg-ActivationDeactivationResumeENDC-r17 ENUMERATED {supported} OPTIONAL +} + +MRDC-Parameters-v1770 ::= SEQUENCE { + -- R4 26-1: Higher Power Limit CA DC + higherPowerLimitMRDC-r17 ENUMERATED {supported} OPTIONAL +} + +-- TAG-MRDC-PARAMETERS-STOP +-- ASN1STOP + +``` + +#### – *NCR-Parameters* + +The IE *NCR-Parameters* is used to indicate the UE capabilities supported by NCR-MT. + +#### ***NCR-Parameters* information element** + +``` + +-- ASN1START +-- TAG-NCR-PARAMETERS-START + +NCR-Parameters-r18 ::= SEQUENCE { + inactiveStateNCR-r18 ENUMERATED {supported} OPTIONAL, + supportedNumberOfDRBs-NCR-r18 ENUMERATED {n1,n16} OPTIONAL, + nonDRB-NCR-r18 ENUMERATED {supported} OPTIONAL +} + +-- TAG-NCR-PARAMETERS-STOP +-- ASN1STOP + +``` + +#### – *NRDC-Parameters* + +The IE *NRDC-Parameters* contains parameters specific to NR-DC, i.e., which are not applicable to NR SA. + +#### ***NRDC-Parameters* information element** + +``` + +-- ASN1START +-- TAG-NRDC-PARAMETERS-START + +NRDC-Parameters ::= SEQUENCE { + measAndMobParametersNRDC MeasAndMobParametersMRDC OPTIONAL, + generalParametersNRDC GeneralParametersMRDC-XDD-Diff OPTIONAL, + fdd-Add-UE-NRDC-Capabilities UE-MRDC-CapabilityAddXDD-Mode OPTIONAL, + tdd-Add-UE-NRDC-Capabilities UE-MRDC-CapabilityAddXDD-Mode OPTIONAL, +} + +``` + +``` + + fr1-Add-UE-NRDC-Capabilities UE-MRDC-CapabilityAddFRX-Mode OPTIONAL, + fr2-Add-UE-NRDC-Capabilities UE-MRDC-CapabilityAddFRX-Mode OPTIONAL, + dummy2 OCTET STRING OPTIONAL, + dummy SEQUENCE {} OPTIONAL +} + +NRDC-Parameters-v1570 ::= SEQUENCE { + sfn-SyncNRDC ENUMERATED {supported} OPTIONAL +} + +NRDC-Parameters-v15c0 ::= SEQUENCE { + pdcp-DuplicationSplitSRB ENUMERATED {supported} OPTIONAL, + pdcp-DuplicationSplitDRB ENUMERATED {supported} OPTIONAL +} + +NRDC-Parameters-v1610 ::= SEQUENCE { + measAndMobParametersNRDC-v1610 MeasAndMobParametersMRDC-v1610 OPTIONAL +} + +NRDC-Parameters-v1700 ::= SEQUENCE { + flc-OverNR-RRC-r17 ENUMERATED {supported} OPTIONAL, + measAndMobParametersNRDC-v1700 MeasAndMobParametersMRDC-v1700 +} + +-- TAG-NRDC-PARAMETERS-STOP +-- ASN1STOP + +``` + +#### – NTN-Parameters + +The IE *NTN-Parameters* is used to convey the subset of UE Radio Access Capability Parameters that apply to NTN access when there is a difference compared to TN access. + +#### NTN-Parameters information element + +``` + +-- ASN1START +-- TAG-NTN-PARAMETERS-START + +NTN-Parameters-r17 ::= SEQUENCE { + inactiveStateNTN-r17 ENUMERATED {supported} OPTIONAL, + ra-SDT-NTN-r17 ENUMERATED {supported} OPTIONAL, + srb-SDT-NTN-r17 ENUMERATED {supported} OPTIONAL, + measAndMobParametersNTN-r17 MeasAndMobParameters OPTIONAL, + mac-ParametersNTN-r17 MAC-Parameters OPTIONAL, + phy-ParametersNTN-r17 Phy-Parameters OPTIONAL, + fdd-Add-UE-NR-CapabilitiesNTN-r17 UE-NR-CapabilityAddXDD-Mode OPTIONAL, + fr1-Add-UE-NR-CapabilitiesNTN-r17 UE-NR-CapabilityAddFRX-Mode OPTIONAL, + ue-BasedPerfMeas-ParametersNTN-r17 UE-BasedPerfMeas-Parameters-r16 OPTIONAL, +} + +``` + +``` + + son-ParametersNTN-r17 SON-Parameters-r16 OPTIONAL +} + +-- TAG-NTN-PARAMETERS-STOP +-- ASN1STOP + +``` + +| NTN-Parameters field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| fdd-Add-UE-NR-CapabilitiesNTN
NTN related capabilities which the UE supports in NTN differently than in TN. If absent, fdd-Add-UE-NR-Capabilities applies to NTN. | +| fr1-Add-UE-NR-CapabilitiesNTN
NTN related capabilities which the UE supports in NTN differently than in TN. If absent, fr1-Add-UE-NR-Capabilities applies to NTN. | +| mac-ParametersNTN
NTN related capabilities which the UE supports in NTN differently than in TN. If absent, mac-Parameters applies to NTN. | +| measAndMobParametersNTN
NTN related capabilities which the UE supports in NTN differently than in TN. If absent, measAndMobParameters applies to NTN. | +| phy-ParametersNTN
NTN related capabilities which the UE supports in NTN differently than in TN. If absent, phy-Parameters applies to NTN. | +| son-ParametersNTN
NTN related capabilities which the UE supports in NTN differently than in TN. If absent, son-Parameters-r16 applies to NTN. | +| ue-BasedPerfMeas-ParametersNTN
NTN related capabilities which the UE supports in NTN differently than in TN. If absent, ue-BasedPerfMeas-Parameters-r16 applies to NTN. | + +#### — ***OLPC-SRS-Pos*** + +The IE *OLPC-SRS-Pos* is used to convey OLPC SRS positioning related parameters specific for a certain band. + +#### ***OLPC-SRS-Pos* information element** + +``` + +-- ASN1START +-- TAG-OLPC-SRS-POS-START + +OLPC-SRS-Pos-r16 ::= SEQUENCE { + olpc-SRS-PosBasedOnPRS-Serving-r16 ENUMERATED {supported} OPTIONAL, + olpc-SRS-PosBasedOnSSB-Neigh-r16 ENUMERATED {supported} OPTIONAL, + olpc-SRS-PosBasedOnPRS-Neigh-r16 ENUMERATED {supported} OPTIONAL, + maxNumberPathLossEstimatePerServing-r16 ENUMERATED {n1, n4, n8, n16} OPTIONAL +} + +--TAG-OLPC-SRS-POS-STOP +-- ASN1STOP + +``` + +#### – PDCP-Parameters + +The IE *PDCP-Parameters* is used to convey capabilities related to PDCP. + +#### PDCP-Parameters information element + +``` +-- ASN1START +-- TAG-PDCP-PARAMETERS-START + +PDCP-Parameters ::= SEQUENCE { + supportedROHC-Profiles SEQUENCE { + profile0x0000 BOOLEAN, + profile0x0001 BOOLEAN, + profile0x0002 BOOLEAN, + profile0x0003 BOOLEAN, + profile0x0004 BOOLEAN, + profile0x0006 BOOLEAN, + profile0x0101 BOOLEAN, + profile0x0102 BOOLEAN, + profile0x0103 BOOLEAN, + profile0x0104 BOOLEAN + }, + maxNumberROHC-ContextSessions ENUMERATED {cs2, cs4, cs8, cs12, cs16, cs24, cs32, cs48, cs64, + cs128, cs256, cs512, cs1024, cs16384, spare2, spare1}, + uplinkOnlyROHC-Profiles ENUMERATED {supported} OPTIONAL, + continueROHC-Context ENUMERATED {supported} OPTIONAL, + outOfOrderDelivery ENUMERATED {supported} OPTIONAL, + shortSN ENUMERATED {supported} OPTIONAL, + pdcp-DuplicationSRB ENUMERATED {supported} OPTIONAL, + pdcp-DuplicationMCG-OrSCG-DRB ENUMERATED {supported} OPTIONAL, + ... + [[ + drb-IAB-r16 ENUMERATED {supported} OPTIONAL, + non-DRB-IAB-r16 ENUMERATED {supported} OPTIONAL, + extendedDiscardTimer-r16 ENUMERATED {supported} OPTIONAL, + continueEHC-Context-r16 ENUMERATED {supported} OPTIONAL, + ehc-r16 ENUMERATED {supported} OPTIONAL, + maxNumberEHC-Contexts-r16 ENUMERATED {cs2, cs4, cs8, cs16, cs32, cs64, cs128, cs256, cs512, + cs1024, cs2048, cs4096, cs8192, cs16384, cs32768, cs65536} OPTIONAL, + jointEHC-ROHC-Config-r16 ENUMERATED {supported} OPTIONAL, + pdcp-DuplicationMoreThanTwoRLC-r16 ENUMERATED {supported} OPTIONAL + ]], + [[ + longSN-RedCap-r17 ENUMERATED {supported} OPTIONAL, + udc-r17 SEQUENCE { + standardDictionary-r17 ENUMERATED {supported} OPTIONAL, + operatorDictionary-r17 SEQUENCE { + versionOfDictionary-r17 INTEGER (0..15), + associatedPLMN-ID-r17 PLMN-Identity + } + } + } +} +``` + +``` + + continueUDC-r17 ENUMERATED {supported} OPTIONAL, + supportOfBufferSize-r17 ENUMERATED {kbyte4, kbyte8} OPTIONAL + } + [[ + [[ + longSN-NCR-r18 ENUMERATED {supported} OPTIONAL + ]] +} + +-- TAG-PDCP-PARAMETERS-STOP +-- ASN1STOP + +``` + +#### – *PDCP-ParametersMRDC* + +The IE *PDCP-ParametersMRDC* is used to convey PDCP related capabilities for MR-DC. + +#### ***PDCP-ParametersMRDC* information element** + +``` + +-- ASN1START +-- TAG-PDCP-PARAMETERSMRDC-START + +PDCP-ParametersMRDC ::= SEQUENCE { + pdcp-DuplicationSplitSRB ENUMERATED {supported} OPTIONAL, + pdcp-DuplicationSplitDRB ENUMERATED {supported} OPTIONAL +} + +PDCP-ParametersMRDC-v1610 ::= SEQUENCE { + scg-DRB-NR-IAB-r16 ENUMERATED {supported} OPTIONAL +} + +-- TAG-PDCP-PARAMETERSMRDC-STOP +-- ASN1STOP + +``` + +#### – *Phy-Parameters* + +The IE *Phy-Parameters* is used to convey the physical layer capabilities. + +#### ***Phy-Parameters* information element** + +``` + +-- ASN1START +-- TAG-PHY-PARAMETERS-START + +Phy-Parameters ::= SEQUENCE { + phy-ParametersCommon Phy-ParametersCommon OPTIONAL, + phy-ParametersXDD-Diff Phy-ParametersXDD-Diff OPTIONAL, + phy-ParametersFRX-Diff Phy-ParametersFRX-Diff OPTIONAL, +} + +``` + +``` + +phy-ParametersFR1 Phy-ParametersFR1 OPTIONAL, +phy-ParametersFR2 Phy-ParametersFR2 OPTIONAL +} + +Phy-Parameters-v16a0 ::= SEQUENCE { + phy-ParametersCommon-v16a0 Phy-ParametersCommon-v16a0 OPTIONAL +} + +Phy-ParametersCommon ::= SEQUENCE { + csi-RS-CFRA-ForHO ENUMERATED {supported} OPTIONAL, + dynamicPRB-BundlingDL ENUMERATED {supported} OPTIONAL, + sp-CSI-ReportPUCCH ENUMERATED {supported} OPTIONAL, + sp-CSI-ReportPUSCH ENUMERATED {supported} OPTIONAL, + nzp-CSI-RS-IntefMgmt ENUMERATED {supported} OPTIONAL, + type2-SP-CSI-Feedback-LongPUCCH ENUMERATED {supported} OPTIONAL, + precoderGranularityCORESET ENUMERATED {supported} OPTIONAL, + dynamicHARQ-ACK-Codebook ENUMERATED {supported} OPTIONAL, + semiStaticHARQ-ACK-Codebook ENUMERATED {supported} OPTIONAL, + spatialBundlingHARQ-ACK ENUMERATED {supported} OPTIONAL, + dynamicBetaOffsetInd-HARQ-ACK-CSI ENUMERATED {supported} OPTIONAL, + pucch-Repetition-F1-3-4 ENUMERATED {supported} OPTIONAL, + ra-Type0-PUSCH ENUMERATED {supported} OPTIONAL, + dynamicSwitchRA-Type0-1-PDSCH ENUMERATED {supported} OPTIONAL, + dynamicSwitchRA-Type0-1-PUSCH ENUMERATED {supported} OPTIONAL, + pdsch-MappingTypeA ENUMERATED {supported} OPTIONAL, + pdsch-MappingTypeB ENUMERATED {supported} OPTIONAL, + interleavingVRB-ToPRB-PDSCH ENUMERATED {supported} OPTIONAL, + interSlotFreqHopping-PUSCH ENUMERATED {supported} OPTIONAL, + type1-PUSCH-RepetitionMultiSlots ENUMERATED {supported} OPTIONAL, + type2-PUSCH-RepetitionMultiSlots ENUMERATED {supported} OPTIONAL, + pusch-RepetitionMultiSlots ENUMERATED {supported} OPTIONAL, + pdsch-RepetitionMultiSlots ENUMERATED {supported} OPTIONAL, + downlinkSPS ENUMERATED {supported} OPTIONAL, + configuredUL-GrantType1 ENUMERATED {supported} OPTIONAL, + configuredUL-GrantType2 ENUMERATED {supported} OPTIONAL, + pre-EmptIndication-DL ENUMERATED {supported} OPTIONAL, + cbg-TransIndication-DL ENUMERATED {supported} OPTIONAL, + cbg-TransIndication-UL ENUMERATED {supported} OPTIONAL, + cbg-FlushIndication-DL ENUMERATED {supported} OPTIONAL, + dynamicHARQ-ACK-CodeB-CBG-Retx-DL ENUMERATED {supported} OPTIONAL, + rateMatchingResrcSetSemi-Static ENUMERATED {supported} OPTIONAL, + rateMatchingResrcSetDynamic ENUMERATED {supported} OPTIONAL, + bwp-SwitchingDelay ENUMERATED {type1, type2} OPTIONAL, + ..., + [[ + dummy ENUMERATED {supported} OPTIONAL + ]], + [[ + maxNumberSearchSpaces ENUMERATED {n10} OPTIONAL, + rateMatchingCtrlResrcSetDynamic ENUMERATED {supported} OPTIONAL, + maxLayersMIMO-Indication ENUMERATED {supported} OPTIONAL + ]]] + +``` + +``` + +]], +[[ +spCellPlacement CarrierAggregationVariant OPTIONAL +]], +[[ +-- R1 9-1: Basic channel structure and procedure of 2-step RACH +twoStepRACH-r16 ENUMERATED {supported} OPTIONAL, +-- R1 11-1: Monitoring DCI format 1_2 and DCI format 0_2 +dci-Format1-2And0-2-r16 ENUMERATED {supported} OPTIONAL, +-- R1 11-1a: Monitoring both DCI format 0 1/1 1 and DCI format 0 2/1 2 in the same search space +monitoringDCI-SameSearchSpace-r16 ENUMERATED {supported} OPTIONAL, +-- R1 11-10: Type 2 configured grant release by DCI format 0_1 +type2-CG-ReleaseDCI-0-1-r16 ENUMERATED {supported} OPTIONAL, +-- R1 11-11: Type 2 configured grant release by DCI format 0_2 +type2-CG-ReleaseDCI-0-2-r16 ENUMERATED {supported} OPTIONAL, +-- R1 12-3: SPS release by DCI format 1_1 +sps-ReleaseDCI-1-1-r16 ENUMERATED {supported} OPTIONAL, +-- R1 12-3a: SPS release by DCI format 1_2 +sps-ReleaseDCI-1-2-r16 ENUMERATED {supported} OPTIONAL, +-- R1 14-8: CSI trigger states containing non-active BWP +csi-TriggerStateNon-ActiveBWP-r16 ENUMERATED {supported} OPTIONAL, +-- R1 20-2: Support up to 4 SMTCs configured for an IAB node MT per frequency location, including IAB-specific SMTC window periodicities +separateSMTC-InterIAB-Support-r16 ENUMERATED {supported} OPTIONAL, +-- R1 20-3: Support RACH configuration separately from the RACH configuration for UE access, including new IAB-specific offset and scaling factors +separateRACH-IAB-Support-r16 ENUMERATED {supported} OPTIONAL, +-- R1 20-5a: Support semi-static configuration/indication of UL-Flexible-DL slot formats for IAB-MT resources +ul-flexibleDL-SlotFormatSemiStatic-IAB-r16 ENUMERATED {supported} OPTIONAL, +-- R1 20-5b: Support dynamic indication of UL-Flexible-DL slot formats for IAB-MT resources +ul-flexibleDL-SlotFormatDynamics-IAB-r16 ENUMERATED {supported} OPTIONAL, +dft-S-OFDM-WaveformUL-IAB-r16 ENUMERATED {supported} OPTIONAL, +-- R1 20-6: Support DCI Format 2_5 based indication of soft resource availability to an IAB node +dci-25-AI-RNTI-Support-IAB-r16 ENUMERATED {supported} OPTIONAL, +-- R1 20-7: Support T_delta reception. +t-DeltaReceptionSupport-IAB-r16 ENUMERATED {supported} OPTIONAL, +-- R1 20-8: Support of Desired guard symbol reporting and provided guard symbol reception. +guardSymbolReportReception-IAB-r16 ENUMERATED {supported} OPTIONAL, +-- R1 18-8 HARQ-ACK codebook type and spatial bundling per PUCCH group +harqACK-CB-SpatialBundlingPUCCH-Group-r16 ENUMERATED {supported} OPTIONAL, +-- R1 19-2: Cross Slot Scheduling +crossSlotScheduling-r16 SEQUENCE { + non-SharedSpectrumChAccess-r16 ENUMERATED {supported} OPTIONAL, + sharedSpectrumChAccess-r16 ENUMERATED {supported} OPTIONAL +} OPTIONAL, +maxNumberSRS-PosPathLossEstimateAllServingCells-r16 ENUMERATED {n1, n4, n8, n16} OPTIONAL, +extendedCG-Periodicities-r16 ENUMERATED {supported} OPTIONAL, +extendedSPS-Periodicities-r16 ENUMERATED {supported} OPTIONAL, +codebookVariantsList-r16 CodebookVariantsList-r16 OPTIONAL, +-- R1 11-6: PUSCH repetition Type A +pusch-RepetitionTypeA-r16 SEQUENCE { + sharedSpectrumChAccess-r16 ENUMERATED {supported} OPTIONAL, +} + +``` + +``` + + non-SharedSpectrumChAccess-r16 ENUMERATED {supported} OPTIONAL + } + OPTIONAL, + -- R1 11-4b: DL priority indication in DCI with mixed DCI formats + dci-DL-PriorityIndicator-r16 ENUMERATED {supported} OPTIONAL, + -- R1 12-1a: UL priority indication in DCI with mixed DCI formats + dci-UL-PriorityIndicator-r16 ENUMERATED {supported} OPTIONAL, + -- R1 16-1e: Maximum number of configured pathloss reference RSs for PUSCH/PUCCH/SRS by RRC for MAC-CE based pathloss reference RS update + maxNumberPathlossRS-Update-r16 ENUMERATED {n4, n8, n16, n32, n64} OPTIONAL, + + -- R1 18-9: Usage of the PDSCH starting time for HARQ-ACK type 2 codebook + type2-HARQ-ACK-Codebook-r16 ENUMERATED {supported} OPTIONAL, + -- R1 16-1g-1: Resources for beam management, pathloss measurement, BFD, RLM and new beam identification across frequency ranges + maxTotalResourcesForAcrossFreqRanges-r16 SEQUENCE { + maxNumberResWithinSlotAcrossCC-AcrossFR-r16 ENUMERATED {n2, n4, n8, n12, n16, n32, n64, n128} OPTIONAL, + maxNumberResAcrossCC-AcrossFR-r16 ENUMERATED {n2, n4, n8, n12, n16, n32, n40, n48, n64, n72, n80, n96, n128, n256} + OPTIONAL + } + OPTIONAL, + -- R1 16-2a-4: HARQ-ACK for multi-DCI based multi-TRP - separate + harqACK-separateMultiDCI-MultiTRP-r16 SEQUENCE { + maxNumberLongPUCCHs-r16 ENUMERATED {longAndLong, longAndShort, shortAndShort} OPTIONAL + } + OPTIONAL, + -- R1 16-2a-4: HARQ-ACK for multi-DCI based multi-TRP - joint + harqACK-jointMultiDCI-MultiTRP-r16 ENUMERATED {supported} OPTIONAL, + -- R4 9-1: BWP switching on multiple CCs RRM requirements + bwp-SwitchingMultiCCs-r16 CHOICE { + type1-r16 ENUMERATED {us100, us200}, + type2-r16 ENUMERATED {us200, us400, us800, us1000} + } + OPTIONAL +], +[[ +targetSMTC-SCG-r16 ENUMERATED {supported} OPTIONAL, +supportRepetitionZeroOffsetRV-r16 ENUMERATED {supported} OPTIONAL, +-- R1 11-12: in-order CBG-based re-transmission +cbg-TransInOrderPUSCH-UL-r16 ENUMERATED {supported} OPTIONAL +], +[[ +-- R4 6-3: Dormant BWP switching on multiple CCs RRM requirements +bwp-SwitchingMultiDormancyCCs-r16 CHOICE { + type1-r16 ENUMERATED {us100, us200}, + type2-r16 ENUMERATED {us200, us400, us800, us1000} +} +OPTIONAL, +-- R1 16-2a-8: Indicates that retransmission scheduled by a different CORESETPoolIndex for multi-DCI multi-TRP is not supported. +supportRetx-Diff-CoresetPool-Multi-DCI-TRP-r16 ENUMERATED {notSupported} OPTIONAL, +-- R1 22-10: Support of pdcch-MonitoringAnyOccasionsWithSpanGap in case of cross-carrier scheduling with different SCSs +pdcch-MonitoringAnyOccasionsWithSpanGapCrossCarrierSch-r16 ENUMERATED {mode2, mode3} OPTIONAL +], +[[ +-- R1 16-1j-1: Support of 2 port CSI-RS for new beam identification +newBeamIdentifications2PortCSI-RS-r16 ENUMERATED {supported} OPTIONAL, +-- R1 16-1j-2: Support of 2 port CSI-RS for pathloss estimation +pathlossEstimation2PortCSI-RS-r16 ENUMERATED {supported} OPTIONAL + +``` + +``` + +]], +[[ +mux-HARQ-ACK-withoutPUCCH-onPUSCH-r16 ENUMERATED {supported} OPTIONAL +]], +[[ +-- R1 31-1: Support of Desired Guard Symbol reporting and provided guard symbol reception. +guardSymbolReportReception-IAB-r17 ENUMERATED {supported} OPTIONAL, +-- R1 31-2: support of restricted IAB-DU beam reception +restricted-IAB-DU-BeamReception-r17 ENUMERATED {supported} OPTIONAL, +-- R1 31-3: support of recommended IAB-MT beam transmission for DL and UL beam +recommended-IAB-MT-BeamTransmission-r17 ENUMERATED {supported} OPTIONAL, +-- R1 31-4: support of case 6 timing alignment indication reception +case6-TimingAlignmentReception-IAB-r17 ENUMERATED {supported} OPTIONAL, +-- R1 31-5: support of case 7 timing offset indication reception and case 7 timing at parent-node indication reception +case7-TimingAlignmentReception-IAB-r17 ENUMERATED {supported} OPTIONAL, +-- R1 31-6: support of desired DL Tx power adjustment reporting and DL Tx power adjustment reception +dl-tx-PowerAdjustment-IAB-r17 ENUMERATED {supported} OPTIONAL, +-- R1 31-7: support of desired IAB-MT PSD range reporting +desired-ul-tx-PowerAdjustment-r17 ENUMERATED {supported} OPTIONAL, +-- R1 31-8: support of monitoring DCI Format 2_5 scrambled by AI-RNTI for indication of FDM soft resource availability to an IAB node +fdm-SoftResourceAvailability-DynamicIndication-r17 ENUMERATED {supported} OPTIONAL, +-- R1 31-10: Support of updated T delta range reception +updated-T-DeltaRangeReception-r17 ENUMERATED {supported} OPTIONAL, +-- R1 30-5: Support slot based dynamic PUCCH repetition indication for PUCCH formats 0/1/2/3/4 +slotBasedDynamicPUCCH-Rep-r17 ENUMERATED {supported} OPTIONAL, +-- R1 25-1: Support of HARQ-ACK deferral in case of TDD collision +sps-HARQ-ACK-Deferral-r17 SEQUENCE { + non-SharedSpectrumChAccess-r17 ENUMERATED {supported} OPTIONAL, + sharedSpectrumChAccess-r17 ENUMERATED {supported} OPTIONAL, +} OPTIONAL, +-- R1 23-1-1k Maximum number of configured CC lists (per UE) +unifiedJointTCI-commonUpdate-r17 INTEGER (1..4) OPTIONAL, +-- R1 23-2-1c PDCCH repetition with a single span of three contiguous OFDM symbols that is within the first four OFDM symbols in a slot +mTRP-PDCCH-singleSpan-r17 ENUMERATED {supported} OPTIONAL, +-- R1 27-23: Support of more than one activated PRS processing windows across all active DL BWPs +supportedActivatedPRS-ProcessingWindow-r17 ENUMERATED {n2, n3, n4} OPTIONAL, +cg-TimeDomainAllocationExtension-r17 ENUMERATED {supported} OPTIONAL +]], +[[ +-- R1 25-20: Propagation delay compensation based on Rel-15 TA procedure for TN and licensed +ta-BasedPDC-TN-NonSharedSpectrumChAccess-r17 ENUMERATED {supported} OPTIONAL, +-- R1 31-11: Directional Collision Handling in DC operation +directionalCollisionDC-IAB-r17 ENUMERATED {supported} OPTIONAL +]], +[[ +dummy1 ENUMERATED {supported} OPTIONAL, +dummy2 ENUMERATED {supported} OPTIONAL, +dummy3 ENUMERATED {supported} OPTIONAL, +dummy4 ENUMERATED {supported} OPTIONAL, +srs-AdditionalRepetition-r17 ENUMERATED {supported} OPTIONAL, +pusch-Repetition-CG-SDT-r17 ENUMERATED {supported} OPTIONAL +]] + +``` + +``` + +]], +[[ +multiPDSCH-PerSlotType1-CB-Support-r17 ENUMERATED {supported} OPTIONAL +]], +[[ +supportedCSI-RS-ReportSettingList-r18 SupportedCSI-RS-ReportSettingList-r18 OPTIONAL, + +-- R1 43-3: Aperiodic beam indication for access link +ncr-AperiodicBeamInd-AccessLink-r18 SEQUENCE { + scs-15kHz-r18 INTEGER (0..1) OPTIONAL, + scs-30kHz-r18 INTEGER (0..1) OPTIONAL, + scs-60kHz-r18 INTEGER (0..2) OPTIONAL, + scs-120kHz-r18 INTEGER (0..2) OPTIONAL, +} OPTIONAL, +-- R1 43-4: Semi-persistent beam indication for access link +ncr-Semi-PersistentBeamInd-AccessLink-r18 ENUMERATED {supported} OPTIONAL, +-- R1 43-5: Simultaneous UL transmission of backhaul link and C-Link +ncr-SimultaneousUL-BackhaulAndC-Link-r18 ENUMERATED {supported} OPTIONAL, +-- R1 43-6: Dedicated signalling for backhaul link beam indication +ncr-BackhaulBeamInd-r18 ENUMERATED {nonUnifiedTCI, unifiedTCI, both} OPTIONAL, +-- R1 43-8: Adaptive beam for NCR backhaul link/C-link +ncr-AdaptiveBeamBackhaulAndC-Link-r18 ENUMERATED {nonUnifiedTCI, unifiedTCI, both} OPTIONAL, + +-- R1 49-4a: Nominal RBG size of Configuration 3 for FDRA type 0 for DCI format 1_3 +nominalRBG-SizeOfConfig-3-FDRA-Type-0-DCI-1-3-r18 ENUMERATED {supported} OPTIONAL, +-- R1 49-4b: Nominal RBG size of Configuration 3 for FDRA type 0 for DCI format 0 3 +nominalRBG-SizeOfConfig-3-FDRA-Type-0-DCI-0-3-r18 ENUMERATED {supported} OPTIONAL, +-- R1 49-4c: Configurable Type-1A fields for DCI format 0_3/1_3 +configurableType-1A-FieldsForDCI-0-3-And-1-3-r18 ENUMERATED {supported} OPTIONAL, +-- R1 49-4d: FDRA Type 1 granularity of 2, 4, 8, or 16 consecutive RBs based RIV for DCI format 1_3/0_3 +fdra-Type-1-Gty-2-4-8-16-RBs-RIV-DCI-1-3-And-0-3-r18 ENUMERATED {supported} OPTIONAL, +-- R1 51-3: Support 5 MHz channel bandwidth with 20 PRB CORESET0 +support-5MHz-ChannelBW-20PRB-CORESET0-r18 ENUMERATED {supported} OPTIONAL, + +-- R1 55-1: Additional SR periodicities +additionalSR-Periodicities-r18 SEQUENCE { + scs-30kHz-r18 ENUMERATED {supported} OPTIONAL, + scs-120kHz-r18 ENUMERATED {supported} OPTIONAL, +} OPTIONAL, +-- R1 55-5: Enable MAC CE based pathloss RS updates for Type 1 CG-PUSCH +pathlossRS-UpdateForType1CG-PUSCH-r18 ENUMERATED {supported} OPTIONAL +]] +} + +Phy-ParametersCommon-v16a0 ::= SEQUENCE { + srs-PeriodicityAndOffsetExt-r16 ENUMERATED {supported} OPTIONAL +} + +Phy-ParametersXDD-Diff ::= SEQUENCE { + dynamicSFI ENUMERATED {supported} OPTIONAL, + twoPUCCH-F0-2-ConsecSymbols ENUMERATED {supported} OPTIONAL, +} + +``` + +``` + +twoDifferentTPC-Loop-PUSCH ENUMERATED {supported} OPTIONAL, +twoDifferentTPC-Loop-PUCCH ENUMERATED {supported} OPTIONAL, +... +[[ +dl-SchedulingOffset-PDSCH-TypeA ENUMERATED {supported} OPTIONAL, +dl-SchedulingOffset-PDSCH-TypeB ENUMERATED {supported} OPTIONAL, +ul-SchedulingOffset ENUMERATED {supported} OPTIONAL +]] +} + +Phy-ParametersFRX-Diff ::= + SEQUENCE { + dynamicSFI ENUMERATED {supported} OPTIONAL, + dummy1 BIT STRING (SIZE (2)) OPTIONAL, + twoFL-DMRS BIT STRING (SIZE (2)) OPTIONAL, + dummy2 BIT STRING (SIZE (2)) OPTIONAL, + dummy3 BIT STRING (SIZE (2)) OPTIONAL, + supportedDMRS-TypeDL ENUMERATED {type1, type1And2} OPTIONAL, + supportedDMRS-TypeUL ENUMERATED {type1, type1And2} OPTIONAL, + semiOpenLoopCSI ENUMERATED {supported} OPTIONAL, + csi-ReportWithoutPMI ENUMERATED {supported} OPTIONAL, + csi-ReportWithoutCQI ENUMERATED {supported} OPTIONAL, + onePortsPTRS BIT STRING (SIZE (2)) OPTIONAL, + twoPUCCH-F0-2-ConsecSymbols ENUMERATED {supported} OPTIONAL, + pucch-F2-WithFH ENUMERATED {supported} OPTIONAL, + pucch-F3-WithFH ENUMERATED {supported} OPTIONAL, + pucch-F4-WithFH ENUMERATED {supported} OPTIONAL, + pucch-F0-2WithoutFH ENUMERATED {notSupported} OPTIONAL, + pucch-F1-3-4WithoutFH ENUMERATED {notSupported} OPTIONAL, + mux-SR-HARQ-ACK-CSI-PUCCH-MultiPerSlot ENUMERATED {supported} OPTIONAL, + uci-CodeBlockSegmentation ENUMERATED {supported} OPTIONAL, + onePUCCH-LongAndShortFormat ENUMERATED {supported} OPTIONAL, + twoPUCCH-AnyOthersInSlot ENUMERATED {supported} OPTIONAL, + intraSlotFreqHopping-PUSCH ENUMERATED {supported} OPTIONAL, + pusCH-LBRM ENUMERATED {supported} OPTIONAL, + pdcch-BlindDetectionCA INTEGER (4..16) OPTIONAL, + tpc-PUSCH-RNTI ENUMERATED {supported} OPTIONAL, + tpc-PUCCH-RNTI ENUMERATED {supported} OPTIONAL, + tpc-SRS-RNTI ENUMERATED {supported} OPTIONAL, + absoluteTPC-Command ENUMERATED {supported} OPTIONAL, + twoDifferentTPC-Loop-PUSCH ENUMERATED {supported} OPTIONAL, + twoDifferentTPC-Loop-PUCCH ENUMERATED {supported} OPTIONAL, + pusCH-HalfPi-BPSK ENUMERATED {supported} OPTIONAL, + pucch-F3-4-HalfPi-BPSK ENUMERATED {supported} OPTIONAL, + almostContiguousCP-OFDM-UL ENUMERATED {supported} OPTIONAL, + sp-CSI-RS ENUMERATED {supported} OPTIONAL, + sp-CSI-IM ENUMERATED {supported} OPTIONAL, + tdd-MultiDL-UL-SwitchPerSlot ENUMERATED {supported} OPTIONAL, + multipleCORESET ENUMERATED {supported} OPTIONAL, + ... + [[ + csi-RS-IM-ReceptionForFeedback CSI-RS-IM-ReceptionForFeedback OPTIONAL, + ] + +``` + +``` + +csi-RS-ProcFrameworkForSRS CSI-RS-ProcFrameworkForSRS OPTIONAL, +csi-ReportFramework CSI-ReportFramework OPTIONAL, +mux-SR-HARQ-ACK-CSI-PUCCH-OncePerSlot SEQUENCE { + sameSymbol ENUMERATED {supported} OPTIONAL, + diffSymbol ENUMERATED {supported} OPTIONAL +} +mux-SR-HARQ-ACK-PUCCH OPTIONAL, +mux-MultipleGroupCtrlCH-Overlap ENUMERATED {supported} OPTIONAL, +dl-SchedulingOffset-PDSCH-TypeA ENUMERATED {supported} OPTIONAL, +dl-SchedulingOffset-PDSCH-TypeB ENUMERATED {supported} OPTIONAL, +ul-SchedulingOffset ENUMERATED {supported} OPTIONAL, +dl-64QAM-MCS-TableAlt ENUMERATED {supported} OPTIONAL, +ul-64QAM-MCS-TableAlt ENUMERATED {supported} OPTIONAL, +cqi-TableAlt ENUMERATED {supported} OPTIONAL, +oneFL-DMRS-TwoAdditionalDMRS-UL ENUMERATED {supported} OPTIONAL, +twoFL-DMRS-TwoAdditionalDMRS-UL ENUMERATED {supported} OPTIONAL, +oneFL-DMRS-ThreeAdditionalDMRS-UL ENUMERATED {supported} OPTIONAL +]], +[[ + pdcch-BlindDetectionNRDC SEQUENCE { + pdcch-BlindDetectionMCG-UE INTEGER (1..15), + pdcch-BlindDetectionSCG-UE INTEGER (1..15) + } +} +mux-HARQ-ACK-PUSCH-DiffSymbol ENUMERATED {supported} OPTIONAL, +]], +[[ + -- R1 11-1b: Type 1 HARQ-ACK codebook support for relative TDRA for DL + type1-HARQ-ACK-Codebook-r16 ENUMERATED {supported} OPTIONAL, + -- R1 11-8: Enhanced UL power control scheme + enhancedPowerControl-r16 ENUMERATED {supported} OPTIONAL, + -- R1 16-1b-1: TCI state activation across multiple CCs + simultaneousTCI-ActMultipleCC-r16 ENUMERATED {supported} OPTIONAL, + -- R1 16-1b-2: Spatial relation update across multiple CCs + simultaneousSpatialRelationMultipleCC-r16 ENUMERATED {supported} OPTIONAL, + cli-RSSI-FDM-DL-r16 ENUMERATED {supported} OPTIONAL, + cli-SRS-RSRP-FDM-DL-r16 ENUMERATED {supported} OPTIONAL, + -- R1 19-3: Maximum MIMO Layer Adaptation + maxLayersMIMO-Adaptation-r16 ENUMERATED {supported} OPTIONAL, + -- R1 12-5: Configuration of aggregation factor per SPS configuration + aggregationFactorSPS-DL-r16 ENUMERATED {supported} OPTIONAL, + -- R1 16-1g: Resources for beam management, pathloss measurement, BFD, RLM and new beam identification + maxTotalResourcesForOneFreqRange-r16 SEQUENCE { + maxNumberResWithinSlotAcrossCC-OneFR-r16 ENUMERATED {n2, n4, n8, n12, n16, n32, n64, n128} OPTIONAL, + maxNumberResAcrossCC-OneFR-r16 ENUMERATED {n2, n4, n8, n12, n16, n32, n40, n48, n64, n72, n80, n96, n128, n256} + OPTIONAL + } +} +OPTIONAL, +-- R1 16-7: Extension of the maximum number of configured aperiodic CSI report settings +csi-ReportFrameworkExt-r16 CSI-ReportFrameworkExt-r16 OPTIONAL, +]], +[[ + twoTCI-Act-servingCellInCC-List-r16 ENUMERATED {supported} OPTIONAL +]] + +``` + +``` + +]], +[[ +-- R1 22-11: Support of 'cri-RI-CQI' report without non-PMI-PortIndication +cri-RI-CQI-WithoutNon-PMI-PortInd-r16 ENUMERATED {supported} OPTIONAL +]], +[[ +-- R1 25-11: 4-bits subband CQI for TN and licensed +cqi-4-BitsSubbandTN-NonSharedSpectrumChAccess-r17 ENUMERATED {supported} OPTIONAL +]], +[[ +multipleCORESET-RedCap-r17 ENUMERATED {supported} OPTIONAL +]] +} + +Phy-ParametersFR1 ::= + SEQUENCE { + pdcch-MonitoringSingleOccasion ENUMERATED {supported} OPTIONAL, + scs-60kHz ENUMERATED {supported} OPTIONAL, + pdsch-256QAM-FR1 ENUMERATED {supported} OPTIONAL, + pdsch-RE-MappingFR1-PerSymbol ENUMERATED {n10, n20} OPTIONAL, + ..., + [[ + pdsch-RE-MappingFR1-PerSlot ENUMERATED {n16, n32, n48, n64, n80, n96, n112, n128, + n144, n160, n176, n192, n208, n224, n240, n256} OPTIONAL + ]], + [[ + -- R1 22-12: PDCCH monitoring with a single span of three contiguous OFDM symbols that is within the first four OFDM symbols in a + -- slot + pdcch-MonitoringSingleSpanFirst4Sym-r16 ENUMERATED {supported} OPTIONAL + ]], + [[ + -- similar to NTN R1 26-10: K1 range extension defined for ATG as well + k1-RangeExtensionATG-r18 ENUMERATED {supported} OPTIONAL, + -- similar to NTN R1 26-5: Increasing the number of HARQ processes defined for ATG as well + maxHARQ-ProcessNumberATG-r18 ENUMERATED {u16d32, u32d16, u32d32} OPTIONAL, + -- similar to NTN R1 26-1: Uplink Time and Frequency pre-compensation and timing relationship enhancements defined for ATG as well + uplinkPreCompensationATG-r18 ENUMERATED {supported} OPTIONAL + ]] + } + +Phy-ParametersFR2 ::= + SEQUENCE { + dummy ENUMERATED {supported} OPTIONAL, + pdsch-RE-MappingFR2-PerSymbol ENUMERATED {n6, n20} OPTIONAL, + ..., + [[ + pCell-FR2 ENUMERATED {supported} OPTIONAL, + pdsch-RE-MappingFR2-PerSlot ENUMERATED {n16, n32, n48, n64, n80, n96, n112, n128, + n144, n160, n176, n192, n208, n224, n240, n256} OPTIONAL + ]], + [[ + -- R1 16-1c: Support of default spatial relation and pathloss reference RS for dedicated-PUCCH/SRS and PUSCH + defaultSpatialRelationPathlossRS-r16 ENUMERATED {supported} OPTIONAL, + ]] + } + +``` + +``` + +-- R1 16-1d: Support of spatial relation update for AP-SRS via MAC CE +spatialRelationUpdateAP-SRS-r16 ENUMERATED {supported} OPTIONAL, +maxNumberSRS-PosSpatialRelationsAllServingCells-r16 ENUMERATED {n0, n1, n2, n4, n8, n16} OPTIONAL +]] +} + +-- TAG-PHY-PARAMETERS-STOP +-- ASN1STOP + +``` + +#### Phy-ParametersFRX-Diff field descriptions + +##### **csi-RS-IM-ReceptionForFeedback/ csi-RS-ProcFrameworkForSRS/ csi-ReportFramework** + +These fields are optionally present in *fr1-fr2-Add-UE-NR-Capabilities* in *UE-NR-Capability*. They shall not be set in any other instance of the IE *Phy-ParametersFRX-Diff*. If the network configures the UE with serving cells on both FR1 and FR2 bands, these parameters, if present, limit the corresponding parameters in *MIMO-ParametersPerBand*. + +#### Phy-ParametersMRDC + +The IE *Phy-ParametersMRDC* is used to convey physical layer capabilities for MR-DC. + +#### Phy-ParametersMRDC information element + +``` + +-- ASN1START +-- TAG-PHY-PARAMETERSMRDC-START + +Phy-ParametersMRDC ::= SEQUENCE { + naics-Capability-List SEQUENCE (SIZE (1..maxNrofNAICS-Entries)) OF NAICS-Capability-Entry OPTIONAL, + ... + [[ + spCellPlacement CarrierAggregationVariant OPTIONAL + ]], + [[ + -- R1 18-3b: Semi-statically configured LTE UL transmissions in all UL subframes not limited to tdm-pattern in case of TDD PCell + tdd-PCellUL-TX-AllUL-Subframe-r16 ENUMERATED {supported} OPTIONAL, + -- R1 18-3a: Semi-statically configured LTE UL transmissions in all UL subframes not limited to tdm-pattern in case of FDD PCell + fdd-PCellUL-TX-AllUL-Subframe-r16 ENUMERATED {supported} OPTIONAL + ]] +} + +NAICS-Capability-Entry ::= SEQUENCE { + numberOfNAICS-CapableCC INTEGER(1..5), + numberOfAggregatedPRB ENUMERATED {n50, n75, n100, n125, n150, n175, n200, n225, + n250, n275, n300, n350, n400, n450, n500, spare}, + ... +} + +-- TAG-PHY-PARAMETERSMRDC-STOP +-- ASN1STOP + +``` + +#### | | |----------------------------------------------| | PHY-ParametersMRDC field descriptions | |----------------------------------------------| + +##### | | |------------------------------| | naics-Capability-List | |------------------------------| + +| | +|-------------------------------------------------------------------------| +| Indicates that UE in MR-DC supports NAICS as defined in TS 36.331 [10]. | +|-------------------------------------------------------------------------| + +###### – *Phy-ParametersSharedSpectrumChAccess* + +The IE *Phy-ParametersSharedSpectrumChAccess* is used to convey the physical layer capabilities specific for shared spectrum channel access. + +#### ***Phy-ParametersSharedSpectrumChAccess* information element** + +``` +-- ASN1START +-- TAG-PHY-PARAMETERSSHARED SPECTRUM CH ACCESS-START + +Phy-ParametersSharedSpectrumChAccess-r16 ::= SEQUENCE { + -- 10-32 (1-2): SS block based SINR measurement (SS-SINR) for unlicensed spectrum + ss-SINR-Meas-r16 ENUMERATED {supported} OPTIONAL, + -- 10-33 (2-32a): Semi-persistent CSI report on PUCCH for unlicensed spectrum + sp-CSI-ReportPUCCH-r16 ENUMERATED {supported} OPTIONAL, + -- 10-33a (2-32b): Semi-persistent CSI report on PUSCH for unlicensed spectrum + sp-CSI-ReportPUSCH-r16 ENUMERATED {supported} OPTIONAL, + -- 10-34 (3-6): Dynamic SFI monitoring for unlicensed spectrum + dynamicSFI-r16 ENUMERATED {supported} OPTIONAL, + -- 10-35c (4-19c): SR/HARQ-ACK/CSI multiplexing once per slot using a PUCCH (or HARQ-ACK/CSI piggybacked on a PUSCH) when SR/HARQ- + -- ACK/CSI are supposed to be sent with different starting symbols in a slot for unlicensed spectrum + -- 10-35 (4-19): SR/HARQ-ACK/CSI multiplexing once per slot using a PUCCH (or HARQ-ACK/CSI piggybacked on a PUSCH) when SR/HARQ- + -- ACK/CSI are supposed to be sent with the same starting symbol on the PUCCH resources in a slot for unlicensed spectrum + mux-SR-HARQ-ACK-CSI-PUCCH-OncePerSlot-r16 SEQUENCE { + sameSymbol-r16 ENUMERATED {supported} OPTIONAL, + diffSymbol-r16 ENUMERATED {supported} OPTIONAL, + } + -- 10-35a (4-19a): Overlapping PUCCH resources have different starting symbols in a slot for unlicensed spectrum + mux-SR-HARQ-ACK-PUCCH-r16 ENUMERATED {supported} OPTIONAL, + -- 10-35b (4-19b): SR/HARQ-ACK/CSI multiplexing more than once per slot using a PUCCH (or HARQ-ACK/CSI piggybacked on a PUSCH) when + -- SR/HARQ ACK/CSI are supposed to be sent with the same or different starting symbol in a slot for unlicensed spectrum + mux-SR-HARQ-ACK-CSI-PUCCH-MultiPerslot-r16 ENUMERATED {supported} OPTIONAL, + -- 10-36 (4-28): HARQ-ACK multiplexing on PUSCH with different PUCCH/PUSCH starting OFDM symbols for unlicensed spectrum + mux-HARQ-ACK-PUSCH-DiffSymbol-r16 ENUMERATED {supported} OPTIONAL, + -- 10-37 (4-23): Repetitions for PUCCH format 1, 3, and 4 over multiple slots with K = 2, 4, 8 for unlicensed spectrum + pucch-Repetition-F1-3-4-r16 ENUMERATED {supported} OPTIONAL, + -- 10-38 (5-14): Type 1 configured PUSCH repetitions over multiple slots for unlicensed spectrum + type1-PUSCH-RepetitionMultiSlots-r16 ENUMERATED {supported} OPTIONAL, + -- 10-39 (5-16): Type 2 configured PUSCH repetitions over multiple slots for unlicensed spectrum + type2-PUSCH-RepetitionMultiSlots-r16 ENUMERATED {supported} OPTIONAL, + -- 10-40 (5-17): PUSCH repetitions over multiple slots for unlicensed spectrum + pusched-RepetitionMultiSlots-r16 ENUMERATED {supported} OPTIONAL, + -- 10-40a (5-17a): PDSCH repetitions over multiple slots for unlicensed spectrum +``` + +``` + +pdsch-RepetitionMultiSlots-r16 ENUMERATED {supported} OPTIONAL, +-- 10-41 (5-18): DL SPS +downlinkSPS-r16 ENUMERATED {supported} OPTIONAL, +-- 10-42 (5-19): Type 1 Configured UL grant +configuredUL-GrantType1-r16 ENUMERATED {supported} OPTIONAL, +-- 10-43 (5-20): Type 2 Configured UL grant +configuredUL-GrantType2-r16 ENUMERATED {supported} OPTIONAL, +-- 10-44 (5-21): Pre-emption indication for DL +pre-EmptIndication-DL-r16 ENUMERATED {supported} OPTIONAL, +... +} + +-- TAG-PHY-PARAMETERS SHARED SPECTRUM CH ACCESS-STOP +-- ASN1STOP + +``` + +##### – *PosSRS-RRC-Inactive-OutsideInitialUL-BWP* + +The IE *PosSRS-RRC-Inactive-OutsideInitialUL-BWP* is used to convey the capabilities supported by the UE for Positioning SRS transmission in RRC\_INACTIVE state configured outside initial UL BWP. + +#### ***PosSRS-RRC-Inactive-OutsideInitialUL-BWP* information element** + +``` + +-- ASN1START +-- TAG-POSSRS-RRC-INACTIVE-OUTSIDEINITIALUL-BWP-START + +PosSRS-RRC-Inactive-OutsideInitialUL-BWP-r17 ::= SEQUENCE { + -- R1 27-15b: Positioning SRS transmission in RRC_INACTIVE state configured outside initial UL BWP + maxSRSPosBandwidthForEachSCS-withinCC-FR1-r17 ENUMERATED {mhz5, mhz10, mhz15, mhz20, mhz25, mhz30, mhz35, mhz40, + mhz45, mhz50, mhz60, mhz70, mhz80, mhz90, mhz100} OPTIONAL, + maxSRSPosBandwidthForEachSCS-withinCC-FR2-r17 ENUMERATED {mhz50, mhz100, mhz200, mhz400} OPTIONAL, + maxNumOfSRSPosResourceSets-r17 ENUMERATED {n1, n2, n4, n8, n12, n16} OPTIONAL, + maxNumOfPeriodicSRSPosResources-r17 ENUMERATED {n1, n2, n4, n8, n16, n32, n64} OPTIONAL, + maxNumOfPeriodicSRSPosResourcesPerSlot-r17 ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10, n12, n14} OPTIONAL, + differentNumerologyBetweenSRSPosAndInitialBWP-r17 ENUMERATED {supported} OPTIONAL, + srsPosWithoutRestrictionOnBWP-r17 ENUMERATED {supported} OPTIONAL, + maxNumOfPeriodicAndSemipersistentSRSPosResources-r17 ENUMERATED {n1, n2, n4, n8, n16, n32, n64} OPTIONAL, + maxNumOfPeriodicAndSemipersistentSRSPosResourcesPerSlot-r17 ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10, n12, n14} OPTIONAL, + differentCenterFreqBetweenSRSPosAndInitialBWP-r17 ENUMERATED {supported} OPTIONAL, + switchingTimeSRS-TX-OtherTX-r17 ENUMERATED {us100, us140, us200, us300, us500} OPTIONAL, + -- R1 27-15c: Support of positioning SRS transmission in RRC_INACTIVE state outside initial BWP with semi-persistent SRS + maxNumOfSemiPersistentSRSPosResources-r17 ENUMERATED {n1, n2, n4, n8, n16, n32, n64} OPTIONAL, + maxNumOfSemiPersistentSRSPosResourcesPerSlot-r17 ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10, n12, n14} OPTIONAL, + ... +} + +-- TAG-POSSRS-RRC-INACTIVE-OUTSIDEINITIALUL-BWP-STOP +-- ASN1STOP + +``` + +#### — *PowSav-Parameters* + +The IE *PowSav-Parameters* is used to convey the capabilities supported by the UE for the power saving preferences. + +#### *PowSav-Parameters* information element + +``` +-- ASN1START +-- TAG-POWSAV-PARAMETERS-START + +PowSav-Parameters-r16 ::= SEQUENCE { + powSav-ParametersCommon-r16 PowSav-ParametersCommon-r16 OPTIONAL, + powSav-ParametersFRX-Diff-r16 PowSav-ParametersFRX-Diff-r16 OPTIONAL, + ... +} + +PowSav-Parameters-v1700 ::= SEQUENCE { + powSav-ParametersFR2-2-r17 PowSav-ParametersFR2-2-r17 OPTIONAL, + ... +} + +PowSav-ParametersCommon-r16 ::= SEQUENCE { + drx-Preference-r16 ENUMERATED {supported} OPTIONAL, + maxCC-Preference-r16 ENUMERATED {supported} OPTIONAL, + releasePreference-r16 ENUMERATED {supported} OPTIONAL, + -- R1 19-4a: UE assistance information + minSchedulingOffsetPreference-r16 ENUMERATED {supported} OPTIONAL, + ... +} + +PowSav-ParametersFRX-Diff-r16 ::= SEQUENCE { + maxBW-Preference-r16 ENUMERATED {supported} OPTIONAL, + maxMIMO-LayerPreference-r16 ENUMERATED {supported} OPTIONAL, + ... +} + +PowSav-ParametersFR2-2-r17 ::= SEQUENCE { + maxBW-Preference-r17 ENUMERATED {supported} OPTIONAL, + maxMIMO-LayerPreference-r17 ENUMERATED {supported} OPTIONAL, + ... +} + +-- TAG-POWSAV-PARAMETERS-STOP +-- ASN1STOP +``` + +#### — *ProcessingParameters* + +The IE *ProcessingParameters* is used to indicate PDSCH/PUSCH processing capabilities supported by the UE. + +#### ProcessingParameters information element + +``` +-- ASN1START +-- TAG-PROCESSINGPARAMETERS-START + +ProcessingParameters ::= SEQUENCE { + fallback ENUMERATED {sc, cap1-only}, + differentTB-PerSlot SEQUENCE { + upto1 NumberOfCarriers OPTIONAL, + upto2 NumberOfCarriers OPTIONAL, + upto4 NumberOfCarriers OPTIONAL, + upto7 NumberOfCarriers OPTIONAL + } OPTIONAL +} + +NumberOfCarriers ::= INTEGER (1..16) + +-- TAG-PROCESSINGPARAMETERS-STOP +-- ASN1STOP +``` + +#### PRS-ProcessingCapabilityOutsideMGinPPWperType + +The IE *PRS-ProcessingCapabilityOutsideMGinPPWperType* is used to indicate DL PRS Processing Capability outside MG capabilities supported by the UE. + +#### PRS-ProcessingCapabilityOutsideMGinPPWperType information element + +``` +-- ASN1START +-- TAG-PRS-PROCESSINGCAPABILITYOUTSIDEMGINPPWPERTYPE-START + +PRS-ProcessingCapabilityOutsideMGinPPWperType-r17 ::= SEQUENCE { + prsProcessingType-r17 ENUMERATED {type1A, type1B, type2}, + ppw-dl-PRS-BufferType-r17 ENUMERATED {type1, type2, ...}, + ppw-durationOfPRS-Processing-r17 CHOICE { + ppw-durationOfPRS-Processing1-r17 SEQUENCE { + ppw-durationOfPRS-ProcessingSymbolsN-r17 ENUMERATED {msDot125, msDot25, msDot5, ms1, ms2, ms4, ms6, ms8, ms12, + ms16, ms20, ms25, ms30, ms32, ms35, ms40, ms45, ms50}, + ppw-durationOfPRS-ProcessingSymbolsT-r17 ENUMERATED {ms1, ms2, ms4, ms8, ms16, ms20, ms30, ms40, ms80, + ms160, ms320, ms640, ms1280} + }, + ppw-durationOfPRS-Processing2-r17 SEQUENCE { + ppw-durationOfPRS-ProcessingSymbolsN2-r17 ENUMERATED {msDot125, msDot25, msDot5, ms1, ms2, ms3, ms4, ms5, + ms6, ms8, ms12}, + ppw-durationOfPRS-ProcessingSymbolsT2-r17 ENUMERATED {ms4, ms5, ms6, ms8} + } + } + ppw-maxNumOfDL-PRS-ResProcessedPerSlot-r17 SEQUENCE { + scs15-r17 ENUMERATED {n1, n2, n4, n6, n8, n12, n16, n24, n32, n48, n64} OPTIONAL, + scs30-r17 ENUMERATED {n1, n2, n4, n6, n8, n12, n16, n24, n32, n48, n64} OPTIONAL, + } OPTIONAL, +} +``` + +``` + + scs60-r17 ENUMERATED {n1, n2, n4, n6, n8, n12, n16, n24, n32, n48, n64} OPTIONAL, + scs120-r17 ENUMERATED {n1, n2, n4, n6, n8, n12, n16, n24, n32, n48, n64} OPTIONAL, + ... + }, + ppw-maxNumOfDL-Bandwidth-r17 CHOICE { + fr1-r17 ENUMERATED {mhz5, mhz10, mhz20, mhz40, mhz50, mhz80, mhz100}, + fr2-r17 ENUMERATED {mhz50, mhz100, mhz200, mhz400} + } +} +-- TAG-PRS-PROCESSINGCAPABILITYOUTSIDEMGINPPWPERtype-STOP +-- ASN1STOP + +``` + +#### — *RAT-Type* + +The IE *RAT-Type* is used to indicate the radio access technology (RAT), including NR, of the requested/transferred UE capabilities. + +#### *RAT-Type* information element + +``` + +-- ASN1START +-- TAG-RAT-TYPE-START + +RAT-Type ::= ENUMERATED {nr, eutra-nr, eutra, utra-fdd-v1610, ...} + +-- TAG-RAT-TYPE-STOP +-- ASN1STOP + +``` + +#### — *RedCapParameters* + +The IE *RedCapParameters* is used to indicate the UE capabilities supported by RedCap UEs. + +#### *RedCapParameters* information element + +``` + +-- ASN1START +-- TAG-REDCAPPARAMETERS-START + +RedCapParameters-r17 ::= SEQUENCE { + -- R1 28-1: RedCap UE + supportOfRedCap-r17 ENUMERATED {supported} OPTIONAL, + supportOf16DRB-RedCap-r17 ENUMERATED {supported} OPTIONAL +} + +RedCapParameters-v1740 ::= SEQUENCE { + ncd-SSB-ForRedCapInitialBWP-SDT-r17 ENUMERATED {supported} OPTIONAL +} + +``` + +-- TAG-REDCAPPARAMETERS-STOP +-- ASN1STOP + +#### — **RF-Parameters** + +The IE *RF-Parameters* is used to convey RF-related capabilities for NR operation. + +#### **RF-Parameters information element** + +``` + +-- ASN1START +-- TAG-RF-PARAMETERS-START + +RF-Parameters ::= + SEQUENCE { + supportedBandListNR + supportedBandCombinationList + appliedFreqBandListFilter + ... + [[ + supportedBandCombinationList-v1540 + srs-SwitchingTimeRequested + ]], + [[ + supportedBandCombinationList-v1550 + ]], + [[ + supportedBandCombinationList-v1560 + ]], + [[ + supportedBandCombinationList-v1610 + supportedBandCombinationListSidelinkEUTRA-NR-r16 + supportedBandCombinationList-UplinkTxSwitch-r16 + ]], + [[ + supportedBandCombinationList-v1630 + supportedBandCombinationListSidelinkEUTRA-NR-v1630 + supportedBandCombinationList-UplinkTxSwitch-v1630 + ]], + [[ + supportedBandCombinationList-v1640 + supportedBandCombinationList-UplinkTxSwitch-v1640 + ]], + [[ + supportedBandCombinationList-v1650 + supportedBandCombinationList-UplinkTxSwitch-v1650 + ]], + [[ + extendedBand-n77-r16 + ]], + [[ + SEQUENCE (SIZE (1..maxBands)) OF BandNR, + BandCombinationList + FreqBandList + OPTIONAL, + OPTIONAL, + BandCombinationList-v1540 + ENUMERATED {true} + OPTIONAL + BandCombinationList-v1550 + OPTIONAL + BandCombinationList-v1560 + OPTIONAL + BandCombinationList-v1610 + BandCombinationListSidelinkEUTRA-NR-r16 + BandCombinationList-UplinkTxSwitch-r16 + OPTIONAL, + OPTIONAL, + OPTIONAL + BandCombinationList-v1630 + BandCombinationListSidelinkEUTRA-NR-v1630 + BandCombinationList-UplinkTxSwitch-v1630 + OPTIONAL, + OPTIONAL, + OPTIONAL + BandCombinationList-v1640 + BandCombinationList-UplinkTxSwitch-v1640 + OPTIONAL, + OPTIONAL + BandCombinationList-v1650 + BandCombinationList-UplinkTxSwitch-v1650 + OPTIONAL, + OPTIONAL + ENUMERATED {supported} + OPTIONAL + ]]] + } + +``` + +``` + +supportedBandCombinationList-UplinkTxSwitch-v1670 BandCombinationList-UplinkTxSwitch-v1670 OPTIONAL +]], +[[ +supportedBandCombinationList-v1680 BandCombinationList-v1680 OPTIONAL +]], +[[ +supportedBandCombinationList-v1690 BandCombinationList-v1690 OPTIONAL, +supportedBandCombinationList-UplinkTxSwitch-v1690 BandCombinationList-UplinkTxSwitch-v1690 OPTIONAL +]], +[[ +supportedBandCombinationList-v1700 BandCombinationList-v1700 OPTIONAL, +supportedBandCombinationList-UplinkTxSwitch-v1700 BandCombinationList-UplinkTxSwitch-v1700 OPTIONAL, +supportedBandCombinationListSL-RelayDiscovery-r17 OCTET STRING OPTIONAL, -- Contains PC5 +BandCombinationListSidelinkNR-r16 +supportedBandCombinationListSL-NonRelayDiscovery-r17 OCTET STRING OPTIONAL, -- Contains PC5 +BandCombinationListSidelinkNR-r16 +supportedBandCombinationListSidelinkEUTRA-NR-v1710 BandCombinationListSidelinkEUTRA-NR-v1710 OPTIONAL, +sidelinkRequested-r17 ENUMERATED {true} OPTIONAL, +extendedBand-n77-2-r17 ENUMERATED {supported} OPTIONAL +]], +[[ +supportedBandCombinationList-v1720 BandCombinationList-v1720 OPTIONAL, +supportedBandCombinationList-UplinkTxSwitch-v1720 BandCombinationList-UplinkTxSwitch-v1720 OPTIONAL +]], +[[ +supportedBandCombinationList-v1730 BandCombinationList-v1730 OPTIONAL, +supportedBandCombinationList-UplinkTxSwitch-v1730 BandCombinationList-UplinkTxSwitch-v1730 OPTIONAL, +supportedBandCombinationListSL-RelayDiscovery-v1730 BandCombinationListSL-Discovery-r17 OPTIONAL, +supportedBandCombinationListSL-NonRelayDiscovery-v1730 BandCombinationListSL-Discovery-r17 OPTIONAL +]], +[[ +supportedBandCombinationList-v1740 BandCombinationList-v1740 OPTIONAL, +supportedBandCombinationList-UplinkTxSwitch-v1740 BandCombinationList-UplinkTxSwitch-v1740 OPTIONAL +]], +[[ +supportedBandCombinationList-v1760 BandCombinationList-v1760 OPTIONAL, +supportedBandCombinationList-UplinkTxSwitch-v1760 BandCombinationList-UplinkTxSwitch-v1760 OPTIONAL +]], +[[ +supportedBandCombinationList-v1770 BandCombinationList-v1770 OPTIONAL, +supportedBandCombinationList-UplinkTxSwitch-v1770 BandCombinationList-UplinkTxSwitch-v1770 OPTIONAL +]], +[[ +supportedBandCombinationList-v1800 BandCombinationList-v1800 OPTIONAL, +supportedBandCombinationList-UplinkTxSwitch-v1800 BandCombinationList-UplinkTxSwitch-v1800 OPTIONAL, +supportedBandCombinationListSL-U2U-Relay-r18 SEQUENCE { + supportedBandCombinationListSL-U2U-RelayDiscovery-r18 OCTET STRING OPTIONAL, -- Contains PC5 + -- BandCombinationListSidelinkNR-r16 + supportedBandCombinationListSL-U2U-DiscoveryExt BandCombinationListSL-Discovery-r17 OPTIONAL +} OPTIONAL +]] + +``` + +``` + +} + +RF-Parameters-v15g0 := + supportedBandCombinationList-v15g0 SEQUENCE { + BandCombinationList-v15g0 OPTIONAL + } + +RF-Parameters-v16a0 := + supportedBandCombinationList-v16a0 SEQUENCE { + BandCombinationList-v16a0 OPTIONAL, + supportedBandCombinationList-UplinkTxSwitch-v16a0 BandCombinationList-UplinkTxSwitch-v16a0 OPTIONAL + } + +RF-Parameters-v16c0 := + supportedBandListNR-v16c0 SEQUENCE { + SEQUENCE (SIZE (1..maxBands)) OF BandNR-v16c0 + } + +BandNR := + SEQUENCE { + bandNR FreqBandIndicatorNR, + modifiedMPR-Behaviour BIT STRING (SIZE (8)) OPTIONAL, + mimo-ParametersPerBand MIMO-ParametersPerBand OPTIONAL, + extendedCP ENUMERATED {supported} OPTIONAL, + multipleTCI ENUMERATED {supported} OPTIONAL, + bwp-WithoutRestriction ENUMERATED {supported} OPTIONAL, + bwp-SameNumerology ENUMERATED {upto2, upto4} OPTIONAL, + bwp-DiffNumerology ENUMERATED {upto4} OPTIONAL, + crossCarrierScheduling-SameSCS ENUMERATED {supported} OPTIONAL, + pdsch-256QAM-FR2 ENUMERATED {supported} OPTIONAL, + puscb-256QAM ENUMERATED {supported} OPTIONAL, + ue-PowerClass ENUMERATED {pc1, pc2, pc3, pc4} OPTIONAL, + rateMatchingLTE-CRS ENUMERATED {supported} OPTIONAL, + channelBWs-DL CHOICE { + fr1 SEQUENCE { + scs-15kHz BIT STRING (SIZE (10)) OPTIONAL, + scs-30kHz BIT STRING (SIZE (10)) OPTIONAL, + scs-60kHz BIT STRING (SIZE (10)) OPTIONAL + }, + fr2 SEQUENCE { + scs-60kHz BIT STRING (SIZE (3)) OPTIONAL, + scs-120kHz BIT STRING (SIZE (3)) OPTIONAL + } + } OPTIONAL, + channelBWs-UL CHOICE { + fr1 SEQUENCE { + scs-15kHz BIT STRING (SIZE (10)) OPTIONAL, + scs-30kHz BIT STRING (SIZE (10)) OPTIONAL, + scs-60kHz BIT STRING (SIZE (10)) OPTIONAL + }, + fr2 SEQUENCE { + scs-60kHz BIT STRING (SIZE (3)) OPTIONAL, + scs-120kHz BIT STRING (SIZE (3)) OPTIONAL + } + } OPTIONAL, + } + +``` + +``` + +... +[[ +maxUplinkDutyCycle-PC2-FR1 ENUMERATED {n60, n70, n80, n90, n100} OPTIONAL +]], +[[ +pucch-SpatialRelInfoMAC-CE ENUMERATED {supported} OPTIONAL, +powerBoosting-pi2BPSK ENUMERATED {supported} OPTIONAL +]], +[[ +maxUplinkDutyCycle-FR2 ENUMERATED {n15, n20, n25, n30, n40, n50, n60, n70, n80, n90, n100} OPTIONAL +]], +[[ +channelBWs-DL-v1590 CHOICE { + fr1 SEQUENCE { + scs-15kHz BIT STRING (SIZE (16)) OPTIONAL, + scs-30kHz BIT STRING (SIZE (16)) OPTIONAL, + scs-60kHz BIT STRING (SIZE (16)) OPTIONAL + }, + fr2 SEQUENCE { + scs-60kHz BIT STRING (SIZE (8)) OPTIONAL, + scs-120kHz BIT STRING (SIZE (8)) OPTIONAL + } +} OPTIONAL, +channelBWs-UL-v1590 CHOICE { + fr1 SEQUENCE { + scs-15kHz BIT STRING (SIZE (16)) OPTIONAL, + scs-30kHz BIT STRING (SIZE (16)) OPTIONAL, + scs-60kHz BIT STRING (SIZE (16)) OPTIONAL + }, + fr2 SEQUENCE { + scs-60kHz BIT STRING (SIZE (8)) OPTIONAL, + scs-120kHz BIT STRING (SIZE (8)) OPTIONAL + } +} OPTIONAL +]], +[[ +asymmetricBandwidthCombinationSet BIT STRING (SIZE (1..32)) OPTIONAL +]], +[[ +-- R1 10: NR-unlicensed +sharedSpectrumChAccessParamsPerBand-r16 SharedSpectrumChAccessParamsPerBand-r16 OPTIONAL, +-- R1 11-7b: Independent cancellation of the overlapping PUSCHs in an intra-band UL CA +cancelOverlappingPUSCH-r16 ENUMERATED {supported} OPTIONAL, +-- R1 14-1: Multiple LTE-CRS rate matching patterns +multipleRateMatchingEUTRA-CRS-r16 SEQUENCE { + maxNumberPatterns-r16 INTEGER (2..6), + maxNumberNon-OverlapPatterns-r16 INTEGER (1..3) +} OPTIONAL, +-- R1 14-1a: Two LTE-CRS overlapping rate matching patterns within a part of NR carrier using 15 kHz overlapping with a LTE carrier +overlapRateMatchingEUTRA-CRS-r16 ENUMERATED {supported} OPTIONAL, +-- R1 14-2: PDSCH Type B mapping of length 9 and 10 OFDM symbols + +``` + +``` + +pdsch-MappingTypeB-Alt-r16 ENUMERATED {supported} OPTIONAL, +-- R1 14-3: One slot periodic TRS configuration for FR1 +oneSlotPeriodicTRS-r16 ENUMERATED {supported} OPTIONAL, +olpc-SRS-Pos-r16 OLPC-SRS-Pos-r16 OPTIONAL, +spatialRelationsSRS-Pos-r16 SpatialRelationsSRS-Pos-r16 OPTIONAL, +simulSRS-MIMO-TransWithinBand-r16 ENUMERATED {n2} OPTIONAL, +channelBW-DL-IAB-r16 CHOICE { + fr1-100mhz SEQUENCE { + scs-15kHz ENUMERATED {supported} OPTIONAL, + scs-30kHz ENUMERATED {supported} OPTIONAL, + scs-60kHz ENUMERATED {supported} OPTIONAL, + }, + fr2-200mhz SEQUENCE { + scs-60kHz ENUMERATED {supported} OPTIONAL, + scs-120kHz ENUMERATED {supported} OPTIONAL, + } +} OPTIONAL, +channelBW-UL-IAB-r16 CHOICE { + fr1-100mhz SEQUENCE { + scs-15kHz ENUMERATED {supported} OPTIONAL, + scs-30kHz ENUMERATED {supported} OPTIONAL, + scs-60kHz ENUMERATED {supported} OPTIONAL, + }, + fr2-200mhz SEQUENCE { + scs-60kHz ENUMERATED {supported} OPTIONAL, + scs-120kHz ENUMERATED {supported} OPTIONAL, + } +} OPTIONAL, +rasterShift7dot5-IAB-r16 ENUMERATED {supported} OPTIONAL, +ue-PowerClass-v1610 ENUMERATED {pcldot5} OPTIONAL, +condHandover-r16 ENUMERATED {supported} OPTIONAL, +condHandoverFailure-r16 ENUMERATED {supported} OPTIONAL, +condHandoverTwoTriggerEvents-r16 ENUMERATED {supported} OPTIONAL, +condPSCellChange-r16 ENUMERATED {supported} OPTIONAL, +condPSCellChangeTwoTriggerEvents-r16 ENUMERATED {supported} OPTIONAL, +mpr-PowerBoost-FR2-r16 ENUMERATED {supported} OPTIONAL, + +-- R1 11-9: Multiple active configured grant configurations for a BWP of a serving cell +activeConfiguredGrant-r16 SEQUENCE { +maxNumberConfigsPerBWP-r16 ENUMERATED {n1, n2, n4, n8, n12}, +maxNumberConfigsAllCC-r16 INTEGER (2..32) +} OPTIONAL, +-- R1 11-9a: Joint release in a DCI for two or more configured grant Type 2 configurations for a given BWP of a serving cell +jointReleaseConfiguredGrantType2-r16 ENUMERATED {supported} OPTIONAL, +-- R1 12-2: Multiple SPS configurations +sps-r16 SEQUENCE { +maxNumberConfigsPerBWP-r16 INTEGER (1..8), +maxNumberConfigsAllCC-r16 INTEGER (2..32) +} OPTIONAL, +-- R1 12-2a: Joint release in a DCI for two or more SPS configurations for a given BWP of a serving cell +jointReleaseSPS-r16 ENUMERATED {supported} OPTIONAL, + +``` + +``` + +-- R1 13-19: Simultaneous positioning SRS and MIMO SRS transmission within a band across multiple CCs +simulSRS-TransWithinBand-r16 ENUMERATED {n2} OPTIONAL, +trs-AdditionalBandwidth-r16 ENUMERATED {trs-AddBW-Set1, trs-AddBW-Set2} OPTIONAL, +handoverIntraF-IAB-r16 ENUMERATED {supported} OPTIONAL +]], +[[ +-- R1 22-5a: Simultaneous transmission of SRS for antenna switching and SRS for CB/NCB /BM for intra-band UL CA +-- R1 22-5c: Simultaneous transmission of SRS for antenna switching and SRS for antenna switching for intra-band UL CA +simulTX-SRS-AntSwitchingIntraBandUL-CA-r16 SimulSRS-ForAntennaSwitching-r16 OPTIONAL, +-- R1 10: NR-unlicensed +sharedSpectrumChAccessParamsPerBand-v1630 SharedSpectrumChAccessParamsPerBand-v1630 OPTIONAL +]], +[[ +handoverUTRA-FDD-r16 ENUMERATED {supported} OPTIONAL, +-- R4 7-4: Report the shorter transient capability supported by the UE: 2, 4 or 7us +enhancedUL-TransientPeriod-r16 ENUMERATED {us2, us4, us7} OPTIONAL, +sharedSpectrumChAccessParamsPerBand-v1640 SharedSpectrumChAccessParamsPerBand-v1640 OPTIONAL +]], +[[ +type1-PUSCH-RepetitionMultiSlots-v1650 ENUMERATED {supported} OPTIONAL, +type2-PUSCH-RepetitionMultiSlots-v1650 ENUMERATED {supported} OPTIONAL, +pusch-RepetitionMultiSlots-v1650 ENUMERATED {supported} OPTIONAL, +configuredUL-GrantType1-v1650 ENUMERATED {supported} OPTIONAL, +configuredUL-GrantType2-v1650 ENUMERATED {supported} OPTIONAL, +sharedSpectrumChAccessParamsPerBand-v1650 SharedSpectrumChAccessParamsPerBand-v1650 OPTIONAL +]], +[[ +enhancedSkipUplinkTxConfigured-v1660 ENUMERATED {supported} OPTIONAL, +enhancedSkipUplinkTxDynamic-v1660 ENUMERATED {supported} OPTIONAL +]], +[[ +maxUplinkDutyCycle-PC1dot5-MPE-FR1-r16 ENUMERATED {n10, n15, n20, n25, n30, n40, n50, n60, n70, n80, n90, n100} OPTIONAL, +txDiversity-r16 ENUMERATED {supported} OPTIONAL +]], +[[ +-- R1 36-1: Support of 1024QAM for PDSCH for FR1 +pdsch-1024QAM-FR1-r17 ENUMERATED {supported} OPTIONAL, +-- R4 22-1 support of FR2 HST operation +ue-PowerClass-v1700 ENUMERATED {pc5, pc6, pc7} OPTIONAL, +-- R1 24: NR extension to 71GHz (FR2-2) +fr2-2-AccessParamsPerBand-r17 FR2-2-AccessParamsPerBand-r17 OPTIONAL, +rlm-Relaxation-r17 ENUMERATED {supported} OPTIONAL, +bfd-Relaxation-r17 ENUMERATED {supported} OPTIONAL, +cg-SDT-r17 ENUMERATED {supported} OPTIONAL, +locationBasedCondHandover-r17 ENUMERATED {supported} OPTIONAL, +timeBasedCondHandover-r17 ENUMERATED {supported} OPTIONAL, +eventA4BasedCondHandover-r17 ENUMERATED {supported} OPTIONAL, +mn-InitiatedCondPSCellChangeNRDC-r17 ENUMERATED {supported} OPTIONAL, +sn-InitiatedCondPSCellChangeNRDC-r17 ENUMERATED {supported} OPTIONAL, +-- R1 29-3a: PDCCH skipping +pdcch-SkippingWithoutSSSG-r17 ENUMERATED {supported} OPTIONAL, + +``` + +``` + +-- R1 29-3b: 2 search space sets group switching +sssg-Switching-1BitInd-r17 ENUMERATED {supported} OPTIONAL, +-- R1 29-3c: 3 search space sets group switching +sssg-Switching-2BitInd-r17 ENUMERATED {supported} OPTIONAL, +-- R1 29-3d: 2 search space sets group switching with PDCCH skipping +pdcch-SkippingWithSSSG-r17 ENUMERATED {supported} OPTIONAL, +-- R1 29-3e: Support Search space set group switching capability 2 for FR1 +searchSpaceSetGrp-switchCap2-r17 ENUMERATED {supported} OPTIONAL, +-- R1 26-1: Uplink Time and Frequency pre-compensation and timing relationship enhancements +uplinkPreCompensation-r17 ENUMERATED {supported} OPTIONAL, +-- R1 26-4: UE reporting of information related to TA pre-compensation +uplink-TA-Reporting-r17 ENUMERATED {supported} OPTIONAL, +-- R1 26-5: Increasing the number of HARQ processes +max-HARQ-ProcessNumber-r17 ENUMERATED {u16d32, u32d16, u32d32} OPTIONAL, +-- R1 26-6: Type-2 HARQ codebook enhancement +type2-HARQ-Codebook-r17 ENUMERATED {supported} OPTIONAL, +-- R1 26-6a: Type-1 HARQ codebook enhancement +type1-HARQ-Codebook-r17 ENUMERATED {supported} OPTIONAL, +-- R1 26-6b: Type-3 HARQ codebook enhancement +type3-HARQ-Codebook-r17 ENUMERATED {supported} OPTIONAL, +-- R1 26-9: UE-specific K offset +ue-specific-K-Offset-r17 ENUMERATED {supported} OPTIONAL, +-- R1 24-1f: Multiple PDSCH scheduling by single DCI for 120kHz in FR2-1 +multiPDSCH-SingleDCI-FR2-1-SCS-120kHz-r17 ENUMERATED {supported} OPTIONAL, +-- R1 24-1g: Multiple PUSCH scheduling by single DCI for 120kHz in FR2-1 +multiPUSCH-SingleDCI-FR2-1-SCS-120kHz-r17 ENUMERATED {supported} OPTIONAL, +-- R4 14-4: Parallel PRS measurements in RRC_INACTIVE state, FR1/FR2 diff +parallelPRS-MeasRRC-Inactive-r17 ENUMERATED {supported} OPTIONAL, +-- R1 27-1-2: Support of UE-TxTEGs for UL TDOA +nr-UE-TxTEG-ID-MaxSupport-r17 ENUMERATED {n1, n2, n3, n4, n6, n8} OPTIONAL, +-- R1 27-17: PRS processing in RRC_INACTIVE +prs-ProcessingRRC-Inactive-r17 ENUMERATED {supported} OPTIONAL, +-- R1 27-3-2: DL PRS measurement outside MG and in a PRS processing window +prs-ProcessingWindowType1A-r17 ENUMERATED {option1, option2, option3} OPTIONAL, +prs-ProcessingWindowType1B-r17 ENUMERATED {option1, option2, option3} OPTIONAL, +prs-ProcessingWindowType2-r17 ENUMERATED {option1, option2, option3} OPTIONAL, +-- R1 27-15: Positioning SRS transmission in RRC_INACTIVE state for initial UL BWP +srs-AllPosResourcesRRC-Inactive-r17 SRS-AllPosResourcesRRC-Inactive-r17 OPTIONAL, +-- R1 27-16: OLPC for positioning SRS in RRC_INACTIVE state - gNB +olpc-SRS-PosRRC-Inactive-r17 OLPC-SRS-Pos-r16 OPTIONAL, +-- R1 27-19: Spatial relation for positioning SRS in RRC_INACTIVE state - gNB +spatialRelationsSRS-PosRRC-Inactive-r17 SpatialRelationsSRS-Pos-r16 OPTIONAL, +-- R1 30-1: Increased maximum number of PUSCH Type A repetitions +maxNumberPUSCH-TypeA-Repetition-r17 ENUMERATED {supported} OPTIONAL, +-- R1 30-2: PUSCH Type A repetitions based on available slots +puschTypeA-RepetitionsAvailSlot-r17 ENUMERATED {supported} OPTIONAL, +-- R1 30-3: TB processing over multi-slot PUSCH +tb-ProcessingMultiSlotPUSCH-r17 ENUMERATED {supported} OPTIONAL, +-- R1 30-3a: Repetition of TB processing over multi-slot PUSCH +tb-ProcessingRepMultiSlotPUSCH-r17 ENUMERATED {supported} OPTIONAL, +-- R1 30-4: The maximum duration for DM-RS bundling + +``` + +``` + +maxDurationDMRS-Bundling-r17 SEQUENCE { + fdd-r17 ENUMERATED {n4, n8, n16, n32} OPTIONAL, + tdd-r17 ENUMERATED {n2, n4, n8, n16} OPTIONAL, +} OPTIONAL, +-- R1 30-6: Repetition of PUSCH transmission scheduled by RAR UL grant and DCI format 0_0 with CRC scrambled by TC-RNTI +pusch-RepetitionMsg3-r17 ENUMERATED {supported} OPTIONAL, +sharedSpectrumChAccessParamsPerBand-v1710 SharedSpectrumChAccessParamsPerBand-v1710 OPTIONAL, +-- R4 25-2: Parallel measurements on cells belonging to a different NGSO satellite than a serving satellite without scheduling restrictions +-- on normal operations with the serving cell +parallelMeasurementWithoutRestriction-r17 ENUMERATED {supported} OPTIONAL, +-- R4 25-5: Parallel measurements on multiple NGSO satellites within a SMTC +maxNumber-NGSO-SatellitesWithinOneSMTC-r17 ENUMERATED {n1, n2, n3, n4} OPTIONAL, +-- R1 26-10: K1 range extension +k1-RangeExtension-r17 ENUMERATED {supported} OPTIONAL, +-- R1 35-1: Aperiodic CSI-RS for tracking for fast SCell activation +aperiodicCSI-RS-FastSCellActivation-r17 SEQUENCE { + maxNumberAperiodicCSI-RS-PerCC-r17 ENUMERATED {n8, n16, n32, n48, n64, n128, n255}, + maxNumberAperiodicCSI-RS-AcrossCCs-r17 ENUMERATED {n8, n16, n32, n64, n128, n256, n512, n1024} +} OPTIONAL, +-- R1 35-2: Aperiodic CSI-RS bandwidth for tracking for fast SCell activation for 10MHz UE channel bandwidth +aperiodicCSI-RS-AdditionalBandwidth-r17 ENUMERATED {addBW-Set1, addBW-Set2} OPTIONAL, +-- R1 28-1a: RRC-configured DL BWP without CD-SSB or NCD-SSB +bwp-WithoutCD-SSB-OrNCD-SSB-RedCap-r17 ENUMERATED {supported} OPTIONAL, +-- R1 28-3: Half-duplex FDD operation type A for (e)RedCap UE +halfDuplexFDD-TypeA-RedCap-r17 ENUMERATED {supported} OPTIONAL, +-- R1 27-15b: Positioning SRS transmission in RRC INACTIVE state configured outside initial UL BWP +posSRS-RRC-Inactive-OutsideInitialUL-BWP-r17 PosSRS-RRC-Inactive-OutsideInitialUL-BWP-r17 OPTIONAL, +-- R4 15-3 UE support of CBW for 480kHz SCS +channelBWs-DL-SCS-480kHz-FR2-2-r17 BIT STRING (SIZE (8)) OPTIONAL, +channelBWs-UL-SCS-480kHz-FR2-2-r17 BIT STRING (SIZE (8)) OPTIONAL, +-- R4 15-4 UE support of CBW for 960kHz SCS +channelBWs-DL-SCS-960kHz-FR2-2-r17 BIT STRING (SIZE (8)) OPTIONAL, +channelBWs-UL-SCS-960kHz-FR2-2-r17 BIT STRING (SIZE (8)) OPTIONAL, +-- R4 17-1 UL gap for Tx power management +ul-GapFR2-r17 ENUMERATED {supported} OPTIONAL, +-- R1 25-4: One-shot HARQ ACK feedback triggered by DCI format 1_2 +oneShotHARQ-feedbackTriggeredByDCI-1-2-r17 ENUMERATED {supported} OPTIONAL, +-- R1 25-5: PHY priority handling for one-shot HARQ ACK feedback +oneShotHARQ-feedbackPhy-Priority-r17 ENUMERATED {supported} OPTIONAL, +-- R1 25-6: Enhanced type 3 HARQ-ACK codebook feedback +enhancedType3-HARQ-CodebookFeedback-r17 SEQUENCE { + enhancedType3-HARQ-Codebooks-r17 ENUMERATED {n1, n2, n4, n8}, + maxNumberPUCCH-Transmissions-r17 ENUMERATED {n1, n2, n3, n4, n5, n6, n7} +} OPTIONAL, +-- R1 25-7: Triggered HARQ-ACK codebook re-transmission +triggeredHARQ-CodebookRetx-r17 SEQUENCE { + minHARQ-Retx-Offset-r17 ENUMERATED {n-7, n-5, n-3, n-1, n1}, + maxHARQ-Retx-Offset-r17 ENUMERATED {n4, n6, n8, n10, n12, n14, n16, n18, n20, n22, n24} +} OPTIONAL +]], +[[ + +``` + +``` + +-- R4 22-2 support of one shot large UL timing adjustment +ue-OneShotUL-TimingAdj-r17 ENUMERATED {supported} OPTIONAL, +-- R1 25-2: Repetitions for PUCCH format 0, and 2 over multiple slots with K = 2, 4, 8 +pucch-Repetition-F0-2-r17 ENUMERATED {supported} OPTIONAL, +-- R1 25-11a: 4-bits subband CQI for NTN and unlicensed +cqi-4-BitsSubbandNTN-SharedSpectrumChAccess-r17 ENUMERATED {supported} OPTIONAL, +-- R1 25-16: HARQ-ACK with different priorities multiplexing on a PUCCH/PUSCH +mux-HARQ-ACK-DiffPriorities-r17 ENUMERATED {supported} OPTIONAL, +-- R1 25-20a: Propagation delay compensation based on Rel-15 TA procedure for NTN and unlicensed +ta-BasedPDC-NTN-SharedSpectrumChAccess-r17 ENUMERATED {supported} OPTIONAL, +-- R1 33-2b: DCI-based enabling/disabling ACK/NACK-based feedback for dynamic scheduling for multicast +ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17 ENUMERATED {supported} OPTIONAL, +-- R1 33-2e: Multiple G-RNTIs for group-common PDSCHs +maxNumberG-RNTI-r17 INTEGER (2..8) OPTIONAL, +-- R1 33-2f: Dynamic multicast with DCI format 4_2 +dynamicMulticastDCI-Format4-2-r17 ENUMERATED {supported} OPTIONAL, +-- R1 33-2i: Supported maximal modulation order for multicast PDSCH +maxModulationOrderForMulticast-r17 CHOICE { + fr1-r17 ENUMERATED {gam256, gam1024}, + fr2-r17 ENUMERATED {gam64, gam256} +} OPTIONAL, +-- R1 33-3-1: Dynamic Slot-level repetition for group-common PDSCH for TN and licensed +dynamicSlotRepetitionMulticastTN-NonSharedSpectrumChAccess-r17 ENUMERATED {n8, n16} OPTIONAL, +-- R1 33-3-1a: Dynamic Slot-level repetition for group-common PDSCH for NTN and unlicensed +dynamicSlotRepetitionMulticastNTN-SharedSpectrumChAccess-r17 ENUMERATED {n8, n16} OPTIONAL, +-- R1 33-4-1: DCI-based enabling/disabling NACK-only based feedback for dynamic scheduling for multicast +nack-OnlyFeedbackForMulticastWithDCI-Enabler-r17 ENUMERATED {supported} OPTIONAL, +-- R1 33-5-1b: DCI-based enabling/disabling ACK/NACK-based feedback for dynamic scheduling for multicast +ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17 ENUMERATED {supported} OPTIONAL, +-- R1 33-5-1h: Multiple G-CS-RNTIs for SPS group-common PDSCHs +maxNumberG-CS-RNTI-r17 INTEGER (2..8) OPTIONAL, +-- R1 33-10: Support group-common PDSCH RE-level rate matching for multicast +re-LevelRateMatchingForMulticast-r17 ENUMERATED {supported} OPTIONAL, +-- R1 36-1a: Support of 1024QAM for PDSCH with maximum 2 MIMO layers for FR1 +pdsch-1024QAM-2MIMO-FR1-r17 ENUMERATED {supported} OPTIONAL, +-- R4 14-3 PRS measurement without MG +prs-MeasurementWithoutMG-r17 ENUMERATED {cpLength, quarterSymbol, halfSymbol, halfSlot} OPTIONAL, +-- R4 25-7: The number of target LEO satellites the UE can monitor per carrier +maxNumber-LEO-SatellitesPerCarrier-r17 INTEGER (3..4) OPTIONAL, +-- R1 27-3-3 DL PRS Processing Capability outside MG - buffering capability +prs-ProcessingCapabilityOutsideMGinPPW-r17 SEQUENCE (SIZE(1..3)) OF PRS-ProcessingCapabilityOutsideMGinPPWperType-r17 OPTIONAL, +-- R1 27-15a: Positioning SRS transmission in RRC INACTIVE state for initial UL BWP with semi-persistent SRS +srs-SemiPersistent-PosResourcesRRC-Inactive-r17 SEQUENCE { + maxNumOfSemiPersistentSRSposResources-r17 ENUMERATED {n1, n2, n4, n8, n16, n32, n64}, + maxNumOfSemiPersistentSRSposResourcesPerSlot-r17 ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10, n12, n14} +} OPTIONAL, +-- R2: UE support of CBW for 120kHz SCS +channelBWs-DL-SCS-120kHz-FR2-2-r17 BIT STRING (SIZE (8)) OPTIONAL, +channelBWs-UL-SCS-120kHz-FR2-2-r17 BIT STRING (SIZE (8)) OPTIONAL, +]], +[[ + +``` + +``` + +-- R1 30-4a: DM-RS bundling for PUSCH repetition type A +dmrs-BundlingPUSCH-RepTypeA-r17 ENUMERATED {supported} OPTIONAL, +-- R1 30-4b: DM-RS bundling for PUSCH repetition type B +dmrs-BundlingPUSCH-RepTypeB-r17 ENUMERATED {supported} OPTIONAL, +-- R1 30-4c: DM-RS bundling for TB processing over multi-slot PUSCH +dmrs-BundlingPUSCH-multiSlot-r17 ENUMERATED {supported} OPTIONAL, +-- R1 30-4d: DMRS bundling for PUCCH repetitions +dmrs-BundlingPUCCH-Rep-r17 ENUMERATED {supported} OPTIONAL, +-- R1 30-4e: Enhanced inter-slot frequency hopping with inter-slot bundling for PUSCH +interSlotFreqHopInterSlotBundlingPUSCH-r17 ENUMERATED {supported} OPTIONAL, +-- R1 30-4f: Enhanced inter-slot frequency hopping for PUCCH repetitions with DMRS bundling +interSlotFreqHopPUCCH-r17 ENUMERATED {supported} OPTIONAL, +-- R1 30-4g: Restart DM-RS bundling +dmrs-BundlingRestart-r17 ENUMERATED {supported} OPTIONAL, +-- R1 30-4h: DM-RS bundling for non-back-to-back transmission +dmrs-BundlingNonBackToBackTX-r17 ENUMERATED {supported} OPTIONAL +], +[[ +-- R1 33-5-1e: Dynamic Slot-level repetition for SPS group-common PDSCH for multicast +maxDynamicSlotRepetitionForSPS-Multicast-r17 ENUMERATED {n8, n16} OPTIONAL, +-- R1 33-5-1g: DCI-based enabling/disabling NACK-only based feedback for SPS group-common PDSCH for multicast +nack-OnlyFeedbackForSPS-MulticastWithDCI-Enabler-r17 ENUMERATED {supported} OPTIONAL, +-- R1 33-5-1i: Multicast SPS scheduling with DCI format 4_2 +sps-MulticastDCI-Format4-2-r17 ENUMERATED {supported} OPTIONAL, +-- R1 33-5-2: Multiple SPS group-common PDSCH configuration on PCell +sps-MulticastMultiConfig-r17 INTEGER (1..8) OPTIONAL, +-- R1 33-6-1: DL priority indication for multicast in DCI + +``` + +``` + +priorityIndicatorInDCI-Multicast-r17 ENUMERATED {supported} OPTIONAL, +-- R1 33-6-1a: DL priority configuration for SPS multicast +priorityIndicatorInDCI-SPS-Multicast-r17 ENUMERATED {supported} OPTIONAL, +-- R1 33-6-2: Two HARQ-ACK codebooks simultaneously constructed for supporting HARQ-ACK codebooks with different priorities +-- for unicast and multicast at a UE +twoHARQ-ACK-CodebookForUnicastAndMulticast-r17 ENUMERATED {supported} OPTIONAL, +-- R1 33-6-3: More than one PUCCH for HARQ-ACK transmission for multicast or for unicast and multicast within a slot +multiPUCCH-HARQ-ACK-ForMulticastUnicast-r17 ENUMERATED {supported} OPTIONAL, +-- R1 33-9: Supporting unicast PDCCH to release SPS group-common PDSCH +releaseSPS-MulticastWithCS-RNTI-r17 ENUMERATED {supported} OPTIONAL +]], +[[ +-- R1 41-3-1a UE autonomous TA adjustment when cell-reselection happens +posUE-TA-AutoAdjustment-r18 ENUMERATED {supported} OPTIONAL, +-- R1 41-4-6a support a Rel-17 single DCI scheduling positioning SRS resource sets across the linked carriers +-- for SRS bandwidth aggregation in RRC_CONNECTED state +posJointTriggerBySingleDCI-RRc-Connected-r18 ENUMERATED {supported} OPTIONAL, +-- R1 41-5-1a PRS measurement with Rx frequency hopping in RRC_INACTIVE for RedCap UEs +dl-PRS-MeasurementWithRxFH-RRc-InactiveforRedCap-r18 ENUMERATED {supported} OPTIONAL, +-- R1 41-5-1b PRS measurement with Rx frequency hopping in RRC_IDLE for RedCap UEs +dl-PRS-MeasurementWithRxFH-RRc-IdleforRedCap-r18 ENUMERATED {supported} OPTIONAL, +-- R1 42-4: Cell DTX and/or DRX operation based on RRC configuration +nes-CellDTX-DRX-r18 ENUMERATED {cellDTXonly, cellDRXonly, both} OPTIONAL, +-- R1 42-5: Cell DTX/DRX operation triggered by DCI format 2_9 +nes-CellDTX-DRX-DCI2-9-r18 ENUMERATED {supported} OPTIONAL, + +-- R1 45-6: UE-based TA measurement +ue-TA-Measurement-r18 INTEGER (1..8) OPTIONAL, +-- R1 45-7: TA indication in cell switch command +ta-IndicationCellSwitch-r18 ENUMERATED {supported} OPTIONAL, + +-- R1 50-1: Multi-PUSCHs for Configured Grant +multiPUSCH-CG-r18 ENUMERATED {n16, n32} OPTIONAL, +-- R1 50-1a: Multiple active multi-PUSCHs configured grant configurations for a BWP of a serving cell +multiPUSCH-ActiveConfiguredGrant-r18 SEQUENCE { + maxNumberConfigsPerBWP ENUMERATED {n1, n2, n4, n8, n12}, + maxNumberConfigsAllCC-FR1 INTEGER (2..32), + maxNumberConfigsAllCC-FR2 INTEGER (2..32) +} OPTIONAL, +-- R1 50-2: UCI indication of unused CG-PUSCH transmission occasions +cg-PUSCH-UTO-UCI-Ind-r18 ENUMERATED {supported} OPTIONAL, +-- R1 50-3: PDCCH monitoring resumption after UL NACK +pdcch-MonitoringResumptionAfterUL-NACK-r18 ENUMERATED {supported} OPTIONAL, + +-- R1 51-1: support for 3MHz channel bandwidth +support-3MHz-ChannelBW-r18 ENUMERATED {supported} OPTIONAL, +-- R1 51-2: support 12 PRB CORESET0 +support-12PRB-CORESET0-r18 ENUMERATED {supported} OPTIONAL, + +-- R1 52-1: Reception of NR PDCCH candidates overlapping with LTE CRS REs +nr-PDCCH-OverlapLTE-CRS-RE-r18 SEQUENCE { + +``` + +``` + + overlapInRE-r18 ENUMERATED {oneSymbolNoOverlap, someOrAllSymOverlap}, + overlapInSymbol-r18 ENUMERATED {symbol12, symbol1And2} +} OPTIONAL, +-- Editor's Note: someOrAllSymOverlap considers to be supported in overlapInRE-r18 only if RAN4 performance requirements for +-- someOrAllSymOverlap are not defined +-- R1 52-1a: Reception of NR PDCCH candidates overlapping with LTE CRS REs with multiple non-overlapping CRS rate matching patterns +nr-PDCCH-OverlapLTE-CRS-RE-MultiPatterns-r18 ENUMERATED {supported} OPTIONAL, +-- R1 52-1b: NR PDCCH reception that overlaps with LTE CRS within a single span of 3 consecutive OFDM symbols that is within the +-- first 4 OFDM symbols in a slot +nr-PDCCH-OverlapLTE-CRS-RE-Span-3-4-r18 ENUMERATED {supported} OPTIONAL, +-- R1 52-2: Two LTE-CRS overlapping rate matching patterns within NR 15 kHz carrier overlapping with LTE carrier (regardless of +-- support or configuration of multi-TRP) +twoRateMatchingEUTRA-CRS-patterns-3-4-r18 SEQUENCE { + maxNumberPatterns-r18 INTEGER (2..6), + maxNumberNon-OverlapPatterns-r18 INTEGER (1..3) +} OPTIONAL, +-- R1 52-2a: Two LTE-CRS overlapping rate matching patterns with two different values of coresetPoolIndex within NR 15 kHz carrier +-- overlapping with LTE carrier +overlapRateMatchingEUTRA-CRS-Patterns-3-4-Diff-CS-Pool-r18 ENUMERATED {supported} OPTIONAL, + +-- R1 53-3: Support RLM/BM/BFD measurements based on NCD-SSB within active BWP +ncd-SSB-BWP-Wor-r18 ENUMERATED {supported} OPTIONAL, +-- R1 53-4: Support Support RLM/BM/BFD measurements based on CSI-RS when CD-SSB is outside active BWP +rlm-BM-BFD-CSI-RS-OutsideActiveBWP-r18 ENUMERATED {supported} OPTIONAL, + +-- R1 55-3: Multiple PUSCHs scheduling by single DCI for non-consecutive slots in FR1 +multiPUSCH-SingleDCI-NonConsSlots-r18 ENUMERATED {supported} OPTIONAL, +-- R1 55-2d: single-symbol DL-PRS used in RTT-based Propagation delay compensation +pdc-maxNumberPRS-ResourceProcessedPerSlot-r18 SEQUENCE { + fr1-r18 SEQUENCE { + scs-15kHz-r18 ENUMERATED {n1, n2, n4, n6, n8, n12, n16, n24, n32, n48, n64} OPTIONAL, + scs-30kHz-r18 ENUMERATED {n1, n2, n4, n6, n8, n12, n16, n24, n32, n48, n64} OPTIONAL, + scs-60kHz-r18 ENUMERATED {n1, n2, n4, n6, n8, n12, n16, n24, n32, n48, n64} OPTIONAL, + }, + fr2-r18 SEQUENCE { + scs-60kHz-r18 ENUMERATED {n1, n2, n4, n6, n8, n12, n16, n24, n32, n48, n64} OPTIONAL, + scs-120kHz-r18 ENUMERATED {n1, n2, n4, n6, n8, n12, n16, n24, n32, n48, n64} OPTIONAL, + } +} OPTIONAL, + +-- R4 27-2: LowerMSD for inter-band NR CA and EN-DC +lowerMSD-r18 SEQUENCE (SIZE (1..maxLowerMSD-r18)) OF LowerMSD-r18 OPTIONAL, + +-- R4 31-2 Beam sweeping factor reduction for FR2 unknown SCell activation +beamSweepingFactorReduction-r18 SEQUENCE { + reduceForCellDetection ENUMERATED {n1, n2, n4, n6}, + reduceForSSB-L1-RSRP-Meas INTEGER (0..7) +} OPTIONAL, + +``` + +``` + +-- R4 35-2: the requirements defined for ATG UE with antenna array or omni-direction antenna requirements. +antennaArrayType-r18 ENUMERATED {supported} OPTIONAL, +locationBasedCondHandoverATG-r18 ENUMERATED {supported} OPTIONAL, +-- R4 35-3: rated maximum output power value range from 23dBm to 40dBm with 1dB as granularity at maximum modulation order and full +-- PRB configurations. +maxOutputPowerATG-r18 INTEGER (1..18) OPTIONAL, + +eventA4BasedCondHandoverNES-r18 ENUMERATED {supported} OPTIONAL, +nesBasedCondHandoverWithDCI-r18 ENUMERATED {supported} OPTIONAL, +rachLessHandoverNTN-r18 ENUMERATED {supported} OPTIONAL, +locationBasedCondHandoverEMC-r18 ENUMERATED {supported} OPTIONAL, +mt-CG-SDT-r18 ENUMERATED {supported} OPTIONAL, +posSRS-RRC-InactiveInitialUL-BWP-r18 ENUMERATED {supported} OPTIONAL, +posSRS-RRC-InactiveOutsideInitialUL-BWP-r18 ENUMERATED {supported} OPTIONAL, +cg-SDT-PeriodicityExt-r18 ENUMERATED {supported} OPTIONAL +]] +} + +BandNR-v16c0 ::= SEQUENCE { + pusch-RepetitionTypeA-v16c0 ENUMERATED {supported} OPTIONAL, + ... +} + +LowerMSD-r18 ::= SEQUENCE { + aggressorband1-r18 FreqBandIndicatorNR, + aggressorband2-r18 FreqBandIndicatorNR OPTIONAL, + msd-Information-r18 SEQUENCE (SIZE (1..maxLowerMSDInfo-r18)) OF MSD-Information-r18 +} + +MSD-Information-r18 ::= SEQUENCE { + msd-Type-r18 ENUMERATED {harmonic, harmonicMixing, crossBandIsolation, imd2, imd3, imd4, imd5, all, spare8, spare7, + spare6, spare5, spare4, spare3, spare2, spare1}, + msd-PowerClass-r18 ENUMERATED {pc1dot5, pc2, pc3}, + msd-Class-r18 ENUMERATED {classI, classII, classIII, classIV, classV, classVI, classVII, classVIII } +} + +-- Editor note: The power class related part can be updated further pending RAN4 discussion. + +-- TAG-RF-PARAMETERS-STOP +-- ASN1STOP + +``` + +| RF-Parameters field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| appliedFreqBandListFilter
In this field the UE mirrors the FreqBandList that the NW provided in the capability enquiry, if any, as described in clause 5.6.1.4. The UE filtered the band combinations in the supportedBandCombinationList in accordance with this appliedFreqBandListFilter . The UE does not include this field if the UE capability is requested by E-UTRAN and the network request includes the field eutra-nr-only [10]. | +| supportedBandCombinationList
A list of band combinations that the UE supports for NR (and NR-DC, if requested). The FeatureSetCombinationId :s in this list refer to the FeatureSetCombination entries in the featureSetCombinations list in the UE-NR-Capability IE. The UE does not include this field if the UE capability is requested by E-UTRAN and the network request includes the field eutra-nr-only [10]. | +| supportedBandCombinationListSidelinkEUTRA-NR
A list of band combinations that the UE supports for NR sidelink communication only, for joint NR sidelink communication and V2X sidelink communication, or for V2X sidelink communication only. The UE does not include this field if the UE capability is requested by E-UTRAN (see TS 36.331[10]) and the network request includes the field eutra-nr-only . | +| supportedBandCombinationListSL-NonRelayDiscovery
A list of band combinations that the UE supports for NR sidelink non-relay discovery. The encoding is defined in PC5 BandCombinationListSidelinkNR-r16 . | +| supportedBandCombinationListSL-RelayDiscovery
A list of band combinations that the UE supports for NR sidelink relay discovery. The encoding is defined in PC5 BandCombinationListSidelinkNR-r16 . | +| supportedBandCombinationListSL-U2U-DiscoveryExt
This field indicates the band parameter in BandCombinationListSL-Discovery-r17 that the UE supports for NR U2U sidelink relay discovery in a band included in supportedBandCombinationListSL-U2U-RelayDiscovery . | +| supportedBandCombinationListSL-U2U-RelayDiscovery
A list of band combinations that the UE supports for NR U2U sidelink relay discovery. The encoding is defined in PC5 BandCombinationListSidelinkNR-r16 . | +| supportedBandCombinationList-UplinkTxSwitch
A list of band combinations that the UE supports dynamic uplink Tx switching for NR UL CA and SUL. The FeatureSetCombinationId :s in this list refer to the FeatureSetCombination entries in the featureSetCombinations list in the UE-NR-Capability IE. The UE does not include this field if the UE capability is requested by E-UTRAN and the network request includes the field eutra-nr-only [10]. | +| supportedBandListNR
A list of NR bands supported by the UE. If supportedBandListNR-v16c0 is included, the UE shall include the same number of entries, and listed in the same order, as in supportedBandListNR (without suffix). | + +#### – RF-ParametersMRDC + +The IE *RF-ParametersMRDC* is used to convey RF related capabilities for MR-DC. + +#### RF-ParametersMRDC information element + +``` +-- ASN1START +-- TAG-RF-PARAMETERSMRDC-START + +RF-ParametersMRDC ::= + SEQUENCE { + supportedBandCombinationList BandCombinationList OPTIONAL, + appliedFreqBandListFilter FreqBandList OPTIONAL, + ... + [[ +``` + +``` + +srs-SwitchingTimeRequested ENUMERATED {true} OPTIONAL, +supportedBandCombinationList-v1540 BandCombinationList-v1540 OPTIONAL +]], +[[ +supportedBandCombinationList-v1550 BandCombinationList-v1550 OPTIONAL +]], +[[ +supportedBandCombinationList-v1560 BandCombinationList-v1560 OPTIONAL, +supportedBandCombinationListNEDC-Only BandCombinationList OPTIONAL +]], +[[ +supportedBandCombinationList-v1570 BandCombinationList-v1570 OPTIONAL +]], +[[ +supportedBandCombinationList-v1580 BandCombinationList-v1580 OPTIONAL +]], +[[ +supportedBandCombinationList-v1590 BandCombinationList-v1590 OPTIONAL +]], +[[ +supportedBandCombinationListNEDC-Only-v15a0 SEQUENCE { + supportedBandCombinationList-v1540 BandCombinationList-v1540 OPTIONAL, + supportedBandCombinationList-v1560 BandCombinationList-v1560 OPTIONAL, + supportedBandCombinationList-v1570 BandCombinationList-v1570 OPTIONAL, + supportedBandCombinationList-v1580 BandCombinationList-v1580 OPTIONAL, + supportedBandCombinationList-v1590 BandCombinationList-v1590 OPTIONAL +} OPTIONAL +]], +[[ +supportedBandCombinationList-v1610 BandCombinationList-v1610 OPTIONAL, +supportedBandCombinationListNEDC-Only-v1610 BandCombinationList-v1610 OPTIONAL, +supportedBandCombinationList-UplinkTxSwitch-r16 BandCombinationList-UplinkTxSwitch-r16 OPTIONAL +]], +[[ +supportedBandCombinationList-v1630 BandCombinationList-v1630 OPTIONAL, +supportedBandCombinationListNEDC-Only-v1630 BandCombinationList-v1630 OPTIONAL, +supportedBandCombinationList-UplinkTxSwitch-v1630 BandCombinationList-UplinkTxSwitch-v1630 OPTIONAL +]], +[[ +supportedBandCombinationList-v1640 BandCombinationList-v1640 OPTIONAL, +supportedBandCombinationListNEDC-Only-v1640 BandCombinationList-v1640 OPTIONAL, +supportedBandCombinationList-UplinkTxSwitch-v1640 BandCombinationList-UplinkTxSwitch-v1640 OPTIONAL +]], +[[ +supportedBandCombinationList-UplinkTxSwitch-v1670 BandCombinationList-UplinkTxSwitch-v1670 OPTIONAL +]], +[[ +supportedBandCombinationList-v1700 BandCombinationList-v1700 OPTIONAL, +supportedBandCombinationList-UplinkTxSwitch-v1700 BandCombinationList-UplinkTxSwitch-v1700 OPTIONAL +]], +[[ + +``` + +``` + + supportedBandCombinationList-v1720 BandCombinationList-v1720 OPTIONAL, + supportedBandCombinationListNEDC-Only-v1720 SEQUENCE { + supportedBandCombinationList-v1700 BandCombinationList-v1700 OPTIONAL, + supportedBandCombinationList-v1720 BandCombinationList-v1720 OPTIONAL, + } OPTIONAL, + supportedBandCombinationList-UplinkTxSwitch-v1720 BandCombinationList-UplinkTxSwitch-v1720 OPTIONAL +], +[[ + supportedBandCombinationList-v1730 BandCombinationList-v1730 OPTIONAL, + supportedBandCombinationListNEDC-Only-v1730 BandCombinationList-v1730 OPTIONAL, + supportedBandCombinationList-UplinkTxSwitch-v1730 BandCombinationList-UplinkTxSwitch-v1730 OPTIONAL +], +[[ + supportedBandCombinationList-v1740 BandCombinationList-v1740 OPTIONAL, + supportedBandCombinationListNEDC-Only-v1740 BandCombinationList-v1740 OPTIONAL, + supportedBandCombinationList-UplinkTxSwitch-v1740 BandCombinationList-UplinkTxSwitch-v1740 OPTIONAL +], +[[ + supportedBandCombinationList-v1770 BandCombinationList-v1770 OPTIONAL, + supportedBandCombinationList-UplinkTxSwitch-v1770 BandCombinationList-UplinkTxSwitch-v1770 OPTIONAL +], +[[ + supportedBandCombinationList-v1800 BandCombinationList-v1800 OPTIONAL, + supportedBandCombinationList-UplinkTxSwitch-v1800 BandCombinationList-v1800 OPTIONAL +]] +} + +RF-ParametersMRDC-v15g0 ::= SEQUENCE { + supportedBandCombinationList-v15g0 BandCombinationList-v15g0 OPTIONAL, + supportedBandCombinationListNEDC-Only-v15g0 BandCombinationList-v15g0 OPTIONAL +} + +RF-ParametersMRDC-v15n0 ::= SEQUENCE { + supportedBandCombinationList-v15n0 BandCombinationList-v15n0 OPTIONAL +} + +RF-ParametersMRDC-v16e0 ::= SEQUENCE { + supportedBandCombinationList-UplinkTxSwitch-v16e0 BandCombinationList-UplinkTxSwitch-v16e0 OPTIONAL +} + +-- TAG-RF-PARAMETERSMRDC-STOP +-- ASN1STOP + +``` + +| RF-ParametersMRDC field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| appliedFreqBandListFilter
In this field the UE mirrors the FreqBandList that the NW provided in the capability enquiry, if any. The UE filtered the band combinations in the supportedBandCombinationList in accordance with this appliedFreqBandListFilter . | +| supportedBandCombinationList
A list of band combinations that the UE supports for (NG)EN-DC, or both (NG)EN-DC and NE-DC. The FeatureSetCombinationId s in this list refer to the FeatureSetCombination entries in the featureSetCombinations list in the UE-MRDC-Capability IE. | +| supportedBandCombinationListNEDC-Only, supportedBandCombinationListNEDC-Only-v1610
A list of band combinations that the UE supports only for NE-DC. The FeatureSetCombinationId s in this list refer to the FeatureSetCombination entries in the featureSetCombinations list in the UE-MRDC-Capability IE. | +| supportedBandCombinationList-UplinkTxSwitch
A list of band combinations that the UE supports dynamic UL Tx switching for (NG)EN-DC. The FeatureSetCombinationId s in this list refer to the FeatureSetCombination entries in the featureSetCombinations list in the UE-MRDC-Capability IE. | + +#### — RLC-Parameters + +The IE *RLC-Parameters* is used to convey capabilities related to RLC. + +#### RLC-Parameters information element + +``` +-- ASN1START +-- TAG-RLC-PARAMETERS-START + +RLC-Parameters ::= SEQUENCE { + am-WithShortSN ENUMERATED {supported} OPTIONAL, + um-WithShortSN ENUMERATED {supported} OPTIONAL, + um-WithLongSN ENUMERATED {supported} OPTIONAL, + ... + [[ + extendedT-PollRetransmit-r16 ENUMERATED {supported} OPTIONAL, + extendedT-StatusProhibit-r16 ENUMERATED {supported} OPTIONAL + ]], + [[ + am-WithLongSN-RedCap-r17 ENUMERATED {supported} OPTIONAL + ]], + [[ + am-WithLongSN-NCR-r18 ENUMERATED {supported} OPTIONAL + ]] +} + +-- TAG-RLC-PARAMETERS-STOP +-- ASN1STOP +``` + +#### — *SDAP-Parameters* + +The IE *SDAP-Parameters* is used to convey capabilities related to SDAP. + +#### *SDAP-Parameters* information element + +``` +-- ASN1START +-- TAG-SDAP-PARAMETERS-START + +SDAP-Parameters ::= SEQUENCE { + as-ReflectiveQoS ENUMERATED {true} OPTIONAL, + ... + [[ + sdap-QoS-IAB-r16 ENUMERATED {supported} OPTIONAL, + sdapHeaderIAB-r16 ENUMERATED {supported} OPTIONAL + ]], + [[ + sdap-QoS-NCR-r18 ENUMERATED {supported} OPTIONAL, + sdap-HeaderNCR-r18 ENUMERATED {supported} OPTIONAL + ]] +} + +-- TAG-SDAP-PARAMETERS-STOP +-- ASN1STOP +``` + +#### — *SharedSpectrumChAccessParamsPerBand* + +The IE *SharedSpectrumChAccessParamsPerBand* is used to convey shared channel access related parameters specific for a certain frequency band (not per feature set or band combination). + +#### *SharedSpectrumChAccessParamsPerBand* information element + +``` +-- ASN1START +-- TAG-SHAREDSPECTRUMCHACCESSPARAMSPERBAND-START + +SharedSpectrumChAccessParamsPerBand-r16 ::= SEQUENCE { + -- R1 10-1: UL channel access for dynamic channel access mode + ul-DynamicChAccess-r16 ENUMERATED {supported} OPTIONAL, + -- R1 10-1a: UL channel access for semi-static channel access mode + ul-Semi-StaticChAccess-r16 ENUMERATED {supported} OPTIONAL, + -- R1 10-2: SSB-based RRM for dynamic channel access mode + ssb-RRM-DynamicChAccess-r16 ENUMERATED {supported} OPTIONAL, + -- R1 10-2a: SSB-based RRM for semi-static channel access mode + ssb-RRM-Semi-StaticChAccess-r16 ENUMERATED {supported} OPTIONAL, + -- R1 10-2b: MIB reading on unlicensed cell + mib-Acquisition-r16 ENUMERATED {supported} OPTIONAL, +} +``` + +``` + +-- R1 10-2c: SSB-based RLM for dynamic channel access mode +ssb-RLM-DynamicChAccess-r16 ENUMERATED {supported} OPTIONAL, +-- R1 10-2d: SSB-based RLM for semi-static channel access mode +ssb-RLM-Semi-StaticChAccess-r16 ENUMERATED {supported} OPTIONAL, +-- R1 10-2e: SIB1 reception on unlicensed cell +sib1-Acquisition-r16 ENUMERATED {supported} OPTIONAL, +-- R1 10-2f: Support monitoring of extended RAR window +extRA-ResponseWindow-r16 ENUMERATED {supported} OPTIONAL, +-- R1 10-2g: SSB-based BFD/CBD for dynamic channel access mode +ssb-BFD-CBD-dynamicChannelAccess-r16 ENUMERATED {supported} OPTIONAL, +-- R1 10-2h: SSB-based BFD/CBD for semi-static channel access mode +ssb-BFD-CBD-semi-staticChannelAccess-r16 ENUMERATED {supported} OPTIONAL, +-- R1 10-2i: CSI-RS-based BFD/CBD for NR-U +csi-RS-BFD-CBD-r16 ENUMERATED {supported} OPTIONAL, +-- R1 10-7: UL channel access for 10 MHz SCell +ul-ChannelBW-SCell-10mhz-r16 ENUMERATED {supported} OPTIONAL, +-- R1 10-10: RSSI and channel occupancy measurement and reporting +rssi-ChannelOccupancyReporting-r16 ENUMERATED {supported} OPTIONAL, +-- R1 10-11: SRS starting position at any OFDM symbol in a slot +srs-StartAnyOFDM-Symbol-r16 ENUMERATED {supported} OPTIONAL, +-- R1 10-20: Support search space set configuration with freqMonitorLocation-r16 +searchSpaceFreqMonitorLocation-r16 INTEGER (1..5) OPTIONAL, +-- R1 10-20a: Support coreset configuration with rb-Offset +coreset-RB-Offset-r16 ENUMERATED {supported} OPTIONAL, +-- R1 10-23: CGI reading on unlicensed cell for ANR functionality +cgi-Acquisition-r16 ENUMERATED {supported} OPTIONAL, +-- R1 10-25: Enable configured UL transmissions when DCI 2_0 is configured but not detected +configuredUL-Tx-r16 ENUMERATED {supported} OPTIONAL, +-- R1 10-27: Wideband PRACH +prach-Wideband-r16 ENUMERATED {supported} OPTIONAL, +-- R1 10-29: Support available RB set indicator field in DCI 2_0 +dci-AvailableRB-Set-r16 ENUMERATED {supported} OPTIONAL, +-- R1 10-30: Support channel occupancy duration indicator field in DCI 2_0 +dci-ChOccupancyDuration-r16 ENUMERATED {supported} OPTIONAL, +-- R1 10-8: Type B PDSCH length {3, 5, 6, 8, 9, 10, 11, 12, 13} without DMRS shift due to CRS collision +typeB-PDSCH-length-r16 ENUMERATED {supported} OPTIONAL, +-- R1 10-9: Search space set group switching with explicit DCI 2_0 bit field trigger or with implicit PDCCH decoding with DCI 2_0 monitoring +searchSpaceSwitchWithDCI-r16 ENUMERATED {supported} OPTIONAL, +-- R1 10-9b: Search space set group switching with implicit PDCCH decoding without DCI 2_0 monitoring +searchSpaceSwitchWithoutDCI-r16 ENUMERATED {supported} OPTIONAL, +-- R1 10-9d: Support Search space set group switching capability 2 +searchSpaceSwitchCapability2-r16 ENUMERATED {supported} OPTIONAL, +-- R1 10-14: Non-numerical PDSCH to HARQ-ACK timing +non-numericalPDSCH-HARQ-timing-r16 ENUMERATED {supported} OPTIONAL, +-- R1 10-15: Enhanced dynamic HARQ codebook +enhancedDynamicHARQ-codebook-r16 ENUMERATED {supported} OPTIONAL, +-- R1 10-16: One-shot HARQ ACK feedback +oneShotHARQ-feedback-r16 ENUMERATED {supported} OPTIONAL, +-- R1 10-17: Multi-PUSCH UL grant +multiPUSCH-UL-grant-r16 ENUMERATED {supported} OPTIONAL, +-- R1 10-26: CSI-RS based RLM for NR-U + +``` + +``` + +csi-RS-RLM-r16 ENUMERATED {supported} OPTIONAL, +dummy ENUMERATED {supported} OPTIONAL, +-- R1 10-31: Support of P/SP-CSI-RS reception with CSI-RS-ValidationWithDCI-r16 configured +periodicAndSemi-PersistentCSI-RS-r16 ENUMERATED {supported} OPTIONAL, +-- R1 10-3: PRB interlace mapping for PUSCH +pusch-PRB-interlace-r16 ENUMERATED {supported} OPTIONAL, +-- R1 10-3a: PRB interlace mapping for PUCCH +pucch-F0-F1-PRB-Interlace-r16 ENUMERATED {supported} OPTIONAL, +-- R1 10-12: OCC for PRB interlace mapping for PF2 and PF3 +occ-PRB-PF2-PF3-r16 ENUMERATED {supported} OPTIONAL, +-- R1 10-13a: Extended CP range of more than one symbol for CG-PUSCH +extCP-rangeCG-PUSCH-r16 ENUMERATED {supported} OPTIONAL, +-- R1 10-18: Configured grant with retransmission in CG resources +configuredGrantWithReTx-r16 ENUMERATED {supported} OPTIONAL, +-- R1 10-21a: Support using ED threshold given by gNB for UL to DL COT sharing +ed-Threshold-r16 ENUMERATED {supported} OPTIONAL, +-- R1 10-21b: Support UL to DL COT sharing +ul-DL-COT-Sharing-r16 ENUMERATED {supported} OPTIONAL, +-- R1 10-24: CG-UCI multiplexing with HARQ ACK +mux-CG-UCI-HARQ-ACK-r16 ENUMERATED {supported} OPTIONAL, +-- R1 10-28: Configured grant with Rel-16 enhanced resource configuration +cg-resourceConfig-r16 ENUMERATED {supported} OPTIONAL, +} + +SharedSpectrumChAccessParamsPerBand-v1630 ::= SEQUENCE { +-- R4 4-1: DL reception in intra-carrier guardband +dl-ReceptionIntraCellGuardband-r16 ENUMERATED {supported} OPTIONAL, +-- R4 4-2: DL reception when gNB does not transmit on all RB sets of a carrier as a result of LBT +dl-ReceptionLBT-subsetRB-r16 ENUMERATED {supported} OPTIONAL, +} + +SharedSpectrumChAccessParamsPerBand-v1640 ::= SEQUENCE { +-- 10-26b(1-4): CSI-RS based RRM measurement with associated SS-block +csi-RSRP-AndRSRQ-MeasWithSSB-r16 ENUMERATED {supported} OPTIONAL, +-- 10-26c(1-5): CSI-RS based RRM measurement without associated SS-block +csi-RSRP-AndRSRQ-MeasWithoutSSB-r16 ENUMERATED {supported} OPTIONAL, +-- 10-26d(1-6): CSI-RS based RS-SINR measurement +csi-SINR-Meas-r16 ENUMERATED {supported} OPTIONAL, +-- 10-26e(1-8): RLM based on a mix of SS block and CSI-RS signals within active BWP +ssb-AndCSI-RS-RLM-r16 ENUMERATED {supported} OPTIONAL, +-- 10-26f(1-9): CSI-RS based contention free RA for HO +csi-RS-CFRA-ForHO-r16 ENUMERATED {supported} OPTIONAL, +} + +SharedSpectrumChAccessParamsPerBand-v1650 ::= SEQUENCE { +-- Extension of R1 10-9 capability to configure up to 16 instead of 4 cells or cell groups, respectively +extendedSearchSpaceSwitchWithDCI-r16 ENUMERATED {supported} OPTIONAL, +} + +SharedSpectrumChAccessParamsPerBand-v1710 ::= SEQUENCE { +-- R1 25-12: UE initiated semi-static channel occupancy with dependent configurations + +``` + +``` + +ul-Semi-StaticChAccessDependentConfig-r17 ENUMERATED {supported} OPTIONAL, +-- R1 25-13: UE initiated semi-static channel occupancy with independent configurations +ul-Semi-StaticChAccessIndependentConfig-r17 ENUMERATED {supported} OPTIONAL +} + +-- TAG-SHAREDSPECTRUMCHACCESSPARAMSPERBAND-STOP +-- ASN1STOP + +``` + +#### SidelinkParameters + +The IE *SidelinkParameters* is used to convey capabilities related to NR and V2X sidelink communications. + +#### SidelinkParameters information element + +``` + +-- ASN1START +-- TAG-SIDELINKPARAMETERS-START + +SidelinkParameters-r16 ::= SEQUENCE { + sidelinkParametersNR-r16 SidelinkParametersNR-r16 OPTIONAL, + sidelinkParametersEUTRA-r16 SidelinkParametersEUTRA-r16 OPTIONAL +} + +SidelinkParametersNR-r16 ::= SEQUENCE { + rlc-ParametersSidelink-r16 RLC-ParametersSidelink-r16 OPTIONAL, + mac-ParametersSidelink-r16 MAC-ParametersSidelink-r16 OPTIONAL, + fdd-Add-UE-Sidelink-Capabilities-r16 UE-SidelinkCapabilityAddXDD-Mode-r16 OPTIONAL, + tdd-Add-UE-Sidelink-Capabilities-r16 UE-SidelinkCapabilityAddXDD-Mode-r16 OPTIONAL, + supportedBandListSidelink-r16 SEQUENCE (SIZE (1..maxBands)) OF BandSidelink-r16 OPTIONAL, + ... + [[ + relayParameters-r17 RelayParameters-r17 OPTIONAL + ]], + [[ + -- R1 32-x: Use of new P0 parameters for open loop power control + p0-OLPC-Sidelink-r17 ENUMERATED {supported} OPTIONAL + ]], + [[ + pdcp-ParametersSidelink-r18 PDCP-ParametersSidelink-r18 OPTIONAL + ]] +} + +SidelinkParametersEUTRA-r16 ::= SEQUENCE { + sl-ParametersEUTRA1-r16 OCTET STRING OPTIONAL, + sl-ParametersEUTRA2-r16 OCTET STRING OPTIONAL, + sl-ParametersEUTRA3-r16 OCTET STRING OPTIONAL, + supportedBandListSidelinkEUTRA-r16 SEQUENCE (SIZE (1..maxBandsEUTRA)) OF BandSidelinkEUTRA-r16 OPTIONAL, + ... +} + +``` + +``` + +RLC-ParametersSidelink-r16 ::= SEQUENCE { + am-WithLongSN-Sidelink-r16 ENUMERATED {supported} OPTIONAL, + um-WithLongSN-Sidelink-r16 ENUMERATED {supported} OPTIONAL, + ... +} + +MAC-ParametersSidelink-r16 ::= SEQUENCE { + mac-ParametersSidelinkCommon-r16 MAC-ParametersSidelinkCommon-r16 OPTIONAL, + mac-ParametersSidelinkXDD-Diff-r16 MAC-ParametersSidelinkXDD-Diff-r16 OPTIONAL, + ... +} + +UE-SidelinkCapabilityAddXDD-Mode-r16 ::= SEQUENCE { + mac-ParametersSidelinkXDD-Diff-r16 MAC-ParametersSidelinkXDD-Diff-r16 OPTIONAL +} + +MAC-ParametersSidelinkCommon-r16 ::= SEQUENCE { + lcp-RestrictionSidelink-r16 ENUMERATED {supported} OPTIONAL, + multipleConfiguredGrantsSidelink-r16 ENUMERATED {supported} OPTIONAL, + ..., + [[ + drx-OnSidelink-r17 ENUMERATED {supported} OPTIONAL + ]], + [[ + sl-LBT-FailureDetectionRecovery-r18 ENUMERATED {supported} OPTIONAL + ]] +} + +MAC-ParametersSidelinkXDD-Diff-r16 ::= SEQUENCE { + multipleSR-ConfigurationsSidelink-r16 ENUMERATED {supported} OPTIONAL, + logicalChannelSR-DelayTimerSidelink-r16 ENUMERATED {supported} OPTIONAL, + ... +} + +BandSidelinkEUTRA-r16 ::= SEQUENCE { + freqBandSidelinkEUTRA-r16 FreqBandIndicatorEUTRA, + -- R1 15-7: Transmitting LTE sidelink mode 3 scheduled by NR Uu + gnb-ScheduledMode3SidelinkEUTRA-r16 SEQUENCE { + gnb-ScheduledMode3DelaySidelinkEUTRA-r16 ENUMERATED {ms0, ms0dot25, ms0dot5, ms0dot625, ms0dot75, ms1, + ms1dot25, ms1dot5, ms1dot75, ms2, ms2dot5, ms3, ms4, + ms5, ms6, ms8, ms10, ms20} + } + -- R1 15-9: Transmitting LTE sidelink mode 4 configured by NR Uu + gnb-ScheduledMode4SidelinkEUTRA-r16 ENUMERATED {supported} OPTIONAL +} + +BandSidelink-r16 ::= SEQUENCE { + freqBandSidelink-r16 FreqBandIndicatorNR, + --15-1 + sl-Reception-r16 SEQUENCE { + harq-RxProcessSidelink-r16 ENUMERATED {n16, n24, n32, n48, n64}, + } +} + +``` + +``` + +psch-RxSidelink-r16 ENUMERATED {value1, value2}, +scs-CP-PatternRxSidelink-r16 CHOICE { + fr1-r16 SEQUENCE { + scs-15kHz-r16 BIT STRING (SIZE (16)) OPTIONAL, + scs-30kHz-r16 BIT STRING (SIZE (16)) OPTIONAL, + scs-60kHz-r16 BIT STRING (SIZE (16)) OPTIONAL + }, + fr2-r16 SEQUENCE { + scs-60kHz-r16 BIT STRING (SIZE (16)) OPTIONAL, + scs-120kHz-r16 BIT STRING (SIZE (16)) OPTIONAL + } +} OPTIONAL, +extendedCP-RxSidelink-r16 ENUMERATED {supported} OPTIONAL, +OPTIONAL, +--15-2 +sl-TransmissionModel-r16 SEQUENCE { + harq-TxProcessModeOneSidelink-r16 ENUMERATED {n8, n16}, + scs-CP-PatternTxSidelinkModeOne-r16 CHOICE { + fr1-r16 SEQUENCE { + scs-15kHz-r16 BIT STRING (SIZE (16)) OPTIONAL, + scs-30kHz-r16 BIT STRING (SIZE (16)) OPTIONAL, + scs-60kHz-r16 BIT STRING (SIZE (16)) OPTIONAL + }, + fr2-r16 SEQUENCE { + scs-60kHz-r16 BIT STRING (SIZE (16)) OPTIONAL, + scs-120kHz-r16 BIT STRING (SIZE (16)) OPTIONAL + } + }, + extendedCP-TxSidelink-r16 ENUMERATED {supported} OPTIONAL, + harq-ReportOnPUCCH-r16 ENUMERATED {supported} OPTIONAL, +} OPTIONAL, +--15-4 +sync-Sidelink-r16 SEQUENCE { + gNB-Sync-r16 ENUMERATED {supported} OPTIONAL, + gNB-GNSS-UE-SyncWithPriorityOnGNB-ENB-r16 ENUMERATED {supported} OPTIONAL, + gNB-GNSS-UE-SyncWithPriorityOnGNSS-r16 ENUMERATED {supported} OPTIONAL, +} OPTIONAL, +--15-10 +sl-Tx-256QAM-r16 ENUMERATED {supported} OPTIONAL, +--15-11 +psfch-FormatZeroSidelink-r16 SEQUENCE { + psfch-RxNumber ENUMERATED {n5, n15, n25, n32, n35, n45, n50, n64}, + psfch-TxNumber ENUMERATED {n4, n8, n16} +} OPTIONAL, +--15-12 +lowSE-64QAM-MCS-TableSidelink-r16 ENUMERATED {supported} OPTIONAL, +--15-15 +enb-sync-Sidelink-r16 ENUMERATED {supported} OPTIONAL, +... +[[ +--15-3 + +``` + +``` + +sl-TransmissionMode2-r16 SEQUENCE { + harq-TxProcessModeTwoSidelink-r16 ENUMERATED {n8, n16}, + scs-CP-PatternTxSidelinkModeTwo-r16 ENUMERATED {supported} OPTIONAL, + dl-openLoopPC-Sidelink-r16 ENUMERATED {supported} OPTIONAL, +} OPTIONAL, +--15-5 +congestionControlSidelink-r16 SEQUENCE { + cbr-ReportSidelink-r16 ENUMERATED {supported} OPTIONAL, + cbr-CR-TimeLimitSidelink-r16 ENUMERATED {time1, time2} OPTIONAL, +} +--15-22 +fewerSymbolSlotSidelink-r16 ENUMERATED {supported} OPTIONAL, +--15-23 +sl-openLoopPC-RSRP-ReportSidelink-r16 ENUMERATED {supported} OPTIONAL, +--13-1 +sl-Rx-256QAM-r16 ENUMERATED {supported} OPTIONAL +]], +[[ +ue-PowerClassSidelink-r16 ENUMERATED {pc2, pc3, spare6, spare5, spare4, spare3, spare2, spare1} + OPTIONAL +]], +[[ +--32-4a +sl-TransmissionMode2-RandomResourceSelection-r17 SEQUENCE { + harq-TxProcessModeTwoSidelink-r17 ENUMERATED {n8, n16}, + scs-CP-PatternTxSidelinkModeTwo-r17 CHOICE { + fr1-r17 SEQUENCE { + scs-15kHz-r17 BIT STRING (SIZE (16)) OPTIONAL, + scs-30kHz-r17 BIT STRING (SIZE (16)) OPTIONAL, + scs-60kHz-r17 BIT STRING (SIZE (16)) OPTIONAL + }, + fr2-r17 SEQUENCE { + scs-60kHz-r17 BIT STRING (SIZE (16)) OPTIONAL, + scs-120kHz-r17 BIT STRING (SIZE (16)) OPTIONAL + } + } OPTIONAL, + extendedCP-Mode2Random-r17 ENUMERATED {supported} OPTIONAL, + dl-openLoopPC-Sidelink-r17 ENUMERATED {supported} OPTIONAL, +} OPTIONAL, +--32-4b +sync-Sidelink-v1710 SEQUENCE { + sync-GNSS-r17 ENUMERATED {supported} OPTIONAL, + gNB-Sync-r17 ENUMERATED {supported} OPTIONAL, + gNB-GNSS-UE-SyncWithPriorityOnGNB-ENB-r17 ENUMERATED {supported} OPTIONAL, + gNB-GNSS-UE-SyncWithPriorityOnGNSS-r17 ENUMERATED {supported} OPTIONAL, +} OPTIONAL, +--32-4c +enb-sync-Sidelink-v1710 ENUMERATED {supported} OPTIONAL, +--32-5a-2 +rx-IUC-Scheme1-PreferredMode2Sidelink-r17 ENUMERATED {supported} OPTIONAL, +--32-5a-3 + +``` + +``` + +rx-IUC-Scheme1-NonPreferredMode2Sidelink-r17 ENUMERATED {supported} OPTIONAL, +--32-5b-2 +rx-IUC-Scheme2-Mode2Sidelink-r17 ENUMERATED {n5, n15, n25, n32, n35, n45, n50, n64} OPTIONAL, +--32-6-1 +rx-IUC-Scheme1-SCI-r17 ENUMERATED {supported} OPTIONAL, +--32-6-2 +rx-IUC-Scheme1-SCI-ExplicitReq-r17 ENUMERATED {supported} OPTIONAL +]], +[[ +-- R4 45-2: SL reception in intra-carrier guard band +sl-ReceptionIntraCarrierGuardBand-r18 ENUMERATED {supported} OPTIONAL +]] +} + +RelayParameters-r17 ::= SEQUENCE { + relayUE-Operation-L2-r17 ENUMERATED {supported} OPTIONAL, + remoteUE-Operation-L2-r17 ENUMERATED {supported} OPTIONAL, + remoteUE-PathSwitchToIdleInactiveRelay-r17 ENUMERATED {supported} OPTIONAL, + ... + [[ + relayUE-U2U-OperationL2-r18 ENUMERATED {supported} OPTIONAL, + remoteUE-U2U-OperationL2-r18 ENUMERATED {supported} OPTIONAL, + remoteUE-U2N-PathSwitchOperationL2-r18 ENUMERATED {supported} OPTIONAL, + multipathRemoteUE-PC5L2-r18 ENUMERATED {supported} OPTIONAL, + multipathRelayUE-PC5L2-r18 ENUMERATED {supported} OPTIONAL, + multipathRelayUE-N3C-r18 ENUMERATED {supported} OPTIONAL, + multipathRemoteUE-N3C-r18 ENUMERATED {supported} OPTIONAL, + remoteUE-IndirectPathAddChangeToIdleInactiveRelay-r18 ENUMERATED {supported} OPTIONAL, + pdcp-DuplicationMoreThanOneUuRLC-r18 ENUMERATED {supported} OPTIONAL + ]] +} + +PDCP-ParametersSidelink-r18 ::= SEQUENCE { + pdcp-DuplicationSRB-sidelink-r18 ENUMERATED {supported} OPTIONAL, + pdcp-DuplicationDRB-sidelink-r18 ENUMERATED {supported} OPTIONAL, + ... +} + +-- TAG-SIDELINKPARAMETERS-STOP +-- ASN1STOP + +``` + +#### SidelinkParametersEUTRA field descriptions + +##### **sl-ParametersEUTRA1, sl-ParametersEUTRA2, sl-ParametersEUTRA3** + +This field includes IE of *SL-Parameters-v1430* (where *v2x-eNB-Scheduled-r14* and *V2X-SupportedBandCombination-r14* shall not be included), *SL-Parameters-v1530* (where *V2X-SupportedBandCombination-r1530* shall not be included) and *SL-Parameters-v1540* respectively defined in 36.331 [10]. It is used for reporting the per-UE capability for V2X sidelink communication. + +#### — *SimultaneousRxTxPerBandPair* + +The IE *SimultaneousRxTxPerBandPair* contains the simultaneous Rx/Tx UE capability for each band pair in a band combination. + +#### *SimultaneousRxTxPerBandPair* information element + +``` +-- ASN1START +-- TAG-SIMULTANEOUSRXTXPERBANDPAIR-START + +SimultaneousRxTxPerBandPair ::= BIT STRING (SIZE (3..496)) + +-- TAG-SIMULTANEOUSRXTXPERBANDPAIR-STOP +-- ASN1STOP +``` + +#### — *SON-Parameters* + +The IE *SON-Parameters* contains SON related parameters. + +#### *SON-Parameters* information element + +``` +-- ASN1START +-- TAG-SON-PARAMETERS-START + +SON-Parameters-r16 ::= SEQUENCE { + rach-Report-r16 ENUMERATED {supported} OPTIONAL, + ... + [[ + rlfReportCHO-r17 ENUMERATED {supported} OPTIONAL, + rlfReportDAPS-r17 ENUMERATED {supported} OPTIONAL, + success-HO-Report-r17 ENUMERATED {supported} OPTIONAL, + twoStepRACH-Report-r17 ENUMERATED {supported} OPTIONAL, + pscell-MHI-Report-r17 ENUMERATED {supported} OPTIONAL, + onDemandSI-Report-r17 ENUMERATED {supported} OPTIONAL + ]], + [[ + spr-Report-r18 ENUMERATED {supported} OPTIONAL, + successIRAT-HO-Report-r18 ENUMERATED {supported} OPTIONAL + ]] +} + +-- TAG-SON-PARAMETERS-STOP +-- ASN1STOP +``` + +#### – *SpatialRelationsSRS-Pos* + +The IE *SpatialRelationsSRS-Pos* is used to convey spatial relation for SRS for positioning related parameters. + +#### *SpatialRelationsSRS-Pos* information element + +``` +-- ASN1START +-- TAG-SPATIALRELATIONSSRS-POS-START + +SpatialRelationsSRS-Pos-r16 ::= SEQUENCE { + spatialRelation-SRS-PosBasedOnSSB-Serving-r16 ENUMERATED {supported} OPTIONAL, + spatialRelation-SRS-PosBasedOnCSI-RS-Serving-r16 ENUMERATED {supported} OPTIONAL, + spatialRelation-SRS-PosBasedOnPRS-Serving-r16 ENUMERATED {supported} OPTIONAL, + spatialRelation-SRS-PosBasedOnSRS-r16 ENUMERATED {supported} OPTIONAL, + spatialRelation-SRS-PosBasedOnSSB-Neigh-r16 ENUMERATED {supported} OPTIONAL, + spatialRelation-SRS-PosBasedOnPRS-Neigh-r16 ENUMERATED {supported} OPTIONAL +} + +--TAG-SPATIALRELATIONSSRS-POS-STOP +-- ASN1STOP +``` + +#### – *SRS-AllPosResourcesRRC-Inactive* + +The IE *SRS-AllPosResourcesRRC-Inactive* is used to convey SRS positioning related parameters specific for a certain band. + +#### *SRS-AllPosResourcesRRC-Inactive* information element + +``` +-- ASN1START +-- TAG-SRS-ALLPOSRESOURCESRRC-INACTIVE-START + +SRS-AllPosResourcesRRC-Inactive-r17 ::= SEQUENCE { + srs-PosResourcesRRC-Inactive-r17 SEQUENCE { + -- R1 27-15: Positioning SRS transmission in RRC_INACTIVE state for initial UL BWP + maxNumberSRS-PosResourceSetPerBWP-r17 ENUMERATED {n1, n2, n4, n8, n12, n16}, + maxNumberSRS-PosResourcesPerBWP-r17 ENUMERATED {n1, n2, n4, n8, n16, n32, n64}, + maxNumberSRS-ResourcesPerBWP-PerSlot-r17 ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10, n12, n14}, + maxNumberPeriodicSRS-PosResourcesPerBWP-r17 ENUMERATED {n1, n2, n4, n8, n16, n32, n64}, + maxNumberPeriodicSRS-PosResourcesPerBWP-PerSlot-r17 ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10, n12, n14}, + dummy1 ENUMERATED {n1, n2, n4, n8, n16, n32, n64 }, + dummy2 ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10, n12, n14} + } +} + +-- TAG-SRS-ALLPOSRESOURCESRRC-INACTIVE-STOP +-- ASN1STOP +``` + +#### | | |------------------------------------------------------------------| | SRS-AllPosResourcesRRC-Inactive field descriptions | |------------------------------------------------------------------| + +###### | | |------------------------------| | dummy1, dummy2 | |------------------------------| + +| | +|-------------------------------------------------------------------------------------------| +| The fields are not used in the specification and the network ignores the received values. | +|-------------------------------------------------------------------------------------------| + +#### – ***SRS-SwitchingTimeNR*** + +The IE *SRS-SwitchingTimeNR* is used to indicate the SRS carrier switching time supported by the UE for one NR band pair. + +#### ***SRS-SwitchingTimeNR information element*** + +``` +-- ASN1START +-- TAG-SRS-SWITCHINGTIMENR-START + +SRS-SwitchingTimeNR ::= SEQUENCE { + switchingTimeDL ENUMERATED {n0us, n30us, n100us, n140us, n200us, n300us, n500us, n900us} OPTIONAL, + switchingTimeUL ENUMERATED {n0us, n30us, n100us, n140us, n200us, n300us, n500us, n900us} OPTIONAL +} + +-- TAG-SRS-SWITCHINGTIMENR-STOP +-- ASN1STOP +``` + +#### – ***SRS-SwitchingTimeEUTRA*** + +The IE *SRS-SwitchingTimeEUTRA* is used to indicate the SRS carrier switching time supported by the UE for one E-UTRA band pair. + +#### ***SRS-SwitchingTimeEUTRA information element*** + +``` +-- ASN1START +-- TAG-SRS-SWITCHINGTIMEEUTRA-START + +SRS-SwitchingTimeEUTRA ::= SEQUENCE { + switchingTimeDL ENUMERATED {n0, n0dot5, n1, n1dot5, n2, n2dot5, n3, n3dot5, n4, n4dot5, n5, n5dot5, n6, n6dot5, n7} + OPTIONAL, + switchingTimeUL ENUMERATED {n0, n0dot5, n1, n1dot5, n2, n2dot5, n3, n3dot5, n4, n4dot5, n5, n5dot5, n6, n6dot5, n7} + OPTIONAL +} + +-- TAG-SRS-SWITCHINGTIMEEUTRA-STOP +-- ASN1STOP +``` + +#### — *SupportedBandwidth* + +The IE *SupportedBandwidth* is used to indicate the channel bandwidth supported by the UE on one carrier of a band of a band combination. + +#### ***SupportedBandwidth* information element** + +``` +-- ASN1START +-- TAG-SUPPORTEDBANDWIDTH-START + +SupportedBandwidth ::= CHOICE { + fr1 ENUMERATED {mhz5, mhz10, mhz15, mhz20, mhz25, mhz30, mhz40, mhz50, mhz60, mhz80, mhz100}, + fr2 ENUMERATED {mhz50, mhz100, mhz200, mhz400} +} + +SupportedBandwidth-v1700 ::= CHOICE { + fr1-r17 ENUMERATED {mhz5, mhz10, mhz15, mhz20, mhz25, mhz30, mhz35, mhz40, mhz45, mhz50, mhz60, mhz70, mhz80, mhz90, mhz100}, + fr2-r17 ENUMERATED {mhz50, mhz100, mhz200, mhz400, mhz800, mhz1600, mhz2000} +} + +-- TAG-SUPPORTEDBANDWIDTH-STOP +-- ASN1STOP +``` + +#### — *UE-BasedPerfMeas-Parameters* + +The IE *UE-BasedPerfMeas-Parameters* contains UE-based performance measurement parameters. + +#### ***UE-BasedPerfMeas-Parameters* information element** + +``` +-- ASN1START +-- TAG-UE-BASEDPERFMEAS-PARAMETERS-START + +UE-BasedPerfMeas-Parameters-r16 ::= SEQUENCE { + barometerMeasReport-r16 ENUMERATED {supported} OPTIONAL, + immMeasBT-r16 ENUMERATED {supported} OPTIONAL, + immMeasWLAN-r16 ENUMERATED {supported} OPTIONAL, + loggedMeasBT-r16 ENUMERATED {supported} OPTIONAL, + loggedMeasurements-r16 ENUMERATED {supported} OPTIONAL, + loggedMeasWLAN-r16 ENUMERATED {supported} OPTIONAL, + orientationMeasReport-r16 ENUMERATED {supported} OPTIONAL, + speedMeasReport-r16 ENUMERATED {supported} OPTIONAL, + gnss-Location-r16 ENUMERATED {supported} OPTIONAL, + ulPDCP-Delay-r16 ENUMERATED {supported} OPTIONAL, + ..., + [[ + sigBasedLogMDT-OverrideProtect-r17 ENUMERATED {supported} OPTIONAL, + multipleCEF-Report-r17 ENUMERATED {supported} OPTIONAL, + excessPacketDelay-r17 ENUMERATED {supported} OPTIONAL, + earlyMeasLog-r17 ENUMERATED {supported} OPTIONAL + ]] +} +``` + +``` + + ]], + [[ + loggedMDT-PNI-NPN-r18 ENUMERATED {supported} OPTIONAL, + loggedMDT-SNPN-r18 ENUMERATED {supported} OPTIONAL + ]] + } + + -- TAG-UE-BASEDPERFMEAS-PARAMETERS-STOP + -- ASN1STOP + +``` + +#### — *UE-CapabilityRAT-ContainerList* + +The IE *UE-CapabilityRAT-ContainerList* contains a list of radio access technology specific capability containers. + +#### *UE-CapabilityRAT-ContainerList* information element + +``` + +-- ASN1START +-- TAG-UE-CAPABILITYRAT-CONTAINERLIST-START + +UE-CapabilityRAT-ContainerList ::= SEQUENCE (SIZE (0..maxRAT-CapabilityContainers)) OF UE-CapabilityRAT-Container + +UE-CapabilityRAT-Container ::= SEQUENCE { + rat-Type RAT-Type, + ue-CapabilityRAT-Container OCTET STRING +} + +-- TAG-UE-CAPABILITYRAT-CONTAINERLIST-STOP +-- ASN1STOP + +``` + +#### *UE-CapabilityRAT-ContainerList* field descriptions + +#### ***ue-CapabilityRAT-Container*** + +Container for the UE capabilities of the indicated RAT. The encoding is defined in the specification of each RAT: + +For *rat-Type* set to *nr*: the encoding of UE capabilities is defined in *UE-NR-Capability*. + +For *rat-Type* set to *eutra-nr*: the encoding of UE capabilities is defined in *UE-MRDC-Capability*. + +For *rat-Type* set to *eutra*: the encoding of UE capabilities is defined in *UE-EUTRA-Capability* specified in TS 36.331 [10]. + +For *rat-Type* set to *utra-fdd*: the octet string contains the INTER RAT HANDOVER INFO message defined in TS 25.331 [45]. + +#### — *UE-CapabilityRAT-RequestList* + +The IE *UE-CapabilityRAT-RequestList* is used to request UE capabilities for one or more RATs from the UE. + +#### *UE-CapabilityRAT-RequestList* information element + +``` +-- ASN1START +``` + +``` + +-- TAG-UE-CAPABILITYRAT-REQUESTLIST-START +UE-CapabilityRAT-RequestList ::= SEQUENCE (SIZE (1..maxRAT-CapabilityContainers)) OF UE-CapabilityRAT-Request +UE-CapabilityRAT-Request ::= SEQUENCE { + rat-Type RAT-Type, + capabilityRequestFilter OCTET STRING OPTIONAL, -- Need N + ... +} +-- TAG-UE-CAPABILITYRAT-REQUESTLIST-STOP +-- ASN1STOP + +``` + +#### UE-CapabilityRAT-Request field descriptions + +##### **capabilityRequestFilter** + +Information by which the network requests the UE to filter the UE capabilities. + +For *rat-Type* set to *nr* or *utra-nr*: the encoding of the *capabilityRequestFilter* is defined in *UE-CapabilityRequestFilterNR*. + +For *rat-Type* set to *utra*: the encoding of the *capabilityRequestFilter* is defined by *UECapabilityEnquiry* message defined in TS36.331 [10], in which *RAT-Type* in *UE-CapabilityRequest* includes only 'utra'. + +##### **rat-Type** + +The RAT type for which the NW requests UE capabilities. + +##### UE-CapabilityRequestFilterCommon + +The IE *UE-CapabilityRequestFilterCommon* is used to request filtered UE capabilities. The filter is common for all capability containers that are requested. + +##### UE-CapabilityRequestFilterCommon information element + +``` + +-- ASN1START +-- TAG-UE-CAPABILITYREQUESTFILTERCOMMON-START +UE-CapabilityRequestFilterCommon ::= SEQUENCE { + mrdc-Request SEQUENCE { + omitEN-DC ENUMERATED {true} OPTIONAL, -- Need N + includeNR-DC ENUMERATED {true} OPTIONAL, -- Need N + includeNE-DC ENUMERATED {true} OPTIONAL, -- Need N + } + ... + [[ + codebookTypeRequest-r16 SEQUENCE { + type1-SinglePanel-r16 ENUMERATED {true} OPTIONAL, -- Need N + type1-MultiPanel-r16 ENUMERATED {true} OPTIONAL, -- Need N + type2-r16 ENUMERATED {true} OPTIONAL, -- Need N + type2-PortSelection-r16 ENUMERATED {true} OPTIONAL, -- Need N + } + uplinkTxSwitchRequest-r16 ENUMERATED {true} OPTIONAL, -- Need N + ]] +``` + +``` + ]], + [[ + requestedCellGrouping-r16 SEQUENCE (SIZE (1..maxCellGroupings-r16)) OF CellGrouping-r16 OPTIONAL -- Cond NRDC + ]], + [[ + fallbackGroupFiveRequest-r17 ENUMERATED {true} OPTIONAL -- Need N + ]], + [[ + lowerMSDRequest-r18 SEQUENCE { + pc1dot5-r18 ENUMERATED {true} OPTIONAL, -- Need N + pc2-r18 ENUMERATED {true} OPTIONAL, -- Need N + pc3-r18 ENUMERATED {true} OPTIONAL -- Need N + } OPTIONAL -- Need N + ]] +} + +CellGrouping-r16 ::= SEQUENCE { + mcg-r16 SEQUENCE (SIZE (1..maxBands)) OF FreqBandIndicatorNR, + scg-r16 SEQUENCE (SIZE (1..maxBands)) OF FreqBandIndicatorNR, + mode-r16 ENUMERATED {sync, async} +} + +-- TAG-UE-CAPABILITYREQUESTFILTERCOMMON-STOP +-- ASN1STOP +``` + +-- Editor Note: The power class related part can be updated further pending RAN4 discussion. + +| UE-CapabilityRequestFilterCommon field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

codebookTypeRequest
Only if this field is present, the UE includes SupportedCSI-RS-Resource supported for the codebook type(s) requested within this field (i.e. type I single/multi-panel, type II and type II port selection) into codebookVariantsList, codebookParametersPerBand and codebookParametersPerBC. If this field is present and none of the codebook types is requested within this field (i.e. empty field), the UE includes SupportedCSI-RS-Resource supported for all codebook types into codebookVariantsList, codebookParametersPerBand and codebookParametersPerBC.

| +|

fallbackGroupFiveRequest
Only if this field is present, the UE supporting FR2 CA bandwidth class from fallback group 5 shall include band combinations with FR2 CA bandwidth class from fallback group 5, and shall omit band combinations with FR2 CA bandwidth class from fallback group 2 or 3 (see TS 38.101-2 [39]) with same or lower capabilities.

| +|

includeNE-DC
Only if this field is present, the UE supporting NE-DC shall indicate support for NE-DC in band combinations and include feature set combinations which are applicable to NE-DC. Band combinations supporting both NE-DC and (NG)EN-DC shall be included in supportedBandCombinationList, band combinations supporting only NE-DC shall be included in supportedBandCombinationListNEDC-Only.

| +|

includeNR-DC
Only if this field is present, the UE supporting NR-DC shall indicate support for NR-DC in band combinations and include feature set combinations which are applicable to NR-DC.

| +|

lowerMSDRequest
Only if this field is present, the UE supporting lower MSD shall indicate the lower MSD capability or the requested power class if supported. Otherwise, the UE supporting lower MSD shall indicate the lower MSD capability for the highest supported power class of the band combination including victim band and aggressor band(s).

| +|

mode
The mode of NR-DC operation that the NW is interested in for this cell grouping. The value sync means that the UE only indicates NR-DC support for band combinations for which it supports synchronous NR-DC with the requested cell grouping. The value async means that the UE only indicates NR-DC support for band combinations for which it supports asynchronous NR-DC with the requested cell grouping.

| +|

omitEN-DC
Only if this field is present, the UE shall omit band combinations and feature set combinations which are only applicable to (NG)EN-DC.

| +|

requestedCellGrouping
The NR-DC cell groupings that the NW is interested in, i.e., the bands that it might use in an MCG and the bands that it might use in an SCG. Only if this field is present, the UE indicates NR-DC support for band combinations for which it supports the requested cell grouping, i.e., in which it supports at least one of the mcg bands on MCG and at least one of the scg bands on the SCG. In its supportedBandCombinationList, the UE indicates which of its NR-DC band combinations supports which of the requested cell groupings. The first element in this list is referred to by ID#0, the second by ID#1 and so on. If this field is absent, the UE only includes band combinations for which it supports NR-DC with only FR1 bands in MCG and only FR2 bands in SCG.
Example 1: requestedCellGrouping is set to mcg=[n1, n7, n41, n66] and scg=[n78, n261]. This assumes that the NW would always use CA among n1, n7, n41 and n66 (depending on which are deployed on a given site) whereas with n78 and/or n261 the NW may need to use DC. With this filter a UE may report a band combination n1A-n7A-n78A for NR-DC only if it supports that serving cells for n1 and n7 are in the MCG and a serving cell for n78 is in the SCG. The UE may also report a band combination n41C-n261M for NR-DC provided that it supports a serving cell for n41 in the MCG and a serving cell for n261 in the SCG.
Example 2: One requestedCellGrouping is set to mcg=[n1, n7, n41, n66] and scg=[n78, n261] and another requestedCellGrouping is set to mcg=[n1, n7, n66] and scg=[n41, n78, n261]. This assumes that the NW uses sometimes CA among n1, n7, n41 and n66 (as in example 1) and sometimes CA among n1, n7 and n66 but DC towards one or several of n41, n78, n261. If a UE supports n1A-n41A-n78A only if n41A and n78A are in the same cell group, this UE may only indicate cell grouping ID#1 (not #0) in its BC.

| +|

uplinkTxSwitchRequest
Only if this field is present, the UE supporting dynamic UL Tx switching shall indicate support for UL Tx switching in band combinations which are applicable to inter-band UL CA, SUL and (NG)EN-DC.

| + +| Conditional Presence | Explanation | +|----------------------|------------------------------------------------------------------------------------------------------| +| NRDC | The field is optionally present, Need N, if includeNR-DC is included. It is absent otherwise. | + +#### – *UE-CapabilityRequestFilterNR* + +The IE *UE-CapabilityRequestFilterNR* is used to request filtered UE capabilities. + +#### *UE-CapabilityRequestFilterNR* information element + +``` +-- ASN1START +-- TAG-UE-CAPABILITYREQUESTFILTERNR-START + +UE-CapabilityRequestFilterNR ::= SEQUENCE { + frequencyBandListFilter FreqBandList OPTIONAL, -- Need N + nonCriticalExtension UE-CapabilityRequestFilterNR-v1540 OPTIONAL +} + +UE-CapabilityRequestFilterNR-v1540 ::= SEQUENCE { + srs-SwitchingTimeRequest ENUMERATED {true} OPTIONAL, -- Need N + nonCriticalExtension UE-CapabilityRequestFilterNR-v1710 OPTIONAL +} + +UE-CapabilityRequestFilterNR-v1710 ::= SEQUENCE { + sidelinkRequest-r17 ENUMERATED {true} OPTIONAL, -- Need N + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +-- TAG-UE-CAPABILITYREQUESTFILTERNR-STOP +-- ASN1STOP +``` + +#### – *UE-MRDC-Capability* + +The IE *UE-MRDC-Capability* is used to convey the UE Radio Access Capability Parameters for MR-DC, see TS 38.306 [26]. + +#### *UE-MRDC-Capability* information element + +``` +-- ASN1START +-- TAG-UE-MRDC-CAPABILITY-START + +UE-MRDC-Capability ::= SEQUENCE { + measAndMobParametersMRDC MeasAndMobParametersMRDC OPTIONAL, + phy-ParametersMRDC-v1530 Phy-ParametersMRDC OPTIONAL, + rf-ParametersMRDC RF-ParametersMRDC, + generalParametersMRDC GeneralParametersMRDC-XDD-Diff OPTIONAL, + fdd-Add-UE-MRDC-Capabilities UE-MRDC-CapabilityAddXDD-Mode OPTIONAL, + tdd-Add-UE-MRDC-Capabilities UE-MRDC-CapabilityAddXDD-Mode OPTIONAL, +``` + +``` + +fr1-Add-UE-MRDC-Capabilities UE-MRDC-CapabilityAddFRX-Mode OPTIONAL, +fr2-Add-UE-MRDC-Capabilities UE-MRDC-CapabilityAddFRX-Mode OPTIONAL, +featureSetCombinations SEQUENCE (SIZE (1..maxFeatureSetCombinations)) OF FeatureSetCombination OPTIONAL, +pdcp-ParametersMRDC-v1530 PDCP-ParametersMRDC OPTIONAL, +lateNonCriticalExtension OCTET STRING (CONTAINING UE-MRDC-Capability-v15g0) OPTIONAL, +nonCriticalExtension UE-MRDC-Capability-v1560 OPTIONAL +} + +-- Regular non-critical extensions: +UE-MRDC-Capability-v1560 ::= SEQUENCE { + receivedFilters OCTET STRING (CONTAINING UECapabilityEnquiry-v1560-IEs) OPTIONAL, + measAndMobParametersMRDC-v1560 MeasAndMobParametersMRDC-v1560 OPTIONAL, + fdd-Add-UE-MRDC-Capabilities-v1560 UE-MRDC-CapabilityAddXDD-Mode-v1560 OPTIONAL, + tdd-Add-UE-MRDC-Capabilities-v1560 UE-MRDC-CapabilityAddXDD-Mode-v1560 OPTIONAL, + nonCriticalExtension UE-MRDC-Capability-v1610 OPTIONAL +} + +UE-MRDC-Capability-v1610 ::= SEQUENCE { + measAndMobParametersMRDC-v1610 MeasAndMobParametersMRDC-v1610 OPTIONAL, + generalParametersMRDC-v1610 GeneralParametersMRDC-v1610 OPTIONAL, + pdcp-ParametersMRDC-v1610 PDCP-ParametersMRDC-v1610 OPTIONAL, + nonCriticalExtension UE-MRDC-Capability-v1700 OPTIONAL +} + +UE-MRDC-Capability-v1700 ::= SEQUENCE { + measAndMobParametersMRDC-v1700 MeasAndMobParametersMRDC-v1700, + nonCriticalExtension UE-MRDC-Capability-v1730 OPTIONAL +} + +UE-MRDC-Capability-v1730 ::= SEQUENCE { + measAndMobParametersMRDC-v1730 MeasAndMobParametersMRDC-v1730 OPTIONAL, + nonCriticalExtension UE-MRDC-Capability-v1800 OPTIONAL +} + +UE-MRDC-Capability-v1800 ::= SEQUENCE { + -- R4 33-2: Support network control of requirementnetwork applicability for UE supporting interBandMRDC-WithOverlapDL-Bands-r16 + requirementTypeIndication-r18 ENUMERATED {supported} OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +-- Late non-critical extensions: +UE-MRDC-Capability-v15g0 ::= SEQUENCE { + rf-ParametersMRDC-v15g0 RF-ParametersMRDC-v15g0 OPTIONAL, + nonCriticalExtension UE-MRDC-Capability-v15n0 OPTIONAL +} + +UE-MRDC-Capability-v15n0 ::= SEQUENCE { + rf-ParametersMRDC-v15n0 RF-ParametersMRDC-v15n0 OPTIONAL, + -- Following field is only for REL-15 late non-critical extensions + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension UE-MRDC-Capability-v16e0 OPTIONAL +} + +``` + +``` + +} + +UE-MRDC-Capability-v16e0 ::= SEQUENCE { + rf-ParametersMRDC-v16e0 RF-ParametersMRDC-v16e0 + nonCriticalExtension SEQUENCE {} +} + +UE-MRDC-CapabilityAddXDD-Mode ::= SEQUENCE { + measAndMobParametersMRDC-XDD-Diff MeasAndMobParametersMRDC-XDD-Diff + generalParametersMRDC-XDD-Diff GeneralParametersMRDC-XDD-Diff +} + +UE-MRDC-CapabilityAddXDD-Mode-v1560 ::= SEQUENCE { + measAndMobParametersMRDC-XDD-Diff-v1560 MeasAndMobParametersMRDC-XDD-Diff-v1560 +} + +UE-MRDC-CapabilityAddFRX-Mode ::= SEQUENCE { + measAndMobParametersMRDC-FRX-Diff MeasAndMobParametersMRDC-FRX-Diff +} + +GeneralParametersMRDC-XDD-Diff ::= SEQUENCE { + splitSRB-WithOneUL-Path ENUMERATED {supported} + splitDRB-withUL-Both-MCG-SCG ENUMERATED {supported} + srb3 ENUMERATED {supported} + dummy ENUMERATED {supported} + ... +} + +GeneralParametersMRDC-v1610 ::= SEQUENCE { + flc-OverEUTRA-r16 ENUMERATED {supported} +} + +-- TAG-UE-MRDC-CAPABILITY-STOP +-- ASN1STOP + +``` + +#### UE-MRDC-Capability field descriptions + +##### featureSetCombinations + +A list of *FeatureSetCombination*:s for *supportedBandCombinationList* and *supportedBandCombinationListNEDC-Only* in *UE-MRDC-Capability*. The *FeatureSetDownlink*:s and *FeatureSetUplink*:s referred to from these *FeatureSetCombination*:s are defined in the *featureSets* list in *UE-NR-Capability*. + +#### — UE-NR-Capability + +The IE *UE-NR-Capability* is used to convey the NR UE Radio Access Capability Parameters, see TS 38.306 [26]. + +#### **UE-NR-Capability information element** + +``` + +-- ASN1START +-- TAG-UE-NR-CAPABILITY-START + +UE-NR-Capability ::= + SEQUENCE { + accessStratumRelease AccessStratumRelease, + pdcp-Parameters PDCP-Parameters, + rlc-Parameters RLC-Parameters, + mac-Parameters MAC-Parameters, + phy-Parameters Phy-Parameters, + rf-Parameters RF-Parameters, + measAndMobParameters MeasAndMobParameters, + fdd-Add-UE-NR-Capabilities UE-NR-CapabilityAddXDD-Mode, + tdd-Add-UE-NR-Capabilities UE-NR-CapabilityAddXDD-Mode, + fr1-Add-UE-NR-Capabilities UE-NR-CapabilityAddFRX-Mode, + fr2-Add-UE-NR-Capabilities UE-NR-CapabilityAddFRX-Mode, + featureSets FeatureSets, + featureSetCombinations SEQUENCE (SIZE (1..maxFeatureSetCombinations)) OF FeatureSetCombination, + lateNonCriticalExtension OCTET STRING (CONTAINING UE-NR-Capability-v15c0), + nonCriticalExtension UE-NR-Capability-v1530 + } + +-- Regular non-critical Rel-15 extensions: +UE-NR-Capability-v1530 ::= + SEQUENCE { + fdd-Add-UE-NR-Capabilities-v1530 UE-NR-CapabilityAddXDD-Mode-v1530, + tdd-Add-UE-NR-Capabilities-v1530 UE-NR-CapabilityAddXDD-Mode-v1530, + dummy ENUMERATED {supported}, + interRAT-Parameters InterRAT-Parameters, + inactiveState ENUMERATED {supported}, + delayBudgetReporting ENUMERATED {supported}, + nonCriticalExtension UE-NR-Capability-v1540 + } + +UE-NR-Capability-v1540 ::= + SEQUENCE { + sdap-Parameters SDAP-Parameters, + overheatingInd ENUMERATED {supported}, + ims-Parameters IMS-Parameters, + fr1-Add-UE-NR-Capabilities-v1540 UE-NR-CapabilityAddFRX-Mode-v1540, + fr2-Add-UE-NR-Capabilities-v1540 UE-NR-CapabilityAddFRX-Mode-v1540, + fr1-fr2-Add-UE-NR-Capabilities UE-NR-CapabilityAddFRX-Mode, + nonCriticalExtension UE-NR-Capability-v1550 + } + +UE-NR-Capability-v1550 ::= + SEQUENCE { + reducedCP-Latency ENUMERATED {supported}, + nonCriticalExtension UE-NR-Capability-v1560 + } + +UE-NR-Capability-v1560 ::= + SEQUENCE { + nrdc-Parameters NRDC-Parameters + } + +``` + +``` + +receivedFilters OCTET STRING (CONTAINING UECapabilityEnquiry-v1560-IEs) OPTIONAL, +nonCriticalExtension UE-NR-Capability-v1570 OPTIONAL +} + +UE-NR-Capability-v1570 ::= + nrdc-Parameters-v1570 NRDC-Parameters-v1570 OPTIONAL, + nonCriticalExtension UE-NR-Capability-v1610 OPTIONAL +} + +-- Late non-critical Rel-15 extensions: +UE-NR-Capability-v15c0 ::= + nrdc-Parameters-v15c0 NRDC-Parameters-v15c0 OPTIONAL, + partialFR2-FallbackRX-Req ENUMERATED {true} OPTIONAL, + nonCriticalExtension UE-NR-Capability-v15g0 OPTIONAL +} + +UE-NR-Capability-v15g0 ::= + rf-Parameters-v15g0 RF-Parameters-v15g0 OPTIONAL, + nonCriticalExtension UE-NR-Capability-v15j0 OPTIONAL +} + +UE-NR-Capability-v15j0 ::= + -- Following field is only for REL-15 late non-critical extensions + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension UE-NR-Capability-v16a0 OPTIONAL +} + +-- Regular non-critical Rel-16 extensions: +UE-NR-Capability-v1610 ::= + inDeviceCoexInd-r16 ENUMERATED {supported} OPTIONAL, + dl-DedicatedMessageSegmentation-r16 ENUMERATED {supported} OPTIONAL, + nrdc-Parameters-v1610 NRDC-Parameters-v1610 OPTIONAL, + powSav-Parameters-r16 PowSav-Parameters-r16 OPTIONAL, + fr1-Add-UE-NR-Capabilities-v1610 UE-NR-CapabilityAddFRX-Mode-v1610 OPTIONAL, + fr2-Add-UE-NR-Capabilities-v1610 UE-NR-CapabilityAddFRX-Mode-v1610 OPTIONAL, + bh-RLF-Indication-r16 ENUMERATED {supported} OPTIONAL, + directSN-AdditionFirstRRC-IAB-r16 ENUMERATED {supported} OPTIONAL, + bap-Parameters-r16 BAP-Parameters-r16 OPTIONAL, + referenceTimeProvision-r16 ENUMERATED {supported} OPTIONAL, + sidelinkParameters-r16 SidelinkParameters-r16 OPTIONAL, + highSpeedParameters-r16 HighSpeedParameters-r16 OPTIONAL, + mac-Parameters-v1610 MAC-Parameters-v1610 OPTIONAL, + mcgRLF-RecoveryViaSCG-r16 ENUMERATED {supported} OPTIONAL, + resumeWithStoredMCG-SCells-r16 ENUMERATED {supported} OPTIONAL, + resumeWithStoredSCG-r16 ENUMERATED {supported} OPTIONAL, + resumeWithSCG-Config-r16 ENUMERATED {supported} OPTIONAL, + ue-BasedPerfMeas-Parameters-r16 UE-BasedPerfMeas-Parameters-r16 OPTIONAL, + son-Parameters-r16 SON-Parameters-r16 OPTIONAL, + onDemandSIB-Connected-r16 ENUMERATED {supported} OPTIONAL, + nonCriticalExtension UE-NR-Capability-v1640 OPTIONAL +} + +``` + +``` + +UE-NR-Capability-v1640 ::= SEQUENCE { + redirectAtResumeByNAS-r16 ENUMERATED {supported} OPTIONAL, + phy-ParametersSharedSpectrumChAccess-r16 Phy-ParametersSharedSpectrumChAccess-r16 OPTIONAL, + nonCriticalExtension UE-NR-Capability-v1650 OPTIONAL +} + +UE-NR-Capability-v1650 ::= SEQUENCE { + mpsPriorityIndication-r16 ENUMERATED {supported} OPTIONAL, + highSpeedParameters-v1650 HighSpeedParameters-v1650 OPTIONAL, + nonCriticalExtension UE-NR-Capability-v1690 OPTIONAL +} + +UE-NR-Capability-v1690 ::= SEQUENCE { + ul-RRC-Segmentation-r16 ENUMERATED {supported} OPTIONAL, + nonCriticalExtension UE-NR-Capability-v1700 OPTIONAL +} + +-- Late non-critical extensions from Rel-16 onwards: +UE-NR-Capability-v16a0 ::= SEQUENCE { + phy-Parameters-v16a0 Phy-Parameters-v16a0 OPTIONAL, + rf-Parameters-v16a0 RF-Parameters-v16a0 OPTIONAL, + nonCriticalExtension UE-NR-Capability-v16c0 OPTIONAL +} + +UE-NR-Capability-v16c0 ::= SEQUENCE { + rf-Parameters-v16c0 RF-Parameters-v16c0 OPTIONAL, + nonCriticalExtension UE-NR-Capability-v16d0 OPTIONAL +} + +UE-NR-Capability-v16d0 ::= SEQUENCE { + featureSets-v16d0 FeatureSets-v16d0 OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +-- Regular non-critical Rel-17 extensions: +UE-NR-Capability-v1700 ::= SEQUENCE { + inactiveStatePO-Determination-r17 ENUMERATED {supported} OPTIONAL, + highSpeedParameters-v1700 HighSpeedParameters-v1700 OPTIONAL, + powSav-Parameters-v1700 PowSav-Parameters-v1700 OPTIONAL, + mac-Parameters-v1700 MAC-Parameters-v1700 OPTIONAL, + ims-Parameters-v1700 IMS-Parameters-v1700 OPTIONAL, + measAndMobParameters-v1700 MeasAndMobParameters-v1700, + appLayerMeasParameters-r17 AppLayerMeasParameters-r17 OPTIONAL, + redCapParameters-r17 RedCapParameters-r17 OPTIONAL, + ra-SDT-r17 ENUMERATED {supported} OPTIONAL, + srb-SDT-r17 ENUMERATED {supported} OPTIONAL, + gNB-SideRTT-BasedPDC-r17 ENUMERATED {supported} OPTIONAL, + bh-RLF-DetectionRecovery-Indication-r17 ENUMERATED {supported} OPTIONAL, + nrdc-Parameters-v1700 NRDC-Parameters-v1700 OPTIONAL, + bap-Parameters-v1700 BAP-Parameters-v1700 OPTIONAL, +} + +``` + +``` + +musim-GapPreference-r17 ENUMERATED {supported} OPTIONAL, +musimLeaveConnected-r17 ENUMERATED {supported} OPTIONAL, +mbs-Parameters-r17 MBS-Parameters-r17, +nonTerrestrialNetwork-r17 ENUMERATED {supported} OPTIONAL, +ntn-ScenarioSupport-r17 ENUMERATED {gso, ngso} OPTIONAL, +sliceInfoforCellReselection-r17 ENUMERATED {supported} OPTIONAL, +ue-RadioPagingInfo-r17 UE-RadioPagingInfo-r17 OPTIONAL, +-- R4 17-2 UL gap pattern for Tx power management +ul-GapFR2-Pattern-r17 BIT STRING (SIZE (4)) OPTIONAL, +ntn-Parameters-r17 NTN-Parameters-r17 OPTIONAL, +nonCriticalExtension UE-NR-Capability-v1740 OPTIONAL +} + +UE-NR-Capability-v1740 ::= + SEQUENCE { + redCapParameters-v1740 RedCapParameters-v1740, + nonCriticalExtension UE-NR-Capability-v1750 OPTIONAL + } + +UE-NR-Capability-v1750 ::= + SEQUENCE { + crossCarrierSchedulingConfigurationRelease-r17 ENUMERATED {supported} OPTIONAL, + nonCriticalExtension UE-NR-Capability-v1800 OPTIONAL + } + +-- Regular non-critical Rel-18 extensions: +UE-NR-Capability-v1800 ::= + SEQUENCE { + airToGroundNetwork-r18 ENUMERATED {supported} OPTIONAL, + eRedCapParameters-r18 ERedCapParameters-r18 OPTIONAL, + ncr-Parameters-r18 NCR-Parameters-r18 OPTIONAL, + softSatelliteSwitchResyncNTN-r18 ENUMERATED {supported} OPTIONAL, + hardSatelliteSwitchResyncNTN-r18 ENUMERATED {supported} OPTIONAL, + mt-SDT-r18 ENUMERATED {supported} OPTIONAL, + mt-SDT-NTN-r18 ENUMERATED {supported} OPTIONAL, + inDeviceCoexIndAutonomousDenial-r18 ENUMERATED {supported} OPTIONAL, + inDeviceCoexIndFDM-r18 ENUMERATED {supported} OPTIONAL, + inDeviceCoexIndTDM-r18 ENUMERATED {supported} OPTIONAL, + musim-GapPriorityPreference-r18 ENUMERATED {supported} OPTIONAL, + musim-CapabilityRestriction-r18 ENUMERATED {supported} OPTIONAL, + multiRx-FR2-Preference-r18 ENUMERATED {supported} OPTIONAL, + ra-InsteadCG-SDT-r18 ENUMERATED {supported} OPTIONAL, + resumeAfterSDT-Release-r18 ENUMERATED {supported} OPTIONAL, + additionalBSR-Table-r18 ENUMERATED {supported} OPTIONAL, + delayStatusReport-r18 ENUMERATED {supported} OPTIONAL, + disableCG-RetransmissionMonitoring-r18 ENUMERATED {supported} OPTIONAL, + enhancedDRX-r18 ENUMERATED {supported} OPTIONAL, + pdu-SetDiscard-r18 ENUMERATED {supported} OPTIONAL, + psi-BasedDiscard-r18 ENUMERATED {supported} OPTIONAL, + ul-TrafficInfo-r18 ENUMERATED {supported} OPTIONAL, + aerialParameters-r18 AerialParameters-r18 OPTIONAL, + nonCriticalExtension SEQUENCE{ } OPTIONAL + } + +``` + +``` + +UE-NR-CapabilityAddXDD-Mode ::= SEQUENCE { + phy-ParametersXDD-Diff Phy-ParametersXDD-Diff OPTIONAL, + mac-ParametersXDD-Diff MAC-ParametersXDD-Diff OPTIONAL, + measAndMobParametersXDD-Diff MeasAndMobParametersXDD-Diff OPTIONAL +} + +UE-NR-CapabilityAddXDD-Mode-v1530 ::= SEQUENCE { + eutra-ParametersXDD-Diff EUTRA-ParametersXDD-Diff +} + +UE-NR-CapabilityAddFRX-Mode ::= SEQUENCE { + phy-ParametersFRX-Diff Phy-ParametersFRX-Diff OPTIONAL, + measAndMobParametersFRX-Diff MeasAndMobParametersFRX-Diff OPTIONAL +} + +UE-NR-CapabilityAddFRX-Mode-v1540 ::= SEQUENCE { + ims-ParametersFRX-Diff IMS-ParametersFRX-Diff OPTIONAL +} + +UE-NR-CapabilityAddFRX-Mode-v1610 ::= SEQUENCE { + powSav-ParametersFRX-Diff-r16 PowSav-ParametersFRX-Diff-r16 OPTIONAL, + mac-ParametersFRX-Diff-r16 MAC-ParametersFRX-Diff-r16 OPTIONAL +} + +BAP-Parameters-r16 ::= SEQUENCE { + flowControlBH-RLC-ChannelBased-r16 ENUMERATED {supported} OPTIONAL, + flowControlRouting-ID-Based-r16 ENUMERATED {supported} OPTIONAL +} + +BAP-Parameters-v1700 ::= SEQUENCE { + bapHeaderRewriting-Rerouting-r17 ENUMERATED {supported} OPTIONAL, + bapHeaderRewriting-Routing-r17 ENUMERATED {supported} OPTIONAL +} + +MBS-Parameters-r17 ::= SEQUENCE { + maxMRB-Add-r17 INTEGER (1..16) OPTIONAL +} + +-- TAG-UE-NR-CAPABILITY-STOP +-- ASN1STOP + +``` + +#### UE-NR-Capability field descriptions + +##### **featureSetCombinations** + +A list of *FeatureSetCombination*:s for *supportedBandCombinationList* in *UE-NR-Capability*. The *FeatureSetDownlink*:s and *FeatureSetUplink*:s referred to from these *FeatureSetCombination*:s are defined in the *featureSets* list in *UE-NR-Capability*. + +##### | | |--------------------------------------------------| | UE-NR-Capability-v1540 field descriptions | |--------------------------------------------------| + +###### | | |------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | fr1-fr2-Add-UE-NR-Capabilities
This instance of UE-NR-CapabilityAddFRX-Mode does not include any other fields than csi-RS-IM-ReceptionForFeedback/ csi-RS-ProcFrameworkForSRS/ csi-ReportFramework . | |------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +#### – ***UE-RadioPagingInfo*** + +The IE *UE-RadioPagingInfo* contains UE capability information needed for paging. + +#### ***UE-RadioPagingInfo* information element** + +``` +-- ASN1START +-- TAG-UE-RADIOPAGINGINFO-START + +UE-RadioPagingInfo-r17 ::= SEQUENCE { + -- R1 29-1: Paging enhancement + pei-SubgroupingSupportBandList-r17 SEQUENCE (SIZE (1..maxBands)) OF FreqBandIndicatorNR OPTIONAL, + ... +} + +-- TAG-UE-RADIOPAGINGINFO-STOP +-- ASN1STOP +``` + +### 6.3.4 Other information elements + +#### – ***AbsoluteTimeInfo*** + +The IE *AbsoluteTimeInfo* indicates an absolute time in a format YY-MM-DD HH:MM:SS and using BCD encoding. The first/ leftmost bit of the bit string contains the most significant bit of the most significant digit of the year and so on. + +#### ***AbsoluteTimeInfo* information element** + +``` +-- ASN1START +-- TAG-ABSOLUTETIMEINFO-START + +AbsoluteTimeInfo-r16 ::= BIT STRING (SIZE (48)) + +-- TAG-ABSOLUTETIMEINFO-STOP +-- ASN1STOP +``` + +#### — *AppLayerIdleInactiveConfig* + +The IE *AppLayerIdleInactiveConfig* indicates parameters specific to application layer measurements applicable to RRC\_IDLE/RRC\_INACTIVE. + +#### *AppLayerIdleInactiveConfig* information element + +``` +-- ASN1START +-- TAG-APPLAYERIDLEINACTIVECONFIG-START + +AppLayerIdleInactiveConfig-r18 ::= SEQUENCE { + configForRRc-IdleInactive-r18 ENUMERATED {true} OPTIONAL, -- Need M + qoe-Reference-r18 OCTET STRING (SIZE (6)) OPTIONAL, -- Need R + qoe-MeasurementType-r18 ENUMERATED {sbased, mbased} OPTIONAL, -- Need R + qoe-AreaScope-r18 Qoe-AreaScope-r18 OPTIONAL, -- Need R + mce-Id-r18 OCTET STRING (SIZE (1)) OPTIONAL, -- Need R + availableRAN-VisibleMetrics-r18 AvailableRAN-VisibleMetrics-r18 OPTIONAL, -- Need R + ... +} + +Qoe-AreaScope-r18 ::= CHOICE { + cellGlobalIdList CellGlobalIdList-r16, + trackingAreaCodeList TrackingAreaCodeList-r16, + trackingAreaIdentityList TrackingAreaIdentityList-r16, + plmn-IdentityList PLMN-IdentityList2-r16, + ... +} + +AvailableRAN-VisibleMetrics-r18 ::= SEQUENCE { + appLayerBufferLevelList-r18 ENUMERATED {true} OPTIONAL, -- Need N + playoutDelayForMediaStartup-r18 ENUMERATED {true} OPTIONAL, -- Need N + ... +} + +-- TAG-APPLAYERIDLEINACTIVECONFIG-STOP +-- ASN1STOP +``` + +| AppLayerIdleInactiveConfig field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| appLayerBufferLevelList
The field defines whether the buffer level for DASH streaming and VR service types can be collected as a RAN visible QoE metric from the UE. | +| configForRRc-IdleInactive
The field indicates whether the application layer measurement configuration is applicable to both RRC_IDLE and RRC_INACTIVE. The field is not configured if the application layer measurement configuration is only applicable to RRC_IDLE or only applicable to RRC_INACTIVE. If the field is not present, the UE assumes that the configuration is not applicable to RRC_IDLE and RRC_INACTIVE. | +| qoe-AreaScope
The field contains the area where the application layer measurement shall start if an application layer session starts. | +| qoe-MeasurementType
Indicates whether the application layer measurement is signalling based or management based. | +| qoe-Reference
Indicates the QoE Reference as defined in TS 28.405 [55], clause 5.2. | +| mce-id
The field contains the Measurement Collection Entity Id, see TS 28.405 [55]. | +| playoutDelayForMediaStartup
The field defines whether the playout delay for DASH streaming and VR service types can be collected as a RAN visible QoE metric from the UE. | + +#### – AppLayerMeasConfig + +The IE *AppLayerMeasConfig* indicates configuration of application layer measurements. + +#### AppLayerMeasConfig information element + +``` +-- ASN1START +-- TAG-APPLAYERMEASCONFIG-START + +AppLayerMeasConfig-r17 ::= + SEQUENCE { + measConfigAppLayerToAddModList-r17 SEQUENCE (SIZE (1..maxNrofAppLayerMeas-r17)) OF MeasConfigAppLayer-r17 OPTIONAL, -- Need N + measConfigAppLayerToReleaseList-r17 SEQUENCE (SIZE (1..maxNrofAppLayerMeas-r17)) OF MeasConfigAppLayerId-r17 OPTIONAL, -- Need N + rrc-SegAllowedSRB4-r17 ENUMERATED {enabled} OPTIONAL, -- Need R + ..., + [[ + rrc-SegAllowedSRB5-r18 ENUMERATED {enabled} OPTIONAL, -- Need R + idleInactiveReportAllowed-r18 ENUMERATED {enabled} OPTIONAL, -- Need R + ]] + } + +MeasConfigAppLayer-r17 ::= + SEQUENCE { + measConfigAppLayerId-r17 MeasConfigAppLayerId-r17, + measConfigAppLayerContainer-r17 OCTET STRING (SIZE (1..8000)) OPTIONAL, -- Need N + serviceType-r17 ENUMERATED {streaming, mtsi, vr, spare5, spare4, spare3, spare2, spare1} OPTIONAL, -- Need M + pauseReporting-r17 BOOLEAN OPTIONAL, -- Need M + transmissionOfSessionStartStop-r17 BOOLEAN OPTIONAL, -- Need M + ran-VisibleParameters-r17 SetupRelease {RAN-VisibleParameters-r17} OPTIONAL, -- Cond ServiceType + ..., + } +-- ASN1END +``` + +``` +[[ + reportingSRB-r18 ENUMERATED {srb4, srb5, spare2, spare1} OPTIONAL, -- Need M + appLayerMeasPriority-r18 INTEGER (1..16) OPTIONAL, -- Need M + appLayerIdleInactiveConfig-r18 AppLayerIdleInactiveConfig-r18 OPTIONAL -- Need M +]] +} + +RAN-VisibleParameters-r17 ::= SEQUENCE { + ran-VisiblePeriodicity-r17 ENUMERATED {ms120, ms240, ms480, ms640, ms1024} OPTIONAL, -- Need S + numberOfBufferLevelEntries-r17 INTEGER (1..8) OPTIONAL, -- Need R + reportPlayoutDelayForMediaStartup-r17 BOOLEAN OPTIONAL, -- Need M + ..., + [[ + ran-VisibleReportingSRB-r18 ENUMERATED {srb4, srb5, spare2, spare1} OPTIONAL -- Need M + ]] +} + +-- TAG-APPLAYERMEASCONFIG-STOP +-- ASN1STOP +``` + +| AppLayerMeasConfig field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| appLayerMeasPriority
The field indicates the priority of the application layer measurement configuration, where a higher value indicates lower priority. If the field is not configured, the application layer measurement configuration has the lowest priority. | +| idleInactiveReportAllowed
The field indicates whether transmission of application layer measurement reports collected in RRC_IDLE and/or RRC_INACTIVE is allowed and if transmission of application layer measurement configurations applicable to RRC_IDLE and/or RRC_INACTIVE is allowed. If the field is not configured, transmission of application layer measurement reports and/or configurations for RRC_IDLE/RRC_INACTIVE are not allowed. | +| measConfigAppLayerContainer
The field contains configuration of application layer measurements, see Annex L (normative) in TS 26.247 [68], clause 16.5 in TS 26.114 [69] and TS 26.118 [70]. | +| measConfigAppLayerId
The field contains the identity of the application layer measurements. When application layer measurements are configured for an SCG, the measConfigAppLayerId is obtained according to TS 38.423 [37], clauses 8.3.1 and 8.3.3. | +| pauseReporting
The field indicates whether the transmission of measReportAppLayerContainer is paused or not. Value true indicates the transmission of measReportAppLayerContainer is paused; value false indicates the transmission of measReportAppLayerContainer is not paused. | +| ran-VisibleParameters
The field indicates whether RAN visible application layer measurements shall be reported or not. | +| ran-VisibleReportingSRB
The field indicates the SRB to be used for transmission of RAN visible application layer measurement reports. | +| reportingSRB
The field indicates the SRB to be used for transmission of encapsulated application layer measurement reports. If application layer measurement reports are received and the configured SRB is not available, the UE stores the reports until the SRB is available or the QoE configuration is released. | +| rrc-SegAllowedSRB4
This field indicates that RRC segmentation of MeasurementReportAppLayer is enabled on SRB4. It may be present only if the UE supports RRC segmentation of the MeasurementReportAppLayer message. | +| rrc-SegAllowedSRB5
This field indicates that RRC segmentation of MeasurementReportAppLayer is enabled on SRB5. The field is configured for an SCG. It may be present only if the UE supports RRC segmentation of the MeasurementReportAppLayer message. | +| serviceType
Indicates the type of application layer measurement. Value streaming indicates Quality of Experience Measurement Collection for streaming services (see TS 26.247 [68]), value mtsi indicates Quality of Experience Measurement Collection for MTSI (see TS 26.114 [69]) and value vr indicates Quality of Experience Measurement Collection for VR service (see TS 26.118 [70]). The network always configures serviceType when application layer measurements are initially configured and at fullConfig . | +| transmissionOfSessionStartStop
Value true indicates that the UE shall transmit indications when the measurement session in the application layer starts and stops. Value false indicates that the UE shall not transmit any session status indications. The UE transmits a session start indication upon configuration of this field set to value true if a session already has started in the application layer. | + +| RAN-VisibleParameters field descriptions | | +|-------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| numberOfBufferLevelEntries | The field contains the maximum number of buffer level entries that can be reported for RAN visible application layer measurements. This field is also used by application layer to calculate the interval of RAN visible buffer level measurement, which is equal to the periodicity of RAN visible application layer measurements reporting divided by numberOfBufferLevelEntries . | +| ran-VisiblePeriodicity | The field indicates the periodicity of RAN visible application layer measurements reporting. Value ms120 indicates 120 ms, value ms240 indicates 240 ms and so on. If this field is absent, the periodicity of RAN visible application layer measurements reporting is the same as the reporting periodicity indicated in measConfigAppLayerContainer . | +| reportPlayoutDelayForMediaStartup | The field indicates whether the UE shall report Playout Delay for Media Startup for RAN visible application layer measurements. | + +| Conditional Presence | Explanation | +|-----------------------------|--------------------------------------------------------------------------------------------------------------------------------------| +| ServiceType | This field is optionally present, Need M, when serviceType is set to streaming or vr . Otherwise, it is absent. | + +#### — *AreaConfiguration* + +The *AreaConfiguration* indicates area for which UE is requested to perform measurement logging. If not configured, measurement logging is not restricted to specific cells or tracking areas but applies as long as the RPLMN is contained in *plmn-IdentityList* stored in *VarLogMeasReport*. + +#### ***AreaConfiguration* information element** + +``` +-- ASN1START +-- TAG-AREACONFIGURATION-START + +AreaConfiguration-r16 ::= SEQUENCE { + areaConfig-r16 AreaConfig-r16, + interFreqTargetList-r16 SEQUENCE(SIZE (1..maxFreq)) OF InterFreqTargetInfo-r16 OPTIONAL -- Need R +} + +AreaConfiguration-r17 ::= SEQUENCE { + areaConfig-r17 AreaConfig-r16 OPTIONAL, -- Need R + interFreqTargetList-r17 SEQUENCE(SIZE (1..maxFreq)) OF InterFreqTargetInfo-r16 OPTIONAL -- Need R +} + +AreaConfiguration-v1800 ::= SEQUENCE { + cag-ConfigList-r18 CAG-ConfigList-r18 OPTIONAL, -- Need R + snpn-ConfigList-r18 SNPN-ConfigList-r18 OPTIONAL -- Need R +} + +AreaConfig-r16 ::= CHOICE { + cellGlobalIdList-r16 CellGlobalIdList-r16, + trackingAreaCodeList-r16 TrackingAreaCodeList-r16, + trackingAreaIdentityList-r16 TrackingAreaIdentityList-r16 +} +``` + +``` + +} + +InterFreqTargetInfo-r16 := SEQUENCE { + dl-CarrierFreq-r16 ARFCN-ValueNR, + cellList-r16 SEQUENCE (SIZE (1..32)) OF PhysCellId +} OPTIONAL -- Need R + +CellGlobalIdList-r16 := SEQUENCE (SIZE (1..32)) OF CGI-Info-Logging-r16 + +TrackingAreaCodeList-r16 := SEQUENCE (SIZE (1..8)) OF TrackingAreaCode + +TrackingAreaIdentityList-r16 := SEQUENCE (SIZE (1..8)) OF TrackingAreaIdentity-r16 + +TrackingAreaIdentity-r16 := SEQUENCE { + plmn-Identity-r16 PLMN-Identity, + trackingAreaCode-r16 TrackingAreaCode +} + +CAG-ConfigList-r18 := SEQUENCE (SIZE (1..maxNPN-r16)) OF CAG-Config-r18 + +CAG-Config-r18 := SEQUENCE { + plmn-Identity-r18 PLMN-Identity, + cag-IdentityList-r18 SEQUENCE (SIZE (1..maxNPN-r16)) OF CAG-IdentityInfo-r16 +} + +SNPN-ConfigList-r18 := CHOICE { + snpn-ConfigCellIdList-r18 SNPN-ConfigCellIdList-r18, + snpn-ConfigTAIList-r18 SNPN-ConfigTAIList-r18, + snpn-ConfigIDList-r18 SNPN-ConfigIDList-r18 +} + +SNPN-ConfigCellIdList-r18 := SEQUENCE (SIZE (1..maxSNPN-ConfigCellId-r18)) OF SNPN-ConfigCellId-r18 + +SNPN-ConfigCellId-r18 := SEQUENCE { + cgi-Identity-r18 CGI-Info-Logging-r16, + nid-IdentityList-r18 SEQUENCE (SIZE (1..maxNPN-r16)) OF NID-r16 +} + +SNPN-ConfigTAIList-r18 := SEQUENCE (SIZE (1..maxSNPN-ConfigTAI-r18)) OF SNPN-ConfigTAI-r18 + +SNPN-ConfigTAI-r18 := SEQUENCE { + tai-Identity-r18 TrackingAreaIdentity-r16, + nid-IdentityList-r18 SEQUENCE (SIZE (1..maxNPN-r16)) OF NID-r16 +} + +SNPN-ConfigIDList-r18 := SEQUENCE (SIZE (1..maxSNPN-ConfigID-r18)) OF SNPN-ConfigID-r18 + +SNPN-ConfigID-r18 := SEQUENCE { + plmn-Identity-r18 PLMN-Identity, + nid-IdentityList-r18 SEQUENCE (SIZE (1..maxNPN-r16)) OF NID-r16 +} + +``` + +``` +-- TAG-AREACONFIGURATION-STOP +-- ASN1STOP +``` + +#### AreaConfiguration field descriptions + +##### ***cag-IdentityList*** + +The *cag-IdentityList* contains one or more CAG IDs. All CAG IDs associated to the same PLMN ID are listed in the same *cag-IdentityList* entry. + +##### ***InterFreqTargetInfo*** + +If configured, it indicates the neighbouring frequency and cells for which UE is requested to perform measurement logging. It can include sync raster or non-sync raster frequencies. + +##### ***nid-IdentityList*** + +The *nid-IdentityList* contains one or more NID. All NIDs associated to the same PLMN ID are listed in the same *nid-IdentityList* entry. + +#### — ***BT-NameList*** + +The IE *BT-NameList* is used to indicate the names of the Bluetooth beacon which the UE is configured to measure. + +#### ***BT-NameList* information element** + +``` +-- ASN1START +-- TAG-BTNAMELIST-START + +BT-NameList-r16 ::= + SEQUENCE (SIZE (1..maxBT-Name-r16)) OF BT-Name-r16 + +BT-Name-r16 ::= + OCTET STRING (SIZE (1..248)) + +-- TAG-BTNAMELIST-STOP +-- ASN1STOP +``` + +#### ***BT-NameList* field descriptions** + +##### ***bt-Name*** + +If configured, the UE only performs Bluetooth measurements according to the names identified. For each name, it refers to LOCAL NAME defined in Bluetooth specification [51]. + +#### — ***DedicatedInfoF1c*** + +The IE *DedicatedInfoF1c* is used to transfer IAB-DU specific F1-C related information between the network and the IAB node. The carried information consists of F1AP message encapsulated in SCTP/IP or F1-C related (SCTP)/IP packet, see TS 38.472 [64]. The RRC layer is transparent for this information. + +#### ***DedicatedInfoF1c* information element** + +``` +-- ASN1START +``` + +``` +-- TAG-DEDICATEDINFO1C-START +DedicatedInfoFlc-r17 := OCTET STRING +-- TAG-DEDICATEDINFO1C-STOP +-- ASN1STOP +``` + +#### – *EUTRA-AllowedMeasBandwidth* + +The IE *EUTRA-AllowedMeasBandwidth* is used to indicate the maximum allowed measurement bandwidth on a carrier frequency as defined by the parameter Transmission Bandwidth Configuration "NRB" in TS 36.104 [33]. The values *mbw6*, *mbw15*, *mbw25*, *mbw50*, *mbw75*, *mbw100* indicate 6, 15, 25, 50, 75 and 100 resource blocks, respectively. + +#### ***EUTRA-AllowedMeasBandwidth* information element** + +``` +-- ASN1START +-- TAG-EUTRA-ALLOWEDMEASBANDWIDTH-START +EUTRA-AllowedMeasBandwidth := ENUMERATED {mbw6, mbw15, mbw25, mbw50, mbw75, mbw100} +-- TAG-EUTRA-ALLOWEDMEASBANDWIDTH-STOP +-- ASN1STOP +``` + +#### – *EUTRA-MBSFN-SubframeConfigList* + +The IE *EUTRA-MBSFN-SubframeConfigList* is used to define an E-UTRA MBSFN subframe pattern (for the purpose of NR rate matching). + +#### ***EUTRA-MBSFN-SubframeConfigList* information element** + +``` +-- ASN1START +-- TAG-EUTRA-MBSFN-SUBFRAMECONFIGLIST-START +EUTRA-MBSFN-SubframeConfigList := SEQUENCE (SIZE (1..maxMBSFN-Allocations)) OF EUTRA-MBSFN-SubframeConfig +EUTRA-MBSFN-SubframeConfig := SEQUENCE { + radioframeAllocationPeriod ENUMERATED {n1, n2, n4, n8, n16, n32}, + radioframeAllocationOffset INTEGER (0..7), + subframeAllocation1 CHOICE { + oneFrame BIT STRING (SIZE(6)), + fourFrames BIT STRING (SIZE(24)) + }, + subframeAllocation2 CHOICE { + oneFrame BIT STRING (SIZE(2)), + fourFrames BIT STRING (SIZE(8)) + } OPTIONAL, -- Need R + ... +} +``` + +``` +-- TAG-EUTRA-MBSFN-SUBFRAMECONFIGLIST-STOP +-- ASN1STOP +``` + +| EUTRA-MBSFN-SubframeConfig field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| radioframeAllocationOffset
Field as defined in MBSFN-SubframeConfig in TS 36.331 [10]. | +| radioframeAllocationPeriod
Field as defined in MBSFN-SubframeConfig in TS 36.331 [10], where SFN refers to the SFN of the NR serving cell. | +| subframeAllocation1
Field as defined in MBSFN-SubframeConfig in TS 36.331 [10], where the UE assumes the duplex mode (FDD or TDD) of the NR cell for which the E-UTRA-MBSFN-SubframeConfig is provided. | +| subframeAllocation2
Field as defined in MBSFN-SubframeConfig-v1430 in TS 36.331 [10], where the UE assumes the duplex mode (FDD or TDD) of the NR cell for which the E-UTRA-MBSFN-SubframeConfig is provided. | + +#### — **EUTRA-MultiBandInfoList** + +The IE *EUTRA-MultiBandInfoList* indicates the list of frequency bands in addition to the band represented by *CarrierFreq* for which cell reselection parameters are common, and a list of *additionalPmax* and *additionalSpectrumEmission*. + +#### **EUTRA-MultiBandInfoList information element** + +``` +-- ASN1START +-- TAG-EUTRA-MULTIBANDINFOLIST-START + +EUTRA-MultiBandInfoList ::= SEQUENCE (SIZE (1..maxMultiBands)) OF EUTRA-MultiBandInfo + +EUTRA-MultiBandInfo ::= SEQUENCE { + eutra-FreqBandIndicator FreqBandIndicatorEUTRA, + eutra-NS-PmaxList EUTRA-NS-PmaxList OPTIONAL -- Need R +} + +-- TAG-EUTRA-MULTIBANDINFOLIST-STOP +-- ASN1STOP +``` + +#### — **EUTRA-MultiBandInfoListAerial** + +The IE *EUTRA-MultiBandInfoListAerial* indicates the list of frequency bands for aerial UE in addition to the band represented by *CarrierFreq* for which cell reselection parameters are common, and a list of *additionalPmax* and *additionalSpectrumEmission*. + +#### EUTRA-MultiBandInfoListAerial information element + +``` +-- ASN1START +-- TAG-EUTRA-MULTIBANDINFOLISTAERIAL-START + +EUTRA-MultiBandInfoListAerial-r18 ::= SEQUENCE (SIZE (1..maxMultiBands)) OF EUTRA-MultiBandInfoAerial-r18 + +EUTRA-MultiBandInfoAerial-r18 ::= SEQUENCE { + eutra-FreqBandIndicator-r18 FreqBandIndicatorEUTRA, + eutra-NS-PmaxListAerial-r18 EUTRA-NS-PmaxList OPTIONAL -- Need R +} + +-- TAG-EUTRA-MULTIBANDINFOLISTAERIAL-STOP +-- ASN1STOP +``` + +#### — EUTRA-NS-PmaxList + +The IE *EUTRA-NS-PmaxList* concerns a list of *additionalPmax* and *additionalSpectrumEmission*, as defined in TS 36.101 [22], table 6.2.4-1 for UEs neither in CE nor BL UEs, TS 36.101 [22], table 6.2.4E-1 for UEs in CE or BL UEs, and TS 36.101 [22], table TBD for Aerial UEs, for a given frequency band. + +#### EUTRA-NS-PmaxList information element + +``` +-- ASN1START +-- TAG-EUTRA-NS-PMAXLIST-START + +EUTRA-NS-PmaxList ::= SEQUENCE (SIZE (1..maxEUTRA-NS-Pmax)) OF EUTRA-NS-PmaxValue + +EUTRA-NS-PmaxValue ::= SEQUENCE { + additionalPmax INTEGER (-30..33) OPTIONAL, -- Need R + additionalSpectrumEmission INTEGER (1..288) OPTIONAL -- Need R +} + +-- TAG-EUTRA-NS-PMAXLIST-STOP +-- ASN1STOP +``` + +#### — EUTRA-PhysCellId + +The IE *EUTRA-PhysCellId* is used to indicate the physical layer identity of the cell, as defined in TS 36.211 [31]. + +#### EUTRA-PhysCellId information element + +``` +-- ASN1START +-- TAG-EUTRA-PHYSCELLID-START + +EUTRA-PhysCellId ::= INTEGER (0..503) +``` + +``` +-- TAG-EUTRA-PHYCELLID-STOP +-- ASN1STOP +``` + +#### – *EUTRA-PhysCellIdRange* + +The IE *EUTRA-PhysCellIdRange* is used to encode either a single or a range of physical cell identities. The range is encoded by using a *start* value and by indicating the number of consecutive physical cell identities (including *start*) in the range. For fields comprising multiple occurrences of *EUTRA-PhysCellIdRange*, NW may configure overlapping ranges of physical cell identities. + +#### *EUTRA-PhysCellIdRange* information element + +``` +-- ASN1START +-- TAG-EUTRA-PHYCELLIDRANGE-START + +EUTRA-PhysCellIdRange ::= SEQUENCE { + start EUTRA-PhysCellId, + range ENUMERATED {n4, n8, n12, n16, n24, n32, n48, n64, n84, n96, + n128, n168, n252, n504, spare2, spare1} + OPTIONAL -- Need N +} + +-- TAG-EUTRA-PHYCELLIDRANGE-STOP +-- ASN1STOP +``` + +#### – *EUTRA-PresenceAntennaPort1* + +The IE *EUTRA-PresenceAntennaPort1* is used to indicate whether all the neighbouring cells use Antenna Port 1. When set to *true*, the UE may assume that at least two cell-specific antenna ports are used in all neighbouring cells. + +#### *EUTRA-PresenceAntennaPort1* information element + +``` +-- ASN1START +-- TAG-EUTRA-PRESENCEANTENNAPORT1-START + +EUTRA-PresenceAntennaPort1 ::= BOOLEAN + +-- TAG-EUTRA-PRESENCEANTENNAPORT1-STOP +-- ASN1STOP +``` + +#### – *EUTRA-Q-OffsetRange* + +The IE *EUTRA-Q-OffsetRange* is used to indicate a cell, or frequency specific offset to be applied when evaluating triggering conditions for measurement reporting. The value in dB. Value *dB-24* corresponds to -24 dB, value *dB-22* corresponds to -22 dB and so on. + +#### **EUTRA-Q-OffsetRange information element** + +``` + +-- ASN1START +-- TAG-EUTRA-Q-OFFSETRANGE-START + +EUTRA-Q-OffsetRange ::= ENUMERATED { + dB-24, dB-22, dB-20, dB-18, dB-16, dB-14, + dB-12, dB-10, dB-8, dB-6, dB-5, dB-4, dB-3, + dB-2, dB-1, dB0, dB1, dB2, dB3, dB4, dB5, + dB6, dB8, dB10, dB12, dB14, dB16, dB18, + dB20, dB22, dB24} + +-- TAG-EUTRA-Q-OFFSETRANGE-STOP +-- ASN1STOP + +``` + +#### — IAB-IP-Address + +The IE *IAB-IP-Address* is used to indicate the IP address/prefix. + +#### **IAB-IP-Address information element** + +``` + +-- ASN1START +-- TAG-IABIPADDRESS-START + +IAB-IP-Address-r16 ::= CHOICE { + IPv4-Address-r16 BIT STRING (SIZE(32)), + IPv6-Address-r16 BIT STRING (SIZE(128)), + IPv6-Prefix-r16 BIT STRING (SIZE(64)), + ... +} + +-- TAG-IABIPADDRESS-STOP +-- ASN1STOP + +``` + +| IAB-IP-Address field descriptions | +|-----------------------------------------------------------------------------------------| +| IPv4-Address
This field is used to provide the allocated IPv4 address. | +| IPv6-Address
This field is used to provide the allocated IPv6 address. | +| IPv6-Prefix
This field is used to provide the allocated IPv6 prefix. | + +#### — *IAB-IP-AddressIndex* + +The IE *IAB-IP-AddressIndex* is used to identify a configuration of an IP address. + +#### *IAB-IP-AddressIndex* information element + +``` +-- ASN1START +-- TAG-IABIPADDRESSINDEX-START + +IAB-IP-AddressIndex-r16 ::= INTEGER (1..maxIAB-IP-Address-r16) + +-- TAG-IABIPADDRESSINDEX-STOP +-- ASN1STOP +``` + +#### — *IAB-IP-Usage* + +The IE *IAB-IP-Usage* is used to indicate the usage of the assigned IP address/prefix. + +#### *IAB-IP-Usage* information element + +``` +-- ASN1START +-- TAG-IAB-IP-USAGE-START + +IAB-IP-Usage-r16 ::= ENUMERATED {f1-C, f1-U, non-F1, spare} + +-- TAG-IAB-IP-USAGE-STOP +-- ASN1STOP +``` + +#### — *LoggingDuration* + +The *LoggingDuration* indicates the duration for which UE is requested to perform measurement logging. Value min10 corresponds to 10 minutes, value min20 corresponds to 20 minutes and so on. + +#### *LoggingDuration* information element + +``` +-- ASN1START +-- TAG-LOGGINGDURATION-START + +LoggingDuration-r16 ::= ENUMERATED { + min10, min20, min40, min60, min90, min120, spare2, spare1} + +-- TAG-LOGGINGDURATION-STOP +-- ASN1STOP +``` + +#### – *LoggingInterval* + +The *LoggingInterval* indicates the periodicity for logging measurement results. Value ms1280 corresponds to 1.28s, value ms2560 corresponds to 2.56s and so on. Value infinity means it is equal to the configured value of the *LoggingDuration* IE. + +#### *LoggingInterval* information element + +``` +-- ASN1START +-- TAG-LOGGINGINTERVAL-START + +LoggingInterval-r16 ::= ENUMERATED { + ms320, ms640, ms1280, ms2560, ms5120, ms10240, ms20480, + ms30720, ms40960, ms61440 , infinity} + +-- TAG-LOGGINGINTERVAL-STOP +-- ASN1STOP +``` + +#### – *LogMeasResultListBT* + +The IE *LogMeasResultListBT* covers measured results for Bluetooth. + +#### *LogMeasResultListBT* information element + +``` +-- ASN1START +-- TAG-LOGMEASRESULTLISTBT-START + +LogMeasResultListBT-r16 ::= SEQUENCE (SIZE (1..maxBT-IdReport-r16)) OF LogMeasResultBT-r16 + +LogMeasResultBT-r16 ::= SEQUENCE { + bt-Addr-r16 BIT STRING (SIZE (48)), + rssi-BT-r16 INTEGER (-128..127) OPTIONAL, + ... +} + +-- TAG-LOGMEASRESULTLISTBT-STOP +-- ASN1STOP +``` + +#### *LogMeasResultListBT* field descriptions + +| | +|----------------------------------------------------------------------------------------------------------------------------------------| +| bt-Addr
This field indicates the Bluetooth public address of the Bluetooth beacon as defined in TS 37.355 [49]. | +| rssi-BT
This field provides the beacon received signal strength indicator (RSSI) in dBm as defined in TS 37.355 [49]. | + +#### LogMeasResultListWLAN + +The IE *LogMeasResultListWLAN* covers measured results for WLAN. + +#### LogMeasResultListWLAN information element + +``` +-- ASN1START +-- TAG-LOGMEASRESULTLISTWLAN-START + +LogMeasResultListWLAN-r16 ::= SEQUENCE (SIZE (1..maxWLAN-Id-Report-r16)) OF LogMeasResultWLAN-r16 + +LogMeasResultWLAN-r16 ::= SEQUENCE { + wlan-Identifiers-r16 WLAN-Identifiers-r16, + rssiWLAN-r16 WLAN-RSSI-Range-r16 OPTIONAL, + rtt-WLAN-r16 WLAN-RTT-r16 OPTIONAL, + ... +} + +WLAN-Identifiers-r16 ::= SEQUENCE { + ssid-r16 OCTET STRING (SIZE (1..32)) OPTIONAL, + bssid-r16 OCTET STRING (SIZE (6)) OPTIONAL, + hssid-r16 OCTET STRING (SIZE (6)) OPTIONAL, + ... +} + +WLAN-RSSI-Range-r16 ::= INTEGER(0..141) + +WLAN-RTT-r16 ::= SEQUENCE { + rttValue-r16 INTEGER (0..16777215), + rttUnits-r16 ENUMERATED { + microseconds, + hundredsofnanoseconds, + tensofnanoseconds, + nanoseconds, + tenthsofnanoseconds, + ...}, + rttAccuracy-r16 INTEGER (0..255) OPTIONAL, + ... +} + +-- TAG-LOGMEASRESULTLISTWLAN-STOP +-- ASN1STOP +``` + +#### LogMeasResultListWLAN field descriptions + +| | | +|--------------|---------------------------------------------------------------------------------------| +| Bssid | Basic Service Set Identifier (BSSID) defined in IEEE 802.11-2012 [50]. | +| Hssid | Homogenous Extended Service Set Identifier (HESSID) defined in IEEE 802.11-2012 [50]. | + +| LogMeasResultListWLAN field descriptions | | +|-------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| rssiWLAN | Measured WLAN RSSI result in dBm. The IE WLAN-RSSI-Range specifies the value range used in WLAN RSSI measurements and thresholds. Integer value for WLAN RSSI measurements is according to mapping table in TS 36.133 [40]. Value 0 corresponds to -infinity, value 1 to -100dBm, value 2 to -99dBm, and so on (i.e. in steps of 1dBm) until value 140, which corresponds to 39dBm, while value 141 corresponds to +infinity. | +| rtt-WLAN | This field provides the measured roundtrip time between the target device and WLAN AP and optionally the accuracy expressed as the standard deviation of the delay. Units for each of these are 1000ns, 100ns, 10ns, 1ns, and 0.1ns as defined in TS 37.355 [49]. | +| rttValue | This field specifies the Round Trip Time (RTT) measurement between the target device and WLAN AP in units given by the field rttUnits as defined in TS 37.355 [49]. | +| rttUnits | This field specifies the Units for the fields rttValue and rttAccuracy. The available Units are 1000ns, 100ns, 10ns, 1ns, and 0.1ns as defined in TS 37.355 [49]. | +| rttAccuracy | This field provides the estimated accuracy of the provided rttValue expressed as the standard deviation in units given by the field rttUnits as defined in TS 37.355 [49]. | +| Ssid | Service Set Identifier (SSID) defined in IEEE 802.11-2012 [50]. | +| Wlan-Identifiers | Indicates the WLAN parameters used for identification of the WLAN for which the measurement results are applicable. | + +#### — *MeasConfigAppLayerId* + +The IE *MeasConfigAppLayerId* identifies the application layer measurement. + +#### ***MeasConfigAppLayerId* information element** + +``` +-- ASN1START +-- TAG-MEASCONFIGAPPLAYERID-START + +MeasConfigAppLayerId-r17 ::= INTEGER (0..maxNrofAppLayerMeas-1-r17) + +-- TAG-MEASCONFIGAPPLAYERID-STOP +-- ASN1STOP +``` + +#### — *OtherConfig* + +The IE *OtherConfig* contains configuration related to miscellaneous other configurations. + +#### ***OtherConfig* information element** + +``` +-- ASN1START +-- TAG-OTHERCONFIG-START + +OtherConfig ::= SEQUENCE { +``` + +``` + +delayBudgetReportingConfig CHOICE{ + release NULL, + setup SEQUENCE{ + delayBudgetReportingProhibitTimer ENUMERATED {s0, s0dot4, s0dot8, s1dot6, s3, s6, s12, s30} + } +} +OPTIONAL -- Need M + +OtherConfig-v1540 ::= SEQUENCE { + overheatingAssistanceConfig SetupRelease {OverheatingAssistanceConfig} + ... +} +OPTIONAL, -- Need M + +OtherConfig-v1610 ::= SEQUENCE { + idc-AssistanceConfig-r16 SetupRelease {IDC-AssistanceConfig-r16} OPTIONAL, -- Need M + drx-PreferenceConfig-r16 SetupRelease {DRX-PreferenceConfig-r16} OPTIONAL, -- Need M + maxBW-PreferenceConfig-r16 SetupRelease {MaxBW-PreferenceConfig-r16} OPTIONAL, -- Need M + maxCC-PreferenceConfig-r16 SetupRelease {MaxCC-PreferenceConfig-r16} OPTIONAL, -- Need M + maxMIMO-LayerPreferenceConfig-r16 SetupRelease {MaxMIMO-LayerPreferenceConfig-r16} OPTIONAL, -- Need M + minSchedulingOffsetPreferenceConfig-r16 SetupRelease {MinSchedulingOffsetPreferenceConfig-r16} OPTIONAL, -- Need M + releasePreferenceConfig-r16 SetupRelease {ReleasePreferenceConfig-r16} OPTIONAL, -- Need M + referenceTimePreferenceReporting-r16 ENUMERATED {true} OPTIONAL, -- Need R + btNameList-r16 SetupRelease {BT-NameList-r16} OPTIONAL, -- Need M + wlanNameList-r16 SetupRelease {WLAN-NameList-r16} OPTIONAL, -- Need M + sensorNameList-r16 SetupRelease {Sensor-NameList-r16} OPTIONAL, -- Need M + obtainCommonLocation-r16 ENUMERATED {true} OPTIONAL, -- Need R + sl-AssistanceConfigNR-r16 ENUMERATED{true} OPTIONAL -- Need R +} + +OtherConfig-v1700 ::= SEQUENCE { + ul-GapFR2-PreferenceConfig-r17 ENUMERATED {true} OPTIONAL, -- Need R + musim-GapAssistanceConfig-r17 SetupRelease {MUSIM-GapAssistanceConfig-r17} OPTIONAL, -- Need M + musim-LeaveAssistanceConfig-r17 SetupRelease {MUSIM-LeaveAssistanceConfig-r17} OPTIONAL, -- Need M + successHO-Config-r17 SetupRelease {SuccessHO-Config-r17} OPTIONAL, -- Need M + maxBW-PreferenceConfigFR2-2-r17 ENUMERATED {true} OPTIONAL, -- Cond maxBW + maxMIMO-LayerPreferenceConfigFR2-2-r17 ENUMERATED {true} OPTIONAL, -- Cond maxMIMO + minSchedulingOffsetPreferenceConfigExt-r17 ENUMERATED {true} OPTIONAL, -- Cond minOffset + rlm-RelaxationReportingConfig-r17 SetupRelease {RLM-RelaxationReportingConfig-r17} OPTIONAL, -- Need M + bfd-RelaxationReportingConfig-r17 SetupRelease {BFD-RelaxationReportingConfig-r17} OPTIONAL, -- Need M + scg-DeactivationPreferenceConfig-r17 SetupRelease {SCG-DeactivationPreferenceConfig-r17} OPTIONAL, -- Cond SCG + rrm-MeasRelaxationReportingConfig-r17 SetupRelease {RRM-MeasRelaxationReportingConfig-r17} OPTIONAL, -- Need M + propDelayDiffReportConfig-r17 SetupRelease {PropDelayDiffReportConfig-r17} OPTIONAL -- Need M +} + +OtherConfig-v1800 ::= SEQUENCE { + idc-AssistanceConfig-v1800 SetupRelease {IDC-AssistanceConfig-v1800} OPTIONAL, -- Need M + multiRx-PreferenceReportingConfigFR2-r18 SetupRelease {MultiRx-PreferenceReportingConfigFR2-r18} OPTIONAL, -- Need M + uav-FlightPathAvailabilityConfig-r18 ENUMERATED {true} OPTIONAL, -- Need R + ul-TrafficInfoReportingConfig-r18 SetupRelease {UL-TrafficInfoReportingConfig-r18} OPTIONAL, -- Need M + n3c-RelayUE-InfoReportConfig-r18 ENUMERATED {true} OPTIONAL, -- Need R + successPSCell-Config-r18 SetupRelease {SuccessPSCell-Config-r18} OPTIONAL, -- Need M +} + +``` + +``` + +sn-InitiatedPSCellChange-r18 ENUMERATED {true} OPTIONAL, --Need M +musim-GapPriorityAssistanceConfig-r18 ENUMERATED {true} OPTIONAL, -- Cond musimGapConfig +musim-CapabilityRestrictionConfig-r18 SetupRelease {MUSIM-CapabilityRestrictionConfig-r18} OPTIONAL -- Need M +} + +IDC-AssistanceConfig-v1800 ::= SEQUENCE { + idc-FDM-AssistanceConfig-r18 SetupRelease {IDC-FDM-AssistanceConfig-r18} OPTIONAL, -- Need M + idc-TDM-AssistanceConfig-r18 ENUMERATED {setup} OPTIONAL -- Cond FDM +} + +MultiRx-PreferenceReportingConfigFR2-r18 ::= SEQUENCE { + multiRx-PreferenceReportingConfigFR2ProhibitTimer-r18 ENUMERATED { + s0, s0dot5, s1, s2, s3, s4, s5, s6, s7, + s8, s9, s10, s20, s30, spare2, spare1} +} + +CandidateServingFreqListNR-r16 ::= SEQUENCE (SIZE (1..maxFreqIDC-r16)) OF ARFCN-ValueNR + +MUSIM-GapAssistanceConfig-r17 ::= SEQUENCE { + musim-GapProhibitTimer-r17 ENUMERATED {s0, s0dot1, s0dot2, s0dot3, s0dot4, s0dot5, s1, s2, s3, s4, s5, s6, s7, s8, s9, s10} +} + +MUSIM-LeaveAssistanceConfig-r17 ::= SEQUENCE { + musim-LeaveWithoutResponseTimer-r17 ENUMERATED {ms10, ms20, ms40, ms60, ms80, ms100, spare2, spare1} +} + +MUSIM-CapabilityRestrictionConfig-r18 ::= SEQUENCE { + musim-CandidateBandList-r18 MUSIM-CandidateBandList-r18 OPTIONAL, -- Need M + musim-WaitTimer-r18 ENUMERATED {ms10, ms20, ms40, ms60, ms80, ms100, spare2, spare1}, + musim-ProhibitTimer-r18 ENUMERATED {ms0, ms10, ms20, ms40, ms60, ms80, spare2, spare1} +} + +MUSIM-CandidateBandList-r18 ::= SEQUENCE (SIZE (1..maxCandidateBandIndex-r18)) OF FreqBandIndicatorNR + +SuccessHO-Config-r17 ::= SEQUENCE { + thresholdPercentageT304-r17 ENUMERATED {p40, p60, p80, spare5, spare4, spare3, spare2, spare1} OPTIONAL, --Need R + thresholdPercentageT310-r17 ENUMERATED {p40, p60, p80, spare5, spare4, spare3, spare2, spare1} OPTIONAL, --Need R + thresholdPercentageT312-r17 ENUMERATED {p20, p40, p60, p80, spare4, spare3, spare2, spare1} OPTIONAL, --Need R + sourceDAPS-FailureReporting-r17 ENUMERATED {true} OPTIONAL, --Need R + ... +} + +SuccessPSCell-Config-r18 ::= SEQUENCE { + thresholdPercentageT304-SCG-r18 ENUMERATED {p40, p60, p80, spare5, spare4, spare3, spare2, spare1} OPTIONAL, --Need R + thresholdPercentageT310-SCG-r18 ENUMERATED {p40, p60, p80, spare5, spare4, spare3, spare2, spare1} OPTIONAL, --Need R + thresholdPercentageT312-SCG-r18 ENUMERATED {p20, p40, p60, p80, spare4, spare3, spare2, spare1} OPTIONAL, --Need R + ... +} + +OverheatingAssistanceConfig ::= SEQUENCE { + +``` + +``` + + overheatingIndicationProhibitTimer ENUMERATED {s0, s0dot5, s1, s2, s5, s10, s20, s30, + s60, s90, s120, s300, s600, spare3, spare2, spare1} +} + +IDC-AssistanceConfig-r16 ::= SEQUENCE { + candidateServingFreqListNR-r16 CandidateServingFreqListNR-r16 OPTIONAL, -- Need R + ... +} + +DRX-PreferenceConfig-r16 ::= SEQUENCE { + drx-PreferenceProhibitTimer-r16 ENUMERATED { + s0, s0dot5, s1, s2, s3, s4, s5, s6, s7, + s8, s9, s10, s20, s30, spare2, spare1} +} + +MaxBW-PreferenceConfig-r16 ::= SEQUENCE { + maxBW-PreferenceProhibitTimer-r16 ENUMERATED { + s0, s0dot5, s1, s2, s3, s4, s5, s6, s7, + s8, s9, s10, s20, s30, spare2, spare1} +} + +MaxCC-PreferenceConfig-r16 ::= SEQUENCE { + maxCC-PreferenceProhibitTimer-r16 ENUMERATED { + s0, s0dot5, s1, s2, s3, s4, s5, s6, s7, + s8, s9, s10, s20, s30, spare2, spare1} +} + +MaxMIMO-LayerPreferenceConfig-r16 ::= SEQUENCE { + maxMIMO-LayerPreferenceProhibitTimer-r16 ENUMERATED { + s0, s0dot5, s1, s2, s3, s4, s5, s6, s7, + s8, s9, s10, s20, s30, spare2, spare1} +} + +MinSchedulingOffsetPreferenceConfig-r16 ::= SEQUENCE { + minSchedulingOffsetPreferenceProhibitTimer-r16 ENUMERATED { + s0, s0dot5, s1, s2, s3, s4, s5, s6, s7, + s8, s9, s10, s20, s30, spare2, spare1} +} + +ReleasePreferenceConfig-r16 ::= SEQUENCE { + releasePreferenceProhibitTimer-r16 ENUMERATED { + s0, s0dot5, s1, s2, s3, s4, s5, s6, s7, + s8, s9, s10, s20, s30, infinity, spare1}, + connectedReporting ENUMERATED {true} OPTIONAL -- Need R +} + +RLM-RelaxationReportingConfig-r17 ::= SEQUENCE { + rlm-RelaxationReportingProhibitTimer ENUMERATED {s0, s0dot5, s1, s2, s5, s10, s20, s30, + s60, s90, s120, s300, s600, infinity, spare2, spare1} +} + +``` + +``` + +BFD-RelaxationReportingConfig-r17 ::= SEQUENCE { + bfd-RelaxtionReportingProhibitTimer ENUMERATED {s0, s0dot5, s1, s2, s5, s10, s20, s30, + s60, s90, s120, s300, s600, infinity, spare2, spare1} +} + +SCG-DeactivationPreferenceConfig-r17 ::= SEQUENCE { + scg-DeactivationPreferenceProhibitTimer-r17 ENUMERATED { + s0, s1, s2, s4, s8, s10, s15, s30, + s60, s120, s180, s240, s300, s600, s900, s1800} +} + +RRM-MeasRelaxationReportingConfig-r17 ::= SEQUENCE { + s-SearchDeltaP-Stationary-r17 ENUMERATED {dB2, dB3, dB6, dB9, dB12, dB15, spare2, spare1}, + t-SearchDeltaP-Stationary-r17 ENUMERATED {s5, s10, s20, s30, s60, s120, s180, s240, s300, spare7, spare6, spare5, + spare4, spare3, spare2, spare1} +} + +PropDelayDiffReportConfig-r17 ::= SEQUENCE { + threshPropDelayDiff-r17 ENUMERATED {ms0dot5, ms1, ms2, ms3, ms4, ms5, ms6 ,ms7, ms8, ms9, ms10, spare5, + spare4, spare3, spare2, spare1} OPTIONAL, -- Need M + neighCellInfoList-r17 SEQUENCE (SIZE (1..maxCellNTN-r17)) OF NeighbourCellInfo-r17 OPTIONAL -- Need M +} + +NeighbourCellInfo-r17 ::= SEQUENCE { + epochTime-r17 EpochTime-r17, + ephemerisInfo-r17 EphemerisInfo-r17 +} + +IDC-FDM-AssistanceConfig-r18 ::= SEQUENCE { + candidateServingFreqRangeListNR-r18 CandidateServingFreqRangeListNR-r18 OPTIONAL, -- Need R + ... +} + +CandidateServingFreqRangeListNR-r18 ::= SEQUENCE (SIZE (1..maxFreqIDC-r16)) OF CandidateServingFreqRangeNR-r18 + +CandidateServingFreqRangeNR-r18 ::= SEQUENCE { + candidateCenterFreq-r18 ARFCN-ValueNR, + candidateBandwidth-r18 ENUMERATED {khz200, khz400, khz600, khz800, mhz1, mhz2, mhz3, mhz4, mhz5, + mhz6, mhz8, mhz10, mhz20, mhz30, mhz40, mhz50, mhz60, mhz80, mhz100, + mhz200, mhz300, mhz400} OPTIONAL -- Need R +} + +UL-TrafficInfoReportingConfig-r18 ::= SEQUENCE { + pdu-SessionsToReportUL-TrafficInfoList-r18 SEQUENCE (SIZE (1.. maxNrofPDU-Sessions-r17)) OF PDU-SessionToReportUL-TrafficInfo-r18, + ul-TrafficInfoProhibitTimer-r18 ENUMERATED {s0, s0dot5, s1, s2, s5, s10, s20, s30, + s60, s90, s120, s300, s600, spare3, spare2, spare1} +} + +PDU-SessionToReportUL-TrafficInfo-r18 ::= SEQUENCE { + pdu-SessionID PDU-SessionID, +} + +``` + +``` + qfi-ToReportUL-TrafficInfoList-r18 SEQUENCE (SIZE (1..maxNrofQFIs)) OF QFI +} + +-- TAG-OTHERCONFIG-STOP +-- ASN1STOP +``` + +| OtherConfig field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| bfd-RelaxationReportingConfig
Configuration for the UE to report the relaxation state of BFD measurements. | +| btNameList
Configuration for the UE to report measurements from specific Bluetooth beacons. NG-RAN configures the field if includeBT-Meas is configured for one or more measurements. | +| candidateBandwidth
Indicates the bandwidth of the candidate frequency range around the center frequency. | +| candidateCenterFreq
Indicates the center frequency of the candidate frequency range. | +| candidateServingFreqListNR
Indicates for each candidate NR serving cells, the center frequency around which UE is requested to report IDC issues. | +| candidateServingFreqRangeListNR
Indicates the candidate frequency range with the combination of the center frequency and the candidate bandwidth, around which the UE is requested to report IDC issues. | +| connectedReporting
Indicates that the UE can report a preference to remain in RRC_CONNECTED state following a report to leave RRC_CONNECTED state. If absent, the UE cannot report a preference to stay in RRC_CONNECTED state. | +| delayBudgetReportingProhibitTimer
Prohibit timer for delay budget reporting. Value in seconds. Value s0 means prohibit timer is set to 0 seconds, value s0dot4 means prohibit timer is set to 0.4 seconds, and so on. | +| drx-PreferenceConfig
Configuration for the UE to report assistance information to inform the gNB about the UE's DRX preferences for power saving. | +| drx-PreferenceProhibitTimer
Prohibit timer for DRX preferences assistance information reporting. Value in seconds. Value s0 means prohibit timer is set to 0 seconds, value s0dot5 means prohibit timer is set to 0.5 seconds, value s1 means prohibit timer is set to 1 second and so on. | +| idc-AssistanceConfig
Configuration for the UE to report assistance information to inform the gNB about UE detected IDC problem. | +| maxBW-PreferenceConfig
Configuration for the UE to report assistance information to inform the gNB about the UE's preferred bandwidth for power saving. | +| maxBW-PreferenceProhibitTimer
Prohibit timer for preferred bandwidth assistance information reporting. Value in seconds. Value s0 means prohibit timer is set to 0 seconds, value s0dot5 means prohibit timer is set to 0.5 seconds, value s1 means prohibit timer is set to 1 second and so on. | +| maxCC-PreferenceConfig
Configuration for the UE to report assistance information to inform the gNB about the UE's preferred number of carriers for power saving. | +| maxBW-PreferenceConfigFR2-2
Configuration for the UE to report assistance information to inform the gNB about the UE's preferred bandwidth for power saving for FR2-2. | +| maxCC-PreferenceProhibitTimer
Prohibit timer for preferred number of carriers assistance information reporting. Value in seconds. Value s0 means prohibit timer is set to 0 seconds, value s0dot5 means prohibit timer is set to 0.5 seconds, value s1 means prohibit timer is set to 1 second and so on. | +| maxMIMO-LayerPreferenceConfig
Configuration for the UE to report assistance information to inform the gNB about the UE's preferred number of MIMO layers for power saving. | +| maxMIMO-LayerPreferenceConfigFR2-2
Configuration for the UE to report assistance information to inform the gNB about the UE's preferred number of MIMO layers for power saving for FR2-2. | + +| | | +|----------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| maxMIMO-LayerPreferenceProhibitTimer | Prohibit timer for preferred number of number of MIMO layers assistance information reporting. Value in seconds. Value s0 means prohibit timer is set to 0 seconds, value s0dot5 means prohibit timer is set to 0.5 seconds, value s1 means prohibit timer is set to 1 second and so on. | +| minSchedulingOffsetPreferenceConfig | Configuration for the UE to report assistance information to inform the gNB about the UE's preferred minimumSchedulingOffset value for cross-slot scheduling for power saving. | +| minSchedulingOffsetPreferenceConfigExt | Configuration for the UE to report assistance information to inform the gNB about the UE's preferred minimumSchedulingOffset value for cross-slot scheduling for power saving for SCS 480 kHz and/or 960 kHz. | +| minSchedulingOffsetPreferenceProhibitTimer | Prohibit timer for preferred minimumSchedulingOffset assistance information reporting. Value in seconds. Value s0 means prohibit timer is set to 0 seconds, value s0dot5 means prohibit timer is set to 0.5 seconds, value s1 means prohibit timer is set to 1 second and so on. | +| multiRx-PreferenceReportingConfigFR2 | Configuration for the UE to report assistant information to inform gNB about the UE's preference on multi-Rx operation for FR2. | +| multiRx-PreferenceReportingConfigFR2ProhibitTimer | Prohibit timer for multi-Rx operation for FR2 reporting. Value in seconds. Value s0 means prohibit timer is set to 0 seconds, value s0dot5 means prohibit timer is set to 0.5 seconds, value s1 means prohibit timer is set to 1 second and so on. | +| musim-CandidateBandList | A list of bands for which the UE is requested to provide information on temporary restricted capabilities for MUSIM operation | +| musim-GapAssistanceConfig | Configuration for the UE to report assistance information for gap preference. | +| musim-GapPriorityAssistanceConfig | Indicates the UE is allowed to provide MUSIM assistance information for gap(s) priority or MUSIM gaps keep preference. | +| musim-GapProhibitTimer | Prohibit timer for MUSIM assistance information reporting for gap preference. | +| musim-LeaveAssistanceConfig | Configuration for the UE to report assistance information for leaving RRC_CONNECTED for MUSIM purpose. | +| musim-LeaveWithoutResponseTimer | Indicates the timer for the UE to enter RRC_IDLE for MUSIM purpose as defined in clause 5.3.8.6. | +| musim-ProhibitTimer | Indicates the prohibit timer for UE temporary restricted capabilities for MUSIM operation. Value in milliseconds. Value ms0 means prohibit timer is set to 0 milliseconds, value ms10 means prohibit timer is set to 10 milliseconds and so on. | +| musim-WaitTimer | Indicates the wait timer for UE temporary restricted capabilities for MUSIM operation. Value in milliseconds. Value ms10 means wait timer is set to 10 milliseconds, value ms20 means wait timer is set to 20 milliseconds and so on. | +| obtainCommonLocation | Requests the UE to attempt to have detailed location information available using GNSS. NR configures the field if includeCommonLocationInfo is configured for one or more measurements. | +| overheatingAssistanceConfig | Configuration for the UE to report assistance information to inform the gNB about UE detected internal overheating. | +| overheatingIndicationProhibitTimer | Prohibit timer for overheating assistance information reporting. Value in seconds. Value s0 means prohibit timer is set to 0 seconds, value s0dot5 means prohibit timer is set to 0.5 seconds, value s1 means prohibit timer is set to 1 second and so on. | +| pdu-SessionsToReportUL-TrafficInfoList | A list of PDU sessions for which the UE shall report UL traffic information. | + +| | | +|------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| propDelayDiffReportConfig | Configuration for the UE to report service link propagation delay difference between serving cell and neighbour cell(s). | +| qfi-ToReportUL-TrafficInfoList | A list of QFIs of a PDU session for which the UE shall report UL traffic information. | +| referenceTimePreferenceReporting | If present, the field indicates the UE is configured to provide reference time assistance information. | +| releasePreferenceConfig | Configuration for the UE to report assistance information to inform the gNB about the UE's preference to leave RRC_CONNECTED state. | +| rlm-RelaxationReportingConfig | Configuration for the UE to report the relaxation state of RLM measurements. | +| releasePreferenceProhibitTimer | Prohibit timer for release preference assistance information reporting. Value in seconds. Value s0 means prohibit timer is set to 0 seconds, value s0dot5 means prohibit timer is set to 0.5 seconds, value s1 means prohibit timer is set to 1 second and so on. Value infinity means that once a UE has reported a release preference, the UE cannot report a release preference again during the RRC connection. | +| s-SearchDeltaP-Stationary | Parameter " S SearchDeltaP-StationaryConnected " in 5.7.4.4. Value dB2 corresponds to 2 dB, dB3 corresponds to 3 dB and so on. | +| scg-DeactivationPreferenceConfig | Configuration of the UE to indicate its preference for SCG deactivation. | +| scg -StatePreferenceProhibitTimer | Prohibit timer for UE indication of its preference for SCG deactivation. Value in seconds. Value s0 means prohibit timer is set to 0 seconds, value s1 means prohibit timer is set to 1 second and so on. | +| sensorNameList | Configuration for the UE to report measurements from specific sensors. NG-RAN configures the field if includeSensor-Meas is configured for one or more measurements. | +| sl-AssistanceConfigNR | Indicate whether UE is configured to provide configured grant assistance information for NR sidelink communication. | +| sn-InitiatedPSCellChange | This field indicates whether the PSCell change procedure included in the RRCReconfiguration message is SN initiated or not. | +| sourceDAPS-FailureReporting | This field indicates whether the UE shall generate the SHR upon successfully completing the DAPS handover to the target cell and if a radio link failure was experienced in the source PCell while executing the DAPS handover. This field is set in the otherConfig configured by the source cell of the DAPS handover. | +| successHO-Config | Configuration for the UE to report the successful handover information to the network. | +| successPSCell-Config | Configuration for the UE to report the successful PSCell change or addition information to the network. | +| t-SearchDeltaP-Stationary | Parameter " T SearchDeltaP-StationaryConnected " in 5.7.4.4. Value in seconds. Value s5 means 5 seconds, value s10 means 10 seconds and so on. | +| thresholdPercentageT304 | This field indicates the threshold for the ratio in percentage between the elapsed T304 timer and the configured value of the T304 timer. Value p40 corresponds to 40%, value p60 corresponds to 60% and so on. This field is set in the otherConfig configured by the target cell of the handover. | +| thresholdPercentageT310 | This field indicates the threshold for the ratio in percentage between the elapsed T310 timer and the configured value of the T310 timer. Value p40 corresponds to 40%, value p60 corresponds to 60% and so on. This field is set in the otherConfig configured by the source cell of the handover. | + +| | | +|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| thresholdPercentageT312 | This field indicates the threshold for the ratio in percentage between the elapsed T312 timer and the configured value(s) of the T312 timer. Value p20 corresponds to 20%, value p40 corresponds to 40% and so on. This field is set in the otherConfig configured by the source cell of the handover. | +| thresholdPercentageT304-SCG | This field indicates the threshold for the ratio in percentage between the elapsed T304 timer associated to the target PSCell and the configured value of the T304 timer. Value p40 corresponds to 40%, value p60 corresponds to 60% and so on. This field is set in the otherConfig configured by the target PSCell of the PSCell change or addition. | +| thresholdPercentageT310-SCG | This field indicates the threshold for the ratio in percentage between the elapsed T310 timer associated to the source PSCell and the configured value of the T310 timer. Value p40 corresponds to 40%, value p60 corresponds to 60% and so on. This field is set in the otherConfig configured by the source PSCell of the PSCell change, or in the otherConfig configured by the PCell for the PSCell change. | +| thresholdPercentageT312-SCG | This field indicates the threshold for the ratio in percentage between the elapsed T312 timer associated to the measurement identity of the target PSCell and the configured value of the T312 timer. Value p20 corresponds to 20%, value p40 corresponds to 40% and so on. This field is set in the otherConfig configured by the source PSCell of the PSCell change, or in the otherConfig configured by the PCell for the PSCell change. | +| threshPropDelayDiff | Threshold for one-way service link propagation delay difference report as specified in 5.7.4.2. | +| uav-FlightPathAvailabilityConfig | Configuration for the UE to indicate the availability of flight path information for Aerial UE operation. | +| ul-GapFR2-PreferenceConfig | Indicates whether UE is configured to request for FR2 UL gap activation/deactivation and preferred FR2 UL gap pattern. | +| wlanNameList | Configuration for the UE to report measurements from specific WLAN APs. NG-RAN configures the field if includeWLAN-Meas is configured for one or more measurements. | +| ul-TrafficInfoProhibitTimer | Prohibit timer for UL traffic information reporting. Value in seconds. Value s0 means prohibit timer is set to 0 seconds, value s0dot5 means prohibit timer is set to 0.5 seconds, value s1 means prohibit timer is set to 1 second and so on. | +| ul-TrafficInfoReportingConfig | Configuration for the UE to report UL traffic information. | + +| NeighbourCellInfo field descriptions | | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| epochTime | Indicates the epoch time used along with the ephemerisInfo to derive the propagation delay difference for the associated neighbour cell. The UE considers epoch time, indicated by the SFN and sub-frame number in this field, to be the frame nearest to the frame in which the message indicating the epoch time is received. This field is used based on the timing of the serving cell, i.e. the SFN and sub-frame number indicated in this field refers to the SFN and sub-frame of the serving cell. | + +| Conditional Presence | Explanation | +|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| FDM | This field is optionally present, need M, if idc-AssistanceConfig-r16 or idc-FDM-AssistanceConfig is setup. Otherwise, it is absent, need R. | +| maxBW | This field is optionally present, need R, if maxBW-PreferenceConfig-r16 is setup; otherwise it is absent, need R. | +| maxMIMO | This field is optionally present, need R, if maxMIMO-LayerPreferenceConfig-r16 is setup; otherwise it is absent, need R. | +| minOffset | This field is optionally present, need R, if minSchedulingOffsetPreferenceConfig-r16 is setup; otherwise it is absent, need R. | +| musimGapConfig | This field is optionally present, need R, if musim-GapAssistanceConfig-r17 is configured; otherwise it is absent, need R. | +| SCG | This field is optionally present, need M, in an RRCReconfiguration message not within mrdc-SecondaryCellGroup and received, either via SRB3 within DLInformationTransferMRDC or via SRB1. Otherwise, it is absent. | + +#### – *PhysCellIdUTRA-FDD* + +The IE *PhysCellIdUTRA-FDD* is used to indicate the physical layer identity of the cell, i.e. the primary scrambling code, as defined in TS 25.331 [45]. + +#### *PhysCellIdUTRA-FDD* information element + +``` +-- ASN1START +-- TAG-PHYCELLIDUTRA-FDD-START + +PhysCellIdUTRA-FDD-r16 ::= INTEGER (0..511) + +-- TAG-PHYCELLIDUTRA-FDD-STOP +-- ASN1STOP +``` + +#### – *RRC-TransactionIdentifier* + +The IE *RRC-TransactionIdentifier* is used, together with the message type, for the identification of an RRC procedure (transaction). + +#### *RRC-TransactionIdentifier* information element + +``` +-- ASN1START +-- TAG-RRC-TRANSACTIONIDENTIFIER-START + +RRC-TransactionIdentifier ::= INTEGER (0..3) + +-- TAG-RRC-TRANSACTIONIDENTIFIER-STOP +-- ASN1STOP +``` + +#### – *Sensor-NameList* + +The IE *Sensor-NameList* is used to indicate the names of the sensors which the UE is configured to measure. + +#### Sensor-NameList information element + +``` +-- ASN1START +-- TAG-SENSORNAMELIST-START + +Sensor-NameList-r16 ::= SEQUENCE { + measUncomBarPre-r16 ENUMERATED {true} OPTIONAL, -- Need R + measUeSpeed ENUMERATED {true} OPTIONAL, -- Need R + measUeOrientation ENUMERATED {true} OPTIONAL, -- Need R +} + +-- TAG-SENSORNAMELIST-STOP +-- ASN1STOP +``` + +#### Sensor-NameList field descriptions + +| | | +|--------------------------|---------------------------------------------------------------------------------------------------------------| +| measUncomBarPre | If configured, the UE reports the uncompensated Barometric pressure measurement as defined in TS 37.355 [49]. | +| measUeSpeed | If configured, the UE reports the UE speed measurement as defined in TS 37.355 [49]. | +| measUeOrientation | If configured, the UE reports the UE orientation information as defined in TS 37.355 [49]. | + +#### — TraceReference + +The *TraceReference* contains parameter Trace Reference as defined in TS 32.422 [52]. + +#### TraceReference information element + +``` +-- ASN1START +-- TAG-TRACEREFERENCE-START + +TraceReference-r16 ::= SEQUENCE { + plmn-Identity-r16 PLMN-Identity, + traceId-r16 OCTET STRING (SIZE (3)) +} + +-- TAG-TRACEREFERENCE-STOP +-- ASN1STOP +``` + +#### — UE-MeasurementsAvailable + +The IE *UE-MeasurementsAvailable* is used to indicate all relevant available indicators for UE measurements. + +#### **UE-MeasurementsAvailable information element** + +``` + +-- ASN1START +-- TAG-UE-MeasurementsAvailable-START + +UE-MeasurementsAvailable-r16 ::= + SEQUENCE { + logMeasAvailable-r16 ENUMERATED {true} OPTIONAL, + logMeasAvailableBT-r16 ENUMERATED {true} OPTIONAL, + logMeasAvailableWLAN-r16 ENUMERATED {true} OPTIONAL, + connEstFailInfoAvailable-r16 ENUMERATED {true} OPTIONAL, + rlf-InfoAvailable-r16 ENUMERATED {true} OPTIONAL, + ... + [[ + successHO-InfoAvailable-r17 ENUMERATED {true} OPTIONAL, + sigLogMeasConfigAvailable-r17 BOOLEAN OPTIONAL + ]], + [[ + successPSCell-InfoAvailable-r18 ENUMERATED {true} OPTIONAL + ]] + } + +-- TAG-UE-MeasurementsAvailable-STOP +-- ASN1STOP + +``` + +#### **UTRA-FDD-Q-OffsetRange** + +The IE *UTRA-FDD-Q-OffsetRange* is used to indicate a frequency specific offset to be applied when evaluating triggering conditions for measurement reporting. The value is in dB. Value *dB-24* corresponds to -24 dB, value *dB-22* corresponds to -22 dB and so on. + +#### **UTRA-FDD-Q-OffsetRange information element** + +``` + +-- ASN1START +-- TAG-UTRA-FDD-Q-OFFSETRANGE-START + +UTRA-FDD-Q-OffsetRange-r16 ::= + ENUMERATED { + dB-24, dB-22, dB-20, dB-18, dB-16, dB-14, + dB-12, dB-10, dB-8, dB-6, dB-5, dB-4, dB-3, + dB-2, dB-1, dB0, dB1, dB2, dB3, dB4, dB5, + dB6, dB8, dB10, dB12, dB14, dB16, dB18, + dB20, dB22, dB24} + +-- TAG-UTRA-FDD-Q-OFFSETRANGE-STOP +-- ASN1STOP + +``` + +#### — VisitedCellInfoList + +The IE *VisitedCellInfoList* includes the mobility history information of maximum of 16 most recently visited primary cells or time spent in any cell selection state and/or camped on any cell state in NR or E-UTRA and, in case of Dual Connectivity, the mobility history information of *maxPSCellHistory* most recently visited primary secondary cell group cells across all the primary cells included in the *VisitedCellInfoList*. The most recently visited cell is stored first in the list. The list includes cells visited in RRC\_IDLE, RRC\_INACTIVE and RRC\_CONNECTED states for NR and RRC\_IDLE and RRC\_CONNECTED for E-UTRA. + +#### VisitedCellInfoList information element + +``` +-- ASN1START +-- TAG-VISITEDCELLINFOLIST-START + +VisitedCellInfoList-r16 ::= SEQUENCE (SIZE (1..maxCellHistory-r16)) OF VisitedCellInfo-r16 + +VisitedCellInfo-r16 ::= SEQUENCE { + visitedCellId-r16 CHOICE { + nr-CellId-r16 CHOICE { + cgi-Info CGI-Info-Logging-r16, + pci-arfcn-r16 PCI-ARFCN-NR-r16 + }, + eutra-CellId-r16 CHOICE { + cellGlobalId-r16 CGI-InfoEUTRA, + pci-arfcn-r16 PCI-ARFCN-EUTRA-r16 + } + } + timeSpent-r16 INTEGER (0..4095), + ... + [[ + visitedPSCellInfoListReport-r17 VisitedPSCellInfoList-r17 + ]] +} + +VisitedPSCellInfoList-r17 ::= SEQUENCE (SIZE (1..maxPSCellHistory-r17)) OF VisitedPSCellInfo-r17 + +VisitedPSCellInfo-r17 ::= SEQUENCE { + visitedCellId-r17 CHOICE { + nr-CellId-r17 CHOICE { + cgi-Info-r17 CGI-Info-Logging-r16, + pci-arfcn-r17 PCI-ARFCN-NR-r16 + }, + eutra-CellId-r17 CHOICE { + cellGlobalId-r17 CGI-InfoEUTRALogging, + pci-arfcn-r17 PCI-ARFCN-EUTRA-r16 + } + } + timeSpent-r17 INTEGER (0..4095), + ... +} +``` + +``` +-- TAG-VISITEDCELLINFOLIST-STOP +-- ASN1STOP +``` + +#### | VisitedCellInfoList field descriptions | |-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| |

timeSpent
This field indicates the duration of stay in the cell or in any cell selection state and/or camped on any cell state in NR or E-UTRA approximated to the closest second. If included in VisitedPSCellInfo, it indicates the duration of stay in the PSCell or without any PSCell. If the duration of stay exceeds 4095s, the UE shall set it to 4095s.

| |

visitedCellId
This field indicates the visited cell id including NR and E-UTRA cells.

| + +#### – *WLAN-NameList* + +The IE *WLAN-NameList* is used to indicate the names of the WLAN AP for which the UE is configured to measure. + +#### ***WLAN-NameList* information element** + +``` +-- ASN1START +-- TAG-WLANNAMELIST-START + +WLAN-NameList-r16 ::= SEQUENCE (SIZE (1..maxWLAN-Name-r16)) OF WLAN-Name-r16 + +WLAN-Name-r16 ::= OCTET STRING (SIZE (1..32)) + +-- ASN1STOP +-- TAG-WLANNAMELIST-STOP +``` + +#### | WLAN-NameList field descriptions | |-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| |

WLAN-Name
If configured, the UE only performs WLAN measurements according to the names identified. For each name, it refers to Service Set Identifier (SSID) defined in IEEE 802.11-2012 [50].

| + +### 6.3.5 Sidelink information elements + +#### – *SL-BWP-Config* + +The IE *SL-BWP-Config* is used to configure the UE specific NR sidelink communication/discovery/positioning on one particular sidelink bandwidth part. + +#### ***SL-BWP-Config* information element** + +``` +-- ASN1START +-- TAG-SL-BWP-CONFIG-START +``` + +``` + +SL-BWP-Config-r16 ::= + sl-BWP-Id BWP-Id, + sl-BWP-Generic-r16 SL-BWP-Generic-r16 OPTIONAL, -- Need M + sl-BWP-PoolConfig-r16 SL-BWP-PoolConfig-r16 OPTIONAL, -- Need M + ... + [[ + sl-BWP-PoolConfigPS-r17 SetupRelease {SL-BWP-PoolConfig-r16} OPTIONAL, -- Need M + sl-BWP-DiscPoolConfig-r17 SetupRelease {SL-BWP-DiscPoolConfig-r17} OPTIONAL -- Need M + ], + [[ + sl-LBT-FailureRecoveryConfig-r18 SetupRelease { SL-LBT-FailureRecoveryConfig-r18 } OPTIONAL, -- Need M + sl-StartingSymbolFirst-r18 ENUMERATED {sym0, sym1, sym2, sym3, sym4, sym5, sym6} OPTIONAL, -- Need M + sl-StartingSymbolSecond-r18 ENUMERATED {sym3, sym4, sym5, sym6, sym7} OPTIONAL, -- Need M + sl-TransmissionStructureForPSCCHandPSSCH-r18 ENUMERATED {contiguousRB, interlaceRB} OPTIONAL, -- Need M + sl-GapOfAdditionalSSSB-Occasion-r18 INTEGER (0..639) OPTIONAL, -- Need M + sl-AbsoluteFrequencySSB-NonAnchorList-r18 SEQUENCE (SIZE (1.. maxSL-NonAnchorRBsets)) OF ARFCN-ValueNR OPTIONAL, -- Need M + sl-NumOfSSS-Brepetition-r18 SEQUENCE (SIZE (1..5)) OF INTEGER (2..9) OPTIONAL, -- Need M + sl-CPE-StartingPositionS-SSB-r18 INTEGER (1..9) OPTIONAL, -- Need M + sl-CWS-ForPsschWithoutHarqAck-r18 ENUMERATED {t1, t8, t16, t32, infinity} OPTIONAL, -- Need M + sl-NumOfAdditionalSSBOccasion-r18 INTEGER (0..4) OPTIONAL, -- Need M + sl-SSSBPowerOffsetOfAnchorRBSet-r18 ENUMERATED {value1, value2} OPTIONAL, -- Need M + sl-RBSetConfigList-r18 SEQUENCE (SIZE (1..5)) OF SL-RBSetConfig-r18 OPTIONAL, -- Need M + sl-BWP-PoolConfigA2X-r18 SetupRelease {SL-BWP-PoolConfig-r16} OPTIONAL, -- Need M + sl-BWP-PRS-PoolConfig-r18 SetupRelease {SL-BWP-PRS-PoolConfig-r18} OPTIONAL -- Need M + ]] +} + +SL-BWP-Generic-r16 ::= + sl-BWP-r16 BWP OPTIONAL, -- Need M + sl-LengthSymbols-r16 ENUMERATED {sym7, sym8, sym9, sym10, sym11, sym12, sym13, sym14} OPTIONAL, -- Need M + sl-StartSymbol-r16 ENUMERATED {sym0, sym1, sym2, sym3, sym4, sym5, sym6, sym7} OPTIONAL, -- Need M + sl-PSBCH-Config-r16 SetupRelease {SL-PSBCH-Config-r16} OPTIONAL, -- Need M + sl-TxDirectCurrentLocation-r16 INTEGER (0..3301) OPTIONAL, -- Need M + ... +} + +-- TAG-SL-BWP-CONFIG-STOP +-- ASN1STOP + +``` + +| SL-BWP-Config field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-AbsoluteFrequencySSB-NonAnchorList
Indicates the lowest S-SSB in a non-anchor RB set via each parameter in this list. Anchor RB set refers to the RB set where S-SSB indicated by sl-AbsoluteFrequencySSB-r16 locates. | +| sl-BWP-DiscPoolConfig
This field indicates the NR sidelink discovery dedicated resource pool configurations on the configured sidelink BWP. The total number of Rx/Tx resource pools configured for communication and discovery does not exceed the maximum number of Rx/Tx resource pool for NR sidelink communication (i.e. maxNrofRXPool-r16/maxNrofTXPool-r16 ). | +| sl-BWP-Generic
This field indicates the generic parameters on the configured sidelink BWP. | +| sl-BWP-Id
An identifier for this sidelink bandwidth part. | +| sl-BWP-PoolConfig
This field indicates the resource pool configurations on the configured sidelink BWP. | +| sl-BWP-PoolConfigA2X
This field indicates the resource pool configurations for A2X services on the configured sidelink BWP. This field does not include sl-TxPoolScheduling . | +| sl-BWP-PoolConfigPS
This field indicates the resource pool configurations for power saving on the configured sidelink BWP. This field does not include sl-TxPoolExceptional . | +| sl-BWP-PRS-PoolConfig
This field indicates the sidelink PRS dedicated resource pool configurations for SL-PRS on the configured sidelink BWP. This field does not include sl-PRS-TxPoolExceptional . | +| sl-CPE-StartingPositionS-SSB
Indicates the CPE starting position within the GP symbol before S-SSB transmission. The value is an index of the set of all candidate CPE starting positions specified in Table 5.3.1-3 of [16, TS 38.211] for Ci=1 and the corresponding SCS of the SL BWP. | +| sl-CWS-ForPsschWithoutHarqAck
The latest CW_p is autonomously increased to the next higher allowed value for every priority class p of {1,2,3,4} if the same CW_p which is different from CW_(max,p) is consecutively used for general of N_init in SL Type 1 LBT for a number of times indicated by this parameter. This operation is restricted only to PSCCH/PSSCH transmission(s) with "HARQ feedback enabled/disabled indicator" in the 2nd stage SCI set to disabled, regardless of whether PSFCH resources being configured in a resource pool. | +| sl-GapOfAdditionalSSSB-Occasion
Indicate the gap between each R16/R17 NR SL S-SSB slot and its first corresponding additional candidate S-SSB occasion, and the gap between adjacent two additional candidate S-SSB occasions corresponding to a R16/R17 NR SL S-SSB slot. | +| sl-LBT-FailureRecoveryConfig
Configures parameters used for detection and cancellation of sidelink consistent LBT failures for operation with shared spectrum channel access, as specified in TS 38.321 [3]. | +| sl-NumOfAdditionalSSSBOccasion
Indicate the number of additional candidate S-SSB occasion(s) for each R16/R17 NR SL S-SSB slot. | +| sl-NumOfSSS-Brepetition
Indicate the number of S-SSB repetitions in frequency domain in one RB set, where first value corresponds to first RB set, second value corresponds to second RB set and so on. Legacy S-SSB are applicable in region with no OCB requirement, or with OCB exemption. | +| sl-SSSBPowerOffsetOfAnchorRBSet
Indicate the power offset for one S-SSB transmission on anchor RB set, where anchor RB set refers to the RB set where S-SSB indicated by sl-AbsoluteFrequencySSB-r16 locates. Value value1 corresponds to the power offset of 10lg(N) , where N is the number of S-SSB repetitions within the anchor RB set, and value2 corresponds to the power offset of 10log(W) , where W is the maximum total number of S-SSB repetitions on RB sets within the SL-BWP. | +| sl-StartingSymbolFirst
Indicates the location of first starting symbol within a slot. Value sym0 corresponds to first symbol, value sym1 corresponds to the second symbol and so on. If the field is not configured, the UE shall use value sym0 . | +| sl-StartingSymbolSecond | + +Indicates the location of second starting symbol within a slot. Value *sym3* corresponds to fourth symbol, value *sym4* corresponds to the fifth symbol and so on. The number of symbols used for PSCCH/PSSCH transmission from second starting symbol is not smaller than 6. Within a slot, the second starting symbol is later than the first starting symbol. PSCCH/PSSCH transmission starting from first or second starting symbol shall have the same ending symbol within a slot. + +##### ***sl-TransmissionStructureForPSCCHandPSSCH*** + +Indicate a SL-BWP is (pre-)configured with contiguous RB-based or interlace RB-based PSCCH/PSSCH transmission. Legacy PSCCH/PSSCH are applicable in region with no OCB requirement, or with OCB exemption. + +#### ***SL-BWP-Generic* field descriptions** + +##### ***sl-LengthSymbols*** + +This field indicates the number of symbols used for sidelink in a slot without S-SSB. A single value can be (pre)configured per sidelink bandwidth part. + +##### ***sl-StartSymbol*** + +This field indicates the starting symbol used for sidelink in a slot without S-SSB. A single value can be (pre)configured per sidelink bandwidth part. + +##### ***sl-TxDirectCurrentLocation*** + +The sidelink Tx/Rx Direct Current location for the carrier. Only values in the value range of this field between 0 and 3299, which indicate the subcarrier index within the carrier corresponding to the numerology of the corresponding sidelink BWP and value 3300, which indicates "Outside the carrier" and value 3301, which indicates "Undetermined position within the carrier" are used in this version of the specification. + +#### — ***SL-BWP-ConfigCommon*** + +The IE *SL-BWP-ConfigCommon* is used to configure the cell-specific configuration information on one particular sidelink bandwidth part. + +#### ***SL-BWP-ConfigCommon* information element** + +``` +-- ASN1START +-- TAG-SL-BWP-CONFIGCOMMON-START + +SL-BWP-ConfigCommon-r16 ::= + SEQUENCE { + sl-BWP-Generic-r16 SL-BWP-Generic-r16 OPTIONAL, -- Need R + sl-BWP-PoolConfigCommon-r16 SL-BWP-PoolConfigCommon-r16 OPTIONAL, -- Need R + ... + [[ + sl-BWP-PoolConfigCommonPS-r17 SL-BWP-PoolConfigCommon-r16 OPTIONAL, -- Need R + sl-BWP-DiscPoolConfigCommon-r17 SL-BWP-DiscPoolConfigCommon-r17 OPTIONAL -- Need R + ]], + [[ + sl-LBT-FailureRecoveryConfig-r18 SetupRelease { SL-LBT-FailureRecoveryConfig-r18 } OPTIONAL, -- Need R + sl-StartingSymbolFirst-r18 ENUMERATED {sym0, sym1, sym2, sym3, sym4, sym5, sym6} OPTIONAL, -- Need R + sl-StartingSymbolSecond-r18 ENUMERATED {sym3, sym4, sym5, sym6, sym7} OPTIONAL, -- Need R + sl-TransmissionStructureForPSCCHandPSSCH-r18 ENUMERATED {contiguousRB, interlaceRB} OPTIONAL, -- Need R + sl-GapOfAdditionalSSB-Occasion-r18 INTEGER (0..639) OPTIONAL, -- Need R + sl-AbsoluteFrequencySSB-NonAnchorList-r18 SEQUENCE (SIZE (1.. maxSL-NonAnchorRBsets)) OF ARFCN-ValueNR OPTIONAL, -- Need R + sl-NumOfSSS-Brepetition-r18 SEQUENCE (SIZE (1..5)) OF INTEGER (2..9) OPTIONAL, -- Need R + sl-CPE-StartingPositionS-SSB-r18 INTEGER (1..9) OPTIONAL, -- Need R + sl-CWS-ForPsschWithoutHargAck-r18 ENUMERATED {t1, t8, t16, t32, infinity} OPTIONAL, -- Need R + sl-NumOfAdditionalSSBOccasion-r18 INTEGER (0..4) OPTIONAL, -- Need R + ]] +``` + +``` +sl-SSSBPowerOffsetOfAnchorRBSet-r18 ENUMERATED {value1, value2} OPTIONAL, -- Need R +sl-PSFCHPowerOffset-r18 INTEGER (0..10) OPTIONAL, -- Need R +sl-RBSetConfigList-r18 SEQUENCE (SIZE (1..5)) OF SL-RBSetConfig-r18 OPTIONAL, -- Need R +sl-BWP-PoolConfigCommonA2X-r18 SL-BWP-PoolConfigCommon-r16 OPTIONAL, -- Need R +sl-BWP-PRS-PoolConfigCommon-r18 SL-BWP-PRS-PoolConfigCommon-r18 OPTIONAL -- Need R +]] +} + +-- TAG-SL-BWP-CONFIGCOMMON-STOP +-- ASN1STOP +``` + +| SL-BWP-ConfigCommon field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-AbsoluteFrequencySSB-NonAnchorList
Indicates the lowest S-SSB in a non-anchor RB set via each parameter in this list. Anchor RB set refers to the RB set where S-SSB indicated by sl-AbsoluteFrequencySSB-r16 locates. | +| sl-BWP-DiscPoolConfigCommon
This field indicates the NR sidelink discovery dedicated resource pool configurations on the configured sidelink BWP. The total number of Rx/Tx resource pools configured for communication and discovery does not exceed the maximum number of Rx/Tx resource pool for NR sidelink communication (i.e. maxNrofRXPool-r16/maxNrofTXPool-r16 ). | +| sl-BWP-Generic
This field indicates the generic parameters on the configured sidelink BWP. | +| sl-BWP-PoolConfigCommon
This field indicates the resource pool configurations on the configured sidelink BWP. | +| sl-BWP-PoolConfigCommonA2X
This field indicates the resource pool configurations for A2X services on the configured sidelink BWP. | +| sl-BWP-PoolConfigCommonPS
This field indicates the resource pool configurations for power saving on the configured sidelink BWP. This field does not include sl-TxPoolExceptional . | +| sl-BWP-PRS-PoolConfigCommon
This field indicates the resource pool configurations for SL-PRS on the configured sidelink BWP. This field does not include sl-PRS-TxPoolExceptional . | +| sl-CPE-StartingPositionS-SSB
Indicates the CPE starting position within the GP symbol before S-SSB transmission. The value is an index of the set of all candidate CPE starting positions specified in Table 5.3.1-3 of [16, TS 38.211] for Ci=1 and the corresponding SCS of the SL BWP. | +| sl-CWS-ForPsschWithoutHarqAck
The latest CW_p is autonomously increased to the next higher allowed value for every priority class p of {1,2,3,4} if the same CW_p which is different from CW_(max,p) is consecutively used for general of N_init in SL Type 1 LBT for a number of times indicated by this parameter. This operation is restricted only to PSCCH/PSSCH transmission(s) with "HARQ feedback enabled/disabled indicator" in the 2nd stage SCI set to disabled, regardless of whether PSFCH resources being configured in a resource pool. | +| sl-GapOfAdditionalSSB-Occasion
Indicate the gap between each R16/R17 NR SL S-SSB slot and its first corresponding additional candidate S-SSB occasion, and the gap between adjacent two additional candidate S-SSB occasions corresponding to a R16/R17 NR SL S-SSB slot. | +| sl-LBT-FailureRecoveryConfig
Configures parameters used for detection and cancellation of sidelink consistent LBT failures for operation with shared spectrum channel access, as specified in TS 38.321 [3]. | +| sl-NumOfAdditionalSSBOccasion
Indicate the number of additional candidate S-SSB occasion(s) for each R16/R17 NR SL S-SSB slot. | +| sl-NumOfSSS-Brepetition
Indicate the number of S-SSB repetitions in frequency domain in one RB set, where first value corresponds to first RB set, second value corresponds to second RB set and so on. Legacy S-SSB are applicable in region with no OCB requirement, or with OCB exemption. | +| sl-PSFCHPowerOffset
Indicates the power offset between Tx power on one common PRB ( P_common ) and Tx power on one dedicated PRB ( P_dedicated ) when transmissionStructureForPSFCH is (pre-)configured as common interlace, i.e., P_common = P_dedicated - offset . UE expects the same (pre-)configured value of PSFCHPowerOffset across all resource pools. The unit is dB. | +| sl-SSBPPowerOffsetOfAnchorRBSet
Indicate the power offset for one S-SSB transmission on anchor RB set, where anchor RB set refers to the RB set where S-SSB indicated by sl-AbsoluteFrequencySSB-r16 locates. Value value1 corresponds to the power offset based on the number of S-SSB repetitions within the anchor RB set, and value2 corresponds to the power offset based on the maximum total number of S-SSB repetitions on RB sets within the SL-BWP. | +| sl-StartingSymbolFirst
Indicates the location of first starting symbol within a slot. Value sym0 corresponds to first symbol, value sym1 corresponds to the second symbol and so on. If the field is not | + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| configured, the UE shall use value sym0 . | +| sl-StartingSymbolSecond
Indicates the location of second starting symbol within a slot. Value sym3 corresponds to fourth symbol, value sym4 corresponds to the fifth symbol and so on. The number of symbols used for PSCCH/PSSCH transmission from second starting symbol is not smaller than 6. Within a slot, the second starting symbol is later than the first starting symbol. PSCCH/PSSCH transmission starting from first or second starting symbol shall have the same ending symbol within a slot. | +| sl-TransmissionStructureForPSCCHandPSSCH
Indicate a SL-BWP is (pre-)configured with contiguous RB-based or interlace RB-based PSCCH/PSSCH transmission. Legacy PSCCH/PSSCH are applicable in region with no OCB requirement, or with OCB exemption. | + +#### SL-BWP-DiscPoolConfig + +The IE *SL-BWP-DiscPoolConfig* is used to configure UE specific NR sidelink discovery dedicated resource pool. + +#### SL-BWP-DiscPoolConfig information element + +``` +-- ASN1START +-- TAG-SL-BWP-DISCPoolCONFIG-START + +SL-BWP-DiscPoolConfig-r17 ::= SEQUENCE { + sl-DiscRxPool-r17 SEQUENCE (SIZE (1..maxNrofRXPool-r16)) OF SL-ResourcePool-r16 OPTIONAL, -- Cond HO + sl-DiscTxPoolSelected-r17 SL-TxPoolDedicated-r16 OPTIONAL, -- Need M + sl-DiscTxPoolScheduling-r17 SL-TxPoolDedicated-r16 OPTIONAL -- Need N +} + +-- TAG-SL-BWP-DISCPoolCONFIG-STOP +-- ASN1STOP +``` + +#### SL-BWP-DiscPoolConfig field descriptions + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-DiscTxPoolScheduling
Indicates the resources by which the UE is allowed to transmit NR sidelink discover based on network scheduling on the configured BWP. For the PSFCH related configuration, if configured, will be used for PSFCH transmission/reception.
When this field is configured together with sl-TxPoolScheduling , the resource pool index (which is used in DCI Format 3_0 in TS 38.212 [17], clause 7.3.1.4.1) is defined as 0, 1, ..., x -1 for the resource pools included in the sl-TxPoolScheduling , and x , x +1, ..., x + y -1 for the resource pools included in sl-DiscTxPoolScheduling , where x is the number of the resource pools in sl-TxPoolScheduling , and y is the number of resource pools in sl-DiscTxPoolScheduling . | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| Conditional Presence | Explanation | +|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| HO | This field is optionally present, need M, in an RRCReconfiguration message including reconfigurationWithSync ; otherwise it is absent, need M. | + +#### — *SL-BWP-DiscPoolConfigCommon* + +The IE *SL-BWP-DiscPoolConfigCommon* is used to configure the cell-specific NR sidelink discovery dedicated resource pool. + +#### *SL-BWP-DiscPoolConfigCommon* information element + +``` +-- ASN1START +-- TAG-SL-BWP-DISCPoolConfigCommon-START + +SL-BWP-DiscPoolConfigCommon-r17 ::= SEQUENCE { + sl-DiscRxPool-r17 SEQUENCE (SIZE (1..maxNrofRXPool-r16)) OF SL-ResourcePool-r16 OPTIONAL, -- Need R + sl-DiscTxPoolSelected-r17 SEQUENCE (SIZE (1..maxNrofTXPool-r16)) OF SL-ResourcePoolConfig-r16 OPTIONAL, -- Need R + ... +} + +-- TAG-SL-BWP-DISCPoolConfigCommon-STOP +-- ASN1STOP +``` + +#### — *SL-BWP-PoolConfig* + +The IE *SL-BWP-PoolConfig* is used to configure NR sidelink communication resource pool. + +#### *SL-BWP-PoolConfig* information element + +``` +-- ASN1START +-- TAG-SL-BWP-POOLCONFIG-START + +SL-BWP-PoolConfig-r16 ::= SEQUENCE { + sl-RxPool-r16 SEQUENCE (SIZE (1..maxNrofRXPool-r16)) OF SL-ResourcePool-r16 OPTIONAL, -- Cond HO + sl-TxPoolSelectedNormal-r16 SL-TxPoolDedicated-r16 OPTIONAL, -- Need M + sl-TxPoolScheduling-r16 SL-TxPoolDedicated-r16 OPTIONAL, -- Need N + sl-TxPoolExceptional-r16 SL-ResourcePoolConfig-r16 OPTIONAL, -- Need M +} + +SL-TxPoolDedicated-r16 ::= SEQUENCE { + sl-PoolToReleaseList-r16 SEQUENCE (SIZE (1..maxNrofTXPool-r16)) OF SL-ResourcePoolID-r16 OPTIONAL, -- Need N + sl-PoolToAddModList-r16 SEQUENCE (SIZE (1..maxNrofTXPool-r16)) OF SL-ResourcePoolConfig-r16 OPTIONAL, -- Need N +} + +SL-ResourcePoolConfig-r16 ::= SEQUENCE { + sl-ResourcePoolID-r16 SL-ResourcePoolID-r16, + sl-ResourcePool-r16 SL-ResourcePool-r16 +} + +SL-ResourcePoolID-r16 ::= INTEGER (1..maxNrofPoolID-r16) + +-- TAG-SL-BWP-POOLCONFIG-STOP +-- ASN1STOP +``` + +| SL-BWP-PoolConfig field descriptions | | +|---------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-RxPool | Indicates the receiving resource pool on the configured BWP. For the PSFCH related configuration, if configured, will be used for PSFCH transmission/reception. If the field is included, it replaces any previous list, i.e. all the entries of the list are replaced and each of the SL-ResourcePool entries is considered to be newly created. | +| sl-TxPoolExceptional | Indicates the resources by which the UE is allowed to perform NR sidelink transmission in exceptional conditions on the configured BWP. For the PSFCH related configuration, if configured, will be used for PSFCH transmission/reception. | +| sl-TxPoolScheduling | Indicates the resources by which the UE is allowed to perform NR sidelink transmission based on network scheduling on the configured BWP. For the PSFCH related configuration, if configured, will be used for PSFCH transmission/reception. | +| sl-TxPoolSelectedNormal | Indicates the resources by which the UE is allowed to perform NR sidelink transmission by UE autonomous resource selection on the configured BWP. For the PSFCH related configuration, if configured, will be used for PSFCH transmission/reception. | + +| Conditional Presence | Explanation | +|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| HO | This field is optionally present, need M, in an RRCREconfiguration message including reconfigurationWithSync ; otherwise it is absent, Need M. | + +#### — SL-BWP-PoolConfigCommon + +The IE *SL-BWP-PoolConfigCommon* is used to configure the cell-specific NR sidelink communication resource pool. + +#### SL-BWP-PoolConfigCommon information element + +``` +-- ASN1START +-- TAG-SL-BWP-POOLCONFIGCOMMON-START + +SL-BWP-PoolConfigCommon-r16 ::= SEQUENCE { + sl-RxPool-r16 SEQUENCE (SIZE (1..maxNrofRXPool-r16)) OF SL-ResourcePool-r16 OPTIONAL, -- Need R + sl-TxPoolSelectedNormal-r16 SEQUENCE (SIZE (1..maxNrofTXPool-r16)) OF SL-ResourcePoolConfig-r16 OPTIONAL, -- Need R + sl-TxPoolExceptional-r16 SL-ResourcePoolConfig-r16 OPTIONAL -- Need R +} + +-- TAG-SL-BWP-POOLCONFIGCOMMON-STOP +-- ASN1STOP +``` + +#### | | |---------------------------------------------------| | SL-BWP-PoolConfigCommon field descriptions | |---------------------------------------------------| + +##### | | |------------------------------------| | sl-TxPoolExceptional | |------------------------------------| + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Indicates the resources by which the UE is allowed to perform NR sidelink transmission in exceptional conditions on the configured BWP. For the PSFCH related configuration, if configured, will be used for PSFCH transmission/reception. This field is not present when SL-BWP-PoolConfigCommon is included in SidelinkPreconfigNR . | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +#### SL-BWP-PRS-PoolConfig + +The IE *SL-BWP-PRS-PoolConfig* is used to configure UE specific NR sidelink PRS dedicated resource pool. + +#### SL-BWP-PRSPoolConfig information element + +``` +-- ASN1START +-- TAG-SL-BWP-PRS-POOLCONFIG-START + +SL-BWP-PRS-PoolConfig-r18 ::= SEQUENCE { + sl-PRS-RxPool-r18 SEQUENCE (SIZE (1..maxNrofRXPool-r16)) OF SL-PRS-ResourcePool-r18 OPTIONAL, -- Cond HO + sl-PRS-TxPoolSelectedNormal-r18 SL-PRS-TxPoolDedicated-r18 OPTIONAL, -- Need M + sl-PRS-TxPoolScheduling-r18 SL-PRS-TxPoolDedicated-r18 OPTIONAL, -- Need N + sl-PRS-TxPoolExceptional-r18 SL-PRS-ResourcePoolConfig-r18 OPTIONAL -- Need R +} + +SL-PRS-TxPoolDedicated-r18 ::= SEQUENCE { + sl-PRS-PoolToReleaseList-r1 SEQUENCE (SIZE (1..maxNrofSL-PRS-TxPool-r18)) OF SL-PRS-ResourcePoolID-r18 OPTIONAL, -- Need N + sl-PRS-PoolToAddModList-r18 SEQUENCE (SIZE (1..maxNrofSL-PRS-TxPool-r18)) OF SL-PRS-ResourcePoolConfig-r18 OPTIONAL -- Need N +} + +SL-PRS-ResourcePoolConfig-r18 ::= SEQUENCE { + sl-PRS-ResourcePoolID-r18 SL-PRS-ResourcePoolID-r18, + sl-PRS-ResourcePool-r18 SL-PRS-ResourcePool-r18 +} OPTIONAL -- Need M + +SL-PRS-ResourcePoolID-r18 ::= INTEGER (1.. maxNrofSL-PRS-TxPool-r18) + +-- TAG-SL-BWP-PRS-POOLCONFIG-STOP +-- ASN1STOP +``` + +Editor's Note: FFS If *sl-PRS-TxPoolExceptional* is used for SL positioning. + +| SL-BWP-PRSPoolConfig field descriptions | | +|------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------| +| sl-PRS-TxPoolSelectedNormal | Indicates the resources by which the UE is allowed to perform SL-PRS transmission by UE autonomous resource selection on the configured BWP. | +| sl-PRS-TxPoolScheduling | Indicates the resources by which the UE is allowed to perform SL-PRS transmission based on network selection on the configured BWP. | +| sl-PRS-TxPoolExceptional | Indicates the resources by which the UE is allowed to perform SL-PRS transmission in exceptional conditions on the configured BWP. | + +| Conditional Presence | Explanation | +|-----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| HO | This field is optionally present, need M, in an RRCREconfiguration message including reconfigurationWithSync ; otherwise it is absent, Need M. | + +#### — ***SL-BWP-PRS-PoolConfigCommon*** + +The IE *SL-BWP-PRSPoolConfigCommon* is used to configure the cell-specific NR sidelink PRS dedicated resource pool. + +#### ***SL-BWP-PRS-PoolConfigCommon* information element** + +``` +-- ASN1START +-- TAG-SL-BWP-PRS-POOLCONFIGCOMMON-START + +SL-BWP-PRS-PoolConfigCommon-r18 ::= SEQUENCE { + sl-PRS-RxPool-r18 SEQUENCE (SIZE (1..maxNrofRXPool-r16)) OF SL-PRS-ResourcePool-r18 OPTIONAL, -- Need R + sl-PRS-TxPoolSelectedNormal-r18 SEQUENCE (SIZE (1..maxNrofSL-PRS-TxPool-r18)) OF SL-PRS-ResourcePoolConfig-r18 OPTIONAL, -- Need R + sl-PRS-TxPoolExceptional-r18 SL-PRS-ResourcePoolConfig-r18 OPTIONAL, -- Need R + ... +} + +-- TAG-SL-BWP-PRSPoolConfigCommon-STOP +-- ASN1STOP +``` + +Editor's Note: FFS If *sl-PRS-TxPoolExceptional* is used for SL positioning. + +| SL-BWP-PRS-PoolConfigCommon field descriptions | | +|-------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-PRS-TxPoolExceptional | Indicates the resources by which the UE is allowed to perform NR sidelink transmission in exceptional conditions on the configured BWP. For the PSFCH related configuration, if configured, will be used for PSFCH transmission/reception. This field is not present when SL-BWP-PRS-PoolConfigCommon is included in SL-PosPreconfigurationNR | + +#### SL-CBR-PriorityTxConfigList + +The IE *SL-CBR-PriorityTxConfigList* indicates the mapping between PSSCH transmission parameter (such as MCS, PRB number, retransmission number, CR limit) sets by using the indexes of the configurations provided in *sl-CBR-PSSCH-TxConfigList*, CBR ranges by an index to the entry of the CBR range configuration in *sl-CBR-RangeConfigList*, and priority ranges. It also indicates the default PSSCH transmission parameters to be used when CBR measurement results are not available, and MCS range for the MCS tables used in the resource pool. + +#### SL-CBR-PriorityTxConfigList information element + +``` +-- ASN1START +-- TAG-SL-CBR-PRIORITYTXCONFIGLIST-START + +SL-CBR-PriorityTxConfigList-r16 ::= SEQUENCE (SIZE (1..8)) OF SL-PriorityTxConfigIndex-r16 +SL-CBR-PriorityTxConfigList-v1650 ::= SEQUENCE (SIZE (1..8)) OF SL-PriorityTxConfigIndex-v1650 + +SL-PriorityTxConfigIndex-r16 ::= SEQUENCE { + sl-PriorityThreshold-r16 INTEGER (1..8) OPTIONAL, -- Need M + sl-DefaultTxConfigIndex-r16 INTEGER (0..maxCBR-Level-1-r16) OPTIONAL, -- Need M + sl-CBR-ConfigIndex-r16 INTEGER (0..maxCBR-Config-1-r16) OPTIONAL, -- Need M + sl-Tx-ConfigIndexList-r16 SEQUENCE (SIZE (1.. maxCBR-Level-r16)) OF SL-TxConfigIndex-r16 OPTIONAL -- Need M +} + +SL-PriorityTxConfigIndex-v1650 ::= SEQUENCE { + sl-MCS-RangeList-r16 SEQUENCE (SIZE (1..maxCBR-Level-r16)) OF SL-MinMaxMCS-List-r16 OPTIONAL -- Need M +} + +SL-TxConfigIndex-r16 ::= INTEGER (0..maxTxConfig-1-r16) + +-- TAG-SL-CBR-PRIORITYTXCONFIGLIST-STOP +-- ASN1STOP +``` + +| SL-CBR-PriorityTxConfigList field descriptions | | +|-------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-CBR-ConfigIndex | Indicates the CBR ranges to be used by an index to the entry of the CBR range configuration in sl-CBR-RangeConfigList . | +| sl-DefaultTxConfigIndex | Indicates the PSSCH transmission parameters to be used by the UEs which do not have available CBR measurement results, by means of an index to the corresponding entry in sl-Tx-ConfigIndexList . Value 0 indicates the first entry in sl-Tx-ConfigIndexList . The field is ignored if the UE has available CBR measurement results. | +| sl-MCS-RangeList | Indicates the minimum MCS value and maximum MCS value for the associated MCS table(s). UE shall ignore the minimum MCS value and maximum MCS value used for table of 64QAM indicated in SL-CBR-PriorityTxConfigList-r16 if SL-CBR-PriorityTxConfigList-v1650 is present. | +| sl-PriorityThreshold | Indicates the upper bound of priority range which is associated with the configurations in sl-CBR-ConfigIndex and in sl-Tx-ConfigIndexList . The upper bounds of the priority ranges are configured in ascending order for consecutive entries of SL-PriorityTxConfigIndex in SL-CBR-PriorityTxConfigList . For the first entry of SL-PriorityTxConfigIndex , the lower bound of the priority range is 1. | +| SL-CBR-PriorityTxConfigList-v1650 | If included, it includes the same number of entries, and listed in the same order, as in SL-CBR-PriorityTxConfigList-r16 . | + +#### SL-CBR-CommonTxConfigList + +The IE *SL-CBR-CommonTxConfigList* indicates the list of PSSCH transmission parameters (such as MCS, sub-channel number, retransmission number, CR limit) in *sl-CBR-PSSCH-TxConfigList*, and the list of CBR ranges in *sl-CBR-RangeConfigList*, to configure congestion control to the UE for sidelink communication. + +#### SL-CBR-CommonTxConfigList information element + +``` +-- ASN1START +-- TAG-SL-CBR-COMMONTXCONFIGLIST-START + +SL-CBR-CommonTxConfigList-r16 ::= SEQUENCE { + sl-CBR-RangeConfigList-r16 SEQUENCE (SIZE (1..maxCBR-Config-r16)) OF SL-CBR-LevelsConfig-r16 OPTIONAL, -- Need M + sl-CBR-PSSCH-TxConfigList-r16 SEQUENCE (SIZE (1..maxTxConfig-r16)) OF SL-CBR-PSSCH-TxConfig-r16 OPTIONAL, -- Need M +} + +SL-CBR-LevelsConfig-r16 ::= SEQUENCE (SIZE (1..maxCBR-Level-r16)) OF SL-CBR-r16 + +SL-CBR-PSSCH-TxConfig-r16 ::= SEQUENCE { + sl-CR-Limit-r16 INTEGER (0..10000) OPTIONAL, -- Need M + sl-TxParameters-r16 SL-PSSCH-TxParameters-r16 OPTIONAL, -- Need M +} + +SL-CBR-r16 ::= INTEGER (0..100) + +-- TAG-SL-CBR-COMMONTXCONFIGLIST-STOP +-- ASN1STOP +``` + +| SL-CBR-CommonTxConfigList field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-CBR-RangeConfigList
Each entry in sl-CBR-RangeConfigList is SL-CBR-LevelsConfig containing the list of CBR ranges. The values within each SL-CBR-LevelsConfig indicate the upper bound of the each CBR range (and implicitly indicate the lower bound of next CBR range) and are configured in ascending order. For the first CBR range of each SL-CBR-LevelsConfig , the lower bound of the CBR range is 0. Value 0 corresponds to 0, value 1 to 0.01, value 2 to 0.02, and so on. | +| sl-CR-Limit
Indicates the maximum limit on the occupancy ratio. Value 0 corresponds to 0, value 1 to 0.0001, value 2 to 0.0002, and so on (i.e. in steps of 0.0001) until value 10000, which corresponds to 1. | +| sl-CBR-PSSCH-TxConfigList
Indicates the list of available PSSCH transmission parameters (such as MCS, sub-channel number, retransmission number and CR limit) configurations. | +| sl-TxParameters
Indicates PSSCH transmission parameters. | + +#### SL-CBR-CommonTxDedicated-SL-PRS-RP-List + +The IE *SL-CBR-CommonTxConfigListDedicated-SL-PRS-RP* indicates the list of SL PRS transmission parameters (such as Maximum SL PRS transmission power, Maximum Number of SL PRS (re-)transmissions, and CR limit) in *sl-CBR-SL-PRS-TxConfigList*, and the list of CBR ranges in *sl-CBR-RangeConfigList-Dedicated-SL-PRS-RP*, to configure congestion control to the UE for sidelink positioning. + +#### SL-CBR-CommonTxDedicatedSL-PRS-RP-List information element + +``` +-- ASN1START +-- TAG- SL-CBR-COMMONTXDEDICATEDSL-PRS-RP-LIST-START + +SL-CBR-CommonTxDedicatedSL-PRS-RP-List-r18 ::= SEQUENCE { + sl-CBR-RangeDedicatedSL-PRS-RP-List-r18 SEQUENCE (SIZE (1..maxCBR-ConfigDedSL-PRS-1-r18)) OF SL-CBR-LevelsDedicatedSL-PRS-RP-r18 + OPTIONAL, -- Need M + sl-CBR-SL-PRS-TxConfigList-r18 SEQUENCE (SIZE (1.. maxNrofSL-PRS-TxConfig-r18)) OF SL-CBR-SL-PRS-TxConfig-r18 + OPTIONAL -- Need M +} + +SL-CBR-LevelsDedicatedSL-PRS-RP-r18 ::= SEQUENCE (SIZE (0..maxCBR-LevelDedSL-PRS-1-r18)) OF SL-CBR-Dedicated-SL-PRS-RP-r18 + +SL-CBR-SL-PRS-TxConfig-r18 ::= SEQUENCE { + sl-PRS-CR-Limit-r18 INTEGER (0..10000) OPTIONAL, -- Need M + sl-PRS-MaxTx-power-r18 INTEGER (-30..33) OPTIONAL, -- Need M + sl-PRS-MaxNum-Transmissions-r18 INTEGER (1..32) OPTIONAL -- Need M +} + +SL-CBR-Dedicated-SL-PRS-RP-r18 ::= INTEGER (0..100) + +-- TAG-SL-CBR-COMMONTXDEDICATEDSL-PRS-RP-LIST-STOP +-- ASN1STOP +``` + +| SL-CBR-CommonTxDedicatedSL-PRS-RP-List field descriptions | | +|------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-CBR-RangeDedicatedSL-PRS-RP-List | Indicates the list of CBR ranges. Each entry of the list indicates in SL-CBR-LevelsConfig-Dedicated-SL-PRS-RP the upper bound of the CBR range for the respective entry. The upper bounds of the CBR ranges are configured in ascending order for consecutive entries of SL-CBR-LevelsConfig-Dedicated-SL-PRS-RP . For the first entry of SL-CBR-LevelsConfig-Dedicated-SL-PRS-RP the lower bound of the CBR range is 0. Value 0 corresponds to 0, value 1 to 0.01, value 2 to 0.02, and so on. | +| sl-CBR-SL-PRS-TxConfigList | Indicates the list of available SL PRS transmission parameters configurations. | +| sl-PRS-CR-Limit | Indicates the maximum limit on the occupancy ratio. Value 0 corresponds to 0, value 1 to 0.0001, value 2 to 0.0002, and so on (i.e. in steps of 0.0001) until value 10000, which corresponds to 1. | +| sl-PRS-MaxNum-Transmissions | Indicates maximum Number of SL PRS (re-)transmissions. | +| sl-PRS-MaxTx-power | Indicates maximum SL PRS transmission power. The unit is dBm. | + +#### SL-ConfigDedicatedNR + +The IE *SL-ConfigDedicatedNR* specifies the dedicated configuration information for NR sidelink communication/discovery/positioning. + +#### SL-ConfigDedicatedNR information element + +``` +-- ASN1START +-- TAG-SL-CONFIGDEDICATEDNR-START + +SL-ConfigDedicatedNR-r16 ::= SEQUENCE { + sl-PHY-MAC-RLC-Config-r16 SL-PHY-MAC-RLC-Config-r16 OPTIONAL, -- Need M + sl-RadioBearerToReleaseList-r16 SEQUENCE (SIZE (1..maxNrofSLRB-r16)) OF SLRB-Uu-ConfigIndex-r16 OPTIONAL, -- Need N + sl-RadioBearerToAddModList-r16 SEQUENCE (SIZE (1..maxNrofSLRB-r16)) OF SL-RadioBearerConfig-r16 OPTIONAL, -- Need N + sl-MeasConfigInfoToReleaseList-r16 SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-DestinationIndex-r16 OPTIONAL, -- Need N + sl-MeasConfigInfoToAddModList-r16 SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-MeasConfigInfo-r16 OPTIONAL, -- Need N + t400-r16 ENUMERATED {ms100, ms200, ms300, ms400, ms600, ms1000, ms1500, ms2000} OPTIONAL, -- Need M + ..., + [[ + sl-PHY-MAC-RLC-Config-v1700 SetupRelease { SL-PHY-MAC-RLC-Config-v1700 } OPTIONAL, -- Need M + sl-DiscConfig-r17 SetupRelease { SL-DiscConfig-r17} OPTIONAL -- Need M + ]], + [[ + sl-DiscConfig-v1800 SetupRelease { SL-DiscConfig-v1800} OPTIONAL -- Need M + ]] +} + +SL-DestinationIndex-r16 ::= INTEGER (0..maxNrofSL-Dest-1-r16) + +SL-PHY-MAC-RLC-Config-r16 ::= SEQUENCE { + sl-ScheduledConfig-r16 SetupRelease { SL-ScheduledConfig-r16 } OPTIONAL, -- Need M + sl-UE-SelectedConfig-r16 SetupRelease { SL-UE-SelectedConfig-r16 } OPTIONAL, -- Need M +} +``` + +``` + +sl-FreqInfoToReleaseList-r16 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF SL-Freq-Id-r16 OPTIONAL, -- Need N +sl-FreqInfoToAddModList-r16 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF SL-FreqConfig-r16 OPTIONAL, -- Need N +sl-RLC-BearerToReleaseList-r16 SEQUENCE (SIZE (1..maxSL-LCID-r16)) OF SL-RLC-BearerConfigIndex-r16 OPTIONAL, -- Need N +sl-RLC-BearerToAddModList-r16 SEQUENCE (SIZE (1..maxSL-LCID-r16)) OF SL-RLC-BearerConfig-r16 OPTIONAL, -- Need N +sl-MaxNumConsecutiveDTX-r16 ENUMERATED {n1, n2, n3, n4, n6, n8, n16, n32} OPTIONAL, -- Need M +sl-CSI-Acquisition-r16 ENUMERATED {enabled} OPTIONAL, -- Need R +sl-CSI-SchedulingRequestId-r16 SetupRelease {SchedulingRequestId} OPTIONAL, -- Need M +sl-SSB-PriorityNR-r16 INTEGER (1..8) OPTIONAL, -- Need R +networkControlledSyncTx-r16 ENUMERATED {on, off} OPTIONAL, -- Need M +} + +SL-PHY-MAC-RLC-Config-v1700 ::= SEQUENCE { + sl-DRX-Config-r17 SL-DRX-Config-r17 OPTIONAL, -- Need M + sl-RLC-ChannelToReleaseList-r17 SEQUENCE (SIZE (1..maxSL-LCID-r16)) OF SL-RLC-ChannelID-r17 OPTIONAL, -- Cond L2U2N + sl-RLC-ChannelToAddModList-r17 SEQUENCE (SIZE (1..maxSL-LCID-r16)) OF SL-RLC-ChannelConfig-r17 OPTIONAL, -- Cond L2U2N + ... + [[ + sl-RLC-BearerToAddModListSizeExt-v1800 SEQUENCE (SIZE (1..maxSL-LCID-r16)) OF SL-RLC-BearerConfig-r16 OPTIONAL, -- Need N + sl-RLC-BearerToReleaseListSizeExt-v1800 SEQUENCE (SIZE (1..maxSL-LCID-r16)) OF SL-RLC-BearerConfigIndex-v1800 OPTIONAL, -- Need N + sl-FreqInfoToAddModListExt-v1800 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF SL-FreqConfigExt-v1800 OPTIONAL, -- Need N + sl-LBT-SchedulingRequestId-r18 SetupRelease {SchedulingRequestId} OPTIONAL, -- Need M + sl-SyncFreqList-r18 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF SL-Freq-Id-r16 OPTIONAL, -- Need M + sl-SyncTxMultiFreq-r18 ENUMERATED {true} OPTIONAL, -- Need R + sl-MaxTransPowerCA-r18 P-Max OPTIONAL, -- Need R + sl-SCCH-CarrierSetConfig-r18 SetupRelease {SL-SCCH-CarrierSetConfig-r18} OPTIONAL, -- Need R + ]] +} + +SL-DiscConfig-r17 ::= SEQUENCE { + sl-RelayUE-Config-r17 SetupRelease { SL-RelayUE-Config-r17} OPTIONAL, -- Cond L2RelayUE + sl-RemoteUE-Config-r17 SetupRelease { SL-RemoteUE-Config-r17} OPTIONAL, -- Cond L2RemoteUE +} + +SL-DiscConfig-v1800 ::= SEQUENCE { + sl-RelayUE-ConfigU2U-r18 SetupRelease { SL-RelayUE-ConfigU2U-r18} OPTIONAL, -- Cond U2URelayUE + sl-RemoteUE-ConfigU2U-r18 SetupRelease { SL-RemoteUE-ConfigU2U-r18} OPTIONAL, -- Cond U2URemoteUE +} + +SL-SCCH-CarrierSetConfig-r18 ::= SEQUENCE { + sl-DestinationList-r18 SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-DestinationIdentity-r16, + sl-SRB-Identity-r18 SEQUENCE (SIZE (1..3)) OF SRB-Identity, + sl-AllowedCarrierFreqSet1-r18 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF INTEGER (1..maxNrofFreqSL-r16), + sl-AllowedCarrierFreqSet2-r18 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF INTEGER (1..maxNrofFreqSL-r16) +} + +-- TAG-SL-CONFIGDEDICATEDNR-STOP +-- ASN1STOP + +``` + +| SL-ConfigDedicatedNR field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-LBT-SchedulingRequestId
Indicates the scheduling request configuration applicable for sidelink consistent LBT failure report, as specified in TS 38.321 [3]. | +| sl-MaxTransPowerCA
The maximum total transmit power to be used by the UE across all sidelink carriers. | +| sl-MeasConfigInfoToAddModList
This field indicates the RSRP measurement configurations for unicast destinations to add and/or modify. | +| sl-MeasConfigInfoToReleaseList
This field indicates the RSRP measurement configurations for unicast destinations to remove. | +| sl-PHY-MAC-RLC-Config
This field indicates the lower layer sidelink radio bearer configurations. | +| sl-RadioBearerToAddModList
This field indicates one or multiple sidelink radio bearer configurations to add and/or modify. This field is not configured to the PC5 connection used for L2 U2N relay operation. | +| sl-RadioBearerToReleaseList
This field indicates one or multiple sidelink radio bearer configurations to remove. This field is not configured to the PC5 connection used for L2 U2N relay operation. | + +| SL-PHY-MAC-RLC-Config field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| networkControlledSyncTx
This field indicates whether the UE shall transmit synchronisation information (i.e. become synchronisation source). Value on indicates the UE to transmit synchronisation information while value off indicates the UE to not transmit such information. | +| sl-DRX-Config
This field indicates the sidelink DRX configuration(s) for unicast, groupcast and/or broadcast communication, as specified in TS 38.321 [3]. | +| sl-MaxNumConsecutiveDTX
This field indicates the maximum number of consecutive HARQ DTX before triggering sidelink RLF. Value n1 corresponds to 1, value n2 corresponds to 2, and so on. | +| sl-FreqInfoToAddModList, sl-FreqInfoToAddModListExt
This field indicates the NR sidelink communication configuration on some carrier frequency (ies) to add and/or modify. If the network includes sl-FreqInfoToAddModListExt , it includes the same number of entries, and listed in the same order, as in sl-FreqInfoToAddModList . | +| sl-FreqInfoToReleaseList
This field indicates the NR sidelink communication configuration on some carrier frequency (ies) to remove. In this release, only one entry can be configured in the list. | +| sl-RLC-BearerToAddModList, sl-RLC-BearerToAddModListSizeExt
This field indicates one or multiple sidelink RLC bearer configurations to add and/or modify. | +| sl-RLC-BearerToReleaseList, sl-RLC-BearerToReleaseListSizeExt
This field indicates one or multiple sidelink RLC bearer configurations to remove. | +| sl-RLC-ChannelToAddModList
This field indicates one or multiple PC5 Relay RLC Channel configurations to add and/or modify. Each PC5 Relay RLC channel configuration provided by network to L2 U2N Relay UE is uniquely associated with one L2 U2N Remote UE. | +| sl-RLC-ChannelToReleaseList
This field indicates one or multiple PC5 Relay RLC Channel configurations to remove. | +| sl-ScheduledConfig
Indicates the configuration for UE to transmit NR sidelink communication based on network scheduling. This field is not configured simultaneously with sl-UE-SelectedConfig . This field is not configured to a L2 U2N Remote UE. | +| sl-UE-SelectedConfig
Indicates the configuration used for UE autonomous resource selection. This field is not configured simultaneously with sl-ScheduledConfig . | +| sl-CSI-Acquisition
Indicates whether CSI reporting is enabled in sidelink unicast. If the field is absent, sidelink CSI reporting is disabled. | +| sl-CSI-SchedulingRequestId
If present, it indicates the scheduling request configuration applicable for Sidelink CSI Reporting MAC CE and Sidelink DRX Command MAC CE, as specified in TS 38.321 [3]. | +| sl-SSB-PriorityNR
This field indicates the priority of NR sidelink SSB transmission and reception. | +| sl-SyncFreqList
Indicates a list of candidate carrier frequencies that can be used for the synchronisation of NR sidelink communication. | +| sl-SyncTxMultiFreq
Indicates that the UE transmits S-SSB on multiple carrier frequencies for NR sidelink communication. If this field is absent, the UE transmits S-SSB only on the synchronisation carrier frequency. | + +| SL-SCCH-CarrierSetConfig field descriptions | | +|-------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-AllowedCarrierFreqSet1, sl-AllowedCarrierFreqSet2 | Indicates the set of carrier frequencies applicable for the transmission of the MAC SDUs from the sidelink SRB logical channels whose associated destination is included in sl-destinationList. If present, network ensures allowedCarrierFreqSet1 and allowedCarrierFreqSet2 do not include the same carrier frequency. The value 1 corresponds to the frequency of first entry in sl-FreqInfoList broadcast in SIB12 , the value 2 corresponds to the frequency of first entry in sl-FreqInfoListSizeExt broadcast in SIB12 , the value 3 corresponds to the frequency of second entry in sl-FreqInfoListSizeExt broadcast in SIB12 and so on. | +| sl-DestinationList | This field indicates the list of destination identify that the allowedCarrierFreqSet1 and allowedCarrierFreqSet2 apply. Only destination identity for unicast link can be included in this field. | +| sl-SRB-Identity | This field indicates the list of sidelink SRB identities that the allowedCarrierFreqSet1 and allowedCarrierFreqSet2 apply. | + +| Conditional Presence | Explanation | +|-----------------------------|----------------------------------------------------------------------------------------------------------| +| L2RelayUE | For L2 U2N Relay UE, the field is optionally present, Need M. Otherwise, it is absent. | +| L2RemoteUE | For L2 U2N Remote UE, the field is optionally present, Need M. Otherwise, it is absent. | +| L2U2N | The field is optional present for L2 U2N Relay UE and L2 U2N Remote UE, need N. Otherwise, it is absent. | +| L2U2U | The field is optional present for L2 U2U Relay UE and L2 U2U Remote UE, need N. Otherwise, it is absent. | +| U2URelayUE | For U2U Relay UE, the field is optionally present, Need M. Otherwise, it is absent. | +| U2URemoteUE | For U2U Remote UE, the field is optionally present, Need M. Otherwise, it is absent. | + +#### -- **SL-ConfiguredGrantConfig** + +The IE *SL-ConfiguredGrantConfig* specifies the configured grant configuration information for NR sidelink communication. + +#### **SL-ConfiguredGrantConfig information element** + +``` +-- ASN1START +-- TAG-SL-CONFIGUREDGRANTCONFIG-START + +SL-ConfiguredGrantConfig-r16 ::= + sl-ConfigIndexCG-r16 + sl-PeriodCG-r16 + sl-NrOfHARQ-Processes-r16 + sl-HARQ-ProcID-offset-r16 + sl-CG-MaxTransNumList-r16 + rrc-ConfiguredSidelinkGrant-r16 + SEQUENCE { + SL-ConfigIndexCG-r16, + SL-PeriodCG-r16 + INTEGER (1..16) + INTEGER (0..15) + SL-CG-MaxTransNumList-r16 + SEQUENCE { + sl-TimeResourceCG-Type1-r16 + sl-StartSubchannelCG-Type1-r16 + sl-FreqResourceCG-Type1-r16 + sl-TimeOffsetCG-Type1-r16 + sl-N1PUCCH-AN-r16 + sl-PSFCH-ToPUCCH-CG-Type1-r16 + sl-ResourcePoolID-r16 + sl-TimeReferenceSFN-Type1-r16 + } + } + OPTIONAL, -- Need M + OPTIONAL, -- Need M + OPTIONAL, -- Need M + OPTIONAL, -- Need M + OPTIONAL, -- Need M + OPTIONAL, -- Need M + OPTIONAL, -- Need M + OPTIONAL, -- Need M + OPTIONAL, -- Need M + OPTIONAL, -- Need M + OPTIONAL, -- Need M + OPTIONAL, -- Need R + OPTIONAL, -- Need M + OPTIONAL, -- Need M + OPTIONAL, -- Need M + OPTIONAL, -- Need S +``` + +``` + } OPTIONAL, -- Need M + ... + [[ + sl-N1PUCCH-AN-Type2-r16 PUCCH-ResourceId OPTIONAL -- Need M + ]], + [[ + sl-StartRBsetCG-Type1-r18 INTEGER (0..4) OPTIONAL -- Need M + ]] +} + +SL-ConfigIndexCG-r16 ::= INTEGER (0..maxNrofCG-SL-1-r16) + +SL-CG-MaxTransNumList-r16 ::= SEQUENCE (SIZE (1..8)) OF SL-CG-MaxTransNum-r16 + +SL-CG-MaxTransNum-r16 ::= SEQUENCE { + sl-Priority-r16 INTEGER (1..8), + sl-MaxTransNum-r16 INTEGER (1..32) +} + +SL-PeriodCG-r16 ::= CHOICE{ + sl-PeriodCG1-r16 ENUMERATED {ms100, ms200, ms300, ms400, ms500, ms600, ms700, ms800, ms900, ms1000, spare6, + spare5, spare4, spare3, spare2, spare1}, + sl-PeriodCG2-r16 INTEGER (1..99) +} + +-- TAG-SL-CONFIGUREDGRANTCONFIG-STOP +-- ASN1STOP +``` + +| SL-ConfiguredGrantConfig field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| rrc-ConfiguredSidelinkGrant
Configuration for "sidelink configured grant" transmission with fully RRC-configured SL grant (Type1). If this field is not configured, the UE uses SL grant configured by DCI addressed to SL-CS-RNTI (Type2). | +| sl-ConfigIndexCG
This field indicates the ID to identify sidelink configured grant. | +| sl-CG-MaxTransNumList
This field indicates the maximum number of times that a TB can be transmitted using the resources provided by the sidelink configured grant. sl-Priority corresponds to the logical channel priority. | +| sl-FreqResourceCG-Type1
Indicates the frequency resource location of sidelink configured grant type 1. An index giving valid combinations of one or two starting sub-channel and length (jointly encoded) as resource indicator value (RIV), as defined in TS 38.214 [19]. | +| sl-HARQ-ProcID-Offset
Indicates the offset used in deriving the HARQ process ID for sidelink configured grant type 1 or sidelink configured grant type 2, see TS 38.321 [3], clause 5.8.3. | +| sl-N1PUCCH-AN
This field indicates the PUCCH resource for HARQ feedback for sidelink configured grant type 1. The actual PUCCH-Resource is configured in sl-PUCCH-Config and referred to by its ID. | +| sl-N1PUCCH-AN-Type2
This field indicates the PUCCH resource for HARQ feedback for PSCCH/PSSCH transmissions without a corresponding PDCCH on sidelink configured grant type 2. The actual PUCCH-Resource is configured in sl-PUCCH-Config and referred to by its ID. | +| sl-NrOfHARQ-Processes
This field indicates the number of HARQ processes configured for a specific sidelink configured grant. It applies for both type 1 and type 2. | +| sl-PeriodCG
This field indicates the period of sidelink configured grant in the unit of ms. | +| sl-PSFCH-ToPUCCH-CG-Type1
This field, for sidelink configured grant type 1, indicates slot offset between the PSFCH associated with the last PSSCH resource of each period and the PUCCH occasion used for reporting sidelink HARQ. | +| sl-ResourcePoolID
Indicates the resource pool in which the sidelink configured grant type 1 is applied. | +| sl-StartRBsetCG-Type1
Indicates starting RB set index of the initial PSSCH transmission of the sidelink configured grant Type 1 for interlace RB-based PSSCH transmission. | +| sl-StartSubchannelCG-Type1
This field indicates the starting sub-channel of sidelink configured grant type 1. An index giving valid sub-channel index. | +| sl-TimeOffsetCG-Type1
This field indicates the slot offset with respect to logical slot defined by sl-TimeReferenceSFN-Type1 , as specified in TS 38.321 [3]. | +| sl-TimeReferenceSFN-Type1
Indicates SFN used for determination of the offset of a resource in time domain. If it is present, the UE uses the 1 st logical slot of associated resource pool after the starting time of the closest SFN with the indicated number preceding the reception of the sidelink configured grant configuration type 1 as reference logical slot, see TS 38.321 [3], clause 5.8.3. If it is not present, the reference SFN is 0. | +| sl-TimeResourceCG-Type1
This field indicates the time resource location of sidelink configured grant type 1. An index giving valid combinations of up to two slot positions (jointly encoded) as time resource indicator value (TRIV), as defined in TS 38.212 [17]. | + +#### – *SL-ConfiguredGrantConfigDedicated-SL-PRS-RP* + +The IE *SL-ConfiguredGrantConfig-Dedicated-SL-PRS-RP* specifies the configured grant configuration information for NR sidelink positioning in a dedicated SL-PRS resource pool. + +#### ***SL-ConfiguredGrantConfigDedicated-SL-PRS-RP* information element** + +``` +-- ASN1START +-- TAG-SL-CONFIGUREDGRANTCONFIGDEDICATEDSL-PRS-RP-START + +SL-ConfiguredGrantConfigDedicatedSL-PRS-RP-r18 ::= SEQUENCE { + sl-ConfigIndexCG-r18 SL-ConfigIndexCG-r16, + sl-PeriodCG-r18 SL-PeriodCG-r16 OPTIONAL, -- Need M + sl-TimeOffsetCG-Type1-r18 INTEGER (0..7999) OPTIONAL, -- Need R + sl-TimeReferenceSFN-Type1-r18 ENUMERATED {sfn512} OPTIONAL, -- Need S + sl-ResourcePoolID-r18 SL-ResourcePoolID-r16 OPTIONAL, -- Need M + sl-TimeResourceCG-Type1-r18 INTEGER (0..496) OPTIONAL, -- Need M + sl-PRS-ResourceIndicationFirstType1-r18 INTEGER (0..11) OPTIONAL, -- Need M + sl-PRS-ResourceIndicationFutureType1-r18 INTEGER (0..143) OPTIONAL -- Need M +} + +-- TAG-SL-CONFIGUREDGRANTCONFIGDEDICATEDSL-PRS-RP-STOP +-- ASN1STOP +``` + +| SL-ConfiguredGrantConfig field descriptions | | +|----------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-ConfigIndexCG | This field indicates the ID to identify sidelink configured grant. | +| sl-PeriodCG | This field indicates the period of SL PRS configured grant in a dedicated resources in ms for either CG type 1 or CG type 2. | +| sl-ResourcePoolID | Indicates the resource pool in which the configured sidelink grant Type 1 is applied. | +| sl-TimeOffsetCG-Type1 | This field indicates the slot offset with respect to logical slot defined by sl-TimeReferenceSFN-Type1-Dedicated-SL-PRS-RP , as specified in TS 38.321 [3]. | +| sl-TimeReferenceSFN-Type1 | Indicates SFN used for determination of the offset of a resource in time domain. If it is present, the UE uses the 1 st logical slot of associated resource pool after the starting time of the closest SFN with the indicated number preceding the reception of the sidelink configured grant configuration type 1 as reference logical slot, see TS 38.321 [3], clause 5.8.3. If it is not present, the reference SFN is 0. | +| sl-TimeResourceCG-Type1 | This field indicates the time resource location of sidelink configured grant type 1. An index giving valid combinations of up to two slot positions (jointly encoded) as time resource indicator value (TRIV), as defined in TS 38.212 [17]. | +| sl-PRS-ResourceIndicationFirstType1 | Indicates SL-PRS Resource ID for the first SL-PRS transmission. | +| sl-PRS-ResourceIndicationFutureType1 | Indicates SL-PRS resource IDs for future SL PRS transmissions. An index giving valid combinations of up to two SL PRS resource IDs (jointly encoded) . | + +#### — *SL-DestinationIdentity* + +The IE *SL-DestinationIdentity* is used to identify a destination of a NR sidelink communication. + +#### ***SL-DestinationIdentity* information element** + +``` +-- ASN1START +-- TAG-SL-DESTINATIONIDENTITY-START + +SL-DestinationIdentity-r16 ::= BIT STRING (SIZE (24)) + +-- TAG-SL-DESTINATIONIDENTITY-STOP +-- ASN1STOP +``` + +#### — *SL-DRX-Config* + +The IE *SL-DRX-Config* is used to configure DRX related parameters for NR sidelink communication/discovery. The SL DRX timers should be calculated in the unit of physical slot. + +#### ***SL-DRX-Config* information element** + +``` +-- ASN1START +``` + +``` + +-- TAG-SL-DRX-CONFIG-START + +SL-DRX-Config-r17 ::= + sl-DRX-ConfigGC-BC-r17 SEQUENCE { + sl-DRX-ConfigGC-BC-r17 OPTIONAL, -- Cond HO + sl-DRX-ConfigUC-ToReleaseList-r17 SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-DestinationIndex-r16 OPTIONAL, -- Need N + sl-DRX-ConfigUC-ToAddModList-r17 SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-DRX-ConfigUC-Info-r17 OPTIONAL, -- Need N + ... + } + +SL-DRX-ConfigUC-Info-r17 ::= + SEQUENCE { + sl-DestinationIndex-r17 OPTIONAL, -- Need N + sl-DRX-ConfigUC-r17 OPTIONAL, -- Need N + ... + } + +-- TAG-SL-DRX-CONFIG-STOP +-- ASN1STOP + +``` + +#### SL-DRX-Config field descriptions + +| | | +|--------------------------------------|--------------------------------------------------------------------------------------------------------------------------------| +| sl-DRX-ConfigGC-BC | This field indicates the sidelink DRX configurations for groupcast and broadcast communication, as specified in TS 38.321 [3]. | +| sl-DRX-ConfigUC-ToReleaseList | This field indicates the sidelink DRX configurations for corresponding unicast destinations to remove. | +| sl-DRX-ConfigUC-ToAddModList | This field indicates the sidelink DRX configurations for corresponding unicast destinations to add and/or modify. | + +| Conditional Presence | Explanation | +|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| HO | This field is optionally present, need M, in an RRCReconfiguration message including reconfigurationWithSync ; otherwise it is absent, Need M. | + +#### – SL-DRX-ConfigGC-BC + +The IE *SL-DRX-ConfigGC-BC* is used to configure DRX related parameters for NR sidelink groupcast and broadcast communication, unicast/broadcast based communication of Direct Link Establishment Request (TS 24.587 [57]), and discovery message (TS 24.554 [72]). + +#### SL-DRX-ConfigGC-BC information element + +``` + +-- ASN1START +-- TAG-SL-DRX-CONFIGGC-BC-START + +SL-DRX-ConfigGC-BC-r17 ::= + SEQUENCE { + sl-DRX-GC-BC-PerQoS-List-r17 SEQUENCE (SIZE (1..maxSL-GC-BC-DRX-QoS-r17)) OF SL-DRX-GC-BC-QoS-r17 OPTIONAL, -- Need M + sl-DRX-GC-generic-r17 SL-DRX-GC-Generic-r17 OPTIONAL, -- Need M + } + +``` + +``` + +sl-DefaultDRX-GC-BC-r17 SL-DRX-GC-BC-QoS-r17 OPTIONAL, -- Need M +... +} + +SL-DRX-GC-BC-QoS-r17 ::= + SEQUENCE { + sl-DRX-GC-BC-MappedQoS-FlowList-r17 SEQUENCE (SIZE (1..maxNrofSL-QFIs-r16)) OF SL-QoS-Profile-r16 OPTIONAL, -- Need M + sl-DRX-GC-BC-OnDurationTimer-r17 CHOICE { + subMilliSeconds INTEGER (1..31), + milliSeconds ENUMERATED { + ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, + ms80, ms100, ms200, ms300, ms400, ms500, ms600, ms800, ms1000, ms1200, + ms1600, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1} + }, + } + sl-DRX-GC-InactivityTimer-r17 ENUMERATED { + ms0, ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, ms80, + ms100, ms200, ms300, ms500, ms750, ms1280, ms1920, ms2560, spare9, spare8, + spare7, spare6, spare5, spare4, spare3, spare2, spare1}, + } + sl-DRX-GC-BC-Cycle-r17 ENUMERATED { + ms10, ms20, ms32, ms40, ms60, ms64, ms70, ms80, ms128, ms160, ms256, ms320, ms512, + ms640, ms1024, ms1280, ms2048, ms2560, ms5120, ms10240, spare12, spare11, spare10, + spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1}, + } + ... + } + +SL-DRX-GC-Generic-r17 ::= + SEQUENCE { + sl-DRX-GC-HARQ-RTT-Timer1-r17 ENUMERATED {sl0, sl1, sl2, sl4, spare4, spare3, spare2, spare1} OPTIONAL, -- Need M + sl-DRX-GC-HARQ-RTT-Timer2-r17 ENUMERATED {sl0, sl1, sl2, sl4, spare4, spare3, spare2, spare1} OPTIONAL, -- Need M + sl-DRX-GC-RetransmissionTimer-r17 ENUMERATED { + sl0, sl1, sl2, sl4, sl6, sl8, sl16, sl24, sl33, sl40, sl64, sl80, sl96, sl112, sl128, + sl160, sl320, spare15, spare14, spare13, spare12, spare11, spare10, spare9, spare8, + spare7, spare6, spare5, spare4, spare3, spare2, spare1} + } + +-- TAG-SL-DRX-CONFIGGC-BC-STOP +-- ASN1STOP + +``` + +| SL-DRX-ConfigGC-BC field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-DefaultDRX-GC-BC
Indicates the default sidelink DRX configuration for groupcast and broadcast communications, which is used for QoS profile(s) that cannot be mapped into DRX configuration(s) configured for dedicated QoS profile(s). This field can be applied for the broadcast based or unicast based communication of Direct Link Establishment Request as described in TS 24.587 [57], ProSe Direct Link Establishment Request message and discovery message as described in TS 24.554 [72]. | +| sl-DRX-GC-BC-PerQoS-List
List of one or multiple sidelink DRX configurations for groupcast and broadcast communication, which are mapped from QoS profile(s). | +| sl-DRX-GC-BC-Cycle
Value in ms, ms10 corresponds to 10ms, ms20 corresponds to 20 ms, ms32 corresponds to 32 ms, and so on. | +| sl-DRX-GC-BC-MappedQoS-FlowsList
List of QoS profiles of the NR sidelink communication, which are mapped to a sidelink DRX configuration. | +| sl-DRX-GC-BC-OnDurationTimer
Value in multiples of 1/32 ms (subMilliSeconds) or in ms (milliSecond). For the latter, value ms1 corresponds to 1 ms, value ms2 corresponds to 2 ms, and so on. | +| sl-DRX-GC-HARQ-RTT-Timer1, sl-DRX-GC-HARQ-RTT-Timer2
Value in number of slot lengths of the sidelink BWP where the transport block was received. Value sl0 corresponds to 0 slots, sl1 corresponds to 1 slot, sl2 corresponds to 2 slots, and so on. sl-DRX-GC-HARQ-RTT-Timer1 is used for HARQ feedback enabled sidelink retransmission if SCI does not indicate retransmission resource(s). sl-DRX-GC-HARQ-RTT-Timer2 is used for HARQ feedback disabled sidelink retransmission in resource pool configured with PSFCH if SCI does not indicate retransmission resource(s). | +| sl-DRX-GC-Generic
Indicates a sidelink DRX configuration for groupcast communication, which is applicable to any QoS profile or any Destination Layer-2 ID. | +| sl-DRX-GC-InactivityTimer
Value in multiple integers of 1 ms, ms0 corresponds to 0, ms1 corresponds to 1 ms, ms2 corresponds to 2 ms, and so on. This field is only valid for groupcast communication. | +| sl-DRX-GC-RetransmissionTimer
Value in number of slot lengths of the sidelink BWP where the transport block was received. Value sl0 corresponds to 0 slots, sl1 corresponds to 1 slot, sl2 corresponds to 2 slots, and so on. | + +#### SL-DRX-ConfigUC + +The IE *SL-DRX-ConfigUC* is used to configure sidelink DRX related parameters for unicast communication. + +#### SL-DRX-ConfigUC information element + +``` +-- ASN1START +-- TAG-DRX-CONFIGUC-START + +SL-DRX-ConfigUC-r17 ::= + sl-drx-onDurationTimer-r17 SEQUENCE { + CHOICE { + subMilliSeconds INTEGER (1..31), + milliSeconds ENUMERATED { + ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, + ms80, ms100, ms200, ms300, ms400, ms500, ms600, ms800, ms1000, ms1200, + ms1600, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 + }, + }, + sl-drx-InactivityTimer-r17 ENUMERATED { + ms0, ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, ms80, + ms100, ms200, ms300, ms500, ms750, ms1280, ms1920, ms2560, spare9, spare8, + }, + } +``` + +``` + + spare7, spare6, spare5, spare4, spare3, spare2, spare1}, +sl-drx-HARQ-RTT-Timer1-r17 ENUMERATED {s10, s11, s12, s14, spare4, spare3, spare2, spare1} OPTIONAL, -- Need M +sl-drx-HARQ-RTT-Timer2-r17 ENUMERATED {s10, s11, s12, s14, spare4, spare3, spare2, spare1} OPTIONAL, -- Need M +sl-drx-RetransmissionTimer-r17 ENUMERATED { + s10, s11, s12, s14, s16, s18, s116, s124, s133, s140, s164, s180, s196, s1112, s1128, + s1160, s1320, spare15, spare14, spare13, spare12, spare11, spare10, spare9, + spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1}, +sl-drx-CycleStartOffset-r17 CHOICE { + ms10 INTEGER(0..9), + ms20 INTEGER(0..19), + ms32 INTEGER(0..31), + ms40 INTEGER(0..39), + ms60 INTEGER(0..59), + ms64 INTEGER(0..63), + ms70 INTEGER(0..69), + ms80 INTEGER(0..79), + ms128 INTEGER(0..127), + ms160 INTEGER(0..159), + ms256 INTEGER(0..255), + ms320 INTEGER(0..319), + ms512 INTEGER(0..511), + ms640 INTEGER(0..639), + ms1024 INTEGER(0..1023), + ms1280 INTEGER(0..1279), + ms2048 INTEGER(0..2047), + ms2560 INTEGER(0..2559), + ms5120 INTEGER(0..5119), + ms10240 INTEGER(0..10239) +}, +sl-drx-SlotOffset INTEGER (0..31) +} + +-- TAG-SL-DRX-CONFIGUC-STOP +-- ASN1STOP + +``` + +| SL-DRX-ConfigUC field descriptions | | +|-------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-drx-CycleStartOffset | Sidelink drx-Cycle in ms and sidelink drx-StartOffset in multiples of 1 ms. | +| sl-drx-HARQ-RTT-Timer1, sl-drx-HARQ-RTT-Timer2 | Value in number of slot lengths of the BWP where the transport block was received. Value sl0 corresponds to 0 slots, sl1 corresponds to 1 slot, sl2 corresponds to 2 slots, and so on. sl-drx-HARQ-RTT-Timer1 is used for HARQ feedback enabled sidelink retransmission if SCI does not indicate retransmission resource(s). sl-drx-HARQ-RTT-Timer2 is used for HARQ feedback disabled sidelink retransmission in resource pool configured with PSFCH if SCI does not indicate retransmission resource(s). | +| sl-drx-InactivityTimer | Value in number of slot lengths of the BWP where the transport block was received, sl0 corresponds to 0, sl1 corresponds to 1 slot, sl2 corresponds to 2 slots, and so on. | +| sl-drx-onDurationTimer | Value in multiples of 1/32 ms (subMilliSeconds) or in ms (milliSecond). For the latter, value ms1 corresponds to 1 ms, value ms2 corresponds to 2 ms, and so on. | +| sl-drx-RetransmissionTimer | Value in number of slot lengths of the BWP where the transport block was received. Value sl0 corresponds to 0 slots, sl1 corresponds to 1 slot, sl2 corresponds to 2 slots, and so on. | +| sl-drx-SlotOffset | Value in 1/32 ms. Value 0 corresponds to 0 ms, value 1 corresponds to 1/32 ms, value 2 corresponds to 2/32 ms, and so on. | + +#### – SL-DRX-ConfigUC-SemiStatic + +The IE *SL-DRX-ConfigUC-SemiStatic* is used to indicate the semi-static sidelink DRX related parameters for unicast communication. + +#### SL-DRX-ConfigUC-SemiStatic information element + +``` +-- ASN1START +-- TAG-DRX-CONFIGUCSEMISTATIC-START + +SL-DRX-ConfigUC-SemiStatic-r17 ::= + sl-drx-onDurationTimer-r17 + sl-drx-CycleStartOffset-r17 + + SEQUENCE { + CHOICE { + subMilliSeconds INTEGER (1..31), + milliSeconds ENUMERATED { + ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, + ms80, ms100, ms200, ms300, ms400, ms500, ms600, ms800, ms1000, ms1200, + ms1600, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 + }, + }, + CHOICE { + ms10 INTEGER (0..9), + ms20 INTEGER (0..19), + ms32 INTEGER (0..31), + ms40 INTEGER (0..39), + ms60 INTEGER (0..59), + ms64 INTEGER (0..63), + ms70 INTEGER (0..69), + ms80 INTEGER (0..79), + ms128 INTEGER (0..127), + ms160 INTEGER (0..159), + ms256 INTEGER (0..255), + }, + } +} +``` + +``` + + ms320 INTEGER (0..319), + ms512 INTEGER (0..511), + ms640 INTEGER (0..639), + ms1024 INTEGER (0..1023), + ms1280 INTEGER (0..1279), + ms2048 INTEGER (0..2047), + ms2560 INTEGER (0..2559), + ms5120 INTEGER (0..5119), + ms10240 INTEGER (0..10239) + }, + sl-drx-SlotOffset-r17 INTEGER (0..31) +} + +-- TAG-SL-DRX-CONFIGUCSEMISTATIC-STOP +-- ASN1STOP + +``` + +#### SL-FreqConfig + +The IE *SL-FreqConfig* specifies the dedicated configuration information on one particular carrier frequency for NR sidelink communication. + +#### SL-FreqConfig information element + +``` + +-- ASN1START +-- TAG-SL-FREQCONFIG-START + +SL-FreqConfig-r16 ::= + SEQUENCE { + sl-Freq-Id-r16 SL-Freq-Id-r16, + sl-SCS-SpecificCarrierList-r16 SEQUENCE (SIZE (1..maxSCSs)) OF SCS-SpecificCarrier, + sl-AbsoluteFrequencyPointA-r16 ARFCN-ValueNR OPTIONAL, -- Need M + sl-AbsoluteFrequencySSB-r16 ARFCN-ValueNR OPTIONAL, -- Need R + frequencyShift7p5khzSL-r16 ENUMERATED {true} OPTIONAL, -- Cond V2X-SL-Shared + valueN-r16 INTEGER (-1..1), + sl-BWP-ToReleaseList-r16 SEQUENCE (SIZE (1..maxNrofSL-BWPs-r16)) OF BWP-Id OPTIONAL, -- Need N + sl-BWP-ToAddModList-r16 SEQUENCE (SIZE (1..maxNrofSL-BWPs-r16)) OF SL-BWP-Config-r16 OPTIONAL, -- Need N + sl-SyncConfigList-r16 SL-SyncConfigList-r16 OPTIONAL, -- Need M + sl-SyncPriority-r16 ENUMERATED {gnss, gnbEnb} OPTIONAL, -- Need M + } + +SL-Freq-Id-r16 ::= + INTEGER (1.. maxNrofFreqSL-r16) + +SL-FreqConfigExt-v1800 ::= + SEQUENCE { + absenceOfAnyOtherTechnology-r18 ENUMERATED {true} OPTIONAL, -- Need M + sl-FreqSelectionConfig-r18 SL-FreqSelectionConfig-r18 OPTIONAL, -- Need M + sl-SyncTxDisabled-r18 ENUMERATED {true} OPTIONAL, -- Need M + sl-EnergyDetectionConfig-r18 CHOICE { + sl-MaxEnergyDetectionThreshold-r18 INTEGER (-85..-52), + sl-EnergyDetectionThresholdOffset-r18 INTEGER (-13..20) + } + ue-ToUE-COT-SharingED-Threshold-r18 INTEGER (-85..-52) OPTIONAL, -- Need M + } + +``` + +``` + harq-ACKFeedbackRatioforCW-AdjustmentGC-Option2-r18 INTEGER (10..100) OPTIONAL, -- Need M + ... +} + +-- TAG-SL-FREQCONFIG-STOP +-- ASN1STOP +``` + +| SL-FreqConfig field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| absenceOfAnyOtherTechnology
Presence of this field indicates absence on a long term basis (e.g. by level of regulation) of any other technology sharing the carrier; absence of this field indicates the potential presence of any other technology sharing the carrier, as specified in TS 37.213 [48] clauses 4.5. This parameter is not expected to be provided if the sidelink carrier is overlapped with uplink carrier. | +| sl-EnergyDetectionConfig
Indicates whether to use the maxEnergyDetectionThreshold or the energyDetectionThresholdOffset (see TS 37.213 [48], clause 4.5.5). | +| sl-EnergyDetectionThresholdOffset
Indicates the offset to the default maximum energy detection threshold value. Unit in dB. Value -13 corresponds to -13dB, value -12 corresponds to -12dB, and so on (i.e. in steps of 1dB) as specified in TS 37.213 [48], clause 4.5.5. | +| frequencyShift7p5khzSL
Enable the NR SL transmission with a 7.5 kHz shift to the LTE raster. If the field is absent, the frequency shift is disabled. | +| harq-ACKFeedbackRatioforCW-AdjustmentGC-Option2
Indicates the ratio threshold for contention window adjustment for SL groupcast option 2 as specified in TS 37.213 [48], clause 4.5.4. Unit is percentage. | +| sl-MaxEnergyDetectionThreshold
Indicates the absolute maximum energy detection threshold value. Unit in dBm. Value -85 corresponds to -85 dBm, value -84 corresponds to -84 dBm, and so on (i.e. in steps of 1dBm) as specified in TS 37.213 [48], clause 4.5.5. | +| sl-AbsoluteFrequencyPointA
Absolute frequency of the reference resource block (Common RB 0). Its lowest subcarrier is also known as Point A. | +| sl-AbsoluteFrequencySSB
Indicates the frequency location of sidelink SSB. The transmission bandwidth for sidelink SSB is within the bandwidth of this sidelink BWP. | +| sl-BWP-ToAddModList
This field indicates the list of sidelink BWP(s) on which the NR sidelink communication configuration is to be added or reconfigured. In this release, only one BWP is allowed to be configured for NR sidelink communication. | +| sl-BWP-ToReleaseList
This field indicates the list of sidelink BWP(s) on which the NR sidelink communication configuration is to be released. | +| sl-Freq-Id
This field indicates the identity of the dedicated configuration information on the carrier frequency for NR sidelink communication. | +| sl-SCS-SpecificCarrierList
A set of UE specific channel bandwidth and location configurations for different subcarrier spacings (numerologies). Defined in relation to Point A. The UE uses the configuration provided in this field only for the purpose of channel bandwidth and location determination. In this release, only one SCS-SpecificCarrier is allowed to be configured for NR sidelink communication. | +| sl-SyncTxDisabled
Indicates that the carrier, even though equipped with synchronisation resources, cannot be used as a synchronisation carrier frequency to transmit S-SSB. | +| sl-SyncPriority
This field indicates synchronization priority order, as specified in clause 5.8.6. All values in sl-SyncPriority are same across all carrier frequencies configured for UEs performing NR sidelink communication on multiple carrier frequencies. | +| ue-ToUE-COT-SharingED-Threshold
Indicates the energy detection threshold that is to be used by a UE to initiate a channel occupancy to be shared to other UE(s), and another UE that shares the initiated channel occupancy shall use this configured parameter for accessing the channel(s) as specified in TS 37.213 [48], clause 4.5.5 for sidelink channel access. Unit in dBm. Value -85 corresponds to -85 dBm, value -84 corresponds to -84 dBm, and so on (i.e. in steps of 1dBm). | + +###### **valueN** + +Indicate the NR SL transmission with a valueN \*5kHz shift to the LTE raster. (see TS 38.101-1 [15], clause 5.4E.2). + +| Conditional Presence | Explanation | +|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| V2X-SL-Shared | This field is mandatory present if the carrier frequency configured for NR sidelink communication is shared by V2X sidelink communication. It is absent, Need R, otherwise. | + +#### SL-FreqConfigCommon + +The IE *SL-FreqConfigCommon* specifies the cell-specific configuration information on one particular carrier frequency for NR sidelink communication. + +#### SL-FreqConfigCommon information element + +``` +-- ASN1START +-- TAG-SL-FREQCONFIGCOMMON-START + +SL-FreqConfigCommon-r16 ::= SEQUENCE { + sl-SCS-SpecificCarrierList-r16 SEQUENCE (SIZE (1..maxSCSs)) OF SCS-SpecificCarrier, + sl-AbsoluteFrequencyPointA-r16 ARFCN-ValueNR, + sl-AbsoluteFrequencySSB-r16 ARFCN-ValueNR OPTIONAL, -- Need R + frequencyShift7p5khzSL-r16 ENUMERATED {true} OPTIONAL, -- Cond V2X-SL-Shared + valueN-r16 INTEGER (-1..1), + sl-BWP-List-r16 SEQUENCE (SIZE (1..maxNrofSL-BWPs-r16)) OF SL-BWP-ConfigCommon-r16 OPTIONAL, -- Need R + sl-SyncPriority-r16 ENUMERATED {gnss, gnbEnb} OPTIONAL, -- Need R + sl-NbAsSync-r16 BOOLEAN OPTIONAL, -- Need R + sl-SyncConfigList-r16 SL-SyncConfigList-r16 OPTIONAL, -- Need R + ... + [[ + absenceOfAnyOtherTechnology-r18 ENUMERATED {true} OPTIONAL, -- Need R + sl-FreqSelectionConfig-r18 SL-FreqSelectionConfig-r18 OPTIONAL, -- Need R + sl-SyncTxDisabled-r18 ENUMERATED {true} OPTIONAL, -- Need R + sl-EnergyDetectionConfig-r18 CHOICE { + sl-MaxEnergyDetectionThreshold-r18 INTEGER (-85..-52), + sl-EnergyDetectionThresholdOffset-r18 INTEGER (-13..20) + } OPTIONAL, -- Need R + ue-toUE-COT-SharingED-Threshold-r18 INTEGER (-85..-52) OPTIONAL, -- Need R + harq-ACKFeedbackRatioforContentionWindowAdjustmentGC-Option2-r18 INTEGER (10..100) OPTIONAL, -- Need R + ]] +} + +-- TAG-SL-FREQCONFIGCOMMON-STOP +-- ASN1STOP +``` + +| SL-FreqConfigCommon field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| absenceOfAnyOtherTechnology
Presence of this field indicates absence on a long term basis (e.g. by level of regulation) of any other technology sharing the carrier; absence of this field indicates the potential presence of any other technology sharing the carrier, as specified in TS 37.213 [48] clauses 4.5.5. This parameter is not expected to be provided if the sidelink carrier is overlapped with uplink carrier. | +| sl-EnergyDetectionConfig
Indicates whether to use the maxEnergyDetectionThreshold or the energyDetectionThresholdOffset (see TS 37.213 [48], clause 4.5.5). | +| sl-EnergyDetectionThresholdOffset
Indicates the offset to the default maximum energy detection threshold value. Unit in dB. Value -13 corresponds to -13dB, value -12 corresponds to -12dB, and so on (i.e. in steps of 1dB) as specified in TS 37.213 [48], clause 4.5.5. | +| frequencyShift7p5khzSL
Enable the NR SL transmission with a 7.5 kHz shift to the LTE raster. If the field is absent, the frequency shift is disabled. | +| harq-ACKFeedbackRatioforContentionWindowAdjustmentGC-Option2
Indicates the ratio threshold for contention window adjustment for SL groupcast option 2 as specified in TS 37.213 [48], clause 4.5.4. Unit is percentage. | +| sl-MaxEnergyDetectionThreshold
Indicates the absolute maximum energy detection threshold value. Unit in dBm. Value -85 corresponds to -85 dBm, value -84 corresponds to -84 dBm, and so on (i.e. in steps of 1dBm) as specified in TS 37.213 [48], clause 4.5.5. | +| sl-AbsoluteFrequencyPointA
Absolute frequency of the reference resource block (Common RB 0). Its lowest subcarrier is also known as Point A. | +| sl-AbsoluteFrequencySSB
Indicates the frequency location of sidelink SSB. The transmission bandwidth for sidelink SSB is within the bandwidth of this sidelink BWP. | +| sl-BWP-List
This field indicates the list of sidelink BWP(s) on which the NR sidelink communication configuration. In this release, only one BWP is allowed to be configured for NR sidelink communication. | +| sl-NbAsSync
This field indicates whether the network can be selected as synchronization reference directly/indirectly only, if sl-SyncPriority is set to gnss. If this field is set to TRUE, the network is enabled to be selected as synchronization reference directly/indirectly. The field is only present in SidelinkPreconfigNR . Otherwise it is absent. All values in sl-NbAsSync are same across all carrier frequencies configured for UEs performing NR sidelink communication on multiple carrier frequencies. | +| sl-SyncTxDisabled
Indicates that the carrier, even though equipped with synchronisation resources, cannot be used as a synchronisation carrier frequency to transmit S-SSB. | +| sl-SyncPriority
This field indicates synchronization priority order, as specified in clause 5.8.6. All values in sl-SyncPriority are same across all carrier frequencies configured for UEs performing NR sidelink communication on multiple carrier frequencies. | +| sl-SyncConfigList
This field indicates the configuration by which the UE is allowed to receive and transmit synchronisation information for NR sidelink communication. Network configures sl-SyncConfig including txParameters when configuring UEs to transmit synchronisation information. If this field is configured in SL-PreconfigurationNR-r16 , only one entry is configured in sl-SyncConfigList . | +| ue-toUE-COT-SharingED-Threshold
Indicates the energy detection threshold that is to be used by a UE to initiate a channel occupancy to be shared to other UE(s), and another UE that shares the initiated channel occupancy shall use this configured parameter for accessing the channel(s) as specified in TS 37.213 [48], clause 4.5.5 for sidelink channel access. Unit in dBm. Value -85 corresponds to -85 dBm, value -84 corresponds to -84 dBm, and so on (i.e. in steps of 1dBm). | +| valueN
Indicate the NR SL transmission with a valueN *5kHz shift to the LTE raster (see TS 38.101-1 [15], clause 5.4E.2). | + +| Conditional Presence | Explanation | +|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| V2X-SL-Shared | This field is mandatory present if the carrier frequency configured for NR sidelink communication is shared by V2X sidelink communication. It is absent, Need R, otherwise. | + +#### – *SL-FreqSelectionConfig* + +The IE *SL-FreqSelectionConfig* specifies the configuration information for carrier selection for NR sidelink transmission using UE autonomous resource selection. + +#### *SL-FreqSelectionConfig* information element + +``` +-- ASN1START +-- TAG-SL-FREQSELECTIONCONFIG-START + +SL-FreqSelectionConfig-r18 ::= SEQUENCE { + sl-priorityList-r18 SEQUENCE (SIZE (1..8)) OF INTEGER (1..8), + sl-threshCBR-FreqReselection-r18 SL-CBR-r16 OPTIONAL, -- Need R + sl-threshCBR-FreqKeeping-r18 SL-CBR-r16 OPTIONAL -- Need R +} + +-- TAG-SL-FREQSELECTIONCONFIG-STOP +-- ASN1STOP +``` + +#### *SL-FreqSelectionConfig* field descriptions + +| | | +|--------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-priorityList | Indicates the list of sidelink logical channel priority which is associated with the configurations in sl-threshCBR-FreqReselection and in sl-threshCBR-FreqKeeping . | +| sl-threshCBR-FreqReselection | Indicates the CBR threshold based on which UE determines whether the carrier frequency can be (re)selected for the transmission of NR sidelink. See TS 38.321 [3]. | +| sl-threshCBR-FreqKeeping | Indicates the CBR threshold based on which UE determines whether the UE can keep using the carrier which was selected for the transmission of NR sidelink. See TS 38.321 [3]. | + +#### – *SL-IndirectPathAddChange* + +The IE *SL-IndirectPathAddChange* specifies the configuration information of SL indirect path for SL indirect path addition/change in MP. + +#### *SL-IndirectPathAddChange* information element + +``` +-- ASN1START +-- TAG-SL-INDIRECTPATHADDCHANGE-START + +SL-IndirectPathAddChange-r18 ::= SEQUENCE { + sl-IndirectPathRelayUE-Identity-r18 SL-SourceIdentity-r17, + sl-IndirectPathCellIdentity-r18 CellIdentity, +} +``` + +``` + +t421-r18 ENUMERATED {ms50, ms100, ms150, ms200, ms500, ms1000, ms2000, ms10000}, +... +} + +-- TAG-SL-INDIRECTPATHADDCHANGE-STOP +-- ASN1STOP + +``` + +#### SL-IndirectPathAddChange field descriptions + +##### sl-IndirectPathRelayUEIdentity + +Indicates the L2 source ID of the L2 U2N Relay UE of SL indirect path. + +##### sl-IndirectPathCellIdentity + +Identifies the serving cell of the indicated L2 U2N Relay UE. + +###### t421 + +Indicates the timer value of T421 to be used during indirect path addition or change. + +#### SL-InterUE-CoordinationConfig + +The IE *SL-InterUE-CoordinationConfig* is used to configure the sidelink inter-UE coordination (between a UE, UE-A, and a peer UE, UE-B) parameters. + +#### SL-InterUE-CoordinationConfig information element + +``` + +-- ASN1START +-- TAG-SL-INTERUE-COORDINATIONCONFIG-START + +SL-InterUE-CoordinationConfig-r17 ::= SEQUENCE { + sl-InterUE-CoordinationScheme1-r17 SL-InterUE-CoordinationScheme1-r17 OPTIONAL, -- Need M + sl-InterUE-CoordinationScheme2-r17 SL-InterUE-CoordinationScheme2-r17 OPTIONAL, -- Need M + ... +} + +SL-InterUE-CoordinationScheme1-r17 ::= SEQUENCE { + sl-IUC-Explicit-r17 ENUMERATED {enabled, disabled} OPTIONAL, -- Need M + sl-IUC-Condition-r17 ENUMERATED {enabled, disabled} OPTIONAL, -- Need M + sl-Condition1-A-2-r17 ENUMERATED {disabled} OPTIONAL, -- Need M + sl-ThresholdRSRP-Condition1-B-1-Option1List-r17 SEQUENCE (SIZE (1..8)) OF SL-ThresholdRSRP-Condition1-B-1-r17 OPTIONAL, -- Need M + sl-ThresholdRSRP-Condition1-B-1-Option2List-r17 SEQUENCE (SIZE (1..8)) OF SL-ThresholdRSRP-Condition1-B-1-r17 OPTIONAL, -- Need M + sl-ContainerCoordInfo-r17 ENUMERATED {enabled, disabled} OPTIONAL, -- Need M + sl-ContainerRequest-r17 ENUMERATED {enabled, disabled} OPTIONAL, -- Need M + sl-TriggerConditionCoordInfo-r17 INTEGER (0..1) OPTIONAL, -- Need M + sl-TriggerConditionRequest-r17 INTEGER (0..1) OPTIONAL, -- Need M + sl-PriorityCoordInfoExplicit-r17 INTEGER (1..8) OPTIONAL, -- Need M + sl-PriorityCoordInfoCondition-r17 INTEGER (1..8) OPTIONAL, -- Need M + sl-PriorityRequest-r17 INTEGER (1..8) OPTIONAL, -- Need M + sl-PriorityPreferredResourceSet-r17 INTEGER (1..8) OPTIONAL, -- Need M + sl-MaxSlotOffsetTRIV-r17 INTEGER (1..8000) OPTIONAL, -- Need M + sl-NumSubCH-PreferredResourceSet-r17 INTEGER (1..27) OPTIONAL, -- Need M +} + +``` + +``` + +sl-ReservedPeriodPreferredResourceSet-r17 INTEGER (1..16) OPTIONAL, -- Need M +sl-DetermineResourceType-r17 ENUMERATED {uea, ueb} OPTIONAL, -- Need M +... +} + +SL-InterUE-CoordinationScheme2-r17 ::= SEQUENCE { + sl-IUC-Scheme2-r17 ENUMERATED {enabled} OPTIONAL, -- Need R + sl-RB-SetPSFCH-r17 BIT STRING (SIZE (10..275)) OPTIONAL, -- Need M + sl-TypeUE-A-r17 ENUMERATED {enabled} OPTIONAL, -- Need R + sl-PSFCH-Occasion-r17 INTEGER (0..1) OPTIONAL, -- Need M + sl-SlotLevelResourceExclusion-r17 ENUMERATED {enabled} OPTIONAL, -- Need R + sl-OptionForCondition2-A-1-r17 INTEGER (0..1) OPTIONAL, -- Need M + sl-IndicationUE-B-r17 ENUMERATED {enabled, disabled} OPTIONAL, -- Need M + ... + [[ + sl-DeltaRSRP-Thresh-v1720 INTEGER (-30..30) OPTIONAL -- Need M + ]] +} + +SL-ThresholdRSRP-Condition1-B-1-r17 ::= SEQUENCE { + sl-Priority-r17 INTEGER (1..8), + sl-ThresholdRSRP-Condition1-B-1-r17 INTEGER (0..66) +} + +-- TAG-SL-INTERUE-COORDINATIONCONFIG-STOP +-- ASN1STOP + +``` + +| SL-InterUE-CoordinationScheme1 field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-Condition1-A-2
Indicates disabling the use of condition of excluding from preferred resource set resource(s) in slot(s) where UE-A, when it is intended receiver of UE-B, does not expect to perform SL reception from UE-B due to half duplex operation. | +| sl-ContainerCoordInfo
Indicates whether a SCI format 2-C can be used as the container of inter-UE coordination information transmission from UE-A to UE-B in Scheme 1 in addition to using MAC CE. | +| sl-ContainerRequest
Indicates whether a SCI format 2-C can be used as the container of an explicit request for inter-UE coordination information transmission from UE-B to UE-A in Scheme 1 in addition to using MAC CE. | +| sl-DetermineResourceType
Indicates how to determine the resource set type to be provided by inter-UE coordination information transmission. Value "uea" means the resource set type is determined by UE-A's implementation. Value "ueb" means the resource set type is determined by UE-B's request. | +| sl-IUC-Condition
Indicates whether inter-UE coordination information triggered by a condition is enabled or not other than explicit request reception. | +| sl-IUC-Explicit
Indicates whether inter-UE coordination information triggered by an explicit request is enabled or not. | +| sl-MaxSlotOffsetTRIV
Indicates the maximum value of logical slot offset with respect to a reference slot that is used for representing the first resource location of each TRIV to indicate the set of resources in Scheme 1 as specified in TS 38.214 [19]. | +| sl-NumSubCH-PreferredResourceSet
Indicates the number of sub-channels used for determining the preferred resource set in Scheme 1 when the inter-UE coordination information transmission is triggered by a condition other than explicit request reception. | +| sl-PriorityCoordInfoCondition
Parameter used to determine the priority values for the purpose defined in TS 38.213 [13] and TS 38.214 [19] including, the priority value for sensing and candidate resource (re-)selection for transmitting the TB carrying the IUC MAC CE and the priority value in the SCI Format 1-A corresponding to the TB carrying the IUC MAC CE, triggered by a condition other than explicit request reception in Scheme 1. The priority value of IUC MAC CE used in LCP procedure (see TS 38.321 [3]) is fixed as "1". | +| sl-PriorityCoordInfoExplicit
Parameter used to determine the priority values for the purpose defined in TS 38.213 [13] and TS 38.214 [19] including, the priority value for sensing and candidate resource (re-)selection for transmitting the TB carrying the IUC MAC CE and the priority value in the SCI Format 1-A corresponding to the TB carrying the IUC MAC CE, triggered by an explicit request in Scheme 1. The priority value of IUC MAC CE used in LCP procedure (see TS 38.321 [3]) is fixed as "1". | +| sl-PriorityPreferredResourceSet
Indicates the priority value used for determining the preferred resource set in Scheme 1 when the inter-UE coordination information transmission is triggered by a condition other than explicit request reception. | +| sl-PriorityRequest
Parameter used to determine the priority values for the purpose defined in TS 38.213 [13] and TS 38.214 [19] including, the priority value for sensing and candidate resource (re-)selection for transmitting the TB carrying the IUC request MAC CE and the priority value in the SCI Format 1-A corresponding to the TB carrying the IUC request MAC CE, in an explicit request for inter-UE coordination information in Scheme 1. The priority value of IUC request MAC CE used in LCP procedure (see TS 38.321 [3]) is fixed as "1". | +| sl-ReservedPeriodPreferredResourceSet
Indicates the resource reservation interval used for determining the preferred resource set in Scheme 1 when the inter-UE coordination information transmission is triggered by a condition, by means of an index to the corresponding entry of sl-ResourceReservePeriodList-r16 . | + +##### **sl-TriggerConditionCoordInfo** + +Indicates the additional alternative trigger condition of inter-UE coordination information triggered by a condition rather than request reception in Scheme-1 from UE-A to UE-B. Value 0 means inter-UE coordination information is triggered by UE-A's implementation. Value 1 means inter-UE coordination information can be triggered only when UE-A has data to be transmitted together with the inter-UE coordination information to UE-B. + +##### **sl-TriggerConditionRequest** + +Indicates the trigger condition of an explicit request from UE-B to UE-A. Value 0 means the explicit request is triggered by UE-B's implementation. Value 1 means the explicit request can be triggered only when UE-B has data or SL-PRS to be transmitted to UE-A. + +##### **sl-ThresholdRSRP-Condition1-B-1-Option1List** + +Indicates the RSRP threshold used to determine reserved resource(s) of other UE(s) whose RSRP measurement is larger than it as the set of resource(s) non-preferred for UE-B's transmission for Condition 1-B-1 of Scheme 1, as specified in TS 38.214 [19]. Value 0 corresponds to minus infinity dBm, value 1 corresponds to -128dBm, value 2 corresponds to -126dBm, value n corresponds to $(-128 + (n-1)*2)$ dBm and so on, value 66 corresponds to infinity dBm. + +##### **sl-ThresholdRSRP-Condition1-B-1-Option2List** + +Indicates the RSRP threshold used to determine reserved resource(s) of other UE(s) whose RSRP measurement is smaller than it as the set of resource(s) non-preferred for UE-B's transmission for Condition 1-B-1 of Scheme 1, as specified in TS 38.214 [19]. Value 0 corresponds to minus infinity dBm, value 1 corresponds to -128dBm, value 2 corresponds to -126dBm, value n corresponds to $(-128 + (n-1)*2)$ dBm and so on, value 66 corresponds to infinity dBm. + +#### **SL-InterUE-CoordinationScheme2 field descriptions** + +##### **sl-DeltaRSRP-Thresh** + +Indicates the RSRP threshold delta value corresponding to *deltaRSRPTHresh* specified in clause 16.3.0 of TS 38.213 [13] and used to determine reserved resource(s) of other UE(s). Value in dB. Only even values (step size 2) allowed. + +##### **sl-IndicationUE-B** + +Indicates whether to enable or disable the usage of 1 LSB of reserved bits of a SCI format 1-A to indicate of whether UE scheduling a conflict TB can be UE-B or not. + +##### **sl-IUC-Scheme2** + +Indicates whether inter-UE coordination Scheme 2 is enabled or not. + +##### **sl-OptionForCondition2-A-1** + +Indicates the RSRP threshold used to consider additional criteria for condition 2-A-1. Value 0 corresponds to using the RSRP threshold according to the priorities included in the SCI, UE uses thresholds *sl-Thres-RSRP-List*, in its resource pool configuration *sl-UE-SelectedConfigRP*, corresponding to *ThresPSSCH-RSRP-List* specified in clause 16.3.0 of TS 38.213 [13]. Value 1 corresponds to using a (pre)configured RSRP threshold delta value *sl-DeltaRSRP-Thresh*, corresponding to *deltaRSRPTHresh* specified in clause 16.3.0 of TS 38.213 [13]. + +##### **sl-PSFCH-Occasion** + +Indicates the reference slot from which a PSFCH occasion for inter-UE coordination information transmission is derived. Value 0 corresponds to the slot where UE-B's SCI is transmitted and value 1 corresponds to the slot where expected/potential resource conflict occurs on PSSCH resource indicated by UE-B's SCI. + +##### **sl-RB-SetPSFCH** + +Indicates the set of PRBs that are actually used for inter-UE coordination information transmission and reception in Scheme 2. The leftmost bit of the bitmap refers to the lowest RB index in the resource pool, and so on. + +##### **sl-SlotLevelResourceExclusion** + +Indicates that physical layer of UE-B reports resources in a slot including the next reserved resource indicated by the corresponding UE-B's SCI to higher layer. + +##### **sl-TypeUE-A** + +Indicates that a non-destination UE of a TB transmitted by UE-B can be UE-A which sends inter-UE coordination information to UE-B, when UE-A is a destination UE of another TB conflicting with the TB transmitted by UE-B. + +#### — *SL-LBT-FailureRecoveryConfig* + +The IE *SL-LBT-FailureRecoveryConfig-r18* is used to configure the parameters used for detection and cancellation of sidelink consistent LBT failures for operation with shared spectrum channel access, as specified in TS 38.321 [3]. + +#### *SL-LBT-FailureRecoveryConfig* information element + +``` +-- ASN1START +-- TAG-SL-LBT-FAILURERECOVERYCONFIG-START + +SL-LBT-FailureRecoveryConfig-r18 ::= SEQUENCE { + sl-lbt-FailureInstanceMaxCount-r18 ENUMERATED {n4, n8, n16, n32, n64, n128} OPTIONAL, -- Need M + sl-lbt-FailureDetectionTimer-r18 ENUMERATED {ms10, ms20, ms40, ms80, ms160, ms320} OPTIONAL, -- Need M + sl-lbt-RecoveryTimer-r18 ENUMERATED {ms10, ms20, ms40, ms80, ms160, ms320} OPTIONAL, -- Need M + ... +} + +-- TAG-SL-LBT-FAILURERECOVERYCONFIG-STOP +-- ASN1STOP +``` + +#### *SL-LBT-FailureRecoveryConfig* field descriptions + +| | | +|----------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-lbt-FailureDetectionTimer | Timer for consistent sidelink LBT failure detection (see TS 38.321 [3]). Value ms10 corresponds to 10 ms, value ms20 corresponds to 20 ms, and so on. | +| sl-lbt-FailureInstanceMaxCount | This field determines after how many LBT failure indications received from the physical layer the UE triggers sidelink LBT failure recovery (see TS 38.321 [3]). Value n4 corresponds to 4, value n8 corresponds to 8, and so on. | +| sl-lbt-RecoveryTimer | Timer for consistent sidelink LBT failure cancellation (see TS 38.321 [3]). Value ms10 corresponds to 10 ms, value ms20 corresponds to 20 ms, and so on. | + +#### — *SL-LogicalChannelConfig* + +The IE *SL-LogicalChannelConfig* is used to configure the sidelink logical channel parameters. + +#### *SL-LogicalChannelConfig* information element + +``` +-- ASN1START +-- TAG-SL-LOGICALCHANNELCONFIG-START + +SL-LogicalChannelConfig-r16 ::= SEQUENCE { + sl-Priority-r16 INTEGER (1..8), + sl-PrioritisedBitRate-r16 ENUMERATED {kBps0, kBps8, kBps16, kBps32, kBps64, kBps128, kBps256, kBps512, + kBps1024, kBps2048, kBps4096, kBps8192, kBps16384, kBps32768, kBps65536, infinity}, + sl-BucketSizeDuration-r16 ENUMERATED {ms5, ms10, ms20, ms50, ms100, ms150, ms300, ms500, ms1000, + spare7, spare6, spare5, spare4, spare3, spare2, spare1}, + sl-ConfiguredGrantType1Allowed-r16 ENUMERATED {true} OPTIONAL, -- Need R +} +``` + +``` + + sl-HARQ-FeedbackEnabled-r16 ENUMERATED {enabled, disabled} OPTIONAL, -- Need R + sl-AllowedCG-List-r16 SEQUENCE (SIZE (0.. maxNrofCG-SL-1-r16)) OF SL-ConfigIndexCG-r16 + OPTIONAL, -- Need R + sl-AllowedSCS-List-r16 SEQUENCE (SIZE (1..maxSCSs)) OF SubcarrierSpacing OPTIONAL, -- Need R + sl-MaxPUSCH-Duration-r16 ENUMERATED {ms0p02, ms0p04, ms0p0625, ms0p125, ms0p25, ms0p5, spare2, spare1} + OPTIONAL, -- Need R + sl-LogicalChannelGroup-r16 INTEGER (0..maxLCG-ID) OPTIONAL, -- Need R + sl-SchedulingRequestId-r16 SchedulingRequestId OPTIONAL, -- Need R + sl-LogicalChannelSR-DelayTimerApplied-r16 BOOLEAN OPTIONAL, -- Need R + ..., + [[ + sl-ChannelAccessPriority-r18 INTEGER (1..4) OPTIONAL, -- Need R + sl-AllowedCarriers-r18 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF INTEGER (1..maxNrofFreqSL-r16) OPTIONAL -- Cond CONNECTED + ]] +} +-- TAG-SL-LOGICALCHANNELCONFIG-STOP +-- ASN1STOP + +``` + +| SL-LogicalChannelConfig field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-AllowedCarriers
If present, SL MAC SDUs from this logical channel can only be mapped to the sidelink carriers indicated in this list. Otherwise, SL MAC SDUs from this logical channel can be mapped to any configured sidelink carriers. The value 1 corresponds to the frequency of first entry in sl-FreqInfoList broadcast in SIB12 , the value 2 corresponds to the frequency of first entry in sl-FreqInfoListSizeExt broadcast in SIB12 , the value 3 corresponds to the frequency of second entry in sl-FreqInfoListSizeExt broadcast in SIB12 and so on. | +| sl-AllowedCG-List
This restriction applies only when the SL grant is a configured grant. If present, SL MAC SDUs from this logical channel can only be mapped to the indicated configured grant configuration. If the size of the sequence is zero, then SL MAC SDUs from this logical channel cannot be mapped to any configured grant configurations. If the field is not present, SL MAC SDUs from this logical channel can be mapped to any configured grant configurations. If the field sl-ConfiguredGrantType1Allowed is present, only those sidelink configured grant type 1 configurations indicated in this sequence are allowed for use by this sidelink logical channel; otherwise, this sequence shall not include any sidelink configured grant type 1 configuration. Corresponds to "sl-AllowedCG-List" as specified in TS 38.321 [3]. | +| sl-AllowedSCS-List
If present, indicate the numerology of UL-SCH resources that this sidelink logical channel is mapped to, when checking the SR trigger condition. Corresponds to 'sl-AllowedSCS-List' in TS 38.321 [3]. | +| sl-BucketSizeDuration
Value in ms. ms5 corresponds to 5 ms, value ms10 corresponds to 10 ms, and so on. | +| sl-ChannelAccessPriority
Indicates the Channel Access Priority Class (CAPC), as specified in TS 38.300 [2], to be used on sidelink transmissions for operation with shared spectrum channel access in FR1. The network configures this field only for DRBs. | +| sl-ConfiguredGrantType1Allowed
If present and set to true, or if the capability lcp-RestrictionSidelink as specified in TS 38.306 [26] is not indicated, SL MAC SDUs from this sidelink logical channel can be transmitted on a sidelink configured grant type 1. Otherwise, SL MAC SDUs from this logical channel cannot be transmitted on a sidelink configured grant type 1. Corresponds to 'sl-configuredGrantType1Allowed' in TS 38.321 [3]. | +| sl-HARQ-FeedbackEnabled
Network always includes this field. It indicates the HARQ feedback enabled/disabled restriction in LCP for this sidelink logical channel. If set to enabled , the sidelink logical channel will be multiplexed only with a logical channel which enabling the HARQ feedback. If set to disabled , the sidelink logical channel cannot be multiplexed with a logical channel which enabling the HARQ feedback. Corresponds to 'sl-HARQ-FeedbackEnabled' in TS 38.321 [3]. If this field of at least one sidelink logical channel for the UE is set to enabled, sl-PSFCH-Config should be mandatory present in configuration SL-ResourcePool of at least one of the sidelink resource pools. | +| sl-LogicalChannelGroup
ID of the sidelink logical channel group, as specified in TS 38.321 [3], which the sidelink logical channel belongs to. | +| sl-LogicalChannelSR-DelayTimerApplied
Indicates whether to apply the delay timer for SR transmission for this sidelink logical channel. Set to false if logicalChannelSR-DelayTimer is not included in sl-BSR-Config . | +| sl-MaxPUSCH-Duration
If present, indicate the maximum PUSCH duration of UL-SCH resources that this sidelink logical channel is mapped to, when checking the SR trigger condition. Corresponds to "sl-MaxPUSCH-Duration" in TS 38.321 [3]. | +| sl-PrioritisedBitRate
Value in kiloBytes/s. Value kBps0 corresponds to 0 kiloBytes/s, value kBps8 corresponds to 8 kiloBytes/s, value kBps16 corresponds to 16 kiloBytes/s, and so on. | +| sl-Priority
Sidelink logical channel priority, as specified in TS 38.321 [3]. | +| sl-SchedulingRequestId
If present, it indicates the scheduling request configuration applicable for this sidelink logical channel, as specified in TS 38.321 [3]. | + +| Conditional Presence | Explanation | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CONNECTED | This field is optionally present, Need M, in an RRCReconfiguration message, for a SL DRB with additional RLC bearer being configured. The field is absent otherwise. | + +#### — *SL-L2RelayUE-Config* + +The IE *SL-L2RelayUE-Config* is used to configure L2 U2N relay operation related configurations used by L2 U2N Relay UE, or L2 U2U relay operation related configurations used by L2 U2U Relay UE. + +#### *SL-L2RelayUE-Config* information element + +``` +-- ASN1START +-- TAG-SL-L2RELAYUE-CONFIG-START + +SL-L2RelayUE-Config-r17 ::= SEQUENCE { + sl-RemoteUE-ToAddModList-r17 SEQUENCE (SIZE (1..maxNrofRemoteUE-r17)) OF SL-RemoteUE-ToAddMod-r17 OPTIONAL, -- Need N + sl-RemoteUE-ToReleaseList-r17 SEQUENCE (SIZE (1..maxNrofRemoteUE-r17)) OF SL-DestinationIdentity-r16 OPTIONAL, -- Need N + ..., + [[ + sl-U2U-RemoteUE-ToAddModList-r18 SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-U2U-RemoteUE-ToAddMod-r18 OPTIONAL, -- Need N + sl-U2U-RemoteUE-ToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-DestinationIdentity-r16 OPTIONAL -- Need N + ]] +} + +SL-RemoteUE-ToAddMod-r17 ::= SEQUENCE { + sl-L2IdentityRemote-r17 SL-DestinationIdentity-r16, + sl-SRAP-ConfigRelay-r17 SL-SRAP-Config-r17 + ... + OPTIONAL, -- Need M +} + +SL-U2U-RemoteUE-ToAddMod-r18 ::= SEQUENCE { + sl-L2IdentityRemote-r18 SL-DestinationIdentity-r16, + sl-SourceRemoteUE-ToAddModList-r18 SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-SourceRemoteUE-ToAddMod-r18 OPTIONAL, -- Need N + sl-SourceRemoteUE-ToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-SourceIdentity-r17 OPTIONAL, -- Need N + ... +} + +SL-SourceRemoteUE-ToAddMod-r18 ::= SEQUENCE { + sl-SourceUE-Identity-r18 SL-SourceIdentity-r17, + sl-SRAP-ConfigU2U-r18 SL-SRAP-ConfigU2U-r18, + ... +} + +-- TAG-SL-L2RELAYUE-CONFIG-STOP +-- ASN1STOP +``` + +| SL-L2RelayUE-Config field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-RemoteUE-ToAddModList
List of L2 U2N Remote UEs to be added and modified to the L2 U2N Relay UE. | +| sl-RemoteUE-ToReleaseList
List of L2 U2N Remote UEs to be released by the L2 U2N Relay UE. | +| sl-U2U-RemoteUE-ToAddModList
List of L2 U2U Remote UEs for which the related configuration is to be added and modified to the L2 U2U Relay UE. | +| sl-U2U-RemoteUE-ToReleaseList
List of L2 U2U Remote UEs for which the related configuration is to be released by the L2 U2U Relay UE. | +| sl-U2U-SourceRemoteUE-ToAddModList
List of Source L2 U2U Remote UEs for which the related configuration is to be added and modified. | +| sl-U2U-SourceRemoteUE-ToReleaseList
List of Source L2 U2U Remote UEs for which the related configuration is to be released. | + +#### SL-L2RemoteUE-Config + +The IE *SL-L2RemoteUE-Config* is used to configure L2 U2N relay operation related configurations used by L2 U2N Remote UE, or L2 U2U relay operation related configurations used by L2 U2U Remote UE. + +#### SL-L2RemoteUE-Config information element + +``` +-- ASN1START +-- TAG-SL-L2REMOTEUE-CONFIG-START + +SL-L2RemoteUE-Config-r17 ::= SEQUENCE { + sl-SRAP-ConfigRemote-r17 SL-SRAP-Config-r17 OPTIONAL, --Need M + sl-UEIdentityRemote-r17 RNTI-Value OPTIONAL, -- Cond FirstRRReconfig + ... + [[ + sl-U2U-RelayUE-ToAddModList-r18 SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-U2U-RelayUE-ToAddMod-r18 OPTIONAL, -- Need N + sl-U2U-RelayUE-ToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-DestinationIdentity-r16 OPTIONAL -- Need N + ]] +} + +SL-U2U-RelayUE-ToAddMod-r18 ::= SEQUENCE { + sl-L2IdentityRelay-r18 SL-DestinationIdentity-r16, + sl-PeerRemoteUE-ToAddModList-r18 SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-PeerRemoteUE-ToAddMod-r18 OPTIONAL, -- Need N + sl-PeerRemoteUE-ToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-DestinationIdentity-r16 OPTIONAL, -- Need N + ... +} + +SL-PeerRemoteUE-ToAddMod-r18 ::= SEQUENCE { + sl-TargetUE-Identity-r18 SL-DestinationIdentity-r16, + sl-SRAP-ConfigU2U-r18 SL-SRAP-ConfigU2U-r18, + ... +} +``` + +``` +-- TAG-SL-L2REMOTEUE-CONFIG-STOP +-- ASN1STOP +``` + +| SL-L2RemoteUE-Config field descriptions | | +|------------------------------------------------|-------------------------------------------------------------------------------------------------------------------| +| sl-SRAP-ConfigRemote | Indicates SRAP configuration used for L2 U2N Remote UE. | +| sl-UEIdentityRemote | Indicates the C-RNTI to the L2 U2N Remote UE. | +| sl-U2U-RelayUE-ToAddModList | List of L2 U2U Relay UEs for which the related configuration is to be added and modified to the L2 U2U Remote UE. | +| sl-U2U-RelayUE-ToReleaseList | List of L2 U2U Relay UEs for which the related configuration is to be released by the L2 U2U Remote UE. | +| sl-U2U-PeerRemoteUE-ToAddModList | List of Peer L2 U2U Remote UEs for which the related configuration is to be added and modified. | +| sl-U2U-PeerRemoteUE-ToReleaseList | List of Peer L2 U2U Remote UEs for which the related configuration is to be released. | + +| Conditional Presence | Explanation | +|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| FirstRRReconfig | This field is mandatory present in the first RRReconfiguration for L2 U2N Remote UE when PCell is on indirect path, i.e. MP configuration is not present. Otherwise the field is absent. | + +#### — *SL-MeasConfigCommon* + +The IE *SL-MeasConfigCommon* is used to set the cell specific SL RSRP measurement configurations for unicast destinations. + +#### ***SL-MeasConfigCommon* information element** + +``` +-- ASN1START +-- TAG-SL-MEASCONFIGCOMMON-START + +SL-MeasConfigCommon-r16 ::= SEQUENCE { + sl-MeasObjectListCommon-r16 SL-MeasObjectList-r16 OPTIONAL, -- Need R + sl-ReportConfigListCommon-r16 SL-ReportConfigList-r16 OPTIONAL, -- Need R + sl-MeasIdListCommon-r16 SL-MeasIdList-r16 OPTIONAL, -- Need R + sl-QuantityConfigCommon-r16 SL-QuantityConfig-r16 OPTIONAL, -- Need R + ... +} + +-- TAG-SL-MEASCONFIGCOMMON-STOP +-- ASN1STOP +``` + +| SL-MeasConfigCommon field descriptions | +|---------------------------------------------------------------------------------------------------------| +| sl-MeasIdListCommon
List of sidelink measurement identities | +| sl-MeasObjectListCommon
List of sidelink measurement objects. | +| sl-QuantityConfigCommon
Indicates the layer 3 filtering coefficient for sidelink measurement. | +| sl-ReportConfigListCommon
List of sidelink measurement reporting configurations. | + +#### SL-MeasConfigInfo + +The IE *SL-MeasConfigInfo* is used to set RSRP measurement configurations for unicast destinations. + +#### SL-MeasConfigInfo information element + +``` +-- ASN1START +-- TAG-SL-MEASCONFIGINFO-START + +SL-MeasConfigInfo-r16 ::= SEQUENCE { + sl-DestinationIndex-r16 SL-DestinationIndex-r16, + sl-MeasConfig-r16 SL-MeasConfig-r16, + ... +} + +SL-MeasConfig-r16 ::= SEQUENCE { + sl-MeasObjectToRemoveList-r16 SL-MeasObjectToRemoveList-r16 OPTIONAL, -- Need N + sl-MeasObjectToAddModList-r16 SL-MeasObjectList-r16 OPTIONAL, -- Need N + sl-ReportConfigToRemoveList-r16 SL-ReportConfigToRemoveList-r16 OPTIONAL, -- Need N + sl-ReportConfigToAddModList-r16 SL-ReportConfigList-r16 OPTIONAL, -- Need N + sl-MeasIdToRemoveList-r16 SL-MeasIdToRemoveList-r16 OPTIONAL, -- Need N + sl-MeasIdToAddModList-r16 SL-MeasIdList-r16 OPTIONAL, -- Need N + sl-QuantityConfig-r16 SL-QuantityConfig-r16 OPTIONAL, -- Need M + ... +} + +SL-MeasObjectToRemoveList-r16 ::= SEQUENCE (SIZE (1..maxNrofSL-ObjectId-r16)) OF SL-MeasObjectId-r16 +SL-ReportConfigToRemoveList-r16 ::= SEQUENCE (SIZE (1..maxNrofSL-ReportConfigId-r16)) OF SL-ReportConfigId-r16 +SL-MeasIdToRemoveList-r16 ::= SEQUENCE (SIZE (1..maxNrofSL-MeasId-r16)) OF SL-MeasId-r16 + +-- TAG-SL-MEASCONFIGINFO-STOP +-- ASN1STOP +``` + +| SL-MeasConfigInfo field descriptions | +|-------------------------------------------------------------------------------------------------------------------| +| sl-MeasIdToAddModList
List of sidelink measurement identities to add and/or modify. | +| sl-MeasIdToRemoveList
List of sidelink measurement identities to remove. | +| sl-MeasObjectToAddModList
List of sidelink measurement objects to add and/or modify. | +| sl-MeasObjectToRemoveList
List of sidelink measurement objects to remove. | +| sl-QuantityConfig
Indicates the layer 3 filtering coefficient for sidelink measurement. | +| sl-ReportConfigToAddModList
List of sidelink measurement reporting configurations to add and/or modify. | +| sl-ReportConfigToRemoveList
List of sidelink measurement reporting configurations to remove. | + +#### — SL-MeasIdList + +The IE *SL-MeasIdList* concerns a list of SL measurement identities to add or modify for a destination, with for each entry the *sl-MeasId*, the associated *sl-MeasObjectId* and the associated *sl-ReportConfigId*. + +#### SL-MeasIdList information element + +``` +-- ASN1START +-- TAG-SL-MEASIDLIST-START + +SL-MeasIdList-r16 ::= SEQUENCE (SIZE (1..maxNrofSL-MeasId-r16)) OF SL-MeasIdInfo-r16 + +SL-MeasIdInfo-r16 ::= SEQUENCE { + sl-MeasId-r16 SL-MeasId-r16, + sl-MeasObjectId-r16 SL-MeasObjectId-r16, + sl-ReportConfigId-r16 SL-ReportConfigId-r16, + ... +} + +SL-MeasId-r16 ::= INTEGER (1..maxNrofSL-MeasId-r16) + +-- TAG-SL-MEASIDLIST-STOP +-- ASN1STOP +``` + +#### — SL-MeasObjectList + +The IE *SL-MeasObjectList* concerns a list of SL measurement objects to add or modify for a destination. + +#### **SL-MeasObjectList information element** + +``` + +-- ASN1START +-- TAG-SL-MEASOBJECTLIST-START + +SL-MeasObjectList-r16 ::= SEQUENCE (SIZE (1..maxNrofSL-ObjectId-r16)) OF SL-MeasObjectInfo-r16 + +SL-MeasObjectInfo-r16 ::= SEQUENCE { + sl-MeasObjectId-r16 SL-MeasObjectId-r16, + sl-MeasObject-r16 SL-MeasObject-r16, + ... +} + +SL-MeasObjectId-r16 ::= INTEGER (1..maxNrofSL-ObjectId-r16) + +SL-MeasObject-r16 ::= SEQUENCE { + frequencyInfoSL-r16 ARFCN-ValueNR, + ... +} + +-- TAG-SL-MEASOBJECTLIST-STOP +-- ASN1STOP + +``` + +#### **SL-MeasObjectList field descriptions** + +##### ***frequencyInfoSL*** + +It indicates the lowest usable subcarrier on the carrier where SL RSRP is measured, determined according to *sl-AbsoluteFrequencyPointA* in IE *SL-FreqConfig/SL-FreqConfigCommon* and *offsetToCarrier* in IE *SCS-SpecificCarrier* configured for *sl-SCS-SpecificCarrierList* in IE *SL-FreqConfig/SL-FreqConfigCommon*. See TS 38.211 [16], clause 8.2.5. + +##### ***sl-MeasObjectId*** + +It is used to identify a sidelink measurement object configuration. + +##### ***sl-MeasObject*** + +It specifies information applicable for sidelink DMRS measurement. + +#### **— *SL-PagingIdentityRemoteUE*** + +The IE *SL-PagingIdentityRemoteUE* includes the Remote UE's paging UE ID. + +#### ***SL-PagingIdentityRemoteUE* information element** + +``` + +-- ASN1START +-- TAG-SL-PAGINGIDENTITYREMOTEUE-START + +SL-PagingIdentityRemoteUE-r17 ::= SEQUENCE { + ng-5G-S-TMSI-r17 NG-5G-S-TMSI, + fullI-RNTI-r17 I-RNTI-Value OPTIONAL -- Need R +} + +``` + +``` + +} +-- TAG-SL-PAGINGIDENTITYREMOTEUE-STOP +-- ASN1STOP + +``` + +#### SL-PBPS-CPS-Config + +The IE *SL-PBPS-CPS-Config* specifies the operation information for a resource pool which can be (pre-)configured to enable full sensing only, partial sensing only, random resource selection only, or any combination(s) thereof. + +#### SL-PBPS-CPS-Config information element + +``` + +-- ASN1START +-- TAG-SL-PBPS-CPS-CONFIG-START + +SL-PBPS-CPS-Config-r17 ::= + SEQUENCE { + sl-AllowedResourceSelectionConfig-r17 ENUMERATED {c1, c2, c3, c4, c5, c6, c7} OPTIONAL, -- Need M + sl-MinNumCandidateSlotsPeriodic-r17 INTEGER (1..32) OPTIONAL, -- Need M + sl-PBPS-OccasionReservePeriodList-r17 SEQUENCE (SIZE (1..16)) OF INTEGER (1..16) OPTIONAL, -- Need M + sl-Additional-PBPS-Occasion-r17 ENUMERATED { monitored } OPTIONAL, -- Need M + sl-CPS-WindowPeriodic-r17 INTEGER (5..30) OPTIONAL, -- Need M + sl-MinNumCandidateSlotsAperiodic-r17 INTEGER (1..32) OPTIONAL, -- Need M + sl-MinNumRssiMeasurementSlots-r17 INTEGER (1..800) OPTIONAL, -- Need M + sl-DefaultCBR-RandomSelection-r17 INTEGER (0..100) OPTIONAL, -- Need M + sl-DefaultCBR-PartialSensing-r17 INTEGER (0..100) OPTIONAL, -- Need M + sl-CPS-WindowAperiodic-r17 INTEGER (0..30) OPTIONAL, -- Need M + sl-PartialSensingInactiveTime-r17 ENUMERATED { enabled, disabled } OPTIONAL, -- Need M + ... + } + +-- TAG-SL-PBPS-CPS-CONFIG-STOP +-- ASN1STOP + +``` + +| SL-PBPS-CPS-Config field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-Additional-PBPS-Occasion
Indicates that UE additionally monitors periodic sensing occasions that correspond to a set of values. (see TS 38.214 [19], clause 8.1.4). | +| sl-AllowedResourceSelectionConfig
Indicates the allowed resource selection mechanism(s), i.e. full sensing only, partial sensing only, random resource selection only, or any combination(s) thereof. (see TS 38.214 [19], clause 8.1.4). Only c1, c4, c5 or c7 can be configured for a Rel-16 resource pool. If this field is not configured for a resource pool included in sl-TxPoolSelectedNormal , only full sensing is allowed in the corresponding resource pool.
c1: only full sensing allowed
c2: only partial sensing allowed
c3: only random selection allowed
c4: full sensing+random selection allowed
c5: full sensing+ partial sensing allowed
c6: partial sensing + random selection allowed
c7: full sensing+ partial sensing + random selection allowed. | +| sl-CPS-WindowAperiodic
Parameter that indicates the minimum size of contiguous partial sensing window in logical slot units for a resource (re)selection procedure and re-evaluation/pre-emption checking triggered by aperiodic transmission. (see TS 38.214 [19], clause 8.1.4). If not configured, the size of contiguous partial sensing window in logical slot units is 31. | +| sl-CPS-WindowPeriodic
Indicates the size of contiguous partial sensing window in logical slot units when UE performs periodic-based and contiguous partial sensing for a resource (re)selection procedure triggered by periodic transmission. If not configured, the size of contiguous partial sensing window in logical slot units is 31. | +| sl-DefaultCBR-PartialSensing
Indicates default value of SL CBR measurement for a UE that is configured to perform partial sensing by its higher layer (including when SL DRX is configured) if the number of SL RSSI measurement slots over CBR measurement window is below sl-MinNumRssiMeasurementSlots , (see TS 38.214 [19], clause 8.1.6). Value 0 corresponds to 0, value 1 to 0.01, value 2 to 0.02, and so on. | +| sl-DefaultCBR-RandomSelection
Indicates default value of CBR measurement for a UE that performs random resource selection if no SL CBR measurement result over SL CBR measurement window, (see TS 38.214 [19], clause 8.1.6). Value 0 corresponds to 0, value 1 to 0.01, value 2 to 0.02, and so on. | +| sl-MinNumCandidateSlotsAperiodic
Indicates the minimum number of Y' slots that are included in the possible candidate resources corresponding to periodic-based partial sensing and/or contiguous partial sensing for resource (re)selection triggered by aperiodic transmission. (see TS 38.214 [19], clause 8.1.4). | +| sl-MinNumCandidateSlotsPeriodic
Indicates the minimum number of Y slots that are included in the possible candidate resources corresponding to periodic-based partial sensing for resource (re)selection triggered by periodic transmission. (see TS 38.214 [19], clause 8.1.4). | +| sl-MinNumRssiMeasurementSlots
Indicates a threshold for a minimum number of SL RSSI measurement slots over CBR measurement window for which the SL RSSI is measured for a UE that is configured to perform partial sensing by its higher layer (including when SL DRX is configured). (see TS 38.214 [19], clause 8.1.6). | +| sl-PartialSensingInactiveTime
Indicates whether or not UE is required to perform SL reception of PSCCH and RSRP measurement for partial sensing on slots in SL DRX inactive time when partial sensing is configured by its higher layer. (see TS 38.214 [19], clause 8.1.4). | +| sl-PBPS-OccasionReservePeriodList
Indicates the subset of periodicity values from sl-ResourceReservePeriodList used to determine periodic sensing occasions in periodic-based partial sensing, by means of an index to the corresponding entry in sl-ResourceReservePeriodList-r16 . If not configured, all periodicity values from sl-ResourceReservePeriodList are used to determine periodic sensing occasions in periodic-based partial sensing (see TS 38.214 [19], clause 8.1.4). | + +#### SL-PDCP-Config + +The IE *SL-PDCP-Config* is used to set the configurable PDCP parameters for a sidelink radio bearer. + +#### SL-PDCP-Config information element + +``` +-- ASN1START +-- TAG-SL-PDCP-CONFIG-START + +SL-PDCP-Config-r16 ::= SEQUENCE { + sl-DiscardTimer-r16 ENUMERATED {ms3, ms10, ms20, ms25, ms30, ms40, ms50, ms60, ms75, ms100, ms150, ms200, + ms250, ms300, ms500, ms750, ms1500, infinity} OPTIONAL, -- Cond Setup + sl-PDCP-SN-Size-r16 ENUMERATED {len12bits, len18bits} OPTIONAL, -- Cond Setup2 + sl-OutOfOrderDelivery ENUMERATED { true } OPTIONAL, -- Need R + ... +} + +-- TAG-SL-PDCP-CONFIG-STOP +-- ASN1STOP +``` + +#### SL-PDCP-Config field descriptions + +| | | +|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-DiscardTimer | Value in ms of discardTimer specified in TS 38.323 [5]. Value ms50 corresponds to 50 ms, value ms100 corresponds to 100 ms and so on. | +| sl-OutOfOrderDelivery | Indicates whether or not outOfOrderDelivery specified in TS 38.323 [5] is configured. This field should be either always present or always absent, after the radio bearer is established. | +| sl-PDCP-SN-Size | PDCP sequence number size for unicast NR sidelink communication, 12 or 18 bits, as specified in TS 38.323 [5]. For groupcast and broadcast NR sidelink communication, only 12 bits is applicable, as specified in 9.1.1.5. | + +| Conditional Presence | Explanation | +|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Setup | The field is mandatory present in case of sidelink DRB setup via dedicated signaling and in case of sidelink DRB configuration via system information and pre-configuration; otherwise the field is optionally present, need M. | +| Setup2 | The field is mandatory present in case of sidelink DRB setup via dedicated signaling and in case of sidelink DRB configuration via system information and pre-configuration for RLC-AM and RLC-UM for unicast NR sidelink communication; otherwise the field is not present, Need M. | + +#### SL-PRS-ResourcePool + +The IE *SL-PRS-ResourcePool* specifies the configuration information for NR sidelink PRS dedicated resource pool. + +#### **SL-PRS-ResourcePool information element** + +``` + +-- ASN1START +-- TAG-SL-PRS-RESOURCEPOOL-START + +SL-PRS-ResourcePool-r18 ::= + SEQUENCE { + sl-PRS-PSCCH-Config-r18 SetupRelease { SL-PSCCH-ConfigDedicatedSL-PRS-RP-r18} OPTIONAL, -- Need M + sl-StartRB-SubchannelDedicatedSL-PRS-RP-r18 INTEGER (0..265) OPTIONAL, -- Need M + sl-RB-Number-r18 INTEGER (10..275) OPTIONAL, -- Need M + sl-TimeResource-r18 BIT STRING (SIZE (10..160)) OPTIONAL, -- Need M + sl-PosAllowedResourceSelectionConfig-r18 ENUMERATED {c1, c2, c3} OPTIONAL, -- Need M + sl-PRS-ResourceReservePeriodList-r18 SEQUENCE (SIZE (1..16)) OF SL-ReservationPeriodAllowedDedicatedSL-PRS-RP-r18 + sl-PRS-ResourcesDedicatedSL-PRS-RP-r18 SEQUENCE (SIZE (1..12)) OF SL-PRS-ResourceDedicatedSL-PRS-RP-r18 OPTIONAL, -- Need M + sl-PRS-PowerControl-r18 SL-PRS-PowerControl-r18 OPTIONAL, -- Need M + sl-SensingWindowDedicatedSL-PRS-RP-r18 ENUMERATED {ms100, ms1100} OPTIONAL, -- Need M + sl-TxPercentageDedicatedSL-PRS-RP-List-r18 SEQUENCE (SIZE (8)) OF SL-TxPercentageDedicatedSL-PRS-RP-Config-r18 OPTIONAL, -- Need M + sl-SCI-basedSL-PRS-TxTriggerSCI1-B-r18 BOOLEAN OPTIONAL, -- Need M + sl-NumSubchannelDedicatedSL-PRS-RP-r18 INTEGER (1..27) OPTIONAL, -- Need M + sl-SubchannelSizeDedicatedSL-PRS-RP-r18 ENUMERATED {n10, n12, n15, n20, n25, n50, n75, n100} OPTIONAL, -- Need M + sl-MaxNumPerReserveDedicatedSL-PRS-RP-r18 ENUMERATED {n2, n3} OPTIONAL, -- Need M + sl-NumReservedBitsSCI1B-DedicatedSL-PRS-RP-r18 INTEGER (0..20) OPTIONAL, -- Need M + sl-SRC-ID-LenDedicatedSL-PRS-RP-r18 ENUMERATED {n12, n24} OPTIONAL, -- Need M + sl-CBR-PriorityTxConfigDedicatedSL-PRS-RP-List-r18 SEQUENCE (SIZE (1..8)) OF SL-PriorityTxConfigIndexDedicatedSL-PRS-RP-r18 + sl-TimeWindowSizeCBR-DedicatedSL-PRS-RP-r18 ENUMERATED {ms100, slot100} OPTIONAL, -- Need M + sl-TimeWindowSizeCR-DedicatedSL-PRS-RP-r18 ENUMERATED {ms1000, slot1000} OPTIONAL, -- Need M + sl-CBR-CommonTxDedicatedSL-PRS-RP-List-r18 SL-CBR-CommonTxDedicatedSL-PRS-RP-List-r18 OPTIONAL, -- Need M + sl-PriorityThreshold-UL-URLLC-r18 INTEGER (1..9) OPTIONAL, -- Need M + sl-PriorityThreshold-r18 INTEGER (1..9) OPTIONAL, -- Need M + } + +SL-PSCCH-ConfigDedicatedSL-PRS-RP-r18 ::= + SEQUENCE { + timeResourcePSCCH-DedicatedSL-PRS-RP-r18 ENUMERATED {n2, n3} OPTIONAL, -- Need M + freqResourcePSCCH-DedicatedSL-PRS-RP-r18 ENUMERATED {n10,n12, n15, n20, n25} OPTIONAL, -- Need M + ... + } + +SL-ReservationPeriodAllowedDedicatedSL-PRS-RP-r18 ::= + CHOICE { + sl-ResourceReservePeriod1-r18 ENUMERATED {ms0, ms100, ms200, ms300, ms400, ms500, ms600, ms700, ms800, ms900, ms1000}, + sl-ResourceReservePeriod2-r18 INTEGER (1..99) + } + +SL-PRS-ResourceDedicatedSL-PRS-RP-r18 ::= + SEQUENCE { + sl-PRS-ResourceID-r18 INTEGER (0..11) OPTIONAL, -- Need M + sl-NumberOfSymbols-r18 INTEGER (1..9) OPTIONAL, -- Need M + sl-CombSize-r18 ENUMERATED{n2,n4,n6} OPTIONAL, -- Need M + sl-PRS-starting-symbol-r18 INTEGER (4..12) OPTIONAL, -- Need M + sl-PRS-comb-offset-r18 INTEGER(1..5) OPTIONAL, -- Need M + } + +``` + +``` + +SL-PRS-PowerControl-r18 ::= SEQUENCE { + dl-P0-SL-PRS-r18 INTEGER (-202..24) OPTIONAL, -- Need M + dl-Alpha-SL-PRS-r18 ENUMERATED {alpha0, alpha04, alpha05, alpha06, alpha07, alpha08, alpha09, alpha1} OPTIONAL, -- Need S + sl-P0-SL-PRS-r18 INTEGER (-202..24) OPTIONAL, -- Need S + sl-Alpha-SL-PRS-r18 ENUMERATED {alpha0, alpha04, alpha05, alpha06, alpha07, alpha08, alpha09, alpha1} OPTIONAL, -- Need S +} + +SL-TxPercentageDedicatedSL-PRS-RP-Config-r18 ::= SEQUENCE { + sl-TxPercentageDedicatedSL-PRS-RP-r18 INTEGER (1..8) OPTIONAL, -- Need M + sl-Priority-DedicatedSL-PRS-RP ENUMERATED {p20, p35, p50} OPTIONAL, -- Need M +} + +SL-PriorityTxConfigIndexDedicatedSL-PRS-RP-r18 ::= SEQUENCE { + sl-PriorityThresholdDedicatedSL-PRS-RP-r18 INTEGER (1..8) OPTIONAL, -- Need M + sl-DefaultTxConfigIndexDedicatedSL-PRS-RP-r18 INTEGER (0..maxCBR-LevelDedSL-PRS-1-r18) OPTIONAL, -- Need M + sl-CBR-ConfigIndexDedicatedSL-PRS-RP-r18 INTEGER (0..maxCBR-ConfigDedSL-PRS-1-r18) OPTIONAL, -- Need M + sl-PRS-TxConfigIndexList-r18 SEQUENCE (SIZE (1.. maxCBR-LevelDedSL-PRS-1-r18)) OF SL-PRS-TxConfigIndex-r18 + OPTIONAL, -- Need M +} + +SL-PRS-TxConfigIndex-r18 ::= INTEGER (0.. maxNrofSL-PRS-TxConfig-r18) + +-- TAG-SL-PRS-RESOURCEPOOL-STOP +-- ASN1STOP + +``` + +#### SL-PRS-ResourcePool field descriptions + +| | | +|-------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-RB-Number | Indicates the number of PRBs in the corresponding SL PRS dedicated resource pool, which consists of contiguous PRBs only. | +| sl-StartRB-Subchannel-DedicatedSL-PRS-RP | Indicates the lowest RB index of the SL PRS dedicated resource pool with respect to the lowest RB index of a SL BWP. | +| sl-TimeResource | This field indicates the bitmap of the SL PRS dedicated resource pool, which is defined by repeating the bitmap with a periodicity during a SFN or DFN cycle. | +| sl-PosAllowedResourceSelectionConfig | Indicates allowed resource allocation method configured per resource pool.
C1: only sensing allowed
C2: only random resource selection allowed
C3: sensing and random resource selection allowed | +| sl-PRS-ResourceReservePeriodList | Indicates set of possible resource reservation period in the unit of ms allowed in the resource pool. Up to 16 values can be configured per resource pool. The possible resource reservation period are periodicities for legacy SL communication and the ones defined for DL-PRS. | +| sl-PRS-ResourcesDedicatedSL-PRS-RP | Indicates SL PRS resources in a slot of dedicated SL PRS resource pool as defined in TS 38.211 [16]. | +| sl-SensingWindowDedicatedSL-PRS-RP | Indicates Parameter that indicates the start of the sensing window for SL PRS in a dedicated resource pool. | +| sl-TxPercentageDedicatedSL-PRS-RP-List | Indicates List of minimum Tx percentage (list per priority) | + +| | | +|--------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-SCI-basedSL-PRS-TxTriggerSCI1-B | Indicates presence of a bit-field in SCI format 1-B to trigger SL-PRS transmission by a receiving UE. | +| sl-NumSubchannelDedicatedSL-PRS-RP | Indicates the number of subchannels in the corresponding resource pool, which consists of contiguous PRBs only. | +| sl-SubchannelSizeDedicatedSL-PRS-RP | Indicates size of a subchannel for PSCCH in number of RBs. | +| sl-MaxNumPerReserveDedicatedSL-PRS-RP | Indicates the maximum number of SL PRS reservations that can be indicated by an SCI. | +| sl-NumReservedBitsSCI1B-DedicatedSL-PRS-RP | Indicates the number of reserved bits in SCI format 1-B. | +| sl-SRC-ID-LenDedicatedSL-PRS-RP | Indicates the number of bits used for the source ID in SCI format 1-B. | +| sl-CBR-PriorityTxConfigList-DedicatedSL-PRS-RP | Indicates the mapping between SL-PRS transmission parameter (such as transmission power, etc.) sets by using the indexes of the configurations in sl-CBR-SL-PRS-TxConfigList , CBR ranges by using the indexes to the entry of the CBR range configurations in sl-CBR-SL-PRS-RangeConfigList , and priority ranges. It also indicates the default SL-PRS transmission parameters to be used when CBR measurement results are not available. | +| sl-PriorityThresholdDedicatedSL-PRS-RP | Indicates the upper bound of priority range which is associated with the configurations in sl-CBR-ConfigIndex-Dedicated-SL-PRS-RP and in sl-PRS-Tx-ConfigIndex . The upper bounds of the priority ranges are configured in ascending order for consecutive entries of SL-PriorityTxConfigIndex-Dedicated-SL-PRS-RP in SL-PriorityTxConfigList-Dedicated-SL-PRS-RP . For the first entry of sl-PriorityThreshold-Dedicated-SL-PRS-RP , the lower bound of the priority range is 1. | +| sl-TimeWindowSizeCBR-DedicatedSL-PRS-RP | Indicates the time window size for CBR measurement in a dedicated SL-PRS resource pool. | +| sl-TimeWindowSizeCR-DedicatedSL-PRS-RP | Indicates the time window size for CR evaluation in a dedicated SL-PRS resource pool. | +| sl-DefaultTxConfigIndexDedicatedSL-PRS-RP | Indicates the SL PRS transmission parameters to be used by the UEs which do not have available CBR measurement results, by means of an index to the corresponding entry in sl-PRS-TxConfigIndexList . Value 0 indicates the first entry in sl-PRS-Tx-ConfigIndexList . The field is ignored if the UE has available CBR measurement results. | +| sl-CBR-ConfigIndexDedicatedSL-PRS-RP | Indicates the CBR ranges to be used by an index to the entry of the CBR range configuration in sl-CBR-RangeConfigList-Dedicated-SL-PRS-RP . | +| sl-PRS-TxConfigIndexList | Indicates List of sl-PRS-Tx-ConfigIndex indicating the SL PRS transmission index | +| sl-PRS-TxConfigIndex | Indicates SL PRS transmission Configuration index. | +| sl-PriorityThreshold | Indicates the threshold used to determine whether NR sidelink transmission in dedicated SL PRS resource pool is prioritized over uplink transmission of priority index 0 as specified in TS 38.213[13], clause 16.2.4.3, or whether PUCCH transmission carrying SL HARQ is prioritized over PUCCH transmission carrying UCI of priority index 0 if they overlap in time as specified in TS 38.213 [13], clause 9.2.5.0. | +| sl-PriorityThresholdUL-URLLC | Indicates the threshold used to determine whether NR sidelink transmission in dedicated SL PRS resource pool is prioritized over uplink transmission of priority index 1 as specified in TS 38.213[13], clause 16.2.4.3, or whether PUCCH transmission carrying SL HARQ is prioritized over PUCCH transmission carrying UCI of priority index 1 if they overlap in time as specified in TS 38.213 [13], clause 9.2.5.0. | + +| SL-PRS-PSCCH-Config field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------| +| freqResourcePSCCH-Dedicated-SL-PRS-RP
Indicates the number of PRBs for PSCCH in a dedicated SL PRS resource pool. | +| timeResourcePSCCH-Dedicated-SL-PRS-RP
Indicates the number of symbols for PSCCH in a dedicated SL PRS resource pool. | + +| SL-PRS-PowerControl field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| dl-P0-SL-PRS
Indicates P0 value for DL pathloss based open loop power control for SL PRS transmission in dedicated SL PRS resource pool. | +| dl-AlphaSL-PRS
Indicates alpha value for DL pathloss based open loop power control for SL PRS transmission in dedicated SL PRS resource pool. | +| sl-P0-SL-PRS
Indicates P0 value for SL pathloss based open loop power control for SL PRS transmission in dedicated SL PRS resource pool. | +| sl-AlphaSL-PRS
Indicates alpha value for downlink pathloss based power control for PSCCH/PSSCH when dl-P0-PSSCH-PSCCH is configured. When the field is absent the UE applies the value 1. | + +#### — ***SL-PSBCH-Config*** + +The IE *SL-PSBCH-Config* indicates PSBCH transmission parameters on each sidelink bandwidth part. + +#### ***SL-PSBCH-Config* information element** + +``` +-- ASN1START +-- TAG-SL-PSBCH-CONFIG-START + +SL-PSBCH-Config-r16 ::= SEQUENCE { + dl-P0-PSBCH-r16 INTEGER (-16..15) OPTIONAL, -- Need M + dl-Alpha-PSBCH-r16 ENUMERATED {alpha0, alpha04, alpha05, alpha06, alpha07, alpha08, alpha09, alpha1} OPTIONAL, -- Need M + ..., + [[ + dl-P0-PSBCH-r17 INTEGER (-202..24) OPTIONAL -- Need M + ]] +} + +-- TAG-SL-PSBCH-CONFIG-STOP +-- ASN1STOP +``` + +| SL-PSBCH-Config field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| dl-Alpha-PSBCH
Indicates alpha value for DL pathloss based power control for PSBCH. When the field is not configured the UE applies the value 1. | +| dl-P0-PSBCH
Indicates P0 value for DL pathloss based power control for PSBCH. If not configured, DL pathloss based power control is disabled for PSBCH. When dl-P0-PSBCH-r17 is configured, the UE ignores dl-P0-PSBCH-r16 .
A Remote UE which is out of coverage, considers downlink pathloss based power control is disabled for PSBCH when dl-P0-PSBCH is configured. | + +#### SL-PSSCH-TxConfigList + +The IE *SL-PSSCH-TxConfigList* indicates PSSCH transmission parameters. When lower layers select parameters from the range indicated in IE *SL-PSSCH-TxConfigList*, the UE considers both configurations in IE *SL-PSSCH-TxConfigList* and the CBR-dependent configurations represented in IE *SL-CBR-PriorityTxConfigList*. Only one IE *SL-PSSCH-TxConfig* is provided per *SL-TypeTxSync*. + +#### SL-PSSCH-TxConfigList information element + +``` +-- ASN1START +-- TAG-SL-PSSCH-TXCONFIGLIST-START + +SL-PSSCH-TxConfigList-r16 ::= SEQUENCE (SIZE (1..maxPSSCH-TxConfig-r16)) OF SL-PSSCH-TxConfig-r16 + +SL-PSSCH-TxConfig-r16 ::= SEQUENCE { + sl-TypeTxSync-r16 SL-TypeTxSync-r16 OPTIONAL, -- Need R + sl-ThresUE-Speed-r16 ENUMERATED {kmph60, kmph80, kmph100, kmph120, + kmph140, kmph160, kmph180, kmph200}, + sl-ParametersAboveThres-r16 SL-PSSCH-TxParameters-r16, + sl-ParametersBelowThres-r16 SL-PSSCH-TxParameters-r16, + ... + [[ + sl-ParametersAboveThres-v1650 SL-MinMaxMCS-List-r16 OPTIONAL, -- Need R + sl-ParametersBelowThres-v1650 SL-MinMaxMCS-List-r16 OPTIONAL, -- Need R + ]] +} + +SL-PSSCH-TxParameters-r16 ::= SEQUENCE { + sl-MinMCS-PSSCH-r16 INTEGER (0..27), + sl-MaxMCS-PSSCH-r16 INTEGER (0..31), + sl-MinSubChannelNumPSSCH-r16 INTEGER (1..27), + sl-MaxSubChannelNumPSSCH-r16 INTEGER (1..27), + sl-MaxTxTransNumPSSCH-r16 INTEGER (1..32), + sl-MaxTxPower-r16 SL-TxPower-r16 OPTIONAL -- Cond CBR +} + +-- TAG-SL-PSSCH-TXCONFIGLIST-STOP +-- ASN1STOP +``` + +| SL-PSSCH-TxConfigList field descriptions | | +|-----------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-MaxTxTransNumPSSCH | Indicates the maximum transmission number (including new transmission and retransmission) for PSSCH. | +| sl-MaxTxPower | This field indicates the maximum transmission power for transmission on PSSCH and PSCCH. | +| sl-MinMCS-PSSCH, sl-MaxMCS-PSSCH | This field indicates the minimum and maximum MCS values used for transmissions on PSSCH. The UE shall ignore the minimum and maximum MCS values used for the associated MCS table(s) in sl-ParametersAboveThres-r16 and sl-ParametersBelowThres-r16 if sl-ParametersAboveThres-v1650 and sl-ParametersBelowThres-v1650 are present, respectively. | +| sl-MinSubChannelNumPSSCH, sl-MaxSubChannelNumPSSCH | This field indicates the minimum and maximum number of sub-channels which may be used for transmissions on PSSCH. | +| sl-TypeTxSync | This field indicates the synchronization reference type. For configurations by the eNB/gNB, only gnbEnb can be configured; and for pre-configuration or when this field is absent, the configuration is applicable for all synchronization reference types. | +| sl-ThresUE-Speed | This field indicates a UE absolute speed threshold. | + +| Conditional Presence | Explanation | +|-----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CBR | The field is optionally present, Need R, when the IE SL-PSSCH-TxParameters is present in SL-CBR-CommonTxConfigList , SL-UE-SelectedConfig , SIB12 or SidelinkPreconfigNR ; otherwise the field is not present, need R. | + +#### — *SL-QoS-FlowIdentity* + +The IE *SL-QoS-FlowIdentity* is used to identify a sidelink QoS flow. + +#### ***SL-QoS-FlowIdentity* information element** + +``` +-- ASN1START +-- TAG-SL-QOS-FLOWIDENTITY-START + +SL-QoS-FlowIdentity-r16 ::= INTEGER (1..maxNrofSL-QFIs-r16) + +-- TAG-SL-QOS-FLOWIDENTITY-STOP +-- ASN1STOP +``` + +#### — *SL-QoS-Profile* + +The IE *SL-QoS-Profile* is used to give the QoS parameters for a sidelink QoS flow. Need codes or conditions specified for *SL-QoS-Profile* do not apply, in case *SL-QoS-Profile* is included in *SidelinkUEInformationNR*. + +#### **SL-QoS-Profile information element** + +``` + +-- ASN1START +-- TAG-SL-QOS-PROFILE-START + +SL-QoS-Profile-r16 ::= SEQUENCE { + sl-PQI-r16 SL-PQI-r16 OPTIONAL, -- Need R + sl-GFBR-r16 INTEGER (0..40000000000) OPTIONAL, -- Need R + sl-MFBR-r16 INTEGER (0..40000000000) OPTIONAL, -- Need R + sl-Range-r16 INTEGER (1..1000) OPTIONAL, -- Need R + ... +} + +SL-PQI-r16 ::= CHOICE { + sl-StandardizedPQI-r16 INTEGER (0..255), + sl-Non-StandardizedPQI-r16 SEQUENCE { + sl-ResourceType-r16 ENUMERATED {gbr, non-GBR, delayCriticalGBR, spare1} OPTIONAL, -- Need R + sl-PriorityLevel-r16 INTEGER (1..8) OPTIONAL, -- Need R + sl-PacketDelayBudget-r16 INTEGER (0..1023) OPTIONAL, -- Need R + sl-PacketErrorRate-r16 INTEGER (0..9) OPTIONAL, -- Need R + sl-AveragingWindow-r16 INTEGER (0..4095) OPTIONAL, -- Need R + sl-MaxDataBurstVolume-r16 INTEGER (0..4095) OPTIONAL, -- Need R + ... + } +} + +-- TAG-SL-QOS-PROFILE-STOP +-- ASN1STOP + +``` + +#### **SL-QoS-Profile field descriptions** + +| | | +|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-GFBR | Indicate the guaranteed bit rate for a GBR QoS flow. The unit is: Kbit/s | +| sl-MFBR | Indicate the maximum bit rate for a GBR QoS flow. The unit is: Kbit/s | +| sl-PQI | This field indicates either the PQI for standardized PQI or non-standardized QoS parameters. | +| sl-Range | This field indicates the range parameter of the Qos flow, as defined in clause 5.4.1.1.1, TS 23.287 [55]. It is present only for groupcast. The unit is meter. | + +| SL-PQI field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-AveragingWindow
Indicates the Averaging Window for a QoS flow, and applies to GBR QoS flows only. Unit: ms. The default value of the IE is 2000ms. | +| sl-MaxDataBurstVolume
Indicates the Maximum Data Burst Volume for a QoS flow, and applies to delay critical GBR QoS flows only. Unit: byte. | +| sl-PacketDelayBudget
Indicates the Packet Delay Budget for a QoS flow. Upper bound value for the delay that a packet may experience expressed in unit of 0.5ms. | +| sl-PacketErrorRate
Indicates the Packet Error Rate for a QoS flow. The packet error rate is expressed as Scalar x 10-k where k is the Exponent. | +| sl-PriorityLevel
Indicates the Priority Level for a QoS flow. Values ordered in decreasing order of priority, i.e. with 1 as the highest priority and 8 as the lowest priority. | +| sl-StandardizedPQI
Indicate the PQI for standardized PQI. | + +#### — **SL-QuantityConfig** + +The IE *SL-QuantityConfig* specifies the layer 3 filtering coefficients for NR SL RSRP measurement for a destination. + +#### **SL-QuantityConfig information element** + +``` +-- ASN1START +-- TAG-SL-QUANTITYCONFIG-START + +SL-QuantityConfig-r16 ::= SEQUENCE { + sl-FilterCoefficientDMRS-r16 FilterCoefficient DEFAULT fc4, + ... +} + +-- TAG-SL-QuantityConfig-STOP +-- ASN1STOP +``` + +| SL-QuantityConfig field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-FilterCoefficientDMRS
DMRS based L3 filter configuration:
Specifies L3 filter configuration for sidelink RSRP measurement result from the L1 fiter(s), as defined in TS 38.215 [9]. | + +#### SL-RadioBearerConfig + +The IE *SL-RadioBearerConfig* specifies the sidelink DRB configuration information for NR sidelink communication. + +#### SL-RadioBearerConfig information element + +``` +-- ASN1START +-- TAG-SL-RADIOBEARERCONFIG-START + +SL-RadioBearerConfig-r16 ::= SEQUENCE { + slrb-Uu-ConfigIndex-r16 SLRB-Uu-ConfigIndex-r16, + sl-SDAP-Config-r16 SL-SDAP-Config-r16 OPTIONAL, -- Cond SLRBSetup + sl-PDCP-Config-r16 SL-PDCP-Config-r16 OPTIONAL, -- Cond SLRBSetup + sl-TransRange-r16 ENUMERATED {m20, m50, m80, m100, m120, m150, m180, m200, m220, m250, m270, m300, m350, m370, + m400, m420, m450, m480, m500, m550, m600, m700, m1000, spare9, spare8, spare7, spare6, + spare5, spare4, spare3, spare2, spare1} OPTIONAL, -- Need R + ... +} + +-- TAG-SL-RADIOBEARERCONFIG-STOP +-- ASN1STOP +``` + +#### SL-RadioBearerConfig field descriptions + +| | | +|----------------------------|-------------------------------------------------------------------------------------| +| sl-PDCP-Config | This field indicates the PDCP parameters for the sidelink DRB. | +| sl-SDAP-Config | This field indicates how to map sidelink QoS flows to sidelink DRB. | +| slrb-Uu-ConfigIndex | This field indicates the index of sidelink DRB configuration. | +| sl-TransRange | This field indicates the transmission range of the sidelink DRB. The unit is meter. | + +| Conditional Presence | Explanation | +|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SLRBSetup | The field is mandatory present in case of sidelink DRB setup via the dedicated signalling and in case of sidelink DRB configuration via system information and pre-configuration; otherwise the field is optionally present, need M. | + +#### SL-RBSetConfig + +The IE *SL-RBSetConfig* specifies the configuration information for RB set for NR Sidelink Communication. + +#### SL-RBSetConfig information element + +``` +-- ASN1START +``` + +``` + +-- TAG-SL-RBSETCONFIG-START + +SL-RBSetConfig-r18 ::= SEQUENCE { + sl-RBSetIndex-r18 INTEGER (0..4), + sl-NumOfSSBRepetition-r18 INTEGER (2..9) OPTIONAL, -- Need M + sl-GapBetweenSSBRepetition-r18 INTEGER (1..84) OPTIONAL -- Need M +} + +-- TAG-SL-RBSETCONFIG-STOP +-- ASN1STOP + +``` + +#### SL-RBSetConfig field descriptions + +##### ***sl-GapBetweenSSBRepetition*** + +Indicate the gap between two adjacent S-SSB repetitions in frequency domain in one RB set, and the gap is between the lowest subcarrier of the upper PSBCH and the highest subcarrier of the lower PSBCH. The Unit is PRB. + +##### ***sl-NumOfSSBRepetition*** + +Indicate the number of S-SSB repetitions in frequency domain in one RB set. Legacy S-SSB are applicable in region with no OCB requirement, or with OCB exemption. + +##### ***sl-RBSetIndex*** + +Indicates the index of RB-set for which the configuration applies. + +#### — ***SL-RelayUE-Config*** + +The IE *SL-RelayUE-Config* specifies the configuration information for NR sidelink U2N Relay UE. + +#### SL-RelayUE-Config information element + +``` + +-- ASN1START +-- TAG-SL-RELAYUE-CONFIG-START + +SL-RelayUE-Config-r17 ::= SEQUENCE { + threshHighRelay-r17 RSRP-Range OPTIONAL, -- Need R + threshLowRelay-r17 RSRP-Range OPTIONAL, -- Need R + hystMaxRelay-r17 Hysteresis OPTIONAL, -- Cond ThreshHighRelay + hystMinRelay-r17 Hysteresis OPTIONAL -- Cond ThreshLowRelay +} + +-- TAG-SL-RELAYUE-CONFIG-STOP +-- ASN1STOP + +``` + +| SL-RelayUE-Config field descriptions | | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------| +| threshHighRelay | Indicates the upper threshold of Uu RSRP for a UE that is in network coverage to evaluate AS layer conditions for U2N relay UE operation. | +| threshLowRelay | Indicates the lower threshold of Uu RSRP for a UE that is in network coverage to evaluate AS layer conditions for U2N relay UE operation. | + +| Conditional Presence | Explanation | +|-----------------------------|---------------------------------------------------------------------------------------------------------| +| ThreshHighRelay | This field is mandatory present if threshHighRelay is included. Otherwise, the field is absent, Need R. | +| ThreshLowRelay | This field is mandatory present if threshLowRelay is included. Otherwise, the field is absent, Need R. | + +#### – **SL-RelayUE-ConfigU2U** + +The IE **SL-RelayUE-ConfigU2U** specifies the threshold configuration information for NR sidelink U2U Relay UE. + +#### **SL-RelayUE-ConfigU2U information element** + +``` +-- ASN1START +-- TAG-SL-RELAYUE-CONFIGU2U-START + +SL-RelayUE-ConfigU2U-r18 ::= SEQUENCE { + sl-RSRP-Thresh-DiscConfig-r18 SL-RSRP-Range-r16 OPTIONAL, -- Need R + sl-hystMaxRelay-r18 Hysteresis OPTIONAL, -- Cond SL-RSRP-ThreshRelay + sd-RSRP-Thresh-DiscConfig-r18 SL-RSRP-Range-r16 OPTIONAL, -- Need R + sd-hystMaxRelay-r18 Hysteresis OPTIONAL -- Cond SD-RSRP-ThreshRelay +} + +-- TAG-SL-RELAYUE-CONFIGU2U-STOP +-- ASN1STOP +``` + +| SL-RelayUE-ConfigU2U field descriptions | | +|------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-RSRP-Thresh-DiscConfig | Indicates the threshold of SL-RSRP for a U2U Relay UE to evaluate AS layer conditions for discovery. The U2U relay UE applies the value of this field to decide which UE(s) can be announced as proximity UE(s) in the discovery message when performing U2U Relay Discovery with Model A, and decide whether to forward the discovery message when performing the U2U Relay Discovery with Model B as specified in [65]. | +| sd-RSRP-Thresh-DiscConfig | Indicates the threshold of SD-RSRP for a U2U Relay UE to evaluate AS layer conditions for discovery. The U2U relay UE applies the value of this field to evaluate AS layer conditions to decide which UE(s) can be announced as proximity UE(s) in the discovery message when performing U2U Relay Discovery with Model A, and decide whether to forward the discovery message when performing the U2U Relay Discovery with Model B or U2U relay communication with integrated Discovery as specified in TS 23.304 [65]. | + +| Conditional Presence | Explanation | +|----------------------------|--------------------------------------------------------------------------------------------------------------------------| +| SL-RSRP-ThreshRelay | This field is mandatory present if sl-RSRP-Thresh-DiscConfig is included. Otherwise, the field is absent, Need R. | +| SD-RSRP-ThreshRelay | This field is mandatory present if sd-RSRP-Thresh-DiscConfig is included. Otherwise, the field is absent, Need R. | + +#### SL-RemoteUE-Config + +The IE *SL-RemoteUE-Config* specifies the configuration information for NR sidelink U2N Remote UE. + +#### SL-RemoteUE-Config information element + +``` +-- ASN1START +-- TAG-SL-REMOTEUE-CONFIG-START + +SL-RemoteUE-Config-r17 ::= SEQUENCE { + threshHighRemote-r17 RSRP-Range OPTIONAL, -- Need R + hystMaxRemote-r17 Hysteresis OPTIONAL, -- Cond ThreshHighRemote + sl-ReselectionConfig-r17 SL-ReselectionConfig-r17 OPTIONAL -- Need R +} + +SL-ReselectionConfig-r17 ::= SEQUENCE { + sl-RSRP-Thresh-r17 SL-RSRP-Range-r16 OPTIONAL, -- Need R + sl-FilterCoefficientRSRP-r17 FilterCoefficient OPTIONAL, -- Need R + sl-HystMin-r17 Hysteresis OPTIONAL -- Cond SL-RSRP-Thresh +} + +-- TAG-SL-REMOTEUE-CONFIG-STOP +-- ASN1STOP +``` + +#### SL-RemoteUE-Config field descriptions + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-ReselectionConfig
Includes the parameters used by the U2N remote UE when selecting/ reselecting a U2N relay UE. | +| threshHighRemote
Indicates the threshold of Uu RSRP for a UE that is in network coverage to evaluate AS layer conditions for U2N remote UE operation. | + +#### SL-ReselectionConfig field descriptions + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-FilterCoefficientRSRP
Specifies L3 filter coefficient for SL communication/ discovery RSRP measurement results from L1 filter. | +| sl-RSRP-Thresh
Indicates the threshold of SL communication/ discovery RSRP for a U2N remote UE to perform relay UE selection/ reselection. | + +| Conditional Presence | Explanation | +|-------------------------|-----------------------------------------------------------------------------------------------------------------| +| SL-RSRP-Thresh | This field is mandatory present if sl-RSRP-Thresh is included. Otherwise, the field is absent, Need R. | +| ThreshHighRemote | This field is mandatory present if threshHighRemote is included. Otherwise, the field is absent, Need R. | + +#### SL-RemoteUE-ConfigU2U + +The IE *SL-RemoteUE-ConfigU2U* specifies the threshold configuration information for NR sidelink U2U Remote UE. + +#### SL-RemoteUE-ConfigU2U information element + +``` +-- ASN1START +-- TAG-SL-REMOTEUE-CONFIGU2U-START + +SL-RemoteUE-ConfigU2U-r18 ::= SEQUENCE { + sl-RSRP-ThreshU2U-r18 SL-RSRP-Range-r16 OPTIONAL, -- Need R + sl-FilterCoefficientU2U-r18 FilterCoefficient OPTIONAL, -- Need R + sl-HystMinU2U-r18 Hysteresis OPTIONAL, -- Cond SL-RSRP-ThreshU2U + sd-RSRP-ThreshU2U-r18 SL-RSRP-Range-r16 OPTIONAL, -- Need R + sd-FilterCoefficientU2U-r18 FilterCoefficient OPTIONAL, -- Need R + sd-HystMinU2U-r18 Hysteresis OPTIONAL -- Cond SD-RSRP-ThreshU2U +} + +-- TAG-SL-REMOTEUE-CONFIGU2U-STOP +-- ASN1STOP +``` + +#### SL-RemoteUE-ConfigU2U field descriptions + +| | | +|---------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-RSRP-ThreshU2U | Indicates the threshold of SL-RSRP for a U2U Remote UE to perform Relay UE selection/ reselection. The U2U remote UE applies the value of this field to evaluate AS layer conditions on direct PC5 link with the peer U2U Remote UE to trigger relay selection, and evaluate AS layer conditions on U2U relay link with U2U Relay UE to trigger relay reselection. | +| sl-FilterCoefficientU2U | Specifies L3 filter coefficient for SL-RSRP measurement results from L1 filter. | +| sd-RSRP-ThreshU2U | Indicates the threshold of SD-RSRP for a U2U Remote UE to perform discovery and Relay UE selection/ reselection. For discovery, the U2U Remote UE applies the value of this field to evaluate AS layer conditions to decide whether to respond the discovery message when performing the U2U Relay Discovery with Model B as specified in TS 23.304 [65]. For relay selection and reselection, the U2U remote UE applies the value of this field to evaluate AS layer conditions on direct PC5 link to trigger relay selection, and evaluate AS layer conditions on U2U relay link to trigger relay reselection. The target U2U remote UE applies the value of this field to evaluate AS layer conditions trigger relay selection when performing U2U relay communication with integrated Discovery as specified in TS 23.304 [65]. | +| sd-FilterCoefficientU2U | Specifies L3 filter coefficient for SD-RSRP measurement results from L1 filter. | + +| Conditional Presence | Explanation | +|--------------------------|------------------------------------------------------------------------------------------------------------------| +| SL-RSRP-ThreshU2U | This field is mandatory present if sl-RSRP-ThreshU2U is included. Otherwise, the field is absent, Need R. | +| SD-RSRP-ThreshU2U | This field is mandatory present if sd-RSRP-ThreshU2U is included. Otherwise, the field is absent, Need R. | + +#### — *SL-ReportConfigList* + +The IE *SL-ReportConfigList* concerns a list of SL measurement reporting configurations to add or modify for a destination. + +#### *SL-ReportConfigList* information element + +``` +-- ASN1START +-- TAG-SL-REPORTCONFIGLIST-START + +SL-ReportConfigList-r16 ::= SEQUENCE (SIZE (1..maxNrofSL-ReportConfigId-r16)) OF SL-ReportConfigInfo-r16 + +SL-ReportConfigInfo-r16 ::= SEQUENCE { + sl-ReportConfigId-r16 SL-ReportConfigId-r16, + sl-ReportConfig-r16 SL-ReportConfig-r16, + ... +} + +SL-ReportConfigId-r16 ::= INTEGER (1..maxNrofSL-ReportConfigId-r16) + +SL-ReportConfig-r16 ::= SEQUENCE { + sl-ReportType-r16 CHOICE { + sl-Periodical-r16 SL-PeriodicalReportConfig-r16, + sl-EventTriggered-r16 SL-EventTriggerConfig-r16, + ... + }, + ... +} + +SL-PeriodicalReportConfig-r16 ::= SEQUENCE { + sl-ReportInterval-r16 ReportInterval, + sl-ReportAmount-r16 ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity}, + sl-ReportQuantity-r16 SL-MeasReportQuantity-r16, + sl-RS-Type-r16 SL-RS-Type-r16, + ... +} + +SL-EventTriggerConfig-r16 ::= SEQUENCE { + sl-EventId-r16 CHOICE { + eventSl-r16 SEQUENCE { + sl-Threshold-r16 SL-MeasTriggerQuantity-r16, + sl-ReportOnLeave-r16 BOOLEAN, + sl-Hysteresis-r16 Hysteresis, + sl-TimeToTrigger-r16 TimeToTrigger, + ... + } + } +} +``` + +``` + + }, + eventS2-r16 SEQUENCE { + s2-Threshold-r16 SL-MeasTriggerQuantity-r16, + sl-ReportOnLeave-r16 BOOLEAN, + sl-Hysteresis-r16 Hysteresis, + sl-TimeToTrigger-r16 TimeToTrigger, + ... + }, + ... +}, +sl-ReportInterval-r16 ReportInterval, +sl-ReportAmount-r16 ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity}, +sl-ReportQuantity-r16 SL-MeasReportQuantity-r16, +sl-RS-Type-r16 SL-RS-Type-r16, +... +} + +SL-MeasReportQuantity-r16 ::= CHOICE { + sl-RSRP-r16 BOOLEAN, + ... +} + +SL-MeasTriggerQuantity-r16 ::= CHOICE { + sl-RSRP-r16 RSRP-Range, + ... +} + +SL-RS-Type-r16 ::= ENUMERATED {dmrs, sl-prs, spare2, spare1} + +-- TAG-SL-REPORTCONFIGLIST-STOP +-- ASN1STOP + +``` + +#### SL-ReportConfig field descriptions + +##### **sl-ReportType** + +Type of the configured sidelink measurement report. + +| SL-EventTriggerConfig field descriptions | | +|-------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-EventId | Choice of sidelink measurement event triggered reporting criteria. | +| sl-ReportAmount | Number of sidelink measurement reports applicable for sl-EventTriggered report type. | +| sl-ReportInterval | Indicates the interval between periodical reports (i.e., when sl-ReportAmount exceeds 1) for sl-EventTriggered report type. | +| sl-ReportOnLeave | indicates whether or not the UE shall initiate the sidelink measurement reporting procedure when the leaving condition is met for a frequency in sl-FrequencyTriggeredList , as specified in 5.8.10.4.1. | +| sl-ReportQuantity | The sidelink measurement quantities to be included in the sidelink measurement report. | +| sl-TimeToTrigger | Time during which specific criteria for the event needs to be met in order to trigger a sidelink measurement report. | +| sN-Threshold | Threshold used for events S1 and S2 specified in clauses 5.8.10.4.2 and 5.8.10.4.3, respectively. | + +| SL-PeriodicalReportConfig field descriptions | | +|-----------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------| +| sl-ReportAmount | Number of sidelink measurement reports applicable for sl-Periodical report type. | +| sl-ReportInterval | Indicates the interval between periodical reports (i.e., when sl-ReportAmount exceeds 1) for sl-Periodical report type. | +| sl-ReportQuantity | The sidelink measurement quantities to be included in the sidelink measurement report. | + +#### — *SL-ResourcePool* + +The IE *SL-ResourcePool* specifies the configuration information for NR sidelink communication resource pool. + +#### ***SL-ResourcePool* information element** + +``` +-- ASN1START +-- TAG-SL-RESOURCEPOOL-START + +SL-ResourcePool-r16 ::= SEQUENCE { + sl-PSCCH-Config-r16 SetupRelease { SL-PSCCH-Config-r16 } OPTIONAL, -- Need M + sl-PSSCH-Config-r16 SetupRelease { SL-PSSCH-Config-r16 } OPTIONAL, -- Need M + sl-PSFCH-Config-r16 SetupRelease { SL-PSFCH-Config-r16 } OPTIONAL, -- Need M + sl-SyncAllowed-r16 SL-SyncAllowed-r16 OPTIONAL, -- Need M + sl-SubchannelSize-r16 ENUMERATED {n10, n12, n15, n20, n25, n50, n75, n100} OPTIONAL, -- Need M + dummy INTEGER (10..160) OPTIONAL, -- Need M + sl-StartRB-Subchannel-r16 INTEGER (0..265) OPTIONAL, -- Need M + sl-NumSubchannel-r16 INTEGER (1..27) OPTIONAL, -- Need M +} +``` + +``` + +sl-Additional-MCS-Table-r16 ENUMERATED {qam256, qam64LowSE, qam256-qam64LowSE } OPTIONAL, -- Need M +sl-ThreshS-RSSI-CBR-r16 INTEGER (0..45) OPTIONAL, -- Need M +sl-TimeWindowSizeCBR-r16 ENUMERATED {ms100, slot100} OPTIONAL, -- Need M +sl-TimeWindowSizeCR-r16 ENUMERATED {ms1000, slot1000} OPTIONAL, -- Need M +sl-PTRS-Config-r16 SL-PTRS-Config-r16 OPTIONAL, -- Need M +sl-UE-SelectedConfigRP-r16 SL-UE-SelectedConfigRP-r16 OPTIONAL, -- Need M +sl-RxParametersNcell-r16 SEQUENCE { + sl-TDD-Configuration-r16 TDD-UL-DL-ConfigCommon OPTIONAL, -- Need M + sl-SyncConfigIndex-r16 INTEGER (0..15) +} OPTIONAL, -- Need M +sl-ZoneConfigMCR-List-r16 SEQUENCE (SIZE (16)) OF SL-ZoneConfigMCR-r16 OPTIONAL, -- Need M +sl-FilterCoefficient-r16 FilterCoefficient OPTIONAL, -- Need M +sl-RB-Number-r16 INTEGER (10..275) OPTIONAL, -- Need M +sl-PreemptionEnable-r16 ENUMERATED {enabled, pl1, pl2, pl3, pl4, pl5, pl6, pl7, pl8} OPTIONAL, -- Need R +sl-PriorityThreshold-UL-URLLC-r16 INTEGER (1..9) OPTIONAL, -- Need M +sl-PriorityThreshold-r16 INTEGER (1..9) OPTIONAL, -- Need M +sl-X-Overhead-r16 ENUMERATED {n0, n3, n6, n9} OPTIONAL, -- Need S +sl-PowerControl-r16 SL-PowerControl-r16 OPTIONAL, -- Need M +sl-TxPercentageList-r16 SL-TxPercentageList-r16 OPTIONAL, -- Need M +sl-MinMaxMCS-List-r16 SL-MinMaxMCS-List-r16 OPTIONAL, -- Need M +... +[[ +sl-TimeResource-r16 BIT STRING (SIZE (10..160)) OPTIONAL -- Need M +]], +[[ +sl-PBPS-CPS-Config-r17 SetupRelease { SL-PBPS-CPS-Config-r17 } OPTIONAL, -- Need M +sl-InterUE-CoordinationConfig-r17 SetupRelease { SL-InterUE-CoordinationConfig-r17 } OPTIONAL -- Need M +]], +[[ +sl-CPE-StartingPositionsPSCCH-PSSCH-InitiateCOT-List-r18 + SetupRelease { SL-CPE-StartingPositionsPSCCH-PSSCH-List-r18 } OPTIONAL, -- Need M +sl-CPE-StartingPositionsPSCCH-PSSCH-InitiateCOT-Default-r18 INTEGER (1..9) OPTIONAL, -- Need M +sl-CPE-StartingPositionsPSCCH-PSSCH-WithinCOT-List-r18 + SetupRelease { SL-CPE-StartingPositionsPSCCH-PSSCH-List-r18 } OPTIONAL, -- Need M +sl-CPE-StartingPositionsPSCCH-PSSCH-WithinCOT-Default-r18 INTEGER (1..9) OPTIONAL, -- Need M +sl-Type1-LBT-BlockingOption1-r18 ENUMERATED {enabled} OPTIONAL, -- Need R +sl-Type1-LBT-BlockingOption2-r18 ENUMERATED {enabled} OPTIONAL, -- Need R +sl-NumInterlacePerSubchannel-r18 ENUMERATED {sc1, sc2} OPTIONAL, -- Need M +sl-NumReferencePRBs-OfInterlace-r18 ENUMERATED {prb10, prb11} OPTIONAL, -- Need M +sl-TransmissionStructureForPSFCH-r18 ENUMERATED {commonInterlace, dedicatedInterlace} OPTIONAL, -- Need M +sl-NumDedicatedPRBs-ForPSFCH-r18 ENUMERATED {prb1, prb2, prb5} OPTIONAL, -- Need M +sl-NumPSFCH-Occasions-r18 ENUMERATED {o1, o2, o3, o4} OPTIONAL, -- Need M +sl-PSFCH-CommonInterlaceIndex-r18 INTEGER (0..9) OPTIONAL, -- Need M +sl-CPE-StartingPositionPSFCH-r18 INTEGER (1..9) OPTIONAL, -- Need M +sl-NumRefSymbolLength-r18 ENUMERATED {sym7, sym8, sym9, sym10, sym11, sym12, sym13, sym14} OPTIONAL, -- Need M +sl-PSFCH-RB-SetList-r18 SEQUENCE (SIZE (1..4)) OF BIT STRING (SIZE (10..275)) OPTIONAL, -- Need M +sl-IUC-RB-SetList-r18 SEQUENCE (SIZE (1..4)) OF BIT STRING (SIZE (10..275)) OPTIONAL, -- Need M +sl-PSFCH-PowerOffset-r18 INTEGER (0..10) OPTIONAL, -- Need M +sl-RBSetIndexOfResourcePool-r18 SEQUENCE (SIZE (1..5)) OF INTEGER (0..4) OPTIONAL, -- Need M +sl-A2X-Service-r18 ENUMERATED {brid, daa, bridAndDAA, spare1} OPTIONAL, -- Need M +sl-PRS-ResourcesSharedSL-PRS-RP-r18 SEQUENCE (SIZE (1..17)) OF SL-PRS-ResourceSharedSL-PRS-RP-r18 OPTIONAL, -- Need M + +``` + +``` + + numSym-SL-PRS-2ndStageSCI-r18 INTEGER (1..4) OPTIONAL, -- Need M + sl-SCI-based-SL-PRS-Tx-Trigger-SCI2-D-r18 BOOLEAN OPTIONAL, -- Need M + sl-TriggerConditionRequest-r17 INTEGER (0..1) OPTIONAL, -- Need M + ]] +} + +SL-CPE-StartingPositionsPSCCH-PSSCH-List-r18 ::= SEQUENCE (SIZE (8)) OF SL-CPE-StartingPositionsPSCCH-PSSCH-r18 + +SL-CPE-StartingPositionsPSCCH-PSSCH-r18 ::= SEQUENCE { + sl-Priority-r18 INTEGER (1..8), + sl-CPE-StartingPositions-r18 SEQUENCE (SIZE (1..9)) OF INTEGER (1..9) +} + +SL-ZoneConfigMCR-r16 ::= SEQUENCE { + sl-ZoneConfigMCR-Index-r16 INTEGER (0..15), + sl-TransRange-r16 ENUMERATED {m20, m50, m80, m100, m120, m150, m180, m200, m220, m250, m270, m300, m350, + m370, m400, m420, m450, m480, m500, m550, m600, m700, m1000, spare9, spare8, + spare7, spare6, spare5, spare4, spare3, spare2, spare1} + OPTIONAL, -- Need M + sl-ZoneConfig-r16 SL-ZoneConfig-r16 OPTIONAL, -- Need M + ... +} + +SL-SyncAllowed-r16 ::= SEQUENCE { + gnss-Sync-r16 ENUMERATED {true} OPTIONAL, -- Need R + gnbEnb-Sync-r16 ENUMERATED {true} OPTIONAL, -- Need R + ue-Sync-r16 ENUMERATED {true} OPTIONAL, -- Need R +} + +SL-PSCCH-Config-r16 ::= SEQUENCE { + sl-TimeResourcePSCCH-r16 ENUMERATED {n2, n3} OPTIONAL, -- Need M + sl-FreqResourcePSCCH-r16 ENUMERATED {n10,n12, n15, n20, n25} OPTIONAL, -- Need M + sl-DMRS-ScrambleID-r16 INTEGER (0..65535) OPTIONAL, -- Need M + sl-NumReservedBits-r16 INTEGER (2..4) OPTIONAL, -- Need M + ... +} + +SL-PSSCH-Config-r16 ::= SEQUENCE { + sl-PSSCH-DMRS-TimePatternList-r16 SEQUENCE (SIZE (1..3)) OF INTEGER (2..4) OPTIONAL, -- Need M + sl-BetaOffsets2ndSCI-r16 SEQUENCE (SIZE (4)) OF SL-BetaOffsets-r16 OPTIONAL, -- Need M + sl-Scaling-r16 ENUMERATED {f0p5, f0p65, f0p8, f1} OPTIONAL, -- Need M + ... +} + +SL-PSFCH-Config-r16 ::= SEQUENCE { + sl-PSFCH-Period-r16 ENUMERATED {s10, s11, s12, s14} OPTIONAL, -- Need M + sl-PSFCH-RB-Set-r16 BIT STRING (SIZE (10..275)) OPTIONAL, -- Need M + sl-NumMuxCS-Pair-r16 ENUMERATED {n1, n2, n3, n6} OPTIONAL, -- Need M + sl-MinTimeGapPSFCH-r16 ENUMERATED {s12, s13} OPTIONAL, -- Need M + sl-PSFCH-HopID-r16 INTEGER (0..1023) OPTIONAL, -- Need M + sl-PSFCH-CandidateResourceType-r16 ENUMERATED {startSubCH, allocSubCH} OPTIONAL, -- Need M +} + +``` + +``` + + ... + } + SL-PTRS-Config-r16 ::= + sl-PTRS-FreqDensity-r16 SEQUENCE (SIZE (2)) OF INTEGER (1..276) OPTIONAL, -- Need M + sl-PTRS-TimeDensity-r16 SEQUENCE (SIZE (3)) OF INTEGER (0..29) OPTIONAL, -- Need M + sl-PTRS-RE-Offset-r16 ENUMERATED {offset01, offset10, offset11} OPTIONAL, -- Need M + ... + } + + SL-UE-SelectedConfigRP-r16 ::= + sl-CBR-PriorityTxConfigList-r16 SL-CBR-PriorityTxConfigList-r16 OPTIONAL, -- Need M + sl-Thres-RSRP-List-r16 SL-Thres-RSRP-List-r16 OPTIONAL, -- Need M + sl-MultiReserveResource-r16 ENUMERATED {enabled} OPTIONAL, -- Need M + sl-MaxNumPerReserve-r16 ENUMERATED {n2, n3} OPTIONAL, -- Need M + sl-SensingWindow-r16 ENUMERATED {ms100, ms1100} OPTIONAL, -- Need M + sl-SelectionWindowList-r16 SL-SelectionWindowList-r16 OPTIONAL, -- Need M + sl-ResourceReservePeriodList-r16 SEQUENCE (SIZE (1..16)) OF SL-ResourceReservePeriod-r16 OPTIONAL, -- Need M + sl-RS-ForSensing-r16 ENUMERATED {pscch, pssch}, + ... + [[ + sl-CBR-PriorityTxConfigList-v1650 SL-CBR-PriorityTxConfigList-v1650 OPTIONAL -- Need M + ]], + [[ + sl-NRPSSCH-EUTRA-ThresRSRP-List-r18 SL-Thres-RSRP-List-r16 OPTIONAL, -- Need M + sl-NRPSFCH-EUTRA-ThresRSRP-List-r18 SL-Thres-RSRP-List-r16 OPTIONAL -- Need M + ]] + } + + SL-ResourceReservePeriod-r16 ::= + sl-ResourceReservePeriod1-r16 ENUMERATED {ms0, ms100, ms200, ms300, ms400, ms500, ms600, ms700, ms800, ms900, ms1000}, + sl-ResourceReservePeriod2-r16 INTEGER (1..99) + } + + SL-SelectionWindowList-r16 ::= + SEQUENCE (SIZE (8)) OF SL-SelectionWindowConfig-r16 + + SL-SelectionWindowConfig-r16 ::= + sl-Priority-r16 INTEGER (1..8), + sl-SelectionWindow-r16 ENUMERATED {n1, n5, n10, n20} + } + + SL-TxPercentageList-r16 ::= + SEQUENCE (SIZE (8)) OF SL-TxPercentageConfig-r16 + + SL-TxPercentageConfig-r16 ::= + sl-Priority-r16 INTEGER (1..8), + sl-TxPercentage-r16 ENUMERATED {p20, p35, p50} + } + + SL-MinMaxMCS-List-r16 ::= + SEQUENCE (SIZE (1..3)) OF SL-MinMaxMCS-Config-r16 + + SL-MinMaxMCS-Config-r16 ::= + sl-MCS-Table-r16 ENUMERATED {gam64, gam256, gam64LowSE}, + +``` + +``` + +sl-MinMCS-PSSCH-r16 INTEGER (0..27), +sl-MaxMCS-PSSCH-r16 INTEGER (0..31) +} + +SL-BetaOffsets-r16 ::= INTEGER (0..31) + +SL-PowerControl-r16 ::= SEQUENCE { + sl-MaxTransPower-r16 INTEGER (-30..33), + sl-Alpha-PSSCH-PSCCH-r16 ENUMERATED {alpha0, alpha04, alpha05, alpha06, alpha07, alpha08, alpha09, alpha1} OPTIONAL, -- Need M + dl-Alpha-PSSCH-PSCCH-r16 ENUMERATED {alpha0, alpha04, alpha05, alpha06, alpha07, alpha08, alpha09, alpha1} OPTIONAL, -- Need S + sl-P0-PSSCH-PSCCH-r16 INTEGER (-16..15) OPTIONAL, -- Need S + dl-P0-PSSCH-PSCCH-r16 INTEGER (-16..15) OPTIONAL, -- Need M + dl-Alpha-PSFCH-r16 ENUMERATED {alpha0, alpha04, alpha05, alpha06, alpha07, alpha08, alpha09, alpha1} OPTIONAL, -- Need S + dl-P0-PSFCH-r16 INTEGER (-16..15) OPTIONAL, -- Need M + ... + [[ + dl-P0-PSSCH-PSCCH-r17 INTEGER (-202..24) OPTIONAL, -- Need M + sl-P0-PSSCH-PSCCH-r17 INTEGER (-202..24) OPTIONAL, -- Need S + dl-P0-PSFCH-r17 INTEGER (-202..24) OPTIONAL, -- Need M + ]] +} + +SL-PRS-ResourceSharedSL-PRS-RP-r18 ::= SEQUENCE { + sl-PRS-ResourceID-r18 INTEGER (0..16) OPTIONAL, -- Need M + mNumberOfSymbols-r18 INTEGER (1..9) OPTIONAL, -- Need M + nCombSize-r18 ENUMERATED{n2,n4,n6} OPTIONAL, -- Need M + sl-PRS-starting-symbol-r18 INTEGER (4..12) OPTIONAL, -- Need M + sl-PRS-comb-offset-r18 INTEGER (1..5) OPTIONAL, -- Need M +} + +-- TAG-SL-RESOURCEPOOL-STOP +-- ASN1STOP + +``` + +Editor's note: The value range of *sl-PSFCH-PowerOffset* may need to be updated based on RAN4 reply LS. + +| SL-ZoneConfigMCR field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-TransRange
Indicates the communication range requirement for the corresponding sl-ZoneConfigMCR-Index . The unit is meter. | +| sl-ZoneConfig
Indicates the zone configuration for the corresponding sl-ZoneConfigMCR-Index . | +| sl-ZoneConfigMCR-Index
Indicates the codepoint of the communication range requirement field in SCI. | + +| SL-ResourcePool field descriptions | | +|-----------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| dummy | This field is not used in the specification. If received it shall be ignored by the UE. | +| numSym-SL-PRS-2ndStageSCI | Indicates the number symbols to be assumed for SL PRS in determining the number of coded modulation symbols for second stage SCI in a slot of a shared SL PRS resource pool. | +| sl-A2X-Service | Presence of this field indicates the resource pool is dedicated for A2X service, i.e., not to be used for other than A2X service. Value brid indicates the resource pool is for BRID, value daa indicates the resource pool is for DAA, and value bridAndDAA indicates the resource pool is for both BRID and DAA. If this field is absent in all the configured resource pools, the UE may choose non-dedicated resource pool for A2X service. | +| sl-Additional-MCS-Table | Indicates the MCS table(s) additionally used in the resource pool. 64QAM table is (pre-)configured as default. Zero, one or two can be additionally (pre-)configured using the 256QAM and/or low-SE MCS tables. If two MCS tables are indicated, 256QAM MCS table is the 1 st table and qam64lowSE MCS table is the 2 nd table as specified in TS 38.214 [19], clause 8.1.3.1. | +| sl-CPE-StartingPositionsPSCCH-PSSCH-InitiateCOT-Default | Indicates CPE starting position index for the default CPE starting position, to be used for PSCCH/PSSCH transmission when UE initiating a COT. | +| sl-CPE-StartingPositionsPSCCH-PSSCH-InitiateCOT-List | Indicates a set of selected indices that correspond to multiple candidate CPE starting positions to be used for PSCCH/PSSCH transmission when UE initiating a COT, associated per L1 priority of PSSCH. | +| sl-CPE-StartingPositionsPSCCH-PSSCH-WithinCOT-Default | Indicates CPE starting position index for the default CPE starting position, to be used by UE for PSCCH/PSSCH transmission within a COT. | +| sl-CPE-StartingPositionsPSCCH-PSSCH-WithinCOT-List | Indicates a set of one or multiple selected indices that correspond to one or multiple candidate CPE starting positions to be used by UE for PSCCH/PSSCH transmission within a COT, associated per L1 priority of PSSCH. | +| sl-CPE-StartingPositionPSFCH | Indicates CPE starting position within the GP symbol before PSFCH transmission. The value is an index of the set of all candidate CPE starting positions specified in Table 5.3.1-3 of [16, TS38.211] for Ci=1 and the corresponding SCS of the SL BWP. | +| sl-FilterCoefficient | This field indicates the filtering coefficient for long-term measurement and reference signal power derivation used for sidelink open-loop power control. | +| sl-InterUE-CoordinationConfig | Indicates the configured sidelink inter-UE coordination parameters. | +| sl-IUC-RB-SetList | The n-th value in the list indicates the set of PRBs that are actually used for inter-UE coordination information transmission and reception in Scheme 2. It shall be (pre-)configured such that N candidate PSFCH occasion(s) are associated with N different PRB sets. PRBs within intra-cell guard band are not used for PSFCH transmission. The length of this list is aligned with sl-NumPSFCH-Occasions . For each PSFCH occasion, the set of PRBs are indicated in the same format as in sl-PSFCH-RB-Set . | +| sl-NumDedicatedPRBs-ForPSFCH | Indicates the value of K3 when each PSFCH transmission occupies "1 common interlace and K3 dedicated PRB(s)" (as indicated by sl-TransmissionStructureForPSFCH ). Value prb1 corresponds to K3=1, value prb2 corresponds to K3=2, and so on. UE expects the same (pre-)configured value of sl-NumDedicatedPRBs-ForPSFCH across all resource pools. | +| sl-NumInterlacePerSubchannel | Indicates the number of (K) interlaces per sub-channel within a resource pool. Value sc1 corresponds to 1 interlace per sub-channel, and value sc2 corresponds to 2 interlaces per sub-channel. The applicable values are related to the subcarrier spacing as below:
For SCS = 15 kHz: K=1 or 2
For SCS = 30 kHz: K=1 | + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-NumPSFCH-Occasions
Indicates one PSCCH/PSSCH transmission has N associated candidate PSFCH occasion(s). Value o1 corresponds to N=1, value o2 corresponds to N=2, and so on. If the field is not configured, the UE shall use value o1 . | +| sl-NumReferencePRBs-OfInterlace
Indicate reference number of PRBs of one interlace within 1 RB set. Value prb10 corresponds to 10 PRBs, and value prb11 corresponds to 11 PRBs. | +| sl-NumRefSymbolLength
Indicates a reference number of symbols for TBS determination. | +| sl-NumSubchannel
Indicates the number of subchannels in the corresponding resource pool, which consists of contiguous PRBs only. | +| sl-PBPS-CPS-Config
Indicates the allowed resource allocation schemes of full sensing only, partial sensing only, random resource selection only, or any combination(s), and the related configuration for power saving resource allocation schemes. This field is absent for sl-TxPoolExceptional . | +| sl-PreemptionEnable
Indicates whether pre-emption is disabled or enabled in a resource pool. If the field is present and the value is p1 , p2 , and so on (but not enabled ), it means that pre-emption is enabled and a priority level p_preemption is configured. If the field is present and the value is enabled , the pre-emption is enabled (but p_preemption is not configured) and pre-emption is applicable to all levels. | +| sl-PriorityThreshold-UL-URLLC
Indicates the threshold used to determine whether NR sidelink transmission is prioritized over uplink transmission of priority index 1 as specified in TS 38.213[13], clause 16.2.4.3, or whether PUCCH transmission carrying SL HARQ is prioritized over PUCCH transmission carrying UCI of priority index 1 if they overlap in time as specified in TS 38.213 [13], clause 9.2.5.0. | +| sl-PriorityThreshold
Indicates the threshold used to determine whether NR sidelink transmission is prioritized over uplink transmission of priority index 0 as specified in TS 38.213[13], clause 16.2.4.3, or whether PUCCH transmission carrying SL HARQ is prioritized over PUCCH transmission carrying UCI of priority index 0 if they overlap in time as specified in TS 38.213 [13], clause 9.2.5.0. | +| sl-PRS-ResourcesSharedSL-PRS-RP
Indicates SL PRS resources in a slot of shared SL PRS resource pool as defined in TS 38.211 [16]. | +| sl-PSFCH-CommonInterlaceIndex
Indicate the index of common interlace to meet OCB requirements when transmissionStructureForPSFCH is set to common interlace. Value 0 corresponds to interlace 0 is used as common interlace, value 1 corresponds to interlace 1 is used as common interlace and so on. | +| sl-PSFCH-PowerOffset
Indicates the power offset between Tx power on one common PRB ( P_common ) and Tx power on one dedicated PRB ( P_dedicated ) when sl-TransmissionStructureForPSFCH is (pre-)configured as commonInterlace , i.e., P_common = P_dedicated - offset. UE expects the same (pre-)configured value of sl-PSFCH-PowerOffset across all resource pools. The unit is dB. | +| sl-PSFCH-RB-SetList
The n-th value in the list indicates the set of PRBs that are actually used for PSFCH transmission and reception of n-th PSFCH occasion of a PSCCH/PSSCH transmission. It shall be (pre-)configured such that N candidate PSFCH occasion(s) are associated with N different PRB sets. PRBs within intra-cell guard band are not used for PSFCH transmission. The length of this list is aligned with sl-NumPSFCH-Occasions . For each PSFCH occasion, the set of PRBs are indicated in the same format as in sl-PSFCH-RB-Set . | +| sl-RB-Number
Indicates the number of PRBs in the corresponding resource pool, which consists of contiguous PRBs only. The remaining RB cannot be used (See TS 38.214[19], clause 8). | +| sl-RBSetIndexOfResourcePool
For interlace RB based PSCCH/PSSCH, indicates the RB set index(s) included in the resource pool. Contiguous RB sets are (pre-)configured for a resource pool. | +| sl-SCI-based-SL-PRS-Tx-Trigger-SCI2-D
Indicates presence of a bit-field in SCI format 2-D to trigger SL-PRS transmission by a receiving UE. | + +| | | +|-----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-StartRB-Subchannel | Indicates the lowest RB index of the subchannel with the lowest index in the resource pool with respect to the lowest RB index of a SL BWP. | +| sl-SubchannelSize | Indicates the minimum granularity in frequency domain for the sensing for PSSCH resource selection in the unit of PRB. | +| sl-SyncAllowed | Indicates the allowed synchronization reference(s) which is (are) allowed to use the configured resource pool. | +| sl-SyncConfigIndex | Indicates the synchronisation configuration that is associated with a reception pool, by means of an index to the corresponding entry SL-SyncConfigList of in SIB12 for NR sidelink communication. | +| sl-TDD-Configuration | Indicates the TDD configuration associated with the reception pool of the cell indicated by sl-SyncConfigIndex . | +| sl-ThreshS-RSSI-CBR | Indicates the S-RSSI threshold for determining the contribution of a sub-channel to the CBR measurement. Value 0 corresponds to -112 dBm, value 1 to -110 dBm, value n to $(-112 + n*2)$ dBm, and so on. | +| sl-TimeResource | Indicates the bitmap of the resource pool, which is defined by repeating the bitmap with a periodicity during a SFN or DFN cycle. | +| sl-TimeWindowSizeCBR | Indicates the time window size for CBR measurement. | +| sl-TimeWindowSizeCR | Indicates the time window size for CR evaluation. | +| sl-TransmissionStructureForPSFCH | Indicate each PSFCH transmission occupies "1 common interlace and K3 dedicated PRB(s)", or "1 dedicated interlace". Value commonInterlace corresponds to "1 common interlace and K3 dedicated PRB(s)", and value dedicatedInterlace corresponds to "1 dedicated interlace". UE expects the same (pre-)configured value of transmissionStructureForPSFCH across all resource pools. | +| sl-TxPercentageList | Indicates the portion of candidate single-slot PSSCH resources over the total resources. Value p20 corresponds to 20%, and so on. | +| sl-Type1-LBT-BlockingOption1 | Indicates UE may avoid selection of N consecutive resource(s) before a reserved resource when the L1 SL priority value for the transmission is higher than the L1 SL priority value of the reserved resource, and UE may also avoid selection of M consecutive resource(s) after a reserved resource when the transmitting symbols of the reserved resource overlap with LBT of the selected resource. The selection of the value N is up to UE implementation from {0, 1, 2}. M is determined based on UE implementation (at least including 0). | +| sl-Type1-LBT-BlockingOption2 | Indicates UE may prioritize/select resource(s) in the slot(s) for transmission, if UE's transmission in slot(s) before a reserved resource is able to share its initiated COT to the reservation. | +| sl-X-Overhead | Accounts for overhead from CSI-RS, PT-RS. If the field is absent, the UE applies value n0 (see TS 38.214 [19], clause 5.1.3.2). | + +| SL-SyncAllowed field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| gnbEnb-Sync
If configured, the (pre-) configured resources can be used if the UE is directly or indirectly synchronized to eNB or gNB (i.e., synchronized to a reference UE which is directly synchronized to eNB or gNB). | +| gnss-Sync
If configured, the (pre-) configured resources can be used if the UE is directly or indirectly synchronized to GNSS (i.e., synchronized to a reference UE which is directly synchronized to GNSS). | +| ue-Sync
If configured, the (pre-) configured resources can be used if the UE is synchronized to a reference UE which is not synchronized to eNB, gNB and GNSS directly or indirectly. | + +| SL-PSCCH-Config field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-FreqResourcePSCCH
Indicates the number of PRBs for PSCCH in a resource pool where it is not greater than the number PRBs of the subchannel. | +| sl-DMRS-ScrambleID
Indicates the initialization value for PSCCH DMRS scrambling. | +| sl-NumReservedBits
Indicates the number of reserved bits in first stage SCI. | +| sl-TimeResourcePSCCH
Indicates the number of symbols of PSCCH in a resource pool. | + +| SL-PSSCH-Config field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-BetaOffsets2ndSCI
Indicates candidates of beta-offset values to determine the number of coded modulation symbols for second stage SCI. The value indicates the index of Table 9.3-2 of TS 38.213 [13]. | +| sl-PSSCH-DMRS-TimePatternList
Indicates the set of PSSCH DMRS time domain patterns in terms of PSSCH DMRS symbols in a slot that can be used in the resource pool. | +| sl-Scaling
Indicates a scaling factor to limit the number of resource elements assigned to the second stage SCI on PSSCH. Value f0p5 corresponds to 0.5, value f0p65 corresponds to 0.65, and so on. | + +| SL-PSFCH-Config field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-MinTimeGapPSFCH
The minimum time gap between PSFCH and the associated PSSCH in the unit of slots. | +| sl-NumMuxCS-Pair
Indicates the number of cyclic shift pairs used for a PSFCH transmission that can be multiplexed in a PRB. | +| sl-PSFCH-CandidateResourceType
Indicates the number of PSFCH resources available for multiplexing HARQ-ACK information in a PSFCH transmission (see TS 38.213 [13], clause 16.3). | +| sl-PSFCH-HopID
Scrambling ID for sequence hopping of the PSFCH used in the resource pool. | +| sl-PSFCH-Period
Indicates the period of PSFCH resource in the unit of slots within this resource pool. If set to s/0 , no resource for PSFCH, and HARQ feedback for all transmissions in the resource pool is disabled. | +| sl-PSFCH-RB-Set
Indicates the set of PRBs that are actually used for PSFCH transmission and reception. The leftmost bit of the bitmap refers to the lowest RB index in the resource pool, and so on. Value 0 in the bitmap indicates that the corresponding PRB is not used for PSFCH transmission and reception while value 1 indicates that the corresponding PRB is used for PSFCH transmission and reception (see TS 38.213 [13]). | + +| SL-PTRS-Config field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-PTRS-FreqDensity
Presence and frequency density of SL PT-RS as a function of scheduled BW. If the field is not configured, the UE uses $K\_PT-RS = 2$ | +| sl-PTRS-TimeDensity
Presence and time density of SL PT-RS as a function of MCS. If the field is not configured, the UE uses $L\_PT-RS = 1$ | +| sl-PTRS-RE-Offset
Indicates the subcarrier offset for SL PT-RS . If the field is not configured, the UE applies the value offset00 (see TS 38.211 [16], clause 8.4.1.2.2). | + +| SL-UE-SelectedConfigRP field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-CBR-PriorityTxConfigList
Indicates the mapping between PSSCH transmission parameter (such as MCS, PRB number, retransmission number, CR limit) sets by using the indexes of the configurations in sl-CBR-PSSCH-TxConfigList , CBR ranges by using the indexes to the entry of the CBR range configurations in sl-CBR-RangeConfigList , and priority ranges. It also indicates the default PSSCH transmission parameters to be used when CBR measurement results are not available, and MCS range for the MCS tables used in the resource pool. The field sl-CBR-PriorityTxConfigList-v1650 is present only when sl-CBR-PriorityTxConfigList-r16 is configured. | +| sl-MaxNumPerReserve
Indicates the maximum number of reserved PSCCH/PSSCH resources that can be indicated by an SCI. | +| sl-MultiReserveResource
Indicates if it is allowed to reserve a sidelink resource for an initial transmission of a TB by an SCI associated with a different TB, based on sensing and resource selection procedure. | +| sl-NRPSFCH-EUTRA-ThresRSRP-List
Indicates a list of 64 thresholds from which a threshold should be selected based on the priority in the decoded EUTRA SCI and the priority in the NR SCI to be transmitted. A NR SL resource is excluded if the corresponding PSFCH transmission occasions overlap with resources indicated or reserved by the decoded EUTRA SCI in time domain and EUTRA PSSCH RSRP in the associated data resource is above the threshold. If the field is present, the UE shall perform the dynamic co-channel coexistence of LTE sidelink and NR sidelink as specified in TS 38.214; otherwise it shall not perform it. | +| sl-NRPSSCH-EUTRA-ThresRSRP-List
Indicates a list of 64 thresholds, and a threshold should be selected based on the priority in the decoded EUTRA SCI and the priority in the NR SCI to be transmitted. A NR SL resource is excluded if it is indicated or reserved by the decoded EUTRA SCI and EUTRA PSSCH RSRP in the associated data resource is above the threshold. | +| sl-ResourceReservePeriodList
Set of possible resource reservation period allowed in the resource pool in the unit of ms. Up to 16 values can be configured per resource pool. The value ms0 is always configured. | +| sl-RS-ForSensing
Indicates whether DMRS of PSCCH or PSSCH is used for L1 RSRP measurement in the sensing operation. | +| sl-SensingWindow
Parameter that indicates the start of the sensing window. | +| sl-SelectionWindowList
Parameter that determines the end of the selection window in the resource selection for a TB with respect to priority indicated in SCI. Value n1 corresponds to $1 \cdot 2^\mu$ , value n5 corresponds to $5 \cdot 2^\mu$ , and so on, where $\mu = 0, 1, 2, 3$ refers to SCS 15, 30, 60, 120 kHz respectively. | +| sl-Thres-RSRP-List
Indicates a list of 64 thresholds, and the threshold should be selected based on the priority in the decoded SCI and the priority in the SCI to be transmitted. A resource is excluded if it is indicated or reserved by a decoded SCI and PSSCH/PSCCH RSRP in the associated data resource is above a threshold. | + +| SL-PowerControl field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-MaxTransPower
Indicates the maximum value of the UE's sidelink transmission power on this resource pool when the sidelink transmission is performed only on this resource pool. The unit is dBm. If the sidelink transmission is PSFCH, and multiple resource pools are used, the maximum transmission power for PSFCH is configured as sum of fields sl-maxTransPower over multiple resource pools, as specified in TS 38.101-1 [15]. | +| sl-Alpha-PSSCH-PSCCH
Indicates alpha value for sidelink pathloss based power control for PSCCH/PSSCH when sl-P0-PSSCH-PSCCH is configured. When the field is absent the UE applies the value 1. | +| sl-P0-PSSCH-PSCCH
Indicates P0 value for sidelink pathloss based power control for PSCCH/PSSCH. If not configured, sidelink pathloss based power control is disabled for PSCCH/PSSCH. When sl-P0-PSSCH-PSCCH-r17 is configured, the UE ignores sl-P0-PSSCH-PSCCH-r16 . | +| dl-Alpha-PSSCH-PSCCH
Indicates alpha value for downlink pathloss based power control for PSCCH/PSSCH when dl-P0-PSSCH-PSCCH is configured. When the field is absent the UE applies the value 1. | +| dl-P0-PSSCH-PSCCH
Indicates P0 value for downlink pathloss based power control for PSCCH/PSSCH. If not configured, downlink pathloss based power control is disabled for PSCCH/PSSCH. When dl-P0-PSSCH-PSCCH-r17 is configured, the UE ignores dl-P0-PSSCH-PSCCH-r16 .
A Remote UE which is out of coverage, considers downlink pathloss based power control is disabled for PSCCH/PSSCH when dl-P0-PSSCH-PSCCH is configured. | +| dl-Alpha-PSFCH
Indicates alpha value for downlink pathloss based power control for PSFCH when dl-P0-PSFCH is configured. When the field is absent the UE applies the value 1. For resource pools configured with PSFCH resources overlapping in time, this field is either not configured in any of the resource pools or configured with the same value for all the resource pools. | +| dl-P0-PSFCH
Indicates P0 value for downlink pathloss based power control for PSFCH. If not configured, downlink pathloss based power control is disabled for PSFCH. When dl-P0-PSFCH-r17 is configured, the UE ignores dl-P0-PSFCH-r16 . For resource pools configured with PSFCH resources overlapping in time, this field is either not configured in any of the resource pools or configured with the same value for all the resource pools.
A Remote UE which is out of coverage, considers downlink pathloss based power control is disabled for PSFCH when dl-P0-PSFCH is configured. | + +| SL-MinMaxMCS-Config field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-MaxMCS-PSSCH
Indicates the maximum MCS value when using the associated MCS table. If no MCS is configured, UE autonomously selects MCS from the full range of values. | +| sl-MinMCS-PSSCH
Indicates the minimum MCS value when using the associated MCS table. If no MCS is configured, UE autonomously selects MCS from the full range of values. | + +| SL-CPE-StartingPositionsPSCCH-PSSCH field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------| +| sl-Priority
Indicates L1 priority of PSSCH. | +| sl-CPE-StartingPositions
Indicates a set of candidate CPE starting positions specified in Table 5.3.1-3 [16, TS38.211], | + +#### SL-RLC-BearerConfig + +The IE *SL-RLC-BearerConfig* specifies the SL RLC bearer configuration information for NR sidelink communication. + +#### SL-RLC-BearerConfig information element + +``` +-- ASN1START +-- TAG-SL-RLC-BEARERCONFIG-START + +SL-RLC-BearerConfig-r16 ::= SEQUENCE { + sl-RLC-BearerConfigIndex-r16 SL-RLC-BearerConfigIndex-r16, + sl-ServedRadioBearer-r16 SLRB-Uu-ConfigIndex-r16 OPTIONAL, -- Cond LCH-SetupOnly + sl-RLC-Config-r16 SL-RLC-Config-r16 OPTIONAL, -- Cond LCH-Setup + sl-MAC-LogicalChannelConfig-r16 SL-LogicalChannelConfig-r16 OPTIONAL, -- Cond LCH-Setup + ... + [[ + sl-RLC-BearerConfigIndex-v1800 SL-RLC-BearerConfigIndex-v1800 OPTIONAL -- Need S + ]] +} + +-- TAG-SL-RLC-BEARERCONFIG-STOP +-- ASN1STOP +``` + +#### SL-RLC-BearerConfig field descriptions + +| | | +|-------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-MAC-LogicalChannelConfig | The field is used to configure MAC SL logical channel parameters. | +| sl-RLC-BearerConfigIndex | The index of the RLC bearer configuration. If the field sl-RLC-BearerConfigIndex-v1800 is present, the UE shall ignore the sl-RLC-BearerConfigIndex-r16 field. | +| sl-RLC-Config | Determines the RLC mode (UM, AM) and provides corresponding parameters. | +| sl-ServedRadioBearer | Associates the sidelink RLC Bearer with a sidelink DRB. It indicates the index of SL radio bearer configuration, which is corresponding to the RLC bearer configuration. | + +| Conditional Presence | Explanation | +|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| LCH-Setup | The field is mandatory present upon creation of a new sidelink logical channel via the dedicated signalling and in case of sidelink DRB configuration via system information and pre-configuration; otherwise the field is optionally present, Need M. | +| LCH-SetupOnly | This field is mandatory present upon creation of a new sidelink logical channel via the dedicated signalling and in case of sidelink DRB configuration via system information and pre-configuration. Otherwise, it is absent, Need M. | + +#### SL-RLC-BearerConfigIndex + +The IE *SL-RLC-BearerConfigIndex* is used to identify a SL RLC bearer configuration. + +#### SL-RLC-BearerConfigIndex information element + +``` +-- ASN1START +-- TAG-SL-RLC-BEARERCONFIGINDEX-START + +SL-RLC-BearerConfigIndex-r16 ::= + INTEGER (1..maxSL-LCID-r16) + +SL-RLC-BearerConfigIndex-r18 ::= + INTEGER (1..maxSL-LCID-r18) + +SL-RLC-BearerConfigIndex-v1800 ::= + INTEGER (maxSL-LCID-Plus1-r18..maxSL-LCID-r18) + +-- TAG-RLC-BEARERCONFIGINDEX-STOP +-- ASN1STOP +``` + +#### SL-RLC-ChannelConfig + +The IE *SL-RLC-ChannelConfig* specifies the configuration information for PC5 Relay RLC channel between L2 U2N Relay UE and L2 U2N Remote UE, or between L2 U2U Remote UE and L2 U2U Relay UE. + +#### SL-RLC-ChannelConfig information element + +``` +-- ASN1START +-- TAG-SL-RLC-CHANNEL-CONFIG-START + +SL-RLC-ChannelConfig-r17 ::= + SEQUENCE { + sl-RLC-ChannelID-r17 SL-RLC-ChannelID-r17, + sl-RLC-Config-r17 SL-RLC-Config-r16 OPTIONAL, -- Need M + sl-MAC-LogicalChannelConfig-r17 SL-LogicalChannelConfig-r16 OPTIONAL, -- Need M + sl-PacketDelayBudget-r17 INTEGER (0..1023) OPTIONAL, -- Need M + ... + } + +-- TAG-SL-RLC-CHANNEL-CONFIG-STOP +-- ASN1STOP +``` + +#### SL-RLC-ChannelConfig field descriptions + +| SL-RLC-ChannelConfig field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-MAC-LogicalChannelConfig
The field is used to configure MAC SL logical channel parameters. | +| sl-RLC-ChannelID
Indicates the PC5 Relay RLC channel in the link between L2 U2N Relay UE and L2 U2N Remote UE, or between L2 U2U Remote UE and L2 U2U Relay UE. | +| sl-RLC-Config
Determines the RLC mode (UM, AM) and provides corresponding parameters. | +| sl-PacketDelayBudget
Indicates the Packet Delay Budget for a PC5 Relay RLC channel used in L2 U2N relay operation. Upper bound value for the delay that a packet may experience expressed in unit of 0.5ms. | + +#### — *SL-RLC-ChannelID* + +The IE *SL-RLC-ChannelID* is used to identify a PC5 Relay RLC channel in the link between L2 U2N Relay UE and L2 U2N Remote UE, or between L2 U2U Relay UE and L2 U2U Remote UE. + +#### *SL-RLC-ChannelID* information element + +``` +-- ASN1START +-- TAG-SL-RLC-CHANNELID-START + +SL-RLC-ChannelID-r17 ::= INTEGER (1..maxSL-LCID-r16) + +-- TAG-SL-RLC-CHANNELID-STOP +-- ASN1STOP +``` + +#### — *SL-RLC-Config* + +The IE *SL-RLC-Config* is used to specify the RLC configuration of sidelink DRB. RLC AM configuration is only applicable to the unicast NR sidelink communication. + +#### *SL-RLC-Config* information element + +``` +-- ASN1START +-- TAG-SL-RLC-CONFIG-START + +SL-RLC-Config-r16 ::= + CHOICE { + sl-AM-RLC-r16 + SEQUENCE { + SN-FieldLengthAM + OPTIONAL, -- Cond SLRBSetup + T-PollRetransmit, + PollPDU, + PollByte, + ENUMERATED { t1, t2, t3, t4, t6, t8, t16, t32 }, + ... + }, + sl-UM-RLC-r16 + SEQUENCE { + SN-FieldLengthUM + OPTIONAL, -- Cond SLRBSetup + ... + }, + ... + } + +-- TAG-SL-RLC-CONFIG-STOP +-- ASN1STOP +``` + +| SL-RLC-Config field descriptions | | +|-----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-MaxRetxThreshold | Parameter value of maxRetxThreshold for RLC AM for NR sidelink communications, see TS 38.322 [4]. Value t1 corresponds to 1 retransmission, value t2 corresponds to 2 retransmissions and so on. | +| sl-PollByte | Parameter value of pollByte for RLC AM for NR sidelink communications, see TS 38.322 [4]. Value kB25 corresponds to 25 kBytes, value kB50 corresponds to 50 kBytes and so on. infinity corresponds to an infinite amount of kBytes. | +| sl-PollPDU | Parameter value of pollPDU for RLC AM for NR sidelink communications, see TS 38.322 [4]. Value p4 corresponds to 4 PDUs, value p8 corresponds to 8 PDUs and so on. infinity corresponds to an infinite number of PDUs. | +| sl-SN-FieldLength | This field indicates the RLC SN field size for NR sidelink communication, see TS 38.322 [4]. For groupcast and broadcast, only value size6 (6 bits) is configured for the field sl-SN-FieldLengthUM . | +| sl-T-PollRetransmit | Timer value of t-PollRetransmit for RLC AM for NR sidelink communications, see TS 38.322 [4], in milliseconds. Value ms5 means 5 ms, value ms10 means 10 ms and so on. | + +| Conditional Presence | Explanation | +|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SLRBSetup | The field is mandatory present in case of sidelink DRB setup via the dedicated signalling and in case of sidelink DRB configuration via system information and pre-configuration; otherwise the field is optionally present, need M. | + +#### SL-ScheduledConfig + +The IE *SL-ScheduledConfig* specifies sidelink communication/positioning configurations used for network scheduled NR sidelink communication/positioning. + +#### SL-ScheduledConfig information element + +``` +-- ASN1START +-- TAG-SL-SCHEDULEDCONFIG-START + +SL-ScheduledConfig-r16 ::= + SEQUENCE { + sl-RNTI-r16 RNTI-Value, + mac-MainConfigSL-r16 MAC-MainConfigSL-r16 + sl-CS-RNTI-r16 RNTI-Value OPTIONAL, -- Need M + sl-PSFCH-ToPUCCH-r16 SEQUENCE (SIZE (1..8)) OF INTEGER (0..15) OPTIONAL, -- Need M + sl-ConfiguredGrantConfigList-r16 SL-ConfiguredGrantConfigList-r16 OPTIONAL, -- Need M + ... + [[ + sl-DCI-ToSL-Trans-r16 SEQUENCE (SIZE (1..8)) OF INTEGER (1..32) OPTIONAL -- Need M + ]], + [[ + sl-ConfiguredGrantConfigDedicated-SL-PRS-RP-List-r18 SL-ConfiguredGrantConfigDedicated-SL-PRS-RP-List-r18 OPTIONAL -- Need M + ]] + } +} +``` + +``` + +MAC-MainConfigSL-r16 ::= SEQUENCE { + sl-BSR-Config-r16 BSR-Config OPTIONAL, -- Need M + ul-PrioritizationThres-r16 INTEGER (1..16) OPTIONAL, -- Need M + sl-PrioritizationThres-r16 INTEGER (1..8) OPTIONAL, -- Need M + ... +} + +SL-ConfiguredGrantConfigList-r16 ::= SEQUENCE { + sl-ConfiguredGrantConfigToReleaseList-r16 SEQUENCE (SIZE (1..maxNrofCG-SL-r16)) OF SL-ConfigIndexCG-r16 OPTIONAL, -- Need N + sl-ConfiguredGrantConfigToAddModList-r16 SEQUENCE (SIZE (1..maxNrofCG-SL-r16)) OF SL-ConfiguredGrantConfig-r16 OPTIONAL -- Need N +} + +SL-ConfiguredGrantConfigDedicated-SL-PRS-RP-List-r18 ::= SEQUENCE { + sl-ConfiguredGrantConfigDedicated-SL-PRS-RPToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofCG-SL-r16)) OF SL-ConfigIndexCG-r16 + OPTIONAL, -- Need N + sl-ConfiguredGrantConfigDedicated-SL-PRS-RPToAddModList-r18 + SEQUENCE (SIZE (1..maxNrofCG-SL-r16)) OF SL-ConfiguredGrantConfigDedicatedSL-PRS-RP-r18 + OPTIONAL -- Need N +} + +-- TAG-SL-SCHEDULEDCONFIG-STOP +-- ASN1STOP + +``` + +#### SL-ScheduledConfig field descriptions + +##### **sl-CS-RNTI** + +Indicate the RNTI used to scramble CRC of DCI format 3\_0, see TS 38.321 [3]. + +##### **sl-DCI-ToSL-Trans** + +Indicate the time gap between DCI reception and the first sidelink transmission scheduled by the DCI (see TS 38.214 [19], clause 8.1.2.1). Value 1 included in this field corresponds to 1 slot, value 2 corresponds to 2 slots and so on, based on the numerology of sidelink BWP. + +##### **sl-PSFCH-ToPUCCH** + +For dynamic grant and configured grant type 2, this field configures the values (in number of slot lengths) of the PSFCH to PUCCH gap. The field PSFCH-to-HARQ\_feedback timing indicator in DCI format 3\_0 selects one of the configured values of the PSFCH to PUCCH gap. + +##### **sl-RNTI** + +Indicate the SL-RNTI used for monitoring the network scheduling to transmit NR sidelink communication (i.e. the mode 1). + +#### MAC-MainConfigSL field descriptions + +##### **sl-BSR-Config** + +This field is to configure the sidelink buffer status report. + +##### **sl-PrioritizationThres** + +Indicates the SL priority threshold, which is used to determine whether SL TX is prioritized over UL TX, as specified in TS 38.321 [3]. Network does not configure the *sl-PrioritizationThres* and the *ul-PrioritizationThres* to the UE separately. + +##### **ul-PrioritizationThres** + +Indicates the UL priority threshold, which is used to determine whether SL TX is prioritized over UL TX, as specified in TS 38.321 [3]. Network does not configure the *sl-PrioritizationThres* and the *ul-PrioritizationThres* to the UE separately. + +#### SL-SDAP-Config + +The IE *SL-SDAP-Config* is used to set the configurable SDAP parameters for a Sidelink DRB. + +#### SL-SDAP-Config information element + +``` +-- ASN1START +-- TAG-SL-SDAP-CONFIG-START + +SL-SDAP-Config-r16 ::= SEQUENCE { + sl-SDAP-Header-r16 ENUMERATED {present, absent}, + sl-DefaultRB-r16 BOOLEAN, + sl-MappedQoS-Flows-r16 CHOICE { + sl-MappedQoS-FlowsList-r16 SEQUENCE (SIZE (1..maxNrofSL-QFIs-r16)) OF SL-QoS-Profile-r16, + sl-MappedQoS-FlowsListDedicated-r16 SL-MappedQoS-FlowsListDedicated-r16 + } OPTIONAL, -- Need M + sl-CastType-r16 ENUMERATED {broadcast, groupcast, unicast, spare1} OPTIONAL, -- Need M + ... +} + +SL-MappedQoS-FlowsListDedicated-r16 ::= SEQUENCE { + sl-MappedQoS-FlowsToAddList-r16 SEQUENCE (SIZE (1..maxNrofSL-QFIs-r16)) OF SL-QoS-FlowIdentity-r16 OPTIONAL, -- Need N + sl-MappedQoS-FlowsToReleaseList-r16 SEQUENCE (SIZE (1..maxNrofSL-QFIs-r16)) OF SL-QoS-FlowIdentity-r16 OPTIONAL -- Need N +} + +-- TAG-SL-SDAP-CONFIG-STOP +-- ASN1STOP +``` + +#### SL-SDAP-Config field descriptions + +| SL-SDAP-Config field descriptions | | +|-----------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-DefaultRB | Indicates whether or not this is the default sidelink DRB for this NR sidelink communication transmission destination. Among all configured instances of SL-SDAP-Config for this destination, this field shall be set to true in at most one instance of SL-SDAP-Config and to false in all other instances. | +| sl-MappedQoS-Flows | Indicates QoS flows to be mapped to the sidelink DRB. If the field is included in dedicated signalling, it is set to sl-MappedQoS-FlowsListDedicated ; otherwise, it is set to sl-MappedQoS-FlowsList . | +| sl-MappedQoS-FlowsList | Indicates the list of QoS profiles of the NR sidelink communication transmission destination mapped to this sidelink DRB. | +| sl-MappedQoS-FlowsToAddList | Indicates the list of SL QoS flows ID of the NR sidelink communication transmission destination to be additionally mapped to this sidelink DRB. | +| sl-MappedQoS-FlowsToReleaseList | Indicates the list of SL QoS flows ID of the NR sidelink communication transmission destination to be released from existing QoS flow to SLRB mapping of this sidelink DRB. | +| sl-SDAP-Header | Indicates whether or not a SDAP header is present on this sidelink DRB. The field cannot be changed after a sidelink DRB is established. This field is set to present if the field sl-DefaultRB is set to true . | + +#### — *SL-ServingCellInfo* + +The IE *SL-ServingCellInfo* is used to indicate the L2 U2N Relay UE's PCell/camping cell, which is considered as PCell/camping cell by the L2 U2N Remote UEs connecting with this L2 U2N Relay UE. + +#### *SL-ServingCellInfo* information element + +``` +-- ASN1START +-- TAG-SL-SERVINGCELLINFO-START + +SL-ServingCellInfo-r17 ::= SEQUENCE { + sl-PhysCellId-r17 PhysCellId, + sl-CarrierFreqNR-r17 ARFCN-ValueNR +} + +-- TAG-SL-SERVINGCELLINFO-STOP +-- ASN1STOP +``` + +#### *SL-ServingCellInfo* field descriptions + +| | +|----------------------------------------------------------------------------| +| sl-CarrierFreqNR | +| Indicates the DL frequency of the cell indicated by sl-PhysCellId . | +| sl-PhysCellId | +| Indicates the PCI of the PCell. | + +#### — *SL-SourceIdentity* + +The IE *SL-SourceIdentity* is used to identify a source of a NR sidelink communication. + +#### *SL-SourceIdentity* information element + +``` +-- ASN1START +-- TAG-SL-SOURCEIDENTITY-START + +SL-SourceIdentity-r17 ::= BIT STRING (SIZE (24)) + +-- TAG-SL-SOURCEIDENTITY-STOP +-- ASN1STOP +``` + +#### — *SL-SRAP-Config* + +The IE *SL-SRAP-Config* is used to set the configurable SRAP parameters used by L2 U2N Relay UE and L2 U2N Remote UE as specified in TS 38.351 [66]. + +#### **SL-SRAP-Config information element** + +``` + +-- ASN1START +-- TAG-SL-SRAP-CONFIG-START + +SL-SRAP-Config-r17 ::= + sl-LocalIdentity-r17 INTEGER (0..255) OPTIONAL, -- Need M + sl-MappingToAddModList-r17 SEQUENCE (SIZE (1..maxLC-ID)) OF SL-MappingToAddMod-r17 OPTIONAL, -- Need N + sl-MappingToReleaseList-r17 SEQUENCE (SIZE (1..maxLC-ID)) OF SL-RemoteUE-RB-Identity-r17 OPTIONAL, -- Need N + ... +} + +SL-MappingToAddMod-r17 ::= + sl-RemoteUE-RB-Identity-r17 SL-RemoteUE-RB-Identity-r17, + sl-EgressRLC-ChannelUu-r17 Uu-RelayRLC-ChannelID-r17 OPTIONAL, -- Cond L2RelayUE + sl-EgressRLC-ChannelPC5-r17 SL-RLC-ChannelID-r17 OPTIONAL, -- Need N + ... +} + +SL-RemoteUE-RB-Identity-r17 ::= + CHOICE { + srb-Identity-r17 INTEGER (0..3), + drb-Identity-r17 DRB-Identity, + ... + } + +-- TAG-SL-SRAP-CONFIG-STOP +-- ASN1STOP + +``` + +| SL-SRAP-Config field descriptions | | +|------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-LocalIdentity | Indicates the local UE ID of the L2 U2N Remote UE used in SRAP as specified in TS 38.351 [66]. | +| sl-MappingToAddModList | Indicates the list of mappings between the bearer identity of the L2 U2N Remote UE and the egress RLC channel as specified in TS 38.351 [66] to be added or modified. | +| sl-MappingToReleaseList | Indicates the list of mappings between the bearer identity of the L2 U2N Remote UE and the egress RLC channel as specified in TS 38.351 [66] to be released. | +| sl-RemoteUE-RB-Identity | Identity of the end-to-end Uu bearer identity of the L2 U2N Remote UE. The value 3 for the field srb-identity-r17 (i.e., for configuring SRB3) is not supported in this version of the specification. | +| sl-EgressRLC-ChannelUu | Indicates the egress RLC channel on Uu Hop for uplink transmissions at the L2 U2N Relay UE. | +| sl-EgressRLC-ChannelPC5 | Indicates the egress RLC channel on PC5 Hop for downlink transmissions at the L2 U2N Relay UE and for uplink transmissions at the L2 U2N Remote UE. | + +| Conditional Presence | Explanation | +|-----------------------------|----------------------------------------------------------------------------------------| +| L2RelayUE | For L2 U2N Relay UE, the field is optionally present, Need M. Otherwise, it is absent. | + +#### – *SL-SRAP-ConfigU2U* + +The IE *SL-SRAP-ConfigU2U* is used to set the configurable SRAP parameters used by L2 U2U Relay UE and L2 U2U Remote UE as specified in TS 38.351 [66]. + +#### *SL-SRAP-ConfigU2U* information element + +``` +-- ASN1START +-- TAG-SL-SRAP-CONFIGU2U-START + +SL-SRAP-ConfigU2U-r18 ::= + SEQUENCE { + sl-MappingToAddMod-U2U-List-r18 SEQUENCE (SIZE (1..maxSL-LCID-r16)) OF SL-MappingToAddMod-U2U-r18 OPTIONAL, -- Need N + sl-MappingToRelease-U2U-List-r18 SEQUENCE (SIZE (1..maxSL-LCID-r16)) OF SLRB-Uu-ConfigIndex-r16 OPTIONAL -- Need N + } + +SL-MappingToAddMod-U2U-r18 ::= + SEQUENCE { + sl-RemoteUE-SLRB-Identity-r18 SLRB-Uu-ConfigIndex-r16, + sl-EgressRLC-ChannelPC5-r18 SL-RLC-ChannelID-r17, + ... + } + +-- TAG-SL-SRAP-CONFIGU2U-STOP +-- ASN1STOP +``` + +#### *SL-SRAP-ConfigU2U* field descriptions + +| | | +|--------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-MappingToAddMod-U2U-List | Indicates the list of mappings between the end-to-end sidelink bearer of a given L2 U2U Remote UE and the egress PC5 Relay RLC channel used by L2 U2U Remote UE and L2 U2U Relay UE when acting as Tx UE, as specified in TS 38.351 [66] to be added or modified. | +| sl-MappingToRelease-U2U-List | Indicates the list of mappings the end-to-end sidelink bearer of a given L2 U2U Remote UE and the egress PC5 Relay RLC channel as specified in TS 38.351 [66] to be released, | +| sl-EgressRLC-ChannelPC5 | Indicates the egress PC5 Relay RLC channel for sidelink transmissions at the L2 U2U Relay UE and at the L2 U2U Remote UE. | +| sl-RemoteUE-SLRB-Identity | Identity of the end-to-end sidelink bearer identity of the L2 U2U Remote UE. | + +#### – *SL-SyncConfig* + +The IE *SL-SyncConfig* specifies the configuration information concerning reception of synchronisation signals from neighbouring cells as well as concerning the transmission of synchronisation signals for sidelink communication. + +#### **SL-SyncConfig information element** + +``` + +-- ASN1START +-- TAG-SL-SYNCCONFIG-START + +SL-SyncConfigList-r16 ::= SEQUENCE (SIZE (1..maxSL-SyncConfig-r16)) OF SL-SyncConfig-r16 + +SL-SyncConfig-r16 ::= SEQUENCE { + sl-SyncRefMinHyst-r16 ENUMERATED {dB0, dB3, dB6, dB9, dB12} OPTIONAL, -- Need R + sl-SyncRefDiffHyst-r16 ENUMERATED {dB0, dB3, dB6, dB9, dB12, dBinf} OPTIONAL, -- Need R + sl-filterCoefficient-r16 FilterCoefficient OPTIONAL, -- Need R + sl-SSB-TimeAllocation1-r16 SL-SSB-TimeAllocation-r16 OPTIONAL, -- Need R + sl-SSB-TimeAllocation2-r16 SL-SSB-TimeAllocation-r16 OPTIONAL, -- Need R + sl-SSB-TimeAllocation3-r16 SL-SSB-TimeAllocation-r16 OPTIONAL, -- Need R + sl-SSID-r16 INTEGER (0..671) OPTIONAL, -- Need R + txParameters-r16 SEQUENCE { + syncTxThreshIC-r16 SL-RSRP-Range-r16 OPTIONAL, -- Need R + syncTxThreshOoC-r16 SL-RSRP-Range-r16 OPTIONAL, -- Need R + syncInfoReserved-r16 BIT STRING (SIZE (2)) OPTIONAL, -- Need R + }, + gnss-Sync-r16 ENUMERATED {true} OPTIONAL, -- Need R + ... +} + +SL-RSRP-Range-r16 ::= INTEGER (0..13) + +SL-SSB-TimeAllocation-r16 ::= SEQUENCE { + sl-NumSSB-WithinPeriod-r16 ENUMERATED {n1, n2, n4, n8, n16, n32, n64} OPTIONAL, -- Need R + sl-TimeOffsetSSB-r16 INTEGER (0..1279) OPTIONAL, -- Need R + sl-TimeInterval-r16 INTEGER (0..639) OPTIONAL, -- Need R +} + +-- TAG-SL-SYNCCONFIG-STOP +-- ASN1STOP + +``` + +| SL-SyncConfig field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| gnss-Sync
If configured, the synchronization configuration is used for SLSS transmission/reception when the UE is synchronized to GNSS. If not configured, the synchronization configuration is used for SLSS transmission/reception when the UE is synchronized to eNB/gNB. | +| sl-SyncRefMinHyst
Hysteresis when evaluating a SyncRef UE using absolute comparison. | +| sl-SyncRefDiffHyst
Hysteresis when evaluating a SyncRef UE using relative comparison. | +| sl-NumSSB-WithinPeriod
Indicates the number of sidelink SSB transmissions within one sidelink SSB period. The applicable values are related to the subcarrier spacing and frequency as follows:
FR1, SCS = 15 kHz: 1
FR1, SCS = 30 kHz: 1, 2
FR1, SCS = 60 kHz: 1, 2, 4
FR2, SCS = 60 kHz: 1, 2, 4, 8, 16, 32
FR2, SCS = 120 kHz: 1, 2, 4, 8, 16, 32, 64
All values in sl-NumSSB-WithinPeriod in sl-SSB-TimeAllocation1 is set to be same across all carrier frequencies configured for UEs performing NR sidelink communication on multiple carrier frequencies, if configured. All values in sl-NumSSB-WithinPeriod in sl-SSB-TimeAllocation2 is set to be same across all carrier frequencies configured for UEs performing NR sidelink communication on multiple carrier frequencies, if configured. All values in sl-NumSSB-WithinPeriod in sl-SSB-TimeAllocation3 is set to be same across all carrier frequencies configured for UEs performing NR sidelink communication on multiple carrier frequencies, if configured. | +| sl-TimeOffsetSSB
Indicates the slot offset from the start of sidelink SSB period to the first sidelink SSB. All values in sl-TimeOffsetSSB in sl-SSB-TimeAllocation1 is set to be same across all carrier frequencies configured for UEs performing NR sidelink communication on multiple carrier frequencies, if configured. All values in sl-TimeOffsetSSB in sl-SSB-TimeAllocation2 is set to be same across all carrier frequencies configured for UEs performing NR sidelink communication on multiple carrier frequencies, if configured. All values in sl-TimeOffsetSSB in sl-SSB-TimeAllocation3 is set to be same across all carrier frequencies configured for UEs performing NR sidelink communication on multiple carrier frequencies, if configured. | +| sl-TimeInterval
Indicates the slot interval between neighboring sidelink SSBs. This value is applicable when there are more than one sidelink SSBs within one sidelink SSB period. All values in sl-TimeInterval in sl-SSB-TimeAllocation1 is set to be same across all carrier frequencies configured for UEs performing NR sidelink communication on multiple carrier frequencies, if configured. All values in sl-TimeInterval in sl-SSB-TimeAllocation2 is set to be same across all carrier frequencies configured for UEs performing NR sidelink communication on multiple carrier frequencies, if configured. All values in sl-TimeInterval in sl-SSB-TimeAllocation3 is set to be same across all carrier frequencies configured for UEs performing NR sidelink communication on multiple carrier frequencies, if configured. | +| sl-SSID
Indicates the ID of sidelink synchronization signal associated with different synchronization priorities. | +| syncInfoReserved
Reserved for future use. | +| syncTxThreshIC, syncTxThreshOoC
Indicates the thresholds used while in coverage and out of coverage, respectively. Value 0 corresponds to -infinity, value 1 to -115 dBm, value 2 to -110 dBm, and so on (i.e. in steps of 5 dBm) until value 12, which corresponds to -60 dBm, while value 13 corresponds to +infinity. | + +#### — *SL-Thres-RSRP-List* + +IE *SL-Thres-RSRP-List* indicates a threshold used for sensing based UE autonomous resource selection (see TS 38.215 [9]). A resource is excluded if it is indicated or reserved by a decoded SCI and PSSCH/PSCCH RSRP in the associated data resource is above the threshold defined by IE *SL-Thres-RSRP-List*. A NR sidelink resource is excluded if the corresponding PSFCH transmission occasions overlap with resources indicated or reserved by the decoded EUTRA SCI in time domain and EUTRA PSSCH RSRP in the associated data resource is above the threshold defined by IE *sl-NRPSFCH-EUTRA-ThresRSRP-List*. A NR sidelink resource is excluded if it is indicated or reserved by the decoded EUTRA SCI and EUTRA PSSCH RSRP in the associated data resource is above the threshold defined by IE *sl-NRPSSCH-EUTRA-ThresRSRP-List*. Value 0 corresponds to minus infinity dBm, value 1 corresponds to -128dBm, value 2 corresponds to -126dBm, value n corresponds to $(-128 + (n-1)*2)$ dBm and so on, value 66 corresponds to infinity dBm. + +#### *SL-Thres-RSRP-List* information element + +``` +-- ASN1START +-- TAG-SL-THRES-RSRP-LIST-START + +SL-Thres-RSRP-List-r16 ::= SEQUENCE (SIZE (64)) OF SL-Thres-RSRP-r16 +SL-Thres-RSRP-r16 ::= INTEGER (0..66) + +-- TAG-SL-THRES-RSRP-LIST-STOP +-- ASN1STOP +``` + +#### — *SL-TxPower* + +The IE *SL-TxPower* is used to limit the UE's sidelink transmission power on a carrier frequency. The unit is dBm. Value minusinfinity corresponds to $-\infty$ . + +#### *SL-TxPower* information element + +``` +-- ASN1START +-- TAG-SL-TXPOWER-START + +SL-TxPower-r16 ::= CHOICE{ + minusinfinity-r16 NULL, + txPower-r16 INTEGER (-30..33) +} + +-- TAG-SL-TXPOWER-STOP +-- ASN1STOP +``` + +#### — *SL-TypeTxSync* + +The IE *SL-TypeTxSync* indicates the synchronization reference type. + +#### **SL-TypeTxSync information element** + +``` + +-- ASN1START +-- TAG-SL-TYPETXSYNC-START + +SL-TypeTxSync-r16 ::= ENUMERATED {gnss, gnbEnb, ue} + +-- TAG-SL-TYPETXSYNC-STOP +-- ASN1STOP + +``` + +#### **SL-UE-SelectedConfig** + +IE *SL-UE-SelectedConfig* specifies sidelink communication configurations used for UE autonomous resource selection. + +#### **SL-UE-SelectedConfig information element** + +``` + +-- ASN1START +-- TAG-SL-UE-SELECTEDCONFIG-START + +SL-UE-SelectedConfig-r16 ::= SEQUENCE { + sl-PSSCH-TxConfigList-r16 OPTIONAL, -- Need R + sl-ProbResourceKeep-r16 ENUMERATED {v0, v0dot2, v0dot4, v0dot6, v0dot8} OPTIONAL, -- Need R + sl-ReselectAfter-r16 ENUMERATED {n1, n2, n3, n4, n5, n6, n7, n8, n9} OPTIONAL, -- Need R + sl-CBR-CommonTxConfigList-r16 OPTIONAL, -- Need R + ul-PrioritizationThres-r16 INTEGER (1..16) OPTIONAL, -- Need R + sl-PrioritizationThres-r16 INTEGER (1..8) OPTIONAL, -- Need R + ... +} + +-- TAG-SL-UE-SELECTEDCONFIG-STOP +-- ASN1STOP + +``` + +| SL-UE-SelectedConfig field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-PrioritizationThres
Indicates the SL priority threshold, which is used to determine whether SL TX is prioritized over UL TX, as specified in TS 38.321 [3]. Network does not configure the sl-PrioritizationThres and the ul-PrioritizationThres to the UE separately. | +| sl-ProbResourceKeep
Indicates the probability with which the UE keeps the current resource when the resource reselection counter reaches zero for sensing based UE autonomous resource selection (see TS 38.321 [3]). | +| sl-PSSCH-TxConfigList
Indicates PSSCH TX parameters such as MCS, sub-channel number, retransmission number, associated to different UE absolute speeds and different synchronization reference types for UE autonomous resource selection. | +| sl-ReselectAfter
Indicates the number of consecutive skipped transmissions before triggering resource reselection for sidelink communication (see TS 38.321 [3]). | +| ul-PrioritizationThres
Indicates the UL priority threshold, which is used to determine whether SL TX is prioritized over UL TX, as specified in TS 38.321 [3]. Network does not configure the sl-PrioritizationThres and the ul-PrioritizationThres to the UE separately. | + +#### — SL-ZoneConfig + +The IE *SL-ZoneConfig* is used to configure the zone ID related parameters. + +#### **SL-ZoneConfig information element** + +``` +-- ASN1START +-- TAG-SL-ZONECONFIG-START + +SL-ZoneConfig-r16 ::= SEQUENCE { + sl-ZoneLength-r16 ENUMERATED { m5, m10, m20, m30, m40, m50, spare2, spare1}, + ... +} + +-- TAG-SL-ZONECONFIG-STOP +-- ASN1STOP +``` + +| SL-ZoneConfig field descriptions | +|-----------------------------------------------------------------------| +| sl-ZoneLength
Indicates the length of each geographic zone. | + +#### — SLRB-Uu-ConfigIndex + +The IE *SLRB-Uu-ConfigIndex* is used to identify a sidelink DRB configuration from the network side. + +#### **SLRB-Uu-ConfigIndex information element** + +``` + +-- ASN1START +-- TAG-SLRB-UU-CONFIGINDEX-START + +SLRB-Uu-ConfigIndex-r16 ::= INTEGER (1..maxNrofSLRB-r16) + +-- TAG-SLRB-UU-CONFIGINDEX-STOP +-- ASN1STOP + +``` + +### 6.3.6 MBS information elements + +#### – *CarrierFreqListMBS* + +The IE *CarrierFreqListMBS* is used to inform network of the frequencies on which the UE is receiving or interested to receive MBS broadcast service via a broadcast MRB. + +#### **CarrierFreqListMBS information element** + +``` + +-- ASN1START +-- TAG-CARRIERFREQLISTMBS-START + +CarrierFreqListMBS-r17 ::= SEQUENCE (SIZE (1..maxFreqMBS-r17)) OF ARFCN-ValueNR + +-- TAG-CARRIERFREQLISTMBS-STOP +-- ASN1STOP + +``` + +#### – *CFR-ConfigMCCH-MTCH* + +The IE *CFR-ConfigMCCH-MTCH* is used to configure the common frequency resource used for MCCH and MTCH reception. + +#### **CFR-ConfigMCCH-MTCH information element** + +``` + +-- ASN1START +-- TAG-CFR-CONFIGMCCH-MTCH-START + +CFR-ConfigMCCH-MTCH-r17 ::= SEQUENCE { + locationAndBandwidthBroadcast-r17 LocationAndBandwidthBroadcast-r17 OPTIONAL, -- Need S + pdsch-ConfigMCCH-r17 PDSCH-ConfigBroadcast-r17 OPTIONAL, -- Need S + commonControlResourceSetExt-r17 ControlResourceSet OPTIONAL -- Cond NotSIB1CommonControlResource +} + +LocationAndBandwidthBroadcast-r17 ::= CHOICE { + sameAsSib1ConfiguredLocationAndBW NULL, + locationAndBandwidth INTEGER (0..37949) +} + +``` + +``` +-- TAG-CFR-CONFIGMCCH-MTCH-STOP +-- ASN1STOP +``` + +#### CFR-ConfigMCCH-MTCH field descriptions + +##### **commonControlResourceSetExt** + +An additional common control resource set which may be configured and used for *searchSpaceMCCH/searchSpaceMTCH* or UE-specific search space in the BWP where *searchSpaceMCCH* is configured. It is contained in the bandwidth of the CFR for broadcast and larger than CORESET#0. + +##### **locationAndBandwidthBroadcast** + +Indicates starting PRB and the number of PRBs of CFR used for MCCH and MTCH reception. + +Value *sameAsSib1ConfiguredLocationAndBW* means the CFR for broadcast has the same location and size as the *locationAndBandwidth* for initial BWP (for RedCap UEs: *initialDownlinkBWP-RedCap* if it is configured and includes CD-SSB and the entire CORESET#0) configured in *SIB1*. + +Value *locationAndBandwidth* is used to configure CFR with bandwidth that is larger than and fully contains the bandwidth for the initial DL BWP (for RedCap UEs: *initialDownlinkBWP-RedCap* if it is configured and includes CD-SSB and the entire CORESET#0) configured in *SIB1* and CORESET#0. The value of the field shall be interpreted as defined in TS 38.214 [19] with assumptions as described in TS 38.213 [13]. + +This field is not included in *cfr-ConfigMCCH-MTCH-RedCap* if *initialDownlinkBWP-RedCap* in *SIB1* is configured but does not include CD-SSB and the entire CORESET#0. If the field is absent, the CFR for broadcast has the same location and size as CORESET#0. + +##### **pdsch-ConfigMCCH** + +Indicates PDSCH parameters used for MCCH transmission. If the field is absent, PDSCH parameters used for MCCH are the same as those of PDSCH configuration provided in *initialDownlinkBWP* in *SIB1*. + +| Conditional Presence | Explanation | +|-------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------| +| NotSIB1CommonControlResource | The field is optional present in case commonControlResourceSet is not configured in SIB1 , Need R, otherwise it is absent. | + +##### DRX-ConfigPTM + +The IE *DRX-Config-PTM* is used to configure DRX related parameters for PTM transmission as specified in TS 38.321 [3]. + +##### DRX-Config-PTM information element + +``` +-- ASN1START +-- TAG-DRX-CONFIGPTM-START + +DRX-ConfigPTM-r17 ::= + SEQUENCE { + drx-onDurationTimerPTM-r17 CHOICE { + subMilliSeconds INTEGER (1..31), + milliSeconds ENUMERATED { + ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, + ms80, ms100, ms200, ms300, ms400, ms500, ms600, ms800, ms1000, ms1200, + ms1600, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 + } + }, + drx-InactivityTimerPTM-r17 ENUMERATED { +``` + +``` + ms0, ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, ms80, + ms100, ms200, ms300, ms500, ms750, ms1280, ms1920, ms2560, spare9, spare8, + spare7, spare6, spare5, spare4, spare3, spare2, spare1 + }, + drx-HARQ-RTT-TimerDL-PTM-r17 INTEGER (0..56) OPTIONAL, -- Cond HARQFeedback + drx-RetransmissionTimerDL-PTM-r17 ENUMERATED { + sl0, sl1, sl2, sl4, sl6, sl8, sl16, sl24, sl33, sl40, sl64, sl80, sl96, sl112, sl128, + sl160, sl320, spare15, spare14, spare13, spare12, spare11, spare10, spare9, + spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 + } + OPTIONAL, -- Cond HARQFeedback + drx-LongCycleStartOffsetPTM-r17 CHOICE { + ms10 INTEGER (0..9), + ms20 INTEGER (0..19), + ms32 INTEGER (0..31), + ms40 INTEGER (0..39), + ms60 INTEGER (0..59), + ms64 INTEGER (0..63), + ms70 INTEGER (0..69), + ms80 INTEGER (0..79), + ms128 INTEGER (0..127), + ms160 INTEGER (0..159), + ms256 INTEGER (0..255), + ms320 INTEGER (0..319), + ms512 INTEGER (0..511), + ms640 INTEGER (0..639), + ms1024 INTEGER (0..1023), + ms1280 INTEGER (0..1279), + ms2048 INTEGER (0..2047), + ms2560 INTEGER (0..2559), + ms5120 INTEGER (0..5119), + ms10240 INTEGER (0..10239) + }, + drx-SlotOffsetPTM-r17 INTEGER (0..31) +} + +-- TAG-DRX-CONFIGPTM-STOP +-- ASN1STOP +``` + +| DRX-Config-PTM field descriptions | | +|------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| drx-HARQ-RTT-Timer-DL-PTM | Value in number of symbols of the CFR where the transport block was received. | +| drx-InactivityTimerPTM | Value in multiple integers of 1 ms. ms0 corresponds to 0, ms1 corresponds to 1 ms, ms2 corresponds to 2 ms, and so on. | +| drx-LongCycleStartOffsetPTM | drx-LongCycle-PTM in ms and drx-StartOffset-PTM in multiples of 1 ms. | +| drx-onDurationTimerPTM | Value in multiples of 1/32 ms (subMilliSeconds) or in ms (milliSecond). For the latter, value ms1 corresponds to 1 ms, value ms2 corresponds to 2 ms, and so on. | +| drx-RetransmissionTimer-DL-PTM | Value in number of slot lengths of the CFR where the transport block was received. value s/0 corresponds to 0 slots, s/1 corresponds to 1 slot, s/2 corresponds to 2 slots, and so on. | +| drx-SlotOffsetPTM | Value in 1/32 ms. Value 0 corresponds to 0 ms, value 1 corresponds to 1/32 ms, value 2 corresponds to 2/32 ms, and so on. | + +| Conditional Presence | Explanation | +|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| HARQFeedback | The field is mandatory present if HARQ feedback is enabled for a G-RNTI/G-CS-RNTI associated with this DRX configuration. The field is optionally present if the IE DRX-ConfigPTM is included in MBSMulticastConfiguration , need R. It is optionally present. Need R, otherwise. | + +#### — *MBS-NeighbourCellList* + +The IE *MBS-NeighbourCellList* indicates a list of neighbour cells where ongoing MBS sessions provided via broadcast MRB in the current cell may also be provided, as indicated in the *mtch-NeighbourCell*. + +#### ***MBS-NeighbourCellList* information element** + +``` +-- ASN1START +-- TAG-MBS-NEIGHBOURCELLIST-START + +MBS-NeighbourCellList-r17 ::= SEQUENCE (SIZE (0..maxNeighCellMBS-r17)) OF MBS-NeighbourCell-r17 + +MBS-NeighbourCell-r17 ::= SEQUENCE { + physCellId-r17 PhysCellId, + carrierFreq-r17 ARFCN-ValueNR OPTIONAL -- Need S +} + +-- TAG-MBS-NEIGHBOURCELLIST-STOP +-- ASN1STOP +``` + +#### **MBS-NeighbourCellList field descriptions** + +##### **carrierFreq** + +Indicates the frequency of the neighbour cell indicated by *physCellId*. Absence of the IE means that the neighbour cell is on the same frequency as the current cell. + +#### — *MBS-NonServingInfoList* + +The IE *MBS-NonServingInfoList* is used to inform network of the frequencies, CFR information and subcarrier spacing for MBS broadcast reception on the non-serving cell. + +#### ***MBS-NonServingInfoList* information element** + +``` +-- ASN1START +-- TAG-MBS-NONSERVINGINFOLIST-START + +MBS-NonServingInfoList-r18 ::= SEQUENCE (SIZE (1..maxFreqMBS-r17)) OF NonServingInfo-r18 + +NonServingInfo-r18 ::= SEQUENCE { + freqInfoMBS-r18 FreqInfoMBS-r18 OPTIONAL, + cfr-InfoMBS-r18 CHOICE { + cfr-Bandwidth-r18 INTEGER (1..maxNrofPhysicalResourceBlocks), + cfr-LocationAndBW-r18 CFR-LocationAndBW-r18 + } + subcarrierSpacing-r18 SubcarrierSpacing OPTIONAL, +} OPTIONAL + +FreqInfoMBS-r18 ::= SEQUENCE { + carrierFreqMBS-r18 ARFCN-ValueNR, + freqBandIndicatorMBS-r18 FreqBandIndicatorNR +} + +CFR-LocationAndBW-r18 ::= SEQUENCE { + locationAndBandwidthMBS-r18 INTEGER (0..37949) OPTIONAL, + absoluteFrequencyPointA-MBS-r18 ARFCN-ValueNR OPTIONAL, + offsetToCarrierMBS-r18 INTEGER (0..2199) OPTIONAL +} + +-- TAG-MBS-NONSERVINGINFOLIST-STOP +-- ASN1STOP +``` + +| MBS-NonServingInfoList field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| freqInfoMBS
Indicates MBS frequency of interest and the frequency band of the non-serving cell for MBS broadcast reception acquired from the SIB21 or the USD as specified in clause 5.9.4.3. | +| cfr-infoMBS
Indicates the CFR information of the non-serving cell for MBS broadcast reception. | +| cfr-BandwidthMBS
Indicates the CFR bandwidth of the non-serving cell for MBS broadcast reception. | +| cfr-LocationAndBW
Indicates the CFR location and bandwidth of the non-serving cell for MBS broadcast reception. | +| subcarrierSpacing
Indicates the subcarrier spacing of the CORESET#0 of the non-serving cell for MBS broadcast reception. | + +| CFR-LocationAndBW field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| locationAndBandwidthMBS
Indicates the starting PRB and the number of PRBs of CFR used for MBS broadcast reception from non-serving cell. The value of the field shall be interpreted as resource indicator value (RIV) as defined TS 38.214 [19] with assumptions as described in TS 38.213 [13]. The first PRB is a PRB determined by subcarrierSpacing , offsetToCarrierMBS and absoluteFrequencyPointA-MBS of the non-serving cell. | +| absoluteFrequencyPointA-MBS
Indicates the absolute frequency position of the reference resource block (Common RB 0) of the non-serving cell for MBS broadcast reception. Its lowest subcarrier is also known as Point A (see TS 38.211 [16], clause 4.4.4.2). | +| offsetToCarrierMBS
Indicates the 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 subcarrierSpacing indicated for the non-serving cell). | + +#### — ***MBS-ServiceList*** + +The IE *MBS-ServiceList* is used to inform the network of the MBS services that the UE is receiving or interested to receive. + +#### ***MBS-ServiceList* information element** + +``` +-- ASN1START +-- TAG-MBS-SERVICELIST-START + +MBS-ServiceList-r17 := SEQUENCE (SIZE (1..maxNrofMBS-ServiceListPerUE-r17)) OF MBS-ServiceInfo-r17 + +MBS-ServiceInfo-r17 := SEQUENCE { + tmgi-r17 TMGI-r17 +} + +-- TAG-MBS-SERVICELIST-STOP +-- ASN1STOP +``` + +#### – *MBS-SessionInfoList* + +The IE *MBS-SessionInfoList* provides the list of ongoing MBS broadcast sessions transmitted via broadcast MRB and, for each MBS broadcast session, the associated G-RNTI and scheduling information. + +##### *MBS-SessionInfoList* information element + +``` +-- ASN1START +-- TAG-MBS-SESSIONINFOLIST-START + +MBS-SessionInfoList-r17 ::= SEQUENCE (SIZE (1..maxNrofMBS-Session-r17)) OF MBS-SessionInfo-r17 + +MBS-SessionInfo-r17 ::= SEQUENCE { + mbs-SessionId-r17 TMGI-r17, + g-RNTI-r17 RNTI-Value, + mrb-ListBroadcast-r17 MRB-ListBroadcast-r17, + mtch-SchedulingInfo-r17 DRX-ConfigPTM-Index-r17 OPTIONAL, -- Need S + mtch-NeighbourCell-r17 BIT STRING (SIZE (maxNeighCellMBS-r17)) OPTIONAL, -- Need S + pdsch-ConfigIndex-r17 PDSCH-ConfigIndex-r17 OPTIONAL, -- Need S + mtch-SSB-MappingWindowIndex-r17 MTCH-SSB-MappingWindowIndex-r17 OPTIONAL -- Cond MTCH-Mapping +} + +DRX-ConfigPTM-Index-r17 ::= INTEGER (0..maxNrofDRX-ConfigPTM-1-r17) + +PDSCH-ConfigIndex-r17 ::= INTEGER (0..maxNrofPDSCH-ConfigPTM-1-r17) + +MTCH-SSB-MappingWindowIndex-r17 ::= INTEGER (0..maxNrofMTCH-SSB-MappingWindow-1-r17) + +MRB-ListBroadcast-r17 ::= SEQUENCE (SIZE (1..maxNrofMRB-Broadcast-r17)) OF MRB-InfoBroadcast-r17 + +MRB-InfoBroadcast-r17 ::= SEQUENCE { + pdcp-Config-r17 MRB-PDCP-ConfigBroadcast-r17, + rlc-Config-r17 MRB-RLC-ConfigBroadcast-r17, + ... +} + +MRB-PDCP-ConfigBroadcast-r17 ::= SEQUENCE { + pdcp-SN-SizeDL-r17 ENUMERATED {len12bits} OPTIONAL, -- Need S + headerCompression-r17 CHOICE { + notUsed NULL, + rohc SEQUENCE { + maxCID-r17 INTEGER (1..16) DEFAULT 15, + profiles-r17 SEQUENCE { + profile0x0000-r17 BOOLEAN, + profile0x0001-r17 BOOLEAN, + profile0x0002-r17 BOOLEAN + } + } + }, + t-Reordering-r17 ENUMERATED {ms1, ms10, ms40, ms160, ms500, ms1000, ms1250, ms2750} OPTIONAL -- Need S +} +``` + +``` + +MRB-RLC-ConfigBroadcast-r17 ::= SEQUENCE { + logicalChannelIdentity-r17 LogicalChannelIdentity, + sn-FieldLength-r17 ENUMERATED {size6} OPTIONAL, -- Need S + t-Reassembly-r17 T-Reassembly OPTIONAL -- Need S +} + +-- TAG-MBS-SESSIONINFOLIST-STOP +-- ASN1STOP + +``` + +| MBS-SessionInfoList field descriptions | | +|-----------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| g-RNTI | G-RNTI used to scramble the scheduling and transmission of MTCH. | +| headerCompression | If rohc is configured, the UE shall apply the configured ROHC profile(s) in downlink. | +| mbs-SessionId | Indicates an identifier of the MBS session provided by the MTCH. | +| mrb-listBroadcast | A list of broadcast MRBs to which the associated broadcast MBS session is mapped to. | +| mtch-neighbourCell | Indicates neighbour cells which provide this service on MTCH. The first bit is set to 1 if the service is provided on MTCH in the first cell in mbs-NeighbourCellList , otherwise it is set to 0. The second bit is set to 1 if the service is provided on MTCH in the second cell in mbs-NeighbourCellList , and so on. If the service is not available in any neighbouring cell and mbs-NeighbourCellList is signalled, the network sets all bits in this field to 0. The field is absent when mbs-NeighbourCellList is absent or an empty mbs-NeighbourCellList is signalled. If this field is absent when mbs-NeighbourCellList is absent or a non-empty mbs-NeighbourCellList is signalled, the related service may or may not be available in any neighbouring cell, i.e. the UE cannot determine the presence or absence of an MBS service in neighbouring cells based on the absence of this field. If this field is absent and an empty mbs-NeighbourCellList is signalled, then the UE shall assume that MBS broadcast services signalled in mbs-SessionInfoList in the MBSBroadcastConfiguration message are not provided in any neighbour cell. | +| mtch-schedulingInfo | Indicates the index of DRX configuration entry in drx-ConfigPTM-List that is used for scheduling the MTCH. The value 0 corresponds to the first entry in drx-ConfigPTM-List , the value 1 corresponds to the second entry in drx-ConfigPTM-List and so on. In case mtch-schedulingInfo is absent for a G-RNTI (i.e. no PTM DRX), the UE shall monitor for PDCCH scrambled with G-RNTI in any slot according to the search space configured for MTCH [see TS 38.213 [13], clause 10.1]. | +| mtch-SSB-MappingWindowIndex | Indicates the index of MTCH-SSB-MappingWindowCycleOffset configuration entry in MTCH-SSB-MappingWindowList . The value 0 corresponds to the first entry in MTCH-SSB-MappingWindowList , the value 1 corresponds to the second entry in MTCH-SSB-MappingWindowList and so on. This field is set to the same value for all MBS sessions mapped to the same G-RNTI. | +| pdcp-SN-SizeDL | Indicates that PDCP sequence number size of 12 bits is used, as specified in TS 38.323 [5]. When the field is absent the UE applies the value as specified in 9.1.1.7. | +| pdschConfigIndex | Indicates the index of PDSCH configuration entry in pdschConfigList for MTCH. Value 0 corresponds to the first entry in pdschConfigList , the value 1 corresponds to the second entry in pdschConfigList and so on. When the field is absent the UE applies the first entry in pdschConfigList for MTCH. | +| sn-FieldLength | Indicates that the RLC SN field size of 6 bits is used, see TS 38.322 [4]. When the field is absent the UE applies the value as specified in 9.1.1.7. | +| t-Reassembly | Timer for reassembly in TS 38.322 [4], in milliseconds. Value ms0 means 0 ms, value ms5 means 5 ms and so on. When the field is absent the UE applies the value in specified in 9.1.1.7. | +| t-Reordering | Value in ms of t-Reordering specified in TS 38.323 [5]. Value ms1 corresponds to 1 ms, value ms10 corresponds to 10 ms, and so on. When the field is absent the UE applies the value as specified in 9.1.1.7. | + +| Conditional Presence | Explanation | +|-----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MTCH-Mapping | The field is mandatory present if the number of actual transmitted SSBs determined according to ssb-PositionsInBurst in SIB1 is more than 1, and searchSpaceMTCH is not set to zero (including the case where searchSpaceMTCH is absent and searchSpaceMCCH is not set to zero). Otherwise, it is absent, Need R. | + +#### – *MBS-SessionInfoListMulticast* + +The IE *MBS-SessionInfoListMulticast* provides a list of MBS multicast sessions transmitted via multicast MRB for RRC\_INACTIVE UEs and, for each MBS multicast session, the associated G-RNTI and scheduling information. + +##### ***MBS-SessionInfoListMulticast* information element** + +``` +-- ASN1START +-- TAG-MBS-SESSIONINFOLISTMULTICAST-START + +MBS-SessionInfoListMulticast-r18 ::= SEQUENCE (SIZE (1..maxNrofMBS-Session-r17)) OF MBS-SessionInfoMulticast-r18 + +MBS-SessionInfoMulticast-r18 ::= SEQUENCE { + mbs-SessionId-r18 TMGI-r17, + g-RNTI-r18 RNTI-Value, + mrb-ListMulticast-r18 MRB-ListMulticast-r18, + mtch-SchedulingInfo-r18 DRX-ConfigPTM-Index-r17, + mtch-NeighbourCell-r18 BIT STRING (SIZE (maxNeighCellMBS-r17)), + pdsch-ConfigIndex-r18 PDSCH-ConfigIndex-r17, + mtch-SSB-MappingWindowIndex-r18 MTCH-SSB-MappingWindowIndex-r17, + thresholdIndex-r18 INTEGER (0..maxNrofThresholdMBS-r18), + pdcp-SYNC-Indicator-r18 ENUMERATED {true}, + stopMonitoringRNTI-r18 ENUMERATED {true} +} + +MRB-ListMulticast-r18 ::= SEQUENCE (SIZE (1.. maxMRB-r17)) OF MRB-InfoMulticast-r18 + +MRB-InfoMulticast-r18 ::= SEQUENCE { + pdcp-Config-r18 MRB-PDCP-ConfigMulticast-r18, + rlc-Config-r18 MRB-RLC-ConfigMulticast-r18, + ... +} + +MRB-PDCP-ConfigMulticast-r18 ::= SEQUENCE { + pdcp-SN-SizeDL-r18 ENUMERATED {len12bits, len18bits}, + headerCompression-r18 CHOICE { + notUsed NULL, + rohc SEQUENCE { + maxCID-r18 INTEGER (1..16) DEFAULT 15, + profiles-r18 SEQUENCE { + profile0x0000-r18 BOOLEAN, + profile0x0001-r18 BOOLEAN, + profile0x0002-r18 BOOLEAN + } + } + }, + t-Reordering-r17 ENUMERATED {ms1, ms10, ms40, ms160, ms500, ms1000, ms1250, ms2750} OPTIONAL -- Need R +} + +MRB-RLC-ConfigMulticast-r18 ::= SEQUENCE { + logicalChannelIdentity-r18 CHOICE { +``` + +``` + + logicalChannelIdentitymulticast-r18 LogicalChannelIdentity, + logicalChannelIdentityExt-r18 LogicalChannelIdentityExt-r17 + }, + sn-FieldLength-r18 ENUMERATED {size6, size12}, + t-Reassembly-r18 T-Reassembly OPTIONAL -- Need R +} + +-- TAG-MBS-SESSIONINFOLISTMULTICAST-STOP +-- ASN1STOP + +``` + +| MBS-SessionInfoListMulticast field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| g-RNTI
G-RNTI used to scramble the scheduling and transmission of multicast MTCH. | +| mbs-SessionId
Indicates an identifier of the MBS session to be received by the UE in RRC_INACTIVE. | +| mrB-listMulticast
A list of multicast MRBs to which the associated MBS multicast session is mapped to. | +| mtch-neighbourCell
Indicates neighbour cells which provide this service on MTCH for RRC_INACTIVE. The first bit is set to 1 if the service is provided on MTCH in the first cell in mbs-NeighbourCellList , otherwise it is set to 0. The second bit is set to 1 if the service is provided on MTCH in the second cell in mbs-NeighbourCellList , and so on. If the service is not available in any neighbouring cell and mbs-NeighbourCellList is signalled, the network sets all bits in this field to 0. The field is absent when mbs-NeighbourCellList is absent or an empty mbs-NeighbourCellList is signalled. If this field is absent when mbs-NeighbourCellList is absent or a non-empty mbs-NeighbourCellList is signalled, the related service may or may not be available in any neighbouring cell, i.e. the UE cannot determine the presence or absence of an MBS service in neighbouring cells based on the absence of this field. If this field is absent and an empty mbs-NeighbourCellList is signalled, then the UE shall assume that MBS multicast services signalled in mbs-SessionInfoListMulticast in the MBSMulticastConfiguration message are not provided in any neighbour cell. | +| mtch-schedulingInfo
Indicates the index of DRX configuration entry in drx-ConfigPTM-List that is used for scheduling the MTCH. The value 0 corresponds to the first entry in drx-ConfigPTM-List , the value 1 corresponds to the second entry in drx-ConfigPTM-List and so on. In case mtch-schedulingInfo is absent for a G-RNTI (i.e. no PTM DRX), the UE shall monitor for PDCCH scrambled with G-RNTI in any slot according to the search space configured for MTCH. | +| mtch-SSB-MappingWindowIndex
Indicates the index of MTCH-SSB-MappingWindowCycleOffset configuration entry in MTCH-SSB-MappingWindowList . The value 0 corresponds to the first entry in MTCH-SSB-MappingWindowList , the value 1 corresponds to the second entry in MTCH-SSB-MappingWindowList and so on. This field is set to the same value for all MBS sessions mapped to the same G-RNTI. | +| pdcP-SN-SizeDL
Indicates PDCP sequence number size of 12 or 18 bits, as specified in TS 38.323 [5]. | +| pdschConfigIndex
Indicates the index of PDSCH configuration entry in pdschConfigList for MTCH. Value 0 corresponds to the first entry in pdschConfigList , the value 1 corresponds to the second entry in pdschConfigList and so on. When the field is absent the UE applies the first entry in pdschConfigList for MTCH. | +| pdcP-SYNC-indicator
Indicates the PDCP COUNT of the corresponding multicast session is synchronized in the RNA, i.e. the cells in the RNA follow a common QoS flow to MRB mapping rule and at the same time PDCP COUNT is set according to the MBS QoS Flow SN. | +| sn-FieldLength
Indicates RLC SN field size of 6 or 12 bits, as specified in TS 38.322 [4]. | +| stopMonitoringRNTI
Indicates the UE to stop monitoring the G-RNTI for the corresponding multicast session. | +| t-Reassembly
Timer for reassembly in TS 38.322 [4], in milliseconds. Value ms0 means 0 ms, value ms5 means 5 ms and so on. | +| t-Reordering
Value in ms of t-Reordering specified in TS 38.323 [5]. Value ms1 corresponds to 1 ms, value ms10 corresponds to 10 ms, and so on. | +| thresholdIndex
Indicates the index of thresholdMBS entry in thresholdMBS-List that is used for RRC connection resume for a UE receiving the corresponding multicast session in RRC_INACTIVE. Value 0 corresponds to the first entry in thresholdMBS-List , the value 1 corresponds to the second entry in thresholdMBS-List and so on. | + +| Conditional Presence | Explanation | +|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MTCH-Mapping | The field is mandatory present if the number of actual transmitted SSBs determined according to ssb-PositionsInBurst in SIB1 is more than 1, and searchSpaceMulticastMTCH is not set to zero (including the case where searchSpaceMulticastMTCH is absent and searchSpaceMulticastMCCH is not set to zero). Otherwise, it is absent, Need R. | +| RRRelease | The field is optionally present if MBS-SessionInfoListMulticast is included in RRRelease message. Otherwise, it is absent. | + +#### – *MTCH-SSB-MappingWindowList* + +The IE *MTCH-SSB-MappingWindowList* is used to configure MTCH PDCCH occasions to SSB mapping window related periodic and offset parameters. + +#### *MTCH-SSB-MappingWindowList* information element + +``` +-- ASN1START +-- TAG-MTCH-SSB-MAPPINGWINDOWLIST-START + +MTCH-SSB-MappingWindowList-r17 ::= SEQUENCE (SIZE (1..maxNrofMTCH-SSB-MappingWindow-r17)) OF MTCH-SSB-MappingWindowCycleOffset-r17 + +MTCH-SSB-MappingWindowCycleOffset-r17 ::= CHOICE { + ms10 INTEGER (0..9), + ms20 INTEGER (0..19), + ms32 INTEGER (0..31), + ms64 INTEGER (0..63), + ms128 INTEGER (0..127), + ms256 INTEGER (0..255) +} + +-- TAG-MTCH-SSB-MAPPINGWINDOWLIST-STOP +-- ASN1STOP +``` + +| MTCH-SSB-MappingWindowList field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

MTCH-SSB-MappingWindowCycleOffset
Indicates the cycle and offset for MTCH PDCCH occasions to SSB mapping. Values in unit of ms. ms10 corresponds to cycle of 10 ms with corresponding offset between 0 and 9 ms, value ms20 corresponds to cycle of 20 ms with corresponding offset between 0 and 19 ms, and so on. The mapping window starts at a subframe in a SFN where [(\text{SFN number} \times 10) + \text{subframe number}] \bmod (\text{cycle}) = \text{offset}.
PDCCH monitoring occasions for MTCH in a mapping window which are not overlapping with UL symbols (determined according to tdd-UL-DL-ConfigurationCommon) are sequentially numbered starting from 1 in the mapping window. The [x \times N + K]^{\text{th}} PDCCH monitoring occasion for MTCH in this mapping window corresponds to the K^{\text{th}} transmitted SSB, where x = 0, 1, \dots, X-1, K = 1, 2, \dots, N, N is the number of actual transmitted SSBs determined according to ssb-PositionsInBurst in SIB1 and X is equal to \text{CEIL}(\text{number of PDCCH monitoring occasions in MTCH to SSB mapping transmission window}/N). The actual transmitted SSBs are sequentially numbered from one in ascending order of their SSB indexes.

| + +#### – *PDSCH-ConfigBroadcast* + +The IE *PDSCH-ConfigBroadcast* is used to configure parameters for acquiring the PDSCH for MCCH and MTCH. + +#### PDSCH-ConfigBroadcast information element + +``` + +-- ASN1START +-- TAG-PDSCH-CONFIGBROADCAST-START + +PDSCH-ConfigBroadcast-r17 ::= SEQUENCE { + pdschConfigList-r17 SEQUENCE (SIZE (1..maxNrofPDSCH-ConfigPTM-r17) ) OF PDSCH-ConfigPTM-r17, + pdsch-TimeDomainAllocationList-r17 PDSCH-TimeDomainResourceAllocationList-r16 OPTIONAL, -- Need R + rateMatchPatternToAddModList-r17 SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF RateMatchPattern OPTIONAL, -- Need R + lte-CRS-ToMatchAround-r17 RateMatchPatternLTE-CRS OPTIONAL, -- Need R + mcs-Table-r17 ENUMERATED {gam256, gam64LowSE} OPTIONAL, -- Need S + xOverhead-r17 ENUMERATED {xOh6, xOh12, xOh18} OPTIONAL, -- Need S +} + +PDSCH-ConfigPTM-r17 ::= SEQUENCE { + dataScramblingIdentityPDSCH-r17 INTEGER (0..1023) OPTIONAL, -- Need S + dmrs-ScramblingID0-r17 INTEGER (0..65535) OPTIONAL, -- Need S + pdsch-AggregationFactor-r17 ENUMERATED {n2, n4, n8} OPTIONAL -- Need S +} + +-- TAG-PDSCH-CONFIGBROADCAST-STOP +-- ASN1STOP + +``` + +#### PDSCH-ConfigBroadcast field descriptions + +| | | +|----------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| lte-CRS-ToMatchAround | Parameters to determine an LTE CRS pattern that the UE shall rate match around. | +| pdschConfigList | List of PDSCH parameters which can be configured per G-RNTI. Only one entity is allowed to be configured if included in SIB20. | +| pdsch-TimeDomainAllocationList | List of time-domain configurations for timing of DL assignment to DL data.
The field pdsch-TimeDomainAllocationList applies to DCI format 4_0 (see table 5.1.2.1.1-1 in TS 38.214 [19]). When the field is absent, the UE follows PDSCH time domain resource allocation determination rule as specified in TS 38.214 [19], clause 5.1.2.1.1. | +| rateMatchPatternToAddModList | Resources patterns which the UE should rate match PDSCH around. The UE rate matches around the union of all resources indicated in the rate match patterns (see TS 38.214 [19], clause 5.1.4.1). | +| mcs-Table | Indicates which MCS table the UE shall use for PDSCH. If the field is absent the UE applies the value 64QAM. The field mcs-Table applies to DCI format 4_0 with CRC scrambled by MCCH-RNTI/G-RNTI (see TS 38.214 [19], clause 5.1.3.1). | +| xOverhead | Accounts for an overhead from CSI-RS, CORESET, etc. If the field is absent, the UE applies value xOh0 (see TS 38.214 [19], clause 5.1.3.2). | + +| PDSCH-ConfigPTM field descriptions | | +|-------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| dataScramblingIdentityPDSCH | Identifier(s) used to initialize data scrambling ( c_init ) for PDSCH as specified in TS 38.211 [16], clause 7.3.1.1. When the field is absent the UE applies the value physCellId configured for this serving cell. | +| dmrs-ScramblingID0 | DL DMRS scrambling initialization (see TS 38.211 [16], clause 7.4.1.1.1). When the field is absent the UE applies the value physCellId configured for this serving cell. | +| pdsch-AggregationFactor | Number of repetitions for dynamic scheduling of MBS broadcast data for MTCH PDSCH (see TS 38.214 [19], clause 5.1.2.1). When the field is absent the UE applies the value 1. | + +#### — ***TMGI*** + +The IE *TMGI* is used to identify the MBS session. + +##### ***TMGI* information element** + +``` +-- ASN1START +-- TAG-TMGI-START + +TMGI-r17 ::= + SEQUENCE { + plmn-Id-r17 CHOICE { + plmn-Index INTEGER (1..maxPLMN), + explicitValue PLMN-Identity + }, + serviceId-r17 OCTET STRING (SIZE (3)) + } + +-- TAG-TMGI-STOP +-- ASN1STOP +``` + +| TMGI field descriptions | | +|---------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| plmn-Index | PLMN index or NPN index according to the plmn-IdentityInfoList and npn-IdentityInfoList fields included in SIB1 . If this field is included in the MRB-ToAddMod-r17 , the UE translates the plmn-Index into the PLMN Identity or SNPN Identity based on the configuration in SIB1 (which is the SIB1 of the target cell in case of handover). The explicitValue is not used for MBS service(s) of an SNPN. | +| serviceId | Uniquely identifies the identity of an MBS service within a PLMN. The field contains octet 3- 5 of the IE Temporary Mobile Group Identity (TMGI) as defined in TS 24.008 [38]. The first octet contains the third octet of the TMGI, the second octet contains the fourth octet of the TMGI and so on. | + +## 6.4 RRC multiplicity and type constraint values + +### – Multiplicity and type constraint definitions + +``` +-- ASN1START +-- TAG-MULTIPLICITY-AND-TYPE-CONSTRAINT-DEFINITIONS-START + +maxAdditionalRACH-r17 INTEGER ::= 256 -- Maximum number of additional RACH configurations. +maxAI-DCI-PayloadSize-r16 INTEGER ::= 128 --Maximum size of the DCI payload scrambled with ai-RNTI +maxAI-DCI-PayloadSize-1-r16 INTEGER ::= 127 --Maximum size of the DCI payload scrambled with ai-RNTI minus 1 +maxBandComb INTEGER ::= 65536 -- Maximum number of DL band combinations +maxBandsUTRA-FDD-r16 INTEGER ::= 64 -- Maximum number of bands listed in UTRA-FDD UE caps +maxCandidateBandIndex-r18 INTEGER ::= 8 -- Maximum number of band entry index for MUSIM capability +maxBH-RLC-ChannelID-r16 INTEGER ::= 65536 -- Maximum value of BH RLC Channel ID +maxBT-IdReport-r16 INTEGER ::= 32 -- Maximum number of Bluetooth IDs to report +maxBT-Name-r16 INTEGER ::= 4 -- Maximum number of Bluetooth name +maxCAG-Cell-r16 INTEGER ::= 16 -- Maximum number of NR CAG cell ranges in SIB3, SIB4 +maxTwoPUCCH-Grp-ConfigList-r16 INTEGER ::= 32 -- Maximum number of supported configuration(s) of {primary PUCCH group + -- config, secondary PUCCH group config} +maxTwoPUCCH-Grp-ConfigList-r17 INTEGER ::= 16 -- Maximum number of supported configuration(s) of {primary PUCCH group + -- config, secondary PUCCH group config} for PUCCH cell switching +maxCBR-Config-r16 INTEGER ::= 8 -- Maximum number of CBR range configurations for sidelink communication + -- congestion control +maxCBR-Config-1-r16 INTEGER ::= 7 -- Maximum number of CBR range configurations for sidelink communication + -- congestion control minus 1 +maxCBR-Level-r16 INTEGER ::= 16 -- Maximum number of CBR levels +maxCBR-Level-1-r16 INTEGER ::= 15 -- Maximum number of CBR levels minus 1 +maxCellATG-r18 INTEGER ::= 8 -- Maximum number of ATG neighbour cells for which assistance information is + -- provided +maxCellExcluded INTEGER ::= 16 -- Maximum number of NR exclude-listed cell ranges in SIB3, SIB4 +maxCellGroupings-r16 INTEGER ::= 32 -- Maximum number of cell groupings for NR-DC +maxCellHistory-r16 INTEGER ::= 16 -- Maximum number of visited PCells reported +maxPSCellHistory-r17 INTEGER ::= 16 -- Maximum number of visited PCells across all reported PCells +maxCellInter INTEGER ::= 16 -- Maximum number of inter-Freq cells listed in SIB4 +maxCellIntra INTEGER ::= 16 -- Maximum number of intra-Freq cells listed in SIB3 +maxCellMeasUTRA INTEGER ::= 32 -- Maximum number of cells in E-UTRAN +maxCellMeasIdle-r16 INTEGER ::= 8 -- Maximum number of cells per carrier for idle/inactive measurements +maxCellMeasUTRA-FDD-r16 INTEGER ::= 32 -- Maximum number of cells in FDD UTRAN +maxCellNTN-r17 INTEGER ::= 4 -- Maximum number of NTN neighbour cells for which assistance information is + -- provided +maxCarrierTypePairList-r16 INTEGER ::= 16 -- Maximum number of supported carrier type pair of (carrier type on which + -- CSI measurement is performed, carrier type on which CSI reporting is + -- performed) for CSI reporting cross PUCCH group +maxCellAllowed INTEGER ::= 16 -- Maximum number of NR allow-listed cell ranges in SIB3, SIB4 +maxEARFCN INTEGER ::= 262143 -- Maximum value of E-UTRA carrier frequency +maxEUTRA-CellExcluded INTEGER ::= 16 -- Maximum number of E-UTRA exclude-listed physical cell identity ranges + -- in SIB5 +maxEUTRA-NS-Pmax INTEGER ::= 8 -- Maximum number of NS and P-Max values per band +maxFeatureCombPreamblesPerRACHResource-r17 INTEGER ::= 256 -- Maximum number of feature combination preambles. +maxLogMeasReport-r16 INTEGER ::= 520 -- Maximum number of entries for logged measurements +maxMultiBands INTEGER ::= 8 -- Maximum number of additional frequency bands that a cell belongs to +``` + +``` + +maxNARFCN INTEGER ::= 3279165 -- Maximum value of NR carrier frequency +maxNR-NS-Pmax INTEGER ::= 8 -- Maximum number of NS and P-Max values per band +maxFreqIdle-r16 INTEGER ::= 8 -- Maximum number of carrier frequencies for idle/inactive measurements +maxNrofServingCells INTEGER ::= 32 -- Max number of serving cells (SpCells + SCells) +maxNrofServingCells-1 INTEGER ::= 31 -- Max number of serving cells (SpCells + SCells) minus 1 +maxNrofAggregatedCellsPerCellGroup INTEGER ::= 16 +maxNrofAggregatedCellsPerCellGroupMinus1-r16 INTEGER ::= 12 +maxNrofAperiodicFwdTimeResource-r18 INTEGER ::= 112 -- Max number of aperiodic fowarding time resources for NCR +maxNrofAperiodicFwdTimeResource-1-r18 INTEGER ::= 111 -- Max number of aperiodic fowarding time resources for NCR minus 1 +maxNrofDUCells-r16 INTEGER ::= 512 -- Max number of cells configured on the collocated IAB-DU +maxNrofAppLayerMeas-r17 INTEGER ::= 16 -- Max number of simultaneous application layer measurements +maxNrofAppLayerMeas-1-r17 INTEGER ::= 15 -- Max number of simultaneous application layer measurements minus 1 +maxNrofAvailabilityCombinationsPerSet-r16 INTEGER ::= 512 -- Max number of AvailabilityCombinationId used in the DCI format 2_5 +maxNrofAvailabilityCombinationsPerSet-1-r16 INTEGER ::= 511 -- Max number of AvailabilityCombinationId used in the DCI format 2_5 minus 1 +maxNrofIABResourceConfig-r17 INTEGER ::= 65536 -- Max number of IAB-ResourceConfigID used in MAC CE +maxNrofIABResourceConfig-1-r17 INTEGER ::= 65535 -- Max number of IAB-ResourceConfigID used in MAC CE minus 1 +maxNrofPeriodicFwdResourceSet-r18 INTEGER ::= 32 -- Max number of periodic fowarding resource sets for NCR +maxNrofPeriodicFwdResourceSet-1-r18 INTEGER ::= 31 -- Max number of periodic fowarding resource sets for NCR minus 1 +maxNrofPeriodicFwdResource-r18 INTEGER ::= 1024 -- Max number of periodic fowarding resources for NCR +maxNrofPeriodicFwdResource-1-r18 INTEGER ::= 1023 -- Max number of periodic fowarding resources for NCR minus 1 +maxNrofSemiPersistentFwdResourceSet-r18 INTEGER ::= 32 -- Max number of semi-persistent fowarding resource sets for NCR +maxNrofSemiPersistentFwdResourceSet-1-r18 INTEGER ::= 31 -- Max number of semi-persistent fowarding resource sets for NCR minus 1 +maxNrofSemiPersistentFwdResource-r18 INTEGER ::= 128 -- Max number of semi-persistent fowarding resources for NCR +maxNrofSemiPersistentFwdResource-1-r18 INTEGER ::= 127 -- Max number of semi-persistent fowarding resources for NCR minus 1 +maxNrofSCellActRS-r17 INTEGER ::= 255 -- Max number of RS configurations per SCell for SCell activation +maxNrofSCells INTEGER ::= 31 -- Max number of secondary serving cells per cell group +maxNrofCellMeas INTEGER ::= 32 -- Maximum number of entries in each of the cell lists in a measurement object +maxNrofCRS-IM-InterfCell-r17 INTEGER ::= 8 -- Maximum number of LTE interference cells for CRS-IM per UE +maxNrofRelayMeas-r17 INTEGER ::= 32 -- Maximum number of L2 U2N Relay UEs to measure for each measurement object +-- on sidelink frequency +maxNrofCG-SL-r16 INTEGER ::= 8 -- Max number of sidelink configured grant +maxNrofCG-SL-1-r16 INTEGER ::= 7 -- Max number of sidelink configured grant minus 1 +maxSL-GC-BC-DRX-QoS-r17 INTEGER ::= 16 -- Max number of sidelink DRX configurations for NR +-- sidelink groupcast/broadcast communication +maxNrofSL-RxInfoSet-r17 INTEGER ::= 4 -- Max number of sidelink DRX configuration sets in sidelink DRX assistant +-- information +maxNrofSS-BlocksToAverage INTEGER ::= 16 -- Max number for the (max) number of SS blocks to average to determine cell measurement +maxNrofCondCells-r16 INTEGER ::= 8 -- Max number of conditional candidate SpCells +maxNrofCondCells-1-r17 INTEGER ::= 7 -- Max number of conditional candidate SpCells minus 1 +maxNrofCSI-RS-ResourcesToAverage INTEGER ::= 16 -- Max number for the (max) number of CSI-RS to average to determine cell measurement +maxNrofDL-Allocations INTEGER ::= 16 -- Maximum number of PDSCH time domain resource allocations +maxNrofDL-AllocationsExt-r17 INTEGER ::= 64 -- Maximum number of PDSCH time domain resource allocations for multi-PDSCH +-- scheduling +maxNrofDL-Allocations-1-r18 INTEGER ::= 15 -- Maximum number of PDSCH time domain resource allocations minus 1 +maxNrofPDU-Sessions-r17 INTEGER ::= 256 -- Maximum number of PDU Sessions +maxNrofSR-ConfigPerCellGroup INTEGER ::= 8 -- Maximum number of SR configurations per cell group +maxNrofLCGs-r18 INTEGER ::= 8 -- Maximum number of LCGs +maxLCG-ID INTEGER ::= 7 -- Maximum value of LCG ID +maxLCG-ID-IAB-r17 INTEGER ::= 255 -- Maximum value of LCG ID for IAB-MT +maxLC-ID INTEGER ::= 32 -- Maximum value of Logical Channel ID +maxLC-ID-Iab-r16 INTEGER ::= 65855 -- Maximum value of BH Logical Channel ID extension +maxLTE-CRS-Patterns-r16 INTEGER ::= 3 -- Maximum number of additional LTE CRS rate matching patterns +maxNrofTAGs INTEGER ::= 4 -- Maximum number of Timing Advance Groups + +``` + +| | | | +|-----------------------------------------|-----------------|--------------------------------------------------------------------------------------| +| maxNrofTAGs-1 | INTEGER ::= 3 | -- Maximum number of Timing Advance Groups minus 1 | +| maxNrofBWP | INTEGER ::= 4 | -- Maximum number of BWPs per serving cell | +| maxNrofCombIDC | INTEGER ::= 128 | -- Maximum number of reported MR-DC combinations for IDC | +| maxNrofSymbols-1 | INTEGER ::= 13 | -- Maximum index identifying a symbol within a slot (14 symbols, indexed from 0..13) | +| maxNrofSlots | INTEGER ::= 320 | -- Maximum number of slots in a 10 ms period | +| maxNrofSlots-1 | INTEGER ::= 319 | -- Maximum number of slots in a 10 ms period minus 1 | +| maxNrofPhysicalResourceBlocks | INTEGER ::= 275 | -- Maximum number of PRBs | +| maxNrofPhysicalResourceBlocks-1 | INTEGER ::= 274 | -- Maximum number of PRBs minus 1 | +| maxNrofPhysicalResourceBlocksPlus1 | INTEGER ::= 276 | -- Maximum number of PRBs plus 1 | +| maxNrofControlResourceSets | INTEGER ::= 12 | -- Max number of CoReSets configurable on a serving cell | +| maxNrofControlResourceSets-1 | INTEGER ::= 11 | -- Max number of CoReSets configurable on a serving cell minus 1 | +| maxNrofControlResourceSets-1-r16 | INTEGER ::= 15 | -- Max number of CoReSets configurable on a serving cell extended in minus 1 | +| maxNrofCoresetPools-r16 | INTEGER ::= 2 | -- Maximum number of CORESET pools | +| maxCoReSetDuration | INTEGER ::= 3 | -- Max number of OFDM symbols in a control resource set | +| maxNrofSearchSpaces-1 | INTEGER ::= 39 | -- Max number of Search Spaces minus 1 | +| maxNrofSearchSpacesLinks-1-r17 | INTEGER ::= 39 | -- Max number of Search Space links minus 1 | +| maxNrofBFDResourcePerSet-r17 | INTEGER ::= 64 | -- Max number of reference signal in one BFD set | +| maxSFI-DCI-PayloadSize | INTEGER ::= 128 | -- Max number payload of a DCI scrambled with SFI-RNTI | +| maxSFI-DCI-PayloadSize-1 | INTEGER ::= 127 | -- Max number payload of a DCI scrambled with SFI-RNTI minus 1 | +| maxIAB-IP-Address-r16 | INTEGER ::= 32 | -- Max number of assigned IP addresses | +| maxINT-DCI-PayloadSize | INTEGER ::= 126 | -- Max number payload of a DCI scrambled with INT-RNTI | +| maxINT-DCI-PayloadSize-1 | INTEGER ::= 125 | -- Max number payload of a DCI scrambled with INT-RNTI minus 1 | +| maxNrofRateMatchPatterns | INTEGER ::= 4 | -- Max number of rate matching patterns that may be configured | +| maxNrofRateMatchPatterns-1 | INTEGER ::= 3 | -- Max number of rate matching patterns that may be configured minus 1 | +| maxNrofRateMatchPatternsPerGroup | INTEGER ::= 8 | -- Max number of rate matching patterns that may be configured in one group | +| maxNrofCSI-ReportConfigurations | INTEGER ::= 48 | -- Maximum number of report configurations | +| maxNrofCSI-ReportConfigurations-1 | INTEGER ::= 47 | -- Maximum number of report configurations minus 1 | +| maxNrofCSI-ResourceConfigurations | INTEGER ::= 112 | -- Maximum number of resource configurations | +| maxNrofCSI-ResourceConfigurations-1 | INTEGER ::= 111 | -- Maximum number of resource configurations minus 1 | +| maxNrofAP-CSI-RS-ResourcesPerSet | INTEGER ::= 16 | | +| maxNrOfCSI-AperiodicTriggers | INTEGER ::= 128 | -- Maximum number of triggers for aperiodic CSI reporting | +| maxNrofReportConfigPerAperiodicTrigger | INTEGER ::= 16 | -- Maximum number of report configurations per trigger state for aperiodic reporting | +| maxNrofNZP-CSI-RS-Resources | INTEGER ::= 192 | -- Maximum number of Non-Zero-Power (NZP) CSI-RS resources | +| maxNrofNZP-CSI-RS-Resources-1 | INTEGER ::= 191 | -- Maximum number of Non-Zero-Power (NZP) CSI-RS resources minus 1 | +| maxNrofNZP-CSI-RS-ResourcesPerSet | INTEGER ::= 64 | -- Maximum number of NZP CSI-RS resources per resource set | +| maxNrofNZP-CSI-RS-ResourcesPerSet-1-r18 | INTEGER ::= 63 | -- Maximum number of NZP CSI-RS resources per resource set minus 1 | +| maxNrofNZP-CSI-RS-ResourceSets | INTEGER ::= 64 | -- Maximum number of NZP CSI-RS resource sets per cell | +| maxNrofNZP-CSI-RS-ResourceSets-1 | INTEGER ::= 63 | -- Maximum number of NZP CSI-RS resource sets per cell minus 1 | +| maxNrofNZP-CSI-RS-ResourceSetsPerConfig | INTEGER ::= 16 | -- Maximum number of resource sets per resource configuration | +| maxNrofNZP-CSI-RS-ResourcesPerConfig | INTEGER ::= 128 | -- Maximum number of resources per resource configuration | +| maxNrofZP-CSI-RS-Resources | INTEGER ::= 32 | -- Maximum number of Zero-Power (ZP) CSI-RS resources | +| maxNrofZP-CSI-RS-Resources-1 | INTEGER ::= 31 | -- Maximum number of Zero-Power (ZP) CSI-RS resources minus 1 | +| maxNrofZP-CSI-RS-ResourceSets-1 | INTEGER ::= 15 | | +| maxNrofZP-CSI-RS-ResourcesPerSet | INTEGER ::= 16 | | +| maxNrofZP-CSI-RS-ResourceSets | INTEGER ::= 16 | | +| maxNrofCSI-IM-Resources | INTEGER ::= 32 | -- Maximum number of CSI-IM resources | +| maxNrofCSI-IM-Resources-1 | INTEGER ::= 31 | -- Maximum number of CSI-IM resources minus 1 | +| maxNrofCSI-IM-ResourcesPerSet | INTEGER ::= 8 | -- Maximum number of CSI-IM resources per set | +| maxNrofCSI-IM-ResourceSets | INTEGER ::= 64 | -- Maximum number of NZP CSI-IM resource sets per cell | +| maxNrofCSI-IM-ResourceSets-1 | INTEGER ::= 63 | -- Maximum number of NZP CSI-IM resource sets per cell minus 1 | +| maxNrofCSI-IM-ResourceSetsPerConfig | INTEGER ::= 16 | -- Maximum number of CSI IM resource sets per resource configuration | +| maxNrofCSI-SSB-ResourcePerSet | INTEGER ::= 64 | -- Maximum number of SSB resources in a resource set | +| maxNrofCSI-SSB-ResourceSets | INTEGER ::= 64 | -- Maximum number of CSI SSB resource sets per cell | + +``` + +maxNrofCSI-SSB-ResourceSets-1 INTEGER ::= 63 -- Maximum number of CSI SSB resource sets per cell minus 1 +maxNrofCSI-SSB-ResourceSetsPerConfig INTEGER ::= 1 -- Maximum number of CSI SSB resource sets per resource configuration +maxNrofCSI-SSB-ResourceSetsPerConfigExt INTEGER ::= 2 -- Maximum number of CSI SSB resource sets per resource configuration +-- extended +maxNrofFailureDetectionResources INTEGER ::= 10 -- Maximum number of failure detection resources +maxNrofFailureDetectionResources-1 INTEGER ::= 9 -- Maximum number of failure detection resources minus 1 +maxNrofFailureDetectionResources-1-r17 INTEGER ::= 63 -- Maximum number of the enhanced failure detection resources minus 1 +maxNrofFreqSL-r16 INTEGER ::= 8 -- Maximum number of carrier frequency for NR sidelink communication +maxNrofFreqSL-1-r18 INTEGER ::= 7 -- Maximum number of carrier frequency for NR sidelink communication minus 1 +maxNrofSL-BWPs-r16 INTEGER ::= 4 -- Maximum number of BWP for NR sidelink communication +maxFreqSL-EUTRA-r16 INTEGER ::= 8 -- Maximum number of EUTRA anchor carrier frequency for NR sidelink communication +maxNrofSL-MeasId-r16 INTEGER ::= 64 -- Maximum number of sidelink measurement identity (RSRP) per destination +maxNrofSL-ObjectId-r16 INTEGER ::= 64 -- Maximum number of sidelink measurement objects (RSRP) per destination +maxNrofSL-ReportConfigId-r16 INTEGER ::= 64 -- Maximum number of sidelink measurement reporting configuration(RSRP) per destination +maxNrofSL-PoolToMeasureNR-r16 INTEGER ::= 8 -- Maximum number of resource pool for NR sidelink measurement to measure for +-- each measurement object (for CBR) +maxFreqSL-NR-r16 INTEGER ::= 8 -- Maximum number of NR anchor carrier frequency for NR sidelink communication +maxNrofSL-QFIs-r16 INTEGER ::= 2048 -- Maximum number of QoS flow for NR sidelink communication per UE +maxNrofSL-QFIsPerDest-r16 INTEGER ::= 64 -- Maximum number of QoS flow per destination for NR sidelink communication +maxNrofObjectId INTEGER ::= 64 -- Maximum number of measurement objects +maxNrofPageRec INTEGER ::= 32 -- Maximum number of page records +maxNrofPCI-Ranges INTEGER ::= 8 -- Maximum number of PCI ranges +maxPLMN INTEGER ::= 12 -- Maximum number of PLMNs broadcast and reported by UE at establishment +maxTAC-r17 INTEGER ::= 12 -- Maximum number of Tracking Area Codes to which a cell belongs to +maxNrofCSI-RS-ResourcesRRM INTEGER ::= 96 -- Maximum number of CSI-RS resources per cell for an RRM measurement object +maxNrofCSI-RS-ResourcesRRM-1 INTEGER ::= 95 -- Maximum number of CSI-RS resources per cell for an RRM measurement object +-- minus 1. +maxNrofMeasId INTEGER ::= 64 -- Maximum number of configured measurements +maxNrofQuantityConfig INTEGER ::= 2 -- Maximum number of quantity configurations +maxNrofCSI-RS-CellsRRM INTEGER ::= 96 -- Maximum number of cells with CSI-RS resources for an RRM measurement object +maxNrofSL-Dest-r16 INTEGER ::= 32 -- Maximum number of destination for NR sidelink communication and discovery +maxNrofSL-Dest-1-r16 INTEGER ::= 31 -- Highest index of destination for NR sidelink communication and discovery +maxNrofSLRB-r16 INTEGER ::= 512 -- Maximum number of radio bearer for NR sidelink communication per UE without +duplication +maxSL-LCID-Plus1-r18 INTEGER ::= 513 -- Maximum number of RLC bearer for NR sidelink communication per UE without duplication +plus 1 +maxSL-LCID-r18 INTEGER ::= 1024 -- Maximum number of RLC bearer for NR sidelink communication per UE with duplication +maxSL-NonAnchorRBsets INTEGER ::= 4 -- Maximum number of non-anchor RB sets +maxSL-LCID-r16 INTEGER ::= 512 -- Maximum number of RLC bearer for NR sidelink communication per UE +maxSL-SyncConfig-r16 INTEGER ::= 16 -- Maximum number of sidelink Sync configurations +maxNrofRXPool-r16 INTEGER ::= 16 -- Maximum number of Rx resource pool for NR sidelink communication and +-- discovery +maxNrofTXPool-r16 INTEGER ::= 8 -- Maximum number of Tx resource pool for NR sidelink communication and +-- discovery +maxNrofPoolID-r16 INTEGER ::= 16 -- Maximum index of resource pool for NR sidelink communication and +-- discovery +maxNrofSRS-PathlossReferenceRS-r16 INTEGER ::= 64 -- Maximum number of RSs used as pathloss reference for SRS power control. +maxNrofSRS-PathlossReferenceRS-1-r16 INTEGER ::= 63 -- Maximum number of RSs used as pathloss reference for SRS power control +-- minus 1. +maxNrofSRS-ResourceSets INTEGER ::= 16 -- Maximum number of SRS resource sets in a BWP. +maxNrofSRS-ResourceSets-1 INTEGER ::= 15 -- Maximum number of SRS resource sets in a BWP minus 1. +maxNrofSRS-PosResourceSets-r16 INTEGER ::= 16 -- Maximum number of SRS Positioning resource sets in a BWP. +maxNrofSRS-PosResourceSets-1-r16 INTEGER ::= 15 -- Maximum number of SRS Positioning resource sets in a BWP minus 1. + +``` + +``` + +maxNrofSRS-Resources INTEGER ::= 64 -- Maximum number of SRS resources. +maxNrofSRS-Resources-1 INTEGER ::= 63 -- Maximum number of SRS resources minus 1. +maxNrofSRS-PosResources-r16 INTEGER ::= 64 -- Maximum number of SRS Positioning resources. +maxNrofSRS-PosResources-1-r16 INTEGER ::= 63 -- Maximum number of SRS Positioning resources minus 1. +maxNrofSRS-ResourcesPerSet INTEGER ::= 16 -- Maximum number of SRS resources in an SRS resource set +maxNrofSRS-TriggerStates-1 INTEGER ::= 3 -- Maximum number of SRS trigger states minus 1, i.e., the largest code point. +maxNrofSRS-TriggerStates-2 INTEGER ::= 2 -- Maximum number of SRS trigger states minus 2. +maxRAT-CapabilityContainers INTEGER ::= 8 -- Maximum number of interworking RAT containers (incl NR and MRDC) +maxSimultaneousBands INTEGER ::= 32 -- Maximum number of simultaneously aggregated bands +maxSimultaneousBands-2-r18 INTEGER ::= 30 -- Maximum number of simultaneously aggregated bands minus 2. +maxULTxSwitchingBandPairs INTEGER ::= 32 -- Maximum number of band pairs supporting dynamic UL Tx switching in a band + -- combination. +maxULTxSwitchingBetweenBandPairs-r18 INTEGER ::= 32 -- Maximum number of combinations of a band pair and another band pair/band + -- between which dyanmic UL Tx switching requires additional switching + -- period. +maxSchedulingBandCombination-r18 INTEGER ::= 32 -- Maximum number of combinations of scheduling cell and co-scheduled cells + -- have same or different carrier type. +maxNrofSlotFormatCombinationsPerSet INTEGER ::= 512 -- Maximum number of Slot Format Combinations in a SF-Set. +maxNrofSlotFormatCombinationsPerSet-1 INTEGER ::= 511 -- Maximum number of Slot Format Combinations in a SF-Set minus 1. +maxNrofTrafficPattern-r16 INTEGER ::= 8 -- Maximum number of Traffic Pattern for NR sidelink communication. +maxNrofPUCCH-Resources INTEGER ::= 128 +maxNrofPUCCH-Resources-1 INTEGER ::= 127 +maxNrofPUCCH-ResourceSets INTEGER ::= 4 -- Maximum number of PUCCH Resource Sets +maxNrofPUCCH-ResourceSets-1 INTEGER ::= 3 -- Maximum number of PUCCH Resource Sets minus 1. +maxNrofPUCCH-ResourcesPerSet INTEGER ::= 32 -- Maximum number of PUCCH Resources per PUCCH-ResourceSet +maxNrofPUCCH-P0-PerSet INTEGER ::= 8 -- Maximum number of P0-pucch present in a p0-pucch set +maxNrofPUCCH-PathlossReferenceRSs INTEGER ::= 4 -- Maximum number of RSs used as pathloss reference for PUCCH power control. +maxNrofPUCCH-PathlossReferenceRSs-1 INTEGER ::= 3 -- Maximum number of RSs used as pathloss reference for PUCCH power control + -- minus 1. +maxNrofPUCCH-PathlossReferenceRSs-r16 INTEGER ::= 64 -- Maximum number of RSs used as pathloss reference for PUCCH power control + -- extended. +maxNrofPUCCH-PathlossReferenceRSs-1-r16 INTEGER ::= 63 -- Maximum number of RSs used as pathloss reference for PUCCH power control + -- minus 1 extended. +maxNrofPUCCH-PathlossReferenceRSs-1-r17 INTEGER ::= 7 -- Maximum number of RSs used as pathloss reference for PUCCH power control + -- minus 1. +maxNrofPUCCH-PathlossReferenceRSsDiff-r16 INTEGER ::= 60 -- Difference between the extended maximum and the non-extended maximum +maxNrofPUCCH-ResourceGroups-r16 INTEGER ::= 4 -- Maximum number of PUCCH resources groups. +maxNrofPUCCH-ResourcesPerGroup-r16 INTEGER ::= 128 -- Maximum number of PUCCH resources in a PUCCH group. +maxNrofPowerControlSetInfos-r17 INTEGER ::= 8 -- Maximum number of PUCCH power control set infos +maxNrofMultiplePUSCHs-r16 INTEGER ::= 8 -- Maximum number of multiple PUSCHs in PUSCH TDRA list +maxNrofP0-PUSCH-AlphaSets INTEGER ::= 30 -- Maximum number of P0-pusch-alpha-sets (see TS 38.213 [13], clause 7.1) +maxNrofP0-PUSCH-AlphaSets-1 INTEGER ::= 29 -- Maximum number of P0-pusch-alpha-sets minus 1 (see TS 38.213 [13], clause 7.1) +maxNrofPUSCH-PathlossReferenceRSs INTEGER ::= 4 -- Maximum number of RSs used as pathloss reference for PUSCH power control. +maxNrofPUSCH-PathlossReferenceRSs-1 INTEGER ::= 3 -- Maximum number of RSs used as pathloss reference for PUSCH power control + -- minus 1. +maxNrofPUSCH-PathlossReferenceRSs-r16 INTEGER ::= 64 -- Maximum number of RSs used as pathloss reference for PUSCH power control + -- extended +maxNrofPUSCH-PathlossReferenceRSs-1-r16 INTEGER ::= 63 -- Maximum number of RSs used as pathloss reference for PUSCH power control + -- extended minus 1 +maxNrofPUSCH-PathlossReferenceRSsDiff-r16 INTEGER ::= 60 -- Difference between maxNrofPUSCH-PathlossReferenceRSs-r16 and + -- maxNrofPUSCH-PathlossReferenceRSs +maxNrofPathlossReferenceRSs-r17 INTEGER ::= 64 -- Maximum number of RSs used as pathloss reference for PUSCH, PUCCH, SRS + -- power control for unified TCI state operation + +``` + +``` + +maxNrofPathlossReferenceRSs-1-r17 INTEGER ::= 63 -- Maximum number of RSs used as pathloss reference for PUSCH, PUCCH, SRS + -- power control for unified TCI state operation minus 1 +maxNrofNAICS-Entries INTEGER ::= 8 -- Maximum number of supported NAICS capability set +maxBands INTEGER ::= 1024 -- Maximum number of supported bands in UE capability. +maxBandsMRDC INTEGER ::= 1280 +maxBandsEUTRA INTEGER ::= 256 +maxCellReport INTEGER ::= 8 +maxDRB INTEGER ::= 29 -- Maximum number of DRBs (that can be added in DRB-ToAddModList). +maxFreq INTEGER ::= 8 -- Max number of frequencies. +maxFreqLayers INTEGER ::= 4 -- Max number of frequency layers. +maxFreqPlus1 INTEGER ::= 9 -- Max number of frequencies for Slicing. +maxFreqIDC-r16 INTEGER ::= 128 -- Max number of frequencies for IDC indication. +maxCombIDC-r16 INTEGER ::= 128 -- Max number of reported UL CA for IDC indication. +maxFreqIDC-MRDC INTEGER ::= 32 -- Maximum number of candidate NR frequencies for MR-DC IDC indication +maxNrofCandidateBeams INTEGER ::= 16 -- Max number of PRACH-ResourceDedicatedBFR in BFR config. +maxNrofCandidateBeams-r16 INTEGER ::= 64 -- Max number of candidate beam resources in BFR config. +maxNrofCandidateBeamsExt-r16 INTEGER ::= 48 -- Max number of PRACH-ResourceDedicatedBFR in the CandidateBeamRSListExt +maxNrofPCIsPerSMTC INTEGER ::= 64 -- Maximum number of PCIs per SMTC. +maxNrofQFTIs INTEGER ::= 64 +maxNrofResourceAvailabilityPerCombination-r16 INTEGER ::= 256 +maxNrOfSemiPersistentPUSCH-Triggers INTEGER ::= 64 -- Maximum number of triggers for semi persistent reporting on PUSCH +maxNrofSR-Resources INTEGER ::= 8 -- Maximum number of SR resources per BWP in a cell. +maxNrofSlotFormatsPerCombination INTEGER ::= 256 +maxNrofSpatialRelationInfos INTEGER ::= 8 +maxNrofSpatialRelationInfos-plus-1 INTEGER ::= 9 +maxNrofSpatialRelationInfos-r16 INTEGER ::= 64 +maxNrofSpatialRelationInfosDiff-r16 INTEGER ::= 56 -- Difference between maxNrofSpatialRelationInfos-r16 and maxNrofSpatialRelationInfos +maxNrofIndexesToReport INTEGER ::= 32 +maxNrofIndexesToReport2 INTEGER ::= 64 +maxNrofSSBs-r16 INTEGER ::= 64 -- Maximum number of SSB resources in a resource set. +maxNrofSSBs-1 INTEGER ::= 63 -- Maximum number of SSB resources in a resource set minus 1. +maxNrofS-NSSAI INTEGER ::= 8 -- Maximum number of S-NSSAI. +maxNrofTCI-StatesPDCCH INTEGER ::= 64 +maxNrofTCI-States INTEGER ::= 128 -- Maximum number of TCI states. +maxNrofTCI-States-1 INTEGER ::= 127 -- Maximum number of TCI states minus 1. +maxUL-TCI-r17 INTEGER ::= 64 -- Maximum number of TCI states. +maxUL-TCI-1-r17 INTEGER ::= 63 -- Maximum number of TCI states minus 1. +maxNrofAdditionalPCI-r17 INTEGER ::= 7 -- Maximum number of additional PCI +maxNrofAdditionalPRACHConfigs-r18 INTEGER ::= 7 -- Maximum number of additional PRACH configurations for 2TA +maxNrofDelayD-r18 INTEGER ::= 4 -- Maximum number of delayD values. +maxMPE-Resources-r17 INTEGER ::= 64 -- Maximum number of pooled MPE resources +maxNrofUL-Allocations INTEGER ::= 16 -- Maximum number of PUSCH time domain resource allocations. +maxQFI INTEGER ::= 63 +maxRA-CSIRS-Resources INTEGER ::= 96 +maxRA-OccasionsPerCSIRS INTEGER ::= 64 -- Maximum number of RA occasions for one CSI-RS +maxRA-Occasions-1 INTEGER ::= 511 -- Maximum number of RA occasions in the system +maxRA-SSB-Resources INTEGER ::= 64 +maxSCSs INTEGER ::= 5 +maxSecondaryCellGroups INTEGER ::= 3 +maxNrofServingCellsEUTRA INTEGER ::= 32 +maxMBSFN-Allocations INTEGER ::= 8 +maxNrofMultiBands INTEGER ::= 8 +maxCellSFTD INTEGER ::= 3 -- Maximum number of cells for SFTD reporting + +``` + +| | | | +|--------------------------------------|------------------|---------------------------------------------------------------------------------------| +| maxReportConfigId | INTEGER ::= 64 | | +| maxNrofCodebooks | INTEGER ::= 16 | -- Maximum number of codebooks supported by the UE | +| maxNrofCSI-RS-ResourcesExt-r16 | INTEGER ::= 16 | -- Maximum number of codebook resources supported by the UE for eType2/Codebook combo | +| maxNrofCSI-RS-ResourcesExt-r17 | INTEGER ::= 8 | -- Maximum number of codebook resources for fetype2R1 and fetype2R2 | +| maxNrofCSI-RS-Resources | INTEGER ::= 7 | -- Maximum number of codebook resources supported by the UE | +| maxNrofCSI-RS-ResourcesAlt-r16 | INTEGER ::= 512 | -- Maximum number of alternative codebook resources supported by the UE | +| maxNrofCSI-RS-ResourcesAlt-r17 | INTEGER ::= 511 | -- Maximum number of alternative codebook resources supported by the UE minus 1 | +| maxNrofSRI-PUSCH-Mappings | INTEGER ::= 16 | | +| maxNrofSRI-PUSCH-Mappings-1 | INTEGER ::= 15 | | +| maxSIB | INTEGER ::= 32 | -- Maximum number of SIBs | +| maxSI-Message | INTEGER ::= 32 | -- Maximum number of SI messages | +| maxSIB-MessagePlus1-r17 | INTEGER ::= 33 | -- Maximum number of SIB messages plus 1 | +| maxPO-perPF | INTEGER ::= 4 | -- Maximum number of paging occasion per paging frame | +| maxPEI-perPF-r17 | INTEGER ::= 4 | -- Maximum number of PEI occasion per paging frame | +| maxAccessCat-1 | INTEGER ::= 63 | -- Maximum number of Access Categories minus 1 | +| maxBarringInfoSet | INTEGER ::= 8 | -- Maximum number of access control parameter sets | +| maxCellEUTRA | INTEGER ::= 8 | -- Maximum number of E-UTRA cells in SIB list | +| maxEUTRA-Carrier | INTEGER ::= 8 | -- Maximum number of E-UTRA carriers in SIB list | +| maxPLMNIdentities | INTEGER ::= 8 | -- Maximum number of PLMN identities in RAN area configurations | +| maxDownlinkFeatureSets | INTEGER ::= 1024 | -- (for NR DL) Total number of FeatureSets (size of the pool) | +| maxUplinkFeatureSets | INTEGER ::= 1024 | -- (for NR UL) Total number of FeatureSets (size of the pool) | +| maxEUTRA-DL-FeatureSets | INTEGER ::= 256 | -- (for E-UTRA) Total number of FeatureSets (size of the pool) | +| maxEUTRA-UL-FeatureSets | INTEGER ::= 256 | -- (for E-UTRA) Total number of FeatureSets (size of the pool) | +| maxFeatureSetsPerBand | INTEGER ::= 128 | -- (for NR) The number of feature sets associated with one band. | +| maxPerCC-FeatureSets | INTEGER ::= 1024 | -- (for NR) Total number of CC-specific FeatureSets (size of the pool) | +| maxFeatureSetCombinations | INTEGER ::= 1024 | -- (for MR-DC/NR) Total number of Feature set combinations (size of the pool) | +| maxInterRAT-RSTD-Freq | INTEGER ::= 3 | | +| maxGIN-r17 | INTEGER ::= 24 | -- Maximum number of broadcast GINs | +| maxHRNN-Len-r16 | INTEGER ::= 48 | -- Maximum length of HRNNs | +| maxNPN-r16 | INTEGER ::= 12 | -- Maximum number of NPNs broadcast and reported by UE at establishment | +| maxSNPN-ConfigCellId-r18 | INTEGER ::= 32 | -- Maximum number of Cell ID subject for SNPNS for MDT scope | +| maxSNPN-ConfigID-r18 | INTEGER ::= 16 | -- Maximum number of SNPNS in the MDT SNPN list | +| maxSNPN-ConfigTAI-r18 | INTEGER ::= 8 | -- Maximum number of TA subject for MDT scope | +| maxNrOfMinSchedulingOffsetValues-r16 | INTEGER ::= 2 | -- Maximum number of min. scheduling offset (K0/K2) configurations | +| maxK0-SchedulingOffset-r16 | INTEGER ::= 16 | -- Maximum number of slots configured as min. scheduling offset (K0) | +| maxK2-SchedulingOffset-r16 | INTEGER ::= 16 | -- Maximum number of slots configured as min. scheduling offset (K2) | +| maxK0-SchedulingOffset-r17 | INTEGER ::= 64 | -- Maximum number of slots configured as min. scheduling offset (K0) | +| maxK2-SchedulingOffset-r17 | INTEGER ::= 64 | -- Maximum number of slots configured as min. scheduling offset (K2) | +| maxDCI-2-6-Size-r16 | INTEGER ::= 140 | -- Maximum size of DCI format 2-6 | +| maxDCI-2-7-Size-r17 | INTEGER ::= 43 | -- Maximum size of DCI format 2-7 | +| maxDCI-2-6-Size-1-r16 | INTEGER ::= 139 | -- Maximum DCI format 2-6 size minus 1 | +| maxDCI-2-9-Size-1-r18 | INTEGER ::= 139 | -- Maximum DCI format 2-9 size minus 1 | +| maxNrofUL-Allocations-r16 | INTEGER ::= 64 | -- Maximum number of PUSCH time domain resource allocations | +| maxNrofUL-Allocations-1-r18 | INTEGER ::= 63 | -- Maximum number of PUSCH time domain resource allocations minus 1 | +| maxNrofP0-PUSCH-Set-r16 | INTEGER ::= 2 | -- Maximum number of P0 PUSCH set(s) | +| maxOnDemandSIB-r16 | INTEGER ::= 8 | -- Maximum number of SIB(s) that can be requested on-demand | +| maxOnDemandPosSIB-r16 | INTEGER ::= 32 | -- Maximum number of posSIB(s) that can be requested on-demand | +| maxCI-DCI-PayloadSize-r16 | INTEGER ::= 126 | -- Maximum number of the DCI size for CI | +| maxCI-DCI-PayloadSize-1-r16 | INTEGER ::= 125 | -- Maximum number of the DCI size for CI minus 1 | +| maxUu-RelayRLC-ChannelID-r17 | INTEGER ::= 32 | -- Maximum value of Uu Relay RLC channel ID | +| maxWLAN-Id-Report-r16 | INTEGER ::= 32 | -- Maximum number of WLAN IDs to report | +| maxWLAN-Name-r16 | INTEGER ::= 4 | -- Maximum number of WLAN name | +| maxRAReport-r16 | INTEGER ::= 8 | -- Maximum number of RA procedures information to be included in the RA report | + +``` + +maxTxConfig-r16 INTEGER ::= 64 -- Maximum number of sidelink transmission parameters configurations +maxTxConfig-1-r16 INTEGER ::= 63 -- Maximum number of sidelink transmission parameters configurations minus 1 +maxPSSCH-TxConfig-r16 INTEGER ::= 16 -- Maximum number of PSSCH TX configurations +maxNrofCLI-RSSI-Resources-r16 INTEGER ::= 64 -- Maximum number of CLI-RSSI resources for UE +maxNrofCLI-RSSI-Resources-1-r16 INTEGER ::= 63 -- Maximum number of CLI-RSSI resources for UE minus 1 +maxNrofCLI-SRS-Resources-r16 INTEGER ::= 32 -- Maximum number of SRS resources for CLI measurement for UE +maxCLI-Report-r16 INTEGER ::= 8 +maxNrofCC-Group-r17 INTEGER ::= 16 -- Maximum number of CC groups for DC location report +maxNrofConfiguredGrantConfig-r16 INTEGER ::= 12 -- Maximum number of configured grant configurations per BWP +maxNrofConfiguredGrantConfig-1-r16 INTEGER ::= 11 -- Maximum number of configured grant configurations per BWP minus 1 +maxNrofCG-Type2DeactivationState INTEGER ::= 16 -- Maximum number of deactivation state for type 2 configured grants per BWP +maxNrofConfiguredGrantConfigMAC-1-r16 INTEGER ::= 31 -- Maximum number of configured grant configurations per MAC entity minus 1 +maxNrofCSI-ReportSubconfigPerCSI-ReportConfig-r18 INTEGER ::= 8 -- Maximum number of CSI report subconfigurations per CSI report +-- configuration +maxNrofCSI-ReportSubconfigPerCSI-ReportConfig-1-r18 INTEGER ::= 7 -- Maximum number of CSI report subconfigurations per CSI report +-- configuration minus 1 +maxNrofSPS-Config-r16 INTEGER ::= 8 -- Maximum number of SPS configurations per BWP +maxNrofSPS-Config-1-r16 INTEGER ::= 7 -- Maximum number of SPS configurations per BWP minus 1 +maxNrofSPS-DeactivationState INTEGER ::= 16 -- Maximum number of deactivation state for SPS per BWP +maxNrofPPW-Config-r17 INTEGER ::= 4 -- Maximum number of Preconfigured PRS processing windows per DL BWP +maxNrofPPW-ID-1-r17 INTEGER ::= 15 -- Maximum number of Preconfigured PRS processing windows minus 1 +maxNrOfTxTEGReport-r17 INTEGER ::= 256 -- Maximum number of UE Tx Timing Error Group Report +maxNrOfTxTEG-ID-1-r17 INTEGER ::= 7 -- Maximum number of UE Tx Timing Error Group ID minus 1 +maxNrofPagingSubgroups-r17 INTEGER ::= 8 -- Maximum number of paging subgroups per paging occasion +maxNrofPUCCH-ResourceGroups-1-r16 INTEGER ::= 3 +maxNrofReqComDC-Location-r17 INTEGER ::= 128 -- Maximum number of requested carriers/BWPs combinations for DC location +-- report +maxNrofServingCellsTCI-r16 INTEGER ::= 32 -- Maximum number of serving cells in simultaneousTCI-UpdateList +maxNrofTxDC-TwoCarrier-r16 INTEGER ::= 64 -- Maximum number of UL Tx DC locations reported by the UE for 2CC uplink CA +maxNrofRB-SetGroups-r17 INTEGER ::= 8 -- Maximum number of RB set groups +maxNrofRB-Sets-r17 INTEGER ::= 8 -- Maximum number of RB sets +maxNrofEnhType3HARQ-ACK-r17 INTEGER ::= 8 -- Maximum number of enhanced type 3 HARQ-ACK codebook +maxNrofEnhType3HARQ-ACK-1-r17 INTEGER ::= 7 -- Maximum number of enhanced type 3 HARQ-ACK codebook minus 1 +maxNrofPRS-ResourcesPerSet-r17 INTEGER ::= 64 -- Maximum number of PRS resources for one set +maxNrofPRS-ResourcesPerSet-1-r17 INTEGER ::= 63 -- Maximum number of PRS resources for one set minus 1 +maxNrofPRS-ResourceOffsetValue-1-r17 INTEGER ::= 511 +maxNrofGapId-r17 INTEGER ::= 8 -- Maximum number of measurement gap ID +maxNrofPreConfigPosGapId-r17 INTEGER ::= 16 -- Maximum number of preconfigured positioning measurement gap +maxNrOfGapPri-r17 INTEGER ::= 16 -- Maximum number of gap priority level +maxCEFReport-r17 INTEGER ::= 4 -- Maximum number of CEF reports by the UE +maxNrofMultiplePDSCHs-r17 INTEGER ::= 8 -- Maximum number of PDSCHs in PDSCH TDRA list +maxSliceInfo-r17 INTEGER ::= 8 -- Maximum number of NSAGs +maxCellSlice-r17 INTEGER ::= 16 -- Maximum number of cells supporting the NSAG +maxNrofTRS-ResourceSets-r17 INTEGER ::= 64 -- Maximum number of TRS resource sets +maxNrofSearchSpaceGroups-1-r17 INTEGER ::= 2 -- Maximum number of search space groups minus 1 +maxNrofRemoteUE-r17 INTEGER ::= 32 -- Maximum number of connected L2 U2N Remote UEs +maxDCI-4-2-Size-r17 INTEGER ::= 140 -- Maximum size of DCI format 4-2 +maxFreqMBS-r17 INTEGER ::= 16 -- Maximum number of MBS frequencies reported in MBSInterestIndication +maxNrofDRX-ConfigPTM-r17 INTEGER ::= 64 -- Max number of DRX configuration for PTM provided in MBS broadcast in a +-- cell +maxNrofDRX-ConfigPTM-1-r17 INTEGER ::= 63 -- Max number of DRX configuration for PTM provided in MBS broadcast in a +-- cell minus 1 +maxNrofMBS-ServiceListPerUE-r17 INTEGER ::= 16 -- Maximum number of services which the UE can include in the MBS interest + +``` + +``` + +maxNrofMBS-Session-r17 INTEGER ::= 1024 -- indication +maxNrofMTCH-SSB-MappingWindow-r17 INTEGER ::= 16 -- Maximum number of MTCH to SSB beam mapping pattern +maxNrofMTCH-SSB-MappingWindow-1-r17 INTEGER ::= 15 -- Maximum number of MTCH to SSB beam mapping pattern minus 1 +maxNrofMRB-Broadcast-r17 INTEGER ::= 4 -- Maximum number of broadcast MRBs configured for one MBS broadcast service +maxNrofPageGroup-r17 INTEGER ::= 32 -- Maximum number of paging groups in a paging message +maxNrofPDSCH-ConfigPTM-r17 INTEGER ::= 16 -- Maximum number of PDSCH configuration groups for PTM +maxNrofPDSCH-ConfigPTM-1-r17 INTEGER ::= 15 -- Maximum number of PDSCH configuration groups for PTM minus 1 +maxG-RNTI-r17 INTEGER ::= 16 -- Maximum number of G-RNTI that can be configured for a UE. +maxG-RNTI-1-r17 INTEGER ::= 15 -- Maximum number of G-RNTI that can be configured for a UE minus 1. +maxG-CS-RNTI-r17 INTEGER ::= 8 -- Maximum number of G-CS-RNTI that can be configured for a UE. +maxG-CS-RNTI-1-r17 INTEGER ::= 7 -- Maximum number of G-CS-RNTI that can be configured for a UE minus 1. +maxMRB-r17 INTEGER ::= 32 -- Maximum number of multicast MRBs (that can be added in MRB-ToAddModList) +maxFSAI-MBS-r17 INTEGER ::= 64 -- Maximum number of MBS frequency selection area identities +maxNeighCellMBS-r17 INTEGER ::= 8 -- Maximum number of MBS broadcast neighbour cells +maxNrofPdcch-BlindDetectionMixed-1-r16 INTEGER ::= 7 -- Maximum number of combinations of mixed Rel-16 and Rel-15 PDCCH +-- monitoring capabilities minus 1 +maxNrofPdcch-BlindDetection-r17 INTEGER ::= 16 -- Maximum number of combinations of PDCCH blind detection monitoring +-- capabilities +maxNrofAltitudeRanges-r18 INTEGER ::= 8 -- Maximum number of altitude ranges for altitude-based measurement configurations +maxWayPoint-r18 INTEGER ::= 20 -- Maximum number of flight path information waypoints +maxAltitude-r18 INTEGER ::= 10000 -- Maximum altitude in meters +minAltitude-r18 INTEGER ::= -420 -- Minimum altitude in meters +maxMeasSequence-r18 INTEGER ::= 64 -- Maximum number of configured sequence for measurement +maxNrofHops-r18-1 INTEGER ::= 5 -- Maximum number of Hops that can be configured for Positioning SRS Transmission +maxNrOfCellsInVA-r18 INTEGER ::= 16 -- Maximum number of cells in validity area for Positioning SRS is FFS +maxNrOfLinkedSRS-PosResourceSet-r18 INTEGER ::= 3 -- Value is FFS Maximum number of SRSPosResourceSets that can be aggregated across CCs +maxCBR-ConfigDedSL-PRS-1-r18 INTEGER ::= 7 -- Maximum number of CBR ranges for dedicated SL PRS resource pool +maxCBR-LevelDedSL-PRS-1-r18 INTEGER ::= 15 -- Maximum number of CBR levels for dedicated SL PRS resource pool +maxNrofSL-PRS-TxPool-r18 INTEGER ::= 8 -- Maximum number of Tx dedicated SL-PRS resource pool for NR sidelink positioning is +FFS +maxNrofSL-PRS-TxConfig-r18 INTEGER ::= 64 -- Maximum number of SL PRS transmission parameter configurations +maxNrOfVA-r18 INTEGER ::= 16 -- Maximum number of validity area is FFS +maxNrofLTM-Configs-r18 INTEGER ::= 8 -- Maximum number of LTM candidate cells +maxNrofLTM-Configs-r18-plus-1 INTEGER ::= 9 -- Maximum number of LTM candidate cells plus 1 +maxNrofLTM-CSI-ReportConfigurations-r18 INTEGER ::= 48 -- Maximum number of LTM CSI reporting configurations +maxNrofLTM-CSI-ReportConfigurations-1-r18 INTEGER ::= 47 -- Maximum number of LTM CSI reporting configurations minus 1 +maxNrofLTM-CSI-SSB-ResourcesPerSet-r18 INTEGER ::= 512 -- Maximum number of LTM CSI SSB resource per set +maxNrofLTM-CSI-ResourceConfigurations-r18 INTEGER ::= 112 -- Maximum number of LTM CSI resource configurations +maxNrofLTM-CSI-ResourceConfigurations-r18-1 INTEGER ::= 111 -- Maximum number of LTM CSI resource configurations minus 1 +maxNrofCandidateTCI-State-r18 INTEGER ::= 128 -- Maximum number of LTM TCI states +maxNrofCandidateTCI-State-r18-1 INTEGER ::= 127 -- Maximum number of LTM TCI states minus 1 +maxNrofCandidateUL-TCI-r18 INTEGER ::= 64 -- Maximum number of LTM UL TCI states +maxNrofCandidateUL-TCI-r18-1 INTEGER ::= 63 -- Maximum number of LTM UL TCI states minus 1 +maxSecurityCellSet-r18 INTEGER ::= 9 -- Maximum number of cell sets for subsequent CPAC. +maxSK-Counter-r18 INTEGER ::= 8 -- Maximum number of SK-counters configured for a cell set for subsequent CPAC. +maxNrofThresholdMBS-r18 INTEGER ::= 8 -- Max number of thresholds of MBS sessions for RRC connection resume for a +-- UE receiving multicast in RRC_INACTIVE +maxTN-AreaInfo-r18 INTEGER ::= 32 -- Maximum number of TN coverage areas for which assistance info is +-- provided in an NTN cell +maxNrofSetsOfCells-r18 INTEGER ::= 4 -- Maximum number of sets of cells for multi-cell PDSCH/PUSCH scheduling +maxNrofSetsOfCells-1-r18 INTEGER ::= 3 -- Maximum number of sets of cells for multi-cell PDSCH/PUSCH scheduling +-- minus 1 + +``` + +``` + +maxNrofCellsInSet-r18 INTEGER ::= 4 -- Maximum number of cells configured in a set of cells for multi-cell + -- PDSCH/PUSCH scheduling +maxNrofCellsInSet-1-r18 INTEGER ::= 3 -- Maximum number of cells configured in a set of cells for multi-cell + -- PDSCH/PUSCH scheduling minus 1 +maxNrofCellCombos-r18 INTEGER ::= 16 -- Maximum number of combinations of co-scheduled cells for multi-cell + -- PDSCH/PUSCH scheduling +maxNrofBWPsInSetOfCells-r18 INTEGER ::= 16 -- Maximum number of BWPs configured in a set of cells for multi-cell + -- PDSCH/PUSCH scheduling +maxLowerMSD-r18 INTEGER ::= 256 -- Maximum number of lower MSD capability sets for a victim band +maxLowerMSDInfo-r18 INTEGER ::= 64 -- Maximum number of lower MSD capability sets for a band combination + +-- TAG-MULTIPLICITY-AND-TYPE-CONSTRAINT-DEFINITIONS-STOP +-- ASN1STOP + +``` + +### – End of NR-RRC-Definitions + +``` + +-- ASN1START + +END + +-- ASN1STOP + +``` + +## 6.5 Short Message + +Short Messages can be transmitted on PDCCH using P-RNTI with or without associated *Paging* message using Short Message field in DCI format 1\_0 (see TS 38.212 [17], clause 7.3.1.2.1). + +Table 6.5-1 defines Short Messages. Bit 1 is the most significant bit. + +**Table 6.5-1: Short Messages** + +| Bit | Short Message | +|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | systemInfoModification
If set to 1: indication of a BCCH modification other than SIB6 , SIB7 , SIB8 and posSIBs . | +| 2 | etwsAndCmasIndication
If set to 1: indication of an ETWS primary notification and/or an ETWS secondary notification and/or a CMAS notification. | +| 3 | stopPagingMonitoring
This bit can be used for only operation with shared spectrum channel access and if nrofPDCCH-MonitoringOccasionPerSSB-InPO is present.
If set to 1: indication that the UE may stop monitoring PDCCH occasion(s) for paging in this Paging Occasion as specified in TS 38.304 [20], clause 7.1. | +| 4 | systemInfoModification-eDRX
If set to 1: indication of a BCCH modification other than SIB6 , SIB7 , SIB8 and posSIBs . This indication applies only to UEs using IDLE eDRX cycle longer than the BCCH modification period. | +| 5 – 8 | Not used in this release of the specification, and shall be ignored by UE if received. | + +## 6.6 PC5 RRC messages + +### 6.6.1 General message structure + +#### – *PC5-RRC-Definitions* + +This ASN.1 segment is the start of the PC5 RRC PDU definitions. + +``` +-- ASN1START +-- TAG-PC5-RRC-DEFINITIONS-START + +PC5-RRC-Definitions DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +IMPORTS + ARFCN-ValueNR, + CellAccessRelatedInfo, + SetupRelease, + RRC-TransactionIdentifier, + SN-FieldLengthAM, + SN-FieldLengthUM, + LogicalChannelIdentity, + maxNrofSLRB-r16, + maxNrofSL-RxInfoSet-r17, + maxNrofSL-QFIs-r16, + maxNrofSL-QFIsPerDest-r16, + PagingCycle, + PagingRecord, + RSRP-Range, + SL-MeasConfig-r16, + SL-MeasId-r16, + FreqBandList, + FreqBandIndicatorNR, + GNSS-ID-r16, + maxNrofRelayMeas-r17, + maxSimultaneousBands, + maxBandComb, + maxBands, + maxSIB, + maxSIB-MessagePlus1-r17, + maxSL-LCID-r16, + maxNrofFreqSL-1-r18, + BandParametersSidelink-r16, + PagingRecord-v1700, + RLC-ParametersSidelink-r16, + SBAS-ID-r16, + SIB1, + SL-DRX-ConfigUC-r17, + SL-DRX-ConfigUC-SemiStatic-r17, +``` + +``` + +SL-PagingIdentityRemoteUE-r17, +SL-RLC-ChannelID-r17, +SL-SourceIdentity-r17, +SystemInformation, +maxNrofSL-Dest-r16, +SL-DestinationIdentity-r16, +SL-QoS-FlowIdentity-r16, +SL-QoS-Info-r16 +FROM NR-RRc-Definitions; + +-- TAG-PC5-RRc-DEFINITIONS-STOP +-- ASN1STOP + +``` + +#### – *SBCCH-SL-BCH-Message* + +The *SBCCH-SL-BCH-Message* class is the set of RRc messages that may be sent from the UE to the UE via SL-BCH on the SBCCH logical channel. + +``` + +-- ASN1START +-- TAG-SBCCH-SL-BCH-MESSAGE-START + +SBCCH-SL-BCH-Message ::= SEQUENCE { + message SBCCH-SL-BCH-MessageType +} + +SBCCH-SL-BCH-MessageType ::= CHOICE { + c1 CHOICE { + masterInformationBlockSidelink MasterInformationBlockSidelink, + spare1 NULL + }, + messageClassExtension SEQUENCE {} +} + +-- TAG-SBCCH-SL-BCH-MESSAGE-STOP +-- ASN1STOP + +``` + +#### – *SCCH-Message* + +The *SCCH-Message* class is the set of PC5-RRc messages that may be sent from the UE to the UE for unicast of NR sidelink communication on SCCH logical channel. + +``` + +-- ASN1START +-- TAG-SCCH-MESSAGE-START + +SCCH-Message ::= SEQUENCE { + message SCCH-MessageType +} + +SCCH-MessageType ::= CHOICE { + c1 CHOICE { + measurementReportSidelink MeasurementReportSidelink, + } +} + +``` + +``` + +rrcReconfigurationSidelink RRCReconfigurationSidelink, +rrcReconfigurationCompleteSidelink RRCReconfigurationCompleteSidelink, +rrcReconfigurationFailureSidelink RRCReconfigurationFailureSidelink, +ueCapabilityEnquirySidelink UECapabilityEnquirySidelink, +ueCapabilityInformationSidelink UECapabilityInformationSidelink, +uuMessageTransferSidelink-r17 UuMessageTransferSidelink-r17, +remoteUEInformationSidelink-r17 RemoteUEInformationSidelink-r17 +}, +messageClassExtension CHOICE { +c2 CHOICE { +notificationMessageSidelink-r17 NotificationMessageSidelink-r17, +ueAssistanceInformationSidelink-r17 UEAssistanceInformationSidelink-r17, +ueInformationRequestSidelink-r18 UEInformationRequestSidelink-r18, +ueInformationResponseSidelink-r18 UEInformationResponseSidelink-r18, spare4 NULL, spare3 NULL, spare2 NULL, spare1 NULL +}, +messageClassExtensionFuture-r17 SEQUENCE { +} +} +} + +-- TAG-SCCH-MESSAGE-STOP +-- ASN1STOP + +``` + +### 6.6.2 Message definitions + +#### – *MasterInformationBlockSidelink* + +The *MasterInformationBlockSidelink* includes the system information transmitted by a UE via SL-BCH. + +Signalling radio bearer: N/A + +RLC-SAP: TM + +Logical channel: SBCCH + +Direction: UE to UE + +#### ***MasterInformationBlockSidelink*** + +``` + +-- ASN1START +-- TAG-MASTERINFORMATIONBLOCKSIDELINK-START + +MasterInformationBlockSidelink ::= SEQUENCE { +sl-TDD-Config-r16 BIT STRING (SIZE (12)), +inCoverage-r16 BOOLEAN, +directFrameNumber-r16 BIT STRING (SIZE (10)), +slotIndex-r16 BIT STRING (SIZE (7)), +reservedBits-r16 BIT STRING (SIZE (2)) +} + +``` + +``` +-- TAG-MASTERINFORMATIONBLOCKSIDELINK-STOP +-- ASN1STOP +``` + +| MasterInformationBlockSidelink field descriptions | | +|----------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| directFrameNumber | Indicates the frame number in which S-SSB transmitted. | +| inCoverage | Value true indicates that the UE transmitting the MasterInformationBlockSidelink is in network coverage, or UE selects GNSS timing as the synchronization reference source. | +| slotIndex | Indicates the slot index in which S-SSB transmitted. | + +#### – ***MeasurementReportSidelink*** + +The *MeasurementReportSidelink* message is used for the indication of measurement results of NR sidelink. + +Signalling radio bearer: SL-SRB3 + +RLC-SAP: AM + +Logical channel: SCCH + +Direction: UE to UE + +#### ***MeasurementReportSidelink message*** + +``` +-- ASN1START +-- TAG-MEASUREMENTREPORTSIDELINK-START + +MeasurementReportSidelink ::= + criticalExtensions + measurementReportSidelink-r16 + criticalExtensionsFuture + } +} + +MeasurementReportSidelink-r16-IEs ::= + sl-MeasResults-r16 + lateNonCriticalExtension + nonCriticalExtension +} + +SL-MeasResults-r16 ::= + sl-MeasId-r16 + sl-MeasResult-r16 + ... +} + +SEQUENCE { + CHOICE { + MeasurementReportSidelink-r16-IEs, + SEQUENCE {} + } +} + +SEQUENCE { + SL-MeasResults-r16, + OCTET STRING + SEQUENCE{} +} + +OPTIONAL, +OPTIONAL + +SEQUENCE { + SL-MeasId-r16, + SL-MeasResult-r16, +} +``` + +``` + +SL-MeasResult-r16 ::= + sl-ResultDMRS-r16 + ... + [[ + sl-Result-SL-PRS-r18 + ]] +} + +SL-MeasQuantityResult-r16 ::= + sl-RSRP-r16 + ... + [[ + sl-Rsrp-DedicatedSL-PRS-RP-r18 + ]] +} + +SL-MeasResultListRelay-r17 ::= + SEQUENCE (SIZE (1..maxNrofRelayMeas-r17)) OF SL-MeasResultRelay-r17 + +SL-MeasResultRelay-r17 ::= + cellIdentity-r17 + sl-RelayUE-Identity-r17 + sl-MeasResult-r17 + ... + [[ + sl-MeasQuantity-r18 + ]] +} + +-- TAG-MEASUREMENTREPORTSIDELINK-STOP +-- ASN1STOP + +``` + +| MeasurementReportSidelink field descriptions | +|--------------------------------------------------------------------------------------------------------------| +| sl-MeasId
Identifies the sidelink measurement identity for which the reporting is being performed. | +| sl-MeasResult
Measured RSRP results of a unicast destination. | +| sl-Rsrp-DedicatedSL-PRS-RP
Measured SL PRS-based filtered RSRP. | + +#### – **NotificationMessageSidelink** + +The *NotificationMessageSidelink* message is used to send notification message from U2N Relay UE to the connected U2N Remote UE or from U2U Relay UE to the connected U2U Remote UE. + +Signalling radio bearer: SL-SRB3 + +RLC-SAP: AM + +Logical channel: SCCH + +Direction: U2N Relay UE to U2N Remote UE or U2U Relay UE to U2U Remote UE + +#### ***NotificationMessageSidelink message*** + +``` +-- ASN1START +-- TAG-NOTIFICATIONMESSAGESIDELINK-START + +NotificationMessageSidelink-r17 ::= SEQUENCE { + criticalExtensions CHOICE { + notificationMessageSidelink-r17 NotificationMessageSidelink-r17-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +NotificationMessageSidelink-r17-IEs ::= SEQUENCE { + indicationType-r17 ENUMERATED { + relayUE-Uu-RLF, relayUE-HO, relayUE-CellReselection, + relayUE-Uu-RRc-Failure + } OPTIONAL, -- Need N + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension NotificationMessageSidelink-v1800-IEs OPTIONAL +} + +NotificationMessageSidelink-v1800-IEs ::= SEQUENCE { + sl-IndicationType-r18 ENUMERATED {relayUE-PC5-RLF, spare1} OPTIONAL, -- Need N + sl-DestinationIdentityRemoteUE-r18 SL-DestinationIdentity-r16 OPTIONAL, -- Need N + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +-- TAG-NOTIFICATIONMESSAGESIDELINK -STOP +-- ASN1STOP +``` + +#### ***RemoteUEInformationSidelink*** + +The *RemoteUEInformationSidelink* message is used to request SIB(s) or provide paging related information as specified in clause 5.8.9.8.1. + +Signalling radio bearer: SL-SRB3 + +RLC-SAP: AM + +Logical channel: SCCH + +Direction: L2 U2N Remote UE to L2 U2N Relay UE + +#### ***RemoteUEInformationSidelink message*** + +``` +-- ASN1START +-- TAG-REMOTEUEINFORMATIONSIDELINK-START +``` + +``` + +RemoteUEInformationSidelink-r17 ::= + criticalExtensions + remoteUEInformationSidelink-r17 + criticalExtensionsFuture + } +} + +RemoteUEInformationSidelink-r17-IEs ::= + sl-RequestedSIB-List-r17 + sl-PagingInfo-RemoteUE-r17 + lateNonCriticalExtension + nonCriticalExtension +} + +RemoteUEInformationSidelink-v1800-IEs ::= + sl-RequestedPosSIB-List-r18 + sl-SFN-DFN-OffsetRequested-r18 + connectionForMP-r18 + lateNonCriticalExtension + nonCriticalExtension +} + +SL-RequestedSIB-List-r17 ::= + SEQUENCE (SIZE (maxSIB-MessagePlus1-r17)) OF SL-SIB-ReqInfo-r17 + +SL-PagingInfo-RemoteUE-r17 ::= + sl-PagingIdentityRemoteUE-r17 + sl-PagingCycleRemoteUE-r17 +} + +SL-SIB-ReqInfo-r17 ::= + ENUMERATED { sib1, sib2, sib3, sib4, sib5, sib6, sib7, sib8, sib9, sib10, sib11, sib12, sib13, + sib14, sib15, sib16, sib17, sib18, sib19, sib20, sib21, sibNotReq11, sibNotReq10, sibNotReq9, + sibNotReq8, sibNotReq7, sibNotReq6, sibNotReq5, sibNotReq4, sibNotReq3, sibNotReq2, + sibNotReq1, ... } + +SL-RequestedPosSIB-List-r18 ::= + SEQUENCE (SIZE (1..maxSIB)) OF SL-PosSIB-ReqInfo-r18 + +SL-PosSIB-ReqInfo-r18 ::= + gnss-id-r18 + sbas-id-r18 + posSibType-r18 +} + +SEQUENCE { + CHOICE { + RemoteUEInformationSidelink-r17-IEs, + SEQUENCE {} + } +} + +SEQUENCE { + SetupRelease { SL-RequestedSIB-List-r17 } OPTIONAL, -- Need M + SetupRelease { SL-PagingInfo-RemoteUE-r17 } OPTIONAL, -- Need M + OCTET STRING OPTIONAL, + RemoteUEInformationSidelink-v1800-IEs OPTIONAL +} + +SEQUENCE { + SetupRelease { SL-RequestedPosSIB-List-r18 } OPTIONAL, -- Need M + ENUMERATED { true } OPTIONAL, -- Need R + ENUMERATED {true} OPTIONAL, -- Need N + OCTET STRING OPTIONAL, + SEQUENCE {} OPTIONAL +} + +SEQUENCE { + SL-PagingIdentityRemoteUE-r17, + PagingCycle OPTIONAL -- Need M +} + +SEQUENCE { + GNSS-ID-r16 OPTIONAL, -- Need R + SBAS-ID-r16 OPTIONAL, -- Cond GNSS-ID-SBAS + ENUMERATED { posSibType1-1, posSibType1-2, posSibType1-3, posSibType1-4, posSibType1-5, posSibType1-6, + posSibType1-7, posSibType1-8, posSibType1-9, posSibType1-10, 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, posSibType6-4, posSibType6-5, posSibType6-6, ... } +} + +-- TAG-REMOTEUEINFORMATIONSIDELINK-STOP +-- ASN1STOP + +``` + +| RemoteUEInformationSidelink-IEs field descriptions | | +|-----------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| connectionForMP | Indicates the connected L2 U2N Relay UE by the L2 U2N Remote UE that the access is for MP. | +| sl-PagingCycleRemoteUE | Indicates the L2 U2N Remote UE's UE specific DRX cycle as the minimum value of the one provided by upper layers (if configured) and the one provided by RRC layer (if configured). Value rf32 corresponds to 32 radio frames, value rf64 corresponds to 64 radio frames and so on. | +| sl-PagingIdentityRemoteUE | Indicates the L2 U2N Remote UE's paging UE ID. | +| sl-PagingInfo-RemoteUE | Indicates the paging information used by L2 U2N Relay UE to perform the connected L2 U2N Remote UE's paging monitoring. | +| sl-RequestedPosSIB-List | Contains a list of requested PosSIBs. | +| sl-RequestedSIB-List | Contains a list of requested SIBs. | +| sl-SFN-DFN-OffsetRequested | If present, this field indicates that the L2 U2N Remote UE requests the L2 U2N Relay UE to provide the SFN-DFN offset in a subsequent RRCReconfigurationSidelink message. | +| SL-SIB-Reqlnfo | Indicates the requested SIB type. Values sibNotReq11, sibNotReq10, ..., sibNotReq1 shall be ignored by L2 U2N relay UE (i.e., no SIB requested). | + +| Conditional presence | Explanation | +|-----------------------------|--------------------------------------------------------------------------------------------------| +| GNSS-ID-SBAS | The field is mandatory present if gnss-id is set to sbas . It is absent otherwise. | + +#### — *RRCReconfigurationSidelink* + +The *RRCReconfigurationSidelink* message is the command to AS configuration of the PC5 RRC connection. It is only applied to unicast of NR sidelink communication. + +Signalling radio bearer: SL-SRB3 + +RLC-SAP: AM + +Logical channel: SCCH + +Direction: UE to UE + +##### *RRCReconfigurationSidelink* message + +``` +-- ASN1START +-- TAG-RRCRECONFIGURATIONSIDELINK-START + +RRCReconfigurationSidelink ::= SEQUENCE { + rrc-TransactionIdentifier-r16 RRC-TransactionIdentifier, +``` + +``` + + criticalExtensions CHOICE { + rrcReconfigurationSidelink-r16 RRCReconfigurationSidelink-r16-IEs, + criticalExtensionsFuture SEQUENCE {} + } + } + } + + RRCReconfigurationSidelink-r16-IEs := SEQUENCE { + slrb-ConfigToAddModList-r16 SEQUENCE (SIZE (1..maxNrofSLRB-r16)) OF SLRB-Config-r16 OPTIONAL, -- Need N + slrb-ConfigToReleaseList-r16 SEQUENCE (SIZE (1..maxNrofSLRB-r16)) OF SLRB-PC5-ConfigIndex-r16 OPTIONAL, -- Need N + sl-MeasConfig-r16 SetupRelease { SL-MeasConfig-r16 } OPTIONAL, -- Need M + sl-CSI-RS-Config-r16 SetupRelease { SL-CSI-RS-Config-r16 } OPTIONAL, -- Need M + sl-ResetConfig-r16 ENUMERATED {true} OPTIONAL, -- Need N + sl-LatencyBoundCSI-Report-r16 INTEGER (3..160) OPTIONAL, -- Need M + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension RRCReconfigurationSidelink-v1700-IEs OPTIONAL + } + + RRCReconfigurationSidelink-v1700-IEs := SEQUENCE { + sl-DRX-ConfigUC-PC5-r17 SetupRelease { SL-DRX-ConfigUC-r17 } OPTIONAL, -- Need M + sl-LatencyBoundIUC-Report-r17 SetupRelease { SL-LatencyBoundIUC-Report-r17 } OPTIONAL, -- Need M + sl-RLC-ChannelToReleaseListPC5-r17 SEQUENCE (SIZE (1..maxSL-LCID-r16)) OF SL-RLC-ChannelID-r17 OPTIONAL, -- Need N + sl-RLC-ChannelToAddModListPC5-r17 SEQUENCE (SIZE (1..maxSL-LCID-r16)) OF SL-RLC-ChannelConfigPC5-r17 OPTIONAL, -- Need N + nonCriticalExtension RRCReconfigurationSidelink-v1800-IEs OPTIONAL + } + + RRCReconfigurationSidelink-v1800-IEs := SEQUENCE { + sl-SFN-DFN-Offset-r18 SetupRelease { SL-SFN-DFN-Offset-r18 } OPTIONAL, -- Need M + sl-CarrierToAddModList-r18 SEQUENCE (SIZE (1..maxNrofFreqSL-1-r18)) OF SL-CarrierConfig-r18 OPTIONAL, -- Need N + sl-CarrierToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofFreqSL-1-r18)) OF SL-CarrierId-r18 OPTIONAL, -- Need N + sl-RLC-BearerToAddModList-r18 SEQUENCE (SIZE (1..maxNrofSLRB-r16)) OF SL-RLC-BearerConfig-r18 OPTIONAL, -- Need N + sl-RLC-BearerToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofSLRB-r16)) OF SL-RLC-BearerConfigIndex-r18 OPTIONAL, -- Need N + sl-LocalID-PairToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-DestinationIdentity-r16 OPTIONAL, -- Need N + sl-LocalID-PairToAddModList-r18 SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-SRAP-ConfigPC5-r18 OPTIONAL, -- Need N + nonCriticalExtension SEQUENCE {} OPTIONAL + } + + SL-CarrierConfig-r18 := SEQUENCE { + sl-Carrier-Id-r18 SL-CarrierId-r18, + sl-OffsetToCarrier-r18 INTEGER (0..2199), + sl-AbsoluteFrequencyPointA-r18 ARFCN-ValueNR OPTIONAL -- Need R + } + + SL-CarrierId-r18 := INTEGER (0..maxNrofFreqSL-1-r18) + + SL-RLC-BearerConfig-r18 := CHOICE { + srb SEQUENCE { + sl-SRB-IdentityWithDuplication INTEGER (1..3), + sl-RLC-BearerConfigIndex-r18 SL-RLC-BearerConfigIndex-r18, + ... + }, + drb SEQUENCE { + slrb-PC5-ConfigIndex-r18 SLRB-PC5-ConfigIndex-r16, + sl-RLC-BearerConfigIndex-r18 SL-RLC-BearerConfigIndex-r18, + } + } + +``` + +``` + + sl-RLC-ConfigPC5-r18 SL-RLC-ConfigPC5-r16 OPTIONAL, -- Need M + sl-MAC-LogicalChannelConfigPC5-r18 SL-LogicalChannelConfigPC5-r16 OPTIONAL, -- Need M + ... + } +} + +SL-RLC-BearerConfigIndex-r18 ::= INTEGER (1..maxSL-LCID-r16) + +SL-LatencyBoundIUC-Report-r17 ::= INTEGER (3..160) + +SLRB-Config-r16 ::= SEQUENCE { + slrb-PC5-ConfigIndex-r16 SLRB-PC5-ConfigIndex-r16, + sl-SDAP-ConfigPC5-r16 SL-SDAP-ConfigPC5-r16 OPTIONAL, -- Need M + sl-PDCP-ConfigPC5-r16 SL-PDCP-ConfigPC5-r16 OPTIONAL, -- Need M + sl-RLC-ConfigPC5-r16 SL-RLC-ConfigPC5-r16 OPTIONAL, -- Need M + sl-MAC-LogicalChannelConfigPC5-r16 SL-LogicalChannelConfigPC5-r16 OPTIONAL, -- Need M + ... +} + +SLRB-PC5-ConfigIndex-r16 ::= INTEGER (1..maxNrofSLRB-r16) + +SL-SDAP-ConfigPC5-r16 ::= SEQUENCE { + sl-MappedQoS-FlowsToAddList-r16 SEQUENCE (SIZE (1.. maxNrofSL-QFIsPerDest-r16)) OF SL-PQFI-r16 OPTIONAL, -- Need N + sl-MappedQoS-FlowsToReleaseList-r16 SEQUENCE (SIZE (1.. maxNrofSL-QFIsPerDest-r16)) OF SL-PQFI-r16 OPTIONAL, -- Need N + sl-SDAP-Header-r16 ENUMERATED {present, absent}, + ... +} + +SL-PDCP-ConfigPC5-r16 ::= SEQUENCE { + sl-PDCP-SN-Size-r16 ENUMERATED {len12bits, len18bits} OPTIONAL, -- Need M + sl-OutOfOrderDelivery-r16 ENUMERATED { true } OPTIONAL, -- Need R + ... +} + +SL-RLC-ConfigPC5-r16 ::= CHOICE { + sl-AM-RLC-r16 SEQUENCE { + sl-SN-FieldLengthAM-r16 SN-FieldLengthAM OPTIONAL, -- Need M + ... + }, + sl-UM-Bi-Directional-RLC-r16 SEQUENCE { + sl-SN-FieldLengthUM-r16 SN-FieldLengthUM OPTIONAL, -- Need M + ... + }, + sl-UM-Uni-Directional-RLC-r16 SEQUENCE { + sl-SN-FieldLengthUM-r16 SN-FieldLengthUM OPTIONAL, -- Need M + ... + } +} + +SL-LogicalChannelConfigPC5-r16 ::= SEQUENCE { + sl-LogicalChannelIdentity-r16 LogicalChannelIdentity, + ... +[[ + +``` + +``` + + sl-LogicalChannelIdentity-v1800 INTEGER (33..38) + ]] +} + +SL-PQFI-r16 ::= INTEGER (1..64) + +SL-CSI-RS-Config-r16 ::= SEQUENCE { + sl-CSI-RS-FreqAllocation-r16 CHOICE { + sl-OneAntennaPort-r16 BIT STRING (SIZE (12)), + sl-TwoAntennaPort-r16 BIT STRING (SIZE (6)) + } + sl-CSI-RS-FirstSymbol-r16 INTEGER (3..12) + ... +} + +SL-RLC-ChannelConfigPC5-r17 ::= SEQUENCE { + sl-RLC-ChannelID-PC5-r17 SL-RLC-ChannelID-r17, + sl-RLC-ConfigPC5-r17 SL-RLC-ConfigPC5-r16 + sl-MAC-LogicalChannelConfigPC5-r17 SL-LogicalChannelConfigPC5-r16 + ... +} + +SL-SFN-DFN-Offset-r18 ::= SEQUENCE { + sl-FrameOffset-r18 INTEGER (0..1023), + sl-SubframeOffset-r18 INTEGER (0..9), + sl-SlotOffset-r18 INTEGER (0..31) +} + +SL-SRAP-ConfigPC5-r18 ::= SEQUENCE { + sl-PeerRemoteUE-L2Identity-r18 SL-DestinationIdentity-r16 + sl-PeerRemoteUE-LocalIdentity-r18 INTEGER (0..255) + sl-RemoteUE-L2Identity-r18 SL-SourceIdentity-r17 + sl-RemoteUE-LocalIdentity-r18 INTEGER (0..255) + ... +} + +-- TAG-RRCRECONFIGURATIONSIDELINK-STOP +-- ASN1STOP + +``` + +Editor's note: Whether the field *sl-AbsoluteFrequencyPointA*, together with *sl-OffsetToCarrier*, is sufficient for Rx UE to understand the carrier to add/modify/release from Rx UE perspective. + +| RRCReconfigurationSidelink field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-AbsoluteFrequencyPointA
Absolute frequency of the reference resource block (Common RB 0). Its lowest subcarrier is also known as Point A. | +| sl-CarrierToAddModList
Indicate the carrier(s) to be added/modified for transmission by UE transmitting RRCReconfigurationSidelink message | +| sl-CarrierToReleaseList
Indicate the carrier(s) to be released for the transmission by UE transmitting RRCReconfigurationSidelink message. | +| sl-CSI-RS-FreqAllocation
Indicates the frequency domain position for sidelink CSI-RS. | +| sl-CSI-RS-FirstSymbol
Indicates the position of first symbol of sidelink CSI-RS. | +| sl-DRX-ConfigUC-PC5
Indicates the NR sidelink DRX configuration for unicast communication, as specified in TS 38.321 [3] | +| sl-LatencyBoundCSI-Report
Indicates the latency bound of SL CSI report from the associated SL CSI triggering in terms of number of slots. | +| sl-LatencyBoundUC-Report
Indicates the latency bound of SL Inter-UE coordination report from the associated SL Inter-UE coordination explicit request triggering in terms of number of slots. | +| sl-LogicalChannelIdentity
Indicates the identity of the sidelink logical channel. | +| sl-MappedQoS-FlowsToAddList
Indicate the QoS flows to be mapped to the configured sidelink DRB. Each entry is indicated by the SL-PQFI , which is used between UEs, as defined in TS 23.287 [55]. | +| sl-MappedQoS-FlowsToReleaseList
Indicate the QoS flows to be released from the configured sidelink DRB. Each entry is indicated by the SL-PQFI , which is used between UEs, as defined in TS 23.287 [55]. | +| sl-MeasConfig
Indicates the sidelink measurement configuration for the unicast destination. | +| sl-OffsetToCarrier
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 subcarrierSpacing defined for this carrier). The maximum value corresponds to $275 \cdot 8 - 1$ . See TS 38.211 [16], clause 4.4.2. | +| sl-OutOfOrderDelivery
Indicates whether or not outOfOrderDelivery specified in TS 38.323 [5] is configured. This field should be either always present or always absent, after the sidelink radio bearer is established. | +| sl-PDCP-SN-Size
Indicates the PDCP SN size of the configured sidelink DRB. | +| sl-Resetconfig
Indicates that the full configuration should be applicable for the RRCReconfigurationSidelink message. | +| sl-RLC-BearerToAddModList
Indicate the additional Sidelink RLC bearer to be added / modified for the configured sidelink DRB. | +| sl-RLC-BearerToReleaseList
Indicate the additional Sidelink RLC bearer to be released for the configured sidelink DRB. | +| sl-SDAP-Header
Indicates whether or not a SDAP header is present on this sidelink DRB. | +| sl-SFN-DFN-Offset
Indicates the SFN-DFN offset to be used for determining the SFN timeline based on the DFN timeline. | +| sl-SRB-IdentityWithDuplication
Indicate the sidelink SRB for which duplication is configured. | + +##### **slrb-PC5-ConfigIndex** + +Indicates the identity of the configuration of a sidelink DRB. In case of L2 U2U relay, only value 4-31 can be signaled for end-to-end sidelink DRB, and all other values are reserved. + +##### **SL-SRAP-ConfigPC5 field descriptions** + +##### **sl-RemoteUE-LocalIdentity** + +Indicates the local UE ID of the L2 U2U Remote UE used in SRAP as specified in TS 38.351 [66]. + +##### **sl-RemoteUE-L2Identity** + +Indicates the Source L2 ID of the L2 U2U Remote UE as specified in TS 23.304 [65]. + +##### **sl-PeerRemoteUE-LocalIdentity** + +Indicates the local UE ID of the peer L2 U2U Remote UE used in SRAP as specified in TS 38.351 [66]. + +##### **sl-PeerRemoteUE-L2Identity** + +Indicates the Source L2 ID of the peer L2 U2U Remote UE as specified in TS 23.304 [65]. + +#### — *RRReconfigurationCompleteSidelink* + +The *RRReconfigurationCompleteSidelink* message is used to confirm the successful completion of a PC5 RRC AS reconfiguration. It is only applied to unicast of NR sidelink communication. + +Signalling radio bearer: SL-SRB3 + +RLC-SAP: AM + +Logical channel: SCCH + +Direction: UE to UE + +##### ***RRReconfigurationCompleteSidelink* message** + +``` +-- ASN1START +-- TAG-RRRECONFIGURATIONCOMPLETESIDELINK-START + +RRReconfigurationCompleteSidelink := SEQUENCE { + rrc-TransactionIdentifier-r16 RRC-TransactionIdentifier, + criticalExtensions CHOICE { + rrcReconfigurationCompleteSidelink-r16 RRReconfigurationCompleteSidelink-r16-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +RRReconfigurationCompleteSidelink-r16-IEs := SEQUENCE { + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension RRReconfigurationCompleteSidelink-v1710-IEs OPTIONAL +} + +RRReconfigurationCompleteSidelink-v1710-IEs := SEQUENCE { +``` + +``` + + dummy ENUMERATED {true}, + nonCriticalExtension RRCReconfigurationCompleteSidelink-v1720-IEs OPTIONAL +} + +RRCReconfigurationCompleteSidelink-v1720-IEs ::= SEQUENCE { + sl-DRX-ConfigReject-v1720 ENUMERATED {true} OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +-- TAG-RRCRECONFIGURATIONCOMPLETESIDELINK-STOP +-- ASN1STOP + +``` + +##### ***RRCReconfigurationCompleteSidelink* field descriptions** + +##### ***dummy*** + +This field is not used in the specification. The UE shall not include this field. If received it shall be ignored by the peer UE. + +##### ***sl-DRX-ConfigReject*** + +Indicates the rejection of sidelink DRX configuration received from the peer UE for the corresponding NR sidelink unicast communication. + +#### – ***RRCReconfigurationFailureSidelink*** + +The *RRCReconfigurationFailureSidelink* message is used to indicate the failure of a PC5 RRC AS reconfiguration. It is only applied to unicast of NR sidelink communication. + +Signalling radio bearer: SL-SRB3 + +RLC-SAP: AM + +Logical channel: SCCH + +Direction: UE to UE + +##### ***RRCReconfigurationFailureSidelink* message** + +``` + +-- ASN1START +-- TAG-RRCRECONFIGURATIONFAILURESIDELINK-START + +RRCReconfigurationFailureSidelink ::= SEQUENCE { + rrc-TransactionIdentifier-r16 RRC-TransactionIdentifier, + criticalExtensions CHOICE { + rrcReconfigurationFailureSidelink-r16 RRCReconfigurationFailureSidelink-r16-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +RRCReconfigurationFailureSidelink-r16-IEs ::= SEQUENCE { + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +``` + +``` + +} +-- TAG-RRCRECONFIGURATIONFAILURESIDELINK-STOP +-- ASN1STOP + +``` + +#### – ***UEAssistanceInformationSidelink*** + +The *UEAssistanceInformationSidelink* message may include sidelink DRX assistance information used to determine the sidelink DRX configuration. + +Signalling radio bearer: SL-SRB3 + +RLC-SAP: AM + +Logical channel: SCCH + +Direction: UE to UE + +##### ***UEAssistanceInformationSidelink* message** + +``` + +-- ASN1START +-- TAG-UEASSISTANCEINFORMATIONSIDELINK-START + +UEAssistanceInformationSidelink-r17 ::= SEQUENCE { + criticalExtensions CHOICE { + ueAssistanceInformationSidelink-r17 UEAssistanceInformationSidelink-r17-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +UEAssistanceInformationSidelink-r17-IEs ::= SEQUENCE { + sl-PreferredDRX-ConfigList-r17 SEQUENCE (SIZE (1..maxNrofSL-RxInfoSet-r17)) OF SL-DRX-ConfigUC-SemiStatic-r17 + OPTIONAL, -- Need R + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +-- TAG-UEASSISTANCEINFORMATIONSIDELINK-STOP +-- ASN1STOP + +``` + +| UEAssistanceInformationSidelink field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-PreferredDRX-ConfigList
Indicates a list of the reference sidelink DRX configurations provided by a UE to a peer UE for determining the sidelink DRX configuration. | + +#### – *UECapabilityEnquirySidelink* + +The *UECapabilityEnquirySidelink* message is used to request UE sidelink capabilities. It is only applied to unicast of NR sidelink communication. + +Signalling radio bearer: SL-SRB3 + +RLC-SAP: AM + +Logical channel: SCCH + +Direction: UE to UE + +##### *UECapabilityEnquirySidelink* message + +``` +-- ASN1START +-- TAG-UECAPABILITYENQUIRYSIDELINK-START + +UECapabilityEnquirySidelink ::= SEQUENCE { + rrc-TransactionIdentifier-r16 RRC-TransactionIdentifier, + criticalExtensions CHOICE { + ueCapabilityEnquirySidelink-r16 UECapabilityEnquirySidelink-r16-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +UECapabilityEnquirySidelink-r16-IEs ::= SEQUENCE { + frequencyBandListFilterSidelink-r16 FreqBandList OPTIONAL, -- Need N + ue-CapabilityInformationSidelink-r16 OCTET STRING OPTIONAL, -- Need N + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension SEQUENCE{} OPTIONAL +} + +-- TAG-UECAPABILITYENQUIRYSIDELINK-STOP +-- ASN1STOP +``` + +##### *UECapabilityEnquirySidelink-IEs* field descriptions + +| | | +|------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| frequencyBandListFilterSidelink | This field is used to indicate frequency bands for which the peer UE is requested to provide supported bands and band combinations for NR sidelink communications. The UE always provides this field. | +| ue-CapabilityInformationSidelink | This field indicates the UECapabilityInformationSidelink message to provide the UE sidelink capability, which can be optionally sent together with UECapabilityEnquirySidelink . | + +#### – *UECapabilityInformationSidelink* + +The *UECapabilityInformationSidelink* message is used to transfer UE radio access capabilities. It is only applied to unicast of NR sidelink communication. + +Signalling radio bearer: SL-SRB3 + +RLC-SAP: AM + +Logical channel: SCCH + +Direction: UE to UE + +##### ***UECapabilityInformationSidelink message*** + +``` +-- ASN1START +-- TAG-UECAPABILITYINFORMATIONSIDELINK-START + +UECapabilityInformationSidelink ::= SEQUENCE { + rrc-TransactionIdentifier-r16 RRC-TransactionIdentifier, + criticalExtensions CHOICE { + ueCapabilityInformationSidelink-r16 UECapabilityInformationSidelink-r16-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +UECapabilityInformationSidelink-r16-IEs ::= SEQUENCE { + accessStratumReleaseSidelink-r16 AccessStratumReleaseSidelink-r16, + pdcp-ParametersSidelink-r16 PDCP-ParametersSidelink-r16 OPTIONAL, + rlc-ParametersSidelink-r16 RLC-ParametersSidelink-r16 OPTIONAL, + supportedBandCombinationListSidelinkNR-r16 BandCombinationListSidelinkNR-r16 OPTIONAL, + supportedBandListSidelink-r16 SEQUENCE (SIZE (1..maxBands)) OF BandSidelinkPC5-r16 OPTIONAL, + appliedFreqBandListFilter-r16 FreqBandList OPTIONAL, + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension UECapabilityInformationSidelink-v1700-IEs OPTIONAL +} + +UECapabilityInformationSidelink-v1700-IEs ::= SEQUENCE { + mac-ParametersSidelink-r17 MAC-ParametersSidelink-r17 OPTIONAL, + supportedBandCombinationListSidelinkNR-v1710 BandCombinationListSidelinkNR-v1710 OPTIONAL, + nonCriticalExtension UECapabilityInformationSidelink-v1800-IEs OPTIONAL +} + +UECapabilityInformationSidelink-v1800-IEs ::= SEQUENCE { + sfn-DFN-OffsetSupported-r18 ENUMERATED { supported } OPTIONAL, + posSIB-ForwardingSupported-r18 ENUMERATED { supported } OPTIONAL, + pdcp-ParametersSidelink-r18 PDCP-ParametersSidelink-r18 OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +PDCP-ParametersSidelink-r18 ::= SEQUENCE { + pdcp-DuplicationSRB-sidelink-r18 ENUMERATED {supported} OPTIONAL, + pdcp-DuplicationDRB-sidelink-r18 ENUMERATED {supported} OPTIONAL, + ... +} +``` + +``` + +MAC-ParametersSidelink-r17 ::= SEQUENCE { + drx-OnSidelink-r17 ENUMERATED {supported} OPTIONAL, + ... +} + +AccessStratumReleaseSidelink-r16 ::= ENUMERATED { rel16, rel17, rel18, spare5, spare4, spare3, spare2, spare1, ... } + +PDCP-ParametersSidelink-r16 ::= SEQUENCE { + outOfOrderDeliverySidelink-r16 ENUMERATED {supported} OPTIONAL, + ... +} + +BandCombinationListSidelinkNR-r16 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombinationParametersSidelinkNR-r16 + +BandCombinationListSidelinkNR-v1710 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombinationParametersSidelinkNR-v1710 + +BandCombinationParametersSidelinkNR-r16 ::= SEQUENCE (SIZE (1..maxSimultaneousBands)) OF BandParametersSidelink-r16 + +BandCombinationParametersSidelinkNR-v1710 ::= SEQUENCE (SIZE (1..maxSimultaneousBands)) OF BandParametersSidelink-v1710 + +BandParametersSidelink-v1710 ::= SEQUENCE { + --32-5a-1 + tx-IUC-Scheme1-Mode2Sidelink-r17 ENUMERATED {supported} OPTIONAL, + --32-5b-1 + tx-IUC-Scheme2-Mode2Sidelink-r17 ENUMERATED {n4, n8, n16} OPTIONAL +} + +BandSidelinkPC5-r16 ::= SEQUENCE { + freqBandSidelink-r16 FreqBandIndicatorNR, + --15-1 + sl-Reception-r16 SEQUENCE { + harq-RxProcessSidelink-r16 ENUMERATED {n16, n24, n32, n64}, + psucch-RxSidelink-r16 ENUMERATED {value1, value2}, + scs-CP-PatternRxSidelink-r16 CHOICE { + fr1-r16 SEQUENCE { + scs-15kHz-r16 BIT STRING (SIZE (16)) OPTIONAL, + scs-30kHz-r16 BIT STRING (SIZE (16)) OPTIONAL, + scs-60kHz-r16 BIT STRING (SIZE (16)) OPTIONAL + }, + fr2-r16 SEQUENCE { + scs-60kHz-r16 BIT STRING (SIZE (16)) OPTIONAL, + scs-120kHz-r16 BIT STRING (SIZE (16)) OPTIONAL + } + } OPTIONAL, + extendedCP-RxSidelink-r16 ENUMERATED {supported} OPTIONAL, + OPTIONAL, + } + --15-10 + sl-Tx-256QAM-r16 ENUMERATED {supported} OPTIONAL, + --15-12 + lowSE-64QAM-MCS-TableSidelink-r16 ENUMERATED {supported} OPTIONAL, + ... + [[ + --15-14 + ]] +``` + +``` + +csi-ReportSidelink-r16 SEQUENCE { + csi-RS-PortsSidelink-r16 ENUMERATED {p1, p2} +} OPTIONAL, +--15-19 +rankTwoReception-r16 ENUMERATED {supported} +--15-23 OPTIONAL, +sl-openLoopPC-RSRP-ReportSidelink-r16 ENUMERATED {supported} +--13-1 OPTIONAL, +sl-Rx-256QAM-r16 ENUMERATED {supported} +]], OPTIONAL +[[ +--32-5a-2 +rx-IUC-Scheme1-PreferredMode2Sidelink-r17 ENUMERATED {supported} +--32-5a-3 OPTIONAL, +rx-IUC-Scheme1-NonPreferredMode2Sidelink-r17 ENUMERATED {supported} +--32-5b-2 OPTIONAL, +rx-IUC-Scheme2-Mode2Sidelink-r17 ENUMERATED {n5, n15, n25, n32, n35, n45, n50, n64} OPTIONAL, +--32-6-1 +rx-IUC-Scheme1-SCI-r17 ENUMERATED {supported} +--32-6-2 OPTIONAL, +rx-IUC-Scheme1-SCI-ExplicitReq-r17 ENUMERATED {supported} +--32-7 OPTIONAL, +scheme2-ConflictDeterminationRSRP-r17 ENUMERATED {supported} +]], OPTIONAL +[[ +-- R4 45-2: SL reception in intra-carrier guard band +sl-ReceptionIntraCarrierGuardBand-r18 ENUMERATED {supported} +]] OPTIONAL +} + +-- TAG-UECAPABILITYINFORMATIONSIDELINK-STOP +-- ASN1STOP + +``` + +#### – ***UEInformationRequestSidelink*** + +The *UEInformationRequestSidelink* message is used to transfer UE information in sidelink, e.g. the end-to-end QoS information for L2 U2U Relay operation. + +Signalling radio bearer: SL-SRB3 + +RLC-SAP: AM + +Logical channel: SCCH + +Direction: L2 U2U Remote UE to L2 U2U Relay UE + +##### ***UEInformationRequestSidelink message*** + +``` + +-- ASN1START +-- TAG-UEINFORMATIONREQUESTSIDELINK-START + +``` + +``` + +UEInformationRequestSidelink-r18 ::= SEQUENCE { + rrc-TransactionIdentifier-r18 RRC-TransactionIdentifier, + criticalExtensions CHOICE { + ueInformationRequestSidelink-r18 UEInformationRequestSidelink-r18-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +UEInformationRequestSidelink-r18-IEs ::= SEQUENCE { + sl-E2E-QoS-ConnectionListPC5-r18 SEQUENCE (SIZE (1.. maxNrofSL-Dest-r16)) OF SL-E2E-QoS-ConnectionPC5-r18 OPTIONAL, -- Need N + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +SL-E2E-QoS-ConnectionPC5-r18 ::= SEQUENCE { + sl-DestinationIdentityRemoteUE-r18 SL-DestinationIdentity-r16, + sl-QoS-InfoList-r18 SEQUENCE (SIZE (1..maxNrofSL-QFIsPerDest-r16)) OF SL-QoS-Info-r16 +} + +-- TAG-UEINFORMATIONREQUESTSIDELINK-STOP +-- ASN1STOP + +``` + +##### ***UEInformationRequestSidelink field descriptions*** + +##### ***SL-E2E-QoS-ConnectionListPC5*** + +Indicates the QoS info for a list of end-to-end PC5 connections with each connection indicated by the destination L2 ID of the peer L2 U2U Remote UE. + +#### — ***UEInformationResponseSidelink*** + +The *UEInformationResponseSidelink* message is used to deliver UE information in sidelink, e.g. the split QoS information for L2 U2U Relay operation. + +Signalling radio bearer: SL-SRB3 + +RLC-SAP: AM + +Logical channel: SCCH + +Direction: L2 U2U Relay UE to L2 U2U Remote UE + +##### ***UEInformationResponseSidelink message*** + +``` + +-- ASN1START +-- TAG-UEINFORMATIONRESPONSESIDELINK-START + +UEInformationResponseSidelink-r18 ::= SEQUENCE { + rrc-TransactionIdentifier-r18 RRC-TransactionIdentifier, + criticalExtensions CHOICE { + +``` + +``` + + ueInformationResponseSidelink-r18 UEInformationResponseSidelink-r18-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +UEInformationResponseSidelink-r18-IEs ::= SEQUENCE { + sl-SplitQoS-ConnectionListPC5-r18 SEQUENCE (SIZE (1.. maxNrofSL-Dest-r16)) OF SL-SplitQoS-ConnectionPC5-r18 OPTIONAL, -- Need N + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +SL-SplitQoS-ConnectionPC5-r18 ::= SEQUENCE { + sl-DestinationIdentityRemoteUE-r18 SL-DestinationIdentity-r16, + sl-SplitQoS-InfoList-r18 SEQUENCE (SIZE (1.. maxNrofSL-QFIsPerDest-r16)) OF SL-SplitQoS-Info-r18 +} + +SL-SplitQoS-Info-r18 ::= SEQUENCE { + sl-QoS-FlowIdentity-r18 SL-QoS-FlowIdentity-r16, + sl-SplitPacketDelayBudget-r18 INTEGER (0..1023) OPTIONAL -- Need M +} + +-- TAG-UEINFORMATIONRESPONSESIDELINK-STOP +-- ASN1STOP + +``` + +##### UEInformationResponseSidelink field descriptions + +##### **sl-SplitQoS-ConnectionListPC5** + +Indicates the split PDB on the first PC5 hop between L2 U2U Relay UE and the L2 U2U Remote UE for a list of end-to-end connection. + +#### – ***UuMessageTransferSidelink*** + +The *UuMessageTransferSidelink* message is used for the sidelink transfer of Paging message and System Information messages. + +Signalling radio bearer: SL-SRB3 + +RLC-SAP: AM + +Logical channel: SCCH + +Direction: L2 U2N Relay UE to L2 U2N Remote UE + +##### ***UuMessageTransferSidelink* message** + +``` + +-- ASN1START +-- TAG-UUMESSAGETRANSFERSIDELINK-START + +UuMessageTransferSidelink-r17 ::= SEQUENCE { + +``` + +``` + +criticalExtensions CHOICE { + uuMessageTransferSidelink-r17 UuMessageTransferSidelink-r17-IEs, + criticalExtensionsFuture SEQUENCE {} +} + +UuMessageTransferSidelink-r17-IEs ::= SEQUENCE { + sl-PagingDelivery-r17 OCTET STRING (CONTAINING PagingRecord) OPTIONAL, -- Need N + sl-SIB1-Delivery-r17 OCTET STRING (CONTAINING SIB1) OPTIONAL, -- Need N + sl-SystemInformationDelivery-r17 OCTET STRING (CONTAINING SystemInformation) OPTIONAL, -- Need N + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension UuMessageTransferSidelink-v1800-IEs OPTIONAL +} + +UuMessageTransferSidelink-v1800-IEs ::= SEQUENCE { + sl-PagingDelivery-r18 OCTET STRING (CONTAINING PagingRecord-v1700) OPTIONAL, -- Need N + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +-- TAG-UUMESSAGETRANSFERSIDELINK-STOP +-- ASN1STOP + +``` + +##### ***UuMessageTransferSidelink-IEs field descriptions*** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-PagingDelivery
This field is used to transfer PagingRecord and PagingRecord-v1700 relevant to the L2 U2N Remote UE in RRC_IDLE or RRC_INACTIVE. | +| sl-SIB1-Delivery
This field is used to transfer SIB1 to the L2 U2N Remote UE in RRC_IDLE or RRC_INACTIVE. | +| sl-SystemInformationDelivery
This field is used to transfer SIBs and posSIBs to the L2 U2N Remote UE in RRC_IDLE or RRC_INACTIVE. | + +— ***End of PC5-RRC-Definitions*** + +``` + +-- ASN1START + +END + +-- ASN1STOP + +``` + +# 7 Variables and constants + +## 7.1 Timers + +### 7.1.1 Timers (Informative) + +| Timer | Start | Stop | At expiry | +|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------| +| T300 | Upon transmission of RRCSsetupRequest . | Upon reception of RRCSsetup or RRCReject message, cell re-selection, relay reselection, and upon abortion of connection establishment by upper layers. | Perform the actions as specified in 5.3.3.7. | +| T301 | Upon transmission of RRCReestablishmentRequest | Upon reception of RRCReestablishment or RRCSsetup message as well as when the selected cell becomes unsuitable or the (re)selected L2 U2N Relay UE becomes unsuitable, upon reception of NotificationMessageSidelink indicating relayUE-HO or relayUE-CellReselection . | Go to RRC_IDLE | +| T302 | Upon reception of RRCReject while performing RRC connection establishment or resume, upon reception of RRCRelease with waitTime . | Upon entering RRC_CONNECTED or RRC_IDLE, upon cell re-selection, upon cell change due to relay (re)selection, and upon reception of RRCReject message. | Inform upper layers about barring alleviation as specified in 5.3.14.4 | + +| Timer | Start | Stop | At expiry | +|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| T304 |

Upon reception of RRCREconfiguration message including reconfigurationWithSync for the MCG which does not include sl-PathSwitchConfig, or upon reception of RRCREconfiguration message including reconfigurationWithSync for the SCG not indicated as deactivated in the NR or E-UTRA message containing the RRCREconfiguration message or upon conditional reconfiguration execution i.e. when applying a stored RRCREconfiguration message including reconfigurationWithSync.

Also, for the MCG and SCG upon an indication from lower layer that an LTM cell switch procedure is triggered and, for the MCG, upon performing an LTM cell switch procedure following cell selection performed while timer T311 is running.

|

Upon successful completion of random access on the corresponding SpCell. In case of a reconfiguration with sync without performing random access procedure, upon receiving a PDCCH transmission addressed to C-RNTI after first UL transmission, for the same HARQ process. In case of an LTM cell switch without performing a random access procedure, upon receiving a PDCCH transmission addressed to C-RNTI after first UL transmission, for the same HARQ process. Upon receiving an indication from lower layers of successful completion of Rach-less handover.

For T304 of SCG, upon SCG release.

|

For T304 of MCG, in case of the handover from NR or intra-NR handover, or path switch from a L2 U2N Relay UE to a NR cell, or a reconfiguration with sync without performing random access procedure, or an LTM cell switch procedure, initiate the RRC re-establishment procedure; In case of handover to NR, perform the actions defined in the specifications applicable for the source RAT. If any DAPS bearer is configured and if there is no RLF in source PCell, initiate the failure information procedure.

For T304 of SCG, inform network about the reconfiguration with sync failure by initiating the SCG failure information procedure as specified in 5.7.3.

| + +| Timer | Start | Stop | At expiry | +|-------|---------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| T310 | Upon detecting physical layer problems for the SpCell i.e. upon receiving N310 consecutive out-of-sync indications from lower layers. | Upon receiving N311 consecutive in-sync indications from lower layers for the SpCell, upon receiving RRCReconfiguration with reconfigurationWithSync for that cell group, upon reception of MobilityFromNRCommand , upon the reconfiguration of rf-TimersAndConstant , upon initiating the connection re-establishment procedure, upon conditional reconfiguration execution i.e. when applying a stored RRCReconfiguration message including reconfigurationWithSync for that cell group, and upon initiating the MCG failure information procedure.
Upon SCG release, if the T310 is kept in SCG. | If the T310 is kept in MCG: If AS security is not activated: go to RRC_IDLE else: initiate the MCG failure information procedure as specified in 5.7.3b or the connection re-establishment procedure as specified in 5.3.7 or the procedure as specified in 5.3.10.3 if any DAPS bearer is configured.
If the T310 is kept in SCG, Inform E-UTRAN/NR about the SCG radio link failure by initiating the SCG failure information procedure as specified in 5.7.3. | +| T311 | Upon initiating the RRC connection re-establishment procedure | Upon selection of a suitable NR cell, or upon selection of a suitable L2 U2N Relay UE, or a cell using another RAT. | Enter RRC_IDLE | + +| Timer | Start | Stop | At expiry | +|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| T312 |

If T312 is configured in MCG: Upon triggering a measurement report for a measurement identity for which T312 has been configured and useT312 has been set to true, while T310 in PCell is running.

If T312 is configured in SCG and useT312 has been set to true: Upon triggering a measurement report for a measurement identity for which T312 has been configured, while T310 in PSCell is running.

|

Upon receiving N311 consecutive in-sync indications from lower layers for the SpCell, receiving RRCREconfiguration with reconfigurationWithSync for that cell group, upon reception of MobilityFromNRCommand, upon initiating the connection re-establishment procedure, upon the reconfiguration of rf-TimersAndConstant, upon initiating the MCG failure information procedure, upon conditional reconfiguration execution i.e. when applying a stored RRCREconfiguration message including reconfigurationWithSync for that cell group, and upon the expiry of T310 in corresponding SpCell.

Upon SCG release, if the T312 is kept in SCG

|

If the T312 is kept in MCG initiate the MCG failure information procedure as specified in 5.7.3b or the connection re-establishment procedure.

If the T312 is kept in SCG, Inform E-UTRAN/NR about the SCG radio link failure by initiating the SCG failure information procedure.as specified in 5.7.3.

| +| T316 | Upon transmission of the MCGFailureInformation message |

Upon receiving RRCRElease, RRCREconfiguration with reconfigurationwithSync for the PCell, MobilityFromNRCommand, or upon initiating the re-establishment procedure

| Perform the actions as specified in 5.7.3b.5. | +| T319 | Upon transmission of RRCREsumeRequest or RRCREsumeRequest1 when the resume procedure is not initiated for SDT. | Upon reception of RRCREsume , RRCSetup , RRCRElease , RRCRElease with suspendConfig or RRCREject message, upon cell re-selection or upon relay (re)selection. | Perform the actions as specified in 5.3.13.5. | +| T319a | Upon transmission of RRCREsumeRequest or RRCREsumeRequest1 when the resume procedure is initiated for SDT. | Upon reception of RRCREsume , RRCSetup , RRCRElease , RRCREject message or upon failure to resume RRC connection for SDT as specified in 5.3.13.5 or upon cell reselection. | Perform the actions as specified in 5.3.13.5. | + +| Timer | Start | Stop | At expiry | +|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------| +| T320 | Upon reception of t320 or upon cell (re)selection to NR from another RAT with validity time configured for dedicated priorities (in which case the remaining validity time is applied). | Upon entering RRC_CONNECTED , upon reception of RRRelease , when PLMN selection or SNPN selection is performed on request by NAS, when the UE enters RRC_IDLE from RRC_INACTIVE , or upon cell (re)selection to another RAT (in which case the timer is carried on to the other RAT). | Discard the cell reselection priority information provided by dedicated signalling. | +| T321 | Upon receiving measConfig including a reportConfig with the reportType set to reportCGI | Upon acquiring the information needed to set all fields of cgi-info , upon receiving measConfig that includes removal of the reportConfig with the reportType set to reportCGI and upon detecting that a cell is not broadcasting SIB1. | Initiate the measurement reporting procedure, stop performing the related measurements. | +| T322 | Upon receiving measConfig including reportConfigNR with the reportType set to reportSFTD and drx-SFTD-NeighMeas is set to true . | Upon acquiring the SFTD measurement results, upon receiving measConfig that includes removal of the reportConfig with the reportType set to reportSFTD . | Initiate the measurement reporting procedure, stop performing the related measurements. | +| T325 | Upon reception of RRRelease message with deprioritisationTimer . | | Stop deprioritisation of all frequencies or NR signalled by RRRelease . | +| T330 | Upon receiving LoggedMeasurementConfiguration message | Upon log volume exceeding the suitable UE memory, upon initiating the release of LoggedMeasurementConfiguration procedure | Perform the actions specified in 5.5a.1.4 | +| T331 | Upon receiving RRRelease message with measIdleDuration | Upon receiving RRSetup , RRResume , RRRelease with idle/inactive measurement configuration, upon cell selection/reselection to a cell that does not belong to the validityArea (if configured), or upon cell re-selection to another RAT. | Perform the actions as specified in 5.7.8.3. | + +| Timer | Start | Stop | At expiry | +|-----------------------------------------------------------------------|--------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------| +| T342 | Upon transmitting UEAssistanceInformation message with DelayBudgetReport . | Upon releasing delayBudgetReportingConfig during the connection re-establishment/resume procedures, and upon receiving delayBudgetReportingConfig set to release . | No action. | +| T345 | Upon transmitting UEAssistanceInformation message with overheatingAssistance | Upon releasing overheatingAssistanceConfig during the connection re-establishment procedure, upon initiating the connection resumption procedure, and upon receiving overheatingAssistanceConfig set to release . | No action. | +| T346a
(The UE maintains one instance of this timer per cell group) | Upon transmitting UEAssistanceInformation message with drx-Preference . | Upon releasing drx-PreferenceConfig during the connection re-establishment/resume procedures, upon receiving drx-PreferenceConfig set to release , or upon performing MR-DC release. | No action. | +| T346b
(The UE maintains one instance of this timer per cell group) | Upon transmitting UEAssistanceInformation message with maxBW-Preference . | Upon releasing maxBW-PreferenceConfig during the connection re-establishment/resume procedures, upon receiving maxBW-PreferenceConfig set to release , or upon performing MR-DC release. | No action. | +| T346c
(The UE maintains one instance of this timer per cell group) | Upon transmitting UEAssistanceInformation message with maxCC-Preference . | Upon releasing maxCC-PreferenceConfig during the connection re-establishment/resume procedures, upon receiving maxCC-PreferenceConfig set to release , or upon performing MR-DC release. | No action. | + +| Timer | Start | Stop | At expiry | +|-----------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------| +| T346d
(The UE maintains one instance of this timer per cell group) | Upon transmitting UEAssistanceInformation message with maxMIMO-LayerPreference . | Upon releasing maxMIMO-LayerPreferenceConfig during the connection re-establishment/resume procedures, upon receiving maxMIMO-LayerPreferenceConfig set to release , or upon performing MR-DC release. | No action. | +| T346e
(The UE maintains one instance of this timer per cell group) | Upon transmitting UEAssistanceInformation message with minSchedulingOffsetPreference . | Upon releasing minSchedulingOffsetPreferenceConfig during the connection re-establishment/resume procedures, upon receiving minSchedulingOffsetPreferenceConfig set to release , or upon performing MR-DC release. | No action. | +| T346f | Upon transmitting UEAssistanceInformation message with releasePreference . | Upon releasing releasePreferenceConfig during the connection re-establishment/resume procedures, or upon receiving releasePreferenceConfig set to release . | No action. | +| T346g | Upon transmitting UEAssistanceInformation message with musim-PreferredRRC-State . | Upon receiving RRRelease , or upon receiving musim-LeaveAssistanceConfig set to release . | Perform the actions as specified in 5.3.8.6. | +| T346h | Upon transmitting UEAssistanceInformation message with musim-GapPreferenceList or musim-GapPriorityPreferenceList Information . | Upon releasing musim-GapAssistanceConfig during the connection re-establishment/resume procedures, or upon receiving musim-GapAssistanceConfig set to release . | No action. | +| T346i | Upon transmitting UEAssistanceInformation message with scg-DeactivationPreference | Upon releasing scg-DeactivationPreferenceConfig during RRC connection re-establishment/resume or upon receiving scg-DeactivationPreferenceConfig set to release . | No action. | + +| Timer | Start | Stop | At expiry | +|--------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------| +| T346j (The UE maintains one instance of this timer per cell group) | Upon transmitting UEAssistanceInformation message with rlm-RelaxationReportingConfig . | Upon releasing rlm-RelaxationReportingConfig during the connection re-establishment/resume procedures, upon receiving rlm-RelaxationReportingConfig set to release , or upon performing MR-DC release. | No action. | +| T346k (The UE maintains one instance of this timer per cell group) | Upon transmitting UEAssistanceInformation message with bfd-RelaxationReportingConfig . | Upon releasing bfd-RelaxationReportingConfig during the connection re-establishment/resume procedures, upon receiving bfd-RelaxationReportingConfig set to release , or upon performing MR-DC release. | No action. | +| T346l (The UE maintains one instance of this timer per QoS flow) | Upon transmitting UEAssistanceInformation message with ul-TrafficInfo for the concerned QoS flow. | Upon releasing ul-TrafficInfoReportingConfig during the connection re-establishment/resume procedures, or upon receiving ul-TrafficInfoReportingConfig set to release . | No action. | +| T346m | Upon transmitting UEAssistanceInformation message with multiRx-PreferenceFR2 . | Upon releasing multiRx-PreferenceReportingConfigFR2 during the connection re-establishment/resume procedures, upon receiving multiRx-PreferenceReportingConfigFR2 set to release . | No action. | +| T346n | Upon transmission of MUSIM temporary restriction of musim-CapRestriction for constraint combination of bands and/or band(s) or combination bands to avoid | Upon releasing musim-CapabilityRestrictionConfig during the connection re-establishment/resume procedures, or upon receiving musim-CapabilityRestrictionConfig set to release . | No action. | + +| Timer | Start | Stop | At expiry | +|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| T348 | Upon transmission of MUSIM temporary restriction of musim-CapRestriction for serving cell(s) with capabilities restricted, release of SCell or release of SCG. | Upon reception of RRCReconfiguration message that does not exceed UE temporary capability restriction transmitted via musim-CapRestriction . | UE may apply the temporary UE capability restriction in accordance with the one indicated in the last transmission of the UEAssistanceInformation message including musim-CapRestriction . | +| T350 | Upon transmitting DedicatedSIBRequest message with requestedSIB-List and/or requestedPosSIB-List . | Upon acquiring the requested SIB(s) or posSIB(s), upon releasing onDemandSIB-Request during the connection re-establishment procedures, upon receiving onDemandSIB-Request set to release, upon reception of RRCRelease or upon successful change of PCell while in RRC_CONNECTED. | No action | +| T380 | Upon reception of t380 in RRCRelease . | Upon reception of RRCResume , RRCSetup or RRCRelease . | Perform the actions as specified in 5.3.13. | +| T390 | When access attempt is barred at access barring check for an Access Category. The UE maintains one instance of this timer per Access Category. | Upon cell (re)selection, upon relay (re)selection, upon entering RRC_CONNECTED, upon reception of RRCReconfiguration including reconfigurationWithSync , upon change of PCell while in RRC_CONNECTED, upon reception of MobilityFromNRCommand , or upon reception of RRCRelease . | Perform the actions as specified in 5.3.14.4. | +| T400 | Upon transmission of RRCReconfigurationSidelink | Upon reception of RRCReconfigurationFailureSidelink or RRCReconfigurationCompleteSidelink | Perform the Sidelink radio link failure related actions as specified in 5.8.9.3. | +| T420 | Upon reception of the RRCReconfiguration message including sl-PathSwitchConfig | Upon successfully sending RRCReconfigurationComplete message (i.e., PC5 RLC acknowledgement is received from target L2 U2N Relay UE) | Perform the RRC re-establishment procedure as specified in 5.3.7. | + +| Timer | Start | Stop | At expiry | +|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------| +| T421 | Upon reception of the RRCREconfiguration message including sl-IndirectPathAddChange | Upon successfully sending RRCREconfigurationComplete message (i.e., PC5 RLC acknowledgement is received from target L2 U2N Relay UE) if split SRB1 with duplication is configured; | Perform the Failure Information Reporting as specified in 5.7.3c. | +| T430 | Start or restart from the subframe indicated by epochTime upon reception of SIB19, or upon reception of RRCREconfiguration message for the target cell including reconfigurationWithSync , or upon conditional reconfiguration execution i.e. when applying a stored RRCREconfiguration message for the target cell including reconfigurationWithSync . | Stop T430, if it is running, for the source cell upon reception of RRCREconfiguration message including reconfigurationWithSync , or upon conditional reconfiguration execution i.e. when applying a stored RRCREconfiguration message including reconfigurationWithSync . | Perform the actions as specified in 5.2.2.6. | + +Editor's Note: FFS the stop condition for other cases, i.e. PC5-RRC trigger, CONNECTED relay UE. + +### 7.1.2 Timer handling + +When the UE applies zero value for a timer, the timer shall be started and immediately expire unless explicitly stated otherwise. + +## 7.2 Counters + +| Counter | Reset | Incremented | When reaching max value | +|---------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|-------------------------| +| N310 | Upon reception of "in-sync" indication from lower layers; upon receiving RRCReconfiguration with reconfigurationWithSync for that cell group; upon initiating the connection re-establishment procedure. | Upon reception of "out-of-sync" from lower layer while the timer T310 is stopped. | Start timer T310 | +| N311 | Upon reception of "out-of-sync" indication from lower layers; upon receiving RRCReconfiguration with reconfigurationWithSync for that cell group; upon initiating the connection re-establishment procedure. | Upon reception of the "in-sync" from lower layer while the timer T310 is running. | Stop the timer T310. | + +## 7.3 Constants + +| Constant | Usage | +|----------|---------------------------------------------------------------------------------------------------| +| N310 | Maximum number of consecutive "out-of-sync" indications for the SpCell received from lower layers | +| N311 | Maximum number of consecutive "in-sync" indications for the SpCell received from lower layers | + +## 7.4 UE variables + +NOTE: To facilitate the specification of the UE behavioural requirements, UE variables are represented using ASN.1. Unless explicitly specified otherwise, it is however up to UE implementation how to store the variables. The optionality of the IEs in ASN.1 is used only to indicate that the values may not always be available. + +### – NR-UE-Variables + +This ASN.1 segment is the start of the NR UE variable definitions. + +-- ASN1START + +``` +-- NR-UE-VARIABLES-START +``` + +``` +NR-UE-Variables DEFINITIONS AUTOMATIC TAGS ::= +``` + +``` +BEGIN +``` + +``` +IMPORTS +``` + +``` + AreaConfiguration-r17, + ARFCN-ValueNR, + CellIdentity, + EUTRA-PhysCellId, + maxCEFReport-r17, + MeasId, + MeasIdToAddModList, + MeasIdleCarrierEUTRA-r16, + MeasIdleCarrierNR-r16, + MeasResultIdleEUTRA-r16, + MeasResultIdleNR-r16, + MeasObjectToAddModList, + MeasConfigAppLayerId-r17, + MeasConfigAppLayer-r17, + maxNrofAppLayerMeas-r17, + AppLayerIdleInactiveConfig-r18, + PhysCellId, + RNTI-Value, + ReportConfigToAddModList, + RSRP-Range, + SL-MeasId-r16, + SL-MeasIdList-r16, + SL-MeasObjectList-r16, + SL-ReportConfigList-r16, + SL-QuantityConfig-r16, + Tx-PoolMeasList-r16, + QuantityConfig, + maxNrofCellMeas, + maxNrofMeasId, + maxFreqIdle-r16, + PhysCellIdEUTRA-FDD-r16, + ValidityAreaList-r16, + CondReconfigToAddModList-r16, + ConnEstFailReport-r16, + LoggingDuration-r16, + LoggingInterval-r16, + LogMeasInfoList-r16, + LogMeasInfo-r16, + RA-Report-r16, + RLF-Report-r16, + TraceReference-r16, + WLAN-Identifiers-r16, + WLAN-NameList-r16, + BT-NameList-r16, + PLMN-Identity, + maxNrofRelayMeas-r17, +``` + +``` + +maxPLMN, +RA-ReportList-r16, +VisitedCellInfoList-r16, +AbsoluteTimeInfo-r16, +LoggedEventTriggerConfig-r16, +LoggedPeriodicalReportConfig-r16, +Sensor-NameList-r16, +SL-SourceIdentity-r17, +SuccessHO-Report-r17, +PLMN-IdentityList2-r16, +AreaConfiguration-r16, +maxNrofSL-MeasId-r16, +maxNrofFreqSL-r16, +maxNrofCLI-RSSI-Resources-r16, +maxNrofCLI-SRS-Resources-r16, +RSSI-ResourceId-r16, +SRS-ResourceId, +VisitedPSCellInfoList-r17, +SuccessPSCell-Report-r18, +maxNPN-r16, +SNPN-ConfigIDList-r18, +AreaConfiguration-v1800, +NID-r16, +LTM-Candidate-r18, +LTM-CSI-ResourceConfig-r18, +SK-CounterConfiguration-r18, +ReferenceConfiguration-r18, +maxNrofLTM-Configs-r18, +maxNrofLTM-CSI-ResourceConfigurations-r18, +maxSecurityCellSet-r18 + +FROM NR-RRC-Definitions; + +-- NR-UE-VARIABLES-STOP +-- ASN1STOP + +``` + +### — *VarAppLayerIdleConfig* + +The UE variable *VarAppLayerIdleConfig* includes the parameters of the application layer measurements stored in the UE while in RRC\_IDLE. + +#### ***VarAppLayerIdleConfig* UE variable** + +``` + +-- ASN1START +-- TAG-VARAPPLAYERIDLECONFIG-START + +VarAppLayerIdleConfig-r18-IEs ::= SEQUENCE { + idleInactiveConfigList-r18 SEQUENCE (SIZE (1..maxNrofAppLayerMeas-r17)) OF VarAppLayerIdle-r18 +} + +VarAppLayerIdle-r18 ::= SEQUENCE { + +``` + +``` + + measConfigAppLayerId-r18 MeasConfigAppLayerId-r17, + serviceType-r18 ENUMERATED {streaming, mtsi, vr, spare5, spare4, spare3, spare2, spare1}, + appLayerIdleInactiveConfig-r18 AppLayerIdleInactiveConfig-r18, + appLayerMeasPriority-r18 INTEGER (1..16) OPTIONAL + } + +-- TAG-VARAPPLAYERIDLECONFIG-STOP +-- ASN1STOP + +``` + +#### – *VarAppLayerPLMN-LisConfig* + +The UE variable *VarAppLayerPLMN-ListConfig* includes the PLMNs to which application layer measurement reports and application layer measurement configurations are allowed to be sent. + +#### *VarAppLayerPLMN-ListConfig* UE variable + +``` + +-- ASN1START +-- TAG-VARAPPLAYERPLMN-LISTCONFIG-START + +VarAppLayerPLMN-ListConfig-r18-IEs ::= SEQUENCE { + plmnConfigList-r18 SEQUENCE (SIZE (1..maxNrofAppLayerMeas-r17)) OF VarAppLayerPLMN-List-r18 +} + +VarAppLayerPLMN-List-r18 ::= SEQUENCE { + measConfigAppLayerId-r18 MeasConfigAppLayerId-r17, + plmn-IdentityList-r18 PLMN-IdentityList2-r16 +} + +-- TAG-VARAPPLAYERPLMN-LISTCONFIG-STOP +-- ASN1STOP + +``` + +#### – *VarConditionalReconfig* + +The UE variable *VarConditionalReconfig* includes the accumulated configuration of the conditional handover, conditional PSCell addition or conditional PSCell change configurations including the pointers to conditional handover, conditional PSCell addition, conditional PSCell change, or subsequent CPAC execution condition (associated *measId(s)*), the stored target candidate SpCell *RRCREconfiguration*, the stored reference configuration, and the stored *SK-Counter* configuration. + +#### *VarConditionalReconfig* UE variable + +``` + +-- ASN1START +-- TAG-VARCONDITIONALRECONFIG-START + +VarConditionalReconfig ::= SEQUENCE { + condReconfigList CondReconfigToAddModList-r16 OPTIONAL, + scpac-ReferenceConfiguration-r18 ReferenceConfiguration-r18 OPTIONAL, + sk-CounterConfiguration-r18 SK-CounterConfiguration-r18 OPTIONAL +} + +``` + +``` +-- TAG-VARCONDITIONALRECONFIG-STOP +-- ASN1STOP +``` + +#### — *VarConnEstFailReport* + +The UE variable *VarConnEstFailReport* includes the connection establishment failure and/or connection resume failure information. + +#### ***VarConnEstFailReport* UE variable** + +``` +-- ASN1START +-- TAG-VARCONNESTFAILREPORT-START + +VarConnEstFailReport-r16 ::= SEQUENCE { + connEstFailReport-r16 ConnEstFailReport-r16, + network-Identity-r18 CHOICE { + plmn-Identity-r18 PLMN-Identity, + snpn-Identity-r18 SNPN-Identity-r18 + } +} + +SNPN-Identity-r18 ::= SEQUENCE { + plmn-Identity-r18 PLMN-Identity, + nid-r18 NID-r16 +} + +-- TAG-VARCONNESTFAILREPORT-STOP +-- ASN1STOP +``` + +#### — *VarConnEstFailReportList* + +The UE variable *VarConnEstFailReportList* includes a list of the connection establishment failure and/or connection resume failure information. + +#### ***VarConnEstFailReportList* UE variable** + +``` +-- ASN1START +-- TAG-VARCONNESTFAILREPORTLIST-START + +VarConnEstFailReportList-r17 ::= SEQUENCE { + connEstFailReportList-r17 SEQUENCE (SIZE (1..maxCEFReport-r17)) OF VarConnEstFailReport-r16 +} + +-- TAG-VARCONNESTFAILREPORTLIST-STOP +-- ASN1STOP +``` + +#### — *VarEventID* + +The UE variable *VarEventID* includes information about the current value of *eventID-TSS* received in SIB9 or in *DLInformationTransfer*. + +#### ***VarEventID* UE variable** + +``` +-- ASN1START +-- TAG-VAREVENTID-START + +VarEventID-r18 ::= SEQUENCE { + storedEventID INTEGER +} + +-- TAG-VAREVENTID-STOP +-- ASN1STOP +``` + +#### — *VarGnbID* + +The UE variable *VarGnbID* includes information about the current value of *GnbID* received as the value of *gNB-ID-Length* leftmost bits of the 36-bit long *cellIdentity* in the first *PLMN-IdentityInfo* IE of *PLMN-IdentityInfoList* in SIB1. + +#### ***VarGnbID* UE variable** + +``` +-- ASN1START +-- TAG-VARGNBID-START + +VarGnbID-r18 ::= SEQUENCE { + storedGnbID BIT STRING (SIZE (32)) +} + +-- TAG-VARGNBID-STOP +-- ASN1STOP +``` + +#### — *VarLogMeasConfig* + +The UE variable *VarLogMeasConfig* includes the configuration of the logging of measurements to be performed by the UE while in *RRC\_IDLE*, *RRC\_INACTIVE*, covering intra-frequency, inter-frequency and inter-RAT mobility related measurements. The UE performs logging of measurements only while in *RRC\_IDLE* and *RRC\_INACTIVE*. + +#### ***VarLogMeasConfig* UE variable** + +``` +-- ASN1START +-- TAG-VARLOGMEASCONFIG-START + +VarLogMeasConfig-r16-IEs ::= SEQUENCE { + areaConfiguration-r16 AreaConfiguration-r16 OPTIONAL, + bt-NameList-r16 BT-NameList-r16 OPTIONAL, + wlan-NameList-r16 WLAN-NameList-r16 OPTIONAL, +``` + +``` + +sensor-NameList-r16 Sensor-NameList-r16 OPTIONAL, +loggingDuration-r16 LoggingDuration-r16, +reportType CHOICE { + periodical LoggedPeriodicalReportConfig-r16, + eventTriggered LoggedEventTriggerConfig-r16 +}, +earlyMeasIndication-r17 ENUMERATED {true} OPTIONAL, +areaConfiguration-r17 AreaConfiguration-r17 OPTIONAL, +areaConfiguration-v1800 AreaConfiguration-v1800 OPTIONAL +} +-- TAG-VARLOGMEASCONFIG-STOP +-- ASN1STOP + +``` + +#### — *VarLogMeasReport* + +The UE variable *VarLogMeasReport* includes the logged measurements information. + +#### *VarLogMeasReport* UE variable + +``` + +-- ASN1START +-- TAG-VARLOGMEASREPORT-START + +VarLogMeasReport-r16 ::= SEQUENCE { + absoluteTimeInfo-r16 AbsoluteTimeInfo-r16, + traceReference-r16 TraceReference-r16, + traceRecordingSessionRef-r16 OCTET STRING (SIZE (2)), + tce-Id-r16 OCTET STRING (SIZE (1)), + logMeasInfoList-r16 LogMeasInfoList-r16, + sigLoggedMeasType-r17 ENUMERATED {true}, + identityList-r18 CHOICE { + plmn-IdentityList-r18 PLMN-IdentityList2-r16, + snpn-ConfigIDList-r18 SNPN-ConfigIDList-r18 + } +} + +-- TAG-VARLOGMEASREPORT-STOP +-- ASN1STOP + +``` + +#### — *VarLTM-Config* + +The IE *VarLTM-Config* is used to store the reference configuration and the LTM candidate configurations. + +#### *VarLTM-Config* UE variable + +``` + +-- ASN1START +-- TAG-VARLTM-CONFIG-START + +VarLTM-Config-r18-IEs ::= SEQUENCE { + +``` + +``` + + ltm-ReferenceConfiguration-r18 ReferenceConfiguration-r18, + ltm-CandidateList-r18 SEQUENCE (SIZE (1..maxNrofLTM-Configs-r18)) OF LTM-Candidate-r18, + ltm-CSI-ResourceConfigList-r18 SEQUENCE (SIZE (1..maxNrofLTM-CSI-ResourceConfigurations-r18)) OF LTM-CSI-ResourceConfig-r18 +} + +-- TAG-VARLTM-CONFIG-STOP +-- ASN1STOP + +``` + +#### – ***VarLTM-ServingCellNoResetID*** + +The IE *VarLTM-ServingCellNoResetID* is used to store the serving cell ID based on which the UE determines whether a L2 reset is needed or not upon an LTM cell switch procedure. + +#### ***VarLTM-ServingCellNoResetID* UE variable** + +``` + +-- ASN1START +-- TAG-VARLTM-SERVINGCELLNORESETID-START + +VarLTM-ServingCellNoResetID-r18-IEs ::= SEQUENCE { + ltm-ServingCellNoResetID-r18 INTEGER +} + +-- TAG-VARLTM-SERVINGCELLNORESETID-STOP +-- ASN1STOP + +``` + +#### – ***VarLTM-ServingCellUE-MeasuredTA-ID*** + +The IE *VarLTM-ServingCellUE-MeasuredTA-ID* is used to store the serving cell ID based on which the UE determines whether UE-based TA measurements are needed or not upon an LTM cell switch procedure. + +#### ***VarLTM-ServingCellUE-MeasuredTA-ID* UE variable** + +``` + +-- ASN1START +-- TAG-VARLTM-SERVINGCELLUE-MEASUREDTA-ID-START + +VarLTM-ServingCellUeMeasuredTA-ID-r18-IEs ::= SEQUENCE { + ltm-ServingCellUE-MeasuredTA-ID-r18 INTEGER +} + +-- TAG-VARLTM-SERVINGCELLUE-MEASUREDTA-ID-STOP +-- ASN1STOP + +``` + +#### — *VarMeasConfig* + +The UE variable *VarMeasConfig* includes the accumulated configuration of the measurements to be performed by the UE, covering intra-frequency, inter-frequency and inter-RAT mobility related measurements. + +#### *VarMeasConfig* UE variable + +``` +-- ASN1START +-- TAG-VARMEASCONFIG-START + +VarMeasConfig ::= SEQUENCE { + -- Measurement identities + measIdList MeasIdToAddModList OPTIONAL, + -- Measurement objects + measObjectList MeasObjectToAddModList OPTIONAL, + -- Reporting configurations + reportConfigList ReportConfigToAddModList OPTIONAL, + -- Other parameters + quantityConfig QuantityConfig OPTIONAL, + s-MeasureConfig CHOICE { + ssb-RSRP RSRP-Range, + csi-RSRP RSRP-Range + } OPTIONAL +} + +-- TAG-VARMEASCONFIG-STOP +-- ASN1STOP +``` + +#### — *VarMeasConfigSL* + +The UE variable *VarMeasConfigSL* includes the accumulated configuration of the NR sidelink measurements to be performed by the UE of unicast destination. + +#### *VarMeasConfigSL* UE variable + +``` +-- ASN1START +-- TAG-VARMEASCONFIGSL-START + +VarMeasConfigSL-r16 ::= SEQUENCE { + -- NR sidelink measurement identities + sl-MeasIdList-r16 SL-MeasIdList-r16 OPTIONAL, + -- NR sidelink measurement objects + sl-MeasObjectList-r16 SL-MeasObjectList-r16 OPTIONAL, + -- NR sidelink reporting configurations + sl-ReportConfigList-r16 SL-ReportConfigList-r16 OPTIONAL, + -- Other parameters + sl-QuantityConfig-r16 SL-QuantityConfig-r16 OPTIONAL +} + +-- TAG-VARMEASCONFIGSL-STOP +``` + +``` +-- ASN1STOP +``` + +#### — *VarMeasIdleConfig* + +The UE variable *VarMeasIdleConfig* includes the configuration of the measurements to be performed by the UE while in RRC\_IDLE or RRC\_INACTIVE for NR inter-frequency and inter-RAT (i.e. EUTRA) measurements. + +#### *VarMeasIdleConfig* UE variable + +``` +-- ASN1START +-- TAG-VARMEASIDLECONFIG-START + +VarMeasIdleConfig-r16 ::= SEQUENCE { + measIdleCarrierListNR-r16 SEQUENCE (SIZE (1..maxFreqIdle-r16)) OF MeasIdleCarrierNR-r16 OPTIONAL, + measIdleCarrierListEUTRA-r16 SEQUENCE (SIZE (1..maxFreqIdle-r16)) OF MeasIdleCarrierEUTRA-r16 OPTIONAL, + measIdleDuration-r16 ENUMERATED {sec10, sec30, sec60, sec120, sec180, sec240, sec300, spare}, + validityAreaList-r16 ValidityAreaList-r16 OPTIONAL +} + +-- TAG-VARMEASIDLECONFIG-STOP +-- ASN1STOP +``` + +#### — *VarMeasIdleReport* + +The UE variable *VarMeasIdleReport* includes the logged measurements information. + +#### *VarMeasIdleReport* UE variable + +``` +-- ASN1START +-- TAG-VARMEASIDLEREPORT-START + +VarMeasIdleReport-r16 ::= SEQUENCE { + measReportIdleNR-r16 MeasResultIdleNR-r16 OPTIONAL, + measReportIdleEUTRA-r16 MeasResultIdleEUTRA-r16 OPTIONAL +} + +-- TAG-VARMEASIDLEREPORT-STOP +-- ASN1STOP +``` + +#### — *VarMeasReportList* + +The UE variable *VarMeasReportList* includes information about the measurements for which the triggering conditions have been met. + +#### *VarMeasReportList* UE variable + +``` +-- ASN1START +``` + +``` + +-- TAG-VARMEASREPORTLIST-START + +VarMeasReportList ::= + SEQUENCE (SIZE (1..maxNrofMeasId)) OF VarMeasReport + +VarMeasReport ::= + SEQUENCE { + -- List of measurement that have been triggered + measId MeasId, + cellsTriggeredList CellsTriggeredList OPTIONAL, + numberOfReportsSent INTEGER, + cli-TriggeredList-r16 CLI-TriggeredList-r16 OPTIONAL, + tx-PoolMeasToAddModListNR-r16 Tx-PoolMeasList-r16 OPTIONAL, + relaysTriggeredList-r17 RelaysTriggeredList-r17 OPTIONAL + } + +CellsTriggeredList ::= + SEQUENCE (SIZE (1..maxNrofCellMeas)) OF CHOICE { + physCellId PhysCellId, + physCellIdEUTRA EUTRA-PhysCellId, + physCellIdUTRA-FDD-r16 PhysCellIdUTRA-FDD-r16 + } + +CLI-TriggeredList-r16 ::= + CHOICE { + srs-RSRP-TriggeredList-r16 SRS-RSRP-TriggeredList-r16, + cli-RSSI-TriggeredList-r16 CLI-RSSI-TriggeredList-r16 + } + +SRS-RSRP-TriggeredList-r16 ::= + SEQUENCE (SIZE (1.. maxNrofCLI-SRS-Resources-r16)) OF SRS-ResourceId + +CLI-RSSI-TriggeredList-r16 ::= + SEQUENCE (SIZE (1.. maxNrofCLI-RSSI-Resources-r16)) OF RSSI-ResourceId-r16 + +RelaysTriggeredList-r17 ::= + SEQUENCE (SIZE (1.. maxNrofRelayMeas-r17)) OF SL-SourceIdentity-r17 + +-- TAG-VARMEASREPORTLIST-STOP +-- ASN1STOP + +``` + +#### — *VarMeasReportListSL* + +The UE variable *VarMeasReportListSL* includes information about the NR sidelink measurements for which the triggering conditions have been met. + +#### ***VarMeasReportListSL* UE variable** + +``` + +-- ASN1START +-- TAG-VARMEASREPORTLISTSL-START + +VarMeasReportListSL-r16 ::= + SEQUENCE (SIZE (1..maxNrofSL-MeasId-r16)) OF VarMeasReportSL-r16 + +VarMeasReportSL-r16 ::= + SEQUENCE { + -- List of NR sidelink measurement that have been triggered + sl-MeasId-r16 SL-MeasId-r16, + sl-FrequencyTriggeredList-r16 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF ARFCN-ValueNR OPTIONAL, + sl-NumberOfReportsSent-r16 INTEGER + } + +``` + +``` + +} +-- TAG-VARMEASREPORTLISTSL-STOP +-- ASN1STOP + +``` + +#### — *VarMobilityHistoryReport* + +The UE variable *VarMobilityHistoryReport* includes the mobility history information. + +#### ***VarMobilityHistoryReport* UE variable** + +``` + +-- ASN1START +-- TAG-VARMOBILITYHISTORYREPORT-START + +VarMobilityHistoryReport-r16 ::= VisitedCellInfoList-r16 + +VarMobilityHistoryReport-r17 ::= SEQUENCE { + visitedCellInfoList-r16 VisitedCellInfoList-r16, + visitedPSCellInfoListReport-r17 VisitedPSCellInfoList-r17 OPTIONAL +} + +-- TAG-VARMOBILITYHISTORYREPORT-STOP +-- ASN1STOP + +``` + +#### — *VarPendingRNA-Update* + +The UE variable *VarPendingRNA-Update* indicates whether there is a pending RNA update procedure or not. The setting of this BOOLEAN variable to *true* means that there is a pending RNA Update procedure. + +#### ***VarPendingRNA-Update* UE variable** + +``` + +-- ASN1START +-- TAG-VARPENDINGRNA-UPDATE-START + +VarPendingRNA-Update ::= + pendingRNA-Update SEQUENCE { + BOOLEAN OPTIONAL + } + +-- TAG-VARPENDINGRNA-UPDATE-STOP +-- ASN1STOP + +``` + +#### — *VarRA-Report* + +The UE variable *VarRA-Report* includes the random-access related information. + +#### VarRA-Report UE variable + +``` +-- ASN1START +-- TAG-VARRA-REPORT-START + +VarRA-Report-r16 := SEQUENCE { + ra-ReportList-r16 RA-ReportList-r16, + identityList-r18 CHOICE { + plmn-IdentityList-r18 PLMN-IdentityList2-r16, + snpn-IdentityList-r18 SEQUENCE (SIZE (1..maxNPN-r16)) OF SNPN-Identity-r18 + } +} + +PLMN-IdentityList-r16 := SEQUENCE (SIZE (1..maxPLMN)) OF PLMN-Identity + +-- TAG-VARRA-REPORT-STOP +-- ASN1STOP +``` + +#### VarResumeMAC-Input + +The UE variable *VarResumeMAC-Input* specifies the input used to generate the *resumeMAC-I* during RRC Connection Resume procedure. + +#### VarResumeMAC-Input variable + +``` +-- ASN1START +-- TAG-VARRESUMEMAC-INPUT-START + +VarResumeMAC-Input := SEQUENCE { + sourcePhysCellId PhysCellId, + targetCellIdentity CellIdentity, + source-c-RNTI RNTI-Value +} + +-- TAG-VARRESUMEMAC-INPUT-STOP +-- ASN1STOP +``` + +##### VarResumeMAC-Input field descriptions + +| | | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| targetCellIdentity | An input variable used to calculate the resumeMAC-I . Set to the cellIdentity of the first PLMN-Identity included in the PLMN-IdentityInfoList broadcasted in SIB1 of the target cell i.e. the cell the UE is trying to resume. | +| source-c-RNTI | Set to C-RNTI that the UE had in the PCell it was connected to prior to suspension of the RRC connection. | +| sourcePhysCellId | Set to the physical cell identity of the PCell the UE was connected to prior to suspension of the RRC connection. | + +#### – *VarRLF-Report* + +The UE variable *VarRLF-Report* includes the radio link failure information or handover failure information. + +##### *VarRLF-Report* UE variable + +``` +-- ASN1START +-- TAG-VARRLF-REPORT-START + +VarRLF-Report-r16 ::= SEQUENCE { + rlf-Report-r16 RLF-Report-r16, + identityList-r18 CHOICE { + plmn-IdentityList-r18 PLMN-IdentityList2-r16, + snpn-IdentityList-r18 SEQUENCE (SIZE (1..maxNPN-r16)) OF SNPN-Identity-r18 + } +} + +-- TAG-VARRLF-REPORT-STOP +-- ASN1STOP +``` + +Editor's note: Logging equivalent SNPNs in SON variables is FFS. + +#### – *VarServingSecurityCellSetID* + +The UE variable *VarServingSecurityCellSetID* includes the security cell set ID of serving PCell. + +#### *VarServingSecurityCellSetID* UE variable + +``` +-- ASN1START +-- TAG-VARCONDITIONALRECONFIG-START + +VarServingSecurityCellSetID ::= SEQUENCE { + servingSecurityCellSetId-r18 INTEGER (1.. maxSecurityCellSet-r18) +} + +-- TAG-VARCONDITIONALRECONFIG-STOP +-- ASN1STOP +``` + +#### – *VarShortMAC-Input* + +The UE variable *VarShortMAC-Input* specifies the input used to generate the *shortMAC-I* during RRC Connection Reestablishment procedure. + +#### *VarShortMAC-Input* variable + +``` +-- ASN1START +``` + +``` + +-- TAG-VARSHORTMAC-INPUT-START + +VarShortMAC-Input := SEQUENCE { + sourcePhysCellId PhysCellId, + targetCellIdentity CellIdentity, + source-c-RNTI RNTI-Value +} + +-- TAG-VARSHORTMAC-INPUT-STOP +-- ASN1STOP + +``` + +##### VarShortMAC-Input field descriptions + +##### **targetCellIdentity** + +An input variable used to calculate the *shortMAC-I*. Set to the *cellIdentity* of the first *PLMN-Identity* in the *PLMN-IdentityInfoList* broadcasted in *SIB1* of the target cell i.e. the cell the UE is trying to reestablish the connection. + +##### **source-c-RNTI** + +Set to C-RNTI that the UE had in the PCell it was connected to prior to the reestablishment. + +##### **sourcePhysCellId** + +Set to the physical cell identity of the PCell the UE was connected to prior to the reestablishment. + +#### — **VarSuccessHO-Report** + +The UE variable *VarSuccessHO-Report* includes the successful handover information. + +##### VarSccessHO-Report variable + +``` + +-- ASN1START +-- TAG-VARSUCCESSHO-Report-START + +VarSuccessHO-Report-r17-IEs := SEQUENCE { + successHO-Report-r17 SuccessHO-Report-r17, + identityList-r18 CHOICE { + plmn-IdentityList-r18 PLMN-IdentityList2-r16, + snpn-IdentityList-r18 SEQUENCE (SIZE (1..maxNPN-r16)) OF SNPN-Identity-r18 + } +} + +-- TAG-VARSUCCESSHO-Report-STOP +-- ASN1STOP + +``` + +#### — **VarSuccessPSCell-Report** + +The UE variable *VarSuccessPSCell-Report* includes the successful PSCell change or addition information. + +#### ***VarSuccessPSCell-Report* variable** + +``` +-- ASN1START +-- TAG-VARSUCCESSPSCELL-Report-START + +VarSuccessPSCell-Report-r18-IEs ::= SEQUENCE { + successPSCell-Report-r18 SuccessPSCell-Report-r18, + identityList-r18 CHOICE { + plmn-IdentityList-r18 PLMN-IdentityList2-r16, + snpn-IdentityList-r18 SEQUENCE (SIZE (1..maxNPN-r16)) OF SNPN-Identity-r18 + } +} + +-- TAG-VARSUCCESSPSCELL-Report-STOP +-- ASN1STOP +``` + +### **— End of *NR-UE-Variables*** + +``` +-- ASN1START + +END + +-- ASN1STOP +``` + +# 8 Protocol data unit abstract syntax + +## 8.1 General + +The RRC PDU contents in clause 6 and clause 10 are described using abstract syntax notation one (ASN.1) as specified in ITU-T Rec. X.680 [6] and X.681 [7]. Transfer syntax for RRC PDUs is derived from their ASN.1 definitions by use of Packed Encoding Rules, unaligned as specified in ITU-T Rec. X.691 [8]. + +The following encoding rules apply in addition to what has been specified in X.691: + +- When a bit string value is placed in a bit-field as specified in 15.6 to 15.11 in X.691, the leading bit of the bit string value shall be placed in the leading bit of the bit-field, and the trailing bit of the bit string value shall be placed in the trailing bit of the bit-field; + +NOTE: The terms 'leading bit' and 'trailing bit' are defined in ITU-T Rec. X.680. When using the 'bstring' notation, the leading bit of the bit string value is on the left, and the trailing bit of the bit string value is on the right. + +- When decoding types constrained with the ASN.1 Contents Constraint ("CONTAINING"), automatic decoding of the contained type should not be performed because errors in the decoding of the contained type should not cause the decoding of the entire RRC message PDU to fail. It is recommended that the decoder first decodes the outer PDU type that contains the OCTET STRING or BIT STRING with the Contents Constraint, and then decodes the contained type that is nested within the OCTET STRING or BIT STRING as a separate step; +- When decoding a) RRC message PDUs, b) BIT STRING constrained with a Contents Constraint, or c) OCTET STRING constrained with a Contents Constraint, PER decoders are required to never report an error if there are extraneous zero or non-zero bits at the end of the encoded RRC message PDU, BIT STRING or OCTET STRING. + +## 8.2 Structure of encoded RRC messages + +An RRC PDU, which is the bit string that is exchanged between peer entities/across the radio interface contains the basic production as defined in X.691. + +RRC PDUs shall be mapped to and from PDCP SDUs (in case of DCCH) or RLC SDUs (in case of PCCH, BCCH or CCCH) upon transmission and reception as follows: + +- when delivering an RRC PDU as an PDCP SDU to the PDCP layer for transmission, the first bit of the RRC PDU shall be represented as the first bit in the PDCP SDU and onwards; and +- when delivering an RRC PDU as an RLC SDU to the RLC layer for transmission, the first bit of the RRC PDU shall be represented as the first bit in the RLC SDU and onwards; and +- upon reception of an PDCP SDU from the PDCP layer, the first bit of the PDCP SDU shall represent the first bit of the RRC PDU and onwards; and +- upon reception of an RLC SDU from the RLC layer, the first bit of the RLC SDU shall represent the first bit of the RRC PDU and onwards. + +## 8.3 Basic production + +The 'basic production' is obtained by applying UNALIGNED PER to the abstract syntax value (the ASN.1 description) as specified in X.691. It always contains a multiple of 8 bits. + +## 8.4 Extension + +The following rules apply with respect to the use of protocol extensions: + +- A transmitter compliant with this version of the specification shall, unless explicitly indicated otherwise on a PDU type basis, set the extension part empty. Transmitters compliant with a later version may send non-empty extensions; + +- A transmitter compliant with this version of the specification shall set spare bits to zero. + +## 8.5 Padding + +If the encoded RRC message does not fill a transport block, the RRC layer shall add padding bits. This applies to PCCH and BCCH. + +Padding bits shall be set to 0 and the number of padding bits is a multiple of 8. + +![Flowchart of RRC level padding process. It shows the flow from RRC-ASN.1 (RRC message and Extension) through an ASN.1 encoder to produce a 'Basic production (always a multiple of 8 bits)'. This is then processed by 'RRC padding' to produce the final 'RRC-PDU', which consists of the 'Basic production' and 'RRC level padding'.](331afcb1534110b4c4f6ddf553a0f7e0_img.jpg) + +``` + +graph TD + subgraph RRC-ASN.1 + A[RRC message] --- B[Extension] + end + A --> C((ASN.1 encoder)) + B --> C + C --> D[Basic production (always a multiple of 8 bits)] + D --> E((RRC padding)) + E --> F[Basic production] + E --> G[RRC level padding] + subgraph RRC-PDU + F --- G + end + +``` + +Flowchart of RRC level padding process. It shows the flow from RRC-ASN.1 (RRC message and Extension) through an ASN.1 encoder to produce a 'Basic production (always a multiple of 8 bits)'. This is then processed by 'RRC padding' to produce the final 'RRC-PDU', which consists of the 'Basic production' and 'RRC level padding'. + +Figure 8.5-1: RRC level padding + +# 9 Specified and default radio configurations + +Specified and default configurations are configurations of which the details are specified in the standard. Specified configurations are fixed while default configurations can be modified using dedicated signalling. The default value for the parameters not listed in following clauses shall be set such as the corresponding features are not configured, i.e. *release* or *false* unless explicitly stated otherwise. + +NOTE: The UE applies the default values specified in the field description of ASN.1 parameters only when the parent IE is present. Hence, the UE does not apply all default values in field descriptions when it applies the "default radio configuration" in accordance with this clause. + +## 9.1 Specified configurations + +### 9.1.1 Logical channel configurations + +#### 9.1.1.1 BCCH configuration + +Parameters + +| Name | Value | Semantics description | Ver | +|-------------------------------|----------|-----------------------|-----| +| SDAP configuration | Not used | | | +| PDCP configuration | Not used | | | +| RLC configuration | TM | | | +| Logical channel configuration | Not used | | | + +NOTE: RRC will perform padding, if required due to the granularity of the TF signalling, as defined in 8.5. + +#### 9.1.1.2 CCCH configuration + +Parameters + +| Name | Value | Semantics description | Ver | +|-------------------------------|----------|-----------------------|-----| +| SDAP configuration | Not used | | | +| PDCP configuration | Not used | | | +| RLC configuration | TM | | | +| Logical channel configuration | | | | +| >priority | 1 | Highest priority | | +| >prioritisedBitRate | infinity | | | +| >bucketSizeDuration | ms1000 | | | +| >logicalChannelGroup | 0 | | | + +#### 9.1.1.3 PCCH configuration + +Parameters + +| Name | Value | Semantics description | Ver | +|-------------------------------|----------|-----------------------|-----| +| SDAP configuration | Not used | | | +| PDCP configuration | Not used | | | +| RLC configuration | TM | | | +| Logical channel configuration | Not used | | | + +NOTE: RRC will perform padding, if required due to the granularity of the TF signalling, as defined in 8.5. + +#### 9.1.1.4 SCCH configuration + +Parameters that are specified for unicast of NR sidelink communication, which is used for the sidelink signalling radio bearer of PC5-RRC message. The SL-SRB using this SCCH configuration is named as SL-SRB3. + +| Name | Value | Semantics description | Ver | +|--------------------------------------------------------------|-----------|----------------------------------------------------------------------------------------------------------------|-------| +| PDCP configuration | | | | +| >t-Reordering | Undefined | Selected by the receiving UE, up to UE implementation | | +| >pdcp-SN-Size | 12 | | | +| SRAP configuration | | Specified for L2 U2U relay operation, which is used for U2U Remote UE's SL-SRB3 with the peer U2U Remote UE. | | +| >sl-RemoteUE-SLRB-Identity | 3 | This parameter is only applicable to L2 U2U relay operation. | | +| RLC configuration | | AM RLC | | +| >sn-FieldLength | 12 | | | +| >t-Reassembly | Undefined | Selected by the receiving UE, up to UE implementation | | +| >t-PollRetransmit | Undefined | Selected by the transmitting UE, up to UE implementation | | +| >pollPDU | Undefined | Selected by the transmitting UE, up to UE implementation | | +| >pollByte | Undefined | Selected by the transmitting UE, up to UE implementation | | +| >maxRetxThreshold | Undefined | Selected by the transmitting UE, up to UE implementation | | +| >t-StatusProhibit | Undefined | Selected by the receiving UE, up to UE implementation | | +| >logicalChannelIdentity | 3 | | | +| MAC configuration | | | | +| >priority | 1 | | | +| >prioritisedBitRate | infinity | | | +| >logicalChannelGroup | 0 | | | +| >schedulingRequestId | 0 | The scheduling request configuration with this value is applicable for this SCCH if configured by the network. | | +| >sl-HARQ-FeedbackEnabled | Undefined | Selected by the transmitting UE, up to UE implementation | | +| Additional RLC configuration | | AM RLC
This RLC is used for PDCP duplication | v1800 | +| >sn-FieldLength | 12 | | v1800 | +| >t-Reassembly | Undefined | Selected by the receiving UE, up to UE implementation | v1800 | +| >t-PollRetransmit | Undefined | Selected by the transmitting UE, up to UE implementation | v1800 | +| >pollPDU | Undefined | Selected by the transmitting UE, up to UE implementation | v1800 | +| >pollByte | Undefined | Selected by the transmitting UE, up to UE implementation | v1800 | +| >maxRetxThreshold | Undefined | Selected by the transmitting UE, up to UE implementation | v1800 | +| >t-StatusProhibit | Undefined | Selected by the receiving UE, up to UE implementation | v1800 | +| >logicalChannelIdentity | FFS | | v1800 | +| MAC configuration associated to additional RLC configuration | | This logical channel is used for PDCP duplication | v1800 | +| >priority | 1 | | v1800 | +| >prioritisedBitRate | infinity | | v1800 | +| >logicalChannelGroup | 0 | | v1800 | +| >schedulingRequestId | 0 | The scheduling request configuration with this value is applicable for this SCCH if configured by the network. | v1800 | +| >sl-HARQ-FeedbackEnabled | Undefined | Selected by the transmitting UE, up to UE implementation | v1800 | + +Parameters that are specified of NR sidelink communication, which is used for the sidelink signalling radio bearer of unprotected PC5-S message (e.g. Direct Link Establishment Request, TS 24.587 [57] or Prose Direct Link Establishment Request, TS 24.554 [72]). The SL-SRB using this SCCH configuration is named as SL-SRB0. + +| Name | Value | Semantics description | Ver | +|------------------------------------|-----------|----------------------------------------------------------------------------------------------------------------|-----| +| PDCP configuration | | | | +| > t-Reordering | Undefined | Selected by the receiving UE, up to UE implementation | | +| > pdcp-SN-Size | 12 | | | +| SRAP configuration | | Specified for L2 U2U relay operation, which is used for U2U Remote UE's SL-SRB0 with the peer U2U Remote UE. | | +| > sl-RemoteUE-SLRB-Identity | 0 | This parameter is only applicable to L2 U2U relay operation. | | +| RLC configuration | | UM RLC | | +| > sn-FieldLength | 6 | | | +| > t-Reassembly | Undefined | Selected by the receiving UE, up to UE implementation | | +| > logicalChannelIdentity | 0 | | | +| MAC configuration | | | | +| > priority | 1 | | | +| > prioritisedBitRate | infinity | | | +| > logicalChannelGroup | 0 | | | +| > schedulingRequestId | 0 | The scheduling request configuration with this value is applicable for this SCCH if configured by the network. | | +| > sl-HARQ-FeedbackEnabled | Undefined | Selected by the transmitting UE, up to UE implementation | | + +Parameters that are specified for unicast of NR sidelink communication, which is used for the sidelink signalling radio bearer of PC5-S message establishing PC5-S security (e.g. Direct Link Security Mode Command and Direct Link Security Mode Complete, TS 24.587 [57] or ProSe Direct Link Security Mode Command and ProSe Direct Link Security Mode Complete, TS 24.554 [72]). The SL-SRB using this SCCH configuration is named as SL-SRB1. + +| Name | Value | Semantics description | Ver | +|--------------------------------------------------------------|-----------|----------------------------------------------------------------------------------------------------------------|-------| +| PDCP configuration | | | | +| >t-Reordering | Undefined | Selected by the receiving UE, up to UE implementation | | +| >pdcp-SN-Size | 12 | | | +| SRAP configuration | | Specified for L2 U2U relay operation, which is used for U2U Remote UE's SL-SRB1 with the peer U2U Remote UE. | | +| >sl-RemoteUE-SLRB-Identity | 1 | This parameter is only applicable to L2 U2U relay operation. | | +| RLC configuration | | AM RLC | | +| >sn-FieldLength | 12 | | | +| >t-Reassembly | Undefined | Selected by the receiving UE, up to UE implementation | | +| >t-PollRetransmit | Undefined | Selected by the transmitting UE, up to UE implementation | | +| >pollPDU | Undefined | Selected by the transmitting UE, up to UE implementation | | +| >pollByte | Undefined | Selected by the transmitting UE, up to UE implementation | | +| >maxRetxThreshold | Undefined | Selected by the transmitting UE, up to UE implementation | | +| >t-StatusProhibit | Undefined | Selected by the receiving UE, up to UE implementation | | +| >logicalChannelIdentity | 1 | | | +| MAC configuration | | | | +| >priority | 1 | | | +| >prioritisedBitRate | infinity | | | +| >logicalChannelGroup | 0 | | | +| >schedulingRequestId | 0 | The scheduling request configuration with this value is applicable for this SCCH if configured by the network. | | +| >sl-HARQ-FeedbackEnabled | Undefined | Selected by the transmitting UE, up to UE implementation | | +| RLC configuration | | AM RLC
This RLC is used for PDCP duplication | v1800 | +| >sn-FieldLength | 12 | | v1800 | +| >t-Reassembly | Undefined | Selected by the receiving UE, up to UE implementation | v1800 | +| >t-PollRetransmit | Undefined | Selected by the transmitting UE, up to UE implementation | v1800 | +| >pollPDU | Undefined | Selected by the transmitting UE, up to UE implementation | v1800 | +| >pollByte | Undefined | Selected by the transmitting UE, up to UE implementation | v1800 | +| >maxRetxThreshold | Undefined | Selected by the transmitting UE, up to UE implementation | v1800 | +| >t-StatusProhibit | Undefined | Selected by the receiving UE, up to UE implementation | v1800 | +| >logicalChannelIdentity | FFS | | v1800 | +| MAC configuration associated to additional RLC configuration | | This logical channel is used for PDCP duplication | v1800 | +| >priority | 1 | | v1800 | +| >prioritisedBitRate | infinity | | v1800 | +| >logicalChannelGroup | 0 | | v1800 | +| >schedulingRequestId | 0 | The scheduling request configuration with this value is applicable for this SCCH if configured by the network. | v1800 | +| >sl-HARQ-FeedbackEnabled | Undefined | Selected by the transmitting UE, up to UE implementation | v1800 | + +Parameters that are specified for unicast of NR sidelink communication, which is used for the sidelink signalling radio bearer of protected PC5-S message except Direct Link Security Mode Complete, TS 24.587 [57] or Prose Direct Link Security Mode Complete, TS 24.554 [72]. The SL-SRB using this SCCH configuration is named as SL-SRB2. + +| Name | Value | Semantics description | Ver | +|--------------------------------------------------------------|-----------|----------------------------------------------------------------------------------------------------------------|-------| +| PDCP configuration | | | | +| > t-Reordering | Undefined | Selected by the receiving UE, up to UE implementation | | +| > pdcp-SN-Size | 12 | | | +| SRAP configuration | | Specified for L2 U2U relay operation, which is used for U2U Remote UE's SL-SRB2 with the peer U2U Remote UE. | | +| > sl-RemoteUE-SLRB-Identity | 2 | This parameter is only applicable to L2 U2U relay operation. | | +| RLC configuration | | AM RLC | | +| > sn-FieldLength | 12 | | | +| > t-Reassembly | Undefined | Selected by the receiving UE, up to UE implementation | | +| > t-PollRetransmit | Undefined | Selected by the transmitting UE, up to UE implementation | | +| > pollPDU | Undefined | Selected by the transmitting UE, up to UE implementation | | +| > pollByte | Undefined | Selected by the transmitting UE, up to UE implementation | | +| > maxRetxThreshold | Undefined | Selected by the transmitting UE, up to UE implementation | | +| > t-StatusProhibit | Undefined | Selected by the receiving UE, up to UE implementation | | +| > logicalChannelIdentity | 2 | | | +| MAC configuration | | | | +| > priority | 1 | | | +| > prioritisedBitRate | infinity | | | +| > logicalChannelGroup | 0 | | | +| > schedulingRequestId | 0 | The scheduling request configuration with this value is applicable for this SCCH if configured by the network. | | +| > sl-HARQ-FeedbackEnabled | Undefined | Selected by the transmitting UE, up to UE implementation | | +| RLC configuration | | AM RLC
This RLC is used for PDCP duplication | v1800 | +| > sn-FieldLength | 12 | | v1800 | +| > t-Reassembly | Undefined | Selected by the receiving UE, up to UE implementation | v1800 | +| > t-PollRetransmit | Undefined | Selected by the transmitting UE, up to UE implementation | v1800 | +| > pollPDU | Undefined | Selected by the transmitting UE, up to UE implementation | v1800 | +| > pollByte | Undefined | Selected by the transmitting UE, up to UE implementation | v1800 | +| > maxRetxThreshold | Undefined | Selected by the transmitting UE, up to UE implementation | v1800 | +| > t-StatusProhibit | Undefined | Selected by the receiving UE, up to UE implementation | v1800 | +| > logicalChannelIdentity | FFS | | v1800 | +| MAC configuration associated to additional RLC configuration | | This logical channel is used for PDCP duplication | v1800 | +| > priority | 1 | | v1800 | +| > prioritisedBitRate | infinity | | v1800 | +| > logicalChannelGroup | 0 | | v1800 | +| > schedulingRequestId | 0 | The scheduling request configuration with this value is applicable for this SCCH if configured by the network. | v1800 | +| > sl-HARQ-FeedbackEnabled | Undefined | Selected by the transmitting UE, up to UE implementation | v1800 | + +Parameters that are specified for NR sidelink discovery, which is used for the sidelink signalling radio bearer of NR sidelink discovery messages (e.g., Announcement message, Solicitation message and Response message, see TS 23.304 [65]). The SL-SRB using this SCCH configuration is named as SL-SRB4. + +| Name | Value | Semantics description | Ver | +|--------------------------|-----------|----------------------------------------------------------------------------------------------------------------|-----| +| PDCP configuration | | | | +| >t-Reordering | Undefined | Selected by the receiving UE, up to UE implementation | | +| >pdcp-SN-Size | 12 | | | +| RLC configuration | | UM RLC | | +| >sn-FieldLength | 6 | | | +| >t-Reassembly | Undefined | Selected by the receiving UE, up to UE implementation | | +| >logicalChannelIdentity | 58 | | | +| MAC configuration | | | | +| >priority | 1 | | | +| >prioritisedBitRate | infinity | | | +| >logicalChannelGroup | 0 | | | +| >schedulingRequestId | 0 | The scheduling request configuration with this value is applicable for this SCCH if configured by the network. | | +| >sl-HARQ-FeedbackEnabled | disabled | HARQ feedback is not supported for NR sidelink discovery transmission | | + +Parameters that are specified for NR sidelink L2 U2N Relay operations, which is used for the PC5 Relay RLC channel for Remote UE's SRB0 message transmission/reception. The PC5 Relay RLC channel using this configuration is named as SL-RLC0. + +| Name | Value | Semantics description | Ver | +|--------------------------|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| RLC configuration | | AM | | +| >sn-FieldLength | 12 | | | +| >t-Reassembly | Undefined | Selected by the receiving UE, up to UE implementation | | +| >t-PollRetransmit | Undefined | Selected by the transmitting UE, up to UE implementation | | +| >pollPDU | Undefined | Selected by the transmitting UE, up to UE implementation | | +| >pollByte | Undefined | Selected by the transmitting UE, up to UE implementation | | +| >maxRetxThreshold | Undefined | Selected by the transmitting UE, up to UE implementation | | +| >t-StatusProhibit | Undefined | Selected by the receiving UE, up to UE implementation | | +| >logicalChannelIdentity | 56 | | | +| MAC configuration | | | | +| >priority | 1 | | | +| >prioritisedBitRate | Infinity | | | +| >logicalChannelGroup | 0 | | | +| >schedulingRequestId | 0 | The scheduling request configuration with this value is applicable for this SCCH if configured by the network. The scheduling request configuration is not applicable to L2 U2N Remote UE. | | +| >sl-HARQ-FeedbackEnabled | Undefined | Selected by the transmitting UE, up to UE implementation | | + +Parameters that are specified for NR sidelink L2 U2U Relay operations, which is used for the PC5 Relay RLC channel for U2U Remote UE's SL-SRB0/1/2/3 message transmission/reception with the peer U2U Remote UE. The PC5 Relay RLC channel using this configuration is named as SL-U2U-RLC. + +| Name | Value | Semantics description | Ver | +|--------------------------|-----------|----------------------------------------------------------------------------------------------------------------|-----| +| RLC configuration | | AM | | +| >sn-FieldLength | 12 | | | +| >t-Reassembly | Undefined | Selected by the receiving UE, up to UE implementation | | +| >t-PollRetransmit | Undefined | Selected by the transmitting UE, up to UE implementation | | +| >pollPDU | Undefined | Selected by the transmitting UE, up to UE implementation | | +| >pollByte | Undefined | Selected by the transmitting UE, up to UE implementation | | +| >maxRetxThreshold | Undefined | Selected by the transmitting UE, up to UE implementation | | +| >t-StatusProhibit | Undefined | Selected by the receiving UE, up to UE implementation | | +| >logicalChannelIdentity | 55 | | | +| MAC configuration | | | | +| >priority | 1 | | | +| >prioritisedBitRate | Infinity | | | +| >logicalChannelGroup | 0 | | | +| >schedulingRequestId | 0 | The scheduling request configuration with this value is applicable for this SCCH if configured by the network. | | +| >sl-HARQ-FeedbackEnabled | Undefined | Selected by the transmitting UE, up to UE implementation | | + +#### 9.1.1.5 STCH configuration + +Parameters that are specified for NR sidelink communication, which is used for the sidelink data radio bearer. + +| Name | Value | Semantics description | Ver | +|-------------------------|-----------|----------------------------------------------------------------------------------------------------------------|-----| +| PDCP configuration | | | | +| >t-Reordering | Undefined | Selected by the receiving UE, up to UE implementation | | +| >pdcp-SN-Size | 12 | For broadcast and groupcast of NR sidelink communication | | +| >maxCID | 15 | For broadcast and groupcast of NR sidelink communication | | +| >profiles | | | | +| RLC configuration | | For broadcast and groupcast of NR sidelink communication, unidirectional UM RLC
UM window size is set to 32 | | +| >t-Reassembly | Undefined | Selected by the receiving UE, up to UE implementation | | +| >sn-FieldLength | 6 | For broadcast and groupcast of NR sidelink communication | | +| >logicalChannelIdentity | Undefined | Selected by the transmitting UE, up to UE implementation | | +| MAC configuration | | | | +| >priority | | | | + +#### 9.1.1.6 MCCH configuration + +Parameters that are specified for MCCH. + +| Name | Value | Semantics description | Ver | +|-------------------|-------|-----------------------|-----| +| RLC configuration | | UM RLC | | +| >sn-FieldLength | 6 | | | +| >t-Reassembly | ms0 | | | + +#### 9.1.1.7 MTCH configuration for MBS broadcast + +Parameters that are specified for MBS broadcast MTCH. + +| Name | Value | Semantics description | Ver | +|--------------------|-------|-----------------------|-----| +| PDCP configuration | | | | +| >t-Reordering | ms0 | | | +| >pdcp-SN-SizeDL | 18 | | | +| RLC configuration | | UM RLC | | +| >sn-FieldLength | 12 | | | +| >t-Reassembly | ms0 | | | + +### 9.1.2 Void + +## 9.2 Default radio configurations + +The following clauses only list default values for REL-15 parameters included in protocol version v15.3.0. For all fields introduced in a later protocol version, the default value is "released" or "false" unless explicitly specified otherwise. If the UE is to apply default configuration while it is configured with some critically extended fields, the UE shall apply the original version of those fields with only default values. + +NOTE 1: In general, the signalling should preferably support a "release" option for fields introduced after v15.3.0. The "value not applicable" should be used restrictively, mainly limited to for fields which value is relevant only if another field is set to a value other than its default. + +NOTE 2: For parameters in *ServingCellConfig*, the default values are specified in the corresponding specification. + +### 9.2.1 Default SRB configurations + +Parameters + +| Name | Value | | | Semantics description | Ver | +|------------------------|----------|------|------|-----------------------|-----| +| | SRB1 | SRB2 | SRB3 | | | +| PDCP-Config | | | | | | +| >t-Reordering | infinity | | | | | +| RLC-Config CHOICE | Am | | | | | +| ul-AM-RLC | | | | | | +| >sn-FieldLength | size12 | | | | | +| >t-PollRetransmit | ms45 | | | | | +| >pollPDU | infinity | | | | | +| >pollByte | infinity | | | | | +| >maxRetxThreshold | t8 | | | | | +| dl-AM-RLC | | | | | | +| >sn-FieldLength | size12 | | | | | +| >t-Reassembly | ms35 | | | | | +| >t-StatusProhibit | ms0 | | | | | +| logicalChannelIdentity | 1 | 2 | 3 | | | +| LogicalChannelConfig | | | | | | +| >priority | 1 | 3 | 1 | | | +| >prioritisedBitRate | infinity | | | | | +| >logicalChannelGroup | 0 | | | | | + +### 9.2.2 Default MAC Cell Group configuration + +Parameters + +| Name | Value | Semantics description | Ver | +|-----------------------------------|-------|-----------------------|-----| +| MAC Cell Group configuration | | | | +| bsr-Config | | | | +| > periodicBSR-Timer | sf10 | | | +| > retxBSR-Timer | sf80 | | | +| phr-Config | | | | +| > phr-PeriodicTimer | sf10 | | | +| > phr-ProhibitTimer | sf10 | | | +| > phr-Tx-PowerFactorChange | dB1 | | | + +### 9.2.3 Default values timers and constants + +Parameters + +| Name | Value | Semantics description | Ver | +|------|---------|-----------------------|-----| +| t310 | ms1000 | | | +| n310 | n1 | | | +| t311 | ms30000 | | | +| n311 | n1 | | | + +### 9.2.4 Default PC5 Relay RLC Channel + +Parameters of the PC5 Relay RLC Channel used for Remote UE's SRB1 RRC message transmission and reception. The PC5 Relay RLC Channel using this configuration is named as SL-RLC1. + +| Name | Value | Semantics description | Ver | +|---------------------------------|-----------|----------------------------------------------------------------------------------------------------------------|-----| +| RLC configuration | | AM | | +| > sn-FieldLength | 12 | | | +| > t-Reassembly | Undefined | Selected by the receiving UE, up to UE implementation | | +| > t-PollRetransmit | Undefined | Selected by the transmitting UE, up to UE implementation | | +| > pollPDU | Undefined | Selected by the transmitting UE, up to UE implementation | | +| > pollByte | Undefined | Selected by the transmitting UE, up to UE implementation | | +| > maxRetxThreshold | Undefined | Selected by the transmitting UE, up to UE implementation | | +| > t-StatusProhibit | Undefined | Selected by the receiving UE, up to UE implementation | | +| > logicalChannelIdentity | 57 | | | +| MAC configuration | | | | +| > priority | 1 | | | +| > prioritisedBitRate | Infinity | | | +| > logicalChannelGroup | 0 | | | +| > schedulingRequestId | 0 | The scheduling request configuration with this value is applicable for this SCCH if configured by the network. | | + +### 9.2.5 Default SRAP configurations + +Parameters that are used for reception of Remote UE's *RRResume*, *RRRelease* in response to an *RRResumeRequest/RRResumeRequest1* and *RRReestablishment* messages. + +| Name | Value | Semantics description | Ver | +|----------------------------------|-----------|------------------------------------------------------------------------------|-----| +| SL SRAP Config | | | | +| > sl-LocalIdentity | Undefined | SRAP PDUs with any local identity will be submitted to the SRB1 PDCP entity. | | +| > sl-RemoteUE-RB-Identity | SRB1 | | | + +## 9.3 Sidelink pre-configured parameters + +This ASN.1 segment is the start of the NR definitions of pre-configured sidelink parameters. + +### – *NR-Sidelink-Preconf* + +``` +-- ASN1START +-- TAG-NR-SIDELINK-PRECONF-DEFINITIONS-START + +NR-Sidelink-Preconf DEFINITIONS AUTOMATIC TAGS ::= +BEGIN + +IMPORTS + SL-RelayUE-ConfigU2U-r18, + SL-RemoteUE-ConfigU2U-r18, + SL-RemoteUE-Config-r17, + SL-DRX-ConfigGC-BC-r17, + SL-Freq-Id-r16, + maxNrofFreqSL-1-r18, + SL-FreqConfigCommon-r16, + SL-RadioBearerConfig-r16, + SL-RLC-BearerConfig-r16, + SL-EUTRA-AnchorCarrierFreqList-r16, + SL-NR-AnchorCarrierFreqList-r16, + SL-MeasConfigCommon-r16, + SL-UE-SelectedConfig-r16, + TDD-UL-DL-ConfigCommon, + maxNrofFreqSL-r16, + maxNrofSLRB-r16, + maxSL-LCID-r16 +FROM NR-RRC-Definitions; + +-- TAG-NR-SIDELINK-PRECONF-DEFINITIONS-STOP +-- ASN1STOP +``` + +### – *SL-PosPreconfigurationNR* + +The IE *SL-PosPreconfigurationNR* includes the sidelink pre-configured parameters used for NR sidelink positioning. Need codes or conditions specified for subfields in *SL-PosPreconfigurationNR* do not apply. + +### *SL-PosPreconfigurationNR* information elements + +``` +-- ASN1START +-- TAG-SL-POSPRECONFIGURATIONNR-START + +SL-PosPreconfigurationNR-r18 ::= SEQUENCE { + sl-PosPreconfigFreqInfoList-r18 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF SL-FreqConfigCommon-r16 OPTIONAL, +``` + +``` + + ... +} + +-- TAG-SL-POSPRECONFIGURATIONNR-STOP +-- ASN1STOP + +``` + +### SL-PosPreconfigurationNR field descriptions + +#### sl-PosPreconfigFreqInfoList + +This field indicates the NR sidelink positioning configuration some carrier frequency(ies). In this release, only one SL-FreqConfig can be configured in the list. + +### SL-PreconfigurationNR + +The IE *SL-PreconfigurationNR* includes the sidelink pre-configured parameters used for NR sidelink communication. Need codes or conditions specified for subfields in *SL-PreconfigurationNR* do not apply. + +### SL-PreconfigurationNR information elements + +``` + +-- ASN1START +-- TAG-SL-PRECONFIGURATIONNR-START + +SL-PreconfigurationNR-r16 ::= + SEQUENCE { + sidelinkPreconfigNR-r16 + SidelinkPreconfigNR-r16, + ... + } + +SidelinkPreconfigNR-r16 ::= + SEQUENCE { + sl-PreconfigFreqInfoList-r16 + SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF SL-FreqConfigCommon-r16 + OPTIONAL, + sl-PreconfigNR-AnchorCarrierFreqList-r16 + SL-NR-AnchorCarrierFreqList-r16 + OPTIONAL, + sl-PreconfigEUTRA-AnchorCarrierFreqList-r16 + SL-EUTRA-AnchorCarrierFreqList-r16 + OPTIONAL, + sl-RadioBearerPreConfigList-r16 + SEQUENCE (SIZE (1..maxNrofSLRB-r16)) OF SL-RadioBearerConfig-r16 + OPTIONAL, + sl-RLC-BearerPreConfigList-r16 + SEQUENCE (SIZE (1..maxSL-LCID-r16)) OF SL-RLC-BearerConfig-r16 + OPTIONAL, + sl-MeasPreConfig-r16 + SL-MeasConfigCommon-r16 + OPTIONAL, + sl-OffsetDFN-r16 + INTEGER (1..1000) + OPTIONAL, + t400-r16 + ENUMERATED{ms100, ms200, ms300, ms400, ms600, ms1000, ms1500, ms2000} + OPTIONAL, + sl-MaxNumConsecutiveDTX-r16 + ENUMERATED {n1, n2, n3, n4, n6, n8, n16, n32} + OPTIONAL, + sl-SSB-PriorityNR-r16 + INTEGER (1..8) + OPTIONAL, + sl-PreconfigGeneral-r16 + SL-PreconfigGeneral-r16 + OPTIONAL, + sl-UE-SelectedPreConfig-r16 + SL-UE-SelectedConfig-r16 + OPTIONAL, + sl-CSI-Acquisition-r16 + ENUMERATED {enabled} + OPTIONAL, + sl-RoHC-Profiles-r16 + SL-RoHC-Profiles-r16 + OPTIONAL, + sl-MaxCID-r16 + INTEGER (1..16383) + DEFAULT 15, + ... + [[ + sl-DRX-PreConfigGC-BC-r17 + SL-DRX-ConfigGC-BC-r17 + OPTIONAL, + sl-TxProfileList-r17 + SL-TxProfileList-r17 + OPTIONAL, + sl-PreconfigDiscConfig-r17 + SL-RemoteUE-Config-r17 + OPTIONAL + ]], + [[ + +``` + +``` + +sl-PreconfigFreqInfoListSizeExt-v1800 SEQUENCE (SIZE (1..maxNrofFreqSL-1-r18)) OF SL-FreqConfigCommon-r16 OPTIONAL, +sl-RLC-BearerConfigListSizeExt-v1800 SEQUENCE (SIZE (1..maxSL-LCID-r16)) OF SL-RLC-BearerConfig-r16 OPTIONAL, +sl-SyncFreqList-r18 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF SL-Freq-Id-r16 OPTIONAL, +sl-SyncTxMultiFreq-r18 ENUMERATED {true} OPTIONAL, +sl-PreconfigDiscConfig-v1800 SL-PreconfigDiscConfig-v1800 OPTIONAL +]] +} + +SL-TxProfileList-r17 ::= SEQUENCE (SIZE (1..256)) OF SL-TxProfile-r17 + +SL-TxProfile-r17 ::= ENUMERATED {drx-Compatible, drx-Incompatible, spare6, spare5, spare4, spare3,spare2, spare1} + +SL-PreconfigGeneral-r16 ::= SEQUENCE { + sl-TDD-Configuration-r16 TDD-UL-DL-ConfigCommon OPTIONAL, + reservedBits-r16 BIT STRING (SIZE (2)) OPTIONAL, + ... +} + +SL-RoHC-Profiles-r16 ::= SEQUENCE { + profile0x0001-r16 BOOLEAN, + profile0x0002-r16 BOOLEAN, + profile0x0003-r16 BOOLEAN, + profile0x0004-r16 BOOLEAN, + profile0x0006-r16 BOOLEAN, + profile0x0101-r16 BOOLEAN, + profile0x0102-r16 BOOLEAN, + profile0x0103-r16 BOOLEAN, + profile0x0104-r16 BOOLEAN +} + +SL-PreconfigDiscConfig-v1800 ::= SEQUENCE { + sl-RelayUE-PreconfigU2U-r18 SL-RelayUE-ConfigU2U-r18, + sl-RemoteUE-PreconfigU2U-r18 SL-RemoteUE-ConfigU2U-r18 +} + +-- TAG-SL-PRECONFIGURATIONNR-STOP +-- ASN1STOP + +``` + +Editor's Note: The mapping configuration (from e2e SLRB to RLC channel) is needed in pre-configuration. The existing table format is used as a baseline, subject to discussion during maintenance. + +| SL-PreconfigurationNR field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-DRX-PreConfig-GC-BC
This field indicates the sidelink DRX configuration for groupcast and broadcast communication, as specified in TS 38.321 [3]. | +| sl-OffsetDFN
Indicates the timing offset for the UE to determine DFN timing when GNSS is used for timing reference. Value 1 corresponds to 0.001 milliseconds, value 2 corresponds to 0.002 milliseconds, and so on. If the field is absent, no offset is applied. | +| sl-PreconfigDiscConfig
This field indicates the configuration for discovery message transmission used by NR sidelink U2N Remote UE, used by NR sidelink U2U Relay UE or used by NR sidelink U2U Remote UE. | +| sl-PreconfigEUTRA-AnchorCarrierFreqList
This field indicates the EUTRA anchor carrier frequency list, which can provide the NR sidelink communication configuration. | +| sl-PreconfigFreqInfoList, sl-PreconfigFreqInfoListSizeExt
This field indicates the NR sidelink communication and/ or NR sidelink discovery configuration some carrier frequency(ies). In this release, only one SL-FreqConfig can be configured in sl-PreconfigFreqInfoList . More entries of SL-FreqConfig can be configured in sl-PreconfigFreqInfoListSizeExt .. | +| sl-PreconfigNR-AnchorCarrierFreqList
This field indicates the NR anchor carrier frequency list, which can provide the NR sidelink communication configuration. | +| sl-RadioBearerPreConfigList
This field indicates one or multiple sidelink radio bearer configurations. | +| sl-RLC-BearerPreConfigList, sl-RLC-BearerPreConfigListSizeExt
This field indicates one or multiple sidelink RLC bearer configurations. | +| sl-RoHC-Profiles
This field indicates the supported RoHC profiles for NR sidelink communications. | +| sl-SSB-PriorityNR
This field indicates the priority of NR sidelink SSB transmission and reception. | +| sl-SyncFreqList
Indicates a list of candidate carrier frequencies that can be used for the synchronisation of NR sidelink communication. For SL-Freq-Id-r16 , the value 1 corresponds to the frequency of first entry in sl-PreconfigFreqInfoList , the value 2 corresponds to the frequency of first entry in sl-PreconfigFreqInfoListSizeExt , the value 3 corresponds to the frequency of second entry in sl-PreconfigFreqInfoListSizeExt and so on. | +| sl-SyncTxMultiFreq
Indicates that the UE transmits S-SSB on multiple carrier frequencies for NR sidelink communication. If this field is absent, the UE transmits S-SSB only on the synchronisation carrier frequency. | +| sl-TxProfileList
List of one or multiple Tx profiles, indicating the compatibility of supporting SL DRX as specified in TS 38.321 [3]. It is up to the UE implementation whether/how to apply this field. | + +— **End of NR-Sidelink-Preconf** + +-- ASN1START + +END + +-- ASN1STOP + +## 9.4 Radio Information Related to Discovery Message + +This clause specifies RRC information elements that are transferred in Discovery Message. + +### – ***SL-AccessInfo-L2U2N*** + +The IE *SL-AccessInfo-L2U2N* includes the radio information included in Discovery Message used for L2 U2N relay operation. + +### ***SL-AccessInfo-L2U2N* information elements** + +``` +-- ASN1START +-- TAG-SL-ACCESSINFO-L2U2N-START + +NR-Sidelink-DiscoveryMessage DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN +IMPORTS + CellAccessRelatedInfo, + SL-ServingCellInfo-r17 +FROM NR-RRC-Definitions; + +SL-AccessInfo-L2U2N-r17 ::= SEQUENCE { + cellAccessRelatedInfo-r17 CellAccessRelatedInfo, + sl-ServingCellInfo-r17 SL-ServingCellInfo-r17, + ... +} + +END + +-- TAG-SL-ACCESSINFO-L2U2N-STOP +-- ASN1STOP +``` + +## 9.5 Radio Information Related to TX Profile + +This clause specifies RRC information elements that are transferred in Tx Profile. + +### – *SL-TxProfile* + +The IE SL-TXProfile includes the Tx profile information. + +### *SL-TxProfile* information elements + +``` +-- ASN1START +-- TAG-SL-TXPROFILE-START + +SL-TxProfile DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +SL-TxProfile-v1800 ::= + ENUMERATED {backwardsCompatible, backwardsIncompatible, +spare6, spare5, spare4, spare3, spare2, spare1} + +END + +-- TAG-SL-TXPROFILE-STOP +-- ASN1STOP +``` + +# 10 Generic error handling + +## 10.1 General + +The generic error handling defined in the subsequent clauses applies unless explicitly specified otherwise e.g. within the procedure specific error handling. + +The UE shall consider a value as not comprehended when it is set: + +- to an extended value that is not defined in the version of the transfer syntax supported by the UE; +- to a spare or reserved value unless the specification defines specific behaviour that the UE shall apply upon receiving the concerned spare/reserved value. + +The UE shall consider a field as not comprehended when it is defined: + +- as spare or reserved unless the specification defines specific behaviour that the UE shall apply upon receiving the concerned spare/reserved field. + +## 10.2 ASN.1 violation or encoding error + +The UE shall: + +- 1> when receiving an RRC message on the BCCH, CCCH, PCCH, MCCH or a PC5 RRC message on SBCCH for which the abstract syntax is invalid [6]: + - 2> ignore the message. + +NOTE: This clause applies in case one or more fields is set to a value, other than a spare, reserved or extended value, not defined in this version of the transfer syntax. E.g. in the case the UE receives value 12 for a field defined as INTEGER (1..11). In cases like this, it may not be possible to reliably detect which field is in the error hence the error handling is at the message level. + +## 10.3 Field set to a not comprehended value + +The UE shall, when receiving an RRC message or PC5 RRC message on any logical channel: + +- 1> if the message includes a field that has a value that the UE does not comprehend: + +- 2> if a default value is defined for this field: + - 3> treat the message while using the default value defined for this field; +- 2> else if the concerned field is optional: + - 3> treat the message as if the field were absent and in accordance with the need code for absence of the concerned field; +- 2> else: + - 3> treat the message as if the field were absent and in accordance with clause 10.4. + +## 10.4 Mandatory field missing + +The UE shall: + +- 1> if the message includes a field that is mandatory to include in the message (e.g. because conditions for mandatory presence are fulfilled) and that field is absent or treated as absent: + - 2> if the RRC message was not received on DCCH or CCCH; or + - 2> if the PC5 RRC message was not received on SCCH: + - 3> if the field concerns a (sub-field of) an entry of a list (i.e. a SEQUENCE OF): + - 4> treat the list as if the entry including the missing or not comprehended field was absent; + - 3> else if the field concerns a sub-field of another field, referred to as the 'parent' field i.e. the field that is one nesting level up compared to the erroneous field: + - 4> consider the 'parent' field to be set to a not comprehended value; + - 4> apply the generic error handling to the subsequent 'parent' field(s), until reaching the top nesting level i.e. the message level; + - 3> else (field at message level): + - 4> ignore the message. + +NOTE 1: The error handling defined in these clauses implies that the UE ignores a message with the message type or version set to a not comprehended value. + +NOTE 2: The nested error handling for messages received on logical channels other than DCCH, CCCH and SCCH applies for errors in extensions also, even for errors that can be regarded as invalid network operation e.g. the network not observing conditional presence. + +NOTE 3: UE behaviour on receipt of an RRC message on DCCH or CCCH or a PC5 RRC message on SCCH that does not include a field that is mandatory (e.g. because conditions for mandatory presence are fulfilled) is unspecified. + +The following ASN.1 further clarifies the levels applicable in case of nested error handling for errors in extension fields. + +``` +-- /example/ ASN1START + +-- Example with extension addition group + +ItemInfoList ::= + SEQUENCE (SIZE (1..max)) OF ItemInfo + +ItemInfo ::= + SEQUENCE { + itemIdentity INTEGER (1..max), + field1 Field1, + field2 Field2 OPTIONAL, -- Need N + ... + [[ + field3-r9 Field3-r9 OPTIONAL, -- Cond Cond1 + field4-r9 Field4-r9 OPTIONAL -- Need N + ]] + } +``` + +``` + +} + +-- Example with traditional non-critical extension (empty sequence) + +BroadcastInfoBlock1 ::= SEQUENCE { + itemIdentity INTEGER (1..max), + field1 Field1, + field2 Field2, + nonCriticalExtension BroadcastInfoBlock1-v940-IEs OPTIONAL -- Need N +} + +BroadcastInfoBlock1-v940-IEs ::= SEQUENCE { + field3-r9 Field3-r9 OPTIONAL, -- Cond Cond1 + field4-r9 Field4-r9 OPTIONAL, -- Need N + nonCriticalExtension SEQUENCE {} OPTIONAL -- Need S +} + +-- ASN1STOP + +``` + +The UE shall, apply the following principles regarding the levels applicable in case of nested error handling: + +- an extension addition group is not regarded as a level on its own. E.g. in the ASN.1 extract in the previous, a error regarding the conditionality of *field3* would result in the entire *itemInfo* entry to be ignored (rather than just the extension addition group containing *field3* and *field4*); +- a traditional *nonCriticalExtension* is not regarded as a level on its own. E.g. in the ASN.1 extract in the previous, an error regarding the conditionality of *field3* would result in the entire *BroadcastInfoBlock1* to be ignored (rather than just the non-critical extension containing *field3* and *field4*). + +## 10.5 Not comprehended field + +The UE shall, when receiving an RRC message on any logical channel: + +- 1> if the message includes a field that the UE does not comprehend: + - 2> treat the rest of the message as if the field was absent. + +NOTE: This clause does not apply to the case of an extension to the value range of a field. Such cases are addressed instead by the requirements in clause 10.3. + +# 11 Radio information related interactions between network nodes + +## 11.1 General + +This clause specifies RRC messages that are transferred between network nodes. These RRC messages may be transferred to or from the UE via another Radio Access Technology. Consequently, these messages have similar characteristics as the RRC messages that are transferred across the NR radio interface, i.e. the same transfer syntax and protocol extension mechanisms apply. + +## 11.2 Inter-node RRC messages + +### 11.2.1 General + +This clause specifies RRC messages that are sent either across the X2-, Xn- or the NG-interface, either to or from the gNB, i.e. a single 'logical channel' is used for all RRC messages transferred across network nodes. The information could originate from or be destined for another RAT. + +``` +-- ASN1START +-- TAG-NR-INTER-NODE-DEFINITIONS-START + +NR-InterNodeDefinitions DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +IMPORTS + AffectedCarrierFreqCombList-r16, + AffectedCarrierFreqRangeCombList-r18, + ARFCN-ValueNR, + ARFCN-ValueEUTRA, + CandidateServingFreqListNR-r16, + CandidateServingFreqRangeListNR-r18, + CellIdentity, + CGI-InfoEUTRA, + CGI-InfoNR, + CondReconfigExecCondSCG-r17, + CSI-RS-Index, + CSI-RS-CellMobility, + DRX-Config, + EUTRA-PhysCellId, + FeatureSetDownlinkPerCC-Id, + FeatureSetUplinkPerCC-Id, + FlightPathInfoReport-r18, + FreqBandIndicatorNR, + GapConfig, + IDC-TDM-Assistance-r18, + maxBandComb, + maxBands, + maxBandsEUTRA, +``` + +maxCandidateBandIndex-r18, +maxCellSFTD, +maxFeatureSetsPerBand, +maxFreq, +maxFreqIDC-MRDC, +maxNrofCombIDC, +maxNrofCondCells-r16, +maxNrofCondCells-1-r17, +maxNrofPhysicalResourceBlocks, +maxNrofSCells, +maxNrofServingCells, +maxNrofServingCells-1, +maxNrofServingCellsEUTRA, +maxNrofIndexesToReport, +maxSimultaneousBands, +MBSInterestIndication-r17, +MeasQuantityResults, +MeasResultCellListSFTD-EUTRA, +MeasResultCellListSFTD-NR, +MeasResultList2NR, +MeasResultSCG-Failure, +MeasResultServFreqListEUTRA-SCG, +MUSIM-CandidateBandList-r18, +MUSIM-CapRestriction-r18, +MUSIM-GapConfig-r17, +NeedForGapsInfoNR-r16, +NeedForGapNCSG-InfoNR-r17, +NeedForGapNCSG-InfoEUTRA-r17, +NeedForInterruptionInfoNR-r18, +OverheatingAssistance, +OverheatingAssistance-r17, +P-Max, +PhysCellId, +RadioBearerConfig, +RAN-NotificationAreaInfo, +ReferenceConfiguration-r18, +ReportConfigNR, +RRCReconfiguration, +ServCellIndex, +SetupRelease, +SSB-Index, +SSB-MTC, +SSB-ToMeasure, +SS-RSSI-Measurement, +ShortMAC-I, +SubcarrierSpacing, +UEAssistanceInformation, +UE-CapabilityRAT-ContainerList, +maxNrofCLI-RSSI-Resources-r16, +maxNrofCLI-SRS-Resources-r16, +RSSI-ResourceId-r16, +SDT-Config-r17, +SidelinkUEInformationNR-r16, + +``` + + SRS-ResourceId, + UE-RadioPagingInfo-r17 +FROM NR-RRC-Definitions; + +-- TAG-NR-INTER-NODE-DEFINITIONS-STOP +-- ASN1STOP + +``` + +### 11.2.2 Message definitions + +#### — *CG-CandidateList* + +This message is used to transfer the SCG radio configuration for one or more candidate cells for Conditional PSCell Addition (CPA) or Conditional PSCell Change (CPC) as generated by the candidate target SgNB. + +Direction: Secondary gNB to master gNB or eNB. + +#### ***CG-CandidateList message*** + +``` + +-- ASN1START +-- TAG-CG-CANDIDATELIST-START + +CG-CandidateList ::= + criticalExtensions SEQUENCE { + c1 CHOICE { + cg-CandidateList-r17 CG-CandidateList-r17-IEs, + spare3 NULL, spare2 NULL, spare1 NULL + }, + criticalExtensionsFuture SEQUENCE {} + } +} + +CG-CandidateList-r17-IEs ::= + cg-CandidateToAddModList-r17 SEQUENCE (SIZE (1..maxNrofCondCells-r16)) OF CG-CandidateInfo-r17 OPTIONAL, + cg-CandidateToReleaseList-r17 SEQUENCE (SIZE (1..maxNrofCondCells-r16)) OF CG-CandidateInfoId-r17 OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL + +CG-CandidateInfo-r17 ::= + cg-CandidateInfoId-r17 CG-CandidateInfoId-r17, + candidateCG-Config-r17 OCTET STRING (CONTAINING CG-Config) +} + +CG-CandidateInfoId-r17 ::= + ssbFrequency-r17 ARFCN-ValueNR, + physCellId-r17 PhysCellId +} + +-- TAG-CG-CANDIDATELIST-STOP +-- ASN1STOP + +``` + +| CG-CandidateList field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| cg-CandidateToAddModList
Contains information regarding candidate target cells to be added or modified for Conditional PSCell Addition (CPA), Conditional PSCell Change (CPC), or CHO with candidate SCG(s) from the candidate target secondary node to the master node. | +| cg-CandidateToReleaseList
Contains information regarding candidate target cells for CPA, CPC, or CHO with candidate SCG(s) to be removed from the candidate target secondary node to the master node. This list is not used in CPA or CPC preparation. | + +| CG-CandidateInfo field descriptions | +|-----------------------------------------------------------------------------------------------------------------| +| cg-CandidateInfo
SSB frequency and Physical Cell Identity of the candidate target cell. | +| candidateCG-Config
CG-Config message corresponding to the cell indicated by cg-CandidateInfo . | + +#### — *HandoverCommand* + +This message is used to transfer the handover command as generated by the target gNB. + +Direction: target gNB to source gNB/source RAN. + +#### ***HandoverCommand message*** + +``` +-- ASN1START +-- TAG-HANDOVER-COMMAND-START + +HandoverCommand ::= + SEQUENCE { + criticalExtensions + CHOICE { + c1 + CHOICE { + handoverCommand + HandoverCommand-IEs, + spare3 NULL, spare2 NULL, spare1 NULL + }, + criticalExtensionsFuture + SEQUENCE {} + } + } + +HandoverCommand-IEs ::= + SEQUENCE { + handoverCommandMessage + OCTET STRING (CONTAINING RRCReconfiguration), + nonCriticalExtension + HandoverCommand-v1800-IEs + OPTIONAL + } + +HandoverCommand-v1800-IEs ::= + SEQUENCE { + candPSCellExecutionConditionInfo-r18 + CandPSCellExecutionConditionInfo-r18 + OPTIONAL, + nonCriticalExtension + SEQUENCE {} + OPTIONAL + } +``` + +``` + +CandPSCellExecutionConditionInfo-r18 ::= SEQUENCE { + candPSCellExecCondReportConfigNR-r18 ReportConfigNR, + ... +} + +-- TAG-HANDOVER-COMMAND-STOP +-- ASN1STOP + +``` + +| HandoverCommand field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| candPSCellExecCondReportConfigNR
Contains execution condition parameters of candidate PSCells in case of CHO with candidate SCG(s). This fields can include only a4-Threshold, hysteresis, timeToTrigger, and rsType . | +| handoverCommandMessage
Contains the RRCReconfiguration message used to perform handover within NR or handover to NR, as generated (entirely) by the target gNB. | + +#### — **HandoverPreparationInformation** + +This message is used to transfer the NR RRC information used by the target gNB during handover preparation or UE context retrieval, e.g. in case of resume or re-establishment, including UE capability information. This message is also used for transferring the information between the CU and DU. + +Direction: source gNB/source RAN to target gNB or CU to DU. + +#### **HandoverPreparationInformation message** + +``` + +-- ASN1START +-- TAG-HANDOVER-PREPARATION-INFORMATION-START + +HandoverPreparationInformation ::= SEQUENCE { + criticalExtensions CHOICE { + c1 CHOICE{ + handoverPreparationInformation HandoverPreparationInformation-IEs, + spare3 NULL, spare2 NULL, spare1 NULL + }, + criticalExtensionsFuture SEQUENCE {} + } +} + +HandoverPreparationInformation-IEs ::= SEQUENCE { + ue-CapabilityRAT-List UE-CapabilityRAT-ContainerList, + sourceConfig AS-Config OPTIONAL, -- Cond HO + rrm-Config RRM-Config OPTIONAL, + as-Context AS-Context OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +AS-Config ::= SEQUENCE { + rrcReconfiguration OCTET STRING (CONTAINING RRCReconfiguration), +} + +``` + +``` + + ... + [[ + sourceRB-SN-Config OCTET STRING (CONTAINING RadioBearerConfig) OPTIONAL, + sourceSCG-NR-Config OCTET STRING (CONTAINING RRCReconfiguration) OPTIONAL, + sourceSCG-EUTRA-Config OCTET STRING OPTIONAL + ]], + [[ + sourceSCG-Configured ENUMERATED {true} OPTIONAL + ]], + [[ + sdt-Config-r17 SDT-Config-r17 OPTIONAL + ]] + } + + AS-Context ::= SEQUENCE { + reestablishmentInfo ReestablishmentInfo OPTIONAL, + configRestrictInfo ConfigRestrictInfoSCG OPTIONAL, + ... + [[ + ran-NotificationAreaInfo RAN-NotificationAreaInfo OPTIONAL + ]], + [[ + ueAssistanceInformation OCTET STRING (CONTAINING UEAssistanceInformation) OPTIONAL -- Cond HO2 + ]], + [[ + selectedBandCombinationSN BandCombinationInfoSN OPTIONAL + ]], + [[ + configRestrictInfoDAPS-r16 ConfigRestrictInfoDAPS-r16 OPTIONAL, + sidelinkUEInformationNR-r16 OCTET STRING OPTIONAL, + sidelinkUEInformationEUTRA-r16 OCTET STRING OPTIONAL, + ueAssistanceInformationEUTRA-r16 OCTET STRING OPTIONAL, + ueAssistanceInformationSCG-r16 OCTET STRING (CONTAINING UEAssistanceInformation) OPTIONAL -- Cond HO2 + needForGapsInfoNR-r16 NeedForGapsInfoNR-r16 OPTIONAL + ]], + [[ + configRestrictInfoDAPS-v1640 ConfigRestrictInfoDAPS-v1640 OPTIONAL + ]], + [[ + needForGapNCSG-InfoNR-r17 NeedForGapNCSG-InfoNR-r17 OPTIONAL, + needForGapNCSG-InfoEUTRA-r17 NeedForGapNCSG-InfoEUTRA-r17 OPTIONAL, + mbsInterestIndication-r17 OCTET STRING (CONTAINING MBSInterestIndication-r17) OPTIONAL + ]], + [[ + needForInterruptionInfoNR-r18 NeedForInterruptionInfoNR-r18 OPTIONAL, + flightPathInfoReport-r18 FlightPathInfoReport-r18 OPTIONAL + ]] + } + + ConfigRestrictInfoDAPS-r16 ::= SEQUENCE { + powerCoordination-r16 SEQUENCE { + p-DAPS-Source-r16 P-Max, + p-DAPS-Target-r16 P-Max, + uplinkPowerSharingDAPS-Mode-r16 ENUMERATED {semi-static-model, semi-static-mode2, dynamic } + } + } + +``` + +``` + +} + +ConfigRestrictInfoDAPS-v1640 ::= SEQUENCE { + sourceFeatureSetPerDownlinkCC-r16 FeatureSetDownlinkPerCC-Id, + sourceFeatureSetPerUplinkCC-r16 FeatureSetUplinkPerCC-Id +} + +ReestablishmentInfo ::= SEQUENCE { + sourcePhysCellId PhysCellId, + targetCellShortMAC-I ShortMAC-I, + additionalReestablishmentInfoList ReestablishmentNCellInfoList OPTIONAL +} + +ReestablishmentNCellInfoList ::= SEQUENCE ( SIZE (1..maxCellPrep) ) OF ReestablishmentNCellInfo + +ReestablishmentNCellInfo ::= SEQUENCE { + cellIdentity CellIdentity, + key-gNodeB-Star BIT STRING (SIZE (256)), + shortMAC-I ShortMAC-I +} + +RRM-Config ::= SEQUENCE { + ue-InactiveTime ENUMERATED { + s1, s2, s3, s5, s7, s10, s15, s20, + s25, s30, s40, s50, min1, min1s20, min1s40, + min2, min2s30, min3, min3s30, min4, min5, min6, + min7, min8, min9, min10, min12, min14, min17, min20, + min24, min28, min33, min38, min44, min50, hr1, + hr1min30, hr2, hr2min30, hr3, hr3min30, hr4, hr5, hr6, + hr8, hr10, hr13, hr16, hr20, day1, day1hr12, day2, + day2hr12, day3, day4, day5, day7, day10, day14, day19, + day24, day30, dayMoreThan30} OPTIONAL, + candidateCellInfoList MeasResultList2NR OPTIONAL, + ... + [[ + candidateCellInfoListSN-EUTRA MeasResultServFreqListEUTRA-SCG OPTIONAL + ]] +} + +-- TAG-HANDOVER-PREPARATION-INFORMATION-STOP +-- ASN1STOP + +``` + +| HandoverPreparationInformation field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| as-Context
Local RAN context required by the target gNB or DU. | +| rrm-Config
Local RAN context used mainly for RRM purposes. | +| sourceConfig
The radio resource configuration as used in the source cell. | +| ue-CapabilityRAT-List
The UE radio access related capabilities concerning RATs supported by the UE. A gNB that retrieves MRDC related capability containers ensures that the set of included MRDC containers is consistent w.r.t. the feature set related information. | +| ue-InactiveTime
Duration while UE has not received or transmitted any user data. Thus the timer is still running in case e.g., UE measures the neighbour cells for the HO purpose. Value s1 corresponds to 1 second, s2 corresponds to 2 seconds and so on. Value min1 corresponds to 1 minute, value min1s20 corresponds to 1 minute and 20 seconds, value min1s40 corresponds to 1 minute and 40 seconds and so on. Value hr1 corresponds to 1 hour, hr1min30 corresponds to 1 hour and 30 minutes and so on. | + +| AS-Config field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| rrcReconfiguration
Contains the RRCReconfiguration configuration as generated entirely by the MN. If the TMGI-r17 is included in the MRB-ToAddMod-r17 in the RadioBearerConfig , the plmn-Index is replaced by the PLMN ID, if needed. | +| sdt-Config
Contains the IE SDT-Config as generated entirely by the last serving gNB. This field is only used during the SDT procedure and the RNA update procedure with UE context relocation as defined in TS 38.300 [2], clause 18.2 and 9.2.2.5 respectively. | +| sourceRB-SN-Config
Contains the IE RadioBearerConfig as generated entirely by the SN. This field is only used when the UE is configured with SN terminated RB(s). | +| sourceSCG-Configured
Value true indicates that the UE is configured with NR or EUTRA SCG in source configuration. The field is only used in NR-DC and NE-DC and is included only if the fields sourceSCG-NR-Config and sourceSCG-EUTRA-Config are absent. | +| sourceSCG-EUTRA-Config
Contains the current dedicated SCG configuration in RRConnectionReconfiguration message as specified in TS 36.331 [10] and generated entirely by the SN. In this version of the specification, the E-UTRA RRConnectionReconfiguration message can only include the field scg-Configuration . This field is only used in NE-DC. | +| sourceSCG-NR-Config
Contains the current dedicated SCG configuration in RRReconfiguration message as generated entirely by the SN. In this version of the specification, the RRReconfiguration message can only include fields secondaryCellGroup and measConfig . This field is only used in NR-DC. | + +| AS-Context field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| configRestrictInfoDAPS
Includes fields for which source cell explicitly indicates the restriction to be observed by target cell during DAPS handover. | +| mbsInterestIndication
Includes the information last reported by the UE in the NR MBSInterestIndication message, where the plmn-Index (if included by the UE in tmgi ) is replaced by the PLMN ID, if needed. A TMGI for which the plmn-Index points to a non-serving SNPN is removed from the NR MBSInterestIndication message. | +| needForGapsInfoNR
Includes measurement gap requirement information of the UE for NR target bands. | +| selectedBandCombinationSN
Indicates the band combination selected by SN in (NG)EN-DC, NE-DC, and NR-DC. | +| sidelinkUEInformationEUTRA
This field includes SidelinkUEInformation IE as specified in TS 36.331 [10]. | +| sidelinkUEInformationNR
This field includes SidelinkUEInformationNR IE. | +| ueAssistanceInformation
Includes for each UE assistance feature the information last reported by the UE, if any. | +| ueAssistanceInformationSCG
Includes for each UE assistance feature associated with the SCG, the information last reported by the UE in the NR UEAssistanceInformation message for the SCG, if any. | + +| ConfigRestrictInfoDAPS field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| sourceFeatureSetPerUplinkCC/sourceFeatureSetPerDownlinkCC
Indicates an index referring to the position of the FeatureSetUplinkPerCC/FeatureSetDownlinkPerCC selected by source in the featureSetsUplinkPerCC/featureSetsDownlinkPerCC . | + +| RRM-Config field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| candidateCellInfoList
A list of the best cells on each frequency for which measurement information was available | +| candidateCellInfoListSN-EUTRA
A list of EUTRA cells including serving cells and best neighbour cells on each serving frequency, for which measurement results were available. This field is only used in NE-DC. | + +| Conditional Presence | Explanation | +|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| HO | The field is mandatory present in case of handover within NR or UE context retrieval, e.g. in case of resume or re-establishment. The field is optionally present in case of handover from E-UTRA/5GC. Otherwise the field is absent. | +| HO2 | The field is optionally present in case of handover within NR; otherwise the field is absent. | + +NOTE 1: The following table indicates per source RAT whether RAT capabilities are included or not. + +| Source RAT | NR capabilities | E-UTRA capabilities | MR-DC capabilities | UTRA capabilities | +|------------|---------------------------------------------------------------------------------------------------------------|---------------------|--------------------|---------------------------------------------| +| NR | May be included if UE Radio Capability ID as specified in 23.502 [43] is used for the UE. Included otherwise. | May be included | May be included | May be included, ignored by gNB if received | +| E-UTRAN | May be included if UE Radio Capability ID as specified in 23.502 [43] is used for the UE. Included otherwise. | May be included | May be included | May be included, ignored by gNB if received | + +NOTE 2: The following table indicates, in case of inter-RAT handover from E-UTRA, which additional IEs are included or not: + +| Source system | sourceConfig | rrm-Config | as-Context | +|---------------|---------------------------------------------------------------------------------------------------|-----------------|--------------| +| E-UTRA/EPC | Not included | May be included | Not included | +| E-UTRA/5GC | May be included, but only radioBearerConfig is included in the RRCReconfiguration . | May be included | Not included | + +#### — CG-Config + +This message is used to transfer the SCG radio configuration as generated by the SgNB or SeNB. It can also be used by a CU to request a DU to perform certain actions, e.g. to request the DU to perform a new lower layer configuration. + +Direction: Secondary gNB or eNB to master gNB or eNB, alternatively CU to DU. + +#### CG-Config message + +``` +-- ASN1START +-- TAG-CG-CONFIG-START + +CG-Config ::= + SEQUENCE { + criticalExtensions + CHOICE { + c1 + CHOICE { + cg-Config + CG-Config-IEs, + spare3 NULL, spare2 NULL, spare1 NULL + }, + criticalExtensionsFuture + SEQUENCE {} + } + } + +CG-Config-IEs ::= + SEQUENCE { + scg-CellGroupConfig + OCTET STRING (CONTAINING RRCReconfiguration) + OPTIONAL, + scg-RB-Config + OCTET STRING (CONTAINING RadioBearerConfig) + OPTIONAL, + configRestrictModReq + ConfigRestrictModReqSCG + OPTIONAL, + drx-InfoSCG + DRX-Info + OPTIONAL, + candidateCellInfoListSN + OCTET STRING (CONTAINING MeasResultList2NR) + OPTIONAL, + measConfigSN + MeasConfigSN + OPTIONAL, + selectedBandCombination + BandCombinationInfoSN + OPTIONAL, + } +-- ASN1END +``` + +``` + + fr-InfoListSCG FR-InfoList OPTIONAL, + candidateServingFreqListNR CandidateServingFreqListNR OPTIONAL, + nonCriticalExtension CG-Config-v1540-IEs OPTIONAL +} + +CG-Config-v1540-IEs ::= SEQUENCE { + pSCellFrequency ARFCN-ValueNR OPTIONAL, + reportCGI-RequestNR SEQUENCE { + requestedCellInfo SEQUENCE { + ssbFrequency ARFCN-ValueNR, + cellForWhichToReportCGI PhysCellId + } + } + ph-InfoSCG PH-TypeListSCG OPTIONAL, + nonCriticalExtension CG-Config-v1560-IEs OPTIONAL +} + +CG-Config-v1560-IEs ::= SEQUENCE { + pSCellFrequencyEUTRA ARFCN-ValueEUTRA OPTIONAL, + scg-CellGroupConfigEUTRA OCTET STRING OPTIONAL, + candidateCellInfoListSN-EUTRA OCTET STRING OPTIONAL, + candidateServingFreqListEUTRA CandidateServingFreqListEUTRA OPTIONAL, + needForGaps ENUMERATED {true} OPTIONAL, + drx-ConfigSCG DRX-Config OPTIONAL, + reportCGI-RequestEUTRA SEQUENCE { + requestedCellInfoEUTRA SEQUENCE { + eutraFrequency ARFCN-ValueEUTRA, + cellForWhichToReportCGI-EUTRA EUTRA-PhysCellId + } + } + nonCriticalExtension CG-Config-v1590-IEs OPTIONAL +} + +CG-Config-v1590-IEs ::= SEQUENCE { + scellFrequenciesSN-NR SEQUENCE (SIZE (1.. maxNrofServingCells-1)) OF ARFCN-ValueNR OPTIONAL, + scellFrequenciesSN-EUTRA SEQUENCE (SIZE (1.. maxNrofServingCells-1)) OF ARFCN-ValueEUTRA OPTIONAL, + nonCriticalExtension CG-Config-v1610-IEs OPTIONAL +} + +CG-Config-v1610-IEs ::= SEQUENCE { + drx-InfoSCG2 DRX-Info2 OPTIONAL, + nonCriticalExtension CG-Config-v1620-IEs OPTIONAL +} + +CG-Config-v1620-IEs ::= SEQUENCE { + ueAssistanceInformationSCG-r16 OCTET STRING (CONTAINING UEAssistanceInformation) OPTIONAL, + nonCriticalExtension CG-Config-v1630-IEs OPTIONAL +} + +CG-Config-v1630-IEs ::= SEQUENCE { + selectedToffset-r16 T-Offset-r16 OPTIONAL, + nonCriticalExtension CG-Config-v1640-IEs OPTIONAL +} + +``` + +``` + +CG-Config-v1640-IEs ::= SEQUENCE { + servCellInfoListSCG-NR-r16 ServCellInfoListSCG-NR-r16 OPTIONAL, + servCellInfoListSCG-EUTRA-r16 ServCellInfoListSCG-EUTRA-r16 OPTIONAL, + nonCriticalExtension CG-Config-v1700-IEs OPTIONAL +} + +CG-Config-v1700-IEs ::= SEQUENCE { + candidateCellInfoListCPC-r17 CandidateCellInfoListCPC-r17 OPTIONAL, + twoPHRModeSCG-r17 ENUMERATED {enabled} OPTIONAL, + nonCriticalExtension CG-Config-v1730-IEs OPTIONAL +} + +CG-Config-v1730-IEs ::= SEQUENCE { + fr1-Carriers-SCG-r17 INTEGER (1..32) OPTIONAL, + fr2-Carriers-SCG-r17 INTEGER (1..32) OPTIONAL, + nonCriticalExtension CG-Config-v1800-IEs OPTIONAL +} + +CG-Config-v1800-IEs ::= SEQUENCE { + candidateServingFreqRangeListNR-r18 CandidateServingFreqRangeListNR-r18 OPTIONAL, + candidateServingFreqListNR-r16 CandidateServingFreqListNR-r16 OPTIONAL, + idc-TDM-AssistanceConfig-r18 ENUMERATED {enabled} OPTIONAL, + candidateCellInfoListSubsequentCPC-r18 CandidateCellInfoListCPC-r17 OPTIONAL, + scpac-ReferenceConfigurationSCG-r18 ReferenceConfiguration-r18 OPTIONAL, + nonCriticalExtension SEQUENCE { OPTIONAL +} + +ServCellInfoListSCG-NR-r16 ::= SEQUENCE (SIZE (1.. maxNrofServingCells)) OF ServCellInfoXCG-NR-r16 + +ServCellInfoXCG-NR-r16 ::= SEQUENCE { + dl-FreqInfo-NR-r16 FrequencyConfig-NR-r16 OPTIONAL, + ul-FreqInfo-NR-r16 FrequencyConfig-NR-r16 OPTIONAL, -- Cond FDD + ... +} + +FrequencyConfig-NR-r16 ::= SEQUENCE { + freqBandIndicatorNR-r16 FreqBandIndicatorNR, + carrierCenterFreq-NR-r16 ARFCN-ValueNR, + carrierBandwidth-NR-r16 INTEGER (1..maxNrofPhysicalResourceBlocks), + subcarrierSpacing-NR-r16 SubcarrierSpacing +} + +ServCellInfoListSCG-EUTRA-r16 ::= SEQUENCE (SIZE (1.. maxNrofServingCellsEUTRA)) OF ServCellInfoXCG-EUTRA-r16 + +ServCellInfoXCG-EUTRA-r16 ::= SEQUENCE { + dl-CarrierFreq-EUTRA-r16 ARFCN-ValueEUTRA OPTIONAL, + ul-CarrierFreq-EUTRA-r16 ARFCN-ValueEUTRA OPTIONAL, -- Cond FDD + transmissionBandwidth-EUTRA-r16 TransmissionBandwidth-EUTRA-r16 OPTIONAL, + ... +} + +TransmissionBandwidth-EUTRA-r16 ::= ENUMERATED {rb6, rb15, rb25, rb50, rb75, rb100} + +``` + +``` + +PH-TypeListSCG ::= SEQUENCE (SIZE (1..maxNrofServingCells)) OF PH-InfoSCG + +PH-InfoSCG ::= SEQUENCE { + servCellIndex ServCellIndex, + ph-Uplink PH-UplinkCarrierSCG, + ph-SupplementaryUplink PH-UplinkCarrierSCG OPTIONAL, + ... + [[ + twoSRS-PUSCH-Repetition-r17 ENUMERATED{enabled} OPTIONAL + ]] +} + +PH-UplinkCarrierSCG ::= SEQUENCE{ + ph-Type1or3 ENUMERATED {type1, type3}, + ... +} + +MeasConfigSN ::= SEQUENCE { + measuredFrequenciesSN SEQUENCE (SIZE (1..maxMeasFreqsSN)) OF NR-FreqInfo OPTIONAL, + ... +} + +NR-FreqInfo ::= SEQUENCE { + measuredFrequency ARFCN-ValueNR OPTIONAL, + ... +} + +ConfigRestrictModReqSCG ::= SEQUENCE { + requestedBC-MRDC BandCombinationInfoSN OPTIONAL, + requestedP-MaxFR1 P-Max OPTIONAL, + ... + [[ + requestedPDCCH-BlindDetectionSCG INTEGER (1..15) OPTIONAL, + requestedP-MaxEUTRA P-Max OPTIONAL + ]], + [[ + requestedP-MaxFR2-r16 P-Max OPTIONAL, + requestedMaxInterFreqMeasIdSCG-r16 INTEGER(1..maxMeasIdentitiesMN) OPTIONAL, + requestedMaxIntraFreqMeasIdSCG-r16 INTEGER(1..maxMeasIdentitiesMN) OPTIONAL, + requestedToffset-r16 T-Offset-r16 OPTIONAL + ]], + [[ + reservedResourceConfigNRDC-r17 ResourceConfigNRDC-r17 OPTIONAL + ]] +} + +BandCombinationIndex ::= INTEGER (1..maxBandComb) + +BandCombinationInfoSN ::= SEQUENCE { + bandCombinationIndex BandCombinationIndex, + requestedFeatureSets FeatureSetEntryIndex +} + +``` + +``` + +FR-InfoList ::= SEQUENCE (SIZE (1..maxNrofServingCells-1)) OF FR-Info + +FR-Info ::= SEQUENCE { + servCellIndex ServCellIndex, + fr-Type ENUMERATED {fr1, fr2} +} + +CandidateServingFreqListNR ::= SEQUENCE (SIZE (1.. maxFreqIDC-MRDC)) OF ARFCN-ValueNR + +CandidateServingFreqListEUTRA ::= SEQUENCE (SIZE (1.. maxFreqIDC-MRDC)) OF ARFCN-ValueEUTRA + +T-Offset-r16 ::= ENUMERATED {ms0dot5, ms0dot75, ms1, ms1dot5, ms2, ms2dot5, ms3, spare1} + +CandidateCellInfoListCPC-r17 ::= SEQUENCE (SIZE (1..maxFreq)) OF CandidateCellInfo-r17 + +CandidateCellInfo-r17 ::= SEQUENCE { + ssbFrequency-r17 ARFCN-ValueNR, + candidateList-r17 SEQUENCE (SIZE (1..maxNrofCondCells-r16)) OF CandidateCell-r17 +} + +CandidateCell-r17 ::= SEQUENCE { + physCellId-r17 PhysCellId, + condExecutionCondSCG-r17 OCTET STRING (CONTAINING CondReconfigExecCondSCG-r17) OPTIONAL +} + +-- TAG-CG-CONFIG-STOP +-- ASN1STOP + +``` + +| CG-Config field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| candidateCellInfoListCPC
Contains information regarding candidate target cells for Conditional PSCell Change (CPC) that the source secondary gNB suggests the target secondary gNB to consider configuring for CPC. | +| candidateCellInfoListSN
Contains information regarding cells that the source secondary node suggests the target secondary gNB to consider configuring. | +| candidateCellInfoListSN-EUTRA
Includes the MeasResultList3EUTRA as specified in TS 36.331 [10]. Contains information regarding cells that the source secondary node suggests the target secondary eNB to consider configuring. This field is only used in NE-DC. | +| candidateCellInfoListSubsequentCPC
Contains information regarding candidate target cells for subsequent CPAC that the master gNB or source secondary gNB suggests the target secondary gNB to consider configuring for subsequent CPAC. | +| candidateServingFreqListNR, candidateServingFreqListEUTRA
Indicates frequencies of candidate serving cells for In-Device Co-existence Indication (see TS 36.331 [10]). | +| candidateServingFreqListNR-r16
indicates the candidate frequencies configured by SN for IDC. This field is only used in NR-DC. | +| candidateServingFreqRangeListNR
indicates the candidate frequency ranges configured by SN for IDC. This field is only used in NR-DC. | +| configRestrictModReq
Used by SN to request changes to SCG configuration restrictions previously set by MN to ensure UE capabilities are respected. E.g. can be used to request configuring an NR band combination whose use MN has previously forbidden. SN only includes this field in SN-initiated procedures. | +| drx-ConfigSCG
This field contains the complete DRX configuration of the SCG. This field is only used in NR-DC. | +| drx-InfoSCG
This field contains the DRX long and short cycle configuration of the SCG. This field is used in (NG)EN-DC and NE-DC. | +| drx-InfoSCG2
This field contains the drx-onDurationTimer configuration of the SCG. This field is only used in (NG)EN-DC. | +| fr-InfoListSCG
Contains information of FR information of serving cells that include PSCell and SCells configured in SCG. | +| fr1-Carriers-SCG, fr2-Carriers-SCG
Indicates the number of FR1 or FR2 serving cells configured in SCG. | +| idc-TDM-AssistanceConfig
Indicates if the IDC TDM reporting is enabled for the UE by SN. This field is only used in NR-DC. | +| measuredFrequenciesSN
Used by SN to indicate a list of frequencies measured by the UE. | +| needForGaps
In NE-DC, indicates whether the SN requests gNB to configure measurements gaps. | +| ph-InfoSCG
Power headroom information in SCG that is needed in the reception of PHR MAC CE of MCG | +| ph-SupplementaryUplink
Power headroom information for supplementary uplink. In the case of (NG)EN-DC and NR-DC, this field is only present when two UL carriers are configured for a serving cell and one UL carrier reports type1 PH while the other reports type 3 PH. | +| ph-Type1or3
Type of power headroom for a certain serving cell in SCG (PSCell and activated SCells). Value type1 refers to type 1 power headroom, value type3 refers to type 3 power headroom. (See TS 38.321 [3]). | + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ph-Uplink
Power headroom information for uplink. | +| pSCellFrequency, pSCellFrequencyEUTRA
Indicates the frequency of PSCell in NR (i.e., pSCellFrequency ) or E-UTRA (i.e., pSCellFrequencyEUTRA ). In this version of the specification, pSCellFrequency is not used in NE-DC whereas pSCellFrequencyEUTRA is only used in NE-DC. pSCellFrequency indicates the absoluteFrequencySSB . | +| reportCGI-RequestNR, reportCGI-RequestEUTRA
Used by SN to indicate to MN about configuring reportCGI procedure. The request may optionally contain information about the cell for which SN intends to configure reportCGI procedure. In this version of the specification, the reportCGI-RequestNR is used in (NG)EN-DC and NR-DC whereas reportCGI-RequestEUTRA is used only for NE-DC. | +| requestedBC-MRDC
Used to request configuring a band combination and corresponding feature sets which are forbidden to use by MN (i.e. outside of the allowedBC-ListMRDC ) to allow re-negotiation of the UE capabilities for SCG configuration. | +| reservedResourceConfigNRDC
Used to request or indicate the maximum number of resources reserved for the SCG. This field is only used in NR-DC. | +| requestedMaxInterFreqMeasIdSCG
Used to request the maximum number of allowed measurement identities to configure for inter-frequency measurement. This field is only used in NR-DC. | +| requestedMaxIntraFreqMeasIdSCG
Used to request the maximum number of allowed measurement identities to configure for intra-frequency measurement on each serving frequency. | +| requestedPDCCH-BlindDetectionSCG
Requested value of the reference number of cells for PDCCH blind detection allowed to be configured for the SCG. | +| requestedP-MaxEUTRA
Requested value for the maximum power for the serving cells the UE can use in E-UTRA SCG. This field is only used in NE-DC. | +| requestedP-MaxFR1
Requested value for the maximum power for the serving cells on frequency range 1 (FR1) in this secondary cell group (see TS 38.104 [12]) the UE can use in NR SCG. | +| requestedP-MaxFR2
Requested value for the maximum power for the serving cells on frequency range 2 (FR2) in this secondary cell group the UE can use in NR SCG. This field is only used in NR-DC. | +| requestedToffset
Requests the new value for the time offset restriction used by the SN for scheduling SCG transmissions (i.e. see TS 38.213 [13]). This field is used in NR-DC only when the fields nrdc-PC-mode-FR1-r16 or nrdc-PC-mode-FR2-r16 are set to dynamic. Value ms0dot5 corresponds to 0.5 ms, value ms0dot75 corresponds to 0.75 ms, value ms1 corresponds to 1ms and so on. | +| scellFrequenciesSN-EUTRA, scellFrequenciesSN-NR
Indicates the frequency of all SCells with SSB configured in SCG. The field scellFrequenciesSN-EUTRA is used in NE-DC; the field scellFrequenciesSN-NR is used in (NG)EN-DC and NR-DC. In (NG)EN-DC, the field is optionally provided to the MN. scellFrequenciesSN-NR indicates absoluteFrequencySSB . | +| scg-CellGroupConfig
Contains the RRCReconfiguration message (containing only secondaryCellGroup and/or measConfig and/or otherConfig and/or appLayerMeasConfig and/or conditionalReconfiguration and/or bap-Config and/or iab-IP-AddressConfigurationList ):
  • - to be sent to the UE, used upon SCG establishment or modification (only when the SCG is not released by the SN), as generated (entirely) by the (target) SgNB. In this case, the SN sets the RRCReconfiguration message in accordance with clause 6 e.g. regarding the "Need" or "Cond" statements.
or
  • - including the current SCG configuration of the UE, when provided in response to a query from MN, or in SN triggered SN change in order to enable delta signaling by the target SN, or in SN triggered modification procedure in order to coordinate CHO or MN-initiated CPC with SCG reconfigurations (see TS 38.423 [35]). In this case, the SN sets the RRCReconfiguration message in accordance with clause 11.2.3.
| + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

The field is absent if neither SCG (re)configuration nor SCG configuration query nor SN triggered modification procedure in order to coordinate CHO or MN-initiated CPC with SCG reconfigurations (see TS 38.423 [35]) nor SN triggered SN change is performed, e.g. at inter-node capability/configuration coordination which does not result in SCG (re)configuration towards the UE. The field is also absent upon an SCG release triggered by the SN. This field is not applicable in NE-DC.

| +|

scg-CellGroupConfigEUTRA
Includes the E-UTRA RRCConnectionReconfiguration message as specified in TS 36.331 [10]. In this version of the specification, the E-UTRA RRC message can only include the field scg-Configuration:

  • - to be sent to the UE, used to (re-)configure the SCG configuration upon SCG establishment or modification (only when the SCG is not released by the SN), as generated (entirely) by the (target) SeNB. In this case, the SN sets the scg-Configuration within the EUTRA RRCConnectionReconfiguration message in accordance with clause 6 in TS 36.331 [10] e.g. regarding the "Need" or "Cond" statements.

or

  • - including the current SCG configuration of the UE, when provided in response to a query from MN, or in SN triggered SN change in order to enable delta signalling by the target SN.

The field is absent if neither SCG (re)configuration nor SCG configuration query nor SN triggered SN change is performed, e.g. at inter-node capability/configuration coordination which does not result in SCG (re)configuration towards the UE. The field is also absent upon an SCG release triggered by the SN. This field is only used in NE-DC.

| +|

scg-RB-Config
Contains the IE RadioBearerConfig:

  • - to be sent to the UE, used to (re-)configure the SCG RB configuration upon SCG establishment or modification, as generated (entirely) by the (target) SgNB or SeNB. In this case, the SN sets the RadioBearerConfig in accordance with clause 6, e.g. regarding the "Need" or "Cond" statements.

or

  • - including the current SCG RB configuration of the UE, when provided in response to a query from MN or in SN triggered SN change or in SN triggered SN release or bearer type change between SN terminated bearer to MN terminated bearer in order to enable delta signaling by the MN or target SN. In this case, the SN sets the RadioBearerConfig in accordance with clause 11.2.3.

The field is absent if neither SCG (re)configuration nor SCG configuration query nor SN triggered SN change nor SN triggered SN release is performed, e.g. at inter-node capability/configuration coordination which does not result in SCG RB (re)configuration.

| +|

scpac-ReferenceConfigurationSCG
Includes the reference configuration associated with the SCG for the candidate supporting subsequent CPAC.

| +|

selectedBandCombination
Indicates the band combination selected by SN in (NG)EN-DC, NE-DC, and NR-DC. The SN should inform the MN with this field whenever the band combination and/or feature set it selected for the SCG changes (i.e. even if the new selection concerns a band combination and/or feature set that is allowed by the allowedBC-ListMRDC)

| +|

selectedToffset
Indicates the value used by the SN for scheduling SCG transmissions (i.e. see TS 38.213 [13]). This field is used in NR-DC only when the fields nrdc-PC-mode-FR1-r16 or nrdc-PC-mode-FR2-r16 are set to dynamic. The SN can only indicate a value that is less than or equal to maxToffset received from MN. This field is used in NR-DC only when MN has included the field maxToffset in CG-ConfigInfo. Value ms0dot5 corresponds to 0.5 ms, value ms0dot75 corresponds to 0.75 ms, value ms1 corresponds to 1ms and so on.

| +|

servCellInfoListSCG-EUTRA
Indicates the carrier frequency and the transmission bandwidth of the serving cell(s) in the SCG in intra-band NE-DC. The field is needed when MN and SN operate serving cells in the same band for either contiguous or non-contiguous intra-band band combination or LTE NR inter-band band combinations where the frequency range of the E-UTRA band is a subset of the frequency range of the NR band (as specified in Table 5.5B.4.1-1 of TS 38.101-3 [34]) in NE-DC.

| +|

servCellInfoListSCG-NR

| + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Indicates the frequency band indicator, carrier center frequency, UE specific channel bandwidth and SCS of the serving cell(s) in the SCG in intra-band (NG)EN-DC. The field is needed when MN and SN operate serving cells in the same band for either contiguous or non-contiguous intra-band band combination or LTE NR inter-band band combinations where the frequency range of the E-UTRA band is a subset of the frequency range of the NR band (as specified in Table 5.5B.4.1-1 of TS 38.101-3 [34]) in (NG)EN-DC. | +| twoPHRModeSCG
Indicates if the power headroom for SCG shall be reported as two PHRs (each PHR associated with a SRS resource set) is enabled or not. | +| twoSRS-PUSCH-Repetition
Indicates whether the indicated serving cell is configured for PUSCH repetition corresponding to two SRS resource sets configured in either srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 with usage 'codebook' or 'noncodebook'. | +| transmissionBandwidth-EUTRA
Indicates the transmission bandwidth on an E-UTRA carrier frequency as defined by the parameter Transmission Bandwidth Configuration "NRB" TS 36.104 [33]. The values rb6, rb15, rb25, rb50, rb75, rb100 indicate 6, 15, 25, 50, 75 and 100 resource blocks respectively. | +| ueAssistanceInformationSCG
Includes for each UE assistance feature associated with the SCG, the information last reported by the UE in the NR UEAssistanceInformation message for the SCG, if any. | + +| BandCombinationInfoSN field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| bandCombinationIndex
In case of NR-DC, this field indicates the position of a band combination in the supportedBandCombinationList . In case of NE-DC, this field indicates the position of a band combination in the supportedBandCombinationList and/or supportedBandCombinationListNEDC-Only . In case of (NG)EN-DC, this field indicates the position of a band combination in the supportedBandCombinationList and/or supportedBandCombinationList-UplinkTxSwitch . Band combination entries in supportedBandCombinationList are referred by an index which corresponds to the position of a band combination in the supportedBandCombinationList . Band combination entries in supportedBandCombinationListNEDC-Only are referred by an index which corresponds to the position of a band combination in the supportedBandCombinationListNEDC-Only increased by the number of entries in supportedBandCombinationList . Band combination entries in supportedBandCombinationList-UplinkTxSwitch are referred by an index which corresponds to the position of a band combination in the supportedBandCombinationList-UplinkTxSwitch increased by the number of entries in supportedBandCombinationList . | +| requestedFeatureSets
The position in the FeatureSetCombination which identifies one FeatureSetUplink/Downlink for each band entry in the associated band combination | + +| Conditional Presence | Explanation | +|-----------------------------|---------------------------------------------------------------------------------------------------------------------------| +| FDD | This field is mandatory present if dl-FreqInfo-NR is included and concerns an FDD carrier; otherwise the field is absent. | + +#### — **CG-ConfigInfo** + +This message is used by master eNB or gNB to request the SgNB or SeNB to perform certain actions e.g. to establish, modify or release an SCG. The message may include additional information e.g. to assist the SgNB or SeNB to set the SCG configuration. It can also be used by a CU to request a DU to perform certain actions, e.g. to establish, or modify an MCG or SCG. + +Direction: Master eNB or gNB to secondary gNB or eNB, alternatively CU to DU. + +#### **CG-ConfigInfo message** + +-- ASN1START + +-- TAG-CG-CONFIG-INFO-START + +``` +CG-ConfigInfo ::= SEQUENCE { + criticalExtensions CHOICE { + c1 CHOICE { + cg-ConfigInfo CG-ConfigInfo-IEs, + spare3 NULL, spare2 NULL, spare1 NULL + }, + criticalExtensionsFuture SEQUENCE {} + } +} + +CG-ConfigInfo-IEs ::= SEQUENCE { + ue-CapabilityInfo OCTET STRING (CONTAINING UE-CapabilityRAT-ContainerList) OPTIONAL,-- Cond SN-AddMod + candidateCellInfoListMN MeasResultList2NR OPTIONAL, + candidateCellInfoListSN OCTET STRING (CONTAINING MeasResultList2NR) OPTIONAL, + measResultCellListSFTD-NR MeasResultCellListSFTD-NR OPTIONAL, + scgFailureInfo SEQUENCE { + failureType ENUMERATED { t310-Expiry, randomAccessProblem, + rlc-MaxNumRetx, synchReconfigFailure-SCG, + scg-reconfigFailure, + srb3-IntegrityFailure }, + measResultSCG OCTET STRING (CONTAINING MeasResultSCG-Failure) + } OPTIONAL, + configRestrictInfo ConfigRestrictInfoSCG OPTIONAL, + drx-InfoMCG DRX-Info OPTIONAL, + measConfigMN MeasConfigMN OPTIONAL, + sourceConfigSCG OCTET STRING (CONTAINING RRCReconfiguration) OPTIONAL, + scg-RB-Config OCTET STRING (CONTAINING RadioBearerConfig) OPTIONAL, + mcg-RB-Config OCTET STRING (CONTAINING RadioBearerConfig) OPTIONAL, + mrdc-AssistanceInfo MRDC-AssistanceInfo OPTIONAL, + nonCriticalExtension CG-ConfigInfo-v1540-IEs OPTIONAL +} + +CG-ConfigInfo-v1540-IEs ::= SEQUENCE { + ph-InfoMCG PH-TypeListMCG OPTIONAL, + measResultReportCGI SEQUENCE { + ssbFrequency ARFCN-ValueNR, + cellForWhichToReportCGI PhysCellId, + cgi-Info CGI-InfoNR + } OPTIONAL, + nonCriticalExtension CG-ConfigInfo-v1560-IEs OPTIONAL +} + +CG-ConfigInfo-v1560-IEs ::= SEQUENCE { + candidateCellInfoListMN-EUTRA OCTET STRING OPTIONAL, + candidateCellInfoListSN-EUTRA OCTET STRING OPTIONAL, + sourceConfigSCG-EUTRA OCTET STRING OPTIONAL, + scgFailureInfoEUTRA SEQUENCE { + failureTypeEUTRA ENUMERATED { t313-Expiry, randomAccessProblem, + rlc-MaxNumRetx, scg-ChangeFailure }, + measResultSCG-EUTRA OCTET STRING + } OPTIONAL, +``` + +``` + +drx-ConfigMCG DRX-Config OPTIONAL, +measResultReportCGI-EUTRA SEQUENCE { + eutraFrequency ARFCN-ValueEUTRA, + cellForWhichToReportCGI-EUTRA EUTRA-PhysCellId, + cgi-InfoEUTRA CGI-InfoEUTRA +} +measResultCellListSFTD-EUTRA MeasResultCellListSFTD-EUTRA OPTIONAL, +fr-InfoListMCG FR-InfoList OPTIONAL, +nonCriticalExtension CG-ConfigInfo-v1570-IEs OPTIONAL +} + +CG-ConfigInfo-v1570-IEs ::= SEQUENCE { + sftdFrequencyList-NR SFTD-FrequencyList-NR OPTIONAL, + sftdFrequencyList-EUTRA SFTD-FrequencyList-EUTRA OPTIONAL, + nonCriticalExtension CG-ConfigInfo-v1590-IEs OPTIONAL +} + +CG-ConfigInfo-v1590-IEs ::= SEQUENCE { + servFrequenciesMN-NR SEQUENCE (SIZE (1.. maxNrofServingCells-1)) OF ARFCN-ValueNR OPTIONAL, + nonCriticalExtension CG-ConfigInfo-v1610-IEs OPTIONAL +} + +CG-ConfigInfo-v1610-IEs ::= SEQUENCE { + drx-InfoMCG2 DRX-Info2 OPTIONAL, + alignedDRX-Indication ENUMERATED {true} OPTIONAL, + scgFailureInfo-r16 SEQUENCE { + failureType-r16 ENUMERATED { scg-lbtFailure-r16, beamFailureRecoveryFailure-r16, + t312-Expiry-r16, bh-RLF-r16, + beamFailure-r17, spare3, spare2, spare1}, + measResultSCG-r16 OCTET STRING (CONTAINING MeasResultSCG-Failure) + } + dummy1 SEQUENCE { OPTIONAL, + failureTypeEUTRA-r16 ENUMERATED { scg-lbtFailure-r16, beamFailureRecoveryFailure-r16, + t312-Expiry-r16, spare5, + spare4, spare3, spare2, spare1}, + measResultSCG-EUTRA-r16 OCTET STRING + } + sidelinkUEInformationNR-r16 OCTET STRING (CONTAINING SidelinkUEInformationNR-r16) OPTIONAL, + sidelinkUEInformationEUTRA-r16 OCTET STRING OPTIONAL, + nonCriticalExtension CG-ConfigInfo-v1620-IEs OPTIONAL +} + +CG-ConfigInfo-v1620-IEs ::= SEQUENCE { + ueAssistanceInformationSourceSCG-r16 OCTET STRING (CONTAINING UEAssistanceInformation) OPTIONAL, + nonCriticalExtension CG-ConfigInfo-v1640-IEs OPTIONAL +} + +CG-ConfigInfo-v1640-IEs ::= SEQUENCE { + servCellInfoListMCG-NR-r16 ServCellInfoListMCG-NR-r16 OPTIONAL, + servCellInfoListMCG-EUTRA-r16 ServCellInfoListMCG-EUTRA-r16 OPTIONAL, + nonCriticalExtension CG-ConfigInfo-v1700-IEs OPTIONAL +} + +``` + +``` + +CG-ConfigInfo-v1700-IEs ::= SEQUENCE { + candidateCellListCPC-r17 CandidateCellListCPC-r17 OPTIONAL, + twoPHRModeMCG-r17 ENUMERATED {enabled} OPTIONAL, + lowMobilityEvaluationConnectedInPCell-r17 ENUMERATED {enabled} OPTIONAL, + nonCriticalExtension CG-ConfigInfo-v1730-IEs OPTIONAL +} + +CG-ConfigInfo-v1730-IEs ::= SEQUENCE { + fr1-Carriers-MCG-r17 INTEGER (1..32) OPTIONAL, + fr2-Carriers-MCG-r17 INTEGER (1..32) OPTIONAL, + nonCriticalExtension CG-ConfigInfo-v1800-IEs OPTIONAL +} + +CG-ConfigInfo-v1800-IEs ::= SEQUENCE { + musim-GapConfigInfo-r18 MUSIM-GapConfig-r17 OPTIONAL, + musim-CapRestrictionInfo-r18 SEQUENCE { + musim-CapRestriction-r18 MUSIM-CapRestriction-r18 OPTIONAL, + musim-CandidateBandList-r18 MUSIM-CandidateBandList-r18 OPTIONAL + } OPTIONAL, + scpac-ReferenceConfiguration-r18 ReferenceConfiguration-r18 OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +-- Editor Note: FFS whether all fields in musim-CapRestriction should be sent to SN. + +ServCellInfoListMCG-NR-r16 ::= SEQUENCE (SIZE (1.. maxNrofServingCells)) OF ServCellInfoXCG-NR-r16 +ServCellInfoListMCG-EUTRA-r16 ::= SEQUENCE (SIZE (1.. maxNrofServingCellsEUTRA)) OF ServCellInfoXCG-EUTRA-r16 +SFTD-FrequencyList-NR ::= SEQUENCE (SIZE (1..maxCellSFTD)) OF ARFCN-ValueNR +SFTD-FrequencyList-EUTRA ::= SEQUENCE (SIZE (1..maxCellSFTD)) OF ARFCN-ValueEUTRA + +ConfigRestrictInfoSCG ::= SEQUENCE { + allowedBC-ListMRDC BandCombinationInfoList OPTIONAL, + powerCoordination-FR1 SEQUENCE { + p-maxNR-FR1 P-Max OPTIONAL, + p-maxEUTRA P-Max OPTIONAL, + p-maxUE-FR1 P-Max OPTIONAL + } OPTIONAL, + servCellIndexRangeSCG SEQUENCE { + lowBound ServCellIndex, + upBound ServCellIndex + } OPTIONAL, -- Cond SN-AddMod + maxMeasFreqsSCG INTEGER(1..maxMeasFreqsMN) OPTIONAL, + dummy INTEGER(1..maxMeasIdentitiesMN) OPTIONAL, + ... + [[ + selectedBandEntriesMNList SEQUENCE (SIZE (1..maxBandComb)) OF SelectedBandEntriesMN OPTIONAL, + pdcch-BlindDetectionSCG INTEGER (1..15) OPTIONAL, + maxNumberROHC-ContextSessionsSN INTEGER (0.. 16384) OPTIONAL + ]], + [[ + +``` + +``` + +maxIntraFreqMeasIdentitiesSCG INTEGER(1..maxMeasIdentitiesMN) OPTIONAL, +maxInterFreqMeasIdentitiesSCG INTEGER(1..maxMeasIdentitiesMN) OPTIONAL +]], +[[ +p-maxNR-FR1-MCG-r16 P-Max OPTIONAL, +powerCoordination-FR2-r16 SEQUENCE { + p-maxNR-FR2-MCG-r16 P-Max OPTIONAL, + p-maxNR-FR2-SCG-r16 P-Max OPTIONAL, + p-maxUE-FR2-r16 P-Max OPTIONAL +} OPTIONAL, +nrdc-PC-mode-FR1-r16 ENUMERATED {semi-static-mode1, semi-static-mode2, dynamic} OPTIONAL, +nrdc-PC-mode-FR2-r16 ENUMERATED {semi-static-mode1, semi-static-mode2, dynamic} OPTIONAL, +maxMeasSRS-ResourcesSCG-r16 INTEGER(0..maxNrofCLI-SRS-Resources-r16) OPTIONAL, +maxMeasCLI-ResourcesSCG-r16 INTEGER(0..maxNrofCLI-RSSI-Resources-r16) OPTIONAL, +maxNumberEHC-ContextsSN-r16 INTEGER(0..65536) OPTIONAL, +allowedReducedConfigForOverheating-r16 OverheatingAssistance OPTIONAL, +maxToffset-r16 T-Offset-r16 OPTIONAL +]], +[[ +allowedReducedConfigForOverheating-r17 OverheatingAssistance-r17 OPTIONAL, +maxNumberUDC-DRB-r17 INTEGER(0..2) OPTIONAL, +maxNumberCPCCandidates-r17 INTEGER(0..maxNrofCondCells-1-r17) OPTIONAL +]], +[[ +allowedResourceConfigNRDC-r17 ResourceConfigNRDC-r17 OPTIONAL +]] +} + +SelectedBandEntriesMN ::= SEQUENCE (SIZE (1..maxSimultaneousBands)) OF BandEntryIndex + +BandEntryIndex ::= INTEGER (0.. maxNrofServingCells) + +PH-TypeListMCG ::= SEQUENCE (SIZE (1..maxNrofServingCells)) OF PH-InfoMCG + +PH-InfoMCG ::= SEQUENCE { + servCellIndex ServCellIndex, + ph-Uplink PH-UplinkCarrierMCG, + ph-SupplementaryUplink PH-UplinkCarrierMCG OPTIONAL, + ..., + [[ + twoSRS-PUSCH-Repetition-r17 ENUMERATED {enabled} OPTIONAL + ]] +} + +PH-UplinkCarrierMCG ::= SEQUENCE { + ph-Type1or3 ENUMERATED {type1, type3}, + ... +} + +BandCombinationInfoList ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombinationInfo + +BandCombinationInfo ::= SEQUENCE { + bandCombinationIndex BandCombinationIndex, + +``` + +``` + + allowedFeatureSetsList SEQUENCE (SIZE (1..maxFeatureSetsPerBand)) OF FeatureSetEntryIndex +} + +FeatureSetEntryIndex ::= INTEGER (1.. maxFeatureSetsPerBand) + +DRX-Info ::= SEQUENCE { + drx-LongCycleStartOffset CHOICE { + ms10 INTEGER(0..9), + ms20 INTEGER(0..19), + ms32 INTEGER(0..31), + ms40 INTEGER(0..39), + ms60 INTEGER(0..59), + ms64 INTEGER(0..63), + ms70 INTEGER(0..69), + ms80 INTEGER(0..79), + ms128 INTEGER(0..127), + ms160 INTEGER(0..159), + ms256 INTEGER(0..255), + ms320 INTEGER(0..319), + ms512 INTEGER(0..511), + ms640 INTEGER(0..639), + ms1024 INTEGER(0..1023), + ms1280 INTEGER(0..1279), + ms2048 INTEGER(0..2047), + ms2560 INTEGER(0..2559), + ms5120 INTEGER(0..5119), + ms10240 INTEGER(0..10239) + }, + shortDRX SEQUENCE { + drx-ShortCycle ENUMERATED { + ms2, ms3, ms4, ms5, ms6, ms7, ms8, ms10, ms14, ms16, ms20, ms30, ms32, + ms35, ms40, ms64, ms80, ms128, ms160, ms256, ms320, ms512, ms640, spare9, + spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 }, + drx-ShortCycleTimer INTEGER (1..16) + } OPTIONAL +} + +DRX-Info2 ::= SEQUENCE { + drx-onDurationTimer CHOICE { + subMilliSeconds INTEGER (1..31), + milliSeconds ENUMERATED { + ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, + ms80, ms100, ms200, ms300, ms400, ms500, ms600, ms800, ms1000, ms1200, + ms1600, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 } + } +} + +MeasConfigMN ::= SEQUENCE { + measuredFrequenciesMN SEQUENCE (SIZE (1..maxMeasFreqsMN)) OF NR-FreqInfo OPTIONAL, + measGapConfig SetupRelease { GapConfig } OPTIONAL, + gapPurpose ENUMERATED {perUE, perFR1} OPTIONAL, + ..., + [[ + +``` + +``` + +measGapConfigFR2 SetupRelease { GapConfig } OPTIONAL +]], +[[ +interFreqNoGap-r16 ENUMERATED {true} OPTIONAL +]] +} + +MRDC-AssistanceInfo ::= SEQUENCE { + affectedCarrierFreqCombInfoListMRDC SEQUENCE (SIZE (1..maxNrofCombIDC)) OF AffectedCarrierFreqCombInfoMRDC, + ..., + [[ + overheatingAssistanceSCG-r16 OCTET STRING (CONTAINING OverheatingAssistance) OPTIONAL + ]], + [[ + overheatingAssistanceSCG-FR2-2-r17 OCTET STRING (CONTAINING OverheatingAssistance-r17) OPTIONAL + ]], + [[ + affectedCarrierFreqRangeCombList-r18 AffectedCarrierFreqRangeCombList-r18 OPTIONAL, + affectedCarrierFreqCombList-r16 AffectedCarrierFreqCombList-r16 OPTIONAL, + idc-TDM-Assistance-r18 IDC-TDM-Assistance-r18 OPTIONAL + ]] +} + +AffectedCarrierFreqCombInfoMRDC ::= SEQUENCE { + victimSystemType VictimSystemType, + interferenceDirectionMRDC ENUMERATED {eutra-nr, nr, other, ultra-nr-other, nr-other, spare3, spare2, spare1}, + affectedCarrierFreqCombMRDC SEQUENCE { + affectedCarrierFreqCombEUTRA AffectedCarrierFreqCombEUTRA OPTIONAL, + affectedCarrierFreqCombNR AffectedCarrierFreqCombNR OPTIONAL + } +} + +VictimSystemType ::= SEQUENCE { + gps ENUMERATED {true} OPTIONAL, + glonass ENUMERATED {true} OPTIONAL, + bds ENUMERATED {true} OPTIONAL, + galileo ENUMERATED {true} OPTIONAL, + wlan ENUMERATED {true} OPTIONAL, + bluetooth ENUMERATED {true} OPTIONAL +} + +AffectedCarrierFreqCombEUTRA ::= SEQUENCE (SIZE (1..maxNrofServingCellsEUTRA)) OF ARFCN-ValueEUTRA + +AffectedCarrierFreqCombNR ::= SEQUENCE (SIZE (1..maxNrofServingCells)) OF ARFCN-ValueNR + +CandidateCellListCPC-r17 ::= SEQUENCE (SIZE (1..maxFreq)) OF CandidateCellCPC-r17 + +CandidateCellCPC-r17 ::= SEQUENCE { + ssbFrequency-r17 ARFCN-ValueNR, + candidateCellList-r17 SEQUENCE (SIZE (1..maxNrofCondCells-r16)) OF PhysCellId +} + +``` + +-- TAG-CG-CONFIG-INFO-STOP + +-- ASN1STOP + +| CG-ConfigInfo field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| affectedCarrierFreqCombList
This field is signalled upon MN not addressing IDC issue and contains the list of NR carrier frequency combinations reported by UE to MN for IDC problem caused by the NR-DC frequency combination. | +| affectedCarrierFreqRangeCombList
This field is signalled upon MN not addressing IDC issue and contains the list of NR carrier frequency range combinations reported by UE to MN for IDC problem caused by the NR-DC frequency combination. | +| alignedDRX-Indication
This field is signalled upon MN triggered CGI reporting by the UE that requires aligned DRX configurations between the MCG and the SCG (i.e. same DRX cycle and on-duration configured by MN completely contains on-duration configured by SN). | +| allowedBC-ListMRDC
A list of indices referring to band combinations in MR-DC capabilities from which SN is allowed to select the SCG band combination. Each entry refers to:
- a band combination numbered according to supportedBandCombinationList and supportedBandCombinationList-UplinkTxSwitch in the UE-MRDC-Capability (in case of (NG)EN-DC), or according to supportedBandCombinationList and supportedBandCombinationListNEDC-Only in the UE-MRDC-Capability (in case of NE-DC), or according to supportedBandCombinationList in the UE-NR-Capability (in case of NR-DC),
- and the Feature Sets allowed for each band entry. All MR-DC band combinations indicated by this field comprise the MCG band combination, which is a superset of the MCG band(s) selected by MN. | +| allowedReducedConfigForOverheating
Indicates the reduced configuration that the SCG is allowed to configure.
reducedMaxCCs in allowedReducedConfigForOverheating indicates the maximum number of downlink/uplink PSCell/SCells that the SCG is allowed to configure. This field is used in (NG)EN-DC and NR-DC.
reducedMaxBW-FR1 and reducedMaxBW-FR2 in allowedReducedConfigForOverheating indicates the maximum aggregated bandwidth across all downlink/uplink carriers of FR1 and FR2-1, respectively that the SCG is allowed to configure. reducedMaxBW-FR2-2 in allowedReducedConfigForOverheating-r17 indicates the maximum aggregated bandwidth across all downlink/uplink carriers of FR2-2 that the SCG is allowed to configure. This field is only used in NR-DC.
reducedMaxMIMO-LayersFR1 and reducedMaxMIMO-LayersFR2 in allowedReducedConfigForOverheating indicates the maximum number of downlink/uplink MIMO layers of each serving cell operating on FR1 and FR2-1, respectively that the SCG is allowed to configure. reducedMaxMIMO-LayersFR2-2 in allowedReducedConfigForOverheating-r17 indicates the maximum number of downlink/uplink MIMO layers of each serving cell operating on FR2-2 that the SCG is allowed to configure. This field is only used in NR-DC. | +| allowedResourceConfigNRDC
Used to indicate the maximum number of resources reserved for the SCG. This field is only used in NR-DC. | +| candidateCellInfoListMN, candidateCellInfoListSN
Contains information regarding cells that the master node or the source node suggests the target gNB or DU to consider configuring. In case of MN initiated CPA, CPC or CHO with candidate SCG(s), the field candidateCellInfoListMN contains information regarding cells that the MN suggests the candidate target secondary node to consider configuring for MN initiated CPA, CPC, CHO with candidate SCG(s), or subsequent CPAC.
For (NG)EN-DC, including CSI-RS measurement results in candidateCellInfoListMN is not supported in this version of the specification. For NR-DC, including SSB and/or CSI-RS measurement results in candidateCellInfoListMN is supported. | +| candidateCellInfoListMN-EUTRA, candidateCellInfoListSN-EUTRA
Includes the MeasResultList3EUTRA as specified in TS 36.331 [10]. Contains information regarding cells that the master node or the source node suggests the target secondary eNB to consider configuring. These fields are only used in NE-DC. | +| candidateCellListCPC
Contains information regarding cells that the source secondary node suggests the candidate target secondary node to consider configuring for SN initiated Conditional PSCell Change (CPC) or SN initiated inter-SN subsequent CPAC. | +| configRestrictInfo
Includes fields for which SgNB is explicitly indicated to observe a configuration restriction. | +| drx-ConfigMCG | + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| This field contains the complete DRX configuration of the MCG. This field is only used in NR-DC. | +| drx-InfoMCG
This field contains the DRX long and short cycle configuration of the MCG. This field is used in (NG)EN-DC and NE-DC. | +| drx-InfoMCG2
This field contains the drx-onDurationTimer configuration of the MCG. This field is only used in (NG)EN-DC. | +| dummy, dummy1
These fields are not used in the specification and SN ignores the received value(s). | +| fr-InfoListMCG
Contains information of FR information of serving cells that include PCell and SCell(s) configured in MCG. | +| fr1-Carriers-MCG, fr2-Carriers-MCG
Indicates the number of FR1 or FR2 serving cells configured in MCG. | +| idc-TDM-Assistance
This field is signalled upon MN not addressing IDC issue and contains IDC TDM assistance information reported by UE to MN for IDC problem. | +| interFreqNoGap
Indicates that the field interFrequencyConfig-NoGap-r16 has been included within the MeasConfig IE generated by the MN. | +| lowMobilityEvaluationConnectedInPCell
Indicates if low mobility criterion has been configured in NR PCell. | +| maxInterFreqMeasIdentitiesSCG
Indicates the maximum number of allowed measurement identities that the SCG is allowed to configure for inter-frequency measurement. The maximum value for this field is 10. If the field is absent, the SCG is allowed to configure inter-frequency measurements up to the maximum value. This field is only used in NR-DC. | +| maxIntraFreqMeasIdentitiesSCG
Indicates the maximum number of allowed measurement identities that the SCG is allowed to configure for intra-frequency measurement on each serving frequency. The maximum value for this field is 9 (in case of (NG)EN-DC or NR-DC) or 10 (in case of NE-DC). If the field is absent, the SCG is allowed to configure intra-frequency measurements up to the maximum value on each serving frequency. | +| maxMeasCLI-ResourceSCG
Indicates the maximum number of CLI RSSI resources that the SCG is allowed to configure. | +| maxMeasFreqsSCG
Indicates the maximum number of NR inter-frequency carriers the SN is allowed to configure with PSCell for measurements. | +| maxMeasSRS-ResourceSCG
Indicates the maximum number of SRS resources that the SCG is allowed to configure for CLI measurement. | +| maxNumberCPCCandidates
Indicates the maximum numbers of conditional reconfigurations the SN is allowed to configure for SN initiated CPC. Value 0 indicates that the SN is not allowed to configure SN initiated CPC. If the field is absent, the SN is allowed to configure up to maxNrofCondCells-r16 conditional reconfigurations for SN-initiated CPC. | +| maxNumberROHC-ContextSessionsSN
Indicates the maximum number of ROHC context sessions allowed to SN terminated bearer, excluding context sessions that leave all headers uncompressed. | +| maxNumberEHC-ContextsSN
Indicates the maximum number of EHC contexts allowed to the SN terminated bearer. The field indicates the number of contexts in addition to CID = "all zeros", as specified in TS 38.323 [5]. | +| maxNumberUDC-DRB
Indicates the maximum number of UDC DRBs allowed to SN terminated bearer. This field is used in NGEN-DC, NR-DC and NE-DC. | +| maxToffset
Indicates the maximum Toffset value the SN is allowed to use for scheduling SCG transmissions (see TS 38.213 [13]). This field is used in NR-DC only when the fields nrdc-PC-mode-FR1-r16 or nrdc-PC-mode-FR2-r16 are set to dynamic. Value ms0dot5 corresponds to 0.5 ms, value ms0dot75 corresponds to 0.75 ms, value ms1 corresponds to 1 ms and so on. | +| measuredFrequenciesMN | + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Used by MN to indicate a list of frequencies measured by the UE. | +| measGapConfig
Indicates the FR1 and perUE measurement gap configuration configured by MN. | +| measGapConfigFR2
Indicates the FR2 measurement gap configuration configured by MN. | +| mcg-RB-Config
Contains all of the fields in the IE RadioBearerConfig used in MN, used by the SN to support delta configuration to UE (i.e. when MN does not use full configuration option), for bearer type change between MN terminated bearer with NR PDCP to SN terminated bearer. It is also used to indicate the PDCP duplication related information for MN terminated split bearer (whether duplication is configured and if so, whether it is initially activated) in SN Addition/Modification procedure. Otherwise, this field is absent. | +| measResultReportCGI, measResultReportCGI-EUTRA
Used by MN to provide SN with CGI-Info for the cell as per SN's request. In this version of the specification, the measResultReportCGI is used for (NG)EN-DC and NR-DC and the measResultReportCGI-EUTRA is used only for NE-DC. | +| measResultSCG-EUTRA
This field includes the MeasResultSCG-FailureMRDC IE as specified in TS 36.331 [10]. This field is only used in NE-DC. | +| measResultSFTD-EUTRA
SFTD measurement results between the PCell and the E-UTRA PScell in NE-DC. This field is only used in NE-DC. | +| mrdc-AssistanceInfo
Contains the IDC assistance information for MR-DC reported by the UE (see TS 36.331 [10]). | +| musim-CapRestrictionInfo
Indicates the UE's preference on SCell(s) to be released, band(s) or combination(s) of bands with restricted capability, or band(s) or band combination(s) to be avoided for UE temporary capabilities restriction purpose with the musim-candidateBandList-r18 only for musim-AffectedBandsList-r18 and musim-AvoidedBandsList -r18 . | +| musim-GapConfigInfo
Indicates the MUSIM gap configuration configured by MN. | +| nrdc-PC-mode-FR1
Indicates the uplink power sharing mode that the UE uses in NR-DC FR1 (see TS 38.213 [13], clause 7.6). | +| nrdc-PC-mode-FR2
Indicates the uplink power sharing mode that the UE uses in NR-DC FR2 (see TS 38.213 [13], clause 7.6). | +| overheatingAssistanceSCG
Contains the UE's preference on reduced configuration for NR SCG to address overheating. This field is only used in (NG)EN-DC. | +| overheatingAssistanceSCG-FR2-2
Contains the UE's preference on reduced configuration for NR SCG on FR2-2 to address overheating. This field is only used in (NG)EN-DC. | +| p-maxEUTRA
Indicates the maximum total transmit power to be used by the UE in the E-UTRA cell group (see TS 36.104 [33]). This field is used in (NG)EN-DC and NE-DC. | +| p-maxNR-FR1
For (NG)EN-DC and NE-DC, the field indicates the maximum total transmit power to be used by the UE in the NR cell group across all serving cells in frequency range 1 (FR1) (see TS 38.104 [12]). For NR-DC, it indicates the maximum total transmit power to be used by the UE in the NR cell group across all serving cells in frequency range 1 (FR1) (see TS 38.104 [12]) the UE can use in NR SCG. | +| p-maxUE-FR1
Indicates the maximum total transmit power to be used by the UE across all serving cells in frequency range 1 (FR1). | +| p-maxNR-FR1-MCG
Indicates the maximum total transmit power to be used by the UE in the NR cell group across all serving cells in frequency range 1 (FR1) (see TS 38.104 [12]) the UE can use in NR MCG. This field is only used in NR-DC. | +| p-maxNR-FR2-SCG
Indicates the maximum total transmit power to be used by the UE in the NR cell group across all serving cells in frequency range 2 (FR2) (see TS 38.104 [12]) the UE can use in NR SCG. | + +| | | +|-------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| p-maxUE-FR2 | Indicates the maximum total transmit power to be used by the UE across all serving cells in frequency range 2 (FR2). | +| p-maxNR-FR2-MCG | Indicates the maximum total transmit power to be used by the UE in the NR cell group across all serving cells in frequency range 2 (FR2) (see TS 38.104 [12]) the UE can use in NR MCG. | +| pdcch-BlindDetectionSCG | Indicates the maximum value of the reference number of cells for PDCCH blind detection allowed to be configured for the SCG. | +| ph-InfoMCG | Power headroom information in MCG that is needed in the reception of PHR MAC CE in SCG. | +| ph-SupplementaryUplink | Power headroom information for supplementary uplink. For UE in (NG)EN-DC, this field is absent. | +| ph-Type1or3 | Type of power headroom for a serving cell in MCG (PCell and activated SCells). type1 refers to type 1 power headroom, type3 refers to type 3 power headroom. (See TS 38.321 [3]). | +| ph-Uplink | Power headroom information for uplink. | +| powerCoordination-FR1 | Indicates the maximum power that the UE can use in FR1. | +| powerCoordination-FR2 | Indicates the maximum power that the UE can use in frequency range 2 (FR2). This field is only used in NR-DC. | +| scgFailureInfo | Contains SCG failure type and measurement results. In case the sender has no measurement results available, the sender may include one empty entry (i.e. without any optional fields present) in measResultPerMOList . This field is used in (NG)EN-DC and NR-DC. | +| scg-RB-Config | Contains all of the fields in the IE RadioBearerConfig used in SN, used to allow the target SN to use delta configuration to the UE, e.g. during SN change. The field is signalled upon change of SN unless MN uses full configuration option. Otherwise, the field is absent. | +| scpac-ReferenceConfiguration | Includes the reference configuration associated with the SCG for the candidate supporting subsequent CPAC. | +| selectedBandEntriesMNList | A list of indices referring to the position of a band entry selected by the MN, in each band combination entry in allowedBC-ListMRDC IE. BandEntryIndex 0 identifies the first band in the bandList of the BandCombination , BandEntryIndex 1 identifies the second band in the bandList of the BandCombination , and so on. This selectedBandEntriesMNList includes the same number of entries, and listed in the same order as in allowedBC-ListMRDC . The SN uses this information to determine which bands out of the NR band combinations in allowedBC-ListMRDC it can configure in SCG in NR-DC. The SN can use this information to determine for which band pair(s) it should check SimultaneousRxBTxPerBandPair . | +| servCellIndexRangeSCG | Range of serving cell indices that SN is allowed to configure for SCG serving cells. | +| servCellInfoListMCG-EUTRA | Indicates the carrier frequency and the transmission bandwidth of the serving cell(s) in the MCG in intra-band (NG)EN-DC. The field is needed when MN and SN operate serving cells in the same band for either contiguous or non-contiguous intra-band band combination or LTE NR inter-band band combinations where the frequency range of the E-UTRA band is a subset of the frequency range of the NR band (as specified in Table 5.5B.4.1-1 of TS 38.101-3 [34]) in (NG)EN-DC. | +| servCellInfoListMCG-NR | Indicates the frequency band indicator, carrier center frequency, UE specific channel bandwidth and SCS of the serving cell(s) in the MCG in intra-band NE-DC. The field is needed when MN and SN operate serving cells in the same band for either contiguous or non-contiguous intra-band band combination or LTE NR inter-band band combinations where the frequency range of the E-UTRA band is a subset of the frequency range of the NR band (as specified in Table 5.5B.4.1-1 of TS 38.101-3 [34]) in NE-DC. | + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| servFrequenciesMN-NR
Indicates the frequency of all serving cells that include PCell and SCell(s) with SSB configured in MCG. This field is only used in NR-DC. servFrequenciesMN-NR indicates absoluteFrequencySSB . | +| sftdFrequencyList-NR
Includes a list of SSB frequencies. Each entry identifies the SSB frequency of a PCell, which corresponds to one MeasResultCellSFTD-NR entry in the MeasResultCellListSFTD-NR . | +| sftdFrequencyList-EUTRA
Includes a list of E-UTRA frequencies. Each entry identifies the carrier frequency of a PCell, which corresponds to one MeasResultSFTD-EUTRA entry in the MeasResultCellListSFTD-EUTRA . | +| sidelinkUEInformationEUTRA
This field contains the E-UTRA SidelinkUEInformation message as specified in TS 36.331 [10]. | +| sidelinkUEInformationNR
This field contains the NR SidelinkUEInformationNR message. | +| sourceConfigSCG
Includes all of the current SCG configurations used by the target SN to build delta configuration to be sent to UE, e.g. during SN change. The field contains the RRReconfiguration message, i.e. including secondaryCellGroup and measConfig . The field is signalled upon change of SN, unless MN uses full configuration option. Otherwise, the field is absent. | +| sourceConfigSCG-EUTRA
Includes the E-UTRA RRConnectionReconfiguration message as specified in TS 36.331 [10]. In this version of the specification, the E-UTRA RRC message can only include the field scg-Configuration . In this version of the specification, this field is absent when master gNB uses full configuration option. This field is only used in NE-DC. | +| twoPHRModeMCG
Indicates if the power headroom for MCG shall be reported as two PHRs (each PHR associated with a SRS resource set) is enabled or not. | +| twoSRS-PUSCH-Repetition
Indicates whether the indicated serving cell is configured for PUSCH repetition corresponding to two SRS resource sets configured in either srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 with usage 'codebook' or 'noncodebook'. | +| ueAssistanceInformationSourceSCG
Includes for each UE assistance feature associated with the SCG, the information last reported by the UE in the NR UEAssistanceInformation message for the source SCG, if any. | +| ue-CapabilityInfo
Contains the IE UE-CapabilityRAT-ContainerList supported by the UE (see NOTE 3). A gNB that retrieves MRDC related capability containers ensures that the set of included MRDC containers is consistent w.r.t. the feature set related information. | + +| BandCombinationInfo field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| allowedFeatureSetsList
Defines a subset of the entries in a FeatureSetCombination . Each index identifies a position in the FeatureSetCombination , which corresponds to one FeatureSetUplink/Downlink for each band entry in the associated band combination. | +| bandCombinationIndex
In case of NR-DC, this field indicates the position of a band combination in the supportedBandCombinationList . In case of NE-DC, this field indicates the position of a band combination in the supportedBandCombinationList and/or supportedBandCombinationListNEDC-Only . In case of (NG)EN-DC, this field indicates the position of a band combination in the supportedBandCombinationList and/or supportedBandCombinationList-UplinkTxSwitch . Band combination entries in supportedBandCombinationList are referred by an index which corresponds to the position of a band combination in the supportedBandCombinationList . Band combination entries in supportedBandCombinationListNEDC-Only are referred by an index which corresponds to the position of a band combination in the supportedBandCombinationListNEDC-Only increased by the number of entries in supportedBandCombinationList . Band combination entries in supportedBandCombinationList-UplinkTxSwitch are referred by an index which corresponds to the position of a band combination in the supportedBandCombinationList-UplinkTxSwitch increased by the number of entries in supportedBandCombinationList . | + +| Conditional Presence | Explanation | +|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SN-AddMod | The field is mandatory present upon SN addition and SN change. It is optionally present upon SN modification and inter-MN handover without SN change. Otherwise, the field is absent. | + +NOTE 3: The following table indicates per MN RAT and SN RAT whether RAT capabilities are included or not in *ue-CapabilityInfo*. + +| MN RAT | SN RAT | NR capabilities | E-UTRA capabilities | MR-DC capabilities | +|---------------|---------------|------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------| +| E-UTRA | NR | Need not be included if the UE Radio Capability ID as specified in 23.502 [43] is used. Included otherwise | Not included | Need not be included if the UE Radio Capability ID as specified in 23.502 [43] is used. Included otherwise | +| NR | E-UTRA | Not included | Need not be included if the UE Radio Capability ID as specified in 23.502 [43] is used. Included otherwise | Need not be included if the UE Radio Capability ID as specified in 23.502 [43] is used. Included otherwise | +| NR | NR | Need not be included if the UE Radio Capability ID as specified in 23.502 [43] is used. Included otherwise | Not included | Not included | + +#### – *MeasurementTimingConfiguration* + +The *MeasurementTimingConfiguration* message is used to convey assistance information for measurement timing. + +Direction: en-gNB to eNB, eNB to en-gNB, gNB to gNB, ng-eNB to gNB, gNB to ng-eNB, ng-eNB to ng-eNB, gNB DU to gNB CU, and gNB CU to gNB DU. + +#### ***MeasurementTimingConfiguration* message** + +-- ASN1START + +-- TAG-MEASUREMENT-TIMING-CONFIGURATION-START + +``` +MeasurementTimingConfiguration ::= SEQUENCE { + criticalExtensions + CHOICE { + cl + CHOICE { + measTimingConf + MeasurementTimingConfiguration-IEs, + spare3 NULL, spare2 NULL, spare1 NULL + }, + criticalExtensionsFuture + SEQUENCE {} + } +} + +MeasurementTimingConfiguration-IEs ::= SEQUENCE { + measTiming + MeasTimingList + OPTIONAL, + nonCriticalExtension + MeasurementTimingConfiguration-v1550-IEs + OPTIONAL +} + +MeasurementTimingConfiguration-v1550-IEs ::= SEQUENCE { + campOnFirstSSB + BOOLEAN, + psCellOnlyOnFirstSSB + BOOLEAN, + nonCriticalExtension + MeasurementTimingConfiguration-v1610-IEs + OPTIONAL +} + +MeasurementTimingConfiguration-v1610-IEs ::= SEQUENCE { + csi-RS-Config-r16 + SEQUENCE { + csi-RS-SubcarrierSpacing-r16 + SubcarrierSpacing, + csi-RS-CellMobility-r16 + CSI-RS-CellMobility, + refSSBFreq-r16 + ARFCN-ValueNR + }, + nonCriticalExtension + SEQUENCE {} + OPTIONAL +} + +MeasTimingList ::= SEQUENCE (SIZE (1..maxMeasFreqsMN)) OF MeasTiming + +MeasTiming ::= SEQUENCE { + frequencyAndTiming + SEQUENCE { + carrierFreq + ARFCN-ValueNR, + ssbSubcarrierSpacing + SubcarrierSpacing, + ssb-MeasurementTimingConfiguration + SSB-MTC, + ss-RSSI-Measurement + SS-RSSI-Measurement + OPTIONAL + } + OPTIONAL, + ... + [[ + ssb-ToMeasure + SSB-ToMeasure + OPTIONAL, + physCellId + PhysCellId + OPTIONAL + ]] +} + +-- TAG-MEASUREMENT-TIMING-CONFIGURATION-STOP +-- ASN1STOP +``` + +| MeasTiming field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| carrierFreq, ssbSubcarrierSpacing
Indicates the frequency and subcarrier spacing of the SS block of the cell for which this message is included, or of other SS blocks within the same carrier. | +| ssb-MeasurementTimingConfiguration
Indicates the SMTC which can be used to search for SSB of the cell for which the message is included. When the message is included in "Served NR Cell Information" (see TS 36.423 [37]), "Served Cell Information NR" (see TS 38.423 [35]), or "Served Cell Information" (see TS 38.473 [36]), the timing is based on the cell for which the message is included. When the message is included in "NR Neighbour Information" (see TS 36.423 [37]), or "Served Cell Information" (see TS 38.423 [35]), the timing is based on the cell indicated in the "Served NR Cell Information" or "Served Cell Information NR" with which the "NR Neighbour Information" or "Neighbour Information NR" is provided. When the message is included in "CU to DU RRC Information", the timing is based on the cell indicated by SpCell ID with which the message is included. If the field is provided by an NTN cell, the offset (derived from parameter periodicityAndOffset ) is based on the assumption that the NTN payload to gNB propagation delay of the cell for which the message is included equals to 0 ms. | +| ss-RSSI-Measurement
Provides the configuration which can be used for RSSI measurements of the cell for which the message is included. | + +| MeasurementTimingConfiguration field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| campOnFirstSSB
Value true indicates that the SSB indicated in the first instance of MeasTiming in the measTiming list can be used for camping and for a PCell configuration (i.e. in spCellConfigCommon of the masterCellGroup ). | +| csi-RS-CellMobility
Indicates the CSI-RS configuration of the cell for which this message is included. The timing of the CSI-RS resources is based on the SSB indicated by refSSBFreq . | +| csi-RS-SubcarrierSpacing
Indicates the subcarrier spacing of the CSI-RS resources included in csi-rs-CellMobility . | +| measTiming
A list of SMTC information, SSB RSSI measurement information and associated NR frequency exchanged via EN-DC X2 Setup, EN-DC Configuration Update, Xn Setup and NG-RAN Node Configuration Update procedures, or F1 messages between gNB DU and gNB CU. | +| physCellId
Physical Cell Identity of the SSB on the ARFCN indicated by carrierFreq . | +| psCellOnlyOnFirstSSB
Value true indicates that only the SSB indicated in the first instance of MeasTiming in the measTiming list can be used for a PSCell configuration (i.e. in spCellConfigCommon of the secondaryCellGroup ). | +| ssb-ToMeasure
The set of SS blocks to be measured within the SMTC measurement duration (see TS 38.215 [9]). | + +#### — **UERadioPagingInformation** + +This message is used to transfer radio paging information, covering both upload to and download from the 5GC, and between gNBs. + +Direction: gNB to/ from 5GC and gNB to/from gNB + +#### **UERadioPagingInformation message** + +``` +-- ASN1START +-- TAG-UE-RADIO-PAGING-INFORMATION-START +``` + +``` + +UERadioPagingInformation ::= SEQUENCE { + criticalExtensions CHOICE { + c1 CHOICE { + ueRadioPagingInformation UERadioPagingInformation-IEs, + spare7 NULL, + spare6 NULL, spare5 NULL, spare4 NULL, + spare3 NULL, spare2 NULL, spare1 NULL + }, + criticalExtensionsFuture SEQUENCE {} + } +} + +UERadioPagingInformation-IEs ::= SEQUENCE { + supportedBandListNRForPaging SEQUENCE (SIZE (1..maxBands)) OF FreqBandIndicatorNR OPTIONAL, + nonCriticalExtension UERadioPagingInformation-v15e0-IEs OPTIONAL +} + +UERadioPagingInformation-v15e0-IEs ::= SEQUENCE { + dl-SchedulingOffset-PDSCH-TypeA-FDD-FR1 ENUMERATED {supported} OPTIONAL, + dl-SchedulingOffset-PDSCH-TypeA-TDD-FR1 ENUMERATED {supported} OPTIONAL, + dl-SchedulingOffset-PDSCH-TypeA-TDD-FR2 ENUMERATED {supported} OPTIONAL, + dl-SchedulingOffset-PDSCH-TypeB-FDD-FR1 ENUMERATED {supported} OPTIONAL, + dl-SchedulingOffset-PDSCH-TypeB-TDD-FR1 ENUMERATED {supported} OPTIONAL, + dl-SchedulingOffset-PDSCH-TypeB-TDD-FR2 ENUMERATED {supported} OPTIONAL, + nonCriticalExtension UERadioPagingInformation-v1700-IEs OPTIONAL +} + +UERadioPagingInformation-v1700-IEs ::= SEQUENCE { + ue-RadioPagingInfo-r17 OCTET STRING (CONTAINING UE-RadioPagingInfo-r17) OPTIONAL, + inactiveStatePO-Determination-r17 ENUMERATED {supported} OPTIONAL, + numberOfRxRedCap-r17 ENUMERATED {one, two} OPTIONAL, + halfDuplexFDD-TypeA-RedCap-r17 SEQUENCE (SIZE (1..maxBands)) OF FreqBandIndicatorNR OPTIONAL, + nonCriticalExtension UERadioPagingInformation-v1800-IEs OPTIONAL +} + +UERadioPagingInformation-v1800-IEs ::= SEQUENCE { + numberOfRxERedCap-r18 ENUMERATED {one, two} OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +-- TAG-UE-RADIO-PAGING-INFORMATION-STOP +-- ASN1STOP + +``` + +| UERadioPagingInformation field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| supportedBandListNRForPaging
Indicates the UE supported NR frequency bands which are derived by the gNB from UE-NR-Capability . | +| dl-SchedulingOffset-PDSCH-TypeA-FDD-FR1
Indicates whether the UE supports DL scheduling slot offset (K0) greater than 0 for PDSCH mapping type A in FDD FR1. | +| dl-SchedulingOffset-PDSCH-TypeA-TDD-FR1
Indicates whether the UE supports DL scheduling slot offset (K0) greater than 0 for PDSCH mapping type A in TDD FR1. | +| dl-SchedulingOffset-PDSCH-TypeA-TDD-FR2
Indicates whether the UE supports DL scheduling slot offset (K0) greater than 0 for PDSCH mapping type A in TDD FR2. | +| dl-SchedulingOffset-PDSCH-TypeB-FDD-FR1
Indicates whether the UE supports DL scheduling slot offset (K0) greater than 0 for PDSCH mapping type B in FDD FR1. | +| dl-SchedulingOffset-PDSCH-TypeB-TDD-FR1
Indicates whether the UE supports DL scheduling slot offset (K0) greater than 0 for PDSCH mapping type B in TDD FR1. | +| dl-SchedulingOffset-PDSCH-TypeB-TDD-FR2
Indicates whether the UE supports DL scheduling slot offset (K0) greater than 0 for PDSCH mapping type B in TDD FR2. | +| halfDuplexFDD-TypeA-RedCap
Indicates whether the (e)RedCap UE only supports half-duplex operation for FDD in the indicated band(s). | +| inactiveStatePO-Determination
Indicates whether the UE supports to use the same i_s to determine PO in RRC_INACTIVE state as in RRC_IDLE state. | +| numberOfRxERedCap
Indicates the number of Rx branches supported by an eRedCap UE. | +| numberOfRxRedCap
Indicates the number of Rx branches supported by a RedCap UE. | +| ue-RadioPagingInfo
The field is used to transfer UE capability information used for paging. The gNB generates the ue-RadioPagingInfo and the contained UE capability information is absent when not supported by the UE. | + +#### – ***UERadioAccessCapabilityInformation*** + +This message is used to transfer UE radio access capability information, covering both upload to and download from the 5GC. + +Direction: ng-eNB or gNB to/ from 5GC + +##### ***UERadioAccessCapabilityInformation message*** + +``` +-- ASN1START +-- TAG-UE-RADIO-ACCESS-CAPABILITY-INFORMATION-START + +UERadioAccessCapabilityInformation ::= SEQUENCE { + criticalExtensions CHOICE { + c1 CHOICE{ + ueRadioAccessCapabilityInformation UERadioAccessCapabilityInformation-IEs, + spare7 NULL, + spare6 NULL, spare5 NULL, spare4 NULL, + spare3 NULL, spare2 NULL, spare1 NULL + }, + }, +} +``` + +``` + + criticalExtensionsFuture SEQUENCE {} + } +} + +UERadioAccessCapabilityInformation-IEs ::= SEQUENCE { + ue-RadioAccessCapabilityInfo OCTET STRING (CONTAINING UE-CapabilityRAT-ContainerList), + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +-- TAG-UE-RADIO-ACCESS-CAPABILITY-INFORMATION-STOP +-- ASN1STOP + +``` + +##### ***UERadioAccessCapabilityInformation-IEs* field descriptions** + +##### ***ue-RadioAccessCapabilityInfo*** + +Including NR, MR-DC, E-UTRA radio access capabilities. A gNB that retrieves MRDC related capability containers ensures that the set of included MRDC containers is consistent w.r.t. the feature set related information. + +### 11.2.3 Mandatory information in inter-node RRC messages + +For the *AS-Config* transferred within the *HandoverPreparationInformation*: + +- The source node shall include all fields necessary to reflect the current AS configuration of the UE, except for the fields *sourceSCG-NR-Config*, *sourceSCG-EUTRA-Config* and *sourceRB-SN-Config*, which can be omitted in case the source MN did not receive the latest configuration from the source SN. For *RRReconfiguration* included in the field *rrcReconfiguration*, *ReconfigurationWithSync* is included with only the mandatory subfields (e.g. *newUE-Identity* and *t304*) and *ServingCellConfigCommon*; +- Need codes or conditions specified for subfields according to IEs defined in clause 6 do not apply. I.e. some fields shall be included regardless of the "Need" or "Cond" e.g. *discardTimer*; +- Based on the received AS configuration, the target node can indicate the delta (difference) to the current AS configuration (as included in *HandoverCommand*) to the UE. The fields *newUE-Identity* and *t304* included in *ReconfigurationWithSync* are not used for delta configuration purpose. + +The *candidateCellInfoListSN(-EUTRA)* in *CG-Config* and the *candidateCellInfoListMN(-EUTRA)/candidateCellInfoListSN(-EUTRA)* in *CG-ConfigInfo* need not be included in procedures that do not involve a change of node. + +For fields *scg-CellGroupConfig*, *scg-CellGroupConfigEUTRA* and *scg-RB-Config* in *CG-Config* (sent upon SN initiated SN change or other conditions as specified in field descriptions) and fields *mcg-RB-Config*, *scg-RB-Config* and *sourceConfigSCG* in *CG-ConfigInfo* (sent upon change of SN): + +- The source node shall include all fields necessary to reflect the current AS configuration of the UE, unless stated otherwise in the field description. For *RRReconfiguration* included in the field *scg-CellGroupConfig* in *CG-Config*, *ReconfigurationWithSync* is included with only the mandatory subfields (e.g. *newUE-Identity* and *t304*) and *ServingCellConfigCommon*; +- Need codes or conditions specified for subfields according to IEs defined in clause 6 do not apply; + +- Based on the received AS configuration, the target node can indicate the delta (difference) as compared to the current AS configuration to the UE. The fields *newUE-Identity* and *t304* in *ReconfigurationWithSync* are always included by the target node, i.e. they are not used for delta configuration purpose to UE. + +For fields in *CG-Config* and *CG-ConfigInfo* listed below, absence of the field means that the receiver maintains the values informed via the previous message. Note that every time there is a change in the configuration covered by a listed field, the MN or SN shall include the field and it shall provide the full configuration provided by that field unless stated otherwise. Otherwise, if there is no change, the field can be omitted: + +- *configRestrictInfo*; +- *gapPurpose*; +- *measGapConfig* (for which delta signaling applies); +- *measGapConfigFR2* (for which delta signaling applies); +- *measResultCellListSFTD*; +- *measResultSFTD-EUTRA*; +- *sftdFrequencyList-EUTRA*; +- *sftdFrequencyList-NR*; +- *ue-CapabilityInfo*; +- *servFrequenciesMN-NR*. + +For other fields in *CG-Config* and *CG-ConfigInfo*, the sender shall always signal the appropriate value even if same as indicated in the previous inter-node message, unless explicitly stated otherwise. + +## 11.3 Inter-node RRC information element definitions + +### – *ResourceConfigNRDC* + +The IE is used to indicate or request the maximum values that can be used by the SCG in NR-DC, with each value equal to or lower than the value of the corresponding field in the UE capability, as reported by the UE, unless specified otherwise. + +### ***ResourceConfigNRDC* information element** + +``` +-- ASN1START +-- TAG-RESOURCECONFIGNRDC-START + +ResourceConfigNRDC-r17 ::= SEQUENCE { + fr1-ResourceConfig-r17 ResourceConfigPerFR-r17 OPTIONAL, + fr2-ResourceConfig-r17 ResourceConfigPerFR-r17 OPTIONAL, + maxNumberResAcrossCC-AcrossFR-r17 INTEGER (0..256) OPTIONAL, +``` + +``` + + ... +} + +ResourceConfigPerFR-r17 ::= SEQUENCE { + bm-MaxNumberCSI-RS-Resource-r17 INTEGER (0..64) OPTIONAL, + bm-MaxNumberAperiodicCSI-RS-Resource-r17 INTEGER (0..64) OPTIONAL, + cg-MaxNumberConfigsAllCC-r17 INTEGER (0..32) OPTIONAL, + maxNumberCSI-RS-BFD-r17 INTEGER (0..64) OPTIONAL, + maxNumberCSI-RS-SSB-CBD-r17 INTEGER (0..256) OPTIONAL, + maxNumberSSB-BFD-r17 INTEGER (0..64) OPTIONAL, + sps-MaxNumberConfigsAllCC-r17 INTEGER (0..32) OPTIONAL, + trs-MaxConfResourceSetsAllCC-r17 INTEGER (0..256) OPTIONAL, + ... +} + +-- TAG-RESOURCECONFIGNRDC-STOP +-- ASN1STOP + +``` + +### ResourceConfigNRDC field descriptions + +#### **fr1-ResourceConfig, fr2-ResourceConfig** + +Indicates the maximum number of resources that SCG is allowed to configure for FR1/FR2, respectively. + +#### **maxNumberResAcrossCC-AcrossFR** + +Indicates the maximum number of configured CSI-RS resources. Corresponds to the UE capability *maxNumberResAcrossCC-AcrossFR-r16* in *maxTotalResourcesForAcrossFreqRanges-r16*. + +### ResourceConfigPerFR field descriptions + +#### **bm-MaxNumberAperiodicCSI-RS-Resource** + +Indicates the maximum number of aperiodic CSI-RS resources that the SCG is allowed to configure for the UE to measure L1-RSRP. Corresponds to the UE capability *maxNumberAperiodicCSI-RS-Resource* in *beamManagementSSB-CSI-RS*. + +#### **bm-MaxNumberCSI-RS-Resource** + +Indicates the maximum total number of NZP-CSI-RS resources that can be configured for the UE to measure L1-RSRP. Corresponds to the UE capability *maxNumberCSI-RS-Resource* in *beamManagementSSB-CSI-RS*. + +#### **cg-MaxNumberConfigsAllCC** + +Indicates the maximum number of active configured grant configurations. Corresponds to the UE capability *maxNumberConfigsAllCC-r16* in *activeConfiguredGrant-r16*. + +#### **maxNumberCSI-RS-BFD** + +Indicates the maximal number of different CSI-RS resources for the UE to monitor PDCCH quality. Corresponds to the UE capability *maxNumberCSI-RS-BFD*. + +#### **maxNumberCSI-RS-SSB-CBD** + +Indicates the maximal number of different CSI-RS (and/or SSB) resources for new beam identifications. Corresponds to the UE capability *maxNumberCSI-RS-SSB-CBD*. + +#### **maxNumberSSB-BFD** + +Indicates the maximal number of different SSBs for the UE to monitor PDCCH quality. Corresponds to the UE capability *maxNumberSSB-BFD*. + +#### **sps-MaxNumberConfigsAllCC** + +Indicates the maximum number of SPS configurations. Corresponds to the UE capability *maxNumberConfigsAllCC-r16* in *sps-r16*. + +#### **trs-MaxConfResourceSetsAllCC** + +Indicates the maximum configured CSI-RS for tracking (i.e. TRS) resource sets. Corresponds to the UE capability *maxConfiguredResourceSetsAllCC* in *csi-RS-ForTracking*. + +## 11.4 Inter-node RRC multiplicity and type constraint values + +### – Multiplicity and type constraints definitions + +``` +-- ASN1START +-- TAG-NR-MULTIPLICITY-AND-CONSTRAINTS-START + +maxMeasFreqsMN INTEGER ::= 32 -- Maximum number of MN-configured measurement frequencies +maxMeasFreqsSN INTEGER ::= 32 -- Maximum number of SN-configured measurement frequencies +maxMeasIdentitiesMN INTEGER ::= 62 -- Maximum number of measurement identities that a UE can be configured with +maxCellPrep INTEGER ::= 32 -- Maximum number of cells prepared for handover + +-- TAG-NR-MULTIPLICITY-AND-CONSTRAINTS-STOP +-- ASN1STOP +``` + +### – *End of NR-InterNodeDefinitions* + +``` +-- ASN1START +-- TAG-NR-INTER-NODE-DEFINITIONS-END-START + +END + +-- TAG-NR-INTER-NODE-DEFINITIONS-END-STOP +-- ASN1STOP +``` + +# --- 12 Processing delay requirements for RRC procedures + +The UE performance requirements for RRC procedures are specified in the following tables. The performance requirement is expressed as the time in [ms] from the end of reception of the network -> UE message on the UE physical layer up to when the UE shall be ready for the reception of uplink grant for the UE -> network response message with no access delay other than the TTI-alignment (e.g. excluding delays caused by scheduling, the random access procedure or physical layer synchronisation). In case the RRC procedure triggers BWP switching, the RRC procedure delay is the value defined in the following table plus the BWP switching delay defined in TS 38.133 [14], clause 8.6.3. + +![Illustration of RRC procedure delay showing two boxes representing the end of reception of a network message and the start of the response message.](5661815043254c37a4e3e4833f51e727_img.jpg) + +The diagram consists of two empty rectangular boxes. The box on the left is wider and positioned lower than the box on the right, which is narrower and taller. These boxes represent key points in time during an RRC procedure: the end of reception of a network message and the start of the response message. + +Illustration of RRC procedure delay showing two boxes representing the end of reception of a network message and the start of the response message. + +**Figure 12.1-1: Illustration of RRC procedure delay** + +**Table 12.1-1: UE performance requirements for RRC procedures for UEs** + +| Procedure title: | Network -> UE | UE -> Network | Value [ms] | Notes | +|----------------------------------------------------------------------------------------------|-------------------------------------|-----------------------------------|-----------------|--------------------------------| +| RRc Connection Control Procedures | | | | | +| RRc reconfiguration | RRcReconfiguration | RRcReconfigurationComplete | 10 | | +| RRc reconfiguration (scell addition/release) | RRcReconfiguration | RRcReconfigurationComplete | 16 | | +| RRc reconfiguration (LTE/NR SCG establishment/ modification/ release) | RRcReconfiguration | RRcReconfigurationComplete | 16 | | +| RRc reconfiguration (Intra-NR mobility with LTE/NR SCG establishment/ modification/ release) | RRcReconfiguration | RRcReconfigurationComplete | 16 | | +| RRc reconfiguration | DL Dedicated Message Segment | RRcReconfigurationComplete | 16+(Nseg -1)*10 | Nseg is number of RRc segments | +| RRc setup | RRcSetup | RRcSetupComplete | 10 | | +| RRc Release | RRcRelease | | NA | | +| RRc re-establishment | RRcReestablishment | RRcReestablishmentComplete | 10 | | + +| Procedure title: | Network -> UE | UE -> Network | Value [ms] | Notes | +|-----------------------------------------------------|-------------------------------------|-------------------------------------------------|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RRC resume | RRResume | RRResumeComplete | 6 or 10 | Value=6 applies for a UE supporting reduced CP latency for the case of RRResume message only including MAC and PHY configuration, reestablishPDCP and reestablishRLC for SRB2, multicast MRB(s) and DRB(s), and no DRX, SPS, configured grant, CA or MIMO re-configuration will be triggered by this message. Further, the UL grant for transmission of RRResumeComplete and the data is transmitted over common search space with DCI format 0_0. In this scenario, the RRC procedure delay [ms] can extend beyond the reception of the UL grant, up to 7 ms.

For other cases, Value = 10 applies. | +| RRC resume (MCG SCell addition/restoration/release) | RRResume | RRResumeComplete | 16 | | +| RRC resume (SCG establishment/restoration/release) | RRResume | RRResumeComplete | 16 | | +| RRC resume | DL Dedicated Message Segment | RRResumeComplete | 16+(Nseg-1)*10 | Nseg is number of RRC segments | +| Initial AS security activation | SecurityModeCommand | SecurityModeComplete/SecurityModeFailure | 5 | | +| Inter RAT mobility | | | | | + +| Procedure title: | Network -> UE | UE -> Network | Value [ms] | Notes | +|---------------------------------------|--------------------------------------------------|------------------------------------|------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| Handover to NR | RRReconfiguration
(sent by other RAT) | RRReconfigurationComplete | NA | The performance of this procedure is specified in TS 36.133 [40] clauses 5.3.4.2, 5.3.4A.2 and 5.3.5.2 in case of handover from E-UTRA to NR. | +| Handover from NR | MobilityFromNRComm
and | | NA | The performance of this procedure is specified in TS 38.133 [14], clauses 6.1.2.1.2 and 6.1.2.2.2. | +| Other procedures | | | | | +| UE assistance information | | UEAssistanceInformation | NA | | +| UE capability transfer | UECapabilityEnquiry | UECapabilityInformation | 80 | | +| UE capability transfer | UECapabilityEnquiry | ULDedicatedMessageSegment | 80 | | +| Counter check | CounterCheck | CounterCheckResponse | 5 | | +| UE information | UEInformationRequest | UEInformationResponse | 15 | | +| DL Information transfer MR-DC | DLInformationTransfer
MRDC | | NA | The UE shall apply the performance requirements of the RRC message included within the DLInformationTransfer MRDC message. | +| IAB other information | | IABOtherInformation | NA | | +| Sidelink UE information | | SidelinkUEInformationNR | NA | | +| UE Positioning assistance information | | UEPositioningAssistanceInfo | NA | | + +# Annex A (informative): Guidelines, mainly on use of ASN.1 + +## A.1 Introduction + +The following clauses contain guidelines for the specification of RRC protocol data units (PDUs) with ASN.1. + +## --- A.2 Procedural specification + +### A.2.1 General principles + +The procedural specification provides an overall high level description regarding the UE behaviour in a particular scenario. + +It should be noted that most of the UE behaviour associated with the reception of a particular field is covered by the applicable parts of the PDU specification. The procedural specification may also include specific details of the UE behaviour upon reception of a field, but typically this should be done only for cases that are not easy to capture in the PDU clause e.g. general actions, more complicated actions depending on the value of multiple fields. + +Likewise, the procedural specification need not specify the UE requirements regarding the setting of fields within the messages that are sent to the network i.e. this may also be covered by the PDU specification. + +### A.2.2 More detailed aspects + +The following more detailed conventions should be used: + +- Bullets: + - Capitals should be used in the same manner as in other parts of the procedural text i.e. in most cases no capital applies since the bullets are part of the sentence starting with 'The UE shall:' + - All bullets, including the last one in a clause, should end with a semi-colon i.e. an '; +- Conditions: + - Whenever multiple conditions apply, a semi-colon should be used at the end of each conditions with the exception of the last one, i.e. as in 'if cond1, or cond2. + +## --- A.3 PDU specification + +### A.3.1 General principles + +#### A.3.1.1 ASN.1 clauses + +The RRC PDU contents are formally and completely described using abstract syntax notation (ASN.1), see X.680 [6], X.681 [7]. + +The complete ASN.1 code is divided into a number of ASN.1 clauses in the specifications. In order to facilitate the extraction of the complete ASN.1 code from the specification, each ASN.1 clause begins with the following: + +- a first text paragraph consisting entirely of an *ASN.1 start tag*, which consists of a double hyphen followed by a single space and the text string "ASN1START" (in all upper case letters); +- a second text paragraph consisting entirely of a *block start tag* is included, which consists of a double hyphen followed by a single space and the text string "TAG-NAME-START" (in all upper case letters), where the "NAME" refers to the main name of the paragraph (in all upper-case letters). + +Similarly, each ASN.1 clause ends with the following: + +- a first text paragraph consisting entirely of a *block stop tag*, which consists of a double hyphen followed by a single space and the text string "TAG-NAME-STOP" (in all upper-case letters), where the "NAME" refers to the main name of the paragraph (in all upper-case letters); +- a second text paragraph consisting entirely of an *ASN.1 stop tag*, which consists of a double hyphen followed by a single space and the text "ASN1STOP" (in all upper case letters). + +This results in the following tags: + +``` +-- ASN1START +-- TAG-NAME-START + +-- TAG-NAME-STOP +-- ASN1STOP +``` + +The text paragraphs containing either of the start and stop tags should not contain any ASN.1 code significant for the complete description of the RRC PDU contents. The complete ASN.1 code may be extracted by copying all the text paragraphs between an ASN.1 start tag and the following ASN.1 stop tag in the order they appear, throughout the specification. + +NOTE: A typical procedure for extraction of the complete ASN.1 code consists of a first step where the entire RRC PDU contents description (ultimately the entire specification) is saved into a plain text (ASCII) file format, followed by a second step where the actual extraction takes place, based on the occurrence of the ASN.1 start and stop tags. + +#### A.3.1.2 ASN.1 identifier naming conventions + +The naming of identifiers (i.e., the ASN.1 field and type identifiers) should be based on the following guidelines: + +- Message (PDU) identifiers should be ordinary mixed case without hyphenation. These identifiers, *e.g.*, the *RRConnectionModificationCommand*, should be used for reference in the procedure text. Abbreviations should be avoided in these identifiers and abbreviated forms of these identifiers should not be used. +- Type identifiers other than PDU identifiers should be ordinary mixed case, with hyphenation used to set off acronyms only where an adjacent letter is a capital, *e.g.*, *EstablishmentCause*, *SelectedPLMN* (not *Selected-PLMN*, since the "d" in "Selected" is lowercase), *InitialUE-Identity* and *MeasSFN-SFN-TimeDifference*. +- Field identifiers shall start with a lowercase letter and use mixed case thereafter, *e.g.*, *establishmentCause*. If a field identifier begins with an acronym (which would normally be in upper case), the entire acronym is lowercase (*plmn-Identity*, not *pLMN-Identity*). The acronym is set off with a hyphen (*ue-Identity*, not *ueIdentity*), in order to facilitate a consistent search pattern with corresponding type identifiers. + +- Identifiers should convey the meaning of the identifier and should avoid adding unnecessary postfixes (e.g. abstractions like 'Info') for the name. +- Identifiers that are likely to be keywords of some language, especially widely used languages, such as C++ or Java, should be avoided to the extent possible. +- Identifiers, other than PDU identifiers, longer than 25 characters should be avoided where possible. It is recommended to use abbreviations, which should be done in a consistent manner i.e. use 'Meas' instead of 'Measurement' for all occurrences. Examples of typical abbreviations are given in table A.3.1.2.1-1 below. +- *For future extension:* When an extension is introduced a suffix is added to the identifier of the concerned ASN.1 field and/or type. A suffix of the form "-rX" is used, with X indicating the release, for ASN.1 fields or types introduced in a later release (i.e. a release later than the original/first release of the protocol) as well as for ASN.1 fields or types for which a revision is introduced in a later release replacing a previous version, e.g., *Foo-r9* for the Rel-9 version of the ASN.1 type *Foo*. A suffix of the form "-rXb" is used for the first revision of a field that it appears in the same release (X) as the original version of the field, "-rXc" for a second intra-release revision and so on. A suffix of the form "-vXYZ" is used for ASN.1 fields or types that only are an extension of a corresponding earlier field or type (see clause A.4), e.g., *AnElement-v10b0* for the extension of the ASN.1 type *AnElement* introduced in version 10.11.0 of the specification. A number 0...9, 10, 11, etc. is used to represent the first part of the version number, indicating the release of the protocol. Lower case letters a, b, c, etc. are used to represent the second (and third) part of the version number if they are greater than 9. In the procedural specification, in field descriptions as well as in headings suffices are not used, unless there is a clear need to distinguish the extension from the original field. +- More generally, in case there is a need to distinguish different variants of an ASN.1 field or IE, a suffix should be added at the end of the identifiers e.g. *MeasObjectUTRA*, *ConfigCommon*. When there is no particular need to distinguish the fields (e.g. because the field is included in different IEs), a common field identifier name may be used. This may be attractive e.g. in case the procedural specification is the same for the different variants. +- It should be avoided to use field identifiers with the same name within the elements of a CHOICE, including using a CHOICE inside a SEQUENCE (to avoid certain compiler errors). + +**Table A.3.1.2-1: Examples of typical abbreviations used in ASN.1 identifiers** + +| Abbreviation | Abbreviated word | +|--------------|------------------------| +| Config | Configuration | +| DL | Downlink | +| Ext | Extension | +| Freq | Frequency | +| Id | Identity | +| Ind | Indication | +| Meas | Measurement | +| MIB | MasterInformationBlock | +| Neigh | Neighbour(ing) | +| Param(s) | Parameter(s) | +| Phys | Physical | +| PCI | Physical Cell Id | +| Proc | Process | +| Reconfig | Reconfiguration | +| Reest | Re-establishment | +| Req | Request | +| Rx | Reception | +| Sched | Scheduling | +| SIB | SystemInformationBlock | +| Sync | Synchronisation | +| Thr | Threshold | +| Tx | Transmission | +| UL | Uplink | + +NOTE: The table A.3.1.2.1-1 is not exhaustive. Additional abbreviations may be used in ASN.1 identifiers when needed. + +#### A.3.1.3 Text references using ASN.1 identifiers + +A text reference into the RRC PDU contents description from other parts of the specification is made using the ASN.1 field identifier of the referenced type. The ASN.1 field and type identifiers used in text references should be in the *italic font style*. The "do not check spelling and grammar" attribute in Word should be set. Quotation marks (i.e., "") should not be used around the ASN.1 field or type identifier. + +A reference to an RRC PDU should be made using the corresponding ASN.1 field identifier followed by the word "message", e.g., a reference to the *RRRelease* message. + +A reference to a specific part of an RRC PDU, or to a specific part of any other ASN.1 type, should be made using the corresponding ASN.1 field identifier followed by the word "field", e.g., a reference to the *prioritisedBitRate* field in the example below. + +``` +-- /example/ ASN1START +LogicalChannelConfig ::= SEQUENCE { + ul-SpecificParameters SEQUENCE { +``` + +``` + + priority Priority, + prioritisedBitRate PrioritisedBitRate, + bucketSizeDuration BucketSizeDuration, + logicalChannelGroup INTEGER (0..3) + } OPTIONAL +} + +-- ASN1STOP + +``` + +NOTE: All the ASN.1 start tags in the ASN.1 clauses, used as examples in this annex to the specification, are deliberately distorted, in order not to include them when the ASN.1 description of the RRC PDU contents is extracted from the specification. + +A reference to a specific type of information element should be made using the corresponding ASN.1 type identifier preceded by the acronym "IE", e.g., a reference to the IE *LogicalChannelConfig* in the example above. + +References to a specific type of information element should only be used when those are generic, i.e., without regard to the particular context wherein the specific type of information element is used. If the reference is related to a particular context, e.g., an RRC PDU type (message) wherein the information element is used, the corresponding field identifier in that context should be used in the text reference. + +A reference to a specific value of an ASN.1 field should be made using the corresponding ASN.1 value without using quotation marks around the ASN.1 value, e.g., 'if the *status* field is set to value *true*'. + +### A.3.2 High-level message structure + +Within each logical channel type, the associated RRC PDU (message) types are alternatives within a CHOICE, as shown in the example below. + +``` + +-- /example/ ASN1START + +DL-DCCH-Message ::= SEQUENCE { + message DL-DCCH-MessageType +} + +DL-DCCH-MessageType ::= CHOICE { + c1 CHOICE { + dlInformationTransfer DLInformationTransfer, + handoverFromEUTRAPreparationRequest HandoverFromEUTRAPreparationRequest, + mobilityFromEUTRACommand MobilityFromEUTRACommand, + rrcConnectionReconfiguration RRCConnectionReconfiguration, + rrcConnectionRelease RRCConnectionRelease, + securityModeCommand SecurityModeCommand, + ueCapabilityEnquiry UECapabilityEnquiry, + spare1 NULL + }, + messageClassExtension SEQUENCE {} +} + +-- ASN1STOP + +``` + +A nested two-level CHOICE structure is used, where the alternative PDU types are alternatives within the inner level *c1* CHOICE. + +Spare alternatives (i.e., *spare1* in this case) may be included within the *c1* CHOICE to facilitate future extension. The number of such spare alternatives should not extend the total number of alternatives beyond an integer-power-of-two number of alternatives (i.e., eight in this case). + +Further extension of the number of alternative PDU types is facilitated using the *messageClassExtension* alternative in the outer level CHOICE. + +### A.3.3 Message definition + +Each PDU (message) type is specified in an ASN.1 clause similar to the one shown in the example below. + +``` +-- /example/ ASN1START + +RRConnectionReconfiguration ::= SEQUENCE { + rrc-TransactionIdentifier RRC-TransactionIdentifier, + criticalExtensions CHOICE { + c1 CHOICE{ + rrcConnectionReconfiguration-r8 RRCConnectionReconfiguration-r8-IEs, + spare3 NULL, spare2 NULL, spare1 NULL + }, + criticalExtensionsFuture SEQUENCE {} + } +} + +RRConnectionReconfiguration-r8-IEs ::= SEQUENCE { + -- Enter the IEs here. + ... +} + +-- ASN1STOP +``` + +Hooks for *critical* and *non-critical* extension should normally be included in the PDU type specification. How these hooks are used is further described in clause A.4. + +Critical extensions are characterised by a redefinition of the PDU contents and need to be governed by a mechanism for protocol version agreement between the encoder and the decoder of the PDU, such that the encoder is prevented from sending a critically extended version of the PDU type, which is not comprehended by the decoder. + +Critical extension of a PDU type is facilitated by a two-level CHOICE structure, where the alternative PDU contents are alternatives within the inner level *c1* CHOICE. Spare alternatives (i.e., *spare3* down to *spare1* in this case) may be included within the *c1* CHOICE. The number of spare alternatives to be included in the original PDU specification should be decided case by case, based on the expected rate of critical extension in the future releases of the protocol. + +Further critical extension, when the spare alternatives from the original specifications are used up, is facilitated using the *criticalExtensionsFuture* in the outer level CHOICE. + +In PDU types where critical extension is not expected in the future releases of the protocol, the inner level *c1* CHOICE and the spare alternatives may be excluded, as shown in the example below. + +``` + +-- /example/ ASN1START + +RRConnectionReconfigurationComplete ::= SEQUENCE { + rrc-TransactionIdentifier RRC-TransactionIdentifier, + criticalExtensions CHOICE { + rrcConnectionReconfigurationComplete-r8 + RRCConnectionReconfigurationComplete-r8-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +RRConnectionReconfigurationComplete-r8-IEs ::= SEQUENCE { + -- Enter the fields here. + ... +} + +-- ASN1STOP + +``` + +Non-critical extensions are characterised by the addition of new information to the original specification of the PDU type. If not comprehended, a non-critical extension may be skipped by the decoder, whilst the decoder is still able to complete the decoding of the comprehended parts of the PDU contents. + +Non-critical extensions at locations other than the end of the message or other than at the end of a field contained in a BIT or OCTET STRING are facilitated by use of the ASN.1 extension marker "...". The original specification of a PDU type should normally include the extension marker at the end of the sequence of information elements contained. + +Non-critical extensions at the end of the message or at the end of a field that is contained in a BIT or OCTET STRING may be facilitated by use of an empty sequence that is marked OPTIONAL e.g. as shown in the following example: + +``` + +-- /example/ ASN1START + +RRMessage-r8-IEs ::= SEQUENCE { + field1 InformationElement1, + field2 InformationElement2, + + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +-- ASN1STOP + +``` + +The ASN.1 clause specifying the contents of a PDU type may be followed by a *field description* table where a further description of, e.g., the semantic properties of the fields may be included. The general format of this table is shown in the example below. The field description table is absent in case there are no fields for which further description needs to be provided e.g. because the PDU does not include any fields, or because an IE is defined for each field while there is nothing specific regarding the use of this IE that needs to be specified. + +| %PDU-TypeIdentifier% field descriptions | +|-------------------------------------------------| +| %field identifier%
Field description. | +| %field identifier%
Field description. | + +The field description table has one column. The header row shall contain the ASN.1 type identifier of the PDU type. + +The following rows are used to provide field descriptions. Each row shall include a first paragraph with a *field identifier* (in ***bold and italic*** font style) referring to the part of the PDU to which it applies. The following paragraphs at the same row may include (in regular font style), e.g., semantic description, references to other specifications and/or specification of value units, which are relevant for the particular part of the PDU. + +The parts of the PDU contents that do not require a field description shall be omitted from the field description table. + +### A.3.4 Information elements + +Each IE (information element) type is specified in an ASN.1 clause similar to the one shown in the example below. + +``` +-- /example/ ASN1START + +PRACH-ConfigSIB ::= + rootSequenceIndex + prach-ConfigInfo +} + SEQUENCE { + INTEGER (0..1023), + PRACH-ConfigInfo + } + +PRACH-Config ::= + rootSequenceIndex + prach-ConfigInfo +} + SEQUENCE { + INTEGER (0..1023), + PRACH-ConfigInfo + OPTIONAL -- Need N + } + +PRACH-ConfigInfo ::= + prach-ConfigIndex + highSpeedFlag + zeroCorrelationZoneConfig +} + SEQUENCE { + ENUMERATED {ffs}, + ENUMERATED {ffs}, + ENUMERATED {ffs} + } + +-- ASN1STOP +``` + +IEs should be introduced whenever there are multiple fields for which the same set of values apply. IEs may also be defined for other reasons e.g. to break down a ASN.1 definition in to smaller pieces. + +A group of closely related IE type definitions, like the IEs *PRACH-ConfigSIB* and *PRACH-Config* in this example, are preferably placed together in a common ASN.1 clause. The IE type identifiers should in this case have a common base, defined as the *generic type identifier*. It may be complemented by a suffix to distinguish the different variants. The "*PRACH-Config*" is the generic type identifier in this example, and the "*SIB*" suffix is added to distinguish the variant. The clause heading and generic references to a group of closely related IEs defined in this way should use the generic type identifier. + +The same principle should apply if a new version, or an extension version, of an existing IE is created for *critical* or *non-critical* extension of the protocol (see clause A.4). The new version, or the extension version, of the IE is included in the same ASN.1 clause defining the original. A suffix is added to the type identifier, using the naming conventions defined in clause A.3.1.2, indicating the release or version of the where the new version, or extension version, was introduced. + +Local IE type definitions, like the IE *PRACH-ConfigInfo* in the example above, may be included in the ASN.1 clause and be referenced in the other IE types defined in the same ASN.1 clause. The use of locally defined IE types should be encouraged, as a tool to break up large and complex IE type definitions. It can improve the readability of the code. There may also be a benefit for the software implementation of the protocol end-points, as these IE types are typically provided by the ASN.1 compiler as independent data elements, to be used in the software implementation. + +An IE type defined in a local context, like the IE *PRACH-ConfigInfo*, should not be referenced directly from other ASN.1 clauses in the RRC specification. An IE type which is referenced in more than one ASN.1 clause should be defined in a separate clause, with a separate heading and a separate ASN.1 clause (possibly as one in a set of closely related IE types, like the IEs *PRACH-ConfigSIB* and *PRACH-Config* in the example above). Such IE types are also referred to as 'global IEs'. + +NOTE: Referring to an IE type, that is defined as a local IE type in the context of another ASN.1 clause, does not generate an ASN.1 compilation error. Nevertheless, using a locally defined IE type in that way makes the IE type definition difficult to find, as it would not be visible at an outline level of the specification. It should be avoided. + +The ASN.1 clause specifying the contents of one or more IE types, like in the example above, may be followed by a *field description* table, where a further description of, e.g., the semantic properties of the fields of the information elements may be included. This table may be absent, similar as indicated in clause A.3.3 for the specification of the PDU type. The general format of the *field description* table is the same as shown in clause A.3.3 for the specification of the PDU type. + +### A.3.5 Fields with optional presence + +A field with optional presence may be declared with the keyword **DEFAULT**. It identifies a default value to be assumed, if the sender does not include a value for that field in the encoding: + +``` +-- /example/ ASN1START + +PreambleInfo ::= + SEQUENCE { + numberOfRA-Preambles INTEGER (1..64) DEFAULT 1, + ... + } + +-- ASN1STOP +``` + +Alternatively, a field with optional presence may be declared with the keyword **OPTIONAL**. It identifies a field for which a value can be omitted. The omission carries semantics, which is different from any normal value of the field: + +``` +-- /example/ ASN1START + +PRACH-Config ::= + SEQUENCE { + rootSequenceIndex INTEGER (0..1023), + prach-ConfigInfo PRACH-ConfigInfo OPTIONAL -- Need N + } +``` + +``` +-- ASN1STOP +``` + +The semantics of an optionally present field, in the case it is omitted, should be indicated at the end of the paragraph including the keyword OPTIONAL, using a short comment text with a need code. The need code includes the keyword "Need", followed by one of the predefined semantics tags (S, M, N or R) defined in clause 6.1. If the semantics tag S is used, the semantics of the absent field are further specified either in the field description table following the ASN.1 clause, or in procedure text. + +The addition of OPTIONAL keywords for capability groups is based on the following guideline. If there is more than one field in the lower level IE, then OPTIONAL keyword is added at the group level. If there is only one field in the lower level IE, OPTIONAL keyword is not added at the group level. + +### A.3.6 Fields with conditional presence + +A field with conditional presence is declared with the keyword OPTIONAL. In addition, a short comment text shall be included at the end of the paragraph including the keyword OPTIONAL. The comment text includes the keyword "Cond", followed by a condition tag associated with the field ("UL" in this example): + +``` +-- /example/ ASN1START +LogicalChannelConfig ::= + ul-SpecificParameters SEQUENCE { + priority SEQUENCE { + ... INTEGER (0), + } OPTIONAL -- Cond UL + } +-- ASN1STOP +``` + +When conditionally present fields are included in an ASN.1 clause, the field description table after the ASN.1 clause shall be followed by a *conditional presence* table. The conditional presence table specifies the conditions for including the fields with conditional presence in the particular ASN.1 clause. + +| Conditional presence | Explanation | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UL | Specification of the conditions for including the field associated with the condition tag = "UL". Semantics in case of optional presence under certain conditions may also be specified. | + +The conditional presence table has two columns. The first column (heading: "Conditional presence") contains the condition tag (in *italic* font style), which links the fields with a condition tag in the ASN.1 clause to an entry in the table. The second column (heading: "Explanation") contains a text specification of the conditions and requirements for the presence of the field. The second column may also include semantics, in case of an optional presence of the field, under certain conditions i.e. using the same predefined tags as defined for optional fields in A.3.5. + +Conditional presence should primarily be used when presence of a field depends on the presence and/or value of other fields within the same message. If the presence of a field depends on whether another feature/function has been configured, while this function can be configured independently e.g. by another message and/or at another point in time, the relation is best reflected by means of a statement in the field description table. + +If the ASN.1 clause does not include any fields with conditional presence, the conditional presence table shall not be included. + +Whenever a field is only applicable in specific cases e.g. TDD, use of conditional presence should be considered. + +### A.3.7 Guidelines on use of lists with elements of SEQUENCE type + +Where an information element has the form of a list (the SEQUENCE OF construct in ASN.1) with the type of the list elements being a SEQUENCE data type, an information element shall be defined for the list elements even if it would not otherwise be needed. + +For example, a list of PLMN identities with reservation flags is defined as in the following example: + +``` +-- /example/ ASN1START +PLMN-IdentityInfoList ::= SEQUENCE (SIZE (1..6)) OF PLMN-IdentityInfo +PLMN-IdentityInfo ::= SEQUENCE { + plmn-Identity PLMN-Identity, + cellReservedForOperatorUse ENUMERATED {reserved, notReserved} +} + +-- ASN1STOP +``` + +rather than as in the following (bad) example, which may cause generated code to contain types with unpredictable names: + +``` +-- /bad example/ ASN1START +PLMN-IdentityList ::= SEQUENCE (SIZE (1..6)) OF SEQUENCE { + plmn-Identity PLMN-Identity, + cellReservedForOperatorUse ENUMERATED {reserved, notReserved} +} + +-- ASN1STOP +``` + +### A.3.8 Guidelines on use of parameterised SetupRelease type + +The usage of the parameterised *SetupRelease* type is like a function call in programming languages where the element type parameter is passed as a parameter. The parameterised type only implies a textual change in abstract syntax where all references to the parameterised type are replaced by the compiler with the release/setup choice. Two examples of the usage are shown below: + +``` +-- /example/ ASN1START +RRMessage-rX-IEs ::= SEQUENCE { + field-rX SetupRelease { IE-rX } OPTIONAL, -- Need M + ... +} + +RRMessage-rX-IEs ::= SEQUENCE { +``` + +``` + + field-rX SetupRelease { Element-rX } OPTIONAL, -- Need M +} + +Element-rX ::= SEQUENCE { + field1-rX IE1-rX, + field2-rX IE2-rX OPTIONAL -- Need N +} OPTIONAL, -- Need M + +-- /example/ ASN1STOP + +``` + +The *SetupRelease* is always be used with only named IEs, i.e. the example below is not allowed: + +``` + +-- /example/ ASN1START + +RRCMessage-rX-IEs ::= SEQUENCE { + field-rX SetupRelease { SEQUENCE { -- Unnamed SEQUENCES are not allowed! + field1-rX IE1-rX, + field2-rX IE2-rX OPTIONAL -- Need N + } } +} OPTIONAL, -- Need M + +-- /example/ ASN1STOP + +``` + +If a field defined using the parameterized *SetupRelease* type requires procedural text, the field is referred to using the values defined for the type itself, namely, "setup" and "release". For example, procedural text for *field-rX* above could be as follows: + +- 1> if *field-rX* is set to "setup": + +- 2> do something; + +- 1> else (*field-rX* is set to "release"): + +- 2> release *field-rX* (if appropriate). + +### A.3.9 Guidelines on use of ToAddModList and ToReleaseList + +In order to benefit from delta signalling when modifying lists with many and/or large elements, so-called add/mod- and release- lists should be used. Instead of a single list containing all elements of the list, the ASN.1 provides two lists. One list is used to convey the actual elements that are to be added to the list or modified in the list. The second list conveys only the identities (IDs) of the list elements that are to be released from the list. In other words, the ASN.1 defines only means to signal modifications to a list maintained in the receiver (typically the UE). An example is provided below: + +``` + +-- /example/ ASN1START + +AnExampleIE ::= SEQUENCE { + elementsToAddModList SEQUENCE (SIZE (1..maxNrofElements)) OF Element OPTIONAL, -- Need N + +``` + +``` + +elementsToReleaseList SEQUENCE (SIZE (1..maxNrofElements)) OF ElementId OPTIONAL, -- Need N +... +} + +Element ::= SEQUENCE { + elementId ElementId, + aField INTEGER (0..16777215), + anotherField OCTET STRING, + ... +} + +ElementId ::= INTEGER (0..maxNrofElements-1) + +maxNrofElements INTEGER ::= 50 +maxNrofElements-1 INTEGER ::= 49 + +-- /example/ ASN1STOP + +``` + +As can be seen, the elements of the list must contain an identity (INTEGER) that identifies the elements unambiguously upon addition, modification and removal. It is recommended to define an IE for that identifier (here *ElementId*) so that it can be used both for a field inside the element as well as in the *elementsToReleaseList*. + +Both lists should be made OPTIONAL and flagged as "Need N". The need code reflects that the UE does not maintain the received lists as such but rather updates its configuration using the information therein. In other words, it is not possible to provide via delta signalling an update to a previously signalled *elementsToAddModList* or *elementsToReleaseList* (which Need M would imply). The update is always in relation to the UE's internal configuration. + +Note that the release of a field (a list element as well as any other field) releases all its sub-fields (sub-fields configured by *elementsToAddModList* and any other sub-field). + +If no procedural text is provided for a set of *ToAddModList* and *ToReleaseList*, the following generic procedure applies: + +The UE shall: + +- 1> for each *ElementId* in the *elementsToReleaseList*: + - 2> if the current UE configuration includes an *Element* with the given *ElementId*: + - 3> release the *Element* from the current UE configuration; +- 1> for each *Element* in the *elementsToAddModList*: + - 2> if the current UE configuration includes an *Element* with the given *ElementId*: + - 3> modify the configured *Element* in accordance with the received *Element*; + - 2> else: + - 3> add received *Element* to the UE configuration. + +### A.3.10 Guidelines on use of lists (without ToAddModList and ToReleaseList) + +As per clause 6.1.3, when using lists without the ToAddModList and ToReleaseList structure, the contents of the lists are always replaced. To illustrate this, an example is provided below: + +``` +-- /example/ ASN1START +-- TAG_EXAMPLE_LISTS_START + +AnExampleIE ::= + elementList SEQUENCE { + elementList SEQUENCE (SIZE (1..maxNrofElements)) OF Element + ... + [[ + elementListExt-v2030 SEQUENCE (SIZE (1..maxNrofElementsExt)) OF Element + ]] + } + OPTIONAL, -- Need M + +Element ::= + useFeatureX BOOLEAN, + aField INTEGER (0..127) + anotherField INTEGER (0..127) + ... + OPTIONAL, -- Need M + OPTIONAL, -- Need R + +maxNrofElements INTEGER := 8 +maxNrofElements-1 INTEGER := 7 +maxNrofElementsExt INTEGER := 8 +maxNrofElementsExt-1 INTEGER := 7 + +-- TAG_EXAMPLE_LISTS_STOP +-- /example/ ASN1STOP +``` + +As can be seen, the *elementList* list itself uses Need M, but each list entry *Element* contains mandatory, Need M and Need R fields. If the list is first signalled to UE with 3 entries, and subsequently again with 2 entries, UE shall retain only the latter list, i.e. the list with 2 elements will completely replace the list with 3 elements. That also means that the field *aField* will be treated as if it was newly created, i.e. network must include it if it wishes UE to utilize the field even if it was previously signalled. This also implies that the Need M field (*aField*) will be treated in the same way as the Need R field (*anotherField*), i.e. delta signalling is not applied and the network has to signal the field to ensure UE does not release the value (which is why Need M should not normally be used in the entries of these lists). + +## A.4 Extension of the PDU specifications + +### A.4.1 General principles to ensure compatibility + +It is essential that extension of the protocol does not affect interoperability i.e. it is essential that implementations based on different versions of the RRC protocol are able to interoperate. In particular, this requirement applies for the following kind of protocol extensions: + +- Introduction of new PDU types (i.e. these should not cause unexpected behaviour or damage). + +- Introduction of additional fields in an extensible PDUs (i.e. it should be possible to ignore uncomprehended extensions without affecting the handling of the other parts of the message). +- Introduction of additional values of an extensible field of PDUs. If used, the behaviour upon reception of an uncomprehended value should be defined. + +It should be noted that the PDU extension mechanism may depend on the logical channel used to transfer the message e.g. for some PDUs an implementation may be aware of the protocol version of the peer in which case selective ignoring of extensions may not be required. + +The non-critical extension mechanism is the primary mechanism for introducing protocol extensions i.e. the critical extension mechanism is used merely when there is a need to introduce a 'clean' message version. Such a need appears when the last message version includes a large number of non-critical extensions, which results in issues like readability, overhead associated with the extension markers. The critical extension mechanism may also be considered when it is complicated to accommodate the extensions by means of non-critical extension mechanisms. + +### A.4.2 Critical extension of messages and fields + +The mechanisms to critically extend a message are defined in A.3.3. There are both "outer branch" and "inner branch" mechanisms available. The "outer branch" consists of a CHOICE having the name *criticalExtensions*, with two values, *c1* and *criticalExtensionsFuture*. The *criticalExtensionsFuture* branch consists of an empty SEQUENCE, while the *c1* branch contains the "inner branch" mechanism. + +The "inner branch" structure is a CHOICE with values of the form "*MessageName-rX-IEs*" (e.g., "*RRConnectionReconfiguration-r8-IEs*") or "*spareX*", with the spare values having type NULL. The "*-rX-IEs*" structures contain the *complete* structure of the message IEs for the appropriate release; i.e., the critical extension branch for the Rel-10 version of a message includes all Rel-8 and Rel-9 fields (that are not obviated in the later version), rather than containing only the additional Rel-10 fields. + +The following guidelines may be used when deciding which mechanism to introduce for a particular message, i.e. only an 'outer branch', or an 'outer branch' in combination with an 'inner branch' including a certain number of spares: + +- For certain messages, e.g. initial uplink messages, messages transmitted on a broadcast channel, critical extension may not be applicable. +- An outer branch may be sufficient for messages not including any fields. +- The number of spares within inner branch should reflect the likelihood that the message will be critically extended in future releases (since each release with a critical extension for the message consumes one of the spare values). The estimation of the critical extension likelihood may be based on the number, size and changeability of the fields included in the message. +- In messages where an inner branch extension mechanism is available, all spare values of the inner branch should be used before any critical extensions are added using the outer branch. + +The following example illustrates the use of the critical extension mechanism by showing the ASN.1 of the original and of a later release + +``` +-- /example/ ASN1START +RRMessage ::= + rrc-TransactionIdentifier + criticalExtensions + c1 + +-- Original release +SEQUENCE { + RRC-TransactionIdentifier, + CHOICE { + CHOICE{ +``` + +``` + + rrcMessage-r8 RRCMessage-r8-IEs, + spare3 NULL, spare2 NULL, spare1 NULL + }, + criticalExtensionsFuture SEQUENCE {} +} +} +-- ASN1STOP + +``` + +``` + +-- /example/ ASN1START -- Later release +RRMessage ::= SEQUENCE { + rrc-TransactionIdentifier RRC-TransactionIdentifier, + criticalExtensions CHOICE { + c1 CHOICE{ + rrcMessage-r8 RRCMessage-r8-IEs, + rrcMessage-r10 RRCMessage-r10-IEs, + rrcMessage-r11 RRCMessage-r11-IEs, + rrcMessage-r14 RRCMessage-r14-IEs + }, + later CHOICE { + c2 CHOICE{ + rrcMessage-r16 RRCMessage-r16-IEs, + spare7 NULL, spare6 NULL, spare5 NULL, spare4 NULL, + spare3 NULL, spare2 NULL, spare1 NULL + }, + criticalExtensionsFuture SEQUENCE {} + } + } +} +-- ASN1STOP + +``` + +It is important to note that critical extensions may also be used at the level of individual fields i.e. a field may be replaced by a critically extended version. When sending the extended version, the original version may also be included (e.g. original field is mandatory, E-UTRAN is unaware if UE supports the extended version). In such cases, a UE supporting both versions may be required to ignore the original field. The following example illustrates the use of the critical extension mechanism by showing the ASN.1 of the original and of a later release. + +``` + +-- /example/ ASN1START -- Original release +RRMessage ::= SEQUENCE { + rrc-TransactionIdentifier RRC-TransactionIdentifier, + criticalExtensions CHOICE { + c1 CHOICE{ + rrcMessage-r8 RRCMessage-r8-IEs, + spare3 NULL, spare2 NULL, spare1 NULL + }, + criticalExtensionsFuture SEQUENCE {} + } +} + +``` + +``` + +} + +RRCMessage-rN-IEs ::= SEQUENCE { + field1-rN ENUMERATED { + value1, value2, value3, value4} OPTIONAL, -- Need N + field2-rN InformationElement2-rN OPTIONAL, -- Need N + nonCriticalExtension RRCConnectionReconfiguration-vMxy-IEs OPTIONAL +} + +RRCConnectionReconfiguration-vMxy-IEs ::= SEQUENCE { + field2-rM InformationElement2-rM OPTIONAL, -- Cond NoField2rN + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +-- ASN1STOP + +``` + +| Conditional presence | Explanation | +|----------------------|------------------------------------------------------------------------------------------------| +| NoField2rN | The field is optionally present, need N, if field2-rN is absent. Otherwise the field is absent | + +Finally, it is noted that a critical extension may be introduced in the same release as the one in which the original field was introduced e.g. to correct an essential ASN.1 error. In such cases a UE capability may be introduced, to assist the network in deciding whether or not to use the critical extension. + +In the case of list fields (SEQUENCE OF types in ASN.1) using the ToAddMod/ToRelease construction, the use of critical extensions to increase the size of a list should be avoided; that is, replacing the original list field by a new field also used to signal entries previously covered by the original field (i.e. extensions done according to the following example) should be avoided: + +``` + +-- /example/ ASN1START -- Discouraged example + +ContainingStructure ::= SEQUENCE { + listElementToAddModList SEQUENCE (SIZE (1..maxNrofListElements)) OF ListElement OPTIONAL, -- Need N + ... + [[ + listElementToAddModList-rN SEQUENCE (SIZE (1..maxNrofListElements-rN)) OF ListElement OPTIONAL -- Need N + ]] +}-- ASN1STOP + +``` + +Instead, a non-critical list extension mechanism should typically be used, such that the extension field only adds the new entries of the list. This approach is further described in clause A.4.3.6. + +If the critical extension mechanism for a list is used, it should be clarified in the field description that the two versions of the list are not configured together, and that the network should release the contents of the original version when configuring the replacement version. + +### A.4.3 Non-critical extension of messages + +#### A.4.3.1 General principles + +The mechanisms to extend a message in a non-critical manner are defined in A.3.3. W.r.t. the use of extension markers, the following additional guidelines apply: + +- When further non-critical extensions are added to a message that has been critically extended, the inclusion of these non-critical extensions in earlier critical branches of the message should be avoided when possible. +- The extension marker ("...") is the primary non-critical extension mechanism that is used but empty sequences may be used if length determinant is not required. Examples of cases where a length determinant is not required: + - at the end of a message; + - at the end of a structure contained in a BIT STRING or OCTET STRING. +- When an extension marker is available, non-critical extensions are preferably placed at the location (e.g. the IE) where the concerned parameter belongs from a logical/functional perspective (referred to as the '*default extension location*'). +- It is desirable to aggregate extensions of the same release or version of the specification into a group, which should be placed at the lowest possible level. +- In specific cases it may be preferable to place extensions elsewhere (referred to as the '*actual extension location*') e.g. when it is possible to aggregate several extensions in a group. In such a case, the group should be placed at the lowest suitable level in the message. +- In case placement at the default extension location affects earlier critical branches of the message, locating the extension at a following higher level in the message should be considered. +- In case an extension is not placed at the default extension location, an IE should be defined. The IE's ASN.1 definition should be placed in the same ASN.1 clause as the default extension location. In case there are intermediate levels in-between the actual and the default extension location, an IE may be defined for each level. Intermediate levels are primarily introduced for readability and overview. Hence intermediate levels need not always be introduced e.g. they may not be needed when the default and the actual extension location are within the same ASN.1 clause. + +#### A.4.3.2 Further guidelines + +Further to the general principles defined in the previous clause, the following additional guidelines apply regarding the use of extension markers: + +- Extension markers within SEQUENCE: + - Extension markers are primarily, but not exclusively, introduced at the higher nesting levels. + - Extension markers are introduced for a SEQUENCE comprising several fields as well as for information elements whose extension would result in complex structures without it (e.g. re-introducing another list). + - Extension markers are introduced to make it possible to maintain important information structures e.g. parameters relevant for one particular RAT. + +- Extension markers are also used for size critical messages (i.e. messages on BCCH, BR-BCCH, PCCH and CCCH), although introduced somewhat more carefully. +- The extension fields introduced (or frozen) in a specific version of the specification are grouped together using double brackets. +- Extension markers within ENUMERATED: + - Spare values may be used until the number of values reaches the next power of 2, while the extension marker caters for extension beyond that limit, given that the use of spare values in a later Release is possible without any error cases. + - A suffix of the form "vXYZ" is used for the identifier of each new value, e.g. "value-vXYZ". +- Extension markers within CHOICE: + - Extension markers are introduced when extension is foreseen and when comprehension is not required by the receiver i.e. behaviour is defined for the case where the receiver cannot comprehend the extended value (e.g. ignoring an optional CHOICE field). It should be noted that defining the behaviour of a receiver upon receiving a not comprehended choice value is not required if the sender is aware whether or not the receiver supports the extended value. + - A suffix of the form "vXYZ" is used for the identifier of each new choice value, e.g. "choice-vXYZ". + +Non-critical extensions at the end of a message/ of a field contained in an OCTET or BIT STRING: + +- When a nonCriticalExtension is actually used, a "Need" code should not be provided for the field, which always is a group including at least one extension and a field facilitating further possible extensions. For simplicity, it is recommended not to provide a "Need" code when the field is not actually used either. + +Further, more general, guidelines: + +- In case a need code is not provided for a group, a "Need" code is provided for all individual extension fields within the group i.e. including for fields that are not marked as OPTIONAL. The latter is to clarify the action upon absence of the whole group. + +#### A.4.3.3 Typical example of evolution of IE with local extensions + +The following example illustrates the use of the extension marker for a number of elementary cases (sequence, enumerated, choice). The example also illustrates how the IE may be revised in case the critical extension mechanism is used. + +**NOTE** In case there is a need to support further extensions of release n while the ASN.1 of release (n+1) has been frozen, without requiring the release n receiver to support decoding of release (n+1) extensions, more advanced mechanisms are needed e.g. including multiple extension markers. + +``` +-- /example/ ASN1START + +InformationElement1 ::= + field1 + field2 + field2a + field2b + SEQUENCE { + ENUMERATED { + value1, value2, value3, value4-v880, + ..., value5-v960 }, + CHOICE { + BOOLEAN, + InformationElement2b, +``` + +``` + + .... + field2c-v960 InformationElement2c-r9 + }, + ... + [[ + field3-r9 InformationElement3-r9 OPTIONAL -- Need R + ]], + [[ + field3-v9a0 InformationElement3-v9a0 OPTIONAL, -- Need R + field4-r9 InformationElement4 OPTIONAL -- Need R + ]] +} + +InformationElement1-r10 ::= + field1 SEQUENCE { + value1, value2, value3, value4-v880, + value5-v960, value6-v1170, spare2, spare1, ... }, + field2 CHOICE { + field2a BOOLEAN, + field2b InformationElement2b, + field2c-v960 InformationElement2c-r9, + .... + field2d-v12b0 INTEGER (0..63) + }, + field3-r9 InformationElement3-r10 OPTIONAL, -- Need R + field4-r9 InformationElement4 OPTIONAL, -- Need R + field5-r10 BOOLEAN, + field6-r10 InformationElement6-r10 OPTIONAL, -- Need R + ... + [[ + field3-v1170 InformationElement3-v1170 OPTIONAL -- Need R + ]] +} + +-- ASN1STOP + +``` + +Some remarks regarding the extensions of *InformationElement1* as shown in the above example: + +- The *InformationElement1* is initially extended with a number of non-critical extensions. In release 10 however, a critical extension is introduced for the message using this IE. Consequently, a new version of the IE *InformationElement1* (i.e. *InformationElement1-r10*) is defined in which the earlier non-critical extensions are incorporated by means of a revision of the original field. +- The *value4-v880* is replacing a spare value defined in the original protocol version for *field1*. Likewise *value6-v1170* replaces *spare3* that was originally defined in the r10 version of *field1*. +- Within the critically extended release 10 version of *InformationElement1*, the names of the original fields/IEs are not changed, unless there is a real need to distinguish them from other fields/IEs. E.g. the *field1* and *InformationElement4* were defined in the original protocol version (release 8) and hence not tagged. Moreover, the *field3-r9* is introduced in release 9 and not re-tagged; although, the *InformationElement3* is also critically extended and therefore tagged *InformationElement3-r10* in the release 10 version of *InformationElement1*. + +#### A.4.3.4 Typical examples of non critical extension at the end of a message + +The following example illustrates the use of non-critical extensions at the end of the message or at the end of a field that is contained in a BIT or OCTET STRING i.e. when an empty sequence is used. + +``` +-- /example/ ASN1START +RRMessage-r8-IEs ::= SEQUENCE { + field1 InformationElement1, + field2 InformationElement2, + field3 InformationElement3 OPTIONAL, -- Need N + nonCriticalExtension RRMessage-v860-IEs OPTIONAL +} + +RRMessage-v860-IEs ::= SEQUENCE { + field4-v860 InformationElement4 OPTIONAL, -- Need S + field5-v860 BOOLEAN OPTIONAL, -- Cond C54 + nonCriticalExtension RRMessage-v940-IEs OPTIONAL +} + +RRMessage-v940-IEs ::= SEQUENCE { + field6-v940 InformationElement6-r9 OPTIONAL, -- Need R + nonCriticalExtensions SEQUENCE {} OPTIONAL +} + +-- ASN1STOP +``` + +Some remarks regarding the extensions shown in the above example: + +- The *InformationElement4* is introduced in the original version of the protocol (release 8) and hence no suffix is used. + +#### A.4.3.5 Examples of non-critical extensions not placed at the default extension location + +The following example illustrates the use of non-critical extensions in case an extension is not placed at the default extension location. + +##### – ***ParentIE-WithEM*** + +The IE *ParentIE-WithEM* is an example of a high level IE including the extension marker (EM). The root encoding of this IE includes two lower level IEs *ChildIE1-WithoutEM* and *ChildIE2-WithoutEM* which not include the extension marker. Consequently, non-critical extensions of the Child-IEs have to be included at the level of the Parent-IE. + +The example illustrates how the two extension IEs *ChildIE1-WithoutEM-vNx0* and *ChildIE2-WithoutEM-vNx0* (both in release N) are used to connect non-critical extensions with a default extension location in the lower level IEs to the actual extension location in this IE. + +##### ***ParentIE-WithEM* information element** + +``` +-- /example/ ASN1START +``` + +``` + +ParentIE-WithEM ::= SEQUENCE { + -- Root encoding, including: + childIE1-WithoutEM ChildIE1-WithoutEM OPTIONAL, -- Need N + childIE2-WithoutEM ChildIE2-WithoutEM OPTIONAL, -- Need N + ... + [[ + childIE1-WithoutEM-vNx0 ChildIE1-WithoutEM-vNx0 OPTIONAL, -- Need N + childIE2-WithoutEM-vNx0 ChildIE2-WithoutEM-vNx0 OPTIONAL -- Need N + ]] +} + +-- ASN1STOP + +``` + +Some remarks regarding the extensions shown in the above example: + +- The fields *childIE-WithoutEM-vNx0* may not really need to be optional (depends on what is defined at the next lower level). +- In general, especially when there are several nesting levels, fields should be marked as optional only when there is a clear reason. +- ***ChildIE1-WithoutEM*** + +The IE *ChildIE1-WithoutEM* is an example of a lower level IE, used to control certain radio configurations including a configurable feature which can be setup or released using the local IE *ChIE1-ConfigurableFeature*. The example illustrates how the new field *chIE1-NewField* is added in release N to the configuration of the configurable feature. The example is based on the following assumptions: + +- When initially configuring as well as when modifying the new field, the original fields of the configurable feature have to be provided also i.e. as if the extended ones were present within the setup branch of this feature. +- When the configurable feature is released, the new field should be released also. +- When omitting the original fields of the configurable feature the UE continues using the existing values (which is used to optimise the signalling for features that typically continue unchanged upon handover). +- When omitting the new field of the configurable feature the UE releases the existing values and discontinues the associated functionality (which may be used to support release of unsupported functionality upon handover to an eNB supporting an earlier protocol version). + +The above assumptions, which affect the use of conditions and need codes, may not always apply. Hence, the example should not be re-used blindly. + +##### ***ChildIE1-WithoutEM* information element** + +``` + +-- /example/ ASN1START + +ChildIE1-WithoutEM ::= SEQUENCE { + -- Root encoding, including: + chIE1-ConfigurableFeature ChIE1-ConfigurableFeature OPTIONAL -- Need N +} + +``` + +``` + +ChildIE1-WithoutEM-vNx0 ::= SEQUENCE { + chIE1-ConfigurableFeature-vNx0 CHIE1-ConfigurableFeature-vNx0 OPTIONAL -- Cond ConfigF +} + +CHIE1-ConfigurableFeature ::= CHOICE { + release NULL, + setup SEQUENCE { + -- Root encoding + } +} + +CHIE1-ConfigurableFeature-vNx0 ::= SEQUENCE { + chIE1-NewField-rN INTEGER (0..31) +} + +-- ASN1STOP + +``` + +| Conditional presence | Explanation | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ConfigF | The field is optional present, need R, in case of chIE1-ConfigurableFeature is included and set to "setup"; otherwise the field is absent and the UE shall delete any existing value for this field. | + +##### — *ChildIE2-WithoutEM* + +The IE *ChildIE2-WithoutEM* is an example of a lower level IE, typically used to control certain radio configurations. The example illustrates how the new field *chIE1-NewField* is added in release N to the configuration of the configurable feature. + +##### *ChildIE2-WithoutEM* information element + +``` + +-- /example/ ASN1START + +ChildIE2-WithoutEM ::= CHOICE { + release NULL, + setup SEQUENCE { + -- Root encoding + } +} + +ChildIE2-WithoutEM-vNx0 ::= SEQUENCE { + chIE2-NewField-rN INTEGER (0..31) OPTIONAL -- Cond ConfigF +} + +-- ASN1STOP + +``` + +| Conditional presence | Explanation | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ConfigF | The field is optional present, need R, in case of chIE2-ConfigurableFeature is included and set to "setup"; otherwise the field is absent and the UE shall delete any existing value for this field. | + +#### A.4.3.6 Non-critical extensions of lists with ToAddMod/ToRelease + +When the size of a list using the ToAddMod/ToRelease construction is extended and/or fields are added to the list element structure, the list should be non-critically extended in accordance with the following general principles: + +- When only the size of the list is extended, this extension is reflected in a non-critical extension of the list, with a "SizeExt" suffix added to the end of the field name (before the -vNxy suffix). The differential size of the extended list uses the suffix "Diff". A new ToRelease list is needed, and its range should include only the increase in list size. In many cases, extending the list size will also require an extended list element ID type to account for the increased size of the list; in these cases the element type will need to be extended to include the extended element ID, resulting in a more complex extension (see example 3 for further discussion of this case). The field description table should indicate that the UE considers the original list and the extension list as a single list; thus entries added with the original list can be modified by the extension list (or removed by the extension of the ToRelease list), or vice versa. The result is as shown in the following example: + +``` +-- /example 1/ ASN1START +ContainingStructure ::= + SEQUENCE { + listElementToAddModList SEQUENCE (SIZE (1..maxNrofListElements)) OF ListElement OPTIONAL, -- Need N + listElementToReleaseList SEQUENCE (SIZE (1..maxNrofListElements)) OF ListElementId OPTIONAL, -- Need N + ... + [[ + -- Non-critical extension lists + listElementToAddModListSizeExt-vNxy SEQUENCE (SIZE (1..maxNrofListElementsDiff-rN)) OF ListElement OPTIONAL, -- Need N + listElementToReleaseListSizeExt-vNxy SEQUENCE (SIZE (1..maxNrofListElementsDiff-rN)) OF ListElementId OPTIONAL -- Need N + ]] + } +-- ASN1STOP +``` + +- When fields are added to the list element structure, an extension marker should normally be used if available. If no extension marker is available or if overhead or other considerations prevent using the extension marker, an extension structure should be created for the new fields, with the suffix "Ext" added to the end of the field name and the element structure type name (before the -vNxy suffix), and a parallel ToAddMod list introduced to hold the new structures, also with the "Ext" suffix. The field description table should indicate that the parallel list contains the same number of entries, and in the same order, as the original list. No new ToRelease list is typically needed (unless the list element ID type changes). It should typically be ensured that the contained fields in the "Ext" elements are releasable without release and add of the entire list element; this can, for instance, be ensured by having the new fields be OPTIONAL Need R. If multiple extensions of the same list are needed, the version suffix should distinguish the lists (e.g. *listElementToAddModListExt-vNwz* added after *listElementToAddModListExt-vNxy*). The result is as shown in the following example: + +``` +-- /example 2/ ASN1START +ContainingStructure ::= + SEQUENCE { + listElementToAddModList SEQUENCE (SIZE (1..maxNrofListElements)) OF ListElement OPTIONAL, -- Need N + } +-- ASN1STOP +``` + +``` + +listElementToReleaseList SEQUENCE (SIZE (1..maxNrofListElements)) OF ListElementId OPTIONAL, -- Need N +... +[[ +-- Parallel list +listElementToAddModListExt-vNx SEQUENCE (SIZE (1..maxNrofListElements)) OF ListElementExt-vNx OPTIONAL -- Need N +]], +[[ +-- Second parallel list from a later spec version +listElementToAddModListExt-vNw SEQUENCE (SIZE (1..maxNrofListElements)) OF ListElementExt-vNw OPTIONAL -- Need N +]] +} + +ListElement ::= + elementId ListElementId, + field1 INTEGER (0..3), + field2 ENUMERATED { value1, value2, value3 } +} + +ListElementExt-vNx ::= + field3-rN BIT STRING (SIZE (8)) OPTIONAL -- Need R +} + +ListElementExt-vNw ::= + field4-rN INTEGER (0..255) OPTIONAL -- Need R +} + +-- ASN1STOP + +``` + +- When the size of a list is extended and fields are added to the list element structure, an extension marker should normally be used for the added fields if available, and the list extended with the non-critical mechanism as described in example 1 above. Note that if the list element ID type changes in this case, the new ID can be added after the extension marker, and the entries of the size-extended ToRelease list should have the type of the new ID (e.g. *ListElementId-vNx*). If no extension marker is available or if overhead or other considerations prevent using the extension marker, an extension structure should be created for the new fields and a parallel list with ToAddMod introduced to hold the extension structures, as in the second example above, for entries of the original list and for entries of the extension list holding new entries. The field description table should indicate that the parallel list contains the same number of entries, and in the same order, as the concatenation of the original list and the extension list. An extended ToRelease list is needed, but no additional parallel ToRelease list is needed (i.e. there is no *listElementToReleaseListExt-vNx* in the example below), as the original and extended ToRelease lists suffice to release any element of the combined list. The extended element ID type should be captured as a non-critical extension of the original element ID type, with the field description indicating that if the extended ID is present, the original ID is ignored. The result is as shown in the following example: + +``` + +-- /example 3/ ASN1START + +ContainingStructure ::= + listElementToAddModList SEQUENCE (SIZE (1..maxNrofListElements)) OF ListElement OPTIONAL, -- Need N + listElementToReleaseList SEQUENCE (SIZE (1..maxNrofListElements)) OF ListElementId OPTIONAL, -- Need N + ... + [[ + -- Non-critical extension lists + listElementToAddModListSizeExt-vNx SEQUENCE (SIZE (1..maxNrofListElementsDiff-rN)) OF ListElement OPTIONAL, -- Need N + listElementToReleaseListSizeExt-vNx SEQUENCE (SIZE (1..maxNrofListElementsDiff-rN)) OF ListElementId-vNx OPTIONAL, -- Need N + -- Parallel list with maxNrofListElements-rN = maxNrofListElements + maxNrofListElementsDiff-rN + +``` + +``` + +listElementToAddModListExt-vNxy SEQUENCE (SIZE (1..maxNrofListElements-rN)) OF ListElementExt-vNxy OPTIONAL -- Need N +]] +} + +ListElement ::= SEQUENCE { + elementId ListElementId, + field1 INTEGER (0..3), + field2 ENUMERATED { value1, value2, value3 } +} + +ListElementExt-vNxy ::= SEQUENCE { + -- Field description should indicate that if the elementId-vNxy is present, the elementId (without suffix) is ignored + elementId-vNxy ListElementId-vNxy OPTIONAL, -- Need S + field3-rN BIT STRING (SIZE (8)) OPTIONAL -- Need R +} + +ListElementId ::= INTEGER (0..maxNrofListElements-1) + +ListElementId-vNxy ::= INTEGER (maxNrofListElements..maxNrofListElements-1-rN) +-- ASN1STOP + +``` + +- When different extensions are made to a list in separate releases, the extension mechanisms described above may interact. In case fields are added in Rel-M (*listElementToAddModListExt-vMxy*) and later the list size is extended in Rel-N (*listElementToAddModListSizeExt-vNwz*), the size-extended list in Rel-N should be a single list extending the combination of *listElementToAddModList* and *listElementToAddModListExt-vMxy*. This requires creating a new type (*ListElement-rN*) to contain the combined fields of *ListElement* and *ListElementExt-vMxy*. A corresponding ToRelease list is needed. The result is as shown in the following example: + +``` + +-- /example 4/ ASN1START + +ContainingStructure ::= SEQUENCE { + listElementToAddModList SEQUENCE (SIZE (1..maxNrofListElements)) OF ListElement OPTIONAL, -- Need N + listElementToReleaseList SEQUENCE (SIZE (1..maxNrofListElements)) OF ListElementId OPTIONAL, -- Need N + ..., + [[ + -- Parallel list (Rel-M) + listElementToAddModListExt-vMxy SEQUENCE (SIZE (1..maxNrofListElements)) OF ListElementExt-vMxy OPTIONAL -- Need N + ]], + [[ + -- Size-extended list (Rel-N) with maxNrofListElements-rN = maxNrofListElements + maxNrofListElementsDiff-rN + listElementToAddModListSizeExt-vNwz SEQUENCE (SIZE (1..maxNrofListElementsDiff-rN)) OF ListElement-rN OPTIONAL, -- Need N + listElementToReleaseListSizeExt-vNwz SEQUENCE (SIZE (1..maxNrofListElementsDiff-rN)) OF ListElementId-vNwz OPTIONAL -- Need N + ]] +} + +ListElement ::= SEQUENCE { + elementId ListElementId, + field1 INTEGER (0..3), + field2 ENUMERATED { value1, value2, value3 } +} + +ListElementExt-vMxy ::= SEQUENCE { + +``` + +``` + + field3-rM BIT STRING (SIZE (8)) OPTIONAL -- Need R +} + +ListElement-rN := SEQUENCE { + elementId-vNwz ListElementId-vNwz, + field1 INTEGER (0..3), + field2 ENUMERATED { value1, value2, value3 }, + field3-rN BIT STRING (SIZE (8)) OPTIONAL -- Need R +} + +ListElementId := INTEGER (0..maxNrofListElements-1) + +ListElementId-vNwz := INTEGER (maxNrofListElements..maxNrofListElementsDiff-1-rN) +-- ASN1STOP + +``` + +## A.5 Guidelines regarding inclusion of transaction identifiers in RRC messages + +The following rules provide guidance on which messages should include a Transaction identifier + +- 1: DL messages on CCCH that move UE to RRC-Idle should not include the RRC transaction identifier. +- 2: All network initiated DL messages by default should include the RRC transaction identifier. +- 3: All UL messages that are direct response to a DL message with an RRC Transaction identifier should include the RRC Transaction identifier. +- 4: All UL messages that require a direct DL response message should include an RRC transaction identifier. +- 5: All UL messages that are not in response to a DL message nor require a corresponding response from the network should not include the RRC Transaction identifier. + +## A.6 Guidelines regarding use of need codes + +The following rule provides guidance for determining need codes for optional downlink fields: + +- if the field needs to be stored by the UE (i.e. maintained) when absent: + - use Need M (=Maintain); +- else, if the field needs to be released by the UE when absent: + - use Need R (=Release); +- else, if UE shall take no action when the field is absent (i.e. UE does not even need to maintain any existing value of the field): + - use Need N (=None); + +- else (UE behaviour upon absence does not fit any of the above conditions): + - use Need S (=Specified); + - specify the UE behaviour upon absence of the field in the procedural text or in the field description table. + +## A.7 Guidelines regarding use of conditions + +Conditions are primarily used to specify network restrictions, for which the following types can be distinguished: + +- Message Contents related constraints e.g. that a field B is mandatory present if the same message includes field A and when it is set value X. +- Configuration Constraints e.g. that a field D can only be signalled if field C is configured and set to value Y. (i.e. regardless of whether field C is present in the same message or previously configured). + +The use of these conditions is illustrated by an example. + +``` +-- /example/ ASN1START +RRCMessage-IEs ::= SEQUENCE { + fieldA FieldA OPTIONAL, -- Need M + fieldB FieldB OPTIONAL, -- Cond FieldAsetToX + fieldC FieldC OPTIONAL, -- Need M + fieldD FieldD OPTIONAL, -- Cond FieldCsetToY + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +-- /example/ ASN1STOP +``` + +| Conditional presence | Explanation | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| FieldAsetToX | The field is mandatory present if fieldA is included and set to valueX. Otherwise the field is optionally present, need R. | +| FieldCsetToY | The field is optionally present, need M, if fieldC is configured and set to valueY. Otherwise the field is absent and the UE does not maintain the value | + +## A.8 Miscellaneous + +The following miscellaneous convention should be used: + +- UE capabilities: TS 38.306 [26] specifies that the network should in general respect the UE's capabilities. Hence there is no need to include statement clarifying that the network, when setting the value of a certain configuration field, shall respect the related UE capabilities unless there is a particular need e.g. particularly complicated cases. + +# --- Annex B (informative): RRC Information + +## B.1 Protection of RRC messages + +The following list provides information which messages can be sent (unprotected) prior to AS security activation and which messages can be sent unprotected after AS security activation. Those messages indicated "-" in "P" column should never be sent unprotected by gNB or UE. Further requirements are defined in the procedural text. + +P...Messages that can be sent (unprotected) prior to AS security activation + +A – I...Messages that can be sent without integrity protection after AS security activation + +A – C...Messages that can be sent unciphered after AS security activation + +NA... Message can never be sent after AS security activation + +| Message | P | A-I | A-C | Comment | +|--------------------------------------|--------|-----|-----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CounterCheck | - | - | - | | +| CounterCheckResponse | - | - | - | | +| DedicatedSIBRequest | + | - | - | | +| DLDedicatedMessageSegment | NOTE 1 | | | | +| DLInformationTransfer | + | - | - | | +| DLInformationTransferMRDC | - | - | - | | +| FailureInformation | - | - | - | | +| LocationMeasurementIndication | - | - | - | | +| MCGFailureInformation | - | - | - | | +| MeasurementReportAppLayer | - | - | - | | +| MBSBroadcastConfiguration | + | + | + | | +| MBSInterestIndication | - | - | - | | +| MIB | + | + | + | | +| MeasurementReport | - | - | - | Measurement configuration may be sent prior to AS security activation. But: In order to protect privacy of UEs, MeasurementReport is only sent from the UE after successful AS security activation. | +| MobilityFromNRCommand | - | - | - | | +| Paging | + | + | + | | +| RRCReconfiguration | + | - | - | The message shall not be sent unprotected before AS security activation if it is used to perform handover or to establish SRB2, SRB4, multicast MRBs and DRBs. | +| RRCReconfigurationComplete | + | - | - | Unprotected, if sent as response to RRCReconfiguration which was sent before AS security activation. | +| RRCReestablishment | - | - | + | Integrity protection applied, but no ciphering. | +| RRCReestablishmentComplete | - | - | - | | +| RRCReestablishmentRequest | - | - | + | This message is not protected by PDCP operation. However, a shortMAC-I is included. | +| RRcreject | + | + | + | Justification for A-I and A-C: the message can be sent in SRB0 in RRC_INACTIVE state, after the AS security is activated. | +| RRcrelease | + | - | - | Justification for P: If the RRC connection only for signalling not requiring DRBs or ciphered messages, or the signalling connection has to be released prematurely, this message is sent as unprotected. RRcrelease message sent before AS security activation cannot include deprioritisationReq , suspendConfig , redirectedCarrierInfo , cellReselectionPriorities information fields. | +| RRcresume | - | - | - | | +| RRcresumeComplete | - | - | - | | +| RRcresumeRequest | - | - | + | This message is not protected by PDCP operation. However, a resumeMAC-I is included. | +| RRcresumeRequest1 | - | - | + | This message is not protected by PDCP operation. However, a resumeMAC-I is included. | +| RRcSetup | + | + | + | Justification for A-I and A-C: the message can be sent in SRB0 in RRC_INACTIVE or RRC_CONNECTED states, after the AS security is activated. | +| RRcSetupComplete | + | NA | NA | | +| RRcSetupRequest | + | NA | NA | | +| RRcSystemInfoRequest | + | + | + | Justification for A-I and A-C: the message can be sent in SRB0 in RRC_INACTIVE state, after the AS security is activated. | +| SIB1 | + | + | + | | +| SCGFailureInformation | - | - | - | | +| SCGFailureInformationEUTRA | - | - | - | | + +| Message | P | A-I | A-C | Comment | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|-----|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SecurityModeCommand | + | NA | NA | Integrity protection applied, but no ciphering (integrity verification done after the message received by RRC). | +| SecurityModeComplete | - | - | + | The message is sent after AS security activation. Integrity protection applied, but no ciphering. Ciphering is applied after completing the procedure. | +| SecurityModeFailure | + | NA | NA | Neither integrity protection nor ciphering applied. | +| SidelinkUEInformationNR | + | - | - | The message shall not be sent unprotected before AS security activation if sl-CapabilityInformationSidelink information field is included in the message. | +| SystemInformation | + | + | + | | +| UEAssistanceInformation | - | - | - | | +| UECapabilityEnquiry | + | - | - | The network should retrieve UE capabilities only after AS security activation. | +| UECapabilityInformation | + | - | - | | +| ULDedicatedMessageSegment | NOTE 1 | | | | +| UEInformationRequest | - | - | - | | +| UEInformationResponse | - | - | - | In order to protect privacy of UEs, UEInformationResponse is only sent from the UE after successful security activation | +| UEPositioningAssistanceInfo | - | - | - | | +| ULInformationTransfer | + | - | - | | +| ULInformationTransferRAT | NOTE 2 | | | | +| ULInformationTransferMRDC | - | - | - | | +| NOTE 1: This message type carries segments of other RRC messages. The protection of an instance of this message is the same as for the message which this message is carrying. | | | | | +| NOTE 2: This message type carries others RRC messages. The protection of an instance of this message is the same as for the message which this message is carrying. | | | | | + +## B.2 Description of BWP configuration options + +There are two possible ways to configure BWP#0 (i.e. the initial BWP) for a UE: + +- 1) Configure *BWP-DownlinkCommon* and *BWP-UplinkCommon* in *ServingCellConfigCommon*, but do not configure dedicated configurations in *BWP-DownlinkDedicated* or *BWP-UplinkDedicated* in *ServingCellConfig*. +- 2) Configure both *BWP-DownlinkCommon* and *BWP-UplinkCommon* in *ServingCellConfigCommon* and configure dedicated configurations in at least one of *BWP-DownlinkDedicated* or *BWP-UplinkDedicated* in *ServingCellConfig*. + +The same way of configuration is used for UL BWP#0 and DL BWP#0 if both are configured. + +With the first option (illustrated by figure B2-1 below), the BWP#0 is not considered to be an RRC-configured BWP, i.e., UE only supporting one BWP can still be configured with BWP#1 in addition to BWP#0 when using this configuration. The BWP#0 can still be used even if it does not have the dedicated configuration, albeit in a more limited manner since only the SIB1-defined configurations are available. For example, only DCI format 1\_0 can be used with BWP#0 without dedicated configuration, so changing to another BWP requires RRCReconfiguration since DCI format 1\_0 doesn't support DCI-based switching. + +![Diagram of BWP configuration option #1. It shows three boxes representing different bandwidth parts (BWPs). The first box, labeled 'BWP#0', is a 'ServingCellConfigCommon' box containing 'BWP-DownlinkCommon' and 'BWP-UplinkCommon'. The second box, labeled 'BWP#1', is a 'ServingCellConfig' box containing 'BWP-Downlink' and 'BWP-Uplink'. An ellipsis indicates more boxes, with a note '(Max 4 BWPs)'. The third box, labeled 'BWP#4', is also a 'ServingCellConfig' box containing 'BWP-Downlink' and 'BWP-Uplink'. To the left of the boxes is the text 'BWP configuration option #1 (1 or more BWPs)'.](1ab8da167ae10f58b4b0b57e0c1283ad_img.jpg) + +Diagram of BWP configuration option #1. It shows three boxes representing different bandwidth parts (BWPs). The first box, labeled 'BWP#0', is a 'ServingCellConfigCommon' box containing 'BWP-DownlinkCommon' and 'BWP-UplinkCommon'. The second box, labeled 'BWP#1', is a 'ServingCellConfig' box containing 'BWP-Downlink' and 'BWP-Uplink'. An ellipsis indicates more boxes, with a note '(Max 4 BWPs)'. The third box, labeled 'BWP#4', is also a 'ServingCellConfig' box containing 'BWP-Downlink' and 'BWP-Uplink'. To the left of the boxes is the text 'BWP configuration option #1 (1 or more BWPs)'. + +**Figure B2-1: BWP#0 configuration without dedicated configuration** + +With the second option (illustrated by figure B2-2 below), the BWP#0 is considered to be an RRC-configured BWP, i.e. UE only supporting one BWP cannot be configured with BWP#1 in addition to BWP#0 when using this configuration. However, UE supporting more than one BWP can still switch to and from BWP#0 e.g. via DCI normally, and there are no explicit limitations to using the BWP#0 (compared to the first option). + +![Diagram of BWP configuration option #2. It shows three boxes representing different bandwidth parts (BWPs). The first box, labeled 'BWP#0', is a 'ServingCellConfigCommon' box containing 'BWP-DownlinkCommon' and 'BWP-UplinkCommon', and also contains a 'ServingCellConfig' box containing 'BWP-DownlinkDedicated' and 'BWP-UplinkDedicated'. The second box, labeled 'BWP#1', is a 'ServingCellConfig' box containing 'BWP-Downlink' and 'BWP-Uplink'. An ellipsis indicates more boxes, with a note '(Max 3 BWPs)'. The third box, labeled 'BWP#3', is also a 'ServingCellConfig' box containing 'BWP-Downlink' and 'BWP-Uplink'. To the left of the boxes is the text 'BWP configuration option #2 (1 or more BWPs)'.](9ef15a4afab1416db28b91184862a3a5_img.jpg) + +Diagram of BWP configuration option #2. It shows three boxes representing different bandwidth parts (BWPs). The first box, labeled 'BWP#0', is a 'ServingCellConfigCommon' box containing 'BWP-DownlinkCommon' and 'BWP-UplinkCommon', and also contains a 'ServingCellConfig' box containing 'BWP-DownlinkDedicated' and 'BWP-UplinkDedicated'. The second box, labeled 'BWP#1', is a 'ServingCellConfig' box containing 'BWP-Downlink' and 'BWP-Uplink'. An ellipsis indicates more boxes, with a note '(Max 3 BWPs)'. The third box, labeled 'BWP#3', is also a 'ServingCellConfig' box containing 'BWP-Downlink' and 'BWP-Uplink'. To the left of the boxes is the text 'BWP configuration option #2 (1 or more BWPs)'. + +**Figure B2-2: BWP#0 configuration with dedicated configuration** + +For BWP#0, the *BWP-DownlinkCommon* and *BWP-UplinkCommon* in *ServingCellConfigCommon* should match the parameters configured by MIB and SIB1 (if provided) in the corresponding serving cell. + +If an (e)RedCap-specific initial DL BWP is configured, for BWP switching, the BWP #0 always maps to the (e)RedCap-specific initial DL BWP. If a RedCap-specific initial UL BWP is configured, for BWP switching on NUL, the BWP #0 always maps to the RedCap-specific initial UL BWP, for BWP switching on SUL, the BWP#0 always maps to the initial UL BWP. + +# --- Annex C (normative):List of CRs Containing Early Implementable Features and Corrections + +This annex lists the Change Requests (CRs) whose changes may be implemented by a UE of an earlier release than which the CR was approved in (i.e. CRs that contain on their coversheets the sentence "Implementation of this CR from Rel-N will not cause interoperability issues"). + +**Table C-1: List of CRs Containing Early Implementable Features and Corrections** + +| TDoc Number (RP-xxxxx): CR Title | CR Number(s) | CR Revision Number(s) | Earliest Implementable Release | Additional Information | +|-----------------------------------------------------------------------------------|---------------------|------------------------------|---------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RP-200335: Correction on usage of access category 2 for UAC for RNA update | 1141 | 2 | Release 15 | | +| RP-201185: Introduction of signalling for high-speed train scenarios | 1464 | 5 | Release 15 | | +| RP-201216: Release-16 UE capabilities based on RAN1, RAN4 feature lists and RAN2 | 1665 | 2 | Release 15 | Early implementation part is referring to the aspect covered by
- R2-2006203: Extension of CSI-RS capabilities per codebook type
- R2-2006360: Intraband EN_DC power class expansion for 29 dBm | +| RP-202768: UE behaviour when UL 7.5KHz shift is not supported | 2107 | 2 | Release 15 | | +| RP-202790: Correction on uac-AccessCategory1-SelectionAssistanceInfo | 2130 | 1 | Release 15 | | +| RP-211483: Clarification on the initiation of RNA update | 2581 | 1 | Release 15 | | +| RP-201190: Introduction of eCall over IMS for NR | 1670 | - | Release 15 | | +| RP-212598: Distinguishing support of extended band n77 | 2810 | 2 | Release 15 | | +| RP-213342: Duty cycle signalling for power class 1.5 | 2817 | 1 | Release 15 | | +| RP-213345: CR on 38.331 for introducing UE capability of txDiversity | 2859 | 1 | Release 15 | | +| RP-220497: Introduction of function for RRM enhancements for Rel-17 NR FR1 HST | 2898 | 2 | Release 16 | | +| RP-220838: Release-17 UE capabilities based on R1 and R4 feature lists (TS38.331) | 2901 | 1 | Release 15 | Early implementation part is referring to the aspect covered by:
- R2-2203898: Introduction of BCS4 and BCS5
- R2-2203836: Introducing UE capability for power class 5 for FR2 FWA | +| RP-221721: CR on the CBM/IBM reporting-38331 | 2916 | 2 | Release 16 | | +| RP-221736: Distinguishing support of band n77 restrictions in Canada | 3078 | 2 | Release 15 | | + +| | | | | | +|------------------------------------------------------------------------------------------------------------------|------|---|------------|--| +| [n77 Canada] | | | | | +| RP-222527: Correction to additionalSpectrumEmission for UL CA in n77 for the US | 3476 | - | Release 15 | | +| RP-222527: Correction to additionalSpectrumEmission for UL CA in n77 for Canada | 3478 | - | Release 15 | | +| RP-232570: Addition of extended number range for NS value | 3900 | 6 | Release 16 | | +| RP-233888: Introduction of FR2 FBG2 CA BW classes | 2867 | 6 | Release 15 | | +| RP-233882: Enhancing SCell A2 event reporting | 4375 | 2 | Release 15 | | +| RP-233890: PTM retransmission reception for multicast DRX with HARQ feedback disabled [PTM_ReTx_Mcast_HARQ_Disb] | 4504 | - | Release 17 | | + +# Annex D (normative): UE requirements on ASN.1 comprehension + +This clause specifies UE requirements regarding the ASN.1 transfer syntax support, i.e. the ASN.1 definitions to be comprehended by the UE. + +A UE that indicates release X in field *accessStratumRelease* shall comprehend the entire transfer syntax (ASN.1) of release X, in particular at least the first version upon ASN.1 freeze. The UE is however not required to support dedicated signalling related transfer syntax associated with optional features it does not support. + +In case a UE that indicates release X in field *accessStratumRelease* supports a feature specified in release Y, which is later than release X, (i.e. early UE implementation) additional requirements apply. The UE obviously also has to support the ASN.1 parts related to indicating support of the feature (in UE capabilities). + +## Critical extensions (dedicated signaling) + +If the early implemented feature involves one or more critical extensions in dedicated signalling, the UE shall comprehend the parts of the transfer syntax (ASN.1) of release Y that are related to the feature implemented early. This, in particular, concerns the ASN.1 parts related to configuration of the feature. + +If configuration of an early implemented feature introduced in release Y involves a message or field that has been critically extended, the UE shall support configuration of all features supported by the UE that are associated with sub-fields of this critical extension. Apart from the early implemented feature(s), the UE needs, however, not to support functionality beyond what is defined in the release the UE indicates in access stratum release. + +Let's consider the example of a UE indicating value X in field *accessStratumRelease* that supports the features A1, A3, and A5, associated with fields *fieldA1*, *fieldA3* and *fieldA5* of *InformationElementA* (see ASN.1 below). + +The feature A5 implemented early is associated with *fieldA5*, and can only be configured by the -rY version of *InformationElementA*. In such case, the UE should support configuration of all the features A1, A3 and A5 associated with fields *fieldA1*, *fieldA3* and *fieldA5* by the -rY version of *InformationElementA*. + +If, however, one of the features was modified, e.g. the feature A3 associated with *fieldA3*, the network should assume the UE only supports the feature A3 according to the release it indicated in field *accessStratumRelease* (i.e. X). + +The UE is neither required to support the additional code-point (*n80-vY0*) nor the additional sub-field (*fieldA3c-rY*). + +``` +InformationElementA-rX ::= SEQUENCE { + fieldA1-rX InformationElementA1-rX OPTIONAL, -- Need N + fieldA2-rX InformationElementA2-rX OPTIONAL, -- Need R + fieldA3-rX InformationElementA3-rX OPTIONAL -- Need R +} + +InformationElementA-rY ::= SEQUENCE { + fieldA1-rY InformationElementA1-rX OPTIONAL, -- Need N + fieldA2-rY InformationElementA2-rX OPTIONAL, -- Need R + fieldA3-rY InformationElementA3-rY OPTIONAL, -- Need R + fieldA4-rY InformationElementA4-rY OPTIONAL, -- Need R + fieldA5-rY InformationElementA5-rY OPTIONAL -- Need R +} + +InformationElementA3-rX ::= SEQUENCE { + fieldA3a-rX InformationElementA3a-rX OPTIONAL, -- Need N +} +``` + +``` + + fieldA3b-rX ENUMERATED {n10, n20, n40} OPTIONAL -- Need R +} + +InformationElementA3-rY ::= SEQUENCE { + fieldA3a-rY InformationElementA3a-rX OPTIONAL, -- Need N + fieldA3b-rY ENUMERATED {n10, n20, n40, n80-vY0} OPTIONAL, -- Need R + fieldA3c-rY InformationElementA3c-rY OPTIONAL -- Need R +} + +``` + +## Non-critical extensions (dedicated and broadcast signaling) + +If the early implemented feature involves one or more non-critical extensions, the UE shall comprehend the parts of the transfer syntax (ASN.1) of release Y that are related to the feature implemented early. + +If the early implemented feature involves one or more non-critical extensions in dedicated signaling, the network does not include extensions introduced after the release X that are not the parts related to the feature which the UE indicates early support of in UE capabilities. The UE shall anyway comprehend the parts of the transfer syntax (ASN.1) which indicate absence of such extensions. + +If the early implemented feature involves one or more non-critical extensions in system information, the SIB(s) containing the release Y fields related to the early implemented features may also include other extensions introduced after the release X that are not the parts related to the feature which the UE supports. The UE shall comprehend such intermediate fields (but again is not required to support the functionality associated with these intermediate fields, in case this concerns optional features not supported by the UE). + +# Annex E (informative): Change history + +| Change history | | | | | | | | +|----------------|-------------|------------|------|-----|---|---------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | C | Subject/Comment | New version | +| 04/2017 | RAN2#9 7bis | R2-1703395 | | | | | 0.0.1 | +| 04/2017 | RAN2#9 7bis | R2-1703922 | | | | | 0.0.2 | +| 05/2017 | RAN2#9 8 | R2-1705815 | | | | | 0.0.3 | +| 06/2017 | RAN2# NR2 | R2-1707187 | | | | | 0.0.4 | +| 08/2017 | RAN2#9 9 | R2-1708468 | | | | | 0.0.5 | +| 09/2017 | RAN2#9 9bis | R2-1710557 | | | | | 0.1.0 | +| 11/2017 | RAN2#1 00 | R2-1713629 | | | | | 0.2.0 | +| 11/2017 | RAN2#1 00 | R2-1714126 | | | | | 0.3.0 | +| 12/2017 | RAN2#1 00 | R2-1714259 | | | | | 0.4.0 | +| 12/2017 | RP#78 | RP-172570 | | | | Submitted for Approval in RAN#78 | 1.0.0 | +| 12/2017 | RP#78 | | | | | Upgraded to Rel-15 (MCC) | 15.0.0 | +| 03/2018 | RP#79 | RP-180479 | 0008 | 1 | F | Corrections for EN-DC (Note: the clause numbering between 15.0.0 and 15.1.0 has changed in some cases). | 15.1.0 | +| 06/2018 | RP-80 | RP-181326 | 0042 | 7 | F | Miscellaneous EN-DC corrections | 15.2.0 | +| | RP-80 | | | | | Correction: Duplicate Foreword clause removed & ASN.1 clauses touched up | 15.2.1 | +| 09/2018 | RP-81 | RP-181942 | 0100 | 4 | F | Introduction of SA | 15.3.0 | +| 12/2018 | RP-82 | RP-182656 | 0179 | 3 | F | Handling of Resume Failure | 15.4.0 | +| | RP-82 | RP-182651 | 0187 | 1 | F | Clarification on the presence of ra-ResponseWindow | 15.4.0 | +| | RP-82 | RP-182656 | 0188 | 3 | F | Addition of RAN specific Access Category | 15.4.0 | +| | RP-82 | RP-182653 | 0199 | 2 | F | CR for TS38.331 on MIB | 15.4.0 | + +| | | | | | | | | +|--|-------|-----------|------|---|---|---------------------------------------------------------------------------------|--------| +| | RP-82 | RP-182653 | 0200 | 1 | F | CR for TS38.331 on PDCCH-ConfigSIB | 15.4.0 | +| | RP-82 | RP-182661 | 0202 | 2 | F | Handling Cell Reselection during SI Request | 15.4.0 | +| | RP-82 | RP-182649 | 0213 | 2 | F | Corrections on security field descriptions | 15.4.0 | +| | RP-82 | RP-182649 | 0216 | 2 | F | Remain issue for T302 | 15.4.0 | +| | RP-82 | RP-182649 | 0219 | 1 | F | [C204] Handling of timer T380 | 15.4.0 | +| | RP-82 | RP-182655 | 0229 | 2 | F | Clarification on configured grant timer in 38.331 | 15.4.0 | +| | RP-82 | RP-182663 | 0232 | 2 | F | CR for ServingCellConfigCommon in 38.331 | 15.4.0 | +| | RP-82 | RP-182659 | 0234 | 3 | F | Introduction of cell level rate matching parameters in ServingCellConfig | 15.4.0 | +| | RP-82 | RP-182650 | 0235 | 2 | F | CR for introducing PSCell frequency in CG-Config | 15.4.0 | +| | RP-82 | RP-182650 | 0236 | 2 | F | CR for security handling for eLTE in 38.331 | 15.4.0 | +| | RP-82 | RP-182650 | 0237 | 1 | F | Handling on simultaneously triggered NAS&AS events (I770) | 15.4.0 | +| | RP-82 | RP-182650 | 0238 | 2 | F | Handling on security keys for resume procedure (I774) | 15.4.0 | +| | RP-82 | RP-182664 | 0239 | 5 | F | RIL I556, I557, I558 on RB handling when resuming | 15.4.0 | +| | RP-82 | RP-182650 | 0242 | 2 | F | Security for RRC connection release | 15.4.0 | +| | RP-82 | RP-182650 | 0243 | 4 | F | Corrections on reestablishment and security procedures | 15.4.0 | +| | RP-82 | RP-182650 | 0244 | 1 | F | RIL I118 on release case to upper layers for CN paging for a UE in RRC_INACTIVE | 15.4.0 | +| | RP-82 | RP-182650 | 0246 | 2 | F | CR on SI request procedure in TS38.331 | 15.4.0 | +| | RP-82 | RP-182650 | 0248 | 2 | F | CR to 38331 on ul-DataSplitThreshold for SRB | 15.4.0 | +| | RP-82 | RP-182652 | 0249 | 2 | F | Clarification of guami-Type | 15.4.0 | +| | RP-82 | RP-182652 | 0252 | 1 | F | CR to 38.331 on Protection of RRC messages Table | 15.4.0 | +| | RP-82 | RP-182663 | 0254 | 2 | F | Access barring check after handover | 15.4.0 | + +| | | | | | | | | +|--|-------|-----------|------|---|---|--------------------------------------------------------------------------------------------|--------| +| | RP-82 | RP-182663 | 0259 | 3 | F | Stop of T390 and related UE actions | 15.4.0 | +| | RP-82 | RP-182657 | 0260 | 4 | F | Corrections for handover between NR and E-UTRA | 15.4.0 | +| | RP-82 | RP-182738 | 0267 | 3 | F | CR on ssb-ToMeasure in MeasurementTimingConfiguration | 15.4.0 | +| | RP-82 | RP-182659 | 0269 | 3 | F | Clarification of the applicability of 38.331 to EN-DC | 15.4.0 | +| | RP-82 | RP-182654 | 0270 | 3 | F | Clarification on the smtc signalled for intra-NR handover, PSCell change or SCell addition | 15.4.0 | +| | RP-82 | RP-182654 | 0273 | 3 | F | CR on fallback to the setup procedure | 15.4.0 | +| | RP-82 | RP-182654 | 0275 | 1 | F | Correction on cell sorting for periodical measurement reporting | 15.4.0 | +| | RP-82 | RP-182660 | 0277 | 2 | F | Measurement related actions upon re-establishment | 15.4.0 | +| | RP-82 | RP-182654 | 0278 | 1 | F | CR on threshold description for cell quality derivation | 15.4.0 | +| | RP-82 | RP-182654 | 0282 | 1 | F | CR to avoid unnecessary L3 filtered beam measurements | 15.4.0 | +| | RP-82 | RP-182660 | 0283 | 2 | F | CR on CGI reporting | 15.4.0 | +| | RP-82 | RP-182660 | 0291 | 3 | F | Additional UE capabilities for NR standalone | 15.4.0 | +| | RP-82 | RP-182667 | 0294 | 4 | F | NR RRC Processing Time | 15.4.0 | +| | RP-82 | RP-182812 | 0295 | 5 | F | Update of L1/RF capabilities | 15.4.0 | +| | RP-82 | RP-182651 | 0296 | 2 | F | UE configuration on re-establishment procedure | 15.4.0 | +| | RP-82 | RP-182651 | 0298 | 2 | F | SIB size limitation [M201] | 15.4.0 | +| | RP-82 | RP-182651 | 0299 | 2 | F | Correction on SRS-TPC-CommandConfig | 15.4.0 | +| | RP-82 | RP-182651 | 0302 | 2 | F | Clarification on counter check procedure | 15.4.0 | +| | RP-82 | RP-182666 | 0307 | 4 | F | CR on the Clarification for the Support of the Delay Budget Report in NR | 15.4.0 | +| | RP-82 | RP-182666 | 0320 | 3 | F | ssb-PositionsInBurst correction | 15.4.0 | +| | RP-82 | RP-182666 | 0325 | 3 | F | Barring behaviour when SIB1 reception fails | 15.4.0 | + +| | | | | | | | | +|--|-------|-----------|------|---|---|------------------------------------------------------------------------|--------| +| | RP-82 | RP-182666 | 0329 | 5 | F | System Information Storing and Validity Clarifications and Corrections | 15.4.0 | +| | RP-82 | RP-182666 | 0330 | 3 | F | SIBs required before initiating connection | 15.4.0 | +| | RP-82 | RP-182652 | 0333 | 1 | F | On contents of measObjectEUTRA | 15.4.0 | +| | RP-82 | RP-182654 | 0335 | 2 | F | A3 and A5 corrections – neighbouring cell definition | 15.4.0 | +| | RP-82 | RP-182650 | 0339 | 2 | F | SI reception in RRC Connected mode (RIL#11611) | 15.4.0 | +| | RP-82 | RP-182650 | 0340 | 2 | F | Miscellaneous corrections on SI procedures | 15.4.0 | +| | RP-82 | RP-182652 | 0342 | 1 | F | On RRM measurements related procedural text corrections | 15.4.0 | +| | RP-82 | RP-182651 | 0344 | 1 | F | Clarification for absense of nr-NS-PmaxList IE | 15.4.0 | +| | RP-82 | RP-182652 | 0345 | 2 | F | Clarification on paging in connected mode | 15.4.0 | +| | RP-82 | RP-182651 | 0350 | 2 | F | ASN.1 correction to fr-InfoListSCG in CG-Config | 15.4.0 | +| | RP-82 | RP-182661 | 0355 | 2 | F | Update of L2 capability parameters | 15.4.0 | +| | RP-82 | RP-182651 | 0364 | 1 | F | Procedures for full config at RRCResume | 15.4.0 | +| | RP-82 | RP-182651 | 0365 | 2 | F | Clarification of PDCP-Config field descriptions | 15.4.0 | +| | RP-82 | RP-182653 | 0368 | 2 | F | UE Context handling during handover to NR | 15.4.0 | +| | RP-82 | RP-182652 | 0371 | 2 | F | [E255] CR to 38.331 on corrections related to CGI reporting timer T321 | 15.4.0 | +| | RP-82 | RP-182655 | 0375 | 3 | F | R2-1817981 CR to 38.331 on pendingRnaUpdate setting | 15.4.0 | +| | RP-82 | RP-182653 | 0376 | 2 | F | Introducing procedure for reporting RLC failures | 15.4.0 | +| | RP-82 | RP-182654 | 0379 | 2 | F | Correction of frequency band indication in MeasObjectNR | 15.4.0 | +| | RP-82 | RP-182654 | 0382 | 2 | F | RRC connection release triggered by upper layers | 15.4.0 | +| | RP-82 | RP-182660 | 0384 | 3 | F | Correction to configuration of measurement object | 15.4.0 | +| | RP-82 | RP-182665 | 0388 | 3 | F | Correction to 38331 in SRS-Config | 15.4.0 | + +| | | | | | | | | +|--|-------|-----------|------|---|---|----------------------------------------------------------------------------|--------| +| | RP-82 | RP-182657 | 0391 | 2 | F | Correction for PowerControl-related issues | 15.4.0 | +| | RP-82 | RP-182668 | 0395 | 4 | F | Inter-band EN-DC Configured Output Power requirements | 15.4.0 | +| | RP-82 | RP-182655 | 0396 | 2 | F | E573 Configuration of SRB1 during Resume | 15.4.0 | +| | RP-82 | RP-182655 | 0402 | 1 | F | Triggers for abortion of RRC establishment | 15.4.0 | +| | RP-82 | RP-182656 | 0406 | 2 | F | Correction on CN type indication for Redirection from NR to E-UTRA | 15.4.0 | +| | RP-82 | RP-182664 | 0409 | 4 | F | Miscellaneous minor corrections | 15.4.0 | +| | RP-82 | RP-182654 | 0410 | 1 | F | Invalidation of L1 parameter nrofCQIsPerReport | 15.4.0 | +| | RP-82 | RP-182654 | 0411 | 1 | F | Clarifications on RNA update and CN registration (N023) | 15.4.0 | +| | RP-82 | RP-182666 | 0412 | 3 | F | Missing optionality bit in CG-ConfigInfo | 15.4.0 | +| | RP-82 | RP-182662 | 0414 | 2 | F | Clarification for the implementation of UE feature list item 6-1 (BWP op1) | 15.4.0 | +| | RP-82 | RP-182654 | 0417 | 1 | F | Clarification on ssb-PositionsInBurst | 15.4.0 | +| | RP-82 | RP-182667 | 0418 | 3 | F | Correction to commonControlResourceSet | 15.4.0 | +| | RP-82 | RP-182667 | 0420 | 2 | F | Correction to TDD configuration in SIB1 | 15.4.0 | +| | RP-82 | RP-182668 | 0421 | 5 | F | Clarification on handling of default parameters | 15.4.0 | +| | RP-82 | RP-182663 | 0429 | 2 | F | SRB3 integrity protection failure handling | 15.4.0 | +| | RP-82 | RP-182653 | 0431 | 2 | F | Corrections to the field descriptions of System Information | 15.4.0 | +| | RP-82 | RP-182653 | 0434 | 1 | F | Correction to SI provision in connected mode | 15.4.0 | +| | RP-82 | RP-182661 | 0436 | 3 | F | PDCCH Monitoring Occasions in SI Window | 15.4.0 | +| | RP-82 | RP-182655 | 0438 | 3 | F | CR on SI Message Acquisition | 15.4.0 | +| | RP-82 | RP-182652 | 0439 | 1 | F | Update of nas-SecurityParamFromNR according to LS from SA3 | 15.4.0 | +| | RP-82 | RP-182652 | 0445 | 2 | F | Correction to Default MAC Cell Group configuration | 15.4.0 | + +| | | | | | | | | +|--|-------|-----------|------|---|---|-------------------------------------------------------------------------------------------------|--------| +| | RP-82 | RP-182652 | 0447 | 1 | F | Correction to missing field descriptions of PLMN Identity | 15.4.0 | +| | RP-82 | RP-182657 | 0448 | 2 | F | Introducing PDCP suspend procedure | 15.4.0 | +| | RP-82 | RP-182657 | 0449 | 2 | F | Correction to PDCP statusReportRequired | 15.4.0 | +| | RP-82 | RP-182664 | 0454 | 3 | F | CR to 38.331 on the ambiguity of targetCellIdentity in Resume/Reestablishment MAC-I calculation | 15.4.0 | +| | RP-82 | RP-182655 | 0457 | 1 | F | Corrections on P-Max description | 15.4.0 | +| | RP-82 | RP-182651 | 0460 | 2 | F | Clarification on Configuration of multiplePHR for EN-DC and NR-CA | 15.4.0 | +| | RP-82 | RP-182656 | 0469 | 2 | F | Correction on conditional presence of PCellOnly | 15.4.0 | +| | RP-82 | RP-182657 | 0474 | 4 | F | Introduction of power boosting indicator for pi2BPSK waveform | 15.4.0 | +| | RP-82 | RP-182655 | 0475 | 1 | F | Correction on the allowedBC-ListMRDC | 15.4.0 | +| | RP-82 | RP-182649 | 0476 | 2 | F | Removal of restriction on RB removal and addition | 15.4.0 | +| | RP-82 | RP-182649 | 0482 | 2 | F | Correction to full configuration | 15.4.0 | +| | RP-82 | RP-182661 | 0492 | 3 | F | CR on MeasurementTimingConfiguration | 15.4.0 | +| | RP-82 | RP-182654 | 0502 | 1 | F | Bandwidth configuration for initial BWP | 15.4.0 | +| | RP-82 | RP-182664 | 0503 | 4 | F | CORESET#0 configuration when SIB1 is not broadcast | 15.4.0 | +| | RP-82 | RP-182663 | 0506 | 1 | F | Correction on the behaviors with cell reselection while T302 is running | 15.4.0 | +| | RP-82 | RP-182661 | 0509 | 2 | F | Correction on SDAP reconfiguration handling | 15.4.0 | +| | RP-82 | RP-182663 | 0510 | 1 | F | Clarification for the UE behaviour in camped normally and camped on any cell states | 15.4.0 | +| | RP-82 | RP-182663 | 0514 | 2 | F | Correction to description of parameter Ns nAndPagingFrameOffset | 15.4.0 | +| | RP-82 | RP-182649 | 0515 | - | F | Correction to description of parameter Ns | 15.4.0 | +| | RP-82 | RP-182661 | 0516 | 1 | F | CR on UE behaviour after SI Acquisition Failure | 15.4.0 | +| | RP-82 | RP-182662 | 0518 | 1 | F | CR on PUCCH-ConfigCommon | 15.4.0 | + +| | | | | | | | | +|--|-------|-----------|------|---|---|--------------------------------------------------------------------------------------------|--------| +| | RP-82 | RP-182662 | 0520 | 1 | F | Clarifications on receiving RRCReject without wait timer | 15.4.0 | +| | RP-82 | RP-182665 | 0522 | 1 | F | CR on powerControlOffset | 15.4.0 | +| | RP-82 | RP-182664 | 0524 | 2 | F | Correction to configuration of firstPDCCH-MonitoringOccasionOfPO | 15.4.0 | +| | RP-82 | RP-182660 | 0539 | 1 | F | R on PCCH-Config | 15.4.0 | +| | RP-82 | RP-182649 | 0541 | - | F | Clarification to no barring configuration for Implicit UAC | 15.4.0 | +| | RP-82 | RP-182649 | 0542 | - | F | Correction to Access Category and barring config determination for implicit access barring | 15.4.0 | +| | RP-82 | RP-182664 | 0543 | 2 | F | Per serving cell MIMO layer configuration | 15.4.0 | +| | RP-82 | RP-182661 | 0545 | 1 | F | Correction to reconfiguration with sync | 15.4.0 | +| | RP-82 | RP-182659 | 0552 | 1 | F | Correction for SSB power | 15.4.0 | +| | RP-82 | RP-182659 | 0554 | 1 | F | Corrections on SearchSpace configuration | 15.4.0 | +| | RP-82 | RP-182665 | 0558 | 1 | F | Correction for TCI state in ControlResourceSet | 15.4.0 | +| | RP-82 | RP-182663 | 0560 | 1 | F | CR for the optional configuration of subbandSize | 15.4.0 | +| | RP-82 | RP-182650 | 0562 | - | F | Correction on ShortMAC-I description in 38.331 | 15.4.0 | +| | RP-82 | RP-182661 | 0567 | 1 | F | CR to the field descriptions of System Information | 15.4.0 | +| | RP-82 | RP-182650 | 0569 | - | F | Clarification on SRB3 release | 15.4.0 | +| | RP-82 | RP-182650 | 0570 | - | F | Avoiding security risk for RLC UM bearers during termination point change | 15.4.0 | +| | RP-82 | RP-182660 | 0571 | 1 | F | MO configuration with SSB SCS for a given SSB frequency | 15.4.0 | +| | RP-82 | RP-182663 | 0572 | 1 | F | Barring alleviation for emergency service | 15.4.0 | +| | RP-82 | RP-182664 | 0575 | 1 | F | Corrections for security configurations during setup of SRB1 | 15.4.0 | +| | RP-82 | RP-182660 | 0577 | 1 | F | Clarification of UE behaviour when frequencyBandList is absent in SIB4 | 15.4.0 | +| | RP-82 | RP-182661 | 0578 | 2 | F | Handling of missing fields in SIB1 | 15.4.0 | + +| | | | | | | | | +|--|-------|-----------|------|---|---|---------------------------------------------------------------------------------|--------| +| | RP-82 | RP-182659 | 0580 | 1 | F | Correction to ControlResourceSetZero | 15.4.0 | +| | RP-82 | RP-182667 | 0582 | 2 | F | Full configuration for inter-RAT handover | 15.4.0 | +| | RP-82 | RP-182664 | 0587 | 1 | F | Corrections on number of RadioLinkMonitoringRS configuration | 15.4.0 | +| | RP-82 | RP-182659 | 0591 | 1 | F | Clarification on phr-Type2OtherCell | 15.4.0 | +| | RP-82 | RP-182667 | 0594 | 2 | F | Addition of PCI in MeasTiming | 15.4.0 | +| | RP-82 | RP-182667 | 0600 | 5 | F | Clarifications to SIBs requiring request procedure | 15.4.0 | +| | RP-82 | RP-182659 | 0601 | 1 | F | Correction for support of initial downlink BWP | 15.4.0 | +| | RP-82 | RP-182657 | 0602 | 1 | F | Miscellaneous corrections related to idle mode SIBs | 15.4.0 | +| | RP-82 | RP-182657 | 0603 | 1 | F | Correction for missing fields in SIB2 and SIB4 | 15.4.0 | +| | RP-82 | RP-182657 | 0604 | 2 | F | Correction to Q-QualMin value range | 15.4.0 | +| | RP-82 | RP-182663 | 0616 | 1 | F | Clarification of cell reselection during resume procedure | 15.4.0 | +| | RP-82 | RP-182663 | 0617 | 1 | F | Determination of Access Identities for RRC-triggered Access Attempts | 15.4.0 | +| | RP-82 | RP-182663 | 0618 | 1 | F | CR to 38.331 on stopping of timer T390 upon reception of RRCRelease | 15.4.0 | +| | RP-82 | RP-182840 | 0620 | 3 | F | CR on MN/SN coordination for report CGI procedure | 15.4.0 | +| | RP-82 | RP-182666 | 0624 | 2 | F | CR to 38.331 on aligning I-RNTI terminology in paging and SuspendConfig (Alt.2) | 15.4.0 | +| | RP-82 | RP-182665 | 0627 | 2 | F | CR to 38.331 on IRAT Cell reselection in RRC_INACTIVE | 15.4.0 | +| | RP-82 | RP-182662 | 0638 | 1 | F | CR for pendingRnaUpdate set | 15.4.0 | +| | RP-82 | RP-182665 | 0640 | 2 | F | Corrections on BWP ID | 15.4.0 | +| | RP-82 | RP-182664 | 0643 | 1 | F | Inter-frequency handover capability | 15.4.0 | +| | RP-82 | RP-182659 | 0646 | 1 | F | Search space configuration for DCI format 2_0 monitoring | 15.4.0 | +| | RP-82 | RP-182739 | 0647 | 3 | F | Correction on power headroom configuration exchange | 15.4.0 | + +| | | | | | | | | +|--|-------|-----------|------|---|---|-------------------------------------------------------------------------|--------| +| | RP-82 | RP-182665 | 0649 | 2 | F | UE capability on PA architecture | 15.4.0 | +| | RP-82 | RP-182662 | 0654 | 1 | F | CR on pdsch-TimeDomainAllocationList and pusch-TimeDomainAllocationList | 15.4.0 | +| | RP-82 | RP-182664 | 0655 | 1 | F | Correction on the SSB based RACH configuration | 15.4.0 | +| | RP-82 | RP-182659 | 0656 | 1 | F | CR on starting bit of Format 2-3 | 15.4.0 | +| | RP-82 | RP-182663 | 0660 | 1 | C | CR on wait timer in RRC release | 15.4.0 | +| | RP-82 | RP-182662 | 0664 | 1 | F | SCell release at RRC Reestablishment | 15.4.0 | +| | RP-82 | RP-182663 | 0665 | 1 | F | Clean up of SRB1 terminology | 15.4.0 | +| | RP-82 | RP-182662 | 0670 | 1 | F | Correction on the size of PUCCH resource ID | 15.4.0 | +| | RP-82 | RP-182667 | 0673 | 3 | F | CR to 38.331 on Integrity Check failure at RRC Reestablishment | 15.4.0 | +| | RP-82 | RP-182661 | 0680 | 1 | F | Correction on SI message acquisition timing | 15.4.0 | +| | RP-82 | RP-182653 | 0682 | - | F | Add t-ReselectionNR-SF in SIB2 | 15.4.0 | +| | RP-82 | RP-182654 | 0683 | - | F | freqBandIndicatorNR correction in MultiFrequencyBandListNR-SIB | 15.4.0 | +| | RP-82 | RP-182658 | 0684 | 2 | F | Corrections to CellSelectionInfo in SIB1 and SIB4 | 15.4.0 | +| | RP-82 | RP-182654 | 0686 | - | F | Correction on the field description of DRX timers | 15.4.0 | +| | RP-82 | RP-182661 | 0687 | 1 | F | Correction on DC subcarrier usage in SetupComplete message | 15.4.0 | +| | RP-82 | RP-182665 | 0688 | 3 | F | Various carrier frequency definition corrections | 15.4.0 | +| | RP-82 | RP-182661 | 0689 | 1 | F | CR on signaling contiguous and non-contiguous EN-DC capability | 15.4.0 | +| | RP-82 | RP-182654 | 0692 | - | F | Update of the usage of QCL type-C | 15.4.0 | +| | RP-82 | RP-182659 | 0694 | 1 | F | Cleanup of references to L1 specifications | 15.4.0 | +| | RP-82 | RP-182660 | 0695 | 1 | F | Correction of MeasResultEUTRA | 15.4.0 | +| | RP-82 | RP-182660 | 0696 | 1 | F | Missing need code for refFreqCSI-RS | 15.4.0 | + +| | | | | | | | | +|--|-------|-----------|------|---|---|---------------------------------------------------------------------------------------------|--------| +| | RP-82 | RP-182661 | 0697 | 2 | F | Missing procedure text in RRC Reconfiguration | 15.4.0 | +| | RP-82 | RP-182781 | 0700 | 3 | F | Correction to UE capability procedures in 38.331 | 15.4.0 | +| | RP-82 | RP-182667 | 0701 | 1 | F | Correction to aperiodicTriggeringOffset | 15.4.0 | +| | RP-82 | RP-182664 | 0709 | 1 | F | CR to 38.331 on including serving cell measurements | 15.4.0 | +| | RP-82 | RP-182660 | 0711 | 1 | F | CR to 38.331 on associatedSSB | 15.4.0 | +| | RP-82 | RP-182662 | 0714 | 1 | F | CR on 38.331 for RRCResumeRequest and RRCResumeRequest1 and protection of RRCResumeRequest1 | 15.4.0 | +| | RP-82 | RP-182667 | 0715 | 2 | F | Correction for reporting of NR serving cell measurements when rsType is missing | 15.4.0 | +| | RP-82 | RP-182656 | 0719 | 1 | F | Clarification of the values for RangeToBestCell | 15.4.0 | +| | RP-82 | RP-182668 | 0721 | 2 | F | CR on handling of timer T380 | 15.4.0 | +| | RP-82 | RP-182662 | 0723 | 2 | F | CR on supporting signalling only connection | 15.4.0 | +| | RP-82 | RP-182838 | 0725 | 3 | F | Signalling introduction of SRS switching capability | 15.4.0 | +| | RP-82 | RP-182667 | 0729 | 3 | B | CR on signalling introduction of UE overheating support in NR SA scenario | 15.4.0 | +| | RP-82 | RP-182856 | 0730 | 4 | F | CR on SRS antenna switching | 15.4.0 | +| | RP-82 | RP-182660 | 0731 | 1 | F | Correction to offsetToPointA | 15.4.0 | +| | RP-82 | RP-182655 | 0732 | - | F | Correction to cell selection parameters | 15.4.0 | +| | RP-82 | RP-182665 | 0746 | 2 | F | CR to 38.331 on stopping T302 and UE related actions | 15.4.0 | +| | RP-82 | RP-182666 | 0750 | 2 | F | Correction on indication for user plane resource release | 15.4.0 | +| | RP-82 | RP-182662 | 0767 | 1 | F | Correction on the terminology scg-ChangeFailure | 15.4.0 | +| | RP-82 | RP-182661 | 0768 | 1 | F | Correction on default configuration | 15.4.0 | +| | RP-82 | RP-182660 | 0772 | 1 | F | Clarification of measurement object for beam reporting for NR cells | 15.4.0 | +| | RP-82 | RP-182667 | 0773 | 3 | F | CR to 38.331 on UE AS Context definition – Include suspendConfig | 15.4.0 | + +| | | | | | | | | +|--|-------|-----------|------|---|---|----------------------------------------------------------------------------------|--------| +| | RP-82 | RP-182661 | 0778 | 1 | F | CR to 38.331 on HO support in Setup Procedure | 15.4.0 | +| | RP-82 | RP-182656 | 0781 | - | F | CR on description of k0 | 15.4.0 | +| | RP-82 | RP-182666 | 0783 | 2 | F | CR to 38.331 on removing FFS of locationInfo | 15.4.0 | +| | RP-82 | RP-182661 | 0787 | - | F | Clarification on MIB Acquisition | 15.4.0 | +| | RP-82 | RP-182662 | 0788 | - | F | CR to 38331 on release after completion of inter-RAT HO | 15.4.0 | +| | RP-82 | RP-182662 | 0789 | - | F | CR to 38.331 on rbg-Size in PDSCH-Config, PUSCH-Config and ConfiguredGrantConfig | 15.4.0 | +| | RP-82 | RP-182657 | 0790 | - | F | Advanced processing time configuration for PDSCH and PUSCH | 15.4.0 | +| | RP-82 | RP-182896 | 0791 | 2 | F | UE specific channel bandwidth signaling | 15.4.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|-------------------------------------------------------------------------------------------------|--------| +| 03/2019 | RP-83 | RP-190541 | 0416 | 4 | F | Clarification on hopping parameters for PUSCH | 15.5.0 | +| | RP-83 | RP-190541 | 0593 | 2 | F | Removal of creation of MCG MAC entity | 15.5.0 | +| | RP-83 | RP-190633 | 0792 | 1 | F | Capability for aperiodic CSI-RS triggering with different numerology between PDCCH and CSI-RS | 15.5.0 | +| | RP-83 | RP-190541 | 0796 | 2 | F | Correction on Mapping between SSBs and PDCCH Monitoring Occasions in SI Window | 15.5.0 | +| | RP-83 | RP-190541 | 0797 | 2 | F | Correction to SI Request Procedure | 15.5.0 | +| | RP-83 | RP-190546 | 0798 | 2 | F | CR to 38.331 on clarification of reportCGI | 15.5.0 | +| | RP-83 | RP-190545 | 0799 | 2 | F | Describing mandatory/optional information in inter-node RRC messages | 15.5.0 | +| | RP-83 | RP-190541 | 0800 | 1 | F | Search space configuration for cross carrier scheduling | 15.5.0 | +| | RP-83 | RP-190542 | 0803 | 1 | F | Clarification on FeatureSetCombinationId zero value | 15.5.0 | +| | RP-83 | RP-190546 | 0805 | 2 | F | Clarification on UE Capability Request Filtering | 15.5.0 | +| | RP-83 | RP-190545 | 0807 | 3 | F | Miscellaneous non-controversial corrections | 15.5.0 | +| | RP-83 | RP-190541 | 0808 | 2 | F | CR to 38.331 on MAC configuration | 15.5.0 | +| | RP-83 | RP-190543 | 0810 | 2 | F | Correction to SCG failure | 15.5.0 | +| | RP-83 | RP-190540 | 0811 | 1 | F | Clarifying handling of parent and child IE need nodes | 15.5.0 | +| | RP-83 | RP-190544 | 0812 | 2 | F | Clarification to channel bandwidth signalling | 15.5.0 | +| | RP-83 | RP-190541 | 0813 | 1 | F | Clarifications to BWP configuration options | 15.5.0 | +| | RP-83 | RP-190543 | 0822 | 2 | F | Correction to EUTRA-MBSFN-SubframeConfig | 15.5.0 | +| | RP-83 | RP-190545 | 0823 | 2 | F | Clarification on dedicated serving cell configuration in Re-establishment | 15.5.0 | +| | RP-83 | RP-190541 | 0828 | 2 | F | Clarification on the BWP id configuration | 15.5.0 | +| | RP-83 | RP-190541 | 0836 | 1 | F | Upon entering a new PLMN which is in the list of EPLMNs in RRC INACTIVE state | 15.5.0 | +| | RP-83 | RP-190546 | 0843 | 1 | F | EUTRA UE capability filtering in NR UE capability enquiry | 15.5.0 | +| | RP-83 | RP-190543 | 0847 | 2 | F | Correction to SIB1 transmission during handover | 15.5.0 | +| | RP-83 | RP-190545 | 0850 | 2 | F | Clarification to monitoring occasion of PWS notification | 15.5.0 | +| | RP-83 | RP-190541 | 0853 | 1 | F | HandoverPreparationInformation for CU/DU | 15.5.0 | +| | RP-83 | RP-190542 | 0855 | 1 | F | CR to introduce simultaneousRxDatassb-DiffNumerology for NR SA | 15.5.0 | +| | RP-83 | RP-190550 | 0858 | - | F | Condition on integrity protection for DRB | 15.5.0 | +| | RP-83 | RP-190544 | 0860 | 2 | F | Handling on UE Inactive AS context upon resume | 15.5.0 | +| | RP-83 | RP-190542 | 0861 | 1 | F | Miscellaneous Corrections for INACTIVE | 15.5.0 | +| | RP-83 | RP-190542 | 0864 | 1 | F | Correction on RRC processing delay | 15.5.0 | +| | RP-83 | RP-190540 | 0865 | - | F | Dummify the ue-BeamLockFunction IE | 15.5.0 | +| | RP-83 | RP-190545 | 0866 | 2 | F | Further update of Need codes | 15.5.0 | +| | RP-83 | RP-190541 | 0867 | 1 | F | Corrections to reestablishment procedure | 15.5.0 | +| | RP-83 | RP-190545 | 0868 | 2 | F | CR on use of positioning measurement gaps for subframe and slot timing detection towards E-UTRA | 15.5.0 | +| | RP-83 | RP-190542 | 0876 | 2 | F | Barring alleviation when T302 or T390 is stopped | 15.5.0 | +| | RP-83 | RP-190544 | 0877 | 2 | F | Correction on smtc configuration in NR SCell addition procedure | 15.5.0 | +| | RP-83 | RP-190543 | 0884 | 2 | F | Correction on the configuration for transform preceding of PUSCH | 15.5.0 | +| | RP-83 | RP-190543 | 0896 | 2 | F | Correction to Need Codes in system information | 15.5.0 | +| | RP-83 | RP-190541 | 0897 | 1 | F | Corrections on drb-ContinueROHC | 15.5.0 | +| | RP-83 | RP-190541 | 0898 | 1 | F | Correction on outOfOrderDelivery | 15.5.0 | +| | RP-83 | RP-190542 | 0902 | 1 | F | Corrections on radio link failure related actions | 15.5.0 | +| | RP-83 | RP-190541 | 0904 | 1 | F | Clarification for SIB validity | 15.5.0 | +| | RP-83 | RP-190540 | 0905 | - | F | Corrections to MFBI | 15.5.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|------------------------------------------------------------------------------------------------------|--------| +| | RP-83 | RP-190542 | 0912 | 1 | F | CR on clarification on the description of NIA0 | 15.5.0 | +| | RP-83 | RP-190542 | 0913 | 1 | F | CR on the number of bits of downlink NAS COUNT value | 15.5.0 | +| | RP-83 | RP-190541 | 0920 | 1 | F | CR to 38.331 for not supporting different quantities for thresholds in Event A5 and B2 | 15.5.0 | +| | RP-83 | RP-190544 | 0922 | 2 | F | CR on SSB type indication | 15.5.0 | +| | RP-83 | RP-190545 | 0923 | 2 | F | Correction for measurements of serving cells without SSB or without CSI-RS | 15.5.0 | +| | RP-83 | RP-190540 | 0930 | - | F | CR on introduction of UE assistance information in inter-node message | 15.5.0 | +| | RP-83 | RP-190540 | 0931 | - | F | CR on description of SRS carrier switching | 15.5.0 | +| | RP-83 | RP-190542 | 0932 | 1 | F | Clarification on the relation between CA configuration and supported featureset combination _Option1 | 15.5.0 | +| | RP-83 | RP-190545 | 0935 | 2 | F | Unification of EN-DC terminology | 15.5.0 | +| | RP-83 | RP-190550 | 0938 | - | F | PDCP re-establishment during SRB modification for EUTRA/5GC | 15.5.0 | +| | RP-83 | RP-190541 | 0939 | 1 | F | The support of drb-ContinueROHC | 15.5.0 | +| | RP-83 | RP-190541 | 0948 | 1 | F | Correction on PTRS port index | 15.5.0 | +| | RP-83 | RP-190541 | 0956 | 1 | F | CR on the supplementaryUplink and uplinkConfig | 15.5.0 | +| | RP-83 | RP-190545 | 0963 | 2 | F | Correction on MIB acquisition upon Reconfiguration with Sync | 15.5.0 | +| | RP-83 | RP-190543 | 0967 | 2 | F | Offset for inter-RAT cell reselection | 15.5.0 | +| | RP-83 | RP-190541 | 0975 | 1 | F | Correction on SI scheduling | 15.5.0 | +| | RP-83 | RP-190543 | 0976 | 2 | F | Correction of uac-AccessCategory1-SelectionAssistanceInfo field description | 15.5.0 | +| | RP-83 | RP-190546 | 0978 | 3 | F | Correction on going to RRC_IDLE upon inter-RAT cell reselection in RRC_INACTIVE | 15.5.0 | +| | RP-83 | RP-190543 | 0981 | 2 | F | Clarification on nrofSS-BlocksToAverage and absThreshSS-BlocksConsolidation | 15.5.0 | +| | RP-83 | RP-190543 | 0984 | 3 | F | Correction on compilation of featureSets for NR container | 15.5.0 | +| | RP-83 | RP-190540 | 0985 | - | F | Enable and disable of security at DRB setup | 15.5.0 | +| | RP-83 | RP-190545 | 0986 | 2 | F | Clarification on TCI state ID | 15.5.0 | +| | RP-83 | RP-190544 | 0987 | - | F | Clarification for random access on SUL | 15.5.0 | +| | RP-83 | RP-190545 | 0988 | 1 | F | Correction on supportedBandwidthCombinationSetEUTRA-v1530 usage | 15.5.0 | +| | RP-83 | RP-190544 | 0989 | - | F | CR on Processing delay requirements for RRC Resume procedures in TS 38.331 | 15.5.0 | +| 04/2019 | RP-83 | | | | | MCC: Formatting error correction (missing carriage return) in the end of clause 5.3.5.11. | 15.5.1 | +| 06/2019 | RP-84 | RP-191379 | 0906 | 5 | F | Reconfig with sync terminology | 15.6.0 | +| | RP-84 | RP-191378 | 0916 | 5 | B | Introduction of late drop NGEN-DC, NE-DC and NR-DC | 15.6.0 | +| | RP-84 | RP-191374 | 0996 | 2 | F | Correction to the need code of some fields in SIB2 | 15.6.0 | +| | RP-84 | RP-191377 | 1003 | 3 | F | Clarification for handling of suspendConfig | 15.6.0 | +| | RP-84 | RP-191377 | 1005 | 3 | F | Reporting of serving cell and best neighbour cell and sorting of beam | 15.6.0 | +| | RP-84 | RP-191377 | 1011 | 1 | F | On T321 timer related informative text correction | 15.6.0 | +| | RP-84 | RP-191377 | 1013 | 1 | C | CR to direct current report for UL and SUL | 15.6.0 | +| | RP-84 | RP-191380 | 1014 | 1 | F | Correction on storing UE AS Inactive Context | 15.6.0 | +| | RP-84 | RP-191373 | 1015 | - | F | Correction on ReconfigurationWithSync | 15.6.0 | +| | RP-84 | RP-191380 | 1016 | 2 | F | Correction on Handover from NR to EUTRAN | 15.6.0 | +| | RP-84 | RP-191373 | 1018 | - | F | Introduction of additional UE capability on HARQ-ACK multiplexing on PUSCH | 15.6.0 | +| | RP-84 | RP-191378 | 1019 | 1 | F | Correction on bar indication of emergency service (access category 2) | 15.6.0 | +| | RP-84 | RP-191373 | 1020 | - | F | Correction on UE configuration for RRC Resume procedure | 15.6.0 | +| | RP-84 | RP-191373 | 1021 | - | F | RRC release with suspend configuration and inter-RAT redirection | 15.6.0 | +| | RP-84 | RP-191373 | 1022 | - | F | RRC Reconfiguration via SRB3 in EN-DC | 15.6.0 | + +| | | | | | | | | +|--|-------|-----------|------|---|---|----------------------------------------------------------------------------------------------------------------------------------|--------| +| | RP-84 | RP-191373 | 1023 | - | F | Corrections on RLC bearer setup | 15.6.0 | +| | RP-84 | RP-191373 | 1024 | - | F | Clarification to Permitted MaxCID for ROHC and Uplink-Only ROHC | 15.6.0 | +| | RP-84 | RP-191373 | 1025 | - | F | Coordination of ROHC capability for MR-DC | 15.6.0 | +| | RP-84 | RP-191373 | 1026 | - | F | Correction on the rlmlnSyncOutOfSyncThreshold | 15.6.0 | +| | RP-84 | RP-191373 | 1027 | - | F | Correction on description of tci-PresentInDCI | 15.6.0 | +| | RP-84 | RP-191374 | 1031 | - | F | RRC processing delay for UE capability transfer | 15.6.0 | +| | RP-84 | RP-191377 | 1032 | 1 | F | Handling of SMTC configuration | 15.6.0 | +| | RP-84 | RP-191378 | 1033 | 1 | F | Clarification on filters used to generate FeatureSets (38.331) | 15.6.0 | +| | RP-84 | RP-191374 | 1034 | - | F | Correction of behavior for eutra-nr-only | 15.6.0 | +| | RP-84 | RP-191377 | 1038 | 1 | F | Clarification on CSI-RS resource configuration in MO | 15.6.0 | +| | RP-84 | RP-191378 | 1039 | 2 | F | Update on usage of Need codes | 15.6.0 | +| | RP-84 | RP-191377 | 1040 | 1 | F | Ignore additional fields in RRC Release message before security activation | 15.6.0 | +| | RP-84 | RP-191374 | 1041 | - | F | Correction on use of Null algorithm for DRBs during emergency calls in LSM | 15.6.0 | +| | RP-84 | RP-191380 | 1042 | 2 | F | NR changes for FullConfig for Inter-RAT intra-system HO | 15.6.0 | +| | RP-84 | RP-191376 | 1043 | 2 | F | Monitoring of short messages with multi-beams | 15.6.0 | +| | RP-84 | RP-191377 | 1045 | 1 | F | Clarification of commonControlResourceSet frequency reference point | 15.6.0 | +| | RP-84 | RP-191379 | 1046 | 2 | F | CR on capability of maxUplinkDutyCycle for FR2 | 15.6.0 | +| | RP-84 | RP-191374 | 1049 | - | F | CR to subcarrierSpacing in RateMatchPattern and SCS-SpecificCarrier | 15.6.0 | +| | RP-84 | RP-191377 | 1053 | 1 | F | CR on transferring common configuration during handover and SN change | 15.6.0 | +| | RP-84 | RP-191381 | 1054 | 2 | F | Correction to barring alleviation | 15.6.0 | +| | RP-84 | RP-191381 | 1055 | 3 | F | UE behaviour on the cell without TAC | 15.6.0 | +| | RP-84 | RP-191379 | 1058 | 2 | F | Correction to RRC resume | 15.6.0 | +| | RP-84 | RP-191376 | 1061 | 1 | F | Corrections to inter-node messages | 15.6.0 | +| | RP-84 | RP-191378 | 1063 | 1 | F | Clarification on mandatory information in inter node RRC messages | 15.6.0 | +| | RP-84 | RP-191374 | 1066 | - | F | Correction to PWS reception | 15.6.0 | +| | RP-84 | RP-191377 | 1068 | 1 | F | Serving cell measurement handling with different rsType configuration scenarios | 15.6.0 | +| | RP-84 | RP-191374 | 1069 | - | F | On CGI reporting contents | 15.6.0 | +| | RP-84 | RP-191374 | 1071 | - | F | CR for 38.331 on security related corrections to UE and Network initiated RRC procedures to increase user's security and privacy | 15.6.0 | +| | RP-84 | RP-191379 | 1072 | 3 | F | Correction on the issue with NCP and ECP for RateMatchPattern | 15.6.0 | +| | RP-84 | RP-191377 | 1075 | 1 | F | Security protection of RRC messages | 15.6.0 | +| | RP-84 | RP-191381 | 1076 | 1 | F | Introduction of a new NR band for LTE/NR spectrum sharing in Band 41/n41 | 15.6.0 | +| | RP-84 | RP-191375 | 1077 | - | F | Stop of T302 and T390 at reception of RRCRelease with waitTime | 15.6.0 | +| | RP-84 | RP-191375 | 1078 | - | F | Restriction of piggybacking of NAS PDUs | 15.6.0 | +| | RP-84 | RP-191379 | 1079 | 3 | F | Correction on intra-band fallback behavior with FeatureSetsPerCC | 15.6.0 | +| | RP-84 | RP-191375 | 1081 | - | F | Removal of spurious requirement on consistency of feature set combination IDs | 15.6.0 | +| | RP-84 | RP-191381 | 1082 | 3 | F | Miscellaneous non-controversial corrections Set II | 15.6.0 | +| | RP-84 | RP-191377 | 1083 | 1 | F | Correction to configuration of security in RadioBearerConfig | 15.6.0 | +| | RP-84 | RP-191379 | 1086 | 2 | F | CR to 38.331 on MeasurementTimingConfiguration | 15.6.0 | +| | RP-84 | RP-191375 | 1088 | - | F | Correction to the description of subcarrierspacing usage in ServingCellConfigCommon | 15.6.0 | +| | RP-84 | RP-191375 | 1089 | - | F | 38.331 Clarification on multiple TA capabilities | 15.6.0 | +| | RP-84 | RP-191375 | 1091 | - | F | Set beamCorrespondenceCA dummy | 15.6.0 | +| | RP-84 | RP-191377 | 1092 | 1 | F | Correction on Measurement Report Triggering for Periodical Report | 15.6.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|------------------------------------------------------------------------------------------------------------|--------| +| | RP-84 | RP-191375 | 1094 | - | F | Correction on PDCP duplication configuration | 15.6.0 | +| | RP-84 | RP-191375 | 1095 | - | F | Correction on BWP configuration | 15.6.0 | +| | RP-84 | RP-191377 | 1097 | 1 | F | Correction on configuration of pucch-ResourceCommon | 15.6.0 | +| | RP-84 | RP-191376 | 1098 | 1 | F | Clarification of PUCCH reconfiguration on NR UL and SUL | 15.6.0 | +| | RP-84 | RP-191375 | 1100 | 1 | F | Correction on initial BWP configuration in DownlinkConfigCommon and UplinkConfigCommon | 15.6.0 | +| | RP-84 | RP-191377 | 1101 | 1 | F | Correction on PUCCH cell | 15.6.0 | +| | RP-84 | RP-191377 | 1103 | 1 | F | Correction on the pdcp-Config | 15.6.0 | +| | RP-84 | RP-191379 | 1104 | 2 | F | Correction on pathlossReferenceLinking | 15.6.0 | +| | RP-84 | RP-191381 | 1106 | 2 | F | Clarification of dedicated priority handling from RRC_INACTIVE to RRC_IDLE | 15.6.0 | +| | RP-84 | RP-191375 | 1110 | - | F | Clarification on sending condition for mcg-RB-Config | 15.6.0 | +| | RP-84 | RP-191375 | 1111 | - | F | Clarification of timing reference for CSI-RS resources | 15.6.0 | +| | RP-84 | RP-191376 | 1113 | - | F | Setting of resumeCause for NAS triggered event | 15.6.0 | +| | RP-84 | RP-191376 | 1114 | - | F | UE capability signalling for FD-MIMO processing capabilities for EN-DC | 15.6.0 | +| | RP-84 | RP-191376 | 1115 | - | F | Modified UE capability on different numerologies within the same PUCCH group | 15.6.0 | +| | RP-84 | RP-191478 | 1116 | 2 | F | Clarification to commonSearchSpaceList in PDCCH-ConfigCommon | 15.6.0 | +| | RP-84 | RP-191589 | 1117 | 1 | F | Removal of "Capability for aperiodic CSI-RS triggering with different numerology between PDCCH and CSI-RS" | 15.6.0 | +| 09/2019 | RP-85 | RP-192196 | 1120 | 1 | C | Additional capability signalling for 1024QAM support | 15.7.0 | +| | RP-85 | RP-192191 | 1121 | 1 | F | Correction on TDD-UL-DL-Config | 15.7.0 | +| | RP-85 | RP-192191 | 1122 | 1 | F | Correction of the secondHopPRB Parameter | 15.7.0 | +| | RP-85 | RP-192190 | 1123 | - | F | RSRP reporting of SFTD measurement in NR-DC | 15.7.0 | +| | RP-85 | RP-192191 | 1124 | 1 | F | Small Corrections for System Information | 15.7.0 | +| | RP-85 | RP-192194 | 1125 | - | F | Corrections for Inter-node Messages | 15.7.0 | +| | RP-85 | RP-192191 | 1126 | 1 | F | Clarification of Layer 3 Filtering for E-UTRA | 15.7.0 | +| | RP-85 | RP-192190 | 1127 | - | F | Clarification on FailureInformation report for NE-DC | 15.7.0 | +| | RP-85 | RP-192191 | 1136 | 1 | F | Clarification to fullConfig in NR | 15.7.0 | +| | RP-85 | RP-192190 | 1137 | - | F | Updates for positioning measurement gaps for subframe and slot timing detection towards E-UTRA | 15.7.0 | +| | RP-85 | RP-192191 | 1138 | 1 | F | Clarification for enabling of configured PUSCH frequency hopping | 15.7.0 | +| | RP-85 | RP-192191 | 1139 | 1 | B | Introduction of SFTD measurement to neighbour cells for NR SA | 15.7.0 | +| | RP-85 | RP-192192 | 1144 | 1 | F | Corrections to 38.331 on SI-schedulingInfo | 15.7.0 | +| | RP-85 | RP-192193 | 1148 | 2 | F | Clarification on SRB2 and DRB configuration | 15.7.0 | +| | RP-85 | RP-192191 | 1151 | 2 | F | PDU session release indication to upper layers during Full Configuration | 15.7.0 | +| | RP-85 | RP-192191 | 1160 | 1 | F | Clarification on max payload of PUCCH-ResourceSet | 15.7.0 | +| | RP-85 | RP-192191 | 1161 | 1 | F | Clarification on PUSCH configuration | 15.7.0 | +| | RP-85 | RP-192192 | 1167 | 1 | F | Correction of condition HO-toNR and HO-Conn | 15.7.0 | +| | RP-85 | RP-192192 | 1172 | 1 | F | Clarifying UE capability freqHoppingPUCCH-F0-2 and freqHoppingPUCCH-F1-3-4 | 15.7.0 | +| | RP-85 | RP-192190 | 1173 | 1 | F | Clarification on selectedBandCombination | 15.7.0 | +| | RP-85 | RP-192193 | 1174 | 2 | F | Clarifying handling of information elements on the F1 interface | 15.7.0 | +| | RP-85 | RP-192192 | 1178 | 1 | F | Correction of field descriptions in UE-CapabilityRequestFilterCommon (38.331) | 15.7.0 | +| | RP-85 | RP-192190 | 1179 | - | F | Clarification of ca-ParametersNR-forDC (38.331) | 15.7.0 | +| | RP-85 | RP-192193 | 1183 | 2 | F | Correction on reestablishRLC | 15.7.0 | +| | RP-85 | RP-192191 | 1185 | 1 | F | Correction on SFTD measurement configuration | 15.7.0 | +| | RP-85 | RP-192193 | 1191 | 2 | F | Handling of embedded RRC message in RRCReconfiguration procedure | 15.7.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|---------------------------------------------------------------------------------------------------|--------| +| | RP-85 | RP-192192 | 1201 | 2 | F | Clarification on definition of PUSCH-Less SCell | 15.7.0 | +| | RP-85 | RP-192190 | 1204 | - | F | Correction on non-critical extension for NRDC-Parameters | 15.7.0 | +| | RP-85 | RP-192191 | 1208 | 1 | F | Correction on UE actions upon going to RRC_IDLE | 15.7.0 | +| | RP-85 | RP-192192 | 1211 | 1 | F | Correction on the acquisition of MIB and SIB1 for re-establishment | 15.7.0 | +| | RP-85 | RP-192192 | 1212 | 1 | F | Correction on band selection in SIB1 | 15.7.0 | +| | RP-85 | RP-192193 | 1213 | 2 | F | Correction on the actions upon reception of SIB2 and SIB4 | 15.7.0 | +| | RP-85 | RP-192193 | 1219 | 3 | F | Miscellaneous non-controversial corrections Set III | 15.7.0 | +| | RP-85 | RP-192194 | 1220 | 3 | F | Channel Bandwidth validation upon SIB1 acquisition | 15.7.0 | +| | RP-85 | RP-192193 | 1224 | 1 | F | Correction of presence conditions for common PSCell parameters | 15.7.0 | +| | RP-85 | RP-192190 | 1226 | - | F | Release of unnecessary power restrictions upon RRC connection re-establishment in NE-DC and NR-DC | 15.7.0 | +| | RP-85 | RP-192193 | 1232 | 2 | F | Correction of field inclusion for inter-node message | 15.7.0 | +| | RP-85 | RP-192192 | 1234 | 1 | F | SFTD measurement information in CG-ConfigInfo | 15.7.0 | +| | RP-85 | RP-192192 | 1235 | 1 | F | Correction for UE context retrieval | 15.7.0 | +| | RP-85 | RP-192190 | 1236 | - | F | Correction on CGI measurements | 15.7.0 | +| | RP-85 | RP-192191 | 1237 | 1 | F | Corrections to SIB8 for CMAS geo-fencing | 15.7.0 | +| | RP-85 | RP-192194 | 1242 | 3 | F | Corrections on the condition of RBTermChange | 15.7.0 | +| | RP-85 | RP-192192 | 1243 | 1 | F | CR on clarification of aggregated bandwidth for overheating | 15.7.0 | +| | RP-85 | RP-192190 | 1244 | - | F | Clarification on the selectedBandEntriesMN - Understanding 1 | 15.7.0 | +| | RP-85 | RP-192194 | 1253 | 1 | F | Correction on RRC connection release indication after handover | 15.7.0 | +| | RP-85 | RP-192193 | 1254 | 2 | F | Corrections on SIB1 configuration | 15.7.0 | +| | RP-85 | RP-192191 | 1256 | 1 | F | Correction on inter-RAT cell re-selection when UE is in RRC_IDLE | 15.7.0 | +| | RP-85 | RP-192193 | 1257 | 2 | F | maxMIMO-Layers for the normal uplink and the supplementary uplink_Option 1 | 15.7.0 | +| | RP-85 | RP-192193 | 1261 | 1 | F | Correction on overheating indication | 15.7.0 | +| | RP-85 | RP-192192 | 1262 | - | F | Handling lists other than AddMod | 15.7.0 | +| | RP-85 | RP-192193 | 1263 | 1 | F | Releasing source cell ConfigCommon fields not present in target cell | 15.7.0 | +| | RP-85 | RP-192347 | 1265 | - | C | Introduction of UE capability for NR-DC with SFN synchronization between PCell and PSCell | 15.7.0 | +| 12/2019 | RP-86 | RP-192934 | 1147 | 2 | C | Security requirement for UE capability enquiry for NR | 15.8.0 | +| | RP-86 | RP-192934 | 1267 | 1 | F | Corrections on CG-Config | 15.8.0 | +| | RP-86 | RP-192934 | 1273 | 1 | F | CR to introduce timer for DRX based SFTD measurement | 15.8.0 | +| | RP-86 | RP-192934 | 1274 | 1 | F | Correction on absence of gapPurpose | 15.8.0 | +| | RP-86 | RP-192934 | 1278 | 1 | F | Correction on field description of cellReselectionInfoCommon | 15.8.0 | +| | RP-86 | RP-192935 | 1283 | 2 | F | Clarifying the alignment of capability filtering across LTE and NR in MR-DC | 15.8.0 | +| | RP-86 | RP-192934 | 1292 | 1 | F | Correction for P-Max in FR2 | 15.8.0 | +| | RP-86 | RP-192934 | 1296 | 2 | F | Correction on frequency indication in SIB1 and SIB2 | 15.8.0 | +| | RP-86 | RP-192937 | 1300 | 2 | F | Handling of AS-Config in HandoverPreparationInformation | 15.8.0 | +| | RP-86 | RP-192936 | 1301 | 2 | F | Corrections on scg-RB-Config in CG-Config | 15.8.0 | +| | RP-86 | RP-192937 | 1305 | 2 | F | Correction on MCG measurements in SCGFailureInformation | 15.8.0 | +| | RP-86 | RP-192937 | 1308 | 3 | F | Correction of SRB3 handling at full configuration (Alt2) | 15.8.0 | +| | RP-86 | RP-192936 | 1309 | 2 | F | Correction to integrity protection in DRB addition and modification | 15.8.0 | +| | RP-86 | RP-192938 | 1323 | 3 | F | Miscellaneous non-controversial corrections Set IV | 15.8.0 | +| | RP-86 | RP-192935 | 1325 | 2 | F | Presence and absence of TAC in NR cell | 15.8.0 | +| | RP-86 | RP-192935 | 1332 | 4 | F | Security Algorithms for Radio Bearers | 15.8.0 | +| | RP-86 | RP-192934 | 1333 | 1 | F | Correction on the Msg3 based on demand system information | 15.8.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------------|--------| +| | RP-86 | RP-192935 | 1335 | 2 | F | Clarification for aggregated bandwidth for overheating | 15.8.0 | +| | RP-86 | RP-192935 | 1337 | 1 | F | Clarification on the feature set report in EUTRAN | 15.8.0 | +| | RP-86 | RP-192934 | 1341 | 1 | F | CR to 38.331 on CGI information | 15.8.0 | +| | RP-86 | RP-192936 | 1357 | 1 | F | Restoring SDAP and RoHC contexts during Resumption | 15.8.0 | +| | RP-86 | RP-192934 | 1358 | - | F | Conditional presence on ue-CapabilityInfo and servCellIndexRangeSCG for inter-MN handover without SN change | 15.8.0 | +| | RP-86 | RP-192934 | 1362 | - | F | Configuration limitation for RRCRelease message in R15 | 15.8.0 | +| | RP-86 | RP-192937 | 1368 | 1 | F | Correction to AS security key update | 15.8.0 | +| | RP-86 | RP-192936 | 1369 | 1 | F | Correction on the condition of RBTermChange | 15.8.0 | +| | RP-86 | RP-192936 | 1375 | 1 | F | Correction on the configuration of split SRB | 15.8.0 | +| | RP-86 | RP-192934 | 1378 | - | F | Correction on camping conditions | 15.8.0 | +| | RP-86 | RP-192937 | 1379 | 1 | F | Correction on CORESET location | 15.8.0 | +| | RP-86 | RP-192938 | 1381 | 2 | F | Correction to key derivation for the UE configured with sk-counter | 15.8.0 | +| | RP-86 | RP-192936 | 1383 | 1 | F | Correction on the pre-condition for reconfiguration with sync of SCG | 15.8.0 | +| | RP-86 | RP-192935 | 1385 | - | F | Correction on AS-Config | 15.8.0 | +| | RP-86 | RP-192935 | 1387 | - | F | Correction on measurement reporting in NR-DC | 15.8.0 | +| | RP-86 | RP-192936 | 1389 | 1 | F | Correction on SIB1 description | 15.8.0 | +| | RP-86 | RP-192937 | 1402 | 1 | F | Correction to Feature Set Combination and Band combination list for NR-DC (38.331) | 15.8.0 | +| | RP-86 | RP-192937 | 1403 | 2 | F | Security requirements for split PDU session (38.331) | 15.8.0 | +| | RP-86 | RP-192938 | 1405 | 2 | F | Correction of UE assistance information | 15.8.0 | +| | RP-86 | RP-192936 | 1406 | 1 | F | Clarification regarding inter-node transfer of UE capability containers | 15.8.0 | +| | RP-86 | RP-192749 | 1421 | 1 | F | NE-DC dynamic power sharing capability | 15.8.0 | +| 03/2020 | RP-87 | RP-200335 | 1272 | 3 | F | Corrections on maxMeasIdentitiesSCG-NR in MR-DC | 15.9.0 | +| | RP-87 | RP-200334 | 1409 | 2 | F | CR on BWCS for inter-ENDC BC with intra-ENDC BC (38.331) | 15.9.0 | +| | RP-87 | RP-200334 | 1410 | 4 | F | CR to 38.331 on support of 70MHz channel bandwidth | 15.9.0 | +| | RP-87 | RP-200335 | 1440 | 2 | F | Clarification on the PLMN-IdentityInfoList | 15.9.0 | +| | RP-87 | RP-200334 | 1444 | 1 | F | Correction on removal of NR-DC and NE-DC band combinations when capabilityRequestFilterCommon is absent | 15.9.0 | +| | RP-87 | RP-200334 | 1450 | 1 | F | Correction on reporting of uplink TX direct current | 15.9.0 | +| | RP-87 | RP-200334 | 1454 | 1 | F | Corrections to the Location measurement indication procedure | 15.9.0 | +| | RP-87 | RP-200334 | 1455 | - | F | Introduction of provisions for late non-critical extensions | 15.9.0 | +| | RP-87 | RP-200334 | 1460 | 1 | F | Correction on p-maxNR-FR1 for NE-DC | 15.9.0 | +| | RP-87 | RP-200334 | 1461 | - | F | Correction on SFTD frequency list in INM | 15.9.0 | +| | RP-87 | RP-200335 | 1472 | 2 | F | Miscellaneous non-controversial corrections Set V | 15.9.0 | +| | RP-87 | RP-200335 | 1475 | 1 | F | Capability coordination for NE-DC | 15.9.0 | +| | RP-87 | RP-200335 | 1483 | 2 | F | CR on fallback BC reporting | 15.9.0 | +| | RP-87 | RP-200334 | 1484 | 1 | F | CR on overheating assistance reporting in handover case | 15.9.0 | +| | RP-87 | RP-200334 | 1496 | 1 | F | Correction on NZP-CSI-RS-ResourceSet | 15.9.0 | +| | RP-87 | RP-200335 | 1501 | 1 | F | UE capability of intra-band requirements for inter-band EN-DC/NE-DC | 15.9.0 | +| 03/2020 | RP-87 | RP-200335 | 1141 | 2 | F | Correction on usage of access category 2 for UAC for RNA update | 16.0.0 | +| | RP-87 | RP-200358 | 1149 | 2 | F | NAS handling error of nas-Container for security key derivation | 16.0.0 | +| | RP-87 | RP-200356 | 1152 | 3 | F | CR on capability of maxUplinkDutyCycle for inter-band EN-DC PC2 UE | 16.0.0 | +| | RP-87 | RP-200357 | 1168 | 3 | F | Support of releasing UL configuration | 16.0.0 | +| | RP-87 | RP-200357 | 1218 | 3 | B | Introduction of a second SMTC per frequency carrier in idle/inactive | 16.0.0 | +| | RP-87 | RP-200358 | 1312 | 3 | C | Introduction of voice fallback indication | 16.0.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|----------------------------------------------------------------------------------------------|--------| +| | RP-87 | RP-200358 | 1354 | 2 | C | CR to 38.331 on CSI-RS inter-node message | 16.0.0 | +| | RP-87 | RP-200335 | 1361 | 1 | B | PRACH prioritization parameters for MPS and MCS | 16.0.0 | +| | RP-87 | RP-200358 | 1433 | 2 | B | Introduction of downgraded configuration for SRS antenna switching | 16.0.0 | +| | RP-87 | RP-200355 | 1434 | 2 | B | Introducing autonomous gap in CGI reporting | 16.0.0 | +| | RP-87 | RP-200351 | 1441 | 1 | B | Introduction of UECapabilityInformation segmentation in TS38.331 | 16.0.0 | +| | RP-87 | RP-200358 | 1443 | 1 | B | Introduction of NR IDC solution | 16.0.0 | +| | RP-87 | RP-200350 | 1446 | 1 | B | Introduction of SRVCC from 5G to 3G | 16.0.0 | +| | RP-87 | RP-200341 | 1462 | 2 | B | Introduction of on-demand SI procedure in RRC_CONNECTED | 16.0.0 | +| | RP-87 | RP-200358 | 1465 | 1 | B | Introduction of DL RRC segmentation | 16.0.0 | +| | RP-87 | RP-200353 | 1468 | 1 | B | Introducing the support of Non-Public Networks | 16.0.0 | +| | RP-87 | RP-200344 | 1469 | 3 | B | CR for 38.331 for Power Savings | 16.0.0 | +| | RP-87 | RP-200349 | 1471 | 4 | B | 38.331 CR on Integrated Access and Backhaul for NR | 16.0.0 | +| | RP-87 | RP-200348 | 1476 | 3 | B | CR for 38.331 for CA&DC enh | 16.0.0 | +| | RP-87 | RP-200341 | 1477 | 2 | B | Introduction of NR operation with Shared Spectrum Access in RRC | 16.0.0 | +| | RP-87 | RP-200347 | 1478 | 2 | B | Introduction of NR mobility enhancement | 16.0.0 | +| | RP-87 | RP-200335 | 1486 | - | B | Introduction of additional RACH configurations for TDD FR1 | 16.0.0 | +| | RP-87 | RP-200343 | 1487 | 1 | B | Introduction of NR eURLLC | 16.0.0 | +| | RP-87 | RP-200354 | 1488 | 2 | B | CR for introducing MDT and SON | 16.0.0 | +| | RP-87 | RP-200357 | 1489 | - | C | CR to 38.331 on DRX coordination | 16.0.0 | +| | RP-87 | RP-200346 | 1493 | 1 | B | Introduction of 5G V2X with NR sidelink | 16.0.0 | +| | RP-87 | RP-200340 | 1494 | 2 | B | Introduction of CLI handling and RIM in TS38.331 | 16.0.0 | +| | RP-87 | RP-200352 | 1498 | 1 | B | Introduction of NR IIoT | 16.0.0 | +| | RP-87 | RP-200342 | 1499 | 1 | B | Introduction of 2-step RA | 16.0.0 | +| | RP-87 | RP-200339 | 1500 | 2 | B | Introduction of MIMO enhancements | 16.0.0 | +| | RP-87 | RP-200359 | 1502 | - | B | Recommended Bit Rate/Query for FLUS and MTSI | 16.0.0 | +| | RP-87 | RP-200345 | 1504 | 2 | B | Introduction of NR positioning | 16.0.0 | +| | RP-87 | RP-200358 | 1505 | - | B | Support of inter-RAT handover from NR to EN-DC in TS 38.331 | 16.0.0 | +| 07/2020 | RP-88 | RP-201191 | 1290 | 4 | C | Missing reportAddNeighMeas in periodic measurement reporting | 16.1.0 | +| | RP-88 | RP-201166 | 1453 | 6 | B | Introduction of NeedForGap capability for NR measurement | 16.1.0 | +| | RP-88 | RP-201185 | 1464 | 5 | B | Introduction of signalling for high-speed train scenarios | 16.1.0 | +| | RP-88 | RP-201191 | 1506 | 2 | F | Corrections to PRACH prioritization procedure for MPS and MCS | 16.1.0 | +| | RP-88 | RP-201182 | 1513 | 2 | F | Finalization of the support of Non-Public Networks | 16.1.0 | +| | RP-88 | RP-201172 | 1528 | 4 | F | Miscellaneous corrections for NR-U | 16.1.0 | +| | RP-88 | RP-201174 | 1540 | 2 | C | CR for 38.331 for Power Savings | 16.1.0 | +| | RP-88 | RP-201180 | 1553 | 3 | F | Correction to transfer of UE capabilities at HO for RACS and minor ASN.1 correction (38.331) | 16.1.0 | +| | RP-88 | RP-201161 | 1556 | 2 | A | Clarification on avoiding keystream repeat due to COUNT reuse | 16.1.0 | +| | RP-88 | RP-201178 | 1557 | 2 | F | CR for 38.331 on CA/DC Enhancements | 16.1.0 | +| | RP-88 | RP-201160 | 1560 | 2 | A | SRS Capability report for SRS only Scell | 16.1.0 | +| | RP-88 | RP-201160 | 1562 | 1 | A | Correction to RequestedCapabilityCommon | 16.1.0 | +| | RP-88 | RP-201187 | 1563 | 2 | A | CR on introduction of BCS to asymmetric channel bandwidths (38.331) | 16.1.0 | +| | RP-88 | RP-201159 | 1568 | 2 | A | Correction on PUCCH configuration | 16.1.0 | +| | RP-88 | RP-201176 | 1569 | 3 | F | Miscellaneous corrections to 38.331 for V2X | 16.1.0 | +| | RP-88 | RP-201160 | 1572 | 2 | A | Correction on the need for reconfiguration with sync in (NG)EN-DC, NR-DC and NE-DC | 16.1.0 | +| | RP-88 | RP-201160 | 1579 | 1 | A | 38331 CR(R16) on inter-RAT SFTD measurements | 16.1.0 | + +| | | | | | | | | +|--|-------|-----------|------|---|----------|---------------------------------------------------------------------------------|--------| +| | RP-88 | RP-201160 | 1587 | 1 | A | Clarification on pdcp-Duplication at RRC Reconfiguration | 16.1.0 | +| | RP-88 | RP-201188 | 1588 | 3 | F | Correction to RRC spec for eURLLC | 16.1.0 | +| | RP-88 | RP-201179 | 1590 | 4 | B | Corrections to 38.331 for supporting IAB in NPN | 16.1.0 | +| | RP-88 | RP-201177 | 1591 | 2 | F | Corrections on NR mobility enhancements | 16.1.0 | +| | RP-88 | RP-201175 | 1592 | 2 | B | Introduction of RRC Positioning | 16.1.0 | +| | RP-88 | RP-201166 | 1596 | 1 | F | Band combination list for NE-DC (Cat-F) | 16.1.0 | +| | RP-88 | RP-201159 | 1599 | - | A | Avoiding security risk for RLC AM bearers during termination point change | 16.1.0 | +| | RP-88 | RP-201161 | 1602 | 1 | A | CR on SRS-CarrierSwitching | 16.1.0 | +| | RP-88 | RP-201164 | 1603 | 1 | A | CR on introduction of extended capabilities for NR-DC only BCs | 16.1.0 | +| | RP-88 | RP-201165 | 1614 | 1 | A | Clarification on the presence of ssb-perRACH-Occasion for the CSI-RS based CFRA | 16.1.0 | +| | RP-88 | RP-201163 | 1624 | 1 | A | Clarification on the maxPUSCH-Duration for LCP Restriction | 16.1.0 | +| | RP-88 | RP-201159 | 1631 | - | A | Clarification for SIB6, SIB7 and SIB8 acquisition during a measurement gap | 16.1.0 | +| | RP-88 | RP-201198 | 1632 | 2 | C | Introduction of secondary DRX group CR 38.331 | 16.1.0 | +| | RP-88 | RP-201164 | 1634 | 1 | A | Correction to CORESET and PDCCH TCI state release | 16.1.0 | +| | RP-88 | RP-201181 | 1641 | - | F | Correction of NR IloT | 16.1.0 | +| | RP-88 | RP-201162 | 1644 | 1 | A | Clarification on release and addition of the uplink for SCell | 16.1.0 | +| | RP-88 | RP-201189 | 1645 | - | F | CR on 38.331 for SRVCC from 5G to 3G | 16.1.0 | +| | RP-88 | RP-201159 | 1649 | - | A | Ambiguity in fr1-fr2-Add-UE-NR-Capabilities parameter | 16.1.0 | +| | RP-88 | RP-201162 | 1656 | 1 | A | Correction to measurement coordination in MR-DC | 16.1.0 | +| | RP-88 | RP-201176 | 1657 | 1 | F | Introduction of on-demand SIB(s) procedure in CONNECTED | 16.1.0 | +| | RP-88 | RP-201164 | 1662 | 1 | A | T310 handling during MobilityFromNR | 16.1.0 | +| | RP-88 | RP-201173 | 1664 | 2 | F | Corrections for 2-step Random Access Type | 16.1.0 | +| | RP-88 | RP-201216 | 1665 | 2 | B | Release-16 UE capabilities based on RAN1, RAN4 feature lists and RAN2 | 16.1.0 | +| | RP-88 | RP-201191 | 1666 | 1 | F | Miscellaneous ASN.1 review corrections | 16.1.0 | +| | RP-88 | RP-201166 | 1668 | 2 | F | Miscellaneous non-controversial corrections Set V | 16.1.0 | +| | RP-88 | RP-201184 | 1669 | 3 | F | Corrections on MDT and SON in NR | 16.1.0 | +| | RP-88 | RP-201190 | 1670 | - | C | Introduction of eCall over IMS for NR | 16.1.0 | +| | RP-88 | RP-201191 | 1671 | 1 | F | 38.331 CR for overheating in (NG)EN-DC and NR-DC | 16.1.0 | +| | RP-88 | RP-201186 | 1673 | 1 | B | Introduction of inter-frequency measurement without gap | 16.1.0 | +| | RP-88 | RP-201164 | 1682 | 2 | A | Correction on SRS antenna capability for carrier switching | 16.1.0 | +| | RP-88 | RP-201161 | 1683 | 1 | A | UE Capability Enhancement for FR1(TDD/FDD) / FR2 CA and DC | 16.1.0 | +| | RP-88 | RP-201164 | 1687 | 1 | A | Correction to re-sending UEAssistanceInformation upon reconfiguration w/ sync | 16.1.0 | +| | RP-88 | RP-201170 | 1696 | 4 | F | eMIMO corrections | 16.1.0 | +| | RP-88 | RP-201166 | 1697 | - | F | Corrections to SIB1 Processing | 16.1.0 | +| | RP-88 | RP-201171 | 1700 | - | F | Corrections for CLI | 16.1.0 | +| | RP-88 | RP-201191 | 1703 | 1 | F | Correction on MN-SN measurements coordination in INM | 16.1.0 | +| | RP-88 | RP-201163 | 1707 | - | A | SMTC Configuration for PSCell Addition for NR-DC (Option 2) | 16.1.0 | +| | RP-88 | RP-201165 | 1711 | 1 | A | Introduction of CGI reporting capabilities | 16.1.0 | +| | RP-88 | RP-201191 | 1716 | - | B | Aperiodic CSI-RS triggering with beam switching timing of 224 and 336 | 16.1.0 | +| | RP-88 | RP-201166 | 1717 | 1 | B | Implementing confirmation of code block group based transmission | 16.1.0 | +| | RP-88 | RP-201179 | 1718 | 1 | F | Correction to TS 38.331 for IAB WI | 16.1.0 | +| | RP-88 | RP-201183 | 1719 | - | B | RRC configuration of supporting UL Tx switching | 16.1.0 | +| | RP-88 | RP-201183 | 1720 | - | B | UE capability of supporting UL Tx switching | 16.1.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|---------------------------------------------------------------------------------|--------| +| 09/2020 | RP-89 | RP-201929 | 1533 | 3 | F | CLI configuration | 16.2.0 | +| | RP-89 | RP-201922 | 1737 | 2 | F | Corrections to failure type for MCGFailureInformation and SCGFailureInformation | 16.2.0 | +| | RP-89 | RP-201937 | 1746 | 1 | A | Clarification on CG-ConfigInfo for NR-DC and NE-DC | 16.2.0 | +| | RP-89 | RP-201963 | 1747 | 1 | F | Miscellaneous corrections for NR IloT | 16.2.0 | +| | RP-89 | RP-201937 | 1749 | 1 | A | CR on SyncAndCellAdd condition | 16.2.0 | +| | RP-89 | RP-201937 | 1751 | 1 | A | CR to clarify UE behaviour after TAT expiry due to reconfigurationWithSync | 16.2.0 | +| | RP-89 | RP-201930 | 1755 | 2 | F | Handling of CPC in fast MCG recovery | 16.2.0 | +| | RP-89 | RP-201986 | 1756 | 4 | B | Release-16 UE capabilities based on RAN1, RAN4 feature lists and RAN2 | 16.2.0 | +| | RP-89 | RP-201989 | 1757 | 1 | F | Minor corrections and update for RRC Positioning | 16.2.0 | +| | RP-89 | RP-201938 | 1764 | 1 | F | Correction on the Cross Carrier Scheduling Configuration | 16.2.0 | +| | RP-89 | RP-201922 | 1768 | 2 | F | Correction on the Configuration of sCellState for 38.331 | 16.2.0 | +| | RP-89 | RP-201930 | 1771 | - | F | Minor Correction for Mobility Further Enhancement | 16.2.0 | +| | RP-89 | RP-201989 | 1779 | - | F | Corrections to acquisition of posSIB(s) in RRC_CONNECTED | 16.2.0 | +| | RP-89 | RP-201989 | 1781 | 1 | F | Corrections to handing posSIB-MappingInfo in SIB1 | 16.2.0 | +| | RP-89 | RP-201938 | 1787 | 1 | F | SMTC Configuration for PSCell Addition and SN Change in NR-DC | 16.2.0 | +| | RP-89 | RP-201923 | 1794 | 1 | F | Corrections of RLF cause Signalling procedure | 16.2.0 | +| | RP-89 | RP-201937 | 1800 | 1 | A | CR on the BandCombination (R16) | 16.2.0 | +| | RP-89 | RP-201922 | 1803 | 1 | F | Adding enableDefaultBeamForCCS for cross-carrier scheduling with different SCS | 16.2.0 | +| | RP-89 | RP-201927 | 1810 | 1 | F | Correction on cross-RAT V2X functionality in TS 38.331 | 16.2.0 | +| | RP-89 | RP-201930 | 1818 | - | F | Time misalignment in DAPS DRB configuration (Alt.2) | 16.2.0 | +| | RP-89 | RP-201927 | 1820 | 2 | F | Miscellaneous correction regarding on demand SIB in CONNECTED | 16.2.0 | +| | RP-89 | RP-201927 | 1821 | 2 | F | Redundant procedural text of on demand SIB in CONNECTED | 16.2.0 | +| | RP-89 | RP-201922 | 1823 | - | F | Correction to field condition on reFR2ServCellAsyncCA | 16.2.0 | +| | RP-89 | RP-201930 | 1836 | - | F | Corrections to Conditional Reconfiguration triggering | 16.2.0 | +| | RP-89 | RP-201921 | 1844 | 3 | F | RRC clarifications for NR-U | 16.2.0 | +| | RP-89 | RP-201930 | 1845 | 1 | F | Clarification on TS38.331 for DAPS | 16.2.0 | +| | RP-89 | RP-201930 | 1847 | - | F | T312 handling during Mobility from NR | 16.2.0 | +| | RP-89 | RP-201930 | 1850 | 2 | F | Correction on the RLF for NR DAPS | 16.2.0 | +| | RP-89 | RP-201932 | 1852 | 1 | F | Correction on beamSwitchTiming values of 224 and 336 | 16.2.0 | +| | RP-89 | RP-201930 | 1861 | - | F | RLF in source cell during DAPS handover | 16.2.0 | +| | RP-89 | RP-201929 | 1862 | 2 | F | Misc. corrections CR for 38.331 for Power Savings | 16.2.0 | +| | RP-89 | RP-201920 | 1863 | 3 | F | Miscellaneous eMIMO corrections | 16.2.0 | +| | RP-89 | RP-201922 | 1864 | 1 | F | Missing fields for Toffset coordination in INM | 16.2.0 | +| | RP-89 | RP-201922 | 1865 | 1 | F | Misc corrections for Rel-16 DCCA | 16.2.0 | +| | RP-89 | RP-201930 | 1866 | - | F | Correction of field description for Mobility Enhancements | 16.2.0 | +| | RP-89 | RP-201930 | 1868 | 1 | F | Correction of description of CHO events for Mobility Enhancements | 16.2.0 | +| | RP-89 | RP-201932 | 1869 | 1 | F | ASN.1 corrections to maintain backwards compatibility | 16.2.0 | +| | RP-89 | RP-201920 | 1870 | 1 | F | Remaining ASN.1 review issues | 16.2.0 | +| | RP-89 | RP-201938 | 1872 | 1 | A | Miscellaneous non-controversial corrections Set VII | 16.2.0 | +| | RP-89 | RP-201925 | 1873 | 1 | B | Introduction of MPE reporting | 16.2.0 | +| | RP-89 | RP-201930 | 1874 | - | F | Corrections to Mobility Enhancements | 16.2.0 | +| | RP-89 | RP-201937 | 1878 | - | A | Clarification on scg-RB-Config | 16.2.0 | +| | RP-89 | RP-201922 | 1879 | 1 | F | Correction on storing SCG configuration in UE INACTIVE AS context | 16.2.0 | +| | RP-89 | RP-201930 | 1886 | - | F | Timer handling upon initiation of RRC re-establishment | 16.2.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|------------------------------------------------------------------------------------------------------------------------|--------| +| | RP-89 | RP-201930 | 1888 | - | F | No support of DAPS HO for a CHO candidate cell | 16.2.0 | +| | RP-89 | RP-201930 | 1898 | - | F | Correction on TS38.331 for CHO | 16.2.0 | +| | RP-89 | RP-201938 | 1908 | 1 | A | Correction on UE assistance information transmission for handover case | 16.2.0 | +| | RP-89 | RP-201931 | 1911 | 2 | F | Correction on the UE Capability presence upon SN addition and SN change | 16.2.0 | +| | RP-89 | RP-201928 | 1924 | 1 | F | Correction on msgA-PUSCH-Config | 16.2.0 | +| | RP-89 | RP-201989 | 1925 | 1 | F | Introduction of PRS measurement gap | 16.2.0 | +| | RP-89 | RP-201927 | 1930 | 1 | F | Miscellaneous corrections on TS 38.331 | 16.2.0 | +| | RP-89 | RP-201930 | 1936 | - | F | Correction on NR CHO | 16.2.0 | +| | RP-89 | RP-201929 | 1937 | 1 | F | Miscellaneous RRC corrections for NR eURLLC | 16.2.0 | +| | RP-89 | RP-201932 | 1948 | 1 | F | Correction on HO from NR to EN-DC | 16.2.0 | +| | RP-89 | RP-201923 | 1952 | 1 | F | Corrections on F1-C transfer path | 16.2.0 | +| | RP-89 | RP-201923 | 1954 | - | F | Corrections on default BH RLC channel | 16.2.0 | +| | RP-89 | RP-201923 | 1955 | 1 | F | Correction on the value range of BH-LogicalChannelIdentity-Ext | 16.2.0 | +| | RP-89 | RP-201923 | 1956 | - | F | Correction on cellReservedForOperatorUse | 16.2.0 | +| | RP-89 | RP-201923 | 1957 | 1 | F | Correction on SearchSpace configuration for IAB | 16.2.0 | +| | RP-89 | RP-201923 | 1958 | - | F | Corrections on the IAB-MT TDD resource configuration | 16.2.0 | +| | RP-89 | RP-201932 | 1961 | 4 | B | CR for Early Implementation in NR | 16.2.0 | +| | RP-89 | RP-201932 | 1969 | 1 | F | CR on UE behavior with E-UTRA cell selection upon mobility from NR failure for enhanced EPS voice fallback | 16.2.0 | +| | RP-89 | RP-201930 | 1974 | 1 | F | CR on drb-ContinueROHC for DAPS | 16.2.0 | +| | RP-89 | RP-201921 | 1976 | 2 | F | Miscellaneous corrections for NR-U | 16.2.0 | +| | RP-89 | RP-201937 | 1979 | 1 | A | Reconfiguring RoHC and setting the drb-ContinueROHC simultaneously | 16.2.0 | +| | RP-89 | RP-201938 | 1986 | 1 | A | Clarification on the SRB configuration for fullConfig during RRC Resume procedure | 16.2.0 | +| | RP-89 | RP-201930 | 1989 | 2 | F | Correction on field description of mrdc-SecondaryCellGroup in NR-DC | 16.2.0 | +| | RP-89 | RP-201927 | 1991 | 2 | F | CR to 38.331 on SLSS ID | 16.2.0 | +| | RP-89 | RP-201927 | 1992 | 1 | F | Correction on RRC parameters for 5G V2X with NR sidelink | 16.2.0 | +| | RP-89 | RP-201922 | 1993 | - | F | Correction on HARQ ACK spatial bundling configurations for secondary PUCCH group | 16.2.0 | +| | RP-89 | RP-201924 | 1994 | 1 | F | Update to IAB-MT capabilities | 16.2.0 | +| | RP-89 | RP-201927 | 1995 | - | F | Adding notes for joint success and failure in crossRAT SL | 16.2.0 | +| | RP-89 | RP-201927 | 1997 | - | F | Corrections on RAN1 related clarifications | 16.2.0 | +| | RP-89 | RP-201931 | 1998 | - | D | Editorial corrections on MDT and SON in NR | 16.2.0 | +| | RP-89 | RP-201931 | 1999 | - | F | Correction to MDT features | 16.2.0 | +| | RP-89 | RP-201931 | 2000 | - | F | Correction to SON features | 16.2.0 | +| | RP-89 | RP-201928 | 2001 | - | F | Corrections for NPNS | 16.2.0 | +| | RP-89 | RP-201927 | 2002 | - | F | Clarification on UL and SL priority thresholds | 16.2.0 | +| | RP-89 | RP-201924 | 2003 | - | F | Miscellaneous IAB Corrections | 16.2.0 | +| | RP-89 | RP-201962 | 2007 | 1 | F | Miscellaneous corrections on UL Tx switching | 16.2.0 | +| | RP-89 | RP-201925 | 2008 | - | B | Configuration for uplink power boosting via suspended IBE requirements | 16.2.0 | +| | RP-89 | RP-201922 | 2009 | - | F | NR-DC UE capabilities | 16.2.0 | +| | RP-89 | RP-201927 | 2010 | 1 | F | Correction on the calculation of CG occasion | 16.2.0 | +| 12/2020 | RP-90 | RP-202775 | 1775 | 2 | F | NR CA additional spectrum emission requirements | 16.3.0 | +| | RP-90 | RP-202777 | 2017 | - | B | Configuration for directional collision handling between reference cell and other cell for half-duplex operation in CA | 16.3.0 | +| | RP-90 | RP-202773 | 2021 | 1 | F | Clarification on referenceTimePreferenceReporting in RRC Reconfiguration Procedure | 16.3.0 | + +| | | | | | | | | +|--|-------|-----------|------|---|---|------------------------------------------------------------------------------------|--------| +| | RP-90 | RP-202790 | 2029 | - | F | Correction on UAI during handover | 16.3.0 | +| | RP-90 | RP-202771 | 2038 | 1 | F | Correction to PDSCH TDRA for DCI 1-2 | 16.3.0 | +| | RP-90 | RP-202789 | 2040 | 1 | A | Correction for configuration of SRS Carrier Switching | 16.3.0 | +| | RP-90 | RP-202767 | 2042 | 1 | F | Correction to NR-U Energy Detection Threshold configuration | 16.3.0 | +| | RP-90 | RP-202778 | 2051 | 1 | B | Release-16 UE capabilities based on RAN1, RAN4 feature lists and RAN2 | 16.3.0 | +| | RP-90 | RP-202767 | 2052 | - | F | Correction of field description for ra-ResponseWindow | 16.3.0 | +| | RP-90 | RP-202767 | 2055 | - | F | Clarification on HARQ process sharing for CGs | 16.3.0 | +| | RP-90 | RP-202790 | 2059 | 1 | A | Corrections on the configurations of HARQ-ACK spatial bundling and CBG in 38.331 | 16.3.0 | +| | RP-90 | RP-202774 | 2061 | 1 | F | Clarification on no support of CA, DC or multi-TRP with DAPS | 16.3.0 | +| | RP-90 | RP-202790 | 2064 | 1 | A | Corrections on PDCP duplication capability for NR-DC | 16.3.0 | +| | RP-90 | RP-202790 | 2066 | 1 | F | Clarification on SIB mapping to SI message | 16.3.0 | +| | RP-90 | RP-202776 | 2075 | 1 | F | UE assistance information for DRX preference | 16.3.0 | +| | RP-90 | RP-202767 | 2091 | 1 | F | Miscellaneous corrections for NR-U | 16.3.0 | +| | RP-90 | RP-202768 | 2107 | 2 | F | UE behaviour when UL 7.5KHz shift is not supported | 16.3.0 | +| | RP-90 | RP-202772 | 2122 | 1 | F | Correction on non-DRB for IAB-MT | 16.3.0 | +| | RP-90 | RP-202772 | 2124 | 1 | F | Corrections on BH RLC channel | 16.3.0 | +| | RP-90 | RP-202772 | 2125 | 1 | F | Corrections on RLF cause determination | 16.3.0 | +| | RP-90 | RP-202790 | 2130 | 1 | F | Correction on uac-AccessCategory1-SelectionAssistanceInfo | 16.3.0 | +| | RP-90 | RP-202790 | 2134 | 2 | F | Miscellaneous non-controversial corrections Set VIII | 16.3.0 | +| | RP-90 | RP-202775 | 2142 | 2 | F | Correction on field description of configuredGrantConfigType2DeactivationStateList | 16.3.0 | +| | RP-90 | RP-202776 | 2145 | 1 | F | Correction on RRC state preference | 16.3.0 | +| | RP-90 | RP-202789 | 2146 | 1 | F | Clarifications for the common search space on the active BWP | 16.3.0 | +| | RP-90 | RP-202771 | 2149 | 1 | F | Corrections to 2-Step RA | 16.3.0 | +| | RP-90 | RP-202777 | 2151 | - | F | Discarding of stored DL RRC message segments when UE transitions to RRC_IDLE | 16.3.0 | +| | RP-90 | RP-202771 | 2159 | - | F | Correction on BFD resource on SCell | 16.3.0 | +| | RP-90 | RP-202770 | 2161 | 2 | F | Misc corrections for Rel-16 DCCA | 16.3.0 | +| | RP-90 | RP-202770 | 2163 | - | F | Missing fields for Toffset coordination | 16.3.0 | +| | RP-90 | RP-202770 | 2166 | 1 | F | Processing delay requirements for DLInformationTransferMRDC | 16.3.0 | +| | RP-90 | RP-202773 | 2175 | 1 | F | Correction regarding reconfigure EHC | 16.3.0 | +| | RP-90 | RP-202770 | 2178 | - | C | Processing delay requirements for RRC resume | 16.3.0 | +| | RP-90 | RP-202770 | 2180 | 1 | F | Correction for fast MCG link recovery in (NG)EN-DC | 16.3.0 | +| | RP-90 | RP-202771 | 2181 | 2 | F | Correction on HARQ ACK/NACK feedback configuration | 16.3.0 | +| | RP-90 | RP-202771 | 2182 | 2 | F | Correction on slot based repetition | 16.3.0 | +| | RP-90 | RP-202772 | 2184 | 1 | F | RRC Miscellaneous Corrections | 16.3.0 | +| | RP-90 | RP-202772 | 2192 | 1 | F | Support of Rel-16 features for SCG in EN-DC and NR-DC | 16.3.0 | +| | RP-90 | RP-202775 | 2198 | 1 | F | Correction on acquisition of MLB and SIB1 | 16.3.0 | +| | RP-90 | RP-202775 | 2199 | - | F | Correction on possIB broadcastStatus | 16.3.0 | +| | RP-90 | RP-202776 | 2215 | - | F | Clarification on SRVCC handover | 16.3.0 | +| | RP-90 | RP-202769 | 2230 | 1 | F | Miscellaneous corrections on TS 38.331 | 16.3.0 | +| | RP-90 | RP-202771 | 2250 | 1 | C | 38331 CR for CSI-RS-ResourceConfigMobility | 16.3.0 | +| | RP-90 | RP-202775 | 2254 | - | F | Correction on T321 for autonomous gap based CGI in FR2 | 16.3.0 | +| | RP-90 | RP-202772 | 2265 | - | F | Transmission suspension on BH RLC channel upon IAB-MT failure | 16.3.0 | +| | RP-90 | RP-202790 | 2273 | 3 | A | CR on TS 38.331 for LCP restriction of configured grant type 1 | 16.3.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|---------------------------------------------------------------------------------------------------|--------| +| | RP-90 | RP-202769 | 2274 | - | F | Correction on RRC parameters for NR SL communication | 16.3.0 | +| | RP-90 | RP-202771 | 2276 | 3 | F | Introduction of capability bit for multi-CC simultaneous TCI activation with multi-TRP | 16.3.0 | +| | RP-90 | RP-202771 | 2277 | 1 | F | Selecting index for PLMN, SNPN and UAC parameters | 16.3.0 | +| | RP-90 | RP-202775 | 2278 | - | F | Positioning RRC updates for posSIB validity check and field description correction | 16.3.0 | +| | RP-90 | RP-202774 | 2280 | - | F | Miscellaneous corrections for conditional reconfiguration | 16.3.0 | +| | RP-90 | RP-202774 | 2282 | - | F | Miscellaneous corrections for DAPS (NR) | 16.3.0 | +| | RP-90 | RP-202773 | 2284 | 1 | F | Corrections for PDCP duplication introduced in IIoT | 16.3.0 | +| | RP-90 | RP-202769 | 2285 | - | F | Corrections on sidelink related RRC procedures | 16.3.0 | +| | RP-90 | RP-202770 | 2287 | - | A | Dummify UE capability of crossCarrierScheduling-OtherSCS | 16.3.0 | +| | RP-90 | RP-202776 | 2293 | - | F | RRC corrections on NR SON and MDT | 16.3.0 | +| | RP-90 | RP-202770 | 2294 | - | F | CR for Unaligned CA signalling in TS 38.331 | 16.3.0 | +| | RP-90 | RP-202767 | 2295 | - | F | Name change of the UE capability for the extended RAR window monitoring | 16.3.0 | +| | RP-90 | RP-202884 | 2297 | - | A | CR to 38.331 on handling of fallbacks for FR2 CA | 16.3.0 | +| 01/2021 | RP-90 | | | | | Corrected the extension marker in type PosSchedulingInfo-r16 so that it passes ASN.1 syntax check | 16.3.1 | +| 03/2021 | RP-91 | RP-210693 | 2034 | 3 | F | Corrections to acquisition of positioning SIBs | 16.4.0 | +| | RP-91 | RP-210702 | 2036 | 3 | A | Clarification to usage of ConfigRestrictModReqSCG | 16.4.0 | +| | RP-91 | RP-210695 | 2147 | 1 | F | Clarification for aperiodic CSI and secondary DRX group | 16.4.0 | +| | RP-91 | RP-210701 | 2237 | 1 | A | Clarification on P-max in FrequencyInfoUL in FR2 | 16.4.0 | +| | RP-91 | RP-210690 | 2298 | 1 | F | Correction on the Handling of Reconfiguration within RRC Resume | 16.4.0 | +| | RP-91 | RP-210690 | 2300 | 1 | F | Clarification on Fast MCG Link Recovery | 16.4.0 | +| | RP-91 | RP-210692 | 2301 | 1 | F | CR on co-configuration of Rel-16 features | 16.4.0 | +| | RP-91 | RP-210689 | 2302 | 2 | F | Correction on reset configuration | 16.4.0 | +| | RP-91 | RP-210689 | 2303 | 1 | F | Clarification on the inter-frequency operation | 16.4.0 | +| | RP-91 | RP-210694 | 2306 | 1 | F | Correction on RSSI and channel occupancy measurements | 16.4.0 | +| | RP-91 | RP-210689 | 2315 | 1 | F | Correction on value range of sl-ConfigIndexCG and sl-HARQ-Procid-offset | 16.4.0 | +| | RP-91 | RP-210693 | 2317 | 1 | F | Clarifications on the required posSIB | 16.4.0 | +| | RP-91 | RP-210697 | 2321 | 1 | F | UE capability of NR to UTRA-FDD CELL_DCH CS handover | 16.4.0 | +| | RP-91 | RP-210693 | 2322 | - | F | Corrections on posSIB validity | 16.4.0 | +| | RP-91 | RP-210694 | 2325 | 1 | F | CR on 38.331 for power saving | 16.4.0 | +| | RP-91 | RP-210701 | 2333 | - | A | CR on SyncAndCellAdd condition | 16.4.0 | +| | RP-91 | RP-210693 | 2341 | 1 | F | RA report and Logged MDT Info extendibility | 16.4.0 | +| | RP-91 | RP-210692 | 2346 | 1 | F | Support of NUL and SUL during DAPS handover | 16.4.0 | +| | RP-91 | RP-210694 | 2360 | - | F | Clarification on NR-U RSSI measurement procedure | 16.4.0 | +| | RP-91 | RP-210703 | 2371 | - | F | Correction to measResultServingMOList impacting EN-DC | 16.4.0 | +| | RP-91 | RP-210695 | 2377 | 2 | B | Inter-node messaging for supporting intra-band EN-DC scenarios | 16.4.0 | +| | RP-91 | RP-210692 | 2379 | - | F | Dummifying intraFreqMultiUL-TransmissionDAPS-r16 capability | 16.4.0 | +| | RP-91 | RP-210690 | 2384 | - | F | HARQ-ACK codebook configuration for secondary PUCCH group | 16.4.0 | +| | RP-91 | RP-210690 | 2385 | 1 | F | Misc corrections for Rel-16 DCCA | 16.4.0 | +| | RP-91 | RP-210694 | 2387 | - | F | RRC corrections for NR-U | 16.4.0 | +| | RP-91 | RP-210689 | 2391 | 3 | F | Correction on SL configured grant type 1 validity under Uu RLF | 16.4.0 | +| | RP-91 | RP-210692 | 2392 | 2 | F | Inability to comply with conditional reconfiguration | 16.4.0 | +| | RP-91 | RP-210691 | 2398 | 2 | F | Miscellaneous corrections on IAB in 38.331 | 16.4.0 | +| | RP-91 | RP-210703 | 2400 | 1 | F | Miscellaneous non-controversial corrections Set IX | 16.4.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|---------------------------------------------------------------------------------------------------------------------------------------------|--------| +| | RP-91 | RP-210695 | 2401 | 1 | F | Correction on complete message at handover from NR to EN-DC | 16.4.0 | +| | RP-91 | RP-210703 | 2402 | 1 | F | Release with Redirect for connection resume triggered by NAS | 16.4.0 | +| | RP-91 | RP-210691 | 2404 | - | F | Correction on the configuration of Type 1 configured grant | 16.4.0 | +| | RP-91 | RP-210703 | 2405 | 1 | F | NR RRC processing time with segmentation | 16.4.0 | +| | RP-91 | RP-210691 | 2407 | 1 | F | Introduction of UE Capability and Configuration for SpCell BFR Enhancement | 16.4.0 | +| | RP-91 | RP-210695 | 2414 | 2 | F | ASN.1 guidelines for extension of lists using ToAddMod structure | 16.4.0 | +| | RP-91 | RP-210692 | 2417 | 2 | F | Corrections for DAPS Handover | 16.4.0 | +| | RP-91 | RP-210689 | 2418 | 1 | F | CR on measurement object modification | 16.4.0 | +| | RP-91 | RP-210692 | 2419 | 1 | F | Clarification on ULInformationTransferMRDC message | 16.4.0 | +| | RP-91 | RP-210690 | 2422 | 1 | F | Clarification on sCellState configuration upon SCell modification | 16.4.0 | +| | RP-91 | RP-210691 | 2427 | 1 | F | Corrections on BAP address and default BAP configuration | 16.4.0 | +| | RP-91 | RP-210691 | 2428 | 2 | F | Corrections on the default configuration with Need M | 16.4.0 | +| | RP-91 | RP-210693 | 2429 | 1 | F | Corrections on NR MDT and SON | 16.4.0 | +| | RP-91 | RP-210693 | 2433 | 1 | F | Clarification for SIBs scheduled in posSchedulingInfoList | 16.4.0 | +| | RP-91 | RP-210690 | 2436 | 2 | F | Correction on tci-PresentInDCI | 16.4.0 | +| | RP-91 | RP-210689 | 2437 | 1 | F | Miscellaneous corrections on TS 38.331 | 16.4.0 | +| | RP-91 | RP-210689 | 2440 | 2 | F | Correction on C-RNTI replacement and conditions for 2-step RA | 16.4.0 | +| | RP-91 | RP-210689 | 2445 | 1 | F | Stop conditions of T320 in NR protocols | 16.4.0 | +| | RP-91 | RP-210697 | 2447 | 1 | F | CR on the Capability of PUCCH Transmissions for HARQ-ACK-38331 | 16.4.0 | +| | RP-91 | RP-210694 | 2448 | 1 | F | UTRA capabilities forwarding in handover preparation | 16.4.0 | +| | RP-91 | RP-210693 | 2449 | 1 | F | Correction on SI window calculation for PosSIB | 16.4.0 | +| | RP-91 | RP-210692 | 2450 | - | F | [Post112-e][254][R16 MOB] Clarification of behaviour to avoid security risk in CHO based recovery after handover without key change failure | 16.4.0 | +| | RP-91 | RP-210693 | 2457 | - | F | Misc corrections on SON and MDT | 16.4.0 | +| | RP-91 | RP-210689 | 2458 | - | F | Correction to 38.331 on intra-frequency reselection | 16.4.0 | +| | RP-91 | RP-210689 | 2460 | - | F | T400 expiry in timer table and protection of RRC messages | 16.4.0 | +| | RP-91 | RP-210692 | 2461 | - | F | Correction on NR Mobility Enhancement | 16.4.0 | +| | RP-91 | RP-210690 | 2462 | - | F | CR on serving cell reporting | 16.4.0 | +| | RP-91 | RP-210697 | 2463 | - | F | Capability for dormant BWP switching of multiple SCells | 16.4.0 | +| | RP-91 | RP-210695 | 2466 | - | F | Correction to PUSCH skipping with UCI without LCH-based prioritization | 16.4.0 | +| | RP-91 | RP-210693 | 2467 | - | F | Corrections on NR MDT and SON | 16.4.0 | +| | RP-91 | RP-210692 | 2468 | 1 | F | Correction on inter-node signalling for DAPS UE capability coordination | 16.4.0 | +| | RP-91 | RP-210702 | 2469 | - | A | Dummy the capability bit v2x-EUTRA | 16.4.0 | +| | RP-91 | RP-210630 | 2470 | 1 | B | Release-16 UE capabilities based on updated RAN1 and RAN4 feature lists | 16.4.0 | +| | RP-91 | RP-210693 | 2471 | - | B | Uplink Tx DC location reporting for two carrier uplink CA | 16.4.0 | +| | RP-91 | | | | | MCC: replaced all "v16xy" with "v1640" | 16.4.1 | +| 06/2021 | RP-92 | RP-211487 | 2413 | 6 | C | Redirection with MPS Indication [Redirect_MPS_I] | 16.5.0 | +| | RP-92 | RP-211474 | 2475 | 3 | F | Corrections to the UE action upon SIB1 reception | 16.5.0 | +| | RP-92 | RP-211470 | 2477 | 1 | F | Correction on parameters of SL configured grant | 16.5.0 | +| | RP-92 | RP-211474 | 2490 | 2 | F | Corrections on the descriptions of SRS-Config | 16.5.0 | +| | RP-92 | RP-211475 | 2494 | 2 | F | Correction on T321 for autonomous gap based CGI reporting in LTE | 16.5.0 | +| | RP-92 | RP-211482 | 2496 | 2 | A | CR on RRC processing delay | 16.5.0 | +| | RP-92 | RP-211475 | 2502 | 1 | F | CR on the configuration restriction on DCI format 0_2/1_2 for unlicensed band (Option 1) | 16.5.0 | +| | RP-92 | RP-211475 | 2505 | 2 | F | Correction on description of ssb-PositionsInBurst in ServingCellConfigCommonSIB | 16.5.0 | + +| | | | | | | | | +|--|-------|-----------|------|---|---|-----------------------------------------------------------------------------------------------|--------| +| | RP-92 | RP-211475 | 2508 | 1 | F | Correction on freqMonitorLocations | 16.5.0 | +| | RP-92 | RP-211486 | 2516 | 3 | A | Clean-up of INM procedure text | 16.5.0 | +| | RP-92 | RP-211485 | 2519 | 3 | F | Miscellaneous non-controversial corrections Set X | 16.5.0 | +| | RP-92 | RP-211485 | 2527 | 3 | A | Clarification on SCellIndex and servCellIndex | 16.5.0 | +| | RP-92 | RP-211484 | 2531 | 2 | A | Correction on firstActiveDownlinkBWP-Id | 16.5.0 | +| | RP-92 | RP-211471 | 2534 | 3 | F | Misc corrections for Rel-16 DCCA | 16.5.0 | +| | RP-92 | RP-211483 | 2540 | 2 | F | Correction on failureType in FailureReportSCG-EUTRA and scgFailureInfoEUTRA | 16.5.0 | +| | RP-92 | RP-211471 | 2543 | 2 | F | Clarification on NR SCG configuration within RRC Resume | 16.5.0 | +| | RP-92 | RP-211484 | 2550 | 3 | A | Clarification on SCS of active DL and UL BWP | 16.5.0 | +| | RP-92 | RP-211470 | 2551 | 3 | F | Miscellaneous corrections on TS 38.331 for NR V2X | 16.5.0 | +| | RP-92 | RP-211470 | 2552 | 3 | F | Corrections on TS 38.331 from the latest RAN1 decisions | 16.5.0 | +| | RP-92 | RP-211485 | 2556 | 2 | A | Clarification on RLC bearer handling in full configuration | 16.5.0 | +| | RP-92 | RP-211472 | 2557 | 2 | F | Miscellaneous corrections on BH RLC channel management for IAB-MT | 16.5.0 | +| | RP-92 | RP-211475 | 2561 | 3 | F | Correction on description of subCarrierSpacing in BWP | 16.5.0 | +| | RP-92 | RP-211470 | 2562 | 2 | F | Correction on releasing referenceTimePreferenceReporting and sl-AssistanceConfigNR | 16.5.0 | +| | RP-92 | RP-211484 | 2564 | 3 | A | Correction on T325 | 16.5.0 | +| | RP-92 | RP-211473 | 2565 | 2 | F | Full configuration for CHO | 16.5.0 | +| | RP-92 | RP-211485 | 2567 | 2 | A | Abortion of RRC connection resume handling | 16.5.0 | +| | RP-92 | RP-211470 | 2569 | 1 | F | Transmission of UEAssistanceInformation or SidelinkUEInformationNR after conditional handover | 16.5.0 | +| | RP-92 | RP-211483 | 2572 | 1 | A | Clarification on SCellFrequencies | 16.5.0 | +| | RP-92 | RP-211474 | 2574 | 1 | F | Correction for the positioning SI offset and clarification on mapping of posSIB to SI | 16.5.0 | +| | RP-92 | RP-211484 | 2579 | 2 | F | UL Config Grant capability differentiation for FR1(TDD/FDD) / FR2 | 16.5.0 | +| | RP-92 | RP-211474 | 2580 | 2 | F | Corrections on the UE capability of indication on supporting the extension of SRSresourceID | 16.5.0 | +| | RP-92 | RP-211483 | 2581 | 1 | F | Clarification on the initiation of RNA update | 16.5.0 | +| | RP-92 | RP-211478 | 2585 | 3 | B | Release-16 UE capabilities based on RAN1 and RAN4 feature lists | 16.5.0 | +| | RP-92 | RP-211472 | 2586 | - | F | Correction on repetition for L1-SINR | 16.5.0 | +| | RP-92 | RP-211475 | 2590 | - | F | Correction on reportSlotOffsetList | 16.5.0 | +| | RP-92 | RP-211486 | 2598 | 1 | F | Clarification on the Timing Reference of PSCell SMTC Configuration | 16.5.0 | +| | RP-92 | RP-211478 | 2599 | 1 | F | Introduction of the intra-NR and inter-RAT HST Capabilities and Configuration | 16.5.0 | +| | RP-92 | RP-211475 | 2600 | - | F | SSB-ToMeasure for NR-U | 16.5.0 | +| | RP-92 | RP-211482 | 2602 | - | A | Clarification on CGI reporting | 16.5.0 | +| | RP-92 | RP-211471 | 2605 | 1 | F | Miscellaneous Corrections to the SNPN | 16.5.0 | +| | RP-92 | RP-211474 | 2609 | - | C | Adding 400 Mhz and 600 MHz frequency separation classes | 16.5.0 | +| | RP-92 | RP-211482 | 2615 | - | A | Correction on CrossCarrierSchedulingConfig Introduced by Two PUCCH Group | 16.5.0 | +| | RP-92 | RP-211473 | 2616 | 1 | F | 38.331 Correction on Failure Recovery via CHO for Inter-RAT Handover Failure | 16.5.0 | +| | RP-92 | RP-211472 | 2619 | 1 | F | Miscellaneous corrections on IAB | 16.5.0 | +| | RP-92 | RP-211471 | 2626 | - | F | Correction on RNA configuration for UE in SNPN access mode | 16.5.0 | +| | RP-92 | RP-211470 | 2636 | 2 | F | Correction of Sidelink Configured Grant Type 1 Usage During Handover | 16.5.0 | +| | RP-92 | RP-211483 | 2639 | - | A | Introduction of DL scheduling slot offset capabilities in UERadioPagingInformation | 16.5.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|-----------------------------------------------------------------------------------------------------------|--------| +| | RP-92 | RP-211474 | 2644 | 2 | F | Clarifications on the TRP definition for positioning | 16.5.0 | +| | RP-92 | RP-211470 | 2647 | 1 | F | Configuration of search spaces for scheduling SL transmissions | 16.5.0 | +| | RP-92 | RP-211475 | 2652 | 1 | F | Correction on description of msg1-SubcarrierSpacing in RACH-ConfigCommon | 16.5.0 | +| | RP-92 | RP-211485 | 2667 | 1 | A | Correction on flow remapping to an added DRB | 16.5.0 | +| | RP-92 | RP-211483 | 2675 | - | A | Clarification on the frequency deprioritisation | 16.5.0 | +| | RP-92 | RP-211486 | 2686 | 1 | A | Correction on A-CSI trigger state configuration | 16.5.0 | +| | RP-92 | RP-211485 | 2690 | 1 | A | RLC and PDCP Re-establishment upon RRC resume/reestablishment | 16.5.0 | +| | RP-92 | RP-211471 | 2696 | - | F | CR on CGI reporting for NPN-only cell | 16.5.0 | +| | RP-92 | RP-211478 | 2699 | - | A | Correction to ca-ParametersNR-ForDC | 16.5.0 | +| | RP-92 | RP-211473 | 2700 | - | F | Clarification on non-coexistence of CHO and DAPS | 16.5.0 | +| | RP-92 | RP-211475 | 2702 | - | F | Extending number of cells for search space switching trigger configuration | 16.5.0 | +| | RP-92 | RP-211471 | 2703 | 2 | C | NR-DC Cell Group capability filtering | 16.5.0 | +| | RP-92 | RP-211478 | 2705 | - | A | CR on the Fallback Band Combination Removing-R16 | 16.5.0 | +| | RP-92 | RP-211471 | 2706 | - | F | SON-MDT Changes agreed in RAN2#114 meeting | 16.5.0 | +| 09/2021 | RP-93 | RP-212444 | 2708 | 1 | F | Correction on UL Skipping for PUSCH in Rel-16 | 16.6.0 | +| | RP-93 | RP-212442 | 2709 | 1 | F | Corrections to SIB validity for NPN only cell | 16.6.0 | +| | RP-93 | RP-212444 | 2714 | - | F | Early implementation of eCall over IMS in NR | 16.6.0 | +| | RP-93 | RP-212441 | 2715 | 1 | F | Miscellaneous corrections on TS 38.331 | 16.6.0 | +| | RP-93 | RP-212443 | 2716 | - | F | Corrections to intra-frequency cell reselection for MIB, SIB1 acquisition failure and TAC absence in SIB1 | 16.6.0 | +| | RP-93 | RP-212442 | 2723 | 1 | F | Correction on TCI configuration for DCI format 1_2 | 16.6.0 | +| | RP-93 | RP-212442 | 2728 | 1 | F | Correction to description of p0-AlphaSets | 16.6.0 | +| | RP-93 | RP-212442 | 2746 | 1 | F | Clarification on the NPN-IdentityInfoList | 16.6.0 | +| | RP-93 | RP-212442 | 2752 | 1 | F | Modification of measId for conditional reconfiguration | 16.6.0 | +| | RP-93 | RP-212443 | 2754 | 1 | F | MIB correction on subCarrierSpacingCommon | 16.6.0 | +| | RP-93 | RP-212442 | 2760 | - | F | Correction to 38.331 on the field description of msgA-TransMax | 16.6.0 | +| | RP-93 | RP-212440 | 2763 | 2 | F | Miscellaneous non-controversial corrections Set XI | 16.6.0 | +| | RP-93 | RP-212441 | 2776 | 1 | F | Corrections on RRC reconfiguration for fast MCG link recovery | 16.6.0 | +| | RP-93 | RP-212442 | 2777 | - | F | Correction on RepetitionSchemeConfig for eMIMO | 16.6.0 | +| | RP-93 | RP-212438 | 2780 | - | A | Correction on fallback band combination for SUL | 16.6.0 | +| | RP-93 | RP-212439 | 2785 | 1 | F | Clarification on RRC processing delay for HO from E-UTRA to NR | 16.6.0 | +| | RP-93 | RP-212443 | 2789 | 1 | F | CR for UE reporting Tx DC location info for the second PA | 16.6.0 | +| | RP-93 | RP-212438 | 2793 | - | A | Correction on inter-RAT measurement report triggering | 16.6.0 | +| | RP-93 | RP-212439 | 2799 | 2 | A | Correction on reconfigurationWithSync | 16.6.0 | +| | RP-93 | RP-212442 | 2800 | 1 | F | Correction to DAPS handover | 16.6.0 | +| | RP-93 | RP-212442 | 2801 | - | F | Corrections to pdsch-HARQ-ACK-CodeBookList | 16.6.0 | +| | RP-93 | RP-212443 | 2802 | - | F | SON-MDT Changes agreed in RAN2#115 meeting | 16.6.0 | +| | RP-93 | RP-212442 | 2803 | - | F | No support for CHO with SCG configuration | 16.6.0 | +| | RP-93 | RP-212440 | 2804 | 2 | F | CR to 38.331 on correcting Rel-15 failure type definition | 16.6.0 | +| | RP-93 | RP-212442 | 2807 | - | F | Handling of candidateBeamRSListExt-v1610 (option A1) | 16.6.0 | +| | RP-93 | RP-212440 | 2808 | - | F | FR1/FR2 differentiation for enhanced UL grant skipping capabilities | 16.6.0 | +| | RP-93 | RP-212598 | 2810 | 2 | C | Distinguishing support of extended band n77 | 16.6.0 | +| 12/2021 | RP-94 | RP-213341 | 2806 | 2 | A | Simultaneous Rx/Tx UE capability per band pair | 16.7.0 | +| | RP-94 | RP-213343 | 2814 | 1 | F | Correction on msgA-SubcarrierSpacing | 16.7.0 | +| | RP-94 | RP-213342 | 2815 | 1 | F | Miscellaneous corrections on TS 38.331 | 16.7.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|---------------------------------------------------------------------------------|--------| +| | RP-94 | RP-213342 | 2817 | 1 | C | Duty cycle signalling for power class 1.5 | 16.7.0 | +| | RP-94 | RP-213344 | 2819 | 1 | F | Correction for default value of rb-offset | 16.7.0 | +| | RP-94 | RP-213343 | 2822 | - | F | Correction on R16 UE capability of supportedSINR-meas-r16 | 16.7.0 | +| | RP-94 | RP-213344 | 2837 | 2 | F | Correction on description of absoluteFrequencySSB | 16.7.0 | +| | RP-94 | RP-213343 | 2842 | 1 | F | Correction on condRRCReconfig field description | 16.7.0 | +| | RP-94 | RP-213341 | 2844 | 1 | F | Miscellaneous non-controversial corrections Set XII | 16.7.0 | +| | RP-94 | RP-213343 | 2845 | 1 | F | Correction to need code for drb-ContinueEHC-DL and drb-ContinueEHC-UL | 16.7.0 | +| | RP-94 | RP-213343 | 2849 | 1 | F | Extension of pathlossReferenceRSs | 16.7.0 | +| | RP-94 | RP-213343 | 2857 | 1 | F | Correction on supportNewDMRS-Port-r16 capability | 16.7.0 | +| | RP-94 | RP-213343 | 2858 | 2 | F | Correction on pucch-SpatialRelationInfo-v1610 | 16.7.0 | +| | RP-94 | RP-213345 | 2859 | 1 | C | CR on 38.331 for introducing UE capability of txDiversity | 16.7.0 | +| | RP-94 | RP-213345 | 2862 | - | F | CR on inter-frequency gapless measurement | 16.7.0 | +| | RP-94 | RP-213344 | 2864 | 2 | F | SON-MDT changes agreed in RAN2#116 meeting | 16.7.0 | +| 03/2022 | RP-95 | RP-220835 | 2786 | 3 | F | Adding UE capability of UL MIMO coherence for UL Tx switching | 16.8.0 | +| | RP-95 | RP-220473 | 2874 | 1 | F | Correction to RRC reconfiguration for IAB | 16.8.0 | +| | RP-95 | RP-220835 | 2879 | 1 | F | Addition of missing description on mobility support for 5G SRVCC to 3G | 16.8.0 | +| | RP-95 | RP-220835 | 2880 | 1 | F | Handling of ServingCellConfigCommon | 16.8.0 | +| | RP-95 | RP-220835 | 2888 | 1 | F | Correction on UL skipping with LCH Prioritization in Rel-16 | 16.8.0 | +| | RP-95 | RP-220835 | 2897 | 1 | F | Correction on Positioning SRS | 16.8.0 | +| | RP-95 | RP-220472 | 2900 | 1 | F | Correction of NCC storage during re-establishment and Resume | 16.8.0 | +| | RP-95 | RP-220473 | 2903 | 1 | F | Miscellaneous corrections on TS 38.331 | 16.8.0 | +| | RP-95 | RP-220473 | 2911 | - | F | Correction on conditional reconfiguration execution for only one triggered cell | 16.8.0 | +| | RP-95 | RP-220473 | 2912 | 2 | F | Introduction of sidelink power class capability indication | 16.8.0 | +| | RP-95 | RP-220493 | 2917 | 1 | F | Correction on inclusion of selectedPLMN-Identity in RRCResumeComplete | 16.8.0 | +| | RP-95 | RP-220835 | 2929 | 1 | F | Correction on invalid symbol pattern | 16.8.0 | +| | RP-95 | RP-220472 | 2939 | - | A | Clarification on SN initiated release of an SCG | 16.8.0 | +| | RP-95 | RP-220473 | 2960 | 2 | F | Clarification on HighSpeedConfig for HST | 16.8.0 | +| | RP-95 | RP-220472 | 2969 | - | F | Miscellaneous non-controversial corrections Set XIII | 16.8.0 | +| 03/2022 | RP-95 | RP-220506 | 2459 | 2 | D | Inclusive Language Review for TS 38.331 | 17.0.0 | +| | RP-95 | RP-220499 | 2465 | 2 | C | Remove the maximum number of MIMO layers restrictions for SUL | 17.0.0 | +| | RP-95 | RP-220486 | 2811 | 5 | B | Introducing Enhancements to Integrated Access and Backhaul for NR | 17.0.0 | +| | RP-95 | RP-220837 | 2846 | 1 | B | Introduction of mobility-state-based cell reselection for NR HSDN [NR_HSDN] | 17.0.0 | +| | RP-95 | RP-220492 | 2865 | 2 | B | Introducing Enhancement of Data Collection for SON and MDT | 17.0.0 | +| | RP-95 | RP-220477 | 2878 | 1 | B | Introduction of NR dynamic spectrum sharing | 17.0.0 | +| | RP-95 | RP-220837 | 2883 | 1 | B | Introduction of MINT [MINT] | 17.0.0 | +| | RP-95 | RP-220481 | 2887 | 1 | B | Introduction of enhanced ILoT&URLLC support for NR | 17.0.0 | +| | RP-95 | RP-220472 | 2889 | 1 | F | Correction on PO determination for UE in inactive state | 17.0.0 | +| | RP-95 | RP-220475 | 2891 | 2 | B | Extending NR operation to 71 GHz | 17.0.0 | +| | RP-95 | RP-220500 | 2893 | 1 | B | Introduction of FR2 UL gap for Rel-17 | 17.0.0 | +| | RP-95 | RP-220497 | 2898 | 2 | B | Introduction of function for RRM enhancements for Rel-17 NR FR1 HST | 17.0.0 | +| | RP-95 | RP-220838 | 2901 | 1 | B | Release-17 UE capabilities based on R1 and R4 feature lists (TS38.331) | 17.0.0 | +| | RP-95 | RP-220476 | 2902 | 1 | B | RRC CR for NR Sidelink enhancement | 17.0.0 | +| | RP-95 | RP-220495 | 2904 | 1 | B | Introducing support of UP IP for EPC connected architectures using NR PDCP | 17.0.0 | +| | RP-95 | RP-220499 | 2909 | 1 | B | RRC configuration for R17 UL Tx switching enhancement | 17.0.0 | +| | RP-95 | RP-220491 | 2910 | 2 | B | Introduction of SL relay | 17.0.0 | +| | RP-95 | RP-220502 | 2913 | 2 | B | Introduction of RRC signaling for measurement gap enhancement | 17.0.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|-----------------------------------------------------------------------------------------------------|--------| +| | RP-95 | RP-220488 | 2919 | 1 | B | Introduction of NR RRC support for MUSIM | 17.0.0 | +| | RP-95 | RP-220490 | 2921 | 1 | B | NR RRC CR for RAN slicing | 17.0.0 | +| | RP-95 | RP-220474 | 2923 | 1 | B | Introduction of Release-17 feMIMO | 17.0.0 | +| | RP-95 | RP-220961 | 2924 | 3 | B | Introduction of ePowSav in TS 38.331 | 17.0.0 | +| | RP-95 | RP-220493 | 2925 | 1 | B | Introducing NPN enhancements: Credentials Holder, UE Onboarding, and IMS emergency support in SNPNS | 17.0.0 | +| | RP-95 | RP-220489 | 2927 | - | B | Introduction of the support for UDC in NR | 17.0.0 | +| | RP-95 | RP-220478 | 2928 | 2 | B | Introduction of NR coverage enhancements in RRC | 17.0.0 | +| | RP-95 | RP-220482 | 2930 | 2 | B | Introduction of Release-17 NTN | 17.0.0 | +| | RP-95 | RP-220498 | 2933 | 1 | B | HST on FR2 | 17.0.0 | +| | RP-95 | RP-220487 | 2937 | 1 | B | Introduction of SDT | 17.0.0 | +| | RP-95 | RP-220496 | 2940 | 1 | B | Introduction of DL 1024 QAM in NR | 17.0.0 | +| | RP-95 | RP-220484 | 2949 | 1 | B | Introduction of NR MBS into 38.331 | 17.0.0 | +| | RP-95 | RP-220836 | 2950 | 2 | B | Introduction of RedCap | 17.0.0 | +| | RP-95 | RP-220487 | 2951 | 1 | B | Introduction of Common RACH Partitioning Aspects | 17.0.0 | +| | RP-95 | RP-220479 | 2952 | 3 | B | Introduction of Enhanced Positioning feature | 17.0.0 | +| | RP-95 | RP-220853 | 2953 | 2 | B | Explicit Indication of SI Scheduling window position [SI-SCHEDULING] | 17.0.0 | +| | RP-95 | RP-220485 | 2954 | 2 | B | Introduction of further multi-RAT dual-connectivity enhancements | 17.0.0 | +| | RP-95 | RP-220494 | 2958 | 2 | B | Introduction of QoE measurements in NR | 17.0.0 | +| 06/2022 | RP-96 | RP-221736 | 2872 | 5 | B | Early Measurements for EPS fallback [IdleMeaEPSFB] | 17.1.0 | +| | RP-96 | RP-221721 | 2916 | 2 | B | CR on the CBM/IBM reporting-38331 | 17.1.0 | +| | RP-96 | RP-221756 | 2998 | 2 | B | Release-17 UE capabilities based on R1 and R4 feature lists (TS38.331) | 17.1.0 | +| | RP-96 | RP-221730 | 3014 | 3 | F | Correction of NR RRC support for MUSIM | 17.1.0 | +| | RP-96 | RP-221720 | 3021 | 1 | B | CR to TS 38.331 on Network assistant signalling for Rel-17 CRS interference mitigation | 17.1.0 | +| | RP-96 | RP-221724 | 3039 | 1 | F | Correction for NR coverage enhancements | 17.1.0 | +| | RP-96 | RP-221719 | 3040 | 1 | F | Corrections to TS 38.331 for RAN slicing | 17.1.0 | +| | RP-96 | RP-221715 | 3055 | 5 | F | RRC correction CR for 71 GHz | 17.1.0 | +| | RP-96 | RP-221755 | 3057 | 1 | F | Clarification and correction for measurement gap enhancement features | 17.1.0 | +| | RP-96 | RP-221713 | 3061 | 1 | A | Corrections on BAP entity release in MR DC release procedures in TS 38.331 | 17.1.0 | +| | RP-96 | RP-221736 | 3078 | 2 | C | Distinguishing support of band n77 restrictions in Canada [n77 Canada] | 17.1.0 | +| | RP-96 | RP-221736 | 3082 | 1 | F | Extension of the time domain resource allocation indicator for CG type 1 with typeB repetition | 17.1.0 | +| | RP-96 | RP-221712 | 3084 | - | A | Correction on FR1-FR1 power control parameters of NR-DC | 17.1.0 | +| | RP-96 | RP-221735 | 3086 | 2 | F | Correction CR for QoE Measurement Collection in NR | 17.1.0 | +| | RP-96 | RP-221717 | 3088 | 1 | F | Correction for NR NTN WI | 17.1.0 | +| | RP-96 | RP-221734 | 3089 | 1 | F | Corrections for eNPN from RAN2#118 | 17.1.0 | +| | RP-96 | RP-221722 | 3090 | 2 | F | Correction for feMIMO WI | 17.1.0 | +| | RP-96 | RP-221726 | 3093 | 2 | F | Correction for enhanced IIoT&URLLC support for NR | 17.1.0 | +| | RP-96 | RP-221723 | 3094 | - | F | Editorial correction for NR dynamic spectrum sharing | 17.1.0 | +| | RP-96 | RP-221729 | 3100 | 2 | F | SDT corrections | 17.1.0 | +| | RP-96 | RP-221721 | 3110 | 1 | F | Addressing FR2 UL gap RILs [Z151, Z152, A803, A804, A807, A808] | 17.1.0 | +| | RP-96 | RP-221725 | 3121 | 2 | F | Correction based upon Positioning RILs | 17.1.0 | +| | RP-96 | RP-221736 | 3122 | 1 | B | Introducing single-bit approach for MINT [MINT] | 17.1.0 | +| | RP-96 | RP-221718 | 3134 | 2 | F | Miscellaneous Rapporteur RRC corrections to IAB | 17.1.0 | +| | RP-96 | RP-221733 | 3136 | 2 | F | Miscellaneous rapporteur corrections for SON-MDT | 17.1.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|------------------------------------------------------------------------------------|--------| +| | RP-96 | RP-221728 | 3137 | 2 | F | Corrections for further MRDC enhancements | 17.1.0 | +| | RP-96 | RP-221754 | 3138 | 1 | F | MBS corrections for TS 38.331 | 17.1.0 | +| | RP-96 | RP-221711 | 3142 | - | A | Correction of Need Code in IE SearchSpace | 17.1.0 | +| | RP-96 | RP-221756 | 3144 | 1 | C | Adding UE capability of CSI reporting cross PUCCH SCell group | 17.1.0 | +| | RP-96 | RP-221732 | 3145 | 2 | F | Miscellaneous corrections for NR SL Relay | 17.1.0 | +| | RP-96 | RP-221716 | 3151 | 1 | F | Miscellaneous corrections for RedCap WI | 17.1.0 | +| | RP-96 | RP-221727 | 3154 | 2 | F | ePowSav corrections for 38.331 | 17.1.0 | +| | RP-96 | RP-221736 | 3164 | 2 | F | ASN1 review general corrections | 17.1.0 | +| | RP-96 | RP-221731 | 3170 | 1 | F | Correction for NR UDC in 38.331 | 17.1.0 | +| | RP-96 | RP-221756 | 3176 | - | A | New UE capability to limit PDCCH monitoring | 17.1.0 | +| | RP-96 | RP-221729 | 3177 | 2 | F | Correction for features applicable to RACH partitioning | 17.1.0 | +| | RP-96 | RP-221756 | 3179 | 1 | C | Introduction UE capability for CHO with SCG configuration [CHOwithDCkept] | 17.1.0 | +| | RP-96 | RP-221736 | 3181 | 1 | B | Introduction of gNB ID length reporting in the NR CGI report [gNB_ID_Length] | 17.1.0 | +| | RP-96 | RP-221730 | 3182 | - | F | Correction on UE behavior for NAS-based busy indication in RRC_INACTIVE | 17.1.0 | +| | RP-96 | RP-221736 | 3183 | - | C | Support of CHO with SCG configuration - 38331 [CHOwithDCkept] | 17.1.0 | +| | RP-96 | RP-221712 | 3185 | - | A | Miscellaneous corrections on TS 38.331 for NR V2X | 17.1.0 | +| | RP-96 | RP-221714 | 3186 | 1 | A | Clarification on the rmtc-Config-r16 | 17.1.0 | +| | RP-96 | RP-221728 | 3187 | 1 | F | Corrections for TRS-based SCell activation | 17.1.0 | +| | RP-96 | RP-221727 | 3190 | - | A | Addressing inconsistency for RRM measurement rules | 17.1.0 | +| | RP-96 | RP-221765 | 3193 | - | A | Introduction of uplink RRC Segmentation capability | 17.1.0 | +| | RP-96 | RP-221718 | 3194 | 1 | B | Introducing IAB MAC CE Configurations in RRC | 17.1.0 | +| | RP-96 | RP-221761 | 3195 | - | F | Miscellaneous non-controversial corrections Set XIV | 17.1.0 | +| | RP-96 | RP-221712 | 3197 | - | A | Correction for the need code and conditions for optional fields in PC5 RRC message | 17.1.0 | +| | RP-96 | RP-221563 | 3202 | - | F | Correction on SL DRX configuration for SL Relay | 17.1.0 | +| | RP-96 | RP-221794 | 3204 | 1 | A | HARQ-ACK multiplexing on PUSCH in the absence of PUCCH | 17.1.0 | +| | RP-96 | RP-221739 | 3205 | 1 | F | Corrections for SL enhancements | 17.1.0 | +| 09/2022 | RP-97 | RP-222524 | 3097 | 3 | B | Introduction of DC location report for more than 2CCs | 17.2.0 | +| | RP-97 | RP-222525 | 3237 | 3 | F | Correction on RRC for 71GHz | 17.2.0 | +| | RP-97 | RP-222527 | 3244 | 1 | B | Release-17 UE capabilities based on R1 and R4 feature lists (TS38.331) | 17.2.0 | +| | RP-97 | RP-222525 | 3254 | 1 | F | Miscellaneous CR on TS 38.331 for ePowSav | 17.2.0 | +| | RP-97 | RP-222519 | 3272 | - | A | Correction to 38.331 on NPN-only cell | 17.2.0 | +| | RP-97 | RP-222519 | 3281 | 1 | A | NR-DC Power Control | 17.2.0 | +| | RP-97 | RP-222516 | 3285 | 1 | A | Corrections on s-MeasureConfig in NR | 17.2.0 | +| | RP-97 | RP-222523 | 3289 | 2 | F | MBS corrections for RRC | 17.2.0 | +| | RP-97 | RP-222524 | 3303 | 2 | F | Correction CR for QoE Measurement Collection in NR | 17.2.0 | +| | RP-97 | RP-222523 | 3315 | 1 | F | Correction for Simultaneous Transmission of SR and PUSCH | 17.2.0 | +| | RP-97 | RP-222521 | 3321 | 1 | A | Correction for SRS-PeriodicityAndOffset | 17.2.0 | +| | RP-97 | RP-222522 | 3323 | 1 | F | Miscellaneous corrections to NR coverage enhancements | 17.2.0 | +| | RP-97 | RP-222523 | 3325 | 2 | F | Corrections for Release-17 feMIMO | 17.2.0 | +| | RP-97 | RP-222524 | 3326 | 2 | F | Corrections for Release-17 NTN | 17.2.0 | +| | RP-97 | RP-222525 | 3334 | 2 | F | Corrections on TS 38.331 for RAN Slicing | 17.2.0 | +| | RP-97 | RP-222525 | 3340 | 2 | F | RRC corrections for SDT | 17.2.0 | +| | RP-97 | RP-222518 | 3347 | 1 | A | Miscellaneous CR on 38.331 | 17.2.0 | +| | RP-97 | RP-222524 | 3348 | 2 | F | Miscellaneous corrections on TS 38.331 for SL enhancements | 17.2.0 | +| | RP-97 | RP-222520 | 3350 | - | A | Correction to add EHC context in UE Inactive AS context | 17.2.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|---------------------------------------------------------------------------------------------------|--------| +| | RP-97 | RP-222523 | 3351 | - | F | Correction to the field description of usage-pdc | 17.2.0 | +| | RP-97 | RP-222524 | 3353 | 2 | F | Miscellaneous correction for Positioning | 17.2.0 | +| | RP-97 | RP-222523 | 3355 | 1 | F | Rapporteur Miscellaneous RRC Corrections for eIAB | 17.2.0 | +| | RP-97 | RP-222526 | 3359 | 3 | F | Correction to MINT - applicableDisasterInfoList [MINT] | 17.2.0 | +| | RP-97 | RP-222525 | 3362 | 1 | F | Miscellaneous non-controversial corrections Set XV | 17.2.0 | +| | RP-97 | RP-222520 | 3395 | 1 | A | Correction of PUSCH repetition configuration | 17.2.0 | +| | RP-97 | RP-222518 | 3397 | 1 | A | Clarification of NULL security algorithm | 17.2.0 | +| | RP-97 | RP-222525 | 3400 | 1 | F | Miscellaneous corrections for RedCap WI | 17.2.0 | +| | RP-97 | RP-222516 | 3407 | 1 | A | Corrections on measurement report triggering | 17.2.0 | +| | RP-97 | RP-222520 | 3417 | 1 | A | Clarification on headerCompression for DAPS bearer | 17.2.0 | +| | RP-97 | RP-222522 | 3422 | 2 | F | Miscellaneous correction of NR RRC support for MUSIM | 17.2.0 | +| | RP-97 | RP-222519 | 3424 | 1 | A | Correction for PUSCH-PowerControl field descriptions for 2-step RACH | 17.2.0 | +| | RP-97 | RP-222520 | 3430 | 1 | A | Correction on PDCCH blind detection capability in CA | 17.2.0 | +| | RP-97 | RP-222517 | 3438 | 1 | A | CR on 38.331 for sn-FieldLength change for the case of bearer type change | 17.2.0 | +| | RP-97 | RP-222523 | 3440 | - | F | CR on 38.331 of field description in PUCCH-Config for PUCCH Carrier Switch | 17.2.0 | +| | RP-97 | RP-222518 | 3451 | 1 | A | Correction on Missing UE behavior on sidelink reset | 17.2.0 | +| | RP-97 | RP-222516 | 3453 | 1 | A | Clarification on codebookParametersPerBC parameter for extension of CSI-RS capabilities reporting | 17.2.0 | +| | RP-97 | RP-222519 | 3455 | 1 | A | Make PC1.5 an early implementation candidate | 17.2.0 | +| | RP-97 | RP-222522 | 3459 | 3 | F | Corrections for further MR-DC enhancements | 17.2.0 | +| | RP-97 | RP-222525 | 3465 | - | F | Correction on UE behaviour about UDC in RRC resume procedure | 17.2.0 | +| | RP-97 | RP-222524 | 3466 | 1 | F | RRC corrections for sidelink relay | 17.2.0 | +| | RP-97 | RP-222522 | 3467 | - | F | MsgA PUSCH resource release upon T304 expiry for SCG | 17.2.0 | +| | RP-97 | RP-222525 | 3469 | - | F | Correction for features applicable for common signalling for RACH Partitioning | 17.2.0 | +| | RP-97 | RP-222523 | 3470 | - | F | RRC Correction for SON MDT | 17.2.0 | +| | RP-97 | RP-222524 | 3471 | - | F | Correction on measurement gap enhancement configurations | 17.2.0 | +| | RP-97 | RP-222521 | 3473 | 1 | A | Correction on mpsPriorityIndication | 17.2.0 | +| | RP-97 | RP-222524 | 3474 | 2 | F | Correction for power-saving resource allocation | 17.2.0 | +| | RP-97 | RP-222524 | 3475 | - | F | Clarification on Joint Gap Configuration | 17.2.0 | +| | RP-97 | RP-222527 | 3477 | - | A | Correction to additionalSpectrumEmission for UL CA in n77 for the US | 17.2.0 | +| | RP-97 | RP-222527 | 3478 | - | F | Correction to additionalSpectrumEmission for UL CA in n77 for Canada | 17.2.0 | +| | RP-97 | RP-222526 | 3479 | - | B | Start drx-HARQ-RTT-TimerUL after last repetition [ulHARQ_RTT_Timer] | 17.2.0 | +| | RP-97 | RP-222524 | 3480 | - | F | Correction on maxNrofRemoteUE | 17.2.0 | +| | RP-97 | RP-222522 | 3481 | - | F | Corrections on CRS-IM network assistance information | 17.2.0 | +| | RP-97 | RP-222553 | 3483 | 1 | B | 38.331 CR for introduction of MBS PDSCH FDM capabilities | 17.2.0 | +| 12/2022 | RP-98 | RP-223404 | 3243 | 1 | A | Correction to firstOFDMSymbolInTimeDomain | 17.3.0 | +| | RP-98 | RP-223410 | 3276 | 5 | F | FR2-2 and CCA configuration | 17.3.0 | +| | RP-98 | RP-223414 | 3486 | 3 | F | Correction to explicit indication of SI Scheduling window position [SI-SCHEDULING] | 17.3.0 | +| | RP-98 | RP-223409 | 3497 | 2 | F | CRS-IM default network configuration assumptions for MBSFN configuration in non-DSS scenario | 17.3.0 | +| | RP-98 | RP-223406 | 3500 | 4 | F | MBS corrections for RRC | 17.3.0 | +| | RP-98 | RP-223410 | 3507 | 3 | F | Clarification on the NR HST configuration | 17.3.0 | +| | RP-98 | RP-223406 | 3532 | 1 | A | Correction on LCID assignment for SL LCH | 17.3.0 | +| | RP-98 | RP-223411 | 3534 | 5 | F | Miscellaneous correction for Positioning | 17.3.0 | +| | RP-98 | RP-223412 | 3541 | 3 | F | Rapporteur CR on TS 38.331 for SL enhancements | 17.3.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|---------------------------------------------------------------------------------------------------------------------------------------------|--------| +| | RP-98 | RP-223414 | 3548 | 3 | C | Correction on E-UTRA cell selection during emergency service fallback and EPS fallback for emergency call [CellSelection_EmergencyFallback] | 17.3.0 | +| | RP-98 | RP-223412 | 3549 | 3 | F | Miscellaneous RRC CR for SL relay | 17.3.0 | +| | RP-98 | RP-223414 | 3557 | 2 | F | Correction to disasterRoamingFromAnyPLMN [MINT] | 17.3.0 | +| | RP-98 | RP-223409 | 3563 | 5 | F | Corrections for further MR-DC enhancements | 17.3.0 | +| | RP-98 | RP-223411 | 3568 | 3 | F | Corrections to intra-band UL CA DC default location | 17.3.0 | +| | RP-98 | RP-223410 | 3569 | 3 | F | Corrections for Release-17 feMIMO | 17.3.0 | +| | RP-98 | RP-223411 | 3570 | 2 | F | Corrections for Release-17 NR NTN | 17.3.0 | +| | RP-98 | RP-223414 | 3577 | 2 | B | Parallel PRACH and SRS/PUCCH/PUSCH transmissions across CCs in intra-band non-contiguous CA [NC-PRACH-SimulTx] | 17.3.0 | +| | RP-98 | RP-223410 | 3606 | 3 | F | Correction to RRC for 71 GHz | 17.3.0 | +| | RP-98 | RP-223413 | 3608 | 2 | F | RRC corrections for SDT | 17.3.0 | +| | RP-98 | RP-223410 | 3614 | 1 | F | Correction to PDC in RRC | 17.3.0 | +| | RP-98 | RP-223406 | 3619 | 1 | A | Miscellaneous CR on 38.331 | 17.3.0 | +| | RP-98 | RP-223415 | 3621 | 2 | B | Release-17 UE capabilities based on R1 and R4 feature lists (TS38.331) | 17.3.0 | +| | RP-98 | RP-223410 | 3633 | 2 | F | Clarification on the TCI assumption for RSSI measurement for FR2-2 | 17.3.0 | +| | RP-98 | RP-223404 | 3641 | 1 | A | 38.331 CR on the periodicity of the MIB | 17.3.0 | +| | RP-98 | RP-223412 | 3656 | 2 | F | Miscellaneous corrections on TS 38.331 for SL enhancements | 17.3.0 | +| | RP-98 | RP-223404 | 3678 | 2 | F | Miscellaneous non-controversial corrections Set XVI | 17.3.0 | +| | RP-98 | RP-223413 | 3698 | 2 | F | Corrections related to FeatureCombinationPreambles | 17.3.0 | +| | RP-98 | RP-223411 | 3703 | 2 | F | Correction CR for QoE measurements in NR | 17.3.0 | +| | RP-98 | RP-223486 | 3704 | 2 | C | Higher granularity for per-FR gap capability[MaxCCPerFRGap] | 17.3.0 | +| | RP-98 | RP-223413 | 3709 | 1 | F | CR on 38.331 for BFD relaxation when two BFD-RS sets are configured | 17.3.0 | +| | RP-98 | RP-223404 | 3711 | 2 | A | Exclude the suspendConfig in the UE Inactive AS context | 17.3.0 | +| | RP-98 | RP-223409 | 3723 | - | F | Clarifications on DMRS bundling for NR Coverage Enhancements | 17.3.0 | +| | RP-98 | RP-223411 | 3729 | 1 | F | Corrections on VIRP configuration and gapPriority description | 17.3.0 | +| | RP-98 | RP-223411 | 3732 | 1 | F | Miscellaneous corrections for RedCap WI | 17.3.0 | +| | RP-98 | RP-223412 | 3736 | 2 | F | Clarification on the determination of NSAG with the NSAG priority | 17.3.0 | +| | RP-98 | RP-223413 | 3741 | 1 | F | RLM and BFD relaxation reporting configurations are missed in the field description of otherConfig while being configured for SCG | 17.3.0 | +| | RP-98 | RP-223406 | 3751 | 2 | F | Correction on PUSCH configuration | 17.3.0 | +| | RP-98 | RP-223407 | 3753 | - | A | Correction on frequency hopping | 17.3.0 | +| | RP-98 | RP-223407 | 3757 | - | A | Clarification on the NR HST configuration | 17.3.0 | +| | RP-98 | RP-223408 | 3760 | 2 | A | Clarification on inter-frequency no gap measurements in NR-DC | 17.3.0 | +| | RP-98 | RP-223409 | 3761 | 1 | F | Correction to support repetition on PDSCH time domain resource allocation for DCI format 1-2 | 17.3.0 | +| | RP-98 | RP-223413 | 3764 | - | F | RRC correction on update of last used cell | 17.3.0 | +| | RP-98 | RP-223409 | 3768 | - | F | Correction on re-establishment procedure while T346g is running | 17.3.0 | +| | RP-98 | RP-223408 | 3770 | 1 | F | RRC Correction for SON MDT | 17.3.0 | +| | RP-98 | RP-223411 | 3771 | - | F | Correction for RACH partitioning with both 2-step and 4-step RA configurations | 17.3.0 | +| 03/2023 | RP-99 | RP-230690 | 3777 | 1 | F | RRC correction on epochTime | 17.4.0 | +| | RP-99 | RP-230691 | 3780 | 1 | F | Corrections to control plane procedures for RedCap UEs | 17.4.0 | +| | RP-99 | RP-230694 | 3786 | - | F | Corrections to on-demand SI request | 17.4.0 | +| | RP-99 | RP-230690 | 3795 | 1 | F | IOT bit for inter satellite measurement (38.331) | 17.4.0 | +| | RP-99 | RP-230691 | 3800 | 1 | F | Correction on RACH configuration for RedCap | 17.4.0 | +| | RP-99 | RP-230686 | 3805 | 1 | A | Correction on T350 stop | 17.4.0 | + +| | | | | | | | | +|--|-------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------|--------| +| | RP-99 | RP-230692 | 3811 | 2 | F | Clarification on ensuring valid version of SIB17 | 17.4.0 | +| | RP-99 | RP-230686 | 3816 | 1 | A | Correction to usage of pusch-TimeDomainAllocation | 17.4.0 | +| | RP-99 | RP-230693 | 3817 | 4 | F | Corrections for SDT operation for REDCAP without CD-SSB | 17.4.0 | +| | RP-99 | RP-230689 | 3818 | 1 | F | CP corrections for NR operation to 71GHz | 17.4.0 | +| | RP-99 | RP-230688 | 3819 | 1 | F | SDT CP corrections | 17.4.0 | +| | RP-99 | RP-230691 | 3820 | - | F | Correction to RAN visible periodicity definition | 17.4.0 | +| | RP-99 | RP-230690 | 3823 | 1 | F | Clarification on measurement relaxation in NTN | 17.4.0 | +| | RP-99 | RP-230689 | 3827 | - | F | Channel Access Control for msg1/msgA in FR2-2 | 17.4.0 | +| | RP-99 | RP-230685 | 3830 | - | A | Corrections for PUCCH SCell | 17.4.0 | +| | RP-99 | RP-230685 | 3842 | 2 | A | Clarification on RLC bearer re-association | 17.4.0 | +| | RP-99 | RP-230688 | 3851 | 1 | F | Miscellaneous correction of NR RRC support for MUSIM | 17.4.0 | +| | RP-99 | RP-230686 | 3853 | 1 | A | Correction on SRS for positioning | 17.4.0 | +| | RP-99 | RP-230692 | 3854 | 1 | F | Correction in Remote UE synchronization | 17.4.0 | +| | RP-99 | RP-230691 | 3855 | - | F | Clarification on QoE configuration for Layer-2 based UE-to-Network Relay | 17.4.0 | +| | RP-99 | RP-230690 | 3861 | - | F | Clarification on essential SIB19 for NR NTN | 17.4.0 | +| | RP-99 | RP-230692 | 3865 | 1 | F | Corrections on SL Relay | 17.4.0 | +| | RP-99 | RP-230690 | 3868 | - | F | Clarification on MBS neighbour cell list | 17.4.0 | +| | RP-99 | RP-230691 | 3869 | 1 | F | Corrections for eDRX on IDLE eDRX cycle | 17.4.0 | +| | RP-99 | RP-230691 | 3870 | - | F | Correction for hyperSFN on SI update | 17.4.0 | +| | RP-99 | RP-230692 | 3874 | - | F | Clarification on dl-P0-PSBCH, dl-P0-PSSCH-PSCCH and dl-P0-PSFCH for OoC Remote UE | 17.4.0 | +| | RP-99 | RP-230691 | 3880 | 2 | F | Correction on RRC configuration for RedCap | 17.4.0 | +| | RP-99 | RP-230686 | 3883 | 1 | A | Conditional inclusion of SBAS ID in posSIBs | 17.4.0 | +| | RP-99 | RP-230689 | 3887 | - | F | Correction on the field descriptions of nrofDownlinkSlots/nrofUplinkSlots | 17.4.0 | +| | RP-99 | RP-230687 | 3890 | 2 | A | Correction on UL RRC segmentation processing delay requirements | 17.4.0 | +| | RP-99 | RP-230688 | 3891 | 2 | F | RRC Configuration for Positioning Measurement Gap Activation/Deactivation Request MAC CE | 17.4.0 | +| | RP-99 | RP-230694 | 3898 | 2 | F | Miscellaneous non-controversial corrections Set XVII | 17.4.0 | +| | RP-99 | RP-230691 | 3909 | - | F | Correction to conditional presence of parameters for SRB4 | 17.4.0 | +| | RP-99 | RP-230689 | 3913 | 2 | F | Corrections on feMIMO | 17.4.0 | +| | RP-99 | RP-230691 | 3917 | 1 | F | Correction on the filed descriptions of NeedForGaps in 38.331 | 17.4.0 | +| | RP-99 | RP-230685 | 3919 | - | A | Band differentiation for capability pusch-RepetitionTypeA-r16 | 17.4.0 | +| | RP-99 | RP-230690 | 3920 | - | F | CR to TS 38.331 on MBS neighbour cell list | 17.4.0 | +| | RP-99 | RP-230687 | 3926 | 1 | F | Correction to security protection requirement for UL DedicadedMessageSegment | 17.4.0 | +| | RP-99 | RP-230689 | 3930 | - | F | Correction on BWP for CSI-RS in TCI-State | 17.4.0 | +| | RP-99 | RP-230692 | 3931 | - | F | Corrections on 38.331 | 17.4.0 | +| | RP-99 | RP-230692 | 3932 | - | F | Miscellaneous correction to SL Relay | 17.4.0 | +| | RP-99 | RP-230690 | 3933 | 1 | F | Miscellaneous RRC corrections for MBS | 17.4.0 | +| | RP-99 | RP-230687 | 3935 | 1 | A | Clarification that IAB-MT follows the UE behaviour for cell barring procedure as defined in TS 38.304 | 17.4.0 | +| | RP-99 | RP-230694 | 3936 | - | F | Introducing deriveSSB-IndexFromCellInter capability for non-NCSG UEs | 17.4.0 | +| | RP-99 | RP-230690 | 3937 | - | F | Correction to PDD reporting | 17.4.0 | +| | RP-99 | RP-230689 | 3938 | - | F | Clarification on BFD-RS configuration | 17.4.0 | +| | RP-99 | RP-230690 | 3940 | - | F | Corrections on satellite ephemeris indication | 17.4.0 | +| | RP-99 | RP-230689 | 3941 | - | F | Corrections on the unified TCI-state configuration for cross cell referencing | 17.4.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|------------------------------------------------------------------------------|--------| +| | RP-99 | RP-230690 | 3942 | - | B | Release-17 MBS UE capabilities based on latest R1 feature list (TS 38.331) | 17.4.0 | +| | RP-99 | RP-230689 | 3943 | - | F | Rel.17 SON/MDT RRC Corrections | 17.4.0 | +| 06/2023 | RP-100 | RP-231411 | 3894 | 4 | A | SIB and PosSIB mappings to SI message | 17.5.0 | +| | RP-100 | RP-231414 | 3946 | 3 | F | Corrections on MBS Broadcast Configuration | 17.5.0 | +| | RP-100 | RP-231414 | 3948 | 4 | F | Correction to PDSCH Aggregation of MBS SPS | 17.5.0 | +| | RP-100 | RP-231412 | 3956 | 2 | F | Corrections on the figure of UE Positioning Assistance Information procedure | 17.5.0 | +| | RP-100 | RP-231413 | 3961 | 2 | F | Miscellaneous corrections for Ext71GHz | 17.5.0 | +| | RP-100 | RP-231413 | 3964 | 2 | F | Clarification for configured grant periodicity | 17.5.0 | +| | RP-100 | RP-231414 | 3967 | 3 | F | Corrections to paging for MBS | 17.5.0 | +| | RP-100 | RP-231413 | 3968 | 2 | F | Correction to RRC for 71 GHz on channel occupancy duration | 17.5.0 | +| | RP-100 | RP-231414 | 3970 | 2 | F | Correction on Need code of IE RLC-Config | 17.5.0 | +| | RP-100 | RP-231415 | 3975 | 1 | F | Correction on SI update for posSIB-r17 | 17.5.0 | +| | RP-100 | RP-231413 | 3977 | 2 | F | Clarification to TS 38.331 on Enhanced BFR MAC CE for feMIMO | 17.5.0 | +| | RP-100 | RP-231418 | 3979 | 3 | F | Clarification on TN EUTRA capability reporting | 17.5.0 | +| | RP-100 | RP-231410 | 3984 | 2 | A | Clarification on RSSI measurement frequency | 17.5.0 | +| | RP-100 | RP-231415 | 3988 | 2 | F | Corrections on initial BWP configuration and NCD-SSB for RedCap | 17.5.0 | +| | RP-100 | RP-231409 | 4001 | 3 | A | Corrections on refServCellIndicator | 17.5.0 | +| | RP-100 | RP-231418 | 4011 | 1 | F | Correction on Event D1 for Rel-17 NTN | 17.5.0 | +| | RP-100 | RP-231410 | 4013 | 2 | A | Correction on the need code for secondary DRX group | 17.5.0 | +| | RP-100 | RP-231414 | 4015 | 3 | F | Correction to mtch-neighbourCell field description | 17.5.0 | +| | RP-100 | RP-231415 | 4017 | 2 | F | ResumeCause IE description correction | 17.5.0 | +| | RP-100 | RP-231413 | 4020 | 3 | F | Correction to timeSCGFailure | 17.5.0 | +| | RP-100 | RP-231418 | 4021 | 3 | F | Correction on missing referencing of the NTN spec in 38.331 | 17.5.0 | +| | RP-100 | RP-231418 | 4025 | 3 | F | Correction on SMTC for NR NTN | 17.5.0 | +| | RP-100 | RP-231414 | 4037 | 2 | F | Corrections on MBS SPS configuration | 17.5.0 | +| | RP-100 | RP-231418 | 4039 | 1 | F | Clarification on T430 handling for target cell | 17.5.0 | +| | RP-100 | RP-231418 | 4040 | 2 | F | Correction on MIB configuration for NR NTN | 17.5.0 | +| | RP-100 | RP-231414 | 4044 | 3 | F | Miscellaneous RRC corrections for MBS | 17.5.0 | +| | RP-100 | RP-231417 | 4050 | 2 | F | Corrections to on-demand SI request | 17.5.0 | +| | RP-100 | RP-231409 | 4053 | 2 | A | Clarification on nas-SecurityParamFromNR field description | 17.5.0 | +| | RP-100 | RP-231410 | 4060 | 3 | A | Correction on pusCh-RepetitionTypeB capability | 17.5.0 | +| | RP-100 | RP-231416 | 4064 | 1 | F | Miscellaneous corrections for SL relay | 17.5.0 | +| | RP-100 | RP-231414 | 4065 | 4 | F | Correction on Supporting MBS in SNPn | 17.5.0 | +| | RP-100 | RP-231410 | 4068 | 1 | A | Corrections including field description for transmission power | 17.5.0 | +| | RP-100 | RP-231416 | 4069 | 1 | F | Miscellaneous corrections on 38.331 for SL enhancements | 17.5.0 | +| | RP-100 | RP-231415 | 4070 | 1 | F | Clarification on applicability of slice-based RA | 17.5.0 | +| | RP-100 | RP-231417 | 4071 | 1 | F | Correction on measCyclePSCell used during SCG deactivation | 17.5.0 | +| | RP-100 | RP-231413 | 4100 | 1 | F | Corrections on R17 unified TCI framework | 17.5.0 | +| | RP-100 | RP-231412 | 4101 | 1 | F | Correction on scg-CellGroupConfig within RRC inter-node message | 17.5.0 | +| | RP-100 | RP-231412 | 4102 | - | F | Correction on PosSRS-RRC-Inactive-OutsidelnitialUL-BWP | 17.5.0 | +| | RP-100 | RP-231415 | 4107 | 1 | F | Corrections on paging monitoring in eDRX | 17.5.0 | +| | RP-100 | RP-231413 | 4110 | - | F | Correction on timeSinceCHO-Reconfig in TS 38.331 | 17.5.0 | +| | RP-100 | RP-231418 | 4112 | 1 | F | Different UE capability support between TN and NTN | 17.5.0 | +| | RP-100 | RP-231416 | 4113 | 2 | F | Sidelink discovery transmission upon reception of SIB12 | 17.5.0 | +| | RP-100 | RP-231415 | 4114 | - | F | Control plane corrections for SDT | 17.5.0 | +| | RP-100 | RP-231417 | 4117 | 2 | F | Miscellaneous non-controversial corrections Set XVIII | 17.5.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|---------------------------------------------------------------------------------------------------------|--------| +| | RP-100 | RP-231418 | 4127 | - | F | CR to 38.331 on Event D1 | 17.5.0 | +| | RP-100 | RP-231417 | 4132 | 2 | A | Clarification on UAI for UL MIMO layers | 17.5.0 | +| | RP-100 | RP-231416 | 4136 | 1 | F | Corrections on deriving timer length of DRX timers for SL | 17.5.0 | +| | RP-100 | RP-231416 | 4140 | 1 | F | RRC corrections for SL Relay | 17.5.0 | +| | RP-100 | RP-231410 | 4142 | 1 | A | Correction to time domain resource assignment in NR-U | 17.5.0 | +| | RP-100 | RP-231413 | 4144 | 1 | F | Correction to RRC for 71GHz on scheduling and HARQ configuration for FR2-2 | 17.5.0 | +| | RP-100 | RP-231414 | 4147 | 1 | F | Correction on gapAssociationPRS | 17.5.0 | +| | RP-100 | RP-231413 | 4148 | - | F | Correction on SCG failure scenario of MHI in TS 38.331 | 17.5.0 | +| | RP-100 | RP-231415 | 4154 | - | F | Clarification on SDT configuration | 17.5.0 | +| | RP-100 | RP-231411 | 4160 | 1 | A | Clarification on reference cell for TCI state | 17.5.0 | +| | RP-100 | RP-231414 | 4161 | 1 | F | Correction for PLMN index in MCCH of SCell | 17.5.0 | +| | RP-100 | RP-231418 | 4163 | - | F | Correction on the description of kmac | 17.5.0 | +| | RP-100 | RP-231415 | 4166 | 1 | F | Correction on the applicable NSAG for slice based RA procedure | 17.5.0 | +| | RP-100 | RP-231413 | 4167 | - | F | Correction to the handling of RLF-Report after successful HO | 17.5.0 | +| | RP-100 | RP-231417 | 4169 | 1 | F | Support of releasing crossCarrierSchedulingConfig | 17.5.0 | +| | RP-100 | RP-231416 | 4170 | 1 | F | Clarification on remote UE reception of SIB1 | 17.5.0 | +| | RP-100 | RP-231416 | 4171 | 1 | F | Handling of PC5 connection release during RRC re-establishment | 17.5.0 | +| | RP-100 | RP-231411 | 4172 | 1 | A | Correction on the release of logged measurement configuration as well as logged measurement information | 17.5.0 | +| | RP-100 | RP-231411 | 4174 | - | A | Correction to the setting of locationInfo in MeasResultSCG-Failure | 17.5.0 | +| 09/2023 | RP-101 | RP-232570 | 3900 | 6 | F | Addition of extended number range for NS value | 17.6.0 | +| | RP-101 | RP-232565 | 3991 | 6 | F | CSI-RS resource coordination in NR-DC | 17.6.0 | +| | RP-101 | RP-232565 | 4158 | 3 | A | Introduction of intra-band EN-DC contiguous capability for UL | 17.6.0 | +| | RP-101 | RP-232566 | 4176 | - | A | Correction on PUCCH resource field description and SSB transmission initiation | 17.6.0 | +| | RP-101 | RP-232667 | 4189 | 2 | F | Correction on Configuration of Enhanced Type 3 HARQ-ACK Codebook for PUCCH group | 17.6.0 | +| | RP-101 | RP-232667 | 4190 | 2 | F | Correction on PUCCH repetition for PUCCH Format 2 | 17.6.0 | +| | RP-101 | RP-232667 | 4192 | 2 | F | Miscellaneous RRC corrections for MBS | 17.6.0 | +| | RP-101 | RP-232568 | 4202 | - | F | Corrections on the unified TCI-state configuration for 38.331 | 17.6.0 | +| | RP-101 | RP-232568 | 4206 | 1 | F | RRC restriction on multi-TRP schemes | 17.6.0 | +| | RP-101 | RP-232570 | 4220 | 1 | F | Correction to RRC for 71 GHz on multi-PDSCH | 17.6.0 | +| | RP-101 | RP-232667 | 4234 | 1 | F | Correction on GNSS-ID for NavIC A-GNSS | 17.6.0 | +| | RP-101 | RP-232565 | 4238 | 1 | F | Miscellaneous non-controversial corrections Set XIX | 17.6.0 | +| | RP-101 | RP-232567 | 4246 | - | A | Clarification to the setting of locationInfo in MeasResultSCG-Failure | 17.6.0 | +| | RP-101 | RP-232567 | 4248 | 2 | A | Clarification on the PLMN check for the reconnectCellID in the RLF report | 17.6.0 | +| | RP-101 | RP-232568 | 4255 | - | F | Filter of SRS carrier switching capabilities | 17.6.0 | +| | RP-101 | RP-232566 | 4260 | 1 | A | Correction on primaryPath for fast MCG link recovery | 17.6.0 | +| | RP-101 | RP-232566 | 4264 | 1 | A | Correction on CHO for R17 | 17.6.0 | +| | RP-101 | RP-232570 | 4265 | - | F | Miscellaneous corrections for power saving features | 17.6.0 | +| | RP-101 | RP-232570 | 4279 | - | F | Correction on 2-step RACH configuration for feature combination | 17.6.0 | +| | RP-101 | RP-232568 | 4294 | - | F | Correction for group based beam reporting configuration | 17.6.0 | +| | RP-101 | RP-232567 | 4295 | 1 | A | Redirection with MPS correction for resume cause | 17.6.0 | +| | RP-101 | RP-232566 | 4298 | - | A | Miscellaneous NR V2X RRC corrections | 17.6.0 | +| | RP-101 | RP-232667 | 4299 | - | F | Miscellaneous corrections for SL enhancements | 17.6.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|---------------------------------------------------------------------------------------|--------| +| | RP-101 | RP-232667 | 4300 | 1 | F | RRC corrections for SL relay | 17.6.0 | +| | RP-101 | RP-232567 | 4302 | - | A | Correction on location configuration for WLAN, BT and sensor for SON and MDT features | 17.6.0 | +| | RP-101 | RP-232568 | 4303 | - | F | Agreed corrections for Rel-17 SONMDT (Ericsson) | 17.6.0 | +| | RP-101 | RP-232698 | 4305 | 1 | F | Correction to SCell PRACH power scaling for UL CA | 17.6.0 | +| 12/2023 | RP-102 | RP-233888 | 2867 | 6 | B | Introduction of FR2 FBG2 CA BW classes | 17.7.0 | +| | RP-102 | RP-233887 | 4016 | 5 | F | Correction to RRC for 71 GHz on multi-PUSCH | 17.7.0 | +| | RP-102 | RP-233887 | 4088 | 3 | F | Further correction to RRC for 71 GHz on multi-PUSCH | 17.7.0 | +| | RP-102 | RP-233889 | 4318 | 2 | F | Correction on Type1 HARQ-ACK codebook generation | 17.7.0 | +| | RP-102 | RP-233887 | 4327 | 3 | F | Corrections on extension of AreaConfiguration | 17.7.0 | +| | RP-102 | RP-233885 | 4329 | 1 | A | Correction of SL synchronisation measurement | 17.7.0 | +| | RP-102 | RP-233888 | 4336 | 2 | F | Correction on LocationMeasurementIndication procedure for positioning | 17.7.0 | +| | RP-102 | RP-233888 | 4340 | 2 | F | Correction on RedCap initial UL/DL BWP | 17.7.0 | +| | RP-102 | RP-233890 | 4341 | 1 | F | Clarification on the meaning of nogap-noncsg | 17.7.0 | +| | RP-102 | RP-233887 | 4348 | 1 | F | Logging previousPSCellId in case of SCG addition failure | 17.7.0 | +| | RP-102 | RP-233887 | 4349 | 1 | F | Successful handover report is missing under ObtainCommonLocationInfo | 17.7.0 | +| | RP-102 | RP-233890 | 4351 | 2 | F | Notes in the RRC release procedure for NR-NTN | 17.7.0 | +| | RP-102 | RP-233884 | 4363 | 2 | F | Miscellaneous non-controversial corrections Set XX | 17.7.0 | +| | RP-102 | RP-233890 | 4382 | 1 | F | Clarification of configuration of transmissionComb in IE SRS-Resource | 17.7.0 | +| | RP-102 | RP-233888 | 4389 | 1 | F | RRC corrections for SL relay | 17.7.0 | +| | RP-102 | RP-233888 | 4390 | 1 | F | Misc RRC corrections for SL enhancements | 17.7.0 | +| | RP-102 | RP-233889 | 4392 | - | F | Corrections for SSB to CG PUSCH mapping | 17.7.0 | +| | RP-102 | RP-233888 | 4395 | - | F | Correction to support autonomous change of UE channel bandwidth during RACH | 17.7.0 | +| | RP-102 | RP-233887 | 4404 | - | F | Correction to SCell activation/deactivation | 17.7.0 | +| | RP-102 | RP-233885 | 4410 | - | A | Correction on carrier frequency for NR SL RSRP measurement | 17.7.0 | +| | RP-102 | RP-233890 | 4413 | 1 | F | Removal of ambiguous term 'legacy' | 17.7.0 | +| | RP-102 | RP-233886 | 4418 | - | A | Correction to 38.331 on GNSS-ID | 17.7.0 | +| | RP-102 | RP-233888 | 4423 | 1 | F | Correction on SL-DRX reject reporting to gNB | 17.7.0 | +| | RP-102 | RP-233888 | 4424 | 1 | F | Correction on the SL destinations in SUI message | 17.7.0 | +| | RP-102 | RP-233888 | 4429 | 1 | F | Clarification on the search space for RedCap | 17.7.0 | +| | RP-102 | RP-233888 | 4430 | 1 | F | Correction for the selected band for HD-FDD capability checking by RedCap UE | 17.7.0 | +| | RP-102 | RP-233886 | 4450 | - | A | Setting the content of the RA report for the selected beam | 17.7.0 | +| | RP-102 | RP-233888 | 4462 | 1 | F | Missing correction for SBAS ID presence in Rel-17 SI scheduling [SI-SCHEDULING] | 17.7.0 | +| | RP-102 | RP-233890 | 4463 | 1 | F | Corrections on description of epochTime and reference point of UTC time and t-Service | 17.7.0 | +| | RP-102 | RP-233888 | 4466 | 1 | F | Correction on SL relay RRC | 17.7.0 | +| | RP-102 | RP-233885 | 4474 | - | A | Correction on type-1 SL CG | 17.7.0 | +| | RP-102 | RP-233888 | 4478 | 1 | F | Correction on multipleCORESET for RedCap UEs | 17.7.0 | +| | RP-102 | RP-233889 | 4485 | - | F | Correction to SDT-Config handling | 17.7.0 | +| | RP-102 | RP-233888 | 4489 | 2 | F | Correction on transmission of SSR Assistance Data based on BDS B1C | 17.7.0 | +| | RP-102 | RP-233889 | 4494 | - | F | Correction to support higher power limit capability for inter-band UL EN-DC | 17.7.0 | +| | RP-102 | RP-233887 | 4498 | 1 | B | Introduction of new CA BW classes for FR2-2 | 17.7.0 | +| | RP-102 | RP-233888 | 4502 | 3 | F | Correction on NCD-SSB time offset for RedCap UEs in TDD | 17.7.0 | +| | RP-102 | RP-233888 | 4505 | - | F | Correction on field description related to CBR-based transmission | 17.7.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|---------------------------------------------------------------------------------------------------------------------|--------| +| | RP-102 | RP-233884 | 4506 | 1 | F | Simultaneous PUSCH and PUCCH transmissions of same priority on different inter-band cells [SimultaneousPUSCH-PUCCH] | 17.7.0 | +| | RP-102 | RP-233889 | 4508 | - | F | Clarification on cellBarredNTN in RRC_CONNECTED | 17.7.0 | +| 12/2023 | RP-102 | RP-233884 | 3971 | 4 | C | Adding SR periodicities for 30 and 120 kHz subcarrier spacing [SR-Periods-30-120-kHz] | 18.0.0 | +| | RP-102 | RP-233881 | 4014 | 4 | B | Introduction of 1-symbol PRS in 38.331[1symbol_PRS] | 18.0.0 | +| | RP-102 | RP-233915 | 4063 | 6 | B | Introduction of further measurement gap enhancements | 18.0.0 | +| | RP-102 | RP-233881 | 4066 | 6 | C | Downlink positioning support and posSIB request for L2 UE-to-network remote UE [PosL2RemoteUE] | 18.0.0 | +| | RP-102 | RP-233882 | 4109 | 4 | B | GNSS LOS/NLOS posSIB broadcast assistance information [GNSS LOS/NLOS] | 18.0.0 | +| | RP-102 | RP-233890 | 4123 | 1 | B | RedCap CFR for MBS broadcast [RedCapMBS_Bcast] | 18.0.0 | +| | RP-102 | RP-233898 | 4162 | 5 | B | Introduction of Network Controlled Repeaters in RRC spec | 18.0.0 | +| | RP-102 | RP-233905 | 4164 | 5 | B | Introduction of In-Device Co-existence (IDC) enhancements for NR | 18.0.0 | +| | RP-102 | RP-233902 | 4194 | 3 | B | Introduction of MT-SDT | 18.0.0 | +| | RP-102 | RP-233911 | 4258 | 3 | B | Introduction of URLLC and Timing Resiliency | 18.0.0 | +| | RP-102 | RP-233882 | 4296 | 2 | C | SSR Satellite PCV Residuals [Rel18PCV] | 18.0.0 | +| | RP-102 | RP-233893 | 4360 | 3 | B | Introduction of R18 DSS | 18.0.0 | +| | RP-102 | RP-233882 | 4375 | 2 | F | Enhancing SCell A2 event reporting [SCell_A2_Enh] | 18.0.0 | +| | RP-102 | RP-233913 | 4380 | 2 | B | Introduction of UE preference for multi-Rx operation in UAI | 18.0.0 | +| | RP-102 | RP-233897 | 4391 | 3 | B | Introduction of Rel-18 SL Evolution | 18.0.0 | +| | RP-102 | RP-233917 | 4396 | 1 | B | Signaling support for intra-band non-collocated NR-CA, EN-DC | 18.0.0 | +| | RP-102 | RP-233938 | 4398 | 1 | B | Introduction of support for BWP operation without restriction | 18.0.0 | +| | RP-102 | RP-233903 | 4401 | 2 | B | Introduction of NR MUSIM enhancements | 18.0.0 | +| | RP-102 | RP-233912 | 4405 | - | B | Introduction of R18 eNPN for TS 38.331 | 18.0.0 | +| | RP-102 | RP-233896 | 4406 | 2 | B | Introduction of MIMO Evolution | 18.0.0 | +| | RP-102 | RP-233882 | 4414 | 2 | B | MUSIM paging cause forwarding [MUSIMPagingCause] | 18.0.0 | +| | RP-102 | RP-233932 | 4416 | 1 | B | Introduction of NR Support for UAV (Uncrewed Aerial Vehicles) | 18.0.0 | +| | RP-102 | RP-233914 | 4422 | 2 | B | Introduction of FR2 SCell enhancements | 18.0.0 | +| | RP-102 | RP-233895 | 4433 | 4 | B | Introduction of Further NR coverage enhancements in RRC | 18.0.0 | +| | RP-102 | RP-233882 | 4435 | 1 | B | Introduction of RRCRelease with resume indication for SDT [SDT_ReleaseEnh] | 18.0.0 | +| | RP-102 | RP-233908 | 4436 | 2 | B | Introduction of XR enhancements into TS 38.331 | 18.0.0 | +| | RP-102 | RP-233916 | 4437 | 1 | B | Introduction of NR ATG in TS 38.331 | 18.0.0 | +| | RP-102 | RP-233882 | 4439 | 1 | B | Introducing procedure for measurement sequence for intra-RAT and inter-RAT measurement [MeasSequence] | 18.0.0 | +| | RP-102 | RP-233904 | 4441 | 2 | B | Introduction of Rel-18 SL relay enhancements | 18.0.0 | +| | RP-102 | RP-233910 | 4446 | 2 | B | Introduction of Enhancement on NR QoE management and optimizations for diverse services | 18.0.0 | +| | RP-102 | RP-233909 | 4452 | 1 | B | CR to 38331 for introducing SON/MDT features in Rel-18 | 18.0.0 | +| | RP-102 | RP-233900 | 4453 | 1 | B | Introduction of Network energy savings for NR | 18.0.0 | +| | RP-102 | RP-233901 | 4454 | 1 | B | Introduction of NR Positioning Enhancements | 18.0.0 | +| | RP-102 | RP-233933 | 4457 | 1 | B | Introduction of mobile IAB | 18.0.0 | +| | RP-102 | RP-233957 | 4458 | 3 | B | Introduction of further NR mobility enhancements | 18.0.0 | +| | RP-102 | RP-233886 | 4469 | 1 | B | Introduction of enhancements of delay measurements upon MO updates [SONMDT-enh] | 18.0.0 | +| | RP-102 | RP-233882 | 4471 | 2 | B | Enhancements for CG-SDT [CG-SDT-Enh] | 18.0.0 | + +| | | | | | | | | +|--|--------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------|--------| +| | RP-102 | RP-233899 | 4480 | 1 | B | Introduction of eRedCap UEs | 18.0.0 | +| | RP-102 | RP-233937 | 4488 | 1 | B | Introduction of network RRC signalling for advanced receiver | 18.0.0 | +| | RP-102 | RP-233907 | 4490 | 5 | B | Introduction of eMBS to RRC | 18.0.0 | +| | RP-102 | RP-233882 | 4492 | 2 | F | Configuration of cell individual offset in ReportConfig [CIO_in_ReportConfig] | 18.0.0 | +| | RP-102 | RP-233906 | 4501 | 1 | B | Introduction of Rel-18 NR NTN enhancements | 18.0.0 | +| | RP-102 | RP-233890 | 4504 | - | B | PTM retransmission reception for multicast DRX with HARQ feedback disabled [PTM_ReTx_Mcast_HARQ_Disb] | 18.0.0 | +| | RP-102 | RP-233894 | 4509 | - | B | Introduction of Rel-18 Multi-carrier enhancements | 18.0.0 | +| | RP-102 | RP-233940 | 4510 | - | B | Introduction of Rel-18 UE capabilities | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38340/0b87abe67b21a93777287649c33e755d_img.jpg b/marked/Rel-18/38_series/38340/0b87abe67b21a93777287649c33e755d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7cee6901b62d9c7c4ae14c7e58880f0a5ed0ca09 --- /dev/null +++ b/marked/Rel-18/38_series/38340/0b87abe67b21a93777287649c33e755d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e572c2e96240112fb2176d709c0e195eea7e9d84c0d9cbf20e25288f547be14b +size 87096 diff --git a/marked/Rel-18/38_series/38340/2834bdd6eb8540277e609decbb924003_img.jpg b/marked/Rel-18/38_series/38340/2834bdd6eb8540277e609decbb924003_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5773d57f121d40774201a401084325df9e6690e1 --- /dev/null +++ b/marked/Rel-18/38_series/38340/2834bdd6eb8540277e609decbb924003_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a0a9e066ecc0a6e83dc944473ddd607b66034181f6c4ef27306e44b70cb5c25 +size 9225 diff --git a/marked/Rel-18/38_series/38340/3b621c21b0af3a504a28d2547e87138f_img.jpg b/marked/Rel-18/38_series/38340/3b621c21b0af3a504a28d2547e87138f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..10c4ae44f4e6b5855ff08fdce2cba5af4caae29e --- /dev/null +++ b/marked/Rel-18/38_series/38340/3b621c21b0af3a504a28d2547e87138f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:515cbc1b932df86f358d73142ddbd3d55e145a2d3cf920c8d57cbaba2222de90 +size 44384 diff --git a/marked/Rel-18/38_series/38340/492256bb98eb10f95553a7b1983c4b96_img.jpg b/marked/Rel-18/38_series/38340/492256bb98eb10f95553a7b1983c4b96_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e04d7277bdac6517b78ca90542f5886990bb7617 --- /dev/null +++ b/marked/Rel-18/38_series/38340/492256bb98eb10f95553a7b1983c4b96_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9497df7892066c3c7416aa711fa5c86da42880bf465f88231d6f5df473dc297 +size 27288 diff --git a/marked/Rel-18/38_series/38340/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38340/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c937107cbae5e112d50a37d6642c3a5ab9f96b28 --- /dev/null +++ b/marked/Rel-18/38_series/38340/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b2338144b401cb85a5c09976271a00f14781f304ab5d0d5638d10ab6ea37b71 +size 8496 diff --git a/marked/Rel-18/38_series/38340/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38340/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fba9b1546cc1b0940d5e11cb8662425d325fcb6f --- /dev/null +++ b/marked/Rel-18/38_series/38340/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2db06581b2a52b692f3bf00df05f565808b75b80dc5e6c158ad4f2d1d9745cd3 +size 5825 diff --git a/marked/Rel-18/38_series/38340/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-18/38_series/38340/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b02b2c4efabc722ffe34625ac46d22918250343 --- /dev/null +++ b/marked/Rel-18/38_series/38340/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0d5de2e7631393540e8856784e9b0ccee6232dc6ee3315f0b24c1954eff1414 +size 56605 diff --git a/marked/Rel-18/38_series/38340/90ddf538ef276510e2b631f7b96654e6_img.jpg b/marked/Rel-18/38_series/38340/90ddf538ef276510e2b631f7b96654e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0307e7ea1bd49f1829a57b518b8e88106ea26779 --- /dev/null +++ b/marked/Rel-18/38_series/38340/90ddf538ef276510e2b631f7b96654e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1d08b1cd7a06cbb9614ae4077078d38df888b1dc6b613283711a7b6f7bb6976 +size 9562 diff --git a/marked/Rel-18/38_series/38340/965aaf7a8b454893b05799d266de6a69_img.jpg b/marked/Rel-18/38_series/38340/965aaf7a8b454893b05799d266de6a69_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..78e4929338987a766d7497a7305062f729cb3658 --- /dev/null +++ b/marked/Rel-18/38_series/38340/965aaf7a8b454893b05799d266de6a69_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:313ee51c9728718e4207f20681b8b68213277f071f3ae26709f03276678e1a3b +size 10286 diff --git a/marked/Rel-18/38_series/38340/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg b/marked/Rel-18/38_series/38340/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..24d2953f92109d3fd477e8eecf5cb47c8f5cc434 --- /dev/null +++ b/marked/Rel-18/38_series/38340/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95c29332068a345fc062601f7f2795643dfe80232f4e37550cb68ae3381dd51e +size 73834 diff --git a/marked/Rel-18/38_series/38340/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-18/38_series/38340/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..93767e0ee685bfcc8476371ee5d2bfb1413bae0e --- /dev/null +++ b/marked/Rel-18/38_series/38340/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dbbe17e458a64e34c20a45ca0e0336567d1ae443c155e88443fd54ebacc46625 +size 9408 diff --git a/marked/Rel-18/38_series/38340/raw.md b/marked/Rel-18/38_series/38340/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..884e173bd79c74bfb0d8ee96bd2e403120de9128 --- /dev/null +++ b/marked/Rel-18/38_series/38340/raw.md @@ -0,0 +1,933 @@ + + +# 3GPP TS 38.340 V18.0.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Backhaul Adaptation Protocol (BAP) specification (Release 18)** + +![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5G" text 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 Abbreviations ..... | 8 | +| 4 General ..... | 8 | +| 4.1 Introduction ..... | 8 | +| 4.2 Architecture..... | 8 | +| 4.2.1 BAP structure ..... | 8 | +| 4.2.2 BAP entities..... | 8 | +| 4.3 Services ..... | 9 | +| 4.3.1 Services provided to upper layers..... | 9 | +| 4.3.2 Services expected from lower layers..... | 9 | +| 4.4 Functions ..... | 9 | +| 4.5 Configurations ..... | 10 | +| 5 Procedures..... | 11 | +| 5.1 BAP entity handling ..... | 11 | +| 5.1.1 BAP entity establishment ..... | 11 | +| 5.1.2 BAP entity release ..... | 11 | +| 5.2 Data transfer ..... | 11 | +| 5.2.1 Transmitting operation ..... | 11 | +| 5.2.1.1 General..... | 11 | +| 5.2.1.2 BAP routing ID selection..... | 11 | +| 5.2.1.2.1 BAP routing ID selection at IAB-node ..... | 11 | +| 5.2.1.2.2 BAP routing ID selection at IAB-donor-DU..... | 12 | +| 5.2.1.3 Routing..... | 13 | +| 5.2.1.4 Mapping to BH RLC Channel ..... | 14 | +| 5.2.1.4.1 Mapping to BH RLC Channel for BAP Data Packets from collocated BAP entity at IAB-node ..... | 14 | +| 5.2.1.4.2 Mapping to BH RLC Channel for BAP SDUs from upper layers at IAB-node ..... | 15 | +| 5.2.1.4.3 Mapping to BH RLC Channel at IAB-donor-DU ..... | 16 | +| 5.2.2 Receiving operation..... | 17 | +| 5.3 Flow control ..... | 18 | +| 5.3.1 Flow control feedback ..... | 18 | +| 5.3.1.1 Transmitting operation..... | 18 | +| 5.3.1.2 Receiving operation ..... | 18 | +| 5.3.2 Flow control polling ..... | 18 | +| 5.4 BH RLF related indications..... | 19 | +| 5.4.1 Transmitting operation ..... | 19 | +| 5.4.2 Receiving operation..... | 19 | +| 5.5 Handling of unknown, unforeseen, and erroneous protocol data..... | 19 | +| 6 Protocol data units, formats, and parameters ..... | 20 | +| 6.1 Protocol data units ..... | 20 | +| 6.1.1 Data PDU..... | 20 | +| 6.1.2 Control PDU ..... | 20 | +| 6.2 Formats..... | 20 | +| 6.2.1 General ..... | 20 | +| 6.2.2 Data PDU..... | 20 | +| 6.2.3 Control PDU ..... | 20 | +| 6.2.3.1 Control PDU for flow control feedback ..... | 20 | +| 6.2.3.2 Control PDU for flow control polling..... | 21 | +| 6.2.3.3 Control PDU for BH RLF indication..... | 22 | +| 6.2.3.4 Control PDU for BH RLF detection indication ..... | 22 | + +| | | | +|---------------------------------------------------|-------------------------------------------------|-----------| +| 6.2.3.5 | Control PDU for BH RLF recovery indication..... | 22 | +| 6.3 | Parameters ..... | 22 | +| 6.3.1 | General ..... | 22 | +| 6.3.2 | DESTINATION ..... | 22 | +| 6.3.3 | PATH..... | 22 | +| 6.3.4 | Data..... | 23 | +| 6.3.5 | R ..... | 23 | +| 6.3.6 | D/C ..... | 23 | +| 6.3.7 | PDU type ..... | 23 | +| 6.3.8 | BH RLC channel ID ..... | 23 | +| 6.3.9 | BAP Routing ID ..... | 23 | +| 6.3.10 | Available Buffer Size ..... | 23 | +| Annex A (informative): Change history..... | | 24 | + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, certain modal verbs have the following meanings: + +**shall** indicates a mandatory requirement to do something + +**shall not** indicates an interdiction (prohibition) to do something + +NOTE 1: The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +NOTE 2: The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +**should** indicates a recommendation to do something + +**should not** indicates a recommendation not to do something + +**may** indicates permission to do something + +**need not** indicates permission not to do something + +NOTE 3: The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +**can** indicates that something is possible + +**cannot** indicates that something is impossible + +NOTE 4: The constructions "can" and "cannot" shall not to be used as substitutes for "may" and "need not". + +**will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document + +**will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document + +**might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +NOTE 5: The constructions "is" and "is not" do not indicate requirements. + +# --- 1 Scope + +The present document provides description of the Backhaul Adaptation Protocol (BAP). + +# --- 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.473: "NG-RAN F1 application protocol (F1AP) protocol specification". +- [6] 3GPP TS 38.401: "NG-RAN; Architecture description". + +# --- 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]. + +**BH RLC channel:** an RLC channel between two nodes, which is used to transport backhaul packets, as defined in TS 38.300 [2]. + +**Boundary IAB-node:** an IAB-node with one RRC interface terminating at a different IAB-donor-CU than the F1 interface, as defined in TS 38.401 [6]. This term is not used for a mobile IAB-node. + +**Egress BH RLC channel:** a BH RLC channel on which a packet is transmitted by a node. + +**Egress link:** a radio link on which a packet is transmitted by a node. + +**F1-terminating donor:** refers to the IAB-donor that terminates F1 for the IAB-node, as defined in TS 38.401 [6]. + +**IAB-donor:** as defined in TS 38.300 [2]. + +**IAB-donor-DU:** as defined in TS 38.401 [6]. + +**IAB-node:** as defined in TS 38.300 [2]. + +**Ingress BH RLC channel:** a BH RLC channel on which a packet is received by a node. + +**Ingress link:** a radio link on which a packet is received by a node. + +**Mobile IAB-node:** as defined in TS 38.300 [2]. + +**Non-F1-terminating donor:** refers to the IAB-donor that has an RRC connection with the boundary node but does not terminate F1 with this boundary IAB-node, as defined in TS 38.401 [6]. + +## 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]. + +| | | +|------|------------------------------------| +| BH | Backhaul | +| DSCP | Differentiated Services Code Point | +| IAB | Integrated Access and Backhaul | +| MT | Mobile Termination | +| TEID | Tunnel Endpoint Identifier | + +# 4 General + +## 4.1 Introduction + +The present document describes the functionalities of BAP. + +## 4.2 Architecture + +### 4.2.1 BAP structure + +Figure 4.2.1-1 represents one possible structure for the BAP sublayer; it should not restrict implementation. The figure is based on the radio interface protocol architecture defined in TS 38.300 [2]. + +![Figure 4.2.1-1: BAP layer, structure view. The diagram shows the BAP sublayer structure. At the top, the BAP sublayer is shown as a box containing a 'BAP entity'. Above the box, 'IAB-MT/IAB-DU/IAB-donor-DU' is labeled, with a 'BAP-SAP' (Service Access Point) indicated by a circle on the top boundary. To the left, a 'C-SAP' (Control Service Access Point) is indicated by a circle on the left boundary. Below the BAP sublayer, the RLC sublayer is shown. It contains 'BH RLC channels' and 'RLC UM-SAP' (Unacknowledged Mode Service Access Point) and 'RLC AM-SAP' (Acknowledged Mode Service Access Point) entities, represented by circles. Arrows show data flow: from the BAP entity to the RLC sublayer, and from the RLC sublayer to the BAP entity. Between the RLC sublayer and the BAP entity, there are two stacked boxes labeled 'BAP - PDU' (Protocol Data Unit) and 'RLC - SDU' (Service Data Unit).](3b621c21b0af3a504a28d2547e87138f_img.jpg) + +Figure 4.2.1-1: BAP layer, structure view. The diagram shows the BAP sublayer structure. At the top, the BAP sublayer is shown as a box containing a 'BAP entity'. Above the box, 'IAB-MT/IAB-DU/IAB-donor-DU' is labeled, with a 'BAP-SAP' (Service Access Point) indicated by a circle on the top boundary. To the left, a 'C-SAP' (Control Service Access Point) is indicated by a circle on the left boundary. Below the BAP sublayer, the RLC sublayer is shown. It contains 'BH RLC channels' and 'RLC UM-SAP' (Unacknowledged Mode Service Access Point) and 'RLC AM-SAP' (Acknowledged Mode Service Access Point) entities, represented by circles. Arrows show data flow: from the BAP entity to the RLC sublayer, and from the RLC sublayer to the BAP entity. Between the RLC sublayer and the BAP entity, there are two stacked boxes labeled 'BAP - PDU' (Protocol Data Unit) and 'RLC - SDU' (Service Data Unit). + +Figure 4.2.1-1: BAP layer, structure view + +The BAP sublayer is configured by upper layers TS 38.331 [3] and TS 38.473 [5]. + +### 4.2.2 BAP entities + +On the IAB-node, the BAP sublayer contains one BAP entity at the MT function and a separate collocated BAP entity at the DU function. A mobile IAB-node may have two logical DU functions, as defined in TS 38.401 [6], which are supported by one common BAP entity at the MT function. The RAN node operating as a mobile IAB-node has no BAP entity at the DU function. On the IAB-donor-DU, the BAP sublayer contains only one BAP entity. Each BAP entity has a transmitting part and a receiving part. + +NOTE: The modelling of BAP entities does not restrict internal implementation of IAB-nodes, i.e. the exact modelling of BAP sublayer may vary for different IAB-node implementations. + +The transmitting part of the BAP entity has a corresponding receiving part of a BAP entity at the IAB-node or IAB-donor-DU across the BH link. + +Figure 4.2.2-1 shows one example of the functional view of the BAP sublayer. This functional view should not restrict implementation. The figure is based on the radio interface protocol architecture defined in TS 38.300 [2]. + +In the example of Figure 4.2.2-1, the receiving part on the BAP entity delivers BAP PDUs to the transmitting part on the collocated BAP entity. Alternatively, the receiving part may deliver BAP SDUs to the collocated transmitting part. When passing BAP SDUs, the receiving part removes the BAP header and the transmitting part adds the BAP header with the same BAP header content as carried on the BAP PDU header prior to removal. Passing BAP SDUs in this manner is therefore functionally equivalent to passing BAP PDUs, in implementation. The following specification therefore refers to the passing of BAP Data Packets. + +Besides, BAP entity generates, delivers/receives BAP Control PDU(s) as described in clause 6.1.2. BAP Control PDU can only be exchanged between peer BAP entities across the BH link. + +In addition to the functions shown in Figure 4.2.2-1, the transmitting part of the BAP entity may perform BAP header rewriting operation, in accordance with clause 5.2.1. + +![Figure 4.2.2-1: Example of functional view of BAP sublayer. The diagram illustrates the data flow within the BAP sublayer, split into Transmitting and Receiving parts. On the left, the Transmitting part (for IAB-DU/IAB-Donor-DU or IAB-MT) receives data from upper layers (to determine BAP address and Path ID, add BAP PDU header, route, and map to BH RLC channel) and from the receiving part of the BAP sublayer on the same node. It also handles BAP Control PDUs. Data is sent to the Egress BH RLC channel. On the right, the Receiving part (for IAB-MT or IAB-DU/IAB-Donor-DU) receives data from the Ingress BH RLC channel, determines if it should be delivered to upper layers or back to the transmitting part, removes the BAP PDU header, and handles BAP Control PDUs. Both parts are connected to the Radio Interface (Uu) at the bottom.](0b87abe67b21a93777287649c33e755d_img.jpg) + +Figure 4.2.2-1: Example of functional view of BAP sublayer. The diagram illustrates the data flow within the BAP sublayer, split into Transmitting and Receiving parts. On the left, the Transmitting part (for IAB-DU/IAB-Donor-DU or IAB-MT) receives data from upper layers (to determine BAP address and Path ID, add BAP PDU header, route, and map to BH RLC channel) and from the receiving part of the BAP sublayer on the same node. It also handles BAP Control PDUs. Data is sent to the Egress BH RLC channel. On the right, the Receiving part (for IAB-MT or IAB-DU/IAB-Donor-DU) receives data from the Ingress BH RLC channel, determines if it should be delivered to upper layers or back to the transmitting part, removes the BAP PDU header, and handles BAP Control PDUs. Both parts are connected to the Radio Interface (Uu) at the bottom. + +Figure 4.2.2-1. Example of functional view of BAP sublayer + +## 4.3 Services + +### 4.3.1 Services provided to upper layers + +The following services are provided by the BAP sublayer to upper layers: + +- data transfer. + +### 4.3.2 Services expected from lower layers + +A BAP 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 BAP sublayer supports the following functions: + +- Data transfer; +- Determination of BAP destination and path for packets from upper layers; +- Determination of egress BH RLC channels for packets routed to next hop; +- Routing of packets to next hop; +- BAP header rewriting; +- Differentiating traffic to be delivered to upper layers from traffic to be delivered to egress link; +- Flow control feedback and polling signalling; +- Handling of BH RLF related indications; + +## 4.5 Configurations + +The configuration of the BAP entity includes: + +- The IAB-node's BAP address(es) via RRC. +- The IAB-donor-DU's BAP address via F1AP. +- Mapping from next hop BAP address to downstream egress link via F1AP. +- Mapping from next hop BAP address to upstream egress link via RRC. +- Mapping from upper layer traffic to BAP routing ID in BAP header via F1AP and RRC. +- The BAP routing entries via F1AP. +- Mapping to egress BH RLC channels via F1AP and RRC. +- Flow control feedback type(s) to be provided, if any, via RRC. +- Inter-donor-DU re-routing enabling/disabling via F1AP. + +BH RLC channels are configured via RRC on the IAB-MT, and via F1AP on the IAB-DU/IAB-donor-DU. + +For F1AP configurations, the following mapping, which are derived from the original F1AP signaling, are used in procedure: + +- Uplink Traffic to Routing ID Mapping Configuration. +- Downlink Traffic to Routing ID Mapping Configuration. +- BH Routing Configuration. +- BH RLC Channel Mapping Configuration. +- Uplink Traffic to BH RLC Channel Mapping Configuration. +- Downlink Traffic to BH RLC Channel Mapping Configuration. +- Header Rewriting Configuration. + +NOTE: For a mobile IAB-node with two logical DUs, separate F1AP configurations are provided for each logical DU by the DU's respective IAB-donor-CU via the corresponding F1AP and are used for the logical DU correspondingly. + +# 5 Procedures + +## 5.1 BAP entity handling + +### 5.1.1 BAP entity establishment + +When upper layers request establishment of a BAP entity, the node shall: + +- establish a BAP entity; +- follow the procedures in clause 5. + +### 5.1.2 BAP entity release + +When upper layers request release of a BAP entity, the node shall: + +- release the BAP entity and the related BAP configurations. + +## 5.2 Data transfer + +### 5.2.1 Transmitting operation + +#### 5.2.1.1 General + +The transmitting part of the BAP entity on the IAB-MT can receive BAP SDUs from upper layers and BAP Data Packets from the receiving part of the BAP entity on the IAB-DU of the same IAB-node, and construct BAP Data PDUs as needed (see clause 4.2.2). The transmitting part of the BAP entity on the IAB-DU can receive BAP Data Packets from the receiving part of the BAP entity on the IAB-MT of the same IAB-node, and construct BAP Data PDUs as needed (see clause 4.2.2). The transmitting part of the BAP entity on the IAB-donor-DU can receive BAP SDUs from upper layers, and construct BAP Data PDUs as needed (see clause 4.2.2). + +Upon receiving a BAP SDU from upper layers, the transmitting part of the BAP entity shall: + +- select a BAP address and a BAP path identity for this BAP SDU in accordance with clause 5.2.1.2; +- construct a BAP Data PDU by adding a BAP header to the BAP SDU, where the DESTINATION field is set to the selected BAP address and the PATH field is set to the selected BAP path identity, in accordance with clause 6.2.2; + +When the BAP entity has a BAP Data PDU to transmit, the transmitting part of the BAP entity shall: + +- for the boundary IAB-node, if the BAP Data PDU is received from the collocated BAP entity, perform the BAP header rewriting operation (if configured) in accordance with clause 5.2.1.5; +- perform routing to determine the egress link in accordance with clause 5.2.1.3; +- determine the egress BH RLC channel in accordance with clause 5.2.1.4; +- submit this BAP Data PDU to the selected egress BH RLC channel of the selected egress link. + +NOTE: Data buffering on the transmitting part of the BAP entity, e.g., until RLC-AM entity has received an acknowledgement, is up to implementation. In case of BH RLF, the transmitting part of the BAP entity may reroute the BAP Data PDUs, which has not been acknowledged by lower layer before the BH RLF, to an alternative path in accordance with clause 5.2.1.3. + +#### 5.2.1.2 BAP routing ID selection + +##### 5.2.1.2.1 BAP routing ID selection at IAB-node + +At an IAB-node, for a BAP SDU received from upper layers and to be transmitted in upstream direction, the BAP entity performs mapping to a BAP address and BAP path identity based on: + +- Uplink Traffic to Routing ID Mapping Configuration, which is derived from F1AP on the IAB-node in TS 38.473 [5], +- *defaultUL-BAP-RoutingID*, which is configured by RRC on the IAB-node in TS 38.331[3]. + +Each entry of the Uplink Traffic to Routing ID Mapping Configuration contains: + +- a traffic type specifier, which is indicated by *UL UP TNL Information* IE for F1-U packets and *Non-UP Traffic Type* IE for non-F1-U packets in TS 38.473 [5], +- a BAP routing ID, which includes a BAP address and a BAP path identity, indicated by *BAP Routing ID* IE in *BH Information* IE in TS 38.473 [5], and +- a Topology indicator, indicating whether the BAP routing ID belongs to the non-F1-terminating donor topology, which is optionally indicated by *Non-F1-terminating IAB-donor Topology Indicator* IE. + +At the IAB-node, for a BAP SDU received from upper layers and to be transmitted in upstream direction, the BAP entity shall: + +- if the Uplink Traffic to Routing ID Mapping Configuration has not been (re)configured by the F1AP associated with the (logical) DU, where this BAP SDU is received, after the last (re)configuration of *defaultUL-BAP-RoutingID* by RRC: + - select the BAP address and the BAP path identity as configured by *defaultUL-BAP-RoutingID* in TS 38.331 [3] for non-F1-U packets; +- else: + - for the BAP SDU encapsulating an F1-U packet: + - select an entry from the Uplink Traffic to Routing ID Mapping Configuration with its traffic type specifier corresponds to the destination IP address and TEID of this BAP SDU; + - for the BAP SDU encapsulating a non-F1-U packet: + - select an entry from the Uplink Traffic to Routing ID Mapping Configuration with its traffic type specifier corresponds to the traffic type of this BAP SDU; + - select the BAP address and the BAP path identity from the BAP routing ID in the entry selected above; + - if the selected entry is configured with *Non-F1-terminating IAB-donor Topology Indicator* IE: + - consider this BAP Data PDU as data to be routed to non-F1-terminating donor topology. + +NOTE 1: Uplink Traffic to Routing ID Mapping Configuration may contain multiple entries for F1-C/non-F1 traffic (for mobile IAB-node, this case occurs when considering both configurations received from two F1AP). It is up to IAB node's implementation to decide which entry is selected. + +NOTE 2: In cases where the same IP address is shared by the two logical DUs, it is up to mobile IAB-node's implementation to decide the logical DU where a BAP SDU encapsulating a non-F1 packet is considered to be received from. The non-F1 traffic does not have to be confined/associated with one specific logical DU. + +##### 5.2.1.2.2 BAP routing ID selection at IAB-donor-DU + +For a BAP SDU received from upper layer at the IAB-donor-DU, the BAP entity performs mapping to a BAP address and a BAP Path identity based on: + +- Downlink Traffic to Routing ID Mapping Configuration, which is derived from *IP-to-layer-2 traffic mapping Information List* IE configured on the IAB-donor-DU in TS 38.473 [5]. + +Each entry of the Downlink Traffic to Routing ID Mapping Configuration contains: + +- a destination IP address, which is indicated by *Destination IAB TNL Address* IE in *IP header information* IE, including an IPv4 address or IPv6 address or an IPv6 address prefix, +- an IPv6 flow label, if configured, which is indicated by *IPv6 Flow Label* IE in *IP header information* IE, + +- a DSCP, if configured, which is indicated by *DSCP IE* in *DS Information List IE* in *IP header information IE*, and +- a BAP routing ID, which is indicated by *BAP Routing ID IE* in *BH Information IE* in TS 38.473 [5]. + +At the IAB-donor-DU, for a BAP SDU received from upper layers and to be transmitted in downstream direction, the BAP entity shall: + +- for the BAP SDU encapsulating an IPv6 packet: + - select an entry from the Downlink Traffic to Routing ID Mapping Configuration which fulfils the following conditions: + - the Destination IP address of this BAP SDU matches the destination IP address in this entry; and + - the IPv6 Flow Label of this BAP SDU matches IPv6 flow label in this entry if configured; and + - the DSCP of this BAP SDU matches DSCP in this entry if configured; +- for the BAP SDU encapsulating an IPv4 packet: + - select an entry from the Downlink Traffic to Routing ID Mapping Configuration which fulfils the following conditions: + - the Destination IP address of this BAP SDU matches the destination IP address in this entry; and + - the DSCP of this BAP SDU matches DSCP in this entry if configured; +- select the BAP address and the BAP path identity from the BAP routing ID in the entry selected above; + +#### 5.2.1.3 Routing + +The BAP entity performs routing based on: + +- the BH Routing Configuration derived from an F1AP message as specified in TS 38.473 [5]. + +Each entry of the BH Routing Configuration contains: + +- a BAP Routing ID consisting of a BAP address and a BAP path identity, which is indicated by *BAP Routing ID IE*, +- a Next Hop BAP Address which is indicated by *Next-Hop BAP Address IE*, and +- a Topology indicator, indicating whether the entry belongs to the non-F1-terminating donor topology, which is optionally indicated by *Non-F1-terminating IAB-donor Topology Indicator IE*. + +In the BH Routing Configuration, the entry configured with *Non-F1-terminating IAB-donor Topology Indicator IE* applies to the BAP Data PDU considered as data to be routed to non-F1-terminating donor topology, and the entry not configured with *Non-F1-terminating IAB-donor Topology Indicator IE* only applies to the BAP Data PDU not considered as data to be routed to non-F1-terminating donor topology. + +For a BAP Data PDU to be transmitted, BAP entity shall: + +- if the BAP Data PDU corresponds to a BAP SDU received from the upper layer, and +- if the BH Routing Configuration has not been (re)configured by the F1AP associated with the (logical) DU, where this BAP SDU is received, after the last (re)configuration of *defaultUL-BH-RLC-Channel* by RRC: + - select the egress link on which the egress BH RLC channel corresponding to *defaultUL-BH-RLC-Channel* is configured as specified in TS 38.331 [3] for non-F1-U packets; +- else if there is an entry in the BH Routing Configuration whose BAP address matches the DESTINATION field, whose BAP path identity is the same as the PATH field, and whose egress link corresponding to the Next Hop BAP Address is available: + - select the egress link corresponding to the Next Hop BAP Address of the entry; + +NOTE 1: An egress link is not considered to be available if the link is in BH RLF. + +NOTE 2: For each combination of a BAP address and a BAP path identity, there should be at most one entry with the same Topology indicator in the BH Routing Configuration. There could be multiple entries of the same BAP address with the same Topology indicator in the BH Routing Configuration. + +NOTE 3: An egress link may not be considered available for a BH Routing Configuration entry with a given BAP routing ID, if it is determined as congested, e.g. based on the received flow control feedback, as defined in clause 5.3.1. + +NOTE 4: In cases where the same IP address is shared by the two logical DUs, it is up to mobile IAB-node's implementation to decide the logical DU where a BAP SDU encapsulating a non-F1 packet is considered to be received from. The non-F1 traffic does not have to be confined/associated with one specific logical DU. + +- else if there is at least one entry in the BH Routing Configuration whose BAP address matches the DESTINATION field, and whose egress link corresponding to the Next Hop BAP Address is available: + - select an entry from the BH Routing Configuration whose BAP address is the same as the DESTINATION field, and whose egress link corresponding to the Next Hop BAP Address is available; + - select the egress link corresponding to the Next Hop BAP Address of the entry selected above; +- else if, for the transmitting part of IAB-MT, at least one egress link is available, and if *Re-routing Enable Indicator* IE is set to true by FIAP: + - if this egress link belongs to F1-terminating donor topology of the boundary IAB-node or the transmitting part of IAB-MT is not at the boundary IAB-node, and there is an entry in the BH Routing Configuration not configured with *Non-F1-terminating IAB-donor Topology Indicator* IE whose Next Hop BAP Address corresponds to this egress link, or + - if this egress link belongs to non-F1-terminating donor topology, and there is an entry in the BH Routing Configuration configured with *Non-F1-terminating IAB-donor Topology Indicator* IE whose Next Hop BAP Address corresponds to this egress link: + - select the egress link; + - rewrite the BAP header of this BAP Data PDU, where the DESTINATION field is set to the leftmost 10 bits of BAP Routing ID of the entry in the BH Routing Configuration (i.e. BAP address), and the PATH field is set to the rightmost 10 bits of BAP Routing ID of the entry (i.e. BAP path identity). + +#### 5.2.1.4 Mapping to BH RLC Channel + +##### 5.2.1.4.1 Mapping to BH RLC Channel for BAP Data Packets from collocated BAP entity at IAB-node + +For a BAP Data Packet received from the collocated BAP entity, the transmitting part of the BAP entity performs mapping to an egress BH RLC channel based on: + +- BH RLC Channel Mapping Configuration, which is derived from *BAP layer BH RLC channel mapping Information List* IE, and optionally together with the *Configured BAP address* IE and the *BH RLC Channel to be Setup/Modified List* IE, as configured on the IAB-node in TS 38.473 [5], + +Each entry of the BH RLC Channel Mapping Configuration contains: + +- an ingress link ID, which is indicated by *Prior-Hop BAP Address* IE, or by the *Configured BAP address* IE in UE-associated F1AP message for upstream, belonging to topology indicated by *Ingress Non-F1-terminating IAB-donor Topology Indicator* IE in F1AP if configured, +- an egress link ID, which is indicated by *Next-Hop BAP Address* IE, or by the *Configured BAP address* IE in UE-associated F1AP message for downstream, belonging to topology indicated by *Egress Non-F1-terminating IAB-donor Topology Indicator* IE in F1AP if configured, +- an ingress BH RLC channel ID, which is indicated by *Ingress BH RLC CH ID* IE, or by the *BH RLC CH ID* IE in UE-associated F1AP message for upstream, and, + +- an egress BH RLC channel ID, which is indicated by *Egress BH RLC CH ID* IE, or by the *BH RLC CH ID* IE in UE-associated F1AP message for downstream. + +For a BAP Data PDU received from an ingress BH RLC channel of an ingress link and for which the egress link has been selected as specified in clause 5.2.1.3: + +- if there is an entry in the BH RLC Channel Mapping Configuration, whose ingress BH RLC channel ID matches the BAP Data PDU's ingress BH RLC channel, whose ingress link ID matches the BAP Data PDU's ingress link, and whose egress link ID corresponds to the selected egress link; + - select the egress BH RLC channel corresponding to egress BH RLC channel ID of this entry; +- else: + - select any egress BH RLC channel on the selected egress link; + +##### 5.2.1.4.2 Mapping to BH RLC Channel for BAP SDUs from upper layers at IAB-node + +For a BAP SDU received from upper layers at the IAB-node, the BAP entity performs mapping to an egress BH RLC channel based on: + +- Uplink Traffic to BH RLC Channel Mapping Configuration, which is derived from F1AP message, configured on the IAB-node in TS 38.473 [5], +- *defaultUL-BH-RLC-Channel*, which is configured by RRC on the IAB-node in TS 38.331[3]. + +Each entry of the Uplink Traffic to BH RLC Channel Mapping Configuration contains: + +- a traffic type specifier, which is indicated by *UL UP TNL Information* IE for F1-U packets or *Non-UP Traffic Type* IE for non-F1-U packets in TS 38.473 [5], +- an egress link ID, which is indicated by *Next-Hop BAP address* IE in *BH Information* IE in TS 38.473 [5], belonging to topology indicated by *Egress Non-F1-terminating IAB-donor Topology Indicator* IE in F1AP if configured, and +- an egress BH RLC channel ID, which is indicated by *BH RLC CH ID* IE in *BH Information* IE in TS 38.473 [5]. + +For a BAP SDU received from upper layers at the IAB-node and to be transmitted in upstream direction, whose egress link has been selected as specified in clause 5.2.1.3, the BAP entity shall: + +- if the Uplink Traffic to BH RLC Channel Mapping Configuration has not been (re)configured by the F1AP associated with the (logical) DU, where this BAP SDU is received, after the last (re)configuration of *defaultUL-BH-RLC-Channel* by RRC: + - select the egress BH RLC channel corresponding to *defaultUL-BH-RLC-Channel* configured in TS 38.331 [3] for non-F1-U packets; +- else: + - for the BAP SDU encapsulating an F1-U packet: + - if there is an entry in the Uplink Traffic to BH RLC Channel Mapping Configuration with its traffic type specifier corresponds to the destination IP address and TEID of this BAP SDU and its egress link ID corresponding to the selected egress link; + - select the egress BH RLC channel corresponding to the egress BH RLC channel ID of this entry; + - else: + - select any egress BH RLC channel on the selected egress link; + - for the BAP SDU encapsulating a non-F1-U packet: + - if there is an entry from the Uplink Traffic to BH RLC Channel Mapping Configuration with its traffic type specifier corresponds to the traffic type of this BAP SDU and its egress link ID corresponding to the selected egress link; + +- select the egress BH RLC channel corresponding to the egress BH RLC channel ID of this entry; +- else: + - select any egress BH RLC channel on the selected egress link; + +NOTE 1: Uplink Traffic to BH RLC Channel Mapping Configuration may contain multiple entries for F1-C/non-F1 traffic (for mobile IAB-node, this case occurs when considering both configurations received from two F1AP). It is up to IAB node's implementation to decide which entry is selected, but the selected entry has to match the BAP routing ID selected in 5.2.1.2.1, i.e. BAP routing ID and BH RLC channel must be derived from the same *BH Information IE*. + +NOTE 2: In cases where the same IP address is shared by the two logical DUs, it is up to mobile IAB-node's implementation to decide the logical DU where a BAP SDU encapsulating a non-F1 packet is considered to be received from. The non-F1 traffic does not have to be confined/associated with one specific logical DU. + +##### 5.2.1.4.3 Mapping to BH RLC Channel at IAB-donor-DU + +For a BAP SDU received from upper layers at the IAB-donor-DU, the BAP entity performs mapping to an egress BH RLC channel based on: + +- Downlink Traffic to BH RLC Channel Mapping Configuration, which is derived from *IP-to-layer-2 traffic mapping Information List IE*, and optionally together with the *Configured BAP address IE* and the *BH RLC Channel to be Setup/Modified List IE*, as configured on the IAB-donor-DU in TS 38.473 [5]. + +Each entry of the Downlink Traffic to BH RLC Channel Mapping Configuration contains: + +- a destination IP address, which is indicated by *Destination IAB TNL Address IE* in *IP header information IE* including an IPv4 address or IPv6 address or an IPv6 address prefix, +- an IPv6 flow label, if configured, which is indicated by *IPv6 Flow Label IE* in *IP header information IE*, +- a DSCP, if configured, which is indicated by *DSCP IE* in *DS Information List IE* in *IP header information IE*, +- an egress link ID, which is indicated by *Next-Hop BAP Address IE* in *BH Information IE*, or by the *Configured BAP address IE* in UE-associated F1AP message, and +- an egress BH RLC channel ID, which is indicated by *Egress BH RLC CH ID IE* in *BH Information IE*, or by the *BH RLC CH ID IE* in UE-associated F1AP message. + +At the IAB-donor-DU, for a BAP SDU received from upper layers and to be transmitted in downstream direction, whose egress link has been selected as specified in clause 5.2.1.3, the BAP entity shall: + +- for the BAP SDU encapsulating an IPv6 packet: + - if there is an entry in the Downlink Traffic to BH RLC Channel Mapping Configuration with its egress link ID corresponding to the selected egress link, and the entry fulfils the following conditions: + - the Destination IP address of this BAP SDU matches the destination IP address in this entry; and + - the IPv6 Flow Label of this BAP SDU matches IPv6 flow label in this entry if configured; and + - the DSCP of this BAP SDU matches DSCP in this entry if configured: + - select the egress BH RLC channel corresponding to egress BH RLC channel ID of this entry; + - else: + - select any egress BH RLC channel on the selected egress link; +- for the BAP SDU encapsulating an IPv4 packet: + - if there is an entry in the Downlink Traffic to BH RLC Channel Mapping Configuration with its egress link ID corresponding to the selected egress link, and the entry fulfils the following conditions: + - the Destination IP address of this BAP SDU matches the destination IP address in this entry; and + +- the DSCP of this BAP SDU matches DSCP in this entry if configured: + - select the egress BH RLC channel corresponding to egress BH RLC channel ID of this entry; +- else: + - select any egress BH RLC channel on the selected egress link; + +#### 5.2.1.5 BAP header rewriting operation + +The BAP entity performs BAP header rewriting based on: + +- the Header Rewriting Configuration derived from an F1AP message as specified in TS 38.473 [5]. + +Each entry of the Header Rewriting Configuration contains: + +- an Ingress Routing ID consisting of a BAP address and a BAP path identity of the BAP Data PDU, which is indicated by *Ingress BAP Routing ID IE*, and +- an Egress Routing ID consisting of a BAP address and a BAP path identity of the BAP Data PDU, which is indicated by *Egress BAP Routing ID IE*, and +- a Topology indicator, indicating whether the Egress Routing ID belongs to the non-F1-terminating donor topology, which is optionally indicated by *Non-F1-terminating IAB-donor Topology Indicator IE*. + +For each BAP Data PDU to be considered for BAP header rewriting, the BAP entity shall: + +- for the IAB-MT of boundary IAB-node, if there is an entry in the Header Rewriting Configuration configured with *Non-F1-terminating IAB-donor Topology Indicator IE*, whose BAP address of Ingress Routing ID matches the DESTINATION field, and whose BAP path identity of Ingress Routing ID matches the PATH field: + - rewrite the BAP header of this BAP Data PDU, where the DESTINATION field is set to the leftmost 10 bits of Egress Routing ID of the entry (i.e. BAP address), and the PATH field is set to the rightmost 10 bits of Egress Routing ID of the entry (i.e. BAP path identity); + - consider this BAP Data PDU as data to be routed to non-F1-terminating donor topology; +- for the IAB-DU of boundary IAB-node, if the ingress link of this BAP Data PDU belongs to non-F1-terminating donor topology of the boundary IAB-node; and +- if there is an entry in the Header Rewriting Configuration not configured with *Non-F1-terminating IAB-donor Topology Indicator IE*, whose BAP address of Ingress Routing ID matches the DESTINATION field, and whose BAP path identity of Ingress Routing ID matches the PATH field: + - rewrite the BAP header of this BAP Data PDU, where the DESTINATION field is set to the leftmost 10 bits of Egress Routing ID of the entry (i.e. BAP address), and the PATH field is set to the rightmost 10 bits of Egress Routing ID of the entry (i.e. BAP path identity). + +NOTE: In this specification, a BH link belongs to the topology of the IAB-donor that provides the configuration of that BH link, as specified in TS 38.331 [3]. + +### 5.2.2 Receiving operation + +Upon receiving a BAP Data PDU from lower layer (i.e. ingress BH RLC channel), the receiving part of the BAP entity shall: + +- if DESTINATION field of this BAP Data PDU matches the BAP address, which is configured for this IAB-node by the IAB-donor providing this ingress BH RLC channel configuration: + - remove the BAP header of this BAP Data PDU and deliver the BAP SDU to upper layers; +- else: + - deliver the BAP Data Packet to the transmitting part of the collocated BAP entity. + +## 5.3 Flow control + +### 5.3.1 Flow control feedback + +#### 5.3.1.1 Transmitting operation + +For a link, the BAP entity at the IAB-MT shall: + +- when a flow control feedback is triggered due to the buffer load exceeding a certain level, or +- when a BAP Control PDU for flow control polling is received at the receiving part, the transmitting part of this BAP entity shall: + - construct a BAP Control PDU for flow control feedback per BH RLC channel, if configured by RRC, in accordance with clause 6.2.3; + - construct a BAP Control PDU for flow control feedback per BAP routing ID, if configured by RRC, in accordance with clause 6.2.3; + - if the egress BH RLC channel for the BAP Control PDU is configured as specified in TS 38.473 [5]: + - submit the BAP Control PDU(s) to the configured egress BH RLC channel of the egress link, indicated by *Egress BH RLC CH ID* IE in *BH Information* IE associated with *Non-UP Traffic Type* IE set to *BAP control PDU* in TS 38.473 [5]; + - else: + - submit the BAP Control PDU(s) to any egress BH RLC channel of the egress link. + +NOTE 1: The BH RLC channel(s) and BAP routing ID(s) to be included in the flow control feedback is up to IAB node implementation, once triggered. + +NOTE 2: For a mobile IAB-node, in case multiple egress BH RLC channels on one egress link are configured for BAP control PDU, it is up to mobile IAB-node's implementation to decide which one is selected. + +#### 5.3.1.2 Receiving operation + +For a link, upon receiving a BAP Control PDU for flow control feedback per BAP routing ID from lower layer, the BAP entity at the IAB-DU or IAB-donor-DU may: + +- if the available buffer size as indicated by the received BAP Control PDU for flow control feedback per BAP routing ID is less than the *Buffer Size Threshold* IE, configured by F1AP in TS 38.473 [5]: + - consider the BH link as congested for this BAP routing ID (for routing defined in accordance with clause 5.2.1.3). + +### 5.3.2 Flow control polling + +When a flow control polling is to be transmitted over an egress link, the transmitting part of the BAP entity at the IAB-DU or IAB-donor-DU: + +- construct a BAP Control PDU for flow control polling in accordance with clause 6.2.3; +- if the egress BH RLC channel for the BAP Control PDU is configured as specified in TS 38.473 [5]: + - submit this BAP Control PDU to the configured egress BH RLC channel of the egress link, indicated by *BH RLC CH ID* IE which is associated with *BAP Control PDU Channel* IE that is set to true in TS 38.473[5]; +- else: + - submit this BAP Control PDU to any egress BH RLC channel of the egress link. + +## 5.4 BH RLF related indications + +### 5.4.1 Transmitting operation + +When a BH RLF recovery failure is detected at the IAB-MT, for each egress link associated with the IAB-DU, the transmitting part of the collocated BAP entity at the IAB-DU may: + +- construct a BAP Control PDU for BH RLF indication in accordance with clause 6.2.3.3; + +When BH RLF(s) occur at the IAB-MT on all the link(s) providing F1 interface over BAP, for each egress link associated with the IAB-DU, the transmitting part of the collocated BAP entity at the IAB-DU may: + +- construct a BAP Control PDU for BH RLF detection indication in accordance with clause 6.2.3.4; + +When BH RLF recovery is successful at the IAB-MT, for each egress link associated with the IAB-DU on which a BAP Control PDU for BH RLF detection indication was transmitted, the transmitting part of the collocated BAP entity at the IAB-DU shall: + +- construct a BAP Control PDU for BH RLF recovery indication in accordance with clause 6.2.3.5; + +For any constructed BAP Control PDU above, the BAP entity shall: + +- if the egress BH RLC channel for the BAP control PDU is configured as specified in TS 38.473 [5]: + - submit this BAP Control PDU to the configured egress BH RLC channel of the egress link, indicated by *BH RLC CH ID* IE which is associated with *BAP Control PDU Channel* that is set to true in TS 38.473 [5]; +- else: + - submit this BAP Control PDU to any egress BH RLC channel of the egress link. + +### 5.4.2 Receiving operation + +Upon receiving a BAP Control PDU for BH RLF indication from lower layer (i.e. ingress BH RLC channel), the receiving part of the BAP entity shall: + +- indicate to upper layers that the BH RLF indication has been received for the ingress link where this BAP Control PDU is received. + +Upon receiving a BAP Control PDU for BH RLF detection indication from lower layer (i.e. ingress BH RLC channel), the receiving part of the BAP entity shall: + +- consider the BH link, from which this BAP Control PDU is received, as not available (for routing defined in accordance with clause 5.2.1.3). + +Upon receiving a BAP Control PDU for BH RLF recovery indication from lower layer (i.e. ingress BH RLC channel), the receiving part of the BAP entity shall: + +- consider the BH link, from which this BAP Control PDU is received, to be available again (for routing defined in accordance with clause 5.2.1.3). + +## 5.5 Handling of unknown, unforeseen, and erroneous protocol data + +When a BAP Data PDU contains a BAP address which is not included in the applied entries of BH Routing Configuration during Routing operation in accordance with clause 5.2.1.3 and the BAP Data PDU contains a BAP address which is not the BAP address of this node in accordance with clause 5.2.2 upon receiving; or + +when a BAP Control PDU that contains reserved or invalid values is received the BAP entity shall: + +- discard the received BAP PDU. + +# 6 Protocol data units, formats, and parameters + +## 6.1 Protocol data units + +### 6.1.1 Data PDU + +The BAP Data PDU is used to convey one of the following in addition to the PDU header: + +- upper layer data. + +### 6.1.2 Control PDU + +The BAP Control PDU is used to convey one of the following in addition to the PDU header: + +- flow control feedback per BH RLC channel; +- flow control feedback per BAP routing ID; +- flow control polling; +- BH RLF related indication; + +## 6.2 Formats + +### 6.2.1 General + +A BAP PDU is a bit string that is byte aligned (i.e. multiple of 8 bits) in length. The formats of BAP PDUs are described in clause 6.2.2, 6.2.3 and their parameters are described in clause 6.3. + +### 6.2.2 Data PDU + +Figure 6.2.2-1 shows the format of the BAP Data PDU. + +![Diagram of BAP Data PDU format showing four octets. Octet 1 contains D/C, R, R, R, and DESTINATION. Octet 2 contains DESTINATION (cont.) and PATH. Octet 3 contains PATH (cont.). Octet 4 contains Data. An ellipsis indicates further octets.](492256bb98eb10f95553a7b1983c4b96_img.jpg) + +| | | | | | | +|---------------------|---|---|---|-------------|-------| +| D/C | R | R | R | DESTINATION | Oct 1 | +| DESTINATION (cont.) | | | | PATH | Oct 2 | +| PATH (cont.) | | | | | Oct 3 | +| Data | | | | | Oct 4 | +| ... | | | | | | + +Diagram of BAP Data PDU format showing four octets. Octet 1 contains D/C, R, R, R, and DESTINATION. Octet 2 contains DESTINATION (cont.) and PATH. Octet 3 contains PATH (cont.). Octet 4 contains Data. An ellipsis indicates further octets. + +Figure 6.2.2-1: BAP Data PDU format + +### 6.2.3 Control PDU + +#### 6.2.3.1 Control PDU for flow control feedback + +Figure 6.2.3.1-1 and 6.2.3.1-2 show the formats of the BAP Control PDU for flow control feedback. + +![BAP Control PDU format for flow control feedback per BH RLC channel. The diagram shows a sequence of fields: D/C, PDU Type, R, R, R (Oct 1); BH RLC channel ID (Oct 2); BH RLC channel ID (cont.) (Oct 3); Available Buffer Size (Oct 4); Available Buffer Size (cont.) (Oct 5); Available Buffer Size (cont.) (Oct 6); BH RLC channel ID (Oct 7); BH RLC channel ID (cont.) (Oct 8); Available Buffer Size (Oct 9); Available Buffer Size (cont.) (Oct 10); Available Buffer Size (cont.) (Oct 11); followed by an ellipsis.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +| | | | | | | +|-------------------------------|----------|---|---|---|--------| +| D/C | PDU Type | R | R | R | Oct 1 | +| BH RLC channel ID | | | | | Oct 2 | +| BH RLC channel ID (cont.) | | | | | Oct 3 | +| Available Buffer Size | | | | | Oct 4 | +| Available Buffer Size (cont.) | | | | | Oct 5 | +| Available Buffer Size (cont.) | | | | | Oct 6 | +| BH RLC channel ID | | | | | Oct 7 | +| BH RLC channel ID (cont.) | | | | | Oct 8 | +| Available Buffer Size | | | | | Oct 9 | +| Available Buffer Size (cont.) | | | | | Oct 10 | +| Available Buffer Size (cont.) | | | | | Oct 11 | +| ... | | | | | | + +BAP Control PDU format for flow control feedback per BH RLC channel. The diagram shows a sequence of fields: D/C, PDU Type, R, R, R (Oct 1); BH RLC channel ID (Oct 2); BH RLC channel ID (cont.) (Oct 3); Available Buffer Size (Oct 4); Available Buffer Size (cont.) (Oct 5); Available Buffer Size (cont.) (Oct 6); BH RLC channel ID (Oct 7); BH RLC channel ID (cont.) (Oct 8); Available Buffer Size (Oct 9); Available Buffer Size (cont.) (Oct 10); Available Buffer Size (cont.) (Oct 11); followed by an ellipsis. + +Figure 6.2.3.1-1: BAP Control PDU format for flow control feedback per BH RLC channel + +![BAP Control PDU format for flow control feedback per BAP routing ID. The diagram shows a sequence of fields: D/C, PDU Type, R, R, R (Oct 1); BAP Routing ID (Oct 2); BAP Routing ID (cont.) (Oct 3); BAP Routing ID (cont.), R, R, R, R (Oct 4); Available Buffer Size (Oct 5); Available Buffer Size (cont.) (Oct 6); Available Buffer Size (cont.) (Oct 7); BAP Routing ID (Oct 8); BAP Routing ID (cont.) (Oct 9); BAP Routing ID (cont.), R, R, R, R (Oct 10); Available Buffer Size (Oct 11); Available Buffer Size (cont.) (Oct 12); Available Buffer Size (cont.) (Oct 13); followed by an ellipsis.](a24e89a6fe9bb70c83f8bf5202baba95_img.jpg) + +| | | | | | | +|-------------------------------|----------|---|---|---|--------| +| D/C | PDU Type | R | R | R | Oct 1 | +| BAP Routing ID | | | | | Oct 2 | +| BAP Routing ID (cont.) | | | | | Oct 3 | +| BAP Routing ID (cont.) | R | R | R | R | Oct 4 | +| Available Buffer Size | | | | | Oct 5 | +| Available Buffer Size (cont.) | | | | | Oct 6 | +| Available Buffer Size (cont.) | | | | | Oct 7 | +| BAP Routing ID | | | | | Oct 8 | +| BAP Routing ID (cont.) | | | | | Oct 9 | +| BAP Routing ID (cont.) | R | R | R | R | Oct 10 | +| Available Buffer Size | | | | | Oct 11 | +| Available Buffer Size (cont.) | | | | | Oct 12 | +| Available Buffer Size (cont.) | | | | | Oct 13 | +| ... | | | | | | + +BAP Control PDU format for flow control feedback per BAP routing ID. The diagram shows a sequence of fields: D/C, PDU Type, R, R, R (Oct 1); BAP Routing ID (Oct 2); BAP Routing ID (cont.) (Oct 3); BAP Routing ID (cont.), R, R, R, R (Oct 4); Available Buffer Size (Oct 5); Available Buffer Size (cont.) (Oct 6); Available Buffer Size (cont.) (Oct 7); BAP Routing ID (Oct 8); BAP Routing ID (cont.) (Oct 9); BAP Routing ID (cont.), R, R, R, R (Oct 10); Available Buffer Size (Oct 11); Available Buffer Size (cont.) (Oct 12); Available Buffer Size (cont.) (Oct 13); followed by an ellipsis. + +Figure 6.2.3.1-2: BAP Control PDU format for flow control feedback per BAP routing ID + +#### 6.2.3.2 Control PDU for flow control polling + +Figure 6.2.3.2-1 shows the formats of the BAP Control PDU for flow control polling. + +![Figure 6.2.3.2-1: BAP Control PDU format for flow control feedback polling. The diagram shows a horizontal bar representing the PDU, divided into five segments. From left to right: a small segment labeled 'D/C', a larger segment labeled 'PDU Type', and three small segments each labeled 'R'. Above the bar, there are tick marks indicating the boundaries of these segments. To the right of the bar, the text 'Oct 1' is present.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +Figure 6.2.3.2-1: BAP Control PDU format for flow control feedback polling. The diagram shows a horizontal bar representing the PDU, divided into five segments. From left to right: a small segment labeled 'D/C', a larger segment labeled 'PDU Type', and three small segments each labeled 'R'. Above the bar, there are tick marks indicating the boundaries of these segments. To the right of the bar, the text 'Oct 1' is present. + +**Figure 6.2.3.2-1: BAP Control PDU format for flow control feedback polling** + +#### 6.2.3.3 Control PDU for BH RLF indication + +Figure 6.2.3.3-1 shows the format of the BAP Control PDU for BH RLF indication. + +![Figure 6.2.3.3-1: BAP Control PDU format for BH RLF indication. The diagram shows a horizontal bar representing the PDU, divided into five segments. From left to right: a small segment labeled 'D/C', a larger segment labeled 'PDU Type', and three small segments each labeled 'R'. Above the bar, there are tick marks indicating the boundaries of these segments. To the right of the bar, the text 'Oct 1' is present.](90ddf538ef276510e2b631f7b96654e6_img.jpg) + +Figure 6.2.3.3-1: BAP Control PDU format for BH RLF indication. The diagram shows a horizontal bar representing the PDU, divided into five segments. From left to right: a small segment labeled 'D/C', a larger segment labeled 'PDU Type', and three small segments each labeled 'R'. Above the bar, there are tick marks indicating the boundaries of these segments. To the right of the bar, the text 'Oct 1' is present. + +**Figure 6.2.3.3-1: BAP Control PDU format for BH RLF indication** + +#### 6.2.3.4 Control PDU for BH RLF detection indication + +Figure 6.2.3.4-1 shows the format of the BAP Control PDU for BH RLF detection indication. + +![Figure 6.2.3.4-1: BAP Control PDU format for BH RLF detection indication. The diagram shows a horizontal bar representing the PDU, divided into five segments. From left to right: a small segment labeled 'D/C', a larger segment labeled 'PDU Type', and three small segments each labeled 'R'. Above the bar, there are tick marks indicating the boundaries of these segments. To the right of the bar, the text 'Oct 1' is present.](2834bdd6eb8540277e609decbb924003_img.jpg) + +Figure 6.2.3.4-1: BAP Control PDU format for BH RLF detection indication. The diagram shows a horizontal bar representing the PDU, divided into five segments. From left to right: a small segment labeled 'D/C', a larger segment labeled 'PDU Type', and three small segments each labeled 'R'. Above the bar, there are tick marks indicating the boundaries of these segments. To the right of the bar, the text 'Oct 1' is present. + +**Figure 6.2.3.4-1: BAP Control PDU format for BH RLF detection indication** + +#### 6.2.3.5 Control PDU for BH RLF recovery indication + +Figure 6.2.3.5-1 shows the format of the BAP Control PDU for BH RLF recovery indication. + +![Figure 6.2.3.5-1: BAP Control PDU format for BH RLF recovery indication. The diagram shows a horizontal bar representing the PDU, divided into five segments. From left to right: a small segment labeled 'D/C', a larger segment labeled 'PDU Type', and three small segments each labeled 'R'. Above the bar, there are tick marks indicating the boundaries of these segments. To the right of the bar, the text 'Oct 1' is present.](965aaf7a8b454893b05799d266de6a69_img.jpg) + +Figure 6.2.3.5-1: BAP Control PDU format for BH RLF recovery indication. The diagram shows a horizontal bar representing the PDU, divided into five segments. From left to right: a small segment labeled 'D/C', a larger segment labeled 'PDU Type', and three small segments each labeled 'R'. Above the bar, there are tick marks indicating the boundaries of these segments. To the right of the bar, the text 'Oct 1' is present. + +**Figure 6.2.3.5-1: BAP Control PDU format for BH RLF recovery indication** + +## 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 string is the first and most significant and the right most bit is the last and least significant bit. + +Unless otherwise mentioned, integers are encoded in standard binary encoding for unsigned integers. In all cases the bits appear ordered from MSB to LSB when read in the PDU. + +### 6.3.2 DESTINATION + +Length: 10 bits. + +This field carries the BAP address of the destination IAB-node or IAB-donor-DU. + +### 6.3.3 PATH + +Length: 10 bits. + +This field carries the BAP path identity. + +### 6.3.4 Data + +Length: Variable + +This field carries the BAP SDU (i.e. IP packet). + +### 6.3.5 R + +Length: 1 bit + +Reserved. In this version of the specification reserved bits shall be set to 0. Reserved bits shall be ignored by the receiver. + +### 6.3.6 D/C + +Length: 1 bit + +This field indicates whether the corresponding BAP PDU is a BAP Data PDU or a BAP Control PDU. + +**Table 6.3.6-1: D/C field** + +| Bit | Description | +|-----|-----------------| +| 0 | BAP Control PDU | +| 1 | BAP Data PDU | + +### 6.3.7 PDU type + +Length: 4 bits + +This field indicates the type of control information included in the corresponding BAP Control PDU. + +**Table 6.3.7-1: PDU type** + +| Bit | Description | +|-----------|------------------------------------------| +| 0000 | Flow control feedback per BH RLC channel | +| 0001 | Flow control feedback per BAP routing ID | +| 0010 | Flow control feedback polling | +| 0011 | BH RLF indication | +| 0100 | BH RLF detection indication | +| 0101 | BH RLF recovery indication | +| 0110-1111 | Reserved | + +### 6.3.8 BH RLC channel ID + +Length: 16 bits. + +This field indicates the identity of the BH RLC channel whose flow control information is provided in the flow control feedback. + +### 6.3.9 BAP Routing ID + +Length: 20 bits. + +This field indicates BAP routing identity, for which the flow control information is provided in the flow control feedback. It contains the BAP address in the leftmost 10 bits and the BAP path identity in the rightmost 10 bits. + +### 6.3.10 Available Buffer Size + +Length: 24 bits. + +This field indicates the maximum traffic volume the transmitter should send. The unit is kilobyte. + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|--------------|------------|------|-----|-----|---------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 10/2019 | RAN2#1 07bis | R2-1914006 | | | | skeleton | 0.0.0 | +| 10/2019 | RAN2#1 07bis | R2-1914008 | | | | Captured agreements made before RAN2#107bis | 0.1.0 | +| 02/2020 | RAN2#1 09e | R2-2002113 | | | | Captured agreements made in RAN2#108 | 0.3.0 | +| 03/2020 | RAN2#1 09e | R2-2002345 | | | | Captured agreements made in RAN2#109e | 0.4.0 | +| 03/2020 | RP-87 | RP-200113 | | | | Version submitted for approval in RAN#87-e | 1.0.0 | +| 03/2020 | RP-87 | | | | | Updated to Rel-16 | 16.0.0 | +| 07/2020 | RP-88 | RP-201179 | 0001 | 4 | F | Miscellaneous corrections to 38.340 for IAB | 16.1.0 | +| 09/2020 | RP-89 | RP-201923 | 0006 | 1 | F | Miscellaneous corrections to 38.340 for IAB | 16.2.0 | +| | RP-89 | RP-201923 | 0007 | - | F | Corrections on flow control BAP control PDU | 16.2.0 | +| 12/2020 | RP-90 | RP-202772 | 0009 | 1 | F | Miscellaneous corrections to 38.340 for IAB | 16.3.0 | +| 03/2021 | RP-91 | RP-210691 | 0012 | 1 | F | Correction on the illustration of BAP entity | 16.4.0 | +| | RP-91 | RP-210691 | 0014 | 1 | F | Miscellaneous corrections to 38.340 for IAB | 16.4.0 | +| 06/2021 | RP-92 | RP-211472 | 0015 | 2 | F | Miscellaneous corrections on BAP transmitting operation and default routing | 16.5.0 | +| | RP-92 | RP-211472 | 0018 | 1 | F | Corrections to the handling of unknown, unforeseen, and erroneous protocol data | 16.5.0 | +| 03/2022 | RP-95 | RP-220486 | 0020 | 2 | B | Introduction of eIAB to TS 38.340 | 17.0.0 | +| 06/2022 | RP-96 | RP-221718 | 0024 | 1 | F | Miscellaneous CR for TS 38.340 | 17.1.0 | +| 09/2022 | RP-97 | RP-222523 | 0029 | 1 | F | Miscellaneous corrections in TS 38.340 for eIAB | 17.2.0 | +| 12/2022 | RP-98 | RP-223410 | 0030 | 1 | F | Miscellaneous corrections in TS 38.340 for eIAB | 17.3.0 | +| 03/2023 | RP-99 | RP-230689 | 0031 | 1 | F | Corrections on the inter-CU routing and header rewriting for eIAB | 17.4.0 | +| 06/2023 | RP-100 | RP-231413 | 0032 | - | F | Corrections on RLF indication for BAP | 17.5.0 | +| 12/2023 | RP-102 | RP-233933 | 0033 | 1 | B | Introduction of mobile IAB in TS 38.340 | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38355/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg b/marked/Rel-18/38_series/38355/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81d2258d49694791a53b62b1eb0d1b36203b30d1 --- /dev/null +++ b/marked/Rel-18/38_series/38355/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7276f2e2a62fcdc9945e5e2664aa1d357d734744d06da59c9732a7781ac2b1f9 +size 18409 diff --git a/marked/Rel-18/38_series/38355/18722c46c9e8475524e634dedd08bac2_img.jpg b/marked/Rel-18/38_series/38355/18722c46c9e8475524e634dedd08bac2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60b031493ec59db30bcc84788bea79b045678797 --- /dev/null +++ b/marked/Rel-18/38_series/38355/18722c46c9e8475524e634dedd08bac2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d94cd22aab9add34d7dd076a809869c0b299f221bc588e0baa1778875069e25 +size 25451 diff --git a/marked/Rel-18/38_series/38355/1bf34e86af3591c80bfbc1c318f811c0_img.jpg b/marked/Rel-18/38_series/38355/1bf34e86af3591c80bfbc1c318f811c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99cfd0a0cc5eff8d54d8af03e1823eb6c89a071d --- /dev/null +++ b/marked/Rel-18/38_series/38355/1bf34e86af3591c80bfbc1c318f811c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b4206033cda2f2bd7c093c7a18a7aeb02eec82b5c0535234d397c2740155b7fc +size 21378 diff --git a/marked/Rel-18/38_series/38355/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-18/38_series/38355/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..074e3beab6943717343d1c634b41ef29f670952f --- /dev/null +++ b/marked/Rel-18/38_series/38355/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d23d1f829a069afea530ba629795084c3d7bbd954cce067aa021b9c35e07fc9d +size 26730 diff --git a/marked/Rel-18/38_series/38355/29f586959675cafdf81cf934954908eb_img.jpg b/marked/Rel-18/38_series/38355/29f586959675cafdf81cf934954908eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae175f60ac63830a3f13c2bf80e86d709bafdbcf --- /dev/null +++ b/marked/Rel-18/38_series/38355/29f586959675cafdf81cf934954908eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e47fd002587292fbf09964ea4d992d5fc6634a662892181006c5114b3948bc9a +size 26080 diff --git a/marked/Rel-18/38_series/38355/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-18/38_series/38355/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5affa608739da2e73445ba74c2f0ce8f264ef47 --- /dev/null +++ b/marked/Rel-18/38_series/38355/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a3dfb3421f549d0bfb5a1e09e79149eaf0ad518caf1ee57780beced9dfb733c +size 21662 diff --git a/marked/Rel-18/38_series/38355/54fabc351eda5228d2fa28cd9ba07971_img.jpg b/marked/Rel-18/38_series/38355/54fabc351eda5228d2fa28cd9ba07971_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..190989c8b317067d5c031e01d02464f631c5e37c --- /dev/null +++ b/marked/Rel-18/38_series/38355/54fabc351eda5228d2fa28cd9ba07971_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:33dafa53913206be96546daa1a267c8cdc7e66aa87d1eb5be9050f79e38bb5ef +size 40896 diff --git a/marked/Rel-18/38_series/38355/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38355/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b75b73b54c58aa4e0a5e594cba3b3ac5bf333efe --- /dev/null +++ b/marked/Rel-18/38_series/38355/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f852ab7bbdb6750055b3fc0cf85a525a13ceae28130245f20299a4947cfd0e8c +size 9639 diff --git a/marked/Rel-18/38_series/38355/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38355/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..328706bc07dfcdc1338edf2dc5ec72ae7477cf7f --- /dev/null +++ b/marked/Rel-18/38_series/38355/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d9d7ae04b198d9c359d092cd919c1e3be37ec6d6b3c6c3e53bea25d62efa0cd9 +size 5765 diff --git a/marked/Rel-18/38_series/38355/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-18/38_series/38355/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..25acbffd2d6022a0887ad7a261aadacdbd8af6dd --- /dev/null +++ b/marked/Rel-18/38_series/38355/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3fac010f2ef0921d11918b4637b3bd9d9df1a497a8a67ef413ea7df40613613f +size 20159 diff --git a/marked/Rel-18/38_series/38355/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg b/marked/Rel-18/38_series/38355/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e11418d40369c7e6259cb2225b9241b3cbe14c7a --- /dev/null +++ b/marked/Rel-18/38_series/38355/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56ff75a102770e35eb2e33c1ee7c3c3aaf2c658f41e779b1b6a4ecf80d791977 +size 19954 diff --git a/marked/Rel-18/38_series/38355/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-18/38_series/38355/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a6450146e82898fe7ab004eea12aed7c03bede6 --- /dev/null +++ b/marked/Rel-18/38_series/38355/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ccf3f74b829a45b16c35828f1c50b9291d8a70999576820b444cb21a1f9ab09 +size 33996 diff --git a/marked/Rel-18/38_series/38355/f6e8acf9f931452d01688d311b5c0364_img.jpg b/marked/Rel-18/38_series/38355/f6e8acf9f931452d01688d311b5c0364_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c8c36776cae7df29e5c96880b969d48ecf62f44d --- /dev/null +++ b/marked/Rel-18/38_series/38355/f6e8acf9f931452d01688d311b5c0364_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d983fae46469583552f6aef651aed45a2f630c5feee2c5ddfdbd252b2e96d664 +size 14341 diff --git a/marked/Rel-18/38_series/38355/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-18/38_series/38355/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..336b06261de82c4a64539b30dbf14dfec1a2a036 --- /dev/null +++ b/marked/Rel-18/38_series/38355/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ddcb352969c3b7695f3084f8dc239c4cc886ad4522c436ea7390beb8aceca602 +size 40108 diff --git a/marked/Rel-18/38_series/38355/raw.md b/marked/Rel-18/38_series/38355/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..c3c3ca86b917298bfa4a2752f27221a197a9768b --- /dev/null +++ b/marked/Rel-18/38_series/38355/raw.md @@ -0,0 +1,3389 @@ + + +# 3GPP TS 38.355 V18.0.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Sidelink Positioning Protocol (SLPP); Protocol specification (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon, and below the entire logo is the text 'A GLOBAL INITIATIVE'. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## 3GPP + +## Postal address --- + +## 3GPP support office address --- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## Internet --- + + + +## --- Copyright Notification --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|---------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions of terms, symbols and abbreviations..... | 8 | +| 3.1 Terms..... | 8 | +| 3.2 Abbreviations ..... | 8 | +| 4 Functionality of Protocol ..... | 8 | +| 4.1 General ..... | 8 | +| 4.1.1 SLPP Configuration..... | 8 | +| 4.1.2 SLPP Sessions and Transactions ..... | 9 | +| 4.1.3 SLPP Positioning Methods..... | 9 | +| 4.1.4 SLPP Messages ..... | 9 | +| 4.2 Common SLPP Session Procedure ..... | 10 | +| 4.3 SLPP Transport ..... | 11 | +| 4.3.1 Transport Layer Requirements ..... | 11 | +| 4.3.2 SLPP Duplicate Detection..... | 11 | +| 4.3.3 SLPP Acknowledgement..... | 11 | +| 4.3.3.1 General..... | 11 | +| 4.3.3.2 Procedure related to Acknowledgement ..... | 11 | +| 4.3.4 SLPP Retransmission ..... | 12 | +| 4.3.4.1 General..... | 12 | +| 4.3.4.2 Procedure related to Retransmission..... | 12 | +| 5 SLPP Procedures..... | 13 | +| 5.1 Procedures related to capability transfer ..... | 13 | +| 5.1.1 General ..... | 13 | +| 5.1.2 Capability Transfer procedure..... | 13 | +| 5.1.3 Capability Indication procedure ..... | 14 | +| 5.1.4 Transmission of SLPP Request Capabilities ..... | 14 | +| 5.1.5 Reception of SLPP Request Capabilities ..... | 14 | +| 5.1.6 Transmission of SLPP Provide Capabilities..... | 15 | +| 5.2 Procedures related to Assistance Data Transfer ..... | 15 | +| 5.2.1 General ..... | 15 | +| 5.2.2 Assistance Data Transfer procedure ..... | 15 | +| 5.2.3 Assistance Data Delivery procedure..... | 16 | +| 5.2.4 Transmission of SLPP Request Assistance Data..... | 16 | +| 5.2.5 Reception of SLPP Request Assistance Data ..... | 16 | +| 5.2.6 Reception of SLPP Provide Assistance Data ..... | 16 | +| 5.3 Procedures related to Location Information Transfer ..... | 17 | +| 5.3.1 General ..... | 17 | +| 5.3.2 Location Information Transfer procedure ..... | 17 | +| 5.3.3 Location Information Delivery procedure..... | 17 | +| 5.3.4 Transmission of Request Location Information ..... | 18 | +| 5.3.5 Reception of Request Location Information ..... | 18 | +| 5.3.6 Transmission of Provide Location Information ..... | 18 | +| 5.4 Error Handling Procedures..... | 19 | +| 5.4.1 General ..... | 19 | +| 5.4.2 Procedures related to Error Indication..... | 19 | +| 5.4.3 SLPP Error Detection..... | 19 | +| 5.4.4 Reception of an SLPP Error Message ..... | 20 | +| 5.5 Abort Procedure ..... | 20 | +| 5.5.1 General ..... | 20 | +| 5.5.2 Procedures related to Abort..... | 20 | +| 5.5.3 Reception of an SLPP Abort Message ..... | 20 | + +| | | | +|-------|----------------------------------------------------------------|----| +| 6 | Protocol data units, formats and parameters (ASN.1) ..... | 22 | +| 6.1 | General ..... | 22 | +| 6.2 | SLPP messages..... | 22 | +| 6.2.1 | General message structure..... | 22 | +| – | SLPP-PDU-Definitions ..... | 22 | +| – | SLPP-Message ..... | 24 | +| – | SLPP-MessageBody ..... | 25 | +| 6.2.2 | Message definitions..... | 26 | +| – | RequestCapabilities ..... | 26 | +| – | ProvideCapabilities ..... | 26 | +| – | RequestAssistanceData ..... | 27 | +| – | ProvideAssistanceData ..... | 27 | +| – | RequestLocationInformation ..... | 28 | +| – | ProvideLocationInformation ..... | 28 | +| – | Abort ..... | 29 | +| – | Error ..... | 29 | +| 6.3 | SLPP information elements..... | 30 | +| 6.3.1 | Common information elements ..... | 30 | +| – | ARFCN-ValueNR ..... | 30 | +| – | CommonIEsAbort ..... | 30 | +| – | CommonIEsError ..... | 31 | +| – | FreqBandIndicatorNR ..... | 31 | +| – | GNSS-ID ..... | 31 | +| – | LCS-GCS-Translation ..... | 32 | +| – | LOS-NLOS-Indicator ..... | 32 | +| – | NCGI ..... | 33 | +| – | NR-PhysCellID ..... | 33 | +| – | PositioningModes ..... | 33 | +| – | SL-RTD-Info ..... | 34 | +| – | SL-TimeStamp ..... | 35 | +| – | SL-TimingQuality ..... | 36 | +| 6.3.2 | UE capability information elements ..... | 37 | +| 6.3.3 | Positioning Method information elements ..... | 37 | +| 6.4 | Multiplicity and type constraint values ..... | 37 | +| – | Multiplicity and type constraint definitions ..... | 37 | +| – | End of SLPP-PDU-Definitions ..... | 37 | +| 6.5 | SLPP PDU Common Contents..... | 37 | +| – | SLPP-PDU-CommonContents ..... | 37 | +| – | CommonIEsRequestCapabilities ..... | 38 | +| – | CommonIEsProvideCapabilities ..... | 38 | +| – | CommonIEsRequestAssistanceData ..... | 38 | +| – | CommonIEsProvideAssistanceData ..... | 39 | +| – | CommonIEsRequestLocationInformation ..... | 39 | +| – | CommonIEsProvideLocationInformation ..... | 43 | +| – | End of SLPP-PDU-CommonContents ..... | 47 | +| 6.6 | SLPP PDU Common SL-PRS Methods Contents..... | 47 | +| – | SLPP-PDU-CommonSL-PRS-MethodsContents ..... | 47 | +| – | CommonSL-PRS-MethodsIEsRequestCapabilities ..... | 48 | +| – | CommonSL-PRS-MethodsIEsProvideCapabilities ..... | 48 | +| – | CommonSL-PRS-MethodsIEsRequestAssistanceData ..... | 49 | +| – | CommonSL-PRS-MethodsIEsProvideAssistanceData ..... | 49 | +| – | CommonSL-PRS-MethodsIEsRequestLocationInformation ..... | 51 | +| – | CommonSL-PRS-MethodsIEsProvideLocationInformation ..... | 52 | +| – | End of SLPP-PDU-CommonSL-PRS-MethodsContents ..... | 52 | +| 6.7 | SLPP PDU SL-AoA Contents..... | 52 | +| – | SLPP-PDU-SL-AoA-Contents ..... | 52 | +| – | SL-AoA-RequestCapabilities ..... | 53 | +| – | SL-AoA-ProvideCapabilities ..... | 53 | +| – | SL-AoA-RequestAssistanceData ..... | 54 | +| – | SL-AoA-ProvideAssistanceData ..... | 54 | +| – | SL-AoA-RequestLocationInformation ..... | 55 | +| – | SL-AoA-ProvideLocationInformation ..... | 55 | + +| | | | +|----------------------------------------------------|---------------------------------------------------------|-----------| +| – | End of SLPP-PDU-SL-AoA-Contents ..... | 57 | +| 6.8 | SLPP PDU SL-RTT Contents ..... | 58 | +| – | SLPP-PDU-SL-RTT-Contents ..... | 58 | +| – | SL-RTT-RequestCapabilities ..... | 58 | +| – | SL-RTT-ProvideCapabilities ..... | 58 | +| – | SL-RTT-RequestAssistanceData ..... | 59 | +| – | SL-RTT-ProvideAssistanceData ..... | 59 | +| – | SL-RTT-RequestLocationInformation ..... | 60 | +| – | SL-RTT-ProvideLocationInformation ..... | 61 | +| – | End of SLPP-PDU-SL-RTT-Contents ..... | 63 | +| 6.9 | SLPP PDU SL-TDOA Contents ..... | 63 | +| – | SLPP-PDU-SL-TDOA-Contents ..... | 63 | +| – | SL-TDOA-RequestCapabilities ..... | 64 | +| – | SL-TDOA-ProvideCapabilities ..... | 64 | +| – | SL-TDOA-RequestAssistanceData ..... | 65 | +| – | SL-TDOA-ProvideAssistanceData ..... | 65 | +| – | SL-TDOA-RequestLocationInformation ..... | 66 | +| – | SL-TDOA-ProvideLocationInformation ..... | 66 | +| – | End of SLPP-PDU-SL-TDOA-Contents ..... | 68 | +| 6.10 | SLPP PDU SL-TOA Contents ..... | 68 | +| – | SLPP-PDU-SL-TOA-Contents ..... | 68 | +| – | SL-TOA-RequestCapabilities ..... | 69 | +| – | SL-TOA-ProvideCapabilities ..... | 69 | +| – | SL-TOA-RequestAssistanceData ..... | 70 | +| – | SL-TOA-ProvideAssistanceData ..... | 70 | +| – | SL-TOA-RequestLocationInformation ..... | 71 | +| – | SL-TOA-ProvideLocationInformation ..... | 72 | +| – | End of SLPP-PDU-SL-TOA-Contents ..... | 73 | +| 6.11 | Information elements related to Discovery Message ..... | 73 | +| – | NR-DiscoveryMessageMetaDataContents ..... | 74 | +| – | RSPP-Metadata ..... | 74 | +| – | End of NR-DiscoveryMessageMetaDataContents ..... | 74 | +| Annex A (informative): Change history ..... | | 76 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the Sidelink Positioning Protocol (SLPP) for the interface between UEs and between UE and LMF. + +# --- 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.331: "NR; Radio Resource Control (RRC); Protocol specification". +- [3] 3GPP TS 38.305: "NG Radio Access Network (NG-RAN); Stage 2 functional specification of User Equipment (UE) positioning in NG-RAN". +- [4] ITU-T Recommendation X.691 (07/2002) "Information technology - ASN.1 encoding rules: Specification of Packed Encoding Rules (PER)" (Same as the ISO/IEC International Standard 8825-2). +- [5] 3GPP TS 23.273: "5G System (5GS) Location Services (LCS); Stage 2". +- [6] 3GPP TS 38.211: "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical channels and modulation". +- [7] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)". +- [8] 3GPP TR 38.901: "Technical Specification Group Radio Access Network; Study on channel model for frequencies from 0.5 to 100 GHz". +- [9] 3GPP TS 23.287: "Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services". +- [10] 3GPP TS 38.101-2: "NR; User Equipment (UE) radio transmission and reception; Part 2: Range 2 Standalone". +- [11] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone". +- [12] 3GPP TS 23.586: "Technical Specification Group Services and System Aspects; Architectural Enhancements to support Ranging based services and Sidelink Positioning". + +# 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:** The individual contents of an information element are referred to as fields. + +**Ranging:** Refers to the determination of the distance between two UEs or more UEs and/or the direction of one UE (i.e. Target UE) from another UE via PC5 interface. + +**Ranging/Sidelink Positioning:** AS functionality enabling ranging-based services and sidelink positioning as specified in TS 23.586 [12]. + +**Anchor UE:** A UE, supporting positioning of target UE, e.g. by transmitting and/or receiving reference signals for positioning, providing positioning-related information, etc. over the Sidelink interface. + +**Target UE:** A UE whose distance, direction and/or position is measured with the support from one or multiple Anchor UEs using Sidelink in the Ranging based service and Sidelink positioning. + +**UE-only Operation:** Operation of Ranging/Sidelink Positioning in which the service request handling and result calculation are performed by 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]. + +| | | +|--------------|-----------------------------------------------------------------------------------| +| LMF | Location Management Function | +| LOS | Line-of-Sight | +| NLOS | Non-Line-of-Sight | +| SL | Sidelink | +| SL-AoA | Sidelink Angle-of-Arrival | +| SLPP | Sidelink Positioning Protocol | +| SL-PRS | Sidelink Positioning Reference Signals | +| SL-PRS-RSRP | Sidelink Positioning Reference Signals based Reference Signal Received Power | +| SL-PRS-RSRPP | Sidelink Positioning Reference Signals based Reference Signal Received Path Power | +| SL-PRS-RSTD | Sidelink Positioning Reference Signals based Reference Signal Time Difference | +| SL-PRS-RTOA | Sidelink Positioning Reference Signals based Relative Time of Arrival | +| SL-RTT | Sidelink Round Trip Time | +| SL-TDOA | Sidelink Time Difference Of Arrival | +| SL-TOA | Sidelink Time Of Arrival | +| UE | User Equipment | + +# 4 Functionality of Protocol + +## 4.1 General + +### 4.1.1 SLPP Configuration + +SLPP is used point-to-point between Endpoints, e.g. server and target in order to obtain absolute position, relative position, or ranging information of target UE using sidelink measurements obtained by one or more reference sources. Figure 4.1.1-1 shows the configuration as applied to the sidelink positioning (as defined in TS 38.305 [3] and TS 23.273 [5]). + +![Diagram illustrating the SLPP Configuration for sidelink positioning. A Target UE sends 'Measurements of Location' to a Server. The Server sends 'Assistance Data' back to the Target. A Reference Source sends 'NR PC5 radio signals' to the Target and 'Assistance Data' to the Server. A dashed line labeled 'SLPP' indicates the protocol layer.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +``` + +graph TD + Target[Target] -- "Measurements of Location" --> Server[Server] + Server -- "Assistance Data" --> Target + RS[Reference Source] -.-> Target : "NR PC5 radio signals" + RS -- "Assistance Data" --> Server + subgraph SLPP + Target + Server + end + +``` + +Diagram illustrating the SLPP Configuration for sidelink positioning. A Target UE sends 'Measurements of Location' to a Server. The Server sends 'Assistance Data' back to the Target. A Reference Source sends 'NR PC5 radio signals' to the Target and 'Assistance Data' to the Server. A dashed line labeled 'SLPP' indicates the protocol layer. + +Figure 4.1.1-1: SLPP Configuration for sidelink positioning + +### 4.1.2 SLPP Sessions and Transactions + +An SLPP session is used between UEs or a Location Server and a UE in order to obtain location related measurements based on NR PC5 radio signals, a location estimate or to transfer assistance data. A single SLPP session is used to support a single location request (e.g., for a single SL-MT-LR, or SL-MO-LR). Multiple SLPP sessions can be used between the same endpoints to support multiple different location requests (as required by TS 23.273 [5]). For UE-only Operation, the instigator of an SLPP session which is the Endpoint who receives the LCS request, initiates an SLPP session by sending an SLPP message containing an assigned session ID (session identifier) to the other endpoint(s). All constituent messages within a session shall contain the same session ID. For LMF involved Operation, the session ID is assigned by target UE and contained in the SLPP messages used for communication between UEs. The session ID may be included in the SLPP message for the communication between target UE and the LMF. + +Each SLPP session comprises one or more SLPP transactions, with each SLPP transaction performing a single operation (capability exchange, assistance data transfer, or location information transfer). The SLPP transactions are realized as SLPP procedures. The instigator of an SLPP session will always instigate the first SLPP transaction, but subsequent transactions may be instigated by either end. SLPP transactions within a session may occur serially or in parallel. SLPP transactions are indicated at the SLPP protocol level with a transaction ID in order to associate messages with one another (e.g., request and response). + +Messages within a transaction are linked by a common transaction identifier. + +### 4.1.3 SLPP Positioning Methods + +This version of the specification defines SL-TDOA, SL-TOA, SL-AoA and SL-RTT positioning methods based on NR PC5 radio signals. + +### 4.1.4 SLPP Messages + +Each SLPP transaction involves the exchange of one or more SLPP messages between Endpoint A and Endpoint B. The general format of an SLPP message consists of a set of common fields followed by a body. The body (which may be empty) contains information specific to a particular message type. Each message type contains information specific to one or more positioning methods and/or information common to all positioning methods. + +The common fields are as follows: + +| Field | Role | +|----------------------|--------------------------------------------------------------------------------| +| Session ID | Identify messages belonging to the same session | +| Transaction ID | Identify messages belonging to the same transaction | +| Transaction End Flag | Indicate when a transaction (e.g. one with periodic responses) has ended | +| Sequence Number | Enable detection of a duplicate SLPP message at a receiver | +| Acknowledgement | Enable an acknowledgement to be requested and/or returned for any SLPP message | + +The following message types are defined: + +- Request Capabilities; +- Provide Capabilities; +- Request Assistance Data; +- Provide Assistance Data; +- Request Location Information; +- Provide Location Information; +- Abort; +- Error. + +## 4.2 Common SLPP Session Procedure + +The purpose of this procedure is to support an SLPP session comprising a sequence of SLPP transactions. The procedure is described in Figure 4.2-1. + +![Sequence diagram of the SLPP Session Procedure between Endpoint A and Endpoint B.](54fabc351eda5228d2fa28cd9ba07971_img.jpg) + +``` + +sequenceDiagram + participant A as Endpoint A + participant B as Endpoint B + Note right of A: 1. SLPP Message (Transaction ID=j, Body) + A->>B: 1. SLPP Message (Transaction ID=j, Body) + Note left of B: 2. Additional SLPP Message (Transaction ID=j, Body) + B-->>A: 2. Additional SLPP Message (Transaction ID=j, Body) + Note left of A: 3. SLPP Message (Transaction ID=k, Body) + A-->>B: 3. SLPP Message (Transaction ID=k, Body) + Note left of B: 4. SLPP Message (Transaction ID=N, Body) + B-->>A: 4. SLPP Message (Transaction ID=N, Body) + +``` + +The diagram illustrates the SLPP Session Procedure between Endpoint A and Endpoint B. It consists of four steps: + + +- Endpoint A sends an SLPP Message (Transaction ID=j, Body) to Endpoint B. +- Endpoint B responds with an Additional SLPP Message (Transaction ID=j, Body) to Endpoint A. +- Endpoint A sends another SLPP Message (Transaction ID=k, Body) to Endpoint B. +- Endpoint B responds with a final SLPP Message (Transaction ID=N, Body) to Endpoint A. + +Sequence diagram of the SLPP Session Procedure between Endpoint A and Endpoint B. + +Figure 4.2-1 SLPP Session Procedure + +1. Endpoint A, which is the Endpoint who receives the LCS request, initiates an SLPP session by sending an SLPP message containing an assigned session identifier for an initial SLPP transaction $j$ to the other endpoint B. +2. Endpoints A and B may exchange further messages to continue the transaction started in step 1. +3. Either endpoint may instigate further transactions by sending additional SLPP messages. +4. A session is terminated by a final transaction $N$ in which SLPP messages will be exchanged between the two endpoints. + +Within the same session, all constituent messages shall contain the same session identifier and within each transaction, all constituent messages shall contain the same transaction identifier. The last message sent in each transaction shall have the IE *endTransaction* set to TRUE. Transactions that occur in parallel shall use different transaction IDs; transaction IDs for completed transactions may be reused at any time after the final message of the previous transaction with the same ID is known to have been received. + +## 4.3 SLPP Transport + +### 4.3.1 Transport Layer Requirements + +SLPP requires reliable, in-sequence delivery of SLPP messages from the underlying transport layers. This clause describes the transport capabilities that are available within SLPP. A UE implementing SLPP shall support SLPP reliable transport (including all three of duplicate detection, acknowledgement, and retransmission). + +### 4.3.2 SLPP Duplicate Detection + +A sender shall include a sequence number in all SLPP messages sent for a particular location session. The sequence number shall be distinct for different SLPP messages sent by the same endpoint for the same endpoint in the same location session (e.g., may start at zero in the first SLPP message and increase monotonically in each succeeding SLPP message). Sequence numbers used in the messages transmitted from different endpoints or for different endpoint are independent (e.g., can be the same). + +A receiver shall record the most recent received sequence number for each location session. If a message is received carrying the same sequence number as that last received for the associated location session, it shall be discarded. Otherwise (i.e., if the sequence number is different), the message shall be processed. + +Sending and receiving sequence numbers shall be deleted in a server when the associated location session is terminated and shall be deleted in the UE(s) when there has been no activity for a particular location session for 10 minutes. + +### 4.3.3 SLPP Acknowledgement + +#### 4.3.3.1 General + +Each SLPP message may carry an acknowledgement request and/or an acknowledgement indicator. A SLPP message including an acknowledgement request (i.e., that include the IE *ackRequested* set to TRUE) shall also include a sequence number. Upon reception of an SLPP message which includes the IE *ackRequested* set to TRUE, a receiver returns an SLPP message with an acknowledgement response (i.e., that includes the *ackIndicator* IE set to the same sequence number of the message being acknowledged). An acknowledgement response may contain no SLPP message body (in which case only the sequence number being acknowledged is significant); alternatively, the acknowledgement may be sent in an SLPP message along with an SLPP message body. An acknowledgement is returned for each received SLPP message that requested an acknowledgement including any duplicate(s). Once a sender receives an acknowledgement for an SLPP message, and provided any included sequence number is matching, it is permitted to send the next SLPP message. No message reordering is needed at the receiver since this stop-and-wait method of sending ensures that messages normally arrive in the correct order. + +When an SLPP message is transported via a NAS SL-MO-LR request, the message does not request an acknowledgement. + +#### 4.3.3.2 Procedure related to Acknowledgement + +Figure 4.3.3.2-1 shows the procedure related to acknowledgement. + +![Sequence diagram illustrating the SLPP Acknowledgement procedure between Endpoint A and Endpoint B.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +``` +sequenceDiagram + participant Endpoint A + participant Endpoint B + Note left of Endpoint A: + Endpoint A->>Endpoint B: 1. Message N + Note right of Endpoint B: + Endpoint B-->>Endpoint A: 2. Message N Acknowledgement + Note left of Endpoint A: + Endpoint A->>Endpoint B: 3. Message N+1 +``` + +The diagram shows a sequence of three messages between Endpoint A and Endpoint B. 1. Endpoint A sends 'Message N' to Endpoint B. 2. Endpoint B receives 'Message N' and sends 'Message N Acknowledgement' back to Endpoint A. 3. Endpoint A receives the acknowledgement and sends 'Message N+1' to Endpoint B. + +Sequence diagram illustrating the SLPP Acknowledgement procedure between Endpoint A and Endpoint B. + +**Figure 4.3.3.2-1: SLPP Acknowledgement procedure** + +1. Endpoint A sends an SLPP message $N$ to Endpoint B which includes the IE *ackRequested* set to TRUE and a sequence number. +2. If SLPP message $N$ is received and Endpoint B is able to decode the *ackRequested* value and sequence number, Endpoint B shall return an acknowledgement for message $N$ . The acknowledgement shall contain the IE *ackIndicator* set to the same sequence number as that in message $N$ . +3. When the acknowledgement for SLPP message $N$ is received and provided the included *ackIndicator* IE matches the sequence number sent in message $N$ , Endpoint A sends the next SLPP message $N+1$ to Endpoint B when this message is available. + +### 4.3.4 SLPP Retransmission + +#### 4.3.4.1 General + +This capability builds on the acknowledgement and duplicate detection capabilities. When an SLPP message which requires acknowledgement is sent and not acknowledged, it is resent by the sender following a timeout period up to three times. If still unacknowledged after that, the sender aborts all SLPP activity for this Endpoint. The timeout period is determined by the sender implementation but shall not be less than a minimum value of 250 ms. + +#### 4.3.4.2 Procedure related to Retransmission + +Figure 4.3.4.2-1 shows the procedure related to retransmission when combined with acknowledgement and duplicate detection. + +![Sequence diagram illustrating the SLPP Retransmission procedure between Endpoint A and Endpoint B.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +``` +sequenceDiagram + participant Endpoint A + participant Endpoint B + Note left of Endpoint A: Endpoint A + Note right of Endpoint B: Endpoint B + Endpoint A->>Endpoint B: 1. Message N + Endpoint B-->>Endpoint A: 2. Message N Acknowledgement + Note left of Endpoint A: Timeout + Endpoint A->>Endpoint B: 3. Message N Retransmission + Endpoint B-->>Endpoint A: 4. Message N Acknowledgement + Note left of Endpoint A: Ack received + Endpoint A->>Endpoint B: 5. Message N+1 +``` + +The diagram shows a sequence of five messages between Endpoint A and Endpoint B. 1. Endpoint A sends a solid arrow message 'Message N' to Endpoint B. 2. Endpoint B responds with a dashed arrow message 'Message N Acknowledgement' back to Endpoint A. 3. If no acknowledgement is received by Endpoint A, it retransmits 'Message N' as a dashed arrow to Endpoint B. 4. Endpoint B receives the retransmission and sends another dashed arrow 'Message N Acknowledgement' back to Endpoint A. 5. Once an acknowledgement is received by Endpoint A, it sends the next message, 'Message N+1', as a solid arrow to Endpoint B. + +Sequence diagram illustrating the SLPP Retransmission procedure between Endpoint A and Endpoint B. + +Figure 4.3.4.2-1: SLPP Retransmission procedure + +1. Endpoint A sends an SLPP message *N* to Endpoint B for a particular location session and includes a request for acknowledgement along with a sequence number. +2. If SLPP message *N* is received and Endpoint B is able to decode the *ackRequested* value and sequence number (regardless of whether the message body can be correctly decoded), Endpoint B shall return an acknowledgement for message *N*. If the acknowledgement is received by Endpoint A (such that the acknowledged message can be identified and sequence numbers are matching), Endpoint A skips steps 3 and 4. +3. If the acknowledgement in step 2 is not received after a timeout period, Endpoint A shall retransmit SLPP message *N* and shall include the same sequence number as in step 1. +4. If SLPP message *N* in step 3 is received and Endpoint B is able to decode the *ackRequested* value and sequence number (regardless of whether the message body can be correctly decoded and whether or not the message is considered a duplicate), Endpoint B shall return an acknowledgement. Steps 3 may be repeated one or more times if the acknowledgement in step 4 is not received after a timeout period by Endpoint A. If the acknowledgement in step 4 is still not received after sending three retransmissions, Endpoint A shall abort all procedures and activity associated with SLPP support for this Endpoint B. +5. Once an acknowledgement in step 2 or step 4 is received, Endpoint A sends the next SLPP message *N+1* for the location session to Endpoint B when this message is available. + +# 5 SLPP Procedures + +## 5.1 Procedures related to capability transfer + +### 5.1.1 General + +The purpose of the procedures that are grouped together in this clause is to enable the transfer of capabilities from Endpoint A to Endpoint B. Capabilities in this context refer to positioning and protocol capabilities related to SLPP and the positioning methods supported by SLPP. + +### 5.1.2 Capability Transfer procedure + +The Capability Transfer procedure is shown in Figure 5.1.2-1. + +![Sequence diagram for SLPP Capability Transfer procedure. Endpoint B sends a RequestCapabilities message to Endpoint A, and Endpoint A responds with a ProvideCapabilities message.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +``` + +sequenceDiagram + participant Endpoint A + participant Endpoint B + Note right of Endpoint B: 1. RequestCapabilities + Endpoint B->>Endpoint A: RequestCapabilities + Note right of Endpoint A: 2. ProvideCapabilities + Endpoint A->>Endpoint B: ProvideCapabilities + +``` + +Sequence diagram for SLPP Capability Transfer procedure. Endpoint B sends a RequestCapabilities message to Endpoint A, and Endpoint A responds with a ProvideCapabilities message. + +**Figure 5.1.2-1: SLPP Capability Transfer procedure** + +1. Endpoint B sends a *RequestCapabilities* message to Endpoint A. Endpoint B may indicate the types of capability needed. +2. Endpoint A responds with a *ProvideCapabilities* message to Endpoint B. The capabilities shall correspond to any capability types specified in step 1. This message shall include the *endTransaction* IE set to TRUE. + +### 5.1.3 Capability Indication procedure + +The Capability Indication procedure allows the Endpoint A to provide unsolicited capabilities to the Endpoint B and is shown in Figure 5.1.3-1. + +![Sequence diagram for SLPP Capability Indication procedure. Endpoint A sends a ProvideCapabilities message to Endpoint B.](f6e8acf9f931452d01688d311b5c0364_img.jpg) + +``` + +sequenceDiagram + participant Endpoint A + participant Endpoint B + Note right of Endpoint A: 1. ProvideCapabilities + Endpoint A->>Endpoint B: ProvideCapabilities + +``` + +Sequence diagram for SLPP Capability Indication procedure. Endpoint A sends a ProvideCapabilities message to Endpoint B. + +**Figure 5.1.3-1: SLPP Capability Indication procedure** + +1. Endpoint A sends a *ProvideCapabilities* message to Endpoint B. This message shall include the *endTransaction* IE set to TRUE. + +### 5.1.4 Transmission of SLPP Request Capabilities + +When triggered to transmit a *RequestCapabilities* message, Endpoint B shall: + +- 1) set the method specific *RequestCapabilities* IEs in accordance with the information received from upper layers. +- 1) deliver the message to lower layers for transmission. + +### 5.1.5 Reception of SLPP Request Capabilities + +Upon receiving a *RequestCapabilities* message, Endpoint A shall generate a *ProvideCapabilities* message as a response. + +Endpoint A shall: + +- 1) for each positioning method for which a request for capabilities is included in the message: + - 2) if Endpoint A supports this positioning method: + - 3) include the capabilities of Endpoint A for that supported positioning method in the response message; + +- 1> set the IE *SessionID* in the response message to the same value as the IE *SessionID* in the received message if received; +- 1> set the IE *SLPP-TransactionID* in the response message to the same value as the IE *SLPP-TransactionID* in the received message; +- 1> deliver the response message to lower layers for transmission. + +### 5.1.6 Transmission of SLPP Provide Capabilities + +When triggered to transmit a *ProvideCapabilities* message, Endpoint A shall: + +- 1> for each positioning method whose capabilities are to be indicated: + - 2> set the corresponding IE to include Endpoint A's capabilities; +- 1> deliver the response to lower layers for transmission. + +## 5.2 Procedures related to Assistance Data Transfer + +### 5.2.1 General + +The purpose of the procedures that are grouped together in this clause is to enable Endpoint A to request assistance data from Endpoint B to assist in positioning, and to enable Endpoint B to transfer assistance data to Endpoint A in the absence of a request. + +### 5.2.2 Assistance Data Transfer procedure + +The Assistance Data Transfer procedure is shown in Figure 5.2.2-1. + +![Sequence diagram of the SLPP Assistance data transfer procedure between Endpoint A and Endpoint B.](18722c46c9e8475524e634dedd08bac2_img.jpg) + +``` +sequenceDiagram + participant Endpoint A + participant Endpoint B + Note left of Endpoint A: + Endpoint A->>Endpoint B: 1. RequestAssistanceData + Note right of Endpoint B: + Endpoint B-->>Endpoint A: 2. ProvideAssistanceData + Note right of Endpoint B: + Endpoint B-->>Endpoint A: 3. ProvideAssistanceData +``` + +The diagram illustrates the SLPP Assistance data transfer procedure between Endpoint A and Endpoint B. It consists of three steps: 1. Endpoint A sends a *RequestAssistanceData* message to Endpoint B. 2. Endpoint B responds with a *ProvideAssistanceData* message to Endpoint A. 3. Endpoint B may transmit one or more additional *ProvideAssistanceData* messages to Endpoint A. The third step is shown with a dashed line, indicating it is optional. + +Sequence diagram of the SLPP Assistance data transfer procedure between Endpoint A and Endpoint B. + +Figure 5.2.2-1: SLPP Assistance data transfer procedure + +1. Endpoint A sends a *RequestAssistanceData* message to Endpoint B. +2. Endpoint B responds with a *ProvideAssistanceData* message to Endpoint A containing assistance data. The transferred assistance data should match or be a subset of the assistance data requested in step 1. Endpoint B may also provide any not requested information that it considers useful to Endpoint A. If step 3 does not occur, this message shall set the *endTransaction* IE to TRUE. +3. Endpoint B may transmit one or more additional *ProvideAssistanceData* messages to Endpoint A containing further assistance data. The transferred assistance data should match or be a subset of the assistance data requested in step 1. Endpoint B may also provide any not requested information that it considers useful to Endpoint A. The last message shall include the *endTransaction* IE set to TRUE. + +### 5.2.3 Assistance Data Delivery procedure + +The Assistance Data Delivery procedure allows Endpoint B to provide unsolicited assistance data to Endpoint A and is shown in Figure 5.2.3-1. + +![Sequence diagram showing the SLPP Assistance data transfer procedure between Endpoint A and Endpoint B. Step 1: Endpoint B sends a solid line 'ProvideAssistanceData' message to Endpoint A. Step 2: Endpoint B sends a dashed line 'ProvideAssistanceData' message to Endpoint A.](a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg) + +``` + +sequenceDiagram + participant Endpoint A + participant Endpoint B + Note right of Endpoint B: 1. ProvideAssistanceData + Endpoint B->>Endpoint A: 1. ProvideAssistanceData + Note right of Endpoint B: 2. ProvideAssistanceData + Endpoint B-->>Endpoint A: 2. ProvideAssistanceData + +``` + +Sequence diagram showing the SLPP Assistance data transfer procedure between Endpoint A and Endpoint B. Step 1: Endpoint B sends a solid line 'ProvideAssistanceData' message to Endpoint A. Step 2: Endpoint B sends a dashed line 'ProvideAssistanceData' message to Endpoint A. + +**Figure 5.2.3-1: SLPP Assistance data transfer procedure** + +1. Endpoint B sends a *ProvideAssistanceData* message to Endpoint A containing assistance data. If step 2 does not occur, this message shall set the *endTransaction* IE to TRUE. +2. Endpoint B may transmit one or more additional *ProvideAssistanceData* messages to Endpoint A containing additional assistance data. The last message shall include the *endTransaction* IE set to TRUE. + +### 5.2.4 Transmission of SLPP Request Assistance Data + +When triggered to transmit a *RequestAssistanceData* message, Endpoint A shall: + +- 1) set the method specific *RequestAssistanceData* IEs in accordance with the information received from upper layers. +- 1) deliver the message to lower layers for transmission. + +### 5.2.5 Reception of SLPP Request Assistance Data + +Upon receiving a *RequestAssistanceData* message, Endpoint B shall generate a *ProvideAssistanceData* message as a response. + +Endpoint B shall: + +- 1) for each positioning method for which a request for assistance data is included in the message: + - 2) if Endpoint B supports this positioning method: + - 3) include the assistance data for that supported positioning method in the response message; +- 1) set the IE *SessionID* in the response message to the same value as the IE *SessionID* in the received message if received; +- 1) set the IE *SLPP-TransactionID* in the response message to the same value as the IE *SLPP-TransactionID* in the received message; +- 1) deliver the response message to lower layers for transmission. + +### 5.2.6 Reception of SLPP Provide Assistance Data + +Upon receiving a *ProvideAssistanceData* message, Endpoint A shall: + +- 1) for each positioning method contained in the message: + +2) deliver the related assistance data to upper layers. + +## 5.3 Procedures related to Location Information Transfer + +### 5.3.1 General + +The purpose of the procedures that are grouped together in this clause is to enable Endpoint B to request location measurement data and/or a location estimate from Endpoint A, and to enable Endpoint A to transfer location measurement data and/or a location estimate to Endpoint B in the absence of a request. + +### 5.3.2 Location Information Transfer procedure + +The Location Information Transfer procedure is shown in Figure 5.3.2-1. + +![Sequence diagram of the SLPP Location Information transfer procedure between Endpoint A and Endpoint B.](29f586959675cafdf81cf934954908eb_img.jpg) + +``` +sequenceDiagram + participant Endpoint B + participant Endpoint A + Note left of Endpoint B: + Endpoint B->>Endpoint A: 1. RequestLocationInformation + Note right of Endpoint A: + Endpoint A->>Endpoint B: 2. ProvideLocationInformation + Note right of Endpoint A: + Endpoint A-->>Endpoint B: 3. ProvideLocationInformation + Note right of Endpoint B: +``` + +The diagram illustrates the SLPP Location Information transfer procedure between Endpoint A and Endpoint B. It consists of three steps: 1. Endpoint B sends a *RequestLocationInformation* message to Endpoint A. 2. Endpoint A responds with a *ProvideLocationInformation* message. 3. If requested in step 1, Endpoint A sends additional *ProvideLocationInformation* messages, represented by a dashed line, until the last message which sets the *endTransaction* IE to TRUE. + +Sequence diagram of the SLPP Location Information transfer procedure between Endpoint A and Endpoint B. + +Figure 5.3.2-1: SLPP Location Information transfer procedure + +1. Endpoint B sends a *RequestLocationInformation* message to Endpoint A to request location information, indicating the type of location information needed and potentially the associated QoS. +2. Endpoint A sends a *ProvideLocationInformation* message to Endpoint B to transfer location information. The location information transferred should match or be a subset of the location information requested in step 1 unless Endpoint B explicitly allows additional location information. If step 3 does not occur, this message shall set the *endTransaction* IE to TRUE. +3. If requested in step 1, Endpoint A sends additional *ProvideLocationInformation* messages to Endpoint B to transfer location information. The location information transferred should match or be a subset of the location information requested in step 1 unless Endpoint B explicitly allows additional location information. The last message shall include the *endTransaction* IE set to TRUE. + +### 5.3.3 Location Information Delivery procedure + +The Location Information Delivery procedure allows Endpoint A to provide unsolicited location information to Endpoint B. The procedure is shown in Figure 5.3.3-1. + +![Sequence diagram illustrating the SLPP Location Information Delivery procedure between Endpoint A and Endpoint B. Step 1 shows a solid arrow from Endpoint A to Endpoint B labeled '1. ProvideLocationInformation'. Step 2 shows a dashed arrow from Endpoint A to Endpoint B labeled '2. ProvideLocationInformation'.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +``` + +sequenceDiagram + participant Endpoint A + participant Endpoint B + Note left of Endpoint A: Step 1 + Endpoint A->>Endpoint B: 1. ProvideLocationInformation + Note left of Endpoint A: Step 2 + Endpoint A-->>Endpoint B: 2. ProvideLocationInformation + +``` + +Sequence diagram illustrating the SLPP Location Information Delivery procedure between Endpoint A and Endpoint B. Step 1 shows a solid arrow from Endpoint A to Endpoint B labeled '1. ProvideLocationInformation'. Step 2 shows a dashed arrow from Endpoint A to Endpoint B labeled '2. ProvideLocationInformation'. + +**Figure 5.3.3-1: SLPP Location Information Delivery procedure** + +1. Endpoint A sends a *ProvideLocationInformation* message to Endpoint B to transfer location information. If step 2 does not occur, this message shall set the *endTransaction* IE to TRUE. +2. Endpoint A may send one or more additional *ProvideLocationInformation* messages to Endpoint B containing additional location information data. The last message shall include the *endTransaction* IE set to TRUE. + +### 5.3.4 Transmission of Request Location Information + +When triggered to transmit a *RequestLocationInformation* message, Endpoint B shall: + +- 1> set the method specific *RequestLocationInformation* IEs in accordance with the information received from upper layers. +- 1> deliver the message to lower layers for transmission. + +### 5.3.5 Reception of Request Location Information + +Upon receiving a *RequestLocationInformation* message, Endpoint A shall: + +- 1> if the requested information is compatible with Endpoint A's capabilities and configuration: + - 2> include the requested information in a *ProvideLocationInformation* message; + - 2> set the IE *SessionID* in the response message to the same value as the IE *SessionID* in the received message if received; + - 2> set the IE *SLPP-TransactionID* in the response to the same value as the IE *SLPP-TransactionID* in the received message; + - 2> deliver the *ProvideLocationInformation* message to lower layers for transmission. +- 1> otherwise: + - 2> if one or more positioning methods are included that Endpoint A does not support: + - 3> continue to process the message as if it contained only information for the supported positioning methods; + - 3> handle the signaling content of the unsupported positioning methods by SLPP error detection as in 5.4.3. + +### 5.3.6 Transmission of Provide Location Information + +When triggered to transmit *ProvideLocationInformation* message, Endpoint A shall: + +- 1> for each positioning method contained in the message: + +- 2> set the corresponding IE to include the available location information; +- 1> deliver the response to lower layers for transmission. + +## 5.4 Error Handling Procedures + +### 5.4.1 General + +This clause describes how a receiving entity behaves in cases when it receives erroneous or unexpected data or detects that certain data are missing. + +### 5.4.2 Procedures related to Error Indication + +Figure 5.4.2-1 shows the Error indication procedure. + +![Sequence diagram illustrating the SLPP Error Indication procedure between Endpoint A and Endpoint B. Step 1: Endpoint A sends a solid arrow labeled '1. SLPP Message' to Endpoint B. Step 2: Endpoint B returns a dashed arrow labeled '2. Error' to Endpoint A.](04f51626e2e10a16e3eb2c4b33cb2742_img.jpg) + +``` + +sequenceDiagram + participant A as Endpoint A + participant B as Endpoint B + Note left of A: + A->>B: 1. SLPP Message + Note right of B: + B-->>A: 2. Error + +``` + +Sequence diagram illustrating the SLPP Error Indication procedure between Endpoint A and Endpoint B. Step 1: Endpoint A sends a solid arrow labeled '1. SLPP Message' to Endpoint B. Step 2: Endpoint B returns a dashed arrow labeled '2. Error' to Endpoint A. + +**Figure 5.4.2-1: SLPP Error Indication procedure** + +1. Endpoint A sends an SLPP message to Endpoint B. +2. Endpoint B determines that the SLPP message in step 1 contains an error. Endpoint B returns an *Error* message to Endpoint A indicating the error or errors and discards the message in step 1. If Endpoint B is able to determine that the erroneous SLPP message in step 1 is an SLPP Error or Abort Message, Endpoint B discards the message in step 1 without returning an *Error* message to Endpoint A. + +### 5.4.3 SLPP Error Detection + +Upon receiving any SLPP message, the receiving entity shall attempt to decode the message and verify the presence of any errors and: + +- 1> if decoding errors are encountered: + - 2> if the receiver cannot determine that the received message is an SLPP *Error* or *Abort* message: + - 3> return an SLPP *Error* message to the sender and include the *SessionID* (if PC5-U is used as transport layer) and the received *SLPP-TransactionID*, if they were decoded, and type of error; + - 3> discard the received message and stop the error detection procedure; +- 1> if the message is a duplicate of a previously received message: + - 2> discard the message and stop the error detection procedure; +- 1> if the *SLPP-TransactionID* matches the *SLPP-TransactionID* for a procedure that is still ongoing for the same session and the message type is invalid for the current state of the procedure: + - 2> abort the ongoing procedure; + - 2> return an SLPP *Error* message to the sender and include the *SessionID* (if PC5-U is used as transport layer), the received transaction ID and type of error; + +- 2> discard the message and stop the error detection procedure; +- 1> if the message type is an SLPP *RequestCapabilities* and some of the requested information is not supported: + - 2> return any information that can be provided in a normal response. +- 1> if the message type is an SLPP *RequestAssistanceData* or *RequestLocationInformation* and some or all of the requested information is not supported: + - 2> return any information that can be provided in a normal response, which includes indications on other information that is not supported. + +### 5.4.4 Reception of an SLPP Error Message + +Upon receiving an *Error* message, Endpoint shall: + +- 1> abort any ongoing procedure associated with the *SessionID* and the *SLPP-TransactionID* if included in the received message. + +Endpoint may: + +- 1> restart the aborted procedure taking into consideration the returned error information. + +## 5.5 Abort Procedure + +### 5.5.1 General + +The purpose of the abort procedure is to allow Endpoints to abort an ongoing procedure due to some unexpected event (e.g., cancellation of a location request by an LCS client). It can also be used to stop an ongoing procedure (e.g., periodic location reporting from an Endpoint). + +### 5.5.2 Procedures related to Abort + +Figure 5.5.2-1 shows the Abort procedure. + +![Sequence diagram illustrating the SLPP Abort procedure between Endpoint A and Endpoint B.](1bf34e86af3591c80bfbc1c318f811c0_img.jpg) + +``` +sequenceDiagram + participant Endpoint A + participant Endpoint B + Note over Endpoint A, Endpoint B: 1. Ongoing Procedure P + Endpoint A->>Endpoint B: 2. Abort +``` + +The diagram shows two vertical lifelines for Endpoint A and Endpoint B. A horizontal bar labeled '1. Ongoing Procedure P' spans across both lifelines, indicating an active process. From a point on the Endpoint A lifeline, below the procedure bar, a solid arrow labeled '2. Abort' points to the Endpoint B lifeline. + +Sequence diagram illustrating the SLPP Abort procedure between Endpoint A and Endpoint B. + +Figure 5.5.2-1: SLPP Abort procedure + +1. A procedure P is ongoing between endpoints A and B. +2. Endpoint A determines that the procedure must be aborted and sends an *Abort* message to Endpoint B carrying the *SessionID* (if PC5-U is used as transport layer) and the *SLPP-TransactionID* for procedure P. Endpoint B aborts procedure P. + +### 5.5.3 Reception of an SLPP Abort Message + +Upon receiving an *Abort* message, Endpoint shall: + +- 1> abort any ongoing procedure associated with the *SessionID* and the *SLPP-TransactionID* indicated in the message. + +# 6 Protocol data units, formats and parameters (ASN.1) + +## 6.1 General + +The contents of each SLPP message is specified in clause 6.2 using ASN.1 to specify the message syntax and using tables when needed to provide further detailed information about the fields specified in the message syntax. The syntax of the information elements that are defined as stand-alone abstract types is further specified in a similar manner in clause 6.3. + +The ASN.1 in this clause uses the same format and coding conventions as described in Annex A of TS 38.331 [2]. Upon receiving a message with the field absent, the UE releases the current value. + +Transfer syntax for SLPP messages is derived from their ASN.1 definitions by use of Basic Packed Encoding Rules (BASIC-PER), Unaligned Variant, as specified in ITU-T Rec. X.691 [4]. The encoded SLPP message always contains a multiple of 8 bits. + +Transfer syntax for SLPP IEs is derived from their ASN.1 definitions by use of Basic Packed Encoding Rules (BASIC-PER), Unaligned Variant, as specified in ITU-T Rec. X.691 [4]. The encoded SLPP IE always contains a multiple of 8 bits. This applies when a single SLPP IE is encoded as the basic production, i.e. for other purposes than encoding the SLPP IE within an SLPP message. + +When specifying information elements which are to be represented by BIT STRINGs, if not otherwise specifically stated in the field description of the concerned IE or elsewhere, the following principle applies with regards to the ordering of bits: + +- The first bit (leftmost bit) contains the most significant bit (MSB); +- the last bit (rightmost bit) contains the least significant bit (LSB). + +## 6.2 SLPP messages + +### 6.2.1 General message structure + +#### – *SLPP-PDU-Definitions* + +This ASN.1 segment is the start of the SLPP PDU definitions. + +``` +-- ASN1START +-- TAG-SLPP-PDU-DEFINITIONS-START + +SLPP-PDU-Definitions DEFINITIONS AUTOMATIC TAGS ::= +BEGIN +``` + +``` +IMPORTS + CommonIEsRequestCapabilities, + CommonIEsProvideCapabilities, + CommonIEsRequestAssistanceData, + CommonIEsProvideAssistanceData, + CommonIEsRequestLocationInformation, + CommonIEsProvideLocationInformation + +FROM + SLPP-PDU-CommonContents + + CommonSL-PRS-MethodsIEsRequestCapabilities, + CommonSL-PRS-MethodsIEsProvideCapabilities, + CommonSL-PRS-MethodsIEsRequestAssistanceData, + CommonSL-PRS-MethodsIEsProvideAssistanceData, + CommonSL-PRS-MethodsIEsRequestLocationInformation, + CommonSL-PRS-MethodsIEsProvideLocationInformation + +FROM + SLPP-PDU-CommonSL-PRS-MethodsContents + + SL-AOA-RequestCapabilities, + SL-AOA-ProvideCapabilities, + SL-AOA-RequestAssistanceData, + SL-AOA-ProvideAssistanceData, + SL-AOA-RequestLocationInformation, + SL-AOA-ProvideLocationInformation + +FROM + SLPP-PDU-SL-AOA-Contents + + SL-RTT-RequestCapabilities, + SL-RTT-ProvideCapabilities, + SL-RTT-RequestAssistanceData, + SL-RTT-ProvideAssistanceData, + SL-RTT-RequestLocationInformation, + SL-RTT-ProvideLocationInformation + +FROM + SLPP-PDU-SL-RTT-Contents + + SL-TDOA-RequestCapabilities, + SL-TDOA-ProvideCapabilities, + SL-TDOA-RequestAssistanceData, + SL-TDOA-ProvideAssistanceData, + SL-TDOA-RequestLocationInformation, + SL-TDOA-ProvideLocationInformation + +FROM + SLPP-PDU-SL-TDOA-Contents + + SL-TOA-RequestCapabilities, +``` + +``` + +SL-TOA-ProvideCapabilities, +SL-TOA-RequestAssistanceData, +SL-TOA-ProvideAssistanceData, +SL-TOA-RequestLocationInformation, +SL-TOA-ProvideLocationInformation + +FROM + SLPP-PDU-SL-TOA-Contents; + +-- TAG-SLPP-PDU-DEFINITIONS-STOP +-- ASN1STOP + +``` + +NOTE 1: An implementation needs to include only the supported "Method" PDUs. Not supported methods do not need to be included. For example, if SL-RTT is not supported by an implementation, the *SLPP-PDU-SL-RTT-Contents* PDU does not need to be included in the protocol. + +NOTE 2: An implementation supporting SL-RTT, SL-AoA, SL-TDOA, or SL-TOA must also support the *SLPP-PDU-CommonSL-PRS-MethodsContents* PDU. + +#### – **SLPP-Message** + +The *SLPP-Message* provides the complete set of information for an invocation or response pertaining to an SLPP transaction. + +``` + +-- ASN1START +-- TAG-SLPP-MESSAGE-START + +SLPP-Message ::= SEQUENCE { + transactionID INTEGER (0..255) OPTIONAL, + endTransaction BOOLEAN, + sequenceNumber SequenceNumber OPTIONAL, + sessionID SessionID OPTIONAL, + acknowledgement Acknowledgement OPTIONAL, + slpp-MessageBody SLPP-MessageBody OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +SequenceNumber ::= INTEGER (0..255) +SessionID ::= OCTET STRING (SIZE (6)) + +Acknowledgement ::= SEQUENCE { + ackRequested BOOLEAN, + ackIndicator SequenceNumber OPTIONAL +} + +-- TAG-SLPP-MESSAGE-STOP +-- ASN1STOP + +``` + +| SLPP-Message field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| acknowledgement
This field is included in an SLPP acknowledgement and in any SLPP message requesting an acknowledgement when SLPP operates over the control plane and is omitted otherwise.
  • - ackRequested: This field indicates whether an SLPP acknowledgement is requested (TRUE) or not (FALSE). A value of TRUE may only be included when an slpp-MessageBody is included.
  • - ackIndicator: This field indicates the sequence number of the message being acknowledged.
| +| endTransaction
This field indicates whether an SLPP message is the last message carrying an slpp-MessageBody in a transaction (TRUE) or not last (FALSE). | +| sequenceNumber
This field may be included when SLPP operates over the control plane and an slpp-MessageBody is included but shall be omitted otherwise. | +| sessionID
This field indicates the session ID which is used to identify messages belonging to the same session. | +| slpp-MessageBody
This field may be omitted in the case the message is sent only to acknowledge a previously received message. | +| transactionID
This field is omitted if an slpp-MessageBody is not present (i.e. in an SLPP message sent only to acknowledge a previously received message) or if it is not available to the transmitting entity (e.g., in an SLPP-Error message triggered by a message that could not be parsed). If present, this field shall be ignored at a receiver in an SLPP message for which the slpp-MessageBody is not present. | + +#### SLPP-MessageBody + +The *SLPP-MessageBody* identifies the type of an SLPP message and contains all SLPP information specifically associated with that type. + +``` +-- ASN1START +-- TAG-SLPP-MESSAGEBODY-START + +SLPP-MessageBody ::= CHOICE { + c1 CHOICE { + requestCapabilities RequestCapabilities, + provideCapabilities ProvideCapabilities, + requestAssistanceData RequestAssistanceData, + provideAssistanceData ProvideAssistanceData, + requestLocationInformation RequestLocationInformation, + provideLocationInformation ProvideLocationInformation, + abort Abort, + error Error, + spare8 NULL, spare7 NULL, spare6 NULL, spare5 NULL, spare4 NULL, spare3 NULL, spare2 NULL, spare1 NULL + }, + messageClassExtension SEQUENCE {} +} + +-- TAG-SLPP-MESSAGEBODY-STOP +-- ASN1STOP +``` + +### 6.2.2 Message definitions + +#### – *RequestCapabilities* + +``` +-- ASN1START +-- TAG-REQUESTCAPABILITIES-START + +RequestCapabilities ::= SEQUENCE { + criticalExtensions CHOICE { + requestCapabilities RequestCapabilities-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +RequestCapabilities-IEs ::= SEQUENCE { + commonIEsRequestCapabilities OCTET STRING OPTIONAL, -- Containing CommonIEsRequestCapabilities + commonSL-PRS-MethodsIEsRequestCapabilities OCTET STRING OPTIONAL, -- Containing CommonSL-PRS-MethodsIEsRequestCapabilities + sl-AoA-RequestCapabilities OCTET STRING OPTIONAL, -- Containing SL-AoA-RequestCapabilities + sl-RTT-RequestCapabilities OCTET STRING OPTIONAL, -- Containing SL-RTT-RequestCapabilities + sl-TDOA-RequestCapabilities OCTET STRING OPTIONAL, -- Containing SL-TDOA-RequestCapabilities + sl-TOA-RequestCapabilities OCTET STRING OPTIONAL, -- Containing SL-TOA-RequestCapabilities + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +-- TAG-REQUESTCAPABILITIES-STOP +-- ASN1STOP +``` + +#### – *ProvideCapabilities* + +``` +-- ASN1START +-- TAG-PROVIDECAPABILITIES-START + +ProvideCapabilities ::= SEQUENCE { + criticalExtensions CHOICE { + provideCapabilities ProvideCapabilities-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +ProvideCapabilities-IEs ::= SEQUENCE { + commonIEsProvideCapabilities OCTET STRING OPTIONAL, -- Containing CommonIEsProvideCapabilities + commonSL-PRS-MethodsIEsProvideCapabilities OCTET STRING OPTIONAL, -- Containing CommonSL-PRS-MethodsIEsProvideCapabilities + sl-AoA-ProvideCapabilities OCTET STRING OPTIONAL, -- Containing SL-AoA-ProvideCapabilities + sl-RTT-ProvideCapabilities OCTET STRING OPTIONAL, -- Containing SL-RTT-ProvideCapabilities + sl-TDOA-ProvideCapabilities OCTET STRING OPTIONAL, -- Containing SL-TDOA-ProvideCapabilities + sl-TOA-ProvideCapabilities OCTET STRING OPTIONAL, -- Containing SL-TOA-ProvideCapabilities +} +``` + +``` + +lateNonCriticalExtension OCTET STRING OPTIONAL, +nonCriticalExtension SEQUENCE {} OPTIONAL +} + +-- TAG-PROVIDECAPABILITIES-STOP +-- ASN1STOP + +``` + +#### – *RequestAssistanceData* + +``` + +-- ASN1START +-- TAG-REQUESTASSISTANCEDATA-START + +RequestAssistanceData ::= SEQUENCE { + criticalExtensions CHOICE { + requestAssistanceData RequestAssistanceData-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +RequestAssistanceData-IEs ::= SEQUENCE { + commonIEsRequestAssistanceData OCTET STRING OPTIONAL, -- Containing CommonIEsRequestAssistanceData + commonSL-PRS-MethodsIEsRequestAssistanceData OCTET STRING OPTIONAL, -- Containing CommonSL-PRS-MethodsIEsRequestAssistanceData + sl-AOA-RequestAssistanceData OCTET STRING OPTIONAL, -- Containing SL-AOA-RequestAssistanceData + sl-RTT-RequestAssistanceData OCTET STRING OPTIONAL, -- Containing SL-RTT-RequestAssistanceData + sl-TDOA-RequestAssistanceData OCTET STRING OPTIONAL, -- Containing SL-TDOA-RequestAssistanceData + sl-TOA-RequestAssistanceData OCTET STRING OPTIONAL, -- Containing SL-TOA-RequestAssistanceData + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +-- TAG-REQUESTASSISTANCEDATA-STOP +-- ASN1STOP + +``` + +#### – *ProvideAssistanceData* + +``` + +-- ASN1START +-- TAG-PROVIDEASSISTANCEDATA-START + +ProvideAssistanceData ::= SEQUENCE { + criticalExtensions CHOICE { + provideAssistanceData ProvideAssistanceData-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +ProvideAssistanceData-IEs ::= SEQUENCE { + commonIEsProvideAssistanceData OCTET STRING OPTIONAL, -- Containing CommonIEsProvideAssistanceData +} + +``` + +``` + +commonSL-PRS-MethodsIEsProvideAssistanceData OCTET STRING OPTIONAL, -- Containing CommonSL-PRS-MethodsIEsProvideAssistanceData +sl-AOA-ProvideAssistanceData OCTET STRING OPTIONAL, -- Containing SL-AOA-ProvideAssistanceData +sl-RTT-ProvideAssistanceData OCTET STRING OPTIONAL, -- Containing SL-RTT-ProvideAssistanceData +sl-TDOA-ProvideAssistanceData OCTET STRING OPTIONAL, -- Containing SL-TDOA-ProvideAssistanceData +sl-TOA-ProvideAssistanceData OCTET STRING OPTIONAL, -- Containing SL-TOA-ProvideAssistanceData +lateNonCriticalExtension OCTET STRING OPTIONAL, +nonCriticalExtension SEQUENCE {} OPTIONAL +} + +-- TAG-PROVIDEASSISTANCEDATA-STOP +-- ASN1STOP + +``` + +#### RequestLocationInformation + +``` + +-- ASN1START +-- TAG-REQUESTLOCATIONINFORMATION-START + +RequestLocationInformation ::= SEQUENCE { + criticalExtensions CHOICE { + requestLocationInformation RequestLocationInformation-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +RequestLocationInformation-IEs ::= SEQUENCE { + commonIEsRequestLocationInformation OCTET STRING OPTIONAL, -- Containing CommonIEsRequestLocationInformation + commonSL-PRS-MethodsIEsRequestLocationInformation OCTET STRING OPTIONAL, -- Containing CommonSL-PRS-MethodsIEsRequestLocationInformation + sl-AOA-RequestLocationInformation OCTET STRING OPTIONAL, -- Containing SL-AOA-RequestLocationInformation + sl-RTT-RequestLocationInformation OCTET STRING OPTIONAL, -- Containing SL-RTT-RequestLocationInformation + sl-TDOA-RequestLocationInformation OCTET STRING OPTIONAL, -- Containing SL-TDOA-RequestLocationInformation + sl-TOA-RequestLocationInformation OCTET STRING OPTIONAL, -- Containing SL-TOA-RequestLocationInformation + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +-- TAG-REQUESTLOCATIONINFORMATION-STOP +-- ASN1STOP + +``` + +#### ProvideLocationInformation + +``` + +-- ASN1START +-- TAG-PROVIDELOCATIONINFORMATION-START + +ProvideLocationInformation ::= SEQUENCE { + criticalExtensions CHOICE { + provideLocationInformation ProvideLocationInformation-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +``` + +``` + +} + +ProvideLocationInformation-IEs ::= SEQUENCE { + commonIEsProvideLocationInformation OCTET STRING OPTIONAL, -- Containing CommonIEsProvideLocationInformation + commonSL-PRS-MethodsIEsProvideLocationInformation OCTET STRING OPTIONAL, -- Containing CommonSL-PRS-MethodsIEsProvideLocationInformation + sl-AOA-ProvideLocationInformation OCTET STRING OPTIONAL, -- Containing SL-AOA-ProvideLocationInformation + sl-RTT-ProvideLocationInformation OCTET STRING OPTIONAL, -- Containing SL-RTT-ProvideLocationInformation + sl-TDOA-ProvideLocationInformation OCTET STRING OPTIONAL, -- Containing SL-TDOA-ProvideLocationInformation + sl-TOA-ProvideLocationInformation OCTET STRING OPTIONAL, -- Containing SL-TOA-ProvideLocationInformation + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +-- TAG-PROVIDELOCATIONINFORMATION-STOP +-- ASN1STOP + +``` + +#### — Abort + +``` + +-- ASN1START +-- TAG-ABORT-START + +Abort ::= SEQUENCE { + criticalExtensions CHOICE { + abort Abort-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +Abort-IEs ::= SEQUENCE { + commonIEsAbort CommonIEsAbort OPTIONAL, + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} + +-- TAG-ABORT-STOP +-- ASN1STOP + +``` + +#### — Error + +``` + +-- ASN1START +-- TAG-ERROR-START + +Error ::= CHOICE { + criticalExtensions CHOICE { + error Error-IEs, + criticalExtensionsFuture SEQUENCE {} + } +} + +``` + +``` +Error-IEs ::= SEQUENCE { + commonIEsError CommonIEsError OPTIONAL, + lateNonCriticalExtension OCTET STRING OPTIONAL, + nonCriticalExtension SEQUENCE {} OPTIONAL +} +-- TAG-ERROR-STOP +-- ASN1STOP +``` + +## 6.3 SLPP information elements + +### 6.3.1 Common information elements + +#### – *ARFCN-ValueNR* + +The *ARFCN-ValueNR* is used to indicate the ARFCN applicable for a downlink, uplink or bi-directional (TDD) NR global frequency raster, as defined in TS 38.101-2 [10] and TS 38.101-1 [11]. + +``` +-- ASN1START +-- TAG-ARFCN-VALUENR-START +ARFCN-ValueNR ::= INTEGER (0..3279165) +-- TAG-ARFCN-VALUENR-STOP +-- ASN1STOP +``` + +#### – *CommonIEsAbort* + +The *CommonIEsAbort* carries common IEs for an Abort SLPP message Type. + +``` +-- ASN1START +-- TAG-COMMONIESABORT-START +CommonIEsAbort ::= SEQUENCE { + abortCause ENUMERATED { undefined, stopPeriodicReporting } +} +-- TAG-COMMONIESABORT-STOP +-- ASN1STOP +``` + +| CommonEsAbort field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

abortCause

This IE defines the request to abort an ongoing procedure. The abort cause 'stopPeriodicReporting' should be used by a endpoint to stop any ongoing location reporting configured as periodicalReporting in the CommonEsRequestLocationInformation.

| + +#### — **CommonEsError** + +The *CommonEsError* carries common IEs for an Error SLPP message Type. + +``` +-- ASN1START +-- TAG-COMMONIESERROR-START + +CommonEsError ::= SEQUENCE { + errorCause ENUMERATED { undefined, slppMessageHeaderError, slppMessageBodyError, incorrectDataValue } +} + +-- TAG-COMMONIESERROR-STOP +-- ASN1STOP +``` + +| CommonEsError field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

errorCause

This IE defines the cause for an error. 'slppMessageHeaderError' and 'slppMessageBodyError' is used if a receiver is able to detect a coding error in the SLPP header (i.e., in the common fields) or SLPP message body respectively. 'incorrectDataValue' is used if a receiver receives an incorrect data value.

| + +#### — **FreqBandIndicatorNR** + +The IE *FreqBandIndicatorNR* specifies the NR band indicator (TS 38.331 [2]). + +``` +-- ASN1START +-- TAG-FREQBANDINDICATORNR-START + +FreqBandIndicatorNR ::= INTEGER (1..1024) + +-- TAG-FREQBANDINDICATORNR-STOP +-- ASN1STOP +``` + +#### — **GNSS-ID** + +The *GNSS-ID* is used to indicate a specific GNSS. + +``` +-- ASN1START +-- TAG-GNSS-ID-START +``` + +``` +GNSS-ID ::= ENUMERATED{ gps, sbas, qzss, galileo, glonass, bds, navic } + +-- TAG-GNSS-ID-STOP +-- ASN1STOP +``` + +#### – *LCS-GCS-Translation* + +The IE *LCS-GCS-Translation* provides the angles $\alpha$ (bearing angle), $\beta$ (downtilt angle) and $\gamma$ (slant angle) for the translation of a Local Coordinate System (LCS) to a Global Coordinate System (GCS) as defined in TR 38.901 [8]. + +``` +-- ASN1START +-- TAG-LCS-GCS-TRANSLATION-START + +LCS-GCS-Translation ::= SEQUENCE { + alpha INTEGER (0..3599), + beta INTEGER (0..3599), + gamma INTEGER (0..3599), + ... +} + +-- TAG-LCS-GCS-TRANSLATION-STOP +-- ASN1STOP +``` + +##### *LCS-GCS-Translation* field descriptions + +| | | +|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| alpha | This field specifies the bearing angle $\alpha$ for the translation of the LCS to a GCS as defined in TR 38.901 [8]. Scale factor 0.1 degree; range 0 to 359 degrees. | +| beta | This field specifies the downtilt angle $\beta$ for the translation of the LCS to a GCS as defined in TR 38.901 [8]. Scale factor 0.1 degrees; range 0 to 359 degrees. | +| gamma | This field specifies the slant angle $\gamma$ for the translation of the LCS to a GCS as defined in TR 38.901 [8]. Scale factor 0.1 degree; range 0 to 359 degrees. | + +#### – *LOS-NLOS-Indicator* + +The IE *LOS-NLOS-Indicator* provides information on the likelihood of a Line-of-Sight (LOS) propagation path from the source to the receiver. + +``` +-- ASN1START +-- TAG-LOS-NLOS-INDICATOR-START + +LOS-NLOS-Indicator ::= SEQUENCE { + indicator CHOICE { + soft INTEGER (0..10), + hard BOOLEAN + } +} +``` + +``` +-- TAG-LOS-NLOS-INDICATOR-STOP +-- ASN1STOP +``` + +##### LOS-NLOS-Indicator field descriptions + +##### *indicator* + +This field provides information on the likelihood of a Line-of-Sight propagation path from the source to the receiver with a value of 1 corresponding to LoS and a value of 0 corresponding to NLoS. + +- **soft**: Integer value '0' indicates likelihood 0, integer value '10' indicates likelihood 1. Scale factor 0.1; range 0 to 1. +- **hard**: FALSE indicates likelihood '0', TRUE indicates likelihood '1'. + +#### — *NCGI* + +The *NCGI* specifies the NR Cell Global Identifier (NCGI) which is used to identify NR cells globally (TS 38.331 [2]). + +``` +-- ASN1START +-- TAG-NCGI-START + +NCGI ::= SEQUENCE { + mcc SEQUENCE (SIZE (3)) OF INTEGER (0..9), + mnc SEQUENCE (SIZE (2..3)) OF INTEGER (0..9), + nr-CellIdentity BIT STRING (SIZE (36)) +} + +-- TAG-NCGI-STOP +-- ASN1STOP +``` + +#### — *NR-PhysCellID* + +The *NR-PhysCellID* specifies the NR physical cell identifier (TS 38.331 [2]). + +``` +-- ASN1START +-- TAG-NR-PHYSCELLID-START + +NR-PhysCellID ::= INTEGER (0..1007) + +-- TAG-NR-PHYSCELLID-STOP +-- ASN1STOP +``` + +#### — *PositioningModes* + +The IE *PositioningModes* is used to indicate several positioning modes using a bit map. + +``` + +-- ASN1START +-- TAG-POSITIONINGMODES-START + +PositioningModes ::= SEQUENCE { + posModes BIT STRING { ue-based (0), ue-assisted (1) } (SIZE (1..8)), + ... +} + +-- TAG-POSITIONINGMODES-STOP +-- ASN1STOP + +``` + +##### PositioningModes field descriptions + +##### *posModes* + +This field specifies the positioning mode(s). This is represented by a bit string, with a one value at the bit position means the particular positioning mode is addressed; a zero value means not addressed. + +##### SL-RTD-Info + +The IE *SL-RTD-Info* provides time synchronization information of anchor UEs between a UE and LMF or another UE. + +``` + +-- ASN1START +-- TAG-SL-RTD-INFO-START + +SL-RTD-Info ::= SEQUENCE { + referenceRTD-Info ReferenceRTD-Info, + rtd-InfoList RTD-InfoList +} + +ReferenceRTD-Info ::= SEQUENCE { + syncSourceType ENUMERATED { gnss, gNB-eNB, ue}, + applicationLayerID OCTET STRING OPTIONAL, + nrCell-Identify SEQUENCE { + nr-PhysCellID NR-PhysCellID, + nr-ARFCN ARFCN-ValueNR, + nr-CellGlobalID NCGI OPTIONAL + } OPTIONAL +} + +RTD-InfoList ::= SEQUENCE (SIZE (1.. maxNrOfSLTxUEs)) OF RTD-InfoListPerTxUE + +RTD-InfoListPerTxUE ::= SEQUENCE { + applicationLayerID OCTET STRING, + rtdBetweenAnchorUEs CHOICE { + subframeOffset INTEGER (0..1966079), + sl-OffsetDFN INTEGER (0..1000) + }, + rtd-Quality SL-TimingQuality +} + +``` + +``` + +} +-- TAG-SL-RTD-INFO-STOP +-- ASN1STOP + +``` + +| SL-RTD-Info field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| nrCell-Identify
This field provides NR cell identity information. The field is present only if the synchronization source of an anchor UE is gNB/eNB. | +| referenceRTD-Info
This field defines the reference RTD and comprises the following sub-fields:
  • - syncSourceType: This field specifies the synchronization source type.
  • - applicationLayerID: This field provides the application layer ID of the reference UE if the syncSourceType is set to UE.
| +| rtdBetweenAnchorUEs
This field specifies the RTD between anchor UEs: | +| rtd-Quality
This field specifies the quality of the RTD. | + +#### – ***SL-TimeStamp*** + +The IE *SL-TimeStamp* defines the UE measurement associated time stamp. + +``` + +-- ASN1START +-- TAG-SL-TIMESTAMP-START + +SL-TimeStamp ::= SEQUENCE { + dfn-Time SEQUENCE { + syncSourceType ENUMERATED { gnss, ue} OPTIONAL, + applicationLayerID OCTET STRING OPTIONAL, + dfn INTEGER (0.. 1023), + nr-Slot CHOICE { + scs15 INTEGER (0..9), + scs30 INTEGER (0..19), + scs60 INTEGER (0..39), + scs120 INTEGER (0..79) + } + } OPTIONAL, + sfn-Time SEQUENCE { + nr-PhysCellID NR-PhysCellID OPTIONAL, + nr-ARFCN ARFCN-ValueNR OPTIONAL, + nr-CellGlobalID NCGI OPTIONAL, + nr-SFN INTEGER (0..1023), + nr-Slot CHOICE { + scs15 INTEGER (0..9), + scs30 INTEGER (0..19), + scs60 INTEGER (0..39), + scs120 INTEGER (0..79) + } + } OPTIONAL +} + +``` + +``` + +} +-- TAG-SL-TIMESTAMP-STOP +-- ASN1STOP + +``` + +| SL-TimingQuality field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| dfn-Time
This field provides the DFN based time stamp. | +| sfn-Time
This field provides the SFN based time stamp. If this field is present, at least one of nr-PhysCellID , nr-ARFCN , or nr-CellGlobalID shall be present. | + +#### – ***SL-TimingQuality*** + +The IE *SL-TimingQuality* defines the quality of a timing value (e.g., of a TOA measurement). + +``` + +-- ASN1START +-- TAG-SL-TIMINGQUALITY-START + +SL-TimingQuality ::= SEQUENCE { + timingQualityValue INTEGER (0..31), + timingQualityResolution ENUMERATED {mdot1, m1, m10, m30} +} + +-- TAG-SL-TIMINGQUALITY-STOP +-- ASN1STOP + +``` + +| SL-TimingQuality field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| timingQualityValue
This field provides an estimate of uncertainty of the timing value for which the IE SL-TimingQuality is provided in units of metres. | +| timingQualityResolution
field provides the resolution used in the timingQualityValue field. Enumerated values mdot1 , m1 , m10 , m30 correspond to 0.1, 1, 10, 30 metres, respectively. | + +### 6.3.2 UE capability information elements + +### 6.3.3 Positioning Method information elements + +## 6.4 Multiplicity and type constraint values + +– *Multiplicity and type constraint definitions* + +``` +-- ASN1START +-- TAG-MULTIPLICITY-AND-TYPE-CONSTRAINT-DEFINITIONS-START + +maxNrOfSLTxUEs INTEGER ::= 256 -- Max Tx UEs per Rx UE, FFS on the value +nrMaxBands INTEGER ::= 1024 -- Maximum number of supported bands in UE capability + +-- TAG-MULTIPLICITY-AND-TYPE-CONSTRAINT-DEFINITIONS-STOP +-- ASN1STOP +``` + +– *End of SLPP-PDU-Definitions* + +``` +-- ASN1START + +END + +-- ASN1STOP +``` + +## 6.5 SLPP PDU Common Contents + +– *SLPP-PDU-CommonContents* + +This ASN.1 segment is the start of the SLPP PDU Common Contents definitions. + +``` +-- ASN1START +-- TAG-SLPP-PDU-COMMONCONTENTS-START + +SLPP-PDU-Common-Contents DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN +IMPORTS + ARFCN-ValueNR, + GNSS-ID, +``` + +``` + NCGI, + NR-PhysCellID +FROM + SLPP-PDU-Definitions; + +-- TAG-SLPP-PDU-COMMON-CONTENTS-STOP +-- ASN1STOP +``` + +### — *CommonIEsRequestCapabilities* + +``` +-- ASN1START +-- TAG-COMMONIESREQUESTCAPABILITIES-START + +CommonIEsRequestCapabilities ::= SEQUENCE { + +} + +-- TAG-COMMONIESREQUESTCAPABILITIES-STOP +-- ASN1STOP +``` + +### — *CommonIEsProvideCapabilities* + +``` +-- ASN1START +-- TAG-COMMONIESPROVIDECAPABILITIES-START + +CommonIEsProvideCapabilities ::= SEQUENCE { + +} +-- TAG-COMMONIESPROVIDECAPABILITIES-STOP +-- ASN1STOP +``` + +### — *CommonIEsRequestAssistanceData* + +``` +-- ASN1START +-- TAG-COMMONIESREQUESTASSISTANCEDATA-START + +CommonIEsRequestAssistanceData ::= SEQUENCE { + +} +-- TAG-COMMONIESREQUESTASSISTANCEDATA-STOP +-- ASN1STOP +``` + +### CommonEsProvideAssistanceData + +``` +-- ASN1START +-- TAG-COMMONIESPROVIDEASSISTANCEDATA-START + +CommonEsProvideAssistanceData ::= SEQUENCE { +} + +-- TAG-COMMONIESPROVIDEASSISTANCEDATA-STOP +-- ASN1STOP +``` + +#### CommonEsRequestLocationInformation + +The *CommonEsRequestLocationInformation* carries common IEs for a Request Location Information SLPP message Type. + +``` +-- ASN1START +-- TAG-COMMONIESREQUESTLOCATIONINFORMATION-START + +CommonEsRequestLocationInformation ::= SEQUENCE { + locationInformationType LocationInformationType, + periodicalReporting PeriodicalReportingCriteria OPTIONAL, + additionalInformation AdditionalInformation OPTIONAL, + qos QoS OPTIONAL, + environment Environment OPTIONAL, + scheduledLocationTime ScheduledLocationTime OPTIONAL, + ... +} + +LocationInformationType ::= ENUMERATED { locationEstimateRequired, locationMeasurementsRequired, locationEstimatePreferred, + locationMeasurementsPreferred, rangeEstimateRequired, rangeMeasurementsRequired, + rangeEstimatePreferred, rangeMeasurementsPreferred, directionEstimateRequired, + directionMeasurementsRequired, directionEstimatePreferred, directionMeasurementsPreferred, + rangeDirectionEstimateRequired, rangeDirectionMeasurementsRequired, + rangeDirectionEstimatePreferred, rangeDirectionMeasurementsPreferred } + +PeriodicalReportingCriteria ::= SEQUENCE { + reportingAmount ENUMERATED { ra2, ra4, ra8, ra16, ra32, ra64, ra-Infinity }, + reportingInterval ENUMERATED { ri1, ri2, ri4, ri8, ri10, ri16, ri20, ri32, ri64 } +} + +AdditionalInformation ::= ENUMERATED { onlyReturnInformationRequested, mayReturnAdditionalInformation } + +QoS ::= SEQUENCE { + horizontalAccuracy HorizontalAccuracy OPTIONAL, + verticalCoordinateRequest BOOLEAN, + verticalAccuracy VerticalAccuracy OPTIONAL, + rangeAccuracy RangeAccuracy OPTIONAL, +} +``` + +``` + + azimuthAccuracy AzimuthAccuracy OPTIONAL, + elevationAccuracy ElevationAccuracy OPTIONAL, + responseTime ResponseTime OPTIONAL, + velocityRequest BOOLEAN, + ... +} + +HorizontalAccuracy ::= SEQUENCE { + accuracy INTEGER(0..255), + confidence INTEGER(0..100), + ... +} + +VerticalAccuracy ::= SEQUENCE { + accuracy INTEGER(0..255), + confidence INTEGER(0..100), + ... +} + +RangeAccuracy ::= SEQUENCE { + accuracy INTEGER(0..127), + confidence INTEGER(0..100), + ... +} + +AzimuthAccuracy ::= SEQUENCE { + accuracy INTEGER(0..127), + confidence INTEGER(0..100), + ... +} + +ElevationAccuracy ::= SEQUENCE { + accuracy INTEGER(0..127), + confidence INTEGER(0..100), + ... +} + +ResponseTime ::= SEQUENCE { + time INTEGER (1..128), + tenMilliSeconds ENUMERATED { true} OPTIONAL, + ... +} + +Environment ::= ENUMERATED { badArea, notBadArea, mixedArea} + +ScheduledLocationTime ::= SEQUENCE { + utc-Time UTCTime OPTIONAL, + gnss-Time SEQUENCE { + gnss-TOD-Msec INTEGER (0..3599999), + gnss-TimeID GNSS-ID + } + nr-Time SEQUENCE { + nr-PhysCellID NR-PhysCellID, + nr-ARFCN ARFCN-ValueNR, + } +} + +``` + +``` + nr-CellGlobalID NCGI OPTIONAL, + nr-SFN INTEGER (0..1023), + nr-Slot CHOICE { + scs15 INTEGER (0..9), + scs30 INTEGER (0..19), + scs60 INTEGER (0..39), + scs120 INTEGER (0..79) + } OPTIONAL +} +relativeTime INTEGER (1..1024) OPTIONAL, + OPTIONAL +} + +-- TAG-COMMONIESREQUESTLOCATIONINFORMATION-STOP +-- ASN1STOP +``` + +| CommonEsRequestLocationInformation field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

additionalInformation

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

| +|

environment

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

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

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

| +|

locationInformationType

This IE indicates whether the server requires a location estimate or measurements. For 'locationEstimateRequired' or 'rangeEstimateRequired', the UE shall return a location or range estimate if possible, or indicate a location error if not possible. For 'locationMeasurementsRequired' or 'rangeMeasurementsRequired', the UE shall return measurements if possible, or indicate a location error if not possible. For 'locationEstimatePreferred' or 'rangeEstimatePreferred', the UE shall return a location or range estimate if possible, but may also or instead return measurements for any requested position methods for which a location estimate is not possible. For 'locationMeasurementsPreferred' or 'rangeMeasurementsPreferred', the UE shall return location or range measurements if possible, but may also or instead return a location estimate for any requested position methods for which return of location measurements is not possible.

| +|

periodicalReporting

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

  • - reportingAmount indicates the number of periodic location information reports requested. Enumerated values correspond to 2, 4, 8, 16, 32, 64, or infinite/indefinite number of reports. If the reportingAmount is 'infinite/indefinite', the UE should continue periodic reporting until an SLPP Abort message is received.
  • - reportingInterval indicates the interval between location information reports and the response time requirement for the first location information report. Enumerated values correspond to reporting intervals of 1, 2, 4, 8, 10, 16, 20, 32, and 64 seconds, respectively. Measurement reports containing no measurements or no location estimate are required when a reportingInterval expires before a UE is able to obtain new measurements or obtain a new location estimate.
| + +##### **qos** + +This IE indicates the quality of service and comprises a number of sub-fields. In the case of measurements, some of the sub-fields apply to the location estimate that could be obtained by the server from the measurements provided by the UE assuming that the measurements are the only sources of error. Fields are as follows: + +- **horizontalAccuracy** indicates the maximum horizontal error in the location estimate at an indicated confidence level. The 'accuracy' corresponds to the encoded uncertainty as defined in TS 23.032 [7] and 'confidence' corresponds to confidence as defined in TS 23.032 [7]. +- **verticalCoordinateRequest** indicates whether a vertical coordinate is required (TRUE) or not (FALSE) +- **verticalAccuracy** indicates the maximum vertical error in the location estimate at an indicated confidence level and is only applicable when a vertical coordinate is requested. The 'accuracy' corresponds to the encoded uncertainty altitude as defined in TS 23.032 [7] and 'confidence' corresponds to confidence as defined in TS 23.032 [7]. +- **responseTime** + - **time** indicates the maximum response time as measured between receipt of the *RequestLocationInformation* and transmission of a *ProvideLocationInformation*. If the *unit* field is absent, this is given as an integer number of seconds between 1 and 128. If the *unit* field is present with enumerated value 'ten-seconds', the maximum response time is given in units of 10-seconds, between 10 and 1280 seconds. If the *unit* field is present with enumerated value 'ten-milli-seconds', the maximum response time is given in units of 10-milli-seconds, between 0.01 and 1.28 seconds. If the *periodicalReporting* IE is included in *CommonEsRequestLocationInformation*, this field should not be included by the location server and shall be ignored by the UE (if included). + - **tenMilliSeconds** indicates the unit of the *time* field corresponds to a resolution of 0.01 seconds. If this field is absent, the unit/resolution is 1 second. + - **velocityRequest** indicates whether velocity (or measurements related to velocity) is requested (TRUE) or not (FALSE). + +All QoS requirements shall be obtained by the UE to the degree possible but it is permitted to return a response that does not fulfill all QoS requirements if some were not attainable. + +##### **scheduledLocationTime** + +This field indicates that the UE is requested to obtain location measurements or location estimate valid at the *scheduledLocationTime* *T* and comprises the following subfields: + +- **utc-Time** provides *T* in UTC in the form of YYMMDDhhmmssZ. +- **gnss-Time** provides *T* in GNSS system time of the GNSS indicated by *gnss-TimeID*. +- **gnss-TOD-msec** specifies the GNSS TOD in 1-milli-second resolution rounded down to the nearest millisecond unit. +- **nr-Time** provides *T* in NR network time. + - **nr-PhysCellID**, **nr-ARFCN**, **nr-CellGlobalID** identifies the reference cell (NR) that is used for the network time. + - **nr-SFN** specifies the system frame number in NR. + - **nr-Slot** specifies the slot number in NR for the indicated subcarrier spacing (SCS). The total NR network time is given by *nr-SFN* + *nr-Slot*. +- **relativeTime** provides *T* in seconds from current time, where current time is defined as the time the *CommonEsRequestLocationInformation* was received. + +NOTE 1: A location estimate returned to an LCS Client, AF or UE for a scheduled location time can be treated by the LCS Client, AF or UE as an estimate of the location of the UE at the scheduled location time (see TS 23.273 [5]). + +NOTE 2: If this field is present, at least one of *utc-Time*, *gnss-Time*, *nr-Time*, or *relativeTime* shall be present. + +### CommonEsProvideLocationInformation + +The *CommonEsProvideLocationInformation* carries common IEs for a Provide Location Information SLPP message Type. + +``` +-- ASN1START +-- TAG-COMMONIESPROVIDELOCATIONINFORMATION-START + +CommonEsProvideLocationInformation ::= SEQUENCE { + locationEstimate LocationCoordinates OPTIONAL, -- [locationTargetUe-sl-pos] + rangeAndOrDirection RangeAndOrDirection OPTIONAL, + velocityEstimate Velocity OPTIONAL, +``` + +``` + +locationError LocationError OPTIONAL, +... +} +LocationCoordinates ::= CHOICE { + ellipsoidPoint Ellipsoid-Point, + ellipsoidPointWithUncertaintyCircle Ellipsoid-PointWithUncertaintyCircle, + ellipsoidPointWithUncertaintyEllipse Ellipsoid-PointWithUncertaintyEllipse, + polygon Polygon, + ellipsoidPointWithAltitude Ellipsoid-PointWithAltitude, + ellipsoidPointWithAltitudeAndUncertaintyEllipsoid Ellipsoid-PointWithAltitudeAndUncertaintyEllipsoid, + ellipsoidArc EllipsoidArc, + ... +} + +Velocity ::= CHOICE { + horizontalVelocity HorizontalVelocity, + horizontalWithVerticalVelocity HorizontalWithVerticalVelocity, + horizontalVelocityWithUncertainty HorizontalVelocityWithUncertainty, + horizontalWithVerticalVelocityAndUncertainty HorizontalWithVerticalVelocityAndUncertainty, + ... +} + +LocationError ::= SEQUENCE { + locationFailureCause LocationFailureCause, + ... +} + +LocationFailureCause ::= ENUMERATED { undefined, requestedMethodNotSupported, positionMethodFailure, periodicLocationMeasurementsNotAvailable} + +Ellipsoid-Point ::= SEQUENCE { + latitudeSign ENUMERATED {north, south}, + degreesLatitude INTEGER (0..8388607), -- 23 bit field + degreesLongitude INTEGER (-8388608..8388607) -- 24 bit field +} + +Ellipsoid-PointWithUncertaintyCircle ::= SEQUENCE { + latitudeSign ENUMERATED {north, south}, + degreesLatitude INTEGER (0..8388607), -- 23 bit field + degreesLongitude INTEGER (-8388608..8388607), -- 24 bit field + uncertainty INTEGER (0..127) +} + +Ellipsoid-PointWithUncertaintyEllipse ::= SEQUENCE { + latitudeSign ENUMERATED {north, south}, + degreesLatitude INTEGER (0..8388607), -- 23 bit field + degreesLongitude INTEGER (-8388608..8388607), -- 24 bit field + uncertaintySemiMajor INTEGER (0..127), + uncertaintySemiMinor INTEGER (0..127), + orientationMajorAxis INTEGER (0..179), + confidence INTEGER (0..100) +} + +``` + +``` + +EllipsoidPointWithAltitude ::= SEQUENCE { + latitudeSign ENUMERATED {north, south}, + degreesLatitude INTEGER (0..8388607), -- 23 bit field + degreesLongitude INTEGER (-8388608..8388607), -- 24 bit field + altitudeDirection ENUMERATED {height, depth}, + altitude INTEGER (0..32767) -- 15 bit field +} + +EllipsoidPointWithAltitudeAndUncertaintyEllipsoid ::= SEQUENCE { + latitudeSign ENUMERATED {north, south}, + degreesLatitude INTEGER (0..8388607), -- 23 bit field + degreesLongitude INTEGER (-8388608..8388607), -- 24 bit field + altitudeDirection ENUMERATED {height, depth}, + altitude INTEGER (0..32767), -- 15 bit field + uncertaintySemiMajor INTEGER (0..127), + uncertaintySemiMinor INTEGER (0..127), + orientationMajorAxis INTEGER (0..179), + uncertaintyAltitude INTEGER (0..127), + confidence INTEGER (0..100) +} + +EllipsoidArc ::= SEQUENCE { + latitudeSign ENUMERATED {north, south}, + degreesLatitude INTEGER (0..8388607), -- 23 bit field + degreesLongitude INTEGER (-8388608..8388607), -- 24 bit field + innerRadius INTEGER (0..65535), -- 16 bit field, + uncertaintyRadius INTEGER (0..127), + offsetAngle INTEGER (0..179), + includedAngle INTEGER (0..179), + confidence INTEGER (0..100) +} + +RangeAndOrDirection ::= SEQUENCE { + range Range OPTIONAL, + azimuth Azimuth OPTIONAL, + elevation Elevation OPTIONAL +} + +Range ::= SEQUENCE { + rangeResult INTEGER (0..999), + uncertainty INTEGER (0..127), + confidence INTEGER (0..100) OPTIONAL +} + +Azimuth ::= SEQUENCE { + azimuthResult INTEGER (0..89), + uncertainty INTEGER (0..127), + confidence INTEGER (0..100) OPTIONAL +} + +Elevation ::= SEQUENCE { + elevationResult INTEGER (0..89), +} + +``` + +``` + uncertainty INTEGER (0..63), + confidence INTEGER (0..100) OPTIONAL +} + +HorizontalVelocity ::= SEQUENCE { + bearing INTEGER(0..359), + horizontalSpeed INTEGER(0..2047) +} + +HorizontalWithVerticalVelocity ::= SEQUENCE { + bearing INTEGER(0..359), + horizontalSpeed INTEGER(0..2047), + verticalDirection ENUMERATED{upward, downward}, + verticalSpeed INTEGER(0..255) +} + +HorizontalVelocityWithUncertainty ::= SEQUENCE { + bearing INTEGER(0..359), + horizontalSpeed INTEGER(0..2047), + uncertaintySpeed INTEGER(0..255) +} + +HorizontalWithVerticalVelocityAndUncertainty ::= SEQUENCE { + bearing INTEGER(0..359), + horizontalSpeed INTEGER(0..2047), + verticalDirection ENUMERATED{upward, downward}, + verticalSpeed INTEGER(0..255), + horizontalUncertaintySpeed INTEGER(0..255), + verticalUncertaintySpeed INTEGER(0..255) +} + +Polygon ::= SEQUENCE (SIZE (3..15)) OF PolygonPoints + +PolygonPoints ::= SEQUENCE { + latitudeSign ENUMERATED {north, south}, + degreesLatitude INTEGER (0..8388607), -- 23 bit field + degreesLongitude INTEGER (-8388608..8388607) -- 24 bit field +} + +-- TAG-COMMONIESPROVIDELOCATIONINFORMATION-STOP +-- ASN1STOP +``` + +| CommonEsProvideLocationInformation field descriptions | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| locationError
This field shall be included if and only if a location estimate and measurements are not included in the SLPP PDU. The field includes information concerning the reason for the lack of location information. The LocationFailureCause 'periodicLocationMeasurementsNotAvailable' shall be used by the UE if periodic location reporting was requested, but no measurements or location estimate are available when the reportingInterval expired. | +| locationEstimate
This field provides a location estimate using one of the geographic shapes defined in TS 23.032 [7]. Coding of the values of the various fields internal to each geographic shape follow the rules in TS 23.032 [7]. The conditions for including this field are defined for the locationInformationType field in a Request Location Information message. | +| velocityEstimate
This field provides a velocity estimate using one of the velocity shapes defined in TS 23.032 [7]. Coding of the values of the various fields internal to each velocity shape follow the rules in TS 23.032 [7]. | + +-- *End of SLPP-PDU-CommonContents* + +``` +-- ASN1START + +END + +-- ASN1STOP +``` + +## 6.6 SLPP PDU Common SL-PRS Methods Contents + +-- *SLPP-PDU-CommonSL-PRS-MethodsContents* + +This ASN.1 segment is the start of the SLPP PDU Common SL-PRS Methods Contents definitions. + +``` +-- ASN1START +-- TAG-SLPP-PDU-COMMONSL-PRS-METHODSCONTENTS-START + +SLPP-PDU-CommonSL-PRS-MethodsContents DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +IMPORTS + EllipsoidPointWithAltitudeAndUncertaintyEllipsoid, + LocationCoordinates + +FROM + SLPP-PDU-CommonContents + + FreqBandIndicatorNR, + SL-TimeStamp, + maxNrOfSLTxUEs, + nrMaxBands +``` + +``` +FROM + SLPP-PDU-Definitions; + +-- TAG-SLPP-PDU-COMMONSL-PRS-METHODSCONTENTS-STOP +-- ASN1STOP +``` + +### — *CommonSL-PRS-MethodsIEsRequestCapabilities* + +``` +-- ASN1START +-- TAG-COMMONSL-PRS-METHODSIESREQUESTCAPABILITIES-START + +CommonSL-PRS-MethodsIEsRequestCapabilities ::= SEQUENCE { +} + +-- TAG-COMMONSL-PRS-METHODSIESREQUESTCAPABILITIES-STOP +-- ASN1STOP +``` + +### — *CommonSL-PRS-MethodsIEsProvideCapabilities* + +``` +-- ASN1START +-- TAG-COMMONSL-PRS-METHODSIESPROVIDECAPABILITIES-START + +CommonSL-PRS-MethodsIEsProvideCapabilities ::= SEQUENCE { + sl-PRS-CapabilityBandList SEQUENCE (SIZE (1..nrMaxBands)) OF SL-PRS-CapabilityPerBand, + ... +} + +SL-PRS-CapabilityPerBand ::= SEQUENCE { + freqBandIndicatorNR FreqBandIndicatorNR, + --R1 41-1-19 ARP location provision for sidelink as assistance data + sl-PositioningARP-LocationProvision ENUMERATED {supported} OPTIONAL, + --R1 41-1-19a Report of Rx ARP-ID with SL positioning measurements + sl-PositioningMeasReportWithRxARP-ID ENUMERATED {supported} OPTIONAL, + ... +} + +-- TAG-COMMONSL-PRS-METHODSIESPROVIDECAPABILITIES-STOP +-- ASN1STOP +``` + +| CommonSL-PRS-MethodsIEsProvideCapabilities field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------| +| sl-PositioningARP-LocationProvision
Indicates whether UE supports of ARP location provision for sidelink as assistance data. | +| sl-PositioningMeasReportWithARP-ID
Indicates whether UE supports providing Rx ARP-ID with SL positioning measurements.. | + +#### CommonSL-PRS-MethodsIEsRequestAssistanceData + +``` +-- ASN1START +-- TAG-COMMONSL-PRS-METHODSIESREQUESTASSISTANCEDATA-START + +CommonSL-PRS-MethodsIEsRequestAssistanceData ::= SEQUENCE { + applicationLayerID OCTET STRING, + sl-PRS-AssistanceDataInfoRequest ENUMERATED { true} OPTIONAL, + sl-PosCalcAssistanceRequest BIT STRING { anchorUE-LocationInfo (0), + sl-ARP-LocationInfo (1) + OPTIONAL, + (SIZE (1..8)) + ... +} +-- TAG-COMMONSL-PRS-METHODSIESREQUESTASSISTANCEDATA-STOP +-- ASN1STOP +``` + +| CommonSL-PRS-MethodsIEsRequestAssistanceData field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| applicationLayerID
This field indicates the application layer ID of the UE who is requesting the assistance data. | +| sl-PRS-AssistanceDataInfoRequest
This field indicates the SL PRS Assistance Data requested. | +| sl-PosCalcAssistanceRequest
This field indicates the Position Calculation Assistance Data requested. This is represented by a bit string, with a one-value at the bit position means the particular assistance data is requested; a zero-value means not requested.
  • - bit 0 indicates whether the field anchorUE-LocationInformation in IE SL-PositionCalculationAssistance is requested or not;
  • - bit 1 indicates whether the field sl-ARP-LocationInfoPerTxUE in IE SL-PositionCalculationAssistance is requested or not;-
| + +#### CommonSL-PRS-MethodsIEsProvideAssistanceData + +``` +-- ASN1START +-- TAG-COMMONSL-PRS-METHODSIESPROVIDEASSISTANCEDATA-START + +CommonSL-PRS-MethodsIEsProvideAssistanceData ::= SEQUENCE { + sl-PRS-AssistanceDataInfo SEQUENCE (SIZE (1..maxNrOfSLTxUEs)) OF SL-PRS-AssistanceData OPTIONAL, + sl-PositionCalculationAssistanceInfo SEQUENCE (SIZE (1..maxNrOfSLTxUEs)) OF SL-PositionCalculationAssistance OPTIONAL, + ... +} +``` + +``` +SL-PRS-AssistanceData ::= SEQUENCE { + applicationLayerID OCTET STRING, + sl-PRS-SequenceID INTEGER(0..4095) OPTIONAL, -- SL PRS sequence generation, from server to Tx UE + sl-POS-ARP-ID-Tx INTEGER (1..4) OPTIONAL, -- sl-pos-arpID-Tx + sl-PRS-ResourceId INTEGER (0..16) OPTIONAL, -- sl-PRS-ResourceId + tx-TimeStamp SL-TimeStamp OPTIONAL, -- Tx TimeStamp + ... +} + +SL-PositionCalculationAssistance ::= SEQUENCE { + anchorUE-LocationInformation LocationCoordinates OPTIONAL, + applicationLayerID OCTET STRING, + sl-ARP-LocationInfoPerTxUE SL-ARP-LocationInfoPerTxUE OPTIONAL, -- sl-ARP-LocationInfo + ... +} + +SL-ARP-LocationInfoPerTxUE ::= SEQUENCE { + referencePoint ReferencePoint OPTIONAL, + arp-LocationInfoList SEQUENCE (SIZE (1..4)) OF ARP-LocationInfoElement, + ... +} + +ReferencePoint ::= SEQUENCE { + location3D EllipsoidPointWithAltitudeAndUncertaintyEllipsoid +} + +ARP-LocationInfoElement ::= SEQUENCE { + sl-POS-ARP-ID INTEGER (1..4), + arp-LocationInfo RelativeLocation OPTIONAL +} + +RelativeLocation ::= SEQUENCE { + milliArcSecondUnits ENUMERATED { mas0-03, mas0-3, mas3, mas30}, + heightUnits ENUMERATED {mm, cm, m, ...}, + deltaLatitude DeltaLatitude, + deltaLongitude DeltaLongitude, + deltaHeight DeltaHeight, + locationUNC LocationUncertainty OPTIONAL +} + +DeltaLatitude ::= SEQUENCE { + deltaLatitude INTEGER (-1024..1023), + coarseDeltaLatitude INTEGER (0..4095) OPTIONAL +} + +DeltaLongitude ::= SEQUENCE { + deltaLongitude INTEGER (-1024..1023), + coarseDeltaLongitude INTEGER (0..4095) OPTIONAL +} +``` + +``` + +DeltaHeight ::= SEQUENCE { + deltaHeight INTEGER (-1024..1023), + coarseDeltaHeight INTEGER (0..4095) OPTIONAL +} + +LocationUncertainty ::= SEQUENCE { + horizontalUncertainty INTEGER (0..255), + horizontalConfidence INTEGER (0..100), + verticalUncertainty INTEGER (0..255), + verticalConfidence INTEGER (0..100) +} + +-- TAG-COMMONSL-PRS-METHODSIESPROVIDEASSISTANCEDATA-STOP +-- ASN1STOP + +``` + +#### CommonSL-PRS-MethodsIEsProvideAssistanceData field descriptions + +| | | +|-------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| anchorUE-LocationInformation | This field provides anchor UE location information to the entity that does the location calculation for absolute SL positioning. | +| arp-LocationInfo | This field specifies the ARP location information. | +| applicationLayerID | This field provides an application layer ID as defined in TS 23.287 [9] which is used to identify a UE. | +| referencePoint | This field specifies the reference point used to define the location of ARPs provided in the arp-LocationInfoList . If this field is absent, the reference point is the same as in the previous entry of the SL-ARP-LocationInfoPerUE in the sl-PositionCalculationAssistanceInfo list. | +| sl-POS-ARP-ID | This field indicates ARP ID of an ARP. The ARP ID is used to uniquely identify an ARP associated with a UE. | +| sl-POS-ARP-ID-Tx | This field indicates ARP ID of an ARP used for transmission of SL PRS. | +| sl-PRS-AssistanceData | This field specifies the sidelink PRS assistance data of Tx UEs. | +| sl-PRS-SequenceID | This field specifies the sequence Id used to initialize cinit value used in pseudo random generator for generation of SL PRS sequence for transmission on a given SL PRS Resource, as specified in TS 38.211 [6]. If the Tx UE does not receive a sequence ID via SLPP message from the server, the Tx UE is expected to select one by itself. | + +#### CommonSL-PRS-MethodsIEsRequestLocationInformation + +``` + +-- ASN1START +-- TAG-COMMONSL-PRS-METHODSIESREQUESTLOCATIONINFORMATION-START + +CommonSL-PRS-MethodsIEsRequestLocationInformation ::= SEQUENCE { +} + +-- TAG-COMMONSL-PRS-METHODSIESREQUESTLOCATIONINFORMATION-STOP +-- ASN1STOP + +``` + +### — *Common-SL-PRS-MethodsIEsProvideLocationInformation* + +``` +-- ASN1START +-- TAG-COMMONSL-PRS-METHODSIESPROVIDELOCATIONINFORMATION-START + +CommonSL-PRS-MethodsIEsProvideLocationInformation ::= SEQUENCE { + ... +} + +-- TAG-COMMONSL-PRS-METHODSIESPROVIDELOCATIONINFORMATION-STOP +-- ASN1STOP +``` + +### — *End of SLPP-PDU-CommonSL-PRS-MethodsContents* + +``` +-- ASN1START + +END + +-- ASN1STOP +``` + +## 6.7 SLPP PDU SL-AoA Contents + +### — *SLPP-PDU-SL-AoA-Contents* + +This ASN.1 segment is the start of the SLPP PDU SL-AoA Contents definitions. + +``` +-- ASN1START +-- TAG-SLPP-PDU-SL-AOA-CONTENTS-START + +SLPP-PDU-SL-AoA-Contents DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +IMPORTS + LCS-GCS-Translation, + LOS-NLOS-Indicator, + PositioningModes, + SL-TimeStamp, + SL-TimingQuality, + maxNrOfSLTxUEs +``` + +``` +FROM + SLPP-PDU-Definitions; + +-- TAG-SLPP-PDU-SL-AOA-CONTENTS-STOP +-- ASN1STOP +``` + +### – ***SL-AoA-RequestCapabilities*** + +``` +-- ASN1START +-- TAG-SL-AOA-REQUESTCAPABILITIES-START + +SL-AoA-RequestCapabilities ::= SEQUENCE { +} + +-- TAG-SL-AOA-REQUESTCAPABILITIES-STOP +-- ASN1STOP +``` + +### – ***SL-AoA-ProvideCapabilities*** + +The IE *SL-AOA-ProvideCapabilities* is used to indicate the support of SL-AOA and to provide SL-AOA positioning capabilities. + +``` +-- ASN1START +-- TAG-SL-AOA-PROVIDECAPABILITIES-START + +SL-AoA-ProvideCapabilities ::= SEQUENCE { + applicationLayerID OCTET STRING, + positioningModes PositioningModes, + tenMsUnitResponseTime PositioningModes OPTIONAL, + periodicalReporting PositioningModes OPTIONAL, + ... +} + +-- TAG-SL-AOA-PROVIDECAPABILITIES-STOP +-- ASN1STOP +``` + +| SL-AoA-ProvideCapabilities field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| periodicalReporting
This field, if present, specifies the positioning modes for which the UE supports periodicalReporting . This is represented by a bit string, with a one value at the bit position means periodicalReporting for the positioning mode is supported; a zero value means not supported. If this field is absent, the UE does not support periodicalReporting in CommonEsRequestLocationInformation . | +| positioningModes
This field specifies the SL-AoA mode(s) supported by the UE. | +| tenMsUnitResponseTime
This field, if present, specifies the positioning modes for which the UE supports the enumerated value ' ten-milli-seconds ' in the IE ResponseTime in IE CommonEsRequestLocationInformation . This is represented by a bit string, with a one value at the bit position means ' ten-milli-seconds ' response time unit for the positioning mode is supported; a zero value means not supported. If this field is absent, the UE does not support ' ten-milli-seconds ' response time unit in CommonEsRequestLocationInformation . | + +### — SL-AoA-RequestAssistanceData + +``` +-- ASN1START +-- TAG-SL-AOA-REQUESTASSISTANCEDATA-START + +SL-AoA-RequestAssistanceData ::= SEQUENCE { + +} +-- TAG-SL-AOA-REQUESTASSISTANCEDATA-STOP +-- ASN1STOP +``` + +### — SL-AoA-ProvideAssistanceData + +``` +-- ASN1START +-- TAG-SL-AOA-PROVIDEASSISTANCEDATA-START + +SL-AoA-ProvideAssistanceData ::= SEQUENCE { + sl-AoA-AssistanceDataInfo SEQUENCE (SIZE (1..maxNrOfSLTxUEs)) OF SL-AoA-AssistanceData OPTIONAL, + ... +} + +SL-AoA-AssistanceData ::= SEQUENCE { + applicationLayerID OCTET STRING, + expectedSL-AzimuthAoA-AndUncertainty INTEGER(0..3599), -- expected-SL-AoA-and-Uncertainty + expectedSL-ZenithAoA-AndUncertainty INTEGER(0..1799), -- expected-SL-AoA-and-Uncertainty + ... +} + +-- TAG-SL-AoA-PROVIDEASSISTANCEDATA-STOP +-- ASN1STOP +``` + +| SL-AoA-ProvideAssistanceData field descriptions | +|---------------------------------------------------------------------------------------------------------------------------------------------| +| expectedSL-AzimuthAoA-AndUncertainty
This field provides expected SL-AzimuthAoA and uncertainty range to a measuring UE. | +| expectedSL-ZenithAoA-AndUncertainty
This field provides expected SL-ZenithAoA and uncertainty range to a measuring UE. | +| applicationLayerID
This field provides an application layer ID as defined in TS 23.287 [9] which is used to identify a UE. | + +### – SL-AoA-RequestLocationInformation + +``` +-- ASN1START +-- TAG-SL-AOA-REQUESTLOCATIONINFORMATION-START + +SL-AoA-RequestLocationInformation ::= SEQUENCE { + sl-ARP-InfoRequest ENUMERATED { true } OPTIONAL, + sl-LOS-NLOS-IndicatorRequest ENUMERATED { true } OPTIONAL, + sl-PRS-RSRP-Request ENUMERATED { true } OPTIONAL, + sl-FirstPathRSRPP-Request ENUMERATED { true } OPTIONAL, + sl-AdditionalPathsRequest ENUMERATED { true } OPTIONAL, + ... +} + +-- TAG-SL-AOA-REQUESTLOCATIONINFORMATION-STOP +-- ASN1STOP +``` + +| SL-AoA-RequestLocationInformation field descriptions | +|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| sl-AdditionalPathsRequest
This field, if present, indicates that the UE is requested to provide sl-AoA-AdditionalPathList . | +| sl-ARP-InfoRequest
This field, if present, indicates that the UE is requested to provide sl-POS-ARP-ID-Rx . | +| sl-FirstPathRSRPP-Request
This field, if present, indicates that the UE is requested to provide sl-FirstPathRSRPP . | +| sl-LOS-NLOS-IndicatorRequest
This field, if present, indicates that the UE is requested to provide the estimated LOS-NLOS-Indicator. | +| sl-PRS-RSRP-Request
This field, if present, indicates that the UE is requested to provide sl-PRS-RSRP-Result . | +| sl-TimingQuality
This field, if present, indicates that the UE is requested to provide sl-TimingQuality . | + +### – SL-AoA-ProvideLocationInformation + +``` +-- ASN1START +-- TAG-SL-AOA-PROVIDELOCATIONINFORMATION-START +``` + +``` + +SL-AoA-ProvideLocationInformation ::= SEQUENCE { + sl-AoA-SignalMeasurementInformation + SL-AoA-SignalMeasurementInformation OPTIONAL, + ... +} + +SL-AoA-SignalMeasurementInformation ::= SEQUENCE { + sl-AoA-MeasList + SEQUENCE (SIZE(1..maxNrOfSLTxUEs)) OF SL-AoA-MeasElement, + ... +} + +SL-AoA-MeasElement ::= SEQUENCE { + applicationLayerID OCTET STRING, + los-NLOS-Indicator LOS-NLOS-Indicator OPTIONAL, -- sl-losNlosIndicator + sl-AngleQuality MeasurementAngleQuality OPTIONAL, -- sl-AngleQuality + sl-AoA-AdditionalPathList SL-AoA-AdditionalPathList OPTIONAL, + sl-AzimuthAoA-FirstPathResult INTEGER (0..3599) OPTIONAL, -- sl-PRS-AoA + sl-AzimuthAoA-LCS-GCS-Translation LCS-GCS-Translation OPTIONAL, -- sl-LCS-to-GCS-translation + sl-POS-ARP-ID-Rx INTEGER (1..4) OPTIONAL, -- sl-pos-arpID-Rx + sl-PRS-ResourceId INTEGER (0..16) OPTIONAL, -- sl-PRS-ResourceId + sl-PRS-RSRP-Result INTEGER (0..126) OPTIONAL, -- sl-PRS-RSRP + sl-PRS-FirstPathRSRPP-Result INTEGER (0..126) OPTIONAL, -- sl-PRS-RSRPP + sl-Timestamp SL-Timestamp OPTIONAL, -- sl-Timestamp + sl-TimingQuality SL-TimingQuality OPTIONAL, -- sl-TimingQuality + sl-ZenithAoA-FirstPathResult INTEGER (0..1799) OPTIONAL, -- sl-PRS-AoA + sl-ZenithAoA-LCS-GCS-Translation LCS-GCS-Translation OPTIONAL, -- sl-LCS-to-GCS-translation + ... +} + +SL-AoA-AdditionalPathList ::= SEQUENCE (SIZE(1..2)) OF SL-AoA-AdditionalPath + +SL-AoA-AdditionalPath ::= SEQUENCE { + sl-AngleQuality MeasurementAngleQuality OPTIONAL, -- sl-AngleQuality + sl-AzimuthAoA-AdditionalPathResult INTEGER (0..3599) OPTIONAL, -- additionalPath-SL-PRS-AoA + sl-AzimuthAoA-LCS-GCS-Translation LCS-GCS-Translation OPTIONAL, -- sl-LCS-to-GCS-translation + sl-ZenithAoA-AdditionalPathResult INTEGER (0..1799) OPTIONAL, -- additionalPath-SL-PRS-AoA + sl-ZenithAoA-LCS-GCS-Translation LCS-GCS-Translation OPTIONAL, -- sl-LCS-to-GCS-translation + sl-PRS-AdditionalPathRSRPP-Result INTEGER (0..126) OPTIONAL, -- additionalPath-SL-PRS-RSRPP + sl-PRS-ResourceId INTEGER (0..16) OPTIONAL, -- sl-PRS-ResourceId + sl-POS-ARP-ID-Rx INTEGER (1..4) OPTIONAL, -- sl-pos-arpID-Rx + sl-Timestamp SL-Timestamp OPTIONAL, -- sl-Timestamp + sl-TimingQuality SL-TimingQuality OPTIONAL, -- sl-TimingQuality + ... +} + +MeasurementAngleQuality ::= SEQUENCE { + azimuthQuality INTEGER (0..255), + zenithQuality INTEGER (0..255) OPTIONAL, + resolution ENUMERATED {deg0dot1} +} + +``` + +``` +-- TAG-SL-AOA-PROVIDELOCATIONINFORMATION-STOP +-- ASN1STOP +``` + +| SL-AoA-ProvideLocationInformation field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| los-NLOS-Indicator
This field specifies the UE's best estimate of the LOS or NLOS of the UE measurements (including RSTD, RTOA, RSRP, RSRPP, AoA and UE Rx-Tx time difference). | +| sl-AngleQuality
This field specifies the angle quality for measurement results reported. | +| sl-AoA-AdditionalPathList
This field specifies the sidelink PRS measurements based on additional path of arrival. | +| sl-AzimuthAoA-FirstPathResult
This field specifies the first path result of SL-AzimuthAoA. | +| sl-AzimuthAoA-LCS-GCS-Translation
This field provides the angles $\alpha$ (bearing angle), $\beta$ (downtilt angle) and $\gamma$ (slant angle) for the translation of a Local Coordinate System (LCS) to a Global Coordinate System (GCS) as defined in TR 38.901 [8]. | +| sl-POS-ARP-ID-Rx
This field indicates ARP ID of an ARP used for reception for per-ARP measurement reporting. The ARP ID is used to uniquely identify an ARP associated with a UE. | +| sl-PRS-ResourceId
This field specifies the PRS resource ID used for SL positioning measurements. | +| sl-PRS-RSRP-Result
This field specifies the sidelink PRS reference signal received power (RSRP) measurement. | +| sl-PRS-FirstPathRSRPP-Result
This field specifies the SL-RSRPP measurement based on first path of arrival. | +| sl-TimeStamp
This field specifies the time instance at which the SL-PRS RSRP (if included) measurement is performed. | +| sl-ZenithAoA-FirstPathResult
This field specifies the first path result of SL-ZenithAoA. | +| sl-ZenithAoA-LCS-GCS-Translation
This field provides the angles $\alpha$ (bearing angle), $\beta$ (downtilt angle) and $\gamma$ (slant angle) for the translation of a Local Coordinate System (LCS) to a Global Coordinate System (GCS) as defined in TR 38.901 [8]. | + +— *End of SLPP-PDU-SL-AoA-Contents* + +``` +-- ASN1START +``` + +``` +END +``` + +``` +-- ASN1STOP +``` + +## 6.8 SLPP PDU SL-RTT Contents + +### – *SLPP-PDU-SL-RTT-Contents* + +This ASN.1 segment is the start of the SLPP PDU SL-RTT Contents definitions. + +``` +-- ASN1START +-- TAG-SLPP-PDU-SL-RTT-CONTENTS-START + +SLPP-PDU-SL-RTT-CONTENTS DEFINITIONS AUTOMATIC TAGS ::= +BEGIN + +IMPORTS + LCS-GCS-Translation, + LOS-NLOS-Indicator, + PositioningModes, + SL-TimeStamp, + SL-TimingQuality, + maxNrOfSLTxUEs + +FROM + SLPP-PDU-Definitions; + +-- TAG-SLPP-PDU-SL-RTT-CONTENTS-STOP +-- ASN1STOP +``` + +### – *SL-RTT-RequestCapabilities* + +``` +-- ASN1START +-- TAG-SL-RTT-REQUESTCAPABILITIES-START + +SL-RTT-RequestCapabilities ::= SEQUENCE { +} + +-- TAG-SL-RTT-REQUESTCAPABILITIES-STOP +-- ASN1STOP +``` + +### – *SL-RTT-ProvideCapabilities* + +The IE SL-RTT-ProvideCapabilities is used to indicate the support of SL-RTT and to provide SL-RTT positioning capabilities. + +``` +-- ASN1START +-- TAG-SL-RTT-PROVIDECAPABILITIES-START +``` + +``` + +SL-RTT-ProvideCapabilities ::= SEQUENCE { + applicationLayerID OCTET STRING, + positioningModes PositioningModes, + tenMsUnitResponseTime PositioningModes OPTIONAL, + periodicalReporting PositioningModes OPTIONAL, + ... +} +-- TAG-SL-RTT-PROVIDECAPABILITIES-STOP +-- ASN1STOP + +``` + +#### ***SL-RTT-ProvideCapabilities field descriptions*** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

periodicalReporting
This field, if present, specifies the positioning modes for which the UE supports periodicalReporting. This is represented by a bit string, with a one value at the bit position means periodicalReporting for the positioning mode is supported; a zero value means not supported. If this field is absent, the UE does not support periodicalReporting in CommonEsRequestLocationInformation.

| +|

positioningModes
This field specifies the SL-RTT mode(s) supported by the UE.

| +|

tenMsUnitResponseTime
This field, if present, specifies the positioning modes for which the UE supports the enumerated value 'ten-milli-seconds' in the IE ResponseTime in IE CommonEsRequestLocationInformation. This is represented by a bit string, with a one value at the bit position means 'ten-milli-seconds' response time unit for the positioning mode is supported; a zero value means not supported. If this field is absent, the UE does not support 'ten-milli-seconds' response time unit in CommonEsRequestLocationInformation.

| + +### — ***SL-RTT-RequestAssistanceData*** + +``` + +-- ASN1START +-- TAG-SL-RTT-REQUESTASSISTANCEDATA-START + +SL-RTT-RequestAssistanceData ::= SEQUENCE { +} +-- TAG-SL-RTT-REQUESTASSISTANCEDATA-STOP +-- ASN1STOP + +``` + +### — ***SL-RTT-ProvideAssistanceData*** + +``` + +-- ASN1START +-- TAG-SL-RTT-PROVIDEASSISTANCEDATA-START + +SL-RTT-ProvideAssistanceData ::= SEQUENCE { +} + +``` + +``` +-- TAG-SL-RTT-PROVIDEASSISTANCEDATA-STOP +-- ASN1STOP +``` + +### – *SL-RTT-RequestLocationInformation* + +``` +-- ASN1START +-- TAG-SL-RTT-REQUESTLOCATIONINFORMATION-START + +SL-RTT-RequestLocationInformation ::= SEQUENCE { + sl-ARP-InfoRequest ENUMERATED { true } OPTIONAL, + sl-LOS-NLOS-IndicatorRequest ENUMERATED { true } OPTIONAL, + sl-PRS-RSRP-Request ENUMERATED { true } OPTIONAL, + sl-FirstPathRSRPP-Request ENUMERATED { true } OPTIONAL, + sl-AdditionalPathsRequest ENUMERATED { true } OPTIONAL, + sl-TimingQuality ENUMERATED { true } OPTIONAL, + multipleSL-PRS-RxTxTimeDiffRequest SEQUENCE { + diffSL-PRS-Receptions ENUMERATED { n2, n3, n4 } OPTIONAL, + diffSL-PRS-Transmissions ENUMERATED { n2, n3, n4 } OPTIONAL + } OPTIONAL, + associatedSL-PRS-TxTimeStampRequest ENUMERATED { true } OPTIONAL, + ... +} + +-- TAG-SL-RTT-REQUESTLOCATIONINFORMATION-STOP +-- ASN1STOP +``` + +| SL-RTT-RequestLocationInformation field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| associatedSL-PRS-TxTimeStampRequest
This field, if present, indicates that the UE is requested to provide the associated SL PRS transmission time stamp. | +| multipleSL-PRS-RxTxTimeDiffRequest
This field, if present, indicates that the UE is requested to provide multiple Rx-Tx measurements for the same SL PRS transmission (resp. reception) and up to N different SL PRS receptions (resp. transmissions) for the same pair of UE(s). Fields are as follows:
  • - diffSL-PRS-Receptions indicates that the UE is requested to provide multiple Rx-Tx measurements for the same SL PRS transmission and up to N different SL PRS receptions.
  • - diffSL-PRS-Transmissions indicates that the UE is requested to provide multiple Rx-Tx measurements for the same SL PRS transmission and up to N different SL PRS transmissions.
| +| sl-AdditionalPathsRequest
This field, if present, indicates that the UE is requested to provide sl-RTT-AdditionalPathList . | +| sl-ARP-InfoRequest
This field, if present, indicates that the UE is requested to provide sl-POS-ARP-ID-Rx . | +| sl-FirstPathRSRPP-Request
This field, if present, indicates that the UE is requested to provide sl-FirstPathRSRPP . | +| sl-LOS-NLOS-IndicatorRequest
This field, if present, indicates that the UE is requested to provide the estimated LOS-NLOS-Indicator. | +| sl-PRS-RSRP-Request
This field, if present, indicates that the UE is requested to provide sl-PRS-RSRP-Result . | +| sl-TimingQuality
This field, if present, indicates that the UE is requested to provide sl-TimingQuality . | + +### — SL-RTT-ProvideLocationInformation + +``` + +-- ASN1START +-- TAG-SL-RTT-PROVIDELOCATIONINFORMATION-START + +SL-RTT-ProvideLocationInformation ::= SEQUENCE { + sl-RTT-SignalMeasurementInformation SL-RTT-SignalMeasurementInformation OPTIONAL, + ... +} + +SL-RTT-SignalMeasurementInformation ::= SEQUENCE { + sl-RTT-MeasList SEQUENCE (SIZE(1..maxNrOfSLTxUEs)) OF SL-RTT-MeasElement, + ... +} + +SL-RTT-MeasElement ::= SEQUENCE { + applicationLayerID OCTET STRING, + los-NLOS-Indicator LOS-NLOS-Indicator OPTIONAL, -- sl-losNlosIndicator + sl-POS-ARP-ID-Rx INTEGER (1..4) OPTIONAL, -- sl-pos-arpID-Rx + sl-PRS-ResourceId INTEGER (0..16) OPTIONAL, -- sl-PRS-ResourceId + sl-PRS-RxTxTimeDiffFirstPathResult 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) + } + sl-PRS-RSRP-Result INTEGER (0..126) OPTIONAL, -- sl-PRS-RxTxTimeDiff + sl-PRS-FirstPathRSRPP-Result INTEGER (0..126) OPTIONAL, -- sl-PRS-RSRP + sl-RTT-AdditionalPathList SL-RTT-AdditionalPathList OPTIONAL, + sl-TimeStamp SL-TimeStamp OPTIONAL, -- sl-Timestamp + sl-TimingQuality SL-TimingQuality OPTIONAL, -- sl-TimingQuality + tx-TimeInfo SL-TimeStamp OPTIONAL, -- tx-Time-Info + ... +} + +SL-RTT-AdditionalPathList ::= SEQUENCE (SIZE(1..8)) OF SL-RTT-AdditionalPath + +SL-RTT-AdditionalPath ::= SEQUENCE { + sl-PRS-RxTxTimeDiffAdditionalPathResult CHOICE { + k0 INTEGER (0..8191), + k1 INTEGER (0..4095), + k2 INTEGER (0..2047), + k3 INTEGER (0..1023), + k4 INTEGER (0..511), + k5 INTEGER (0..255) + } + sl-PRS-AdditionalPathRSRPP-Result INTEGER (0..126) OPTIONAL, -- additionalPath-SL-PRS-Rx-Tx-TimeDiff + sl-PRS-ResourceId INTEGER (0..16) OPTIONAL, -- additionalPath-SL-PRS-RSRP + sl-POS-ARP-ID-Rx INTEGER (1..4) OPTIONAL, -- sl-PRS-ResourceId + sl-TimeStamp SL-TimeStamp OPTIONAL, -- sl-pos-arpID-Rx + sl-TimingQuality SL-TimingQuality OPTIONAL, -- sl-Timestamp + tx-TimeInfo SL-TimeStamp OPTIONAL, -- sl-TimingQuality + ... +} + +-- TAG-SL-RTT-PROVIDELOCATIONINFORMATION-STOP +-- ASN1STOP + +``` + +| SL-RTT-ProvideLocationInformation field descriptions | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| los-NLOS-Indicator
This field specifies the UE's best estimate of the LOS or NLOS of the UE measurements (including RSTD, RTOA, RSRP, RSRPP, AoA and UE Rx-Tx time difference). | +| sl-POS-ARP-ID-Rx
This field indicates ARP ID of an ARP used for reception for per-ARP measurement reporting. The ARP ID is used to uniquely identify an ARP associated with a UE. | +| sl-PRS-ResourceId
This field specifies the PRS resource ID used for SL positioning measurements. | +| sl-PRS-RxTxTimeDiffFirstPathResult
This field specifies SL Rx-Tx time difference measurement based on first path of arrival. | +| sl-PRS-RSRP-Result
This field specifies the sidelink PRS reference signal received power (RSRP) measurement. | +| sl-PRS-FirstPathRSRPP-Result
This field specifies the SL-RSRPP measurement based on first path of arrival. | +| sl-RTT-AdditionalPathList
This field specifies the sidelink PRS measurements based on additional path of arrival. | +| sl-TimeStamp
This field specifies the time instance at which the SL Rx-Tx time difference and SL-PRS RSRP (if included) measurement is performed. | + +-- *End of SLPP-PDU-SL-RTT-Contents* + +``` +-- ASN1START + +END + +-- ASN1STOP +``` + +## 6.9 SLPP PDU SL-TDOA Contents + +-- *SLPP-PDU-SL-TDOA-Contents* + +This ASN.1 segment is the start of the SLPP PDU SL-TDOA Contents definitions. + +``` +-- ASN1START +-- TAG-SLPP-PDU-SL-TDOA-CONTENTS-START + +SLPP-PDU-SL-TDOA-CONTENTS DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +IMPORTS + LCS-GCS-Translation, + LOS-NLOS-Indicator, + PositioningModes, +``` + +``` + +SL-RTD-Info, +SL-TimeStamp, +SL-TimingQuality, +maxNrOfSLTxUEs + +FROM + SLPP-PDU-Definitions; + +-- TAG-SLPP-PDU-SL-TDOA-CONTENTS-STOP +-- ASN1STOP + +``` + +### — *SL-TDOA-RequestCapabilities* + +``` + +-- ASN1START +-- TAG-SL-TDOA-REQUESTCAPABILITIES-START + +SL-TDOA-RequestCapabilities ::= SEQUENCE { + +} + +-- TAG-SL-TDOA-REQUESTCAPABILITIES-STOP +-- ASN1STOP + +``` + +### — *SL-TDOA-ProvideCapabilities* + +The IE *SL-TDOA-ProvideCapabilities* is used to indicate the support of SL-TDOA and to provide SL-TDOA positioning capabilities. + +``` + +-- ASN1START +-- TAG-SL-TDOA-PROVIDECAPABILITIES-START + +SL-TDOA-ProvideCapabilities ::= SEQUENCE { + applicationLayerID OCTET STRING, + positioningModes PositioningModes, + tenMsUnitResponseTime PositioningModes OPTIONAL, + periodicalReporting PositioningModes OPTIONAL, + ... +} + +-- TAG-SL-TDOA-PROVIDECAPABILITIES-STOP +-- ASN1STOP + +``` + +| SL-TDOA-ProvideCapabilities field descriptions | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| periodicalReporting
This field, if present, specifies the positioning modes for which the UE supports periodicalReporting . This is represented by a bit string, with a one value at the bit position means periodicalReporting for the positioning mode is supported; a zero value means not supported. If this field is absent, the UE does not support periodicalReporting in CommonEsRequestLocationInformation . | +| positioningModes
This field specifies the SL-TDOA mode(s) supported by the UE. | +| tenMsUnitResponseTime
This field, if present, specifies the positioning modes for which the UE supports the enumerated value ' ten-milli-seconds ' in the IE ResponseTime in IE CommonEsRequestLocationInformation . This is represented by a bit string, with a one value at the bit position means ' ten-milli-seconds ' response time unit for the positioning mode is supported; a zero value means not supported. If this field is absent, the UE does not support ' ten-milli-seconds ' response time unit in CommonEsRequestLocationInformation . | + +### — SL-TDOA-RequestAssistanceData + +``` +-- ASN1START +-- TAG-SL-TDOA-REQUESTASSISTANCEDATA-START + +SL-TDOA-RequestAssistanceData ::= SEQUENCE { + sl-RTD-InfoRequest ENUMERATED { true } OPTIONAL, + ... +} + +-- TAG-SL-TDOA-REQUESTASSISTANCEDATA-STOP +-- ASN1STOP +``` + +| SL-TDOA-RequestAssistanceData field descriptions | +|-------------------------------------------------------------------------------------| +| sl-RTD-InfoRequest
This field indicates the SL RTD information requested. | + +### — SL-TDOA-ProvideAssistanceData + +``` +-- ASN1START +-- TAG-SL-TDOA-PROVIDEASSISTANCEDATA-START + +SL-TDOA-ProvideAssistanceData ::= SEQUENCE { + sl-PositionCalculationAssistanceTDOA SL-PositionCalculationAssistanceTDOA OPTIONAL +} + +SL-PositionCalculationAssistanceTDOA ::= SEQUENCE { + sl-RTD-Info SL-RTD-Info OPTIONAL +} + +-- TAG-SL-TDOA-PROVIDEASSISTANCEDATA-STOP +-- ASN1STOP +``` + +#### | | |---------------------------------------------------------| | SL-TDOA-ProvideAssistanceData field descriptions | |---------------------------------------------------------| + +#### | | |--------------------| | sl-RTD-Info | |--------------------| + +| | +|----------------------------------------------------------------| +| This field provides synchronization information of anchor UEs. | +|----------------------------------------------------------------| + +### — SL-TDOA-RequestLocationInformation + +``` +-- ASN1START +-- TAG-SL-TDOA-REQUESTLOCATIONINFORMATION-START + +SL-TDOA-RequestLocationInformation ::= SEQUENCE { + sl-ARP-InfoRequest ENUMERATED { true } OPTIONAL, + sl-LOS-NLOS-IndicatorRequest ENUMERATED { true } OPTIONAL, + sl-PRS-RSRP-Request ENUMERATED { true } OPTIONAL, + sl-FirstPathRSRPP-Request ENUMERATED { true } OPTIONAL, + sl-AdditionalPathsRequest ENUMERATED { true } OPTIONAL, + sl-TimingQuality ENUMERATED { true } OPTIONAL, + ... +} + +-- TAG-SL-TDOA-REQUESTLOCATIONINFORMATION-STOP +-- ASN1STOP +``` + +#### | | |--------------------------------------------------------------| | SL-TDOA-RequestLocationInformation field descriptions | |--------------------------------------------------------------| + +#### | | |---------------------------| | sl-ARP-InfoRequest | |---------------------------| + +| | +|-------------------------------------------------------------------------------------------------| +| This field, if present, indicates that the UE is requested to provide sl-POS-ARP-ID-Rx . | +|-------------------------------------------------------------------------------------------------| + +#### | | |-------------------------------------| | sl-LOS-NLOS-IndicatorRequest | |-------------------------------------| + +| | +|---------------------------------------------------------------------------------------------------------| +| This field, if present, indicates that the UE is requested to provide the estimated LOS-NLOS-Indicator. | +|---------------------------------------------------------------------------------------------------------| + +#### | | |----------------------------| | sl-PRS-RSRP-Request | |----------------------------| + +| | +|---------------------------------------------------------------------------------------------------| +| This field, if present, indicates that the UE is requested to provide sl-PRS-RSRP-Result . | +|---------------------------------------------------------------------------------------------------| + +#### | | |----------------------------------| | sl-FirstPathRSRPP-Request | |----------------------------------| + +| | +|--------------------------------------------------------------------------------------------------| +| This field, if present, indicates that the UE is requested to provide sl-FirstPathRSRPP . | +|--------------------------------------------------------------------------------------------------| + +#### | | |----------------------------------| | sl-AdditionalPathsRequest | |----------------------------------| + +| | +|-----------------------------------------------------------------------------------------------------------| +| This field, if present, indicates that the UE is requested to provide sl-TDOA-AdditionalPathList . | +|-----------------------------------------------------------------------------------------------------------| + +#### | | |-------------------------| | sl-TimingQuality | |-------------------------| + +| | +|-------------------------------------------------------------------------------------------------| +| This field, if present, indicates that the UE is requested to provide sl-TimingQuality . | +|-------------------------------------------------------------------------------------------------| + +### — SL-TDOA-ProvideLocationInformation + +``` +-- ASN1START +-- TAG-SL-TDOA-PROVIDELOCATIONINFORMATION-START +``` + +``` + +SL-TDOA-ProvideLocationInformation ::= SEQUENCE { + sl-RSTD-ReferenceUE-Info SEQUENCE { + applicationLayerID OCTET STRING + } + sl-TDOA-SignalMeasurementInformation SL-TDOA-SignalMeasurementInformation OPTIONAL, + ... +} + +SL-TDOA-SignalMeasurementInformation ::= SEQUENCE { + sl-TDOA-MeasList SEQUENCE (SIZE(1..maxNrOfSLTxUEs)) OF SL-TDOA-MeasElement, + ... +} + +SL-TDOA-MeasElement ::= SEQUENCE { + applicationLayerID OCTET STRING, + los-NLOS-Indicator LOS-NLOS-Indicator OPTIONAL, -- sl-losNlosIndicator + sl-POS-ARP-ID-Rx INTEGER (1..4) OPTIONAL, -- sl-pos-arpID-Rx + sl-PRS-ResourceId INTEGER (0..16) OPTIONAL, -- sl-PRS-ResourceId + sl-PRS-RSRP-Result INTEGER (0..126) OPTIONAL, -- sl-PRS-RSRP + sl-PRS-FirstPathRSRPP-Result INTEGER (0..126) OPTIONAL, -- sl-PRS-RSRPP + sl-RSTD-FirstPathResult 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) + } + sl-TDOA-AdditionalPathList SL-TDOA-AdditionalPathList OPTIONAL, + sl-Timestamp SL-Timestamp OPTIONAL, -- sl-Timestamp + sl-TimingQuality SL-TimingQuality OPTIONAL, -- sl-TimingQuality + ... +} + +SL-TDOA-AdditionalPathList ::= SEQUENCE (SIZE(1..8)) OF SL-TDOA-AdditionalPath + +SL-TDOA-AdditionalPath ::= SEQUENCE { + sl-RSTD-AdditionalPathResult 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) + } + sl-PRS-AdditionalPathRSRPP-Result INTEGER (0..126) OPTIONAL, -- additionalPath-SL-PRS-RSRPP + sl-PRS-ResourceId INTEGER (0..16) OPTIONAL, -- sl-PRS-ResourceId + sl-POS-ARP-ID-Rx INTEGER (1..4) OPTIONAL, -- sl-pos-arpID-Rx + sl-Timestamp SL-Timestamp OPTIONAL, -- sl-Timestamp + sl-TimingQuality SL-TimingQuality OPTIONAL, -- sl-TimingQuality +} + +``` + +``` + + ... + } + + -- TAG-SL-TDOA-PROVIDELOCATIONINFORMATION-STOP + -- ASN1STOP + +``` + +| SL-TDOA-ProvideLocationInformation field descriptions | | +|---------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| los-NLOS-Indicator | This field specifies the UE's best estimate of the LOS or NLOS of the UE measurements (including RSTD, RTOA, RSRP, RSRPP, AoA and UE Rx-Tx time difference). | +| sl-POS-ARP-ID-Rx | This field indicates ARP ID of an ARP used for reception for per-ARP measurement reporting. The ARP ID is used to uniquely identify an ARP associated with a UE. | +| sl-PRS-ResourceId | This field specifies the PRS resource ID used for SL positioning measurements. | +| sl-PRS-RSRP-Result | This field specifies the sidelink PRS reference signal received power (RSRP) measurement. | +| sl-PRS-FirstPathRSRPP-Result | This field specifies the SL-RSRPP measurement based on first path of arrival. | +| sl-TDOA-AdditionalPathList | This field specifies the sidelink PRS measurements based on additional path of arrival. | +| sl-RSTD-FirstPathResult | This field specifies the SL-RSTD measurement based on first path of arrival. | +| sl-RSTD-ReferenceUE-Info | This field indicates reference UE information for SL-PRS based RSTD measurement report. | +| sl-TimeStamp | This field specifies the time instance at which the SL RSTD and SL-PRS RSRP (if included) measurement is performed. | + +– ***End of SLPP-PDU-SL-TDOA-Contents*** + +``` + + -- ASN1START + +END + + -- ASN1STOP + +``` + +## 6.10 SLPP PDU SL-TOA Contents + +– ***SLPP-PDU-SL-TOA-Contents*** + +This ASN.1 segment is the start of the SLPP PDU SL-TOA Contents definitions. + +``` + + -- ASN1START + +``` + +``` + +-- TAG-SLPP-PDU-SL-TOA-CONTENTS-START + +SLPP-PDU-SL-TOA-CONTENTS DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +IMPORTS + LCS-GCS-Translation, + LOS-NLOS-Indicator, + PositioningModes, + SL-RTD-Info, + SL-TimeStamp, + SL-TimingQuality, + maxNrOfSLTxUEs + +FROM + SLPP-PDU-Definitions; + +-- TAG-SLPP-PDU-SL-TOA-CONTENTS-STOP +-- ASN1STOP + +``` + +### – *SL-TOA-RequestCapabilities* + +``` + +-- ASN1START +-- TAG-SL-TOA-REQUESTCAPABILITIES-START + +SL-TOA-RequestCapabilities ::= SEQUENCE { +} + +-- TAG-SL-TOA-REQUESTCAPABILITIES-STOP +-- ASN1STOP + +``` + +### – *SL-TOA-ProvideCapabilities* + +The IE *SL-TOA-ProvideCapabilities* is used to indicate the support of SL-TOA and to provide SL-TOA positioning capabilities. + +``` + +-- ASN1START +-- TAG-SL-TOA-PROVIDECAPABILITIES-START + +SL-TOA-ProvideCapabilities ::= SEQUENCE { + applicationLayerID OCTET STRING, + positioningModes PositioningModes, + tenMsUnitResponseTime PositioningModes OPTIONAL, + periodicalReporting PositioningModes OPTIONAL, + ... +} + +``` + +``` + +} +-- TAG-SL-TOA-PROVIDECAPABILITIES-STOP +-- ASN1STOP + +``` + +#### SL-TOA-ProvideCapabilities field descriptions + +##### ***periodicalReporting*** + +This field, if present, specifies the positioning modes for which the UE supports *periodicalReporting*. This is represented by a bit string, with a one value at the bit position means *periodicalReporting* for the positioning mode is supported; a zero value means not supported. If this field is absent, the UE does not support *periodicalReporting* in *CommonEsRequestLocationInformation*. + +##### ***positioningModes*** + +This field specifies the SL-TOA mode(s) supported by the UE. + +##### ***tenMsUnitResponseTime*** + +This field, if present, specifies the positioning modes for which the UE supports the enumerated value '*ten-milli-seconds*' in the IE *ResponseTime* in IE *CommonEsRequestLocationInformation*. This is represented by a bit string, with a one value at the bit position means '*ten-milli-seconds*' response time unit for the positioning mode is supported; a zero value means not supported. If this field is absent, the UE does not support '*ten-milli-seconds*' response time unit in *CommonEsRequestLocationInformation*. + +### — ***SL-TOA-RequestAssistanceData*** + +``` + +-- ASN1START +-- TAG-SL-TOA-REQUESTASSISTANCEDATA-START + +SL-TOA-RequestAssistanceData ::= SEQUENCE { + sl-RTD-InfoRequest ENUMERATED { true } OPTIONAL, + ... +} + +-- TAG-SL-TOA-REQUESTASSISTANCEDATA-STOP +-- ASN1STOP + +``` + +#### SL-TOA-RequestAssistanceData field descriptions + +#### ***sl-RTD-InfoRequest*** + +This field indicates the SL RTD information requested. + +#### — ***SL-TOA-ProvideAssistanceData*** + +``` + +-- ASN1START +-- TAG-SL-TOA-PROVIDEASSISTANCEDATA-START + +SL-TOA-ProvideAssistanceData ::= SEQUENCE { + sl-PositionCalculationAssistanceTOA SL-PositionCalculationAssistanceTOA OPTIONAL +} + +``` + +``` + +SL-PositionCalculationAssistanceTOA ::= SEQUENCE { + sl-RTD-Info SL-RTD-Info OPTIONAL +} + +-- TAG-SL-TOA-PROVIDEASSISTANCEDATA-STOP +-- ASN1STOP + +``` + +#### | SL-TOA-ProvideAssistanceData field descriptions | |--------------------------------------------------------------------------------------| | sl-RTD-Info
This field provides synchronization information of anchor UEs. | + +#### SL-TOA-RequestLocationInformation + +``` + +-- ASN1START +-- TAG-SL-TOA-REQUESTLOCATIONINFORMATION-START + +SL-TOA-RequestLocationInformation ::= SEQUENCE { + sl-ARP-InfoRequest ENUMERATED { true } OPTIONAL, + sl-LOS-NLOS-IndicatorRequest ENUMERATED { true } OPTIONAL, + sl-PRS-RSRP-Request ENUMERATED { true } OPTIONAL, + sl-FirstPathRSRPP-Request ENUMERATED { true } OPTIONAL, + sl-AdditionalPathsRequest ENUMERATED { true } OPTIONAL, + sl-TimingQuality ENUMERATED { true } OPTIONAL, + ... +} + +-- TAG-SL-TOA-REQUESTLOCATIONINFORMATION-STOP +-- ASN1STOP + +``` + +#### | SL-TOA-RequestLocationInformation field descriptions | |--------------------------------------------------------------------------------------------------------------------------------------------------------| | sl-AdditionalPathsRequest
This field, if present, indicates that the UE is requested to provide sl-TOA-AdditionalPathList . | | sl-ARP-InfoRequest
This field, if present, indicates that the UE is requested to provide sl-POS-ARP-ID-Rx . | | sl-FirstPathRSRPP-Request
This field, if present, indicates that the UE is requested to provide sl-FirstPathRSRPP . | | sl-LOS-NLOS-IndicatorRequest
This field, if present, indicates that the UE is requested to provide the estimated LOS-NLOS-Indicator . | | sl-PRS-RSRP-Request
This field, if present, indicates that the UE is requested to provide sl-PRS-RSRP-Result . | | sl-TimingQuality
This field, if present, indicates that the UE is requested to provide sl-TimingQuality . | + +#### SL-TOA-ProvideLocationInformation + +``` + +-- ASN1START +-- TAG-SL-TOA-PROVIDELOCATIONINFORMATION-START + +SL-TOA-ProvideLocationInformation ::= SEQUENCE { + sl-TOA-SignalMeasurementInformation + SL-TOA-SignalMeasurementInformation OPTIONAL, + ... +} + +SL-TOA-SignalMeasurementInformation ::= SEQUENCE { + sl-TOA-MeasList + SEQUENCE (SIZE(1..maxNrOfSLTxUEs)) OF SL-TOA-MeasElement, + ... +} + +SL-TOA-MeasElement ::= SEQUENCE { + applicationLayerID + OCTET STRING, + los-NLOS-Indicator + LOS-NLOS-Indicator OPTIONAL, -- sl-losNlosIndicator + sl-RTOA-FirstPathResult + 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) + } + OPTIONAL, -- sl-PRS-RTOA + sl-POS-ARP-ID-Rx + INTEGER (1..4) OPTIONAL, -- sl-pos-arpID-Rx + sl-PRS-ResourceId + INTEGER (0..16) OPTIONAL, -- sl-PRS-ResourceId + sl-PRS-RSRP-Result + INTEGER (0..126) OPTIONAL, -- sl-PRS-RSRP + sl-PRS-FirstPathRSRPP-Result + INTEGER (0..126) OPTIONAL, -- sl-PRS-RSRPP + sl-TOA-AdditionalPathList + SL-TOA-AdditionalPathList OPTIONAL, + sl-Timestamp + SL-Timestamp OPTIONAL, -- sl-Timestamp + sl-TimingQuality + SL-TimingQuality OPTIONAL, -- sl-TimingQuality + ... +} + +SL-TOA-AdditionalPathList ::= SEQUENCE (SIZE(1..8)) OF SL-TOA-AdditionalPath + +SL-TOA-AdditionalPath ::= SEQUENCE { + sl-RTOA-AdditionalPathResult + 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) + } + OPTIONAL, -- additionalPath-SL-PRS-RTOA + sl-PRS-AdditionalPathRSRPP-Result + INTEGER (0..126) OPTIONAL, -- additionalPath-SL-PRS-RSRPP + sl-PRS-ResourceId + INTEGER (0..16) OPTIONAL, -- sl-PRS-ResourceId + sl-POS-ARP-ID-Rx + INTEGER (1..4) OPTIONAL, -- sl-pos-arpID-Rx +} + +``` + +``` + +sl-TimeStamp SL-TimeStamp OPTIONAL, -- sl-Timestamp +sl-TimingQuality SL-TimingQuality OPTIONAL, -- sl-TimingQuality +... +} + +-- TAG-SL-TOA-PROVIDELOCATIONINFORMATION-STOP +-- ASN1STOP + +``` + +| SL-TOA-ProvideLocationInformation field descriptions | | +|-------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| los-NLOS-Indicator | This field specifies the UE's best estimate of the LOS or NLOS of the UE measurements (including RSTD, RTOA, RSRP, RSRPP, AoA and UE Rx-Tx time difference). | +| sl-TOA-AdditionalPathList | This field specifies the sidelink PRS measurements based on additional path of arrival. | +| sl-POS-ARP-ID-Rx | This field indicates ARP ID of an ARP used for reception for per-ARP measurement reporting. The ARP ID is used to uniquely identify an ARP associated with a UE. | +| sl-PRS-ResourceId | This field specifies the PRS resource ID used for SL positioning measurements. | +| sl-PRS-RSRP-Result | This field specifies the sidelink PRS reference signal received power (RSRP) measurement. | +| sl-PRS-FirstPathRSRPP-Result | This field specifies the SL-RSRPP measurement based on first path of arrival. | +| sl-RTOA-FirstPathResult | This field specifies the SL-RTOA measurement based on first path of arrival. | +| sl-TimeStamp | This field specifies the time instance at which the SL RTOA and SL-PRS RSRP (if included) measurement is performed. | + +– **End of SLPP-PDU-SL-TOA-Contents** + +``` + +-- ASN1START + +END + +-- ASN1STOP + +``` + +## 6.11 Information elements related to Discovery Message + +This clause specifies information elements that are transferred in Discovery Message for ranging and sidelink positioning. + +### – *NR-DiscoveryMessageMetaDataContents* + +This ASN.1 segment is the start of the *NR-DiscoveryMessageMetaDataContents* definitions. + +``` +-- ASN1START +-- TAG-NR-DISCOVERYMESSAGEMETADATACONTENTS-START + +NR-DiscoveryMessageMetaDataContents DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- TAG-NR-DISCOVERYMESSAGEMETADATACONTENTS-STOP +-- ASN1STOP +``` + +### – *RSPP-Metadata* + +The IE *RSPP-Metadata* includes the UE information included in Discovery Message for ranging and sidelink positioning. + +``` +-- ASN1START +-- TAG-RSPP-METADATA-START + +RSPP-Metadata ::= SEQUENCE { + ue-RoleList BIT STRING { anchorUE(0), serverUE(1), targetUE(2) } (SIZE (1..8)), + knownLocationAvailable ENUMERATED {true} OPTIONAL +} + +-- TAG-RSPP-METADATA-STOP +-- ASN1STOP +``` + +| RSPP-Metadata field descriptions | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

ue-RoleList
This field indicates the UE role associate with the discovery message. This is represented by a bit string, with a one value at the bit position means the particular UE role associate with the discovery message.

  • - bit 0 indicates whether the UE supports UE role as an Anchor UE or not;
  • - bit 1 indicates whether the UE supports UE role as a Server UE or not;
  • - bit 2 indicates whether the UE supports UE role as a Target UE or not;
| +|

knownLocationAvailable
This field indicates whether the location of an Anchor UE is known or is able to be known, e.g., via Uu based positioning. The field can only be present if the bit 0 of ue-RoleList is set.

| + +### – *End of NR-DiscoveryMessageMetaDataContents* + +``` +-- ASN1START +``` + +END + +-- ASN1STOP + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|----------------|------------|----|-----|-----|-----------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 04/2023 | RAN2#121 bis-e | R2-2302739 | | | | | 0.0.1 | +| 04/2023 | RAN2#121 bis-e | R2-2304306 | | | | | 0.0.2 | +| 05/2023 | RAN2#122 | R2-2305439 | | | | | 0.0.3 | +| 08/2023 | RAN2#123 | R2-2307663 | | | | | 0.0.4 | +| 09/2023 | RAN2#123 | R2-2309183 | | | | Endorsed by RAN2 in email discussion [Post123][415] | 0.0.5 | +| 09/2023 | RAN#101 | RP-232009 | | | | To be presented to RAN for information | 1.0.0 | +| 10/2023 | RAN2#123 bis | R2-2310222 | | | | Not endorsed in RAN2#123bis | 1.1.0 | +| 11/2023 | RAN2#124 | R2-2312021 | | | | | 1.2.0 | +| 11/2023 | RAN2#124 | R2-2313630 | | | | Agreed by RAN2 in email discussion [Post124][419] | 1.3.0 | +| 12/2023 | RAN#102 | RP-233391 | | | | To be presented to RAN for Approval | 2.0.0 | +| 12/2023 | RAN#102 | | | | | Promoted to Rel-18 after approval | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38401/0931f3e098bd4539041de11c50cec2d2_img.jpg b/marked/Rel-18/38_series/38401/0931f3e098bd4539041de11c50cec2d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b0c3894fd40a71a7f487e661aaf3676076d41dd --- /dev/null +++ b/marked/Rel-18/38_series/38401/0931f3e098bd4539041de11c50cec2d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd395e9548ea6059a3719c7cd3042e09f5975bfe08b66fc1c42d901ab8031b39 +size 85842 diff --git a/marked/Rel-18/38_series/38401/0997dbaa9dfecedd60029d70b53327b8_img.jpg b/marked/Rel-18/38_series/38401/0997dbaa9dfecedd60029d70b53327b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..97e4eba1afe71536d4e4a05a7c7f46b3fb52e3a2 --- /dev/null +++ b/marked/Rel-18/38_series/38401/0997dbaa9dfecedd60029d70b53327b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ffdeb0e87f71d1595372730a31ea6bf17976447af7ec025b12937c2fcfec5c12 +size 55208 diff --git a/marked/Rel-18/38_series/38401/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg b/marked/Rel-18/38_series/38401/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..538f2c3042f792c01ea258f631c65ede888c8267 --- /dev/null +++ b/marked/Rel-18/38_series/38401/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ac7c9bfd5e3e77a8276f0a19c912e22273b7e66dd7fb1dd457d7b7830de137e +size 44346 diff --git a/marked/Rel-18/38_series/38401/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg b/marked/Rel-18/38_series/38401/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b13d134d0490196df1bdc510f7581e5ab0ae4965 --- /dev/null +++ b/marked/Rel-18/38_series/38401/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed6ab657c8afdd59982ab1cf341c36812338a6ebff6046aedb96e7baac8a989e +size 52998 diff --git a/marked/Rel-18/38_series/38401/11f18bf0233d812ad2604f88f3385d60_img.jpg b/marked/Rel-18/38_series/38401/11f18bf0233d812ad2604f88f3385d60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e09ac4be68e768430bbf9d39ff3c154a2fad07c --- /dev/null +++ b/marked/Rel-18/38_series/38401/11f18bf0233d812ad2604f88f3385d60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:605f3db88090ab5a47a7446eb886e31a70c523a5e3c99507ea74f3fd9750fde6 +size 41262 diff --git a/marked/Rel-18/38_series/38401/18003425d0e8638dde4acc9c5c468c5c_img.jpg b/marked/Rel-18/38_series/38401/18003425d0e8638dde4acc9c5c468c5c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36a4f0ed673fe7e2b5c778f7eb82ca0b22d5b962 --- /dev/null +++ b/marked/Rel-18/38_series/38401/18003425d0e8638dde4acc9c5c468c5c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35d8bfd2b30d085a916cabdc5697f5eb5663565644cc6d9e0720d90696b1722a +size 53861 diff --git a/marked/Rel-18/38_series/38401/187d05bf7ead21e1394b61320d8b3632_img.jpg b/marked/Rel-18/38_series/38401/187d05bf7ead21e1394b61320d8b3632_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ce18a21edbb6e78ab4affcc70d47fc1bfb253055 --- /dev/null +++ b/marked/Rel-18/38_series/38401/187d05bf7ead21e1394b61320d8b3632_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fed46b0179236d209b9eb9c5d79497f2b317ee0b749643c7f6cf482648868f3b +size 48778 diff --git a/marked/Rel-18/38_series/38401/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg b/marked/Rel-18/38_series/38401/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bddcd9425b7e8fa25a6505bf9b8d4cb2bf8db212 --- /dev/null +++ b/marked/Rel-18/38_series/38401/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ea2c0e638bad18d303a7991c2c7a4b6d8e23d386b17d47ad918d9d171b5a681 +size 43670 diff --git a/marked/Rel-18/38_series/38401/245166735676c675f98f535bc4c6f0a1_img.jpg b/marked/Rel-18/38_series/38401/245166735676c675f98f535bc4c6f0a1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb1db76428e68633d0dcffdf360e4f65536973a2 --- /dev/null +++ b/marked/Rel-18/38_series/38401/245166735676c675f98f535bc4c6f0a1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de05e91bd50f608e82f55dd4f9c89c19d2ed63790d56afe638e42da016d4dc76 +size 129736 diff --git a/marked/Rel-18/38_series/38401/273610b2edda13f5c3de995f4e845396_img.jpg b/marked/Rel-18/38_series/38401/273610b2edda13f5c3de995f4e845396_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fdd2ecd6c3b8078418fba18c5884f76bfe7494b5 --- /dev/null +++ b/marked/Rel-18/38_series/38401/273610b2edda13f5c3de995f4e845396_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b538c9a05e3985324f7daa9d62d8944f57c7b2e712a2af344ac8f1c92c3128a +size 88404 diff --git a/marked/Rel-18/38_series/38401/276d5f4022bc6b9e4687f9ba4fc7594c_img.jpg b/marked/Rel-18/38_series/38401/276d5f4022bc6b9e4687f9ba4fc7594c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..223e7521c7485ab9368cc920c95ba6f8ba5c7c11 --- /dev/null +++ b/marked/Rel-18/38_series/38401/276d5f4022bc6b9e4687f9ba4fc7594c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f7eaca8e7a5ff122fd1d177cc29f4c35814e7cb8ab285f0ea8085d9b5bf7f8b4 +size 176450 diff --git a/marked/Rel-18/38_series/38401/2a476a0b3dbc3429436246db4784ff9f_img.jpg b/marked/Rel-18/38_series/38401/2a476a0b3dbc3429436246db4784ff9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d0c19598f5ae0108ec4e682f85ae0aac6e88c0f8 --- /dev/null +++ b/marked/Rel-18/38_series/38401/2a476a0b3dbc3429436246db4784ff9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c211be27e69097b6f7ac6cf2877aea6b30ca77f76f5ca027c378aa91aa76477 +size 93819 diff --git a/marked/Rel-18/38_series/38401/3334fcca5dac808f4fd3840aba35bc2e_img.jpg b/marked/Rel-18/38_series/38401/3334fcca5dac808f4fd3840aba35bc2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b605798a09a580695e011994ca75f8cccb6a05bb --- /dev/null +++ b/marked/Rel-18/38_series/38401/3334fcca5dac808f4fd3840aba35bc2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f2e1708b8bf738dbc5addfd9bbf06307869061e74e63baf4a561c993db1314f +size 81161 diff --git a/marked/Rel-18/38_series/38401/3337af75dfee8af7687b4f49914d6c93_img.jpg b/marked/Rel-18/38_series/38401/3337af75dfee8af7687b4f49914d6c93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..286ee3d0218627ce8a5aa4bb0c32174d4e19a910 --- /dev/null +++ b/marked/Rel-18/38_series/38401/3337af75dfee8af7687b4f49914d6c93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9197ba390051e8023a9edf99a9ac7bb00e3fb05f6ff0b4b39bcd7ca79078bd55 +size 110218 diff --git a/marked/Rel-18/38_series/38401/37e75e07bd69576f817434fc996be253_img.jpg b/marked/Rel-18/38_series/38401/37e75e07bd69576f817434fc996be253_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38fc42c5c2c542e25580a953c25699bdab9a37c3 --- /dev/null +++ b/marked/Rel-18/38_series/38401/37e75e07bd69576f817434fc996be253_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:043a733c315906e3c2fe7920f54605e08ef949697b6b3dcd5b69dddc1416132d +size 61285 diff --git a/marked/Rel-18/38_series/38401/468be155058fd5d2862919eb8ec35496_img.jpg b/marked/Rel-18/38_series/38401/468be155058fd5d2862919eb8ec35496_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f46bdd4f42e3dc82397195f73d452fa67388fce9 --- /dev/null +++ b/marked/Rel-18/38_series/38401/468be155058fd5d2862919eb8ec35496_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9543c04718479eccdbce1cb56200ea38246715accad16579c6026dac12fe71e2 +size 66310 diff --git a/marked/Rel-18/38_series/38401/4e3bce0b4a3062f7f237acd0b04e5c66_img.jpg b/marked/Rel-18/38_series/38401/4e3bce0b4a3062f7f237acd0b04e5c66_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c7418e28b998b7fec7af56a4c346c4942a777bc6 --- /dev/null +++ b/marked/Rel-18/38_series/38401/4e3bce0b4a3062f7f237acd0b04e5c66_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a286d2e3d7424e85ef350c7059893ddab4c4254864c11131a85586ad2800d33e +size 43768 diff --git a/marked/Rel-18/38_series/38401/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg b/marked/Rel-18/38_series/38401/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab9a174e4e7873ff81bcf47bdfe7ae0c633d6e40 --- /dev/null +++ b/marked/Rel-18/38_series/38401/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba0e8ae8935db84a1205645e7f6b667a4ab3e91d3d2bc2b3f49eec929d2d2f6a +size 75866 diff --git a/marked/Rel-18/38_series/38401/5478f70a6cef3e5672b2b22d28830cfb_img.jpg b/marked/Rel-18/38_series/38401/5478f70a6cef3e5672b2b22d28830cfb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..80ad6a6d9fb309a7d9a647c30bbdfcca0c848408 --- /dev/null +++ b/marked/Rel-18/38_series/38401/5478f70a6cef3e5672b2b22d28830cfb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a7974b848ee1be541b54a657a5e30096bcb6c78fbaed65bb6d7dba8ca6a499d +size 136488 diff --git a/marked/Rel-18/38_series/38401/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38401/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7902ce37421769fea33eae01569e7c7143d7688d --- /dev/null +++ b/marked/Rel-18/38_series/38401/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:34c7c6845dce16d5395824cb9f7b51ac87d19c213022d807841d042d3f4dcca8 +size 8354 diff --git a/marked/Rel-18/38_series/38401/61b2e15aedbb8a8dffc5426c0a284eb1_img.jpg b/marked/Rel-18/38_series/38401/61b2e15aedbb8a8dffc5426c0a284eb1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..483f290a77354b5c72e9a33ad05b2c19ff3d56cc --- /dev/null +++ b/marked/Rel-18/38_series/38401/61b2e15aedbb8a8dffc5426c0a284eb1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51ea40be5bae83cb759081f93a76fccccdadde4662a1b84ddad92b2e7d7380d2 +size 73455 diff --git a/marked/Rel-18/38_series/38401/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38401/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a60cae1e1dfbd48e7089b790f2ba85d40e4feca --- /dev/null +++ b/marked/Rel-18/38_series/38401/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1b0e54207cd68bd3b605b4da47f198c7eca0363642f9a4de0c699368454b9f42 +size 6962 diff --git a/marked/Rel-18/38_series/38401/67a1dd734d3de6e31754caf85d6fe77f_img.jpg b/marked/Rel-18/38_series/38401/67a1dd734d3de6e31754caf85d6fe77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..909deebdafe0d7bfe01237767c445e24caf4505c --- /dev/null +++ b/marked/Rel-18/38_series/38401/67a1dd734d3de6e31754caf85d6fe77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2d1f914871d92ac155e91727b8858e061422d25bded34fbec4f564866b2ac49 +size 68455 diff --git a/marked/Rel-18/38_series/38401/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-18/38_series/38401/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d6b2f5f63618da43d45b83477bae098dadcb930d --- /dev/null +++ b/marked/Rel-18/38_series/38401/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:21af463b6564592a5addd649753f999cfe2098d143ad2a3a5aa2294620688f62 +size 172106 diff --git a/marked/Rel-18/38_series/38401/77464a47f104d0d647b2414591137b64_img.jpg b/marked/Rel-18/38_series/38401/77464a47f104d0d647b2414591137b64_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a87906e44f9894c52d81fdb2db00f07a81637eb --- /dev/null +++ b/marked/Rel-18/38_series/38401/77464a47f104d0d647b2414591137b64_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e8be2bc20a5f7bc8f05634993f6c1b14925fb1a1defc20878d526501ed55b97 +size 62715 diff --git a/marked/Rel-18/38_series/38401/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-18/38_series/38401/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ccdf4b57a87deefa46806a1bcbd1dc6016cb8f6 --- /dev/null +++ b/marked/Rel-18/38_series/38401/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db1ace8a8b2ade0a0d9af8b0538e16c6fa19adfc33fa4fb5d01fdad4ebab5173 +size 207131 diff --git a/marked/Rel-18/38_series/38401/7ed5d5770331f31ade15439a21c31425_img.jpg b/marked/Rel-18/38_series/38401/7ed5d5770331f31ade15439a21c31425_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b4c0f3a36689002da5754fb9cfa4eec3717923e8 --- /dev/null +++ b/marked/Rel-18/38_series/38401/7ed5d5770331f31ade15439a21c31425_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:44e33ae2e59148847eaea972f3d9c539c81ab937e1dab0b532739f75f951e5a5 +size 54660 diff --git a/marked/Rel-18/38_series/38401/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-18/38_series/38401/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b8161fa081c293b9a1c05171ff983a4c1f8318b8 --- /dev/null +++ b/marked/Rel-18/38_series/38401/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3448f16a7b00ca458e7d7b2bd5bbb63577699309e9525fd16b601c1d69eaa5c3 +size 63742 diff --git a/marked/Rel-18/38_series/38401/884c44b6cb9fbe15347e0562a6085df2_img.jpg b/marked/Rel-18/38_series/38401/884c44b6cb9fbe15347e0562a6085df2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..517ce90831cec961bc53d05d49ca1b1a7b7d74dd --- /dev/null +++ b/marked/Rel-18/38_series/38401/884c44b6cb9fbe15347e0562a6085df2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d9edcb50eb3f689814ecf69349d7a78395f41b78994bd811f11d0a22e21fb56 +size 80221 diff --git a/marked/Rel-18/38_series/38401/8faeb7db381e28ab1ba06e9f48c19c6e_img.jpg b/marked/Rel-18/38_series/38401/8faeb7db381e28ab1ba06e9f48c19c6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..182a3ba18aad023809084c93a2b6bfc38acebe04 --- /dev/null +++ b/marked/Rel-18/38_series/38401/8faeb7db381e28ab1ba06e9f48c19c6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cbfea33a26886fd2e41cefa27368ebc46cf6506a76211838759a34fc01556613 +size 90326 diff --git a/marked/Rel-18/38_series/38401/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg b/marked/Rel-18/38_series/38401/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28eb6f8140274aa466713a2456898597e975e1d6 --- /dev/null +++ b/marked/Rel-18/38_series/38401/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:771dbc8d6e0c81e1c5b51917c14bce0bcc53815de351235a7d81d86247f69e65 +size 121399 diff --git a/marked/Rel-18/38_series/38401/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg b/marked/Rel-18/38_series/38401/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c62afaa8f29637de6993914519aa1a5d8bec6c5d --- /dev/null +++ b/marked/Rel-18/38_series/38401/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b09067d1f87c6ea544f86a240537d6ee1899befb1e4e1b53ff16b60dd013aea0 +size 85389 diff --git a/marked/Rel-18/38_series/38401/9b9dc99e34bb68ec85598e9d4bfda777_img.jpg b/marked/Rel-18/38_series/38401/9b9dc99e34bb68ec85598e9d4bfda777_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d63fcc80b2b06ad450e61acf57ca98c5b26a2b10 --- /dev/null +++ b/marked/Rel-18/38_series/38401/9b9dc99e34bb68ec85598e9d4bfda777_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4daf4c103e70b62cb8011131e1cd242dbbdee8affcce703cf0d28278e0d188cb +size 168284 diff --git a/marked/Rel-18/38_series/38401/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg b/marked/Rel-18/38_series/38401/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b48d43d55e2f3ec2cd9e4e33c56d6cee4d05408 --- /dev/null +++ b/marked/Rel-18/38_series/38401/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95a69572fa2e05623d546e0d53669bc78449778688edc0d2208c9b8f8ba31a70 +size 143461 diff --git a/marked/Rel-18/38_series/38401/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-18/38_series/38401/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0fbab0a0294353a1b73c44b696e05183c14a2500 --- /dev/null +++ b/marked/Rel-18/38_series/38401/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ede634a240be57d18e27a12a82b662df24712cfe5fa1ef9027dd08f8d85ea09f +size 44246 diff --git a/marked/Rel-18/38_series/38401/a4b868a176f7e0448ee72483727e9f6f_img.jpg b/marked/Rel-18/38_series/38401/a4b868a176f7e0448ee72483727e9f6f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..857b53e71d05f2bc6ce830011e4ff4d02b47bcff --- /dev/null +++ b/marked/Rel-18/38_series/38401/a4b868a176f7e0448ee72483727e9f6f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:026b1e25faa5ec6ac2446a334ef95985b86e3d2cb112d267a467df6b70e472ad +size 22510 diff --git a/marked/Rel-18/38_series/38401/a760132c773ae85ff8cedb26b500f223_img.jpg b/marked/Rel-18/38_series/38401/a760132c773ae85ff8cedb26b500f223_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36e626289c77de252a9ad18f4f79163e9f25a8f2 --- /dev/null +++ b/marked/Rel-18/38_series/38401/a760132c773ae85ff8cedb26b500f223_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c5fef0537a05136d0bb9e3ffe0efafd90a661d63045abb4f9db1de9a9cf4c0c9 +size 119460 diff --git a/marked/Rel-18/38_series/38401/b11b654648249b38a82129a35555b481_img.jpg b/marked/Rel-18/38_series/38401/b11b654648249b38a82129a35555b481_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bbb34d5eda06e343f1cbe82aee778dc0d264f09a --- /dev/null +++ b/marked/Rel-18/38_series/38401/b11b654648249b38a82129a35555b481_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b4abed083032a7df6c5daeefc75c3bf8d6bc8aaef7fe3c89f37383d0c8d4769 +size 95451 diff --git a/marked/Rel-18/38_series/38401/b43872c7a81f62572f3be03b77d8655f_img.jpg b/marked/Rel-18/38_series/38401/b43872c7a81f62572f3be03b77d8655f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e86215796e92026d112560d08554684a714f099 --- /dev/null +++ b/marked/Rel-18/38_series/38401/b43872c7a81f62572f3be03b77d8655f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:804dbd3f35fef62f8d9cf8ca9015555891d767ef2648db86d75e0e75e8032cae +size 70119 diff --git a/marked/Rel-18/38_series/38401/b63f41ca262d8ce9ef8affb62607f32b_img.jpg b/marked/Rel-18/38_series/38401/b63f41ca262d8ce9ef8affb62607f32b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ac31d08105280beaf185045d1e82995628b73f4 --- /dev/null +++ b/marked/Rel-18/38_series/38401/b63f41ca262d8ce9ef8affb62607f32b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:239e637bb147d299162ffdf87dde894fd87eb4d7c26e5ed7ab77fd2d97ff35de +size 67299 diff --git a/marked/Rel-18/38_series/38401/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg b/marked/Rel-18/38_series/38401/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c131ef602b0510def1579295fe02afd916ffab19 --- /dev/null +++ b/marked/Rel-18/38_series/38401/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:54fde56565da16c6bdf3c874187571362f2c9e7319aeb7f78836d1b6a9fe5e1e +size 212311 diff --git a/marked/Rel-18/38_series/38401/d0438bd44baf768f9c42bb4ff4431849_img.jpg b/marked/Rel-18/38_series/38401/d0438bd44baf768f9c42bb4ff4431849_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..37d4b88d73cc850fad8da6c4c544b54137f350cf --- /dev/null +++ b/marked/Rel-18/38_series/38401/d0438bd44baf768f9c42bb4ff4431849_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ccf00e5db864bea2829fac7067a5800e649b60a54b27e9f36182d9bcc685eff +size 55287 diff --git a/marked/Rel-18/38_series/38401/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg b/marked/Rel-18/38_series/38401/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc17d55e0687809602d74fcbe7d220be7294bf02 --- /dev/null +++ b/marked/Rel-18/38_series/38401/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:538f6b12a564a50de96dbaae46870cbd0672f00fae480cb33db37bafd79b36fd +size 111463 diff --git a/marked/Rel-18/38_series/38401/e16bfa31d748f4d99ec4ae3d16656926_img.jpg b/marked/Rel-18/38_series/38401/e16bfa31d748f4d99ec4ae3d16656926_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b559f674b1abae4b71528376eb38fc24f72e423 --- /dev/null +++ b/marked/Rel-18/38_series/38401/e16bfa31d748f4d99ec4ae3d16656926_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f012263080aab3436152f392dffe9089cd3f474eae2dc75f2542908c91d9f38 +size 137069 diff --git a/marked/Rel-18/38_series/38401/e6d2a5fe2df965cbe598f8ea80fbb7d6_img.jpg b/marked/Rel-18/38_series/38401/e6d2a5fe2df965cbe598f8ea80fbb7d6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d5fa0dabb064e951308e080f32bcfda097351c3 --- /dev/null +++ b/marked/Rel-18/38_series/38401/e6d2a5fe2df965cbe598f8ea80fbb7d6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a7dede2010db0760ec5e8db9bd2aacedeba8fe7e1867973b02b10469c976990c +size 98293 diff --git a/marked/Rel-18/38_series/38401/f4e5a86da5c799372a7c1ea2397dedb7_img.jpg b/marked/Rel-18/38_series/38401/f4e5a86da5c799372a7c1ea2397dedb7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8251a8a86679b3ea90bab53a9eacf985809d6b2b --- /dev/null +++ b/marked/Rel-18/38_series/38401/f4e5a86da5c799372a7c1ea2397dedb7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe92b1e5d49185018eb621ff8c5d0560fc95c3794bb4ae4cebe4cae6f60066d9 +size 50977 diff --git a/marked/Rel-18/38_series/38401/fe4f9338148fd891afbd3e301f9bad33_img.jpg b/marked/Rel-18/38_series/38401/fe4f9338148fd891afbd3e301f9bad33_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c923586bd7fe29d8149ea663259e96b63b064d7 --- /dev/null +++ b/marked/Rel-18/38_series/38401/fe4f9338148fd891afbd3e301f9bad33_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a14538a7c3dc212f976a49e9de1f980d3366361f1c10dee010de5f305b2b212f +size 110649 diff --git a/marked/Rel-18/38_series/38401/ffb6acd27b8e3a54392840948a75869f_img.jpg b/marked/Rel-18/38_series/38401/ffb6acd27b8e3a54392840948a75869f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9569587521dd6f25e31e548580fb79f57a6675cd --- /dev/null +++ b/marked/Rel-18/38_series/38401/ffb6acd27b8e3a54392840948a75869f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b27ac1a0f88951a4c1bf6989ffe74f45c7d7024a54e004e6ae992ecb456348a2 +size 80663 diff --git a/marked/Rel-18/38_series/38401/raw.md b/marked/Rel-18/38_series/38401/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0aff5438a4d747b6db89c729c6675f7169ff5467 --- /dev/null +++ b/marked/Rel-18/38_series/38401/raw.md @@ -0,0 +1,5655 @@ + + +# 3GPP TS 38.401 V18.0.0 (2023-12) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Architecture description (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +The logo for 5G Advanced, featuring a stylized '5G' in black with a green wave-like graphic above the 'G', and the word 'ADVANCED' in smaller black letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. The 'P' has a red signal wave icon at its base, and a small 'TM' trademark symbol is located to the upper right of the 'P'. + +3GPP logo + +## --- **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** + +--- + + + +## --- **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 and abbreviations ..... | 9 | +| 3.1 Definitions..... | 9 | +| 3.2 Abbreviations ..... | 11 | +| 4 General principles ..... | 13 | +| 5 General architecture ..... | 13 | +| 5.1 General ..... | 13 | +| 5.2 User plane..... | 13 | +| 5.3 Control plane..... | 14 | +| 6 NG-RAN architecture ..... | 15 | +| 6.1 Overview ..... | 15 | +| 6.1.1 Overall Architecture of NG-RAN ..... | 15 | +| 6.1.2 Overall architecture for separation of gNB-CU-CP and gNB-CU-UP..... | 16 | +| 6.1.3 Overall Architecture of IAB ..... | 17 | +| 6.1.4 Protocol stacks of IAB..... | 18 | +| 6.1.5 Overall Architecture of NR MBS..... | 20 | +| 6.1.6 Protocol stacks of L2 UE-to-Network Relay..... | 20 | +| 6.2 NG-RAN identifiers ..... | 21 | +| 6.2.1 Principle of handling Application Protocol Identities ..... | 21 | +| 6.2.2 gNB-DU ID ..... | 23 | +| 6.2.3 ng-eNB-DU ID ..... | 23 | +| 6.2.4 gNB-CU-UP ID ..... | 24 | +| 6.2.5 RAN UE ID ..... | 24 | +| 6.3 Transport addresses..... | 24 | +| 6.4 UE associations in NG-RAN Node..... | 24 | +| 6.5 MBS Session associations in NG-RAN Node..... | 25 | +| 7 NG-RAN functions description ..... | 26 | +| 7.0 General ..... | 26 | +| 7.1 NG-RAN sharing..... | 27 | +| 7.2 Remote Interference Management ..... | 27 | +| 7.3 Cross-Link Interference Management..... | 27 | +| 7.4 Support for Non-Public Networks..... | 27 | +| 7.5 RACH Optimisation Function..... | 27 | +| 7.6 Positioning..... | 27 | +| 7.7 Support for NR MBS..... | 27 | +| 7.7.1 Support of dynamic PTP and PTM switching..... | 28 | +| 7.7.2 Support of resource efficiency for RAN Sharing ..... | 28 | +| 7.7.2.1 General..... | 28 | +| 7.7.2.2 Support of resource efficiency for MOON ..... | 28 | +| 7.7.2.3 Support of resource efficiency for RAN Sharing with multiple cell-ID broadcast ..... | 28 | +| 7.7.3 Support of Multicast reception for UEs in RRC_INACTIVE..... | 28 | +| 7.8 PCI Optimisation Function..... | 28 | +| 7.9 Support for CCO ..... | 29 | +| 7.9.1 General ..... | 29 | +| 7.9.2 OAM requirements..... | 29 | +| 7.9.3 Dynamic coverage configuration changes..... | 29 | +| 7.10 Support of RAN visible QoE measurement ..... | 29 | +| 7.11 Support of AI/ML in NG-RAN..... | 29 | +| 8 Overall procedures in gNB-CU/gNB-DU Architecture..... | 29 | +| 8.1 UE Initial Access..... | 29 | + +| | | | +|----------|-----------------------------------------------------------------------------------------|----| +| 8.2 | Intra-gNB-CU Mobility..... | 31 | +| 8.2.1 | Intra-NR Mobility..... | 31 | +| 8.2.1.1 | Inter-gNB-DU Mobility ..... | 31 | +| 8.2.1.2 | Intra-gNB-DU handover ..... | 32 | +| 8.2.1.3 | Inter-gNB-DU Conditional Handover or Conditional PSCell Change or subsequent CPAC ..... | 33 | +| 8.2.1.4 | Intra-gNB-DU LTM ..... | 34 | +| 8.2.1.5 | Inter-gNB-DU LTM ..... | 36 | +| 8.2.1.6 | LTM with gNB-CU-UP change..... | 39 | +| 8.2.2 | EN-DC Mobility ..... | 41 | +| 8.2.2.1 | Inter-gNB-DU Mobility using MCG SRB..... | 41 | +| 8.2.2.2 | Inter-gNB-DU Mobility using SCG SRB (SRB3)..... | 43 | +| 8.2.2.3 | Inter-gNB-DU Conditional PSCell Change using MCG SRB without MN negotiation..... | 43 | +| 8.2.3 | Intra-CU topology adaptation procedure..... | 45 | +| 8.2.3.1 | Intra-CU topology adaptation procedure in SA ..... | 45 | +| 8.2.3.2 | Intra-CU topology adaptation procedure in NSA using MCG SRB..... | 48 | +| 8.2.3.3 | Intra-CU topology adaptation procedure in NSA using SCG SRB (SRB3)..... | 50 | +| 8.2.4 | Intra-CU topological redundancy procedure ..... | 50 | +| 8.2.5 | Intra-CU Backhaul RLF recovery for IAB-nodes in SA mode ..... | 53 | +| 8.3 | Mechanism of centralized retransmission of lost PDUs ..... | 54 | +| 8.3.1 | Centralized Retransmission in Intra gNB-CU Cases..... | 54 | +| 8.4 | Multi-Connectivity operation..... | 55 | +| 8.4.1 | Secondary Node Addition ..... | 55 | +| 8.4.1.1 | EN-DC ..... | 55 | +| 8.4.2 | Secondary Node Release (MN/SN initiated)..... | 56 | +| 8.4.2.1 | EN-DC ..... | 56 | +| 8.4.3 | SCG suspend/resume in RRC_INACTIVE..... | 57 | +| 8.4.4 | SCG Deactivation and Activation ..... | 58 | +| 8.4.4.1 | SN Addition with SCG Activation or Deactivation..... | 59 | +| 8.4.4.2 | MN initiated SN Modification with SCG Activation or Deactivation ..... | 60 | +| 8.4.4.3 | SN initiated SN Modification with SCG Activation or Deactivation..... | 61 | +| 8.5 | F1 Startup and cells activation ..... | 61 | +| 8.6 | RRC state transition ..... | 63 | +| 8.6.1 | RRC connected to RRC inactive ..... | 63 | +| 8.6.2 | RRC inactive to other states ..... | 63 | +| 8.7 | RRC connection reestablishment ..... | 65 | +| 8.8 | Multiple TNLAs for F1-C ..... | 67 | +| 8.9 | Overall procedures involving E1 and F1..... | 68 | +| 8.9.1 | UE Initial Access ..... | 68 | +| 8.9.2 | Bearer context setup over F1-U..... | 69 | +| 8.9.3 | Bearer context release over F1-U ..... | 71 | +| 8.9.3.1 | gNB-CU-CP initiated bearer context release ..... | 71 | +| 8.9.3.2 | gNB-CU-UP initiated bearer context release..... | 71 | +| 8.9.4 | Inter-gNB handover involving gNB-CU-UP change ..... | 72 | +| 8.9.5 | Change of gNB-CU-UP ..... | 74 | +| 8.9.6 | RRC State transition ..... | 75 | +| 8.9.6.1 | RRC Connected to RRC Inactive ..... | 75 | +| 8.9.6.2 | RRC Inactive to other states ..... | 76 | +| 8.9.7 | Trace activation/deactivation over F1 and E1 ..... | 78 | +| 8.9.8 | BH RLC channel establishment procedure ..... | 78 | +| 8.9.9 | Traffic Mapping..... | 80 | +| 8.9.9.1 | Traffic Mapping from IP-layer to Layer-2 ..... | 80 | +| 8.9.9.2 | BH RLC Channel Mapping on BAP Layer ..... | 80 | +| 8.9.10 | IAB-node release ..... | 80 | +| 8.9.10.1 | IAB-node orderly release..... | 81 | +| 8.9.10.2 | IAB-node disorderly release ..... | 81 | +| 8.9.11 | IAB-node OAM..... | 81 | +| 8.9.12 | Handling of IAB-MTs in INACTIVE State ..... | 81 | +| 8.9.13 | IP Address Allocation for IAB-nodes ..... | 81 | +| 8.9.14 | Mobile IAB-node authorization ..... | 82 | +| 8.9.15 | IAB-donor-CU-based NR Cell Identity (NCI) (re-)configuration for mobile IAB cells ..... | 83 | +| 8.9.16 | TAC/RANAC (re-)configuration for mobile IAB ..... | 83 | +| 8.10 | Multiple TNLAs for E1 ..... | 83 | + +| | | | +|----------|---------------------------------------------------------------------------------------------|-----| +| 8.11 | Support of Network Sharing with multiple cell-ID broadcast ..... | 85 | +| 8.11.1 | General ..... | 85 | +| 8.11.2 | Initial Registration – separate PLMN signalling ..... | 85 | +| 8.11.3 | RRC Connection Reestablishment – separate PLMN signalling ..... | 86 | +| 8.11.4 | Support of shared signalling transport..... | 87 | +| 8.12 | IAB-node Integration Procedure ..... | 87 | +| 8.12.1 | Standalone IAB integration ..... | 87 | +| 8.12.2 | NSA IAB Integration procedure..... | 88 | +| 8.12.3 | Mobile IAB-node integration ..... | 89 | +| 8.13 | Overall procedures for MDT..... | 90 | +| 8.13.0 | General ..... | 90 | +| 8.13.1 | Signalling based MDT activation..... | 90 | +| 8.13.2 | Management based MDT activation..... | 91 | +| 8.13.2.1 | General..... | 91 | +| 8.13.2.2 | Management based MDT Activation in gNB-CU-CP..... | 91 | +| 8.13.2.3 | Management based MDT Activation in gNB-DU..... | 92 | +| 8.13.2.4 | Management based MDT Activation in gNB-CU-UP..... | 93 | +| 8.13.2.5 | User consent propagation in EN-DC ..... | 94 | +| 8.13.2.6 | User consent propagation in MR-DC with 5GC..... | 95 | +| 8.13.2.7 | Management based trace activation in MR-DC with 5GC ..... | 96 | +| 8.13.3 | Alignment of MDT and QoE Measurements ..... | 97 | +| 8.13.4 | MDT reporting..... | 97 | +| 8.14 | Self-optimisation ..... | 97 | +| 8.14.1 | Overall procedures for MRO..... | 97 | +| 8.14.1.1 | Signalling of RLF information from gNB-CU to gNB-DU ..... | 98 | +| 8.14.1.2 | Signalling of RACH information from gNB-CU to gNB-DU..... | 98 | +| 8.15 | Overall procedures for NR MBS..... | 99 | +| 8.15.1 | General ..... | 99 | +| 8.15.1.1 | Broadcast MBS Session Setup..... | 99 | +| 8.15.1.2 | Multicast MBS Session Context Establishment ..... | 100 | +| 8.15.1.3 | Multicast MRB type re-configuration with F1-U ptp-retransmission tunnel establishment ..... | 102 | +| 8.15.2 | Mobility procedure for Multicast ..... | 103 | +| 8.15.2.1 | Inter-gNB-CU Mobility between MBS Supporting nodes ..... | 103 | +| 8.16 | Overall procedures for CPAC ..... | 104 | +| 8.16.1 | MN initiated Conditional PSCell Addition ..... | 104 | +| 8.16.2 | MN initiated conditional SN Change ..... | 105 | +| 8.16.3 | SN initiated conditional inter-SN Change ..... | 105 | +| 8.17 | IAB Inter-CU Topology Management..... | 105 | +| 8.17.1 | IAB Inter-donor-DU Re-routing..... | 105 | +| 8.17.2 | IAB Inter-CU Topology Redundancy ..... | 106 | +| 8.17.2.1 | IAB Inter-CU topological redundancy procedure ..... | 106 | +| 8.17.3 | IAB Inter-CU Topology Adaptation ..... | 108 | +| 8.17.3.1 | IAB inter-CU topology adaptation procedure ..... | 108 | +| 8.17.3.2 | IAB inter-CU topology adaptation procedure with descendant IAB-node..... | 111 | +| 8.17.4 | IAB Inter-CU Backhaul RLF recovery for single connected IAB-node..... | 113 | +| 8.18 | Overall procedure for Small Data Transmission during RRC Inactive ..... | 116 | +| 8.18.1 | RACH based SDT ..... | 116 | +| 8.18.2 | CG based SDT ..... | 117 | +| 8.18.3 | RA-SDT or non-SDT with CG-SDT configuration ..... | 119 | +| 8.18.4 | MT-SDT ..... | 119 | +| 8.19 | Overall procedures for L2 UE-to-Network Relay..... | 120 | +| 8.19.1 | Remote UE initial access..... | 120 | +| 8.19.2 | Remote UE RRC Reestablishment..... | 123 | +| 8.19.3 | Remote UE RRC Inactive to other states ..... | 125 | +| 8.19.4 | Service Continuity for L2 U2N relay ..... | 127 | +| 8.19.4.1 | Inter-gNB-DU switch from direct to indirect path ..... | 127 | +| 8.19.4.2 | Intra-gNB-DU switch from direct to indirect path ..... | 129 | +| 8.19.4.3 | Inter-gNB-CU switch from direct to indirect path..... | 130 | +| 8.20 | Void..... | 132 | +| 8.21 | Overall procedures for Network Controlled Repeater ..... | 132 | +| 8.21.1 | NCR Integration Procedure ..... | 132 | +| 8.22 | Overall procedures for multi-path support..... | 133 | + +| | | | +|--------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------|------------| +| 8.22.1 | Inter-DU direct path addition on top of indirect path ..... | 133 | +| 8.22.2 | Inter-DU indirect path addition on top of direct path ..... | 135 | +| 8.22.3 | Intra-DU direct path addition on top of indirect path ..... | 136 | +| 8.22.4 | Intra-DU indirect path addition on top of direct path ..... | 138 | +| 8.23 | Mobile IAB migration procedures ..... | 139 | +| 8.23.1 | Migration of mobile IAB-MT via Xn handover ..... | 139 | +| 8.23.2 | Migration of mobile IAB-MT via NG handover ..... | 140 | +| 8.23.3 | Mobile IAB-DU migration procedure ..... | 141 | +| 8.23.4 | Mobile IAB-node RLF recovery ..... | 142 | +| 8.24 | Timing resiliency service ..... | 142 | +| 8.24.1 | RAN TSS reporting towards the CN ..... | 142 | +| 8.24.2 | RAN TSS reporting towards the UE ..... | 144 | +| 9 | Synchronization ..... | 145 | +| 9.1 | gNB Synchronization ..... | 145 | +| 10 | NG-RAN interfaces ..... | 146 | +| 10.1 | NG interface ..... | 146 | +| 10.2 | Xn interface ..... | 146 | +| 10.3 | F1 interface ..... | 146 | +| 10.4 | E1 interface ..... | 146 | +| 10.5 | Antenna interface - general principles ..... | 146 | +| 11 | Overall procedures in NG-RAN Architecture ..... | 146 | +| 11.1 | Multiple TNLAs for Xn-C ..... | 146 | +| Annex A (informative): | Deployment scenarios of gNB/en-gNB ..... | 148 | +| Annex B: NG-RAN Architecture for Radio Access Network Sharing with multiple cell ID broadcast (informative) | ..... | 149 | +| Annex C (informative): | Change History ..... | 150 | + +# --- 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 overall architecture of the NG-RAN, including interfaces NG, Xn and F1 interfaces and their interaction with the radio interface. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 38.300: "NR; Overall description; Stage-2". +- [3] 3GPP TS 23.501: "System Architecture for the 5G System". +- [4] 3GPP TS 38.473: "NG-RAN; F1 application protocol (F1AP)". +- [5] 3GPP TS 38.414: "NG-RAN; NG data transport". +- [6] 3GPP TS 38.424: "NG-RAN; Xn data transport". +- [7] 3GPP TS 38.474: "NG-RAN; F1 data transport". +- [8] ITU-T Recommendation G.823 (2000-03): "The control of jitter and wander within digital networks which are based on the 2048 kbit/s hierarchy". +- [9] ITU-T Recommendation G.824 (2000-03): "The control of jitter and wander within digital networks which are based on the 1544 kbit/s hierarchy". +- [10] ITU-T Recommendation G.825 (2001-08): "The control of jitter and wander within digital networks which are based on the synchronous digital hierarchy (SDH)". +- [11] ITU-T Recommendation G.8261/Y.1361 (2008-04): "Timing and Synchronization aspects in Packet networks". +- [12] 3GPP TS 37.340: "NR; Multi-connectivity; Overall description; Stage-2". +- [13] 3GPP TS 33.501: "Security Architecture and Procedures for 5G System". +- [14] 3GPP TS 38.410: "NG-RAN; NG general aspect and principles". +- [15] 3GPP TS 38.420: "NG-RAN; Xn general aspects and principles". +- [16] 3GPP TS 38.470: "NG-RAN; F1 general aspects and principles". +- [17] 3GPP TS 38.460: "NG-RAN; E1 general aspects and principles". +- [18] 3GPP TS 33.210: "3G security; Network Domain Security (NDS); IP Network Layer Security". +- [19] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA), Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2". +- [20] 3GPP TS 32.422: "Trace control and configuration management". + +- [21] 3GPP TS 37.470: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and NG-RAN; W1 general aspects and principles; Stage-2". +- [22] 3GPP TS 38.340: "NR; Backhaul Adaptation Protocol (BAP) specification". +- [23] 3GPP TS 38.331: "NR; Radio Resource Control (RRC) protocol specification". +- [24] 3GPP TS 38.425: "NG-RAN; NR user plane Protocol". +- [25] 3GPP TS 38.305: "NG Radio Access Network (NG-RAN); Stage 2 functional specification of User Equipment (UE) positioning in NG-RAN". +- [26] 3GPP TS 38.472: "NG-RAN; F1 signalling transport". +- [27] 3GPP TS 23.247: " Architectural enhancements for 5G multicast-broadcast services; Stage 2". +- [28] 3GPP TS 36.401: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Architecture Description". +- [29] IETF RFC 4555 (2006-06): "RFC IKEv2 Mobility and Multihoming Protocol (MOBIKE)". +- [30] 3GPP TS 38.321 "NR; Medium Access Control (MAC) protocol specification". +- [31] 3GPP TS 37.320: "Radio measurement collection for Minimization of Drive Tests (MDT); Overall description; Stage 2". +- [32] 3GPP TS 23.502: "Procedures for the 5G System (5GS); Stage 2". +- [33] 3GPP TS 28.532: "Management and orchestration; Generic management services". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purpose 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]. + +**Associated QoS Flow:** as defined in TS 23.247 [27]. + +**Associated QoS flow information:** Information encompassing: QoS flow QoS parameters for associated QoS flows and mapping information between mapped (unicast) QoS flows and associated QoS flows. The respective information is included in a way that non-supporting RAN nodes would not establish respective RAN resources irrespective the multicast session state. + +**Boundary IAB-node:** an IAB-node with one RRC interface terminating at a different IAB-donor-CU than the F1 interface. This definition applies to partial migration, inter-donor redundancy and inter-donor RLF recovery. + +**Conditional Handover:** as defined in TS 38.300 [2]. + +**Conditional PSCell Addition:** as defined in TS 37.340 [12]. + +**Conditional PSCell Change:** as defined in TS 37.340 [12]. + +**DAPS Handover:** as defined in TS 38.300 [2]. + +**eNB-CP:** as defined in TS 36.401 [28]. + +**eNB-UP:** as defined in TS 36.401 [28]. + +**en-gNB:** as defined in TS 37.340 [12]. + +**Early Data Forwarding:** as defined in TS 38.300 [2]. + +**F1-terminating IAB-donor:** Refers to the IAB-donor that terminates F1 for the boundary IAB-node or a mobile IAB-node. + +**gNB:** as defined in TS 38.300 [2]. + +**gNB Central Unit (gNB-CU):** a logical node hosting RRC, SDAP and PDCP protocols of the gNB or RRC and PDCP protocols of the en-gNB that controls the operation of one or more gNB-DUs. The gNB-CU terminates the F1 interface connected with the gNB-DU. + +**gNB Distributed Unit (gNB-DU):** a logical node hosting RLC, MAC and PHY layers of the gNB or en-gNB, and its operation is partly controlled by gNB-CU. One gNB-DU supports one or multiple cells. One cell is supported by only one gNB-DU. The gNB-DU terminates the F1 interface connected with the gNB-CU. For DC operation, the MgNB-DU designates the gNB-DU of an en-gNB or a gNB acting as master node, and the SgNB-DU designates the gNB-DU of an en-gNB or a gNB acting as secondary node. + +**gNB-CU-Control Plane (gNB-CU-CP):** a logical node hosting the RRC and the control plane part of the PDCP protocol of the gNB-CU for an en-gNB or a gNB. The gNB-CU-CP terminates the E1 interface connected with the gNB-CU-UP and the F1-C interface connected with the gNB-DU. For DC operation, the MgNB-CU-CP designates the gNB-CU-CP of the gNB-CU for an en-gNB or a gNB acting as master node, and the SgNB-CU-CP designates the gNB-CU-CP of the gNB-CU for an en-gNB or a gNB acting as secondary node. + +**gNB-CU-User Plane (gNB-CU-UP):** a logical node hosting the user plane part of the PDCP protocol of the gNB-CU for an en-gNB, and the user plane part of the PDCP protocol and the SDAP protocol of the gNB-CU for a gNB. The gNB-CU-UP terminates the E1 interface connected with the gNB-CU-CP and the F1-U interface connected with the gNB-DU. For DC operation, the MgNB-CU-UP designates the gNB-CU-UP of the gNB-CU for an en-gNB or a gNB acting as master node, and the SgNB-CU-UP designates the gNB-CU-UP of the gNB-CU for an en-gNB or a gNB acting as secondary node. + +**IAB-node:** as defined in TS 38.300 [2]. + +**IAB-donor:** as defined in TS 38.300 [2]. + +**IAB-donor-CU:** the gNB-CU of an IAB-donor, terminating the F1 interface towards IAB-nodes and IAB-donor-DU. + +**IAB-donor-DU:** the gNB-DU of an IAB-donor, hosting the IAB BAP sublayer (as defined in TS 38.340 [22]), providing wireless backhaul to IAB-nodes. + +**IAB-DU:** as defined in TS 38.300 [2]. + +**IAB-MT:** as defined in TS 38.300 [2]. + +**IAB Topology:** as defined in TS 38.300 [2]. + +**Mapped QoS flows:** Unicast QoS flows requested to be established, i.e. included in the legacy QoS flow lists in a way, that non-support RAN nodes would attempt to establish unicast QoS flows and supporting RAN nodes can identify them as mapped QoS flows based on the associated QoS information. + +**Master node:** as defined in TS 37.340 [12]. + +**Master gNB:** see TS 37.340 [12]. + +**MBS session resource:** This term is used for specification of NG, Xn, F1 and E1 interfaces. It denotes NG-RAN interface and radio resources provided to support an MBS Session. + +**MP Relay UE:** as defined in TS 38.300 [2]. + +**MP Remote UE:** as defined in TS 38.300 [2]. + +**Multi-path:** as defined in TS 38.300 [2]. + +**ng-eNB:** as defined in TS 38.300 [2]. + +**ng-eNB Central Unit (ng-eNB-CU):** as defined in TS 37.470 [21]. + +**ng-eNB Distributed Unit (ng-eNB-DU):** as defined in TS 37.470 [21]. + +**ng-eNB-CU-Control Plane (ng-eNB-CU-CP):** a logical node hosting the RRC and the control plane part of the PDCP protocol of the ng-eNB-CU for an ng-eNB. The ng-eNB-CU-CP terminates the E1 interface connected with the ng-eNB-CU-UP and the W1-C interface connected with the ng-eNB-DU. + +**ng-eNB-CU-User Plane (ng-eNB-CU-UP):** a logical node hosting the user plane part of the PDCP protocol and the SDAP protocol of the ng-eNB-CU for an ng-eNB. The ng-eNB-CU-UP terminates the E1 interface connected with the ng-eNB-CU-CP and the W1-U interface connected with the ng-eNB-DU. + +**NG-RAN node:** as defined in TS 38.300 [2]. + +**Non-F1-terminating IAB-donor of boundary IAB-node:** Refers to the IAB-donor that has an RRC connection with the boundary node but does not terminate F1 with this boundary node. + +**PDU Session Resource:** This term is used for specification of NG, Xn, and E1 interfaces. It denotes NG-RAN interface and radio resources provided to support a PDU Session. + +**Public Network Integrated NPN:** as defined in TS 23.501 [3]. + +**RRC-terminating IAB-donor:** Refers to the IAB-donor that terminates the RRC connection of the mobile IAB-node. The RRC-terminating IAB-donor may also be an F1-terminating IAB-donor. + +**Secondary gNB:** see TS 37.340 [12]. + +**Stand-alone Non-Public Network:** as defined in TS 23.501 [3]. + +Subsequent CPAC: see TS 37.340 [12]. + +**U2N Relay UE:** as defined in TS 38.300 [2]. + +**U2N Remote UE:** as defined in TS 38.300 [2]. + +## 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 | +| AP | Application Protocol | +| AS | Access Stratum | +| AI | Artificial Intelligence | +| BAP | Backhaul Adaptation Protocol | +| BH | Backhaul | +| BSR | Buffer Status Report | +| CAG | Closed Access Group | +| CHO | Conditional Handover | +| CLI | Cross-Link Interference | +| CM | Connection Management | +| CMAS | Commercial Mobile Alert Service | +| CPA | Conditional PSCell Addition | +| CPC | Conditional PSCell Change | +| DAPS | Dual Active Protocol Stack | +| DU | Distributed Unit | +| EM | Element Manager | +| EN-DC | E-UTRA-NR Dual Connectivity | +| ETWS | Earthquake and Tsunami Warning System | +| F1-U | F1 User plane interface | +| F1-C | F1 Control plane interface | +| F1AP | F1 Application Protocol | +| FDD | Frequency Division Duplex | +| FTEID | Fully Qualified TEID | +| GTP-U | GPRS Tunnelling Protocol | +| IAB | Integrated Access and Backhaul | + +| | | +|---------|-------------------------------------------------| +| IP | Internet Protocol | +| L2 | Layer-2 | +| LTM | L1/L2 Triggered Mobility | +| MBS | Multicast Broadcast Service | +| MCG | Master Cell Group | +| MDT | Minimization of Drive Tests | +| MN | Master Node | +| MgNB | Master gNB | +| mIAB | Mobile IAB | +| mIAB-DU | Mobile IAB Distributed Unit | +| mIAB-MT | Mobile IAB Mobile Termination | +| MP | Multi-Path | +| MRB | MBS Radio Bearer | +| MRDC | Multi-Radio Dual Connectivity | +| N3C | Non-3GPP Connection | +| ML | Machine Learning | +| MT-SDT | Mobile Terminated Small Data Transmission | +| NAS | Non-Access Stratum | +| NCI | NR Cell Identity | +| NID | Network identifier | +| NPN | Non-Public Network | +| NSA | Non Standalone | +| OAM | Operation, Administration and Maintenance | +| PNI-NPN | Public Network Integrated Non-Public Network | +| PTP | Point to Point | +| PTM | Point to Multipoint | +| PWS | Public Warning System | +| QoE | Quality of Experience | +| QoS | Quality of Service | +| RANAC | RAN Area Code | +| RET | Remote Electrical Tilting | +| RIM | Remote Interference Management | +| RIM-RS | Remote Interference Management Reference Signal | +| RLF | Radio Link Failure | +| RNL | Radio Network Layer | +| RRC | Radio Resource Control | +| SA | Standalone | +| SAP | Service Access Point | +| SCG | Secondary Cell Group | +| SCTP | Stream Control Transmission Protocol | +| SDT | Small Data Transmission | +| SFN | System Frame Number | +| SgNB | Secondary gNB | +| SM | Session Management | +| SMF | Session Management Function | +| SN | Secondary Node | +| SNPN | Stand-alone Non-Public Network | +| SRAP | Sidelink Relay Adaptation Protocol | +| TAC | Tracking Area Code | +| TCE | Trace Collection Entity | +| TDD | Time Division Duplex | +| TDM | Time Division Multiplexing | +| TEID | Tunnel Endpoint Identifier | +| TMA | Tower Mounted Amplifier | +| TNL | Transport Network Layer | +| U2N | UE-to-Network | +| UL | Uplink | + +# --- 4 General principles + +The general principles guiding the definition of NG-RAN architecture as well as the NG-RAN interfaces are the following: + +- Logical separation of signalling and data transport networks. +- NG-RAN and 5GC functions are fully separated from transport functions. Addressing scheme used in NG-RAN and 5GC shall not be tied to the addressing schemes of transport functions. The fact that some NG-RAN or 5GC functions reside in the same equipment as some transport functions does not make the transport functions part of the NG-RAN or the 5GC. +- Mobility for an RRC connection is fully controlled by the NG-RAN. +- The NG-RAN interfaces are defined along the following principles: + - The functional division across the interfaces have as few options as possible. + - Interfaces are based on a logical model of the entity controlled through this interface. + - One physical network element can implement multiple logical nodes. + +# --- 5 General architecture + +## 5.1 General + +The protocols over Uu and NG interfaces are divided into two structures: + +- **User plane protocols** + +These are the protocols implementing the actual PDU Session service, i.e. carrying user data through the access stratum. + +- **Control plane protocols** + +These are the protocols for controlling the PDU Sessions and the connection between the UE and the network from different aspects (including requesting the service, controlling different transmission resources, handover etc.). Also a mechanism for transparent transfer of NAS messages is included. + +## 5.2 User plane + +The PDU Session Resource service is offered from SAP to SAP by the Access Stratum. Figure 5.2-1 shows the protocols on the Uu and the NG interfaces that linked together provide this PDU Session Resource service. + +![Figure 5.2-1: NG and Uu user plane diagram showing protocol stacks for UE, NG-RAN, and 5GC.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +The diagram illustrates the user plane protocol stacks across three entities: UE, NG-RAN, and 5GC, separated by Radio (Uu) and NG interfaces. The stack is divided into Non-Access Stratum (NAS) and Access Stratum (AS). + +- UE:** Contains a NAS block and an AS block. The AS block contains "Radio protocols (1)". +- NG-RAN:** Contains an AS block with two sub-components: "Radio protocols (1)" and "NG protocols (2)". +- 5GC:** Contains a NAS block and an AS block. The AS block contains "NG protocols (2)". +- Interfaces:** + - Radio (Uu):** The interface between UE and NG-RAN. + - NG:** The interface between NG-RAN and 5GC. +- Strata:** + - Non-Access Stratum:** The upper stratum in the UE and 5GC. + - Access Stratum:** The lower stratum in the UE, NG-RAN, and 5GC. + +Figure 5.2-1: NG and Uu user plane diagram showing protocol stacks for UE, NG-RAN, and 5GC. + +NOTE 1: The radio interface protocols are defined in TS 38.2xx and TS 38.3xx. + +NOTE 2: The NG interface protocols are defined in TS 38.41x. + +**Figure 5.2-1: NG and Uu user plane** + +## 5.3 Control plane + +Figure 5.3-1 shows the control plane (signalling) protocol stacks on NG and Uu interfaces. + +![Figure 5.3-1: NG and Uu control plane diagram showing protocol stacks for UE, NG-RAN, and 5GC.](c036e2540a94b31357ceb0002f0cacab_img.jpg) + +The diagram illustrates the control plane protocol stacks across three entities: UE, NG-RAN, and 5GC, separated by Radio (Uu) and NG interfaces. The stack is divided into Non-Access Stratum (NAS) and Access Stratum (AS). + +- UE:** Contains a NAS block with "CM, SM (3)" and an AS block with "Radio protocols (1)". +- NG-RAN:** Contains an AS block with two sub-components: "Radio protocols (1)" and "NG protocols (2)". +- 5GC:** Contains a NAS block with "CM, SM (3)" and an AS block with "NG protocols (2)". +- Interfaces:** + - Radio (Uu):** The interface between UE and NG-RAN. + - NG:** The interface between NG-RAN and 5GC. +- Strata:** + - Non-Access Stratum:** The upper stratum in the UE and 5GC. + - Access Stratum:** The lower stratum in the UE, NG-RAN, and 5GC. + +Figure 5.3-1: NG and Uu control plane diagram showing protocol stacks for UE, NG-RAN, and 5GC. + +NOTE 1: The radio interface protocols are defined in TS 38.2xx and TS 38.3xx. + +NOTE 2: The protocol is defined in TS 38.41x. (Description of NG interface). + +NOTE 3: CM, SM: This exemplifies a set of NAS control protocols between UE and 5GC. The evolution of the protocol architecture for these protocols is outside the scope of the present document. + +**Figure 5.3-1: NG and Uu control plane** + +NOTE: Both the Radio protocols and the NG protocols contain a mechanism to transparently transfer NAS messages. + +# 6 NG-RAN architecture + +## 6.1 Overview + +### 6.1.1 Overall Architecture of NG-RAN + +![Figure 6.1-1: Overall architecture diagram showing 5GC connected to NG-RAN via NG interfaces. NG-RAN contains gNBs, with one gNB connected to another via Xn-C, and a gNB-CU connected to two gNB-DUs via F1 interfaces.](9ae17964ddd9b814c7d905b1af2fddf2_img.jpg) + +The diagram illustrates the overall architecture of NG-RAN. At the top, a box labeled '5GC' is connected to the 'NG-RAN' box below it via two vertical lines labeled 'NG'. Inside the 'NG-RAN' box, there are two main components: a 'gNB' on the left and a 'gNB-CU' on the right. A horizontal line labeled 'Xn-C' connects the 'gNB' on the left to the 'gNB-CU' on the right. Below the 'gNB-CU', there are two boxes labeled 'gNB-DU'. Vertical lines labeled 'F1' connect the 'gNB-CU' to each of the 'gNB-DU' boxes. + +Figure 6.1-1: Overall architecture diagram showing 5GC connected to NG-RAN via NG interfaces. NG-RAN contains gNBs, with one gNB connected to another via Xn-C, and a gNB-CU connected to two gNB-DUs via F1 interfaces. + +**Figure 6.1-1: Overall architecture** + +The NG-RAN consists of a set of gNBs connected to the 5GC through the NG interface. + +**NOTE:** As specified in TS 38.300 [2], NG-RAN could also consist of a set of ng-eNBs, an ng-eNB may consist of an ng-eNB-CU and one or more ng-eNB-DU(s). An ng-eNB-CU and an ng-eNB-DU is connected via W1 interface. The general principle described in this clause also applies to ng-eNB and W1 interface, if not explicitly specified otherwise. + +An gNB can support FDD mode, TDD mode or dual mode operation. + +gNBs can be interconnected through the Xn interface. + +A gNB may consist of a gNB-CU and one or more gNB-DU(s). A gNB-CU and a gNB-DU is connected via F1 interface. + +One gNB-DU is connected to only one gNB-CU. + +**NOTE:** In case of network sharing with multiple cell ID broadcast, each Cell Identity associated with a subset of PLMNs corresponds to a gNB-DU and the gNB-CU it is connected to, i.e. the corresponding gNB-DUs share the same physical layer cell resources. + +**NOTE:** For resiliency, a gNB-DU may be connected to multiple gNB-CUs by appropriate implementation. + +NG, Xn and F1 are logical interfaces. + +For NG-RAN, the NG and Xn-C interfaces for a gNB consisting of a gNB-CU and gNB-DUs, terminate in the gNB-CU. For EN-DC, the S1-U and X2-C interfaces for a gNB consisting of a gNB-CU and gNB-DUs, terminate in the gNB-CU. The gNB-CU and connected gNB-DUs are only visible to other gNBs and the 5GC as a gNB. A possible deployment scenario is described in Annex A. + +The node hosting user plane part of NR PDCP (e.g. gNB-CU, gNB-CU-UP, and for EN-DC, MeNB or SgNB depending on the bearer split) shall perform user inactivity monitoring and further informs its inactivity or (re)activation to the node having C-plane connection towards the core network (e.g. over E1, X2). The node hosting NR RLC (e.g. + +gNB-DU) may perform user inactivity monitoring and further inform its inactivity or (re)activation to the node hosting control plane, e.g. gNB-CU or gNB-CU-CP. + +UL PDCP configuration (i.e. how the UE uses the UL at the assisting node) is indicated via X2-C (for EN-DC), Xn-C (for NG-RAN) and F1-C. Radio Link Outage/Resume for DL and/or UL is indicated via X2-U (for EN-DC), Xn-U (for NG-RAN) and F1-U. + +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, is defined as part of the RNL. + +For each NG-RAN interface (NG, Xn, F1) the related TNL protocol and the functionality are specified. The TNL provides services for user plane transport, signalling transport. + +In NG-Flex configuration, each NG-RAN node is connected to all AMFs of AMF Sets within an AMF Region supporting at least one slice also supported by the NG-RAN node. The AMF Set and the AMF Region are defined in TS 23.501 [3]. + +If security protection for control plane and user plane data on TNL of NG-RAN interfaces has to be supported, NDS/IP TS 33.501 [13] shall be applied. + +### 6.1.2 Overall architecture for separation of gNB-CU-CP and gNB-CU-UP + +The overall architecture for separation of gNB-CU-CP and gNB-CU-UP is depicted in Figure 6.1.2-1. + +NOTE: NG-RAN could also consist of a set of ng-eNBs, an ng-eNB may consist of an ng-eNB-CU-CP, one or more ng-eNB-CU-UP(s), and one or more ng-eNB-DU(s). An ng-eNB-CU-CP and an ng-eNB-CU-UP is connected via the E1 interface. An ng-eNB-DU is connected to an ng-eNB-CU-CP via the F1-C interface, and to an ng-eNB-CU-UP via the F1-U interface. The general principle described in this clause also applies to ng-eNB and its corresponding E1 and F1 interfaces, if not explicitly specified otherwise. + +![Diagram of the overall architecture for separation of gNB-CU-CP and gNB-CU-UP. A dashed box labeled 'gNB' contains a 'gNB-CU-CP' block, multiple 'gNB-CU-UP' blocks (stacked), and two 'gNB-DU' blocks. The 'gNB-CU-CP' is connected to the 'gNB-CU-UP' blocks via an 'E1' interface. The 'gNB-CU-CP' is also connected to the 'gNB-DU' blocks via 'F1-C' interfaces. The 'gNB-CU-UP' blocks are connected to the 'gNB-DU' blocks via 'F1-U' interfaces. The connections are shown as lines: solid lines for E1 and F1-C, and dashed lines for F1-U.](2de714cedbbdd36f901f71bafa78f75a_img.jpg) + +Diagram of the overall architecture for separation of gNB-CU-CP and gNB-CU-UP. A dashed box labeled 'gNB' contains a 'gNB-CU-CP' block, multiple 'gNB-CU-UP' blocks (stacked), and two 'gNB-DU' blocks. The 'gNB-CU-CP' is connected to the 'gNB-CU-UP' blocks via an 'E1' interface. The 'gNB-CU-CP' is also connected to the 'gNB-DU' blocks via 'F1-C' interfaces. The 'gNB-CU-UP' blocks are connected to the 'gNB-DU' blocks via 'F1-U' interfaces. The connections are shown as lines: solid lines for E1 and F1-C, and dashed lines for F1-U. + +**Figure 6.1.2-1. Overall architecture for separation of gNB-CU-CP and gNB-CU-UP** + +- A gNB may consist of a gNB-CU-CP, multiple gNB-CU-UPs and multiple gNB-DUs; +- The gNB-CU-CP is connected to the gNB-DU through the F1-C interface; +- The gNB-CU-UP is connected to the gNB-DU through the F1-U interface; +- The gNB-CU-UP is connected to the gNB-CU-CP through the E1 interface; +- One gNB-DU is connected to only one gNB-CU-CP; +- One gNB-CU-UP is connected to only one gNB-CU-CP; + +NOTE 1: For resiliency, a gNB-DU and/or a gNB-CU-UP may be connected to multiple gNB-CU-CPs by appropriate implementation. + +- One gNB-DU can be connected to multiple gNB-CU-UPs under the control of the same gNB-CU-CP; + +- One gNB-CU-UP can be connected to multiple DUs under the control of the same gNB-CU-CP; + +NOTE 2: The connectivity between a gNB-CU-UP and a gNB-DU is established by the gNB-CU-CP using Bearer Context Management functions. + +NOTE 3: The gNB-CU-CP selects the appropriate gNB-CU-UP(s) for the requested services for the UE. In case of multiple CU-UPs they belong to same security domain as defined in TS 33.210 [18]. + +NOTE 4: Data forwarding between gNB-CU-UPs during intra-gNB-CU-CP handover within a gNB may be supported by Xn-U. + +### 6.1.3 Overall Architecture of IAB + +![Figure 6.1.3-1: Overall architecture of IAB. The diagram shows the hierarchy of an IAB network. At the top is the 5GC (5G Core). Below it, a gNB (Base Station) and an IAB-donor are connected via NG interfaces. The gNB is connected to the IAB-donor via an Xn-C interface. The IAB-donor contains an IAB-donor-CU (Central Unit) and an IAB-donor-DU (Distributed Unit) connected by an F1 interface. The IAB-donor-DU is connected to an IAB-node via an NR Uu interface. This IAB-node is connected to another IAB-node via another NR Uu interface. The second IAB-node is connected to the IAB-donor-CU via an F1 interface. The entire NG RAN (Radio Access Network) is shown as a large box containing the gNB, IAB-donor, and the two IAB-nodes.](43837b056625d3d6ce615e4c02f163bb_img.jpg) + +Figure 6.1.3-1: Overall architecture of IAB. The diagram shows the hierarchy of an IAB network. At the top is the 5GC (5G Core). Below it, a gNB (Base Station) and an IAB-donor are connected via NG interfaces. The gNB is connected to the IAB-donor via an Xn-C interface. The IAB-donor contains an IAB-donor-CU (Central Unit) and an IAB-donor-DU (Distributed Unit) connected by an F1 interface. The IAB-donor-DU is connected to an IAB-node via an NR Uu interface. This IAB-node is connected to another IAB-node via another NR Uu interface. The second IAB-node is connected to the IAB-donor-CU via an F1 interface. The entire NG RAN (Radio Access Network) is shown as a large box containing the gNB, IAB-donor, and the two IAB-nodes. + +**Figure 6.1.3-1: Overall architecture of IAB** + +The NG-RAN supports IAB by the IAB-node wirelessly connecting to the gNB capable of serving the IAB-nodes, named IAB-donor. + +The IAB-donor consists of an IAB-donor-CU and one or more IAB-donor-DU(s). In case of separation of gNB-CU-CP and gNB-CU-UP, the IAB-donor may consist of an IAB-donor-CU-CP, multiple IAB-donor-CU-UPs and multiple IAB-donor-DUs. + +The IAB-node connects to an upstream IAB-node or an IAB-donor-DU via a subset of the UE functionalities of the NR Uu interface (named IAB-MT function of IAB-node). The IAB-node provides wireless backhaul to the downstream IAB-nodes and UEs via the network functionalities of the NR Uu interface (named IAB-DU function of IAB-node). + +The F1-C traffic between an IAB-node and IAB-donor-CU is backhauled via the IAB-donor-DU and the optional intermediate hop IAB-node(s). + +The F1-U traffic between an IAB-node and IAB-donor-CU is backhauled via the IAB-donor-DU and the optional intermediate hop IAB-node(s). + +All functions specified for a gNB-DU are equally applicable for an IAB-DU and IAB-donor-DU, unless otherwise stated, and all functions specified for a gNB-CU are equally applicable for an IAB-donor-CU, unless otherwise stated. All functions specified for the UE context are equally applicable for managing the context of IAB-MT, unless otherwise stated. + +### 6.1.4 Protocol stacks of IAB + +Figure 6.1.4-1 shows the protocol stack for F1-U between IAB-DU and the IAB-donor-CU-UP, and Figure 6.1.4-2 shows the protocol stack for F1-C between IAB-DU and the IAB-donor-CU-CP. In these example figures, F1-U and F1-C traffic are carried over two backhaul hops. + +NOTE: F1 needs to be security-protected as described in TS 33.501. The security layer is not shown in the Figure 6.1.4-1, Figure 6.1.4-2 and Figure 6.1.4-3. + +![Figure 6.1.4-1: Protocol stack for F1-U of IAB. This diagram illustrates the protocol layers for User Plane (F1-U) traffic across four entities: IAB-node 2, IAB-node 1, IAB-donor-DU, and IAB-donor-CU-UP. IAB-node 2 and IAB-node 1 each contain an IAB-DU and an IAB-MT. F1-U traffic originates in the IAB-DU of IAB-node 2, passing through IP, UDP, and GTP-U layers. It then traverses the backhaul (BH) RLC channel between the IAB-MT of IAB-node 2 and the IAB-DU of IAB-node 1. At IAB-node 1, the traffic passes through the IAB-MT's RLC, MAC, and PHY layers, then through the IAB-DU's BAP, RLC, MAC, and PHY layers. It continues across another BH RLC channel to the IAB-donor-DU. In the IAB-donor-DU, the traffic goes through the PHY, MAC, RLC, and BAP layers, then enters the intra-donor F1 section where it passes through two IP layers and an L2 layer. Finally, it reaches the IAB-donor-CU-UP, passing through the L2, L1, IP, UDP, and GTP-U layers.](77464a47f104d0d647b2414591137b64_img.jpg) + +Figure 6.1.4-1: Protocol stack for F1-U of IAB. This diagram illustrates the protocol layers for User Plane (F1-U) traffic across four entities: IAB-node 2, IAB-node 1, IAB-donor-DU, and IAB-donor-CU-UP. IAB-node 2 and IAB-node 1 each contain an IAB-DU and an IAB-MT. F1-U traffic originates in the IAB-DU of IAB-node 2, passing through IP, UDP, and GTP-U layers. It then traverses the backhaul (BH) RLC channel between the IAB-MT of IAB-node 2 and the IAB-DU of IAB-node 1. At IAB-node 1, the traffic passes through the IAB-MT's RLC, MAC, and PHY layers, then through the IAB-DU's BAP, RLC, MAC, and PHY layers. It continues across another BH RLC channel to the IAB-donor-DU. In the IAB-donor-DU, the traffic goes through the PHY, MAC, RLC, and BAP layers, then enters the intra-donor F1 section where it passes through two IP layers and an L2 layer. Finally, it reaches the IAB-donor-CU-UP, passing through the L2, L1, IP, UDP, and GTP-U layers. + +Figure 6.1.4-1: Protocol stack for F1-U of IAB + +![Figure 6.1.4-2: Protocol stack for F1-C of IAB. This diagram illustrates the protocol layers for Control Plane (F1-C) traffic across the same four entities: IAB-node 2, IAB-node 1, IAB-donor-DU, and IAB-donor-CU-CP. F1-C traffic originates in the IAB-DU of IAB-node 2, passing through IP, SCTP, and F1AP layers. It then traverses the BH RLC channel between the IAB-MT of IAB-node 2 and the IAB-DU of IAB-node 1. At IAB-node 1, the traffic passes through the IAB-MT's RLC, MAC, and PHY layers, then through the IAB-DU's BAP, RLC, MAC, and PHY layers. It continues across another BH RLC channel to the IAB-donor-DU. In the IAB-donor-DU, the traffic goes through the PHY, MAC, RLC, and BAP layers, then enters the intra-donor F1 section where it passes through two IP layers and an L2 layer. Finally, it reaches the IAB-donor-CU-CP, passing through the L2, L1, IP, SCTP, and F1AP layers.](3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg) + +Figure 6.1.4-2: Protocol stack for F1-C of IAB. This diagram illustrates the protocol layers for Control Plane (F1-C) traffic across the same four entities: IAB-node 2, IAB-node 1, IAB-donor-DU, and IAB-donor-CU-CP. F1-C traffic originates in the IAB-DU of IAB-node 2, passing through IP, SCTP, and F1AP layers. It then traverses the BH RLC channel between the IAB-MT of IAB-node 2 and the IAB-DU of IAB-node 1. At IAB-node 1, the traffic passes through the IAB-MT's RLC, MAC, and PHY layers, then through the IAB-DU's BAP, RLC, MAC, and PHY layers. It continues across another BH RLC channel to the IAB-donor-DU. In the IAB-donor-DU, the traffic goes through the PHY, MAC, RLC, and BAP layers, then enters the intra-donor F1 section where it passes through two IP layers and an L2 layer. Finally, it reaches the IAB-donor-CU-CP, passing through the L2, L1, IP, SCTP, and F1AP layers. + +Figure 6.1.4-2: Protocol stack for F1-C of IAB + +Figure 6.1.4-3 shows the protocol stack for F1-C between IAB-DU and the IAB-donor-CU-CP, when the F1-C traffic is exchanged via the MeNB. + +![Protocol stack diagram for IAB F1-C traffic exchanged via the MeNB. It shows three main entities: IAB-node (split into IAB-DU and IAB-MT), MeNB, and IAB-donor-CU-CP. The IAB-DU contains F1AP, SCTP, IP, LTE RRC, LTE PDCP, LTE RLC, LTE MAC, and LTE PHY. The IAB-MT contains LTE RRC, LTE PDCP, LTE RLC, LTE MAC, and LTE PHY. The MeNB contains LTE RRC, X2AP, SCTP, IP, LTE MAC, L2, and L1. The IAB-donor-CU-CP contains F1AP, SCTP, IP, X2AP, SCTP, IP, L2, and L1. Connections are shown between the IAB-DU and MeNB via LTE-Uu, and between the MeNB and IAB-donor-CU-CP via X2-C.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +Protocol stack diagram for IAB F1-C traffic exchanged via the MeNB. It shows three main entities: IAB-node (split into IAB-DU and IAB-MT), MeNB, and IAB-donor-CU-CP. The IAB-DU contains F1AP, SCTP, IP, LTE RRC, LTE PDCP, LTE RLC, LTE MAC, and LTE PHY. The IAB-MT contains LTE RRC, LTE PDCP, LTE RLC, LTE MAC, and LTE PHY. The MeNB contains LTE RRC, X2AP, SCTP, IP, LTE MAC, L2, and L1. The IAB-donor-CU-CP contains F1AP, SCTP, IP, X2AP, SCTP, IP, L2, and L1. Connections are shown between the IAB-DU and MeNB via LTE-Uu, and between the MeNB and IAB-donor-CU-CP via X2-C. + +**Fig. 6.1.4-3: Protocol stack for IAB F1-C traffic exchanged via the MeNB** + +Figure 6.1.4-4 shows the protocol stack for F1-C between IAB-DU and the IAB-donor-CU-CP, when the F1-C traffic is exchanged via the MgNB. + +![Protocol stack diagram for IAB F1-C traffic exchanged via the MgNB. It shows three main entities: IAB-node (split into IAB-DU and IAB-MT), MgNB, and IAB-donor-CU-CP. The IAB-DU contains F1AP, SCTP, IP, NR RRC, NR PDCP, NR RLC, NR MAC, and NR PHY. The IAB-MT contains NR RRC, NR PDCP, NR RLC, NR MAC, and NR PHY. The MgNB contains NR RRC, XnAP, SCTP, IP, NR MAC, L2, and L1. The IAB-donor-CU-CP contains F1AP, SCTP, IP, XnAP, SCTP, IP, L2, and L1. Connections are shown between the IAB-DU and MgNB via NR-Uu, and between the MgNB and IAB-donor-CU-CP via Xn-C.](a734898ce18e972938949637c32a34f4_img.jpg) + +Protocol stack diagram for IAB F1-C traffic exchanged via the MgNB. It shows three main entities: IAB-node (split into IAB-DU and IAB-MT), MgNB, and IAB-donor-CU-CP. The IAB-DU contains F1AP, SCTP, IP, NR RRC, NR PDCP, NR RLC, NR MAC, and NR PHY. The IAB-MT contains NR RRC, NR PDCP, NR RLC, NR MAC, and NR PHY. The MgNB contains NR RRC, XnAP, SCTP, IP, NR MAC, L2, and L1. The IAB-donor-CU-CP contains F1AP, SCTP, IP, XnAP, SCTP, IP, L2, and L1. Connections are shown between the IAB-DU and MgNB via NR-Uu, and between the MgNB and IAB-donor-CU-CP via Xn-C. + +**Fig. 6.1.4-4: Protocol stack for IAB F1-C traffic exchanged via the MgNB** + +Figure 6.1.4-5 shows the protocol stack for F1-C between IAB-DU and the IAB-donor-CU-CP, when the F1-C traffic is exchanged via the SgNB. + +![Figure 6.1.4-5: Protocol stack for IAB F1-C traffic exchanged via the SgNB. The diagram shows three main entities: IAB-node (consisting of IAB-DU and IAB-MT), SgNB, and IAB-donor-CU-CP. The IAB-DU contains layers F1AP, SCTP, IP, NR RRC, NR PDCP, NR RLC, NR MAC, and NR PHY. The IAB-MT contains layers NR RRC, NR PDCP, NR RLC, NR MAC, and NR PHY. The SgNB contains layers NR RLC, XnAP, NR MAC, SCTP, NR PHY, IP, L2, and L1. The IAB-donor-CU-CP contains layers F1AP, SCTP, IP, NR RRC, NR PDCP, XnAP, SCTP, IP, L2, and L1. Connections are shown between the IAB-DU and SgNB via the NR-Uu interface, and between the SgNB and IAB-donor-CU-CP via the Xn-C interface. The F1-C traffic path is highlighted, showing the flow of F1AP messages from the IAB-DU through the SgNB to the IAB-donor-CU-CP.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +Figure 6.1.4-5: Protocol stack for IAB F1-C traffic exchanged via the SgNB. The diagram shows three main entities: IAB-node (consisting of IAB-DU and IAB-MT), SgNB, and IAB-donor-CU-CP. The IAB-DU contains layers F1AP, SCTP, IP, NR RRC, NR PDCP, NR RLC, NR MAC, and NR PHY. The IAB-MT contains layers NR RRC, NR PDCP, NR RLC, NR MAC, and NR PHY. The SgNB contains layers NR RLC, XnAP, NR MAC, SCTP, NR PHY, IP, L2, and L1. The IAB-donor-CU-CP contains layers F1AP, SCTP, IP, NR RRC, NR PDCP, XnAP, SCTP, IP, L2, and L1. Connections are shown between the IAB-DU and SgNB via the NR-Uu interface, and between the SgNB and IAB-donor-CU-CP via the Xn-C interface. The F1-C traffic path is highlighted, showing the flow of F1AP messages from the IAB-DU through the SgNB to the IAB-donor-CU-CP. + +Fig. 6.1.4-5: Protocol stack for IAB F1-C traffic exchanged via the SgNB + +### 6.1.5 Overall Architecture of NR MBS + +The overall architecture specified in clause 6.1.1 and 6.1.2 applies for NR MBS. + +Upon establishment of a MBS Session resource by the 5GC, the gNB-CU triggers the establishment of MRBs, involving the gNB-DU. If E1 is deployed, the gNB-CU-CP triggers establishment of respective MBS UP resources in the gNB-CU-UP. + +The gNB-DU assigns the G-RNTI. + +A shared F1-U tunnel is used between the gNB-CU and the gNB-DU for MRB with PTM transmission. UE dedicated F1-U tunnels are used between the gNB-CU and the gNB-DU for data transmission of PTP retransmission and PTP forwarding of an MRB. For an MRB configured with PTP only transmission either a shared F1-U or a UE dedicated F1-U tunnel is used, dependent on the lower layer configuration. The gNB-DU assigns the DL GTP-U TEID and provides it to the gNB-CU. If E1 is deployed the gNB-CU-CP forwards it to the gNB-CU-UP. + +For both broadcast and multicast, DL flow control maybe used for the shared F1-U tunnel established for the MRB, as specified in TS 38.425 [24]. + +### 6.1.6 Protocol stacks of L2 UE-to-Network Relay + +The protocol stacks for the user plane and control plane of L2 U2N Relay architecture are described in Figure 6.1.6-1 and Figure 6.1.6-2, respectively. The Uu SRAP is terminated between U2N relay UE and gNB-DU. + +![Figure 6.1.6-1: User plane protocol stack for L2 UE-to-Network Relay. The diagram shows four entities: Remote UE, UE-to-Network Relay UE, gNB-DU, and gNB-CU(-UP). The Remote UE has layers Uu-SDAP, Uu-PDCP, PC5-SRAP, PC5-RLC, PC5-MAC, and PC5-PHY. The Relay UE has layers PC5-SRAP, PC5-RLC, PC5-MAC, PC5-PHY on the PC5 side, and Uu-SRAP, Uu-RLC, Uu-MAC, Uu-PHY on the Uu side. The gNB-DU has layers Uu-SRAP, Uu-RLC, Uu-MAC, Uu-PHY, GTP/UDP/IP, L2, and L1. The gNB-CU(-UP) has layers Uu-SDAP, Uu-PDCP, GTP/UDP/IP, L2, and L1. Connections are shown between the Remote UE and Relay UE (PC5), between the Relay UE and gNB-DU (Uu), and between the gNB-DU and gNB-CU(-UP) (F1).](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +Figure 6.1.6-1: User plane protocol stack for L2 UE-to-Network Relay. The diagram shows four entities: Remote UE, UE-to-Network Relay UE, gNB-DU, and gNB-CU(-UP). The Remote UE has layers Uu-SDAP, Uu-PDCP, PC5-SRAP, PC5-RLC, PC5-MAC, and PC5-PHY. The Relay UE has layers PC5-SRAP, PC5-RLC, PC5-MAC, PC5-PHY on the PC5 side, and Uu-SRAP, Uu-RLC, Uu-MAC, Uu-PHY on the Uu side. The gNB-DU has layers Uu-SRAP, Uu-RLC, Uu-MAC, Uu-PHY, GTP/UDP/IP, L2, and L1. The gNB-CU(-UP) has layers Uu-SDAP, Uu-PDCP, GTP/UDP/IP, L2, and L1. Connections are shown between the Remote UE and Relay UE (PC5), between the Relay UE and gNB-DU (Uu), and between the gNB-DU and gNB-CU(-UP) (F1). + +Figure 6.1.6-1: User plane protocol stack for L2 UE-to-Network Relay + +![Figure 6.1.6-2: Control plane protocol stack for L2 UE-to-Network Relay. The diagram shows four entities: Remote UE, UE-to-Network Relay UE, gNB-DU, and gNB-CU(-CP). The Remote UE has layers Uu-RRC, Uu-PDCP, PC5-SRAP, PC5-RLC, PC5-MAC, and PC5-PHY. The Relay UE has layers PC5-SRAP, PC5-RLC, PC5-MAC, PC5-PHY on the PC5 side, and Uu-SRAP, Uu-RLC, Uu-MAC, Uu-PHY on the Uu side. The gNB-DU has layers Uu-SRAP, Uu-RLC, Uu-MAC, Uu-PHY, SCTP/IP, L2, and L1. The gNB-CU(-CP) has layers Uu-RRC, Uu-PDCP, SCTP/IP, L2, and L1. Connections are shown between the Remote UE and Relay UE (PC5), between the Relay UE and gNB-DU (Uu), and between the gNB-DU and gNB-CU(-CP) (F1).](a24e89a6fe9bb70c83f8bf5202baba95_img.jpg) + +Figure 6.1.6-2: Control plane protocol stack for L2 UE-to-Network Relay. The diagram shows four entities: Remote UE, UE-to-Network Relay UE, gNB-DU, and gNB-CU(-CP). The Remote UE has layers Uu-RRC, Uu-PDCP, PC5-SRAP, PC5-RLC, PC5-MAC, and PC5-PHY. The Relay UE has layers PC5-SRAP, PC5-RLC, PC5-MAC, PC5-PHY on the PC5 side, and Uu-SRAP, Uu-RLC, Uu-MAC, Uu-PHY on the Uu side. The gNB-DU has layers Uu-SRAP, Uu-RLC, Uu-MAC, Uu-PHY, SCTP/IP, L2, and L1. The gNB-CU(-CP) has layers Uu-RRC, Uu-PDCP, SCTP/IP, L2, and L1. Connections are shown between the Remote UE and Relay UE (PC5), between the Relay UE and gNB-DU (Uu), and between the gNB-DU and gNB-CU(-CP) (F1). + +Figure 6.1.6-2: Control plane protocol stack for L2 UE-to-Network Relay + +## 6.2 NG-RAN identifiers + +### 6.2.1 Principle of handling Application Protocol Identities + +An Application Protocol Identity (AP ID) is allocated when a new UE-associated logical connection is created in either an NG-RAN node or an AMF. An AP ID shall uniquely identify a logical connection associated to a UE over the NG interface or Xn interface within a node (NG-RAN node or AMF) or over the F1 interface or over the E1 interface or over the W1 interface. Upon receipt of a message that has a new AP ID from the sending node, the receiving node shall store the AP ID of the sending node for the duration of the logical connection. The receiving node shall assign the AP ID to be used to identify the logical connection associated to the UE and include it as well as the previously received new AP ID from the sending node, in the first returned message to the sending node. In all subsequent messages to and from sending node, both AP IDs of sending node and receiving node shall be included. For MBS-associated logical connections of the E1 interface and the F1 interface the same principles for AP IDs apply as for UE-associated logical connections. + +The definitions of AP IDs as used on NG interface or Xn interface or F1 interface or E1 interface are shown below: + +**RAN UE NGAP ID:** + +A RAN UE NGAP ID shall be allocated so as to uniquely identify the UE over the NG interface within an gNB. When an AMF receives an RAN UE NGAP ID it shall store it for the duration of the UE-associated logical NG-connection for this UE. Once known to an AMF this is included in all UE associated NGAP signalling. + +The RAN UE NGAP ID shall be unique within the logical NG-RAN node. + +#### **AMF UE NGAP ID:** + +An AMF UE NGAP ID shall be allocated so as to uniquely identify the UE over the NG interface within the AMF. When a NG-RAN node receives an AMF UE NGAP ID it shall store it for the duration of the UE-associated logical NG-connection for this UE. Once known to a NG-RAN node this ID is included in all UE associated NGAP signalling. + +The AMF UE NGAP ID shall be unique within an AMF Set as specified in TS 23.501 [3]. + +##### **Old NG-RAN node UE XnAP ID:** + +An Old NG-RAN node UE XnAP ID shall be allocated so as to uniquely identify the UE over the Xn interface within a source NG-RAN node. When a target NG-RAN node receives an Old NG-RAN node UE XnAP ID it shall store it for the duration of the UE-associated logical Xn-connection for this UE. Once known to a target NG-RAN node this ID is included in all UE associated XnAP signalling. The Old NG-RAN node UE XnAP ID shall be unique within the logical NG-RAN node. + +##### **New NG-RAN node UE XnAP ID:** + +A New NG-RAN node UE XnAP ID shall be allocated so as to uniquely identify the UE over the Xn interface within a target NG-RAN node. When a source NG-RAN node receives a New NG-RAN node UE XnAP ID it shall store it for the duration of the UE-associated logical Xn-connection for this UE. Once known to a source NG-RAN node this ID is included in all UE associated XnAP signalling. The New NG-RAN node UE XnAP ID shall be unique within the logical NG-RAN node. + +##### **M-NG-RAN node UE XnAP ID:** + +An M-NG-RAN node UE XnAP ID shall be allocated so as to uniquely identify the UE over the Xn interface within an M-NG-RAN node for dual connectivity. When an S-NG-RAN node receives an M-NG-RAN node UE XnAP ID it shall store it for the duration of the UE-associated logical Xn-connection for this UE. Once known to an S-NG-RAN node this ID is included in all UE associated XnAP signalling. The M-NG-RAN node UE XnAP ID shall be unique within the logical NG-RAN node. + +##### **S-NG-RAN node UE XnAP ID:** + +A S-NG-RAN node UE XnAP ID shall be allocated so as to uniquely identify the UE over the Xn interface within an S-NG-RAN node for dual connectivity. When an M-NG-RAN node receives a S-NG-RAN node UE XnAP ID it shall store it for the duration of the UE-associated logical Xn-connection for this UE. Once known to an M-NG-RAN node this ID is included in all UE associated XnAP signalling. The S-NG-RAN node UE XnAP ID shall be unique within the logical NG-RAN node. + +##### **gNB-CU UE F1AP ID:** + +A gNB-CU UE F1AP ID shall be allocated so as to uniquely identify the UE over the F1 interface within a gNB-CU. When a gNB-DU receives a gNB-CU UE F1AP ID it shall store it for the duration of the UE-associated logical F1-connection for this UE. The gNB-CU UE F1AP ID shall be unique within the gNB-CU logical node. + +##### **gNB-DU UE F1AP ID:** + +A gNB-DU UE F1AP ID shall be allocated so as to uniquely identify the UE over the F1 interface within a gNB-DU. When a gNB-CU receives a gNB-DU UE F1AP ID it shall store it for the duration of the UE-associated logical F1-connection for this UE. The gNB-DU UE F1AP ID shall be unique within the gNB-DU logical node. + +##### **gNB-CU-CP UE E1AP ID:** + +A gNB-CU-CP UE E1AP ID shall be allocated so as to uniquely identify the UE over the E1 interface within a gNB-CU-CP (respectively an ng-eNB-CU-CP, or an eNB-CP as defined in TS 36.401[28]). When a gNB-CU-UP (respectively an ng-eNB-CU-UP, or an eNB-UP as defined in TS 36.401[28]) receives a gNB-CU-CP UE E1AP ID it shall store it for the duration of the UE-associated logical E1-connection for this UE. The gNB-CU- + +CP UE E1AP ID shall be unique within the gNB-CU-CP (respectively the ng-eNB-CU-CP, or the eNB-CP as defined in TS 36.401[28]) logical node. + +##### **gNB-CU-UP UE E1AP ID:** + +A gNB-CU-UP UE E1AP ID shall be allocated so as to uniquely identify the UE over the E1 interface within a gNB-CU-UP (respectively an ng-eNB-CU-UP, or an eNB-UP as defined in TS 36.401[28]). When a gNB-CU-CP (respectively an ng-eNB-CU-CP, or an eNB-CP as defined in TS 36.401[28]) receives a gNB-CU-UP UE E1AP ID it shall store it for the duration of the UE-associated logical E1-connection for this UE. The gNB-CU-UP UE E1AP ID shall be unique within the gNB-CU-UP (respectively the ng-eNB-CU-UP, or the eNB-UP as defined in TS 36.401[28]) logical node. + +##### **ng-eNB-CU UE W1AP ID:** + +An ng-eNB-CU UE W1AP ID shall be allocated so as to uniquely identify the UE over the W1 interface within an ng-eNB-CU. When an ng-eNB-DU receives an ng-eNB-CU UE W1AP ID it shall store it for the duration of the UE-associated logical W1-connection for this UE. The ng-eNB-CU UE W1AP ID shall be unique within the ng-eNB-CU logical node. + +##### **ng-eNB-DU UE W1AP ID:** + +An ng-eNB-DU UE W1AP ID shall be allocated so as to uniquely identify the UE over the W1 interface within an ng-eNB-DU. When an ng-eNB-CU receives an ng-eNB-DU UE W1AP ID it shall store it for the duration of the UE-associated logical W1-connection for this UE. The ng-eNB-DU UE W1AP ID shall be unique within the ng-eNB-DU logical node. + +##### **gNB-CU MBS F1AP ID:** + +A gNB-CU MBS F1AP ID shall be allocated so as to uniquely identify the MBS Session Context over the F1 interface within a gNB-CU. When a gNB-DU receives a gNB-CU MBS F1AP ID it shall store it for the duration of the MBS-associated logical F1-connection for that MBS Session. The gNB-CU MBS F1AP ID shall be unique within the gNB-CU logical node. + +##### **gNB-DU MBS F1AP ID:** + +A gNB-DU MBS F1AP ID shall be allocated so as to uniquely identify the MBS Session Context over the F1 interface within a gNB-DU. When a gNB-CU receives a gNB-DU MBS F1AP ID it shall store it for the duration of the MBS-associated logical F1-connection for this MBS Session. The gNB-DU MBS F1AP ID shall be unique within the gNB-DU logical node. + +#### **gNB-CU-CP MBS E1AP ID:** + +A gNB-CU-CP MBS E1AP ID shall be allocated so as to uniquely identify the MBS Session Context over the E1 interface within a gNB-CU-CP. When a gNB-CU-UP receives a gNB-CU-CP MBS E1AP ID it shall store it for the duration of the MBS-associated logical E1-connection for that MBS Session. The gNB-CU-CP MBS E1AP ID shall be unique within the gNB-CU-CP logical node. + +#### **gNB-CU-UP MBS E1AP ID:** + +A gNB-CU-UP MBS E1AP ID shall be allocated so as to uniquely identify the MBS Session Context over the E1 interface within a gNB-CU-UP. When a gNB-CU-CP receives a gNB-CU-UP MBS E1AP ID it shall store it for the duration of the MBS-associated logical E1-connection for this MBS Session. The gNB-CU-UP MBS E1AP ID shall be unique within the gNB-CU-UP logical node. + +### **6.2.2 gNB-DU ID** + +The gNB-DU ID is configured at the gNB-DU and used to uniquely identify the gNB-DU at least within a gNB-CU. + +### **6.2.3 ng-eNB-DU ID** + +The ng-eNB-DU ID is configured at the ng-eNB-DU and used to uniquely identify the ng-eNB-DU at least within an ng-eNB-CU. The ng-eNB-DU provides its ng-eNB-DU ID to the ng-eNB-CU during the W1 Setup procedure. The ng-eNB-DU ID is used only within W1AP procedures. + +### 6.2.4 gNB-CU-UP ID + +The gNB-CU-UP ID is configured at the gNB-CU-CP and used to uniquely identify the gNB-CU-UP at least within a gNB-CU-CP. The gNB-CU-UP provides its gNB-CU-UP ID to the gNB-CU-CP during the E1 Setup procedure. The gNB-CP-UP ID is used only within E1AP procedures. + +NOTE 1: This identity is also used to uniquely identify the ng-eNB-CU-UP at least within an ng-eNB-CU-CP in case CP/UP separation is implemented in ng-eNB. + +NOTE 2: This identity is also used to uniquely identify the eNB at least within an eNB-CP in case CP/UP separation is implemented in eNB. + +### 6.2.5 RAN UE ID + +The RAN UE ID is an identifier allocated to a UE by the gNB-DU during UE Initial Access or by the gNB-CU during UE Context Setup. It is transferred over E1 and F1 interface, in order to do correlation of data for a given UE in case of disaggregated gNB deployment. The RAN UE ID is unique within a gNB. + +## 6.3 Transport addresses + +The transport layer address parameter is transported in the radio network application signalling procedures that result in establishment of transport bearer connections. + +The transport layer address parameter shall not be interpreted in the radio network application protocols and reveal the addressing format used in the transport layer. + +The formats of the transport layer addresses are further described in TS 38.414 [5], TS 38.424 [6] and TS 38.474 [7]. + +## 6.4 UE associations in NG-RAN Node + +There are several types of UE associations needed in the NG-RAN node: the "NG-RAN node UE context" used to store all information needed for a UE and the associations between the UE and the logical NG and Xn connections used for NG/XnAP UE associated messages. An "NG-RAN node UE context" exists for a UE in CM\_CONNECTED. + +### Definitions: + +### **NG-RAN node UE context:–** + +An NG-RAN node UE context is a block of information in an NG-RAN node associated to one UE. The block of information contains the necessary information required to maintain the NG-RAN services towards the active UE. An NG-RAN node UE context is established when the transition to RRC CONNECTED for a UE is completed or in the target NG-RAN node after completion of handover resource allocation during handover preparation, in which case at least UE state information, security information, UE capability information and the identities of the UE-associated logical NG-connection shall be included in the NG-RAN node UE context. + +For Dual Connectivity an NG-RAN node UE context is also established in the S-NG-RAN node after completion of S-NG-RAN node Addition Preparation procedure. + +If radio bearers are requested to be setup during a UE Context setup or modification procedure, the UE capabilities are signalled to the receiving node as part of the UE context setup or modification procedures. + +#### **Bearer context:** + +A bearer context is a block of information in a gNB-CU-UP node associated to one UE that is used for the sake of communication over the E1 interface. It may include the information about data radio bearers, PDU sessions and QoS-flows associated to the UE. The block of information contains the necessary information required to maintain user-plane services toward the UE. + +### **UE-associated logical NG/Xn/F1/E1-connection:** + +NGAP, XnAP, F1AP and E1AP provide means to exchange control plane messages associated with the UE over the respectively NG-C, Xn-C, F1-C or E1 interface. + +A UE-associated logical connection is established during the first NGAP/XnAP/F1AP message exchange between the NG/Xn/F1 peer nodes. + +The connection is maintained as long as UE associated NG/XnAP/F1AP messages need to be exchanged over the NG/Xn/F1 interface. + +The UE-associated logical NG-connection uses the identities AMF UE NGAP ID and RAN UE NGAP ID. + +The UE-associated logical Xn-connection uses the identities Old NG-RAN node UE XnAP ID and New NG-RAN node UE XnAP ID, or M-NG-RAN node UE XnAP ID and S-NG-RAN node UE XnAP ID. + +The UE-associated logical F1-connection uses the identities gNB-CU UE F1AP ID and gNB-DU UE F1AP ID. + +The UE-associated logical E1-connection uses the identities gNB-CU-CP UE E1AP ID and gNB-CU-UP UE E1AP ID. + +When a node (AMF or gNB) receives a UE associated NGAP/XnAP/F1AP/E1AP message the node retrieves the associated UE based on the NGAP/XnAP/F1AP/E1AP ID. + +### **UE-associated signalling:** + +UE-associated signalling is an exchange of NGAP/XnAP/F1AP/E1AP messages associated with one UE over the UE-associated logical NG/Xn/F1/E1-connection. + +- NOTE1: The UE-associated logical NG-connection may exist before the NG-RAN node UE context is setup in the NG-RAN node. +- NOTE2: The UE-associated logical F1-connection may exist before the UE context is setup in the gNB-DU. +- NOTE3: The general principle described in this clause also applies to ng-eNB and W1/E1 interface, if not explicitly specified otherwise. + +## **6.5 MBS Session associations in NG-RAN Node** + +The following MBS Session associations are defined in the NG-RAN node to support NR MBS: + +**NG-RAN MBS session resource context:** Encompasses CP and UP, transport and radio resources to support an MBS Session. For multicast it also encompasses the MBS Session state (active, de-activated) and information about joined UEs. If an MBS session resource within a gNB serves multiple MBS service areas, as specified in TS 23.247 [27] the same NG RAN MBS session resource context may be associated with multiple NG-U resources. For a multicast MBS session, NG-U resources are setup or released by the gNB upon UE mobility or UEs leaving or joining the multicast MBS session. + +### **MBS Session context in a gNB-DU:** + +The definition of an MBS Session context in a gNB-DU applicable for broadcast and multicast. + +An MBS Session context in a gNB-DU + +- is a block of information associated to an MBS Session, which may consist of one or several MRB Contexts; +- corresponds to either one or several F1-U tunnels. + +### **MRB Context in a gNB-DU:** + +An MRB Context is a block of information in a gNB-DU associated to an MRB (MRB “instance”). The gNB-DU sets up resources for each MRB Context in a gNB-DU associated to an MBS Session context + +- based on information provided within MBS Session Context related information as received by the gNB-DU (e.g. MRB QoS, MBS service area information, etc.), and, +- for multicast, based on the UE Contexts established for RRC\_CONNECTED UEs within the gNB-DU containing joining information of the UE for the respective multicast session. +- for broadcast, the gNB-DU determines whether F1-U tunnels are setup per gNB-DU or per MBS Area Session ID served by the gNB-DU. + +- for multicast, the gNB-DU determines whether F1-U tunnels are setup per gNB-DU or per cell served by the DU or per MBS Area Session ID served by the gNB-DU or for ptp retransmissions or for a ptp-only MRB leg. + +For multicast, for each MRB, the gNB-DU provides the MRB specific Uu configuration to the gNB-CU to configure the UE. + +### **Multicast F1-U Context:** + +A Multicast F1-U Context is a block of information in a gNB-DU to control the F1-U tunnels associated to the MRB Contexts established for a multicast MBS session. A Multicast F1-U Context is either established per gNB-DU or per cell served by the gNB-DU or per MBS Area Session ID served by the gNB-DU or for ptp retransmissions or for ptp forwarding or for a ptp-only MRB leg. Several Multicast F1-U contexts may exist in parallel in a gNB-DU for the same multicast MBS session. + +### **Allocation and usage of MRB ID values on NG-RAN interfaces for multicast MBS sessions:** + +- F1 interface: an MRB ID signalled on an F1 interface instance identifies uniquely an MRB among all MRB contexts in an gNB-DU, allocated for all active multicast MBS sessions served by that gNB-DU. The value of each MRB ID is the same value as communicated to UEs served by that gNB-DU. +- E1 interface: an MRB ID signalled on an E1 interface instance identifies uniquely an MRB among all MRBs allocated for a multicast MBS session. +- Xn interface, NG interface: MRB IDs are signalled on Xn/NG interfaces for providing MBS QoS flow to MRB mapping information and data forwarding information from the source gNB. The value of the MRB ID signalled on the Xn/NG interface is the same value as communicated to UEs at the source cell. + +### **Allocation and usage of MRB ID values on NG-RAN interfaces for broadcast MBS sessions:** + +- An MRB ID signalled on NG-RAN interfaces identifies uniquely an MRB among all MRBs allocated for a broadcast MBS session. + +### **MBS-associated logical F1/E1-connection:** + +F1AP and E1AP provide means to exchange control plane messages associated with an MBS session over the respective F1/E1 interface. + +An MBS-associated logical connection is established during the first F1AP/E1AP message exchange between the F1/E1 peer nodes. + +The connection is maintained as long as MBS associated F1AP/E1AP messages need to be exchanged over the F1/E1 interface. + +The MBS-associated logical F1-connection uses the identities gNB-CU MBS F1AP ID and gNB-DU MBS F1AP ID. + +The MBS-associated logical E1-connection uses the identities gNB-CU-CP MBS E1AP ID and gNB-CU-UP MBS E1AP ID. + +When a node (DU or CU or CU-CP and CU-UP) receives an MBS associated F1AP/E1AP message the node retrieves the associated MBS session based on the F1AP/E1AP ID. + +### **MBS-associated signalling:** + +MBS-associated signalling is an exchange of F1AP/E1AP messages associated with one MBS session over the MBS-associated logical F1/E1-connection. + +# --- **7 NG-RAN functions description** + +## **7.0 General** + +For the list of functions refer to TS 38.300 [2]. + +## 7.1 NG-RAN sharing + +NG-RAN supports radio access network sharing as specified in TS 23.501 [3] and TS 38.300 [2] and TS 36.300 [19]. + +## 7.2 Remote Interference Management + +The Remote Interference Management function in non-split gNB case is specified in TS 38.300 [2]. + +In case of split gNB architecture, in the victim set, a gNB-DU detects the remote interference. If remote interference is detected, the gNB-DU can send out the RIM-RS. In the aggressor set, if a gNB-DU detects the RIM-RS sent by the victim gNB(s), it sends to the gNB-CU the RIM-RS detection status and the victim Set ID. The gNB-CU acts as a coordinator on behalf of its affiliated gNB-DUs, where the gNB-CU merges the outgoing RIM information received from its gNB-DUs in the aggressor set and forwards the merged information to all the gNBs in the victim set. + +Similarly, in the victim set, the gNB-CU distributes the incoming RIM information to all the gNB-DUs in the set, as indicated in the RIM information received from the aggressor set. + +In addition, to facilitate consolidation of RIM information, the gNB-DU provides the associated aggressor set ID and the victim set ID of each serving cell to the gNB-CU. + +## 7.3 Cross-Link Interference Management + +The Cross-Link Interference Management function in non-split gNB case is specified in TS 38.300 [2]. + +In case of split gNB architecture, the gNB-CU forwards the TDD DL/UL patterns received from neighboring nodes to each concerned gNB-DU. The gNB-DU reports the TDD DL/UL patterns of its serving cells to the gNB-CU if Cross-Link Interference is detected. + +## 7.4 Support for Non-Public Networks + +NG-RAN supports NPN as specified in TS 23.501 [3] and TS 38.300 [2]. + +## 7.5 RACH Optimisation Function + +The RACH Optimization Function in non-split gNB case is specified in TS 38.300 [2]. + +In case of split gNB architecture, RACH configuration conflict detection and resolution function is located at the gNB-DU. To perform RACH optimisation at gNB-DU, gNB-CU sends the RA Report retrieved from the UE(s) to gNB-DU via FIAP signalling. The gNB-DU signals the PRACH configuration per-cell to gNB-CU. The gNB-CU may forward a limited set of neighbour cell's PRACH configurations received from neighbour gNBs and other gNB-DUs to the gNB-DU to resolve the configuration conflict. + +### RA Report retrieval + +When a UE performs successful random access attempts which are only known by the gNB-DU (e.g., beam failure recovery, UL synchronization issue, scheduling request failure, no PUCCH resource available), the gNB-DU may inform the gNB-CU about the occurrences of successful random access procedures in the gNB-DU via a RACH indication. The gNB-CU may then retrieve the RA Report from the UE(s) based on the RACH indication received via FIAP signalling from the gNB-DU. + +## 7.6 Positioning + +The NG-RAN supports the positioning functionality as specified in TS 38.305 [25]. + +## 7.7 Support for NR MBS + +The Support of NR MBS in non-split gNB case is specified in TS 38.300 [2]. + +### 7.7.1 Support of dynamic PTP and PTM switching + +For UEs in RRC\_CONNECTED, NG-RAN supports dynamic switch between PTP and PTM for MBS as specified in TS 38.300 [2]. + +In case of split gNB architecture, for a MRB with common PDCP involving both PTP (RLC leg) and PTM (RLC leg), upon receiving the MBS data from the gNB-CU via a shared F1-U tunnel, the gNB-DU makes decision of using PTP (RLC leg) or PTM (RLC leg) or both. + +For UEs in RRC\_INACTIVE only PTM is supported as specified in TS 38.300 [2]. + +### 7.7.2 Support of resource efficiency for RAN Sharing + +#### 7.7.2.1 General + +Resource efficiency for RAN sharing is supported in both MOCN scenario and Multiple Cell-ID Broadcast scenario. + +#### 7.7.2.2 Support of resource efficiency for MOCN + +Information enabling identifying broadcast MBS sessions for which RAN resources could be shared by the involved gNB-DUs and the gNB-CU-UP is provided by the gNB-CU-CP. Only one set of shared F1-U resources is established and kept as long as there is one PLMN keeping the Multicast service. + +#### 7.7.2.3 Support of resource efficiency for RAN Sharing with multiple cell-ID broadcast + +gNB-DUs sharing the same physical cell resources receive via F1-C information enabling identifying broadcast MBS sessions providing identical content. The identification is based on Associated Session ID, for location dependent MBS services, the MBS Service Area is also taken into account. + +Applying resource efficiency for RAN Sharing with multiple cell-ID broadcast + +- resolve different QoS requirements received from the participating 5GCs in an implementation specific way. +- F1-U resources are established towards either all involved gNB-CUs or only some of them which is decided by the entity controlling the involved gNB-DUs sharing the same physical cell resources. The gNB-DU is able to trigger the gNB-CU to establish F1-U resources. +- the gNB-CU-CP takes into account the decision F1-U resources have been established or not to decide whether to establish NG-U resources. + +### 7.7.3 Support of Multicast reception for UEs in RRC\_INACTIVE + +F1AP supports to enable and disable multicast reception for UEs in RRC\_INACTIVE state for a specific multicast session on cell level. + +The gNB-CU decides whether multicast reception in RRC\_INACTIVE is applied. + +## 7.8 PCI Optimisation Function + +The PCI Optimization Function in non-split gNB case is specified in TS 38.300 [2]. + +In split gNB architecture, the OAM configures a PCI for each NR cell to the gNB-DU. + +For centralized PCI assignment in split gNB architecture, the gNB-CU detects PCI conflict of NR cells and reports the NR cells suffering PCI conflict to OAM directly. The OAM is in charge of reassigning a new PCI for the NR cell subject to PCI conflict. + +For distributed PCI assignment in split gNB architecture, the OAM assigns a list of PCIs for each NR cell and sends the configured PCI list to the gNB-CU. If the gNB-CU detects PCI conflict, the gNB-CU may select a new PCI value from + +the preconfigured PCI list for the NR cell and send it to the gNB-DU by either F1 Setup procedure or gNB-CU configuration update procedure. + +## 7.9 Support for CCO + +### 7.9.1 General + +The NR Capacity and Coverage Optimization (CCO) Function in non-split gNB case is specified in TS 38.300 [2]. The objective of this function is to detect and mitigate coverage and cell edge interference issues. + +### 7.9.2 OAM requirements + +Each gNB-DU may be configured with alternative coverage configurations by OAM. The alternative coverage configurations contain relevant radio parameters and may also include a range for how each parameter is allowed to be adjusted. + +### 7.9.3 Dynamic coverage configuration changes + +In case of split gNB architecture, CCO detection function is located at the gNB-CU. The gNB-CU signals to the gNB-DU the CCO issue and the affected cells and beams. The gNB-DU resolves the CCO issue concerning own served cell by local action within the OAM configured limits. The gNB-DU may also take into account information received for other cells when adopting the CCO configuration. The gNB-DU informs the gNB-CU of the new coverage states adopted. + +## 7.10 Support of RAN visible QoE measurement + +The RAN visible QoE measurement function is specified in TS 38.300 [2]. + +In split gNB architecture, upon the reception of the RAN visible QoE measurement report from the UE, the gNB-CU may forward the corresponding QoE information to the gNB-DU. The QoE information transferred to the gNB-DU may include the RAN visible QoE measurement results received from the UE, along with the corresponding DRB ID(s). + +The gNB-DU may deactivate the transfer of RAN visible QoE measurement results from the gNB-CU, by initiating QoE Information Transfer Control procedure towards the gNB-CU. + +## 7.11 Support of AI/ML in NG-RAN + +The support of AI/ML in NG-RAN is specified in TS 38.300 [2]. + +In case of CU-DU split architecture, the following scenarios may be supported: + +- AI/ML Model Training is located in the OAM and AI/ML Model Inference is located in the gNB-CU. +- AI/ML Model Training and Model Inference are both located in the gNB-CU. + +# --- 8 Overall procedures in gNB-CU/gNB-DU Architecture + +## 8.1 UE Initial Access + +The signalling flow for UE Initial access is shown in Figure 8.1-1. + +![Sequence diagram of UE Initial Access procedure showing interactions between UE, gNB-DU, gNB-CU, and AMF.](dd5771673aececa53d42ece89218299d_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB-DU + participant gNB-CU + participant AMF + + Note left of UE: 1. RRCSetupRequest + UE->>gNB-DU: 1. RRCSetupRequest + Note right of gNB-DU: 2. INITIAL UL RRC MESSAGE TRANSFER + gNB-DU->>gNB-CU: 2. INITIAL UL RRC MESSAGE TRANSFER + Note right of gNB-CU: 3. DL RRC MESSAGE TRANSFER + gNB-CU->>gNB-DU: 3. DL RRC MESSAGE TRANSFER + Note left of gNB-DU: 4. RRCSetup + gNB-DU->>UE: 4. RRCSetup + Note left of UE: 5. RRCSetupComplete + UE->>gNB-DU: 5. RRCSetupComplete + Note right of gNB-DU: 6. UL RRC MESSAGE TRANSFER + gNB-DU->>gNB-CU: 6. UL RRC MESSAGE TRANSFER + Note right of gNB-CU: 7. INITIAL UE MESSAGE + gNB-CU->>AMF: 7. INITIAL UE MESSAGE + Note right of AMF: 8. INITIAL CONTEXT SETUP REQUEST + AMF->>gNB-CU: 8. INITIAL CONTEXT SETUP REQUEST + Note right of gNB-CU: 9. UE CONTEXT SETUP REQUEST + gNB-CU->>gNB-DU: 9. UE CONTEXT SETUP REQUEST + Note left of gNB-DU: 10. SecurityModeCommand + gNB-DU->>UE: 10. SecurityModeCommand + Note right of gNB-DU: 11. UE CONTEXT SETUP RESPONSE + gNB-DU->>gNB-CU: 11. UE CONTEXT SETUP RESPONSE + Note left of gNB-DU: 12. SecurityModeComplete + UE->>gNB-DU: 12. SecurityModeComplete + Note right of gNB-DU: 13. UL RRC MESSAGE TRANSFER + gNB-DU->>gNB-CU: 13. UL RRC MESSAGE TRANSFER + Note right of gNB-CU: 14. DL RRC MESSAGE TRANSFER + gNB-CU->>gNB-DU: 14. DL RRC MESSAGE TRANSFER + Note left of gNB-DU: 15. RRCReconfiguration + gNB-DU->>UE: 15. RRCReconfiguration + Note left of UE: 16. RRCReconfigurationComplete + UE->>gNB-DU: 16. RRCReconfigurationComplete + Note right of gNB-DU: 17. UL RRC MESSAGE TRANSFER + gNB-DU->>gNB-CU: 17. UL RRC MESSAGE TRANSFER + Note right of gNB-CU: 18. INITIAL CONTEXT SETUP RESPONSE + gNB-CU->>AMF: 18. INITIAL CONTEXT SETUP RESPONSE + +``` + +Sequence diagram of UE Initial Access procedure showing interactions between UE, gNB-DU, gNB-CU, and AMF. + +**Figure 8.1-1: UE Initial Access procedure** + +1. The UE sends an *RRCSetupRequest* message to the gNB-DU. +2. The gNB-DU includes the RRC message and, if the UE is admitted, the corresponding low layer configuration for the UE in the INITIAL UL RRC MESSAGE TRANSFER message and transfers to the gNB-CU. The INITIAL UL RRC MESSAGE TRANSFER message includes the C-RNTI allocated by the gNB-DU. If the gNB-DU identifies the UE as a Reduced Capability UE during the random access procedure, a NR RedCap UE Indication is provided in the INITIAL UL RRC MESSAGE TRANSFER message. +3. The gNB-CU allocates a gNB-CU UE FIAP ID for the UE and generates a *RRCSetup* message towards UE. The RRC message is encapsulated in the DL RRC MESSAGE TRANSFER message. +4. The gNB-DU sends the *RRCSetup* message to the UE. +5. The UE sends the RRC CONNECTION SETUP COMPLETE message to the gNB-DU. +6. The gNB-DU encapsulates the RRC message in the UL RRC MESSAGE TRANSFER message and sends it to the gNB-CU. +7. The gNB-CU sends the INITIAL UE MESSAGE message to the AMF. +8. The AMF sends the INITIAL CONTEXT SETUP REQUEST message to the gNB-CU. +9. The gNB-CU sends the UE CONTEXT SETUP REQUEST message to establish the UE context in the gNB-DU. In this message, it may also encapsulate the *SecurityModeCommand* message. In case of NG-RAN sharing, the gNB-CU includes the serving PLMN ID (for SNPNS the serving SNPN ID). +10. The gNB-DU sends the *SecurityModeCommand* message to the UE. +11. The gNB-DU sends the UE CONTEXT SETUP RESPONSE message to the gNB-CU. +12. The UE responds with the *SecurityModeComplete* message. + +13. The gNB-DU encapsulates the RRC message in the UL RRC MESSAGE TRANSFER message and sends it to the gNB-CU. +14. The gNB-CU generates the *RRCReconfiguration* message and encapsulates it in the DL RRC MESSAGE TRANSFER message. +15. The gNB-DU sends *RRCReconfiguration* message to the UE. +16. The UE sends *RRCReconfigurationComplete* message to the gNB-DU. +17. The gNB-DU encapsulates the RRC message in the UL RRC MESSAGE TRANSFER message and send it to the gNB-CU. +18. The gNB-CU sends the INITIAL CONTEXT SETUP RESPONSE message to the AMF. + +## 8.2 Intra-gNB-CU Mobility + +### 8.2.1 Intra-NR Mobility + +#### 8.2.1.1 Inter-gNB-DU Mobility + +This procedure is used for the case when the UE moves from one gNB-DU to another gNB-DU within the same gNB-CU during NR operation. Figure 8.2.1.1-1 shows the inter-gNB-DU mobility procedure for intra-NR. + +![Sequence diagram for Inter-gNB-DU Mobility for intra-NR. The diagram shows the interaction between UE, Source gNB-DU, Target gNB-DU, and gNB-CU. The process involves measurement reporting, context modification, context setup, random access, and context release.](dc1f232cfd39be5c20b21374ad4c04c0_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Source gNB-DU + participant Target gNB-DU + participant gNB-CU + + Note left of UE: Downlink user data + Note left of UE: Uplink user data + UE->>Source gNB-DU: 1. MeasurementReport + Source gNB-DU->>gNB-CU: 2. UL RRC MESSAGE TRANSFER (MeasurementReport) + gNB-CU->>Source gNB-DU: 2a. UE CONTEXT MODIFICATION REQUEST + Source gNB-DU->>gNB-CU: 2b. UE CONTEXT MODIFICATION RESPONSE + gNB-CU->>Target gNB-DU: 3. UE CONTEXT SETUP REQUEST + Target gNB-DU->>gNB-CU: 4. UE CONTEXT SETUP RESPONSE + gNB-CU->>Source gNB-DU: 5. UE CONTEXT MODIFICATION REQUEST (RRCReconfiguration) + Source gNB-DU->>UE: 6. RRCReconfiguration + Note right of UE: Downlink Data Delivery Status + Source gNB-DU->>gNB-CU: 7. UE CONTEXT MODIFICATION RESPONSE + Note left of UE: Random Access Procedure + UE->>Target gNB-DU: 8. Random Access Procedure + Note right of Target gNB-DU: Downlink Data Delivery Status + Target gNB-DU->>UE: 9. RRCReconfigurationComplete + Note right of Target gNB-DU: Downlink User Data + Target gNB-DU->>gNB-CU: 10. UL RRC MESSAGE TRANSFER (RRCReconfigurationComplete) + Note left of UE: Downlink user data + Note left of UE: Uplink user data + Source gNB-DU->>gNB-CU: 11. UE CONTEXT RELEASE COMMAND + gNB-CU->>Source gNB-DU: 12. UE CONTEXT RELEASE COMPLETE + +``` + +Sequence diagram for Inter-gNB-DU Mobility for intra-NR. The diagram shows the interaction between UE, Source gNB-DU, Target gNB-DU, and gNB-CU. The process involves measurement reporting, context modification, context setup, random access, and context release. + +Figure 8.2.1.1-1: Inter-gNB-DU Mobility for intra-NR + +1. The UE sends a *MeasurementReport* message to the source gNB-DU. + +2. The source gNB-DU sends an UL RRC MESSAGE TRANSFER message to the gNB-CU to convey the received *MeasurementReport* message. + - 2a. The gNB-CU may send an UE CONTEXT MODIFICATION REQUEST message to the source gNB-DU to query the latest configuration. + - 2b. The source gNB-DU responds with an UE CONTEXT MODIFICATION RESPONSE message that includes full configuration information. + 3. The gNB-CU sends an UE CONTEXT SETUP REQUEST message to the target gNB-DU to create an UE context and setup one or more data bearers. The UE CONTEXT SETUP REQUEST message includes a HandoverPreparationInformation. In case of NG-RAN sharing, the gNB-CU includes the serving PLMN ID (for SNPNs the serving SNPN ID). + 4. The target gNB-DU responds to the gNB-CU with an UE CONTEXT SETUP RESPONSE message. + 5. The gNB-CU sends a UE CONTEXT MODIFICATION REQUEST message to the source gNB-DU, which includes a generated *RRCREconfiguration* message and indicates to stop the data transmission for the UE. The source gNB-DU also sends a Downlink Data Delivery Status frame to inform the gNB-CU about the unsuccessfully transmitted downlink data to the UE. +- NOTE: In case of DAPS Handover, the UE CONTEXT MODIFICATION REQUEST message in step 5 may indicate to stop the data transmission only for the DRB(s) not subject to DAPS Handover or may not indicate to stop the data transmission at all. Instead, the DL RRC Message Transfer procedure can be used to carry the handover command to the UE. The UE CONTEXT MODIFICATION REQUEST message that indicates to stop the data transmission for the UE is sent to the source gNB-DU once the gNB-CU knows that the UE has successfully accessed the target gNB-DU, for which the source gNB-DU sends a DDDS frame about the unsuccessfully transmitted downlink data to the gNB-CU. +6. The source gNB-DU forwards the received *RRCREconfiguration* message to the UE. + 7. The source gNB-DU responds to the gNB-CU with the UE CONTEXT MODIFICATION RESPONSE message. + 8. A Random Access procedure is performed at the target gNB-DU. The target gNB-DU sends a Downlink Data Delivery Status frame to inform the gNB-CU. Downlink packets, which may include PDCP PDUs not successfully transmitted in the source gNB-DU, are sent from the gNB-CU to the target gNB-DU. +- NOTE: It is up to gNB-CU implementation whether to start sending DL User Data to gNB-DU before or after reception of the Downlink Data Delivery Status. +9. The UE responds to the target gNB-DU with an *RRCREconfigurationComplete* message. + 10. The target gNB-DU sends an UL RRC MESSAGE TRANSFER message to the gNB-CU to convey the received *RRCREconfigurationComplete* message. Downlink packets are sent to the UE. Also, uplink packets are sent from the UE, which are forwarded to the gNB-CU through the target gNB-DU. + 11. The gNB-CU sends an UE CONTEXT RELEASE COMMAND message to the source gNB-DU. + 12. The source gNB-DU releases the UE context and responds the gNB-CU with an UE CONTEXT RELEASE COMPLETE message. + +#### 8.2.1.2 Intra-gNB-DU handover + +This procedure is used for the case that the UE moves from one cell to another cell within the same gNB-DU or for the case that intra-cell handover is performed during NR operation, and supported by the UE Context Modification (gNB-CU initiated) procedure as specified in TS 38.473 [4]. When the intra-gNB-DU handover is performed (either inter-cell or intra-cell), the gNB-CU provides new UL GTP TEID to the gNB-DU and the gNB-DU provides new DL GTP TEID to the gNB-CU. The gNB-DU shall continue sending UL PDCP PDUs to the gNB-CU using the previous UL GTP TEID until it re-establishes the RLC, and after then start sending using the new UL GTP TEID. The gNB-CU shall continue sending DL PDCP PDUs to the gNB-DU using the previous DL GTP TEID until it performs PDCP re-establishment or PDCP data recovery, and after then start sending using the new DL GTP TEID. + +#### 8.2.1.3 Inter-gNB-DU Conditional Handover or Conditional PSCell Change or subsequent CPAC + +This procedure is used for the case when the UE moves from one gNB-DU to another gNB-DU within the same gNB-CU during NR operation for conditional handover or conditional PSCell change or subsequent CPAC. Figure 8.2.1.3-1 shows the inter-gNB-DU conditional mobility procedure for intra-NR. + +![Sequence diagram for Inter-gNB-DU Conditional Handover or Conditional PSCell Change or subsequent CPAC. The diagram shows interactions between UE, Source gNB-DU, Candidate gNB-DU, and gNB-CU. It includes steps for measurement reporting, RRC reconfiguration, random access, and context modification/release.](5478f70a6cef3e5672b2b22d28830cfb_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Source gNB-DU + participant Candidate gNB-DU + participant gNB-CU + + Note left of UE: Downlink user data + Note left of UE: Uplink user data + UE->>Source gNB-DU: 1. MeasurementReport + Source gNB-DU->>gNB-CU: 2. UL RRC MESSAGE TRANSFER (MeasurementReport) + gNB-CU->>Candidate gNB-DU: 3. UE CONTEXT SETUP REQUEST (Conditional Inter-DU Mobility Information) + Candidate gNB-DU->>gNB-CU: 4. UE CONTEXT SETUP RESPONSE (Requested Target Cell ID) + gNB-CU->>Source gNB-DU: 5. DL RRC MESSAGE TRANSFER (RRReconfiguration) + Source gNB-DU->>UE: 6. RRReconfiguration + UE->>Source gNB-DU: 7. RRReconfigurationComplete + Source gNB-DU->>gNB-CU: 8. UL RRC MESSAGE TRANSFER (RRReconfigurationComplete) + Note left of UE: 9. Execution condition(s) are fulfilled + UE->>Candidate gNB-DU: 10. Random Access Procedure + Candidate gNB-DU->>gNB-CU: Downlink Data Delivery Status + gNB-CU->>Candidate gNB-DU: ACCESS SUCCESS + Candidate gNB-DU->>UE: 11. RRReconfigurationComplete + Candidate gNB-DU->>gNB-CU: 12. UL RRC MESSAGE TRANSFER (RRReconfigurationComplete) + gNB-CU->>Source gNB-DU: 13. UE CONTEXT MODIFICATION REQUEST + Source gNB-DU->>gNB-CU: Downlink Data Delivery Status + gNB-CU->>Candidate gNB-DU: Downlink User Data + Note left of UE: Downlink user data + Note left of UE: Uplink user data + Candidate gNB-DU->>gNB-CU: 14. UE CONTEXT MODIFICATION RESPONSE + gNB-CU->>Source gNB-DU: 15. UE CONTEXT RELEASE COMMAND + Source gNB-DU->>gNB-CU: 16. UE CONTEXT RELEASE COMPLETE + +``` + +Sequence diagram for Inter-gNB-DU Conditional Handover or Conditional PSCell Change or subsequent CPAC. The diagram shows interactions between UE, Source gNB-DU, Candidate gNB-DU, and gNB-CU. It includes steps for measurement reporting, RRC reconfiguration, random access, and context modification/release. + +**Figure 8.2.1.3-1: Inter-gNB-DU Conditional Handover or Conditional PSCell Change or subsequent CPAC for intra-NR** + +- 1-2. The steps 1-2 are as defined in clause 8.2.1.1. +3. The gNB-CU sends an UE CONTEXT SETUP REQUEST message to the candidate gNB-DU to create an UE context and setup one or more data bearers. The UE CONTEXT SETUP REQUEST message is sent for each candidate cell and includes a HandoverPreparationInformation (conditional handover) or a CG-ConfigInfo (conditional PSCell change or subsequent CPAC). +4. The candidate gNB-DU responds to the gNB-CU with an UE CONTEXT SETUP RESPONSE message including the target cell ID that was requested from the gNB-CU. The response message is sent for each requested candidate cell. + +5. The gNB-CU sends a DL RRC MESSAGE TRANSFER message to the source gNB-DU, which includes a generated *RRReconfiguration* message. + 6. The step 6 is as defined in clause 8.2.1.1. + - 7-8. The UE responds to the source gNB-DU with an *RRReconfigurationComplete* message, for which the source gNB-DU forwards to the gNB-CU via an UL RRC MESSAGE TRANSFER message. + 9. An execution condition to trigger initiation of conditional handover or conditional PSCell change or subsequent CPAC is fulfilled. + 10. A Random Access procedure is performed at the candidate gNB-DU, which becomes the target gNB-DU if successful. The target gNB-DU sends a Downlink Data Delivery Status frame to inform the gNB-CU. The target gNB-DU also sends an ACCESS SUCCESS message to inform the gNB-CU of which cell the UE has successfully accessed. + - 11-12. The steps 11-12 are as defined in steps 9-10 in clause 8.2.1.1. + 13. The gNB-CU sends a UE CONTEXT MODIFICATION REQUEST message to the source gNB-DU and indicates to stop the data transmission for the UE. The source gNB-DU also sends a Downlink Data Delivery Status frame to inform the gNB-CU about the unsuccessfully transmitted downlink data to the UE. Downlink packets, which may include PDCP PDUs not successfully transmitted in the source gNB-DU, are sent from the gNB-CU to the target gNB-DU. +- NOTE: The step 13 may happen before step 12, as soon as the gNB-CU knows which cell the UE has successfully accessed. +- NOTE: The gNB-CU may initiate UE Context Release procedure toward the other signalling connections or other candidate target gNB-DUs, if any, to cancel conditional handover or conditional PSCell change for the UE. +14. The source gNB-DU responds to the gNB-CU with the UE CONTEXT MODIFICATION RESPONSE message. + - 15 -16. The steps 15-16 are as defined in steps 11-12 in clause 8.2.1.1. + +The step 15~16 shall not happen if all of the PSCells in the source gNB-DU remain configured as the candidate PSCell(s) in the subsequent CPAC. + +#### 8.2.1.4 Intra-gNB-DU LTM + +This procedure is used for the case when the UE moves within the same gNB-DU during NR operation for LTM. Figure 8.2.1.4-1 shows the intra-gNB-DU LTM procedure for intra-NR. + +![Sequence diagram for Intra-gNB-DU LTM showing interactions between UE, gNB-DU, and gNB-CU.](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +The diagram illustrates the sequence of messages for Intra-gNB-DU LTM. It features three lifelines: UE, gNB-DU, and gNB-CU. The process begins with the UE sending 'User Data' to the gNB-DU, which then forwards it to the gNB-CU. The gNB-DU sends '1. L3 Measurement Control and Reports' to the UE. The gNB-CU makes a '2. LTM Configuration Decision' and sends a '3. UE CONTEXT MODIFICATION REQUEST' to the gNB-DU. The gNB-DU responds with '4. UE CONTEXT MODIFICATION RESPONSE'. The gNB-CU sends another '5. UE CONTEXT MODIFICATION REQUEST' to the gNB-DU, which responds with '6. UE CONTEXT MODIFICATION RESPONSE'. The gNB-CU sends a '7. DL RRC MESSAGE TRANSFER (RRReconfiguration)' to the gNB-DU, which then sends '8. RRReconfiguration' to the UE. The UE responds with '9. RRReconfigurationComplete' to the gNB-DU. The gNB-DU sends '10. UL RRC MESSAGE TRANSFER (RRReconfigurationComplete)' to the gNB-CU. The UE performs '11. Early TA acquisition' and sends '12. L1 measurement report' to the gNB-DU. The gNB-DU makes an 'Inter-cell Mobility Execution Decision' and sends '13. Cell Switch Command' to the UE. The gNB-DU sends '14. DU-CU CELL SWITCH NOTIFICATION (Target cell ID)' to the gNB-CU. The gNB-CU sends a 'Downlink Data Delivery Status' to the gNB-DU. The gNB-DU detects the UE access ('15. The gNB-DU detects the UE access') and sends '16. ACCESS SUCCESS (Target cell ID)' to the gNB-CU. The UE sends '17. RRReconfigurationComplete' to the gNB-DU. The gNB-DU sends '18. UL RRC MESSAGE TRANSFER (RRReconfigurationComplete)' to the gNB-CU. The gNB-CU sends '19. UE CONTEXT MODIFICATION REQUEST (Prepared cells to be released)' to the gNB-DU, which responds with '20. UE CONTEXT MODIFICATION RESPONSE'. Finally, the UE sends 'User Data' to the gNB-DU, which forwards it to the gNB-CU. + +``` + +sequenceDiagram + participant UE + participant gNB-DU + participant gNB-CU + + Note left of UE: User Data + Note right of gNB-CU: User Data + Note over UE, gNB-DU: 1. L3 Measurement Control and Reports + Note right of gNB-CU: 2. LTM Configuration Decision + gNB-CU->>gNB-DU: 3. UE CONTEXT MODIFICATION REQUEST + gNB-DU-->>gNB-CU: 4. UE CONTEXT MODIFICATION RESPONSE + gNB-CU->>gNB-DU: 5. UE CONTEXT MODIFICATION REQUEST + gNB-DU-->>gNB-CU: 6. UE CONTEXT MODIFICATION RESPONSE + gNB-CU->>gNB-DU: 7. DL RRC MESSAGE TRANSFER (RRReconfiguration) + gNB-DU->>UE: 8. RRReconfiguration + UE->>gNB-DU: 9. RRReconfigurationComplete + gNB-DU->>gNB-CU: 10. UL RRC MESSAGE TRANSFER (RRReconfigurationComplete) + Note left of UE: 11. Early TA acquisition + UE->>gNB-DU: 12. L1 measurement report + Note over gNB-DU: Inter-cell Mobility Execution Decision + gNB-DU->>UE: 13. Cell Switch Command + gNB-DU->>gNB-CU: 14. DU-CU CELL SWITCH NOTIFICATION (Target cell ID) + Note right of gNB-CU: Downlink Data Delivery Status + Note over gNB-DU: 15. The gNB-DU detects the UE access + gNB-DU->>gNB-CU: 16. ACCESS SUCCESS (Target cell ID) + UE->>gNB-DU: 17. RRReconfigurationComplete + gNB-DU->>gNB-CU: 18. UL RRC MESSAGE TRANSFER (RRReconfigurationComplete) + gNB-CU->>gNB-DU: 19. UE CONTEXT MODIFICATION REQUEST (Prepared cells to be released) + gNB-DU-->>gNB-CU: 20. UE CONTEXT MODIFICATION RESPONSE + Note left of UE: User Data + Note right of gNB-CU: User Data + +``` + +Sequence diagram for Intra-gNB-DU LTM showing interactions between UE, gNB-DU, and gNB-CU. + +Figure 8.2.1.4-1: Intra-gNB-DU LTM + +1. The UE sends a *MeasurementReport* message (L3 measurement result) to the gNB-DU containing measurements of neighbouring cells. The gNB-DU sends an UL RRC MESSAGE TRANSFER message conveying the received *MeasurementReport* message to the gNB-CU. + +2. The gNB-CU determines to initiate LTM configuration. + 3. The gNB-CU sends a UE CONTEXT MODIFICATION REQUEST message to the gNB-DU containing one target candidate cell ID, the LTM configuration ID of the candidate cell, and LTM configuration ID mapping list, the CSI resource configuration. The gNB-CU requests PRACH resources from the gNB-DU. The gNB-CU may request the gNB-DU to provide the lower layer configuration for the purpose of generating the reference configuration. + 4. If the gNB-DU accepts the request of LTM configuration, it responds with a UE CONTEXT MODIFICATION RESPONSE message including the generated lower layer RRC configurations (e.g., TCI state configuration, RACH configuration, and the CSI report configuration) for the accepted target candidate cell. +- NOTE 1: Steps 3 and 4 may be initiated multiple times for LTM candidate cell preparation of multiple cells including the source cell. +5. The gNB-CU sends a UE CONTEXT MODIFICATION REQUEST message to the source gNB-DU including the collected TCI state configurations and the gNB-CU may send the CSI report configuration for all the accepted target candidate cells. + 6. The source gNB-DU responds with a UE CONTEXT MODIFICATION RESPONSE message which includes an updated lower layer configuration, e.g., containing the CSI report configuration of the source cell. +- NOTE 2: In case of subsequent LTM, the CU-initiated UE Context Modification procedure may be invoked per each candidate cell to transfer to the candidate gNB-DU the CSI report configuration, TCI state information, RACH configuration, and the LTM configuration IDs of the candidate cells. +7. The gNB-CU sends a DL RRC MESSAGE TRANSFER message to the gNB-DU, which includes the generated *RRReconfiguration* message with the LTM configuration. + 8. The gNB-DU forwards the received *RRReconfiguration* message to the UE. + 9. The UE responds to the gNB-DU with an *RRReconfigurationComplete* message. + 10. The gNB-DU forwards the *RRReconfigurationComplete* message to the gNB-CU via an UL RRC MESSAGE TRANSFER message. + 11. Early synchronization may be performed as specified in TS 38.300 [2]. + 12. The UE sends the L1 measurement result to the gNB-DU. The gNB-DU decides to execute LTM. + 13. The gNB-DU sends the Cell Switch command to the UE. + 14. The gNB-DU sends the DU-CU CELL CHANGE NOTIFICATION message to the gNB-CU to indicate the initiation of the Cell Switch command to the UE including the target cell ID and the TCI state ID. + 15. The gNB-DU detects the UE access as specified in TS 38.300 [2]. + 16. The target gNB-DU sends the ACCESS SUCCESS message to the gNB-CU with the target cell ID. + 17. The UE sends an *RRReconfigurationComplete* message to the gNB-DU. + 18. The gNB-DU forwards the *RRReconfigurationComplete* message to the gNB-CU via an UL RRC MESSAGE TRANSFER message. + 19. The gNB-CU may send the UE CONTEXT MODIFICATION REQUEST message to the gNB-DU to release the resources of prepared cells. + 20. The gNB-DU responds with a UE CONTEXT MODIFICATION RESPONSE message. + +#### 8.2.1.5 Inter-gNB-DU LTM + +This procedure is used for the case when the UE moves from one gNB-DU to another gNB-DU within the same gNB-CU during NR operation for LTM. Figure 8.2.1.5-1 shows the inter-gNB-DU LTM procedure for intra-NR. + +![Sequence diagram of LTM (Long Term Measurement) procedure between UE, Source gNB-DU, Candidate gNB-DU, and gNB-CU.](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +The sequence diagram illustrates the LTM procedure involving four entities: UE, Source gNB-DU, Candidate gNB-DU, and gNB-CU. The process begins with 'User Data' exchange between the UE and the gNB-CU. The sequence of messages is as follows: + +- 1. L3 Measurement Control and Reports**: A message from the UE to the Source gNB-DU. +- 2. LTM Configuration Decision**: A decision made by the gNB-CU. +- 3. UE CONTEXT SETUP REQUEST**: A message from the gNB-CU to the Candidate gNB-DU. +- 4. UE CONTEXT SETUP RESPONSE**: A message from the Candidate gNB-DU to the gNB-CU. +- 5. UE CONTEXT MODIFICATION REQUEST**: A message from the gNB-CU to the Source gNB-DU. +- 6. UE CONTEXT MODIFICATION RESPONSE**: A message from the Source gNB-DU to the gNB-CU. +- 7. UE CONTEXT MODIFICATION REQUEST**: A message from the gNB-CU to the Candidate gNB-DU. +- 8. UE CONTEXT MODIFICATION RESPONSE**: A message from the Candidate gNB-DU to the gNB-CU. +- 9. DL RRC MESSAGE TRANSFER (RRReconfiguration)**: A message from the gNB-CU to the Source gNB-DU. +- 10. RRReconfiguration**: A message from the Source gNB-DU to the UE. +- 11. RRReconfigurationComplete**: A message from the UE to the Source gNB-DU. +- 12. UL RRC MESSAGE TRANSFER (RRReconfigurationComplete)**: A message from the Source gNB-DU to the gNB-CU. +- 13. early TA acquisition**: A message from the UE to the Candidate gNB-DU. +- 14. DU-CU TA INFORMATION TRANSFER**: A message from the Candidate gNB-DU to the gNB-CU. +- 15. CU-DU TA INFORMATION TRANSFER**: A message from the gNB-CU to the Source gNB-DU. +- 16. L1 measurement report**: A message from the UE to the Source gNB-DU. +- 17. LTM Cell switch decision**: A decision made by the Source gNB-DU. +- 18. Cell Switch Command**: A message from the Source gNB-DU to the UE. +- 19. DU-CU CELL SWITCH NOTIFICATION (Target cell ID, TCI State ID)**: A message from the Source gNB-DU to the gNB-CU. +- 20. CU-DU CELL SWITCH NOTIFICATION (Target cell ID, TCI State ID)**: A message from the gNB-CU to the Candidate gNB-DU. +- Downlink Data Delivery Status**: A message from the Source gNB-DU to the gNB-CU. +- 21. The gNB-DU detects the UE access**: A message from the Candidate gNB-DU to the gNB-CU. +- 22. ACCESS SUCCESS (Target cell ID)**: A message from the Candidate gNB-DU to the gNB-CU. +- 23. RRReconfigurationComplete**: A message from the UE to the Candidate gNB-DU. +- 24. UL RRC MESSAGE TRANSFER (RRReconfigurationComplete)**: A message from the Candidate gNB-DU to the gNB-CU. +- 25. UE CONTEXT RELEASE COMMAND (Prepared cells to be released)**: A message from the gNB-CU to the Source gNB-DU. +- 26. UE CONTEXT RELEASE COMPLETE**: A message from the Source gNB-DU to the gNB-CU. + +The process concludes with 'User Data' exchange between the UE and the gNB-CU. + +Sequence diagram of LTM (Long Term Measurement) procedure between UE, Source gNB-DU, Candidate gNB-DU, and gNB-CU. + +**Figure 8.2.1.5-1: Inter-gNB-DU LTM** + +1. The UE sends a *MeasurementReport* message (L3 measurement result) to the source gNB-DU containing measurements of neighbouring cells. The source gNB-DU sends an UL RRC MESSAGE TRANSFER message conveying the received *MeasurementReport* message to the gNB-CU. +2. The gNB-CU determines to initiate LTM configuration. +3. The gNB-CU sends a UE CONTEXT SETUP REQUEST message to the candidate gNB-DU(s), containing one target candidate cell ID, the LTM configuration ID of the candidate cell, LTM configuration ID mapping list, and the CSI resource configuration. The gNB-CU indicates the source gNB-DU ID, and requests PRACH resources from the candidate gNB-DU. The gNB-CU may request the candidate gNB-DU to provide the lower layer configuration for the purpose of generating the reference configuration. +4. If the candidate gNB-DU accepts the request of LTM configuration, it responds with a UE CONTEXT SETUP RESPONSE message including the generated lower layer RRC configurations (e.g., TCI state configuration, RACH configuration, and the CSI report configuration) for the accepted target candidate cell. + +NOTE 1: The CU-initiated UE Context Modification procedure may be initiated for preparing candidate cells in the source gNB-DU as specified in step 3 and 4 in 8.2.1.4 Intra-gNB-DU LTM. + +5. The gNB-CU sends a UE CONTEXT MODIFICATION REQUEST message to the source gNB-DU including the collected CSI report configuration, RACH configuration and the TCI state configuration for the accepted target candidate cell(s) in other gNB-DU(s). +6. The source gNB-DU responds with a UE CONTEXT MODIFICATION RESPONSE message which includes an updated lower layer configuration, e.g., containing the CSI report configuration. +7. The gNB-CU sends a UE CONTEXT MODIFICATION REQUEST message to the candidate gNB-DU(s) containing the CSI report configuration, TCI state information, RACH Configuration, and the LTM configuration IDs of the candidate cells in other candidate gNB-DU(s). The gNB-CU may also provide the lower layer part of the reference configuration to the candidate gNB-DU(s). The gNB-CU may also provide an updated CSI resource configuration to the candidate gNB-DU(s). + +NOTE 2: The candidate cell may be the same cell as source cell. + +8. The candidate gNB-DU responds with a UE CONTEXT MODIFICATION RESPONSE message including the updated lower layer configuration. The candidate gNB-DU may also respond the updated CSI report configuration. +9. The gNB-CU sends a DL RRC MESSAGE TRANSFER message to the source gNB-DU, which includes the generated *RRReconfiguration* message with the LTM configuration. +10. The source gNB-DU forwards the received *RRReconfiguration* message to the UE. +11. The UE responds to the source gNB-DU with an *RRReconfigurationComplete* message. +12. The source gNB-DU forwards the *RRReconfigurationComplete* message to the gNB-CU via an UL RRC MESSAGE TRANSFER message. +13. Early synchronization may be performed as specified in TS 38.300 [2]. +- 14 - 15. The candidate gNB-DU sends the TA value, the associated CFRA resource information, the candidate cell ID and the source gNB-DU ID to the source gNB-DU via the DU-CU TA INFORMATION TRANSFER and CU-DU TA INFORMATION TRANSFER messages, for which the source gNB-DU ID is omitted in the CU-DU TA INFORMATION TRANSFER message. +16. The UE sends the L1 measurement result to the source gNB-DU. +17. The source gNB-DU decides to execute LTM to a candidate target cell. +18. The source gNB-DU sends the Cell Switch command to the UE. +19. The source gNB-DU sends the DU-CU CELL SWITCH NOTIFICATION message to the gNB-CU to indicate the initiation of the Cell Switch command to the UE, for which the message includes the target cell ID and the TCI state ID. + +20. The gNB-CU forwards the target cell ID and the TCI state ID to the target gNB-DU in the CU-DU CELL SWITCH NOTIFICATION message. +21. The target gNB-DU detects the UE access as specified in TS 38.300 [2]. +22. The target gNB-DU sends the ACCESS SUCCESS message to the gNB-CU with the target cell ID. +23. The UE sends an *RRReconfigurationComplete* message to the target gNB-DU. +24. The target gNB-DU forwards the *RRReconfigurationComplete* message to the gNB-CU via an UL RRC MESSAGE TRANSFER message. +25. The gNB-CU may send the UE CONTEXT RELEASE COMMAND message to the source gNB-DU to release the resources of prepared cells. +26. The source gNB-DU responds with a UE CONTEXT RELEASE COMPLETE message. + +#### 8.2.1.6 LTM with gNB-CU-UP change + +Figure 8.2.1.6-1 shows the procedure used for LTM with the change of gNB-CU-UP within a gNB. + +![Sequence diagram for LTM with the change of gNB-CU-UP. The diagram shows interactions between Source gNB-DU, Target gNB-DU, gNB-CU-CP, Source gNB-CU-UP, Target gNB-CU-UP, and AMF/UPF. It details the flow of messages for measurement, configuration, RRC transfer, cell switch notification, bearer context modification, data forwarding, and path update.](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +``` + +sequenceDiagram + participant Source gNB-DU + participant Target gNB-DU + participant gNB-CU-CP + participant Source gNB-CU-UP + participant Target gNB-CU-UP + participant AMF/UPF + + Note right of gNB-CU-CP: 1. LTM configuration decision + + Source gNB-DU->>gNB-CU-CP: 0. measurement report + gNB-CU-CP->>Target gNB-CU-UP: 2. BEARER CONTEXT SETUP REQUEST + Target gNB-CU-UP-->>gNB-CU-CP: 3. BEARER CONTEXT SETUP RESPONSE + Note left of Source gNB-DU: 4. LTM configuration procedures + gNB-CU-CP->>Source gNB-DU: 5. DL RRC MESSAGE TRANSFER (RRReconfiguration) + Source gNB-DU->>gNB-CU-CP: 6. UL RRC MESSAGE TRANSFER (RRReconfigurationComplete) + Note right of Source gNB-DU: 7. LTM decision + Source gNB-DU->>gNB-CU-CP: 8. DU-CU CELL SWITCH NOTIFICATION + gNB-CU-CP->>Source gNB-CU-UP: 9. BEARER CONTEXT MODIFICATION REQUEST + Source gNB-CU-UP-->>gNB-CU-CP: 10. BEARER CONTEXT MODIFICATION RESPONSE + gNB-CU-CP->>Target gNB-CU-UP: 11. BEARER CONTEXT MODIFICATION REQUEST + Target gNB-CU-UP-->>gNB-CU-CP: 12. BEARER CONTEXT MODIFICATION RESPONSE + Note right of Target gNB-CU-UP: 13. Data forwarding + Note left of Target gNB-DU: 14. UE detected + Target gNB-DU->>gNB-CU-CP: 15. ACCESS SUCCESS + Note right of gNB-CU-CP: 16. Path Update procedure is performed towards the core network + Note right of Source gNB-CU-UP: 17. End Marker Packet + Note right of Source gNB-DU: 18. New path + gNB-CU-CP->>Source gNB-CU-UP: 19. BEARER CONTEXT RELEASE COMMAND + Source gNB-CU-UP-->>gNB-CU-CP: 20. BEARER CONTEXT RELEASE COMPLETE + +``` + +Sequence diagram for LTM with the change of gNB-CU-UP. The diagram shows interactions between Source gNB-DU, Target gNB-DU, gNB-CU-CP, Source gNB-CU-UP, Target gNB-CU-UP, and AMF/UPF. It details the flow of messages for measurement, configuration, RRC transfer, cell switch notification, bearer context modification, data forwarding, and path update. + +Figure 8.2.1.6-1 LTM with the change of gNB-CU-UP + +0. The source gNB-DU forwards the Measurement Report to the gNB-CU-CP. +1. The gNB-CU-CP decides to initiate LTM configuration. +2. The gNB-CU-CP sends a BEARER CONTEXT SETUP REQUEST message containing UL TNL address information for NG-U to setup the bearer context in the target gNB-CU-UP. + +3. The target gNB-CU-UP responds with a BEARER CONTEXT SETUP RESPONSE message containing the UL TNL address information for F1-U, DL TNL address information for NG-U, and the TNL address information for data forwarding to the target gNB-CU-UP. +4. LTM configuration procedures are performed between gNB-CU and candidate gNB-DUs, and between gNB-CU and source gNB-DU as specified from step 3 to step 8 in section 8.2.1.5. +- 5 - 6. The gNB-CU-CP sends the RRC Reconfiguration message to the UE. +7. The UE sends the lower layer measurement result to the source gNB-DU, and the source gNB-DU decides to execute LTM to a candidate target cell. +8. The source gNB-DU sends the DU-CU CELL SWITCH NOTIFICATION message to the gNB-CU-CP with the selected target cell ID. +- 9-10. The gNB-CU-CP performs the Bearer Context Modification procedure to retrieve the PDCP UL/DL status and to exchange the TNL address information for data forwarding for the bearers. +- 11-12. The gNB-CU-CP performs the Bearer Context Modification procedure to send the DL TNL address information for F1-U and the PDCP UP/DL status to the target gNB-CU-UP. +13. Data Forwarding may be performed from the source gNB-CU-UP to the target gNB-CU-UP. +14. The target gNB-DU detects the UE in the target cell. +15. The target gNB-DU sends an ACCESS SUCCESS message to the gNB-CU-CP. +- 16-18. Path Switch procedure is performed to update the DL TNL address information for the NG-U towards the core network. +- 19-20. Bearer Context Release procedure may be performed to release the UE context in the source gNB-DU. + +### 8.2.2 EN-DC Mobility + +#### 8.2.2.1 Inter-gNB-DU Mobility using MCG SRB + +This procedure is used for the case the UE moves from one gNB-DU to another gNB-DU within the same gNB-CU when only MCG SRB is available during EN-DC operation. Figure 8.2.2.1-1 shows the inter-gNB-DU mobility procedure using MCG SRB in EN-DC. + +![Sequence diagram for Inter-gNB-DU Mobility using MCG SRB in EN-DC. The diagram shows the interaction between UE, Source gNB-DU, Target gNB-DU, gNB-CU, and MeNB. It details the signaling steps for mobility, including RRC transfer, context modification, and data delivery status.](9252ccfbbe9e34cb108f0060f2b563f1_img.jpg) + +The sequence diagram illustrates the interaction between the UE, Source gNB-DU, Target gNB-DU, gNB-CU, and MeNB for Inter-gNB-DU Mobility using MCG SRB in EN-DC. The process is as follows: + +- The UE sends Downlink user data and Uplink user data to the Source gNB-DU. +- The Source gNB-DU sends **1. ULInformationTransferMRDC (containing NR RRC MeasurementReport)** to the MeNB. +- The MeNB sends **2. RRC TRANSFER** to the gNB-CU. +- The gNB-CU sends **3. UE CONTEXT MODIFICATION REQUEST** to the Source gNB-DU. +- The Source gNB-DU responds with **4. UE CONTEXT MODIFICATION RESPONSE** to the gNB-CU. +- The gNB-CU sends **5. UE CONTEXT SETUP REQUEST** to the Target gNB-DU. +- The Target gNB-DU responds with **6. UE CONTEXT SETUP RESPONSE** to the gNB-CU. +- The gNB-CU sends **7. UE CONTEXT MODIFICATION REQUEST** to the Source gNB-DU. +- The Source gNB-DU sends **Downlink Data Delivery Status** to the gNB-CU. +- The Source gNB-DU responds with **8. UE CONTEXT MODIFICATION RESPONSE** to the gNB-CU. +- The gNB-CU sends **9. SGNB MODIFICATION REQUIRED** to the MeNB. +- The MeNB sends **10. SGNB MODIFICATION REQUEST** to the gNB-CU. +- The gNB-CU responds with **11. SGNB MODIFICATION REQUEST ACKNOWLEDGE** to the MeNB. +- A horizontal bar indicates that **12. RRC Reconfiguration procedure is performed between the MeNB and the UE.** +- The gNB-CU sends **13. SGNB MODIFICATION CONFIRM** to the MeNB. +- The UE performs a **14. Random Access Procedure** with the Target gNB-DU. +- The Target gNB-DU sends **Downlink Data Delivery Status** and **Downlink User Data** to the gNB-CU. +- The UE sends Uplink user data to the Target gNB-DU. +- The Target gNB-DU sends Downlink user data to the UE. +- The Source gNB-DU sends **15. UE CONTEXT RELEASE COMMAND** to the gNB-CU. +- The gNB-CU responds with **16. UE CONTEXT RELEASE COMPLETE** to the Source gNB-DU. + +Sequence diagram for Inter-gNB-DU Mobility using MCG SRB in EN-DC. The diagram shows the interaction between UE, Source gNB-DU, Target gNB-DU, gNB-CU, and MeNB. It details the signaling steps for mobility, including RRC transfer, context modification, and data delivery status. + +**Figure 8.2.2.1-1: Inter-gNB-DU Mobility using MCG SRB in EN-DC** + +1. The UE sends an *ULInformationTransferMRDC* message to the MeNB. +2. The MeNB sends RRC TRANSFER message to the gNB-CU. +3. The gNB-CU may send UE CONTEXT MODIFICATION REQUEST message to the source gNB-DU to query the latest SCG configuration. +4. The source gNB-DU responds with an UE CONTEXT MODIFICATION RESPONSE message that includes full configuration information. +5. The gNB-CU sends an UE CONTEXT SETUP REQUEST message to the target gNB-DU to create an UE context and setup one or more data bearers. The UE CONTEXT SETUP REQUEST message includes a CG ConfigInfo. +6. The target gNB-DU responds the gNB-CU with an UE CONTEXT SETUP RESPONSE message. +7. The gNB-CU sends a UE CONTEXT MODIFICATION REQUEST message to the source gNB-DU indicating to stop the data transmission to the UE. The source gNB-DU also sends a Downlink Data Delivery Status frame to inform the gNB-CU about the unsuccessfully transmitted downlink data to the UE. +8. The source gNB-DU responds the gNB-CU with an UE CONTEXT MODIFICATION RESPONSE message. +9. The gNB-CU sends an SGNB MODIFICATION REQUIRED message to the MeNB. + +- 10/11. The MeNB Initiated SgNB Modification procedure may be triggered by the SgNB Initiated SgNB Modification procedure (e.g. to provide information such as data forwarding addresses, new SN security key, measurement gap, etc...). + 12. The MeNB and the UE perform RRC Connection Reconfiguration procedure. + 13. The MeNB sends an SgNB MODIFICATION CONFIRM message to the gNB-CU. + 14. Random Access procedure is performed at the target gNB-DU. The target gNB-DU sends a Downlink Data Delivery Status frame to inform the gNB-CU. Downlink packets, which may include PDCP PDUs not successfully transmitted in the source gNB-DU, are sent from the gNB-CU to the target gNB-DU. Downlink packets are sent to the UE. Also, uplink packets are sent from the UE, which are forwarded to the gNB-CU through the target gNB-DU. +- NOTE: It is up to gNB-CU implementation whether to start sending DL User Data to gNB-DU before or after reception of the Downlink Data Delivery Status. +15. The gNB-CU sends an UE CONTEXT RELEASE COMMAND message to the source gNB-DU. + 16. The source gNB-DU releases the UE context and responds the gNB-CU with an UE CONTEXT RELEASE COMPLETE message. + +#### 8.2.2.2 Inter-gNB-DU Mobility using SCG SRB (SRB3) + +This procedure is used for the case the UE moves from one gNB-DU to another gNB-DU when SCG SRB (SRB3) is available during EN-DC operation. The procedure is the same as inter-gNB-DU Mobility for intra-NR as defined in clause 8.2.1.1 but the UE CONTEXT SETUP REQUEST message includes a CG-ConfigInfo. + +#### 8.2.2.3 Inter-gNB-DU Conditional PSCell Change using MCG SRB without MN negotiation + +This procedure is used for the case where the UE moves from one gNB-DU to another gNB-DU within the same gNB-CU when only MCG SRB is available and the MN's configuration is not changed during EN-DC operation for conditional PSCell change. Figure 8.2.2.3-1 shows the inter-gNB-DU conditional PSCell change procedure using MCG SRB in EN-DC. + +![Sequence diagram for Inter-gNB-DU Conditional PSCell Change using MCG SRB without MN negotiation in EN-DC. The diagram shows interactions between UE, Source gNB-DU, Candidate gNB-DU, gNB-CU, and MeNB. It details the flow of RRC messages, user data, and context modifications for a conditional handover.](32ff77da4286b58c4778033acaa10836_img.jpg) + +The sequence diagram illustrates the following steps: + +- Initial State:** Downlink and Uplink user data are being transferred between the UE and the Source gNB-DU. +- Step 1:** The UE sends a *ULInformationTransferMRDC* (containing NR RRC MeasurementReport) to the Source gNB-DU. +- Step 2:** The Source gNB-DU sends an *RRC TRANSFER* message to the MeNB. +- Step 3:** The MeNB sends a *UE CONTEXT MODIFICATION REQUEST* to the Source gNB-DU. +- Step 4:** The Source gNB-DU responds with a *UE CONTEXT MODIFICATION RESPONSE*. +- Step 5:** The Source gNB-DU sends a *UE CONTEXT SETUP REQUEST* (Conditional Inter-DU Mobility Information) to the Candidate gNB-DU. +- Step 6:** The Candidate gNB-DU responds with a *UE CONTEXT SETUP RESPONSE* (Requested Target Cell ID). +- Step 7:** The Candidate gNB-DU sends an *SGNB MODIFICATION REQUIRED* (*RRReconfiguration*) message to the gNB-CU. +- Step 8:** A box indicates that the *RRC Reconfiguration/Complete* procedure is performed between the MeNB and the UE. +- Step 9:** The gNB-CU sends an *SGNB MODIFICATION CONFIRM* (*RRReconfigurationComplete*) message to the Candidate gNB-DU. +- Step 10:** A box indicates that the execution condition(s) are fulfilled. +- Step 11:** The UE initiates a *Random Access Procedure* with the Candidate gNB-DU. +- Step 12:** The Candidate gNB-DU sends a *Downlink Data Delivery Status* and *ACCESS SUCCESS* message to the gNB-CU. +- Step 13:** The gNB-CU sends a *ULInformationTransferMRDC* (containing *RRReconfigurationComplete*) to the Source gNB-DU. +- Step 14:** The Source gNB-DU sends an *RRC TRANSFER* (*RRReconfigurationComplete*) message to the MeNB. +- Step 15:** The MeNB sends a *UE CONTEXT MODIFICATION REQUEST* to the Source gNB-DU. +- Step 16:** The Source gNB-DU sends a *Downlink Data Delivery Status* message to the gNB-CU. +- Step 17:** The Source gNB-DU sends a *UE CONTEXT MODIFICATION RESPONSE* to the MeNB. +- Step 18:** The MeNB sends a *UE CONTEXT RELEASE COMMAND* to the Source gNB-DU. +- Step 19:** The Source gNB-DU sends a *UE CONTEXT RELEASE COMPLETE* message to the MeNB. +- Final State:** Downlink and Uplink user data are transferred between the UE and the Candidate gNB-DU. + +Sequence diagram for Inter-gNB-DU Conditional PSCell Change using MCG SRB without MN negotiation in EN-DC. The diagram shows interactions between UE, Source gNB-DU, Candidate gNB-DU, gNB-CU, and MeNB. It details the flow of RRC messages, user data, and context modifications for a conditional handover. + +**Figure 8.2.2.3-1: Inter-gNB-DU Conditional PSCell Change using MCG SRB without MN negotiation in EN-DC** + +- The steps 1-4 are as defined in clause 8.2.2.1. +- The gNB-CU sends an *UE CONTEXT SETUP REQUEST* message to the candidate gNB-DU to create an UE context and setup one or more data bearers. The *UE CONTEXT SETUP REQUEST* message is sent for each candidate cell and includes a *CG-ConfigInfo*. +- The candidate gNB-DU responds the gNB-CU with an *UE CONTEXT SETUP RESPONSE* message including the target cell ID that was requested from the gNB-CU. The response message is sent for each requested candidate cell. +- The gNB-CU sends an *SGNB MODIFICATION REQUIRED* message to the MeNB, which includes a generated *RRReconfiguration* message. +- The MeNB and the UE perform *RRC Connection Reconfiguration/Complete* procedure. + +9. The MeNB sends an SGNB MODIFICATION CONFIRM message to the gNB-CU, to convey the received *RRCReconfigurationComplete* message at step 8. + 10. An execution condition to trigger initiation of conditional PSCell change is fulfilled. + 11. Random Access procedure is performed at the candidate gNB-DU, which becomes the target gNB-DU if successful. The target gNB-DU sends a Downlink Data Delivery Status frame to inform the gNB-CU. The target gNB-DU also sends an ACCESS SUCCESS message to inform the gNB-CU of which cell the UE has successfully accessed. + - 12-13. The UE responds with an *RRCReconfigurationComplete* message (embedded in an *ULInformationTransferMRDC* message), which the MeNB forwards to the gNB-CU via an RRC TRANSFER message. + 14. The gNB-CU sends a UE CONTEXT MODIFICATION REQUEST message to the source gNB-DU and indicates to stop the data transmission for the UE. The source gNB-DU sends a Downlink Data Delivery Status frame to inform the gNB-CU about the unsuccessfully transmitted downlink data to the UE. Downlink packets, which may include PDCP PDUs not successfully transmitted in the source gNB-DU, are sent from the gNB-CU to the target gNB-DU. Downlink packets are sent to the UE. Also, uplink packets are sent from the UE, which are forwarded to the gNB-CU through the target gNB-DU. +- NOTE: The step 14 may happen before step 13, as soon as the gNB-CU knows which cell the UE has successfully accessed. +- NOTE: The gNB-CU may initiate UE Context Release procedure toward the other signalling connections or other candidate target gNB-DUs, if any, to cancel conditional PSCell change for the UE. +15. The source gNB-DU responds to the gNB-CU with the UE CONTEXT MODIFICATION RESPONSE message. + - 16-17. The steps 16-17 are as defined in steps 11-12 in clause 8.2.1.1. + +### 8.2.3 Intra-CU topology adaptation procedure + +#### 8.2.3.1 Intra-CU topology adaptation procedure in SA + +During the intra-CU topology adaptation in SA, both the source and the target parent node are served by the same IAB-donor-CU. The target parent node may use a different IAB-donor-DU than the source parent node. The source path may have common nodes with the target path. Figure 8.2.3.1-1 shows an example of the topology adaptation procedure, where the target parent node uses a different IAB-donor-DU than the one used by the source parent node. + +![Sequence diagram of IAB intra-CU topology adaptation procedure. The diagram shows the interaction between a UE, a Migrating IAB-node, Source Path (Source Parent IAB-node, Intermediate hop IAB-node, Source IAB-donor-DU), Target Path (Target Parent IAB-node, Intermediate hop IAB-node, Target IAB-donor-DU), and an IAB-donor-CU. The procedure involves measurement reporting, context setup, RRC reconfiguration, random access, and path redirection.](4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg) + +The diagram illustrates the IAB intra-CU topology adaptation procedure. It features the following components and steps: + +- UE**: User Equipment. +- Migrating IAB-node**: The node that is moving from the source path to the target path. +- Source Path**: Comprises the **Source Parent IAB-node**, an **Intermediate hop IAB-node on the source path**, and the **Source IAB-donor-DU**. +- Target Path**: Comprises the **Target Parent IAB-node**, an **Intermediate hop IAB-node on the target path**, and the **Target IAB-donor-DU**. +- IAB-donor-CU**: Central Unit of the IAB donor. + +**Sequence of Messages:** + +- 1. MeasurementReport**: From Migrating IAB-node to Source Parent IAB-node. +- 2. UL RRC MESSAGE TRANSFER (MeasurementReport)**: From Source Parent IAB-node to IAB-donor-CU. +- 3. UE CONTEXT SETUP REQUEST**: From IAB-donor-CU to Target Parent IAB-node. +- 4. UE CONTEXT SETUP RESPONSE**: From Target Parent IAB-node to IAB-donor-CU. +- 5. UE CONTEXT MODIFICATION REQUEST (RRCReconfiguration)**: From IAB-donor-CU to Source Parent IAB-node. +- 6. RRCReconfiguration**: From Source Parent IAB-node to Migrating IAB-node. +- 7. UE CONTEXT MODIFICATION RESPONSE**: From Source Parent IAB-node to IAB-donor-CU. +- 8. Random Access Procedure**: Between Migrating IAB-node and Target Parent IAB-node. +- 9. RRCReconfigurationComplete**: From Migrating IAB-node to Target Parent IAB-node. +- 10. UL RRC MESSAGE TRANSFER (RRCReconfigurationComplete)**: From Target Parent IAB-node to IAB-donor-CU. +- 11. Configuration of BH RLC channel, BAP route and mapping rules along target path between migrating IAB-node and target IAB-donor-DU via target parent IAB-node.**: A block message from IAB-donor-CU to Target Parent IAB-node. +- 12. Redirection of migrating IAB-node-DU's F1 association to new TNL address(es).**: A block message from IAB-donor-CU to Target Parent IAB-node. +- 13. UE CONTEXT RELEASE COMMAND**: From IAB-donor-CU to Source Parent IAB-node. +- 14. UE CONTEXT RELEASE COMPLETE**: From Source Parent IAB-node to IAB-donor-CU. +- 15. Release of BAP route along source-path between migrating IAB-node and source IAB-donor-DU via source parent IAB-node.**: A block message from IAB-donor-CU to Source Parent IAB-node. + +**Data Flow:** + +- Downlink user data**: Indicated by green dashed arrows from IAB-donor-CU towards the UE. +- Uplink user data**: Indicated by green dashed arrows from the UE towards IAB-donor-CU. + +Sequence diagram of IAB intra-CU topology adaptation procedure. The diagram shows the interaction between a UE, a Migrating IAB-node, Source Path (Source Parent IAB-node, Intermediate hop IAB-node, Source IAB-donor-DU), Target Path (Target Parent IAB-node, Intermediate hop IAB-node, Target IAB-donor-DU), and an IAB-donor-CU. The procedure involves measurement reporting, context setup, RRC reconfiguration, random access, and path redirection. + +Figure 8.2.3.1-1: IAB intra-CU topology adaptation procedure + +- The migrating IAB-MT sends a *MeasurementReport* message to the source parent node IAB-DU. This report is based on a Measurement Configuration the migrating IAB-MT received from the IAB-donor-CU before. +- The source parent node IAB-DU sends an UL RRC MESSAGE TRANSFER message to the IAB-donor-CU to convey the received *MeasurementReport*. +- The IAB-donor-CU sends a UE CONTEXT SETUP REQUEST message to the target parent node IAB-DU to create the UE context for the migrating IAB-MT and set up one or more bearers. These bearers can be used by the migrating IAB-MT for its own signalling, and, optionally, data traffic. +- The target parent node IAB-DU responds to the IAB-donor-CU with a UE CONTEXT SETUP RESPONSE message. +- The IAB-donor-CU sends a UE CONTEXT MODIFICATION REQUEST message to the source parent node IAB-DU, which includes a generated *RRCReconfiguration* message. The *RRCReconfiguration* message includes a default BH RLC channel and a default BAP Routing ID configuration for UL F1-C/non-F1 traffic mapping on the target path. It may include additional BH RLC channels. This step may also include allocation of TNL address(es) that is (are) routable via the target IAB-donor-DU. The new TNL address(es) may be included in the *RRCReconfiguration* message as a replacement for the TNL address(es) that is (are) routable via the source IAB-donor-DU. In case IPsec tunnel mode is used to protect the F1 and non-F1 traffic, the allocated TNL address is outer IP address. The TNL address replacement is not necessary if the source and target paths use the same IAB-donor-DU. The *Transmission Action Indicator* in the UE CONTEXT MODIFICATION REQUEST message indicates to stop the data transmission to the migrating IAB-node. +- The source parent node IAB-DU forwards the received *RRCReconfiguration* message to the migrating IAB-MT. + +7. The source parent node IAB-DU responds to the IAB-donor-CU with the UE CONTEXT MODIFICATION RESPONSE message. +8. A Random Access procedure is performed at the target parent node IAB-DU. +9. The migrating IAB-MT responds to the target parent node IAB-DU with an *RRCREconfigurationComplete* message. +10. The target parent node IAB-DU sends an UL RRC MESSAGE TRANSFER message to the IAB-donor-CU to convey the received *RRCREconfigurationComplete* message. Also, uplink packets can be sent from the migrating IAB-MT, which are forwarded to the IAB-donor-CU through the target parent node IAB-DU. These UL packets belong to the IAB-MT's own signalling and, optionally, data traffic. +11. The IAB-donor-CU configures BH RLC channels and BAP-sublayer routing entries on the target path between the target parent IAB-node and target IAB-donor-DU as well as DL mappings on the target IAB-donor-DU for the migrating IAB-node's target path. These configurations may be performed at an earlier stage, e.g. immediately after step 3, or before step 3. The IAB-donor-CU may establish additional BH RLC channels to the migrating IAB-MT via RRC message. +12. The F1-C connections are switched to use the migrating IAB-node's new TNL address(es), IAB-donor-CU updates the UL BH information associated to each GTP-tunnel to migrating IAB-node. This step may also update UL FTEID and DL FTEID associated to each GTP-tunnel. All F1-U tunnels are switched to use the migrating IAB-node's new TNL address(es). This step may use non-UE associated signaling in E1 and/or F1 interface to provide updated UP configuration for F1-U tunnels of multiple connected UEs or child IAB-MTs. The IAB-donor-CU may also update the UL BH information associated with non-UP traffic. Implementation must ensure the avoidance of potential race conditions, i.e. no conflicting configurations are concurrently performed using UE-associated and non-UE-associated procedures. + +In case IPsec tunnel mode is used for TNL protection, the IAB-node may use MOBIKE (IETF RFC 4555 [29]) to migrate the IPsec tunnel to the new IP outer addresses. After the completion of the MOBIKE procedure, the IAB-DU initiates an FIAP gNB-DU Configuration Update procedure from which the IAB-donor-CU can conclude whether the existing inner IP address(es) (e.g. for SCTP association) and the DL F-TEID can be reused. + +If new TNL addresses for F1-C traffic are configured, new SCTP association(s) between the migrating IAB-node and the IAB-donor-CU may be established using the new TNL address information of the migrating IAB-node. The migrating IAB-node sends an FIAP gNB-DU CONFIGURATION UPDATE message to the IAB-donor-CU, which may include new (outer) IP addresses and corresponding new (inner) IP address for the F1-U traffic to be switched to the target path. + +13. The IAB-donor-CU sends a UE CONTEXT RELEASE COMMAND message to the source parent node IAB-DU. +14. The source parent node IAB-DU releases the migrating IAB-MT's context and responds to the IAB-donor-CU with a UE CONTEXT RELEASE COMPLETE message. +15. The IAB-donor-CU releases BH RLC channels and BAP-sublayer routing entries on the source path between source parent IAB-node and source IAB-donor-DU. + +NOTE: In case that the source path and target path have common nodes, the BH RLC channels and BAP-sublayer routing entries of those nodes may not need to be released in Step 15. + +Steps 11, 12 and 15 should also be performed for the migrating IAB-node's descendant nodes, as follows: + +The IAB-donor-CU may allocate new TNL address(es) that is (are) routable via the target IAB-donor-DU to the descendent nodes via *RRCREconfiguration* message. + +If needed, the IAB-donor-CU may also provide a new default UL mapping which includes a default BH RLC channel and a default BAP Routing ID for UL F1-C/non-F1 traffic on the target path, to the descendant nodes via *RRCREconfiguration* message. + +If needed, the IAB-donor-CU configures BH RLC channels, BAP-sublayer routing entries and BH RLC channel mappings on the target path for the descendant nodes in the same manner as described for the migrating IAB-node in step 11. + +The descendant nodes switch their F1-C connections and F1-U tunnels to new TNL addresses that are anchored at the new IAB-donor-DU, in the same manner as described for the migrating IAB-node in step 12. + +Based on implementation, these steps can be performed after or in parallel with the handover of the migrating IAB-node. + +To enable performing these steps in parallel, the IAB-donor-CU sends the RRCReconfiguration message with the new TNL address(es) and the new default BAP configuration to the descendent node while the migrating IAB-MT is still connected with source parent node, for example, before Step 5. In this case, the UE CONTEXT MODIFICATION REQUEST message carrying this RRCReconfiguration message includes a conditional delivery indication for the descendent node's parent IAB-DU. Based on this indication, the parent IAB-DU retains the RRCReconfiguration message until the conditions for delivery are met, as specified in TS 38.473 [4]. The IAB-donor-CU may further configure the BAP-sublayer routing entries on the migrating IAB-node and the descendant nodes while the migrating IAB-MT is still connected with the source parent node. + +- NOTE: In upstream direction, in-flight packets between the source parent node and the IAB-donor-CU can be delivered even after the target path is established. +- NOTE: In-flight downlink data in the source path may be discarded, up to implementation via the NR user plane protocol (TS 38.425 [24]). +- NOTE: The IAB-donor-CU can determine the unsuccessfully transmitted downlink data over the backhaul link by implementation. + +#### 8.2.3.2 Intra-CU topology adaptation procedure in NSA using MCG SRB + +This procedure is used when the migrating IAB-MT moves from source parent node to target parent node within the same IAB-donor-CU while only MCG SRB is available for IAB-node during EN-DC operation. The target parent node may use a different IAB-donor-DU than the one used by the source parent node. The source path may have common nodes with the target path. Figure 8.2.3.2-1 shows the topology adaptation procedure using MCG SRB of IAB-MT in EN-DC, where the target parent node uses a different IAB-donor-DU than the source parent node. + +![Sequence diagram of IAB intra-CU topology adaptation procedure using MCG SRB in EN-DC. The diagram shows the interaction between a UE, a Migrating IAB-node, Source Path nodes (Source Parent IAB-node, Intermediate hop IAB-node, Source IAB-donor-DU), Target Path nodes (Target Parent IAB-node, Intermediate hop IAB-node, Target IAB-donor-DU), an IAB-donor-CU, and a MeNB. The procedure involves signaling for context modification, context setup, SGNB modification, RRC reconfiguration, random access, and final release of the source path.](8d66c9c295023a1380f9986d3663bb1e_img.jpg) + +The diagram illustrates the sequence of messages for IAB intra-CU topology adaptation. It starts with the Migrating IAB-node sending a *ULInformationTransferMRDC* (containing NR RRC *MeasurementReport*) to the MeNB. The MeNB responds with *2.RRC TRANSFER* to the IAB-donor-CU. The IAB-donor-CU then sends *3.UE CONTEXT MODIFICATION REQUEST* to the Source Parent IAB-node, which replies with *4.UE CONTEXT MODIFICATION RESPONSE*. Next, *5.UE CONTEXT SETUP REQUEST* and *6.UE CONTEXT SETUP RESPONSE* are exchanged between the IAB-donor-CU and the Target Parent IAB-node. The IAB-donor-CU sends *7.UE CONTEXT MODIFICATION REQUEST* to the Source Parent IAB-node, which responds with *8.UE CONTEXT MODIFICATION RESPONSE* and a *Downlink Data Delivery Status*. The IAB-donor-CU then sends *9.SGNB MODIFICATION REQUIRED* to the MeNB, which responds with *10.SGNB MODIFICATION REQUEST* and *11.SGNB MODIFICATION REQUEST ACKNOWLEDGE*. A message indicates that the *12.RRC Reconfiguration procedure is performed between the MeNB and the migrating IAB-MT*. The IAB-donor-CU sends *13.SGNB MODIFICATION CONFIRM* to the MeNB. The Migrating IAB-node performs *14.Random Access procedure* with the Target Parent IAB-node. Subsequent messages include *15.Configuration of BH RLC channel, BAP route and mapping rules along target path between migrating IAB-node and target IAB-donor-DU via target parent IAB-node*, *16.Redirection of migrating IAB-node-DU's F1 association to new TNL address(es)*, *17.UE CONTEXT RELEASE COMMAND*, *18.UE CONTEXT RELEASE COMPLETE*, and finally *19:Release of BAP route along source-path between migrating IAB-node and source IAB-donor-DU via source parent IAB-node*. Green dashed arrows represent user data flow (Downlink and Uplink) throughout the process. + +Sequence diagram of IAB intra-CU topology adaptation procedure using MCG SRB in EN-DC. The diagram shows the interaction between a UE, a Migrating IAB-node, Source Path nodes (Source Parent IAB-node, Intermediate hop IAB-node, Source IAB-donor-DU), Target Path nodes (Target Parent IAB-node, Intermediate hop IAB-node, Target IAB-donor-DU), an IAB-donor-CU, and a MeNB. The procedure involves signaling for context modification, context setup, SGNB modification, RRC reconfiguration, random access, and final release of the source path. + +**Figure 8.2.3.2-1: IAB intra-CU topology adaptation procedure using MCG SRB in EN-DC** + +1. The migrating IAB-MT sends an *ULInformationTransferMRDC* message to the MeNB +2. The MeNB sends RRC TRANSFER message to the IAB-donor-CU. +3. The IAB-donor-CU may send UE CONTEXT MODIFICATION REQUEST message to the source parent node IAB-DU, to query the latest SCG configuration. +4. The source parent node IAB-DU responds with a UE CONTEXT MODIFICATION RESPONSE message that includes full configuration information. +5. The IAB-donor-CU sends a UE CONTEXT SETUP REQUEST message to the target parent node IAB-DU, to create a UE context for migrating IAB-MT and set up one or more bearers. These bearers can be used by the migrating IAB-MT for its own signalling, and, optionally, data traffic. The UE CONTEXT SETUP REQUEST message includes *CG-ConfigInfo*. +6. The target parent node IAB-DU responds to the IAB-donor-CU with a UE CONTEXT SETUP RESPONSE message. +7. The IAB-donor-CU sends a UE CONTEXT MODIFICATION REQUEST message to the source parent node IAB-DU, this message includes the *Transmission Action Indicator* IE, which instructs the source parent node IAB-DU to stop the data transmission to the migrating IAB-node. The source parent node IAB-DU also sends a *Downlink Data Delivery Status* frame to inform the IAB-donor-CU about the unsuccessfully transmitted downlink data to the migrating IAB-node. + +8. The source parent node IAB-DU responds to the IAB-donor-CU with a UE CONTEXT MODIFICATION RESPONSE message. +9. The IAB-donor-CU sends an SGNB MODIFICATION REQUIRED message to the MeNB. +- 10/11. The MeNB initiated SgNB Modification procedure may be triggered by the SgNB initiated SgNB Modification procedure (e.g. to provide information such as data forwarding addresses, new SN security key, measurement gap, etc.). +12. The MeNB and the migrating IAB-MT perform RRC Connection Reconfiguration procedure. The *RRCConnectionReconfiguration* message includes information as described for the intra-CU topology adaptation procedure in SA in clause 8.2.3.1. +13. The MeNB sends an SGNB MODIFICATION CONFIRM message to the IAB-donor-CU. +14. The migrating IAB-MT performs Random Access procedure at the target parent node IAB-DU. +- 15-19. The remaining steps of the procedure follow the steps 11-15 of the intra-CU topology adaptation procedure in SA scenario, as defined in clause 8.2.3.1. The main difference is that the RRC message for the migrating IAB-node, if involved, will be transmitted using the MCG SRB. + +#### 8.2.3.3 Intra-CU topology adaptation procedure in NSA using SCG SRB (SRB3) + +This procedure is used when the migrating IAB-MT moves from source parent node to target parent node within the same IAB-donor-CU, when SCG SRB (SRB3) is available for IAB-node during EN-DC operation. The target parent node may use a different IAB-donor-DU than the source parent node. The source path may have common nodes with the target path. The procedure is the same as intra-CU topology adaptation procedure in SA scenario as defined in clause 8.2.3.1 but the UE CONTEXT SETUP REQUEST message includes *CG-ConfigInfo* in step 3. + +### 8.2.4 Intra-CU topological redundancy procedure + +The intra-CU topological redundancy procedure enables the establishment and release of redundant paths in the IAB-topology underneath the same IAB-donor-CU. The redundant paths may use different IAB-donor-DUs. They may also have common intermediate nodes. Since topological redundancy uses NR-DC for the IAB-MT, it is only supported for IAB-nodes operating in SA mode. + +Figure 8.2.4-1 shows an example for an IAB topology, where one IAB-node, referred to as the dual-connecting IAB-node, has two paths towards the IAB-donor via different IAB-donor-DUs. + +![Figure 8.2.4-1: Example for IAB topology with two redundant paths. The diagram shows an IAB-donor at the top containing CU-CP and CU-UP. Below it are two parallel paths. The first path consists of DU 1 (First-path IAB-donor DU), a First-path IAB-node (IAB-MT/IAB-DU), and a First parent IAB-node (IAB-MT/IAB-DU). The second path consists of DU 2 (Second-path IAB-donor DU), a Second-path IAB-node (IAB-MT/IAB-DU), and a Second parent IAB-node (IAB-MT/IAB-DU). Both parent IAB-nodes connect to a Dual-connecting IAB-node (MT/DU) via MCG and SCG links. This dual-connecting node is connected to a UE via an NR Uu link.](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +Figure 8.2.4-1: Example for IAB topology with two redundant paths. The diagram shows an IAB-donor at the top containing CU-CP and CU-UP. Below it are two parallel paths. The first path consists of DU 1 (First-path IAB-donor DU), a First-path IAB-node (IAB-MT/IAB-DU), and a First parent IAB-node (IAB-MT/IAB-DU). The second path consists of DU 2 (Second-path IAB-donor DU), a Second-path IAB-node (IAB-MT/IAB-DU), and a Second parent IAB-node (IAB-MT/IAB-DU). Both parent IAB-nodes connect to a Dual-connecting IAB-node (MT/DU) via MCG and SCG links. This dual-connecting node is connected to a UE via an NR Uu link. + +Figure 8.2.4-1: Example for IAB topology with two redundant paths + +![Figure 8.2.4-2: Procedure for establishment of redundant path in IAB topology. This sequence diagram shows the interaction between a UE, Dual-connecting IAB-node, First parent IAB-node, Intermediate hop IAB-node on the first path, First path IAB-donor-DU, Second parent IAB-node, Intermediate hop IAB-node on the second path, Second path IAB-donor-DU, and IAB-donor-CU. The process includes: 1. MeasurementReport from UE to Dual-connecting IAB-node; 2. UL RRC MESSAGE TRANSFER (MeasurementReport) from Dual-connecting IAB-node to IAB-donor-CU; 3. UE CONTEXT SETUP REQUEST from IAB-donor-CU to Second parent IAB-node; 4. UE CONTEXT SETUP RESPONSE from Second parent IAB-node to IAB-donor-CU; 5. DL RRC MESSAGE TRANSFER (RRCREconfiguration) from IAB-donor-CU to Dual-connecting IAB-node; 6. RRCReconfiguration from Dual-connecting IAB-node to UE; 7. RRCReconfigurationComplete from UE to Dual-connecting IAB-node; 8. UL RRC MESSAGE TRANSFER (RRCREconfigurationComplete) from Dual-connecting IAB-node to IAB-donor-CU; 9. Random Access procedure between Dual-connecting IAB-node and Second parent IAB-node; 10. Configuration of BAP route and mapping rules along the second path between dual-connecting IAB-node and the second path IAB-donor-DU via the second parent IAB-node; 11. Addition of new TNL address(es) to dual-connecting IAB-node DU's F1-C associations; 12. UE CONTEXT MODIFICATION REQUEST from IAB-donor-CU to Dual-connecting IAB-node; 13. UE CONTEXT MODIFICATION RESPONSE from Dual-connecting IAB-node to IAB-donor-CU. Green dashed arrows indicate downlink and uplink user data flows.](036c200da9b64c3eb5aae2d67bb53e1f_img.jpg) + +Figure 8.2.4-2: Procedure for establishment of redundant path in IAB topology. This sequence diagram shows the interaction between a UE, Dual-connecting IAB-node, First parent IAB-node, Intermediate hop IAB-node on the first path, First path IAB-donor-DU, Second parent IAB-node, Intermediate hop IAB-node on the second path, Second path IAB-donor-DU, and IAB-donor-CU. The process includes: 1. MeasurementReport from UE to Dual-connecting IAB-node; 2. UL RRC MESSAGE TRANSFER (MeasurementReport) from Dual-connecting IAB-node to IAB-donor-CU; 3. UE CONTEXT SETUP REQUEST from IAB-donor-CU to Second parent IAB-node; 4. UE CONTEXT SETUP RESPONSE from Second parent IAB-node to IAB-donor-CU; 5. DL RRC MESSAGE TRANSFER (RRCREconfiguration) from IAB-donor-CU to Dual-connecting IAB-node; 6. RRCReconfiguration from Dual-connecting IAB-node to UE; 7. RRCReconfigurationComplete from UE to Dual-connecting IAB-node; 8. UL RRC MESSAGE TRANSFER (RRCREconfigurationComplete) from Dual-connecting IAB-node to IAB-donor-CU; 9. Random Access procedure between Dual-connecting IAB-node and Second parent IAB-node; 10. Configuration of BAP route and mapping rules along the second path between dual-connecting IAB-node and the second path IAB-donor-DU via the second parent IAB-node; 11. Addition of new TNL address(es) to dual-connecting IAB-node DU's F1-C associations; 12. UE CONTEXT MODIFICATION REQUEST from IAB-donor-CU to Dual-connecting IAB-node; 13. UE CONTEXT MODIFICATION RESPONSE from Dual-connecting IAB-node to IAB-donor-CU. Green dashed arrows indicate downlink and uplink user data flows. + +Figure 8.2.4-2: Procedure for establishment of redundant path in IAB topology + +Figure 8.2.4-2 shows the procedure for the establishment of the second path. This procedure has the following steps: + +1. The dual-connecting IAB-MT sends a *MeasurementReport* message to the first parent node IAB-DU. This report is based on a Measurement Configuration the dual-connecting IAB-MT received from the IAB-donor-CU before. +2. The first parent node IAB-DU sends an UL RRC MESSAGE TRANSFER message to the IAB-donor-CU to convey the received *MeasurementReport*. +3. The IAB-donor-CU sends the UE CONTEXT SETUP REQUEST message to the second parent node IAB-DU, to create the UE context for the dual-connecting IAB-MT and to set up one or more bearers. These bearers can be used by the dual-connecting IAB-MT for its own signalling, and, optionally, data traffic. +4. The second parent node IAB-DU responds to the IAB-donor-CU with a UE CONTEXT SETUP RESPONSE message. +5. The IAB-donor-CU sends a DL RRC MESSAGE TRANSFER message to the first parent node IAB-DU, which includes a generated *RRCReconfiguration* message. The *RRCReconfiguration* message may contain one or more TNL address(es) for the dual-connecting IAB-DU, which are anchored at the second-path IAB-donor-DU. The IAB-donor-CU can proactively obtain these TNL addresses from the second-path IAB-donor-DU. In case IPsec tunnel mode is used to protect the F1 and non-F1 traffic, the allocated TNL address is the outer IP address. The TNL address allocation is not necessary if the first and second paths use the same IAB-donor-DU. +6. The first parent node IAB-DU forwards the received *RRCReconfiguration* message to the dual-connecting IAB-MT. +7. The dual-connecting IAB-MT responds to the first parent node IAB-DU with an *RRCReconfigurationComplete* message. +8. The first parent node IAB-DU sends an UL RRC MESSAGE TRANSFER message to the IAB-donor-CU, to convey the received *RRCReconfigurationComplete* message. +9. A Random Access procedure is performed at the second parent node IAB-DU. +10. The IAB-donor-CU configures BH RLC channels and BAP-layer route entries on the second path between dual-connecting IAB-node and second-path IAB-donor-DU. These configurations may be performed at an earlier stage, e.g. immediately after step 3. +11. The new TNL addresses allocated in step 5 (if any) are added to the dual-connecting IAB-DU's F1-C association(s) with the IAB-donor-CU. The IAB-donor-CU may configure new UL BH information on the second path for F1AP messages. + +If new TNL addresses for F1-C traffic are configured, new SCTP association(s) between the dual-connecting IAB-node and the IAB-donor-CU may be established using the new TNL address information of the dual-connecting IAB-node. The dual-connecting IAB-node sends an F1AP gNB-DU CONFIGURATION UPDATE message to the IAB-donor-CU, which may include new (outer) IP addresses and corresponding new (inner) IP address for the F1-U traffic to be switched to the target path. +12. The IAB-donor-CU may migrate the F1-U tunnels it has with the dual-connecting IAB-DU from the first path to the second path via the UE CONTEXT MODIFICATION REQUEST message. +13. The dual-connectivity IAB-DU replies with a UE CONTEXT MODIFICATION RESPONSE message. + +Steps 12 and 13 can be performed for a subset of UE bearers, e.g., to balance the load between the first and the second path. + +In case the second path is used for the dual-connecting IAB-node's descendant node(s), Steps 10 and 11 are also performed for the descendant node(s), as follows: + +When the second path uses a different IAB-donor-DU, the IAB-donor-CU shall configure the descendent IAB-DU(s) with one or more new TNL addresses, which are anchored on the IAB-donor-DU of the second path. + +If needed, the IAB-donor-CU configures BH RLC channels, BAP-layer route entries on the target path for the descendant nodes and the BH RLC channel mappings on the descendant nodes in the same manner as described for the dual-connecting IAB-node in step 10. + +The descendant nodes' new TNL addresses (if any) are added to the descendant node IAB-DU's F1-C association(s) with the IAB-donor-CU. The IAB-donor-CU may configure UL BH information for the second path to carry FIAP messages. + +The IAB-donor-CU may migrate the F1-U tunnels it has with the dual-connecting IAB-node's descendant node(s) from the first path to the second path, as described for step 12. + +Based on implementation, these steps can be performed after or in parallel with the redundant path addition of the dual connecting IAB-node. + +The IAB-donor-CU may initiate the release of the redundant path by releasing the BAP routing entries and modifying/releasing the BH RLC channels on that path. + +### 8.2.5 Intra-CU Backhaul RLF recovery for IAB-nodes in SA mode + +The intra-CU backhaul RLF recovery procedure for IAB-nodes in SA mode enables migration of an IAB-node to another parent node underneath the same IAB-donor-CU, when the IAB-MT declares a backhaul RLF. The declaration of backhaul RLF is described in TS 38.331 [23]. + +NOTE: Determination of whether the recovery occurs at the same or at a different IAB-donor-CU is up to implementation. + +Figure 8.2.5-1 shows an example of the BH RLF recovery procedure for an IAB-node in SA mode. In this example, the IAB-node changes from its initial parent node to a new parent node, where the new parent node is served by an IAB-donor-DU different than the one serving its initial parent node. + +![Sequence diagram of IAB intra-CU backhaul RLF recovery procedure for an IAB-node in SA mode. The diagram shows the flow of user data and control messages between a UE, a Recovery IAB-node, an Initial Path (Initial Parent IAB-node, Intermediate hop IAB-node on the initial path, Initial IAB-donor-DU), a Recovery Path (New Parent IAB-node, Intermediate hop IAB-node on the new path, New IAB-donor-DU), and an IAB-donor-CU. The procedure involves three main steps: 1. Determination of BH RLF on initial path, 2. RRC Re-establishment at recovery parent IAB-node DU, and 3. Same as steps 11-15 of intra-CU topology adaptation procedure. Downlink user data flows from the IAB-donor-CU through the recovery path to the UE. Uplink user data flows from the UE through the recovery path to the IAB-donor-CU.](f5d2a88925807080157c7cfb1d41cf0b_img.jpg) + +Sequence diagram of IAB intra-CU backhaul RLF recovery procedure for an IAB-node in SA mode. The diagram shows the flow of user data and control messages between a UE, a Recovery IAB-node, an Initial Path (Initial Parent IAB-node, Intermediate hop IAB-node on the initial path, Initial IAB-donor-DU), a Recovery Path (New Parent IAB-node, Intermediate hop IAB-node on the new path, New IAB-donor-DU), and an IAB-donor-CU. The procedure involves three main steps: 1. Determination of BH RLF on initial path, 2. RRC Re-establishment at recovery parent IAB-node DU, and 3. Same as steps 11-15 of intra-CU topology adaptation procedure. Downlink user data flows from the IAB-donor-CU through the recovery path to the UE. Uplink user data flows from the UE through the recovery path to the IAB-donor-CU. + +Figure 8.2.5-1: IAB intra-CU backhaul RLF recovery procedure for an IAB-node in SA mode + +1. The IAB-MT declares BH RLF for the MCG as described in TS 38.331 [23], clause 5.3.10.3. +2. The IAB-MT undergoing recovery from RLF conducts the RRC re-establishment procedure at the new parent node, as defined in clause 8.7. In this procedure, the IAB-donor-CU may provide new TNL address(es), which is(are) anchored at the new IAB-donor-DU, to the IAB-MT via RRC signalling. Furthermore, the IAB-donor-CU may also provide a new default UL mapping which includes a default BH RLC channel and a default BAP Routing ID for UL F1-C/non-F1 traffic on the target path, to the IAB-node undergoing recovery from RLF via *RRCREconfiguration* message in this procedure. +3. The remaining part of the procedure follows the steps 11-15 of the intra-CU topology adaptation procedure defined in clause 8.2.3.1. + +Descendant node(s) of the IAB-node undergoing recovery from RLF may also need to switch to new TNL address(es) anchored in the target-path IAB-donor-DU following the same mechanism as described for IAB intra-CU topology adaptation procedure in clause 8.2.3.1. The descendant node(s) may also be provided with new default UL mapping via RRC, after the IAB-node undergoing recovery from RLF connects the IAB-donor-CU via the recovery path. + +## 8.3 Mechanism of centralized retransmission of lost PDUs + +### 8.3.1 Centralized Retransmission in Intra gNB-CU Cases + +This mechanism allows to perform the retransmission of the PDCP PDUs that are not delivered by a gNB-DU (gNB-DU1) because the corresponding radio links toward the UE are subject to outage. When such outage occurs, the gNB-DU affected by outage informs the gNB-CU of such event. The gNB-CU can switch transmission of data traffic, as well as perform retransmission of undelivered PDCP PDUs, from the gNB-DU affected by outage to other available gNB-DUs (e.g. gNB-DU2 in Figure 8.3.1-1) with a well-functioning radio link toward the UE. The mechanism is also applicable in EN-DC and MR-DC with 5GC, refer to TS 37.340 [12]. + +![Sequence diagram illustrating the procedure for centralized retransmission in intra gNB-CU scenarios. The diagram shows the interaction between a UE, gNB-DU1, gNB-DU2, and gNB-CU. The process starts with the UE connected to the gNB-CU at RRC and PDCP level, with DRBs configured on gNB-DU1 and gNB-DU2. When gNB-DU1 detects a radio link outage, it sends an F1-U DDS PDU (Radio Link Outage) to the gNB-CU. The gNB-CU then decides to switch traffic delivery to gNB-DU2 and sends undelivered PDCP PDUs to it. Once the link is restored, the gNB-CU sends an F1-U DDS PDU (Radio Link Resume) to gNB-DU1 and resumes data traffic transmission to it.](7722d62e33dcc894cc8555e9474c5606_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB-DU1 + participant gNB-DU2 + participant gNB-CU + + Note over UE, gNB-DU2: 0. UE is connected to the gNB-CU at RRC and PDCP level. UE has DRBs configured and active on gNB-DU1 and gNB-DU2 + Note over gNB-DU1: 1. gNB-DU1 determines that the radio link is subject to an outage, e.g. blocking fast fading + gNB-DU1->>gNB-CU: 2. F1-U DDS PDU (Radio Link Outage, lost F1-U sequence numbers) + Note over gNB-CU: 3. gNB-CU decides whether there are other gNB-DUs able to serve the UE and switches traffic delivery and retransmission of undelivered PDCP PDUs from gNB-DU1 to such gNB-DUs. gNB-CU does not necessarily remove gNB-DU1's DRBs + gNB-CU->>gNB-DU2: 4. gNB-DU switches traffic delivery to gNB-DU2. gNB-CU sends undelivered PDCP PDUs to gNB-DU2 + gNB-DU2->>gNB-CU: 5. F1-U DDS PDU (Radio Link Resume) + gNB-CU->>gNB-DU1: 6. gNB-CU resumes data traffic transmission to gNB-DU1 + +``` + +Sequence diagram illustrating the procedure for centralized retransmission in intra gNB-CU scenarios. The diagram shows the interaction between a UE, gNB-DU1, gNB-DU2, and gNB-CU. The process starts with the UE connected to the gNB-CU at RRC and PDCP level, with DRBs configured on gNB-DU1 and gNB-DU2. When gNB-DU1 detects a radio link outage, it sends an F1-U DDS PDU (Radio Link Outage) to the gNB-CU. The gNB-CU then decides to switch traffic delivery to gNB-DU2 and sends undelivered PDCP PDUs to it. Once the link is restored, the gNB-CU sends an F1-U DDS PDU (Radio Link Resume) to gNB-DU1 and resumes data traffic transmission to it. + +**Figure 8.3.1-1: Procedure for centralized retransmission in intra gNB-CU scenarios** + +The mechanism is shown in Figure 8.3.1-1 and targets the multi-connectivity scenario, where a UE is served by multiple data radio bearers established at least on two gNB-DUs, and it includes the following steps: + +0. The UE is connected and can transmit/receive data to/from gNB-DU1 and gNB-DU2. +1. gNB-DU1 realizes that the radio link towards the UE is experiencing outage. +2. gNB-DU1 sends the "Radio Link Outage" notification message to the gNB-CU over the F1-U interface, as part of the DDS PDU of the concerned data radio bearer. The message may include information to be used by the gNB-CU to perform retransmission of the PDCP PDUs that were not delivered by the gNB-DU1 (e.g. the highest transmitted NR PDCP Sequence Number, the highest successfully delivered NR PDCP Sequence Number and the lost NR-U Sequence Numbers). +3. gNB-CU decides to switch data traffic transmission and retransmission of PDCP PDUs that were undelivered in gNB-DU1 via gNB-DU2. gNB-CU stops sending downlink traffic to gNB-DU1. The radio leg between gNB-DU1 and the UE is not necessarily removed. +4. gNB-CU starts sending traffic (namely new PDUs and potentially retransmitted PDUs) to gNB-DU2. + +5. If gNB-DU1 realizes that the radio link of the concerned data radio bearer is back in normal operation, it may send a "Radio Link Resume" notification message as part of the DDS PDU over the F1-U interface to inform the gNB-CU that the radio link can be used again for the concerned data radio bearer. +6. gNB-CU may start sending traffic (namely new PDUs and potentially retransmitted PDUs) of the concerned data radio bearer via gNB-DU1 again. + +## 8.4 Multi-Connectivity operation + +### 8.4.1 Secondary Node Addition + +#### 8.4.1.1 EN-DC + +This clause gives the SgNB addition procedure in EN-DC given that en-gNB consists of gNB-CU and gNB-DU(s), as shown in Figure 8.4.1.1-1. + +![Sequence diagram of the SgNB addition procedure in EN-DC. The diagram shows interactions between UE, MeNB, gNB-CU, gNB-DU, S-GW, and MME. The procedure starts with MeNB sending an SgNB Addition Request to gNB-CU, which then sends a UE Context Setup Request to gNB-DU. gNB-DU responds with a UE Context Setup Response. MeNB then sends an RRC Connection Reconfiguration to UE, which completes it. MeNB sends an SgNB Reconfiguration Complete to gNB-CU. gNB-CU sends Downlink user data to gNB-DU. UE performs a Random Access Procedure with gNB-DU. gNB-CU sends SN Status Transfer to gNB-DU. gNB-CU sends Data Forwarding to S-GW. Finally, a Path Update procedure is initiated between MeNB and MME.](71b0a68b4dd64961465d2b0e790538de_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MeNB + participant gNB-CU + participant gNB-DU + participant S-GW + participant MME + + MeNB->>gNB-CU: 1. SgNB ADDITION REQUEST (carry CG-ConfigInfo) + gNB-CU->>gNB-DU: a1. UE CONTEXT SETUP REQUEST (carry CG-ConfigInfo) + gNB-DU-->>gNB-CU: a2. UE CONTEXT SETUP RESPONSE + gNB-CU->>MeNB: 2. SgNB ADDITION REQUEST ACKNOWLEDGE (carry CG-Config) + MeNB->>UE: 3. RRCConnectionReconfiguration + UE-->>MeNB: 4. RRCConnectionReconfigurationComplete + MeNB->>gNB-CU: 5. SgNB RECONFIGURATION COMPLETE + gNB-CU-->>gNB-DU: Downlink user data + UE->>gNB-DU: 6. Random Access Procedure + gNB-DU-->>gNB-CU: Uplink user data + gNB-CU->>gNB-DU: 7. SN STATUS TRANSFER + gNB-CU-->>S-GW: 8. Data Forwarding + Note right of MeNB: Path Update procedure + +``` + +Sequence diagram of the SgNB addition procedure in EN-DC. The diagram shows interactions between UE, MeNB, gNB-CU, gNB-DU, S-GW, and MME. The procedure starts with MeNB sending an SgNB Addition Request to gNB-CU, which then sends a UE Context Setup Request to gNB-DU. gNB-DU responds with a UE Context Setup Response. MeNB then sends an RRC Connection Reconfiguration to UE, which completes it. MeNB sends an SgNB Reconfiguration Complete to gNB-CU. gNB-CU sends Downlink user data to gNB-DU. UE performs a Random Access Procedure with gNB-DU. gNB-CU sends SN Status Transfer to gNB-DU. gNB-CU sends Data Forwarding to S-GW. Finally, a Path Update procedure is initiated between MeNB and MME. + +Figure 8.4.1.1-1: SgNB addition procedure in EN-DC + +1~8: refer to TS 37.340 [12]. + +a1. After receiving the SgNB ADDITION REQUEST message from MeNB, the gNB-CU sends the UE CONTEXT SETUP REQUEST message to the gNB-DU to create a UE context. As specified in TS 37.340 [12], in the course of a Secondary Node Change, the UE CONTEXT SETUP REQUEST message may contain source cell group configuration to allow gNB-DU to perform delta configuration. + +a2. The gNB-DU responds to the gNB-CU with the UE CONTEXT SETUP RESPONSE message. In case the gNB-DU receives the UE CONTEXT SETUP REQUEST message without the source cell group configuration or in the course of a Secondary Node Change as specified in TS 37.340 [12] or if the gNB-DU decides to perform full configuration after receiving the source cell group configuration, it shall perform full configuration and indicate that it has applied full configuration in the UE CONTEXT SETUP RESPONSE message. + +NOTE: On Inter-gNB-CU Mobility, same method is performed to achieve full configuration and delta configuration. + +### 8.4.2 Secondary Node Release (MN/SN initiated) + +#### 8.4.2.1 EN-DC + +This clause gives the SgNB release procedure in EN-DC given that the en-gNB consists of a gNB-CU and gNB-DU(s). + +##### MN initiated SN Release + +![Sequence diagram of the SgNB release procedure in EN-DC (MN initiated). The diagram shows interactions between UE, MeNB, gNB-CU, gNB-DU, S-GW, and MME. The procedure starts with MeNB sending an SgNB RELEASE REQUEST to gNB-CU. gNB-CU responds with SgNB RELEASE REQUEST ACKNOWLEDGE. MeNB then sends an RRCConnectionReconfiguration to UE. gNB-CU sends a UE CONTEXT MODIFICATION REQUEST to gNB-DU, which responds with UE CONTEXT MODIFICATION RESPONSE. MeNB sends an SN STATUS TRANSFER to gNB-CU. gNB-CU sends Data Forwarding to S-GW. A Path Update procedure is initiated between MeNB and MME. MeNB sends a UE CONTEXT RELEASE to gNB-CU. gNB-CU sends a UE CONTEXT RELEASE COMMAND to gNB-DU, which responds with UE CONTEXT RELEASE COMPLETE.](0997dbaa9dfecedd60029d70b53327b8_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MeNB + participant gNB-CU + participant gNB-DU + participant S-GW + participant MME + + MeNB->>gNB-CU: 1. SgNB RELEASE REQUEST + gNB-CU-->>MeNB: 2. SgNB RELEASE REQUEST ACKNOWLEDGE + MeNB->>UE: 3. RRCConnectionReconfiguration + UE-->>MeNB: 4. RRCConnectionReconfigurationComplete + gNB-CU->>gNB-DU: a1. UE CONTEXT MODIFICATION REQUEST + gNB-DU-->>gNB-CU: a2. UE CONTEXT MODIFICATION RESPONSE + MeNB->>gNB-CU: 5. SN STATUS TRANSFER + gNB-CU-->>S-GW: 6. Data Forwarding + Note right of MeNB: 7. Path Update procedure + MeNB->>gNB-CU: 8. UE CONTEXT RELEASE + gNB-CU->>gNB-DU: a3. UE CONTEXT RELEASE COMMAND + gNB-DU-->>gNB-CU: a4. UE CONTEXT RELEASE COMPLETE + +``` + +Sequence diagram of the SgNB release procedure in EN-DC (MN initiated). The diagram shows interactions between UE, MeNB, gNB-CU, gNB-DU, S-GW, and MME. The procedure starts with MeNB sending an SgNB RELEASE REQUEST to gNB-CU. gNB-CU responds with SgNB RELEASE REQUEST ACKNOWLEDGE. MeNB then sends an RRCConnectionReconfiguration to UE. gNB-CU sends a UE CONTEXT MODIFICATION REQUEST to gNB-DU, which responds with UE CONTEXT MODIFICATION RESPONSE. MeNB sends an SN STATUS TRANSFER to gNB-CU. gNB-CU sends Data Forwarding to S-GW. A Path Update procedure is initiated between MeNB and MME. MeNB sends a UE CONTEXT RELEASE to gNB-CU. gNB-CU sends a UE CONTEXT RELEASE COMMAND to gNB-DU, which responds with UE CONTEXT RELEASE COMPLETE. + +Figure 8.4.2.1-1 SgNB release procedure in EN-DC (MN initiated) + +1~8: refer to TS 37.340 [12]. + +NOTE: The timing of sending the Step 2 SgNB RELEASE REQUEST ACKNOWLEDGE message is an example, it may be sent e.g. after step a1 or after a2 and it is up to implementation. + +- a1. After receiving SgNB RELEASE REQUEST message from MeNB, gNB-CU sends the UE CONTEXT MODIFICATION REQUEST message to gNB-DU to stop the data transmission for the UE. It is up to gNB-DU implementation when to stop the UE scheduling. +- a2. gNB-DU responds to gNB-CU with UE CONTEXT MODIFICATION RESPONSE message. +- a3. After receiving the UE CONTEXT RELEASE message from MeNB, the gNB-CU sends the UE CONTEXT RELEASE COMMAND message to the gNB-DU to release the UE context. +- a4. The gNB-DU responds to the gNB-CU with the UE CONTEXT RELEASE COMPLETE message. + +##### SN initiated SN Release + +![Sequence diagram of the SgNB release procedure in EN-DC (SN initiated). The diagram shows interactions between UE, MeNB, gNB-CU, gNB-DU, S-GW, and MME. The procedure starts with the MeNB sending an SgNB Release Required to the gNB-CU. The gNB-CU sends a UE Context Modification Request to the gNB-DU (a1) and a UE Context Release to the MeNB (8). The gNB-DU responds with a UE Context Modification Response (a2). The MeNB sends an RRC Connection Reconfiguration to the UE (3), which completes with RRC Connection Reconfiguration Complete (4). The gNB-CU sends an SN Status Transfer (5) and Data Forwarding (6) to the S-GW. A Path Update procedure (7) occurs between the MeNB and the MME. Finally, the gNB-CU sends a UE Context Release Command to the gNB-DU (a3), which responds with a UE Context Release Complete (a4).](7ed5d5770331f31ade15439a21c31425_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MeNB + participant gNB-CU + participant gNB-DU + participant S-GW + participant MME + + MeNB->>gNB-CU: 1. SgNB RELEASE REQUIRED + gNB-CU->>gNB-DU: a1. UE CONTEXT MODIFICATION REQUEST + gNB-DU-->>gNB-CU: a2. UE CONTEXT MODIFICATION RESPONSE + MeNB->>gNB-CU: 2. SgNB RELEASE CONFIRM + MeNB->>UE: 3. RRCConnectionReconfiguration + UE-->>MeNB: 4. RRCConnectionReconfigurationComplete + gNB-CU->>gNB-DU: 8. UE CONTEXT RELEASE + gNB-CU->>gNB-DU: a3. UE CONTEXT RELEASE COMMAND + gNB-DU-->>gNB-CU: a4. UE CONTEXT RELEASE COMPLETE + gNB-CU->>S-GW: 5. SN STATUS TRANSFER + gNB-CU->>S-GW: 6. Data Forwarding + MeNB->>MME: 7. Path Update procedure + +``` + +Sequence diagram of the SgNB release procedure in EN-DC (SN initiated). The diagram shows interactions between UE, MeNB, gNB-CU, gNB-DU, S-GW, and MME. The procedure starts with the MeNB sending an SgNB Release Required to the gNB-CU. The gNB-CU sends a UE Context Modification Request to the gNB-DU (a1) and a UE Context Release to the MeNB (8). The gNB-DU responds with a UE Context Modification Response (a2). The MeNB sends an RRC Connection Reconfiguration to the UE (3), which completes with RRC Connection Reconfiguration Complete (4). The gNB-CU sends an SN Status Transfer (5) and Data Forwarding (6) to the S-GW. A Path Update procedure (7) occurs between the MeNB and the MME. Finally, the gNB-CU sends a UE Context Release Command to the gNB-DU (a3), which responds with a UE Context Release Complete (a4). + +**Figure 8.4.2.1-2 SgNB release procedure in EN-DC (SN initiated)** + +1~8: refer to TS 37.340 [12]. + +- a1. gNB-CU sends the UE CONTEXT MODIFICATION REQUEST message to gNB-DU to stop the data transmission for the UE. It is up to gNB-DU implementation when to stop the UE scheduling. This step may occur before step 1. +- a2. gNB-DU responds to gNB-CU with UE CONTEXT MODIFICATION RESPONSE message. +- a3. After receiving the UE CONTEXT RELEASE message from MeNB, the gNB-CU sends the UE CONTEXT RELEASE COMMAND message to the gNB-DU to release the UE context. +- a4. The gNB-DU responds to the gNB-CU with the UE CONTEXT RELEASE COMPLETE message. + +### 8.4.3 SCG suspend/resume in RRC\_INACTIVE + +In the following, the procedure for SCG resume in RRC\_INACTIVE is described. + +![Sequence diagram for SCG Suspend/Resume in RRC_INACTIVE state. The diagram shows interactions between UE, MN, SN-CU, and SN-DU. The process involves suspending lower layers, then later resuming them, with various context modification and RRC messages exchanged between the entities.](3337af75dfee8af7687b4f49914d6c93_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MN + participant SN-CU + participant SN-DU + + Note right of SN-DU: Find UE context based on the gNB-DU +UE F1AP ID + + SN-CU->>SN-DU: 1. UE CONTEXT MODIFICATION REQUEST (suspend lower layers) + SN-DU-->>SN-CU: 2. UE CONTEXT MODIFICATION RESPONSE (suspend lower layers) + SN-CU->>MN: 3. Activity Notification (active) + MN->>SN-CU: 4. SN Modification Request (resume lower layers) + SN-CU->>SN-DU: 5. UE CONTEXT MODIFICATION REQUEST (resume lower layers) + SN-DU-->>SN-CU: 6. UE CONTEXT MODIFICATION RESPONSE (resume lower layers) + SN-CU->>MN: 7. SN Modification Request Acknowledge (carry SN RRC reconfiguration message) + MN->>UE: 8. RRC(Connection)Resume (restoreSCG) (carry SN RRC reconfiguration message) + UE-->>MN: 9. RRC(Connection)ResumeComplete (carry SN RRC reconfiguration complete) + MN->>SN-CU: 10. SN Reconfiguration Complete (carry SN RRC reconfiguration complete) + MN-->>UE: 11. Random Access Procedure + +``` + +Sequence diagram for SCG Suspend/Resume in RRC\_INACTIVE state. The diagram shows interactions between UE, MN, SN-CU, and SN-DU. The process involves suspending lower layers, then later resuming them, with various context modification and RRC messages exchanged between the entities. + +**Figure 8.4.3-1: SCG Suspend/Resume in RRC\_INACTIVE** + +1. The CU of SN sends the UE CONTEXT MODIFICATION REQUEST message to the DU of SN to suspend the SCG of the UE before the UE enters into RRC\_INACTIVE state from RRC\_CONNECTED state. + +2. The DU of SN sends the UE CONTEXT MODIFICATION RESPONSE to the CU of SN, and keeps all lower layer configuration for UEs without transmitting or receiving data from UE. + +3~4: refer to TS 37.340 [12]. + +5. The CU of SN sends the UE CONTEXT MODIFICATION REQUEST message to the DU of SN to resume the SCG of the UE before the UE enters into RRC\_CONNECTED state from RRC\_INACTIVE state. + +6. The DU of SN sends the UE CONTEXT MODIFICATION RESPONSE message to the CU of SN, and uses the previously stored lower layer configuration for the UE. + +7~11: refer to TS 37.340 [12]. + +### 8.4.4 SCG Deactivation and Activation + +This clause gives the NR SCG deactivation and activation procedures in MR-DC given that the SN consists of a gNB-CU and gNB-DU(s). + +#### 8.4.4.1 SN Addition with SCG Activation or Deactivation + +![Sequence diagram illustrating the SCG Activation or Deactivation in SN Addition procedure. The diagram shows interactions between MN-CU-UP, MN-CU-CP, SN-CU-CP, SN-CU-UP, and SN-DU. The sequence starts with MN-CU-CP sending an SN Addition Request to SN-CU-CP. SN-CU-CP then sends a BEARER CONTEXT SETUP REQUEST to SN-CU-UP, which responds with a BEARER CONTEXT SETUP RESPONSE. SN-CU-CP sends a UE CONTEXT SETUP REQUEST to SN-DU, which responds with a UE CONTEXT SETUP RESPONSE. SN-CU-CP then sends a BEARER CONTEXT MODIFICATION REQUEST to SN-CU-UP, which responds with a BEARER CONTEXT MODIFICATION RESPONSE. SN-CU-CP sends an SN Addition Request Acknowledge to MN-CU-CP. MN-CU-CP then sends a BEARER CONTEXT MODIFICATION REQUEST to MN-CU-UP, which responds with a BEARER CONTEXT MODIFICATION RESPONSE.](03d9aaba6c1af8bfd8e42c1d2422ae5c_img.jpg) + +``` + +sequenceDiagram + participant MN-CU-UP + participant MN-CU-CP + participant SN-CU-CP + participant SN-CU-UP + participant SN-DU + + MN-CU-CP->>SN-CU-CP: 1. SN Addition Request (activate or deactivate the SCG) + SN-CU-CP-->>SN-CU-UP: 2. BEARER CONTEXT SETUP REQUEST (SCG activated or deactivated) + SN-CU-UP-->>SN-CU-CP: 3. BEARER CONTEXT SETUP RESPONSE + SN-CU-CP->>SN-DU: 4. UE CONTEXT SETUP REQUEST (activate or deactivate the SCG) + SN-DU-->>SN-CU-CP: 5. UE CONTEXT SETUP RESPONSE (SCG status) + SN-CU-CP-->>SN-CU-UP: 6. BEARER CONTEXT MODIFICATION REQUEST (SCG status) + SN-CU-UP-->>SN-CU-CP: 7. BEARER CONTEXT MODIFICATION RESPONSE + SN-CU-CP->>MN-CU-CP: 8. SN Addition Request Acknowledge (SCG status) + MN-CU-CP-->>MN-CU-UP: 9. BEARER CONTEXT MODIFICATION REQUEST (SCG status) + MN-CU-UP-->>MN-CU-CP: 10. BEARER CONTEXT MODIFICATION RESPONSE + +``` + +Sequence diagram illustrating the SCG Activation or Deactivation in SN Addition procedure. The diagram shows interactions between MN-CU-UP, MN-CU-CP, SN-CU-CP, SN-CU-UP, and SN-DU. The sequence starts with MN-CU-CP sending an SN Addition Request to SN-CU-CP. SN-CU-CP then sends a BEARER CONTEXT SETUP REQUEST to SN-CU-UP, which responds with a BEARER CONTEXT SETUP RESPONSE. SN-CU-CP sends a UE CONTEXT SETUP REQUEST to SN-DU, which responds with a UE CONTEXT SETUP RESPONSE. SN-CU-CP then sends a BEARER CONTEXT MODIFICATION REQUEST to SN-CU-UP, which responds with a BEARER CONTEXT MODIFICATION RESPONSE. SN-CU-CP sends an SN Addition Request Acknowledge to MN-CU-CP. MN-CU-CP then sends a BEARER CONTEXT MODIFICATION REQUEST to MN-CU-UP, which responds with a BEARER CONTEXT MODIFICATION RESPONSE. + +**Figure 8.4.4.1-1: SCG Activation or Deactivation in SN Addition procedure** + +1. The MN sends the SN Addition Request message to the SN, indicates the request of SCG activation or deactivation. +2. The SN-CU-CP may send the BEARER CONTEXT SETUP REQUEST message to the SN-CU-UP to setup bearer context and notify the activation or deactivation of the SCG. +3. The SN-CU-UP sends the BEARER CONTEXT SETUP RESPONSE message to the SN-CU-CP. +4. The SN-CU sends the UE CONTEXT SETUP REQUEST message to the SN-DU to setup UE context and indicate the request of SCG activation or deactivation. +5. The SN-DU sends the UE CONTEXT SETUP RESPONSE message to the SN-CU, indicates the SCG status. In case SCG activation is requested, the SN-DU shall indicate SCG activated in the message. +6. The SN-CU-CP may send the BEARER CONTEXT MODIFICATION REQUEST message to the SN-CU-UP as described in clause 8.9.2 and may notify the SCG status if needed. +7. The SN-CU-UP sends the BEARER CONTEXT MODIFICATION RESPONSE message to the SN-CU-CP. +8. The SN sends the SN Addition Request Acknowledge message to the MN, indicates the SCG status. In case SCG activation is requested, the SN shall indicate SCG activated in the message. +9. The MN-CU-CP may send the BEARER CONTEXT MODIFICATION REQUEST message to the MN-CU-UP to notify the SCG status. +10. The MN-CU-UP sends the BEARER CONTEXT MODIFICATION RESPONSE message to the MN-CU-CP. + +#### 8.4.4.2 MN initiated SN Modification with SCG Activation or Deactivation + +![Sequence diagram illustrating the SCG Activation or Deactivation in MN initiated SN Modification procedure. The diagram shows interactions between MN-CU-UP, MN-CU-CP, SN-CU-CP, SN-CU-UP, and SN-DU. The process starts with SCG deactivated or activated, followed by SN Modification Request, BEARER CONTEXT MODIFICATION REQUEST/RESPONSE, and UE CONTEXT MODIFICATION REQUEST/RESPONSE messages.](efbdfb3d9d5a7a7782ef29e131f9f280_img.jpg) + +``` + +sequenceDiagram + participant MN-CU-UP + participant MN-CU-CP + participant SN-CU-CP + participant SN-CU-UP + participant SN-DU + + Note over MN-CU-UP, SN-DU: 1. SCG deactivated or activated + MN-CU-CP->>SN-CU-CP: 2. SN Modification Request (activate or deactivate the SCG) + SN-CU-CP->>SN-CU-UP: 3. BEARER CONTEXT MODIFICATION REQUEST (SCG activated or deactivated) + SN-CU-UP-->>SN-CU-CP: 4. BEARER CONTEXT MODIFICATION RESPONSE + SN-CU-CP->>SN-DU: 5. UE CONTEXT MODIFICATION REQUEST (activate or deactivate the SCG) + SN-DU-->>SN-CU-CP: 6. UE CONTEXT MODIFICATION RESPONSE (SCG status) + SN-CU-CP->>SN-CU-UP: 7. BEARER CONTEXT MODIFICATION REQUEST (SCG status) + SN-CU-UP-->>SN-CU-CP: 8. BEARER CONTEXT MODIFICATION RESPONSE + SN-CU-CP-->>MN-CU-CP: 9. SN Modification Request Acknowledge (SCG status) + MN-CU-CP->>MN-CU-UP: 10. BEARER CONTEXT MODIFICATION REQUEST (SCG status) + MN-CU-UP-->>MN-CU-CP: 11. BEARER CONTEXT MODIFICATION RESPONSE + +``` + +Sequence diagram illustrating the SCG Activation or Deactivation in MN initiated SN Modification procedure. The diagram shows interactions between MN-CU-UP, MN-CU-CP, SN-CU-CP, SN-CU-UP, and SN-DU. The process starts with SCG deactivated or activated, followed by SN Modification Request, BEARER CONTEXT MODIFICATION REQUEST/RESPONSE, and UE CONTEXT MODIFICATION REQUEST/RESPONSE messages. + +**Figure 8.4.4.2-1: SCG Activation or Deactivation in MN initiated SN Modification procedure** + +1. SCG is deactivated or activated. + 2. The MN sends the SN Modification Request message to the SN, indicates the request of SCG activation or deactivation. + 3. The SN-CU-CP may send the BEARER CONTEXT MODIFICATION REQUEST message to the SN-CU-UP to notify the SCG activation or deactivation. + 4. The SN-CU-UP sends the BEARER CONTEXT MODIFICATION RESPONSE message to the SN-CU-CP. + 5. The SN-CU sends the UE CONTEXT MODIFICATION REQUEST message to the SN-DU to indicate the request of SCG activation or deactivation. + 6. The SN-DU may send the UE CONTEXT MODIFICATION RESPONSE message to the SN-CU, indicates the SCG status. + 7. The SN-CU-CP sends the BEARER CONTEXT MODIFICATION REQUEST message to the SN-CU-UP to notify the SCG status. + 8. The SN-CU-UP sends the BEARER CONTEXT MODIFICATION RESPONSE message to the SN-CU-CP. +- NOTE: Step 7 and 8 may be skipped in case the SN-DU accepted the SCG activation or deactivation request. +9. The SN sends the SN Modification Request Acknowledge message towards the MN, indicates the SCG status. + 10. The MN-CU-CP may send the BEARER CONTEXT MODIFICATION REQUEST message to the MN-CU-UP to notify the SCG status. + 11. The MN-CU-UP sends the BEARER CONTEXT MODIFICATION RESPONSE message to the MN-CU-CP. + +#### 8.4.4.3 SN initiated SN Modification with SCG Activation or Deactivation + +![Sequence diagram for SCG Activation or Deactivation in SN initiated SN Modification procedure. The diagram shows interactions between MN-CU-UP, MN-CU-CP, SN-CU-CP, SN-CU-UP, and SN-DU. The process starts with SCG deactivated or activated, followed by a series of BEARER CONTEXT MODIFICATION REQUEST/RESPONSE and UE CONTEXT MODIFICATION REQUEST/RESPONSE messages, ending with SN Modification Required and SN Modification Confirm messages.](50ef8602c7c9edd2da0e2133e772c2a2_img.jpg) + +``` + +sequenceDiagram + participant MN-CU-UP + participant MN-CU-CP + participant SN-CU-CP + participant SN-CU-UP + participant SN-DU + + Note over MN-CU-UP, SN-DU: 1. SCG deactivated or activated + SN-CU-CP->>SN-CU-UP: 2. BEARER CONTEXT MODIFICATION REQUEST (SCG activated or deactivated) + SN-CU-UP-->>SN-CU-CP: 3. BEARER CONTEXT MODIFICATION RESPONSE + SN-CU-CP->>SN-DU: 4. UE CONTEXT MODIFICATION REQUEST (activate or deactivate the SCG) + SN-DU-->>SN-CU-CP: 5. UE CONTEXT MODIFICATION RESPONSE (SCG status) + SN-CU-CP->>SN-CU-UP: 6. BEARER CONTEXT MODIFICATION REQUEST (SCG status) + SN-CU-UP-->>SN-CU-CP: 7. BEARER CONTEXT MODIFICATION RESPONSE + SN-CU-CP->>MN-CU-CP: 8. SN Modification Required (activate or deactivate the SCG) + MN-CU-CP->>MN-CU-UP: 9. BEARER CONTEXT MODIFICATION REQUEST (SCG status) + MN-CU-UP-->>MN-CU-CP: 10. BEARER CONTEXT MODIFICATION RESPONSE + MN-CU-CP->>SN-CU-CP: 11. SN Modification Confirm + +``` + +Sequence diagram for SCG Activation or Deactivation in SN initiated SN Modification procedure. The diagram shows interactions between MN-CU-UP, MN-CU-CP, SN-CU-CP, SN-CU-UP, and SN-DU. The process starts with SCG deactivated or activated, followed by a series of BEARER CONTEXT MODIFICATION REQUEST/RESPONSE and UE CONTEXT MODIFICATION REQUEST/RESPONSE messages, ending with SN Modification Required and SN Modification Confirm messages. + +**Figure 8.4.4.3-1: SCG Activation or Deactivation in SN initiated SN Modification procedure** + +1. SCG is deactivated or activated. + 2. The SN-CU-CP may send the BEARER CONTEXT MODIFICATION REQUEST message to the SN-CU-UP to notify the SCG activation or deactivation. + 3. The SN-CU-UP sends the BEARER CONTEXT MODIFICATION RESPONSE message to the SN-CU-CP. + 4. The SN-CU sends the UE CONTEXT MODIFICATION REQUEST message to the SN-DU to indicate the request of SCG activation or deactivation. + 5. The SN-DU sends the UE CONTEXT MODIFICATION RESPONSE message to the SN-CU, indicates the SCG status. + 6. The SN-CU-CP may send the BEARER CONTEXT MODIFICATION REQUEST message to the SN-CU-UP to notify the SCG status. + 7. The SN-CU-UP sends the BEARER CONTEXT MODIFICATION RESPONSE message to the SN-CU-CP. +- NOTE 1: Step 6 and 7 may be skipped in case the SN-DU accepted the SCG activation or deactivation request. +8. The SN sends the SN Modification Required message to the MN, indicates the request of SCG activation or deactivation. + 9. The MN-CU-CP may send the BEARER CONTEXT MODIFICATION REQUEST message to the MN-CU-UP to notify the SCG status. + 10. The MN-CU-UP sends the BEARER CONTEXT MODIFICATION RESPONSE message to the MN-CU-CP. +- NOTE 2: Based on implementation, step 9 and 10 can be performed after step 11. +11. The MN sends the SN Modification Confirm message to the SN. +- NOTE 3: Step 8-11 are not performed in case the SN-DU rejected the SCG activation or deactivation request. + +## 8.5 F1 Startup and cells activation + +This function allows to setup the F1 interface between a gNB-DU and a gNB-CU and it allows to activate the gNB-DU cells. + +![Sequence diagram illustrating F1 startup and cell activation. The diagram shows four lifelines: gNB-DU, gNB-CU, 5GC, and gNB/eNB. The process starts with a '0. Pre-operational state' between gNB-DU and gNB-CU. Step 1: gNB-DU sends '1. F1 SETUP REQUEST' to gNB-CU. Step 2: gNB-CU sends '2. NG Setup/gNB Configuration Update' to 5GC. Step 3: gNB-CU sends '3. F1 SETUP RESPONSE' to gNB-DU. Step 4: gNB-CU sends '4. GNB-CU CONFIGURATION UPDATE' to gNB-DU. Step 5: gNB-DU sends '5. GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE' to gNB-CU. Step 6: gNB-CU sends '6. Xn/X2 Setup' to gNB/eNB.](56a5265d174ce056c1dbe5e7a60839fc_img.jpg) + +``` + +sequenceDiagram + participant gNB-DU + participant gNB-CU + participant 5GC + participant gNB/eNB + Note over gNB-DU, gNB-CU: 0. Pre-operational state + gNB-DU->>gNB-CU: 1. F1 SETUP REQUEST + gNB-CU->>5GC: 2. NG Setup/gNB Configuration Update + gNB-CU-->>gNB-DU: 3. F1 SETUP RESPONSE + gNB-CU-->>gNB-DU: 4. GNB-CU CONFIGURATION UPDATE + gNB-DU-->>gNB-CU: 5. GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE + gNB-CU-->>gNB/eNB: 6. Xn/X2 Setup + +``` + +Sequence diagram illustrating F1 startup and cell activation. The diagram shows four lifelines: gNB-DU, gNB-CU, 5GC, and gNB/eNB. The process starts with a '0. Pre-operational state' between gNB-DU and gNB-CU. Step 1: gNB-DU sends '1. F1 SETUP REQUEST' to gNB-CU. Step 2: gNB-CU sends '2. NG Setup/gNB Configuration Update' to 5GC. Step 3: gNB-CU sends '3. F1 SETUP RESPONSE' to gNB-DU. Step 4: gNB-CU sends '4. GNB-CU CONFIGURATION UPDATE' to gNB-DU. Step 5: gNB-DU sends '5. GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE' to gNB-CU. Step 6: gNB-CU sends '6. Xn/X2 Setup' to gNB/eNB. + +**Figure 8.5-1: F1 startup and cell activation** + +0. The gNB-DU and its cells are configured by OAM in the F1 pre-operational state. The gNB-DU has TNL connectivity toward the gNB-CU. +1. The gNB-DU sends an F1 SETUP REQUEST message to the gNB-CU including a list of cells that are configured and ready to be activated. For each cell supporting NPN the gNB-DU includes NPN specific information. +2. In NG-RAN, the gNB-CU ensures the connectivity toward the core network. For this reason, the gNB-CU may initiate either the NG Setup or the gNB Configuration Update procedure towards 5GC. +3. The gNB-CU sends an F1 SETUP RESPONSE message to the gNB-DU that optionally includes a list of cells to be activated. The cells in the list of cells to be activated in F1 SETUP RESPONSE message become active, while the cells not in the list are inactive. The cells that are active are *Out-of-Service* until the gNB-DU indicates that they are *In-Service*. The gNB-DU will initiate the gNB-DU Configuration Update procedure towards the gNB-CU and includes the cell(s) that are *In-Service* and/or the cell(s) that are *Out-Of-Service*. The gNB-DU may also indicate cell(s) to be deleted, in which case the gNB-CU removes the corresponding cell(s) information. +4. The gNB-CU may send a GNB CU CONFIGURATION UPDATE message to the gNB-DU that optionally includes a list of cells to be activated, e.g., in case that these cells were not activated using the F1 SETUP RESPONSE message. +5. The gNB-DU replies with a GNB CU CONFIGURATION UPDATE ACKNOWLEDGE message that optionally includes a list of cells that failed to be activated. The gNB-CU regards all Active cells as *Out-Of-Service* until the gNB-DU indicates that they are *In-Service*. +6. The gNB-CU may initiate either the Xn Setup towards a neighbour NG-RAN node or the EN-DC X2 Setup procedure towards a neighbour eNB. + +NOTE 1: For NG-RAN in case that the F1 SETUP RESPONSE message is not used to activate any cell, step 2 may be performed after step 3. + +Over the F1 interface between a gNB-CU and a gNB-DU pair, the following two Cell States are possible: + +- *Inactive*: the cell is known by both the gNB-DU and the gNB-CU. The cell shall not serve UEs; +- *Active*: the cell is known by both the gNB-DU and the gNB-CU. The cell should try to provide services to the UEs. + +The gNB-CU decides whether the Cell State should be “Inactive” or “Active”. The gNB-CU can request the gNB-DU to change the Cell State using the F1 SETUP RESPONSE, the GNB DU CONFIGURATION UPDATE ACKNOWLEDGE, or the GNB CU CONFIGURATION UPDATE messages. + +The gNB-DU reports to the gNB-CU the *Service Status*. The *Service Status* is the state of the radio transmission over the air. The *Service Status* is reported by the gNB-DU for cells for which the Cell State is “Active”. The following *Service Status* are defined: + +- *In-Service*: the cell is operational and able to serve UEs. +- *Out-Of-Service*: the cell is not operational, and it is not able to serve UEs. The gNB-DU is trying to make the cell operational. + +The gNB-DU reports the *Service Status* using the GNB DU CONFIGURATION UPDATE message. + +NOTE 2: If gNB-DU regards that one or more cells cannot become operational, the gNB-DU deletes them and reports them using the GNB DU CONFIGURATION UPDATE message. + +## 8.6 RRC state transition + +### 8.6.1 RRC connected to RRC inactive + +This clause gives the RRC connected to RRC inactive state transition given that gNB consists of gNB-CU and gNB-DU(s), as shown in Figure 8.6.1-1. + +![Sequence diagram of RRC connected to RRC inactive state transition procedure. Lifelines: UE, gNB-DU, gNB-CU. The gNB-CU determines the UE to enter into RRC inactive mode. It sends a UE CONTEXT RELEASE COMMAND to the gNB-DU. The gNB-DU forwards an RRCRelease (suspendConfig) message to the UE. The gNB-DU then sends a UE CONTEXT RELEASE COMPLETE message back to the gNB-CU.](a4b868a176f7e0448ee72483727e9f6f_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB-DU + participant gNB-CU + Note right of gNB-CU: Determines UE to enter into RRC inactive mode + gNB-CU->>gNB-DU: 1. UE CONTEXT RELEASE COMMAND + gNB-DU->>UE: 2. RRCRelease (suspendConfig) + gNB-DU->>gNB-CU: 3. UE CONTEXT RELEASE COMPLETE + +``` + +Sequence diagram of RRC connected to RRC inactive state transition procedure. Lifelines: UE, gNB-DU, gNB-CU. The gNB-CU determines the UE to enter into RRC inactive mode. It sends a UE CONTEXT RELEASE COMMAND to the gNB-DU. The gNB-DU forwards an RRCRelease (suspendConfig) message to the UE. The gNB-DU then sends a UE CONTEXT RELEASE COMPLETE message back to the gNB-CU. + +Figure 8.6.1-1: RRC connected to RRC inactive state transition procedure + +0. At first, the gNB-CU determines the UE to enter into RRC inactive mode from connected mode. +1. The gNB-CU generates *RRCRelease* message which includes suspend configuration towards UE. The *RRC* message is encapsulated in *UE CONTEXT RELEASE COMMAND* message to the gNB-DU. +2. The gNB-DU forwards *RRCRelease* message to UE. +3. The gNB-DU responds with *UE CONTEXT RELEASE COMPLETE* message. + +### 8.6.2 RRC inactive to other states + +This clause gives the RRC inactive to other RRC states transition given that gNB consists of gNB-CU and gNB-DU(s), as shown in Figure 8.6.2-1. + +![Sequence diagram illustrating the RRC inactive to other RRC states transition procedure between UE, gNB-DU, and gNB-CU.](575d7d345b3ec04393bb2ec720ebabca_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB-DU + participant gNB-CU + + Note right of gNB-CU: 1. PAGING + gNB-CU-->gNB-DU: 1. PAGING + Note left of gNB-DU: 2. Paging + gNB-DU-->UE: 2. Paging + Note left of UE: 3. RRCResumeRequest + UE->>gNB-DU: 3. RRCResumeRequest + Note right of gNB-DU: 4. INITIAL UL RRC MESSAGE TRANSFER + gNB-DU->>gNB-CU: 4. INITIAL UL RRC MESSAGE TRANSFER + Note right of gNB-CU: 5. UE CONTEXT SETUP REQUEST + gNB-CU-->gNB-DU: 5. UE CONTEXT SETUP REQUEST + Note right of gNB-DU: 6. UE CONTEXT SETUP RESPONSE + gNB-DU-->gNB-CU: 6. UE CONTEXT SETUP RESPONSE + Note right of gNB-CU: 7. DL RRC MESSAGE TRANSFER + gNB-CU->>gNB-DU: 7. DL RRC MESSAGE TRANSFER + Note left of gNB-DU: 8. RRCResume/RRCHeset/RRCHeset/RRCHeset + gNB-DU-->UE: 8. RRCResume/RRCHeset/RRCHeset/RRCHeset + Note left of UE: 9. RRCResumeComplete/RRCHesetComplete + UE-->>gNB-DU: 9. RRCResumeComplete/RRCHesetComplete + Note right of gNB-DU: 10. UL RRC MESSAGE TRANSFER + gNB-DU-->gNB-CU: 10. UL RRC MESSAGE TRANSFER + +``` + +Sequence diagram illustrating the RRC inactive to other RRC states transition procedure between UE, gNB-DU, and gNB-CU. + +**Figure 8.6.2-1: RRC inactive to other RRC states transition procedure** + +1. If data is received from 5GC, the gNB-CU sends PAGING message to the gNB-DU. + +2. The gNB-DU sends *Paging* message to UE. + +NOTE: Step 1 and 2 only exist in case of DL data arrival. + +3. The UE sends *RRCResumeRequest* message either upon RAN-based paging, UL data arrival or RNA update. + +4. The gNB-DU includes *RRCResumeRequest* in a non-UE associated INITIAL UL RRC MESSAGE TRANSFER message and transfer to the gNB-CU. + +5. For UE Inactive to UE Active transitions, excluding transitions due to signalling exchange only, the gNB-CU allocates gNB-CU UE F1AP ID and sends UE CONTEXT SETUP REQUEST message to gNB-DU, which may include SRB ID(s) and DRB ID(s) to be setup, CellGroupConfig stored in gNB-CU or retrieved from the old NG-RAN node may also be included. In case of NG-RAN sharing, the gNB-CU includes the serving PLMN ID (in case of SNPNS the serving NID). + +6. The gNB-DU responds with UE CONTEXT SETUP RESPONSE message, which contains RLC/MAC/PHY configuration of SRB and DRBs provided by the gNB-DU. + +NOTE: Step 5 and step 6 exist for inactive to active transitions, excluding transitions due to signalling exchange only. When gNB-CU successfully retrieves and verifies the UE context, it may decide to let the UE enter into RRC active mode. gNB-CU shall trigger UE context setup procedure between gNB-CU and gNB-DU, during which both SRB1, SRB2 and DRB(s) can be setup. For signalling exchange only transitions, gNB-CU does not trigger UE Context Setup procedure. For inactive to Idle transitions the gNB-CU does not trigger the UE Context Setup procedure. + +7. The gNB-CU generates *RRCResume/RRCHeset/RRCHeset/RRCHeset* message or receives *RRCHeset* message from the old NG-RAN node towards the UE. The RRC message is encapsulated in DL RRC MESSAGE TRANSFER message together with SRB ID. + +8. The gNB-DU forwards RRC message to the UE either over SRB0 or SRB1 as indicated by the SRB ID. + +NOTE: In step 7, it is expected that gNB-CU takes appropriate action, e.g. generates RRC resume message for inactive to active state transition (for both cases of signaling exchange only, and UP data exchange), generates *RRCSsetup* message for fallback to establish a new RRC connection, and generates or receives from the old NG-RAN node either *RRcrelease* message without suspend configuration for inactive to idle state transition, or *RRcrelease* message with suspend configuration to remain in inactive state. If step 5 and 6 are not performed, the gNB-DU deduces the SRB on which to deliver the RRC message in step 7 from the SRB ID, i.e. SRB ID "0" corresponds to SRB0, SRB ID "1" corresponds to SRB1. + +9. The UE sends *RRcresumeComplete/RRCSsetupComplete* message to the gNB-DU. + +10. The gNB-DU encapsulates RRC in UL RRC MESSAGE TRANSFER message and send to the gNB-CU. + +NOTE: Step 9 and step 10 exist for inactive to active state transition (for both cases of signaling exchange only, and UP data exchange). UE generates *RRcresumeComplete/RRCSsetupComplete* message for resume the existing RRC connection or fallback to a new RRC connection respectively. + +## 8.7 RRC connection reestablishment + +This procedure is used for the case that UE tries to reestablish the RRC connection, as shown in Figure 8.7-1. + +![Sequence diagram of RRC connection reestablishment procedure between UE, gNB-DU, and gNB-CU.](fcc757566216206ceddbd6c775e8db02_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB-DU + participant gNB-CU + + Note right of gNB-DU: Allocate new C-RNTI and SRB1 configuration + + UE->>gNB-DU: 1. Preamble + gNB-DU-->>UE: 2. RAR + Note right of gNB-DU: Allocate new C-RNTI and SRB1 configuration + UE->>gNB-DU: 3. RRCReestablishmentRequest (old C-RNTI, old PCI) + gNB-DU->>gNB-CU: 4. INITIAL UL RRC MESSAGE TRANSFER (new C-RNTI, RRC message) + gNB-CU-->>gNB-DU: 5. DL RRC MESSAGE TRANSFER (old gNB-DU FIAP UE ID) + gNB-DU-->>UE: 6. RRCReestablishment + Note right of gNB-DU: Find UE context based on old gNB-DU UE FIAP ID, replace old C-RNTI/PCI with new C-RNTI/PCI + UE->>gNB-DU: 7. RRCReestablishmentComplete + gNB-DU->>gNB-CU: 8. UL RRC MESSAGE TRANSFER + gNB-CU-->>gNB-DU: 9. UE CONTEXT MODIFICATION REQUEST + gNB-DU-->>gNB-CU: 10. UE CONTEXT MODIFICATION RESPONSE + gNB-CU-->>gNB-DU: 9'. UE CONTEXT MODIFICATION REQUIRED + gNB-DU-->>gNB-CU: 10'. UE CONTEXT MODIFICATION CONFIRM + gNB-DU-->>UE: 12. RRCReconfiguration + UE->>gNB-DU: 13. RRCReconfigurationComplete + gNB-DU->>gNB-CU: 14. UL RRC MESSAGE TRANSFER + +``` + +Sequence diagram of RRC connection reestablishment procedure between UE, gNB-DU, and gNB-CU. + +**Figure 8.7-1: RRC connection reestablishment procedure** + +1. The UE sends a preamble to the gNB-DU. +2. The gNB-DU allocates new C-RNTI and responds with RAR. +3. The UE sends an *RRCReestablishmentRequest* message to the gNB-DU, which contains old C-RNTI and old PCI. +4. The gNB-DU includes the RRC message and, if the UE is admitted, the corresponding low layer configuration for the UE in the INITIAL UL RRC MESSAGE TRANSFER message and transfers to the gNB-CU. The INITIAL UL RRC MESSAGE TRANSFER message includes the new C-RNTI. If the gNB-DU identifies the UE as a Reduced Capability UE during the random access procedure, a NR RedCap UE Indication is provided in the INITIAL UL RRC MESSAGE TRANSFER message. +5. The gNB-CU includes an *RRCReestablishment* message and transfers to the gNB-DU. If the UE requests to reestablish RRC connection in the last serving gNB-DU, the DL RRC MESSAGE TRANSFER message shall include old gNB-DU UE FIAP ID. +6. The gNB-DU retrieves the UE context based on the old gNB-DU UE FIAP ID, and replaces old C-RNTI/PCI with new C-RNTI/PCI. It sends the *RRCReestablishment* message to UE. + +- 7-8. The UE sends an *RRCReestablishmentComplete* message to the gNB-DU. The gNB-DU encapsulates the RRC message in the UL RRC MESSAGE TRANSFER message and sends to the gNB-CU. +- 9-10. The gNB-CU triggers an UE Context Modification procedure by sending UE CONTEXT MODIFICATION REQUEST message, which may include DRBs to be modified and released list. The gNB-DU responses with the UE CONTEXT MODIFICATION RESPONSE message. +- 9'-10'. The gNB-DU triggers an UE Context Modification procedure by sending UE CONTEXT MODIFICATION REQUIRED message, which may include DRBs to be modified and released list. The gNB-CU responses with UE CONTEXT MODIFICATION CONFIRM message. +- NOTE: Here it is assumed that the UE accessed the original gNB-DU where the UE context is available for that UE, and either steps 9-10 or steps 9'-10' may be executed or both could be skipped. +- NOTE: If the UE accessed from a gNB-DU other than the original one, the gNB-CU should trigger the UE Context Setup procedure toward this new gNB-DU. +- 11-12. The gNB-CU includes an *RRCReconfiguration* message into the DL RRC MESSAGE TRANSFER message and transfers to the gNB-DU. The gNB-DU forwards it to the UE. +- 13-14. The UE sends an *RRCReconfigurationComplete* message to the gNB-DU, and the gNB-DU forwards it to the gNB-CU. + +## 8.8 Multiple TNLAs for F1-C + +In the following, the procedure for managing multiple TNLAs for F1-C is described. + +![Sequence diagram showing the procedure for managing multiple TNLAs for F1-C between gNB-DU and gNB-CU.](9e26cd5584f423e1b2155fb341db579f_img.jpg) + +``` + +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: 1. TNLA establishment (TNLA1) + gNB-DU->>gNB-CU: 1. TNLA establishment (TNLA1) + gNB-CU-->>gNB-DU: 1. TNLA establishment (TNLA1) + gNB-DU->>gNB-CU: 2. F1 SETUP REQUEST + gNB-CU-->>gNB-DU: 3. F1 SETUP RESPONSE + gNB-CU->>gNB-DU: 4. GNB-CU CONFIGURATION UPDATE + Note left of gNB-DU: 5. TNLA establishment (TNLA2) + gNB-DU->>gNB-CU: 5. TNLA establishment (TNLA2) + gNB-CU-->>gNB-DU: 5. TNLA establishment (TNLA2) + gNB-DU->>gNB-CU: 6. GNB-CU CONFIGURATION UPDATE ACK + Note left of gNB-DU: 7. TNLA establishment (TNLA3) + gNB-DU->>gNB-CU: 7. TNLA establishment (TNLA3) + gNB-CU-->>gNB-DU: 7. TNLA establishment (TNLA3) + gNB-DU->>gNB-CU: 8. GNB-DU CONFIGURATION UPDATE + gNB-CU-->>gNB-DU: 9. GNB-DU CONFIGURATION UPDATE ACK + +``` + +The diagram illustrates the interaction between a gNB-DU and a gNB-CU for managing multiple TNLAs. It consists of nine steps: 1. TNLA establishment (TNLA1) from gNB-DU to gNB-CU; 2. F1 SETUP REQUEST from gNB-DU to gNB-CU; 3. F1 SETUP RESPONSE from gNB-CU to gNB-DU; 4. GNB-CU CONFIGURATION UPDATE from gNB-CU to gNB-DU; 5. TNLA establishment (TNLA2) from gNB-DU to gNB-CU; 6. GNB-CU CONFIGURATION UPDATE ACK from gNB-DU to gNB-CU; 7. TNLA establishment (TNLA3) from gNB-DU to gNB-CU; 8. GNB-DU CONFIGURATION UPDATE from gNB-DU to gNB-CU; and 9. GNB-DU CONFIGURATION UPDATE ACK from gNB-CU to gNB-DU. Steps 1, 5, and 7 are highlighted with dashed lines and arrows, indicating TNLA establishment procedures. + +Sequence diagram showing the procedure for managing multiple TNLAs for F1-C between gNB-DU and gNB-CU. + +Figure 8.8-1: Managing multiple TNLAs for F1-C. + +1. The gNB-DU establishes the first TNLA with the gNB-CU using a configured TNL address. + +NOTE: The gNB-DU may use different source and/or destination IP end point(s) if the TNL establishment towards one IP end point fails. How the gNB-DU gets the remote IP end point(s) and its own IP address are outside the scope of this specification. + +- 2-3. Once the TNLA has been established, the gNB-DU initiates the F1 Setup procedure to exchange application level configuration data. +- 4-6. The gNB-CU may add additional TNL Endpoint(s) to be used for F1-C signalling between the gNB-CU and the gNB-DU pair using the gNB-CU Configuration Update procedure. The gNB-CU Configuration Update procedure also allows the gNB-CU to request the gNB-DU to modify or release TNLA(s). +- 7-9. The gNB-DU may add additional TNL association(s) to be used for F1-C signalling using a gNB-CU endpoint already in use for existing TNL associations between the gNB-CU and the gNB-DU pair. The gNB-DU CONFIGURATION UPDATE message including the gNB-DU ID shall be the first F1AP message sent on an additional TNLA of an already setup F1-C interface instance after the TNL association has become operational. + +The F1AP UE TNLA binding is a binding between a F1AP UE association and a specific TNL association for a given UE. After the F1AP UE TNLA binding is created, the gNB-CU can update the UE TNLA binding by sending the F1AP message for the UE to the gNB-DU via a different TNLA. The gNB-DU shall update the F1AP UE TNLA binding with the new TNLA. The gNB-DU Configuration Update procedure also allows the gNB-DU to inform the gNB-CU that the indicated TNLA(s) will be removed by the gNB-DU. + +## 8.9 Overall procedures involving E1 and F1 + +The following clauses describe the overall procedures involving E1 and F1. + +NOTE: The general principles and procedures described in this clause also apply to ng-eNB and W1/E1 interface, i.e. W1 interface between ng-eNB-DU and ng-eNB-CU-CP/ng-eNB-CU-UP, E1 interface between ng-eNB-CU-CP and ng-eNB-CU-UP, if not explicitly specified otherwise. + +### 8.9.1 UE Initial Access + +The signalling flow for UE Initial access involving E1 and F1 is shown in Figure 8.9.1-1. + +![Sequence diagram of UE Initial Access procedure involving E1 and F1. Lifelines: UE, gNB-DU, gNB-CU-CP, gNB-CU-UP, AMF. The sequence shows RRC setup, initial context setup, bearer context setup, and security mode command exchanges between the UE and the gNB components, with the gNB-CU-CP interacting with the AMF and gNB-CU-UP.](e2c120be98ede6deb60dd341f5a9803b_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB-DU + participant gNB-CU-CP + participant gNB-CU-UP + participant AMF + + Note left of UE: Steps 1-8 are defined in clause 8.1. + UE->>gNB-DU: 1. RRCSetupRequest + gNB-DU->>gNB-CU-CP: 2. INITIAL UL RRC MESSAGE TRANSFER + gNB-CU-CP->>gNB-DU: 3. DL RRC MESSAGE TRANSFER + gNB-DU->>UE: 4. RRCSetup + UE->>gNB-DU: 5. RRCSetupComplete + gNB-DU->>gNB-CU-CP: 6. UL RRC MESSAGE TRANSFER + gNB-CU-CP->>AMF: 7. INITIAL UE MESSAGE + AMF->>gNB-CU-CP: 8. INITIAL CONTEXT SETUP REQUEST + Note right of gNB-CU-CP: 9. The gNB-CU-CP sends the BEARER CONTEXT SETUP REQUEST message to establish the bearer context in the gNB-CU-UP. + gNB-CU-CP->>gNB-CU-UP: 9. BEARER CONTEXT SETUP REQUEST + Note right of gNB-CU-UP: 10. The gNB-CU-UP sends the BEARER CONTEXT SETUP RESPONSE message to the gNB-CU-CP, including F1-U UL TEID and transport layer address allocated by the gNB-CU-UP. + gNB-CU-UP->>gNB-CU-CP: 10. BEARER CONTEXT SETUP RESPONSE + gNB-CU-CP->>gNB-DU: 11. UE CONTEXT SETUP REQUEST + gNB-DU->>UE: 12. SecurityModeCommand + gNB-DU->>gNB-CU-CP: 13. UE CONTEXT SETUP RESPONSE + Note right of gNB-CU-CP: 14. The gNB-CU-CP sends the BEARER CONTEXT MODIFICATION REQUEST message to the gNB-CU-UP, including F1-U DL TEID and transport layer address allocated by the gNB-DU. + gNB-CU-CP->>gNB-CU-UP: 14. BEARER CONTEXT MODIFICATION REQUEST + Note right of gNB-CU-UP: 15. The gNB-CU-UP sends the BEARER CONTEXT MODIFICATION RESPONSE message to the gNB-CU-CP. + gNB-CU-UP->>gNB-CU-CP: 15. BEARER CONTEXT MODIFICATION RESPONSE + Note left of UE: Steps 16-22 are defined in clause 8.1. + UE->>gNB-DU: 16. SecurityModeComplete + gNB-DU->>gNB-CU-CP: 17. UL RRC MESSAGE TRANSFER + gNB-CU-CP->>gNB-DU: 18. DL RRC MESSAGE TRANSFER + gNB-DU->>UE: 19. RRCReconfiguration + UE->>gNB-DU: 20. RRCReconfigurationComplete + gNB-DU->>gNB-CU-CP: 21. UL RRC MESSAGE TRANSFER + gNB-CU-CP->>AMF: 22. INITIAL CONTEXT SETUP RESPONSE + +``` + +Sequence diagram of UE Initial Access procedure involving E1 and F1. Lifelines: UE, gNB-DU, gNB-CU-CP, gNB-CU-UP, AMF. The sequence shows RRC setup, initial context setup, bearer context setup, and security mode command exchanges between the UE and the gNB components, with the gNB-CU-CP interacting with the AMF and gNB-CU-UP. + +**Figure 8.9.1-1: UE Initial Access procedure involving E1 and F1** + +Steps 1-8 are defined in clause 8.1. + +9. The gNB-CU-CP sends the BEARER CONTEXT SETUP REQUEST message to establish the bearer context in the gNB-CU-UP. + +10. The gNB-CU-UP sends the BEARER CONTEXT SETUP RESPONSE message to the gNB-CU-CP, including F1-U UL TEID and transport layer address allocated by the gNB-CU-UP. + +Steps 11-13 are defined in clause 8.1. + +14. The gNB-CU-CP sends the BEARER CONTEXT MODIFICATION REQUEST message to the gNB-CU-UP, including F1-U DL TEID and transport layer address allocated by the gNB-DU. + +15. The gNB-CU-UP sends the BEARER CONTEXT MODIFICATION RESPONSE message to the gNB-CU-CP. + +Steps 16-22 are defined in clause 8.1. + +NOTE: Steps 14-15 and steps 16-17 can happen in parallel, but both are before step 18. + +### 8.9.2 Bearer context setup over F1-U + +Figure 8.9.2-1 shows the procedure used to setup the bearer context in the gNB-CU-UP. + +![Sequence diagram illustrating Bearer context setup over F1-U. The diagram shows three entities: gNB-DU, gNB-CU-UP, and gNB-CU-CP. The sequence starts with a trigger in gNB-CU-CP (0. Bearer context setup is triggered). Step 1: gNB-CU-CP sends a BEARER CONTEXT SETUP REQUEST to gNB-CU-UP. Step 2: gNB-CU-UP sends a BEARER CONTEXT SETUP RESPONSE to gNB-CU-CP. Step 3: gNB-CU-CP initiates the F1 UE context setup procedure with gNB-DU. Step 4: gNB-CU-CP sends a BEARER CONTEXT MODIFICATION REQUEST to gNB-CU-UP. Step 5: gNB-CU-UP sends a BEARER CONTEXT MODIFICATION RESPONSE to gNB-CU-CP. Uplink user data is shown as a dashed green arrow from gNB-DU to gNB-CU-UP. Downlink user data is shown as a dashed green arrow from gNB-CU-UP to gNB-DU.](0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg) + +``` + +sequenceDiagram + participant gNB-DU + participant gNB-CU-UP + participant gNB-CU-CP + Note right of gNB-CU-CP: 0. Bearer context setup is triggered + gNB-CU-CP->>gNB-CU-UP: 1. BEARER CONTEXT SETUP REQUEST + gNB-CU-UP-->>gNB-CU-CP: 2. BEARER CONTEXT SETUP RESPONSE + gNB-CU-CP->>gNB-DU: 3. F1 UE context setup procedure + gNB-CU-CP->>gNB-CU-UP: 4. BEARER CONTEXT MODIFICATION REQUEST + gNB-CU-UP-->>gNB-CU-CP: 5. BEARER CONTEXT MODIFICATION RESPONSE + Note left of gNB-CU-UP: Uplink user data + Note right of gNB-CU-UP: Downlink user data + +``` + +Sequence diagram illustrating Bearer context setup over F1-U. The diagram shows three entities: gNB-DU, gNB-CU-UP, and gNB-CU-CP. The sequence starts with a trigger in gNB-CU-CP (0. Bearer context setup is triggered). Step 1: gNB-CU-CP sends a BEARER CONTEXT SETUP REQUEST to gNB-CU-UP. Step 2: gNB-CU-UP sends a BEARER CONTEXT SETUP RESPONSE to gNB-CU-CP. Step 3: gNB-CU-CP initiates the F1 UE context setup procedure with gNB-DU. Step 4: gNB-CU-CP sends a BEARER CONTEXT MODIFICATION REQUEST to gNB-CU-UP. Step 5: gNB-CU-UP sends a BEARER CONTEXT MODIFICATION RESPONSE to gNB-CU-CP. Uplink user data is shown as a dashed green arrow from gNB-DU to gNB-CU-UP. Downlink user data is shown as a dashed green arrow from gNB-CU-UP to gNB-DU. + +**Figure 8.9.2-1: Bearer context setup over F1-U** + +0. Bearer context setup (e.g., following an SGNB ADDITION REQUEST message from the MeNB) is triggered in gNB-CU-CP. +1. The gNB-CU-CP sends a BEARER CONTEXT SETUP REQUEST message containing UL TNL address information for S1-U or NG-U, and if required, DL TNL address information for X2-U to setup the bearer context in the gNB-CU-UP. For NG-RAN, the gNB-CU-CP decides flow-to-DRB mapping and sends the generated SDAP and PDCP configuration to the gNB-CU-UP. +- NOTE: In case of Conditional Handover or Conditional PSCell Addition/Change, the BEARER CONTEXT SETUP REQUEST message indicates to ignore the included security context and not to initiate sending downlink packets until the UE successfully accesses. Up to implementation, the gNB-CU-CP may request to establish bearer context as if a regular HO was requested. +2. The gNB-CU-UP responds with a BEARER CONTEXT SETUP RESPONSE message containing the UL TNL address information for F1-U, and DL TNL address information for S1-U or NG-U, and if required, UL TNL address information for X2-U or Xn-U. +- NOTE: The indirect data transmission for split bearer through the gNB-CU-UP is not precluded. +3. F1 UE context setup procedure is performed to setup one or more bearers in the gNB-DU. +4. The gNB-CU-CP sends a BEARER CONTEXT MODIFICATION REQUEST message containing the DL TNL address information for F1-U or Xn-U, and PDCP status. +- NOTE: In case the indirect path indication is received in step 4, the gNB-CU-UP may not discard the DL data based on the Downlink Data Delivery Status frame received from the gNB-DU. During the inter-gNB indirect-to-direct or indirect-to-indirect path switching, the source gNB-CU-UP forwards the buffered DL data to the target gNB as specified in TS 38.300 [2]. +5. The gNB-CU-UP responds with a BEARER CONTEXT MODIFICATION RESPONSE message. + +### 8.9.3 Bearer context release over F1-U + +#### 8.9.3.1 gNB-CU-CP initiated bearer context release + +Figure 8.9.3.1-1 shows the procedure used to release the bearer context in the gNB-CU-UP initiated by the gNB-CU-CP. + +![Sequence diagram for gNB-CU-CP initiated bearer context release over F1-U. The diagram shows three lifelines: gNB-DU, gNB-CU-UP, and gNB-CU-CP. The sequence starts with the gNB-CU-CP triggering the release (0). It then sends a BEARER CONTEXT MODIFICATION REQUEST (1) to the gNB-CU-UP, which responds with a BEARER CONTEXT MODIFICATION RESPONSE (2). The gNB-CU-CP then initiates an F1 UE context modification procedure (3) with the gNB-DU. A dashed box indicates a possible UE Context Release from MeNB (4). The gNB-CU-CP sends a BEARER CONTEXT RELEASE COMMAND (5) to the gNB-CU-UP, which initiates an F1 UE context release procedure (6) with the gNB-DU. Finally, the gNB-CU-UP sends a BEARER CONTEXT RELEASE COMPLETE (7) to the gNB-CU-CP.](d6c377ae3e619ff992bd3647dbf43593_img.jpg) + +``` + +sequenceDiagram + participant gNB-DU + participant gNB-CU-UP + participant gNB-CU-CP + Note right of gNB-CU-CP: 0. Bearer context release is triggered + gNB-CU-CP->>gNB-CU-UP: 1. BEARER CONTEXT MODIFICATION REQUEST + gNB-CU-UP-->>gNB-CU-CP: 2. BEARER CONTEXT MODIFICATION RESPONSE + gNB-CU-CP-->>gNB-DU: 3. F1 UE context modification procedure + Note right of gNB-CU-CP: 4. UE Context Release from MeNB + gNB-CU-CP->>gNB-CU-UP: 5. BEARER CONTEXT RELEASE COMMAND + gNB-CU-UP-->>gNB-DU: 6. F1 UE context release procedure + gNB-CU-UP->>gNB-CU-CP: 7. BEARER CONTEXT RELEASE COMPLETE + +``` + +Sequence diagram for gNB-CU-CP initiated bearer context release over F1-U. The diagram shows three lifelines: gNB-DU, gNB-CU-UP, and gNB-CU-CP. The sequence starts with the gNB-CU-CP triggering the release (0). It then sends a BEARER CONTEXT MODIFICATION REQUEST (1) to the gNB-CU-UP, which responds with a BEARER CONTEXT MODIFICATION RESPONSE (2). The gNB-CU-CP then initiates an F1 UE context modification procedure (3) with the gNB-DU. A dashed box indicates a possible UE Context Release from MeNB (4). The gNB-CU-CP sends a BEARER CONTEXT RELEASE COMMAND (5) to the gNB-CU-UP, which initiates an F1 UE context release procedure (6) with the gNB-DU. Finally, the gNB-CU-UP sends a BEARER CONTEXT RELEASE COMPLETE (7) to the gNB-CU-CP. + +**Figure 8.9.3.1-1: Bearer context release over F1-U – gNB-CU-CP initiated** + +0. Bearer context release (e.g., following an SGNB RELEASE REQUEST message from the MeNB) is triggered in gNB-CU-CP. + 1. The gNB-CU-CP sends a BEARER CONTEXT MODIFICATION REQUEST message to the gNB-CU-UP. + 2. The gNB-CU-UP responds with a BEARER CONTEXT MODIFICATION RESPONSE carrying the PDCP UL/DL status. + 3. F1 UE context modification procedure is performed to stop the data transmission for the UE. It is up to gNB-DU implementation when to stop the UE scheduling. +- NOTE: step 1-3 are performed only if the PDCP status of the bearer(s) needs to be preserved e.g., for bearer type change. +4. The gNB-CU-CP may receive the UE CONTEXT RELEASE message from the MeNB in EN-DC operation as described in clause 8.4.2.1. + 5. and 7. Bearer context release procedure is performed. + 6. F1 UE context release procedure is performed to release the UE context in the gNB-DU. + +#### 8.9.3.2 gNB-CU-UP initiated bearer context release + +Figure 8.9.3.2-1 shows the procedure used to release the bearer context in the gNB-CU-UP initiated by the gNB-CU-UP. + +![Sequence diagram for Bearer context release over F1-U initiated by gNB-CU-UP. The diagram shows three lifelines: gNB-DU, gNB-CU-UP, and gNB-CU-CP. The process starts with the gNB-CU-UP triggering the release. It then sends a BEARER CONTEXT RELEASE REQUEST to the gNB-CU-CP. The gNB-CU-CP responds with a BEARER CONTEXT MODIFICATION REQUEST to the gNB-CU-UP, which in turn sends a BEARER CONTEXT MODIFICATION RESPONSE. The gNB-CU-CP then initiates the F1 UE context modification procedure with the gNB-DU. A dashed box indicates a UE Context Release from the MeNB to the gNB-CU-CP. The gNB-CU-CP sends a BEARER CONTEXT RELEASE COMMAND to the gNB-CU-UP, which responds with a BEARER CONTEXT RELEASE COMPLETE. Finally, the gNB-CU-CP initiates the F1 UE context release procedure with the gNB-DU.](4b398c5e8c4fd656d5b7a61806400650_img.jpg) + +``` + +sequenceDiagram + participant gNB-DU + participant gNB-CU-UP + participant gNB-CU-CP + Note right of gNB-CU-UP: 0. Bearer context release is triggered + gNB-CU-UP->>gNB-CU-CP: 1. BEARER CONTEXT RELEASE REQUEST + gNB-CU-CP-->>gNB-CU-UP: 2. BEARER CONTEXT MODIFICATION REQUEST + gNB-CU-UP-->>gNB-CU-CP: 3. BEARER CONTEXT MODIFICATION RESPONSE + gNB-CU-CP-->>gNB-DU: 4. F1 UE context modification procedure + Note right of gNB-CU-CP: 5. UE Context Release from MeNB + gNB-CU-CP-->>gNB-CU-UP: 6. BEARER CONTEXT RELEASE COMMAND + gNB-CU-UP-->>gNB-CU-CP: 7. BEARER CONTEXT RELEASE COMPLETE + gNB-CU-CP-->>gNB-DU: 8. F1 UE context release procedure + +``` + +Sequence diagram for Bearer context release over F1-U initiated by gNB-CU-UP. The diagram shows three lifelines: gNB-DU, gNB-CU-UP, and gNB-CU-CP. The process starts with the gNB-CU-UP triggering the release. It then sends a BEARER CONTEXT RELEASE REQUEST to the gNB-CU-CP. The gNB-CU-CP responds with a BEARER CONTEXT MODIFICATION REQUEST to the gNB-CU-UP, which in turn sends a BEARER CONTEXT MODIFICATION RESPONSE. The gNB-CU-CP then initiates the F1 UE context modification procedure with the gNB-DU. A dashed box indicates a UE Context Release from the MeNB to the gNB-CU-CP. The gNB-CU-CP sends a BEARER CONTEXT RELEASE COMMAND to the gNB-CU-UP, which responds with a BEARER CONTEXT RELEASE COMPLETE. Finally, the gNB-CU-CP initiates the F1 UE context release procedure with the gNB-DU. + +**Figure 8.9.3.2-1: Bearer context release over F1-U – gNB-CU-UP initiated** + +0. Bearer context release is triggered in gNB-CU-UP e.g., due to local failure. +1. The gNB-CU-UP sends a BEARER CONTEXT RELEASE REQUEST message to request the release of the bearer context in the gNB-CU-UP. This message may contain the PDCP status. +- 2.- 5. If the PDCP status needs to be preserved, the E1 Bearer Context Modification and the F1 UE Context Modification procedures are performed. The E1 Bearer Context Modification procedure is used to convey data forwarding information to the gNB-CU-UP. The gNB-CU-CP may receive the UE Context Release from the MeNB. +6. The gNB-CU-CP sends a BEARER CONTEXT RELEASE COMMAND message to release the bearer context in the gNB-CU-UP. +7. The gNB-CU-UP responds with a BEARER CONTEXT RELEASE COMPLETE to confirm the release of the bearer context including also data forwarding information. +8. F1 UE context release procedure may be performed to release the UE context in the gNB-DU. + +### 8.9.4 Inter-gNB handover involving gNB-CU-UP change + +Figure 8.9.4-1 shows the procedure used for inter-gNB handover involving gNB-CU-UP change. Overall inter-gNB handover procedure is specified in TS 37.340 [12]. + +![Sequence diagram for Inter-gNB handover involving gNB-CU-UP change. The diagram shows interactions between Source gNB (DU, CU-UP, CU-CP), Target gNB (DU, CU-UP, CU-CP), and AMF/UPF. The process involves HO Request, Bearer Context Setup, HO Request Acknowledge, F1 UE Context Modification, Bearer Context Modification, SN Status Transfer, HO Success, and UE Context Release.](347010b7ac06d3ae97927fde0f784d7c_img.jpg) + +``` + +sequenceDiagram + participant Source gNB-DU + participant Source gNB-CU-UP + participant Source gNB-CU-CP + participant Target gNB-DU + participant Target gNB-CU-UP + participant Target gNB-CU-CP + participant AMF/UPF + + Note right of Source gNB-CU-CP: Source gNB + Note right of Target gNB-CU-CP: Target gNB + + Source gNB-CU-CP->>Target gNB-CU-CP: 1. HANDOVER REQUEST + Note right of Target gNB-CU-CP: 2-4. Bearer Context Setup procedure + Target gNB-CU-CP->>Source gNB-CU-CP: 5. HANDOVER REQUEST ACKNOWLEDGE (data forwarding info) + Source gNB-CU-CP->>Source gNB-DU: 6. F1 UE Context Modification procedure + Note right of Source gNB-CU-CP: 7-8. Bearer Context Modification procedure + Source gNB-CU-CP->>Source gNB-CU-UP: 7. BEARER CONTEXT MODIFICATION REQUEST (data forwarding info) + Source gNB-CU-UP->>Source gNB-CU-CP: 8. BEARER CONTEXT MODIFICATION RESPONSE + Source gNB-CU-CP->>Target gNB-CU-CP: 9. SN STATUS TRANSFER or EARLY STATUS TRANSFER + Note right of Target gNB-CU-CP: 10-11. Bearer Context Modification procedure + Target gNB-CU-CP->>Target gNB-CU-UP: 10. BEARER CONTEXT MODIFICATION REQUEST + Target gNB-CU-UP->>Target gNB-CU-CP: 11. BEARER CONTEXT MODIFICATION RESPONSE + Note right of Source gNB-CU-UP: 12. Data Forwarding + Source gNB-CU-UP->>Target gNB-CU-UP: 12. Data Forwarding + Note right of Target gNB-DU: UE attached via RACH + Target gNB-CU-CP->>Source gNB-CU-CP: 12a. HANDOVER SUCCESS + Source gNB-CU-CP->>Source gNB-DU: 12b. F1 UE Context Modification procedure + Note right of Source gNB-CU-CP: 12c-12d. Bearer Context Modification procedure + Source gNB-CU-CP->>Source gNB-CU-UP: 12c. BEARER CONTEXT MODIFICATION REQUEST + Source gNB-CU-UP->>Source gNB-CU-CP: 12d. BEARER CONTEXT MODIFICATION RESPONSE + Source gNB-CU-CP->>Target gNB-CU-CP: 12e. SN STATUS TRANSFER + Note right of Target gNB-CU-CP: 12f-12g. Bearer Context Modification procedure + Target gNB-CU-CP->>Target gNB-CU-UP: 12f. BEARER CONTEXT MODIFICATION REQUEST + Target gNB-CU-UP->>Target gNB-CU-CP: 12g. BEARER CONTEXT MODIFICATION RESPONSE + Note right of AMF/UPF: 13. Path Switch procedure is performed + AMF/UPF->>Target gNB-CU-UP: 14. End Marker Packet + Target gNB-CU-UP->>Source gNB-CU-UP: 14. End Marker Packet + Note right of Target gNB-CU-UP: 15. New Path + Target gNB-CU-UP->>AMF/UPF: 15. New Path + Source gNB-CU-CP->>Target gNB-CU-CP: 16. UE CONTEXT RELEASE + Source gNB-CU-CP->>Source gNB-CU-UP: 17. BEARER CONTEXT RELEASE COMMAND + Source gNB-CU-CP->>Source gNB-DU: 18. F1 UE Context Release procedure + Source gNB-CU-CP->>Source gNB-CU-UP: 19. BEARER CONTEXT RELEASE COMPLETE + +``` + +Sequence diagram for Inter-gNB handover involving gNB-CU-UP change. The diagram shows interactions between Source gNB (DU, CU-UP, CU-CP), Target gNB (DU, CU-UP, CU-CP), and AMF/UPF. The process involves HO Request, Bearer Context Setup, HO Request Acknowledge, F1 UE Context Modification, Bearer Context Modification, SN Status Transfer, HO Success, and UE Context Release. + +**Figure 8.9.4-1: Inter-gNB handover involving gNB-CU-UP change** + +- The source gNB-CU-CP sends HANDOVER REQUEST message to the target gNB-CU-CP. In case of Conditional Handover, the target gNB is regarded as a candidate gNB which is only accessed by the UE when the CHO condition(s) are fulfilled. + 4. Bearer Context Setup procedure is performed as described in clause 8.9.2. + - The target gNB-CU-CP responds the source gNB-CU-CP with an HANDOVER REQUEST ACKNOWLEDGE message. +- NOTE: In case of Conditional Handover, it is up to target gNB-CU-CP implementation to make sure that the EARLY STATUS TRANSFER information is forwarded to the right gNB-CU-UP (e.g. separate UE-associated signalling connection over Xn interface for each gNB-CU-UP). +- The F1 UE Context Modification procedure is performed to send the handover command to the UE, and to indicate to stop the data transmission for the UE. +- NOTE: In case of DAPS Handover or Conditional Handover, the F1 UE Context Modification procedure in step 6 does not indicate to stop the data transmission for the UE. Instead, the F1 DL RRC Message Transfer procedure can be used which carries the handover command to the UE. +- Bearer Context Modification procedure (gNB-CU-CP initiated) is performed to enable the gNB-CU-CP to retrieve the PDCP UL/DL status and to exchange data forwarding information for the bearer. + - The source gNB-CU-CP sends an SN STATUS TRANSFER message to the target gNB-CU-CP. + +- NOTE: In case of DAPS Handover, the EARLY STATUS TRANSFER message is sent for DRBs configured with DAPS instead of the SN STATUS TRANSFER message. +- NOTE: In case of Conditional Handover, the EARLY STATUS TRANSFER message is sent only if early data forwarding is applied. +- NOTE: The COUNT related info for the EARLY STATUS TRANSFER message is retrieved from the source gNB-CU-UP via the steps 7/8. +- 10-11. Bearer Context Modification procedure is performed as described in clause 8.9.2. The target gNB-CU-CP does not transfer the PDCP UL/DL status carried from the SN STATUS TRANSFER message to the target gNB-CU-UP if the PDCP status does not need to be preserved (e.g. full configuration). In case of DAPS Handover or Conditional Handover, the COUNT related info carried by the EARLY STATUS TRANSFER message is provided to the target gNB-CU-UP. +12. Data Forwarding may be performed from the source gNB-CU-UP to the target gNB-CU-UP. +- NOTE: In case of Conditional Handover, the UE performs RACH when the CHO condition(s) are fulfilled. Once successfully accessed, the target gNB-DU sends an ACCESS SUCCESS message to inform the target gNB-CU-CP of which cell the UE has accessed through. The target gNB-CU-CP may forward to the target gNB-CU-UP, necessary information for sending downlink packets (i.e. DL TNL address information for F1-U and UP security information corresponding to the accessed cell), via a Bearer context modification procedure. The target gNB-CU-CP may initiate Bearer context release procedure toward the other signalling connections or other candidate target gNB-CU-UPs, if any, to release the prepared conditional handover resources for the UE. +- 12a. In case of DAPS Handover or Conditional Handover, the target gNB-CU-CP sends the HANDOVER SUCCESS message to the source gNB-CU-CP to inform that the UE has successfully accessed the target cell. +- 12b In case of DAPS Handover or Conditional Handover, the F1 UE Context Modification procedure is performed to indicate to stop the data transmission for the UE. +- 12c-12d. In case of DAPS Handover or Conditional Handover, the Bearer context modification procedure (gNB-CU-CP initiated) is performed to indicate the source gNB-CU-UP to stop packet delivery and also to retrieve the PDCP UL/DL status. +- 12e. In case of DAPS Handover or Conditional Handover, the source gNB-CU-CP sends the SN STATUS TRANSFER message to the target gNB-CU-CP. +- 12f-12g. In case of DAPS Handover or Conditional Handover, the Bearer context modification procedure is performed to provide the PDCP UL/DL status to the target gNB-CU-UP only if the PDCP status needs to be preserved as described in TS 38.300 [2]. +- NOTE: In case of Conditional Handover, inactivity monitoring is performed after step 12g. +- 13-15. Path Switch procedure is performed to update the DL TNL address information for the NG-U towards the core network. +16. The target gNB-CU-CP sends an UE CONTEXT RELEASE message to the source gNB-CU-CP. +17. and 19. Bearer Context Release procedure is performed. +18. F1 UE Context Release procedure is performed to release the UE context in the source gNB-DU. + +### 8.9.5 Change of gNB-CU-UP + +Figure 8.9.5-1 shows the procedure used for the change of gNB-CU-UP within a gNB. + +![Sequence diagram illustrating the 'Change of gNB-CU-UP' procedure. The diagram shows interactions between gNB-DU, Source gNB-CU-UP, Target gNB-CU-UP, gNB-CU-CP, and AMF/UPF. The process starts with a change trigger in gNB-CU-CP, followed by Bearer Context Setup, F1 UE context management, Bearer Context Modification (twice), Data Forwarding, End Marker Packet, New Path establishment, and finally Bearer Context Release.](2a476a0b3dbc3429436246db4784ff9f_img.jpg) + +``` + +sequenceDiagram + participant gNB-DU + participant Source gNB-CU-UP + participant Target gNB-CU-UP + participant gNB-CU-CP + participant AMF/UPF + + Note right of gNB-CU-CP: 1. Change of gNB-CU-UP is triggered + gNB-CU-CP->>Target gNB-CU-UP: 2. BEARER CONTEXT SETUP REQUEST + Target gNB-CU-UP-->>gNB-CU-CP: 3. BEARER CONTEXT SETUP RESPONSE + gNB-CU-CP->>gNB-DU: 4. F1 UE context management procedure (bearer modification) + gNB-CU-CP->>Source gNB-CU-UP: 5. BEARER CONTEXT MODIFICATION REQUEST + Source gNB-CU-UP-->>gNB-CU-CP: 6. BEARER CONTEXT MODIFICATION RESPONSE + gNB-CU-CP->>Target gNB-CU-UP: 7. BEARER CONTEXT MODIFICATION REQUEST + Target gNB-CU-UP-->>gNB-CU-CP: 8. BEARER CONTEXT MODIFICATION RESPONSE + Source gNB-CU-UP-->>Target gNB-CU-UP: 9. Data Forwarding + Note right of AMF/UPF: 10. PDU Session Resource Indication procedure is performed + Source gNB-CU-UP-->>Target gNB-CU-UP: 11. End Marker Packet + Target gNB-CU-UP-->>AMF/UPF: 12. New Path + gNB-CU-CP->>Source gNB-CU-UP: 13. BEARER CONTEXT RELEASE COMMAND + Source gNB-CU-UP-->>gNB-CU-CP: 14. BEARER CONTEXT RELEASE COMPLETE + +``` + +Sequence diagram illustrating the 'Change of gNB-CU-UP' procedure. The diagram shows interactions between gNB-DU, Source gNB-CU-UP, Target gNB-CU-UP, gNB-CU-CP, and AMF/UPF. The process starts with a change trigger in gNB-CU-CP, followed by Bearer Context Setup, F1 UE context management, Bearer Context Modification (twice), Data Forwarding, End Marker Packet, New Path establishment, and finally Bearer Context Release. + +**Figure 8.9.5-1: Change of gNB-CU-UP** + +1. Change of gNB-CU-UP is triggered in gNB-CU-CP based on e.g., measurement report from the UE. +- 2-3. Bearer Context Setup procedure is performed as described in clause 8.9.2. +4. F1 UE Context Modification procedure is performed to change the UL TNL address information for F1-U for one or more bearers in the gNB-DU. +- 5-6. Bearer Context Modification procedure (gNB-CU-CP initiated) is performed to enable the gNB-CU-CP to retrieve the PDCP UL/DL status and to exchange data forwarding information for the bearer. +- 7-8. Bearer Context Modification procedure is performed as described in clause 8.9.2. +9. Data Forwarding may be performed from the source gNB-CU-UP to the target gNB-CU-UP. +- 10-12. PDU Session Resource Modify Indication procedure is performed to update the DL TNL address information for the NG-U towards the core network. +- 13-14. Bearer Context Release procedure (gNB-CU-CP initiated) is performed as described in clause 8.9.3. + +### 8.9.6 RRC State transition + +#### 8.9.6.1 RRC Connected to RRC Inactive + +The procedure for changing the UE state from RRC-connected to RRC-inactive is shown in Figure 8.9.6.1-1. + +![Sequence diagram illustrating the RRC Connected to RRC Inactive state transition. The diagram shows four lifelines: UE, gNB-DU, gNB-CU-UP, and gNB-CU-CP. The sequence of messages is: 1. gNB-CU-CP sends BEARER CONTEXT SETUP REQUEST (inactivity timer) to gNB-CU-UP; 2. gNB-CU-UP sends BEARER CONTEXT SETUP RESPONSE to gNB-CU-CP; 3. gNB-CU-UP sends BEARER CONTEXT INACTIVITY NOTIFICATION to gNB-CU-CP; 4. gNB-CU-CP makes a decision to change the UE state to RRC-inactive; 5. gNB-CU-CP sends BEARER CONTEXT MODIFICATION REQUEST (with suspend indication) to gNB-CU-UP; 6. gNB-CU-UP sends BEARER CONTEXT MODIFICATION RESPONSE (report PDCP status for e.g., data reporting) to gNB-CU-CP; 7. gNB-CU-CP sends UE CONTEXT RELEASE COMMAND (with RRCRelease) to gNB-DU; 8. gNB-DU sends RRCRelease to UE; 9. gNB-DU sends UE CONTEXT RELEASE COMPLETE to gNB-CU-CP.](0931f3e098bd4539041de11c50cec2d2_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB-DU + participant gNB-CU-UP + participant gNB-CU-CP + Note right of gNB-CU-CP: 4. Decision of changing the UE state to RRC-inactive + gNB-CU-CP->>gNB-CU-UP: 1. BEARER CONTEXT SETUP REQUEST (inactivity timer) + gNB-CU-UP-->>gNB-CU-CP: 2. BEARER CONTEXT SETUP RESPONSE + gNB-CU-UP->>gNB-CU-CP: 3. BEARER CONTEXT INACTIVITY NOTIFICATION + gNB-CU-CP->>gNB-CU-UP: 5. BEARER CONTEXT MODIFICATION REQUEST (with suspend indication) + gNB-CU-UP-->>gNB-CU-CP: 6. BEARER CONTEXT MODIFICATION RESPONSE (report PDCP status for e.g., data reporting) + gNB-CU-CP->>gNB-DU: 7. UE CONTEXT RELEASE COMMAND (with RRCRelease) + gNB-DU->>UE: 8. RRCRelease + gNB-DU-->>gNB-CU-CP: 9. UE CONTEXT RELEASE COMPLETE + +``` + +Sequence diagram illustrating the RRC Connected to RRC Inactive state transition. The diagram shows four lifelines: UE, gNB-DU, gNB-CU-UP, and gNB-CU-CP. The sequence of messages is: 1. gNB-CU-CP sends BEARER CONTEXT SETUP REQUEST (inactivity timer) to gNB-CU-UP; 2. gNB-CU-UP sends BEARER CONTEXT SETUP RESPONSE to gNB-CU-CP; 3. gNB-CU-UP sends BEARER CONTEXT INACTIVITY NOTIFICATION to gNB-CU-CP; 4. gNB-CU-CP makes a decision to change the UE state to RRC-inactive; 5. gNB-CU-CP sends BEARER CONTEXT MODIFICATION REQUEST (with suspend indication) to gNB-CU-UP; 6. gNB-CU-UP sends BEARER CONTEXT MODIFICATION RESPONSE (report PDCP status for e.g., data reporting) to gNB-CU-CP; 7. gNB-CU-CP sends UE CONTEXT RELEASE COMMAND (with RRCRelease) to gNB-DU; 8. gNB-DU sends RRCRelease to UE; 9. gNB-DU sends UE CONTEXT RELEASE COMPLETE to gNB-CU-CP. + +**Figure 8.9.6.1-1: RRC Connected to RRC Inactive state transition.** + +1. The gNB-CU-CP sends BEARER CONTEXT SETUP REQUEST message with UE/PDU session/DRB level inactivity timer. + 2. The gNB-CU-UP sends BEARER CONTEXT SETUP RESPONSE message. + 3. The gNB-CU-UP sends BEARER CONTEXT INACTIVITY NOTIFICATION message with inactivity monitoring results. + 4. The gNB-CU-CP determines that the UE should enter RRC-inactive (e.g., after receiving Bearer Context Inactivity Notification procedure). + 5. The gNB-CU-CP sends BEARER CONTEXT MODIFICATION REQUEST message with a Bearer Context Status Change to the gNB-CU-UP, which indicates that the UE is entering RRC-inactive state. The gNB-CU-CP keeps the F1 UL TEIDs. + 6. The gNB-CU-UP sends the BEARER CONTEXT MODIFICATION RESPONSE message including the PDCP UL and DL status that may be needed for e.g., data volume reporting. The gNB-CU-UP keeps the Bearer Context, the UE-associated logical E1-connection, the NG-U related resource (e.g., NG-U DL TEIDs) and the F1 UL TEIDs. + 7. The gNB-CU-CP sends the UE CONTEXT RELEASE COMMAND message to the gNB-DU serving the UE, together with the *RRCRelease* message to be sent to the UE. + 8. The gNB-DU sends the *RRCRelease* message to the UE. + 9. The gNB-DU sends the UE CONTEXT RELEASE COMPLETE message to the gNB-CU-CP. +- NOTE: step 5 and step 7 can be performed at the same time. + +#### 8.9.6.2 RRC Inactive to other states + +The procedure for changing the UE state from RRC-inactive to RRC-connected is shown in Figure 8.9.6.2-1. + +![Sequence diagram illustrating the RRC Inactive to RRC Connected state transition. The diagram shows interactions between UE, gNB-DU, gNB-CU-UP, and gNB-CU-CP. The process starts with DL traffic detection on the NG-U tunnel(s) at the gNB-CU-UP, followed by a DL DATA NOTIFICATION to the gNB-CU-CP, which then sends a PAGING message to the gNB-DU, which in turn sends a Paging message to the UE. The UE responds with an RRCResumeRequest. The gNB-DU sends an INITIAL UL RRC MESSAGE TRANSFER to the gNB-CU-CP. The gNB-CU-CP sends a UE CONTEXT SETUP REQUEST (with UL TEIDs) to the gNB-DU. The gNB-DU responds with a UE CONTEXT SETUP RESPONSE (with DL TEIDs). The gNB-CU-CP and the UE perform the RRC-Resume procedure via the gNB-DU. The gNB-CU-CP sends a BEARER CONTEXT MODIFICATION REQUEST (with resume indication and DL TEIDs) to the gNB-CU-UP. The gNB-CU-UP responds with a BEARER CONTEXT MODIFICATION RESPONSE.](ffb6acd27b8e3a54392840948a75869f_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB-DU + participant gNB-CU-UP + participant gNB-CU-CP + + Note right of gNB-CU-UP: 0. DL traffic detected on the NG-U tunnel(s) + gNB-CU-UP->>gNB-CU-CP: 1. DL DATA NOTIFICATION + gNB-CU-CP->>gNB-DU: 2. PAGING + gNB-DU->>UE: 3. Paging + UE->>gNB-DU: 4. RRCResumeRequest + gNB-DU->>gNB-CU-CP: 5. INITIAL UL RRC MESSAGE TRANSFER + gNB-CU-CP->>gNB-DU: 6. UE CONTEXT SETUP REQUEST (UL TEIDs) + gNB-DU->>gNB-CU-CP: 7. UE CONTEXT SETUP RESPONSE (DL TEIDs) + gNB-CU-CP->>gNB-DU: 8. RRC-Resume + gNB-CU-CP->>gNB-CU-UP: 9. BEARER CONTEXT MODIFICATION REQUEST (with resume indication and DL TEIDs) + gNB-CU-UP->>gNB-CU-CP: 10. BEARER CONTEXT MODIFICATION RESPONSE + +``` + +Sequence diagram illustrating the RRC Inactive to RRC Connected state transition. The diagram shows interactions between UE, gNB-DU, gNB-CU-UP, and gNB-CU-CP. The process starts with DL traffic detection on the NG-U tunnel(s) at the gNB-CU-UP, followed by a DL DATA NOTIFICATION to the gNB-CU-CP, which then sends a PAGING message to the gNB-DU, which in turn sends a Paging message to the UE. The UE responds with an RRCResumeRequest. The gNB-DU sends an INITIAL UL RRC MESSAGE TRANSFER to the gNB-CU-CP. The gNB-CU-CP sends a UE CONTEXT SETUP REQUEST (with UL TEIDs) to the gNB-DU. The gNB-DU responds with a UE CONTEXT SETUP RESPONSE (with DL TEIDs). The gNB-CU-CP and the UE perform the RRC-Resume procedure via the gNB-DU. The gNB-CU-CP sends a BEARER CONTEXT MODIFICATION REQUEST (with resume indication and DL TEIDs) to the gNB-CU-UP. The gNB-CU-UP responds with a BEARER CONTEXT MODIFICATION RESPONSE. + +**Figure 8.9.6.2-1: RRC Inactive to RRC Connected state transition.** + +0. The gNB-CU-UP receives DL data on NG-U interface. +1. The gNB-CU-UP sends DL DATA NOTIFICATION message to the gNB-CU-CP. +2. The gNB-CU-CP sends PAGING message to the gNB-DU. +3. The gNB-DU sends the *Paging* message to the UE. +4. The UE sends *RRCResumeRequest* message either upon RAN paging or UL data arrival. +5. The gNB-DU sends the INITIAL UL RRC MESSAGE TRANSFER message to the gNB-CU-CP. +6. The gNB-CU-CP sends UE CONTEXT SETUP REQUEST message including the stored F1 UL TEIDs to create the UE context in the gNB-DU. +7. The gNB-DU responds with the UE CONTEXT SETUP RESPONSE message including the F1 DL TEIDs allocated for the DRBs. +8. The gNB-CU-CP and the UE perform the RRC-Resume procedure via the gNB-DU. +9. The gNB-CU-CP sends BEARER CONTEXT MODIFICATION REQUEST message with a RRC Resume indication, which indicates that the UE is resuming from RRC-inactive state. The gNB-CU-CP also includes the F1 DL TEIDs received from the gNB-DU in step 7. +10. The gNB-CU-UP responds with the BEARER CONTEXT MODIFICATION RESPONSE message. + +NOTE: steps 0-3 are needed only in case of DL data. + +NOTE steps 8 and 9 can be performed in parallel. + +### 8.9.7 Trace activation/deactivation over F1 and E1 + +Figure 8.9.6-1 shows the procedure used for the activation and the deactivation of UE traces in the gNB-DU, the gNB-CU-UP or both. + +![Sequence diagram showing trace activation and deactivation over F1 and E1 interfaces between AMF/MeNB, gNB-CU-CP, gNB-DU, and gNB-CU-UP.](b63f41ca262d8ce9ef8affb62607f32b_img.jpg) + +``` + +sequenceDiagram + participant AMF or MeNB + participant gNB-CU-CP + participant gNB-DU + participant gNB-CU-UP + + Note right of gNB-DU: 3. gNB-DU, gNB-CU-UP or both initiate the requested trace session + Note right of gNB-DU: 6. gNB-DU, gNB-CU-UP or both stop the trace session + + AMF or MeNB->>gNB-CU-CP: 1. TRACE START + gNB-CU-CP-->>gNB-DU: 2a. TRACE START + gNB-CU-CP-->>gNB-CU-UP: 2b. TRACE START + Note right of gNB-DU: 3. gNB-DU, gNB-CU-UP or both initiate the requested trace session + AMF or MeNB->>gNB-CU-CP: 4. DEACTIVATE TRACE + gNB-CU-CP-->>gNB-DU: 5a. DEACTIVATE TRACE + gNB-CU-CP-->>gNB-CU-UP: 5b. DEACTIVATE TRACE + Note right of gNB-DU: 6. gNB-DU, gNB-CU-UP or both stop the trace session + +``` + +Sequence diagram showing trace activation and deactivation over F1 and E1 interfaces between AMF/MeNB, gNB-CU-CP, gNB-DU, and gNB-CU-UP. + +**Figure 8.9.6-1: Trace activation/deactivation over F1 and E1** + +1. The gNB-CU-CP receives a TRACE START message from the AMF or the MeNB (in case of EN-DC). +2. The gNB-CU-CP initiates the Trace Start procedure by sending a TRACE START message to the gNB-DU, the gNB-CU-UP or both. +3. Upon reception of the TRACE START message, the gNB-DU, the gNB-CU-UP or both initiate the requested trace session and report it as described in TS 32.422 [20]. +4. The gNB-CU-CP receives a DEACTIVATE TRACE message from the AMF or the MeNB (in case of EN-DC). +5. The gNB-CU-CP initiates the Deactivate Trace procedure by sending a DEACTIVATE TRACE message to the gNB-DU, the gNB-CU-UP or both. +6. Upon reception of the DEACTIVATE TRACE message, the gNB-DU, the gNB-CU-UP or both stop the trace session for the indicated trace reference. + +### 8.9.8 BH RLC channel establishment procedure + +NOTE: The general principles and procedures described in this clause does not apply to ng-eNB + +The BH RLC channel is an RLC channel used for backhauling between IAB-node and IAB-donor-DU, or between different IAB-nodes. The BH RLC channel establishment may be triggered by a UE accessing the network and establishing a DRB. + +![Sequence diagram showing the signalling flow for IAB BH RLC channel establishment procedure between IAB-node 2, IAB-node 1, IAB-donor-DU, and IAB-donor-CU.](3198cdf0dbe501c46fe0e4073c7d8451_img.jpg) + +``` + +sequenceDiagram + participant IAB-node 2 + participant IAB-node 1 + participant IAB-donor-DU + participant IAB-donor-CU + + Note right of IAB-donor-CU: 1. UE CONTEXT MODIFICATION REQUEST + IAB-donor-CU->>IAB-donor-DU: 1. UE CONTEXT MODIFICATION REQUEST + Note right of IAB-donor-DU: 2. UE CONTEXT MODIFICATION RESPONSE + IAB-donor-DU-->>IAB-donor-CU: 2. UE CONTEXT MODIFICATION RESPONSE + Note right of IAB-donor-CU: 3. DL RRC MESSAGE TRANSFER (RRCReconfiguration) + IAB-donor-CU->>IAB-donor-DU: 3. DL RRC MESSAGE TRANSFER (RRCReconfiguration) + Note right of IAB-donor-DU: 4. RRCReconfiguration + IAB-donor-DU->>IAB-node 1: 4. RRCReconfiguration + Note right of IAB-node 1: 5. RRCReconfigurationComplete + IAB-node 1->>IAB-donor-DU: 5. RRCReconfigurationComplete + Note right of IAB-donor-DU: 6. UL RRC MESSAGE TRANSFER (RRCReconfigurationComplete) + IAB-donor-DU->>IAB-donor-CU: 6. UL RRC MESSAGE TRANSFER (RRCReconfigurationComplete) + Note right of IAB-donor-CU: 7. UE CONTEXT MODIFICATION REQUEST + IAB-donor-CU->>IAB-node 1: 7. UE CONTEXT MODIFICATION REQUEST + Note right of IAB-node 1: 8. UE CONTEXT MODIFICATION RESPONSE + IAB-node 1->>IAB-donor-CU: 8. UE CONTEXT MODIFICATION RESPONSE + Note right of IAB-donor-CU: 9. DL RRC MESSAGE TRANSFER (RRCReconfiguration) + IAB-donor-CU->>IAB-node 1: 9. DL RRC MESSAGE TRANSFER (RRCReconfiguration) + Note right of IAB-node 1: 10. RRCReconfiguration + IAB-node 1->>IAB-node 2: 10. RRCReconfiguration + Note right of IAB-node 2: 11. RRCReconfigurationComplete + IAB-node 2->>IAB-node 1: 11. RRCReconfigurationComplete + Note right of IAB-node 1: 12. UL RRC MESSAGE TRANSFER (RRCReconfigurationComplete) + IAB-node 1->>IAB-donor-CU: 12. UL RRC MESSAGE TRANSFER (RRCReconfigurationComplete) + +``` + +Sequence diagram showing the signalling flow for IAB BH RLC channel establishment procedure between IAB-node 2, IAB-node 1, IAB-donor-DU, and IAB-donor-CU. + +**Figure 8.9.8-1: Signalling flow for IAB BH RLC channel establishment procedure** + +1. The IAB-donor-CU sends to the IAB-donor-DU a UE CONTEXT MODIFICATION REQUEST message for setting up the parent-node IAB-DU side of the BH link between IAB-donor-DU and IAB-node 1. This step is optional and is required only when a new BH RLC channel needs to be established on the BH link between IAB-donor-DU and IAB-node 1. +2. The IAB-donor-DU sends the UE CONTEXT MODIFICATION RESPONSE message to the IAB-donor-CU. +3. The IAB-donor-CU sends to the IAB-donor-DU a DL RRC MESSAGE TRANSFER message encapsulating the *RRCReconfiguration* message for configuring the IAB-MT of IAB-node 1. This step is optional and is required only when a new BH RLC channel needs to be established on the BH link between IAB-donor-DU and IAB-node 1. +4. The IAB-donor-DU decapsulates and forwards the *RRCReconfiguration* message to the IAB-MT of IAB-node 1. This step is optional and is required only when a new BH RLC channel needs to be established on the BH link between IAB-donor-DU and IAB-node 1. +5. The IAB-MT of IAB-node 1 sends to the IAB-donor-DU an *RRCReconfigurationComplete* message destined to the IAB-donor-CU. This step is optional and is required only when a new BH RLC channel needs to be established on the BH link between IAB-donor-DU and IAB-node 1. +6. The IAB-donor-DU sends the UL RRC MESSAGE TRANSFER message encapsulating the *RRCReconfigurationComplete* message to the IAB-donor-CU. This step is optional and is required only when a new BH RLC channel needs to be established on the BH link between IAB-donor-DU and IAB-node 1. +7. The IAB-donor-CU sends to the IAB-DU of IAB-node 1 a UE CONTEXT MODIFICATION REQUEST message for setting up the parent node IAB-DU side of the BH link between IAB-node 1 and IAB-node 2. This step is optional and is required only when a new BH RLC channel needs to be established on the BH link between IAB-node 1 and IAB-node 2. +8. The IAB-node 1 sends the UE CONTEXT MODIFICATION RESPONSE message to the IAB-donor-CU. +9. The IAB-donor-CU sends to the IAB-DU of IAB-node 1 a DL RRC MESSAGE TRANSFER message encapsulating the *RRCReconfiguration* message for configuring the IAB-MT of IAB-node 2. This step is optional and is required only when a new BH RLC channel needs to be established on the BH link between IAB-node 1 and IAB-node 2. + +10. The IAB-DU of IAB-node 1 decapsulates and forwards the *RRCReconfiguration* message to the IAB-MT of IAB-node 2. This step is optional and is required only when a new BH RLC channel needs to be established on the BH link between IAB-node 1 and IAB-node 2. +11. The IAB-MT of IAB-node 2 sends to IAB-node 1 an *RRCReconfigurationComplete* message destined to the IAB-donor-CU. This step is optional and is required only when a new BH RLC channel needs to be established on the BH link between IAB-node 1 and IAB-node 2. +12. IAB-node 1 sends the UL RRC MESSAGE TRANSFER message encapsulating the *RRCReconfigurationComplete* message to the IAB-donor-CU. This step is optional and is required only when a new BH RLC channel needs to be established on the BH link between IAB-node 1 and IAB-node 2. + +The IAB-donor-CU uses the existing CU-DU split principles and the UE Context Setup procedure or UE Context Modification procedure to configure the parent IAB-DU side of the BH RLC channel. The IAB-donor-CU uses RRC signaling (which is encapsulated in the DL RRC MESSAGE TRANSFER message terminating at the parent node IAB-DU side of the BH RLC channel) to configure the child node IAB-MT side of the BH RLC channel. + +The IAB-donor-CU configures the IAB-DU with a mapping to the BH RLC channel to be used for a specific UL F1-U tunnel during the UE Context Setup procedure or the F1-AP UE Context Modification procedure for the UE. + +### 8.9.9 Traffic Mapping + +NOTE: The general principles and procedures described in this clause does not apply to ng-eNB. + +#### 8.9.9.1 Traffic Mapping from IP-layer to Layer-2 + +When forwarding IP packets, the IAB-donor-DU performs the traffic mapping from IP-layer to layer-2 as defined in TS 38.340 [22]. The traffic mapping information is configured by the IAB-donor-CU, which contains the IP header information, and the BH information including the BAP routing ID and a list of egress link and BH RLC channel pairs. + +Multiple traffic mappings can contain the same BAP routing ID and/or list of egress link and BH RLC channel pairs. + +The traffic mappings can be configured as part of the UE Context Setup or UE Context Modification procedures. They may also be configured via the non-UE-associated BAP Mapping Configuration procedure. + +NOTE: Implementation must ensure the avoidance of potential race conditions, i.e. no conflicting configurations are concurrently performed using UE-associated and non-UE-associated procedures. + +The traffic mapping from IP-layer to layer-2 may include IPv6 Flow Label information. For DL F1 or X2 traffic, the IPv6 Flow Label information is set by the IAB-donor-CU or MeNB, respectively. When this traffic is protected via IPsec tunnel mode, the IPv6 Flow Label is set on the inner header by the IAB-donor-CU or MeNB, and the security gateway shall copy the IPv6 Flow Label from the inner IP header to the outer IP header to ensure that the IAB-donor-DU can perform the traffic mapping considering the IPv6 Flow Label. + +NOTE: Implementation must ensure that IPv6 Flow Label collisions are avoided on the IP backhaul network between security gateway and IAB-donor-DU. + +#### 8.9.9.2 BH RLC Channel Mapping on BAP Layer + +When traffic is forwarded on BAP layer as described in TS 38.300 [2], the IAB-node performs the BH RLC channel mapping as defined in TS 38.340 [22]. The BH RLC channel mapping information is configured by the IAB-donor-CU. + +The BH RLC channel mappings can be configured as part of the UE Context Setup or UE Context Modification procedures. They may also be configured via the non-UE-associated BAP Configuration procedure. + +NOTE: Implementation must ensure the avoidance of potential race conditions, i.e. that no conflicting configurations are concurrently performed using UE-associated and non-UE-associated procedures. + +### 8.9.10 IAB-node release + +NOTE: The general principles and procedures described in this clause does not apply to ng-eNB. + +An IAB-node may depart the network either in an orderly fashion, which implies that both the network and the IAB-node are aware in advance, or in a disorderly fashion (e.g. due to an RLF with failed recovery). + +#### 8.9.10.1 IAB-node orderly release + +For orderly release, the IAB-donor-CU can remove the F1 interface connection to the IAB-DU without releasing the IAB-MT. If the IAB-MT needs to be released, IAB-MT will perform the deregistration procedure. If both F1 interface and IAB-MT need to be released, the IAB-donor-CU should remove the F1 interface to the IAB-DU before it releases the collocated IAB-MT. The deregistration procedure is the same as the UE deregistration procedure. The IAB-donor-CU hands over the UEs or child IAB-nodes currently connected to the IAB-node's cell(s) to another cell(s), or releases the UEs and may stop accepting incoming handovers or connections to the IAB-node that is about to be released. The IAB-donor-CU may also update/release the BH RLC channels in the intermediate hops. At this point, the F1 interface will be released and the corresponding SCTP associations will be removed. + +#### 8.9.10.2 IAB-node disorderly release + +For the disorderly release case, how to remove the IAB-node context is up to network implementation. + +### 8.9.11 IAB-node OAM + +NOTE: The general principles and procedures described in this clause does not apply to ng-eNB. + +The IAB-node receives commands, configuration data and software downloads (e.g. for equipment software upgrades) from its OAM system. The IAB-node can also send alarms and traffic counter information to its OAM system. The transport connection between the IAB-node and its OAM, using IP, is provided by the IAB-MT's PDU session via 5G network, or the IAB-MT's PDN connection via LTE network when IAB-MT uses EN-DC. + +NOTE: The transport connection between the IAB-node and its OAM may also be provided using the Backhaul IP layer by implementation. + +Alarms in the IAB generate bursts of high-priority traffic, to be transported in real time. Traffic counters generate bursts of traffic, but their transport need not be real-time. Configuration messages from OAM to the IAB will also generate small bursts of traffic, possibly with lower priority than alarms but still delay-sensitive: when a configuration is committed on the OAM, the time interval between the commitment and the effect on the equipment shall be small. Alarm messages and commands should be transported on a high-priority bearer, while counters may be transported on a lower priority bearer. + +OAM software download to the IAB may generate larger amounts of data, but both the required data rate and the priority of this kind of traffic are much lower than in the case of alarms, commands and counters. + +For different types of OAM traffic, it is necessary to use different DRBs between the IAB-MT and the serving DU, and different BH RLC channels for intermediate hops, with different QoS parameters. Aggregation of F1-U traffic for OAM with other F1-U traffic on the same BH RLC channels is not precluded. The QoS parameters are provided to the IAB-donor during the IAB-MT's PDU session establishment, or the IAB-MT's PDN connection establishment when IAB-MT uses EN-DC. + +NOTE: When the transport connection between the IAB-node and its OAM is provided by the Backhaul IP layer, the OAM traffic may be aggregated with other traffic types on the same BH RLC channel. The QoS for OAM is ensured by implementation. + +The continuity of OAM connectivity needs to be ensured as the mobile IAB-node moves across the mobile network. + +### 8.9.12 Handling of IAB-MTs in INACTIVE State + +NOTE: The general principles and procedures described in this clause does not apply to ng-eNB. + +The IAB-MT optionally supports the RRC INACTIVE state. Upon the IAB-MT entering the RRC INACTIVE state, it is up to implementation to keep or release the F1 connection of the collocated IAB-DU. + +### 8.9.13 IP Address Allocation for IAB-nodes + +NOTE: The general principles and procedures described in this clause does not apply to ng-eNB. + +An IAB-node may obtain IP address(es) either from the IAB-donor or from the OAM system. The IP address(es) is(are) used by the IAB-node for F1 and non-F1 traffic exchange via the backhaul. In case IPsec tunnel mode is used to protect + +this F1 and non-F1 traffic, the IP address(es) refer to the outer tunnel addresses. The allocation of the inner tunnel IP address(es) is outside of 3GPP scope. + +**NOTE:** The non-F1 traffic of an IAB-node includes all IP traffic that is not used for the management or transport of F1-C as specified in TS 38.472 [26] or F1-U as specified in TS 38.474 [7]. The non-F1 traffic may include, e.g., OAM traffic if it is transferred using the BH RLC channel. + +In case of IAB-donor-based IP address allocation, the IP address(es) is(are) allocated by the IAB-donor-CU or IAB-donor-DU. In both cases, the IAB-node requests the IP address(es) via RRC from the IAB-donor-CU. It includes a separate IP address request for each usage, where the usages defined are all traffic, F1-U, F1-C and non-F1. The IAB-donor-CU may initiate the IAB TNL Address Allocation procedure to obtain IP addresses from the IAB-donor-DU. The IAB-donor-CU sends the IP addresses allocated for each usage to the IAB-node via RRC. In case of IAB inter-CU topology management, the F1-terminating IAB-donor-CU may obtain the IP addresses for each usage in the non-F1-terminating IAB-donor-CU's topology from the non-F1-terminating IAB-donor-CU for the boundary IAB-node and the descendant IAB-nodes of the boundary IAB-node. + +The IAB-node may be allocated one or multiple IPv6 addresses or one 64-bit IPv6 prefix for each usage and/or one or multiple IPv4 addresses for each usage. Each allocated IP address/IPv6 prefix is unique within the IAB network and routable from the wireline network. + +In case of OAM-based IP address allocation, the IAB-node informs the IAB-donor-CU via an UL RRC message about the IP address(es) it received for each purpose. This occurs before the IAB node uses the IP address(es) for UL and/or DL traffic. + +The IAB-donor-CU configures the IAB-donor-DU with mappings between IP header fields and L2 parameters (BAP Routing ID, BH RLC channels) used for DL traffic. Each mapping configuration may hold an IPv4 address, IPv6 address or a 64-bit IPv6 prefix. In case of two mapping entries matching the same IP header where one holds an IPv6 prefix and the other holds a full IPv6 address, the one with full IPv6 address takes precedence at the IAB-donor-DU. + +In case of IAB-donor-allocated IP addresses, the IAB-node's IP address(es) can be updated using DL RRC signalling. + +For F1-C traffic transfer for NSA IAB, the LTE leg and NR leg should use separate IP address pairs {IAB-DU's IP address, IAB-donor-CU's IP address}. How the IAB-DU gets the remote IP end point(s) and its own IP address for LTE leg is not specified in this release. + +### 8.9.14 Mobile IAB-node authorization + +During the mobile IAB-node integration procedure, the RRC-terminating IAB-donor-CU receives the authorization status of the mobile IAB-node from the 5GC. If the authorization status is "not authorized", the RRC-terminating IAB-donor-CU will neither establish any backhaul resources nor allocate any BAP address, TNL address or default BAP configuration for this mobile IAB-node. If the authorization status for the mobile IAB-node changes, the 5GC sends an updated authorization status to the RRC-terminating IAB-donor-CU. + +In case the mobile IAB-MT and its co-located mobile IAB-DU connect to same IAB-donor-CU, and the updated authorization status received from the 5GC is "not authorized", the IAB-donor-CU will perform the following actions in this order: it will attempt to hand over the UEs served by the mobile IAB-node to other cell(s), release the F1 interface towards the mobile IAB-DU, and release all backhaul resources (including the BAP address, TNL address and default BAP reconfiguration) for this mobile IAB-node. + +In case the mobile IAB-MT and its co-located mobile IAB-DU connect to different IAB-donor-CUs, the RRC-terminating IAB-donor sends the updated authorization status to the F1-terminating IAB-donor-CU via the IAB TRANSPORT MIGRATION MODIFICATION REQUEST message. The F1-terminating IAB-donor-CU confirms the reception of the updated authorization status via the IAB TRANSPORT MIGRATION MODIFICATION RESPONSE message. + +**NOTE:** In absence of Xn connectivity between the RRC-terminating IAB-donor-CU and the F1-terminating IAB-donor-CU, the passing of the authorization status is left up to implementation. + +If the updated authorization status for the mobile IAB-node is "not authorized", the F1-terminating IAB-donor, attempts to hand over the UEs served by the mobile IAB-node to other cell(s), and then releases the F1 interface towards the mobile IAB-DU. After that, the F1-terminating IAB-donor requests from the RRC-terminating IAB-donor the release of all the offloaded traffic via the IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message. The RRC-terminating IAB-donor releases the offloaded traffic and all backhaul resources (including BAP address, TNL address + +and default BAP reconfiguration) for this mobile IAB-node. The RRC-terminating IAB-donor may send an indication which indicates that the mobile IAB-MT can be deregistered, to AMF. + +If the authorization status is changed back from “not authorized” to “authorized”, the phase 2 and phase 3 of the mobile IAB-node integration procedure as defined in clause 8.12.3 are carried out. + +### 8.9.15 IAB-donor-CU-based NR Cell Identity (NCI) (re-)configuration for mobile IAB cells + +The NCIs of the cells served by a mobile IAB-DU configured by the OAM can be reconfigured by the F1-terminating IAB-donor-CU serving the mobile IAB-DU, in case of an NCI collision with cells of other gNB-DUs served by the IAB-donor-CU. The reconfiguration of NCI pertains to the reconfiguration of the cellLocalId part of the NCI, where the new cellLocalId(s) are based on a list of NCIs that has been configured on this F1-terminating IAB-donor-CU. + +The value change of cellLocalId(s) shall be indicated to the OAM system of the mobile IAB-DU following the NCI reconfiguration. The mobile IAB-DU can notify OAM about the reconfigured cellLocalId(s) using notifications specified in TS 28.532 [33]. + +NOTE: This shall not affect the existing procedure of configuring NCGI of cells served by a stationary gNB-DU via the OAM. + +### 8.9.16 TAC/RANAC (re-)configuration for mobile IAB + +The TAC/RANAC of mobile IAB-DU's cell is configured by the OAM, and it can be reconfigured by the OAM during the mobile IAB-node movement. The TAC/RANAC of the mobile IAB-DU's cell need not be same as the TAC/RANAC of the co-located mobile IAB-MT's serving cell. The TAC/RANAC broadcasted by the mobile IAB-DU cell can be changed in order to reflect the mobile IAB-node's physical location. + +## 8.10 Multiple TNLA for E1 + +NOTE: The general principles and procedures described in this clause also apply to ng-eNB and W1/E1 interface, i.e. W1 interface between ng-eNB-DU and ng-eNB-CU-CP/ng-eNB-CU-UP, E1 interface between ng-eNB-CU-CP and ng-eNB-CU-UP, if not explicitly specified otherwise. + +In the following, the procedure for managing multiple TNLA for E1 is described. + +![Sequence diagram illustrating the management of multiple TNLAs for E1 between gNB-CU-UP and gNB-CU-CP. The diagram shows two main paths: (A) initiated by gNB-CU-UP and (B) initiated by gNB-CU-CP. Both paths involve TNLA establishment, E1 Setup, and Configuration Update/ACK messages.](4806f9f95fff13a30d6523bd6ffeac63_img.jpg) + +``` + +sequenceDiagram + participant gNB-CU-UP + participant gNB-CU-CP + + Note left of gNB-CU-UP: (A) gNB-CU-UP initiated + gNB-CU-UP->>gNB-CU-CP: 1. TNLA establishment (TNLA1) + gNB-CU-UP->>gNB-CU-CP: 2. GNB-CU-UP E1 SETUP REQUEST + gNB-CU-CP-->>gNB-CU-UP: 3. GNB-CU-UP E1 SETUP RESPONSE + + Note left of gNB-CU-CP: (B) gNB-CU-CP initiated + gNB-CU-CP->>gNB-CU-UP: 2. GNB-CU-CP E1 SETUP REQUEST + gNB-CU-UP-->>gNB-CU-CP: 3. GNB-CU-CP E1 SETUP RESPONSE + + gNB-CU-CP->>gNB-CU-UP: 4. GNB-CU-CP CONFIGURATION UPDATE + + Note left of gNB-CU-UP: Additional TNLA establishment + gNB-CU-UP->>gNB-CU-CP: 5. TNLA establishment (TNLA2) + gNB-CU-CP-->>gNB-CU-UP: 6. GNB-CU-CP CONFIGURATION UPDATE ACK + + gNB-CU-UP->>gNB-CU-CP: 7. TNLA establishment (TNLA3) + gNB-CU-UP->>gNB-CU-CP: 8. GNB-CU-UP CONFIGURATION UPDATE + gNB-CU-CP-->>gNB-CU-UP: 9. GNB-CU-UP CONFIGURATION UPDATE ACK + +``` + +Sequence diagram illustrating the management of multiple TNLAs for E1 between gNB-CU-UP and gNB-CU-CP. The diagram shows two main paths: (A) initiated by gNB-CU-UP and (B) initiated by gNB-CU-CP. Both paths involve TNLA establishment, E1 Setup, and Configuration Update/ACK messages. + +**Figure 8.10-1: Managing multiple TNLAs for E1.** + +- Either the gNB-CU-CP or gNB-CU-UP establishes the first SCTP association with the gNB-CU-UP or gNB-CU-CP respectively using a configured TNL address. + +NOTE: The gNB-CU-UP/gNB-CU-CP may use different source and/or destination IP end point(s) if the TNL establishment towards one IP end point fails. How the gNB-CU-UP/gNB-CU-CP gets the remote IP end point(s) and its own IP address are outside the scope of this specification. + +- (A). Once the TNLA (gNB-CU-UP initiated) has been established, the gNB-CU-UP initiates the E1 Setup procedure to exchange application level configuration data. + +- (B). Once the TNLA (gNB-CU-CP initiated) has been established, the gNB-CU-CP initiates the E1 Setup procedure to exchange application level configuration data. + +- The gNB-CU-CP may add additional SCTP Endpoint(s) to be used for E1 signalling between the gNB-CU-CP and the gNB-CU-UP pair using the gNB-CU-CP Configuration Update procedure. The gNB-CU-CP Configuration Update procedure also allows the gNB-CU-CP to request the gNB-CU-UP to modify or release TNLA(s). + +- The gNB-CU-UP may add additional TNL association(s) to be used for E1 signalling using a gNB-CU-CP endpoint already in use for existing TNL associations between the gNB-CU-CP and the gNB-CU-UP pair. The gNB-CU-UP CONFIGURATION UPDATE message including the gNB-CU-UP ID shall be the first E1AP message sent on an additional TNLA of an already setup E1 interface instance after the TNL association has become operational. The E1AP UE TNLA binding is a binding between a E1AP UE association and a specific TNL association for a given UE. After the E1AP UE TNLA binding is created, the gNB-CU-CP can update the UE TNLA binding by sending the E1AP message for the UE to the gNB-CU-UP via a different TNLA. The gNB-CU-UP shall update the E1AP UE TNLA binding with the new TNLA. The gNB-CU-UP Configuration Update procedure also allows the gNB-CU-UP to inform the gNB-CU-CP that the indicated TNLA(s) will be removed by the gNB-CU-UP. + +## 8.11 Support of Network Sharing with multiple cell-ID broadcast + +### 8.11.1 General + +This clause describes necessary additions as compared to the case where network sharing with multiple cell-ID broadcast is not applied. + +The signalling flows in the subsequent clauses assuming 2 sharing operators, A and B. The F1-C signalling transport deployment used is indicated within the subsequent clauses. + +### 8.11.2 Initial Registration – separate PLMN signalling + +The signalling flow for Initial Registration for network sharing with multiple cell-ID broadcast with separate per-PLMN signalling is shown in Figure 8.11.2-1. + +In this example message flow + +- the UE is assumed to not provide an ue-Identity from which the DU is able to deduce the PLMN ID. +- each F1-C interface instance uses a separate signalling transport or share signalling transport with other F1-C interface instances. +- the gNB-DUA/B entity shown in Figure 8.11.2-1 is a simplified representation of the gNB-DUA of PLMN A, the gNB DUB of PLMN B and respective radio resources of the shared cell. + +![Sequence diagram of UE Initial Access procedure and network sharing with multiple cell-ID broadcast. The diagram shows interactions between UE, gNB-DU_A/B, gNB-CU_A, and gNB-CU_B. Steps 1-5 are RRC Setup. Step 6 is UE CONTEXT RELEASE REQUEST from gNB-DU_A/B to gNB-CU_A with cause 'PLMN not served by the CU'. Step 7 is INITIAL UL RRC MESSAGE TRANSFER from gNB-DU_A/B to gNB-CU_B. Step 8 is UE CONTEXT RELEASE COMMAND from gNB-CU_A to gNB-DU_A/B. Step 9 is UE CONTEXT RELEASE COMPLETE from gNB-DU_A/B to gNB-CU_A. A note indicates that after step 5, the DU interprets the RRCSetupComplete message and becomes aware that PLMN(B) is not being served by CU_A.](e6d2a5fe2df965cbe598f8ea80fbb7d6_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB-DU_A/B + participant gNB-CU_A + participant gNB-CU_B + + Note right of gNB-DU_A/B: DU interprets RRCSetupComplete message, i.e it is aware of PLMN(B) not being served by CU_A + + UE->>gNB-DU_A/B: 1. RRCSetupRequest + gNB-DU_A/B->>gNB-CU_A: 2. INITIAL UL RRC MESSAGE TRANSFER +(gNB-DU UE F1AP, NR CGI_A, C-RNTI, RRC-container, ...) + gNB-CU_A->>gNB-DU_A/B: 3. DL RRC MESSAGE TRANSFER +(gNB-CU/DU UE F1AP, SRB ID, RRC-container, ...) + gNB-DU_A/B->>UE: 4. RRCSetup + UE->>gNB-DU_A/B: 5. RRCSetupComplete + gNB-DU_A/B->>gNB-CU_A: 6. UE CONTEXT RELEASE REQUEST +(gNB-CU/DU UE F1AP, cause = "PLMN not served by the CU") + gNB-DU_A/B->>gNB-CU_B: 7. INITIAL UL RRC MESSAGE TRANSFER +(gNB-DU UE F1AP, NR CGI_B, C-RNTI (the very same as in step 2), +RRC-container = RRCSetupRequest (as received in step 1), +RRC-container = RRCSetupComplete (as received in step 5) ... ) + gNB-CU_A->>gNB-DU_A/B: 8. UE CONTEXT RELEASE COMMAND +(gNB-CU/DU UE F1AP) + gNB-DU_A/B->>gNB-CU_A: 9. UE CONTEXT RELEASE COMPLETE +(gNB-CU/DU UE F1AP) + +``` + +Sequence diagram of UE Initial Access procedure and network sharing with multiple cell-ID broadcast. The diagram shows interactions between UE, gNB-DU\_A/B, gNB-CU\_A, and gNB-CU\_B. Steps 1-5 are RRC Setup. Step 6 is UE CONTEXT RELEASE REQUEST from gNB-DU\_A/B to gNB-CU\_A with cause 'PLMN not served by the CU'. Step 7 is INITIAL UL RRC MESSAGE TRANSFER from gNB-DU\_A/B to gNB-CU\_B. Step 8 is UE CONTEXT RELEASE COMMAND from gNB-CU\_A to gNB-DU\_A/B. Step 9 is UE CONTEXT RELEASE COMPLETE from gNB-DU\_A/B to gNB-CU\_A. A note indicates that after step 5, the DU interprets the RRCSetupComplete message and becomes aware that PLMN(B) is not being served by CU\_A. + +**Figure 8.11.2-1: UE Initial Access procedure and network sharing with multiple cell-ID broadcast** + +NOTE: Steps 1-5 are defined in clause 8.1. Note, that the selectedPLMN-Identity is provided in step 5. + +6. The gNB-DUA sends the F1AP UE CONTEXT RELEASE REQUEST message to the gNB-CUA, including a Cause set to "PLMN not served by the CU". + +7. The gNB-DUB sends the FIAP INITIAL UL RRC MESSAGE to the gNB-CUB, including the NR CGI associated with PLMNB, the C-RNTI indicated by the gNB-DUA at step 2, and the RRC-Container IE and the *RRC-Container-RRCSetupComplete* IE with the RRC message received in step 1 and step 5 respectively. The *RRC-Container-RRCSetupComplete* IE are included in the INITIAL UL RRC MESSAGE TRANSFER for the case of network sharing and shall contain the RRC messages received via the RRC *UL-DCCH-Message* IE from the UE, but never previously sent to the gNB-CUB. +8. The gNB-CUA sends the UE CONTEXT RELEASE COMMAND message to the gNB-DU. +9. The gNB-DU sends the UE CONTEXT RELEASE COMPLETE message to the gNB-CUA. + +NOTE: Initiating procedures from gNB-DUA towards gNB-CUA and from gNB-DUB to gNB-CUB in parallel is not precluded. + +### 8.11.3 RRC Connection Reestablishment – separate PLMN signalling + +The signalling flow for RRC Connection Reestablishment for network sharing with multiple cell-ID broadcast with separate per-PLMN signalling is shown in Figure 8.11.3-1. + +In this example message flow + +- each F1-C/Xn-C interface instance uses either a separate signalling transport or a share signalling transport with other interface instances. +- the New gNB-DUA/B entity shown in Figure 8.11.3-1 is a simplified representation of the New gNB-DUA of PLMN A, the New gNB DUB of PLMN B and respective radio resources of the shared cell. + +![Sequence diagram for RRC Connection Reestablishment with multiple cell-ID broadcast. Lifelines: UE, New gNB-DU A/B, New gNB-CU A, New gNB-CU B, Old gNB A, Old gNB B. The process involves RRCReestablishmentRequest from UE, INITIAL UL RRC MESSAGE TRANSFER to New gNB-CU A, RETRIEVE UE CONTEXT REQUEST to Old gNB A, RETRIEVE UE CONTEXT FAILURE from Old gNB A, DL RRC MESSAGE TRANSFER to New gNB-DU A/B, INITIAL UL RRC MESSAGE TRANSFER to New gNB-CU B, RETRIEVE UE CONTEXT REQUEST to Old gNB B, RETRIEVE UE CONTEXT RESPONSE from Old gNB B, DL RRC MESSAGE TRANSFER to New gNB-DU A/B, RRCReestablishment to UE, RRCReestablishmentComplete from UE, and UL RRC MESSAGE TRANSFER to New gNB-CU B. A note indicates steps 2A and 2B could be parallel.](a760132c773ae85ff8cedb26b500f223_img.jpg) + +``` + +sequenceDiagram + participant UE + participant New gNB-DU A/B + participant New gNB-CU A + participant New gNB-CU B + participant Old gNB A + participant Old gNB B + + Note right of New gNB-DU A/B: Note, that 2A and 2B could be issued in parallel + + UE->>New gNB-DU A/B: 1. RRCReestablishmentRequest + New gNB-DU A/B->>New gNB-CU A: 2A. INITIAL UL RRC MESSAGE TRANSFER +(gNB-DU UE F1AP, NR CGI, C-RNTI, RRC-container,...) + New gNB-CU A->>Old gNB A: 3A. RETRIEVE UE CONTEXT REQUEST +(New UE XnAP ID, C-RNTI, MAC-I, New cell ID, ReestCause) + Old gNB A-->>New gNB-CU A: 4A. RETRIEVE UE CONTEXT FAILURE +(New/Old UE XnAP ID, Cause) + New gNB-CU A->>New gNB-DU A/B: 5A. DL RRC MESSAGE TRANSFER +(gNB-CU/DU UE F1AP, SRB ID, RRC-container = RRCSsetup +Indication that UE context was not found. +RRC container(as received in step1)) + New gNB-DU A/B->>New gNB-CU B: 2B. INITIAL UL RRC MESSAGE TRANSFER +(gNB-DU UE F1AP, NR CGI, C-RNTI, RRC-container,...) + New gNB-CU B->>Old gNB B: 3B. RETRIEVE UE CONTEXT REQUEST +(New UE XnAP ID, C-RNTI, MAC-I, New cell ID, ReestCause) + Old gNB B-->>New gNB-CU B: 4B. RETRIEVE UE CONTEXT RESPONSE +(New/Old UE XnAP ID, UE context ... ) + New gNB-CU B->>New gNB-DU A/B: 5B. DL RRC MESSAGE TRANSFER +(gNB-CU/DU UE F1AP, SRB ID +RRC-container = RRCReestablishment) + New gNB-DU A/B->>UE: 6. RRCReestablishment + UE->>New gNB-DU A/B: 7. RRCReestablishmentComplete + New gNB-DU A/B->>New gNB-CU B: 8. UL RRC MESSAGE TRANSFER +(gNB-CU/DU UE F1AP, SRB ID, RRC-container) + +``` + +Sequence diagram for RRC Connection Reestablishment with multiple cell-ID broadcast. Lifelines: UE, New gNB-DU A/B, New gNB-CU A, New gNB-CU B, Old gNB A, Old gNB B. The process involves RRCReestablishmentRequest from UE, INITIAL UL RRC MESSAGE TRANSFER to New gNB-CU A, RETRIEVE UE CONTEXT REQUEST to Old gNB A, RETRIEVE UE CONTEXT FAILURE from Old gNB A, DL RRC MESSAGE TRANSFER to New gNB-DU A/B, INITIAL UL RRC MESSAGE TRANSFER to New gNB-CU B, RETRIEVE UE CONTEXT REQUEST to Old gNB B, RETRIEVE UE CONTEXT RESPONSE from Old gNB B, DL RRC MESSAGE TRANSFER to New gNB-DU A/B, RRCReestablishment to UE, RRCReestablishmentComplete from UE, and UL RRC MESSAGE TRANSFER to New gNB-CU B. A note indicates steps 2A and 2B could be parallel. + +**Figure 8.11.3-1: RRC Connection Reestablishment and network sharing with multiple cell-ID broadcast** + +1. The UE sends the RRCReestablishmentRequest. +- 2A-5A. Depicts the case where the UE context could not be retrieved by the new gNB-CUA. In step 2A, the NR CGI associated to PLMNA is indicated. In step 5A, the gNB-CUA would prepare the possibility to revert back to + +normal RRC Connection Establishment, indicating that the UE Context was not retrievable and may include the re-directed RRC message as received in step 1. After step 5A, the gNB-DUA may redirect the UE towards the PLMN indicated in DL RRC MESSAGE TRANSFER message, if the PLMN assistance information is provided by the gNB-CUA. If the New gNB-DUA/B was not able to deduce the RRC message from step 1, this indicator triggers step 2B. The New gNB-DUA is supposed to trigger the release the UE-associated signalling connection (not shown). + +2B-5B. Depicts the case where the UE context was retrievable by the New gNB-CUB. In step 2B, the NR CGI associated to PLMNB is indicated. Step 2B also includes the C-RNTI allocated at reception of step 1. + +6-8. The RRC Connection Reestablishment continues with the New gNB-CUB. + +NOTE: If all gNB-CUs indicate that the UE context is not retrievable, the RRC connection reestablishment falls back to RRC Connection setup, as described in clause 8.11.2. + +NOTE: Initiating procedures from gNB-DUA towards gNB-CUA and from gNB-DUB to gNB-CUB in parallel is not precluded. + +### 8.11.4 Support of shared signalling transport + +This clause specifies for F1-C, Xn-C and, in case of EN-DC, for X2-C, how an interface instance is identified in case of network sharing with multiple cell ID broadcast with shared signalling transport. + +For UE associated signalling, the interface instance is identified by assigning on F1-C appropriate UE F1AP IDs, on Xn-C appropriate UE XnAP IDs and on X2-C appropriate UE X2AP IDs. + +For non-UE associated signalling, the interface instance is identified on F1-C by the assigning an appropriate value to the Transaction ID, on Xn-C and X2-C by including the Interface Instance Indication in the respective message and assigning an appropriate value to it. + +## 8.12 IAB-node Integration Procedure + +### 8.12.1 Standalone IAB integration + +A high-level flow chart for SA-based IAB integration is shown in the Figure 8.12.1-1: + +![Figure 8.12.1-1: The integration procedure for IAB-node in SA. The diagram shows a sequence of phases for IAB-node integration. At the top, five entities are shown: IAB-node 2, IAB-node 1, IAB-donor (containing IAB-donor-DU and IAB-donor-CU), and 5GC(for IAB). Vertical lines connect these entities to a series of horizontal bars representing phases. Phase 1: IAB-MT setup involves IAB-node 2, IAB-node 1, and IAB-donor. Phase 2-1: BH RLC channel establishment involves IAB-node 1, IAB-donor, and 5GC(for IAB). Phase 2-2: Routing update involves IAB-node 1, IAB-donor, and 5GC(for IAB). Phase 3: IAB-DU setup involves IAB-node 1, IAB-donor, and 5GC(for IAB).](d0438bd44baf768f9c42bb4ff4431849_img.jpg) + +Figure 8.12.1-1: The integration procedure for IAB-node in SA. The diagram shows a sequence of phases for IAB-node integration. At the top, five entities are shown: IAB-node 2, IAB-node 1, IAB-donor (containing IAB-donor-DU and IAB-donor-CU), and 5GC(for IAB). Vertical lines connect these entities to a series of horizontal bars representing phases. Phase 1: IAB-MT setup involves IAB-node 2, IAB-node 1, and IAB-donor. Phase 2-1: BH RLC channel establishment involves IAB-node 1, IAB-donor, and 5GC(for IAB). Phase 2-2: Routing update involves IAB-node 1, IAB-donor, and 5GC(for IAB). Phase 3: IAB-DU setup involves IAB-node 1, IAB-donor, and 5GC(for IAB). + +**Figure 8.12.1-1: The integration procedure for IAB-node in SA** + +Phase 1: IAB-MT setup. In this phase, the IAB-MT of the new IAB-node (e.g. IAB-node 2 in Figure 8.12.1-1) connects to the network in the same way as a UE, by performing RRC connection setup procedure with IAB-donor-CU, authentication with the core network, IAB-node 2-related context management, IAB-node 2's access traffic-related radio bearer configuration at the RAN side (SRBs and optionally DRBs), and, optionally, OAM + +connectivity establishment by using the IAB-MT's PDU session. The IAB-node can select the parent node for access based on an over-the-air indication from potential parent node IAB-DU (transmitted in SIB1). To indicate its IAB capability, the IAB-MT includes the IAB-node indication in *RRCSetupComplete* message, to assist the IAB-donor to select an AMF supporting IAB. + +NOTE: The signalling flow for UE initial access procedure as shown in Figure 8.1-1/Figure 8.9.1-1 is used for the setup of the IAB-MT. + +Phase 2-1: BH RLC channel establishment. During the bootstrapping procedure, one default BH RLC channel for non-UP traffic e.g. carrying F1-C traffic/non-F1 traffic to and from the IAB-node 2 in the integration phase, is established. This may require the setup of a new BH RLC channel or modification of an existing BH RLC channel between IAB-node 1 and IAB-donor-DU. The IAB-donor-CU may establish additional (non-default) BH RLC channels. This phase also includes configuring the BAP Address of the IAB-node 2 and default BAP Routing ID for the upstream direction. + +NOTE: If the OAM connectivity is supported via backhaul IP layer by implementation, one or more BH RLC channels used for OAM traffic can also be established. + +Phase 2-2: Routing update. In this phase, the BAP sublayer is updated to support routing between the new IAB-node 2 and the IAB-donor-DU. For the downstream direction, the IAB-donor-CU initiates F1AP procedure to configure the IAB-donor-DU with the mapping from IP header field(s) to the BAP Routing ID related to IAB-node 2. The routing tables are updated on all ancestor IAB-nodes (e.g. IAB-node 1 in Figure 8.12.1-1) and on the IAB-donor-DU, with routing entries for the new BAP Routing ID(s). This phase may also include the IP address allocation procedure for IAB-node 2. IAB-node 2 may request one or more IP addresses from the IAB-donor-CU via RRC. The IAB-donor-CU may send the IP address(es) to the IAB-node 2 via RRC. The IAB-donor-CU may obtain the IP address(es) from the IAB-donor-DU via F1-AP or by other means (e.g. OAM, DHCP). IP address allocation procedure may occur at any time after RRC connection has been established. + +Phase 3: IAB-DU part setup. In this phase, the IAB-DU of IAB-node 2 is configured via OAM. The IAB-DU of IAB-node 2 initiates the TNL establishment, and F1 setup (as defined in clause 8.5) with the IAB-donor-CU using the allocated IP address(es). The IAB-donor-CU discovers collocation of IAB-MT and IAB-DU from the IAB-node's BAP Address included in the F1 SETUP REQUEST message. After the F1 is set up, the IAB-node 2 can start serving the UEs. + +NOTE: The IAB-DU can discover the IAB-donor-CU's IP address in the same manner as a non-IAB gNB-DU. + +NOTE: If the IAB-node establishes NR-DC before the establishment of F1-C connection, the MN decides whether the MN or the SN becomes the F1-terminating IAB-donor. In case it decides that the SN becomes the F1-terminating IAB-donor, it notifies the SN via Xn. The IAB-node can implicitly derive whether the MN or the SN is the F1-terminating IAB-donor, e.g., based on the entity which provides the default BAP configuration. + +NOTE: For OAM-based IAB-donor selection, if the IAB-node establishes NR-DC before the establishment of F1-C connection, the IAB-node indicates the F1-terminating IAB-donor by signaling its IP address(es) to this IAB-donor via RRC signaling. + +### 8.12.2 NSA IAB Integration procedure + +The IAB integration procedure for NSA is shown in Figure 8.12.2-1. + +![Figure 8.12.2-1: Signalling flow for IAB integration procedure in NSA. The diagram shows a sequence of phases between an IAB-node (containing IAB-DU and IAB-MT), an eNB, and an IAB-donor (containing IAB-donor-DU and IAB-donor-CU).](750b1652a4f4791b84c02aa755a1dedd_img.jpg) + +``` + +sequenceDiagram + participant IAB-DU as IAB-DU + participant IAB-MT as IAB-MT + participant eNB as eNB + participant IAB-donor-DU as IAB-donor-DU + participant IAB-donor-CU as IAB-donor-CU + + Note right of IAB-MT: Phase 1-1: IAB-MT setup with E-UTRAN + IAB-MT->>eNB: + Note right of IAB-MT: Phase 1-2: SgNB addition + IAB-MT->>eNB: + Note right of IAB-MT: Phase 2-1: BH RLC channel establishment + IAB-MT->>eNB: + Note right of IAB-MT: Phase 2-2: Routing update + IAB-MT->>eNB: + Note right of IAB-MT: Phase 3: IAB-DU setup + IAB-MT->>eNB: + +``` + +Figure 8.12.2-1: Signalling flow for IAB integration procedure in NSA. The diagram shows a sequence of phases between an IAB-node (containing IAB-DU and IAB-MT), an eNB, and an IAB-donor (containing IAB-donor-DU and IAB-donor-CU). + +**Figure 8.12.2-1: Signalling flow for IAB integration procedure in NSA** + +Phase 1-1. IAB-MT part setup with E-UTRAN. In this phase, the IAB-MT part connects to the LTE network as a UE, by performing RRC connection setup procedure with an eNB, authentication with the EPC, IAB-node's access traffic-related radio bearer configuration at the E-UTRAN side, and optionally, OAM connectivity establishment by using the IAB-MT's PDN connection. The IAB-node can select the IAB-supporting eNB based on an over-the-air indication from eNB (transmitted in SIB1). To indicate its IAB capability, the IAB-MT includes the IAB-node indication in *RRConnectionSetupComplete* message, to assist the eNB to select an MME supporting IAB. The eNB then configures the IAB-MT part with an NR measurement configuration in order to perform discovery, measurement and measurement reporting of candidate gNBs. To enable the eNB choose an en-gNB which supports IAB function, the IAB capability of neighbour gNBs can be pre-configured in the eNB (e.g. by OAM). + +NOTE: Other ways to enable the eNB know the IAB capability of neighbour gNBs are not precluded. + +Phase 1-2. SgNB addition. In this phase, the IAB-MT part connects to the parent node IAB-DU and IAB-donor-CU via the EN-DC SgNB Addition procedure. The procedure defined in clause 8.4.1 is reused. The eNB includes "*IAB Node Indication*" in SgNB ADDITION REQUEST message to inform the IAB-donor-CU that the request is for an IAB-node. In addition, SRB3 can be set up for the IAB-MT, to transmit RRC message between the IAB-MT and the IAB-donor-CU via the NR links directly. + +Phase 2-1: BH RLC channel establishment. This phase is the same as Phase 2-1 in the standalone IAB integration procedure (refer to the Phase 2-1 in clause 8.12.1). This step may occur in Phase 1-2. + +Phase 2-2: Routing update. This phase is the same as Phase 2-2 in the standalone IAB integration procedure (refer to the Phase 2-2 in clause 8.12.1), except that the IP traffic on the F1-C interface may be transmitted via the MeNB. + +Phase 3. IAB-DU part setup. This phase is the same as Phase 3 in the standalone IAB integration procedure (refer to the Phase 3 in clause 8.12.1), except that the IP traffic on the F1-C interface may be transmitted via the MeNB. + +The IAB-donor-CU decides to only configure LTE leg, or only to configure NR leg, or to configure both LTE leg and NR leg, to be used for F1-C traffic transfer. The configuration may be performed before IAB-DU part setup. IAB-donor-CU may also change the configuration after IAB-DU part setup. In case the configuration is not performed before IAB-DU part setup, the IAB node uses the NR leg as the default one. When both LTE leg and NR leg are configured, it is up to the implementation to select the leg for F1-C traffic transfer. + +### 8.12.3 Mobile IAB-node integration + +During the integration, the mobile IAB-MT and the mobile IAB-DU can connect to the same IAB-donor or to different IAB-donors. The procedure for the latter case is shown in Figure 8.12.3-1. + +![Sequence diagram of the decoupled mobile IAB-node integration procedure. The diagram shows interactions between F1-terminating IAB-donor-CU, mobile IAB-node, intermediate IAB-node 1, RRC-terminating IAB-donor (containing IAB-donor-DU and IAB-donor-CU), and 5GC(for mobile IAB). The procedure consists of four phases: Phase 1: Mobile IAB-MT setup; Phase 2-1: BH RLC channel establishment; Phase 2-2: Routing update; and Phase 3: Mobile IAB-DU setup.](f61d0925551545b5938b3a4d1bbf63c3_img.jpg) + +Sequence diagram of the decoupled mobile IAB-node integration procedure. The diagram shows interactions between F1-terminating IAB-donor-CU, mobile IAB-node, intermediate IAB-node 1, RRC-terminating IAB-donor (containing IAB-donor-DU and IAB-donor-CU), and 5GC(for mobile IAB). The procedure consists of four phases: Phase 1: Mobile IAB-MT setup; Phase 2-1: BH RLC channel establishment; Phase 2-2: Routing update; and Phase 3: Mobile IAB-DU setup. + +**Figure 8.12.3-1: Decoupled mobile IAB-node integration procedure** + +Phase 1: Equivalent procedure to Phase 1 of the IAB-node integration in SA mode in clause 8.12.1, where the mobile IAB-node and the RRC-terminating IAB-donor correspond to IAB-node 2 and the IAB-donor, respectively. The mobile IAB-node selects the parent node based on a mobile-IAB-specific over-the-air indication (transmitted in SIB1). The mobile IAB-MT includes a mobile-IAB-node-specific indication in the *RRCSetupComplete* message to assist the RRC-terminating IAB-donor in selecting an AMF supporting mobile IAB. + +Phase 2-1: Same as Phase 2-1 of procedure in clause 8.12.1. + +Phase 2-2: Same as Phase 2-2 of procedure in clause 8.12.1. + +Phase 3: Mobile IAB-DU part setup. In this phase, the mobile IAB-DU is configured via OAM. The configured information includes, e.g., the information of the F1-terminating IAB-donor-CU, to enable the mobile IAB-DU to initiate the establishment of F1-C to the F1-terminating IAB-donor-CU. The mobile IAB-DU initiates the TNL establishment, and F1 setup (as defined in clause 8.5) with the F1-terminating IAB-donor-CU using the default BAP routing ID and default BH RLC channel configured by the RRC-terminating IAB-donor-CU in Phase 2-1 for upstream traffic. During the F1 setup, the mobile IAB-DU includes the gNB ID of the RRC-terminating IAB-donor-CU and the BAP address of the co-located mobile IAB-MT in the F1 SETUP REQUEST message. The mobile IAB-node determines this gNB ID based on the over-the-air broadcast (SIB1) by the RRC-terminating IAB-donor. + +After the F1 is set up, the mobile IAB-node can start serving UEs. The F1-terminating IAB-donor-CU can initiate the IAB Transport Migration Management procedure towards the RRC-terminating IAB-donor-CU as defined in clause 8.17.3.1. + +## 8.13 Overall procedures for MDT + +### 8.13.0 General + +The following clauses describe the overall procedures for MDT (TS 37.320 [31]) involving E1 and F1. + +### 8.13.1 Signalling based MDT activation + +The signalling flow for Signalling based MDT activation involving E1 and F1 is shown in Figure 8.13.1-1. + +![Sequence diagram for Signalling based MDT Activation. The diagram shows four lifelines: gNB-DU, gNB-CU-CP, gNB-CU-UP, and AMF. The sequence of messages is: 1. AMF sends '1 TRACE START' to gNB-CU-CP. 2. gNB-CU-CP sends '2 TRACE START' to gNB-CU-UP. 3. gNB-CU-CP sends '3 TRACE START' to gNB-DU. A decision box between steps 1 and 2 indicates 'if the MDT measurement is performed in CU-UP and/or DU'.](3750b0149a6380885998ab3ca6a8787c_img.jpg) + +``` + +sequenceDiagram + participant AMF + participant gNB-CU-UP + participant gNB-CU-CP + participant gNB-DU + Note right of gNB-CU-CP: if the MDT measurement is performed in CU-UP and/or DU + AMF->>gNB-CU-CP: 1 TRACE START + gNB-CU-CP->>gNB-CU-UP: 2 TRACE START + gNB-CU-CP->>gNB-DU: 3 TRACE START + +``` + +Sequence diagram for Signalling based MDT Activation. The diagram shows four lifelines: gNB-DU, gNB-CU-CP, gNB-CU-UP, and AMF. The sequence of messages is: 1. AMF sends '1 TRACE START' to gNB-CU-CP. 2. gNB-CU-CP sends '2 TRACE START' to gNB-CU-UP. 3. gNB-CU-CP sends '3 TRACE START' to gNB-DU. A decision box between steps 1 and 2 indicates 'if the MDT measurement is performed in CU-UP and/or DU'. + +**Figure 8.13.1-1 Signalling based MDT Activation** + +1. The AMF starts a trace session and sends a TRACE START message to the gNB. The AMF shall consider the MDT user consent information when activating an MDT trace session for the UE as defined in TS 32.422 [20]. TRACE START message includes the parameters for configuring MDT measurements. +2. The gNB-CU-CP decides if the gNB-CU-UP, or the gNB-DU, or both, should be involved in the MDT measurement. If the gNB-CU-UP should be involved in the MDT measurement, the gNB-CU-CP sends TRACE START message to the gNB-CU-UP, including MDT configuration parameters. +3. If the gNB-DU should be involved in the MDT measurement, the gNB-CU-CP sends TRACE START message to the gNB-DU, including MDT configuration parameters. + +### 8.13.2 Management based MDT activation + +#### 8.13.2.1 General + +In Management Based Trace Activation towards a gNB-CU-CP, gNB-CU-UP or a gNB-DU can be fulfilled with the Cell Traffic trace functionality defined in TS 32.422 [20]. The configuration parameters of the Trace Session that are received by a node in split RAN architecture are defined in TS 32.422 [20]. + +The following description is valid for both an en-gNB and a gNB. + +If the MDT measurement is initiated by the EM towards the gNB-CU-CP, and if the activation involves measurements collected by multiple nodes under the same gNB-CU-CP control in a split RAN architecture, the EM sends MDT measurement activation to the gNB-CU-CP and the gNB-CU-CP may further decide which gNB-DU(s) or which gNB-CU-UP(s) to perform the MDT measurement. + +When gNB-CU-CP or a gNB-DU receive the Trace Session Activation message from the management system for a given cell or a list of cell(s) under its control, the gNB-CU-CP or gNB-DU shall start a Trace Session for the given cell or list of cell(s). For Management Based MDT sent directly to a gNB-CU-UP, no MDT Area Configuration (apart from PLMN IDs) is to be included in the MDT activation indication. + +The signalling flows for management based MDT activation in gNB-CU-CP, gNB-DU and gNB-CU-UP are shown in Figure 8.13.2.2-1, Figure 8.13.2.3-1 and in Figure 8.13.2.4-1 respectively. + +#### 8.13.2.2 Management based MDT Activation in gNB-CU-CP + +The signalling flow for Management based MDT Activation in gNB-CU-CP is shown in Figure 8.13.2.2-1. + +![Sequence diagram for Management based MDT Activation in gNB-CU-CP. The diagram shows five lifelines: EM, gNB-CU-CP, gNB-DU, gNB-CU-UP, and AMF. The sequence of messages is: 1. Trace Session Activation from EM to gNB-CU-CP; 2. Select UEs, assign TRSR (internal to gNB-CU-CP); 3. TRACE START from gNB-CU-CP to gNB-CU-UP; 4. TRACE START from gNB-CU-CP to gNB-DU; 5. CELL TRAFFIC TRACE (Trace ID) from gNB-CU-CP to AMF.](38d82ffe820e339811b396206f40a201_img.jpg) + +``` + +sequenceDiagram + participant EM + participant gNB-CU-CP + participant gNB-DU + participant gNB-CU-UP + participant AMF + Note right of gNB-CU-CP: Select UEs, assign TRSR + EM->>gNB-CU-CP: 1 Trace Session Activation + gNB-CU-CP-->>gNB-CU-UP: 2 TRACE START + gNB-CU-CP-->>gNB-DU: 3 TRACE START + gNB-CU-CP-->>AMF: 4 CELL TRAFFIC TRACE (Trace ID) + +``` + +Sequence diagram for Management based MDT Activation in gNB-CU-CP. The diagram shows five lifelines: EM, gNB-CU-CP, gNB-DU, gNB-CU-UP, and AMF. The sequence of messages is: 1. Trace Session Activation from EM to gNB-CU-CP; 2. Select UEs, assign TRSR (internal to gNB-CU-CP); 3. TRACE START from gNB-CU-CP to gNB-CU-UP; 4. TRACE START from gNB-CU-CP to gNB-DU; 5. CELL TRAFFIC TRACE (Trace ID) from gNB-CU-CP to AMF. + +**Figure 8.13.2.2-1 Management based MDT Activation in gNB-CU-CP** + +1. The EM sends a Trace Session activation request to the gNB-CU-CP. This request includes the parameters for configuring UE measurements. +2. The gNB-CU-CP shall select the suitable UEs for MDT data collection. If the UE is not in the specified area or if the serving PLMN is not within the Management Based MDT PLMN List the UE shall not be selected by the gNB-CU-CP for MDT data collection as defined in TS 32.422 [20]. + +For each selected UE, if the gNB-CU-UP should perform MDT measurement, the gNB-CU-CP sends TRACE START message to the gNB-CU-UP, including MDT configuration parameters. + +3. For each selected UE, if the gNB-DU should perform MDT measurement, the gNB-CU-CP sends TRACE START message to the gNB-DU, including MDT configuration parameters. +4. The gNB-CU-CP may send CELL TRAFFIC TRACE message to the AMF for the selected UE, including Trace ID for MDT. The AMF forwards Trace ID and other information to the TCE as specified in TS 32.422 [20]. + +If the UE reports an indication of measurement pollution, the gNB-CU-CP shall, if supported, include such indication as part of the measurement report to be sent to the TCE so that the TCE is able to correlate and filter the affected measurements. + +#### 8.13.2.3 Management based MDT Activation in gNB-DU + +The signalling flow for Management based MDT Activation in gNB-DU is shown in Figure 8.13.2.3-1. + +![Sequence diagram for Management based MDT Activation in gNB-DU. The diagram shows five lifelines: EM, gNB-DU, gNB-CU-UP, gNB-CU-CP, and AMF. The sequence of messages is: 1. gNB-CU-CP sends a UE CONTEXT SETUP REQUEST to gNB-DU. 2. gNB-DU sends a UE CONTEXT SETUP RESPONSE to gNB-CU-CP. 3. EM sends a Trace Session Activation to gNB-DU. 4. gNB-DU performs an internal action 'Select UEs, assign TRSR'. 5. gNB-DU sends a CELL TRAFFIC TRACE (Trace ID) to gNB-CU-CP. 6. gNB-CU-CP sends a CELL TRAFFIC TRACE (Trace ID) to AMF.](11f18bf0233d812ad2604f88f3385d60_img.jpg) + +``` + +sequenceDiagram + participant EM + participant gNB-DU + participant gNB-CU-UP + participant gNB-CU-CP + participant AMF + + Note right of gNB-DU: Select UEs, assign TRSR + + gNB-CU-CP->>gNB-DU: 1 UE CONTEXT SETUP REQUEST + gNB-DU-->>gNB-CU-CP: 2 UE CONTEXT SETUP RESPONSE + EM->>gNB-DU: 3 Trace Session Activation + gNB-DU->>gNB-CU-CP: 4 CELL TRAFFIC TRACE (Trace ID) + gNB-CU-CP->>AMF: 5 CELL TRAFFIC TRACE (Trace ID) + +``` + +Sequence diagram for Management based MDT Activation in gNB-DU. The diagram shows five lifelines: EM, gNB-DU, gNB-CU-UP, gNB-CU-CP, and AMF. The sequence of messages is: 1. gNB-CU-CP sends a UE CONTEXT SETUP REQUEST to gNB-DU. 2. gNB-DU sends a UE CONTEXT SETUP RESPONSE to gNB-CU-CP. 3. EM sends a Trace Session Activation to gNB-DU. 4. gNB-DU performs an internal action 'Select UEs, assign TRSR'. 5. gNB-DU sends a CELL TRAFFIC TRACE (Trace ID) to gNB-CU-CP. 6. gNB-CU-CP sends a CELL TRAFFIC TRACE (Trace ID) to AMF. + +**Figure 8.13.2.3-1 Management based MDT Activation in gNB-DU** + +1. The gNB-CU-CP sends UE CONTEXT SETUP REQUEST message to the gNB-DU, including Management based MDT PLMN List. The message may include the *Polluted Measurement Indicator* IE. If the gNB-DU has received the *Polluted Measurement Indicator* IE, the gNB-DU includes the information contained in such indicator as part of the measurement report to be sent to the TCE, so that the TCE is able to correlate and filter the affected measurements. +2. The gNB-DU sends UE CONTEXT SETUP RESPONSE message to the gNB-CU-CP. +3. The EM sends a Trace Session activation request to the gNB-DU. This request includes the parameters for configuring UE measurements. +4. The gNB-DU shall select the suitable UEs for MDT data collection. If the UE is not in the specified area or if the serving PLMN is not within the Management Based MDT PLMN List the UE shall not be selected by the gNB-DU for MDT data collection as defined in TS 32.422 [20]. + +For each selected UE, the gNB-DU may send CELL TRAFFIC TRACE message to the gNB-CU-CP in the F1 UE associated signalling, including Trace ID for MDT. + +5. Upon reception of a CELL TRAFFIC TRACE message from F1, the gNB-CU-CP shall send CELL TRAFFIC TRACE message to the AMF for this UE, including Trace ID for MDT. The AMF forwards Trace ID and other information to the TCE as specified in TS 32.422 [20]. + +#### 8.13.2.4 Management based MDT Activation in gNB-CU-UP + +The signalling flow for Management based MDT Activation in gNB-CU-UP is shown in Figure 8.13.2.4-1. + +![Sequence diagram for Management based MDT Activation in gNB-CU-UP. The diagram shows interactions between EM, gNB-CU-UP, gNB-DU, gNB-CU-CP, and AMF. The sequence is: 1. gNB-CU-CP sends BEARER CONTEXT SETUP REQUEST to gNB-CU-UP. 2. gNB-CU-UP sends BEARER CONTEXT SETUP RESPONSE to gNB-CU-CP. 3. EM sends Trace Session Activation to gNB-CU-UP. 4. gNB-CU-UP selects UEs and assigns TRSR, then sends CELL TRAFFIC TRACE (Trace ID) to gNB-CU-CP. 5. gNB-CU-CP sends CELL TRAFFIC TRACE (Trace ID) to AMF.](1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg) + +``` + +sequenceDiagram + participant EM + participant gNB-CU-UP + participant gNB-DU + participant gNB-CU-CP + participant AMF + + Note right of gNB-CU-UP: Select UEs, assign TRSR + + gNB-CU-CP->>gNB-CU-UP: 1 BEARER CONTEXT SETUP REQUEST + gNB-CU-UP-->>gNB-CU-CP: 2 BEARER CONTEXT SETUP RESPONSE + EM->>gNB-CU-UP: 3 Trace Session Activation + gNB-CU-UP->>gNB-CU-CP: 4 CELL TRAFFIC TRACE (Trace ID) + gNB-CU-CP->>AMF: 5 CELL TRAFFIC TRACE (Trace ID) + +``` + +Sequence diagram for Management based MDT Activation in gNB-CU-UP. The diagram shows interactions between EM, gNB-CU-UP, gNB-DU, gNB-CU-CP, and AMF. The sequence is: 1. gNB-CU-CP sends BEARER CONTEXT SETUP REQUEST to gNB-CU-UP. 2. gNB-CU-UP sends BEARER CONTEXT SETUP RESPONSE to gNB-CU-CP. 3. EM sends Trace Session Activation to gNB-CU-UP. 4. gNB-CU-UP selects UEs and assigns TRSR, then sends CELL TRAFFIC TRACE (Trace ID) to gNB-CU-CP. 5. gNB-CU-CP sends CELL TRAFFIC TRACE (Trace ID) to AMF. + +**Figure 8.13.2.4-1 Management based MDT Activation in gNB-CU-UP** + +1. The gNB-CU-CP sends BEARER CONTEXT SETUP REQUEST message to the gNB-CU-UP, including Management based MDT PLMN List. The message may include Polluted Measurement Indicator. If the gNB-DU has received the *Polluted Measurement Indicator* IE, the gNB-DU includes the information contained in such indicator as part of the measurement report to be sent to the TCE so that the TCE is able to correlate and filter the affected measurements. +2. The gNB-CU-UP sends BEARER CONTEXT SETUP RESPONSE message to the gNB-CU-CP. +3. The EM sends a Trace Session activation request to the gNB-CU-UP. This request includes the parameters for configuring UE measurements. +4. The gNB-CU-UP shall select the suitable UEs for MDT data collection. If the serving PLMN is not within the Management Based MDT PLMN List the UE shall not be selected by the gNB-CU-UP for MDT data collection as defined in TS 32.422 [20]. + +For each selected UE, the gNB-CU-UP may send CELL TRAFFIC TRACE message to the gNB-CU-CP in the E1 UE associated signalling, including Trace ID for MDT + +5. Upon reception of a CELL TRAFFIC TRACE message from E1, the gNB-CU-CP shall send CELL TRAFFIC TRACE message to the AMF for this UE, including Trace ID for MDT. The AMF forwards Trace ID and other information to the TCE as specified in TS 32.422 [20]. + +#### 8.13.2.5 User consent propagation in EN-DC + +In the EN-DC case, the EM provides the MDT configuration to both MeNB and en-gNB independently. + +As specified in TS 32.422 [20] in Management based MDT getting user consent is required before activating the MDT functionality because of privacy and legal obligations. In the case of EN-DC user consent gets communicated to the MeNB at the UE context setup procedure using the INITIAL CONTEXT SETUP REQUEST message. In particular when the Management Based MDT Allowed IE is contained in the INITIAL CONTEXT SETUP REQUEST message, the MeNB stores it in the UE context and uses it, together with information in the Management Based MDT PLMN List IE, if available, to allow subsequent selection of the UE for management based MDT as specified in TS 32.422 [20]. The MeNB may also receive user consent information in the HANDOVER REQUEST message. The MeNB will forward the MDT user consent to the SgNB at EN-DC setup. In particular, if available in the UE context, the MeNB will include the Management Based MDT Allowed IE and the Management Based MDT PLMN List IE in the SGNB ADDITION REQUEST message to the SgNB. Furthermore, the user consent will be forwarded to the relevant gNB-CU-UP at the bearer context setup or to the gNB-DU by including the Management Based MDT PLMN List IE in the BEARER CONTEXT SETUP REQUEST or UE CONTEXT SETUP REQUEST. + +The signalling flow for User consent proposition in EN-DC is shown in Figure 8.13.2.5-1. + +![Sequence diagram illustrating User consent propagation in EN-DC. The diagram shows the flow of information between MME, MeNB, gNB-CU-CP, gNB-DU, and gNB-CU-UP. The process starts with '0. User consent provisioning' at the MME. Step 1: MME sends '1 INITIAL CONTEXT SETUP REQUEST (Management Based MDT Allowed and Management Based MDT PLMN List)' to MeNB. MeNB then performs 'Storing UE consent within the UE context'. Step 2: MeNB sends '2 SGNB ADDITION REQUEST (Management Based MDT Allowed and Management Based MDT PLMN List)' to gNB-CU-CP. Step 3a: gNB-CU-CP sends '3a UE CONTEXT SETUP REQUEST (Management based MDT PLMN List)' to gNB-DU. Step 3b: gNB-CU-CP sends '3b BEARER CONTEXT SETUP REQUEST (Management based MDT PLMN List)' to gNB-CU-UP.](d2417b04116c354deccb25d98a84a0fb_img.jpg) + +``` + +sequenceDiagram + participant MME + participant MeNB + participant gNB-CU-CP + participant gNB-DU + participant gNB-CU-UP + + Note left of MME: 0. User consent provisioning + MME->>MeNB: 1 INITIAL CONTEXT SETUP REQUEST (Management Based MDT Allowed and Management Based MDT PLMN List) + Note right of MeNB: Storing UE consent within the UE context + MeNB->>gNB-CU-CP: 2 SGNB ADDITION REQUEST (Management Based MDT Allowed and Management Based MDT PLMN List) + gNB-CU-CP-->>gNB-DU: 3a UE CONTEXT SETUP REQUEST (Management based MDT PLMN List) + gNB-CU-CP-->>gNB-CU-UP: 3b BEARER CONTEXT SETUP REQUEST (Management based MDT PLMN List) + +``` + +Sequence diagram illustrating User consent propagation in EN-DC. The diagram shows the flow of information between MME, MeNB, gNB-CU-CP, gNB-DU, and gNB-CU-UP. The process starts with '0. User consent provisioning' at the MME. Step 1: MME sends '1 INITIAL CONTEXT SETUP REQUEST (Management Based MDT Allowed and Management Based MDT PLMN List)' to MeNB. MeNB then performs 'Storing UE consent within the UE context'. Step 2: MeNB sends '2 SGNB ADDITION REQUEST (Management Based MDT Allowed and Management Based MDT PLMN List)' to gNB-CU-CP. Step 3a: gNB-CU-CP sends '3a UE CONTEXT SETUP REQUEST (Management based MDT PLMN List)' to gNB-DU. Step 3b: gNB-CU-CP sends '3b BEARER CONTEXT SETUP REQUEST (Management based MDT PLMN List)' to gNB-CU-UP. + +**Figure 8.13.2.5-1 User consent propagation in EN-DC** + +0. User Context information are made available at the MME. +1. The MME sends INITIAL CONTEXT SETUP REQUEST message to the MeNB, including Management Based MDT Allowed IE and the Management based MDT PLMN List IE to communicate user consent to the eNB. +2. The MeNB sends SGNB ADDITION REQUEST to the gNB-CU-CP at EN-DC setup. This request includes Management Based MDT Allowed IE and, optionally, the Management based MDT PLMN List IE, if available. +- 3a. The user consent is communicated to the gNB-DU at the UE context setup by including the Management based MDT PLMN List IE in the UE CONTEXT SETUP REQUEST. +- 3b. The user consent is communicated to the gNB-CU-UP at the bearer context setup by including the Management based MDT PLMN List IE in the BEARER CONTEXT SETUP REQUEST. + +#### 8.13.2.6 User consent propagation in MR-DC with 5GC + +As specified in TS 32.422 [20] in Management based MDT getting user consent is required before activating the MDT functionality because of privacy and legal obligations. User consent is communicated to the MN at the UE context setup procedure using the INITIAL CONTEXT SETUP REQUEST message, or in HANDOVER REQUEST and PATH SWITCH REQUEST ACKNOWLEDGE messages. Modified user consent information may be received in the UE CONTEXT MODIFICATION REQUEST message. The MN stores the received information in the UE context and uses it to allow subsequent selection of the UE for management based MDT as specified in TS 32.422 [20]. The MN will forward the MDT user consent to the SN at MR-DC setup, i.e., if available in the UE context, the MN will include the Management Based MDT PLMN List IE in the S-NODE ADDITION REQUEST message or in the S-NODE MODIFICATION REQUEST message sent to the SN. Furthermore, in NR-DC and NGEN-DC, the user consent will be forwarded to the relevant SgNB-CU-UP at the bearer context setup or to the SgNB-DU by including the Management Based MDT PLMN List information in the BEARER CONTEXT SETUP REQUEST or UE CONTEXT SETUP REQUEST. Furthermore, in NR-DC and NGEN-DC, the user consent may be updated to the relevant SgNB-CU-UP at the bearer context modification or to the SgNB-DU by including the Management Based MDT PLMN List information in the BEARER CONTEXT MODIFICATION REQUEST or UE CONTEXT MODIFICATION REQUEST. + +The signalling flow for User consent propagation in NR-DC and NGEN-DC is shown in Figure 8.13.2.6-1. + +![Sequence diagram showing user consent propagation in NR-DC and NGEN-DC. The diagram involves five entities: AMF, MN, SgNB-CU-CP, SgNB-DU, and SgNB-CU-UP. The sequence starts with '0. User consent provisioning' at the AMF. Step 1: AMF sends '1 INITIAL CONTEXT SETUP REQUEST (Management Based MDT PLMN List)' to MN, which triggers 'Storing UE consent within the UE context'. Step 2: MN sends '2 S-NODE ADDITION REQUEST (Management Based MDT PLMN List)' to SgNB-CU-CP. Step 3a: SgNB-CU-CP sends '3a UE CONTEXT SETUP REQUEST (Management based MDT PLMN List)' to SgNB-DU. Step 3b: SgNB-CU-CP sends '3b BEARER CONTEXT SETUP REQUEST (Management based MDT PLMN List)' to SgNB-CU-UP.](18003425d0e8638dde4acc9c5c468c5c_img.jpg) + +``` + +sequenceDiagram + participant AMF + participant MN + participant SgNB-CU-CP + participant SgNB-DU + participant SgNB-CU-UP + + Note left of AMF: 0. User consent provisioning + AMF->>MN: 1 INITIAL CONTEXT SETUP REQUEST (Management Based MDT PLMN List) + Note right of MN: Storing UE consent within the UE context + MN->>SgNB-CU-CP: 2 S-NODE ADDITION REQUEST (Management Based MDT PLMN List) + SgNB-CU-CP->>SgNB-DU: 3a UE CONTEXT SETUP REQUEST (Management based MDT PLMN List) + SgNB-CU-CP->>SgNB-CU-UP: 3b BEARER CONTEXT SETUP REQUEST (Management based MDT PLMN List) + +``` + +Sequence diagram showing user consent propagation in NR-DC and NGEN-DC. The diagram involves five entities: AMF, MN, SgNB-CU-CP, SgNB-DU, and SgNB-CU-UP. The sequence starts with '0. User consent provisioning' at the AMF. Step 1: AMF sends '1 INITIAL CONTEXT SETUP REQUEST (Management Based MDT PLMN List)' to MN, which triggers 'Storing UE consent within the UE context'. Step 2: MN sends '2 S-NODE ADDITION REQUEST (Management Based MDT PLMN List)' to SgNB-CU-CP. Step 3a: SgNB-CU-CP sends '3a UE CONTEXT SETUP REQUEST (Management based MDT PLMN List)' to SgNB-DU. Step 3b: SgNB-CU-CP sends '3b BEARER CONTEXT SETUP REQUEST (Management based MDT PLMN List)' to SgNB-CU-UP. + +**Figure 8.13.2.6-1 User consent propagation in NR-DC and NGEN-DC** + +0. User Context information are made available at the AMF. +1. The AMF sends INITIAL CONTEXT SETUP REQUEST message to the MN, including the Management based MDT PLMN List IE to communicate user consent to the MN. +2. The MN sends S-NODE ADDITION REQUEST to the SgNB-CU-CP at NR-DC setup. This request includes the Management based MDT PLMN List IE. +- 3a. The user consent is communicated to the SgNB-DU at the UE context setup by including the Management based MDT PLMN List IE in the UE CONTEXT SETUP REQUEST. +- 3b. The user consent is communicated to the SgNB-CU-UP at the bearer context setup by including the Management based MDT PLMN List IE in the BEARER CONTEXT SETUP REQUEST. + +#### 8.13.2.7 Management based trace activation in MR-DC with 5GC + +In the MR-DC with 5GC case, the EM provides the MDT configuration to both MN and SN independently. + +In Management Based Trace Activation towards a SN, the SN may send the CELL TRAFFIC TRACE message including the Trace ID and privacy indicator to the MN as described in TS 32.422 [20]. Upon reception of the CELL TRAFFIC TRACE message from the SN, the MN will send a CELL TRAFFIC TRACE message including the Trace ID and privacy indicator to the CN for this UE. The CN forwards the Trace ID and other information to the TCE as specified in TS 32.422 [20]. + +The following shows a flow chart summarizing the functionality in MR-DC when the SN is the SgNB. + +![Sequence diagram illustrating data anonymization in MR-DC when the SN is the SgNB. The diagram shows interactions between CN, MN, SgNB-CU-CP, SgNB-DU, gNB-CU-UP, and EM. The process involves four steps: 0. Management based MDT activation from EM to SgNB-CU-CP, SgNB-DU, and gNB-CU-UP; 1. CELL TRAFFIC TRACE(Trace ID) from gNB-CU-UP to SgNB-CU-CP; 2. CELL TRAFFIC TRACE(Trace ID) from SgNB-CU-CP to MN; 3. CELL TRAFFIC TRACE(Trace ID) from MN to CN.](0dfdff10c725fe9c332b07ade9d23a5e_img.jpg) + +``` + +sequenceDiagram + participant EM + participant gNB-CU-UP + participant SgNB-DU + participant SgNB-CU-CP + participant MN + participant CN + + Note right of EM: 0. Management based MDT activation + EM->>gNB-CU-UP: + EM->>SgNB-DU: + EM->>SgNB-CU-CP: + Note right of gNB-CU-UP: 1. CELL TRAFFIC TRACE(Trace ID) + gNB-CU-UP->>SgNB-CU-CP: + Note right of SgNB-CU-CP: 2. CELL TRAFFIC TRACE(Trace ID) + SgNB-CU-CP->>MN: + Note right of MN: 3. CELL TRAFFIC TRACE(Trace ID) + MN->>CN: + +``` + +Sequence diagram illustrating data anonymization in MR-DC when the SN is the SgNB. The diagram shows interactions between CN, MN, SgNB-CU-CP, SgNB-DU, gNB-CU-UP, and EM. The process involves four steps: 0. Management based MDT activation from EM to SgNB-CU-CP, SgNB-DU, and gNB-CU-UP; 1. CELL TRAFFIC TRACE(Trace ID) from gNB-CU-UP to SgNB-CU-CP; 2. CELL TRAFFIC TRACE(Trace ID) from SgNB-CU-CP to MN; 3. CELL TRAFFIC TRACE(Trace ID) from MN to CN. + +**Figure 8.13.2.7-1 Data anonymization in MR-DC when the SN is the SgNB** + +0. The gNB-CU-CP, the gNB-CU-UP, the gNB-DU receives the MDT configuration from EM and select the suitable UEs for MDT data collection. The anonymization MDT configuration parameter from the EM is considered to be IMEI-TAC. +1. For the management based MDT activation in gNB-CU-UP and/or in gNB-DU, if the gNB-CU-UP and/or the gNB-DU receive an MDT Configuration including the anonymization parameter set to IMEI-TAC, the gNB-CU-UP and/or gNB-DU send CELL TRAFFIC TRACE message to the gNB-CU-CP for this UE, including Trace ID and privacy indicator. +2. For the management based MDT activation in gNB-CU-CP, upon receiving the CELL TRAFFIC TRACE message from E1/F1, the gNB-CU-CP shall send a CELL TRAFFIC TRACE message to the MN for this UE, including Trace ID and privacy indicator. +3. The MN sends a CELL TRAFFIC TRACE message to the CN for this UE, including Trace ID and privacy indicator. The CN forwards Trace ID and other information to the TCE as specified in TS 32.422 [20]. + +### 8.13.3 Alignment of MDT and QoE Measurements + +In case of split gNB architecture, the gNB-CU-CP can send the TRACE START message for the MDT measurement subject to alignment with a QoE measurement to the gNB-CU-UP and gNB-DU, e.g., upon/after the reception of QoE measurement session start indication from the UE, as specified in TS 38.300 [2]. + +### 8.13.4 MDT reporting + +Each node involved in the MDT measurement reports the measurements collected directly to the TCE the node has been configured with. + +In the case where issues (e.g. in-device coexistence problem) potentially affecting immediate MDT measurements were detected during a measurement reporting process, an indication of the issue should be logged in the affected measurement reports to the TCE so that the TCE is able to correlate and filter the affected measurements. + +## 8.14 Self-optimisation + +### 8.14.1 Overall procedures for MRO + +The following clauses describe the overall procedures for MRO involving F1. + +#### 8.14.1.1 Signalling of RLF information from gNB-CU to gNB-DU + +The signalling flow for signalling of RLF information from gNB-CU to gNB-DU is shown in Figure 8.14.1.1-1, where the example where NG-RAN nodes exchange the RLF Report via the Xn: FAILURE INDICATION message has been considered. + +![Sequence diagram showing the signalling of RLF information from gNB-CU to gNB-DU in NG RAN. The diagram involves four lifelines: UE, gNB1-DU, gNB1-CU, and gNB2. The sequence of messages is: 1. RRC: UE Information Request/Response (including RLF Report from the UE) between UE and gNB2; 2. Xn: Failure Indication (including RLF Report) from gNB2 to gNB1-CU; 3. F1: Access and Mobility Indication (including RLF Report) from gNB1-CU to gNB1-DU.](e60c2d24a97a2855d98671d27ea43d0f_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB1-DU + participant gNB1-CU + participant gNB2 + UE->>gNB2: 1. RRC: UE Information Request/Response (including RLF Report from the UE) + gNB2->>gNB1-CU: 2. Xn: Failure Indication (including RLF Report) + gNB1-CU->>gNB1-DU: 3. F1: Access and Mobility Indication (including RLF Report) + +``` + +Sequence diagram showing the signalling of RLF information from gNB-CU to gNB-DU in NG RAN. The diagram involves four lifelines: UE, gNB1-DU, gNB1-CU, and gNB2. The sequence of messages is: 1. RRC: UE Information Request/Response (including RLF Report from the UE) between UE and gNB2; 2. Xn: Failure Indication (including RLF Report) from gNB2 to gNB1-CU; 3. F1: Access and Mobility Indication (including RLF Report) from gNB1-CU to gNB1-DU. + +**Figure 8.14.1.1-1 Example of signalling of RLF information from gNB-CU to gNB-DU in NG RAN** + +1. A UE with a logged RLF Report connects to a cell in gNB2 and it signals the RLF Report to gNB2 by means of the RRC UE Information Request/Response procedures. +2. The gNB2 sends an Xn: Failure Indication to gNB1-CU where the UE may have previously been connected prior to the connection failure. This includes also the RLF Report. +3. The gNB1-CU sends the F1: Access and Mobility Indication message to the gNB1-DU, including the RLF Report. + +It is also possible for the gNB-CU receiving the RLF Report from the UE to signal it directly to the gNB-DU by means of the F1: Access and Mobility Indication procedure. + +#### 8.14.1.2 Signalling of RACH information from gNB-CU to gNB-DU + +The signalling flow for signalling of RACH information from gNB-CU to gNB-DU is shown in Figure 8.14.1.2-1, where the example where NG-RAN nodes exchange the RACH Report via the Xn: ACCESS AND MOBILITY INDICATION message has been considered. + +![Sequence diagram showing RACH information signaling from gNB-CU to gNB-DU in NG-RAN. The diagram involves four entities: UE, gNB1-DU, gNB1-CU, and gNB2. The sequence of messages is: 1. RRC: UE Information Request/Response (including RACH Report from the UE) from UE to gNB2; 2. Xn: Access and Mobility Indication (including RACH report) from gNB2 to gNB1-CU; 3. F1: Access and Mobility Indication (including RACH Report) from gNB1-CU to gNB1-DU.](a963ca41bde1669b18a4b783616f228b_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB1-DU + participant gNB1-CU + participant gNB2 + Note right of UE: 1. RRC: UE Information Request/Response (including RACH Report from the UE) + UE->>gNB2: + Note right of gNB2: 2. Xn: Access and Mobility Indication (including RACH report) + gNB2->>gNB1-CU: + Note right of gNB1-CU: 3. F1: Access and Mobility Indication (including RACH Report) + gNB1-CU->>gNB1-DU: + +``` + +Sequence diagram showing RACH information signaling from gNB-CU to gNB-DU in NG-RAN. The diagram involves four entities: UE, gNB1-DU, gNB1-CU, and gNB2. The sequence of messages is: 1. RRC: UE Information Request/Response (including RACH Report from the UE) from UE to gNB2; 2. Xn: Access and Mobility Indication (including RACH report) from gNB2 to gNB1-CU; 3. F1: Access and Mobility Indication (including RACH Report) from gNB1-CU to gNB1-DU. + +**Figure 8.14.1.2-1 Example of signalling of RACH information from gNB-CU to gNB-DU in NG-RAN** + +1. A UE with a RACH Report concerning cells of gNB1 connects to a cell in gNB2 and it signals the RACH Report to gNB2 by means of the RRC UE Information Request/Response procedures. +2. GNB2 sends an Xn: Access and Mobility Indication message to gNB1-CU where the UE may have previously been connected. This includes also the RACH Report. +3. GNB1-CU sends the F1: Access and Mobility Indication message to the gNB1-DU, including the RACH Report. + +It is also possible for the gNB-CU receiving the RACH Report from the UE to signal it directly to the gNB-DU by means of the F1: Access and Mobility Indication procedure. + +## 8.15 Overall procedures for NR MBS + +### 8.15.1 General + +The following clauses describe the overall procedures for NR MBS involving E1 and F1. + +#### 8.15.1.1 Broadcast MBS Session Setup + +Figure 8.15.1.1-1 illustrates an exemplified interaction of NGAP, E1AP, F1AP and RRC protocol functions at Broadcast MBS Session Setup. + +![Sequence diagram showing Broadcast MBS Session Setup. The diagram involves five entities: UE, gNB-DU, gNB-CU-CP, gNB-CU-UP, and 5GC. The sequence of messages is: 1. NGAP Broadcast Session Setup Request from 5GC to gNB-CU-CP; 2. E1AP BC Bearer Context Setup Request from gNB-CU-CP to gNB-CU-UP; 3. E1AP BC Bearer Context Setup Response from gNB-CU-UP to gNB-CU-CP; 4. IGMP/MLD join from gNB-CU-UP to 5GC; 5. F1AP Broadcast Context Setup Request from gNB-CU-CP to gNB-DU; 6. F1AP Broadcast Context Setup Response from gNB-DU to gNB-CU-CP; 7. E1AP BC Bearer Context Modification Request from gNB-CU-CP to gNB-CU-UP; 8. E1AP BC Bearer Context Modification Response from gNB-CU-UP to gNB-CU-CP; 9. MCCH configuration from gNB-CU-CP to gNB-DU; 10. NGAP Broadcast Session Setup Response from gNB-CU-CP to 5GC; 11. Broadcast MBS Media Stream from gNB-CU-UP to gNB-DU.](b43872c7a81f62572f3be03b77d8655f_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB-DU + participant gNB-CU-CP + participant gNB-CU-UP + participant 5GC + Note right of 5GC: 1. NGAP Broadcast Session Setup Request (5GC NG-U TNL) + 5GC->>gNB-CU-CP: + Note right of gNB-CU-CP: 2. E1AP BC Bearer Context Setup Request (5GC NG-U TNL) + gNB-CU-CP->>gNB-CU-UP: + Note right of gNB-CU-UP: 3. E1AP BC Bearer Context Setup Response (NG-U unicast: gNb NG-U TNL, F1-U TNL CU) + gNB-CU-UP->>gNB-CU-CP: + Note right of gNB-CU-UP: 4. IGMP/MLD join (for NG-U multicast transport) + gNB-CU-UP->>5GC: + Note right of gNB-CU-CP: 5. F1AP Broadcast Context Setup Request (F1-U TNL CU) + gNB-CU-CP->>gNB-DU: + Note right of gNB-DU: 6. F1AP Broadcast Context Setup Response (F1-U TNL DU) + gNB-DU->>gNB-CU-CP: + Note right of gNB-CU-CP: 7. E1AP BC Bearer Context Modification Request (F1-U TNL DU) + gNB-CU-CP->>gNB-CU-UP: + Note right of gNB-CU-UP: 8. E1AP BC Bearer Context Modification Response + gNB-CU-UP->>gNB-CU-CP: + Note right of gNB-CU-CP: 9. MCCH configuration + gNB-CU-CP->>gNB-DU: + Note right of gNB-CU-CP: 10. NGAP Broadcast Session Setup Response (NG-U unicast: gNb NG-U TNL) + gNB-CU-CP->>5GC: + Note right of gNB-CU-UP: 11. Broadcast MBS Media Stream + gNB-CU-UP-->>gNB-DU: + gNB-DU-->>UE: + +``` + +Sequence diagram showing Broadcast MBS Session Setup. The diagram involves five entities: UE, gNB-DU, gNB-CU-CP, gNB-CU-UP, and 5GC. The sequence of messages is: 1. NGAP Broadcast Session Setup Request from 5GC to gNB-CU-CP; 2. E1AP BC Bearer Context Setup Request from gNB-CU-CP to gNB-CU-UP; 3. E1AP BC Bearer Context Setup Response from gNB-CU-UP to gNB-CU-CP; 4. IGMP/MLD join from gNB-CU-UP to 5GC; 5. F1AP Broadcast Context Setup Request from gNB-CU-CP to gNB-DU; 6. F1AP Broadcast Context Setup Response from gNB-DU to gNB-CU-CP; 7. E1AP BC Bearer Context Modification Request from gNB-CU-CP to gNB-CU-UP; 8. E1AP BC Bearer Context Modification Response from gNB-CU-UP to gNB-CU-CP; 9. MCCH configuration from gNB-CU-CP to gNB-DU; 10. NGAP Broadcast Session Setup Response from gNB-CU-CP to 5GC; 11. Broadcast MBS Media Stream from gNB-CU-UP to gNB-DU. + +**Figure 8.15.1.1-1: Broadcast MBS Session Setup** + +1. The 5GC starts the broadcast session by sending the NGAP Broadcast Session Setup Request message to the gNB containing the TMGI, S-NSSAI, 5G QoS Profile, area information and transport information (for NG-U multicast transport it provides the IP multicast address and the IP source specific multicast address). +- 2/3. The gNB-CU-CP sets up the broadcast bearer context, providing NG-U transport information from the 5GC to the gNB-CU-UP and receiving from the gNB-CU-UP the NG-U GTP DL TEID in case NG-U unicast transport was selected and an F1-U GTP UL TEID per MRB. +4. In case of NG-U multicast transport, the gNB-CU-UP joins the NG-U multicast group. +- 5/6. The gNB-CU-CP establishes the Broadcast MBS Session Context at the gNB-DU, providing MRB configuration, other relevant session parameters and F1-U GTP UL TEID information, and receiving F1-U GTP DL TEID information. +- 7/8. The gNB-CU-CP triggers BC Bearer Context Modification Request towards the gNB-CU-UP to provide the F1-U GTP DL TEID information. +9. The gNB-DU configures broadcast resources and provides broadcast configuration information to the UEs by means of MCCH. +10. The gNB-CU CP successfully terminates the NGAP broadcast Session Setup procedure. In case the gNB has chosen NG-U unicast transport, NG-U GTP DL TEID information is provided to the 5GC. +11. The broadcast MBS media stream is provided to the UEs. + +On NG-U, in case of location dependent broadcast MBS Sessions, multiple shared NG-U transport tunnels may need to be setup, one per Area Session ID served by the gNB. + +In case of shared NG-U termination, + +- the gNB-CU-UP may provide the gNB-CU-CP at E1 setup or configuration update about established shared NG-U terminations, indicated by one or several MBS Session IDs. +- at establishment of the BC bearer context in the gNB-CU-UP, the gNB-CU-CP may request the gNB-CU-UP to either apply the available MRB configuration of the shared NG-U termination, or to apply the MRB configuration requested by the gNB-CU-CP. The gNB-CU-UP provides the MRB configuration to the gNB-CU-CP if the MRB configuration requested by the gNB-CU-CP and the available MRB configuration of the shared NG-U termination are different. + +#### 8.15.1.2 Multicast MBS Session Context Establishment + +Figure 8.15.1.2-1 illustrates an exemplified interaction of NGAP, E1AP, F1AP and RRC protocol functions for Multicast MBS Session Context Establishment with a UE joining an active multicast session as the first UE joining in its serving gNB. + +![Sequence diagram for Multicast MBS Session Context establishment. Lifelines: UE, gNB-DU, gNB-CU-CP, gNB-CU-UP, 5GC. The process involves NGAP and F1AP signaling to establish multicast bearers and context across the network elements.](e16bfa31d748f4d99ec4ae3d16656926_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB-DU + participant gNB-CU-CP + participant gNB-CU-UP + participant 5GC + + Note right of gNB-DU: 0. No MBS Context established for a certain multicast MBS Session (TMGI) which is currently active + + Note left of gNB-CU-CP: 1. UE joins the multicast session. + + gNB-CU-CP->>gNB-CU-UP: 1. NGAP PDU Session Resource Modify Request (join TMGI) + gNB-CU-CP->>gNB-CU-UP: 2. E1AP MC Bearer Context Setup Request + gNB-CU-UP-->>gNB-CU-CP: 3. E1AP MC Bearer Context Setup Response (NG-U unicast: gNB NG-U TNL) + gNB-CU-CP->>5GC: 4. NGAP Distribution Setup Request (NG-U unicast: gNB NG-U TNL) + 5GC-->>gNB-CU-CP: 5. NGAP Distribution Setup Response (5GC NG-U TNL, MBS QoS Parameters) + gNB-CU-CP->>gNB-CU-UP: 5a. E1AP MC Bearer Context Modification Request (5GC NG-U TNL, MBS QoS Parameters) + gNB-CU-UP-->>gNB-CU-CP: 5b. E1AP MC Bearer Context Modification Response + gNB-CU-CP->>gNB-DU: 6. F1AP Multicast Context Setup Request + gNB-DU-->>gNB-CU-CP: 7. F1AP Multicast Context Setup Response + gNB-CU-CP->>gNB-DU: 8. F1AP UE Context Modification Request (TMGI, UE Multicast MRB to Be Setup List) + gNB-DU-->>gNB-CU-CP: 9. F1AP UE Context Modification Response (DU To CU RRC Information) + gNB-CU-CP->>gNB-DU: 10. F1AP Multicast Distribution Setup Request (F1-U TNL DU) + gNB-CU-CP->>gNB-CU-UP: 11. E1AP MC Bearer Context Modification Request (F1-U TNL DU) + gNB-CU-UP-->>gNB-CU-CP: 12. E1AP MC Bearer Context Modification Response (F1-U TNL CU) + gNB-DU-->>gNB-CU-CP: 13. F1AP Multicast Distribution Setup Response (F1-U TNL CU) + Note right of gNB-CU-UP: 14. IGMP/MLD join (for NG-U mc transport) + gNB-CU-CP->>5GC: 15. NGAP PDU Session Resource Modify Response + + Note left of UE: 16. per UE RRC Configuration with MRB resources + gNB-CU-CP->>gNB-DU: 16d. RRCReconfiguration + gNB-DU-->>gNB-CU-CP: 16c. F1AP DL RRC Message Transfer + gNB-CU-CP->>gNB-DU: 16e. RRCReconfigurationComplete + gNB-DU-->>gNB-CU-CP: 16f. F1AP UL RRC Message Transfer + + Note right of gNB-DU: 17. Multicast MBS Media Stream + +``` + +Sequence diagram for Multicast MBS Session Context establishment. Lifelines: UE, gNB-DU, gNB-CU-CP, gNB-CU-UP, 5GC. The process involves NGAP and F1AP signaling to establish multicast bearers and context across the network elements. + +**Figure 8.15.1.2-1: Multicast MBS Session Context establishment** + +0. For a certain multicast MBS session (TMGI), which is currently active, no multicast MBS session context is yet established in the gNB. + +1. The UE joins the multicast session. + +NOTE 1: NAS related details for PDU Session signalling are not shown in Figure 8.15.1.2-1. + +2/3. The gNB-CU-CP establishes the multicast bearer context at the gNB-CU-UP. For unicast NG-U transport the GTP DL TEID is retrieved. + +4/5. The gNB-CU-CP triggers the NGAP Distribution Setup procedure. For unicast NG-U transport, DL GTP TEID is provided to the 5GC. For multicast NG-U transport, multicast address information is retrieved from the 5GC. Multicast session QoS parameters are provided by the 5GC. + +5a/5b. The gNB-CU-CP triggers the setup of MRB resources via the E1AP MC Bearer Context Modification procedure. For multicast NG-U transport the 5GC shared NG-U multicast address information is provided to the gNB-CU-UP. Multicast session QoS parameters are provided to the gNB-CU-UP. + +6/7. The gNB-CU-CP establishes the Multicast Context at the gNB-DU, providing MRB configuration. It may contain MBS Area Session ID information. + +8/9. The gNB-CU-CP retrieves the MRB configuration for the joined UE from the gNB-DU via F1 UE Context Management procedures. + +NOTE 2: The interactions between the gNB-CU-CP and gNB-CU-UP for UE specific Bearer Context management before and after step 8/9 are not illustrated in this Figure. + +10. The gNB-DU triggers the establishment of F1-U resources, which are established either per gNB-DU or per cell or per MBS Area Session ID. +- 11/12. The gNB-CU-UP side of the F1-U is established by means of the E1AP MC Bearer Context Modification procedure, providing the gNB-DU side F1-U TNL to the gNB-CU-UP, which provides the gNB-CU-UP side F1-U TNL address in return. +13. The gNB-CU-UP side F1-U TNL address is provided to the gNB-DU. +14. In case of NG-U multicast transport, the gNB-CU-UP joins the NG-U multicast group. +15. The gNB successfully terminates the NGAP procedure for establishing the multicast session context. +16. The gNB-CU-CP RRC-configures each UE which has joined the multicast group. +17. The multicast MBS media stream is provided to the UEs. + +On NG-U, in case of location dependent multicast MBS Sessions, multiple shared NG-U transport tunnels may need to be setup, one per Area Session ID served by the gNB. + +In case of shared NG-U termination, + +- the gNB-CU-UP may provide the gNB-CU-CP at E1 setup or configuration update about established shared NG-U terminations, indicated by one or several MBS Session IDs. +- at establishment of the MC bearer context in the gNB-CU-UP, the gNB-CU-CP may request the gNB-CU-UP to either apply the available MRB configuration of the shared NG-U termination, or to apply the MRB configuration requested by the gNB-CU-CP. The gNB-CU-UP provides the MRB configuration to the gNB-CU-CP if the MRB configuration requested by the gNB-CU-CP and the available MRB configuration of the shared NG-U termination are different. + +#### 8.15.1.3 Multicast MRB type re-configuration with F1-U ptp-retransmission tunnel establishment + +![Sequence diagram for Multicast MRB type re-configuration with F1-U ptp-retransmission tunnel establishment. The diagram shows interactions between UE, gNB-DU, gNB-CU-CP, gNB-CU-UP, and 5GC. The process involves F1AP UE Context Modification, F1AP Multicast Distribution Setup, E1AP MC Bearer Context Modification, RRC Reconfiguration, and PDCP Status Report and PDCP PDU retransmissions.](468be155058fd5d2862919eb8ec35496_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB-DU + participant gNB-CU-CP + participant gNB-CU-UP + participant 5GC + + Note right of gNB-DU: 1. F1AP UE Context Modification Required +(DU to CU RRC Information, per MRB: MRB type reconfiguration) + gNB-DU->>gNB-CU-CP: 1. F1AP UE Context Modification Required + Note right of gNB-CU-CP: 2. F1AP UE Context Modification Confirm +(RRContainer, per MRB MBS PTP Retransmission Tunnel Required) + gNB-CU-CP->>gNB-DU: 2. F1AP UE Context Modification Confirm + Note right of gNB-DU: 4. F1AP Multicast Distribution Setup Request +(F1-U TNL DU) + gNB-DU->>gNB-CU-CP: 4. F1AP Multicast Distribution Setup Request + Note right of gNB-CU-CP: 5. E1AP MC Bearer Context Modification Request +(F1-U TNL DU) + gNB-CU-CP->>gNB-CU-UP: 5. E1AP MC Bearer Context Modification Request + Note right of gNB-CU-UP: 6. E1AP MC Bearer Context Modification Response +(F1-U TNL CU) + gNB-CU-UP->>gNB-CU-CP: 6. E1AP MC Bearer Context Modification Response + Note right of gNB-CU-CP: 7. F1AP Multicast Distribution Setup Response +(F1-U TNL CU) + gNB-CU-CP->>gNB-DU: 7. F1AP Multicast Distribution Setup Response + Note right of gNB-DU: 8. RRCReconfiguration + gNB-DU->>UE: 8. RRCReconfiguration + Note right of UE: 9a. RRCReconfigurationComplete + UE->>gNB-DU: 9a. RRCReconfigurationComplete + Note right of gNB-DU: 9b. F1AP UL RRC Message Transfer + gNB-DU->>gNB-CU-CP: 9b. F1AP UL RRC Message Transfer + Note right of gNB-DU: 10. PDCP Status Report and PDCP PDU retransmissions + gNB-DU->>gNB-CU-UP: 10. PDCP Status Report and PDCP PDU retransmissions + +``` + +Sequence diagram for Multicast MRB type re-configuration with F1-U ptp-retransmission tunnel establishment. The diagram shows interactions between UE, gNB-DU, gNB-CU-CP, gNB-CU-UP, and 5GC. The process involves F1AP UE Context Modification, F1AP Multicast Distribution Setup, E1AP MC Bearer Context Modification, RRC Reconfiguration, and PDCP Status Report and PDCP PDU retransmissions. + +**Figure 8.15.1.3-1: Multicast MRB type re-configuration with F1-U ptp retransmission tunnel establishment** + +1. The gNB-DU decides to change the MRB type configuration for a UE and provides the new configuration to the gNB-CU-CP along with a per-MRB MRB type reconfiguration indication and the MRB Reconfigured RLC mode. +2. The gNB-CU-CP confirms the modification request and indicates this to the gNB-DU. The gNB-CU-CP may request the gNB-DU to establish F1-U ptp retransmission resources in order for the UE to perform PDCP Status Report and receive retransmitted PDCP PDUs for the reconfigured MRBs. +4. - 7. If necessary, the gNB-DU requests the establishment of F1-U resources for ptp retransmission by means of triggering the F1AP Multicast Distribution Setup procedure, which in turn triggers the E1AP MC Bearer Context Modification procedure to exchange F1-U tunnel end-point addresses. + +NOTE: Depending on MRB bearer type reconfiguration the gNB-DU may also request to release some F1-U resources. + +8/9. The RRC Reconfiguration procedure is performed + +10. PDCP Status Report and PDCP PDU retransmission can take place via the established F1-U ptp retransmission resources. + +### 8.15.2 Mobility procedure for Multicast + +#### 8.15.2.1 Inter-gNB-CU Mobility between MBS Supporting nodes + +Figure 8.15.2.1-1 shows the inter-gNB-CU multicast mobility procedure between MBS Supporting nodes during an active multicast session. + +![Sequence diagram of the inter-gNB-CU multicast mobility procedure. The diagram shows interactions between Source gNB-CU-CP, Source gNB-CU-UP, Target gNB-DU, Target gNB-CU-CP, Target gNB-CU-UP, and CN. The procedure involves MC BEARER CONTEXT MODIFICATION REQUEST/RESPONSE, HANDOVER REQUEST/ACKNOWLEDGE, BEARER CONTEXT SETUP REQUEST/RESPONSE, UE CONTEXT SETUP REQUEST/RESPONSE, MULTICAST DISTRIBUTION SETUP REQUEST/RESPONSE, and MRB data forwarding steps.](41af98c5f15e6022f8ddde55567cf56e_img.jpg) + +``` + +sequenceDiagram + participant Source gNB-CU-CP + participant Source gNB-CU-UP + participant Target gNB-DU + participant Target gNB-CU-CP + participant Target gNB-CU-UP + participant CN + + Note left of Source gNB-CU-CP: 1. MC BEARER CONTEXT MODIFICATION REQUEST + Source gNB-CU-CP->>Source gNB-CU-UP: 1. MC BEARER CONTEXT MODIFICATION REQUEST + Note right of Source gNB-CU-UP: 2. MC BEARER CONTEXT MODIFICATION RESPONSE + Source gNB-CU-UP-->>Source gNB-CU-CP: 2. MC BEARER CONTEXT MODIFICATION RESPONSE + Note left of Source gNB-CU-CP: 3. HANDOVER REQUEST + Source gNB-CU-CP->>Target gNB-CU-CP: 3. HANDOVER REQUEST + Note right of Target gNB-CU-CP: 4. Multicast MBS Session Context Establishment procedure + Target gNB-CU-CP->>Target gNB-CU-UP: 5. BEARER CONTEXT SETUP REQUEST + Note right of Target gNB-CU-UP: 6. BEARER CONTEXT SETUP RESPONSE + Target gNB-CU-UP-->>Target gNB-CU-CP: 6. BEARER CONTEXT SETUP RESPONSE + Note left of Target gNB-CU-CP: 7. UE CONTEXT SETUP REQUEST + Target gNB-CU-CP->>Target gNB-DU: 7. UE CONTEXT SETUP REQUEST + Note right of Target gNB-DU: 8. UE CONTEXT SETUP RESPONSE + Target gNB-DU-->>Target gNB-CU-CP: 8. UE CONTEXT SETUP RESPONSE + Note left of Target gNB-CU-CP: 9. MULTICAST DISTRIBUTION SETUP REQUEST + Target gNB-CU-CP->>Target gNB-DU: 9. MULTICAST DISTRIBUTION SETUP REQUEST + Note right of Target gNB-DU: 12. MULTICAST DISTRIBUTION SETUP RESPONSE + Target gNB-DU-->>Target gNB-CU-CP: 12. MULTICAST DISTRIBUTION SETUP RESPONSE + Note left of Target gNB-CU-CP: 10. MC BEARER CONTEXT MODIFICATION REQUEST + Target gNB-CU-CP->>Target gNB-CU-UP: 10. MC BEARER CONTEXT MODIFICATION REQUEST + Note right of Target gNB-CU-UP: 11. MC BEARER CONTEXT MODIFICATION RESPONSE + Target gNB-CU-UP-->>Target gNB-CU-CP: 11. MC BEARER CONTEXT MODIFICATION RESPONSE + Note left of Target gNB-CU-CP: 13. HANDOVER REQUEST ACKNOWLEDGE + Target gNB-CU-CP->>Source gNB-CU-CP: 13. HANDOVER REQUEST ACKNOWLEDGE + Note left of Source gNB-CU-CP: 14. MC BEARER CONTEXT MODIFICATION REQUEST + Source gNB-CU-CP->>Source gNB-CU-UP: 14. MC BEARER CONTEXT MODIFICATION REQUEST + Note right of Source gNB-CU-UP: 15. MC BEARER CONTEXT MODIFICATION RESPONSE + Source gNB-CU-UP-->>Source gNB-CU-CP: 15. MC BEARER CONTEXT MODIFICATION RESPONSE + Note right of Target gNB-CU-UP: 16. MRB data forwarding + Target gNB-CU-UP->>Source gNB-CU-UP: 16. MRB data forwarding + Note right of Source gNB-CU-UP: 17. MRB forwarding/catch up data + Source gNB-CU-UP->>Target gNB-CU-UP: 17. MRB forwarding/catch up data + +``` + +Sequence diagram of the inter-gNB-CU multicast mobility procedure. The diagram shows interactions between Source gNB-CU-CP, Source gNB-CU-UP, Target gNB-DU, Target gNB-CU-CP, Target gNB-CU-UP, and CN. The procedure involves MC BEARER CONTEXT MODIFICATION REQUEST/RESPONSE, HANDOVER REQUEST/ACKNOWLEDGE, BEARER CONTEXT SETUP REQUEST/RESPONSE, UE CONTEXT SETUP REQUEST/RESPONSE, MULTICAST DISTRIBUTION SETUP REQUEST/RESPONSE, and MRB data forwarding steps. + +Figure 8.15.2.1-1: Inter-gNB-CU Mobility for Multicast + +1. The Source gNB-CU-CP sends MC BEARER CONTEXT MODIFICATION REQUEST message towards the Source gNB-CU-UP, to request the last delivered MRB Progress of an MBS Session related to a Multicast F1-U Context Reference E1. +2. The Source gNB-CU-UP responds to the gNB-CU-CP in the MC BEARER CONTEXT MODIFICATION RESPONSE message, providing the last delivered MRB Progress. +3. The source gNB-CU-CP sends the HANDOVER REQUEST message to the target gNB-CU-CP with the last delivered MRB progress for the Multicast sessions the UE has joined. +4. In case the Multicast session which the UE has joined was not established in the target cell, the target gNB-CU-CP triggers the Multicast MBS Session Context Establishment procedure as defined in section 8.15.1.2. +5. The target gNB-CU-CP triggers MC BEARER CONTEXT SETUP REQUEST message towards the target gNB-CU-UP. +6. The target gNB-CU-UP responds to the target gNB-CU-CP by sending the MC BEARER CONTEXT SETUP RESPONSE message. + +7. The target gNB-CU-CP sends UE CONTEXT SETUP REQUEST towards the target gNB-DU. If the target gNB-CU-CP has decided to request a PTP Forwarding tunnel, the message contains the PTP Forwarding Tunnel Required indication and the last delivered MRB Progress for the MRBs requested to be configured. + 8. The target gNB-DU sends UE CONTEXT SETUP RESPONSE towards the target gNB-CU-CP. + 9. If a PTP Forwarding Tunnel was requested in step 7, the target gNB-DU shall, if supported, trigger the F1-U tunnel establishment via MULTICAST DISTRIBUTION SETUP REQUEST, including the F1-U DL UP TNL information and the last delivered MRB Progress for the each of the MRB. + 10. The target gNB-CU-CP sends the MC BEARER CONTEXT MODIFICATION REQUEST towards the target gNB-CU-UP, including for each MRB a request for the oldest available MRB Progress information, the last delivered MRB Progress, and the F1-U DL UP TNL information. + 11. Based on the information received in step 10, the target gNB-CU-UP determines whether the Xn-U data forwarding is needed or not, and in case it is needed, provide for each MRB the oldest available MRB Progress and the assigned XN-U DL Forwarding UP TNL Info to the target gNB-CU-CP in the MC BEARER CONTEXT MODIFICATION RESPONSE message. + 12. In case step 9 was triggered, the target gNB-CU-CP sends the MULTICAST DISTRIBUTION SETUP RESPONSE to the target gNB-DU. + 13. The target gNB-CU-CP sends HANDOVER REQUEST ACKNOWLEDGE to the source gNB-CU-CP, including the XN-U DL Forwarding UP TNL Info and the oldest available MRB Progress for each MRB. + 14. The source gNB-CU-CP forwards the XN-U DL Forwarding UP TNL Info and the oldest available MRB Progress for each MRB to the source gNB-CU-UP via MC BEARER CONTEXT MODIFICATION REQUEST message. + 15. The source gNB-CU-UP sends the MC BEARER CONTEXT MODIFICATION RESPONSE message to the source gNB-CU-CP. + 16. The source gNB-CU-UP starts to forward MBS data towards the target gNB-CU-UP. +- NOTE: step 16 may happen before or after or in parallel with step 15. +17. If a PTP Forwarding Tunnel was established, the target gNB-CU-UP sends the forwarding data to the target gNB-DU. + +## 8.16 Overall procedures for CPAC + +The following clauses describe the overall procedures for CPAC involving E1 and F1. + +### 8.16.1 MN initiated Conditional PSCell Addition + +The procedure for MN initiated Conditional PSCell Addition (CPA) is shown in Figure 8.16-1. + +![Sequence diagram for Conditional Secondary Node Addition procedure. Lifelines: UE, MN, SN-CU-CP, SN-CU-UP, SN-DU, Other potential SN, UPF, AMF. The procedure involves SN Addition Request, Bearer Context Setup, RRC reconfiguration, Random Access Procedure, SN Status Transfer, Data Forwarding, and Path Update procedure.](d04c50badc78d5ba47bf4e352af4a754_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MN + participant SN-CU-CP + participant SN-CU-UP + participant SN-DU + participant Other potential SN + participant UPF + participant AMF + + Note left of MN: 1. SN Addition Request + MN->>SN-CU-CP: 1. SN Addition Request + SN-CU-CP->>SN-CU-UP: a1. BEARER CONTEXT SETUP REQUEST + SN-CU-UP-->>SN-CU-CP: a2. BEARER CONTEXT SETUP RESPONSE + SN-CU-CP->>SN-DU: a3. F1 UE context setup procedure + SN-CU-CP->>SN-CU-UP: a4. BEARER CONTEXT MODIFICATION REQUEST + SN-CU-UP-->>SN-CU-CP: a5. BEARER CONTEXT MODIFICATION RESPONSE + Note left of MN: 2. SN Addition Request Acknowledge + MN->>SN-CU-CP: 2. SN Addition Request Acknowledge + Note left of MN: 2a. Xn-U Address Indication + MN->>Other potential SN: 2a. Xn-U Address Indication + Note left of MN: 3. RRC reconfiguration* Message (Containing MN RRC reconfiguration** >> SN RRCReconfiguration***) + MN->>UE: 3. RRC reconfiguration* Message (Containing MN RRC reconfiguration** >> SN RRCReconfiguration***) + Note left of MN: 4. RRC reconfiguration complete* message + UE->>MN: 4. RRC reconfiguration complete* message + Note left of MN: 4a. RRC reconfiguration complete** message (containing SN RRCReconfigurationComplete***) + MN->>UE: 4a. RRC reconfiguration complete** message (containing SN RRCReconfigurationComplete***) + Note left of MN: 5a. SN Reconfiguration Complete + MN->>SN-CU-CP: 5a. SN Reconfiguration Complete + Note left of SN-CU-CP: 5b. SN Release Request + SN-CU-CP->>Other potential SN: 5b. SN Release Request + Note left of SN-CU-CP: 5c. SN Release Request Acknowledge + SN-CU-CP-->>Other potential SN: 5c. SN Release Request Acknowledge + Note left of MN: 6. Random Access Procedure + MN->>UE: 6. Random Access Procedure + Note left of SN-DU: Downlink Data Delivery Status + SN-DU->>SN-CU-UP: Downlink Data Delivery Status + Note left of SN-DU: a6. ACCESS SUCCESS + SN-DU->>SN-CU-CP: a6. ACCESS SUCCESS + Note left of MN: 7. SN Status Transfer + MN->>SN-CU-CP: 7. SN Status Transfer + Note left of MN: 8. Data Forwarding + MN->>SN-CU-UP: 8. Data Forwarding + Note left of MN: Path Update procedure + MN->>SN-CU-CP: 9. PDU Session Modification Indication + SN-CU-CP->>SN-CU-UP: 9. PDU Session Modification Indication + Note left of SN-CU-UP: 10. Bearer Modification + SN-CU-UP->>UPF: 10. Bearer Modification + Note left of MN: 11. End Marker Packet + MN->>SN-CU-UP: 11. End Marker Packet + Note left of MN: 12. PDU Session Modification Confirmation + MN->>SN-CU-CP: 12. PDU Session Modification Confirmation + SN-CU-CP-->>SN-CU-UP: 12. PDU Session Modification Confirmation + +``` + +Sequence diagram for Conditional Secondary Node Addition procedure. Lifelines: UE, MN, SN-CU-CP, SN-CU-UP, SN-DU, Other potential SN, UPF, AMF. The procedure involves SN Addition Request, Bearer Context Setup, RRC reconfiguration, Random Access Procedure, SN Status Transfer, Data Forwarding, and Path Update procedure. + +Figure 8.16.1-1 Conditional Secondary Node Addition procedure + +1-12. The steps 1-12 are as defined in TS 37.340 [12]. + +a1-a5. The steps a1-a5 are as defined in clause 8.9.2 and with conditional indications. + +a6. After Random Access procedure successfully performed at the candidate gNB-DU which becomes the target SN gNB-DU, the target gNB-DU sends a Downlink Data Delivery Status frame to inform the target gNB-CU-UP. The target gNB-DU also sends an ACCESS SUCCESS message to inform the target gNB-CU-CP of which cell the UE has successfully accessed. + +### 8.16.2 MN initiated conditional SN Change + +The procedure for MN initiated conditional SN Change refer to TS 37.340[12]. In case of split gNB architecture, the procedures between gNB-CU and gNB-DU and the procedures between gNB-CU-CP and gNB-CU-UP refer to 8.16.1. + +### 8.16.3 SN initiated conditional inter-SN Change + +The procedure for SN initiated conditional SN Change refer to TS 37.340[12]. In case of split gNB architecture, the procedures between gNB-CU and gNB-DU and the procedures between gNB-CU-CP and gNB-CU-UP refer to 8.16.1. + +## 8.17 IAB Inter-CU Topology Management + +### 8.17.1 IAB Inter-donor-DU Re-routing + +When an IAB-donor-DU is configured to support inter-donor-DU re-routing, the IAB-donor-DU may identify a re-routed UL IP packet based on the source IP address field of the UL packet, and forwards UL IP packets, whose source IP addresses are anchored at a peer IAB-donor-DU, to this peer IAB-donor-DU via a tunnel. The IAB-donor-DU and the peer IAB-donor-DU may be controlled by the same IAB-donor-CU or by two different IAB-donor-CUs. The inter-donor-DU tunnel may be a GTP-U tunnel. The configuration of the tunnel is up to implementation. At the IAB-donor- + +DU forwarding the UL IP packets, inter-donor-DU tunnelling may be restricted to only a subset of the IP addresses anchored at the peer IAB-donor-DU. For this purpose, the IAB-donor-CU configures the IAB-donor-DU for forwarding the UL IP packets with a list of TNL addresses and/or prefixes for which tunnelling should be permitted and TNL address filtering should be exempted. + +NOTE: Tunnel types other than GTP-U may be used for the inter-donor-DU tunnel, by implementation. + +### 8.17.2 IAB Inter-CU Topology Redundancy + +#### 8.17.2.1 IAB Inter-CU topological redundancy procedure + +The inter-CU topological redundancy procedure enables the establishment, modification and release of redundant paths in IAB-topologies underneath different IAB-donor-CUs. Since topological redundancy uses NR-DC for the IAB-MT, it is only supported for IAB-nodes operating in the SA mode. + +Figure 8.17.2.1-1 shows an example of the inter-CU topological redundancy procedure, where a second backhaul path is established for a dual-connecting IAB-node via a separate IAB-topology that is not controlled by the F1-terminating IAB-donor-CU. The dual-connecting IAB-DU retains the F1 connection with the F1-terminating IAB-donor-CU. Since the dual-connecting IAB-MT also maintains an RRC connection with the non-F1-terminating IAB-donor-CU, this procedure renders the dual-connecting IAB-node as a boundary IAB-node. + +![Sequence diagram of the IAB inter-CU topology redundancy procedure. The diagram shows the interaction between a UE, a Dual-connecting IAB-node, an F1-terminating IAB-donor-CU, a Non-F1-terminating IAB-donor-CU, and an NGC. It details the steps for establishing a second backhaul path and migrating the F1 connection.](9b9dc99e34bb68ec85598e9d4bfda777_img.jpg) + +The diagram illustrates the sequence of messages for the IAB inter-CU topology redundancy procedure. It is divided into two main parts: the initial state and the procedure steps. + +**Initial State:** At the top, two horizontal dashed green arrows represent 'Downlink user data' and 'Uplink user data' flowing from the UE through the Dual-connecting IAB-node. The downlink path splits: one part goes through the 'First path in F1-terminating IAB-donor-CU's topology' (consisting of 'First parent IAB-node', 'Intermediate-hop IAB-node on the first path', and 'First-path IAB-donor-DU') to the F1-terminating IAB-donor-CU; the other part goes through the 'Second path in Non-F1-terminating IAB-donor-CU's topology' (consisting of 'Second parent IAB-node', 'Intermediate-hop IAB-node on the second path', and 'Second-path IAB-donor-DU') to the Non-F1-terminating IAB-donor-CU. Both donor CUs then forward data to the NGC. + +**Procedure Steps:** + +- 1. NR-DC establishment procedure for the IAB-MT of the dual-connecting IAB-node:** A message from the Dual-connecting IAB-node to the F1-terminating IAB-donor-CU. +- 2. IAB TRANSPORT MIGRATION MANAGEMENT REQUEST:** A message from the F1-terminating IAB-donor-CU to the Non-F1-terminating IAB-donor-CU. +- 3. DL RRC MESSAGE TRANSFER (RRCReconfiguration):** A message from the Non-F1-terminating IAB-donor-CU to the F1-terminating IAB-donor-CU. +- 4. RRCReconfiguration:** A message from the F1-terminating IAB-donor-CU to the Dual-connecting IAB-node. +- 5. RRCReconfigurationComplete:** A message from the Dual-connecting IAB-node to the F1-terminating IAB-donor-CU. +- 6. UL RRC MESSAGE TRANSFER (RRCReconfigurationComplete):** A message from the F1-terminating IAB-donor-CU to the Non-F1-terminating IAB-donor-CU. +- 7. Configuration or modification of BH RLC channel, BAP route and mapping rules along target path between dual-connecting IAB-node and second-path IAB-donor-DU via second parent IAB-node:** A message from the Non-F1-terminating IAB-donor-CU to the F1-terminating IAB-donor-CU. +- 8. IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE:** A message from the F1-terminating IAB-donor-CU to the Non-F1-terminating IAB-donor-CU. +- 9. Redirection of dual-connecting IAB-node-DU's F1 to second path and reporting of new F1-U TNL info to F1-terminating IAB-donor-CU:** A message from the Non-F1-terminating IAB-donor-CU to the F1-terminating IAB-donor-CU. +- 10. IAB TRANSPORT MIGRATION MANAGEMENT REQUEST:** A message from the F1-terminating IAB-donor-CU to the Non-F1-terminating IAB-donor-CU. +- 11. IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE:** A message from the Non-F1-terminating IAB-donor-CU to the F1-terminating IAB-donor-CU. +- 12. Repeat steps above as needed:** A final block indicating the procedure can repeat. + +**Final State:** At the bottom, the user data paths are shown again. The downlink user data now flows from the UE through the Dual-connecting IAB-node, then through the second path (Second parent IAB-node, Intermediate-hop IAB-node on the second path, Second-path IAB-donor-DU) to the Non-F1-terminating IAB-donor-CU, and finally to the NGC. The uplink user data flows from the NGC through the Non-F1-terminating IAB-donor-CU, then through the second path back to the Dual-connecting IAB-node, and finally to the UE. + +Sequence diagram of the IAB inter-CU topology redundancy procedure. The diagram shows the interaction between a UE, a Dual-connecting IAB-node, an F1-terminating IAB-donor-CU, a Non-F1-terminating IAB-donor-CU, and an NGC. It details the steps for establishing a second backhaul path and migrating the F1 connection. + +Figure 8.17.2.1-1 IAB inter-CU topology redundancy procedure + +1. The NR-DC establishment procedure is performed for the IAB-MT of the dual-connecting IAB-node as described in TS 37.340 [12], clause 10.2. This procedure can be conducted before or after establishment of the F1 interface between the IAB-DU and an IAB-donor-CU. +2. The F1-terminating IAB-donor-CU sends an IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message to the non-F1-terminating IAB-donor-CU to provide the context of the traffic to be offloaded. +3. The non-F1-terminating IAB-donor-CU sends a DL RRC MESSAGE TRANSFER message to the second parent IAB-DU, which includes an *RRCReconfiguration* message for the dual-connecting IAB-MT. The RRC configuration includes a BAP address for the boundary node, pertaining to the non-F1-terminating IAB-donor-CU's topology. The RRC configuration may include new TNL address(es) for the dual-connecting IAB-node, anchored at the second-path, i.e., at the IAB-donor-DU under the non-F1-terminating IAB-donor-CU. In case IPsec tunnel mode is used to protect the F1 and non-F1 traffic, the new TNL address refers to the outer IP address. +4. The second parent IAB-DU forwards the received *RRCReconfiguration* message to the dual-connecting IAB-MT. +5. The dual-connecting IAB-MT responds to the second parent IAB-DU with an *RRCReconfigurationComplete* message. +6. The second parent IAB-DU sends an UL RRC MESSAGE TRANSFER message to the non-F1-terminating IAB-donor-CU, to convey the received *RRCReconfigurationComplete* message. +7. The non-F1-terminating IAB-donor-CU may configure or modify BH RLC channels and BAP-sublayer routing entries on the second path between the dual-connecting IAB-node and the second-path IAB-donor-DU, as well as DL mappings on the second-path IAB-donor-DU for the dual-connecting IAB-node's second path. The DL mappings may be based on the TNL address(es) allocated to the dual-connecting IAB-node in step 3. These configurations may support the transport of UP and non-UP traffic on the second path. +8. The non-F1-terminating IAB-donor-CU responds with an IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE message to the F1-terminating IAB-donor-CU, to provide the mapping information for the traffic to be offloaded as indicated in step 2. The message includes the L2 info necessary to configure the dual-connecting IAB-node with the UL mappings for this traffic. The message includes the DSCP/IPv6 Flow Label values to be used for the DL traffic to be offloaded. +9. The F1-terminating IAB-donor-CU updates the boundary node with the UL BH information received from the non-F1-terminating IAB-donor-CU in Step 8 for the traffic to be offloaded. This step may also update UL FTEID and DL FTEID associated with individual GTP-tunnel(s). The affected GTP tunnel(s) will be switched to use the dual-connecting IAB-node's new TNL address(es). This step may use non-UE associated signaling in E1 and/or F1 interface to provide updated UP configuration for F1-U tunnels of multiple connected UEs or child IAB-MTs. Implementation must ensure the avoidance of potential race conditions, i.e., that no conflicting configurations are concurrently performed using UE-associated and non-UE-associated procedures. + +The F1-terminating IAB-donor-CU may also provide UL BH information associated with non-UP traffic. New TNL addresses for F1-C traffic configured in step 3, if any, can be added to the dual-connecting IAB-DU's F1-C association(s) with the F1-terminating IAB-donor-CU. + +If new TNL addresses for F1-C traffic are configured, new SCTP association(s) between the dual-connecting IAB-node and the F1-terminating IAB-donor-CU may be established using the new TNL address information of the dual-connecting IAB-node. The dual-connecting IAB-node sends an F1AP gNB-DU CONFIGURATION UPDATE message to the F1-terminating IAB-donor-CU, which may include new (outer) IP addresses and corresponding new (inner) IP address for offloaded F1-U traffic. + +NOTE: The IP address selected by the boundary IAB-node for a traffic needs to be anchored at the IAB-donor-DU whose BAP address is contained in the BAP routing ID of the UL mapping for this traffic, and configured by the IAB-donor (MN/SN) of the egress topology of the traffic. + +10. The F1-terminating IAB-donor-CU sends an IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message to the non-F1-terminating IAB-donor-CU, to modify the context of the dual-connecting IAB-node's offloaded traffic. The message may include the DL TNL address information used for the offloaded traffic and reported by the boundary node in step 9. The non-F1-terminating IAB-donor-CU may use this information to configure DL mappings on the second-path IAB-donor-DU. + +11. The non-F1-terminating IAB-donor-CU responds with an IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE message to the F1-terminating IAB-donor-CU. +12. The steps above, may be repeated, except step 1, if needed, for the F1-terminating IAB-donor-CU to request addition, modification, or release of the offloaded traffic. The non-F1-terminating IAB-donor-CU can fully or partially reject the addition or modification requested by the F1-terminating IAB-donor-CU. + +The non-F1-terminating IAB-donor-CU may request the modification of the L2 transport for the offloaded traffic in the non-F1-terminating IAB-donor-CU's topology using the IAB TRANSPORT MIGRATION MODIFICATION REQUEST message. The F1-terminating IAB-donor-CU reconfigures UL BH mappings accordingly and acknowledges the modification via the IAB TRANSPORT MIGRATION MODIFICATION RESPONSE message. The non-F1-terminating IAB-donor-CU may further reconfigure the TNL addresses of the dual-connecting IAB-node via RRC. + +The traffic offload for descendant nodes follows the same procedure as defined for the partial migration in clause 8.17.3.2. + +The F1-terminating IAB-donor-CU may request full or partial release of the offloaded traffic from the non-F1-terminating IAB-donor-CU by initiating the IAB Transport Migration Management procedure towards the non-F1-terminating IAB-donor-CU (e.g., for the purpose of revoking, or in case UE bearers are released). + +The traffic offload for the dual-connecting IAB-node and the descendent nodes can be partially or fully revoked, resulting in the return of the offloaded traffic back to the F1-terminating IAB-donor-CU's topology. Full or partial traffic revoking can be initiated by the F1-terminating IAB-donor-CU by initiating the IAB Transport Migration Management procedure towards the non-F1-terminating IAB-donor-CU. The non-F1-terminating IAB-donor-CU can request partial or full revoking of traffic offload from the F1-terminating IAB-donor-CU by initiating the IAB Transport Migration Modification procedure towards the F1-terminating IAB-donor-CU. + +## 8.17.3 IAB Inter-CU Topology Adaptation + +### 8.17.3.1 IAB inter-CU topology adaptation procedure + +During the inter-CU topology adaptation for a single-connected IAB-node, the IAB-MT migrates from an old parent node to a new parent node, where the old and the new parent nodes are served by different IAB-donor-CUs. Without loss of generality, the old parent node is referred to as source parent node, and the new parent node is referred to as target parent node. + +Figure 8.17.3.1-1 shows an example of the topology adaptation procedure, where the IAB-MT is migrated from a source IAB-donor-CU to a target IAB-donor-CU. In this procedure, the migrating IAB-node becomes a boundary IAB-node since its IAB-DU retains F1AP with the source IAB-donor-CU while its IAB-MT obtains RRC connectivity with the target IAB-donor-CU. + +![Sequence diagram of IAB inter-CU topology adaptation procedure. The diagram shows two phases: Phase 1 (IAB-MT migration) and Phase 2 (F1 transport migration). It involves a UE, a Migrating IAB node, Source Path (Source Parent IAB-node, Intermediate hop IAB-node, Source IAB-donor-DU), Source IAB-donor-CU, Target Path (Target Parent IAB-node, Intermediate hop IAB-node, Target IAB-donor-DU), Target IAB-donor-CU, and NGC. The procedure includes signaling messages like HANDOVER REQUEST, UE CONTEXT SETUP REQUEST, RRCReconfiguration, and IAB TRANSPORT MIGRATION MANAGEMENT REQUEST, as well as data flow adjustments for downlink and uplink user data.](ba676d18b6a00f27c5bfaec9eeec20be_img.jpg) + +The diagram illustrates the IAB inter-CU topology adaptation procedure, divided into two main phases: + +- Phase 1: IAB-MT migration** (Steps 1-12): + - The Source IAB-donor-CU sends a **1. HANDOVER REQUEST** to the Target IAB-donor-CU. + - The Target IAB-donor-CU sends a **2. UE CONTEXT SETUP REQUEST** to the Target Parent IAB-node. + - The Target Parent IAB-node sends a **3. UE CONTEXT SETUP RESPONSE** to the Target IAB-donor-CU. + - The Target IAB-donor-CU sends a **4. HANDOVER REQUEST ACKNOWLEDGE (RRRCReconfiguration)** to the Source IAB-donor-CU. + - The Source IAB-donor-CU sends a **5. UE CONTEXT MODIFICATION REQUEST (RRRCReconfiguration)** to the Source Parent IAB-node. + - The Source Parent IAB-node sends a **6. RRRCReconfiguration** to the Migrating IAB node. + - The Migrating IAB node sends a **7. UE CONTEXT MODIFICATION RESPONSE** to the Source IAB-donor-CU. + - The Source IAB-donor-CU initiates a **8. Random Access Procedure** with the Migrating IAB node. + - The Migrating IAB node sends a **9. RRRCReconfigurationComplete** to the Source IAB-donor-CU. + - The Source IAB-donor-CU sends a **10. UL RRC MESSAGE TRANSFER (RRRCReconfigurationComplete)** to the Target IAB-donor-CU. + - The Target IAB-donor-CU initiates a **11. Path Switch Procedure** with the NGC. + - The Target IAB-donor-CU sends a **12. UE CONTEXT RELEASE** to the Source IAB-donor-CU. +- Step 13:** Release of BAP route along source path between migrating IAB-node and source IAB-donor-DU via source parent IAB-node. +- Phase 2: F1 transport migration** (Steps 14-20): + - 14. Configuration of BH RLC channel, BAP route and mapping rules along target path** between migrating IAB-node and target IAB-donor-DU via target parent IAB-node. + - 15. Redirection of migrating IAB-node-DU's F1-C to target path and reporting of new F1-U TNL info to source IAB-donor-CU**. + - The Source IAB-donor-CU sends a **16. IAB TRANSPORT MIGRATION MANAGEMENT REQUEST** to the Target IAB-donor-CU. + - 17. Configuration or modification of BH RLC channel, BAP route and mapping rules along target path** between migrating IAB-node and target IAB-donor-DU via target parent IAB-node. + - The Target IAB-donor-CU sends a **18. IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE** to the Source IAB-donor-CU. + - 19. Redirection of migrating IAB-node-DU's F1-U to target path and update of BAP mapping configuration**. + - 20. Repeat steps 16-19 as needed**. + +Data flows are indicated by green dashed arrows: + + +- Downlink user data:** Flows from the NGC, through the Target IAB-donor-CU and Target Path, to the Migrating IAB node, and finally to the UE. +- Uplink user data:** Flows from the UE, through the Migrating IAB node and Source Path, to the Source IAB-donor-CU, and finally to the NGC. + +Sequence diagram of IAB inter-CU topology adaptation procedure. The diagram shows two phases: Phase 1 (IAB-MT migration) and Phase 2 (F1 transport migration). It involves a UE, a Migrating IAB node, Source Path (Source Parent IAB-node, Intermediate hop IAB-node, Source IAB-donor-DU), Source IAB-donor-CU, Target Path (Target Parent IAB-node, Intermediate hop IAB-node, Target IAB-donor-DU), Target IAB-donor-CU, and NGC. The procedure includes signaling messages like HANDOVER REQUEST, UE CONTEXT SETUP REQUEST, RRCReconfiguration, and IAB TRANSPORT MIGRATION MANAGEMENT REQUEST, as well as data flow adjustments for downlink and uplink user data. + +**Figure 8.17.3.1-1: IAB inter-CU topology adaptation procedure** + +- The source IAB-donor-CU sends an Xn HANDOVER REQUEST message to the target IAB-donor-CU . This message may include the migrating IAB-node's TNL address information in the RRC container. +- The target IAB-donor-CU sends a UE CONTEXT SETUP REQUEST message to the target parent node IAB-DU, to create the UE context for the migrating IAB-MT and to set up the bearers, which the migrating IAB-MT uses for its signaling, and, optionally, data traffic. + +3. The target parent node IAB-DU responds to the target IAB-donor-CU with a UE CONTEXT SETUP RESPONSE message. +4. The target IAB-donor-CU performs admission control and provides the new RRC configuration as part of the HANDOVER REQUEST ACKNOWLEDGE message. The RRC configuration includes a BAP address for the boundary node in the target IAB-donor-CU's topology, a default BH RLC channel and a default BAP routing ID configuration for UL F1-C/non-F1 traffic mapping on the target path. The RRC configuration may include the new TNL address(es) anchored at the target IAB-donor-DU for the migrating node. +5. The source IAB-donor-CU sends a UE CONTEXT MODIFICATION REQUEST message to the source parent node IAB-DU, which includes the received *RRCReconfiguration* message from the target IAB-donor-CU. +6. The source parent node IAB-DU forwards the received *RRCReconfiguration* message to the migrating IAB-MT. +7. The source parent node IAB-DU responds to the source IAB-donor-CU with the UE CONTEXT MODIFICATION RESPONSE message. +8. The migrating IAB-MT performs a random access procedure at the target parent node IAB-DU. +9. The migrating IAB-MT responds to the target parent node IAB-DU with an *RRCReconfigurationComplete* message. +10. The target parent node IAB-DU sends an UL RRC MESSAGE TRANSFER message to the target IAB-donor-CU, to convey the received *RRCReconfigurationComplete* message. +11. The target IAB-donor-CU triggers the path switch procedure for the migrating IAB-MT, if needed. +12. The target IAB-donor-CU sends UE CONTEXT RELEASE message to the source IAB-donor-CU. + +NOTE: The XnAP UE IDs of the migrating node are retained at target and source IAB-donor-CU as long as the target path is used for transport of traffic between the migrating node and the source IAB-donor-CU. + +13. The source IAB-donor-CU may release BH RLC channels and BAP-sublayer routing entries on the source path between source parent IAB-node of the migrating IAB-node and the source IAB-donor-DU. +14. The target IAB-donor-CU configures BH RLC channels and BAP-sublayer routing entries on the target path between the migrating IAB-node and target IAB-donor-DU, as well as DL mappings on the target IAB-donor-DU for the migrating IAB-node's target path. These configurations support the transport of F1-C traffic on the target path. +15. The F1-C connection between the migrating IAB-node and the source IAB-donor-CU are switched to the target path using the new TNL address information of the migrating IAB-node. The migrating IAB-node may report the new TNL address information it wants to use for F1-U traffic to the source IAB-donor-CU, via the gNB-DU CONFIGURATION UPDATE message. + +In case IPsec tunnel mode is used for TNL protection, the migrating IAB-node may use MOBIKE (IETF RFC 4555 [29]) to migrate the IPsec tunnel to the new IP outer addresses. After the completion of the MOBIKE procedure, the migrating IAB-DU initiates an F1AP gNB-DU Configuration Update procedure from which the IAB-donor-CU can conclude whether the existing inner IP address(es) (e.g., for SCTP association) and the DL F-TEID can be reused. + +If new TNL addresses for F1-C traffic are configured, new SCTP association(s) between the migrating IAB-node and the F1-terminating IAB-donor-CU may be established using the new TNL address information of the migrating IAB-node. The migrating IAB-node sends an F1AP gNB-DU CONFIGURATION UPDATE message to the F1-terminating IAB-donor-CU, which may include new (outer) IP addresses and corresponding new (inner) IP address for the F1-U traffic to be switched to the target path. + +16. The source IAB-donor-CU sends an IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message to the target IAB-donor-CU, to provide the context of the traffic to be offloaded. The message may include the new DL TNL address information necessary for the target IAB-donor-CU to configure or modify DL mappings on the target IAB-donor-DU. +17. The target IAB-donor-CU may configure or modify BH RLC channels and BAP-sublayer routing entries on the target path between the migrating IAB-node and target IAB-donor-DU, as well as DL mappings on the target + +IAB-donor-DU for the migrating IAB-node's target path. These configurations may support the transport of UP and non-UP traffic on the target path. + +18. The target IAB-donor-CU responds to the source IAB-donor-CU with an IAB Transport Migration Management Response message, to provide the mapping information for the traffic to be offloaded. The message includes the L2 info that is used in the target IAB-donor-CU's topology and necessary to configure the migrating IAB-node with the UL mappings of traffic indicated in step 16. The message includes the DSCP/IPv6 Flow Label values used to configure the DL mappings of traffic indicated in step 16. +19. The F1-U connections of the migrating IAB-node with the source IAB-donor-CU are switched to use the migrating IAB-node's new TNL address(es). The source IAB-donor-CU provides to the IAB-DU of the migrating IAB-node the updated UL BH information for the traffic indicated in step 16, based on the UL BH information received from the target IAB-donor-CU in step 18. The source IAB-donor-CU may also update the UL BH information associated with non-UP traffic. This step may use UE associated signaling or non-UE associated signaling in E1 and/or F1 interface. Implementation must ensure the avoidance of potential race conditions, i.e., that no conflicting configurations are concurrently performed using UE-associated and non-UE-associated procedures. +20. The steps 16 to 19 may be repeated, if needed, where the source IAB-donor-CU can request the offload of further traffic, or the modification or release of offloaded traffic. The target IAB-donor-CU can fully or partially reject addition or modification requests by the source IAB-donor-CU. + +The target IAB-donor-CU may request the modification of the L2 transport for the offloaded traffic in the target IAB-donor-CU's topology using the IAB TRANSPORT MIGRATION MODIFICATION REQUEST message. The source IAB-donor-CU reconfigures the UL BH mappings accordingly, and acknowledges the modification via the IAB TRANSPORT MIGRATION MODIFICATION RESPONSE message. The target IAB-donor-CU may further reconfigure the TNL addresses of the migrating IAB-node via RRC. + +The traffic offload through the inter-CU topology adaptation procedure for the migrating IAB-node can be fully revoked. + +The non-F1-terminating IAB-donor-CU can initiate the full revoking of traffic offload by executing the XnAP Handover Preparation procedure for the migrating IAB-MT. After the migrating IAB-MT is handed over in reverse direction, i.e., from the non-F1-terminating IAB-donor-CU to the F1-terminating IAB-donor-CU, the traffic of the migrating IAB-node's IAB-DU is routed again along the former source path. + +The F1-terminating IAB-donor-CU can initiate the full revoking of traffic offload by requesting the release of all offloaded traffic from the non-F1-terminating IAB-donor-CU by sending the IAB TRANSPORT MIGRATION MANAGEMENT REQUEST to the non-F1-terminating IAB-donor-CU. This message may trigger the XnAP Handover Preparation procedure for the migrating IAB-MT towards the F1-terminating IAB-donor-CU. + +The F1-terminating IAB-donor-CU may request full or partial release of the offloaded traffic from the non-F1-terminating IAB-donor-CU via the IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message. + +### 8.17.3.2 IAB inter-CU topology adaptation procedure with descendant IAB-node + +Figure 8.17.3.2-1 shows an example of the topology adaptation procedure where the migrating IAB-MT is migrated from a source IAB-donor-CU to a target IAB-donor-CU, and where the migrating IAB-node has a descendant IAB-node which retains both its RRC connection and F1 connection with the source IAB-donor-CU. + +![Sequence diagram of IAB inter-CU topology adaptation procedure with descendant IAB-node. The diagram shows interactions between UE, Descendant IAB-node, Migrating IAB-node, Source path (Source parent IAB-node, Intermediate hop IAB-node on the source path, Source IAB-donor-DU), Source IAB-donor-CU, Target path (Target parent IAB-node, Intermediate hop IAB-node on the target path, Target IAB-donor-DU), Target IAB-donor-CU, and NGC.](9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg) + +The diagram illustrates the following steps for IAB inter-CU topology adaptation: + +0. Topology adaptation procedure of Section 8.17.3.1 +1. IAB TRANSPORT MIGRATION MANAGEMENT REQUEST (from Source IAB-donor-CU to Target IAB-donor-CU) +2. Configuration or modification of BH RLC channel, BAP route and mapping rules along target path between migrating IAB-node and target IAB-donor-DU via target parent IAB-node. +3. IAB TNL Address Allocation (between Target IAB-donor-CU and Target IAB-donor-DU) +4. IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE (from Target IAB-donor-CU to Source IAB-donor-CU) +5. BAP Mapping Configuration (from Source IAB-donor-CU to Migrating IAB-node) +6. DL RRC MESSAGE TRANSFER (RRCReconfiguration) (from Source IAB-donor-CU to Migrating IAB-node) +7. RRCReconfiguration (from Migrating IAB-node to Descendant IAB-node) +8. RRCReconfigurationComplete (from Descendant IAB-node to Migrating IAB-node) +9. UL RRC MESSAGE TRANSFER (RRCReconfigurationComplete) (from Migrating IAB-node to Source IAB-donor-CU) +10. Configuration of UL BH mappings and BAP routing entries (at Migrating IAB-node) +11. Redirection of descendant IAB-node-DU's F1 to target path and reporting of new F1-U TNL info to source IAB-donor-CU +12. IAB TRANSPORT MIGRATION MANAGEMENT REQUEST (from Source IAB-donor-CU to Target IAB-donor-CU) +13. IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE (from Target IAB-donor-CU to Source IAB-donor-CU) +14. Repeat steps above as needed + +The diagram also shows initial and final states of Downlink user data and Uplink user data paths across the nodes. + +Sequence diagram of IAB inter-CU topology adaptation procedure with descendant IAB-node. The diagram shows interactions between UE, Descendant IAB-node, Migrating IAB-node, Source path (Source parent IAB-node, Intermediate hop IAB-node on the source path, Source IAB-donor-DU), Source IAB-donor-CU, Target path (Target parent IAB-node, Intermediate hop IAB-node on the target path, Target IAB-donor-DU), Target IAB-donor-CU, and NGC. + +**Figure 8.17.3.2-1: IAB inter-CU topology adaptation procedure with descendant IAB-node** + +0. The topology adaptation procedure of clause 8.17.3.1 is performed for the migrating IAB-node. +1. The source IAB-donor-CU sends an IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message to the target IAB-donor-CU to provide the context of the descendant IAB-node's traffic to be offloaded. The message may include a request for new TNL address(es) for the descendant IAB-node(s), anchored at a target IAB-donor-DU. The source IAB-donor-CU includes an identifier of the migrating IAB-node in the request message. This could be performed in parallel with step 0 after the source IAB-donor-CU receives HANDOVER REQUEST ACKNOWLEDGE message, e.g., the context of the traffic to be offloaded for the migrating/descendant nodes and IP address request information could be contained in the same IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message. +2. The target IAB-donor-CU determines the target IAB-donor-DU, based on the identifier of the migrating IAB-node. The target IAB-donor-CU may configure or modify BH RLC channels and BAP-sublayer routing entries on the target path between the boundary IAB-node and target IAB-donor-DU, as well as DL mappings on the target IAB-donor-DU for the migrating IAB-node's target path. These configurations may support the transport of UP and non-UP traffic on the target path. +3. The target IAB-donor-CU may obtain new TNL address(es) from the target IAB-donor-DU, based on the request for TNL address(es) received in step 1. +4. The target IAB-donor-CU responds with an IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE message to the source IAB-donor-CU, to provide the mapping information for the traffic to be offloaded. The message includes the L2 info from the target IAB-donor-CU topology that is necessary to configure the migrating IAB-node with the BAP-sublayer routing, header-rewriting and BH RLC CH mapping entries of traffic indicated in step 1. The message includes the DSCP/IPv6 Flow Label values to be used for the DL traffic to be offloaded as indicated in step 1. The message may include the new TNL address(es) obtained in step 3, if any. + +- NOTE 1: The target IAB-donor-CU should select the same IAB-donor-DU in its IAB topology for all to-be-offloaded traffic, whose UL BH mappings received from the source IAB-donor-CU in step 1 share the same BAP address. +- NOTE 2: The target IAB-donor-CU should provide the same Egress BAP Routing ID for all to-be-offloaded uplink traffic, whose UL BH mappings received from the source IAB-donor-CU in step 1 share the same Ingress BAP Routing ID. +5. The source IAB-donor-CU configures the migrating IAB-node's IAB-DU with the BAP-sublayer routing, header-rewriting and BH RLC CH mapping entries of the migrating IAB-node. + 6. The source IAB-donor-CU sends a DL RRC MESSAGE TRANSFER message to the descendant IAB-node's parent IAB-DU, which includes an *RRCReconfiguration* message for the descendant IAB-MT. The RRC configuration may include the new TNL addresses received in step 4. If needed, the source IAB-donor-CU may also provide a new default UL mapping which includes a default BH RLC channel and a default BAP Routing ID on the target path, to the descendant nodes via *RRCReconfiguration* message. + 7. The descendant IAB-node's parent IAB-DU forwards the received *RRCReconfiguration* message to the descendant IAB-MT. + 8. The descendant IAB-MT responds to the migrating IAB-node's IAB-DU with an *RRCReconfigurationComplete* message. + 9. The migrating IAB-node's IAB-DU sends an UL RRC MESSAGE TRANSFER message to the source IAB-donor-CU, to convey the received *RRCReconfigurationComplete* message. + 10. If needed, the source IAB-donor-CU configures UL BH mappings on the descendant node and BAP-sublayer routing entries between the descendant node and the migrating IAB-node. This step may be performed at an earlier stage, e.g., immediately after step 4. + 11. The F1-C connections and F1-U tunnels are switched to use the descendant IAB-node's new TNL address(es), if any, as described in Steps 15 and 19 of the inter-CU topology adaptation procedure in clause 8.17.3.1. +- NOTE: The IP address selected by the descendant IAB-node for an offloaded traffic needs to be anchored at the IAB-donor-DU whose BAP address is contained in the BAP routing ID of the UL mapping for this traffic, and obtained in step 7. +12. The source IAB-donor-CU sends an IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message to the target IAB-donor-CU, to modify the context of the descendant IAB-node's offloaded traffic. The message may include the DL TNL address information received in step 11 that is necessary for the target IAB-donor-CU to configure or modify DL mappings on the target IAB-donor-DU. + 13. The target IAB-donor-CU responds with an IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE message to the source IAB-donor-CU. + 14. The of steps above may be repeated, if needed, for the source IAB-donor-CU to request addition, modification or release of the offloaded traffic pertaining to the descendant IAB-node. The target IAB-donor-CU can fully or partially reject addition or modification requests by the source IAB-donor-CU. + +The target IAB-donor-CU may trigger the modification of the L2 transport of the offloaded traffic in the target IAB-donor-CU's topology using the IAB TRANSPORT MIGRATION MODIFICATION REQUEST message. Based on this message, the source IAB-donor-CU may reconfigure the UL BH mappings on the descendant nodes, the routing entries and BH RLC channel mappings on the migrating node and the descendant nodes, and the BAP header rewriting entries on the migrating node, and acknowledges the modification via the IAB TRANSPORT MIGRATION MODIFICATION RESPONSE message. The target IAB-donor-CU may further provide updated TNL address information for the descendant IAB-node to the source IAB-donor-CU. + +The full or partial release or revoking of traffic offload pertaining to the descendant IAB-nodes and their served UEs follows the same procedure as defined for the partial migration in clause 8.17.3.1. + +## 8.17.4 IAB Inter-CU Backhaul RLF recovery for single connected IAB-node + +The inter-CU backhaul RLF recovery procedure for IAB-nodes in SA mode enables recovery of an IAB-node to another parent node underneath a different IAB-donor-CU, when the IAB-MT of the IAB-node detects backhaul RLF. + +Figure 8.17.4-1 shows an example of the backhaul RLF recovery procedure for an IAB-node in SA mode. In this example, the IAB-node changes from its initial parent node to a new parent node, where the new parent node is served by a different IAB-donor-CU than that serving its initial parent node. In this procedure, the recovering IAB-node becomes a boundary IAB-node since the IAB-DU retains F1AP with the initial IAB-donor-CU while its IAB-MT obtains RRC connectivity with the new IAB-donor-CU. + +![Sequence diagram of IAB inter-CU backhaul RLF recovery procedure for an IAB-node in SA mode. The diagram shows two phases: Phase 1 (IAB-MT recovery) and Phase 2 (F1 transport migration). It involves interactions between UE, Recovering IAB node, Initial Path (Initial Parent IAB-node, Intermediate hop IAB-node, Initial IAB-donor-DU), Initial IAB-donor-CU, Recovery Path (New Parent IAB-node, Intermediate hop IAB-node, New IAB-donor-DU), New IAB-donor-CU, and NGC. The process includes RRC reestablishment, RRC reconfiguration, and path switch procedures.](276d5f4022bc6b9e4687f9ba4fc7594c_img.jpg) + +The diagram illustrates the sequence of messages for IAB inter-CU backhaul RLF recovery. It is divided into two main phases: + +- Phase 1: IAB-MT recovery** (Steps 1-12): + - 1. Determination of BH RLF on initial path + - 2. Random Access Procedure + - 3. RRCReestablishmentRequest + - 4. INITIAL UL RRC MESSAGE TRANSFER (RRCReestablishmentRequest) + - 5. Xn Retrieve UE Context procedure + - 6. DL RRC MESSAGE TRANSFER (RRCReestablishment) + - 7. RRCReestablishment + - 8. RRCReestablishmentComplete + - 9. UL RRC MESSAGE TRANSFER (RRCReestablishmentComplete) + - 10. UE Context Setup procedure + - 11. Path Switch Procedure + - 12. UE CONTEXT RELEASE +- Phase 2: F1 transport migration** (Steps 13-18): + - 13. Release of BAP route along source path between migrating IAB-node and source IAB-donor-DU via source parent IAB-node + - 14. DL RRC MESSAGE TRANSFER (RRCReconfiguration) + - 15. RRCReconfiguration + - 16. RRCReconfigurationComplete + - 17. UL RRC MESSAGE TRANSFER (RRCReconfigurationComplete) + - 18. Same as steps 14-20 of inter-CU topology adaptation procedure + +Downlink user data flows from NGC through the IAB-donor-CUs and IAB-donors to the UE. Uplink user data flows from the UE through the IAB-donors and IAB-donor-CUs to the NGC. During the recovery, user data is temporarily rerouted through the new path. + +Sequence diagram of IAB inter-CU backhaul RLF recovery procedure for an IAB-node in SA mode. The diagram shows two phases: Phase 1 (IAB-MT recovery) and Phase 2 (F1 transport migration). It involves interactions between UE, Recovering IAB node, Initial Path (Initial Parent IAB-node, Intermediate hop IAB-node, Initial IAB-donor-DU), Initial IAB-donor-CU, Recovery Path (New Parent IAB-node, Intermediate hop IAB-node, New IAB-donor-DU), New IAB-donor-CU, and NGC. The process includes RRC reestablishment, RRC reconfiguration, and path switch procedures. + +**Figure 8.17.4-1: IAB inter-CU backhaul RLF recovery procedure for an IAB-node in SA mode** + +1. The IAB-MT of the IAB-node detects backhaul RLF. +2. The IAB-MT attempts RLF recovery by performing Random Access towards a new parent IAB-DU. + +3. The IAB-MT undergoing RLF recovery sends an *RRCREestablishmentRequest* message to the new parent IAB-DU. +4. The new parent IAB-DU sends an INITIAL UL RRC MESSAGE to the new IAB-donor-CU, to convey the received *RRCREestablishmentRequest* message. +5. The new IAB-donor-CU retrieves the UE Context for the IAB-MT undergoing recovery, through the XnAP Retrieve UE Context procedure. The initial IAB-donor-CU may include the TNL address information of the IAB-node undergoing recovery in the RRC container of the RETRIEVE UE CONTEXT RESPONSE message. +6. The new IAB-donor-CU sends a DL RRC MESSAGE TRANSFER message to the new parent IAB-DU, to convey the generated *RRCREestablishment* message. +7. The new parent IAB-DU sends an *RRCREestablishment* message to the IAB-MT undergoing recovery. +8. The IAB-MT undergoing recovery sends an *RRCREestablishmentComplete* message to the new parent IAB-DU. +9. The new parent IAB-DU sends an UL RRC MESSAGE TRANSFER message to the new IAB-donor-CU, to convey the received *RRCREestablishmentComplete* message. +10. The new IAB-donor-CU triggers the UE Context Setup procedure toward the new parent IAB-DU, to create the UE context for the IAB-MT undergoing recovery and to set up one or more bearers. These bearers can be used by the IAB-MT undergoing recovery for its own signalling, and, optionally, data traffic. +11. The new IAB-donor-CU triggers the path switch procedure for the IAB-MT undergoing recovery, if needed. +12. The new IAB-donor-CU sends UE CONTEXT RELEASE message to the initial IAB-donor-CU. + +NOTE: The XnAP UE IDs of the boundary IAB-MT are retained at initial IAB-donor-CU and new IAB-donor-CU as long as the recovery path is used for transport of traffic between the IAB-node undergoing recovery and the initial IAB-donor-CU. + +13. The initial IAB-donor-CU may release the BH RLC channels and BAP-sublayer routing entries on the initial path between the initial parent IAB-node and the initial IAB-donor-DU. +14. The new IAB-donor-CU sends a DL RRC MESSAGE TRANSFER message to the new parent IAB-DU, which includes an *RRCREconfiguration* message for the IAB-MT undergoing recovery. The RRC configuration may include new TNL addresses anchored at the new IAB-donor-DU. The RRC configuration may further include a BAP address for the recovery IAB-node in the new IAB-donor-CU's topology, default BH RLC channel and a default BAP routing ID configuration for UL F1-C/non-F1 traffic mapping on the recovery path. +15. The new parent IAB-DU forwards the received *RRCREconfiguration* message to the IAB-MT undergoing recovery. +16. The IAB-MT undergoing recovery responds to the new parent IAB-DU with an *RRCREconfigurationComplete* message. +17. The new parent IAB-DU sends an UL RRC MESSAGE TRANSFER message to the new IAB-donor-CU, to convey the received *RRCREconfigurationComplete* message. +18. The remaining part of the procedure follows the steps 14-20 of the inter-CU topology adaptation procedure defined in clause 8.17.3.1. + +Traffic offload for descendant nodes follows the same procedure as that of clause 8.17.3.2. + +The new IAB-donor-CU may request the modification of the L2 transport of the offloaded traffic in the new IAB-donor-CU's topology. The new IAB-donor-CU may further reconfigure the TNL addresses of the boundary IAB-node via RRC. + +The traffic offload due to inter-CU RLF recovery procedure for the boundary IAB-node and its descendant IAB-nodes can be fully revoked. In this case, the boundary IAB-MT is handed over in reverse direction, i.e., from the new IAB-donor-CU to the initial IAB-donor-CU, and the traffic of the boundary IAB-DU and the descendant IAB-DUs is routed again along the initial path used prior to BH RLF recovery. + +The new IAB-donor-CU can initiate the full revoking of traffic offload by executing the XnAP Handover Preparation procedure for the boundary IAB-MT towards the initial IAB-donor-CU. + +The initial IAB-donor-CU can initiate the full revoking of traffic offload in the same manner as described in clause 8.17.3.1 for the revoking initiated by the F1-terminating IAB-donor-CU. + +The initial IAB-donor-CU may request full or partial release of the offloaded traffic from the new IAB-donor-CU via the IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message. + +## 8.18 Overall procedure for Small Data Transmission during RRC Inactive + +### 8.18.1 RACH based SDT + +The procedure for RACH based small data transmission in RRC Inactive is shown in Figure 8.18.1-1. + +![Sequence diagram for RACH based Small Data Transmission in RRC Inactive state. The diagram shows four participants: UE, gNB-DU, gNB-CU-CP, and gNB-CU-UP. The sequence of messages is: 1. UE sends RRCResumeRequest (+ UL SDT data and/or UL SDT signalling) to gNB-DU; 2. gNB-DU buffers the data/signalling; 3. gNB-DU sends INITIAL UL RRC MESSAGE TRANSFER (SDT indication, assistance information) to gNB-CU-CP; 4. gNB-CU-CP sends UE CONTEXT SETUP REQUEST (UL TEIDs) to gNB-DU; 5. gNB-DU sends UE CONTEXT SETUP RESPONSE (DL TEIDs) to gNB-CU-CP; 6. gNB-CU-CP sends BEARER CONTEXT MODIFICATION REQUEST (SDT DRB resume, DL TEIDs) to gNB-CU-UP; 7. gNB-CU-UP sends BEARER CONTEXT MODIFICATION RESPONSE to gNB-CU-CP.](ad4da36431850ac19ba59bb74ec29dc9_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB-DU + participant gNB-CU-CP + participant gNB-CU-UP + Note left of gNB-DU: 2. Buffer UL data/signalling + UE->>gNB-DU: 1. RRCResumeRequest ++ UL SDT data and/or UL SDT signalling + gNB-DU->>gNB-CU-CP: 3. INITIAL UL RRC MESSAGE TRANSFER +(SDT indication, assistance information) + gNB-CU-CP->>gNB-DU: 4. UE CONTEXT SETUP REQUEST (UL TEIDs) + gNB-DU->>gNB-CU-CP: 5. UE CONTEXT SETUP RESPONSE (DL TEIDs) + gNB-CU-CP->>gNB-CU-UP: 6. BEARER CONTEXT MODIFICATION REQUEST +(SDT DRB resume, DL TEIDs) + gNB-CU-UP->>gNB-CU-CP: 7. BEARER CONTEXT MODIFICATION RESPONSE + +``` + +Sequence diagram for RACH based Small Data Transmission in RRC Inactive state. The diagram shows four participants: UE, gNB-DU, gNB-CU-CP, and gNB-CU-UP. The sequence of messages is: 1. UE sends RRCResumeRequest (+ UL SDT data and/or UL SDT signalling) to gNB-DU; 2. gNB-DU buffers the data/signalling; 3. gNB-DU sends INITIAL UL RRC MESSAGE TRANSFER (SDT indication, assistance information) to gNB-CU-CP; 4. gNB-CU-CP sends UE CONTEXT SETUP REQUEST (UL TEIDs) to gNB-DU; 5. gNB-DU sends UE CONTEXT SETUP RESPONSE (DL TEIDs) to gNB-CU-CP; 6. gNB-CU-CP sends BEARER CONTEXT MODIFICATION REQUEST (SDT DRB resume, DL TEIDs) to gNB-CU-UP; 7. gNB-CU-UP sends BEARER CONTEXT MODIFICATION RESPONSE to gNB-CU-CP. + +**Figure 8.18.1-1: RACH based Small Data Transmission in RRC Inactive state.** + +1. The UE in RRC Inactive sends the *RRCResumeRequest* message together with UL SDT data and/or UL SDT signalling. +2. The gNB-DU buffers the UL SDT data and/or UL SDT signalling. +3. The step 3 is as defined in step 4 in clause 8.6.2, including an indication of SDT access. The gNB-DU may also provide SDT assistance information. +- 4-5. If UE context is successfully retrieved as specified in TS 38.300 [2], the steps 4-5 are as defined in steps 6-7 in clause 8.9.6.2. The UL SDT data, if any, is forwarded to the gNB-CU-UP, and the UL signalling, if any, is forwarded to the gNB-CU-CP via the UL RRC MESSAGE TRANSFER message, in which any UL NAS PDU is delivered to AMF. + +NOTE 1: In case that full UE context is retrieved from another gNB-CU-CP as specified in TS 38.300 [2], the gNB-CU-CP first establishes the UE context in the gNB-CU-UP via the Bearer Context Setup procedure and F1-U UL TEIDs are retrieved before step 4. The BEARER CONTEXT SETUP REQUEST message may include an indication to suspend non-SDT bearers, and in this case, the BEARER CONTEXT MODIFICATION REQUEST message in step 6 does not include resume indication for SDT DRBs. + +NOTE 2: In case that only partial UE context for SDT including F1-U UL TEIDs is retrieved from another gNB-CU-CP as specified in TS 38.300 [2], the gNB-CU-CP uses those F1-U UL TEIDs for steps 4-5, and the subsequent steps 6-7 are not executed. The F1-U DL TEIDs received from the gNB-DU in step 5 should be forwarded to the other gNB-CU-CP, to be used for transferring of the DL SDT data. In addition, the UL SDT data, if any, is forwarded from the gNB-DU to the gNB-CU-UP of the other gNB-CU-CP for which the partial context is retrieved, and the UL signalling, if any, is forwarded from the gNB-CU-CP to the other gNB-CU-CP (the last serving gNB-CU-CP) via the XnAP RRC TRANSFER message. + +NOTE 3: The other gNB-CU-UP may need to buffer the UL SDT data if received before the SDT bearer(s) are resumed. + +6. The gNB-CU-CP sends the BEARER CONTEXT MODIFICATION REQUEST message including an resume indication for SDT DRBs. The gNB-CU-CP also includes the F1-U DL TEIDs received from the gNB-DU in step 5. + +7. The gNB-CU-UP responds with the BEARER CONTEXT MODIFICATION RESPONSE message. + +NOTE 4: void. + +Upon receiving the UE INACTIVITY NOTIFICATION message without SDT volume threshold crossed indication from the gNB-DU, the gNB-CU, if serving the UE and deciding to terminate the ongoing SDT procedure, shall transmit the UE CONTEXT RELEASE COMMAND message to the gNB-DU. + +If CG-SDT is (re-)configured, the gNB-CU may request the gNB-DU to keep CG-SDT configuration and resources in the UE CONTEXT RELEASE COMMAND message. + +NOTE 5: Upon receiving BSR from the UE, in case that UL SDT data size in the BSR is larger than the threshold configured from the gNB-CU-CP, the gNB-DU sends the UE INACTIVITY NOTIFICATION message with the SDT volume threshold crossed indication to the gNB-CU-CP. Upon receiving such indication, the gNB-CU-CP may terminate the ongoing SDT procedure, by sending the *RRResume* message to move the UE to RRC\_CONNECTED, or by sending the *RRRelease* message to move the UE to RRC\_INACTIVE. + +Upon receiving non-SDT data, the gNB-CU-UP shall send the DL DATA NOTIFICATION message to the gNB-CU-CP. The gNB-CU-CP shall terminate the ongoing SDT procedure as specified in TS 38.300 [2]. + +If the amount of the received DL SDT data is above the data size threshold configured by the gNB-CU-CP, the gNB-CU-UP shall send the DL DATA NOTIFICATION message with the SDT data size threshold crossed indication. The gNB-CU-CP may terminate the ongoing SDT procedure. + +## 8.18.2 CG based SDT + +The procedure for CG based small data transmission in RRC Inactive is shown in Figure 8.18.2-1. + +![Sequence diagram for CG based Small Data Transmission in RRC Inactive state. The diagram shows the interaction between UE, gNB-DU, gNB-CU-CP, and gNB-CU-UP. The process starts with the gNB-CU-CP deciding to move the UE into RRC_inactive mode. It then sends a UE CONTEXT MODIFICATION REQUEST to the gNB-DU, which responds with UE CONTEXT MODIFICATION RESPONSE. The gNB-CU-CP then sends a BEARER CONTEXT MODIFICATION REQUEST to the gNB-CU-UP, which responds with BEARER CONTEXT MODIFICATION RESPONSE. The gNB-CU-CP then sends a UE CONTEXT RELEASE COMMAND to the gNB-DU, which responds with UE CONTEXT RELEASE COMPLETE. The gNB-DU then sends an RRCRelease message to the UE. After a period of time in RRC_inactive mode, the UE sends an RRCResumeRequest with UL SDT data and/or UL SDT signalling to the gNB-DU. The gNB-DU then sends an UL RRC MESSAGE TRANSFER (RRResumeRequest) to the gNB-CU-CP. The gNB-CU-CP then sends a BEARER CONTEXT MODIFICATION REQUEST to the gNB-CU-UP, which responds with BEARER CONTEXT MODIFICATION RESPONSE. The gNB-CU-CP then sends a UL SDT Data message to the gNB-CU-UP. The gNB-CU-UP then sends a UL RRC MESSAGE TRANSFER (UL SDT Signalling) to the gNB-DU. Finally, the gNB-DU sends a Subsequent SDT Data transmission message to the UE.](fe4f9338148fd891afbd3e301f9bad33_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB-DU + participant gNB-CU-CP + participant gNB-CU-UP + + Note right of gNB-CU-CP: 1.gNB-CU-CP decides to move UE into RRC_inactive + gNB-CU-CP->>gNB-DU: 2.UE CONTEXT MODIFICATION REQUEST (CG-SDT query indicator) + gNB-DU-->>gNB-CU-CP: 3.UE CONTEXT MODIFICATION RESPONSE (CG-SDT lower layer resource) + gNB-CU-CP->>gNB-CU-UP: 4.BEARER CONTEXT MODIFICATION REQUEST (with suspend indication) + gNB-CU-UP-->>gNB-CU-CP: 5.BEARER CONTEXT MODIFICATION RESPONSE + gNB-CU-CP->>gNB-DU: 6.UE CONTEXT RELEASE COMMAND (CG-SDT kept indicator, RRRelease) + gNB-DU-->>gNB-CU-CP: 8.UE CONTEXT RELEASE COMPLETE + gNB-DU->>UE: 7. RRRelease (suspend indication, CG-SDT config) + + Note over UE, gNB-CU-UP: After a period of time of UE being in RRC_inactive mode + UE->>gNB-DU: 9. RRResumeRequest + UL SDT data and/or UL SDT signalling + gNB-DU->>gNB-CU-CP: 10.UL RRC MESSAGE TRANSFER (RRResumeRequest) + gNB-CU-CP->>gNB-CU-UP: 11.BEARER CONTEXT MODIFICATION REQUEST (SDT DRB resume) + gNB-CU-UP-->>gNB-CU-CP: 12.BEARER CONTEXT MODIFICATION RESPONSE + gNB-CU-CP-->>gNB-CU-UP: 13.UL SDT Data + gNB-CU-CP-->>gNB-DU: 13a.UL RRC MESSAGE TRANSFER (UL SDT Signalling) + Note over UE, gNB-CU-UP: Subsequent SDT Data transmission + +``` + +Sequence diagram for CG based Small Data Transmission in RRC Inactive state. The diagram shows the interaction between UE, gNB-DU, gNB-CU-CP, and gNB-CU-UP. The process starts with the gNB-CU-CP deciding to move the UE into RRC\_inactive mode. It then sends a UE CONTEXT MODIFICATION REQUEST to the gNB-DU, which responds with UE CONTEXT MODIFICATION RESPONSE. The gNB-CU-CP then sends a BEARER CONTEXT MODIFICATION REQUEST to the gNB-CU-UP, which responds with BEARER CONTEXT MODIFICATION RESPONSE. The gNB-CU-CP then sends a UE CONTEXT RELEASE COMMAND to the gNB-DU, which responds with UE CONTEXT RELEASE COMPLETE. The gNB-DU then sends an RRCRelease message to the UE. After a period of time in RRC\_inactive mode, the UE sends an RRCResumeRequest with UL SDT data and/or UL SDT signalling to the gNB-DU. The gNB-DU then sends an UL RRC MESSAGE TRANSFER (RRResumeRequest) to the gNB-CU-CP. The gNB-CU-CP then sends a BEARER CONTEXT MODIFICATION REQUEST to the gNB-CU-UP, which responds with BEARER CONTEXT MODIFICATION RESPONSE. The gNB-CU-CP then sends a UL SDT Data message to the gNB-CU-UP. The gNB-CU-UP then sends a UL RRC MESSAGE TRANSFER (UL SDT Signalling) to the gNB-DU. Finally, the gNB-DU sends a Subsequent SDT Data transmission message to the UE. + +Figure 8.18.2-1: CG based Small Data Transmission in RRC Inactive state. + +1. The gNB-CU decides to move UE into RRC\_INACTIVE state. +2. The gNB-CU-CP decides to configure CG-SDT, it sends UE CONTEXT MODIFICATION REQUEST message including a query indication for CG-SDT related resource configuration associated with the information of SDT Radio Bearer(s). +3. The gNB-DU sends the UE CONTEXT MODIFICATION RESPONSE message including the CG-SDT related resource configurations for the requested SDT Radio Bearer(s) within the *DU to CU RRC Information* IE. +4. The gNB-CU-CP sends the BEARER CONTEXT MODIFICATION REQUEST towards the gNB-CU-UP, with the suspend indication. +5. The gNB-CU-UP sends the BEARER CONTEXT MODIFICATION RESPONSE towards the gNB-CU-CP. +6. The gNB-CU-CP sends the UE CONTEXT RELEASE COMMAND message to the gNB-DU including an *RRCRelease* message to the UE with the CG-SDT information within suspend configuration. The gNB-CU notifies the gNB-DU to keep the SDT RLC config, F1-U tunnels, F1AP UE association, and store the CG resource for SDT when the UE is entering RRC\_INACTIVE state with an explicit CG-SDT kept indicator. +7. The gNB-DU sends the *RRCRelease* message to UE. +8. The gNB-DU sends UE CONTEXT RELEASE COMPLETE message. The gNB-DU keeps the SDT RLC config, F1-U tunnels, F1AP UE association, and stores the CG resource for SDT when the UE entering RRC\_INACTIVE. The gNB-DU also stores the C-RNTI, CS-RNTI, and which bearers are CG-SDT bearers. + +After a period of time of the UE being in RRC\_INACTIVE state. + +9. The UE decides to perform CG based SDT procedure, it sends the *RRCResumeRequest* message together with UL SDT data/UL NAS PDU. +10. The gNB-DU sends the UL RRC MESSAGE TRANSFER message including the *RRCResumeRequest* message to indicate the access due to CG-SDT. +- 11/12. If UE context is successfully retrieved as specified in TS 38.300 [2], the gNB-CU-CP initiates the BEARER CONTEXT MODIFICATION procedure to resume SDT DRBs. +- 13 – 13a. The gNB-DU sends the UL SDT data, if any, to the gNB-CU-UP, and/or sends the UL signalling, if any, to the gNB-CU-CP via the UL RRC MESSAGE TRANSFER message, in which any UL NAS PDU is delivered to AMF. + +NOTE 1: void. + +Upon receiving the UE INACTIVITY NOTIFICATION message without SDT volume threshold crossed indication from the gNB-DU and deciding to terminate the ongoing SDT procedure, the gNB-CU shall transmit the UE CONTEXT RELEASE COMMAND message to the gNB-DU. + +NOTE 2: Upon receiving BSR from the UE, in case that UL SDT data size in the BSR is larger than the threshold configured from the gNB-CU-CP, the gNB-DU sends the UE INACTIVITY NOTIFICATION message with the SDT volume threshold crossed indication to the gNB-CU-CP. Upon receiving such indication, the gNB-CU-CP may terminate the ongoing SDT procedure, by sending the *RRCResume* message to move the UE to RRC\_CONNECTED, or by sending the *RRCRelease* message to move the UE to RRC\_INACTIVE. + +If CG-SDT is re-configured, the gNB-CU may request the gNB-DU to keep CG-SDT configuration and resources in the UE CONTEXT RELEASE COMMAND message. + +Upon receiving non-SDT data, the gNB-CU-UP shall send the DL DATA NOTIFICATION message to the gNB-CU-CP. The gNB-CU-CP shall terminate the ongoing SDT procedure as specified in TS 38.300 [2]. + +If the amount of the received DL SDT data is above the data size threshold configured by the gNB-CU-CP, the gNB-CU-UP shall send the DL DATA NOTIFICATION message with the SDT data size threshold crossed indication. The gNB-CU-CP may terminate the ongoing SDT procedure. + +### 8.18.3 RA-SDT or non-SDT with CG-SDT configuration + +The procedure for the case where the UE has CG-SDT resource configurations but decides to perform RACH based small data transmission in RRC Inactive or to perform RACH procedure to transit to RRC Connected (see TS 38.321 [30] clause 5.27) is shown in Figure 8.18.3-1. + +![Sequence diagram for RA-SDT or non-SDT with CG-SDT configuration. The diagram shows interactions between UE, gNB-DU, and gNB-CU-CP. It starts with an RRCRelease message from gNB-DU to UE. After a period in RRC_INACTIVE mode, the UE sends an RRCResumeRequest. The gNB-DU buffers the data, sends an INITIAL UL RRC MESSAGE TRANSFER to the gNB-CU-CP, which responds with a UE CONTEXT SETUP REQUEST. Finally, the gNB-DU sends a UE CONTEXT SETUP RESPONSE to the UE.](67a1dd734d3de6e31754caf85d6fe77f_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB-DU + participant gNB-CU-CP + Note left of UE: After a period of time of UE being in RRC_INACTIVE mode + UE->>gNB-DU: 1. RRCResumeRequest (+ UL SDT data and/or UL SDT signalling) + Note right of gNB-DU: 2. Buffer UL SDT data/signalling + gNB-DU->>gNB-CU-CP: 3. INITIAL UL RRC MESSAGE TRANSFER (RRCResumeRequest, new gNB DU UE F1AP ID) + gNB-CU-CP->>gNB-DU: 4. UE CONTEXT SETUP REQUEST (new gNB DU UE F1AP ID, (optional) old gNB-DU UE F1AP ID) + gNB-CU-CP->>gNB-DU: 5. UE CONTEXT SETUP RESPONSE (new gNB DU UE F1AP ID) + gNB-DU->>UE: 0. RRCRelease (suspend indication, CG-SDT config) + +``` + +Sequence diagram for RA-SDT or non-SDT with CG-SDT configuration. The diagram shows interactions between UE, gNB-DU, and gNB-CU-CP. It starts with an RRCRelease message from gNB-DU to UE. After a period in RRC\_INACTIVE mode, the UE sends an RRCResumeRequest. The gNB-DU buffers the data, sends an INITIAL UL RRC MESSAGE TRANSFER to the gNB-CU-CP, which responds with a UE CONTEXT SETUP REQUEST. Finally, the gNB-DU sends a UE CONTEXT SETUP RESPONSE to the UE. + +Figure 8.18.3-1: RA-SDT or non-SDT with CG-SDT configuration. + +1. The UE in RRC Inactive sends *RRCResumeRequest* message. If the UE decides to perform RACH based SDT procedure, it also sends UL SDT data and/or UL SDT signalling. +2. The gNB-DU buffers the UL SDT data and/or UL SDT signalling. +3. The gNB-DU sends the INITIAL UL RRC MESSAGE TRANSFER message to the gNB-CU-CP, including a new gNB-DU UE F1AP ID, and in case of RACH based SDT access, the gNB-DU provides an indication of SDT access and may also the SDT assistance information. +4. If UE context is successfully retrieved as specified in TS 38.300 [2], the gNB-CU-CP sends the UE CONTEXT SETUP REQUEST message with the stored (or retrieved from the last serving gNB) F1 UL TEIDs and the new gNB-DU UE F1AP ID received in step 3. + +In case that the gNB-DU is the one that sent the *RRCRelease* message with CG-SDT resource configurations to the UE, the gNB-CU-CP also includes the old gNB-DU UE F1AP ID and the old gNB-CU F1AP UE ID within the *Old CG-SDT Session Info* IE of the UE CONTEXT SETUP REQUEST message. + +In case that the gNB-CU-CP is the one that generated the *RRCRelease* message with CG-SDT resource configurations but the gNB-DU is not the old gNB-DU that sent the *RRCRelease* message to the UE, the gNB-CU-CP initiates the UE Context Release procedure by sending the UE CONTEXT RELEASE COMMAND message to the old gNB-DU. + +In case that the UE accesses a gNB other than the last serving gNB, upon receiving the RETRIEVE UE CONTEXT REQUEST message from the receiving gNB-CU-CP, the last serving gNB-CU-CP initiates the UE Context Release procedure by sending the UE CONTEXT RELEASE COMMAND message to the last serving gNB-DU. + +5. The gNB-DU sends the UE CONTEXT SETUP RESPONSE message with the new gNB-DU UE F1AP ID. In case the old gNB-DU UE F1AP ID is received within the *Old CG-SDT Session Info* IE in step 4, the gNB-DU retrieves the stored CG-SDT resource configurations and UE context based on the *Old CG-SDT Session Info* IE, if any, and associates them with the new gNB-DU F1AP UE ID. + +### 8.18.4 MT-SDT + +The procedure for mobile terminated small data transmission in RRC Inactive is shown in Figure 8.18.4-1. + +![Sequence diagram for Mobile Terminated Small Data Transmission in RRC Inactive state. The diagram shows interactions between UE, gNB-DU, gNB-CU-CP, and gNB-CU-UP. The steps are: 1. Bearer context setup or modification from gNB-CU-CP to gNB-DU; 2a-0. DL traffic detected on the NG-U tunnel(s) at gNB-CU-UP; 2a-1. DL DATA NOTIFICATION (MT-SDT information) from gNB-CU-UP to gNB-CU-CP; 2b. DL signalling received over the NGAP at gNB-CU-CP; 3. PAGING (MT-SDT indication) from gNB-CU-CP to gNB-DU; 4. Paging (MT-SDT indicator) from gNB-DU to UE; 5. SDT procedures as specified in 8.18.1 or from step9 in 8.18.2 or from step1 in 8.18.3, or the RRC connection resume procedure as described in 8.6.2 or 8.9.6.2.](9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB-DU + participant gNB-CU-CP + participant gNB-CU-UP + + Note over gNB-CU-CP, gNB-DU: 1. Bearer context setup or modification + gNB-CU-CP->>gNB-DU: 1. Bearer context setup or modification + Note right of gNB-CU-UP: 2a-0. DL traffic detected on the NG-U tunnel(s) + gNB-CU-UP->>gNB-CU-CP: 2a-1. DL DATA NOTIFICATION (MT-SDT information) + Note right of gNB-CU-CP: 2b. DL signalling received over the NGAP + gNB-CU-CP->>gNB-DU: 3. PAGING (MT-SDT indication) + gNB-DU->>UE: 4. Paging (MT-SDT indicator) + Note over UE, gNB-DU: 5. SDT procedures as specified in 8.18.1 or from step9 in 8.18.2 or from step1 in 8.18.3, or the RRC connection resume procedure as described in 8.6.2 or 8.9.6.2. + +``` + +Sequence diagram for Mobile Terminated Small Data Transmission in RRC Inactive state. The diagram shows interactions between UE, gNB-DU, gNB-CU-CP, and gNB-CU-UP. The steps are: 1. Bearer context setup or modification from gNB-CU-CP to gNB-DU; 2a-0. DL traffic detected on the NG-U tunnel(s) at gNB-CU-UP; 2a-1. DL DATA NOTIFICATION (MT-SDT information) from gNB-CU-UP to gNB-CU-CP; 2b. DL signalling received over the NGAP at gNB-CU-CP; 3. PAGING (MT-SDT indication) from gNB-CU-CP to gNB-DU; 4. Paging (MT-SDT indicator) from gNB-DU to UE; 5. SDT procedures as specified in 8.18.1 or from step9 in 8.18.2 or from step1 in 8.18.3, or the RRC connection resume procedure as described in 8.6.2 or 8.9.6.2. + +**Figure 8.18.4-1: Mobile Terminated Small Data Transmission in RRC Inactive state.** + +1. During the setup or modification of the bearer context as specified in 8.9.2, the gNB-CU-CP requests the gNB-CU-UP to provide MT-SDT information. +- 2a-0. The gNB-CU-UP receives DL data for the UE in RRC Inactive on NG-U interface. +- 2a-1. The gNB-CU-UP sends DL DATA NOTIFICATION message to the gNB-CU-CP. If determining that DL data packets are only mapped to SDT bearers, as requested in step 1, the gNB-CU-UP includes the MT-SDT information in the DL DATA NOTIFICATION message. +- 2b. The gNB-CU-CP receives DL NAS signalling over NGAP. +3. After 2a or 2b, the gNB-CU-CP sends PAGING message to the gNB-DU. The MT-SDT indication may be included in the PAGING message. +4. The gNB-DU sends the *Paging* message to the UE. In case the MT-SDT indication is received in step 3, the gNB-DU includes the MT-SDT indicator in the *Paging* message. +5. If the UE has been successfully reached, it initiates the RRC connection resume procedure as described in 8.6.2 or 8.9.6.2, or initiates the SDT procedure as described from step 1 in 8.18.1 or from step 9 in 8.18.2 or from step 1 in 8.18.3 with the following difference: + - In case SDT procedure is initiated, the UE may indicate MT-SDT in the RRCResumeRequest, which may be without UL data. + +## 8.19 Overall procedures for L2 UE-to-Network Relay + +### 8.19.1 Remote UE initial access + +The signalling flow for Remote UE Initial access is shown in Figure 8.19.1-1. + +![Sequence diagram of Remote UE Initial Access procedure. Lifelines: Remote UE, Relay UE, gNB-DU, gNB-CU, AMF. The procedure involves discovery, RRC setup relay, context modification, and final context setup.](da85343976fdbb19f866d9ddbdad0eae_img.jpg) + +``` + +sequenceDiagram + participant Remote UE + participant Relay UE + participant gNB-DU + participant gNB-CU + participant AMF + + Note over Remote UE, Relay UE: 1. Discovery & PC5 Connection Establishment + Remote UE->>Relay UE: 2. RRCSetupRequest + Relay UE->>gNB-DU: 3.(relay UE) SidelinkUEInformationNR + gNB-DU->>gNB-CU: 4.(relay UE) UL RRC MESSAGE TRANSFER + gNB-CU->>gNB-DU: 5. (relay UE) UE CONTEXT MODIFICATION REQUEST + gNB-DU->>gNB-CU: 6. (relay UE) UE CONTEXT MODIFICATION RESPONSE + gNB-CU->>gNB-DU: 7. (relay UE) DL RRC MESSAGE TRANSFER + gNB-DU->>Relay UE: 8. (relay UE) RRCReconfiguration + Relay UE->>gNB-DU: 9. (relay UE) RRCReconfigurationComplete + gNB-DU->>gNB-CU: 10. (relay UE) UL RRC MESSAGE TRANSFER + Relay UE->>gNB-DU: 11. RRCSetupRequest + gNB-DU->>gNB-CU: 12. INITIAL UL RRC MESSAGE TRANSFER + gNB-CU->>gNB-DU: 13. DL RRC MESSAGE TRANSFER + gNB-DU->>Remote UE: 14. RRCSetup + Note over gNB-DU, gNB-CU: 15. Prepare PC5 and Uu RLC Channel for SRB1 + Remote UE->>gNB-DU: 16. RRCSetupComplete + gNB-DU->>gNB-CU: 17. UL RRC MESSAGE TRANSFER + gNB-CU->>AMF: 18. INITIAL UE MESSAGE + AMF->>gNB-CU: 19. INITIAL CONTEXT SETUP REQUEST + gNB-CU->>gNB-DU: 20. UE CONTEXT SETUP REQUEST + gNB-DU->>gNB-CU: 22. UE CONTEXT SETUP RESPONSE + Remote UE->>gNB-DU: 21. SecurityModeCommand + gNB-DU->>gNB-CU: 24. UL RRC MESSAGE TRANSFER + gNB-CU->>gNB-DU: 25. DL RRC MESSAGE TRANSFER + Remote UE->>gNB-DU: 23. SecurityModeComplete + gNB-DU->>gNB-CU: 28. UL RRC MESSAGE TRANSFER + gNB-CU->>AMF: 29. INITIAL CONTEXT SETUP RESPONSE + Remote UE->>gNB-DU: 26. RRCReconfiguration + gNB-DU->>gNB-CU: 30. Prepare PC5 and Uu RLC Channel for DRBs/SRBs + Remote UE->>gNB-DU: 27. RRCReconfigurationComplete + +``` + +Sequence diagram of Remote UE Initial Access procedure. Lifelines: Remote UE, Relay UE, gNB-DU, gNB-CU, AMF. The procedure involves discovery, RRC setup relay, context modification, and final context setup. + +**Figure 8.19.1-1: Remote UE Initial Access procedure** + +1. The U2N Remote UE and the U2N Relay UE perform discovery procedure, and establish PC5 connection using NR ProSe procedure. +2. The U2N Remote UE sends an *RRCSetupRequest* message to the U2N Relay UE via PC5 Relay RLC Channel. +3. The U2N Relay UE withholds the received RRC message and sends the *SidelinkUEInformationNR* message to the gNB-DU. Before that, if the U2N Relay UE is in *RRC\_IDLE/RRC\_INACTIVE* state, it should trigger the RRC establishment/resume procedure to enter *RRC\_CONNECTED* state and gNB may configure the U2N Relay UE with Uu Relay RLC channel(s) for relaying of U2N Remote UE's SRB0/1. + +4. The gNB-DU sends the UL RRC MESSAGE TRANSFER message of the U2N Relay UE by encapsulating the *SidelinkUEInformationNR* message to gNB-CU, and gNB-CU allocates the local ID of U2N Remote UE. +5. The gNB-CU sends the UE CONTEXT MODIFICATION REQUEST message of the U2N Relay UE to gNB-DU. Such message may request the establishment of Uu Relay RLC channel(s) for the transmission of U2N Remote UE's SRB0/1 if not configured yet. +6. The gNB-DU sends the UE CONTEXT MODIFICATION RESPONSE message of the U2N Relay UE to gNB-CU. +7. The gNB-CU sends the DL RRC MESSAGE TRANSFER message of the U2N Relay UE to gNB-DU by encapsulating the *RRCReconfiguration* message, which contains the local ID allocated to the U2N Remote UE. The *RRCReconfiguration* message shall also contain the Uu Relay RLC channel(s) configuration if not configured and bearer mapping for relaying of U2N Remote UE's SRB0/1. +8. The gNB-DU sends the *RRCReconfiguration* message to the U2N Relay UE to configure the local ID of the U2N Remote UE, the Uu Relay RLC channel(s) configuration and bearer mapping for relaying of U2N Remote UE's SRB0/1. +9. The U2N Relay UE sends the *RRCReconfigurationComplete* message to gNB-DU. +10. The gNB-DU sends the UL RRC MESSAGE TRANSFER message of the U2N Relay UE by encapsulating the *RRCReconfigurationComplete* message to gNB-CU. +11. After receiving the local ID of the U2N Remote UE and the Uu Relay RLC channel(s) configuration and bearer mapping for relaying of U2N Remote UE's SRB0, the U2N Relay UE sends the *RRCSetupRequest* message of the U2N Remote UE to gNB-DU. The local ID of the U2N Remote UE and RB ID for SRB0 are conveyed in the SRAP header. +12. The gNB-DU allocates a C-RNTI and a gNB-DU UE F1AP ID for the U2N Remote UE and sends the INITIAL UL RRC MESSAGE TRANSFER message to gNB-CU by encapsulating the *RRCSetupRequest* message of the U2N Remote UE. In addition, the local ID of the U2N Remote UE, the gNB-DU UE F1AP ID of the U2N Relay UE and the sidelink configuration container for at least the PC5 Relay RLC channel configuration for relaying of U2N Remote UE's SRB1 are included in the INITIAL UL RRC MESSAGE TRANSFER message. +13. The gNB-CU allocates a gNB-CU UE F1AP ID for the U2N Remote UE and generates a *RRCSetup* message towards the U2N Remote UE. The RRC message is encapsulated in the DL RRC MESSAGE TRANSFER message, and includes the configurations of PC5 Relay RLC channel and bearer mapping at least for the transmission of U2N Remote UE's SRB1. +14. The gNB-DU sends the *RRCSetup* message to the U2N Remote UE via the U2N Relay UE. +15. The gNB-CU configures the U2N Relay UE with PC5 Relay RLC channel, Uu Relay RLC channel and bearer mapping for relaying of U2N Remote UE's SRB1. According to the configuration from gNB-CU, the U2N Relay UE establishes a PC5 Relay RLC channel for relaying of U2N Remote UE's SRB1 over PC5 and establishes a Uu Relay RLC channel for relaying of U2N Remote UE's SRB1 towards gNB-DU if not configured yet. + +NOTE 1: This step may be performed earlier, e.g., via steps 5~8. + +16. The U2N Remote UE sends the *RRCSetupComplete* message to the gNB-DU via the U2N Relay UE. +17. The gNB-DU encapsulates the RRC message in the UL RRC MESSAGE TRANSFER message and sends it to the gNB-CU. +18. Upon receiving the *RRCSetupComplete* message of U2N Remote UE, the gNB-CU sends the INITIAL UE MESSAGE message to the AMF. +19. The AMF sends the INITIAL CONTEXT SETUP REQUEST message to the gNB-CU. +20. The gNB-CU sends the UE CONTEXT SETUP REQUEST message to establish the U2N Remote UE context in the gNB-DU. Such message may request the configuration of PC5 Relay RLC channels for the transmission of U2N Remote UE's SRB2 and DRBs, and may also encapsulate the *SecurityModeCommand* message. +21. The gNB-DU sends the *SecurityModeCommand* message to the U2N Remote UE via U2N Relay UE. + +22. The gNB-DU sends the UE CONTEXT SETUP RESPONSE message of the U2N Remote UE to the gNB-CU, which contains the configuration of PC5 Relay RLC channels for the transmission of U2N Remote UE's SRB2 and DRBs. +23. The U2N Remote UE responds with the *SecurityModeComplete* message. +24. The gNB-DU encapsulates the RRC message in the UL RRC MESSAGE TRANSFER message and sends it to the gNB-CU. +25. The gNB-CU generates the *RRCReconfiguration* message for U2N Remote UE and encapsulates it in the DL RRC MESSAGE TRANSFER message. The *RRCReconfiguration* message contains the configuration of PC5 Relay RLC channels and bearer mapping for the transmission of U2N Remote UE's SRB2 and DRBs. +26. The gNB-DU sends *RRCReconfiguration* message to the U2N Remote UE via the U2N Relay UE. +27. The U2N Remote UE sends *RRCReconfigurationComplete* message to the gNB-DU via the U2N Relay UE. +28. The gNB-DU encapsulates the RRC message in the UL RRC MESSAGE TRANSFER message and send it to the gNB-CU. +29. The gNB-CU sends the INITIAL CONTEXT SETUP RESPONSE message to the AMF. +30. The gNB-CU configures additional Uu Relay RLC channels between the gNB-DU and the U2N Relay UE, and additional PC5 Relay RLC channels for the U2N Relay UE for relaying of U2N Remote UE's DRBs and SRBs. Also, such step may configure the bearer mapping between U2N Remote UE's DRB/SRB and PC5/Uu Relay RLC channel at the U2N Relay UE. + +NOTE 2: This step may be performed earlier. + +## 8.19.2 Remote UE RRC Reestablishment + +The signalling flow for Remote UE RRC Reestablishment is shown in Figure 8.19.2-1. + +![Sequence diagram showing RRC procedures between Remote UE, Relay UE, gNB-DU, and gNB-CU.](72d448a65347c51989171748789c7d4b_img.jpg) + +``` + +sequenceDiagram + participant Remote UE + participant Relay UE + participant gNB-DU + participant gNB-CU + + Note over Remote UE, Relay UE: 1. Discovery & PC5 Connection Establishment + Remote UE->>Relay UE: 2. RRCReestablishmentRequest + Relay UE->>gNB-DU: 3.(relay UE) SidelinkUEInformationNR + gNB-DU->>gNB-CU: 4.(relay UE) UL RRC MESSAGE TRANSFER + gNB-CU->>gNB-DU: 5. (relay UE) UE CONTEXT MODIFICATION REQUEST + gNB-DU->>gNB-CU: 6. (relay UE) UE CONTEXT MODIFICATION RESPONSE + gNB-CU->>gNB-DU: 7. (relay UE) DL RRC MESSAGE TRANSFER + gNB-DU->>Relay UE: 8. (relay UE) RRCReconfiguration + Relay UE->>gNB-DU: 9. (relay UE) RRCReconfigurationComplete + gNB-DU->>gNB-CU: 10. (relay UE) UL RRC MESSAGE TRANSFER + Relay UE->>gNB-DU: 11. RRCReestablishmentRequest + gNB-DU->>gNB-CU: 12. INITIAL UL RRC MESSAGE TRANSFER + Note over gNB-DU, gNB-CU: 13. Prepare PC5 and Uu RLC Channel for SRB1 + gNB-CU->>gNB-DU: 14. DL RRC MESSAGE TRANSFER + gNB-DU->>Remote UE: 15. RRCReestablishment + Remote UE->>gNB-DU: 16. RRCReestablishmentComplete + gNB-DU->>gNB-CU: 17. UL RRC MESSAGE TRANSFER + gNB-CU->>gNB-DU: 18. UE CONTEXT MODIFICATION REQUEST + gNB-DU->>gNB-CU: 19. UE CONTEXT MODIFICATION RESPONSE + gNB-CU->>gNB-DU: 18'. UE CONTEXT MODIFICATION REQUIRED + gNB-DU->>gNB-CU: 19'. UE CONTEXT MODIFICATION CONFIRM + gNB-CU->>gNB-DU: 20. DL RRC MESSAGE TRANSFER + gNB-DU->>Remote UE: 21. RRCReconfiguration + Remote UE->>gNB-DU: 22. RRCReconfigurationComplete + gNB-DU->>gNB-CU: 23. UL RRC MESSAGE TRANSFER + Note over gNB-DU, gNB-CU: 24. Prepare PC5 and Uu RLC Channel for DRBs/SRBs + +``` + +The sequence diagram illustrates the RRC procedures between a Remote UE, a Relay UE, gNB-DU, and gNB-CU. The process begins with Discovery & PC5 Connection Establishment between the Remote UE and Relay UE. The Remote UE sends an RRCReestablishmentRequest to the Relay UE, which then forwards SidelinkUEInformationNR to the gNB-DU. The gNB-DU interacts with the gNB-CU via UL RRC MESSAGE TRANSFER, UE CONTEXT MODIFICATION REQUEST/RESPONSE, and DL RRC MESSAGE TRANSFER. The gNB-DU then sends an RRCReconfiguration to the Relay UE, which responds with RRCReconfigurationComplete. The gNB-DU forwards this to the gNB-CU via UL RRC MESSAGE TRANSFER. The gNB-DU also receives an RRCReestablishmentRequest from the Relay UE and forwards it to the gNB-CU via INITIAL UL RRC MESSAGE TRANSFER. A preparation step for PC5 and Uu RLC Channel for SRB1 occurs. The gNB-CU sends a DL RRC MESSAGE TRANSFER to the gNB-DU, which then sends an RRCReestablishment to the Remote UE. The Remote UE responds with RRCReestablishmentComplete to the gNB-DU, which forwards it to the gNB-CU via UL RRC MESSAGE TRANSFER. The gNB-CU then sends UE CONTEXT MODIFICATION REQUEST/RESPONSE and UE CONTEXT MODIFICATION REQUIRED/CONFIRM messages. The gNB-CU sends a DL RRC MESSAGE TRANSFER to the gNB-DU, which then sends an RRCReconfiguration to the Remote UE. The Remote UE responds with RRCReconfigurationComplete to the gNB-DU, which forwards it to the gNB-CU via UL RRC MESSAGE TRANSFER. Finally, a preparation step for PC5 and Uu RLC Channel for DRBs/SRBs occurs. + +Sequence diagram showing RRC procedures between Remote UE, Relay UE, gNB-DU, and gNB-CU. + +**Figure 8.19.2-1: Remote UE RRC Reestablishment procedure** + +1. The U2N Remote UE and the U2N Relay UE perform discovery procedure, and establish PC5 connection using NR ProSe procedure. This step may be omitted if PC5 connection was established. +2. The U2N Remote UE sends an *RRCREestablishmentRequest* message to the U2N Relay UE via PC5 Relay RLC Channel. +- 3~10. The gNB-CU allocates the local ID of the U2N Remote UE if the U2N Relay UE does not have it. The details of those steps can be referred to clause 8.19.1. +11. After receiving the local ID of the U2N Remote UE, the U2N Relay UE sends the *RRCREestablishmentRequest* message of the U2N Remote UE to gNB-DU. +12. The gNB-DU allocates a C-RNTI and a gNB-DU UE F1AP ID for the U2N Remote UE and sends the INITIAL UL RRC MESSAGE TRANSFER message to gNB-CU by encapsulating the *RRCREestablishmentRequest* message of the U2N Remote UE. In addition, the local ID of the U2N Remote UE, the gNB-DU UE F1AP ID of the U2N Relay UE and the sidelink configuration container for at least the PC5 Relay RLC channel configuration for relaying of U2N Remote UE's SRB1 are included in the INITIAL UL RRC MESSAGE TRANSFER message. +13. The gNB-CU configures the U2N Relay UE with PC5 Relay RLC channel, Uu Relay RLC channel and bearer mapping for relaying of U2N Remote UE's SRB1. According to the configuration from gNB-CU, the U2N Relay UE establishes a PC5 Relay RLC channel for relaying of U2N Remote UE's SRB1 over PC5 and establishes a Uu Relay RLC channel for relaying of U2N Remote UE's SRB1 over Uu. + +NOTE 1: This step may be performed earlier, e.g., via steps 5~8. + +- 14~23. The details of those steps can be referred to Steps 5~14 in clause 8.7. For L2 U2N relay, the RRC message(s) between the U2N Remote UE and the gNB-DU are relayed via the U2N Relay UE; Steps 18~19 may additionally perform the configurations of PC5 Relay RLC channel(s) for relaying of U2N Remote UE's SRB1, SRB2 and DRBs. +24. The gNB-CU configures additional Uu Relay RLC channels between the gNB-DU and the U2N Relay UE, and additional PC5 Relay RLC channels for the U2N Relay UE for relaying of U2N Remote UE's DRBs and SRBs. Also, such step may configure the bearer mapping between U2N Remote UE's DRB/SRB and PC5/Uu Relay RLC channel at the U2N Relay UE. + +NOTE 2: This step may be performed earlier. + +### 8.19.3 Remote UE RRC Inactive to other states + +The signalling flow for Remote UE from RRC Inactive to other states is shown in Figure 8.19.3-1. + +![Sequence diagram of the Remote UE RRC Resume procedure involving Remote UE, Relay UE, gNB-DU, and gNB-CU.](24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg) + +``` + +sequenceDiagram + participant Remote UE + participant Relay UE + participant gNB-DU + participant gNB-CU + + Note over Remote UE, Relay UE: 1. Discovery & PC5 Connection Establishment + Remote UE->>Relay UE: 2. RRCResumeRequest + Relay UE->>gNB-DU: 3.(relay UE) SidelinkUEInformationNR + gNB-DU->>gNB-CU: 4.(relay UE) UL RRC MESSAGE TRANSFER + gNB-CU->>gNB-DU: 5. (relay UE) UE CONTEXT MODIFICATION REQUEST + gNB-DU->>gNB-CU: 6. (relay UE) UE CONTEXT MODIFICATION RESPONSE + gNB-CU->>gNB-DU: 7. (relay UE) DL RRC MESSAGE TRANSFER + gNB-DU->>Relay UE: 8. (relay UE) RRCReconfiguration + Relay UE->>gNB-DU: 9. (relay UE) RRCReconfigurationComplete + gNB-DU->>gNB-CU: 10. (relay UE) UL RRC MESSAGE TRANSFER + Relay UE->>gNB-DU: 11. RRCResumeRequest + gNB-DU->>gNB-CU: 12. INITIAL UL RRC MESSAGE TRANSFER + Note over gNB-DU, gNB-CU: 13. Prepare PC5 and Uu RLC Channel for SRB1 + gNB-CU->>gNB-DU: 14. UE CONTEXT SETUP REQUEST + gNB-DU-->>gNB-CU: 15. UE CONTEXT SETUP RESPONSE + gNB-CU->>gNB-DU: 16. DL RRC MESSAGE TRANSFER + gNB-DU->>Remote UE: 17. RRCResume/RRReject/RRSetup/RRRelease + Remote UE->>gNB-DU: 18. RRCResumeComplete/RRSetupComplete + gNB-DU->>gNB-CU: 19. UL RRC MESSAGE TRANSFER + Note over gNB-DU, gNB-CU: 20. Prepare PC5 and Uu RLC Channel for DRBs/SRBs + +``` + +The sequence diagram illustrates the Remote UE RRC Resume procedure. It begins with the Remote UE and Relay UE performing a discovery procedure and establishing a PC5 connection (Step 1). The Remote UE sends an *RRCResumeRequest* message to the Relay UE (Step 2). The Relay UE then forwards this as a *SidelinkUEInformationNR* message to the gNB-DU (Step 3). The gNB-DU transfers this as an UL RRC MESSAGE TRANSFER to the gNB-CU (Step 4). The gNB-CU responds with a UE CONTEXT MODIFICATION REQUEST (Step 5), which the gNB-DU relays to the gNB-CU as a UE CONTEXT MODIFICATION RESPONSE (Step 6). The gNB-CU then sends a DL RRC MESSAGE TRANSFER to the gNB-DU (Step 7), which the gNB-DU relays as an *RRCReconfiguration* message to the Relay UE (Step 8). The Relay UE responds with an *RRCReconfigurationComplete* message to the gNB-DU (Step 9), which is transferred as an UL RRC MESSAGE TRANSFER to the gNB-CU (Step 10). The Relay UE also sends an *RRCResumeRequest* message to the gNB-DU (Step 11), which is transferred as an INITIAL UL RRC MESSAGE TRANSFER to the gNB-CU (Step 12). A note indicates the preparation of PC5 and Uu RLC channels for SRB1 (Step 13). The gNB-CU sends a UE CONTEXT SETUP REQUEST to the gNB-DU (Step 14), which responds with a UE CONTEXT SETUP RESPONSE (Step 15). The gNB-CU then sends a DL RRC MESSAGE TRANSFER to the gNB-DU (Step 16), which the gNB-DU relays as an *RRCResume/RRReject/RRSetup/RRRelease* message to the Remote UE (Step 17). The Remote UE responds with an *RRCResumeComplete/RRSetupComplete* message to the gNB-DU (Step 18), which is transferred as a UL RRC MESSAGE TRANSFER to the gNB-CU (Step 19). Finally, a note indicates the preparation of PC5 and Uu RLC channels for DRBs/SRBs (Step 20). + +Sequence diagram of the Remote UE RRC Resume procedure involving Remote UE, Relay UE, gNB-DU, and gNB-CU. + +**Figure 8.19.3-1: Remote UE RRC Resume procedure** + +1. The U2N Remote UE and the U2N Relay UE perform discovery procedure, and establish PC5 connection using NR ProSe procedure. This step may be omitted if PC5 connection was established. +2. The U2N Remote UE sends an *RRCResumeRequest* message to the U2N Relay UE via PC5 RLC Relay Channel. +- 3~10. The gNB-CU allocates the local ID of the U2N Remote UE if the U2N Relay UE does not have it. The details of those steps can be referred to clause 8.19.1. + +11. After receiving the local ID of the U2N Remote UE, the U2N Relay UE sends the *RRCSummaryRequest* message of the U2N Remote UE to gNB-DU. +12. The gNB-DU allocates a C-RNTI and a gNB-DU UE F1AP ID for the U2N Remote UE and sends the INITIAL UL RRC MESSAGE TRANSFER message to gNB-CU by encapsulating the *RRCSummaryRequest* message of the U2N Remote UE. In addition, the local ID of the U2N Remote UE, the gNB-DU UE F1AP ID of the U2N Relay UE and the sidelink configuration container for at least the PC5 Relay RLC channel configuration for relaying of U2N Remote UE's SRB1 are included in the INITIAL UL RRC MESSAGE TRANSFER message. +13. The gNB-CU configures the U2N Relay UE with PC5 Relay RLC channel, Uu Relay RLC channel and bearer mapping for relaying of U2N Remote UE's SRB1. According to the configuration from gNB-CU, the U2N Relay UE establishes a PC5 Relay RLC channel for relaying of U2N Remote UE's SRB1 over PC5 and establishes a Uu Relay RLC channel for relaying of U2N Remote UE's SRB1 over Uu. + +NOTE 1: This step may be performed earlier, e.g., via steps 5~8. + +- 14~19. The details of those steps can be referred to Steps 5~10 in clause 8.6.2. For L2 U2N relay, the RRC message(s) between the U2N Remote UE and the gNB-DU are relayed via the U2N Relay UE; Steps 14~15 may additionally perform the configurations of PC5 Relay RLC channel(s) for relaying of U2N Remote UE's SRB2 and DRBs. +20. The gNB-CU establishes additional Uu Relay RLC channels between the gNB-DU and the U2N Relay UE, and additional PC5 Relay RLC channels for the U2N Relay UE for relaying of U2N Remote UE's DRBs and SRBs. Also, such step may configure the bearer mapping between U2N Remote UE's DRB/SRB and PC5/Uu Relay RLC channel at the U2N Relay UE. + +NOTE 2: This step may be performed earlier. + +## 8.19.4 Service Continuity for L2 U2N relay + +### 8.19.4.1 Inter-gNB-DU switch from direct to indirect path + +The signalling flow for U2N Remote UE switch from direct to indirect path with gNB-DU change is shown in Figure 8.19.4.1-1. + +![Sequence diagram illustrating the U2N Remote UE Direct-to-indirect Path Switch with gNB-DU change procedure. The diagram shows interactions between Remote UE, Target Relay UE, Source gNB-DU, Target gNB-DU, and gNB-CU. The process involves measurement configuration, decision making, reconfiguration, context setup, and path switch completion.](684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg) + +``` + +sequenceDiagram + participant Remote UE + participant Target Relay UE + participant Source gNB-DU + participant Target gNB-DU + participant gNB-CU + + Note left of Remote UE: DL/UL data + Remote UE->>gNB-CU: 1. Measurement configuration and reporting + Note right of gNB-CU: 2. Decision of switching to a target U2N Relay UE + gNB-CU->>Target Relay UE: 3. Reconfiguration to target U2N Relay UE + gNB-CU->>Target gNB-DU: 4. UE CONTEXT SETUP REQUEST + Target gNB-DU->>gNB-CU: 5. UE CONTEXT SETUP RESPONSE + gNB-CU->>Source gNB-DU: 6. UE CONTEXT MODIFICATION REQUEST (RRCReconfiguration) + Source gNB-DU->>Remote UE: 7. RRCReconfiguration + Note left of Remote UE: 9. PC5 connection establishment + Remote UE->>Target gNB-DU: 10. RRCReconfigurationComplete + Note left of Remote UE: DL/UL data + Target gNB-DU->>gNB-CU: 11. UL RRC MESSAGE TRANSFER + gNB-CU->>Source gNB-DU: 12. UE CONTEXT RELEASE COMMAND + Source gNB-DU->>gNB-CU: 13. UE CONTEXT RELEASE COMPLETE + +``` + +Sequence diagram illustrating the U2N Remote UE Direct-to-indirect Path Switch with gNB-DU change procedure. The diagram shows interactions between Remote UE, Target Relay UE, Source gNB-DU, Target gNB-DU, and gNB-CU. The process involves measurement configuration, decision making, reconfiguration, context setup, and path switch completion. + +**Figure 8.19.4.1-1: U2N Remote UE Direct-to-indirect Path Switch with gNB-DU change procedure** + +1. The Uu measurement configuration and measurement report signalling is performed between U2N Remote UE and gNB-CU to evaluate both relay link measurement and Uu link measurement. The U2N Remote UE may report one or multiple candidate U2N Relay UE(s) and Uu measurement results after it measures/discovers the candidate U2N Relay UE(s). +2. The gNB-CU decides to switch the U2N Remote UE to a target U2N Relay UE under a different gNB-DU (i.e., target gNB-DU). +3. The reconfiguration to target U2N Relay UE is performed among U2N Relay UE, the target gNB-DU and gNB-CU, if the U2N Relay UE is in RRC\_CONNECTED state. The gNB-CU sends an *RRCReconfiguration* message to the target U2N Relay UE. If the target Relay UE is in RRC\_IDLE/INACTIVE state, this step is skipped and the configuration to the target U2N Relay UE is performed in Step 10. +4. gNB-CU sends the UE CONTEXT SETUP REQUEST message for the U2N Remote UE to the target gNB-DU, which contains the path switch configuration at least. +5. gNB-DU responds with the UE CONTEXT SETUP RESPONSE message to gNB-CU. +6. gNB-CU sends the UE CONTEXT MODIFICATION REQUEST message by including the *RRCReconfiguration* message to the source gNB-DU. The contents in the *RRCReconfiguration* message may include at least path switch configuration, PC5 Relay RLC channel configuration for relaying traffic, bearer mapping configuration and the associated radio bearer(s). +7. The source gNB-DU sends the *RRCReconfiguration* message to the U2N Remote UE. The U2N Remote UE stops UP and CP transmission over Uu after reception of *RRCReconfiguration* message from the gNB. +8. The source gNB-DU sends the UE CONTEXT MODIFICATION RESPONSE message to the gNB-CU. + +9. The U2N Remote UE establishes PC5 connection with target U2N Relay UE. +10. The U2N Remote UE completes the path switch procedure by sending the *RRCReconfigurationComplete* message to the target gNB-DU via the target U2N Relay UE. In case the U2N relay UE is in RRC\_IDLE/INACTIVE state, when the U2N relay UE receives the *RRCReconfigurationComplete* message, the reception of the *RRCReconfigurationComplete* message will first trigger RRC setup/resume procedure for the U2N relay UE to enter RRC\_CONNECTED state. +11. The target gNB-DU sends the UL RRC MESSAGE TRANSFER message to gNB-CU by including the *RRCReconfigurationComplete* message. +12. The gNB-CU sends an UE CONTEXT RELEASE COMMAND message to the source gNB-DU. +13. The source gNB-DU releases the UE context and responds the gNB-CU with an UE CONTEXT RELEASE COMPLETE message. + +#### 8.19.4.2 Intra-gNB-DU switch from direct to indirect path + +The signalling flow for U2N Remote UE switch from direct to indirect path without gNB-DU change is shown in Figure 8.19.4.2-1. + +![Sequence diagram for U2N Remote UE Direct-to-indirect Path Switch without gNB-DU change procedure. The diagram shows four lifelines: Remote UE, Target Relay UE, gNB-DU, and gNB-CU. The process starts with DL/UL data exchange between Remote UE and gNB-CU. Step 1: Measurement configuration and reporting from gNB-CU to Remote UE. Step 2: Decision of switching to a target U2N Relay UE at gNB-CU. Step 3: Reconfiguration to target U2N Relay UE from gNB-CU to Remote UE. Step 4: UE CONTEXT MODIFICATION REQUEST from gNB-CU to gNB-DU. Step 5: UE CONTEXT MODIFICATION RESPONSE from gNB-DU to gNB-CU. Step 6: DL RRC MESSAGE TRANSFER from gNB-CU to gNB-DU. Step 7: RRCReconfiguration from gNB-DU to Remote UE. Step 8: PC5 connection establishment between Remote UE and Target Relay UE. Step 9: RRCReconfigurationComplete from Remote UE to gNB-DU via Target Relay UE. Step 10: UL RRC MESSAGE TRANSFER from gNB-DU to gNB-CU. The process ends with DL/UL data exchange between Remote UE and gNB-CU via Target Relay UE.](b11b654648249b38a82129a35555b481_img.jpg) + +``` + +sequenceDiagram + participant Remote UE + participant Target Relay UE + participant gNB-DU + participant gNB-CU + + Note right of gNB-CU: DL/UL data + gNB-CU->>Remote UE: 1. Measurement configuration and reporting + Note right of gNB-CU: 2. Decision of switching to a target U2N Relay UE + gNB-CU->>Remote UE: 3. Reconfiguration to target U2N Relay UE + gNB-CU->>gNB-DU: 4. UE CONTEXT MODIFICATION REQUEST + gNB-DU->>gNB-CU: 5. UE CONTEXT MODIFICATION RESPONSE + gNB-CU->>gNB-DU: 6. DL RRC MESSAGE TRANSFER + gNB-DU->>Remote UE: 7. RRCReconfiguration + Note left of Remote UE: 8. PC5 connection establishment + Remote UE->>gNB-DU: 9. RRCReconfigurationComplete + gNB-DU->>gNB-CU: 10. UL RRC MESSAGE TRANSFER + Note right of gNB-CU: DL/UL data + +``` + +Sequence diagram for U2N Remote UE Direct-to-indirect Path Switch without gNB-DU change procedure. The diagram shows four lifelines: Remote UE, Target Relay UE, gNB-DU, and gNB-CU. The process starts with DL/UL data exchange between Remote UE and gNB-CU. Step 1: Measurement configuration and reporting from gNB-CU to Remote UE. Step 2: Decision of switching to a target U2N Relay UE at gNB-CU. Step 3: Reconfiguration to target U2N Relay UE from gNB-CU to Remote UE. Step 4: UE CONTEXT MODIFICATION REQUEST from gNB-CU to gNB-DU. Step 5: UE CONTEXT MODIFICATION RESPONSE from gNB-DU to gNB-CU. Step 6: DL RRC MESSAGE TRANSFER from gNB-CU to gNB-DU. Step 7: RRCReconfiguration from gNB-DU to Remote UE. Step 8: PC5 connection establishment between Remote UE and Target Relay UE. Step 9: RRCReconfigurationComplete from Remote UE to gNB-DU via Target Relay UE. Step 10: UL RRC MESSAGE TRANSFER from gNB-DU to gNB-CU. The process ends with DL/UL data exchange between Remote UE and gNB-CU via Target Relay UE. + +Figure 8.19.4.2-1: U2N Remote UE Direct-to-indirect Path Switch without gNB-DU change procedure + +1. The Uu measurement configuration and measurement report signalling is performed between U2N Remote UE and gNB-CU to evaluate both relay link measurement and Uu link measurement. The U2N Remote UE may report one or multiple candidate U2N Relay UE(s) and Uu measurement results after it measures/discovers the candidate U2N Relay UE(s). + +2. The gNB-CU decides to switch the U2N Remote UE to a target U2N Relay UE under the same gNB-DU. +3. The reconfiguration to target U2N Relay UE is performed among U2N Relay UE, gNB-DU and gNB-CU if U2N Relay UE is in RRC\_CONNECTED state. The gNB-CU sends an *RRCReconfiguration* message to the target U2N Relay UE. If the target Relay UE is in RRC\_IDLE/INACTIVE state, this step is skipped and the configuration to the target U2N Relay UE is performed in Step 9. +4. gNB-CU sends the UE CONTEXT MODIFICATION REQUEST message for the U2N Remote UE to gNB-DU, which contains the path switch configuration at least. The F1-U packets of the U2N Remote UE can be continuously transmitted via previous tunnels if there is no tunnel update in this step. +5. gNB-DU responds with the UE CONTEXT MODIFICATION RESPONSE message to gNB-CU. +6. gNB-CU sends the DL RRC MESSAGE TRANSFER message by including the *RRCReconfiguration* message to gNB-DU. The contents in the *RRCReconfiguration* message may include at least path switch configuration, PC5 Relay RLC channel configuration for relaying traffic, bearer mapping configuration and the associated radio bearer(s). +7. gNB-DU sends the *RRCReconfiguration* message to the U2N Remote UE. The U2N Remote UE stops UP and CP transmission over Uu after reception of *RRCReconfiguration* message from the gNB. +8. The U2N Remote UE establishes PC5 connection with target U2N Relay UE. +9. The U2N Remote UE completes the path switch procedure by sending the *RRCReconfigurationComplete* message to the gNB-DU via the target U2N Relay UE. In case the U2N Relay UE is in RRC\_IDLE/INACTIVE state when receiving the *RRCReconfigurationComplete* message, the reception of the *RRCReconfigurationComplete* message will first trigger RRC setup/resume procedure for the U2N relay UE to enter RRC\_CONNECTED state. +10. The gNB-DU sends the UL RRC MESSAGE TRANSFER message to gNB-CU by including the *RRCReconfigurationComplete* message. + +#### 8.19.4.3 Inter-gNB-CU switch from direct to indirect path + +The signalling flow for U2N Remote UE switch from direct to indirect path with gNB-CU change is shown in Figure 8.19.4.3-1. + +![Sequence diagram of U2N Remote UE Direct-to-indirect Path Switch with gNB-CU change procedure. The diagram shows interactions between Remote UE, Source gNB (DU and CU), Target Relay UE, Target gNB (DU and CU), and 5GC. It details steps from measurement configuration to path switch completion and context release.](245166735676c675f98f535bc4c6f0a1_img.jpg) + +``` + +sequenceDiagram + participant Remote UE + subgraph Source gNB + S-DU[Source gNB-DU] + S-CU[Source gNB-CU] + end + participant Target Relay UE + subgraph Target gNB + T-DU[Target gNB-DU] + T-CU[Target gNB-CU] + end + participant 5GC + + Note right of S-CU: DL/UL data + Remote UE->>S-CU: 1. Measurement configuration and reporting + S-CU->>S-CU: 2. Decision of indirect path switching + S-CU->>T-CU: 3. HANDOVER REQUEST (List of Candidate U2N Relay UE(s)) + T-CU->>T-CU: 4. Selection of target U2N Relay UE + Note right of T-CU: 5. Reconfiguration to target U2N Relay UE + T-CU->>T-DU: 6. UE CONTEXT SETUP REQUEST + T-DU->>T-CU: 7. UE CONTEXT SETUP RESPONSE + T-CU->>S-CU: 8. HANDOVER REQUEST ACKNOWLEDGE (RRCReconfiguration) + S-CU->>S-DU: 9. UE CONTEXT MODIFICATION REQUEST (RRCReconfiguration) + S-DU->>Remote UE: 10. RRCReconfiguration + Remote UE->>S-DU: 11. UE CONTEXT MODIFICATION RESPONSE + S-DU->>T-DU: 12. SN STATUS TRANSFER + Note right of S-CU: DL/UL data + S-CU->>5GC: 13. Data forwarding + Remote UE->>Target Relay UE: 14. PC5 Connection Establishment + Remote UE->>S-DU: 15. RRCReconfigurationComplete + S-DU->>T-DU: 16. UL RRC MESSAGE TRANSFER + Note right of T-CU: 17. Path Switch procedure is performed + Note right of T-CU: DL/UL data + T-CU->>S-CU: 18. UE CONTEXT RELEASE + S-DU->>S-CU: 19. UE Context Release procedure + +``` + +Sequence diagram of U2N Remote UE Direct-to-indirect Path Switch with gNB-CU change procedure. The diagram shows interactions between Remote UE, Source gNB (DU and CU), Target Relay UE, Target gNB (DU and CU), and 5GC. It details steps from measurement configuration to path switch completion and context release. + +Figure 8.19.4.3-1. U2N Remote UE Direct-to-indirect Path Switch with gNB-CU change procedure + +1. The Uu measurement configuration and measurement report signalling are performed between U2N Remote UE and source gNB-CU to evaluate both relay link measurement and Uu link measurement. The U2N Remote UE may report one or multiple candidate U2N Relay UE(s) and Uu measurement results after it measures/discovers the candidate U2N Relay UE(s). +2. The source gNB-CU decides to switch the U2N Remote UE to one of the candidate U2N Relay UE(s). +3. The source gNB-CU sends the HANDOVER REQUEST message to the target gNB-CU. The HANDOVER REQUEST message may include a list of candidate U2N Relay UE(s) of same cell of the target gNB. +4. The target gNB-CU decides to accept the indirect path switching to the target U2N Relay UE among the candidate U2N Relay UE(s). +5. The reconfiguration to target U2N Relay UE is performed among target U2N Relay UE, the target gNB-DU and target gNB-CU, if the target U2N Relay UE is in RRC\_CONNECTED state. The target gNB-CU allocates the local ID for the U2N Remote UE. The target gNB-CU sends an *RRCReconfiguration* message to the target U2N + +Relay UE. If the target U2N Relay UE is in RRC\_IDLE/INACTIVE state, this step is skipped and the configuration to the target U2N Relay UE is performed in Step 15. + +6. The target gNB-CU sends the UE CONTEXT SETUP REQUEST message for the U2N Remote UE to the target gNB-DU, which contains the path switch configuration at least. +7. The target gNB-DU responds with the UE CONTEXT SETUP RESPONSE message to the target gNB-CU. +8. The target gNB-CU responds the source gNB-CU with an HANDOVER REQUEST ACKNOWLEDGE message by including the *RRCREconfiguration* message. The contents in the *RRCREconfiguration* message may include at least path switch configuration, PC5 Relay RLC channel configuration for relay traffic, bearer mapping and the associated radio bearer(s). +9. The source gNB-CU sends to the source gNB-DU the UE CONTEXT MODIFICATION REQUEST message to send the handover command to the U2N Remote UE, and to indicate to stop the data transmission for the U2N Remote UE. +10. The source gNB-DU sends the *RRCREconfiguration* message to the U2N Remote UE. The U2N Remote UE stops UP and CP transmission over Uu after reception of *RRCREconfiguration* message from the source gNB. +11. The source gNB-DU sends the UE CONTEXT MODIFICATION RESPONSE message to the source gNB-CU. +12. The source gNB-CU sends an SN STATUS TRANSFER message to the target gNB-CU. +13. Data Forwarding may be performed from the source gNB-CU to the target gNB-CU. +14. The U2N Remote UE establishes PC5 connection with target U2N Relay UE. +15. The U2N Remote UE completes the path switch procedure by sending the *RRCREconfigurationComplete* message to the target gNB-DU via the target U2N Relay UE. In case the target U2N Relay UE is in RRC\_IDLE/INACTIVE state when receiving the *RRCREconfigurationComplete* message, the reception of the *RRCREconfigurationComplete* message will first trigger RRC setup/resume procedure for the target U2N Relay UE to enter RRC\_CONNECTED state. +16. The target gNB-DU sends the UL RRC MESSAGE TRANSFER message to target gNB-CU by including the *RRCREconfigurationComplete* message. +17. Path Switch procedure is performed to switch the DL data path towards the target gNB-CU and to establish an NG-C interface instance towards the target gNB-CU. +18. The target gNB-CU sends an UE CONTEXT RELEASE message to the source gNB-CU. +19. The source gNB-CU initiates a F1 UE Context Release procedure to release the UE context of the U2N Remote UE in the source gNB-DU. + +## 8.20 Void + +## 8.21 Overall procedures for Network Controlled Repeater + +### 8.21.1 NCR Integration Procedure + +A high-level flow chart for NCR integration is shown in Figure 8.22.1-1: + +![Sequence diagram showing the integration procedure for NCR. The diagram illustrates three phases: Phase 1: NCR-MT setup, Phase 2: NCR configuration, and Phase 3: NCR Start Operation. The entities involved are NCR, gNB (containing gNB-DU and gNB-CU), and 5GC. The NCR-MT connects to the gNB-CU, which then interacts with the 5GC. The gNB-CU configures the gNB-DU, which then configures the NCR. Finally, the gNB-DU starts operation.](db7a693cf26f527ac6c0d4d41da20858_img.jpg) + +``` +sequenceDiagram + participant NCR + subgraph gNB + gNB-DU + gNB-CU + end + participant 5GC + Note right of gNB: Phase 1: NCR-MT setup + NCR->>gNB-CU: RRCSetupComplete (NCR indication) + gNB-CU->>5GC: Authentication/Authorization + 5GC-->>gNB-CU: Authorization info + gNB-CU->>gNB-DU: Authorization info + Note right of gNB: Phase 2: NCR configuration + gNB-CU->>gNB-DU: RRC configuration + gNB-DU->>NCR: RRC configuration + Note right of gNB: Phase 3: NCR Start Operation + gNB-DU->>NCR: Start Operation +``` + +Sequence diagram showing the integration procedure for NCR. The diagram illustrates three phases: Phase 1: NCR-MT setup, Phase 2: NCR configuration, and Phase 3: NCR Start Operation. The entities involved are NCR, gNB (containing gNB-DU and gNB-CU), and 5GC. The NCR-MT connects to the gNB-CU, which then interacts with the 5GC. The gNB-CU configures the gNB-DU, which then configures the NCR. Finally, the gNB-DU starts operation. + +**Figure 8.21.1-1: The integration procedure for NCR** + +Phase 1: NCR-MT setup. In this phase, the NCR-MT of the NCR (re-)selects a cell that broadcasts the *NCR support* indicator in SIB1. It then connects to the network as a UE, by performing the RRC connection setup procedure with the gNB-CU, and authentication with the 5GC. The NCR-MT includes the NCR indication in the *RRCSetupComplete* message. The gNB selects an appropriate AMF for the NCR. Upon receiving the NCR authorization information from 5GC, the gNB-CU provides the authorization information to the gNB-DU. + +NOTE: The signalling flow for UE initial access procedure as shown in Figure 8.1-1/Figure 8.9.1-1 is used for the setup of the NCR-MT. + +Phase 2: NCR configuration. The gNB-CU may configure the NCR via RRC. + +Phase 3: NCR Start Operation. After the NCR is configured, it may start serving the UE(s). + +## 8.22 Overall procedures for multi-path support + +### 8.22.1 Inter-DU direct path addition on top of indirect path + +The signalling flow for inter-DU direct path addition is shown in Figure 8.22.1-1. This procedure is only applicable to the MP Remote UE using PC5 link. + +![Sequence diagram illustrating the signalling procedure of inter-DU direct path addition on top of indirect path. The diagram shows interactions between Remote UE, Relay UE, gNB-DU1, gNB-DU2, and gNB-CU. The process starts with DL/UL data flow from Remote UE to gNB-CU via Relay UE. Step 1: Measurement configuration and reporting from gNB-CU to Remote UE. Step 2: Decision of addition of direct path via gNB-DU1 at gNB-CU. Step 3: UE CONTEXT SETUP REQUEST from gNB-CU to gNB-DU1. Step 4: UE CONTEXT SETUP RESPONSE from gNB-DU1 to gNB-CU. Step 5: Reconfiguration to relay UE (indicated by a grey bar). Step 6: UE CONTEXT MODIFICATION REQUEST (RRCReconfiguration) from gNB-CU to gNB-DU2. Step 7: RRCReconfiguration from gNB-DU2 to Remote UE. Step 8: UE CONTEXT MODIFICATION RESPONSE from gNB-DU2 to gNB-CU. Step 9: Random access procedure from Remote UE to gNB-DU1. Step 10: RRCReconfigurationComplete from gNB-DU1 to Remote UE. Step 10a: RRCReconfigurationComplete from gNB-DU2 to gNB-CU. Step 11: UL RRC MESSAGE TRANSFER from gNB-DU1 to gNB-CU. Step 11a: UL RRC MESSAGE TRANSFER from gNB-DU2 to gNB-CU. The process ends with DL/UL data flow from Remote UE to gNB-CU via gNB-DU1.](8faeb7db381e28ab1ba06e9f48c19c6e_img.jpg) + +Sequence diagram illustrating the signalling procedure of inter-DU direct path addition on top of indirect path. The diagram shows interactions between Remote UE, Relay UE, gNB-DU1, gNB-DU2, and gNB-CU. The process starts with DL/UL data flow from Remote UE to gNB-CU via Relay UE. Step 1: Measurement configuration and reporting from gNB-CU to Remote UE. Step 2: Decision of addition of direct path via gNB-DU1 at gNB-CU. Step 3: UE CONTEXT SETUP REQUEST from gNB-CU to gNB-DU1. Step 4: UE CONTEXT SETUP RESPONSE from gNB-DU1 to gNB-CU. Step 5: Reconfiguration to relay UE (indicated by a grey bar). Step 6: UE CONTEXT MODIFICATION REQUEST (RRCReconfiguration) from gNB-CU to gNB-DU2. Step 7: RRCReconfiguration from gNB-DU2 to Remote UE. Step 8: UE CONTEXT MODIFICATION RESPONSE from gNB-DU2 to gNB-CU. Step 9: Random access procedure from Remote UE to gNB-DU1. Step 10: RRCReconfigurationComplete from gNB-DU1 to Remote UE. Step 10a: RRCReconfigurationComplete from gNB-DU2 to gNB-CU. Step 11: UL RRC MESSAGE TRANSFER from gNB-DU1 to gNB-CU. Step 11a: UL RRC MESSAGE TRANSFER from gNB-DU2 to gNB-CU. The process ends with DL/UL data flow from Remote UE to gNB-CU via gNB-DU1. + +**Figure 8.22.1-1: Signalling procedure of inter-DU direct path addition on top of indirect path** + +1. The Uu measurement configuration and measurement report signalling are performed between MP Remote UE and the gNB-CU to evaluate both relay link measurement and Uu link measurement. The MP Remote UE may report Uu measurement results of neighboring cells and one or multiple candidate MP Relay UE(s). + 2. The gNB-CU decides to add the direct path to MP Remote UE under a different gNB-DU (i.e., gNB-DU1). +- NOTE: Mode 1 resource configuration cannot be configured for MP Remote UE in inter-gNB-DU multi-path relay in this release. +3. The gNB-CU sends the UE CONTEXT SETUP REQUEST message for the MP Remote UE to the gNB-DU1, which contains at least the direct path configuration. + 4. The gNB-DU1 responds to the gNB-CU with a UE CONTEXT SETUP RESPONSE message. + 5. The gNB-CU sends an *RRCReconfiguration* message to the MP Relay UE to update the indirect path configuration if necessary. + 6. The gNB-CU sends the UE CONTEXT MODIFICATION REQUEST message for MP Remote UE by including the direct path addition information and the *RRCReconfiguration* message to the gNB-DU2. The gNB-DU2 may update the stored UE context for MP Remote UE. The contents in the *RRCReconfiguration* message may include at least direct path addition configuration, RLC channel configuration, bearer mapping and the associated radio bearer(s). + 7. The gNB-DU2 sends the *RRCReconfiguration* message to the MP Remote UE. + 8. The gNB-DU2 sends the UE CONTEXT MODIFICATION RESPONSE message to the gNB-CU. + 9. The MP Remote UE performs random access procedure at the gNB-DU1. + 10. *RRCReconfigurationComplete* from gNB-DU1 to Remote UE. + - 10a. *RRCReconfigurationComplete* from gNB-DU2 to gNB-CU. + 11. UL RRC MESSAGE TRANSFER from gNB-DU1 to gNB-CU. + - 11a. UL RRC MESSAGE TRANSFER from gNB-DU2 to gNB-CU. + +10. The MP Remote UE sends the *RRCReconfigurationComplete* message to the gNB-DU1 via direct path in order to complete the direct path addition procedure. +- 10a. In case the SRB1 with duplication is configured, the MP Remote UE also sends the *RRCReconfigurationComplete* message to the gNB-DU2 via indirect path. +11. The gNB-DU1 sends the UL RRC MESSAGE TRANSFER message to gNB-CU by including the *RRCReconfigurationComplete* message received in step 10. +- 11a. In case the SRB1 with duplication is configured, the gNB-DU2 also sends the UL RRC MESSAGE TRANSFER message to gNB-CU by including the *RRCReconfigurationComplete* message received in step 10a. + +## 8.22.2 Inter-DU indirect path addition on top of direct path + +The signalling flow for inter-DU indirect path addition is shown in Figure 8.22.2-1. + +![Sequence diagram of the signalling procedure for inter-DU indirect path addition on top of direct path. The diagram shows interactions between Remote UE, Relay UE, gNB-DU1, gNB-DU2, and gNB-CU. It includes steps for measurement configuration, decision making, reconfiguration, context setup, and data transfer.](ca9fd3bd2fe73a46244dd1d017ffa3b5_img.jpg) + +``` + +sequenceDiagram + participant Remote UE + participant Relay UE + participant gNB-DU1 + participant gNB-DU2 + participant gNB-CU + + Note right of gNB-CU: 2. Decision of addition of indirect path via relay UE and gNB-DU2 + + Remote UE->>gNB-CU: 1. Measurement configuration and reporting + gNB-CU-->>gNB-CU: 2. Decision of addition of indirect path via relay UE and gNB-DU2 + gNB-CU->>Relay UE: 3. Reconfiguration to relay UE + gNB-CU->>gNB-DU2: 4. UE CONTEXT SETUP REQUEST + gNB-DU2-->>gNB-CU: 5. UE CONTEXT SETUP RESPONSE + gNB-CU->>gNB-DU1: 6. DL RRC MESSAGE TRANSFER (RRCReconfiguration) + gNB-DU1->>Remote UE: 7. RRCReconfiguration + Remote UE->>Relay UE: 8. PC5 connection establishment + Remote UE->>gNB-DU1: 9. RRCReconfigurationComplete + Remote UE-->>gNB-DU2: 9a. RRCReconfigurationComplete + gNB-DU1->>gNB-CU: 10. UL RRC MESSAGE TRANSFER + gNB-DU2-->>gNB-CU: 10a. UL RRC MESSAGE TRANSFER + + Note left of Remote UE: DL/UL data + Remote UE-->>gNB-CU: DL/UL data + gNB-CU-->>gNB-DU1: DL/UL data + gNB-DU1-->>Relay UE: DL/UL data + gNB-DU1-->>gNB-DU2: DL/UL data + gNB-DU2-->>gNB-CU: DL/UL data + +``` + +Sequence diagram of the signalling procedure for inter-DU indirect path addition on top of direct path. The diagram shows interactions between Remote UE, Relay UE, gNB-DU1, gNB-DU2, and gNB-CU. It includes steps for measurement configuration, decision making, reconfiguration, context setup, and data transfer. + +Figure 8.22.2-1 Signalling procedure of inter-DU indirect path addition on top of direct path + +1. If the MP Remote UE is connected with the MP Relay UE using PC5 link, the Uu measurement configuration and measurement report signalling are performed between MP Remote UE and the gNB-CU to evaluate relay link measurement and Uu link measurement. The MP Remote UE may report Uu measurement results of neighboring cells and one or multiple candidate MP Relay UE(s). + +In case that the MP Remote UE is connected with the MP Relay UE using N3C and the MP Relay UE is in RRC\_CONNECTED state, the MP Remote UE reports at least the list of the C-RNTI and the cell ID of one or multiple candidate MP Relay UE(s). + +2. The gNB-CU decides to add the indirect path via MP Relay UE to MP Remote UE under a different gNB-DU (i.e., gNB-DU2). + +NOTE: Mode 1 resource configuration cannot be configured for MP Remote UE in inter-gNB-DU multi-path relay in this release. + +3. The reconfiguration to MP Relay UE is performed among MP Relay UE, the gNB-DU2 and the gNB-CU if MP Relay UE is in RRC\_CONNECTED state. The gNB-CU sends an *RRCReconfiguration* message to the MP Relay UE. If the MP Relay UE is in RRC\_IDLE/INACTIVE state, this step is skipped. + 4. The gNB-CU sends the UE CONTEXT SETUP REQUEST message for the MP Remote UE to the gNB-DU2, which contains the indirect path addition configuration at least. + 5. The gNB-DU2 responds to the gNB-CU with a UE CONTEXT SETUP RESPONSE message. + 6. The gNB-CU sends the DL RRC MESSAGE TRANSFER message for MP Remote UE by including the *RRCReconfiguration* message to gNB-DU1. If the MP Remote UE is connected with the MP Relay UE using the PC5 link, the contents in the *RRCReconfiguration* message may include at least indirect path addition configuration, PC5 Relay RLC channel configuration for relay traffic, bearer mapping and the associated radio bearer(s). If the MP Remote UE is using N3C, the contents in the *RRCReconfiguration* message may include at least indirect path addition configuration, bearer mapping and the associated radio bearer(s). + 7. The gNB-DU1 sends the *RRCReconfiguration* message to the MP Remote UE. + 8. If the MP Remote UE is using the PC5 link, the MP Remote UE establishes PC5 connection with the target MP Relay UE. If the MP Remote UE is connected with the MP Relay UE using N3C, this step is skipped. + 9. The MP Remote UE sends the *RRCReconfigurationComplete* message to the gNB-DU1 via direct path in order to complete the indirect path addition procedure. + - 9a. In case the SRB1 with duplication is configured, the MP Remote UE also sends the *RRCReconfigurationComplete* message to the gNB-DU2 via indirect path. +- NOTE: In the case that the target MP Relay UE for indirect path addition is in RRC\_IDLE/INACTIVE state, how the MP Remote UE triggers the MP Relay UE to be in RRC\_CONNECTED state is specified in TS 38.300 [2]. +10. The gNB-DU1 sends the UL RRC MESSAGE TRANSFER message to gNB-CU by including the *RRCReconfigurationComplete* message received in step 9. + - 10a. In case the SRB1 with duplication is configured, the gNB-DU2 also sends the UL RRC MESSAGE TRANSFER message to gNB-CU by including the *RRCReconfigurationComplete* message received in step 9a. + +### 8.22.3 Intra-DU direct path addition on top of indirect path + +The signaling flow for intra-DU direct path addition is shown in Fig. 8.22.3-1. This procedure is only applicable to the MP Remote UE using PC5 link. + +![Sequence diagram illustrating the signalling procedure of intra-DU direct path addition on top of indirect path. The diagram shows four lifelines: Remote UE, Relay UE, gNB-DU, and gNB-CU. The process starts with DL/UL data flow between Remote UE and gNB-CU via Relay UE. Step 1: Measurement configuration and reporting from gNB-CU to Remote UE. Step 2: Decision of addition of direct path at gNB-CU. Step 3: UE CONTEXT MODIFICATION REQUEST from gNB-CU to gNB-DU. Step 4: UE CONTEXT MODIFICATION RESPONSE from gNB-DU to gNB-CU. Step 5: Reconfiguration to relay UE (gNB-CU to Relay UE). Step 6: DL RRC MESSAGE TRANSFER from gNB-CU to gNB-DU. Step 7: RRCReconfiguration from gNB-DU to Remote UE. Step 8: Random access procedure between Remote UE and gNB-DU. Step 9: RRCReconfigurationComplete from Remote UE to gNB-DU. Step 9a: RRCReconfigurationComplete from Remote UE to gNB-CU via Relay UE. Step 10: UL RRC MESSAGE TRANSFER from gNB-DU to gNB-CU. Step 10a: UL RRC MESSAGE TRANSFER from gNB-DU to gNB-CU via Relay UE. The process ends with DL/UL data flow between Remote UE and gNB-CU via gNB-DU.](3334fcca5dac808f4fd3840aba35bc2e_img.jpg) + +``` + +sequenceDiagram + participant Remote UE + participant Relay UE + participant gNB-DU + participant gNB-CU + + Note right of gNB-CU: DL/UL data + Remote UE->>gNB-CU: 1. Measurement configuration and reporting + gNB-CU->>gNB-CU: 2. Decision of addition of direct path + gNB-CU->>gNB-DU: 3. UE CONTEXT MODIFICATION REQUEST + gNB-DU->>gNB-CU: 4. UE CONTEXT MODIFICATION RESPONSE + gNB-CU->>Relay UE: 5. Reconfiguration to relay UE + gNB-CU->>gNB-DU: 6. DL RRC MESSAGE TRANSFER + gNB-DU->>Remote UE: 7. RRCReconfiguration + Remote UE->>gNB-DU: 8. Random access procedure + Remote UE->>gNB-DU: 9. RRCReconfigurationComplete + Remote UE-->>gNB-CU: 9a. RRCReconfigurationComplete + gNB-DU->>gNB-CU: 10. UL RRC MESSAGE TRANSFER + gNB-DU-->>gNB-CU: 10a. UL RRC MESSAGE TRANSFER + Note right of gNB-CU: DL/UL data + +``` + +Sequence diagram illustrating the signalling procedure of intra-DU direct path addition on top of indirect path. The diagram shows four lifelines: Remote UE, Relay UE, gNB-DU, and gNB-CU. The process starts with DL/UL data flow between Remote UE and gNB-CU via Relay UE. Step 1: Measurement configuration and reporting from gNB-CU to Remote UE. Step 2: Decision of addition of direct path at gNB-CU. Step 3: UE CONTEXT MODIFICATION REQUEST from gNB-CU to gNB-DU. Step 4: UE CONTEXT MODIFICATION RESPONSE from gNB-DU to gNB-CU. Step 5: Reconfiguration to relay UE (gNB-CU to Relay UE). Step 6: DL RRC MESSAGE TRANSFER from gNB-CU to gNB-DU. Step 7: RRCReconfiguration from gNB-DU to Remote UE. Step 8: Random access procedure between Remote UE and gNB-DU. Step 9: RRCReconfigurationComplete from Remote UE to gNB-DU. Step 9a: RRCReconfigurationComplete from Remote UE to gNB-CU via Relay UE. Step 10: UL RRC MESSAGE TRANSFER from gNB-DU to gNB-CU. Step 10a: UL RRC MESSAGE TRANSFER from gNB-DU to gNB-CU via Relay UE. The process ends with DL/UL data flow between Remote UE and gNB-CU via gNB-DU. + +**Figure 8.22.3-1: Signalling procedure of intra-DU direct path addition on top of indirect path** + +1. The Uu measurement configuration and measurement report signalling are performed between MP Remote UE and gNB-CU to evaluate both relay link measurement and Uu link measurement. The MP Remote UE may report Uu measurement results of neighboring cells and one or multiple candidate MP Relay UE(s). +2. The gNB-CU decides to add the direct path to MP Remote UE under the same gNB-DU. +3. The gNB-CU sends the UE CONTEXT MODIFICATION REQUEST message for the MP Remote UE to the gNB-DU, which contains at least the direct path configuration. +4. The gNB-DU responds to the gNB-CU with a UE CONTEXT MODIFICATION RESPONSE message. +5. The gNB-CU sends an *RRCReconfiguration* message to the MP Relay UE to update the indirect path configuration if necessary. +6. The gNB-CU sends the DL RRC MESSAGE TRANSFER message for MP Remote UE by including the *RRCReconfiguration* message to the gNB-DU. The contents in the *RRCReconfiguration* message may include at least direct path addition configuration, RLC channel configuration, bearer mapping and the associated radio bearer(s). +7. The gNB-DU sends the *RRCReconfiguration* message to the MP Remote UE. +8. The MP Remote UE performs random access procedure at the gNB-DU. +9. The MP Remote UE sends the *RRCReconfigurationComplete* message to the gNB-DU via direct path in order to complete the direct path addition procedure. + +9a. In case the SRB1 with duplication is configured, the *RRCReconfigurationComplete* message is also sent to the gNB-DU via indirect path. + +10/10a. The gNB-DU sends the UL RRC MESSAGE TRANSFER message to gNB-CU by including the *RRCReconfigurationComplete* message. + +## 8.22.4 Intra-DU indirect path addition on top of direct path + +The signaling flow for intra-DU indirect path addition is shown in Fig. 8.22.4-1. + +![Sequence diagram showing the signaling procedure for intra-DU indirect path addition on top of direct path. The diagram involves four entities: Remote UE, Relay UE, gNB-DU, and gNB-CU. The process starts with DL/UL data exchange between Remote UE and gNB-CU. Step 1: gNB-CU sends 'Measurement configuration and reporting' to Remote UE. Step 2: gNB-CU makes a 'Decision of addition of indirect path'. Step 3: gNB-CU sends 'Reconfiguration to relay UE' to gNB-DU. Step 4: gNB-DU sends 'UE CONTEXT MODIFICATION REQUEST' to gNB-CU. Step 5: gNB-CU sends 'UE CONTEXT MODIFICATION RESPONSE' to gNB-DU. Step 6: gNB-DU sends 'DL RRC MESSAGE TRANSFER' to gNB-CU. Step 7: gNB-DU sends 'RRCReconfiguration' to Remote UE. Step 8: Remote UE and Relay UE perform 'PC5 connection establishment'. Step 9: Remote UE sends 'RRCReconfigurationComplete' to gNB-DU. Step 9a: Remote UE also sends 'RRCReconfigurationComplete' to gNB-DU via the Relay UE. Step 10: gNB-DU sends 'UL RRC MESSAGE TRANSFER' to gNB-CU. Step 10a: gNB-DU sends 'UL RRC MESSAGE TRANSFER' to gNB-CU via the Relay UE. The process ends with DL/UL data exchange between Remote UE and gNB-CU via the Relay UE.](273610b2edda13f5c3de995f4e845396_img.jpg) + +``` + +sequenceDiagram + participant Remote UE + participant Relay UE + participant gNB-DU + participant gNB-CU + + Note left of Remote UE: DL/UL data + Remote UE->>gNB-CU: 1. Measurement configuration and reporting + gNB-CU->>gNB-CU: 2. Decision of addition of indirect path + gNB-CU->>gNB-DU: 3. Reconfiguration to relay UE + gNB-DU->>gNB-CU: 4. UE CONTEXT MODIFICATION REQUEST + gNB-CU->>gNB-DU: 5. UE CONTEXT MODIFICATION RESPONSE + gNB-DU->>gNB-CU: 6. DL RRC MESSAGE TRANSFER + gNB-DU->>Remote UE: 7. RRCReconfiguration + Note left of Remote UE: 8. PC5 connection establishment + Remote UE->>gNB-DU: 9. RRCReconfigurationComplete + Remote UE-->>gNB-DU: 9a. RRCReconfigurationComplete + gNB-DU->>gNB-CU: 10. UL RRC MESSAGE TRANSFER + gNB-DU-->>gNB-CU: 10a. UL RRC MESSAGE TRANSFER + Note right of gNB-CU: DL/UL data + +``` + +Sequence diagram showing the signaling procedure for intra-DU indirect path addition on top of direct path. The diagram involves four entities: Remote UE, Relay UE, gNB-DU, and gNB-CU. The process starts with DL/UL data exchange between Remote UE and gNB-CU. Step 1: gNB-CU sends 'Measurement configuration and reporting' to Remote UE. Step 2: gNB-CU makes a 'Decision of addition of indirect path'. Step 3: gNB-CU sends 'Reconfiguration to relay UE' to gNB-DU. Step 4: gNB-DU sends 'UE CONTEXT MODIFICATION REQUEST' to gNB-CU. Step 5: gNB-CU sends 'UE CONTEXT MODIFICATION RESPONSE' to gNB-DU. Step 6: gNB-DU sends 'DL RRC MESSAGE TRANSFER' to gNB-CU. Step 7: gNB-DU sends 'RRCReconfiguration' to Remote UE. Step 8: Remote UE and Relay UE perform 'PC5 connection establishment'. Step 9: Remote UE sends 'RRCReconfigurationComplete' to gNB-DU. Step 9a: Remote UE also sends 'RRCReconfigurationComplete' to gNB-DU via the Relay UE. Step 10: gNB-DU sends 'UL RRC MESSAGE TRANSFER' to gNB-CU. Step 10a: gNB-DU sends 'UL RRC MESSAGE TRANSFER' to gNB-CU via the Relay UE. The process ends with DL/UL data exchange between Remote UE and gNB-CU via the Relay UE. + +Figure 8.22.4-1: Signalling procedure of intra-DU indirect path addition on top of direct path + +1. If the MP Remote UE is connected with the MP Relay UE using PC5 link, the Uu measurement configuration and measurement report signalling are performed between MP Remote UE and gNB-CU to evaluate relay link measurement and Uu link measurement. The MP Remote UE may report Uu measurement results of neighboring cells and one or multiple candidate MP Relay UE(s). + +In case that the MP Remote UE is connected with the MP Relay UE using N3C and the MP Relay UE is in RRC\_CONNECTED state, the MP Remote UE reports at least the list of the C-RNTI and the cell ID of one or multiple candidate MP Relay UE(s). + +2. The gNB-CU decides to add the indirect path via MP Relay UE to MP Remote UE under the same gNB-DU. + 3. The reconfiguration to MP Relay UE is performed among MP Relay UE, gNB-DU and gNB-CU if MP Relay UE is in RRC\_CONNECTED state. The gNB-CU sends an *RRCReconfiguration* message to the MP Relay UE. If the MP Relay UE is in RRC\_IDLE/INACTIVE state, this step is skipped. + 4. The gNB-CU sends the UE CONTEXT MODIFICATION REQUEST message for the MP Remote UE to the gNB-DU, which contains the indirect path addition configuration at least. + 5. The gNB-DU responds to the gNB-CU with a UE CONTEXT MODIFICATION RESPONSE message. + 6. The gNB-CU sends the DL RRC MESSAGE TRANSFER message for MP Remote UE by including the *RRCReconfiguration* message to gNB-DU. If the MP Remote UE is connected with the MP Relay UE using the PC5 link, the contents in the *RRCReconfiguration* message may include at least indirect path addition configuration, PC5 Relay RLC channel configuration for relay traffic, bearer mapping and the associated radio bearer(s). If the MP Remote UE is using N3C, the contents in the *RRCReconfiguration* message may include at least indirect path addition configuration, bearer mapping and the associated radio bearer(s). + 7. The gNB-DU sends the *RRCReconfiguration* message to the MP Remote UE. + 8. If the MP Remote UE is using the PC5 link, the MP Remote UE establishes PC5 connection with the target MP Relay UE. If the MP Remote UE is using N3C, this step is skipped. + 9. The MP Remote UE sends the *RRCReconfigurationComplete* message to the gNB-DU via direct path to complete the indirect path addition procedure. + - 9a. In case the SRB1 with duplication is configured, the *RRCReconfigurationComplete* message is also sent to the gNB-DU via indirect path. +- NOTE: In the case that the target MP Relay UE for indirect path addition is in RRC\_IDLE/INACTIVE state, how the MP Remote UE triggers the MP Relay UE to be in RRC\_CONNECTED state is specified in TS 38.300 [2]. +- 10/10a. The gNB-DU sends the UL RRC MESSAGE TRANSFER message to gNB-CU by including the *RRCReconfigurationComplete* message. + +## 8.23 Mobile IAB migration procedures + +### 8.23.1 Migration of mobile IAB-MT via Xn handover + +The mobile IAB-MT can be migrated from a source RRC-terminating IAB-donor-CU to a target RRC-terminating IAB-donor-CU using the Xn handover procedure. During this migration, the mobile IAB-DU co-located with the mobile IAB-MT is connected to an F1-terminating IAB-donor-CU, which may be the same as the source RRC-terminating IAB-donor-CU or the target RRC-terminating IAB-donor-CU, or it can be different from both the source and the target RRC-terminating IAB-donor-CU. + +Figure 8.23.1-1 shows an example of mobile IAB-MT migration via Xn handover. In this example, the mobile IAB-MT is connected to the source RRC-terminating IAB-donor-CU via a source path of an IAB topology before the migration, and it is connected to the target RRC-terminating IAB-donor-CU via a target path of a different IAB topology after the migration. + +![Figure 8.23.1-1: Procedure for Xn-based migration of mobile IAB-MT. The diagram shows a sequence of four steps for the topology adaptation procedure. The network components involved are: Mobile IAB-node, Source path (Source path IAB-node, Intermediate-hop IAB-node on the source path, Source-path IAB-donor-DU), Source RRC-terminating IAB-donor-CU, Target path (Target path IAB-node, Intermediate-hop IAB-node on the target path, Target-path IAB-donor-DU), Target RRC-terminating IAB-donor-CU, F1-terminating IAB-donor-CU, and NGC. Step 1: Steps 1-14 of the topology adaptation procedure of clause 8.17.3.1, where the mIAB-MT performs Xn-based handover from the source RRC-terminating IAB-donor-CU to the target RRC-terminating IAB-donor-CU. Step 2: Steps 15 of the topology adaptation procedure of clause 8.17.3.1 to redirect the mIAB-DU's F1-C to the target path and report F1-U TNL information to the F1-terminating IAB-donor-CU. Step 3: Sending information related to target RRC-terminating IAB-donor-CU to the F1-terminating IAB-donor-CU. Step 4: Steps 16-20 of the topology adaptation procedure of clause 8.17.3.1, where the F1-terminating IAB-donor-CU initiates IAB Transport Migration Management procedure to the target RRC-terminating IAB-donor-CU. The BH RLC channel, BAP route and mapping rules along the target path are re-configured, and F1-U of the mIAB-DU is migrated to the target path.](d22fb161d760fcf9fe3fb7b36f81c6fb_img.jpg) + +Figure 8.23.1-1: Procedure for Xn-based migration of mobile IAB-MT. The diagram shows a sequence of four steps for the topology adaptation procedure. The network components involved are: Mobile IAB-node, Source path (Source path IAB-node, Intermediate-hop IAB-node on the source path, Source-path IAB-donor-DU), Source RRC-terminating IAB-donor-CU, Target path (Target path IAB-node, Intermediate-hop IAB-node on the target path, Target-path IAB-donor-DU), Target RRC-terminating IAB-donor-CU, F1-terminating IAB-donor-CU, and NGC. Step 1: Steps 1-14 of the topology adaptation procedure of clause 8.17.3.1, where the mIAB-MT performs Xn-based handover from the source RRC-terminating IAB-donor-CU to the target RRC-terminating IAB-donor-CU. Step 2: Steps 15 of the topology adaptation procedure of clause 8.17.3.1 to redirect the mIAB-DU's F1-C to the target path and report F1-U TNL information to the F1-terminating IAB-donor-CU. Step 3: Sending information related to target RRC-terminating IAB-donor-CU to the F1-terminating IAB-donor-CU. Step 4: Steps 16-20 of the topology adaptation procedure of clause 8.17.3.1, where the F1-terminating IAB-donor-CU initiates IAB Transport Migration Management procedure to the target RRC-terminating IAB-donor-CU. The BH RLC channel, BAP route and mapping rules along the target path are re-configured, and F1-U of the mIAB-DU is migrated to the target path. + +**Figure 8.23.1-1: Procedure for Xn-based migration of mobile IAB-MT** + +1. Steps 1-14 of the topology adaptation procedure in clause 8.17.3.1 are performed to conduct Xn handover of the mobile IAB-MT from the source parent IAB-node connected to the source RRC-terminating IAB-donor-CU to the target parent IAB-node connected to the target RRC-terminating IAB-donor-CU. In these steps, the mobile IAB-node corresponds to the migrating IAB-node in clause 8.17.3.1, and the mobile IAB-MT's source and target RRC-terminating IAB-donor-CUs correspond to the respective source and target IAB-donor-CUs of clause 8.17.3.1. The source RRC-terminating IAB-donor-CU should retain the UE XnAP IDs allocated for the mobile IAB-MT as long as the mobile IAB-MT is connected. +2. Same as step 15 of the topology adaptation procedure in clause 8.17.3.1, where the F1-C connection between the co-located mobile IAB-DU and its F1-terminating IAB-donor-CU is switched to the target path using the new TNL address information of the IAB-MT. In this step, the mobile IAB-node corresponds to the migrating IAB-node, and the F1-terminating IAB-donor-CU corresponds to the source IAB-donor-CU. +3. The mobile IAB-DU passes to the F1-terminating IAB-donor-CU via FIAP the gNB ID of the target RRC-terminating IAB-donor-CU and the mobile IAB-node's BAP address allocated by the target RRC-terminating IAB-donor-CU. In case the migration of the mobile IAB-MT occurs during DU migration, each logical mobile IAB-DU passes this information to its respective F1-terminating IAB-donor-CU. The F1-terminating IAB-donor-CU retains the UE XnAP ID that it allocated to the mobile IAB-MT as long as the co-located mobile IAB-DU connects to this CU, and retains the UE XnAP ID allocated for the mobile IAB-MT by the source RRC-terminating IAB-donor-CU until the present step (step 3). +4. Steps 16-20 of the topology adaptation procedure in clause 8.17.3.1, where the F1-terminating IAB-donor-CU initiates the IAB Transport Migration Management procedure towards the target RRC-terminating IAB-donor-CU to provide the context of the offloaded traffic. The target RRC-terminating IAB-donor-CU reconfigures the BAP sublayer and/or BH RLC channels on the target path accordingly, and provides the UL BH information for UL BH reconfigurations to be conducted by the F1-terminating IAB-donor-CU on the mobile IAB-node. Then, the F1-U connections of the mobile IAB-node are migrated to the target path. + +## 8.23.2 Migration of mobile IAB-MT via NG handover + +The mobile IAB-MT can be migrated from a source RRC-terminating IAB-donor-CU to a target RRC-terminating IAB-donor-CU using the NG handover procedure. During this migration, the mobile IAB-DU co-located with the mobile IAB-MT is connected to an F1-terminating IAB-donor-CU, which may be the same as the source RRC-terminating IAB-donor-CU or the target RRC-terminating IAB-donor-CU, or it can be different from both the source and the target RRC-terminating IAB-donor-CU. + +Figure 8.23.2-1 shows an example of mobile IAB-MT migration via NG handover. In this example, the mobile IAB-MT is connected to the source RRC-terminating IAB-donor-CU via a source path of an IAB topology before the migration, and it is connected to the target RRC-terminating IAB-donor-CU via a target path of a different IAB topology after the migration. + +![Figure 8.23.2-1: Procedure for NG-based migration of mobile IAB-MT. The diagram shows a sequence of nodes: Mobile IAB-node, Source path (Source path IAB-node, Intermediate-hop IAB-node on the source path, Source-path IAB-donor-DU), Source RRC-terminating IAB-donor-CU, Target path (Target path IAB-node, Intermediate-hop IAB-node on the target path, Target-path IAB-donor-DU), Target RRC-terminating IAB-donor-CU, F1-terminating IAB-donor-CU, and NGC. Two steps are indicated: 1. Similar to Steps 1-14 of the topology adaption procedure in Section 8.17.3.1, where the mIAB-MT performs NG-based handover from the source RRC-terminating IAB-donor-CU to the target RRC-terminating IAB-donor-CU. 2. Steps 2-4 of Section 8.YY.1.](f4e5a86da5c799372a7c1ea2397dedb7_img.jpg) + +Figure 8.23.2-1: Procedure for NG-based migration of mobile IAB-MT. The diagram shows a sequence of nodes: Mobile IAB-node, Source path (Source path IAB-node, Intermediate-hop IAB-node on the source path, Source-path IAB-donor-DU), Source RRC-terminating IAB-donor-CU, Target path (Target path IAB-node, Intermediate-hop IAB-node on the target path, Target-path IAB-donor-DU), Target RRC-terminating IAB-donor-CU, F1-terminating IAB-donor-CU, and NGC. Two steps are indicated: 1. Similar to Steps 1-14 of the topology adaption procedure in Section 8.17.3.1, where the mIAB-MT performs NG-based handover from the source RRC-terminating IAB-donor-CU to the target RRC-terminating IAB-donor-CU. 2. Steps 2-4 of Section 8.YY.1. + +**Figure 8.23.2-1: Procedure for NG-based migration of mobile IAB-MT** + +1. Similar to Step 1-14 in clause 8.17.3.1, where the NG-based handover procedure as defined in clauses 4.9.1.3.2 and 4.9.1.3.3 in TS 23.502 [32] is used instead of Xn-based handover procedure. +2. Same as step 2 to step 4 in clause 8.23.1. + +**NOTE** How to perform the IAB Transport Migration Management/Modification procedures and the IAB Resource Coordination procedure between the F1-terminating IAB-donor-CU and the target RRC-terminating IAB-donor-CU without Xn interface is up to implementation. + +### 8.23.3 Mobile IAB-DU migration procedure + +To support the mobile IAB-DU migration procedure, the mobile IAB-node concurrently supports two logical mobile IAB-DUs, which have F1 connections set up with the source F1-terminating IAB-donor-CU and target F1-terminating IAB-donor-CU, respectively. The mobile IAB-MT's IAB-donor-CU may be same as either the source F1-terminating IAB-donor-CU or the target F1-terminating IAB-donor-CU, or it may be different from both source and target F1-terminating IAB-donor-CUs. + +The UE(s) connected to the mobile IAB-node are handed over from the cell(s) of the source logical mobile IAB-DU that have F1 set up with the source F1-terminating IAB-donor-CU to the cell(s) of the target logical mobile IAB-DU that have F1 set up with the target F1-terminating IAB-donor-CU. After the UE(s) are handed over, the F1 between the source logical mobile IAB-DU's and the source F1-terminating IAB-donor-CU may be removed. + +Figure 8.23.3-1 shows an example of the mobile IAB-DU migration procedure. In this example, the source and the target F1-terminating IAB-donor-CUs are different from the RRC-terminating IAB-donor-CU. + +![Figure 8.23.3-1: Mobile IAB-DU inter-CU migration procedure. The diagram shows a sequence of nodes: UE, Mobile IAB node (Source Logical DU, Target Logical DU, MT), Source F1-terminating IAB-donor-CU, Target F1-terminating IAB-donor-CU, RRC-terminating IAB-donor (DU, CU), and Mobile IAB parent nodes. Six steps are indicated: 1. MIAB F1 SETUP TRIGGERING, 2. F1 SETUP REQUEST, 3. F1 SETUP RESPONSE, 4. MIAB F1 SETUP OUTCOME NOTIFICATION, 5. UE HANDOVER, IAB TMM procedure between Target F1-terminating IAB-donor-CU and the RRC-terminating IAB-donor-CU, 6. F1 removal.](37e75e07bd69576f817434fc996be253_img.jpg) + +Figure 8.23.3-1: Mobile IAB-DU inter-CU migration procedure. The diagram shows a sequence of nodes: UE, Mobile IAB node (Source Logical DU, Target Logical DU, MT), Source F1-terminating IAB-donor-CU, Target F1-terminating IAB-donor-CU, RRC-terminating IAB-donor (DU, CU), and Mobile IAB parent nodes. Six steps are indicated: 1. MIAB F1 SETUP TRIGGERING, 2. F1 SETUP REQUEST, 3. F1 SETUP RESPONSE, 4. MIAB F1 SETUP OUTCOME NOTIFICATION, 5. UE HANDOVER, IAB TMM procedure between Target F1-terminating IAB-donor-CU and the RRC-terminating IAB-donor-CU, 6. F1 removal. + +**Figure 8.23.3-1: Mobile IAB-DU inter-CU migration procedure** + +1. The source F1-terminating IAB-donor-CU may send an MIAB F1 SETUP TRIGGERING message to the source logical mobile IAB-DU to initialize the F1 Setup procedure towards the target F1-terminating IAB-donor-CU. The MIAB F1 SETUP TRIGGERING message includes the gNB ID of the target F1-terminating IAB-donor-CU and the information needed to establish the TNL connection with the target F1-terminating IAB-donor-CU for F1-C. + +**NOTE:** The mobile IAB-DU migration can also be triggered by the OAM. In this case, the OAM provides the mobile IAB-node with all information to initiate the F1 Setup procedure towards the target F1-terminating IAB-donor-CU, and step 1 is omitted. + +2. The target logical mobile IAB-DU initiates TNL establishment and F1 setup (as defined in clause 8.5) with the target F1-terminating IAB-donor-CU. During the F1 Setup procedure, the target logical mobile IAB-DU includes + +the gNB ID of the RRC-terminating IAB-donor-CU, and the BAP address of the co-located mobile IAB-MT in the F1 SETUP REQUEST message. + +3. The target F1-terminating IAB-donor-CU responds to the target logical mobile IAB-DU with an F1 SETUP RESPONSE message. After F1 setup with the target F1-terminating IAB-donor-CU, the target logical mobile IAB-DU can serve UEs via the target mobile IAB-DU's activated cell(s). +4. By sending the MIAB F1 SETUP OUTCOME NOTIFICATION message, the source logical mobile IAB-DU informs the source F1-terminating IAB-donor-CU about the outcome of the F1 interface setup between the co-located target logical mobile IAB-DU and the target F1-terminating IAB-donor-CU. The source logical mobile IAB-DU may provide the source F1-terminating IAB-donor-CU with a mapping between activated cells of the source logical mobile IAB-DU and activated cells of the target logical mobile IAB-DU. If the mobile IAB-DU migration is triggered by the OAM, the gNB-ID of the target F1-terminating IAB-donor-CU is included in this message. +5. The source F1-terminating IAB-donor-CU hands over the UE from a source cell served by the source logical mobile IAB-DU to a target cell served by the target logical mobile IAB-DU. The target F1-terminating IAB-donor-CU initiates the IAB Transport Migration Management procedure towards the RRC-terminating IAB-donor-CU for offloading the UE's traffic during this step. In case the IAB Transport Migration Management procedure is the first procedure for the mobile IAB-MT, it includes the mobile IAB-MT's BAP address in the IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message. After the completion of the UE handover, the source F1-terminating IAB-donor-CU requests the release of the UE's traffic offloaded to the RRC-terminating IAB-donor-CU by initiating IAB Transport Migration Management procedure. + +NOTE 1: In step 5, the sequence of procedures for UE Handover and the IAB Transport Migration Management procedure initiated by the target F1-terminating IAB-donor-CU is up to implementation. + +NOTE 2: It is up to RRC-terminating IAB-donor-CU's implementation to set up new backhaul resources or reuse the existing backhaul resources for the UE's traffic. + +NOTE 3: How to perform the IAB Transport Migration Management/Modification procedures, and the IAB Resource Coordination procedure between the target F1-terminating IAB-donor-CU and the RRC-terminating IAB-donor-CU without Xn interface is up to implementation. + +6. After all the UEs are handed over, the source F1-terminating IAB-donor-CU may initiate the removal of the F1 interface towards the source logical mobile IAB-DU. + +### 8.23.4 Mobile IAB-node RLF recovery + +When the mobile IAB-MT detects backhaul RLF, the mobile IAB-MT can perform inter-CU backhaul RLF recovery procedure to another parent node underneath a different IAB-donor-CU. The procedure is the same as steps 1-18 of IAB inter-CU backhaul RLF recovery procedure described in clause 8.17.4 where the mobile IAB-node corresponds to the Recovery IAB-node. + +## 8.24 Timing resiliency service + +The following clauses describe the overall procedures for RAN Timing Synchronisation Status (TSS) reporting involving gNB-CU/gNB-DU. + +### 8.24.1 RAN TSS reporting towards the CN + +The signaling flow for RAN TSS reporting towards the CN is shown in Figure 8.24.1-1. This procedure is used when the TSCTSF subscribes to RAN TSS reporting at the AMF as described in TS 23.502 [32]. + +![Sequence diagram illustrating RAN TSS reporting towards the CN. The diagram shows interactions between gNB-DU, gNB-CU, and AMF. The process starts with gNB-DU having RAN TSS thresholds configured. The AMF sends a TIMING SYNCHRONISATION STATUS REQUEST to the gNB-CU, which then sends the same request to the gNB-DU. The gNB-DU responds with a TIMING SYNCHRONISATION STATUS RESPONSE to the gNB-CU, which in turn responds to the AMF. The gNB-DU then sends a TIMING SYNCHRONISATION STATUS REPORT to the gNB-CU, which forwards it to the AMF. Later, a primary source event occurs at the gNB-DU, triggering another TIMING SYNCHRONISATION STATUS REPORT to the gNB-CU, which is then forwarded to the AMF.](61b2e15aedbb8a8dffc5426c0a284eb1_img.jpg) + +``` + +sequenceDiagram + participant gNB-DU + participant gNB-CU + participant AMF + Note left of gNB-DU: 0. RAN TSS thresholds configured + AMF->>gNB-CU: 1. TIMING SYNCHRONISATION STATUS REQUEST + gNB-CU->>gNB-DU: 2. TIMING SYNCHRONISATION STATUS REQUEST + gNB-DU->>gNB-CU: 3. TIMING SYNCHRONISATION STATUS RESPONSE + gNB-CU->>AMF: 4. TIMING SYNCHRONISATION STATUS RESPONSE + gNB-DU->>gNB-CU: 5. TIMING SYNCHRONISATION STATUS REPORT + gNB-CU->>AMF: 6. TIMING SYNCHRONISATION STATUS REPORT + Note left of gNB-DU: 7. Primary source event + gNB-DU->>gNB-CU: 8. TIMING SYNCHRONISATION STATUS REPORT + gNB-CU->>AMF: 9. TIMING SYNCHRONISATION STATUS REPORT + +``` + +Sequence diagram illustrating RAN TSS reporting towards the CN. The diagram shows interactions between gNB-DU, gNB-CU, and AMF. The process starts with gNB-DU having RAN TSS thresholds configured. The AMF sends a TIMING SYNCHRONISATION STATUS REQUEST to the gNB-CU, which then sends the same request to the gNB-DU. The gNB-DU responds with a TIMING SYNCHRONISATION STATUS RESPONSE to the gNB-CU, which in turn responds to the AMF. The gNB-DU then sends a TIMING SYNCHRONISATION STATUS REPORT to the gNB-CU, which forwards it to the AMF. Later, a primary source event occurs at the gNB-DU, triggering another TIMING SYNCHRONISATION STATUS REPORT to the gNB-CU, which is then forwarded to the AMF. + +**Figure 8.24.1-1: RAN TSS reporting towards the CN** + +0. The gNB-DU is pre-configured with a threshold for each RAN TSS attribute it supports. The gNB-DU does not report RAN TSS attribute values better than the pre-configured thresholds, i.e. if a RAN TSS attribute has a value better than the pre-configured threshold, the gNB-DU reports the threshold value to the gNB-CU instead. + +NOTE 1: It is assumed the pre-configured thresholds in the gNB-DU are sufficient to meet UE time sync performance requirement which are configured by the operator. + +- The AMF requests RAN TSS reporting by sending the TIMING SYNCHRONISATION STATUS REQUEST message to the gNB-CU. +- The gNB-CU requests RAN TSS reporting from at least one gNB-DU by sending the TIMING SYNCHRONISATION STATUS REQUEST message to the gNB-DU. + +NOTE 2: It is up to gNB-CU implementation whether to send the request to all its gNB-DUs or to a particular subset of its gNB-DUs, depending on e.g. network topology. + +- The gNB-DU replies to the gNB-CU by sending the TIMING SYNCHRONISATION STATUS RESPONSE message. + +- The gNB-CU replies to the AMF by sending the TIMING SYNCHRONISATION STATUS RESPONSE message. If the gNB-CU does not receive a successful response from at least one gNB-DU, the gNB-CU replies to the AMF by sending the TIMING SYNCHRONISATION STATUS FAILURE message and the flow stops at this step. + +- Upon sending the response to the gNB-CU, the gNB-DU provides a first RAN TSS report to the gNB-CU by sending the TIMING SYNCHRONISATION STATUS REPORT message. + +NOTE 3: The RAN TSS attributes included in the report is up to gNB-DU implementation. + +- The gNB-CU sends the TIMING SYNCHRONISATION STATUS REPORT message to the AMF. The message contains the RAN TSS attributes received from the gNB-DU and the *RAN TSS Scope* IE to indicate whether the scope of the RAN TSS report is “RAN node level” or “cell list level”. + +- Later, the gNB-DU detects a primary source event: + +- a RAN TSS attribute cannot meet a pre-configured threshold (i.e. status is degraded); +- a RAN TSS attribute meets the pre-configured threshold again (i.e. status is no longer degraded); +- event a) occurred and b) has not yet been reached, the gNB-DU performs periodic reporting or a previously reported RAN TSS attribute value can no longer be met. + +NOTE 4: Additional primary source events, if any, are up to gNB-DU implementation. + +8. Upon detecting the primary source event, the gNB-DU provides an updated RAN TSS report to the gNB-CU by sending a TIMING SYNCHRONISATION STATUS REPORT message. +9. Same as step 6. + +## 8.24.2 RAN TSS reporting towards the UE + +The signaling flow for RAN TSS reporting towards the UE in RRC\_CONNECTED state is shown in Figure 8.24.2-1. + +![Sequence diagram showing RAN TSS reporting towards the UE in RRC_CONNECTED state. The diagram involves four entities: UE, gNB-DU, gNB-CU, and AMF. The sequence of messages is: 1. INITIAL CONTEXT SETUP REQUEST (with Clock Quality Reporting Control Information) from AMF to gNB-CU; 2. INITIAL CONTEXT SETUP RESPONSE from gNB-CU to AMF; 3. DLInfoTransfer message (with Clock Quality Information) from gNB-CU to UE; 4. Primary source event detection at gNB-DU; 5. TIMING SYNCHRONISATION STATUS REPORT from gNB-DU to gNB-CU; 6. DLInfoTransfer message (with Clock Quality Information) from gNB-CU to UE.](4e3bce0b4a3062f7f237acd0b04e5c66_img.jpg) + +``` + +sequenceDiagram + participant AMF + participant gNB-CU + participant gNB-DU + participant UE + Note right of AMF: 1. INITIAL CONTEXT SETUP REQUEST +(Clock Quality Reporting Control Information) + AMF->>gNB-CU: 1. INITIAL CONTEXT SETUP REQUEST + Note right of gNB-CU: 2. INITIAL CONTEXT SETUP RESPONSE + gNB-CU->>AMF: 2. INITIAL CONTEXT SETUP RESPONSE + Note right of gNB-CU: 3. DLInfoTransfer message +(Clock Quality Information) + gNB-CU->>UE: 3. DLInfoTransfer message + Note left of gNB-DU: 4. Primary source event + gNB-DU->>gNB-CU: 5. TIMING SYNCHRONISATION STATUS REPORT + Note right of gNB-CU: 6. DLInfoTransfer message +(Clock Quality Information) + gNB-CU->>UE: 6. DLInfoTransfer message + +``` + +Sequence diagram showing RAN TSS reporting towards the UE in RRC\_CONNECTED state. The diagram involves four entities: UE, gNB-DU, gNB-CU, and AMF. The sequence of messages is: 1. INITIAL CONTEXT SETUP REQUEST (with Clock Quality Reporting Control Information) from AMF to gNB-CU; 2. INITIAL CONTEXT SETUP RESPONSE from gNB-CU to AMF; 3. DLInfoTransfer message (with Clock Quality Information) from gNB-CU to UE; 4. Primary source event detection at gNB-DU; 5. TIMING SYNCHRONISATION STATUS REPORT from gNB-DU to gNB-CU; 6. DLInfoTransfer message (with Clock Quality Information) from gNB-CU to UE. + +**Figure 8.24.2-1: RAN TSS reporting towards the UE in RRC\_CONNECTED state** + +NOTE 1: In this signalling flow, it is assumed that RAN TSS reporting is already enabled at the gNB-DU. + +1. The AMF sends the INITIAL CONTEXT SETUP REQUEST message to the gNB-CU, containing the *Clock Quality Reporting Control Information* IE within the *Time Synchronization Assistance Information* IE. The clock quality reporting control information indicates the clock quality detail level to provide to the UE, i.e. “metrics” or “acceptable/not acceptable indication”. If clock quality detail level equals “acceptable/not acceptable indication”, the clock quality reporting control information also contains the clock quality acceptance criteria. + +NOTE 2: The clock quality reporting control information can also be provided in the UE CONTEXT MODIFICATION REQUEST, HANDOVER REQUEST, or PATH SWITCH REQUEST ACKNOWLEDGE messages. + +2. The gNB-CU replies to the AMF by sending the INITIAL CONTEXT SETUP RESPONSE message. +3. The gNB-CU sends the latest clock quality information to the UE by sending the *DLInformationTransfer* message. The clock quality information provided to the UE depends on the clock quality detail level received in step 1 (i.e., “metrics” or “acceptable/not acceptable indication”). +4. Later, the gNB-DU detects a primary source event: + - a) a RAN TSS attribute cannot meet a pre-configured threshold (i.e. status is degraded); + - b) a RAN TSS attribute meets the pre-configured threshold again (i.e. status is no longer degraded); + - c) event a) occurred and b) has not yet been reached, the gNB-DU performs periodic reporting or a previously reported RAN TSS attribute value can no longer be met. + +NOTE 3: Additional primary source events, if any, are up to gNB-DU implementation. + +5. Upon detecting the primary source event, the gNB-DU provides an updated RAN TSS report to the gNB-CU by sending a TIMING SYNCHRONISATION STATUS REPORT message. +6. Same as step 3. + +## 9 Synchronization + +### 9.1 gNB Synchronization + +The gNB shall support a logical synchronization port for phase-, time- and/or frequency synchronization. + +Logical synchronization port for phase- and time-synchronization shall provide: + +- 1) accuracy that allows to meet the gNB requirements on maximum relative phase difference for all gNBs in synchronized TDD-unicast area; +- 2) continuous time without leap seconds traceable to common time reference for all gNBs in synchronized TDD-unicast area. In the case the TDD-unicast area is not isolated, the common time reference shall be traceable to the Coordinated Universal Time (UTC). + +A logical synchronization port for phase- and time-synchronization may also be provided for e.g., all gNBs in FDD time domain inter-cell interference coordination synchronization area. + +Furthermore common SFN initialization time shall be provided for all gNBs in synchronized TDD-unicast area. + +In case of non isolated networks, the start of the radio frame on the output shall be synchronous with the input time reference, i.e., when an UTC traceable reference is required, the start of the radio frame shall be aligned with the start time of the UTC second. + +Unless otherwise mutually agreed by the operators of the cells in non isolated networks and/or unless different SFN initialization offsettings do not affect operators' networks in the same area, the common SFN initialization time should be 1980-01-06T00:00:19 International Atomic Time (TAI). + +Based on this information, the gNB may derive the SFN according to the following formula: + +$$SFN = \{time\} \bmod \{period(SFN)\},$$ + +where: + +time                    time adjusted by the common SFN initialization time, in units of 10 ms to match the length of radio frame and accuracy accordingly; + +period(SFN)        SFN period. + +In case gNB is connected via TDM interface, it may be used to frequency synchronize the gNB. The characteristics of the clock in the gNB shall be designed taking into account that the jitter and wander performance requirements on the interface are in accordance with network limits for output wander at traffic interfaces of either ITU-T Recommendation G.823 [8], ITU-T Recommendation G.824 [9] or network limits for the maximum output jitter and wander at any hierarchical interface of ITU-T Recommendation G.825 [10], whichever is applicable. + +In case gNB is connected via Ethernet interface and the network supports Synchronous Ethernet, the gNB may use this interface to get frequency synchronization. In this case the design of the gNB clock should be done considering the jitter and wander performance requirements on the interface are as specified for output jitter and wander at EEC interfaces of ITU-T Recommendation G.8261/Y.1361 [11], defined in clause 9.2.1. Further considerations on Synchronous Ethernet recommendations and architectural aspects are defined in clause 12.2.1 and Annex A of ITU-T Recommendation G.8261/Y.1361 [11]. + +A configurable LTE TDD-offset of start frame shall be supported by all gNBs in synchronized TDD-unicast areas in order to achieve interoperability in coexistence scenarios. + +--- + +## 10 NG-RAN interfaces + +### 10.1 NG interface + +TS 38.410 [14] specifies NG interface general aspects and principles. + +### 10.2 Xn interface + +TS 38.420 [15] specifies Xn interface general aspects and principles. + +### 10.3 F1 interface + +TS 38.470 [16] specifies F1 interface general aspects and principles. + +### 10.4 E1 interface + +TS 38.460 [17] specifies E1 interface general aspects and principles. + +### 10.5 Antenna interface - general principles + +The Iuant interface for the control of RET antennas or TMAs is a logical part of the NG-RAN. + +The support of any standardised antenna interface technique shall not be prevented; e.g. AISG (Antenna interface standards group) specifications may be used. + +--- + +## 11 Overall procedures in NG-RAN Architecture + +### 11.1 Multiple TNLAs for Xn-C + +In the following, the procedure for managing multiple TNLAs for Xn-C is described. + +![Sequence diagram illustrating the management of multiple TNLAs for Xn-C between NG-RAN node1 and NG-RAN node2. The diagram shows three separate TNLA establishment procedures (TNLA1, TNLA2, TNLA3) interleaved with Xn Setup and NG-RAN Node Configuration Update messages.](884c44b6cb9fbe15347e0562a6085df2_img.jpg) + +``` + +sequenceDiagram + participant NG-RAN node1 + participant NG-RAN node2 + Note right of NG-RAN node1: 1. TNLA establishment (TNLA1) + NG-RAN node1->>NG-RAN node2: 1. TNLA establishment (TNLA1) + NG-RAN node2-->>NG-RAN node1: 1. TNLA establishment (TNLA1) + Note right of NG-RAN node1: 2. Xn SETUP REQUEST + NG-RAN node1->>NG-RAN node2: 2. Xn SETUP REQUEST + NG-RAN node2-->>NG-RAN node1: 3. Xn SETUP RESPONSE + Note right of NG-RAN node1: 4. NG-RAN NODE CONFIGURATION UPDATE + NG-RAN node1->>NG-RAN node2: 4. NG-RAN NODE CONFIGURATION UPDATE + Note right of NG-RAN node1: 5. TNLA establishment (TNLA2) + NG-RAN node1->>NG-RAN node2: 5. TNLA establishment (TNLA2) + NG-RAN node2-->>NG-RAN node1: 5. TNLA establishment (TNLA2) + Note right of NG-RAN node1: 6. NG-RAN NODE CONFIGURATION UPDATE ACK + NG-RAN node1->>NG-RAN node2: 6. NG-RAN NODE CONFIGURATION UPDATE ACK + Note right of NG-RAN node1: 7. NG-RAN NODE CONFIGURATION UPDATE + NG-RAN node1->>NG-RAN node2: 7. NG-RAN NODE CONFIGURATION UPDATE + Note right of NG-RAN node1: 8. TNLA establishment (TNLA3) + NG-RAN node1->>NG-RAN node2: 8. TNLA establishment (TNLA3) + NG-RAN node2-->>NG-RAN node1: 8. TNLA establishment (TNLA3) + Note right of NG-RAN node1: 9. NG-RAN NODE CONFIGURATION UPDATE ACK + NG-RAN node1->>NG-RAN node2: 9. NG-RAN NODE CONFIGURATION UPDATE ACK + +``` + +Sequence diagram illustrating the management of multiple TNLAs for Xn-C between NG-RAN node1 and NG-RAN node2. The diagram shows three separate TNLA establishment procedures (TNLA1, TNLA2, TNLA3) interleaved with Xn Setup and NG-RAN Node Configuration Update messages. + +**Figure 11.1-1: Managing multiple TNLAs for Xn-C.** + +1. The NG-RAN node1 establishes the first TNLA with the NG-RAN node2 using a configured TNL address. + +NOTE: The NG-RAN node1 may use different source and/or destination IP end point(s) if the TNL establishment towards one IP end point fails. How the NG-RAN node1 gets the remote IP end point(s) and its own IP address are outside the scope of this specification. + +- 2-3. Once the TNLA has been established, the NG-RAN node1 initiates the Xn Setup procedure to exchange application level configuration data + +- 4-6. The NG-RAN node2 may add additional TNL Endpoint(s) to be used for Xn-C signalling between the NG-RAN node1 and the NG-RAN node2 pair using the NG-RAN node Configuration Update procedure. NG-RAN node Configuration Update procedure also allows the NG-RAN node2 to request the NG-RAN node1 to modify or release TNLA(s). + +- 7-9. The NG-RAN node1 may add additional TNL Endpoint(s) to be used for Xn-C signalling between the NG-RAN node1 and the NG-RAN node2 pair using the NG-RAN node Configuration Update procedure. NG-RAN node Configuration Update procedure also allows the NG-RAN node1 to request the NG-RAN node2 to modify or release TNLA(s). + +The XnAP UE TNLA binding is a binding between a XnAP UE association and a specific TNL association for a given UE. After the XnAP UE TNLA binding is created, the NG-RAN node1 or the NG-RAN node2 can update the UE TNLA binding by sending the first available XnAP message for the UE to the peer NG-RAN node via a different TNLA. The peer NG-RAN node shall update the XnAP UE TNLA binding with the new TNLA. + +# Annex A (informative): Deployment scenarios of gNB/en-gNB + +Figure A-1 shows logical nodes (CU-C, CU-U and DU), internal to a logical gNB/en-gNB. Protocol terminations of the NG and Xn interfaces are depicted as ellipses in Figure A-1. The terms "Central Entity" and "Distributed Entity" shown in Figure A-1 refer to physical network nodes. + +![Diagram of a logical gNB/en-gNB showing Central and Distributed Entities with their internal logical nodes and external interfaces.](16e2337d7302fa71012e69303a459c35_img.jpg) + +The diagram illustrates the internal structure of a logical gNB/en-gNB. A dashed blue box labeled 'Logical gNB/en-gNB' contains two main physical network nodes: the 'Central Entity' (top, grey background) and the 'Distributed Entity' (bottom, green background). The Central Entity contains four logical nodes: 'Xn-C' (ellipse, left), 'CU-C' (rectangle, center-left), 'CU-U' (rectangle, center-right), and 'Xn-U' (ellipse, right). The Distributed Entity contains the 'DU' (rectangle, center). External interfaces are shown as lines connecting to ellipses: 'Xn-C' connects to an external 'Xn-C' ellipse on the left; 'Xn-U' connects to an external 'Xn-U' ellipse on the right; 'NG-C' connects to an external 'NG-C' ellipse at the top; and 'NG-U' connects to an external 'NG-U' ellipse at the top. Internal interfaces are shown as lines connecting logical nodes: 'F1-C' connects the 'CU-C' to the 'DU', and 'F1-U' connects the 'CU-U' to the 'DU'. + +Diagram of a logical gNB/en-gNB showing Central and Distributed Entities with their internal logical nodes and external interfaces. + +Figure A-1: Example deployment of an Logical gNB/en-gNB + +--- + +## Annex B: NG-RAN Architecture for Radio Access Network Sharing with multiple cell ID broadcast (informative) + +Each gNB-DU serving a cell identified by a Cell Identity associated with a subset of PLMNs is connected to a gNB-CU via a single F1-C interface instance. + +Each F1-C interface instance is setup individually. + +F1-C interface instances terminating at gNB-DUs which share the same physical radio resources may share the same F1-C signalling transport resources. If this option is applied, + +- non-UE associated signalling is associated to an F1-C interface instance by allocating the corresponding Transaction ID from a value range associated to that F1-C interface instance. +- node related, non-UE associated F1-C interface signalling may provide information destined for multiple logical nodes in a single F1AP procedure instance once the F1-C interface instance is setup. + +NOTE 1: If the Transaction ID corresponds to more than one interface instance, the respective F1AP message carries information destined for multiple logical nodes. + +- a UE associated signalling connection is associated to an F1-C interface instance by allocating values for the corresponding gNB-DU UE F1AP ID and gNB-CU UE F1AP ID so that they can be mapped to that interface instance. + +NOTE 2: One possible implementation is to partition the value ranges of the gNB-DU UE F1AP ID and gNB-CU UE F1AP ID and associate each value range with an F1-C interface instance. + +Interpreting the content of RRC MSG3 and other unciphered RRC message by the gNB-DU is supported. + +Content for System Information Broadcast is assumed to be coordinated among the sharing PLMNs. PLMN specific SIB1 content is controlled by the respective PLMN owner. Non PLMN specific content needs coordination to avoid contradicting indication by PLMN specific gNB-CUs. For Warning messages (SIB6, SIB7 and SIB8), if provided by more than one gNB-CU, warning message duplicates are identified by provision of the Message Number and the Serial Number by the gNB-CU and don't trigger new broadcast or replace existing broadcast. Other coordination between gNB-CUs is ensured by appropriate implementation. + +## Annex C (informative): Change History + +| | | | | | | Change history | | | +|---------|----------------|-----------|------|-----|-----|------------------------------------------------------------------------------------------------------------------|-------------|--| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | | +| 2017-04 | RAN3#95bis | R3-171307 | | | | First Draft | 0.0.1 | | +| 2017-05 | RAN3#96 | R3-171962 | | | | Reflected agreed TP in RAN3#96.
Added new Clause 8 for overall procedure for gNB-CU/DU architecture | 0.1.0 | | +| 2017-06 | RAN3#NR Ad Hoc | R3-172634 | | | | Reflected agreed TP in RAN3#NR Ad Hoc in 2017-06 (Qingdao) | 0.2.0 | | +| 2017-08 | RAN3#97 | R3-173449 | | | | Reflected agreed TP in RAN3#97 | 0.3.0 | | +| 2017-10 | RAN3#97bis | R3-174237 | | | | Reflected agreed TP in RAN3#97bis | 0.4.0 | | +| 2017-10 | RAN3#97bis | R3-174258 | | | | Removed subclauses under 10.3 (moved to 38.470) | 0.4.1 | | +| 2017-11 | RAN3#98 | R3-175054 | | | | Reflected agreed TP in RAN3#98 | 0.5.0 | | +| 2017-12 | RP-78 | RP-172545 | | | | Submit to RAN Plenary#78 for approval | 1.0.0 | | +| 2017-12 | RP-78 | | | | | TR Approved by RAN plenary | 15.0.0 | | +| 2018-03 | RP-79 | RP-180468 | 0007 | 1 | - | Correction on intra-gNB-DU handover | 15.1.0 | | +| 2018-06 | RP-80 | RP-181237 | 0001 | 5 | B | Introduction of SA NR (38.401 Baseline CR covering RAN3 agreements) | 15.2.0 | | +| 2018-06 | RP-80 | RP-181240 | 0008 | 4 | B | Introduction of Separation of CP and UP for Split Option 2 (38.401 Baseline CR covering RAN3 agreements) | 15.2.0 | | +| 2018-06 | RP-80 | RP-181238 | 0012 | 1 | F | CR to TS38.401 on UL blockage | 15.2.0 | | +| 2018-06 | RP-80 | RP-181238 | 0014 | 1 | F | CR to 38.401 on DL User Data to DU | 15.2.0 | | +| 2018-06 | RP-80 | RP-181238 | 0016 | - | F | TP for 38.401 in supporting full configuration | 15.2.0 | | +| 2018-09 | RP-81 | RP-181922 | 0022 | 2 | F | NR Corrections (38.401 Baseline CR covering RAN3-101 agreements) | 15.3.0 | | +| 2018-12 | RP-82 | RP-182707 | 0023 | 3 | F | NR Corrections (TS 38.401 Baseline CR covering RAN3-101Bis and RAN3-102 agreements) | 15.4.0 | | +| 2019-03 | RP-83 | RP-190554 | 0025 | - | F | Correction to Intra-gNB-CU mobility | 15.5.0 | | +| 2019-03 | RP-83 | RP-190560 | 0026 | 1 | F | Correction from Rapporteur for 38.401 | 15.5.0 | | +| 2019-03 | RP-83 | RP-190554 | 0037 | 1 | F | About Cells Failed to be Activated IE | 15.5.0 | | +| 2019-07 | RP-84 | RP-191394 | 0039 | 3 | F | Correction of AMF set related statements | 15.6.0 | | +| 2019-07 | RP-84 | RP-191395 | 0063 | 1 | F | CR to 38.401 on Multiple TNLAs for F1-C and E1 | 15.6.0 | | +| 2019-07 | RP-84 | RP-191395 | 0065 | - | F | Multiple TNLAs for Xn-C | 15.6.0 | | +| 2019-07 | RP-84 | RP-191502 | 0043 | 2 | F | Clarify the support for multiple TNLAs for F1-C | 15.6.0 | | +| 2019-07 | RP-84 | RP-191397 | 0067 | 1 | F | RAN sharing with multiple Cell ID broadcast | 15.6.0 | | +| 2019-07 | RP-84 | RP-191396 | 0068 | 1 | F | Procedure description on optional IEs in CU to DU RRC information IE. | 15.6.0 | | +| 2019-12 | RP-86 | RP-192916 | 0045 | 4 | F | Correction to RRC Inactive transition | 15.7.0 | | +| 2019-12 | RP-86 | RP-192916 | 0104 | - | F | Inter-gNB-DU mobility using MCG SRB procedure | 15.7.0 | | +| 2019-12 | RP-86 | RP-192754 | 0105 | 2 | F | CR for RRC Container IE in Initial UL RRC Message Transfer procedure | 15.7.0 | | +| 2019-12 | RP-86 | RP-192908 | 0060 | 4 | B | Introduction of RIM in TS 38.401 | 16.0.0 | | +| 2019-12 | RP-86 | RP-192913 | 0075 | 1 | F | Trace function support stage-2 | 16.0.0 | | +| 2019-12 | RP-86 | RP-192913 | 0097 | 2 | F | Introduction of common time standard source | 16.0.0 | | +| 2019-12 | RP-86 | RP-192911 | 0107 | 2 | F | CR to 38.401 on corrections to ng-eNB deployment | 16.0.0 | | +| 2019-12 | RP-86 | RP-192908 | 0109 | - | B | Introduction of Cross-link Interference Management | 16.0.0 | | +| 2019-12 | RP-86 | RP-192910 | 0112 | - | B | Support of SN Resume during the RRCResume procedure | 16.0.0 | | +| 2020-03 | RP-87-e | RP-200425 | 0114 | - | D | Rapporteur updating of specification 38.401 | 16.1.0 | | +| 2020-07 | RP-88-e | RP-201077 | 0033 | 21 | B | BL CR to 38.401 Support for IAB | 16.2.0 | | +| 2020-07 | RP-88-e | RP-201082 | 0099 | 7 | B | Addition of MDT features | 16.2.0 | | +| 2020-07 | RP-88-e | RP-201080 | 0102 | 6 | B | BL CR NPN for TS 38.401 | 16.2.0 | | +| 2020-07 | RP-88-e | RP-201075 | 0110 | 6 | B | Baseline CR for introducing Rel-16 NR mobility enhancement | 16.2.0 | | +| 2020-07 | RP-88-e | RP-201082 | 0116 | 4 | B | Addition of SON features | 16.2.0 | | +| 2020-07 | RP-88-e | RP-201091 | 0122 | 1 | A | Correction for gNB-DU transmission stop description in the inter-gNB HO involving gNB-CU-UP change | 16.2.0 | | +| 2020-07 | RP-88-e | RP-201085 | 0130 | - | F | Rapporteur Corrections to 38.401 | 16.2.0 | | +| 2020-09 | RP-89-e | RP-201945 | 0115 | 7 | B | F1 support for positioning | 16.3.0 | | +| 2020-09 | RP-89-e | RP-201954 | 0135 | 2 | A | Adding missing steps querying the source DU's latest configuration during the inter-gNB-DU mobility for intra-NR | 16.3.0 | | +| 2020-09 | RP-89-e | RP-201954 | 0137 | 2 | A | SCTP association change when current SCTP association is failed | 16.3.0 | | +| 2020-09 | RP-89-e | RP-201947 | 0142 | 1 | F | Rapporteur Corrections to 38.401 | 16.3.0 | | +| 2020-09 | RP-89-e | RP-201954 | 0148 | 2 | A | Correction for intra-gNB-DU handover description | 16.3.0 | | +| 2020-12 | RP-90-e | RP-202311 | 0154 | 1 | F | Correction on CPC Complete Transfer | 16.4.0 | | +| 2020-12 | RP-90-e | RP-202311 | 0156 | 3 | F | Correction of Intra-system HO data forwarding | 16.4.0 | | +| 2021-03 | RP-91-e | RP-210231 | 0146 | 4 | F | Corrections on clarification of non-F1 traffic | 16.5.0 | | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2021-03 | RP-91-e | RP-210233 | 0168 | 1 | F | Stage-2 CR on transmission stop for Rel-16 DAPS handover | 16.5.0 | +| 2021-06 | RP-92-e | RP-211317 | 0172 | 1 | F | Correction on Signalling based MDT Activation [NR_SON_MDT-Core] | 16.6.0 | +| 2021-09 | RP-93-e | RP-211882 | 0170 | 3 | F | Suspend Configuration | 16.7.0 | +| 2021-12 | RP-94-e | RP-212864 | 0188 | 1 | F | Correction the text of stage 2 for DL Xn-U address information transfer (CR to TS 38.401, R16) | 16.8.0 | +| 2022-03 | RP-95-e | RP-220276 | 0193 | 2 | F | CR to 38.401: Correction on IPv6 Flow Label handling for IAB using IPsec tunnel mode | 16.9.0 | +| 2022-03 | RP-95-e | RP-220224 | 0153 | 13 | B | Introduction of NR MBS | 17.0.0 | +| 2022-03 | RP-95-e | RP-220221 | 0165 | 9 | B | BLCR to 38.401 Addition of SON features enhancement | 17.0.0 | +| 2022-03 | RP-95-e | RP-220935 | 0166 | 9 | B | BLCR to 38.401: Support of MDT enhancement | 17.0.0 | +| 2022-03 | RP-95-e | RP-220218 | 0174 | 7 | B | CPAC BL CR to TS38.401 | 17.0.0 | +| 2022-03 | RP-95-e | RP-220218 | 0176 | 10 | B | SCG BL CR to TS 38.401 | 17.0.0 | +| 2022-03 | RP-95-e | RP-220217 | 0178 | 7 | B | CR to 38.401: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution | 17.0.0 | +| 2022-03 | RP-95-e | RP-220222 | 0179 | 10 | B | BL CR to TS 38.401 on support of eIAB | 17.0.0 | +| 2022-03 | RP-95-e | RP-220230 | 0191 | 3 | B | Draft BL CR to TS 38.401 on RedCap UEs | 17.0.0 | +| 2022-03 | RP-95-e | RP-220233 | 0192 | 3 | B | RA-SDT BLCR to TS 38.401 | 17.0.0 | +| 2022-03 | RP-95-e | RP-220231 | 0195 | 3 | B | BL CR to TS38.401 on Rel-17 Sidelink Relay | 17.0.0 | +| 2022-03 | RP-95-e | RP-220233 | 0196 | 1 | B | CG-SDT BLCR to TS 38.401 | 17.0.0 | +| 2022-03 | RP-95-e | RP-220229 | 0198 | - | B | BL CR to TS38.401 for alignment of MDT and QoE | 17.0.0 | +| 2022-06 | RP-96 | RP-221136 | 0202 | 1 | F | Correction on SDT | 17.1.0 | +| 2022-06 | RP-96 | RP-221141 | 0207 | 1 | F | Corrections on MDT | 17.1.0 | +| 2022-06 | RP-96 | RP-221139 | 0209 | 1 | F | CR on TS38.401 for Rel-17 Sidelink Relay | 17.1.0 | +| 2022-06 | RP-96 | RP-221145 | 0210 | 2 | D | Rapporteur Update to TS 38.401 | 17.1.0 | +| 2022-06 | RP-96 | RP-221134 | 0214 | 2 | F | Remove the editor's notes related to consent information | 17.1.0 | +| 2022-06 | RP-96 | RP-221135 | 0220 | 1 | F | CR to 38.401 for Corrections on Overall procedures for CPAC | 17.1.0 | +| 2022-06 | RP-96 | RP-221141 | 0225 | 1 | F | Correction to 38.401 for SON features enhancement | 17.1.0 | +| 2022-06 | RP-96 | RP-221135 | 0228 | 2 | F | Correction for stage 2 on SCG (de)activation | 17.1.0 | +| 2022-06 | RP-96 | RP-221143 | 0232 | 1 | F | QoE Rel-17 Corrections | 17.1.0 | +| 2022-06 | RP-96 | RP-221128 | 0233 | - | F | Stage-2 corrections on IAB architecture | 17.1.0 | +| 2022-07 | | | | | | Editorial correction
- change the font style from "H1" to "normal" in clause 7.10. | 17.1.1 | +| 2022-09 | RP-97-e | RP-222189 | 0235 | 2 | F | Stage 2 Clarification on SDT to TS 38.401 | 17.2.0 | +| 2022-09 | RP-97-e | RP-222201 | 0239 | 2 | F | Correction on gNB-DU ID | 17.2.0 | +| 2022-09 | RP-97-e | RP-222189 | 0241 | 1 | F | Clarification to CG based SDT | 17.2.0 | +| 2022-09 | RP-97-e | RP-222183 | 0242 | - | F | Correction on protocol stack for IAB | 17.2.0 | +| 2022-09 | RP-97-e | RP-222188 | 0244 | - | F | Further Corrections for NR MBS | 17.2.0 | +| 2022-09 | RP-97-e | RP-222183 | 0246 | 2 | F | Corrections for Rel-17 IAB on topology adaptation | 17.2.0 | +| 2022-09 | RP-97-e | RP-222183 | 0250 | 2 | F | Corrections on IAB inter-CU topology adaptation | 17.2.0 | +| 2022-09 | RP-97-e | RP-222190 | 0252 | 1 | F | Correction to 38.401 for SL relay | 17.2.0 | +| 2022-12 | RP-98-e | RP-222882 | 0258 | 3 | F | Correction on F1-U tunnels for multicast MRB | 17.3.0 | +| 2022-12 | RP-98-e | RP-222882 | 0261 | 3 | F | Correction on Multicast Session Establishment | 17.3.0 | +| 2022-12 | RP-98-e | RP-222882 | 0262 | 2 | F | Correction on Multicast Mobility procedure | 17.3.0 | +| 2022-12 | RP-98-e | RP-222882 | 0263 | 1 | F | Correction on definition of Multicast F1-U Context | 17.3.0 | +| 2022-12 | RP-98-e | RP-222882 | 0266 | 1 | F | Introduction of further multicast session flow on MRB type reconfiguration | 17.3.0 | +| 2022-12 | RP-98-e | RP-222888 | 0269 | 2 | F | SL relay corrections | 17.3.0 | +| 2023-03 | RAN#99 | RP-230581 | 0273 | 3 | F | Clarification on SDT to 38.401 | 17.4.0 | +| 2023-03 | RAN#99 | RP-230583 | 0275 | 1 | F | Providing MBS QoS Flow Information during Multicast Session Establishment | 17.4.0 | +| 2023-03 | RAN#99 | RP-230586 | 0276 | 1 | F | Miscellaneous corrections for IAB inter-CU procedures | 17.4.0 | +| 2023-03 | RAN#99 | RP-230581 | 0279 | 1 | F | 38.401 Correction for Rel-17 SDT | 17.4.0 | +| 2023-03 | RAN#99 | RP-230583 | 0280 | 1 | F | Correction to TS 38.401 on Broadcast session establishment | 17.4.0 | +| 2023-06 | RAN#100 | RP-231074 | 0287 | 2 | F | Correction on Multicast session establishment | 17.5.0 | +| 2023-06 | RAN#100 | RP-231080 | 0290 | 2 | F | Correction on L2 U2N Relay Remote UE RRC procedures | 17.5.0 | +| 2023-09 | RAN#101 | RP-231895 | 0298 | 0 | A | Correction for change of gNB-CU-UP | 17.6.0 | +| 2023-09 | RAN#101 | RP-231901 | 0299 | 1 | F | Corrections to TS 38.401 for SL relay | 17.6.0 | +| 2023-09 | RAN#101 | RP-231902 | 0306 | 3 | F | Correction on non-SDT data arrival during on-going SDT session | 17.6.0 | +| 2023-12 | RAN#102 | RP-233854 | 0295 | 4 | F | Clarification of the RAN UE ID usage in stage-2 | 17.7.0 | +| 2023-12 | RAN#102 | RP-233852 | 0311 | - | F | Correction on small data transmission | 17.7.0 | +| 2023-12 | RAN#102 | RP-233818 | 0260 | 16 | B | Introduction of L1L2Mob and S-CPAC | 18.0.0 | +| 2023-12 | RAN#102 | RP-234067 | 0265 | 11 | B | Support of AI/ML in NG-RAN in the case of split architecture | 18.0.0 | +| 2023-12 | RAN#102 | RP-233833 | 0267 | 10 | B | Introduction of R18 QoE measurement enhancements | 18.0.0 | +| 2023-12 | RAN#102 | RP-233814 | 0274 | 7 | B | Support of Network-Controlled Repeater | 18.0.0 | +| 2023-12 | RAN#102 | RP-233829 | 0281 | 10 | B | Introduction of NR MBS enhancements | 18.0.0 | +| 2023-12 | RAN#102 | RP-233832 | 0282 | 6 | B | Addition of SON features enhancement | 18.0.0 | +| 2023-12 | RAN#102 | RP-233819 | 0284 | 8 | B | Introduction on MT-SDT | 18.0.0 | +| 2023-12 | RAN#102 | RP-233822 | 0285 | 9 | B | Introduction of NR SL relay enhancements | 18.0.0 | + +| Change history | | | | | | | | +|-----------------------|----------------|-------------|-----------|------------|------------|-----------------------------------------------------------------|--------------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2023-12 | RAN#102 | RP-233845 | 0302 | 3 | B | Support of oversize UL SDT Data Arrival [Large SDT Uplink Data] | 18.0.0 | +| 2023-12 | RAN#102 | RP-233834 | 0308 | 4 | B | Support for mobile IAB | 18.0.0 | +| 2023-12 | RAN#102 | RP-233838 | 0309 | 3 | B | Introduction of 5G Timing Resiliency and URLLC enhancements | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38413/0084ef0a1a9dee9842da698ab9b098ad_img.jpg b/marked/Rel-18/38_series/38413/0084ef0a1a9dee9842da698ab9b098ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61e8b390fcee711f2724fb1d9b933030bcaf6e2f --- /dev/null +++ b/marked/Rel-18/38_series/38413/0084ef0a1a9dee9842da698ab9b098ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:72be6e8e2102cc3218ec3b113551f308db4a29568cb698e80270307a468f9202 +size 14361 diff --git a/marked/Rel-18/38_series/38413/03a73cf37615028406f13c2aea732d60_img.jpg b/marked/Rel-18/38_series/38413/03a73cf37615028406f13c2aea732d60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5846c9afb70d4848e762a969f2f79644c1ee2911 --- /dev/null +++ b/marked/Rel-18/38_series/38413/03a73cf37615028406f13c2aea732d60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2ed1d47c183ba5185a7d52a48d076fb4b607f053d641bd28ddea94de2f1389d +size 21339 diff --git a/marked/Rel-18/38_series/38413/09036266c6dba47efb2613ceaebe2b19_img.jpg b/marked/Rel-18/38_series/38413/09036266c6dba47efb2613ceaebe2b19_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69e01dfcb9c0da9815e4b99259d55f5a17b18b65 --- /dev/null +++ b/marked/Rel-18/38_series/38413/09036266c6dba47efb2613ceaebe2b19_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b1163de8b361607cbb52a6a49ad8b6a13e34b4321c4a9d94e6e93f90d9b85f2 +size 12619 diff --git a/marked/Rel-18/38_series/38413/0db2dd2a5c02140f5b395569f17ab91d_img.jpg b/marked/Rel-18/38_series/38413/0db2dd2a5c02140f5b395569f17ab91d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ccc22cf47bd671a3eacb2fc8ef13fccf26858eb0 --- /dev/null +++ b/marked/Rel-18/38_series/38413/0db2dd2a5c02140f5b395569f17ab91d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0da155b95bd489b10366a90b8e21c90e3c92e1e00d2537ddb61339ec65614d48 +size 12414 diff --git a/marked/Rel-18/38_series/38413/10cc1e74f2b71404f021bb8b3cec0ff0_img.jpg b/marked/Rel-18/38_series/38413/10cc1e74f2b71404f021bb8b3cec0ff0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2938c1d2e2ab2ccf44fa40878ad05a022b12f8a8 --- /dev/null +++ b/marked/Rel-18/38_series/38413/10cc1e74f2b71404f021bb8b3cec0ff0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2f8ecf0fa55ceef95a7b4af3daac1ed1f5f5b28dc17c63ad12c49f852fde319 +size 19795 diff --git a/marked/Rel-18/38_series/38413/131048f570c4d9960a21e7dd73c4fd6b_img.jpg b/marked/Rel-18/38_series/38413/131048f570c4d9960a21e7dd73c4fd6b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..137e4fcbe126f89fbbf913f3156f27f151cadb15 --- /dev/null +++ b/marked/Rel-18/38_series/38413/131048f570c4d9960a21e7dd73c4fd6b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:38c3d825381318fbec9d87077091851cd53910be0a16e3e445151b08d48f2e34 +size 30589 diff --git a/marked/Rel-18/38_series/38413/161bf538038ac4e9c2cd42f8d9dbd732_img.jpg b/marked/Rel-18/38_series/38413/161bf538038ac4e9c2cd42f8d9dbd732_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f449f35a7dd12fe4a394dc8c69c3c7d8499ba66 --- /dev/null +++ b/marked/Rel-18/38_series/38413/161bf538038ac4e9c2cd42f8d9dbd732_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe6bc0df77dce9577d90efd2843cc0cb491bf647eb921d11825e87aa5067f682 +size 17530 diff --git a/marked/Rel-18/38_series/38413/18b87e4ce7ef441f5620b8d6539a2939_img.jpg b/marked/Rel-18/38_series/38413/18b87e4ce7ef441f5620b8d6539a2939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00de88b555b349e5ef18d1777cc5cb040f4347aa --- /dev/null +++ b/marked/Rel-18/38_series/38413/18b87e4ce7ef441f5620b8d6539a2939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02fad76282aa319dea9f5979e825e1f4af6b6d44b140a98e6167521cdc3693e7 +size 27072 diff --git a/marked/Rel-18/38_series/38413/18d7d8de298d79e7bc87af5217f11203_img.jpg b/marked/Rel-18/38_series/38413/18d7d8de298d79e7bc87af5217f11203_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..299ccff41d6acb66faf9513150220e6e407864c9 --- /dev/null +++ b/marked/Rel-18/38_series/38413/18d7d8de298d79e7bc87af5217f11203_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ac4c3a683be120f3d5ca1cd54e84d918f0c484d4d19ba84e0e5ceeccc6573b9e +size 15198 diff --git a/marked/Rel-18/38_series/38413/18fb2f2a7bdbb03074578da43004abaa_img.jpg b/marked/Rel-18/38_series/38413/18fb2f2a7bdbb03074578da43004abaa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d2796bafe63c2fe73ec70995860389ecb9ad886f --- /dev/null +++ b/marked/Rel-18/38_series/38413/18fb2f2a7bdbb03074578da43004abaa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9eb3445d9a5c91632ac71803b9a36fc5a1c54554efd916c6d66960615cb2c9bb +size 20547 diff --git a/marked/Rel-18/38_series/38413/199a8b4c5c620006757a17e930769566_img.jpg b/marked/Rel-18/38_series/38413/199a8b4c5c620006757a17e930769566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1fc39940e4db8c9d068ed4e3b92188c0c3e7e44 --- /dev/null +++ b/marked/Rel-18/38_series/38413/199a8b4c5c620006757a17e930769566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c01a503e6a4b2bd61a2c5e22c32091229f38dc816a5e9b1de7f459ea9e2b63f +size 12196 diff --git a/marked/Rel-18/38_series/38413/1bd6a020aa71784ed74367899560cbb9_img.jpg b/marked/Rel-18/38_series/38413/1bd6a020aa71784ed74367899560cbb9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dbb719ff27c011e4ff79619250cf6971dfada258 --- /dev/null +++ b/marked/Rel-18/38_series/38413/1bd6a020aa71784ed74367899560cbb9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2a99db2caca68afc5f4d0e639d9497c8ed62a17b3b49363b73a0eb76c94a174 +size 13784 diff --git a/marked/Rel-18/38_series/38413/1fa325e34e0974a6426c93e541a7ee86_img.jpg b/marked/Rel-18/38_series/38413/1fa325e34e0974a6426c93e541a7ee86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..977e69a55d5b2d99b3712ba89555980a666cf6b8 --- /dev/null +++ b/marked/Rel-18/38_series/38413/1fa325e34e0974a6426c93e541a7ee86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c25bf6f3973f1d7144af0bdcf4ad53018d8689a15abfda744d2c9196113b5ac1 +size 17508 diff --git a/marked/Rel-18/38_series/38413/21c8a1f65b4718372aadf6a1cc10204d_img.jpg b/marked/Rel-18/38_series/38413/21c8a1f65b4718372aadf6a1cc10204d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e3bb166e5e1a03aab2b1443545b761f2035cee2f --- /dev/null +++ b/marked/Rel-18/38_series/38413/21c8a1f65b4718372aadf6a1cc10204d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:096238f221df21f057ab0e85dd075398313df7929dad9734e03580025c560513 +size 12445 diff --git a/marked/Rel-18/38_series/38413/23cb65390082ab306c15bd3d8196135e_img.jpg b/marked/Rel-18/38_series/38413/23cb65390082ab306c15bd3d8196135e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..87b202c268177df35e27c7b09f88311c8a5656ba --- /dev/null +++ b/marked/Rel-18/38_series/38413/23cb65390082ab306c15bd3d8196135e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a3e582e4a4fc7699618e51dd8c98ccc331db210ac0ea4ba5afdee77a76f81f3a +size 11689 diff --git a/marked/Rel-18/38_series/38413/24b10c86fe55f7126e355d9bc6fef7b9_img.jpg b/marked/Rel-18/38_series/38413/24b10c86fe55f7126e355d9bc6fef7b9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c5d7e1b06b7a8555719264d0824548bc13c586e2 --- /dev/null +++ b/marked/Rel-18/38_series/38413/24b10c86fe55f7126e355d9bc6fef7b9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca6d0339d59479a3db1f182b65fcae529da80dde31bc9741b27be11d4ccfc1fa +size 23848 diff --git a/marked/Rel-18/38_series/38413/276d5f4022bc6b9e4687f9ba4fc7594c_img.jpg b/marked/Rel-18/38_series/38413/276d5f4022bc6b9e4687f9ba4fc7594c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..57c60ebe9269c7082e67117160d68e55a7e912f6 --- /dev/null +++ b/marked/Rel-18/38_series/38413/276d5f4022bc6b9e4687f9ba4fc7594c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19820d44df69e180e256c2e70baa6f9b431c0a4aa7a56f09116c0663d1170076 +size 13367 diff --git a/marked/Rel-18/38_series/38413/2dca0da216307a42a155676028e18ee6_img.jpg b/marked/Rel-18/38_series/38413/2dca0da216307a42a155676028e18ee6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c217c18c53a250495572186ad23dbca213ac6839 --- /dev/null +++ b/marked/Rel-18/38_series/38413/2dca0da216307a42a155676028e18ee6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14edd40de773fb9ef9ea7cd51c627aeef0f04130b055ec3a8426391d665bff5d +size 16274 diff --git a/marked/Rel-18/38_series/38413/2e3b1ae09da2cba02f0bb8a531f1515e_img.jpg b/marked/Rel-18/38_series/38413/2e3b1ae09da2cba02f0bb8a531f1515e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67dc8a3e3a46f103e619781e3134b8a7562f74dc --- /dev/null +++ b/marked/Rel-18/38_series/38413/2e3b1ae09da2cba02f0bb8a531f1515e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:543856e81ae75edc96566ca797b54c5a40ad53ac365eff261afffcc479c05bce +size 17082 diff --git a/marked/Rel-18/38_series/38413/300130063df853c2bf2589510f69dbba_img.jpg b/marked/Rel-18/38_series/38413/300130063df853c2bf2589510f69dbba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4efb660b121a30b4017d50ca1923d231a6258221 --- /dev/null +++ b/marked/Rel-18/38_series/38413/300130063df853c2bf2589510f69dbba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:edd10af2190143b40d792ee2d78893342205997a3000e2ddd6ad5949760408ce +size 17141 diff --git a/marked/Rel-18/38_series/38413/3295c6ffe9f6d00c3811c37d327ac844_img.jpg b/marked/Rel-18/38_series/38413/3295c6ffe9f6d00c3811c37d327ac844_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f5281fc72b7007a5476f3ddb7fb01cdd9bb26197 --- /dev/null +++ b/marked/Rel-18/38_series/38413/3295c6ffe9f6d00c3811c37d327ac844_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f82966591f3bcbe69a36f0e913e33b6b30f4d59fb7aed58eb730fb823b403421 +size 28002 diff --git a/marked/Rel-18/38_series/38413/3688d0bf7f55bb025d194f921007f471_img.jpg b/marked/Rel-18/38_series/38413/3688d0bf7f55bb025d194f921007f471_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f1e39600b8645497f4949eac00ec71eda561909 --- /dev/null +++ b/marked/Rel-18/38_series/38413/3688d0bf7f55bb025d194f921007f471_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:668dd0ff28a4829fd5cfeb35e963e8916791bd11f0fcd34cbc47f03720644252 +size 12697 diff --git a/marked/Rel-18/38_series/38413/377087fbf1dd0a11c3a435bcd7b6fc35_img.jpg b/marked/Rel-18/38_series/38413/377087fbf1dd0a11c3a435bcd7b6fc35_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e3098a8ae0195a4e2bbf21f95d5ea2ce93ddada8 --- /dev/null +++ b/marked/Rel-18/38_series/38413/377087fbf1dd0a11c3a435bcd7b6fc35_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e17e0a10ade3a713e18c280969bd668555d1243c6c23c106f25e7b77bc13fdb3 +size 15436 diff --git a/marked/Rel-18/38_series/38413/3941735fafadf9a59b811f67fcdca7b3_img.jpg b/marked/Rel-18/38_series/38413/3941735fafadf9a59b811f67fcdca7b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..007eda7edf1149d4fc59ebb1a8a86ce5a72d1bca --- /dev/null +++ b/marked/Rel-18/38_series/38413/3941735fafadf9a59b811f67fcdca7b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c9e1522516ac7a26ad602b781ac0cec74c4bd05d6019e1cbb5771469c8939b7c +size 16589 diff --git a/marked/Rel-18/38_series/38413/3d590ad29ecfe728f07432e6fcb59064_img.jpg b/marked/Rel-18/38_series/38413/3d590ad29ecfe728f07432e6fcb59064_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6cbacb7803b9f45ac0395c0273c17487d47d20e2 --- /dev/null +++ b/marked/Rel-18/38_series/38413/3d590ad29ecfe728f07432e6fcb59064_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c6d711ac152897ee228abd86c0dc87fbb3fd2850deb023dfd2558473c0f6ae11 +size 19026 diff --git a/marked/Rel-18/38_series/38413/3d9614f297f466a7c9b0f4b74f6aaf03_img.jpg b/marked/Rel-18/38_series/38413/3d9614f297f466a7c9b0f4b74f6aaf03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7857c990c9165a43017e1ab7f861139b7148b865 --- /dev/null +++ b/marked/Rel-18/38_series/38413/3d9614f297f466a7c9b0f4b74f6aaf03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68da0623bae283fa3fa8045f72277d6fd572bc19c705eaad35a9167f52ec0ac1 +size 12563 diff --git a/marked/Rel-18/38_series/38413/3f2ccb513ccdda4c3e19aea59f7f6215_img.jpg b/marked/Rel-18/38_series/38413/3f2ccb513ccdda4c3e19aea59f7f6215_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42ee85e7310f44d0641848c54e5b8d0a985f1a68 --- /dev/null +++ b/marked/Rel-18/38_series/38413/3f2ccb513ccdda4c3e19aea59f7f6215_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5dfe8321ccb745fec421712d47844b9380ba215ba478e36d45421d3c1482482 +size 13295 diff --git a/marked/Rel-18/38_series/38413/458fdbcb4015a4ee90bd84809afc4aac_img.jpg b/marked/Rel-18/38_series/38413/458fdbcb4015a4ee90bd84809afc4aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..467bcf57fb91a0f8fe141fa6f7b4277d3a510ac5 --- /dev/null +++ b/marked/Rel-18/38_series/38413/458fdbcb4015a4ee90bd84809afc4aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f0313dc84f428f76e71ce4ee811d643c5a85e5c450a6fcef95544eec3ad148c4 +size 15869 diff --git a/marked/Rel-18/38_series/38413/461ef997feb933486effd3b0d3504016_img.jpg b/marked/Rel-18/38_series/38413/461ef997feb933486effd3b0d3504016_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9894e9dbdc76b543cf172f632fc5df23c240d8cb --- /dev/null +++ b/marked/Rel-18/38_series/38413/461ef997feb933486effd3b0d3504016_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b32f3da12072e1e446daf481b3500a3b20c88c7f63331f60b09483e1d640ae35 +size 12845 diff --git a/marked/Rel-18/38_series/38413/46b47a38697e3aedb09cccd7eba47192_img.jpg b/marked/Rel-18/38_series/38413/46b47a38697e3aedb09cccd7eba47192_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca1c9a0a2a27dbb8281cf380f75ba07f711e745a --- /dev/null +++ b/marked/Rel-18/38_series/38413/46b47a38697e3aedb09cccd7eba47192_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6c2bedaec2a0225a5c2948a8885328da86769352ea852be907442696de14d449 +size 12601 diff --git a/marked/Rel-18/38_series/38413/48fecf94dd9fb955caddbf2fb01b7b9b_img.jpg b/marked/Rel-18/38_series/38413/48fecf94dd9fb955caddbf2fb01b7b9b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..666df5ca7e61b7112def1253a49df1d8c7641bca --- /dev/null +++ b/marked/Rel-18/38_series/38413/48fecf94dd9fb955caddbf2fb01b7b9b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:549f273c9df0b9c0bba025f0eb812c0b0dd2cb7defc12686a9b20f0400699c83 +size 22929 diff --git a/marked/Rel-18/38_series/38413/4bb669bb31262e53e4f3c8ec0fd7624a_img.jpg b/marked/Rel-18/38_series/38413/4bb669bb31262e53e4f3c8ec0fd7624a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f71d26c64a9a68cc90f12a24d9a9f35bf5dac93 --- /dev/null +++ b/marked/Rel-18/38_series/38413/4bb669bb31262e53e4f3c8ec0fd7624a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6abf07bef9aee7a9fae76690fdfe62580a11734c06a44ead319c6d28b8148beb +size 12244 diff --git a/marked/Rel-18/38_series/38413/4cb2d3c8066966514fdc92491fe8feed_img.jpg b/marked/Rel-18/38_series/38413/4cb2d3c8066966514fdc92491fe8feed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c0c5789910142d3fdcd5c8cec45e77a0ee9c362c --- /dev/null +++ b/marked/Rel-18/38_series/38413/4cb2d3c8066966514fdc92491fe8feed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:feb7b23d66485981fd14177cc20b33d472e6d44f7ade2d77419d8ad935abed8b +size 13487 diff --git a/marked/Rel-18/38_series/38413/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg b/marked/Rel-18/38_series/38413/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8546a17fb14cb6b8317eb25a3832a196f4b6e053 --- /dev/null +++ b/marked/Rel-18/38_series/38413/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8ae0401e2976d4679e12b19333142c4ee84a5f5bb61814c2e135c3d9529ac11 +size 16345 diff --git a/marked/Rel-18/38_series/38413/53d32fee66efd06385d5d38b01b1a663_img.jpg b/marked/Rel-18/38_series/38413/53d32fee66efd06385d5d38b01b1a663_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0215941edc2335010eb9c3f5785696f03a874f5d --- /dev/null +++ b/marked/Rel-18/38_series/38413/53d32fee66efd06385d5d38b01b1a663_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d2a24a547ed39ab8324756c3f869f41d3e6574ff0b78e5eb93e71ac72e2af60 +size 23560 diff --git a/marked/Rel-18/38_series/38413/58e07d355a649f1fbd8a041b88207829_img.jpg b/marked/Rel-18/38_series/38413/58e07d355a649f1fbd8a041b88207829_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22a09338f79f7540362f2e43c1a16b7faa94ba87 --- /dev/null +++ b/marked/Rel-18/38_series/38413/58e07d355a649f1fbd8a041b88207829_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:278db04356b29ff8538ed7293006ffba1a3dc2b36893c1c46fa81bc83467368b +size 12135 diff --git a/marked/Rel-18/38_series/38413/5de3d4570bdb30251a009a25795993e9_img.jpg b/marked/Rel-18/38_series/38413/5de3d4570bdb30251a009a25795993e9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f91912b91fc5e65a1b1ce7e505ddcfc31507bac --- /dev/null +++ b/marked/Rel-18/38_series/38413/5de3d4570bdb30251a009a25795993e9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da79b8b0ddc4d0a4d34c6b1ea49b0cfcb27506be88a1a0e82a6fc1d169165683 +size 13184 diff --git a/marked/Rel-18/38_series/38413/5ec3284657e4df0df3653dd61d0ecd13_img.jpg b/marked/Rel-18/38_series/38413/5ec3284657e4df0df3653dd61d0ecd13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f38c4398fe8ea42e4bbee51fe62dee89f180be4d --- /dev/null +++ b/marked/Rel-18/38_series/38413/5ec3284657e4df0df3653dd61d0ecd13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0621b514cf12f11bd53b618e340f60335aec6c9d72570ee3ca31c0359a2e6b4e +size 12973 diff --git a/marked/Rel-18/38_series/38413/5efe6377e22b9ab76a19a70da29976b9_img.jpg b/marked/Rel-18/38_series/38413/5efe6377e22b9ab76a19a70da29976b9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7f38d16837d4fb16991df3f4cfb9f48f46e5682d --- /dev/null +++ b/marked/Rel-18/38_series/38413/5efe6377e22b9ab76a19a70da29976b9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e191f94f1152ed66304cb433ac5fe31e2b23a4ee5528676cd21d254b7c35fe85 +size 13036 diff --git a/marked/Rel-18/38_series/38413/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38413/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..213bec3f4e78bcb891afab76563d60fc933baf47 --- /dev/null +++ b/marked/Rel-18/38_series/38413/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f479c679e7e023b4e208384e28e9e3d5bdc8eba80a210569d96e951ad9df80c1 +size 9497 diff --git a/marked/Rel-18/38_series/38413/62ee64afa2d368d732de66628cf2c841_img.jpg b/marked/Rel-18/38_series/38413/62ee64afa2d368d732de66628cf2c841_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a4cb9672628ce85ca85bb71373693c8b3c4cf360 --- /dev/null +++ b/marked/Rel-18/38_series/38413/62ee64afa2d368d732de66628cf2c841_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e00ece12c0626bd4067f63b3ef72a5b9078e98cd040c459110f7269833bc4555 +size 15320 diff --git a/marked/Rel-18/38_series/38413/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38413/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e7e5c06c6ee6b5bad97031fcfbecd546e1641251 --- /dev/null +++ b/marked/Rel-18/38_series/38413/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:41981b86a7d6f950f557ef3851a8f9fc5f7b30df9fae943ceacb21469db40386 +size 6798 diff --git a/marked/Rel-18/38_series/38413/64cda8ce20067bc360ce2f3a5c9352b7_img.jpg b/marked/Rel-18/38_series/38413/64cda8ce20067bc360ce2f3a5c9352b7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2548efb54103d66bd9f00d32e68559486f33f45d --- /dev/null +++ b/marked/Rel-18/38_series/38413/64cda8ce20067bc360ce2f3a5c9352b7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:337947231670a1e63032869581082466de52c6815d52809d75c68f8a0b147ffc +size 24645 diff --git a/marked/Rel-18/38_series/38413/653c8e65f33b3bb03c92688243b27ab5_img.jpg b/marked/Rel-18/38_series/38413/653c8e65f33b3bb03c92688243b27ab5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d95ce82f929a56a257b5922aaebb89b3eacee7be --- /dev/null +++ b/marked/Rel-18/38_series/38413/653c8e65f33b3bb03c92688243b27ab5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:30b8e99eeb5766660dfa3b40e56d883ef991787523524c3cac567f589c60664f +size 18678 diff --git a/marked/Rel-18/38_series/38413/66d5189a924662748cac6a9b22a272e9_img.jpg b/marked/Rel-18/38_series/38413/66d5189a924662748cac6a9b22a272e9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f2d50ae8b1d0f369e9c6ec5f5dc6baec7b13d202 --- /dev/null +++ b/marked/Rel-18/38_series/38413/66d5189a924662748cac6a9b22a272e9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96b1efb62d65f35d57df81c53dfde3b579c4543e7334340f52371493dd9df7bc +size 11948 diff --git a/marked/Rel-18/38_series/38413/6ac768852938a68d913005126c4d9e8a_img.jpg b/marked/Rel-18/38_series/38413/6ac768852938a68d913005126c4d9e8a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e904963cf731ff487a41ef7714df62a56f31b72 --- /dev/null +++ b/marked/Rel-18/38_series/38413/6ac768852938a68d913005126c4d9e8a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b127703552a6057cd3419eeaf81c77aa940a72dc792f30d76d55068507856042 +size 25417 diff --git a/marked/Rel-18/38_series/38413/6b0035ff72f9d3c2ef6141caf9a6c743_img.jpg b/marked/Rel-18/38_series/38413/6b0035ff72f9d3c2ef6141caf9a6c743_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b1a6a933a44859826b667de0346fd0be47d4e4e --- /dev/null +++ b/marked/Rel-18/38_series/38413/6b0035ff72f9d3c2ef6141caf9a6c743_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5a84c17d5576c5b5b3ad9810112070a8e77ebb5755f4c33999bd2778602a984 +size 13612 diff --git a/marked/Rel-18/38_series/38413/6e9fbc3d95eb2b3f67cbbbd5de0c3999_img.jpg b/marked/Rel-18/38_series/38413/6e9fbc3d95eb2b3f67cbbbd5de0c3999_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4619ce9b9266adfea1fa0e7985c13cc1f34896b8 --- /dev/null +++ b/marked/Rel-18/38_series/38413/6e9fbc3d95eb2b3f67cbbbd5de0c3999_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d73ba39377a546b9ebad3cdadf6fa4aa15280e2ca8d3ee78c54306149640549e +size 12368 diff --git a/marked/Rel-18/38_series/38413/747516f5861a0ddf31e3851da8e34b95_img.jpg b/marked/Rel-18/38_series/38413/747516f5861a0ddf31e3851da8e34b95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e591d097aa1ff3069b0402979d8cc378249c7043 --- /dev/null +++ b/marked/Rel-18/38_series/38413/747516f5861a0ddf31e3851da8e34b95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:38dc2ad40d9b71a5a2c1a3b6431a79e56349260102d74bd77be3f51c8c5df0a9 +size 27830 diff --git a/marked/Rel-18/38_series/38413/77534ce9b1e09b533f730d8f45e01956_img.jpg b/marked/Rel-18/38_series/38413/77534ce9b1e09b533f730d8f45e01956_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28af31673bee652da19c319a41e107529298f81f --- /dev/null +++ b/marked/Rel-18/38_series/38413/77534ce9b1e09b533f730d8f45e01956_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e68aa864204009f917c718b49b09bd5450749d91514a854ab85a9383a5345a4 +size 12163 diff --git a/marked/Rel-18/38_series/38413/7b2d685b805535c1e94aee1365753b92_img.jpg b/marked/Rel-18/38_series/38413/7b2d685b805535c1e94aee1365753b92_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d31632b438587b3f933ea166c9afaf511b7936f --- /dev/null +++ b/marked/Rel-18/38_series/38413/7b2d685b805535c1e94aee1365753b92_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c32326e8af693003b86b9f1dc70c30e3463b1660c7946b5a681e6928eb26ff58 +size 12428 diff --git a/marked/Rel-18/38_series/38413/7c239d0d8d8e5ee7edb275ae16c2269e_img.jpg b/marked/Rel-18/38_series/38413/7c239d0d8d8e5ee7edb275ae16c2269e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..95074f618bc115ed3fe03f76ca7f598b480407b3 --- /dev/null +++ b/marked/Rel-18/38_series/38413/7c239d0d8d8e5ee7edb275ae16c2269e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6ba7cc29e35b965c4687737d829286e089c126910c724a8de419b26ced6cb4ec +size 25170 diff --git a/marked/Rel-18/38_series/38413/7d0629aa168bf800e491bcbd1979f262_img.jpg b/marked/Rel-18/38_series/38413/7d0629aa168bf800e491bcbd1979f262_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aaf9196ee5f42b1b22e3adee1ba857fdb1cbbc58 --- /dev/null +++ b/marked/Rel-18/38_series/38413/7d0629aa168bf800e491bcbd1979f262_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8731f3c51e2bf7eaffd14334bb2b7bdb2b7fc42a401e46650916102ff38e3075 +size 13224 diff --git a/marked/Rel-18/38_series/38413/7f7718a1d18d1f9055d85871d02364b3_img.jpg b/marked/Rel-18/38_series/38413/7f7718a1d18d1f9055d85871d02364b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..826747f54b8fa921ddd67d2f6d83c45578fdde11 --- /dev/null +++ b/marked/Rel-18/38_series/38413/7f7718a1d18d1f9055d85871d02364b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:86a8c0ea5a1ceecb92569050a00fd2a808f73a766b4cf91716cd3129b6ff3896 +size 11538 diff --git a/marked/Rel-18/38_series/38413/82340ab4d7b2db48ce408d8db6fde6b6_img.jpg b/marked/Rel-18/38_series/38413/82340ab4d7b2db48ce408d8db6fde6b6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ce1e4c217e847ea74cef8746526ed23118608f6a --- /dev/null +++ b/marked/Rel-18/38_series/38413/82340ab4d7b2db48ce408d8db6fde6b6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96dad389f7b5fa4eb146effefc425f2932acf42cf982f74231317f44b22cb556 +size 12321 diff --git a/marked/Rel-18/38_series/38413/8277ec2f29c84d97cbe70bc413a42cd1_img.jpg b/marked/Rel-18/38_series/38413/8277ec2f29c84d97cbe70bc413a42cd1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ec234e79273b1318927d4979531a1c88fd49a26 --- /dev/null +++ b/marked/Rel-18/38_series/38413/8277ec2f29c84d97cbe70bc413a42cd1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e5d7c9f3aac09d3b6f9026b6d4c8b565efe112fc482eb4318878c2f2e793e7b +size 11395 diff --git a/marked/Rel-18/38_series/38413/8395ccdee8a80af834aca2bdfd7f9a9b_img.jpg b/marked/Rel-18/38_series/38413/8395ccdee8a80af834aca2bdfd7f9a9b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be8b02d99bacaeb73e0ce277b228a3ff88418869 --- /dev/null +++ b/marked/Rel-18/38_series/38413/8395ccdee8a80af834aca2bdfd7f9a9b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5443b6cd3e0d03b2868d2038bfca77152113f3ad383a7120ea9e423b9b78be8a +size 11326 diff --git a/marked/Rel-18/38_series/38413/85680f3dcbe15424dd54fa3fd9e1c90d_img.jpg b/marked/Rel-18/38_series/38413/85680f3dcbe15424dd54fa3fd9e1c90d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d2bd0165bc16b659bf7abb56e132a403b144121 --- /dev/null +++ b/marked/Rel-18/38_series/38413/85680f3dcbe15424dd54fa3fd9e1c90d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ee2fb4e37c36730c6b257d8d79d300d6fe8438ecb8b3f62f5c19458d723330e +size 12433 diff --git a/marked/Rel-18/38_series/38413/8768e42bf1062f1af11f259fc52a92e9_img.jpg b/marked/Rel-18/38_series/38413/8768e42bf1062f1af11f259fc52a92e9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b9f998a84a3135c95b372ce22990a39d83262d14 --- /dev/null +++ b/marked/Rel-18/38_series/38413/8768e42bf1062f1af11f259fc52a92e9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c5128b544724f7ef07446c08e747a2eea1a027fbe8c568ccdafa655dd5f11e5 +size 13367 diff --git a/marked/Rel-18/38_series/38413/8a9a4dc9f8f886d283f9a75e5b2287f4_img.jpg b/marked/Rel-18/38_series/38413/8a9a4dc9f8f886d283f9a75e5b2287f4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c63a8fec5627eb2969dfe6efbef5635cdc19e7a --- /dev/null +++ b/marked/Rel-18/38_series/38413/8a9a4dc9f8f886d283f9a75e5b2287f4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11cacc70629cb4f95561096c1b406592a7f4e5904d89dafa8c582a147a2def35 +size 13080 diff --git a/marked/Rel-18/38_series/38413/8b5a2bf5517051acf8bcc2587bcb73a1_img.jpg b/marked/Rel-18/38_series/38413/8b5a2bf5517051acf8bcc2587bcb73a1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..489edbf266bbac0b740329ad83fab053cc691437 --- /dev/null +++ b/marked/Rel-18/38_series/38413/8b5a2bf5517051acf8bcc2587bcb73a1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b11937faf2eb8b654917ef3889e1424859521fd5c6cffb13d03ecc9ff9f35da +size 12960 diff --git a/marked/Rel-18/38_series/38413/8fce89f02626b8a0c50e2245bc3e7ce7_img.jpg b/marked/Rel-18/38_series/38413/8fce89f02626b8a0c50e2245bc3e7ce7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..372a63fcdfff023b519fbac83cd41a63276fd9f4 --- /dev/null +++ b/marked/Rel-18/38_series/38413/8fce89f02626b8a0c50e2245bc3e7ce7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:92ad03b2bea5480c849d90c501dc0cdca686b02eede24753364ec9a6a3ad1637 +size 24831 diff --git a/marked/Rel-18/38_series/38413/93bc9e79386c488b5f130ab90aacf464_img.jpg b/marked/Rel-18/38_series/38413/93bc9e79386c488b5f130ab90aacf464_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..96960873ce9f23edb856f8003f6a0a70892848fa --- /dev/null +++ b/marked/Rel-18/38_series/38413/93bc9e79386c488b5f130ab90aacf464_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83af43fee633ab85d22159d3356ba959f5977664486015f3e9330f35e98f95c3 +size 26166 diff --git a/marked/Rel-18/38_series/38413/97bac2cf7c2b7516804ea0ce39211258_img.jpg b/marked/Rel-18/38_series/38413/97bac2cf7c2b7516804ea0ce39211258_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5d7dc8d5570a82d6601a5a48cdb8103ed069620 --- /dev/null +++ b/marked/Rel-18/38_series/38413/97bac2cf7c2b7516804ea0ce39211258_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0bc3bdd695efdc20f520ea4146240c82174503f56baf922cf8c071144d682810 +size 12446 diff --git a/marked/Rel-18/38_series/38413/9b9dc99e34bb68ec85598e9d4bfda777_img.jpg b/marked/Rel-18/38_series/38413/9b9dc99e34bb68ec85598e9d4bfda777_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..507af7de750ce0930e82c30882e000cb5c48250c --- /dev/null +++ b/marked/Rel-18/38_series/38413/9b9dc99e34bb68ec85598e9d4bfda777_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:01400d9bb2f6e214f5c09c81d7f09b75aeca4de37a584d868c071cc84fee9215 +size 12508 diff --git a/marked/Rel-18/38_series/38413/9eba62b255ea4757497c72582d0fa54e_img.jpg b/marked/Rel-18/38_series/38413/9eba62b255ea4757497c72582d0fa54e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1bf75bbd9337f3c39556cd0105f9f3f38c2f86c0 --- /dev/null +++ b/marked/Rel-18/38_series/38413/9eba62b255ea4757497c72582d0fa54e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a4b4f4e95502613c2ebccad5b33b631e7e8b2ec6354c8139da698c50980c719d +size 12089 diff --git a/marked/Rel-18/38_series/38413/9f50279046b74a4e66a1a0144c3b1d11_img.jpg b/marked/Rel-18/38_series/38413/9f50279046b74a4e66a1a0144c3b1d11_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc823b262df43098fdcdd5860e7a6a0875776fdf --- /dev/null +++ b/marked/Rel-18/38_series/38413/9f50279046b74a4e66a1a0144c3b1d11_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:77d1d3a8e83eb191f8448961fa5173732ec63e93ee903c67a89dbb14b5d19ef9 +size 14222 diff --git a/marked/Rel-18/38_series/38413/9ff197cc407757d6a88e5e9f353864d0_img.jpg b/marked/Rel-18/38_series/38413/9ff197cc407757d6a88e5e9f353864d0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e1e8dc41b6a3bd4ebce52f4a23f23a5e95d68ad9 --- /dev/null +++ b/marked/Rel-18/38_series/38413/9ff197cc407757d6a88e5e9f353864d0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bbfaabb748c6d19d3aab72d6e9ed08592d1317f9cca0953ffd7c536245f9ef10 +size 12389 diff --git a/marked/Rel-18/38_series/38413/a3083eec2a883ee8327b3c24174df6a9_img.jpg b/marked/Rel-18/38_series/38413/a3083eec2a883ee8327b3c24174df6a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e967581216594573d861d34eec56e62b86661000 --- /dev/null +++ b/marked/Rel-18/38_series/38413/a3083eec2a883ee8327b3c24174df6a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:175e07741f2da3f1685bb5a070f5bf5b364ac060fdf7d69c02a4fa12a739beab +size 14587 diff --git a/marked/Rel-18/38_series/38413/a4b868a176f7e0448ee72483727e9f6f_img.jpg b/marked/Rel-18/38_series/38413/a4b868a176f7e0448ee72483727e9f6f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..72f77cea9f016ff446ee4966614e0c9474319716 --- /dev/null +++ b/marked/Rel-18/38_series/38413/a4b868a176f7e0448ee72483727e9f6f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb9945fe2469c69f5c8610074c97cf71fa6848dde38d3328e66f0c177ff04741 +size 14292 diff --git a/marked/Rel-18/38_series/38413/a83c022a6dac411615bcc38b7cd0d573_img.jpg b/marked/Rel-18/38_series/38413/a83c022a6dac411615bcc38b7cd0d573_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ab7aa072508bd94b82f321054c4b0931e159d12 --- /dev/null +++ b/marked/Rel-18/38_series/38413/a83c022a6dac411615bcc38b7cd0d573_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef2b6446bba47ed332d7af85e6bce058648feb4b542fa752c8c81b841b977de7 +size 13093 diff --git a/marked/Rel-18/38_series/38413/a890c88f5a03b77a0de8feaac5313821_img.jpg b/marked/Rel-18/38_series/38413/a890c88f5a03b77a0de8feaac5313821_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1fc39940e4db8c9d068ed4e3b92188c0c3e7e44 --- /dev/null +++ b/marked/Rel-18/38_series/38413/a890c88f5a03b77a0de8feaac5313821_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c01a503e6a4b2bd61a2c5e22c32091229f38dc816a5e9b1de7f459ea9e2b63f +size 12196 diff --git a/marked/Rel-18/38_series/38413/a9159a006d67a834a7b1a771c18191cc_img.jpg b/marked/Rel-18/38_series/38413/a9159a006d67a834a7b1a771c18191cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ffcfbdf9f38719058bebfc58cb0dfe89242de05f --- /dev/null +++ b/marked/Rel-18/38_series/38413/a9159a006d67a834a7b1a771c18191cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d29bcf92d4be05099e6f14b00a639090b169af33764e563a1b0bc6794a83f65 +size 15524 diff --git a/marked/Rel-18/38_series/38413/a9241101d638c568cd5a84ab7ad39f15_img.jpg b/marked/Rel-18/38_series/38413/a9241101d638c568cd5a84ab7ad39f15_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77fb3a3b5b8ac5c907259a363e224f1c43423b0a --- /dev/null +++ b/marked/Rel-18/38_series/38413/a9241101d638c568cd5a84ab7ad39f15_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da4be784f7574eba151a7aa1fee3de44998086d39370b3bc7be1bc15b454452f +size 12793 diff --git a/marked/Rel-18/38_series/38413/b14bb69bbf2f5c6daa53581440a858be_img.jpg b/marked/Rel-18/38_series/38413/b14bb69bbf2f5c6daa53581440a858be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d43ddeeb901b31fb07665493c94c63b779e99392 --- /dev/null +++ b/marked/Rel-18/38_series/38413/b14bb69bbf2f5c6daa53581440a858be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:103b1878f1fef80e0404a95e2c94e8e17043a2ac94b98163276a7a0bd07c0600 +size 15886 diff --git a/marked/Rel-18/38_series/38413/b15cf8c50195a52cca59b4645c6f59fa_img.jpg b/marked/Rel-18/38_series/38413/b15cf8c50195a52cca59b4645c6f59fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba023f2222031fef882228c1f2902fb15a1648ba --- /dev/null +++ b/marked/Rel-18/38_series/38413/b15cf8c50195a52cca59b4645c6f59fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f600fbc9add9f8af8f7c35dbf7090d0a6be084c43988fe8c47410dca74bc0ec9 +size 25954 diff --git a/marked/Rel-18/38_series/38413/b30e390cb591b39482fe7ecd4c4cd84b_img.jpg b/marked/Rel-18/38_series/38413/b30e390cb591b39482fe7ecd4c4cd84b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c63a8fec5627eb2969dfe6efbef5635cdc19e7a --- /dev/null +++ b/marked/Rel-18/38_series/38413/b30e390cb591b39482fe7ecd4c4cd84b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11cacc70629cb4f95561096c1b406592a7f4e5904d89dafa8c582a147a2def35 +size 13080 diff --git a/marked/Rel-18/38_series/38413/b432c6c13fa4f8bb90f5fb9060ef3bcd_img.jpg b/marked/Rel-18/38_series/38413/b432c6c13fa4f8bb90f5fb9060ef3bcd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6cf63e72927a62b51c3ed37dd1cbd282e4f1731f --- /dev/null +++ b/marked/Rel-18/38_series/38413/b432c6c13fa4f8bb90f5fb9060ef3bcd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:623f02d376346c3d836f3f09a36ed5ee4e5effc6a1b71938ff448f260fe5c9fc +size 16080 diff --git a/marked/Rel-18/38_series/38413/bc90605aeb4173d4b4aa6eb475037a0c_img.jpg b/marked/Rel-18/38_series/38413/bc90605aeb4173d4b4aa6eb475037a0c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..200a81a19d56e15853f8bfb0e424283fc3b4ed1a --- /dev/null +++ b/marked/Rel-18/38_series/38413/bc90605aeb4173d4b4aa6eb475037a0c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a6ab2f88524cce0bf6b8fc9b25ed43c74132c5737e06ec328230d17fb46d5d5f +size 13010 diff --git a/marked/Rel-18/38_series/38413/bd50d56ae2c12a92466ba2aea1a78040_img.jpg b/marked/Rel-18/38_series/38413/bd50d56ae2c12a92466ba2aea1a78040_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d3de454e81ccedb600d2a13d09d782bf7d025420 --- /dev/null +++ b/marked/Rel-18/38_series/38413/bd50d56ae2c12a92466ba2aea1a78040_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bebfc13ec8630f528ba5b2a0b39e0ed95ba29f91a961d20afff9615face74408 +size 17629 diff --git a/marked/Rel-18/38_series/38413/bfca6639dd4b8480f2d96d2b61c806d9_img.jpg b/marked/Rel-18/38_series/38413/bfca6639dd4b8480f2d96d2b61c806d9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..087885a12e48b696baa6537963e3da09612adfce --- /dev/null +++ b/marked/Rel-18/38_series/38413/bfca6639dd4b8480f2d96d2b61c806d9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc32225566d5e6c74712665d0fbf7bbe06bfc3b7792ca9c1d5389da5a1e4903c +size 14123 diff --git a/marked/Rel-18/38_series/38413/c020c072c67473d7823d1f9551942732_img.jpg b/marked/Rel-18/38_series/38413/c020c072c67473d7823d1f9551942732_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81c0b277ee7db951b5bb073277430e35d0a353d7 --- /dev/null +++ b/marked/Rel-18/38_series/38413/c020c072c67473d7823d1f9551942732_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:613c25a2ae55909f9d4fe818d75713369fef8387fb0ae7f51e9c40a30188fc82 +size 12785 diff --git a/marked/Rel-18/38_series/38413/c0ad2ff14abd38f0733a3186353484d2_img.jpg b/marked/Rel-18/38_series/38413/c0ad2ff14abd38f0733a3186353484d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a157f811d183c87f96ed64216eb94f9cd586e41 --- /dev/null +++ b/marked/Rel-18/38_series/38413/c0ad2ff14abd38f0733a3186353484d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6cacba5712f1f96b5f861331658e545f53191c9feea9475e53edf7783ac51545 +size 12694 diff --git a/marked/Rel-18/38_series/38413/c1bf17571f9cedf76c4072121295d10e_img.jpg b/marked/Rel-18/38_series/38413/c1bf17571f9cedf76c4072121295d10e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..093419d453b046b0c0ad337d8bb411ac34d0f9ce --- /dev/null +++ b/marked/Rel-18/38_series/38413/c1bf17571f9cedf76c4072121295d10e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee1f4516dcd90581495e2a972721b1beda956d4c52d04268deaafbadd3a54e38 +size 24280 diff --git a/marked/Rel-18/38_series/38413/c5424b117a719524c619938e97c4cb1f_img.jpg b/marked/Rel-18/38_series/38413/c5424b117a719524c619938e97c4cb1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..39a5cc5abf02c01ffe2d378ad170e676a9f3e0cf --- /dev/null +++ b/marked/Rel-18/38_series/38413/c5424b117a719524c619938e97c4cb1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4334e76a4882683d45618efefb461796b19fda04ebed7452c824ca54e2164db8 +size 12255 diff --git a/marked/Rel-18/38_series/38413/c5d9ee57705b6598bd43f9c075fec3c7_img.jpg b/marked/Rel-18/38_series/38413/c5d9ee57705b6598bd43f9c075fec3c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c28350d7df714342df0cd6360ce07639750b8e76 --- /dev/null +++ b/marked/Rel-18/38_series/38413/c5d9ee57705b6598bd43f9c075fec3c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2873fa3c380e0a9007ee36a1878d6d927554139a5cb7e2dbe2fce2e18e8d944f +size 28757 diff --git a/marked/Rel-18/38_series/38413/c78f017dab5586c098c5d7c6a8f1d432_img.jpg b/marked/Rel-18/38_series/38413/c78f017dab5586c098c5d7c6a8f1d432_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cab9c616858c4d3ec823ed54305db1efde81210d --- /dev/null +++ b/marked/Rel-18/38_series/38413/c78f017dab5586c098c5d7c6a8f1d432_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ddf47b9489f96ebf1a128118bc659e466c92fecde183cda4d338eb622f3ed82 +size 12391 diff --git a/marked/Rel-18/38_series/38413/c7e196e0c468cc7b9a84c12c951209a0_img.jpg b/marked/Rel-18/38_series/38413/c7e196e0c468cc7b9a84c12c951209a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b7d8d9c00f6bb59db57bb31eacc14a2bf174b03 --- /dev/null +++ b/marked/Rel-18/38_series/38413/c7e196e0c468cc7b9a84c12c951209a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7161866a029a5a5d5849410109a0ca4563d88fc576abe7be60681b59c57016ba +size 32571 diff --git a/marked/Rel-18/38_series/38413/ca3fe82a47b87503fc317d0dbd188ef9_img.jpg b/marked/Rel-18/38_series/38413/ca3fe82a47b87503fc317d0dbd188ef9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8121ca241f43334d45ea409641d0bb3c73b5a3ea --- /dev/null +++ b/marked/Rel-18/38_series/38413/ca3fe82a47b87503fc317d0dbd188ef9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b6ed6f6ea4b8caa6d41d0ddc7574e6127b23091dd5da341771d503cf89232439 +size 15175 diff --git a/marked/Rel-18/38_series/38413/ceb6fe29e2d57711907569c31182b3c2_img.jpg b/marked/Rel-18/38_series/38413/ceb6fe29e2d57711907569c31182b3c2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9e1884bcb6c9def8e264b975db091d84d80c0f2 --- /dev/null +++ b/marked/Rel-18/38_series/38413/ceb6fe29e2d57711907569c31182b3c2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5d5095e38cc5b278248e8d4fa363ca0e9feebc5cc7323f39bf5be04e5dde8ed +size 13034 diff --git a/marked/Rel-18/38_series/38413/d4ed35f72863013455b8f015e0f2e47e_img.jpg b/marked/Rel-18/38_series/38413/d4ed35f72863013455b8f015e0f2e47e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ec78ecc95d98eb8571bba6eb8c1f9c93fde8588 --- /dev/null +++ b/marked/Rel-18/38_series/38413/d4ed35f72863013455b8f015e0f2e47e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09547938c61bbbd4ab4c6ca8c5a99adbbf0ef3bf53ff86144eabef6b981c60e8 +size 11181 diff --git a/marked/Rel-18/38_series/38413/da87c1b628b63a046d8a0d0fc2c058ea_img.jpg b/marked/Rel-18/38_series/38413/da87c1b628b63a046d8a0d0fc2c058ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c689d75fa79e81d26ec9ae1b25abef976d442967 --- /dev/null +++ b/marked/Rel-18/38_series/38413/da87c1b628b63a046d8a0d0fc2c058ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eac979c7a9ca865fa6ac62bf6f3e8f8d17d9e16fb91b04eb45391af85a1f058f +size 13060 diff --git a/marked/Rel-18/38_series/38413/ddcf2f580e914bff1e7756ed288874e1_img.jpg b/marked/Rel-18/38_series/38413/ddcf2f580e914bff1e7756ed288874e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..862496d2ecd7f84fc213de4265d9a9b452c6f066 --- /dev/null +++ b/marked/Rel-18/38_series/38413/ddcf2f580e914bff1e7756ed288874e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3cffafb30fcbe8f1fa53125e236764c19909c59ed6d170f09e3f97578a40631e +size 13816 diff --git a/marked/Rel-18/38_series/38413/e29db6b12743ccb6dc6c48860eb8b4fb_img.jpg b/marked/Rel-18/38_series/38413/e29db6b12743ccb6dc6c48860eb8b4fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6cf6d13079c6ddb7b58b029bc0ed574566eeb59d --- /dev/null +++ b/marked/Rel-18/38_series/38413/e29db6b12743ccb6dc6c48860eb8b4fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d9df6948f07c25ef7b58eccaf2933d1730965c7bc62da86b5a9052db977e708 +size 27596 diff --git a/marked/Rel-18/38_series/38413/e4aab374983ba0fc24496fe7cd11c06c_img.jpg b/marked/Rel-18/38_series/38413/e4aab374983ba0fc24496fe7cd11c06c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1fdb2df0effebae26b11ea4c29a5c9b20cca92e5 --- /dev/null +++ b/marked/Rel-18/38_series/38413/e4aab374983ba0fc24496fe7cd11c06c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:713d5d48aff75e98782a2142e6f672cc68814fcf5ae1bcc7c1e6e62f1a9dfedc +size 12801 diff --git a/marked/Rel-18/38_series/38413/e5ded42f8e352da02ee86cb55550c45d_img.jpg b/marked/Rel-18/38_series/38413/e5ded42f8e352da02ee86cb55550c45d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc0a93d64013b227e4b542b9f2cf85bfae9e7985 --- /dev/null +++ b/marked/Rel-18/38_series/38413/e5ded42f8e352da02ee86cb55550c45d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c712d6d4294ff85b4691abd790aed041e45a5966ea722b433576457ba1897ba6 +size 22054 diff --git a/marked/Rel-18/38_series/38413/e67bca96ac67ddab7a8762b49d4c438d_img.jpg b/marked/Rel-18/38_series/38413/e67bca96ac67ddab7a8762b49d4c438d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d949daf28b0731820b93033aca9e2c71c59ecb5 --- /dev/null +++ b/marked/Rel-18/38_series/38413/e67bca96ac67ddab7a8762b49d4c438d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f7b5debebbf5c3ee5a71cad0b0d3a4b2e8dcf736bf89b7e30f573ca4b38f41cb +size 24303 diff --git a/marked/Rel-18/38_series/38413/f0e3f79f8b55cbaba4a467e762854eae_img.jpg b/marked/Rel-18/38_series/38413/f0e3f79f8b55cbaba4a467e762854eae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7fd6e40cec07c1a37854272fb3b414856387fbbf --- /dev/null +++ b/marked/Rel-18/38_series/38413/f0e3f79f8b55cbaba4a467e762854eae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bebb749fe3d9931042e9e0c067453f1db29861e0986606b86101cc9224b71731 +size 12845 diff --git a/marked/Rel-18/38_series/38413/f874851e6d8b67f9ecbc8e056ac6db8f_img.jpg b/marked/Rel-18/38_series/38413/f874851e6d8b67f9ecbc8e056ac6db8f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5661de666c0245e0dcaeb00cb41a6d8705954d61 --- /dev/null +++ b/marked/Rel-18/38_series/38413/f874851e6d8b67f9ecbc8e056ac6db8f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d39fce5a8237c54ebbeca93ecb29f8a0ba11f06ee0f05fb82cfe63f5b9d92f9 +size 12437 diff --git a/marked/Rel-18/38_series/38413/faeab87eabc08d09a83cac8f66d1c126_img.jpg b/marked/Rel-18/38_series/38413/faeab87eabc08d09a83cac8f66d1c126_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..03a10d48e166c93938ffc8d79abc656b20034596 --- /dev/null +++ b/marked/Rel-18/38_series/38413/faeab87eabc08d09a83cac8f66d1c126_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36f61e6d0ac269a240c57daebcbdb09038be5346812cf22c410939d8dcbfb114 +size 12709 diff --git a/marked/Rel-18/38_series/38413/fe2ffb87faa0257386b73d34f10bbfbd_img.jpg b/marked/Rel-18/38_series/38413/fe2ffb87faa0257386b73d34f10bbfbd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ec08f8c56405f3c170be98f5eaf938afbfabd5f --- /dev/null +++ b/marked/Rel-18/38_series/38413/fe2ffb87faa0257386b73d34f10bbfbd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a0026937d25155fc00e072cbf7599947722c1512c4cb930c6dd24d28b996afe4 +size 17016 diff --git a/marked/Rel-18/38_series/38413/ff6ed9ff347451f49c87007e1a1b92f6_img.jpg b/marked/Rel-18/38_series/38413/ff6ed9ff347451f49c87007e1a1b92f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..897fdf05ddc4d6788edc4ab25187793bf70c354f --- /dev/null +++ b/marked/Rel-18/38_series/38413/ff6ed9ff347451f49c87007e1a1b92f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d367ef671c27941dd849872284e0e39ae9dc055eaa7922832a66448e6e91d0a5 +size 23491 diff --git a/marked/Rel-18/38_series/38413/ffe2d3e622dd30bea4caf15951c60e42_img.jpg b/marked/Rel-18/38_series/38413/ffe2d3e622dd30bea4caf15951c60e42_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c0a186e0ac8465e02db4774b6e6b1ce08e1d8eaf --- /dev/null +++ b/marked/Rel-18/38_series/38413/ffe2d3e622dd30bea4caf15951c60e42_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bb0844655489725f598d1443a09f7b88e964a2f76cb7dedde4d01229440a2720 +size 25636 diff --git a/marked/Rel-18/38_series/38413/raw.md b/marked/Rel-18/38_series/38413/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..7264d297c53a4657fda13bf35b236747549c642a --- /dev/null +++ b/marked/Rel-18/38_series/38413/raw.md @@ -0,0 +1,31638 @@ + + +# 3GPP TS 38.413 V18.0.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; NG Application Protocol (NGAP) (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black capital letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' in smaller black capital letters below the logo. + +3GPP logo + +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..... | 19 | +| 1 Scope..... | 20 | +| 2 References..... | 20 | +| 3 Definitions and abbreviations..... | 22 | +| 3.1 Definitions..... | 22 | +| 3.2 Abbreviations..... | 23 | +| 4 General..... | 24 | +| 4.1 Procedure Specification Principles..... | 24 | +| 4.2 Forwards and Backwards Compatibility..... | 25 | +| 4.3 Specification Notations..... | 25 | +| 5 NGAP Services..... | 25 | +| 6 Services Expected from Signalling Transport..... | 25 | +| 7 Functions of NGAP..... | 25 | +| 8 NGAP Procedures..... | 26 | +| 8.1 List of NGAP Elementary Procedures..... | 26 | +| 8.2 PDU Session Management Procedures..... | 29 | +| 8.2.1 PDU Session Resource Setup..... | 29 | +| 8.2.1.1 General..... | 29 | +| 8.2.1.2 Successful Operation..... | 29 | + +## **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.3 | Unsuccessful Operation..... | 33 | +| 8.2.1.4 | Abnormal Conditions..... | 33 | +| 8.2.2 | PDU Session Resource Release..... | 34 | +| 8.2.2.1 | General..... | 34 | +| 8.2.2.2 | Successful Operation..... | 34 | +| 8.2.2.3 | Unsuccessful Operation..... | 35 | +| 8.2.2.4 | Abnormal Conditions..... | 35 | +| 8.2.3 | PDU Session Resource Modify..... | 35 | +| 8.2.3.1 | General..... | 35 | +| 8.2.3.2 | Successful Operation..... | 35 | +| 8.2.3.3 | Unsuccessful Operation..... | 39 | +| 8.2.3.4 | Abnormal Conditions..... | 39 | +| 8.2.4 | PDU Session Resource Notify..... | 40 | +| 8.2.4.1 | General..... | 40 | +| 8.2.4.2 | Successful Operation..... | 40 | +| 8.2.4.3 | Abnormal Conditions..... | 41 | +| 8.2.5 | PDU Session Resource Modify Indication..... | 41 | +| 8.2.5.1 | General..... | 41 | +| 8.2.5.2 | Successful Operation..... | 41 | +| 8.2.5.3 | Unsuccessful Operation..... | 43 | +| 8.2.5.4 | Abnormal Conditions..... | 43 | +| 8.3 | UE Context Management Procedures..... | 43 | +| 8.3.1 | Initial Context Setup..... | 43 | +| 8.3.1.1 | General..... | 43 | +| 8.3.1.2 | Successful Operation..... | 43 | +| 8.3.1.3 | Unsuccessful Operation..... | 47 | +| 8.3.1.4 | Abnormal Conditions..... | 48 | +| 8.3.2 | UE Context Release Request (NG-RAN node initiated)..... | 48 | +| 8.3.2.1 | General..... | 48 | +| 8.3.2.2 | Successful Operation..... | 48 | + +| | | | +|---------|------------------------------------------|----| +| 8.3.2.3 | Abnormal Conditions..... | 49 | +| 8.3.3 | UE Context Release (AMF initiated)..... | 49 | +| 8.3.3.1 | General..... | 49 | +| 8.3.3.2 | Successful Operation..... | 49 | +| 8.3.3.3 | Unsuccessful Operation..... | 50 | +| 8.3.3.4 | Abnormal Conditions..... | 50 | +| 8.3.4 | UE Context Modification..... | 50 | +| 8.3.4.1 | General..... | 50 | +| 8.3.4.2 | Successful Operation..... | 50 | +| 8.3.4.3 | Unsuccessful Operation..... | 54 | +| 8.3.4.4 | Abnormal Conditions..... | 54 | +| 8.3.5 | RRC Inactive Transition Report..... | 54 | +| 8.3.5.1 | General..... | 54 | +| 8.3.5.2 | Successful Operation..... | 54 | +| 8.3.5.3 | Abnormal Conditions..... | 55 | +| 8.3.6 | Connection Establishment Indication..... | 55 | +| 8.3.6.1 | General..... | 55 | +| 8.3.6.2 | Successful Operation..... | 55 | +| 8.3.6.3 | Abnormal Conditions..... | 56 | +| 8.3.7 | AMF CP Relocation Indication..... | 56 | +| 8.3.7.1 | General..... | 56 | +| 8.3.7.2 | Successful Operation..... | 56 | +| 8.3.7.3 | Abnormal Conditions..... | 57 | +| 8.3.8 | RAN CP Relocation Indication..... | 57 | +| 8.3.8.1 | General..... | 57 | +| 8.3.8.2 | Successful Operation..... | 57 | +| 8.3.8.3 | Abnormal Conditions..... | 58 | +| 8.3.9 | Retrieve UE Information..... | 58 | +| 8.3.9.1 | General..... | 58 | +| 8.3.9.2 | Successful Operation..... | 58 | + +| | | | +|----------|----------------------------------------|----| +| 8.3.9.3 | Abnormal Conditions..... | 58 | +| 8.3.10 | UE Information Transfer..... | 58 | +| 8.3.10.1 | General..... | 58 | +| 8.3.10.2 | Successful Operation..... | 58 | +| 8.3.10.3 | Abnormal Conditions..... | 59 | +| 8.3.11 | UE Context Suspend..... | 59 | +| 8.3.11.1 | General..... | 59 | +| 8.3.11.2 | Successful Operation..... | 60 | +| 8.3.11.3 | Unsuccessful Operation..... | 60 | +| 8.3.11.4 | Abnormal Conditions..... | 60 | +| 8.3.12 | UE Context Resume..... | 61 | +| 8.3.12.1 | General..... | 61 | +| 8.3.12.2 | Successful Operation..... | 61 | +| 8.3.12.3 | Unsuccessful Operation..... | 62 | +| 8.3.13 | MT Communication Handling..... | 62 | +| 8.3.13.1 | General..... | 62 | +| 8.3.13.2 | Successful Operation..... | 62 | +| 8.3.13.3 | Unsuccessful Operation..... | 63 | +| 8.3.14 | RAN Paging Request..... | 63 | +| 8.3.14.1 | General..... | 63 | +| 8.3.14.2 | Successful Operation..... | 63 | +| 8.3.14.3 | Abnormal Conditions..... | 63 | +| 8.4 | UE Mobility Management Procedures..... | 64 | +| 8.4.1 | Handover Preparation..... | 64 | +| 8.4.1.1 | General..... | 64 | +| 8.4.1.2 | Successful Operation..... | 64 | +| 8.4.1.3 | Unsuccessful Operation..... | 66 | +| 8.4.1.4 | Abnormal Conditions..... | 66 | +| 8.4.2 | Handover Resource Allocation..... | 67 | +| 8.4.2.1 | General..... | 67 | + +| | | | +|---------|---------------------------------------|----| +| 8.4.2.2 | Successful Operation..... | 67 | +| 8.4.2.3 | Unsuccessful Operation..... | 74 | +| 8.4.2.4 | Abnormal Conditions..... | 74 | +| 8.4.3 | Handover Notification..... | 75 | +| 8.4.3.1 | General..... | 75 | +| 8.4.3.2 | Successful Operation..... | 75 | +| 8.4.3.3 | Abnormal Conditions..... | 76 | +| 8.4.4 | Path Switch Request..... | 76 | +| 8.4.4.1 | General..... | 76 | +| 8.4.4.2 | Successful Operation..... | 76 | +| 8.4.4.3 | Unsuccessful Operation..... | 81 | +| 8.4.4.4 | Abnormal Conditions..... | 81 | +| 8.4.5 | Handover Cancellation..... | 81 | +| 8.4.5.1 | General..... | 81 | +| 8.4.5.2 | Successful Operation..... | 82 | +| 8.4.5.3 | Unsuccessful Operation..... | 82 | +| 8.4.5.4 | Abnormal Conditions..... | 82 | +| 8.4.6 | Uplink RAN Status Transfer..... | 82 | +| 8.4.6.1 | General..... | 82 | +| 8.4.6.2 | Successful Operation..... | 82 | +| 8.4.6.3 | Abnormal Conditions..... | 83 | +| 8.4.7 | Downlink RAN Status Transfer..... | 83 | +| 8.4.7.1 | General..... | 83 | +| 8.4.7.2 | Successful Operation..... | 83 | +| 8.4.7.3 | Abnormal Conditions..... | 83 | +| 8.4.8 | Handover Success..... | 83 | +| 8.4.8.1 | General..... | 83 | +| 8.4.8.2 | Successful Operation..... | 84 | +| 8.4.8.3 | Abnormal Conditions..... | 84 | +| 8.4.9 | Uplink RAN Early Status Transfer..... | 84 | + +| | | | +|----------|-------------------------------------------|----| +| 8.4.9.1 | General..... | 84 | +| 8.4.9.2 | Successful Operation..... | 84 | +| 8.4.9.3 | Abnormal Conditions..... | 84 | +| 8.4.10 | Downlink RAN Early Status Transfer..... | 85 | +| 8.4.10.1 | General..... | 85 | +| 8.4.10.2 | Successful Operation..... | 85 | +| 8.4.10.3 | Abnormal Conditions..... | 85 | +| 8.5 | Paging Procedures..... | 85 | +| 8.5.1 | Paging..... | 85 | +| 8.5.1.1 | General..... | 85 | +| 8.5.1.2 | Successful Operation..... | 86 | +| 8.5.1.3 | Abnormal Conditions..... | 87 | +| 8.5.2 | Multicast Group Paging..... | 87 | +| 8.5.2.1 | General..... | 87 | +| 8.5.2.2 | Successful Operation..... | 87 | +| 8.5.2.3 | Abnormal Conditions..... | 88 | +| 8.6 | Transport of NAS Messages Procedures..... | 88 | +| 8.6.1 | Initial UE Message..... | 88 | +| 8.6.1.1 | General..... | 88 | +| 8.6.1.2 | Successful Operation..... | 88 | +| 8.6.1.3 | Abnormal Conditions..... | 89 | +| 8.6.2 | Downlink NAS Transport..... | 89 | +| 8.6.2.1 | General..... | 89 | +| 8.6.2.2 | Successful Operation..... | 89 | +| 8.6.2.3 | Abnormal Conditions..... | 91 | +| 8.6.3 | Uplink NAS Transport..... | 91 | +| 8.6.3.1 | General..... | 91 | +| 8.6.3.2 | Successful Operation..... | 91 | +| 8.6.3.3 | Abnormal Conditions..... | 91 | +| 8.6.4 | NAS Non Delivery Indication..... | 92 | + +| | | | +|-----------|--------------------------------------------|-----| +| 8.6.4.1 | General..... | 92 | +| 8.6.4.2 | Successful Operation..... | 92 | +| 8.6.4.3 | Abnormal Conditions..... | 92 | +| 8.6.5 | Reroute NAS Request..... | 92 | +| 8.6.5.1 | General..... | 92 | +| 8.6.5.2 | Successful Operation..... | 92 | +| 8.6.5.3 | Abnormal Conditions..... | 93 | +| 8.7 | Interface Management Procedures..... | 93 | +| 8.7.1 | NG Setup..... | 93 | +| 8.7.1.1 | General..... | 93 | +| 8.7.1.2 | Successful Operation..... | 93 | +| 8.7.1.3 | Unsuccessful Operation..... | 94 | +| 8.7.1.4 | Abnormal Conditions..... | 95 | +| 8.7.2 | RAN Configuration Update..... | 95 | +| 8.7.2.1 | General..... | 95 | +| 8.7.2.2 | Successful Operation..... | 95 | +| 8.7.2.3 | Unsuccessful Operation..... | 96 | +| 8.7.2.4 | Abnormal Conditions..... | 96 | +| 8.7.3 | AMF Configuration Update..... | 96 | +| 8.7.3.1 | General..... | 96 | +| 8.7.3.2 | Successful Operation..... | 97 | +| 8.7.3.3 | Unsuccessful Operation..... | 98 | +| 8.7.3.4 | Abnormal Conditions..... | 98 | +| 8.7.4 | NG Reset..... | 99 | +| 8.7.4.1 | General..... | 99 | +| 8.7.4.2 | Successful Operation..... | 99 | +| 8.7.4.2.1 | NG Reset initiated by the AMF..... | 99 | +| 8.7.4.2.2 | NG Reset initiated by the NG-RAN node..... | 100 | +| 8.7.4.3 | Unsuccessful Operation..... | 100 | +| 8.7.4.4 | Abnormal Conditions..... | 100 | + +| | | | +|-----------|----------------------------------------------|-----| +| 8.7.4.4.1 | Abnormal Condition at the 5GC..... | 100 | +| 8.7.4.4.2 | Abnormal Condition at the NG-RAN..... | 101 | +| 8.7.4.4.3 | Crossing of NG RESET Messages..... | 101 | +| 8.7.5 | Error Indication..... | 101 | +| 8.7.5.1 | General..... | 101 | +| 8.7.5.2 | Successful Operation..... | 101 | +| 8.7.5.3 | Abnormal Conditions..... | 102 | +| 8.7.6 | AMF Status Indication..... | 102 | +| 8.7.6.1 | General..... | 102 | +| 8.7.6.2 | Successful Operation..... | 102 | +| 8.7.6.3 | Abnormal Conditions..... | 103 | +| 8.7.7 | Overload Start..... | 103 | +| 8.7.7.1 | General..... | 103 | +| 8.7.7.2 | Successful Operation..... | 103 | +| 8.7.7.3 | Abnormal Conditions..... | 104 | +| 8.7.8 | Overload Stop..... | 104 | +| 8.7.8.1 | General..... | 104 | +| 8.7.8.2 | Successful Operation..... | 104 | +| 8.7.8.3 | Abnormal Conditions..... | 104 | +| 8.8 | Configuration Transfer Procedures..... | 104 | +| 8.8.1 | Uplink RAN Configuration Transfer..... | 104 | +| 8.8.1.1 | General..... | 104 | +| 8.8.1.2 | Successful Operation..... | 105 | +| 8.8.1.3 | Abnormal Conditions..... | 105 | +| 8.8.2 | Downlink RAN Configuration Transfer..... | 105 | +| 8.8.2.1 | General..... | 105 | +| 8.8.2.2 | Successful Operation..... | 105 | +| 8.8.2.3 | Abnormal Conditions..... | 106 | +| 8.9 | Warning Message Transmission Procedures..... | 106 | +| 8.9.1 | Write-Replace Warning..... | 106 | + +| | | | +|----------|-------------------------------------------------|-----| +| 8.9.1.1 | General..... | 106 | +| 8.9.1.2 | Successful Operation..... | 107 | +| 8.9.1.3 | Unsuccessful Operation..... | 108 | +| 8.9.1.4 | Abnormal Conditions..... | 108 | +| 8.9.2 | PWS Cancel..... | 108 | +| 8.9.2.1 | General..... | 108 | +| 8.9.2.2 | Successful Operation..... | 108 | +| 8.9.2.3 | Unsuccessful Operation..... | 109 | +| 8.9.2.4 | Abnormal Conditions..... | 109 | +| 8.9.3 | PWS Restart Indication..... | 109 | +| 8.9.3.1 | General..... | 109 | +| 8.9.3.2 | Successful Operation..... | 109 | +| 8.9.3.3 | Abnormal Conditions..... | 109 | +| 8.9.4 | PWS Failure Indication..... | 109 | +| 8.9.4.1 | General..... | 109 | +| 8.9.4.2 | Successful Operation..... | 110 | +| 8.9.4.3 | Abnormal Conditions..... | 110 | +| 8.10 | NRPPa Transport Procedures..... | 110 | +| 8.10.1 | General..... | 110 | +| 8.10.2 | Successful Operations..... | 110 | +| 8.10.2.1 | DOWNLINK UE ASSOCIATED NRPPA TRANSPORT..... | 110 | +| 8.10.2.2 | UPLINK UE ASSOCIATED NRPPA TRANSPORT..... | 111 | +| 8.10.2.3 | DOWNLINK NON UE ASSOCIATED NRPPA TRANSPORT..... | 111 | +| 8.10.2.4 | UPLINK NON UE ASSOCIATED NRPPA TRANSPORT..... | 111 | +| 8.10.3 | Unsuccessful Operations..... | 112 | +| 8.10.4 | Abnormal Conditions..... | 112 | +| 8.11 | Trace Procedures..... | 112 | +| 8.11.1 | Trace Start..... | 112 | +| 8.11.1.1 | General..... | 112 | +| 8.11.1.2 | Successful Operation..... | 112 | + +| | | | +|----------|--------------------------------------------|-----| +| 8.11.1.3 | Abnormal Conditions..... | 113 | +| 8.11.2 | Trace Failure Indication..... | 113 | +| 8.11.2.1 | General..... | 113 | +| 8.11.2.2 | Successful Operation..... | 113 | +| 8.11.2.3 | Abnormal Conditions..... | 113 | +| 8.11.3 | Deactivate Trace..... | 114 | +| 8.11.3.1 | General..... | 114 | +| 8.11.3.2 | Successful Operation..... | 114 | +| 8.11.3.3 | Abnormal Conditions..... | 114 | +| 8.11.4 | Cell Traffic Trace..... | 114 | +| 8.11.4.1 | General..... | 114 | +| 8.11.4.2 | Successful Operation..... | 114 | +| 8.11.4.3 | Abnormal Conditions..... | 115 | +| 8.12 | Location Reporting Procedures..... | 115 | +| 8.12.1 | Location Reporting Control..... | 115 | +| 8.12.1.1 | General..... | 115 | +| 8.12.1.2 | Successful Operation..... | 115 | +| 8.12.1.3 | Abnormal Conditions..... | 116 | +| 8.12.2 | Location Reporting Failure Indication..... | 116 | +| 8.12.2.1 | General..... | 116 | +| 8.12.2.2 | Successful Operation..... | 116 | +| 8.12.2.3 | Abnormal Conditions..... | 116 | +| 8.12.3 | Location Report..... | 117 | +| 8.12.3.1 | General..... | 117 | +| 8.12.3.2 | Successful Operation..... | 117 | +| 8.12.3.3 | Abnormal Conditions..... | 117 | +| 8.13 | UE TNLA Binding Procedures..... | 117 | +| 8.13.1 | UE TNLA Binding Release..... | 117 | +| 8.13.1.1 | General..... | 117 | +| 8.13.1.2 | Successful Operation..... | 117 | + +| | | | +|----------|------------------------------------------------|-----| +| 8.13.1.3 | Abnormal Conditions..... | 118 | +| 8.14 | UE Radio Capability Management Procedures..... | 118 | +| 8.14.1 | UE Radio Capability Info Indication..... | 118 | +| 8.14.1.1 | General..... | 118 | +| 8.14.1.2 | Successful Operation..... | 118 | +| 8.14.1.3 | Abnormal Conditions..... | 118 | +| 8.14.2 | UE Radio Capability Check..... | 118 | +| 8.14.2.1 | General..... | 118 | +| 8.14.2.2 | Successful Operation..... | 119 | +| 8.14.2.3 | Unsuccessful Operation..... | 119 | +| 8.14.2.4 | Abnormal Conditions..... | 119 | +| 8.14.3 | UE Radio Capability ID Mapping..... | 119 | +| 8.14.3.1 | General..... | 119 | +| 8.14.3.2 | Successful Operation..... | 120 | +| 8.14.3.3 | Unsuccessful Operation..... | 120 | +| 8.14.3.4 | Abnormal Conditions..... | 120 | +| 8.15 | Data Usage Reporting Procedures..... | 120 | +| 8.15.1 | Secondary RAT Data Usage Report..... | 120 | +| 8.15.1.1 | General..... | 120 | +| 8.15.1.2 | Successful Operation..... | 120 | +| 8.15.1.3 | Abnormal Conditions..... | 121 | +| 8.16 | RIM Information Transfer Procedures..... | 121 | +| 8.16.1 | Uplink RIM Information Transfer..... | 121 | +| 8.16.1.1 | General..... | 121 | +| 8.16.1.2 | Successful Operation..... | 121 | +| 8.16.1.3 | Abnormal Conditions..... | 121 | +| 8.16.2 | Downlink RIM Information Transfer..... | 121 | +| 8.16.2.1 | General..... | 121 | +| 8.16.2.2 | Successful Operation..... | 122 | +| 8.16.2.3 | Abnormal Conditions..... | 122 | + +| | | | +|----------|----------------------------------------------|-----| +| 8.17 | Broadcast Session Management Procedures..... | 122 | +| 8.17.1 | Broadcast Session Setup..... | 122 | +| 8.17.1.1 | General..... | 122 | +| 8.17.1.2 | Successful Operation..... | 122 | +| 8.17.1.3 | Unsuccessful Operation..... | 123 | +| 8.17.1.4 | Abnormal Conditions..... | 123 | +| 8.17.2 | Broadcast Session Modification..... | 123 | +| 8.17.2.1 | General..... | 123 | +| 8.17.2.2 | Successful Operation..... | 123 | +| 8.17.2.3 | Unsuccessful Operation..... | 124 | +| 8.17.2.4 | Abnormal Conditions..... | 124 | +| 8.17.3 | Broadcast Session Release..... | 124 | +| 8.17.3.1 | General..... | 124 | +| 8.17.3.2 | Successful Operation..... | 124 | +| 8.17.3.3 | Unsuccessful Operation..... | 125 | +| 8.17.3.4 | Abnormal Conditions..... | 125 | +| 8.17.4 | Broadcast Session Release Required..... | 125 | +| 8.17.4.1 | General..... | 125 | +| 8.17.4.2 | Successful Operation..... | 125 | +| 8.17.4.3 | Abnormal Conditions..... | 125 | +| 8.17.5 | Broadcast Session Transport..... | 125 | +| 8.17.5.1 | General..... | 125 | +| 8.17.5.2 | Successful Operation..... | 126 | +| 8.17.5.3 | Unsuccessful Operation..... | 126 | +| 8.17.5.4 | Abnormal Conditions..... | 126 | +| 8.18 | Multicast Session Management Procedures..... | 126 | +| 8.18.1 | Distribution Setup..... | 126 | +| 8.18.1.1 | General..... | 126 | +| 8.18.1.2 | Successful Operation..... | 127 | +| 8.18.1.3 | Unsuccessful Operation..... | 127 | + +| | | | +|----------|---------------------------------------------------------|-----| +| 8.18.1.4 | Abnormal Conditions..... | 127 | +| 8.18.2 | Distribution Release..... | 127 | +| 8.18.2.1 | General..... | 127 | +| 8.18.2.2 | Successful Operation..... | 128 | +| 8.18.2.3 | Unsuccessful Operation..... | 128 | +| 8.18.2.4 | Abnormal Conditions..... | 128 | +| 8.18.3 | Multicast Session Activation..... | 128 | +| 8.18.3.1 | General..... | 128 | +| 8.18.3.2 | Successful Operation..... | 129 | +| 8.18.3.3 | Unsuccessful Operation..... | 129 | +| 8.18.3.4 | Abnormal Conditions..... | 129 | +| 8.18.4 | Multicast Session Deactivation..... | 130 | +| 8.18.4.1 | General..... | 130 | +| 8.18.4.2 | Successful Operation..... | 130 | +| 8.18.4.3 | Unsuccessful Operation..... | 130 | +| 8.18.4.4 | Abnormal Conditions..... | 130 | +| 8.18.5 | Multicast Session Update..... | 130 | +| 8.18.5.1 | General..... | 130 | +| 8.18.5.2 | Successful Operation..... | 131 | +| 8.18.5.3 | Unsuccessful Operation..... | 132 | +| 8.18.5.4 | Abnormal Conditions..... | 132 | +| 8.19 | Timing Synchronisation Status Reporting Procedures..... | 132 | +| 8.19.1 | Timing Synchronisation Status..... | 132 | +| 8.19.1.1 | General..... | 132 | +| 8.19.1.2 | Successful Operation..... | 132 | +| 8.19.1.3 | Unsuccessful Operation..... | 133 | +| 8.19.1.4 | Abnormal Conditions..... | 133 | +| 8.19.2 | Timing Synchronisation Status Report..... | 133 | +| 8.19.2.1 | General..... | 133 | +| 8.19.2.2 | Successful Operation..... | 133 | + +| | | | +|----------|-----------------------------------------------|-----| +| 8.19.2.3 | Abnormal Conditions..... | 133 | +| 9 | Elements for NGAP Communication..... | 134 | +| 9.0 | General..... | 134 | +| 9.1 | Tabular Format Contents..... | 134 | +| 9.1.1 | Presence..... | 134 | +| 9.1.2 | Criticality..... | 134 | +| 9.1.3 | Range..... | 134 | +| 9.1.4 | Assigned Criticality..... | 135 | +| 9.2 | Message Functional Defnition and Content..... | 135 | +| 9.2.1 | PDU Session Management Messages..... | 135 | +| 9.2.1.1 | PDU SESSION RESOURCE SETUP REQUEST..... | 135 | +| 9.2.1.2 | PDU SESSION RESOURCE SETUP RESPONSE..... | 135 | +| 9.2.1.3 | PDU SESSION RESOURCE RELEASE COMMAND..... | 136 | +| 9.2.1.4 | PDU SESSION RESOURCE RELEASE RESPONSE..... | 137 | +| 9.2.1.5 | PDU SESSION RESOURCE MODIFY REQUEST..... | 137 | +| 9.2.1.6 | PDU SESSION RESOURCE MODIFY RESPONSE..... | 139 | +| 9.2.1.7 | PDU SESSION RESOURCE NOTIFY..... | 139 | +| 9.2.1.8 | PDU SESSION RESOURCE MODIFY INDICATION..... | 140 | +| 9.2.1.9 | PDU SESSION RESOURCE MODIFY CONFIRM..... | 141 | +| 9.2.2 | UE Context Management Messages..... | 141 | +| 9.2.2.1 | INITIAL CONTEXT SETUP REQUEST..... | 141 | +| 9.2.2.2 | INITIAL CONTEXT SETUP RESPONSE..... | 144 | +| 9.2.2.3 | INITIAL CONTEXT SETUP FAILURE..... | 145 | +| 9.2.2.4 | UE CONTEXT RELEASE REQUEST..... | 145 | +| 9.2.2.5 | UE CONTEXT RELEASE COMMAND..... | 146 | +| 9.2.2.6 | UE CONTEXT RELEASE COMPLETE..... | 146 | +| 9.2.2.7 | UE CONTEXT MODIFICATION REQUEST..... | 146 | +| 9.2.2.8 | UE CONTEXT MODIFICATION RESPONSE..... | 148 | +| 9.2.2.9 | UE CONTEXT MODIFICATION FAILURE..... | 148 | +| 9.2.2.10 | RRC INACTIVE TRANSITION REPORT..... | 149 | + +| | | | +|----------|------------------------------------------|-----| +| 9.2.2.11 | CONNECTION ESTABLISHMENT INDICATION..... | 149 | +| 9.2.2.12 | AMF CP RELOCATION INDICATION..... | 150 | +| 9.2.2.13 | RAN CP RELOCATION INDICATION..... | 150 | +| 9.2.2.14 | RETRIEVE UE INFORMATION..... | 150 | +| 9.2.2.15 | UE INFORMATION TRANSFER..... | 150 | +| 9.2.2.16 | UE CONTEXT SUSPEND REQUEST..... | 151 | +| 9.2.2.17 | UE CONTEXT SUSPEND RESPONSE..... | 151 | +| 9.2.2.18 | UE CONTEXT SUSPEND FAILURE..... | 152 | +| 9.2.2.19 | UE CONTEXT RESUME REQUEST..... | 152 | +| 9.2.2.20 | UE CONTEXT RESUME RESPONSE..... | 153 | +| 9.2.2.21 | UE CONTEXT RESUME FAILURE..... | 154 | +| 9.2.2.22 | MT COMMUNICATION HANDLING REQUEST..... | 154 | +| 9.2.2.23 | MT COMMUNICATION HANDLING RESPONSE..... | 155 | +| 9.2.2.24 | MT COMMUNICATION HANDLING FAILURE..... | 155 | +| 9.2.2.25 | RAN PAGING REQUEST..... | 155 | +| 9.2.3 | UE Mobility Management Messages..... | 156 | +| 9.2.3.1 | HANDOVER REQUIRED..... | 156 | +| 9.2.3.2 | HANDOVER COMMAND..... | 156 | +| 9.2.3.3 | HANDOVER PREPARATION FAILURE..... | 157 | +| 9.2.3.4 | HANDOVER REQUEST..... | 158 | +| 9.2.3.5 | HANDOVER REQUEST ACKNOWLEDGE..... | 161 | +| 9.2.3.6 | HANDOVER FAILURE..... | 161 | +| 9.2.3.7 | HANDOVER NOTIFY..... | 162 | +| 9.2.3.8 | PATH SWITCH REQUEST..... | 163 | +| 9.2.3.9 | PATH SWITCH REQUEST ACKNOWLEDGE..... | 164 | +| 9.2.3.10 | PATH SWITCH REQUEST FAILURE..... | 167 | +| 9.2.3.11 | HANDOVER CANCEL..... | 167 | +| 9.2.3.12 | HANDOVER CANCEL ACKNOWLEDGE..... | 167 | +| 9.2.3.13 | UPLINK RAN STATUS TRANSFER..... | 168 | +| 9.2.3.14 | DOWNLINK RAN STATUS TRANSFER..... | 168 | + +| | | | +|----------|-------------------------------------------|-----| +| 9.2.3.15 | HANDOVER SUCCESS..... | 168 | +| 9.2.3.16 | UPLINK RAN EARLY STATUS TRANSFER..... | 168 | +| 9.2.3.17 | DOWNLINK RAN EARLY STATUS TRANSFER..... | 169 | +| 9.2.4 | Paging Messages..... | 169 | +| 9.2.4.1 | PAGING..... | 169 | +| 9.2.4.2 | MULTICAST GROUP PAGING..... | 170 | +| 9.2.5 | NAS Transport Messages..... | 171 | +| 9.2.5.1 | INITIAL UE MESSAGE..... | 171 | +| 9.2.5.2 | DOWNLINK NAS TRANSPORT..... | 172 | +| 9.2.5.3 | UPLINK NAS TRANSPORT..... | 172 | +| 9.2.5.4 | NAS NON DELIVERY INDICATION..... | 173 | +| 9.2.5.5 | REROUTE NAS REQUEST..... | 173 | +| 9.2.6 | Interface Management Messages..... | 174 | +| 9.2.6.1 | NG SETUP REQUEST..... | 174 | +| 9.2.6.2 | NG SETUP RESPONSE..... | 175 | +| 9.2.6.3 | NG SETUP FAILURE..... | 176 | +| 9.2.6.4 | RAN CONFIGURATION UPDATE..... | 176 | +| 9.2.6.5 | RAN CONFIGURATION UPDATE ACKNOWLEDGE..... | 178 | +| 9.2.6.6 | RAN CONFIGURATION UPDATE FAILURE..... | 178 | +| 9.2.6.7 | AMF CONFIGURATION UPDATE..... | 178 | +| 9.2.6.8 | AMF CONFIGURATION UPDATE ACKNOWLEDGE..... | 180 | +| 9.2.6.9 | AMF CONFIGURATION UPDATE FAILURE..... | 180 | +| 9.2.6.10 | AMF STATUS INDICATION..... | 181 | +| 9.2.6.11 | NG RESET..... | 181 | +| 9.2.6.12 | NG RESET ACKNOWLEDGE..... | 181 | +| 9.2.6.13 | ERROR INDICATION..... | 182 | +| 9.2.6.14 | OVERLOAD START..... | 182 | +| 9.2.6.15 | OVERLOAD STOP..... | 182 | +| 9.2.7 | Configuration Transfer Messages..... | 183 | +| 9.2.7.1 | UPLINK RAN CONFIGURATION TRANSFER..... | 183 | + +| | | | +|----------|-------------------------------------------------|-----| +| 9.2.7.2 | DOWNLINK RAN CONFIGURATION TRANSFER..... | 183 | +| 9.2.8 | Warning Message Transmission Messages..... | 183 | +| 9.2.8.1 | WRITE-REPLACE WARNING REQUEST..... | 183 | +| 9.2.8.2 | WRITE-REPLACE WARNING RESPONSE..... | 184 | +| 9.2.8.3 | PWS CANCEL REQUEST..... | 184 | +| 9.2.8.4 | PWS CANCEL RESPONSE..... | 184 | +| 9.2.8.5 | PWS RESTART INDICATION..... | 185 | +| 9.2.8.6 | PWS FAILURE INDICATION..... | 185 | +| 9.2.9 | NRPPa Transport Messages..... | 186 | +| 9.2.9.1 | DOWNLINK UE ASSOCIATED NRPPA TRANSPORT..... | 186 | +| 9.2.9.2 | UPLINK UE ASSOCIATED NRPPA TRANSPORT..... | 186 | +| 9.2.9.3 | DOWNLINK NON UE ASSOCIATED NRPPA TRANSPORT..... | 187 | +| 9.2.9.4 | UPLINK NON UE ASSOCIATED NRPPA TRANSPORT..... | 187 | +| 9.2.10 | Trace Messages..... | 187 | +| 9.2.10.1 | TRACE START..... | 187 | +| 9.2.10.2 | TRACE FAILURE INDICATION..... | 187 | +| 9.2.10.3 | DEACTIVATE TRACE..... | 187 | +| 9.2.10.4 | CELL TRAFFIC TRACE..... | 188 | +| 9.2.11 | Location Reporting Messages..... | 188 | +| 9.2.11.1 | LOCATION REPORTING CONTROL..... | 188 | +| 9.2.11.2 | LOCATION REPORTING FAILURE INDICATION..... | 189 | +| 9.2.11.3 | LOCATION REPORT..... | 189 | +| 9.2.12 | UE TNLA Binding Messages..... | 189 | +| 9.2.12.1 | UE TNLA BINDING RELEASE REQUEST..... | 189 | +| 9.2.13 | UE Radio Capability Management Messages..... | 190 | +| 9.2.13.1 | UE RADIO CAPABILITY INFO INDICATION..... | 190 | +| 9.2.13.2 | UE RADIO CAPABILITY CHECK REQUEST..... | 190 | +| 9.2.13.3 | UE RADIO CAPABILITY CHECK RESPONSE..... | 190 | +| 9.2.13.4 | UE RADIO CAPABILITY ID MAPPING REQUEST..... | 190 | +| 9.2.13.5 | UE RADIO CAPABILITY ID MAPPING RESPONSE..... | 191 | + +| | | | +|-----------|----------------------------------------------|-----| +| 9.2.14 | Data Usage Reporting Messages..... | 191 | +| 9.2.14.1 | SECONDARY RAT DATA USAGE REPORT..... | 191 | +| 9.2.15 | RIM Information Transfer Messages..... | 191 | +| 9.2.15.1 | UPLINK RIM INFORMATION TRANSFER..... | 191 | +| 9.2.15.2 | DOWNLINK RIM INFORMATION TRANSFER..... | 192 | +| 9.2.16 | Broadcast Session Management Messages..... | 192 | +| 9.2.16.1 | BROADCAST SESSION SETUP REQUEST..... | 192 | +| 9.2.16.2 | BROADCAST SESSION SETUP RESPONSE..... | 192 | +| 9.2.16.3 | BROADCAST SESSION SETUP FAILURE..... | 193 | +| 9.2.16.4 | BROADCAST SESSION MODIFICATION REQUEST..... | 193 | +| 9.2.16.5 | BROADCAST SESSION MODIFICATION RESPONSE..... | 193 | +| 9.2.16.6 | BROADCAST SESSION MODIFICATION FAILURE..... | 194 | +| 9.2.16.7 | BROADCAST SESSION RELEASE REQUEST..... | 194 | +| 9.2.16.8 | BROADCAST SESSION RELEASE RESPONSE..... | 194 | +| 9.2.16.9 | BROADCAST SESSION RELEASE REQUIRED..... | 194 | +| 9.2.16.10 | BROADCAST SESSION TRANSPORT REQUEST..... | 195 | +| 9.2.16.11 | BROADCAST SESSION TRANSPORT RESPONSE..... | 195 | +| 9.2.16.12 | BROADCAST SESSION TRANSPORT FAILURE..... | 195 | +| 9.2.17 | Multicast Session Management Messages..... | 196 | +| 9.2.17.1 | DISTRIBUTION SETUP REQUEST..... | 196 | +| 9.2.17.2 | DISTRIBUTION SETUP RESPONSE..... | 196 | +| 9.2.17.3 | DISTRIBUTION SETUP FAILURE..... | 196 | +| 9.2.17.4 | DISTRIBUTION RELEASE REQUEST..... | 197 | +| 9.2.17.5 | DISTRIBUTION RELEASE RESPONSE..... | 197 | +| 9.2.17.6 | MULTICAST SESSION ACTIVATION REQUEST..... | 197 | +| 9.2.17.7 | MULTICAST SESSION ACTIVATION RESPONSE..... | 197 | +| 9.2.17.8 | MULTICAST SESSION ACTIVATION FAILURE..... | 198 | +| 9.2.17.9 | MULTICAST SESSION DEACTIVATION REQUEST..... | 198 | +| 9.2.17.10 | MULTICAST SESSION DEACTIVATION RESPONSE..... | 198 | +| 9.2.17.11 | MULTICAST SESSION UPDATE REQUEST..... | 198 | + +| | | | +|-----------|-----------------------------------------------------------|-----| +| 9.2.17.12 | MULTICAST SESSION UPDATE RESPONSE..... | 199 | +| 9.2.17.13 | MULTICAST SESSION UPDATE FAILURE..... | 199 | +| 9.2.18 | Timing Synchronisation Status Reporting Messages..... | 199 | +| 9.2.18.1 | TIMING SYNCHRONISATION STATUS REQUEST..... | 199 | +| 9.2.18.2 | TIMING SYNCHRONISATION STATUS RESPONSE..... | 199 | +| 9.2.18.3 | TIMING SYNCHRONISATION STATUS FAILURE..... | 200 | +| 9.2.18.4 | TIMING SYNCHRONISATION STATUS REPORT..... | 200 | +| 9.3 | Information Element Definitions..... | 200 | +| 9.3.1 | Radio Network Layer Related IEs..... | 200 | +| 9.3.1.1 | Message Type..... | 200 | +| 9.3.1.2 | Cause..... | 200 | +| 9.3.1.3 | Criticality Diagnostics..... | 206 | +| 9.3.1.4 | Bit Rate..... | 206 | +| 9.3.1.5 | Global RAN Node ID..... | 207 | +| 9.3.1.6 | Global gNB ID..... | 207 | +| 9.3.1.7 | NR CGI..... | 207 | +| 9.3.1.8 | Global ng-eNB ID..... | 208 | +| 9.3.1.9 | E-UTRA CGI..... | 208 | +| 9.3.1.10 | GBR QoS Flow Information..... | 208 | +| 9.3.1.11 | Void..... | 209 | +| 9.3.1.12 | QoS Flow Level QoS Parameters..... | 209 | +| 9.3.1.13 | QoS Flow List with Cause..... | 210 | +| 9.3.1.14 | Trace Activation..... | 211 | +| 9.3.1.15 | Core Network Assistance Information for RRC INACTIVE..... | 212 | +| 9.3.1.16 | User Location Information..... | 213 | +| 9.3.1.17 | Slice Support List..... | 215 | +| 9.3.1.18 | Dynamic 5QI Descriptor..... | 215 | +| 9.3.1.19 | Allocation and Retention Priority..... | 217 | +| 9.3.1.20 | Source to Target Transparent Container..... | 217 | +| 9.3.1.21 | Target to Source Transparent Container..... | 218 | + +| | | | +|----------|---------------------------------------------------------------------|-----| +| 9.3.1.22 | Handover Type..... | 218 | +| 9.3.1.23 | MICO Mode Indication..... | 219 | +| 9.3.1.24 | S-NSSAI..... | 219 | +| 9.3.1.25 | Target ID..... | 219 | +| 9.3.1.26 | Emergency Fallback Indicator..... | 220 | +| 9.3.1.27 | Security Indication..... | 220 | +| 9.3.1.28 | Non Dynamic 5QI Descriptor..... | 221 | +| 9.3.1.29 | Source NG-RAN Node to Target NG-RAN Node Transparent Container..... | 222 | +| 9.3.1.30 | Target NG-RAN Node to Source NG-RAN Node Transparent Container..... | 225 | +| 9.3.1.31 | Allowed NSSAI..... | 227 | +| 9.3.1.32 | Relative AMF Capacity..... | 227 | +| 9.3.1.33 | DL Forwarding..... | 227 | +| 9.3.1.34 | DRBs to QoS Flows Mapping List..... | 227 | +| 9.3.1.35 | Message Identifier..... | 228 | +| 9.3.1.36 | Serial Number..... | 228 | +| 9.3.1.37 | Warning Area List..... | 228 | +| 9.3.1.38 | Number of Broadcasts Requested..... | 228 | +| 9.3.1.39 | Warning Type..... | 229 | +| 9.3.1.40 | Void..... | 229 | +| 9.3.1.41 | Data Coding Scheme..... | 229 | +| 9.3.1.42 | Warning Message Contents..... | 229 | +| 9.3.1.43 | Broadcast Completed Area List..... | 229 | +| 9.3.1.44 | Broadcast Cancelled Area List..... | 230 | +| 9.3.1.45 | Number of Broadcasts..... | 232 | +| 9.3.1.46 | Concurrent Warning Message Indicator..... | 232 | +| 9.3.1.47 | Cancel-All Warning Messages Indicator..... | 232 | +| 9.3.1.48 | Emergency Area ID..... | 232 | +| 9.3.1.49 | Repetition Period..... | 232 | +| 9.3.1.50 | PDU Session ID..... | 233 | +| 9.3.1.51 | QoS Flow Identifier..... | 233 | + +| | | | +|-----------|------------------------------------------------|-----| +| 9.3.1.52 | PDU Session Type..... | 233 | +| 9.3.1.53 | DRB ID..... | 233 | +| 9.3.1.54 | Masked IMEISV..... | 233 | +| 9.3.1.55 | New Security Context Indicator..... | 234 | +| 9.3.1.56 | Time to Wait..... | 234 | +| 9.3.1.57 | Global N3IWF ID..... | 234 | +| 9.3.1.58 | UE Aggregate Maximum Bit Rate..... | 234 | +| 9.3.1.59 | Security Result..... | 235 | +| 9.3.1.60 | User Plane Security Information..... | 235 | +| 9.3.1.61 | Index to RAT/Frequency Selection Priority..... | 235 | +| 9.3.1.62 | Data Forwarding Accepted..... | 235 | +| 9.3.1.63 | Data Forwarding Not Possible..... | 235 | +| 9.3.1.64 | Direct Forwarding Path Availability..... | 236 | +| 9.3.1.65 | Location Reporting Request Type..... | 236 | +| 9.3.1.66 | Area of Interest..... | 238 | +| 9.3.1.67 | UE Presence in Area of Interest List..... | 238 | +| 9.3.1.68 | UE Radio Capability for Paging..... | 238 | +| 9.3.1.69 | Assistance Data for Paging..... | 239 | +| 9.3.1.70 | Assistance Data for Recommended Cells..... | 239 | +| 9.3.1.71 | Recommended Cells for Paging..... | 239 | +| 9.3.1.72 | Paging Attempt Information..... | 239 | +| 9.3.1.73 | NG-RAN CGI..... | 240 | +| 9.3.1.74 | UE Radio Capability..... | 240 | +| 9.3.1.74a | UE Radio Capability – E-UTRA Format..... | 240 | +| 9.3.1.75 | Time Stamp..... | 240 | +| 9.3.1.76 | Location Reporting Reference ID..... | 241 | +| 9.3.1.77 | Data Forwarding Response DRB List..... | 241 | +| 9.3.1.78 | Paging Priority..... | 241 | +| 9.3.1.79 | Packet Loss Rate..... | 241 | +| 9.3.1.80 | Packet Delay Budget..... | 241 | + +| | | | +|-----------|----------------------------------------------------------------|-----| +| 9.3.1.81 | Packet Error Rate..... | 242 | +| 9.3.1.82 | Averaging Window..... | 242 | +| 9.3.1.83 | Maximum Data Burst Volume..... | 242 | +| 9.3.1.84 | Priority Level..... | 242 | +| 9.3.1.85 | Mobility Restriction List..... | 242 | +| 9.3.1.86 | UE Security Capabilities..... | 244 | +| 9.3.1.87 | Security Key..... | 246 | +| 9.3.1.88 | Security Context..... | 246 | +| 9.3.1.89 | IMS Voice Support Indicator..... | 246 | +| 9.3.1.90 | Paging DRX..... | 246 | +| 9.3.1.91 | RRC Inactive Transition Report Request..... | 247 | +| 9.3.1.92 | RRC State..... | 247 | +| 9.3.1.93 | Expected UE Behaviour..... | 247 | +| 9.3.1.94 | Expected UE Activity Behaviour..... | 248 | +| 9.3.1.95 | UE History Information..... | 249 | +| 9.3.1.96 | Last Visited Cell Information..... | 249 | +| 9.3.1.97 | Last Visited NG-RAN Cell Information..... | 250 | +| 9.3.1.98 | Cell Type..... | 250 | +| 9.3.1.99 | Associated QoS Flow List..... | 251 | +| 9.3.1.100 | Information on Recommended Cells and RAN Nodes for Paging..... | 251 | +| 9.3.1.101 | Recommended RAN Nodes for Paging..... | 251 | +| 9.3.1.102 | PDU Session Aggregate Maximum Bit Rate..... | 252 | +| 9.3.1.103 | Maximum Integrity Protected Data Rate..... | 252 | +| 9.3.1.104 | Overload Response..... | 252 | +| 9.3.1.105 | Overload Action..... | 252 | +| 9.3.1.106 | Traffic Load Reduction Indication..... | 253 | +| 9.3.1.107 | Slice Overload List..... | 253 | +| 9.3.1.108 | RAN Status Transfer Transparent Container..... | 253 | +| 9.3.1.109 | COUNT Value for PDCP SN Length 12..... | 255 | +| 9.3.1.110 | COUNT Value for PDCP SN Length 18..... | 255 | + +| | | | +|-----------|-------------------------------------------|-----| +| 9.3.1.111 | RRC Establishment Cause..... | 255 | +| 9.3.1.112 | Warning Area Coordinates..... | 256 | +| 9.3.1.113 | Network Instance..... | 256 | +| 9.3.1.114 | Secondary RAT Usage Information..... | 256 | +| 9.3.1.115 | Volume Timed Report List..... | 257 | +| 9.3.1.116 | Redirection for Voice EPS Fallback..... | 257 | +| 9.3.1.117 | UE Retention Information..... | 258 | +| 9.3.1.118 | UL Forwarding..... | 258 | +| 9.3.1.119 | CN Assisted RAN Parameters Tuning..... | 258 | +| 9.3.1.120 | Common Network Instance..... | 258 | +| 9.3.1.121 | Data Forwarding Response E-RAB List..... | 258 | +| 9.3.1.122 | gNB Set ID..... | 259 | +| 9.3.1.123 | RNC-ID..... | 259 | +| 9.3.1.124 | Extended RNC-ID..... | 259 | +| 9.3.1.125 | RAT Information..... | 259 | +| 9.3.1.126 | Extended RAT Restriction Information..... | 259 | +| 9.3.1.127 | SgNB UE X2AP ID..... | 260 | +| 9.3.1.128 | SRVCC Operation Possible..... | 260 | +| 9.3.1.129 | IAB Authorized..... | 260 | +| 9.3.1.130 | TSC Traffic Characteristics..... | 260 | +| 9.3.1.131 | TSC Assistance Information..... | 261 | +| 9.3.1.132 | Periodicity..... | 261 | +| 9.3.1.133 | Burst Arrival Time..... | 261 | +| 9.3.1.134 | Redundant QoS Flow Indicator..... | 261 | +| 9.3.1.135 | Extended Packet Delay Budget..... | 262 | +| 9.3.1.136 | Redundant PDU Session Information..... | 262 | +| 9.3.1.137 | NB-IoT Default Paging DRX..... | 262 | +| 9.3.1.138 | NB-IoT Paging eDRX Information..... | 262 | +| 9.3.1.139 | NB-IoT Paging DRX..... | 263 | +| 9.3.1.140 | Enhanced Coverage Restriction..... | 263 | + +| | | | +|-----------|--------------------------------------------------|-----| +| 9.3.1.141 | Paging Assistance Data for CE Capable UE..... | 263 | +| 9.3.1.142 | UE Radio Capability ID..... | 263 | +| 9.3.1.143 | WUS Assistance Information..... | 264 | +| 9.3.1.144 | UE Differentiation Information..... | 264 | +| 9.3.1.145 | NB-IoT UE Priority..... | 266 | +| 9.3.1.146 | NR V2X Services Authorized..... | 266 | +| 9.3.1.147 | LTE V2X Services Authorized..... | 266 | +| 9.3.1.148 | NR UE Sidelink Aggregate Maximum Bit Rate..... | 266 | +| 9.3.1.149 | LTE UE Sidelink Aggregate Maximum Bit Rate..... | 266 | +| 9.3.1.150 | PC5 QoS Parameters..... | 267 | +| 9.3.1.151 | Alternative QoS Parameters Set List..... | 267 | +| 9.3.1.152 | Alternative QoS Parameters Set Index..... | 268 | +| 9.3.1.153 | Alternative QoS Parameters Set Notify Index..... | 268 | +| 9.3.1.154 | E-UTRA Paging eDRX Information..... | 268 | +| 9.3.1.155 | CE-mode-B Restricted..... | 268 | +| 9.3.1.156 | CE-mode-B Support Indicator..... | 269 | +| 9.3.1.157 | LTE-M Indication..... | 269 | +| 9.3.1.158 | Suspend Request Indication..... | 269 | +| 9.3.1.159 | Suspend Response Indication..... | 269 | +| 9.3.1.160 | UE User Plane CIoT Support Indicator..... | 269 | +| 9.3.1.161 | Global TNGF ID..... | 270 | +| 9.3.1.162 | Global W-AGF ID..... | 270 | +| 9.3.1.163 | Global TWIF ID..... | 270 | +| 9.3.1.164 | W-AGF User Location Information..... | 271 | +| 9.3.1.165 | Global eNB ID..... | 272 | +| 9.3.1.166 | UE History Information from UE..... | 272 | +| 9.3.1.167 | MDT Configuration..... | 272 | +| 9.3.1.168 | MDT PLMN List..... | 272 | +| 9.3.1.169 | MDT Configuration-NR..... | 273 | +| 9.3.1.170 | MDT Configuration-EUTRA..... | 277 | + +| | | | +|-----------|-----------------------------------------------------------------------------|-----| +| 9.3.1.171 | M1 Configuration..... | 277 | +| 9.3.1.172 | M4 Configuration..... | 279 | +| 9.3.1.173 | M5 Configuration..... | 279 | +| 9.3.1.174 | M6 Configuration..... | 280 | +| 9.3.1.175 | M7 Configuration..... | 280 | +| 9.3.1.176 | MDT Location Information..... | 280 | +| 9.3.1.177 | Bluetooth Measurement Configuration..... | 281 | +| 9.3.1.178 | WLAN Measurement Configuration..... | 281 | +| 9.3.1.179 | Sensor Measurement Configuration..... | 281 | +| 9.3.1.180 | Event Trigger Logged MDT Configuration..... | 282 | +| 9.3.1.181 | NR Frequency Info..... | 283 | +| 9.3.1.182 | Area Scope of Neighbour Cells..... | 283 | +| 9.3.1.183 | NPN Paging Assistance Information..... | 283 | +| 9.3.1.184 | NPN Mobility Information..... | 284 | +| 9.3.1.185 | Cell CAG Information..... | 284 | +| 9.3.1.186 | Target to Source Failure Transparent Container..... | 285 | +| 9.3.1.187 | Target NG-RAN Node to Source NG-RAN Node Failure Transparent Container..... | 285 | +| 9.3.1.188 | DAPS Request Information..... | 285 | +| 9.3.1.189 | DAPS Response Information..... | 285 | +| 9.3.1.190 | Early Status Transfer Transparent Container..... | 286 | +| 9.3.1.191 | Extended Slice Support List..... | 287 | +| 9.3.1.192 | UE Capability Info Request..... | 287 | +| 9.3.1.193 | Extended RAN Node Name..... | 287 | +| 9.3.1.194 | MICO All PLMN..... | 287 | +| 9.3.1.195 | Source Node ID..... | 288 | +| 9.3.1.196 | E-UTRAN Composite Available Capacity Group..... | 288 | +| 9.3.1.197 | E-UTRAN Composite Available Capacity..... | 288 | +| 9.3.1.198 | E-UTRAN Cell Capacity Class Value..... | 288 | +| 9.3.1.199 | E-UTRAN Capacity Value..... | 288 | +| 9.3.1.200 | E-UTRAN Radio Resource Status..... | 289 | + +| | | | +|-----------|-----------------------------------------------------------------|-----| +| 9.3.1.201 | Void..... | 289 | +| 9.3.1.202 | Void..... | 289 | +| 9.3.1.203 | Void..... | 289 | +| 9.3.1.204 | Void..... | 289 | +| 9.3.1.205 | NR Radio Resource Status..... | 289 | +| 9.3.1.206 | MBS Session ID..... | 290 | +| 9.3.1.207 | MBS Area Session ID..... | 290 | +| 9.3.1.208 | MBS Service Area..... | 290 | +| 9.3.1.209 | MBS Service Area information..... | 291 | +| 9.3.1.210 | MBS Support Indicator..... | 291 | +| 9.3.1.211 | MBS Session Setup Request List..... | 291 | +| 9.3.1.212 | MBS Session Setup or Modify Request List..... | 292 | +| 9.3.1.213 | MBS Session Setup Response List..... | 293 | +| 9.3.1.214 | MBS Session Failed to Setup List..... | 293 | +| 9.3.1.215 | MBS Session To Release List..... | 294 | +| 9.3.1.216 | Multicast Group Paging Area..... | 294 | +| 9.3.1.217 | MBS Session Status..... | 294 | +| 9.3.1.218 | MRB ID..... | 295 | +| 9.3.1.219 | MRB Progress Information..... | 295 | +| 9.3.1.220 | Time Synchronisation Assistance Information..... | 295 | +| 9.3.1.221 | Survival Time..... | 295 | +| 9.3.1.222 | QMC Deactivation..... | 295 | +| 9.3.1.223 | QMC Configuration Information..... | 296 | +| 9.3.1.224 | UE Application Layer Measurement Configuration Information..... | 296 | +| 9.3.1.225 | Available RAN Visible QoE Metrics..... | 299 | +| 9.3.1.226 | Void..... | 299 | +| 9.3.1.227 | NR Paging eDRX Information..... | 299 | +| 9.3.1.228 | RedCap Indication..... | 300 | +| 9.3.1.229 | Target NSSAI Information..... | 300 | +| 9.3.1.230 | Target NSSAI..... | 300 | + +| | | | +|-----------|----------------------------------------------------|-----| +| 9.3.1.231 | UE Slice Maximum Bit Rate List..... | 300 | +| 9.3.1.232 | PEIPS Assistance Information..... | 301 | +| 9.3.1.233 | 5G ProSe Authorized..... | 301 | +| 9.3.1.234 | 5G ProSe PC5 QoS Parameters..... | 302 | +| 9.3.1.235 | Last Visited PSCell Information..... | 303 | +| 9.3.1.236 | MBS QoS Flows To Be Setup List..... | 303 | +| 9.3.1.237 | Reporting System..... | 304 | +| 9.3.1.238 | TAI NSAG Support List..... | 304 | +| 9.3.1.239 | NGAP Protocol IE-Id..... | 304 | +| 9.3.1.240 | NGAP Protocol IE Support Information..... | 304 | +| 9.3.1.241 | NGAP Protocol IE Presence Information..... | 305 | +| 9.3.1.242 | NGAP IE Support Information Response List..... | 305 | +| 9.3.1.243 | MDT PLMN Modification List..... | 305 | +| 9.3.1.244 | Excess Packet Delay Threshold Configuration..... | 305 | +| 9.3.1.245 | Network Controlled Repeater Authorized..... | 306 | +| 9.3.1.246 | Aerial UE Subscription Information..... | 306 | +| 9.3.1.247 | NR A2X Services Authorized..... | 306 | +| 9.3.1.248 | LTE A2X Services Authorized..... | 307 | +| 9.3.1.249 | A2X PC5 QoS Parameters..... | 307 | +| 9.3.1.250 | Clock Quality Reporting Control Information..... | 307 | +| 9.3.1.251 | Clock Quality Acceptance Criteria..... | 307 | +| 9.3.1.252 | RAN Timing Synchronisation Status Information..... | 308 | +| 9.3.1.253 | Clock Accuracy..... | 308 | +| 9.3.1.254 | RAN TSS Scope..... | 309 | +| 9.3.1.255 | Burst Arrival Time Window..... | 309 | +| 9.3.1.256 | Periodicity Range..... | 309 | +| 9.3.1.257 | TSC Traffic Characteristics Feedback..... | 310 | +| 9.3.1.258 | TSC Feedback Information..... | 310 | +| 9.3.1.259 | Mobile IAB Authorized..... | 310 | +| 9.3.1.260 | IAB-MT User Location Information..... | 310 | + +| | | | +|-----------|--------------------------------------------------------------|-----| +| 9.3.1.261 | Partially Allowed NSSAI..... | 311 | +| 9.3.1.262 | Associated Session ID..... | 311 | +| 9.3.1.263 | MBS Assistance Information..... | 311 | +| 9.3.1.264 | PDU Set QoS Parameters..... | 311 | +| 9.3.1.265 | N6 Jitter Information..... | 312 | +| 9.3.1.266 | ECN Marking or Congestion Information Reporting Request..... | 312 | +| 9.3.1.267 | ECN Marking or Congestion Information Reporting Status..... | 312 | +| 9.3.1.268 | PDU Set based Handling Indicator..... | 313 | +| 9.3.2 | Transport Network Layer Related IEs..... | 313 | +| 9.3.2.1 | QoS Flow per TNL Information List..... | 313 | +| 9.3.2.2 | UP Transport Layer Information..... | 313 | +| 9.3.2.3 | E-RAB ID..... | 313 | +| 9.3.2.4 | Transport Layer Address..... | 314 | +| 9.3.2.5 | GTP-TEID..... | 314 | +| 9.3.2.6 | CP Transport Layer Information..... | 314 | +| 9.3.2.7 | TNL Association List..... | 314 | +| 9.3.2.8 | QoS Flow per TNL Information..... | 315 | +| 9.3.2.9 | TNL Association Usage..... | 315 | +| 9.3.2.10 | TNL Address Weight Factor..... | 315 | +| 9.3.2.11 | UP Transport Layer Information Pair List..... | 315 | +| 9.3.2.12 | UP Transport Layer Information List..... | 315 | +| 9.3.2.13 | QoS Flow List with Data Forwarding..... | 316 | +| 9.3.2.14 | URI..... | 316 | +| 9.3.2.15 | MBS Session TNL Information 5GC..... | 317 | +| 9.3.2.16 | Shared NG-U Multicast TNL Information..... | 317 | +| 9.3.2.17 | MBS Session TNL Information NG-RAN..... | 317 | +| 9.3.3 | NAS Related IEs..... | 318 | +| 9.3.3.1 | AMF UE NGAP ID..... | 318 | +| 9.3.3.2 | RAN UE NGAP ID..... | 318 | +| 9.3.3.3 | GUAMI..... | 318 | + +| | | | +|----------|-----------------------------------------------|-----| +| 9.3.3.4 | NAS-PDU..... | 319 | +| 9.3.3.5 | PLMN Identity..... | 319 | +| 9.3.3.6 | SON Configuration Transfer..... | 319 | +| 9.3.3.7 | SON Information..... | 320 | +| 9.3.3.8 | SON Information Reply..... | 320 | +| 9.3.3.9 | Xn TNL Configuration Info..... | 320 | +| 9.3.3.10 | TAC..... | 321 | +| 9.3.3.11 | TAI..... | 321 | +| 9.3.3.12 | AMF Set ID..... | 322 | +| 9.3.3.13 | Routing ID..... | 322 | +| 9.3.3.14 | NRPPa-PDU..... | 322 | +| 9.3.3.15 | RAN Paging Priority..... | 322 | +| 9.3.3.16 | EPS TAC..... | 322 | +| 9.3.3.17 | EPS TAI..... | 323 | +| 9.3.3.18 | UE Paging Identity..... | 323 | +| 9.3.3.19 | AMF Pointer..... | 323 | +| 9.3.3.20 | 5G-S-TMSI..... | 323 | +| 9.3.3.21 | AMF Name..... | 323 | +| 9.3.3.22 | Paging Origin..... | 323 | +| 9.3.3.23 | UE Identity Index Value..... | 324 | +| 9.3.3.24 | Periodic Registration Update Timer..... | 324 | +| 9.3.3.25 | UE-associated Logical NG-connection List..... | 324 | +| 9.3.3.26 | NAS Security Parameters from NG-RAN..... | 325 | +| 9.3.3.27 | Source to Target AMF Information Reroute..... | 325 | +| 9.3.3.28 | RIM Information Transfer..... | 325 | +| 9.3.3.29 | RIM Information..... | 326 | +| 9.3.3.30 | LAI..... | 326 | +| 9.3.3.31 | Extended Connected Time..... | 326 | +| 9.3.3.32 | End Indication..... | 326 | +| 9.3.3.33 | Inter-system SON Configuration Transfer..... | 327 | + +| | | | +|----------|-------------------------------------------|-----| +| 9.3.3.34 | Inter-system SON Information..... | 327 | +| 9.3.3.35 | SON Information Report..... | 328 | +| 9.3.3.36 | Inter-system SON Information Report..... | 328 | +| 9.3.3.37 | Failure Indication..... | 329 | +| 9.3.3.38 | Inter-system Failure Indication..... | 329 | +| 9.3.3.39 | HO Report..... | 329 | +| 9.3.3.40 | Inter-system HO Report..... | 331 | +| 9.3.3.41 | UE RLF Report Container..... | 333 | +| 9.3.3.42 | NID..... | 333 | +| 9.3.3.43 | CAG ID..... | 333 | +| 9.3.3.44 | NPN Support..... | 334 | +| 9.3.3.45 | Allowed PNI-NPN List..... | 334 | +| 9.3.3.46 | NPN Access Information..... | 334 | +| 9.3.3.47 | Cell CAG List..... | 335 | +| 9.3.3.48 | UL CP Security Information..... | 335 | +| 9.3.3.49 | DL CP Security Information..... | 335 | +| 9.3.3.50 | Configured TAC Indication..... | 335 | +| 9.3.3.51 | Extended AMF Name..... | 335 | +| 9.3.3.52 | Extended UE Identity Index Value..... | 336 | +| 9.3.3.53 | NR NTN TAI Information..... | 336 | +| 9.3.3.54 | Inter-system SON Information Request..... | 336 | +| 9.3.3.55 | Inter-system SON Information Reply..... | 336 | +| 9.3.3.56 | Inter-system Cell Activation Request..... | 337 | +| 9.3.3.57 | Inter-system Cell State Indication..... | 337 | +| 9.3.3.58 | Inter-system Cell Activation Reply..... | 337 | +| 9.3.3.59 | Inter-system Resource Status Request..... | 337 | +| 9.3.3.60 | Inter-system Resource Status Report..... | 339 | +| 9.3.3.61 | Inter-system Resource Status Reply..... | 339 | +| 9.3.3.62 | Hashed UE Identity Index Value..... | 339 | +| 9.3.3.63 | Paging Policy Differentiation..... | 340 | + +| | | | +|----------|-------------------------------------------------------------------|-----| +| 9.3.3.64 | NR Paging Long eDRX Information for RRC INACTIVE..... | 340 | +| 9.3.3.65 | PNI-NPN Area Scope of MDT..... | 340 | +| 9.3.4 | SMF Related IEs..... | 341 | +| 9.3.4.1 | PDU Session Resource Setup Request Transfer..... | 341 | +| 9.3.4.2 | PDU Session Resource Setup Response Transfer..... | 343 | +| 9.3.4.3 | PDU Session Resource Modify Request Transfer..... | 345 | +| 9.3.4.4 | PDU Session Resource Modify Response Transfer..... | 347 | +| 9.3.4.5 | PDU Session Resource Notify Transfer..... | 349 | +| 9.3.4.6 | PDU Session Resource Modify Indication Transfer..... | 351 | +| 9.3.4.7 | PDU Session Resource Modify Confirm Transfer..... | 351 | +| 9.3.4.8 | Path Switch Request Transfer..... | 352 | +| 9.3.4.9 | Path Switch Request Acknowledge Transfer..... | 354 | +| 9.3.4.10 | Handover Command Transfer..... | 356 | +| 9.3.4.11 | Handover Request Acknowledge Transfer..... | 357 | +| 9.3.4.12 | PDU Session Resource Release Command Transfer..... | 359 | +| 9.3.4.13 | PDU Session Resource Notify Released Transfer..... | 359 | +| 9.3.4.14 | Handover Required Transfer..... | 359 | +| 9.3.4.15 | Path Switch Request Setup Failed Transfer..... | 360 | +| 9.3.4.16 | PDU Session Resource Setup Unsuccessful Transfer..... | 360 | +| 9.3.4.17 | PDU Session Resource Modify Unsuccessful Transfer..... | 360 | +| 9.3.4.18 | Handover Preparation Unsuccessful Transfer..... | 360 | +| 9.3.4.19 | Handover Resource Allocation Unsuccessful Transfer..... | 360 | +| 9.3.4.20 | Path Switch Request Unsuccessful Transfer..... | 360 | +| 9.3.4.21 | PDU Session Resource Release Response Transfer..... | 361 | +| 9.3.4.22 | PDU Session Resource Modify Indication Unsuccessful Transfer..... | 361 | +| 9.3.4.23 | Secondary RAT Data Usage Report Transfer..... | 361 | +| 9.3.4.24 | UE Context Resume Request Transfer..... | 361 | +| 9.3.4.25 | UE Context Resume Response Transfer..... | 361 | +| 9.3.4.26 | UE Context Suspend Request Transfer..... | 362 | +| 9.3.5 | MB-SMF Related IEs..... | 362 | + +| | | | +|----------|-------------------------------------------------------------------|-----| +| 9.3.5.1 | Void..... | 362 | +| 9.3.5.2 | Void..... | 362 | +| 9.3.5.3 | MBS Session Setup or Modification Request Transfer..... | 362 | +| 9.3.5.4 | Void..... | 362 | +| 9.3.5.5 | MBS Session Setup or Modification Response Transfer..... | 362 | +| 9.3.5.6 | MBS Session Setup or Modification Failure Transfer..... | 362 | +| 9.3.5.7 | MBS Distribution Setup Request Transfer..... | 363 | +| 9.3.5.8 | MBS Distribution Setup Response Transfer..... | 363 | +| 9.3.5.9 | MBS Distribution Setup Unsuccessful Transfer..... | 363 | +| 9.3.5.10 | MBS Distribution Release Request Transfer..... | 363 | +| 9.3.5.11 | Multicast Session Activation Request Transfer..... | 364 | +| 9.3.5.12 | Multicast Session Deactivation Request Transfer..... | 364 | +| 9.3.5.13 | Multicast Session Update Request Transfer..... | 364 | +| 9.3.5.14 | MBS Session Release Response Transfer..... | 364 | +| 9.3.5.15 | Broadcast Transport Request Transfer..... | 365 | +| 9.3.5.16 | Broadcast Transport Response Transfer..... | 365 | +| 9.3.5.17 | Broadcast Transport Failure Transfer..... | 365 | +| 9.4 | Message and Information Element Abstract Syntax (with ASN.1)..... | 365 | +| 9.4.1 | General..... | 365 | +| 9.4.2 | Usage of private message mechanism for non-standard use..... | 366 | +| 9.4.3 | Elementary Procedure Definitions..... | 367 | +| 9.4.4 | PDU Definitions..... | 385 | +| 9.4.5 | Information Element Definitions..... | 457 | +| 9.4.6 | Common Definitions..... | 612 | +| 9.4.7 | Constant Definitions..... | 612 | +| 9.4.8 | Container Definitions..... | 625 | +| 9.5 | Message Transfer Syntax..... | 630 | +| 9.6 | Timers..... | 630 | +| 10 | Handling of Unknown, Unforeseen and Erroneous Protocol Data..... | 631 | +| 10.1 | General..... | 631 | + +| | | | +|-------------------------------|---------------------------------------------------------------------------------------------------|------------| +| 10.2 | Transfer Syntax Error..... | 631 | +| 10.3 | Abstract Syntax Error..... | 631 | +| 10.3.1 | General..... | 631 | +| 10.3.2 | Criticality Information..... | 632 | +| 10.3.3 | Presence Information..... | 632 | +| 10.3.4 | Not comprehended IE/IE group..... | 633 | +| 10.3.4.1 | Procedure Code..... | 633 | +| 10.3.4.1A | Type of Message..... | 633 | +| 10.3.4.2 | IEs other than the Procedure Code and Type of Message..... | 633 | +| 10.3.5 | Missing IE or IE group..... | 634 | +| 10.3.6 | IEs or IE groups received in wrong order or with too many occurrences or erroneously present..... | 635 | +| 10.4 | Logical Error..... | 636 | +| 10.5 | Exceptions..... | 636 | +| 10.6 | Handling of AP ID..... | 637 | +| Annex A (informative): | Change history..... | 638 | + +--- + +## Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- Y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +--- + +# 1 Scope + +The present document specifies the radio network layer signalling protocol for the NG interface. The NG Application Protocol (NGAP) supports the functions of the NG interface by signalling procedures defined in this document. NGAP is developed in accordance to the general principles stated in TS 38.401 [2] and TS 38.410 [3]. + +--- + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 38.401: "NG-RAN; Architecture description". +- [3] 3GPP TS 38.410: "NG-RAN; NG general aspects and principles". +- [4] ITU-T Recommendation X.691 (07/2002): "Information technology – ASN.1 encoding rules: Specification of Packed Encoding Rules (PER)". +- [5] ITU-T Recommendation X.680 (07/2002): "Information technology – Abstract Syntax Notation One (ASN.1): Specification of basic notation". +- [6] ITU-T Recommendation X.681 (07/2002): "Information technology – Abstract Syntax Notation One (ASN.1): Information object specification". +- [7] 3GPP TR 25.921 (version.7.0.0): "Guidelines and principles for protocol description and error handling". +- [8] 3GPP TS 38.300: "NR; NR and NG-RAN Overall Description; Stage 2". +- [9] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2". +- [10] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2". +- [11] 3GPP TS 32.422: "Trace control and configuration management". +- [12] 3GPP TS 38.304: "NR; User Equipment (UE) procedures in idle mode and in RRC inactive state". +- [13] 3GPP TS 33.501: "Security architecture and procedures for 5G System". +- [14] 3GPP TS 38.414: "NG-RAN; NG data transport". +- [15] 3GPP TS 29.281: "General Packet Radio System (GPRS); Tunnelling Protocol User Plane (GTPv1-U)". +- [16] 3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)". + +- [17] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2". +- [18] 3GPP TS 38.331: "NG-RAN; Radio Resource Control (RRC) Protocol Specification". +- [19] 3GPP TS 38.455: "NG-RAN; NR Positioning Protocol A (NRPPa)". +- [20] 3GPP TS 23.007: "Technical Specification Group Core Network Terminals; Restoration procedures". +- [21] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource Control (RRC); Protocol specification". +- [22] 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)". +- [23] 3GPP TS 23.003: "Numbering, addressing and identification". +- [24] 3GPP TS 38.423: "NG-RAN; Xn Application Protocol (XnAP)". +- [25] IETF RFC 5905 (2010-06): "Network Time Protocol Version 4: Protocol and Algorithms Specification". +- [26] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3". +- [27] 3GPP TS 33.401: "3GPP System Architecture Evolution (SAE); Security architecture". +- [28] 3GPP TS 25.413: "UTRAN Iu interface RANAP signalling". +- [29] 3GPP TS 36.304: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode". +- [30] 3GPP TS 29.531: "5G System; Network Slice Selection Services; Stage 3". +- [31] 3GPP TS 23.216: "Single Radio Voice Call Continuity (SRVCC); Stage 2". +- [32] 3GPP TS 37.340: " Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Stage 2". +- [33] 3GPP TS 23.287: "Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services". +- [34] 3GPP TS 23.316: "Wireless and wireline convergence access support for the 5G System (5GS)". +- [35] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3". +- [36] 3GPP TS 29.510: "5G System; Network Function Repository Services; Stage 3". +- [37] CableLabs WR-TR-5WWC-ARCH: "5G Wireless Wireline Converged Core Architecture". +- [38] 3GPP TS 36.401: "E-UTRAN Architecture Description". +- [39] 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception". +- [40] 3GPP TS 36.423: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP) ". +- [41] 3GPP TS 37.320: "Universal Terrestrial Radio Access (UTRA), Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Radio measurement collection for Minimization of Drive Tests (MDT); Overall description; Stage 2". +- [42] 3GPP TS 36.306: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio access capabilities". + +- [43] 3GPP TS 29.244: "Interface between the Control Plane and the User Plane Nodes; Stage 3". +- [44] 3GPP TS 23.247: "Architectural enhancements for 5G multicast-broadcast services; Stage 2". +- [45] 3GPP TS 28.405: "Telecommunication management; Quality of Experience (QoE) measurement collection; Control and configuration". +- [46] 3GPP TS 26.247: "Transparent end-to-end Packet-switched Streaming Service (PSS); Progressive Download and Dynamic Adaptive Streaming over HTTP (3GP-DASH)". +- [47] 3GPP TS 23.304: "Proximity based Services (ProSe) in the 5G System (5GS)". +- [48] 3GPP TS 38.314: "NR; Layer 2 Measurements". +- [49] 3GPP TS 36.314: "Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 - Measurements". +- [50] 3GPP TS 23.203: "Policy and charging control architecture". +- [51] 3GPP TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction". +- [52] 3GPP TS 26.118: "Virtual Reality (VR) profiles for streaming applications". +- [53] IETF RFC 4122: "A Universally Unique Identifier (UUID) URN Namespace". +- [54] 3GPP TS 23.256: "Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2". +- [55] IEEE Std 1588: "IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems", Edition 2019. +- [56] 3GPP TS 29.585: "5G System (5GS); Session Management Function (SMF) / Centralized User Configuration (CUC) to Access Network Talker Listener (AN-TL) and Core Network Talker Listener (CN-TL) protocol aspects; Stage 3". + +--- + +## 3 Definitions and abbreviations + +### 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**ACL functionality:** as defined in TS 36.413 [16]. + +**CAG cell:** as defined in TS 38.300 [8]. + +**DAPS Handover:** as defined in TS 38.300 [8]. + +**Elementary Procedure:** NGAP consists of Elementary Procedures (EPs). An Elementary Procedure is a unit of interaction between the NG-RAN node and the AMF. 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 NGAP EPs together or together with EPs from other interfaces is specified in stage 2 specifications (e.g., TS 38.401 [2], TS 38.410 [3] and TS 38.300 [8]). + +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. + +**en-gNB:** as defined in TS 37.340 [32]. + +**gNB:** as defined in TS 38.300 [8]. + +**MBS session resource:** as defined in TS 38.401 [2]. + +**Mobile IAB-node:** as defined in TS 38.300 [8]. + +**Mobile IAB-MT:** as defined in TS 38.300 [8]. + +**NB-IoT:** as defined in TS 36.300 [17]. + +**ng-eNB:** as defined in TS 38.300 [8]. + +**NG-RAN node:** as defined in TS 38.300 [8]. + +**Non-CAG cell:** as defined in TS 38.300 [8]. + +**PDU session resource:** as defined in TS 38.401 [2]. + +**Public Network Integrated NPN:** as defined in TS 23.501 [9]. + +**Stand-alone Non-Public Network:** as defined in TS 23.501 [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]. + +| | | +|-----|-----------------------------------------| +| 5GC | 5G Core Network | +| 5QI | 5G QoS Identifier | +| ACL | Access Control List | +| AMF | Access and Mobility Management Function | +| CAG | Closed Access Group | + +| | | +|---------------|-----------------------------------------------------------------------------| +| CGI | Cell Global Identifier | +| CP | Control Plane | +| DAPS | Dual Active Protocol Stacks | +| DC | Dual Connectivity | +| DL | Downlink | +| EPC | Evolved Packet Core | +| FN-RG | Fixed Network Residential Gateway | +| GUAMI | Globally Unique AMF Identifier | +| HFC | Hybrid Fiber-Coax | +| IAB | Integrated Access and Backhaul | +| IMEISV | International Mobile station Equipment Identity and Software Version number | +| LMF | Location Management Function | +| MBS | Multicast/Broadcast Service | +| N3IWF | Non 3GPP InterWorking Function | +| NB-IoT | Narrow Band Internet of Things | +| NID | Network Identifier | +| NGAP | NG Application Protocol | +| NPN | Non-Public Network | +| NRPPa | NR Positioning Protocol Annex | +| NSAG | Network Slice AS Group | +| NSCI | New Security Context Indicator | +| NSSAI | Network Slice Selection Assistance Information | +| OTDOA | Observed Time Difference of Arrival | +| PEIPS | Paging Early Indication with Paging Subgrouping | +| PNI-NPN | Public Network Integrated Non-Public Network | +| ProSe | Proximity Services | +| PSCell | Primary SCG Cell | +| PTP | Point to Point | +| PTM | Point to Multipoint | +| QMC | QoE Measurement Collection | +| QoE | Quality of Experience | +| RedCap | Reduced Capability | +| RIM | Remote Interference Management | +| RIM-RS | RIM Reference Signal | +| RSN | Redundancy Sequence Number | +| SCG | Secondary Cell Group | +| SCTP | Stream Control Transmission Protocol | +| SgNB | Secondary gNB | +| SMF | Session Management Function | +| S-NG-RAN node | Secondary NG-RAN node | +| SNPN | Stand-alone Non-Public Network | +| S-NSSAI | Single Network Slice Selection Assistance Information | +| TAC | Tracking Area Code | +| TAI | Tracking Area Identity | +| TSS | Timing Synchronisation Status | +| TNAP | Trusted Non-3GPP Access Point | +| TNGF | Trusted Non-3GPP Gateway Function | +| TNLA | Transport Network Layer Association | +| TWAP | Trusted WLAN Access Point | +| TWIF | Trusted WLAN Interworking Function | +| UL | Uplink | +| UP | User Plane | +| UPF | User Plane Function | + +| | | +|-------|----------------------------------| +| V2X | Vehicle-to-Everything | +| W-AGF | Wireline Access Gateway Function | +| WUS | Wake Up Signal | + +--- + +## 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., Procedure Name 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., MESSAGE NAME 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., *Information Element IE*. + +Value of an IE When referring to the value of an information element (IE) in the specification the "Value" is written as it is specified in subclause 9.2 enclosed by quotation marks, e.g., "Value". + +## 5 NGAP Services + +NGAP provides the signalling service between the NG-RAN node and the AMF that is required to fulfil the NGAP functions described in TS 38.410 [3]. NGAP services are divided into two groups: + +Non UE-associated services: They are related to the whole NG interface instance between the NG-RAN node and AMF utilising a non UE-associated signalling connection. + +UE-associated services: They are related to one UE. NGAP functions that provide these services are associated with a UE-associated signalling connection that is maintained for the UE in question. + +## 6 Services Expected from Signalling Transport + +The signalling connection shall provide in sequence delivery of NGAP messages. NGAP shall be notified if the signalling connection breaks. + +## 7 Functions of NGAP + +The functions of NGAP are described in TS 38.410 [3]. + +## 8 NGAP Procedures + +### 8.1 List of NGAP 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 8.1-1: Class 1 procedures** + +| Elementary Procedure | Initiating Message | Successful Outcome | Unsuccessful Outcome | +|--------------------------|--------------------------|-----------------------------------------|----------------------------------| +| | | Response message | Response message | +| AMF Configuration Update | AMF CONFIGURATION UPDATE | AMF CONFIGURATION UPDATE
ACKNOWLEDGE | AMF CONFIGURATION UPDATE FAILURE | +| RAN Configuration Update | RAN CONFIGURATION UPDATE | RAN CONFIGURATION UPDATE
ACKNOWLEDGE | RAN CONFIGURATION UPDATE FAILURE | +| Handover Cancellation | HANDOVER CANCEL | HANDOVER CANCEL
ACKNOWLEDGE | | +| Handover Preparation | HANDOVER REQUIRED | HANDOVER COMMAND | HANDOVER PREPARATION FAILURE | + +| Elementary Procedure | Initiating Message | Successful Outcome | Unsuccessful Outcome | +|----------------------------------------|----------------------------------------|-----------------------------------------|----------------------------------------| +| | | Response message | Response message | +| Handover Resource Allocation | HANDOVER REQUEST | HANDOVER REQUEST ACKNOWLEDGE | HANDOVER FAILURE | +| Initial Context Setup | INITIAL CONTEXT SETUP REQUEST | INITIAL CONTEXT SETUP RESPONSE | INITIAL CONTEXT SETUP FAILURE | +| NG Reset | NG RESET | NG RESET ACKNOWLEDGE | | +| NG Setup | NG SETUP REQUEST | NG SETUP RESPONSE | NG SETUP FAILURE | +| Path Switch Request | PATH SWITCH REQUEST | PATH SWITCH REQUEST ACKNOWLEDGE | PATH SWITCH REQUEST FAILURE | +| PDU Session Resource Modify | PDU SESSION RESOURCE MODIFY REQUEST | PDU SESSION RESOURCE MODIFY RESPONSE | | +| PDU Session Resource Modify Indication | PDU SESSION RESOURCE MODIFY INDICATION | PDU SESSION RESOURCE MODIFY CONFIRM | | +| PDU Session Resource Release | PDU SESSION RESOURCE RELEASE COMMAND | PDU SESSION RESOURCE RELEASE RESPONSE | | +| PDU Session Resource Setup | PDU SESSION RESOURCE SETUP REQUEST | PDU SESSION RESOURCE SETUP RESPONSE | | +| UE Context Modification | UE CONTEXT MODIFICATION REQUEST | UE CONTEXT MODIFICATION RESPONSE | UE CONTEXT MODIFICATION FAILURE | +| UE Context Release | UE CONTEXT RELEASE COMMAND | UE CONTEXT RELEASE COMPLETE | | +| Write-Replace Warning | WRITE-REPLACE WARNING REQUEST | WRITE-REPLACE WARNING RESPONSE | | +| PWS Cancel | PWS CANCEL REQUEST | PWS CANCEL RESPONSE | | +| UE Radio Capability Check | UE RADIO CAPABILITY CHECK REQUEST | UE RADIO CAPABILITY CHECK RESPONSE | | +| UE Context Suspend | UE CONTEXT SUSPEND REQUEST | UE CONTEXT SUSPEND RESPONSE | UE CONTEXT SUSPEND FAILURE | +| UE Context Resume | UE CONTEXT RESUME REQUEST | UE CONTEXT RESUME RESPONSE | UE CONTEXT RESUME FAILURE | +| UE Radio Capability ID Mapping | UE RADIO CAPABILITY ID MAPPING REQUEST | UE RADIO CAPABILITY ID MAPPING RESPONSE | | +| Broadcast Session Setup | BROADCAST SESSION SETUP REQUEST | BROADCAST SESSION SETUP RESPONSE | BROADCAST SESSION SETUP FAILURE | +| Broadcast Session Modification | BROADCAST SESSION MODIFICATION REQUEST | BROADCAST SESSION MODIFICATION RESPONSE | BROADCAST SESSION MODIFICATION FAILURE | +| Broadcast Session Release | BROADCAST SESSION RELEASE REQUEST | BROADCAST SESSION RELEASE RESPONSE | | +| Distribution Setup | DISTRIBUTION SETUP REQUEST | DISTRIBUTION SETUP RESPONSE | DISTRIBUTION SETUP FAILURE | +| Distribution Release | DISTRIBUTION RELEASE REQUEST | DISTRIBUTION RELEASE RESPONSE | | + +| Elementary Procedure | Initiating Message | Successful Outcome | Unsuccessful Outcome | +|--------------------------------|----------------------------------------|-----------------------------------------|---------------------------------------| +| | | Response message | Response message | +| Multicast Session Activation | MULTICAST SESSION ACTIVATION REQUEST | MULTICAST SESSION ACTIVATION RESPONSE | MULTICAST SESSION ACTIVATION FAILURE | +| Multicast Session Deactivation | MULTICAST SESSION DEACTIVATION REQUEST | MULTICAST SESSION DEACTIVATION RESPONSE | | +| Multicast Session Update | MULTICAST SESSION UPDATE REQUEST | MULTICAST SESSION UPDATE RESPONSE | MULTICAST SESSION UPDATE FAILURE | +| Timing Synchronisation Status | TIMING SYNCHRONISATION STATUS REQUEST | TIMING SYNCHRONISATION STATUS RESPONSE | TIMING SYNCHRONISATION STATUS FAILURE | +| MT Communication Handling | MT COMMUNICATION HANDLING REQUEST | MT COMMUNICATION HANDLING RESPONSE | MT COMMUNICATION HANDLING FAILURE | +| Broadcast Session Transport | BROADCAST SESSION TRANSPORT REQUEST | BROADCAST SESSION TRANSPORT RESPONSE | BROADCAST SESSION TRANSPORT FAILURE | + +**Table 8.1-2: Class 2 procedures** + +| Elementary Procedure | Message | +|--------------------------------------------|--------------------------------------------| +| Downlink RAN Configuration Transfer | DOWNLINK RAN CONFIGURATION TRANSFER | +| Downlink RAN Status Transfer | DOWNLINK RAN STATUS TRANSFER | +| Downlink NAS Transport | DOWNLINK NAS TRANSPORT | +| Error Indication | ERROR INDICATION | +| Uplink RAN Configuration Transfer | UPLINK RAN CONFIGURATION TRANSFER | +| Uplink RAN Status Transfer | UPLINK RAN STATUS TRANSFER | +| Handover Notification | HANDOVER NOTIFY | +| Initial UE Message | INITIAL UE MESSAGE | +| NAS Non Delivery Indication | NAS NON DELIVERY INDICATION | +| Paging | PAGING | +| PDU Session Resource Notify | PDU SESSION RESOURCE NOTIFY | +| Reroute NAS Request | REROUTE NAS REQUEST | +| UE Context Release Request | UE CONTEXT RELEASE REQUEST | +| Uplink NAS Transport | UPLINK NAS TRANSPORT | +| AMF Status Indication | AMF STATUS INDICATION | +| PWS Restart Indication | PWS RESTART INDICATION | +| PWS Failure Indication | PWS FAILURE INDICATION | +| Downlink UE Associated NRPPa Transport | DOWNLINK UE ASSOCIATED NRPPA TRANSPORT | +| Uplink UE Associated NRPPa Transport | UPLINK UE ASSOCIATED NRPPA TRANSPORT | +| Downlink Non UE Associated NRPPa Transport | DOWNLINK NON UE ASSOCIATED NRPPA TRANSPORT | +| Uplink Non UE Associated NRPPa Transport | UPLINK NON UE ASSOCIATED NRPPA TRANSPORT | +| Trace Start | TRACE START | +| Trace Failure Indication | TRACE FAILURE INDICATION | +| Deactivate Trace | DEACTIVATE TRACE | +| Cell Traffic Trace | CELL TRAFFIC TRACE | +| Location Reporting Control | LOCATION REPORTING CONTROL | +| Location Reporting Failure Indication | LOCATION REPORTING FAILURE INDICATION | +| Location Report | LOCATION REPORT | +| UE TNLA Binding Release | UE TNLA BINDING RELEASE REQUEST | +| UE Radio Capability Info Indication | UE RADIO CAPABILITY INFO INDICATION | +| RRC Inactive Transition Report | RRC INACTIVE TRANSITION REPORT | +| Overload Start | OVERLOAD START | +| Overload Stop | OVERLOAD STOP | +| Secondary RAT Data Usage Report | SECONDARY RAT DATA USAGE REPORT | +| Uplink RIM Information Transfer | UPLINK RIM INFORMATION TRANSFER | +| Downlink RIM Information Transfer | DOWNLINK RIM INFORMATION TRANSFER | +| Retrieve UE Information | RETRIEVE UE INFORMATION | +| UE Information Transfer | UE INFORMATION TRANSFER | +| RAN CP Relocation Indication | RAN CP RELOCATION INDICATION | +| Connection Establishment Indication | CONNECTION ESTABLISHMENT INDICATION | +| AMF CP Relocation Indication | AMF CP RELOCATION INDICATION | +| Handover Success | HANDOVER SUCCESS | +| Uplink RAN Early Status Transfer | UPLINK RAN EARLY STATUS TRANSFER | +| Downlink RAN Early Status Transfer | DOWNLINK RAN EARLY STATUS TRANSFER | +| Multicast Group Paging | MULTICAST GROUP PAGING | +| Broadcast Session Release Required | BROADCAST SESSION RELEASE REQUIRED | +| Timing Synchronisation Status Report | TIMING SYNCHRONISATION STATUS REPORT | +| RAN Paging Request | RAN PAGING REQUEST | + +## 8.2 PDU Session Management Procedures + +### 8.2.1 PDU Session Resource Setup + +#### 8.2.1.1 General + +The purpose of the PDU Session Resource Setup procedure is to assign resources on Uu and NG-U for one or several PDU sessions and the corresponding QoS flows, and to setup corresponding DRBs for a given UE. The procedure uses UE-associated signalling. + +#### 8.2.1.2 Successful Operation + +![Sequence diagram showing the successful operation of PDU session resource setup between an NG-RAN node and an AMF. The AMF sends a PDU SESSION RESOURCE SETUP REQUEST message to the NG-RAN node, and the NG-RAN node responds with a PDU SESSION RESOURCE SETUP RESPONSE message.](a3083eec2a883ee8327b3c24174df6a9_img.jpg) + +``` + +sequenceDiagram + participant AMF + participant NG-RAN node + Note left of NG-RAN node: + AMF->>NG-RAN node: PDU SESSION RESOURCE SETUP REQUEST + NG-RAN node-->>AMF: PDU SESSION RESOURCE SETUP RESPONSE + Note right of AMF: + +``` + +Sequence diagram showing the successful operation of PDU session resource setup between an NG-RAN node and an AMF. The AMF sends a PDU SESSION RESOURCE SETUP REQUEST message to the NG-RAN node, and the NG-RAN node responds with a PDU SESSION RESOURCE SETUP RESPONSE message. + +**Figure 8.2.1.2-1: PDU session resource setup: successful operation** + +The AMF initiates the procedure by sending a PDU SESSION RESOURCE SETUP REQUEST message to the NG-RAN node. + +The PDU SESSION RESOURCE SETUP REQUEST message shall contain the information required by the NG-RAN node to setup the PDU session related NG-RAN configuration consisting of at least one PDU session resource and include each PDU session resource to setup in the *PDU Session Resource Setup Request List IE*. + +Upon reception of the PDU SESSION RESOURCE SETUP REQUEST message, if resources are available for the requested configuration, the NG-RAN node shall execute the requested NG-RAN configuration and allocate associated resources over NG and over Uu for each PDU session listed in the *PDU Session Resource Setup Request List IE*. + +If the *RAN Paging Priority IE* is included in the PDU SESSION RESOURCE SETUP REQUEST message, the NG-RAN node may use it to determine a priority for paging the UE in RRC\_INACTIVE state. + +For each requested PDU session, if resources are available for the requested configuration, the NG-RAN node shall establish at least one DRB and associate each accepted QoS flow of the PDU session which is not associated with an MBS QoS flow to a DRB established. + +For each PDU session successfully established the NG-RAN node shall pass to the UE the *PDU Session NAS-PDU IE*, if included. The NG-RAN node shall not send to the UE the PDU Session NAS PDUs associated to the failed PDU sessions. + +If the *NAS-PDU IE* is included in the PDU SESSION RESOURCE SETUP REQUEST message, the NG-RAN node shall pass it to the UE. + +For each PDU session the NG-RAN node shall store the *UL NG-U UP TNL Information IE* included in the *PDU Session Resource Setup Request Transfer IE* contained in the PDU SESSION RESOURCE SETUP REQUEST message and use it as the uplink termination point for the user plane data for this PDU session. + +For each PDU session, if the *Additional UL NG-U UP TNL Information IE* is included in the *PDU Session Resource Setup Request Transfer IE* contained in the PDU SESSION RESOURCE SETUP REQUEST message, the NG-RAN + +node may allocate for this split PDU session resources for an additional NG-U transport bearer for some or all of the QoS flows present in the *QoS Flow Setup Request List* IE and it shall indicate these QoS flows in the *Additional DL QoS Flow per TNL Information* IE in the *PDU Session Resource Setup Response Transfer* IE. In case the *Additional DL QoS Flow per TNL Information* IE is not included the SMF shall consider the proposed additional UL NG-U UP TNL information as available again. + +For each PDU session, if the *Network Instance* IE is included in the *PDU Session Resource Setup Request Transfer* IE contained in the PDU SESSION RESOURCE SETUP REQUEST message and the *Common Network Instance* IE is not present, the NG-RAN node shall, if supported, use it when selecting transport network resource as specified in TS 23.501 [9]. + +For each PDU session, if the *Common Network Instance* IE is included in the *PDU Session Resource Setup Request Transfer* IE or in the *Additional UL NG-U UP TNL Information* IE, or in the *Additional Redundant UL NG-U UP TNL Information* IE contained in the PDU SESSION RESOURCE SETUP REQUEST message, the NG-RAN node shall, if supported, use it when selecting transport network resource for the concerned NG-U transport bearer as specified in TS 23.501 [9]. + +For each PDU session, if the *Redundant UL NG-U UP TNL Information* IE is included in the *PDU Session Resource Setup Request Transfer* IE of the PDU SESSION RESOURCE SETUP REQUEST message, the NG-RAN node shall, if supported, use it as the uplink termination point for the user plane data for this PDU session for the redundant transmission and it shall include the *Redundant QoS Flow per TNL Information* IE in the *PDU Session Resource Setup Response Transfer* IE as described in TS 23.501 [9]. + +For each PDU session, if the *Additional Redundant UL NG-U UP TNL Information* IE is included in the *PDU Session Resource Setup Request Transfer* IE contained in the PDU SESSION RESOURCE SETUP REQUEST message, the NG-RAN node may allocate for this split PDU session resources for an additional redundant NG-U transport bearer for some or all of the QoS flows present in the *QoS Flow Setup Request List* IE and it shall indicate these QoS flows in the *Additional Redundant DL QoS Flow per TNL Information* IE in the *PDU Session Resource Setup Response Transfer* IE. In case the *Additional Redundant DL QoS Flow per TNL Information* IE is not included the SMF shall consider the proposed additional Redundant UL NG-U UP TNL information as available again. + +For each PDU session, if the *Redundant Common Network Instance* IE is included in the *PDU Session Resource Setup Request Transfer* IE contained in the PDU SESSION RESOURCE SETUP REQUEST message, the NG-RAN node shall, if supported, use it when selecting transport network resource for the redundant transmission as specified in TS 23.501 [9]. + +For each PDU session, if the *TSC Traffic Characteristics* IE is included in the *PDU Session Resource Setup Request Transfer* IE contained in the PDU SESSION RESOURCE SETUP REQUEST message, the NG-RAN node shall, if supported, store it and use it as specified in TS 23.501 [9]. For each QoS flow which has been successfully established, if the *Burst Arrival Time* IE is included in the *TSC Assistance Information Uplink* IE of the *TSC Traffic Characteristics* IE, the NG-RAN node may include the *AN Packet Delay Budget Uplink* IE for the same QoS flow within the PDU SESSION RESOURCE SETUP RESPONSE message as specified in TS 23.501 [9]. If the *RAN Feedback Type* IE is included in the *TSC Traffic Characteristics* IE, the NG-RAN node shall, if supported, take this information into account when determining the feedback to provide in the *TSC Traffic Characteristics Feedback* IE in the *PDU Session Resource Setup Response Transfer* IE in the PDU SESSION RESOURCE SETUP RESPONSE message as specified in TS 23.501 [9]. + +For each PDU session, if the *PDU Session Type* IE included in the *PDU Session Resource Setup Request Transfer* IE of the PDU SESSION RESOURCE SETUP REQUEST message is set to "ethernet", the NG-RAN node may perform appropriate header compression for the concerned PDU session, or if it is set to "unstructured", the NG-RAN node shall not perform header compression for the concerned PDU session. + +For each PDU session for which the *Security Indication* IE is included in the *PDU Session Resource Setup Request Transfer* IE of the PDU SESSION RESOURCE SETUP REQUEST message, and the *Integrity Protection Indication* IE or *Confidentiality Protection Indication* IE is set to "required", then the NG-RAN node shall perform user plane integrity protection or ciphering, respectively, for the concerned PDU session. If the NG-RAN node cannot perform the + +user plane integrity protection or ciphering, it shall reject the setup of the PDU session resources with an appropriate cause value. + +If the NG-RAN node is an ng-eNB, it shall behave as specified in TS 33.501 [13]. + +For each PDU session for which the *Security Indication* IE is included in the *PDU Session Resource Setup Request Transfer* IE of the PDU SESSION RESOURCE SETUP REQUEST message, and the *Integrity Protection Indication* IE or *Confidentiality Protection Indication* IE is set to "preferred", then the NG-RAN node should, if supported, perform user plane integrity protection or ciphering, respectively, for the concerned PDU session and shall notify whether it performed the user plane integrity protection or ciphering by including the *Integrity Protection Result* IE or *Confidentiality Protection Result* IE, respectively, in the *PDU Session Resource Setup Response Transfer* IE of the PDU SESSION RESOURCE SETUP RESPONSE message. + +For each PDU session for which the *Maximum Integrity Protected Data Rate Downlink* IE or the *Maximum Integrity Protected Data Rate Uplink* IE are included in the *Security Indication* IE in the *PDU Session Resource Setup Request Transfer* IE of the PDU SESSION RESOURCE SETUP REQUEST message, the NG-RAN node shall store the respective information and, if integrity protection is to be performed for the PDU session, it shall enforce the traffic limits corresponding to the received values, for the concerned PDU session and concerned UE, as specified in TS 23.501 [9]. + +For each PDU session for which the *Security Indication* IE is included in the *PDU Session Resource Setup Request Transfer* IE of the PDU SESSION RESOURCE SETUP REQUEST message: + +- if the *Integrity Protection Indication* IE is set to "not needed", then the NG-RAN node shall not perform user plane integrity protection for the concerned PDU session; +- if the *Confidentiality Protection Indication* IE is set to "not needed", then the NG-RAN node shall not perform user plane ciphering for the concerned PDU session. + +For each PDU session for which the *PDU Session Aggregate Maximum Bit Rate* IE is included in the *PDU Session Resource Setup Request Transfer* IE of the PDU SESSION RESOURCE SETUP REQUEST message, the NG-RAN node shall store the received value in the UE context and use it when enforcing traffic policing for Non-GBR QoS flows for the concerned UE as specified in TS 23.501 [9]. + +For each PDU session in the PDU SESSION RESOURCE SETUP REQUEST message, if the *Additional QoS Flow Information* IE is included in the *QoS Flow Level QoS Parameters* IE in the *PDU Session Resource Setup Request Transfer* IE of the PDU SESSION RESOURCE SETUP REQUEST message, the NG-RAN node may consider it for the DRB allocation process. It is up to NG-RAN node implementation to decide whether and how to use it. + +For each PDU session in the PDU SESSION RESOURCE SETUP REQUEST message, if the *Alternative QoS Parameters Set List* IE is included in the *GBR QoS Flow Information* IE in the *PDU Session Resource Setup Request Transfer* IE of the PDU SESSION RESOURCE SETUP REQUEST message, the NG-RAN node may accept the setup of the QoS flow when notification control has been enabled if the requested QoS parameters or at least one of the alternative QoS parameters sets can be fulfilled at the time of setup. In case the NG-RAN node accepts the setup fulfilling one of the alternative QoS parameters it shall indicate the alternative QoS parameters set which it currently fulfils in the *Current QoS Parameters Set Index* IE within the *PDU Session Resource Setup Response Transfer* IE of the PDU SESSION RESOURCE SETUP RESPONSE message. + +For each QoS flow which has been successfully established, the NG-RAN node shall, if supported, store the *Redundant QoS Flow Indicator* IE if included in the *PDU Session Resource Setup Request Transfer* IE contained in the PDU SESSION RESOURCE SETUP REQUEST message and consider it for the redundant transmission as specified in TS 23.501 [9]. + +For each QoS flow which has been successfully established, if the *QoS Monitoring Request* IE was included in the *QoS Flow Level QoS Parameters* IE contained in the PDU SESSION RESOURCE SETUP REQUEST message, the NG-RAN node shall store this information, and, if supported, perform delay measurement and QoS monitoring, as specified in TS 23.501 [9]. If the *QoS Monitoring Reporting Frequency* IE was included in the *QoS Flow Level QoS Parameters* + +IE contained in the PDU SESSION RESOURCE SETUP REQUEST message, the NG-RAN node shall store this information and, if supported, use it for RAN part delay reporting. + +For each QoS flow requested to be setup, if the *PDU Set QoS Parameters* IE is included in the *QoS Flow Level QoS Parameters* IE contained in the PDU SESSION RESOURCE SETUP REQUEST message, the NG-RAN node shall, if supported, store the received PDU Set QoS Parameters in the UE context and use it as specified in TS 23.501 [9]. If the *ECN Marking or Congestion Information Reporting Request* IE is included in the *PDU Session Resource Setup Request Transfer* IE contained in the PDU SESSION RESOURCE SETUP REQUEST message, the NG-RAN node shall, if supported, use it accordingly for the specific QoS flow. If the *ECN Marking or Congestion Information Reporting Status* IE is included in the *PDU Session Resource Setup Response Transfer* IE as described in TS 23.501 [9], the AMF shall, if supported, use it to deduce if ECN marking at NG-RAN or ECN marking at UPF or congestion information reporting is active or not active. + +For each QoS flow requested to be setup the NG-RAN node shall take into account the received *QoS Flow Level QoS Parameters* IE. For each QoS flow the NG-RAN node shall establish or modify the resources according to the values of the *Allocation and Retention Priority* IE (priority level and pre-emption indicators) and the resource situation as follows: + +- The NG-RAN node shall consider the priority level of the requested QoS flow, when deciding on the resource allocation. +- The priority levels and the pre-emption indicators may (individually or in combination) be used to determine whether the QoS flow setup has to be performed unconditionally and immediately. If the requested QoS flow is marked as "may trigger pre-emption" and the resource situation requires so, the NG-RAN node may trigger the pre-emption procedure which may then cause the forced release of a lower priority QoS flow which is marked as "pre-emptable". Whilst the process and the extent of the pre-emption procedure are operator-dependent, the pre-emption indicators shall be treated as follows: + 1. The values of the last received *Pre-emption Vulnerability* IE and *Priority Level* IE shall prevail. + 2. If the *Pre-emption Capability* IE is set to "may trigger pre-emption", then this allocation request may trigger the pre-emption procedure. + 3. If the *Pre-emption Capability* IE is set to "shall not trigger pre-emption", then this allocation request shall not trigger the pre-emption procedure. + 4. If the *Pre-emption Vulnerability* IE is set to "pre-emptable", then this QoS flow shall be included in the pre-emption process. + 5. If the *Pre-emption Vulnerability* IE is set to "not pre-emptable", then this QoS flow shall not be included in the pre-emption process. +- The NG-RAN node pre-emption process shall keep the following rules: + 1. The NG-RAN node shall only pre-empt QoS flows with lower priority, in ascending order of priority. + 2. The pre-emption may be done for QoS flows belonging to the same UE or to other UEs. + +For each QoS flow which has been successfully established, the NG-RAN node shall store the mapped E-RAB ID if included in the *PDU Session Resource Setup Request Transfer* IE contained in the PDU SESSION RESOURCE SETUP REQUEST message and use it as specified in TS 38.300 [8]. + +For each PDU session, if the *Redundant PDU Session Information* IE is included in the *PDU Session Resource Setup Request Transfer* IE contained in the PDU SESSION RESOURCE SETUP REQUEST message, the NG-RAN node shall, if supported, store the received information in the UE context and setup the redundant user plane for the redundant PDU session as specified in TS38.300 [8] and TS 23.501 [9]. If the *PDU Session Type* IE is set to "ethernet" and the redundancy requirement is fulfilled using a secondary NG-RAN node, the NG-RAN node shall, if supported, include the *Global RAN Node ID of Secondary NG-RAN Node* IE in the *PDU Session Resource Setup Response* + +*Transfer* IE of the PDU SESSION RESOURCE SETUP RESPONSE message. If the *PDU Session Pair ID* IE is included in the *Redundant PDU Session Information* IE, the NG-RAN node may use it to identify the paired PDU sessions. + +The NG-RAN node shall report to the AMF in the PDU SESSION RESOURCE SETUP RESPONSE message the result for each PDU session resource requested to be setup: + +- For each PDU session resource successfully setup, the *PDU Session Resource Setup Response Transfer* IE shall be included containing: + 1. The NG-U UP transport layer information to be used for the PDU session and associated list of QoS flows which have been successfully established, in the *QoS Flow per TNL Information* IE. + 2. The list of QoS flows which failed to be established, if any, in the *QoS Flow Failed to Setup List* IE. When the NG-RAN node reports unsuccessful establishment of a QoS flow, the cause value should be precise enough to enable the SMF to know the reason for the unsuccessful establishment. +- For each PDU session resource which failed to be setup, the *PDU Session Resource Setup Unsuccessful Transfer* IE shall be included containing a cause value that should be precise enough to enable the SMF to know the reason for the unsuccessful establishment. + +Upon reception of the PDU SESSION RESOURCE SETUP RESPONSE message the AMF shall, for each PDU session indicated in the *PDU Session ID* IE, transfer transparently the *PDU Session Resource Setup Response Transfer* IE or *PDU Session Resource Setup Unsuccessful Transfer* IE to the SMF associated with the concerned PDU session. + +Upon reception of the PDU SESSION RESOURCE SETUP REQUEST message to setup a QoS flow for IMS voice, if the NG-RAN node is not able to support IMS voice, the NG-RAN node shall initiate EPS fallback or RAT fallback for IMS voice procedure as specified in TS 23.501 [9] and report unsuccessful establishment of the QoS flow in the *PDU Session Resource Setup Response Transfer* IE or in the *PDU Session Resource Setup Unsuccessful Transfer* IE with cause value "IMS voice EPS fallback or RAT fallback triggered". + +For each PDU session for which the *Global RAN Node ID of Secondary NG-RAN Node* IE is included in the *PDU Session Resource Setup Response Transfer* IE of the PDU SESSION RESOURCE SETUP RESPONSE message, the SMF shall, if supported, handle this information as specified in TS 23.501 [9]. + +The *UE Aggregate Maximum Bit Rate* IE should be sent to the NG-RAN node if the AMF has not sent it previously. If it is included in the PDU SESSION RESOURCE SETUP REQUEST message, the NG-RAN node shall store the UE Aggregate Maximum Bit Rate in the UE context, and use the received UE Aggregate Maximum Bit Rate for all Non-GBR QoS flows for the concerned UE as specified in TS 23.501 [9]. + +For each PDU session, if the *PDU Session Expected UE Activity Behaviour* IE is included in the PDU SESSION RESOURCE SETUP REQUEST message, the NG-RAN node shall, if supported, handle this information as specified in TS 23.501 [9]. + +If the *UE Slice Maximum Bit Rate List* IE is included in the PDU SESSION RESOURCE SETUP REQUEST message, the NG-RAN node shall, if supported, store the UE Slice Maximum Bit Rate List in the UE context, and use it for each S-NSSAI for the concerned UE as specified in TS 23.501 [9]. + +The NG-RAN node shall, if supported, report in the PDU SESSION RESOURCE SETUP RESPONSE message location information of the UE in the *User Location Information* IE. + +If the *User Location Information* IE is included in the PDU SESSION RESOURCE SETUP RESPONSE message, the AMF shall handle this information as specified in TS 23.501 [9]. + +For each PDU session, if the *Downlink TL Container* IE is included in the *PDU Session Resource Setup Request Transfer* IE of the PDU SESSION RESOURCE SETUP REQUEST message, the NG-RAN node shall, if supported, handle it as specified in TS 23.501 [9] and shall include the *Uplink TL Container* IE in the *PDU Session Resource Setup Response Transfer* IE as specified in TS 23.501 [9]. + +If the *PDU Set QoS Parameters* IE is included in the PDU SESSION RESOURCE SETUP REQUEST message, the NG-RAN node shall, if supported, report in the PDU SESSION RESOURCE SETUP RESPONSE message the *PDU Set based Handling Indicator* IE in the *PDU Session Resource Setup Response Transfer* IE. If the *PDU Set based Handling Indicator* IE is included in the *PDU Session Resource Setup Response Transfer* IE in the PDU SESSION RESOURCE SETUP RESPONSE message, the SMF shall, if supported, handle this information as specified in TS 23.501 [9]. + +#### **Interactions with Handover Preparation procedure:** + +If a handover becomes necessary during the PDU Session Resource Setup procedure, the NG-RAN node may interrupt the ongoing PDU Session Resource Setup procedure and initiate the Handover Preparation procedure as follows: + +1. The NG-RAN node shall send the PDU SESSION RESOURCE SETUP RESPONSE message in which the NG-RAN node shall indicate, if necessary, all the PDU session resources which failed to be setup with an appropriate cause value, e.g. "NG intra-system handover triggered", "NG inter-system handover triggered" or "Xn handover triggered". +2. The NG-RAN node shall trigger the handover procedure. + +### **8.2.1.3 Unsuccessful Operation** + +The unsuccessful operation is specified in the successful operation section. + +### **8.2.1.4 Abnormal Conditions** + +If the NG-RAN node receives a PDU SESSION RESOURCE SETUP REQUEST message containing several *PDU Session ID* IEs (in the *PDU Session Resource Setup Request List* IE) set to the same value, the NG-RAN node shall report the establishment of the corresponding PDU sessions as failed in the PDU SESSION RESOURCE SETUP RESPONSE message with an appropriate cause value. + +If the NG-RAN node receives a PDU SESSION RESOURCE SETUP REQUEST message containing a *PDU Session ID* IE (in the *PDU Session Resource Setup Request List* IE) set to a value that identifies an active PDU session (established before the PDU SESSION RESOURCE SETUP REQUEST message was received), the NG-RAN node shall report the establishment of the new PDU session as failed in the PDU SESSION RESOURCE SETUP RESPONSE message with an appropriate cause value. + +If the NG-RAN node receives a PDU SESSION RESOURCE SETUP REQUEST message containing a *QoS Flow Setup Request List* IE in the *PDU Session Resource Setup Request Transfer* IE including at least one Non-GBR QoS flow but the *PDU Session Aggregate Maximum Bit Rate* IE is not present, the NG-RAN node shall report the establishment of the corresponding PDU session as failed in the PDU SESSION RESOURCE SETUP REQUEST message with an appropriate cause value. + +If the NG-RAN node receives a PDU SESSION RESOURCE SETUP REQUEST message containing a *QoS Flow Level QoS Parameters* IE in the *PDU Session Resource Setup Request Transfer* IE for a GBR QoS flow but the *GBR QoS Flow Information* IE is not present, the NG-RAN node shall report the establishment of the corresponding QoS flow as failed in the *PDU Session Resource Setup Response Transfer* IE of the PDU SESSION RESOURCE SETUP RESPONSE message with an appropriate cause value. If the NG-RAN node receives a PDU SESSION RESOURCE SETUP REQUEST message containing the *Delay Critical* IE in the *Dynamic 5QI Descriptor* IE of the *QoS Flow Level QoS Parameters* IE of the *PDU Session Resource Setup Request Transfer* IE set to the value "delay critical" but the *Maximum Data Burst Volume* IE is not present, the NG-RAN node shall report the establishment of the corresponding QoS flow as failed in the *PDU Session Resource Setup Response Transfer* IE of the PDU SESSION RESOURCE SETUP RESPONSE message with an appropriate cause value. + +## 8.2.2 PDU Session Resource Release + +### 8.2.2.1 General + +The purpose of the PDU Session Resource Release procedure is to enable the release of already established PDU session resources for a given UE. The procedure uses UE-associated signalling. + +### 8.2.2.2 Successful Operation + +![Sequence diagram showing the successful operation of PDU session resource release. The AMF sends a PDU SESSION RESOURCE RELEASE COMMAND to the NG-RAN node, and the NG-RAN node responds with a PDU SESSION RESOURCE RELEASE RESPONSE.](458fdbcb4015a4ee90bd84809afc4aac_img.jpg) + +``` +sequenceDiagram + participant AMF + participant NG-RAN node + Note left of NG-RAN node: + AMF->>NG-RAN node: PDU SESSION RESOURCE RELEASE COMMAND + NG-RAN node-->>AMF: PDU SESSION RESOURCE RELEASE RESPONSE + Note right of AMF: +``` + +Sequence diagram showing the successful operation of PDU session resource release. The AMF sends a PDU SESSION RESOURCE RELEASE COMMAND to the NG-RAN node, and the NG-RAN node responds with a PDU SESSION RESOURCE RELEASE RESPONSE. + +**Figure 8.2.2.2-1: PDU session resource release: successful operation** + +The AMF initiates the procedure by sending a PDU SESSION RESOURCE RELEASE COMMAND message. + +The PDU SESSION RESOURCE RELEASE COMMAND message shall contain the information required by the NG-RAN node to release at least one PDU session resource, and include each PDU session resource to release in the *PDU Session Resource to Release List* IE. + +If a *NAS-PDU* IE is contained in the PDU SESSION RESOURCE RELEASE COMMAND message, the NG-RAN node shall pass it to the UE. + +Upon reception of the PDU SESSION RESOURCE RELEASE COMMAND message the NG-RAN node shall execute the release of the requested PDU sessions. For each PDU session to be released the NG-RAN node shall release the corresponding resources over Uu and over NG, if any. + +If the *RAN Paging Priority* IE is included in the PDU SESSION RESOURCE RELEASE COMMAND message, the NG-RAN node may use it to determine a priority for paging the UE in RRC\_INACTIVE state. + +The NG-RAN node shall, if supported, report in the PDU SESSION RESOURCE RELEASE RESPONSE message location information of the UE in the *User Location Information* IE. + +After sending a PDU SESSION RESOURCE RELEASE RESPONSE message, the NG-RAN node shall be prepared to receive a PDU SESSION RESOURCE SETUP REQUEST message requesting establishment of a PDU session with a PDU Session ID corresponding to one of the PDU Session IDs that was present in the *PDU Session Resource to Release List* IE of the PDU SESSION RESOURCE RELEASE COMMAND message. + +If the *User Location Information* IE is included in the PDU SESSION RESOURCE RELEASE RESPONSE message, the AMF shall handle this information as specified in TS 23.501 [9]. + +For each PDU session for which the *Secondary RAT Usage Information* IE is included in the *PDU Session Resource Release Response Transfer* IE, the SMF shall handle this information as specified in TS 23.502 [10]. + +For each PDU session, if the *Downlink TL Container* IE for a QoS flow is included in the *PDU Session Resource Release Command Transfer* IE of the PDU SESSION RESOURCE RELEASE COMMAND message, the NG-RAN node shall, if supported, handle it as specified in TS 23.501 [9] and shall include the *Uplink TL Container* IE for the indicated QoS flow in the *PDU Session Resource Release Response Transfer* IE as specified in TS 23.501 [9]. + +### 8.2.2.3 Unsuccessful Operation + +The unsuccessful operation is specified in the successful operation section. + +### 8.2.2.4 Abnormal Conditions + +If the NG-RAN node receives a PDU SESSION RESOURCE RELEASE COMMAND message containing multiple *PDU Session ID* IEs (in the *PDU Session Resource to Release List* IE) set to the same value, the NG-RAN node shall initiate the release of one corresponding PDU session and ignore the duplication of the instances of the selected corresponding PDU sessions. + +## 8.2.3 PDU Session Resource Modify + +### 8.2.3.1 General + +The purpose of the PDU Session Resource Modify procedure is to enable configuration modifications of already established PDU session(s) for a given UE. It is also to enable the setup, modification and release of the QoS flow for already established PDU session(s). The procedure uses UE-associated signalling. + +### 8.2.3.2 Successful Operation + +![Sequence diagram showing the successful operation of PDU session resource modify. The AMF sends a PDU SESSION RESOURCE MODIFY REQUEST message to the NG-RAN node, and the NG-RAN node responds with a PDU SESSION RESOURCE MODIFY RESPONSE message.](62ee64afa2d368d732de66628cf2c841_img.jpg) + +``` +sequenceDiagram + participant AMF + participant NG-RAN node + Note left of NG-RAN node: + AMF->>NG-RAN node: PDU SESSION RESOURCE MODIFY REQUEST + NG-RAN node-->>AMF: PDU SESSION RESOURCE MODIFY RESPONSE + Note right of AMF: +``` + +Sequence diagram showing the successful operation of PDU session resource modify. The AMF sends a PDU SESSION RESOURCE MODIFY REQUEST message to the NG-RAN node, and the NG-RAN node responds with a PDU SESSION RESOURCE MODIFY RESPONSE message. + +**Figure 8.2.3.2-1: PDU session resource modify: successful operation** + +The AMF initiates the procedure by sending a PDU SESSION RESOURCE MODIFY REQUEST message to the NG-RAN node. + +The PDU SESSION RESOURCE MODIFY REQUEST message shall contain the information required by the NG-RAN node, which may trigger the NG-RAN configuration modification for the existing PDU sessions listed in the *PDU Session Resource Modify Request List* IE. + +Upon reception of the PDU SESSION RESOURCE MODIFY REQUEST message, if the NG-RAN configuration is triggered to be modified and if resources are available for the modified NG-RAN configuration, the NG-RAN node shall execute the configuration modification for the requested PDU session. + +If the *RAN Paging Priority* IE is included in the PDU SESSION RESOURCE MODIFY REQUEST message, the NG-RAN node may use it to determine a priority for paging the UE in RRC\_INACTIVE state. + +For each PDU session, if the *S-NSSAI* IE is included in the *PDU Session Resource Modify Request Item* IE contained in the PDU SESSION RESOURCE MODIFY REQUEST message, the NG-RAN node shall replace the previously provided S-NSSAI by the received S-NSSAI for the concerned PDU session and use it as specified in TS 23.502 [10]. + +For each PDU session, if the *Network Instance* IE is included in the *PDU Session Resource Modify Request Transfer* IE contained in the PDU SESSION RESOURCE MODIFY REQUEST message and the *Common Network Instance* IE is not present, the NG-RAN node shall, if supported, use it as specified in TS 23.501 [9]. + +For each PDU session, if the *Common Network Instance* IE is included in the *PDU Session Resource Modify Request Transfer* IE or in the *Additional UL NG-U UP TNL Information* IE, or in the *Additional Redundant UL NG-U UP TNL Information* IE contained in the PDU SESSION RESOURCE MODIFY REQUEST message, the NG-RAN node shall, if supported, use it when selecting transport network resource for the concerned NG-U transport bearer as specified in TS 23.501 [9]. + +For each PDU session, if the *Redundant Common Network Instance* IE is included in the *PDU Session Resource Modify Request Transfer* IE contained in the PDU SESSION RESOURCE MODIFY REQUEST message, the NG-RAN node shall, if supported, use it for the redundant transmission as specified in TS 23.501 [9]. + +For each PDU session, if the *TSC Traffic Characteristics* IE is included in the *PDU Session Resource Modify Request Transfer* IE contained in the PDU SESSION RESOURCE MODIFY REQUEST message, the NG-RAN node shall, if supported, store it and use it as specified in TS 23.501 [9]. If the *RAN Feedback Type* IE is included in the *TSC Traffic Characteristics* IE, the NG-RAN node shall, if supported, take this information into account when determining the feedback to provide in the *TSC Traffic Characteristics Feedback* IE in the *PDU Session Resource Modify Response Transfer* IE in the PDU SESSION RESOURCE MODIFY RESPONSE message as specified in TS 23.501 [9]. + +For each PDU session, if the *Redundant QoS Flow Indicator* IE is included and set to “false” for all QoS flows, the NG-RAN node shall, if supported, stop the redundant transmission and release the redundant tunnel for the concerned PDU session as specified in TS 23.501 [9]. + +For each PDU session, if the *Downlink TL Container* IE for a QoS flow is included in the *PDU Session Resource Modify Request Transfer* IE contained in the PDU SESSION RESOURCE MODIFY REQUEST message, the NG-RAN node shall, if supported, handle it as specified in TS 23.501 [9] and shall include the *Uplink TL Container* IE for the indicated QoS flow in the *PDU Session Resource Modify Response Transfer* IE as specified in TS 23.501 [9]. + +For each PDU session in the PDU SESSION RESOURCE MODIFY REQUEST message, if the *Alternative QoS Parameters Set List* IE is included in the *GBR QoS Flow Information* IE in the *PDU Session Resource Modify Request Transfer* IE of the PDU SESSION RESOURCE MODIFY REQUEST message, the NG-RAN node may accept the setup of the QoS flow when notification control has been enabled if the requested QoS parameters or at least one of the alternative QoS parameters sets can be fulfilled at the time of setup. In case the NG-RAN node accepts the setup fulfilling one of the alternative QoS parameters it shall indicate the alternative QoS parameters set which it currently fulfils in the *Current QoS Parameters Set Index* IE within the *PDU Session Resource Setup Response Transfer* IE of the PDU SESSION RESOURCE MODIFY RESPONSE message. + +For each PDU session included in the *PDU Session Resource Modify Request List* IE: + +- For each QoS flow included in the *QoS Flow Add or Modify Request List* IE, based on the *QoS Flow Level QoS Parameters* IE, the NG-RAN node may establish, modify or release the DRB configuration and may change allocation of resources on NG or Uu accordingly. The NG-RAN node shall associate each QoS flow accepted to setup or modify which is not associated with an MBS QoS flow with a DRB of the PDU session. The associated DRB for the QoS flow accepted to modify may not change. If the *PDU Set QoS Parameters* IE is received, the NG-RAN node shall, if supported, store the received PDU Set QoS Parameters in the UE context and use it as specified in TS 23.501 [9]. If the *ECN Marking or Congestion Information Reporting Request* IE is included in the *PDU Session Resource Setup Request Transfer* IE contained in the PDU SESSION RESOURCE SETUP REQUEST message, the NG-RAN node shall, if supported, use it accordingly for the specific QoS flow. If the *ECN Marking or Congestion Information Reporting Status* IE is included in the *PDU Session Resource Modify Response Transfer* IE as described in TS 23.501 [9], the AMF shall, if supported, use it to deduce if ECN marking at NG-RAN or ECN marking at UPF or congestion information reporting is active or not active. +- For each QoS flow, if the *Redundant QoS Flow Indicator* IE is included, the NG-RAN node shall, if supported, store it and consider it for the redundant transmission as specified in TS 23.501 [9]. +- For each QoS flow included in the *QoS Flow Add or Modify Request List* IE, if the *QoS Flow Add or Modify Request Item* IE is included for an existing *QoS Flow Identifier* IE, the NG-RAN node shall overwrite the content of the full *QoS Flow Add or Modify Request Item* IE. + +- For each QoS flow included in the *QoS Flow to Release List* IE, the NG-RAN node shall de-associate the QoS flow with the previously associated DRB. +- For each QoS flow included in the *QoS Flow Add or Modify Request List* IE, if the *UL NG-U UP TNL Information* IE is included, the NG-RAN node shall, if supported, include the *DL NG-U UP TNL Information* IE in the *QoS Flow Add or Modify Response Item* IE for the QoS flow within the PDU SESSION RESOURCE MODIFY RESPONSE message as specified in TS 23.501 [9]. +- For each QoS flow, if the *Burst Arrival Time* IE is included in the *TSC Assistance Information Uplink* IE of the *TSC Traffic Characteristics* IE, the NG-RAN node may include the *AN Packet Delay Budget Uplink* IE for the same QoS flow within the PDU SESSION RESOURCE MODIFY RESPONSE message as specified in TS 23.501 [9]. +- If the *NAS-PDU* IE is received for the PDU session, the NG-RAN node shall pass it to the UE only if at least one of the requests included in the *PDU Session Resource Modify Request Transfer* IE is successful (i.e. the PDU session is included in the *PDU Session Resource Modify Response Item* IE of the PDU SESSION RESOURCE MODIFY RESPONSE message). +- The NG-RAN node may change allocation of resources on NG according to the requested target configuration. +- If the *PDU Session Aggregate Maximum Bit Rate* IE is included in the *PDU Session Resource Modify Request Transfer* IE, the NG-RAN node shall store and use the received PDU Session Aggregate Maximum Bit Rate value when enforcing traffic policing for Non-GBR QoS flows for the concerned UE as specified in TS 23.501 [9]. +- If the *UL NG-U UP TNL Information* IE in the *UL NG-U UP TNL Modify List* IE is included in the *PDU Session Resource Modify Request Transfer* IE, the NG-RAN node shall update the transport layer information for the uplink data accordingly for the concerned transport bearers identified by the *DL NG-U UP TNL Information* IE included in the *PDU Session Resource Modify Request Transfer* IE for the concerned PDU session. +- If the *Additional UL NG-U UP TNL Information* IE is included in the *PDU Session Resource Modify Request Transfer* IE, the NG-RAN node may allocate resources for an additional NG-U transport bearer for some or all of the QoS flows present in the *QoS Flow Add or Modify Request List* IE and it shall indicate these QoS flows in the *Additional DL QoS Flow per TNL Information* IE in the *PDU Session Resource Modify Response Transfer* IE. In case the *Additional DL QoS Flow per TNL Information* IE is not included the SMF shall consider the proposed additional UL NG-U UP TNL information as available again. +- In case more than one NG-U transport bearers have been set up for the PDU session, if all the QoS flows associated to one existing NG-U transport bearer are included in the *QoS Flow to Release List* IE in the *PDU Session Resource Modify Request Transfer* IE, the NG-RAN node and 5GC shall consider that the concerned NG-U transport bearer is removed for the PDU session, and both NG-RAN node and 5GC shall therefore consider the related NG-U UP TNL information as available again. +- If the *Redundant UL NG-U UP TNL Information* IE within the *UL NG-U UP TNL Modify List* IE is included in the *PDU Session Resource Modify Request Transfer* IE, the NG-RAN node shall, if supported, update the transport layer information for the uplink data accordingly for the concerned transport bearer identified by the *Redundant DL NG-U UP TNL Information* IE included in the *PDU Session Resource Modify Request Transfer* IE for the concerned PDU session. +- If the *Additional Redundant UL NG-U UP TNL Information* IE is included in the *PDU Session Resource Modify Request Transfer* IE, the NG-RAN node may allocate resources for an additional redundant NG-U transport bearer for some or all of the QoS flows present in the *QoS Flow Add or Modify Request List* IE and it shall, if supported, indicate these QoS flows in the *Additional Redundant DL QoS Flow per TNL Information* IE in the *PDU Session Resource Modify Response Transfer* IE. In case the *Additional Redundant DL QoS Flow per TNL Information* IE is not included the SMF shall consider the proposed additional Redundant UL NG-U UP TNL information as available again. + +- If the *Redundant UL NG-U UP TNL Information* IE is included in the *PDU Session Resource Modify Request Transfer* IE, the NG-RAN node may allocate resources for a redundant NG-U transport bearer for some or all of the QoS flows present in the *QoS Flow Add or Modify Request List* IE and it shall, if supported, indicate the corresponding NG-RAN endpoint of this NG-U transport bearer in the *Redundant DL NG-U UP TNL Information* IE in the *PDU Session Resource Modify Response Transfer* IE. +- If the *Security Indication* IE is included in the *PDU Session Resource Modify Request Transfer* IE, the NG-RAN node shall, if supported, only update the maximum integrity protected data rate uplink and/or the maximum integrity protected data rate downlink, and take them into account as defined in the PDU Session Resource Setup procedure. + +For each QoS flow which has been successfully added or modified, if the *QoS Monitoring Request* IE was included in the *QoS Flow Level QoS Parameters* IE contained in the PDU SESSION RESOURCE MODIFY REQUEST message, the NG-RAN node shall store this information, and, if supported, perform delay measurement and QoS monitoring, as specified in TS 23.501 [9]. If the *QoS Monitoring Reporting Frequency* IE was included in the *QoS Flow Level QoS Parameters* IE contained in the PDU SESSION RESOURCE MODIFY REQUEST message, the NG-RAN node shall store this information and, if supported, use it for RAN part delay reporting. + +The NG-RAN node shall report to the AMF, in the PDU SESSION RESOURCE MODIFY RESPONSE message, the result for each PDU session requested to be modified listed in the PDU SESSION RESOURCE MODIFY REQUEST message: + +- For each PDU session which is successfully modified, the *PDU Session Resource Modify Response Transfer* IE shall be included containing: + 1. The list of QoS flows which have been successfully setup or modified, if any, in the *QoS Flow Add or Modify Response List* IE in case the PDU Session Resource Modify procedure is triggered by QoS flow setup or modification. + 2. The list of QoS flows which have failed to be setup or modified, if any, in the *QoS Flow Failed to Add or Modify List* IE in case the PDU Session Resource Modify procedure is triggered by QoS flow setup or modification. +- For each PDU session which failed to be modified, the *PDU Session Resource Modify Unsuccessful Transfer* IE shall be included containing the failure cause. +- For each PDU session, if the *DL NG-U UP TNL Information* IE is included in the *PDU Session Resource Modify Response Transfer* IE in the PDU SESSION RESOURCE MODIFY RESPONSE message, it shall be considered by the SMF as the new DL transport layer address for the PDU session. The NG-RAN also may indicate the mapping between each new DL transport layer address and the corresponding UL transport layer address assigned by the 5GC. +- For each PDU session, if the *Additional NG-U UP TNL Information* IE is included in the *PDU Session Resource Modify Response Transfer* IE in the PDU SESSION RESOURCE MODIFY RESPONSE message, it shall, if supported, be considered by the SMF as the new DL transport layer address(es) for the PDU session. The NG-RAN also may indicate the mapping between each new DL transport layer address and the corresponding UL transport layer address assigned by the 5GC. +- For each PDU session, if the *Additional Redundant NG-U UP TNL Information* IE is included in the *PDU Session Resource Modify Response Transfer* IE in the PDU SESSION RESOURCE MODIFY RESPONSE message, it shall, if supported, be considered by the SMF as the new DL transport layer address(es) for the PDU session for the redundant transmission. The NG-RAN also may indicate the mapping between each new redundant DL transport layer address and the corresponding redundant UL transport layer address assigned by the 5GC. + +Upon reception of the PDU SESSION RESOURCE MODIFY RESPONSE message the AMF shall, for each PDU session indicated in the *PDU Session ID* IE, transfer transparently the *PDU Session Resource Modify Response* + +*Transfer IE* or *PDU Session Resource Modify Unsuccessful Transfer IE* to each SMF associated with the concerned PDU session. + +The NG-RAN node shall, if supported, report in the PDU SESSION RESOURCE MODIFY RESPONSE message location information of the UE in the *User Location Information IE*. + +For a PDU session or a QoS flow which failed to be modified, the NG-RAN node shall fall back to the configuration of the PDU session or the QoS flow as it was configured prior to the reception of the PDU SESSION RESOURCE MODIFY REQUEST message. + +Upon reception of the PDU SESSION RESOURCE MODIFY REQUEST message to setup a QoS flow for IMS voice, if the NG-RAN node is not able to support IMS voice, the NG-RAN node shall initiate EPS fallback or RAT fallback for IMS voice procedure as specified in TS 23.501 [9] and report unsuccessful establishment of the QoS flow in the *PDU Session Resource Modify Response Transfer IE* or in the *PDU Session Resource Modify Unsuccessful Transfer IE* with cause value "IMS voice EPS fallback or RAT fallback triggered". + +If the *User Location Information IE* is included in the PDU SESSION RESOURCE MODIFY RESPONSE message, the AMF shall handle this information as specified in TS 23.501 [9]. + +For each PDU session, if the *PDU Session Expected UE Activity Behaviour IE* is included in the PDU SESSION RESOURCE MODIFY REQUEST message, the NG-RAN node shall, if supported, handle this information as specified in TS 23.501 [9]. + +For each PDU session for which the *Secondary RAT Usage Information IE* is included in the *PDU Session Resource Modify Response Transfer IE*, the SMF shall handle this information as specified in TS 23.502 [10]. + +If the *PDU Set QoS Parameters IE* is included in the PDU SESSION RESOURCE MODIFY REQUEST message, the NG-RAN node shall, if supported, report in the PDU SESSION RESOURCE MODIFY RESPONSE message the *PDU Set based Handling Indicator IE* in the *PDU Session Resource Modify Response Transfer IE*. If the *PDU Set based Handling Indicator IE* is included in the *PDU Session Resource Modify Response Transfer IE* in the PDU SESSION RESOURCE MODIFY RESPONSE message, the SMF shall, if supported, handle this information as specified in TS 23.501 [9]. + +#### **Interactions with Handover Preparation procedure:** + +If a handover becomes necessary during the PDU Session Resource Modify procedure, the NG-RAN node may interrupt the ongoing PDU Session Resource Modify procedure and initiate the Handover Preparation procedure as follows: + +1. The NG-RAN node shall send the PDU SESSION RESOURCE MODIFY RESPONSE message in which the NG-RAN node shall indicate, if necessary, all the PDU sessions failed with an appropriate cause value, e.g. "NG intra-system handover triggered", "NG inter-system handover triggered" or "Xn handover triggered". +2. The NG-RAN node shall trigger the handover procedure. + +### **8.2.3.3 Unsuccessful Operation** + +The unsuccessful operation is specified in the successful operation section. + +### **8.2.3.4 Abnormal Conditions** + +If the NG-RAN node receives a PDU SESSION RESOURCE MODIFY REQUEST message containing several *PDU Session ID IEs* (in the *PDU Session Resource Modify Request List IE*) set to the same value, the NG-RAN node shall report the modification of the corresponding PDU sessions as failed in the PDU SESSION RESOURCE MODIFY RESPONSE message with an appropriate cause value. + +If the NG-RAN node receives a PDU SESSION RESOURCE MODIFY REQUEST message containing some *PDU Session ID* IEs (in the *PDU Session Resource Modify Request List* IE) that the NG-RAN node does not recognize, the NG-RAN node shall report the corresponding invalid PDU sessions as failed in the PDU SESSION RESOURCE MODIFY RESPONSE message with an appropriate cause value. + +If the NG-RAN node receives a PDU SESSION RESOURCE MODIFY REQUEST message containing a *QoS Flow Level QoS Parameters* IE in the *PDU Session Resource Modify Request Transfer* IE for a GBR QoS flow but the *GBR QoS Flow Information* IE is not present, the NG-RAN node shall report the addition or modification of the corresponding QoS flow as failed in the *PDU Session Resource Modify Response Transfer* IE of the PDU SESSION RESOURCE MODIFY RESPONSE message with an appropriate cause value. + +If the NG-RAN node receives a PDU SESSION RESOURCE MODIFY REQUEST message containing the *Delay Critical* IE in the *Dynamic 5QI Descriptor* IE of the *QoS Flow Level QoS Parameters* IE of the *PDU Session Resource Modify Request Transfer* IE set to the value “delay critical” but the *Maximum Data Burst Volume* IE is not present, the NG-RAN node shall report the addition or modification of the corresponding QoS flow as failed in the *PDU Session Resource Modify Response Transfer* IE of the PDU SESSION RESOURCE MODIFY RESPONSE message with an appropriate cause value. + +If the NG-RAN node receives a PDU SESSION RESOURCE MODIFY REQUEST message containing a PDU session in the *PDU Session Resource Modify Request List* IE with the same QoS flow included both in the *QoS Flow Add or Modify Request List* IE and the *QoS Flow to Release List* IE, the NG-RAN node shall report the corresponding QoS flow as failed in the *QoS Flow Failed to Add or Modify List* IE in the *PDU Session Resource Modify Response Transfer* IE of the PDU SESSION RESOURCE MODIFY RESPONSE message with an appropriate cause value if the PDU session is modified successfully. The NG-RAN node shall not release the QoS flow when the corresponding QoS flow already exists. + +## 8.2.4 PDU Session Resource Notify + +### 8.2.4.1 General + +The purpose of the PDU Session Resource Notify procedure is to notify that the already established QoS flow(s) or PDU session(s) for a given UE are released or not fulfilled anymore or fulfilled again by the NG-RAN node for which notification control is requested. It is also used to notify that the updated QoS parameters during the Path Switch Request procedure are not successfully accepted by the NG-RAN node. The procedure uses UE-associated signalling. + +### 8.2.4.2 Successful Operation + +![Sequence diagram showing the PDU session resource notify procedure. The NG-RAN node sends a PDU SESSION RESOURCE NOTIFY message to the AMF.](d4ed35f72863013455b8f015e0f2e47e_img.jpg) + +``` +sequenceDiagram + participant NG-RAN node + participant AMF + Note left of NG-RAN node: + NG-RAN node->>AMF: PDU SESSION RESOURCE NOTIFY + Note right of AMF: + Note left of NG-RAN node: + Note right of AMF: +``` + +Sequence diagram showing the PDU session resource notify procedure. The NG-RAN node sends a PDU SESSION RESOURCE NOTIFY message to the AMF. + +Figure 8.2.4.2-1: PDU session resource notify + +The NG-RAN node initiates the procedure by sending a PDU SESSION RESOURCE NOTIFY message. + +The PDU SESSION RESOURCE NOTIFY message shall contain the information of PDU session resources or QoS flows which are released or not fulfilled anymore or fulfilled again by the NG-RAN node. + +- For each PDU session for which some QoS flows are released or not fulfilled anymore or fulfilled again by the NG-RAN node, the *PDU Session Resource Notify Transfer* IE shall be included containing: + 1. The list of QoS flows which are released by the NG-RAN node, if any, in the *QoS Flow Released List* IE. + 2. The list of GBR QoS flows which are not fulfilled anymore or fulfilled again by the NG-RAN node, if any, in the *QoS Flow Notify List* IE together with the *Notification Cause* IE. For a QoS flow indicated as not fulfilled anymore the NG-RAN node may also indicate an alternative QoS parameters set which it can currently fulfil in the *Current QoS Parameters Set Index* IE. For a QoS flow indicated as not fulfilled anymore the NG-RAN node may also indicate the RAN feedback in the *TSC Traffic Characteristics Feedback* IE. + 3. The list of QoS flows for which the QoS parameters were updated but could not be successfully accepted by the NG-RAN node during the Path Switch Request procedure, if any, in the *QoS Flow Feedback List* IE which may be associated with a value it could offer. +- For each PDU session resource which is released by the NG-RAN node, the *PDU Session Resource Notify Released Transfer* IE shall be included containing the release cause in the *Cause* IE. + +The NG-RAN node shall, if supported, report in the PDU SESSION RESOURCE NOTIFY message location information of the UE in the *User Location Information* IE. + +Upon reception of the PDU SESSION RESOURCE NOTIFY message, the AMF shall, for each PDU session indicated in the *PDU Session ID* IE, transfer transparently the *PDU Session Resource Notify Transfer* IE or *PDU Session Resource Notify Released Transfer* IE to the SMF associated with the concerned PDU session. Upon reception of *PDU Session Resource Notify Transfer* IE, the SMF normally initiate the appropriate release or modify procedure on the core network side for the PDU session(s) or QoS flow(s) identified as not fulfilled anymore. + +For each PDU session for which the *Secondary RAT Usage Information* IE is included in the *PDU Session Resource Notify Transfer* IE or the *PDU Session Resource Notify Released Transfer* IE, the SMF shall handle this information as specified in TS 23.502 [10]. + +If the *User Location Information* IE is included in the PDU SESSION RESOURCE NOTIFY message, the AMF shall handle this information as specified in TS 23.501 [9]. + +#### 8.2.4.3 Abnormal Conditions + +Void. + +### 8.2.5 PDU Session Resource Modify Indication + +#### 8.2.5.1 General + +The purpose of the PDU Session Resource Modify Indication procedure is for the NG-RAN node to request modification of the established PDU session(s). The procedure uses UE-associated signalling. + +## 8.2.5.2 Successful Operation + +![Sequence diagram showing the successful operation of PDU session resource modify indication. The NG-RAN node sends a PDU SESSION RESOURCE MODIFY INDICATION message to the AMF, and the AMF responds with a PDU SESSION RESOURCE MODIFY CONFIRM message.](50ef8602c7c9edd2da0e2133e772c2a2_img.jpg) + +``` + +sequenceDiagram + participant NG-RAN node + participant AMF + Note left of NG-RAN node: + NG-RAN node->>AMF: PDU SESSION RESOURCE MODIFY INDICATION + Note right of AMF: + AMF-->>NG-RAN node: PDU SESSION RESOURCE MODIFY CONFIRM + Note left of NG-RAN node: + +``` + +Sequence diagram showing the successful operation of PDU session resource modify indication. The NG-RAN node sends a PDU SESSION RESOURCE MODIFY INDICATION message to the AMF, and the AMF responds with a PDU SESSION RESOURCE MODIFY CONFIRM message. + +**Figure 8.2.5.2-1: PDU session resource modify indication: successful operation** + +The NG-RAN node initiates the procedure by sending a PDU SESSION RESOURCE MODIFY INDICATION message. Upon reception of the PDU SESSION RESOURCE MODIFY INDICATION message, the AMF shall, for each PDU session indicated in the *PDU Session ID* IE, transparently transfer the *PDU Session Resource Modify Indication Transfer* IE to the SMF associated with the concerned PDU session. + +For each PDU session for which the *DL QoS Flow per TNL Information* IE is included in the *PDU Session Resource Modify Indication Transfer* IE in the PDU SESSION RESOURCE MODIFY INDICATION message, the SMF shall, if the request is accepted, consider the included DL transport layer address as the DL transport layer address for the included associated QoS flows and provide the associated UL transport layer address in the *UL NG-U UP TNL Information* IE in the *PDU Session Resource Modify Confirm Transfer* IE in the PDU SESSION RESOURCE MODIFY CONFIRM message. + +For each PDU session for which the *Additional DL QoS Flow per TNL Information* IE is included in the *PDU Session Resource Modify Indication Transfer* IE in the PDU SESSION RESOURCE MODIFY INDICATION message, the SMF shall, if supported, consider for this split PDU session each included DL transport layer address(es) as the DL transport layer address(s) for the included associated QoS flows and it may provide the associated UL transport layer address(s) in the *Additional NG-U UP TNL Information* IE in the *PDU Session Resource Modify Confirm Transfer* IE in the PDU SESSION RESOURCE MODIFY CONFIRM message. + +In case more than one NG-U transport bearers have been set up for the PDU session, the *DL QoS Flow per TNL Information* IE and the *Additional DL QoS Flow per TNL Information* IE in the *PDU Session Resource Modify Indication Transfer* IE in the PDU SESSION RESOURCE MODIFY INDICATION message shall be included if at least one QoS flow is associated to their respective NG-U transport bearer; if no QoS flow is associated to one existing NG-U transport bearer after the modification, the NG-RAN node and 5GC shall consider that the concerned NG-U transport bearer is removed for the PDU session, and both NG-RAN node and 5GC shall therefore consider the related NG-U UP TNL information as available again. + +For each PDU session for which the *Redundant DL QoS Flow per TNL Information* IE is included in the *PDU Session Resource Modify Indication Transfer* IE in the PDU SESSION RESOURCE MODIFY INDICATION message, the SMF shall, if supported, consider the included DL transport layer address as the new DL transport layer address for the included associated QoS flows for redundant transmission and it may provide the associated UL transport layer address in the *Redundant UL NG-U UP TNL Information* IE in the *PDU Session Resource Modify Confirm Transfer* IE in the PDU SESSION RESOURCE MODIFY CONFIRM message. + +For each PDU session for which the *Additional Redundant DL QoS Flow per TNL Information* IE is included in the *PDU Session Resource Modify Indication Transfer* IE in the PDU SESSION RESOURCE MODIFY INDICATION message, the SMF shall, if supported, consider for this split PDU session each included DL transport layer address(es) as the new downlink termination point(s) for the included associated QoS flows and it may provide the associated UL transport layer address(s) in the *Additional Redundant NG-U UP TNL Information* IE in the *PDU Session Resource Modify Confirm Transfer* IE in the PDU SESSION RESOURCE MODIFY CONFIRM message for the redundant transmission. + +For each PDU session for which the *Global RAN Node ID of Secondary NG-RAN Node* IE is included in the *PDU Session Resource Modify Indication Transfer* IE of the PDU SESSION RESOURCE MODIFY INDICATION message, the SMF shall, if supported, handle this information as specified in TS 23.501 [9]. + +If the *Security Result* IE is included in the *PDU Session Resource Modify Indication Transfer* IE in the PDU SESSION RESOURCE MODIFY INDICATION message, it shall be considered by the SMF as the new security status of the PDU session. + +For each PDU session for which the *Secondary RAT Usage Information* IE is included in the *PDU Session Resource Modify Indication Transfer* IE, the SMF shall handle this information as specified in TS 23.502 [10]. + +The AMF shall report to the NG-RAN node in the PDU SESSION MODIFY RESOURCE CONFIRM message the result for each PDU session listed in PDU SESSION RESOURCE MODIFY INDICATION message: + +- For each PDU session which is successfully modified, the *PDU Session Resource Modify Confirm Transfer* IE shall be included containing: + 1. The list of QoS flows which have been successfully modified in the *QoS Flow Modify Confirm List* IE. + 2. The list of QoS flows which have failed to be modified, if any, in the *QoS Flow Failed to Modify List* IE. +- For each PDU session which failed to be modified, the *PDU Session Resource Modify Indication Unsuccessful Transfer* IE shall be included to report the failure cause. + +Upon reception of the *PDU Session Resource Modify Confirm Transfer* IE for each PDU session listed in the PDU SESSION RESOURCE MODIFY CONFIRM message: + +- If the *QoS Flow Failed To Modify List* IE is included, the NG-RAN node shall either + 1. de-associate the corresponding DRB for the concerned QoS flow, or + 2. keep the previous transport layer information before sending the PDU SESSION RESOURCE MODIFY INDICATION unchanged for the concerned QoS flow. + +Upon reception of the *PDU Session Resource Modify Indication Unsuccessful Transfer* IE for each PDU session listed in the PDU SESSION RESOURCE MODIFY CONFIRM message, the NG-RAN node shall either: + +1. release all corresponding NG-RAN configuration and resources for the concerned PDU session, or +2. keep the previous transport layer information before sending the PDU SESSION RESOURCE MODIFY INDICATION unchanged for the concerned PDU session. + +The NG-RAN node shall, if supported, report in the PDU SESSION RESOURCE MODIFY INDICATION message location information of the UE in the *User Location Information* IE. + +#### **Interactions with PDU Session Resource Setup procedure or PDU Session Resource Modification procedure:** + +If the PDU SESSION RESOURCE MODIFY INDICATION message is received by the AMF during an ongoing PDU Session Resource Setup procedure or an ongoing PDU Session Resource Modification procedure, the AMF shall proceed with the PDU Session Resource Modify Indication procedure. + +If the *PDU Session Resource Modify Indication Transfer* IE is received by the SMF during an ongoing PDU Session Resource Setup procedure or an ongoing PDU Session Resource Modification procedure, the SMF shall process the *PDU Session Resource Modify Indication Transfer* IE. + +### **8.2.5.3 Unsuccessful Operation** + +The unsuccessful operation is specified in the successful operation section. + +### 8.2.5.4 Abnormal Conditions + +Void. + +## 8.3 UE Context Management Procedures + +### 8.3.1 Initial Context Setup + +#### 8.3.1.1 General + +The purpose of the Initial Context Setup procedure is to establish the necessary overall initial UE context at the NG-RAN node, when required, including PDU session context, the Security Key, Mobility Restriction List, UE Radio Capability and UE Security Capabilities, etc. The AMF may initiate the Initial Context Setup procedure if a UE-associated logical NG-connection exists for the UE or if the AMF has received the *RAN UE NGAP ID* IE in an INITIAL UE MESSAGE message or if the NG-RAN node has already initiated a UE-associated logical NG-connection by sending an INITIAL UE MESSAGE message via another NG interface instance. The procedure uses UE-associated signalling. + +For signalling only connections and if the *UE Context Request* IE is not received in the Initial UE Message, the AMF may be configured to trigger the procedure for all NAS procedures or on a per NAS procedure basis depending on operator's configuration. + +#### 8.3.1.2 Successful Operation + +![Sequence diagram showing the successful operation of the Initial Context Setup procedure. The AMF sends an INITIAL CONTEXT SETUP REQUEST message to the NG-RAN node, and the NG-RAN node responds with an INITIAL CONTEXT SETUP RESPONSE message.](a4b868a176f7e0448ee72483727e9f6f_img.jpg) + +``` + +sequenceDiagram + participant AMF + participant NG-RAN node + Note left of NG-RAN node: + AMF->>NG-RAN node: INITIAL CONTEXT SETUP REQUEST + NG-RAN node-->>AMF: INITIAL CONTEXT SETUP RESPONSE + Note right of AMF: + +``` + +Sequence diagram showing the successful operation of the Initial Context Setup procedure. The AMF sends an INITIAL CONTEXT SETUP REQUEST message to the NG-RAN node, and the NG-RAN node responds with an INITIAL CONTEXT SETUP RESPONSE message. + +**Figure 8.3.1.2-1: Initial context setup: successful operation** + +In case of the establishment of a PDU session the 5GC shall be prepared to receive user data before the INITIAL CONTEXT SETUP RESPONSE message has been received by the AMF. If no UE-associated logical NG-connection exists, the UE-associated logical NG-connection shall be established at reception of the INITIAL CONTEXT SETUP REQUEST message. + +The INITIAL CONTEXT SETUP REQUEST message shall contain the *Index to RAT/Frequency Selection Priority* IE, if available in the AMF. + +If the *NAS-PDU* IE is included in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall pass it transparently towards the UE. + +If the *Masked IMEISV* IE is contained in the INITIAL CONTEXT SETUP REQUEST message the target NG-RAN node shall, if supported, use it to determine the characteristics of the UE for subsequent handling. + +Upon receipt of the INITIAL CONTEXT SETUP REQUEST message the NG-RAN node shall + +- attempt to execute the requested PDU session configuration; + +- store the received UE Aggregate Maximum Bit Rate in the UE context, and use the received UE Aggregate Maximum Bit Rate for Non-GBR QoS flows for the concerned UE as specified in TS 23.501 [9]; +- store the received Mobility Restriction List in the UE context; +- store the received UE Radio Capability in the UE context; +- store the received Index to RAT/Frequency Selection Priority in the UE context and use it as defined in TS 23.501 [9]; +- store the received UE Security Capabilities in the UE context; +- store the received Security Key in the UE context and, if the NG-RAN node is required to activate security for the UE, take this security key into use; +- if supported, store the received SRVCC Operation Possible in the UE context and use it as defined in TS 23.216 [31]; +- store the received NR V2X Services Authorization information, if supported, in the UE context; +- store the received LTE V2X Services Authorization information, if supported, in the UE context; +- store the received NR A2X Services Authorization information, if supported, in the UE context; +- store the received LTE A2X Services Authorization information, if supported, in the UE context; +- store the received NR UE Sidelink Aggregate Maximum Bit Rate, if supported, in the UE context, and use it for the concerned UE's sidelink communication in network scheduled mode for NR V2X services; +- store the received LTE UE Sidelink Aggregate Maximum Bit Rate, if supported, in the UE context, and use it for the concerned UE's sidelink communication in network scheduled mode for LTE V2X services; +- store the received NR A2X UE PC5 Aggregate Maximum Bit Rate, if supported, in the UE context, and use it for the concerned UE's sidelink communication in network scheduled mode for NR A2X services; +- store the received LTE A2X UE PC5 Aggregate Maximum Bit Rate, if supported, in the UE context, and use it for the concerned UE's sidelink communication in network scheduled mode for LTE A2X services; +- store the received PC5 QoS Parameters, if supported, in the UE context and use it as defined in TS 23.287 [33]; +- store the A2X PC5 QoS Parameters, if supported, in the UE context and use it as defined in TS 23.256 [54]. +- store the received Management Based MDT PLMN List information, if supported, in the UE context; +- if supported, store the received IAB Authorization information in the UE context, and use it accordingly for the IAB-MT; +- store the received 5G ProSe Authorization information in the UE context, if supported, and use it for the concerned UE's sidelink communication in network scheduled mode for 5G ProSe services; +- store the 5G ProSe UE PC5 Aggregate Maximum Bit Rate in the UE context, if supported, and use it for the concerned UE's sidelink communication in network scheduled mode for 5G ProSe services; +- store the 5G ProSe PC5 QoS Parameters, if supported, in the UE context and use it as defined in TS 23.304 [47]; +- store the received Network Controlled Repeater Authorization, if supported, in the UE context; +- if supported, store the received Mobile IAB Authorization information in the UE context, and use it accordingly for the mobile IAB-MT; + +- store the received PDU Set QoS parameters, if supported, in the UE context and use it as specified in TS 23.501 [9]. + +For the Initial Context Setup an initial value for the Next Hop Chaining Count is stored in the UE context. + +If the *PDU Session Resource Setup Request List* IE is contained in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall behave the same as defined in the PDU Session Resource Setup procedure. The NG-RAN node shall report to the AMF in the INITIAL CONTEXT SETUP RESPONSE message the result for each PDU session resource requested to be setup as defined in the PDU Session Resource Setup procedure. + +Upon reception of the INITIAL CONTEXT SETUP RESPONSE message the AMF shall, for each PDU session indicated in the *PDU Session ID* IE, transfer transparently the *PDU Session Resource Setup Response Transfer* IE or *PDU Session Resource Setup Unsuccessful Transfer* IE to the SMF associated with the concerned PDU session. In case the splitting PDU session is not used by the NG-RAN node, the SMF should remove the Additional Transport Layer Information, if any. + +The NG-RAN node shall use the information in the *Mobility Restriction List* IE if present in the INITIAL CONTEXT SETUP REQUEST message to + +- determine a target for subsequent mobility action for which the NG-RAN node provides information about the target of the mobility action towards the UE; +- select a proper SCG during dual connectivity operation; +- assign proper RNA(s) for the UE when moving the UE to RRC\_INACTIVE state. + +If the *Mobility Restriction List* IE is not contained in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall consider that no roaming and no access restriction apply to the UE except for the PNI NPN mobility as described in TS 23.501 [9]. The NG-RAN node shall also consider that no roaming and no access restriction apply to the UE when: + +- one of the QoS flows includes a particular ARP value (TS 23.501 [9]). + +The NG-RAN node shall consider that roaming or access to CAG cells is only allowed if the *Allowed PNI-NPN List* IE is contained in the INITIAL CONTEXT SETUP REQUEST message, as described in TS 23.501 [9]. + +If the *Trace Activation* IE is included in the INITIAL CONTEXT SETUP REQUEST message the NG-RAN node shall, if supported, initiate the requested trace function as described in TS 32.422 [11]. In particular, the NG-RAN node 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 [11]; +- if the *Trace Activation* IE includes the *MDT Activation* IE set to "Immediate MDT Only", "Logged MDT only", initiate the requested MDT session as described in TS 32.422 [11] and the NG-RAN node shall ignore the *Interfaces To Trace* IE and the *Trace Depth* IE; +- if the *Trace Activation* IE includes the *MDT Location Information* IE within the *MDT Configuration* IE, store this information and take it into account in the requested MDT session; +- if the *Trace Activation* IE includes the *Signalling Based MDT PLMN List* IE within the *MDT Configuration* IE, the NG-RAN node may use it to propagate the MDT Configuration as described in TS 37.320 [41]. +- if the *Trace Activation* IE includes the *Bluetooth Measurement Configuration* IE within the *MDT Configuration* IE, take it into account for MDT Configuration as described in TS 37.320 [41]. +- if the *Trace Activation* IE includes the *WLAN Measurement Configuration* IE within the *MDT Configuration* IE, take it into account for MDT Configuration as described in TS 37.320 [41]. + +- if the *Trace Activation* IE includes the *Sensor Measurement Configuration* IE within the *MDT Configuration* IE, take it into account for MDT Configuration as described in TS 37.320 [41]. +- if the *Trace Activation* IE includes the *MDT Configuration* IE and if the NG-RAN node is a gNB at least the *MDT Configuration-NR* IE shall be present, while if the NG-RAN node is an ng-eNB at least the *MDT Configuration-EUTRA* IE shall be present. + +If the *UE Security Capabilities* IE included in the INITIAL CONTEXT SETUP REQUEST message only contains the EIA0 or NIA0 algorithm as defined in TS 33.501 [13] and if the EIA0 or NIA0 algorithm is defined in the configured list of allowed integrity protection algorithms in the NG-RAN node (TS 33.501 [13]), the NG-RAN node shall take it into use and ignore the keys received in the *Security Key* IE. + +If the *QMC Configuration Information* IE is included in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall, if supported, use it for QoE management, as described in TS 38.300 [8]. If the *Assistance Information for QoE Measurement* IE is included in the *UE Application Layer Measurement Configuration Information* IE within the *QMC Configuration Information* IE, the NG-RAN node may take it into account for controlling the UE reporting when the NG-RAN node is overloaded, as described in TS 38.300 [8]. + +If the *Core Network Assistance Information for RRC INACTIVE* IE is included in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall, if supported, store this information in the UE context and use it for the RRC\_INACTIVE state decision and RNA configuration for the UE and RAN paging if any for a UE in RRC\_INACTIVE state, as specified in TS 38.300 [8]. If the *MICO All PLMN* IE is included in the *Core Network Assistance Information for RRC INACTIVE* IE the NG-RAN node shall, if supported, consider that the registration area for the UE is the full PLMN and ignore the *TAI List for RRC Inactive* IE. If the *Paging Cause Indication for Voice Service* IE is included in the *Core Network Assistance Information for RRC INACTIVE* IE, the NG-RAN node shall, if supported, store and use it as specified in 38.300 [8]. If the *PEIPS Assistance Information* IE is included in the *Core Network Assistance Information for RRC INACTIVE* IE, the NG-RAN node shall, if supported, store it and use it for paging subgrouping the UE in RRC\_INACTIVE state, as specified in TS 38.300 [8]. If the *CN MT Communication Handling* IE is included in the *Core Network Assistance Information for RRC INACTIVE* IE, the NG-RAN node shall, if supported, store it and may subsequently request, based on implementation, the CN for mobile terminated communication handling as described in TS 23.502 [10]. + +If the *CN Assisted RAN Parameters Tuning* IE is included in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node may use it as described in TS 23.501 [9]. + +If the *RRC Inactive Transition Report Request* IE is included in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall, if supported, store this information in the UE context. + +If the *Emergency Fallback Indicator* IE is included in the INITIAL CONTEXT SETUP REQUEST message, it indicates that the UE context to be set up is subject to emergency service fallback as described in TS 23.501 [9] and the NG-RAN node may, if supported, take the appropriate mobility actions. + +If the *Old AMF* IE is included in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall consider that this UE-associated logical NG-connection was redirected to this AMF from another AMF identified by the *Old AMF* IE. + +If the *Redirection for Voice EPS Fallback* IE is included in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall, if supported, store it and use it in a subsequent decision of EPS fallback for voice as specified in TS 23.502 [10]. + +If the *Location Reporting Request Type* IE is included in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node should perform the requested location reporting functionality for the UE as described in subclause 8.12. + +If the *Enhanced Coverage Restriction* IE is included in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall, if supported, store this information in the UE context and use it as defined in TS 23.501 [9]. + +If the *Extended Connected Time* IE is included in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall, if supported, use it as described in TS 23.501 [9]. + +If the *UE Differentiation Information* IE is included in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall, if supported, store this information in the UE context for further use according to TS 23.501 [9]. + +If the *CE-mode-B Restricted* IE is included in the INITIAL CONTEXT SETUP REQUEST message and the *Enhanced Coverage Restriction* IE is not set to "restricted" and the Enhanced Coverage Restriction information stored in the UE context is not set to "restricted", the NG-RAN node shall, if supported, store this information in the UE context and use it as defined in TS 23.501 [9]. + +If the *UE User Plane CIoT Support Indicator* IE is included in the INITIAL CONTEXT SETUP REQUEST message the NG-RAN node shall, if supported, store this information in the UE context and consider that User Plane CIoT 5GS Optimisation as specified in TS 23.501 [9] is supported for the UE. + +If the *Management Based MDT PLMN List* IE is contained in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall, if supported, use it to allow subsequent selection of the UE for management based MDT defined in TS 32.422 [11]. + +If the INITIAL CONTEXT SETUP REQUEST message contains the *UE Radio Capability ID* IE, the NG-RAN node shall, if supported, use it as specified in TS 23.501 [9] and TS 23.502 [10]. + +For each PDU session, if the *PDU Session Expected UE Activity Behaviour* IE is included in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall, if supported, handle this information as specified in TS 23.501 [9]. + +If the *Time Synchronisation Assistance Information* IE is included in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall, if supported, store the information in the UE context and use it as defined in TS 23.501 [9]. + +If the *Target NSSAI Information* IE is contained in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node may use this information as specified in TS 23.501 [9]. + +If the *Partially Allowed NSSAI* IE is contained in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall, if supported, deduce from it the partially allowed network slices for the UE, store and replace any previously received Partially Allowed NSSAI and use it as specified in TS 23.501 [9]. + +If the *UE Slice Maximum Bit Rate List* IE is included in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall, if supported, store the received UE Slice Maximum Bit Rate List in the UE context, and use it for each S-NSSAI for the concerned UE as specified in TS 23.501 [9]. + +If the *Aerial UE Subscription Information* IE is included in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall, if supported, store this information in the UE context and use it as defined in TS 38.300 [8]. + +If the *PNI-NPN Area Scope of MDT* IE is included in the *MDT Configuration-NR* IE included in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall, if supported, use it to derive the MDT area scope for MDT measurement collection in PNI-NPN areas. Upon reception of the *PNI-NPN Area Scope of MDT* IE, the NG-RAN node shall consider that the area scope for MDT measurement collection in PNI-NPN areas is defined only by the areas included in the *PNI-NPN Area Scope of MDT* IE. + +#### **Interactions with Initial UE Message procedure:** + +The NG-RAN node shall use the *AMF UE NGAP ID* IE and *RAN UE NGAP ID* IE received in the INITIAL CONTEXT SETUP REQUEST message as identification of the logical connection even if the *RAN UE NGAP ID* IE had been allocated in an INITIAL UE MESSAGE message sent over a different NG interface instance. + +#### **Interactions with RRC Inactive Transition Report procedure:** + +If the *RRC Inactive Transition Report Request* IE is included in the INITIAL CONTEXT SETUP REQUEST message and set to "subsequent state transition report", the NG-RAN node shall, if supported, send the RRC INACTIVE TRANSITION REPORT message to the AMF to report the RRC state of the UE when the UE enters or leaves RRC\_INACTIVE state. + +### 8.3.1.3 Unsuccessful Operation + +![Sequence diagram showing an unsuccessful initial context setup operation between an NG-RAN node and an AMF. The AMF sends an INITIAL CONTEXT SETUP REQUEST to the NG-RAN node, and the NG-RAN node responds with an INITIAL CONTEXT SETUP FAILURE.](bfca6639dd4b8480f2d96d2b61c806d9_img.jpg) + +``` + +sequenceDiagram + participant AMF + participant NG-RAN node + Note left of NG-RAN node: + AMF->>NG-RAN node: INITIAL CONTEXT SETUP REQUEST + NG-RAN node-->>AMF: INITIAL CONTEXT SETUP FAILURE + Note right of AMF: + +``` + +Sequence diagram showing an unsuccessful initial context setup operation between an NG-RAN node and an AMF. The AMF sends an INITIAL CONTEXT SETUP REQUEST to the NG-RAN node, and the NG-RAN node responds with an INITIAL CONTEXT SETUP FAILURE. + +Figure 8.3.1.3-1: Initial context setup: unsuccessful operation + +If the NG-RAN node is not able to establish an NG UE context, it shall consider the procedure as failed and reply with the INITIAL CONTEXT SETUP FAILURE message. + +If the *PDU Session Resource Setup Request List* IE is contained in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall report to the AMF, in the INITIAL CONTEXT SETUP FAILURE message, the unsuccessful establishment result for each PDU session resource requested to be setup as defined in the PDU Session Resource Setup procedure. + +Upon reception of the INITIAL CONTEXT SETUP FAILURE message the AMF shall, for each PDU session indicated in the *PDU Session ID* IE, transfer transparently the *PDU Session Resource Setup Unsuccessful Transfer* IE to the SMF associated with the concerned PDU session and may consider that the NAS PDU included in the INITIAL CONTEXT SETUP REQUEST message was not delivered. + +### 8.3.1.4 Abnormal Conditions + +If the supported algorithms for encryption defined in the *Encryption Algorithms* IE in the *UE Security Capabilities* IE, plus the mandated support of EEA0 and NEA0 in all UEs (TS 33.501 [13]), do not match any allowed algorithms defined in the configured list of allowed encryption algorithms in the NG-RAN node (TS 33.501 [13]), the NG-RAN node shall reject the procedure using the INITIAL CONTEXT SETUP FAILURE message. + +If the *Partially Allowed NSSAI* IE is received in the INITIAL CONTEXT SETUP REQUEST message and the total number of S-NSSAIs included in the Allowed NSSAI and Partially Allowed NSSAI exceeds eight, the NG-RAN node shall consider the procedure as failed. + +If any of the S-NSSAI which is present in the *Partially Allowed NSSAI* IE is also present in the *Allowed NSSAI* IE, the NG-RAN node shall consider the procedure as failed. + +If the supported algorithms for integrity defined in the *Integrity Protection Algorithms* IE in the *UE Security Capabilities* IE, plus the mandated support of the EIA0 and NIA0 algorithm in all UEs (TS 33.501 [13]), do not match any allowed algorithms defined in the configured list of allowed integrity protection algorithms in the NG-RAN node (TS 33.501 [13]), the NG-RAN node shall reject the procedure using the INITIAL CONTEXT SETUP FAILURE message. + +If both the *PNI-NPN Area Scope of MDT* IE and the *Area Scope of MDT* IE are included in the *MDT Configuration-NR* IE in the INITIAL CONTEXT SETUP REQUEST message, and the *Area Scope of MDT* IE is set to "PNI-NPN based", the NG-RAN node shall, if supported, use it to derive the MDT area scope for MDT measurement collection in PNI-NPN areas, and ignore the *PNI-NPN Area Scope of MDT* IE. + +## 8.3.2 UE Context Release Request (NG-RAN node initiated) + +### 8.3.2.1 General + +The purpose of the UE Context Release Request procedure is to enable the NG-RAN node to request the AMF to release the UE-associated logical NG-connection due to NG-RAN node generated reasons. The procedure uses UE-associated signalling. + +### 8.3.2.2 Successful Operation + +![Sequence diagram showing the UE context release request procedure. An NG-RAN node sends a UE CONTEXT RELEASE REQUEST message to an AMF.](23cb65390082ab306c15bd3d8196135e_img.jpg) + +``` +sequenceDiagram + participant NG-RAN node + participant AMF + Note left of NG-RAN node: + NG-RAN node->>AMF: UE CONTEXT RELEASE REQUEST + Note right of AMF: + Note right of AMF: +``` + +Sequence diagram showing the UE context release request procedure. An NG-RAN node sends a UE CONTEXT RELEASE REQUEST message to an AMF. + +**Figure 8.3.2.2-1: UE context release request** + +The NG-RAN node controlling a UE-associated logical NG-connection initiates the procedure by sending a UE CONTEXT RELEASE REQUEST message towards the affected AMF. + +The UE CONTEXT RELEASE REQUEST message shall indicate the appropriate cause value, e.g., "TXNRELOCOOverall Expiry", "Redirection", for the requested UE-associated logical NG-connection release. + +If the *PDU Session Resource List* IE is included in the UE CONTEXT RELEASE REQUEST message, the AMF shall handle this information as specified in TS 23.502 [10]. + +#### **Interactions with UE Context Release procedure:** + +The UE Context Release procedure should be initiated upon reception of a UE CONTEXT RELEASE REQUEST message with the release cause different than user inactivity. The UE Context Release procedure should be initiated upon reception of a UE CONTEXT RELEASE REQUEST message with release cause user inactivity and there is no downlink signaling, which refers to TS 23.502 [10]. If the UE was configured with DC radio resources at the time UE Context Release Request procedure was triggered, and the PSCell information was available, the NG-RAN node shall store the PSCell information in the UE context. + +### 8.3.2.3 Abnormal Conditions + +Void. + +## 8.3.3 UE Context Release (AMF initiated) + +### 8.3.3.1 General + +The purpose of the UE Context Release procedure is to enable the AMF to order the release of the UE-associated logical NG-connection due to various reasons, e.g., completion of a transaction between the UE and the 5GC, or release of the old UE-associated logical NG-connection when the UE has initiated the establishment of a new UE-associated logical NG-connection, etc. The procedure uses UE-associated signalling. + +### 8.3.3.2 Successful Operation + +![Sequence diagram for UE context release: successful operation. The diagram shows two lifelines: NG-RAN node and AMF. The AMF sends a UE CONTEXT RELEASE COMMAND message to the NG-RAN node. The NG-RAN node responds with a UE CONTEXT RELEASE COMPLETE message to the AMF.](a9159a006d67a834a7b1a771c18191cc_img.jpg) + +``` + +sequenceDiagram + participant AMF + participant NG-RAN node + Note left of NG-RAN node: + AMF->>NG-RAN node: UE CONTEXT RELEASE COMMAND + NG-RAN node-->>AMF: UE CONTEXT RELEASE COMPLETE + Note right of AMF: + +``` + +Sequence diagram for UE context release: successful operation. The diagram shows two lifelines: NG-RAN node and AMF. The AMF sends a UE CONTEXT RELEASE COMMAND message to the NG-RAN node. The NG-RAN node responds with a UE CONTEXT RELEASE COMPLETE message to the AMF. + +**Figure 8.3.3.2-1: UE context release: successful operation** + +The AMF initiates the procedure by sending the UE CONTEXT RELEASE COMMAND message to the NG-RAN node. + +The UE CONTEXT RELEASE COMMAND message shall contain both the AMF UE NGAP ID IE and the *RAN UE NGAP ID IE* if available, otherwise the message shall contain the *AMF UE NGAP ID IE*. + +Upon reception of the UE CONTEXT RELEASE COMMAND message, the NG-RAN node shall release all related signalling and user data transport resources and reply with the UE CONTEXT RELEASE COMPLETE message. + +If the *PDU Session Resource List* IE is included in the UE CONTEXT RELEASE COMPLETE message, the AMF shall handle this information as specified in TS 23.502 [10]. + +If the *User Location Information* IE is included in the UE CONTEXT RELEASE COMPLETE message, the AMF shall handle this information as specified in TS 23.502 [10]. + +If the *Information on Recommended Cells and RAN Nodes for Paging* IE is included in the UE CONTEXT RELEASE COMPLETE message, the AMF shall, if supported, store it and may use it for subsequent paging. + +For each PDU session for which the *Secondary RAT Usage Information* IE is included in the *PDU Session Resource Release Response Transfer* IE, the SMF shall handle this information as specified in TS 23.502 [10]. + +If the *Paging Assistance Data for CE Capable UE* IE is included in the UE CONTEXT RELEASE COMPLETE message, the AMF shall, if supported, store it and use it for subsequent paging, as specified in TS 23.502 [10]. + +### 8.3.3.3 Unsuccessful Operation + +Not applicable. + +### 8.3.3.4 Abnormal Conditions + +If the UE Context Release procedure is not initiated towards the NG-RAN node before the expiry of the timer $TNG_{RELOCOoverall}$ , the NG-RAN node shall request the AMF to release the UE context. + +If the UE returns to the NG-RAN node before the reception of the UE CONTEXT RELEASE COMMAND message or the expiry of the timer $TNG_{RELOCOoverall}$ , the NG-RAN node shall stop the timer $TNG_{RELOCOoverall}$ and continue to serve the UE. + +## 8.3.4 UE Context Modification + +### 8.3.4.1 General + +The purpose of the UE Context Modification procedure is to partly modify the established UE context. The procedure uses UE-associated signalling. + +### 8.3.4.2 Successful Operation + +![Sequence diagram showing the successful operation of UE context modification. The diagram shows two vertical lifelines: NG-RAN node (left) and AMF (right). The AMF sends a 'UE CONTEXT MODIFICATION REQUEST' message to the NG-RAN node. The NG-RAN node responds with a 'UE CONTEXT MODIFICATION RESPONSE' message back to the AMF. Both lifelines end with a thick horizontal bar at the bottom.](b432c6c13fa4f8bb90f5fb9060ef3bcd_img.jpg) + +``` + +sequenceDiagram + participant AMF + participant NG-RAN node + Note left of NG-RAN node: + AMF->>NG-RAN node: UE CONTEXT MODIFICATION REQUEST + NG-RAN node-->>AMF: UE CONTEXT MODIFICATION RESPONSE + Note right of AMF: + +``` + +Sequence diagram showing the successful operation of UE context modification. The diagram shows two vertical lifelines: NG-RAN node (left) and AMF (right). The AMF sends a 'UE CONTEXT MODIFICATION REQUEST' message to the NG-RAN node. The NG-RAN node responds with a 'UE CONTEXT MODIFICATION RESPONSE' message back to the AMF. Both lifelines end with a thick horizontal bar at the bottom. + +**Figure 8.3.4.2-1: UE context modification: successful operation** + +Upon receipt of the UE CONTEXT MODIFICATION REQUEST message the NG-RAN node shall + +- if supported, store the received IAB Authorization information in the UE context. If the *IAB Authorized* IE is set to "not authorized" for an IAB-MT, the NG-RAN node shall, if supported, initiate actions to ensure that the IAB node will not serve any UE(s). +- if supported, store the received Mobile IAB Authorization information in the UE context. If the *Mobile IAB Authorized* IE is set to "not authorized" for a mobile IAB-MT, the NG-RAN node shall, if supported, initiate actions to ensure that the mobile IAB-node will not serve any UE(s). + +If the *Security Key* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node shall store it and perform AS key re-keying according to TS 33.501 [13]. + +If the *UE Security Capabilities* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node shall store them and take them into use together with the received keys according to TS 33.501 [13]. + +If the *Index to RAT/Frequency Selection Priority* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node shall, if supported, use it as defined in TS 23.501 [9]. + +If the *RAN Paging Priority* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node may use it to determine a priority for paging the UE in RRC\_INACTIVE state. + +If the *UE Aggregate Maximum Bit Rate* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node shall + +- replace the previously provided UE Aggregate Maximum Bit Rate by the received UE Aggregate Maximum Bit Rate in the UE context; +- use the received UE Aggregate Maximum Bit Rate for all Non-GBR QoS flows for the concerned UE as specified in TS 23.501 [9]. + +If the *Core Network Assistance Information for RRC INACTIVE* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node shall, if supported, replace the previously provided Core Network Assistance Information for RRC INACTIVE and use it for the RRC\_INACTIVE state decision and RNA configuration for the UE and RAN paging if any for a UE in RRC\_INACTIVE state, as specified in TS 38.300 [8]. If the *MICO All PLMN* IE is + +included in the *Core Network Assistance Information for RRC INACTIVE* IE the NG-RAN node shall, if supported, consider that the registration area for the UE is the full PLMN and ignore the *TAI List for RRC Inactive* IE. If the *Paging Cause Indication for Voice Service* IE is included in the *Core Network Assistance Information for RRC INACTIVE* IE, the NG-RAN node shall, if supported, store and use it as specified in TS 38.300 [8]. If the *PEIPS Assistance Information* IE is included in the *Core Network Assistance Information for RRC INACTIVE* IE, the NG-RAN node shall, if supported, store it and use it for paging subgrouping the UE in RRC\_INACTIVE state, as specified in TS 38.300 [8]. If the *CN MT Communication Handling* IE is included in the *Core Network Assistance Information for RRC INACTIVE* IE, the NG-RAN node shall, if supported, store it and may subsequently request, based on implementation, the CN for mobile terminated communication handling as described in TS 23.502 [10]. + +If the *CN Assisted RAN Parameters Tuning* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node may use it as described in TS 23.501 [9]. + +If the *RRC Inactive Transition Report Request* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node shall, if supported, store this information in the UE context and report to the AMF the *User Location Information* IE and the *RRC State* IE in the UE CONTEXT MODIFICATION RESPONSE message. + +If the *RRC Inactive Transition Report Request* IE is included in the UE CONTEXT MODIFICATION REQUEST message and set to "cancel report", the NG-RAN node shall, if supported, stop reporting to the AMF the RRC state of the UE. + +The NG-RAN node shall report, in the UE CONTEXT MODIFICATION RESPONSE message to the AMF, the successful update of the UE context. + +If the *Emergency Fallback Indicator* IE is included in the UE CONTEXT MODIFICATION REQUEST message, it indicates that the concerned UE context is subject to emergency service fallback as described in TS 23.501 [9] and the NG-RAN node may, if supported, take the appropriate mobility actions taking into account the *Emergency Service Target CN* IE if provided. + +If the *New AMF UE NGAP ID* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node shall use the received value for future signalling with the AMF. + +If the *New GUAMI* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node shall replace the previously stored GUAMI as specified in TS 23.501 [9]. + +If the *SRVCC Operation Possible* IE is included in UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node shall, if supported, store the content of the received *SRVCC Operation Possible* IE in the UE context and use it as defined in TS 23.216 [31]. + +If the *NR V2X Services Authorized* IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node 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 NG-RAN node 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 NG-RAN node 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 NG-RAN node shall, if supported, initiate actions to ensure that the UE is no longer accessing the relevant service(s). + +If the *NR A2X Services Authorized* IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node 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 NG-RAN node 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 NG-RAN node 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 NG-RAN node shall, if supported, initiate actions to ensure that the UE is no longer accessing the relevant service(s). + +If the *NR UE Sidelink Aggregate Maximum Bit Rate* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node shall, if supported: + +- replace the previously provided NR UE 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 *LTE UE Sidelink Aggregate Maximum Bit Rate* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node shall, if supported: + +- replace the previously provided LTE UE 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 A2X UE PC5 Aggregate Maximum Bit Rate* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node shall, if supported: + +- replace the previously provided NR A2X 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 NR A2X services. + +If the *LTE A2X UE PC5 Aggregate Maximum Bit Rate* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node shall, if supported: + +- replace the previously provided LTE A2X 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 LTE A2X services. + +If the *PC5 QoS Parameters* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node shall, if supported, use it as defined in TS 23.287 [33]. + +If the *A2X PC5 QoS Parameters* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node shall, if supported, use it as defined in TS 23.256 [54]. + +If the UE CONTEXT MODIFICATION REQUEST message contains the *UE Radio Capability ID* IE, the NG-RAN node shall, if supported, use it as specified in TS 23.501 [9] and TS 23.502 [10]. + +If the *Time Synchronisation Assistance Information* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node shall, if supported, store the information in the UE context and use it as defined in TS 23.501 [9]. + +If the *QMC Configuration Information* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node shall, if supported, use it for QoE management, as described in TS 38.300 [8]. If the *Assistance Information for QoE Measurement* IE is included in the *UE Application Layer Measurement Configuration Information* IE within the *QMC Configuration Information* IE, the NG-RAN node may take it into account for controlling the UE reporting when the NG-RAN node is overloaded, as described in TS 38.300 [8]. + +If the *QMC Deactivation* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node shall, if supported, deactivate the QMC configurations therein. + +If the *UE Slice Maximum Bit Rate List* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node shall, if supported: + +- store and replace the previously provided UE Slice Maximum Bit Rate List, if any, by the received UE Slice Maximum Bit Rate List in the UE context; +- use the received UE Slice Maximum Bit Rate List for each S-NSSAI for the concerned UE as specified in TS 23.501 [9]. + +If the *Management Based MDT PLMN Modification List* IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node 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 [11]. + +If the *5G ProSe Authorized* IE is included in UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node shall, if supported, update the 5G ProSe authorization information for the UE accordingly. If the *5G ProSe Authorized* IE includes one or more IEs set to “not authorized”, the NG-RAN node shall, if supported, initiate actions to ensure that the UE is no longer accessing the relevant 5G ProSe service(s). + +If the *5G ProSe UE PC5 Aggregate Maximum Bit Rate* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node 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 QoS Parameters* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node shall, if supported, use it as defined in TS 23.304 [47]. + +If the *Network Controlled Repeater Authorized* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node shall, if supported, update its Network Controlled Repeater Authorization information for the UE accordingly and take it into account when configuring UE information. + +If the *Aerial UE Subscription Information* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node shall, if supported, store the information or overwrite any previously stored information in the UE context and use it as defined in TS 38.300 [8]. + +#### **Interactions with RRC Inactive Transition Report procedure:** + +If the *RRC Inactive Transition Report Request* IE is included in the UE CONTEXT MODIFICATION REQUEST message and set to "single RRC connected state report", the NG-RAN node shall, if supported and if the UE is in RRC\_INACTIVE state, send one subsequent RRC INACTIVE TRANSITION REPORT message to the AMF when the RRC state transitions to RRC\_CONNECTED state. + +If the *RRC Inactive Transition Report Request* IE is included in the UE CONTEXT MODIFICATION REQUEST message and set to "subsequent state transition report", the NG-RAN node shall, if supported, send the RRC INACTIVE TRANSITION REPORT message to the AMF to report the RRC state of the UE when the UE enters or leaves RRC\_INACTIVE state. + +### 8.3.4.3 Unsuccessful Operation + +![Sequence diagram for UE context modification: unsuccessful operation](9f50279046b74a4e66a1a0144c3b1d11_img.jpg) + +A sequence diagram showing the interaction between an NG-RAN node and an AMF for an unsuccessful UE context modification. The AMF sends a 'UE CONTEXT MODIFICATION REQUEST' message to the NG-RAN node. The NG-RAN node responds with a 'UE CONTEXT MODIFICATION FAILURE' message back to the AMF. Both entities are represented by rectangular boxes with lifelines extending downwards, and there are solid black bars at the base of each lifeline. + +Sequence diagram for UE context modification: unsuccessful operation + +**Figure 8.3.4.3-1: UE context modification: unsuccessful operation** + +In case the UE context update cannot be performed successfully, the NG-RAN node shall respond with the UE CONTEXT MODIFICATION FAILURE message to the AMF with an appropriate cause value in the *Cause* IE. + +If the *New AMF UE NGAP ID* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node may use the received *New AMF UE NGAP ID* IE or *Old AMF UE NGAP ID* IE in the UE CONTEXT MODIFICATION FAILURE message. + +### 8.3.4.4 Abnormal Conditions + +If the UE CONTEXT MODIFICATION REQUEST message including the *New AMF UE NGAP ID* IE is received after the NG-RAN node has initiated another class 1 NGAP EP, the NG-RAN node shall be prepared to receive the response message containing an AMF UE NGAP ID with the value received in the *New AMF UE NGAP ID* IE. + +NOTE: If the *Emergency Fallback Indicator* IE and the *Security Key* IE are both included in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node may handle only the *Emergency Fallback Indicator* IE. + +## 8.3.5 RRC Inactive Transition Report + +### 8.3.5.1 General + +The purpose of the RRC Inactive Transition Report procedure is to notify the AMF when the UE enters or leaves RRC\_INACTIVE state. The procedure uses UE-associated signalling. + +### 8.3.5.2 Successful Operation + +![Sequence diagram for RRC Inactive transition report](8395ccdee8a80af834aca2bdfd7f9a9b_img.jpg) + +A sequence diagram showing the RRC Inactive transition report procedure. The NG-RAN node sends an 'RRC INACTIVE TRANSITION REPORT' message to the AMF. Both entities are represented by rectangular boxes with lifelines extending downwards, and there are solid black bars at the base of each lifeline. + +Sequence diagram for RRC Inactive transition report + +**Figure 8.3.5.2-1: RRC Inactive transition report** + +The NG-RAN node initiates the procedure by sending an RRC INACTIVE TRANSITION REPORT message to the AMF. Upon reception of the RRC INACTIVE TRANSITION REPORT message, the AMF shall take appropriate actions based on the information indicated by the *RRC State* IE. + +### 8.3.5.3 Abnormal Conditions + +Void. + +## 8.3.6 Connection Establishment Indication + +### 8.3.6.1 General + +The purpose of the Connection Establishment Indication procedure is to enable the AMF to complete the establishment of the UE-associated logical NG-connection. The procedure uses UE-associated signalling. This procedure applies only if the NG-RAN node is an ng-eNB. + +### 8.3.6.2 Successful Operation + +![Sequence diagram showing the Connection Establishment Indication procedure. The AMF sends a CONNECTION ESTABLISHMENT INDICATION message to the NG-RAN node.](10cc1e74f2b71404f021bb8b3cec0ff0_img.jpg) + +``` +sequenceDiagram + participant AMF + participant NG-RAN node + Note right of AMF: + AMF->>NG-RAN node: CONNECTION ESTABLISHMENT INDICATION + Note left of NG-RAN node: + Note right of NG-RAN node: + Note left of AMF: + Note right of AMF: +``` + +The diagram illustrates the successful operation of the Connection Establishment Indication procedure. It features two vertical lifelines: 'NG-RAN node' on the left and 'AMF' on the right. A horizontal arrow labeled 'CONNECTION ESTABLISHMENT INDICATION' points from the AMF lifeline to the NG-RAN node lifeline. Both lifelines have a small horizontal bar at the bottom, indicating the start of the procedure. + +Sequence diagram showing the Connection Establishment Indication procedure. The AMF sends a CONNECTION ESTABLISHMENT INDICATION message to the NG-RAN node. + +**Figure 8.3.6.2-1: Connection Establishment Indication procedure. Successful operation.** + +The AMF initiates the procedure by sending a CONNECTION ESTABLISHMENT INDICATION message to the NG-RAN node. + +If the UE-associated logical NG-connection is not established, the AMF shall allocate a unique AMF UE NGAP ID to be used for the UE and include it in the CONNECTION ESTABLISHMENT INDICATION message. + +If the *UE Radio Capability* IE is included in the CONNECTION ESTABLISHMENT INDICATION message, the NG-RAN node shall store this information in the UE context, and use it as defined in TS 38.300 [8]. + +If the *End Indication* IE is included in the CONNECTION ESTABLISHMENT INDICATION message and set to "no further data", the NG-RAN node shall consider that there are no further NAS PDUs to be transmitted for this UE. + +If the *S-NSSAI* IE is contained in the CONNECTION ESTABLISHMENT INDICATION message, the NG-RAN node shall store this information in the UE context, and use it as specified in TS 23.501 [9]. + +If the *Allowed NSSAI* IE is contained in the CONNECTION ESTABLISHMENT INDICATION message, the NG-RAN node shall store this information in the UE context, and use it as specified in TS 23.501 [9]. + +If the *Partially Allowed NSSAI* IE is contained in the CONNECTION ESTABLISHMENT INDICATION message, the NG-RAN node shall, if supported, deduce from it the partially allowed network slices for the UE, store and replace any previously received Partially Allowed NSSAI and use it as specified in TS 23.501 [9]. + +If the *UE Differentiation Information* IE is included in the CONNECTION ESTABLISHMENT INDICATION message, the NG-RAN node shall, if supported, store this information in the UE context for further use according to TS 23.501 [9]. + +If the *DL CP Security Information* IE is included in the CONNECTION ESTABLISHMENT INDICATION message, the NG-RAN node shall forward this information to the UE as described in TS 36.300 [17]. + +If the NB-IoT UE Priority IE is contained in the CONNECTION ESTABLISHMENT INDICATION message, the NG-RAN node shall, if supported, store this information in the UE context, and use it as specified in TS 23.501 [9]. + +If the *Enhanced Coverage Restriction* IE is included in the CONNECTION ESTABLISHMENT INDICATION message, the NG-RAN node shall, if supported, store this information in the UE context and use it as defined in TS 23.501 [9]. + +If the *CE-mode-B Restricted* IE is included in the CONNECTION ESTABLISHMENT INDICATION message and the *Enhanced Coverage Restriction* IE is not set to "restricted" and the Enhanced Coverage Restricted information stored in the UE context is not set to "restricted", the NG-RAN node shall, if supported, store this information in the UE context and use it as defined in TS 23.501 [9]. + +If the *UE Radio Capability ID* IE is contained in the CONNECTION ESTABLISHMENT INDICATION message, the NG-RAN node shall, if supported, use it as specified in TS 23.501 [9] and TS 23.502 [10]. + +If the *Masked IMEISV* IE is contained in the CONNECTION ESTABLISHMENT INDICATION message, the NG-RAN node shall, if supported, use it to determine the characteristics of the UE for subsequent handling. + +If the *Old AMF* IE is included in the CONNECTION ESTABLISHMENT INDICATION message, the NG-RAN node shall consider that this UE-associated logical NG-connection was redirected to this AMF from another AMF identified by the *Old AMF* IE. + +### 8.3.6.3 Abnormal Conditions + +If the *Partially Allowed NSSAI* IE is received in the CONNECTION ESTABLISHMENT INDICATION message and the total number of S-NSSAIs included in the Allowed NSSAI and Partially Allowed NSSAI exceeds eight, the NG-RAN node shall consider the procedure as failed. + +If any of the S-NSSAI which is present in the *Partially Allowed NSSAI* IE is also present in the *Allowed NSSAI* IE, the NG-RAN node shall consider the procedure as failed. + +## 8.3.7 AMF CP Relocation Indication + +### 8.3.7.1 General + +The purpose of the AMF CP Relocation Indication procedure is to inform the NG-RAN node that the UE's connection is to be relocated to another NG-RAN node as described in TS 38.300 [8], for a UE using Control Plane CIoT 5GS Optimisation. This procedure applies only if the NG-RAN node is an ng-eNB. + +The procedure uses UE-associated signalling. + +### 8.3.7.2 Successful Operation + +![Sequence diagram showing the AMF CP Relocation Indication procedure. The AMF sends a message to the NG-RAN node.](fe2ffb87faa0257386b73d34f10bbfbd_img.jpg) + +``` +sequenceDiagram + participant AMF + participant NG-RAN node + Note left of NG-RAN node: + Note right of AMF: + AMF->>NG-RAN node: AMF CP RELOCATION INDICATION +``` + +The diagram illustrates the successful operation of the AMF CP Relocation Indication procedure. It shows two entities: the NG-RAN node and the AMF. A horizontal arrow labeled "AMF CP RELOCATION INDICATION" points from the AMF to the NG-RAN node. Both entities are represented by rectangular boxes with vertical lines extending downwards to a horizontal bar at the bottom, indicating the timeline of the procedure. + +Sequence diagram showing the AMF CP Relocation Indication procedure. The AMF sends a message to the NG-RAN node. + +**Figure 8.3.7.2-1: AMF CP Relocation Indication. Successful operation.** + +The AMF initiates the procedure by sending an AMF CP RELOCATION INDICATION message to the NG-RAN node. + +Upon reception of the AMF CP RELOCATION INDICATION message, the NG-RAN node shall terminate the delivery of NAS messages that have been received from the AMF. + +If the *S-NSSAI* IE is contained in the AMF CP RELOCATION INDICATION message, the NG-RAN node shall store this information in the UE context, and use it as specified in TS 23.501 [9]. + +If the *Allowed NSSAI* IE is contained in the AMF CP RELOCATION INDICATION message, the NG-RAN node shall store this information in the UE context, and use it as specified in TS 23.501 [9]. + +If the *Partially Allowed NSSAI* IE is contained in the AMF CP RELOCATION INDICATION message, the NG-RAN node shall, if supported, deduce from it the partially allowed network slices for the UE, store and replace any previously received Partially Allowed NSSAI and use it as specified in TS 23.501 [9]. + +#### **Interactions with NAS Non Delivery Indication procedure:** + +On reception of the AMF CP RELOCATION INDICATION message, the NG-RAN node may initiate NAS Non Delivery Indication procedure(s) to report the non-delivery of any NAS PDUs previously received from the AMF. + +### **8.3.7.3 Abnormal Conditions** + +If the *Partially Allowed NSSAI* IE is received in the AMF CP RELOCATION INDICATION message and the total number of S-NSSAIs included in the Allowed NSSAI and Partially Allowed NSSAI exceeds eight, the NG-RAN node shall consider the procedure as failed. + +If any of the S-NSSAI which is present in the *Partially Allowed NSSAI* IE is also present in the *Allowed NSSAI* IE, the NG-RAN node shall consider the procedure as failed. + +## **8.3.8 RAN CP Relocation Indication** + +### **8.3.8.1 General** + +The purpose of the RAN CP Relocation Indication procedure is to request the AMF to authenticate the UE's re-establishment request, and trigger the establishment of the respective UE-associated logical NG-connection, for a NB-IoT UE using Control Plane CIoT 5GS Optimisation. This procedure applies only if the NG-RAN node is an ng-eNB. + +The procedure uses UE-associated signalling. + +### **8.3.8.2 Successful Operation** + +![Sequence diagram showing the RAN CP Relocation Indication procedure. An NG-RAN node sends a RAN CP RELOCATION INDICATION message to the AMF.](2dca0da216307a42a155676028e18ee6_img.jpg) + +``` +sequenceDiagram + participant NG-RAN node + participant AMF + Note left of NG-RAN node: + NG-RAN node->>AMF: RAN CP RELOCATION INDICATION + Note right of AMF: + Note left of NG-RAN node: + Note right of AMF: +``` + +Sequence diagram showing the RAN CP Relocation Indication procedure. An NG-RAN node sends a RAN CP RELOCATION INDICATION message to the AMF. + +**Figure 8.3.8.2-1: RAN CP Relocation Indication.** + +The NG-RAN node initiates the procedure by sending a RAN CP RELOCATION INDICATION message to the AMF. + +The NG-RAN node shall allocate a unique RAN UE NGAP ID to be used for the UE and the NG-RAN node shall include this identity in the RAN CP RELOCATION INDICATION message. + +Upon receiving the RAN CP RELOCATION INDICATION message, the AMF shall authenticate the request using the NAS-level security information received in the *UL CP Security Information* IE and if the authentication is successful initiate the Connection Establishment Indication procedure including NAS-level security information in the *DL CP Security Information* IE. + +In case the AMF cannot authenticate the UE's request, the CONNECTION ESTABLISHMENT INDICATION message does not contain security information, and the NG-RAN node shall fail the RRC Re-establishment. + +In case of authentication failure, the NG-RAN node and the AMF should locally release the allocated NG resources, if any. + +#### **Interactions with the AMF CP Relocation and UE Context Release procedures:** + +In case of successful UE authentication, the AMF initiates the UE Context Release procedure to release the UE's NG-connection in the old NG-RAN node. The AMF may initiate the AMF CP Relocation procedure before the release procedure in order to trigger the old NG-RAN node to return non-delivered NAS PDUs to the AMF. + +### **8.3.8.3 Abnormal Conditions** + +Void. + +## **8.3.9 Retrieve UE Information** + +### **8.3.9.1 General** + +The purpose of the Retrieve UE Information procedure is for the NG-RAN node to request the UE information including NB-IoT UE Priority and UE Radio Capability from the AMF, for a NB-IoT UE using Control Plane CIoT 5GS Optimisation. The procedure uses non UE-associated signalling. This procedure applies only if the NG-RAN node is an ng-eNB. + +### **8.3.9.2 Successful Operation** + +![Sequence diagram showing the successful operation of the Retrieve UE Information procedure. The NG-RAN node sends a RETRIEVE UE INFORMATION message to the AMF.](3941735fafadf9a59b811f67fcdca7b3_img.jpg) + +``` +sequenceDiagram + participant NG-RAN node + participant AMF + Note left of NG-RAN node: + NG-RAN node->>AMF: RETRIEVE UE INFORMATION + Note right of AMF: +``` + +Sequence diagram showing the successful operation of the Retrieve UE Information procedure. The NG-RAN node sends a RETRIEVE UE INFORMATION message to the AMF. + +**Figure 8.3.9.2-1: Retrieve UE Information** + +The NG-RAN node initiates the procedure by sending the RETRIEVE UE INFORMATION message to the AMF. + +### **8.3.9.3 Abnormal Conditions** + +Void. + +## 8.3.10 UE Information Transfer + +### 8.3.10.1 General + +The purpose of the UE Information Transfer procedure is for the AMF to send the UE information including NB-IoT UE Priority and UE Radio Capability to the NG-RAN node, for a NB-IoT UE using Control Plane CIoT 5GS Optimisation. The procedure uses non UE-associated signalling. This procedure applies only if the NG-RAN node is an ng-eNB. + +### 8.3.10.2 Successful Operation + +![Sequence diagram showing the UE Information Transfer procedure. The AMF sends a UE INFORMATION TRANSFER message to the NG-RAN node.](bd50d56ae2c12a92466ba2aea1a78040_img.jpg) + +``` +sequenceDiagram + participant AMF + participant NG-RAN node + Note right of AMF: UE INFORMATION TRANSFER + AMF->>NG-RAN node: UE INFORMATION TRANSFER + Note left of NG-RAN node: +``` + +Sequence diagram showing the UE Information Transfer procedure. The AMF sends a UE INFORMATION TRANSFER message to the NG-RAN node. + +Figure 8.3.10.2-1: UE Information Transfer + +The AMF initiates the procedure by sending the UE INFORMATION TRANSFER message to the NG-RAN node. + +If the *NB-IoT UE Priority* IE is contained in the UE INFORMATION TRANSFER message, the NG-RAN node shall store this information in the UE context, and use it as specified in TS 23.501 [9]. + +If the *UE Radio Capability* IE is contained in the UE INFORMATION TRANSFER message, the NG-RAN node shall store this information in the UE context, and use it as specified in TS 23.501 [9]. + +If the *S-NSSAI* IE is contained in the UE INFORMATION TRANSFER message, the NG-RAN node shall store this information in the UE context, and use it as specified in TS 23.501 [9]. + +If the *Allowed NSSAI* IE is contained in the UE INFORMATION TRANSFER message, the NG-RAN node shall store this information in the UE context, and use it as specified in TS 23.501 [9]. + +If the *Partially Allowed NSSAI* IE is contained in the UE INFORMATION TRANSFER message, the NG-RAN node shall, if supported, deduce from it the partially allowed network slices for the UE, store and replace any previously received Partially Allowed NSSAI and use it as specified in TS 23.501 [9]. + +If the *UE Differentiation Information* IE is included in the UE INFORMATION TRANSFER message, the NG-RAN node shall, if supported, store this information in the UE context for further use according to TS 23.501 [9]. + +If the *Masked IMEISV* IE is contained in the UE INFORMATION TRANSFER message, the NG-RAN node shall, if supported, use it to determine the characteristics of the UE for subsequent handling. + +### 8.3.10.3 Abnormal Conditions + +If the *Partially Allowed NSSAI* IE is received in the UE INFORMATION TRANSFER message and the total number of S-NSSAIs included in the Allowed NSSAI and Partially Allowed NSSAI exceeds eight, the NG-RAN node shall consider the procedure as failed. + +If any of the S-NSSAI which is present in the *Partially Allowed NSSAI* IE is also present in the *Allowed NSSAI* IE, the NG-RAN node shall consider the procedure as failed. + +## 8.3.11 UE Context Suspend + +### 8.3.11.1 General + +The purpose of the UE Context Suspend procedure is to suspend the UE-associated logical NG-connection and the NG-U transport bearer with the 5GC while keeping the UE context in the NG-RAN node. The procedure uses UE-associated signalling. + +In this version of the specification, this procedure applies only if the NG-RAN node is an ng-eNB. + +### 8.3.11.2 Successful Operation + +![Sequence diagram for UE Context Suspend: Successful operation. The diagram shows two vertical lifelines. The left lifeline represents the NG-RAN node, and the right lifeline represents the AMF. A horizontal arrow points from the NG-RAN node to the AMF, representing the UE CONTEXT SUSPEND REQUEST message. A return arrow points from the AMF back to the NG-RAN node, representing the UE CONTEXT SUSPEND RESPONSE message. Both lifelines have a thick black horizontal bar at the top, indicating active periods.](ddcf2f580e914bff1e7756ed288874e1_img.jpg) + +Sequence diagram for UE Context Suspend: Successful operation. The diagram shows two vertical lifelines. The left lifeline represents the NG-RAN node, and the right lifeline represents the AMF. A horizontal arrow points from the NG-RAN node to the AMF, representing the UE CONTEXT SUSPEND REQUEST message. A return arrow points from the AMF back to the NG-RAN node, representing the UE CONTEXT SUSPEND RESPONSE message. Both lifelines have a thick black horizontal bar at the top, indicating active periods. + +**Figure 8.3.11.2-1: UE Context Suspend: Successful operation.** + +The NG-RAN node initiates the procedure by sending the UE CONTEXT SUSPEND REQUEST message to the AMF. + +Upon receipt of the UE CONTEXT SUSPEND REQUEST message the AMF shall act as defined in TS 23.502 [10]. + +Upon receipt of the UE CONTEXT SUSPEND RESPONSE message the NG-RAN node shall suspend the UE context, the UE-associated logical NG-connection and the related PDU session contexts and send the UE to RRC\_IDLE. + +If the *Information on Recommended Cells and RAN Nodes for Paging* IE is included in the UE CONTEXT SUSPEND REQUEST message, the AMF shall, if supported, store it and may use it for subsequent paging. + +If the *Paging Assistance Data for CE Capable UE* IE is included in the UE CONTEXT SUSPEND REQUEST message, the AMF shall, if supported, store it and use it for subsequent paging, as specified in TS 23.502 [10]. + +If the *Security Context* IE is included in the UE CONTEXT SUSPEND RESPONSE message, the NG-RAN node shall store the received *Security Context* IE in the UE context and remove any existing unused stored {NH, NCC} as specified in TS 33.501 [13]. + +If the *Suspend Indicator* IE is included in the UE CONTEXT SUSPEND REQUEST message, the SMF shall, if supported, consider the associated PDU session as suspended. + +### 8.3.11.3 Unsuccessful Operation + +![Sequence diagram for UE Context Suspend: unsuccessful operation. The NG-RAN node sends a UE CONTEXT SUSPEND REQUEST to the AMF, and the AMF responds with a UE CONTEXT SUSPEND FAILURE.](e5ded42f8e352da02ee86cb55550c45d_img.jpg) + +``` + +sequenceDiagram + participant NG-RAN node + participant AMF + Note left of NG-RAN node: + NG-RAN node->>AMF: UE CONTEXT SUSPEND REQUEST + Note right of AMF: + AMF-->>NG-RAN node: UE CONTEXT SUSPEND FAILURE + Note left of NG-RAN node: + +``` + +Sequence diagram for UE Context Suspend: unsuccessful operation. The NG-RAN node sends a UE CONTEXT SUSPEND REQUEST to the AMF, and the AMF responds with a UE CONTEXT SUSPEND FAILURE. + +**Figure 8.3.11.3-1: UE Context Suspend: unsuccessful operation.** + +If the AMF decides to not suspend the connection e.g. due to pending downlink data to be sent, it shall send the UE CONTEXT SUSPEND FAILURE message to the NG-RAN node. + +### 8.3.11.4 Abnormal Conditions + +Void. + +## 8.3.12 UE Context Resume + +### 8.3.12.1 General + +The purpose of the UE Context Resume procedure is to resume the UE context, the suspended UE-associated logical NG-connection and the related NG-U transport bearer in the 5GC for this UE. The procedure uses UE-associated signalling. + +In this version of the specification, this procedure applies only if the NG-RAN node is an ng-eNB. + +### 8.3.12.2 Successful Operation + +![Sequence diagram for UE Context Resume procedure: Successful operation. The NG-RAN node sends a UE CONTEXT RESUME REQUEST to the AMF, and the AMF responds with a UE CONTEXT RESUME RESPONSE.](0084ef0a1a9dee9842da698ab9b098ad_img.jpg) + +``` + +sequenceDiagram + participant NG-RAN node + participant AMF + Note left of NG-RAN node: + NG-RAN node->>AMF: UE CONTEXT RESUME REQUEST + Note right of AMF: + AMF-->>NG-RAN node: UE CONTEXT RESUME RESPONSE + Note left of NG-RAN node: + +``` + +Sequence diagram for UE Context Resume procedure: Successful operation. The NG-RAN node sends a UE CONTEXT RESUME REQUEST to the AMF, and the AMF responds with a UE CONTEXT RESUME RESPONSE. + +**Figure 8.3.12.2-1: UE Context Resume procedure. Successful operation.** + +The NG-RAN node initiates the procedure by sending the UE CONTEXT RESUME REQUEST message to the AMF. If the NG-RAN node is not able to admit any suspended PDU sessions, the NG-RAN node shall indicate this in the *PDU Session Resource Failed to Resume List* IE. If the NG-RAN node is not able to admit certain QoS flows for a PDU session, the NG-RAN node shall indicate this in the *QoS Flow Failed to Resume List* IE included in the *UE Context Resume Request Transfer* IE for that PDU session. + +Upon receipt of the UE CONTEXT RESUME REQUEST message the AMF shall act as defined in TS 23.502 [10] and respond with the UE CONTEXT RESUME RESPONSE message. If the AMF is not able to admit any suspended PDU sessions, the AMF shall indicate this in the *PDU Session Resource Failed to Resume List* IE. If the SMF is not able to + +admit certain QoS flows for a PDU session, the SMF shall indicate this in the *QoS Flow Failed to Resume List* IE included in the *UE Context Resume Response Transfer* IE for that PDU session. + +The NG-RAN node shall release resources for each PDU session or QoS flow failed to resume and shall assume that the 5GC has released respective resources as well. + +If the *Security Context* IE is included in the UE CONTEXT RESUME RESPONSE message, the NG-RAN node shall store the received *Security Context* IE in the UE context and the NG-RAN node shall use it for the next suspend/resume or Xn handover or Intra NG-RAN node handovers as specified in TS 33.501 [13]. + +If the *Suspend Request Indication* IE is included in the UE CONTEXT RESUME REQUEST message, the AMF shall, if supported, consider that the NG-RAN node is requesting immediate transition to RRC IDLE with Suspend as specified in TS 23.502 [10]. If the *Suspend Response Indication* IE is included in the UE CONTEXT RESUME RESPONSE message, the NG-RAN node shall suspend the UE context, the UE-associated logical NG-connection and the related PDU session contexts and send the UE to RRC\_IDLE. + +If the *Information on Recommended Cells and RAN Nodes for Paging* IE is included in the UE CONTEXT RESUME REQUEST message, the AMF shall, if supported, store it and may use it for subsequent paging. + +If the *Paging Assistance Data for CE Capable UE* IE is included in the UE CONTEXT RESUME REQUEST message, the AMF shall, if supported, store it and use it for subsequent paging, as specified in TS 23.502 [10]. + +If the *Extended Connected Time* IE is included in the UE CONTEXT RESUME RESPONSE message, the NG-RAN node shall, if supported, use it as described in TS 23.501 [9]. + +### 8.3.12.3 Unsuccessful Operation + +![Sequence diagram illustrating an unsuccessful UE Context resume operation. A large black rectangle represents the User Equipment (UE). Below it, two smaller black rectangles represent the NG-RAN node (left) and the AMF (right). A dashed arrow points from the AMF to the NG-RAN node, indicating a failure response. A solid arrow points from the NG-RAN node to the UE, indicating the final RRC connection release.](7b2d685b805535c1e94aee1365753b92_img.jpg) + +Sequence diagram illustrating an unsuccessful UE Context resume operation. A large black rectangle represents the User Equipment (UE). Below it, two smaller black rectangles represent the NG-RAN node (left) and the AMF (right). A dashed arrow points from the AMF to the NG-RAN node, indicating a failure response. A solid arrow points from the NG-RAN node to the UE, indicating the final RRC connection release. + +**Figure 8.3.12.3-1: UE Context resume: unsuccessful operation.** + +If the AMF is not able to resume a single PDU session, it releases the UE-associated logical NG-connection by sending the UE CONTEXT RESUME FAILURE message to the NG-RAN node. Upon reception of the UE CONTEXT RESUME FAILURE message the NG-RAN node shall release the RRC connection as specified in TS 36.331 [21] and release all related signalling and user data transport resources. + +## 8.3.13 MT Communication Handling + +### 8.3.13.1 General + +The purpose of the MT Communication Handling procedure is to request the AMF to activate or deactivate the CN based MT Communication handling for a UE in RRC\_INACTIVE state with extended DRX beyond 10.24 seconds as specified in TS 23.501 [9]. The procedure uses UE-associated signalling. + +### 8.3.13.2 Successful Operation + +![Sequence diagram for MT Communication Handling procedure. Successful operation. The diagram shows two lifelines: NG-RAN node and AMF. The NG-RAN node sends an MT COMMUNICATION HANDLING REQUEST to the AMF. The AMF responds with an MT COMMUNICATION HANDLING RESPONSE.](64cda8ce20067bc360ce2f3a5c9352b7_img.jpg) + +``` +sequenceDiagram + participant NG-RAN node + participant AMF + Note left of NG-RAN node: + NG-RAN node->>AMF: MT COMMUNICATION HANDLING REQUEST + Note right of AMF: + AMF-->>NG-RAN node: MT COMMUNICATION HANDLING RESPONSE + Note left of NG-RAN node: +``` + +Sequence diagram for MT Communication Handling procedure. Successful operation. The diagram shows two lifelines: NG-RAN node and AMF. The NG-RAN node sends an MT COMMUNICATION HANDLING REQUEST to the AMF. The AMF responds with an MT COMMUNICATION HANDLING RESPONSE. + +**Figure 8.3.13.2-1: MT Communication Handling procedure. Successful operation.** + +The NG-RAN node initiates the procedure by sending the MT COMMUNICATION HANDLING REQUEST message to the AMF. + +If the *5GC Action* IE is included in the MT COMMUNICATION HANDLING REQUEST message and set to "HLCom Activate", the AMF shall activate MT communication handling as specified in TS 23.501 [9] and take into account the *NR Paging Long eDRX Information for RRC INACTIVE* IE when applying MT communication handling as specified in TS 38.304 [12] and TS 23.502 [10]. + +If the *5GC Action* IE is included in the MT COMMUNICATION HANDLING REQUEST message and set to "HLCom Deactivate", the AMF shall deactivate MT communication handling as specified in TS 23.501 [9]. + +### 8.3.13.3 Unsuccessful Operation + +![Sequence diagram for MT Communication Handling procedure. Unsuccessful operation. The diagram shows two lifelines: NG-RAN node and AMF. The NG-RAN node sends an MT COMMUNICATION HANDLING REQUEST to the AMF. The AMF responds with an MT COMMUNICATION HANDLING FAILURE.](747516f5861a0ddf31e3851da8e34b95_img.jpg) + +``` +sequenceDiagram + participant NG-RAN node + participant AMF + Note left of NG-RAN node: + NG-RAN node->>AMF: MT COMMUNICATION HANDLING REQUEST + Note right of AMF: + AMF-->>NG-RAN node: MT COMMUNICATION HANDLING FAILURE + Note left of NG-RAN node: +``` + +Sequence diagram for MT Communication Handling procedure. Unsuccessful operation. The diagram shows two lifelines: NG-RAN node and AMF. The NG-RAN node sends an MT COMMUNICATION HANDLING REQUEST to the AMF. The AMF responds with an MT COMMUNICATION HANDLING FAILURE. + +**Figure 8.3.13.3-1: MT Communication Handling: unsuccessful operation.** + +If the AMF is not able to activate CN based mobile terminating communication handling for the UE configured with eDRX cycle value longer than 10.24 seconds in RRC\_INACTIVE state, it shall send a MT COMMUNICATION HANDLING FAILURE message to the NG-RAN node. + +## 8.3.14 RAN Paging Request + +### 8.3.14.1 General + +This procedure is initiated by the AMF to indicate that there is DL data buffered in 5GC or DL signalling arrives for the UE. The procedure uses UE-associated signalling. + +### 8.3.14.2 Successful Operation + +![Sequence diagram for RAN Paging Request](18d7d8de298d79e7bc87af5217f11203_img.jpg) + +A sequence diagram showing the interaction between an NG-RAN node and an AMF. The AMF sends a 'RAN PAGING REQUEST' message to the NG-RAN node. The NG-RAN node is represented by a vertical line with a rectangle at the top labeled 'NG-RAN node'. The AMF is represented by a vertical line with a rectangle at the top labeled 'AMF'. Both lifelines have a thick horizontal bar at the bottom. The message arrow points from the AMF lifeline to the NG-RAN node lifeline. + +Sequence diagram for RAN Paging Request + +Figure 8.3.14.2-1: RAN Paging Request + +The AMF initiates the RAN Paging Request procedure by sending the RAN PAGING REQUEST message to the NG-RAN node. + +Upon reception of the RAN PAGING REQUEST message, the NG-RAN node shall perform RAN Paging for the UE in RRC\_INACTIVE state. + +If the *Paging Policy Differentiation* IE is included in the RAN PAGING REQUEST message, the NG-RAN node shall, if supported, take it into account when performing RAN Paging for the UE in RRC\_INACTIVE state. + +If the *DL Signalling* IE is included in the RAN PAGING REQUEST message, the NG-RAN node shall, if supported, take it into account when performing RAN Paging for the UE in RRC\_INACTIVE state. + +### 8.3.14.3 Abnormal Conditions + +Void. + +## 8.4 UE Mobility Management Procedures + +### 8.4.1 Handover Preparation + +#### 8.4.1.1 General + +The purpose of the Handover Preparation procedure is to request the preparation of resources at the target side via the 5GC. There is only one Handover Preparation procedure ongoing at the same time for a certain UE. The procedure uses UE-associated signalling. + +#### 8.4.1.2 Successful Operation + +![Sequence diagram for Handover preparation: successful operation](21c8a1f65b4718372aadf6a1cc10204d_img.jpg) + +A sequence diagram showing the interaction between two entities, likely representing the source and target NG-RAN nodes. The diagram consists of two vertical lifelines, each with a thick horizontal bar at the bottom. A message arrow points from the right lifeline to the left lifeline. The background of the diagram is a large black rectangle with a white rectangle in the top right corner. + +Sequence diagram for Handover preparation: successful operation + +Figure 8.4.1.2-1: Handover preparation: successful operation + +The source NG-RAN node initiates the handover preparation by sending the HANDOVER REQUIRED message to the serving AMF. When the source NG-RAN node sends the HANDOVER REQUIRED message, it shall start the timer $T_{NGRELOCprep}$ . The source NG-RAN node shall indicate the appropriate cause value for the handover in the *Cause* IE. + +Upon reception of the HANDOVER REQUIRED message the AMF shall, for each PDU session indicated in the *PDU Session ID* IE, transparently transfer the *Handover Required Transfer* IE to the SMF associated with the concerned PDU session. If the UE is a mobile IAB-MT which does not have any PDU sessions activated, the AMF shall ignore the *PDU Session Resource List* IE, and behave as specified in TS 23.502 [10]. + +In case of intra-system handover, the information in the *Source to Target Transparent Container* IE shall be encoded according to the definition of the *Source NG-RAN node to Target NG-RAN node Transparent Container* IE. + +If the *DL Forwarding* IE is included for a given QoS flow in the *PDU Session Resource Information Item* IE within the *Source NG-RAN node to Target NG-RAN node Transparent Container* IE of the HANDOVER REQUIRED message and it is set to "DL forwarding proposed", it indicates that the source NG-RAN node proposes forwarding of downlink data for that QoS flow. + +If the *UL Forwarding* IE is included for a given QoS flow in the *PDU Session Resource Information Item* IE within the *Source NG-RAN Node to Target NG-RAN Node Transparent Container* IE of the HANDOVER REQUIRED message and it is set to "UL forwarding proposed", it indicates that the source NG-RAN node proposes forwarding of uplink data for that QoS flow. + +If the *DRBs to QoS Flows Mapping List* IE is included in the *PDU Session Resource Information Item* IE within the *Source NG-RAN node to Target NG-RAN node Transparent Container* IE of the HANDOVER REQUIRED message, it implicitly indicates that the source NG-RAN node proposes forwarding of downlink data for those DRBs. + +If the *QoS Flow Mapping Indication* IE for a QoS flow is included in the *Associated QoS Flow List* IE within the *DRBs to QoS Flows Mapping List* IE within the *Source NG-RAN node to Target NG-RAN node Transparent Container* IE of the HANDOVER REQUIRED message, it indicates that the source NG-RAN node has mapped only the uplink or downlink of the QoS flow to the DRB. + +The source NG-RAN node shall, for each MRB of each MBS session contained in the *MBS Session Information Target to Source List* IE, start data forwarding to the TNL address contained in the *DL Forwarding UP TNL Information* IE. If the *MRB Progress Information* IE is contained for an MRB in the *Data Forwarding Response MRB List* IE in the *MBS Session Information Target to Source List* IE, the source NG-RAN node may use this information to determine when to stop data forwarding. + +In case of intra-system handover, if the HANDOVER COMMAND message contains the *DL Forwarding UP TNL Information* IE for a given DRB within the *Data Forwarding Response DRB List* IE in the *Handover Command Transfer* IE, the source NG-RAN node shall consider that the forwarding of downlink data for this DRB is accepted by the target NG-RAN node. If the HANDOVER COMMAND message contains the *UL Forwarding UP TNL Information* IE for a given DRB in the *Data Forwarding Response DRB List* IE within the *Handover Command Transfer* IE, it means the target NG-RAN node has requested the forwarding of uplink data for this DRB. + +In case direct data forwarding is applied for inter-system handover, if the *Data Forwarding Response E-RAB List* IE in the *Handover Command Transfer* IE is included in the HANDOVER COMMAND message, the source NG-RAN node shall consider that forwarding of downlink data for this E-RAB is accepted by the target eNB. + +If the HANDOVER COMMAND message contains the *UL Forwarding UP TNL Information* IE for a given PDU session within the *Handover Command Transfer* IE, the source NG-RAN node shall consider that the forwarding of uplink data of the QoS flows is accepted by the target NG-RAN node. + +In case of inter-system handover to LTE, the information in the *Source to Target Transparent Container* IE shall be encoded according to the *Source eNB to Target eNB Transparent Container* IE definition as specified in TS 36.413 [16]. + +If the *Direct Forwarding Path Availability* IE is included in the HANDOVER REQUIRED message the AMF shall handle it as specified in TS 23.502 [10]. + +If the *Direct Forwarding Path Availability* IE is included within the *Handover Required Transfer* IE of the HANDOVER REQUIRED message the SMF shall handle it as specified in TS 23.502 [10]. + +When the preparation, including the reservation of resources at the target side is ready, the AMF responds with the HANDOVER COMMAND message to the source NG-RAN node. In case of intra-system handover, the AMF shall include the *PDU Session Resource Handover List* IE in the HANDOVER COMMAND message. + +Upon reception of the HANDOVER COMMAND message the source NG-RAN node shall stop the timer $TNG_{RELOCprep}$ and start the timer $TNG_{RELOCoverall}$ . + +If there are any PDU sessions that could not be admitted in the target, they shall be indicated in the *PDU Session Resource to Release List* IE. + +NOTE: As an exception in case of inter-system handover to LTE, the AMF generates the *Handover Preparation Unsuccessful Transfer* IE in the *PDU Session Resource to Release List* IE. + +If the HANDOVER COMMAND message contains the *QoS Flow to be Forwarded List* IE and/or *Data Forwarding Response DRB List* IE within the *Handover Command Transfer* IE for a given PDU session, then the source NG-RAN node should initiate data forwarding for the QoS flows as specified in TS 38.300 [8]. + +If the HANDOVER COMMAND message contains the *Additional DL Forwarding UP TNL Information* IE within the *Handover Command Transfer* IE, the source NG-RAN node should initiate data forwarding of the PDU session split in different tunnel and shall use the received UP transport layer information for the forwarding QoS flows associated to it. + +If the HANDOVER COMMAND message contains the *Additional UL Forwarding UP TNL Information* IE within the *Handover Command Transfer* IE, the source NG-RAN node should initiate data forwarding of the PDU session split in different tunnels using the received UP transport layer information. + +If the *NAS Security Parameters from NG-RAN* IE is included in the HANDOVER COMMAND message the NG-RAN node shall use it as specified in TS 33.501 [13]. + +If the *Target to Source Transparent Container* IE has been received by the AMF from the handover target then the transparent container shall be included in the HANDOVER COMMAND message. + +If the HANDOVER COMMAND message contains the *QoS Flow Failed to Setup List* IE within the *Handover Command Transfer* IE, the source NG-RAN node shall consider that the listed QoS flows are failed to be handed over. + +In case of inter-system handover to LTE, the information in the *Target to Source Transparent Container* IE shall be encoded according to the definition of the *Target eNB to Source eNB Transparent Container* IE as specified in TS 36.413 [16]. + +If the *Index to RAT/Frequency Selection Priority* IE is contained in the *Source NG-RAN Node to Target NG-RAN Node Transparent Container* IE, the target NG-RAN node shall store the content of the received *Index to RAT/Frequency Selection Priority* IE in the UE context and use it as defined in TS 23.501 [9]. + +If the *DAPS Request Information* IE is included for a DRB in the *Source NG-RAN Node to Target NG-RAN Node Transparent Container* IE within the HANDOVER REQUIRED message, it indicates that the request concerns a DAPS Handover for that DRB, as described in TS 38.300 [8]. + +#### **Interactions with other NGAP procedures:** + +If, after a HANDOVER REQUIRED message is sent and before the Handover Preparation procedure is terminated, the source NG-RAN node receives an AMF initiated PDU Session Management procedure on the same UE-associated signalling connection, the source NG-RAN node shall either: + +1. Cancel the Handover Preparation procedure by executing the Handover Cancellation procedure with an appropriate cause value. After successful completion of the Handover Cancellation procedure, the source NG-RAN node shall continue the AMF initiated PDU Session Management procedure. + +or + +2. Terminate the AMF initiated PDU Session Management procedure by sending the appropriate response message with an appropriate cause value, e.g. "NG intra-system handover triggered" or "NG inter-system handover triggered" to the AMF and then the source NG-RAN node shall continue with the handover procedure. + +#### 8.4.1.3 Unsuccessful Operation + +![Diagram illustrating an unsuccessful handover preparation operation. It shows a source NG-RAN node (represented by a black rectangle) and a target NG-RAN node (represented by a white rectangle) connected to an AMF (represented by a large black rectangle). A message arrow points from the source NG-RAN node to the AMF, and another message arrow points from the AMF back to the source NG-RAN node, indicating a failure response.](4bb669bb31262e53e4f3c8ec0fd7624a_img.jpg) + +Diagram illustrating an unsuccessful handover preparation operation. It shows a source NG-RAN node (represented by a black rectangle) and a target NG-RAN node (represented by a white rectangle) connected to an AMF (represented by a large black rectangle). A message arrow points from the source NG-RAN node to the AMF, and another message arrow points from the AMF back to the source NG-RAN node, indicating a failure response. + +**Figure 8.4.1.3-1: Handover preparation: unsuccessful operation** + +If the 5GC or the target side is not able to accept any of the PDU session resources or a failure occurs during the Handover Preparation, the AMF sends the HANDOVER PREPARATION FAILURE message with an appropriate cause value to the source NG-RAN node. + +If the *Target to Source Failure Transparent Container* IE has been received by the AMF from the handover target then the transparent container shall be included in the HANDOVER PREPARATION FAILURE message. + +If the *Target to Source Failure Transparent Container* IE is received in the HANDOVER PREPARATION FAILURE message including the *Cell CAG Information* IE, the source NG-RAN node shall, if supported, store and replace the PNI-NPN information associated with the indicated cell. + +##### **Interaction with Handover Cancel procedure:** + +If there is no response from the AMF to the HANDOVER REQUIRED message before timer TNGRELOCprep expires in the source NG-RAN node, the source NG-RAN node should cancel the Handover Preparation procedure by initiating the Handover Cancel procedure with the appropriate value for the *Cause* IE. The source NG-RAN node shall ignore any HANDOVER COMMAND message or HANDOVER PREPARATION FAILURE message received after the initiation of the Handover Cancel procedure. + +#### 8.4.1.4 Abnormal Conditions + +In case of inter-system handover, if the NG-RAN node receives at least one PDU Session ID included in the *PDU Session Resource Handover List* IE without at least one valid associated GTP tunnel address pair (in either UL or DL), then the NG-RAN node shall consider it as a logical error and act as described in subclause 10.4. A GTP tunnel address pair is considered valid if both the *GTP-TEID* IE and the *Endpoint IP Address* IE are present. + +## 8.4.2 Handover Resource Allocation + +### 8.4.2.1 General + +The purpose of the Handover Resource Allocation procedure is to reserve resources at the target NG-RAN node for the handover of a UE. The procedure uses UE-associated signalling. + +### 8.4.2.2 Successful Operation + +![Diagram illustrating the successful operation of handover resource allocation. It shows a source NG-RAN node (represented by a black rectangle) sending a message to a target NG-RAN node (represented by a white rectangle). The message is indicated by a horizontal arrow pointing from the source to the target. Below each rectangle is a small black horizontal bar representing the base of the node.](c020c072c67473d7823d1f9551942732_img.jpg) + +Diagram illustrating the successful operation of handover resource allocation. It shows a source NG-RAN node (represented by a black rectangle) sending a message to a target NG-RAN node (represented by a white rectangle). The message is indicated by a horizontal arrow pointing from the source to the target. Below each rectangle is a small black horizontal bar representing the base of the node. + +**Figure 8.4.2.2-1: Handover resource allocation: successful operation** + +The AMF initiates the procedure by sending the HANDOVER REQUEST message to the target NG-RAN node. + +If the *Masked IMEISV* IE is contained in the HANDOVER REQUEST message the target NG-RAN node shall, if supported, use it to determine the characteristics of the UE for subsequent handling. + +Upon receipt of the HANDOVER REQUEST message the target NG-RAN node shall + +- attempt to execute the requested PDU session configuration and associated security; +- store the received UE Aggregate Maximum Bit Rate in the UE context, and use the received UE Aggregate Maximum Bit Rate for all Non-GBR QoS flows for the concerned UE as specified in TS 23.501 [9]; +- store the received Mobility Restriction List in the UE context; +- store the received UE Security Capabilities in the UE context; +- store the received Security Context in the UE context and take it into use as defined in TS 33.501 [13]; +- if supported, store the received UE Slice Maximum Bit Rate List in the UE context and use the received UE Slice Maximum Bit Rate List for each S-NSSAI for the concerned UE as specified in TS 23.501 [9]. +- if supported, store the received PDU Set QoS parameters in the UE context and use it as specified in TS 23.501 [9]. + +Upon reception of the *UE History Information* IE, which is included within the *Source to Target Transparent Container* IE of the HANDOVER REQUEST message, the target NG-RAN node shall collect the information defined as mandatory in the *UE History Information* IE and shall, if supported, collect the information defined as optional in the *UE History Information* IE, for as long as the UE stays in one of its cells, and store the collected information to be used for future handover preparations. + +Upon receiving the *PDU Session Resource Setup List* IE contained in the HANDOVER REQUEST message and the HANDOVER REQUEST message does not contain the *No PDU Session Indication* IE, the target NG-RAN node shall behave the same as defined in the PDU Session Resource Setup procedure. The target NG-RAN node shall report to the AMF in the HANDOVER REQUEST ACKNOWLEDGE message the result for each PDU session resource requested to be setup. In particular, for each PDU session resource successfully setup, it shall include the *Handover Request Acknowledge Transfer* IE containing the following information: + +- The list of QoS flows which have been successfully established in the *QoS Flow Setup Response List* IE. +- The *Data Forwarding Accepted* IE if the data forwarding for the QoS flow is accepted. +- The list of QoS flows which have failed to be established, if any, in the *QoS Flow Failed to Setup List* IE. +- The UP transport layer information to be used for the PDU session. +- The security result associated to the PDU session. +- The redundant UP transport layer information to be used for the redundant transmission for the PDU session. +- The PDU Set based Handling Indicator if the HANDOVER REQUEST message includes the *PDU Set QoS Parameters* IE. + +For each PDU session resource which failed to be setup, the *Handover Resource Allocation Unsuccessful Transfer* IE shall be included in the HANDOVER REQUEST ACKNOWLEDGE message containing a cause value that should be precise enough to enable the SMF to know the reason for the unsuccessful establishment. + +For each PDU session included in the HANDOVER REQUEST ACKNOWLEDGE message, if the *Current QoS Parameters Set Index* IE is included for a QoS flow in the *QoS Flow Setup Response List* IE within the *Handover Request Acknowledge Transfer* IE the SMF shall consider it as the currently fulfilled QoS parameters set among the alternative QoS parameters for the involved QoS flow. + +Upon reception of the HANDOVER REQUEST ACKNOWLEDGE message the AMF shall, for each PDU session indicated in the *PDU Session ID* IE, transfer transparently the *Handover Request Acknowledge Transfer* IE or *Handover Resource Allocation Unsuccessful Transfer* IE to the SMF associated with the concerned PDU session. + +If the HANDOVER REQUEST message contains the *Data Forwarding Not Possible* IE associated with a given PDU session within the *Handover Request Transfer* IE set to "data forwarding not possible", the target NG-RAN node may not include the *DL Forwarding UP TNL Information* IE and for intra-system handover the *Data Forwarding Response DRB List* IE within the *Handover Request Acknowledge Transfer* IE in the HANDOVER REQUEST ACKNOWLEDGE message for that PDU session. + +If the HANDOVER REQUEST message contains the *Redundant PDU Session Information* IE associated with a given PDU session within the *Handover Request Transfer* IE, the target NG-RAN node shall, if supported, store the received information in the UE context and use it for redundant PDU session setup as specified in TS38.300 [8] and TS 23.501 [9]. If the *PDU Session Type* IE is set to "ethernet" and the redundancy requirement is fulfilled using a secondary NG-RAN node, the NG-RAN node shall, if supported, include the *Global RAN Node ID of Secondary NG-RAN Node* IE in the *Handover Request Acknowledge Transfer* IE of the HANDOVER REQUEST ACKNOWLEDGE message. If the *PDU Session Pair ID* IE is included in the *Redundant PDU Session Information* IE, the NG-RAN node may use it to identify the paired PDU sessions. + +For each PDU session for which the *Global RAN Node ID of Secondary NG-RAN Node* IE is included in the *Handover Request Acknowledge Transfer* IE of the HANDOVER REQUEST ACKNOWLEDGE message, the SMF shall, if supported, handle this information as specified in TS 23.501 [9]. + +In case of intra-system handover, if the target NG-RAN node accepts the downlink data forwarding for at least one QoS flow for which the *DL Forwarding* IE is set to "DL forwarding proposed", it may include the *DL Forwarding UP TNL Information* IE in the *Handover Request Acknowledge Transfer* IE as forwarding tunnel for the QoS flows listed in the *QoS Flow Setup Response List* IE of the HANDOVER REQUEST ACKNOWLEDGE message. + +In case of intra-system handover, if the target NG-RAN node accepts the uplink data forwarding for at least one QoS flow for which the *UL Forwarding* IE is set to "UL forwarding proposed", it may include the *UL Forwarding UP TNL Information* IE in the *Handover Request Acknowledge Transfer* IE for the PDU session within the *PDU Session Resource Admitted List* IE of the HANDOVER REQUEST ACKNOWLEDGE message. + +In case of intra-system handover, for each PDU session for which the *Additional DL UP TNL Information for HO List* IE is included in the *Handover Request Acknowledge Transfer* IE of the HANDOVER REQUEST ACKNOWLEDGE message, the SMF shall consider the included *Additional DL NG-U UP TNL Information* IE as the downlink termination point for the associated flows indicated in the *Additional QoS Flow Setup Response List* IE for this PDU session split in different tunnels and shall consider the *Additional DL Forwarding UP TNL Information* IE, if included, as the forwarding tunnel associated to these QoS flows. + +In case of intra-system handover, for each PDU session for which the *Additional UL Forwarding UP TNL Information* IE is included in the *Handover Request Acknowledge Transfer* IE of the HANDOVER REQUEST ACKNOWLEDGE message, the SMF shall consider it as the termination points for the uplink forwarding tunnels for this PDU session split in different tunnels. + +In case of intra-system handover, if the target NG-RAN node accepts the data forwarding for a successfully configured DRB, the target NG-RAN node may include the *DL Forwarding UP TNL Information* IE for the DRB within the *Data Forwarding Response DRB List* IE within *Handover Request Acknowledge Transfer* IE of the HANDOVER REQUEST ACKNOWLEDGE message. + +In case of intra-system handover, if the target NG-RAN node receives the *Direct Forwarding Path Availability* IE set to "direct path available" within the *PDU Session Resource Setup Request Transfer* IE, the target NG-RAN node shall, if supported, assign the UP Transport Layer Information for intra-system direct data forwarding from the appropriate address space, if applicable. + +If the HANDOVER REQUEST ACKNOWLEDGE message contains the *UL Forwarding UP TNL Information* IE for a given DRB in the *Data Forwarding Response DRB List* IE within the *Handover Request Acknowledge Transfer* IE, it indicates the target NG-RAN node has requested the forwarding of uplink data for the DRB. + +In case of inter-system handover from E-UTRAN, if the *PDU Session Resource Setup Request Transfer* IE contains the *Direct Forwarding Path Availability* IE set to "direct path available", the target NG-RAN node shall, if supported, and if it accepts downlink data forwarding for the QoS flows mapped to an E-RAB of an admitted PDU session, include the *DL Forwarding UP TNL Information* IE in the *Data Forwarding Response E-RAB List* IE in the *Handover Request Acknowledge Transfer* IE in the HANDOVER REQUEST ACKNOWLEDGE message for that mapped E-RAB. + +In case of inter-system handover from E-UTRAN, the target NG-RAN node includes the *Data Forwarding Accepted* IE for each QoS flow that the *DL Forwarding* IE is set to "DL forwarding proposed" for the corresponding E-RAB in the *Source NG-RAN Node to Target NG-RAN Node Transparent Container* IE and that the target NG-RAN node has admitted the proposed forwarding of downlink data for the QoS flow. If indirect data forwarding is applied for inter-system handover, if the target NG-RAN node accepts the downlink data forwarding for at least one QoS flow of an admitted PDU session it shall include the *DL Forwarding UP TNL Information* IE in the *PDU Session Resource Setup Response Transfer* IE for that PDU session within the *PDU Session Resources Admitted List* IE of the HANDOVER REQUEST ACKNOWLEDGE message. + +In case of inter-system handover from E-UTRAN with direct forwarding, if the target NG-RAN node receives the *SgNB UE X2AP ID* IE in the *Source NG-RAN Node to Target NG-RAN Node Transparent Container* IE, it may use it for internal forwarding as described in TS 37.340 [32]. + +In case of inter-system handover from E-UTRAN, if the target cell is a CAG cell, the target NG-RAN node shall include the *NPN Access Information* IE in the HANDOVER REQUEST ACKNOWLEDGE message, and the AMF shall consider that the included information is associated to the target cell and to the UE's serving PLMN identity, and use it as specified in TS 23.501 [9]. + +The target NG-RAN node shall use the information in the *Mobility Restriction List* IE if present in the HANDOVER REQUEST message to + +- determine a target for subsequent mobility action for which the target NG-RAN node provides information about the target of the mobility action towards the UE; +- select a proper SCG during dual connectivity operation; + +- assign proper RNA(s) for the UE when moving the UE to RRC\_INACTIVE state. + +If the *Mobility Restriction List* IE is not contained in the HANDOVER REQUEST message, the target NG-RAN node shall consider that no roaming and no access restriction apply to the UE except for the PNI NPN mobility as described in TS 23.501 [9]. The target NG-RAN node shall also consider that no roaming and no access restriction apply to the UE when: + +- one of the QoS flows includes a particular ARP value (TS 23.501 [9]). + +The NG-RAN node shall consider that roaming or access to CAG cells is only allowed if the *Allowed PNI-NPN List* IE is contained in the HANDOVER REQUEST message, as described in TS 23.501 [9]. + +If the *Trace Activation* IE is included in the HANDOVER REQUEST message the target NG-RAN node shall, if supported, initiate the requested trace function as described in TS 32.422 [11]. In particular, the NG-RAN node 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 [11]; +- if the *Trace Activation* IE includes the *MDT Activation* IE set to "Immediate MDT Only", "Logged MDT only", initiate the requested MDT session as described in TS 32.422 [11] and the target NG-RAN node shall ignore the *Interfaces To Trace* IE and the *Trace Depth* IE; +- if the *Trace Activation* IE includes the *MDT Location Information* IE within the *MDT Configuration* IE, store this information and take it into account in the requested MDT session; +- if the *Trace Activation* IE includes the *Signalling Based MDT PLMN List* IE within the *MDT Configuration* IE, the NG-RAN node may use it to propagate the MDT Configuration as described in TS 37.320 [41]. +- if the *Trace Activation* IE includes the *Bluetooth Measurement Configuration* IE within the *MDT Configuration* IE, take it into account for MDT Configuration as described in TS 37.320 [41]. +- if the *Trace Activation* IE includes the *WLAN Measurement Configuration* IE within the *MDT Configuration* IE, take it into account for MDT Configuration as described in TS 37.320 [41]. +- if the *Trace Activation* IE includes the *Sensor Measurement Configuration* IE within the *MDT Configuration* IE, take it into account for MDT Configuration as described in TS 37.320 [41]. +- if the *Trace Activation* IE includes the *MDT Configuration* IE and if the NG-RAN node is a gNB at least the *MDT Configuration-NR* IE shall be present, while if the NG-RAN node is an ng-eNB at least the *MDT Configuration-EUTRA* IE shall be present. + +If the *Location Reporting Request Type* IE is included in the HANDOVER REQUEST message, the target NG-RAN node should perform the requested location reporting functionality for the UE as described in subclause 8.12. + +If the *Core Network Assistance Information for RRC INACTIVE* IE is included in the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, store this information in the UE context and use it for the RRC\_INACTIVE state decision and RNA configuration for the UE and RAN paging if any for a UE in RRC\_INACTIVE state, as specified in TS 38.300 [8]. If the *MICO All PLMN* IE is included in the *Core Network Assistance Information for RRC INACTIVE* IE the NG-RAN node shall, if supported, consider that the registration area for the UE is the full PLMN and ignore the *TAI List for RRC Inactive* IE. If the *Paging Cause Indication for Voice Service* IE is included in the *Core Network Assistance Information for RRC INACTIVE* IE, the NG-RAN node shall, if supported, store and use it as specified in TS 38.300 [8]. If the *PEIPS Assistance Information* IE is included in the *Core Network Assistance Information for RRC INACTIVE* IE, the NG-RAN node shall, if supported, store it and use it for paging subgrouping the UE in RRC\_INACTIVE state, as specified in TS 38.300 [8]. If the *CN MT Communication Handling* IE is included in the *Core Network Assistance Information for RRC INACTIVE* IE, the NG-RAN node shall, if supported, store it and may subsequently request, based on implementation, the CN for mobile terminated communication handling as described in TS 23.502 [10]. + +If the *CN Assisted RAN Parameters Tuning* IE is included in the HANDOVER REQUEST message, the NG-RAN node may use it as described in TS 23.501 [9]. + +If the *New Security Context Indicator* IE is included in the HANDOVER REQUEST message, the target NG-RAN node shall use the information as specified in TS 33.501 [13]. + +If the *NASC* IE is included in the HANDOVER REQUEST message, the target NG-RAN node shall use it towards the UE as specified in TS 33.501 [13]. + +If the *RRC Inactive Transition Report Request* IE is included in the HANDOVER REQUEST message, the NG-RAN node shall, if supported, store this information in the UE context. + +If the *Redirection for Voice EPS Fallback* IE is included in the HANDOVER REQUEST message, the NG-RAN node shall, if supported, store it and use it in a subsequent decision of EPS fallback for voice as specified in TS 23.502 [10]. + +If the *SRVCC Operation Possible* IE is included in the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, store the content of the received *SRVCC Operation Possible* IE in the UE context and use it as defined in TS 23.216 [31]. + +If the *IAB Authorized* IE is contained in the HANDOVER REQUEST message, the NG-RAN node shall, if supported, consider that the handover is for an IAB node. + +If the *Mobile IAB Authorized* IE is contained in the HANDOVER REQUEST message, the NG-RAN node shall, if supported, consider that the handover is for a mobile IAB-node. In addition, if the *No PDU Session Indication* IE is contained in the HANDOVER REQUEST message, the NG-RAN node shall, if supported, consider the mobile IAB-MT does not have any PDU sessions activated, ignore the *PDU Session Resource Setup List* IE, and it shall not take any action with respect to PDU session setup. + +If the *Enhanced Coverage Restriction* IE is included in the HANDOVER REQUEST message, the NG-RAN node shall, if supported, store this information in the UE context and use it as defined in TS 23.501 [9]. + +If the *UE Differentiation Information* IE is included in the HANDOVER REQUEST message, the NG-RAN node shall, if supported, store this information in the UE context for further use according to TS 23.501 [9]. + +If the *UE User Plane CIoT Support Indicator* IE is included in the HANDOVER REQUEST message the NG-RAN node shall, if supported, store this information in the UE context and consider that User Plane CIoT 5GS Optimisation as specified in TS 23.501 [9] is supported for the UE. + +Upon reception of the *UE History Information from UE* IE, which is included within the *Source to Target Transparent Container* IE of the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, store the collected information and use it for future handover preparations. + +After all necessary resources for the admitted PDU session resources have been allocated, the target NG-RAN node shall generate the HANDOVER REQUEST ACKNOWLEDGE message. + +If the *RedCap Indication* IE is included in the HANDOVER REQUEST ACKNOWLEDGE message, the AMF shall, if supported, consider the UE as a RedCap UE that was previously served by a E-UTRA cell, and use the IE according to TS 23.501 [9]. + +For each QoS flow which has been established in the target NG-RAN node, if the *QoS Monitoring Request* IE was included in the *QoS Flow Level QoS Parameters* IE contained in the HANDOVER REQUEST message, the target NG-RAN node shall store this information, and, if supported, perform delay measurement and QoS monitoring, as specified in TS 23.501 [9]. If the *QoS Monitoring Reporting Frequency* IE was included in the *QoS Flow Level QoS Parameters* IE contained in the HANDOVER REQUEST message, the target NG-RAN node shall store this information and, if supported, use it for RAN part delay reporting. + +If the *NR V2X Services Authorized* IE is contained in the HANDOVER REQUEST message and it contains one or more IEs set to "authorized", the NG-RAN 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 HANDOVER REQUEST message and it contains one or more IEs set to "authorized", the NG-RAN node shall, if supported, consider that the UE is authorized for the relevant service(s). + +If the *NR A2X Services Authorized* IE is contained in the HANDOVER REQUEST message and it contains one or more IEs set to "authorized", the NG-RAN 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 HANDOVER REQUEST message and it contains one or more IEs set to "authorized", the NG-RAN 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 included in the HANDOVER REQUEST message, the NG-RAN node shall, if supported, use the received value 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 included in the HANDOVER REQUEST message, the NG-RAN node shall, if supported, use the received value for the concerned UE's sidelink communication in network scheduled mode for LTE V2X services. + +If the *NR A2X UE PC5Aggregate Maximum Bit Rate* IE is included in the HANDOVER REQUEST message, the NG-RAN node shall, if supported, use the received value for the concerned UE's sidelink communication in network scheduled mode for NR A2X services. + +If the *LTE A2X UE PC5 Aggregate Maximum Bit Rate* IE is included in the HANDOVER REQUEST message, the NG-RAN node shall, if supported, use the received value for the concerned UE's sidelink communication in network scheduled mode for LTE A2X services. + +If the *PC5 QoS Parameters* IE is included in the HANDOVER REQUEST message, the NG-RAN node shall, if supported, use it as defined in TS 23.287 [33]. + +If the *A2X PC5 QoS Parameters* IE is included in the HANDOVER REQUEST message, the NG-RAN node shall, if supported, use it as defined in TS 23.256 [54]. + +If the *CE-mode-B Restricted* IE is included in the HANDOVER REQUEST message and the *Enhanced Coverage Restriction* IE is not set to "restricted" and the Enhanced Coverage Restriction information stored in the UE context is not set to "restricted", the NG-RAN node shall, if supported, store this information in the UE context and use it as defined in TS 23.501 [9]. + +If the *Management Based MDT PLMN List* IE is contained in the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, store the received information in the UE context, and use this information to allow subsequent selections of the UE for management based MDT defined in TS 32.422 [11]. + +If the HANDOVER REQUEST message contains the *UE Radio Capability ID* IE, the NG-RAN node shall, if supported, use it as specified in TS 23.501 [9] and TS 23.502 [10]. + +If the *DAPS Request Information* IE is included for a DRB in the *Source NG-RAN Node to Target NG-RAN Node Transparent Container* IE within the HANDOVER REQUEST message, the target NG-RAN node shall consider that the request concerns a DAPS Handover for that DRB, as described in TS 38.300 [8]. The target NG-RAN node shall include the *DAPS Response information List* IE in the *Target NG-RAN Node to Source NG-RAN Node Transparent Container* IE within the HANDOVER REQUEST ACKNOWLEDGE message, containing the *DAPS Response Information* IE for each DRB requested to be configured with DAPS Handover. + +If the *Extended Connected Time* IE is included in the HANDOVER REQUEST message, the NG-RAN node shall, if supported, use it as described in TS 23.501 [9]. + +If the target NG-RAN node receives the *UE Context Reference at Source* IE in the *Source NG-RAN Node to Target NG-RAN Node Transparent Container* IE within the HANDOVER REQUEST message, it may use it to identify an existing UE. + +If the *Source Node ID* IE is included in the *Source NG-RAN Node to Target NG-RAN Node Transparent Container* IE within the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, use it to decide whether direct forwarding path is available between the target NG-RAN node and this source RAN node. If the direct forwarding path is available, the target NG-RAN node shall include the *Direct Forwarding Path Availability* IE in the *Target NG-RAN Node to Source NG-RAN Node Transparent Container* IE within the HANDOVER REQUEST ACKNOWLEDGE message. + +In case there are MBS sessions the UE has joined, for all the MBS sessions the UE has joined, the SMF shall, if supported, include the *MBS Session Setup Request List* IE within the *PDU Session Resource Setup Request Transfer* IE in the HANDOVER REQUEST message. + +If the HANDOVER REQUEST message contains the *MBS Session Setup Request List* IE in a *PDU Session Resource Setup Request Transfer* IE the NG-RAN node shall, if supported, use it as specified in TS 23.247 [44] and TS 38.300 [8]. + +If the *MBS Active Session Information Source to Target List* IE is contained in the *Source NG-RAN Node to Target NG-RAN Node Transparent Container* IE within the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, assume the indicated MBS sessions to be active and establish MBS session resources as specified in TS 23.247 [44] and TS 38.300 [8], if applicable. The target NG-RAN node shall, if supported, consider that the MBS sessions the UE has joined which are not included in the *MBS Active Session Information Source to Target List* IE are inactive. + +If the *MBS Area Session ID* IE is included in the *MBS Active Session Information Source to Target List* IE in the *Source NG-RAN Node to Target NG-RAN Node Transparent Container* IE within the HANDOVER REQUEST message, the target NG-RAN shall use this information as indication from which MBS Area Session ID the UE is handed over. + +If the *MBS Service Area* IE is included in the *MBS Active Session Information Source to Target List* IE in the *Source NG-RAN Node to Target NG-RAN Node Transparent Container* IE within the HANDOVER REQUEST message, the target NG-RAN shall use this information to setup respective MBS session resources, if applicable. + +If the target NG-RAN node decides to allocate resource for data forwarding for an active MBS session, respective information is provided for that MBS session within the *Data Forwarding Response MRB List* IE in the *MBS Active Session Information Target to Source List* IE in the *Target NG-RAN Node to Source NG-RAN Node Transparent Container* IE. + +If the *Time Synchronisation Assistance Information* IE is included in the HANDOVER REQUEST message, the NG-RAN node shall, if supported, store the information in the UE context and use it as defined in TS 23.501 [9]. + +If the *5G ProSe Authorized* IE is contained in the HANDOVER REQUEST message and it contains one or more IEs set to "authorized", the NG-RAN 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 included in the HANDOVER REQUEST message, the NG-RAN node shall, if supported, use the received value for the concerned UE's sidelink communication in network scheduled mode for 5G ProSe services. + +If the *5G ProSe PC5 QoS Parameters* IE is included in the HANDOVER REQUEST message, the NG-RAN node shall, if supported, use it as defined in TS 23.304 [47]. + +If for a given QoS flow the *Source Transport Layer Address* IE is included within the *Source NG-RAN Node to Target NG-RAN Node Transparent Container* IE of the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, store this information and use it as part of its ACL functionality configuration actions for direct data + +forwarding, if such ACL functionality is deployed and if direct forwarding path is available between the target NG-RAN node and this source RAN node. + +If for a given QoS flow the *Source Node Transport Layer Address* IE is included within the *Source NG-RAN Node to Target NG-RAN Node Transparent Container* IE of the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, store this information and use it as part of its ACL functionality configuration actions for direct data forwarding, if such ACL functionality is deployed and if direct forwarding path is available between the target NG-RAN node and this source RAN node. + +If for a given E-RAB the *Source Transport Layer Address* IE is included within the *Source NG-RAN Node to Target NG-RAN Node Transparent Container* IE of the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, store this information and use it as part of its ACL functionality configuration actions for direct data forwarding, if such ACL functionality is deployed and if direct forwarding path is available between the target NG-RAN node and this source RAN node. + +If for a given E-RAB the *Source Node Transport Layer Address* IE is included within the *Source NG-RAN Node to Target NG-RAN Node Transparent Container* IE of the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, store this information and use it as part of its ACL functionality configuration actions for direct data forwarding, if such ACL functionality is deployed and if direct forwarding path is available between the target NG-RAN node and this source RAN node. + +If the HANDOVER REQUEST message contains within the *Source NG-RAN Node to Target NG-RAN Node Transparent Container* IE the *NGAP IE Support Information Request List* IE, the target NG-RAN node shall, if supported and the target NG-RAN node accepts the request for handover, for each included NGAP Protocol IE-Id provided within the *Target NG-RAN Node to Source NG-RAN Node Transparent Container* IE in the HANDOVER REQUEST ACKNOWLEDGE message + +- set the *NGAP Protocol IE Support Information* IE to "supported" if the target NG-RAN node has information that the functionality associated with the indicated IE is supported +- set the *NGAP Protocol IE Support Information* IE to "not-supported" if the target NG-RAN node has information that the functionality associated with the indicated IE is not supported + +on the interface instance via which the HANDOVER REQUEST message has been received, and + +- set the *NGAP Protocol IE Presence Information* IE to "present" if the target NG-RAN node has received the respective NGAP Protocol IE-Id in the HANDOVER REQUEST message, and "not-present" otherwise. + +If the HANDOVER REQUEST message contains within the *Source NG-RAN Node to Target NG-RAN Node Transparent Container* IE the *Time Based Handover Information* IE, the target NG-RAN node may use this information to allocate necessary resources for the incoming handover. + +If the *Candidate Relay UE Information List* IE is included in the *Source NG-RAN Node to Target NG-RAN Node Transparent Container* IE within the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, use it to configure the path switch to indirect path as specified in TS 38.300 [8]. + +If the *Aerial UE Subscription Information* IE is included in the HANDOVER REQUEST message, the NG-RAN node shall, if supported, store this information in the UE context and use it as defined in TS 38.300 [8]. + +If the *PNI-NPN Area Scope of MDT* IE is included in the *MDT Configuration-NR* IE included in the HANDOVER REQUEST message, the NG-RAN node shall, if supported, use it to derive the MDT area scope for MDT measurement collection in PNI-NPN areas. Upon reception of the *PNI-NPN Area Scope of MDT* IE, the NG-RAN node shall consider that the area scope for MDT measurement collection in PNI-NPN areas is defined only by the areas included in the *PNI-NPN Area Scope of MDT* IE. + +If the *Partially Allowed NSSAI* IE is contained in the HANDOVER REQUEST message, the NG-RAN node shall, if supported, deduce from it the partially allowed network slices for the UE, store and replace any previously received Partially Allowed NSSAI and use it as specified in TS 23.501 [9]. + +#### Interactions with RRC Inactive Transition Report procedure: + +If the *RRC Inactive Transition Report Request* IE is included in the HANDOVER REQUEST message and set to "subsequent state transition report", the NG-RAN node shall, if supported, send the RRC INACTIVE TRANSITION REPORT message to the AMF to report the RRC state of the UE when the UE enters or leaves RRC\_INACTIVE state. + +### 8.4.2.3 Unsuccessful Operation + +![Sequence diagram illustrating an unsuccessful handover resource allocation. A Source NG-RAN node (represented by a black rectangle) sends a HANDOVER REQUEST message (represented by a horizontal arrow) to a Target NG-RAN node (represented by a black rectangle). The Target NG-RAN node responds with a HANDOVER FAILURE message (represented by a horizontal arrow pointing back to the Source NG-RAN node).](09036266c6dba47efb2613ceaebe2b19_img.jpg) + +Sequence diagram illustrating an unsuccessful handover resource allocation. A Source NG-RAN node (represented by a black rectangle) sends a HANDOVER REQUEST message (represented by a horizontal arrow) to a Target NG-RAN node (represented by a black rectangle). The Target NG-RAN node responds with a HANDOVER FAILURE message (represented by a horizontal arrow pointing back to the Source NG-RAN node). + +**Figure 8.4.2.3-1: Handover resource allocation: unsuccessful operation** + +If the target NG-RAN node does not admit any of the PDU session resources, or a failure occurs during the Handover Preparation, it shall send the HANDOVER FAILURE message to the AMF with an appropriate cause value. + +If the HANDOVER REQUEST message contains within the *Source NG-RAN Node to Target NG-RAN Node Transparent Container* IE the *NGAP IE Support Information Request List* IE, the target NG-RAN node shall, if supported and the target NG-RAN node does not accept the request for handover, for each included NGAP Protocol IE-Id provided within the *Target NG-RAN Node to Source NG-RAN Node Failure Transparent Container* IE in the HANDOVER FAILURE message + +- set the *NGAP Protocol IE Support Information* IE to "supported" if the target NG-RAN node has information that the functionality associated with the indicated IE is supported +- set the *NGAP Protocol IE Support Information* IE to "not-supported" if the target NG-RAN node has information that the functionality associated with the indicated IE is not supported + +on the interface instance via which the HANDOVER REQUEST message has been received, and + +- set the *NGAP Protocol IE Presence Information* IE to "present" if the target NG-RAN node has received the respective NGAP Protocol IE-Id in the HANDOVER REQUEST message, and "not-present" otherwise. + +### 8.4.2.4 Abnormal Conditions + +If the supported algorithms for encryption defined in the *Encryption Algorithms* IE in the *UE Security Capabilities* IE, plus the mandated support of EEA0 and NEA0 in all UEs (TS 33.501 [13]), do not match any allowed algorithms defined in the configured list of allowed encryption algorithms in the NG-RAN node (TS 33.501 [13]), the target NG-RAN node shall reject the procedure using the HANDOVER FAILURE message. + +If the supported algorithms for integrity defined in the *Integrity Protection Algorithms* IE in the *UE Security Capabilities* IE, plus the mandated support of the EIA0 and NIA0 algorithm in all UEs (TS 33.501 [13]), do not match any allowed algorithms defined in the configured list of allowed integrity protection algorithms in the NG-RAN node (TS 33.501 [13]), the target NG-RAN node shall reject the procedure using the HANDOVER FAILURE message. + +If the target NG-RAN node receives a HANDOVER REQUEST message which does not contain the *Mobility Restriction List* IE, and the serving PLMN cannot be determined otherwise by the NG-RAN node, the target NG-RAN node shall reject the procedure using the HANDOVER FAILURE message. + +If the target NG-RAN node receives a HANDOVER REQUEST message containing the *Mobility Restriction List* IE, and the serving PLMN indicated is not supported by the target cell, the target NG-RAN node shall reject the procedure using the HANDOVER FAILURE message. + +If the target NG-RAN node receives a HANDOVER REQUEST message containing an *Allowed PNI-NPN List* IE in the *Mobility Restriction List* IE which does not allow access to the cell indicated in the *Target Cell ID* IE, the target NG-RAN node shall reject the procedure using the HANDOVER FAILURE message with an appropriate cause value and may include the *Cell CAG Information* IE corresponding to this cell and the selected PLMN. + +If the target NG-RAN node receives a HANDOVER REQUEST message containing a *Serving PLMN* IE and *Serving NID* IE in the *Mobility Restriction List* IE which does not allow access to the cell indicated in the *Target Cell ID* IE, the target NG-RAN node shall reject the procedure using the HANDOVER FAILURE message with an appropriate cause value. + +If both the *PNI-NPN Area Scope of MDT* IE and the *Area Scope of MDT* IE are included in the *MDT Configuration-NR* IE in the HANDOVER REQUEST message, and the *Area Scope of MDT* IE is set to "PNI-NPN based", the NG-RAN node shall, if supported, use it to derive the MDT area scope for MDT measurement collection in PNI-NPN areas, and ignore the *PNI-NPN Area Scope of MDT* IE. + +If the *Partially Allowed NSSAI* IE is received in the HANDOVER REQUEST message and the total number of S-NSSAIs included in the Allowed NSSAI and Partially Allowed NSSAI exceeds eight, the NG-RAN node shall consider the procedure as failed. + +If any of the S-NSSAI which is present in the *Partially Allowed NSSAI* IE is also present in the *Allowed NSSAI* IE, the NG-RAN node shall consider the procedure as failed. + +## 8.4.3 Handover Notification + +### 8.4.3.1 General + +The purpose of the Handover Notification procedure is to indicate to the AMF that the UE has arrived to the target cell and the NG-based handover has been successfully completed. The procedure uses UE-associated signalling. + +### 8.4.3.2 Successful Operation + +![Sequence diagram for Handover notification. A target NG-RAN node (represented by a black rectangle) sends a HANDOVER NOTIFY message (represented by a horizontal arrow) to the AMF (represented by a vertical line at the bottom).](58e07d355a649f1fbd8a041b88207829_img.jpg) + +The diagram illustrates the successful operation of the Handover Notification procedure. It shows a target NG-RAN node, represented by a large black rectangle with a white rectangular area in its top right corner. Below this rectangle, a vertical line extends downwards to a short horizontal bar, representing the AMF. A horizontal arrow points from the target NG-RAN node to the AMF, indicating the transmission of the HANDOVER NOTIFY message. + +Sequence diagram for Handover notification. A target NG-RAN node (represented by a black rectangle) sends a HANDOVER NOTIFY message (represented by a horizontal arrow) to the AMF (represented by a vertical line at the bottom). + +Figure 8.4.3.2-1: Handover notification + +The target NG-RAN node shall send the HANDOVER NOTIFY message to the AMF when the UE has been identified in the target cell and the NG-based handover has been successfully completed. + +#### Interactions with Handover Success procedure: + +If the *Notify Source NG-RAN Node* IE is included in the HANDOVER NOTIFY message, the AMF shall, if supported, notify the source NG-RAN node that the UE has successfully accessed the target NG-RAN node by sending the HANDOVER SUCCESS message. + +### 8.4.3.3 Abnormal Conditions + +Void. + +## 8.4.4 Path Switch Request + +### 8.4.4.1 General + +The purpose of the Path Switch Request procedure is to establish a UE associated signalling connection to the 5GC and, if applicable, to request the switch of the downlink termination point of the NG-U transport bearer towards a new termination point. The procedure uses UE-associated signalling. + +### 8.4.4.2 Successful Operation + +![Diagram illustrating the successful operation of a Path Switch Request. It shows a large black rectangle representing the 5GC (5G Core) and two smaller black rectangles representing NG-RAN nodes. A horizontal arrow points from the right NG-RAN node to the 5GC, indicating the Path Switch Request message. A return arrow points from the 5GC to the left NG-RAN node, indicating the Path Switch Request Acknowledge message.](c78f017dab5586c098c5d7c6a8f1d432_img.jpg) + +Diagram illustrating the successful operation of a Path Switch Request. It shows a large black rectangle representing the 5GC (5G Core) and two smaller black rectangles representing NG-RAN nodes. A horizontal arrow points from the right NG-RAN node to the 5GC, indicating the Path Switch Request message. A return arrow points from the 5GC to the left NG-RAN node, indicating the Path Switch Request Acknowledge message. + +**Figure 8.4.4.2-1: Path switch request: successful operation** + +The NG-RAN node initiates the procedure by sending the PATH SWITCH REQUEST message to the AMF. Upon reception of the PATH SWITCH REQUEST message the AMF shall, for each PDU session indicated in the *PDU Session ID* IE, transparently transfer the *Path Switch Request Transfer* IE to the SMF associated with the concerned PDU session. + +If the *RRC Resume Cause* IE is included in the PATH SWITCH REQUEST message, the AMF shall, if supported, use it as described in TS 23.502 [10] for User Plane CIoT 5GS Optimisation when the NG-RAN node is an ng-eNB. + +If the *RedCap Indication* IE is included in the PATH SWITCH REQUEST message, the AMF shall, if supported, consider the UE as a RedCap UE that was previously served by a E-UTRA cell, and use the IE according to TS 23.501 [9]. + +After all necessary updates including the UP path switch have been successfully completed in the 5GC for at least one of the PDU session resources included in the PATH SWITCH REQUEST, the AMF shall send the PATH SWITCH REQUEST ACKNOWLEDGE message to the NG-RAN node and the procedure ends. + +The list of accepted QoS flows shall be included in the PATH SWITCH REQUEST message within the *Path Switch Request Transfer* IE. The SMF shall handle this information as specified in TS 23.502 [10]. + +For each PDU session for which the *Additional DL QoS Flow per TNL Information* IE is included in the *Path Switch Request Transfer* IE of the PATH SWITCH REQUEST message, the SMF may use each included UP transport layer information as the downlink termination point for the included associated QoS flows for this PDU session split in different tunnels. + +The list of PDU sessions which failed to be setup, if any, shall be included in the PATH SWITCH REQUEST message within the *Path Switch Request Setup Failed Transfer* IE. The AMF shall handle this information as specified in TS 23.502 [10]. + +For each PDU session for which the *User Plane Security Information* IE is included in the *Path Switch Request Transfer* IE of the PATH SWITCH REQUEST message, the SMF shall behave as specified in TS 33.501 [13] and may send back the *Security Indication* IE within the *Path Switch Request Acknowledge Transfer* IE of the PATH SWITCH REQUEST ACKNOWLEDGE message. + +For each PDU session for which the *DL NG-U TNL Information Reused* IE set to "true" is included in the *Path Switch Request Transfer* IE of the PATH SWITCH REQUEST message, the SMF shall, if supported, consider that the DL TNL information contained in the *DL NG-U UP TNL Information* IE has been reused. + +For each PDU session for which the *Additional Redundant DL QoS Flow per TNL Information* IE is included in the *Path Switch Request Transfer* IE of the PATH SWITCH REQUEST message, the SMF may use each included UP transport layer information as the downlink termination point for the included associated QoS flows for this PDU session split in different tunnels for the redundant transmission. + +For each PDU session for which the *Redundant DL NG-U TNL Information Reused* IE is included in the *Path Switch Request Transfer* IE of the PATH SWITCH REQUEST message, the SMF shall, if supported, consider the included DL transport layer address as the DL transport layer address for the redundant transmission as specified in TS 23.501 [9]. + +For each PDU session for which the *Global RAN Node ID of Secondary NG-RAN Node* IE is included in the *Path Switch Request Transfer* IE of the PATH SWITCH REQUEST message, the SMF shall, if supported, handle this information as specified in TS 23.501 [9]. + +For each PDU session included in the PATH SWITCH REQUEST message, if the *Current QoS Parameters Set Index* IE is included in the *Path Switch Request Transfer* IE the SMF shall consider it as the currently fulfilled QoS parameters set among the alternative QoS parameters for the involved QoS flow. + +The NG-RAN node shall, if supported, report in the PATH SWITCH REQUEST message the *PDU Set based Handling Indicator* IE in the *Path Switch Request Transfer* IE. If the *PDU Set based Handling Indicator* IE is included in the *Path Switch Request Transfer* IE in the PATH SWITCH REQUEST message, the SMF shall, if supported, handle this information as specified in TS 23.501 [9]. + +If the *Security Indication* IE is included within the *Path Switch Request Acknowledge Transfer* IE of the PATH SWITCH REQUEST ACKNOWLEDGE message, the NG-RAN node shall behave as specified in TS 33.501 [13]. + +If the *UL NG-U UP TNL Information* IE is included within the *Path Switch Request Acknowledge Transfer* IE of the PATH SWITCH REQUEST ACKNOWLEDGE message, the NG-RAN node shall store this information and use it as the uplink termination point for the user plane data for this PDU session. + +If the *Additional NG-U UP TNL Information* IE is included within the *Path Switch Request Acknowledge Transfer* IE of the PATH SWITCH REQUEST ACKNOWLEDGE message, the NG-RAN node shall store this information and use the included *UL NG-U UP TNL Information* IE(s) as the uplink termination point(s) of the user plane data for this PDU session split in different tunnel. + +If the *Redundant UL NG-U UP TNL Information* IE is included within the *Path Switch Request Acknowledge Transfer* IE of the PATH SWITCH REQUEST ACKNOWLEDGE message, the NG-RAN node shall, if supported, store this information and use it as the uplink termination point for the user plane data for the redundant transmission for this PDU session as specified in TS 23.501 [9]. + +If the *Additional Redundant NG-U UP TNL Information* IE is included within the *Path Switch Request Acknowledge Transfer* IE of the PATH SWITCH REQUEST ACKNOWLEDGE message, the NG-RAN node shall, if supported, store this information and use the included *UL NG-U UP TNL Information* IE(s) as the uplink termination point(s) of the user plane data for this PDU session split in different tunnel. + +If the *CN Packet Delay Budget Downlink* IE is included within the *Path Switch Request Acknowledge Transfer* IE of the PATH SWITCH REQUEST ACKNOWLEDGE message, the NG-RAN node shall, if supported, replace the previously provided CN Packet Delay Budget Downlink if any and use it as specified in TS 23.502 [10]. + +If the *CN Packet Delay Budget Uplink* IE is included within the *Path Switch Request Acknowledge Transfer* IE of the PATH SWITCH REQUEST ACKNOWLEDGE message, the NG-RAN node shall, if supported, replace the previously provided CN Packet Delay Budget Uplink if any and use it as specified in TS 23.502 [10]. + +If the *Burst Arrival Time Downlink* IE is included within the *Path Switch Request Acknowledge Transfer* IE of the PATH SWITCH REQUEST ACKNOWLEDGE message, the NG-RAN node shall, if supported, replace the previously provided value if any and use it as specified in TS 23.502 [10]. + +If the *Core Network Assistance Information for RRC INACTIVE* IE is included in the PATH SWITCH REQUEST ACKNOWLEDGE message, the NG-RAN node shall, if supported, store this information in the UE context and use it for the RRC\_INACTIVE state decision and RNA configuration for the UE and RAN paging if any for a UE in RRC\_INACTIVE state, as specified in TS 38.300 [8]. If the *MICO All PLMN* IE is included in the *Core Network Assistance Information for RRC INACTIVE* IE the NG-RAN node shall, if supported, consider that the registration area for the UE is the full PLMN and ignore the *TAI List for RRC Inactive* IE. If the *Paging Cause Indication for Voice Service* IE is included in the *Core Network Assistance Information for RRC INACTIVE* IE, the NG-RAN node shall, if supported, store and use it as specified in TS 38.300 [8]. If the *PEIPS Assistance Information* IE is included in the *Core Network Assistance Information for RRC INACTIVE* IE, the NG-RAN node shall, if supported, store it and use it for paging subgrouping the UE in RRC\_INACTIVE state, as specified in TS 38.300 [8]. If the *CN MT Communication Handling* IE is included in the *Core Network Assistance Information for RRC INACTIVE* IE, the NG-RAN node shall, if supported, store it and may subsequently request, based on implementation, the CN for mobile terminated communication handling as described in TS 23.502 [10]. + +If the *CN Assisted RAN Parameters Tuning* IE is included in the PATH SWITCH REQUEST ACKNOWLEDGE message, the NG-RAN node may use it as described in TS 23.501 [9]. + +If the *RRC Inactive Transition Report Request* IE is included in the PATH SWITCH REQUEST ACKNOWLEDGE message, the NG-RAN node shall, if supported, store this information in the UE context. + +If the *New Security Context Indicator* IE is included in the PATH SWITCH REQUEST ACKNOWLEDGE message, the NG-RAN node shall use the information as specified in TS 33.501 [13]. + +Upon reception of the PATH SWITCH REQUEST ACKNOWLEDGE message the NG-RAN node shall store the received *Security Context* IE in the UE context and the NG-RAN node shall use it as specified in TS 33.501 [13]. + +If the *UE Security Capabilities* IE is included in the PATH SWITCH REQUEST ACKNOWLEDGE message, the NG-RAN node shall handle it accordingly (TS 33.501 [13]). + +If the *Redirection for Voice EPS Fallback* IE is included in the PATH SWITCH REQUEST ACKNOWLEDGE message, the NG-RAN node shall, if supported, store it and use it in a subsequent decision of EPS fallback for voice as specified in TS 23.502 [10]. + +If the *PDU Session Resource Released List* IE is included in the PATH SWITCH REQUEST ACKNOWLEDGE message, the NG-RAN node shall release the corresponding QoS flows and regard the PDU session(s) indicated in the *PDU Session Resource Released List* IE as being released. The appropriate cause value for each PDU session released is included in the *Path Switch Request Unsuccessful Transfer* IE contained in the PATH SWITCH REQUEST ACKNOWLEDGE message. + +If the *SRVCC Operation Possible* IE is included in the PATH SWITCH REQUEST ACKNOWLEDGE message, the NG-RAN node shall, if supported, store the content of the received *SRVCC Operation Possible* IE in the UE context and use it as defined in TS 23.216 [31]. + +If the *Enhanced Coverage Restriction* IE is included in the PATH SWITCH REQUEST ACKNOWLEDGE message, the NG-RAN node shall, if supported, store this information in the UE context and use it as defined in TS 23.501 [9]. + +If the *Extended Connected Time* IE is included in the PATH SWITCH REQUEST ACKNOWLEDGE message, the NG-RAN node shall, if supported, use it as described in TS 23.501 [9]. + +If the *UE Differentiation Information* IE is included in the PATH SWITCH REQUEST ACKNOWLEDGE message, the NG-RAN node shall, if supported, store this information in the UE context for further use according to TS 23.501 [9]. + +If the *NR V2X Services Authorized* IE is contained in the PATH SWITCH REQUEST ACKNOWLEDGE message, the NG-RAN node shall, if supported, update its NR 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 NG-RAN node 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 PATH SWITCH REQUEST ACKNOWLEDGE message, the NG-RAN node shall, if supported, update its LTE 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 NG-RAN node shall, if supported, initiate actions to ensure that the UE is no longer accessing the relevant service(s). + +If the *NR A2X Services Authorized* IE is contained in the PATH SWITCH REQUEST ACKNOWLEDGE message, the NG-RAN node shall, if supported, update its NR 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 NG-RAN node 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 PATH SWITCH REQUEST ACKNOWLEDGE message, the NG-RAN node shall, if supported, update its LTE 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 NG-RAN node shall, if supported, initiate actions to ensure that the UE is no longer accessing the relevant service(s). + +If the *NR UE Sidelink Aggregate Maximum Bit Rate* IE is included in the PATH SWITCH REQUEST ACKNOWLEDGE message, the NG-RAN node shall, if supported: + +- replace the previously provided UE 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 *LTE UE Sidelink Aggregate Maximum Bit Rate* IE is included in the PATH SWITCH REQUEST ACKNOWLEDGE message, the NG-RAN node shall, if supported: + +- replace the previously provided UE 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 A2X UE PC5 Aggregate Maximum Bit Rate* IE is included in the PATH SWITCH REQUEST ACKNOWLEDGE message, the NG-RAN node shall, if supported: + +- replace the previously provided NR A2X 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 NR A2X services. + +If the *LTE A2X UE PC5 Aggregate Maximum Bit Rate* IE is included in the PATH SWITCH REQUEST ACKNOWLEDGE message, the NG-RAN node shall, if supported: + +- replace the previously provided LTE A2X 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 LTE A2X services. + +If the *PC5 QoS Parameters* IE is included in the PATH SWITCH REQUEST ACKNOWLEDGE message, the NG-RAN node shall, if supported, use it as defined in TS 23.287 [33]. + +If the *A2X PC5 QoS Parameters* IE is included in the PATH SWITCH REQUEST ACKNOWLEDGE message, the NG-RAN node shall, if supported, use it as defined in TS 23.256 [54]. + +If the *CE-mode-B Restricted* IE is included in the PATH SWITCH REQUEST ACKNOWLEDGE message and the *Enhanced Coverage Restriction* IE is not set to "restricted" and the Enhanced Coverage Restriction information stored in the UE context is not set to "restricted", the NG-RAN node shall, if supported, store this information in the UE context and use it as defined in TS 23.501 [9]. + +If the *UE User Plane CIoT Support Indicator* IE is included in the PATH SWITCH REQUEST ACKNOWLEDGE message the NG-RAN node shall, if supported, store this information in the UE context and consider that User Plane CIoT 5GS Optimisation as specified in TS 23.501 [9] is supported for the UE. + +If the PATH SWITCH REQUEST ACKNOWLEDGE message contains the *UE Radio Capability ID* IE, the NG-RAN node shall, if supported, use it as specified in TS 23.501 [9] and TS 23.502 [10]. + +If the PATH SWITCH REQUEST ACKNOWLEDGE message contains the *Alternative QoS Parameters Set List* IE, the NG-RAN node shall, if supported, use it as specified in TS 23.502 [10]. + +For each PDU session, if the *PDU Session Expected UE Activity Behaviour* IE is included in the PATH SWITCH REQUEST ACKNOWLEDGE message, the NG-RAN node shall, if supported, handle this information as specified in TS 23.501 [9]. + +If the PATH SWITCH REQUEST ACKNOWLEDGE message contains the *Management Based MDT PLMN List* IE, the NG-RAN node shall store it in the UE context, and if supported, use it to allow subsequent selection of the UE for management based MDT defined in TS 32.422 [11]. + +If the PATH SWITCH REQUEST ACKNOWLEDGE message contains the *Management Based MDT PLMN Modification List* IE, the NG-RAN node shall, if supported, use it to overwrite any previously stored management based MDT PLMN list information in the UE context and use the received information to allow subsequent selection of the UE for management based MDT defined in TS 32.422 [11]. + +If the *Time Synchronisation Assistance Information* IE is included in the PATH SWITCH REQUEST ACKNOWLEDGE message, the NG-RAN node shall, if supported, store the information in the UE context and use it as defined in TS 23.501 [9]. + +If the *5G ProSe Authorized* IE is contained in the PATH SWITCH REQUEST ACKNOWLEDGE message, the NG-RAN node shall, if supported, update its ProSe authorization information for the UE accordingly. If the *5G ProSe Authorized* IE includes one and more IEs set to "not authorized", the NG-RAN node shall, if supported, initiate actions to ensure that the UE is no longer accessing the relevant 5G ProSe service(s). + +If the *5G ProSe UE PC5 Aggregate Maximum Bit Rate* IE is included in the PATH SWITCH REQUEST ACKNOWLEDGE message, the NG-RAN node 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 QoS Parameters* IE is included in the PATH SWITCH REQUEST ACKNOWLEDGE message, the NG-RAN node shall, if supported, use it as defined in TS 23.304 [47]. + +If the *Aerial UE Subscription Information* IE is included in the PATH SWITCH REQUEST ACKNOWLEDGE message, the NG-RAN node shall, if supported, store the information or overwrite any previously stored information in the UE context and use it as defined in TS 38.300 [8]. + +If the *IAB Authorized* IE is contained in the PATH SWITCH REQUEST ACKNOWLEDGE message, the NG-RAN node shall, if supported, store the received IAB Authorization information in the UE context. If the *IAB Authorized* IE is set to "not authorized" for an IAB-MT, the NG-RAN node shall, if supported, initiate actions to ensure that the IAB node will not serve any UE(s). + +If the *Mobile IAB Authorized* IE is included in the PATH SWITCH REQUEST ACKNOWLEDGE message, the NG-RAN node shall, if supported, store the received mobile IAB Authorization status in the UE context of the mobile IAB-MT. If the *Mobile IAB Authorized* IE for a mobile IAB-MT is set to "not authorized", the NG-RAN node shall, if supported, ensure that the mobile IAB-node will not serve any UE(s). + +If the *Partially Allowed NSSAI* IE is contained in the PATH SWITCH REQUEST ACKNOWLEDGE message, the NG-RAN node shall, if supported, deduce from it the partially allowed network slices for the UE, store and replace any previously received Partially Allowed NSSAI and use it as specified in TS 23.501 [9]. + +#### Interactions with RRC Inactive Transition Report procedure: + +If the *RRC Inactive Transition Report Request* IE is included in the PATH SWITCH REQUEST ACKNOWLEDGE message and set to "single RRC connected state report" and the UE is in RRC\_CONNECTED state, the NG-RAN node shall, if supported, send one RRC INACTIVE TRANSITION REPORT message to the AMF to report the RRC state of the UE. + +If the *RRC Inactive Transition Report Request* IE is included in the PATH SWITCH REQUEST ACKNOWLEDGE message and set to "single RRC connected state report" and the UE is in RRC\_INACTIVE state, the NG-RAN node shall, if supported, send to the AMF one RRC INACTIVE TRANSITION REPORT message plus one subsequent RRC INACTIVE TRANSITION REPORT message when the RRC state transitions to RRC\_CONNECTED state. + +If the *RRC Inactive Transition Report Request* IE is included in the PATH SWITCH REQUEST ACKNOWLEDGE message and set to "subsequent state transition report", the NG-RAN node shall, if supported, send one RRC INACTIVE TRANSITION REPORT message to the AMF to report the RRC state of the UE and subsequent RRC INACTIVE TRANSITION REPORT messages to report the RRC state of the UE when the UE enters or leaves RRC\_INACTIVE state. + +#### Interactions with PDU Session Resource Notify procedure: + +If the QoS related parameters (e.g. the *CN Packet Delay Budget Downlink* IE or the *CN Packet Delay Budget Uplink* IE) are included in the *Path Switch Request Acknowledge Transfer* IE of the PATH SWITCH REQUEST ACKNOWLEDGE message, but can not be successfully accepted by the NG-RAN node, the NG-RAN node should continue to use the old values received from the source NG-RAN node, if any. The NG-RAN node shall, if supported, send the PDU SESSION RESOURCE NOTIFY message to notify the AMF. + +### 8.4.4.3 Unsuccessful Operation + +![Sequence diagram illustrating an unsuccessful path switch request operation. The diagram shows two vertical lifelines representing network entities. A message arrow points from the right lifeline to the left lifeline. The left lifeline has a large black rectangular block covering its upper portion, indicating a failure or error state. The right lifeline also has a black rectangular block at its top. The message arrow originates from the right lifeline and points to the left lifeline, but the operation is unsuccessful as indicated by the title and the visual representation of an error state.](8277ec2f29c84d97cbe70bc413a42cd1_img.jpg) + +Sequence diagram illustrating an unsuccessful path switch request operation. The diagram shows two vertical lifelines representing network entities. A message arrow points from the right lifeline to the left lifeline. The left lifeline has a large black rectangular block covering its upper portion, indicating a failure or error state. The right lifeline also has a black rectangular block at its top. The message arrow originates from the right lifeline and points to the left lifeline, but the operation is unsuccessful as indicated by the title and the visual representation of an error state. + +Figure 8.4.4.3-1: Path switch request: unsuccessful operation + +If the 5GC fails to switch the downlink termination point of the NG-U transport bearer towards a new termination point for all PDU session resources, the AMF shall send the PATH SWITCH REQUEST FAILURE message to the NG-RAN node. + +The NG-RAN node shall release the corresponding QoS flows and regard the PDU session(s) indicated in the *PDU Session Resource Released List* IE included in the PATH SWITCH REQUEST FAILURE message as being released. + +The appropriate cause value for each PDU session released is included in the *Path Switch Request Unsuccessful Transfer* IE contained in the PATH SWITCH REQUEST FAILURE message. + +#### 8.4.4.4 Abnormal Conditions + +If the AMF receives a PATH SWITCH REQUEST message containing several *PDU Session ID* IEs (in the *PDU Session Resource to be Switched in Downlink List* IE) set to the same value, the AMF shall send the PATH SWITCH REQUEST FAILURE message to the NG-RAN node. + +NOTE: As an exception, the AMF generates the *Path Switch Request Unsuccessful Transfer* IE. + +If the *Partially Allowed NSSAI* IE is received in the PATH SWITCH REQUEST ACKNOWLEDGE message and the total number of S-NSSAIs included in the Allowed NSSAI and Partially Allowed NSSAI exceeds eight, the NG-RAN node shall consider the procedure as failed. + +If any of the S-NSSAI which is present in the *Partially Allowed NSSAI* IE is also present in the *Allowed NSSAI* IE, the NG-RAN node shall consider the procedure as failed. + +### 8.4.5 Handover Cancellation + +#### 8.4.5.1 General + +The purpose of the Handover Cancellation procedure is to enable a source NG-RAN node to cancel an ongoing handover preparation or an already prepared handover. The procedure uses UE-associated signalling. + +#### 8.4.5.2 Successful Operation + +![Sequence diagram for Handover cancel: successful operation. It shows a source NG-RAN node (represented by a black rectangle) sending a message to the AMF (represented by a white rectangle). The AMF then sends a response message back to the source NG-RAN node. The source NG-RAN node is shown as a large black rectangle with a white rectangle on top right, and the AMF is shown as a smaller black rectangle at the bottom right.](c0ad2ff14abd38f0733a3186353484d2_img.jpg) + +Sequence diagram for Handover cancel: successful operation. It shows a source NG-RAN node (represented by a black rectangle) sending a message to the AMF (represented by a white rectangle). The AMF then sends a response message back to the source NG-RAN node. The source NG-RAN node is shown as a large black rectangle with a white rectangle on top right, and the AMF is shown as a smaller black rectangle at the bottom right. + +Figure 8.4.5.2-1: Handover cancel: successful operation + +The source NG-RAN node initiates the procedure by sending a HANDOVER CANCEL message to the AMF. + +#### 8.4.5.3 Unsuccessful Operation + +Not applicable. + +#### 8.4.5.4 Abnormal Conditions + +If the source NG-RAN node becomes aware of the fact that an expected HANDOVER CANCEL ACKNOWLEDGE message is missing, the source NG-RAN node shall consider the Handover Cancellation procedure as successfully terminated. + +### 8.4.6 Uplink RAN Status Transfer + +#### 8.4.6.1 General + +The purpose of the Uplink RAN Status Transfer procedure is to enable lossless NG-based handover. The procedure uses UE-associated signalling. + +#### 8.4.6.2 Successful Operation + +![Diagram illustrating the Uplink RAN status transfer procedure. A source NG-RAN node (represented by a black rectangle) sends a message (represented by a horizontal arrow) to the AMF (represented by a white rectangle). The AMF then sends a message (represented by a vertical arrow) to the target NG-RAN node (represented by a black rectangle).](9b9dc99e34bb68ec85598e9d4bfda777_img.jpg) + +Diagram illustrating the Uplink RAN status transfer procedure. A source NG-RAN node (represented by a black rectangle) sends a message (represented by a horizontal arrow) to the AMF (represented by a white rectangle). The AMF then sends a message (represented by a vertical arrow) to the target NG-RAN node (represented by a black rectangle). + +**Figure 8.4.6.2-1: Uplink RAN status transfer** + +The source NG-RAN node initiates the procedure by stopping the assigning of PDCP-SNs to downlink SDUs and sending the UPLINK RAN STATUS TRANSFER message to the AMF at the point in time when it considers the transmitter/receiver status to be frozen. + +For each DRB for which PDCP-SN and HFN status preservation applies, the source NG-RAN node shall include the *DRB ID* IE, the *UL COUNT Value* IE and the *DL COUNT Value* IE within the *DRBs Subject to Status Transfer List* IE in the *RAN Status Transfer Transparent Container* IE of the UPLINK RAN STATUS TRANSFER message. + +The source NG-RAN node may also include in the UPLINK RAN STATUS TRANSFER message the missing and the received uplink SDUs in the *Receive Status of UL PDCP SDUs* IE for each DRB for which the source NG-RAN node has accepted the request from the target NG-RAN node for uplink forwarding. + +#### 8.4.6.3 Abnormal Conditions + +Void. + +### 8.4.7 Downlink RAN Status Transfer + +#### 8.4.7.1 General + +The purpose of the Downlink RAN Status Transfer procedure is to enable lossless NG-based handover. The procedure uses UE-associated signalling. + +### 8.4.7.2 Successful Operation + +![Diagram illustrating Downlink RAN status transfer. A large black rectangle represents the target NG-RAN node. Below it, two smaller black rectangles represent the source and target radio interfaces. A horizontal line with an arrow pointing left connects the target interface to the source interface, representing the transfer of status information.](199a8b4c5c620006757a17e930769566_img.jpg) + +Diagram illustrating Downlink RAN status transfer. A large black rectangle represents the target NG-RAN node. Below it, two smaller black rectangles represent the source and target radio interfaces. A horizontal line with an arrow pointing left connects the target interface to the source interface, representing the transfer of status information. + +**Figure 8.4.7.2-1: Downlink RAN status transfer** + +The AMF initiates the procedure by sending the DOWNLINK RAN STATUS TRANSFER message to the target NG-RAN node. The target NG-RAN node using Full Configuration for this handover as per TS 38.300 [8] shall ignore the information received in this message. + +For each DRB in the *DRBs Subject to Status Transfer List* IE within the *RAN Status Transfer Transparent Container* IE, the target NG-RAN node shall not deliver any uplink packet which has a PDCP-SN lower than the value of the *UL Count Value* IE. + +For each DRB in the *DRBs Subject to Status Transfer List* IE within the *RAN Status Transfer Transparent Container* IE, the target NG-RAN node shall use the value of the *DL COUNT Value* IE for the first downlink packet for which there is no PDCP-SN yet assigned. + +If the *Receive Status of UL PDCP SDUs* IE is included for at least one DRB in the *RAN Status Transfer Transparent Container* IE of the DOWNLINK RAN STATUS TRANSFER message, the target NG-RAN node may use it in a Status Report message sent to the UE over the radio interface. + +### 8.4.7.3 Abnormal Conditions + +If the target NG-RAN node receives this message for a UE for which no prepared handover exists at the target NG-RAN node, the target NG-RAN node shall ignore the message. + +## 8.4.8 Handover Success + +### 8.4.8.1 General + +The Handover Success procedure is used during a DAPS Handover, to inform the source NG-RAN node that the UE has successfully accessed the target NG-RAN node. The procedure uses UE-associated signalling. + +#### 8.4.8.2 Successful Operation + +![Diagram of Handover Success](5ec3284657e4df0df3653dd61d0ecd13_img.jpg) + +A diagram showing a handover success scenario. At the top, a large black rectangle represents the User Equipment (UE). Below it, two smaller black rectangles represent the source and target NG-RAN nodes. A horizontal line with an arrow pointing from the target NG-RAN node on the right to the source NG-RAN node on the left represents the HANDOVER SUCCESS message being sent from the AMF (which is connected to both nodes) to the source NG-RAN node. + +Diagram of Handover Success + +**Figure 8.4.8.2-1: Handover Success** + +The AMF initiates the procedure by sending the HANDOVER SUCCESS message to the source NG-RAN node. + +#### 8.4.8.3 Abnormal Conditions + +If the HANDOVER SUCCESS message refers to a context that does not exist, the source NG-RAN node shall ignore the message. + +### 8.4.9 Uplink RAN Early Status Transfer + +#### 8.4.9.1 General + +The purpose of the Uplink RAN Early Status Transfer procedure is to transfer the COUNT of the first downlink SDU that the source NG-RAN node forwards to the target NG-RAN node, from the source NG-RAN node to the target NG-RAN node via the AMF during NG DAPS Handover, or the COUNT for discarding of already forwarded downlink SDUs for respective DRB(s) during NG-handover with time-based trigger condition. The procedure uses UE-associated signalling. + +#### 8.4.9.2 Successful Operation + +![Diagram of Uplink RAN Early Status Transfer](1fa325e34e0974a6426c93e541a7ee86_img.jpg) + +A diagram showing the Uplink RAN Early Status Transfer procedure. On the left, a box labeled 'source NG-RAN node' is connected to a horizontal line representing the NG interface. On the right, a box labeled 'AMF' is also connected to this interface. A horizontal arrow labeled 'UPLINK RAN EARLY STATUS TRANSFER' points from the source NG-RAN node to the AMF. + +Diagram of Uplink RAN Early Status Transfer + +**Figure 8.4.9.2-1: Uplink RAN Early Status Transfer** + +The source NG-RAN node initiates the procedure by sending the UPLINK RAN EARLY STATUS TRANSFER message to the AMF when it considers at least a DRB to be simultaneously served by the source and the target NG-RAN nodes during NG DAPS Handover or sending the UPLINK RAN EARLY STATUS TRANSFER message to the AMF after it initiated a handover preparation with time-based trigger condition. + +For each DRB for which DAPS Handover applies, the source NG-RAN node shall include the *DRB ID* IE and the *FIRST DL COUNT Value* IE within the *DRBs Subject To Early Status Transfer Item* IE in the *Early Status Transfer Transparent Container* IE of the UPLINK RAN EARLY STATUS TRANSFER message. + +### 8.4.9.3 Abnormal Conditions + +Void. + +## 8.4.10 Downlink RAN Early Status Transfer + +### 8.4.10.1 General + +The purpose of the Downlink RAN Early Status Transfer procedure is to transfer the COUNT of the first downlink SDU that the source NG-RAN node forwards to the target NG-RAN node, from the source NG-RAN node to the target NG-RAN node via the AMF during NG DAPS Handover, or the COUNT for discarding of already forwarded downlink SDUs for respective DRB during NG-handover with time-based trigger condition. The procedure uses UE-associated signalling. + +### 8.4.10.2 Successful Operation + +![Sequence diagram showing the Downlink RAN Early Status Transfer procedure. The AMF sends a DOWNLINK RAN EARLY STATUS TRANSFER message to the target NG-RAN node.](2e3b1ae09da2cba02f0bb8a531f1515e_img.jpg) + +``` +sequenceDiagram + participant AMF + participant target NG-RAN node + Note left of AMF: AMF initiates procedure + AMF->>target NG-RAN node: DOWNLINK RAN EARLY STATUS TRANSFER + Note right of target NG-RAN node: Target node receives message +``` + +Sequence diagram showing the Downlink RAN Early Status Transfer procedure. The AMF sends a DOWNLINK RAN EARLY STATUS TRANSFER message to the target NG-RAN node. + +**Figure 8.4.10.2-1: Downlink RAN Early Status Transfer** + +The AMF initiates the procedure by sending the DOWNLINK RAN EARLY STATUS TRANSFER message to the target NG-RAN node. + +For each DRB for which the *FIRST DL COUNT Value* IE is received in the DOWNLINK RAN EARLY STATUS TRANSFER message, the target NG-RAN node shall use it as the COUNT of the first downlink SDU that the source NG-RAN node forwards to the target NG-RAN node. + +For each DRB in the *DRBs Subject To Early Status Transfer List* IE for which the *DISCARD DL COUNT Value* IE is received in the DOWNLINK RAN EARLY STATUS TRANSFER message, the target NG-RAN node does not transmit forwarded downlink SDUs to the UE whose COUNT is less than the provided and discards them if transmission has not been attempted. + +### 8.4.10.3 Abnormal Conditions + +If the target NG-RAN node receives this message for a UE for which no prepared handover exists at the target NG-RAN node, the target NG-RAN node shall ignore the message. + +## 8.5 Paging Procedures + +### 8.5.1 Paging + +#### 8.5.1.1 General + +The purpose of the Paging procedure is to enable the AMF to page a UE in the specific NG-RAN node. + +### 8.5.1.2 Successful Operation + +![Diagram illustrating the Paging procedure. A large black rectangle represents the NG-RAN node. Below it, two smaller black rectangles represent the UE. A vertical line descends from the bottom of the NG-RAN node to the first UE. A horizontal line with an arrow pointing left connects the first UE to the second UE, representing the paging message being forwarded.](b30e390cb591b39482fe7ecd4c4cd84b_img.jpg) + +Diagram illustrating the Paging procedure. A large black rectangle represents the NG-RAN node. Below it, two smaller black rectangles represent the UE. A vertical line descends from the bottom of the NG-RAN node to the first UE. A horizontal line with an arrow pointing left connects the first UE to the second UE, representing the paging message being forwarded. + +**Figure 8.5.1.2-1: Paging** + +The AMF initiates the Paging procedure by sending the PAGING message to the NG-RAN node. + +At the reception of the PAGING message, the NG-RAN node shall perform paging of the UE in cells which belong to tracking areas as indicated in the *TAI List for Paging* IE. + +If the *Paging DRX* IE is included in the PAGING message, the NG-RAN node shall use it according to TS 38.304 [12] and TS 36.304 [29]. + +For each cell that belongs to any of the tracking areas indicated in the *TAI List for Paging* IE, the NG-RAN node shall generate one page on the radio interface. + +If the *Paging Priority* IE is included in the PAGING message, the NG-RAN node may use it according to TS 23.501 [9]. + +If the *UE Radio Capability for Paging* IE is included in the PAGING message, the NG-RAN node may use it to apply specific paging schemes. + +If the *Assistance Data for Recommended Cells* IE is included in the *Assistance Data for Paging* IE it may be used, together with the *Paging Attempt Information* IE if also present, according to TS 38.300 [8]. + +If the *Next Paging Area Scope* IE is included in the *Paging Attempt Information* IE it may be used for paging the UE according to TS 38.300 [8]. + +If the *Paging Origin* IE is included in the PAGING message, the NG-RAN node shall transfer it to the UE according to TS 38.331 [18] and TS 36.331 [21]. + +If the *NB-IoT Paging eDRX Information* IE is included in the PAGING message, the NG-RAN node shall, if supported, use it according to TS 36.304 [29]. If the *NB-IoT Paging Time Window* IE is included in the *NB-IoT Paging eDRX Information* IE, the NG-RAN node shall take this information into account to determine the UE's paging occasion according to TS 36.304 [29]. The NG-RAN node should take into account the reception time of the PAGING message on the NG interface to determine when to page the UE. + +If the *NB-IoT Paging DRX* IE is included in the PAGING message, the NG-RAN node shall use it according to TS 36.304 [29]. + +If the *Enhanced Coverage Restriction* IE is included in the PAGING message, the NG-RAN node shall, if supported, use it as defined in TS 23.501 [9]. + +If the *Paging Assistance Data for CE Capable UE* IE is included in the *Assistance Data for Paging* IE in the PAGING message, it may be used for paging the indicated CE capable UE, according to TS 36.300 [17]. + +If the *WUS Assistance Information* IE is included in the PAGING message, the NG-RAN node shall, if supported, use it to determine the WUS group for the UE, as specified in TS 36.304 [29]. + +If the *E-UTRA Paging eDRX Information* IE is included in the PAGING message, the NG-RAN node shall, if supported, use it according to TS 36.304 [29]. If the *E-UTRA Paging Time Window* IE is included in the *E-UTRA Paging eDRX Information* IE, the NG-RAN node shall take this information into account to determine the UE's paging occasion according to TS 36.304 [29]. The NG-RAN node should take into account the reception time of the PAGING message on the NGAP interface to determine when to page the UE. + +If the *CE-mode-B Restricted* IE is included in the PAGING message and the *Enhanced Coverage Restriction* IE is not set to "restricted", the NG-RAN node shall, if supported, use it as defined in TS 23.501 [9]. + +If the *NPN Paging Assistance Information* IE is included in the *Assistance Data for Paging* IE, the NG-RAN node may take it into account when determining the cells where paging will be performed. + +If the *NR Paging eDRX Information* IE is included in the PAGING message, the NG-RAN node shall, if supported, use it according to TS 38.304 [12] and TS 23.501 [9]. If the *NR Paging Time Window* IE is included in the *NR Paging eDRX Information* IE, the NG-RAN node shall take this information into account to determine the UE's paging occasion according to TS 38.304 [12]. + +If the *Paging Cause* IE is included in the PAGING message, the NG-RAN node shall, if supported, transfer it to the UE according to TS 38.331 [18] and TS 36.331 [21]. + +If the *PEIPS Assistance Information* IE is included in the PAGING message, the NG-RAN node shall, if supported, use it for paging subgrouping of the UE, as specified in TS 38.300 [8]. + +### 8.5.1.3 Abnormal Conditions + +Void. + +## 8.5.2 Multicast Group Paging + +### 8.5.2.1 General + +The purpose of the Multicast Group Paging procedure is to enable the AMF to notify CM-IDLE UEs which have joined a multicast MBS session about its activation. The procedure uses non-UE associated signalling. + +### 8.5.2.2 Successful Operation + +![Sequence diagram showing the Multicast Group Paging procedure. The AMF sends a MULTICAST GROUP PAGING message to the NG-RAN node.](ca3fe82a47b87503fc317d0dbd188ef9_img.jpg) + +``` +sequenceDiagram + participant AMF + participant NG-RAN node + Note right of AMF: + AMF->>NG-RAN node: MULTICAST GROUP PAGING + Note left of NG-RAN node: + Note right of NG-RAN node: +``` + +The diagram illustrates the interaction between the AMF and the NG-RAN node for Multicast Group Paging. It shows a single message flow from the AMF to the NG-RAN node labeled "MULTICAST GROUP PAGING". Both entities are represented by rectangular boxes with lifelines extending downwards, and each has a thick horizontal bar at the bottom of its lifeline. + +Sequence diagram showing the Multicast Group Paging procedure. The AMF sends a MULTICAST GROUP PAGING message to the NG-RAN node. + +**Figure 8.5.2.2-1: Multicast Group Paging** + +The AMF initiates the Multicast Group Paging procedure by sending the MULTICAST GROUP PAGING message to the NG-RAN node. + +At the reception of the MULTICAST GROUP PAGING message, the NG-RAN node shall perform multicast group paging of the MBS session identified by the *MBS Session ID* IE utilising information provided by the AMF. + +If the *Paging DRX* IE is included in the MULTICAST GROUP PAGING message, the NG-RAN node shall use it according to TS 38.304 [12]. + +If the *MBS Service Area* IE is included in the MULTICAST GROUP PAGING message, the NG-RAN node shall take it into account during multicast group paging, as specified in TS 23.247 [44]. + +If the *UE Paging List* IE is included in the MULTICAST GROUP PAGING message, the NG-RAN node shall, if supported, use it according to TS 38.304 [12]. If absent, the NG-RAN node 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 [12]. + +### 8.5.2.3 Abnormal Conditions + +Void. + +## 8.6 Transport of NAS Messages Procedures + +### 8.6.1 Initial UE Message + +#### 8.6.1.1 General + +The Initial UE Message procedure is used when the NG-RAN node has received from the radio interface the first uplink NAS message to be forwarded to an AMF. + +#### 8.6.1.2 Successful Operation + +![Sequence diagram for Initial UE message procedure. The diagram shows two vertical lifelines. The left lifeline has a white rectangular box at the top and a black rectangular box at the bottom. The right lifeline also has a white rectangular box at the top and a black rectangular box at the bottom. A horizontal arrow points from the black box on the left lifeline to the black box on the right lifeline, representing the INITIAL UE MESSAGE message sent from the NG-RAN node to the AMF.](377087fbf1dd0a11c3a435bcd7b6fc35_img.jpg) + +Sequence diagram for Initial UE message procedure. The diagram shows two vertical lifelines. The left lifeline has a white rectangular box at the top and a black rectangular box at the bottom. The right lifeline also has a white rectangular box at the top and a black rectangular box at the bottom. A horizontal arrow points from the black box on the left lifeline to the black box on the right lifeline, representing the INITIAL UE MESSAGE message sent from the NG-RAN node to the AMF. + +**Figure 8.6.1.2-1: Initial UE message** + +The NG-RAN node initiates the procedure by sending an INITIAL UE MESSAGE message to the AMF. The NG-RAN node shall allocate a unique RAN UE NGAP ID to be used for the UE and the NG-RAN node shall include this identity in the INITIAL UE MESSAGE message. + +The *NAS-PDU* IE contains a UE – AMF message that is transferred without interpretation in the NG-RAN node. + +In case of network sharing, the selected PLMN is indicated by the *PLMN Identity* IE within the *TAI* IE included in the INITIAL UE MESSAGE message. + +When the NG-RAN node has received from the radio interface the *5G-S-TMSI* IE, it shall include it in the INITIAL UE MESSAGE message. + +If the *AMF Set ID* IE is included in the INITIAL UE MESSAGE message this indicates that the message is a rerouted message and the AMF shall, if supported, use the IE as described in TS 23.502 [10]. + +If the *UE Context Request* IE is included in the INITIAL UE MESSAGE message the AMF shall trigger an Initial Context Setup procedure towards the NG-RAN node. + +If the *Allowed NSSAI* IE is included in the INITIAL UE MESSAGE message the AMF shall use the IE as defined in TS 23.502 [10]. + +If the *Partially Allowed NSSAI* IE is contained in the INITIAL UE MESSAGE message, the AMF shall, if supported, use the IE as defined in TS 23.502 [10]. + +If the *Source to Target AMF Information Reroute* IE is included in the INITIAL UE MESSAGE message the AMF shall use the IE as defined in TS 23.502 [10]. + +If the *IAB Node Indication* IE is included in the INITIAL UE MESSAGE message, the AMF shall consider that the message is related to an IAB node. + +If the *CE-mode-B Support Indicator* IE is included in the INITIAL UE MESSAGE message and set to "supported", the AMF shall, if supported, use the extended NAS timer settings for the UE as specified in TS 23.501 [9]. + +If the *LTE-M indication* IE is included in the INITIAL UE MESSAGE message the AMF shall, if supported, use it according to TS 23.501 [9]. + +If the *EDT Session* IE set to "true" is included in the INITIAL UE MESSAGE message and the NG-RAN node is an ng-eNB, the AMF shall, if supported, consider that the message has been received as a result of an EDT session initiated by the UE. + +If PNI-NPN related information within the *NPN Access Information* IE is received in the INITIAL UE MESSAGE message, the AMF shall, if supported, consider that the included information is associated to the cell via which the UE has sent the first NAS message, and to the PLMN Identity which is indicated within the *TAI* IE, and use the included information as specified in TS 23.501 [9]. + +In case of network sharing for SNPNs, the selected SNPN is indicated within the *User Location Information* IE included in the INITIAL UE MESSAGE message by the *PLMN Identity* IE within the *TAI* IE and the *NID* IE. + +If the *RedCap Indication* IE is included in the INITIAL UE MESSAGE message, the AMF shall, if supported, use it according to TS 23.501 [9]. + +If the *Mobile IAB Node Indication* IE is included in the INITIAL UE MESSAGE message, the AMF shall consider that the message is related to a mobile IAB-node. + +### 8.6.1.3 Abnormal Conditions + +If the 5G-S-TMSI is not received by the AMF in the INITIAL UE MESSAGE message whereas expected, the AMF shall consider the procedure as failed. + +If the *Partially Allowed NSSAI* IE is received in the INITIAL UE MESSAGE message and the total number of S-NSSAIs included in the Allowed NSSAI and Partially Allowed NSSAI exceeds eight, the AMF shall consider the procedure as failed. + +If any of the S-NSSAI which is present in the *Partially Allowed NSSAI* IE is also present in the *Allowed NSSAI* IE, the AMF shall consider the procedure as failed. + +## 8.6.2 Downlink NAS Transport + +### 8.6.2.1 General + +The Downlink NAS Transport procedure is used when the AMF only needs to send a NAS message transparently via the NG-RAN node to the UE, and a UE-associated logical NG-connection exists for the UE or the AMF has received the *RAN UE NGAP ID* IE in an INITIAL UE MESSAGE message or if the NG-RAN node has already initiated a UE-associated logical NG-connection by sending an INITIAL UE MESSAGE message via another NG interface instance. + +### 8.6.2.2 Successful Operation + +![Diagram illustrating Downlink NAS transport. It shows a sequence of messages between an AMF (top left, black rectangle) and an NG-RAN node (top right, white rectangle). A message is sent from the AMF to the NG-RAN node. Below the AMF is a UE (bottom left, black rectangle) connected to the AMF. Below the NG-RAN node is another UE (bottom right, black rectangle) connected to the NG-RAN node. A horizontal arrow points from the NG-RAN node to the UE connected to the AMF, representing the downlink NAS transport.](276d5f4022bc6b9e4687f9ba4fc7594c_img.jpg) + +Diagram illustrating Downlink NAS transport. It shows a sequence of messages between an AMF (top left, black rectangle) and an NG-RAN node (top right, white rectangle). A message is sent from the AMF to the NG-RAN node. Below the AMF is a UE (bottom left, black rectangle) connected to the AMF. Below the NG-RAN node is another UE (bottom right, black rectangle) connected to the NG-RAN node. A horizontal arrow points from the NG-RAN node to the UE connected to the AMF, representing the downlink NAS transport. + +**Figure 8.6.2.2-1: Downlink NAS transport** + +The AMF initiates the procedure by sending a DOWNLINK NAS TRANSPORT message to the NG-RAN node. If the UE-associated logical NG-connection is not established, the AMF shall allocate a unique AMF UE NGAP ID to be used for the UE and include that in the DOWNLINK NAS TRANSPORT message; by receiving the *AMF UE NGAP ID* IE in the DOWNLINK NAS TRANSPORT message, the NG-RAN node establishes the UE-associated logical NG-connection. + +If the *RAN Paging Priority* IE is included in the DOWNLINK NAS TRANSPORT message, the NG-RAN node may use it to determine a priority for paging the UE in RRC\_INACTIVE state. + +The *NAS-PDU* IE contains an AMF – UE message that is transferred without interpretation in the NG-RAN node. + +If the *Mobility Restriction List* IE is contained in the DOWNLINK NAS TRANSPORT message, the NG-RAN node shall overwrite any previously stored mobility restriction information in the UE context. The NG-RAN node shall use the information in the *Mobility Restriction List* IE if present in the DOWNLINK NAS TRANSPORT message to: + +- determine a target for subsequent mobility action for which the NG-RAN node provides information about the target of the mobility action towards the UE; +- select a proper SCG during dual connectivity operation; +- assign proper RNA(s) for the UE when moving the UE to RRC\_INACTIVE state. + +If the *Mobility Restriction List* IE is not contained in the DOWNLINK NAS TRANSPORT message and there is no previously stored mobility restriction information, the NG-RAN node shall consider that no roaming and no access restriction apply to the UE except for the PNI NPN mobility as described in TS 23.501 [9]. + +The NG-RAN node shall consider that roaming or access to CAG cells is only allowed if the *Allowed PNI-NPN List* IE is contained in the DOWNLINK NAS TRANSPORT message, as described in TS 23.501 [9]. + +If the *Index to RAT/Frequency Selection Priority* IE is included in the DOWNLINK NAS TRANSPORT message, the NG-RAN node shall, if supported, use it as defined in TS 23.501 [9]. + +The *UE Aggregate Maximum Bit Rate* IE should be sent to the NG-RAN node if the AMF has not sent it previously. If it is included in the DOWNLINK NAS TRANSPORT message, the NG-RAN node shall store the UE Aggregate Maximum Bit Rate in the UE context, and use the received UE Aggregate Maximum Bit Rate for all Non-GBR QoS flows for the concerned UE as specified in TS 23.501 [9]. + +If the *Old AMF* IE is included in the DOWNLINK NAS TRANSPORT message, the NG-RAN node shall consider that this UE-associated logical NG-connection was redirected to this AMF from another AMF identified by the *Old AMF* IE. + +If the *SRVCC Operation Possible* IE is included in the DOWNLINK NAS TRANSPORT message, the NG-RAN node shall, if supported, store the content of the received *SRVCC Operation Possible* IE in the UE context and use it as defined in TS 23.216 [31]. + +If the *Extended Connected Time* IE is included in the DOWNLINK NAS TRANSPORT message, the NG-RAN node shall, if supported, use it as described in TS 23.501 [9]. + +If the *Enhanced Coverage Restriction* IE is included in the DOWNLINK NAS TRANSPORT message, the NG-RAN node shall, if supported, store this information in the UE context and use it as defined in TS 23.501 [9]. + +If the *UE Differentiation Information* IE is included in the DOWNLINK NAS TRANSPORT message, the NG-RAN node shall, if supported, store this information in the UE context for further use according to TS 23.501 [9]. + +If the *CE-mode-B Restricted* IE is included in the DOWNLINK NAS TRANSPORT message and the *Enhanced Coverage Restriction* IE is not set to "restricted" and the Enhanced Coverage Restricted information stored in the UE context is not set to "restricted", the NG-RAN node shall, if supported, store this information in the UE context and use it as defined in TS 23.501 [9]. + +If the *UE Radio Capability* IE is included in the DOWNLINK NAS TRANSPORT message, the NG-RAN node shall store this information in the UE context, and use it as defined in TS 38.300 [8]. + +If the *End Indication* IE is included in the DOWNLINK NAS TRANSPORT message and set to "no further data", the NG-RAN node shall consider that besides the included NAS PDU in this message, there are no further NAS PDUs to be transmitted for this UE. + +If the DOWNLINK NAS TRANSPORT message contains the *UE Radio Capability ID* IE, the NG-RAN node shall, if supported, use it as specified in TS 23.501 [9] and TS 23.502 [10]. + +If the *Target NSSAI Information* IE is contained in the DOWNLINK NAS TRANSPORT message, the NG-RAN node may use this information as specified in TS 23.501 [9]. + +If the *Partially Allowed NSSAI* IE is contained in the DOWNLINK NAS TRANSPORT message, the NG-RAN node shall, if supported, deduce from it the partially allowed network slices for the UE, store and replace any previously received Partially Allowed NSSAI and use it as specified in TS 23.501 [9]. + +If the *Masked IMEISV* IE is included in the DOWNLINK NAS TRANSPORT message, the NG-RAN node shall, if supported, use it to determine the characteristics of the UE for subsequent handling. + +#### **Interactions with Initial UE Message procedure:** + +The NG-RAN node shall use the *AMF UE NGAP ID* IE and *RAN UE NGAP ID* IE received in the DOWNLINK NAS TRANSPORT message as identification of the logical connection even if the *RAN UE NGAP ID* IE had been allocated in an INITIAL UE MESSAGE message sent over a different NG interface instance. + +#### **Interaction with the UE Radio Capability Info Indication procedure:** + +If the *UE Capability Info Request* IE set to "requested" is included in the DOWNLINK NAS TRANSPORT message, the NG-RAN node shall trigger the UE Radio Capability Info Indication procedure if UE capability related information was successfully retrieved from the UE. + +### **8.6.2.3 Abnormal Conditions** + +If the *Partially Allowed NSSAI* IE is received in the DOWNLINK NAS TRANSPORT message and the total number of S-NSSAIs included in the Allowed NSSAI and Partially Allowed NSSAI exceeds eight, the NG-RAN node shall consider the procedure as failed. + +If any of the S-NSSAI which is present in the *Partially Allowed NSSAI* IE is also present in the *Allowed NSSAI* IE, the NG-RAN node shall consider the procedure as failed. + +## 8.6.3 Uplink NAS Transport + +### 8.6.3.1 General + +The Uplink NAS Transport procedure is used when the NG-RAN node has received from the radio interface a NAS message to be forwarded to the AMF to which a UE-associated logical NG-connection for the UE exists. + +### 8.6.3.2 Successful Operation + +![Sequence diagram for Uplink NAS transport showing a message from NG-RAN to AMF.](3f2ccb513ccdda4c3e19aea59f7f6215_img.jpg) + +The diagram illustrates the successful operation of Uplink NAS transport. It features two main entities: an NG-RAN node (represented by a white rectangle with a black top bar) and an AMF (represented by a white rectangle with a black top bar). A horizontal arrow points from the NG-RAN node to the AMF, representing the UPLINK NAS TRANSPORT message. Vertical lines extend from each entity down to a solid black horizontal bar at the bottom, representing the user plane or radio interface. + +Sequence diagram for Uplink NAS transport showing a message from NG-RAN to AMF. + +**Figure 8.6.3.2-1: Uplink NAS transport** + +The NG-RAN node initiates the procedure by sending an UPLINK NAS TRANSPORT message to the AMF. + +The *NAS-PDU* IE contains a UE – AMF message that is transferred without interpretation in the NG-RAN node. + +### 8.6.3.3 Abnormal Conditions + +Void. + +## 8.6.4 NAS Non Delivery Indication + +### 8.6.4.1 General + +The NAS Non Delivery Indication procedure is used when the NG-RAN node decides not to start the delivery of a NAS message that has been received over a UE-associated logical NG-connection or the NG-RAN node is unable to ensure that the message has been received by the UE. + +### 8.6.4.2 Successful Operation + +![Sequence diagram for NAS non delivery indication showing a message from NG-RAN to AMF.](9eba62b255ea4757497c72582d0fa54e_img.jpg) + +The diagram illustrates the successful operation of NAS non delivery indication. It features two main entities: an NG-RAN node (represented by a black rectangle with a white top bar) and an AMF (represented by a black rectangle with a white top bar). A horizontal arrow points from the NG-RAN node to the AMF, representing the NAS NON DELIVERY INDICATION message. Vertical lines extend from each entity down to a solid black horizontal bar at the bottom, representing the user plane or radio interface. + +Sequence diagram for NAS non delivery indication showing a message from NG-RAN to AMF. + +**Figure 8.6.4.2-1: NAS non delivery indication** + +The NG-RAN node initiates the procedure by sending a NAS NON DELIVERY INDICATION message to the AMF. The NG-RAN node shall report the non-delivery of a NAS message by including the non-delivered NAS message + +within the *NAS-PDU* IE and an appropriate cause value within the *Cause* IE, e.g., "NG intra system handover triggered", "NG inter system handover triggered" or "Xn handover triggered". + +### 8.6.4.3 Abnormal Conditions + +Void. + +## 8.6.5 Reroute NAS Request + +### 8.6.5.1 General + +The purpose of the Reroute NAS Request procedure is to enable the AMF to request for a rerouting of the INITIAL UE MESSAGE message to another AMF. + +### 8.6.5.2 Successful Operation + +![Sequence diagram for Reroute NAS request. It shows two vertical lifelines. The left lifeline has a black bar at the top and a black bar at the bottom. The right lifeline has a white bar at the top and a black bar at the bottom. A horizontal arrow points from the right lifeline to the left lifeline, indicating the Reroute NAS Request message.](7d0629aa168bf800e491bcbd1979f262_img.jpg) + +``` +sequenceDiagram + participant AMF + participant NG-RAN + Note left of AMF: [Black Bar] + Note right of NG-RAN: [White Bar] + NG-RAN->>AMF: Reroute NAS Request + Note left of AMF: [Black Bar] +``` + +Sequence diagram for Reroute NAS request. It shows two vertical lifelines. The left lifeline has a black bar at the top and a black bar at the bottom. The right lifeline has a white bar at the top and a black bar at the bottom. A horizontal arrow points from the right lifeline to the left lifeline, indicating the Reroute NAS Request message. + +Figure 8.6.5.2-1: Reroute NAS request + +The AMF initiates the procedure by sending a REROUTE NAS REQUEST message to the NG-RAN node. The NG-RAN node shall, if supported, reroute the INITIAL UE MESSAGE message to an AMF indicated by the *AMF Set ID* IE as described in TS 23.501 [9]. + +If the *Allowed NSSAI* IE is included in the REROUTE NAS REQUEST message, then the NG-RAN node shall propagate it in the rerouted INITIAL UE MESSAGE message as defined in TS 23.502 [10]. + +If the *Partially Allowed NSSAI* IE is contained in the REROUTE NAS REQUEST message, the NG-RAN node shall, if supported, propagate it in the rerouted INITIAL UE MESSAGE message as defined in TS 23.502 [10]. + +If the *Source to Target AMF Information Reroute* IE is included in the REROUTE NAS REQUEST message, then the NG-RAN node shall propagate it in the rerouted INITIAL UE MESSAGE message as defined in TS 23.502 [10]. + +### 8.6.5.3 Abnormal Conditions + +If the *Partially Allowed NSSAI* IE is received in the REROUTE NAS REQUEST message and the total number of S-NSSAIs included in the Allowed NSSAI and Partially Allowed NSSAI exceeds eight, the NG-RAN node shall consider the procedure as failed. + +If any of the S-NSSAI which is present in the *Partially Allowed NSSAI* IE is also present in the *Allowed NSSAI* IE, the NG-RAN node shall consider the procedure as failed. + +## 8.7 Interface Management Procedures + +### 8.7.1 NG Setup + +#### 8.7.1.1 General + +The purpose of the NG Setup procedure is to exchange application level data needed for the NG-RAN node and the AMF to correctly interoperate on the NG-C interface. This procedure shall be the first NGAP procedure triggered after the TNL association has become operational. The procedure uses non-UE associated signalling. + +This procedure erases any existing application level configuration data in the two nodes, replaces it by the one received and clears AMF overload state information at the NG-RAN node. If the NG-RAN node and AMF do not agree on retaining the UE contexts this procedure also re-initialises the NGAP UE-related contexts (if any) and erases all related signalling connections in the two nodes like an NG Reset procedure would do. + +#### 8.7.1.2 Successful Operation + +![Sequence diagram illustrating the successful operation of the NG setup procedure. The diagram shows two vertical lifelines representing the NG-RAN node (left) and the AMF (right). The NG-RAN node sends a message (NG SETUP REQUEST) to the AMF, indicated by a horizontal arrow pointing from left to right. The AMF responds with a message (NG SETUP RESPONSE), indicated by a horizontal arrow pointing from right to left. Both lifelines have a solid black bar at the top and bottom, representing the start and end of the procedure.](1bd6a020aa71784ed74367899560cbb9_img.jpg) + +Sequence diagram illustrating the successful operation of the NG setup procedure. The diagram shows two vertical lifelines representing the NG-RAN node (left) and the AMF (right). The NG-RAN node sends a message (NG SETUP REQUEST) to the AMF, indicated by a horizontal arrow pointing from left to right. The AMF responds with a message (NG SETUP RESPONSE), indicated by a horizontal arrow pointing from right to left. Both lifelines have a solid black bar at the top and bottom, representing the start and end of the procedure. + +**Figure 8.7.1.2-1: NG setup: successful operation** + +The NG-RAN node initiates the procedure by sending an NG SETUP REQUEST message including the appropriate data to the AMF. The AMF responds with an NG SETUP RESPONSE message including the appropriate data. + +If the *Configured TAC Indication* IE set to "true" is included for a Tracking Area contained in the *Supported TA List* IE in the NG SETUP REQUEST message, the AMF may take it into account to optimise NG-C signalling towards this NG-RAN node. + +If the *UE Retention Information* IE set to "ues-retained" is included in the NG SETUP REQUEST message, the AMF may accept the proposal to retain the existing UE related contexts and signalling connections by including the *UE Retention Information* IE set to "ues-retained" in the NG SETUP RESPONSE message. + +If the AMF supports IAB, the AMF shall include the *IAB Supported* IE in the NG SETUP RESPONSE message. If the *IAB Supported* IE is included in the NG SETUP RESPONSE message, the NG-RAN node shall, if supported, store this information and use it for further AMF selection for the IAB-MT. + +The AMF shall include the *Backup AMF Name* IE, if available, in the *Served GUAMI List* IE in the NG SETUP RESPONSE message. The NG-RAN node shall, if supported, consider the AMF as indicated by the *Backup AMF Name* IE when performing AMF reselection, as specified in TS 23.501 [9]. + +If the *GUAMI Type* IE is included in the NG SETUP RESPONSE message, the NG-RAN node shall store the received value and use it for further AMF selection as defined in TS 23.501 [9]. + +If the *RAN Node Name* IE is included in the NG SETUP REQUEST message, the AMF may use this IE as a human readable name of the NG-RAN node. If the *Extended RAN Node Name* IE is included in the NG SETUP REQUEST message, the AMF may use this IE as a human readable name of the NG-RAN node and shall ignore the *RAN Node Name* IE if also included. + +If the *AMF Name* IE is included in the NG SETUP RESPONSE message, the NG-RAN node may use this IE as a human readable name of the AMF. If the *Extended AMF Name* IE is included in the NG SETUP RESPONSE message, the NG-RAN node may use this IE as a human readable name of the AMF and shall ignore the *AMF Name* IE if also included. + +If the *NB-IoT Default Paging DRX* IE is included in the NG SETUP REQUEST message, the AMF shall take it into account for paging. + +If the *RAT Information* IE is included in the NG SETUP REQUEST message, the AMF shall handle this information as specified in TS 23.502 [10]. + +If the *NID* IE within the *NPN Support* IE is included within a *Broadcast PLMN Item* IE in the NG SETUP REQUEST message, the AMF shall consider that the NG-RAN node supports the indicated S-NSSAI(s) for the corresponding tracking area code for the SNPN identified by the *PLMN Identity* IE and the *NID* IE. + +If the *NID* IE within the *NPN Support* IE is included within a *PLMN Support Item* IE in the NG SETUP RESPONSE message, the NG-RAN node shall consider that the AMF supports the SNPN identified by the *PLMN Identity* IE and the *NID* IE. + +If the *Onboarding Support* IE is also included within the same *PLMN Support Item* IE, the NG-RAN node shall, if supported, consider that the AMF supports UE onboarding for the identified SNPN, as specified in TS 23.501 [9]. + +If the *TAI NSAG Support List* IE is included in the *Broadcast PLMN Item* IE in the NG SETUP REQUEST message, the AMF shall, if supported, use this information as specified in TS 23.501 [9]. + +If the AMF supports mobile IAB, the AMF shall include the *Mobile IAB Supported* IE in the NG SETUP RESPONSE message. If the *Mobile IAB Supported* IE is included in the NG SETUP RESPONSE message, the NG-RAN node shall, if supported, store this information and further use it for AMF selection for the mobile IAB-MT. + +### 8.7.1.3 Unsuccessful Operation + +![Sequence diagram illustrating an unsuccessful NG setup operation. A large black rectangle represents the AMF, and a smaller black rectangle represents the NG-RAN node. A dashed arrow points from the NG-RAN node to the AMF, indicating a request. A solid arrow points from the AMF back to the NG-RAN node, indicating a response.](461ef997feb933486effd3b0d3504016_img.jpg) + +``` +sequenceDiagram + participant NG-RAN + participant AMF + Note right of AMF: [Unsuccessful Operation] + NG-RAN->>AMF: NG SETUP REQUEST + AMF-->>NG-RAN: NG SETUP FAILURE +``` + +Sequence diagram illustrating an unsuccessful NG setup operation. A large black rectangle represents the AMF, and a smaller black rectangle represents the NG-RAN node. A dashed arrow points from the NG-RAN node to the AMF, indicating a request. A solid arrow points from the AMF back to the NG-RAN node, indicating a response. + +Figure 8.7.1.3-1: NG setup: unsuccessful operation + +If the AMF cannot accept the setup, it should respond with an NG SETUP FAILURE message and appropriate cause value. + +If the NG SETUP FAILURE message includes the *Time to Wait* IE, the NG-RAN node shall wait at least for the indicated time before reinitiating the NG Setup procedure towards the same AMF. + +### 8.7.1.4 Abnormal Conditions + +If the AMF does not identify any of the PLMNs/SNPNs indicated in the NG SETUP REQUEST message, it shall reject the NG Setup procedure with an appropriate cause value. + +If none of the RATs indicated by the NG-RAN node in the NG SETUP REQUEST message is supported by the AMF, then the AMF shall fail the NG Setup procedure with an appropriate cause value. + +## 8.7.2 RAN Configuration Update + +### 8.7.2.1 General + +The purpose of the RAN Configuration Update procedure is to update application level configuration data needed for the NG-RAN node and the AMF to interoperate correctly on the NG-C interface. This procedure does not affect existing UE-related contexts, if any. The procedure uses non UE-associated signalling. + +### 8.7.2.2 Successful Operation + +![Sequence diagram illustrating the successful operation of the RAN configuration update procedure. The diagram shows two entities: an NG-RAN node (represented by a black rectangle with a white top-right corner) and an AMF (represented by a black rectangle). A message arrow points from the NG-RAN node to the AMF, and a return message arrow points from the AMF back to the NG-RAN node.](8b5a2bf5517051acf8bcc2587bcb73a1_img.jpg) + +Sequence diagram illustrating the successful operation of the RAN configuration update procedure. The diagram shows two entities: an NG-RAN node (represented by a black rectangle with a white top-right corner) and an AMF (represented by a black rectangle). A message arrow points from the NG-RAN node to the AMF, and a return message arrow points from the AMF back to the NG-RAN node. + +**Figure 8.7.2.2-1: RAN configuration update: successful operation** + +The NG-RAN node initiates the procedure by sending a RAN CONFIGURATION UPDATE message to the AMF including an appropriate set of updated configuration data that it has just taken into operational use. The AMF responds with a RAN CONFIGURATION UPDATE ACKNOWLEDGE message to acknowledge that it successfully updated the configuration data. If an information element is not included in the RAN CONFIGURATION UPDATE message, the AMF shall interpret that the corresponding configuration data is not changed and shall continue to operate the NG-C interface with the existing related configuration data. + +If the *Supported TA List* IE is included in the RAN CONFIGURATION UPDATE message, the AMF shall overwrite the whole list of supported TAs and the corresponding list of supported slices for each TA, and use them for subsequent registration area management of the UE. + +If the *Configured TAC Indication* IE set to "true" is included for a Tracking Area contained in the *Supported TA List* IE in the RAN CONFIGURATION UPDATE message, the AMF may take it into account to optimise NG-C signalling towards this NG-RAN node. + +If the *Global RAN Node ID* IE is included in the RAN CONFIGURATION UPDATE message, the AMF shall associate the TNLA to the NG-C interface instance using the Global RAN Node ID. + +If the RAN CONFIGURATION UPDATE message includes the *NG-RAN TNL Association to Remove List* IE, the AMF shall, if supported, initiate removal of the TNL association(s) indicated by NG-RAN TNL endpoint(s) and AMF TNL endpoint(s) if the *TNL Association Transport Layer Address at AMF* IE is present, or the TNL association(s) indicated by NG-RAN TNL endpoint(s) if the *TNL Association Transport Layer Address at AMF* IE is absent: + +- if the received *TNL Association Transport Layer Address* IE includes the *Port Number* IE, the NG-RAN TNL endpoint is identified by the *Endpoint IP Address* IE and the *Port Number* IE. Otherwise, the NG-RAN TNL endpoints correspond to all NG-RAN TNL endpoints identified by the *Endpoint IP Address* IE and any port number(s). +- if the received *TNL Association Transport Layer Address at AMF* IE includes the *Port Number* IE, the AMF TNL endpoint is identified by the *Endpoint IP Address* IE and the *Port Number* IE. Otherwise, the AMF TNL endpoints correspond to all AMF TNL endpoints identified by the *Endpoint IP Address* IE and any port number(s). + +If the RAN CONFIGURATION UPDATE message includes the *RAN Node Name* IE, the AMF may store it or update this IE value if already stored, and use it as a human readable name of the NG-RAN node. If the RAN CONFIGURATION UPDATE message includes the *Extended RAN Node Name* IE, the AMF may store it or update this IE value if already stored, and use it as a human readable name of the NG-RAN node and shall ignore the *RAN Node Name* IE if also included. + +If the *NB-IoT Default Paging DRX* IE is included in the RAN CONFIGURATION UPDATE message, the AMF shall overwrite any previously stored NB-IoT default paging DRX value for the NG-RAN node. + +If the *RAT Information* IE is included in the RAN CONFIGURATION UPDATE message, the AMF shall handle this information as specified in TS 23.502 [10]. + +If the *NID* IE within the *NPN Support* IE is included within a *Broadcast PLMN Item* IE in the RAN CONFIGURATION UPDATE message, the AMF shall consider that the NG-RAN node supports the indicated S-NSSAI(s) for the corresponding tracking area code for the SNPN identified by the *PLMN Identity* IE and the *NID* IE. + +If the *TAI NSAG Support List* IE is included in the *Broadcast PLMN Item* IE in the RAN CONFIGURATION UPDATE message, the AMF shall, if supported, use this information as specified in TS 23.501 [9]. + +### 8.7.2.3 Unsuccessful Operation + +![Sequence diagram for RAN configuration update: unsuccessful operation. The diagram shows a horizontal line representing the timeline. On the left, a vertical line descends from the horizontal line to a small horizontal bar, representing the AMF. On the right, another vertical line descends from the horizontal line to a small horizontal bar, representing the NG-RAN node. A long horizontal arrow points from the NG-RAN node back to the AMF. The upper portion of the diagram is a large black rectangle, and the lower portion is a white rectangle.](f0e3f79f8b55cbaba4a467e762854eae_img.jpg) + +Sequence diagram for RAN configuration update: unsuccessful operation. The diagram shows a horizontal line representing the timeline. On the left, a vertical line descends from the horizontal line to a small horizontal bar, representing the AMF. On the right, another vertical line descends from the horizontal line to a small horizontal bar, representing the NG-RAN node. A long horizontal arrow points from the NG-RAN node back to the AMF. The upper portion of the diagram is a large black rectangle, and the lower portion is a white rectangle. + +Figure 8.7.2.3-1: RAN configuration update: unsuccessful operation + +If the AMF cannot accept the update, it shall respond with a RAN CONFIGURATION UPDATE FAILURE message and appropriate cause value. + +If the *Time to Wait* IE is included in the RAN CONFIGURATION UPDATE FAILURE message, the NG-RAN node shall wait at least for the indicated time before reinitiating the RAN Configuration Update procedure towards the same AMF. + +### 8.7.2.4 Abnormal Conditions + +If the NG-RAN node, after initiating the RAN Configuration Update procedure, receives neither a RAN CONFIGURATION UPDATE ACKNOWLEDGE nor a RAN CONFIGURATION UPDATE FAILURE message, the NG-RAN node may reinitiate a further RAN Configuration Update procedure towards the same AMF, provided that the content of the new RAN CONFIGURATION UPDATE message is identical to the content of the previously unacknowledged RAN CONFIGURATION UPDATE message. + +## 8.7.3 AMF Configuration Update + +### 8.7.3.1 General + +The purpose of the AMF Configuration Update procedure is to update application level configuration data needed for the NG-RAN node and AMF to interoperate correctly on the NG-C interface. This procedure does not affect existing UE-related contexts, if any. The procedure uses non UE-associated signalling. + +### 8.7.3.2 Successful Operation + +![Diagram illustrating the AMF configuration update: successful operation. It shows a large black rectangle representing the AMF and a smaller black rectangle representing the NG-RAN node. A horizontal arrow points from the AMF to the NG-RAN node, indicating the flow of the configuration update message.](c5424b117a719524c619938e97c4cb1f_img.jpg) + +Diagram illustrating the AMF configuration update: successful operation. It shows a large black rectangle representing the AMF and a smaller black rectangle representing the NG-RAN node. A horizontal arrow points from the AMF to the NG-RAN node, indicating the flow of the configuration update message. + +**Figure 8.7.3.2-1: AMF configuration update: successful operation** + +The AMF initiates the procedure by sending an AMF CONFIGURATION UPDATE message including the appropriate updated configuration data to the NG-RAN node. The NG-RAN node responds with an AMF CONFIGURATION UPDATE ACKNOWLEDGE message to acknowledge that it successfully updated the configuration data. Unless stated otherwise, if an information element is not included in the AMF CONFIGURATION UPDATE message, the NG-RAN node shall interpret that the corresponding configuration data is not changed and shall continue to operate the NG-C interface with the existing related configuration data. + +If the *PLMN Support List* IE is included in the AMF CONFIGURATION UPDATE message, the NG-RAN node shall overwrite the whole list of supported PLMN/SNPN Identities and the corresponding list of AMF slices and, if present, other associated information for each PLMN/SNPN Identity and use the received values for further network slice selection and AMF selection. + +If the *AMF TNL Association to Add List* IE is included in the AMF CONFIGURATION UPDATE message, the NG-RAN node shall, if supported, use it to establish the TNL association(s) with the AMF. If the *AMF TNL Association to Add List* IE is included in the AMF CONFIGURATION UPDATE message, and if the *AMF TNL Association Address* IE does not include the *Port Number* IE, the NG-RAN node shall assume that port number value 38412 is used for the endpoint. The NG-RAN node shall report to the AMF, in the AMF CONFIGURATION UPDATE ACKNOWLEDGE message, the successful establishment of the TNL association(s) with the AMF as follows: + +- A list of successfully established TNL associations shall be included in the *AMF TNL Association Setup List* IE; +- A list of TNL associations that failed to be established shall be included in the *AMF TNL Association Failed to Setup List* IE. + +If the AMF CONFIGURATION UPDATE message includes the *AMF TNL Association to Remove List* IE, the NG-RAN node shall, if supported, initiate removal of the TNL association(s) indicated by AMF TNL endpoint(s) and NG-RAN node TNL endpoint(s) if the *TNL Association Transport Layer Address NG-RAN* IE is present, or the TNL association(s) indicated by AMF TNL endpoint(s) if the *TNL Association Transport Layer Address NG-RAN* IE is absent: + +- if the received *AMF TNL Association Address* IE includes the *Port Number* IE, the AMF TNL endpoint is identified by the *Endpoint IP Address* IE and the *Port Number* IE. Otherwise, the AMF TNL endpoints correspond to all AMF TNL endpoints identified by the *Endpoint IP Address* IE and any port number(s). +- if the received *TNL Association Transport Layer Address NG-RAN* IE includes the *Port Number* IE, the NG-RAN node TNL endpoint is identified by the *Endpoint IP Address* IE and the *Port Number* IE. Otherwise, the NG-RAN node TNL endpoints correspond to all NG-RAN node TNL endpoints identified by the *Endpoint IP Address* IE and any port number(s). + +If the *AMF Name* IE is included in the AMF CONFIGURATION UPDATE message, the NG-RAN node shall overwrite the previously stored AMF name and use it to identify the AMF. + +If the AMF CONFIGURATION UPDATE message includes the *AMF Name* IE, the NG-RAN node may store it or update this IE value if already stored, and use it as a human readable name of the AMF. If the AMF CONFIGURATION UPDATE message includes the *Extended AMF Name* IE, the NG-RAN node may store it or update this IE value if already stored, and use it as a human readable name of the AMF and shall ignore the *AMF Name* IE if also included. + +If the *Served GUAMI List* IE is included in the AMF CONFIGURATION UPDATE message, the NG-RAN node shall overwrite the whole list of GUAMIs served by the AMF by the new list and use the received values for further AMF management and AMF selection as defined in TS 23.501 [9]. + +If the *Relative AMF Capacity* IE is included in the AMF CONFIGURATION UPDATE message, the NG-RAN node may use it as defined in TS 23.501 [9]. + +If the *AMF TNL Association to Update List* IE is included in the AMF CONFIGURATION UPDATE message the NG-RAN node shall, if supported, update the TNL association(s) indicated by the received AMF Transport Layer information towards the AMF: + +- if the received *AMF TNL Association Address* IE includes the *Port Number* IE, the AMF TNL endpoint is identified by the *Endpoint IP Address* IE and the *Port Number* IE. Otherwise, the AMF TNL endpoints correspond to all AMF TNL endpoints identified by the *Endpoint IP Address* IE and any port number(s). + +If the *TNL Association Usage* IE or the *TNL Address Weight Factor* IE is included in the *AMF TNL Association to Add List* IE or the *AMF TNL Association to Update List* IE, the NG-RAN node shall, if supported, consider it as defined in TS 23.502 [10]. + +If the *NID* IE within the *NPN Support* IE is included within a *PLMN Support Item* IE in the AMF CONFIGURATION UPDATE message, the NG-RAN node shall consider that the AMF supports the SNPN identified by the *PLMN Identity* IE and the *NID* IE. + +If the *Onboarding Support* IE is also included within the same *PLMN Support Item* IE, the NG-RAN node shall, if supported, consider that the AMF supports UE onboarding for the identified SNPN, as specified in TS 23.501 [9]. + +### 8.7.3.3 Unsuccessful Operation + +![Sequence diagram showing an unsuccessful AMF configuration update operation. Two vertical lines represent the AMF (left) and NG-RAN (right). A horizontal arrow points from the AMF to the NG-RAN. Above the NG-RAN's vertical line, there is a black rectangular box with a white rectangle in its top right corner, representing a failure or error state.](9ff197cc407757d6a88e5e9f353864d0_img.jpg) + +Sequence diagram showing an unsuccessful AMF configuration update operation. Two vertical lines represent the AMF (left) and NG-RAN (right). A horizontal arrow points from the AMF to the NG-RAN. Above the NG-RAN's vertical line, there is a black rectangular box with a white rectangle in its top right corner, representing a failure or error state. + +**Figure 8.7.3.3-1: AMF configuration update: unsuccessful operation** + +If the NG-RAN node cannot accept the update, it shall respond with an AMF CONFIGURATION UPDATE FAILURE message and appropriate cause value. + +If the *Time to Wait* IE is included in the AMF CONFIGURATION UPDATE FAILURE message, the AMF shall wait at least for the indicated time before reinitiating the AMF Configuration Update procedure towards the same NG-RAN node. + +### 8.7.3.4 Abnormal Conditions + +If the AMF receives neither an AMF CONFIGURATION UPDATE ACKNOWLEDGE nor an AMF CONFIGURATION UPDATE FAILURE message, the AMF may reinitiate the AMF Configuration Update procedure towards the same NG-RAN node provided that the content of the new AMF CONFIGURATION UPDATE message is identical to the content of the previously unacknowledged AMF CONFIGURATION UPDATE message. + +## 8.7.4 NG Reset + +### 8.7.4.1 General + +The purpose of the NG Reset procedure is to initialise or re-initialise the RAN, or part of RAN NGAP UE-related contexts, in the event of a failure in the 5GC or vice versa. This procedure does not affect the application level configuration data exchanged during, e.g., the NG Setup procedure. The procedure uses non-UE associated signalling. + +### 8.7.4.2 Successful Operation + +#### 8.7.4.2.1 NG Reset initiated by the AMF + +![Sequence diagram showing the NG reset initiated by the AMF. The AMF (top) sends an NG RESET message to the NG-RAN node (bottom). The NG-RAN node responds with an NG RESET ACKNOWLEDGE message. The diagram is simplified, showing only the initial request and the start of the response.](97bac2cf7c2b7516804ea0ce39211258_img.jpg) + +``` + +sequenceDiagram + participant AMF + participant NG-RAN + Note right of AMF: NG RESET initiated by the AMF + AMF->>NG-RAN: NG RESET + NG-RAN-->>AMF: NG RESET ACKNOWLEDGE + +``` + +Sequence diagram showing the NG reset initiated by the AMF. The AMF (top) sends an NG RESET message to the NG-RAN node (bottom). The NG-RAN node responds with an NG RESET ACKNOWLEDGE message. The diagram is simplified, showing only the initial request and the start of the response. + +**Figure 8.7.4.2.1-1: NG reset initiated by the AMF: successful operation** + +In the event of a failure at the AMF which has resulted in the loss of some or all transaction reference information, an NG RESET message shall be sent to the NG-RAN node. + +At reception of the NG RESET message the NG-RAN node shall release all allocated resources on NG and Uu related to the UE association(s) indicated explicitly or implicitly in the NG RESET message and remove the indicated UE contexts including NGAP ID. + +After the NG-RAN node has released all assigned NG resources and the UE NGAP IDs for all indicated UE associations which can be used for new UE-associated logical NG-connections over the NG interface, the NG-RAN node shall respond with the NG RESET ACKNOWLEDGE message. The NG-RAN node does not need to wait for the release of radio resources to be completed before returning the NG RESET ACKNOWLEDGE message. + +If the NG RESET message contains the *UE-associated Logical NG-connection List* IE, then: + +- The NG-RAN node shall use the *AMF UE NGAP ID* IE and/or the *RAN UE NGAP ID* IE to explicitly identify the UE association(s) to be reset. +- The NG-RAN node shall include in the NG RESET ACKNOWLEDGE message, for each UE association to be reset, the *UE-associated Logical NG-connection Item* IE in the *UE-associated Logical NG-connection List* IE. The *UE-associated Logical NG-connection Item* IEs shall be in the same order as received in the NG RESET message and shall include also unknown UE-associated logical NG-connections. Empty *UE-associated Logical NG-connection Item* IEs, received in the NG RESET message, may be omitted in the NG RESET ACKNOWLEDGE message. + +- If the *AMF UE NGAP ID* IE is included in the *UE-associated Logical NG-connection Item* IE for a UE association, the NG-RAN node shall include the *AMF UE NGAP ID* IE in the corresponding *UE-associated Logical NG-connection Item* IE in the NG RESET ACKNOWLEDGE message. +- If the *RAN UE NGAP ID* IE is included in the *UE-associated Logical NG-connection Item* IE for a UE association, the NG-RAN node shall include the *RAN UE NGAP ID* IE in the corresponding *UE-associated Logical NG-connection Item* IE in the NG RESET ACKNOWLEDGE message. + +#### Interactions with other procedures: + +If the NG RESET message is received, any other ongoing procedure (except for another NG Reset procedure) on the same NG interface related to a UE association, indicated explicitly or implicitly in the NG RESET message, shall be aborted. + +#### 8.7.4.2.2 NG Reset initiated by the NG-RAN node + +![Diagram illustrating the successful operation of an NG reset initiated by the NG-RAN node. The diagram shows a large black rectangle representing the NG-RAN node, with a smaller white rectangle in its top right corner. Below the main rectangle, there are two small black rectangles representing the AMF. A horizontal line with an arrow pointing left connects the right AMF rectangle to the NG-RAN node, representing the NG RESET message. A return line connects the NG-RAN node to the left AMF rectangle, representing the NG RESET ACKNOWLEDGE message.](a9241101d638c568cd5a84ab7ad39f15_img.jpg) + +Diagram illustrating the successful operation of an NG reset initiated by the NG-RAN node. The diagram shows a large black rectangle representing the NG-RAN node, with a smaller white rectangle in its top right corner. Below the main rectangle, there are two small black rectangles representing the AMF. A horizontal line with an arrow pointing left connects the right AMF rectangle to the NG-RAN node, representing the NG RESET message. A return line connects the NG-RAN node to the left AMF rectangle, representing the NG RESET ACKNOWLEDGE message. + +**Figure 8.7.4.2.2-1: NG reset initiated by the NG-RAN node: successful operation** + +In the event of a failure at the NG-RAN node which has resulted in the loss of some or all transaction reference information, an NG RESET message shall be sent to the AMF. + +At reception of the NG RESET message the AMF shall release all allocated resources on NG related to the UE association(s) indicated explicitly or implicitly in the NG RESET message and remove the NGAP ID for the indicated UE associations. + +After the AMF has released all assigned NG resources and the UE NGAP IDs for all indicated UE associations which can be used for new UE-associated logical NG-connections over the NG interface, the AMF shall respond with the NG RESET ACKNOWLEDGE message. + +If the NG RESET message contains the *UE-associated Logical NG-connection List* IE, then: + +- The AMF shall use the *AMF UE NGAP ID* IE and/or the *RAN UE NGAP ID* IE to explicitly identify the UE association(s) to be reset. +- The AMF shall include in the NG RESET ACKNOWLEDGE message, for each UE association to be reset, the *UE-associated Logical NG-connection Item* IE in the *UE-associated Logical NG-connection List* IE. The *UE-associated Logical NG-connection Item* IEs shall be in the same order as received in the NG RESET message and shall include also unknown UE-associated logical NG-connections. Empty *UE-associated Logical NG-connection Item* IEs, received in the NG RESET message, may be omitted in the NG RESET ACKNOWLEDGE message. +- If the *AMF UE NGAP ID* IE is included in the *UE-associated Logical NG-connection Item* IE for a UE association, the AMF shall include the *AMF UE NGAP ID* IE in the corresponding *UE-associated Logical NG-connection Item* IE in the NG RESET ACKNOWLEDGE message. + +- If the *RAN UE NGAP ID IE* is included in a *UE-associated Logical NG-connection Item IE* for a UE association, the AMF shall include the *RAN UE NGAP ID IE* in the corresponding *UE-associated Logical NG-connection Item IE* in the NG RESET ACKNOWLEDGE message. + +#### **Interactions with other procedures:** + +If the NG RESET message is received, any other ongoing procedure (except for another NG Reset procedure) on the same NG interface related to a UE association, indicated explicitly or implicitly in the NG RESET message, shall be aborted. + +### **8.7.4.3 Unsuccessful Operation** + +Not applicable. + +### **8.7.4.4 Abnormal Conditions** + +#### **8.7.4.4.1 Abnormal Condition at the 5GC** + +If the NG RESET message includes the *UE-associated Logical NG-connection List IE*, but neither the *AMF UE NGAP ID IE* nor the *RAN UE NGAP ID IE* is present for a *UE-associated Logical NG-connection Item IE*, then the AMF shall ignore the *UE-associated Logical NG-connection Item IE*. The AMF may return the empty *UE-associated Logical NG-connection Item IE* in the *UE-associated Logical NG-connection List IE* in the NG RESET ACKNOWLEDGE message. + +#### **8.7.4.4.2 Abnormal Condition at the NG-RAN** + +If the NG RESET message includes the *UE-associated Logical NG-connection List IE*, but neither the *AMF UE NGAP ID IE* nor the *RAN UE NGAP ID IE* is present for a *UE-associated Logical NG-connection Item IE*, then the NG-RAN node shall ignore the *UE-associated Logical NG-connection Item IE*. The NG-RAN node may return the empty *UE-associated Logical NG-connection Item IE* in the *UE-associated Logical NG-connection List IE* in the NG RESET ACKNOWLEDGE message. + +#### **8.7.4.4.3 Crossing of NG RESET Messages** + +If an NG Reset procedure is ongoing in the NG-RAN node and the NG-RAN node receives an NG RESET message from the peer entity on the same NG interface related to one or several UE associations previously requested to be reset, indicated explicitly or implicitly in the received NG RESET message, the NG-RAN node shall respond with the NG RESET ACKNOWLEDGE message as described in 8.7.4.2.1. + +If an NG Reset procedure is ongoing in the AMF and the AMF receives an NG RESET message from the peer entity on the same NG interface related to one or several UE associations previously requested to be reset, indicated explicitly or implicitly in the received NG RESET message, the AMF shall respond with the NG RESET ACKNOWLEDGE message as described in 8.7.4.2.2. + +## **8.7.5 Error Indication** + +### **8.7.5.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.7.5.2 Successful Operation + +![Sequence diagram showing an error indication initiated by the AMF.](6b0035ff72f9d3c2ef6141caf9a6c743_img.jpg) + +A sequence diagram illustrating the 'Error indication initiated by the AMF'. It features two vertical lifelines. The left lifeline has a black bar at the top and a white bar below it. The right lifeline has a white bar at the top and a black bar below it. A horizontal arrow points from the right lifeline to the left lifeline, positioned between the two bars. + +Sequence diagram showing an error indication initiated by the AMF. + +Figure 8.7.5.2-1: Error indication initiated by the AMF + +![Sequence diagram showing an error indication initiated by the NG-RAN node.](85680f3dcbe15424dd54fa3fd9e1c90d_img.jpg) + +A sequence diagram illustrating the 'Error indication initiated by the NG-RAN node'. It features two vertical lifelines. The left lifeline has a black bar at the top and a white bar below it. The right lifeline has a white bar at the top and a black bar below it. A horizontal arrow points from the left lifeline to the right lifeline, positioned between the two bars. + +Sequence diagram showing an error indication initiated by the NG-RAN node. + +Figure 8.7.5.2-2: Error indication initiated by the NG-RAN node + +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 *AMF UE NGAP ID* IE and the *RAN UE NGAP ID* IE shall be included in the ERROR INDICATION message. If one or both of the *AMF UE NGAP ID* IE and the *RAN UE NGAP ID* IE are not correct, the cause shall be set to an appropriate value, e.g., "Unknown local UE NGAP ID" or "Inconsistent remote UE NGAP ID". + +### 8.7.5.3 Abnormal Conditions + +Void. + +## 8.7.6 AMF Status Indication + +### 8.7.6.1 General + +The purpose of the AMF Status Indication procedure is to support AMF management functions. The procedure uses non UE-associated signalling. + +### 8.7.6.2 Successful Operation + +![Diagram of AMF status indication](a890c88f5a03b77a0de8feaac5313821_img.jpg) + +The diagram shows a large black rectangle at the top representing the AMF, with a white rectangular area in its top right corner. Below the AMF, there are two small black horizontal bars representing NG-RAN nodes. A vertical line descends from the left side of the AMF to the left NG-RAN node. Another vertical line descends from the right side of the AMF to the right NG-RAN node. A horizontal arrow originates from the right NG-RAN node and points back to the left side of the AMF, representing the AMF STATUS INDICATION message. + +Diagram of AMF status indication + +**Figure 8.7.6.2-1: AMF status indication** + +The AMF initiates the procedure by sending an AMF STATUS INDICATION message to the NG-RAN node. + +Upon receipt of the AMF STATUS INDICATION message, the NG-RAN node shall consider the indicated GUAMI(s) will be unavailable and perform AMF reselection as defined in TS 23.501 [9]. + +The NG-RAN node shall, if supported, act accordingly as specified in TS 23.501 [9], based on the presence or absence of the *Timer Approach for GUAMI Removal* IE. + +If the *Backup AMF Name* IE is included in the AMF STATUS INDICATION message, the NG-RAN node shall, if supported, perform AMF reselection considering the AMF as indicated by the *Backup AMF Name* IE as specified in TS 23.501 [9]. + +### 8.7.6.3 Abnormal Conditions + +Void. + +## 8.7.7 Overload Start + +### 8.7.7.1 General + +The purpose of the Overload Start procedure is to inform an NG-RAN node to reduce the signalling load towards the concerned AMF. The procedure uses non-UE associated signalling. + +### 8.7.7.2 Successful Operation + +![Diagram of Overload start](77534ce9b1e09b533f730d8f45e01956_img.jpg) + +The diagram is identical to Figure 8.7.6.2-1, showing a large black rectangle (AMF) at the top with a white rectangle in its top right. Below it are two small black horizontal bars (NG-RAN nodes). Vertical lines connect the AMF to each NG-RAN node. A horizontal arrow originates from the right NG-RAN node and points back to the left side of the AMF, representing the OVERLOAD START message. + +Diagram of Overload start + +**Figure 8.7.7.2-1: Overload start** + +The NG-RAN node receiving the OVERLOAD START message shall assume the AMF from which it receives the message as being in an overloaded state. + +If the *Overload Action* IE is included the *AMF Overload Response* IE within the OVERLOAD START message, the NG-RAN node shall use it to identify the related signalling traffic. When the *Overload Action* IE is set to + +- "reject RRC connection establishments for non-emergency mobile originated data transfer" (i.e., reject traffic corresponding to RRC cause "mo-data", "mo-SMS", "mo-VideoCall" and "mo-VoiceCall" in TS 38.331 [18] or "mo-data" and "mo-VoiceCall" in TS 36.331 [21]), or +- "reject RRC connection establishments for signalling" (i.e., reject traffic corresponding to RRC cause "mo-data", "mo-SMS", "mo-signalling", "mo-VideoCall" and "mo-VoiceCall" in TS 38.331 [18] or "mo-data", "mo-signalling" and "mo-VoiceCall" in TS 36.331 [21]), or +- "only permit RRC connection establishments for emergency sessions and mobile terminated services" (i.e., only permit traffic corresponding to RRC cause "emergency" and "mt-Access" in TS 38.331 [18] or in TS 36.331 [21]), or +- "only permit RRC connection establishments for high priority sessions and mobile terminated services" (i.e., only permit traffic corresponding to RRC cause "highPriorityAccess", "mps-PriorityAccess", "mcs-PriorityAccess" and "mt-Access" in TS 38.331 [18] or "highPriorityAccess", "mo-ExceptionData" and "mt-Access" in TS 36.331 [21]), + +the NG-RAN node shall: + +- if the *AMF Traffic Load Reduction Indication* IE is included in the OVERLOAD START message, reduce the signalling traffic by the indicated percentage, +- otherwise ensure that only the signalling traffic not indicated as to be rejected is sent to the AMF. + +If the *Overload Start NSSAI List* IE is included in the OVERLOAD START message, the NG-RAN node shall: + +- if the *Slice Traffic Load Reduction Indication* IE is present, reduce the signalling traffic by the indicated percentage for the UE(s) whose requested NSSAI only include S-NSSAI(s) contained in the *Overload Start NSSAI List* IE, and the signalling traffic indicated as to be reduced by the *Overload Action* IE in the *Slice Overload Response* IE if the IE is present, +- otherwise ensure that only the signalling traffic from UE(s) whose requested NSSAI includes S-NSSAI(s) other than the ones contained in the *Overload Start NSSAI List* IE, or the signalling traffic not indicated as to be reduced by the *Overload Action* IE in the *Slice Overload Response* IE for the UE(s) if the requested NSSAI matched, is sent to the AMF. + +If an overload control is ongoing and the NG-RAN node receives a further OVERLOAD START message, the NG-RAN node shall replace the contents of the previously received information with the new one. + +### 8.7.7.3 Abnormal Conditions + +Void. + +## 8.7.8 Overload Stop + +### 8.7.8.1 General + +The purpose of the Overload Stop procedure is to signal to an NG-RAN node the AMF is connected to that the overload situation at the AMF has ended and normal operation shall resume. The procedure uses non-UE associated signalling. + +### 8.7.8.2 Successful Operation + +![Sequence diagram for Overload stop. It shows two vertical lifelines. The left lifeline has a black bar at the top and a black bar at the bottom. The right lifeline has a white bar at the top and a black bar at the bottom. A horizontal arrow points from the right lifeline to the left lifeline, indicating a message transfer.](8768e42bf1062f1af11f259fc52a92e9_img.jpg) + +Sequence diagram for Overload stop. It shows two vertical lifelines. The left lifeline has a black bar at the top and a black bar at the bottom. The right lifeline has a white bar at the top and a black bar at the bottom. A horizontal arrow points from the right lifeline to the left lifeline, indicating a message transfer. + +**Figure 8.7.8.2-1: Overload stop** + +The NG-RAN node receiving the OVERLOAD STOP message shall assume that the overload situation at the AMF from which it receives the message has ended and shall resume normal operation for the applicable traffic towards this AMF. + +### 8.7.8.3 Abnormal Conditions + +Void. + +## 8.8 Configuration Transfer Procedures + +### 8.8.1 Uplink RAN Configuration Transfer + +#### 8.8.1.1 General + +The purpose of the Uplink RAN Configuration Transfer procedure is to transfer RAN configuration information from the NG-RAN node to the AMF. The AMF does not interpret the transferred RAN configuration information. This procedure uses non-UE associated signalling. + +#### 8.8.1.2 Successful Operation + +![Sequence diagram for Uplink RAN configuration transfer. It shows two vertical lifelines. The left lifeline has a black bar at the top and a black bar at the bottom. The right lifeline has a white bar at the top and a black bar at the bottom. A horizontal arrow points from the left lifeline to the right lifeline, indicating a message transfer.](faeab87eabc08d09a83cac8f66d1c126_img.jpg) + +Sequence diagram for Uplink RAN configuration transfer. It shows two vertical lifelines. The left lifeline has a black bar at the top and a black bar at the bottom. The right lifeline has a white bar at the top and a black bar at the bottom. A horizontal arrow points from the left lifeline to the right lifeline, indicating a message transfer. + +**Figure 8.8.1.2-1: Uplink RAN configuration transfer** + +The NG-RAN node initiates the procedure by sending the UPLINK RAN CONFIGURATION TRANSFER message to the AMF. + +If the AMF receives the *SON Configuration Transfer* IE, it shall transparently transfer the *SON Configuration Transfer* IE towards the NG-RAN node indicated in the *Target RAN Node ID* IE which is included in the *SON Configuration Transfer* IE. If the *NR CGI* IE is included within the *Target RAN Node ID* IE, the AMF shall, if supported, ignore the + +*Global RAN Node ID* IE within the *Target RAN Node ID* IE, and use it to identify the target gNB as described in TS 38.300 [8]. + +If the AMF receives the *EN-DC SON Configuration Transfer* IE, it shall transparently transfer the *EN-DC SON Configuration Transfer* IE towards an MME serving the eNB indicated in the *Target eNB-ID* IE which is included in the *EN-DC SON Configuration Transfer* IE. + +If the AMF receives the *Inter-system SON Configuration Transfer* IE, it shall transparently transfer the *Inter-system SON Configuration Transfer* IE towards an MME serving the eNB indicated in the *Target eNB-ID* IE which is included in the *Inter-system SON Configuration Transfer* IE. + +### 8.8.1.3 Abnormal Conditions + +Void. + +## 8.8.2 Downlink RAN Configuration Transfer + +### 8.8.2.1 General + +The purpose of the Downlink RAN Configuration Transfer procedure is to transfer RAN configuration information from the AMF to the NG-RAN node. This procedure uses non-UE associated signalling. + +### 8.8.2.2 Successful Operation + +![Diagram illustrating the Downlink RAN configuration transfer procedure. It shows a large black rectangle representing the AMF and a smaller black rectangle representing the NG-RAN node. A horizontal line with an arrow pointing from the NG-RAN node to the AMF indicates the transfer of configuration information.](6e9fbc3d95eb2b3f67cbbbd5de0c3999_img.jpg) + +The diagram shows a large black rectangle at the top representing the AMF. Below it, a smaller black rectangle represents the NG-RAN node. A horizontal line with an arrow pointing from the NG-RAN node to the AMF indicates the transfer of configuration information. + +Diagram illustrating the Downlink RAN configuration transfer procedure. It shows a large black rectangle representing the AMF and a smaller black rectangle representing the NG-RAN node. A horizontal line with an arrow pointing from the NG-RAN node to the AMF indicates the transfer of configuration information. + +**Figure 8.8.2.2-1: Downlink RAN configuration transfer** + +The procedure is initiated with an DOWNLINK RAN CONFIGURATION TRANSFER message sent from the AMF to the NG-RAN node. + +If the NG-RAN node receives, in the *SON Configuration Transfer* IE or in the *EN-DC SON Configuration Transfer* IE, the *SON Information* IE containing the *SON Information Request* IE, it may transfer back the requested information either towards the NG-RAN node indicated in the *Source RAN Node ID* IE of the *SON Configuration Transfer* IE or towards an eNB indicated in the *Source eNB-ID* IE of the *EN-DC SON Configuration Transfer* IE by initiating the Uplink RAN Configuration Transfer procedure. + +If the NG-RAN node receives, in the *SON Configuration Transfer* IE, the *Xn TNL Configuration Info* IE containing the *Xn Extended Transport Layer Addresses* IE, it may use it as part of its ACL functionality configuration actions, if such ACL functionality is deployed. + +If the NG-RAN node receives, in the *SON Configuration Transfer* IE, the *SON Information* IE containing the *SON Information Reply* IE including the *Xn TNL Configuration Info* IE as an answer to a former request, it may use it to initiate the Xn TNL establishment. + +In case the *IP-Sec Transport Layer Address* IE is present and the *GTP Transport Layer Addresses* IE within the *Xn Extended Transport Layer Addresses* IE is not empty, GTP traffic is conveyed within an IP-Sec tunnel terminated at the IP-Sec tunnel endpoint given in the *IP-Sec Transport Layer Address* IE. + +In case the *IP-Sec Transport Layer Address* IE is not present, GTP traffic is terminated at the endpoints given by the list of addresses in the *Xn GTP Transport Layer Addresses* IE within the *Xn Extended Transport Layer Addresses* IE. + +In case the *Xn GTP Transport Layer Addresses* IE is empty and the *IP-Sec Transport Layer Address* IE is present, SCTP traffic is conveyed within an IP-Sec tunnel terminated at the IP-Sec tunnel endpoint given in the *IP-Sec Transport Layer Address* IE, within the *Xn Extended Transport Layer Addresses* IE. + +In case the *Xn SCTP Transport Layer Addresses* IE is present and the *IP-Sec Transport Layer Address* IE is also present, the concerned SCTP traffic is conveyed within an IP-Sec tunnel terminated at the IP-Sec tunnel endpoint given in this *IP-Sec Transport Layer Address* IE, within the *Xn Extended Transport Layer Addresses* IE. + +If the NG-RAN node receives the *SON Information* IE containing the *SON Information Report* IE it may use it as specified in TS 38.300 [8]. + +If the NG-RAN node receives the *Inter-system SON Information* IE containing the *Inter-system SON Information Report* IE it may use it as specified in TS 38.300 [8]. + +If the NG-RAN node receives the *Inter-system SON Information* IE containing the *Inter-system SON Information Request* IE or the *Inter-system SON Information Reply* IE, it may use it as specified in TS 38.300 [8]. If the *Reporting System* IE in the *Inter-system SON Information Request* IE is set to 'No Reporting', the DOWNLINK RAN CONFIGURATION TRANSFER message shall be ignored. + +If the NG-RAN node is configured to use one IPsec tunnel for all NG and Xn traffic (IPsec star topology) then the traffic to the peer NG-RAN node shall be routed through this IPsec tunnel and the *IP-Sec Transport Layer Address* IE shall be ignored. + +### 8.8.2.3 Abnormal Conditions + +Void. + +## 8.9 Warning Message Transmission Procedures + +### 8.9.1 Write-Replace Warning + +#### 8.9.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.9.1.2 Successful Operation + +![Diagram illustrating the Write-Replace Warning procedure: successful operation. It shows a horizontal bar representing the NG-RAN node, with a black rectangle on the left and a white rectangle on the right. Below the bar, two vertical lines extend downwards to small black rectangles. A horizontal arrow points from the left vertical line to the right vertical line, indicating the flow of the procedure.](bc90605aeb4173d4b4aa6eb475037a0c_img.jpg) + +Diagram illustrating the Write-Replace Warning procedure: successful operation. It shows a horizontal bar representing the NG-RAN node, with a black rectangle on the left and a white rectangle on the right. Below the bar, two vertical lines extend downwards to small black rectangles. A horizontal arrow points from the left vertical line to the right vertical line, indicating the flow of the procedure. + +**Figure 8.9.1.2-1: Write-Replace Warning procedure: successful operation** + +The AMF initiates the procedure by sending a WRITE-REPLACE WARNING REQUEST message to the NG-RAN node. + +Upon receipt of the WRITE-REPLACE WARNING REQUEST message, the NG-RAN node shall prioritise its resources to process the warning message. + +If, in a certain area, broadcast of a warning message is already ongoing and the NG-RAN node receives a WRITE-REPLACE WARNING REQUEST message with *Message Identifier* IE and/or *Serial Number* IE which are different from those in the warning message being broadcast, and if the *Concurrent Warning Message Indicator* IE is not present, the NG-RAN node shall replace the warning message being broadcast with the newly received one for that area. + +If the NG-RAN node receives a WRITE-REPLACE WARNING REQUEST message with a warning message identified by the *Message Identifier* IE and *Serial Number* IE and if there are no prior warning messages being broadcast in any of the warning areas indicated in the *Warning Area List* IE, the NG-RAN node shall broadcast the received warning message for those area(s). + +If, in a certain area, broadcast of one or more warning messages are already ongoing and the NG-RAN node receives a WRITE-REPLACE WARNING REQUEST message with a *Message Identifier* IE and/or *Serial Number* IE which are different from those in any of the warning messages being broadcast, and if the *Concurrent Warning Message Indicator* IE is present, the NG-RAN node shall schedule the received warning message for broadcast, for that area. + +If the *Concurrent Warning Message Indicator* IE is present and if a value "0" is received in the *Number of Broadcasts Requested* IE, the NG-RAN node shall broadcast the received warning message indefinitely until requested otherwise to stop broadcasting, except if the *Repetition Period* IE is set to "0". + +If, in a certain area, broadcast of one or more warning messages are already ongoing and the NG-RAN node receives a WRITE-REPLACE WARNING REQUEST message with *Message Identifier* IE and *Serial Number* IE which correspond to one of the warning messages already being broadcast in that area, the NG-RAN node shall not start a new broadcast or replace an existing one but it shall still reply by sending a WRITE-REPLACE WARNING RESPONSE message which includes the *Broadcast Completed Area List* IE set according to the ongoing broadcast. + +If the *Warning Area List* IE is not included in the WRITE-REPLACE WARNING REQUEST message, the NG-RAN node shall broadcast the indicated message in all of the cells within the NG-RAN node. + +If the *Warning Type* IE is included in the WRITE-REPLACE WARNING REQUEST message, the NG-RAN node shall broadcast the Primary Notification irrespective of the setting of the *Repetition Period* IE and the *Number of Broadcasts Requested* IE, and process the Primary Notification according to TS 36.331 [21] and TS 38.331 [18]. + +If the *Data Coding Scheme* IE and the *Warning Message Contents* IE are both included in the WRITE-REPLACE WARNING REQUEST message, the NG-RAN node shall schedule a broadcast of the warning message according to the value of the *Repetition Period* IE and the *Number of Broadcasts Requested* IE and process the warning message according to TS 36.331 [21] and TS 38.331 [18]. + +If the *Warning Area Coordinates* IE is included in the WRITE-REPLACE WARNING REQUEST message, the NG-RAN node shall include this information together with the warning message being broadcast according to TS 36.331 [21] and TS 38.331 [18]. + +The NG-RAN node acknowledges the WRITE-REPLACE WARNING REQUEST message by sending a WRITE-REPLACE WARNING RESPONSE message to the AMF. + +If the *Broadcast Completed Area List* IE is not included in the WRITE-REPLACE WARNING RESPONSE message, the AMF shall consider that the broadcast is unsuccessful in all the cells within the NG-RAN node. + +#### 8.9.1.3 Unsuccessful Operation + +Not applicable. + +#### 8.9.1.4 Abnormal Conditions + +If the *Concurrent Warning Message Indicator* IE is not present and if a value "0" is received in the *Number of Broadcasts Requested* IE, the NG-RAN node shall not broadcast the received secondary notification. + +If the *Concurrent Warning Message Indicator* IE is included and if a value "0" is received in the *Repetition Period* IE, the NG-RAN node shall not broadcast the received warning message except if the *Number of Broadcasts Requested* IE is set to "1". + +If the *Concurrent Warning Message Indicator* IE is not included and if a value "0" is received in the *Repetition Period* IE, the NG-RAN node shall not broadcast the received secondary notification except if the *Number of Broadcasts Requested* IE is set to "1". + +### 8.9.2 PWS Cancel + +#### 8.9.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.9.2.2 Successful Operation + +![Sequence diagram illustrating the PWS Cancel procedure: successful operation. The diagram shows three horizontal lifelines. The top lifeline has a white box on the left and a white box on the right. The middle lifeline is a solid black bar. The bottom lifeline is a solid black bar. A vertical line descends from the left white box to the bottom lifeline. A vertical line descends from the right white box to the middle lifeline. A horizontal arrow points from the middle lifeline to the bottom lifeline. A horizontal arrow points from the bottom lifeline to the middle lifeline. A horizontal arrow points from the middle lifeline to the right white box.](18fb2f2a7bdbb03074578da43004abaa_img.jpg) + +Sequence diagram illustrating the PWS Cancel procedure: successful operation. The diagram shows three horizontal lifelines. The top lifeline has a white box on the left and a white box on the right. The middle lifeline is a solid black bar. The bottom lifeline is a solid black bar. A vertical line descends from the left white box to the bottom lifeline. A vertical line descends from the right white box to the middle lifeline. A horizontal arrow points from the middle lifeline to the bottom lifeline. A horizontal arrow points from the bottom lifeline to the middle lifeline. A horizontal arrow points from the middle lifeline to the right white box. + +**Figure 8.9.2.2-1: PWS Cancel procedure: successful operation** + +The AMF initiates the procedure by sending a PWS CANCEL REQUEST message to the NG-RAN node. + +If the NG-RAN node receives a PWS CANCEL REQUEST message and broadcast of the warning message identified by the *Message Identifier* and *Serial Number* IE is ongoing in an area indicated within the *Warning Area List* IE, the NG-RAN node shall stop broadcasting the warning message within that area and discard the warning message for that area. + +If the *Warning Area List* IE is not included in the PWS CANCEL REQUEST message, the NG-RAN node shall stop broadcasting and discard the warning message identified by the *Message Identifier* IE and the *Serial Number* IE in all of the cells in the NG-RAN node. + +The NG-RAN node shall acknowledge the PWS CANCEL REQUEST message by sending the PWS CANCEL RESPONSE message, with the *Message Identifier* IE and the *Serial Number* IE copied from the PWS CANCEL REQUEST message and shall, if there is an area to report where an ongoing broadcast was stopped successfully, include the *Broadcast Cancelled Area List* IE. + +If an area included in the *Warning Area List* IE in the PWS CANCEL REQUEST message does not appear in the *Broadcast Cancelled Area List* IE, the AMF shall consider that the NG-RAN node had no ongoing broadcast to stop for the same *Message Identifier* and *Serial Number* in that area. + +If the *Broadcast Cancelled Area List* IE is not included in the PWS CANCEL RESPONSE message, the AMF shall consider that the NG-RAN node had no ongoing broadcast to stop for the same *Message Identifier* and *Serial Number*. + +If the *Cancel-All Warning Messages Indicator* IE is present in the PWS CANCEL REQUEST message, then the NG-RAN node shall stop broadcasting and discard all warning messages for the area as indicated in the *Warning Area List* IE or in all the cells of the NG-RAN node if the *Warning Area List* IE is not included. The NG-RAN node shall acknowledge the PWS CANCEL REQUEST message by sending the PWS CANCEL RESPONSE message, with the *Message Identifier* IE and the *Serial Number* IE copied from the PWS CANCEL REQUEST message and shall, if there is area to report where an ongoing broadcast was stopped successfully, include the *Broadcast Cancelled Area List* IE with the *Number of Broadcasts* IE set to 0. + +#### 8.9.2.3 Unsuccessful Operation + +Not applicable. + +#### 8.9.2.4 Abnormal Conditions + +Void. + +### 8.9.3 PWS Restart Indication + +#### 8.9.3.1 General + +The purpose of the PWS Restart Indication procedure is to inform the AMF that PWS information for some or all cells of the NG-RAN node may be reloaded from the CBC if needed. The procedure uses non UE-associated signalling. + +#### 8.9.3.2 Successful Operation + +![Sequence diagram for PWS restart indication showing a message from the NG-RAN node to the AMF.](f874851e6d8b67f9ecbc8e056ac6db8f_img.jpg) + +The diagram illustrates a sequence of two vertical lifelines. The left lifeline represents the NG-RAN node and the right lifeline represents the AMF. A horizontal arrow points from the NG-RAN node to the AMF, indicating the PWS restart indication message. Both lifelines are represented by thick black vertical bars. + +Sequence diagram for PWS restart indication showing a message from the NG-RAN node to the AMF. + +Figure 8.9.3.2-1: PWS restart indication + +The NG-RAN node initiates the procedure by sending a PWS RESTART INDICATION message to the AMF. On receipt of a PWS RESTART INDICATION message, the AMF shall act as defined in TS 23.007 [20]. + +If the Emergency Area ID is available, the NG-RAN node shall also include it in the *Emergency Area ID List for Restart IE*. + +### 8.9.3.3 Abnormal Conditions + +Void. + +## 8.9.4 PWS Failure Indication + +### 8.9.4.1 General + +The purpose of the PWS Failure Indication procedure is to inform the AMF that ongoing PWS operation for one or more cells of the NG-RAN node has failed. The procedure uses non UE-associated signalling. + +### 8.9.4.2 Successful Operation + +![Diagram illustrating the PWS failure indication procedure. It shows a large black rectangle representing the NG-RAN node, with a white rectangle inside its top right corner. Below the main black rectangle, there are two small black horizontal bars. A horizontal arrow points from the left small bar to the right small bar, indicating the flow of the PWS FAILURE INDICATION message from the NG-RAN node to the AMF.](e4aab374983ba0fc24496fe7cd11c06c_img.jpg) + +Diagram illustrating the PWS failure indication procedure. It shows a large black rectangle representing the NG-RAN node, with a white rectangle inside its top right corner. Below the main black rectangle, there are two small black horizontal bars. A horizontal arrow points from the left small bar to the right small bar, indicating the flow of the PWS FAILURE INDICATION message from the NG-RAN node to the AMF. + +**Figure 8.9.4.2-1: PWS failure indication** + +The NG-RAN node initiates the procedure by sending a PWS FAILURE INDICATION message to the AMF. On receipt of a PWS FAILURE INDICATION message, the AMF shall act as defined in TS 23.041 [22]. + +### 8.9.4.3 Abnormal Conditions + +Void. + +## 8.10 NRPPa Transport Procedures + +### 8.10.1 General + +The purpose of the NRPPa Transport procedures is to carry NRPPa signalling (defined in TS 38.455 [19]) between the NG-RAN node and the LMF over the NG interface. + +The Downlink UE Associated NRPPa Transport procedure and the Uplink UE Associated NRPPa Transport procedure use UE-associated signalling. The UE-associated signalling is used to support E-CID Location Information Transfer, Positioning Information Transfer, Measurement Preconfiguration Information Transfer, and Reporting of General Error Situations due to reception of an NRPPa message that utilized UE-associated signalling. + +The Downlink Non UE Associated NRPPa Transport procedure and the Uplink Non UE Associated NRPPa Transport procedure use non-UE associated signalling. The non-UE associated signalling is used to support OTDOA Information Transfer, Assistance Information Transfer, TRP Information Transfer, Measurement Information Transfer, PRS + +Information Transfer, and Reporting of General Error Situations due to reception of an NRPPa message that utilized non-UE associated signalling. + +## 8.10.2 Successful Operations + +### 8.10.2.1 DOWNLINK UE ASSOCIATED NRPPA TRANSPORT + +![Sequence diagram for Downlink UE-associated NRPPa transport showing a message from the AMF to the NG-RAN node.](5efe6377e22b9ab76a19a70da29976b9_img.jpg) + +The diagram illustrates a sequence of two vertical lifelines. The left lifeline represents the AMF and the right lifeline represents the NG-RAN node. Both lifelines have a black rectangular block at the top. A horizontal arrow points from the AMF lifeline to the NG-RAN node lifeline, indicating the direction of the DOWNLINK UE ASSOCIATED NRPPA TRANSPORT message. + +Sequence diagram for Downlink UE-associated NRPPa transport showing a message from the AMF to the NG-RAN node. + +Figure 8.10.2.1-1: Downlink UE-associated NRPPa transport + +The AMF initiates the procedure by sending the DOWNLINK UE ASSOCIATED NRPPA TRANSPORT message to the NG-RAN node. + +### 8.10.2.2 UPLINK UE ASSOCIATED NRPPA TRANSPORT + +![Sequence diagram for Uplink UE-associated NRPPa transport showing a message from the NG-RAN node to the AMF.](0db2dd2a5c02140f5b395569f17ab91d_img.jpg) + +The diagram illustrates a sequence of two vertical lifelines. The left lifeline represents the AMF and the right lifeline represents the NG-RAN node. Both lifelines have a black rectangular block at the top. A horizontal arrow points from the NG-RAN node lifeline to the AMF lifeline, indicating the direction of the UPLINK UE ASSOCIATED NRPPA TRANSPORT message. + +Sequence diagram for Uplink UE-associated NRPPa transport showing a message from the NG-RAN node to the AMF. + +Figure 8.10.2.2-1: Uplink UE-associated NRPPa transport + +The NG-RAN node initiates the procedure by sending the UPLINK UE ASSOCIATED NRPPA TRANSPORT message to the AMF. + +### 8.10.2.3 DOWNLINK NON UE ASSOCIATED NRPPA TRANSPORT + +![Sequence diagram for Downlink non UE-associated NRPPa transport showing a message from the AMF to the NG-RAN node.](4cb2d3c8066966514fdc92491fe8feed_img.jpg) + +The diagram illustrates a sequence of two vertical lifelines. The left lifeline represents the AMF and the right lifeline represents the NG-RAN node. Both lifelines have a black rectangular block at the top. A horizontal arrow points from the AMF lifeline to the NG-RAN node lifeline, indicating the direction of the DOWNLINK NON UE ASSOCIATED NRPPA TRANSPORT message. + +Sequence diagram for Downlink non UE-associated NRPPa transport showing a message from the AMF to the NG-RAN node. + +Figure 8.10.2.3-1: Downlink non UE-associated NRPPa transport + +The AMF initiates the procedure by sending the DOWNLINK NON UE ASSOCIATED NRPPA TRANSPORT message to the NG-RAN node. + +#### 8.10.2.4 UPLINK NON UE ASSOCIATED NRPPA TRANSPORT + +![Diagram illustrating the Uplink non UE-associated NRPPa transport procedure. A large black rectangle represents the NG-RAN node, with a white rectangle inside its top right corner. Below the rectangle, two small black horizontal bars represent the AMF (left) and the NG-RAN node (right). A horizontal arrow points from the NG-RAN node bar to the AMF bar, indicating the direction of the Uplink non UE-associated NRPPa transport message.](82340ab4d7b2db48ce408d8db6fde6b6_img.jpg) + +Diagram illustrating the Uplink non UE-associated NRPPa transport procedure. A large black rectangle represents the NG-RAN node, with a white rectangle inside its top right corner. Below the rectangle, two small black horizontal bars represent the AMF (left) and the NG-RAN node (right). A horizontal arrow points from the NG-RAN node bar to the AMF bar, indicating the direction of the Uplink non UE-associated NRPPa transport message. + +**Figure 8.10.2.4-1: Uplink non UE-associated NRPPa transport** + +The NG-RAN node initiates the procedure by sending the UPLINK NON UE ASSOCIATED NRPPA TRANSPORT message to the AMF. + +### 8.10.3 Unsuccessful Operations + +Not applicable. + +### 8.10.4 Abnormal Conditions + +If an AMF receives an UPLINK UE ASSOCIATED NRPPA TRANSPORT message with an unknown Routing ID for the UE, the AMF shall ignore the message. + +If an AMF receives an UPLINK NON UE ASSOCIATED NRPPA TRANSPORT message indicating an unknown or unreachable Routing ID, the AMF shall ignore the message. + +## 8.11 Trace Procedures + +### 8.11.1 Trace Start + +#### 8.11.1.1 General + +The purpose of the Trace Start procedure is to allow the AMF to request the NG-RAN node to initiate a trace session for a UE. The procedure uses UE-associated signalling. If no UE-associated logical NG-connection exists, the UE-associated logical NG-connection shall be established as part of the procedure. + +### 8.11.1.2 Successful Operation + +![Diagram illustrating the Trace start procedure. A large black rectangle represents the NG-RAN node, with a white rectangle inside its top right corner. Below the main rectangle, two smaller black rectangles represent the AMF (left) and the UE (right). A horizontal arrow points from the AMF to the NG-RAN node, indicating the TRACE START message.](8a9a4dc9f8f886d283f9a75e5b2287f4_img.jpg) + +Diagram illustrating the Trace start procedure. A large black rectangle represents the NG-RAN node, with a white rectangle inside its top right corner. Below the main rectangle, two smaller black rectangles represent the AMF (left) and the UE (right). A horizontal arrow points from the AMF to the NG-RAN node, indicating the TRACE START message. + +**Figure 8.11.1.2-1: Trace start** + +The AMF initiates the procedure by sending a TRACE START message. Upon reception of the TRACE START message, the NG-RAN node shall initiate the requested trace session as described in TS 32.422 [11]. + +If the *Trace Activation* IE is included in the TRACE START message which includes the *MDT Activation* IE set to "Immediate MDT and Trace", the NG-RAN node shall, if supported, initiate the requested trace session and MDT session as described in TS 32.422 [11]. + +If the *Trace Activation* IE is included in the TRACE START message which includes the *MDT Activation* IE set to "Immediate MDT Only", "Logged MDT only", the NG-RAN node shall, if supported, initiate the requested MDT session as described in TS 32.422 [11] and the NG-RAN node shall ignore the *Interfaces To Trace* IE and the *Trace Depth* IE. + +If the *Trace Activation* IE includes the *MDT Location Information* IE within the *MDT Configuration* IE, the NG-RAN node shall, if supported, store this information and take it into account in the requested MDT session. + +If the *Trace Activation* IE is included in the TRACE START message which includes the *MDT Activation* IE set to "Immediate MDT Only", "Logged MDT only" and if the *Signalling Based MDT PLMN List* IE is included in the *MDT Configuration* IE, the NG-RAN node may use it to propagate the MDT Configuration as described in TS 37.320 [41]. + +If the *Trace Activation* IE includes the *Bluetooth Measurement Configuration* IE within the *MDT Configuration* IE, the NG-RAN node shall, if supported, take it into account for MDT Configuration as described in TS 37.320 [41]. + +If the *Trace Activation* IE includes the *WLAN Measurement Configuration* IE within the *MDT Configuration* IE, the NG-RAN node shall, if supported, take it into account for MDT Configuration as described in TS 37.320 [41]. + +If the *Trace Activation* IE includes the *Sensor Measurement Configuration* IE within the *MDT Configuration* IE, the NG-RAN node shall, if supported, take it into account for MDT Configuration as described in TS 37.320 [41]. + +If the *Trace Activation* IE includes the *MDT Configuration* IE and if the NG-RAN node is a gNB at least the *MDT Configuration-NR* IE shall be present, while if the NG-RAN node is an ng-eNB at least the *MDT Configuration-EUTRA* IE shall be present. + +If the *PNI-NPN Area Scope of MDT* IE is included in the *MDT Configuration-NR* IE included in the TRACE START message, the NG-RAN node shall, if supported, use it to derive the MDT area scope for MDT measurement collection in PNI-NPN areas. Upon reception of the *PNI-NPN Area Scope of MDT* IE, the NG-RAN node shall consider that the area scope for MDT measurement collection in PNI-NPN areas is defined only by the areas included in the *PNI-NPN Area Scope of MDT* IE. + +#### Interactions with other procedures: + +If the NG-RAN node is not able to initiate the trace session due to ongoing handover of the UE to another NG-RAN node, the NG-RAN node shall initiate a Trace Failure Indication procedure with the appropriate cause value. + +### 8.11.1.3 Abnormal Conditions + +If both the *PNI-NPN Area Scope of MDT* IE and the *Area Scope of MDT* IE included in the *MDT Configuration-NR* IE in the TRACE START message, and the *Area Scope of MDT* IE is set to "PNI-NPN based", the NG-RAN node shall, if supported, use it to derive the MDT area scope for MDT measurement collection in PNI-NPN areas, and ignore the *PNI-NPN Area Scope of MDT* IE. + +## 8.11.2 Trace Failure Indication + +### 8.11.2.1 General + +The purpose of the Trace Failure Indication procedure is to allow the NG-RAN node to inform the AMF that a Trace Start procedure or a Deactivate Trace procedure or an ongoing trace has failed due to an interaction with a handover procedure or due to reception of multiple trace activations while the UE is in RRC-INACTIVE. The procedure uses UE-associated signalling. + +### 8.11.2.2 Successful Operation + +![Sequence diagram for Trace failure indication. A long black rectangle at the top represents the NG-RAN node, with a white rectangle on its right side. Below it, two short black horizontal bars represent the AMF. A horizontal arrow points from the left AMF bar to the right AMF bar, passing through the NG-RAN node's timeline.](46b47a38697e3aedb09cccd7eba47192_img.jpg) + +The diagram illustrates the successful operation of the Trace Failure Indication procedure. It shows a sequence of messages between the NG-RAN node (represented by a long black rectangle at the top) and the AMF (represented by two short black horizontal bars at the bottom). A horizontal arrow originates from the left AMF bar and points to the right AMF bar, indicating the flow of the TRACE FAILURE INDICATION message. The arrow passes through the NG-RAN node's timeline, which is represented by a vertical line extending from the bottom of the long black rectangle. + +Sequence diagram for Trace failure indication. A long black rectangle at the top represents the NG-RAN node, with a white rectangle on its right side. Below it, two short black horizontal bars represent the AMF. A horizontal arrow points from the left AMF bar to the right AMF bar, passing through the NG-RAN node's timeline. + +Figure 8.11.2.2-1: Trace failure indication + +The NG-RAN node initiates the procedure by sending a TRACE FAILURE INDICATION message. Upon reception of the TRACE FAILURE INDICATION message, the AMF shall take appropriate actions based on the failure reason indicated by the *Cause* IE. + +### 8.11.2.3 Abnormal Conditions + +Void. + +## 8.11.3 Deactivate Trace + +### 8.11.3.1 General + +The purpose of the Deactivate Trace procedure is to allow the AMF to request the NG-RAN node to stop the trace session for the indicated trace reference. The procedure uses UE-associated signalling. + +### 8.11.3.2 Successful Operation + +![Sequence diagram for Deactivate trace procedure. It shows two vertical lifelines. The left lifeline has a black rectangle at the top and a small black rectangle at the bottom. The right lifeline has a black rectangle at the top and a small black rectangle at the bottom. A horizontal arrow points from the right lifeline to the left lifeline, passing through the black rectangles at the top.](a83c022a6dac411615bcc38b7cd0d573_img.jpg) + +Sequence diagram for Deactivate trace procedure. It shows two vertical lifelines. The left lifeline has a black rectangle at the top and a small black rectangle at the bottom. The right lifeline has a black rectangle at the top and a small black rectangle at the bottom. A horizontal arrow points from the right lifeline to the left lifeline, passing through the black rectangles at the top. + +**Figure 8.11.3.2-1: Deactivate trace** + +The AMF initiates the procedure by sending a DEACTIVATE TRACE message to the NG-RAN node as described in TS 32.422 [11]. Upon reception of the DEACTIVATE TRACE message, the NG-RAN node shall stop the trace session for the indicated trace reference in the *NG-RAN Trace ID* IE. + +#### Interactions with other procedures: + +If the NG-RAN node is not able to stop the trace session due to ongoing handover of the UE to another NG-RAN node, the NG-RAN node shall initiate a Trace Failure Indication procedure with the appropriate cause value. + +### 8.11.3.3 Abnormal Conditions + +Void. + +## 8.11.4 Cell Traffic Trace + +### 8.11.4.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 AMF. The procedure uses UE-associated signalling. + +### 8.11.4.2 Successful Operation + +![Sequence diagram for Cell traffic trace procedure. It shows two vertical lifelines. The left lifeline has a black rectangle at the top and a small black rectangle at the bottom. The right lifeline has a black rectangle at the top and a small black rectangle at the bottom. A horizontal arrow points from the left lifeline to the right lifeline, passing through the black rectangles at the top.](3d9614f297f466a7c9b0f4b74f6aaf03_img.jpg) + +Sequence diagram for Cell traffic trace procedure. It shows two vertical lifelines. The left lifeline has a black rectangle at the top and a small black rectangle at the bottom. The right lifeline has a black rectangle at the top and a small black rectangle at the bottom. A horizontal arrow points from the left lifeline to the right lifeline, passing through the black rectangles at the top. + +**Figure 8.11.4.2-1: Cell traffic trace** + +The NG-RAN node initiates the procedure by sending a CELL TRAFFIC TRACE message. + +If the *Privacy Indicator* IE is included in the message, the AMF shall take the information into account for anonymization of MDT data as described in TS 32.422 [11]. + +### 8.11.4.3 Abnormal Conditions + +Void. + +## 8.12 Location Reporting Procedures + +### 8.12.1 Location Reporting Control + +#### 8.12.1.1 General + +The purpose of the Location Reporting Control procedure is to allow the AMF to request the NG-RAN node to report the UE's current location, or the UE's last known location with time stamp, or the UE's presence in the area of interest while in CM-CONNECTED state as specified in TS 23.501 [9] and TS 23.502 [10]. The procedure uses UE-associated signalling. + +#### 8.12.1.2 Successful Operation + +![Diagram illustrating the Location reporting control procedure. A large black rectangle represents the NG-RAN node, with a white rectangle inside its top right corner. Below the main black rectangle, there are two smaller black rectangles representing the UE. A horizontal line with an arrow pointing left connects the right UE to the NG-RAN node, representing the LOCATION REPORTING CONTROL message.](5de3d4570bdb30251a009a25795993e9_img.jpg) + +Diagram illustrating the Location reporting control procedure. A large black rectangle represents the NG-RAN node, with a white rectangle inside its top right corner. Below the main black rectangle, there are two smaller black rectangles representing the UE. A horizontal line with an arrow pointing left connects the right UE to the NG-RAN node, representing the LOCATION REPORTING CONTROL message. + +**Figure 8.12.1.2-1: Location reporting control** + +The AMF initiates the procedure by sending a LOCATION REPORTING CONTROL message to the NG-RAN node. On receipt of the LOCATION REPORTING CONTROL message the NG-RAN node shall perform the requested location reporting control action for the UE. + +The *Location Reporting Request Type* IE indicates to the NG-RAN node whether: + +- to report directly; +- to report upon change of serving cell; +- to report UE presence in the area of interest; +- to stop reporting at change of serving cell; +- to stop reporting UE presence in the area of interest; +- to cancel location reporting for the UE; +- to report upon change of serving cell and to report UE presence in the area of interest. + +If the *Area Of Interest List* IE is included in the *Location Reporting Request Type* IE in the LOCATION REPORTING CONTROL message, the NG-RAN node shall store this information and use it to track the UE's presence in the area of interest as defined in TS 23.502 [10]. + +NOTE: The NG-RAN reports the UE presence for all set of Location Reporting Reference IDs for inter-NG-RAN node handover. + +If the *Additional Location Information* IE is included in the LOCATION REPORTING CONTROL message and set to "Include PSCell" then, if Dual Connectivity is activated, the NG-RAN node shall include the current PSCell in the report. If a report upon change of serving cell is requested, the NG-RAN node shall provide the report also whenever the UE changes the PSCell, and when Dual Connectivity is activated. + +If reporting upon change of serving cell is requested, the NG-RAN node shall send a report immediately and shall send a report whenever the UE's location changes. + +If the *Event Type* IE is set to "stop UE presence in the area of interest", and if the *Additional Cancelled Location Reporting Reference ID List* IE is included in the *Location Reporting Request Type* IE within the LOCATION REPORTING CONTROL message, the NG-RAN node shall, if supported, stop reporting UE presence for all received Location Reporting Reference IDs. + +### 8.12.1.3 Abnormal Conditions + +#### Interactions with Location Reporting Failure Indication procedure: + +If the NG-RAN node receives a LOCATION REPORTING CONTROL message containing several *Location Reporting Reference ID* IE set to the same value, the NG-RAN node shall send the LOCATION REPORTING FAILURE INDICATION message with an appropriate cause value. + +If the *Location Reporting Request Type* IE in the received LOCATION REPORTING CONTROL message contains the *Event Type* IE set to neither "UE presence in the area of interest" nor "change of serving cell and UE presence in the Area of Interest", but the *Area of Interest List* IE is present, the NG-RAN node shall ignore the *Area of Interest List* IE, and proceed with the Location Reporting Procedure. + +## 8.12.2 Location Reporting Failure Indication + +### 8.12.2.1 General + +The purpose of the Location Reporting Failure Indication procedure is to allow the NG-RAN node to inform the AMF that the location reporting request contained in the Location Reporting Control procedure, the Handover Resource Allocation procedure or the Initial Context Setup procedure has failed. The procedure uses UE-associated signalling. + +### 8.12.2.2 Successful Operation + +![Sequence diagram illustrating the Location reporting failure indication procedure. A vertical line on the left represents the NG-RAN node, and a vertical line on the right represents the AMF. A message arrow points from the NG-RAN node to the AMF. The AMF is represented by a large black rectangle with a white rectangle in its top right corner. The NG-RAN node is represented by a small black rectangle at the bottom left.](3688d0bf7f55bb025d194f921007f471_img.jpg) + +``` +sequenceDiagram + participant NG-RAN + participant AMF + Note right of AMF: AMF (Black box with white top-right corner) + NG-RAN->>AMF: LOCATION REPORTING FAILURE INDICATION + Note left of NG-RAN: NG-RAN (Small black box) +``` + +Sequence diagram illustrating the Location reporting failure indication procedure. A vertical line on the left represents the NG-RAN node, and a vertical line on the right represents the AMF. A message arrow points from the NG-RAN node to the AMF. The AMF is represented by a large black rectangle with a white rectangle in its top right corner. The NG-RAN node is represented by a small black rectangle at the bottom left. + +Figure 8.12.2.2-1: Location reporting failure indication + +The NG-RAN node initiates the procedure by sending a LOCATION REPORTING FAILURE INDICATION message to the AMF. Upon reception of the LOCATION REPORTING FAILURE INDICATION message the AMF shall, based on the failure reason indicated by the *Cause* IE, take appropriate action. + +### 8.12.2.3 Abnormal Conditions + +Void. + +## 8.12.3 Location Report + +### 8.12.3.1 General + +The purpose of the Location Report procedure is to provide the UE's current location, the UE's last known location with time stamp, or the UE's presence in the area of interest to the AMF. The procedure uses UE-associated signalling. + +### 8.12.3.2 Successful Operation + +![Sequence diagram for Figure 8.12.3.2-1: Location report. The diagram shows two lifelines: NG-RAN (top) and AMF (bottom). The NG-RAN node sends a LOCATION REPORT message to the AMF. The AMF responds with a LOCATION REPORT RESPONSE message. The NG-RAN node then sends a LOCATION REPORT COMPLETE message to the AMF.](b14bb69bbf2f5c6daa53581440a858be_img.jpg) + +``` +sequenceDiagram + participant NG-RAN + participant AMF + Note left of NG-RAN: NG-RAN initiates Location Report + NG-RAN->>AMF: LOCATION REPORT + AMF-->>NG-RAN: LOCATION REPORT RESPONSE + NG-RAN->>AMF: LOCATION REPORT COMPLETE +``` + +Sequence diagram for Figure 8.12.3.2-1: Location report. The diagram shows two lifelines: NG-RAN (top) and AMF (bottom). The NG-RAN node sends a LOCATION REPORT message to the AMF. The AMF responds with a LOCATION REPORT RESPONSE message. The NG-RAN node then sends a LOCATION REPORT COMPLETE message to the AMF. + +**Figure 8.12.3.2-1: Location report** + +The NG-RAN node initiates the procedure by sending a LOCATION REPORT message to the AMF. The LOCATION REPORT message may be used as a response to the LOCATION REPORTING CONTROL message. + +### 8.12.3.3 Abnormal Conditions + +Void. + +## 8.13 UE TNLA Binding Procedures + +### 8.13.1 UE TNLA Binding Release + +#### 8.13.1.1 General + +The purpose of the UE TNLA Binding Release procedure is to request the NG-RAN node to release the NGAP UE TNLA binding, while requesting the NG-RAN node to maintain NG-U (user plane connectivity) and UE context information as specified in TS 23.502 [10]. The procedure uses UE-associated signalling. + +### 8.13.1.2 Successful Operation + +![Sequence diagram for UE TNLA binding release request. A UE (User Equipment) sends a message to the NG-RAN node. The NG-RAN node then sends a message to the AMF (Access and Management Function).](ceb6fe29e2d57711907569c31182b3c2_img.jpg) + +The diagram shows a sequence of messages for the 'UE TNLA binding release request'. It consists of three lifelines: UE, NG-RAN, and AMF. The UE sends a message to the NG-RAN node. The NG-RAN node then sends a message to the AMF. The AMF sends a response back to the NG-RAN node, which in turn sends a response back to the UE. + +Sequence diagram for UE TNLA binding release request. A UE (User Equipment) sends a message to the NG-RAN node. The NG-RAN node then sends a message to the AMF (Access and Management Function). + +**Figure 8.13.1.2-1: UE TNLA binding release request** + +At reception of the UE TNLA BINDING RELEASE REQUEST message, the NG-RAN node shall release the UE TNLA binding for the UE indicated in the UE TNLA BINDING RELEASE REQUEST message. The NG-RAN node shall keep the NG-U (user plane connectivity) and UE context information for the UE, and behave according to TS 23.502 [10]. + +### 8.13.1.3 Abnormal Conditions + +Void. + +## 8.14 UE Radio Capability Management Procedures + +### 8.14.1 UE Radio Capability Info Indication + +#### 8.14.1.1 General + +The purpose of the UE Radio Capability Info Indication procedure is to enable the NG-RAN node to provide to the AMF UE radio capability-related information. The procedure uses UE-associated signalling. + +#### 8.14.1.2 Successful Operation + +![Sequence diagram for UE radio capability info indication. The NG-RAN node sends a message to the AMF. The AMF sends a response back to the NG-RAN node.](66d5189a924662748cac6a9b22a272e9_img.jpg) + +The diagram shows a sequence of messages for the 'UE radio capability info indication'. It consists of three lifelines: NG-RAN, AMF, and UE. The NG-RAN node sends a message to the AMF. The AMF sends a response back to the NG-RAN node. The NG-RAN node then sends a message to the UE. + +Sequence diagram for UE radio capability info indication. The NG-RAN node sends a message to the AMF. The AMF sends a response back to the NG-RAN node. + +**Figure 8.14.1.2-1: UE radio capability info indication** + +The NG-RAN node controlling a UE-associated logical NG connection initiates the procedure by sending a UE RADIO CAPABILITY INFO INDICATION message to the AMF including the UE radio capability information. + +The UE RADIO CAPABILITY INFO INDICATION message may also include paging specific UE radio capability information within the *UE Radio Capability for Paging* IE. If the *UE Radio Capability for Paging* IE includes the *UE Radio Capability for Paging of NR* IE and the *UE Radio Capability for Paging of E-UTRA* IE, the AMF shall, if supported, use it as specified in TS 23.501 [9]. + +The UE radio capability information received by the AMF shall replace previously stored corresponding UE radio capability information in the AMF for the UE, as described in TS 23.501 [9]. + +If the UE RADIO CAPABILITY INFO INDICATION message includes the *UE Radio Capability – E-UTRA Format* IE, the AMF shall, if supported, use it as specified in TS 23.501 [9]. + +### 8.14.1.3 Abnormal Conditions + +Void. + +## 8.14.2 UE Radio Capability Check + +### 8.14.2.1 General + +The purpose of the UE Radio Capability Check procedure is for the AMF to request the NG-RAN node to derive and provide an indication to the AMF on whether the UE radio capabilities are compatible with the network configuration for IMS voice. The procedure uses UE-associated signalling. + +### 8.14.2.2 Successful Operation + +![Sequence diagram illustrating the successful operation of the UE radio capability check procedure. The diagram shows two vertical lifelines representing the AMF (left) and the NG-RAN node (right). A horizontal arrow points from the AMF lifeline to the NG-RAN node lifeline, representing the UE RADIO CAPABILITY CHECK REQUEST message. The AMF lifeline is shown as a thick black rectangle with a white rectangular box at the top right. The NG-RAN node lifeline is shown as a thin black rectangle. Both lifelines end in short horizontal bars at the bottom.](7f7718a1d18d1f9055d85871d02364b3_img.jpg) + +Sequence diagram illustrating the successful operation of the UE radio capability check procedure. The diagram shows two vertical lifelines representing the AMF (left) and the NG-RAN node (right). A horizontal arrow points from the AMF lifeline to the NG-RAN node lifeline, representing the UE RADIO CAPABILITY CHECK REQUEST message. The AMF lifeline is shown as a thick black rectangle with a white rectangular box at the top right. The NG-RAN node lifeline is shown as a thin black rectangle. Both lifelines end in short horizontal bars at the bottom. + +**Figure 8.14.2.2-1: UE radio capability check procedure: successful operation** + +The AMF initiates the procedure by sending a UE RADIO CAPABILITY CHECK REQUEST message. If the UE-associated logical NG-connection is not established, the AMF shall allocate a unique AMF UE NGAP ID to be used for the UE and include the *AMF UE NGAP ID* IE in the UE RADIO CAPABILITY CHECK REQUEST message; by receiving the *AMF UE NGAP ID* IE in the UE RADIO CAPABILITY CHECK REQUEST message, the NG-RAN node establishes the UE-associated logical NG-connection. + +Upon receipt of the UE RADIO CAPABILITY CHECK REQUEST message, the NG-RAN node checks whether the UE radio capabilities are compatible with the network configuration for IMS voice, and responds with a UE RADIO CAPABILITY CHECK RESPONSE message, as defined in TS 23.502 [10]. + +If the *UE Radio Capability* IE is contained in the UE RADIO CAPABILITY CHECK REQUEST message, the NG-RAN node shall use it to determine the value of the *IMS Voice Support Indicator* IE to be included in the UE RADIO CAPABILITY CHECK RESPONSE message. + +If the UE RADIO CAPABILITY CHECK REQUEST message contains the *UE Radio Capability ID* IE, the NG-RAN node shall, if supported, use it as specified in TS 23.501 [9] and TS 23.502 [10]. + +### 8.14.2.3 Unsuccessful Operation + +Not applicable. + +#### 8.14.2.4 Abnormal Conditions + +Void. + +### 8.14.3 UE Radio Capability ID Mapping + +#### 8.14.3.1 General + +The purpose of the UE Radio Capability ID Mapping procedure is for the NG-RAN node to request from the AMF UE Radio Capability information mapped to the UE Radio Capability ID. + +The procedure uses non UE-associated signalling. + +#### 8.14.3.2 Successful Operation + +![Sequence diagram showing the successful operation of the UE Radio Capability ID Mapping procedure between an NG-RAN node and an AMF.](24b10c86fe55f7126e355d9bc6fef7b9_img.jpg) + +``` +sequenceDiagram + participant NG-RAN node + participant AMF + Note left of NG-RAN node: + NG-RAN node->>AMF: UE RADIO CAPABILITY ID MAPPING REQUEST + Note right of AMF: + AMF-->>NG-RAN node: UE RADIO CAPABILITY ID MAPPING RESPONSE + Note left of NG-RAN node: + Note right of AMF: +``` + +The diagram illustrates the successful operation of the UE Radio Capability ID Mapping procedure. It features two vertical lifelines: 'NG-RAN node' on the left and 'AMF' on the right. The NG-RAN node sends a 'UE RADIO CAPABILITY ID MAPPING REQUEST' message to the AMF. The AMF responds with a 'UE RADIO CAPABILITY ID MAPPING RESPONSE' message. Both lifelines have a thick horizontal bar at the bottom, indicating the end of the sequence. + +Sequence diagram showing the successful operation of the UE Radio Capability ID Mapping procedure between an NG-RAN node and an AMF. + +**Figure 8.14.3.2-1: UE Radio Capability ID Mapping procedure: successful operation** + +The NG-RAN node initiates the procedure by sending a UE RADIO CAPABILITY ID MAPPING REQUEST message. + +Upon receipt of the UE RADIO CAPABILITY ID MAPPING REQUEST message, the AMF shall provide within the UE RADIO CAPABILITY ID MAPPING RESPONSE message the UE Radio Capability information mapped to the UE Capability ID indicated in the UE RADIO CAPABILITY ID MAPPING REQUEST message. + +#### 8.14.3.3 Unsuccessful Operation + +Not applicable. + +#### 8.14.3.4 Abnormal Conditions + +Void. + +### 8.15 Data Usage Reporting Procedures + +#### 8.15.1 Secondary RAT Data Usage Report + +##### 8.15.1.1 General + +The purpose of the Secondary RAT Data Usage Report procedure is to provide information on the used resources of the secondary RAT (e.g. NR resources during MR-DC operation) as specified in TS 23.501 [9]. The procedure uses UE-associated signalling. + +### 8.15.1.2 Successful Operation + +![Diagram illustrating the Secondary RAT data usage report procedure. A large black rectangle represents the NG-RAN node, with a white rectangle inside its top right corner. Below the rectangle, two vertical lines extend downwards to two small black horizontal bars. A horizontal arrow points from the left vertical line to the right vertical line, indicating the flow of the report from the NG-RAN node to the AMF.](da87c1b628b63a046d8a0d0fc2c058ea_img.jpg) + +Diagram illustrating the Secondary RAT data usage report procedure. A large black rectangle represents the NG-RAN node, with a white rectangle inside its top right corner. Below the rectangle, two vertical lines extend downwards to two small black horizontal bars. A horizontal arrow points from the left vertical line to the right vertical line, indicating the flow of the report from the NG-RAN node to the AMF. + +**Figure 8.15.1.2-1: Secondary RAT data usage report** + +The NG-RAN node initiates the procedure by sending the SECONDARY RAT DATA USAGE REPORT message to the AMF. + +If the *Handover Flag* IE is included in the SECONDARY RAT DATA USAGE REPORT message, it indicates that for each PDU session the AMF should buffer the *Secondary RAT Data Usage Report Transfer* IE since the secondary RAT data usage report is sent due to handover as defined in TS 23.502 [10]. + +For each PDU session for which the *Secondary RAT Usage Information List* IE is included in the the *Secondary RAT Data Usage Transfer* IE, the SMF shall handle this information as specified in TS 23.502 [10]. + +The NG-RAN node shall, if supported, report in the SECONDARY RAT DATA USAGE REPORT message location information of the UE in the *User Location Information* IE. + +### 8.15.1.3 Abnormal Conditions + +Void. + +## 8.16 RIM Information Transfer Procedures + +### 8.16.1 Uplink RIM Information Transfer + +#### 8.16.1.1 General + +The purpose of the Uplink RIM Information Transfer procedure is to transfer RIM information from the NG-RAN node to the AMF. The AMF does not interpret the transferred RIM information. This procedure uses non-UE associated signalling. + +### 8.16.1.2 Successful Operation + +![Sequence diagram for Uplink RIM Information Transfer](3d590ad29ecfe728f07432e6fcb59064_img.jpg) + +A sequence diagram showing the interaction between an NG-RAN node and an AMF. The NG-RAN node is on the left and the AMF is on the right. A horizontal arrow labeled "UPLINK RIM INFORMATION TRANSFER" points from the NG-RAN node to the AMF. Both entities have a vertical lifeline extending downwards from their respective boxes. + +Sequence diagram for Uplink RIM Information Transfer + +**Figure 8.16.1.2-1: Uplink RIM Information Transfer** + +The NG-RAN node initiates the procedure by sending an UPLINK RIM INFORMATION TRANSFER message to the AMF. + +Upon reception of the UPLINK RIM INFORMATION TRANSFER message, the AMF shall transparently transfer it towards the NG-RAN node indicated in the *Target RAN Node ID* IE. + +### 8.16.1.3 Abnormal Conditions + +Void. + +## 8.16.2 Downlink RIM Information Transfer + +### 8.16.2.1 General + +The purpose of the Downlink RIM Information Transfer procedure is to transfer RIM information from the AMF to the NG-RAN node. This procedure uses non-UE associated signalling. + +### 8.16.2.2 Successful Operation + +![Sequence diagram for Downlink RIM Information Transfer](653c8e65f33b3bb03c92688243b27ab5_img.jpg) + +A sequence diagram showing the interaction between an AMF and an NG-RAN node. The AMF is on the right and the NG-RAN node is on the left. A horizontal arrow labeled "DOWNLINK RIM INFORMATION TRANSFER" points from the AMF to the NG-RAN node. Both entities have a vertical lifeline extending downwards from their respective boxes. + +Sequence diagram for Downlink RIM Information Transfer + +**Figure 8.16.2.2-1: Downlink RIM Information Transfer** + +The AMF initiates the procedure by sending a DOWNLINK RIM INFORMATION TRANSFER message to the NG-RAN node. The NG-RAN node may use the RIM information in the received DOWNLINK RIM INFORMATION TRANSFER message for executing the RIM functionality, as specified in TS 38.300 [8]. + +### 8.16.2.3 Abnormal Conditions + +Void. + +## 8.17 Broadcast Session Management Procedures + +### 8.17.1 Broadcast Session Setup + +#### 8.17.1.1 General + +The purpose of the Broadcast Session Setup procedure is to request the NG-RAN node to setup MBS session resources for a broadcast MBS session. The procedure uses non-UE associated signalling. + +#### 8.17.1.2 Successful Operation + +![Sequence diagram showing the successful operation of Broadcast Session Setup. The AMF sends a BROADCAST SESSION SETUP REQUEST message to the NG-RAN node, and the NG-RAN node responds with a BROADCAST SESSION SETUP RESPONSE message.](ff6ed9ff347451f49c87007e1a1b92f6_img.jpg) + +``` +sequenceDiagram + participant AMF + participant NG-RAN node + Note left of NG-RAN node: + AMF->>NG-RAN node: BROADCAST SESSION SETUP REQUEST + NG-RAN node-->>AMF: BROADCAST SESSION SETUP RESPONSE + Note right of AMF: +``` + +Sequence diagram showing the successful operation of Broadcast Session Setup. The AMF sends a BROADCAST SESSION SETUP REQUEST message to the NG-RAN node, and the NG-RAN node responds with a BROADCAST SESSION SETUP RESPONSE message. + +**Figure 8.17.1.2-1: Broadcast Session Setup, successful operation.** + +The AMF initiates the procedure by sending a BROADCAST SESSION SETUP REQUEST message to the NG-RAN node. If the NG-RAN node accepts all the MBS QoS flows in the MBS session at least in one of its cells, the NG-RAN node responds with the BROADCAST SESSION SETUP RESPONSE message. + +If the *MBS Service Area* IE is included in the BROADCAST SESSION SETUP REQUEST message, the NG-RAN node shall take it into account as specified in TS 23.247 [44]. + +If the *MBS Session FSA ID List* IE is included in the BROADCAST SESSION SETUP REQUEST message, the NG-RAN node shall take it into account to determine cells/frequencies within the MBS service area to broadcast MBS session data as specified in TS 23.247 [44]. + +If the *Supported UE Type List* IE is included in the BROADCAST SESSION SETUP REQUEST message, the NG-RAN node shall, if supported, take it into account for configuring MBS session resources. + +If the *Associated Session ID* IE is included in the BROADCAST SESSION SETUP REQUEST message the NG-RAN node shall, if supported, take this information into account to determine whether MBS session resource sharing is possible, as specified in TS 38.300 [8]. If the NG-RAN node decides to not establish shared NG-U resources towards the 5GC it shall include the *Shared NG-U Not Established* IE set to "not established" in the *MBS Session Setup or Modification Response Transfer* IE. + +### 8.17.1.3 Unsuccessful Operation + +![Sequence diagram for Broadcast Session Setup, unsuccessful operation. The AMF sends a BROADCAST SESSION SETUP REQUEST to the NG-RAN node, which responds with a BROADCAST SESSION SETUP FAILURE.](c1bf17571f9cedf76c4072121295d10e_img.jpg) + +``` +sequenceDiagram + participant AMF + participant NG-RAN node + Note left of NG-RAN node: + AMF->>NG-RAN node: BROADCAST SESSION SETUP REQUEST + NG-RAN node-->>AMF: BROADCAST SESSION SETUP FAILURE + Note right of AMF: +``` + +Sequence diagram for Broadcast Session Setup, unsuccessful operation. The AMF sends a BROADCAST SESSION SETUP REQUEST to the NG-RAN node, which responds with a BROADCAST SESSION SETUP FAILURE. + +**Figure 8.17.1.3-1: Broadcast Session Setup, unsuccessful operation.** + +If the NG-RAN node is not able to provide the requested MBS session resources for all the MBS QoS flows in the MBS session in any of its cells, it shall send the BROADCAST SESSION SETUP FAILURE message. + +### 8.17.1.4 Abnormal Conditions + +Void. + +## 8.17.2 Broadcast Session Modification + +### 8.17.2.1 General + +The purpose of the Broadcast Session Modification procedure is to request the NG-RAN node to update the MBS session resources or the area related to a previously established broadcast MBS session. The procedure uses non-UE associated signalling. + +### 8.17.2.2 Successful Operation + +![Sequence diagram for Broadcast Session Modification, successful operation. The AMF sends a BROADCAST SESSION MODIFICATION REQUEST to the NG-RAN node, which responds with a BROADCAST SESSION MODIFICATION RESPONSE.](6ac768852938a68d913005126c4d9e8a_img.jpg) + +``` +sequenceDiagram + participant AMF + participant NG-RAN node + Note left of NG-RAN node: + AMF->>NG-RAN node: BROADCAST SESSION MODIFICATION REQUEST + NG-RAN node-->>AMF: BROADCAST SESSION MODIFICATION RESPONSE + Note right of AMF: +``` + +Sequence diagram for Broadcast Session Modification, successful operation. The AMF sends a BROADCAST SESSION MODIFICATION REQUEST to the NG-RAN node, which responds with a BROADCAST SESSION MODIFICATION RESPONSE. + +**Figure 8.17.2.2-1: Broadcast Session Modification, successful operation.** + +The AMF initiates the procedure by sending a BROADCAST SESSION MODIFICATION REQUEST message to the NG-RAN node. + +If the *MBS Service Area* IE is included in the BROADCAST SESSION MODIFICATION REQUEST message, the NG-RAN node shall update the MBS service area and send the BROADCAST SESSION MODIFICATION RESPONSE message. + +If the *MBS Session Modification Request Transfer* IE is included in the BROADCAST SESSION MODIFICATION REQUEST message, the NG-RAN node shall replace the previously provided information by the newly received one and update the MBS session resources and area as requested and send the BROADCAST SESSION MODIFICATION RESPONSE message. + +If the *Supported UE Type List* IE is included in the BROADCAST SESSION MODIFICATION REQUEST message, the NG-RAN node shall, if supported, take it into account for configuring MBS session resources. + +### 8.17.2.3 Unsuccessful Operation + +![Sequence diagram for Broadcast Session Modification, unsuccessful operation. The AMF sends a BROADCAST SESSION MODIFICATION REQUEST to the NG-RAN node, and the NG-RAN node responds with a BROADCAST SESSION MODIFICATION FAILURE.](93bc9e79386c488b5f130ab90aacf464_img.jpg) + +``` +sequenceDiagram + participant AMF + participant NG-RAN node + Note left of NG-RAN node: + AMF->>NG-RAN node: BROADCAST SESSION MODIFICATION REQUEST + Note right of NG-RAN node: + NG-RAN node-->>AMF: BROADCAST SESSION MODIFICATION FAILURE + Note right of AMF: +``` + +Sequence diagram for Broadcast Session Modification, unsuccessful operation. The AMF sends a BROADCAST SESSION MODIFICATION REQUEST to the NG-RAN node, and the NG-RAN node responds with a BROADCAST SESSION MODIFICATION FAILURE. + +**Figure 8.17.2.3-1: Broadcast Session Modification, unsuccessful operation.** + +If the NG-RAN node fails to update any requested modification, the NG-RAN node shall send the BROADCAST SESSION MODIFICATION FAILURE message. + +### 8.17.2.4 Abnormal Conditions + +Void. + +## 8.17.3 Broadcast Session Release + +### 8.17.3.1 General + +The purpose of the Broadcast Session Release procedure is to release the MBS session resources related to a previously established broadcast MBS session. The procedure uses non-UE associated signalling. + +### 8.17.3.2 Successful Operation + +![Sequence diagram for Broadcast Session Release, successful operation. The AMF sends a BROADCAST SESSION RELEASE REQUEST to the NG-RAN node, and the NG-RAN node responds with a BROADCAST SESSION RELEASE RESPONSE.](e67bca96ac67ddab7a8762b49d4c438d_img.jpg) + +``` +sequenceDiagram + participant AMF + participant NG-RAN node + Note left of NG-RAN node: + AMF->>NG-RAN node: BROADCAST SESSION RELEASE REQUEST + Note right of NG-RAN node: + NG-RAN node-->>AMF: BROADCAST SESSION RELEASE RESPONSE + Note right of AMF: +``` + +Sequence diagram for Broadcast Session Release, successful operation. The AMF sends a BROADCAST SESSION RELEASE REQUEST to the NG-RAN node, and the NG-RAN node responds with a BROADCAST SESSION RELEASE RESPONSE. + +**Figure 8.17.3.2-1: Broadcast Session Release, successful operation.** + +The AMF initiates the procedure by sending a BROADCAST SESSION RELEASE REQUEST message to the NG-RAN node. + +Upon reception of the BROADCAST SESSION RELEASE REQUEST message, the NG-RAN node shall respond with the BROADCAST SESSION RELEASE RESPONSE message. The NG-RAN node shall stop broadcasting and release all MBS session resources associated with the broadcast session. + +Upon reception of the BROADCAST SESSION RELEASE RESPONSE message, the AMF shall transfer transparently the *Broadcast Session Release Response Transfer* IE, if available, to the MB-SMF. + +### 8.17.3.3 Unsuccessful Operation + +Not applicable. + +### 8.17.3.4 Abnormal Conditions + +Void. + +## 8.17.4 Broadcast Session Release Required + +### 8.17.4.1 General + +The purpose of the Broadcast Session Release Required procedure is to trigger the AMF to release the MBS session resources related to a previously established broadcast MBS session. The procedure uses non-UE associated signalling. + +### 8.17.4.2 Successful Operation + +![Sequence diagram showing the successful operation of the Broadcast Session Release Required procedure. An NG-RAN node sends a BROADCAST SESSION RELEASE REQUIRED message to the AMF.](161bf538038ac4e9c2cd42f8d9dbd732_img.jpg) + +``` +sequenceDiagram + participant NG-RAN node + participant AMF + Note left of NG-RAN node: + NG-RAN node->>AMF: BROADCAST SESSION RELEASE REQUIRED + Note right of AMF: +``` + +Sequence diagram showing the successful operation of the Broadcast Session Release Required procedure. An NG-RAN node sends a BROADCAST SESSION RELEASE REQUIRED message to the AMF. + +**Figure 8.17.4.2-1: Broadcast Session Release Required, successful operation.** + +The NG-RAN node initiates the procedure by sending a BROADCAST SESSION RELEASE REQUIRED message to the AMF. + +Upon reception of the BROADCAST SESSION RELEASE REQUIRED message, the AMF shall realize that the NG-RAN node is lacking adequate MBS session resources for a previously established broadcast MBS session and initiate the release of the MBS session resources. + +### 8.17.4.3 Abnormal Conditions + +Void. + +## 8.17.5 Broadcast Session Transport + +### 8.17.5.1 General + +The purpose of the Broadcast Session Transport procedure is to assign NG-U resources for a broadcast MBS session. The procedure uses non-UE associated signalling. + +### 8.17.5.2 Successful Operation + +![Sequence diagram for Successful Operation of Broadcast Session Transport](b15cf8c50195a52cca59b4645c6f59fa_img.jpg) + +``` +sequenceDiagram + participant NG-RAN node + participant AMF + Note left of NG-RAN node: + NG-RAN node->>AMF: BROADCAST SESSION TRANSPORT REQUEST + Note right of AMF: + AMF-->>NG-RAN node: BROADCAST SESSION TRANSPORT RESPONSE + Note left of NG-RAN node: +``` + +The diagram shows a sequence of messages between an NG-RAN node and an AMF. The NG-RAN node sends a 'BROADCAST SESSION TRANSPORT REQUEST' to the AMF, and the AMF responds with a 'BROADCAST SESSION TRANSPORT RESPONSE'. Both messages are shown as horizontal arrows between the two entities, which are represented by boxes with vertical lines extending downwards to a horizontal bar. + +Sequence diagram for Successful Operation of Broadcast Session Transport + +**Figure 8.17.5.2-1: Broadcast Session Transport, successful operation.** + +The NG-RAN node initiates the procedure by sending a BROADCAST SESSION TRANSPORT REQUEST message to AMF. The AMF responds with a BROADCAST SESSION TRANSPORT RESPONSE message. + +If the *Shared NG-U Unicast TNL Information* IE is included in the *MBS Session TNL Information NG-RAN* IE within the *MBS Session Transport Request Transfer* IE in the BROADCAST SESSION TRANSPORT REQUEST message, the MB-SMF shall use the included information as the downlink termination point for the shared NG-U transport. + +### 8.17.5.3 Unsuccessful Operation + +![Sequence diagram for Unsuccessful Operation of Broadcast Session Transport](3295c6ffe9f6d00c3811c37d327ac844_img.jpg) + +``` +sequenceDiagram + participant NG-RAN node + participant AMF + Note left of NG-RAN node: + NG-RAN node->>AMF: BROADCAST SESSION TRANSPORT REQUEST + Note right of AMF: + AMF-->>NG-RAN node: BROADCAST SESSION TRANSPORT FAILURE + Note left of NG-RAN node: +``` + +The diagram shows a sequence of messages between an NG-RAN node and an AMF. The NG-RAN node sends a 'BROADCAST SESSION TRANSPORT REQUEST' to the AMF, and the AMF responds with a 'BROADCAST SESSION TRANSPORT FAILURE'. Both messages are shown as horizontal arrows between the two entities, which are represented by boxes with vertical lines extending downwards to a horizontal bar. + +Sequence diagram for Unsuccessful Operation of Broadcast Session Transport + +**Figure 8.17.5.3-1: Broadcast Session Transport, unsuccessful operation.** + +In case the shared NG-U transport cannot be setup successfully, the AMF shall respond with the BROADCAST SESSION TRANSPORT FAILURE message to the NG-RAN node with an appropriate cause value. + +### 8.17.5.4 Abnormal Conditions + +Void. + +## 8.18 Multicast Session Management Procedures + +### 8.18.1 Distribution Setup + +#### 8.18.1.1 General + +The purpose of the Distribution Setup procedure is to assign NG-U resources for a multicast MBS session. The procedure uses non-UE-associated signalling. + +### 8.18.1.2 Successful Operation + +![Sequence diagram for Successful Operation of Distribution Setup](ffe2d3e622dd30bea4caf15951c60e42_img.jpg) + +``` +sequenceDiagram + participant NG-RAN node + participant AMF + Note left of NG-RAN node: + NG-RAN node->>AMF: DISTRIBUTION SETUP REQUEST + Note right of AMF: + AMF-->>NG-RAN node: DISTRIBUTION SETUP RESPONSE + Note left of NG-RAN node: +``` + +The diagram illustrates a successful distribution setup procedure. It features two lifelines: 'NG-RAN node' on the left and 'AMF' on the right. The NG-RAN node sends a 'DISTRIBUTION SETUP REQUEST' message to the AMF. The AMF responds with a 'DISTRIBUTION SETUP RESPONSE' message. Both lifelines have a thick horizontal bar at the bottom, indicating the start and end of the procedure. + +Sequence diagram for Successful Operation of Distribution Setup + +**Figure 8.18.1.2-1: Distribution Setup, successful operation.** + +The NG-RAN node initiates the procedure by sending a DISTRIBUTION SETUP REQUEST message to the AMF. The AMF responds with a DISTRIBUTION SETUP RESPONSE message. + +For location dependent multicast sessions, the NG-RAN node shall include the *MBS Area Session ID* IE in the DISTRIBUTION SETUP REQUEST message, and the AMF shall provide the same value of the *MBS Area Session ID* IE in the DISTRIBUTION SETUP RESPONSE message. + +If the *Shared NG-U Unicast TNL Information* IE is included in the *MBS Distribution Setup Request Transfer* IE in the DISTRIBUTION SETUP REQUEST message, the MB-SMF shall use the included information as the downlink termination point for the shared NG-U transport. + +If the *Shared NG-U Unicast TNL Information* IE is not included in the *MBS Distribution Setup Request Transfer* IE in the DISTRIBUTION SETUP REQUEST message, the MB-SMF shall interpret that the IP multicast is used for this shared NG-U transport, and include the *Shared NG-U Multicast TNL Information* IE in the *MBS Distribution Setup Response Transfer* IE in the DISTRIBUTION SETUP RESPONSE message. + +### 8.18.1.3 Unsuccessful Operation + +![Sequence diagram for Unsuccessful Operation of Distribution Setup](03a73cf37615028406f13c2aea732d60_img.jpg) + +``` +sequenceDiagram + participant NG-RAN node + participant AMF + Note left of NG-RAN node: + NG-RAN node->>AMF: DISTRIBUTION SETUP REQUEST + Note right of AMF: + AMF-->>NG-RAN node: DISTRIBUTION SETUP FAILURE + Note left of NG-RAN node: +``` + +The diagram illustrates an unsuccessful distribution setup procedure. It features two lifelines: 'NG-RAN node' on the left and 'AMF' on the right. The NG-RAN node sends a 'DISTRIBUTION SETUP REQUEST' message to the AMF. The AMF responds with a 'DISTRIBUTION SETUP FAILURE' message. Both lifelines have a thick horizontal bar at the bottom, indicating the start and end of the procedure. + +Sequence diagram for Unsuccessful Operation of Distribution Setup + +**Figure 8.18.1.3-1: Distribution Setup, unsuccessful operation.** + +In case the shared NG-U transport cannot be setup successfully, the AMF shall respond with the DISTRIBUTION SETUP FAILURE message to the NG-RAN node with an appropriate cause value. + +### 8.18.1.4 Abnormal Conditions + +Void. + +## 8.18.2 Distribution Release + +### 8.18.2.1 General + +The purpose of the Distribution Release procedure is to enable the release of already established NG-U resources for a given multicast MBS session, or for a given area session of the multicast MBS session. The procedure uses non-UE-associated signalling. + +### 8.18.2.2 Successful Operation + +![Sequence diagram for Distribution Release, successful operation. The diagram shows two lifelines: NG-RAN node and AMF. The NG-RAN node sends a DISTRIBUTION RELEASE REQUEST message to the AMF. The AMF responds with a DISTRIBUTION RELEASE RESPONSE message. Both lifelines end with a thick horizontal bar.](48fecf94dd9fb955caddbf2fb01b7b9b_img.jpg) + +``` +sequenceDiagram + participant NG-RAN node + participant AMF + Note left of NG-RAN node: + NG-RAN node->>AMF: DISTRIBUTION RELEASE REQUEST + Note right of AMF: + AMF-->>NG-RAN node: DISTRIBUTION RELEASE RESPONSE + Note left of NG-RAN node: + Note right of AMF: +``` + +Sequence diagram for Distribution Release, successful operation. The diagram shows two lifelines: NG-RAN node and AMF. The NG-RAN node sends a DISTRIBUTION RELEASE REQUEST message to the AMF. The AMF responds with a DISTRIBUTION RELEASE RESPONSE message. Both lifelines end with a thick horizontal bar. + +Figure 8.18.2.2-1: Distribution Release, successful operation. + +The NG-RAN node initiates the procedure by sending a DISTRIBUTION RELEASE REQUEST message. + +Upon receipt of the DISTRIBUTION RELEASE REQUEST message, the AMF shall send the DISTRIBUTION RELEASE RESPONSE message after successfully removing the corresponding NG-U resource for the MBS session. + +For location dependent multicast session, the NG-RAN node shall include the *MBS Area Session ID* IE in the DISTRIBUTION RELEASE REQUEST message, and the AMF shall provide the same value of the *MBS Area Session ID* IE in the DISTRIBUTION RELEASE RESPONSE message. + +If unicast shared NG-U transport is used, the NG-RAN node shall include the *Shared NG-U TNL Information* IE in the *MBS Distribution Release Request Transfer* IE in the DISTRIBUTION RELEASE REQUEST message, and the MB-SMF shall release the corresponding shared NG-U transport as specified in TS 23.247 [44]. + +### 8.18.2.3 Unsuccessful Operation + +Not applicable. + +### 8.18.2.4 Abnormal Conditions + +Void. + +## 8.18.3 Multicast Session Activation + +### 8.18.3.1 General + +The purpose of the Multicast Session Activation procedure is to request a NG-RAN node to activate the MBS session resources of a multicast MBS session. The procedure uses non-UE-associated signalling. + +### 8.18.3.2 Successful Operation + +![Sequence diagram for Successful Operation of Multicast Session Activation](c5d9ee57705b6598bd43f9c075fec3c7_img.jpg) + +``` +sequenceDiagram + participant AMF + participant NG-RAN node + Note left of NG-RAN node: + AMF->>NG-RAN node: MULTICAST SESSION ACTIVATION REQUEST + NG-RAN node-->>AMF: MULTICAST SESSION ACTIVATION RESPONSE + Note right of AMF: +``` + +The diagram illustrates a successful multicast session activation. It features two vertical lifelines: 'NG-RAN node' on the left and 'AMF' on the right. The AMF sends a 'MULTICAST SESSION ACTIVATION REQUEST' message to the NG-RAN node. The NG-RAN node responds with a 'MULTICAST SESSION ACTIVATION RESPONSE' message. Both lifelines end with a thick horizontal bar, indicating the completion of the interaction. + +Sequence diagram for Successful Operation of Multicast Session Activation + +**Figure 8.18.3.2-1: Multicast Session Activation, successful operation.** + +The AMF initiates the procedure by sending a MULTICAST SESSION ACTIVATION REQUEST message to the NG-RAN node. + +Upon receipt of the MULTICAST SESSION ACTIVATION REQUEST, the NG-RAN node activates the previously requested MBS session resources corresponding to the MBS session indicated in the MULTICAST SESSION ACTIVATION REQUEST message and indicates in the MULTICAST SESSION ACTIVATION RESPONSE message for which MBS session the request was fulfilled. + +### 8.18.3.3 Unsuccessful Operation + +![Sequence diagram for Unsuccessful Operation of Multicast Session Activation](131048f570c4d9960a21e7dd73c4fd6b_img.jpg) + +``` +sequenceDiagram + participant AMF + participant NG-RAN node + Note left of NG-RAN node: + AMF->>NG-RAN node: MULTICAST SESSION ACTIVATION REQUEST + NG-RAN node-->>AMF: MULTICAST SESSION ACTIVATION FAILURE + Note right of AMF: +``` + +The diagram illustrates an unsuccessful multicast session activation. It features two vertical lifelines: 'NG-RAN node' on the left and 'AMF' on the right. The AMF sends a 'MULTICAST SESSION ACTIVATION REQUEST' message to the NG-RAN node. The NG-RAN node responds with a 'MULTICAST SESSION ACTIVATION FAILURE' message. Both lifelines end with a thick horizontal bar, indicating the completion of the interaction. + +Sequence diagram for Unsuccessful Operation of Multicast Session Activation + +**Figure 8.18.3.3-1: Multicast Session Activation, unsuccessful operation.** + +If the NG-RAN node cannot activate the previously requested MBS session resources indicated by the MULTICAST SESSION ACTIVATION REQUEST message, it shall respond with a MULTICAST SESSION ACTIVATION FAILURE message with an appropriate cause value. + +### 8.18.3.4 Abnormal Conditions + +Void. + +## 8.18.4 Multicast Session Deactivation + +### 8.18.4.1 General + +The purpose of the Multicast Session Deactivation procedure is to request a NG-RAN node to deactivate the multicast MBS session resources of one MBS session. The procedure uses non-UE-associated signalling. + +### 8.18.4.2 Successful Operation + +![Sequence diagram for Multicast Session Deactivation, successful operation. The diagram shows two lifelines: NG-RAN node and AMF. The AMF sends a MULTICAST SESSION DEACTIVATION REQUEST message to the NG-RAN node. The NG-RAN node responds with a MULTICAST SESSION DEACTIVATION RESPONSE message to the AMF.](c7e196e0c468cc7b9a84c12c951209a0_img.jpg) + +``` +sequenceDiagram + participant AMF + participant NG-RAN node + Note left of NG-RAN node: + AMF->>NG-RAN node: MULTICAST SESSION DEACTIVATION REQUEST + NG-RAN node-->>AMF: MULTICAST SESSION DEACTIVATION RESPONSE + Note right of AMF: +``` + +Sequence diagram for Multicast Session Deactivation, successful operation. The diagram shows two lifelines: NG-RAN node and AMF. The AMF sends a MULTICAST SESSION DEACTIVATION REQUEST message to the NG-RAN node. The NG-RAN node responds with a MULTICAST SESSION DEACTIVATION RESPONSE message to the AMF. + +**Figure 8.18.4.2-1: Multicast Session Deactivation, successful operation.** + +The AMF initiates the procedure by sending a MULTICAST SESSION DEACTIVATION REQUEST message to the NG-RAN node. + +Upon receipt of this message, the NG-RAN node shall deactivate the previously requested MBS session resources corresponding to the MBS session indicated in the MULTICAST SESSION DEACTIVATION REQUEST message if the MBS resources are active and shall indicate in the MULTICAST SESSION DEACTIVATION RESPONSE message for which MBS session the request was fulfilled. + +### 8.18.4.3 Unsuccessful Operation + +Not applicable. + +### 8.18.4.4 Abnormal Conditions + +Void. + +## 8.18.5 Multicast Session Update + +### 8.18.5.1 General + +The purpose of the Multicast Session Update procedure is to request the NG-RAN node to update the NG-RAN MBS session resources or area related to a multicast MBS session. The procedure uses non-UE associated signalling. + +### 8.18.5.2 Successful Operation + +![Sequence diagram showing the successful operation of a Multicast Session Update. The AMF sends a MULTICAST SESSION UPDATE REQUEST to the NG-RAN node, and the NG-RAN node responds with a MULTICAST SESSION UPDATE RESPONSE.](e29db6b12743ccb6dc6c48860eb8b4fb_img.jpg) + +``` +sequenceDiagram + participant AMF + participant NG-RAN node + Note left of NG-RAN node: NG-RAN node + AMF->>NG-RAN node: MULTICAST SESSION UPDATE REQUEST + NG-RAN node-->>AMF: MULTICAST SESSION UPDATE RESPONSE +``` + +Sequence diagram showing the successful operation of a Multicast Session Update. The AMF sends a MULTICAST SESSION UPDATE REQUEST to the NG-RAN node, and the NG-RAN node responds with a MULTICAST SESSION UPDATE RESPONSE. + +**Figure 8.18.5.2-1: Multicast Session Update, successful operation.** + +The AMF initiates the procedure by sending a MULTICAST SESSION UPDATE REQUEST message to the NG-RAN node. + +Upon receipt of the MULTICAST SESSION UPDATE REQUEST message, the NG-RAN node shall, if requested, update the MBS QoS profile and/or MBS Service Area for the multicast service and send the MULTICAST SESSION UPDATE RESPONSE message to the AMF. + +For location dependent multicast session, the AMF shall include the *MBS Area Session ID* IE in the MULTICAST SESSION UPDATE REQUEST message, and the NG-RAN node shall provide the same value of the *MBS Area Session ID* IE in the MULTICAST SESSION UPDATE RESPONSE message. + +In case the *MBS Service Area Information* IE is included in the *Multicast Session Update Request Transfer* IE in the MULTICAST SESSION UPDATE REQUEST message, the NG-RAN node shall update the stored MBS Service Area Information for that service, as specified in TS 23.247 [44]. + +In case the *MBS QoS Flows To Be Setup or Modify List* IE is included in the *Multicast Session Update Request Transfer* IE in the MULTICAST SESSION UPDATE REQUEST message, the NG-RAN node shall setup or modify the MBS QoS profile accordingly. + +In case the *MBS QoS Flows To Be Release List* IE is included in the *Multicast Session Update Request Transfer* IE in the MULTICAST SESSION UPDATE REQUEST message, the NG-RAN node shall release the indicated MBS QoS flows. + +In case the *MBS Session TNL Information 5GC* IE is included in the *Multicast Session Update Request Transfer* IE in the MULTICAST SESSION UPDATE REQUEST message, the NG-RAN node shall take the information into account and update related NG-U resources. + +### 8.18.5.3 Unsuccessful Operation + +![Sequence diagram for Unsuccessful Operation of Multicast Session Update](18b87e4ce7ef441f5620b8d6539a2939_img.jpg) + +``` +sequenceDiagram + participant AMF + participant NG-RAN node + Note left of NG-RAN node: + AMF->>NG-RAN node: MULTICAST SESSION UPDATE REQUEST + NG-RAN node-->>AMF: MULTICAST SESSION UPDATE FAILURE + Note right of AMF: +``` + +The diagram illustrates the interaction between an AMF and an NG-RAN node for an unsuccessful multicast session update. The AMF sends a 'MULTICAST SESSION UPDATE REQUEST' to the NG-RAN node. The NG-RAN node responds with a 'MULTICAST SESSION UPDATE FAILURE' message. Both entities are shown with lifelines and activation bars at the bottom. + +Sequence diagram for Unsuccessful Operation of Multicast Session Update + +**Figure 8.18.5.3-1: Multicast Session Update, unsuccessful operation.** + +If the NG-RAN node is not able to perform any of the requested update, it shall respond with a MULTICAST SESSION UPDATE FAILURE message with an appropriate cause value. + +### 8.18.5.4 Abnormal Conditions + +Void. + +## 8.19 Timing Synchronisation Status Reporting Procedures + +### 8.19.1 Timing Synchronisation Status + +#### 8.19.1.1 General + +The purpose of the Timing Synchronisation Status procedure is to enable the AMF to request the NG-RAN node to start or stop reporting of RAN timing synchronisation status information as specified in TS 23.501 [9] and TS 23.502 [10]. The procedure uses non-UE associated signalling. + +#### 8.19.1.2 Successful Operation + +![Sequence diagram for Successful Operation of Timing Synchronisation Status procedure](7c239d0d8d8e5ee7edb275ae16c2269e_img.jpg) + +``` +sequenceDiagram + participant AMF + participant NG-RAN node + Note left of NG-RAN node: + AMF->>NG-RAN node: TIMING SYNCHRONISATION STATUS REQUEST + NG-RAN node-->>AMF: TIMING SYNCHRONISATION STATUS RESPONSE + Note right of AMF: +``` + +The diagram illustrates the interaction between an AMF and an NG-RAN node for a successful timing synchronisation status procedure. The AMF sends a 'TIMING SYNCHRONISATION STATUS REQUEST' to the NG-RAN node. The NG-RAN node responds with a 'TIMING SYNCHRONISATION STATUS RESPONSE' message. Both entities are shown with lifelines and activation bars at the bottom. + +Sequence diagram for Successful Operation of Timing Synchronisation Status procedure + +**Figure 8.19.1.2-1: Timing synchronisation status procedure: successful operation** + +The AMF initiates the procedure by sending a TIMING SYNCHRONISATION STATUS REQUEST message to the NG-RAN node. + +If the *RAN TSS Request Type* IE included in the TIMING SYNCHRONISATION STATUS REQUEST message is set to "start", the NG-RAN node shall start the RAN TSS reporting. If the *RAN TSS Request Type* IE is set to "stop", the NG-RAN node shall stop the reporting. + +#### 8.19.1.3 Unsuccessful Operation + +![Sequence diagram for Unsuccessful Operation](8fce89f02626b8a0c50e2245bc3e7ce7_img.jpg) + +``` +sequenceDiagram + participant AMF + participant NG-RAN node + Note left of NG-RAN node: + AMF->>NG-RAN node: TIMING SYNCHRONISATION STATUS REQUEST + Note right of NG-RAN node: + NG-RAN node-->>AMF: TIMING SYNCHRONISATION STATUS FAILURE + Note right of AMF: +``` + +The diagram shows a sequence of messages between an AMF and an NG-RAN node. The AMF sends a 'TIMING SYNCHRONISATION STATUS REQUEST' message to the NG-RAN node. The NG-RAN node responds with a 'TIMING SYNCHRONISATION STATUS FAILURE' message. Both nodes have a thick horizontal bar at the bottom of their lifelines, indicating the start and end of the procedure. + +Sequence diagram for Unsuccessful Operation + +**Figure 8.19.1.3-1: Timing synchronisation status procedure: unsuccessful operation** + +If the NG-RAN node 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.19.1.4 Abnormal Conditions + +Void. + +### 8.19.2 Timing Synchronisation Status Report + +#### 8.19.2.1 General + +The purpose of the Timing Synchronisation Status Report procedure is to enable the NG-RAN node to provide RAN timing synchronisation status information to the AMF as specified in TS 23.501 [9] and TS 23.502 [10]. The procedure uses non-UE associated signalling. + +#### 8.19.2.2 Successful Operation + +![Sequence diagram for Successful Operation](300130063df853c2bf2589510f69dbba_img.jpg) + +``` +sequenceDiagram + participant NG-RAN node + participant AMF + Note left of NG-RAN node: + NG-RAN node->>AMF: TIMING SYNCHRONISATION STATUS REPORT + Note right of AMF: +``` + +The diagram shows a sequence of messages between an NG-RAN node and an AMF. The NG-RAN node sends a 'TIMING SYNCHRONISATION STATUS REPORT' message to the AMF. Both nodes have a thick horizontal bar at the bottom of their lifelines, indicating the start and end of the procedure. + +Sequence diagram for Successful Operation + +**Figure 8.19.2.2-1: Timing synchronisation status report** + +The NG-RAN node initiates the procedure by sending a TIMING SYNCHRONISATION STATUS REPORT message to the AMF. + +#### 8.19.2.3 Abnormal Conditions + +Void. + +## 9 Elements for NGAP Communication + +### 9.0 General + +Subclauses 9.2 and 9.3 present the NGAP 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 [7]. + +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; + +### 9.1 Tabular Format Contents + +#### 9.1.1 Presence + +All IEs are marked mandatory, optional or conditional according to table 9.1.1-1. + +**Table 9.1.1-1: Meaning of content within "Presence" column** + +| Abbreviation | Meaning | +|--------------|------------------------------------------------------------------------------------------------------------------------------------------| +| M | IEs marked as Mandatory (M) shall always be included in the message. | +| O | IEs marked as Optional (O) may or may not be included in the message. | +| C | IEs marked as Conditional (C) shall be included in a message only if the condition is satisfied. Otherwise the IE shall not be included. | + +#### 9.1.2 Criticality + +Each IE or group of IEs may have criticality information applied to it according to table 9.1.2-1. + +**Table 9.1.2-1: Meaning of content within "Criticality" column** + +| Abbreviation | Meaning | +|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| – | No criticality information is applied explicitly. | +| YES | Criticality information is applied. This is usable only for non-repeatable IEs | +| GLOBAL | The IE and all its repetitions together have one common criticality information. This is usable only for repeatable IEs. | +| EACH | Each repetition of the IE has its own criticality information. It is not allowed to assign different criticality values to the repetitions. This is usable only for repeatable IEs. | + +### 9.1.3 Range + +The Range column indicates the allowed number of copies of repetitive IEs/IE groups. + +### 9.1.4 Assigned Criticality + +The Assigned Criticality column provides the actual criticality information as defined in subclause 10.3.2, if applicable. + +## 9.2 Message Functional Definition and Content + +### 9.2.1 PDU Session Management Messages + +#### 9.2.1.1 PDU SESSION RESOURCE SETUP REQUEST + +This message is sent by the AMF and is used to request the NG-RAN node to assign resources on Uu and NG-U for one or several PDU session resources. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------------|----------|--------------------------|--------------------------------------------|------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| RAN Paging Priority | O | | 9.3.3.15 | | YES | ignore | +| NAS-PDU | O | | 9.3.3.4 | | YES | reject | +| PDU Session Resource Setup Request List | | 1 | | | YES | reject | +| >PDU Session Resource Setup Request Item | | 1.. | | | - | | +| >>PDU Session ID | M | | 9.3.1.50 | | - | | +| >>PDU Session NAS-PDU | O | | NAS-PDU
9.3.3.4 | | - | | +| >>S-NSSAI | M | | 9.3.1.24 | | - | | +| >>PDU Session Resource Setup Request Transfer | M | | OCTET STRING | Containing the PDU Session Resource Setup Request Transfer IE specified in subclause 9.3.4.1. | - | | +| >>PDU Session Expected UE Activity Behaviour | O | | Expected UE Activity Behaviour
9.3.1.94 | Expected UE Activity Behaviour for the PDU Session. | YES | ignore | +| UE Aggregate Maximum Bit Rate | O | | 9.3.1.58 | | YES | ignore | +| UE Slice Maximum Bit Rate List | O | | 9.3.1.231 | | YES | ignore | + +| Range bound | Explanation | +|--------------------|-------------------------------------------------------------------| +| maxnoofPDUSessions | Maximum no. of PDU sessions allowed towards one UE. Value is 256. | + +### 9.2.1.2 PDU SESSION RESOURCE SETUP RESPONSE + +This message is sent by the NG-RAN node as a response to the request to assign resources on Uu and NG-U for one or several PDU session resources. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------------|----------|--------------------------|-----------------------|------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | ignore | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | ignore | +| PDU Session Resource Setup Response List | | 0..1 | | | YES | ignore | +| >PDU Session Resource Setup Response Item | | 1.. | | | - | | +| >>PDU Session ID | M | | 9.3.1.50 | | - | | +| >>PDU Session Resource Setup Response Transfer | M | | OCTET STRING | Containing the PDU Session Resource Setup Response Transfer IE specified in subclause 9.3.4.2. | - | | +| PDU Session Resource Failed to Setup List | | 0..1 | | | YES | ignore | +| >PDU Session Resource Failed to Setup Item | | 1.. | | | - | | +| >>PDU Session ID | M | | 9.3.1.50 | | - | | +| >>PDU Session Resource Setup Unsuccessful Transfer | M | | OCTET STRING | Containing the PDU Session Resource Setup Unsuccessful Transfer IE specified in subclause 9.3.4.16. | - | | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | +| User Location Information | O | | 9.3.1.16 | | YES | ignore | + +| Range bound | Explanation | +|--------------------|-------------------------------------------------------------------| +| maxnoofPDUSessions | Maximum no. of PDU sessions allowed towards one UE. Value is 256. | + +### 9.2.1.3 PDU SESSION RESOURCE RELEASE COMMAND + +This message is sent by the AMF and is used to request the NG-RAN node to release already established PDU session resources for a given UE. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------------|----------|--------------------------|-----------------------|---------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| RAN Paging Priority | O | | 9.3.3.15 | | YES | ignore | +| NAS-PDU | O | | 9.3.3.4 | | YES | ignore | +| PDU Session Resource to Release List | | 1 | | | YES | reject | +| >PDU Session Resource to Release Item | | 1.. | | | - | | +| >>PDU Session ID | M | | 9.3.1.50 | | - | | +| >>PDU Session Resource Release Command Transfer | M | | OCTET STRING | Containing the PDU Session Resource Release Command Transfer IE specified in subclause 9.3.4.12. | - | | + +| Range bound | Explanation | +|--------------------|-------------------------------------------------------------------| +| maxnoofPDUSessions | Maximum no. of PDU sessions allowed towards one UE. Value is 256. | + +## 9.2.1.4 PDU SESSION RESOURCE RELEASE RESPONSE + +This message is sent by the NG-RAN node as a response to the request to release already established PDU session resources for a given UE. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------------------|----------|--------------------------|-----------------------|----------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | ignore | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | ignore | +| PDU Session Resource Released List | | 1 | | | YES | ignore | +| >PDU Session Resource Released Item | | 1.. | | | - | | +| >>PDU Session ID | M | | 9.3.1.50 | | - | | +| >>PDU Session Resource Release Response Transfer | M | | OCTET STRING | Containing the PDU Session Resource Release Response Transfer IE specified in subclause 9.3.4.21. | - | | +| User Location Information | O | | 9.3.1.16 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.1.5 PDU SESSION RESOURCE MODIFY REQUEST + +This message is sent by the AMF and is used to request the NG-RAN node to enable modifications of already established PDU session resources for a given UE. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------------|----------|--------------------------|-----------------------------------------|-------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| RAN Paging Priority | O | | 9.3.3.15 | | YES | ignore | +| PDU Session Resource Modify Request List | | 1 | | | YES | reject | +| >PDU Session Resource Modify Request Item | | 1.. | | | - | | +| >>PDU Session ID | M | | 9.3.1.50 | | - | | +| >>NAS-PDU | O | | 9.3.3.4 | | - | | +| >>PDU Session Resource Modify Request Transfer | M | | OCTET STRING | Containing the PDU Session Resource Modify Request Transfer IE specified in subclause 9.3.4.3. | - | | +| >>S-NSSAI | O | | 9.3.1.24 | | YES | reject | +| >>PDU Session Expected UE Activity Behaviour | O | | Expected UE Activity Behaviour 9.3.1.94 | Expected UE Activity Behaviour for the PDU Session. | YES | ignore | + +| Range bound | Explanation | +|--------------------|-------------------------------------------------------------------| +| maxnoofPDUSessions | Maximum no. of PDU sessions allowed towards one UE. Value is 256. | + +### 9.2.1.6 PDU SESSION RESOURCE MODIFY RESPONSE + +This message is sent by the NG-RAN node and is used to report the outcome of the request from the PDU SESSION RESOURCE MODIFY REQUEST message. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------------------|----------|--------------------------|-----------------------|-------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | ignore | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | ignore | +| PDU Session Resource Modify Response List | | 0..1 | | | YES | ignore | +| > PDU Session Resource Modify Response Item | | 1.. | | | - | | +| >>PDU Session ID | M | | 9.3.1.50 | | - | | +| >>PDU Session Resource Modify Response Transfer | M | | OCTET STRING | Containing the PDU Session Resource Modify Response Transfer IE specified in subclause 9.3.4.4. | - | | +| PDU Session Resource Failed to Modify List | | 0..1 | | | YES | ignore | +| > PDU Session Resource Failed to Modify Item | | 1.. | | | - | | +| >>PDU Session ID | M | | 9.3.1.50 | | - | | +| >>PDU Session Resource Modify Unsuccessful Transfer | M | | OCTET STRING | Containing the PDU Session Resource Modify Unsuccessful Transfer IE specified in subclause 9.3.4.17. | - | | +| User Location Information | O | | 9.3.1.16 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +| Range bound | Explanation | +|--------------------|-------------------------------------------------------------------| +| maxnoofPDUSessions | Maximum no. of PDU sessions allowed towards one UE. Value is 256. | + +### 9.2.1.7 PDU SESSION RESOURCE NOTIFY + +This message is sent by the NG-RAN node to notify that the QoS requirements of already established GBR QoS flow(s) for which notification control has been requested are either not fulfilled anymore or fulfilled again by the NG-RAN node. This message can also be sent by the NG-RAN node to notify that PDU session resource(s) for a given UE are released. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------------|----------|--------------------------|-----------------------|---------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| PDU Session Resource Notify List | | 0..1 | | | YES | reject | +| >PDU Session Resource Notify Item | | 1.. | | | - | | +| >>PDU Session ID | M | | 9.3.1.50 | | - | | +| >>PDU Session Resource Notify Transfer | M | | OCTET STRING | Containing the PDU Session Resource Notify Transfer IE specified in subclause 9.3.4.5. | - | | +| PDU Session Resource Released List | | 0..1 | | | YES | ignore | +| >PDU Session Resource Released Item | | 1.. | | | - | | +| >>PDU Session ID | M | | 9.3.1.50 | | - | | +| >>PDU Session Resource Notify Released Transfer | M | | OCTET STRING | Containing the PDU Session Resource Notify Released Transfer IE specified in subclause 9.3.4.13. | - | | +| User Location Information | O | | 9.3.1.16 | | YES | ignore | + +| Range bound | Explanation | +|--------------------|-------------------------------------------------------------------| +| maxnoofPDUSessions | Maximum no. of PDU sessions allowed towards one UE. Value is 256. | + +## 9.2.1.8 PDU SESSION RESOURCE MODIFY INDICATION + +This message is sent by the NG-RAN node and is used to request the AMF to enable modifications of already established PDU session resources for a given UE. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------------|----------|--------------------------|-----------------------|----------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| PDU Session Resource Modify Indication List | | 1 | | | YES | reject | +| >PDU Session Resource Modify Indication Item | | 1.. | | | - | | +| >>PDU Session ID | M | | 9.3.1.50 | | - | | +| >>PDU Session Resource Modify Indication Transfer | M | | OCTET STRING | Containing the PDU Session Resource Modify Indication Transfer IE specified in subclause 9.3.4.6. | - | | +| User Location Information | O | | 9.3.1.16 | | YES | ignore | + +| Range bound | Explanation | +|--------------------|-------------------------------------------------------------------| +| maxnoofPDUSessions | Maximum no. of PDU sessions allowed towards one UE. Value is 256. | + +## 9.2.1.9 PDU SESSION RESOURCE MODIFY CONFIRM + +This message is sent by the AMF and is used to confirm the outcome of the request from the PDU SESSION RESOURCE MODIFY INDICATION message. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------------------------|----------|--------------------------|-----------------------|------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | ignore | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | ignore | +| PDU Session Resource Modify Confirm List | | 0..1 | | | YES | ignore | +| >PDU Session Resource Modify Confirm Item | | 1.. | | | - | | +| >>PDU Session ID | M | | 9.3.1.50 | | - | | +| >>PDU Session Resource Modify Confirm Transfer | M | | OCTET STRING | Containing the PDU Session Resource Modify Confirm Transfer IE specified in subclause 9.3.4.7. | - | | +| PDU Session Resource Failed to Modify List | | 0..1 | | | YES | ignore | +| >PDU Session Resource Failed to Modify Item | | 1.. | | | - | | +| >>PDU Session ID | M | | 9.3.1.50 | | - | | +| >>PDU Session Resource Modify Indication Unsuccessful Transfer | M | | OCTET STRING | Containing the PDU Session Resource Modify Indication Unsuccessful Transfer IE specified in subclause 9.3.4.22. | - | | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +| Range bound | Explanation | +|--------------------|-------------------------------------------------------------------| +| maxnoofPDUSessions | Maximum no. of PDU sessions allowed towards one UE. Value is 256. | + +## 9.2.2 UE Context Management Messages + +### 9.2.2.1 INITIAL CONTEXT SETUP REQUEST + +This message is sent by the AMF to request the setup of a UE context. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------------------|---------------------------------------------|---------------------------------|--------------------------------------------|------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| Old AMF | O | | AMF Name
9.3.3.21 | | YES | reject | +| UE Aggregate Maximum Bit Rate | C-
ifPDUses
sionReso
urceSetu
p | | 9.3.1.58 | | YES | reject | +| Core Network Assistance Information for RRC INACTIVE | O | | 9.3.1.15 | | YES | ignore | +| GUAMI | M | | 9.3.3.3 | | YES | reject | +| PDU Session Resource Setup Request List | | 0..1 | | | YES | reject | +| > PDU Session Resource Setup Request Item | | 1..ofPDUSes
sions> | | | - | | +| >>PDU Session ID | M | | 9.3.1.50 | | - | | +| >>PDU Session NAS-PDU | O | | NAS-PDU
9.3.3.4 | | - | | +| >>S-NSSAI | M | | 9.3.1.24 | | - | | +| >>PDU Session Resource Setup Request Transfer | M | | OCTET STRING | Containing the PDU Session Resource Setup Request Transfer IE specified in subclause 9.3.4.1. | - | | +| >>PDU Session Expected UE Activity Behaviour | O | | Expected UE Activity Behaviour
9.3.1.94 | Expected UE Activity Behaviour for the PDU Session. | YES | ignore | +| Allowed NSSAI | M | | 9.3.1.31 | Indicates the S-NSSAIs permitted by the network | YES | reject | +| UE Security Capabilities | M | | 9.3.1.86 | | YES | reject | +| Security Key | M | | 9.3.1.87 | | YES | reject | +| Trace Activation | O | | 9.3.1.14 | | YES | ignore | +| Mobility Restriction List | O | | 9.3.1.85 | | YES | ignore | +| UE Radio Capability | O | | 9.3.1.74 | | YES | ignore | +| Index to RAT/Frequency Selection Priority | O | | 9.3.1.61 | | YES | ignore | +| Masked IMEISV | O | | 9.3.1.54 | | YES | ignore | +| NAS-PDU | O | | 9.3.3.4 | | YES | ignore | +| Emergency Fallback Indicator | O | | 9.3.1.26 | | YES | reject | +| RRC Inactive Transition Report Request | O | | 9.3.1.91 | | YES | ignore | +| UE Radio Capability for Paging | O | | 9.3.1.68 | | YES | ignore | +| Redirection for Voice EPS Fallback | O | | 9.3.1.116 | | YES | ignore | +| Location Reporting Request Type | O | | 9.3.1.65 | | YES | ignore | +| CN Assisted RAN | O | | 9.3.1.119 | | YES | ignore | + +| | | | | | | | +|---------------------------------------------|---|--|-----------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| Parameters Tuning | | | | | | | +| SRVCC Operation Possible | O | | 9.3.1.128 | | YES | ignore | +| IAB Authorized | O | | 9.3.1.129 | | YES | ignore | +| Enhanced Coverage Restriction | O | | 9.3.1.140 | | YES | ignore | +| Extended Connected Time | O | | 9.3.3.31 | | YES | ignore | +| UE Differentiation Information | O | | 9.3.1.144 | | YES | ignore | +| NR V2X Services Authorized | O | | 9.3.1.146 | | YES | ignore | +| LTE V2X Services Authorized | O | | 9.3.1.147 | | YES | ignore | +| NR UE Sidelink Aggregate Maximum Bit Rate | O | | 9.3.1.148 | 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.149 | This IE applies only if the UE is authorized for LTE V2X services. | YES | ignore | +| PC5 QoS Parameters | O | | 9.3.1.150 | This IE applies only if the UE is authorized for NR V2X services. | YES | ignore | +| CE-mode-B Restricted | O | | 9.3.1.155 | | YES | ignore | +| UE User Plane CIoT Support Indicator | O | | 9.3.1.160 | | YES | ignore | +| RG Level Wireline Access Characteristics | O | | OCTET STRING | Specified in TS 23.316 [34]. Indicates the wireline access technology specific QoS information corresponding to a specific wireline access subscription. | YES | ignore | +| Management Based MDT PLMN List | O | | MDT PLMN List 9.3.1.168 | | YES | ignore | +| UE Radio Capability ID | O | | 9.3.1.142 | | YES | reject | +| Time Synchronisation Assistance Information | O | | 9.3.1.220 | | YES | ignore | +| QMC Configuration Information | O | | 9.3.1.223 | | YES | ignore | +| Target NSSAI Information | O | | 9.3.1.229 | | YES | ignore | +| UE Slice Maximum Bit Rate List | O | | 9.3.1.231 | | YES | ignore | +| 5G ProSe Authorized | O | | 9.3.1.233 | | YES | ignore | +| 5G ProSe UE PC5 Aggregate Maximum Bit Rate | O | | NR UE Sidelink Aggregate Maximum Bit Rate 9.3.1.148 | This IE applies only if the UE is authorized for 5G ProSe services. | YES | ignore | +| 5G ProSe PC5 QoS Parameters | O | | 9.3.1.234 | This IE applies only if the UE is authorized for 5G | YES | ignore | + +| | | | | | | | +|-------------------------------------------|---|--|---------------------------------------------------------|--------------------------------------------------------------------|-----|--------| +| | | | | ProSe services. | | | +| Network Controlled Repeater Authorized | O | | 9.3.1.245 | | YES | ignore | +| Aerial UE Subscription Information | O | | 9.3.1.246 | | YES | ignore | +| NR A2X Services Authorized | O | | 9.3.1.247 | | YES | ignore | +| LTE A2X Services Authorized | O | | 9.3.1.248 | | YES | ignore | +| NR A2X UE PC5 Aggregate Maximum Bit Rate | O | | NR UE Sidelink Aggregate Maximum Bit Rate
9.3.1.148 | This IE applies only if the UE is authorized for NR A2X services. | YES | ignore | +| LTE A2X UE PC5 Aggregate Maximum Bit Rate | O | | LTE UE Sidelink Aggregate Maximum Bit Rate
9.3.1.149 | This IE applies only if the UE is authorized for LTE A2X services. | YES | ignore | +| A2X PC5 QoS Parameters | O | | 9.3.1.249 | This IE applies only if the UE is authorized for A2X services. | YES | ignore | +| Mobile IAB Authorized | O | | 9.3.1.259 | | YES | ignore | +| Partially Allowed NSSAI | O | | 9.3.1.261 | Indicates the S-NSSAIs partially permitted by the network. | YES | ignore | + +| Range bound | Explanation | +|--------------------|-------------------------------------------------------------------| +| maxnoofPDUSessions | Maximum no. of PDU sessions allowed towards one UE. Value is 256. | + +| Condition | Explanation | +|---------------------------|---------------------------------------------------------------------------------------| +| ifPDUSessionResourceSetup | This IE shall be present if the PDU Session Resource Setup List IE is present. | + +## 9.2.2.2 INITIAL CONTEXT SETUP RESPONSE + +This message is sent by the NG-RAN node to confirm the setup of a UE context. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------------|----------|--------------------------|-----------------------|------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | ignore | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | ignore | +| PDU Session Resource Setup Response List | | 0..1 | | | YES | ignore | +| > PDU Session Resource Setup Response Item | | 1.. | | | - | | +| >>PDU Session ID | M | | 9.3.1.50 | | - | | +| >>PDU Session Resource Setup Response Transfer | M | | OCTET STRING | Containing the PDU Session Resource Setup Response Transfer IE specified in subclause 9.3.4.2. | - | | +| PDU Session Resource Failed to Setup List | | 0..1 | | | YES | ignore | +| > PDU Session Resource Failed to Setup Item | | 1.. | | | - | | +| >>PDU Session ID | M | | 9.3.1.50 | | - | | +| >>PDU Session Resource Setup Unsuccessful Transfer | M | | OCTET STRING | Containing the PDU Session Resource Setup Unsuccessful Transfer IE specified in subclause 9.3.4.16. | - | | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +| Range bound | Explanation | +|--------------------|-------------------------------------------------------------------| +| maxnoofPDUSessions | Maximum no. of PDU sessions allowed towards one UE. Value is 256. | + +### 9.2.2.3 INITIAL CONTEXT SETUP FAILURE + +This message is sent by the NG-RAN node to indicate that the setup of the UE context was unsuccessful. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------------|----------|--------------------------|-----------------------|------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | ignore | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | ignore | +| PDU Session Resource Failed to Setup List | | 0..1 | | | YES | ignore | +| >PDU Session Resource Failed to Setup Item | | 1.. | | | - | | +| >>PDU Session ID | M | | 9.3.1.50 | | - | | +| >>PDU Session Resource Setup Unsuccessful Transfer | M | | OCTET STRING | Containing the PDU Session Resource Setup Unsuccessful Transfer IE specified in subclause 9.3.4.16. | - | | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +| Range bound | Explanation | +|--------------------|-------------------------------------------------------------------| +| maxnoofPDUSessions | Maximum no. of PDU sessions allowed towards one UE. Value is 256. | + +## 9.2.2.4 UE CONTEXT RELEASE REQUEST + +This message is sent by the NG-RAN node to request the release of the UE-associated logical NG-connection over the NG interface. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------|----------|--------------------------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| PDU Session Resource List | | 0..1 | | | YES | reject | +| >PDU Session Resource Item | | 1.. | | | - | | +| >>PDU Session ID | M | | 9.3.1.50 | | - | | +| Cause | M | | 9.3.1.2 | | YES | ignore | + +| Range bound | Explanation | +|--------------------|-------------------------------------------------------------------| +| maxnoofPDUSessions | Maximum no. of PDU sessions allowed towards one UE. Value is 256. | + +## 9.2.2.5 UE CONTEXT RELEASE COMMAND + +This message is sent by the AMF to request the release of the UE-associated logical NG-connection over the NG interface. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| CHOICE UE NGAP IDs | M | | | | YES | reject | +| > UE NGAP ID pair | | | | | | | +| >>AMF UE NGAP ID | M | | 9.3.3.1 | | - | | +| >>RAN UE NGAP ID | M | | 9.3.3.2 | | - | | +| > AMF UE NGAP ID | | | | | | | +| >>AMF UE NGAP ID | M | | 9.3.3.1 | | - | | +| Cause | M | | 9.3.1.2 | | YES | ignore | + +## 9.2.2.6 UE CONTEXT RELEASE COMPLETE + +This message is sent by the NG-RAN node to confirm the release of the UE-associated logical NG-connection over the NG interface. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------------------------|----------|--------------------------|-----------------------|----------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | ignore | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | ignore | +| User Location Information | O | | 9.3.1.16 | | YES | ignore | +| Information on Recommended Cells and RAN Nodes for Paging | O | | 9.3.1.100 | | YES | ignore | +| PDU Session Resource List | | 0..1 | | | YES | reject | +| > PDU Session Resource Item | | 1.. | | | - | | +| >>PDU Session ID | M | | 9.3.1.50 | | - | | +| >>PDU Session Resource Release Response Transfer | O | | OCTET STRING | Containing the PDU Session Resource Release Response Transfer IE specified in subclause 9.3.4.21. | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | +| Paging Assistance Data for CE Capable UE | O | | 9.3.1.141 | | YES | ignore | + +| Range bound | Explanation | +|--------------------|-------------------------------------------------------------------| +| maxnoofPDUSessions | Maximum no. of PDU sessions allowed towards one UE. Value is 256. | + +## 9.2.2.7 UE CONTEXT MODIFICATION REQUEST + +This message is sent by the AMF to provide UE Context information changes to the NG-RAN node. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------------------|----------|-------|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| RAN Paging Priority | O | | 9.3.3.15 | | YES | ignore | +| Security Key | O | | 9.3.1.87 | | YES | reject | +| Index to RAT/Frequency Selection Priority | O | | 9.3.1.61 | | YES | ignore | +| UE Aggregate Maximum Bit Rate | O | | 9.3.1.58 | | YES | ignore | +| UE Security Capabilities | O | | 9.3.1.86 | | YES | reject | +| Core Network Assistance Information for RRC INACTIVE | O | | 9.3.1.15 | | YES | ignore | +| Emergency Fallback Indicator | O | | 9.3.1.26 | | YES | reject | +| New AMF UE NGAP ID | O | | AMF UE NGAP ID
9.3.3.1 | | YES | reject | +| RRC Inactive Transition Report Request | O | | 9.3.1.91 | | YES | ignore | +| New GUAMI | O | | GUAMI
9.3.3.3 | | YES | reject | +| CN Assisted RAN Parameters Tuning | O | | 9.3.1.119 | | YES | ignore | +| SRVCC Operation Possible | O | | 9.3.1.128 | | YES | ignore | +| IAB Authorized | O | | 9.3.1.129 | | YES | ignore | +| NR V2X Services Authorized | O | | 9.3.1.146 | | YES | ignore | +| LTE V2X Services Authorized | O | | 9.3.1.147 | | YES | ignore | +| NR UE Sidelink Aggregate Maximum Bit Rate | O | | 9.3.1.148 | 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.149 | This IE applies only if the UE is authorized for LTE V2X services. | YES | ignore | +| PC5 QoS Parameters | O | | 9.3.1.150 | This IE applies only if the UE is authorized for NR V2X services. | YES | ignore | +| UE Radio Capability ID | O | | 9.3.1.142 | | YES | reject | +| RG Level Wireline Access Characteristics | O | | OCTET STRING | Specified in TS 23.316 [34]. Indicates the wireline access technology specific QoS information corresponding to a specific wireline access subscription. | YES | ignore | +| Time Synchronisation Assistance Information | O | | 9.3.1.220 | | YES | ignore | + +| | | | | | | | +|---------------------------------------------|---|--|---------------------------------------------------------|---------------------------------------------------------------------|-----|--------| +| QMC Configuration Information | O | | 9.3.1.223 | | YES | ignore | +| QMC Deactivation | O | | 9.3.1.222 | | YES | ignore | +| UE Slice Maximum Bit Rate List | O | | 9.3.1.231 | | YES | ignore | +| Management Based MDT PLMN Modification List | O | | MDT PLMN Modification List
9.3.1.243 | | YES | ignore | +| 5G ProSe Authorized | O | | 9.3.1.233 | | YES | ignore | +| 5G ProSe UE PC5 Aggregate Maximum Bit Rate | O | | NR UE Sidelink Aggregate Maximum Bit Rate
9.3.1.148 | This IE applies only if the UE is authorized for 5G ProSe services. | YES | ignore | +| 5G ProSe PC5 QoS Parameters | O | | 9.3.1.234 | This IE applies only if the UE is authorized for 5G ProSe services. | YES | ignore | +| Network Controlled Repeater Authorized | O | | 9.3.1.245 | | YES | ignore | +| Aerial UE Subscription Information | O | | 9.3.1.246 | | YES | ignore | +| NR A2X Services Authorized | O | | 9.3.1.247 | | YES | ignore | +| LTE A2X Services Authorized | O | | 9.3.1.248 | | YES | ignore | +| NR A2X UE PC5 Aggregate Maximum Bit Rate | O | | NR UE Sidelink Aggregate Maximum Bit Rate
9.3.1.148 | This IE applies only if the UE is authorized for NR A2X services. | YES | ignore | +| LTE A2X UE PC5 Aggregate Maximum Bit Rate | O | | LTE UE Sidelink Aggregate Maximum Bit Rate
9.3.1.149 | This IE applies only if the UE is authorized for LTE A2X services. | YES | ignore | +| A2X PC5 QoS Parameters | O | | 9.3.1.249 | This IE applies only if the UE is authorized for A2X services. | YES | ignore | +| Mobile IAB Authorized | O | | 9.3.1.259 | | YES | ignore | + +## 9.2.2.8 UE CONTEXT MODIFICATION RESPONSE + +This message is sent by the NG-RAN node to confirm the performed UE context updates. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | ignore | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | ignore | +| RRC State | O | | 9.3.1.92 | | YES | ignore | +| User Location Information | O | | 9.3.1.16 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.2.9 UE CONTEXT MODIFICATION FAILURE + +This message is sent by the NG-RAN node in case the performed UE context update is not successful. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | ignore | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | ignore | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.2.10 RRC INACTIVE TRANSITION REPORT + +This message is sent by the NG-RAN node to notify the 5GC the UE enters or leaves RRC\_INACTIVE state. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| RRC State | M | | 9.3.1.92 | | YES | ignore | +| User Location Information | M | | 9.3.1.16 | | YES | ignore | + +### 9.2.2.11 CONNECTION ESTABLISHMENT INDICATION + +This message is sent by the AMF to complete the establishment of the UE-associated logical NG-connection. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------|----------|-------|-----------------------|------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| UE Radio Capability | O | | 9.3.1.74 | | YES | ignore | +| End Indication | O | | 9.3.3.32 | | YES | ignore | +| S-NSSAI | O | | 9.3.1.24 | | YES | ignore | +| Allowed NSSAI | O | | 9.3.1.31 | Indicates the S-NSSAIs permitted by the network | YES | ignore | +| UE Differentiation Information | O | | 9.3.1.144 | | YES | ignore | +| DL CP Security Information | O | | 9.3.3.49 | | YES | ignore | +| NB-IoT UE Priority | O | | 9.3.1.145 | | YES | ignore | +| Enhanced Coverage Restriction | O | | 9.3.1.140 | | YES | ignore | +| CE-mode-B Restricted | O | | 9.3.1.155 | | YES | ignore | +| UE Radio Capability ID | O | | 9.3.1.142 | | YES | reject | +| Masked IMEISV | O | | 9.3.1.54 | | YES | ignore | +| Old AMF | O | | AMF Name
9.3.3.21 | | YES | reject | +| Partially Allowed NSSAI | O | | 9.3.1.261 | Indicates the S-NSSAIs partially permitted by the network. | YES | ignore | + +## 9.2.2.12 AMF CP RELOCATION INDICATION + +This message is sent by the AMF to inform the NG-RAN node that the UE is to be relocated as described in TS. 38.300 [8]. + +Direction: AMF → NG-RAN node. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| S-NSSAI | O | | 9.3.1.24 | | YES | ignore | +| Allowed NSSAI | O | | 9.3.1.31 | Indicates the S-NSSAIs permitted by the network | YES | ignore | +| Partially Allowed NSSAI | O | | 9.3.1.261 | Indicates the S-NSSAIs partially permitted by the network. | YES | ignore | + +### 9.2.2.13 RAN CP RELOCATION INDICATION + +This message is sent by the NG-RAN node to initiate the establishment of a UE-associated logical NG-connection, following the reception of re-establishment request. + +Direction: NG-RAN node → AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| 5G-S-TMSI | M | | 9.3.3.20 | | YES | reject | +| E-UTRA CGI | M | | 9.3.1.9 | | YES | ignore | +| TAI | M | | 9.3.3.11 | | YES | ignore | +| UL CP Security Information | M | | 9.3.3.48 | | YES | reject | + +### 9.2.2.14 RETRIEVE UE INFORMATION + +The message is sent by the NG-RAN node to request UE information over the NG interface. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| 5G-S-TMSI | M | | 9.3.3.20 | | YES | reject | + +### 9.2.2.15 UE INFORMATION TRANSFER + +The message is sent by the AMF to transfer UE information over the NG interface. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------|----------|-------|-----------------------|------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| 5G-S-TMSI | M | | 9.3.3.20 | | YES | reject | +| NB-IoT UE Priority | O | | 9.3.1.145 | | YES | ignore | +| UE Radio Capability | O | | 9.3.1.74 | | YES | ignore | +| S-NSSAI | O | | 9.3.1.24 | | YES | ignore | +| Allowed NSSAI | O | | 9.3.1.31 | Indicates the S-NSSAIs permitted by the network | YES | ignore | +| UE Differentiation Information | O | | 9.3.1.144 | | YES | ignore | +| Masked IMEISV | O | | 9.3.1.54 | | YES | ignore | +| Partially Allowed NSSAI | O | | 9.3.1.261 | Indicates the S-NSSAIs partially permitted by the network. | YES | ignore | + +### 9.2.2.16 UE CONTEXT SUSPEND REQUEST + +This message is sent by the NG-RAN node to request the AMF to suspend the UE context and the related PDU session contexts. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------------------------|----------|-------------------------|-----------------------------------------------------------------------------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| Information on Recommended Cells and RAN Nodes for Paging | O | | 9.3.1.100 | | YES | ignore | +| Paging Assistance Data for CE Capable UE | O | | 9.3.1.141 | | YES | ignore | +| PDU Session Resource Suspend List | | 0..1 | | | YES | reject | +| > PDU Session Resource Suspend Item | | 1.. | | | - | | +| >>PDU Session ID | M | | 9.3.1.50 | | - | | +| >>UE Context Suspend Request Transfer | M | | Containing the UE Context Suspend Request Transfer IE specified in subclause 9.3.4.26. | | - | | + +| Range bound | Explanation | +|--------------------|-------------------------------------------------------------------| +| maxnoofPDUSessions | Maximum no. of PDU sessions allowed towards one UE. Value is 256. | + +### 9.2.2.17 UE CONTEXT SUSPEND RESPONSE + +This message is sent by the AMF to indicate to the NG-RAN node the UE context and the related PDU session contexts have been suspended. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | ignore | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | ignore | +| Security Context | O | | 9.3.1.88 | | YES | reject | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.2.18 UE CONTEXT SUSPEND FAILURE + +This message is sent by the AMF to indicate to the NG-RAN node that suspension of the UE context has failed in the 5GC. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | ignore | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | ignore | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +## 9.2.2.19 UE CONTEXT RESUME REQUEST + +This message is sent by the NG-RAN node to request the AMF to resume the UE-associated logical NG-connection and UE context. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------------------------|----------|---------------------------|-----------------------------------|---------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| RRC Resume Cause | M | | RRC Establishment Cause 9.3.1.111 | | YES | ignore | +| PDU Session Resource Resume List | | 0..1 | | | YES | reject | +| >PDU Session Resource Resume Item | | 1.. | | | - | | +| >>PDU Session ID | M | | 9.3.1.50 | | - | | +| >>UE Context Resume Request Transfer | M | | OCTET STRING | Containing the UE Context Resume Request Transfer IE specified in subclause 9.3.4.24 | - | | +| PDU Session Resource Failed to Resume List | | 0..1 | | | YES | reject | +| >PDU Session Resource Failed to Resume Item | | 1.. | | | - | | +| >>PDU Session ID | M | | 9.3.1.50 | | - | | +| >>Cause | M | | 9.3.1.2 | | - | | +| Suspend Request Indication | O | | 9.3.1.158 | | YES | ignore | +| Information on Recommended Cells and RAN Nodes for Paging | O | | 9.3.1.100 | | YES | ignore | +| Paging Assistance Data for CE Capable UE | O | | 9.3.1.141 | | YES | ignore | + +| Range bound | Explanation | +|--------------------|-------------------------------------------------------------------| +| maxnoofPDUSessions | Maximum no. of PDU sessions allowed towards one UE. Value is 256. | + +### 9.2.2.20 UE CONTEXT RESUME RESPONSE + +This message is sent by the AMF to indicate to the NG-RAN node that the UE context and the related PDU session contexts have been resumed in the 5GC. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------------------|----------|--------------------------|-----------------------|----------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | ignore | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | ignore | +| PDU Session Resource Resume List | | 0..1 | | | YES | reject | +| >PDU Session Resource Resume Item | | 1.. | | | - | | +| >>PDU Session ID | M | | 9.3.1.50 | | - | | +| >>UE Context Resume Response Transfer | M | | OCTET STRING | Containing the UE Context Resume Response Transfer IE specified in subclause 9.3.4.25 | - | | +| PDU Session Resource Failed to Resume List | | 0..1 | | | YES | reject | +| >PDU Session Resource Failed to Resume Item | | 1.. | | | - | | +| >>PDU Session ID | M | | 9.3.1.50 | | - | | +| >>Cause | M | | 9.3.1.2 | | - | | +| Security Context | O | | 9.3.1.88 | | YES | reject | +| Suspend Response Indication | O | | 9.3.1.159 | | YES | ignore | +| Extended Connected Time | O | | 9.3.3.31 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +| Range bound | Explanation | +|--------------------|-------------------------------------------------------------------| +| maxnoofPDUSessions | Maximum no. of PDU sessions allowed towards one UE. Value is 256. | + +### 9.2.2.21 UE CONTEXT RESUME FAILURE + +This message is sent by the AMF to indicate to the NG-RAN node that resumption of the UE context and the related PDU session contexts has failed in the 5GC. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | ignore | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | ignore | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.2.22 MT COMMUNICATION HANDLING REQUEST + +This message is sent by the NG-RAN node to the AMF to request activating or deactivating CN based MT communication handling for UEs in RRC\_INACTIVE state with long eDRX beyond 10.24 seconds as specified in TS 23.501 [9]. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------------|----------|-------|------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| CHOICE 5GC Action | M | | | | YES | reject | +| >HLCom Activate | | | | | | | +| >>NR Paging Long eDRX Information for RRC INACTIVE | M | | 9.3.3.64 | | - | | +| >HLcom Deactivate | | | | | | | +| >>UE Reachability Indication | M | | ENUMERATED (true, ...) | | - | | + +### 9.2.2.23 MT COMMUNICATION HANDLING RESPONSE + +This message is sent by the AMF to indicate that CN based MT Communication handling was successfully activated or deactivated, as specified in TS 23.501 [9]. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.2.24 MT COMMUNICATION HANDLING FAILURE + +This message is sent by the AMF to indicate that CN based MT Communication handling was unsuccessful. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.2.25 RAN PAGING REQUEST + +This message is sent by the AMF to request RAN Paging due to MT data buffered in 5GC or the arrival of DL signalling for the UE. + +Direction: AMF → NG-RAN + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------|----------|-------|------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | ignore | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | ignore | +| Paging Policy Differentiation | O | | 9.3.3.63 | | YES | ignore | +| DL Signalling | O | | ENUMERATED (true, ...) | | YES | ignore | + +## 9.2.3 UE Mobility Management Messages + +### 9.2.3.1 HANDOVER REQUIRED + +This message is sent by the source NG-RAN node to the AMF to request the preparation of resources at the target. + +Direction: NG-RAN node → AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------|----------|--------------------------|-----------------------|--------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| Handover Type | M | | 9.3.1.22 | | YES | reject | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Target ID | M | | 9.3.1.25 | | YES | reject | +| Direct Forwarding Path Availability | O | | 9.3.1.64 | | YES | ignore | +| PDU Session Resource List | | 1 | | | YES | reject | +| >PDU Session Resource Item | | 1.. | | | - | | +| >>PDU Session ID | M | | 9.3.1.50 | | - | | +| >>Handover Required Transfer | M | | OCTET STRING | Containing the Handover Required Transfer IE specified in subclause 9.3.4.14. | - | | +| Source to Target Transparent Container | M | | 9.3.1.20 | | YES | reject | + +| Range bound | Explanation | +|--------------------|-------------------------------------------------------------------| +| maxnoofPDUSessions | Maximum no. of PDU sessions allowed towards one UE. Value is 256. | + +### 9.2.3.2 HANDOVER COMMAND + +This message is sent by the AMF to inform the source NG-RAN node that resources for the handover have been prepared at the target side. + +Direction: AMF → NG-RAN node. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------|----------------|--------------------------|-----------------------|------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| Handover Type | M | | 9.3.1.22 | | YES | reject | +| NAS Security Parameters from NG-RAN | C-ift EPSU TRA | | 9.3.3.26 | | YES | reject | +| PDU Session Resource Handover List | | 0..1 | | | YES | ignore | +| >PDU Session Resource Handover Item | | 1.. | | | - | | +| >>PDU Session ID | M | | 9.3.1.50 | | - | | +| >>Handover Command Transfer | M | | OCTET STRING | Containing the Handover Command Transfer IE specified in subclause 9.3.4.10. | - | | +| PDU Session Resource to Release List | | 0..1 | | | YES | ignore | +| >PDU Session Resource to Release Item | | 1.. | | | - | | +| >>PDU Session ID | M | | 9.3.1.50 | | - | | +| >>Handover Preparation Unsuccessful Transfer | M | | OCTET STRING | Containing the Handover Preparation Unsuccessful Transfer IE specified in subclause 9.3.4.18. | - | | +| Target to Source Transparent Container | M | | 9.3.1.21 | | YES | reject | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +| Range bound | Explanation | +|--------------------|-------------------------------------------------------------------| +| maxnoofPDUSessions | Maximum no. of PDU sessions allowed towards one UE. Value is 256. | + +| Condition | Explanation | +|--------------|-------------------------------------------------------------------------------------------------------| +| ift EPSU TRA | This IE shall be present if the Handover Type IE is set to the value "5GStoEPS" or "5GtoUTRA". | + +### 9.2.3.3 HANDOVER PREPARATION FAILURE + +This message is sent by the AMF to inform the source NG-RAN node that the Handover Preparation has failed. + +Direction: AMF → NG-RAN node. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | ignore | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | ignore | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | +| Target to Source Failure
Transparent Container | O | | 9.3.1.186 | | YES | ignore | + +### 9.2.3.4 HANDOVER REQUEST + +This message is sent by the AMF to the target NG-RAN node to request the preparation of resources. + +Direction: AMF → NG-RAN node. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------------------|----------|--------------------------|-----------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| Handover Type | M | | 9.3.1.22 | | YES | reject | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| UE Aggregate Maximum Bit Rate | M | | 9.3.1.58 | | YES | reject | +| Core Network Assistance Information for RRC INACTIVE | O | | 9.3.1.15 | | YES | ignore | +| UE Security Capabilities | M | | 9.3.1.86 | | YES | reject | +| Security Context | M | | 9.3.1.88 | | YES | reject | +| New Security Context Indicator | O | | 9.3.1.55 | | YES | reject | +| NASC | O | | NAS-PDU 9.3.3.4 | Refers to either the "Intra N1 mode NAS transparent container" or the "S1 mode to N1 mode NAS transparent container", the details of the IE definition and the encoding are specified in TS 24.501 [26]. | YES | reject | +| PDU Session Resource Setup List | | 1 | | | YES | reject | +| >PDU Session Resource Setup Item | | 1.. | | | - | | +| >>PDU Session ID | M | | 9.3.1.50 | | - | | +| >>S-NSSAI | M | | 9.3.1.24 | | - | | +| >>Handover Request Transfer | M | | OCTET STRING | Containing the PDU Session Resource Setup Request Transfer IE specified in subclause 9.3.4.1. | - | | +| >>PDU Session Expected UE Activity Behaviour | O | | Expected UE Activity Behaviour 9.3.1.94 | Expected UE Activity Behaviour for the PDU Session. | YES | ignore | +| Allowed NSSAI | M | | 9.3.1.31 | Indicates the S-NSSAIs permitted by the network. | YES | reject | +| Trace Activation | O | | 9.3.1.14 | | YES | ignore | +| Masked IMEISV | O | | 9.3.1.54 | | YES | ignore | +| Source to Target Transparent Container | M | | 9.3.1.20 | | YES | reject | +| Mobility Restriction List | O | | 9.3.1.85 | | YES | ignore | +| Location Reporting Request Type | O | | 9.3.1.65 | | YES | ignore | +| RRC Inactive Transition Report Request | O | | 9.3.1.91 | | YES | ignore | +| GUAMI | M | | 9.3.3.3 | | YES | reject | + +| | | | | | | | +|---------------------------------------------|---|--|--------------------------------------------------------|---------------------------------------------------------------------|-----|--------| +| Redirection for Voice EPS Fallback | O | | 9.3.1.116 | | YES | ignore | +| CN Assisted RAN Parameters Tuning | O | | 9.3.1.119 | | YES | ignore | +| SRVCC Operation Possible | O | | 9.3.1.128 | | YES | ignore | +| IAB Authorized | O | | 9.3.1.129 | | YES | reject | +| Enhanced Coverage Restriction | O | | 9.3.1.140 | | YES | ignore | +| UE Differentiation Information | O | | 9.3.1.144 | | YES | ignore | +| NR V2X Services Authorized | O | | 9.3.1.146 | | YES | ignore | +| LTE V2X Services Authorized | O | | 9.3.1.147 | | YES | ignore | +| NR UE Sidelink Aggregate Maximum Bit Rate | O | | 9.3.1.148 | 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.149 | This IE applies only if the UE is authorized for LTE V2X services. | YES | ignore | +| PC5 QoS Parameters | O | | 9.3.1.150 | This IE applies only if the UE is authorized for NR V2X services. | YES | ignore | +| CE-mode-B Restricted | O | | 9.3.1.155 | | YES | ignore | +| UE User Plane CIoT Support Indicator | O | | 9.3.1.160 | | YES | ignore | +| Management Based MDT PLMN List | O | | MDT PLMN List
9.3.1.168 | | YES | ignore | +| UE Radio Capability ID | O | | 9.3.1.142 | | YES | reject | +| Extended Connected Time | O | | 9.3.3.31 | | YES | ignore | +| Time Synchronisation Assistance Information | O | | 9.3.1.220 | | YES | ignore | +| UE Slice Maximum Bit Rate List | O | | 9.3.1.231 | | YES | ignore | +| 5G ProSe Authorized | O | | 9.3.1.233 | | YES | ignore | +| 5G ProSe UE PC5 Aggregate Maximum Bit Rate | O | | NR UE Sidelink Aggregate Maximum Bit Rate
9.3.1.148 | This IE applies only if the UE is authorized for 5G ProSe services. | YES | ignore | +| 5G ProSe PC5 QoS Parameters | O | | 9.3.1.234 | This IE applies only if the UE is authorized for 5G ProSe services. | YES | ignore | +| Aerial UE Subscription Information | O | | 9.3.1.246 | | YES | ignore | +| NR A2X Services Authorized | O | | 9.3.1.247 | | YES | ignore | +| LTE A2X Services Authorized | O | | 9.3.1.248 | | YES | ignore | +| NR A2X UE PC5 Aggregate Maximum Bit Rate | O | | NR UE Sidelink Aggregate Maximum Bit Rate | This IE applies only if the UE is authorized for NR | YES | ignore | + +| | | | | | | | +|-------------------------------------------|---|--|---------------------------------------------------------|--------------------------------------------------------------------|-----|--------| +| | | | 9.3.1.148 | A2X services. | | | +| LTE A2X UE PC5 Aggregate Maximum Bit Rate | O | | LTE UE Sidelink Aggregate Maximum Bit Rate
9.3.1.149 | This IE applies only if the UE is authorized for LTE A2X services. | YES | ignore | +| A2X PC5 QoS Parameters | O | | 9.3.1.249 | This IE applies only if the UE is authorized for A2X services. | YES | ignore | +| Mobile IAB Authorized | O | | 9.3.1.259 | | YES | ignore | +| No PDU Session Indication | O | | ENUMERATED (true, ...) | This IE applies only if the UE is a mobile IAB-MT. | YES | ignore | +| Partially Allowed NSSAI | O | | 9.3.1.261 | Indicates the S-NSSAIs partially permitted by the network. | YES | ignore | + +| Range bound | Explanation | +|--------------------|-------------------------------------------------------------------| +| maxnoofPDUSessions | Maximum no. of PDU sessions allowed towards one UE. Value is 256. | + +### 9.2.3.5 HANDOVER REQUEST ACKNOWLEDGE + +This message is sent by the target NG-RAN node to inform the AMF about the prepared resources at the target. + +Direction: NG-RAN node → AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------------------|----------|--------------------------|-----------------------|--------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | ignore | +| RAN UE NGAP ID | M | | 9.3.3.2 | Allocated at the target NG-RAN node. | YES | ignore | +| PDU Session Resource Admitted List | | 1 | | | YES | ignore | +| >PDU Session Resource Admitted Item | | 1.. | | | - | | +| >>PDU Session ID | M | | 9.3.1.50 | | - | | +| >>Handover Request Acknowledge Transfer | M | | OCTET STRING | Containing the Handover Request Acknowledge Transfer IE specified in subclause 9.3.4.11. | - | | +| PDU Session Resource Failed to Setup List | | 0..1 | | | YES | ignore | +| >PDU Session Resource Failed to Setup Item | | 1.. | | | - | | +| >>PDU Session ID | M | | 9.3.1.50 | | - | | +| >>Handover Resource Allocation Unsuccessful Transfer | M | | OCTET STRING | Containing the Handover Resource Allocation Unsuccessful Transfer IE specified in subclause 9.3.4.19. | - | | +| Target to Source Transparent Container | M | | 9.3.1.21 | | YES | reject | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | +| NPN Access Information | O | | 9.3.3.46 | | YES | reject | +| RedCap Indication | O | | 9.3.1.228 | | YES | ignore | + +| Range bound | Explanation | +|--------------------|-------------------------------------------------------------------| +| maxnoofPDUSessions | Maximum no. of PDU sessions allowed towards one UE. Value is 256. | + +### 9.2.3.6 HANDOVER FAILURE + +This message is sent by the target NG-RAN node to inform the AMF that the preparation of resources has failed. + +Direction: NG-RAN node → AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | ignore | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | +| Target to Source Failure Transparent Container | O | | 9.3.1.186 | | YES | ignore | + +### 9.2.3.7 HANDOVER NOTIFY + +This message is sent by the target NG-RAN node to inform the AMF that the UE has been identified in the target cell and the handover has been completed. + +Direction: NG-RAN node → AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------|----------|-------|--------------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| User Location Information | M | | 9.3.1.16 | | YES | ignore | +| Notify Source NG-RAN Node | O | | ENUMERATED (NotifySource, ...) | | YES | ignore | + +### 9.2.3.8 PATH SWITCH REQUEST + +This message is sent by the NG-RAN node to inform the AMF of the new serving NG-RAN node and to transfer some NG-U DL tunnel termination point(s) to the SMF via the AMF for one or multiple PDU session resources. + +Direction: NG-RAN node → AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------------------------|----------|--------------------------|--------------------------------------|-----------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| Source AMF UE NGAP ID | M | | AMF UE NGAP ID
9.3.3.1 | | YES | reject | +| User Location Information | M | | 9.3.1.16 | | YES | ignore | +| UE Security Capabilities | M | | 9.3.1.86 | | YES | ignore | +| PDU Session Resource to be Switched in Downlink List | | 1 | | | YES | reject | +| >PDU Session Resource to be Switched in Downlink Item | | 1.. | | | - | | +| >>PDU Session ID | M | | 9.3.1.50 | | - | | +| >>Path Switch Request Transfer | M | | OCTET STRING | Containing the Path Switch Request Transfer IE specified in subclause 9.3.4.8. | - | | +| PDU Session Resource Failed to Setup List | | 0..1 | | | YES | ignore | +| >PDU Session Resource Failed to Setup Item | | 1.. | | | - | | +| >>PDU Session ID | M | | 9.3.1.50 | | - | | +| >>Path Switch Request Setup Failed Transfer | M | | OCTET STRING | Containing the Path Switch Request Setup Failed Transfer IE specified in subclause 9.3.4.15. | - | | +| RRC Resume Cause | O | | RRC Establishment Cause
9.3.1.111 | | YES | ignore | +| RedCap Indication | O | | 9.3.1.228 | | YES | ignore | + +| Range bound | Explanation | +|--------------------|-------------------------------------------------------------------| +| maxnoofPDUSessions | Maximum no. of PDU sessions allowed towards one UE. Value is 256. | + +### 9.2.3.9 PATH SWITCH REQUEST ACKNOWLEDGE + +This message is sent by the AMF to inform the NG-RAN node that the path switch has been successfully completed in the 5GC. + +Direction: AMF → NG-RAN node. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------------------|----------|--------------------------|-----------------------------------------|-----------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | ignore | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | ignore | +| UE Security Capabilities | O | | 9.3.1.86 | | YES | reject | +| Security Context | M | | 9.3.1.88 | | YES | reject | +| New Security Context Indicator | O | | 9.3.1.55 | | YES | reject | +| PDU Session Resource Switched List | | 1 | | | YES | ignore | +| >PDU Session Resource Switched Item | | 1.. | | | - | | +| >>PDU Session ID | M | | 9.3.1.50 | | - | | +| >>Path Switch Request Acknowledge Transfer | M | | OCTET STRING | Containing the Path Switch Request Acknowledge Transfer IE specified in subclause 9.3.4.9. | - | | +| >>PDU Session Expected UE Activity Behaviour | O | | Expected UE Activity Behaviour 9.3.1.94 | Expected UE Activity Behaviour for the PDU Session. | YES | ignore | +| PDU Session Resource Released List | | 0..1 | | | YES | ignore | +| >PDU Session Resource Released Item | | 1.. | | | - | | +| >>PDU Session ID | M | | 9.3.1.50 | | - | | +| >>Path Switch Request Unsuccessful Transfer | M | | OCTET STRING | Containing the Path Switch Request Unsuccessful Transfer IE specified in subclause 9.3.4.20. | - | | +| Allowed NSSAI | M | | 9.3.1.31 | Indicates the S-NSSAIs permitted by the network. | YES | reject | +| Core Network Assistance Information for RRC INACTIVE | O | | 9.3.1.15 | | YES | ignore | +| RRC Inactive Transition Report Request | O | | 9.3.1.91 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | +| Redirection for Voice EPS Fallback | O | | 9.3.1.116 | | YES | ignore | +| CN Assisted RAN Parameters Tuning | O | | 9.3.1.119 | | YES | ignore | +| SRVCC Operation Possible | O | | 9.3.1.128 | | YES | ignore | +| Enhanced Coverage Restriction | O | | 9.3.1.140 | | YES | ignore | + +| | | | | | | | +|---------------------------------------------|---|--|--------------------------------------------------------|---------------------------------------------------------------------------------------------|-----|--------| +| Extended Connected Time | O | | 9.3.3.31 | | YES | ignore | +| UE Differentiation Information | O | | 9.3.1.144 | | YES | ignore | +| NR V2X Services Authorized | O | | 9.3.1.146 | | YES | ignore | +| LTE V2X Services Authorized | O | | 9.3.1.147 | | YES | ignore | +| NR UE Sidelink Aggregate Maximum Bit Rate | O | | 9.3.1.148 | 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.149 | This IE applies only if the UE is authorized for LTE V2X services. | YES | ignore | +| PC5 QoS Parameters | O | | 9.3.1.150 | This IE applies only if the UE is authorized for NR V2X services. | YES | ignore | +| CE-mode-B Restricted | O | | 9.3.1.155 | | YES | ignore | +| UE User Plane CIoT Support Indicator | O | | 9.3.1.160 | | YES | ignore | +| UE Radio Capability ID | O | | 9.3.1.142 | | YES | reject | +| Management Based MDT PLMN List | O | | MDT PLMN List
9.3.1.168 | This IE is ignored if the Management Based MDT PLMN Modification List IE is present. | YES | ignore | +| Time Synchronisation Assistance Information | O | | 9.3.1.220 | | YES | ignore | +| 5G ProSe Authorized | O | | 9.3.1.233 | | YES | ignore | +| 5G ProSe UE PC5 Aggregate Maximum Bit Rate | O | | NR UE Sidelink Aggregate Maximum Bit Rate
9.3.1.148 | This IE applies only if the UE is authorized for 5G ProSe services. | YES | ignore | +| 5G ProSe PC5 QoS Parameters | O | | 9.3.1.234 | This IE applies only if the UE is authorized for 5G ProSe services. | YES | ignore | +| Management Based MDT PLMN Modification List | O | | MDT PLMN Modification List
9.3.1.243 | | YES | ignore | +| IAB Authorized | O | | 9.3.1.129 | | YES | ignore | +| Aerial UE Subscription Information | O | | 9.3.1.246 | | YES | ignore | +| NR A2X Services Authorized | O | | 9.3.1.247 | | YES | ignore | +| LTE A2X Services Authorized | O | | 9.3.1.248 | | YES | ignore | +| NR A2X UE PC5 Aggregate Maximum Bit Rate | O | | NR UE Sidelink Aggregate Maximum Bit Rate
9.3.1.148 | This IE applies only if the UE is authorized for NR A2X services. | YES | ignore | +| LTE A2X UE PC5 Aggregate Maximum Bit Rate | O | | LTE UE Sidelink Aggregate Maximum Bit | This IE applies only if the UE is authorized for LTE | YES | ignore | + +| | | | | | | | +|---------------------------|---|--|-------------------|-------------------------------------------------------------------------|-----|--------| +| | | | Rate
9.3.1.149 | A2X services. | | | +| A2X PC5 QoS
Parameters | O | | 9.3.1.249 | This IE applies
only if the UE is
authorized for A2X
services. | YES | ignore | +| Mobile IAB Authorized | O | | 9.3.1.259 | | YES | ignore | +| Partially Allowed NSSAI | O | | 9.3.1.261 | Indicates the S-
NSSAIs partially
permitted by the
network. | YES | ignore | + +| Range bound | Explanation | +|--------------------|-------------------------------------------------------------------| +| maxnoofPDUSessions | Maximum no. of PDU sessions allowed towards one UE. Value is 256. | + +### 9.2.3.10 PATH SWITCH REQUEST FAILURE + +This message is sent by the AMF to inform the NG-RAN node that a failure has occurred in the 5GC during the Path Switch Request procedure. + +Direction: AMF → NG-RAN node. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------------|----------|--------------------------|-----------------------|-----------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | ignore | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | ignore | +| PDU Session Resource Released List | | 1 | | | YES | ignore | +| >PDU Session Resource Released Item | | 1.. | | | - | | +| >>PDU Session ID | M | | 9.3.1.50 | | - | | +| >>Path Switch Request Unsuccessful Transfer | M | | OCTET STRING | Containing the PDU session Path Switch Request Unsuccessful Transfer IE specified in subclause 9.3.4.20. | - | | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +| Range bound | Explanation | +|--------------------|-------------------------------------------------------------------| +| maxnoofPDUSessions | Maximum no. of PDU sessions allowed towards one UE. Value is 256. | + +### 9.2.3.11 HANDOVER CANCEL + +This message is sent by the source NG-RAN node to the AMF to request the cancellation of an ongoing handover. + +Direction: NG-RAN node → AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| Cause | M | | 9.3.1.2 | | YES | ignore | + +### 9.2.3.12 HANDOVER CANCEL ACKNOWLEDGE + +This message is sent by the AMF to the source NG-RAN node to confirm that the ongoing handover was cancelled. + +Direction: AMF → NG-RAN node. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | ignore | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.3.13 UPLINK RAN STATUS TRANSFER + +This message is sent by the source NG-RAN node to transfer the uplink PDCP-SN and HFN receiver status and the downlink PDCP SN and HFN transmitter status during intra 5GC NG-based handover. + +Direction: NG-RAN node → AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| RAN Status Transfer
Transparent Container | M | | 9.3.1.108 | | YES | reject | + +### 9.2.3.14 DOWNLINK RAN STATUS TRANSFER + +This message is sent by the AMF to the target NG-RAN node to transfer the uplink PDCP-SN and HFN receiver status and the downlink PDCP SN and HFN transmitter status during intra 5GC NG-based handover. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| RAN Status Transfer
Transparent Container | M | | 9.3.1.108 | | YES | reject | + +### 9.2.3.15 HANDOVER SUCCESS + +This message is sent by the AMF to the source NG-RAN node to indicate the successful access of the UE toward the target NG-RAN node. + +Direction: AMF → NG-RAN node. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | + +### 9.2.3.16 UPLINK RAN EARLY STATUS TRANSFER + +This message is sent by the source NG-RAN node to transfer the COUNT value(s) of the first forwarded downlink SDU(s) during NG DAPS Handover, and during NG-handover with time-based trigger condition. + +Direction: NG-RAN node → AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| Early Status Transfer
Transparent Container | M | | 9.3.1.190 | | YES | reject | + +### 9.2.3.17 DOWNLINK RAN EARLY STATUS TRANSFER + +This message is sent by the AMF to transfer the COUNT value(s) of the first forwarded downlink SDU(s) during NG DAPS Handover, and during NG-handover with time-based trigger condition. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| Early Status Transfer
Transparent Container | M | | 9.3.1.190 | | YES | reject | + +## 9.2.4 Paging Messages + +### 9.2.4.1 PAGING + +This message is sent by the AMF and is used to page a UE in one or several tracking areas. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------|----------|---------------------------|-------------------------|-------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| UE Paging Identity | M | | 9.3.3.18 | | YES | ignore | +| Paging DRX | O | | 9.3.1.90 | | YES | ignore | +| TAI List for Paging | | 1 | | | YES | ignore | +| >TAI List for Paging Item | | 1.. | | | - | | +| >>TAI | M | | 9.3.3.11 | | - | | +| Paging Priority | O | | 9.3.1.78 | | YES | ignore | +| UE Radio Capability for Paging | O | | 9.3.1.68 | | YES | ignore | +| Paging Origin | O | | 9.3.3.22 | | YES | ignore | +| Assistance Data for Paging | O | | 9.3.1.69 | | YES | ignore | +| NB-IoT Paging eDRX Information | O | | 9.3.1.138 | | YES | ignore | +| NB-IoT Paging DRX | O | | 9.3.1.139 | If this IE is present, the Paging DRX IE is ignored. | YES | ignore | +| Enhanced Coverage Restriction | O | | 9.3.1.140 | | YES | ignore | +| WUS Assistance Information | O | | 9.3.1.143 | | YES | ignore | +| E-UTRA Paging eDRX Information | O | | 9.3.1.154 | | YES | ignore | +| CE-mode-B Restricted | O | | 9.3.1.155 | | YES | ignore | +| NR Paging eDRX Information | O | | 9.3.1.227 | | YES | ignore | +| Paging Cause | O | | ENUMERATED (voice, ...) | | YES | ignore | +| PEIPS Assistance Information | O | | 9.3.1.232 | | YES | ignore | + +| Range bound | Explanation | +|---------------------|---------------------------------------------| +| maxnoofTAIforPaging | Maximum no. of TAI for paging. Value is 16. | + +## 9.2.4.2 MULTICAST GROUP PAGING + +This message is sent by the AMF and is used to notify involved UEs about the activation of a multicast MBS session. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------|----------|--------------------------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| MBS Session ID | M | | 9.3.1.206 | | YES | ignore | +| MBS Service Area | O | | 9.3.1.208 | | YES | ignore | +| Multicast Group Paging Area List | | 1 | | | YES | ignore | +| > Multicast Group Paging Area Item | | 1.. | | | - | | +| >>Multicast Group Paging Area | M | | 9.3.1.216 | | - | | +| >> UE Paging List | | 0..1 | | | - | | +| >>> UE Paging Item | | 1.. | | | - | | +| >>>>UE Identity Index Value | M | | 9.3.3.23 | | - | | +| >>>>Paging DRX | O | | 9.3.1.90 | | - | | + +| Range bound | Explanation | +|---------------------|----------------------------------------------------------------------------------------------| +| maxnoofPagingAreas | Maximum no. of paging areas for multicast group paging. Value is 64. | +| maxnoofUEsforPaging | Maximum no. of UEs allowed within one paging area for multicast group paging. Value is 4096. | + +## 9.2.5 NAS Transport Messages + +### 9.2.5.1 INITIAL UE MESSAGE + +This message is sent by the NG-RAN node to transfer the initial layer 3 message to the AMF over the NG interface. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------|----------|-------|-----------------------------|-------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| NAS-PDU | M | | 9.3.3.4 | | YES | reject | +| User Location Information | M | | 9.3.1.16 | | YES | reject | +| RRC Establishment Cause | M | | 9.3.1.111 | | YES | ignore | +| 5G-S-TMSI | O | | 9.3.3.20 | | YES | reject | +| AMF Set ID | O | | 9.3.3.12 | | YES | ignore | +| UE Context Request | O | | ENUMERATED (requested, ...) | | YES | ignore | +| Allowed NSSAI | O | | 9.3.1.31 | | YES | reject | +| Source to Target AMF Information Reroute | O | | 9.3.3.27 | | YES | ignore | +| Selected PLMN Identity | O | | PLMN Identity 9.3.3.5 | Indicates the selected PLMN id for the non-3GPP access. | YES | ignore | +| IAB Node Indication | O | | ENUMERATED (true, ...) | Indication of an IAB node | YES | reject | +| CE-mode-B Support Indicator | O | | 9.3.1.156 | | YES | reject | +| LTE-M Indication | O | | 9.3.1.157 | | YES | ignore | +| EDT Session | O | | ENUMERATED (true, ...) | | YES | ignore | +| Authenticated Indication | O | | ENUMERATED (true, ...) | Indicates the FN-RG has been authenticated by the access network. | YES | ignore | +| NPN Access Information | O | | 9.3.3.46 | | YES | reject | +| RedCap Indication | O | | 9.3.1.228 | | YES | ignore | +| Selected NID | O | | NID 9.3.3.42 | Indicates together with the Selected PLMN Identity IE, the selected SNPn Identity for the non-3GPP access. | YES | ignore | +| Mobile IAB Node Indication | O | | ENUMERATED (true, ...) | Indicates that the UE is a mobile IAB-node | YES | reject | +| Partially Allowed NSSAI | O | | 9.3.1.261 | Indicates the S-NSSAIs partially permitted by the network. | YES | ignore | + +### 9.2.5.2 DOWNLINK NAS TRANSPORT + +This message is sent by the AMF and is used for carrying NAS information over the NG interface. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------|----------|-------|-----------------------|------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| Old AMF | O | | AMF Name
9.3.3.21 | | YES | reject | +| RAN Paging Priority | O | | 9.3.3.15 | | YES | ignore | +| NAS-PDU | M | | 9.3.3.4 | | YES | reject | +| Mobility Restriction List | O | | 9.3.1.85 | | YES | ignore | +| Index to RAT/Frequency Selection Priority | O | | 9.3.1.61 | | YES | ignore | +| UE Aggregate Maximum Bit Rate | O | | 9.3.1.58 | | YES | ignore | +| Allowed NSSAI | O | | 9.3.1.31 | Indicates the S-NSSAIs permitted by the network. | YES | reject | +| SRVCC Operation Possible | O | | 9.3.1.128 | | YES | ignore | +| Enhanced Coverage Restriction | O | | 9.3.1.140 | | YES | ignore | +| Extended Connected Time | O | | 9.3.3.31 | | YES | ignore | +| UE Differentiation Information | O | | 9.3.1.144 | | YES | ignore | +| CE-mode-B Restricted | O | | 9.3.1.155 | | YES | ignore | +| UE Radio Capability | O | | 9.3.1.74 | | YES | ignore | +| UE Capability Info Request | O | | 9.3.1.192 | | YES | ignore | +| End Indication | O | | 9.3.3.32 | | YES | ignore | +| UE Radio Capability ID | O | | 9.3.1.142 | | YES | reject | +| Target NSSAI Information | O | | 9.3.1.229 | | YES | ignore | +| Masked IMEISV | O | | 9.3.1.54 | | YES | ignore | +| Partially Allowed NSSAI | O | | 9.3.1.261 | Indicates the S-NSSAIs partially permitted by the network. | YES | ignore | + +### 9.2.5.3 UPLINK NAS TRANSPORT + +This message is sent by the NG-RAN node and is used for carrying NAS information over the NG interface. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------|----------|-------|-----------------------|----------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| NAS-PDU | M | | 9.3.3.4 | | YES | reject | +| User Location Information | M | | 9.3.1.16 | | YES | ignore | +| W-AGF Identity Information | O | | OCTET STRING | Containing the WAgfInfo IE specified in TS 29.510 [36]. | YES | reject | +| TNGF Identity Information | O | | OCTET STRING | Containing the TngfInfo IE specified in TS 29.510 [36]. | YES | reject | +| TWIF Identity Information | O | | OCTET STRING | Containing the TwifInfo IE specified in TS 29.510 [36]. | YES | reject | + +#### 9.2.5.4 NAS NON DELIVERY INDICATION + +This message is sent by the NG-RAN node and is used for reporting the non-delivery of a NAS PDU previously received within a DOWNLINK NAS TRANSPORT message or the *NAS-PDU* IE previously received within the PDU SESSION RESOURCE SETUP REQUEST message over the NG interface. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| NAS-PDU | M | | 9.3.3.4 | | YES | ignore | +| Cause | M | | 9.3.1.2 | | YES | ignore | + +### 9.2.5.5 REROUTE NAS REQUEST + +This message is sent by the AMF in order to request for a rerouting of the INITIAL UE MESSAGE to another AMF. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------|----------|-------|-----------------------|------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| AMF UE NGAP ID | O | | 9.3.3.1 | | YES | ignore | +| NGAP Message | M | | OCTET STRING | Contains the INITIAL UE MESSAGE | YES | reject | +| AMF Set ID | M | | 9.3.3.12 | | YES | reject | +| Allowed NSSAI | O | | 9.3.1.31 | | YES | reject | +| Source to Target AMF Information Reroute | O | | 9.3.3.27 | | YES | ignore | +| Partially Allowed NSSAI | O | | 9.3.1.261 | Indicates the S-NSSAIs partially permitted by the network. | YES | ignore | + +## 9.2.6 Interface Management Messages + +### 9.2.6.1 NG SETUP REQUEST + +This message is sent by the NG-RAN node to transfer application layer information for an NG-C interface instance. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------------------------|----------|---------------------|---------------------------------------|-------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| Global RAN Node ID | M | | 9.3.1.5 | | YES | reject | +| RAN Node Name | O | | PrintableString (SIZE(1..150, ...)) | | YES | ignore | +| Supported TA List | | 1 | | Supported TAs in the NG-RAN node. | YES | reject | +| >Supported TA Item | | 1.. | | | - | | +| >>TAC | M | | 9.3.3.10 | Broadcast TAC | - | | +| >>Broadcast PLMN List | | 1 | | | - | | +| >>>Broadcast PLMN Item | | 1.. | | | - | | +| >>>>PLMN Identity | M | | 9.3.3.5 | Broadcast PLMN | - | | +| >>>>TAI Slice Support List | M | | Slice Support List 9.3.1.17 | Supported S-NSSAIs per TAC, per PLMN or per SNPN. | - | | +| >>>>NPN Support | O | | 9.3.3.44 | If the NID IE is included, it identifies a SNPN together with the PLMN Identity IE. | YES | reject | +| >>>>Extended TAI Slice Support List | O | | Extended Slice Support List 9.3.1.191 | Additional Supported S-NSSAIs per TAC, per PLMN or per SNPN. | YES | reject | +| >>>>TAI NSAG Support List | O | | 9.3.1.238 | NSAG information associated with the slices per TAC, per PLMN or per SNPN. | YES | ignore | +| >>Configured TAC Indication | O | | 9.3.3.50 | | YES | ignore | +| >>RAT Information | O | | 9.3.1.125 | RAT information associated with the TAC of the indicated PLMN(s). | YES | reject | +| Default Paging DRX | M | | Paging DRX 9.3.1.90 | | YES | ignore | +| UE Retention Information | O | | 9.3.1.117 | | YES | ignore | +| NB-IoT Default Paging DRX | O | | 9.3.1.137 | | YES | ignore | +| Extended RAN Node Name | O | | 9.3.1.193 | | YES | ignore | + +| Range bound | Explanation | +|---------------|----------------------------------------------| +| maxnoofTACs | Maximum no. of TACs. Value is 256. | +| maxnoofBPLMNs | Maximum no. of Broadcast PLMNs. Value is 12. | + +### 9.2.6.2 NG SETUP RESPONSE + +This message is sent by the AMF to transfer application layer information for an NG-C interface instance. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------|----------|----------------------------|-------------------------------------|---------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF Name | M | | 9.3.3.21 | | YES | reject | +| Served GUAMI List | | 1 | | | YES | reject | +| >Served GUAMI Item | | 1.. | | | - | | +| >>GUAMI | M | | 9.3.3.3 | | - | | +| >>Backup AMF Name | O | | AMF Name
9.3.3.21 | | - | | +| >>GUAMI Type | O | | ENUMERATED
(native, mapped, ...) | | YES | ignore | +| Relative AMF Capacity | M | | 9.3.1.32 | | YES | ignore | +| PLMN Support List | | 1 | | | YES | reject | +| >PLMN Support Item | | 1.. | | | - | | +| >>PLMN Identity | M | | 9.3.3.5 | | - | | +| >>Slice Support List | M | | 9.3.1.17 | Supported S-NSSAIs per PLMN or per SNPN. | - | | +| >>NPN Support | O | | 9.3.3.44 | If NID IE is included, it identifies a SNPN together with the PLMN Identity IE. | YES | reject | +| >>Extended Slice Support List | O | | 9.3.1.191 | Additional Supported S-NSSAIs per PLMN or per SNPN. | YES | reject | +| >>Onboarding Support | O | | ENUMERATED
(true, ...) | Indication of onboarding support. | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | +| UE Retention Information | O | | 9.3.1.117 | | YES | ignore | +| IAB Supported | O | | ENUMERATED
(true, ...) | Indication of support for IAB. | YES | ignore | +| Extended AMF Name | O | | 9.3.3.51 | | YES | ignore | +| Mobile IAB Supported | O | | ENUMERATED
(true, ...) | Indication of support for mobile IAB. | YES | ignore | + +| Range bound | Explanation | +|---------------------|-------------------------------------------------------| +| maxnoofServedGUAMIs | Maximum no. of GUAMIs served by an AMF. Value is 256. | +| maxnoofPLMNs | Maximum no. of PLMNs per message. Value is 12. | + +### 9.2.6.3 NG SETUP FAILURE + +This message is sent by the AMF to indicate NG setup failure. + +Direction: AMF → NG-RAN node + +| 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 | +| Time to Wait | O | | 9.3.1.56 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.6.4 RAN CONFIGURATION UPDATE + +This message is sent by the NG-RAN node to transfer updated application layer information for an NG-C interface instance. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------------------------------|----------|------------------------------|----------------------------------------|-------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| RAN Node Name | O | | PrintableString (SIZE(1..150, ...)) | | YES | ignore | +| Supported TA List | | 0..1 | | Supported TAs in the NG-RAN node. | YES | reject | +| >Supported TA Item | | 1.. | | | - | | +| >>TAC | M | | 9.3.3.10 | Broadcast TAC | - | | +| >>Broadcast PLMN List | | 1 | | | - | | +| >>>Broadcast PLMN Item | | 1.. | | | - | | +| >>>>PLMN Identity | M | | 9.3.3.5 | Broadcast PLMN | - | | +| >>>>TAI Slice Support List | M | | Slice Support List 9.3.1.17 | Supported S-NSSAIs per TAC, per PLMN or per SNPN. | - | | +| >>>>NPN Support | O | | 9.3.3.44 | If the NID IE is included, it identifies a SNPN together with the PLMN Identity IE. | YES | reject | +| >>>>Extended TAI Slice Support List | O | | Extended Slice Support List 9.3.1.191 | Additional Supported S-NSSAIs per TAC, per PLMN or per SNPN. | YES | reject | +| >>>>TAI NSAG Support List | O | | 9.3.1.238 | NSAG information associated with the slices per TAC, per PLMN or per SNPN. | YES | ignore | +| >>Configured TAC Indication | O | | 9.3.3.50 | | YES | ignore | +| >>RAT Information | O | | 9.3.1.125 | RAT information associated with the TAC of the indicated PLMN(s). | YES | reject | +| Default Paging DRX | O | | Paging DRX 9.3.1.90 | | YES | ignore | +| Global RAN Node ID | O | | 9.3.1.5 | | YES | ignore | +| NG-RAN TNL Association to Remove List | | 0..1 | | | YES | reject | +| >NG-RAN TNL Association to Remove Item | | 1.. | | | - | | +| >>TNL Association Transport Layer Address | M | | CP Transport Layer Information 9.3.2.6 | Transport layer address of the NG-RAN node. | - | | +| >>TNL Association Transport Layer Address at AMF | O | | CP Transport Layer Information 9.3.2.6 | Transport layer address of the AMF. | - | | + +| | | | | | | | +|---------------------------|---|--|-----------|--|-----|--------| +| NB-IoT Default Paging DRX | O | | 9.3.1.137 | | YES | ignore | +| Extended RAN Node Name | O | | 9.3.1.193 | | YES | ignore | + +| Range bound | Explanation | +|------------------------|-----------------------------------------------------------------------------------| +| maxnoofTACs | Maximum no. of TACs. Value is 256. | +| maxnoofBPLMNs | Maximum no. of Broadcast PLMNs. Value is 12. | +| maxnoofTNLAssociations | Maximum no. of TNL Associations between the NG-RAN node and the AMF. Value is 32. | + +### 9.2.6.5 RAN CONFIGURATION UPDATE ACKNOWLEDGE + +This message is sent by the AMF to acknowledge the NG-RAN node transfer of updated information for an NG-C interface instance. + +Direction: AMF → NG-RAN node + +| 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.6.6 RAN CONFIGURATION UPDATE FAILURE + +This message is sent by the AMF to indicate RAN configuration update failure. + +Direction: AMF → NG-RAN node + +| 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 | +| Time to Wait | O | | 9.3.1.56 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.6.7 AMF CONFIGURATION UPDATE + +This message is sent by the AMF to transfer updated information for an NG-C interface instance. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------|----------|------------------------------|-------------------------------------------|-------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF Name | O | | 9.3.3.21 | | YES | reject | +| Served GUAMI List | | 0..1 | | | YES | reject | +| >Served GUAMI Item | | 1.. | | | - | | +| >>GUAMI | M | | 9.3.3.3 | | - | | +| >>Backup AMF Name | O | | AMF Name
9.3.3.21 | | - | | +| >>GUAMI Type | O | | ENUMERATED
(native, mapped, ...) | | YES | ignore | +| Relative AMF Capacity | O | | 9.3.1.32 | | YES | ignore | +| PLMN Support List | | 0..1 | | | YES | reject | +| >PLMN Support Item | | 1.. | | | - | | +| >>PLMN Identity | M | | 9.3.3.5 | | - | | +| >>Slice Support List | M | | 9.3.1.17 | Supported S-NSSAIs per PLMN or per SNPN. | - | | +| >>NPN Support | O | | 9.3.3.44 | If the NID IE is included, it identifies a SNPN together with the PLMN Identity IE. | YES | reject | +| >>Extended Slice Support List | O | | 9.3.1.191 | Additional Supported S-NSSAIs per PLMN or per SNPN. | YES | reject | +| >>Onboarding Support | O | | ENUMERATED
(true, ...) | Indication of onboarding support. | YES | ignore | +| AMF TNL Association to Add List | | 0..1 | | | YES | ignore | +| >AMF TNL Association to Add Item | | 1.. | | | - | | +| >>AMF TNL Association Address | M | | CP Transport Layer Information
9.3.2.6 | AMF Transport Layer information used to set up the new TNL association. | - | | +| >>TNL Association Usage | O | | 9.3.2.9 | | - | | +| >>TNL Address Weight Factor | M | | 9.3.2.10 | | - | | +| AMF TNL Association to Remove List | | 0..1 | | | YES | ignore | +| >AMF TNL Association to Remove Item | | 1.. | | | - | | +| >>AMF TNL Association Address | M | | CP Transport Layer Information
9.3.2.6 | Transport Layer Address of the AMF. | - | | +| >>TNL Association Transport Layer | O | | CP Transport | Transport Layer Address of the NG- | YES | reject | + +| | | | | | | | +|---------------------------------------------|---|------------------------------|----------------------------------------|-------------------------------------------------------------------------------------|-----|--------| +| Address NG-RAN | | | Layer Address 9.3.2.6 | RAN node. | | | +| AMF TNL Association to Update List | | 0..1 | | | YES | ignore | +| > AMF TNL Association to Update Item | | 1.. | | | - | | +| >>AMF TNL Association Address | M | | CP Transport Layer Information 9.3.2.6 | AMF Transport Layer information used to identify the TNL association to be updated. | - | | +| >>TNL Association Usage | O | | 9.3.2.9 | | - | | +| >>TNL Address Weight Factor | O | | 9.3.2.10 | | - | | +| Extended AMF Name | O | | 9.3.3.51 | | YES | ignore | + +| Range bound | Explanation | +|------------------------|-----------------------------------------------------------------------------------| +| maxnoofServedGUAMIs | Maximum no. of GUAMIs served by an AMF. Value is 256. | +| maxnoofPLMNs | Maximum no. of PLMNs per message. Value is 12. | +| maxnoofTNLAssociations | Maximum no. of TNL Associations between the NG-RAN node and the AMF. Value is 32. | + +## 9.2.6.8 AMF CONFIGURATION UPDATE ACKNOWLEDGE + +This message is sent by the NG-RAN node to acknowledge the AMF transfer of updated information for an NG-C interface instance. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------|----------|------------------------------|----------------------------------------|------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF TNL Association Setup List | | 0..1 | | | YES | ignore | +| > AMF TNL Association Setup Item | | 1.. | | | - | | +| >>AMF TNL Association Address | M | | CP Transport Layer Information 9.3.2.6 | Previously received AMF Transport Layer information for the TNL association. | - | | +| AMF TNL Association Failed to Setup List | O | | TNL Association List 9.3.2.7 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +| Range bound | Explanation | +|------------------------|-----------------------------------------------------------------------------------| +| maxnoofTNLAssociations | Maximum no. of TNL Associations between the NG-RAN node and the AMF. Value is 32. | + +### 9.2.6.9 AMF CONFIGURATION UPDATE FAILURE + +This message is sent by the NG-RAN node to indicate AMF configuration update failure. + +Direction: NG-RAN node → AMF + +| 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 | +| Time to Wait | O | | 9.3.1.56 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.6.10 AMF STATUS INDICATION + +This message is sent by the AMF to support AMF management functions. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------|----------|----------------------------|-------------------------------|--------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| Unavailable GUAMI List | | 1 | | Indicates the GUAMIs configured to be unavailable at the AMF | YES | reject | +| >Unavailable GUAMI Item | | 1.. | | | - | | +| >>GUAMI | M | | 9.3.3.3 | | - | | +| >>Timer Approach for GUAMI Removal | O | | ENUMERATED (apply timer, ...) | | - | | +| >>Backup AMF Name | O | | AMF Name 9.3.3.21 | | - | | + +| Range bound | Explanation | +|---------------------|-------------------------------------------------------| +| maxnoofServedGUAMIs | Maximum no. of GUAMIs served by an AMF. Value is 256. | + +### 9.2.6.11 NG RESET + +This message is sent by both the NG-RAN node and the AMF to request that the NG interface, or parts of the NG interface, be reset. + +Direction: NG-RAN node → AMF and AMF → NG-RAN node + +| 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 | +| CHOICE Reset Type | M | | | | YES | reject | +| > NG interface | | | | | | | +| >>Reset All | M | | ENUMERATED
(Reset all, ...) | | - | | +| > Part of NG interface | | | | | | | +| >>UE-associated
Logical NG-connection
List | M | | 9.3.3.25 | | - | | + +### 9.2.6.12 NG RESET ACKNOWLEDGE + +This message is sent by both the NG-RAN node and the AMF as a response to an NG RESET message. + +Direction: NG-RAN node → AMF and AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| UE-associated Logical
NG-connection List | O | | 9.3.3.25 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.6.13 ERROR INDICATION + +This message is sent by both the NG-RAN node and the AMF to indicate that some error has been detected in the node. + +Direction: NG-RAN node → AMF and AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| AMF UE NGAP ID | O | | 9.3.3.1 | | YES | ignore | +| RAN UE NGAP ID | O | | 9.3.3.2 | | YES | ignore | +| Cause | O | | 9.3.1.2 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | +| 5G-S-TMSI | O | | 9.3.3.20 | | YES | ignore | + +### 9.2.6.14 OVERLOAD START + +This message is sent by the AMF and is used to indicate to the NG-RAN node that the AMF is overloaded. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------|----------|-------------------------|------------------------------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| AMF Overload Response | O | | Overload Response
9.3.1.104 | | YES | reject | +| AMF Traffic Load Reduction Indication | O | | Traffic Load Reduction Indication
9.3.1.106 | | YES | ignore | +| Overload Start NSSAI List | | 0..1 | | | YES | ignore | +| > Overload Start NSSAI Item | | 1.. | | | - | | +| >>Slice Overload List | M | | 9.3.1.107 | | - | | +| >>Slice Overload Response | O | | Overload Response
9.3.1.104 | | - | | +| >>Slice Traffic Load Reduction Indication | O | | Traffic Load Reduction Indication
9.3.1.106 | | - | | + +| Range bound | Explanation | +|-------------------|--------------------------------------------------------------| +| maxnoofSliceItems | Maximum no. of signalled slice support items. Value is 1024. | + +## 9.2.6.15 OVERLOAD STOP + +This message is sent by the AMF and is used to indicate that the AMF is no longer overloaded. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | + +## 9.2.7 Configuration Transfer Messages + +### 9.2.7.1 UPLINK RAN CONFIGURATION TRANSFER + +This message is sent by the NG-RAN node in order to transfer RAN configuration information. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| SON Configuration Transfer | O | | 9.3.3.6 | | YES | ignore | +| EN-DC SON Configuration Transfer | O | | OCTET STRING | Contains the EN-DC SON Configuration Transfer IE as defined in TS 36.413 [16]. | YES | ignore | +| Inter-system SON Configuration Transfer | O | | 9.3.3.33 | | YES | ignore | + +## 9.2.7.2 DOWNLINK RAN CONFIGURATION TRANSFER + +This message is sent by the AMF in order to transfer RAN configuration information. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| SON Configuration Transfer | O | | 9.3.3.6 | | YES | ignore | +| EN-DC SON Configuration Transfer | O | | OCTET STRING | Contains the EN-DC SON Configuration Transfer IE as defined in TS 36.413 [16]. | YES | ignore | +| Inter-system SON Configuration Transfer | O | | 9.3.3.33 | | YES | ignore | + +## 9.2.8 Warning Message Transmission Messages + +### 9.2.8.1 WRITE-REPLACE WARNING REQUEST + +This message is sent by the AMF to request the start or overwrite of the broadcast of a warning message. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------|----------|-------|-------------------------|---------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| Message Identifier | M | | 9.3.1.35 | | YES | reject | +| Serial Number | M | | 9.3.1.36 | | YES | reject | +| Warning Area List | O | | 9.3.1.37 | | YES | ignore | +| Repetition Period | M | | 9.3.1.49 | | YES | reject | +| Number of Broadcasts Requested | M | | 9.3.1.38 | | YES | reject | +| Warning Type | O | | 9.3.1.39 | | YES | ignore | +| Warning Security Information | O | | OCTET STRING (SIZE(50)) | This IE is not used in the specification. If received, the IE is ignored. | YES | ignore | +| Data Coding Scheme | O | | 9.3.1.41 | | YES | ignore | +| Warning Message Contents | O | | 9.3.1.42 | | YES | ignore | +| Concurrent Warning Message Indicator | O | | 9.3.1.46 | | YES | reject | +| Warning Area Coordinates | O | | 9.3.1.112 | | YES | ignore | + +## 9.2.8.2 WRITE-REPLACE WARNING RESPONSE + +This message is sent by the NG-RAN node to acknowledge the AMF on the start or overwrite request of a warning message. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| Message Identifier | M | | 9.3.1.35 | | YES | reject | +| Serial Number | M | | 9.3.1.36 | | YES | reject | +| Broadcast Completed Area List | O | | 9.3.1.43 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +## 9.2.8.3 PWS CANCEL REQUEST + +This message is forwarded by the AMF to the NG-RAN node to cancel an already ongoing broadcast of a warning message. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| Message Identifier | M | | 9.3.1.35 | | YES | reject | +| Serial Number | M | | 9.3.1.36 | | YES | reject | +| Warning Area List | O | | 9.3.1.37 | | YES | ignore | +| Cancel-All Warning Messages Indicator | O | | 9.3.1.47 | | YES | reject | + +### 9.2.8.4 PWS CANCEL RESPONSE + +This message is sent by the NG-RAN node to indicate the list of warning areas where cancellation of the broadcast of the identified message was successful and unsuccessful. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| Message Identifier | M | | 9.3.1.35 | | YES | reject | +| Serial Number | M | | 9.3.1.36 | | YES | reject | +| Broadcast Cancelled Area List | O | | 9.3.1.44 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.8.5 PWS RESTART INDICATION + +This message is sent by the NG-RAN node to inform the AMF that PWS information for some or all cells of the NG-RAN node are available for reloading from the CBC if needed. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------|----------|-----------------------------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| CHOICE Cell List for Restart | M | | | | YES | reject | +| >E-UTRA | | | | | | | +| >>E-UTRA Cell List for Restart | | 1.. | | | - | | +| >>>E-UTRA CGI | M | | 9.3.1.9 | | - | | +| >NR | | | | | | | +| >>NR Cell List for Restart | | 1.. | | | - | | +| >>>NR CGI | M | | 9.3.1.7 | | - | | +| Global RAN Node ID | M | | 9.3.1.5 | | YES | reject | +| TAI List for Restart | | 1.. | | | YES | reject | +| >TAI | M | | 9.3.3.11 | | - | | +| Emergency Area ID List for Restart | | 0.. | | | YES | reject | +| >Emergency Area ID | M | | 9.3.1.48 | | - | | + +| Range bound | Explanation | +|----------------------|--------------------------------------------------------------------------------------------------| +| maxnoofCellsinngeNB | Maximum no. of cells that can be served by an ng-eNB. Value is 256. | +| maxnoofCellsingNB | Maximum no. of cells that can be served by a gNB. Value is 16384. | +| maxnoofTAIforRestart | Maximum no. of TAIs subject for reloading warning message broadcast. Value is 2048. | +| maxnoofEAIforRestart | Maximum no. of Emergency Area IDs subject for reloading warning message broadcast. Value is 256. | + +### 9.2.8.6 PWS FAILURE INDICATION + +This message is sent by the NG-RAN node to inform the AMF that ongoing PWS operation for one or more cells of the NG-RAN node has failed. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------|----------|----------------------------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| CHOICE PWS Failed Cell List | M | | | | YES | reject | +| >E-UTRA | | | | | | | +| >>PWS Failed E-UTRA Cell List | | 1.. | | | - | | +| >>>E-UTRA CGI | M | | 9.3.1.9 | | - | | +| >NR | | | | | | | +| >>PWS Failed NR Cell List | | 1.. | | | - | | +| >>>NR CGI | M | | 9.3.1.7 | | - | | +| Global RAN Node ID | M | | 9.3.1.5 | | YES | reject | + +| Range bound | Explanation | +|---------------------|---------------------------------------------------------------------| +| maxnoofCellsinngeNB | Maximum no. of cells that can be served by an ng-eNB. Value is 256. | +| maxnoofCellsingNB | Maximum no. of cells that can be served by a gNB. Value is 16384. | + +### 9.2.9 NRPPa Transport Messages + +#### 9.2.9.1 DOWNLINK UE ASSOCIATED NRPPA TRANSPORT + +This message is sent by the AMF and is used for carrying NRPPa message over the NG interface. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| Routing ID | M | | 9.3.3.13 | | YES | reject | +| NRPPa-PDU | M | | 9.3.3.14 | | YES | reject | + +#### 9.2.9.2 UPLINK UE ASSOCIATED NRPPA TRANSPORT + +This message is sent by the NG-RAN node and is used for carrying NRPPa message over the NG interface. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| Routing ID | M | | 9.3.3.13 | | YES | reject | +| NRPPa-PDU | M | | 9.3.3.14 | | YES | reject | + +### 9.2.9.3 DOWNLINK NON UE ASSOCIATED NRPPA TRANSPORT + +This message is sent by the AMF and is used for carrying NRPPa message over the NG interface. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| Routing ID | M | | 9.3.3.13 | | YES | reject | +| NRPPa-PDU | M | | 9.3.3.14 | | YES | reject | + +### 9.2.9.4 UPLINK NON UE ASSOCIATED NRPPA TRANSPORT + +This message is sent by the NG-RAN node and is used for carrying NRPPa message over the NG interface. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| Routing ID | M | | 9.3.3.13 | | YES | reject | +| NRPPa-PDU | M | | 9.3.3.14 | | YES | reject | + +## 9.2.10 Trace Messages + +### 9.2.10.1 TRACE START + +This message is sent by the AMF to initiate a trace session for a UE. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| Trace Activation | M | | 9.3.1.14 | | YES | ignore | + +### 9.2.10.2 TRACE FAILURE INDICATION + +This message is sent by the NG-RAN node to indicate that a Trace Start procedure or a Deactivate Trace procedure has failed for a UE. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------|----------|-------|------------------------|------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| NG-RAN Trace ID | M | | OCTET STRING (SIZE(8)) | As per NG-RAN Trace ID in Trace Activation IE | YES | ignore | +| Cause | M | | 9.3.1.2 | | YES | ignore | + +### 9.2.10.3 DEACTIVATE TRACE + +This message is sent by the AMF to deactivate a trace session. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------|----------|-------|------------------------|------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| NG-RAN Trace ID | M | | OCTET STRING (SIZE(8)) | As per NG-RAN Trace ID in Trace Activation IE | YES | ignore | + +### 9.2.10.4 CELL TRAFFIC TRACE + +This message is sent by the NG-RAN node to transfer trace specific information. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------|----------|-------|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| NG-RAN Trace ID | M | | OCTET STRING (SIZE(8)) | This IE is composed of the following: Trace Reference defined in TS 32.422 [11] (leftmost 6 octets, with PLMN information encoded as in 9.3.3.5), and Trace Recording Session Reference defined in TS 32.422 [11] (last 2 octets). | YES | ignore | +| NG-RAN CGI | M | | 9.3.1.73 | | YES | ignore | +| Trace Collection Entity IP Address | M | | Transport Layer Address 9.3.2.4 | For File based Reporting. Defined in TS 32.422 [11]. This IE is ignored if the Trace Collection Entity URI IE is present | YES | ignore | +| Privacy Indicator | O | | ENUMERATED (Immediate MDT, Logged MDT, ...) | | YES | ignore | +| Trace Collection Entity URI | O | | URI 9.3.2.14 | For Streaming based Reporting. Defined in TS 32.422 [11]. | YES | ignore | + +## 9.2.11 Location Reporting Messages + +### 9.2.11.1 LOCATION REPORTING CONTROL + +This message is used by the AMF to request the NG-RAN node to report the location of the UE. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| Location Reporting Request Type | M | | 9.3.1.65 | | YES | ignore | + +## 9.2.11.2 LOCATION REPORTING FAILURE INDICATION + +This message is sent by the NG-RAN node and is used to indicate the failure of location reporting. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| Cause | M | | 9.3.1.2 | | YES | ignore | + +## 9.2.11.3 LOCATION REPORT + +This message is used to provide the UE's location. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| User Location Information | M | | 9.3.1.16 | | YES | ignore | +| UE Presence in Area of Interest List | O | | 9.3.1.67 | | YES | ignore | +| Location Reporting Request Type | M | | 9.3.1.65 | Contains the Location Reporting Request Type to which the Location Report refers. | YES | ignore | + +## 9.2.12 UE TNLA Binding Messages + +### 9.2.12.1 UE TNLA BINDING RELEASE REQUEST + +This message is sent by the AMF to request the NG-RAN node to release the TNLA binding for the respective UE. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | + +## 9.2.13 UE Radio Capability Management Messages + +### 9.2.13.1 UE RADIO CAPABILITY INFO INDICATION + +This message is sent by the NG-RAN node to provide UE radio capability related information to the AMF. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| UE Radio Capability | M | | 9.3.1.74 | | YES | ignore | +| UE Radio Capability for Paging | O | | 9.3.1.68 | | YES | ignore | +| UE Radio Capability – E-UTRA Format | O | | 9.3.1.74a | | YES | ignore | + +### 9.2.13.2 UE RADIO CAPABILITY CHECK REQUEST + +This message is sent by the AMF to request the NG-RAN node to check the compatibility between the UE radio capabilities and network configuration on IMS voice. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | reject | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | reject | +| UE Radio Capability | O | | 9.3.1.74 | | YES | ignore | +| UE Radio Capability ID | O | | 9.3.1.142 | | YES | reject | + +### 9.2.13.3 UE RADIO CAPABILITY CHECK RESPONSE + +This message is sent by the NG-RAN node to report IMS voice compatibility between the UE radio capabilities and network configuration. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | ignore | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | ignore | +| IMS Voice Support Indicator | M | | 9.3.1.89 | | YES | reject | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.13.4 UE RADIO CAPABILITY ID MAPPING REQUEST + +This message is sent by the NG-RAN node to request the AMF to provide mapping information for the indicated UE Radio Capability ID. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| UE Radio Capability ID | M | | 9.3.1.142 | | YES | reject | + +### 9.2.13.5 UE RADIO CAPABILITY ID MAPPING RESPONSE + +This message is sent by the AMF to provide UE Radio Capability information which is mapped to the UE Radio Capability ID indicated by the NG-RAN node in the UE RADIO CAPABILITY ID MAPPING REQUEST message. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| UE Radio Capability ID | M | | 9.3.1.142 | | YES | reject | +| UE Radio Capability | M | | 9.3.1.74 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +## 9.2.14 Data Usage Reporting Messages + +### 9.2.14.1 SECONDARY RAT DATA USAGE REPORT + +This message is sent by the NG-RAN node to report Secondary RAT data usage. + +Direction: NG-RAN → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------------------|----------|-------------------------|----------------------------------------|---------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| AMF UE NGAP ID | M | | 9.3.3.1 | | YES | ignore | +| RAN UE NGAP ID | M | | 9.3.3.2 | | YES | ignore | +| PDU Session Resource Secondary RAT Usage List | | 1 | | | YES | ignore | +| >PDU Session Resource Secondary RAT Usage Item | | 1.. | | | - | | +| >>PDU Session ID | M | | 9.3.1.50 | | - | | +| >>Secondary RAT Data Usage Report Transfer | M | | OCTET STRING | Containing the Secondary RAT Data Usage Report Transfer IE specified in subclause 9.3.4.23 | - | | +| Handover Flag | O | | ENUMERATED (handover_preparation, ...) | | YES | ignore | +| User Location Information | O | | 9.3.1.16 | | YES | ignore | + +| Range bound | Explanation | +|--------------------|-------------------------------------------------------------------| +| maxnoofPDUSessions | Maximum no. of PDU sessions allowed towards one UE. Value is 256. | + +## 9.2.15 RIM Information Transfer Messages + +### 9.2.15.1 UPLINK RIM INFORMATION TRANSFER + +This message is sent by the NG-RAN node to the AMF to transfer the RIM Information. + +Direction: NG-RAN → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| RIM Information Transfer | O | | 9.3.3.28 | | YES | ignore | + +### 9.2.15.2 DOWNLINK RIM INFORMATION TRANSFER + +This message is sent by the AMF to the NG-RAN node to transfer the RIM Information. + +Direction: AMF → NG-RAN + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| RIM Information Transfer | O | | 9.3.3.28 | | YES | ignore | + +## 9.2.16 Broadcast Session Management Messages + +### 9.2.16.1 BROADCAST SESSION SETUP REQUEST + +This message is sent by the AMF to establish MBS session resources for a broadcast MBS session. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| MBS Session ID | M | | 9.3.1.206 | | YES | reject | +| S-NSSAI | M | | 9.3.1.24 | | YES | reject | +| MBS Service Area | M | | 9.3.1.208 | | YES | reject | +| MBS Session Setup Request Transfer | M | | OCTET STRING | Containing the MBS Session Setup or Modification Request Transfer IE specified in subclause 9.3.5.3 | YES | reject | +| Associated Session ID | O | | 9.3.1.262 | | YES | ignore | + +### 9.2.16.2 BROADCAST SESSION SETUP RESPONSE + +This message is sent by the NG-RAN node to report the successful outcome of the request from the BROADCAST SESSION SETUP REQUEST message. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| MBS Session ID | M | | 9.3.1.206 | | YES | reject | +| MBS Session Setup Response Transfer | O | | OCTET STRING | Containing the MBS Session Setup or Modification Response Transfer IE specified in subclause 9.3.5.5 | YES | reject | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.16.3 BROADCAST SESSION SETUP FAILURE + +This message is sent by the NG-RAN node to report the unsuccessful outcome of the request from the BROADCAST SESSION SETUP REQUEST message. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| MBS Session ID | M | | 9.3.1.206 | | YES | reject | +| MBS Session Setup Failure Transfer | O | | OCTET STRING | Containing the MBS Session Setup or Modification Failure Transfer IE specified in subclause 9.3.5.6 | YES | ignore | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.16.4 BROADCAST SESSION MODIFICATION REQUEST + +This message is sent by the AMF to modify MBS session resources or the MBS session broadcast area of a previously established broadcast MBS session. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| MBS Session ID | M | | 9.3.1.206 | | YES | reject | +| MBS Service Area | O | | 9.3.1.208 | | YES | reject | +| MBS Session Modification Request Transfer | O | | OCTET STRING | Containing the MBS Session Setup or Modification Request Transfer IE specified in subclause 9.3.5.3 | YES | reject | + +### 9.2.16.5 BROADCAST SESSION MODIFICATION RESPONSE + +This message is sent by the NG-RAN node to report the successful outcome of the request from the BROADCAST SESSION MODIFICATION REQUEST message. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| MBS Session ID | M | | 9.3.1.206 | | YES | reject | +| MBS Session Modification Response Transfer | O | | OCTET STRING | Containing the MBS Session Setup or Modification Response Transfer IE specified in subclause 9.3.5.5 | YES | reject | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.16.6 BROADCAST SESSION MODIFICATION FAILURE + +This message is sent by the NG-RAN node to report the unsuccessful outcome of the request from the BROADCAST SESSION MODIFICATION REQUEST message. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| MBS Session ID | M | | 9.3.1.206 | | YES | reject | +| MBS Session Modification Failure Transfer | O | | OCTET STRING | Containing the MBS Session Setup or Modification Failure Transfer IE specified in subclause 9.3.5.6 | YES | ignore | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.16.7 BROADCAST SESSION RELEASE REQUEST + +This message is sent by the AMF to release the MBS session resources of a previously established broadcast MBS session. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| MBS Session ID | M | | 9.3.1.206 | | YES | reject | +| Cause | M | | 9.3.1.2 | | YES | ignore | + +### 9.2.16.8 BROADCAST SESSION RELEASE RESPONSE + +This message is sent by the NG-RAN node to acknowledge the BROADCAST SESSION RELEASE REQUEST message. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| MBS Session ID | M | | 9.3.1.206 | | YES | reject | +| MBS Session Release Response Transfer | O | | OCTET STRING | Containing the MBS Session Release Response Transfer IE specified in subclause 9.3.5.14 | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.16.9 BROADCAST SESSION RELEASE REQUIRED + +This message is sent by the NG-RAN node to trigger the AMF to initiate the release of corresponding MBS session resources. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| MBS Session ID | M | | 9.3.1.206 | | YES | reject | +| Cause | M | | 9.3.1.2 | | YES | ignore | + +### 9.2.16.10 BROADCAST SESSION TRANSPORT REQUEST + +This message is sent by the NG-RAN node to request the setup of the NG-U transport for a broadcast MBS session. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| MBS Session ID | M | | 9.3.1.206 | | YES | reject | +| Broadcast Transport Request Transfer | M | | OCTET STRING | Containing the Broadcast Transport Request Transfer IE specified in subclause 9.3.5.15 | YES | reject | + +### 9.2.16.11 BROADCAST SESSION TRANSPORT RESPONSE + +This message is sent by the AMF to confirm the setup of the NG-U transport for the broadcast MBS session. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| MBS Session ID | M | | 9.3.1.206 | | YES | reject | +| Broadcast Transport Response Transfer | M | | OCTET STRING | Containing the Broadcast Transport Response Transfer IE specified in subclause 9.3.5.16 | YES | reject | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +## 9.2.16.12 BROADCAST SESSION TRANSPORT FAILURE + +This message is sent by the AMF to indicate that the setup of the NG-U transport was unsuccessful. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| MBS Session ID | M | | 9.3.1.206 | | YES | reject | +| Broadcast Transport Failure Transfer | M | | OCTET STRING | Containing the Broadcast Transport Failure Transfer IE specified in subclause 9.3.5.17 | YES | ignore | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +## 9.2.17 Multicast Session Management Messages + +### 9.2.17.1 DISTRIBUTION SETUP REQUEST + +This message is sent by the NG-RAN node to request the setup of the NG-U transport for a multicast MBS session, or for one area session of a location dependent multicast MBS session. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| MBS Session ID | M | | 9.3.1.206 | | YES | reject | +| MBS Area Session ID | O | | 9.3.1.207 | | YES | reject | +| MBS Distribution Setup Request Transfer | M | | OCTET STRING | Containing the MBS Distribution Setup Request Transfer IE specified in subclause 9.3.5.7. | YES | reject | + +### 9.2.17.2 DISTRIBUTION SETUP RESPONSE + +This message is sent by the AMF to confirm the setup of the NG-U transport. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| MBS Session ID | M | | 9.3.1.206 | | YES | reject | +| MBS Area Session ID | O | | 9.3.1.207 | | YES | reject | +| MBS Distribution Setup Response Transfer | M | | OCTET STRING | Containing the MBS Distribution Setup Response Transfer IE specified in subclause 9.3.5.8. | YES | reject | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.17.3 DISTRIBUTION SETUP FAILURE + +This message is sent by the AMF to indicate that the setup of the NG-U transport was unsuccessful. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| MBS Session ID | M | | 9.3.1.206 | | YES | reject | +| MBS Area Session ID | O | | 9.3.1.207 | | YES | reject | +| MBS Distribution Setup Unsuccessful Transfer | M | | OCTET STRING | Containing the MBS Distribution Setup Unsuccessful Transfer IE specified in subclause 9.3.5.9. | YES | ignore | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.17.4 DISTRIBUTION RELEASE REQUEST + +This message is sent by the NG-RAN node to request the release of the NG-U transport. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| MBS Session ID | M | | 9.3.1.206 | | YES | reject | +| MBS Area Session ID | O | | 9.3.1.207 | | YES | reject | +| MBS Distribution Release Request Transfer | M | | OCTET STRING | Containing the MBS Distribution Release Request Transfer IE specified in subclause 9.3.5.10. | YES | reject | +| Cause | M | | 9.3.1.2 | | YES | ignore | + +### 9.2.17.5 DISTRIBUTION RELEASE RESPONSE + +This message is sent by the AMF to confirm the release of the NG-U transport. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| MBS Session ID | M | | 9.3.1.206 | | YES | reject | +| MBS Area Session ID | O | | 9.3.1.207 | | YES | reject | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.17.6 MULTICAST SESSION ACTIVATION REQUEST + +This message is sent by the AMF to a NG-RAN node to request for activating MBS session resources for a multicast MBS session. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| MBS Session ID | M | | 9.3.1.206 | | YES | reject | +| Multicast Session Activation Request Transfer | M | | OCTET STRING | Containing the Multicast Session Activation Request Transfer IE specified in subclause 9.3.5.11. | YES | reject | + +### 9.2.17.7 MULTICAST SESSION ACTIVATION RESPONSE + +This message is sent by the NG-RAN node to the AMF to indicate that the MBS session resources have been activated. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| MBS Session ID | M | | 9.3.1.206 | | YES | reject | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +## 9.2.17.8 MULTICAST SESSION ACTIVATION FAILURE + +This message is sent by the NG-RAN node to the AMF to indicate that the requested activation of the MBS session resources has failed. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.13 | | YES | reject | +| MBS Session ID | M | | 9.3.1.206 | | YES | reject | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +## 9.2.17.9 MULTICAST SESSION DEACTIVATION REQUEST + +This message is sent by the AMF to a NG-RAN node to request to deactivate the MBS session resources of a multicast MBS session. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| MBS Session ID | M | | 9.3.1.206 | | YES | reject | +| Multicast Session Deactivation Request Transfer | M | | OCTET STRING | Containing the Multicast Session Deactivation Request Transfer IE specified in subclause 9.3.5.12. | YES | reject | + +## 9.2.17.10 MULTICAST SESSION DEACTIVATION RESPONSE + +This message is sent by the NG-RAN node to the AMF to indicate that the MBS session resources have been deactivated. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| MBS Session ID | M | | 9.3.1.206 | | YES | reject | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +## 9.2.17.11 MULTICAST SESSION UPDATE REQUEST + +This message is sent by the AMF to a NG-RAN node to update the MBS session resources information. + +Direction: AMF → NG-RAN node + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| MBS Session ID | M | | 9.3.1.206 | | YES | reject | +| MBS Area Session ID | O | | 9.3.1.207 | | YES | reject | +| Multicast Session Update Request Transfer | M | | OCTET STRING | Containing the Multicast Session Update Request Transfer IE specified in subclause 9.3.5.13. | YES | reject | + +## 9.2.17.12 MULTICAST SESSION UPDATE RESPONSE + +This message is sent by the NG-RAN node to the AMF to confirm the update of MBS information. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| MBS Session ID | M | | 9.3.1.206 | | YES | reject | +| MBS Area Session ID | O | | 9.3.1.207 | | YES | reject | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +## 9.2.17.13 MULTICAST SESSION UPDATE FAILURE + +This message is sent by the NG-RAN node to the AMF to indicate multicast session update failure. + +Direction: NG-RAN node → AMF + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| MBS Session ID | M | | 9.3.1.206 | | YES | reject | +| MBS Area Session ID | O | | 9.3.1.207 | | YES | reject | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +## 9.2.18 Timing Synchronisation Status Reporting Messages + +### 9.2.18.1 TIMING SYNCHRONISATION STATUS REQUEST + +This message is sent by the AMF to request the NG-RAN node to start or stop reporting of RAN timing synchronization status information. + +Direction: AMF → NG-RAN node + +| 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.18.2 TIMING SYNCHRONISATION STATUS RESPONSE + +This message is sent by the NG-RAN node to confirm the request to start or stop reporting of RAN timing synchronization status information. + +Direction: NG-RAN node → AMF + +| 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.18.3 TIMING SYNCHRONISATION STATUS FAILURE + +This message is sent by the NG-RAN node to indicate that reporting of RAN timing synchronisation status information cannot be initiated. + +Direction: NG-RAN node → AMF + +| 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.18.4 TIMING SYNCHRONISATION STATUS REPORT + +This message is sent by the NG-RAN node to report previously requested RAN timing synchronisation status information. + +Direction: NG-RAN node → AMF + +| 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.252 | | YES | ignore | +| RAN TSS Scope | M | | 9.3.1.254 | | 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 | +|-----------------|----------|-------|----------------------------------------------------------------------------------------|-----------------------| +| 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 NGAP 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,
TXnRELOCOOverall expiry,
Successful handover,
Release due to NG-RAN generated reason,
Release due to 5GC generated reason,
Handover cancelled,
Partial handover,
Handover failure in target 5GC/NG-RAN node or target system,
Handover target not allowed,
TNGRELOCOOverall expiry,
TNGRELOCprep expiry,
Cell not available,
Unknown target ID,
No radio resources available in target cell,
Unknown local UE NGAP ID,
Inconsistent remote UE NGAP ID,
Handover desirable for radio reasons,
Time critical handover,
Resource optimisation handover,
Reduce load in serving cell,
User inactivity,
Radio connection with UE lost,
Radio resources not available,
Invalid QoS combination,
Failure in the radio interface procedure,
Interaction with other procedure,
Unknown PDU Session ID,
Unknown QoS Flow ID,
Multiple PDU Session ID Instances,
Multiple QoS Flow ID Instances,
Encryption and/or integrity protection algorithms not supported,
NG intra-system handover triggered,
NG inter-system handover triggered,
Xn handover triggered,
Not supported 5QI value,
UE context transfer,
IMS voice EPS fallback or RAT fallback triggered,
UP integrity protection not possible,
UP confidentiality protection not possible,
Slice(s) not supported,
UE in RRC_INACTIVE state not reachable,
Redirection,
Resources not available for the | | + +| | | | | | +|--------------------------------------|---|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| | | | slice(s),
UE maximum integrity protected data rate reason,
Release due to CN-detected mobility,
..., N26 interface not available,
Release due to pre-emption,
Multiple Location Reporting Reference ID Instances,
RSN not available for the UP,
NPN access denied,
CAG only access denied,
Insufficient UE Capabilities,
RedCap UE not supported,
Unknown MBS Session ID,
Indicated MBS Session Area Information not served by the gNB,
Inconsistent slice info for the session,
Misaligned association for the multicast and unicast sessions or flows) | | +| >Transport Layer | | | | | +| >>Transport Layer Cause | M | | ENUMERATED
(Transport resource unavailable,
Unspecified,
...) | | +| >NAS | | | | | +| >>NAS Cause | M | | ENUMERATED
(Normal release,
Authentication failure,
Deregister,
Unspecified,
..., UE not in PLMN serving area,
Mobile IAB not authorized
) | | +| >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,
...) | | +| >Miscellaneous | | | | | +| >>Miscellaneous Cause | M | | ENUMERATED
(Control processing overload,
Not enough user plane processing resources,
Hardware failure,
O&M intervention,
Unknown PLMN or SNPn,
Unspecified,
...) | | + +The meaning of the different cause values is described in the following tables. 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. | +| TXnRELOCOoverall expiry | The timer guarding the handover that takes place over Xn has abnormally expired. | +| Successful handover | Successful handover. | +| Release due to NG-RAN generated reason | Release is initiated due to NG-RAN generated reason. | +| Release due to 5GC generated reason | Release is initiated due to 5GC generated reason. | +| Handover cancelled | The reason for the action is cancellation of Handover. | +| Partial handover | Provides a reason for the handover cancellation. The HANDOVER COMMAND message from AMF contained PDU Session Resource to Release List IE or QoS flow to Release List and the source NG-RAN node estimated service continuity for the UE would be better by not proceeding with handover towards this particular target NG-RAN node. | +| Handover failure in target 5GC/ NG-RAN node or target system | The handover failed due to a failure in target 5GC/NG-RAN node or target system. | +| Handover target not allowed | Handover to the indicated target cell is not allowed for the UE in question. | +| TNG RELOCOoverall expiry | The reason for the action is expiry of timer TNG RELOCOoverall . | +| TNG RELOCprep expiry | Handover Preparation procedure is cancelled when timer TNG RELOCprep expires. | +| Cell not available | The concerned cell is not available. | +| Unknown target ID | Handover rejected because the target ID is not known to the AMF. | +| No radio resources available in target cell | Load on target cell is too high. | +| Unknown local UE NGAP ID | The action failed because the receiving node does not recognise the local UE NGAP ID. | +| Inconsistent remote UE NGAP ID | The action failed because the receiving node considers that the received remote UE NGAP ID is inconsistent. | +| Handover desirable for radio reasons | The reason for requesting handover is radio related. | +| Time critical handover | Handover is requested for time critical reason i.e., this cause value is reserved to represent all critical cases where the connection is likely to be dropped if handover is not performed. | +| Resource optimisation handover | The reason for requesting handover is to improve the load distribution with the neighbour cells. | +| Reduce load in serving cell | Load on serving cell needs to be reduced. When applied to handover preparation, it indicates the handover is triggered due to load balancing. | +| User inactivity | The action is requested due to inactivity on all user data radio bearers (i.e., DRBs and, if applicable, MRBs as per section 16.10.5.2 in TS 38.300 [8]), e.g., NG is requested to be released in order to optimise the radio resources. For L2 U2N Relay UE, this action is requested due to user inactivity on all PDU sessions of L2 U2N Relay UE and its served remote UE(s). | +| Radio connection with UE lost | The action is requested due to losing the radio connection to the UE. | +| Radio resources not available | No requested radio resources are available. | +| Invalid QoS combination | The action was failed because of invalid QoS combination. | +| Failure in the radio interface procedure | Radio interface procedure has failed. | +| Interaction with other procedure | The action is due to an ongoing interaction with another procedure. | +| Unknown PDU Session ID | The action failed because the PDU Session ID is unknown in the NG-RAN node. | +| Unknown QoS Flow ID | The action failed because the QoS Flow ID is unknown in the NG-RAN node. | +| Multiple PDU Session ID instances | The action failed because multiple instance of the same PDU Session had been provided to/from the NG-RAN node. | +| Multiple QoS Flow ID instances | The action failed because multiple instances of the same QoS flow had been provided to the NG-RAN node. | +| Encryption and/or integrity protection algorithms not supported | The NG-RAN node is unable to support any of the encryption and/or integrity protection algorithms supported by the UE. | +| NG intra-system handover triggered | The action is due to a NG intra-system handover that has been triggered. | + +| | | +|------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NG inter-system handover triggered | The action is due to a NG inter-system handover that has been triggered. | +| Xn handover triggered | The action is due to an Xn handover that has been triggered. | +| Not supported 5QI value | The QoS flow setup failed because the requested 5QI is not supported. | +| UE context transfer | The action is due to a UE resumes from the NG-RAN node different from the one which sent the UE into RRC_INACTIVE state. | +| IMS voice EPS fallback or RAT fallback triggered | The setup of QoS flow is failed due to EPS fallback or RAT fallback for IMS voice using handover or redirection. | +| UP integrity protection not possible | The PDU session cannot be accepted according to the required user plane integrity protection policy. | +| UP confidentiality protection not possible | The PDU session cannot be accepted according to the required user plane confidentiality protection policy. | +| Slice(s) not supported | Slice(s) not supported. | +| UE in RRC_INACTIVE state not reachable | The action is requested due to RAN paging failure. | +| Redirection | The release is requested due to inter-system redirection or intra-system redirection. | +| Resources not available for the slice(s) | The requested resources are not available for the slice(s). | +| UE maximum integrity protected data rate reason | The request is not accepted in order to comply with the maximum data rate for integrity protection supported by the UE. | +| Release due to CN-detected mobility | The context release is requested by the AMF because the UE is already served by another CN node (same or different system), or another NG interface of the same CN node. | +| N26 interface not available | The action failed due to a temporary failure of the N26 interface. | +| Release due to pre-emption | Release is initiated due to pre-emption. | +| Multiple Location Reporting Reference ID Instances | The action failed because multiple areas of interest are set with the same Location Reporting Reference ID. | +| RSN not available for the UP | The redundant user plane resources indicated by RSN are not available. | +| NPN access denied | Access was denied, or release is requested, for NPN reasons. | +| CAG only access denied | Access was denied because the cell is a non-CAG cell and UE is only allowed to access CAG cells. | +| Insufficient UE Capabilities | The procedure can't proceed due to insufficient UE capabilities. | +| RedCap UE not supported | The action failed because target NG-RAN node does not support RedCap UE. | +| Unknown MBS Session ID | The action failed because the MBS Session ID is unknown. | +| Indicated MBS Session Area Information not served by the gNB | The action failed because the none of the cells in indicated MBS Session Area Information served by the NG-RAN node. | +| Inconsistent slice info for the session | The action failed because the slice info of the multicast session is inconsistent. | +| Misaligned association for the multicast and unicast sessions or flows | The action failed because the Associated Unicast QoS Flow ID has already been used, or the Associated Unicast QoS Flow ID is not defined, or the Associated Unicast QoS Flow ID is not released, or multiple MBS QoS flows associated to the same unicast QoS flow, or same multicast session associated to multiple PDU Sessions. | + +| Transport Layer cause | Meaning | +|--------------------------------|----------------------------------------------------------------------------------------------------------| +| Transport resource unavailable | The required transport resources are not available. | +| Unspecified | Sent when none of the above cause values applies but still the cause is Transport Network Layer related. | + +| NAS cause | Meaning | +|-----------------------------|------------------------------------------------------------------------------------------------------------| +| Normal release | The release is normal. | +| Authentication failure | The action is due to authentication failure. | +| Deregister | The action is due to deregister. | +| Unspecified | Sent when none of the above other cause values applies but still the cause is NAS related. | +| UE not in PLMN serving area | The release is due to the UE not being within the serving area of its current PLMN (for NTN). | +| Mobile IAB not authorized | The release is due to the NG-RAN node having completed the operation for a non-authorized mobile IAB-node. | + +| 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 | Not 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. | +| Unknown PLMN or SNPN | The AMF does not identify any PLMN or SNPN provided by the NG-RAN node. | +| Unspecified failure | Sent when none of the above cause values applies and the cause is not related to any of the categories Radio Network Layer, Transport Network Layer, NAS or Protocol. | + +### 9.3.1.3 Criticality Diagnostics + +The *Criticality Diagnostics* IE is sent by the NG-RAN node or the AMF 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. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------------------|----------|--------------------|---------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| Procedure Code | O | | INTEGER (0..255) | 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) | Used only if the Criticality Diagnostics is part of Error Indication procedure. | +| Procedure Criticality | O | | ENUMERATED (reject, ignore, notify) | Used for reporting the Criticality of the Triggering message (Procedure). | +| Information Element Criticality Diagnostics | | 0.. | | | +| >IE Criticality | M | | ENUMERATED (reject, ignore, notify) | 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. Value is 256. | + +### 9.3.1.4 Bit Rate + +This IE indicates the number of bits delivered by NG-RAN in UL or to NG-RAN in DL or by UE in sidelink 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 aggregate 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.5 Global RAN Node ID + +This IE is used to globally identify an NG-RAN node (see TS 38.300 [8]). + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| CHOICE NG-RAN node | M | | | | - | | +| > gNB | | | | | | | +| >>Global gNB ID | M | | 9.3.1.6 | | - | | +| > ng-eNB | | | | | | | +| >>Global ng-eNB ID | M | | 9.3.1.8 | | - | | +| > N3IWF | | | | | | | +| >>Global N3IWF ID | M | | 9.3.1.57 | | - | | +| > TNGF | | | | | | | +| >>Global TNGF ID | M | | 9.3.1.161 | | YES | reject | +| > TWIF | | | | | | | +| >>Global TWIF ID | M | | 9.3.1.163 | | YES | reject | +| > W-AGF | | | | | | | +| >>Global W-AGF ID | M | | 9.3.1.162 | | YES | reject | + +### 9.3.1.6 Global gNB ID + +This IE is used to globally identify a gNB (see TS 38.300 [8]). + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------|----------|-------|---------------------------|--------------------------------------------------------------------------------------------------------------------------------| +| PLMN Identity | M | | 9.3.3.5 | | +| 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.7 NR CGI + +This IE is used to globally identify an NR cell (see TS 38.300 [8]). + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------| +| PLMN Identity | M | | 9.3.3.5 | | +| NR Cell Identity | M | | BIT STRING (SIZE(36)) | The leftmost bits of the NR Cell Identity IE correspond to the gNB ID (defined in subclause 9.3.1.6). | + +### 9.3.1.8 Global ng-eNB ID + +This IE is used to globally identify an ng-eNB (see TS 38.300 [8]). + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------| +| PLMN Identity | M | | 9.3.3.5 | | +| CHOICE ng-eNB ID | M | | | | +| > Macro ng-eNB ID | | | | | +| >>Macro ng-eNB ID | M | | BIT STRING (SIZE(20)) | Equal to the 20 leftmost bits of the E-UTRA Cell Identity IE contained in the E-UTRA CGI IE of each cell served by the ng-eNB. | +| > Short Macro ng-eNB ID | | | | | +| >>Short Macro ng-eNB ID | M | | BIT STRING (SIZE(18)) | Equal to the 18 leftmost bits of the E-UTRA Cell Identity IE contained in the E-UTRA CGI IE of each cell served by the ng-eNB. | +| > Long Macro ng-eNB ID | | | | | +| >>Long Macro ng-eNB ID | M | | BIT STRING (SIZE(21)) | Equal to the 21 leftmost bits of the E-UTRA Cell Identity IE contained in the E-UTRA CGI IE of each cell served by the ng-eNB. | + +### 9.3.1.9 E-UTRA CGI + +This IE is used to globally identify an E-UTRA cell (see TS 36.300 [17]). + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PLMN Identity | M | | 9.3.3.5 | | +| E-UTRA Cell Identity | M | | BIT STRING (SIZE(28)) | The leftmost bits of the E-UTRA Cell Identity IE correspond to the ng-eNB ID (defined in subclause 9.3.1.8) and to the eNB ID (defined in subclause 9.3.1.165). | + +### 9.3.1.10 GBR QoS Flow Information + +This IE indicates QoS parameters for a GBR QoS flow for downlink and uplink. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------|----------|-------|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Maximum Flow Bit Rate Downlink | M | | Bit Rate
9.3.1.4 | Maximum Bit Rate in DL. Details in TS 23.501 [9]. | - | | +| Maximum Flow Bit Rate Uplink | M | | Bit Rate
9.3.1.4 | Maximum Bit Rate in UL. Details in TS 23.501 [9]. | - | | +| Guaranteed Flow Bit Rate Downlink | M | | Bit Rate
9.3.1.4 | Guaranteed Bit Rate (provided there is data to deliver) in DL. Details in TS 23.501 [9]. | - | | +| Guaranteed Flow Bit Rate Uplink | M | | Bit Rate
9.3.1.4 | Guaranteed Bit Rate (provided there is data to deliver) in UL. Details in TS 23.501 [9]. | - | | +| Notification Control | O | | ENUMERATED
(notification requested, ...) | Details in TS 23.501 [9]. | - | | +| Maximum Packet Loss Rate Downlink | O | | Packet Loss Rate
9.3.1.79 | Indicates the maximum rate for lost packets that can be tolerated in the downlink direction. Details in TS 23.501 [9]. | - | | +| Maximum Packet Loss Rate Uplink | O | | Packet Loss Rate
9.3.1.79 | Indicates the maximum rate for lost packets that can be tolerated in the uplink direction. Details in TS 23.501 [9]. | - | | +| Alternative QoS Parameters Set List | O | | 9.3.1.151 | Indicates alternative sets of QoS parameters for the QoS flow. | YES | ignore | + +9.3.1.11 Void + +9.3.1.12 QoS Flow Level QoS Parameters + +This IE defines the QoS parameters to be applied to a QoS flow. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------|----------|-------|--------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| CHOICE QoS Characteristics | M | | | | - | | +| >Non-dynamic 5QI | | | | | | | +| >>Non Dynamic 5QI Descriptor | M | | 9.3.1.28 | | - | | +| >Dynamic 5QI | | | | | | | +| >>Dynamic 5QI Descriptor | M | | 9.3.1.18 | | - | | +| Allocation and Retention Priority | M | | 9.3.1.19 | | - | | +| GBR QoS Flow Information | O | | 9.3.1.10 | This IE shall be present for GBR QoS flows and is ignored otherwise. | - | | +| Reflective QoS Attribute | O | | ENUMERATED (subject to, ...) | Details in TS 23.501 [9]. This IE may be present in case of Non-GBR QoS flows and is ignored otherwise. | - | | +| Additional QoS Flow Information | O | | ENUMERATED (more likely, ...) | This IE indicates that traffic for this QoS flow is likely to appear more often than traffic for other flows established for the PDU session. This IE may be present in case of Non-GBR QoS flows and is ignored otherwise. | - | | +| 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 | +| QoS Monitoring Reporting Frequency | O | | INTEGER (1..1800, ...) | Indicates the reporting frequency for RAN part delay for QoS monitoring. Units: second | YES | ignore | +| PDU Set QoS Parameters | O | | 9.3.1.264 | | YES | ignore | + +### 9.3.1.13 QoS Flow List with Cause + +This IE contains a list of QoS flows with a cause value. It is used for example to indicate failed QoS flow(s) or QoS flow(s) to be released. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------|----------|----------------------|-----------------------|-----------------------| +| QoS Flow Item | | 1.. | | | +| >QoS Flow Identifier | M | | 9.3.1.51 | | +| >Cause | M | | 9.3.1.2 | | + +| Range bound | Explanation | +|-----------------|-----------------------------------------------------------------------| +| maxnoofQoSFlows | Maximum no. of QoS flows allowed within one PDU session. Value is 64. | + +### 9.3.1.14 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 | +|------------------------------------|----------|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| NG-RAN Trace ID | M | | OCTET STRING (SIZE(8)) | This IE is composed of the following:
Trace Reference defined in TS 32.422 [11] (leftmost 6 octets, with PLMN information encoded as in 9.3.3.5), and
Trace Recording Session Reference defined in TS 32.422 [11] (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 [11]. | - | | +| Trace Collection Entity IP Address | M | | Transport Layer Address 9.3.2.4 | For File based Reporting. Defined in TS 32.422 [11].
This IE is ignored if the Trace Collection Entity URI IE is present. | - | | +| MDT Configuration | O | | 9.3.1.167 | | YES | ignore | +| Trace Collection Entity URI | O | | URI 9.3.2.14 | For Streaming based Reporting. Defined in TS | YES | ignore | + +| | | | | | | | +|--|--|--|--|--------------|--|--| +| | | | | 32.422 [11]. | | | +|--|--|--|--|--------------|--|--| + +### 9.3.1.15 Core Network Assistance Information for RRC INACTIVE + +This IE provides assistance information for RRC\_INACTIVE configuration. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------|----------|----------------------------|-----------------------------|--------------------------------------------------------------------------------------------------------|-------------|----------------------| +| UE Identity Index Value | M | | 9.3.3.23 | | - | | +| UE Specific DRX | O | | Paging DRX
9.3.1.90 | | - | | +| Periodic Registration Update Timer | M | | 9.3.3.24 | | - | | +| MICO Mode Indication | O | | 9.3.1.23 | | - | | +| TAI List for RRC Inactive | | 1 | | | - | | +| >TAI List for RRC Inactive Item | | 1.. | | | - | | +| >>TAI | M | | 9.3.3.11 | | - | | +| Expected UE Behaviour | O | | 9.3.1.93 | | - | | +| E-UTRA Paging eDRX Information | O | | 9.3.1.154 | | YES | ignore | +| Extended UE Identity Index Value | O | | 9.3.3.52 | | YES | ignore | +| UE Radio Capability for Paging | O | | 9.3.1.68 | | YES | ignore | +| MICO All PLMN | O | | 9.3.1.194 | | YES | ignore | +| NR Paging eDRX Information | O | | 9.3.1.227 | | YES | ignore | +| Paging Cause Indication for Voice Service | O | | ENUMERATED (supported, ...) | This IE indicates whether the UE supports the feature of indication of paging cause for voice service. | YES | ignore | +| PEIPS Assistance Information | O | | 9.3.1.232 | | YES | ignore | +| Hashed UE Identity Index Value | O | | 9.3.3.62 | | YES | ignore | +| CN MT Communication Handling | O | | ENUMERATED (supported, ...) | This IE indicates the CN support of CN based MT communication handling. | YES | ignore | + +| Range bound | Explanation | +|-----------------------|----------------------------------------------------| +| maxnoofTAIforInactive | Maximum no. of TAIs for RRC Inactive. Value is 16. | + +### 9.3.1.16 User Location Information + +This IE is used to provide location information of the UE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------|----------|-------|------------------------------------|----------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| CHOICE User Location Information | M | | | | - | | +| >E-UTRA user location information | | | | | | | +| >>E-UTRA CGI | M | | 9.3.1.9 | | - | | +| >>TAI | M | | 9.3.3.11 | | - | | +| >>Age of Location | O | | Time Stamp
9.3.1.75 | Indicates the UTC time when the location information was generated. | - | | +| >>PSCell Information | O | | NG-RAN CGI
9.3.1.73 | | YES | ignore | +| >NR user location information | | | | | | | +| >>NR CGI | M | | 9.3.1.7 | | - | | +| >>TAI | M | | 9.3.3.11 | This IE is ignored if the NR NTN TAI Information IE is present. | - | | +| >>Age of Location | O | | Time Stamp
9.3.1.75 | Indicates the UTC time when the location information was generated. | - | | +| >>PSCell Information | O | | NG-RAN CGI
9.3.1.73 | | YES | ignore | +| >>NID | O | | 9.3.3.42 | | YES | reject | +| >>NR NTN TAI Information | O | | 9.3.3.53 | | YES | ignore | +| >>IAB-MT User Location Information | O | | 9.3.1.260 | Indicates the user location information of a mobile IAB-MT, which is co-located with the UE's serving mobile IAB-DU. | YES | ignore | +| >N3IWF user location information | | | | | | | +| >>IP Address | M | | Transport Layer Address
9.3.2.4 | UE's local IP address used to reach the N3IWF | - | | +| >>Port Number | O | | OCTET STRING
(SIZE(2)) | UDP or TCP source port number if NAT is detected. | - | | +| >>TAI | O | | 9.3.3.11 | | YES | ignore | +| >TNGF user location information | | | | | YES | ignore | +| >>TNAP ID | M | | OCTET STRING | TNAP Identifier used to identify the TNAP. Details in TS 29.571 [35]. | - | | +| >>IP Address | M | | Transport Layer Address
9.3.2.4 | UE's local IP address used to reach the TNGF. | - | | + +| | | | | | | | +|-----------------------------------|---|--|---------------------------------|----------------------------------------------------------------------------------------|-----|--------| +| >>Port Number | O | | OCTET STRING (SIZE(2)) | UDP or TCP source port number if NAT is detected. | - | | +| >>TAI | O | | 9.3.3.11 | | YES | ignore | +| >TWIF user location information | | | | | YES | ignore | +| >>TWAP ID | M | | OCTET STRING | TWAP Identifier used to identify the TWAP. Details in TS 29.571 [35]. | - | | +| >>IP Address | M | | Transport Layer Address 9.3.2.4 | Non-5G-Capable over WLAN device's local IP address used to reach the TWIF. | - | | +| >>Port Number | O | | OCTET STRING (SIZE(2)) | UDP or TCP source port number if NAT is detected. | - | | +| >>TAI | O | | 9.3.3.11 | | YES | ignore | +| >W-AGF user location information | | | | Indicates the location information via wireline access as specified in TS 23.316 [34]. | YES | ignore | +| >>W-AGF user location information | M | | 9.3.1.164 | | - | | + +### 9.3.1.17 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 | | 1.. | | | +| >S-NSSAI | M | | 9.3.1.24 | | + +| Range bound | Explanation | +|-------------------|--------------------------------------------------------------| +| maxnoofSliceItems | Maximum no. of signalled slice support items. Value is 1024. | + +### 9.3.1.18 Dynamic 5QI Descriptor + +This IE indicates the QoS Characteristics for a Non-standardised or not pre-configured 5QI for downlink and uplink. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------|-------------|-------|------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Priority Level | M | | 9.3.1.84 | Priority Level is specified in TS 23.501 [9]. | - | | +| Packet Delay Budget | M | | 9.3.1.80 | Packet Delay Budget is specified in TS 23.501 [9]. This IE is ignored if the Extended Packet Delay Budget IE is present. | - | | +| Packet Error Rate | M | | 9.3.1.81 | Packet Error Rate is specified in TS 23.501 [9]. | - | | +| 5QI | O | | INTEGER (0..255, ...) | Indicates the dynamically assigned 5QI as specified in TS 23.501 [9]. | - | | +| Delay Critical | C-ifGBRflow | | ENUMERATED (delay critical, non-delay critical, ...) | Indicates whether the GBR QoS flow is delay critical as specified in TS 23.501 [9]. | - | | +| Averaging Window | C-ifGBRflow | | 9.3.1.82 | Averaging Window is specified in TS 23.501 [9]. | - | | +| Maximum Data Burst Volume | O | | 9.3.1.83 | Maximum Data Burst Volume is specified in TS 23.501 [9]. 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.135 | Packet Delay Budget is specified in TS 23.501 [9]. | YES | ignore | +| CN Packet Delay Budget Downlink | O | | Extended Packet Delay Budget 9.3.1.135 | Core Network Packet Delay Budget is specified in TS 23.501 [9]. This IE may be present in case of GBR QoS flows and is ignored otherwise. | YES | ignore | +| CN Packet Delay Budget Uplink | O | | Extended Packet Delay Budget 9.3.1.135 | Core Network Packet Delay Budget is specified in TS 23.501 [9]. This IE may be present in case of GBR QoS flows and is ignored otherwise. | YES | ignore | + +| 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.19 Allocation and Retention Priority + +This IE specifies the relative importance of a QoS flow compared to other QoS flows for allocation and retention of NG-RAN resources. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|----------|-------|--------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Priority Level | M | | INTEGER (1..15) |

Desc.: This IE defines the relative importance of a resource request (see TS 23.501 [9]).

Usage: Values are ordered in decreasing order of priority, i.e., with 1 as the highest priority and 15 as the lowest priority.

| +| 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 [9]).

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 NG-RAN node.

| +| Pre-emption Vulnerability | M | | ENUMERATED (not pre-emptable, pre-emptable, ...) |

Desc.: This IE indicates the vulnerability of the QoS flow to pre-emption of other QoS flows (see TS 23.501 [9]).

Usage: The QoS flow shall not be pre-empted by other QoS flows or the QoS flow may be pre-empted by other QoS flows.

Note: The Pre-emption Vulnerability indicator applies for the entire duration of the QoS flow, unless modified and as such indicates whether the QoS flow is a target of the pre-emption procedures/processes of the NG-RAN node.

| + +### 9.3.1.20 Source to Target Transparent Container + +This IE is used to transparently pass radio related information from the handover source to the handover target through the core network; it is produced by the source RAN node and is transmitted to the target RAN node. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Source to Target Transparent Container | M | | OCTET STRING | This IE includes a transparent container from the source RAN node to the target RAN node. The octets of the OCTET STRING are encoded according to the specifications of the target system.
Note: In the current version of the specification, this IE may carry either the Source NG-RAN Node to Target NG-RAN Node Transparent Container IE or the Source eNB to Target eNB Transparent Container IE as defined in TS 36.413 [16] or the Source RNC to Target RNC Transparent Container IE as defined in TS 25.413 [28]. | + +### 9.3.1.21 Target to Source Transparent Container + +This IE is used to transparently pass radio related information from the handover target to the handover source through the core network; it is produced by the target RAN node and is transmitted to the source RAN node. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Target to Source Transparent Container | M | | OCTET STRING | This IE includes a transparent container from the target RAN node to the source RAN node. The octets of the OCTET STRING are encoded according to the specifications of the target system.
Note: In the current version of the specification, this IE may carry either the Target NG-RAN Node to Source NG-RAN Node Transparent Container IE or the Target eNB to Source eNB Transparent Container IE as defined in TS 36.413 [16], or the Target RNC to Source RNC Transparent Container IE as defined in TS 25.413 [28]. | + +### 9.3.1.22 Handover Type + +This IE indicates which kind of handover was triggered in the source side. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------| +| Handover Type | M | | ENUMERATED
(Intra5GS,
5GStoEPS,
EPSto5GS, ...,
5GStoUTRA) | Intra5GS: NG-RAN node to NG-RAN node
5GStoEPS: NG-RAN node to eNB
EPSto5GS: eNB to NG-RAN node
5GStoUTRA: NG-RAN node to UTRA | + +### 9.3.1.23 MICO Mode Indication + +This IE indicates that the UE is configured with MICO mode by the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------|----------|-------|---------------------------|-----------------------| +| MICO Mode Indication | M | | ENUMERATED
(true, ...) | | + +### 9.3.1.24 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.25 Target ID + +This IE identifies the target for the handover. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------|----------|-------|-----------------------------|---------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| CHOICE Target ID | M | | | | - | | +| >NG-RAN | | | | | | | +| >>Global RAN Node ID | M | | 9.3.1.5 | | - | | +| >>Selected TAI | M | | TAI
9.3.3.11 | | - | | +| >>Selected Target SNPN Identity | O | | NID
9.3.3.42 | This IE together with the PLMN Identity IE included in the Selected TAI IE indicates the target SNPN. | YES | reject | +| >E-UTRAN | | | | | | | +| >>Global eNB ID | M | | Global ng-eNB ID
9.3.1.8 | | - | | +| >>Selected EPS TAI | M | | EPS TAI
9.3.3.17 | | - | | +| >Target RNC-ID | | | | | YES | reject | +| >>LAI | M | | 9.3.3.30 | | - | | +| >>RNC-ID | M | | 9.3.1.123 | This IE is ignored if the Extended RNC-ID IE is included in the Target ID IE. | - | | +| >>Extended RNC-ID | O | | 9.3.1.124 | The Extended RNC-ID IE is used if the RNC identity has a value larger than 4095. | - | | +| >Target Home eNB ID | | | | | YES | reject | +| >>PLMN Identity | M | | 9.3.3.5 | | - | | +| >>Home eNB ID | M | | BIT STRING (SIZE(28)) | Equal to the E-UTRA Cell Identity IE contained in the E-UTRA CGI IE of the cell served by the eNB. | - | | +| >>Selected EPS TAI | M | | EPS TAI
9.3.3.17 | | - | | + +### 9.3.1.26 Emergency Fallback Indicator + +The IE indicates emergency service fallback. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------------|----------|-------|------------------------------------------------|-----------------------| +| Emergency Fallback Request Indicator | M | | ENUMERATED (emergency fallback requested, ...) | | +| Emergency Service Target CN | O | | ENUMERATED (5GC, EPC, ...) | | + +### 9.3.1.27 Security Indication + +This IE contains the user plane integrity protection indication and confidentiality protection indication which indicates the requirements on UP integrity protection and ciphering for corresponding PDU sessions, respectively. Additionally, this IE contains the maximum integrity protected data rate per UE for integrity protection for DRBs. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------------|---------------------------------------------|-------|---------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Integrity Protection Indication | M | | ENUMERATED (required, preferred, not needed, ...) | Indicates whether UP integrity protection shall apply, should apply or shall not apply for the concerned PDU session. | - | | +| Confidentiality Protection Indication | M | | ENUMERATED (required, preferred, not needed, ...) | Indicates whether UP ciphering shall apply, should apply or shall not apply for the concerned PDU session. | - | | +| Maximum Integrity Protected Data Rate Uplink | C-ifIntegrity ProtectionRequiredorPreferred | | Maximum Integrity Protected Data Rate 9.3.1.103 | Indicates the maximum aggregate rate for integrity protected DRBs supported by the UE in UL. If the Maximum Integrity Protected Data Rate Downlink IE is absent, this IE applies to both UL and DL. | - | | +| Maximum Integrity Protected Data Rate Downlink | O | | Maximum Integrity Protected Data Rate 9.3.1.103 | Indicates the maximum aggregate rate for integrity protected DRBs supported by the UE in the DL. | YES | ignore | + +| Condition | Explanation | +|------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| ifIntegrityProtectionRequiredorPreferred | This IE shall be present if the Integrity Protection Indication IE within the Security Indication IE is set to "required" or "preferred". | + +### 9.3.1.28 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, ...) | Indicates the standardized or pre-configured 5QI as specified in TS 23.501 [9]. | - | | +| Priority Level | O | | 9.3.1.84 | Priority Level is specified in TS 23.501 [9]. When included, it overrides standardized or pre-configured value. | - | | +| Averaging Window | O | | 9.3.1.82 | Averaging Window is specified in TS 23.501 [9]. When included, it overrides standardized or pre-configured value. | - | | +| Maximum Data Burst Volume | O | | 9.3.1.83 | Maximum Data Burst Volume is specified in TS 23.501 [9]. When included, it overrides standardized or pre-configured value. | - | | +| CN Packet Delay Budget Downlink | O | | Extended Packet Delay Budget
9.3.1.135 | Core Network Packet Delay Budget is specified in TS 23.501 [9]. This IE may be present in case of GBR QoS flows and is ignored otherwise. | YES | ignore | +| CN Packet Delay Budget Uplink | O | | Extended Packet Delay Budget
9.3.1.135 | Core Network Packet Delay Budget is specified in TS 23.501 [9]. This IE may be present in case of GBR QoS flows and is ignored otherwise. | YES | ignore | + +### 9.3.1.29 Source NG-RAN Node to Target NG-RAN Node Transparent Container + +This IE is produced by the source NG-RAN node and is transmitted to the target NG-RAN node. For inter-system handovers to 5G, the IE is transmitted from the external handover source to the target NG-RAN node. + +This IE is transparent to the 5GC. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------------|----------|-------------------------|---------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| RRC Container | M | | OCTET STRING | Includes the HandoverPreparationInformation message as defined in TS 38.331 [18] if the target is a gNB. Includes the HandoverPreparationInformation message as defined in TS 36.331 [21] if the target is an ng-eNB. | - | | +| PDU Session Resource Information List | | 0..1 | | For intra-system handovers in NG-RAN. | - | | +| > PDU Session Resource Information Item | | 1.. | | | - | | +| >>PDU Session ID | M | | 9.3.1.50 | | - | | +| >>QoS Flow Information List | | 1 | | | - | | +| >>>QoS Flow Information Item | | 1.. | | | - | | +| >>>>QoS Flow Identifier | M | | 9.3.1.51 | | - | | +| >>>>DL Forwarding | O | | 9.3.1.33 | | - | | +| >>>>UL Forwarding | O | | 9.3.1.118 | | YES | ignore | +| >>>>Source Transport Layer Address | O | | Transport Layer Address 9.3.2.4 | Identifies the TNL address used by the sending node for direct data forwarding towards the target NG-RAN node | YES | ignore | +| >>>>Source Node Transport Layer Address | O | | Transport Layer Address 9.3.2.4 | Identifies the TNL address used by the source SN node for direct data forwarding towards the target NG-RAN node | YES | ignore | +| >>DRBs to QoS Flows Mapping List | O | | 9.3.1.34 | | - | | +| E-RAB Information List | | 0..1 | | For inter-system handovers to 5G. | - | | +| > E-RAB Information Item | | 1.. | | | - | | +| >>E-RAB ID | M | | 9.3.2.3 | | - | | +| >>DL Forwarding | O | | 9.3.1.33 | | - | | +| >>Source Transport Layer Address | O | | Transport Layer Address 9.3.2.4 | Identifies the TNL address used by the sending node | YES | ignore | + +| | | | | | | | +|--|--|--|--|-----------------------------------------------------------|--|--| +| | | | | for direct data forwarding towards the target NG-RAN node | | | +|--|--|--|--|-----------------------------------------------------------|--|--| + +| | | | | | | | +|---------------------------------------------------------------|---|-------------------------------|---------------------------------|------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| >>Source Node Transport Layer Address | O | | Transport Layer Address 9.3.2.4 | Identifies the TNL address used by the source SN node for direct data forwarding towards the target NG-RAN node | YES | ignore | +| Target Cell ID | M | | NG-RAN CGI 9.3.1.73 | | - | | +| Index to RAT/Frequency Selection Priority | O | | 9.3.1.61 | | - | | +| UE History Information | M | | 9.3.1.95 | | - | | +| SgNB UE X2AP ID | O | | 9.3.1.127 | Allocated at the Source en-gNB | - | | +| UE History Information from UE | O | | 9.3.1.166 | | YES | ignore | +| Source Node ID | O | | 9.3.1.195 | Source SN ID | YES | ignore | +| UE Context Reference at Source | O | | RAN UE NGAP ID 9.3.3.2 | | YES | ignore | +| MBS Active Session Information Source to Target List | | 0..1 | | | YES | ignore | +| > MBS Active Session Information Source to Target Item | | 1.. | | | - | | +| >>MBS Session ID | M | | 9.3.1.206 | | - | | +| >>MBS Area Session ID | O | | 9.3.1.207 | If included, this IE indicates the MBS Area Session ID of the UE at the NG-RAN node from which the UE context is transferred | - | | +| >>MBS Service Area | O | | 9.3.1.208 | Included if available in source NG-RAN node. | - | | +| >>MBS QoS Flows To Be Setup List | M | | 9.3.1.236 | | - | | +| >> MBS Mapping and Data Forwarding Request List | | 0..1 | | | - | | +| >>> MBS Mapping and Data Forwarding Request Item | | 1.. | | | - | | +| >>>>MRB ID | M | | 9.3.1.218 | Contains the MRB ID value allocated at the source NG-RAN node. | - | | +| >>>> MBS QoS Flow List | | 1.. | | | - | | +| >>>>>MBS QoS Flow Identifier | M | | QoS Flow Identifier 9.3.1.51 | | - | | +| >>>>MRB Progress | O | | 9.3.1.219 | The SN | - | | + +| | | | | | | | +|-------------------------------------------------|---|--------------------------------|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| Information | | | | information of the last packet which has already been delivered for the MRB. | | | +| QMC Configuration Information | O | | 9.3.1.223 | Used for passing the QoE measurement information from the source NG-RAN node to the target NG-RAN node. | YES | ignore | +| NGAP IE Support Information Request List | | 0..1 | | | YES | ignore | +| >NGAP IE Support Information Request Item | | 1.. | | | - | | +| >>NGAP Protocol IE-Id | M | | 9.3.1.239 | | - | | +| Candidate Relay UE Information List | | 0..1 | | | YES | reject | +| >Candidate Relay UE Information Item | | 1.. | | | - | | +| >>Candidate Relay UE ID | M | | BIT STRING (SIZE(24)) | Includes the SL-SourceIdentity for the candidate relay UE as defined in TS 38.331 [18]. | - | | +| Time Based Handover Information | | 0..1 | | This IE only applies to NTN. | YES | ignore | +| >Handover Window Start | M | | INTEGER (0..549755813887) | Corresponds to information provided in t1-Threshold contained in the ReportConfigNR IE as defined in TS 38.331 [18] | - | | +| >Handover Window Duration | M | | INTEGER (1..6000) | Corresponds to information provided in the duration contained in the condEventT1 contained in the ReportConfigNR IE as defined in TS 38.331 [18] | - | | + +| Range bound | Explanation | +|--------------------------|---------------------------------------------------------------------------| +| maxnoofPDUSessions | Maximum no. of PDU sessions allowed towards one UE. Value is 256. | +| maxnoofQoSFlows | Maximum no. of QoS flows allowed within one PDU session. Value is 64. | +| maxnoofE-RABs | Maximum no. of E-RABs allowed towards one UE. Value is 256. | +| maxnoofMBSSessions | Maximum no. of MBS sessions allowed within one PDU session. Value is 32. | +| maxnoofMBSSessionsofUE | Maximum no. of MBS sessions allowed towards one UE. Value is 256. | +| maxnoofMBSQoSflows | Maximum no. of MBS QoS flows allowed within one MBS session. Value is 64. | +| maxnoofMRBs | Maximum no. of MRBs. Value is 32. | +| maxnoofIESupportInfo | Maximum no. of IE Support Information. Value is 32. | +| maxnoofCandidateRelayUEs | Maximum no. of Candidate Relay UEs. Value is 32. | + +### 9.3.1.30 Target NG-RAN Node to Source NG-RAN Node Transparent Container + +This IE is produced by the target NG-RAN node and is transmitted to the source NG-RAN node. For inter-system handovers to 5G, the IE is transmitted from the target NG-RAN node to the external relocation source. + +This IE is transparent to the 5GC. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------------------------------|----------|-------------------------------|----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| RRC Container | M | | OCTET STRING | Includes the HandoverCommand message as defined in TS 38.331 [18] if the target is a gNB. Includes the HandoverCommand message as defined in TS 36.331 [21] if the target is an ng-eNB. | - | | +| DAPS Response Information List | | 0..1 | | | YES | ignore | +| > DAPS Response Information Item | | 1.. | | | - | | +| >>DRB ID | M | | 9.3.1.153 | | - | | +| >>DAPS Response Information | M | | 9.3.1.189 | Indicates the response to a requested DAPS Handover | - | | +| Direct Forwarding Path Availability | O | | 9.3.1.164 | Indicates whether a direct forwarding path between the source SN and the target NG-RAN node is available for inter-system handover | YES | ignore | +| MBS Active Session Information Target to Source List | | 0..1 | | | YES | ignore | +| > MBS Active Session Information Target to Source Item | | 1.. | | | - | | +| >>MBS Session ID | M | | 9.3.1.206 | | - | | +| >> Data Forwarding Response MRB List | | 0..1 | | | - | | +| >>> Data Forwarding Response MRB Item | | 1.. | | | - | | +| >>>>MRB ID | M | | 9.3.1.218 | Contains the MRB ID value allocated at the source NG-RAN node. | - | | +| >>>>DL Forwarding UP TNL Information | M | | UP Transport Layer Information 9.3.2.2 | | - | | +| >>>>MRB Progress Information | O | | 9.3.1.219 | This IE includes the information of the oldest packet available at the target NG-RAN node for the MRB. | - | | + +| | | | | | | | +|-------------------------------------------|---|--|-----------|--|-----|--------| +| NGAP IE Support Information Response List | O | | 9.3.1.242 | | YES | ignore | +|-------------------------------------------|---|--|-----------|--|-----|--------| + +| Range bound | Explanation | +|------------------------|-------------------------------------------------------------------| +| maxnoofDRBs | Maximum no. of DRBs allowed towards one UE. Value is 32. | +| maxnoofMBSSessionsofUE | Maximum no. of MBS sessions allowed towards one UE. Value is 256. | +| maxnoofMRBs | Maximum no. of MRBs. Value is 32. | + +### 9.3.1.31 Allowed NSSAI + +This IE contains the allowed NSSAI. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------|----------|----------------------------|-----------------------|-----------------------| +| Allowed S-NSSAI List | | 1 | | | +| >Allowed S-NSSAI Item | | 1.. | | | +| >>S-NSSAI | M | | 9.3.1.24 | | + +| Range bound | Explanation | +|------------------------|---------------------------------------------| +| maxnoofAllowedS-NSSAIs | Maximum no. of allowed S-NSSAI. Value is 8. | + +### 9.3.1.32 Relative AMF Capacity + +This IE indicates the relative processing capacity of an AMF with respect to the other AMFs in the AMF Set in order to load-balance AMFs within an AMF Set defined in TS 23.501 [9]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------|----------|-------|-----------------------|-----------------------| +| Relative AMF Capacity | M | | INTEGER (0..255) | | + +### 9.3.1.33 DL Forwarding + +This IE indicates that the QoS flow or E-RAB is proposed for forwarding of downlink packets. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|------------------------------------------|-----------------------| +| DL Forwarding | M | | ENUMERATED (DL forwarding proposed, ...) | | + +### 9.3.1.34 DRBs to QoS Flows Mapping List + +This IE contains a list of DRBs containing information about the mapped QoS flows. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------|----------|------------------|-----------------------|---------------------------------------------------------|-------------|----------------------| +| DRBs to QoS Flows Mapping Item | | 1.. | | | - | | +| >DRB ID | M | | 9.3.1.53 | | - | | +| >Associated QoS Flow List | M | | 9.3.1.99 | Contains information of the QoS flows mapped to the DRB | - | | +| >DAPS Request Information | O | | 9.3.1.188 | | YES | ignore | + +| Range bound | Explanation | +|-------------|----------------------------------------------------------| +| maxnoofDRBs | Maximum no. of DRBs allowed towards one UE. Value is 32. | + +### 9.3.1.35 Message Identifier + +This IE identifies the warning message. It is set by the AMF and transferred to the UE by the NG-RAN node. + +| 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 NG-RAN node. | + +### 9.3.1.36 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.37 Warning Area List + +This IE indicates the areas where the warning message needs to be broadcast or cancelled. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------|----------|------------------------------|-----------------------|-----------------------| +| CHOICE Warning Area | M | | | | +| >E-UTRA Cell IDs | | | | | +| >>EUTRA CGI List for Warning | | 1.. | | | +| >>>E-UTRA CGI | M | | 9.3.1.9 | | +| >NR Cell IDs | | | | | +| >>NR CGI List for Warning | | 1.. | | | +| >>>NR CGI | M | | 9.3.1.7 | | +| >TAIs for Warning | | | | | +| >>TAI List for Warning | | 1.. | | | +| >>>TAI | M | | 9.3.3.11 | | +| >Emergency Area IDs | | | | | +| >>Emergency Area ID List | | 1.. | | | +| >>>Emergency Area ID | M | | 9.3.1.48 | | + +| Range bound | Explanation | +|-------------------------|-----------------------------------------------------------------------------------------| +| maxnoofCellIDforWarning | Maximum no. of Cell ID subject for warning message broadcast. Value is 65535. | +| maxnoofTAIforWarning | Maximum no. of TAI subject for warning message broadcast. Value is 65535. | +| maxnoofEmergencyAreaID | Maximum no. of Emergency Area ID subject for warning message broadcast. Value is 65535. | + +### 9.3.1.38 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.39 Warning Type + +This IE indicates types of the disaster. This IE also indicates that a Primary Notification is included. This IE can be used by the UE to differentiate the type of alert according to the type of disaster. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|------------------------|-----------------------| +| Warning Type | M | | OCTET STRING (SIZE(2)) | | + +### 9.3.1.40 Void + +### 9.3.1.41 Data Coding Scheme + +This IE identifies the alphabet or coding employed for the message characters and message handling at the UE (it is passed transparently from the 5GC to the UE). + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------|----------|-------|-----------------------|-----------------------| +| Data Coding Scheme | M | | BIT STRING (SIZE(8)) | | + +### 9.3.1.42 Warning Message Contents + +This IE contains user information, e.g., the message with warning contents, and will be broadcast over the radio interface. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------|----------|-------|------------------------------|-----------------------| +| Warning Message Contents | M | | OCTET STRING (SIZE(1..9600)) | | + +### 9.3.1.43 Broadcast Completed Area List + +This IE indicates the areas where either resources are available to perform the broadcast or where broadcast is performed successfully. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------------|----------|------------------------------|-----------------------|-----------------------| +| CHOICE Broadcast Completed Area | M | | | | +| >Cell ID Broadcast E-UTRA | | | | | +| >>Completed Cell List | | 1.. | | | +| >>>E-UTRA CGI | M | | 9.3.1.9 | | +| >TAI Broadcast E-UTRA | | | | | +| >>TAI Broadcast | | 1.. | | | +| >>>TAI | M | | 9.3.3.11 | | +| >>>Completed Cell in TAI List | | 1.. | | | +| >>>>E-UTRA CGI | M | | 9.3.1.9 | | +| >Emergency Area ID Broadcast E-UTRA | | | | | +| >>Emergency Area ID Broadcast | | 1.. | | | +| >>>Emergency Area ID | M | | 9.3.1.48 | | +| >>>Completed Cell in Emergency Area ID List | | 1.. | | | +| >>>>E-UTRA CGI | M | | 9.3.1.9 | | +| >Cell ID Broadcast NR | | | | | +| >>Completed Cell List | | 1.. | | | +| >>>NR-CGI | M | | 9.3.1.7 | | +| >TAI Broadcast NR | | | | | +| >>TAI Broadcast | | 1.. | | | +| >>>TAI | M | | 9.3.3.11 | | +| >>>Completed Cell in TAI List | | 1.. | | | +| >>>>NR-CGI | M | | 9.3.1.7 | | +| >Emergency Area ID Broadcast NR | | | | | +| >>Emergency Area ID Broadcast | | 1.. | | | +| >>>Emergency Area ID | M | | 9.3.1.48 | | +| >>>Completed Cell in Emergency Area ID List | | 1.. | | | +| >>>>NR-CGI | M | | 9.3.1.7 | | + +| Range bound | Explanation | +|-------------------------|-----------------------------------------------------------------------------------------| +| maxnoofCellIDforWarning | Maximum no. of Cell ID subject for warning message broadcast. Value is 65535. | +| maxnoofTAIforWarning | Maximum no. of TAI subject for warning message broadcast. Value is 65535. | +| maxnoofEmergencyAreaID | Maximum no. of Emergency Area ID subject for warning message broadcast. Value is 65535. | +| maxnoofCellinTAI | Maximum no. of Cell ID within a TAI. Value is 65535. | +| maxnoofCellinEAI | Maximum no. of Cell ID within an Emergency Area. Value is 65535. | + +### 9.3.1.44 Broadcast Cancelled Area List + +This IE indicates the areas where broadcast was stopped successfully. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------------|----------|------------------------------|-----------------------|-----------------------| +| CHOICE Broadcast Cancelled Area | M | | | | +| >Cell ID Cancelled E-UTRA | | | | | +| >>Cancelled Cell List | | 1.. | | | +| >>>E-UTRA CGI | M | | 9.3.1.9 | | +| >>>Number of Broadcasts | M | | 9.3.1.45 | | +| >TAI Cancelled E-UTRA | | | | | +| >>TAI Cancelled | | 1.. | | | +| >>>TAI | M | | 9.3.3.11 | | +| >>>Cancelled Cell in TAI List | | 1.. | | | +| >>>>E-UTRA CGI | M | | 9.3.1.9 | | +| >>>>Number of Broadcasts | M | | 9.3.1.45 | | +| >Emergency Area ID Cancelled E-UTRA | | | | | +| >>Emergency Area ID Cancelled | | 1.. | | | +| >>>Emergency Area ID | M | | 9.3.1.48 | | +| >>>Cancelled Cell in Emergency Area ID List | | 1.. | | | +| >>>>E-UTRA CGI | M | | 9.3.1.9 | | +| >>>>Number of Broadcasts | M | | 9.3.1.45 | | +| >Cell ID Cancelled NR | | | | | +| >>Cancelled Cell List | | 1.. | | | +| >>>NR-CGI | M | | 9.3.1.7 | | +| >>>Number of Broadcasts | M | | 9.3.1.45 | | +| >TAI Cancelled NR | | | | | +| >>TAI Cancelled | | 1.. | | | +| >>>TAI | M | | 9.3.3.11 | | +| >>>Cancelled Cell in TAI List | | 1.. | | | +| >>>>NR-CGI | M | | 9.3.1.7 | | +| >>>>Number of Broadcasts | M | | 9.3.1.45 | | +| >Emergency Area ID Cancelled NR | | | | | +| >>Emergency Area ID Cancelled | | 1.. | | | +| >>>Emergency Area ID | M | | 9.3.1.48 | | +| >>>Cancelled Cell in Emergency Area ID List | | 1.. | | | +| >>>>NR-CGI | M | | 9.3.1.7 | | +| >>>>Number of Broadcasts | M | | 9.3.1.45 | | + +| Range bound | Explanation | +|-------------------------|-----------------------------------------------------------------------------------------| +| maxnoofCellIDforWarning | Maximum no. of Cell ID subject for warning message broadcast. Value is 65535. | +| maxnoofTAIforWarning | Maximum no. of TAI subject for warning message broadcast. Value is 65535. | +| maxnoofEmergencyAreaID | Maximum no. of Emergency Area ID subject for warning message broadcast. Value is 65535. | +| maxnoofCellinTAI | Maximum no. of Cell ID within a TAI. Value is 65535. | +| maxnoofCellinEAI | Maximum no. of Cell ID within an Emergency Area. Value is 65535. | + +### 9.3.1.45 Number of Broadcasts + +This IE indicates the number of times that a particular message has been broadcast in a given warning area. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------| +| 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. | + +### 9.3.1.46 Concurrent Warning Message Indicator + +This IE indicates to the NG-RAN node that the received warning message is a new message to be scheduled for concurrent broadcast with any other ongoing broadcast of warning messages. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------------|----------|-------|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------| +| Concurrent Warning Message Indicator | M | | ENUMERATED
(true, ...) | This IE is used to identify a PWS type warning system which allows the broadcast of multiple concurrent warning messages over the radio. | + +### 9.3.1.47 Cancel-All Warning Messages Indicator + +This IE indicates to the NG-RAN node to stop all already ongoing broadcast of warning messages in the NG-RAN node or in an area. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------|----------|-------|---------------------------|-----------------------| +| Cancel-All Warning Messages Indicator | M | | ENUMERATED
(true, ...) | | + +### 9.3.1.48 Emergency Area ID + +This IE is used to indicate the area which has the emergency impact. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------|----------|-------|---------------------------|-----------------------------------------------------------------------------------------------| +| Emergency Area ID | M | | OCTET STRING
(SIZE(3)) | Emergency Area ID may consist of several cells. Emergency Area ID is defined by the operator. | + +### 9.3.1.49 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.50 PDU Session ID + +This IE identifies a PDU Session for a UE. The definition and use of the PDU Session ID is specified in TS 23.501 [9]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------|----------|-------|-----------------------|-----------------------| +| PDU Session ID | M | | INTEGER (0..255) | | + +### 9.3.1.51 QoS Flow Identifier + +This IE identifies a QoS flow within a PDU Session, or a MBS QoS flow within a MBS session. The definition and use of the QoS Flow Identifier is specified in TS 23.501 [9]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------|----------|-------|-----------------------|-----------------------| +| QoS Flow Identifier | M | | INTEGER (0..63, ...) | | + +### 9.3.1.52 PDU Session Type + +This IE indicates the PDU Session Type as specified in TS 23.501 [9]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------|----------|-------|-----------------------------------------------------------------------|-----------------------| +| PDU Session Type | M | | ENUMERATED
(lpv4, lpv6, lpv4v6,
ethernet,
unstructured, ...) | | + +### 9.3.1.53 DRB ID + +This IE contains the DRB ID. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-----------------------| +| DRB ID | M | | INTEGER (1..32, ...) | | + +### 9.3.1.54 Masked IMEISV + +This IE 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.55 New Security Context Indicator + +This IE indicates that the AMF has activated a new 5G NAS security context as described in TS 33.501 [13]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------|----------|-------|------------------------|----------------------------------------| +| New Security Context Indicator | M | | ENUMERATED (true, ...) | The NSCI as defined in TS 33.501 [13]. | + +### 9.3.1.56 Time to Wait + +This IE defines the minimum allowed waiting time. + +| 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.57 Global N3IWF ID + +This IE is used to globally identify an N3IWF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------|----------|-------|-----------------------|-----------------------| +| PLMN Identity | M | | 9.3.3.5 | | +| CHOICE N3IWF ID | M | | | | +| > N3IWF ID | | | | | +| >> N3IWF ID | M | | BIT STRING (SIZE(16)) | | + +### 9.3.1.58 UE Aggregate Maximum Bit Rate + +This IE is applicable for all Non-GBR QoS flows per UE which is defined for the downlink and the uplink direction and a subscription parameter provided by the AMF to the NG-RAN node. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------| +| UE Aggregate Maximum Bit Rate | | 1 | | Applicable for Non-GBR QoS flows. | +| >UE Aggregate Maximum Bit Rate Downlink | M | | Bit Rate
9.3.1.4 | This IE indicates the UE Aggregate Maximum Bit Rate as specified in TS 23.501 [9] in the downlink direction. | +| >UE Aggregate Maximum Bit Rate Uplink | M | | Bit Rate
9.3.1.4 | This IE indicates the UE Aggregate Maximum Bit Rate as specified in TS 23.501 [9] in the uplink direction. | + +### 9.3.1.59 Security Result + +This IE indicates whether the security policy indicated as "preferred" in the *Security Indication* IE is performed or not. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------------|----------|-------|-----------------------------------------------|----------------------------------------------------------------------------------------------| +| Integrity Protection Result | M | | ENUMERATED
(performed, not performed, ...) | Indicates whether UP integrity protection is performed or not for the concerned PDU session. | +| Confidentiality Protection Result | M | | ENUMERATED
(performed, not performed, ...) | Indicates whether UP ciphering is performed or not for the concerned PDU session. | + +### 9.3.1.60 User Plane Security Information + +This IE indicates user plane security information related to security policy. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------|----------|-------|-----------------------|-----------------------| +| Security Result | M | | 9.3.1.59 | | +| Security Indication | M | | 9.3.1.27 | | + +### 9.3.1.61 Index to RAT/Frequency Selection Priority + +This IE is used to define local configuration for RRM strategies such as camp priorities in Idle mode and control of inter-RAT/inter-frequency handover in Active mode (see TS 23.501 [9]). + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------------|----------|-------|-----------------------|-----------------------| +| Index to RAT/Frequency Selection Priority | M | | INTEGER (1..256, ...) | | + +### 9.3.1.62 Data Forwarding Accepted + +This IE indicates that the NG-RAN node accepts the proposed DL data forwarding for the QoS flow which is subject to data forwarding. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------|----------|-------|-----------------------------------------------|-----------------------| +| Data Forwarding Accepted | M | | ENUMERATED
(data forwarding accepted, ...) | | + +### 9.3.1.63 Data Forwarding Not Possible + +This IE indicates that the 5GC decided that the corresponding PDU session will not be subject to data forwarding. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------|----------|-------|---------------------------------------------------|-----------------------| +| Data Forwarding Not Possible | M | | ENUMERATED
(data forwarding not possible, ...) | | + +### 9.3.1.64 Direct Forwarding Path Availability + +This IE indicates whether a direct forwarding path is available. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------|----------|-------|--------------------------------------------|-----------------------| +| Direct Forwarding Path Availability | M | | ENUMERATED
(direct path available, ...) | | + +### 9.3.1.65 Location Reporting Request Type + +This IE indicates the type of location request to be handled by the NG-RAN node. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------------------------------|-----------------------------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------|----------------------| +| Event Type | M | | ENUMERATED (direct, change of serving cell, UE presence in the area of interest, stop change of serving cell, stop UE presence in the area of interest, cancel location reporting for the UE, ... change of serving cell and UE presence in the Area of Interest) | | - | | +| Report Area | M | | ENUMERATED (cell, ...) | | - | | +| Area of Interest List | | 0..1 | | | - | | +| >Area of Interest Item | | 1.. | | | - | | +| >>Area of Interest | M | | 9.3.1.66 | | - | | +| >>Location Reporting Reference ID | M | | 9.3.1.76 | | - | | +| Location Reporting Reference ID to be Cancelled | C- ifEventTypeisStop UEPresin Aol | | Location Reporting Reference ID 9.3.1.76 | | - | | +| Additional Location Information | O | | ENUMERATED (Include PSCell, ...) | | YES | ignore | +| Additional Cancelled Location Reporting Reference ID List | | 0..1 | | | YES | reject | +| >Additional Cancelled Location Reporting Reference ID Item | | 1.. | | | - | | +| >>Location Reporting Reference ID to be Cancelled | M | | Location Reporting Reference ID 9.3.1.76 | | - | | + +| Range bound | Explanation | +|-------------|------------------------------------------------| +| maxnoofAol | Maximum no. of areas of interest. Value is 64. | + +| Condition | Explanation | +|------------------------------|------------------------------------------------------------------------------------------------------------| +| ifEventTypeisStopUEPresinAol | This IE shall be present if the Event Type IE is set to "stop UE presence in the area of interest". | + +### 9.3.1.66 Area of Interest + +This IE indicates the area of interest. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------|----------|--------------------------|-----------------------|-----------------------| +| Area of Interest TAI List | | 0..1 | | | +| >Area of Interest TAI Item | | 1.. | | | +| >>TAI | M | | 9.3.3.11 | | +| Area of Interest Cell List | | 0..1 | | | +| >Area of Interest Cell Item | | 1.. | | | +| >>NG-RAN CGI | M | | 9.3.1.73 | | +| Area of Interest RAN Node List | | 0..1 | | | +| >Area of Interest RAN Node Item | | 1.. | | | +| >>Global RAN Node ID | M | | 9.3.1.5 | | + +| Range bound | Explanation | +|---------------------|--------------------------------------------------------------------| +| maxnoofTAIinAoI | Maximum no. of tracking areas in an area of interest. Value is 16. | +| maxnoofCellinAoI | Maximum no. of cells in an area of interest. Value is 256. | +| maxnoofRANNodeinAoI | Maximum no. of NG-RAN nodes in an area of interest. Value is 64. | + +### 9.3.1.67 UE Presence in Area of Interest List + +This IE indicates the UE presence in the area of interest. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------------|----------|-----------------|------------------------------------|-----------------------| +| UE Presence in Area of Interest Item | | 1.. | | | +| >Location Reporting Reference ID | M | | 9.3.1.76 | | +| >UE Presence | M | | ENUMERATED (in, out, unknown, ...) | | + +| Range bound | Explanation | +|-------------|------------------------------------------------| +| maxnoofAoI | Maximum no. of areas of interest. Value is 64. | + +### 9.3.1.68 UE Radio Capability for Paging + +This IE contains paging specific UE Radio Capability information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------| +| UE Radio Capability for Paging of NR | O | | OCTET STRING | Includes the UERadioPagingInformation message as defined in TS 38.331 [18]. | +| UE Radio Capability for Paging of E-UTRA | O | | OCTET STRING | Includes the UERadioPagingInformation message as defined in TS 36.331 [21]. | +| UE Radio Capability for Paging of NB-IoT | O | | OCTET STRING | Includes the UERadioPagingInformation-NB message as defined in TS 36.331 [21]. | + +### 9.3.1.69 Assistance Data for Paging + +This IE provides assistance information for paging optimisation. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Assistance Data for Recommended Cells | O | | 9.3.1.70 | | - | | +| Paging Attempt Information | O | | 9.3.1.72 | | - | | +| NPN Paging Assistance Information | O | | 9.3.1.183 | | YES | ignore | +| Paging Assistance Data for CE Capable UE | O | | 9.3.1.141 | | YES | ignore | + +### 9.3.1.70 Assistance Data for Recommended Cells + +This IE provides assistance information for paging in recommended cells. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------|----------|-------|-----------------------|-----------------------| +| Recommended Cells for Paging | M | | 9.3.1.71 | | + +### 9.3.1.71 Recommended Cells for Paging + +This IE contains the recommended cells for paging. + +This IE is transparent to the 5GC. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------|----------|------------------------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Recommended Cell List | | 1 | | | +| > Recommended Cell Item | | 1.. | | Includes visited and non-visited cells, where visited cells are listed in the order the UE visited them with the most recent cell being the first in the list. Non-visited cells are included immediately after the visited cell they are associated with. | +| >>NG-RAN CGI | M | | 9.3.1.73 | | +| >>Time Stayed in Cell | O | | INTEGER (0..4095) | This is included for visited cells and indicates the time a UE stayed in a cell in seconds. If the UE stays in a cell more than 4095 seconds, this IE is set to 4095. | + +| Range bound | Explanation | +|-------------------------|------------------------------------------------| +| maxnoofRecommendedCells | Maximum no. of recommended Cells. Value is 16. | + +### 9.3.1.72 Paging Attempt Information + +This IE includes information related to the paging count over NG. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------------|----------|-------|---------------------------------|----------------------------------------------------------------------------------------------------------------------| +| Paging Attempt Count | M | | INTEGER (1..16, ...) | Paging attempt count (see TS 38.300 [8]). | +| Intended Number of Paging Attempts | M | | INTEGER (1..16, ...) | Intended number of paging attempts (see TS 38.300 [8]). | +| Next Paging Area Scope | O | | ENUMERATED (same, changed, ...) | Indicates whether the paging area scope will change or not at next paging attempt. Usage specified in TS 38.300 [8]. | + +### 9.3.1.73 NG-RAN CGI + +This IE is used to globally identify a cell in NG-RAN. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------|----------|-------|-----------------------|-----------------------| +| CHOICE NG-RAN CGI | M | | | | +| >NR | | | | | +| >>NR CGI | M | | 9.3.1.7 | | +| >E-UTRA | | | | | +| >>E-UTRA CGI | M | | 9.3.1.9 | | + +### 9.3.1.74 UE Radio Capability + +This IE contains UE Radio Capability information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UE Radio Capability | M | | OCTET STRING | Includes either the UERadioAccessCapabilityInformation message as defined in TS 38.331 [18], or the UERadioAccessCapabilityInformation-NB message as defined in TS 36.331 [21]. | + +### 9.3.1.74a UE Radio Capability – E-UTRA Format + +This IE contains UE Radio Capability information to support Mode of operation A as specified in TS 23.501 [9]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------| +| UE Radio Capability – E-UTRA Format | M | | OCTET STRING | Includes the UERadioAccessCapabilityInformation message as defined in TS 36.331 [21]. | + +### 9.3.1.75 Time Stamp + +This IE contains UTC time information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|------------------------|-----------------------------------------------------------------------------------------------------------------------------------| +| Time Stamp | M | | OCTET STRING (SIZE(4)) | Encoded in the same format as the first four octets of the 64-bit timestamp format as defined in section 6 of IETF RFC 5905 [25]. | + +### 9.3.1.76 Location Reporting Reference ID + +This IE contains the Location Reporting Reference ID. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------|----------|-------|-----------------------|-----------------------| +| Location Reporting Reference ID | M | | INTEGER (1..64, ...) | | + +### 9.3.1.77 Data Forwarding Response DRB List + +This IE indicates data forwarding related information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------------------|----------|------------------|-------------------------------------------|-----------------------| +| Data Forwarding Response DRB Item | | 1.. | | | +| >DRB ID | M | | 9.3.1.53 | | +| >DL Forwarding UP TNL Information | O | | UP Transport Layer Information
9.3.2.2 | | +| >UL Forwarding UP TNL Information | O | | UP Transport Layer Information
9.3.2.2 | | + +| Range bound | Explanation | +|-------------|----------------------------------------------------------| +| maxnoofDRBs | Maximum no. of DRBs allowed towards one UE. Value is 32. | + +### 9.3.1.78 Paging Priority + +This element 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.79 Packet Loss Rate + +This IE indicates the Packet Loss Rate for a QoS flow. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------|----------|-------|------------------------|----------------------------------------------------------------------------------| +| Packet Loss Rate | M | | INTEGER (0..1000, ...) | Ratio of lost packets per number of packets sent, expressed in tenth of percent. | + +### 9.3.1.80 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.81 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 Scalar x 10-k where k is the Exponent . | +| Exponent | M | | INTEGER (0..9, ...) | | + +### 9.3.1.82 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 of the IE is 2000ms. | + +### 9.3.1.83 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.84 Priority Level + +This IE indicates the Priority Level for a QoS flow. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------| +| Priority Level | M | | INTEGER (1..127, ...) | Values ordered in decreasing order of priority, i.e. with 1 as the highest priority and 127 as the lowest priority. | + +### 9.3.1.85 Mobility Restriction List + +This IE defines roaming or access restrictions for subsequent mobility action for which the NG-RAN provides information about the target of the mobility action towards the UE, e.g., handover, or for SCG selection during dual connectivity operation or for assigning proper RNAs. NG-RAN behaviour upon receiving this IE is specified in TS 23.501 [9]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------|----------|----------------------------|-------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Serving PLMN | M | | PLMN Identity 9.3.3.5 | | - | | +| Equivalent PLMNs | | 0.. | | Allowed PLMNs in addition to Serving PLMN. This list corresponds to the list of "equivalent PLMNs" as defined in TS 24.501 [26]. This list is part of the roaming restriction information. Roaming restrictions apply to PLMNs other than the Serving PLMN and Equivalent PLMNs. | - | | +| >PLMN Identity | M | | 9.3.3.5 | | - | | +| RAT Restrictions | | 0.. | | This IE contains RAT restriction related information as specified in TS 23.501 [9]. | - | | +| >PLMN Identity | M | | 9.3.3.5 | | - | | +| >RAT Restriction Information | M | | BIT STRING { e-UTRA (0), nR (1), nR-unlicensed (2), nR-LEO (3), nR-MEO (4), nR-GEO (5), nR-OTHERSAT (6)} (SIZE(8, ...)) | Each position in the bitmap represents a RAT. If a bit is set to "1", the respective RAT is restricted for the UE. If a bit is set to "0", the respective RAT is not restricted for the UE. Bit 7 reserved for future use. | - | | +| >Extended RAT Restriction Information | O | | 9.3.1.126 | If this IE is included, the RAT Restriction Information IE is ignored. | YES | ignore | +| Forbidden Area Information | | 0.. | | This IE contains Forbidden Area information as specified in TS 23.501 [9]. | - | | +| >PLMN Identity | M | | 9.3.3.5 | | - | | +| >Forbidden TACs | | 1.. | | | - | | +| >>TAC | M | | 9.3.3.10 | The TAC of the forbidden TAI. | - | | +| Service Area | | 0..Information | | ofEPLMNsPlusOne > | | Service Area Restriction information as specified in TS 23.501 [9]. | | | +| >PLMN Identity | M | | 9.3.3.5 | | - | | +| >Allowed TACs | | 0..<maxno ofAllowed Areas> | | | - | | +| >>TAC | M | | 9.3.3.10 | The TAC of the allowed TAI. | - | | +| >Not Allowed TACs | | 0..<maxno ofAllowed Areas> | | | - | | +| >>TAC | M | | 9.3.3.10 | The TAC of the not-allowed TAI. | - | | +| Last E-UTRAN PLMN Identity | O | | PLMN Identity 9.3.3.5 | Indicates the E-UTRAN PLMN ID from where the UE formerly handed over to 5GS and which is preferred in case of subsequent mobility to EPS. | YES | ignore | +| Core Network Type Restriction for Serving PLMN | O | | ENUMERATED (EPCForbidden, ...) | Indicates whether the UE is restricted to connect to EPC for the Serving PLMN as specified in TS 23.501 [9]. | YES | ignore | +| Core Network Type Restriction for Equivalent PLMNs | | 0..<maxno ofEPLMNs> | | | YES | ignore | +| >PLMN Identity | M | | 9.3.3.5 | Includes any of the Equivalent PLMNs listed in the Mobility Restriction List IE for which CN Type restriction applies as specified in TS 23.501 [9]. | - | | +| >Core Network Type Restriction | M | | ENUMERATED (EPCForbidden, 5GCForbidden, ...) | Indicates whether the UE is restricted to connect to EPC or to 5GC for this PLMN. | - | | +| NPN Mobility Information | O | | 9.3.1.184 | | YES | reject | + +| Range bound | Explanation | +|----------------------|--------------------------------------------------------------------| +| maxnoofEPLMNs | Maximum no. of equivalent PLMNs. Value is 15. | +| maxnoofEPLMNsPlusOne | Maximum no. of allowed PLMNs. Value is 16. | +| maxnoofForbTACs | Maximum no. of forbidden Tracking Area Codes. Value is 4096. | +| maxnoofAllowedAreas | Maximum no. of allowed or not allowed Tracking Areas. Value is 16. | + +### 9.3.1.86 UE Security Capabilities + +This IE defines the supported algorithms for encryption and integrity protection in the UE. The Security Capabilities received from NAS signaling shall not be modified or truncated when forwarded to NG-RAN nodes and the NG-RAN nodes store and send the complete bitmaps without modification or truncation as specified in TS 38.300 [8]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------------|----------|-------|----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NR Encryption Algorithms | M | | BIT STRING (SIZE(16, ...)) | Each position in the bitmap represents an encryption algorithm:
"all bits equal to 0" – UE supports no other algorithm than NEA0,
"first bit" – 128-NEA1,
"second bit" – 128-NEA2,
"third bit" – 128-NEA3,
"fourth to seventh bit" are mapped from bit 4 to bit 1 of octet 3 in the UE Security Capability IE defined in TS 24.501 [26],
other bits reserved for future use.
Value '1' indicates support and value '0' indicates no support of the algorithm.
Algorithms are defined in TS 33.501 [13]. | +| NR Integrity Protection Algorithms | M | | BIT STRING (SIZE(16, ...)) | Each position in the bitmap represents an integrity protection algorithm:
"all bits equal to 0" – UE supports no other algorithm than NIA0,
"first bit" – 128-NIA1,
"second bit" – 128-NIA2,
"third bit" – 128-NIA3,
"fourth to seventh bit" are mapped from bit 4 to bit 1 of octet 4 in the UE Security Capability IE defined in TS 24.501 [26],
other bits reserved for future use.
Value '1' indicates support and value '0' indicates no support of the algorithm.
Algorithms are defined in TS 33.501 [13]. | +| E-UTRA Encryption Algorithms | M | | BIT STRING (SIZE(16, ...)) | Each position in the bitmap represents an encryption algorithm:
"all bits equal to 0" – UE supports no other algorithm than EEA0,
"first bit" – 128-EEA1,
"second bit" – 128-EEA2,
"third bit" – 128-EEA3,
"fourth to seventh bit" are mapped from bit 4 to bit 1 of octet 5 in the UE Security Capability IE defined in TS 24.501 [26],
other bits reserved for future use.
Value '1' indicates support and value '0' indicates no support of | + +| | | | | | +|----------------------------------------|---|--|----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | | the algorithm.
Algorithms are defined in TS 33.401 [27]. | +| E-UTRA Integrity Protection Algorithms | M | | BIT STRING (SIZE(16, ...)) | Each position in the bitmap represents an encryption algorithm:
"all bits equal to 0" – UE supports no other algorithm than EIA0,
"first bit" – 128-EIA1,
"second bit" – 128-EIA2,
"third bit" – 128-EIA3,
"fourth to seventh bit" are mapped from bit 4 to bit 1 of octet 6 in the UE Security Capability IE defined in TS 24.501 [26],
other bits reserved for future use.
Value '1' indicates support and value '0' indicates no support of the algorithm.
Algorithms are defined in TS 33.401 [27]. | + +### 9.3.1.87 Security Key + +This IE is used to apply security in the NG-RAN for different scenarios as defined in TS 33.501 [13]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|------------------------|---------------------------------------------------------------------------| +| Security Key | M | | BIT STRING (SIZE(256)) | Key material for NG-RAN node or Next Hop Key as defined in TS 33.501 [13] | + +### 9.3.1.88 Security Context + +This IE provides security related parameters to the NG-RAN node which are used to derive security keys for user plane traffic and RRC signalling messages and for security parameter generation for subsequent mobility, see TS 33.501 [13]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------| +| Next Hop Chaining Count | M | | INTEGER (0..7) | Next Hop Chaining Counter (NCC) defined in TS 33.501 [13]. | +| Next-Hop NH | M | | Security Key 9.3.1.87 | The NH together with the NCC is used to derive the security configuration as defined in TS 33.501 [13]. | + +### 9.3.1.89 IMS Voice Support Indicator + +This IE is set by the NG-RAN node to indicate whether the UE radio capabilities are compatible with the network configuration for IMS voice. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------|----------|-------|-----------------------------------------------|-----------------------| +| IMS Voice Support Indicator | M | | ENUMERATED
(Supported, Not Supported, ...) | | + +### 9.3.1.90 Paging DRX + +This IE indicates the Paging DRX as defined in TS 38.304 [12] and TS 36.304 [29]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|------------------------------------|-------------------------------| +| Paging DRX | M | | ENUMERATED (32, 64, 128, 256, ...) | Unit: [number of radioframes] | + +### 9.3.1.91 RRC Inactive Transition Report Request + +This IE is used to request the NG-RAN node to report or stop reporting to the 5GC when the UE enters or leaves RRC\_INACTIVE state. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------|----------|-------|-----------------------------------------------------------------------------------------------------------|-----------------------| +| RRC Inactive Transition Report Request | M | | ENUMERATED
(Subsequent state transition report, Single RRC connected state report, Cancel report, ...) | | + +### 9.3.1.92 RRC State + +This IE indicates the RRC state of the UE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|------------------------------------------|--------------------------------------------| +| RRC State | M | | ENUMERATED
(Inactive, Connected, ...) | Indicates the current RRC state of the UE. | + +### 9.3.1.93 Expected UE Behaviour + +This IE indicates the behaviour of a UE with predictable activity and/or mobility behaviour, to assist the NG-RAN node in e.g. determining the optimum RRC connection time or helping with the RRC\_INACTIVE state transition and RNA configuration (e.g. size and shape of the RNA). + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------------------------|----------|-------------------------------------|-------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Expected UE Activity Behaviour | O | | 9.3.1.94 | | +| Expected HO Interval | O | | ENUMERATED (sec15, sec30, sec60, sec90, sec120, sec180, long-time, ...) | Indicates the expected time interval between inter NG-RAN node handovers.
If "long-time" is included, the interval between inter NG-RAN node handovers is expected to be longer than 180 seconds. | +| Expected UE Mobility | O | | ENUMERATED (stationary, mobile, ...) | Indicates whether the UE is expected to be stationary or mobile. | +| Expected UE Moving Trajectory | | 0..1 | | Indicates the UE's expected geographical movement. | +| >Expected UE Moving Trajectory Item | | 1.. | | Includes list of visited and non-visited cells, where visited cells are listed in the order the UE visited them with the most recent cell being the first in the list. Non-visited cells are included immediately after the visited cell they are associated with. | +| >>NG-RAN CGI | M | | 9.3.1.73 | | +| >>Time Stayed in Cell | O | | INTEGER (0..4095) | Included for visited cells and indicates the time a UE stayed in a cell in seconds. If the UE stays in a cell more than 4095 seconds, this IE is set to 4095. | + +| Range bound | Explanation | +|--------------------------------|------------------------------------------------------------| +| maxnoofCellsUEMovingTrajectory | Maximum no. of cells of UE moving trajectory. Value is 16. | + +### 9.3.1.94 Expected UE Activity Behaviour + +This IE indicates information about the expected "UE activity behaviour" of the UE or the PDU session as defined in TS 23.501 [9]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------------|----------|-------|--------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Expected Activity Period | O | | INTEGER (1..30 40 50 60 80 100 120 150 180 181, ...) | If set to "181" the expected activity time is longer than 180 seconds.
The remaining values indicate the expected activity time in [seconds]. | +| Expected Idle Period | O | | INTEGER (1..30 40 50 60 80 100 120 150 180 181, ...) | If set to "181" the expected idle time is longer than 180 seconds.
The remaining values indicate the expected idle time in [seconds]. | +| Source of UE Activity Behaviour Information | O | | ENUMERATED (subscription information, statistics, ...) | If "subscription information" is indicated, the information contained in the Expected Activity Period IE and the Expected Idle Period IE, if present, is derived from subscription information.
If "statistics" is indicated, the information contained in the Expected Activity Period IE and the Expected Idle Period IE, if present, is derived from statistical information. | + +### 9.3.1.95 UE History Information + +This IE contains information about cells that a UE has been served by in active state prior to the target cell. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------|----------|----------------------------------|-----------------------|-----------------------------------------------------------| +| Last Visited Cell Item | | 1.. | | Most recent information is added to the top of this list. | +| >Last Visited Cell Information | M | | 9.3.1.96 | | + +| Range bound | Explanation | +|-----------------------------|------------------------------------------------------------------| +| maxnoofCellsInUEHistoryInfo | Maximum no. of cells in the UE history information. Value is 16. | + +### 9.3.1.96 Last Visited Cell Information + +This IE may contain cell specific information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------------|----------|-------|-----------------------|----------------------------| +| CHOICE Last Visited Cell Information | M | | | | +| >NG-RAN Cell | | | | | +| >>Last Visited NG-RAN Cell Information | M | | 9.3.1.97 | | +| >E-UTRAN Cell | | | | | +| >>Last Visited E-UTRAN Cell Information | M | | OCTET STRING | Defined in TS 36.413 [16]. | +| >UTRAN Cell | | | | | +| >>Last Visited UTRAN Cell Information | M | | OCTET STRING | Defined in TS 25.413 [28]. | +| >GERAN Cell | | | | | +| >>Last Visited GERAN Cell Information | M | | OCTET STRING | Defined in TS 36.413 [16]. | + +### 9.3.1.97 Last Visited NG-RAN Cell Information + +This IE contains information about a cell. In case of NR cell, this IE contains information about a set of NR cells with the same NR ARFCN for reference point A, and the *Global Cell ID* IE identifies one of the NR cells in the set. The information is to be used for RRM purposes. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------------|----------|--------------------------------------------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Global Cell ID | M | | NG-RAN CGI 9.3.1.73 | | - | | +| Cell Type | M | | 9.3.1.98 | | - | | +| Time UE Stayed in Cell | M | | INTEGER (0..4095) | The duration of time the UE stayed in the cell, or set of NR cells with the same NR ARFCN for reference point A, in seconds. If the duration is more than 4095s, this IE is set to 4095. | - | | +| Time UE Stayed in Cell Enhanced Granularity | O | | INTEGER (0..40950) | The duration of time the UE stayed in the cell, or set of NR cells with the same NR ARFCN for reference point A, in 1/10 seconds. If the duration is more than 4095s, this IE is set to 40950. | - | | +| HO Cause Value | O | | Cause 9.3.1.2 | The cause for the handover. | - | | +| Last Visited PSCell List | | 0.. | | List of cells configured as PSCells. Most recent PSCell related information is added to the top of the list. | YES | ignore | +| >Last Visited PSCell Information | M | | 9.3.1.235 | The PSCell related information. | - | | + +| Range bound | Explanation | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------| +| maxnoofPSCellsPerPrimaryCellinUEHistoryInfo | Maximum number of last visited PSCell information records that can be reported in the IE. Value is 8. | + +### 9.3.1.98 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.99 Associated QoS Flow List + +This IE indicates the list of QoS flows associated with e.g. a DRB or UP TNL endpoint. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------|----------|----------------------|------------------------------------------------|-----------------------------------------------------------------|-------------|----------------------| +| Associated QoS Flow Item | | 1.. | | | - | | +| >QoS Flow Identifier | M | | 9.3.1.51 | | - | | +| >QoS Flow Mapping Indication | O | | ENUMERATED (ul, dl, ...) | | - | | +| >Current QoS Parameters Set Index | O | | Alternative QoS Parameters Set Index 9.3.1.152 | Index to the currently fulfilled alternative QoS parameters set | YES | ignore | + +| Range bound | Explanation | +|-----------------|-----------------------------------------------------------------------| +| maxnoofQoSFlows | Maximum no. of QoS flows allowed within one PDU session. Value is 64. | + +### 9.3.1.100 Information on Recommended Cells and RAN Nodes for Paging + +This IE provides information on recommended cells and NG-RAN nodes for paging. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------|----------|-------|-----------------------|-----------------------| +| Recommended Cells for Paging | M | | 9.3.1.71 | | +| Recommended RAN Nodes for Paging | M | | 9.3.1.101 | | + +### 9.3.1.101 Recommended RAN Nodes for Paging + +This IE contains recommended NG-RAN nodes for paging. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------------|----------|---------------------------------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Recommended RAN Node List | | 1 | | | +| > Recommended RAN Node Item | | 1.. | | Includes visited and non-visited NG-RAN nodes, where visited NG-RAN nodes are listed in the order the UE visited them with the most recent NG-RAN node being the first in the list. Non-visited NG-RAN nodes are included after the visited NG-RAN node they are associated with. | +| >>CHOICE AMF Paging Target | | | | The AMF paging target is either an NG-RAN node identity or a TAI as specified in TS 38.300 [8]. | +| >>>RAN Node | | | | | +| >>>>Global RAN Node ID | M | | 9.3.1.5 | | +| >>>TAI | | | | | +| >>>>TAI | M | | 9.3.3.11 | | + +| Range bound | Explanation | +|----------------------------|-------------------------------------------------------| +| maxnoofRedommendedRANNodes | Maximum no. of recommended NG-RAN nodes. Value is 16. | + +### 9.3.1.102 PDU Session Aggregate Maximum Bit Rate + +This IE is applicable for all Non-GBR QoS flows per PDU session which is defined for the downlink and the uplink direction and is provided by the SMF to the NG-RAN node. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------| +| PDU Session Aggregate Maximum Bit Rate | | 1 | | Applicable for Non-GBR QoS flows. | +| >PDU Session Aggregate Maximum Bit Rate Downlink | M | | Bit Rate 9.3.1.4 | Indicates the PDU session Aggregate Maximum Bit Rate as specified in TS 23.501 [9] in the downlink direction. | +| >PDU Session Aggregate Maximum Bit Rate Uplink | M | | Bit Rate 9.3.1.4 | Indicates the PDU session Aggregate Maximum Bit Rate as specified in TS 23.501 [9] in the uplink direction. | + +### 9.3.1.103 Maximum Integrity Protected Data Rate + +This IE indicates the maximum aggregate data rate for integrity protected DRBs for a UE as defined in TS 38.300 [8]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------|----------|-------|---------------------------------------|----------------------------------------------------------------------------------------------------------------| +| Maximum Integrity Protected Data Rate | M | | ENUMERATED (64kbps, max UE rate, ...) | Defines the upper bound of the aggregate data rate of user plane integrity protected data for either UL or DL. | + +### 9.3.1.104 Overload Response + +This IE indicates the required behaviour of the NG-RAN node in an overload situation. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------|----------|-------|-----------------------|-----------------------| +| CHOICE Overload Response | M | | | | +| > Overload Action | | | | | +| >> Overload Action | M | | 9.3.1.105 | | + +### 9.3.1.105 Overload Action + +This IE indicates which signalling traffic is subject to rejection by the NG-RAN node in an AMF overload situation as defined in TS 23.501 [9]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------|----------|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| Overload 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.106 Traffic Load Reduction Indication + +This IE indicates the percentage of the type of traffic relative to the instantaneous incoming rate at the NG-RAN node, as indicated in the *Overload Action* IE, to be rejected. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------------|----------|-------|-----------------------|-----------------------| +| Traffic Load Reduction Indication | M | | INTEGER (1..99) | | + +### 9.3.1.107 Slice Overload List + +This IE indicates the list of overloaded slices. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------|----------|------------------------|-----------------------|-----------------------| +| Slice Overload Item | | 1.. | | | +| >S-NSSAI | M | | 9.3.1.24 | | + +| Range bound | Explanation | +|-------------------|--------------------------------------------------------------| +| maxnoofSliceItems | Maximum no. of signalled slice support items. Value is 1024. | + +### 9.3.1.108 RAN Status Transfer Transparent Container + +This IE is produced by the source NG-RAN node and is transmitted to the target NG-RAN node. It is used for intra 5GC NG handover. + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------------|----------|-------------------|------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| DRBs Subject to Status Transfer List | | 1 | | | - | | +| > DRBs Subject to Status Transfer Item | | 1.. | | | - | | +| >>DRB ID | M | | 9.3.1.153 | | - | | +| >>CHOICE UL DRB Status | M | | | | - | | +| >>>12 bits | | | | | | | +| >>>>UL COUNT Value | M | | COUNT Value for PDCP SN Length 12
9.3.1.109 | PDCP-SN and HFN of the first missing UL PDCP SDU in case of 12 bit long PDCP-SN. | - | | +| >>>>Receive Status of UL PDCP SDUs | O | | BIT STRING (SIZE(1..2048)) |

The IE is used in case of 12 bit long PDCP-SN.

The first bit indicates the status of the SDU after the First Missing UL PDCP SDU.

The N^{\text{th}} bit indicates the status of the UL PDCP SDU in position (N + \text{First Missing SDU Number}) modulo (1 + \text{the maximum value of the PDCP-SN}).

0: PDCP SDU has not been received.
1: PDCP SDU has been received correctly.

| - | | +| >>>18 bits | | | | | | | +| >>>>UL COUNT Value | M | | COUNT Value for PDCP SN Length 18
9.3.1.110 | PDCP-SN and HFN of the first missing UL PDCP SDU in case of 18 bit long PDCP-SN. | - | | +| >>>>Receive Status of UL PDCP SDUs | O | | BIT STRING (SIZE(1..131072 )) |

The IE is used in case of 18 bit long PDCP-SN.

The first bit indicates the status of the SDU after the First Missing UL PDCP SDU.

The N^{\text{th}} bit indicates the status of the UL PDCP SDU in position (N + \text{First Missing SDU Number}) modulo (1 + \text{the maximum value of the PDCP-SN}).

| - | | + +| | | | | | | | +|---------------------------------------------------------|---|--|------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| | | | | modulo (1 + the maximum value of the PDCP-SN).

0: PDCP SDU has not been received.
1: PDCP SDU has been received correctly. | | | +| >>CHOICE DL DRB Status | M | | | | - | | +| >>>12 bits | | | | | | | +| >>>>DL COUNT Value | M | | COUNT Value for PDCP SN Length 12
9.3.1.109 | PDCP-SN and HFN that the target NG-RAN node should assign for the next DL PDCP SDU not having an SN yet in case of 12 bit long PDCP-SN. | - | | +| >>>18 bits | | | | | | | +| >>>>DL COUNT Value | M | | COUNT Value for PDCP SN Length 18
9.3.1.110 | PDCP-SN and HFN that the target NG-RAN node should assign for the next DL PDCP SDU not having an SN yet in case of 18 bit long PDCP-SN. | - | | +| >>Old Associated QoS Flow List - UL End Marker Expected | O | | Associated QoS Flow List
9.3.1.99 | Indicates that the source NG-RAN node has initiated QoS flow re-mapping and has not yet received SDAP end markers, as described in TS 38.300 [8]. | YES | ignore | + +| Range bound | Explanation | +|-------------|----------------------------------------------------------| +| maxnoofDRBs | Maximum no. of DRBs allowed towards one UE. Value is 32. | + +### 9.3.1.109 COUNT Value for PDCP SN Length 12 + +This IE contains a PDCP sequence number and a hyper frame number in case of 12 bit long PDCP-SN. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|----------|-------|-----------------------|-----------------------| +| PDCP SN Length 12 | M | | INTEGER (0..4095) | | +| HFN for PDCP SN Length 12 | M | | INTEGER (0..1048575) | | + +### 9.3.1.110 COUNT Value for PDCP SN Length 18 + +This IE contains a PDCP sequence number and a hyper frame number in case of 18 bit long PDCP-SN. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|----------|-------|-----------------------|-----------------------| +| PDCP SN Length 18 | M | | INTEGER (0..262143) | | +| HFN for PDCP SN Length 18 | M | | INTEGER (0..16383) | | + +### 9.3.1.111 RRC Establishment Cause + +This IE indicates the reason for RRC Connection Establishment as received from the UE in the *EstablishmentCause* IE defined in TS 38.331 [18] or the *EstablishmentCause-5GC* IE defined in TS 36.331 [21], or the reason for RRC Connection Resume as received from the UE in the *ResumeCause* IE defined in TS 38.331 [18] or the *ResumeCause-r15* IE defined in TS 36.331 [21], or the reason for RRC Connection Establishment as received from the UE in the *EstablishmentCause-NB* IE defined in TS 36.331 [21]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------|----------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RRC Establishment Cause | M | | ENUMERATED (emergency, highPriorityAccess, mt-Access, mo-Signalling, mo-Data, mo-VoiceCall, mo-VideoCall, mo-SMS, mps-PriorityAccess, mcs-PriorityAccess, ..., notAvailable, mo-ExceptionData) | The notAvailable value is used in case the UE is re-establishing an RRC connection but there is fallback to RRC connection establishment as described in TS 38.331 [18], or the UE is resuming an RRC connection and the cause value received from the UE does not map to any other value of the RRC Establishment Cause IE. | + +### 9.3.1.112 Warning Area Coordinates + +This IE contains the affected alert area coordinates of a warning message, and will be broadcast over the radio interface. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------|----------|-------|------------------------------|-----------------------| +| Warning Area Coordinates | M | | OCTET STRING (SIZE(1..1024)) | | + +### 9.3.1.113 Network Instance + +This IE provides the network instance to be used by the NG-RAN node when selecting a particular transport network resource as described in TS 23.501 [9]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------|----------|-------|-----------------------|-----------------------| +| Network Instance | M | | INTEGER (1..256, ...) | | + +### 9.3.1.114 Secondary RAT Usage Information + +This IE provides information on the secondary resources used with MR-DC. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------------|----------|----------------------|---------------------------------------------------------------|-----------------------| +| PDU Session Usage Report | | 0..1 | | | +| >RAT Type | M | | ENUMERATED (nR, e-UTRA, ..., nR-unlicensed, eUTRA-unlicensed) | | +| >PDU Session Timed Report List | M | | Volume Timed Report List 9.3.1.115 | | +| QoS Flows Usage Report List | | 0..1 | | | +| >QoS Flow Usage Report Item | | 1.. | | | +| >>QoS Flow Indicator | M | | 9.3.1.51 | | +| >>RAT Type | M | | ENUMERATED (nR, e-UTRA, ..., nR-unlicensed, eUTRA-unlicensed) | | +| >>QoS Flows Timed Report List | M | | Volume Timed Report List 9.3.1.115 | | + +| Range bound | Explanation | +|-----------------|-----------------------------------------------------------------------| +| maxnoofQoSFlows | Maximum no. of QoS flows allowed within one PDU session. Value is 64. | + +### 9.3.1.115 Volume Timed Report List + +This IE provides information on the data usage. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------|----------|-------------------------|---------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Volume Timed Report Item | | 1.. | | | +| >Start Timestamp | M | | OCTET STRING (SIZE(4)) | UTC time encoded in the same format as the first four octets of the 64-bit timestamp format as defined in section 6 of IETF RFC 5905 [25]. It indicates the start time of the collecting period of the included Usage Count UL IE and Usage Count DL IE. | +| >End Timestamp | M | | OCTET STRING (SIZE(4)) | UTC time encoded in the same format as the first four octets of the 64-bit timestamp format as defined in section 6 of IETF RFC 5905 [25]. It indicates the end time of the collecting period of the included Usage Count UL IE and Usage Count DL IE. | +| >Usage Count UL | M | | INTEGER (0..2 64 -1) | The unit is: octets. | +| >Usage Count DL | M | | INTEGER (0..2 64 -1) | The unit is: octets. | + +| Range bound | Explanation | +|--------------------|----------------------------------------------------| +| maxnoofTimePeriods | Maximum no. of time reporting periods. Value is 2. | + +### 9.3.1.116 Redirection for Voice EPS Fallback + +This IE is used to indicate that the AMF and the UE support the redirection for voice for EPS Fallback. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------------|----------|-------|---------------------------------------------|-----------------------| +| Redirection for Voice EPS Fallback | M | | ENUMERATED
(possible, not-possible, ...) | | + +### 9.3.1.117 UE Retention Information + +This IE allows the NG-RAN node and the AMF to indicate whether prior UE related contexts and related UE-associated logical NG-connections and RRC connections are intended to be retained. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------|----------|-------|-----------------------------------|-----------------------| +| UE Retention Information | M | | ENUMERATED
(ues-retained, ...) | | + +### 9.3.1.118 UL Forwarding + +This IE indicates that the QoS flow is proposed for forwarding of uplink packets. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|---------------------------------------------|-----------------------| +| UL Forwarding | M | | ENUMERATED
(UL forwarding proposed, ...) | | + +### 9.3.1.119 CN Assisted RAN Parameters Tuning + +This IE provides information for assisting in parameters tuning of the NG-RAN node. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------| +| Expected UE Behaviour | O | | 9.3.1.93 | This IE may be present in case the Core Network Assistance Information for RRC INACTIVE IE is not included and is ignored otherwise. | + +### 9.3.1.120 Common Network Instance + +This IE provides the common network instance to be used by the NG-RAN node when selecting a particular transport network resource as described in TS 23.501 [9] in a format common with 5GC. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------| +| Common Network Instance | M | | OCTET STRING | The octets of OCTET STRING are encoded as the Network Instance field of the Network Instance IE specified in TS 29.244 [43] | + +### 9.3.1.121 Data Forwarding Response E-RAB List + +This IE is used at inter-system HO to provide DL data forwarding address information, if direct data forwarding is applied. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------------------|----------|--------------------|----------------------------------------|-------------------------------------------------------------------------------------| +| Data Forwarding Response E-RAB List | | 1.. | | The list may include the same DL Forwarding UP TNL Information for multiple E-RABs. | +| >E-RAB ID | M | | 9.3.2.3 | | +| >DL Forwarding UP TNL Information | M | | UP Transport Layer Information 9.3.2.2 | | + +| Range bound | Explanation | +|---------------|--------------------------------------| +| maxnoofE-RABs | Maximum no. of E-RABs. Value is 256. | + +### 9.3.1.122 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.123 RNC-ID + +The RNC-ID is used to identify an RNC. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-----------------------| +| RNC-ID | M | | INTEGER (0..4095) | | + +### 9.3.1.124 Extended RNC-ID + +This IE is used to identify an RNC. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------|----------|-------|-----------------------|-------------------------------------------------------------------| +| Extended RNC-ID | M | | INTEGER (4096..65535) | This IE is used if the RNC identity has a value larger than 4095. | + +### 9.3.1.125 RAT Information + +This IE provides RAT related information associated with a TAC, used as described in TS 23.501 [9]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------|----------|-------|------------------------------------------------------------------------------|-----------------------| +| RAT Information | M | | ENUMERATED
(unlicensed, nb-IoT, ..., nR-LEO, nR-MEO, nR-GEO, nR-OTHERSAT) | | + +### 9.3.1.126 Extended RAT Restriction Information + +This IE provides RAT restrictions as specified in TS 23.501 [9]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|----------|-------|----------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Primary RAT Restriction | M | | BIT STRING {
e-UTRA (0),
nR (1), nR-unlicensed (2), nR-LEO (3),
nR-MEO (4), nR-GEO (5),
nR-OTHERSAT (6)}
(SIZE(8, ...)) | Each position in the bitmap represents a Primary RAT. If a bit is set to "1", the respective RAT is restricted for the UE. If a bit is set to "0", the respective RAT is not restricted for the UE. Bit 7 reserved for future use. The Primary RAT is the RAT used in the access cell, or target cell. | +| Secondary RAT Restriction | M | | BIT STRING {
e-UTRA (0),
nR (1), e-UTRA-unlicensed (2), nR-unlicensed (3)}
(SIZE(8, ...)) | Each position in the bitmap represents a Secondary RAT. If a bit is set to "1", the respective RAT is restricted for the UE. If a bit is set to "0", the respective RAT is not restricted for the UE. Bits 4-7 reserved for future use. A Secondary RAT is a RAT, distinct from the UE's primary RAT, used in any cell serving the UE excluding the PCell. | + +### 9.3.1.127 SgNB UE X2AP ID + +This IE uniquely identifies an UE over the X2 interface within an en-gNB. The usage of this IE is defined in TS 37.340 [32]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------|----------|-------|---------------------------|-----------------------| +| SgNB UE X2AP ID | M | | INTEGER (0.. $2^{32}-1$ ) | | + +### 9.3.1.128 SRVCC Operation Possible + +This IE indicates that both UE and AMF are SRVCC-capable. NG-RAN behaviour on receipt of this IE is specified in TS 23.216 [31]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------|----------|-------|---------------------------------------------|-------------------------------------------------------------------| +| SRVCC Operation Possible | M | | ENUMERATED
(Possible, not Possible, ...) | The value "Possible" indicates that UE and AMF are SRVCC capable. | + +### 9.3.1.129 IAB Authorized + +This IE provides information about the authorization status of the IAB node. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------|----------|-------|-------------------------------------------------|----------------------------------------------| +| IAB Authorized | M | | ENUMERATED
(authorized, not authorized, ...) | Indicates the IAB node authorization status. | + +### 9.3.1.130 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.131 | | +| TSC Assistance Information Uplink | O | | TSC Assistance Information
9.3.1.131 | | + +### 9.3.1.131 TSC Assistance Information + +This IE provides the TSC assistance information for a TSC QoS flow in the uplink or downlink (see TS 23.501 [9]). + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------|----------|-------|---------------------------|-----------------------|-------------|----------------------| +| Periodicity | M | | 9.3.1.132 | | - | | +| Burst Arrival Time | O | | 9.3.1.133 | | - | | +| Survival Time | O | | 9.3.1.221 | | YES | ignore | +| CHOICE RAN Feedback Type | O | | | | YES | ignore | +| > proactive | | | | | | | +| >>Burst Arrival Time Window | M | | 9.3.1.255 | | - | | +| >>Periodicity Range | O | | 9.3.1.256 | | - | | +| > reactive | | | | | | | +| >>Capability for BAT Adaptation | M | | ENUMERATED
(true, ...) | | - | | +| N6 Jitter Information | O | | 9.3.1.265 | | YES | ignore | + +### 9.3.1.132 Periodicity + +This IE indicates the Periodicity of the TSC QoS flow as defined in TS 23.501 [9]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------------|-----------------------------------------| +| Periodicity | M | | INTEGER
(0..640000, ...) | Periodicity expressed in units of 1 us. | + +### 9.3.1.133 Burst Arrival Time + +This IE indicates the Burst Arrival Time of the TSC QoS flow as defined in TS 23.501 [9]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------| +| Burst Arrival Time | M | | OCTET STRING | Encoded in the same format as the ReferenceTime IE as defined in TS 38.331 [18]. The value is provided with 1 us accuracy. | + +### 9.3.1.134 Redundant QoS Flow Indicator + +This IE provides the redundant QoS flow indicator for a QoS flow as specified in TS 23.501 [9]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------|----------|-------|-----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Redundant QoS Flow Indicator | M | | ENUMERATED
(true, false) | This IE indicates whether this QoS flow is requested for the redundant transmission. Value "true" indicates that redundant transmission is requested for this QoS flow. Value "false" indicates that redundant transmission is requested to be stopped if started. | + +### 9.3.1.135 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.136 Redundant PDU Session Information + +This IE defines Redundancy information to be applied to a PDU session. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------|----------|-------|--------------------------|---------------------------------------------------------------------------------------------------------|-------------|----------------------| +| RSN | M | | ENUMERATED (v1, v2, ...) | | - | | +| PDU Session Pair ID | O | | INTEGER (0..255, ...) | as defined in TS 23.501 [9].
This IE may be present in the request message and is ignored otherwise. | YES | ignore | + +### 9.3.1.137 NB-IoT Default Paging DRX + +This IE indicates the NB-IoT Default Paging DRX as defined in TS 36.304 [29]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|----------|-------|---------------------------------------|-------------------------------| +| NB-IoT Default Paging DRX | M | | ENUMERATED (128, 256, 512, 1024, ...) | Unit: [number of radioframes] | + +### 9.3.1.138 NB-IoT Paging eDRX Information + +This IE indicates the NB-IoT Paging eDRX parameters as defined in TS 36.304 [29]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|----------|-------|-------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------| +| NB-IoT Paging eDRX Cycle | M | | ENUMERATED (hf2, hf4, hf6, hf8, hf10, hf12, hf14, hf16, hf32, hf64, hf128, hf256, hf512, hf1024, ...) | T eDRX defined in TS 36.304 [29].
Unit: [number of hyperframes]. | +| NB-IoT Paging Time Window | O | | ENUMERATED (s1, s2, s3, s4, s5, s6, s7, s8, s9, s10, s11, s12, s13, s14, s15, s16, ...) | Unit: [2.56 seconds] | + +### 9.3.1.139 NB-IoT Paging DRX + +This IE indicates the NB-IoT UE specific Paging DRX as defined in TS 36.304 [29]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------|----------|-------|-----------------------------------------------|-------------------------------| +| NB-IoT Paging DRX | M | | ENUMERATED (32, 64, 128, 256, 512, 1024, ...) | Unit: [number of radioframes] | + +### 9.3.1.140 Enhanced Coverage Restriction + +This IE provides information on the restriction information of using Coverage Enhancement. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------|----------|-------|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Enhanced Coverage Restriction | O | | ENUMERATED (restricted, ...) | Indicates whether the UE is restricted to use coverage enhancement.
Value "restricted" indicates that the UE is not allowed to use coverage enhancement. | + +### 9.3.1.141 Paging Assistance Data for CE Capable UE + +This IE provides Assistance Data for paging CE capable UE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Global Cell ID | M | | E-UTRA CGI 9.3.1.9 | | +| Coverage Enhancement Level | M | | OCTET STRING | Includes either the UEPagingCoverageInformation message as defined in TS 36.331 [21], or the UEPagingCoverageInformation-NB message as defined in TS 36.331 [21]. | + +### 9.3.1.142 UE Radio Capability ID + +This IE contains the UE Radio Capability ID. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------|----------|-------|-----------------------|----------------------------| +| UE Radio Capability ID | M | | OCTET STRING | Defined in TS 23.003 [23]. | + +### 9.3.1.143 WUS Assistance Information + +This IE provides WUS Assistance Information to be used by the NG-RAN node for determining the WUS group for the UE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------|----------|-------|----------------------------------------------------------------------------------------------------------------------------|-----------------------| +| Paging Probability Information | M | | ENUMERATED (p00, p05, p10, p15, p20, p25, p30, p35, p40, p45, p50, p55, p60, p65, p70, p75, p80, p85, p90, p95, p100, ...) | Unit: percentage | + +### 9.3.1.144 UE Differentiation Information + +This IE is generated by the AMF based on the UE subscription information, it provides the Expected UE Behavior Information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------|----------|-------|---------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Periodic Communication Indicator | O | | ENUMERATED (periodically, on demand, ...) | This IE indicates whether the UE communicates periodically or not, e.g. only on demand. | +| Periodic Time | O | | INTEGER (1..3600, ...) | This IE indicates the interval time of periodic communication, the unit is: second | +| Scheduled Communication Time | | 0..1 | | This IE indicates the time zone and day of the week when the UE is available for communication. | +| >Day of Week | O | | BIT STRING (SIZE(7)) | Each position in the bitmap represents a day of the week: first bit = Mon, second bit = Tue, third bit = Wed, and so on. Value '1' indicates 'scheduled'. Value '0' indicates 'not scheduled'.
If Day-Of-Week is not provided, this is interpreted as every day of the week. | +| >Time of Day Start | O | | INTEGER (0..86399, ...) | This IE indicates the time to start of the day, each value represents the corresponding second since 00:00 of the day.
If Time-Of-Day-Start is not provided, starting time is start of the day(s) indicated by Day-Of-Week-Mask. | +| >Time of Day End | O | | INTEGER (0..86399, ...) | This IE indicates the time to start of the day, each value represents the corresponding second since 00:00 of the day. The value of this IE should be bigger than the value of Time of Day Start IE.

If Time-Of-Day-End is not provided, ending time is end of the day(s) indicated by Day-Of-Week-Mask. | +| Stationary Indication | O | | ENUMERATED (stationary, mobile, ...) | | +| Traffic Profile | O | | ENUMERATED (single packet, dual packets, multiple packets, ...) | "single packet" indicates single packet transmission (UL or DL),
"dual packets" indicates dual packet transmission (UL with subsequent DL, or DL with subsequent UL),
"multiple packets" indicates multiple packets transmission. | +| Battery Indication | O | | ENUMERATED (battery powered, battery powered not rechargeable or replaceable, not battery powered, ...) | "battery powered" indicates that the UE is battery powered and the battery is rechargeable/replaceable,
"battery powered not rechargeable or replaceable" indicates that the UE is battery powered but the battery is not | + +| | | | | | +|--|--|--|--|-----------------------------------------------------------------------------------------------| +| | | | | rechargeable/replaceable, "not battery powered" indicates that the UE is not battery powered. | +|--|--|--|--|-----------------------------------------------------------------------------------------------| + +### 9.3.1.145 NB-IoT UE Priority + +This IE provides the NB-IoT UE Priority and to be used by the NG-RAN to prioritise between UEs accessing via NB-IoT. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------|----------|-------|-----------------------|----------------------------------------| +| NB-IoT UE Priority | M | | INTEGER (0..255, ...) | Lower value indicates higher priority. | + +### 9.3.1.146 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.147 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.148 NR UE Sidelink Aggregate Maximum Bit Rate + +This IE provides information on the Aggregate Maximum Bitrate of the UE's sidelink communication. + +| 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 is not valid, and considered as a logical error by the receiving NG-RAN node. | + +### 9.3.1.149 LTE UE Sidelink Aggregate Maximum Bit Rate + +This IE provides information on the Aggregate Maximum Bitrate of the UE's sidelink communication for LTE V2X services. + +| 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 is not valid, and considered as a logical error by the receiving NG-RAN node. | + +### 9.3.1.150 PC5 QoS Parameters + +This IE provides information on the PC5 QoS parameters of the UE's sidelink communication for NR PC5. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------|----------|-------------------------|-----------------------------------------------------------------------|---------------------------------------------------------------------| +| PC5 QoS Flow List | | 1 | | | +| > PC5 QoS Flow Item | | 1.. | | | +| >>PQI | M | | INTEGER (0..255, ...) | PQI is a special 5QI as specified in TS 23.501 [9]. | +| >> PC5 Flow Bit Rates | | 0..1 | | Only applies for GBR QoS Flows. | +| >>>Guaranteed Flow Bit Rate | M | | Bit Rate
9.3.1.4 | Guaranteed Bit Rate for the PC5 QoS flow. Details in TS 23.501 [9]. | +| >>>Maximum Flow Bit Rate | M | | Bit Rate
9.3.1.4 | Maximum Bit Rate for the PC5 QoS flow. Details in TS 23.501 [9]. | +| >>Range | O | | ENUMERATED (m50, m80, m180, m200, m350, m400, m500, m700, m1000, ...) | Only applies for groupcast. | +| PC5 Link Aggregate Bit Rates | O | | Bit Rate
9.3.1.4 | Only applies for non-GBR QoS Flows. | + +| Range bound | Explanation | +|--------------------|---------------------------------------------------------------------| +| maxnoofPC5QoSFlows | Maximum no. of PC5 QoS flows allowed towards one UE. Value is 2048. | + +### 9.3.1.151 Alternative QoS Parameters Set List + +This IE contains alternative sets of QoS parameters which the NG-RAN node can indicate to be fulfilled when notification control is enabled and it cannot fulfil the requested list of QoS parameters. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------------------|----------|-------------------------|-----------------------|-----------------------| +| Alternative QoS Parameters Set Item | | 1.. | | | +| >Alternative QoS Parameters Set Index | M | | 9.3.1.152 | | +| >Guaranteed Flow Bit Rate Downlink | O | | Bit Rate
9.3.1.4 | | +| >Guaranteed Flow Bit Rate Uplink | O | | Bit Rate
9.3.1.4 | | +| >Packet Delay Budget | O | | 9.3.1.80 | | +| >Packet Error Rate | O | | 9.3.1.81 | | + +| Range bound | Explanation | +|--------------------|--------------------------------------------------------------------------------------------| +| maxnoofQoSparaSets | Maximum no. of alternative sets of QoS Parameters allowed for the QoS profile. Value is 8. | + +### 9.3.1.152 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 the Alternative QoS Parameters Set List IE corresponding to the currently fulfilled alternative QoS parameters set. | + +### 9.3.1.153 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 parameters set. | + +### 9.3.1.154 E-UTRA Paging eDRX Information + +This IE indicates the E-UTRA Paging eDRX parameters as defined in TS 36.304 [29]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|----------|-------|-----------------------------------------------------------------------------------------------------|-----------------------------------------------------------------| +| E-UTRA Paging eDRX Cycle | M | | ENUMERATED (hfhalf, hf1, hf2, hf4, hf6, hf8, hf10, hf12, hf14, hf16, hf32, hf64, hf128, hf256, ...) | TeDRX defined in TS 36.304 [29]. Unit: [number of hyperframes]. | +| E-UTRA Paging Time Window | O | | ENUMERATED (s1, s2, s3, s4, s5, s6, s7, s8, s9, s10, s11, s12, s13, s14, s15, s16, ...) | Unit: [1.28 second]. | + +### 9.3.1.155 CE-mode-B Restricted + +This IE provides information on the restriction information of using Coverage Enhancement Mode B. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------|----------|-------|----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CE-mode-B Restricted | M | | ENUMERATED (restricted, not-restricted, ...) | Indicates whether the UE is restricted to use coverage enhancement.
Value "restricted" indicates that the UE is not allowed to use coverage enhancement mode B.
Value "not-restricted" indicates that the UE is allowed to use coverage enhancement mode B. | + +### 9.3.1.156 CE-mode-B Support Indicator + +This IE indicates whether CE-mode-B as specified in TS 36.306[42] is supported for the UE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------|----------|-------|-----------------------------|-----------------------| +| CE-mode-B Support Indicator | M | | ENUMERATED (supported, ...) | | + +### 9.3.1.157 LTE-M Indication + +This IE is provided by the NG-RAN node to inform that the UE indicates category M1 or M2 in its UE Radio Capability. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------|----------|-------|-------------------------|-----------------------| +| LTE-M Indication | M | | ENUMERATED (LTE-M, ...) | | + +### 9.3.1.158 Suspend Request Indication + +This IE indicates that the NG-RAN node requests immediate transition to RRC idle with suspend, as specified in TS 23.502 [10]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------|----------|-------|----------------------------------------|-----------------------| +| Suspend Request Indication | M | | ENUMERATED
(suspend-requested, ...) | | + +### 9.3.1.159 Suspend Response Indication + +This IE is used by the AMF to inform the NG-RAN node to suspend the UE and send it to RRC\_IDLE, as specified in TS 23.502 [10]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------|----------|-------|----------------------------------------|-----------------------| +| Suspend Response Indication | M | | ENUMERATED
(suspend-indicated, ...) | | + +### 9.3.1.160 UE User Plane CIoT Support Indicator + +This IE indicates whether User Plane CIoT 5GS Optimisation as specified in TS 23.501 [9] is supported for the UE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------------|----------|-------|--------------------------------|-----------------------| +| UE User Plane CIoT Support Indicator | M | | ENUMERATED
(supported, ...) | | + +### 9.3.1.161 Global TNGF ID + +This IE is used to globally identify a TNGF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------|----------|-------|-------------------------------|-----------------------| +| PLMN Identity | M | | 9.3.3.5 | | +| CHOICE TNGF ID | M | | | | +| > TNGF ID | | | | | +| >> TNGF ID | M | | BIT STRING
(SIZE(32, ...)) | | + +### 9.3.1.162 Global W-AGF ID + +This IE is used to globally identify a W-AGF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------|----------|-------|-------------------------------|-----------------------| +| PLMN Identity | M | | 9.3.3.5 | | +| CHOICE W-AGF ID | M | | | | +| > W-AGF ID | | | | | +| >> W-AGF ID | M | | BIT STRING
(SIZE(16, ...)) | | + +### 9.3.1.163 Global TWIF ID + +This IE is used to globally identify a TWIF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------|----------|-------|-------------------------------|-----------------------| +| PLMN Identity | M | | 9.3.3.5 | | +| CHOICE TWIF ID | M | | | | +| > TWIF ID | | | | | +| >> TWIF ID | M | | BIT STRING
(SIZE(32, ...)) | | + +### 9.3.1.164 W-AGF User Location Information + +This IE indicates the location information via wireline access as specified in TS 23.316 [34]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------------|----------|-------|-------------------------------|---------------------------------------------------------------------------------------------------------|-------------|----------------------| +| CHOICE W-AGF User Location Information | M | | | | - | | +| > Global Line ID | | | | | - | | +| >> Global Line ID | M | | OCTET STRING | Encoded as defined in TS 23.003 [23]. | - | | +| >> Line Type | O | | ENUMERATED
(DSL, PON, ...) | | - | | +| >> TAI | O | | 9.3.3.11 | | YES | ignore | +| > HFC Node ID | | | | | - | | +| >> HFC Node ID | M | | OCTET STRING | Indicates the identifier of the HFC node as specified in [37].
Encoded as defined in TS 23.003 [23]. | - | | +| > Global Cable ID | | | | | YES | ignore | +| >> Global Cable ID | M | | OCTET STRING | Encoded as defined in TS 23.003 [23]. | - | | +| > HFC Node ID New | | | | | YES | ignore | +| >> HFC Node ID | M | | OCTET STRING | Indicates the identifier of the HFC node as specified in [37].
Encoded as defined in TS 23.003 [23]. | - | | +| >> TAI | M | | 9.3.3.11 | | - | | +| >> Global Cable ID | O | | OCTET STRING | Encoded as defined in TS 23.003 [23]. | YES | ignore | +| > Global Cable ID New | | | | | YES | ignore | +| >> Global Cable ID | M | | OCTET STRING | Encoded as defined in TS 23.003 [23]. | - | | +| >> TAI | M | | 9.3.3.11 | | - | | + +### 9.3.1.165 Global eNB ID + +This IE is used to globally identify an eNB (see TS 36.401 [38]). + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------| +| PLMN Identity | M | | 9.3.3.5 | | +| CHOICE eNB ID | M | | | | +| >Macro eNB ID | | | | | +| >>Macro eNB ID | M | | BIT STRING (SIZE(20)) | Equal to the 20 leftmost bits of the E-UTRA Cell Identity IE contained in the E-UTRA CGI IE of each cell served by the eNB. | +| >Home eNB ID | | | | | +| >>Home eNB ID | M | | BIT STRING (SIZE(28)) | Equal to the E-UTRA Cell Identity IE contained in the E-UTRA CGI IE of the cell served by the eNB. | +| >Short Macro eNB ID | | | | | +| >>Short Macro eNB ID | M | | BIT STRING (SIZE(18)) | Equal to the 18 leftmost bits of the E-UTRA Cell Identity IE contained in the E-UTRA CGI IE of each cell served by the eNB. | +| >Long Macro eNB ID | | | | | +| >>Long Macro eNB ID | M | | BIT STRING (SIZE(21)) | Equal to the 21 leftmost bits of the E-UTRA Cell Identity IE contained in the E-UTRA CGI IE of each cell served by the eNB. | + +### 9.3.1.166 UE History Information from UE + +This IE contains information about mobility history report for a UE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------| +| CHOICE UE History Information from UE | M | | | | +| >NR | | | | | +| >>NR Mobility History Report | M | | OCTET STRING | Includes the mobilityHistoryReport contained in the UEInformationResponse message as defined in TS 38.331 [18]. | + +### 9.3.1.167 MDT Configuration + +This IE defines the MDT configuration parameters. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------|----------|-------|-----------------------|-----------------------| +| MDT Configuration-NR | O | | 9.3.1.169 | | +| MDT Configuration-EUTRA | O | | 9.3.1.170 | | + +### 9.3.1.168 MDT PLMN List + +The purpose of the *MDT PLMN List* IE is to provide the list of PLMN allowed for MDT. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------|----------|----------------------|-----------------------|-----------------------| +| MDT PLMN List | | 1.. | | | +| >PLMN Identity | M | | 9.3.3.5 | | + +| Range bound | Explanation | +|-----------------|---------------------------------------------------------| +| maxnoofMDTPLMNs | Maximum no. of PLMNs in the MDT PLMN list. Value is 16. | + +### 9.3.1.169 MDT Configuration-NR + +This IE defines the MDT configuration parameters of NR. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------|----------|---------------------------|-----------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| MDT Activation | M | | ENUMERATED
(Immediate MDT only, Logged MDT only, Immediate MDT and Trace, ...) | | - | | +| CHOICE Area Scope of MDT | M | | | | - | | +| >Cell based | | | | If PNI-NPN Area Scope of MDT IE is present, this IE covers non-CAG cells only, where non-CAG cells refer to cells that only provide public access. | | | +| >>Cell ID List for MDT | | 1.. | | | | | +| >>>NR CGI | M | | 9.3.1.7 | | - | | +| >TA based | | | | If PNI-NPN Area Scope of MDT IE is present, this IE covers non-CAG cells only, where non-CAG cells refer to cells that only provide public access. | | | +| >>TA List for MDT | | 1.. | | | | | +| >>>TAC | M | | 9.3.3.10 | The TAI is derived using the current serving PLMN. | - | | +| >PLMN wide | | | NULL | | | | +| >TAI based | | | | If PNI-NPN Area Scope of MDT IE is present, this IE covers non-CAG cells only, where non-CAG cells refer to cells that only provide public access. | | | +| >>TAI List for MDT | | 1.. | | | | | +| >>>TAI | M | | | | - | | +| >PNI-NPN Based MDT | | | | | YES | ignore | +| >>CAG List for MDT | | 1.. | | | - | | +| >>>PLMN ID | | | 9.3.3.5 | | - | | +| >>>CAG ID | M | | 9.3.3.43 | | - | | +| >SNPN Cell Based | | | | | YES | ignore | + +| | | | | | | | +|------------------------------------------|--------|---------------------------|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| MDT | | | | | | | +| >>SNPN Cell ID List for MDT | | 1.. | | | - | | +| >>>NR CGI | M | | 9.3.1.7 | | - | - | +| >>>NID | M | | 9.3.3.42 | Identifies an SNPN together with the PLMN Identity in the NR CGI IE. | - | - | +| >SNPN TAI Based MDT | | | | | YES | ignore | +| >>SNPN TAI List | | 1.. | | | - | - | +| >>>TAI | M | | 9.3.3.11 | | - | - | +| >>>NID | M | | 9.3.3.42 | Identifies an SNPN together with the PLMN Identity in the TAI IE. | - | - | +| >SNPN Based MDT | | | | | YES | ignore | +| >>MDT SNPN List | | 1.. | | | - | | +| >>>PLMN Identity | M | | 9.3.3.5 | | - | | +| >>>NID | M | | 9.3.3.42 | Identifies an SNPN together with the PLMN Identity IE. | - | | +| CHOICE MDT Mode | M | | | | - | | +| >Immediate MDT | | | | | | | +| >>Measurements to Activate | M | | BITSTRING (SIZE(8)) | Each position in the bitmap indicates a MDT measurement, as defined in TS 37.320 [41].
First Bit = M1,
Second Bit= M2,
Third Bit = M4,
Fourth Bit = M5,
Fifth Bit = M6,
Sixth Bit = M7,
Seventh Bit = logging of M1 from event triggered measurement reports according to existing RRM configuration, other bits reserved for future use.
Value “1” indicates “activate” and value “0” indicates “do not activate”. | - | | +| >>M1 Configuration | C-ifM1 | | 9.3.1.171 | | - | | +| >>M4 Configuration | C-ifM4 | | 9.3.1.172 | | - | | +| >>M5 Configuration | C-ifM5 | | 9.3.1.173 | | - | | +| >>M6 Configuration | C-ifM6 | | 9.3.1.174 | | - | | +| >>M7 Configuration | C-ifM7 | | 9.3.1.175 | | - | | + +| | | | | | | | +|--------------------------------------------|---|--|---------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| >>Bluetooth Measurement Configuration | O | | 9.3.1.177 | | - | | +| >>WLAN Measurement Configuration | O | | 9.3.1.178 | | - | | +| >>MDT Location Information | O | | 9.3.1.176 | | - | | +| >>Sensor Measurement Configuration | O | | 9.3.1.179 | | - | | +| >Logged MDT | | | | | | | +| >>Logging Interval | M | | ENUMERATED (320ms, 640ms, 1280ms, 2560ms, 5120ms, 10240ms, 20480ms, 30720ms, 40960ms, 61440ms, infinity, ...) | Corresponds to the LoggingInterval IE as defined in TS 38.331 [18]. | - | | +| >>Logging Duration | M | | ENUMERATED (10, 20, 40, 60, 90, 120, ...) | Corresponds to the LoggingDuration IE as defined in TS 38.331 [18]. Unit: [minute]. | - | | +| >>CHOICE Report Type | M | | | | - | | +| >>> Periodical | | | NULL | | | | +| >>> Event Triggered | | | | | | | +| >>>>Event Trigger Logged MDT Configuration | M | | 9.3.1.180 | | - | | +| >>Bluetooth Measurement Configuration | O | | 9.3.1.177 | | - | | +| >>WLAN Measurement Configuration | O | | 9.3.1.178 | | - | | +| >>Sensor Measurement Configuration | O | | 9.3.1.179 | | - | | +| >>Area Scope of Neighbour Cells | O | | 9.3.1.182 | | - | | +| >>Early Measurement | O | | ENUMERATED (true, ...) | This IE indicates whether the UE is allowed to log measurements on early measurement related frequencies in logged MDT as specified in TS 38.331 [18]. | YES | ignore | +| Signalling Based MDT PLMN List | O | | MDT PLMN List 9.3.1.168 | | - | | +| PNI-NPN Area Scope of MDT | O | | 9.3.3.65 | This IE is ignored if the PLMN Wide IE | YES | ignore | + +| | | | | | | | +|--|--|--|--|------------|--|--| +| | | | | is present | | | +|--|--|--|--|------------|--|--| + +| Range bound | Explanation | +|---------------------|------------------------------------------------------------| +| maxnoofCellIDforMDT | Maximum no. of Cell ID subject for MDT scope. Value is 32. | +| maxnoofTAforMDT | Maximum no. of TA subject for MDT scope. Value is 8. | +| maxnoofCAGforMDT | Maximum no. of CAG IDs for MDT scope. Value is 256. | +| maxnoofMDTSNPNs | Maximum no. of SNPNS in the MDT SNPNS list. Value is 16. | + +| Condition | Explanation | +|-----------|---------------------------------------------------------------------------------------------------| +| C-ifM1 | This IE shall be present if the Measurements to Activate IE has the first bit set to "1". | +| C-ifM4 | This IE shall be present if the Measurements to Activate IE has the third bit set to "1". | +| C-ifM5 | This IE shall be present if the Measurements to Activate IE has the fourth bit set to "1". | +| C-ifM6 | This IE shall be present if the Measurements to Activate IE has the fifth bit set to "1". | +| C-ifM7 | This IE shall be present if the Measurements to Activate IE has the sixth bit set to "1". | + +### 9.3.1.170 MDT Configuration-EUTRA + +This IE defines the MDT configuration parameters of EUTRA. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------|----------|--------------------------|-----------------------------------------------------------------------------------|----------------------------------------------------| +| MDT Activation | M | | ENUMERATED
(Immediate MDT only, Logged MDT only, Immediate MDT and Trace, ...) | | +| CHOICE Area Scope of MDT | M | | | | +| >Cell based | | | | | +| >>Cell ID List for MDT | | 1.. | | | +| >>>E-UTRA CGI | M | | 9.3.1.9 | | +| >TA based | | | | | +| >>TA List for MDT | | 1.. | | | +| >>>TAC | M | | 9.3.3.10 | The TAI is derived using the current serving PLMN. | +| >PLMN wide | | | NULL | | +| >TAI based | | | | | +| >>TAI List for MDT | | 1.. | | | +| >>>TAI | M | | 9.3.3.11 | | +| MDT Mode | M | | OCTET STRING | MDTMode IE defined in TS 36.413 [16]. | +| Signalling Based MDT PLMN List | O | | MDT PLMN List
9.3.1.168 | | + +| Range bound | Explanation | +|---------------------|------------------------------------------------------------| +| maxnoofCellIDforMDT | Maximum no. of Cell ID subject for MDT scope. Value is 32. | +| maxnoofTAforMDT | Maximum no. of TA subject for MDT scope. Value is 8. | + +### 9.3.1.171 M1 Configuration + +This IE defines the parameters for M1 measurement collection. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------|-------------------------|-------|-----------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| M1 Reporting Trigger | M | | ENUMERATED (periodic, A2event-triggered, A2event-triggered periodic, ...) | | - | | +| M1 Threshold Event A2 | C-
ifM1A2tri
gger | | | | - | | +| >CHOICE Threshold Type | M | | | | - | | +| >>RSRP | | | | | | | +| >>>Threshold RSRP | M | | INTEGER (0..127) | Corresponds to the RSRP-Range IE as defined in TS 38.331 [18]. | - | | +| >>RSRQ | | | | | | | +| >>>Threshold RSRQ | M | | INTEGER (0..127) | Corresponds to the RSRQ-Range IE as defined in TS 38.331 [18]. | - | | +| >>SINR | | | | | | | +| >>>Threshold SINR | M | | INTEGER (0..127) | Corresponds to the SINR-Range IE as defined in TS 38.331 [18]. | - | | +| M1 Periodic Reporting | C-
ifperiodic
MDT | | | | - | | +| >Report Interval | M | | ENUMERATED (ms120, ms240, ms480, ms640, ms1024, ms2048, ms5120, ms10240, min1, min6, min12, min30, min60) | Corresponds to the ReportInterval IE as defined in TS 38.331 [18]. The value min60 is not used in the specification. | - | | +| >Report Amount | M | | ENUMERATED (1, 2, 4, 8, 16, 32, 64, infinity) | Number of reports. | - | | +| >Extended Report Interval | O | | ENUMERATED (ms20480, ms40960, ...) | This IE is the extension of the Report Interval IE. If this IE is present, the Report Interval | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------------|-------------------|-------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | IE is ignored. | | | +| Include Beam Measurements Indication | O | | ENUMERATED (true, ...) | To configure whether the UE should include beam level measurements. | YES | ignore | +| Beam Measurements Report Configuration | C-ifM1BeamMeasInd | | | | YES | ignore | +| >Beam Measurements Report Quantity | | 0..1 | | This IE indicates the beam measurement quantity and corresponds to the MeasReportQuantity IE as defined in TS 38.331 [18]. | - | | +| >>RSRP | M | | ENUMERATED (true, ...) | | - | | +| >>RSRQ | M | | ENUMERATED (true, ...) | | - | | +| >>SINR | M | | ENUMERATED (true, ...) | | - | | +| >MaxNrofRS-IndexesToReport | O | | INTEGER (1..64, ...) | Indicates the max number of beam measurements to be reported and corresponds to the maxNrofRS-IndexesToReport in the ReportConfigNR IE as defined in TS 38.331 [18]. | - | | + +| Condition | Explanation | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------| +| C-ifM1A2trigger | This IE shall be present if the M1 Reporting Trigger IE is set to "A2event-triggered" or to "A2event-triggered periodic". | +| C-ifperiodicMDT | This IE shall be present if the M1 Reporting Trigger IE is set to "periodic", or to "A2event-triggered periodic". | +| C-ifM1BeamMeasInd | This IE shall be present if the Include Beam Measurements Indication IE is set to "true". | + +### 9.3.1.172 M4 Configuration + +This IE defines the parameters for M4 measurement collection. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------|----------|-------|--------------------------------------------------------------|-----------------------|-------------|----------------------| +| M4 Collection Period | M | | ENUMERATED (ms1024, ms2048, ms5120, ms10240, min1, ...) | | - | | +| M4 Links to Log | M | | ENUMERATED (uplink, downlink, both-uplink-and-downlink, ...) | | - | | +| M4 Report Amount | O | | ENUMERATED (1, 2, 4, 8, 16, 32, 64, infinity, ...) | Number of reports. | YES | ignore | + +### 9.3.1.173 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, 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.174 M6 Configuration + +This IE defines the parameters for M6 measurement collection. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------------|----------|-------|---------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------|----------------------| +| M6 Report Interval | M | | ENUMERATED (ms120, ms240, ms480, ms640, ms1024, ms2048, ms5120, ms10240, ms20480, ms40960, min1, min6, min12, min30, ...) | | - | | +| M6 Links to Log | M | | ENUMERATED (uplink, downlink, both-uplink-and-downlink, ...) | | - | | +| M6 Report Amount | O | | ENUMERATED (1, 2, 4, 8, 16, 32, 64, infinity, ...) | Number of reports | YES | ignore | +| Excess Packet Delay Threshold Configuration | O | | 9.3.1.244 | | YES | ignore | + +### 9.3.1.175 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 (uplink, downlink, both-uplink-and-downlink, ...) | | - | | +| M7 Report Amount | O | | ENUMERATED (1, 2, 4, 8, 16, 32, 64, infinity, ...) | Number of reports | YES | ignore | + +### 9.3.1.176 MDT Location Information + +This IE defines the MDT Location Information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MDT Location Information | M | | BITSTRING (SIZE(8)) | Each position in the bitmap represents requested location information as defined in TS 37.320 [41].
First Bit = GNSS
Other bits are reserved for future use and are ignored if received.
Value “1” indicates “activate” and value “0” indicates “do not activate”. | + +### 9.3.1.177 Bluetooth Measurement Configuration + +This IE defines the parameters for Bluetooth measurement collection. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------------------------|----------|---------------------------|------------------------------|--------------------------------------------------------------------------------------------| +| Bluetooth Measurement Configuration | M | | ENUMERATED (Setup, ...) | | +| Bluetooth Measurement Configuration Name List | | 0..1 | | This IE is present if the Bluetooth Measurement Configuration IE is set to “Setup”. | +| >Bluetooth Measurement Configuration Name Item | | 1.. | | | +| >>Bluetooth Measurement Configuration Name | M | | OCTET STRING (SIZE (1..248)) | | +| BT RSSI | O | | ENUMERATED (true, ...) | In case of Immediate MDT, it corresponds to M8 measurement as defined in TS 37.320 [41]. | + +| Range bound | Explanation | +|----------------------|--------------------------------------------------------------------------------------------| +| maxnoofBluetoothName | Maximum no. of Bluetooth local name used for Bluetooth measurement collection. Value is 4. | + +### 9.3.1.178 WLAN Measurement Configuration + +This IE defines the parameters for WLAN measurement collection. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------------------|----------|----------------------|-----------------------------|--------------------------------------------------------------------------------------------| +| WLAN Measurement Configuration | M | | ENUMERATED (Setup, ...) | | +| WLAN Measurement Configuration Name List | | 0..1 | | This IE is present if the Bluetooth Measurement Configuration IE is set to "Setup". | +| > WLAN Measurement Configuration Name Item | | 1.. | | | +| >>WLAN Measurement Configuration Name | M | | OCTET STRING (SIZE (1..32)) | | +| WLAN RSSI | O | | ENUMERATED (true, ...) | In case of Immediate MDT, it corresponds to M8 as defined in TS 37.320 [41]. | +| WLAN RTT | O | | ENUMERATED (true, ...) | In case of Immediate MDT, it corresponds to M9 as defined in TS 37.320 [41]. | + +| Range bound | Explanation | +|-----------------|----------------------------------------------------------------------------| +| maxnoofWLANName | Maximum no. of WLAN SSID used for WLAN measurement collection. Value is 4. | + +### 9.3.1.179 Sensor Measurement Configuration + +This IE defines the parameters for Sensor measurement collection. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------------------------------|----------|------------------------|-------------------------|-----------------------| +| Sensor Measurement Configuration | M | | ENUMERATED (Setup, ...) | | +| Sensor Measurement Configuration Name List | | 0..1 | | | +| > Sensor Measurement Configuration Name Item | | 1.. | | | +| >>CHOICE Sensor Name | M | | | | +| >>> Uncompensated Barometric | | | | | +| >>>>Uncompensated Barometric Configuration | M | | ENUMERATED (true, ...) | | +| >>> UE speed | | | | | +| >>>>UE Speed Configuration | M | | ENUMERATED (true, ...) | | +| >>> UE orientation | | | | | +| >>>>UE orientation Configuration | M | | ENUMERATED (true, ...) | | + +| Range bound | Explanation | +|-------------------|-------------------------------------------------------------------------------------| +| maxnoofSensorName | Maximum no. of Sensor local name used for Sensor measurement collection. Value is 3 | + +### 9.3.1.180 Event Trigger Logged MDT Configuration + +This IE defines the event trigger logged MDT configuration. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------------|----------|-------|----------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------| +| CHOICE Event trigger type | M | | | | +| > Out-of-coverage | | | | | +| >>Out-of-Coverage Configuration | M | | ENUMERATED (true, ...) | | +| > L1 Event | | | | | +| >>CHOICE L1 Event Threshold | M | | | | +| >>> RSRP | | | | | +| >>>>Threshold RSRP | M | | INTEGER (0..127) | Corresponds to the RSRP-Range IE as defined in TS 38.331 [18]. | +| >>> RSRQ | | | | | +| >>>>Threshold RSRQ | M | | INTEGER (0..127) | Corresponds to the RSRQ-Range IE as defined in TS 38.331 [18]. | +| >>Hysteresis | M | | INTEGER (0..30) | This parameter is used within the entry and leave condition of an event triggered reporting condition. | +| >>Time to Trigger | M | | ENUMERATED (ms0, ms40, ms64, ms80, ms100, ms128, ms160, ms256, ms320, ms480, ms512, ms640, ms1024, ms1280, ms2560, ms5120) | Time during which specific criteria for the event needs to be met in order to trigger a measurement report. | + +### 9.3.1.181 NR Frequency Info + +This defines the carrier frequency and bands used in a cell for a given direction (UL or DL) in FDD or for both UL and DL directions in TDD. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------|----------|--------------------------|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NR ARFCN | M | | INTEGER (0..maxNRARFCN) | RF Reference Frequency as defined in TS 38.104 [39], 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. | +| NR Frequency Band List | | 1 | | This IE is not used in this specification and is ignored. | +| >NR Frequency Band Item | | 1.. | | | +| >>NR Frequency Band | M | | INTEGER (1.. 1024, ...) | Primary NR Operating Band as defined in TS 38.104 [39], section 5.4.2.3. The value 1 corresponds to n1, value 2 corresponds to NR operating band n2, etc. | + +| Range bound | Explanation | +|--------------------|----------------------------------------------------------------------| +| maxNRARFCN | Maximum value of NRARFCNs. Value is 3279165. | +| maxnoofNRCellBands | Maximum no. of frequency bands supported for a NR cell. Value is 32. | + +### 9.3.1.182 Area Scope of Neighbour Cells + +This IE defines the area scope of neighbour cells for logged MDT. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------------|----------|----------------------------|------------------------|-----------------------| +| Area Scope of Neighbour Cells Item | M | 1.. | | | +| >NR Frequency Info | M | | 9.3.1.181 | | +| >PCI List for MDT | | 0.. | | | +| >>NR PCI | M | | INTEGER (0..1007, ...) | NR Physical Cell ID | + +| Range bound | Explanation | +|-----------------------|-------------------------------------------------------------------------| +| maxnoofFreqforMDT | Maximum no. of Frequency Information subject for MDT scope. Value is 8. | +| maxnoofNeighPCIforMDT | Maximum no. of Neighbour cells subject for MDT scope. Value is 32. | + +### 9.3.1.183 NPN Paging Assistance Information + +This IE contains NPN Paging Assistance Information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------------------|----------|-------|----------------------------------|-----------------------| +| CHOICE NPN Paging Assistance Information | M | | | | +| >PNI-NPN Paging Assistance | | | | | +| >>PNI-NPN Paging Assistance | M | | Allowed PNI-NPN List
9.3.3.45 | | + +### 9.3.1.184 NPN Mobility Information + +This IE indicates the access restrictions related to an NPN. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------|----------|-------------------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| CHOICE NPN Mobility Information | M | | | | - | | +| > SNPN Mobility Information | | | | | - | | +| >>Serving NID | M | | NID
9.3.3.42 | | - | | +| >>Equivalent SNPNs List | | 0..1 | | | YES | reject | +| >>>Equivalent SNPNs Item | | 1.. | | Allowed SNPNs in addition to Serving SNPN.
This list corresponds to the list of "equivalent SNPNs" as defined in TS 24.501 [26].
This list is part of the roaming restriction information.
Roaming restrictions apply to SNPNs other than the Serving SNPN and Equivalent SNPNs. | - | | +| >>>>PLMN Identity | M | | 9.3.3.5 | | - | | +| >>>>NID | M | | 9.3.3.42 | | - | | +| > PNI-NPN Mobility Information | | | | | - | | +| >>Allowed PNI-NPN List | M | | 9.3.3.45 | | - | | + +| Range bound | Explanation | +|--------------|-----------------------------------------------| +| maxnoofESPNs | Maximum no. of equivalent SNPNs. Value is 15. | + +### 9.3.1.185 Cell CAG Information + +This IE provides information about support of closed access groups for a designated cell. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-----------------------| +| NG-RAN CGI | M | | 9.3.1.73 | | +| Cell CAG List | M | | 9.3.3.47 | | + +### 9.3.1.186 Target to Source Failure Transparent Container + +This IE is used to transparently pass radio related information from the handover target to the handover source through the core network in case of failure of the preparation at the target; it is produced by the target RAN node and is transmitted to the source RAN node. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Target to Source Failure Transparent Container | M | | OCTET STRING | This IE includes a transparent container from the target RAN node to the source RAN node. The octets of the OCTET STRING are encoded according to the specifications of the target system.
Note: In the current version of the specification, this IE may carry the Target NG-RAN Node to Source NG-RAN Node Failure Transparent Container IE. | + +### 9.3.1.187 Target NG-RAN Node to Source NG-RAN Node Failure Transparent Container + +This IE is produced by the target NG-RAN node and is transmitted to the source NG-RAN node in case of preparation failure. + +This IE is transparent to the 5GC. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Cell CAG Information | O | | 9.3.1.185 | | - | | +| NGAP IE Support Information Response List | O | | 9.3.1.242 | | YES | ignore | + +### 9.3.1.188 DAPS Request Information + +The *DAPS Indicator* IE indicates that the source NG-RAN node requests a DAPS Handover for the concerned DRB. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------|----------|-------|------------------------------------|-------------------------------------------| +| DAPS Indicator | M | | ENUMERATED (DAPS HO required, ...) | Indicates that DAPS Handover is requested | + +### 9.3.1.189 DAPS Response Information + +The *DAPS Response Indicator* IE indicates the per DRB response to a requested DAPS Handover. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------|----------|-------|----------------------------------------------------------|-------------------------------------------------| +| DAPS Response Indicator | M | | ENUMERATED (DAPS HO accepted, DAPS HO not accepted, ...) | Indicates that DAPS Handover is accepted or not | + +### 9.3.1.190 Early Status Transfer Transparent Container + +The *Early Status Transfer Transparent Container* IE is an information element that is produced by the source NG-RAN node and is transmitted to the target NG-RAN node. This IE is used for the NG DAPS handover case, and for the NG-handover with time-based trigger condition case. + +This IE is transparent to the 5GC. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------------|----------|--------------------|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| CHOICE Procedure Stage | M | | | | - | | +| > First DL COUNT | | | | | | | +| >>DRBs Subject To Early Status Transfer List | | 1 | | | - | | +| >>>DRBs Subject To Early Status Transfer Item | | 1.. | | | - | | +| >>>>DRB ID | M | | 9.3.1.53 | | - | | +| >>>>CHOICE First DL COUNT | M | | | | - | | +| >>>>>12 bits | | | | | | | +| >>>>>>FIRST DL COUNT Value | M | | COUNT Value for PDCP SN Length 12 9.3.1.109 | PDCP-SN and Hyper frame number of the first DL SDU that the source NG-RAN node forwards to the target NG-RAN node in case of 12 bit long PDCP-SN | - | | +| >>>>>18 bits | | | | | | | +| >>>>>>FIRST DL COUNT Value | M | | COUNT Value for PDCP SN Length 18 9.3.1.110 | PDCP-SN and Hyper frame number of the first DL SDU that the source NG-RAN node forwards to the target NG-RAN node in case of 18 bit long PDCP-SN | - | | +| > DL Discarding | | | | | YES | ignore | +| >>DRBs Subject To DL Discarding List | | 1 | | | - | | +| >>>DRBs Subject To DL Discarding Item | | 1 .. | | | - | | +| >>>>DRB ID | M | | 9.3.1.53 | | - | | +| >>>>CHOICE DL Discarding | M | | | | - | | +| >>>>>12 bits | | | | | | | +| >>>>>>DISCARD DL COUNT Value | M | | COUNT Value for PDCP SN Length 12 9.3.1.109 | PDCP-SN and Hyper frame number for which the receiving NG-RAN node should discard forwarded DL SDUs | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------|----------|-------|---------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | associated with lower values in case of 12 bit long PDCP-SN | | | +| >>>>>18 bits | | | | | | | +| >>>>>DISCARD
DL COUNT Value | M | | COUNT Value for PDCP SN
Length 18
9.3.1.110 | PDCP-SN and Hyper frame number for which the receiving NG-RAN node should discard forwarded DL SDUs associated with lower values in case of 18 bit long PDCP-SN | - | | + +| Range bound | Explanation | +|-------------|----------------------------------------------------------| +| maxnoofDRBs | Maximum no. of DRBs allowed towards one UE. Value is 32. | + +### 9.3.1.191 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 | | 1.. | | | +| >S-NSSAI | M | | 9.3.1.24 | | + +| Range bound | Explanation | +|----------------------|---------------------------------------------------------------| +| maxnoofExtSliceItems | Maximum no. of signalled slice support items. Value is 65535. | + +### 9.3.1.192 UE Capability Info Request + +This IE indicates the request to provide to the AMF the UE radio capability related information when retrieved from the UE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------|----------|-------|--------------------------------|-----------------------| +| UE Capability Info Request | M | | ENUMERATED
(requested, ...) | | + +### 9.3.1.193 Extended RAN Node Name + +This IE provides extended human readable name of the NG-RAN node. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------|----------|-------|--------------------------------------|-----------------------| +| RAN Node Name Visible | O | | VisibleString
(SIZE(1..150, ...)) | | +| RAN Node Name UTF8 | O | | UTF8String
(SIZE(1..150, ...)) | | + +### 9.3.1.194 MICO All PLMN + +This IE indicates that the UE is configured with MICO mode by the AMF for the “all PLMN” as specified in TS 23.501 [9]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|---------------------------|-----------------------| +| MICO All PLMN | M | | ENUMERATED
(true, ...) | | + +### 9.3.1.195 Source Node ID + +This IE identifies the source SN for the handover. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------|----------|-------|--------------------------|-------------------------------------------------------------------------------------------------------| +| CHOICE Source Node ID | M | | | | +| > Source E-UTRAN Node ID | | | | | +| >>Source en-gNB ID | M | | Global gNB ID
9.3.1.6 | This IE is used for handover from EN-DC to SA. The source en-gNB ID is the identity of the source SN. | + +### 9.3.1.196 E-UTRAN Composite Available Capacity Group + +This IE indicates the overall available resource level in the cell in downlink and uplink. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------|----------|-------|---------------------------------------------------|-----------------------| +| Composite Available Capacity Downlink | M | | E-UTRAN Composite Available Capacity
9.3.1.197 | For the downlink | +| Composite Available Capacity Uplink | M | | E-UTRAN Composite Available Capacity
9.3.1.197 | For the uplink | + +### 9.3.1.197 E-UTRAN Composite Available Capacity + +This 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 | +|-----------------------------------|----------|-------|-----------------------|---------------------------------------------------------------------| +| E-UTRAN Cell Capacity Class Value | O | | 9.3.1.198 | | +| E-UTRAN Capacity Value | M | | 9.3.1.199 | '0' indicates no resource is available, Measured on a linear scale. | + +### 9.3.1.198 E-UTRAN Cell Capacity Class Value + +This IE indicates the value that classifies the cell capacity with regards to the other cells. This IE only indicates resources that are configured for traffic purposes. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Cell Capacity Class Value | M | | INTEGER (1..100, ...) | Value 1 indicates the minimum cell capacity, and 100 indicates the maximum cell capacity. There should be a linear relation between cell capacity and Cell Capacity Class Value. | + +### 9.3.1.199 E-UTRAN Capacity Value + +This IE indicates the amount of resources that are available relative to the total E-UTRAN resources. The capacity value should be measured and reported so that the minimum E-UTRAN resource usage of existing services is reserved according to implementation. This 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 indicates no available capacity, and 100 indicates maximum available capacity. Capacity Value should be measured on a linear scale. | + +### 9.3.1.200 E-UTRAN Radio Resource Status + +This IE indicates the usage of the PRBs for all traffic in downlink and uplink (TS 36.314 [49], TS 23.203 [50]) and the usage of PDCCH CCEs for downlink and uplink scheduling. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------|----------|-------|-----------------------|-----------------------| +| DL GBR PRB Usage | M | | INTEGER (0..100) | | +| UL GBR PRB Usage | M | | INTEGER (0..100) | | +| DL Non-GBR PRB Usage | M | | INTEGER (0..100) | | +| UL Non-GBR PRB Usage | M | | INTEGER (0..100) | | +| DL Total PRB Usage | M | | INTEGER (0..100) | | +| UL Total PRB Usage | M | | INTEGER (0..100) | | +| DL Scheduling PDCCH CCE Usage | O | | INTEGER (0..100) | | +| UL Scheduling PDCCH CCE Usage | O | | INTEGER (0..100) | | + +9.3.1.201 Void + +9.3.1.202 Void + +9.3.1.203 Void + +9.3.1.204 Void + +## 9.3.1.205 NR Radio Resource Status + +This IE indicates the usage of the PRBs per cell for MIMO for all traffic in Downlink and Uplink. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------| +| 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 [48]. | +| 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 [48]. | +| 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 [48]. | +| 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 [48]. | +| 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 [48]. | +| 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 [48]. | + +## 9.3.1.206 MBS Session ID + +This IE uniquely identifies an MBS session. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|------------------------|---------------------------------------| +| TMGI | M | | OCTET STRING (SIZE(6)) | Encoded as defined in TS 23.003 [23]. | +| NID | O | | 9.3.3.42 | | + +## 9.3.1.207 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.208 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.209 | | +| > location dependent | | | | | +| >>MBS Service Area Information List | | 1 | | | +| >>>MBS Service Area Information Item | | 1.. | | | +| >>>>MBS Area Session ID | M | | 9.3.1.207 | | +| >>>>MBS Service Area Information | M | | 9.3.1.209 | | + +| 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.209 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.. | | | +| >NR CGI | M | | 9.3.1.7 | | +| MBS Service Area TAI List | | 0.. | | | +| >TAI | M | | 9.3.3.11 | | + +| Range bound | Explanation | +|--------------------|--------------------------------------------------------------------------| +| maxnoofCellsforMBS | Maximum no. of cells allowed within one MBS Service Area. Value is 8192. | +| maxnoofTAIforMBS | Maximum no. of TAs allowed within one MBS Service Area. Value is 1024. | + +### 9.3.1.210 MBS Support Indicator + +This IE indicates whether MBS is supported for the NG-RAN node. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------|----------|-------|---------------------------|-----------------------| +| MBS Support Indicator | M | | ENUMERATED
(true, ...) | | + +### 9.3.1.211 MBS Session Setup Request List + +This IE provides information related to MBS sessions joined by the UE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------------------|----------|---------------------------------|---------------------------------|-----------------------|-------------|----------------------| +| MBS Session Setup Request List | | 1 | | | - | | +| > MBS Session Setup Request Item | | 1..oofMBS
essions> | | | - | | +| >>MBS Session ID | M | | 9.3.1.206 | | - | | +| >>MBS Area Session ID | O | | 9.3.1.207 | | - | | +| >> Associated MBS QoS Flow Setup Request List | | 0..1 | | | - | | +| >>> Associated MBS QoS Flow Setup Request Item | | 1..oofMBSQ
oSflows> | | | - | | +| >>>>MBS QoS Flow Identifier | M | | QoS Flow Identifier
9.3.1.51 | | - | | +| >>>>Associated Unicast QoS Flow Identifier | M | | QoS Flow Identifier
9.3.1.51 | | - | | +| >>MBS Assistance Information | O | | 9.3.1.263 | | YES | ignore | + +| Range bound | Explanation | +|--------------------|---------------------------------------------------------------------------| +| maxnoofMBSSessions | Maximum no. of MBS sessions allowed within one PDU session. Value is 32. | +| maxnoofMBSQoSflows | Maximum no. of MBS QoS flows allowed within one MBS session. Value is 64. | + +### 9.3.1.212 MBS Session Setup or Modify Request List + +This IE provides information related to MBS sessions joined by the UE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------------------------|----------|-------------------------|--------------------------------------|-------------------------------------------------------------------------------------|-------------|----------------------| +| MBS Session Setup or Modify Request List | | 1 | | | - | | +| > MBS Session Setup or Modify Request Item | | 1.. | | | - | | +| >>MBS Session ID | M | | 9.3.1.206 | | - | | +| >>MBS Area Session ID | O | | 9.3.1.207 | | - | | +| >>Associated MBS QoS Flow Setup or Modify Request List | | 0..1 | | | - | | +| >>>Associated MBS QoS Flow Setup or Modify Request Item | | 1.. | | | - | | +| >>>>MBS QoS Flow Identifier | M | | QoS Flow Identifier
9.3.1.51 | | - | | +| >>>>Associated Unicast QoS Flow Identifier | M | | QoS Flow Identifier
9.3.1.51 | | - | | +| >>MBS QoS Flow To Release List | O | | QoS Flow List with Cause
9.3.1.13 | This IE indicates the MBS QoS Flow Identifiers of the MBS QoS Flows to be released. | - | | +| >>MBS Assistance Information | O | | 9.3.1.263 | | YES | ignore | + +| Range bound | Explanation | +|--------------------|---------------------------------------------------------------------------| +| maxnoofMBSSessions | Maximum no. of MBS sessions allowed within one PDU session. Value is 32. | +| maxnoofMBSQoSflows | Maximum no. of MBS QoS flows allowed within one MBS session. Value is 64. | + +### 9.3.1.213 MBS Session Setup Response List + +This IE contains a list of information related to MBS sessions. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------------------|----------|-------------------------|-----------------------|-----------------------| +| MBS Session Setup Response List | | 1 | | | +| > MBS Session Setup Response Item | | 1.. | | | +| >>MBS Session ID | M | | 9.3.1.206 | | +| >>MBS Area Session ID | O | | 9.3.1.207 | | + +| Range bound | Explanation | +|--------------------|--------------------------------------------------------------------------| +| maxnoofMBSSessions | Maximum no. of MBS sessions allowed within one PDU session. Value is 32. | + +### 9.3.1.214 MBS Session Failed to Setup List + +This IE contains a list of information related to MBS sessions. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------------------|----------|------------------------|-----------------------|-----------------------| +| MBS Session Failed to Setup List | | 1 | | | +| >MBS Session Failed to Setup Item | | 1.. | | | +| >>MBS Session ID | M | | 9.3.1.206 | | +| >>MBS Area Session ID | O | | 9.3.1.207 | | +| >>Cause | M | | 9.3.1.2 | | + +| Range bound | Explanation | +|-------------------|--------------------------------------------------------------------------| +| maxnoofMBSessions | Maximum no. of MBS Sessions allowed within one PDU session. Value is 32. | + +### 9.3.1.215 MBS Session To Release List + +This IE indicates MBS sessions to be removed. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------------|----------|------------------------|-----------------------|-----------------------| +| MBS Session To Release List | | 1 | | | +| >MBS Session To Release Item | | 1.. | | | +| >>MBS Session ID | M | | 9.3.1.206 | | +| >>Cause | M | | 9.3.1.2 | | + +| Range bound | Explanation | +|-------------------|--------------------------------------------------------------------------| +| maxnoofMBSessions | Maximum no. of MBS sessions allowed within one PDU session. Value is 32. | + +### 9.3.1.216 Multicast Group Paging Area + +This IE contains a list of TAIs corresponding to the multicast group paging area. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------|----------|--------------------------|-----------------------|-----------------------| +| MBS Area TAI List | | 1.. | | | +| >TAI | M | | 9.3.3.11 | | + +| Range bound | Explanation | +|---------------------|--------------------------------------------------------------| +| maxnoofTAIforPaging | Maximum no. of TAIs for multicast group paging. Value is 16. | + +### 9.3.1.217 MBS Session Status + +This IE indicates whether the MBS session is activated or deactivated. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------|----------|-------|------------------------------------------|-----------------------| +| MBS Session Status | M | | ENUMERATED (activated, deactivated, ...) | | + +### 9.3.1.218 MRB ID + +This IE contains the MRB ID as specified in TS 38.401 [2]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-----------------------| +| MRB ID | M | | INTEGER (1..512, ...) | | + +### 9.3.1.219 MRB Progress Information + +This IE contains the MRB progress information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------|----------|-------|-----------------------|-----------------------| +| CHOICE PDCP SN Status | M | | | | +| >12bits | | | | | +| >>PDCP SN Length 12 | M | | INTEGER (0..4095) | | +| >18bits | | | | | +| >>PDCP SN Length 18 | M | | INTEGER (0..262143) | | + +### 9.3.1.220 Time Synchronisation Assistance Information + +This IE indicates 5G access stratum time distribution parameters as defined in TS 23.501 [9]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------------|-------------|-------|-------------------------------------|----------------------------|-------------|----------------------| +| Time Distribution Indication | M | | ENUMERATED (enabled, disabled, ...) | | - | | +| Uu Time Synchronisation Error Budget | C-ifEnabled | | INTEGER (1..1000000, ...) | Expressed in units of 1ns. | - | | +| Clock Quality Reporting Control Information | O | | 9.3.1.250 | | YES | ignore | + +| Condition | Explanation | +|-----------|---------------------------------------------------------------------------------------------| +| ifEnabled | This IE shall be present if the Time Distribution Indication IE is set to "enabled". | + +### 9.3.1.221 Survival Time + +This IE indicates the Survival Time of the TSC QoS flow as defined in TS 23.501 [9]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|---------------------------|-------------------------------------------| +| Survival Time | M | | INTEGER (0..1920000, ...) | Survival time expressed in units of 1 us. | + +### 9.3.1.222 QMC Deactivation + +This IE indicates the QMC configurations to be deactivated. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|----------|--------------------------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| QoE Reference List | | 1.. | | | +| >QoE Reference | M | | OCTET STRING (SIZE(6)) | QoE Reference , as defined in clause 5.2 of TS 28.405 [45]. It consists of MCC+MNC+QMC ID, where the MCC and MNC are coming with the QMC activation request from the management system to identify one PLMN containing the management system, and QMC ID is a 3-bytes Octet String. | + +| Range bound | Explanation | +|-----------------------|---------------------------------------------------------------| +| maxnoofUEAppLayerMeas | Maximum no. of UE application layer measurement. Value is 16. | + +### 9.3.1.223 QMC Configuration Information + +This IE contains the configuration information for the QMC functionality. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------------------------------------|----------|--------------------------------|-----------------------|-----------------------| +| UE Application Layer Measurement Information List | | 1 | | | +| >UE Application Layer Measurement Information Item | | 1.. | | | +| >>UE Application Layer Measurement Configuration Information | M | | 9.3.1.224 | | + +| Range bound | Explanation | +|-----------------------|----------------------------------------------------------------| +| maxnoofUEAppLayerMeas | Maximum no. of UE application layer measurements. Value is 16. | + +### 9.3.1.224 UE Application Layer Measurement Configuration Information + +This IE defines configuration information for the QMC functionality. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------|----------|----------------------------------|--------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| QoE Reference | M | | OCTET STRING (SIZE(6)) | QoE Reference , as defined in clause 5.2 of TS 28.405 [45]. It consists of MCC+MNC+QMC ID, where the MCC and MNC are coming with the QMC activation request from the management system to identify one PLMN containing the management system, and QMC ID is a 3-bytes Octet String. | - | | +| Service Type | M | | ENUMERATED (QMC for DASH streaming, QMC for MTSI, QMC for VR, ...) | This IE indicates the service type of QoE measurements. | - | | +| CHOICE Area Scope of QMC | O | | | | - | | +| > Cell based | | | | | | | +| >>Cell ID List for QMC | | 1..oofCellIDf
orQMC> | | | - | | +| >>>NG-RAN CGI | M | | 9.3.1.73 | This IE can indicate the NR CGI and E-UTRA CGI. | - | | +| > TA based | | | | | | | +| >>TA List for QMC | | 1..oofTAforQ
MC> | | | - | | +| >>>TAC | M | | 9.3.3.10 | The TAI is derived using the current serving PLMN. | - | | +| > TAI based | | | | | | | +| >>TAI List for QMC | | 1..oofTAforQ
MC> | | | - | | +| >>>TAI | M | | 9.3.3.11 | | - | | +| > PLMN area based | | | | | | | +| >>PLMN List for QMC | | 1..oofPLMNf
orQMC> | | | - | | +| >>>PLMN Identity | M | | 9.3.3.5 | | - | | +| Measurement Collection Entity IP Address | M | | Transport Layer Address 9.3.2.4 | The IP address of the entity receiving the QoE measurement report. | - | | +| QoE Measurement Status | O | | ENUMERATED (ongoing, ...) | Indicates whether the QoE | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|------------------------------------------------------------------------|-------------|----------------------| +| | | | | measurement has been started.
Present in case of NG-based handover. | | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------------------------|----------|----------------------------|-------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Container for Application Layer Measurement Configuration | O | | OCTET STRING (SIZE(1.. 8000)) | Contains application layer measurement configuration, see Annex L in 26.247 [46], clause 16.5 in TS 26.114 [51] and clause 9 in TS 26.118 [52]. Present in case of initial QoE configuration, and shall be included in Source to Target Transparent Container IE for signalling-based QMC during NG-based handover. | - | | +| Measurement Configuration Application Layer ID | O | | INTEGER (0..15, ...) | This IE is present only when the message containing it is NG-based handover related. The IE indicates the identity of the application layer measurement configuration and corresponds to the MeasConfigAppLayerId IE as defined in TS 38.331 [18]. | - | | +| Slice Support List for QMC | | 0..1 | | | - | | +| >Slice Support QMC Item | | 1.. | | | - | | +| >>S-NSSAI | M | | 9.3.1.24 | | - | | +| CHOICE MDT Alignment Information | O | | | Indicates the MDT measurements with which alignment is required. | - | | +| >S-based MDT | | | | | | | +| >>NG-RAN Trace ID | M | | OCTET STRING (SIZE(8)) | This IE is composed of the following: Trace Reference defined in TS 32.422 [11] (leftmost 6 octets, with PLMN information encoded as in 9.3.3.5), and Trace | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------------|----------|-------|----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | Recording Session Reference defined in TS 32.422 [11] (last 2 octets). | | | +| Available RAN Visible QoE Metrics | O | | 9.3.1.225 | Present in case of initial QoE configuration and in case of NG-based handover for signalling-based QoE measurement. | - | | +| Assistance Information for QoE Measurement | O | | INTEGER (1..16, ...) | This IE indicates the suggested priority of the application layer measurement configuration. Values are ordered in decreasing order of priority, i.e. with 1 as the highest priority and 16 as the lowest priority. | YES | ignore | +| MBS Communication Service Type | O | | ENUMERATED (broadcast, multicast, ...) | This IE indicates for which type of MBS communication service the QoE measurement configuration pertains to. | YES | ignore | + +| Range bound | Explanation | +|---------------------|-------------------------------------------------------------------------| +| maxnoofCellIDforQMC | Maximum no. of Cell ID subject for QMC scope. Value is 32. | +| maxnoofTAforQMC | Maximum no. of TA subject for QMC scope. Value is 8. | +| maxnoofPLMNforQMC | Maximum no. of PLMNs in the PLMN list for QMC scope. Value is 16. | +| maxnoofNSSAIforQMC | Maximum no. of S-NSSAIs in the S-NSSAI list for QMC scope. Value is 16. | + +### 9.3.1.225 Available RAN Visible QoE Metrics + +This IE defines which RAN visible QoE metrics can be configured by the NG-RAN in the RAN visible QoE measurement. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------|----------|-------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| Application Layer Buffer Level List | O | | ENUMERATED (true, ...) | The IE defines whether the Buffer Level can be collected as a RAN visible QoE metric by NG-RAN from UE, for DASH streaming and VR service types. | +| Playout Delay for Media Startup | O | | ENUMERATED (true, ...) | The IE defines whether the Playout delay can be collected as a RAN visible QoE metric by NG-RAN from UE, for DASH streaming and VR service types. | + +### 9.3.1.226 Void + +### 9.3.1.227 NR Paging eDRX Information + +This IE indicates the NR Paging eDRX parameters as defined in TS 38.304 [12]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------|----------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------| +| NR Paging eDRX Cycle | M | | ENUMERATED (hfquarter, hfhalf, hf1, hf2, hf4, hf8, hf16, hf32, hf64, hf128, hf256, hf512, hf1024, ...) | $T_{\text{eDRX CN}}$ defined in TS 38.304 [12]. 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) | PTW defined in TS 38.304 [12]. Unit: [1.28 seconds] | + +### 9.3.1.228 RedCap Indication + +This IE is provided by the NG-RAN node to inform that the UE indicates Reduced Capability. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------|----------|-------|--------------------------|-----------------------| +| RedCap Indication | M | | ENUMERATED (RedCap, ...) | | + +### 9.3.1.229 Target NSSAI Information + +This IE contains the Target NSSAI and Index to RAT/Frequency Selection Priority as specified in TS 23.501 [9]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------------|----------|-------|-----------------------|-----------------------| +| Target NSSAI | M | | 9.3.1.230 | | +| Index to RAT/Frequency Selection Priority | M | | 9.3.1.61 | | + +### 9.3.1.230 Target NSSAI + +This IE contains the Target NSSAI as specified in TS 23.501 [9]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------|----------|----------------------------|-----------------------|-----------------------| +| Target S-NSSAI List | | 1 | | | +| >Target S-NSSAI Item | | 1.. | | | +| >>S-NSSAI | M | | 9.3.1.24 | | + +| Range bound | Explanation | +|-----------------------|---------------------------------------------| +| maxnoofTargetS-NSSAIs | Maximum no. of Target S-NSSAIs. Value is 8. | + +### 9.3.1.231 UE Slice Maximum Bit Rate List + +This IE contains the UE Slice Maximum Bit Rate List as specified in TS 23.501 [9]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------|----------|-----------------------------|-----------------------|----------------------------------------------------------------------------| +| UE Slice Maximum Bit Rate Item | | 1.. | | Applicable across all GBR and Non-GBR QoS flows. | +| >S-NSSAI | M | | 9.3.1.24 | | +| >UE Slice Maximum Bit Rate Downlink | M | | Bit Rate
9.3.1.4 | This IE indicates the downlink UE-Slice-MBR as specified in TS 23.501 [9]. | +| >UE Slice Maximum Bit Rate Uplink | M | | Bit Rate
9.3.1.4 | This IE indicates the uplink UE-Slice-MBR as specified in TS 23.501 [9]. | + +| Range bound | Explanation | +|------------------------|---------------------------------------------| +| maxnoofAllowedS-NSSAIs | Maximum no. of allowed S-NSSAI. Value is 8. | + +### 9.3.1.232 PEIPS Assistance Information + +This IE provides the information related to CN paging subgrouping for a particular UE, as specified in TS 38.304 [12]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------|----------|-------|-----------------------|-----------------------| +| CN Subgroup ID | M | | INTEGER (0..7, ...) | | + +### 9.3.1.233 5G ProSe Authorized + +This IE provides information on the authorization status of the UE to use the 5G 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.234 5G ProSe PC5 QoS Parameters + +This IE provides information on the 5G ProSe PC5 QoS parameters of the UE's sidelink communication for 5G ProSe services. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------|----------|-------------------------|-----------------------------------------------------------------------|---------------------------------------------------------------------| +| 5G ProSe PC5 QoS Flow List | | 1 | | | +| >>5G ProSe PC5 QoS Flow Item | | 1.. | | | +| >>PQI | M | | INTEGER (0..255, ...) | PQI is a special 5QI as specified in TS 23.501 [9]. | +| >>5G ProSe PC5 Flow Bit Rates | | 0..1 | | Only applies for GBR QoS flows. | +| >>>Guaranteed Flow Bit Rate | M | | Bit Rate 9.3.1.4 | Guaranteed Bit Rate for the PC5 QoS flow. Details in TS 23.501 [9]. | +| >>>Maximum Flow Bit Rate | M | | Bit Rate 9.3.1.4 | Maximum Bit Rate for the PC5 QoS flow. Details in TS 23.501 [9]. | +| >>Range | O | | ENUMERATED (m50, m80, m180, m200, m350, m400, m500, m700, m1000, ...) | Only applies for groupcast. | +| 5G ProSe PC5 Link Aggregate Bit Rates | O | | Bit Rate 9.3.1.4 | Only applies for Non-GBR QoS flows. | + +| Range bound | Explanation | +|--------------------|---------------------------------------------------------------------| +| maxnoofPC5QoSFlows | Maximum no. of PC5 QoS flows allowed towards one UE. Value is 2048. | + +### 9.3.1.235 Last Visited PSCell Information + +The Last Visited PSCell Information may contain cell specific information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PSCell ID | O | | NG-RAN CGI 9.3.1.73 | This IE is present when the SCG resources are configured for the UE. | +| Time Stay | M | | INTEGER (0..40950) | The duration of the time the UE stayed in the cell in 1/10 seconds. If the UE stays in a cell more than 4095s, this IE is set to 40950.
Or the duration of the time when no SCG resources are configured for the UE. | + +### 9.3.1.236 MBS QoS Flows To Be Setup List + +This IE contains a list of QoS flows and their associated QoS parameters. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------------------|----------|-------------------------|----------------------------------------------|-----------------------| +| MBS QoS Flows Setup Request Item | | 1.. | | | +| >MBS QoS Flow Identifier | M | | QoS Flow Identifier
9.3.1.51 | | +| >MBS QoS Flow Level QoS Parameters | M | | QoS Flow Level
QoS Parameters
9.3.1.12 | | + +| Range bound | Explanation | +|--------------------|---------------------------------------------------------------------------| +| maxnoofMBSQoSFlows | Maximum no. of MBS QoS flows allowed within one MBS session. Value is 64. | + +### 9.3.1.237 Reporting System + +This IE lists the cells on the reporting system. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------|----------|---------------------------|------------------------|---------------------------------------------------------------------------------------------------| +| CHOICE Reporting System | | | | | +| >E-UTRAN | | | | | +| >>E-UTRAN Cell To Report List | | 1 | | | +| >>>E-UTRAN Cell To Report Item | | 1.. | | | +| >>>>Cell ID | M | | E-UTRA CGI
9.3.1.9 | | +| >NG-RAN | | | | | +| >>NG-RAN Cell To Report List | | 1 | | | +| >>>NG-RAN Cell To Report Item | | 1.. | | | +| >>>>Cell ID | M | | NG-RAN CGI
9.3.1.73 | | +| >No Reporting | | | NULL | Resource status not available.
Applicable to the Inter-system Resource Status Reply IE. | + +| Range bound | Explanation | +|----------------------|----------------------------------------------------------| +| maxnoofReportedCells | Maximum no. of cells that can be reported. Value is 256. | + +### 9.3.1.238 TAI NSAG Support List + +This IE contains the slice group mapping for all groups configured at the NG-RAN node per TAI. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------|----------|-------------------|---------------------------------------------|-----------------------------------------------------------| +| TAI NSAG Support Item | | 1.. | | | +| >NSAG ID | M | | INTEGER (0..255,
...) | | +| >NSAG Slice Support List | M | | Extended Slice
Support List
9.3.1.191 | Indicates the list of slices which
belong to the NSAG. | + +| Range bound | Explanation | +|--------------|--------------------------------------------------------| +| maxnoofNSAGs | Maximum no. of Slice Groups for the TAI. Value is 256. | + +### 9.3.1.239 NGAP Protocol IE-Id + +This IE uniquely identifies an NGAP Protocol IE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------|----------|-------|-----------------------|-----------------------| +| NGAP Protocol IE-Id | M | | INTEGER
(0..65535) | | + +### 9.3.1.240 NGAP Protocol IE Support Information + +This IE provides information about support of functions associated to an NGAP Protocol IE-Id. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------------|----------|-------|-----------------------------------------------|-----------------------| +| NGAP Protocol IE Support Information | M | | ENUMERATED
(supported, not-supported, ...) | | + +### 9.3.1.241 NGAP Protocol IE Presence Information + +This IE provides information on whether an NGAP Protocol IE-Id was received within the message requesting the information (i.e. HANDOVER REQUEST). + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------|----------|-------|--------------------------------------|-----------------------| +| NGAP Protocol IE Presence Information | M | | ENUMERATED
(present, not present) | | + +### 9.3.1.242 NGAP IE Support Information Response List + +This IE provides information about support of functions associated to a list of NGAP Protocol IE-Ids. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------------------------|----------|----------------------------|-----------------------|-----------------------| +| NGAP IE Support Information Response Item | | 1.. | | | +| >NGAP Protocol IE-Id | M | | 9.3.1.239 | | +| >NGAP Protocol IE Support Information | M | | 9.3.1.240 | | +| >NGAP Protocol IE Presence Information | M | | 9.3.1.241 | | + +| Range bound | Explanation | +|----------------------|-----------------------------------------------------| +| maxnoofIESupportInfo | Maximum no. of IE Support Information. Value is 32. | + +### 9.3.1.243 MDT PLMN Modification List + +This IE provides the modified list of PLMN allowed for MDT. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------------|----------|-----------------------------------|-----------------------|-----------------------------------------------------------| +| MDT PLMN Modification List | | 0..<maxnoofMDTPLMNs> | | An empty list indicates there is no PLMN allowed for MDT. | +| >PLMN Identity | M | | 9.3.3.5 | | + +| Range bound | Explanation | +|-----------------|---------------------------------------------------------| +| maxnoofMDTPLMNs | Maximum no. of PLMNs in the MDT PLMN list. Value is 16. | + +### 9.3.1.244 Excess Packet Delay Threshold Configuration + +This IE defines the parameters for Excess Packet Delay Threshold configuration to support the calculation of the PDCP Excess Packet Delay in the UL per DRB as specified in TS 38.314 [48]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------------|----------|---------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------| +| Excess Packet Delay Threshold Item | | 1..<maxnoofThresholdsForExcessPacketDelay> | | | +| >5QI | M | | INTEGER (0..255, ...) | Indicates the standardized or pre-configured 5QI as specified in TS 23.501 [9]. | +| >Excess Packet Delay Threshold Value | M | | ENUMERATED (ms0.25, ms0.5, ms1, ms2, ms4, ms5, ms10, ms20, ms30, ms40, ms50, ms60, ms70, ms80, ms90, ms100, ms150, ms300, ms500, ...) | | + +| Range bound | Explanation | +|---------------------------------------|--------------------------------------------------------------------------------| +| maxnoofThresholdsForExcessPacketDelay | Maximum no. of thresholds for Excess Packet Delay configuration. Value is 255. | + +### 9.3.1.245 Network Controlled Repeater Authorized + +This IE provides the authorization status of the UE to act as a Network Controlled Repeater. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------|----------|-------|----------------------------------------------|-----------------------------------------------------------------------| +| Network Controlled Repeater Authorized | M | | ENUMERATED (authorized, not authorized, ...) | Indicates whether the UE is authorized as Network Controlled Repeater | + +### 9.3.1.246 Aerial UE Subscription Information + +This information element is used by the NG-RAN node to know if the UE is allowed to use aerial function, refer to TS 23.501 [9]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------------|----------|-------|---------------------------------------|-----------------------| +| Aerial UE Subscription Information | M | | ENUMERATED (allowed, not allowed,...) | | + +### 9.3.1.247 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 | +|-------------------|----------|-------|----------------------------------------------|-------------------------------------------------------------| +| UAV UE | O | | ENUMERATED (authorized, not authorized, ...) | Indicates whether the UE is authorized as UAV UE | +| UAV controller UE | O | | ENUMERATED (authorized, not authorized, ...) | Indicates whether the UE is authorized as UAV controller UE | + +### 9.3.1.248 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 | +|-------------------|----------|-------|----------------------------------------------|-------------------------------------------------------------| +| UAV UE | O | | ENUMERATED (authorized, not authorized, ...) | Indicates whether the UE is authorized as UAV UE | +| UAV controller UE | O | | ENUMERATED (authorized, not authorized, ...) | Indicates whether the UE is authorized as UAV controller UE | + +### 9.3.1.249 A2X PC5 QoS Parameters + +This IE provides information on the PC5 QoS parameters of the UE's sidelink communication for A2X. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------|----------|-------------------------|-----------------------------------------------------------------------|---------------------------------------------------------------------| +| A2X PC5 QoS Flow List | | 1 | | | +| > A2X PC5 QoS Flow Item | | 1.. | | | +| >>A2X PQI | M | | INTEGER (0..255, ...) | PQI is a special 5QI as specified in TS 23.501 [9]. | +| >> A2X PC5 Flow Bit Rates | | 0..1 | | Only applies for GBR QoS Flows. | +| >>>A2X Guaranteed Flow Bit Rate | M | | Bit Rate 9.3.1.4 | Guaranteed Bit Rate for the PC5 QoS flow. Details in TS 23.501 [9]. | +| >>>A2X Maximum Flow Bit Rate | M | | Bit Rate 9.3.1.4 | Maximum Bit Rate for the PC5 QoS flow. Details in TS 23.501 [9]. | +| >>A2X Range | O | | ENUMERATED (m50, m80, m180, m200, m350, m400, m500, m700, m1000, ...) | Only applies for groupcast. | +| A2X PC5 Link Aggregate Bit Rates | O | | Bit Rate 9.3.1.4 | Only applies for non-GBR QoS Flows. | + +| Range bound | Explanation | +|--------------------|---------------------------------------------------------------------| +| maxnoofPC5QoSFlows | Maximum no. of PC5 QoS flows allowed towards one UE. Value is 2048. | + +### 9.3.1.250 Clock Quality Reporting Control Information + +This IE indicates the clock quality reporting control information as defined in TS 23.501 [9]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------------|----------|-------|-----------------------|-----------------------| +| CHOICE Clock Quality Detail Level | M | | | | +| > clock quality metrics | | | NULL | | +| > clock quality acceptance indication | | | | | +| >>Clock Quality Acceptance Criteria | M | | 9.3.1.251 | | + +### 9.3.1.251 Clock Quality Acceptance Criteria + +This IE indicates the clock quality acceptance criteria as defined in TS 23.501 [9]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|----------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Synchronisation State | O | | BIT STRING {
locked (0),
holdover (1),
freeRun (2) }
(SIZE (8, ...)) | Each position in the bitmap represents a synchronisation state.
If a bit is set to "1", the respective synchronisation state is acceptable. If a bit is set to "0", the respective synchronisation state is not acceptable.
Bits 3-7 reserved for future use. | +| Traceable to UTC | O | | ENUMERATED
(true, ...) | | +| Traceable to GNSS | O | | ENUMERATED
(true, ...) | | +| Clock Frequency Stability | O | | BIT STRING (SIZE
(16)) | Indicates the offsetScaledLogVariance as specified in TS 23.501 [9]. | +| Clock Accuracy | O | | INTEGER
(1..400000000, ...) | Clock accuracy expressed in units of 25 ns. | +| Parent Time Source | O | | BIT STRING {
syncE (0),
pTP (1),
gNSS (2),
atomicClock (3),
terrestrialRadio (4),
serialTimeCode (5),
nTP (6),
handset (7),
other (8) }
(SIZE (16, ...)) | Each position in the bitmap represents a parent time source.
If a bit is set to "1", the respective parent time source is acceptable.
If a bit is set to "0", the respective parent time source is not acceptable.
Bits 9-15 reserved for future use. | + +### 9.3.1.252 RAN Timing Synchronisation Status Information + +This IE indicates the RAN timing synchronisation status information provided towards the AMF as defined in TS 23.501 [9]. + +| 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 [9]. | +| Clock Accuracy | O | | 9.3.1.253 | | +| Parent Time Source | O | | ENUMERATED
(syncE, pTP, gNSS,
atomicClock,
terrestrialRadio,
serialTimeCode,
nTP, handSet,
other, ...) | | + +### 9.3.1.253 Clock Accuracy + +This IE indicates the clock accuracy as defined in TS 23.501 [9]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------|----------|-------|---------------------------------|-------------------------------------------------------------------------------------------------------------| +| CHOICE Clock Accuracy | M | | | | +| >Value | | | | | +| >>Clock Accuracy Value | M | | INTEGER (1..
400000000, ...) | Indicates the absolute clock accuracy value. Unit in 25ns. | +| >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 [55]. | + +### 9.3.1.254 RAN TSS Scope + +This IE indicates the scope of the RAN timing synchronisation status as defined in TS 23.501 [9]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------|----------|------------------------------------|-----------------------|-----------------------| +| CHOICE RAN TSS scope | M | | | | +| > RAN node level | | | | | +| >>Global gNB ID | M | | 9.3.1.6 | | +| > cell list level | | | | | +| >> RAN TSS Cell List | | 1 | | | +| >>> RAN TSS Cell Item | | 1.. <maxnoofCellsTSS> | | | +| >>>>NR CGI | M | | 9.3.1.7 | | + +| Range bound | Explanation | +|-----------------|------------------------------------------------------------------------------------------------| +| maxnoofCellsTSS | Maximum no. of Cell IDs in the scope of the RAN timing synchronisation status. Value is 16384. | + +### 9.3.1.255 Burst Arrival Time Window + +This IE indicates the burst arrival time window of the TSC QoS flow as defined in TS 23.501 [9]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------|----------|-------|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Burst Arrival Time Window Start | 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. | +| Burst Arrival Time Window End | 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.256 Periodicity Range + +This IE indicates the periodicity range for the TSC QoS flow as defined in TS 23.501 [9]. + +| 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.132 | | +| >>Periodicity Upper Bound | M | | Periodicity
9.3.1.132 | | +| > Periodicity List | | | | | +| >>Allowed Periodicity List | | 1 | | | +| >>>Allowed Periodicity Item | | 1.. | | | +| >>>>Allowed Periodicity | M | | Periodicity
9.3.1.132 | | + +| Range bound | Explanation | +|-----------------------------|---------------------------------------------------| +| maxnoofPeriodicities | Maximum no. of allowed periodicities. Value is 8. | + +### 9.3.1.257 TSC Traffic Characteristics Feedback + +This IE provides the TSC traffic characteristics feedback of a TSC QoS flow (see TS 23.501 [9]). + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------------|----------|-------|---------------------------------------|-----------------------| +| TSC Feedback Information Downlink | O | | TSC Feedback Information
9.3.1.258 | | +| TSC Feedback Information Uplink | O | | TSC Feedback Information
9.3.1.258 | | + +### 9.3.1.258 TSC Feedback Information + +This IE provides the TSC feedback information for a TSC QoS flow in the uplink or downlink (see TS 23.501 [9]). + +| 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.132 | Not applicable to reactive RAN feedback. | + +### 9.3.1.259 Mobile IAB Authorized + +This IE provides information about the authorization status of the mobile IAB-node. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------|----------|-------|----------------------------------------------|-----------------------------------------------------| +| Mobile IAB Authorized | M | | ENUMERATED (authorized, not authorized, ...) | Indicates the mobile IAB-node authorization status. | + +### 9.3.1.260 IAB-MT User Location Information + +This IE contains the NR CGI and the TAI for the co-located mobile IAB-MT of the UE's serving mobile IAB-DU. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------| +| NR CGI | M | | 9.3.1.7 | The NR CGI of the cell, which is the serving cell of the mobile IAB-MT co-located with the mobile IAB-DU that serves the UE. | +| TAI | O | | 9.3.3.11 | The TAI supported by the cell, which is the serving cell of the mobile IAB-MT co-located with the UE's serving mobile IAB-DU. | + +### 9.3.1.261 Partially Allowed NSSAI + +This IE contains a list of S-NSSAI(s) partially permitted by the network for the UE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------|----------|--------------------------------------|-----------------------|-----------------------| +| Partially Allowed S-NSSAI List | | 1 | | | +| >Partially Allowed S-NSSAI Item | | 1.. | | | +| >>S-NSSAI | M | | 9.3.1.24 | | + +| Range bound | Explanation | +|---------------------------------|-------------------------------------------------------| +| maxnoofPartiallyAllowedS-NSSAIs | Maximum no. of partially allowed S-NSSAI. Value is 8. | + +### 9.3.1.262 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 the AssociatedSessionId IE defined in TS 29.571 [35]. The gNB does not interpret the content of the Associated Session ID IE. | + +### 9.3.1.263 MBS Assistance Information + +This IE provides MBS Assistance Information as specified in TS 38.300 [8] and TS 23.247 [44]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------|----------|-------|------------------------|-----------------------| +| MBS Assistance Information | M | | ENUMERATED (true, ...) | | + +### 9.3.1.264 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 Packet Delay Budget | O | | Extended Packet Delay Budget 9.3.1.135 | PDU Set Delay Budget as specified in TS 23.501 [9]. | +| PDU Set Error Rate | O | | Packet Error Rate 9.3.1.81 | PDU Set Error Rate as specified in TS 23.501 [9]. | +| PDU Set Integrated Handling Information | O | | ENUMERATED (true, false, ...) | PDU Set Integrated Handling Information as specified in TS 23.501 [9]. | + +### 9.3.1.265 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 (-127..127) | Indicates the lower bound of the 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.266 ECN Marking or Congestion Information Reporting Request + +This IE indicates to the NG-RAN node to perform ECN marking or to report information for ECN marking or to report congestion information for a QoS Flow. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------------------------------|----------|-------|--------------------------------------|-----------------------| +| CHOICE ECN Marking or Congestion Information Request | M | | | | +| > ECN Marking at RAN | | | | | +| >>ECN Marking at NG-RAN Request | M | | ENUMERATED (ul, dl, both, stop, ...) | | +| > ECN Marking at UPF | | | | | +| >>ECN Marking at UPF Request | M | | ENUMERATED (ul, dl, both, stop, ...) | | +| > Congestion Information | | | | | +| >>Congestion Information Request | M | | ENUMERATED (ul, dl, both, stop, ...) | | + +### 9.3.1.267 ECN Marking or Congestion Information Reporting Status + +This IE contains a list of QoS flows with activation status information for NG-RAN node to perform ECN marking or to report information for ECN marking or to report congestion information reporting. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------------------------------------------|----------|-----------------------------------|--------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| +| ECN Marking or Congestion Information Reporting Status Item | | 1..<maxnoofQoSFlows> | | | +| >QoS Flow Identifier | M | | 9.3.1.51 | | +| >Activation Status | M | | ENUMERATED (active, not Active, ...) | Indicates whether ECN marking at NG-RAN or reporting information for ECN marking at UPF or congestion information reporting is active or not active. | + +| Range bound | Explanation | +|-----------------|-----------------------------------------------------------------------| +| maxnoofQoSFlows | Maximum no. of QoS flows allowed within one PDU session. Value is 64. | + +### 9.3.1.268 PDU Set based Handling Indicator + +This IE indicates whether PDU Set based Handling is supported for the NG-RAN node. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------|----------|-------|-----------------------------|-----------------------| +| PDU Set based Handling Indicator | M | | ENUMERATED (supported, ...) | | + +## 9.3.2 Transport Network Layer Related IEs + +### 9.3.2.1 QoS Flow per TNL Information List + +This IE is used to provide a list of additional UP transport layer information for a split PDU session, along with the associated QoS flows. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------------------|----------|----------------------------------------------------|-----------------------|-----------------------| +| QoS Flow per TNL Information Item | | 1..<maxnoofMultiConnectivityMinusOne> | | | +| >QoS Flow per TNL Information | M | | 9.3.2.8 | | + +| Range bound | Explanation | +|----------------------------------|--------------------------------------------------------------------------------------------------------------------------| +| maxnoofMultiConnectivityMinusOne | Maximum no. of connectivity allowed for a UE minus one. Value is 3. The current version of the specification supports 1. | + +### 9.3.2.2 UP Transport Layer Information + +This IE is used to provide the NG user plane transport layer information associated with a PDU session for an NG-RAN node – UPF pair. In this release it corresponds to an IP address and a GTP Tunnel Endpoint Identifier. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------------|----------|-------|------------------------------------|-----------------------| +| CHOICE UP Transport Layer Information | M | | | | +| >GTP tunnel | | | | | +| >>Endpoint IP Address | M | | Transport Layer Address
9.3.2.4 | | +| >>GTP-TEID | M | | 9.3.2.5 | | + +### 9.3.2.3 E-RAB ID + +This IE is the identifier of the LTE E-RAB. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-----------------------| +| E-RAB ID | M | | INTEGER (0..15, ...) | | + +### 9.3.2.4 Transport Layer Address + +This 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 [14]. | + +### 9.3.2.5 GTP-TEID + +This IE is the GTP Tunnel Endpoint Identifier to be used for the user plane transport between the NG-RAN node and the UPF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|------------------------|--------------------------------------------| +| GTP-TEID | M | | OCTET STRING (SIZE(4)) | For details and range, see TS 29.281 [15]. | + +### 9.3.2.6 CP Transport Layer Information + +This IE is used to provide the NG control plane transport layer information associated with an NG-RAN node – AMF pair. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------|----------|-------|---------------------------------|-----------------------|-------------|----------------------| +| CHOICE CP Transport Layer Information | | | | | - | | +| >Endpoint-IP-address | | | | | | | +| >>Endpoint IP Address | M | | Transport Layer Address 9.3.2.4 | | - | | +| >Endpoint-IP-address-and-port | | | | | YES | reject | +| >>Endpoint IP Address | M | | Transport Layer Address 9.3.2.4 | | - | | +| >>Port Number | M | | OCTET STRING (SIZE(2)) | | - | | + +### 9.3.2.7 TNL Association List + +This IE contains a list of TNL associations. It is used for example to indicate failed TNL association(s). + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------|----------|-----------------------------|----------------------------------------|-----------------------| +| TNL Association Item | | 1.. | | | +| >TNL Association Address | M | | CP Transport Layer Information 9.3.2.6 | | +| >Cause | M | | 9.3.1.2 | | + +| Range bound | Explanation | +|------------------------|-----------------------------------------------------------------------------------| +| maxnoofTNLAssociations | Maximum no. of TNL Associations between the NG-RAN node and the AMF. Value is 32. | + +### 9.3.2.8 QoS Flow per TNL Information + +This IE indicates the NG-U transport layer information and associated list of QoS flows. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------|----------|-------|-----------------------|-----------------------| +| UP Transport Layer Information | M | | 9.3.2.2 | | +| Associated QoS Flow List | M | | 9.3.1.99 | | + +### 9.3.2.9 TNL Association Usage + +This IE indicates the usage of the TNL association. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------|----------|-------|------------------------------------|----------------------------------------------------------------------------------------------------------------------------| +| 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. | + +### 9.3.2.10 TNL Address Weight Factor + +This IE indicates the weight factor of the TNL address. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TNL Address Weight Factor | M | | INTEGER (0..255) | Value 0 indicates the TNL address is not permitted for the initial NGAP message. If the value for each TNL address is the same, it indicates the deployments that rely solely on 5GC-based load balancing. | + +### 9.3.2.11 UP Transport Layer Information Pair List + +This IE is used to provide a list of uplink UP transport layer information and associated downlink UP transport layer information for a split PDU session. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------------------|----------|---------------------------------------|----------------------------------------|-----------------------| +| UP Transport Layer Information Pair Item | | 1.. | | | +| >UL NG-U UP TNL Information | M | | UP Transport Layer Information 9.3.2.2 | | +| >DL NG-U UP TNL Information | M | | UP Transport Layer Information 9.3.2.2 | | + +| Range bound | Explanation | +|----------------------------------|--------------------------------------------------------------------------------------------------------------------------| +| maxnoofMultiConnectivityMinusOne | Maximum no. of connectivity allowed for a UE minus one. Value is 3. The current version of the specification supports 1. | + +### 9.3.2.12 UP Transport Layer Information List + +This IE is used to provide a list of additional UP transport layer information for a split PDU session. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------------|----------|-------------------------------------------------------|----------------------------------------|-----------------------|-------------|----------------------| +| UP Transport Layer Information Item | | 1..oofMultiC
onnectivit
yMinusOn
e> | | | - | | +| >NG-U UP TNL Information | M | | UP Transport Layer Information 9.3.2.2 | | - | | +| >Common Network Instance | O | | 9.3.1.120 | | YES | ignore | + +| Range bound | Explanation | +|----------------------------------|--------------------------------------------------------------------------------------------------------------------------| +| maxnoofMultiConnectivityMinusOne | Maximum no. of connectivity allowed for a UE minus one. Value is 3. The current version of the specification supports 1. | + +### 9.3.2.13 QoS Flow List with Data Forwarding + +This IE is used to provide a list of QoS flows with indication if forwarding is accepted. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------|----------|------------------------------|------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| QoS Flow Item with Data Forwarding | | 1..oofQoSFl
ows> | | | - | | +| >QoS Flow Identifier | M | | 9.3.1.51 | | - | | +| >Data Forwarding Accepted | O | | 9.3.1.62 | This IE is included for the QoS flows in the PDU session to be forwarded over the PDU session forwarding tunnel. It may be included for the QoS flows in the PDU session to be forwarded over the DRB forwarding tunnel(s). | - | | +| >Current QoS Parameters Set Index | O | | Alternative QoS Parameters Set Index 9.3.1.152 | Index to the currently fulfilled alternative QoS parameters set | YES | ignore | + +| Range bound | Explanation | +|-----------------|-----------------------------------------------------------------------| +| maxnoofQoSFlows | Maximum no. of QoS flows allowed within one PDU session. Value is 64. | + +### 9.3.2.14 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.15 MBS Session TNL Information 5GC + +This IE provides 5GC TNL information for location dependent and location independent MBS sessions. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------------|----------|---------------------------------------|-----------------------|-----------------------| +| CHOICE Session Type | M | | | | +| > location independent | | | | | +| >>Shared NG-U Multicast TNL Information | M | | 9.3.2.16 | | +| > location dependent | | | | | +| >>MBS Session TNL Information 5GC List | | 1 | | | +| >>>MBS Session TNL Information 5GC Item | | 1.. | | | +| >>>>MBS Area Session ID | M | | 9.3.1.207 | | +| >>>>Shared NG-U Multicast TNL Information | M | | 9.3.2.16 | | + +| Range bound | Explanation | +|----------------------------------|------------------------------------------------------------| +| maxnoofMBSServiceAreaInformation | Maximum no. of MBS Service Area Information. Value is 256. | + +### 9.3.2.16 Shared NG-U Multicast TNL Information + +This IE provides the shared NG user plane transport layer information associated with an MBS session at the 5GC. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------|----------|-------|------------------------------------|-----------------------| +| IP Multicast Address | M | | Transport Layer Address
9.3.2.4 | | +| IP Source Address | M | | Transport Layer Address
9.3.2.4 | | +| GTP-TEID at 5GC | M | | GTP-TEID
9.3.2.5 | | + +### 9.3.2.17 MBS Session TNL Information NG-RAN + +This IE provides NG-RAN TNL information for location dependent and location independent broadcast MBS sessions. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------------------|----------|------------------------------------------------|-------------------------------------------|-----------------------| +| CHOICE Session Type | M | | | | +| > location independent | | | | | +| >>Shared NG-U Unicast TNL Information | M | | UP Transport Layer Information
9.3.2.2 | | +| > location dependent | | | | | +| >>MBS Session TNL Information NG-RAN List | | 1 | | | +| >>>MBS Session TNL Information NG-RAN Item | | 1..< maxnoofMBSServiceAreaInformation > | | | +| >>>>MBS Area Session ID | M | | 9.3.1.207 | | +| >>>>Shared NG-U Unicast TNL Information | O | | UP Transport Layer Information
9.3.2.2 | | + +| Range bound | Explanation | +|-----------------------------------------|------------------------------------------------------------| +| maxnoofMBSServiceAreaInformation | Maximum no. of MBS Service Area Information. Value is 256. | + +### 9.3.3 NAS Related IEs + +#### 9.3.3.1 AMF UE NGAP ID + +This IE uniquely identifies the UE association over the NG interface, as described in TS 38.401 [2]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------|----------|-------|---------------------------------|-----------------------| +| AMF UE NGAP ID | M | | INTEGER (0..2 40 -1) | | + +#### 9.3.3.2 RAN UE NGAP ID + +This IE uniquely identifies the UE association over the NG interface within the NG-RAN node. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------|----------|-------|---------------------------------|-----------------------| +| RAN UE NGAP ID | M | | INTEGER (0..2 32 -1) | | + +#### 9.3.3.3 GUAMI + +This IE indicates the AMF identity. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-----------------------| +| PLMN Identity | M | | 9.3.3.5 | | +| AMF Region ID | M | | BIT STRING (SIZE(8)) | | +| AMF Set ID | M | | 9.3.3.12 | | +| AMF Pointer | M | | 9.3.3.19 | | + +### 9.3.3.4 NAS-PDU + +This IE contains a 5GC – UE or UE – 5GC message that is transferred without interpretation in the NG-RAN node. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-------------------------------------------| +| NAS-PDU | M | | OCTET STRING | The content is defined in TS 24.501 [26]. | + +### 9.3.3.5 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.3.3.6 SON Configuration Transfer + +This IE contains the configuration information, used by e.g., SON functionality, and additionally includes the NG-RAN node identifier of the destination of this configuration information and the NG-RAN node identifier of the source of this information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------|-------------------------------|-------|-----------------------|-------------------------------------------------------------------------------------|-------------|----------------------| +| Target RAN Node ID SON | | 1 | | | - | | +| >Global RAN Node ID | M | | 9.3.1.5 | | - | | +| >Selected TAI | M | | TAI
9.3.3.11 | | - | | +| >NR CGI | O | | 9.3.1.7 | This IE is ignored if the SON Information IE contains the SON Information Reply IE. | YES | ignore | +| Source RAN Node ID | | 1 | | | - | | +| >Global RAN Node ID | M | | 9.3.1.5 | | - | | +| >Selected TAI | M | | TAI
9.3.3.11 | | - | | +| SON Information | M | | 9.3.3.7 | | - | | +| Xn TNL Configuration Info | C-
ifSONInformationRequest | | 9.3.3.9 | Source NG-RAN node Xn TNL Configuration Info. | - | | + +| Condition | Explanation | +|-------------------------|-------------------------------------------------------------------------------------------------------------------------------| +| ifSONInformationRequest | This IE shall be present if the SON Information IE contains the SON Information Request IE set to "Xn TNL Configuration Info" | + +### 9.3.3.7 SON Information + +This IE identifies the nature of the configuration information transferred, i.e., a request, a reply or a report. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------|----------|-------|------------------------------------------------|-----------------------|-------------|----------------------| +| CHOICE SON Information | M | | | | - | | +| >SON Information Request | | | | | | | +| >>SON Information Request | M | | ENUMERATED
(Xn TNL Configuration Info, ...) | | - | | +| >SON Information Reply | | | | | | | +| >>SON Information Reply | M | | 9.3.3.8 | | - | | +| >SON Information Report | | | | | | | +| >>SON Information Report | M | | 9.3.3.35 | | YES | ignore | + +### 9.3.3.8 SON Information Reply + +This IE contains the configuration information to be replied to the NG-RAN node. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|----------|-------|-----------------------|-----------------------| +| Xn TNL Configuration Info | O | | 9.3.3.9 | | + +### 9.3.3.9 Xn TNL Configuration Info + +This IE is used for signalling Xn TNL Configuration information for automatic Xn SCTP association establishment. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------|----------|------------------------|---------------------------------|--------------------------------------------------------------------------------------|-------------|----------------------| +| Xn Transport Layer Addresses | | 1.. | | | - | | +| >Transport Layer Address | M | | 9.3.2.4 | Transport Layer Addresses for Xn SCTP endpoint. | - | | +| Xn Extended Transport Layer Addresses | | 0.. | | | - | | +| >IP-Sec Transport Layer Address | O | | Transport Layer Address 9.3.2.4 | Transport Layer Addresses for IP-Sec endpoint. | - | | +| >Xn GTP Transport Layer Addresses | | 0.. | | | - | | +| >>GTP Transport Layer Address | M | | Transport Layer Address 9.3.2.4 | GTP Transport Layer Addresses for GTP end-points (used for data forwarding over Xn). | - | | +| >Xn SCTP Transport Layer Addresses | | 0.. | | | YES | ignore | +| >>Transport Layer Address SCTP | M | | Transport Layer Address 9.3.2.4 | Transport Layer Addresses for Xn SCTP endpoint. | - | | + +| Range bound | Explanation | +|-------------------|--------------------------------------------------------------------------------------------------| +| maxnoofXnTLAs | Maximum no. of Xn Transport Layer Addresses for an SCTP end-point. Value is 2. | +| maxnoofXnExtTLAs | Maximum no. of Xn Extended Transport Layer Addresses in the message. Value is 16. | +| maxnoofXnGTP-TLAs | Maximum no. of Xn GTP Transport Layer Addresses for a GTP end-point in the message. Value is 16. | + +### 9.3.3.10 TAC + +This IE 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.3.3.11 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.3.5 | | +| TAC | M | | 9.3.3.10 | | + +### 9.3.3.12 AMF Set ID + +This IE is used to uniquely identify an AMF Set within the AMF Region. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-----------------------| +| AMF Set ID | M | | BIT STRING (SIZE(10)) | | + +### 9.3.3.13 Routing ID + +This IE is used to identify an LMF within the 5GC. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Routing ID | M | | OCTET STRING | The maximum length is 16 octets, referring to the length of a Universally Unique Identifier (UUID) version 4 as specified in section 4.4 in IETF RFC 4122 [53] | + +### 9.3.3.14 NRPPa-PDU + +This IE contains an NG-RAN node – LMF or LMF – NG-RAN node message that is transferred without interpretation in the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-----------------------| +| NRPPa-PDU | M | | OCTET STRING | | + +### 9.3.3.15 RAN Paging Priority + +This IE contains the service priority as defined in TS 23.501 [9]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------| +| RAN Paging Priority | M | | INTEGER (1..256) | Values ordered in decreasing order of priority, i.e. with 1 as the highest priority and 256 as the lowest priority | + +### 9.3.3.16 EPS TAC + +This IE is used to uniquely identify an EPS Tracking Area Code. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|------------------------|-----------------------| +| EPS TAC | M | | OCTET STRING (SIZE(2)) | | + +### 9.3.3.17 EPS TAI + +This IE is used to uniquely identify an EPS Tracking Area. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-----------------------| +| PLMN Identity | M | | 9.3.3.5 | | +| EPS TAC | M | | 9.3.3.16 | | + +### 9.3.3.18 UE Paging Identity + +This IE represents the Identity with which the UE is paged. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------|----------|-------|-----------------------|-----------------------| +| CHOICE UE Paging Identity | M | | | | +| >5G-S-TMSI | | | | | +| >>5G-S-TMSI | M | | 9.3.3.20 | | + +### 9.3.3.19 AMF Pointer + +This IE is used to identify one or more AMF(s) within the AMF Set. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-----------------------| +| AMF Pointer | M | | BIT STRING (SIZE(6)) | | + +### 9.3.3.20 5G-S-TMSI + +This IE is used for security reasons, to hide the identity of a subscriber. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|------------------------|-----------------------------------------------------| +| AMF Set ID | M | | 9.3.3.12 | | +| AMF Pointer | M | | 9.3.3.19 | | +| 5G-TMSI | M | | OCTET STRING (SIZE(4)) | 5G-TMSI is unique within the AMF that allocated it. | + +### 9.3.3.21 AMF Name + +This IE is used to uniquely identify the AMF (see TS 38.300 [8]). It may also be used as a human readable name of the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-------------------------------------|-----------------------| +| AMF Name | M | | PrintableString (SIZE(1..150, ...)) | | + +### 9.3.3.22 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.3.23 UE Identity Index Value + +This IE is used by the NG-RAN node to calculate the Paging Frame as specified in TS 38.304 [12] and TS 36.304 [29]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------|----------|-------|-----------------------|----------------------------------------------------------| +| CHOICE UE Identity Index Value | | | | | +| >Index Length 10 | | | | | +| >>Index Length 10 | M | | BIT STRING (SIZE(10)) | Coded as specified in TS 38.304 [12] and TS 36.304 [29]. | + +### 9.3.3.24 Periodic Registration Update Timer + +This IE is used to assist NG-RAN to generate corresponding timer for periodic RNA update for RRC\_INACTIVE UEs. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Periodic Registration Update Timer | M | | BIT STRING (SIZE(8)) |

Bits 5 to 1 represent the binary coded timer value.

Bits 6 to 8 define the timer value unit for the Periodic Registration Update Timer as follows:

Bits
8 7 6

0 0 0 value is incremented in multiples of 10 minutes

0 0 1 value is incremented in multiples of 1 hour

0 1 0 value is incremented in multiples of 10 hours

0 1 1 value is incremented in multiples of 2 seconds

1 0 0 value is incremented in multiples of 30 seconds

1 0 1 value is incremented in multiples of 1 minute

1 1 1 value indicates that the timer is deactivated.

1 1 0 value is incremented in multiples of 1 hour in this version of the protocol.

| + +### 9.3.3.25 UE-associated Logical NG-connection List + +This IE contains a list of UE-associated logical NG-connections. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------------------|----------|----------------------------------|-----------------------|-----------------------| +| UE-associated Logical NG-connection Item | | 1.. | | | +| >AMF UE NGAP ID | O | | 9.3.3.1 | | +| >RAN UE NGAP ID | O | | 9.3.3.2 | | + +| Range bound | Explanation | +|-----------------------------|------------------------------------------------------------------------------------------------------| +| maxnoofNGConnectionsToReset | Maximum no. of UE-associated logical NG-connections allowed to reset in one message. Value is 65536. | + +### 9.3.3.26 NAS Security Parameters from NG-RAN + +This IE provides security related parameters for inter-system handover from NG-RAN to E-UTRAN or from NG-RAN to UTRAN via the eNB to the UE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| NAS Security Parameters from NG-RAN | M | | OCTET STRING | Refers to the N1 mode to S1 mode NAS transparent container IE, the details of the IE definition and the encoding are specified in TS 24.501 [26]. | + +### 9.3.3.27 Source to Target AMF Information Reroute + +This IE is used to transparently pass information provided by NSSF from the source AMF to the target AMF through the NG-RAN node; it is produced by the source core network node and is transmitted to the target core network node. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------|----------|-------|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Configured NSSAI | O | | OCTET STRING (SIZE(128)) | The maximum number of S-NSSAI in Configured NSSAI is 16. This IE contains optional mapping S-NSSAI. When present, this IE shall be transmitted transparent from the source Core network node to the target Core network node. The octets of the OCTET STRING are encoded according to description in TS 29.531 [30]. | +| Rejected NSSAI in PLMN | O | | OCTET STRING (SIZE(32)) | This IE contain the rejected NSSAI(s) in the PLMN. When present, this IE shall be transmitted transparent from the source Core network node to the target Core network node. The octets of the OCTET STRING are encoded according to description in TS 29.531 [30]. | +| Rejected NSSAI in TA | O | | OCTET STRING (SIZE(32)) | This IE contain the rejected NSSAI(s) in the TA. When present, this IE shall be transmitted transparent from the source Core network node to the target Core network node. The octets of the OCTET STRING are encoded according to description in TS 29.531 [30]. | + +### 9.3.3.28 RIM Information Transfer + +This IE contains information used by the RIM functionality, and additionally includes the NG-RAN node identifier of the destination of the RIM information and the NG-RAN node identifier of the source of this information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------|----------|-------|-----------------------|-----------------------| +| Target RAN Node ID RIM | | 1 | | | +| >Global RAN Node ID | M | | 9.3.1.5 | | +| >Selected TAI | M | | TAI
9.3.3.11 | | +| Source RAN Node ID | | 1 | | | +| >Global RAN Node ID | M | | 9.3.1.5 | | +| >Selected TAI | M | | TAI
9.3.3.11 | | +| RIM Information | M | | 9.3.3.29 | | + +### 9.3.3.29 RIM Information + +This IE contains the RIM information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------|----------|-------|-----------------------------------------------------|------------------------| +| Target gNB Set ID | M | | gNB Set ID
9.3.1.122 | The victim gNB Set ID. | +| RIM-RS Detection | M | | ENUMERATED
(RS detected, RS
disappeared, ...) | | + +### 9.3.3.30 LAI + +This IE is used to uniquely identify a Location Area. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------|----------|-------|---------------------------|----------------------------| +| LAI | | | | | +| >PLMN Identity | M | | 9.3.3.5 | | +| >LAC | M | | OCTET STRING
(SIZE(2)) | 0000 and FFFE not allowed. | + +### 9.3.3.31 Extended Connected Time + +This IE indicates the minimum time the RAN should keep the UE in RRC\_CONNECTED state regardless of inactivity, as defined in TS 23.501 [9]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Extended Connected Time | M | | INTEGER (0..255) | Minimum time the RAN should keep the UE in RRC_CONNECTED state. Unit is second.
Value of "0" indicates that the AMF is aware of pending data traffic, but no specific time value is requested. | + +### 9.3.3.32 End Indication + +This IE indicates that there are no further NAS PDUs to be transmitted for this UE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------|----------|-------|-----------------------------------------------------------------|-----------------------| +| End Indication | M | | ENUMERATED
(no further data,
further data exists,
...) | | + +### 9.3.3.33 Inter-system SON Configuration Transfer + +This IE contains the configuration information, used by e.g., SON functionality, transmitted between an NG-RAN node and an eNB and additionally includes the node identifier of the destination of this configuration information and the node identifier of the source of this information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------|----------|-------|-----------------------|-----------------------| +| CHOICE Transfer Type | M | | | | +| >from E-UTRAN to NG-RAN | | | | | +| >>Source eNB-ID | | 1 | | | +| >>>Global eNB ID | M | | 9.3.1.165 | | +| >>>Selected EPS TAI | M | | EPS TAI
9.3.3.17 | | +| >>Target NG-RAN node ID | | 1 | | | +| >>>Global RAN Node ID | M | | 9.3.1.5 | | +| >>>Selected TAI | M | | TAI
9.3.3.11 | | +| >from NG-RAN to E-UTRAN | | | | | +| >>Source NG-RAN Node ID | | 1 | | | +| >>>Global RAN Node ID | M | | 9.3.1.5 | | +| >>>Selected TAI | M | | TAI
9.3.3.11 | | +| >>Target eNB-ID | | 1 | | | +| >>>Global eNB ID | M | | 9.3.1.165 | | +| >>>Selected EPS TAI | M | | EPS TAI
9.3.3.17 | | +| Inter-system SON Information | M | | 9.3.3.34 | | + +### 9.3.3.34 Inter-system SON Information + +This IE identifies the nature of the configuration information transferred. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| CHOICE Inter-system SON Information | M | | | | - | | +| > Inter-system SON Information Report | | | | | | | +| >>Inter-system SON Information Report | M | | 9.3.3.36 | | - | | +| > Inter-system SON Information Request | | | | | | | +| >>Inter-system SON Information Request | M | | 9.3.3.54 | | YES | ignore | +| > Inter-system SON Information Reply | | | | | | | +| >>Inter-system SON Information Reply | M | | 9.3.3.55 | | YES | ignore | + +### 9.3.3.35 SON Information Report + +This IE contains the configuration information to be transferred. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------------------------|----------|-----------------------------------------------------------|-----------------------|-----------------------------------------------------------------------------------------|-------------|----------------------| +| CHOICE SON
Information Report | M | | | | - | | +| >Failure Indication
Information | | | | | | | +| >>Failure Indication | M | | 9.3.3.37 | | - | | +| >HO Report Information | | | | | | | +| >>HO Report | M | | 9.3.3.39 | | - | | +| >Successful HO Report
Information | | | | | | | +| >>Successful HO
Report List | | 1 | | | YES | ignore | +| >>>Successful HO
Report Item | | 1..oofSucces
sfulHORe
ports> | | | - | | +| >>>>Successful HO
Report Container | M | | OCTET STRING | Includes the
SuccessHO-
Report IE as
defined in TS
38.331 [18]. | - | | +| >Successful PSCell
Change Report
Information | | | | | YES | ignore | +| >>Successful PSCell
Change Report List | | 1 | | | - | | +| >>>Successful
PSCell Change
Report Item | | 1..oofSucces
sfulPSCell
ChangeR
eports> | | | - | | +| >>>>Successful
PSCell Change
Report Container | M | | OCTET STRING | Includes
the SuccessPSCel
l-Report IE as
defined in TS
38.331 [18]. | - | | + +| Range bound | Explanation | +|------------------------------------------|---------------------------------------------------------------| +| maxnoofSuccessfulHOReports | Maximum no. of Successful HO Reports. Value is 64. | +| maxnoofSuccessfulPSCellChangeRep
orts | Maximum no. of Successful PSCell Change Reports. Value is 64. | + +### 9.3.3.36 Inter-system SON Information Report + +This IE contains the configuration information to be transferred. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| CHOICE SON
Information Report | M | | | | - | | +| >HO Report Information | | | | | | | +| >>Inter-system HO
Report | M | | 9.3.3.40 | | - | | +| >Failure Indication
Information | | | | | | | +| >>Inter-system Failure
Indication | M | | 9.3.3.38 | | - | | +| >Energy Savings
Indication | | | | | | | +| >>Inter-system Cell
State Indication | M | | 9.3.3.57 | | YES | ignore | +| >Resource Status
Report | | | | | | | +| >>Inter-system
Resource Status
Report | M | | 9.3.3.60 | | YES | ignore | + +### 9.3.3.37 Failure Indication + +This IE contains the failure indication to be transferred. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------|----------|-------|-----------------------|-----------------------| +| UE RLF Report Container | O | | 9.3.3.41 | | + +### 9.3.3.38 Inter-system Failure Indication + +This IE contains the failure indication to be transferred. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------|----------|-------|-----------------------|------------------------------------------------------------------------| +| UE RLF Report Container | O | | 9.3.3.41 | Only contains the LTE RLF report in this version of the specification. | + +### 9.3.3.39 HO Report + +This IE contains the HO report to be transferred. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------|-------------------------------------------------------------------|-------|--------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Handover Report Type | M | | ENUMERATED
(HO too early,
HO to wrong
cell, Inter-system
ping-pong, ...) | | - | | +| Handover Cause | M | | Cause
9.3.1.2 | Indicates handover
cause employed
for handover from
source cell | - | | +| Source Cell CGI | M | | NG-RAN CGI
9.3.1.73 | NG-RAN CGI of
the source cell for
handover
procedure | - | | +| Target Cell CGI | M | | NG-RAN CGI
9.3.1.73 | NG-RAN CGI of
the target cell for
handover
procedure.
If the Handover
Report Type is set
to "Inter-system
ping-pong", it
contains the target
cell of the inter
system handover
from the other
system to NG-RAN
node cell | - | | +| Re-establishment Cell
CGI | C-
ifHandov
erReport
Type
HoToWro
ngCell | | NG-RAN CGI
9.3.1.73 | NG-RAN CGI of
the cell where UE
attempted re-
establishment or
where the UE
successfully re-
connected after the
failure | - | | +| Source Cell C-RNTI | O | | BIT STRING
(SIZE (16)) | C-RNTI allocated
at the source NG-
RAN node | - | | +| Target Cell in E-UTRAN | C-
ifHandov
erReport
Type
Intersyste
mpingpon
g | | E-UTRA CGI
9.3.1.9 | E-UTRA CGI of the
E-UTRAN target
cell for handover
procedure | - | | +| Mobility Information | O | | BIT STRING
(SIZE (16)) | This IE is not used
in the specification.
If received, the IE
is ignored. | - | | +| UE RLF Report
Container | O | | 9.3.3.41 | The UE RLF
Report Container
IE received in the
FAILURE
INDICATION
message. | - | | +| Extended Mobility
Information | O | | BIT STRING
(SIZE (32)) | Corresponds to the
Mobility | YES | ignore | + +| | | | | | | | +|--------------------|---|--|--------------------------|----------------------------------------------------------------------------------------------------------------|-----|--------| +| | | | | Information IE provided in the HANDOVER REQUEST message from the source NG-RAN node | | | +| Target Cell C-RNTI | O | | BIT STRING (SIZE (16)) | C-RNTI allocated at the target NG-RAN node. | YES | ignore | +| Time Since Failure | O | | INTEGER (0..172800, ...) | Corresponds to the TimeSinceFailure IE received from the UE in RLF Report as defined in TS 36.331 [21]. | YES | ignore | + +| Condition | Explanation | +|-----------------------------------------|-------------------------------------------------------------------------------------------------------------| +| ifHandoverReportTypeHoToWrongCell | This IE shall be present if the Handover Report Type IE is set to the value "HO to wrong cell" | +| ifHandoverReportTypeIntersystempingpong | This IE shall be present if the Handover Report Type IE is set to the value "Inter-system ping-pong" | + +### 9.3.3.40 Inter-system HO Report + +This IE contains the inter-system HO report to be transferred. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------|----------|----------------------------|-------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| CHOICE Handover Report Type | M | | | | - | | +| >Too early Inter-system HO | | | | | | | +| >>Source Cell ID | M | | E-UTRA CGI 9.3.1.9 | CGI of the source cell for the HO. | - | | +| >>Failure Cell ID | M | | NG-RAN CGI 9.3.1.73 | CGI of the target cell for the HO. | - | | +| >>UE RLF Report Container | O | | 9.3.3.41 | | - | | +| >Inter-system Unnecessary HO | | | | | | | +| >>Source Cell CGI | M | | NG-RAN CGI 9.3.1.73 | Source NR cell in NG-RAN | - | | +| >>Target Cell CGI | M | | E-UTRA CGI 9.3.1.9 | Target cell in E-UTRAN | - | | +| >>Early IRAT HO | M | | ENUMERATED (true, false, ...) | Is set to "true" if the measurement period expired due to an inter-RAT handover towards NR executed within the configured measurement duration and otherwise set to "false" | - | | +| >>Candidate Cell List | | 1 | | | - | | +| >>>Candidate Cell Item | | 1.. | | | - | | +| >>>>CHOICE Candidate Cell Type | M | | | | - | | +| >>>>>Candidate CGI | | | | | | | +| >>>>>Candidate Cell ID | M | | NR CGI 9.3.1.7 | This IE contains an NR CGI. | - | | +| >>>>>Candidate PCI | | | | | | | +| >>>>>Candidate PCI | M | | INTEGER (0..1007, ...) | This IE includes the NR Physical Cell Identifier of detected cells not included in the Candidate Cell List IE and for which an NR CGI could not be derived. | - | | +| >>>>>Candidate NR ARFCN | M | | INTEGER (0..maxNRARFCN) | RF Reference Frequency as defined in TS 38.104 [39], section 5.4.2.1. The frequency provided in this IE identifies the | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | absolute frequency position of the reference resource block (Common RB 0) of the carrier. Its lowest subcarrier is also known as Point A. | | | +| >Inter-system Mobility Failure for Voice Fallback | | | | | YES | ignore | +| >>Source Cell ID | M | | NG-RAN CGI 9.3.1.73 | CGI of the source cell for HO | - | | +| >>Failure Cell ID | M | | E-UTRA CGI 9.3.1.9 | CGI of the failure cell for HO | - | | +| >>Re-connect Cell ID | O | | E-UTRA CGI 9.3.1.9 | E-UTRA CGI of the cell where UE attempted re-establishment or where the UE successfully re-connected after the failure. | - | | +| >>UE RLF Report Container | O | | 9.3.3.41 | | - | | + +| Range bound | Explanation | +|-----------------------|----------------------------------------------| +| maxnoofCandidateCells | Maximum no. of candidate cells. Value is 32 | +| maxNRARFCN | Maximum value of NRARFCNs. Value is 3279165. | + +### 9.3.3.41 UE RLF Report Container + +This IE contains the RLF Report to be transferred. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------------| +| CHOICE RLF type | M | | | | +| >NR | | | | | +| >>NR UE RLF Report Container | M | | OCTET STRING | Includes the nr-RLF-Report contained in the UEInformationResponse message as defined in TS 38.331 [18]. | +| >LTE | | | | | +| >>LTE UE RLF Report Container | M | | OCTET STRING | Includes the RLF-Report-r9 contained in the UEInformationResponse message as defined in TS 36.331 [21] | + +### 9.3.3.42 NID + +This IE is used to identify (together with a PLMN identifier) a Stand-alone Non-Public Network. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|----------------------------| +| NID | M | | BIT STRING (SIZE(44)) | Defined in TS 23.003 [23]. | + +### 9.3.3.43 CAG ID + +This IE is used to identify (together with a PLMN identifier) a Public Network Integrated NPN. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|----------------------------| +| CAG ID | M | | BIT STRING (SIZE(32)) | Defined in TS 23.003 [23]. | + +### 9.3.3.44 NPN Support + +For SNPN, this IE identifies a supported SNPN together with the associated PLMN ID. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|----------|-------|-----------------------|-----------------------| +| CHOICE NPN Support | M | | | | +| >SNPN | | | | | +| >>NID | M | | 9.3.3.42 | | + +### 9.3.3.45 Allowed PNI-NPN List + +This IE contains information on allowed UE mobility in PNI-NPN including allowed PNI-NPNs and whether the UE is allowed to access non-CAG cells for each PLMN. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------|----------|--------------------------------|----------------------------------------------|-----------------------------------------------------------------------------------------------------| +| Allowed PNI-NPN Item | | 1.. | | | +| >PLMN Identity | M | | 9.3.3.5 | | +| >PNI-NPN Restricted | M | | ENUMERATED (restricted, not-restricted, ...) | If set to "restricted", indicates that the UE is not allowed to access non-CAG cells for this PLMN. | +| >Allowed CAG List per PLMN | | 1.. | | | +| >>CAG ID | M | | 9.3.3.43 | | + +| Range bound | Explanation | +|---------------------------|-----------------------------------------------------------------------------| +| maxnoofEPLMNs+1 | Maximum no. of equivalent PLMNs plus one serving PLMN. Value is 16. | +| maxnoofAllowedCAGsperPLMN | Maximum number of CAGs per PLMN in UE's Allowed PNI-NPN list. Value is 256. | + +### 9.3.3.46 NPN Access Information + +This IE contains information to perform access control for NPN. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------------|----------|-------|-----------------------|-----------------------| +| CHOICE NPN Access Information | M | | | | +| > PNI-NPN Access Information | | | | | +| >>Cell CAG List | M | | 9.3.3.47 | | + +### 9.3.3.47 Cell CAG List + +This IE indicates the list of CAG IDs supported by a cell. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------|----------|-------------------------|-----------------------|-----------------------| +| Cell CAG List | | 1.. | | | +| >CAG ID | M | | 9.3.3.43 | | + +| Range bound | Explanation | +|--------------------|-----------------------------------------------------------------------| +| maxnoofCAGsperCell | Maximum no. of CAGs per cell. Value is 64. Max is 12 in this release. | + +### 9.3.3.48 UL CP Security Information + +This IE contains NAS level security information to enable UE authentication by the AMF as described in TS 33.401 [27]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|----------------------------| +| UL NAS MAC | M | | BIT STRING (SIZE(16)) | Defined in TS 33.401 [27]. | +| UL NAS Count | M | | BIT STRING (SIZE(5)) | Defined in TS 33.401 [27]. | + +### 9.3.3.49 DL CP Security Information + +This IE contains NAS level security information to be forwarded to the UE as described in TS 33.401 [27]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|----------------------------| +| DL NAS MAC | M | | BIT STRING (SIZE(16)) | Defined in TS 33.401 [27]. | + +### 9.3.3.50 Configured TAC Indication + +This IE indicates that in all NR cells served by the gNB, the TAC with which this IE is associated, is only configured but not broadcast. + +NOTE: This IE is defined in accordance to the possibility foreseen in TS 38.331 [18] 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.3.51 Extended AMF Name + +This IE provides extended human readable name of the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------|----------|-------|--------------------------------------|-----------------------| +| AMF Name Visible | O | | VisibleString
(SIZE(1..150, ...)) | | +| AMF Name UTF8 | O | | UTF8String
(SIZE(1..150, ...)) | | + +### 9.3.3.52 Extended UE Identity Index Value + +This IE is used by the NG-RAN node to calculate the Paging Frame and Paging Occasion as specified in TS 36.304 [29], the Paging Frame and Paging Occasion for eDRX and the UE\_ID based subgroup ID as specified in TS 38.304 [12]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------|----------|-------|--------------------------|-----------------------| +| Extended UE Identity Index Value | M | | BIT STRING
(SIZE(16)) | | + +### 9.3.3.53 NR NTN TAI Information + +This IE contains the TAI information for NR NTN. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------------|----------|-------------------------------------|--------------------------|-------------------------------------------------------------------------------------| +| Serving PLMN | M | | PLMN Identity
9.3.3.5 | Indicates the UE's serving PLMN. | +| TAC List in NR NTN | | 1.. <maxnoofTACsinNTN> | | Includes all TAC(s) broadcast in the cell, for the UE's serving PLMN. | +| >TAC | M | | 9.3.3.10 | | +| UE Location Derived TAC in NR NTN | O | | TAC
9.3.3.10 | This IE contains TAC information derived from the actual UE location, if available. | + +| Range bound | Explanation | +|------------------|------------------------------------------------------| +| maxnoofTACsinNTN | Maximum no. of TACs broadcast per cell. Value is 12. | + +### 9.3.3.54 Inter-system SON Information Request + +This IE contains the request information to be transferred. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------------------|----------|-------|-----------------------|-----------------------| +| CHOICE Inter-system SON Information Request | M | | | | +| >NG-RAN Cell Activation | | | | | +| >>Inter-system Cell Activation Request | M | | 9.3.3.56 | | +| >Resource Status | | | | | +| >>Inter-system Resource Status Request | M | | 9.3.3.59 | | + +### 9.3.3.55 Inter-system SON Information Reply + +This IE contains the reply information to be transferred. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------------------------|----------|-------|-----------------------|-----------------------| +| CHOICE Inter-system SON Information Reply | M | | | | +| >NG-RAN Cell Activation | | | | | +| >>Inter-system Cell Activation Reply | M | | 9.3.3.58 | | +| >Resource Status | | | | | +| >>Inter-system Resource Status Reply | M | | 9.3.3.61 | | + +### 9.3.3.56 Inter-system Cell Activation Request + +This IE contains request information for inter-system Cell Activation. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------|----------|------------------------------|----------------------------|-----------------------| +| Activation ID | M | | INTEGER
(0..16384, ...) | Allocated by the eNB. | +| Cells to Activate List | | 1.. | | | +| >NG-RAN CGI | M | | 9.3.1.73 | | + +| Range bound | Explanation | +|-------------------------|---------------------------------------------------------------------------| +| maxnoofCellsInNGRANNode | Maximum no. of cells that can be served by a NG-RAN node. Value is 16384. | + +### 9.3.3.57 Inter-system Cell State Indication + +This IE contains notification information for inter-system Cell Activation and Deactivation. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------|----------|------------------------------|------------------------------------------------|-----------------------| +| Notification Cell List | | 1 | | | +| > Notification Cell Item | | 1.. | | | +| >>NG-RAN CGI | M | | 9.3.1.73 | | +| >>Notify Flag | M | | ENUMERATED
(Activated,
Deactivated, ...) | | + +| Range bound | Explanation | +|-------------------------|---------------------------------------------------------------------------| +| maxnoofCellsInNGRANNode | Maximum no. of cells that can be served by a NG-RAN node. Value is 16384. | + +### 9.3.3.58 Inter-system Cell Activation Reply + +This IE contains reply information for inter-system Cell Activation. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------|----------|------------------------------|----------------------------|-----------------------| +| Activated Cells List | | 1.. | | | +| >NG-RAN CGI | M | | 9.3.1.73 | | +| Activation ID | M | | INTEGER
(0..16384, ...) | Allocated by the eNB. | + +| Range bound | Explanation | +|-------------------------|---------------------------------------------------------------------------| +| maxnoofCellsInNGRANNode | Maximum no. of cells that can be served by a NG-RAN node. Value is 16384. | + +### 9.3.3.59 Inter-system Resource Status Request + +This IE contains information on the requested Inter-system Load Reporting reporting. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------------------|----------|-------|-------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Reporting System | M | | 9.3.1.237 | | +| Report Characteristics | M | | BITSTRING (SIZE(32)) | Each position in the bitmap indicates measurement object the receiving node is requested to report.
First Bit = Number of Active UEs,
Second Bit = RRC connections,
Third Bit = PRB.
Other bits reserved for future use. | +| CHOICE report type | M | | | | +| > Event based reporting | | | | | +| >>Inter-system Resource Threshold Low | M | | INTEGER (0..100) | Inter-system Resource Status reporting is enabled when Composite Available Capacity is above this threshold or is disabled when Composite Available Capacity is below this threshold.

The reporting node sends a report when the cell Composite Available Capacity becomes greater than or equal to the threshold. | +| >>Inter-system Resource Threshold High | M | | INTEGER (0..100) | Inter-system Resource Status reporting is enabled when Composite Available Capacity is below this threshold or is disabled when Composite Available Capacity is above this threshold.

The reporting node sends a report when the cell Composite Available Capacity becomes smaller than or equal to the threshold. | +| >>Number of Measurement Reporting Levels | M | | ENUMERATED (2, 3, 4, 5, 10, ..., 0) | The reporting node divides the cell load scale into the indicated number of reporting levels, evenly distributed on a linear scale between the Inter-system Resource Threshold Low and the Inter-system Resource Threshold High. The reporting node sends a report each time the cell load changes from one reporting level to another. If the value is "0", the IE is ignored and only the Inter-system Resource Threshold Low and the Inter-system Resource Threshold High are used as the reporting levels. | +| > Periodic Reporting | | | | | +| >>Reporting Periodicity | M | | ENUMERATED (stop, single, | Periodicity that can be used for reporting. If the value is "stop", | + +| | | | | | +|--|--|--|---------------------------------------|----------------------------------------------------------------------------------------------------------------| +| | | | 1000ms, 2000ms, 5000ms, 10000ms, ...) | the reporting node is asked to stop the periodic reporting. If the value is "single" there is only one report. | +|--|--|--|---------------------------------------|----------------------------------------------------------------------------------------------------------------| + +| Range bound | Explanation | +|----------------------|----------------------------------------------------------| +| maxnoofReportedCells | Maximum no. of cells that can be reported. Value is 256. | + +### 9.3.3.60 Inter-system Resource Status Report + +This IE contains the Inter-system load report. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------------------------|----------|---------------------------|------------------------------------------------------|-----------------------------------------------------------------------------------------------| +| CHOICE Reporting System | M | | | | +| >E-UTRAN | | | | | +| >>E-UTRAN Cell Report List | | 1 | | | +| >>>E-UTRAN Cell Report Item | | 1.. | | | +| >>>>Cell ID | M | | E-UTRA CGI 9.3.1.9 | | +| >>>>E-UTRAN Composite Available Capacity Group | M | | 9.3.1.196 | Corresponds to the Composite Available Capacity Group IE as defined in TS 36.423 [40]. | +| >>>>Number of Active UEs | O | | INTEGER (0..16777215, ...) | Corresponds to the Number of Active UEs IE as defined in TS 36.314 [49]. | +| >>>>RRC Connections | O | | INTEGER (1..65536, ...) | Corresponds to the RRC Connections IE as defined in TS 38.423 [24]. | +| >>>>E-UTRAN Radio Resource Status | O | | 9.3.1.200 | | +| >NG-RAN | | | | | +| >>NG-RAN Cell Report List | | 1 | | | +| >>>NG-RAN Cell Report Item | | 1.. | | | +| >>>>Cell ID | M | | NG-RAN CGI 9.3.1.73 | | +| >>>>NR Composite Available Capacity Group | M | | E-UTRAN Composite Available Capacity Group 9.3.1.196 | Corresponds to the Composite Available Capacity Group IE as defined in TS 36.423 [40]. | +| >>>>Number of Active UEs | O | | INTEGER (0..16777215, ...) | Corresponds to the Number of Active UEs IE as defined in TS 38.423 [24]. | +| >>>>RRC Connections | O | | INTEGER (1..65536, ...) | Corresponds to the RRC Connections IE as defined in TS 38.423 [24]. | +| >>>>NR Radio Resource Status | O | | 9.3.1.205 | | + +| Range bound | Explanation | +|----------------------|----------------------------------------------------------| +| maxnoofReportedCells | Maximum no. of cells that can be reported. Value is 256. | + +### 9.3.3.61 Inter-system Resource Status Reply + +This IE indicates for which cell(s) the inter-system load reporting was successfully initiated. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------|----------|-------|-----------------------|-----------------------| +| Reporting System | M | | 9.3.1.237 | | + +### 9.3.3.62 Hashed UE Identity Index Value + +This IE is the 13 Most Significant Bits (MSBs) of the Hashed ID defined in TS 38.304 [12] or TS 36.304 [29]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------|----------|-------|----------------------------|-----------------------| +| Hashed UE Identity Index Value | M | | BIT STRING (SIZE(13, ...)) | | + +### 9.3.3.63 Paging Policy Differentiation + +This IE provides paging policy differentiation information for a UE in RRC\_INACTIVE state. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------| +| Paging Policy Indicator | O | | INTEGER (0..7, ...) | Used for paging policy differentiation as specified in TS 23.501 [9]. | +| Allocation and Retention Priority | O | | 9.3.1.19 | | +| QoS Flow Identifier | O | | 9.3.1.51 | | +| PDU Session ID | O | | 9.3.1.50 | | +| 5QI | O | | INTEGER (0..255, ...) | Indicates the 5QI associated with the PDU session | + +### 9.3.3.64 NR Paging Long eDRX Information for RRC INACTIVE + +This IE indicates the NR Paging long eDRX parameters as defined in TS 38.304 [12]. + +| 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 [12].
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 seconds] | + +### 9.3.3.65 PNI-NPN Area Scope of MDT + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------|----------|-----------------------|-----------------------|-----------------------| +| CAG List for MDT | | 1.. | | | +| >PLMN Identity | M | | 9.3.3.5 | | +| >CAG ID | M | | 9.3.3.43 | | + +| Range bound | Explanation | +|------------------|----------------------------------------------------------| +| maxnoofCAGforMDT | Maximum no. of CAG IDs for MDT area scope. Value is 256. | + +## 9.3.4 SMF Related IEs + +### 9.3.4.1 PDU Session Resource Setup Request Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------------------------|----------|----------------------|----------------------------------------------|---------------------------------------------------------------------------------------------------------|-------------|----------------------| +| PDU Session Aggregate Maximum Bit Rate | O | | 9.3.1.102 | This IE shall be present when at least one Non-GBR QoS flow is being setup and is ignored otherwise. | YES | reject | +| UL NG-U UP TNL Information | M | | UP Transport Layer Information 9.3.2.2 | UPF endpoint of the NG-U transport bearer, for delivery of UL PDUs. | YES | reject | +| Additional UL NG-U UP TNL Information | O | | UP Transport Layer Information List 9.3.2.12 | UPF endpoint of the additional NG-U transport bearer(s), for delivery of UL PDUs for split PDU session. | YES | reject | +| Data Forwarding Not Possible | O | | 9.3.1.63 | This IE may be present in case of HANDOVER REQUEST message and is ignored otherwise. | YES | reject | +| PDU Session Type | M | | 9.3.1.52 | | YES | reject | +| Security Indication | O | | 9.3.1.27 | | YES | reject | +| Network Instance | O | | 9.3.1.113 | This IE is ignored if the Common Network Instance IE is included. | YES | reject | +| QoS Flow Setup Request List | | 1 | | | YES | reject | +| >QoS Flow Setup Request Item | | 1.. | | | - | | +| >>QoS Flow Identifier | M | | 9.3.1.51 | | - | | +| >>QoS Flow Level | M | | 9.3.1.12 | | - | | +| QoS Parameters | | | | | | | +| >>E-RAB ID | O | | 9.3.2.3 | | - | | +| >>TSC Traffic Characteristics | O | | 9.3.1.130 | Traffic pattern information associated with the QFI. Details in TS 23.501 [9]. | YES | ignore | +| >>Redundant QoS Flow Indicator | O | | 9.3.1.134 | This IE indicates whether this QoS flow is requested for the redundant transmission. | YES | ignore | +| >>ECN Marking or Congestion Information Reporting Request | O | | 9.3.1.266 | | YES | ignore | +| Common Network Instance | O | | 9.3.1.120 | | YES | ignore | +| Direct Forwarding Path Availability | O | | 9.3.1.64 | This IE may be present in case of inter-system | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------------|----------|-------|----------------------------------------------|-------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | handover and intra-system handover. | | | +| Redundant UL NG-U UP TNL Information | O | | UP Transport Layer Information 9.3.2.2 | UPF endpoint of the NG-U transport bearer, for delivery of UL PDUs for the redundant transmission. | YES | ignore | +| Additional Redundant UL NG-U UP TNL Information | O | | UP Transport Layer Information List 9.3.2.12 | UPF endpoint of the additional NG-U transport bearer(s), for delivery of redundant UL PDUs for split PDU session. | YES | ignore | +| Redundant Common Network Instance | O | | Common Network Instance 9.3.1.120 | | YES | ignore | +| Redundant PDU Session Information | O | | 9.3.1.136 | | YES | ignore | +| MBS Session Setup Request List | O | | 9.3.1.211 | | YES | ignore | +| Downlink TL Container | O | | OCTET STRING | Containing the Get Request message specified in TS 29.585 [56]. | YES | ignore | + +| Range bound | Explanation | +|-----------------|-----------------------------------------------------------------------| +| maxnoofQoSFlows | Maximum no. of QoS flows allowed within one PDU session. Value is 64. | + +### 9.3.4.2 PDU Session Resource Setup Response Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------------------|----------|-------|-------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| DL QoS Flow per TNL Information | M | | QoS Flow per TNL Information 9.3.2.8 | NG-RAN node endpoint of the NG-U transport bearer for delivery of DL PDUs, together with associated QoS flows. | - | | +| Additional DL QoS Flow per TNL Information | O | | QoS Flow per TNL Information List 9.3.2.1 | NG-RAN node endpoint of the additional NG-U transport bearer(s) for delivery of DL PDUs for split PDU session, together with associated QoS flows and corresponding to the Additional UL NG-U UP TNL Information IE in the PDU Session Resource Setup Request Transfer IE. | - | | +| Security Result | O | | 9.3.1.59 | | - | | +| QoS Flow Failed to Setup List | O | | QoS Flow List with Cause 9.3.1.13 | | - | | +| Redundant DL QoS Flow per TNL Information | O | | QoS Flow per TNL Information 9.3.2.8 | NG-RAN node endpoint of the NG-U transport bearer(s) for delivery of DL PDUs of the indicated Redundant QoS Flow(s) and corresponding to the Redundant UL NG-U UP TNL Information IE in the PDU Session Resource Setup Request Transfer IE. | YES | ignore | +| Additional Redundant DL QoS Flow per TNL Information | O | | QoS Flow per TNL Information List 9.3.2.1 | NG-RAN node endpoint of the additional NG-U transport bearer(s) for delivery of redundant DL PDUs for split PDU session, together with associated QoS flows and corresponding to | YES | ignore | + +| | | | | | | | +|--------------------------------------------------------|---|----------------------|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|-----|--------| +| | | | | the Additional Redundant UL NG-U UP TNL Information IE in the PDU Session Resource Setup Request Transfer IE. | | | +| Used RSN Information | O | | Redundant PDU Session Information 9.3.1.136 | | YES | ignore | +| Global RAN Node ID of Secondary NG-RAN Node | O | | Global RAN Node ID 9.3.1.5 | | YES | ignore | +| MBS Support Indicator | O | | 9.3.1.210 | | YES | ignore | +| MBS Session Setup Response List | O | | 9.3.1.213 | | YES | ignore | +| MBS Session Failed to Setup List | O | | 9.3.1.214 | | YES | ignore | +| QoS Flow TSC List | | 0..1 | | | YES | ignore | +| >QoS Flow TSC Item | | 1.. | | | - | | +| >>QoS Flow Identifier | M | | 9.3.1.51 | | - | | +| >>TSC Traffic Characteristics Feedback | O | | 9.3.1.257 | | - | | +| >>AN Packet Delay Budget Uplink | O | | Extended Packet Delay Budget 9.3.1.135 | Indicates the dynamic value of 5G-AN PDB in UL direction for the QoS flow as specified in TS 23.501 [9] | - | | +| Uplink TL Container | O | | OCTET STRING | Containing the Get Response message specified in TS 29.585 [56]. | YES | ignore | +| ECN Marking or Congestion Information Reporting Status | O | | 9.3.1.267 | | YES | ignore | +| PDU Set based Handling Indicator | O | | 9.3.1.268 | | YES | ignore | + +| Range bound | Explanation | +|-----------------|-----------------------------------------------------------------------| +| maxnoofQoSFlows | Maximum no. of QoS flows allowed within one PDU session. Value is 64. | + +### 9.3.4.3 PDU Session Resource Modify Request Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------|----------|--------------------------------|----------------------------------------|----------------------------------------------------------------------------------------------------|-------------|----------------------| +| PDU Session Aggregate Maximum Bit Rate | O | | 9.3.1.102 | | YES | reject | +| UL NG-U UP TNL Modify List | | 0..1 | | | YES | reject | +| > UL NG-U UP TNL Modify Item | | 1.. | | This IE(s) are included only for modification of an existing tunnel. | - | | +| >>UL NG-U UP TNL Information | M | | UP Transport Layer Information 9.3.2.2 | UPF endpoint of the NG-U transport bearer, for delivery of UL PDUs. | - | | +| >>DL NG-U UP TNL Information | M | | UP Transport Layer Information 9.3.2.2 | Identifies the NG-U transport bearer at the NG-RAN node. | - | | +| >>Redundant UL NG-U UP TNL Information | O | | UP Transport Layer Information 9.3.2.2 | UPF endpoint of the NG-U transport bearer, for delivery of UL PDUs for the redundant transmission. | YES | ignore | +| >>Redundant DL NG-U UP TNL Information | O | | UP Transport Layer Information 9.3.2.2 | Identifies the NG-U transport bearer at the NG-RAN node for the redundant transmission. | YES | ignore | +| Network Instance | O | | 9.3.1.113 | This IE is ignored if the Common Network Instance IE is included. | YES | reject | +| QoS Flow Add or Modify Request List | | 0..1 | | | YES | reject | +| > QoS Flow Add or Modify Request Item | | 1.. | | | - | | +| >>QoS Flow Identifier | M | | 9.3.1.51 | | - | | +| >>QoS Flow Level QoS Parameters | O | | 9.3.1.12 | | - | | +| >>E-RAB ID | O | | 9.3.2.3 | | - | | +| >>TSC Traffic Characteristics | O | | 9.3.1.130 | Traffic pattern information associated with the QFI. Details in TS 23.501 [9]. | YES | ignore | +| >>Redundant QoS Flow Indicator | O | | 9.3.1.134 | This IE indicates whether this QoS flow is requested for the redundant transmission. | YES | ignore | +| >>UL NG-U UP TNL Information | O | | UP Transport Layer Information 9.3.2.2 | This IE indicates the UPF endpoint of NG-U transport bearer for the QoS flow. | YES | ignore | +| >>Downlink TL Container | O | | OCTET STRING | Containing the Set Request message | YES | ignore | + +| | | | | | | | +|-----------------------------------------------------------|---|--|----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| | | | | specified in TS 29.585 [56]. | | | +| >>ECN Marking or Congestion Information Reporting Request | O | | 9.3.1.266 | | YES | ignore | +| QoS Flow to Release List | O | | QoS Flow List with Cause 9.3.1.13 | | YES | reject | +| Additional UL NG-U UP TNL Information | O | | UP Transport Layer Information List 9.3.2.12 | UPF endpoint of the additional NG-U transport bearer(s) proposed for delivery of UL PDUs for split PDU session. | YES | reject | +| Common Network Instance | O | | 9.3.1.120 | | YES | ignore | +| Additional Redundant UL NG-U UP TNL Information | O | | UP Transport Layer Information List 9.3.2.12 | UPF endpoint of the additional NG-U transport bearer(s) proposed for delivery of redundant UL PDUs for split PDU session. | YES | ignore | +| Redundant Common Network Instance | O | | Common Network Instance 9.3.1.120 | | YES | ignore | +| Redundant UL NG-U UP TNL Information | O | | UP Transport Layer Information 9.3.2.2 | UPF endpoint of the NG-U transport bearer, for delivery of UL PDUs for the redundant transmission of the Redundant QoS Flow(s). | YES | ignore | +| Security Indication | O | | 9.3.1.27 | | YES | ignore | +| MBS Session Setup or Modify Request List | O | | 9.3.1.212 | | YES | ignore | +| MBS Session To Release List | O | | 9.3.1.215 | | YES | ignore | + +| Range bound | Explanation | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------| +| maxnoofQoSFlows | Maximum no. of QoS flows allowed within one PDU session. Value is 64. | +| maxnoofMultiConnectivity | Maximum no. of connectivity allowed for a UE. Value is 4. The current version of the specification supports up to 2 connectivity. | + +### 9.3.4.4 PDU Session Resource Modify Response Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------------|----------|-----------------------|---------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| DL NG-U UP TNL Information | O | | UP Transport Layer Information 9.3.2.2 | NG-RAN node endpoint of the NG-U transport bearer, for delivery of DL PDUs. | - | | +| UL NG-U UP TNL Information | O | | UP Transport Layer Information 9.3.2.2 | Identifies the NG-U transport bearer at the 5GC node. | - | | +| QoS Flow Add or Modify Response List | | 0..1 | | | - | | +| >QoS Flow Add or Modify Response Item | | 1.. | | | - | | +| >>QoS Flow Identifier | M | | 9.3.1.51 | | - | | +| >>Current QoS Parameters Set Index | O | | Alternative QoS Parameters Set Index 9.3.1.152 | Index to the currently fulfilled alternative QoS parameters set | YES | Ignore | +| >>TSC Traffic Characteristics Feedback | O | | 9.3.1.257 | | YES | ignore | +| >>Uplink TL Container | O | | OCTET STRING | Containing the Set Response message specified in TS 29.585 [56]. | YES | ignore | +| >>DL NG-U UP TNL Information | O | | UP Transport Layer Information 9.3.2.2 | NG-RAN node endpoint of NG-U transport bearer for the QoS flow. | YES | ignore | +| >>AN Packet Delay Budget Uplink | O | | Extended Packet Delay Budget 9.3.1.135 | Indicates the dynamic value of 5G-AN PDB in UL direction for the QoS flow as specified in TS 23.501 [9]. | YES | ignore | +| Additional DL QoS Flow per TNL Information | O | | QoS Flow per TNL Information List 9.3.2.1 | NG-RAN node endpoint of the additional NG-U transport bearer(s) for delivery of DL PDUs for split PDU session, together with associated QoS flows. | - | | +| QoS Flow Failed to Add or Modify List | O | | QoS Flow List with Cause 9.3.1.13 | | - | | +| Additional NG-U UP TNL Information | O | | UP Transport Layer Information Pair List 9.3.2.11 | NG-RAN node endpoint of the NG-U transport bearer corresponding to the modified UPF endpoint received in the PDU | YES | ignore | + +| | | | | | | | +|--|--|--|--|--------------------------------------------------------------------------------------------------|--|--| +| | | | | Session Resource
Modify Request
Transfer IE in case
of PDU session
split. | | | +|--|--|--|--|--------------------------------------------------------------------------------------------------|--|--| + +| | | | | | | | +|--------------------------------------------------------|---|--|---------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| Redundant DL NG-U UP TNL Information | O | | UP Transport Layer Information 9.3.2.2 | NG-RAN node endpoint of the NG-U transport bearer, for delivery of DL PDUs for the redundant transmission. | YES | ignore | +| Redundant UL NG-U UP TNL Information | O | | UP Transport Layer Information 9.3.2.2 | Identifies the NG-U transport bearer at the 5GC node for the redundant transmission. | YES | ignore | +| Additional Redundant DL QoS Flow per TNL Information | O | | QoS Flow per TNL Information List 9.3.2.1 | NG-RAN node endpoint of the additional NG-U transport bearer(s) for delivery of redundant DL PDUs for split PDU session, together with associated QoS flows. | YES | ignore | +| Additional Redundant NG-U UP TNL Information | O | | UP Transport Layer Information Pair List 9.3.2.11 | NG-RAN node endpoint of the NG-U transport bearer for delivery of redundant DL PDUs corresponding to the modified UPF endpoint(s) received in the UL NG-U UP TNL Modify List IE of the PDU Session Resource Modify Request Transfer IE in case of PDU session split. | YES | ignore | +| Secondary RAT Usage Information | O | | 9.3.1.114 | | YES | ignore | +| MBS Support Indicator | O | | 9.3.1.210 | | YES | ignore | +| MBS Session Setup or Modify Response List | O | | MBS Session Setup Response List 9.3.1.213 | | YES | ignore | +| MBS Session Failed to Setup or Modify List | O | | MBS Session Failed to Setup List 9.3.1.214 | | YES | ignore | +| ECN Marking or Congestion Information Reporting Status | O | | 9.3.1.267 | | YES | ignore | +| PDU Set based Handling Indicator | O | | 9.3.1.268 | | YES | ignore | + +| Range bound | Explanation | +|-----------------|-----------------------------------------------------------------------| +| maxnoofQoSFlows | Maximum no. of QoS flows allowed within one PDU session. Value is 64. | + +#### 9.3.4.5 PDU Session Resource Notify Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------------------|----------|-----------------------|---------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| QoS Flow Notify List | | 0..1 | | | - | | +| >QoS Flow Notify Item | | 1.. | | | - | | +| >>QoS Flow Identifier | M | | 9.3.1.151 | | - | | +| >>Notification Cause | M | | ENUMERATED (fulfilled, not fulfilled, ...) | | - | | +| >>Current QoS Parameters Set Index | O | | Alternative QoS Parameters Set Notify Index 9.3.1.153 | Index to the currently fulfilled alternative QoS parameters set. Value 0 indicates that NG-RAN cannot even fulfil the lowest alternative parameters set. | YES | Ignore | +| >>TSC Traffic Characteristics Feedback | O | | 9.3.1.257 | | YES | ignore | +| QoS Flow Released List | O | | QoS Flow List with Cause 9.3.1.13 | | - | | +| Secondary RAT Usage Information | O | | 9.3.1.114 | | YES | ignore | +| QoS Flow Feedback List | | 0..1 | | | YES | ignore | +| >QoS Flow Feedback Item | | 1.. | | | - | | +| >>QoS Flow Identifier | M | | 9.3.1.151 | | - | | +| >>Update Feedback | O | | BIT STRING { CN PDB DL(0), CN PDB UL(1)} (SIZE(8, ...)) | Each position in the bitmap represents a QoS parameter. If a bit is set to "1", the respective parameter was not updated. If a bit is set to "0", the respective parameter was successfully updated. Bits 2-7 reserved for future use. | - | | +| >>CN Packet Delay Budget Downlink | O | | Extended Packet Delay Budget 9.3.1.135 | Indicates when the packet delay budget downlink was not updated in path switch that NG-RAN can offer this value | - | | +| >>CN Packet Delay Budget Uplink | O | | Extended Packet Delay Budget 9.3.1.135 | Indicates when the packet delay budget uplink was | - | | + +| | | | | | | | +|--|--|--|--|-------------------------------------------------------------|--|--| +| | | | | not updated in path switch that NG-RAN can offer this value | | | +|--|--|--|--|-------------------------------------------------------------|--|--| + +| Range bound | Explanation | +|-----------------|-----------------------------------------------------------------------| +| maxnoofQoSFlows | Maximum no. of QoS flows allowed within one PDU session. Value is 64. | + +#### 9.3.4.6 PDU Session Resource Modify Indication Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------------------|----------|-------|-------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| DL QoS Flow per TNL Information | M | | QoS Flow per TNL Information 9.3.2.8 | NG-RAN node endpoint of the NG-U transport bearer for delivery of DL PDUs, together with associated QoS flows. | - | | +| Additional DL QoS Flow per TNL Information | O | | QoS Flow per TNL Information List 9.3.2.1 | NG-RAN node endpoint of the additional NG-U transport bearer(s) for delivery of DL PDUs for split PDU session, together with associated QoS flows | - | | +| Secondary RAT Usage Information | O | | 9.3.1.114 | | YES | ignore | +| Security Result | O | | 9.3.1.59 | Current UP security status | YES | ignore | +| Redundant DL QoS Flow per TNL Information | O | | QoS Flow per TNL Information 9.3.2.8 | NG-RAN node endpoint of the NG-U transport bearer for delivery of DL PDUs for the redundant transmission, together with associated QoS flows. | YES | ignore | +| Additional Redundant DL QoS Flow per TNL Information | O | | QoS Flow per TNL Information List 9.3.2.1 | NG-RAN node endpoint of the additional NG-U transport bearer(s) for delivery of Redundant DL PDUs for split PDU session, together with associated QoS flows. | YES | ignore | +| Global RAN Node ID of Secondary NG-RAN Node | O | | Global RAN Node ID 9.3.1.5 | | YES | ignore | + +### 9.3.4.7 PDU Session Resource Modify Confirm Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------|----------|----------------------|---------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| QoS Flow Modify Confirm List | | 1 | | | - | | +| >QoS Flow Modify Confirm Item | | 1.. | | | - | | +| >>QoS Flow Identifier | M | | 9.3.1.51 | | - | | +| UL NG-U UP TNL Information | M | | UP Transport Layer Information 9.3.2.2 | UPF endpoint of the NG-U transport bearer corresponding to the DL QoS Flow per TNL Information IE received in the PDU Session Resource Modify Indication Transfer IE. | - | | +| Additional NG-U UP TNL Information | O | | UP Transport Layer Information Pair List 9.3.2.11 | NG-RAN node endpoint of the NG-U transport bearer indicated in the PDU Session Resource Modify Indication Transfer IE and the corresponding UPF endpoint for split PDU session. | - | | +| QoS Flow Failed to Modify List | O | | QoS Flow List with Cause 9.3.1.13 | | - | | +| Redundant UL NG-U UP TNL Information | O | | UP Transport Layer Information 9.3.2.2 | UPF endpoint of the NG-U transport bearer identified by the above redundant DL NG-U UP TNL Information IE for the redundant transmission. | YES | ignore | +| Additional Redundant NG-U UP TNL Information | O | | UP Transport Layer Information Pair List 9.3.2.11 | NG-RAN node endpoint of the NG-U transport bearer for the redundant transmission indicated in the PDU Session Resource Modify Indication Transfer IE and the corresponding UPF endpoint for split PDU session. | YES | ignore | + +| Range bound | Explanation | +|-----------------|-----------------------------------------------------------------------| +| maxnoofQoSFlows | Maximum no. of QoS flows allowed within one PDU session. Value is 64. | + +#### 9.3.4.8 Path Switch Request Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------------------|----------|-----------------------|------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| DL NG-U UP TNL Information | M | | UP Transport Layer Information 9.3.2.2 | NG-RAN node endpoint of the NG-U transport bearer, for delivery of DL PDUs. | - | | +| DL NG-U TNL Information Reused | O | | ENUMERATED (true, ...) | Indicates that DL NG-U TNL Information has been reused. | - | | +| User Plane Security Information | O | | 9.3.1.60 | | - | | +| QoS Flow Accepted List | | 1 | | QoS flows associated with the DL NG-U UP TNL Information IE. | - | | +| > QoS Flow Accepted Item | | 1.. | | | - | | +| >>QoS Flow Identifier | M | | 9.3.1.51 | | - | | +| >>Current QoS Parameters Set Index | O | | Alternative QoS Parameters Set Index 9.3.1.152 | Index to the currently fulfilled alternative QoS parameters set. | YES | ignore | +| Additional DL QoS Flow per TNL Information | O | | QoS Flow per TNL Information List 9.3.2.1 | NG-RAN node endpoint of the additional NG-U transport bearer(s) for delivery of DL PDUs for split PDU session, together with associated QoS flows. | YES | ignore | +| Redundant DL NG-U UP TNL Information | O | | UP Transport Layer Information 9.3.2.2 | NG-RAN node endpoint of the NG-U transport bearer, for delivery of redundant DL PDUs. | YES | ignore | +| Redundant DL NG-U TNL Information Reused | O | | ENUMERATED (true, ...) | Indicates that Redundant DL NG-U TNL Information has been reused. | YES | ignore | +| Additional Redundant DL QoS Flow per TNL Information | O | | QoS Flow per TNL Information List 9.3.2.1 | NG-RAN node endpoint of the additional NG-U transport bearer(s) for delivery of Redundant DL PDUs for split PDU session, together with associated QoS flows. | YES | ignore | +| Used RSN Information | O | | Redundant PDU Session Information 9.3.1.136 | | YES | ignore | +| Global RAN Node ID of | O | | Global RAN | | YES | ignore | + +| | | | | | | | +|----------------------------------|---|--|--------------------|--|-----|--------| +| Secondary NG-RAN Node | | | Node ID
9.3.1.5 | | | | +| MBS Support Indicator | O | | 9.3.1.210 | | YES | ignore | +| PDU Set based Handling Indicator | O | | 9.3.1.268 | | YES | ignore | + +| Range bound | Explanation | +|-----------------|-----------------------------------------------------------------------| +| maxnoofQoSFlows | Maximum no. of QoS flows allowed within one PDU session. Value is 64. | + +### 9.3.4.9 Path Switch Request Acknowledge Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------|----------|-----------------------|---------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| UL NG-U UP TNL Information | O | | UP Transport Layer Information 9.3.2.2 | UPF endpoint of the NG-U transport bearer corresponding to the DL NG-U UP TNL Information IE received in the Path Switch Request Transfer IE. | - | | +| Security Indication | O | | 9.3.1.27 | | - | | +| Additional NG-U UP TNL Information | O | | UP Transport Layer Information Pair List 9.3.2.11 | NG-RAN node endpoint of the NG-U transport bearer indicated in the Path Switch Request Transfer IE and the corresponding UPF endpoint for split PDU session. | YES | ignore | +| Redundant UL NG-U UP TNL Information | O | | UP Transport Layer Information 9.3.2.2 | UPF endpoint of the NG-U transport bearer, for delivery of UL PDUs for the redundant transmission. | YES | ignore | +| Additional Redundant NG-U UP TNL Information | O | | UP Transport Layer Information Pair List 9.3.2.11 | NG-RAN node endpoint of the NG-U transport bearer for the redundant transmission indicated in the Path Switch Request Transfer IE and the corresponding UPF endpoint for split PDU session. | YES | ignore | +| QoS Flow Parameters List | | 0..1 | | | YES | ignore | +| >QoS Flow Parameters Item | | 1.. | | | - | | +| >>QoS Flow Identifier | M | | 9.3.1.51 | | - | | +| >>Alternative QoS Parameters Set List | O | | 9.3.1.151 | Indicates alternative sets of QoS parameters for the QoS flow. | - | | +| >>CN Packet Delay Budget Downlink | O | | Extended Packet Delay Budget 9.3.1.135 | Core Network Packet Delay Budget is specified in TS 23.501 [9]. This IE may be present in case of GBR QoS flows | YES | ignore | + +| | | | | | | | +|---------------------------------|---|--|----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| | | | | and is ignored otherwise. | | | +| >>CN Packet Delay Budget Uplink | O | | Extended Packet Delay Budget 9.3.1.135 | Core Network Packet Delay Budget is specified in TS 23.501 [9]. This IE may be present in case of GBR QoS flows and is ignored otherwise. | YES | ignore | +| >>Burst Arrival Time Downlink | O | | Burst Arrival Time 9.3.1.133 | Indicates the downlink Burst Arrival Time of the TSC QoS flow | YES | ignore | + +| Range bound | Explanation | +|-----------------|-----------------------------------------------------------------------| +| maxnoofQoSFlows | Maximum no. of QoS flows allowed within one PDU session. Value is 64. | + +### 9.3.4.10 Handover Command Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------------|----------|-----------------------|----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| DL Forwarding UP TNL Information | O | | UP Transport Layer Information 9.3.2.2 | To deliver forwarded DL PDUs per PDU session tunnel. | - | | +| QoS Flow to be Forwarded List | | 0..1 | | | - | | +| > QoS Flow to be Forwarded Item | | 1.. | | | - | | +| >>QoS Flow Identifier | M | | 9.3.1.51 | | - | | +| Data Forwarding Response DRB List | O | | 9.3.1.77 | | - | | +| Additional DL Forwarding UP TNL Information | O | | QoS Flow per TNL Information List 9.3.2.1 | NG-RAN node endpoint to deliver forwarded DL PDUs for split PDU session tunnel, together with associated QoS flows to be forwarded. | YES | ignore | +| UL Forwarding UP TNL Information | O | | UP Transport Layer Information 9.3.2.2 | To deliver forwarded UL PDUs | YES | reject | +| Additional UL Forwarding UP TNL Information | O | | UP Transport Layer Information List 9.3.2.12 | NG-RAN node endpoint to deliver forwarded UL PDUs for split PDU session tunnel. | YES | reject | +| Data Forwarding Response E-RAB List | O | | 9.3.1.121 | | YES | ignore | +| QoS Flow Failed to Setup List | O | | QoS Flow List with Cause 9.3.1.13 | | YES | ignore | + +| Range bound | Explanation | +|-----------------|-----------------------------------------------------------------------| +| maxnoofQoSFlows | Maximum no. of QoS flows allowed within one PDU session. Value is 64. | + +### 9.3.4.11 Handover Request Acknowledge Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------------------|----------|-----------------------------------------|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| DL NG-U UP TNL Information | M | | UP Transport Layer Information 9.3.2.2 | NG-RAN node endpoint of the NG-U transport bearer, for delivery of DL PDUs. | - | | +| DL Forwarding UP TNL Information | O | | UP Transport Layer Information 9.3.2.2 | To deliver forwarded DL PDUs. | - | | +| Security Result | O | | 9.3.1.59 | | - | | +| QoS Flow Setup Response List | M | | QoS Flow List with Data Forwarding 9.3.2.13 | QoS flows associated with the DL NG-U UP TNL Information IE. | - | | +| QoS Flow Failed to Setup List | O | | QoS Flow List with Cause 9.3.1.13 | | - | | +| Data Forwarding Response DRB List | O | | 9.3.1.77 | | - | | +| Additional DL UP TNL Information for HO List | | 0..1 | | | YES | ignore | +| > Additional DL UP TNL Information for HO Item | | 1.. | | Additional DL UP TNL Information for split PDU session, in the same order as the UPF endpoint of the additional NG-U transport bearer(s) received in the Handover Request Transfer IE of the Handover Request message. | - | | +| >>Additional DL NG-U UP TNL Information | M | | UP Transport Layer Information 9.3.2.2 | NG-RAN node endpoint of the additional NG-U transport bearer for delivery of DL PDUs. | - | | +| >>Additional QoS Flow Setup Response List | M | | QoS Flow List with Data Forwarding 9.3.2.13 | QoS flows associated with the Additional DL NG-U UP TNL Information IE. | - | | +| >>Additional DL Forwarding UP TNL Information | O | | UP Transport Layer Information 9.3.2.2 | NG-RAN node endpoint to deliver forwarded DL PDUs. | - | | +| >>Additional Redundant DL NG-U UP TNL Information | O | | UP Transport Layer Information 9.3.2.2 | NG-RAN node endpoint of the additional NG-U transport bearer for delivery of redundant DL PDUs. | YES | ignore | +| UL Forwarding UP TNL | O | | UP Transport | To deliver | YES | reject | + +| | | | | | | | +|---------------------------------------------|---|--|----------------------------------------------|------------------------------------------------------------------------------------------------------------|-----|--------| +| Information | | | Layer Information 9.3.2.2 | forwarded UL PDUs | | | +| Additional UL Forwarding UP TNL Information | O | | UP Transport Layer Information List 9.3.2.12 | NG-RAN node endpoint to deliver forwarded UL PDUs for split PDU session. | YES | reject | +| Data Forwarding Response E-RAB List | O | | 9.3.1.121 | | YES | ignore | +| Redundant DL NG-U UP TNL Information | O | | UP Transport Layer Information 9.3.2.2 | NG-RAN node endpoint of the NG-U transport bearer, for delivery of DL PDUs for the redundant transmission. | YES | ignore | +| Used RSN Information | O | | Redundant PDU Session Information 9.3.1.136 | | YES | ignore | +| Global RAN Node ID of Secondary NG-RAN Node | O | | Global RAN Node ID 9.3.1.5 | | YES | ignore | +| MBS Support Indicator | O | | 9.3.1.210 | | YES | ignore | +| PDU Set based Handling Indicator | O | | 9.3.1.268 | | YES | ignore | + +| Range bound | Explanation | +|----------------------------------|--------------------------------------------------------------------------------------------------------------------------| +| maxnoofQoSFlows | Maximum no. of QoS flows allowed within one PDU session. Value is 64. | +| maxnoofMultiConnectivityMinusOne | Maximum no. of connectivity allowed for a UE minus one. Value is 3. The current version of the specification supports 1. | + +### 9.3.4.12 PDU Session Resource Release Command Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------|----------|----------------------|-----------------------|-----------------------------------------------------------------|-------------|----------------------| +| Cause | M | | 9.3.1.2 | | - | | +| QoS Flow Additional Information List | | 0..1 | | | YES | ignore | +| >QoS Flow Additional Information Item | | 1.. | | | - | | +| >>QoS Flow Identifier | M | | 9.3.1.51 | | - | | +| >>Downlink TL Container | O | | OCTET STRING | Containing the Set Request message specified in TS 29.585 [56]. | - | | + +| Range bound | Explanation | +|-----------------|-----------------------------------------------------------------------| +| maxnoofQoSFlows | Maximum no. of QoS flows allowed within one PDU session. Value is 64. | + +### 9.3.4.13 PDU Session Resource Notify Released Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Cause | M | | 9.3.1.2 | | - | | +| Secondary RAT Usage Information | O | | 9.3.1.114 | | YES | ignore | + +### 9.3.4.14 Handover Required Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------|----------|-------|-----------------------|-----------------------| +| Direct Forwarding Path Availability | O | | 9.3.1.64 | | + +### 9.3.4.15 Path Switch Request Setup Failed Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-----------------------| +| Cause | M | | 9.3.1.2 | | + +### 9.3.4.16 PDU Session Resource Setup Unsuccessful Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------|----------|-------|-----------------------|-----------------------| +| Cause | M | | 9.3.1.2 | | +| Criticality Diagnostics | O | | 9.3.1.3 | | + +### 9.3.4.17 PDU Session Resource Modify Unsuccessful Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------|----------|-------|-----------------------|-----------------------| +| Cause | M | | 9.3.1.2 | | +| Criticality Diagnostics | O | | 9.3.1.3 | | + +### 9.3.4.18 Handover Preparation Unsuccessful Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-----------------------| +| Cause | M | | 9.3.1.2 | | + +### 9.3.4.19 Handover Resource Allocation Unsuccessful Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------|----------|-------|-----------------------|-----------------------| +| Cause | M | | 9.3.1.2 | | +| Criticality Diagnostics | O | | 9.3.1.3 | | + +### 9.3.4.20 Path Switch Request Unsuccessful Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-----------------------| +| Cause | M | | 9.3.1.2 | | + +### 9.3.4.21 PDU Session Resource Release Response Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------------|----------|------------------------------|-----------------------|------------------------------------------------------------------|-------------|----------------------| +| Secondary RAT Usage Information | O | | 9.3.1.114 | | YES | ignore | +| QoS Flow Additional Information List | | 0..1 | | | YES | ignore | +| >QoS Flow Additional Information Item | | 1..oofQoSFl
ows> | | | - | | +| >>QoS Flow Identifier | M | | 9.3.1.51 | | - | | +| >>Uplink TL Container | O | | OCTET STRING | Containing the Set Response message specified in TS 29.585 [56]. | - | | + +| Range bound | Explanation | +|-----------------|-----------------------------------------------------------------------| +| maxnoofQoSFlows | Maximum no. of QoS flows allowed within one PDU session. Value is 64. | + +### 9.3.4.22 PDU Session Resource Modify Indication Unsuccessful Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-----------------------| +| Cause | M | | 9.3.1.2 | | + +### 9.3.4.23 Secondary RAT Data Usage Report Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------|----------|-------|-----------------------|-----------------------| +| Secondary RAT Usage Information | O | | 9.3.1.114 | | + +### 9.3.4.24 UE Context Resume Request Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------|----------|-------|--------------------------------------|-----------------------| +| QoS Flow Failed to Resume List | O | | QoS Flow List with Cause
9.3.1.13 | | + +### 9.3.4.25 UE Context Resume Response Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------|----------|-------|--------------------------------------|-----------------------| +| QoS Flow Failed to Resume List | O | | QoS Flow List with Cause
9.3.1.13 | | + +### 9.3.4.26 UE Context Suspend Request Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------|----------|-------|---------------------------|-----------------------| +| Suspend Indicator | O | | ENUMERATED
(true, ...) | | + +## 9.3.5 MB-SMF Related IEs + +### 9.3.5.1 Void + +### 9.3.5.2 Void + +### 9.3.5.3 MBS Session Setup or Modification Request Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------------|----------|----------------------|--------------------------------------------|-----------------------|-------------|----------------------| +| MBS Session TNL Information 5GC | O | | 9.3.2.15 | | YES | reject | +| MBS QoS Flows To Be Setup or Modified List | M | | MBS QoS Flows To Be Setup List 9.3.1.236 | | YES | reject | +| MBS Session FSA ID List | | 0.. | | | YES | ignore | +| >MBS Frequency Selection Area Identity | M | | OCTET STRING (SIZE(3)) | | - | | +| Supported UE Type List | | 0.. | | | YES | ignore | +| >Supported UE Type | M | | ENUMERATED (Non-RedCap UE, RedCap UE, ...) | | - | | + +| Range bound | Explanation | +|--------------------|-----------------------------------------------------------------------| +| maxnoofMBSQoSFlows | Maximum no. of QoS Flows allowed within one MBS session. Value is 64. | +| maxnoofMBSFSAs | Maximum no. of FSA IDs for one MBS session. Value is 64. | +| maxnoofUETypes | Maximum no. of associated UE types. Value is 8. | + +### 9.3.5.4 Void + +### 9.3.5.5 MBS Session Setup or Modification Response Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------------|----------|-------|-----------------------|-----------------------| +| MBS Session TNL Information NG-RAN | O | | 9.3.2.17 | | + +### 9.3.5.6 MBS Session Setup or Modification Failure Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------|----------|-------|-----------------------|-----------------------| +| Cause | M | | 9.3.1.2 | | +| Criticality Diagnostics | O | | 9.3.1.3 | | + +### 9.3.5.7 MBS Distribution Setup Request Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------|----------|-------|-------------------------------------------|-----------------------------------------------------------------------------| +| MBS Session ID | M | | 9.3.1.206 | | +| MBS Area Session ID | O | | 9.3.1.207 | | +| Shared NG-U Unicast TNL Information | O | | UP Transport Layer Information
9.3.2.2 | NG-RAN node endpoint of the NG-U transport bearer, for delivery of DL PDUs. | + +### 9.3.5.8 MBS Distribution Setup Response Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------|----------|-------|-----------------------|-----------------------| +| MBS Session ID | M | | 9.3.1.206 | | +| MBS Area Session ID | O | | 9.3.1.207 | | +| Shared NG-U Multicast TNL Information | O | | 9.3.2.16 | | +| MBS QoS Flows To Be Setup List | M | | 9.3.1.236 | | +| MBS Session Status | M | | 9.3.1.217 | | +| MBS Service Area | O | | 9.3.1.208 | | + +| Range bound | Explanation | +|--------------------|-----------------------------------------------------------------------| +| maxnoofMBSQoSFlows | Maximum no. of QoS Flows allowed within one MBS session. Value is 64. | + +### 9.3.5.9 MBS Distribution Setup Unsuccessful Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------|----------|-------|-----------------------|-----------------------| +| MBS Session ID | M | | 9.3.1.206 | | +| MBS Area Session ID | O | | 9.3.1.207 | | +| Cause | M | | 9.3.1.2 | | +| Criticality Diagnostics | O | | 9.3.1.3 | | + +### 9.3.5.10 MBS Distribution Release Request Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------|----------|-------|-------------------------------------------|-----------------------------------------------------------------------------| +| MBS Session ID | M | | 9.3.1.206 | | +| MBS Area Session ID | O | | 9.3.1.207 | | +| Shared NG-U Unicast TNL Information | O | | UP Transport Layer Information
9.3.2.2 | NG-RAN node endpoint of the NG-U transport bearer, for delivery of DL PDUs. | +| Cause | M | | 9.3.1.2 | | + +### 9.3.5.11 Multicast Session Activation Request Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------|----------|-------|-----------------------|-----------------------| +| MBS Session ID | M | | 9.3.1.206 | | + +### 9.3.5.12 Multicast Session Deactivation Request Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------|----------|-------|-----------------------|-----------------------| +| MBS Session ID | M | | 9.3.1.206 | | + +### 9.3.5.13 Multicast Session Update Request Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------------|----------|-------|------------------------------------------|-------------------------------------------------------------------------------------|-------------|----------------------| +| MBS Session ID | M | | 9.3.1.206 | | YES | reject | +| MBS Service Area | O | | 9.3.1.208 | | YES | reject | +| MBS QoS Flows To Be Setup or Modified List | O | | MBS QoS Flows To Be Setup List 9.3.1.236 | | YES | reject | +| MBS QoS Flow To Release List | O | | QoS Flow List with Cause 9.3.1.13 | This IE indicates the MBS QoS flow Identifiers of the MBS QoS flows to be released. | YES | reject | +| MBS Session TNL Information 5GC | O | | 9.3.2.15 | | YES | reject | + +| Range bound | Explanation | +|--------------------|-----------------------------------------------------------------------| +| maxnoofMBSQoSFlows | Maximum no. of QoS Flows allowed within one MBS session. Value is 64. | + +### 9.3.5.14 MBS Session Release Response Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------------|----------|-------|-----------------------|-----------------------| +| MBS Session TNL Information NG-RAN | O | | 9.3.2.17 | | + +### 9.3.5.15 Broadcast Transport Request Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------------|----------|-------|-----------------------|-----------------------| +| MBS Session ID | M | | 9.3.1.206 | | +| MBS Session TNL Information NG-RAN | M | | 9.3.2.17 | | + +### 9.3.5.16 Broadcast Transport Response Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------|----------|-------|-----------------------|-----------------------| +| MBS Session ID | M | | 9.3.1.206 | | + +### 9.3.5.17 Broadcast Transport Failure Transfer + +This IE is transparent to the AMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------|----------|-------|-----------------------|-----------------------| +| MBS Session ID | M | | 9.3.1.206 | | +| Cause | M | | 9.3.1.2 | | +| Criticality Diagnostics | O | | 9.3.1.3 | | + +## 9.4 Message and Information Element Abstract Syntax (with ASN.1) + +### 9.4.1 General + +NGAP ASN.1 definition conforms to ITU-T Rec. X.691 [4], ITU-T Rec. X.680 [5] and ITU-T Rec. X.681 [6]. + +The ASN.1 definition specifies the structure and content of NGAP messages. NGAP 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 NGAP 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 NGAP message that is not constructed as defined above is received, this shall be considered as Abstract Syntax Error, and the message shall be handled as defined for Abstract Syntax Error in subclause 10.3.6. + +## 9.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 + +-- + +-- \*\*\*\*\* + +NGAP-PDU-Descriptions { + +itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + +ngran-Access (22) modules (3) ngap (1) version1 (1) ngap-PDU-Descriptions (0)} + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- \*\*\*\*\* + +-- + +-- IE parameter types from other modules. + +-- + +-- \*\*\*\*\* + +IMPORTS + +3GPP + +Criticality, +ProcedureCode +FROM NGAP-CommonDataTypes + +AMFConfigurationUpdate, +AMFConfigurationUpdateAcknowledge, +AMFConfigurationUpdateFailure, +AMFPCRelocationIndication, +AMFStatusIndication, +BroadcastSessionModificationFailure, +BroadcastSessionModificationRequest, +BroadcastSessionModificationResponse, +BroadcastSessionReleaseRequest, +BroadcastSessionReleaseRequired, +BroadcastSessionReleaseResponse, +BroadcastSessionSetupFailure, +BroadcastSessionSetupRequest, +BroadcastSessionSetupResponse, +BroadcastSessionTransportFailure, +BroadcastSessionTransportRequest, +BroadcastSessionTransportResponse, +CellTrafficTrace, + +ConnectionEstablishmentIndication, +DeactivateTrace, +DistributionReleaseRequest, +DistributionReleaseResponse, +DistributionSetupFailure, +DistributionSetupRequest, +DistributionSetupResponse, +DownlinkNASTransport, +DownlinkNonUEAssociatedNRPPaTransport, +DownlinkRANConfigurationTransfer, +DownlinkRANEarlyStatusTransfer, +DownlinkRANStatusTransfer, +DownlinkUEAssociatedNRPPaTransport, +ErrorIndication, +HandoverCancel, +HandoverCancelAcknowledge, +HandoverCommand, +HandoverFailure, +HandoverNotify, +HandoverPreparationFailure, +HandoverRequest, +HandoverRequestAcknowledge, +HandoverRequired, + +HandoverSuccess, +InitialContextSetupFailure, +InitialContextSetupRequest, +InitialContextSetupResponse, +InitialUEMessage, +LocationReport, +LocationReportingControl, +LocationReportingFailureIndication, +MTCommunicationHandlingRequest, +MTCommunicationHandlingResponse, +MTCommunicationHandlingFailure, +MulticastSessionActivationFailure, +MulticastSessionActivationRequest, +MulticastSessionActivationResponse, +MulticastSessionDeactivationRequest, +MulticastSessionDeactivationResponse, +MulticastSessionUpdateFailure, +MulticastSessionUpdateRequest, +MulticastSessionUpdateResponse, +MulticastGroupPaging, +NASNonDeliveryIndication, +NGReset, +NGResetAcknowledge, + +NGSetupFailure, +NGSetupRequest, +NGSetupResponse, +OverloadStart, +OverloadStop, +Paging, +PathSwitchRequest, +PathSwitchRequestAcknowledge, +PathSwitchRequestFailure, +PDUSessionResourceModifyConfirm, +PDUSessionResourceModifyIndication, +PDUSessionResourceModifyRequest, +PDUSessionResourceModifyResponse, +PDUSessionResourceNotify, +PDUSessionResourceReleaseCommand, +PDUSessionResourceReleaseResponse, +PDUSessionResourceSetupRequest, +PDUSessionResourceSetupResponse, +PrivateMessage, +PWSCancelRequest, +PWSCancelResponse, +PWSFailureIndication, +PWSRestartIndication, + +RANConfigurationUpdate, +RANConfigurationUpdateAcknowledge, +RANConfigurationUpdateFailure, +RANCPRelocationIndication, +RANPagingRequest, +RerouteNASRequest, +RetrieveUEInformation, +RRCInactiveTransitionReport, +SecondaryRATDataUsageReport, +TimingSynchronisationStatusRequest, +TimingSynchronisationStatusResponse, +TimingSynchronisationStatusFailure, +TimingSynchronisationStatusReport, +TraceFailureIndication, +TraceStart, +UEContextModificationFailure, +UEContextModificationRequest, +UEContextModificationResponse, +UEContextReleaseCommand, +UEContextReleaseComplete, +UEContextReleaseRequest, +UEContextResumeRequest, +UEContextResumeResponse, + +UEContextResumeFailure, +UEContextSuspendRequest, +UEContextSuspendResponse, +UEContextSuspendFailure, +UEInformationTransfer, +UERadioCapabilityCheckRequest, +UERadioCapabilityCheckResponse, +UERadioCapabilityIDMappingRequest, +UERadioCapabilityIDMappingResponse, +UERadioCapabilityInfoIndication, +UETNLABindingReleaseRequest, +UplinkNASTransport, +UplinkNonUEAssociatedNRPPaTransport, +UplinkRANConfigurationTransfer, +UplinkRANEarlyStatusTransfer, +UplinkRANStatusTransfer, +UplinkUEAssociatedNRPPaTransport, +WriteReplaceWarningRequest, +WriteReplaceWarningResponse, +UplinkRIMInformationTransfer, +DownlinkRIMInformationTransfer + +FROM NGAP-PDU-Contents + +id-AMFConfigurationUpdate, +id-AMFCPRelocationIndication, +id-AMFStatusIndication, +id-BroadcastSessionModification, +id-BroadcastSessionRelease, +id-BroadcastSessionReleaseRequired, +id-BroadcastSessionSetup, +id-BroadcastSessionTransport, +id-CellTrafficTrace, +id-ConnectionEstablishmentIndication, +id-DeactivateTrace, +id-DistributionRelease, +id-DistributionSetup, +id-DownlinkNASTransport, +id-DownlinkNonUEAssociatedNRPPaTransport, +id-DownlinkRANConfigurationTransfer, +id-DownlinkRANEarlyStatusTransfer, +id-DownlinkRANStatusTransfer, +id-DownlinkRIMInformationTransfer, +id-DownlinkUEAssociatedNRPPaTransport, +id-ErrorIndication, + +id-HandoverCancel, +id-HandoverNotification, +id-HandoverPreparation, +id-HandoverResourceAllocation, +id-HandoverSuccess, +id-InitialContextSetup, +id-InitialUEMessage, +id-LocationReport, +id-LocationReportingControl, +id-LocationReportingFailureIndication, +id-MTCommunicationHandling, +id-MulticastGroupPaging, +id-MulticastSessionActivation, +id-MulticastSessionDeactivation, +id-MulticastSessionUpdate, +id-NASNonDeliveryIndication, +id-NGReset, +id-NGSetup, +id-OverloadStart, +id-OverloadStop, +id-Paging, +id-PathSwitchRequest, +id-PDUSessionResourceModify, + +id-PDUSessionResourceModifyIndication, +id-PDUSessionResourceNotify, +id-PDUSessionResourceRelease, +id-PDUSessionResourceSetup, +id-PrivateMessage, +id-PWSCancel, +id-PWSFailureIndication, +id-PWSRestartIndication, +id-RANConfigurationUpdate, +id-RANCPRelocationIndication, +id-RANPagingRequest, +id-RerouteNASRequest, +id-RetrieveUEInformation, +id-RRCInactiveTransitionReport, +id-SecondaryRATDataUsageReport, +id-TimingSynchronisationStatus, +id-TimingSynchronisationStatusReport, +id-TraceFailureIndication, +id-TraceStart, +id-UEContextModification, +id-UEContextRelease, +id-UEContextReleaseRequest, +id-UEContextResume, + +``` + +id-UEContextSuspend, +id-UEInformationTransfer, +id-UERadioCapabilityCheck, +id-UERadioCapabilityIDMapping, +id-UERadioCapabilityInfoIndication, +id-UETNLBindingRelease, +id-UplinkNASTransport, +id-UplinkNonUEAssociatedNRPPaTransport, +id-UplinkRANConfigurationTransfer, +id-UplinkRANEarlyStatusTransfer, +id-UplinkRANStatusTransfer, +id-UplinkRIMInformationTransfer, +id-UplinkUEAssociatedNRPPaTransport, +id-WriteReplaceWarning + +``` + +FROM NGAP-Constants; + +``` + +-- ***** +-- +-- Interface Elementary Procedure Class +-- +-- ***** + +``` + +``` + +NGAP-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 +-- +-- ***** + +``` + +``` +NGAP-PDU ::= CHOICE { + initiatingMessage InitiatingMessage, + successfulOutcome SuccessfulOutcome, + unsuccessfulOutcome UnsuccessfulOutcome, + ... +} + +InitiatingMessage ::= SEQUENCE { + procedureCode NGAP-ELEMENTARY-PROCEDURE.&procedureCode ({NGAP-ELEMENTARY-PROCEDURES}), + criticality NGAP-ELEMENTARY-PROCEDURE.&criticality ({NGAP-ELEMENTARY-PROCEDURES}{@procedureCode}), + value NGAP-ELEMENTARY-PROCEDURE.&InitiatingMessage ({NGAP-ELEMENTARY-PROCEDURES}{@procedureCode}) +} + +SuccessfulOutcome ::= SEQUENCE { + procedureCode NGAP-ELEMENTARY-PROCEDURE.&procedureCode ({NGAP-ELEMENTARY-PROCEDURES}), + criticality NGAP-ELEMENTARY-PROCEDURE.&criticality ({NGAP-ELEMENTARY-PROCEDURES}{@procedureCode}), + value NGAP-ELEMENTARY-PROCEDURE.&SuccessfulOutcome ({NGAP-ELEMENTARY-PROCEDURES}{@procedureCode}) +} + +UnsuccessfulOutcome ::= SEQUENCE { + procedureCode NGAP-ELEMENTARY-PROCEDURE.&procedureCode ({NGAP-ELEMENTARY-PROCEDURES}), + criticality NGAP-ELEMENTARY-PROCEDURE.&criticality ({NGAP-ELEMENTARY-PROCEDURES}{@procedureCode}), + value NGAP-ELEMENTARY-PROCEDURE.&UnsuccessfulOutcome ({NGAP-ELEMENTARY-PROCEDURES}{@procedureCode}) +} +``` + +``` +} + +-- ***** +-- +-- Interface Elementary Procedure List +-- +-- ***** +``` + +``` +NGAP-ELEMENTARY-PROCEDURES NGAP-ELEMENTARY-PROCEDURE ::= { + NGAP-ELEMENTARY-PROCEDURES-CLASS-1 | + NGAP-ELEMENTARY-PROCEDURES-CLASS-2, + ... +} +``` + +``` +NGAP-ELEMENTARY-PROCEDURES-CLASS-1 NGAP-ELEMENTARY-PROCEDURE ::= { + aMfConfigurationUpdate | + broadcastSessionModification | + broadcastSessionRelease | + broadcastSessionSetup | + broadcastSessionTransport | + distributionSetup | + distributionRelease | + handoverCancel | +``` + +| | | +|------------------------------------|--| +| handoverPreparation | | +| handoverResourceAllocation | | +| initialContextSetup | | +| mtCommunicationHandling | | +| multicastSessionActivation | | +| multicastSessionDeactivation | | +| multicastSessionUpdate | | +| ngReset | | +| ngSetup | | +| pathSwitchRequest | | +| pDUSessionResourceModify | | +| pDUSessionResourceModifyIndication | | +| pDUSessionResourceRelease | | +| pDUSessionResourceSetup | | +| pWSCancel | | +| rANConfigurationUpdate | | +| timingSynchronisationStatus | | +| uEContextModification | | +| uEContextRelease | | +| uEContextResume | | +| uEContextSuspend | | +| uERadioCapabilityCheck | | +| uERadioCapabilityIDMapping | | + +``` + writeReplaceWarning + , + ... + } + + NGAP-ELEMENTARY-PROCEDURES-CLASS-2 NGAP-ELEMENTARY-PROCEDURE ::= { + aMFCPRelocationIndication | + aMFStatusIndication | + broadcastSessionReleaseRequired | + cellTrafficTrace | + connectionEstablishmentIndication | + deactivateTrace | + downlinkNASTransport | + downlinkNonUEAssociatedNRPPaTransport | + downlinkRANConfigurationTransfer | + downlinkRANEarlyStatusTransfer | + downlinkRANStatusTransfer | + downlinkRIMInformationTransfer | + downlinkUEAssociatedNRPPaTransport | + errorIndication | + handoverNotification | + handoverSuccess | + initialUEMessage | + locationReport | +``` + +| | | +|------------------------------------|--| +| locationReportingControl | | +| locationReportingFailureIndication | | +| multicastGroupPaging | | +| nASNonDeliveryIndication | | +| overloadStart | | +| overloadStop | | +| paging | | +| pDUSessionResourceNotify | | +| privateMessage | | +| pWSFailureIndication | | +| pWSRestartIndication | | +| rANCPRelocationIndication | | +| rANPagingRequest | | +| rerouteNASRequest | | +| retrieveUEInformation | | +| rRCInactiveTransitionReport | | +| secondaryRATDataUsageReport | | +| timingSynchronisationStatusReport | | +| traceFailureIndication | | +| traceStart | | +| uEContextReleaseRequest | | +| uEInformationTransfer | | +| uERadioCapabilityInfoIndication | | + +``` + + uETNLABindingRelease | + uplinkNASTransport | + uplinkNonUEAssociatedNRPPaTransport | + uplinkRANConfigurationTransfer | + uplinkRANEarlyStatusTransfer | + uplinkRANStatusTransfer | + uplinkRIMInformationTransfer | + uplinkUEAssociatedNRPPaTransport | + ... +} + +-- ***** +-- +-- Interface Elementary Procedures +-- +-- ***** + +aMFConfigurationUpdate NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE AMFConfigurationUpdate + SUCCESSFUL OUTCOME AMFConfigurationUpdateAcknowledgement + UNSUCCESSFUL OUTCOME AMFConfigurationUpdateFailure + PROCEDURE CODE id-AMFConfigurationUpdate +} + +``` + +``` + CRITICALITY reject + } + + aMFCPRelocationIndication NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE AMFCPRelocationIndication + PROCEDURE CODE id-AMFCPRelocationIndication + CRITICALITY reject + } + + aMFStatusIndication NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE AMFStatusIndication + PROCEDURE CODE id-AMFStatusIndication + CRITICALITY ignore + } + + broadcastSessionModification NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE BroadcastSessionModificationRequest + SUCCESSFUL OUTCOME BroadcastSessionModificationResponse + UNSUCCESSFUL OUTCOME BroadcastSessionModificationFailure + PROCEDURE CODE id-BroadcastSessionModification + CRITICALITY reject + } +``` + +``` +broadcastSessionRelease NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE BroadcastSessionReleaseRequest + SUCCESSFUL OUTCOME BroadcastSessionReleaseResponse + PROCEDURE CODE id-BroadcastSessionRelease + CRITICALITY reject +} + +broadcastSessionReleaseRequired NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE BroadcastSessionReleaseRequired + PROCEDURE CODE id-BroadcastSessionReleaseRequired + CRITICALITY reject +} + +broadcastSessionSetup NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE BroadcastSessionSetupRequest + SUCCESSFUL OUTCOME BroadcastSessionSetupResponse + UNSUCCESSFUL OUTCOME BroadcastSessionSetupFailure + PROCEDURE CODE id-BroadcastSessionSetup + CRITICALITY reject +} + +broadcastSessionTransport NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE BroadcastSessionTransportRequest +``` + +``` + SUCCESSFUL OUTCOME BroadcastSessionTransportResponse + UNSUCCESSFUL OUTCOME BroadcastSessionTransportFailure + PROCEDURE CODE id-BroadcastSessionTransport + CRITICALITY reject +} + +cellTrafficTrace NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE CellTrafficTrace + PROCEDURE CODE id-CellTrafficTrace + CRITICALITY ignore +} + +connectionEstablishmentIndication NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE ConnectionEstablishmentIndication + PROCEDURE CODE id-ConnectionEstablishmentIndication + CRITICALITY reject +} + +deactivateTrace NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE DeactivateTrace + PROCEDURE CODE id-DeactivateTrace + CRITICALITY ignore +} +``` + +``` +distributionSetup NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE DistributionSetupRequest + SUCCESSFUL OUTCOME DistributionSetupResponse + UNSUCCESSFUL OUTCOME DistributionSetupFailure + PROCEDURE CODE id-DistributionSetup + CRITICALITY reject +} + +distributionRelease NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE DistributionReleaseRequest + SUCCESSFUL OUTCOME DistributionReleaseResponse + PROCEDURE CODE id-DistributionRelease + CRITICALITY reject +} + +downlinkNASTransport NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE DownlinkNASTransport + PROCEDURE CODE id-DownlinkNASTransport + CRITICALITY ignore +} + +downlinkNonUEAssociatedNRPPaTransport NGAP-ELEMENTARY-PROCEDURE ::= { +``` + +``` + INITIATING MESSAGE DownlinkNonUEAssociatedNRPPaTransport + PROCEDURE CODE id-DownlinkNonUEAssociatedNRPPaTransport + CRITICALITY ignore +} + +downlinkRANConfigurationTransfer NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE DownlinkRANConfigurationTransfer + PROCEDURE CODE id-DownlinkRANConfigurationTransfer + CRITICALITY ignore +} + +downlinkRANEarlyStatusTransfer NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE DownlinkRANEarlyStatusTransfer + PROCEDURE CODE id-DownlinkRANEarlyStatusTransfer + CRITICALITY ignore +} + +downlinkRANStatusTransfer NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE DownlinkRANStatusTransfer + PROCEDURE CODE id-DownlinkRANStatusTransfer + CRITICALITY ignore +} +``` + +``` +downlinkUEAssociatedNRPPaTransport NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE DownlinkUEAssociatedNRPPaTransport + PROCEDURE CODE id-DownlinkUEAssociatedNRPPaTransport + CRITICALITY ignore +} + +errorIndication NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE ErrorIndication + PROCEDURE CODE id-ErrorIndication + CRITICALITY ignore +} + +handoverCancel NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE HandoverCancel + SUCCESSFUL OUTCOME HandoverCancelAcknowledge + PROCEDURE CODE id-HandoverCancel + CRITICALITY reject +} + +handoverNotification NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE HandoverNotify + PROCEDURE CODE id-HandoverNotification + CRITICALITY ignore +} +``` + +} + +handoverPreparation NGAP-ELEMENTARY-PROCEDURE ::= { + +    INITIATING MESSAGE       HandoverRequired +    SUCCESSFUL OUTCOME      HandoverCommand +    UNSUCCESSFUL OUTCOME   HandoverPreparationFailure +    PROCEDURE CODE          id-HandoverPreparation +    CRITICALITY             reject + +} + +handoverResourceAllocation NGAP-ELEMENTARY-PROCEDURE ::= { + +    INITIATING MESSAGE       HandoverRequest +    SUCCESSFUL OUTCOME      HandoverRequestAcknowledge +    UNSUCCESSFUL OUTCOME   HandoverFailure +    PROCEDURE CODE          id-HandoverResourceAllocation +    CRITICALITY             reject + +} + +handoverSuccess NGAP-ELEMENTARY-PROCEDURE ::= { + +    INITIATING MESSAGE       HandoverSuccess +    PROCEDURE CODE          id-HandoverSuccess +    CRITICALITY             ignore + +} + +``` +initialContextSetup NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE InitialContextSetupRequest + SUCCESSFUL OUTCOME InitialContextSetupResponse + UNSUCCESSFUL OUTCOME InitialContextSetupFailure + PROCEDURE CODE id-InitialContextSetup + CRITICALITY reject +} +``` + +``` +initialUEMessage NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE InitialUEMessage + PROCEDURE CODE id-InitialUEMessage + CRITICALITY ignore +} +``` + +``` +locationReport NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE LocationReport + PROCEDURE CODE id-LocationReport + CRITICALITY ignore +} +``` + +``` +locationReportingControl NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE LocationReportingControl +} +``` + +``` + PROCEDURE CODE id-LocationReportingControl + CRITICALITY ignore + } + + locationReportingFailureIndication NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE LocationReportingFailureIndication + PROCEDURE CODE id-LocationReportingFailureIndication + CRITICALITY ignore + } + + mTCommunicationHandling NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE MTCommunicationHandlingRequest + SUCCESSFUL OUTCOME MTCommunicationHandlingResponse + UNSUCCESSFUL OUTCOME MTCommunicationHandlingFailure + PROCEDURE CODE id-MTCommunicationHandling + CRITICALITY reject + } + + multicastSessionActivation NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE MulticastSessionActivationRequest + SUCCESSFUL OUTCOME MulticastSessionActivationResponse + UNSUCCESSFUL OUTCOME MulticastSessionActivationFailure + PROCEDURE CODE id-MulticastSessionActivation + } +``` + +``` + CRITICALITY reject + } + + multicastSessionDeactivation NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE MulticastSessionDeactivationRequest + SUCCESSFUL OUTCOME MulticastSessionDeactivationResponse + PROCEDURE CODE id-MulticastSessionDeactivation + CRITICALITY reject + } + + multicastSessionUpdate NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE MulticastSessionUpdateRequest + SUCCESSFUL OUTCOME MulticastSessionUpdateResponse + UNSUCCESSFUL OUTCOME MulticastSessionUpdateFailure + PROCEDURE CODE id-MulticastSessionUpdate + CRITICALITY reject + } + + multicastGroupPaging NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE MulticastGroupPaging + PROCEDURE CODE id-MulticastGroupPaging + CRITICALITY ignore + } +``` + +``` +nASNonDeliveryIndication NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE NASNonDeliveryIndication + PROCEDURE CODE id-NASNonDeliveryIndication + CRITICALITY ignore +} + +nGReset NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE NGReset + SUCCESSFUL OUTCOME NGResetAcknowledge + PROCEDURE CODE id-NGReset + CRITICALITY reject +} + +nGSetup NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE NGSetupRequest + SUCCESSFUL OUTCOME NGSetupResponse + UNSUCCESSFUL OUTCOME NGSetupFailure + PROCEDURE CODE id-NGSetup + CRITICALITY reject +} + +overloadStart NGAP-ELEMENTARY-PROCEDURE ::= { +``` + +``` + INITIATING MESSAGE OverloadStart + PROCEDURE CODE id-OverloadStart + CRITICALITY ignore +} + +overloadStop NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE OverloadStop + PROCEDURE CODE id-OverloadStop + CRITICALITY reject +} + +paging NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Paging + PROCEDURE CODE id-Paging + CRITICALITY ignore +} + +pathSwitchRequest NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PathSwitchRequest + SUCCESSFUL OUTCOME PathSwitchRequestAcknowledge + UNSUCCESSFUL OUTCOME PathSwitchRequestFailure + PROCEDURE CODE id-PathSwitchRequest + CRITICALITY reject +} +``` + +``` +} + +pDUSessionResourceModify NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PDUSessionResourceModifyRequest + SUCCESSFUL OUTCOME PDUSessionResourceModifyResponse + PROCEDURE CODE id-PDUSessionResourceModify + CRITICALITY reject +} + +pDUSessionResourceModifyIndication NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PDUSessionResourceModifyIndication + SUCCESSFUL OUTCOME PDUSessionResourceModifyConfirm + PROCEDURE CODE id-PDUSessionResourceModifyIndication + CRITICALITY reject +} + +pDUSessionResourceNotify NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PDUSessionResourceNotify + PROCEDURE CODE id-PDUSessionResourceNotify + CRITICALITY ignore +} + +pDUSessionResourceRelease NGAP-ELEMENTARY-PROCEDURE ::= { +``` + +``` + INITIATING MESSAGE PDUSessionResourceReleaseCommand + SUCCESSFUL OUTCOME PDUSessionResourceReleaseResponse + PROCEDURE CODE id-PDUSessionResourceRelease + CRITICALITY reject +} +``` + +``` +pDUSessionResourceSetup NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PDUSessionResourceSetupRequest + SUCCESSFUL OUTCOME PDUSessionResourceSetupResponse + PROCEDURE CODE id-PDUSessionResourceSetup + CRITICALITY reject +} +``` + +``` +privateMessage NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PrivateMessage + PROCEDURE CODE id-PrivateMessage + CRITICALITY ignore +} +``` + +``` +pWSCancel NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PWSCancelRequest + SUCCESSFUL OUTCOME PWSCancelResponse + PROCEDURE CODE id-PWSCancel +``` + +``` + CRITICALITY reject + } + + pWSFailureIndication NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PWSFailureIndication + PROCEDURE CODE id-PWSFailureIndication + CRITICALITY ignore + } + + pWSRestartIndication NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PWSRestartIndication + PROCEDURE CODE id-PWSRestartIndication + CRITICALITY ignore + } + + rANConfigurationUpdate NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE RANConfigurationUpdate + SUCCESSFUL OUTCOME RANConfigurationUpdateAcknowledge + UNSUCCESSFUL OUTCOME RANConfigurationUpdateFailure + PROCEDURE CODE id-RANConfigurationUpdate + CRITICALITY reject + } +``` + +``` +rANCPRelocationIndication NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE RANCPRelocationIndication + PROCEDURE CODE id-RANCPRelocationIndication + CRITICALITY reject +} +``` + +``` +rANPagingRequest NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE RANPagingRequest + PROCEDURE CODE id-RANPagingRequest + CRITICALITY ignore +} +``` + +``` +rerouteNASRequest NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE RerouteNASRequest + PROCEDURE CODE id-RerouteNASRequest + CRITICALITY reject +} +``` + +``` +retrieveUEInformation NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE RetrieveUEInformation + PROCEDURE CODE id-RetrieveUEInformation + CRITICALITY reject +} +``` + +``` +rRCInactiveTransitionReport NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE RRCInactiveTransitionReport + PROCEDURE CODE id-RRCInactiveTransitionReport + CRITICALITY ignore +} + +secondaryRATDataUsageReport NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE SecondaryRATDataUsageReport + PROCEDURE CODE id-SecondaryRATDataUsageReport + CRITICALITY ignore +} + +timingSynchronisationStatus NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE TimingSynchronisationStatusRequest + SUCCESSFUL OUTCOME TimingSynchronisationStatusResponse + UNSUCCESSFUL OUTCOME TimingSynchronisationStatusFailure + PROCEDURE CODE id-TimingSynchronisationStatus + CRITICALITY reject +} + +timingSynchronisationStatusReport NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE TimingSynchronisationStatusReport +``` + +``` + PROCEDURE CODE id-TimingSynchronisationStatusReport + CRITICALITY ignore +} +``` + +``` +traceFailureIndication NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE TraceFailureIndication + PROCEDURE CODE id-TraceFailureIndication + CRITICALITY ignore +} +``` + +``` +traceStart NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE TraceStart + PROCEDURE CODE id-TraceStart + CRITICALITY ignore +} +``` + +``` +uEContextModification NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE UEContextModificationRequest + SUCCESSFUL OUTCOME UEContextModificationResponse + UNSUCCESSFUL OUTCOME UEContextModificationFailure + PROCEDURE CODE id-UEContextModification + CRITICALITY reject +} +``` + +``` +uEContextRelease NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE UEContextReleaseCommand + SUCCESSFUL OUTCOME UEContextReleaseComplete + PROCEDURE CODE id-UEContextRelease + CRITICALITY reject +} + +uEContextReleaseRequest NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE UEContextReleaseRequest + PROCEDURE CODE id-UEContextReleaseRequest + CRITICALITY ignore +} + +uEContextResume NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE UEContextResumeRequest + SUCCESSFUL OUTCOME UEContextResumeResponse + UNSUCCESSFUL OUTCOME UEContextResumeFailure + PROCEDURE CODE id-UEContextResume + CRITICALITY reject +} + +uEContextSuspend NGAP-ELEMENTARY-PROCEDURE ::= { +``` + +``` + INITIATING MESSAGE UEContextSuspendRequest + SUCCESSFUL OUTCOME UEContextSuspendResponse + UNSUCCESSFUL OUTCOME UEContextSuspendFailure + PROCEDURE CODE id-UEContextSuspend + CRITICALITY reject +} + +uEInformationTransfer NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE UEInformationTransfer + PROCEDURE CODE id-UEInformationTransfer + CRITICALITY reject +} + +uERadioCapabilityCheck NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE UERadioCapabilityCheckRequest + SUCCESSFUL OUTCOME UERadioCapabilityCheckResponse + PROCEDURE CODE id-UERadioCapabilityCheck + CRITICALITY reject +} + +uERadioCapabilityIDMapping NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE UERadioCapabilityIDMappingRequest + SUCCESSFUL OUTCOME UERadioCapabilityIDMappingResponse +``` + +``` + PROCEDURE CODE id-UERadioCapabilityIDMapping + CRITICALITY reject + } + + uERadioCapabilityInfoIndication NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE UERadioCapabilityInfoIndication + PROCEDURE CODE id-UERadioCapabilityInfoIndication + CRITICALITY ignore + } + + uETNLABindingRelease NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE UETNLABindingReleaseRequest + PROCEDURE CODE id-UETNLABindingRelease + CRITICALITY ignore + } + + uplinkNASTransport NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE UplinkNASTransport + PROCEDURE CODE id-UplinkNASTransport + CRITICALITY ignore + } + + uplinkNonUEAssociatedNRPPaTransport NGAP-ELEMENTARY-PROCEDURE ::= { +``` + +``` + INITIATING MESSAGE UplinkNonUEAssociatedNRPPaTransport + PROCEDURE CODE id-UplinkNonUEAssociatedNRPPaTransport + CRITICALITY ignore +} + +uplinkRANConfigurationTransfer NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE UplinkRANConfigurationTransfer + PROCEDURE CODE id-UplinkRANConfigurationTransfer + CRITICALITY ignore +} + +uplinkRANEarlyStatusTransfer NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE UplinkRANEarlyStatusTransfer + PROCEDURE CODE id-UplinkRANEarlyStatusTransfer + CRITICALITY reject +} + +uplinkRANStatusTransfer NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE UplinkRANStatusTransfer + PROCEDURE CODE id-UplinkRANStatusTransfer + CRITICALITY ignore +} +``` + +``` +uplinkUEAssociatedNRPPaTransport NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE UplinkUEAssociatedNRPPaTransport + PROCEDURE CODE id-UplinkUEAssociatedNRPPaTransport + CRITICALITY ignore +} + +writeReplaceWarning NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE WriteReplaceWarningRequest + SUCCESSFUL OUTCOME WriteReplaceWarningResponse + PROCEDURE CODE id-WriteReplaceWarning + CRITICALITY reject +} + +uplinkRIMInformationTransfer NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE UplinkRIMInformationTransfer + PROCEDURE CODE id-UplinkRIMInformationTransfer + CRITICALITY ignore +} + +downlinkRIMInformationTransfer NGAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE DownlinkRIMInformationTransfer + PROCEDURE CODE id-DownlinkRIMInformationTransfer + CRITICALITY ignore +} +``` + +} + +END + +-- ASN1STOP + +### 9.4.4 PDU Definitions + +-- ASN1START + +-- \*\*\*\*\* + +-- + +-- PDU definitions for NGAP. + +-- + +-- \*\*\*\*\* + +NGAP-PDU-Contents { + +itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + +ngran-Access (22) modules (3) ngap (1) version1 (1) ngap-PDU-Contents (1) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +``` +-- ***** +-- +-- IE parameter types from other modules. +-- +-- ***** +``` + +IMPORTS + +``` +A2X-PC5-QoS-Parameters, +AerialUEsubscriptionInformation, +AllowedNSSAI, +AMFName, +AMFSetID, +AMF-TNLAssociationSetupList, +AMF-TNLAssociationToAddList, +AMF-TNLAssociationToRemoveList, +AMF-TNLAssociationToUpdateList, +AMF-UE-NGAP-ID, +AssistanceDataForPaging, +AssociatedSessionID, +AuthenticatedIndication, +BroadcastCancelledAreaList, +BroadcastCompletedAreaList, +``` + +BroadcastTransportFailureTransfer, +BroadcastTransportRequestTransfer, +BroadcastTransportResponseTransfer, +CancelAllWarningMessages, +Cause, +CellIDListForRestart, +CEmodeBrestricted, +CEmodeBSupport-Indicator, +CNAssistedRANTuning, +ConcurrentWarningMessageInd, +CoreNetworkAssistanceInformationForInactive, +CPTransportLayerInformation, +CriticalityDiagnostics, +DataCodingScheme, +DirectForwardingPathAvailability, +DL-CP-SecurityInformation, +DL-Signalling, +EarlyStatusTransfer-TransparentContainer, +EDT-Session, +EmergencyAreaIDListForRestart, +EmergencyFallbackIndicator, +EN-DCSONConfigurationTransfer, +EndIndication, + +Enhanced-CoverageRestriction, +EUTRA-CGI, +EUTRA-PagingeDRXInformation, +Extended-AMFName, +Extended-ConnectedTime, +Extended-RANNodeName, +FiveGCAction, +FiveG-ProSeAuthorized, +FiveG-ProSePC5QoSParameters, +FiveG-S-TMSI, +GlobalRANNodeID, +GUAMI, +HandoverFlag, +HandoverType, +IAB-Authorized, +IABNodeIndication, +IAB-Supported, +IMSVoiceSupportIndicator, +IndexToRFSP, +InfoOnRecommendedCellsAndRANNodesForPaging, +IntersystemSONConfigurationTransfer, +LAI, +LocationReportingRequestType, + +LTE-A2X-ServicesAuthorized, +ITEM-Indication, +LTEUESidelinkAggregateMaximumBitrate, +LTEV2XServicesAuthorized, +MaskedIMEISV, +MBS-AreaSessionID, +MBS-DistributionReleaseRequestTransfer, +MBS-DistributionSetupRequestTransfer, +MBS-DistributionSetupResponseTransfer, +MBS-DistributionSetupUnsuccessfulTransfer, +MBS-ServiceArea, +MBS-SessionID, +MBSSessionReleaseResponseTransfer, +MBSSessionSetupOrModFailureTransfer, +MBSSessionSetupOrModRequestTransfer, +MBSSessionSetupOrModResponseTransfer, +MDTPLMNList, +MDTPLMNModificationList, +MessageIdentifier, +MobileIAB-Authorized, +MobileIABNodeIndication, +MobileIAB-Supported, +MobilityRestrictionList, + +MulticastGroupPagingAreaList, +MulticastSessionActivationRequestTransfer, +MulticastSessionDeactivationRequestTransfer, +MulticastSessionUpdateRequestTransfer, +NAS-PDU, +NASSecurityParametersFromNGRAN, +NB-IoT-DefaultPagingDRX, +NB-IoT-PagingDRX, +NB-IoT-Paging-eDRXInfo, +NB-IoT-UEPriority, +NetworkControlledRepeaterAuthorized, +NewSecurityContextInd, +NGRAN-CGI, +NGRAN-TNLAssociationToRemoveList, +NGRANTraceID, +NID, +NoPDUSessionIndication, +NotifySourceNGRANNode, +NPN-AccessInformation, +NR-A2X-ServicesAuthorized, +NR-CGI, +NR-PagingeDRXInformation, +NRPPa-PDU, + +NRUESidelinkAggregateMaximumBitrate, +NRV2XServicesAuthorized, +NumberOfBroadcastsRequested, +OverloadResponse, +OverloadStartNSSAILList, +PagingAssisDataforCEcapabUE, +PagingCause, +PagingDRX, +PagingOrigin, +PagingPolicyDifferentiation, +PagingPriority, +Partially-Allowed-NSSAI, +PC5QoSParameters, +PDUSessionAggregateMaximumBitRate, +PDUSessionResourceAdmittedList, +PDUSessionResourceFailedToModifyListModCfm, +PDUSessionResourceFailedToModifyListModRes, +PDUSessionResourceFailedToResumeListRESReq, +PDUSessionResourceFailedToResumeListRESRes, +PDUSessionResourceFailedToSetupListCxtFail, +PDUSessionResourceFailedToSetupListCxtRes, +PDUSessionResourceFailedToSetupListHOAck, +PDUSessionResourceFailedToSetupListPSReq, + +PDUSessionResourceFailedToSetupListSURes, +PDUSessionResourceHandoverList, +PDUSessionResourceListCxtRelCpl, +PDUSessionResourceListCxtRelReq, +PDUSessionResourceListHORqd, +PDUSessionResourceModifyListModCfm, +PDUSessionResourceModifyListModInd, +PDUSessionResourceModifyListModReq, +PDUSessionResourceModifyListModRes, +PDUSessionResourceNotifyList, +PDUSessionResourceReleasedListNot, +PDUSessionResourceReleasedListPSAck, +PDUSessionResourceReleasedListPSFail, +PDUSessionResourceReleasedListRelRes, +PDUSessionResourceResumeListRESReq, +PDUSessionResourceResumeListRESRes, +PDUSessionResourceSecondaryRATUsageList, +PDUSessionResourceSetupListCxtReq, +PDUSessionResourceSetupListCxtRes, +PDUSessionResourceSetupListHOReq, +PDUSessionResourceSetupListSUReq, +PDUSessionResourceSetupListSURes, +PDUSessionResourceSuspendListSUSReq, + +PDUSessionResourceSwitchedList, +PDUSessionResourceToBeSwitchedDLList, +PDUSessionResourceToReleaseListHOCmd, +PDUSessionResourceToReleaseListRelCmd, +PEIPSassistanceInformation, +PLMNIdentity, +PLMNSupportList, +PrivacyIndicator, +PWSFailedCellIDList, +QMCConfigInfo, +QMCDDeactivation, +RANNodeName, +RANPagingPriority, +RANStatusTransfer-TransparentContainer, +RANTimingSynchronisationStatusInfo, +RAN-TSSRequestType, +RAN-TSSScope, +RAN-UE-NGAP-ID, +RedCapIndication, +RedirectionVoiceFallback, +RelativeAMFCapacity, +RepetitionPeriod, +ResetType, + +RGLevelWirelineAccessCharacteristics, +RIMInformationTransfer, +RoutingID, +RRCEstablishmentCause, +RRInactiveTransitionReportRequest, +RRCState, +SecurityContext, +SecurityKey, +SerialNumber, +ServedGUAMIList, +SliceSupportList, +S-NSSAI, +SONConfigurationTransfer, +SourceToTarget-AMFInformationReroute, +SourceToTarget-TransparentContainer, +SRVCCOperationPossible, +SupportedTAList, +Suspend-Request-Indication, +Suspend-Response-Indication, +TAI, +TAIListForPaging, +TAIListForRestart, +TargetID, + +TargetNSSAIInformation, +TargettoSource-Failure-TransparentContainer, +TargetToSource-TransparentContainer, +TimeSyncAssistanceInfo, +TimeToWait, +TNLAssociationList, +TraceActivation, +TrafficLoadReductionIndication, +TransportLayerAddress, +UEAggregateMaximumBitRate, +UE-associatedLogicalNG-connectionList, +UECapabilityInfoRequest, +UEContextRequest, +UE-DifferentiationInfo, +UE-NGAP-IDs, +UEPagingIdentity, +UEPresenceInAreaOfInterestList, +UERadioCapability, +UERadioCapabilityForPaging, +UERadioCapabilityID, +UERetentionInformation, +UESecurityCapabilities, +UESliceMaximumBitRateList, + +UE-UP-CIoT-Support, +UL-CP-SecurityInformation, +UnavailableGUAMIList, +URI-address, +UserLocationInformation, +WarningAreaCoordinates, +WarningAreaList, +WarningMessageContents, +WarningSecurityInfo, +WarningType, +WUS-Assistance-Information + +FROM NGAP-IEs + +PrivateIE-Container{}, +ProtocolExtensionContainer{}, +ProtocolIE-Container{}, +ProtocolIE-ContainerList{}, +ProtocolIE-ContainerPair{}, +ProtocolIE-SingleContainer{}, +NGAP-PRIVATE-IES, +NGAP-PROTOCOL-EXTENSION, +NGAP-PROTOCOL-IES, + +NGAP-PROTOCOL-IES-PAIR + +FROM NGAP-Containers + +id-A2X-PC5-QoS-Parameters, +id-AerialUESubscriptionInformation, +id-AllowedNSSAI, +id-AMFName, +id-AMFOverloadResponse, +id-AMFSetID, +id-AMF-TNLAssociationFailedToSetupList, +id-AMF-TNLAssociationSetupList, +id-AMF-TNLAssociationToAddList, +id-AMF-TNLAssociationToRemoveList, +id-AMF-TNLAssociationToUpdateList, +id-AMFTrafficLoadReductionIndication, +id-AMF-UE-NGAP-ID, +id-AssistanceDataForPaging, +id-AssociatedSessionID, +id-AuthenticatedIndication, +id-BroadcastCancelledAreaList, +id-BroadcastCompletedAreaList, +id-BroadcastTransportFailureTransfer, + +id-BroadcastTransportRequestTransfer, +id-BroadcastTransportResponseTransfer, +id-CancelAllWarningMessages, +id-Cause, +id-CellIDListForRestart, +id-CEmodeBrestricted, +id-CEmodeBSupport-Indicator, +id-CNAssistedRANTuning, +id-ConcurrentWarningMessageInd, +id-CoreNetworkAssistanceInformationForInactive, +id-CriticalityDiagnostics, +id-DataCodingScheme, +id-DefaultPagingDRX, +id-DirectForwardingPathAvailability, +id-DL-CP-SecurityInformation, +id-DL-Signalling, +id-EarlyStatusTransfer-TransparentContainer, +id-EDT-Session, +id-EmergencyAreaIDListForRestart, +id-EmergencyFallbackIndicator, +id-ENDC-SONConfigurationTransferDL, +id-ENDC-SONConfigurationTransferUL, +id-EndIndication, + +id-Enhanced-CoverageRestriction, +id-EUTRA-CGI, +id-EUTRA-PagingeDRXInformation, +id-Extended-AMFName, +id-Extended-ConnectedTime, +id-Extended-RANNodeName, +id-FiveGCAction, +id-FiveG-ProSeAuthorized, +id-FiveG-ProSePC5QoSParameters, +id-FiveG-ProSeUEPC5AggregateMaximumBitRate, +id-FiveG-S-TMSI, +id-GlobalRANNodeID, +id-GUAMI, +id-HandoverFlag, +id-HandoverType, +id-IAB-Authorized, +id-IABNodeIndication, +id-IAB-Supported, +id-IMSVoiceSupportIndicator, +id-IndexToRFSP, +id-InfoOnRecommendedCellsAndRANNodesForPaging, +id-IntersystemSONConfigurationTransferDL, +id-IntersystemSONConfigurationTransferUL, + +id-LocationReportingRequestType, +id-LTE-A2X-ServicesAuthorized, +id-LTE-A2X-UE-PC5-AggregateMaximumBitRate, +id-LTEM-Indication, +id-LTEUESidelinkAggregateMaximumBitrate, +id-LTEV2XServicesAuthorized, +id-ManagementBasedMDTPLMNList, +id-ManagementBasedMDTPLMNModificationList, +id-MaskedIMEISV, +id-MBS-AreaSessionID, +id-MBS-DistributionReleaseRequestTransfer, +id-MBS-DistributionSetupRequestTransfer, +id-MBS-DistributionSetupResponseTransfer, +id-MBS-DistributionSetupUnsuccessfulTransfer, +id-MBS-ServiceArea, +id-MBS-SessionID, +id-MBSSessionModificationFailureTransfer, +id-MBSSessionModificationRequestTransfer, +id-MBSSessionModificationResponseTransfer, +id-MBSSessionReleaseResponseTransfer, +id-MBSSessionSetupFailureTransfer, +id-MBSSessionSetupRequestTransfer, +id-MBSSessionSetupResponseTransfer, + +id-MessageIdentifier, +id-MobileIAB-Authorized, +id-MobileIABNodeIndication, +id-MobileIAB-Supported, +id-MobilityRestrictionList, +id-MulticastGroupPagingAreaList, +id-MulticastSessionActivationRequestTransfer, +id-MulticastSessionDeactivationRequestTransfer, +id-MulticastSessionUpdateRequestTransfer, +id-NASC, +id-NAS-PDU, +id-NASSecurityParametersFromNGRAN, +id-NB-IoT-DefaultPagingDRX, +id-NB-IoT-PagingDRX, +id-NB-IoT-Paging-eDRXInfo, +id-NB-IoT-UEPriority, +id-NetworkControlledRepeaterAuthorized, +id-NewAMF-UE-NGAP-ID, +id-NewGUAMI, +id-NewSecurityContextInd, +id-NGAP-Message, +id-NGRAN-CGI, +id-NGRAN-TNLAssociationToRemoveList, + +id-NGRANTraceID, +id-NoPDUSessionIndication, +id-NotifySourceNGRANNode, +id-NPN-AccessInformation, +id-NR-A2X-ServicesAuthorized, +id-NR-A2X-UE-PC5-AggregateMaximumBitRate, +id-NR-PagingeDRXInformation, +id-NRPPa-PDU, +id-NRUESidelinkAggregateMaximumBitrate, +id-NRV2XServicesAuthorized, +id-NumberOfBroadcastsRequested, +id-OldAMF, +id-OverloadStartNSSAIList, +id-PagingAssisDataforCEcapabUE, +id-PagingCause, +id-PagingDRX, +id-PagingOrigin, +id-PagingPolicyDifferentiation, +id-PagingPriority, +id-Partially-Allowed-NSSAI, +id-PC5QoSParameters, +id-PDUSessionResourceAdmittedList, +id-PDUSessionResourceFailedToModifyListModCfm, + +id-PDUSessionResourceFailedToModifyListModRes, +id-PDUSessionResourceFailedToResumeListRESReq, +id-PDUSessionResourceFailedToResumeListRESRes, +id-PDUSessionResourceFailedToSetupListCxtFail, +id-PDUSessionResourceFailedToSetupListCxtRes, +id-PDUSessionResourceFailedToSetupListHOAck, +id-PDUSessionResourceFailedToSetupListPSReq, +id-PDUSessionResourceFailedToSetupListSUSRes, +id-PDUSessionResourceHandoverList, +id-PDUSessionResourceListCxtRelCpl, +id-PDUSessionResourceListCxtRelReq, +id-PDUSessionResourceListHORqd, +id-PDUSessionResourceModifyListModCfm, +id-PDUSessionResourceModifyListModInd, +id-PDUSessionResourceModifyListModReq, +id-PDUSessionResourceModifyListModRes, +id-PDUSessionResourceNotifyList, +id-PDUSessionResourceReleasedListNot, +id-PDUSessionResourceReleasedListPSAck, +id-PDUSessionResourceReleasedListPSFail, +id-PDUSessionResourceReleasedListRelRes, +id-PDUSessionResourceResumeListRESReq, +id-PDUSessionResourceResumeListRESRes, + +id-PDUSessionResourceSecondaryRATUsageList, +id-PDUSessionResourceSetupListCxtReq, +id-PDUSessionResourceSetupListCxtRes, +id-PDUSessionResourceSetupListHOReq, +id-PDUSessionResourceSetupListSUReq, +id-PDUSessionResourceSetupListSUSRes, +id-PDUSessionResourceSuspendListSUSReq, +id-PDUSessionResourceSwitchedList, +id-PDUSessionResourceToBeSwitchedDLList, +id-PDUSessionResourceToReleaseListHOCmd, +id-PDUSessionResourceToReleaseListRelCmd, +id-PEIPSasssistanceInformation, +id-PLMNSupportList, +id-PrivacyIndicator, +id-PWSFailedCellIDList, +id-QMCConfigInfo, +id-QMCDeactivation, +id-RANNodename, +id-RANPagingPriority, +id-RANStatusTransfer-TransparentContainer, +id-RANTimingSynchronisationStatusInfo, +id-RAN-TSSRequestType, +id-RAN-TSSScope, + +id-RAN-UE-NGAP-ID, +id-RedCapIndication, +id-RedirectionVoiceFallback, +id-RelativeAMFCapacity, +id-RepetitionPeriod, +id-ResetType, +id-RGLevelWirelineAccessCharacteristics, +id-RIMInformationTransfer, +id-RoutingID, +id-RRCEstablishmentCause, +id-RRCInactiveTransitionReportRequest, +id-RRC-Resume-Cause, +id-RRCState, +id-SecurityContext, +id-SecurityKey, +id-SelectedNID, +id-SelectedPLMNIdentity, +id-SerialNumber, +id-ServedGUAMIList, +id-SliceSupportList, +id-S-NSSAI, +id-SONConfigurationTransferDL, +id-SONConfigurationTransferUL, + +id-SourceAMF-UE-NGAP-ID, +id-SourceToTarget-AMFInformationReroute, +id-SourceToTarget-TransparentContainer, +id-SRVCCOperationPossible, +id-SupportedTAList, +id-Suspend-Request-Indication, +id-Suspend-Response-Indication, +id-TAI, +id-TAIListForPaging, +id-TAIListForRestart, +id-TargetID, +id-TargetNSSAIInformation, +id-TargettoSource-Failure-TransparentContainer, +id-TargetToSource-TransparentContainer, +id-TimeSyncAssistanceInfo, +id-TimeToWait, +id-TNGFIdentityInformation, +id-TraceActivation, +id-TraceCollectionEntityIPAddress, +id-TraceCollectionEntityURI, +id-TWIFIdentityInformation, +id-UEAggregateMaximumBitRate, +id-UE-associatedLogicalNG-connectionList, + +id-UECapabilityInfoRequest, +id-UEContextRequest, +id-UE-DifferentiationInfo, +id-UE-NGAP-IDs, +id-UEPagingIdentity, +id-UEPresenceInAreaOfInterestList, +id-UERadioCapability, +id-UERadioCapability-EUTRA-Format, +id-UERadioCapabilityForPaging, +id-UERadioCapabilityID, +id-UERetentionInformation, +id-UESecurityCapabilities, +id-UESliceMaximumBitRateList, +id-UE-UP-CIoT-Support, +id-UL-CP-SecurityInformation, +id-UnavailableGUAMIList, +id-UserLocationInformation, +id-W-AGFIdentityInformation, +id-WarningAreaCoordinates, +id-WarningAreaList, +id-WarningMessageContents, +id-WarningSecurityInfo, +id-WarningType, + +id-WUS-Assistance-Information + +FROM NGAP-Constants; + +-- \*\*\*\*\* + +-- + +-- PDU SESSION MANAGEMENT ELEMENTARY PROCEDURES + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- PDU Session Resource Setup Elementary Procedure + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- PDU SESSION RESOURCE SETUP REQUEST + +-- + +-- \*\*\*\*\* + +``` + +PDUSessionResourceSetupRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {PDUSessionResourceSetupRequestIEs} }, + ... +} + +``` + +``` + +PDUSessionResourceSetupRequestIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY reject TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-NGAP-ID CRITICALITY reject TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RANPagingPriority CRITICALITY ignore TYPE RANPagingPriority PRESENCE optional }| + { ID id-NAS-PDU CRITICALITY reject TYPE NAS-PDU PRESENCE optional }| + { ID id-PDUSessionResourceSetupListSUReq CRITICALITY reject TYPE PDUSessionResourceSetupListSUReq PRESENCE mandatory }| + { ID id-UEAggregateMaximumBitRate CRITICALITY ignore TYPE UEAggregateMaximumBitRate PRESENCE optional }| + { ID id-UESliceMaximumBitRateList CRITICALITY ignore TYPE UESliceMaximumBitRateList PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- PDU SESSION RESOURCE SETUP RESPONSE +-- +-- ***** + +``` + +``` + +PDUSessionResourceSetupResponse ::= SEQUENCE { + +``` + +``` + +protocolIEs ProtocolIE-Container { {PDUSessionResourceSetupResponseIEs} }, +... +} + +``` + +``` + +PDUSessionResourceSetupResponseIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY ignore TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-NGAP-ID CRITICALITY ignore TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-PDUSessionResourceSetupListSURes CRITICALITY ignore TYPE PDUSessionResourceSetupListSURes PRESENCE optional }| + { ID id-PDUSessionResourceFailedToSetupListSURes CRITICALITY ignore TYPE PDUSessionResourceFailedToSetupListSURes PRESENCE optional }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }| + { ID id-UserLocationInformation CRITICALITY ignore TYPE UserLocationInformation PRESENCE optional }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- PDU Session Resource Release Elementary Procedure + +``` + +-- +-- ***** +-- ***** +-- +-- PDU SESSION RESOURCE RELEASE COMMAND +-- +-- ***** + +``` + +``` + +PDUSessionResourceReleaseCommand ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {PDUSessionResourceReleaseCommandIEs} }, + ... +} + +``` + +``` + +PDUSessionResourceReleaseCommandIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY reject TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-NGAP-ID CRITICALITY reject TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RANPagingPriority CRITICALITY ignore TYPE RANPagingPriority PRESENCE optional }| + { ID id-NAS-PDU CRITICALITY ignore TYPE NAS-PDU PRESENCE optional }| + { ID id-PDUSessionResourceToReleaseListRelCmd CRITICALITY reject TYPE PDUSessionResourceToReleaseListRelCmd PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- PDU SESSION RESOURCE RELEASE RESPONSE +-- +-- ***** + +``` + +``` + +PDUSessionResourceReleaseResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {PDUSessionResourceReleaseResponseIEs} }, + ... +} + +``` + +``` + +PDUSessionResourceReleaseResponseIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY ignore TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-NGAP-ID CRITICALITY ignore TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-PDUSessionResourceReleasedListRelRes CRITICALITY ignore TYPE PDUSessionResourceReleasedListRelRes PRESENCE mandatory }| + { ID id-UserLocationInformation CRITICALITY ignore TYPE UserLocationInformation PRESENCE optional }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- PDU Session Resource Modify Elementary Procedure + +``` + +``` + +-- +-- ***** +-- ***** +-- +-- PDU SESSION RESOURCE MODIFY REQUEST +-- +-- ***** + +``` + +``` + +PDUSessionResourceModifyRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {PDUSessionResourceModifyRequestIEs} }, + ... +} + +``` + +``` + +PDUSessionResourceModifyRequestIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY reject TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-NGAP-ID CRITICALITY reject TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RANPagingPriority CRITICALITY ignore TYPE RANPagingPriority PRESENCE optional }| + { ID id-PDUSessionResourceModifyListModReq CRITICALITY reject TYPE PDUSessionResourceModifyListModReq PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- PDU SESSION RESOURCE MODIFY RESPONSE +-- +-- ***** + +``` + +``` + +PDUSessionResourceModifyResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {PDUSessionResourceModifyResponseIEs} }, + ... +} + +``` + +``` + +PDUSessionResourceModifyResponseIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY ignore TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-NGAP-ID CRITICALITY ignore TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-PDUSessionResourceModifyListModRes CRITICALITY ignore TYPE PDUSessionResourceModifyListModRes PRESENCE optional }| + { ID id-PDUSessionResourceFailedToModifyListModRes CRITICALITY ignore TYPE PDUSessionResourceFailedToModifyListModRes PRESENCE optional }| + { ID id-UserLocationInformation CRITICALITY ignore TYPE UserLocationInformation PRESENCE optional }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** + +``` + +``` + +-- +-- PDU Session Resource Notify Elementary Procedure +-- +-- ***** +-- +-- ***** +-- +-- PDU SESSION RESOURCE NOTIFY +-- +-- ***** + +``` + +``` + +PDUSessionResourceNotify ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {PDUSessionResourceNotifyIEs} }, + ... +} + +``` + +``` + +PDUSessionResourceNotifyIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY reject TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-NGAP-ID CRITICALITY reject TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-PDUSessionResourceNotifyList CRITICALITY reject TYPE PDUSessionResourceNotifyList PRESENCE optional }| + { ID id-PDUSessionResourceReleasedListNot CRITICALITY ignore TYPE PDUSessionResourceReleasedListNot PRESENCE optional }| + { ID id-UserLocationInformation CRITICALITY ignore TYPE UserLocationInformation PRESENCE optional }, + ... +} + +``` + +} + +-- \*\*\*\*\* + +-- + +-- PDU Session Resource Modify Indication Elementary Procedure + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- PDU SESSION RESOURCE MODIFY INDICATION + +-- + +-- \*\*\*\*\* + +PDUSessionResourceModifyIndication := SEQUENCE { + +    protocolIEs    ProtocolIE-Container    { {PDUSessionResourceModifyIndicationIEs} }, + +    ... +} + +PDUSessionResourceModifyIndicationIEs NGAP-PROTOCOL-IES := { + +    { ID id-AMF-UE-NGAP-ID                            CRITICALITY reject  TYPE AMF-UE-NGAP-ID                    PRESENCE mandatory  }| + +    { ID id-RAN-UE-NGAP-ID                           CRITICALITY reject  TYPE RAN-UE-NGAP-ID                    PRESENCE mandatory  }| + +``` + + { ID id-PDUSessionResourceModifyListModInd CRITICALITY reject TYPE PDUSessionResourceModifyListModInd PRESENCE mandatory }| + { ID id-UserLocationInformation CRITICALITY ignore TYPE UserLocationInformation PRESENCE optional }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- PDU SESSION RESOURCE MODIFY CONFIRM + +-- + +-- \*\*\*\*\* + +``` + +PDUSessionResourceModifyConfirm ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {PDUSessionResourceModifyConfirmIEs} }, + ... +} + +``` + +``` + +PDUSessionResourceModifyConfirmIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY ignore TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-NGAP-ID CRITICALITY ignore TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-PDUSessionResourceModifyListModCfm CRITICALITY ignore TYPE PDUSessionResourceModifyListModCfm PRESENCE optional }| + { ID id-PDUSessionResourceFailedToModifyListModCfm CRITICALITY ignore TYPE PDUSessionResourceFailedToModifyListModCfm PRESENCE optional }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +``` + +} + +-- ***** +-- +-- UE CONTEXT MANAGEMENT ELEMENTARY PROCEDURES +-- +-- ***** +-- +-- ***** +-- +-- Initial Context Setup Elementary Procedure +-- +-- ***** +-- +-- ***** +-- +-- INITIAL CONTEXT SETUP REQUEST +-- +-- ***** + +InitialContextSetupRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {InitialContextSetupRequestIEs} }, + ... +} + +``` + +} + +InitialContextSetupRequestIEs NGAP-PROTOCOL-IES ::= { + +| | | | | | +|-----------------------------------------------------|--------------------|--------------------------------------------------|----------------------|---| +| { ID id-AMF-UE-NGAP-ID | CRITICALITY reject | TYPE AMF-UE-NGAP-ID | PRESENCE mandatory | } | +| { ID id-RAN-UE-NGAP-ID | CRITICALITY reject | TYPE RAN-UE-NGAP-ID | PRESENCE mandatory | } | +| { ID id-OldAMF | CRITICALITY reject | TYPE AMFName | PRESENCE optional | } | +| { ID id-UEAggregateMaximumBitRate | CRITICALITY reject | TYPE UEAggregateMaximumBitRate | PRESENCE conditional | } | +| { ID id-CoreNetworkAssistanceInformationForInactive | CRITICALITY ignore | TYPE CoreNetworkAssistanceInformationForInactive | PRESENCE optional | } | +| { ID id-GUAMI | CRITICALITY reject | TYPE GUAMI | PRESENCE mandatory | } | +| { ID id-PDUSessionResourceSetupListCxtReq | CRITICALITY reject | TYPE PDUSessionResourceSetupListCxtReq | PRESENCE optional | } | +| { ID id-AllowedNSSAI | CRITICALITY reject | TYPE AllowedNSSAI | PRESENCE mandatory | } | +| { ID id-UESecurityCapabilities | CRITICALITY reject | TYPE UESecurityCapabilities | PRESENCE mandatory | } | +| { ID id-SecurityKey | CRITICALITY reject | TYPE SecurityKey | PRESENCE mandatory | } | +| { ID id-TraceActivation | CRITICALITY ignore | TYPE TraceActivation | PRESENCE optional | } | +| { ID id-MobilityRestrictionList | CRITICALITY ignore | TYPE MobilityRestrictionList | PRESENCE optional | } | +| { ID id-UERadioCapability | CRITICALITY ignore | TYPE UERadioCapability | PRESENCE optional | } | +| { ID id-IndexToRFSP | CRITICALITY ignore | TYPE IndexToRFSP | PRESENCE optional | } | +| { ID id-MaskedIMEISV | CRITICALITY ignore | TYPE MaskedIMEISV | PRESENCE optional | } | +| { ID id-NAS-PDU | CRITICALITY ignore | TYPE NAS-PDU | PRESENCE optional | } | +| { ID id-EmergencyFallbackIndicator | CRITICALITY reject | TYPE EmergencyFallbackIndicator | PRESENCE optional | } | +| { ID id-RRCInactiveTransitionReportRequest | CRITICALITY ignore | TYPE RRCInactiveTransitionReportRequest | PRESENCE optional | } | +| { ID id-UERadioCapabilityForPaging | CRITICALITY ignore | TYPE UERadioCapabilityForPaging | PRESENCE optional | } | + +``` + +{ ID id-RedirectionVoiceFallback CRITICALITY ignore TYPE RedirectionVoiceFallback PRESENCE optional }| +{ ID id-LocationReportingRequestType CRITICALITY ignore TYPE LocationReportingRequestType PRESENCE optional }| +{ ID id-CNAssistedRANTuning CRITICALITY ignore TYPE CNAssistedRANTuning PRESENCE optional }| +{ ID id-SRVCCOperationPossible CRITICALITY ignore TYPE SRVCCOperationPossible PRESENCE optional }| +{ ID id-IAB-Authorized CRITICALITY ignore TYPE IAB-Authorized PRESENCE optional }| +{ ID id-Enhanced-CoverageRestriction CRITICALITY ignore TYPE Enhanced-CoverageRestriction PRESENCE optional }| +{ ID id-Extended-ConnectedTime CRITICALITY ignore TYPE Extended-ConnectedTime PRESENCE optional }| +{ ID id-UE-DifferentiationInfo CRITICALITY ignore TYPE UE-DifferentiationInfo 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-PC5QoSParameters CRITICALITY ignore TYPE PC5QoSParameters PRESENCE optional }| +{ ID id-CEmodeBrestricted CRITICALITY ignore TYPE CEmodeBrestricted PRESENCE optional }| +{ ID id-UE-UP-CIoT-Support CRITICALITY ignore TYPE UE-UP-CIoT-Support PRESENCE optional }| +{ ID id-RGLevelWirelineAccessCharacteristics CRITICALITY ignore TYPE RGLevelWirelineAccessCharacteristics PRESENCE optional }| +{ ID id-ManagementBasedMDTPLMNList CRITICALITY ignore TYPE MDTPLMNList PRESENCE optional }| +{ ID id-UERadioCapabilityID CRITICALITY reject TYPE UERadioCapabilityID PRESENCE optional }| +{ ID id-TimeSyncAssistanceInfo CRITICALITY ignore TYPE TimeSyncAssistanceInfo PRESENCE optional }| +{ ID id-QMCConfigInfo CRITICALITY ignore TYPE QMCConfigInfo PRESENCE optional }| +{ ID id-TargetNSSAIInformation CRITICALITY ignore TYPE TargetNSSAIInformation PRESENCE optional }| +{ ID id-UESliceMaximumBitRateList CRITICALITY ignore TYPE UESliceMaximumBitRateList 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-ProSePC5QoSParameters CRITICALITY ignore TYPE FiveG-ProSePC5QoSParameters PRESENCE optional }| + { ID id-NetworkControlledRepeaterAuthorized CRITICALITY ignore TYPE NetworkControlledRepeaterAuthorized PRESENCE optional }| + { ID id-AerialUEsubscriptionInformation CRITICALITY ignore TYPE AerialUEsubscriptionInformation PRESENCE optional }| + { ID id-NR-A2X-ServicesAuthorized CRITICALITY ignore TYPE NR-A2X-ServicesAuthorized PRESENCE optional }| + { ID id-LTE-A2X-ServicesAuthorized CRITICALITY ignore TYPE LTE-A2X-ServicesAuthorized PRESENCE optional }| + { ID id-NR-A2X-UE-PC5-AggregateMaximumBitRate CRITICALITY ignore TYPE NRUESidelinkAggregateMaximumBitrate PRESENCE optional }| + { ID id-LTE-A2X-UE-PC5-AggregateMaximumBitRate CRITICALITY ignore TYPE LTEUESidelinkAggregateMaximumBitrate PRESENCE optional }| + { ID id-A2X-PC5-QoS-Parameters CRITICALITY ignore TYPE A2X-PC5-QoS-Parameters PRESENCE optional }| + { ID id-MobileIAB-Authorized CRITICALITY ignore TYPE MobileIAB-Authorized PRESENCE optional }| + { ID id-Partially-Allowed-NSSAI CRITICALITY ignore TYPE Partially-Allowed-NSSAI PRESENCE optional }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- INITIAL CONTEXT SETUP RESPONSE + +-- + +-- \*\*\*\*\* + +``` + +InitialContextSetupResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {InitialContextSetupResponseIEs} }, + ... +} + +``` + +} + +``` + +InitialContextSetupResponseIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY ignore TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-NGAP-ID CRITICALITY ignore TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-PDUSessionResourceSetupListCxtRes CRITICALITY ignore TYPE PDUSessionResourceSetupListCxtRes PRESENCE optional }| + { ID id-PDUSessionResourceFailedToSetupListCxtRes CRITICALITY ignore TYPE PDUSessionResourceFailedToSetupListCxtRes PRESENCE optional }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +-- \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* +-- +-- INITIAL CONTEXT SETUP FAILURE +-- +-- \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* + +``` + +InitialContextSetupFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {InitialContextSetupFailureIEs} }, + ... +} + +``` + +} + +``` + +InitialContextSetupFailureIEs NGAP-PROTOCOL-IEs ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY ignore TYPE AMF-UE-NGAP-ID PRESENCE mandatory } | + { ID id-RAN-UE-NGAP-ID CRITICALITY ignore TYPE RAN-UE-NGAP-ID PRESENCE mandatory } | + { ID id-PDUSessionResourceFailedToSetupListCxtFail CRITICALITY ignore TYPE PDUSessionResourceFailedToSetupListCxtFail PRESENCE optional } | + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory } | + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + + +-- ************************************************************** +-- +-- UE Context Release Request Elementary Procedure +-- +-- ************************************************************** + +-- ************************************************************** +-- +-- UE CONTEXT RELEASE REQUEST +-- +-- ************************************************************** + +UEContextReleaseRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {UEContextReleaseRequest-IEs} }, + +``` + +... +} + +UEContextReleaseRequest-IEs NGAP-PROTOCOL-IES ::= { +    { ID id-AMF-UE-NGAP-ID                    CRITICALITY reject  TYPE AMF-UE-NGAP-ID                    PRESENCE mandatory  }| +    { ID id-RAN-UE-NGAP-ID                    CRITICALITY reject  TYPE RAN-UE-NGAP-ID                    PRESENCE mandatory  }| +    { ID id-PDUSessionResourceListCxtRelReq  CRITICALITY reject  TYPE PDUSessionResourceListCxtRelReq  PRESENCE optional   }| +    { ID id-Cause                                CRITICALITY ignore  TYPE Cause                                PRESENCE mandatory  }, +    ... +} + +-- \*\*\*\*\* + +-- + +-- UE Context Release Elementary Procedure + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- UE CONTEXT RELEASE COMMAND + +-- + +-- \*\*\*\*\* + +``` + +UEContextReleaseCommand ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {UEContextReleaseCommand-IEs} }, + ... +} + +``` + +``` + +UEContextReleaseCommand-IEs NGAP-PROTOCOL-IES ::= { + { ID id-UE-NGAP-IDs CRITICALITY reject TYPE UE-NGAP-IDs PRESENCE mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- UE CONTEXT RELEASE COMPLETE +-- +-- ***** + +``` + +``` + +UEContextReleaseComplete ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {UEContextReleaseComplete-IEs} }, + ... +} + +``` + +``` + +UEContextReleaseComplete-IEs NGAP-PROTOCOL-IES ::= { + +``` + +``` + + { ID id-AMF-UE-NGAP-ID CRITICALITY ignore TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-NGAP-ID CRITICALITY ignore TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-UserLocationInformation CRITICALITY ignore TYPE UserLocationInformation PRESENCE optional }| + { ID id-InfoOnRecommendedCellsAndRANNodesForPaging CRITICALITY ignore TYPE InfoOnRecommendedCellsAndRANNodesForPaging PRESENCE optional }| + { ID id-PDUSessionResourceListCxtRelCpl CRITICALITY reject TYPE PDUSessionResourceListCxtRelCpl PRESENCE optional }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }| + { ID id-PagingAssisDataforCEcapabUE CRITICALITY ignore TYPE PagingAssisDataforCEcapabUE PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- UE Context Resume Elementary Procedure +-- +-- ***** +-- +-- ***** +-- +-- UE CONTEXT RESUME REQUEST +-- +-- ***** + +``` + +``` +UEContextResumeRequest ::= SEQUENCE { +``` + +``` + +protocolIEs ProtocolIE-Container { {UEContextResumeRequestIEs} }, +... +} + +``` + +``` + +UEContextResumeRequestIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY reject TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-NGAP-ID CRITICALITY reject TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RRC-Resume-Cause CRITICALITY ignore TYPE RRCEstablishmentCause PRESENCE mandatory }| + { ID id-PDUSessionResourceResumeListRESReq CRITICALITY reject TYPE PDUSessionResourceResumeListRESReq PRESENCE optional }| + { ID id-PDUSessionResourceFailedToResumeListRESReq CRITICALITY reject TYPE PDUSessionResourceFailedToResumeListRESReq PRESENCE optional }| + { ID id-Suspend-Request-Indication CRITICALITY ignore TYPE Suspend-Request-Indication PRESENCE optional }| + { ID id-InfoOnRecommendedCellsAndRANNodesForPaging CRITICALITY ignore TYPE InfoOnRecommendedCellsAndRANNodesForPaging PRESENCE optional }| + { ID id-PagingAssisDataforCEcapabUE CRITICALITY ignore TYPE PagingAssisDataforCEcapabUE PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- UE CONTEXT RESUME RESPONSE +-- +-- ***** + +``` + +UEContextResumeResponse ::= SEQUENCE { + +    protocolIEs    ProtocolIE-Container    { {UEContextResumeResponseIEs} }, + +    ... + +} + +UEContextResumeResponseIEs NGAP-PROTOCOL-IES ::= { + +    { ID id-AMF-UE-NGAP-ID                    CRITICALITY ignore  TYPE AMF-UE-NGAP-ID                    PRESENCE mandatory  }| + +    { ID id-RAN-UE-NGAP-ID                    CRITICALITY ignore  TYPE RAN-UE-NGAP-ID                    PRESENCE mandatory  }| + +    { ID id-PDUSessionResourceResumeListRESRes    CRITICALITY reject  TYPE PDUSessionResourceResumeListRESRes    PRESENCE optional  }| + +    { ID id-PDUSessionResourceFailedToResumeListRESRes    CRITICALITY reject  TYPE PDUSessionResourceFailedToResumeListRESRes    PRESENCE optional +    }| + +    { ID id-SecurityContext                    CRITICALITY reject  TYPE SecurityContext                    PRESENCE optional  }| + +    { ID id-Suspend-Response-Indication            CRITICALITY ignore  TYPE Suspend-Response-Indication            PRESENCE optional  }| + +    { ID id-Extended-ConnectedTime                CRITICALITY ignore  TYPE Extended-ConnectedTime                    PRESENCE optional  }| + +    { ID id-CriticalityDiagnostics                CRITICALITY ignore  TYPE CriticalityDiagnostics                    PRESENCE optional  }, + +    ... + +} + +-- \*\*\*\*\* + +-- + +-- UE CONTEXT RESUME FAILURE + +-- + +-- \*\*\*\*\* + +``` + +UEContextResumeFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { UEContextResumeFailureIEs} }, + ... +} + +UEContextResumeFailureIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY ignore TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-NGAP-ID CRITICALITY ignore TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- UE Context Suspend Elementary Procedure +-- +-- ***** +-- +-- ***** +-- +-- ***** +-- +-- ***** +-- +-- + +``` + +-- UE CONTEXT SUSPEND REQUEST + +-- + +-- \*\*\*\*\* + +``` + +UEContextSuspendRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {UEContextSuspendRequestIEs} }, + ... +} + +``` + +``` + +UEContextSuspendRequestIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY reject TYPE AMF-UE-NGAP-ID PRESENCE mandatory } | + { ID id-RAN-UE-NGAP-ID CRITICALITY reject TYPE RAN-UE-NGAP-ID PRESENCE mandatory } | + { ID id-InfoOnRecommendedCellsAndRANNodesForPaging CRITICALITY ignore TYPE InfoOnRecommendedCellsAndRANNodesForPaging PRESENCE optional } | + { ID id-PagingAssisDataforCEcapabUE CRITICALITY ignore TYPE PagingAssisDataforCEcapabUE PRESENCE optional } | + { ID id-PDUSessionResourceSuspendListSUSReq CRITICALITY reject TYPE PDUSessionResourceSuspendListSUSReq PRESENCE optional }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- UE CONTEXT SUSPEND RESPONSE + +-- + +-- \*\*\*\*\* + +``` + +UEContextSuspendResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { UEContextSuspendResponseIEs } }, + ... +} + +UEContextSuspendResponseIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY ignore TYPE AMF-UE-NGAP-ID PRESENCE mandatory } | + { ID id-RAN-UE-NGAP-ID CRITICALITY ignore TYPE RAN-UE-NGAP-ID PRESENCE mandatory } | + { ID id-SecurityContext CRITICALITY reject TYPE SecurityContext PRESENCE optional } | + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +-- ***** +-- +-- UE CONTEXT SUSPEND FAILURE +-- +-- ***** + +UEContextSuspendFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { UEContextSuspendFailureIEs } }, + ... +} + +``` + +``` + +} + +UEContextSuspendFailureIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY ignore TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-NGAP-ID CRITICALITY ignore TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- UE Context Modification Elementary Procedure +-- +-- ***** +-- +-- ***** +-- +-- UE CONTEXT MODIFICATION REQUEST +-- +-- ***** + +``` + +``` + +UEContextModificationRequest ::= SEQUENCE { + +``` + +``` + +protocolIEs ProtocolIE-Container { {UEContextModificationRequestIEs} }, +... +} + +``` + +``` + +UEContextModificationRequestIEs NGAP-PROTOCOL-IES ::= { + +``` + +``` + + { ID id-AMF-UE-NGAP-ID CRITICALITY reject TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-NGAP-ID CRITICALITY reject TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RANPagingPriority CRITICALITY ignore TYPE RANPagingPriority PRESENCE optional }| + { ID id-SecurityKey CRITICALITY reject TYPE SecurityKey PRESENCE optional }| + { ID id-IndexToRFSP CRITICALITY ignore TYPE IndexToRFSP PRESENCE optional }| + { ID id-UEAggregateMaximumBitRate CRITICALITY ignore TYPE UEAggregateMaximumBitRate PRESENCE optional }| + { ID id-UESecurityCapabilities CRITICALITY reject TYPE UESecurityCapabilities PRESENCE optional }| + { ID id-CoreNetworkAssistanceInformationForInactive CRITICALITY ignore TYPE CoreNetworkAssistanceInformationForInactive PRESENCE optional }| + { ID id-EmergencyFallbackIndicator CRITICALITY reject TYPE EmergencyFallbackIndicator PRESENCE optional }| + { ID id-NewAMF-UE-NGAP-ID CRITICALITY reject TYPE AMF-UE-NGAP-ID PRESENCE optional }| + { ID id-RRCInactiveTransitionReportRequest CRITICALITY ignore TYPE RRCInactiveTransitionReportRequest PRESENCE optional }| + { ID id-NewGUAMI CRITICALITY reject TYPE GUAMI PRESENCE optional }| + { ID id-CNAssistedRANTuning CRITICALITY ignore TYPE CNAssistedRANTuning PRESENCE optional }| + { ID id-SRVCCOperationPossible CRITICALITY ignore TYPE SRVCCOperationPossible PRESENCE optional }| + { ID id-IAB-Authorized CRITICALITY ignore TYPE IAB-Authorized 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-PC5QoSParameters CRITICALITY ignore TYPE PC5QoSParameters PRESENCE optional }| +{ ID id-UERadioCapabilityID CRITICALITY reject TYPE UERadioCapabilityID PRESENCE optional }| +{ ID id-RGLevelWirelineAccessCharacteristics CRITICALITY ignore TYPE RGLevelWirelineAccessCharacteristics PRESENCE optional }| +{ ID id-TimeSyncAssistanceInfo CRITICALITY ignore TYPE TimeSyncAssistanceInfo PRESENCE optional }| +{ ID id-QMCConfigInfo CRITICALITY ignore TYPE QMCConfigInfo PRESENCE optional }| +{ ID id-QMCDeactivation CRITICALITY ignore TYPE QMCDeactivation PRESENCE optional }| +{ ID id-UESliceMaximumBitRateList CRITICALITY ignore TYPE UESliceMaximumBitRateList PRESENCE optional }| +{ ID id-ManagementBasedMDTPLMNModificationList CRITICALITY ignore TYPE MDTPLMNModificationList 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-ProSePC5QoSParameters CRITICALITY ignore TYPE FiveG-ProSePC5QoSParameters PRESENCE optional }| +{ ID id-NetworkControlledRepeaterAuthorized CRITICALITY ignore TYPE NetworkControlledRepeaterAuthorized PRESENCE optional }| +{ ID id-AerialUEsubscriptionInformation CRITICALITY ignore TYPE AerialUEsubscriptionInformation PRESENCE optional }| +{ ID id-NR-A2X-ServicesAuthorized CRITICALITY ignore TYPE NR-A2X-ServicesAuthorized PRESENCE optional }| +{ ID id-LTE-A2X-ServicesAuthorized CRITICALITY ignore TYPE LTE-A2X-ServicesAuthorized PRESENCE optional }| +{ ID id-NR-A2X-UE-PC5-AggregateMaximumBitRate CRITICALITY ignore TYPE NRUESidelinkAggregateMaximumBitrate PRESENCE optional }| +{ ID id-LTE-A2X-UE-PC5-AggregateMaximumBitRate CRITICALITY ignore TYPE LTEUESidelinkAggregateMaximumBitrate PRESENCE optional }| +{ ID id-A2X-PC5-QoS-Parameters CRITICALITY ignore TYPE A2X-PC5-QoS-Parameters PRESENCE optional }| +{ ID id-MobileIAB-Authorized CRITICALITY ignore TYPE MobileIAB-Authorized PRESENCE optional }, +... +} + +``` + +``` + +-- ***** +-- +-- UE CONTEXT MODIFICATION RESPONSE +-- +-- ***** + +``` + +``` + +UEContextModificationResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {UEContextModificationResponseIEs} }, + ... +} + +``` + +``` + +UEContextModificationResponseIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY ignore TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-NGAP-ID CRITICALITY ignore TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RRCState CRITICALITY ignore TYPE RRCState PRESENCE optional }| + { ID id-UserLocationInformation CRITICALITY ignore TYPE UserLocationInformation PRESENCE optional }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- + +``` + +-- UE CONTEXT MODIFICATION FAILURE + +-- + +-- \*\*\*\*\* + +UEContextModificationFailure ::= SEQUENCE { + +    protocolIEs    ProtocolIE-Container    { {UEContextModificationFailureIEs} }, + +    ... + +} + +UEContextModificationFailureIEs NGAP-PROTOCOL-IES ::= { + +    { ID id-AMF-UE-NGAP-ID    CRITICALITY ignore    TYPE AMF-UE-NGAP-ID    PRESENCE mandatory }| + +    { ID id-RAN-UE-NGAP-ID    CRITICALITY ignore    TYPE RAN-UE-NGAP-ID    PRESENCE mandatory }| + +    { ID id-Cause    CRITICALITY ignore    TYPE Cause    PRESENCE mandatory }| + +    { ID id-CriticalityDiagnostics    CRITICALITY ignore    TYPE CriticalityDiagnostics    PRESENCE optional }, + +    ... + +} + +-- \*\*\*\*\* + +-- + +-- RRC INACTIVE TRANSITION REPORT + +-- + +-- \*\*\*\*\* + +``` + +RRCInactiveTransitionReport ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {RRCInactiveTransitionReportIEs} }, + ... +} + +``` + +``` + +RRCInactiveTransitionReportIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY reject TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-NGAP-ID CRITICALITY reject TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RRCState CRITICALITY ignore TYPE RRCState PRESENCE mandatory }| + { ID id-UserLocationInformation CRITICALITY ignore TYPE UserLocationInformation PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- Retrieve UE Information +-- +-- ***** + +``` + +``` + +RetrieveUEInformation ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { RetrieveUEInformationIEs} }, + ... +} + +``` + +``` +RetrieveUEInformationIEs NGAP-PROTOCOL-IES ::= { + { ID id-FiveG-S-TMSI CRITICALITY reject TYPE FiveG-S-TMSI PRESENCE mandatory }, + ... +} + +-- ***** + +-- UE Information Transfer +-- + +-- ***** + +UEInformationTransfer ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { UEInformationTransferIEs } }, + ... +} + +UEInformationTransferIEs NGAP-PROTOCOL-IES ::= { + { ID id-FiveG-S-TMSI CRITICALITY reject TYPE FiveG-S-TMSI PRESENCE mandatory }| + { ID id-NB-IoT-UEPriority CRITICALITY ignore TYPE NB-IoT-UEPriority PRESENCE optional }| + { ID id-UERadioCapability CRITICALITY ignore TYPE UERadioCapability PRESENCE optional }| + { ID id-S-NSSAI CRITICALITY ignore TYPE S-NSSAI PRESENCE optional }| +``` + +``` + + { ID id-AllowedNSSAI CRITICALITY ignore TYPE AllowedNSSAI PRESENCE optional }| + { ID id-UE-DifferentiationInfo CRITICALITY ignore TYPE UE-DifferentiationInfo PRESENCE optional }| + { ID id-MaskedIMEISV CRITICALITY ignore TYPE MaskedIMEISV PRESENCE optional }| + { ID id-Partially-Allowed-NSSAI CRITICALITY ignore TYPE Partially-Allowed-NSSAI PRESENCE optional }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- RAN CP Relocation Indication + +-- + +-- \*\*\*\*\* + +``` + +RANCPRelocationIndication ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { RANCPRelocationIndicationIEs} }, + ... +} + +``` + +``` + +RANCPRelocationIndicationIEs NGAP-PROTOCOL-IES ::= { + +``` + +``` + + { ID id-RAN-UE-NGAP-ID CRITICALITY reject TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-FiveG-S-TMSI CRITICALITY reject TYPE FiveG-S-TMSI PRESENCE mandatory }| + { ID id-EUTRA-CGI CRITICALITY ignore TYPE EUTRA-CGI PRESENCE mandatory }| + { ID id-TAI CRITICALITY ignore TYPE TAI PRESENCE mandatory }| + +``` + +``` + + { ID id-UL-CP-SecurityInformation CRITICALITY reject TYPE UL-CP-SecurityInformation PRESENCE mandatory }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- UE MOBILITY MANAGEMENT ELEMENTARY PROCEDURES + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- Handover Preparation Elementary Procedure + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- HANDOVER REQUIRED + +-- + +-- \*\*\*\*\* + +HandoverRequired ::= SEQUENCE { + +``` + +protocolIEs ProtocolIE-Container { {HandoverRequiredIEs} }, +... +} + +``` + +``` + +HandoverRequiredIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY reject TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-NGAP-ID CRITICALITY reject TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-HandoverType CRITICALITY reject TYPE HandoverType PRESENCE mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| + { ID id-TargetID CRITICALITY reject TYPE TargetID PRESENCE mandatory }| + { ID id-DirectForwardingPathAvailability CRITICALITY ignore TYPE DirectForwardingPathAvailability PRESENCE optional }| + { ID id-PDUSessionResourceListHORqd CRITICALITY reject TYPE PDUSessionResourceListHORqd PRESENCE mandatory }| + { ID id-SourceToTarget-TransparentContainer CRITICALITY reject TYPE SourceToTarget-TransparentContainer PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- HANDOVER COMMAND +-- +-- ***** + +``` + +``` + +HandoverCommand ::= SEQUENCE { + +``` + +``` + +protocolIEs ProtocolIE-Container { {HandoverCommandIEs} }, +... +} + +``` + +``` + +HandoverCommandIEs NGAP-PROTOCOL-IES ::= { + +``` + +``` + + { ID id-AMF-UE-NGAP-ID CRITICALITY reject TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-NGAP-ID CRITICALITY reject TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-HandoverType CRITICALITY reject TYPE HandoverType PRESENCE mandatory }| + { ID id-NASSecurityParametersFromNGRAN CRITICALITY reject TYPE NASSecurityParametersFromNGRAN PRESENCE conditional }| + -- This IE shall be present if HandoverType IE is set to value "5GStoEPPS" or "5GStoUTRAN" -- + { ID id-PDUSessionResourceHandoverList CRITICALITY ignore TYPE PDUSessionResourceHandoverList PRESENCE optional }| + { ID id-PDUSessionResourceToReleaseListHOCmd CRITICALITY ignore TYPE PDUSessionResourceToReleaseListHOCmd PRESENCE optional }| + { ID id-TargetToSource-TransparentContainer CRITICALITY reject TYPE TargetToSource-TransparentContainer PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- HANDOVER PREPARATION FAILURE +-- +-- ***** + +``` + +HandoverPreparationFailure ::= SEQUENCE { + +    protocolIEs    ProtocolIE-Container    { {HandoverPreparationFailureIEs} }, + +    ... + +} + +HandoverPreparationFailureIEs NGAP-PROTOCOL-IEs ::= { + +    { ID id-AMF-UE-NGAP-ID    CRITICALITY ignore    TYPE AMF-UE-NGAP-ID    PRESENCE mandatory }| + +    { ID id-RAN-UE-NGAP-ID    CRITICALITY ignore    TYPE RAN-UE-NGAP-ID    PRESENCE mandatory }| + +    { ID id-Cause    CRITICALITY ignore    TYPE Cause    PRESENCE mandatory }| + +    { ID id-CriticalityDiagnostics    CRITICALITY ignore    TYPE CriticalityDiagnostics    PRESENCE optional }| + +    { ID id-TargettoSource-Failure-TransparentContainer    CRITICALITY ignore    TYPE TargettoSource-Failure-TransparentContainer    PRESENCE optional +}, + +    ... + +} + +-- \*\*\*\*\* + +-- + +-- Handover Resource Allocation Elementary Procedure + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +``` + +-- +-- HANDOVER REQUEST +-- +-- ***** + +``` + +``` + +HandoverRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {HandoverRequestIEs} }, + ... +} + +``` + +``` + +HandoverRequestIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY reject TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + { ID id-HandoverType CRITICALITY reject TYPE HandoverType PRESENCE mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| + { ID id-UEAggregateMaximumBitRate CRITICALITY reject TYPE UEAggregateMaximumBitRate PRESENCE mandatory }| + { ID id-CoreNetworkAssistanceInformationForInactive CRITICALITY ignore TYPE CoreNetworkAssistanceInformationForInactive PRESENCE optional }| + { ID id-UESecurityCapabilities CRITICALITY reject TYPE UESecurityCapabilities PRESENCE mandatory }| + { ID id-SecurityContext CRITICALITY reject TYPE SecurityContext PRESENCE mandatory }| + { ID id-NewSecurityContextInd CRITICALITY reject TYPE NewSecurityContextInd PRESENCE optional }| + { ID id-NASC CRITICALITY reject TYPE NAS-PDU PRESENCE optional }| + { ID id-PDUSessionResourceSetupListHOReq CRITICALITY reject TYPE PDUSessionResourceSetupListHOReq PRESENCE mandatory }| + { ID id-AllowedNSSAI CRITICALITY reject TYPE AllowedNSSAI PRESENCE mandatory }| +} + +``` + +| | | | | | +|----------------------------------------------|--------------------|-------------------------------------------|--------------------|---| +| { ID id-TraceActivation | CRITICALITY ignore | TYPE TraceActivation | PRESENCE optional | } | +| { ID id-MaskedIMEISV | CRITICALITY ignore | TYPE MaskedIMEISV | PRESENCE optional | } | +| { ID id-SourceToTarget-TransparentContainer | CRITICALITY reject | TYPE SourceToTarget-TransparentContainer | PRESENCE mandatory | } | +| { ID id-MobilityRestrictionList | CRITICALITY ignore | TYPE MobilityRestrictionList | PRESENCE optional | } | +| { ID id-LocationReportingRequestType | CRITICALITY ignore | TYPE LocationReportingRequestType | PRESENCE optional | } | +| { ID id-RRCTransitionReportRequest | CRITICALITY ignore | TYPE RRCTransitionReportRequest | PRESENCE optional | } | +| { ID id-GUAMI | CRITICALITY reject | TYPE GUAMI | PRESENCE mandatory | } | +| { ID id-RedirectionVoiceFallback | CRITICALITY ignore | TYPE RedirectionVoiceFallback | PRESENCE optional | } | +| { ID id-CNAssistedRANTuning | CRITICALITY ignore | TYPE CNAssistedRANTuning | PRESENCE optional | } | +| { ID id-SRVCCOperationPossible | CRITICALITY ignore | TYPE SRVCCOperationPossible | PRESENCE optional | } | +| { ID id-IAB-Authorized | CRITICALITY reject | TYPE IAB-Authorized | PRESENCE optional | } | +| { ID id-Enhanced-CoverageRestriction | CRITICALITY ignore | TYPE Enhanced-CoverageRestriction | PRESENCE optional | } | +| { ID id-UE-DifferentiationInfo | CRITICALITY ignore | TYPE UE-DifferentiationInfo | 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-PC5QoSParameters | CRITICALITY ignore | TYPE PC5QoSParameters | PRESENCE optional | } | +| { ID id-CEmodeBrestricted | CRITICALITY ignore | TYPE CEmodeBrestricted | PRESENCE optional | } | +| { ID id-UE-UP-CIoT-Support | CRITICALITY ignore | TYPE UE-UP-CIoT-Support | PRESENCE optional | } | +| { ID id-ManagementBasedMDTPLMNList | CRITICALITY ignore | TYPE MDTPLMNList | PRESENCE optional | } | +| { ID id-UERadioCapabilityID | CRITICALITY reject | TYPE UERadioCapabilityID | PRESENCE optional | } | +| { ID id-Extended-ConnectedTime | CRITICALITY ignore | TYPE Extended-ConnectedTime | PRESENCE optional | } | + +``` + + { ID id-TimeSyncAssistanceInfo CRITICALITY ignore TYPE TimeSyncAssistanceInfo PRESENCE optional }| + { ID id-UESliceMaximumBitRateList CRITICALITY ignore TYPE UESliceMaximumBitRateList 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-ProSePC5QoSParameters CRITICALITY ignore TYPE FiveG-ProSePC5QoSParameters PRESENCE optional }| + { ID id-AerialUEsubscriptionInformation CRITICALITY ignore TYPE AerialUEsubscriptionInformation PRESENCE optional }| + { ID id-NR-A2X-ServicesAuthorized CRITICALITY ignore TYPE NR-A2X-ServicesAuthorized PRESENCE optional }| + { ID id-LTE-A2X-ServicesAuthorized CRITICALITY ignore TYPE LTE-A2X-ServicesAuthorized PRESENCE optional }| + { ID id-NR-A2X-UE-PC5-AggregateMaximumBitRate CRITICALITY ignore TYPE NRUESidelinkAggregateMaximumBitrate PRESENCE optional }| + { ID id-LTE-A2X-UE-PC5-AggregateMaximumBitRate CRITICALITY ignore TYPE LTEUESidelinkAggregateMaximumBitrate PRESENCE optional }| + { ID id-A2X-PC5-QoS-Parameters CRITICALITY ignore TYPE A2X-PC5-QoS-Parameters PRESENCE optional }| + { ID id-MobileIAB-Authorized CRITICALITY ignore TYPE MobileIAB-Authorized PRESENCE optional }| + { ID id-NoPDUSessionIndication CRITICALITY ignore TYPE NoPDUSessionIndication PRESENCE optional }| + { ID id-Partially-Allowed-NSSAI CRITICALITY ignore TYPE Partially-Allowed-NSSAI PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- HANDOVER REQUEST ACKNOWLEDGE +-- +-- ***** + +``` + +``` + +HandoverRequestAcknowledge ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {HandoverRequestAcknowledgeIEs} }, + ... +} + +``` + +``` + +HandoverRequestAcknowledgeIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY ignore TYPE AMF-UE-NGAP-ID PRESENCE mandatory } | + { ID id-RAN-UE-NGAP-ID CRITICALITY ignore TYPE RAN-UE-NGAP-ID PRESENCE mandatory } | + { ID id-PDUSessionResourceAdmittedList CRITICALITY ignore TYPE PDUSessionResourceAdmittedList PRESENCE mandatory } | + { ID id-PDUSessionResourceFailedToSetupListHOAck CRITICALITY ignore TYPE PDUSessionResourceFailedToSetupListHOAck PRESENCE optional } | + { ID id-TargetToSource-TransparentContainer CRITICALITY reject TYPE TargetToSource-TransparentContainer PRESENCE mandatory } | + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional } | + { ID id-NPN-AccessInformation CRITICALITY reject TYPE NPN-AccessInformation PRESENCE optional } | + { ID id-RedCapIndication CRITICALITY ignore TYPE RedCapIndication PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- HANDOVER FAILURE +-- +-- ***** + +``` + +``` + +HandoverFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { HandoverFailureIEs } }, + ... +} + +HandoverFailureIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY ignore TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }| + { ID id-TargettoSource-Failure-TransparentContainer CRITICALITY ignore TYPE TargettoSource-Failure-TransparentContainer PRESENCE optional + }, + ... +} + +``` + +-- \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* + +-- + +-- Handover Notification Elementary Procedure + +-- + +-- \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* + +-- \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* + +-- + +-- HANDOVER NOTIFY + +-- + +-- \*\*\*\*\* + +HandoverNotify ::= SEQUENCE { + +    protocolIEs    ProtocolIE-Container    { { HandoverNotifyIEs} }, + +    ... + +} + +HandoverNotifyIEs NGAP-PROTOCOL-IES ::= { + +    { ID id-AMF-UE-NGAP-ID    CRITICALITY reject    TYPE AMF-UE-NGAP-ID    PRESENCE mandatory }| + +    { ID id-RAN-UE-NGAP-ID    CRITICALITY reject    TYPE RAN-UE-NGAP-ID    PRESENCE mandatory }| + +    { ID id-UserLocationInformation    CRITICALITY ignore    TYPE UserLocationInformation    PRESENCE mandatory }| + +    { ID id-NotifySourceNGRANNode    CRITICALITY ignore    TYPE NotifySourceNGRANNode    PRESENCE optional }, + +    ... + +} + +-- \*\*\*\*\* + +-- + +-- Path Switch Request Elementary Procedure + +-- + +-- \*\*\*\*\* + +``` + +-- ***** +-- +-- PATH SWITCH REQUEST +-- +-- ***** + +``` + +``` + +PathSwitchRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { PathSwitchRequestIEs } }, + ... +} + +``` + +``` + +PathSwitchRequestIEs NGAP-PROTOCOL-IES ::= { + { ID id-RAN-UE-NGAP-ID CRITICALITY reject TYPE RAN-UE-NGAP-ID PRESENCE mandatory } | + { ID id-SourceAMF-UE-NGAP-ID CRITICALITY reject TYPE AMF-UE-NGAP-ID PRESENCE mandatory } | + { ID id-UserLocationInformation CRITICALITY ignore TYPE UserLocationInformation PRESENCE mandatory } | + { ID id-UESecurityCapabilities CRITICALITY ignore TYPE UESecurityCapabilities PRESENCE mandatory } | + { ID id-PDUSessionResourceToBeSwitchedDLList CRITICALITY reject TYPE PDUSessionResourceToBeSwitchedDLList PRESENCE mandatory } | + { ID id-PDUSessionResourceFailedToSetupListPSReq CRITICALITY ignore TYPE PDUSessionResourceFailedToSetupListPSReq PRESENCE optional } | + { ID id-RRC-Resume-Cause CRITICALITY ignore TYPE RRCEstablishmentCause PRESENCE optional } | + { ID id-RedCapIndication CRITICALITY ignore TYPE RedCapIndication PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- PATH SWITCH REQUEST ACKNOWLEDGE +-- +-- ***** + +``` + +``` + +PathSwitchRequestAcknowledge ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { PathSwitchRequestAcknowledgeIEs } }, + ... +} + +``` + +``` + +PathSwitchRequestAcknowledgeIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY ignore TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-NGAP-ID CRITICALITY ignore TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-UESecurityCapabilities CRITICALITY reject TYPE UESecurityCapabilities PRESENCE optional }| + { ID id-SecurityContext CRITICALITY reject TYPE SecurityContext PRESENCE mandatory }| + { ID id-NewSecurityContextInd CRITICALITY reject TYPE NewSecurityContextInd PRESENCE optional }| + { ID id-PDUSessionResourceSwitchedList CRITICALITY ignore TYPE PDUSessionResourceSwitchedList PRESENCE mandatory }| + { ID id-PDUSessionResourceReleasedListPSAck CRITICALITY ignore TYPE PDUSessionResourceReleasedListPSAck PRESENCE optional }| + { ID id-AllowedNSSAI CRITICALITY reject TYPE AllowedNSSAI PRESENCE mandatory }| + { ID id-CoreNetworkAssistanceInformationForInactive CRITICALITY ignore TYPE CoreNetworkAssistanceInformationForInactive PRESENCE optional }| +} + +``` + +``` + +{ ID id-RRInactiveTransitionReportRequest CRITICALITY ignore TYPE RRCInactiveTransitionReportRequest PRESENCE optional }| +{ ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }| +{ ID id-RedirectionVoiceFallback CRITICALITY ignore TYPE RedirectionVoiceFallback PRESENCE optional }| +{ ID id-CNAssistedRANTuning CRITICALITY ignore TYPE CNAssistedRANTuning PRESENCE optional }| +{ ID id-SRVCCOperationPossible CRITICALITY ignore TYPE SRVCCOperationPossible PRESENCE optional }| +{ ID id-Enhanced-CoverageRestriction CRITICALITY ignore TYPE Enhanced-CoverageRestriction PRESENCE optional }| +{ ID id-Extended-ConnectedTime CRITICALITY ignore TYPE Extended-ConnectedTime PRESENCE optional }| +{ ID id-UE-DifferentiationInfo CRITICALITY ignore TYPE UE-DifferentiationInfo 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-PC5QoSParameters CRITICALITY ignore TYPE PC5QoSParameters PRESENCE optional }| +{ ID id-CEmodeBrestricted CRITICALITY ignore TYPE CEmodeBrestricted PRESENCE optional }| +{ ID id-UE-UP-CIoT-Support CRITICALITY ignore TYPE UE-UP-CIoT-Support PRESENCE optional }| +{ ID id-UERadioCapabilityID CRITICALITY reject TYPE UERadioCapabilityID PRESENCE optional }| +{ ID id-ManagementBasedMDTPLMNList CRITICALITY ignore TYPE MDTPLMNList PRESENCE optional }| +{ ID id-TimeSyncAssistanceInfo CRITICALITY ignore TYPE TimeSyncAssistanceInfo 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-ProSePC5QoSParameters CRITICALITY ignore TYPE FiveG-ProSePC5QoSParameters PRESENCE optional }| +{ ID id-ManagementBasedMDTPLMNModificationList CRITICALITY ignore TYPE MDTPLMNModificationList PRESENCE optional }| +{ ID id-IAB-Authorized CRITICALITY ignore TYPE IAB-Authorized PRESENCE optional }| + +``` + +``` + + { ID id-AerialUEsubscriptionInformation CRITICALITY ignore TYPE AerialUEsubscriptionInformation PRESENCE optional }| + { ID id-NR-A2X-ServicesAuthorized CRITICALITY ignore TYPE NR-A2X-ServicesAuthorized PRESENCE optional }| + { ID id-LTE-A2X-ServicesAuthorized CRITICALITY ignore TYPE LTE-A2X-ServicesAuthorized PRESENCE optional }| + { ID id-NR-A2X-UE-PC5-AggregateMaximumBitRate CRITICALITY ignore TYPE NRUESidelinkAggregateMaximumBitrate PRESENCE optional }| + { ID id-LTE-A2X-UE-PC5-AggregateMaximumBitRate CRITICALITY ignore TYPE LTEUESidelinkAggregateMaximumBitrate PRESENCE optional }| + { ID id-A2X-PC5-QoS-Parameters CRITICALITY ignore TYPE A2X-PC5-QoS-Parameters PRESENCE optional }| + { ID id-MobileIAB-Authorized CRITICALITY ignore TYPE MobileIAB-Authorized PRESENCE optional }| + { ID id-Partially-Allowed-NSSAI CRITICALITY ignore TYPE Partially-Allowed-NSSAI PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- PATH SWITCH REQUEST FAILURE +-- +-- ***** + +``` + +``` + +PathSwitchRequestFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { PathSwitchRequestFailureIEs } }, + ... +} + +``` + +``` + +PathSwitchRequestFailureIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY ignore TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-NGAP-ID CRITICALITY ignore TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-PDUSessionResourceReleasedListPSFail CRITICALITY ignore TYPE PDUSessionResourceReleasedListPSFail PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- Handover Cancellation Elementary Procedure + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- HANDOVER CANCEL + +-- + +-- \*\*\*\*\* + +``` + +HandoverCancel ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { HandoverCancelIEs } }, + ... +} + +``` + +} + +HandoverCancelIEs NGAP-PROTOCOL-IES ::= { + +{ ID id-AMF-UE-NGAP-ID      CRITICALITY reject    TYPE AMF-UE-NGAP-ID      PRESENCE mandatory }| +{ ID id-RAN-UE-NGAP-ID      CRITICALITY reject    TYPE RAN-UE-NGAP-ID     PRESENCE mandatory }| +{ ID id-Cause                CRITICALITY ignore    TYPE Cause                PRESENCE mandatory }, +... + +} + +-- \*\*\*\*\* + +-- + +-- HANDOVER CANCEL ACKNOWLEDGE + +-- + +-- \*\*\*\*\* + +HandoverCancelAcknowledge ::= SEQUENCE { + +protocolIEs      ProtocolIE-Container      { { HandoverCancelAcknowledgeIEs} }, +... + +} + +HandoverCancelAcknowledgeIEs NGAP-PROTOCOL-IES ::= { + +{ ID id-AMF-UE-NGAP-ID      CRITICALITY ignore    TYPE AMF-UE-NGAP-ID      PRESENCE mandatory }| +{ ID id-RAN-UE-NGAP-ID      CRITICALITY ignore    TYPE RAN-UE-NGAP-ID     PRESENCE mandatory }| + +``` + + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- HANDOVER SUCCESS ELEMENTARY PROCEDURE + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- HANDOVER SUCCESS + +-- + +-- \*\*\*\*\* + +``` + +HandoverSuccess ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { HandoverSuccessIEs } }, + ... +} + +``` + +``` + +HandoverSuccessIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY reject TYPE AMF-UE-NGAP-ID PRESENCE mandatory } | + +``` + +``` + + { ID id-RAN-UE-NGAP-ID CRITICALITY reject TYPE RAN-UE-NGAP-ID PRESENCE mandatory }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- UPLINK RAN EARLY STATUS TRANSFER ELEMENTARY PROCEDURE + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- Uplink RAN Early Status Transfer + +-- + +-- \*\*\*\*\* + +``` + +UplinkRANEarlyStatusTransfer ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {UplinkRANEarlyStatusTransferIEs} }, + ... +} + +``` + +``` + +UplinkRANEarlyStatusTransferIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY reject TYPE AMF-UE-NGAP-ID PRESENCE mandatory } | + +``` + +``` + + { ID id-RAN-UE-NGAP-ID CRITICALITY reject TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-EarlyStatusTransfer-TransparentContainer CRITICALITY reject TYPE EarlyStatusTransfer-TransparentContainer PRESENCE mandatory }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- DOWNLINK RAN EARLY STATUS TRANSFER ELEMENTARY PROCEDURE + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- Downlink RAN Early Status Transfer + +-- + +-- \*\*\*\*\* + +``` + +DownlinkRANEarlyStatusTransfer ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {DownlinkRANEarlyStatusTransferIEs} }, + ... +} + +``` + +``` + +DownlinkRANEarlyStatusTransferIEs NGAP-PROTOCOL-IES ::= { + +``` + +``` + + { ID id-AMF-UE-NGAP-ID CRITICALITY reject TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-NGAP-ID CRITICALITY reject TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-EarlyStatusTransfer-TransparentContainer CRITICALITY reject TYPE EarlyStatusTransfer-TransparentContainer PRESENCE mandatory }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- Uplink RAN Status Transfer Elementary Procedure + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- UPLINK RAN STATUS TRANSFER + +-- + +-- \*\*\*\*\* + +``` + +UplinkRANStatusTransfer ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {UplinkRANStatusTransferIEs} }, + ... +} + +``` + +``` + +UplinkRANStatusTransferIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY reject TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-NGAP-ID CRITICALITY reject TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RANStatusTransfer-TransparentContainer CRITICALITY reject TYPE RANStatusTransfer-TransparentContainer PRESENCE mandatory }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- Downlink RAN Status Transfer Elementary Procedure + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- DOWNLINK RAN STATUS TRANSFER + +-- + +-- \*\*\*\*\* + +``` + +DownlinkRANStatusTransfer ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {DownlinkRANStatusTransferIEs} }, + ... +} + +``` + +} + +DownlinkRANStatusTransferIEs NGAP-PROTOCOL-IES ::= { + +{ ID id-AMF-UE-NGAP-ID                                    CRITICALITY reject    TYPE AMF-UE-NGAP-ID                                    PRESENCE mandatory } | + +{ ID id-RAN-UE-NGAP-ID                                    CRITICALITY reject    TYPE RAN-UE-NGAP-ID                                    PRESENCE mandatory } | + +{ ID id-RANStatusTransfer-TransparentContainer    CRITICALITY reject    TYPE RANStatusTransfer-TransparentContainer    PRESENCE mandatory }, + +... + +} + +-- \*\*\*\*\* + +-- + +-- PAGING ELEMENTARY PROCEDURE + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- PAGING + +-- + +-- \*\*\*\*\* + +Paging ::= SEQUENCE { + +protocolIEs      ProtocolIE-Container      { {PagingIEs} }, + +``` + + ... +} + +PagingIEs NGAP-PROTOCOL-IES ::= { + { ID id-UEPagingIdentity CRITICALITY ignore TYPE UEPagingIdentity PRESENCE mandatory }| + { ID id-PagingDRX CRITICALITY ignore TYPE PagingDRX PRESENCE optional }| + { ID id-TAIListForPaging CRITICALITY ignore TYPE TAIListForPaging PRESENCE mandatory }| + { ID id-PagingPriority CRITICALITY ignore TYPE PagingPriority PRESENCE optional }| + { ID id-UERadioCapabilityForPaging CRITICALITY ignore TYPE UERadioCapabilityForPaging PRESENCE optional }| + { ID id-PagingOrigin CRITICALITY ignore TYPE PagingOrigin PRESENCE optional }| + { ID id-AssistanceDataForPaging CRITICALITY ignore TYPE AssistanceDataForPaging PRESENCE optional }| + { ID id-NB-IoT-Paging-eDRXInfo CRITICALITY ignore TYPE NB-IoT-Paging-eDRXInfo PRESENCE optional }| + { ID id-NB-IoT-PagingDRX CRITICALITY ignore TYPE NB-IoT-PagingDRX PRESENCE optional }| + { ID id-Enhanced-CoverageRestriction CRITICALITY ignore TYPE Enhanced-CoverageRestriction PRESENCE optional }| + { ID id-WUS-Assistance-Information CRITICALITY ignore TYPE WUS-Assistance-Information PRESENCE optional }| + { ID id-EUTRA-PagingeDRXInformation CRITICALITY ignore TYPE EUTRA-PagingeDRXInformation PRESENCE optional }| + { ID id-CEmodeBrestricted CRITICALITY ignore TYPE CEmodeBrestricted PRESENCE optional }| + { ID id-NR-PagingeDRXInformation CRITICALITY ignore TYPE NR-PagingeDRXInformation PRESENCE optional }| + { ID id-PagingCause CRITICALITY ignore TYPE PagingCause PRESENCE optional }| + { ID id-PEIPSassistanceInformation CRITICALITY ignore TYPE PEIPSassistanceInformation PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- NAS TRANSPORT ELEMENTARY PROCEDURES +-- +-- ***** +-- +-- ***** +-- +-- INITIAL UE MESSAGE +-- +-- ***** + +``` + +``` + +InitialUEMessage ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {InitialUEMessage-IEs} }, + ... +} + +``` + +``` + +InitialUEMessage-IEs NGAP-PROTOCOL-IES ::= { + { ID id-RAN-UE-NGAP-ID CRITICALITY reject TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-NAS-PDU CRITICALITY reject TYPE NAS-PDU PRESENCE mandatory }| + { ID id-UserLocationInformation CRITICALITY reject TYPE UserLocationInformation PRESENCE mandatory }| + { ID id-RRCEstablishmentCause CRITICALITY ignore TYPE RRCEstablishmentCause PRESENCE mandatory }| + { ID id-FiveG-S-TMSI CRITICALITY reject TYPE FiveG-S-TMSI PRESENCE optional }| +} + +``` + +``` + + { ID id-AMFSetID CRITICALITY ignore TYPE AMFSetID PRESENCE optional }| + { ID id-UEContextRequest CRITICALITY ignore TYPE UEContextRequest PRESENCE optional }| + { ID id-AllowedNSSAI CRITICALITY reject TYPE AllowedNSSAI PRESENCE optional }| + { ID id-SourceToTarget-AMFInformationReroute CRITICALITY ignore TYPE SourceToTarget-AMFInformationReroute PRESENCE optional }| + { ID id-SelectedPLMNIdentity CRITICALITY ignore TYPE PLMNIdentity PRESENCE optional }| + { ID id-IABNodeIndication CRITICALITY reject TYPE IABNodeIndication PRESENCE optional }| + { ID id-CEmodeBSupport-Indicator CRITICALITY reject TYPE CEmodeBSupport-Indicator PRESENCE optional }| + { ID id-LTEM-Indication CRITICALITY ignore TYPE LTEM-Indication PRESENCE optional }| + { ID id-EDT-Session CRITICALITY ignore TYPE EDT-Session PRESENCE optional }| + { ID id-AuthenticatedIndication CRITICALITY ignore TYPE AuthenticatedIndication PRESENCE optional }| + { ID id-NPN-AccessInformation CRITICALITY reject TYPE NPN-AccessInformation PRESENCE optional }| + { ID id-RedCapIndication CRITICALITY ignore TYPE RedCapIndication PRESENCE optional }| + { ID id-SelectedNID CRITICALITY ignore TYPE NID PRESENCE optional }| + { ID id-MobileIABNodeIndication CRITICALITY reject TYPE MobileIABNodeIndication PRESENCE optional }| + { ID id-Partially-Allowed-NSSAI CRITICALITY ignore TYPE Partially-Allowed-NSSAI PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- DOWNLINK NAS TRANSPORT +-- +-- ***** + +``` + +``` +DownlinkNASTransport ::= SEQUENCE { +``` + +``` + protocolIEs ProtocolIE-Container { {DownlinkNASTransport-IEs} }, +``` + +``` + ... +``` + +``` +} +``` + +``` +DownlinkNASTransport-IEs NGAP-PROTOCOL-IEs ::= { +``` + +``` + { ID id-AMF-UE-NGAP-ID CRITICALITY reject TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-NGAP-ID CRITICALITY reject TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-OldAMF CRITICALITY reject TYPE AMFName PRESENCE optional }| + { ID id-RANPagingPriority CRITICALITY ignore TYPE RANPagingPriority PRESENCE optional }| + { ID id-NAS-PDU CRITICALITY reject TYPE NAS-PDU PRESENCE mandatory }| + { ID id-MobilityRestrictionList CRITICALITY ignore TYPE MobilityRestrictionList PRESENCE optional }| + { ID id-IndexToRFSP CRITICALITY ignore TYPE IndexToRFSP PRESENCE optional }| + { ID id-UEAggregateMaximumBitRate CRITICALITY ignore TYPE UEAggregateMaximumBitRate PRESENCE optional }| + { ID id-AllowedNSSAI CRITICALITY reject TYPE AllowedNSSAI PRESENCE optional }| + { ID id-SRVCCOperationPossible CRITICALITY ignore TYPE SRVCCOperationPossible PRESENCE optional }| + { ID id-Enhanced-CoverageRestriction CRITICALITY ignore TYPE Enhanced-CoverageRestriction PRESENCE optional }| + { ID id-Extended-ConnectedTime CRITICALITY ignore TYPE Extended-ConnectedTime PRESENCE optional }| + { ID id-UE-DifferentiationInfo CRITICALITY ignore TYPE UE-DifferentiationInfo PRESENCE optional }| + { ID id-CEmodeBrestricted CRITICALITY ignore TYPE CEmodeBrestricted PRESENCE optional }| + { ID id-UERadioCapability CRITICALITY ignore TYPE UERadioCapability PRESENCE optional }| + { ID id-UECapabilityInfoRequest CRITICALITY ignore TYPE UECapabilityInfoRequest PRESENCE optional }| +``` + +``` + + { ID id-EndIndication CRITICALITY ignore TYPE EndIndication PRESENCE optional }| + { ID id-UERadioCapabilityID CRITICALITY reject TYPE UERadioCapabilityID PRESENCE optional }| + { ID id-TargetNSSAIInformation CRITICALITY ignore TYPE TargetNSSAIInformation PRESENCE optional }| + { ID id-MaskedIMEISV CRITICALITY ignore TYPE MaskedIMEISV PRESENCE optional }| + { ID id-Partially-Allowed-NSSAI CRITICALITY ignore TYPE Partially-Allowed-NSSAI PRESENCE optional }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- UPLINK NAS TRANSPORT + +-- + +-- \*\*\*\*\* + +``` + +UplinkNASTransport ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {UplinkNASTransport-IEs} }, + ... +} + +``` + +``` + +UplinkNASTransport-IEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY reject TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-NGAP-ID CRITICALITY reject TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-NAS-PDU CRITICALITY reject TYPE NAS-PDU PRESENCE mandatory }| +} + +``` + +``` + + { ID id-UserLocationInformation CRITICALITY ignore TYPE UserLocationInformation PRESENCE mandatory }| + { ID id-W-AGFIdentityInformation CRITICALITY reject TYPE OCTET STRING PRESENCE optional }| + { ID id-TNGFIdentityInformation CRITICALITY reject TYPE OCTET STRING PRESENCE optional }| + { ID id-TWIFIdentityInformation CRITICALITY reject TYPE OCTET STRING PRESENCE optional }, + ... +} + +``` + +``` +-- ***** +``` + +``` +-- +``` + +``` +-- NAS NON DELIVERY INDICATION +``` + +``` +-- +``` + +``` +-- ***** +``` + +``` + +NASNonDeliveryIndication ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {NASNonDeliveryIndication-IEs} }, + ... +} + +``` + +``` + +NASNonDeliveryIndication-IEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY reject TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-NGAP-ID CRITICALITY reject TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-NAS-PDU CRITICALITY ignore TYPE NAS-PDU PRESENCE mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }, + +``` + +``` + + ... + } + + -- ***** + -- + -- REROUTE NAS REQUEST + -- + -- ***** + +``` + +``` + +RerouteNASRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {RerouteNASRequest-IEs} }, + ... +} + +``` + +``` + +RerouteNASRequest-IEs NGAP-PROTOCOL-IES ::= { + { ID id-RAN-UE-NGAP-ID CRITICALITY reject TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-AMF-UE-NGAP-ID CRITICALITY ignore TYPE AMF-UE-NGAP-ID PRESENCE optional }| + { ID id-NGAP-Message CRITICALITY reject TYPE OCTET STRING PRESENCE mandatory }| + { ID id-AMFSetID CRITICALITY reject TYPE AMFSetID PRESENCE mandatory }| + { ID id-AllowedNSSAI CRITICALITY reject TYPE AllowedNSSAI PRESENCE optional }| + { ID id-SourceToTarget-AMFInformationReroute CRITICALITY ignore TYPE SourceToTarget-AMFInformationReroute PRESENCE optional }| + { ID id-Partially-Allowed-NSSAI CRITICALITY ignore TYPE Partially-Allowed-NSSAI PRESENCE optional }, + ... +} + +``` + +``` + +} + +-- ***** +-- +-- INTERFACE MANAGEMENT ELEMENTARY PROCEDURES +-- +-- ***** +-- +-- ***** +-- +-- NG Setup Elementary Procedure +-- +-- ***** +-- +-- ***** +-- +-- NG SETUP REQUEST +-- +-- ***** + +NGSetupRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {NGSetupRequestIEs} }, + ... +} + +``` + +``` + +} + +NGSetupRequestIEs NGAP-PROTOCOL-IES ::= { + { ID id-GlobalRANNodeID CRITICALITY reject TYPE GlobalRANNodeID PRESENCE mandatory }| + { ID id-RANNodeName CRITICALITY ignore TYPE RANNodeName PRESENCE optional }| + { ID id-SupportedTAList CRITICALITY reject TYPE SupportedTAList PRESENCE mandatory }| + { ID id-DefaultPagingDRX CRITICALITY ignore TYPE PagingDRX PRESENCE mandatory }| + { ID id-UERetentionInformation CRITICALITY ignore TYPE UERetentionInformation PRESENCE optional }| + { ID id-NB-IoT-DefaultPagingDRX CRITICALITY ignore TYPE NB-IoT-DefaultPagingDRX PRESENCE optional }| + { ID id-Extended-RANNodeName CRITICALITY ignore TYPE Extended-RANNodeName PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- NG SETUP RESPONSE +-- +-- ***** + +``` + +``` + +NGSetupResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {NGSetupResponseIEs} }, + ... +} + +``` + +``` + +NGSetupResponseIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMFName CRITICALITY reject TYPE AMFName PRESENCE mandatory }| + { ID id-ServedGUAMIList CRITICALITY reject TYPE ServedGUAMIList PRESENCE mandatory }| + { ID id-RelativeAMFCapacity CRITICALITY ignore TYPE RelativeAMFCapacity PRESENCE mandatory }| + { ID id-PLMNSupportList CRITICALITY reject TYPE PLMNSupportList PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }| + { ID id-URetentionInformation CRITICALITY ignore TYPE URetentionInformation PRESENCE optional }| + { ID id-IAB-Supported CRITICALITY ignore TYPE IAB-Supported PRESENCE optional }| + { ID id-Extended-AMFName CRITICALITY ignore TYPE Extended-AMFName PRESENCE optional }| + { ID id-MobileIAB-Supported CRITICALITY ignore TYPE MobileIAB-Supported PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- NG SETUP FAILURE +-- +-- ***** + +``` + +``` + +NGSetupFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {NGSetupFailureIEs} }, + ... +} + +``` + +``` + +} + +NGSetupFailureIEs NGAP-PROTOCOL-IES ::= { + { 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 }, + ... +} + +``` + +``` + +-- ***** +-- +-- RAN Configuration Update Elementary Procedure +-- +-- ***** +-- +-- ***** +-- +-- RAN CONFIGURATION UPDATE +-- +-- ***** + +``` + +``` + +RANConfigurationUpdate ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {RANConfigurationUpdateIEs} }, + +``` + +... +} + +RANConfigurationUpdateIEs NGAP-PROTOCOL-IES ::= { + +| | | | | +|------------------------------------------|--------------------|---------------------------------------|----------------------| +| { ID id-RANNodeName | CRITICALITY ignore | TYPE RANNodeName | PRESENCE optional | +| { ID id-SupportedTAList | CRITICALITY reject | TYPE SupportedTAList | PRESENCE optional | +| { ID id-DefaultPagingDRX | CRITICALITY ignore | TYPE PagingDRX | PRESENCE optional | +| { ID id-GlobalRANNodeID | CRITICALITY ignore | TYPE GlobalRANNodeID | PRESENCE optional | +| { ID id-NGRAN-TNLAssociationToRemoveList | CRITICALITY reject | TYPE NGRAN-TNLAssociationToRemoveList | PRESENCE optional | +| { ID id-NB-IoT-DefaultPagingDRX | CRITICALITY ignore | TYPE NB-IoT-DefaultPagingDRX | PRESENCE optional | +| { ID id-Extended-RANNodeName | CRITICALITY ignore | TYPE Extended-RANNodeName | PRESENCE optional ), | + +... +} + +-- \*\*\*\*\* + +-- + +-- RAN CONFIGURATION UPDATE ACKNOWLEDGE + +-- + +-- \*\*\*\*\* + +RANConfigurationUpdateAcknowledge ::= SEQUENCE { + +| | | | +|-------------|----------------------|---------------------------------------------| +| protocolIEs | ProtocolIE-Container | { {RANConfigurationUpdateAcknowledgeIEs} }, | +|-------------|----------------------|---------------------------------------------| + +... + +``` + +} + +RANConfigurationUpdateAcknowledgeIEs NGAP-PROTOCOL-IES ::= { + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +-- ***** +-- +-- RAN CONFIGURATION UPDATE FAILURE +-- +-- ***** + +RANConfigurationUpdateFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {RANConfigurationUpdateFailureIEs} }, + ... +} + +RANConfigurationUpdateFailureIEs NGAP-PROTOCOL-IES ::= { + { 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 }, + ... +} + +``` + +} + +-- \*\*\*\*\* + +-- + +-- AMF Configuration Update Elementary Procedure + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- AMF CONFIGURATION UPDATE + +-- + +-- \*\*\*\*\* + +AMFConfigurationUpdate ::= SEQUENCE { + +    protocolIEs    ProtocolIE-Container    { {AMFConfigurationUpdateIEs} }, + +    ... + +} + +AMFConfigurationUpdateIEs NGAP-PROTOCOL-IES ::= { + +| | | | | | +|-----------------------------|--------------------|--------------------------|-------------------|--| +| { ID id-AMFName | CRITICALITY reject | TYPE AMFName | PRESENCE optional | | +| { ID id-ServedGUAMIList | CRITICALITY reject | TYPE ServedGUAMIList | PRESENCE optional | | +| { ID id-RelativeAMFCapacity | CRITICALITY ignore | TYPE RelativeAMFCapacity | PRESENCE optional | | + +``` + + { ID id-PLMNSupportList CRITICALITY reject TYPE PLMNSupportList PRESENCE optional }| + { ID id-AMF-TNLAssociationToAddList CRITICALITY ignore TYPE AMF-TNLAssociationToAddList PRESENCE optional }| + { ID id-AMF-TNLAssociationToRemoveList CRITICALITY ignore TYPE AMF-TNLAssociationToRemoveList PRESENCE optional }| + { ID id-AMF-TNLAssociationToUpdateList CRITICALITY ignore TYPE AMF-TNLAssociationToUpdateList PRESENCE optional }| + { ID id-Extended-AMFName CRITICALITY ignore TYPE Extended-AMFName PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- AMF CONFIGURATION UPDATE ACKNOWLEDGE +-- +-- ***** + +``` + +``` + +AMFConfigurationUpdateAcknowledge ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {AMFConfigurationUpdateAcknowledgeIEs} }, + ... +} + +``` + +``` + +AMFConfigurationUpdateAcknowledgeIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-TNLAssociationSetupList CRITICALITY ignore TYPE AMF-TNLAssociationSetupList PRESENCE optional }| + { ID id-AMF-TNLAssociationFailedToSetupList CRITICALITY ignore TYPE TNLAssociationList PRESENCE optional }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + +``` + +``` + + ... + } + + -- ***** + -- + -- AMF CONFIGURATION UPDATE FAILURE + -- + -- ***** + + AMFConfigurationUpdateFailure := SEQUENCE { + protocolIEs ProtocolIE-Container { {AMFConfigurationUpdateFailureIEs} }, + ... + } + + AMFConfigurationUpdateFailureIEs NGAP-PROTOCOL-IES := { + { 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 }, + ... + } + + -- ***** + -- + +``` + +-- AMF Status Indication Elementary Procedure + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- AMF STATUS INDICATION + +-- + +-- \*\*\*\*\* + +AMFStatusIndication ::= SEQUENCE { + +    protocolIEs    ProtocolIE-Container    { {AMFStatusIndicationIEs} }, + +    ... + +} + +AMFStatusIndicationIEs NGAP-PROTOCOL-IES ::= { + +    { ID id-UnavailableGUAMIList    CRITICALITY reject    TYPE UnavailableGUAMIList    PRESENCE mandatory }, + +    ... + +} + +-- \*\*\*\*\* + +-- + +-- NG Reset Elementary Procedure + +``` + +-- +-- ***** +-- ***** +-- +-- NG RESET +-- +-- ***** + +``` + +``` + +NGReset ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {NGResetIEs} }, + ... +} + +``` + +``` + +NGResetIEs NGAP-PROTOCOL-IES ::= { + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| + { ID id-ResetType CRITICALITY reject TYPE ResetType PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- NG RESET ACKNOWLEDGE + +``` + +-- + +-- \*\*\*\*\* + +NGResetAcknowledge ::= SEQUENCE { + +    protocolIEs    ProtocolIE-Container    { {NGResetAcknowledgeIEs} }, + +    ... + +} + +NGResetAcknowledgeIEs NGAP-PROTOCOL-IES ::= { + +    { ID id-UE-associatedLogicalNG-connectionList    CRITICALITY ignore    TYPE UE-associatedLogicalNG-connectionList    PRESENCE optional }| + +    { ID id-CriticalityDiagnostics    CRITICALITY ignore    TYPE CriticalityDiagnostics    PRESENCE optional }, + +    ... + +} + +-- \*\*\*\*\* + +-- + +-- Error Indication Elementary Procedure + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- ERROR INDICATION + +-- +-- \*\*\*\*\* + +ErrorIndication ::= SEQUENCE { +    protocolIEs    ProtocolIE-Container    { {ErrorIndicationIEs} }, +    ... +} + +ErrorIndicationIEs NGAP-PROTOCOL-IES ::= { +    { ID id-AMF-UE-NGAP-ID    CRITICALITY ignore    TYPE AMF-UE-NGAP-ID    PRESENCE optional }| +    { ID id-RAN-UE-NGAP-ID    CRITICALITY ignore    TYPE RAN-UE-NGAP-ID    PRESENCE optional }| +    { ID id-Cause    CRITICALITY ignore    TYPE Cause    PRESENCE optional }| +    { ID id-CriticalityDiagnostics    CRITICALITY ignore    TYPE CriticalityDiagnostics    PRESENCE optional }| +    { ID id-FiveG-S-TMSI    CRITICALITY ignore    TYPE FiveG-S-TMSI    PRESENCE optional }, +    ... +} + +-- \*\*\*\*\* +-- +-- OVERLOAD START +-- +-- \*\*\*\*\* + +OverloadStart ::= SEQUENCE { + +    protocolIEs    ProtocolIE-Container    { {OverloadStartIEs} }, + +    ... + +} + +OverloadStartIEs NGAP-PROTOCOL-IES ::= { + +    { ID id-AMFOverloadResponse                    CRITICALITY reject  TYPE OverloadResponse          PRESENCE optional  }| + +    { ID id-AMFTrafficLoadReductionIndication    CRITICALITY ignore  TYPE TrafficLoadReductionIndication  PRESENCE optional  }| + +    { ID id-OverloadStartNSSAIList                CRITICALITY ignore  TYPE OverloadStartNSSAIList          PRESENCE optional  }, + +    ... + +} + +-- \*\*\*\*\* + +-- + +-- OVERLOAD STOP + +-- + +-- \*\*\*\*\* + +OverloadStop ::= SEQUENCE { + +    protocolIEs    ProtocolIE-Container    { {OverloadStopIEs} }, + +    ... + +} + +OverloadStopIEs NGAP-PROTOCOL-IES ::= { + +... +} + +-- \*\*\*\*\* + +-- + +-- CONFIGURATION TRANSFER ELEMENTARY PROCEDURES + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- UPLINK RAN CONFIGURATION TRANSFER + +-- + +-- \*\*\*\*\* + +UplinkRANConfigurationTransfer ::= SEQUENCE { + +protocolIEs ProtocolIE-Container { {UplinkRANConfigurationTransferIEs} }, + +... +} + +UplinkRANConfigurationTransferIEs NGAP-PROTOCOL-IES ::= { + +{ ID id-SONConfigurationTransferUL CRITICALITY ignore TYPE SONConfigurationTransfer PRESENCE optional }| + +``` + + { ID id-ENDC-SONConfigurationTransferUL CRITICALITY ignore TYPE EN-DCSONConfigurationTransfer PRESENCE optional }| + { ID id-IntersystemSONConfigurationTransferUL CRITICALITY ignore TYPE IntersystemSONConfigurationTransfer PRESENCE optional }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- DOWNLINK RAN CONFIGURATION TRANSFER + +-- + +-- \*\*\*\*\* + +``` + +DownlinkRANConfigurationTransfer ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {DownlinkRANConfigurationTransferIEs} }, + ... +} + +``` + +``` + +DownlinkRANConfigurationTransferIEs NGAP-PROTOCOL-IES ::= { + { ID id-SONConfigurationTransferDL CRITICALITY ignore TYPE SONConfigurationTransfer PRESENCE optional }| + { ID id-ENDC-SONConfigurationTransferDL CRITICALITY ignore TYPE EN-DCSONConfigurationTransfer PRESENCE optional }| + { ID id-IntersystemSONConfigurationTransferDL CRITICALITY ignore TYPE IntersystemSONConfigurationTransfer PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- WARNING MESSAGE TRANSMISSION ELEMENTARY PROCEDURES +-- +-- ***** +-- +-- ***** +-- +-- Write-Replace Warning Elementary Procedure +-- +-- ***** +-- +-- ***** +-- +-- WRITE-REPLACE WARNING REQUEST +-- +-- ***** + +``` + +``` + +WriteReplaceWarningRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {WriteReplaceWarningRequestIEs} }, + ... +} + +``` + +``` + +WriteReplaceWarningRequestIEs NGAP-PROTOCOL-IEs ::= { + { ID id-MessageIdentifier CRITICALITY reject TYPE MessageIdentifier PRESENCE mandatory }| + { ID id-SerialNumber CRITICALITY reject TYPE SerialNumber PRESENCE mandatory }| + { ID id-WarningAreaList CRITICALITY ignore TYPE WarningAreaList PRESENCE optional }| + { ID id-RepetitionPeriod CRITICALITY reject TYPE RepetitionPeriod PRESENCE mandatory }| + { ID id-NumberOfBroadcastsRequested CRITICALITY reject TYPE NumberOfBroadcastsRequested PRESENCE mandatory }| + { ID id-WarningType CRITICALITY ignore TYPE WarningType PRESENCE optional }| + { ID id-WarningSecurityInfo CRITICALITY ignore TYPE WarningSecurityInfo PRESENCE optional }| + { ID id-DataCodingScheme CRITICALITY ignore TYPE DataCodingScheme PRESENCE optional }| + { ID id-WarningMessageContents CRITICALITY ignore TYPE WarningMessageContents PRESENCE optional }| + { ID id-ConcurrentWarningMessageInd CRITICALITY reject TYPE ConcurrentWarningMessageInd PRESENCE optional }| + { ID id-WarningAreaCoordinates CRITICALITY ignore TYPE WarningAreaCoordinates PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- WRITE-REPLACE WARNING RESPONSE +-- +-- ***** + +``` + +``` + +WriteReplaceWarningResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {WriteReplaceWarningResponseIEs} }, + +``` + +... +} + +WriteReplaceWarningResponseIEs NGAP-PROTOCOL-IES ::= { + +| | | | | | +|------------------------------------|--------------------|---------------------------------|--------------------|----| +| { ID id-MessageIdentifier | CRITICALITY reject | TYPE MessageIdentifier | PRESENCE mandatory | } | +| { ID id-SerialNumber | CRITICALITY reject | TYPE SerialNumber | PRESENCE mandatory | } | +| { ID id-BroadcastCompletedAreaList | CRITICALITY ignore | TYPE BroadcastCompletedAreaList | PRESENCE optional | } | +| { ID id-CriticalityDiagnostics | CRITICALITY ignore | TYPE CriticalityDiagnostics | PRESENCE optional | }, | + +... +} + +-- \*\*\*\*\* + +-- + +-- PWS Cancel Elementary Procedure + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- PWS CANCEL REQUEST + +-- + +-- \*\*\*\*\* + +``` + +PWSCancelRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {PWSCancelRequestIEs} }, + ... +} + +PWSCancelRequestIEs NGAP-PROTOCOL-IES ::= { + { ID id-MessageIdentifier CRITICALITY reject TYPE MessageIdentifier PRESENCE mandatory }| + { ID id-SerialNumber CRITICALITY reject TYPE SerialNumber PRESENCE mandatory }| + { ID id-WarningAreaList CRITICALITY ignore TYPE WarningAreaList PRESENCE optional }| + { ID id-CancelAllWarningMessages CRITICALITY reject TYPE CancelAllWarningMessages PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- PWS CANCEL RESPONSE +-- +-- ***** + +``` + +``` + +PWSCancelResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {PWSCancelResponseIEs} }, + ... +} + +``` + +``` + +PWSCancelResponseIEs NGAP-PROTOCOL-IES ::= { + { ID id-MessageIdentifier CRITICALITY reject TYPE MessageIdentifier PRESENCE mandatory }| + { ID id-SerialNumber CRITICALITY reject TYPE SerialNumber PRESENCE mandatory }| + { ID id-BroadcastCancelledAreaList CRITICALITY ignore TYPE BroadcastCancelledAreaList PRESENCE optional }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- PWS Restart Indication Elementary Procedure + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- PWS RESTART INDICATION + +-- + +-- \*\*\*\*\* + +``` + +PWSRestartIndication ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {PWSRestartIndicationIEs} }, + +``` + +... +} + +PWSRestartIndicationIEs NGAP-PROTOCOL-IES ::= { + +``` + + { ID id-CellIDListForRestart CRITICALITY reject TYPE CellIDListForRestart PRESENCE mandatory }| + { ID id-GlobalRANNodeID CRITICALITY reject TYPE GlobalRANNodeID PRESENCE mandatory }| + { ID id-TAILListForRestart CRITICALITY reject TYPE TAILListForRestart PRESENCE mandatory }| + { ID id-EmergencyAreaIDListForRestart CRITICALITY reject TYPE EmergencyAreaIDListForRestart PRESENCE optional }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- PWS Failure Indication Elementary Procedure + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- PWS FAILURE INDICATION + +-- + +-- \*\*\*\*\* + +``` + +PWSFailureIndication ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {PWSFailureIndicationIEs} }, + ... +} + +``` + +``` + +PWSFailureIndicationIEs NGAP-PROTOCOL-IES ::= { + { ID id-PWSFailedCellIDList CRITICALITY reject TYPE PWSFailedCellIDList PRESENCE mandatory } | + { ID id-GlobalRANNodeID CRITICALITY reject TYPE GlobalRANNodeID PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- NRPPA TRANSPORT ELEMENTARY PROCEDURES +-- +-- ***** +-- +-- ***** +-- +-- DOWNLINK UE ASSOCIATED NRPPA TRANSPORT +-- +-- ***** + +``` + +``` + +DownlinkUEAssociatedNRPPaTransport ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {DownlinkUEAssociatedNRPPaTransportIEs} }, + ... +} + +``` + +``` + +DownlinkUEAssociatedNRPPaTransportIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY reject TYPE AMF-UE-NGAP-ID PRESENCE mandatory } | + { ID id-RAN-UE-NGAP-ID CRITICALITY reject TYPE RAN-UE-NGAP-ID PRESENCE mandatory } | + { ID id-RoutingID CRITICALITY reject TYPE RoutingID PRESENCE mandatory } | + { ID id-NRPPa-PDU CRITICALITY reject TYPE NRPPa-PDU PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- UPLINK UE ASSOCIATED NRPPA TRANSPORT +-- +-- ***** + +``` + +``` + +UplinkUEAssociatedNRPPaTransport ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {UplinkUEAssociatedNRPPaTransportIEs} }, + ... +} + +``` + +``` + +UplinkUEAssociatedNRPPaTransportIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY reject TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-NGAP-ID CRITICALITY reject TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RoutingID CRITICALITY reject TYPE RoutingID PRESENCE mandatory }| + { ID id-NRPPa-PDU CRITICALITY reject TYPE NRPPa-PDU PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- DOWNLINK NON UE ASSOCIATED NRPPA TRANSPORT +-- +-- ***** + +``` + +``` + +DownlinkNonUEAssociatedNRPPaTransport ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {DownlinkNonUEAssociatedNRPPaTransportIEs} }, + ... +} + +``` + +``` + +DownlinkNonUEAssociatedNRPPaTransportIEs NGAP-PROTOCOL-IES ::= { + { ID id-RoutingID CRITICALITY reject TYPE RoutingID PRESENCE mandatory }| + { ID id-NRPPa-PDU CRITICALITY reject TYPE NRPPa-PDU PRESENCE mandatory }, + +``` + +``` + + ... + } + + -- ***** + -- + -- UPLINK NON UE ASSOCIATED NRPPA TRANSPORT + -- + -- ***** + +``` + +``` + +UplinkNonUEAssociatedNRPPaTransport ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {UplinkNonUEAssociatedNRPPaTransportIEs} }, + ... +} + +``` + +``` + +UplinkNonUEAssociatedNRPPaTransportIEs NGAP-PROTOCOL-IES ::= { + { ID id-RoutingID CRITICALITY reject TYPE RoutingID PRESENCE mandatory } | + { ID id-NRPPa-PDU CRITICALITY reject TYPE NRPPa-PDU PRESENCE mandatory }, + ... +} + +``` + +``` + + -- ***** + -- + -- TRACE ELEMENTARY PROCEDURES + +``` + +``` + +-- +-- ***** +-- ***** +-- +-- TRACE START +-- +-- ***** + +TraceStart ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {TraceStartIEs} }, + ... +} + +TraceStartIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY reject TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-NGAP-ID CRITICALITY reject TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-TraceActivation CRITICALITY ignore TYPE TraceActivation PRESENCE mandatory }, + ... +} + +-- ***** +-- + +``` + +-- TRACE FAILURE INDICATION + +-- + +-- \*\*\*\*\* + +``` + +TraceFailureIndication ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {TraceFailureIndicationIEs} }, + ... +} + +``` + +``` + +TraceFailureIndicationIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY reject TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-NGAP-ID CRITICALITY reject TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-NGRANTraceID CRITICALITY ignore TYPE NGRANTraceID PRESENCE mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- DEACTIVATE TRACE + +-- + +-- \*\*\*\*\* + +DeactivateTrace ::= SEQUENCE { + +    protocolIEs    ProtocolIE-Container    { {DeactivateTraceIEs} }, + +    ... + +} + +DeactivateTraceIEs NGAP-PROTOCOL-IES ::= { + +    { ID id-AMF-UE-NGAP-ID    CRITICALITY reject    TYPE AMF-UE-NGAP-ID    PRESENCE mandatory }| + +    { ID id-RAN-UE-NGAP-ID    CRITICALITY reject    TYPE RAN-UE-NGAP-ID    PRESENCE mandatory }| + +    { ID id-NGRANTraceID    CRITICALITY ignore    TYPE NGRANTraceID    PRESENCE mandatory }, + +    ... + +} + +-- \*\*\*\*\* + +-- + +-- CELL TRAFFIC TRACE + +-- + +-- \*\*\*\*\* + +CellTrafficTrace ::= SEQUENCE { + +    protocolIEs    ProtocolIE-Container    { {CellTrafficTraceIEs} }, + +    ... + +} + +``` + +CellTrafficTraceIEs NGAP-PROTOCOL-IES ::= { + {ID id-AMF-UE-NGAP-ID CRITICALITY reject TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + {ID id-RAN-UE-NGAP-ID CRITICALITY reject TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + {ID id-NGRANTraceID CRITICALITY ignore TYPE NGRANTraceID PRESENCE mandatory }| + {ID id-NGRAN-CGI CRITICALITY ignore TYPE NGRAN-CGI 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 }, + ... +} + +``` + +-- \*\*\*\*\* + +-- +-- LOCATION REPORTING ELEMENTARY PROCEDURES + +-- +-- \*\*\*\*\* + +-- +-- \*\*\*\*\* + +-- +-- LOCATION REPORTING CONTROL + +-- +-- \*\*\*\*\* + +``` + +LocationReportingControl ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {LocationReportingControlIEs} }, + ... +} + +``` + +``` + +LocationReportingControlIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY reject TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-NGAP-ID CRITICALITY reject TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-LocationReportingRequestType CRITICALITY ignore TYPE LocationReportingRequestType PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- LOCATION REPORTING FAILURE INDICATION +-- +-- ***** + +``` + +``` + +LocationReportingFailureIndication ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {LocationReportingFailureIndicationIEs} }, + ... +} + +``` + +``` + +LocationReportingFailureIndicationIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY reject TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-NGAP-ID CRITICALITY reject TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- LOCATION REPORT +-- +-- ***** + +``` + +``` + +LocationReport ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {LocationReportIEs} }, + ... +} + +``` + +``` + +LocationReportIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY reject TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-NGAP-ID CRITICALITY reject TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-UserLocationInformation CRITICALITY ignore TYPE UserLocationInformation PRESENCE mandatory }| + { ID id-UEPresenceInAreaOfInterestList CRITICALITY ignore TYPE UEPresenceInAreaOfInterestList PRESENCE optional }| +} + +``` + +``` + + { ID id-LocationReportingRequestType CRITICALITY ignore TYPE LocationReportingRequestType PRESENCE mandatory }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- UE TNLA BINDING ELEMENTARY PROCEDURES + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- UE TNLA BINDING RELEASE REQUEST + +-- + +-- \*\*\*\*\* + +``` + +UETNLABindingReleaseRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {UETNLABindingReleaseRequestIEs} }, + ... +} + +``` + +``` + +UETNLABindingReleaseRequestIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY reject TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + +``` + +``` + + { ID id-RAN-UE-NGAP-ID CRITICALITY reject TYPE RAN-UE-NGAP-ID PRESENCE mandatory }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- UE RADIO CAPABILITY MANAGEMENT ELEMENTARY PROCEDURES + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- UE RADIO CAPABILITY INFO INDICATION + +-- + +-- \*\*\*\*\* + +UERadioCapabilityInfoIndication ::= SEQUENCE { + +protocolIEs ProtocolIE-Container { {UERadioCapabilityInfoIndicationIEs} }, + +... + +} + +UERadioCapabilityInfoIndicationIEs NGAP-PROTOCOL-IEs ::= { + +{ ID id-AMF-UE-NGAP-ID CRITICALITY reject TYPE AMF-UE-NGAP-ID PRESENCE mandatory } | + +``` + + { ID id-RAN-UE-NGAP-ID CRITICALITY reject TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-UERadioCapability CRITICALITY ignore TYPE UERadioCapability PRESENCE mandatory }| + { ID id-UERadioCapabilityForPaging CRITICALITY ignore TYPE UERadioCapabilityForPaging PRESENCE optional }| + { ID id-UERadioCapability-EUTRA-Format CRITICALITY ignore TYPE UERadioCapability PRESENCE optional }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- UE Radio Capability Check Elementary Procedure + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- UE RADIO CAPABILITY CHECK REQUEST + +-- + +-- \*\*\*\*\* + +``` + +UERadioCapabilityCheckRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {UERadioCapabilityCheckRequestIEs} }, + ... +} + +``` + +``` + +UERadioCapabilityCheckRequestIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY reject TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-NGAP-ID CRITICALITY reject TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-UERadioCapability CRITICALITY ignore TYPE UERadioCapability PRESENCE optional }| + { ID id-UERadioCapabilityID CRITICALITY reject TYPE UERadioCapabilityID PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- UE RADIO CAPABILITY CHECK RESPONSE +-- +-- ***** + +``` + +``` + +UERadioCapabilityCheckResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {UERadioCapabilityCheckResponseIEs} }, + ... +} + +``` + +``` + +UERadioCapabilityCheckResponseIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY ignore TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-NGAP-ID CRITICALITY ignore TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + +``` + +``` + + { ID id-IMSVoiceSupportIndicator CRITICALITY reject TYPE IMSVoiceSupportIndicator PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- PRIVATE MESSAGE ELEMENTARY PROCEDURE + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- PRIVATE MESSAGE + +-- + +-- \*\*\*\*\* + +``` + +PrivateMessage ::= SEQUENCE { + privateIEs PrivateIE-Container { { PrivateMessageIEs } }, + ... +} + +``` + +``` + +PrivateMessageIEs NGAP-PRIVATE-IES ::= { + +``` + +``` + + ... + } + + -- ***** + -- + -- DATA USAGE REPORTING ELEMENTARY PROCEDURES + -- + -- ***** + + -- ***** + -- + -- SECONDARY RAT DATA USAGE REPORT + -- + -- ***** + +``` + +``` + +SecondaryRATDataUsageReport ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {SecondaryRATDataUsageReportIEs} }, + ... +} + +``` + +``` + +SecondaryRATDataUsageReportIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY ignore TYPE AMF-UE-NGAP-ID PRESENCE mandatory } | + +``` + +``` + + { ID id-RAN-UE-NGAP-ID CRITICALITY ignore TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-PDUSessionResourceSecondaryRATUsageList CRITICALITY ignore TYPE PDUSessionResourceSecondaryRATUsageList PRESENCE mandatory }| + { ID id-HandoverFlag CRITICALITY ignore TYPE HandoverFlag PRESENCE optional }| + { ID id-UserLocationInformation CRITICALITY ignore TYPE UserLocationInformation PRESENCE optional }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- RIM INFORMATION TRANSFER ELEMENTARY PROCEDURES + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- UPLINK RIM INFORMATION TRANSFER + +-- + +-- \*\*\*\*\* + +``` + +UplinkRIMInformationTransfer ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {UplinkRIMInformationTransferIEs} }, + ... +} + +``` + +``` + +UplinkRIMInformationTransferIEs NGAP-PROTOCOL-IES ::= { + { ID id-RIMInformationTransfer CRITICALITY ignore TYPE RIMInformationTransfer PRESENCE optional }, + ... +} + +-- ***** +-- +-- DOWNLINK RIM INFORMATION TRANSFER +-- +-- ***** + +DownlinkRIMInformationTransfer ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {DownlinkRIMInformationTransferIEs} }, + ... +} + +DownlinkRIMInformationTransferIEs NGAP-PROTOCOL-IES ::= { + { ID id-RIMInformationTransfer CRITICALITY ignore TYPE RIMInformationTransfer PRESENCE optional }, + ... +} + +-- ***** + +``` + +``` + +-- +-- Connection Establishment Indication +-- +-- ***** + +``` + +``` + +ConnectionEstablishmentIndication ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {ConnectionEstablishmentIndicationIEs} }, + ... +} + +``` + +``` + +ConnectionEstablishmentIndicationIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY reject TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-NGAP-ID CRITICALITY reject TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-UERadioCapability CRITICALITY ignore TYPE UERadioCapability PRESENCE optional }| + { ID id-EndIndication CRITICALITY ignore TYPE EndIndication PRESENCE optional }| + { ID id-S-NSSAI CRITICALITY ignore TYPE S-NSSAI PRESENCE optional }| + { ID id-AllowedNSSAI CRITICALITY ignore TYPE AllowedNSSAI PRESENCE optional }| + { ID id-UE-DifferentiationInfo CRITICALITY ignore TYPE UE-DifferentiationInfo PRESENCE optional }| + { ID id-DL-CP-SecurityInformation CRITICALITY ignore TYPE DL-CP-SecurityInformation PRESENCE optional }| + { ID id-NB-IoT-UEPriority CRITICALITY ignore TYPE NB-IoT-UEPriority PRESENCE optional }| + { ID id-Enhanced-CoverageRestriction CRITICALITY ignore TYPE Enhanced-CoverageRestriction PRESENCE optional }| + { ID id-CEmodeBrestricted CRITICALITY ignore TYPE CEmodeBrestricted PRESENCE optional }| + { ID id-UERadioCapabilityID CRITICALITY reject TYPE UERadioCapabilityID PRESENCE optional }| +} + +``` + +``` + + { ID id-MaskedIMEISV CRITICALITY ignore TYPE MaskedIMEISV PRESENCE optional }| + { ID id-OldAMF CRITICALITY reject TYPE AMFName PRESENCE optional }| + { ID id-Partially-Allowed-NSSAI CRITICALITY ignore TYPE Partially-Allowed-NSSAI PRESENCE optional }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- UE RADIO CAPABILITY ID MAPPING ELEMENTARY PROCEDURES + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- UE RADIO CAPABILITY ID MAPPING REQUEST + +-- + +-- \*\*\*\*\* + +``` + +UERadioCapabilityIDMappingRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {UERadioCapabilityIDMappingRequestIEs} }, + ... +} + +``` + +UERadioCapabilityIDMappingRequestIEs NGAP-PROTOCOL-IES ::= { + +{ ID id-UERadioCapabilityID CRITICALITY reject TYPE UERadioCapabilityID PRESENCE mandatory }, + +... + +} + +-- \*\*\*\*\* + +-- + +-- UE RADIO CAPABILITY ID MAPPING RESPONSE + +-- + +-- \*\*\*\*\* + +UERadioCapabilityIDMappingResponse ::= SEQUENCE { + +protocolIEs ProtocolIE-Container { {UERadioCapabilityIDMappingResponseIEs} }, + +... + +} + +UERadioCapabilityIDMappingResponseIEs NGAP-PROTOCOL-IES ::= { + +{ ID id-UERadioCapabilityID CRITICALITY reject TYPE UERadioCapabilityID PRESENCE mandatory }| + +{ ID id-UERadioCapability CRITICALITY ignore TYPE UERadioCapability PRESENCE mandatory }| + +{ ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + +... + +} + +``` + +-- ***** +-- +-- AMF CP Relocation Indication +-- +-- ***** + +``` + +``` + +AMFCPRelocationIndication ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { AMFCPRelocationIndicationIEs} }, + ... +} + +``` + +``` + +AMFCPRelocationIndicationIEs NGAP-PROTOCOL-IEs ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY reject TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-NGAP-ID CRITICALITY reject TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-S-NSSAI CRITICALITY ignore TYPE S-NSSAI PRESENCE optional }| + { ID id-AllowedNSSAI CRITICALITY ignore TYPE AllowedNSSAI PRESENCE optional }| + { ID id-Partially-Allowed-NSSAI CRITICALITY ignore TYPE Partially-Allowed-NSSAI PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- + +``` + +-- MBS SESSION MANAGEMENT ELEMENTARY PROCEDURES + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- Broadcast Session Setup Elementary Procedure + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- BROADCAST SESSION SETUP REQUEST + +-- + +-- \*\*\*\*\* + +BroadcastSessionSetupRequest ::= SEQUENCE { + +    protocolIEs    ProtocolIE-Container    { {BroadcastSessionSetupRequestIEs} }, + +    ... + +} + +BroadcastSessionSetupRequestIEs NGAP-PROTOCOL-IES ::= { + +    { ID id-MBS-SessionID                                    CRITICALITY reject  TYPE MBS-SessionID                                    PRESENCE mandatory  }| + +``` + + { ID id-S-NSSAI CRITICALITY reject TYPE S-NSSAI PRESENCE mandatory }| + { ID id-MBS-ServiceArea CRITICALITY reject TYPE MBS-ServiceArea PRESENCE mandatory }| + { ID id-MBSSessionSetupRequestTransfer CRITICALITY reject TYPE OCTET STRING (CONTAINING MBSSessionSetupOrModRequestTransfer) PRESENCE +mandatory }| + { ID id-AssociatedSessionID CRITICALITY ignore TYPE AssociatedSessionID PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- BROADCAST SESSION SETUP RESPONSE +-- +-- ***** + +``` + +``` + +BroadcastSessionSetupResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {BroadcastSessionSetupResponseIEs} }, + ... +} + +``` + +``` + +BroadcastSessionSetupResponseIEs NGAP-PROTOCOL-IES ::= { + { ID id-MBS-SessionID CRITICALITY reject TYPE MBS-SessionID PRESENCE mandatory }| + { ID id-MBSSessionSetupResponseTransfer CRITICALITY reject TYPE OCTET STRING (CONTAINING MBSSessionSetupOrModResponseTransfer) PRESENCE +optional }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + +``` + +``` + + ... + } + + -- ***** + -- + -- BROADCAST SESSION SETUP FAILURE + -- + -- ***** + +BroadcastSessionSetupFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {BroadcastSessionSetupFailureIEs} }, + ... +} + +BroadcastSessionSetupFailureIEs NGAP-PROTOCOL-IES ::= { + { ID id-MBS-SessionID CRITICALITY reject TYPE MBS-SessionID PRESENCE mandatory }| + { ID id-MBSSessionSetupFailureTransfer CRITICALITY ignore TYPE OCTET STRING (CONTAINING MBSSessionSetupOrModFailureTransfer) PRESENCE +optional }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- Broadcast Session Modification Elementary Procedure +-- +-- ***** +-- +-- ***** +-- +-- BROADCAST SESSION MODIFICATION REQUEST +-- +-- ***** + +``` + +``` + +BroadcastSessionModificationRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {BroadcastSessionModificationRequestIEs} }, + ... +} + +``` + +``` + +BroadcastSessionModificationRequestIEs NGAP-PROTOCOL-IES ::= { + { ID id-MBS-SessionID CRITICALITY reject TYPE MBS-SessionID PRESENCE mandatory }| + { ID id-MBS-ServiceArea CRITICALITY reject TYPE MBS-ServiceArea PRESENCE optional }| + { ID id-MBSSessionModificationRequestTransfer CRITICALITY reject TYPE OCTET STRING (CONTAINING MBSSessionSetupOrModRequestTransfer) PRESENCE +optional }, + ... +} + +``` + +} + +-- \*\*\*\*\* +-- +-- BROADCAST SESSION MODIFICATION RESPONSE +-- +-- \*\*\*\*\* + +BroadcastSessionModificationResponse ::= SEQUENCE { +    protocolIEs    ProtocolIE-Container    { {BroadcastSessionModificationResponseIEs} }, +    ... +} + +BroadcastSessionModificationResponseIEs NGAP-PROTOCOL-IES ::= { +    { ID id-MBS-SessionID                                    CRITICALITY reject  TYPE MBS-SessionID                                    PRESENCE mandatory  }| +    { ID id-MBSSessionModificationResponseTransfer  CRITICALITY reject  TYPE OCTET STRING (CONTAINING MBSSessionSetupOrModResponseTransfer) PRESENCE +optional    }| +    { ID id-CriticalityDiagnostics                            CRITICALITY ignore  TYPE CriticalityDiagnostics                                    PRESENCE optional  }, +    ... +} + +-- \*\*\*\*\* +-- + +-- BROADCAST SESSION MODIFICATION FAILURE + +-- + +-- \*\*\*\*\* + +BroadcastSessionModificationFailure ::= SEQUENCE { + +    protocolIEs    ProtocolIE-Container    { {BroadcastSessionModificationFailureIEs} }, + +    ... + +} + +BroadcastSessionModificationFailureIEs NGAP-PROTOCOL-IES ::= { + +    { ID id-MBS-SessionID                            CRITICALITY reject  TYPE MBS-SessionID                            PRESENCE mandatory  }| + +    { ID id-MBSSessionModificationFailureTransfer  CRITICALITY ignore  TYPE OCTET STRING (CONTAINING MBSSessionSetupOrModFailureTransfer) PRESENCE +optional    }| + +    { ID id-Cause                                    CRITICALITY ignore  TYPE Cause                                    PRESENCE mandatory  }| + +    { ID id-CriticalityDiagnostics                CRITICALITY ignore  TYPE CriticalityDiagnostics                            PRESENCE optional  }, + +    ... + +} + +-- \*\*\*\*\* + +-- + +-- Broadcast Session Release Elementary Procedure + +-- + +-- \*\*\*\*\* + +``` + +-- ***** +-- +-- BROADCAST SESSION RELEASE REQUEST +-- +-- ***** + +``` + +``` + +BroadcastSessionReleaseRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {BroadcastSessionReleaseRequestIEs} }, + ... +} + +``` + +``` + +BroadcastSessionReleaseRequestIEs NGAP-PROTOCOL-IES ::= { + { ID id-MBS-SessionID CRITICALITY reject TYPE MBS-SessionID PRESENCE mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- Broadcast Session Release Required Elementary Procedure +-- +-- ***** + +``` + +``` + +-- ***** +-- +-- BROADCAST SESSION RELEASE REQUIRED +-- +-- ***** + +``` + +``` + +BroadcastSessionReleaseRequired := SEQUENCE { + protocolIEs ProtocolIE-Container { {BroadcastSessionReleaseRequiredIEs} }, + ... +} + +``` + +``` + +BroadcastSessionReleaseRequiredIEs NGAP-PROTOCOL-IES := { + { ID id-MBS-SessionID CRITICALITY reject TYPE MBS-SessionID PRESENCE mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- BROADCAST SESSION RELEASE RESPONSE +-- +-- ***** + +``` + +BroadcastSessionReleaseResponse ::= SEQUENCE { + +    protocolIEs    ProtocolIE-Container    { {BroadcastSessionReleaseResponseIEs} }, + +    ... + +} + +BroadcastSessionReleaseResponseIEs NGAP-PROTOCOL-IES ::= { + +    { ID id-MBS-SessionID                            CRITICALITY reject  TYPE MBS-SessionID                            PRESENCE mandatory  }| + +    { ID id-MBSSessionReleaseResponseTransfer    CRITICALITY ignore  TYPE OCTET STRING (CONTAINING MBSSessionReleaseResponseTransfer)  PRESENCE +optional            }| + +    { ID id-CriticalityDiagnostics                CRITICALITY ignore  TYPE CriticalityDiagnostics                            PRESENCE optional  }, + +    ... + +} + +-- \*\*\*\*\* + +-- + +-- Broadcast Session Transport Elementary Procedure + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +``` +-- BROADCAST SESSION TRANSPORT REQUEST +``` + +``` +-- +``` + +``` +-- ***** +``` + +``` +BroadcastSessionTransportRequest ::= SEQUENCE { +``` + +``` + protocolIEs ProtocolIE-Container { {BroadcastSessionTransportRequestIEs} }, +``` + +``` + ... +``` + +``` +} +``` + +``` +BroadcastSessionTransportRequestIEs NGAP-PROTOCOL-IES ::= { +``` + +``` + { ID id-MBS-SessionID CRITICALITY reject TYPE MBS-SessionID PRESENCE mandatory } | +``` + +``` + { ID id-BroadcastTransportRequestTransfer CRITICALITY reject TYPE OCTET STRING (CONTAINING BroadcastTransportRequestTransfer) PRESENCE mandatory }, +``` + +``` + ... +``` + +``` +} +``` + +``` +-- ***** +``` + +``` +-- +``` + +``` +-- BROADCAST SESSION TRANSPORT RESPONSE +``` + +``` +-- +``` + +``` +-- ***** +``` + +``` +BroadcastSessionTransportResponse ::= SEQUENCE { +``` + +``` + + protocolIEs ProtocolIE-Container { {BroadcastSessionTransportResponseIEs} }, + ... +} + +``` + +``` + +BroadcastSessionTransportResponseIEs NGAP-PROTOCOL-IES ::= { + { ID id-MBS-SessionID CRITICALITY reject TYPE MBS-SessionID PRESENCE mandatory }| + { ID id-BroadcastTransportResponseTransfer CRITICALITY reject TYPE OCTET STRING (CONTAINING BroadcastTransportResponseTransfer) PRESENCE mandatory + }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- BROADCAST SESSION TRANSPORT FAILURE +-- +-- ***** + +``` + +``` + +BroadcastSessionTransportFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {BroadcastSessionTransportFailureIEs} }, + ... +} + +``` + +BroadcastSessionTransportFailureIEs NGAP-PROTOCOL-IES ::= { + +``` + + { ID id-MBS-SessionID CRITICALITY reject TYPE MBS-SessionID PRESENCE mandatory }| + { ID id-BroadcastTransportFailureTransfer CRITICALITY ignore TYPE OCTET STRING (CONTAINING BroadcastTransportFailureTransfer) PRESENCE +mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- Distribution Setup Elementary Procedure +-- +-- ***** +-- +-- ***** +-- +-- DISTRIBUTION SETUP REQUEST +-- +-- ***** + +``` + +``` + +DistributionSetupRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {DistributionSetupRequestIEs} }, + ... +} + +DistributionSetupRequestIEs NGAP-PROTOCOL-IES ::= { + { ID id-MBS-SessionID CRITICALITY reject TYPE MBS-SessionID PRESENCE mandatory } | + { ID id-MBS-AreaSessionID CRITICALITY reject TYPE MBS-AreaSessionID PRESENCE optional } | + { ID id-MBS-DistributionSetupRequestTransfer CRITICALITY reject TYPE OCTET STRING (CONTAINING MBS-DistributionSetupRequestTransfer) + PRESENCE mandatory }, + ... +} + +-- ***** +-- +-- DISTRIBUTION SETUP RESPONSE +-- +-- ***** + +DistributionSetupResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {DistributionSetupResponseIEs} }, + ... +} + +``` + +``` + +DistributionSetupResponseIEs NGAP-PROTOCOL-IES ::= { + { ID id-MBS-SessionID CRITICALITY reject TYPE MBS-SessionID PRESENCE mandatory }| + { ID id-MBS-AreaSessionID CRITICALITY reject TYPE MBS-AreaSessionID PRESENCE optional }| + { ID id-MBS-DistributionSetupResponseTransfer CRITICALITY reject TYPE OCTET STRING (CONTAINING MBS-DistributionSetupResponseTransfer) + PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +-- \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* +-- +-- DISTRIBUTION SETUP FAILURE +-- +-- \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* + +``` + +DistributionSetupFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {DistributionSetupFailureIEs} }, + ... +} + +``` + +``` + +DistributionSetupFailureIEs NGAP-PROTOCOL-IES ::= { + { ID id-MBS-SessionID CRITICALITY reject TYPE MBS-SessionID PRESENCE mandatory }| + +``` + +``` + + { ID id-MBS-AreaSessionID CRITICALITY reject TYPE MBS-AreaSessionID PRESENCE optional }| + { ID id-MBS-DistributionSetupUnsuccessfulTransfer CRITICALITY ignore TYPE OCTET STRING (CONTAINING MBS-DistributionSetupUnsuccessfulTransfer) + PRESENCE mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- Distribution Release Elementary Procedure + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- DISTRIBUTION RELEASE REQUEST + +-- + +-- \*\*\*\*\* + +``` + +DistributionReleaseRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {DistributionReleaseRequestIEs} }, + ... +} + +``` + +} + +DistributionReleaseRequestIEs NGAP-PROTOCOL-IES ::= { + +{ ID id-MBS-SessionID CRITICALITY reject TYPE MBS-SessionID PRESENCE mandatory }| + +{ ID id-MBS-AreaSessionID CRITICALITY reject TYPE MBS-AreaSessionID PRESENCE optional }| + +{ ID id-MBS-DistributionReleaseRequestTransfer CRITICALITY reject TYPE OCTET STRING (CONTAINING MBS-DistributionReleaseRequestTransfer) +PRESENCE mandatory }| + +{ ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }, + +... + +} + +-- \*\*\*\*\* + +-- + +-- DISTRIBUTION RELEASE RESPONSE + +-- + +-- \*\*\*\*\* + +DistributionReleaseResponse ::= SEQUENCE { + +protocolIEs ProtocolIE-Container { {DistributionReleaseResponseIEs} }, + +... + +} + +DistributionReleaseResponseIEs NGAP-PROTOCOL-IES ::= { + +``` + + { ID id-MBS-SessionID CRITICALITY reject TYPE MBS-SessionID PRESENCE mandatory }| + { ID id-MBS-AreaSessionID CRITICALITY reject TYPE MBS-AreaSessionID PRESENCE optional }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +-- \*\*\*\*\* + +-- +-- Multicast Session Activation Elementary Procedure +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- +-- MULTICAST SESSION ACTIVATION REQUEST +-- + +-- \*\*\*\*\* + +``` + +MulticastSessionActivationRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {MulticastSessionActivationRequestIEs} }, + ... +} + +``` + +``` +MulticastSessionActivationRequestIEs NGAP-PROTOCOL-IES ::= { + { ID id-MBS-SessionID CRITICALITY reject TYPE MBS-SessionID PRESENCE mandatory }| + { ID id-MulticastSessionActivationRequestTransfer CRITICALITY reject TYPE OCTET STRING (CONTAINING MulticastSessionActivationRequestTransfer) + PRESENCE mandatory }, + ... +} + +-- ***** +-- +-- MULTICAST SESSION ACTIVATION RESPONSE +-- +-- ***** + +MulticastSessionActivationResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {MulticastSessionActivationResponseIEs} }, + ... +} + +MulticastSessionActivationResponseIEs NGAP-PROTOCOL-IES ::= { + { ID id-MBS-SessionID CRITICALITY reject TYPE MBS-SessionID PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} +``` + +``` + +-- ***** +-- +-- MULTICAST SESSION ACTIVATION FAILURE +-- +-- ***** + +``` + +``` + +MulticastSessionActivationFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {MulticastSessionActivationFailureIEs} }, + ... +} + +``` + +``` + +MulticastSessionActivationFailureIEs NGAP-PROTOCOL-IES ::= { + { ID id-MBS-SessionID CRITICALITY reject TYPE MBS-SessionID PRESENCE mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- Multicast Session Deactivation Elementary Procedure +-- + +``` + +``` + +-- ***** +-- +-- ***** +-- +-- MULTICAST SESSION DEACTIVATION REQUEST +-- +-- ***** + +``` + +``` + +MulticastSessionDeactivationRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {MulticastSessionDeactivationRequestIEs} }, + ... +} + +``` + +``` + +MulticastSessionDeactivationRequestIEs NGAP-PROTOCOL-IES ::= { + { ID id-MBS-SessionID CRITICALITY reject TYPE MBS-SessionID PRESENCE mandatory } | + { ID id-MulticastSessionDeactivationRequestTransfer CRITICALITY reject TYPE OCTET STRING (CONTAINING MulticastSessionDeactivationRequestTransfer) + PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- MULTICAST SESSION DEACTIVATION RESPONSE + +``` + +-- +-- \*\*\*\*\* + +MulticastSessionDeactivationResponse ::= SEQUENCE { +    protocolIEs    ProtocolIE-Container    { {MulticastSessionDeactivationResponseIEs} }, +    ... +} + +MulticastSessionDeactivationResponseIEs NGAP-PROTOCOL-IES ::= { +    { ID id-MBS-SessionID                                    CRITICALITY reject  TYPE MBS-SessionID                            PRESENCE mandatory  }| +    { ID id-CriticalityDiagnostics                          CRITICALITY ignore  TYPE CriticalityDiagnostics                            PRESENCE optional  }, +    ... +} + +-- \*\*\*\*\* + +-- +-- Multicast Session Update Elementary Procedure + +-- +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- +-- MULTICAST SESSION UPDATE REQUEST + +-- +-- \*\*\*\*\* + +MulticastSessionUpdateRequest ::= SEQUENCE { +    protocolIEs    ProtocolIE-Container    { {MulticastSessionUpdateRequestIEs} }, +    ... +} + +MulticastSessionUpdateRequestIEs NGAP-PROTOCOL-IES ::= { +    { ID id-MBS-SessionID                    CRITICALITY reject  TYPE MBS-SessionID                    PRESENCE mandatory  }| +    { ID id-MBS-AreaSessionID                CRITICALITY reject  TYPE MBS-AreaSessionID                    PRESENCE optional   }| +    { ID id-MulticastSessionUpdateRequestTransfer  CRITICALITY reject  TYPE OCTET STRING (CONTAINING MulticastSessionUpdateRequestTransfer) +    PRESENCE mandatory  }, +    ... +} + +-- \*\*\*\*\* +-- + +-- MULTICAST SESSION UPDATE RESPONSE + +-- +-- \*\*\*\*\* + +MulticastSessionUpdateResponse ::= SEQUENCE { + +``` + + protocolIEs ProtocolIE-Container { {MulticastSessionUpdateResponseIEs} }, + ... +} + +MulticastSessionUpdateResponseIEs NGAP-PROTOCOL-IES ::= { + { ID id-MBS-SessionID CRITICALITY reject TYPE MBS-SessionID PRESENCE mandatory }| + { ID id-MBS-AreaSessionID CRITICALITY reject TYPE MBS-AreaSessionID PRESENCE optional }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +-- ***** +-- +-- MULTICAST SESSION UPDATE FAILURE +-- +-- ***** + +MulticastSessionUpdateFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {MulticastSessionUpdateFailureIEs} }, + ... +} + +MulticastSessionUpdateFailureIEs NGAP-PROTOCOL-IES ::= { + +``` + +``` + + { ID id-MBS-SessionID CRITICALITY reject TYPE MBS-SessionID PRESENCE mandatory }| + { ID id-MBS-AreaSessionID CRITICALITY reject TYPE MBS-AreaSessionID PRESENCE optional }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- MULTICAST GROUP PAGING ELEMENTARY PROCEDURE + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- MULTICAST GROUP PAGING + +-- + +-- \*\*\*\*\* + +``` + +MulticastGroupPaging ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {MulticastGroupPagingIEs} }, + ... +} + +``` + +``` + +MulticastGroupPagingIEs NGAP-PROTOCOL-IES ::= { + { ID id-MBS-SessionID CRITICALITY ignore TYPE MBS-SessionID PRESENCE mandatory }| + { ID id-MBS-ServiceArea CRITICALITY ignore TYPE MBS-ServiceArea PRESENCE optional }| + { ID id-MulticastGroupPagingAreaList CRITICALITY ignore TYPE MulticastGroupPagingAreaList PRESENCE mandatory }, + ... +} + +``` + +-- \*\*\*\*\* + +-- +-- TIMING SYNCHRONISATION STATUS REPORTING ELEMENTARY PROCEDURES + +-- +-- \*\*\*\*\* + +-- +-- \*\*\*\*\* + +-- +-- Timing Synchronisation Status Elementary Procedure + +-- +-- \*\*\*\*\* + +-- +-- \*\*\*\*\* + +-- +-- TIMING SYNCHRONISATION STATUS REQUEST + +-- + +-- \*\*\*\*\* + +``` + +TimingSynchronisationStatusRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {TimingSynchronisationStatusRequestIEs} }, + ... +} + +``` + +``` + +TimingSynchronisationStatusRequestIEs NGAP-PROTOCOL-IES ::= { + { ID id-RAN-TSSRequestType CRITICALITY reject TYPE RAN-TSSRequestType PRESENCE mandatory }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- TIMING SYNCHRONISATION STATUS RESPONSE + +-- + +-- \*\*\*\*\* + +``` + +TimingSynchronisationStatusResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {TimingSynchronisationStatusResponseIEs} }, + ... +} + +``` + +``` +TimingSynchronisationStatusResponseIEs NGAP-PROTOCOL-IES ::= { + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +-- ***** +-- +-- TIMING SYNCHRONISATION STATUS FAILURE +-- +-- ***** + +TimingSynchronisationStatusFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { TimingSynchronisationStatusFailureIEs } }, + ... +} + +TimingSynchronisationStatusFailureIEs NGAP-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 { {TimingSynchronisationStatusReportIEs} }, + ... +} + +``` + +``` + +TimingSynchronisationStatusReportIEs NGAP-PROTOCOL-IES ::= { + { ID id-RANTimingSynchronisationStatusInfo CRITICALITY ignore TYPE RANTimingSynchronisationStatusInfo PRESENCE mandatory } | + { ID id-RAN-TSSScope CRITICALITY ignore TYPE RAN-TSSScope PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- MT Communication Handling Elementary Procedure +-- +-- ***** + +-- ***** +-- +-- MT COMMUNICATION HANDLING REQUEST +-- +-- ***** + +``` + +``` + +MTCommunicationHandlingRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { MTCommunicationHandlingRequestIEs } }, + ... +} + +``` + +``` + +MTCommunicationHandlingRequestIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY reject TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-NGAP-ID CRITICALITY reject TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-FiveGCAction CRITICALITY reject TYPE FiveGCAction PRESENCE mandatory }, + ... +} + +``` + +} + +-- \*\*\*\*\* + +-- + +-- MT COMMUNICATION HANDLING RESPONSE + +-- + +-- \*\*\*\*\* + +MTCommunicationHandlingResponse ::= SEQUENCE { + +    protocolIEs    ProtocolIE-Container    { {MTCommunicationHandlingResponseIEs} }, + +    ... + +} + +MTCommunicationHandlingResponseIEs NGAP-PROTOCOL-IES ::= { + +    { ID id-AMF-UE-NGAP-ID                    CRITICALITY reject  TYPE AMF-UE-NGAP-ID                    PRESENCE mandatory  }| + +    { ID id-RAN-UE-NGAP-ID                    CRITICALITY reject  TYPE RAN-UE-NGAP-ID                    PRESENCE mandatory  }| + +    { ID id-CriticalityDiagnostics            CRITICALITY ignore  TYPE CriticalityDiagnostics                PRESENCE optional  }, + +    ... + +} + +-- \*\*\*\*\* + +-- + +-- MT COMMUNICATION HANDLING FAILURE + +-- + +-- \*\*\*\*\* + +MTCommunicationHandlingFailure ::= SEQUENCE { + +    protocolIEs    ProtocolIE-Container    { { MTCommunicationHandlingFailureIEs } }, + +    ... + +} + +MTCommunicationHandlingFailureIEs NGAP-PROTOCOL-IES ::= { + +    { ID id-AMF-UE-NGAP-ID    CRITICALITY reject  TYPE AMF-UE-NGAP-ID    PRESENCE mandatory  }| + +    { ID id-RAN-UE-NGAP-ID    CRITICALITY reject  TYPE RAN-UE-NGAP-ID    PRESENCE mandatory  }| + +    { ID id-Cause            CRITICALITY ignore  TYPE Cause            PRESENCE mandatory  }| + +    { ID id-CriticalityDiagnostics  CRITICALITY ignore  TYPE CriticalityDiagnostics  PRESENCE optional  }, + +    ... + +} + +-- \*\*\*\*\* + +-- RAN Paging Request procedure + +-- + +-- \*\*\*\*\* + +``` +-- ***** +-- +-- RAN PAGING REQUEST +-- +-- ***** +``` + +``` +RANPagingRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { RANPagingRequestIEs } }, + ... +} +``` + +``` +RANPagingRequestIEs NGAP-PROTOCOL-IES ::= { + { ID id-AMF-UE-NGAP-ID CRITICALITY ignore TYPE AMF-UE-NGAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-NGAP-ID CRITICALITY ignore TYPE RAN-UE-NGAP-ID PRESENCE mandatory }| + { ID id-PagingPolicyDifferentiation CRITICALITY ignore TYPE PagingPolicyDifferentiation PRESENCE optional }| + { ID id-DL-Signalling CRITICALITY ignore TYPE DL-Signalling PRESENCE optional }, + ... +} +``` + +``` +END +``` + +``` +-- ASN1STOP +``` + +## 9.4.5 Information Element Definitions + +``` +-- ASN1START + +-- ***** +-- +-- Information Element Definitions +-- +-- ***** + +NGAP-IEs { + + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + ngran-Access (22) modules (3) ngap (1) version1 (1) ngap-IEs (2) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +IMPORTS + + id-AdditionalDLForwardingUPTNLInformation, + id-AdditionalULForwardingUPTNLInformation, + id-AdditionalDLQosFlowPerTNLInformation, + id-AdditionalDLUPTNLInformationForHOList, + id-AdditionalNGU-UP-TNLInformation, +``` + +id-AdditionalRedundantDL-NGU-UP-TNLInformation, +id-AdditionalRedundantDLQoSFlowPerTNLInformation, +id-AdditionalRedundantNGU-UP-TNLInformation, +id-AdditionalRedundantUL-NGU-UP-TNLInformation, +id-AdditionalUL-NGU-UP-TNLInformation, +id-AlternativeQoSParaSetList, +id-AssistanceInformationQoE-Meas, +id-AdditionalCancelledlocationReportingReferenceIDList, +id-BurstArrivalTimeDownlink, +id-Cause, +id-CNPacketDelayBudgetDL, +id-CNPacketDelayBudgetUL, +id-CNTypeRestrictionsForEquivalent, +id-CNTypeRestrictionsForServing, +id-CommonNetworkInstance, +id-ConfiguredTACIndication, +id-CN-MT-CommunicationHandling, +id-CurrentQoSParaSetIndex, +id-DAPSRequestInfo, +id-DAPSResponseInfoList, +id-DataForwardingNotPossible, +id-DataForwardingResponseERABList, +id-DirectForwardingPathAvailability, + +id-DL-NGU-UP-TNLInformation, +id-DownlinkTLContainer, +id-EndpointIPAddressAndPort, +id-EnergySavingIndication, +id-ExtendedMobilityInformation, +id-ExtendedPacketDelayBudget, +id-ExtendedRATRestrictionInformation, +id-ExtendedReportIntervalMDT, +id-ExtendedSliceSupportList, +id-ExtendedTAISliceSupportList, +id-ExtendedUEIdentityIndexValue, +id-EUTRA-PagingeDRXInformation, +id-EquivalentSNPNsList, +id-GlobalCable-ID, +id-GlobalRANNodeID, +id-GlobalTNGF-ID, +id-GlobalTWIF-ID, +id-GlobalW-AGF-ID, +id-GUAMIType, +id-HashedUEIdentityIndexValue, +id-IncludeBeamMeasurementsIndication, +id-IntersystemSONInformationRequest, +id-IntersystemSONInformationReply, + +id-IntersystemResourceStatusUpdate, +id-IntersystemMobilityFailureforVoiceFallback, +id-LastEUTRAN-PLMNIdentity, +id-LastVisitedPSCellList, +id-LocationReportingAdditionalInfo, +id-M4ReportAmount, +id-M5ReportAmount, +id-M6ReportAmount, +id-ExcessPacketDelayThresholdConfiguration, +id-M7ReportAmount, +id-MaximumIntegrityProtectedDataRate-DL, +id-MBS-AreaSessionID, +id-MBS-QoSFlowsToBeSetupList, +id-MBS-QoSFlowsToBeSetupModList, +id-MBS-QoSFlowToReleaseList, +id-MBS-ServiceArea, +id-MBS-SessionFSAIDList, +id-MBS-SessionID, +id-MBS-ActiveSessionInformation-SourcetoTargetList, +id-MBS-ActiveSessionInformation-TargettoSourceList, +id-MBS-AssistanceInformation, +id-MBS-SessionTNLInfo5GC, +id-MBS-SupportIndicator, + +id-MBSSessionFailedtoSetupList, +id-MBSSessionFailedtoSetuporModifyList, +id-MBSSessionSetupResponseList, +id-MBSSessionSetuporModifyResponseList, +id-MBSSessionToReleaseList, +id-MBSSessionSetupRequestList, +id-MBSSessionSetuporModifyRequestList, +id-MDTConfiguration, +id-MicoAllPLMN, +id-NetworkInstance, +id-NGAPIESupportInformationRequestList, +id-NGAPIESupportInformationResponseList, +id-NID, +id-NR-CGI, +id-NRNTNTAInformation, +id-NPN-MobilityInformation, +id-NPN-PagingAssistanceInformation, +id-NPN-Support, +id-NR-PagingeDRXInformation, +id-OldAssociatedQosFlowList-ULendmarkerexpected, +id-OnboardingSupport, +id-PagingAssisDataforCEcapabUE, +id-PagingCauseIndicationForVoiceService, + +id-PDUSessionAggregateMaximumBitRate, +id-PduSessionExpectedUEActivityBehaviour, +id-PDUSessionPairID, +id-PDUSessionResourceFailedToSetupListCxtFail, +id-PDUSessionResourceReleaseResponseTransfer, +id-PDUSessionType, +id-PEIPSassistanceInformation, +id-PSCellInformation, +id-PNI-NPNBasedMDT, +id-PNI-NPN-AreaScopeofMDT, +id-QMCConfigInfo, +id-QosFlowAdditionalInfoList, +id-QosFlowAddOrModifyRequestList, +id-QosFlowFailedToSetupList, +id-QosFlowFeedbackList, +id-QosFlowParametersList, +id-QosFlowSetupRequestList, +id-QosFlowToReleaseList, +id-QosMonitoringRequest, +id-QosMonitoringReportingFrequency, +id-SNPN-CellBasedMDT, +id-SNPN-TAIBasedMDT, +id-SNPN-BasedMDT, + +id-SuccessfulHandoverReportList, +id-SupportedUETypeList, +id-UEContextReferenceAtSource, +id-RAT-Information, +id-RedundantCommonNetworkInstance, +id-RedundantDL-NGU-TNLInformationReused, +id-RedundantDL-NGU-UP-TNLInformation, +id-RedundantDLQosFlowPerTNLInformation, +id-RedundantPDUSessionInformation, +id-RedundantQosFlowIndicator, +id-RedundantUL-NGU-UP-TNLInformation, +id-SCTP-TLAs, +id-SecondaryRATUsageInformation, +id-SecurityIndication, +id-SecurityResult, +id-SgNB-UE-X2AP-ID, +id-S-NSSAI, +id-SONInformationReport, +id-SourceNodeID, +id-SourceNodeTNLAddrInfo, +id-SourceTNLAddrInfo, +id-SurvivalTime, +id-Selected-Target-SNPN-Identity, + +id-TNLAssociationTransportLayerAddressNGRAN, +id-TAINSAGSupportList, +id-TargetHomeENB-ID, +id-TargetRNC-ID, +id-TimeBasedHandoverInformation, +id-TraceCollectionEntityURI, +id-TSCTrafficCharacteristics, +id-UEHistoryInformationFromTheUE, +id-UERadioCapabilityForPaging, +id-UERadioCapabilityForPagingOfNB-IoT, +id-UL-NGU-UP-TNLInformation, +id-UL-NGU-UP-TNLModifyList, +id-ULForwarding, +id-ULForwardingUP-TNLInformation, +id-UplinkTLContainer, +id-UsedRSNInformation, +id-UserLocationInformationTNGF, +id-UserLocationInformationTWIF, +id-UserLocationInformationW-AGF, +id-EarlyMeasurement, +id-BeamMeasurementsReportConfiguration, +id-DLDiscarding, +id-TAI, + +id-HFCNode-ID-new, +id-GlobalCable-ID-new, +id-FiveGProSeLayer2Multipath, +id-CandidateRelayUEInformationList, +id-FiveGProSeLayer2UEtoUERelay, +id-FiveGProSeLayer2UEtoUERemote, +id-SuccessfulPSCellChangeReportList, +id-TargetCellCRNTI, +id-TimeSinceFailure, +id-ClockQualityReportingControlInfo, +id-RANfeedbacktype, +id-QoSFlowTSCList, +id-TSCTrafficCharacteristicsFeedback, +id-ANPacketDelayBudgetUL, +id-MBSCommServiceType, +id-IAB-MTUserLocationInformation, +id-PDUsetQoSParameters, +id-PDUSetbasedHandlingIndicator, +id-N6JitterInformation, +id-ECNMarkingorCongestionInformationReportingRequest, +id-ECNMarkingorCongestionInformationReportingStatus, +maxnoofAllowedAreas, +maxnoofAllowedCAGsperPLMN, + +maxnoofAllowedS-NSSAIs, +maxnoofAoIMinusOne, +maxnoofBluetoothName, +maxnoofBPLMNs, +maxnoofCAGforMDT, +maxnoofCAGSperCell, +maxnoofCandidateCells, +maxnoofCellIDforMDT, +maxnoofCellIDforQMC, +maxnoofCellIDforWarning, +maxnoofCellinAoI, +maxnoofCellinEAI, +maxnoofCellsforMBS, +maxnoofCellsingNB, +maxnoofCellsinngeNB, +maxnoofCellsinNGRANNode, +maxnoofCellinTAI, +maxnoofCellsinUEHistoryInfo, +maxnoofCellsUEMovingTrajectory, +maxnoofDRBs, +maxnoofEmergencyAreaID, +maxnoofEAIforRestart, +maxnoofEPLMNs, + +maxnoofEPLMNsPlusOne, +maxnoofE-RABs, +maxnoofErrors, +maxnoofExtSliceItems, +maxnoofESPNs, +maxnoofForbTACs, +maxnoofFreqforMDT, +maxnoofMBSFSA, +maxnoofMBSQoSFlows, +maxnoofMBSServiceAreaInformation, +maxnoofMBSAreaSessionIDs, +maxnoofMBSSessions, +maxnoofMBSSessionsofUE, +maxnoofMDTPLMNs, +maxnoofMRBs, +maxnoofMultiConnectivity, +maxnoofMultiConnectivityMinusOne, +maxnoofNeighPCIforMDT, +maxnoofNGAPIESupportInfo, +maxnoofNGConnectionsToReset, +maxNRARFCN, +maxnoofNRCellBands, +maxnoofNSAGs, + +maxnoofPagingAreas, +maxnoofPC5QoSFlows, +maxnoofPDUSessions, +maxnoofPLMNs, +maxnoofPLMNforQMC, +maxnoofQoSFlows, +maxnoofQoSParaSets, +maxnoofRANNodeinAoI, +maxnoofRecommendedCells, +maxnoofRecommendedRANNodes, +maxnoofAoI, +maxnoofPSCellsPerPrimaryCellinUEHistoryInfo, +maxnoofReportedCells, +maxnoofSensorName, +maxnoofServedGUAMIs, +maxnoofSliceItems, +maxnoofMDTSNPNs, +maxnoofSNSSAIforQMC, +maxnoofSuccessfulHOReports, +maxnoofTACs, +maxnoofTACsinNTN, +maxnoofTAforMDT, +maxnoofTAforQMC, + +maxnoofTAIforInactive, +maxnoofTAIforMBS, +maxnoofTAIforPaging, +maxnoofTAIforRestart, +maxnoofTAIforWarning, +maxnoofTAInAoI, +maxnoofTargetS-NSSAIs, +maxnoofTimePeriods, +maxnoofTNLAssociations, +maxnoofUEAppLayerMeas, +maxnoofUEsforPaging, +maxnoofUETypes, +maxnoofWLANNName, +maxnoofXnExtTLAs, +maxnoofXnGTP-TLAs, +maxnoofXnTLAs, +maxnoofThresholdsForExcessPacketDelay, +maxnoofCandidateRelayUEs, +maxnoofSuccessfulPSCellChangeReports, +maxnoofCellsTSS, +maxnoofPeriodicities, +maxnoofPartiallyAllowedS-NSSAIs + +FROM NGAP-Constants + +Criticality, +ProcedureCode, +ProtocolIE-ID, +TriggeringMessage + +FROM NGAP-CommonDataTypes + +ProtocolExtensionContainer{}, +ProtocolIE-Container{}, +NGAP-PROTOCOL-EXTENSION, +ProtocolIE-SingleContainer{}, +NGAP-PROTOCOL-IES + +FROM NGAP-Containers; + +-- A + +AdditionalDLUPTNLInformationForHOList ::= SEQUENCE (SIZE(1..maxnoofMultiConnectivityMinusOne)) OF AdditionalDLUPTNLInformationForHOItem + +AdditionalDLUPTNLInformationForHOItem ::= SEQUENCE { +    additionalDL-NGU-UP-TNLInformation            UPTTransportLayerInformation, +    additionalQosFlowSetupResponseList            QosFlowListWithDataForwarding, + +``` + additionalDLForwardingUPTNLInformation UPTransportLayerInformation OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { AdditionalDLUPTNLInformationForHOItem-ExtIEs} } OPTIONAL, + ... +} + +AdditionalDLUPTNLInformationForHOItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-AdditionalRedundantDL-NGU-UP-TNLInformation CRITICALITY ignore EXTENSION UPTransportLayerInformation PRESENCE optional }, + ... +} + +AdditionalQosFlowInformation ::= ENUMERATED { + more-likely, + ... +} + +AerialUEsubscriptionInformation ::= ENUMERATED { + allowed, + not-allowed, + ... +} + +A2X-PC5-FlowBitRates ::= SEQUENCE { + a2X-GuaranteedFlowBitRate BitRate, +``` + +``` + a2X-MaximumFlowBitRate BitRate, + iE-Extensions ProtocolExtensionContainer { {A2X-PC5-FlowBitRates-ExtIEs} } OPTIONAL, + ... +} + +A2X-PC5-FlowBitRates-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +A2X-PC5-QoS-Flow-List ::= SEQUENCE (SIZE(1..maxnoofPC5QoSFlows)) OF A2X-PC5-QoS-Flow-Item + +A2X-PC5-QoS-Flow-Item ::= SEQUENCE { + a2X-PQI INTEGER (0..255, ...), + a2X-PC5-FlowBitRates A2X-PC5-FlowBitRates OPTIONAL, + a2X-Range ENUMERATED {m50, m80, m180, m200, + m350, m400, m500, m700, + m1000, ...} OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {A2X-PC5-QoS-Flow-Item-ExtIEs} } OPTIONAL, + ... +} + +A2X-PC5-QoS-Flow-Item-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +} + +A2X-PC5-QoS-Parameters ::= SEQUENCE { + a2X-PC5-QoS-Flow-List A2X-PC5-QoS-Flow-List, + a2X-PC5-LinkAggregateBitRates BitRate OPTIONAL, + iE-Extensions ProtocolExtensionContainer { A2X-PC5-QoS-Parameters-ExtIEs } OPTIONAL, + ... +} + +A2X-PC5-QoS-Parameters-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +AdditionalCancelledlocationReportingReferenceIDList ::= SEQUENCE (SIZE(1.. maxnoofAoIMinusOne)) OF AdditionalCancelledlocationReportingReferenceIDItem + +AdditionalCancelledlocationReportingReferenceIDItem ::= SEQUENCE { + locationReportingReferenceIDToBeCancelled LocationReportingReferenceID, + iE-Extensions ProtocolExtensionContainer { AdditionalCancelledlocationReportingReferenceIDItem-ExtIEs } OPTIONAL, + ... +} + +AdditionalCancelledlocationReportingReferenceIDItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +} + +AllocationAndRetentionPriority ::= SEQUENCE { + +priorityLevelARP               PriorityLevelARP, +pre-emptionCapability       Pre-emptionCapability, +pre-emptionVulnerability   Pre-emptionVulnerability, +iE-Extensions               ProtocolExtensionContainer { {AllocationAndRetentionPriority-ExtIEs} } OPTIONAL, +... + +} + +AllocationAndRetentionPriority-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + +... + +} + +Allowed-CAG-List-per-PLMN ::= SEQUENCE (SIZE(1..maxnoofAllowedCAGsperPLMN)) OF CAG-ID + +AllowedNSSAI ::= SEQUENCE (SIZE(1..maxnoofAllowedS-NSSAIs)) OF AllowedNSSAI-Item + +AllowedNSSAI-Item ::= SEQUENCE { + +s-NSSAI                   S-NSSAI, +iE-Extensions           ProtocolExtensionContainer { {AllowedNSSAI-Item-ExtIEs} } OPTIONAL, +... + +} + +``` +AllowedNSSAI-Item-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +Allowed-PNI-NPN-List ::= SEQUENCE (SIZE(1..maxnoofEPLMNsPlusOne)) OF Allowed-PNI-NPN-Item +``` + +``` +Allowed-PNI-NPN-Item ::= SEQUENCE { +``` + +``` + pLMNIdentity PLMNIdentity, +``` + +``` + pNI-NPN-restricted ENUMERATED {restricted, not-restricted, ...}, +``` + +``` + allowed-CAG-List-per-PLMN Allowed-CAG-List-per-PLMN, +``` + +``` + iE-Extensions ProtocolExtensionContainer { {Allowed-PNI-NPN-Item-ExtIEs} } OPTIONAL, +``` + +``` + ... +``` + +``` +} +``` + +``` +Allowed-PNI-NPN-Item-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +AllowedTACs ::= SEQUENCE (SIZE(1..maxnoofAllowedAreas)) OF TAC +``` + +``` +AlternativeQoSParaSetIndex ::= INTEGER (1..8, ...) +``` + +AlternativeQoSParaSetNotifyIndex ::= INTEGER (0..8, ...) + +``` +AlternativeQoSParaSetList ::= SEQUENCE (SIZE(1..maxnoofQosParaSets)) OF AlternativeQoSParaSetItem +``` + +``` + +AlternativeQoSParaSetItem ::= SEQUENCE { + alternativeQoSParaSetIndex AlternativeQoSParaSetIndex, + guaranteedFlowBitRateDL BitRate OPTIONAL, + guaranteedFlowBitRateUL BitRate OPTIONAL, + packetDelayBudget PacketDelayBudget OPTIONAL, + packetErrorRate PacketErrorRate OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {AlternativeQoSParaSetItem-ExtIEs} } OPTIONAL, + ... +} + +``` + +``` + +AlternativeQoSParaSetItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +AssistanceInformationQoE-Meas ::= INTEGER (1..16, ...) + +AMFName ::= PrintableString (SIZE(1..150, ...)) + +AMFNameVisibleString ::= VisibleString (SIZE(1..150, ...)) + +AMFNameUTF8String ::= UTF8String (SIZE(1..150, ...)) + +AMFPagingTarget ::= CHOICE { +    globalRANNodeID       GlobalRANNodeID, +    tAI                   TAI, +    choice-Extensions    ProtocolIE-SingleContainer { {AMFPagingTarget-ExtIEs} } +} + +AMFPagingTarget-ExtIEs NGAP-PROTOCOL-IES ::= { +    ... +} + +AMFPointer ::= BIT STRING (SIZE(6)) + +AMFRegionID ::= BIT STRING (SIZE(8)) + +AMFSetID ::= BIT STRING (SIZE(10)) + +AMF-TNLAssociationSetupList ::= SEQUENCE (SIZE(1..maxnoofTNLAssociations)) OF AMF-TNLAssociationSetupItem + +AMF-TNLAssociationSetupItem ::= SEQUENCE { +    aMF-TNLAssociationAddress      CPTransportLayerInformation, + +``` + iE-Extensions ProtocolExtensionContainer { {AMF-TNLAssociationSetupItem-ExtIEs} } OPTIONAL, + ... +} + +AMF-TNLAssociationSetupItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +AMF-TNLAssociationToAddList ::= SEQUENCE (SIZE(1..maxnoofTNLAssociations)) OF AMF-TNLAssociationToAddItem + +AMF-TNLAssociationToAddItem ::= SEQUENCE { + aMF-TNLAssociationAddress CPTransportLayerInformation, + tNLAssociationUsage TNLAssociationUsage OPTIONAL, + tNLAddressWeightFactor TNLAddressWeightFactor, + iE-Extensions ProtocolExtensionContainer { {AMF-TNLAssociationToAddItem-ExtIEs} } OPTIONAL, + ... +} + +AMF-TNLAssociationToAddItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +AMF-TNLAssociationToRemoveList ::= SEQUENCE (SIZE(1..maxnoofTNLAssociations)) OF AMF-TNLAssociationToRemoveItem +``` + +``` +AMF-TNLAssociationToRemoveItem ::= SEQUENCE { + aMF-TNLAssociationAddress CPTransportLayerInformation, + iE-Extensions ProtocolExtensionContainer { {AMF-TNLAssociationToRemoveItem-ExtIEs} } OPTIONAL, + ... +} + +AMF-TNLAssociationToRemoveItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + {ID id-TNLAssociationTransportLayerAddressNGRAN CRITICALITY reject EXTENSION CPTransportLayerInformation PRESENCE optional}, + ... +} + +AMF-TNLAssociationToUpdateList ::= SEQUENCE (SIZE(1..maxnoofTNLAssociations)) OF AMF-TNLAssociationToUpdateItem + +AMF-TNLAssociationToUpdateItem ::= SEQUENCE { + aMF-TNLAssociationAddress CPTransportLayerInformation, + tNLAssociationUsage TNLAssociationUsage OPTIONAL, + tNLAddressWeightFactor TNLAddressWeightFactor OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {AMF-TNLAssociationToUpdateItem-ExtIEs} } OPTIONAL, + ... +} + +AMF-TNLAssociationToUpdateItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +} + +AMF-UE-NGAP-ID ::= INTEGER (0..1099511627775) + +AreaOfInterest ::= SEQUENCE { + areaOfInterestTAIList AreaOfInterestTAIList OPTIONAL, + areaOfInterestCellList AreaOfInterestCellList OPTIONAL, + areaOfInterestRANNodeList AreaOfInterestRANNodeList OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {AreaOfInterest-ExtIEs} } OPTIONAL, + ... +} + +AreaOfInterest-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +AreaOfInterestCellList ::= SEQUENCE (SIZE(1..maxnoofCellinAoI)) OF AreaOfInterestCellItem + +AreaOfInterestCellItem ::= SEQUENCE { + nGRAN-CGI NGRAN-CGI, + iE-Extensions ProtocolExtensionContainer { {AreaOfInterestCellItem-ExtIEs} } OPTIONAL, + ... +} +``` + +} + +AreaOfInterestCellItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + +... + +} + +AreaOfInterestList ::= SEQUENCE (SIZE(1..maxnoofAoI)) OF AreaOfInterestItem + +AreaOfInterestItem ::= SEQUENCE { + +areaOfInterest AreaOfInterest, + +locationReportingReferenceID LocationReportingReferenceID, + +iE-Extensions ProtocolExtensionContainer { {AreaOfInterestItem-ExtIEs} } OPTIONAL, + +... + +} + +AreaOfInterestItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + +... + +} + +AreaOfInterestRANNodeList ::= SEQUENCE (SIZE(1..maxnoofRANNodeinAoI)) OF AreaOfInterestRANNodeItem + +AreaOfInterestRANNodeItem ::= SEQUENCE { + +globalRANNodeID GlobalRANNodeID, + +``` + iE-Extensions ProtocolExtensionContainer { {AreaOfInterestRANNodeItem-ExtIEs} } OPTIONAL, + ... +} + +AreaOfInterestRANNodeItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +AreaOfInterestTAIList ::= SEQUENCE (SIZE(1..maxnoofTAIinAoI)) OF AreaOfInterestTAIItem + +AreaOfInterestTAIItem ::= SEQUENCE { + tAI TAI, + iE-Extensions ProtocolExtensionContainer { {AreaOfInterestTAIItem-ExtIEs} } OPTIONAL, + ... +} + +AreaOfInterestTAIItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +AssistanceDataForPaging ::= SEQUENCE { + assistanceDataForRecommendedCells AssistanceDataForRecommendedCells OPTIONAL, + pagingAttemptInformation PagingAttemptInformation OPTIONAL, +``` + +``` + iE-Extensions ProtocolExtensionContainer { {AssistanceDataForPaging-ExtIEs} } OPTIONAL, + ... +} + +AssistanceDataForPaging-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-NPN-PagingAssistanceInformation CRITICALITY ignore EXTENSION NPN-PagingAssistanceInformation PRESENCE optional }| + { ID id-PagingAssisDataforCEcapabUE CRITICALITY ignore EXTENSION PagingAssisDataforCEcapabUE PRESENCE optional }, + ... +} + +AssistanceDataForRecommendedCells ::= SEQUENCE { + recommendedCellsForPaging RecommendedCellsForPaging, + iE-Extensions ProtocolExtensionContainer { {AssistanceDataForRecommendedCells-ExtIEs} } OPTIONAL, + ... +} + +AssistanceDataForRecommendedCells-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +AssociatedMBSQosFlowSetupRequestList ::= SEQUENCE (SIZE(1..maxnoofMBSQoSFlows)) OF AssociatedMBSQosFlowSetupRequestItem + +AssociatedMBSQosFlowSetupRequestItem ::= SEQUENCE { +``` + +``` + mBS-QosFlowIdentifier QosFlowIdentifier, + associatedUnicastQosFlowIdentifier QosFlowIdentifier, + iE-Extensions ProtocolExtensionContainer { { AssociatedMBSQosFlowSetupRequestItem-ExtIEs} } OPTIONAL, + ... +} + +AssociatedMBSQosFlowSetupRequestItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +AssociatedMBSQosFlowSetuporModifyRequestList ::= SEQUENCE (SIZE(1..maxnoofMBSQoSFlows)) OF AssociatedMBSQosFlowSetuporModifyRequestItem + +AssociatedMBSQosFlowSetuporModifyRequestItem ::= SEQUENCE { + mBS-QosFlowIdentifier QosFlowIdentifier, + associatedUnicastQosFlowIdentifier QosFlowIdentifier, + iE-Extensions ProtocolExtensionContainer { { AssociatedMBSQosFlowSetuporModifyRequestItem-ExtIEs} } OPTIONAL, + ... +} + +AssociatedMBSQosFlowSetuporModifyRequestItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +AssociatedQosFlowList ::= SEQUENCE (SIZE(1..maxnoofQosFlows)) OF AssociatedQosFlowItem + +AssociatedQosFlowItem ::= SEQUENCE { +    qosFlowIdentifier          QosFlowIdentifier, +    qosFlowMappingIndication    ENUMERATED {ul, dl, ...}                    OPTIONAL, +    iE-Extensions          ProtocolExtensionContainer { {AssociatedQosFlowItem-ExtIEs} }    OPTIONAL, +    ... +} + +AssociatedQosFlowItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +    { ID id-CurrentQoSParaSetIndex CRITICALITY ignore EXTENSION AlternativeQoSParaSetIndex PRESENCE optional }, +    ... +} + +AssociatedSessionID ::= OCTET STRING + +AuthenticatedIndication ::= ENUMERATED {true, ...} + +AveragingWindow ::= INTEGER (0..4095, ...) + +AreaScopeOfMDT-NR ::= CHOICE { +    cellBased                CellBasedMDT-NR, +    tABased                  TABasedMDT, + +``` + pLMNWide NULL, + tAIBased TAIBasedMDT, + choice-Extensions ProtocolIE-SingleContainer { {AreaScopeOfMDT-NR-ExtIEs} } +} + +AreaScopeOfMDT-NR-ExtIEs NGAP-PROTOCOL-IES ::= { + { ID id-PNI-NPNBasedMDT CRITICALITY ignore TYPE PNI-NPNBasedMDT PRESENCE mandatory } | + { ID id-SNPN-CellBasedMDT CRITICALITY ignore TYPE SNPN-CellBasedMDT PRESENCE mandatory } | + { ID id-SNPN-TAIBasedMDT CRITICALITY ignore TYPE SNPN-TAIBasedMDT PRESENCE mandatory } | + { ID id-SNPN-BasedMDT CRITICALITY ignore TYPE SNPN-BasedMDT PRESENCE mandatory }, + ... +} + +AreaScopeOfMDT-EUTRA ::= CHOICE { + cellBased CellBasedMDT-EUTRA, + tABased TABasedMDT, + pLMNWide NULL, + tAIBased TAIBasedMDT, + choice-Extensions ProtocolIE-SingleContainer { {AreaScopeOfMDT-EUTRA-ExtIEs} } +} + +AreaScopeOfMDT-EUTRA-ExtIEs NGAP-PROTOCOL-IES ::= { + ... +} +``` + +``` +} +``` + +``` +AreaScopeOfNeighCellsList ::= SEQUENCE (SIZE(1..maxnoofFreqforMDT)) OF AreaScopeOfNeighCellsItem +``` + +``` +AreaScopeOfNeighCellsItem ::= SEQUENCE { +``` + +``` + nrFrequencyInfo NRFrequencyInfo, +``` + +``` + pciListForMDT PCIListForMDT OPTIONAL, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { AreaScopeOfNeighCellsItem-ExtIEs} } OPTIONAL, +``` + +``` + ... +``` + +``` +} +``` + +``` +AreaScopeOfNeighCellsItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +AreaScopeOfQMC ::= CHOICE { +``` + +``` + cellBased CellBasedQMC, +``` + +``` + tABased TABasedQMC, +``` + +``` + tAIBased TAIBasedQMC, +``` + +``` + pLMNAreaBased PLMNAreaBasedQMC, +``` + +``` + choice-Extensions ProtocolIE-SingleContainer { { AreaScopeOfQMC-ExtIEs} } +``` + +``` +} +``` + +``` +AreaScopeOfQMC-ExtIEs NGAP-PROTOCOL-IES ::= { +``` + +``` + ... +} + +AvailableRANVisibleQoEMetrics ::= SEQUENCE { + applicationLayerBufferLevelList ENUMERATED {true, ...} OPTIONAL, + playoutDelayForMediaStartup ENUMERATED {true, ...} OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { AvailableRANVisibleQoEMetrics-ExtIEs} } OPTIONAL, + ... +} + +AvailableRANVisibleQoEMetrics-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- B + +BeamMeasurementsReportConfiguration ::= SEQUENCE { + beamMeasurementsReportQuantity BeamMeasurementsReportQuantity OPTIONAL, + maxNrofRS-IndexesToReport MaxNrofRS-IndexesToReport OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { BeamMeasurementsReportConfiguration-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +BeamMeasurementsReportConfiguration-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +BeamMeasurementsReportQuantity ::= SEQUENCE { + rSRP ENUMERATED {true, ...}, + rSRQ ENUMERATED {true, ...}, + SINR ENUMERATED {true, ...}, + iE-Extensions ProtocolExtensionContainer { { BeamMeasurementsReportQuantity-ExtIEs } } OPTIONAL, + ... +} + +BeamMeasurementsReportQuantity-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +BitRate ::= INTEGER (0..40000000000000, ...) + +BroadcastCancelledAreaList ::= CHOICE { + cellIDCancelledEUTRA CellIDCancelledEUTRA, + tAICancelledEUTRA TAICancelledEUTRA, + emergencyAreaIDCancelledEUTRA EmergencyAreaIDCancelledEUTRA, +``` + +``` + cellIDCancelledNR CellIDCancelledNR, + tAICancelledNR TAICancelledNR, + emergencyAreaIDCancelledNR EmergencyAreaIDCancelledNR, + choice-Extensions ProtocolIE-SingleContainer { {BroadcastCancelledAreaList-ExtIEs} } + } + + BroadcastCancelledAreaList-ExtIEs NGAP-PROTOCOL-IES ::= { + ... + } + + BroadcastCompletedAreaList ::= CHOICE { + cellIDBroadcastEUTRA CellIDBroadcastEUTRA, + tAIBroadcastEUTRA TAIBroadcastEUTRA, + emergencyAreaIDBroadcastEUTRA EmergencyAreaIDBroadcastEUTRA, + cellIDBroadcastNR CellIDBroadcastNR, + tAIBroadcastNR TAIBroadcastNR, + emergencyAreaIDBroadcastNR EmergencyAreaIDBroadcastNR, + choice-Extensions ProtocolIE-SingleContainer { {BroadcastCompletedAreaList-ExtIEs} } + } + + BroadcastCompletedAreaList-ExtIEs NGAP-PROTOCOL-IES ::= { + ... + } +``` + +BroadcastPLMNList ::= SEQUENCE (SIZE(1..maxnoofBPLMNs)) OF BroadcastPLMNItem + +BroadcastPLMNItem ::= SEQUENCE { +    pLMNIdentity            PLMNIdentity, +    tAISliceSupportList    SliceSupportList, +    iE-Extensions        ProtocolExtensionContainer { {BroadcastPLMNItem-ExtIEs} } OPTIONAL, +    ... +} + +BroadcastPLMNItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +    {ID id-NPN-Support                    CRITICALITY reject  EXTENSION NPN-Support                    PRESENCE optional}| +    {ID id-ExtendedTAISliceSupportList  CRITICALITY reject  EXTENSION ExtendedSliceSupportList  PRESENCE optional}| +    {ID id-TAINSAGSupportList          CRITICALITY ignore  EXTENSION TAINSAGSupportList          PRESENCE optional}, +    ... +} + +BroadcastTransportFailureTransfer ::= SEQUENCE { +    mBS-SessionID            MBS-SessionID, +    cause                    Cause, +    criticalityDiagnostics  CriticalityDiagnostics                                            OPTIONAL, +    iE-Extensions          ProtocolExtensionContainer { { BroadcastTransportFailureTransfer-ExtIEs} } OPTIONAL, +    ... +} + +``` +} + +BroadcastTransportFailureTransfer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +BroadcastTransportRequestTransfer ::= SEQUENCE { + mBS-SessionID MBS-SessionID, + mBS-SessionTNLInfoNGRAN MBS-SessionTNLInfoNGRAN, + iE-Extensions ProtocolExtensionContainer { {BroadcastTransportRequestTransfer-ExtIEs} } OPTIONAL, + ... +} + +BroadcastTransportRequestTransfer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +BroadcastTransportResponseTransfer ::= SEQUENCE { + mBS-SessionID MBS-SessionID, + iE-Extensions ProtocolExtensionContainer { {BroadcastTransportResponseTransfer-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +BroadcastTransportResponseTransfer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +BluetoothMeasurementConfiguration ::= SEQUENCE { + bluetoothMeasConfig BluetoothMeasConfig, + bluetoothMeasConfigNameList BluetoothMeasConfigNameList OPTIONAL, + bt-rssi ENUMERATED {true, ...} OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { BluetoothMeasurementConfiguration-ExtIEs } } OPTIONAL, + ... +} + +BluetoothMeasurementConfiguration-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +BluetoothMeasConfigNameList ::= SEQUENCE (SIZE(1..maxnoofBluetoothName)) OF BluetoothMeasConfigNameItem + +BluetoothMeasConfigNameItem ::= SEQUENCE { + bluetoothName BluetoothName, + iE-Extensions ProtocolExtensionContainer { { BluetoothMeasConfigNameItem-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +BluetoothMeasConfigNameItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +BluetoothMeasConfig ::= ENUMERATED {setup, ...} +``` + +``` +BluetoothName ::= OCTET STRING (SIZE (1..248)) +``` + +``` +BurstArrivalTime ::= OCTET STRING +``` + +``` +BurstArrivalTimeWindow ::= SEQUENCE { +``` + +``` + burstArrivalTimeWindowStart INTEGER (0..640000, ...), +``` + +``` + burstArrivalTimeWindowEnd INTEGER (0..640000, ...), +``` + +``` + iE-Extension ProtocolExtensionContainer { {BurstArrivalTimeWindow-ExtIEs} } OPTIONAL, +``` + +``` + ... +``` + +``` +} +``` + +``` +BurstArrivalTimeWindow-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +-- C +``` + +CAG-ID ::= BIT STRING (SIZE(32)) + +CandidateRelayUEInformationList ::= SEQUENCE (SIZE(1.. maxnoofCandidateRelayUEs)) OF CandidateRelayUEInformationItem + +CandidateRelayUEInformationItem ::= SEQUENCE { +    candidateRelayUE-Id       CandidateRelayUE-ID, +    iE-Extensions            ProtocolExtensionContainer { { CandidateRelayUEInformationItem-ExtIEs} } OPTIONAL, +    ... +} + +CandidateRelayUEInformationItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +    ... +} + +CandidateRelayUE-ID ::= BIT STRING (SIZE(24)) + +CancelAllWarningMessages ::= ENUMERATED { +    true, +    ... +} + +CancelledCellsInEAI-EUTRA ::= SEQUENCE (SIZE(1..maxnoofCellinEAI)) OF CancelledCellsInEAI-EUTRA-Item + +``` +CancelledCellsInEAI-EUTRA-Item ::= SEQUENCE { + eUTRA-CGI EUTRA-CGI, + numberOfBroadcasts NumberOfBroadcasts, + iE-Extensions ProtocolExtensionContainer { {CancelledCellsInEAI-EUTRA-Item-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +CancelledCellsInEAI-EUTRA-Item-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +CancelledCellsInEAI-NR ::= SEQUENCE (SIZE(1..maxnoofCellinEAI)) OF CancelledCellsInEAI-NR-Item +``` + +``` +CancelledCellsInEAI-NR-Item ::= SEQUENCE { + nR-CGI NR-CGI, + numberOfBroadcasts NumberOfBroadcasts, + iE-Extensions ProtocolExtensionContainer { {CancelledCellsInEAI-NR-Item-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +CancelledCellsInEAI-NR-Item-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +} + +CancelledCellsInTAI-EUTRA ::= SEQUENCE (SIZE(1..maxnoofCellinTAI)) OF CancelledCellsInTAI-EUTRA-Item + +CancelledCellsInTAI-EUTRA-Item ::= SEQUENCE { + +eUTRA-CGI EUTRA-CGI, + +numberOfBroadcasts NumberOfBroadcasts, + +iE-Extensions ProtocolExtensionContainer { {CancelledCellsInTAI-EUTRA-Item-ExtIEs} } OPTIONAL, + +... + +} + +CancelledCellsInTAI-EUTRA-Item-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + +... + +} + +CancelledCellsInTAI-NR ::= SEQUENCE (SIZE(1..maxnoofCellinTAI)) OF CancelledCellsInTAI-NR-Item + +CancelledCellsInTAI-NR-Item ::= SEQUENCE{ + +nR-CGI NR-CGI, + +numberOfBroadcasts NumberOfBroadcasts, + +iE-Extensions ProtocolExtensionContainer { {CancelledCellsInTAI-NR-Item-ExtIEs} } OPTIONAL, + +... + +} + +``` +CancelledCellsInTAI-NR-Item-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +CandidateCellList ::= SEQUENCE (SIZE(1.. maxnoofCandidateCells)) OF CandidateCellItem + +CandidateCellItem ::= SEQUENCE{ + candidateCell CandidateCell, + iE-Extensions ProtocolExtensionContainer { {CandidateCellItem-ExtIEs} } OPTIONAL, + ... +} + +CandidateCellItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +CandidateCell ::= CHOICE { + candidateCGI CandidateCellID, + candidatePCI CandidatePCI, + choice-Extensions ProtocolIE-SingleContainer { { CandidateCell-ExtIEs} } +} +``` + +``` +CandidateCell-ExtIEs NGAP-PROTOCOL-IES ::= { + ... +} +``` + +``` +CandidateCellID ::= SEQUENCE { + candidateCellID NR-CGI, + iE-Extensions ProtocolExtensionContainer { { CandidateCellID-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +CandidateCellID-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +CandidatePCI ::= SEQUENCE { + candidatePCI INTEGER (0..1007, ...), + candidateNRARFCN INTEGER (0..maxNRARFCN), + iE-Extensions ProtocolExtensionContainer { { CandidatePCI-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +CandidatePCI-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +} + +Cause ::= CHOICE { + radioNetwork CauseRadioNetwork, + transport CauseTransport, + nas CauseNas, + protocol CauseProtocol, + misc CauseMisc, + choice-Extensions ProtocolIE-SingleContainer { {Cause-ExtIEs} } +} + +Cause-ExtIEs NGAP-PROTOCOL-IES ::= { + ... +} + +CauseMisc ::= ENUMERATED { + control-processing-overload, + not-enough-user-plane-processing-resources, + hardware-failure, + om-intervention, + unknown-PLMN-or-SNPN, + unspecified, +``` + +``` + ... +} + +CauseNas ::= ENUMERATED { + normal-release, + authentication-failure, + deregister, + unspecified, + ..., + uE-not-in-PLMN-serving-area, + mobile-IAB-not-authorized +} + +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, + txnrelocoverall-expiry, + successful-handover, + release-due-to-ngran-generated-reason, + release-due-to-5gc-generated-reason, + handover-cancelled, + partial-handover, + ho-failure-in-target-5GC-ngran-node-or-target-system, + ho-target-not-allowed, + tngrelocoverall-expiry, + tngrelocprep-expiry, + cell-not-available, + unknown-targetID, + no-radio-resources-available-in-target-cell, + unknown-local-UE-NGAP-ID, + inconsistent-remote-UE-NGAP-ID, + handover-desirable-for-radio-reason, + time-critical-handover, + resource-optimisation-handover, + reduce-load-in-serving-cell, + user-inactivity, +} +``` + +radio-connection-with-ue-lost, +radio-resources-not-available, +invalid-qos-combination, +failure-in-radio-interface-procedure, +interaction-with-other-procedure, +unknown-PDU-session-ID, +unkown-qos-flow-ID, +multiple-PDU-session-ID-instances, +multiple-qos-flow-ID-instances, +encryption-and-or-integrity-protection-algorithms-not-supported, +ng-intra-system-handover-triggered, +ng-inter-system-handover-triggered, +xn-handover-triggered, +not-supported-5QI-value, +ue-context-transfer, +ims-voice-eps-fallback-or-rat-fallback-triggered, +up-integrity-protection-not-possible, +up-confidentiality-protection-not-possible, +slice-not-supported, +ue-in-rrc-inactive-state-not-reachable, +redirection, +resources-not-available-for-the-slice, +ue-max-integrity-protected-data-rate-reason, + +``` + release-due-to-cn-detected-mobility, + ... + n26-interface-not-available, + release-due-to-pre-emption, + multiple-location-reporting-reference-ID-instances, + rsn-not-available-for-the-up, + npn-access-denied, + cag-only-access-denied, + insufficient-ue-capabilities, + redcap-ue-not-supported, + unknown-MBS-Session-ID, + indicated-MBS-session-area-information-not-served-by-the-gNB, + inconsistent-slice-info-for-the-session, + misaligned-association-for-multicast-unicast +} +``` + +``` +CauseTransport ::= ENUMERATED { + transport-resource-unavailable, + unspecified, + ... +} +``` + +``` +Cell-CAGInformation ::= SEQUENCE { +``` + +``` + nGRAN-CGI NGRAN-CGI, + cellCAGList CellCAGList, + iE-Extensions ProtocolExtensionContainer { {Cell-CAGInformation-ExtIEs} } OPTIONAL, + ... +} + +Cell-CAGInformation-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +CellCAGList ::= SEQUENCE (SIZE(1..maxnoofCAGSperCell)) OF CAG-ID + +CellIDBroadcastEUTRA ::= SEQUENCE (SIZE(1..maxnoofCellIDforWarning)) OF CellIDBroadcastEUTRA-Item + +CellIDBroadcastEUTRA-Item ::= SEQUENCE { + eUTRA-CGI EUTRA-CGI, + iE-Extensions ProtocolExtensionContainer { {CellIDBroadcastEUTRA-Item-ExtIEs} } OPTIONAL, + ... +} + +CellIDBroadcastEUTRA-Item-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +} +``` + +``` +CellIDBroadcastNR ::= SEQUENCE (SIZE(1..maxnoofCellIDforWarning)) OF CellIDBroadcastNR-Item +``` + +``` +CellIDBroadcastNR-Item ::= SEQUENCE { +``` + +``` + nR-CGI NR-CGI, +``` + +``` + iE-Extensions ProtocolExtensionContainer { {CellIDBroadcastNR-Item-ExtIEs} } OPTIONAL, +``` + +``` + ... +``` + +``` +} +``` + +``` +CellIDBroadcastNR-Item-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +CellIDCancelledEUTRA ::= SEQUENCE (SIZE(1..maxnoofCellIDforWarning)) OF CellIDCancelledEUTRA-Item +``` + +``` +CellIDCancelledEUTRA-Item ::= SEQUENCE { +``` + +``` + eUTRA-CGI EUTRA-CGI, +``` + +``` + numberOfBroadcasts NumberOfBroadcasts, +``` + +``` + iE-Extensions ProtocolExtensionContainer { {CellIDCancelledEUTRA-Item-ExtIEs} } OPTIONAL, +``` + +``` + ... +``` + +``` +} +``` + +``` +CellIDCancelledEUTRA-Item-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +CellIDCancelledNR ::= SEQUENCE (SIZE(1..maxnoofCellIDforWarning)) OF CellIDCancelledNR-Item + +CellIDCancelledNR-Item ::= SEQUENCE { + nR-CGI NR-CGI, + numberOfBroadcasts NumberOfBroadcasts, + iE-Extensions ProtocolExtensionContainer { {CellIDCancelledNR-Item-ExtIEs} } OPTIONAL, + ... +} + +CellIDCancelledNR-Item-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +CellIDListForRestart ::= CHOICE { + eUTRA-CGIListforRestart EUTRA-CGIList, + nR-CGIListforRestart NR-CGIList, + choice-Extensions ProtocolIE-SingleContainer { {CellIDListForRestart-ExtIEs} } +} +``` + +``` +CellIDListForRestart-ExtIEs NGAP-PROTOCOL-IES ::= { + ... +} +``` + +``` +CellSize ::= ENUMERATED {verysmall, small, medium, large, ...} +``` + +``` +CellType ::= SEQUENCE { + cellSize CellSize, + iE-Extensions ProtocolExtensionContainer { {CellType-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +CellType-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +CEmodeBSupport-Indicator ::= ENUMERATED {supported,...} +``` + +``` +CEmodeBrestricted ::= ENUMERATED { + restricted, + not-restricted, +``` + +``` + ... +} + +ClockAccuracy ::= CHOICE { + clockAccuracyValue INTEGER (1..40000000, ...), + clockAccuracyIndex INTEGER (32..47, ...), + choice-Extensions ProtocolIE-SingleContainer { { ClockAccuracy-ExtIEs } } +} + +ClockAccuracy-ExtIEs NGAP-PROTOCOL-IES ::= { + ... +} + +ClockQualityAcceptanceIndication ::= SEQUENCE { + clockQualityAcceptanceCriteria ClockQualityAcceptanceCriteria, + iE-Extensions ProtocolExtensionContainer { {ClockQualityAcceptanceIndication-ExtIEs} } OPTIONAL, + ... +} + +ClockQualityAcceptanceIndication-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +ClockQualityAcceptanceCriteria ::= SEQUENCE { + synchronisationState BIT STRING (SIZE(8, ...)) OPTIONAL, + traceabletoUTC ENUMERATED {true, ...} OPTIONAL, + traceabletoGNSS ENUMERATED {true, ...} OPTIONAL, + clockFrequencyStability BIT STRING (SIZE(16)) OPTIONAL, + clockAccuracy INTEGER (1..400000000, ...) OPTIONAL, + parentTimeSource BIT STRING (SIZE(16, ...)) OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { ClockQualityAcceptanceCriteria-ExtIEs} } OPTIONAL, + ... +} + +ClockQualityAcceptanceCriteria-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +ClockQualityReportingControlInfo ::= SEQUENCE { + clockQualityDetailLevel ClockQualityDetailLevel, + iE-Extensions ProtocolExtensionContainer { {ClockQualityReportingControlInfo-ExtIEs} } OPTIONAL, + ... +} + +ClockQualityReportingControlInfo-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +} + +ClockQualityDetailLevel ::= CHOICE { +    clockQualityMetrics                          NULL, +    clockQualityAcceptanceIndication          ClockQualityAcceptanceIndication, +    choice-extensions          ProtocolIE-SingleContainer { {ClockQualityDetailLevel-ExtIEs} } +} + +ClockQualityDetailLevel-ExtIEs NGAP-PROTOCOL-IES ::= { +    ... +} + +CNAssistedRANTuning ::= SEQUENCE { +    expectedUEBehaviour                  ExpectedUEBehaviour                  OPTIONAL, +    iE-Extensions          ProtocolExtensionContainer { {CNAssistedRANTuning-ExtIEs} } OPTIONAL, +    ... +} + +CNAssistedRANTuning-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +    ... +} + +CNsubgroupID ::= INTEGER (0..7, ...) + +CNTypeRestrictionsForEquivalent ::= SEQUENCE (SIZE(1..maxnoofEPLMNs)) OF CNTypeRestrictionsForEquivalentItem + +CNTypeRestrictionsForEquivalentItem ::= SEQUENCE { + +plmnIdentity PLMNIdentity, + +cn-Type ENUMERATED {epc-forbidden, fiveGC-forbidden, ...}, + +iE-Extensions ProtocolExtensionContainer { {CNTypeRestrictionsForEquivalentItem-ExtIEs} } OPTIONAL, + +... + +} + +CNTypeRestrictionsForEquivalentItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + +... + +} + +CNTypeRestrictionsForServing ::= ENUMERATED { + +epc-forbidden, + +... + +} + +CommonNetworkInstance ::= OCTET STRING + +CompletedCellsInEAI-EUTRA ::= SEQUENCE (SIZE(1..maxnoofCellinEAI)) OF CompletedCellsInEAI-EUTRA-Item + +``` +CompletedCellsInEAI-EUTRA-Item ::= SEQUENCE { + eUTRA-CGI EUTRA-CGI, + iE-Extensions ProtocolExtensionContainer { {CompletedCellsInEAI-EUTRA-Item-ExtIEs} } OPTIONAL, + ... +} + +CompletedCellsInEAI-EUTRA-Item-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +CompletedCellsInEAI-NR ::= SEQUENCE (SIZE(1..maxnoofCellinEAI)) OF CompletedCellsInEAI-NR-Item + +CompletedCellsInEAI-NR-Item ::= SEQUENCE { + nR-CGI NR-CGI, + iE-Extensions ProtocolExtensionContainer { {CompletedCellsInEAI-NR-Item-ExtIEs} } OPTIONAL, + ... +} + +CompletedCellsInEAI-NR-Item-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +CompletedCellsInTAI-EUTRA ::= SEQUENCE (SIZE(1..maxnoofCellinTAI)) OF CompletedCellsInTAI-EUTRA-Item +``` + +``` +CompletedCellsInTAI-EUTRA-Item ::= SEQUENCE{ + eUTRA-CGI EUTRA-CGI, + iE-Extensions ProtocolExtensionContainer { {CompletedCellsInTAI-EUTRA-Item-ExtIEs} } OPTIONAL, + ... +} + +CompletedCellsInTAI-EUTRA-Item-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +CompletedCellsInTAI-NR ::= SEQUENCE (SIZE(1..maxnoofCellinTAI)) OF CompletedCellsInTAI-NR-Item + +CompletedCellsInTAI-NR-Item ::= SEQUENCE{ + nR-CGI NR-CGI, + iE-Extensions ProtocolExtensionContainer { {CompletedCellsInTAI-NR-Item-ExtIEs} } OPTIONAL, + ... +} + +CompletedCellsInTAI-NR-Item-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +ConcurrentWarningMessageInd ::= ENUMERATED { + true, + ... +} + +ConfidentialityProtectionIndication ::= ENUMERATED { + required, + preferred, + not-needed, + ... +} + +ConfidentialityProtectionResult ::= ENUMERATED { + performed, + not-performed, + ... +} + +ConfiguredTACIndication ::= ENUMERATED { + true, + ... +} +``` + +``` + +CoreNetworkAssistanceInformationForInactive ::= SEQUENCE { + uEIdentityIndexValue UEIdentityIndexValue, + uESpecificDRX PagingDRX OPTIONAL, + periodicRegistrationUpdateTimer PeriodicRegistrationUpdateTimer, + mICOModeIndication MICOModeIndication OPTIONAL, + tAIListForInactive TAIListForInactive, + expectedUEBehaviour ExpectedUEBehaviour OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {CoreNetworkAssistanceInformationForInactive-ExtIEs} } OPTIONAL, + ... +} + +``` + +``` + +CoreNetworkAssistanceInformationForInactive-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-EUTRA-PagingeDRXInformation CRITICALITY ignore EXTENSION EUTRA-PagingeDRXInformation PRESENCE optional } | + { ID id-ExtendedUEIdentityIndexValue CRITICALITY ignore EXTENSION ExtendedUEIdentityIndexValue PRESENCE optional } | + { ID id-UERadioCapabilityForPaging CRITICALITY ignore EXTENSION UERadioCapabilityForPaging PRESENCE optional } | + { ID id-MicoAllPLMN CRITICALITY ignore EXTENSION MicoAllPLMN PRESENCE optional } | + { ID id-NR-PagingeDRXInformation CRITICALITY ignore EXTENSION NR-PagingeDRXInformation PRESENCE optional } | + { ID id-PagingCauseIndicationForVoiceService CRITICALITY ignore EXTENSION PagingCauseIndicationForVoiceService PRESENCE optional } | + { ID id-PEIPSasssistanceInformation CRITICALITY ignore EXTENSION PEIPSasssistanceInformation PRESENCE optional } | + { ID id-HashedUEIdentityIndexValue CRITICALITY ignore EXTENSION HashedUEIdentityIndexValue PRESENCE optional } | + { ID id-CN-MT-CommunicationHandling CRITICALITY ignore EXTENSION CN-MT-CommunicationHandling PRESENCE optional }, + ... +} + +``` + +CN-MT-CommunicationHandling ::= ENUMERATED {supported, ...} + +COUNTValueForPDCP-SN12 ::= SEQUENCE { +    pDCP-SN12          INTEGER (0..4095), +    hFN-PDCP-SN12    INTEGER (0..1048575), +    iE-Extensions    ProtocolExtensionContainer { {COUNTValueForPDCP-SN12-ExtIEs} } OPTIONAL, +    ... +} + +COUNTValueForPDCP-SN12-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +    ... +} + +COUNTValueForPDCP-SN18 ::= SEQUENCE { +    pDCP-SN18          INTEGER (0..262143), +    hFN-PDCP-SN18    INTEGER (0..16383), +    iE-Extensions    ProtocolExtensionContainer { {COUNTValueForPDCP-SN18-ExtIEs} } OPTIONAL, +    ... +} + +COUNTValueForPDCP-SN18-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +    ... +} + +``` +} + +CoverageEnhancementLevel ::= OCTET STRING + +CPTransportLayerInformation ::= CHOICE { + endpointIPAddress TransportLayerAddress, + choice-Extensions ProtocolIE-SingleContainer { {CPTransportLayerInformation-ExtIEs} } +} + +CPTransportLayerInformation-ExtIEs NGAP-PROTOCOL-IES ::= { + { ID id-EndpointIPAddressAndPort CRITICALITY reject TYPE EndpointIPAddressAndPort PRESENCE mandatory }, + ... +} + +CriticalityDiagnostics ::= SEQUENCE { + procedureCode ProcedureCode OPTIONAL, + triggeringMessage TriggeringMessage OPTIONAL, + procedureCriticality Criticality OPTIONAL, + iEsCriticalityDiagnostics CriticalityDiagnostics-IE-List OPTIONAL, + iE-Extensions ProtocolExtensionContainer {{CriticalityDiagnostics-ExtIEs}} OPTIONAL, + ... +} +``` + +``` +CriticalityDiagnostics-ExtIEs NGAP-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 NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +C-RNTI ::= BIT STRING (SIZE(16)) + +CellBasedMDT-NR ::= SEQUENCE { + cellIdListforMDT CellIdListforMDT-NR, + iE-Extensions ProtocolExtensionContainer { {CellBasedMDT-NR-ExtIEs} } OPTIONAL, +``` + +``` + ... +} + +CellBasedMDT-NR-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +CellIdListforMDT-NR ::= SEQUENCE (SIZE(1..maxnoofCellIDforMDT)) OF NR-CGI + +CellBasedMDT-EUTRA ::= SEQUENCE { + cellIdListforMDT CellIdListforMDT-EUTRA, + iE-Extensions ProtocolExtensionContainer { {CellBasedMDT-EUTRA-ExtIEs} } OPTIONAL, + ... +} + +CellBasedMDT-EUTRA-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +CellBasedQMC ::= SEQUENCE { + cellIdListforQMC CellIdListforQMC, + iE-Extensions ProtocolExtensionContainer { {CellBasedQMC-ExtIEs} } OPTIONAL, +``` + +``` + ... +} + +CellBasedQMC-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +CellIdListforQMC ::= SEQUENCE (SIZE(1..maxnoofCellIDforQMC)) OF NGRAN-CGI + +CellIdListforMDT-EUTRA ::= SEQUENCE (SIZE(1..maxnoofCellIDforMDT)) OF EUTRA-CGI + +CAGListforMDT ::= SEQUENCE { + plmnID PLMNIdentity, + cAGID CAG-ID, + iE-Extensions ProtocolExtensionContainer { {CAGListforMDT-ExtIEs} } OPTIONAL, + ... +} + +CAGListforMDT-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +-- D + +DataCodingScheme ::= BIT STRING (SIZE(8)) + +DataForwardingAccepted ::= ENUMERATED { +    data-forwarding-accepted, +    ... +} + +DataForwardingNotPossible ::= ENUMERATED { +    data-forwarding-not-possible, +    ... +} + +DataForwardingResponseDRBList ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF DataForwardingResponseDRBItem + +DataForwardingResponseDRBItem ::= SEQUENCE { +    dRB-ID                                DRB-ID, +    dLForwardingUP-TNLInformation    UPTransportLayerInformation    OPTIONAL, +    uLForwardingUP-TNLInformation    UPTransportLayerInformation    OPTIONAL, +    iE-Extensions    ProtocolExtensionContainer {{DataForwardingResponseDRBItem-ExtIEs}}    OPTIONAL, +    ... +} + +``` +DataForwardingResponseDRBItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +DAPSRequestInfo ::= SEQUENCE { + dAPSIndicator ENUMERATED {daps-ho-required, ...}, + iE-Extensions ProtocolExtensionContainer { {DAPSRequestInfo-ExtIEs} } OPTIONAL, + ... +} + +DAPSRequestInfo-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +DAPSResponseInfoList ::= SEQUENCE (SIZE(1.. maxnoofDRBs)) OF DAPSResponseInfoItem + +DAPSResponseInfoItem ::= SEQUENCE { + dRB-ID DRB-ID, + dAPSResponseInfo DAPSResponseInfo, + iE-Extension ProtocolExtensionContainer { {DAPSResponseInfoItem-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +DAPSResponseInfoItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +DAPSResponseInfo ::= SEQUENCE { + dapsresponseindicator ENUMERATED {daps-ho-accepted, daps-ho-not-accepted, ...}, + iE-Extensions ProtocolExtensionContainer { { DAPSResponseInfo-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +DAPSResponseInfo-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +DataForwardingResponseERABList ::= SEQUENCE (SIZE(1..maxnoofE-RABs)) OF DataForwardingResponseERABListItem +``` + +``` +DataForwardingResponseERABListItem ::= SEQUENCE { + e-RAB-ID E-RAB-ID, + dLForwardingUP-TNLInformation UPTransportLayerInformation, + iE-Extensions ProtocolExtensionContainer { {DataForwardingResponseERABListItem-ExtIEs} } OPTIONAL, + ... +} +``` + +} + +DataForwardingResponseERABListItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +DelayCritical ::= ENUMERATED { + delay-critical, + non-delay-critical, + ... +} + +DL-CP-SecurityInformation ::= SEQUENCE { + dl-NAS-MAC DL-NAS-MAC, + iE-Extensions ProtocolExtensionContainer { { DL-CP-SecurityInformation-ExtIEs} } OPTIONAL, + ... +} + +DL-CP-SecurityInformation-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +DL-Signalling ::= ENUMERATED {true, ...} + +DL-NAS-MAC ::= BIT STRING (SIZE (16)) + +DLForwarding ::= ENUMERATED { +    dl-forwarding-proposed, +    ... +} + +DL-NGU-TNLInformationReused ::= ENUMERATED { +    true, +    ... +} + +DirectForwardingPathAvailability ::= ENUMERATED { +    direct-path-available, +    ... +} + +DRB-ID ::= INTEGER (1..32, ...) + +DRBsSubjectToStatusTransferList ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF DRBsSubjectToStatusTransferItem + +``` +DRBsSubjectToStatusTransferItem ::= SEQUENCE { + dRB-ID DRB-ID, + dRBStatusUL DRBStatusUL, + dRBStatusDL DRBStatusDL, + iE-Extension ProtocolExtensionContainer { {DRBsSubjectToStatusTransferItem-ExtIEs} } OPTIONAL, + ... +} + +DRBsSubjectToStatusTransferItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-OldAssociatedQosFlowList-ULendmarkerexpected CRITICALITY ignore EXTENSION AssociatedQosFlowList PRESENCE optional }, + ... +} + +DRBStatusDL ::= CHOICE { + dRBStatusDL12 DRBStatusDL12, + dRBStatusDL18 DRBStatusDL18, + choice-Extensions ProtocolIE-SingleContainer { {DRBStatusDL-ExtIEs} } +} + +DRBStatusDL-ExtIEs NGAP-PROTOCOL-IES ::= { + ... +} +``` + +``` +DRBStatusDL12 ::= SEQUENCE { + dL-COUNTValue COUNTValueForPDCP-SN12, + iE-Extension ProtocolExtensionContainer { {DRBStatusDL12-ExtIEs} } OPTIONAL, + ... +} + +DRBStatusDL12-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +DRBStatusDL18 ::= SEQUENCE { + dL-COUNTValue COUNTValueForPDCP-SN18, + iE-Extension ProtocolExtensionContainer { {DRBStatusDL18-ExtIEs} } OPTIONAL, + ... +} + +DRBStatusDL18-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +DRBStatusUL ::= CHOICE { + dRBStatusUL12 DRBStatusUL12, + dRBStatusUL18 DRBStatusUL18, +} +``` + +``` + choice-Extensions ProtocolIE-SingleContainer { {DRBStatusUL-ExtIEs} } + } + + DRBStatusUL-ExtIEs NGAP-PROTOCOL-IES ::= { + ... + } + + DRBStatusUL12 ::= SEQUENCE { + uL-COUNTValue COUNTValueForPDCP-SN12, + receiveStatusOfUL-PDCP-SDUs BIT STRING (SIZE(1..2048)) OPTIONAL, + iE-Extension ProtocolExtensionContainer { {DRBStatusUL12-ExtIEs} } OPTIONAL, + ... + } + + DRBStatusUL12-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... + } + + DRBStatusUL18 ::= SEQUENCE { + uL-COUNTValue COUNTValueForPDCP-SN18, + receiveStatusOfUL-PDCP-SDUs BIT STRING (SIZE(1..131072)) OPTIONAL, + iE-Extension ProtocolExtensionContainer { {DRBStatusUL18-ExtIEs} } OPTIONAL, + ... + } +``` + +} + +DRBStatusUL18-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + +... + +} + +DRBsToQosFlowsMappingList ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF DRBsToQosFlowsMappingItem + +DRBsToQosFlowsMappingItem ::= SEQUENCE { + +dRB-ID                                    DRB-ID, + +associatedQosFlowList                  AssociatedQosFlowList, + +iE-Extensions          ProtocolExtensionContainer { {DRBsToQosFlowsMappingItem-ExtIEs} }          OPTIONAL, + +... + +} + +DRBsToQosFlowsMappingItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + +{ ID id-DAPSRequestInfo CRITICALITY ignore EXTENSION DAPSRequestInfo PRESENCE optional }, + +... + +} + +Dynamic5QIDescriptor ::= SEQUENCE { + +priorityLevelQos                  PriorityLevelQos, + +packetDelayBudget                  PacketDelayBudget, + +``` + + packetErrorRate PacketErrorRate, + fiveQI FiveQI OPTIONAL, + delayCritical DelayCritical OPTIONAL, +-- The above IE shall be present in case of GBR QoS flow + averagingWindow AveragingWindow OPTIONAL, +-- The above IE shall be present in case of GBR QoS flow + maximumDataBurstVolume MaximumDataBurstVolume OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {Dynamic5QIDescriptor-ExtIEs} } OPTIONAL, + ... + } + + Dynamic5QIDescriptor-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-ExtendedPacketDelayBudget CRITICALITY ignore EXTENSION ExtendedPacketDelayBudget PRESENCE optional }| + { ID id-CNPacketDelayBudgetDL CRITICALITY ignore EXTENSION ExtendedPacketDelayBudget PRESENCE optional }| + { ID id-CNPacketDelayBudgetUL CRITICALITY ignore EXTENSION ExtendedPacketDelayBudget PRESENCE optional }, + ... + } + +-- E + +EarlyMeasurement ::= ENUMERATED {true, ...} + +EarlyStatusTransfer-TransparentContainer ::= SEQUENCE { + +``` + +``` +procedureStage ProcedureStageChoice, +iE-Extensions ProtocolExtensionContainer { {EarlyStatusTransfer-TransparentContainer-ExtIEs} } OPTIONAL, +... +} + +EarlyStatusTransfer-TransparentContainer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +ProcedureStageChoice ::= CHOICE { + first-dl-count FirstDLCount, + choice-Extensions ProtocolIE-SingleContainer { {ProcedureStageChoice-ExtIEs} } +} + +ProcedureStageChoice-ExtIEs NGAP-PROTOCOL-IES ::= { + { ID id-DLDiscarding CRITICALITY ignore TYPE DLDiscarding PRESENCE optional }, + ... +} + +DLDiscarding ::= SEQUENCE { + dRBsSubjectToDLDiscarding DRBsSubjectToDLDiscarding-List, + iE-Extension ProtocolExtensionContainer { {DLDiscarding-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +} +``` + +``` +DLDiscarding-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +DRBsSubjectToDLDiscarding-List ::= SEQUENCE (SIZE (1..maxnoofDRBs)) OF DRBsSubjectToDLDiscarding-Item +``` + +``` +DRBsSubjectToDLDiscarding-Item ::= SEQUENCE { +``` + +``` + drbID DRB-ID, +``` + +``` + dlCount DLCountChoice, +``` + +``` + iE-Extension ProtocolExtensionContainer { { DRBsSubjectToDLDiscarding-Item-ExtIEs} } OPTIONAL, +``` + +``` + ... +``` + +``` +} +``` + +``` +DRBsSubjectToDLDiscarding-Item-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +DLCountChoice ::= CHOICE { +``` + +``` + count12bits COUNT-PDCP-SN12, +``` + +``` + count18bits COUNT-PDCP-SN18, +``` + +``` + choice-extension ProtocolIE-SingleContainer { {DLCountChoice-ExtIEs} } +``` + +} + +DLCountChoice-ExtIEs NGAP-PROTOCOL-IES ::= { + +... + +} + +COUNT-PDCP-SN12 ::= SEQUENCE { + +pdcp-SN12 INTEGER (0..4095), + +hfn-PDCP-SN12 INTEGER (0..1048575), + +iE-Extensions ProtocolExtensionContainer { {COUNT-PDCP-SN12-ExtIEs} } OPTIONAL, + +... + +} + +COUNT-PDCP-SN12-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + +... + +} + +COUNT-PDCP-SN18 ::= SEQUENCE { + +pdcp-SN18 INTEGER (0..262143), + +hfn-PDCP-SN18 INTEGER (0..16383), + +iE-Extensions ProtocolExtensionContainer { {COUNT-PDCP-SN18-ExtIEs} } OPTIONAL, + +``` + ... +} + +COUNT-PDCP-SN18-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +FirstDLCount ::= SEQUENCE { + dRBsSubjectToEarlyStatusTransfer dRBsSubjectToEarlyStatusTransfer-List, + iE-Extension ProtocolExtensionContainer { {FirstDLCount-ExtIEs} } OPTIONAL, + ... +} + +FirstDLCount-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +dRBsSubjectToEarlyStatusTransfer-List ::= SEQUENCE (SIZE (1.. maxnoofDRBs)) OF dRBsSubjectToEarlyStatusTransfer-Item + +dRBsSubjectToEarlyStatusTransfer-Item ::= SEQUENCE { + dRB-ID DRB-ID, + firstDLCOUNT DRBStatusDL, + iE-Extension ProtocolExtensionContainer { { dRBsSubjectToEarlyStatusTransfer-Item-ExtIEs} } OPTIONAL, +``` + +``` + ... +} + +DRBsSubjectToEarlyStatusTransfer-Item-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +ECNMarkingorCongestionInformationReportingRequest ::= CHOICE { + eCNMarkingRequest ECNMarkingRequest, + congestionMonitoringRequest CongestionMonitoringRequest, + choice-Extensions ProtocolIE-SingleContainer { {ECNMarkingorCongestionInformationReportingRequest-ExtIEs} } +} + +ECNMarkingorCongestionInformationReportingRequest-ExtIEs NGAP-PROTOCOL-IES ::= { + ... +} + +ECNMarkingRequest ::= ENUMERATED {ul, dl, both, stop, ...} + +CongestionMonitoringRequest ::= ENUMERATED {ul, dl, both, stop, ...} +``` + +``` +ECNMarkingorCongestionInformationReportingStatus ::= SEQUENCE (SIZE (1..maxnoofQosFlows)) OF ECNMarkingorCongestionInformationReportingStatus-Item +``` + +``` +ECNMarkingorCongestionInformationReportingStatus-Item ::= SEQUENCE { + qosFlowIdentifier QosFlowIdentifier, + activationStatus ActivationStatus, + iE-Extension ProtocolExtensionContainer { ECNMarkingorCongestionInformationReportingStatus-Item-ExtIEs } OPTIONAL, + ... +} +``` + +``` +ECNMarkingorCongestionInformationReportingStatus-Item-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +ActivationStatus ::= ENUMERATED { + active, + not-active, + ... +} +``` + +``` +EDT-Session ::= ENUMERATED { + true, + ... +} +``` + +EmergencyAreaID ::= OCTET STRING (SIZE(3)) + +EmergencyAreaIDBroadcastEUTRA ::= SEQUENCE (SIZE(1..maxnoofEmergencyAreaID)) OF EmergencyAreaIDBroadcastEUTRA-Item + +EmergencyAreaIDBroadcastEUTRA-Item ::= SEQUENCE { +    emergencyAreaID                  EmergencyAreaID, +    completedCellsInEAI-EUTRA      CompletedCellsInEAI-EUTRA, +    iE-Extensions                  ProtocolExtensionContainer { {EmergencyAreaIDBroadcastEUTRA-Item-ExtIEs} } OPTIONAL, +    ... +} + +EmergencyAreaIDBroadcastEUTRA-Item-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +    ... +} + +EmergencyAreaIDBroadcastNR ::= SEQUENCE (SIZE(1..maxnoofEmergencyAreaID)) OF EmergencyAreaIDBroadcastNR-Item + +EmergencyAreaIDBroadcastNR-Item ::= SEQUENCE { +    emergencyAreaID                  EmergencyAreaID, +    completedCellsInEAI-NR         CompletedCellsInEAI-NR, +    iE-Extensions                  ProtocolExtensionContainer { {EmergencyAreaIDBroadcastNR-Item-ExtIEs} } OPTIONAL, +    ... +} + +``` +} + +EmergencyAreaIDBroadcastNR-Item-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +EmergencyAreaIDCancelledEUTRA ::= SEQUENCE (SIZE(1..maxnoofEmergencyAreaID)) OF EmergencyAreaIDCancelledEUTRA-Item + +EmergencyAreaIDCancelledEUTRA-Item ::= SEQUENCE { + emergencyAreaID EmergencyAreaID, + cancelledCellsInEAI-EUTRA CancelledCellsInEAI-EUTRA, + iE-Extensions ProtocolExtensionContainer { {EmergencyAreaIDCancelledEUTRA-Item-ExtIEs} } OPTIONAL, + ... +} + +EmergencyAreaIDCancelledEUTRA-Item-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +EmergencyAreaIDCancelledNR ::= SEQUENCE (SIZE(1..maxnoofEmergencyAreaID)) OF EmergencyAreaIDCancelledNR-Item + +EmergencyAreaIDCancelledNR-Item ::= SEQUENCE { + emergencyAreaID EmergencyAreaID, +``` + +``` + cancelledCellsInEAI-NR CancelledCellsInEAI-NR, + iE-Extensions ProtocolExtensionContainer { {EmergencyAreaIDCancelledNR-Item-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +EmergencyAreaIDCancelledNR-Item-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +EmergencyAreaIDList ::= SEQUENCE (SIZE(1..maxnoofEmergencyAreaID)) OF EmergencyAreaID +``` + +``` +EmergencyAreaIDListForRestart ::= SEQUENCE (SIZE(1..maxnoofEAIforRestart)) OF EmergencyAreaID +``` + +``` +EmergencyFallbackIndicator ::= SEQUENCE { + emergencyFallbackRequestIndicator EmergencyFallbackRequestIndicator, + emergencyServiceTargetCN EmergencyServiceTargetCN OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {EmergencyFallbackIndicator-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +EmergencyFallbackIndicator-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +EmergencyFallbackRequestIndicator ::= ENUMERATED { +``` + +``` + emergency-fallback-requested, +``` + +``` + ... +``` + +``` +} +``` + +``` +EmergencyServiceTargetCN ::= ENUMERATED { +``` + +``` + fiveGC, +``` + +``` + epc, +``` + +``` + ... +``` + +``` +} +``` + +``` +ENB-ID ::= CHOICE { +``` + +``` + macroENB-ID BIT STRING (SIZE(20)), +``` + +``` + homeENB-ID BIT STRING (SIZE(28)), +``` + +``` + short-macroENB-ID BIT STRING (SIZE(18)), +``` + +``` + long-macroENB-ID BIT STRING (SIZE(21)), +``` + +``` + choice-Extensions ProtocolIE-SingleContainer { { ENB-ID-ExtIEs } } +``` + +``` +} +``` + +``` +ENB-ID-ExtIEs NGAP-PROTOCOL-IES ::= { +``` + +``` + ... +``` + +``` +} +``` + +Enhanced-CoverageRestriction ::= ENUMERATED {restricted, ... } + +Extended-ConnectedTime ::= INTEGER (0..255) + +EN-DCSONConfigurationTransfer ::= OCTET STRING + +EndpointIPAddressAndPort ::=SEQUENCE { +    endpointIPAddress TransportLayerAddress, +    portNumber          PortNumber, +    iE-Extensions     ProtocolExtensionContainer { { EndpointIPAddressAndPort-ExtIEs} } OPTIONAL +} + +EndIndication ::= ENUMERATED { +    no-further-data, +    further-data-exists, +    ... +} + +EndpointIPAddressAndPort-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +    ... +} + +} + +EquivalentPLMNs ::= SEQUENCE (SIZE(1..maxnoofEPLMNs)) OF PLMNIdentity + +EPS-TAC ::= OCTET STRING (SIZE(2)) + +EPS-TAI ::= SEQUENCE { +    pLMNIdentity    PLMNIdentity, +    ePS-TAC        EPS-TAC, +    iE-Extensions  ProtocolExtensionContainer { {EPS-TAI-ExtIEs} } OPTIONAL, +    ... +} + +EPS-TAI-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +    ... +} + +E-RAB-ID ::= INTEGER (0..15, ...) + +E-RABInformationList ::= SEQUENCE (SIZE(1..maxnoofE-RABs)) OF E-RABInformationItem + +E-RABInformationItem ::= SEQUENCE { +    e-RAB-ID        E-RAB-ID, + +``` + dLForwarding DLForwarding OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {E-RABInformationItem-ExtIEs} } OPTIONAL, + ... +} + +E-RABInformationItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + {ID id-SourceTNLAddrInfo CRITICALITY ignore EXTENSION TransportLayerAddress PRESENCE optional}| + {ID id-SourceNodeTNLAddrInfo CRITICALITY ignore EXTENSION TransportLayerAddress PRESENCE optional}, + ... +} + +EUTRACellIdentity ::= BIT STRING (SIZE(28)) + +EUTRA-CGI ::= SEQUENCE { + pLMNIdentity PLMNIdentity, + eUTRACellIdentity EUTRACellIdentity, + iE-Extensions ProtocolExtensionContainer { {EUTRA-CGI-ExtIEs} } OPTIONAL, + ... +} + +EUTRA-CGI-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +EUTRA-CGIList ::= SEQUENCE (SIZE(1..maxnoofCellsinngeNB)) OF EUTRA-CGI + +EUTRA-CGIListForWarning ::= SEQUENCE (SIZE(1..maxnoofCellIDforWarning)) OF EUTRA-CGI + +EUTRA-PagingeDRXInformation ::= SEQUENCE { + eUTRA-paging-eDRX-Cycle EUTRA-Paging-eDRX-Cycle, + eUTRA-paging-Time-Window EUTRA-Paging-Time-Window OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {EUTRA-PagingeDRXInformation-ExtIEs} } OPTIONAL, + ... +} + +EUTRA-PagingeDRXInformation-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +EUTRA-Paging-eDRX-Cycle ::= ENUMERATED { + hfhalf, hf1, hf2, hf4, hf6, + hf8, hf10, hf12, hf14, hf16, + hf32, hf64, hf128, hf256, + ... +} +``` + +EUTRA-Paging-Time-Window ::= ENUMERATED { + +s1, s2, s3, s4, s5, + +s6, s7, s8, s9, s10, + +s11, s12, s13, s14, s15, s16, + +... + +} + +EUTRAencryptionAlgorithms ::= BIT STRING (SIZE(16, ...)) + +EUTRAintegrityProtectionAlgorithms ::= BIT STRING (SIZE(16, ...)) + +EventType ::= ENUMERATED { + +direct, + +change-of-serve-cell, + +ue-presence-in-area-of-interest, + +stop-change-of-serve-cell, + +stop-ue-presence-in-area-of-interest, + +cancel-location-reporting-for-the-ue, + +... + +change-of-serving-cell-and-UE-presence-in-the-Area-of-Interest + +} + +ExcessPacketDelayThresholdConfiguration ::= SEQUENCE (SIZE(1..maxnoofThresholdsForExcessPacketDelay)) OF ExcessPacketDelayThresholdItem + +``` +ExcessPacketDelayThresholdItem ::= SEQUENCE { + fiveQi FiveQI, + excessPacketDelayThresholdValue ExcessPacketDelayThresholdValue, + iE-Extensions ProtocolExtensionContainer { { ExcessPacketDelayThresholdItem-ExtIEs} } OPTIONAL, + ... +} + +ExcessPacketDelayThresholdItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +ExcessPacketDelayThresholdValue ::= ENUMERATED { + ms0dot25, ms0dot5, ms1, ms2, ms4, ms5, ms10, ms20, ms30, ms40, ms50, ms60, ms70, ms80, ms90, ms100, ms150, ms300, ms500, + ... +} + +ExpectedActivityPeriod ::= INTEGER (1..30|40|50|60|80|100|120|150|180|181, ...) + +ExpectedHOInterval ::= ENUMERATED { + sec15, sec30, sec60, sec90, sec120, sec180, long-time, + ... +} +``` + +ExpectedIdlePeriod ::= INTEGER (1..30|40|50|60|80|100|120|150|180|181, ...) + +ExpectedUEActivityBehaviour ::= SEQUENCE { +    expectedActivityPeriod                    ExpectedActivityPeriod                    OPTIONAL, +    expectedIdlePeriod                        ExpectedIdlePeriod                        OPTIONAL, +    sourceOfUEActivityBehaviourInformation    SourceOfUEActivityBehaviourInformation    OPTIONAL, +    iE-Extensions            ProtocolExtensionContainer { {ExpectedUEActivityBehaviour-ExtIEs} } OPTIONAL, +    ... +} + +ExpectedUEActivityBehaviour-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +    ... +} + +ExpectedUEBehaviour ::= SEQUENCE { +    expectedUEActivityBehaviour    ExpectedUEActivityBehaviour                    OPTIONAL, +    expectedHOInterval            ExpectedHOInterval                                OPTIONAL, +    expectedUEMobility            ExpectedUEMobility                                OPTIONAL, +    expectedUEMovingTrajectory    ExpectedUEMovingTrajectory                    OPTIONAL, +    iE-Extensions            ProtocolExtensionContainer { {ExpectedUEBehaviour-ExtIEs} } OPTIONAL, +    ... +} + +``` +ExpectedUEBehaviour-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +ExpectedUEMobility ::= ENUMERATED { + stationary, + mobile, + ... +} +``` + +``` +ExpectedUEMovingTrajectory ::= SEQUENCE (SIZE(1..maxnoofCellsUEMovingTrajectory)) OF ExpectedUEMovingTrajectoryItem +``` + +``` +ExpectedUEMovingTrajectoryItem ::= SEQUENCE { + nGRAN-CGI NGRAN-CGI, + timeStayedInCell INTEGER (0..4095) OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {ExpectedUEMovingTrajectoryItem-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +ExpectedUEMovingTrajectoryItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +Extended-AMFName ::= SEQUENCE { + aMFNameVisibleString AMFNameVisibleString OPTIONAL, + aMFNameUTF8String AMFNameUTF8String OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Extended-AMFName-ExtIEs } } OPTIONAL, + ... +} + +Extended-AMFName-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +ExtendedPacketDelayBudget ::= INTEGER (1..65535, ..., 65536..109999) + +Extended-RANNodeName ::= SEQUENCE { + rANNodeNameVisibleString RANNodeNameVisibleString OPTIONAL, + rANNodeNameUTF8String RANNodeNameUTF8String OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Extended-RANNodeName-ExtIEs } } OPTIONAL, ... +} + +Extended-RANNodeName-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +} + +``` +ExtendedRATRestrictionInformation ::= SEQUENCE { + primaryRATRestriction BIT STRING (SIZE(8, ...)), + secondaryRATRestriction BIT STRING (SIZE(8, ...)), + iE-Extensions ProtocolExtensionContainer { {ExtendedRATRestrictionInformation-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +ExtendedRATRestrictionInformation-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +ExtendedRNC-ID ::= INTEGER (4096..65535) +``` + +``` +ExtendedSliceSupportList ::= SEQUENCE (SIZE(1..maxnoofExtSliceItems)) OF SliceSupportItem +``` + +``` +ExtendedUEIdentityIndexValue ::= BIT STRING (SIZE(16)) +``` + +``` +EventTrigger ::= CHOICE { + outOfCoverage ENUMERATED {true, ...}, + eventL1LoggedMDTConfig EventL1LoggedMDTConfig, + choice-Extensions ProtocolIE-SingleContainer { { EventTrigger-ExtIEs} } +``` + +``` +} +``` + +``` +EventTrigger-ExtIEs NGAP-PROTOCOL-IES ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +EventL1LoggedMDTConfig ::= SEQUENCE { +``` + +``` + l1Threshold MeasurementThresholdL1LoggedMDT, +``` + +``` + hysteresis Hysteresis, +``` + +``` + timeToTrigger TimeToTrigger, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { EventL1LoggedMDTConfig-ExtIEs} } OPTIONAL, +``` + +``` + ... +``` + +``` +} +``` + +``` +EventL1LoggedMDTConfig-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +MeasurementThresholdL1LoggedMDT ::= CHOICE { +``` + +``` + threshold-RSRP Threshold-RSRP, +``` + +``` + threshold-RSRQ Threshold-RSRQ, +``` + +``` + choice-Extensions ProtocolIE-SingleContainer { { MeasurementThresholdL1LoggedMDT-ExtIEs} } +``` + +``` +} +``` + +``` +MeasurementThresholdL1LoggedMDT-ExtIEs NGAP-PROTOCOL-IES ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +EquivalentSNPNsList ::= SEQUENCE (SIZE(1..maxnoofESPNs)) OF EquivalentSNPNsItem +``` + +``` +EquivalentSNPNsItem ::= SEQUENCE { +``` + +``` + plmnIdentity PLMNIdentity, +``` + +``` + nID NID, +``` + +``` + iE-Extensions ProtocolExtensionContainer { {EquivalentSNPNsItem-ExtIEs} } OPTIONAL, +``` + +``` + ... +``` + +``` +} +``` + +``` +EquivalentSNPNsItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +-- F +``` + +``` +FailureIndication ::= SEQUENCE { +``` + +``` + uERLFReportContainer UERLFReportContainer, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { FailureIndication-ExtIEs} } OPTIONAL, +``` + +``` + ... +} + +FailureIndication-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +FiveGCAction ::= CHOICE { + hLComActivate HLComActivate, + hLComDeactivate HLComDeactivate, + choice-Extensions ProtocolIE-SingleContainer { {FiveGCAction-ExtIEs} } +} + +FiveGCAction-ExtIEs NGAP-PROTOCOL-IES ::= { + ... +} + +FiveG-ProSeAuthorized ::= SEQUENCE { + fiveGProSeDirectDiscovery FiveGProSeDirectDiscovery OPTIONAL, + fiveGProSeDirectCommunication FiveGProSeDirectCommunication OPTIONAL, + fiveGProSeLayer2UEtoNetworkRelay FiveGProSeLayer2UEtoNetworkRelay OPTIONAL, + fiveGProSeLayer3UEtoNetworkRelay FiveGProSeLayer3UEtoNetworkRelay OPTIONAL, + fiveGProSeLayer2RemoteUE FiveGProSeLayer2RemoteUE OPTIONAL, +``` + +``` + iE-Extensions ProtocolExtensionContainer { {FiveG-ProSeAuthorized-ExtIEs} } OPTIONAL, + ... +} + +FiveG-ProSeAuthorized-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-FiveGProSeLayer2Multipath CRITICALITY ignore EXTENSION FiveGProSeLayer2Multipath PRESENCE optional }| + { ID id-FiveGProSeLayer2UEtoUERelay CRITICALITY ignore EXTENSION FiveGProSeLayer2UEtoUERelay PRESENCE optional }| + { ID id-FiveGProSeLayer2UEtoUERemote CRITICALITY ignore EXTENSION FiveGProSeLayer2UEtoUERemote PRESENCE optional }, + ... +} + +FiveGProSeDirectDiscovery ::= ENUMERATED { + authorized, + not-authorized, + ... +} + +FiveGProSeDirectCommunication ::= ENUMERATED { + authorized, + not-authorized, + ... +} +``` + +``` +FiveGProSeLayer2UEtoNetworkRelay ::= ENUMERATED { + authorized, + not-authorized, + ... +} +``` + +``` +FiveGProSeLayer3UEtoNetworkRelay ::= ENUMERATED { + authorized, + not-authorized, + ... +} +``` + +``` +FiveGProSeLayer2RemoteUE ::= ENUMERATED { + authorized, + not-authorized, + ... +} +``` + +``` +FiveGProSeLayer2Multipart ::= ENUMERATED { + authorized, + not-authorized, + ... +} +``` + +``` +FiveGProSeLayer2UEtoUERelay ::= ENUMERATED { + authorized, + not-authorized, + ... +} + +FiveGProSeLayer2UEtoUERemote ::= ENUMERATED { + authorized, + not-authorized, + ... +} + +FiveG-ProSePC5QoSParameters ::= SEQUENCE { + fiveGProSePC5QoSFlowList FiveGProSePC5QoSFlowList, + fiveGProSePC5LinkAggregateBitRates BitRate OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { FiveG-ProSePC5QoSParameters-ExtIEs} } OPTIONAL, + ... +} + +FiveG-ProSePC5QoSParameters-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +FiveGProSePC5QoSFlowList ::= SEQUENCE (SIZE(1..maxnoofPC5QoSFlows)) OF FiveGProSePC5QoSFlowItem + +FiveGProSePC5QoSFlowItem ::= SEQUENCE { + fiveGproSepQI FiveQI, + fiveGproSepc5FlowBitRates FiveGProSePC5FlowBitRates OPTIONAL, + fiveGproSerange Range OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { FiveGProSePC5QoSFlowItem-ExtIEs} } OPTIONAL, + ... +} + +FiveGProSePC5QoSFlowItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +FiveGProSePC5FlowBitRates ::= SEQUENCE { + fiveGproSeguardedFlowBitRate BitRate, + fiveGproSemaximumFlowBitRate BitRate, + iE-Extensions ProtocolExtensionContainer { { FiveGProSePC5FlowBitRates-ExtIEs} } OPTIONAL, + ... +} + +FiveGProSePC5FlowBitRates-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +} + +FiveG-S-TMSI ::= SEQUENCE { + aMFSetID AMFSetID, + aMFPointer AMFPointer, + fiveG-TMSI FiveG-TMSI, + iE-Extensions ProtocolExtensionContainer { {FiveG-S-TMSI-ExtIEs} } OPTIONAL, + ... +} + +FiveG-S-TMSI-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +FiveG-TMSI ::= OCTET STRING (SIZE(4)) + +FiveQI ::= INTEGER (0..255, ...) + +ForbiddenAreaInformation ::= SEQUENCE (SIZE(1.. maxnoofEPLMNsPlusOne)) OF ForbiddenAreaInformation-Item + +ForbiddenAreaInformation-Item ::= SEQUENCE { +``` + +``` + pLMNIdentity PLMNIdentity, + forbiddenTACs ForbiddenTACs, + iE-Extensions ProtocolExtensionContainer { {ForbiddenAreaInformation-Item-ExtIEs} } OPTIONAL, + ... +} + +ForbiddenAreaInformation-Item-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +ForbiddenTACs ::= SEQUENCE (SIZE(1..maxnoofForbTACs)) OF TAC + +FromEUTRANToNGRAN ::= SEQUENCE { + sourceeNBID IntersystemSONeNBID, + targetNGRANnodeID IntersystemSONNGRANnodeID, + iE-Extensions ProtocolExtensionContainer { { FromEUTRANToNGRAN-ExtIEs} } OPTIONAL +} + +FromEUTRANToNGRAN-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +FromNGRANToEUTRAN ::= SEQUENCE { +``` + +``` +sourceNGRANnodeID IntersystemSONNGRANnodeID, +targeteNBID IntersystemSONeNBID, +iE-Extensions ProtocolExtensionContainer { { FromNGRANtoEUTRAN-ExtIEs } } OPTIONAL +} +``` + +``` +FromNGRANtoEUTRAN-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +-- G + +``` +GBR-QosInformation ::= SEQUENCE { + maximumFlowBitRateDL BitRate, + maximumFlowBitRateUL BitRate, + guaranteedFlowBitRateDL BitRate, + guaranteedFlowBitRateUL BitRate, + notificationControl NotificationControl OPTIONAL, + maximumPacketLossRateDL PacketLossRate OPTIONAL, + maximumPacketLossRateUL PacketLossRate OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { GBR-QosInformation-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +GBR-QosInformation-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-AlternativeQoSParaSetList CRITICALITY ignore EXTENSION AlternativeQoSParaSetList PRESENCE optional }, + ... +} +``` + +``` +GlobalCable-ID ::= OCTET STRING +``` + +``` +GlobalCable-ID-new ::= SEQUENCE { + globalCable-ID GlobalCable-ID, + tAI TAI, + iE-Extensions ProtocolExtensionContainer { { GlobalCable-ID-new-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +GlobalCable-ID-new-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +GlobalENB-ID ::= SEQUENCE { + pLMNIdentity PLMNIdentity, + eNB-ID ENB-ID, + iE-Extensions ProtocolExtensionContainer { {GlobalENB-ID-ExtIEs} } OPTIONAL, + ... +} +``` + +} + +GlobalENB-ID-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + +... + +} + +GlobalGNB-ID ::= SEQUENCE { + +    pLMNIdentity    PLMNIdentity, + +    gNB-ID        GNB-ID, + +    iE-Extensions    ProtocolExtensionContainer { {GlobalGNB-ID-ExtIEs} } OPTIONAL, + +    ... + +} + +GlobalGNB-ID-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + +... + +} + +GlobalN3IWF-ID ::= SEQUENCE { + +    pLMNIdentity    PLMNIdentity, + +    n3IWF-ID        N3IWF-ID, + +    iE-Extensions    ProtocolExtensionContainer { {GlobalN3IWF-ID-ExtIEs} } OPTIONAL, + +    ... + +} + +GlobalN3IWF-ID-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + +... + +} + +GlobalLine-ID ::= SEQUENCE { + +globalLineIdentity GlobalLineIdentity, + +lineType LineType + +OPTIONAL, + +iE-Extensions ProtocolExtensionContainer { {GlobalLine-ID-ExtIEs} } + +OPTIONAL, + +... + +} + +GlobalLine-ID-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + +{ ID id-TAI + +CRITICALITY ignore + +EXTENSION TAI + +PRESENCE optional }, + +... + +} + +GlobalLineIdentity ::= OCTET STRING + +GlobalNgENB-ID ::= SEQUENCE { + +pLMNIdentity PLMNIdentity, + +ngENB-ID NgENB-ID, + +``` + iE-Extensions ProtocolExtensionContainer { {GlobalNgENB-ID-ExtIEs} } OPTIONAL, + ... +} + +GlobalNgENB-ID-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +GlobalRANNodeID ::= CHOICE { + globalGNB-ID GlobalGNB-ID, + globalNgENB-ID GlobalNgENB-ID, + globalN3IWF-ID GlobalN3IWF-ID, + choice-Extensions ProtocolIE-SingleContainer { {GlobalRANNodeID-ExtIEs} } +} + +GlobalRANNodeID-ExtIEs NGAP-PROTOCOL-IES ::= { + { ID id-GlobalTNGF-ID CRITICALITY reject TYPE GlobalTNGF-ID PRESENCE mandatory }| + { ID id-GlobalTWIF-ID CRITICALITY reject TYPE GlobalTWIF-ID PRESENCE mandatory }| + { ID id-GlobalW-AGF-ID CRITICALITY reject TYPE GlobalW-AGF-ID PRESENCE mandatory }, + ... +} + +GlobalTNGF-ID ::= SEQUENCE { +``` + +``` + pLMNIdentity PLMNIdentity, + tNGF-ID TNGF-ID, + iE-Extensions ProtocolExtensionContainer { { GlobalTNGF-ID-ExtIEs } } OPTIONAL, + ... +} + +GlobalTNGF-ID-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +GlobalTWIF-ID ::= SEQUENCE { + pLMNIdentity PLMNIdentity, + tWIF-ID TWIF-ID, + iE-Extensions ProtocolExtensionContainer { { GlobalTWIF-ID-ExtIEs } } OPTIONAL, + ... +} + +GlobalTWIF-ID-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +GlobalW-AGF-ID ::= SEQUENCE { + pLMNIdentity PLMNIdentity, + w-AGF-ID W-AGF-ID, + iE-Extensions ProtocolExtensionContainer { { GlobalW-AGF-ID-ExtIEs } } OPTIONAL, + ... +} + +GlobalW-AGF-ID-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +GNB-ID ::= CHOICE { + gNB-ID BIT STRING (SIZE(22..32)), + choice-Extensions ProtocolIE-SingleContainer { {GNB-ID-ExtIEs} } +} + +GNB-ID-ExtIEs NGAP-PROTOCOL-IES ::= { + ... +} + +GTP-TEID ::= OCTET STRING (SIZE(4)) + +GTPTunnel ::= SEQUENCE { +``` + +``` + transportLayerAddress TransportLayerAddress, + gTP-TEID GTP-TEID, + iE-Extensions ProtocolExtensionContainer { {GTP Tunnel-ExtIEs} } OPTIONAL, + ... +} + +GTP Tunnel-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +GUAMI ::= SEQUENCE { + pLMNIdentity PLMNIdentity, + aMFRegionID AMFRegionID, + aMFSetID AMFSetID, + aMFPointer AMFPointer, + iE-Extensions ProtocolExtensionContainer { {GUAMI-ExtIEs} } OPTIONAL, + ... +} + +GUAMI-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +GUAMIType ::= ENUMERATED {native, mapped, ...} + +-- H + +HandoverCommandTransfer ::= SEQUENCE { +     dLForwardingUP-TNLInformation      UPTransportLayerInformation                      OPTIONAL, +     qosFlowToBeForwardedList            QosFlowToBeForwardedList                            OPTIONAL, +     dataForwardingResponseDRBList      DataForwardingResponseDRBList                      OPTIONAL, +     iE-Extensions                      ProtocolExtensionContainer { {HandoverCommandTransfer-ExtIEs} } OPTIONAL, +     ... +} + +HandoverCommandTransfer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +     { ID id-AdditionalDLForwardingUPTNLInformation      CRITICALITY ignore    EXTENSION QosFlowPerTNLInformationList      PRESENCE optional    }| +     { ID id-ULForwardingUP-TNLInformation                CRITICALITY reject    EXTENSION UPTransportLayerInformation            PRESENCE optional    }| +     { ID id-AdditionalULForwardingUPTNLInformation      CRITICALITY reject    EXTENSION UPTransportLayerInformationList      PRESENCE optional    }| +     { ID id-DataForwardingResponseERABList                CRITICALITY ignore    EXTENSION DataForwardingResponseERABList        PRESENCE optional    }| +     { ID id-QosFlowFailedToSetupList                      CRITICALITY ignore    EXTENSION QosFlowListWithCause                  PRESENCE optional    }, +     ... +} + +HandoverFlag ::= ENUMERATED { +     handover-preparation, + +``` + ... +} + +HandoverPreparationUnsuccessfulTransfer ::= SEQUENCE { + cause Cause, + iE-Extensions ProtocolExtensionContainer { {HandoverPreparationUnsuccessfulTransfer-ExtIEs} } OPTIONAL, + ... +} + +HandoverPreparationUnsuccessfulTransfer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +HandoverRequestAcknowledgeTransfer ::= SEQUENCE { + dL-NGU-UP-TNLInformation UPTransportLayerInformation, + dLForwardingUP-TNLInformation UPTransportLayerInformation OPTIONAL, + securityResult SecurityResult OPTIONAL, + qosFlowSetupResponseList QosFlowListWithDataForwarding, + qosFlowFailedToSetupList QosFlowListWithCause OPTIONAL, + dataForwardingResponseDRBList DataForwardingResponseDRBList OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {HandoverRequestAcknowledgeTransfer-ExtIEs} } OPTIONAL, + ... +} +``` + +``` + +HandoverRequestAcknowledgeTransfer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-AdditionalDLUPTNLInformationForHOList CRITICALITY ignore EXTENSION AdditionalDLUPTNLInformationForHOList PRESENCE optional }| + { ID id-ULForwardingUP-TNLInformation CRITICALITY reject EXTENSION UPTransportLayerInformation PRESENCE optional }| + { ID id-AdditionalULForwardingUPTNLInformation CRITICALITY reject EXTENSION UPTransportLayerInformationList PRESENCE optional }| + { ID id-DataForwardingResponseERABList CRITICALITY ignore EXTENSION DataForwardingResponseERABList PRESENCE optional }| + { ID id-RedundantDL-NGU-UP-TNLInformation CRITICALITY ignore EXTENSION UPTransportLayerInformation PRESENCE optional }| + { ID id-UsedRSNInformation CRITICALITY ignore EXTENSION RedundantPDUSessionInformation PRESENCE optional }| + { ID id-GlobalRANNodeID CRITICALITY ignore EXTENSION GlobalRANNodeID PRESENCE optional }| + { ID id-MBS-SupportIndicator CRITICALITY ignore EXTENSION MBS-SupportIndicator PRESENCE optional }| + { ID id-PDUSetbasedHandlingIndicator CRITICALITY ignore EXTENSION PDUSetbasedHandlingIndicator PRESENCE optional }, + ... +} + +``` + +``` + +HandoverRequiredTransfer ::= SEQUENCE { + directForwardingPathAvailability DirectForwardingPathAvailability OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {HandoverRequiredTransfer-ExtIEs} } OPTIONAL, + ... +} + +``` + +``` + +HandoverRequiredTransfer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +``` +HandoverResourceAllocationUnsuccessfulTransfer ::= SEQUENCE { + cause Cause, + criticalityDiagnostics CriticalityDiagnostics OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {HandoverResourceAllocationUnsuccessfulTransfer-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +HandoverResourceAllocationUnsuccessfulTransfer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +HandoverType ::= ENUMERATED { + intra5gs, + fivegs-to-eps, + eps-to-5gs, + ..., + fivegs-to-utran +} +``` + +``` +HashedUEIdentityIndexValue ::= BIT STRING (SIZE(13, ...)) +``` + +HFCNode-ID ::= OCTET STRING + +HFCNode-ID-new ::= SEQUENCE { +    hFCNode-ID          HFCNode-ID, +    tAI                 TAI, +    iE-Extensions     ProtocolExtensionContainer { { HFCNode-ID-new-ExtIEs} } OPTIONAL, +    ... +} + +HFCNode-ID-new-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +    { ID id-GlobalCable-ID          CRITICALITY ignore  EXTENSION GlobalCable-ID          PRESENCE optional  }, +    ... +} + +HLComActivate ::= SEQUENCE { +    nR-Paging-Long-eDRX-Information-for-RRC-INACTIVE    NR-Paging-Long-eDRX-Information-for-RRC-INACTIVE, +    iE-Extensions                                          ProtocolExtensionContainer { { HLComActivate-ExtIEs} } OPTIONAL, +    ... +} + +HLComActivate-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +    ... +} + +``` +HLComDeactivate ::= SEQUENCE { + uEReachabilityIndication ENUMERATED {true, ...}, + iE-Extensions ProtocolExtensionContainer { { HLComDeactivate-ExtIEs} } OPTIONAL, + ... +} + +HLComDeactivate-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +HOReport ::= SEQUENCE { + handoverReportType ENUMERATED {ho-too-early, ho-to-wrong-cell, intersystem-ping-pong, ...}, + handoverCause Cause, + sourcecellCGI NGRAN-CGI, + targetcellCGI NGRAN-CGI, + reestablishmentcellCGI NGRAN-CGI OPTIONAL, + -- The above IE shall be present if the Handover Report Type IE is set to the value "HO to wrong cell" -- + sourcecellC-RNTI BIT STRING (SIZE(16)) OPTIONAL, + targetcellinE-UTRAN EUTRA-CGI OPTIONAL, + -- The above IE shall be present if the Handover Report Type IE is set to the value "Inter System ping-pong" -- + mobilityInformation MobilityInformation OPTIONAL, + uERLFRportContainer UERLFRportContainer OPTIONAL, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { HOReport-ExtIEs} } OPTIONAL, + ... +} + +HOReport-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-ExtendedMobilityInformation CRITICALITY ignore EXTENSION ExtendedMobilityInformation PRESENCE optional }| + { ID id-TargetCellCRNTI CRITICALITY ignore EXTENSION C-RNTI PRESENCE optional }| + { ID id-TimeSinceFailure CRITICALITY ignore EXTENSION TimeSinceFailure PRESENCE optional }, + ... +} + +Hysteresis ::= INTEGER (0..30) + +-- I + +IAB-Authorized ::= ENUMERATED { + authorized, + not-authorized, + ... +} + +IAB-MTUserLocationInformation ::= SEQUENCE { +``` + +``` + nRCGI NR-CGI, + tAI TAI OPTIONAL, + iE-Extensions ProtocolExtensionContainer { IAB-MTUserLocationInformation-ExtIEs } OPTIONAL, + ... +} + +IAB-MTUserLocationInformation-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +IAB-Supported ::= ENUMERATED { + true, + ... +} + +IABNodeIndication ::= ENUMERATED { + true, + ... +} + +IMSVoiceSupportIndicator ::= ENUMERATED { + supported, + not-supported, +``` + +``` + ... +} + +IndexToRFSP ::= INTEGER (1..256, ...) + +InfoOnRecommendedCellsAndRANNodesForPaging ::= SEQUENCE { + recommendedCellsForPaging RecommendedCellsForPaging, + recommendRANNodesForPaging RecommendedRANNodesForPaging, + iE-Extensions ProtocolExtensionContainer { {InfoOnRecommendedCellsAndRANNodesForPaging-ExtIEs} } OPTIONAL, + ... +} + +InfoOnRecommendedCellsAndRANNodesForPaging-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +IntegrityProtectionIndication ::= ENUMERATED { + required, + preferred, + not-needed, + ... +} +``` + +``` +IntegrityProtectionResult ::= ENUMERATED { + performed, + not-performed, + ... +} + +IntendedNumberOfPagingAttempts ::= INTEGER (1..16, ...) + +InterfacesToTrace ::= BIT STRING (SIZE(8)) + +ImmediateMDTNr ::= SEQUENCE { + measurementsToActivate MeasurementsToActivate, + m1Configuration M1Configuration OPTIONAL, + -- The above IE shall be present if the Measurements to Activate IE has the first bit set to "1" + m4Configuration M4Configuration OPTIONAL, + -- The above IE shall be present if the Measurements to Activate IE has the third bit set to "1" + m5Configuration M5Configuration OPTIONAL, + -- The above IE shall be present if the Measurements to Activate IE has the fourth bit set to "1" + m6Configuration M6Configuration OPTIONAL, + -- The above IE shall be present if the Measurements to Activate IE has the fifth bit set to "1" + m7Configuration M7Configuration OPTIONAL, + -- The above IE shall be present if the Measurements to Activate IE has the sixth bit set to "1" +``` + +``` + bluetoothMeasurementConfiguration BluetoothMeasurementConfiguration OPTIONAL, + wlanMeasurementConfiguration WLANMeasurementConfiguration OPTIONAL, + mDT-Location-Info MDT-Location-Info OPTIONAL, + sensorMeasurementConfiguration SensorMeasurementConfiguration OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { ImmediateMDTNr-ExtIEs} } OPTIONAL, + ... + } + + ImmediateMDTNr-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... + } + + InterSystemFailureIndication ::= SEQUENCE { + uERLFReportContainer UERLFReportContainer OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { InterSystemFailureIndication-ExtIEs} } OPTIONAL, + ... + } + + InterSystemFailureIndication-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... + } + + IntersystemSONConfigurationTransfer ::= SEQUENCE { +``` + +``` +transferType IntersystemSONTransferType, +intersystemSONInformation IntersystemSONInformation, +iE-Extensions ProtocolExtensionContainer { { IntersystemSONConfigurationTransfer-ExtIEs} } OPTIONAL, +... +} + +IntersystemSONConfigurationTransfer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +... +} + +IntersystemSONTransferType ::= CHOICE { + fromEUTRANtoNGRAN FromEUTRANtoNGRAN, + fromNGRANtoEUTRAN FromNGRANtoEUTRAN, + choice-Extensions ProtocolIE-SingleContainer { { IntersystemSONTransferType-ExtIEs} } +} + +IntersystemSONTransferType-ExtIEs NGAP-PROTOCOL-IES ::= { +... +} + +IntersystemSONeNBID ::= SEQUENCE { + globaleNBID GlobalENB-ID, + selectedEPSTAI EPS-TAI, + iE-Extensions ProtocolExtensionContainer { { IntersystemSONeNBID-ExtIEs} } OPTIONAL, +``` + +``` + ... +} + +IntersystemSONeNBID-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +IntersystemSONGRANnodeID ::= SEQUENCE { + globalRANNodeID GlobalRANNodeID, + selectedTAI TAI, + iE-Extensions ProtocolExtensionContainer { { IntersystemSONGRANnodeID-ExtIEs} } OPTIONAL, + ... +} + +IntersystemSONGRANnodeID-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +IntersystemSONInformation ::= CHOICE { + intersystemSONInformationReport IntersystemSONInformationReport, + choice-Extensions ProtocolIE-SingleContainer { { IntersystemSONInformation-ExtIEs} } +} +``` + +``` +IntersystemSONInformation-ExtIEs NGAP-PROTOCOL-IES ::= { + { ID id-IntersystemSONInformationRequest CRITICALITY ignore TYPE IntersystemSONInformationRequest PRESENCE mandatory }| + { ID id-IntersystemSONInformationReply CRITICALITY ignore TYPE IntersystemSONInformationReply PRESENCE mandatory }, + ... +} +``` + +``` +-- ----- +-- INTER SYSTEM SON INFORMATION REQUEST +-- ----- +``` + +``` +IntersystemSONInformationRequest ::= CHOICE { + nGRAN-CellActivation IntersystemCellActivationRequest, + resourceStatus IntersystemResourceStatusRequest, + choice-Extensions ProtocolIE-SingleContainer { { IntersystemSONInformationRequest-ExtIEs } } +} +``` + +``` +IntersystemSONInformationRequest-ExtIEs NGAP-PROTOCOL-IES ::= { + ... +} +``` + +``` +IntersystemCellActivationRequest ::= SEQUENCE { + activationID INTEGER (0..16384, ...), + cellsToActivateList CellsToActivateList, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { IntersystemCellActivationRequest-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +IntersystemCellActivationRequest-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +CellsToActivateList ::= SEQUENCE (SIZE(1..maxnoofCellsinNGRANNode)) OF NGRAN-CGI +``` + +``` +-- ----- +-- Inter System Resource Status Request +-- ----- +``` + +``` +IntersystemResourceStatusRequest ::= SEQUENCE { + reportingSystem ReportingSystem, + reportCharacteristics ReportCharacteristics, + reportType ReportType, + iE-Extensions ProtocolExtensionContainer { { IntersystemResourceStatusRequest-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +IntersystemResourceStatusRequest-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +ReportingSystem ::= CHOICE { + eUTRAN EUTRAN-ReportingSystemIEs, + nGRAN NGRAN-ReportingSystemIEs, + noReporting NULL, + choice-Extensions ProtocolIE-SingleContainer { { ReportingSystem-ExtIEs } } +} + +ReportingSystem-ExtIEs NGAP-PROTOCOL-IES ::= { + ... +} + +EUTRAN-ReportingSystemIEs ::= SEQUENCE { + eUTRAN-CellToReportList EUTRAN-CellToReportList, + iE-Extensions ProtocolExtensionContainer { { EUTRAN-ReportingSystemIEs-ExtIEs } } OPTIONAL, + ... +} + +EUTRAN-ReportingSystemIEs-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +} + +NGRAN-ReportingSystemIEs ::= SEQUENCE { + +    nGRAN-CellToReportList            nGRAN-CellToReportList, +    iE-Extensions            ProtocolExtensionContainer { {NGRAN-ReportingSystemIEs-ExtIEs} } OPTIONAL, +    ... + +} + +NGRAN-ReportingSystemIEs-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + +    ... + +} + +EUTRAN-CellToReportList ::= SEQUENCE (SIZE(1..maxnoofReportedCells)) OF EUTRAN-CellToReportItem + +EUTRAN-CellToReportItem ::= SEQUENCE { + +    eCGI                EUTRA-CGI, +    iE-Extensions            ProtocolExtensionContainer { {EUTRAN-CellToReportItem-ExtIEs} } OPTIONAL, +    ... + +} + +EUTRAN-CellToReportItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + +    ... + +} + +NGRAN-CellToReportList ::= SEQUENCE (SIZE(1.. maxnoofReportedCells)) OF NGRAN-CellToReportItem + +NGRAN-CellToReportItem ::= SEQUENCE { +    nGRAN-CGI              nGRAN-CGI, +    iE-Extensions        ProtocolExtensionContainer { {NGRAN-CellToReportItem-ExtIEs} } OPTIONAL, +    ... +} + +NGRAN-CellToReportItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +    ... +} + +ReportCharacteristics ::= BIT STRING(SIZE(32)) + +ReportType ::= CHOICE { +    eventBasedReporting    EventBasedReportingIEs, +    periodicReporting    PeriodicReportingIEs, +    choice-Extensions    ProtocolIE-SingleContainer { { ReportType-ExtIEs} } +} + +ReportType-ExtIEs NGAP-PROTOCOL-IES ::= { + +``` + ... +} + +EventBasedReportingIEs ::= SEQUENCE { + intersystemResourceThresholdLow IntersystemResourceThreshold, + intersystemResourceThresholdHigh IntersystemResourceThreshold, + numberOfMeasurementReportingLevels NumberOfMeasurementReportingLevels, + iE-Extensions ProtocolExtensionContainer { {EventBasedReportingIEs-ExtIEs} } OPTIONAL, + ... +} + +EventBasedReportingIEs-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +IntersystemResourceThreshold ::= INTEGER(0..100) + +NumberOfMeasurementReportingLevels ::= ENUMERATED {n2, n3, n4, n5, n10, ..., n0} + +PeriodicReportingIEs ::= SEQUENCE { + reportingPeriodicity ReportingPeriodicity, + iE-Extensions ProtocolExtensionContainer { {PeriodicReportingIEs-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +PeriodicReportingIEs-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +ReportingPeriodicity ::= ENUMERATED { + stop, + single, + ms1000, + ms2000, + ms5000, + ms10000, + ... +} +``` + +``` +-- ----- +-- INTER SYSTEM SON INFORMATION REPLY +-- ----- +``` + +``` +IntersystemSONInformationReply ::= CHOICE { + nGRAN-CellActivation IntersystemCellActivationReply, + resourceStatus IntersystemResourceStatusReply, +``` + +``` + choice-Extensions ProtocolIE-SingleContainer { { IntersystemSONInformationReply-ExtIEs} } + } + + IntersystemSONInformationReply-ExtIEs NGAP-PROTOCOL-IES ::= { + ... + } + + IntersystemCellActivationReply ::= SEQUENCE { + activatedCellList ActivatedCellList, + activation-ID INTEGER(0..16384, ..), + iE-Extensions ProtocolExtensionContainer { { IntersystemCellActivationReply-ExtIEs} } OPTIONAL, + ... + } + + IntersystemCellActivationReply-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... + } + + ActivatedCellList ::= SEQUENCE (SIZE(1..maxnoofCellsinNGRANNode)) OF NGRAN-CGI + +-- ----- + +-- Inter System Resource Status Reply +``` + +``` +-- ----- + +IntersystemResourceStatusReply ::= SEQUENCE { + reportingsystem ReportingSystem, + iE-Extensions ProtocolExtensionContainer { { IntersystemResourceStatusReply-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +IntersystemResourceStatusReply-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +-- ----- +-- INTER SYSTEM SON INFORMATION REPORT +-- ----- +``` + +``` +IntersystemSONInformationReport ::= CHOICE { + hOReportInformation InterSystemHOReport, + failureIndicationInformation InterSystemFailureIndication, + choice-Extensions ProtocolIE-SingleContainer { { IntersystemSONInformationReport-ExtIEs} } +} +``` + +``` +IntersystemSONInformationReport-ExtIEs NGAP-PROTOCOL-IES ::= { + { ID id-EnergySavingIndication CRITICALITY ignore TYPE IntersystemCellStateIndication PRESENCE mandatory }| + { ID id-IntersystemResourceStatusUpdate CRITICALITY ignore TYPE IntersystemResourceStatusReport PRESENCE mandatory }, + ... +} +``` + +``` +IntersystemCellStateIndication ::= SEQUENCE { + notificationCellList NotificationCellList, + iE-Extensions ProtocolExtensionContainer { { IntersystemCellStateIndication-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +IntersystemCellStateIndication-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +NotificationCellList ::= SEQUENCE (SIZE(1.. maxnoofCellsinNGRANNode)) OF NotificationCell-Item +``` + +``` +NotificationCell-Item ::= SEQUENCE { + nGRAN-CGI NGRAN-CGI, + notifyFlag ENUMERATED {activated, deactivated, ...}, + iE-Extensions ProtocolExtensionContainer { { NotificationCell-Item-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +} + +NotificationCell-Item-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ----- + +-- Inter System Resource Status Report + +-- ----- + +IntersystemResourceStatusReport ::= SEQUENCE { + reportingSystem ResourceStatusReportingSystem, + iE-Extensions ProtocolExtensionContainer { { IntersystemResourceStatusReport-ExtIEs } } OPTIONAL, + ... +} + +IntersystemResourceStatusReport-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +ResourceStatusReportingSystem ::= CHOICE { + eUTRAN-ReportingStatus EUTRAN-ReportingStatusIEs, + nGRAN-ReportingStatus NGRAN-ReportingStatusIEs, +} +``` + +``` + choice-Extensions ProtocolIE-SingleContainer { { ResourceStatusReportingSystem-ExtIEs} } +} +``` + +``` +ResourceStatusReportingSystem-ExtIEs NGAP-PROTOCOL-IES ::= { + ... +} +``` + +``` +EUTRAN-ReportingStatusIEs ::= SEQUENCE { + eUTRAN-CellReportList EUTRAN-CellReportList, + iE-Extensions ProtocolExtensionContainer { {EUTRAN-ReportingStatusIEs-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +EUTRAN-ReportingStatusIEs-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +EUTRAN-CellReportList ::= SEQUENCE (SIZE(1..maxnoofReportedCells)) OF EUTRAN-CellReportItem +``` + +``` +EUTRAN-CellReportItem ::= SEQUENCE { + eCGI EUTRA-CGI, + eUTRAN-CompositeAvailableCapacityGroup EUTRAN-CompositeAvailableCapacityGroup, + eUTRAN-NumberOfActiveUEs EUTRAN-NumberOfActiveUEs OPTIONAL, +``` + +``` + eUTRAN-NoofRRCConnections NGRAN-NoofRRCConnections OPTIONAL, + eUTRAN-RadioResourceStatus EUTRAN-RadioResourceStatus OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { EUTRAN-CellReportItem-ExtIEs} } OPTIONAL, + ... +} + +EUTRAN-CellReportItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +EUTRAN-CompositeAvailableCapacityGroup ::= SEQUENCE { + dL-CompositeAvailableCapacity CompositeAvailableCapacity, + uL-CompositeAvailableCapacity CompositeAvailableCapacity, + iE-Extensions ProtocolExtensionContainer { { EUTRAN-CompositeAvailableCapacityGroup-ExtIEs} } OPTIONAL, + ... +} + +EUTRAN-CompositeAvailableCapacityGroup-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +CompositeAvailableCapacity ::= SEQUENCE { +``` + +``` + cellCapacityClassValue INTEGER (1..100, ...) OPTIONAL, + capacityValue INTEGER (0..100), + iE-Extensions ProtocolExtensionContainer { {CompositeAvailableCapacity-ExtIEs} } OPTIONAL, + ... +} + +CompositeAvailableCapacity-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +EUTRAN-NumberOfActiveUEs ::= INTEGER (0..16777215, ...) + +EUTRAN-RadioResourceStatus ::= SEQUENCE { + dL-GBR-PRB-usage INTEGER (0..100), + uL-GBR-PRB-usage INTEGER (0..100), + dL-non-GBR-PRB-usage INTEGER (0..100), + uL-non-GBR-PRB-usage INTEGER (0..100), + dL-Total-PRB-usage INTEGER (0..100), + uL-Total-PRB-usage INTEGER (0..100), + dL-scheduling-PDCCH-CCE-usage INTEGER (0..100) OPTIONAL, + uL-scheduling-PDCCH-CCE-usage INTEGER (0..100) OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {EUTRAN-RadioResourceStatus-ExtIEs} } OPTIONAL, + ... +} +``` + +} + +EUTRAN-RadioResourceStatus-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + +... + +} + +NGRAN-ReportingStatusIEs ::= SEQUENCE { + +    nGRAN-CellReportList                            NGRAN-CellReportList, +    iE-Extensions            ProtocolExtensionContainer { {NGRAN-ReportingStatusIEs-ExtIEs} }    OPTIONAL, + +... + +} + +NGRAN-ReportingStatusIEs-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + +... + +} + +NGRAN-CellReportList ::= SEQUENCE (SIZE(1..maxnoofReportedCells)) OF NGRAN-CellReportItem + +NGRAN-CellReportItem ::= SEQUENCE { + +    nGRAN-CGI                            NGRAN-CGI, +    nGRAN-CompositeAvailableCapacityGroup    EUTRAN-CompositeAvailableCapacityGroup, +    nGRAN-NumberOfActiveUEs                NGRAN-NumberOfActiveUEs                OPTIONAL, +    nGRAN-NoofRRConnections                NGRAN-NoofRRConnections                OPTIONAL, + +``` + nGRAN-RadioResourceStatus NGRAN-RadioResourceStatus OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {NGRAN-CellReportItem-ExtIEs} } OPTIONAL, + ... +} + +NGRAN-CellReportItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +NGRAN-NumberOfActiveUEs ::= INTEGER (0..16777215, ...) + +NGRAN-NoofRRConnections ::= INTEGER (1..65536, ...) + +NGRAN-RadioResourceStatus ::= 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 { { NGRAN-RadioResourceStatus-ExtIEs} } OPTIONAL, + ... +} +``` + +} + +NGRAN-RadioResourceStatus-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + +... + +} + +InterSystemHOReport ::= SEQUENCE { + +handoverReportType      InterSystemHandoverReportType, + +iE-Extensions            ProtocolExtensionContainer { { InterSystemHOReport-ExtIEs } }      OPTIONAL, + +... + +} + +InterSystemHOReport-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + +... + +} + +InterSystemHandoverReportType ::= CHOICE { + +tooearlyIntersystemHO      TooearlyIntersystemHO, + +intersystemUnnecessaryHO      IntersystemUnnecessaryHO, + +choice-Extensions      ProtocolIE-SingleContainer { { InterSystemHandoverReportType-ExtIEs } } + +} + +InterSystemHandoverReportType-ExtIEs NGAP-PROTOCOL-IES ::= { + +``` +{ ID id-IntersystemMobilityFailureforVoiceFallback CRITICALITY ignore TYPE IntersystemMobilityFailureforVoiceFallback PRESENCE mandatory }, +... +} + +IntersystemMobilityFailureforVoiceFallback ::= SEQUENCE { + sourcecellID NGRAN-CGI, + targetcellID EUTRA-CGI, + reconnectCellID EUTRA-CGI OPTIONAL, + uERLFReportContainer UERLFReportContainer OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { IntersystemMobilityFailureforVoiceFallback-ExtIEs } } OPTIONAL, + ... +} + +IntersystemMobilityFailureforVoiceFallback-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +IntersystemUnnecessaryHO ::= SEQUENCE { + sourcecellID NGRAN-CGI, + targetcellID EUTRA-CGI, + earlyIRATHO ENUMERATED {true, false, ...}, + candidateCellList CandidateCellList, + iE-Extensions ProtocolExtensionContainer { { IntersystemUnnecessaryHO-ExtIEs } } OPTIONAL, +``` + +``` + ... +} + +IntersystemUnnecessaryHO-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- J +-- K +-- L + +LAC ::= OCTET STRING (SIZE (2)) + +LAI ::= SEQUENCE { + pLMNIdentity PLMNIdentity, + LAC LAC, + iE-Extensions ProtocolExtensionContainer { {LAI-ExtIEs} } OPTIONAL, + ... +} + +LAI-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +LastVisitedCellInformation ::= CHOICE { + nGRANCell LastVisitedNGRANCellInformation, + eUTRANCell LastVisitedEUTRANCellInformation, + uTRANCell LastVisitedUTRANCellInformation, + gERANCell LastVisitedGERANCellInformation, + choice-Extensions ProtocolIE-SingleContainer { {LastVisitedCellInformation-ExtIEs} } +} + +LastVisitedCellInformation-ExtIEs NGAP-PROTOCOL-IES ::= { + ... +} + +LastVisitedCellItem ::= SEQUENCE { + lastVisitedCellInformation LastVisitedCellInformation, + iE-Extensions ProtocolExtensionContainer { {LastVisitedCellItem-ExtIEs} } OPTIONAL, + ... +} + +LastVisitedCellItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +LastVisitedEUTRANCellInformation ::= OCTET STRING + +LastVisitedGERANCellInformation ::= OCTET STRING + +LastVisitedNGRANCellInformation ::= SEQUENCE { +    globalCellID                    NGRAN-CGI, +    cellType                        CellType, +    timeUEStayedInCell            TimeUEStayedInCell, +    timeUEStayedInCellEnhancedGranularity    TimeUEStayedInCellEnhancedGranularity    OPTIONAL, +    hOCauseValue                    Cause                                                    OPTIONAL, +    iE-Extensions                ProtocolExtensionContainer { LastVisitedNGRANCellInformation-ExtIEs } OPTIONAL, +    ... +} + +LastVisitedNGRANCellInformation-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +    { ID id-LastVisitedPSCellList    CRITICALITY ignore    EXTENSION LastVisitedPSCellList PRESENCE optional }, +    ... +} + +LastVisitedPSCellList ::= SEQUENCE (SIZE(1..maxnoofPSCellsPerPrimaryCellinUEHistoryInfo)) OF LastVisitedPSCellInformation + +LastVisitedPSCellInformation ::= SEQUENCE { +    pSCellID                    NGRAN-CGI                    OPTIONAL, + +``` +timeStay INTEGER (0..40950), +iE-Extensions ProtocolExtensionContainer { {LastVisitedPSCellInformation-ExtIEs} } OPTIONAL, +... +} +``` + +``` +LastVisitedPSCellInformation-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +... +} +``` + +``` +LastVisitedUTRANCellInformation ::= OCTET STRING +``` + +``` +LineType ::= ENUMERATED { + dsl, + pon, + ... +} +``` + +``` +LocationReportingAdditionalInfo ::= ENUMERATED { + includePSCell, + ... +} +``` + +LocationReportingReferenceID ::= INTEGER (1..64, ...) + +LocationReportingRequestType ::= SEQUENCE { + +    eventType                            EventType, +    reportArea                            ReportArea, +    areaOfInterestList                    AreaOfInterestList                    OPTIONAL, +    locationReportingReferenceIDToBeCancelled    LocationReportingReferenceID                    OPTIONAL, + +-- The above IE shall be present if the event type is set to "stop reporting UE presence in the area of interest" + +    iE-Extensions            ProtocolExtensionContainer { {LocationReportingRequestType-ExtIEs} }            OPTIONAL, +    ... + +} + +LocationReportingRequestType-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + +    { ID id-LocationReportingAdditionalInfo CRITICALITY ignore EXTENSION LocationReportingAdditionalInfo PRESENCE optional }| + +    { ID id-AdditionalCancelledlocationReportingReferenceIDList CRITICALITY reject EXTENSION AdditionalCancelledlocationReportingReferenceIDList PRESENCE optional }, + +    ... + +} + +LoggedMDTNr ::= SEQUENCE { + +    loggingInterval                    LoggingInterval, +    loggingDuration                    LoggingDuration, +    loggedMDTTrigger                    LoggedMDTTrigger, + +``` + bluetoothMeasurementConfiguration BluetoothMeasurementConfiguration OPTIONAL, + wlanMeasurementConfiguration WLANMeasurementConfiguration OPTIONAL, + sensorMeasurementConfiguration SensorMeasurementConfiguration OPTIONAL, + areaScopeOfNeighCellsList AreaScopeOfNeighCellsList OPTIONAL, + iE-Extensions ProtocolExtensionContainer { LoggedMDTNr-ExtIEs } OPTIONAL, + ... +} + +LoggedMDTNr-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-EarlyMeasurement CRITICALITY ignore EXTENSION EarlyMeasurement PRESENCE optional }, + ... +} + +LoggingInterval ::= ENUMERATED { + ms320, ms640, ms1280, ms2560, ms5120, ms10240, ms20480, ms30720, ms40960, ms61440, + infinity, + ... +} + +LoggingDuration ::= ENUMERATED {m10, m20, m40, m60, m90, m120, ...} + +Links-to-log ::= ENUMERATED { + uplink, +``` + +``` +downlink, +both-uplink-and-downlink, +... +} + +LoggedMDTTrigger ::= CHOICE{ + periodical NULL, + eventTrigger EventTrigger, + choice-Extensions ProtocolIE-SingleContainer { {LoggedMDTTrigger-ExtIEs} } +} + +LoggedMDTTrigger-ExtIEs NGAP-PROTOCOL-IES ::= { + ... +} + +LTEM-Indication ::= ENUMERATED {lte-m,...} + +LTEUERLFReportContainer ::= OCTET STRING + +LTEV2XServicesAuthorized ::= SEQUENCE { + vehicleUE VehicleUE OPTIONAL, + pedestrianUE PedestrianUE OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {LTEV2XServicesAuthorized-ExtIEs} } OPTIONAL, +``` + +``` + ... +} + +LTEV2XServicesAuthorized-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +LTEUESidelinkAggregateMaximumBitrate ::= SEQUENCE { + uESidelinkAggregateMaximumBitRate BitRate, + iE-Extensions ProtocolExtensionContainer { { LTEUE-Sidelink-Aggregate-MaximumBitrates-ExtIEs } } OPTIONAL, + ... +} + +LTEUE-Sidelink-Aggregate-MaximumBitrates-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +LTE-A2X-ServicesAuthorized ::= SEQUENCE { + uAV-UE ENUMERATED {authorized, not-authorized, ...} OPTIONAL, + uAV-ControllerUE ENUMERATED {authorized, not-authorized, ...} OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { LTE-A2X-ServicesAuthorized-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +LTE-A2X-ServicesAuthorized-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +-- M +``` + +``` +MaskedIMEISV ::= BIT STRING (SIZE(64)) +``` + +``` +MaximumDataBurstVolume ::= INTEGER (0..4095, ..., 4096.. 2000000) +``` + +``` +MessageIdentifier ::= BIT STRING (SIZE(16)) +``` + +``` +MaximumIntegrityProtectedDataRate ::= ENUMERATED { + bitrate64kbs, + maximum-UE-rate, + ... +} +``` + +``` +MBS-AreaSessionID ::= INTEGER (0..65535, ...) +``` + +``` +MBSCommServiceType ::= ENUMERATED {broadcast, multicast, ...} +``` + +MBS-DataForwardingResponseMRBList ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF MBS-DataForwardingResponseMRBItem + +MBS-DataForwardingResponseMRBItem ::= SEQUENCE { +    mRB-ID                            MRB-ID, +    dL-Forwarding-UPTNLInformation    UPTransportLayerInformation, +    mRB-ProgressInformation            MRB-ProgressInformation            OPTIONAL, +    iE-Extensions                    ProtocolExtensionContainer { { MBS-DataForwardingResponseMRBItem-ExtIEs} } OPTIONAL, +    ... +} + +MBS-DataForwardingResponseMRBItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +    ... +} + +MBS-MappingandDataForwardingRequestList ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF MBS-MappingandDataForwardingRequestItem + +MBS-MappingandDataForwardingRequestItem ::= SEQUENCE { +    mRB-ID                            MRB-ID, +    mBS-QoSFlowList                MBS-QoSFlowList, +    mRB-ProgressInformation            MRB-ProgressInformation            OPTIONAL, +    iE-Extensions            ProtocolExtensionContainer { { MBS-MappingandDataForwardingRequestItem-ExtIEs} } OPTIONAL, +    ... +} + +} + +MBS-MappingandDataForwardingRequestItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + +... + +} + +MBS-QoSFlowList ::= SEQUENCE (SIZE(1..maxnoofMBSQoSFlows)) OF QoSFlowIdentifier + +MRB-ProgressInformation ::= CHOICE { + +pDCP-SN-Length12 INTEGER (0..4095), + +pDCP-SN-Length18 INTEGER (0..262143), + +choice-Extensions ProtocolIE-SingleContainer { { MRB-ProgressInformation-ExtIEs} } + +} + +MRB-ProgressInformation-ExtIEs NGAP-PROTOCOL-IES ::= { + +... + +} + +MBS-QoSFlowsToBeSetupList ::= SEQUENCE (SIZE(1.. maxnoofMBSQoSFlows)) OF MBS-QoSFlowsToBeSetupItem + +MBS-QoSFlowsToBeSetupItem ::= SEQUENCE { + +mBSqoSFlowIdentifier QoSFlowIdentifier, + +mBSqoSFlowLevelQoSParameters QoSFlowLevelQoSParameters, + +``` +iE-Extensions ProtocolExtensionContainer { {MBS-QoSFlowsToBeSetupItem-ExtIEs} } OPTIONAL, +... +} + +MBS-QoSFlowsToBeSetupItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +... +} + +MBS-ServiceArea ::= CHOICE { + locationindependent MBS-ServiceAreaInformation, + locationdependent MBS-ServiceAreaInformationList, + choice-Extensions ProtocolIE-SingleContainer { {MBS-ServiceArea-ExtIEs} } +} + +MBS-ServiceArea-ExtIEs NGAP-PROTOCOL-IES ::= { +... +} + +MBS-ServiceAreaInformationList ::= SEQUENCE (SIZE(1..maxnoofMBSServiceAreaInformation)) OF MBS-ServiceAreaInformationItem + +MBS-ServiceAreaInformationItem ::= SEQUENCE { +``` + +``` + mBS-AreaSessionID MBS-AreaSessionID, + mBS-ServiceAreaInformation MBS-ServiceAreaInformation, + iE-Extensions ProtocolExtensionContainer { {MBS-ServiceAreaInformationItem-ExtIEs} } OPTIONAL, + ... + } + + MBS-ServiceAreaInformationItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... + } + + MBS-ServiceAreaInformation ::= SEQUENCE { + mBS-ServiceAreaCellList MBS-ServiceAreaCellList OPTIONAL, + mBS-ServiceAreaTAIList MBS-ServiceAreaTAIList OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {MBS-ServiceAreaInformation-ExtIEs} } OPTIONAL, + ... + } + + MBS-ServiceAreaInformation-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... + } + + MBS-ServiceAreaCellList ::= SEQUENCE (SIZE(1.. maxnoofCellsforMBS)) OF NR-CGI +``` + +MBS-ServiceAreaTAIList ::= SEQUENCE (SIZE(1.. maxnoofTAIforMBS)) OF TAI + +MBS-SessionID ::= SEQUENCE { +    tMGI                    TMGI, +    nID                     NID                                                    OPTIONAL, +    iE-Extensions         ProtocolExtensionContainer { {MBS-SessionID-ExtIEs} }    OPTIONAL, +    ... +} + +MBS-SessionID-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +    ... +} + +MBSSessionFailedtoSetupList ::= SEQUENCE (SIZE(1.. maxnoofMBSSessions)) OF MBSSessionFailedtoSetupItem + +MBSSessionFailedtoSetupItem ::= SEQUENCE { +    mBS-SessionID          MBS-SessionID, +    mBS-AreaSessionID     MBS-AreaSessionID                                                    OPTIONAL, +    cause                    Cause, +    iE-Extensions         ProtocolExtensionContainer { { MBSSessionFailedtoSetupItem-ExtIEs} }    OPTIONAL, +    ... +} + +``` +MBSSessionFailedtoSetupItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +MBS-ActiveSessionInformation-SourcetoTargetList ::= SEQUENCE (SIZE(1..maxnoofMBSSessionsofUE)) OF MBS-ActiveSessionInformation-SourcetoTargetItem + +MBS-ActiveSessionInformation-SourcetoTargetItem ::= SEQUENCE { + mBS-SessionID mBS-SessionID, + mBS-AreaSessionID mBS-AreaSessionID OPTIONAL, + mBS-ServiceArea mBS-ServiceArea OPTIONAL, + mBS-QoSFlowsToBeSetupList mBS-QoSFlowsToBeSetupList, + mBS-MappingandDataForwardingRequestList mBS-MappingandDataForwardingRequestList OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { MBS-ActiveSessionInformation-SourcetoTargetItem-ExtIEs} } OPTIONAL, + ... +} + +MBS-ActiveSessionInformation-SourcetoTargetItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +MBS-ActiveSessionInformation-TargettoSourceList ::= SEQUENCE (SIZE(1..maxnoofMBSSessionsofUE)) OF MBS-ActiveSessionInformation-TargettoSourceItem + +MBS-ActiveSessionInformation-TargettoSourceItem ::= SEQUENCE { +``` + +``` + mBS-SessionID MBS-SessionID, + mBS-DataForwardingResponseMRBList MBS-DataForwardingResponseMRBList + OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { MBS-ActiveSessionInformation-TargettoSourceItem-ExtIEs} } OPTIONAL, + ... +} + +MBS-ActiveSessionInformation-TargettoSourceItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +MBS-AssistanceInformation ::= ENUMERATED {true, ...} + +MBSSessionSetupOrModFailureTransfer ::= SEQUENCE { + cause Cause, + criticalityDiagnostics CriticalityDiagnostics OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { MBSSessionSetupOrModFailureTransfer-ExtIEs} } OPTIONAL, + ... +} + +MBSSessionSetupOrModFailureTransfer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +MBSSessionSetupResponseList ::= SEQUENCE (SIZE(1.. maxnoofMBSSessions)) OF MBSSessionSetupResponseItem +``` + +``` +MBSSessionSetupResponseItem ::= SEQUENCE { + mBS-SessionID mBS-SessionID, + mBS-AreaSessionID mBS-AreaSessionID OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { MBSSessionSetupResponseItem-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +MBSSessionSetupResponseItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +MBSSessionSetupOrModRequestTransfer ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { MBSSessionSetupOrModRequestTransferIEs} }, + ... +} +``` + +``` +MBSSessionSetupOrModRequestTransferIEs NGAP-PROTOCOL-IES ::= { + { ID id-MBS-SessionTNLInfo5GC CRITICALITY reject TYPE MBS-SessionTNLInfo5GC PRESENCE optional }| + { ID id-MBS-QoSFlowsToBeSetupModList CRITICALITY reject TYPE MBS-QoSFlowsToBeSetupList PRESENCE mandatory }| + { ID id-MBS-SessionFSAIDList CRITICALITY ignore TYPE MBS-SessionFSAIDList PRESENCE optional }| + { ID id-SupportedUETypeList CRITICALITY ignore TYPE SupportedUETypeList PRESENCE optional }, +``` + +``` + ... +} + +SupportedUETypeList ::= SEQUENCE (SIZE(1.. maxnoofUETypes)) OF SupportedUEType + +SupportedUEType ::= ENUMERATED {non-RedCap-UE, redCap-UE, ...} + +MBS-SessionFSAIDList ::= SEQUENCE (SIZE(1.. maxnoofMBSFSAs)) OF MBS-SessionFSAID + +MBS-SessionFSAID ::= OCTET STRING (SIZE(3)) + +MBSSessionReleaseResponseTransfer ::= SEQUENCE { + mBS-SessionTNLInfoNGRAN MBS-SessionTNLInfoNGRAN OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {MBSSessionReleaseResponseTransfer-ExtIEs} } OPTIONAL, + ... +} + +MBSSessionReleaseResponseTransfer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +MBSSessionSetupOrModResponseTransfer ::= SEQUENCE { + mBS-SessionTNLInfoNGRAN MBS-SessionTNLInfoNGRAN OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {MBSSessionSetupOrModResponseTransfer-ExtIEs} } OPTIONAL, +``` + +``` + ... +} + +MBSSessionSetupOrModResponseTransfer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +MBS-SupportIndicator ::= ENUMERATED { + true, + ... +} + +MBS-SessionTNLInfo5GC ::= CHOICE { + locationindependent SharedNGU-MulticastTNLInformation, + locationdependent MBS-SessionTNLInfo5GCList, + choice-Extensions ProtocolIE-SingleContainer { {MBS-SessionTNLInfo5GC-ExtIEs} } +} + +MBS-SessionTNLInfo5GC-ExtIEs NGAP-PROTOCOL-IES ::= { + ... +} + +MBS-SessionTNLInfo5GCList ::= SEQUENCE (SIZE(1..maxnoofMBSServiceAreaInformation)) OF MBS-SessionTNLInfo5GCItem +``` + +``` +MBS-SessionTNLInfo5GCItem ::= SEQUENCE { + mBS-AreaSessionID mBS-AreaSessionID, + sharedNGU-MulticastTNLInformation SharedNGU-MulticastTNLInformation, + iE-Extensions ProtocolExtensionContainer { {MBS-SessionTNLInfo5GCItem-ExtIEs} } OPTIONAL, + ... +} + +MBS-SessionTNLInfo5GCItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +MBS-SessionTNLInfoNGRAN ::= CHOICE { + locationindependent UPTransportLayerInformation, + locationdependent MBS-SessionTNLInfoNGRANList, + choice-Extensions ProtocolIE-SingleContainer { {MBS-SessionTNLInfoNGRAN-ExtIEs} } +} + +MBS-SessionTNLInfoNGRAN-ExtIEs NGAP-PROTOCOL-IES ::= { + ... +} + +MBS-SessionTNLInfoNGRANList ::= SEQUENCE (SIZE(1..maxnoofMBSServiceAreaInformation)) OF MBS-SessionTNLInfoNGRANItem +``` + +``` +MBS-SessionTNLInfoNGRANItem ::= SEQUENCE { + mBS-AreaSessionID MBS-AreaSessionID, + sharedNGU-UnicastTNLInformation UPTransportLayerInformation OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {MBS-SessionTNLInfoNGRANItem-ExtIEs} } OPTIONAL, + ... +} + +MBS-SessionTNLInfoNGRANItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +MBS-DistributionReleaseRequestTransfer ::= SEQUENCE { + mBS-SessionID MBS-SessionID, + mBS-AreaSessionID MBS-AreaSessionID OPTIONAL, + sharedNGU-UnicastTNLInformation UPTransportLayerInformation OPTIONAL, + cause Cause, + iE-Extensions ProtocolExtensionContainer { { MBS-DistributionReleaseRequestTransfer-ExtIEs} } OPTIONAL, + ... +} + +MBS-DistributionReleaseRequestTransfer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +} + +MBS-DistributionSetupRequestTransfer ::= SEQUENCE { + mBS-SessionID mBS-SessionID, + mBS-AreaSessionID mBS-AreaSessionID OPTIONAL, + sharedNGU-UnicastTNLInformation UPTransportLayerInformation OPTIONAL, + iE-Extensions ProtocolExtensionContainer { MBS-DistributionSetupRequestTransfer-ExtIEs } OPTIONAL, + ... +} + +MBS-DistributionSetupRequestTransfer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +MBS-DistributionSetupResponseTransfer ::= SEQUENCE { + mBS-SessionID mBS-SessionID, + mBS-AreaSessionID mBS-AreaSessionID OPTIONAL, + sharedNGU-MulticastTNLInformation SharedNGU-MulticastTNLInformation OPTIONAL, + mBS-QoSFlowsToBeSetupList mBS-QoSFlowsToBeSetupList, + mBSSessionStatus mBSSessionStatus, + mBS-ServiceArea mBS-ServiceArea OPTIONAL, + iE-Extensions ProtocolExtensionContainer { MBS-DistributionSetupResponseTransfer-ExtIEs } OPTIONAL, + ... +} +``` + +``` +} + +MBS-DistributionSetupResponseTransfer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +MBS-DistributionSetupUnsuccessfulTransfer ::= SEQUENCE { + mBS-SessionID MBS-SessionID, + mBS-AreaSessionID MBS-AreaSessionID OPTIONAL, + cause Cause, + criticalityDiagnostics CriticalityDiagnostics OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { MBS-DistributionSetupUnsuccessfulTransfer-ExtIEs } } OPTIONAL, + ... +} + +MBS-DistributionSetupUnsuccessfulTransfer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +MBSSessionSetupRequestList ::= SEQUENCE (SIZE(1..maxnoofMBSSessions)) OF MBSSessionSetupRequestItem + +MBSSessionSetupRequestItem ::= SEQUENCE { +``` + +``` + + mBS-SessionID MBS-SessionID, + mBS-AreaSessionID MBS-AreaSessionID OPTIONAL, + associatedMBSQosFlowSetupRequestList AssociatedMBSQosFlowSetupRequestList OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { MBSSessionSetupRequestItem-ExtIEs} } OPTIONAL, + ... +} + +``` + +``` + +MBSSessionSetupRequestItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-MBS-AssistanceInformation CRITICALITY ignore EXTENSION MBS-AssistanceInformation PRESENCE optional }, + ... +} + +``` + +``` + +MBSSessionSetuporModifyRequestList ::= SEQUENCE (SIZE(1..maxnoofMBSSessions)) OF MBSSessionSetuporModifyRequestItem + +``` + +``` + +MBSSessionSetuporModifyRequestItem ::= SEQUENCE { + mBS-SessionID MBS-SessionID, + mBS-AreaSessionID MBS-AreaSessionID OPTIONAL, + associatedMBSQosFlowSetuporModifyRequestList AssociatedMBSQosFlowSetuporModifyRequestList OPTIONAL, + mBS-QosFlowToReleaseList QosFlowListWithCause OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {MBSSessionSetuporModifyRequestItem-ExtIEs} } OPTIONAL, + ... +} + +``` + +``` +MBSSessionSetuporModifyRequestItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-MBS-AssistanceInformation CRITICALITY ignore EXTENSION MBS-AssistanceInformation PRESENCE optional }, + ... +} +``` + +``` +MBSSessionToReleaseList ::= SEQUENCE (SIZE(1..maxnoofMBSSessions)) OF MBSSessionToReleaseItem +``` + +``` +MBSSessionToReleaseItem ::= SEQUENCE { + mBS-SessionID MBS-SessionID, + cause Cause, + iE-Extensions ProtocolExtensionContainer { { MBSSessionToReleaseItem-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +MBSSessionToReleaseItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +MBSSessionStatus ::= ENUMERATED { + activated, + deactivated, + ... +} +``` + +} + +``` +MicoAllPLMN ::= ENUMERATED { + true, + ... +} +``` + +``` +MICOModeIndication ::= ENUMERATED { + true, + ... +} +``` + +``` +MobilityInformation ::= BIT STRING (SIZE(16)) +``` + +``` +ExtendedMobilityInformation ::= BIT STRING (SIZE(32)) +``` + +``` +MobilityRestrictionList ::= SEQUENCE { + servingPLMN PLMNIdentity, + equivalentPLMNs EquivalentPLMNs OPTIONAL, + rATRestrictions RATRestrictions OPTIONAL, + forbiddenAreaInformation ForbiddenAreaInformation OPTIONAL, + serviceAreaInformation ServiceAreaInformation OPTIONAL, +``` + +``` + + iE-Extensions ProtocolExtensionContainer { {MobilityRestrictionList-ExtIEs} } OPTIONAL, + ... + } + + MobilityRestrictionList-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-LastEUTRAN-PLMNIdentity CRITICALITY ignore EXTENSION PLMNIdentity PRESENCE optional }| + { ID id-CNTypeRestrictionsForServing CRITICALITY ignore EXTENSION CNTypeRestrictionsForServing PRESENCE optional }| + { ID id-CNTypeRestrictionsForEquivalent CRITICALITY ignore EXTENSION CNTypeRestrictionsForEquivalent PRESENCE optional }| + { ID id-NPN-MobilityInformation CRITICALITY reject EXTENSION NPN-MobilityInformation PRESENCE optional }, + ... + } + + MDT-AlignmentInfo ::= CHOICE { + s-basedMDT NGRANTraceID, + choice-Extensions ProtocolIE-SingleContainer { { MDT-AlignmentInfo-ExtIEs} } + } + + MDT-AlignmentInfo-ExtIEs NGAP-PROTOCOL-IES ::= { + ... + } + + MDTPLMNList ::= SEQUENCE (SIZE(1..maxnoofMDTPLMNs)) OF PLMNIdentity + +``` + +``` +MDTPLMNModificationList ::= SEQUENCE (SIZE(0..maxnoofMDTPLMNs)) OF PLMNIdentity +``` + +``` +MDT-Configuration ::= SEQUENCE { + mdt-Config-NR MDT-Configuration-NR OPTIONAL, + mdt-Config-EUTRA MDT-Configuration-EUTRA OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { MDT-Configuration-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +MDT-Configuration-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +MDT-Configuration-NR ::= SEQUENCE { + mdt-Activation MDT-Activation, + areaScopeOfMDT AreaScopeOfMDT-NR, + mDTModeNr MDTModeNr, + signallingBasedMDTPLMNList MDTPLMNList OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { MDT-Configuration-NR-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +MDT-Configuration-NR-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +``` + +``` +{ ID id-PNI-NPN-AreaScopeofMDT CRITICALITY ignore EXTENSION PNI-NPN-AreaScopeofMDT PRESENCE optional }, + ... +} + +MDT-Configuration-EUTRA ::= SEQUENCE { + mdt-Activation MDT-Activation, + areaScopeOfMDT AreaScopeOfMDT-EUTRA, + mDTMode MDTModeEutra, + signallingBasedMDTPLMNList MDTPLMNList OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { MDT-Configuration-EUTRA-ExtIEs} } OPTIONAL, + ... +} + +MDT-Configuration-EUTRA-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +MDT-Activation ::= ENUMERATED { + immediate-MDT-only, + logged-MDT-only, + immediate-MDT-and-Trace, + ... +} +``` + +``` +MDTModeNr ::= CHOICE { + immediateMDTNr ImmediateMDTNr, + loggedMDTNr LoggedMDTNr, + choice-Extensions ProtocolIE-SingleContainer { {MDTModeNr-ExtIEs} } +} + +MDTModeNr-ExtIEs NGAP-PROTOCOL-IES ::= { + ... +} + +MDTModeEutra ::= OCTET STRING + +MeasurementsToActivate ::= BIT STRING(SIZE(8)) + +MobileIAB-Authorized ::= ENUMERATED { + authorized, + not-authorized, + ... +} + +MobileIABNodeIndication ::= ENUMERATED { + true, +``` + +``` + ... +} + +MobileIAB-Supported ::= ENUMERATED { + true, + ... +} + +MRB-ID ::= INTEGER (1..512, ...) + +MulticastSessionActivationRequestTransfer ::= SEQUENCE { + mBS-SessionID MBS-SessionID, + iE-Extensions ProtocolExtensionContainer { { MulticastSessionActivationRequestTransfer-ExtIEs} } OPTIONAL, + ... +} + +MulticastSessionActivationRequestTransfer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +MulticastSessionDeactivationRequestTransfer ::= SEQUENCE { + mBS-SessionID MBS-SessionID, + iE-Extensions ProtocolExtensionContainer { { MulticastSessionDeactivationRequestTransfer-ExtIEs} } OPTIONAL, +``` + +``` + + ... + } + +``` + +``` + +MulticastSessionDeactivationRequestTransfer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +``` + +MulticastSessionUpdateRequestTransfer ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {MulticastSessionUpdateRequestTransferIEs} }, + ... +} + +``` + +``` + +MulticastSessionUpdateRequestTransferIEs NGAP-PROTOCOL-IES ::= { + { ID id-MBS-SessionID CRITICALITY reject TYPE MBS-SessionID PRESENCE mandatory }| + { ID id-MBS-ServiceArea CRITICALITY reject TYPE MBS-ServiceArea PRESENCE optional }| + { ID id-MBS-QoSFlowsToBeSetupModList CRITICALITY reject TYPE MBS-QoSFlowsToBeSetupList PRESENCE optional }| + { ID id-MBS-QoSFlowToReleaseList CRITICALITY reject TYPE QoSFlowListWithCause PRESENCE optional }| + { ID id-MBS-SessionTNLInfo5GC CRITICALITY reject TYPE MBS-SessionTNLInfo5GC PRESENCE optional }, + ... +} + +``` + +``` + +MulticastGroupPagingAreaList ::= SEQUENCE (SIZE(1..maxnoofPagingAreas)) OF MulticastGroupPagingAreaItem + +``` + +``` +MulticastGroupPagingAreaItem ::= SEQUENCE { + multicastGroupPagingArea MulticastGroupPagingArea, + uE-PagingList UE-PagingList OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { MulticastGroupPagingAreaItem-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +MulticastGroupPagingAreaItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +MBS-AreaTAIList ::= SEQUENCE (SIZE(1..maxnoofTAIforPaging)) OF TAI +``` + +``` +MulticastGroupPagingArea ::= SEQUENCE { + mBS-AreaTAIList MBS-AreaTAIList, + iE-Extensions ProtocolExtensionContainer { { MulticastGroupPagingArea-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +MulticastGroupPagingArea-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +UE-PagingList ::= SEQUENCE (SIZE(1..maxnoofUEsforPaging)) OF UE-PagingItem + +UE-PagingItem ::= SEQUENCE { +    uEIdentityIndexValue    UEIdentityIndexValue, +    pagingDRX              PagingDRX                                  OPTIONAL, +    iE-Extensions        ProtocolExtensionContainer { { UE-PagingItem-ExtIEs} } OPTIONAL, +    ... +} + +UE-PagingItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +    ... +} + +M1Configuration ::= SEQUENCE { +    mlreportingTrigger    M1ReportingTrigger, +    mlthresholdEventA2    M1ThresholdEventA2                                  OPTIONAL, +    -- The above IE shall be present if the M1 Reporting Trigger IE is set to "A2event-triggered" or "A2event-triggered periodic" +    mlperiodicReporting    M1PeriodicReporting                                  OPTIONAL, +    -- The above IE shall be present if the M1 Reporting Trigger IE is set to "periodic" or "A2event-triggered periodic" +    iE-Extensions        ProtocolExtensionContainer { { M1Configuration-ExtIEs} } OPTIONAL, +    ... +} + +``` +M1Configuration-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-IncludeBeamMeasurementsIndication CRITICALITY ignore EXTENSION IncludeBeamMeasurementsIndication PRESENCE optional } | + { ID id-BeamMeasurementsReportConfiguration CRITICALITY ignore EXTENSION BeamMeasurementsReportConfiguration PRESENCE conditional }, + -- The above IE shall be present if the IncludeBeamMeasurementsIndication IE is set to "true" + ... +} + +IncludeBeamMeasurementsIndication ::= ENUMERATED { + true, + ... +} + +MaxNrofRS-IndexesToReport ::= INTEGER (1..64, ...) + +M1ReportingTrigger ::= ENUMERATED { + periodic, + a2eventtriggered, + a2eventtriggered-periodic, + ... +} + +M1ThresholdEventA2 ::= SEQUENCE { +``` + +``` + m1ThresholdType M1ThresholdType, + iE-Extensions ProtocolExtensionContainer { { M1ThresholdEventA2-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +M1ThresholdEventA2-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +M1ThresholdType ::= CHOICE { + threshold-RSRP Threshold-RSRP, + threshold-RSRQ Threshold-RSRQ, + threshold-SINR Threshold-SINR, + choice-Extensions ProtocolIE-SingleContainer { {M1ThresholdType-ExtIEs} } +} +``` + +``` +M1ThresholdType-ExtIEs NGAP-PROTOCOL-IES ::= { + ... +} +``` + +``` +M1PeriodicReporting ::= SEQUENCE { + reportInterval ReportIntervalMDT, + reportAmount ReportAmountMDT, +} +``` + +``` + iE-Extensions ProtocolExtensionContainer { { M1PeriodicReporting-ExtIEs} } OPTIONAL, + ... +} + +M1PeriodicReporting-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + {ID id-ExtendedReportIntervalMDT CRITICALITY ignore EXTENSION ExtendedReportIntervalMDT PRESENCE optional}, + ... +} + +M4Configuration ::= SEQUENCE { + m4period M4period, + m4-links-to-log Links-to-log, + iE-Extensions ProtocolExtensionContainer { { M4Configuration-ExtIEs} } OPTIONAL, + ... +} + +M4Configuration-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-M4ReportAmount CRITICALITY ignore EXTENSION M4ReportAmountMDT PRESENCE optional }, + ... +} + +M4ReportAmountMDT ::= ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity, ...} +``` + +M4period ::= ENUMERATED {ms1024, ms2048, ms5120, ms10240, min1, ... } + +M5Configuration ::= SEQUENCE { +    m5period          M5period, +    m5-links-to-log   Links-to-log, +    iE-Extensions     ProtocolExtensionContainer { { M5Configuration-ExtIEs } } OPTIONAL, +    ... +} + +M5Configuration-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +    { ID id-M5ReportAmount          CRITICALITY ignore  EXTENSION M5ReportAmountMDT          PRESENCE optional  }, +    ... +} + +M5ReportAmountMDT ::= ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity, ...} + +M5period ::= ENUMERATED {ms1024, ms2048, ms5120, ms10240, min1, ... } + +M6Configuration ::= SEQUENCE { +    m6report-Interval  M6report-Interval, +    m6-links-to-log    Links-to-log, +    iE-Extensions      ProtocolExtensionContainer { { M6Configuration-ExtIEs } } OPTIONAL, + +``` + ... +} + +M6Configuration-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-M6ReportAmount CRITICALITY ignore EXTENSION M6ReportAmountMDT PRESENCE optional } | + { ID id-ExcessPacketDelayThresholdConfiguration CRITICALITY ignore EXTENSION ExcessPacketDelayThresholdConfiguration PRESENCE optional }, + ... +} + +M6ReportAmountMDT ::= ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity, ...} + +M6report-Interval ::= ENUMERATED { + ms120, ms240, ms480, ms640, ms1024, ms2048, ms5120, ms10240, ms20480, ms40960, min1, min6, min12, min30, + ... +} + +M7Configuration ::= SEQUENCE { + m7period M7period, + m7-links-to-log Links-to-log, + iE-Extensions ProtocolExtensionContainer { { M7Configuration-ExtIEs} } OPTIONAL, + ... +} +``` + +} + +M7Configuration-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + +{ ID id-M7ReportAmount CRITICALITY ignore EXTENSION M7ReportAmountMDT PRESENCE optional }, + +... + +} + +M7ReportAmountMDT ::= ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity, ...} + +M7period ::= INTEGER(1..60, ...) + +MDT-Location-Info ::= SEQUENCE { + +MDT-Location-Information MDT-Location-Information, + +iE-Extensions ProtocolExtensionContainer { { MDT-Location-Info-ExtIEs } } OPTIONAL, + +... + +} + +MDT-Location-Info-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + +... + +} + +MDT-Location-Information ::= BIT STRING (SIZE (8)) + +-- N + +N3IWF-ID ::= CHOICE { + +    n3IWF-ID            BIT STRING (SIZE(16)), +    choice-Extensions    ProtocolIE-SingleContainer { {N3IWF-ID-ExtIEs} } + +} + +N3IWF-ID-ExtIEs NGAP-PROTOCOL-IES ::= { + +    ... + +} + +N6JitterInformation ::= SEQUENCE { + +    n6JitterLowerBound    INTEGER (-127..127), +    n6JitterUpperBound    INTEGER (-127..127), +    iE-Extensions        ProtocolExtensionContainer { { N6JitterInformation-ExtIEs} }    OPTIONAL, + +    ... + +} + +N6JitterInformation-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + +    ... + +} + +NAS-PDU ::= OCTET STRING + +NASSecurityParametersFromNGRAN ::= OCTET STRING + +NB-IoT-DefaultPagingDRX ::= ENUMERATED { + +    rf128, rf256, rf512, rf1024, + +    ... + +} + +NB-IoT-PagingDRX ::= ENUMERATED { + +    rf32, rf64, rf128, rf256, rf512, rf1024, + +    ... + +} + +NB-IoT-Paging-eDRXCycle ::= ENUMERATED { + +    hf2, hf4, hf6, hf8, hf10, hf12, hf14, hf16, hf32, hf64, hf128, hf256, hf512, hf1024, + +    ... + +} + +NB-IoT-Paging-TimeWindow ::= ENUMERATED { + +    s1, s2, s3, s4, s5, s6, s7, s8, s9, s10, s11, s12, s13, s14, s15, s16, + +    ... + +} + +``` +NB-IoT-Paging-eDRXInfo ::= SEQUENCE { + nB-IoT-Paging-eDRXCycle NB-IoT-Paging-eDRXCycle, + nB-IoT-Paging-TimeWindow NB-IoT-Paging-TimeWindow OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { NB-IoT-Paging-eDRXInfo-ExtIEs} } OPTIONAL, + ... +} + +NB-IoT-Paging-eDRXInfo-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +NB-IoT-UEPriority ::= INTEGER (0..255, ...) + +NetworkControlledRepeaterAuthorized ::= ENUMERATED {authorized, not-authorized, ...} + +NetworkInstance ::= INTEGER (1..256, ...) + +NewSecurityContextInd ::= ENUMERATED { + true, + ... +} + +NextHopChainingCount ::= INTEGER (0..7) +``` + +``` +NextPagingAreaScope ::= ENUMERATED { +``` + +``` + same, +``` + +``` + changed, +``` + +``` + ... +``` + +``` +} +``` + +``` +NGAPIESupportInformationRequestList ::= SEQUENCE (SIZE(1.. maxnoofNGAPIESupportInfo)) OF NGAPIESupportInformationRequestItem +``` + +``` +NGAPIESupportInformationRequestItem ::= SEQUENCE { +``` + +``` + ngap-ProtocolIE-Id ProtocolIE-ID, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { NGAPIESupportInformationRequestItem-ExtIEs} } OPTIONAL, +``` + +``` + ... +``` + +``` +} +``` + +``` +NGAPIESupportInformationRequestItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +NGAPIESupportInformationResponseList ::= SEQUENCE (SIZE(1.. maxnoofNGAPIESupportInfo)) OF NGAPIESupportInformationResponseItem +``` + +``` +NGAPIESupportInformationResponseItem ::= SEQUENCE { +``` + +``` + ngap-ProtocolIE-Id ProtocolIE-ID, +``` + +``` + ngap-ProtocolIESupportInfo ENUMERATED {supported, not-supported, ...}, + ngap-ProtocolIEPresenceInfo ENUMERATED {present, not-present, ...}, + iE-Extensions ProtocolExtensionContainer { { NGAPIESupportInformationResponseItem-ExtIEs} } OPTIONAL, + ... +} + +NGAPIESupportInformationResponseItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +NgENB-ID ::= CHOICE { + macroNgENB-ID BIT STRING (SIZE(20)), + shortMacroNgENB-ID BIT STRING (SIZE(18)), + longMacroNgENB-ID BIT STRING (SIZE(21)), + choice-Extensions ProtocolIE-SingleContainer { {NgENB-ID-ExtIEs} } +} + +NgENB-ID-ExtIEs NGAP-PROTOCOL-IES ::= { + ... +} + +NotifySourceNGRANNode ::= ENUMERATED { + notifySource, +``` + +``` + ... +} + +NGRAN-CGI ::= CHOICE { + nR-CGI NR-CGI, + eUTRA-CGI EUTRA-CGI, + choice-Extensions ProtocolIE-SingleContainer { {NGRAN-CGI-ExtIEs} } +} + +NGRAN-CGI-ExtIEs NGAP-PROTOCOL-IES ::= { + ... +} + +NGRAN-TNLAssociationToRemoveList ::= SEQUENCE (SIZE(1..maxnoofTNLAssociations)) OF NGRAN-TNLAssociationToRemoveItem + +NGRAN-TNLAssociationToRemoveItem ::= SEQUENCE { + tNLAssociationTransportLayerAddress CPTransportLayerInformation, + tNLAssociationTransportLayerAddressAMF CPTransportLayerInformation OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { NGRAN-TNLAssociationToRemoveItem-ExtIEs} } OPTIONAL +} + +NGRAN-TNLAssociationToRemoveItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +} + +NGRANTraceID ::= OCTET STRING (SIZE(8)) + +NID ::= BIT STRING (SIZE(44)) + +NonDynamic5QIDescriptor ::= SEQUENCE { + fiveQI FiveQI, + priorityLevelQos PriorityLevelQos OPTIONAL, + averagingWindow AveragingWindow OPTIONAL, + maximumDataBurstVolume MaximumDataBurstVolume OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {NonDynamic5QIDescriptor-ExtIEs} } OPTIONAL, + ... +} + +NonDynamic5QIDescriptor-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-CNPacketDelayBudgetDL CRITICALITY ignore EXTENSION ExtendedPacketDelayBudget PRESENCE optional } | + { ID id-CNPacketDelayBudgetUL CRITICALITY ignore EXTENSION ExtendedPacketDelayBudget PRESENCE optional }, + ... +} + +NoPDUSessionIndication ::= ENUMERATED {true, ...} +``` + +NotAllowedTACs ::= SEQUENCE (SIZE(1..maxnoofAllowedAreas)) OF TAC + +NotificationCause ::= ENUMERATED { + fulfilled, + not-fulfilled, + ... +} + +NotificationControl ::= ENUMERATED { + notification-requested, + ... +} + +NPN-AccessInformation ::= CHOICE { + pNI-NPN-Access-Information      CellCAGList, + choice-Extensions                  ProtocolIE-SingleContainer { {NPN-AccessInformation-ExtIEs} } +} + +NPN-AccessInformation-ExtIEs NGAP-PROTOCOL-IES ::= { + ... +} + +NPN-MobilityInformation ::= CHOICE { + +``` + sNPN-MobilityInformation sNPN-MobilityInformation, + pNI-NPN-MobilityInformation pNI-NPN-MobilityInformation, + choice-Extensions ProtocolIE-SingleContainer { {NPN-MobilityInformation-ExtIEs} } +} + +NPN-MobilityInformation-ExtIEs NGAP-PROTOCOL-IES ::= { + ... +} + +NPN-PagingAssistanceInformation ::= CHOICE { + pNI-NPN-PagingAssistance Allowed-PNI-NPN-List, + choice-Extensions ProtocolIE-SingleContainer { {NPN-PagingAssistanceInformation-ExtIEs} } +} + +NPN-PagingAssistanceInformation-ExtIEs NGAP-PROTOCOL-IES ::= { + ... +} + +NPN-Support ::= CHOICE { + sNPN NID, + choice-Extensions ProtocolIE-SingleContainer { {NPN-Support-ExtIEs} } +} +``` + +``` +NPN-Support-ExtIEs NGAP-PROTOCOL-IES ::= { + ... +} + +NRCellIdentity ::= BIT STRING (SIZE(36)) + +NR-CGI ::= SEQUENCE { + pLMNIdentity PLMNIdentity, + nRCellIdentity NRCellIdentity, + iE-Extensions ProtocolExtensionContainer { {NR-CGI-ExtIEs} } OPTIONAL, + ... +} + +NR-CGI-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +NR-CGIList ::= SEQUENCE (SIZE(1..maxnoofCellsingNB)) OF NR-CGI + +NR-CGIListForWarning ::= SEQUENCE (SIZE(1..maxnoofCellIDforWarning)) OF NR-CGI + +NR-PagingeDRXInformation ::= SEQUENCE { +``` + +``` + nR-paging-eDRX-Cycle NR-Paging-eDRX-Cycle, + nR-paging-Time-Window NR-Paging-Time-Window OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {NR-PagingeDRXInformation-ExtIEs} } OPTIONAL, + ... +} + +NR-PagingeDRXInformation-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +NR-Paging-eDRX-Cycle ::= ENUMERATED { + hfquarter, hfhalf, hf1, hf2, hf4, hf8, hf16, + hf32, hf64, hf128, hf256, hf512, hf1024, + ... +} + +NR-Paging-Long-eDRX-Information-for-RRC-INACTIVE ::= SEQUENCE { + nR-paging-Long-eDRX-Cycle-for-RRC-INACTIVE NR-Paging-Long-eDRX-Cycle-for-RRC-INACTIVE, + nR-paging-Time-Window-for-RRC-INACTIVE NR-Paging-Time-Window-for-RRC-INACTIVE, + iE-Extensions ProtocolExtensionContainer { {NR-Paging-Long-eDRX-Information-for-RRC-INACTIVE-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +NR-Paging-Long-eDRX-Information-for-RRC-INACTIVE-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +NR-Paging-Long-eDRX-Cycle-for-RRC-INACTIVE ::= ENUMERATED { +``` + +``` + hf2, hf4, hf8, hf16, +``` + +``` + hf32, hf64, hf128, hf256, hf512, hf1024, +``` + +``` + ... +``` + +``` +} +``` + +``` +NR-Paging-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-Time-Window-for-RRC-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, + ... +} + +NREncryptionAlgorithms ::= BIT STRING (SIZE(16, ...)) + +NRIntegrityProtectionAlgorithms ::= BIT STRING (SIZE(16, ...)) + +NRMobilityHistoryReport ::= OCTET STRING + +NRPPa-PDU ::= OCTET STRING + +NRUERLReportContainer ::= OCTET STRING + +NRNTNTAInformation ::= SEQUENCE { + servingPLMN PLMNIdentity, + tACLListInNRNTN TACLListInNRNTN, + uELocationDerivedTACInNRNTN TAC OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { NRNTNTAInformation-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +NRNTNAIInformation-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +NumberOfBroadcasts ::= INTEGER (0..65535) +``` + +``` +NumberOfBroadcastsRequested ::= INTEGER (0..65535) +``` + +``` +NRARFCN ::= INTEGER (0.. maxNRARFCN) +``` + +``` +NRFrequencyBand ::= INTEGER (1..1024, ...) +``` + +``` +NRFrequencyBand-List ::= SEQUENCE (SIZE(1..maxnoofNRCellBands)) OF NRFrequencyBandItem +``` + +``` +NRFrequencyBandItem ::= SEQUENCE { + nr-frequency-band NRFrequencyBand, + iE-Extension ProtocolExtensionContainer { {NRFrequencyBandItem-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +NRFrequencyBandItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +} + +NRFrequencyInfo ::= SEQUENCE { +    nrARFCN              NRARFCN, +    frequencyBand-List   NRFrequencyBand-List, +    iE-Extension         ProtocolExtensionContainer { {NRFrequencyInfo-ExtIEs} } OPTIONAL, +    ... +} + +NRFrequencyInfo-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +    ... +} + +NR-PCI ::= INTEGER (0..1007, ...) + +NRV2XServicesAuthorized ::= SEQUENCE { +    vehicleUE            VehicleUE                                                          OPTIONAL, +    pedestrianUE         PedestrianUE                                                         OPTIONAL, +    iE-Extensions        ProtocolExtensionContainer { {NRV2XServicesAuthorized-ExtIEs} } OPTIONAL, +    ... +} + +NRV2XServicesAuthorized-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + +``` + ... +} + +VehicleUE ::= ENUMERATED { + authorized, + not-authorized, + ... +} + +PedestrianUE ::= ENUMERATED { + authorized, + not-authorized, + ... +} + +NRUESidelinkAggregateMaximumBitrate ::= SEQUENCE { + uESidelinkAggregateMaximumBitRate BitRate, + iE-Extensions ProtocolExtensionContainer { {NRUESidelinkAggregateMaximumBitrate-ExtIEs} } OPTIONAL, + ... +} + +NRUESidelinkAggregateMaximumBitrate-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +} + +NSAG-ID ::= INTEGER (0..255, ...) + +NR-A2X-ServicesAuthorized ::= SEQUENCE { + +uAV-UE ENUMERATED {authorized, not-authorized, ...} OPTIONAL, + +uAV-ControllerUE ENUMERATED {authorized, not-authorized, ...} OPTIONAL, + +iE-Extensions ProtocolExtensionContainer { {NR-A2X-ServicesAuthorized-ExtIEs} } OPTIONAL, + +... + +} + +NR-A2X-ServicesAuthorized-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + +... + +} + +-- O + +OnboardingSupport ::= ENUMERATED { + +true, + +... + +} + +OverloadAction ::= 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, + ... + } + +OverloadResponse ::= CHOICE { + overloadAction OverloadAction, + choice-Extensions ProtocolIE-SingleContainer { {OverloadResponse-ExtIEs} } +} + +OverloadResponse-ExtIEs NGAP-PROTOCOL-IES ::= { + ... +} + +OverloadStartNSSAIList ::= SEQUENCE (SIZE (1..maxnoofSliceItems)) OF OverloadStartNSSAIItem + +OverloadStartNSSAIItem ::= SEQUENCE { + sliceOverloadList SliceOverloadList, + sliceOverloadResponse OverloadResponse OPTIONAL, + sliceTrafficLoadReductionIndication TrafficLoadReductionIndication OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {OverloadStartNSSAIItem-ExtIEs} } OPTIONAL, +``` + +``` + ... +} + +OverloadStartNSSAItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- P + +PacketDelayBudget ::= INTEGER (0..1023, ...) + +PacketErrorRate ::= SEQUENCE { + pERScalar INTEGER (0..9, ...), + pERExponent INTEGER (0..9, ...), + iE-Extensions ProtocolExtensionContainer { {PacketErrorRate-ExtIEs} } OPTIONAL, + ... +} + +PacketErrorRate-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +PacketLossRate ::= INTEGER (0..1000, ...) +``` + +``` +PagingAssisDataforCEcapabUE ::= SEQUENCE { + eUTRA-CGI EUTRA-CGI, + coverageEnhancementLevel CoverageEnhancementLevel, + iE-Extensions ProtocolExtensionContainer { { PagingAssisDataforCEcapabUE-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +PagingAssisDataforCEcapabUE-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +PagingAttemptInformation ::= SEQUENCE { + pagingAttemptCount PagingAttemptCount, + intendedNumberOfPagingAttempts IntendedNumberOfPagingAttempts, + nextPagingAreaScope NextPagingAreaScope OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { PagingAttemptInformation-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +PagingAttemptInformation-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +PagingAttemptCount ::= INTEGER (1..16, ...) + +PagingCause ::= ENUMERATED { +    voice, +    ... +} + +PagingCauseIndicationForVoiceService ::= ENUMERATED { +    supported, +    ... +} + +PagingDRX ::= ENUMERATED { +    v32, +    v64, +    v128, +    v256, +    ... +} + +PagingOrigin ::= ENUMERATED { +    non-3gpp, + +``` + ... +} + +PagingPolicyDifferentiation ::= SEQUENCE { + pagingPolicyIndicator PagingPolicyIndicator OPTIONAL, + allocationAndRetentionPriority AllocationAndRetentionPriority OPTIONAL, + qosFlowIdentifier QosFlowIdentifier OPTIONAL, + pduSessionID PDUSessionID OPTIONAL, + fiveQI FiveQI OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { PagingPolicyDifferentiation-ExtIEs} } OPTIONAL, + ... +} + +PagingPolicyDifferentiation-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +PagingPolicyIndicator ::= INTEGER (0..7, ...) + +PagingPriority ::= ENUMERATED { + prioLevel1, + prioLevel2, + prioLevel3, +``` + +``` +prioLevel14, +prioLevel15, +prioLevel16, +prioLevel17, +prioLevel18, +... +} +``` + +``` +PagingProbabilityInformation ::= ENUMERATED { + p00, p05, p10, p15, p20, p25, p30, p35, p40, p45, p50, p55, p60, p65, p70, p75, p80, p85, p90, p95, p100, + ... +} +``` + +``` +ParentTimeSource ::= ENUMERATED {sync, ptp, gnss, atomicclock, terrestrialradio, serialtimecode, ntp, handset, other, ...} +``` + +``` +Partially-Allowed-NSSAI ::= SEQUENCE (SIZE(1.. maxnoofPartiallyAllowedS-NSSAIs)) OF SliceSupportItem +``` + +``` +PathSwitchRequestAcknowledgeTransfer ::= SEQUENCE { + uL-NGU-UP-TNLInformation UPTransportLayerInformation OPTIONAL, + securityIndication SecurityIndication OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {PathSwitchRequestAcknowledgeTransfer-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +PathSwitchRequestAcknowledgeTransfer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-AdditionalNGU-UP-TNLInformation CRITICALITY ignore EXTENSION UPTransportLayerInformationPairList PRESENCE optional }| + { ID id-RedundantUL-NGU-UP-TNLInformation CRITICALITY ignore EXTENSION UPTransportLayerInformation PRESENCE optional }| + { ID id-AdditionalRedundantNGU-UP-TNLInformation CRITICALITY ignore EXTENSION UPTransportLayerInformationPairList PRESENCE optional }| + { ID id-QosFlowParametersList CRITICALITY ignore EXTENSION QosFlowParametersList PRESENCE optional }, + ... +} +``` + +``` +PathSwitchRequestSetupFailedTransfer ::= SEQUENCE { + cause Cause, + iE-Extensions ProtocolExtensionContainer { {PathSwitchRequestSetupFailedTransfer-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +PathSwitchRequestSetupFailedTransfer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +PathSwitchRequestTransfer ::= SEQUENCE { + dL-NGU-UP-TNLInformation UPTransportLayerInformation, + dL-NGU-TNLInformationReused DL-NGU-TNLInformationReused OPTIONAL, + userPlaneSecurityInformation UserPlaneSecurityInformation OPTIONAL, +``` + +``` + + qosFlowAcceptedList QosFlowAcceptedList, + iE-Extensions ProtocolExtensionContainer { {PathSwitchRequestTransfer-ExtIEs} } OPTIONAL, + ... +} + +PathSwitchRequestTransfer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-AdditionalDLQosFlowPerTNLInformation CRITICALITY ignore EXTENSION QosFlowPerTNLInformationList PRESENCE optional }| + { ID id-RedundantDL-NGU-UP-TNLInformation CRITICALITY ignore EXTENSION UPTransportLayerInformation PRESENCE optional }| + { ID id-RedundantDL-NGU-TNLInformationReused CRITICALITY ignore EXTENSION DL-NGU-TNLInformationReused PRESENCE optional }| + { ID id-AdditionalRedundantDLQosFlowPerTNLInformation CRITICALITY ignore EXTENSION QosFlowPerTNLInformationList PRESENCE optional }| + { ID id-UsedRSNInformation CRITICALITY ignore EXTENSION RedundantPDUSessionInformation PRESENCE optional }| + { ID id-GlobalRANNodeID CRITICALITY ignore EXTENSION GlobalRANNodeID PRESENCE optional }| + { ID id-MBS-SupportIndicator CRITICALITY ignore EXTENSION MBS-SupportIndicator PRESENCE optional }| + { ID id-PDUSetbasedHandlingIndicator CRITICALITY ignore EXTENSION PDUSetbasedHandlingIndicator PRESENCE optional }, + ... +} + +PathSwitchRequestUnsuccessfulTransfer ::= SEQUENCE { + cause Cause, + iE-Extensions ProtocolExtensionContainer { {PathSwitchRequestUnsuccessfulTransfer-ExtIEs} } OPTIONAL, + ... +} + +``` + +``` +PathSwitchRequestUnsuccessfulTransfer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +PC5QoSParameters ::= SEQUENCE { + pc5QoSFlowList PC5QoSFlowList, + pc5LinkAggregateBitRates BitRate OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { PC5QoSParameters-ExtIEs} } OPTIONAL, + ... +} + +PC5QoSParameters-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +PC5QoSFlowList ::= SEQUENCE (SIZE(1..maxnoofPC5QoSFlows)) OF PC5QoSFlowItem + +PC5QoSFlowItem ::= SEQUENCE { + pQI FiveQI, + pc5FlowBitRates PC5FlowBitRates OPTIONAL, + range Range OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { PC5QoSFlowItem-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +} +``` + +``` +PC5QoSFlowItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +PC5FlowBitRates ::= SEQUENCE { +``` + +``` + guaranteedFlowBitRate BitRate, +``` + +``` + maximumFlowBitRate BitRate, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { PC5FlowBitRates-ExtIEs} } OPTIONAL, +``` + +``` + ... +``` + +``` +} +``` + +``` +PC5FlowBitRates-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +PCIListForMDT ::= SEQUENCE (SIZE(1.. maxnoofNeighPCIforMDT)) OF NR-PCI +``` + +``` +PrivacyIndicator ::= ENUMERATED { +``` + +``` + immediate-MDT, +``` + +``` + logged-MDT, +``` + +``` + ... +} + +PDUSessionAggregateMaximumBitRate ::= SEQUENCE { + pDUSessionAggregateMaximumBitRateDL BitRate, + pDUSessionAggregateMaximumBitRateUL BitRate, + iE-Extensions ProtocolExtensionContainer { {PDUSessionAggregateMaximumBitRate-ExtIEs} } OPTIONAL, + ... +} + +PDUSessionAggregateMaximumBitRate-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +PDUSessionID ::= INTEGER (0..255) + +PDUSessionPairID ::= INTEGER (0..255, ...) + +PDUSessionResourceAdmittedList ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourceAdmittedItem + +PDUSessionResourceAdmittedItem ::= SEQUENCE { + pDUSessionID pDUSessionID, + handoverRequestAcknowledgeTransfer OCTET STRING (CONTAINING HandoverRequestAcknowledgeTransfer), +} +``` + +``` + iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceAdmittedItem-ExtIEs} } OPTIONAL, + ... +} + +PDUSessionResourceAdmittedItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +PDUSessionResourceFailedToModifyListModCfm ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourceFailedToModifyItemModCfm + +PDUSessionResourceFailedToModifyItemModCfm ::= SEQUENCE { + pDUSessionID pDUSessionID, + pDUSessionResourceModifyIndicationUnsuccessfulTransfer OCTET STRING (CONTAINING PDUSessionResourceModifyIndicationUnsuccessfulTransfer), + iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceFailedToModifyItemModCfm-ExtIEs} } OPTIONAL, + ... +} + +PDUSessionResourceFailedToModifyItemModCfm-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +PDUSessionResourceFailedToModifyListModRes ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourceFailedToModifyItemModRes +``` + +``` +PDUSessionResourceFailedToModifyItemModRes ::= SEQUENCE { + pDUSessionID pDUSessionID, + pDUSessionResourceModifyUnsuccessfulTransfer OCTET STRING (CONTAINING PDUSessionResourceModifyUnsuccessfulTransfer), + iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceFailedToModifyItemModRes-ExtIEs} } OPTIONAL, + ... +} + +PDUSessionResourceFailedToModifyItemModRes-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +PDUSessionResourceFailedToResumeListRESReq ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourceFailedToResumeItemRESReq + +PDUSessionResourceFailedToResumeItemRESReq ::= SEQUENCE { + pDUSessionID pDUSessionID, + cause Cause, + iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceFailedToResumeItemRESReq-ExtIEs} } OPTIONAL, + ... +} + +PDUSessionResourceFailedToResumeItemRESReq-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +PDUSessionResourceFailedToResumeListRESRes ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourceFailedToResumeItemRESRes +``` + +``` +PDUSessionResourceFailedToResumeItemRESRes ::= SEQUENCE { + pDUSessionID pDUSessionID, + cause Cause, + iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceFailedToResumeItemRESRes-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +PDUSessionResourceFailedToResumeItemRESRes-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +PDUSessionResourceFailedToSetupListCxtFail ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourceFailedToSetupItemCxtFail +``` + +``` +PDUSessionResourceFailedToSetupItemCxtFail ::= SEQUENCE { + pDUSessionID pDUSessionID, + pDUSessionResourceSetupUnsuccessfulTransfer OCTET STRING (CONTAINING PDUSessionResourceSetupUnsuccessfulTransfer), + iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceFailedToSetupItemCxtFail-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +PDUSessionResourceFailedToSetupItemCxtFail-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +PDUSessionResourceFailedToSetupListCxtRes ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourceFailedToSetupItemCxtRes + +PDUSessionResourceFailedToSetupItemCxtRes ::= SEQUENCE { + pDUSessionID pDUSessionID, + pDUSessionResourceSetupUnsuccessfulTransfer OCTET STRING (CONTAINING PDUSessionResourceSetupUnsuccessfulTransfer), + iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceFailedToSetupItemCxtRes-ExtIEs} } OPTIONAL, + ... +} + +PDUSessionResourceFailedToSetupItemCxtRes-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +PDUSessionResourceFailedToSetupListHOAck ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourceFailedToSetupItemHOAck + +PDUSessionResourceFailedToSetupItemHOAck ::= SEQUENCE { + pDUSessionID pDUSessionID, + handoverResourceAllocationUnsuccessfulTransfer OCTET STRING (CONTAINING HandoverResourceAllocationUnsuccessfulTransfer), +} +``` + +``` + iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceFailedToSetupItemHOAck-ExtIEs} } OPTIONAL, + ... +} + +PDUSessionResourceFailedToSetupItemHOAck-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +PDUSessionResourceFailedToSetupListPSReq ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourceFailedToSetupItemPSReq + +PDUSessionResourceFailedToSetupItemPSReq ::= SEQUENCE { + pDUSessionID pDUSessionID, + pathSwitchRequestSetupFailedTransfer OCTET STRING (CONTAINING PathSwitchRequestSetupFailedTransfer), + iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceFailedToSetupItemPSReq-ExtIEs} } OPTIONAL, + ... +} + +PDUSessionResourceFailedToSetupItemPSReq-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +PDUSessionResourceFailedToSetupListSURes ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourceFailedToSetupItemSURes +``` + +``` +PDUSessionResourceFailedToSetupItemSURes ::= SEQUENCE { + pDUSessionID pDUSessionID, + pDUSessionResourceSetupUnsuccessfulTransfer OCTET STRING (CONTAINING PDUSessionResourceSetupUnsuccessfulTransfer), + iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceFailedToSetupItemSURes-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +PDUSessionResourceFailedToSetupItemSURes-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +PDUSessionResourceHandoverList ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourceHandoverItem +``` + +``` +PDUSessionResourceHandoverItem ::= SEQUENCE { + pDUSessionID pDUSessionID, + handoverCommandTransfer OCTET STRING (CONTAINING HandoverCommandTransfer), + iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceHandoverItem-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +PDUSessionResourceHandoverItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +PDUSessionResourceInformationList ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourceInformationItem +``` + +``` +PDUSessionResourceInformationItem ::= SEQUENCE { + pDUSessionID pDUSessionID, + qosFlowInformationList QosFlowInformationList, + dRBsToQosFlowsMappingList DRBsToQosFlowsMappingList OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceInformationItem-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +PDUSessionResourceInformationItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +PDUSessionResourceListCxtRelCpl ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourceItemCxtRelCpl +``` + +``` +PDUSessionResourceItemCxtRelCpl ::= SEQUENCE { + pDUSessionID pDUSessionID, + iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceItemCxtRelCpl-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +PDUSessionResourceItemCxtRelCpl-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-PDUSessionResourceReleaseResponseTransfer CRITICALITY ignore EXTENSION OCTET STRING (CONTAINING + PDUSessionResourceReleaseResponseTransfer) PRESENCE optional }, + ... +} + +PDUSessionResourceListCxtRelReq ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourceItemCxtRelReq + +PDUSessionResourceItemCxtRelReq ::= SEQUENCE { + pDUSessionID pDUSessionID, + iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceItemCxtRelReq-ExtIEs} } OPTIONAL, + ... +} + +PDUSessionResourceItemCxtRelReq-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +PDUSessionResourceListHORqd ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourceItemHORqd + +PDUSessionResourceItemHORqd ::= SEQUENCE { + pDUSessionID pDUSessionID, + handoverRequiredTransfer OCTET STRING (CONTAINING HandoverRequiredTransfer), +} +``` + +``` + iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceItemHORqd-ExtIEs} } OPTIONAL, + ... +} + +PDUSessionResourceItemHORqd-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +PDUSessionResourceModifyConfirmTransfer ::= SEQUENCE { + qosFlowModifyConfirmList QosFlowModifyConfirmList, + uLNGU-UP-TNLInformation UPTransportLayerInformation, + additionalNG-UUPTNLInformation UPTransportLayerInformationPairList OPTIONAL, + qosFlowFailedToModifyList QosFlowListWithCause OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceModifyConfirmTransfer-ExtIEs} } OPTIONAL, + ... +} + +PDUSessionResourceModifyConfirmTransfer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-RedundantUL-NGU-UP-TNLInformation CRITICALITY ignore EXTENSION UPTransportLayerInformation PRESENCE optional }| + { ID id-AdditionalRedundantNGU-UP-TNLInformation CRITICALITY ignore EXTENSION UPTransportLayerInformationPairList PRESENCE optional }, + ... +} +``` + +``` + +PDUSessionResourceModifyIndicationUnsuccessfulTransfer ::= SEQUENCE { + cause Cause, + iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceModifyIndicationUnsuccessfulTransfer-ExtIEs} } OPTIONAL, + ... +} + +``` + +``` + +PDUSessionResourceModifyIndicationUnsuccessfulTransfer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +``` + +PDUSessionResourceModifyRequestTransfer ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {PDUSessionResourceModifyRequestTransferIEs} }, + ... +} + +``` + +``` + +PDUSessionResourceModifyRequestTransferIEs NGAP-PROTOCOL-IES ::= { + { ID id-PDUSessionAggregateMaximumBitRate CRITICALITY reject TYPE PDUSessionAggregateMaximumBitRate PRESENCE optional } | + { ID id-UL-NGU-UP-TNLModifyList CRITICALITY reject TYPE UL-NGU-UP-TNLModifyList PRESENCE optional } | + { ID id-NetworkInstance CRITICALITY reject TYPE NetworkInstance PRESENCE optional } | + { ID id-QosFlowAddOrModifyRequestList CRITICALITY reject TYPE QosFlowAddOrModifyRequestList PRESENCE optional } | + { ID id-QosFlowToReleaseList CRITICALITY reject TYPE QosFlowListWithCause PRESENCE optional } | + { ID id-AdditionalUL-NGU-UP-TNLInformation CRITICALITY reject TYPE UPTransportLayerInformationList PRESENCE optional } | + { ID id-CommonNetworkInstance CRITICALITY ignore TYPE CommonNetworkInstance PRESENCE optional } | +} + +``` + +``` + + { ID id-AdditionalRedundantUL-NGU-UP-TNLInformation CRITICALITY ignore TYPE UPTransportLayerInformationList PRESENCE optional }| + { ID id-RedundantCommonNetworkInstance CRITICALITY ignore TYPE CommonNetworkInstance PRESENCE optional }| + { ID id-RedundantUL-NGU-UP-TNLInformation CRITICALITY ignore TYPE UPTransportLayerInformation PRESENCE optional }| + { ID id-SecurityIndication CRITICALITY ignore TYPE SecurityIndication PRESENCE optional }| + { ID id-MBSSessionSetuporModifyRequestList CRITICALITY ignore TYPE MBSSessionSetuporModifyRequestList PRESENCE optional }| + { ID id-MBSSessionToReleaseList CRITICALITY ignore TYPE MBSSessionToReleaseList PRESENCE optional }, + ... +} + +PDUSessionResourceModifyResponseTransfer ::= SEQUENCE { + dL-NGU-UP-TNLInformation UPTransportLayerInformation OPTIONAL, + uL-NGU-UP-TNLInformation UPTransportLayerInformation OPTIONAL, + qosFlowAddOrModifyResponseList QosFlowAddOrModifyResponseList OPTIONAL, + additionalDLQosFlowPerTNLInformation QosFlowPerTNLInformationList OPTIONAL, + qosFlowFailedToAddOrModifyList QosFlowListWithCause OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceModifyResponseTransfer-ExtIEs} } OPTIONAL, + ... +} + +PDUSessionResourceModifyResponseTransfer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-AdditionalNGU-UP-TNLInformation CRITICALITY ignore EXTENSION UPTransportLayerInformationPairList PRESENCE optional }| + { ID id-RedundantDL-NGU-UP-TNLInformation CRITICALITY ignore EXTENSION UPTransportLayerInformation PRESENCE optional }| + { ID id-RedundantUL-NGU-UP-TNLInformation CRITICALITY ignore EXTENSION UPTransportLayerInformation PRESENCE optional }| +} + +``` + +``` + + { ID id-AdditionalRedundantDLQosFlowPerTNLInformation CRITICALITY ignore EXTENSION QosFlowPerTNLInformationList PRESENCE optional }| + { ID id-AdditionalRedundantNGU-UP-TNLInformation CRITICALITY ignore EXTENSION UPTransportLayerInformationPairList PRESENCE optional }| + { ID id-SecondaryRATUsageInformation CRITICALITY ignore EXTENSION SecondaryRATUsageInformation PRESENCE optional }| + { ID id-MBS-SupportIndicator CRITICALITY ignore EXTENSION MBS-SupportIndicator PRESENCE optional }| + { ID id-MBSSessionSetuporModifyResponseList CRITICALITY ignore EXTENSION MBSSessionSetupResponseList PRESENCE optional }| + { ID id-MBSSessionFailedtoSetuporModifyList CRITICALITY ignore EXTENSION MBSSessionFailedtoSetupList PRESENCE optional }| + { ID id-ECNMarkingorCongestionInformationReportingStatus CRITICALITY ignore EXTENSION ECNMarkingorCongestionInformationReportingStatus + PRESENCE optional }| + { ID id-PDUSetbasedHandlingIndicator CRITICALITY ignore EXTENSION PDUSetbasedHandlingIndicator PRESENCE optional }, + ... +} + +``` + +``` + +PDUSessionResourceModifyIndicationTransfer ::= SEQUENCE { + dLQosFlowPerTNLInformation QosFlowPerTNLInformation, + additionalDLQosFlowPerTNLInformation QosFlowPerTNLInformationList OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceModifyIndicationTransfer-ExtIEs} } OPTIONAL, + ... +} + +``` + +``` + +PDUSessionResourceModifyIndicationTransfer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-SecondaryRATUsageInformation CRITICALITY ignore EXTENSION SecondaryRATUsageInformation PRESENCE optional }| + { ID id-SecurityResult CRITICALITY ignore EXTENSION SecurityResult PRESENCE optional }| + { ID id-RedundantDLQosFlowPerTNLInformation CRITICALITY ignore EXTENSION QosFlowPerTNLInformation PRESENCE optional }| +} + +``` + +``` +{ ID id-AdditionalRedundantDLQosFlowPerTNLInformation CRITICALITY ignore EXTENSION QosFlowPerTNLInformationList PRESENCE optional }| +{ ID id-GlobalRANNodeID CRITICALITY ignore EXTENSION GlobalRANNodeID PRESENCE optional }, +... +} +``` + +``` +PDUSessionResourceModifyListModCfm ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourceModifyItemModCfm +``` + +``` +PDUSessionResourceModifyItemModCfm ::= SEQUENCE { + pDUSessionID PDUSessionID, + pDUSessionResourceModifyConfirmTransfer OCTET STRING (CONTAINING PDUSessionResourceModifyConfirmTransfer), + iE-Extensions ProtocolExtensionContainer { PDUSessionResourceModifyItemModCfm-ExtIEs } OPTIONAL, + ... +} +``` + +``` +PDUSessionResourceModifyItemModCfm-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +PDUSessionResourceModifyListModInd ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourceModifyItemModInd +``` + +``` +PDUSessionResourceModifyItemModInd ::= SEQUENCE { + pDUSessionID PDUSessionID, + pDUSessionResourceModifyIndicationTransfer OCTET STRING (CONTAINING PDUSessionResourceModifyIndicationTransfer), +} +``` + +``` + iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceModifyItemModInd-ExtIEs} } OPTIONAL, + ... +} + +PDUSessionResourceModifyItemModInd-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +PDUSessionResourceModifyListModReq ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourceModifyItemModReq + +PDUSessionResourceModifyItemModReq ::= SEQUENCE { + pDUSessionID pDUSessionID, + nAS-PDU NAS-PDU OPTIONAL, + pDUSessionResourceModifyRequestTransfer OCTET STRING (CONTAINING PDUSessionResourceModifyRequestTransfer), + iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceModifyItemModReq-ExtIEs} } OPTIONAL, + ... +} + +PDUSessionResourceModifyItemModReq-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-S-NSSAI CRITICALITY reject EXTENSION S-NSSAI PRESENCE optional }| + { ID id-PduSessionExpectedUEActivityBehaviour CRITICALITY ignore EXTENSION ExpectedUEActivityBehaviour PRESENCE optional }, + ... +} +``` + +PDUSessionResourceModifyListModRes ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourceModifyItemModRes + +PDUSessionResourceModifyItemModRes ::= SEQUENCE { + +    pDUSessionID                                    pDUSessionID, +    pDUSessionResourceModifyResponseTransfer    OCTET STRING (CONTAINING PDUSessionResourceModifyResponseTransfer), +    iE-Extensions    ProtocolExtensionContainer { {PDUSessionResourceModifyItemModRes-ExtIEs} }    OPTIONAL, +    ... +} + +PDUSessionResourceModifyItemModRes-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + +    ... +} + +PDUSessionResourceModifyUnsuccessfulTransfer ::= SEQUENCE { + +    cause                            Cause, +    criticalityDiagnostics        CriticalityDiagnostics                                    OPTIONAL, +    iE-Extensions    ProtocolExtensionContainer { {PDUSessionResourceModifyUnsuccessfulTransfer-ExtIEs} }    OPTIONAL, +    ... +} + +PDUSessionResourceModifyUnsuccessfulTransfer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + +    ... +} + +``` +} + +PDUSessionResourceNotifyList ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourceNotifyItem + +PDUSessionResourceNotifyItem ::= SEQUENCE { + pDUSessionID pDUSessionID, + pDUSessionResourceNotifyTransfer OCTET STRING (CONTAINING PDUSessionResourceNotifyTransfer), + iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceNotifyItem-ExtIEs} } OPTIONAL, + ... +} + +PDUSessionResourceNotifyItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +PDUSessionResourceNotifyReleasedTransfer ::= SEQUENCE { + cause Cause, + iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceNotifyReleasedTransfer-ExtIEs} } OPTIONAL, + ... +} + +PDUSessionResourceNotifyReleasedTransfer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-SecondaryRATUsageInformation CRITICALITY ignore EXTENSION SecondaryRATUsageInformation PRESENCE optional }, +``` + +``` + ... +} + +PDUSessionResourceNotifyTransfer ::= SEQUENCE { + qosFlowNotifyList QosFlowNotifyList OPTIONAL, + qosFlowReleasedList QosFlowListWithCause OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceNotifyTransfer-ExtIEs} } OPTIONAL, + ... +} + +PDUSessionResourceNotifyTransfer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-SecondaryRATUsageInformation CRITICALITY ignore EXTENSION SecondaryRATUsageInformation PRESENCE optional }| + { ID id-QosFlowFeedbackList CRITICALITY ignore EXTENSION QosFlowFeedbackList PRESENCE optional }, + ... +} + +PDUSessionResourceReleaseCommandTransfer ::= SEQUENCE { + cause Cause, + iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceReleaseCommandTransfer-ExtIEs} } OPTIONAL, + ... +} + +PDUSessionResourceReleaseCommandTransfer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +``` + +``` +{ ID id-QosFlowAdditionalInfoList CRITICALITY ignore EXTENSION QosFlowAdditionalInfoListRelCom PRESENCE optional }, +... +} + +PDUSessionResourceReleasedListNot ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourceReleasedItemNot + +PDUSessionResourceReleasedItemNot ::= SEQUENCE { + pDUSessionID pDUSessionID, + pDUSessionResourceNotifyReleasedTransfer OCTET STRING (CONTAINING PDUSessionResourceNotifyReleasedTransfer), + iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceReleasedItemNot-ExtIEs} } OPTIONAL, + ... +} + +PDUSessionResourceReleasedItemNot-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +PDUSessionResourceReleasedListPSAck ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourceReleasedItemPSAck + +PDUSessionResourceReleasedItemPSAck ::= SEQUENCE { + pDUSessionID pDUSessionID, + pathSwitchRequestUnsuccessfulTransfer OCTET STRING (CONTAINING PathSwitchRequestUnsuccessfulTransfer), + iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceReleasedItemPSAck-ExtIEs} } OPTIONAL, +``` + +``` + ... +} + +PDUSessionResourceReleasedItemPSAck-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +PDUSessionResourceReleasedListPSFail ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourceReleasedItemPSFail + +PDUSessionResourceReleasedItemPSFail ::= SEQUENCE { + pDUSessionID pDUSessionID, + pathSwitchRequestUnsuccessfulTransfer OCTET STRING (CONTAINING PathSwitchRequestUnsuccessfulTransfer), + iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceReleasedItemPSFail-ExtIEs} } OPTIONAL, + ... +} + +PDUSessionResourceReleasedItemPSFail-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +PDUSessionResourceReleasedListRelRes ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourceReleasedItemRelRes + +PDUSessionResourceReleasedItemRelRes ::= SEQUENCE { +``` + +``` + pDUSessionID pDUSessionID, + pDUSessionResourceReleaseResponseTransfer OCTET STRING (CONTAINING pDUSessionResourceReleaseResponseTransfer), + iE-Extensions ProtocolExtensionContainer { {pDUSessionResourceReleasedItemRelRes-ExtIEs} } OPTIONAL, + ... +} + +pDUSessionResourceReleasedItemRelRes-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +pDUSessionResourceReleaseResponseTransfer ::= SEQUENCE { + iE-Extensions ProtocolExtensionContainer { {pDUSessionResourceReleaseResponseTransfer-ExtIEs} } OPTIONAL, + ... +} + +pDUSessionResourceReleaseResponseTransfer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-SecondaryRATUsageInformation CRITICALITY ignore EXTENSION SecondaryRATUsageInformation PRESENCE optional }| + { ID id-QosFlowAdditionalInfoList CRITICALITY ignore EXTENSION QosFlowAdditionalInfoListRelRes PRESENCE optional }, + ... +} + +pDUSessionResourceResumeListRESReq ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF pDUSessionResourceResumeItemRESReq +``` + +``` +PDUSessionResourceResumeItemRESReq ::= SEQUENCE { + pDUSessionID pDUSessionID, + uEContextResumeRequestTransfer OCTET STRING (CONTAINING UEContextResumeRequestTransfer), + iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceResumeItemRESReq-ExtIEs} } OPTIONAL, + ... +} + +PDUSessionResourceResumeItemRESReq-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +PDUSessionResourceResumeListRESRes ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourceResumeItemRESRes + +PDUSessionResourceResumeItemRESRes ::= SEQUENCE { + pDUSessionID pDUSessionID, + uEContextResumeResponseTransfer OCTET STRING (CONTAINING UEContextResumeResponseTransfer), + iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceResumeItemRESRes-ExtIEs} } OPTIONAL, + ... +} + +PDUSessionResourceResumeItemRESRes-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +PDUSessionResourceSecondaryRATUsageList ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourceSecondaryRATUsageItem + +PDUSessionResourceSecondaryRATUsageItem ::= SEQUENCE { +    pDUSessionID                            pDUSessionID, +    secondaryRATDataUsageReportTransfer    OCTET STRING (CONTAINING SecondaryRATDataUsageReportTransfer), +    iE-Extensions            ProtocolExtensionContainer { {PDUSessionResourceSecondaryRATUsageItem-ExtIEs} } OPTIONAL, +    ... +} + +PDUSessionResourceSecondaryRATUsageItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +    ... +} + +PDUSessionResourceSetupListCxtReq ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourceSetupItemCxtReq + +PDUSessionResourceSetupItemCxtReq ::= SEQUENCE { +    pDUSessionID                            pDUSessionID, +    nAS-PDU                                NAS-PDU                                        OPTIONAL, +    s-NSSAI                                S-NSSAI, +    pDUSessionResourceSetupRequestTransfer    OCTET STRING (CONTAINING PDUSessionResourceSetupRequestTransfer), +    iE-Extensions            ProtocolExtensionContainer { {PDUSessionResourceSetupItemCxtReq-ExtIEs} } OPTIONAL, +    ... +} + +``` +} + +PDUSessionResourceSetupItemCxtReq-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ID id-PduSessionExpectedUEActivityBehaviour CRITICALITY ignore EXTENSION ExpectedUEActivityBehaviour PRESENCE optional }, + ... +} + +PDUSessionResourceSetupListCxtRes ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourceSetupItemCxtRes + +PDUSessionResourceSetupItemCxtRes ::= SEQUENCE { + pDUSessionID pDUSessionID, + pDUSessionResourceSetupResponseTransfer OCTET STRING (CONTAINING PDUSessionResourceSetupResponseTransfer), + iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceSetupItemCxtRes-ExtIEs} } OPTIONAL, + ... +} + +PDUSessionResourceSetupItemCxtRes-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +PDUSessionResourceSetupListHOReq ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourceSetupItemHOReq + +PDUSessionResourceSetupItemHOReq ::= SEQUENCE { +``` + +``` + pDUSessionID PDUSessionID, + s-NSSAI S-NSSAI, + handoverRequestTransfer OCTET STRING (CONTAINING PDUSessionResourceSetupRequestTransfer), + iE-Extensions ProtocolExtensionContainer { PDUSessionResourceSetupItemHOReq-ExtIEs } OPTIONAL, + ... +} + +PDUSessionResourceSetupItemHOReq-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-PduSessionExpectedUEActivityBehaviour CRITICALITY ignore EXTENSION ExpectedUEActivityBehaviour PRESENCE optional }, + ... +} + +PDUSessionResourceSetupListSUReq ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourceSetupItemSUReq + +PDUSessionResourceSetupItemSUReq ::= SEQUENCE { + pDUSessionID PDUSessionID, + pDUSessionNAS-PDU NAS-PDU OPTIONAL, + s-NSSAI S-NSSAI, + pDUSessionResourceSetupRequestTransfer OCTET STRING (CONTAINING PDUSessionResourceSetupRequestTransfer), + iE-Extensions ProtocolExtensionContainer { PDUSessionResourceSetupItemSUReq-ExtIEs } OPTIONAL, + ... +} +``` + +``` +PDUSessionResourceSetupItemSUReq-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-PduSessionExpectedUEActivityBehaviour CRITICALITY ignore EXTENSION ExpectedUEActivityBehaviour PRESENCE optional }, + ... +} + +PDUSessionResourceSetupListSURes ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourceSetupItemSURes + +PDUSessionResourceSetupItemSURes ::= SEQUENCE { + pDUSessionID pDUSessionID, + pDUSessionResourceSetupResponseTransfer OCTET STRING (CONTAINING PDUSessionResourceSetupResponseTransfer), + iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceSetupItemSURes-ExtIEs} } OPTIONAL, + ... +} + +PDUSessionResourceSetupItemSURes-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +PDUSessionResourceSetupRequestTransfer ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {PDUSessionResourceSetupRequestTransferIEs} }, + ... +} +``` + +``` + +PDUSessionResourceSetupRequestTransferIEs NGAP-PROTOCOL-IEs ::= { + { ID id-PDUSessionAggregateMaximumBitRate CRITICALITY reject TYPE PDUSessionAggregateMaximumBitRate PRESENCE optional }| + { ID id-UL-NGU-UP-TNLInformation CRITICALITY reject TYPE UPTransportLayerInformation PRESENCE mandatory }| + { ID id-AdditionalUL-NGU-UP-TNLInformation CRITICALITY reject TYPE UPTransportLayerInformationList PRESENCE optional }| + { ID id-DataForwardingNotPossible CRITICALITY reject TYPE DataForwardingNotPossible PRESENCE optional }| + { ID id-PDUSessionType CRITICALITY reject TYPE PDUSessionType PRESENCE mandatory }| + { ID id-SecurityIndication CRITICALITY reject TYPE SecurityIndication PRESENCE optional }| + { ID id-NetworkInstance CRITICALITY reject TYPE NetworkInstance PRESENCE optional }| + { ID id-QosFlowSetupRequestList CRITICALITY reject TYPE QosFlowSetupRequestList PRESENCE mandatory }| + { ID id-CommonNetworkInstance CRITICALITY ignore TYPE CommonNetworkInstance PRESENCE optional }| + { ID id-DirectForwardingPathAvailability CRITICALITY ignore TYPE DirectForwardingPathAvailability PRESENCE optional }| + { ID id-RedundantUL-NGU-UP-TNLInformation CRITICALITY ignore TYPE UPTransportLayerInformation PRESENCE optional }| + { ID id-AdditionalRedundantUL-NGU-UP-TNLInformation CRITICALITY ignore TYPE UPTransportLayerInformationList PRESENCE optional }| + { ID id-RedundantCommonNetworkInstance CRITICALITY ignore TYPE CommonNetworkInstance PRESENCE optional }| + { ID id-RedundantPDUSessionInformation CRITICALITY ignore TYPE RedundantPDUSessionInformation PRESENCE optional }| + { ID id-MBSSessionSetupRequestList CRITICALITY ignore TYPE MBSSessionSetupRequestList PRESENCE optional }| + { ID id-DownlinkTLContainer CRITICALITY ignore TYPE TLContainer PRESENCE optional }, + ... +} + +``` + +``` + +PDUSessionResourceSetupResponseTransfer ::= SEQUENCE { + dLQosFlowPerTNLInformation QosFlowPerTNLInformation, + additionalDLQosFlowPerTNLInformation QosFlowPerTNLInformationList OPTIONAL, +} + +``` + +``` + +securityResult SecurityResult OPTIONAL, +qosFlowFailedToSetupList QosFlowListWithCause OPTIONAL, +iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceSetupResponseTransfer-ExtIEs} } OPTIONAL, +... +} + +PDUSessionResourceSetupResponseTransfer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + + { ID id-RedundantDLQosFlowPerTNLInformation CRITICALITY ignore EXTENSION QosFlowPerTNLInformation PRESENCE optional }| + { ID id-AdditionalRedundantDLQosFlowPerTNLInformation CRITICALITY ignore EXTENSION QosFlowPerTNLInformationList PRESENCE optional }| + { ID id-UsedRSNInformation CRITICALITY ignore EXTENSION RedundantPDUSessionInformation PRESENCE optional }| + { ID id-GlobalRANNodeID CRITICALITY ignore EXTENSION GlobalRANNodeID PRESENCE optional }| + { ID id-MBS-SupportIndicator CRITICALITY ignore EXTENSION MBS-SupportIndicator PRESENCE optional }| + { ID id-MBSSessionSetupResponseList CRITICALITY ignore EXTENSION MBSSessionSetupResponseList PRESENCE optional }| + { ID id-MBSSessionFailedtoSetupList CRITICALITY ignore EXTENSION MBSSessionFailedtoSetupList PRESENCE optional }| + { ID id-QoSFlowTSCList CRITICALITY ignore EXTENSION QoSFlowTSCList PRESENCE optional }| + { ID id-UplinkTLContainer CRITICALITY ignore EXTENSION TLContainer PRESENCE optional }| + { ID id-ECNMarkingorCongestionInformationReportingStatus CRITICALITY ignore EXTENSION ECNMarkingorCongestionInformationReportingStatus PRESENCE optional }| + { ID id-PDUSetbasedHandlingIndicator CRITICALITY ignore EXTENSION PDUSetbasedHandlingIndicator PRESENCE optional }, + ... +} + +PDUSessionResourceSetupUnsuccessfulTransfer ::= SEQUENCE { + +``` + +``` + cause Cause, + criticalityDiagnostics CriticalityDiagnostics OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceSetupUnsuccessfulTransfer-ExtIEs} } OPTIONAL, + ... +} + +PDUSessionResourceSetupUnsuccessfulTransfer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +PDUSessionResourceSuspendListSUSReq ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourceSuspendItemSUSReq + +PDUSessionResourceSuspendItemSUSReq ::= SEQUENCE { + pDUSessionID PDUSessionID, + uEContextSuspendRequestTransfer OCTET STRING (CONTAINING UEContextSuspendRequestTransfer), + iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceSuspendItemSUSReq-ExtIEs} } OPTIONAL, + ... +} + +PDUSessionResourceSuspendItemSUSReq-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +PDUSessionResourceSwitchedList ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourceSwitchedItem + +PDUSessionResourceSwitchedItem ::= SEQUENCE { + +    pDUSessionID                            pDUSessionID, +    pathSwitchRequestAcknowledgeTransfer    OCTET STRING (CONTAINING PathSwitchRequestAcknowledgeTransfer), +    iE-Extensions    ProtocolExtensionContainer { { PDUSessionResourceSwitchedItem-ExtIEs} } OPTIONAL, +    ... +} + +PDUSessionResourceSwitchedItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + +    { ID id-PduSessionExpectedUEActivityBehaviour    CRITICALITY ignore    EXTENSION ExpectedUEActivityBehaviour PRESENCE optional }, +    ... +} + +PDUSessionResourceToBeSwitchedDLList ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourceToBeSwitchedDLItem + +PDUSessionResourceToBeSwitchedDLItem ::= SEQUENCE { + +    pDUSessionID                            pDUSessionID, +    pathSwitchRequestTransfer    OCTET STRING (CONTAINING PathSwitchRequestTransfer), +    iE-Extensions    ProtocolExtensionContainer { { PDUSessionResourceToBeSwitchedDLItem-ExtIEs} } OPTIONAL, +    ... +} + +``` +PDUSessionResourceToBeSwitchedDLItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +PDUSessionResourceToReleaseListHOCmd ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourceToReleaseItemHOCmd + +PDUSessionResourceToReleaseItemHOCmd ::= SEQUENCE { + pDUSessionID pDUSessionID, + handoverPreparationUnsuccessfulTransfer OCTET STRING (CONTAINING HandoverPreparationUnsuccessfulTransfer), + iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceToReleaseItemHOCmd-ExtIEs} } OPTIONAL, + ... +} + +PDUSessionResourceToReleaseItemHOCmd-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +PDUSessionResourceToReleaseListRelCmd ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourceToReleaseItemRelCmd + +PDUSessionResourceToReleaseItemRelCmd ::= SEQUENCE { + pDUSessionID pDUSessionID, + pDUSessionResourceReleaseCommandTransfer OCTET STRING (CONTAINING PDUSessionResourceReleaseCommandTransfer), + iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceToReleaseItemRelCmd-ExtIEs} } OPTIONAL, +``` + +``` + ... +} + +PDUSessionResourceToReleaseItemRelCmd-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +PDUSessionType ::= ENUMERATED { + ipv4, + ipv6, + ipv4v6, + ethernet, + unstructured, + ... +} + +PDUSessionUsageReport ::= SEQUENCE { + rATType ENUMERATED {nr, eutra, ..., nr-unlicensed, e-utra-unlicensed}, + pDUSessionTimedReportList VolumeTimedReportList, + iE-Extensions ProtocolExtensionContainer { {PDUSessionUsageReport-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +PDUSessionUsageReport-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +PDUSetQoSParameters ::= SEQUENCE { + pduSetDelayBudget ExtendedPacketDelayBudget OPTIONAL, + pduSetErrorRate PacketErrorRate OPTIONAL, + pduSetIntegratedHandlingInformation ENUMERATED {true, false, ...} OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { PDUSetQoSParameters-ExtIEs } } OPTIONAL +} + +PDUSetQoSParameters-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +PDUSetbasedHandlingIndicator ::= ENUMERATED {supported, ...} + +PEIPSassistanceInformation ::= SEQUENCE { + cNsubgroupID CNsubgroupID, + iE-Extensions ProtocolExtensionContainer { { PEIPSassistanceInformation-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +PEIPSassistanceInformation-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +Periodicity ::= INTEGER (0..640000, ...) + +PeriodicityBound ::= SEQUENCE { + periodicityLowerBound Periodicity, + periodicityUpperBound Periodicity, + iE-Extensions ProtocolExtensionContainer { {PeriodicityBound-ExtIEs} } OPTIONAL, + ... +} + +PeriodicityBound-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +PeriodicityList ::= SEQUENCE { + allowedPeriodicityList AllowedPeriodicityList, + iE-Extensions ProtocolExtensionContainer { {PeriodicityList-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +PeriodicityList-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +AllowedPeriodicityList ::= SEQUENCE (SIZE(1..maxnoofPeriodicities)) OF Periodicity + +PeriodicityRange ::= CHOICE { + periodicityBound PeriodicityBound, + periodicityList AllowedPeriodicityList, + choice-extensions ProtocolIE-SingleContainer { {PeriodicityRange-ExtIEs} } +} + +PeriodicityRange-ExtIEs NGAP-PROTOCOL-IES ::= { + ... +} + +PeriodicRegistrationUpdateTimer ::= BIT STRING (SIZE(8)) + +PLMNIdentity ::= OCTET STRING (SIZE(3)) + +PLMNAreaBasedQMC ::= SEQUENCE { + plmnListforQMC PLMNListforQMC, + iE-Extensions ProtocolExtensionContainer { {PLMNAreaBasedQMC-ExtIEs} } OPTIONAL, +} +``` + +``` + ... +} + +PLMNAreaBasedQMC-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +PLMNListforQMC ::= SEQUENCE (SIZE(1..maxnoofPLMNforQMC)) OF PLMNIdentity + +PLMNSupportList ::= SEQUENCE (SIZE(1..maxnoofPLMNs)) OF PLMNSupportItem + +PLMNSupportItem ::= SEQUENCE { + pLMNIdentity PLMNIdentity, + sliceSupportList SliceSupportList, + iE-Extensions ProtocolExtensionContainer { {PLMNSupportItem-ExtIEs} } OPTIONAL, + ... +} + +PLMNSupportItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-NPN-Support CRITICALITY reject EXTENSION NPN-Support PRESENCE optional }| + { ID id-ExtendedSliceSupportList CRITICALITY reject EXTENSION ExtendedSliceSupportList PRESENCE optional }| + { ID id-OnboardingSupport CRITICALITY ignore EXTENSION OnboardingSupport PRESENCE optional }, + ... +} +``` + +} + +PNI-NPN-MobilityInformation ::= SEQUENCE { +    allowed-PNI-NPI-List          Allowed-PNI-NPN-List, +    iE-Extensions               ProtocolExtensionContainer { {PNI-NPN-MobilityInformation-ExtIEs} } OPTIONAL, +    ... +} + +PNI-NPN-MobilityInformation-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +    ... +} + +PortNumber ::= OCTET STRING (SIZE(2)) + +Pre-emptionCapability ::= ENUMERATED { +    shall-not-trigger-pre-emption, +    may-trigger-pre-emption, +    ... +} + +Pre-emptionVulnerability ::= ENUMERATED { +    not-pre-emptable, +    pre-emptable, +} + +``` + ... +} + +PriorityLevelARP ::= INTEGER (1..15) + +PriorityLevelQos ::= INTEGER (1..127, ...) + +PWSFailedCellIDList ::= CHOICE { + eUTRA-CGI-PWSFailedList EUTRA-CGIList, + nR-CGI-PWSFailedList NR-CGIList, + choice-Extensions ProtocolIE-SingleContainer { {PWSFailedCellIDList-ExtIEs} } +} + +PWSFailedCellIDList-ExtIEs NGAP-PROTOCOL-IES ::= { + ... +} + +PNI-NPNBasedMDT ::= SEQUENCE (SIZE(1..maxnoofCAGforMDT)) OF PNI-NPNBasedMDT-Item + +PNI-NPN-AreaScopeofMDT ::= SEQUENCE (SIZE(1..maxnoofCAGforMDT)) OF CAGListforMDT + +PNI-NPNBasedMDT-Item ::= SEQUENCE { + plmnID PLMNIdentity, +``` + +``` + cAGID CAG-ID, + iE-Extensions ProtocolExtensionContainer { {PNI-NPNBasedMDT-Item-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +PNI-NPNBasedMDT-Item-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +-- Q + +``` +QMConfigInfo ::= SEQUENCE { + uEAppLayerMeasInfoList UEAppLayerMeasInfoList, + iE-Extensions ProtocolExtensionContainer { {QMConfigInfo-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +QMConfigInfo-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +QMDeactivation ::= SEQUENCE { +``` + +``` + qoEReferenceList QoEReferenceList, + iE-Extensions ProtocolExtensionContainer { { QMCDeactivation-ExtIEs } } OPTIONAL, + ... +} + +QMCDeactivation-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +QoEReferenceList ::= SEQUENCE (SIZE(1..maxnoofUEAppLayerMeas)) OF QoEReference + +QoEReference ::= OCTET STRING (SIZE(6)) + +QosCharacteristics ::= CHOICE { + nonDynamic5QI NonDynamic5QIDescriptor, + dynamic5QI Dynamic5QIDescriptor, + choice-Extensions ProtocolIE-SingleContainer { { QosCharacteristics-ExtIEs } } +} + +QosCharacteristics-ExtIEs NGAP-PROTOCOL-IES ::= { + ... +} +``` + +``` +QosFlowAcceptedList ::= SEQUENCE (SIZE(1..maxnoofQosFlows)) OF QosFlowAcceptedItem +``` + +``` +QosFlowAcceptedItem ::= SEQUENCE { + qosFlowIdentifier QosFlowIdentifier, + iE-Extensions ProtocolExtensionContainer { {QosFlowAcceptedItem-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +QosFlowAcceptedItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-CurrentQoSParaSetIndex CRITICALITY ignore EXTENSION AlternativeQoSParaSetIndex PRESENCE optional }, + ... +} +``` + +``` +QosFlowAdditionalInfoListRelCom ::= SEQUENCE (SIZE(1..maxnoofQosFlows)) OF QosFlowAdditionalInfoItemRelCom +``` + +``` +QosFlowAdditionalInfoItemRelCom ::= SEQUENCE { + qosFlowIdentifier QosFlowIdentifier, + downlinkTLContainer TLContainer OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {QosFlowAdditionalInfoItemRelCom-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +QosFlowAdditionalInfoItemRelCom-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +} + +QosFlowAdditionalInfoListRelRes ::= SEQUENCE (SIZE(1..maxnoofQosFlows)) OF QosFlowAdditionalInfoItemRelRes + +QosFlowAdditionalInfoItemRelRes ::= SEQUENCE { + qosFlowIdentifier QosFlowIdentifier, + uplinkTLContainer TLContainer OPTIONAL, + iE-Extensions ProtocolExtensionContainer { (QosFlowAdditionalInfoItemRelRes-ExtIEs) } OPTIONAL, + ... +} + +QosFlowAdditionalInfoItemRelRes-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +QosFlowAddOrModifyRequestList ::= SEQUENCE (SIZE(1..maxnoofQosFlows)) OF QosFlowAddOrModifyRequestItem + +QosFlowAddOrModifyRequestItem ::= SEQUENCE { + qosFlowIdentifier QosFlowIdentifier, + qosFlowLevelQosParameters QosFlowLevelQosParameters OPTIONAL, + e-RAB-ID E-RAB-ID OPTIONAL, +``` + +``` + + iE-Extensions ProtocolExtensionContainer { {QosFlowAddOrModifyRequestItem-ExtIEs} } OPTIONAL, + ... +} + +QosFlowAddOrModifyRequestItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + {ID id-TSCTrafficCharacteristics CRITICALITY ignore EXTENSION TSCTrafficCharacteristics PRESENCE optional }| + {ID id-RedundantQosFlowIndicator CRITICALITY ignore EXTENSION RedundantQosFlowIndicator PRESENCE optional }| + {ID id-UL-NGU-UP-TNLInformation CRITICALITY ignore EXTENSION UPTransportLayerInformation PRESENCE optional }| + {ID id-DownlinkTLContainer CRITICALITY ignore EXTENSION TLContainer PRESENCE optional }| + {ID id-ECNMarkingorCongestionInformationReportingRequest CRITICALITY ignore EXTENSION ECNMarkingorCongestionInformationReportingRequest + PRESENCE optional }, + ... +} + +QosFlowAddOrModifyResponseList ::= SEQUENCE (SIZE(1..maxnoofQosFlows)) OF QosFlowAddOrModifyResponseItem + +QosFlowAddOrModifyResponseItem ::= SEQUENCE { + qosFlowIdentifier QosFlowIdentifier, + iE-Extensions ProtocolExtensionContainer { {QosFlowAddOrModifyResponseItem-ExtIEs} } OPTIONAL, + ... +} + +QosFlowAddOrModifyResponseItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + +``` + +``` + + { ID id-CurrentQoSParaSetIndex CRITICALITY ignore EXTENSION AlternativeQoSParaSetIndex PRESENCE optional }| + { ID id-TSCTrafficCharacteristicsFeedback CRITICALITY ignore EXTENSION TSCTrafficCharacteristicsFeedback PRESENCE optional }| + { ID id-UplinkTLContainer CRITICALITY ignore EXTENSION TLContainer PRESENCE optional }| + { ID id-DL-NGU-UP-TNLInformation CRITICALITY ignore EXTENSION UPTransportLayerInformation PRESENCE optional }| + { ID id-ANPacketDelayBudgetUL CRITICALITY ignore EXTENSION ExtendedPacketDelayBudget PRESENCE optional }, + ... +} + +``` + +``` + +QosFlowFeedbackList ::= SEQUENCE (SIZE(1..maxnoofQosFlows)) OF QosFlowFeedbackItem + +``` + +``` + +QosFlowFeedbackItem ::= SEQUENCE { + qosFlowIdentifier QosFlowIdentifier, + updateFeedback UpdateFeedback OPTIONAL, + cNpacketDelayBudgetDL ExtendedPacketDelayBudget OPTIONAL, + cNpacketDelayBudgetUL ExtendedPacketDelayBudget OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {QosFlowFeedbackItem-ExtIEs} } OPTIONAL, + ... +} + +``` + +``` + +QosFlowFeedbackItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +QosFlowIdentifier ::= INTEGER (0..63, ...) + +QosFlowInformationList ::= SEQUENCE (SIZE(1..maxnoofQosFlows)) OF QosFlowInformationItem + +QosFlowInformationItem ::= SEQUENCE { +    qosFlowIdentifier    QosFlowIdentifier, +    dLForwarding        DLForwarding                                                    OPTIONAL, +    iE-Extensions        ProtocolExtensionContainer { {QosFlowInformationItem-ExtIEs} } OPTIONAL, +    ... +} + +QosFlowInformationItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +    {ID id-ULForwarding                CRITICALITY ignore    EXTENSION ULForwarding                PRESENCE optional}| +    {ID id-SourceTNLAddrInfo            CRITICALITY ignore    EXTENSION TransportLayerAddress PRESENCE optional}| +    {ID id-SourceNodeTNLAddrInfo    CRITICALITY ignore    EXTENSION TransportLayerAddress PRESENCE optional}, +    ... +} + +QosFlowLevelQosParameters ::= SEQUENCE { +    qosCharacteristics                QosCharacteristics, +    allocationAndRetentionPriority    AllocationAndRetentionPriority, +    gBR-QosInformation                GBR-QosInformation                                            OPTIONAL, +    reflectiveQosAttribute            ReflectiveQosAttribute                                            OPTIONAL, + +``` + additionalQosFlowInformation AdditionalQosFlowInformation OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {QosFlowLevelQosParameters-ExtIEs} } OPTIONAL, + ... +} + +QosFlowLevelQosParameters-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + {ID id-QosMonitoringRequest CRITICALITY ignore EXTENSION QosMonitoringRequest PRESENCE optional}| + {ID id-QosMonitoringReportingFrequency CRITICALITY ignore EXTENSION QosMonitoringReportingFrequency PRESENCE optional}| + {ID id-PDUsetQoSParameters CRITICALITY ignore EXTENSION PDUsetQoSParameters PRESENCE optional}, + ... +} + +QosMonitoringRequest ::= ENUMERATED {ul, dl, both, ..., stop} + +QosMonitoringReportingFrequency ::= INTEGER (1..1800, ...) + +QoSFlowList ::= SEQUENCE (SIZE(1..maxnoofQosFlows)) OF QosFlowIdentifier + +QosFlowListWithCause ::= SEQUENCE (SIZE(1..maxnoofQosFlows)) OF QosFlowWithCauseItem + +QosFlowWithCauseItem ::= SEQUENCE { + qosFlowIdentifier QosFlowIdentifier, +``` + +``` + cause Cause, + iE-Extensions ProtocolExtensionContainer { {QosFlowWithCauseItem-ExtIEs} } OPTIONAL, + ... + } + + QosFlowWithCauseItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... + } + + QosFlowModifyConfirmList ::= SEQUENCE (SIZE(1..maxnoofQosFlows)) OF QosFlowModifyConfirmItem + + QosFlowModifyConfirmItem ::= SEQUENCE { + qosFlowIdentifier QosFlowIdentifier, + iE-Extensions ProtocolExtensionContainer { {QosFlowModifyConfirmItem-ExtIEs} } OPTIONAL, + ... + } + + QosFlowModifyConfirmItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... + } + + QosFlowNotifyList ::= SEQUENCE (SIZE(1..maxnoofQosFlows)) OF QosFlowNotifyItem +``` + +``` +QosFlowNotifyItem ::= SEQUENCE { + qosFlowIdentifier QosFlowIdentifier, + notificationCause NotificationCause, + iE-Extensions ProtocolExtensionContainer { {QosFlowNotifyItem-ExtIEs} } OPTIONAL, + ... +} + +QosFlowNotifyItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-CurrentQoSParaSetIndex CRITICALITY ignore EXTENSION AlternativeQoSParaSetNotifyIndex PRESENCE optional }| + { ID id-TSCTrafficCharacteristicsFeedback CRITICALITY ignore EXTENSION TSCTrafficCharacteristicsFeedback PRESENCE optional }, + ... +} + +QosFlowParametersList ::= SEQUENCE (SIZE(1..maxnoofQoSFlows)) OF QosFlowParametersItem + +QosFlowParametersItem ::= SEQUENCE { + qosFlowIdentifier QosFlowIdentifier, + alternativeQoSParaSetList AlternativeQoSParaSetList OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {QosFlowParametersItem-ExtIEs} } OPTIONAL, + ... +} + +QosFlowParametersItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-CNPacketDelayBudgetDL CRITICALITY ignore EXTENSION ExtendedPacketDelayBudget PRESENCE optional }| +``` + +``` +{ ID id-CNPacketDelayBudgetUL CRITICALITY ignore EXTENSION ExtendedPacketDelayBudget PRESENCE optional }| +{ ID id-BurstArrivalTimeDownlink CRITICALITY ignore EXTENSION BurstArrivalTime PRESENCE optional }, +... +} +``` + +``` +QosFlowPerTNLInformation ::= SEQUENCE { + uPTransportLayerInformation UPTransportLayerInformation, + associatedQosFlowList AssociatedQosFlowList, + iE-Extensions ProtocolExtensionContainer { { QosFlowPerTNLInformation-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +QosFlowPerTNLInformation-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +QosFlowPerTNLInformationList ::= SEQUENCE (SIZE(1..maxnoofMultiConnectivityMinusOne)) OF QosFlowPerTNLInformationItem +``` + +``` +QosFlowPerTNLInformationItem ::= SEQUENCE { + qosFlowPerTNLInformation QosFlowPerTNLInformation, + iE-Extensions ProtocolExtensionContainer { { QosFlowPerTNLInformationItem-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +QosFlowPerTNLInformationItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +QosFlowSetupRequestList ::= SEQUENCE (SIZE(1..maxnoofQosFlows)) OF QosFlowSetupRequestItem +``` + +``` +QosFlowSetupRequestItem ::= SEQUENCE { +``` + +``` + qosFlowIdentifier QosFlowIdentifier, +``` + +``` + qosFlowLevelQosParameters QosFlowLevelQosParameters, +``` + +``` + e-RAB-ID E-RAB-ID OPTIONAL, +``` + +``` + iE-Extensions ProtocolExtensionContainer { (QosFlowSetupRequestItem-ExtIEs) } OPTIONAL, +``` + +``` + ... +``` + +``` +} +``` + +``` +QosFlowSetupRequestItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +``` + +``` + {ID id-TSCTrafficCharacteristics CRITICALITY ignore EXTENSION TSCTrafficCharacteristics PRESENCE optional }| +``` + +``` + {ID id-RedundantQosFlowIndicator CRITICALITY ignore EXTENSION RedundantQosFlowIndicator PRESENCE optional }| +``` + +``` + {ID id-ECNMarkingorCongestionInformationReportingRequest CRITICALITY ignore EXTENSION ECNMarkingorCongestionInformationReportingRequest + PRESENCE optional }, +``` + +``` + ... +``` + +``` +} +``` + +QosFlowListWithDataForwarding ::= SEQUENCE (SIZE(1..maxnoofQosFlows)) OF QosFlowItemWithDataForwarding + +QosFlowItemWithDataForwarding ::= SEQUENCE { +    qosFlowIdentifier          QosFlowIdentifier, +    dataForwardingAccepted     DataForwardingAccepted                                  OPTIONAL, +    iE-Extensions            ProtocolExtensionContainer { {QosFlowItemWithDataForwarding-ExtIEs} } OPTIONAL, +    ... +} + +QosFlowItemWithDataForwarding-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +    { ID id-CurrentQoSParaSetIndex CRITICALITY ignore EXTENSION AlternativeQoSParaSetIndex PRESENCE optional }, +    ... +} + +QosFlowToBeForwardedList ::= SEQUENCE (SIZE(1..maxnoofQosFlows)) OF QosFlowToBeForwardedItem + +QosFlowToBeForwardedItem ::= SEQUENCE { +    qosFlowIdentifier          QosFlowIdentifier, +    iE-Extensions            ProtocolExtensionContainer { {QosFlowToBeForwardedItem-ExtIEs} } OPTIONAL, +    ... +} + +QosFlowToBeForwardedItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + +``` + ... +} + +QoSFlowTSCList ::= SEQUENCE (SIZE(1..maxnoofQoSFlows)) OF QoSFlowTSCItem + +QoSFlowTSCItem ::= SEQUENCE { + qosFlowIdentifier QoSFlowIdentifier, + tSCTrafficCharacteristicsFeedback TSCTrafficCharacteristicsFeedback OPTIONAL, + aNPacketDelayBudgetUL ExtendedPacketDelayBudget OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {QoSFlowTSCItem-ExtIEs} } OPTIONAL, + ... +} + +QoSFlowTSCItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +QoSFlowsUsageReportList ::= SEQUENCE (SIZE(1..maxnoofQoSFlows)) OF QoSFlowsUsageReport-Item + +QoSFlowsUsageReport-Item ::= SEQUENCE { + qosFlowIdentifier QoSFlowIdentifier, + rATType ENUMERATED {nr, eutra, ..., nr-unlicensed, e-utra-unlicensed}, + qosFlowsTimedReportList VolumeTimedReportList, +``` + +``` + iE-Extensions ProtocolExtensionContainer { {QoSFlowsUsageReport-Item-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +QoSFlowsUsageReport-Item-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +-- R + +``` +RANfeedbacktype ::= CHOICE { + proactive RANfeedbacktype-proactive, + reactive RANfeedbacktype-reactive, + choice-extensions ProtocolIE-SingleContainer { {RANfeedbacktype-ExtIEs} } +} +``` + +``` +RANfeedbacktype-ExtIEs NGAP-PROTOCOL-IES ::= { + ... +} +``` + +``` +RANfeedbacktype-proactive ::= SEQUENCE { + burstArrivalTimeWindow BurstArrivalTimeWindow, + periodicityRange PeriodicityRange OPTIONAL, +``` + +``` + iE-Extension ProtocolExtensionContainer { {RANfeedbacktype-proactive-ExtIEs} } OPTIONAL, + ... +} + +RANfeedbacktype-proactive-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +RANfeedbacktype-reactive ::= SEQUENCE { + capabilityForBATAdaptation ENUMERATED {true, ...}, + iE-Extension ProtocolExtensionContainer { {RANfeedbacktype-reactive-ExtIEs} } OPTIONAL, + ... +} + +RANfeedbacktype-reactive-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +Range ::= ENUMERATED {m50, m80, m180, m200, m350, m400, m500, m700, m1000, ...} + +RANNodeName ::= PrintableString (SIZE(1..150, ...)) + +RANNodeNameVisibleString ::= VisibleString (SIZE(1..150, ...)) +``` + +RANNodeNameUTF8String ::= UTF8String (SIZE(1..150, ...)) + +RANPagingPriority ::= INTEGER (1..256) + +RANStatusTransfer-TransparentContainer ::= SEQUENCE { +    dRBsSubjectToStatusTransferList    DRBsSubjectToStatusTransferList, +    iE-Extensions    ProtocolExtensionContainer { {RANStatusTransfer-TransparentContainer-ExtIEs} } OPTIONAL, +    ... +} + +RANStatusTransfer-TransparentContainer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +    ... +} + +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 NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +RAN-TSSRequestType ::= ENUMERATED {start, stop, ...} + +RAN-TSSScope ::= CHOICE { + rANNodeLevel GlobalGNB-ID, + cellListLevel RANTSSCellList, + choice-Extensions ProtocolIE-SingleContainer { { RAN-TSSScope-ExtIEs} } +} + +RAN-TSSScope-ExtIEs NGAP-PROTOCOL-IES ::= { + ... +} + +RANTSSCellList ::= SEQUENCE (SIZE(1..maxnoofCellsTSS)) OF RANTSSCellItem + +RANTSSCellItem ::= SEQUENCE { +``` + +``` + nRCGI NR-CGI, + iE-Extensions ProtocolExtensionContainer { {RANTSSCellItem-ExtIEs} } OPTIONAL, + ... +} + +RANTSSCellItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +RAN-UE-NGAP-ID ::= INTEGER (0..4294967295) + +RAT-Information ::= ENUMERATED { + unlicensed, + nb-IoT, + ..., + nR-LEO, + nR-MEO, + nR-GEO, + nR-OTHERSAT +} + +RATRestrictions ::= SEQUENCE (SIZE(1..maxnoofEPLMNsPlusOne)) OF RATRestrictions-Item +``` + +``` +RATRestrictions-Item ::= SEQUENCE { + pLMNIdentity PLMNIdentity, + rATRestrictionInformation RATRestrictionInformation, + iE-Extensions ProtocolExtensionContainer { {RATRestrictions-Item-ExtIEs} } OPTIONAL, + ... +} + +RATRestrictions-Item-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-ExtendedRATRestrictionInformation CRITICALITY ignore EXTENSION ExtendedRATRestrictionInformation PRESENCE optional }, + ... +} + +RATRestrictionInformation ::= BIT STRING (SIZE(8, ...)) + +RecommendedCellsForPaging ::= SEQUENCE { + recommendedCellList RecommendedCellList, + iE-Extensions ProtocolExtensionContainer { {RecommendedCellsForPaging-ExtIEs} } OPTIONAL, + ... +} + +RecommendedCellsForPaging-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +RecommendedCellList ::= SEQUENCE (SIZE(1..maxnoofRecommendedCells)) OF RecommendedCellItem +``` + +``` +RecommendedCellItem ::= SEQUENCE { + nGRAN-CGI NGRAN-CGI, + timeStayedInCell INTEGER (0..4095) OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {RecommendedCellItem-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +RecommendedCellItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +RecommendedRANNodesForPaging ::= SEQUENCE { + recommendedRANNodeList RecommendedRANNodeList, + iE-Extensions ProtocolExtensionContainer { {RecommendedRANNodesForPaging-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +RecommendedRANNodesForPaging-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +RecommendedRANNodeList ::= SEQUENCE (SIZE(1..maxnoofRecommendedRANNodes)) OF RecommendedRANNodeItem +``` + +``` +RecommendedRANNodeItem ::= SEQUENCE { + aMFPagingTarget AMFPagingTarget, + iE-Extensions ProtocolExtensionContainer { {RecommendedRANNodeItem-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +RecommendedRANNodeItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +RedCapIndication ::= ENUMERATED { + redcap, + ... +} +``` + +``` +RedirectionVoiceFallback ::= ENUMERATED { + possible, + not-possible, + ... +} +``` + +``` +RedundantPDUSessionInformation ::= SEQUENCE { + rSN RSN, + iE-Extensions ProtocolExtensionContainer { {RedundantPDUSessionInformation-ExtIEs} } OPTIONAL, + ... +} + +RedundantPDUSessionInformation-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-PDUSessionPairID CRITICALITY ignore EXTENSION PDUSessionPairID PRESENCE optional }, + ... +} + +RedundantQosFlowIndicator ::= ENUMERATED {true, false} + +ReflectiveQosAttribute ::= ENUMERATED { + subject-to, + ... +} + +RelativeAMFCapacity ::= INTEGER (0..255) + +ReportArea ::= ENUMERATED { + cell, +``` + +``` + ... +} + +RepetitionPeriod ::= INTEGER (0..131071) + +ResetAll ::= ENUMERATED { + reset-all, + ... +} + +ReportAmountMDT ::= ENUMERATED { + r1, r2, r4, r8, r16, r32, r64, rinfinity +} + +ReportIntervalMDT ::= ENUMERATED { + ms120, ms240, ms480, ms640, ms1024, ms2048, ms5120, ms10240, min1, min6, min12, min30, min60 +} + +ExtendedReportIntervalMDT ::= ENUMERATED { + ms20480, ms40960, ... +} + +ResetType ::= CHOICE { +``` + +``` + nG-Interface ResetAll, + partOfNG-Interface UE-associatedLogicalNG-connectionList, + choice-Extensions ProtocolIE-SingleContainer { {ResetType-ExtIEs} } +} +``` + +``` +ResetType-ExtIEs NGAP-PROTOCOL-IES ::= { + ... +} +``` + +``` +RGLevelWirelineAccessCharacteristics ::= OCTET STRING +``` + +``` +RNC-ID ::= INTEGER (0..4095) +``` + +``` +RoutingID ::= OCTET STRING +``` + +``` +RRContainer ::= OCTET STRING +``` + +``` +RRCEstablishmentCause ::= ENUMERATED { + emergency, + highPriorityAccess, + mt-Access, + mo-Signalling, + mo-Data, +} +``` + +``` + mo-VoiceCall, + mo-VideoCall, + mo-SMS, + mps-PriorityAccess, + mcs-PriorityAccess, + ..., + notAvailable, + mo-ExceptionData +} + +RRCInactiveTransitionReportRequest ::= ENUMERATED { + subsequent-state-transition-report, + single-rrc-connected-state-report, + cancel-report, + ... +} + +RRCState ::= ENUMERATED { + inactive, + connected, + ... +} +``` + +RSN ::= ENUMERATED {v1, v2, ...} + +RIMInformationTransfer ::= SEQUENCE { +    targetRANNodeID-RIM           TargetRANNodeID-RIM, +    sourceRANNodeID              SourceRANNodeID, +    rIMInformation               RIMInformation, +    iE-Extensions                ProtocolExtensionContainer { {RIMInformationTransfer-ExtIEs} } OPTIONAL, +    ... +} + +RIMInformationTransfer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +    ... +} + +RIMInformation ::= SEQUENCE { +    targetgNBSetID               GNBSetID, +    rIM-RSDetection              ENUMERATED {rs-detected, rs-disappeared, ...}, +    iE-Extensions                ProtocolExtensionContainer { {RIMInformation-ExtIEs} } OPTIONAL, +    ... +} + +RIMInformation-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + +``` + ... +} + +GNBSetID ::= BIT STRING (SIZE(22)) + +-- S + +ScheduledCommunicationTime ::= SEQUENCE { + dayOfWeek BIT STRING (SIZE(7)) OPTIONAL, + timeOfDayStart INTEGER (0..86399, ...) OPTIONAL, + timeOfDayEnd INTEGER (0..86399, ...) OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { ScheduledCommunicationTime-ExtIEs} } OPTIONAL, + ... +} + +ScheduledCommunicationTime-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +SCTP-TLAs ::= SEQUENCE (SIZE(1..maxnoofXnTLAs)) OF TransportLayerAddress + +SD ::= OCTET STRING (SIZE(3)) +``` + +``` +SecondaryRATUsageInformation ::= SEQUENCE { + pduSessionUsageReport pduSessionUsageReport OPTIONAL, + qosFlowsUsageReportList qosFlowsUsageReportList OPTIONAL, + iE-Extension protocolExtensionContainer { {SecondaryRATUsageInformation-ExtIEs} } OPTIONAL, + ... +} + +SecondaryRATUsageInformation-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +SecondaryRATDataUsageReportTransfer ::= SEQUENCE { + secondaryRATUsageInformation secondaryRATUsageInformation OPTIONAL, + iE-Extensions protocolExtensionContainer { {SecondaryRATDataUsageReportTransfer-ExtIEs} } OPTIONAL, + ... +} + +SecondaryRATDataUsageReportTransfer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +SecurityContext ::= SEQUENCE { + nextHopChainingCount nextHopChainingCount, +``` + +``` + nextHopNH SecurityKey, + iE-Extensions ProtocolExtensionContainer { {SecurityContext-ExtIEs} } OPTIONAL, + ... + } + + SecurityContext-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... + } + + SecurityIndication ::= SEQUENCE { + integrityProtectionIndication IntegrityProtectionIndication, + confidentialityProtectionIndication ConfidentialityProtectionIndication, + maximumIntegrityProtectedDataRate-UL MaximumIntegrityProtectedDataRate OPTIONAL, + -- The above IE shall be present if integrity protection is required or preferred + iE-Extensions ProtocolExtensionContainer { {SecurityIndication-ExtIEs} } OPTIONAL, + ... + } + + SecurityIndication-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-MaximumIntegrityProtectedDataRate-DL CRITICALITY ignore EXTENSION MaximumIntegrityProtectedDataRate PRESENCE optional }, + ... + } +``` + +SecurityKey ::= BIT STRING (SIZE(256)) + +SecurityResult ::= SEQUENCE { +    integrityProtectionResult    IntegrityProtectionResult, +    confidentialityProtectionResult    ConfidentialityProtectionResult, +    iE-Extensions    ProtocolExtensionContainer { {SecurityResult-ExtIEs} } OPTIONAL, +    ... +} + +SecurityResult-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +    ... +} + +SensorMeasurementConfiguration ::= SEQUENCE { +    sensorMeasConfig    SensorMeasConfig, +    sensorMeasConfigNameList    SensorMeasConfigNameList    OPTIONAL, +    iE-Extensions    ProtocolExtensionContainer { {SensorMeasurementConfiguration-ExtIEs} } OPTIONAL, +    ... +} + +SensorMeasurementConfiguration-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +    ... +} + +``` +SensorMeasConfigNameList ::= SEQUENCE (SIZE(1..maxnoofSensorName)) OF SensorMeasConfigNameItem +``` + +``` +SensorMeasConfigNameItem ::= SEQUENCE { + sensorNameConfig SensorNameConfig, + iE-Extensions ProtocolExtensionContainer { { SensorMeasConfigNameItem-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +SensorMeasConfigNameItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +SensorMeasConfig ::= ENUMERATED {setup,...} +``` + +``` +SensorNameConfig ::= CHOICE { + uncompensatedBarometricConfig ENUMERATED {true, ...}, + ueSpeedConfig ENUMERATED {true, ...}, + ueOrientationConfig ENUMERATED {true, ...}, + choice-Extensions ProtocolIE-SingleContainer { {SensorNameConfig-ExtIEs} } +} +``` + +``` +SensorNameConfig-ExtIEs NGAP-PROTOCOL-IES ::= { +``` + +``` + ... +} + +SerialNumber ::= BIT STRING (SIZE(16)) + +ServedGUAMIList ::= SEQUENCE (SIZE(1..maxnooServedGUAMIs)) OF ServedGUAMIItem + +ServedGUAMIItem ::= SEQUENCE { + gUAMI GUAMI, + backupAMFName AMFName OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {ServedGUAMIItem-ExtIEs} } OPTIONAL, + ... +} + +ServedGUAMIItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + {ID id-GUAMIType CRITICALITY ignore EXTENSION GUAMIType PRESENCE optional }, + ... +} + +ServiceAreaInformation ::= SEQUENCE (SIZE(1.. maxnoofEPLMNsPlusOne)) OF ServiceAreaInformation-Item + +ServiceAreaInformation-Item ::= SEQUENCE { + pLMNIdentity PLMNIdentity, +``` + +``` + allowedTACs AllowedTACs OPTIONAL, + notAllowedTACs NotAllowedTACs OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {ServiceAreaInformation-Item-ExtIEs} } OPTIONAL, + ... +} + +ServiceAreaInformation-Item-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +ServiceType ::= ENUMERATED {streaming, mTSI, vR, ...} + +SgNB-UE-X2AP-ID ::= INTEGER (0..4294967295) + +SharedNGU-MulticastTNLInformation ::= SEQUENCE { + iP-MulticastAddress TransportLayerAddress, + iP-SourceAddress TransportLayerAddress, + gTP-TEID GTP-TEID, + iE-Extensions ProtocolExtensionContainer { {SharedNGU-MulticastTNLInformation-ExtIEs} } OPTIONAL, + ... +} + +SharedNGU-MulticastTNLInformation-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +``` + +``` +... +} + +SliceOverloadList ::= SEQUENCE (SIZE(1..maxnoofSliceItems)) OF SliceOverloadItem + +SliceOverloadItem ::= SEQUENCE { + s-NSSAI S-NSSAI, + iE-Extensions ProtocolExtensionContainer { {SliceOverloadItem-ExtIEs} } OPTIONAL, + ... +} + +SliceOverloadItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +SliceSupportList ::= SEQUENCE (SIZE(1..maxnoofSliceItems)) OF SliceSupportItem + +SliceSupportItem ::= SEQUENCE { + s-NSSAI S-NSSAI, + iE-Extensions ProtocolExtensionContainer { {SliceSupportItem-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +SliceSupportItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +SliceSupportListQMC ::= SEQUENCE (SIZE(1..maxnoofSNSSAIforQMC)) OF SliceSupportQMC-Item + +SliceSupportQMC-Item ::= SEQUENCE { + s-NSSAI S-NSSAI, + iE-Extensions ProtocolExtensionContainer { {SliceSupportQMC-Item-ExtIEs} } OPTIONAL, + ... +} + +SliceSupportQMC-Item-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +SNPN-MobilityInformation ::= SEQUENCE { + serving-NID NID, + iE-Extensions ProtocolExtensionContainer { {SNPN-MobilityInformation-ExtIEs} } OPTIONAL, + ... +} + +SNPN-MobilityInformation-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +``` + +``` +{ID id-EquivalentSNPNSList CRITICALITY reject EXTENSION EquivalentSNPNSList PRESENCE optional}, +... +} +``` + +``` +S-NSSAI ::= SEQUENCE { + sST SST, + sD SD OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { S-NSSAI-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +S-NSSAI-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +SONConfigurationTransfer ::= SEQUENCE { + targetRANNodeID-SON TargetRANNodeID-SON, + sourceRANNodeID SourceRANNodeID, + sONInformation SONInformation, + xnTNLConfigurationInfo XnTNLConfigurationInfo OPTIONAL, +-- The above IE shall be present if the SON Information IE contains the SON Information Request IE set to "Xn TNL Configuration Info" + iE-Extensions ProtocolExtensionContainer { {SONConfigurationTransfer-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +} + +SONConfigurationTransfer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +SONInformation ::= CHOICE { + sONInformationRequest sONInformationRequest, + sONInformationReply sONInformationReply, + choice-Extensions ProtocolIE-SingleContainer { {SONInformation-ExtIEs} } +} + +SONInformation-ExtIEs NGAP-PROTOCOL-IES ::= { + { ID id-SONInformationReport CRITICALITY ignore TYPE SONInformationReport PRESENCE mandatory }, + ... +} + +SONInformationReply ::= SEQUENCE { + xnTNLConfigurationInfo XnTNLConfigurationInfo OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {SONInformationReply-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +SONInformationReply-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +SONInformationReport ::= CHOICE { + failureIndicationInformation FailureIndication, + hOReportInformation HOReport, + choice-Extensions ProtocolIE-SingleContainer { { SONInformationReport-ExtIEs } } +} +``` + +``` +SONInformationReport-ExtIEs NGAP-PROTOCOL-IES ::= { + { ID id-SuccessfulHandoverReportList CRITICALITY ignore TYPE SuccessfulHandoverReportList PRESENCE mandatory } | + { ID id-SuccessfulPSCellChangeReportList CRITICALITY ignore TYPE SuccessfulPSCellChangeReportList PRESENCE mandatory }, + ... +} +``` + +``` +SNPN-CellBasedMDT ::= SEQUENCE { + sNPNCellIdListforMDT SNPNCellIdListforMDT, + iE-Extensions ProtocolExtensionContainer { { SNPN-CellBasedMDT-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +SNPN-CellBasedMDT-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +} + +SNPNCellIdListforMDT ::= SEQUENCE (SIZE(1..maxnoofCellIDforMDT)) OF SNPNCellIdListforMDTItem + +SNPNCellIdListforMDTItem ::= SEQUENCE { + nR-CGI NR-CGI, + nID NID, + iE-Extensions ProtocolExtensionContainer {{ SNPNCellIdListforMDTItem-ExtIEs}} OPTIONAL, + ... +} + +SNPNCellIdListforMDTItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +SNPN-TAIBasedMDT ::= SEQUENCE { + sNPNTAIListforMDT sNPNTAIListforMDT, + iE-Extensions ProtocolExtensionContainer { {SNPN-TAIBasedMDT-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +SNPN-TAIBasedMDT-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +SNPNTAIListforMDT ::= SEQUENCE (SIZE(1.. maxnoofTAforMDT)) OF SNPNTAIListforMDTItem + +SNPNTAIListforMDTItem ::= SEQUENCE { + tAI TAI, + nID NID, + iE-Extensions ProtocolExtensionContainer {{ SNPNTAIListforMDTItem-ExtIEs}} OPTIONAL, + ... +} + +SNPNTAIListforMDTItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +SNPN-BasedMDT ::= SEQUENCE { + sPNListforMDT sPNListforMDT, + iE-Extensions ProtocolExtensionContainer { {SNPN-BasedMDT-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +SNPN-BasedMDT-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +SNPNListforMDT ::= SEQUENCE (SIZE(1.. maxnoofMDTSNPNs)) OF SNPNListforMDTItem +``` + +``` +SNPNListforMDTItem ::= SEQUENCE { +``` + +``` + pLMNIdentity PLMNIdentity, +``` + +``` + nID NID, +``` + +``` + iE-Extensions ProtocolExtensionContainer {{ SNPNListforMDTItem-ExtIEs}} OPTIONAL, +``` + +``` + ... +``` + +``` +} +``` + +``` +SNPNListforMDTItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +-- ----- +``` + +``` +-- SON Information Report +``` + +``` +-- ----- +``` + +``` +SuccessfulHandoverReportList ::= SEQUENCE (SIZE(1..maxnoofSuccessfulHOReports)) OF SuccessfulHandoverReport-Item +``` + +``` +SuccessfulHandoverReport-Item ::= SEQUENCE { + successfulHOReportContainer OCTET STRING, + iE-Extensions ProtocolExtensionContainer { { SuccessfulHandoverReport-Item-ExtIEs} } OPTIONAL, + ... +} + +SuccessfulHandoverReport-Item-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +SuccessfulPSCellChangeReportList ::= SEQUENCE (SIZE(1..maxnoofSuccessfulPSCellChangeReports)) OF SuccessfulPSCellChangeReport-Item + +SuccessfulPSCellChangeReport-Item ::= SEQUENCE { + successfulPSCellChangeReportContainer OCTET STRING, + iE-Extensions ProtocolExtensionContainer { { SuccessfulPSCellChangeReport-Item-ExtIEs} } OPTIONAL, + ... +} + +SuccessfulPSCellChangeReport-Item-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +SONInformationRequest ::= ENUMERATED { +``` + +``` + + xn-TNL-configuration-info, + ... +} + +``` + +``` + +SourceNGRANNode-ToTargetNGRANNode-TransparentContainer ::= SEQUENCE { + rRCContainer RRCContainer, + pDUSessionResourceInformationList pDUSessionResourceInformationList OPTIONAL, + e-RABInformationList e-RABInformationList OPTIONAL, + targetCell-ID NGRAN-CGI, + indexToRFSP IndexToRFSP OPTIONAL, + uEHistoryInformation uEHistoryInformation, + iE-Extensions ProtocolExtensionContainer { {SourceNGRANNode-ToTargetNGRANNode-TransparentContainer-ExtIEs} } OPTIONAL, + ... +} + +``` + +``` + +SourceNGRANNode-ToTargetNGRANNode-TransparentContainer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-SgNB-UE-X2AP-ID CRITICALITY ignore EXTENSION SgNB-UE-X2AP-ID PRESENCE optional }| + { ID id-UEHistoryInformationFromTheUE CRITICALITY ignore EXTENSION UEHistoryInformationFromTheUE PRESENCE optional }| + { ID id-SourceNodeID CRITICALITY ignore EXTENSION SourceNodeID PRESENCE optional }| + { ID id-UEContextReferenceAtSource CRITICALITY ignore EXTENSION RAN-UE-NGAP-ID PRESENCE optional }| + { ID id-MBS-ActiveSessionInformation-SourcetoTargetList CRITICALITY ignore EXTENSION MBS-ActiveSessionInformation-SourcetoTargetList PRESENCE +optional }| + { ID id-QMCConfigInfo CRITICALITY ignore EXTENSION QMCConfigInfo PRESENCE optional }| +} + +``` + +``` +{ ID id-NGAPIESupportInformationRequestList CRITICALITY ignore EXTENSION NGAPIESupportInformationRequestList PRESENCE optional }| +{ ID id-CandidateRelayUEInformationList CRITICALITY reject EXTENSION CandidateRelayUEInformationList PRESENCE optional }| +{ ID id-TimeBasedHandoverInformation CRITICALITY ignore EXTENSION TimeBasedHandoverInformation PRESENCE optional }, +... +} +``` + +``` +SourceNodeID ::= CHOICE { + sourceengNB-ID GlobalGNB-ID, + choice-Extensions ProtocolIE-SingleContainer { { SourceNodeID-ExtIEs} } +} +``` + +``` +SourceNodeID-ExtIEs NGAP-PROTOCOL-IES ::= { + ... +} +``` + +``` +SourceOfUEActivityBehaviourInformation ::= ENUMERATED { + subscription-information, + statistics, + ... +} +``` + +``` +SourceRANNodeID ::= SEQUENCE { + globalRANNodeID GlobalRANNodeID, +``` + +``` + selectedTAI TAI, + iE-Extensions ProtocolExtensionContainer { {SourceRANNodeID-ExtIEs} } OPTIONAL, + ... +} + +SourceRANNodeID-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +SourceToTarget-TransparentContainer ::= OCTET STRING + +-- This IE includes a transparent container from the source RAN node to the target RAN node. + +-- The octets of the OCTET STRING are encoded according to the specifications of the target system. + +SourceToTarget-AMFInformationReroute ::= SEQUENCE { + configuredNSSAI ConfiguredNSSAI OPTIONAL, + rejectedNSSAIinPLMN RejectedNSSAIinPLMN OPTIONAL, + rejectedNSSAIinTA RejectedNSSAIinTA OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {SourceToTarget-AMFInformationReroute-ExtIEs} } OPTIONAL, + ... +} + +SourceToTarget-AMFInformationReroute-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +} + +-- This IE includes information from the source Core node to the target Core node for reroute information provide by NSSF. +-- The octets of the OCTET STRING are encoded according to the specifications of the Core network. + +SRVCCOperationPossible ::= ENUMERATED { + possible, + notPossible, + ... +} + +ConfiguredNSSAI ::= OCTET STRING (SIZE(128)) + +RejectedNSSAIinPLMN ::= OCTET STRING (SIZE(32)) + +RejectedNSSAIinTA ::= OCTET STRING (SIZE(32)) + +SST ::= OCTET STRING (SIZE(1)) + +SupportedTAList ::= SEQUENCE (SIZE(1..maxnoofTACs)) OF SupportedTAItem + +SupportedTAItem ::= SEQUENCE { + tAC TAC, +``` + +``` + broadcastPLMNList BroadcastPLMNList, + iE-Extensions ProtocolExtensionContainer { {SupportedTAItem-ExtIEs} } OPTIONAL, + ... +} + +SupportedTAItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + {ID id-ConfiguredTACIndication CRITICALITY ignore EXTENSION ConfiguredTACIndication PRESENCE optional }| + {ID id-RAT-Information CRITICALITY reject EXTENSION RAT-Information PRESENCE optional }, + ... +} + +SuspendIndicator ::= ENUMERATED { + true, + ... +} + +Suspend-Request-Indication ::= ENUMERATED { + suspend-requested, + ... +} + +Suspend-Response-Indication ::= ENUMERATED { + suspend-indicated, +``` + +``` + ... +} + +SurvivalTime ::= INTEGER (0..1920000, ...) + +-- T + +TAC ::= OCTET STRING (SIZE(3)) + +TACListInNRNTN ::= SEQUENCE (SIZE(1..maxnoofTACsinNTN)) OF TAC + +TAI ::= SEQUENCE { + pLMNIdentity PLMNIdentity, + tAC TAC, + iE-Extensions ProtocolExtensionContainer { {TAI-ExtIEs} } OPTIONAL, + ... +} + +TAI-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +TAIBroadcastEUTRA ::= SEQUENCE (SIZE(1..maxnoofTAIforWarning)) OF TAIBroadcastEUTRA-Item +``` + +``` +TAIBroadcastEUTRA-Item ::= SEQUENCE { + tAI TAI, + completedCellsInTAI-EUTRA CompletedCellsInTAI-EUTRA, + iE-Extensions ProtocolExtensionContainer { {TAIBroadcastEUTRA-Item-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +TAIBroadcastEUTRA-Item-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +TAIBroadcastNR ::= SEQUENCE (SIZE(1..maxnoofTAIforWarning)) OF TAIBroadcastNR-Item +``` + +``` +TAIBroadcastNR-Item ::= SEQUENCE { + tAI TAI, + completedCellsInTAI-NR CompletedCellsInTAI-NR, + iE-Extensions ProtocolExtensionContainer { {TAIBroadcastNR-Item-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +TAIBroadcastNR-Item-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +} + +TAICancelledEUTRA ::= SEQUENCE (SIZE(1..maxnoofTAIforWarning)) OF TAICancelledEUTRA-Item + +TAICancelledEUTRA-Item ::= SEQUENCE { + tAI TAI, + cancelledCellsInTAI-EUTRA CancelledCellsInTAI-EUTRA, + iE-Extensions ProtocolExtensionContainer { {TAICancelledEUTRA-Item-ExtIEs} } OPTIONAL, + ... +} + +TAICancelledEUTRA-Item-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +TAICancelledNR ::= SEQUENCE (SIZE(1..maxnoofTAIforWarning)) OF TAICancelledNR-Item + +TAICancelledNR-Item ::= SEQUENCE { + tAI TAI, + cancelledCellsInTAI-NR CancelledCellsInTAI-NR, + iE-Extensions ProtocolExtensionContainer { {TAICancelledNR-Item-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +} +``` + +``` +TAICancelledNR-Item-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +TAIListForInactive ::= SEQUENCE (SIZE(1..maxnoofTAIforInactive)) OF TAIListForInactiveItem +``` + +``` +TAIListForInactiveItem ::= SEQUENCE { +``` + +``` + tAI TAI, +``` + +``` + iE-Extensions ProtocolExtensionContainer { {TAIListForInactiveItem-ExtIEs} } OPTIONAL, +``` + +``` + ... +``` + +``` +} +``` + +``` +TAIListForInactiveItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +TAIListForPaging ::= SEQUENCE (SIZE(1..maxnoofTAIforPaging)) OF TAIListForPagingItem +``` + +``` +TAIListForPagingItem ::= SEQUENCE { +``` + +``` + tAI TAI, +``` + +``` + iE-Extensions ProtocolExtensionContainer { {TAIListForPagingItem-ExtIEs} } OPTIONAL, +``` + +``` + ... +} + +TAIListForPagingItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +TAIListForRestart ::= SEQUENCE (SIZE(1..maxnoofTAIforRestart)) OF TAI + +TAIListForWarning ::= SEQUENCE (SIZE(1..maxnoofTAIforWarning)) OF TAI + +TAINSAGSupportList ::= SEQUENCE (SIZE(1..maxnoofNSAGs)) OF TAINSAGSupportItem + +TAINSAGSupportItem ::= SEQUENCE { + nSAG-ID NSAG-ID, + nSAGSliceSupportList ExtendedSliceSupportList, + iE-Extensions ProtocolExtensionContainer { {TAINSAGSupportItem-ExtIEs} } OPTIONAL, + ... +} + +TAINSAGSupportItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +TargeteNB-ID ::= SEQUENCE { + globalENB-ID GlobalNgENB-ID, + selected-EPS-TAI EPS-TAI, + iE-Extensions ProtocolExtensionContainer { {TargeteNB-ID-ExtIEs} } OPTIONAL, + ... +} + +TargeteNB-ID-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +TargetHomeENB-ID ::= SEQUENCE { + pLMNIdentity PLMNIdentity, + homeENB-ID BIT STRING (SIZE(28)), + selected-EPS-TAI EPS-TAI, + iE-Extensions ProtocolExtensionContainer { {TargetHomeENB-ID-ExtIEs} } OPTIONAL, + ... +} + +TargetHomeENB-ID-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +TargetID ::= CHOICE { + targetRANNodeID TargetRANNodeID, + targeteNB-ID TargeteNB-ID, + choice-Extensions ProtocolIE-SingleContainer { {TargetID-ExtIEs} } +} + +TargetID-ExtIEs NGAP-PROTOCOL-IES ::= { + {ID id-TargetRNC-ID CRITICALITY reject TYPE TargetRNC-ID PRESENCE mandatory }| + {ID id-TargetHomeENB-ID CRITICALITY reject TYPE TargetHomeENB-ID PRESENCE mandatory }, + ... +} + +TargetNGRANNode-ToSourceNGRANNode-TransparentContainer ::= SEQUENCE { + rRCContainer RRCContainer, + iE-Extensions ProtocolExtensionContainer { {TargetNGRANNode-ToSourceNGRANNode-TransparentContainer-ExtIEs} } OPTIONAL, + ... +} + +TargetNGRANNode-ToSourceNGRANNode-TransparentContainer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-DAPSResponseInfoList CRITICALITY ignore EXTENSION DAPSResponseInfoList PRESENCE optional }| + { ID id-DirectForwardingPathAvailability CRITICALITY ignore EXTENSION DirectForwardingPathAvailability PRESENCE optional }| +``` + +``` +{ ID id-MBS-ActiveSessionInformation-TargettoSourceList CRITICALITY ignore EXTENSION MBS-ActiveSessionInformation-TargettoSourceList PRESENCE optional }| +``` + +``` +{ ID id-NGAPIESupportInformationResponseList CRITICALITY ignore EXTENSION NGAPIESupportInformationResponseList PRESENCE optional }, +... +} +``` + +``` +TargetNGRANNode-ToSourceNGRANNode-FailureTransparentContainer ::= SEQUENCE { + cell-CAGInformation Cell-CAGInformation OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {TargetNGRANNode-ToSourceNGRANNode-FailureTransparentContainer-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +TargetNGRANNode-ToSourceNGRANNode-FailureTransparentContainer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-NGAPIESupportInformationResponseList CRITICALITY ignore EXTENSION NGAPIESupportInformationResponseList PRESENCE optional }, + ... +} +``` + +``` +TargetNSSAI ::= SEQUENCE (SIZE(1..maxnoofTargetS-NSSAIs)) OF TargetNSSAI-Item +``` + +``` +TargetNSSAI-Item ::= SEQUENCE { + s-NSSAI S-NSSAI, + iE-Extensions ProtocolExtensionContainer { {TargetNSSAI-Item-ExtIEs} } OPTIONAL, + ... +} +``` + +} + +TargetNSSAI-Item-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + +... + +} + +TargetNSSAIInformation ::= SEQUENCE { + +targetNSSAI TargetNSSAI, + +indexToRFSP IndexToRFSP, + +iE-Extensions ProtocolExtensionContainer { {TargetNSSAIInformation-Item-ExtIEs} } OPTIONAL, + +... + +} + +TargetNSSAIInformation-Item-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + +... + +} + +TargetRANNodeID ::= SEQUENCE { + +globalRANNodeID GlobalRANNodeID, + +selectedTAI TAI, + +iE-Extensions ProtocolExtensionContainer { {TargetRANNodeID-ExtIEs} } OPTIONAL, + +... + +} + +``` +TargetRANNodeID-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + {ID id-Selected-Target-SNPN-Identity CRITICALITY reject EXTENSION NID PRESENCE optional }, + ... +} + +TargetRANNodeID-RIM ::= SEQUENCE { + globalRANNodeID GlobalRANNodeID, + selectedTAI TAI, + iE-Extensions ProtocolExtensionContainer { {TargetRANNodeID-RIM-ExtIEs} } OPTIONAL, + ... +} + +TargetRANNodeID-RIM-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +TargetRANNodeID-SON ::= SEQUENCE { + globalRANNodeID GlobalRANNodeID, + selectedTAI TAI, + iE-Extensions ProtocolExtensionContainer { {TargetRANNodeID-SON-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +TargetRANNodeID-SON-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + {ID id-NR-CGI CRITICALITY ignore EXTENSION NR-CGI PRESENCE optional }, + ... +} + +TargetRNC-ID ::= SEQUENCE { + lAI LAI, + rNC-ID RNC-ID, + extendedRNC-ID ExtendedRNC-ID OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {TargetRNC-ID-ExtIEs} } OPTIONAL, + ... +} + +TargetRNC-ID-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +TargetToSource-TransparentContainer ::= OCTET STRING + +-- This IE includes a transparent container from the target RAN node to the source RAN node. + +-- The octets of the OCTET STRING are encoded according to the specifications of the target system. + +TargettoSource-Failure-TransparentContainer ::= OCTET STRING +``` + +-- This IE includes a transparent container from the target RAN node to the source RAN node. +-- The octets of the OCTET STRING are encoded according to the specifications of the target system (if applicable). + +``` +TimeBasedHandoverInformation ::= SEQUENCE { + hOWindowStart HandoverWindowStart, + hOWindowDuration HandoverWindowDuration, + iE-Extensions ProtocolExtensionContainer { {TimeBasedHandoverInformation-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +TimeBasedHandoverInformation-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +HandoverWindowStart ::= INTEGER (0..549755813887) +``` + +``` +HandoverWindowDuration ::= INTEGER (1..6000) +``` + +``` +TimerApproachForGUAMIRemoval ::= ENUMERATED { + apply-timer, + ... +} +``` + +TimeSinceFailure ::= INTEGER (0..172800, ...) + +TimeStamp ::= OCTET STRING (SIZE(4)) + +TimeSyncAssistanceInfo ::= SEQUENCE { + +timeDistributionIndication      ENUMERATED {enabled, disabled, ...}, + +uUTimeSyncErrorBudget          INTEGER (1..1000000, ...)                      OPTIONAL, + +-- The above IE shall be present if the Time Distribution Indication IE is set to the value "enabled" + +iE-Extensions                  ProtocolExtensionContainer { {TimeSyncAssistanceInfo-ExtIEs} } OPTIONAL, + +... + +} + +TimeSyncAssistanceInfo-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + +{ ID id-ClockQualityReportingControlInfo      CRITICALITY ignore      EXTENSION ClockQualityReportingControlInfo      PRESENCE optional}, + +... + +} + +TimeToWait ::= ENUMERATED {v1s, v2s, v5s, v10s, v20s, v60s, ...} + +TimeUEStayedInCell ::= INTEGER (0..4095) + +TimeUEStayedInCellEnhancedGranularity ::= INTEGER (0..40950) + +TMGI ::= OCTET STRING (SIZE(6)) + +TNAP-ID ::= OCTET STRING + +TNGF-ID ::= CHOICE { +    tNGF-ID              BIT STRING (SIZE(32, ...)), +    choice-Extensions    ProtocolIE-SingleContainer { {TNGF-ID-ExtIEs} } +} + +TNGF-ID-ExtIEs NGAP-PROTOCOL-IES ::= { +    ... +} + +TNLAddressWeightFactor ::= INTEGER (0..255) + +TNLAssociationList ::= SEQUENCE (SIZE(1..maxnoofTNLAssociations)) OF TNLAssociationItem + +TNLAssociationItem ::= SEQUENCE { +    tNLAssociationAddress    CPTransportLayerInformation, +    cause                    Cause, +    iE-Extensions          ProtocolExtensionContainer { {TNLAssociationItem-ExtIEs} } OPTIONAL, +    ... +} + +``` +TNLAssociationItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +TNLAssociationUsage ::= ENUMERATED { +``` + +``` + ue, +``` + +``` + non-ue, +``` + +``` + both, +``` + +``` + ... +``` + +``` +} +``` + +``` +ToearlyIntersystemHO ::= SEQUENCE { +``` + +``` + sourcecellID EUTRA-CGI, +``` + +``` + failurecellID NGRAN-CGI, +``` + +``` + uERLFReportContainer UERLFReportContainer OPTIONAL, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { ToearlyIntersystemHO-ExtIEs} } OPTIONAL, +``` + +``` + ... +``` + +``` +} +``` + +``` +ToearlyIntersystemHO-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +TraceActivation ::= SEQUENCE { + nGRANTraceID NGRANTraceID, + interfacesToTrace InterfacesToTrace, + traceDepth TraceDepth, + traceCollectionEntityIPAddress TransportLayerAddress, + iE-Extensions ProtocolExtensionContainer { {TraceActivation-ExtIEs} } OPTIONAL, + ... +} + +TraceActivation-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-MDTConfiguration CRITICALITY ignore EXTENSION MDT-Configuration PRESENCE optional }| + { ID id-TraceCollectionEntityURI CRITICALITY ignore EXTENSION URI-address PRESENCE optional }, + ... +} + +TraceDepth ::= ENUMERATED { + minimum, + medium, + maximum, + minimumWithoutVendorSpecificExtension, + mediumWithoutVendorSpecificExtension, + maximumWithoutVendorSpecificExtension, +} +``` + +``` + ... +} + +TrafficLoadReductionIndication ::= INTEGER (1..99) + +TransportLayerAddress ::= BIT STRING (SIZE(1..160, ...)) + +TypeOfError ::= ENUMERATED { + not-understood, + missing, + ... +} + +TAIBasedMDT ::= SEQUENCE { + tAIListforMDT TAIListforMDT, + iE-Extensions ProtocolExtensionContainer { {TAIBasedMDT-ExtIEs} } OPTIONAL, + ... +} + +TAIBasedMDT-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +TAIListforMDT ::= SEQUENCE (SIZE(1..maxnoofTAforMDT)) OF TAI +``` + +``` +TAIBasedQMC ::= SEQUENCE { + tAIListforQMC TAIListforQMC, + iE-Extensions ProtocolExtensionContainer { {TAIBasedQMC-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +TAIBasedQMC-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +TAIListforQMC ::= SEQUENCE (SIZE(1..maxnoofTAforQMC)) OF TAI +``` + +``` +TABasedQMC ::= SEQUENCE { + tAListforQMC TAListforQMC, + iE-Extensions ProtocolExtensionContainer { {TABasedQMC-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +TABasedQMC-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +TAListforQMC ::= SEQUENCE (SIZE(1..maxnoofTAforQMC)) OF TAC + +TABasedMDT ::= SEQUENCE { +    tAListforMDT    TAListforMDT, +    iE-Extensions    ProtocolExtensionContainer { {TABasedMDT-ExtIEs} } OPTIONAL, +    ... +} + +TABasedMDT-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +    ... +} + +TAListforMDT ::= SEQUENCE (SIZE(1..maxnoofTAforMDT)) OF TAC + +Threshold-RSRP ::= INTEGER(0..127) + +Threshold-RSRQ ::= INTEGER(0..127) + +Threshold-SINR ::= INTEGER(0..127) + +TimeToTrigger ::= ENUMERATED {ms0, ms40, ms64, ms80, ms100, ms128, ms160, ms256, ms320, ms480, ms512, ms640, ms1024, ms1280, ms2560, ms5120} + +TLContainer ::= OCTET STRING + +TWAP-ID ::= OCTET STRING + +TWIF-ID ::= CHOICE { +    tWIF-ID              BIT STRING (SIZE(32, ...)), +    choice-Extensions    ProtocolIE-SingleContainer { {TWIF-ID-ExtIEs} } +} + +TWIF-ID-ExtIEs NGAP-PROTOCOL-IES ::= { +    ... +} + +TSCAssistanceInformation ::= SEQUENCE { +    periodicity          Periodicity, +    burstArrivalTime    BurstArrivalTime                                    OPTIONAL, +    iE-Extensions      ProtocolExtensionContainer { {TSCAssistanceInformation-ExtIEs} }    OPTIONAL, +    ... +} + +TSCAssistanceInformation-ExtIEs NGAP-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 NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +TSCTrafficCharacteristicsFeedback ::= SEQUENCE { + tSCFeedbackInformationDL TSCFeedbackInformation OPTIONAL, + tSCFeedbackInformationUL TSCFeedbackInformation OPTIONAL, + iE-Extensions ProtocolExtensionContainer { TSCTrafficCharacteristicsFeedback-ExtIEs } OPTIONAL, + ... +} +``` + +``` +TSCTrafficCharacteristicsFeedback-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +TSCFeedbackInformation ::= SEQUENCE { + burstArrivalTimeOffset INTEGER (-640000..640000, ...), + adjustedPeriodicity Periodicity OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { TSCFeedbackInformation-ExtIEs} } OPTIONAL, + ... +} + +TSCFeedbackInformation-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- U + +UEAggregateMaximumBitRate ::= SEQUENCE { + uEAggregateMaximumBitRateDL BitRate, + uEAggregateMaximumBitRateUL BitRate, + iE-Extensions ProtocolExtensionContainer { {UEAggregateMaximumBitRate-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +} +``` + +``` +UEAggregateMaximumBitRate-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +UEAppLayerMeasInfoList ::= SEQUENCE (SIZE(1..maxnoofUEAppLayerMeas)) OF UEAppLayerMeasInfoItem +``` + +``` +UEAppLayerMeasInfoItem ::= SEQUENCE { +``` + +``` + uEAppLayerMeasConfigInfo UEAppLayerMeasConfigInfo, +``` + +``` + iE-Extensions ProtocolExtensionContainer { UEAppLayerMeasInfoItem-ExtIEs } OPTIONAL, +``` + +``` + ... +``` + +``` +} +``` + +``` +UEAppLayerMeasInfoItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +UEAppLayerMeasConfigInfo ::= SEQUENCE { +``` + +``` + qoEReference QoEReference, +``` + +``` + serviceType ServiceType, +``` + +``` + areaScopeOfQMC AreaScopeOfQMC OPTIONAL, +``` + +``` + measCollEntityIPAddress TransportLayerAddress, +``` + +``` + + qoEMeasurementStatus ENUMERATED {ongoing,...} OPTIONAL, + containerForAppLayerMeasConfig OCTET STRING (SIZE(1..8000)) OPTIONAL, + measConfigAppLayerID INTEGER (0..15, ...) OPTIONAL, + sliceSupportListQMC SliceSupportListQMC OPTIONAL, + mDT-AlignmentInfo MDT-AlignmentInfo OPTIONAL, + availableRANVisibleQoEMetrics AvailableRANVisibleQoEMetrics OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { UEAppLayerMeasConfigInfo-ExtIEs} } OPTIONAL, + ... +} + +UEAppLayerMeasConfigInfo-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-AssistanceInformationQoE-Meas CRITICALITY ignore EXTENSION AssistanceInformationQoE-Meas PRESENCE optional } | + { ID id-MBSCommServiceType CRITICALITY ignore EXTENSION MBSCommServiceType PRESENCE optional }, + ... +} + +UE-associatedLogicalNG-connectionList ::= SEQUENCE (SIZE(1..maxnoofNGConnectionsToReset)) OF UE-associatedLogicalNG-connectionItem + +UE-associatedLogicalNG-connectionItem ::= SEQUENCE { + aMF-UE-NGAP-ID AMF-UE-NGAP-ID OPTIONAL, + rAN-UE-NGAP-ID RAN-UE-NGAP-ID OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {UE-associatedLogicalNG-connectionItem-ExtIEs} } OPTIONAL, + ... +} + +``` + +} + +UE-associatedLogicalNG-connectionItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + +... + +} + +UECapabilityInfoRequest ::= ENUMERATED { + +requested, + +... + +} + +UEContextRequest ::= ENUMERATED {requested, ...} + +UEContextResumeRequestTransfer ::= SEQUENCE { + +    qosFlowFailedToResumeList                      QosFlowListWithCause                      OPTIONAL, + +    iE-Extensions              ProtocolExtensionContainer { {UEContextResumeRequestTransfer-ExtIEs} }      OPTIONAL, + +    ... + +} + +UEContextResumeRequestTransfer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + +... + +} + +``` +UEContextResumeResponseTransfer ::= SEQUENCE { + qosFlowFailedToResumeList QosFlowListWithCause OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {UEContextResumeResponseTransfer-ExtIEs} } OPTIONAL, + ... +} + +UEContextResumeResponseTransfer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +UEContextSuspendRequestTransfer ::= SEQUENCE { + suspendIndicator SuspendIndicator OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {UEContextSuspendRequestTransfer-ExtIEs} } OPTIONAL, + ... +} + +UEContextSuspendRequestTransfer-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +UE-DifferentiationInfo ::= SEQUENCE { + periodicCommunicationIndicator ENUMERATED {periodically, ondemand, ... } OPTIONAL, +``` + +``` + periodicTime INTEGER (1..3600, ...) OPTIONAL, + scheduledCommunicationTime ScheduledCommunicationTime OPTIONAL, + stationaryIndication ENUMERATED {stationary, mobile, ...} OPTIONAL, + trafficProfile ENUMERATED {single-packet, dual-packets, multiple-packets, ...} OPTIONAL, + batteryIndication ENUMERATED {battery-powered, battery-powered-not-rechargeable-or-replaceable, not-battery-powered, ...} OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { UE-DifferentiationInfo-ExtIEs} } OPTIONAL, + ... +} + +UE-DifferentiationInfo-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +UEHistoryInformation ::= SEQUENCE (SIZE(1..maxnoofCellsInUEHistoryInfo)) OF LastVisitedCellItem + +UEHistoryInformationFromTheUE ::= CHOICE { + nR NRMobilityHistoryReport, + choice-Extensions ProtocolIE-SingleContainer { {UEHistoryInformationFromTheUE-ExtIEs} } +} + +UEHistoryInformationFromTheUE-ExtIEs NGAP-PROTOCOL-IES ::= { + ... +} +``` + +``` +UEIdentityIndexValue ::= CHOICE { + indexLength10 BIT STRING (SIZE(10)), + choice-Extensions ProtocolIE-SingleContainer { {UEIdentityIndexValue-ExtIEs} } +} +``` + +``` +UEIdentityIndexValue-ExtIEs NGAP-PROTOCOL-IES ::= { + ... +} +``` + +``` +UE-NGAP-IDs ::= CHOICE { + uE-NGAP-ID-pair UE-NGAP-ID-pair, + aMF-UE-NGAP-ID AMF-UE-NGAP-ID, + choice-Extensions ProtocolIE-SingleContainer { {UE-NGAP-IDs-ExtIEs} } +} +``` + +``` +UE-NGAP-IDs-ExtIEs NGAP-PROTOCOL-IES ::= { + ... +} +``` + +``` +UE-NGAP-ID-pair ::= SEQUENCE{ + aMF-UE-NGAP-ID AMF-UE-NGAP-ID, + rAN-UE-NGAP-ID RAN-UE-NGAP-ID, +} +``` + +``` + iE-Extensions ProtocolExtensionContainer { {UE-NGAP-ID-pair-ExtIEs} } OPTIONAL, + ... +} + +UE-NGAP-ID-pair-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +UEPagingIdentity ::= CHOICE { + fiveG-S-TMSI FiveG-S-TMSI, + choice-Extensions ProtocolIE-SingleContainer { {UEPagingIdentity-ExtIEs} } +} + +UEPagingIdentity-ExtIEs NGAP-PROTOCOL-IES ::= { + ... +} + +UEPresence ::= ENUMERATED {in, out, unknown, ...} + +UEPresenceInAreaOfInterestList ::= SEQUENCE (SIZE(1..maxnoofAoI)) OF UEPresenceInAreaOfInterestItem + +UEPresenceInAreaOfInterestItem ::= SEQUENCE { + locationReportingReferenceID LocationReportingReferenceID, +``` + +``` + uEPresence UEPresence, + iE-Extensions ProtocolExtensionContainer { {UEPresenceInAreaOfInterestItem-ExtIEs} } OPTIONAL, + ... +} + +UEPresenceInAreaOfInterestItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +UERadioCapability ::= OCTET STRING + +UERadioCapabilityForPaging ::= SEQUENCE { + uERadioCapabilityForPagingOfNR UERadioCapabilityForPagingOfNR OPTIONAL, + uERadioCapabilityForPagingOfEUTRA UERadioCapabilityForPagingOfEUTRA OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {UERadioCapabilityForPaging-ExtIEs} } OPTIONAL, + ... +} + +UERadioCapabilityForPaging-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-UERadioCapabilityForPagingOfNB-IoT CRITICALITY ignore EXTENSION UERadioCapabilityForPagingOfNB-IoT PRESENCE optional }, + ... +} +``` + +UERadioCapabilityForPagingOfNB-IoT ::= OCTET STRING + +UERadioCapabilityForPagingOfNR ::= OCTET STRING + +UERadioCapabilityForPagingOfEUTRA ::= OCTET STRING + +UERadioCapabilityID ::= OCTET STRING + +UERetentionInformation ::= ENUMERATED { +    ues-retained, +    ... +} + +UERLFReportContainer ::= CHOICE { +    nR            NRUERLFReportContainer, +    lTE           LTEUERLFReportContainer, +    choice-Extensions    ProtocolIE-SingleContainer { {UERLFReportContainer-ExtIEs} } +} + +UERLFReportContainer-ExtIEs NGAP-PROTOCOL-IES ::= { +    ... +} + +``` +UESecurityCapabilities ::= SEQUENCE { + nRencryptionAlgorithms NRencryptionAlgorithms, + nRintegrityProtectionAlgorithms NRintegrityProtectionAlgorithms, + eUTRAencryptionAlgorithms EUTRAencryptionAlgorithms, + eUTRAintegrityProtectionAlgorithms EUTRAintegrityProtectionAlgorithms, + iE-Extensions ProtocolExtensionContainer { {UESecurityCapabilities-ExtIEs} } OPTIONAL, + ... +} + +UESecurityCapabilities-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +UESliceMaximumBitRateList ::= SEQUENCE (SIZE(1..maxnoofAllowedS-NSSAIs)) OF UESliceMaximumBitRateItem + +UESliceMaximumBitRateItem ::= SEQUENCE { + s-NSSAI S-NSSAI, + uESliceMaximumBitRateDL BitRate, + uESliceMaximumBitRateUL BitRate, + iE-Extensions ProtocolExtensionContainer { { UESliceMaximumBitRateItem-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +UESliceMaximumBitRateItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +UE-UP-CIoT-Support ::= ENUMERATED {supported, ...} + +UL-CP-SecurityInformation ::= SEQUENCE { + ul-NAS-MAC UL-NAS-MAC, + ul-NAS-Count UL-NAS-Count, + iE-Extensions ProtocolExtensionContainer { { UL-CP-SecurityInformation-ExtIEs} } OPTIONAL, + ... +} + +UL-CP-SecurityInformation-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +UL-NAS-MAC ::= BIT STRING (SIZE (16)) + +UL-NAS-Count ::= BIT STRING (SIZE (5)) + +UL-NGU-UP-TNLModifyList ::= SEQUENCE (SIZE(1..maxnoofMultiConnectivity)) OF UL-NGU-UP-TNLModifyItem +``` + +``` +UL-NGU-UP-TNLModifyItem ::= SEQUENCE { + uL-NGU-UP-TNLInformation UPTransportLayerInformation, + dL-NGU-UP-TNLInformation UPTransportLayerInformation, + iE-Extensions ProtocolExtensionContainer { {UL-NGU-UP-TNLModifyItem-ExtIEs} } OPTIONAL, + ... +} + +UL-NGU-UP-TNLModifyItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-RedundantUL-NGU-UP-TNLInformation CRITICALITY ignore EXTENSION UPTransportLayerInformation PRESENCE optional } | + { ID id-RedundantDL-NGU-UP-TNLInformation CRITICALITY ignore EXTENSION UPTransportLayerInformation PRESENCE optional }, + ... +} + +UnavailableGUAMIList ::= SEQUENCE (SIZE(1..maxnooServedGUAMIs)) OF UnavailableGUAMIItem + +UnavailableGUAMIItem ::= SEQUENCE { + gUAMI GUAMI, + timerApproachForGUAMIRemoval TimerApproachForGUAMIRemoval OPTIONAL, + backupAMFName AMFName OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {UnavailableGUAMIItem-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +UnavailableGUAMIItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +ULForwarding ::= ENUMERATED { + ul-forwarding-proposed, + ... +} +``` + +``` +UpdateFeedback ::= BIT STRING (SIZE(8, ...)) +``` + +``` +UPTransportLayerInformation ::= CHOICE { + gTPTunnel GTPTunnel, + choice-Extensions ProtocolIE-SingleContainer { {UPTransportLayerInformation-ExtIEs} } +} +``` + +``` +UPTransportLayerInformation-ExtIEs NGAP-PROTOCOL-IES ::= { + ... +} +``` + +``` +UPTransportLayerInformationList ::= SEQUENCE (SIZE(1..maxnoofMultiConnectivityMinusOne)) OF UPTransportLayerInformationItem +``` + +``` +UPTransportLayerInformationItem ::= SEQUENCE { + nGU-UP-TNLInformation UPTransportLayerInformation, + iE-Extensions ProtocolExtensionContainer { {UPTransportLayerInformationItem-ExtIEs} } OPTIONAL, + ... +} + +UPTransportLayerInformationItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-CommonNetworkInstance CRITICALITY ignore EXTENSION CommonNetworkInstance PRESENCE optional }, + ... +} + +UPTransportLayerInformationPairList ::= SEQUENCE (SIZE(1..maxnoofMultiConnectivityMinusOne)) OF UPTransportLayerInformationPairItem + +UPTransportLayerInformationPairItem ::= SEQUENCE { + uL-NGU-UP-TNLInformation UPTransportLayerInformation, + dL-NGU-UP-TNLInformation UPTransportLayerInformation, + iE-Extensions ProtocolExtensionContainer { {UPTransportLayerInformationPairItem-ExtIEs} } OPTIONAL, + ... +} + +UPTransportLayerInformationPairItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +} + +URI-address ::= VisibleString + +UserLocationInformation ::= CHOICE { + userLocationInformationEUTRA UserLocationInformationEUTRA, + userLocationInformationNR UserLocationInformationNR, + userLocationInformationN3IWF UserLocationInformationN3IWF, + choice-Extensions ProtocolIE-SingleContainer { {UserLocationInformation-ExtIEs} } +} + +UserLocationInformation-ExtIEs NGAP-PROTOCOL-IES ::= { + { ID id-UserLocationInformationTNGF CRITICALITY ignore TYPE UserLocationInformationTNGF PRESENCE mandatory }| + { ID id-UserLocationInformationTWIF CRITICALITY ignore TYPE UserLocationInformationTWIF PRESENCE mandatory }| + { ID id-UserLocationInformationW-AGF CRITICALITY ignore TYPE UserLocationInformationW-AGF PRESENCE mandatory }, + ... +} + +UserLocationInformationEUTRA ::= SEQUENCE { + eUTRA-CGI EUTRA-CGI, + tAI TAI, + timeStamp TimeStamp OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {UserLocationInformationEUTRA-ExtIEs} } OPTIONAL, +``` + +``` + ... +} + +UserLocationInformationEUTRA-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-PSCellInformation CRITICALITY ignore EXTENSION NGRAN-CGI PRESENCE optional}, + ... +} + +UserLocationInformationN3IWF ::= SEQUENCE { + iPAddress TransportLayerAddress, + portNumber PortNumber, + iE-Extensions ProtocolExtensionContainer { {UserLocationInformationN3IWF-ExtIEs} } OPTIONAL, + ... +} + +UserLocationInformationN3IWF-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-TAI CRITICALITY ignore EXTENSION TAI PRESENCE optional }, + ... +} + +UserLocationInformationTNGF ::= SEQUENCE { + tNAP-ID TNAP-ID, + iPAddress TransportLayerAddress, +``` + +``` +portNumber PortNumber OPTIONAL, +iE-Extensions ProtocolExtensionContainer { {UserLocationInformationTNGF-ExtIEs} } OPTIONAL, +... +} + +UserLocationInformationTNGF-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-TAI CRITICALITY ignore EXTENSION TAI PRESENCE optional }, + ... +} + +UserLocationInformationTWIF ::= SEQUENCE { + tWAP-ID TWAP-ID, + ipAddress TransportLayerAddress, + portNumber PortNumber OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {UserLocationInformationTWIF-ExtIEs} } OPTIONAL, + ... +} + +UserLocationInformationTWIF-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-TAI CRITICALITY ignore EXTENSION TAI PRESENCE optional }, + ... +} +``` + +``` + +UserLocationInformationW-AGF ::= CHOICE { + globalLine-ID GlobalLine-ID, + hFCNode-ID HFCNode-ID, + choice-Extensions ProtocolIE-SingleContainer { { UserLocationInformationW-AGF-ExtIEs} } +} + +UserLocationInformationW-AGF-ExtIEs NGAP-PROTOCOL-IES ::= { + { ID id-GlobalCable-ID CRITICALITY ignore TYPE GlobalCable-ID PRESENCE mandatory }| + { ID id-HFCNode-ID-new CRITICALITY ignore TYPE HFCNode-ID-new PRESENCE mandatory }| + { ID id-GlobalCable-ID-new CRITICALITY ignore TYPE GlobalCable-ID-new PRESENCE mandatory }, + ... +} + +UserLocationInformationNR ::= SEQUENCE { + nR-CGI NR-CGI, + tAI TAI, + timeStamp Timestamp OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {UserLocationInformationNR-ExtIEs} } OPTIONAL, + ... +} + +UserLocationInformationNR-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-PSCellInformation CRITICALITY ignore EXTENSION NGRAN-CGI PRESENCE optional }| + +``` + +``` +{ ID id-NID CRITICALITY reject EXTENSION NID PRESENCE optional }| +{ ID id-NRNTNTAIInformation CRITICALITY ignore EXTENSION NRNTNTAIInformation PRESENCE optional }| +{ ID id-IAB-MTUserLocationInformation CRITICALITY ignore EXTENSION IAB-MTUserLocationInformation PRESENCE optional }, +... +} +``` + +``` +UserPlaneSecurityInformation ::= SEQUENCE { + securityResult SecurityResult, + securityIndication SecurityIndication, + iE-Extensions ProtocolExtensionContainer { {UserPlaneSecurityInformation-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +UserPlaneSecurityInformation-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +-- V +``` + +``` +VolumeTimedReportList ::= SEQUENCE (SIZE(1..maxnoofTimePeriods)) OF VolumeTimedReport-Item +``` + +``` +VolumeTimedReport-Item ::= SEQUENCE { + startTimestamp OCTET STRING (SIZE(4)), +``` + +``` +endTimeStamp OCTET STRING (SIZE(4)), +usageCountUL INTEGER (0..18446744073709551615), +usageCountDL INTEGER (0..18446744073709551615), +iE-Extensions ProtocolExtensionContainer { {VolumeTimedReport-Item-ExtIEs} } OPTIONAL, +... +} + +VolumeTimedReport-Item-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- W + +W-AGF-ID ::= CHOICE { + w-AGF-ID BIT STRING (SIZE(16, ...)), + choice-Extensions ProtocolIE-SingleContainer { {W-AGF-ID-ExtIEs} } +} + +W-AGF-ID-ExtIEs NGAP-PROTOCOL-IES ::= { + ... +} + +WarningAreaCoordinates ::= OCTET STRING (SIZE(1..1024)) +``` + +``` +WarningAreaList ::= CHOICE { + eUTRA-CGIListForWarning EUTRA-CGIListForWarning, + nR-CGIListForWarning NR-CGIListForWarning, + tAIListForWarning TAIListForWarning, + emergencyAreaIDList EmergencyAreaIDList, + choice-Extensions ProtocolIE-SingleContainer { {WarningAreaList-ExtIEs} } +} + +WarningAreaList-ExtIEs NGAP-PROTOCOL-IES ::= { + ... +} + +WarningMessageContents ::= OCTET STRING (SIZE(1..9600)) + +WarningSecurityInfo ::= OCTET STRING (SIZE(50)) + +WarningType ::= OCTET STRING (SIZE(2)) + +WLANMeasurementConfiguration ::= SEQUENCE { + wlanMeasConfig WLANMeasConfig, + wlanMeasConfigNameList WLANMeasConfigNameList OPTIONAL, + wlan-rssi ENUMERATED {true, ...} OPTIONAL, +``` + +``` +wlan-rtt ENUMERATED {true, ...} OPTIONAL, +iE-Extensions ProtocolExtensionContainer { { WLANMeasurementConfiguration-ExtIEs } } OPTIONAL, +... +} + +WLANMeasurementConfiguration-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +WLANMeasConfigNameList ::= SEQUENCE (SIZE(1..maxnoofWLANName)) OF WLANMeasConfigNameItem + +WLANMeasConfigNameItem ::= SEQUENCE { + wLANName wLANName, + iE-Extensions ProtocolExtensionContainer { { WLANMeasConfigNameItem-ExtIEs } } OPTIONAL, + ... +} + +WLANMeasConfigNameItem-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +WLANMeasConfig ::= ENUMERATED {setup,...} +``` + +WLANNName ::= OCTET STRING (SIZE (1..32)) + +WUS-Assistance-Information ::= SEQUENCE { +    pagingProbabilityInformation            PagingProbabilityInformation, +    iE-Extensions            ProtocolExtensionContainer { { WUS-Assistance-Information-ExtIEs } } OPTIONAL, +    ... +} + +WUS-Assistance-Information-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { +    ... +} + +-- X + +XnExtTLAs ::= SEQUENCE (SIZE(1..maxnoofXnExtTLAs)) OF XnExtTLA-Item + +XnExtTLA-Item ::= SEQUENCE { +    iPsecTLA                    TransportLayerAddress                    OPTIONAL, +    gTP-TLAs                    XnGTP-TLAs                    OPTIONAL, +    iE-Extensions            ProtocolExtensionContainer { {XnExtTLA-Item-ExtIEs} } OPTIONAL, +    ... +} + +``` +XnExtTLA-Item-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + { ID id-SCTP-TLAs CRITICALITY ignore EXTENSION SCTP-TLAs PRESENCE optional }, + ... +} + +XnGTP-TLAs ::= SEQUENCE (SIZE(1..maxnoofXnGTP-TLAs)) OF TransportLayerAddress + +XnTLAs ::= SEQUENCE (SIZE(1..maxnoofXnTLAs)) OF TransportLayerAddress + +XnTNLConfigurationInfo ::= SEQUENCE { + xnTransportLayerAddresses XnTLAs, + xnExtendedTransportLayerAddresses XnExtTLAs OPTIONAL, + iE-Extensions ProtocolExtensionContainer { XnTNLConfigurationInfo-ExtIEs } OPTIONAL, + ... +} + +XnTNLConfigurationInfo-ExtIEs NGAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- Y + +-- Z +``` + +END + +-- ASN1STOP + +## 9.4.6 Common Definitions + +-- ASN1START + +-- \*\*\*\*\* + +-- + +-- Common definitions + +-- + +-- \*\*\*\*\* + +NGAP-CommonDataTypes { + +itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + +ngran-Access (22) modules (3) ngap (1) version1 (1) ngap-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 + +``` + +``` + +-- +-- ***** + +NGAP-Constants { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + ngran-Access (22) modules (3) ngap (1) version1 (1) ngap-Constants (4) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- ***** + +-- +-- IE parameter types from other modules. +-- +-- ***** + +IMPORTS + + ProcedureCode, + ProtocolIE-ID + +FROM NGAP-CommonDataTypes; + +``` + +``` +-- ***** +-- +-- Elementary Procedures +-- +-- ***** + +id-AMFConfigurationUpdate ProcedureCode ::= 0 +id-AMFStatusIndication ProcedureCode ::= 1 +id-CellTrafficTrace ProcedureCode ::= 2 +id-DeactivateTrace ProcedureCode ::= 3 +id-DownlinkNASTransport ProcedureCode ::= 4 +id-DownlinkNonUEAssociatedNRPPaTransport ProcedureCode ::= 5 +id-DownlinkRANConfigurationTransfer ProcedureCode ::= 6 +id-DownlinkRANStatusTransfer ProcedureCode ::= 7 +id-DownlinkUEAssociatedNRPPaTransport ProcedureCode ::= 8 +id-ErrorIndication ProcedureCode ::= 9 +id-HandoverCancel ProcedureCode ::= 10 +id-HandoverNotification ProcedureCode ::= 11 +id-HandoverPreparation ProcedureCode ::= 12 +id-HandoverResourceAllocation ProcedureCode ::= 13 +id-InitialContextSetup ProcedureCode ::= 14 +id-InitialUEMessage ProcedureCode ::= 15 +``` + +| | | +|---------------------------------------|----------------------| +| id-LocationReportingControl | ProcedureCode ::= 16 | +| id-LocationReportingFailureIndication | ProcedureCode ::= 17 | +| id-LocationReport | ProcedureCode ::= 18 | +| id-NASNonDeliveryIndication | ProcedureCode ::= 19 | +| id-NGReset | ProcedureCode ::= 20 | +| id-NGSetup | ProcedureCode ::= 21 | +| id-OverloadStart | ProcedureCode ::= 22 | +| id-OverloadStop | ProcedureCode ::= 23 | +| id-Paging | ProcedureCode ::= 24 | +| id-PathSwitchRequest | ProcedureCode ::= 25 | +| id-PDUSessionResourceModify | ProcedureCode ::= 26 | +| id-PDUSessionResourceModifyIndication | ProcedureCode ::= 27 | +| id-PDUSessionResourceRelease | ProcedureCode ::= 28 | +| id-PDUSessionResourceSetup | ProcedureCode ::= 29 | +| id-PDUSessionResourceNotify | ProcedureCode ::= 30 | +| id-PrivateMessage | ProcedureCode ::= 31 | +| id-PWSCancel | ProcedureCode ::= 32 | +| id-PWSFailureIndication | ProcedureCode ::= 33 | +| id-PWSRestartIndication | ProcedureCode ::= 34 | +| id-RANConfigurationUpdate | ProcedureCode ::= 35 | +| id-RerouteNASRequest | ProcedureCode ::= 36 | +| id-RRCTInactiveTransitionReport | ProcedureCode ::= 37 | +| id-TraceFailureIndication | ProcedureCode ::= 38 | + +| | | +|----------------------------------------|----------------------| +| id-TraceStart | ProcedureCode ::= 39 | +| id-UEContextModification | ProcedureCode ::= 40 | +| id-UEContextRelease | ProcedureCode ::= 41 | +| id-UEContextReleaseRequest | ProcedureCode ::= 42 | +| id-UERadioCapabilityCheck | ProcedureCode ::= 43 | +| id-UERadioCapabilityInfoIndication | ProcedureCode ::= 44 | +| id-UETNLBindingRelease | ProcedureCode ::= 45 | +| id-UplinkNASTransport | ProcedureCode ::= 46 | +| id-UplinkNonUEAssociatedNRPPaTransport | ProcedureCode ::= 47 | +| id-UplinkRANConfigurationTransfer | ProcedureCode ::= 48 | +| id-UplinkRANStatusTransfer | ProcedureCode ::= 49 | +| id-UplinkUEAssociatedNRPPaTransport | ProcedureCode ::= 50 | +| id-WriteReplaceWarning | ProcedureCode ::= 51 | +| id-SecondaryRATDataUsageReport | ProcedureCode ::= 52 | +| id-UplinkRIMInformationTransfer | ProcedureCode ::= 53 | +| id-DownlinkRIMInformationTransfer | ProcedureCode ::= 54 | +| id-RetrieveUEInformation | ProcedureCode ::= 55 | +| id-UEInformationTransfer | ProcedureCode ::= 56 | +| id-RANCPRelocationIndication | ProcedureCode ::= 57 | +| id-UEContextResume | ProcedureCode ::= 58 | +| id-UEContextSuspend | ProcedureCode ::= 59 | +| id-UERadioCapabilityIDMapping | ProcedureCode ::= 60 | +| id-HandoverSuccess | ProcedureCode ::= 61 | + +| | | +|--------------------------------------|----------------------| +| id-UplinkRANEarlyStatusTransfer | ProcedureCode ::= 62 | +| id-DownlinkRANEarlyStatusTransfer | ProcedureCode ::= 63 | +| id-AMFCPRelocationIndication | ProcedureCode ::= 64 | +| id-ConnectionEstablishmentIndication | ProcedureCode ::= 65 | +| id-BroadcastSessionModification | ProcedureCode ::= 66 | +| id-BroadcastSessionRelease | ProcedureCode ::= 67 | +| id-BroadcastSessionSetup | ProcedureCode ::= 68 | +| id-DistributionSetup | ProcedureCode ::= 69 | +| id-DistributionRelease | ProcedureCode ::= 70 | +| id-MulticastSessionActivation | ProcedureCode ::= 71 | +| id-MulticastSessionDeactivation | ProcedureCode ::= 72 | +| id-MulticastSessionUpdate | ProcedureCode ::= 73 | +| id-MulticastGroupPaging | ProcedureCode ::= 74 | +| id-BroadcastSessionReleaseRequired | ProcedureCode ::= 75 | +| id-TimingSynchronisationStatus | ProcedureCode ::= 76 | +| id-TimingSynchronisationStatusReport | ProcedureCode ::= 77 | +| id-MTCommunicationHandling | ProcedureCode ::= 78 | +| id-RANPagingRequest | ProcedureCode ::= 79 | +| id-BroadcastSessionTransport | ProcedureCode ::= 80 | + +-- \*\*\*\*\* + +``` +-- + +-- Extension constants + +-- + +-- ***** + +maxPrivateIEs INTEGER ::= 65535 +maxProtocolExtensions INTEGER ::= 65535 +maxProtocolIEs INTEGER ::= 65535 + +-- ***** + +-- + +-- Lists + +-- + +-- ***** + +maxnoofAllowedAreas INTEGER ::= 16 +maxnoofAllowedCAGsperPLMN INTEGER ::= 256 +maxnoofAllowedS-NSSAIs INTEGER ::= 8 +maxnoofBluetoothName INTEGER ::= 4 +maxnoofBPLMNs INTEGER ::= 12 +maxnoofCAGSperCell INTEGER ::= 64 +maxnoofCellIDforMDT INTEGER ::= 32 +maxnoofCellIDforWarning INTEGER ::= 65535 +``` + +maxnoofCellinAoI INTEGER ::= 256 +maxnoofCellinEAI INTEGER ::= 65535 +maxnoofCellinTAI INTEGER ::= 65535 +maxnoofCellsforMBS INTEGER ::= 8192 +maxnoofCellsingNB INTEGER ::= 16384 +maxnoofCellsinngeNB INTEGER ::= 256 +maxnoofCellsinNGRANNode INTEGER ::= 16384 +maxnoofCellsinUEHistoryInfo INTEGER ::= 16 +maxnoofCellsUEMovingTrajectory INTEGER ::= 16 +maxnoofDRBs INTEGER ::= 32 +maxnoofEmergencyAreaID INTEGER ::= 65535 +maxnoofEAIforRestart INTEGER ::= 256 +maxnoofEPLMNs INTEGER ::= 15 +maxnoofEPLMNsPlusOne INTEGER ::= 16 +maxnoofE-RABs INTEGER ::= 256 +maxnoofErrors INTEGER ::= 256 +maxnoofExtSliceItems INTEGER ::= 65535 +maxnoofForbTACs INTEGER ::= 4096 +maxnoofFreqforMDT INTEGER ::= 8 +maxnoofMBSAreaSessionIDs INTEGER ::= 256 +maxnoofMBSFSAs INTEGER ::= 64 +maxnoofMBSQoSFlows INTEGER ::= 64 +maxnoofMBSSessions INTEGER ::= 32 + +| | | +|---------------------------------------------|-------------------| +| maxnoofMBSSessionsofUE | INTEGER ::= 256 | +| maxnoofMBSServiceAreaInformation | INTEGER ::= 256 | +| maxnoofMDTPLMNs | INTEGER ::= 16 | +| maxnoofMRBs | INTEGER ::= 32 | +| maxnoofMultiConnectivity | INTEGER ::= 4 | +| maxnoofMultiConnectivityMinusOne | INTEGER ::= 3 | +| maxnoofNeighPCIforMDT | INTEGER ::= 32 | +| maxnoofNGAPIESupportInfo | INTEGER ::= 32 | +| maxnoofNGConnectionsToReset | INTEGER ::= 65536 | +| maxnoofNRCellBands | INTEGER ::= 32 | +| maxnoofNSAGs | INTEGER ::= 256 | +| maxnoofPagingAreas | INTEGER ::= 64 | +| maxnoofPC5QoSFlows | INTEGER ::= 2048 | +| maxnoofPDUSessions | INTEGER ::= 256 | +| maxnoofPLMNs | INTEGER ::= 12 | +| maxnoofPSCellsPerPrimaryCellinUEHistoryInfo | INTEGER ::= 8 | +| maxnoofQoSFlows | INTEGER ::= 64 | +| maxnoofQoSParaSets | INTEGER ::= 8 | +| maxnoofRANNodeinAoI | INTEGER ::= 64 | +| maxnoofRecommendedCells | INTEGER ::= 16 | +| maxnoofRecommendedRANNodes | INTEGER ::= 16 | +| maxnoofAoI | INTEGER ::= 64 | +| maxnoofAoIMinusOne | INTEGER ::= 63 | + +| | | +|----------------------------|-------------------| +| maxnoofReportedCells | INTEGER ::= 256 | +| maxnoofSensorName | INTEGER ::= 3 | +| maxnoofServedGUAMIs | INTEGER ::= 256 | +| maxnoofSliceItems | INTEGER ::= 1024 | +| maxnoofSuccessfulHOReports | INTEGER ::= 64 | +| maxnoofTACs | INTEGER ::= 256 | +| maxnoofTACsinNTN | INTEGER ::= 12 | +| maxnoofTAforMDT | INTEGER ::= 8 | +| maxnoofTAIforInactive | INTEGER ::= 16 | +| maxnoofTAIforMBS | INTEGER ::= 1024 | +| maxnoofTAIforPaging | INTEGER ::= 16 | +| maxnoofTAIforRestart | INTEGER ::= 2048 | +| maxnoofTAIforWarning | INTEGER ::= 65535 | +| maxnoofTAInAoI | INTEGER ::= 16 | +| maxnoofTimePeriods | INTEGER ::= 2 | +| maxnoofTNLAssociations | INTEGER ::= 32 | +| maxnoofUEsforPaging | INTEGER ::= 4096 | +| maxnoofUETypes | INTEGER ::= 8 | +| maxnoofWLANNName | INTEGER ::= 4 | +| maxnoofXnExtTLAs | INTEGER ::= 16 | +| maxnoofXnGTP-TLAs | INTEGER ::= 16 | +| maxnoofXnTLAs | INTEGER ::= 2 | +| maxnoofCandidateCells | INTEGER ::= 32 | + +``` + +maxnoofTargetS-NSSAIs INTEGER ::= 8 +maxNRARFCN INTEGER ::= 3279165 +maxnoofCellIDforQMC INTEGER ::= 32 +maxnoofPLMNforQMC INTEGER ::= 16 +maxnoofUEAppLayerMeas INTEGER ::= 16 +maxnoofSNSSAIforQMC INTEGER ::= 16 +maxnoofTAforQMC INTEGER ::= 8 +maxnoofThresholdsForExcessPacketDelay INTEGER ::= 255 +maxnoofESNPNS INTEGER ::= 15 +maxnoofCandidateRelayUEs INTEGER ::= 32 +maxnoofSuccessfulPSCellChangeReports INTEGER ::= 64 +maxnoofCellsTSS INTEGER ::= 16384 +maxnoofPeriodicities INTEGER ::= 8 +maxnoofCAGforMDT INTEGER ::= 256 +maxnoofMDTSNPNS INTEGER ::= 16 +maxnoofPartiallyAllowedS-NSSAIs INTEGER ::= 8 + +``` + +``` + +-- ***** +-- +-- IEs +-- +-- ***** + +``` + +| | | +|------------------------------------------------|----------------------| +| id-AllowedNSSAI | ProtocolIE-ID ::= 0 | +| id-AMFName | ProtocolIE-ID ::= 1 | +| id-AMFOverloadResponse | ProtocolIE-ID ::= 2 | +| id-AMFSetID | ProtocolIE-ID ::= 3 | +| id-AMF-TNLAssociationFailedToSetupList | ProtocolIE-ID ::= 4 | +| id-AMF-TNLAssociationSetupList | ProtocolIE-ID ::= 5 | +| id-AMF-TNLAssociationToAddList | ProtocolIE-ID ::= 6 | +| id-AMF-TNLAssociationToRemoveList | ProtocolIE-ID ::= 7 | +| id-AMF-TNLAssociationToUpdateList | ProtocolIE-ID ::= 8 | +| id-AMFTrafficLoadReductionIndication | ProtocolIE-ID ::= 9 | +| id-AMF-UE-NGAP-ID | ProtocolIE-ID ::= 10 | +| id-AssistanceDataForPaging | ProtocolIE-ID ::= 11 | +| id-BroadcastCancelledAreaList | ProtocolIE-ID ::= 12 | +| id-BroadcastCompletedAreaList | ProtocolIE-ID ::= 13 | +| id-CancelAllWarningMessages | ProtocolIE-ID ::= 14 | +| id-Cause | ProtocolIE-ID ::= 15 | +| id-CellIDListForRestart | ProtocolIE-ID ::= 16 | +| id-ConcurrentWarningMessageInd | ProtocolIE-ID ::= 17 | +| id-CoreNetworkAssistanceInformationForInactive | ProtocolIE-ID ::= 18 | +| id-CriticalityDiagnostics | ProtocolIE-ID ::= 19 | +| id-DataCodingScheme | ProtocolIE-ID ::= 20 | +| id-DefaultPagingDRX | ProtocolIE-ID ::= 21 | + +| | | +|-----------------------------------------------|----------------------| +| id-DirectForwardingPathAvailability | ProtocolIE-ID ::= 22 | +| id-EmergencyAreaIDListForRestart | ProtocolIE-ID ::= 23 | +| id-EmergencyFallbackIndicator | ProtocolIE-ID ::= 24 | +| id-EUTRA-CGI | ProtocolIE-ID ::= 25 | +| id-FiveG-S-TMSI | ProtocolIE-ID ::= 26 | +| id-GlobalRANNodeID | ProtocolIE-ID ::= 27 | +| id-GUAMI | ProtocolIE-ID ::= 28 | +| id-HandoverType | ProtocolIE-ID ::= 29 | +| id-IMSVoiceSupportIndicator | ProtocolIE-ID ::= 30 | +| id-IndexToRFSP | ProtocolIE-ID ::= 31 | +| id-InfoOnRecommendedCellsAndRANNodesForPaging | ProtocolIE-ID ::= 32 | +| id-LocationReportingRequestType | ProtocolIE-ID ::= 33 | +| id-MaskedIMEISV | ProtocolIE-ID ::= 34 | +| id-MessageIdentifier | ProtocolIE-ID ::= 35 | +| id-MobilityRestrictionList | ProtocolIE-ID ::= 36 | +| id-NASC | ProtocolIE-ID ::= 37 | +| id-NAS-PDU | ProtocolIE-ID ::= 38 | +| id-NASSecurityParametersFromNGRAN | ProtocolIE-ID ::= 39 | +| id-NewAMF-UE-NGAP-ID | ProtocolIE-ID ::= 40 | +| id-NewSecurityContextInd | ProtocolIE-ID ::= 41 | +| id-NGAP-Message | ProtocolIE-ID ::= 42 | +| id-NGRAN-CGI | ProtocolIE-ID ::= 43 | +| id-NGRANTraceID | ProtocolIE-ID ::= 44 | + +| | | +|-----------------------------------------------|----------------------| +| id-NR-CGI | ProtocolIE-ID ::= 45 | +| id-NRPPa-PDU | ProtocolIE-ID ::= 46 | +| id-NumberOfBroadcastsRequested | ProtocolIE-ID ::= 47 | +| id-OldAMF | ProtocolIE-ID ::= 48 | +| id-OverloadStartNSSAIList | ProtocolIE-ID ::= 49 | +| id-PagingDRX | ProtocolIE-ID ::= 50 | +| id-PagingOrigin | ProtocolIE-ID ::= 51 | +| id-PagingPriority | ProtocolIE-ID ::= 52 | +| id-PDUSessionResourceAdmittedList | ProtocolIE-ID ::= 53 | +| id-PDUSessionResourceFailedToModifyListModRes | ProtocolIE-ID ::= 54 | +| id-PDUSessionResourceFailedToSetupListCxtRes | ProtocolIE-ID ::= 55 | +| id-PDUSessionResourceFailedToSetupListHOAck | ProtocolIE-ID ::= 56 | +| id-PDUSessionResourceFailedToSetupListPSReq | ProtocolIE-ID ::= 57 | +| id-PDUSessionResourceFailedToSetupListSURes | ProtocolIE-ID ::= 58 | +| id-PDUSessionResourceHandoverList | ProtocolIE-ID ::= 59 | +| id-PDUSessionResourceListCxtRelCpl | ProtocolIE-ID ::= 60 | +| id-PDUSessionResourceListHORqd | ProtocolIE-ID ::= 61 | +| id-PDUSessionResourceModifyListModCfm | ProtocolIE-ID ::= 62 | +| id-PDUSessionResourceModifyListModInd | ProtocolIE-ID ::= 63 | +| id-PDUSessionResourceModifyListModReq | ProtocolIE-ID ::= 64 | +| id-PDUSessionResourceModifyListModRes | ProtocolIE-ID ::= 65 | +| id-PDUSessionResourceNotifyList | ProtocolIE-ID ::= 66 | +| id-PDUSessionResourceReleasedListNot | ProtocolIE-ID ::= 67 | + +| | | +|-------------------------------------------|----------------------| +| id-PDUSessionResourceReleasedListPSAck | ProtocolIE-ID ::= 68 | +| id-PDUSessionResourceReleasedListPSFail | ProtocolIE-ID ::= 69 | +| id-PDUSessionResourceReleasedListRelRes | ProtocolIE-ID ::= 70 | +| id-PDUSessionResourceSetupListCxtReq | ProtocolIE-ID ::= 71 | +| id-PDUSessionResourceSetupListCxtRes | ProtocolIE-ID ::= 72 | +| id-PDUSessionResourceSetupListHOReq | ProtocolIE-ID ::= 73 | +| id-PDUSessionResourceSetupListSUReq | ProtocolIE-ID ::= 74 | +| id-PDUSessionResourceSetupListSUSRes | ProtocolIE-ID ::= 75 | +| id-PDUSessionResourceToBeSwitchedDLList | ProtocolIE-ID ::= 76 | +| id-PDUSessionResourceSwitchedList | ProtocolIE-ID ::= 77 | +| id-PDUSessionResourceToReleaseListHOCmd | ProtocolIE-ID ::= 78 | +| id-PDUSessionResourceToReleaseListRelCmd | ProtocolIE-ID ::= 79 | +| id-PLMNSupportList | ProtocolIE-ID ::= 80 | +| id-PWSFailedCellIDList | ProtocolIE-ID ::= 81 | +| id-RANNodeName | ProtocolIE-ID ::= 82 | +| id-RANPagingPriority | ProtocolIE-ID ::= 83 | +| id-RANStatusTransfer-TransparentContainer | ProtocolIE-ID ::= 84 | +| id-RAN-UE-NGAP-ID | ProtocolIE-ID ::= 85 | +| id-RelativeAMFCapacity | ProtocolIE-ID ::= 86 | +| id-RepetitionPeriod | ProtocolIE-ID ::= 87 | +| id-ResetType | ProtocolIE-ID ::= 88 | +| id-RoutingID | ProtocolIE-ID ::= 89 | +| id-RRCEstablishmentCause | ProtocolIE-ID ::= 90 | + +| | | +|------------------------------------------|-----------------------| +| id-RRCInactiveTransitionReportRequest | ProtocolIE-ID ::= 91 | +| id-RRCState | ProtocolIE-ID ::= 92 | +| id-SecurityContext | ProtocolIE-ID ::= 93 | +| id-SecurityKey | ProtocolIE-ID ::= 94 | +| id-SerialNumber | ProtocolIE-ID ::= 95 | +| id-ServedGUAMIList | ProtocolIE-ID ::= 96 | +| id-SliceSupportList | ProtocolIE-ID ::= 97 | +| id-SONConfigurationTransferDL | ProtocolIE-ID ::= 98 | +| id-SONConfigurationTransferUL | ProtocolIE-ID ::= 99 | +| id-SourceAMF-UE-NGAP-ID | ProtocolIE-ID ::= 100 | +| id-SourceToTarget-TransparentContainer | ProtocolIE-ID ::= 101 | +| id-SupportedTAList | ProtocolIE-ID ::= 102 | +| id-TAIListForPaging | ProtocolIE-ID ::= 103 | +| id-TAIListForRestart | ProtocolIE-ID ::= 104 | +| id-TargetID | ProtocolIE-ID ::= 105 | +| id-TargetToSource-TransparentContainer | ProtocolIE-ID ::= 106 | +| id-TimeToWait | ProtocolIE-ID ::= 107 | +| id-TraceActivation | ProtocolIE-ID ::= 108 | +| id-TraceCollectionEntityIPAddress | ProtocolIE-ID ::= 109 | +| id-UEAggregateMaximumBitRate | ProtocolIE-ID ::= 110 | +| id-UE-associatedLogicalNG-connectionList | ProtocolIE-ID ::= 111 | +| id-UEContextRequest | ProtocolIE-ID ::= 112 | +| id-UE-NGAP-IDs | ProtocolIE-ID ::= 114 | + +| | | +|-----------------------------------------------|-----------------------| +| id-UEPagingIdentity | ProtocolIE-ID ::= 115 | +| id-UEPresenceInAreaOfInterestList | ProtocolIE-ID ::= 116 | +| id-UERadioCapability | ProtocolIE-ID ::= 117 | +| id-UERadioCapabilityForPaging | ProtocolIE-ID ::= 118 | +| id-UESecurityCapabilities | ProtocolIE-ID ::= 119 | +| id-UnavailableGUAMIList | ProtocolIE-ID ::= 120 | +| id-UserLocationInformation | ProtocolIE-ID ::= 121 | +| id-WarningAreaList | ProtocolIE-ID ::= 122 | +| id-WarningMessageContents | ProtocolIE-ID ::= 123 | +| id-WarningSecurityInfo | ProtocolIE-ID ::= 124 | +| id-WarningType | ProtocolIE-ID ::= 125 | +| id-AdditionalUL-NGU-UP-TNLInformation | ProtocolIE-ID ::= 126 | +| id-DataForwardingNotPossible | ProtocolIE-ID ::= 127 | +| id-DL-NGU-UP-TNLInformation | ProtocolIE-ID ::= 128 | +| id-NetworkInstance | ProtocolIE-ID ::= 129 | +| id-PDUSessionAggregateMaximumBitRate | ProtocolIE-ID ::= 130 | +| id-PDUSessionResourceFailedToModifyListModCfm | ProtocolIE-ID ::= 131 | +| id-PDUSessionResourceFailedToSetupListCxtFail | ProtocolIE-ID ::= 132 | +| id-PDUSessionResourceListCxtRelReq | ProtocolIE-ID ::= 133 | +| id-PDUSessionType | ProtocolIE-ID ::= 134 | +| id-QosFlowAddOrModifyRequestList | ProtocolIE-ID ::= 135 | +| id-QosFlowSetupRequestList | ProtocolIE-ID ::= 136 | +| id-QosFlowToReleaseList | ProtocolIE-ID ::= 137 | + +| | | +|-------------------------------------------------|-----------------------| +| id-SecurityIndication | ProtocolIE-ID ::= 138 | +| id-UL-NGU-UP-TNLInformation | ProtocolIE-ID ::= 139 | +| id-UL-NGU-UP-TNLModifyList | ProtocolIE-ID ::= 140 | +| id-WarningAreaCoordinates | ProtocolIE-ID ::= 141 | +| id-PDUSessionResourceSecondaryRATUsageList | ProtocolIE-ID ::= 142 | +| id-HandoverFlag | ProtocolIE-ID ::= 143 | +| id-SecondaryRATUsageInformation | ProtocolIE-ID ::= 144 | +| id-PDUSessionResourceReleaseResponseTransfer | ProtocolIE-ID ::= 145 | +| id-RedirectionVoiceFallback | ProtocolIE-ID ::= 146 | +| id-UERetentionInformation | ProtocolIE-ID ::= 147 | +| id-S-NSSAI | ProtocolIE-ID ::= 148 | +| id-PSCellInformation | ProtocolIE-ID ::= 149 | +| id-LastEUTRAN-PLMNIdentity | ProtocolIE-ID ::= 150 | +| id-MaximumIntegrityProtectedDataRate-DL | ProtocolIE-ID ::= 151 | +| id-AdditionalDLForwardingUPTNLInformation | ProtocolIE-ID ::= 152 | +| id-AdditionalDLUPTNLInformationForHOList | ProtocolIE-ID ::= 153 | +| id-AdditionalNGU-UP-TNLInformation | ProtocolIE-ID ::= 154 | +| id-AdditionalDLQosFlowPerTNLInformation | ProtocolIE-ID ::= 155 | +| id-SecurityResult | ProtocolIE-ID ::= 156 | +| id-ENDC-SONConfigurationTransferDL | ProtocolIE-ID ::= 157 | +| id-ENDC-SONConfigurationTransferUL | ProtocolIE-ID ::= 158 | +| id-OldAssociatedQosFlowList-ULendmarkerexpected | ProtocolIE-ID ::= 159 | +| id-CNTTypeRestrictionsForEquivalent | ProtocolIE-ID ::= 160 | + +| | | +|------------------------------------------------|-----------------------| +| id-CNTypeRestrictionsForServing | ProtocolIE-ID ::= 161 | +| id-NewGUAMI | ProtocolIE-ID ::= 162 | +| id-ULForwarding | ProtocolIE-ID ::= 163 | +| id-ULForwardingUP-TNLInformation | ProtocolIE-ID ::= 164 | +| id-CNAssistedRANTuning | ProtocolIE-ID ::= 165 | +| id-CommonNetworkInstance | ProtocolIE-ID ::= 166 | +| id-NGRAN-TNLAssociationToRemoveList | ProtocolIE-ID ::= 167 | +| id-TNLAssociationTransportLayerAddressNGRAN | ProtocolIE-ID ::= 168 | +| id-EndpointIPAddressAndPort | ProtocolIE-ID ::= 169 | +| id-LocationReportingAdditionalInfo | ProtocolIE-ID ::= 170 | +| id-SourceToTarget-AMFInformationReroute | ProtocolIE-ID ::= 171 | +| id-AdditionalULForwardingUPTNLInformation | ProtocolIE-ID ::= 172 | +| id-SCTP-TLAs | ProtocolIE-ID ::= 173 | +| id-SelectedPLMNIdentity | ProtocolIE-ID ::= 174 | +| id-RIMInformationTransfer | ProtocolIE-ID ::= 175 | +| id-GUAMIType | ProtocolIE-ID ::= 176 | +| id-SRVCCOperationPossible | ProtocolIE-ID ::= 177 | +| id-TargetRNC-ID | ProtocolIE-ID ::= 178 | +| id-RAT-Information | ProtocolIE-ID ::= 179 | +| id-ExtendedRATRestrictionInformation | ProtocolIE-ID ::= 180 | +| id-QosMonitoringRequest | ProtocolIE-ID ::= 181 | +| id-SgNB-UE-X2AP-ID | ProtocolIE-ID ::= 182 | +| id-AdditionalRedundantDL-NGU-UP-TNLInformation | ProtocolIE-ID ::= 183 | + +| | | +|--------------------------------------------------|-----------------------| +| id-AdditionalRedundantDLQosFlowPerTNLInformation | ProtocolIE-ID ::= 184 | +| id-AdditionalRedundantNGU-UP-TNLInformation | ProtocolIE-ID ::= 185 | +| id-AdditionalRedundantUL-NGU-UP-TNLInformation | ProtocolIE-ID ::= 186 | +| id-CNPacketDelayBudgetDL | ProtocolIE-ID ::= 187 | +| id-CNPacketDelayBudgetUL | ProtocolIE-ID ::= 188 | +| id-ExtendedPacketDelayBudget | ProtocolIE-ID ::= 189 | +| id-RedundantCommonNetworkInstance | ProtocolIE-ID ::= 190 | +| id-RedundantDL-NGU-TNLInformationReused | ProtocolIE-ID ::= 191 | +| id-RedundantDL-NGU-UP-TNLInformation | ProtocolIE-ID ::= 192 | +| id-RedundantDLQosFlowPerTNLInformation | ProtocolIE-ID ::= 193 | +| id-RedundantQosFlowIndicator | ProtocolIE-ID ::= 194 | +| id-RedundantUL-NGU-UP-TNLInformation | ProtocolIE-ID ::= 195 | +| id-TSCTrafficCharacteristics | ProtocolIE-ID ::= 196 | +| id-RedundantPDUSessionInformation | ProtocolIE-ID ::= 197 | +| id-UsedRSNInformation | ProtocolIE-ID ::= 198 | +| id-IAB-Authorized | ProtocolIE-ID ::= 199 | +| id-IAB-Supported | ProtocolIE-ID ::= 200 | +| id-IABNodeIndication | ProtocolIE-ID ::= 201 | +| id-NB-IoT-PagingDRX | ProtocolIE-ID ::= 202 | +| id-NB-IoT-Paging-eDRXInfo | ProtocolIE-ID ::= 203 | +| id-NB-IoT-DefaultPagingDRX | ProtocolIE-ID ::= 204 | +| id-Enhanced-CoverageRestriction | ProtocolIE-ID ::= 205 | +| id-Extended-ConnectedTime | ProtocolIE-ID ::= 206 | + +| | | +|-----------------------------------------------|-----------------------| +| id-PagingAssisDataforCEcapabUE | ProtocolIE-ID ::= 207 | +| id-WUS-Assistance-Information | ProtocolIE-ID ::= 208 | +| id-UE-DifferentiationInfo | ProtocolIE-ID ::= 209 | +| id-NB-IoT-UEPriority | ProtocolIE-ID ::= 210 | +| id-UL-CP-SecurityInformation | ProtocolIE-ID ::= 211 | +| id-DL-CP-SecurityInformation | ProtocolIE-ID ::= 212 | +| id-TAI | ProtocolIE-ID ::= 213 | +| id-UERadioCapabilityForPagingOfNB-IoT | ProtocolIE-ID ::= 214 | +| id-LTEV2XServicesAuthorized | ProtocolIE-ID ::= 215 | +| id-NRV2XServicesAuthorized | ProtocolIE-ID ::= 216 | +| id-LTEUESidelinkAggregateMaximumBitrate | ProtocolIE-ID ::= 217 | +| id-NRUESidelinkAggregateMaximumBitrate | ProtocolIE-ID ::= 218 | +| id-PC5QoSParameters | ProtocolIE-ID ::= 219 | +| id-AlternativeQoSParaSetList | ProtocolIE-ID ::= 220 | +| id-CurrentQoSParaSetIndex | ProtocolIE-ID ::= 221 | +| id-CEmodeBrestricted | ProtocolIE-ID ::= 222 | +| id-EUTRA-PagingeDRXInformation | ProtocolIE-ID ::= 223 | +| id-CEmodeBSupport-Indicator | ProtocolIE-ID ::= 224 | +| id-LTEM-Indication | ProtocolIE-ID ::= 225 | +| id-EndIndication | ProtocolIE-ID ::= 226 | +| id-EDT-Session | ProtocolIE-ID ::= 227 | +| id-UECapabilityInfoRequest | ProtocolIE-ID ::= 228 | +| id-PDUSessionResourceFailedToResumeListRESReq | ProtocolIE-ID ::= 229 | + +| | | +|-----------------------------------------------|-----------------------| +| id-PDUSessionResourceFailedToResumeListRESRes | ProtocolIE-ID ::= 230 | +| id-PDUSessionResourceSuspendListSUSReq | ProtocolIE-ID ::= 231 | +| id-PDUSessionResourceResumeListRESReq | ProtocolIE-ID ::= 232 | +| id-PDUSessionResourceResumeListRESRes | ProtocolIE-ID ::= 233 | +| id-UE-UP-CIoT-Support | ProtocolIE-ID ::= 234 | +| id-Suspend-Request-Indication | ProtocolIE-ID ::= 235 | +| id-Suspend-Response-Indication | ProtocolIE-ID ::= 236 | +| id-RRC-Resume-Cause | ProtocolIE-ID ::= 237 | +| id-RGLevelWirelineAccessCharacteristics | ProtocolIE-ID ::= 238 | +| id-W-AGFIdentityInformation | ProtocolIE-ID ::= 239 | +| id-GlobalTNGF-ID | ProtocolIE-ID ::= 240 | +| id-GlobalTWIF-ID | ProtocolIE-ID ::= 241 | +| id-GlobalW-AGF-ID | ProtocolIE-ID ::= 242 | +| id-UserLocationInformationW-AGF | ProtocolIE-ID ::= 243 | +| id-UserLocationInformationTNGF | ProtocolIE-ID ::= 244 | +| id-AuthenticatedIndication | ProtocolIE-ID ::= 245 | +| id-TNGFIdentityInformation | ProtocolIE-ID ::= 246 | +| id-TWIFIdentityInformation | ProtocolIE-ID ::= 247 | +| id-UserLocationInformationTWIF | ProtocolIE-ID ::= 248 | +| id-DataForwardingResponseERABList | ProtocolIE-ID ::= 249 | +| id-IntersystemSONConfigurationTransferDL | ProtocolIE-ID ::= 250 | +| id-IntersystemSONConfigurationTransferUL | ProtocolIE-ID ::= 251 | +| id-SONInformationReport | ProtocolIE-ID ::= 252 | + +| | | +|------------------------------------------------|-----------------------| +| id-UEHistoryInformationFromTheUE | ProtocolIE-ID ::= 253 | +| id-ManagementBasedMDTFLMNList | ProtocolIE-ID ::= 254 | +| id-MDTConfiguration | ProtocolIE-ID ::= 255 | +| id-PrivacyIndicator | ProtocolIE-ID ::= 256 | +| id-TraceCollectionEntityURI | ProtocolIE-ID ::= 257 | +| id-NPN-Support | ProtocolIE-ID ::= 258 | +| id-NPN-AccessInformation | ProtocolIE-ID ::= 259 | +| id-NPN-PagingAssistanceInformation | ProtocolIE-ID ::= 260 | +| id-NPN-MobilityInformation | ProtocolIE-ID ::= 261 | +| id-TargettoSource-Failure-TransparentContainer | ProtocolIE-ID ::= 262 | +| id-NID | ProtocolIE-ID ::= 263 | +| id-UERadioCapabilityID | ProtocolIE-ID ::= 264 | +| id-UERadioCapability-EUTRA-Format | ProtocolIE-ID ::= 265 | +| id-DAPSRequestInfo | ProtocolIE-ID ::= 266 | +| id-DAPSResponseInfoList | ProtocolIE-ID ::= 267 | +| id-EarlyStatusTransfer-TransparentContainer | ProtocolIE-ID ::= 268 | +| id-NotifySourceNGRANNode | ProtocolIE-ID ::= 269 | +| id-ExtendedSliceSupportList | ProtocolIE-ID ::= 270 | +| id-ExtendedTAISliceSupportList | ProtocolIE-ID ::= 271 | +| id-ConfiguredTACIndication | ProtocolIE-ID ::= 272 | +| id-Extended-RANNodeName | ProtocolIE-ID ::= 273 | +| id-Extended-AMFName | ProtocolIE-ID ::= 274 | +| id-GlobalCable-ID | ProtocolIE-ID ::= 275 | + +| | | +|------------------------------------------|-----------------------| +| id-QosMonitoringReportingFrequency | ProtocolIE-ID ::= 276 | +| id-QosFlowParametersList | ProtocolIE-ID ::= 277 | +| id-QosFlowFeedbackList | ProtocolIE-ID ::= 278 | +| id-BurstArrivalTimeDownlink | ProtocolIE-ID ::= 279 | +| id-ExtendedUEIdentityIndexValue | ProtocolIE-ID ::= 280 | +| id-PduSessionExpectedUEActivityBehaviour | ProtocolIE-ID ::= 281 | +| id-MicoAllPLMN | ProtocolIE-ID ::= 282 | +| id-QosFlowFailedToSetupList | ProtocolIE-ID ::= 283 | +| id-SourceTNLAddrInfo | ProtocolIE-ID ::= 284 | +| id-ExtendedReportIntervalMDT | ProtocolIE-ID ::= 285 | +| id-SourceNodeID | ProtocolIE-ID ::= 286 | +| id-NRNTTAInformation | ProtocolIE-ID ::= 287 | +| id-UEContextReferenceAtSource | ProtocolIE-ID ::= 288 | +| id-LastVisitedPSCellList | ProtocolIE-ID ::= 289 | +| id-IntersystemSONInformationRequest | ProtocolIE-ID ::= 290 | +| id-IntersystemSONInformationReply | ProtocolIE-ID ::= 291 | +| id-EnergySavingIndication | ProtocolIE-ID ::= 292 | +| id-IntersystemResourceStatusUpdate | ProtocolIE-ID ::= 293 | +| id-SuccessfulHandoverReportList | ProtocolIE-ID ::= 294 | +| id-MBS-AreaSessionID | ProtocolIE-ID ::= 295 | +| id-MBS-QoSFlowsToBeSetupList | ProtocolIE-ID ::= 296 | +| id-MBS-QoSFlowsToBeSetupModList | ProtocolIE-ID ::= 297 | +| id-MBS-ServiceArea | ProtocolIE-ID ::= 298 | + +| | | +|----------------------------------------------------|-----------------------| +| id-MBS-SessionID | ProtocolIE-ID ::= 299 | +| id-MBS-DistributionReleaseRequestTransfer | ProtocolIE-ID ::= 300 | +| id-MBS-DistributionSetupRequestTransfer | ProtocolIE-ID ::= 301 | +| id-MBS-DistributionSetupResponseTransfer | ProtocolIE-ID ::= 302 | +| id-MBS-DistributionSetupUnsuccessfulTransfer | ProtocolIE-ID ::= 303 | +| id-MulticastSessionActivationRequestTransfer | ProtocolIE-ID ::= 304 | +| id-MulticastSessionDeactivationRequestTransfer | ProtocolIE-ID ::= 305 | +| id-MulticastSessionUpdateRequestTransfer | ProtocolIE-ID ::= 306 | +| id-MulticastGroupPagingAreaList | ProtocolIE-ID ::= 307 | +| id-MBS-SupportIndicator | ProtocolIE-ID ::= 309 | +| id-MBSSessionFailedtoSetupList | ProtocolIE-ID ::= 310 | +| id-MBSSessionFailedtoSetuporModifyList | ProtocolIE-ID ::= 311 | +| id-MBSSessionSetupResponseList | ProtocolIE-ID ::= 312 | +| id-MBSSessionSetuporModifyResponseList | ProtocolIE-ID ::= 313 | +| id-MBSSessionSetupFailureTransfer | ProtocolIE-ID ::= 314 | +| id-MBSSessionSetupRequestTransfer | ProtocolIE-ID ::= 315 | +| id-MBSSessionSetupResponseTransfer | ProtocolIE-ID ::= 316 | +| id-MBSSessionToReleaseList | ProtocolIE-ID ::= 317 | +| id-MBSSessionSetupRequestList | ProtocolIE-ID ::= 318 | +| id-MBSSessionSetuporModifyRequestList | ProtocolIE-ID ::= 319 | +| id-MBS-ActiveSessionInformation-SourcetoTargetList | ProtocolIE-ID ::= 323 | +| id-MBS-ActiveSessionInformation-TargettoSourceList | ProtocolIE-ID ::= 324 | +| id-OnboardingSupport | ProtocolIE-ID ::= 325 | + +| | | +|--------------------------------------------|-----------------------| +| id-TimeSyncAssistanceInfo | ProtocolIE-ID ::= 326 | +| id-SurvivalTime | ProtocolIE-ID ::= 327 | +| id-QMCConfigInfo | ProtocolIE-ID ::= 328 | +| id-QMCDeactivation | ProtocolIE-ID ::= 329 | +| id-PDUSessionPairID | ProtocolIE-ID ::= 331 | +| id-NR-PagingeDRXInformation | ProtocolIE-ID ::= 332 | +| id-RedCapIndication | ProtocolIE-ID ::= 333 | +| id-TargetNSSAIInformation | ProtocolIE-ID ::= 334 | +| id-UESliceMaximumBitRateList | ProtocolIE-ID ::= 335 | +| id-M4ReportAmount | ProtocolIE-ID ::= 336 | +| id-M5ReportAmount | ProtocolIE-ID ::= 337 | +| id-M6ReportAmount | ProtocolIE-ID ::= 338 | +| id-M7ReportAmount | ProtocolIE-ID ::= 339 | +| id-IncludeBeamMeasurementsIndication | ProtocolIE-ID ::= 340 | +| id-ExcessPacketDelayThresholdConfiguration | ProtocolIE-ID ::= 341 | +| id-PagingCause | ProtocolIE-ID ::= 342 | +| id-PagingCauseIndicationForVoiceService | ProtocolIE-ID ::= 343 | +| id-PEIPSAssistanceInformation | ProtocolIE-ID ::= 344 | +| id-FiveG-ProSeAuthorized | ProtocolIE-ID ::= 345 | +| id-FiveG-ProSeUEPC5AggregateMaximumBitRate | ProtocolIE-ID ::= 346 | +| id-FiveG-ProSePC5QoSParameters | ProtocolIE-ID ::= 347 | +| id-MBSsessionModificationFailureTransfer | ProtocolIE-ID ::= 348 | +| id-MBSsessionModificationRequestTransfer | ProtocolIE-ID ::= 349 | + +| | | +|--------------------------------------------------------|-----------------------| +| id-MBSsessionModificationResponseTransfer | ProtocolIE-ID ::= 350 | +| id-MBS-QoSFlowToReleaseList | ProtocolIE-ID ::= 351 | +| id-MBS-SessionTNLInfo5GC | ProtocolIE-ID ::= 352 | +| id-TAINSAGSupportList | ProtocolIE-ID ::= 353 | +| id-SourceNodeTNLAddrInfo | ProtocolIE-ID ::= 354 | +| id-NGAPIESupportInformationRequestList | ProtocolIE-ID ::= 355 | +| id-NGAPIESupportInformationResponseList | ProtocolIE-ID ::= 356 | +| id-MBS-SessionFSAIDList | ProtocolIE-ID ::= 357 | +| id-MBSsessionReleaseResponseTransfer | ProtocolIE-ID ::= 358 | +| id-ManagementBasedMDTPLMNModificationList | ProtocolIE-ID ::= 359 | +| id-EarlyMeasurement | ProtocolIE-ID ::= 360 | +| id-BeamMeasurementsReportConfiguration | ProtocolIE-ID ::= 361 | +| id-HFCNode-ID-new | ProtocolIE-ID ::= 362 | +| id-GlobalCable-ID-new | ProtocolIE-ID ::= 363 | +| id-TargetHomeENB-ID | ProtocolIE-ID ::= 364 | +| id-HashedUEIdentityIndexValue | ProtocolIE-ID ::= 365 | +| id-ExtendedMobilityInformation | ProtocolIE-ID ::= 366 | +| id-NetworkControlledRepeaterAuthorized | ProtocolIE-ID ::= 367 | +| id-AdditionalCancelledlocationReportingReferenceIDList | ProtocolIE-ID ::= 368 | +| id-Selected-Target-SNPN-Identity | ProtocolIE-ID ::= 369 | +| id-EquivalentSNPNsList | ProtocolIE-ID ::= 370 | +| id-SelectedNID | ProtocolIE-ID ::= 371 | +| id-SupportedUETypeList | ProtocolIE-ID ::= 372 | + +| | | +|-----------------------------------------------|-----------------------| +| id-AerialUEsubscriptionInformation | ProtocolIE-ID ::= 373 | +| id-NR-A2X-ServicesAuthorized | ProtocolIE-ID ::= 374 | +| id-LTE-A2X-ServicesAuthorized | ProtocolIE-ID ::= 375 | +| id-NR-A2X-UE-PC5-AggregateMaximumBitRate | ProtocolIE-ID ::= 376 | +| id-LTE-A2X-UE-PC5-AggregateMaximumBitRate | ProtocolIE-ID ::= 377 | +| id-A2X-PC5-QoS-Parameters | ProtocolIE-ID ::= 378 | +| id-FiveGProSeLayer2Multipath | ProtocolIE-ID ::= 379 | +| id-FiveGProSeLayer2UEtoUERelay | ProtocolIE-ID ::= 380 | +| id-FiveGProSeLayer2UEtoUERemote | ProtocolIE-ID ::= 381 | +| id-CandidateRelayUEInformationList | ProtocolIE-ID ::= 382 | +| id-SuccessfulPSCellChangeReportList | ProtocolIE-ID ::= 383 | +| id-IntersystemMobilityFailureforVoiceFallback | ProtocolIE-ID ::= 384 | +| id-TargetCellCRNTI | ProtocolIE-ID ::= 385 | +| id-TimeSinceFailure | ProtocolIE-ID ::= 386 | +| id-RANTimingSynchronisationStatusInfo | ProtocolIE-ID ::= 387 | +| id-RAN-TSSRequestType | ProtocolIE-ID ::= 388 | +| id-RAN-TSSScope | ProtocolIE-ID ::= 389 | +| id-ClockQualityReportingControlInfo | ProtocolIE-ID ::= 390 | +| id-RANfeedbacktype | ProtocolIE-ID ::= 391 | +| id-QoSFlowTSCList | ProtocolIE-ID ::= 392 | +| id-TSCTrafficCharacteristicsFeedback | ProtocolIE-ID ::= 393 | +| id-DownlinkTLContainer | ProtocolIE-ID ::= 394 | +| id-UplinkTLContainer | ProtocolIE-ID ::= 395 | + +| | | +|--------------------------------------|-----------------------| +| id-ANPacketDelayBudgetUL | ProtocolIE-ID ::= 396 | +| id-QosFlowAdditionalInfoList | ProtocolIE-ID ::= 397 | +| id-AssistanceInformationQoE-Meas | ProtocolIE-ID ::= 398 | +| id-MBSCommServiceType | ProtocolIE-ID ::= 399 | +| id-MobileIAB-Authorized | ProtocolIE-ID ::= 400 | +| id-IAB-MTUserLocationInformation | ProtocolIE-ID ::= 401 | +| id-MobileIABNodeIndication | ProtocolIE-ID ::= 402 | +| id-NoPDUSessionIndication | ProtocolIE-ID ::= 403 | +| id-MobileIAB-Supported | ProtocolIE-ID ::= 404 | +| id-CN-MT-CommunicationHandling | ProtocolIE-ID ::= 405 | +| id-FiveGCAction | ProtocolIE-ID ::= 406 | +| id-PagingPolicyDifferentiation | ProtocolIE-ID ::= 407 | +| id-DL-Signalling | ProtocolIE-ID ::= 408 | +| id-PNI-NPN-AreaScopeofMDT | ProtocolIE-ID ::= 409 | +| id-PNI-NPNBasedMDT | ProtocolIE-ID ::= 410 | +| id-SNPN-CellBasedMDT | ProtocolIE-ID ::= 411 | +| id-SNPN-TAIBasedMDT | ProtocolIE-ID ::= 412 | +| id-SNPN-BasedMDT | ProtocolIE-ID ::= 413 | +| id-Partially-Allowed-NSSAI | ProtocolIE-ID ::= 414 | +| id-AssociatedSessionID | ProtocolIE-ID ::= 415 | +| id-MBS-AssistanceInformation | ProtocolIE-ID ::= 416 | +| id-BroadcastTransportFailureTransfer | ProtocolIE-ID ::= 417 | +| id-BroadcastTransportRequestTransfer | ProtocolIE-ID ::= 418 | + +``` + +id-BroadcastTransportResponseTransfer ProtocolIE-ID ::= 419 +id-TimeBasedHandoverInformation ProtocolIE-ID ::= 420 +id-DLDiscarding ProtocolIE-ID ::= 421 +id-PDUSetQoSParameters ProtocolIE-ID ::= 422 +id-PDUSetbasedHandlingIndicator ProtocolIE-ID ::= 423 +id-N6JitterInformation ProtocolIE-ID ::= 424 +id-ECNMarkingorCongestionInformationReportingRequest ProtocolIE-ID ::= 425 +id-ECNMarkingorCongestionInformationReportingStatus ProtocolIE-ID ::= 426 + +``` + +END + +-- ASN1STOP + +### 9.4.8 Container Definitions + +-- ASN1START + +-- \*\*\*\*\* + +-- + +-- Container definitions + +-- + +-- \*\*\*\*\* + +``` +NGAP-Containers { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + ngran-Access (22) modules (3) ngap (1) version1 (1) ngap-Containers (5) } +``` + +``` +DEFINITIONS AUTOMATIC TAGS ::= +``` + +``` +BEGIN +``` + +``` +-- ***** +-- +-- IE parameter types from other modules. +-- +-- ***** +``` + +``` +IMPORTS +``` + +``` +Criticality, +Presence, +PrivateIE-ID, +ProtocolExtensionID, +ProtocolIE-ID +``` + +``` +FROM NGAP-CommonDataTypes +``` + +``` + +maxPrivateIEs, +maxProtocolExtensions, +maxProtocolIEs +FROM NGAP-Constants; + +-- ***** +-- +-- Class Definition for Protocol IEs +-- +-- ***** + +NGAP-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 +-- +-- ***** + +NGAP-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 + -- + -- ***** + + NGAP-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 + +-- + +-- \*\*\*\*\* + +NGAP-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 {NGAP-PROTOCOL-IES : IEsSetParam} ::= + SEQUENCE (SIZE (0..maxProtocolIEs)) OF + ProtocolIE-Field {{IEsSetParam}} + +``` + +``` + +ProtocolIE-SingleContainer {NGAP-PROTOCOL-IES : IEsSetParam} ::= + ProtocolIE-Field {{IEsSetParam}} + +``` + +``` + +ProtocolIE-Field {NGAP-PROTOCOL-IES : IEsSetParam} ::= SEQUENCE { + id NGAP-PROTOCOL-IES.&id ({IEsSetParam}), + criticality NGAP-PROTOCOL-IES.&criticality ({IEsSetParam}{@id}), + value NGAP-PROTOCOL-IES.&Value ({IEsSetParam}{@id}) +} + +``` + +``` + +-- ***** +-- +-- Container for Protocol IE Pairs +-- +-- ***** + +``` + +``` + +ProtocolIE-ContainerPair {NGAP-PROTOCOL-IES-PAIR : IEsSetParam} ::= + SEQUENCE (SIZE (0..maxProtocolIEs)) OF + ProtocolIE-FieldPair {{IEsSetParam}} + +``` + +``` + +ProtocolIE-FieldPair {NGAP-PROTOCOL-IES-PAIR : IEsSetParam} ::= SEQUENCE { + id NGAP-PROTOCOL-IES-PAIR.&id {{IEsSetParam}}, + firstCriticality NGAP-PROTOCOL-IES-PAIR.&firstCriticality {{IEsSetParam}{@id}}, + firstValue NGAP-PROTOCOL-IES-PAIR.&FirstValue {{IEsSetParam}{@id}}, + secondCriticality NGAP-PROTOCOL-IES-PAIR.&secondCriticality {{IEsSetParam}{@id}}, + secondValue NGAP-PROTOCOL-IES-PAIR.&SecondValue {{IEsSetParam}{@id}} +} + +``` + +``` + +-- ***** +-- +-- Container Lists for Protocol IE Containers +-- +-- ***** + +``` + +``` + +ProtocolIE-ContainerList {INTEGER : lowerBound, INTEGER : upperBound, NGAP-PROTOCOL-IES : IEsSetParam} ::= + SEQUENCE (SIZE (lowerBound..upperBound)) OF + ProtocolIE-SingleContainer {{IEsSetParam}} + +``` + +``` + +ProtocolIE-ContainerPairList {INTEGER : lowerBound, INTEGER : upperBound, NGAP-PROTOCOL-IES-PAIR : IEsSetParam} ::= + SEQUENCE (SIZE (lowerBound..upperBound)) OF + ProtocolIE-ContainerPair {{IEsSetParam}} + +``` + +``` + +-- ***** + +``` + +``` +-- + +-- Container for Protocol Extensions + +-- + +-- ***** + +ProtocolExtensionContainer {NGAP-PROTOCOL-EXTENSION : ExtensionSetParam} ::= + + SEQUENCE (SIZE (1..maxProtocolExtensions)) OF + + ProtocolExtensionField {{ExtensionSetParam}} + +ProtocolExtensionField {NGAP-PROTOCOL-EXTENSION : ExtensionSetParam} ::= SEQUENCE { + + id NGAP-PROTOCOL-EXTENSION.&id ({ExtensionSetParam}), + + criticality NGAP-PROTOCOL-EXTENSION.&criticality ({ExtensionSetParam}{@id}), + + extensionValue NGAP-PROTOCOL-EXTENSION.&Extension ({ExtensionSetParam}{@id}) + +} + +-- ***** + +-- + +-- Container for Private IEs + +-- + +-- ***** + +PrivateIE-Container {NGAP-PRIVATE-IEs : IEsSetParam } ::= + + SEQUENCE (SIZE (1..maxPrivateIEs)) OF +``` + +``` +PrivateIE-Field {{IEsSetParam}} + +PrivateIE-Field {NGAP-PRIVATE-IES : IEsSetParam} ::= SEQUENCE { + id NGAP-PRIVATE-IES.&id ({IEsSetParam}), + criticality NGAP-PRIVATE-IES.&criticality ({IEsSetParam}{@id}), + value NGAP-PRIVATE-IES.&Value ({IEsSetParam}{@id}) +} + +END + +-- ASN1STOP +``` + +## 9.5 Message Transfer Syntax + +NGAP shall use the ASN.1 Basic Packed Encoding Rules (BASIC-PER) Aligned Variant as transfer syntax as specified in ITU-T Rec. X.691 [4]. + +## 9.6 Timers + +### TNGRELOCprep + +- Specifies the maximum time for the Handover Preparation procedure in the source NG-RAN node. + +### TNGRELOCOverall + +- Specifies the maximum time for the protection of the overall handover procedure in the source NG-RAN node. + +### TXnRELOCOverall + +- Specified in TS 38.423 [24]. + +# 10 Handling of Unknown, Unforeseen and Erroneous Protocol Data + +## 10.1 General + +Protocol Error cases can be divided into three classes: + +- Transfer Syntax Error. +- Abstract Syntax Error. +- Logical Error. + +Protocol errors can occur in the following functions within a receiving node: + +![Diagram illustrating Protocol Errors in NGAP. It shows two boxes on the left: 'NGAP functional entity' at the top and 'ASN.1 Decoding' at the bottom, connected by a double-headed arrow. Brackets on the right group these functions with error types: 'Logical Errors' and 'Abstract Syntax Errors' are grouped with the NGAP functional entity, and 'Transfer Syntax Errors' is grouped with ASN.1 Decoding. A large upward arrow on the far right indicates the flow of error reporting from Transfer Syntax Errors up to Logical Errors.](53d32fee66efd06385d5d38b01b1a663_img.jpg) + +Diagram illustrating Protocol Errors in NGAP. It shows two boxes on the left: 'NGAP functional entity' at the top and 'ASN.1 Decoding' at the bottom, connected by a double-headed arrow. Brackets on the right group these functions with error types: 'Logical Errors' and 'Abstract Syntax Errors' are grouped with the NGAP functional entity, and 'Transfer Syntax Errors' is grouped with ASN.1 Decoding. A large upward arrow on the far right indicates the flow of error reporting from Transfer Syntax Errors up to Logical Errors. + +**Figure 10.1-1: Protocol Errors in NGAP.** + +The information stated in subclauses 10.2, 10.3 and 10.4, to be included in the message used when reporting an error, is what at minimum shall be included. Other optional information elements within the message may also be included, if available. This is also valid for the case when the reporting is done with a response message. The latter is an exception to what is stated in subclause 4.1. + +## 10.2 Transfer Syntax Error + +A Transfer Syntax Error occurs when the receiver is not able to decode the received physical message. Transfer syntax errors are always detected in the process of ASN.1 decoding. If a Transfer Syntax Error occurs, the receiver should initiate Error Indication procedure with appropriate cause value for the Transfer Syntax protocol error. + +Examples for Transfer Syntax Errors are: + +- Violation of value ranges in ASN.1 definition of messages. E.g., if an IE has a defined value range of 0 to 10 (ASN.1: INTEGER (0..10)), and 12 will be received, then this will be treated as a transfer syntax error. +- Violation in list element constraints. E.g., if a list is defined as containing 1 to 10 elements, and 12 elements will be received, then this case will be handled as a transfer syntax error. +- Missing mandatory elements in ASN.1 SEQUENCE definitions (as sent by the originator of the message). +- Wrong order of elements in ASN.1 SEQUENCE definitions (as sent by the originator of the message). + +## 10.3 Abstract Syntax Error + +### 10.3.1 General + +An Abstract Syntax Error occurs when the receiving functional NGAP entity: + +1. receives IEs or IE groups that cannot be understood (unknown IE ID); +2. receives IEs for which the logical range is violated (e.g., ASN.1 definition: 0 to 15, the logical range is 0 to 10, while values 11 to 15 are undefined), and 12 will be received; this case will be handled as an abstract syntax error using criticality information sent by the originator of the message); +3. does not receive IEs or IE groups but according to the specified presence of the concerning object, the IEs or IE groups should have been present in the received message. +4. receives IEs or IE groups that are defined to be part of that message in wrong order or with too many occurrences of the same IE or IE group; +5. receives IEs or IE groups but according to the conditional presence of the concerning object and the specified condition, the IEs or IE groups should not have been present in the received message. +6. receives IEs or IE groups for a functionality that is not supported. + +Cases 1, 2 and 6 (not comprehended IE/IE group) are handled based on received Criticality information. Case 3 (missing IE/IE group) is handled based on Criticality information and Presence information for the missing IE/IE group specified in the version of the specification used by the receiver. Case 4 (IEs or IE groups in wrong order or with too many occurrences) and Case 5 (erroneously present conditional IEs or IE groups) result in rejecting the procedure. + +If an Abstract Syntax Error occurs, the receiver shall read the remaining message and shall then for each detected Abstract Syntax Error that belong to cases 1-3 and 6 act according to the Criticality Information and Presence Information for the IE/IE group due to which Abstract Syntax Error occurred in accordance with subclauses 10.3.4 and 10.3.5. The handling of cases 4 and 5 is specified in subclause 10.3.6. + +### 10.3.2 Criticality Information + +In the NGAP messages there is criticality information set for individual IEs and/or IE groups. This criticality information instructs the receiver how to act when receiving an IE or an IE group that is not comprehended, i.e., the entire item (IE or IE group) which is not (fully or partially) comprehended shall be treated in accordance with its own criticality information as specified in subclause 10.3.4. + +In addition, the criticality information is used in case of the missing IE/IE group abstract syntax error (see subclause 10.3.5). + +The receiving node shall take different actions depending on the value of the Criticality Information. The three possible values of the Criticality Information for an IE/IE group are: + +- Reject IE. +- Ignore IE and Notify Sender. +- Ignore IE. + +The comprehension of different IEs or IE groups within a standard version or between standard versions is not mandated. Any IE or IE group that is not supported shall be considered not comprehended, even if another IE or IE group for that EP from that standard version is comprehended, and action based on criticality shall be applied. + +The comprehension of different EPs within a standard version or between different standard versions is not mandated. Any EP that is not supported shall be considered not comprehended, even if another EP from that standard version is comprehended, and action based on criticality shall be applied. + +### 10.3.3 Presence Information + +For many IEs/IE groups which are optional according to the ASN.1 transfer syntax, NGAP specifies separately if the presence of these IEs/IE groups is optional or mandatory with respect to RNS application by means of the presence field of the concerning object of class NGAP-PROTOCOL-IES, NGAP-PROTOCOL-IES-PAIR, NGAP-PROTOCOL-EXTENSION or NGAP-PRIVATE-IES. + +The presence field of the indicated classes supports three values: + +1. Optional; +2. Conditional; +3. Mandatory. + +If an IE/IE group is not included in a received message and the presence of the IE/IE group is mandatory or the presence is conditional and the condition is true according to the version of the specification used by the receiver, an abstract syntax error occurs due to a missing IE/IE group. + +If an IE/IE group is included in a received message and the presence of the IE/IE group is conditional and the condition is false according to the version of the specification used by the receiver, an abstract syntax error occurs due to this erroneously present conditional IE/IE group. + +### 10.3.4 Not comprehended IE/IE group + +#### 10.3.4.1 Procedure Code + +The receiving node shall treat the different types of received criticality information of the *Procedure Code* IE according to the following: + +##### **Reject IE:** + +- If a message is received with a *Procedure Code* IE marked with "*Reject IE*" which the receiving node does not comprehend, the receiving node shall reject the procedure using the Error Indication procedure. + +##### **Ignore IE and Notify Sender:** + +- If a message is received with a *Procedure Code* IE marked with "*Ignore IE and Notify Sender*" which the receiving node does not comprehend, the receiving node shall ignore the procedure and initiate the Error Indication procedure. + +##### **Ignore IE:** + +- If a message is received with a *Procedure Code* IE marked with "*Ignore IE*" which the receiving node does not comprehend, the receiving node shall ignore the procedure. + +When using the Error Indication procedure to reject a procedure or to report an ignored procedure it shall include the *Procedure Code* IE, the *Triggering Message* IE, and the *Procedure Criticality* IE in the *Criticality Diagnostics* IE. + +#### 10.3.4.1A Type of Message + +When the receiving node cannot decode the *Type of Message* IE, the Error Indication procedure shall be initiated with an appropriate cause value. + +### 10.3.4.2 IEs other than the Procedure Code and Type of Message + +The receiving node shall treat the different types of received criticality information of an IE/IE group other than the *Procedure Code* IE and *Type of Message* IE according to the following: + +#### Reject IE: + +- If a message *initiating* a procedure is received containing one or more IEs/IE group marked with "*Reject IE*" which the receiving node does not comprehend; none of the functional requests of the message shall be executed. The receiving node shall reject the procedure and report the rejection of one or more IEs/IE group using the message normally used to report unsuccessful outcome of the procedure. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the message used to report the unsuccessful outcome of the procedure, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. +- If a message *initiating* a procedure that does not have a message to report unsuccessful outcome is received containing one or more IEs/IE groups marked with "*Reject IE*" which the receiving node does not comprehend, the receiving node shall terminate the procedure and initiate the Error Indication procedure. +- If a *response* message is received containing one or more IEs marked with "*Reject IE*", that the receiving node does not comprehend, the receiving node shall consider the procedure as unsuccessfully terminated and initiate local error handling. + +#### Ignore IE and Notify Sender: + +- If a message *initiating* a procedure is received containing one or more IEs/IE groups marked with "*Ignore IE and Notify Sender*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups, continue with the procedure as if the not comprehended IEs/IE groups were not received (except for the reporting) using the understood IEs/IE groups, and report in the response message of the procedure that one or more IEs/IE groups have been ignored. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the response message, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. +- if a message *initiating* a procedure that does not have a message to report the outcome of the procedure is received containing one or more IEs/IE groups marked with "*Ignore IE and Notify Sender*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups, continue with the procedure as if the not comprehended IEs/IE groups were not received (except for the reporting) using the understood IEs/IE groups, and initiate the Error Indication procedure to report that one or more IEs/IE groups have been ignored. +- If a *response* message is received containing one or more IEs/IE groups marked with "*Ignore IE and Notify Sender*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups, continue with the procedure as if the not comprehended IEs/IE groups were not received (except for the reporting) using the understood IEs/IE groups and initiate the Error Indication procedure. + +**Ignore IE:** + +- If a message *initiating* a procedure is received containing one or more IEs/IE groups marked with "*Ignore IE*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups and continue with the procedure as if the not comprehended IEs/IE groups were not received using the understood IEs/IE groups. +- If a *response* message is received containing one or more IEs/IE groups marked with "*Ignore IE*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups and continue with the procedure as if the not comprehended IEs/IE groups were not received using the understood IEs/IE groups. + +When reporting not comprehended IEs/IE groups marked with "*Reject IE*" or "*Ignore IE and Notify Sender*" using a response message defined for the procedure, the *Information Element Criticality Diagnostics* IE shall be included in the *Criticality Diagnostics* IE for each reported IE/IE group. + +When reporting not comprehended IEs/IE groups marked with "*Reject IE*" or "*Ignore IE and Notify Sender*" using the Error Indication procedure, the *Procedure Code* IE, the *Triggering Message* IE, *Procedure Criticality* IE, and the *Information Element Criticality Diagnostics* IE shall be included in the *Criticality Diagnostics* IE for each reported IE/IE group. + +### 10.3.5 Missing IE or IE group + +The receiving node shall treat the missing IE/IE group according to the criticality information for the missing IE/IE group in the received message specified in the version of this specification used by the receiver: + +**Reject IE:** + +- if a received message *initiating* a procedure is missing one or more IEs/IE groups with specified criticality "*Reject IE*"; none of the functional requests of the message shall be executed. The receiving node shall reject the procedure and report the missing IEs/IE groups using the message normally used to report unsuccessful outcome of the procedure. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the message used to report the unsuccessful outcome of the procedure, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. +- if a received message *initiating* a procedure that does not have a message to report unsuccessful outcome is missing one or more IEs/IE groups with specified criticality "*Reject IE*", the receiving node shall terminate the procedure and initiate the Error Indication procedure. +- if a received *response* message is missing one or more IEs/IE groups with specified criticality "*Reject IE*", the receiving node shall consider the procedure as unsuccessfully terminated and initiate local error handling. + +**Ignore IE and Notify Sender:** + +- if a received message *initiating* a procedure is missing one or more IEs/IE groups with specified criticality "*Ignore IE and Notify Sender*", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message and report in the response message of the procedure that one or more IEs/IE groups were missing. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the response message, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. +- if a received message *initiating* a procedure that does not have a message to report the outcome of the procedure is missing one or more IEs/IE groups with specified criticality "*Ignore IE and Notify Sender*", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message and initiate the Error Indication procedure to report that one or more IEs/IE groups were missing. + +- if a received *response* message is missing one or more IEs/IE groups with specified criticality "*Ignore IE and Notify Sender*", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message and initiate the Error Indication procedure to report that one or more IEs/IE groups were missing. + +**Ignore IE:** + +- if a received message *initiating* a procedure is missing one or more IEs/IE groups with specified criticality "*Ignore IE*", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message. +- if a received *response* message is missing one or more IEs/IE groups with specified criticality "*Ignore IE*", the receiving node shall ignore that those IEs/IE groups are missing and continue with the procedure based on the other IEs/IE groups present in the message. + +When reporting missing IEs/IE groups with specified criticality "*Reject IE*" or "*Ignore IE and Notify Sender*" using a response message defined for the procedure, the *Information Element Criticality Diagnostics* IE shall be included in the *Criticality Diagnostics* IE for each reported IE/IE group. + +When reporting missing IEs/IE groups with specified criticality "*Reject IE*" or "*Ignore IE and Notify Sender*" using the Error Indication procedure, the *Procedure Code* IE, the *Triggering Message* IE, *Procedure Criticality* IE, and the *Information Element Criticality Diagnostics* IE shall be included in the *Criticality Diagnostics* IE for each reported IE/IE group. + +### 10.3.6 IEs or IE groups received in wrong order or with too many occurrences or erroneously present + +If a message with IEs or IE groups in wrong order or with too many occurrences is received or if IEs or IE groups with a conditional presence are present when the condition is not met (i.e., erroneously present), the receiving node shall behave according to the following: + +- If a message *initiating* a procedure is received containing IEs or IE groups in wrong order or with too many occurrences or erroneously present, none of the functional requests of the message shall be executed. The receiving node shall reject the procedure and report the cause value "Abstract Syntax Error (Falsely Constructed Message)" using the message normally used to report unsuccessful outcome of the procedure. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the message used to report the unsuccessful outcome of the procedure, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. +- If a message *initiating* a procedure that does not have a message to report unsuccessful outcome is received containing IEs or IE groups in wrong order or with too many occurrences or erroneously present, the receiving node shall terminate the procedure and initiate the Error Indication procedure, and use cause value "Abstract Syntax Error (Falsely Constructed Message)". +- If a *response* message is received containing IEs or IE groups in wrong order or with too many occurrences or erroneously present, the receiving node shall consider the procedure as unsuccessfully terminated and initiate local error handling. + +When determining the correct order only the IEs specified in the specification version used by the receiver shall be considered. + +## 10.4 Logical Error + +Logical error situations occur when a message is comprehended correctly, but the information contained within the message is not valid (i.e., semantic error), or describes a procedure which is not compatible with the state of the + +receiver. In these conditions, the following behaviour shall be performed (unless otherwise specified) as defined by the class of the elementary procedure, irrespective of the criticality information of the IEs/IE groups containing the erroneous values. + +#### Class 1: + +Where the logical error occurs in a request message of a class 1 procedure, and the procedure has a message to report this unsuccessful outcome, this message shall be sent with an appropriate cause value. Typical cause values are: + +- Semantic Error. +- Message not compatible with receiver state. + +Where the logical error is contained in a request message of a class 1 procedure, and the procedure does not have a message to report this unsuccessful outcome, the procedure shall be terminated and the Error Indication procedure shall be initiated with an appropriate cause value. The *Procedure Code* IE and the *Triggering Message* IE within the *Criticality Diagnostics* IE shall then be included in order to identify the message containing the logical error. + +Where the logical error exists in a response message of a class 1 procedure, the procedure shall be considered as unsuccessfully terminated and local error handling shall be initiated. + +#### Class 2: + +Where the logical error occurs in a message of a class 2 procedure, the procedure shall be terminated and the Error Indication procedure shall be initiated with an appropriate cause value. The *Procedure Code* IE and the *Triggering Message* IE within the *Criticality Diagnostics* IE shall then be included in order to identify the message containing the logical error. + +## 10.5 Exceptions + +The error handling for all the cases described hereafter shall take precedence over any other error handling described in the other subclauses of clause 10. + +- If any type of error (Transfer Syntax Error, Abstract Syntax Error or Logical Error) is detected in the ERROR INDICATION message, it shall not trigger the Error Indication procedure in the receiving Node but local error handling. +- In case a response message or Error Indication message needs to be returned, but the information necessary to determine the receiver of that message is missing, the procedure shall be considered as unsuccessfully terminated and local error handling shall be initiated. +- If an error that terminates a procedure occurs, the returned cause value shall reflect the error that caused the termination of the procedure even if one or more abstract syntax errors with criticality "ignore and notify" have earlier occurred within the same procedure. +- If an AP ID error is detected, the error handling as described in subclause 10.6 shall be applied. + +## 10.6 Handling of AP ID + +NOTE: The "first message", the "first returned message" and the "last message" as used below correspond to messages for a UE-associated logical connection. The "first message" has a new AP ID from the sending node and the "first returned message" is the first response message, which has a new AP ID from the node sending the "first returned message". Thereafter the two AP IDs are included in all messages over the UE-associated logical connection unless otherwise allowed by the specification. The "last message" is a message sent by a node in order to complete the termination of a given UE-associated logical connection, such that no other messages for the same connection are expected in either direction. The nodes should ensure as far as possible that previously allocated AP ID are not immediately reused. + +If a node receives a first returned message that includes an unknown local AP ID, the receiving node shall initiate an Error Indication procedure with inclusion of the received AP IDs from the peer node and an appropriate cause value. Both nodes shall initiate a local release of any established UE-associated logical connection (for the same NG interface) having these AP IDs as local or remote identifier. + +If a node receives a message (other than the first or first returned messages) including an erroneous AP ID that is either an unknown local AP ID, or an inconsistent remote AP ID (i.e. it is different to the remote AP ID stored previously for this UE-associated logical connection) for the same NG interface: + +- if this message is not the last message for this UE-associated logical connection, the node shall initiate an Error Indication procedure with inclusion of the received AP ID(s) from the peer node and an appropriate cause value. Both nodes shall initiate a local release of any established UE-associated logical connection (for the same NG interface) having the erroneous AP ID as either the local or remote identifier. +- if this message is the last message for this UE-associated logical connection, the receiving node shall initiate a local release of any established UE-associated logical connection (for the same NG interface) having the erroneous AP ID as either the local or remote identifier. + +--- + +## Annex A (informative): Change history + +| Change history | | | | | | | | | +|----------------|---------|-----------|------|-----|-----|---------------------------------------------------------------------------------------------------------------------------------|--|-------------| +| Date | Meeting | Tdoc | CR | Rev | Cat | Subject/Comment | | New version | +| 2017-04 | R3#95b | R3-171209 | - | - | - | TS skeleton | | 0.0.0 | +| 2017-04 | R3#95b | R3-171311 | - | - | - | Incorporated agreed TPs from R3#95b | | 0.0.1 | +| 2017-05 | R3#96 | R3-171480 | - | - | - | Update of title page and change history | | 0.0.2 | +| 2017-05 | R3#96 | R3-171975 | - | - | - | Incorporated agreed TPs from R3#96 | | 0.1.0 | +| 2017-07 | R3 NR#2 | R3-172604 | - | - | - | Incorporated agreed TPs from R3 NR#2 Adhoc | | 0.2.0 | +| 2017-08 | R3#97 | R3-173447 | - | - | - | Incorporated agreed TPs from R3#97 | | 0.3.0 | +| 2017-10 | R3#97b | R3-174239 | - | - | - | Incorporated agreed TPs from R3#97b | | 0.4.0 | +| 2017-12 | R3#98 | R3-175056 | - | - | - | Incorporated agreed TPs from R3#98 | | 0.5.0 | +| 2018-01 | R3 NR#1 | R3-180651 | - | - | - | Incorporated agreed TPs from R3 NR Adhoc 1801 | | 0.6.0 | +| 2018-03 | R3#99 | R3-181588 | - | - | - | Incorporated agreed TPs from R3#99 | | 0.7.0 | +| 2018-04 | R3#99b | R3-182524 | - | - | - | Incorporated agreed TPs from R3#99b | | 0.8.0 | +| 2018-05 | R3#100 | R3-183592 | - | - | - | Incorporated agreed TPs from R3#100 | | 0.9.0 | +| 2018-06 | RAN#80 | RP-180737 | - | - | - | 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 | 2 | F | NR Corrections (38.413 Baseline CR covering RAN3-101 agreements) | | 15.1.0 | +| 2018-12 | RAN#82 | RP-182448 | 0003 | 2 | F | Baseline CR for TS 38.413 | | 15.2.0 | +| 2019-03 | RAN#83 | RP-190556 | 0005 | 3 | F | NGAP Corrections for UP Security Handling in DC during PDU Session Lifetime | | 15.3.0 | +| 2019-03 | RAN#83 | RP-190555 | 0008 | 2 | F | Separate UL/DL limits for UE's maximum IP rate | | 15.3.0 | +| 2019-03 | RAN#83 | RP-190554 | 0009 | 1 | F | Data volume reporting for MR-DC with 5GC | | 15.3.0 | +| 2019-03 | RAN#83 | RP-190554 | 0010 | 3 | F | Correction of PDU Session split at handover | | 15.3.0 | +| 2019-03 | RAN#83 | RP-190556 | 0011 | 1 | F | Correction of EPS Voice Fallback | | 15.3.0 | +| 2019-03 | RAN#83 | RP-190556 | 0012 | - | F | Correction of slice support over NG | | 15.3.0 | +| 2019-03 | RAN#83 | RP-190556 | 0014 | 1 | F | Rapporteur updates for TS 38.413 | | 15.3.0 | +| 2019-03 | RAN#83 | RP-190556 | 0015 | - | F | Correction of User Location Information IE presence in HANDOVER NOTIFY | | 15.3.0 | +| 2019-03 | RAN#83 | RP-190556 | 0019 | 1 | F | Correction to RRC state report | | 15.3.0 | +| 2019-03 | RAN#83 | RP-190555 | 0021 | - | F | Support of RAN initiated multiple SCTP associations | | 15.3.0 | +| 2019-03 | RAN#83 | RP-190556 | 0023 | - | F | Corrections on RAN/AMF Configuration Update | | 15.3.0 | +| 2019-03 | RAN#83 | RP-190556 | 0024 | 2 | F | Correction of EPC interworking | | 15.3.0 | +| 2019-03 | RAN#83 | RP-190556 | 0025 | 1 | F | Correction of Emergency Fallback | | 15.3.0 | +| 2019-03 | RAN#83 | RP-190202 | 0027 | 3 | F | Transfer of the PSCell information to Core Network | | 15.3.0 | +| 2019-03 | RAN#83 | RP-190558 | 0028 | 1 | F | Release due to pre-emption | | 15.3.0 | +| 2019-03 | RAN#83 | RP-190558 | 0029 | - | F | Handling of APID for the first returned message | | 15.3.0 | +| 2019-03 | RAN#83 | RP-190556 | 0037 | - | F | Clarification on the usage of TNL information | | 15.3.0 | +| 2019-03 | RAN#83 | RP-190556 | 0044 | 1 | F | NG Setup Correction and UE context retention | | 15.3.0 | +| 2019-03 | RAN#83 | RP-190556 | 0045 | 1 | F | UE AMBR handling in PDU Session Resource Setup procedure | | 15.3.0 | +| 2019-03 | RAN#83 | RP-190556 | 0046 | 1 | F | Remove the second tunnel in the PDU session split, 5GC initiated | | 15.3.0 | +| 2019-03 | RAN#83 | RP-190556 | 0048 | 1 | F | When NG-RAN node fails to set up a QoS flow for IMS voice | | 15.3.0 | +| 2019-03 | RAN#83 | RP-190556 | 0052 | - | F | Correction of ASN.1 for PDU Session Resource Modify Response | | 15.3.0 | +| 2019-03 | RAN#83 | RP-190556 | 0053 | 1 | F | Cause value in RRC fallback case | | 15.3.0 | +| 2019-03 | RAN#83 | RP-190556 | 0058 | 2 | F | S-NSSAI update during EPS to 5GS handover | | 15.3.0 | +| 2019-03 | RAN#83 | RP-190561 | 0064 | 1 | F | Introduction of TNL Address discovery for EN-DC (using new container) | | 15.3.0 | +| 2019-03 | RAN#83 | RP-190200 | 0066 | - | F | Correction of ASN.1 for SON Configuration Transfer and PDU Session Resource Modify Request Transfer | | 15.3.0 | +| 2019-07 | RAN#84 | RP-191394 | 0099 | 1 | F | Rapporteur updates for TS 38.413 | | 15.4.0 | +| 2019-07 | RP-84 | RP-191397 | 0041 | 2 | F | Support of ongoing re-mapping on source side during SDAP mobility | | 15.4.0 | +| 2019-07 | RP-84 | RP-191397 | 0067 | 1 | F | NGAP Further Clarification of S-NSSAI Update for EPS to 5GS HO | | 15.4.0 | +| 2019-07 | RP-84 | RP-191394 | 0071 | - | F | CR38413 for Clarification on PDU Session resource modify | | 15.4.0 | +| 2019-07 | RP-84 | RP-191397 | 0075 | 1 | F | Correction of Core Network Type Restrictions | | 15.4.0 | +| 2019-07 | RP-84 | RP-191394 | 0077 | 1 | F | Correction of PDU Session Release | | 15.4.0 | +| 2019-07 | RP-84 | RP-191395 | 0084 | 2 | F | Removal of multiple SCTP associations
PS: This CR was not implemented as it was not based on the latest version of the spec. | | 15.4.0 | +| 2019-07 | RP-84 | RP-191394 | 0095 | - | F | Correction on Error Indication procedure | | 15.4.0 | +| 2019-07 | RP-84 | RP-191394 | 0096 | - | F | Location Report Request Type | | 15.4.0 | + +| | | | | | | | | +|---------|---------|-----------|------|----|---|-------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2019-07 | RP-84 | RP-191394 | 0101 | 2 | F | GUAMI update in case of AMF change | 15.4.0 | +| 2019-07 | RP-84 | RP-191397 | 0102 | 2 | F | Data forwarding and QoS flow remapping | 15.4.0 | +| 2019-07 | RP-84 | RP-191397 | 0111 | 1 | F | Correction of CN Assistance Information | 15.4.0 | +| 2019-07 | RP-84 | RP-191397 | 0112 | | F | Correction of Network Instance | 15.4.0 | +| 2019-07 | RP-84 | RP-191394 | 0117 | 1 | F | Correction of AMF UE NGAP ID | 15.4.0 | +| 2019-07 | RP-84 | RP-191394 | 0130 | 1 | F | Adding PSCell to the User Location Information | 15.4.0 | +| 2019-07 | RP-84 | RP-191394 | 0135 | | F | Correction on Handover Command message | 15.4.0 | +| 2019-07 | RP-84 | RP-191394 | 0148 | | F | Correction of duplicated descriptions on additional UL tunnel information | 15.4.0 | +| 2019-09 | RP-85 | RP-192167 | 0084 | 4 | F | Removal of multiple SCTP associations | 15.5.0 | +| 2019-09 | RP-85 | RP-192166 | 0161 | 2 | F | Correction of secured signalling connection | 15.5.0 | +| 2019-09 | RP-85 | RP-192167 | 0178 | 1 | F | PDU Session fail in Path Switch Request procedure | 15.5.0 | +| 2019-09 | RP-85 | RP-192167 | 0195 | 2 | F | Reroute NSSF provided information | 15.5.0 | +| 2019-09 | RP-85 | RP-192166 | 0199 | | F | Correction of Handover Command message | 15.5.0 | +| 2019-09 | RP-85 | RP-192167 | 0220 | 1 | F | NGAP correction of Initial Context Setup procedure text | 15.5.0 | +| 2019-09 | RP-85 | RP-192167 | 0226 | 1 | F | Rapporteur cleanup of IE semantics descriptions | 15.5.0 | +| 2019-12 | RP-86 | RP-192915 | 0256 | 1 | F | Correction of NAS transparent container | 15.6.0 | +| 2019-12 | RP-86 | RP-192915 | 0258 | 1 | F | Missing procedural texts for NG interface | 15.6.0 | +| 2019-12 | RP-86 | RP-192915 | 0261 | | F | Correction of Handover Command | 15.6.0 | +| 2019-12 | RP-86 | RP-192915 | 0262 | 1 | F | Correction of S-NSSAI coding | 15.6.0 | +| 2019-12 | RP-86 | RP-192916 | 0269 | 1 | F | Correction of Port Number IE in tabular | 15.6.0 | +| 2019-12 | RP-86 | RP-192915 | 0276 | 2 | F | Enable inclusion of the Backup AMF Name IE | 15.6.0 | +| 2019-12 | RP-86 | RP-192916 | 0281 | | F | Correction of NG Handover | 15.6.0 | +| 2019-12 | RP-86 | RP-192896 | 0286 | 3 | F | Addition of abnormal cases for location report procedure | 15.6.0 | +| 2019-12 | RP-86 | RP-192916 | 0300 | 2 | F | CR to 38.413 on clarifications to Xn TNL Configuration Info | 15.6.0 | +| 2019-12 | RP-86 | RP-192916 | 0303 | | F | CR for Clarification on purpose of path switch request | 15.6.0 | +| 2019-12 | RP-86 | RP-193055 | 0304 | - | F | Correction of Xn TNL Configuration Info | 15.6.0 | +| 2019-12 | RP-86 | RP-192912 | 0051 | 7 | B | Support of Direct Data forwarding for handover between 4G and 5G | 16.0.0 | +| 2019-12 | RP-86 | RP-192908 | 0137 | 6 | B | CR to 38.413 for signalling design for RIM | 16.0.0 | +| 2019-12 | RP-86 | RP-192916 | 0143 | 3 | B | The GUAMI and GUMMEI usage for EPS/5GS interworking | 16.0.0 | +| 2019-12 | RP-86 | RP-192913 | 0266 | 1 | C | Extending the MDBV Range | 16.0.0 | +| 2020-03 | RP-87-e | RP-200424 | 0234 | 6 | B | Support of SRVCC from 5G to 3G | 16.1.0 | +| 2020-03 | RP-87-e | RP-200422 | 0291 | 2 | B | Introduction of NR-U | 16.1.0 | +| 2020-03 | RP-87-e | RP-200425 | 0314 | 1 | F | Addition of the PSCell information in the path update procedure | 16.1.0 | +| 2020-03 | RP-87-e | RP-200428 | 0317 | | A | Correction of Warning Security Information in ETWS primary notification | 16.1.0 | +| 2020-03 | RP-87-e | RP-200429 | 0319 | | A | Correction of tabular for Xn TNL Configuration Info | 16.1.0 | +| 2020-03 | RP-87-e | RP-200425 | 0320 | 1 | F | NGAP Rapporteur corrections | 16.1.0 | +| 2020-03 | RP-87-e | RP-200475 | 0329 | 4 | B | E2E delay measurement for QoS monitoring for URLLC | 16.1.0 | +| 2020-03 | RP-87-e | RP-200419 | 0331 | 1 | B | Inter-system direct forwarding with shared SgNB/gNB | 16.1.0 | +| 2020-03 | RP-87-e | RP-200428 | 0335 | | A | Correction of RAN paging priority | 16.1.0 | +| 2020-03 | RP-87-e | RP-200428 | 0337 | 1 | A | PDU session resource in UE context release | 16.1.0 | +| 2020-03 | RP-87-e | RP-200423 | 0347 | 2 | B | Introducing Radio Capability Optimisation (RACS)
(The CR is not implemented. The CR was marked agreed by mistake while the WI is not yet complete) | 16.1.0 | +| 2020-07 | RP-88-e | RP-201077 | 0063 | 13 | B | BL CR to 38.413: Support for IAB | 16.2.0 | +| 2020-07 | RP-88-e | RP-201079 | 0082 | 15 | B | Introduction of NR_IOT support to TS 38.413 | 16.2.0 | +| 2020-07 | RP-88-e | RP-201088 | 0120 | 10 | B | Introduction of NB-IoT Paging and eDRX aspects | 16.2.0 | +| 2020-07 | RP-88-e | RP-201086 | 0153 | 11 | B | Common CP/UP aspects of CIoT UEs when connected to 5GC | 16.2.0 | +| 2020-07 | RP-88-e | RP-201335 | 0156 | 11 | B | Introduction of NB-IoT related NG-AP procedures | 16.2.0 | +| 2020-07 | RP-88-e | RP-201088 | 0157 | 9 | B | Introduction of CP UP NB-IoT Others | 16.2.0 | +| 2020-07 | RP-88-e | RP-201074 | 0168 | 10 | B | Support of NR V2X over NG | 16.2.0 | +| 2020-07 | RP-88-e | RP-201087 | 0172 | 10 | B | Introduction of eMTC connected to 5GC | 16.2.0 | +| 2020-07 | RP-88-e | RP-201086 | 0173 | 8 | B | Introduction of Control Plane CIoT 5GS Optimisation for NB-IOT and eMTC | 16.2.0 | +| 2020-07 | RP-88-e | RP-201086 | 0188 | 10 | B | Introduction of Suspend-Resume | 16.2.0 | +| 2020-07 | RP-88-e | RP-201081 | 0192 | 11 | B | CR for introducing WWC in RAN | 16.2.0 | +| 2020-07 | RP-88-e | RP-201082 | 0237 | 10 | B | Addition of SON features | 16.2.0 | +| 2020-07 | RP-88-e | RP-201082 | 0280 | 7 | B | Addition of MDT feature | 16.2.0 | +| 2020-07 | RP-88-e | RP-201080 | 0290 | 9 | B | Introduction of Non-Public Networks | 16.2.0 | +| 2020-07 | RP-88-e | RP-201079 | 0313 | 4 | B | Support of Ethernet Header Compression | 16.2.0 | + +| | | | | | | | | +|---------|---------|-----------|------|---|---|-----------------------------------------------------------------------------------------------------------|--------| +| 2020-07 | RP-88-e | RP-201078 | 0347 | 6 | B | Introducing Radio Capability Optimisation (RACS) | 16.2.0 | +| 2020-07 | RP-88-e | RP-201091 | 0357 | 2 | A | Clarification the usage of the New AMF UE NGAP ID included in the UE CONTEXT MODIFICATION REQUEST message | 16.2.0 | +| 2020-07 | RP-88-e | RP-201075 | 0362 | 5 | B | Baseline CR for introducing Rel-16 NR mobility enhancement | 16.2.0 | +| 2020-07 | RP-88-e | RP-201083 | 0364 | | F | ASN.1 Correction of the Data Forwarding Response E-RAB List IE | 16.2.0 | +| 2020-07 | RP-88-e | RP-201085 | 0365 | | F | NGAP Rapporteur corrections | 16.2.0 | +| 2020-07 | RP-88-e | RP-201091 | 0371 | 1 | A | Correction of Revoke E-RAB ID | 16.2.0 | +| 2020-07 | RP-88-e | RP-200795 | 0372 | 3 | F | Voice fallback triggered by PDU session resource setup | 16.2.0 | +| 2020-07 | RP-88-e | RP-201091 | 0379 | 1 | A | Correction on AS rekeying handling | 16.2.0 | +| 2020-07 | RP-88-e | RP-201090 | 0389 | 3 | A | Correction to PDU SESSION RESOURCE MODIFY CONFIRM | 16.2.0 | +| 2020-07 | RP-88-e | RP-201092 | 0392 | 1 | A | Selected PLMN ID for untrusted non-3GPP access | 16.2.0 | +| 2020-07 | RP-88-e | RP-201090 | 0395 | 2 | A | Correction on PDU Session Resource Modification Procedures | 16.2.0 | +| 2020-07 | RP-88-e | RP-201085 | 0401 | 1 | F | QoS monitoring for URLLC | 16.2.0 | +| 2020-07 | RP-88-e | RP-201090 | 0408 | 4 | F | Correction of S-NSSAI range | 16.2.0 | +| 2020-09 | RP-89-e | RP-201955 | 0383 | 3 | F | Support of PSCell/SCell-only operation mode | 16.3.0 | +| 2020-09 | RP-89-e | RP-201945 | 0396 | 4 | B | Update of the NRPPa Transport procedure to support NR positioning | 16.3.0 | +| 2020-09 | RP-89-e | RP-201948 | 0416 | - | F | NGAP tabular corrections and asn.1 review | 16.3.0 | +| 2020-09 | RP-89-e | RP-201950 | 0417 | 1 | F | Rapporteur cleanup of NGAP | 16.3.0 | +| 2020-09 | RP-89-e | RP-201955 | 0425 | 1 | F | Correction of NAS PDU in PDU Session Modify | 16.3.0 | +| 2020-09 | RP-89-e | RP-201948 | 0427 | 1 | F | Correction of NPN CAG Cells and non-CAG Cells | 16.3.0 | +| 2020-09 | RP-89-e | RP-201955 | 0443 | 1 | A | Failure case of user location report | 16.3.0 | +| 2020-09 | RP-89-e | RP-201955 | 0445 | 1 | A | Multiple location reporting requests and report | 16.3.0 | +| 2020-09 | RP-89-e | RP-201955 | 0462 | - | F | Correction of asn.1 in NGAP Elementary Procedure List | 16.3.0 | +| 2020-09 | RP-89-e | RP-201955 | 0463 | 1 | F | Corrections to 38.413 on node name type | 16.3.0 | +| 2020-12 | RP-90-e | RP-202314 | 0410 | 1 | F | Correction on Coverage Enhancement Restrictions | 16.4.0 | +| 2020-12 | RP-90-e | RP-202314 | 0411 | 2 | F | Correction on immediate suspension | 16.4.0 | +| 2020-12 | RP-90-e | RP-202310 | 0414 | 1 | F | Add the support for updating RG Level Wireline Access Characteristics and Global Cable ID | 16.4.0 | +| 2020-12 | RP-90-e | RP-202314 | 0483 | 2 | F | Correction of usage of the Extended Connected Time | 16.4.0 | +| 2020-12 | RP-90-e | RP-202312 | 0484 | 1 | F | Support of release on CAG subscription change | 16.4.0 | +| 2020-12 | RP-90-e | RP-202313 | 0485 | - | F | Removal of duplicate import | 16.4.0 | +| 2020-12 | RP-90-e | RP-202311 | 0486 | 1 | F | Correction of Redundant Tunnel Setup | 16.4.0 | +| 2020-12 | RP-90-e | RP-202314 | 0499 | 1 | F | CR38413 for clarification on UE-associated signalling for NB-IoT procedures in Rel-16 | 16.4.0 | +| 2020-12 | RP-90-e | RP-202315 | 0501 | 1 | F | CR38413 for clarification on UE-associated signalling in Rel-16 | 16.4.0 | +| 2020-12 | RP-90-e | RP-202315 | 0505 | 1 | A | Clarification on an abnormal condition in PDU Session Resource Modify Procedure | 16.4.0 | +| 2020-12 | RP-90-e | RP-202313 | 0507 | 1 | F | Introduction of reporting frequency for QoS monitoring for URLLC | 16.4.0 | +| 2020-12 | RP-90-e | RP-202310 | 0511 | 1 | F | Introducing AQP in path switch request acknowledge message | 16.4.0 | +| 2020-12 | RP-90-e | RP-202312 | 0512 | 1 | F | Introducing UE radio capability ID in Connection Establishment Indication | 16.4.0 | +| 2020-12 | RP-90-e | RP-202314 | 0514 | | F | Correction of RAN CP Relocation | 16.4.0 | +| 2021-03 | RP-91-e | RP-210239 | 0355 | 5 | A | Clarification of AS re-keying in the UE Context Modification procedure | 16.5.0 | +| 2021-03 | RP-91-e | RP-210235 | 0508 | 4 | F | Introducing QoS parameters update at Xn handover | 16.5.0 | +| 2021-03 | RP-91-e | RP-210239 | 0520 | 2 | F | Including the Redundant UL NG-U UP TNL Information in the Modify Request | 16.5.0 | +| 2021-03 | RP-91-e | RP-210232 | 0533 | 1 | F | Correction of SNPN failures | 16.5.0 | +| 2021-03 | RP-91-e | RP-210239 | 0534 | 1 | F | Update on QoS monitoring control | 16.5.0 | +| 2021-03 | RP-91-e | RP-210237 | 0537 | 2 | F | Correction on RAT Information Handling | 16.5.0 | +| 2021-03 | RP-91-e | RP-210230 | 0541 | - | F | Correction to NRPPa Transport procedure description | 16.5.0 | +| 2021-03 | RP-91-e | RP-210237 | 0544 | - | F | Correction on UE identity index for eMTC UE in RRC_INACTIVE | 16.5.0 | +| 2021-03 | RP-91-e | RP-210235 | 0557 | 2 | F | Clarification of Secondary RAT in mobility restrictions | 16.5.0 | +| 2021-06 | RP-92-e | RP-211315 | 0477 | 3 | F | Clarification on TAI Slice Support List | 16.6.0 | +| 2021-06 | RP-92-e | RP-211333 | 0522 | 3 | F | Introducing Maximum Integrity Protected Data Rate after EPC to 5GC handover | 16.6.0 | +| 2021-06 | RP-92-e | RP-211333 | 0547 | 2 | F | Supporting use of UE Radio Capability for Paging in RRC_INACTIVE | 16.6.0 | +| 2021-06 | RP-92-e | RP-211333 | 0556 | 2 | A | Interactions with other procedures for the UE TNLA BINDING RELEASE | 16.6.0 | +| 2021-06 | RP-92-e | RP-211333 | 0574 | 1 | F | Correction of PDU Session Resource Modification | 16.6.0 | +| 2021-06 | RP-92-e | RP-211334 | 0583 | 1 | A | Correction on Abnormal Conditions in Handover Preparation | 16.6.0 | + +| | | | | | | | | +|--|--|--|--|--|--|-------------------|--| +| | | | | | | Procedure for R16 | | +|--|--|--|--|--|--|-------------------|--| + +| | | | | | | | | +|---------|---------|-----------|------|----|---|--------------------------------------------------------------------------------------|--------| +| 2021-06 | RP-92-e | RP-211334 | 0603 | 2 | F | Cause value on NG for insufficient UE capabilities CR 38.413 | 16.6.0 | +| 2021-06 | RP-92-e | RP-211333 | 0610 | - | F | Correction on the use of the Core Network Assistance Information for RRC INACTIVE IE | 16.6.0 | +| 2021-06 | RP-92-e | RP-211324 | 0614 | 2 | F | Correction on Extended UE Identity Index Value | 16.6.0 | +| 2021-09 | RP-93-e | RP-211882 | 0376 | 7 | F | NAS Non-Delivery | 16.7.0 | +| 2021-09 | RP-93-e | RP-211881 | 0431 | 4 | F | Correction on Expected UE activity behaviour | 16.7.0 | +| 2021-09 | RP-93-e | RP-211881 | 0626 | | F | Correction of MICO mode | 16.7.0 | +| 2021-09 | RP-93-e | RP-211876 | 0631 | - | F | Correcting Presence of the Cell CAG Information IE in ASN.1 | 16.7.0 | +| 2021-09 | RP-93-e | RP-211882 | 0633 | 1 | A | Deactivation of the MICO mode indication | 16.7.0 | +| 2021-09 | RP-93-e | RP-211881 | 0637 | 1 | F | Correction of NAS PDU Non Delivery | 16.7.0 | +| 2021-09 | RP-93-e | RP-211882 | 0641 | 1 | F | On IEs with reject criticality in the source and target transparent container | 16.7.0 | +| 2021-09 | RP-93-e | RP-211881 | 0645 | 1 | F | Missing QoS Flows not Admitted List in HANDOVER COMMAND | 16.7.0 | +| 2021-09 | RP-93-e | RP-211883 | 0646 | - | F | Clarification on the specified maximum length of the Routing ID Octet String | 16.7.0 | +| 2021-09 | RP-93-e | RP-211882 | 0660 | | F | Correction CR on Network instance | 16.7.0 | +| 2021-12 | RP-94-e | RP-212863 | 0663 | 1 | F | Correction of Data Volume Report | 16.8.0 | +| 2021-12 | RP-94-e | RP-212863 | 0671 | 1 | F | Adding reference for coding of Common Network Instance | 16.8.0 | +| 2021-12 | RP-94-e | RP-212869 | 0679 | 1 | F | Clarification of UE with CAG information in UE subscription | 16.8.0 | +| 2021-12 | RP-94-e | RP-212868 | 0688 | 1 | F | (NGAP CR) support the UE Radio Capability for Paging in RACS context | 16.8.0 | +| 2021-12 | RP-94-e | RP-212871 | 0693 | 1 | F | Redundant network instance for split PDU session | 16.8.0 | +| 2021-12 | RP-94-e | RP-212864 | 0713 | 1 | F | Allocation of TNL addresses for intra-system data forwarding | 16.8.0 | +| 2022-03 | RP-95-e | RP-220278 | 0619 | 3 | F | Support of dynamic ACL during handover and dual connectivity | 16.9.0 | +| 2022-03 | RP-95-e | RP-220243 | 0691 | 2 | F | Direct data forwarding for 4G to 5G handover | 16.9.0 | +| 2022-03 | RP-95-e | RP-220280 | 0727 | 1 | F | Propagation of user consent related information during Xn inter-PLMN handover | 16.9.0 | +| 2022-03 | RP-95-e | RP-220278 | 0735 | | F | Correction on PDU Session Resource Setup procedure | 16.9.0 | +| 2022-03 | RP-95-e | RP-220279 | 0742 | 2 | F | Correction of SNPN setup failure | 16.9.0 | +| 2022-03 | RP-95-e | RP-220280 | 0746 | 1 | F | Value range misalignment for MDT M1, M8 and M9 configuration | 16.9.0 | +| 2022-03 | RP-95-e | RP-220279 | 0751 | 1 | F | Clarification of the usage of an IE in case of DAPS HO | 16.9.0 | +| 2022-03 | RP-95-e | RP-220277 | 0752 | 1 | F | Correction of intra-system Data Forwarding | 16.9.0 | +| 2022-03 | RP-95-e | RP-220243 | 0760 | 2 | F | Direct data forwarding for mobility between DC and SA | 16.9.0 | +| 2022-03 | RP-95-e | RP-220225 | 0490 | 10 | B | Introduction of NTN | 17.0.0 | +| 2022-03 | RP-95-e | RP-220221 | 0530 | 10 | B | BLCR to 38.413_Addition of SON features enhancement | 17.0.0 | +| 2022-03 | RP-95-e | RP-220224 | 0548 | 7 | B | BL CR for NR MBS for 38.413 | 17.0.0 | +| 2022-03 | RP-95-e | RP-220236 | 0558 | 5 | F | Correction for Chapter 10 | 17.0.0 | +| 2022-03 | RP-95-e | RP-220220 | 0594 | 8 | B | Supporting enhanced private network | 17.0.0 | +| 2022-03 | RP-95-e | RP-220223 | 0598 | 8 | B | Introduction of enhanced Industrial IoT over NG | 17.0.0 | +| 2022-03 | RP-95-e | RP-220229 | 0615 | 8 | B | CR to 38.413 on QoE measurement configuration | 17.0.0 | +| 2022-03 | RP-95-e | RP-220294 | 0647 | 3 | B | Support for Enhancement of Redundant PDU Sessions [Paired_ID] | 17.0.0 | +| 2022-03 | RP-95-e | RP-220230 | 0664 | 6 | B | Support for Redcap UEs | 17.0.0 | +| 2022-03 | RP-95-e | RP-220236 | 0666 | 3 | D | NGAP rapporteur corrections | 17.0.0 | +| 2022-03 | RP-95-e | RP-220236 | 0669 | 3 | C | Support for mapping complete security capabilities from NAS [UE_Sec_Caps] | 17.0.0 | +| 2022-03 | RP-95-e | RP-220232 | 0682 | 5 | B | Supporting network slicing enhancement | 17.0.0 | +| 2022-03 | RP-95-e | RP-220221 | 0718 | 4 | B | BLCR to 38.413: Support of MDT enhancement | 17.0.0 | +| 2022-03 | RP-95-e | RP-220219 | 0724 | 3 | B | Introduction of Multi-SIM Support over NG | 17.0.0 | +| 2022-03 | RP-95-e | RP-220235 | 0725 | 3 | B | Support for UE Power Saving Enhancements | 17.0.0 | +| 2022-03 | RP-95-e | RP-220231 | 0743 | 5 | B | Support of 5G ProSe Authorization for NG-AP | 17.0.0 | +| 2022-03 | RP-95-e | RP-220228 | 0754 | - | B | Introduction of NR positioning enhancements to NGAP | 17.0.0 | +| 2022-06 | RP-96 | RP-221811 | 0571 | 8 | B | Support for handling unknown length of gNB identifier [gNB_ID_Length] | 17.1.0 | +| 2022-06 | RP-96 | RP-221134 | 0764 | 2 | F | NGAP ASN.1 review for MBS | 17.1.0 | +| 2022-06 | RP-96 | RP-221145 | 0765 | 1 | D | NGAP rapporteur corrections | 17.1.0 | +| 2022-06 | RP-96 | RP-221134 | 0766 | - | D | Moving MBS Session TNL-related IEs to the correct subclause | 17.1.0 | +| 2022-06 | RP-96 | RP-221127 | 0776 | 1 | F | Adding serving PLMN information in ULI for NTN | 17.1.0 | +| 2022-06 | RP-96 | RP-221141 | 0777 | - | F | Alignment of ASN.1 and tabular for inter-RAT MLB solution | 17.1.0 | +| 2022-06 | RP-96 | RP-221150 | 0784 | 1 | A | Correction of NAS PDU Delivery | 17.1.0 | +| 2022-06 | RP-96 | RP-221129 | 0785 | 2 | F | Correction of Slice Group Configuration | 17.1.0 | +| 2022-06 | RP-96 | RP-221150 | 0791 | 3 | A | NGAP CR for ACL remaining issues | 17.1.0 | +| 2022-06 | RP-96 | RP-221139 | 0793 | 1 | F | Corrections on NR SL relay for 38.413 | 17.1.0 | + +| | | | | | | | | +|---------|---------|-----------|------|---|---|------------------------------------------------------------------------------------|--------| +| 2022-06 | RP-96 | RP-221133 | 0798 | | F | UE Power Saving Correction in NGAP | 17.1.0 | +| 2022-06 | RP-96 | RP-221145 | 0800 | 4 | B | Exchange of protocol support at target RAN node for NG handover [PROT_SUP] | 17.1.0 | +| 2022-06 | RP-96 | RP-221134 | 0801 | 2 | F | MBS NGAP Corrections | 17.1.0 | +| 2022-06 | RP-96 | RP-221141 | 0807 | 1 | F | NGAP Inter-System Load Balancing corrections for procedure and IEs | 17.1.0 | +| 2022-06 | RP-96 | RP-221141 | 0808 | 1 | D | NGAP rapporteur corrections for SON | 17.1.0 | +| 2022-06 | RP-96 | RP-221137 | 0811 | 2 | F | MUSIM Correction on NGAP | 17.1.0 | +| 2022-06 | RP-96 | RP-221134 | 0813 | 1 | F | Correction of MBS Session Management | 17.1.0 | +| 2022-06 | RP-96 | RP-221143 | 0821 | 2 | F | CR to 38.413 for Corrections on NR QoE Capability | 17.1.0 | +| 2022-06 | RP-96 | RP-221134 | 0828 | 1 | F | NGAP corrections on MBS feature | 17.1.0 | +| 2022-06 | RP-96 | RP-221134 | 0829 | 1 | F | Remaining issues over NGAP for NR MBS | 17.1.0 | +| 2022-06 | RP-96 | RP-221141 | 0832 | 1 | F | Correction on R17 SON MDT for 38.413 | 17.1.0 | +| 2022-06 | RP-96 | RP-221143 | 0841 | 2 | F | CR to 38.413 on corrections to configuration details | 17.1.0 | +| 2022-06 | RP-96 | RP-221134 | 0843 | 1 | F | Introduction of broadcast session release required procedure | 17.1.0 | +| 2022-06 | RP-96 | RP-221153 | 0851 | 2 | A | Correction to Frequency Band Info in MDT Configuration | 17.1.0 | +| 2022-06 | RP-96 | RP-221141 | 0853 | - | F | Inter-system energy saving corrections | 17.1.0 | +| 2022-06 | RP-96 | RP-221141 | 0854 | - | F | Correction on user consent modification | 17.1.0 | +| 2022-06 | | | | | | Table of Contents error update | 17.1.1 | +| 2022-09 | RP-97-e | RP-222191 | 0855 | 1 | F | Correction of Inter-system Resource Status Reporting | 17.2.0 | +| 2022-09 | RP-97-e | RP-222191 | 0856 | - | F | ASN.1 correction for Inter-system Resource Status Report | 17.2.0 | +| 2022-09 | RP-97-e | RP-222188 | 0857 | 1 | F | Correction on other leftover issues on NGAP for MBS | 17.2.0 | +| 2022-09 | RP-97-e | RP-222199 | 0859 | 1 | A | CAG access control without mobility restrictions | 17.2.0 | +| 2022-09 | RP-97-e | RP-222188 | 0864 | 1 | F | Further Corrections for NR MBS | 17.2.0 | +| 2022-09 | RP-97-e | RP-222088 | 0866 | 1 | F | Correction of Paging eDRX Information | 17.2.0 | +| 2022-09 | RP-97-e | RP-222192 | 0868 | 1 | F | Correction to R17 QoE | 17.2.0 | +| 2022-09 | RP-97-e | RP-222188 | 0870 | 1 | F | Correction on Multicast Session Deactivation procedure | 17.2.0 | +| 2022-09 | RP-97-e | RP-222188 | 0871 | 1 | F | Introduction of MBS specific cause values | 17.2.0 | +| 2022-09 | RP-97-e | RP-222188 | 0872 | 1 | F | Correction on Multicast Group Paging | 17.2.0 | +| 2022-09 | RP-97-e | RP-222198 | 0875 | 1 | A | Addition of Masked IMEISV for UEs using CP CLoT 5GS optimisation | 17.2.0 | +| 2022-09 | RP-97-e | RP-222191 | 0881 | - | F | Correction to early measurement collection | 17.2.0 | +| 2022-09 | RP-97-e | RP-222627 | 0882 | 2 | F | Collection on beam measurement report configuration in M1 | 17.2.0 | +| 2022-12 | RP-98-e | RP-222882 | 0796 | 5 | F | Correction on User Inactivity for Multicast Session | 17.3.0 | +| 2022-12 | RP-98-e | RP-222893 | 0901 | 1 | F | Additional ULI provision with PScell information | 17.3.0 | +| 2022-12 | RP-98-e | RP-223477 | 0922 | 6 | F | NGAP Corrections for Excess Packet Delay | 17.3.0 | +| 2023-03 | RAN#99 | RP-230593 | 0888 | 2 | F | Correction of inter-system handover to open access HeNB | 17.4.0 | +| 2023-03 | RAN#99 | RP-230584 | 0920 | 2 | F | Correction on the user consent in PATH SWITCH REQUEST ACKNOWLEDGE message (REL-17) | 17.4.0 | +| 2023-03 | RAN#99 | RP-230596 | 0927 | 1 | A | Clarification on IAB Authorized IE in UE Context Modification procedure | 17.4.0 | +| 2023-03 | RAN#99 | RP-230589 | 0929 | 2 | F | Correction on the UE identity index for paging RedCap UE to TS38.413 | 17.4.0 | +| 2023-03 | RAN#99 | RP-230593 | 0930 | - | F | Correction of references to RRC protocol elements | 17.4.0 | +| 2023-03 | RAN#99 | RP-230593 | 0947 | - | F | Correction of ULI for non-3GPP access | 17.4.0 | +| 2023-03 | RAN#99 | RP-230584 | 0949 | - | F | Correction on SON Configuration Transfer | 17.4.0 | +| 2023-03 | RAN#99 | RP-230593 | 0952 | 1 | F | Correction to Global eNB ID in NGAP | 17.4.0 | +| 2023-03 | RAN#99 | RP-230593 | 0963 | 2 | F | Correction on UP security procedure | 17.4.0 | +| 2023-06 | RAN#100 | RP-231073 | 0931 | 2 | F | Correction of Burst Arrival Time semantics description | 17.5.0 | +| 2023-06 | RAN#100 | RP-231075 | 0940 | 3 | A | Corrections on TNL association addition, update and removal | 17.5.0 | +| 2023-06 | RAN#100 | RP-231069 | 0946 | 2 | F | Correction of NB-IoT CP optimization during AMF change | 17.5.0 | +| 2023-06 | RAN#100 | RP-231069 | 0968 | 2 | A | Correction of RRC Resume Cause in PATH SWITCH REQUEST message | 17.5.0 | +| 2023-06 | RAN#100 | RP-231067 | 0976 | 3 | F | Introduction of Hashed UE Identity Index Value for RRC_INACTIVE with eDRX | 17.5.0 | +| 2023-06 | RAN#100 | RP-231071 | 0979 | 2 | F | Correction on Event-based Reporting for Inter-system Resource Status Request | 17.5.0 | +| 2023-06 | RAN#100 | RP-231076 | 0987 | 2 | F | Correction on Extended Packet Delay Budget | 17.5.0 | +| 2023-06 | RAN#100 | RP-231072 | 0996 | 0 | A | Clarify the usage of IAB Supported IE | 17.5.0 | +| 2023-06 | RAN#100 | RP-231078 | 1001 | 1 | F | Correction on the QoE Area Scope IE in QMC Configuration Information | 17.5.0 | +| 2023-09 | RAN#101 | RP-231900 | 0954 | 6 | A | Clarification on maximum length of Routing ID | 17.6.0 | +| 2023-09 | RAN#101 | RP-231902 | 1012 | 1 | A | Correction of Mobility Information | 17.6.0 | + +| | | | | | | | | +|---------|---------|-----------|------|----|---|-------------------------------------------------------------------------------------------------------------|--------| +| 2023-09 | RAN#101 | RP-231896 | 1014 | 1 | F | Transferring of IAB authorized info during inter-CU topology adaptation and backhaul RLF recovery procedure | 17.6.0 | +| 2023-09 | RAN#101 | RP-231897 | 1017 | - | F | Correction on the sharedNGU-MulticastTNLInformation | 17.6.0 | +| 2023-09 | RAN#101 | RP-231897 | 1018 | - | F | ASN.1 and tabular alignment for Broadcast related messages | 17.6.0 | +| 2023-12 | RAN#102 | RP-233854 | 1028 | 2 | F | Support of multiple Trace activations | 17.7.0 | +| 2023-12 | RAN#102 | RP-233854 | 1036 | 1 | F | Correction of Interaction with PDU Session Resource Indication | 17.7.0 | +| 2023-12 | RAN#102 | RP-233824 | 0618 | 14 | B | Introduction of Aerial authorization information and A2X services support | 18.0.0 | +| 2023-12 | RAN#102 | RP-233845 | 0877 | 5 | B | Correction on Location Reporting Control [LRC-Enh] | 18.0.0 | +| 2023-12 | RAN#102 | RP-233814 | 0890 | 8 | B | Network-Controlled Repeaters Authorization | 18.0.0 | +| 2023-12 | RAN#102 | RP-233845 | 0911 | 4 | B | Location Reporting Enhancements [LRC-Enh] | 18.0.0 | +| 2023-12 | RAN#102 | RP-233822 | 0928 | 9 | B | Support for NR Sidelink Relay Enhancements | 18.0.0 | +| 2023-12 | RAN#102 | RP-233832 | 0964 | 8 | B | Support for SON over NG | 18.0.0 | +| 2023-12 | RAN#102 | RP-233838 | 0972 | 9 | B | Introduction of 5G Timing Resiliency and URLLC enhancements | 18.0.0 | +| 2023-12 | RAN#102 | RP-233833 | 0984 | 8 | B | Introduction of R18 QoE measurement enhancements | 18.0.0 | +| 2023-12 | RAN#102 | RP-233840 | 0985 | 10 | B | Support of the enhanced NPN phase 2 | 18.0.0 | +| 2023-12 | RAN#102 | RP-233834 | 0988 | 6 | B | (CR to 38.413) Support for mobile IAB | 18.0.0 | +| 2023-12 | RAN#102 | RP-233815 | 0989 | 7 | B | Introduction of NR Redcap Enhancement | 18.0.0 | +| 2023-12 | RAN#102 | RP-233832 | 0990 | 8 | B | Introduction of MDT enhancements to support Non-Public Networks | 18.0.0 | +| 2023-12 | RAN#102 | RP-233839 | 1006 | 6 | B | Introduction of Enhancement of RAN Slicing for NR | 18.0.0 | +| 2023-12 | RAN#102 | RP-233828 | 1007 | 7 | B | Introduction of NR MBS enhancements | 18.0.0 | +| 2023-12 | RAN#102 | RP-233826 | 1008 | 8 | B | CR for NR NTN | 18.0.0 | +| 2023-12 | RAN#102 | RP-233844 | 1019 | 5 | F | Solving Misalignment in UE Context Release procedure | 18.0.0 | +| 2023-12 | RAN#102 | RP-233830 | 1025 | 4 | B | (CR to 38.413) Support for NR XR | 18.0.0 | +| 2023-12 | RAN#102 | RP-233843 | 1041 | 1 | B | Correction of user location information for wireline access | 18.0.0 | +| 2023-12 | RAN#102 | RP-233845 | 1044 | 1 | B | Introduction of RedCap UE MBS Broadcast reception [RedcapMBS] | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38414/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38414/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a93c4d0bda174b0bd353ced9a4097e6ca326bdc6 --- /dev/null +++ b/marked/Rel-18/38_series/38414/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/38414/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38414/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dad398ad55ab709aab08e88c51219e16b8a2a236 --- /dev/null +++ b/marked/Rel-18/38_series/38414/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b2683fc7b3539cb457c0b4f46c6fb930ea3852979ddf9a69136d44b35d963ce9 +size 7260 diff --git a/marked/Rel-18/38_series/38414/68ca7669d38a3c31f5a2c3a06fa802e3_img.jpg b/marked/Rel-18/38_series/38414/68ca7669d38a3c31f5a2c3a06fa802e3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ef61c449e693594e4f3f138d2f939a5bd48e3e6 --- /dev/null +++ b/marked/Rel-18/38_series/38414/68ca7669d38a3c31f5a2c3a06fa802e3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:80ddf6eae0a33be2449f565434a66846d63227d7fe861f40d1cc8e3c27dc3ef3 +size 13412 diff --git a/marked/Rel-18/38_series/38414/raw.md b/marked/Rel-18/38_series/38414/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..c0f116f2d8fd2d45439be31800b5e6937eb2c3ac --- /dev/null +++ b/marked/Rel-18/38_series/38414/raw.md @@ -0,0 +1,201 @@ + + +# 3GPP TS 38.414 V18.0.0(2024-03) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; NG data transport (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' in small black letters below the logo. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# --- Contents + +| | | +|---------------------------------------------------|----------| +| Foreword ..... | 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 NG 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 NG interface. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2". +- [3] 3GPP TS 29.281: "General Packet Radio System (GPRS) Tunnelling Protocol User Plane (GTPv1-U)". +- [4] IETF RFC 768 (1980-08): "User Datagram Protocol". +- [5] IETF RFC 8200 (2017-07): "Internet Protocol, Version 6 (IPv6) Specification". +- [6] IETF RFC 791 (1981-09): "Internet Protocol". +- [7] IETF RFC 2474 (1998-12): "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers". +- [8] 3GPP TS 38.300: "NR and NG-RAN 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]. + +**gNB:** as defined in TS 38.300 [8]. + +**ng-eNB:** as defined in TS 38.300 [8]. + +**NG-RAN node:** as defined in TS 38.300 [8]. + +**NG-U:** as defined in TS 38.300 [8]. + +**PDU Session:** as defined in TS 23.501[2]. + +## 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]. + +| | | +|------|-----------------------------------------| +| 5GC | 5G Core | +| 5QI | 5G QoS Identifier | +| AMF | Access and Mobility Management Function | +| GTP | GPRS Tunnelling Protocol | +| IP | Internet Protocol | +| NGAP | NG Application Protocol | +| TEID | Tunnel Endpoint Identifier | +| UDP | User Datagram Protocol | +| UPF | User Plane Function | + +# --- 4 Data Link Layer + +Any data link protocol that fulfills the requirements toward the upper layer may be used. + +# --- 5 NG Interface user plane protocol + +## 5.1 General + +Both gNB and ng-eNB can be connected to the 5GC over the NG interface. + +The transport layer for data streams over NG is an IP based Transport. The following figure shows the transport protocol stacks over NG. + +![Diagram showing the transport network layer stack for data streams over NG. 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.](68ca7669d38a3c31f5a2c3a06fa802e3_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 NG. 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 NG** + +The GTP-U (TS 29.281 [3]) protocol over UDP over IP shall be supported as the transport for data streams on the NG interface. The data link layer is as specified in clause 4. + +The transport bearer is identified by the GTP-U TEID (TS 29.281 [3]) and the IP address (source TEID, destination TEID, source IP address, destination IP address). + +## 5.2 GTP-U + +The GTP-U (TS 29.281 [3]) protocol shall be used over the NG-U interface toward the 5GC. + +## 5.3 UDP/IP + +The path protocol used shall be UDP (IETF RFC 768 [4]). + +The UDP port number for GTP-U shall be as defined in TS 29.281 [3]. + +The NG-RAN node and the 5GC shall support fragmentation and assembly of GTP packets at the IP layer. + +The NG-RAN node and the 5GC shall support IPv6 (IETF RFC 8200 [5]) and/or IPv4 (IETF RFC 791 [6]). + +There may be one or several IP addresses in the NG-RAN node and in the 5GC. The packet processing function in the 5GC shall send downstream packets of a given PDU Session to the NG-RAN node IP address (received in NGAP) associated to that particular PDU Session. The packet processing function in the NG-RAN node shall send upstream packets of a given PDU Session to the 5GC IP address (received in NGAP) associated to that particular PDU Session. + +The Transport Layer Address signalled in NGAP 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 [7]) shall be supported. The mapping between traffic categories and Diffserv code points shall be configurable by O&M based on 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. \ No newline at end of file diff --git a/marked/Rel-18/38_series/38422/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38422/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac0918ec81139fd28b157b6a94c21aaa9609d717 --- /dev/null +++ b/marked/Rel-18/38_series/38422/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa3e310ae07f8c6b6cc797408d842ecf0dd18213ae13a952727d76379a0abeae +size 9575 diff --git a/marked/Rel-18/38_series/38422/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38422/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9be956f57294c16ee88aac4fa213400abbb4b479 --- /dev/null +++ b/marked/Rel-18/38_series/38422/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36225da287f5b74375357e8f6f078d5234bd933d9c8ff8d8547a3f44c514208a +size 5866 diff --git a/marked/Rel-18/38_series/38422/68ca7669d38a3c31f5a2c3a06fa802e3_img.jpg b/marked/Rel-18/38_series/38422/68ca7669d38a3c31f5a2c3a06fa802e3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15e1ebd7b8ffe4f9ec48595d68ea87bda3c9d173 --- /dev/null +++ b/marked/Rel-18/38_series/38422/68ca7669d38a3c31f5a2c3a06fa802e3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a65ce3da3bc98b4c8b7c342e3e2a58c44efff032181102d2e428dcec4d149732 +size 20260 diff --git a/marked/Rel-18/38_series/38422/raw.md b/marked/Rel-18/38_series/38422/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e17657596be04d92b982f27610a393ca6196bd43 --- /dev/null +++ b/marked/Rel-18/38_series/38422/raw.md @@ -0,0 +1,192 @@ + + +# 3GPP TS 38.422 V18.1.0(2024-06) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Xn signalling transport (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' in smaller letters below the logo. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **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 Xn signalling bearer..... | 6 | +| 4.1 Functions and protocol stack..... | 6 | +| 5 Data link layer..... | 6 | +| 6 IP layer..... | 7 | +| 7 Transport layer..... | 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 signalling transport to be used across Xn interface. The Xn interface provides means for interconnecting two NG-RAN nodes. The Xn interface is a logical interface between two nodes of the NG-RAN. The present document describes how the XnAP signalling messages are transported over Xn. + +# --- 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 4960: "Stream Control Transmission Protocol". +- [3] 3GPP TS 38.300: "NR; Overall Description; Stage 2". +- [4] IETF RFC 8200 (2017-07): "Internet Protocol, Version 6 (IPv6) Specification". +- [5] IETF RFC 791 (1981-09): "Internet Protocol". +- [6] IETF RFC 2474 (1998-12): "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers". +- [7] IETF RFC 6083 (2011-01): "Datagram Transport Layer Security (DTLS) for Stream Control Transmission Protocol (SCTP)". +- [8] IETF RFC 6335 (2011-08): "Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry". +- [9] IANA: "Stream Control Transmission Protocol (SCTP) Parameters", []. +- [10] 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]. + +**NG-RAN node:** as defined in TS 38.300 [3] + +**Xn:** interface between two NG-RAN nodes, providing an interconnection point between the NG-RAN nodes. + +**Xn-C:** Reference point for the control plane protocol between NG-RAN nodes. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|----------|--------------------------------------| +| IP | Internet Protocol | +| SCTP | Stream Control Transmission Protocol | +| DiffServ | Differentiated Service | +| PPP | Point to Point Protocol | +| IANA | Internet Assigned Number Authority | + +# 4 Xn signalling bearer + +## 4.1 Functions and protocol stack + +Xn-C signalling bearer provides the following functions: + +- Provision of reliable transfer of XnAP message over Xn-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 Xn-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: Xn-C signalling bearer protocol stack diagram](68ca7669d38a3c31f5a2c3a06fa802e3_img.jpg) + +The diagram illustrates the protocol stack for the Xn-C signalling bearer. It is divided into two main sections by a horizontal line with an oval in the center, representing the Xn-C interface. Above the interface is the **Radio Network Layer**, which contains the **XnAP** protocol. Below the interface is the **Transport Network Layer**, which consists of four stacked protocols: **SCTP** (top), **IP**, **Data link layer**, and **Physical layer** (bottom). + +Figure 4.1-1: Xn-C signalling bearer protocol stack diagram + +**Figure 4.1-1: Xn-C signalling bearer protocol stack** + +The Transport Network Layer is based on IP transport, comprising SCTP on top of IP. + +# 5 Data link layer + +The support of any suitable Data Link Layer protocol, e.g. PPP, Ethernet, etc., shall not be prevented. + +# 6 IP layer + +The NG-RAN node shall support IPv6 (IETF RFC 8200 [4]) and/or IPv4 (IETF RFC 791 [5]). + +The IP layer of Xn-C only supports point-to-point transmission for delivering XnAP message. + +The NG-RAN node shall support the Diffserv Code Point marking as described in IETF RFC 2474 [6]. + +# 7 Transport layer + +SCTP (IETF RFC 4960 [2]) shall be supported as the transport layer of Xn-C signalling bearer. The Payload Protocol Identifier (ppid) to be used by SCTP for the application layer protocol XnAP and for DTLS over SCTP (IETF RFC 6083 [7]) is assigned by IANA in [9]. 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. + +An NG RAN node shall support a configuration with a single SCTP association per NG RAN node pair. Configurations with multiple SCTP endpoints per the NG RAN node pair should be supported. When configurations with multiple SCTP associations are supported, the NG RAN node may request to dynamically add/remove SCTP associations between the NG RAN node pair. Within the set of SCTP associations established between one NG RAN node pair, a single SCTP association shall be employed for XnAP elementary procedures that utilize non-UE-associated signalling with the possibility of fail-over to a new association to enable robustness. The SCTP Destination Port number value to be used by XnAP is assigned by IANA in [10]. When a NG-RAN node requests to dynamically add additional SCTP associations between the NG RAN node pair, the SCTP Destination Port number value may be the one assigned by IANA in [10], or any dynamic port value (IETF RFC 6335 [8]). The NG RAN node configuration update procedure shall be the first XnAP procedure triggered on an additional TNLA of an already setup Xn-C interface instance after the TNL association has become operational, and the peer NG RAN node shall associate the TNLA to the Xn-C interface instance using the included Global NG-RAN Node ID. + +Between one pair of two NG-RAN nodes: + +- a single pair of stream identifiers shall be reserved over an SCTP association for the sole use of XnAP 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 XnAP elementary procedures that utilize UE-associated signallings. However, a few pairs (i.e. more than one) should be reserved. +- For a single UE-associated signalling, the NG RAN nodes 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 unless 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 one NG-RAN node, at any time for an already established SCTP association, which shall be handled as defined in IETF RFC 4960 [2] 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. \ No newline at end of file diff --git a/marked/Rel-18/38_series/38425/410562339ce067fdc6fa41940c118658_img.jpg b/marked/Rel-18/38_series/38425/410562339ce067fdc6fa41940c118658_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d57ec7e3ded8a42d2bbbca5b5662e823d62988ad --- /dev/null +++ b/marked/Rel-18/38_series/38425/410562339ce067fdc6fa41940c118658_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:440ad5971b6e6bb1485fd881783072f2710ac6309f7acc45088275e6019fd614 +size 13811 diff --git a/marked/Rel-18/38_series/38425/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38425/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a12bd172eae6962f68aef2ed3de3fb114470d75a --- /dev/null +++ b/marked/Rel-18/38_series/38425/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d5f52c51654e2b8a6e5a500b916923ee9d61278649740fe111ea761205e6bcd +size 9737 diff --git a/marked/Rel-18/38_series/38425/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38425/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..80b09310f7c3e6c4494af5da8986ec17060d3703 --- /dev/null +++ b/marked/Rel-18/38_series/38425/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f2cb4a512fe90b899ba16d951a113fd09a7c8ce13d65b19f60271e63d18ad7a4 +size 5608 diff --git a/marked/Rel-18/38_series/38425/7f17c430b9598e4d748a8041457810b3_img.jpg b/marked/Rel-18/38_series/38425/7f17c430b9598e4d748a8041457810b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..01df424240e292c40f85fb8111c7ca8d7c91141a --- /dev/null +++ b/marked/Rel-18/38_series/38425/7f17c430b9598e4d748a8041457810b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e8a7a028e9479917c7a82287754a9623d3342b52d3279282b3659e3087c8d75 +size 12645 diff --git a/marked/Rel-18/38_series/38425/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-18/38_series/38425/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d96a72a7e2382a3831a41f14612f587420b02212 --- /dev/null +++ b/marked/Rel-18/38_series/38425/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4288e42698096c5c5cb21f8f99e3b48e85f3ff73c9270b802af138ab9cf6a7b2 +size 12448 diff --git a/marked/Rel-18/38_series/38425/raw.md b/marked/Rel-18/38_series/38425/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..51bdb7a133d438a6fe31b08d6a54d6ece45b4a3e --- /dev/null +++ b/marked/Rel-18/38_series/38425/raw.md @@ -0,0 +1,1115 @@ + + +# 3GPP TS 38.425 V18.0.0 (2023-12) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; NR user plane protocol (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 + +## --- **Keywords** + +--- + +NR-RAN + +## **3GPP** + +## --- **Postal address** + +## --- **3GPP support office address** + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + +--- + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|----------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 7 | +| 4 General..... | 7 | +| 4.1 General aspects..... | 7 | +| 5 NR user plane protocol ..... | 7 | +| 5.1 General ..... | 7 | +| 5.2 NR user plane protocol layer services..... | 7 | +| 5.3 Services expected from the Transport Network Layer..... | 8 | +| 5.4 Elementary procedures..... | 9 | +| 5.4.1 Transfer of Downlink User Data ..... | 9 | +| 5.4.1.1 Successful operation ..... | 9 | +| 5.4.1.2 Unsuccessful operation..... | 10 | +| 5.4.2 Downlink Data Delivery Status..... | 10 | +| 5.4.2.1 Successful operation ..... | 10 | +| 5.4.2.2 Unsuccessful operation ..... | 12 | +| 5.4.3 Transfer of Assistance Information ..... | 12 | +| 5.4.3.1 Successful operation ..... | 12 | +| 5.5 Elements for the NR user plane protocol ..... | 13 | +| 5.5.1 General ..... | 13 | +| 5.5.2 Frame format for the NR user plane protocol..... | 14 | +| 5.5.2.1 DL USER DATA (PDU Type 0)..... | 14 | +| 5.5.2.2 DL DATA DELIVERY STATUS (PDU Type 1)..... | 15 | +| 5.5.2.3 ASSISTANCE INFORMATION DATA (PDU Type 2) ..... | 17 | +| 5.5.3 Coding of information elements in frames ..... | 18 | +| 5.5.3.1 PDU Type ..... | 18 | +| 5.5.3.2 Spare ..... | 18 | +| 5.5.3.3 Report polling ..... | 18 | +| 5.5.3.4 NR-U Sequence Number ..... | 18 | +| 5.5.3.5 Desired buffer size for the data radio bearer..... | 18 | +| 5.5.3.6 Desired Data Rate ..... | 18 | +| 5.5.3.7 DL Flush ..... | 19 | +| 5.5.3.8 DL discard NR PDCP PDU SN..... | 19 | +| 5.5.3.9 DL Discard Blocks..... | 19 | +| 5.5.3.10 DL discard NR PDCP PDU SN start ..... | 19 | +| 5.5.3.11 DL discard Number of blocks..... | 19 | +| 5.5.3.12 Discarded Block size ..... | 19 | +| 5.5.3.13 Lost Packet Report..... | 19 | +| 5.5.3.14 Final Frame Indication..... | 20 | +| 5.5.3.15 Number of lost NR-U Sequence Number ranges reported ..... | 20 | +| 5.5.3.16 Start of lost NR-U Sequence Number range..... | 20 | +| 5.5.3.17 End of lost NR-U Sequence Number range..... | 20 | +| 5.5.3.18 Highest Delivered NR PDCP SN Ind ..... | 20 | +| 5.5.3.19 Highest successfully delivered NR PDCP Sequence Number..... | 20 | +| 5.5.3.20 Highest Transmitted NR PDCP SN Ind..... | 20 | +| 5.5.3.21 Highest transmitted NR PDCP Sequence Number ..... | 21 | +| 5.5.3.22 Cause Report..... | 21 | +| 5.5.3.23 Cause Value ..... | 21 | +| 5.5.3.24 Padding ..... | 21 | +| 5.5.3.28 Void ..... | 21 | +| 5.5.3.29 Retransmission flag..... | 21 | + +| | | | +|-------------------------------|-----------------------------------------------------------------------------------|-----------| +| 5.5.3.30 | Delivered Retransmitted NR PDCP SN Ind ..... | 21 | +| 5.5.3.31 | Retransmitted NR PDCP SN Ind ..... | 22 | +| 5.5.3.32 | Successfully delivered retransmitted NR PDCP Sequence Number ..... | 22 | +| 5.5.3.33 | Retransmitted NR PDCP Sequence Number ..... | 22 | +| 5.5.3.34 | Data Rate Indication ..... | 22 | +| 5.5.3.35 | PDCP Duplication Indication ..... | 22 | +| 5.5.3.36 | PDCP Duplication Activation Suggestion ..... | 22 | +| 5.5.3.37 | Number of Assistance Information Field ..... | 22 | +| 5.5.3.38 | Assistance Information Type ..... | 23 | +| 5.5.3.39 | Radio Quality Assistance Information ..... | 23 | +| 5.5.3.40 | Assistance Information Report Polling Flag ..... | 23 | +| 5.5.3.41 | Report Delivered ..... | 23 | +| 5.5.3.42 | DL report NR PDCP PDU SN ..... | 23 | +| 5.5.3.43 | User data existence flag ..... | 23 | +| 5.5.3.44 | Number of octets for Radio Quality Assistance Information Field ..... | 24 | +| 5.5.3.45 | Assistance Information Indication ..... | 24 | +| 5.5.3.46 | UL Delay Indicator ..... | 24 | +| 5.5.3.47 | DL Delay Indicator ..... | 24 | +| 5.5.3.48 | UL Delay DU Result ..... | 24 | +| 5.5.3.49 | DL Delay DU Result ..... | 24 | +| 5.5.3.50 | Delivered NR PDCP SN Range Ind ..... | 25 | +| 5.5.3.51 | Number of successfully delivered out of sequence PDCP Sequence Number range ..... | 25 | +| 5.5.3.52 | Start of successfully delivered out of sequence PDCP Sequence Number range ..... | 25 | +| 5.5.3.53 | End of successfully delivered out of sequence PDCP Sequence Number range ..... | 25 | +| 5.5.3.54 | Request OutOfSeq Report ..... | 25 | +| 5.5.3.55 | NR-U SN Ind. .... | 25 | +| 5.5.3.56 | Feedback Delay Ind. .... | 26 | +| 5.5.3.57 | NR-U Sequence Number of Polling Frame ..... | 26 | +| 5.5.3.58 | Feedback Delay Result ..... | 26 | +| 5.5.3.59 | UL Congestion Information Indicator ..... | 26 | +| 5.5.3.60 | DL Congestion Information Indicator ..... | 26 | +| 5.5.3.61 | UL Congestion Information ..... | 26 | +| 5.5.3.62 | DL Congestion Information ..... | 26 | +| 5.5.4 | Timers ..... | 27 | +| 5.6 | Handling of unknown, unforeseen and erroneous protocol data ..... | 27 | +| Annex A (informative): | Example of using future Extension ..... | 28 | +| A.1 | Example of using Future Extension field ..... | 28 | +| A.1.1 | New IE Flags ..... | 28 | +| Annex B (informative): | Change history ..... | 29 | + +# --- 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 NR user plane protocol functions used within NG-RAN and, for EN-DC and LTE UP-CP split within E-UTRAN. NR user plane protocol functions may reside in nodes terminating either the X2-U (for EN-DC) or the Xn-U or the F1-U interface. User plane protocol functions support both E-UTRA PDCP and NR PDCP. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 29.281: "General Packet Radio System (GPRS) Tunnelling Protocol User Plane (GTPv1-U)". +- [3] 3GPP TS 37.340: "NR; Multi-connectivity; Overall description; Stage-2". +- [4] 3GPP TS 36.321: "Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification". +- [5] 3GPP TS 38.321: "NR; Medium Access Control (MAC) protocol specification". +- [6] 3GPP TS 36.322: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Link Control (RLC) protocol specification". +- [7] 3GPP TS 38.322: "NR; Radio Link Control (RLC) protocol specification". +- [8] 3GPP TS 23.501: "System Architecture for the 5G System". +- [9] 3GPP TS 36.401: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Architecture description". + +# 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]. + +**Corresponding node:** a node interacting with a node hosting PDCP for flow control. In an IAB network, this is the IAB-DU serving the UE for the corresponding data radio bearer. + +**eNB-CP:** as defined in TS 36.401 [9]. + +**eNB-UP:** as defined in TS 36.401 [9]. + +**Master node:** as defined in TS 37.340 [3]. + +**Secondary node:** as defined in TS 37.340 [3]. + +## 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]. + +| | | +|-------|--------------------------------| +| EN-DC | E-UTRA-NR Dual Connectivity | +| IAB | Integrated Access and Backhaul | +| MBS | Multicast/Broadcast Service | +| MR-DC | Multi-RAT Dual Connectivity | +| MRB | MBS Radio Bearer | +| PTM | Point To Multipoint | + +# --- 4 General + +## 4.1 General aspects + +The NR user plane protocol is located in the User Plane of the Radio Network layer over either the Xn or the X2 or the F1 interface or the W1 interface or the UP interface between eNB-CP and eNB-UP. + +The NR user plane protocol is used to convey control information related to the user data flow management of data radio bearers. + +Each NR user plane protocol instance is associated to one data radio bearer only. There is one NR user plane instance per GTP tunnel. When a GTP tunnel is set up, a new NR user plane instance is set up. + +If configured, NR user plane protocol instances exist at the Master node and the Secondary node in the context of DC or at nodes hosting F1-U protocol terminations or at nodes hosting W1-U protocol terminations or at eNB-CP and eNB-UP. The NR user plane protocol supports direct communication between NR user plane protocol entities, regardless of whether they terminate the same or different user plane interfaces. + +**NOTE:** User data radio bearers may be setup for data forwarding purposes during Xn HO or during DC related mobility without requiring the execution of any additional data radio bearer related user plane protocol functions related to an NR user plane protocol instance. + +On each data radio bearer, the NR user plane protocol operates with RLC AM or RLC UM. + +In this version of the present document, NR user plane protocol data is conveyed by GTP-U protocol means, more specifically, by means of the "NR RAN Container" GTP-U extension header as defined in TS 29.281 [2]. + +# --- 5 NR user plane protocol + +## 5.1 General + +The NR user plane protocol layer is using services of the transport network layer in order to allow flow control of user data packets transferred from the node hosting PDCP to the corresponding node. + +## 5.2 NR user plane protocol layer services + +**NOTE 1:** In this section, NR user plane protocol layer services are also applicable to E-UTRA PDCP. With this understanding, each instance of NR PDCP can be replaced by E-UTRA PDCP. + +The following functions are provided by the NR user plane protocol: + +- Provision of NR user plane specific sequence number information for user data transferred from the node hosting NR PDCP to the corresponding node for a specific data radio bearer. +- Information of successful in sequence delivery of NR PDCP PDUs to the UE from the corresponding node for user data associated with a specific data radio bearer. +- Information of NR PDCP PDUs that were not delivered to the UE or not transmitted to the lower layers. +- Information of NR PDCP PDUs transmitted to the lower layers for user data associated with a specific data radio bearer. +- Information of downlink NR PDCP PDUs to be discarded for user data associated with a specific data radio bearer; +- Information of the currently desired buffer size at the corresponding node for transmitting to the UE user data associated with a specific data radio bearer. +- Information of the currently desired data rate in bytes at the corresponding node for transmitting to the UE user data associated with a specific data radio bearer; +- Information of successful in sequence delivery of NR PDCP PDUs to the UE from the corresponding node for retransmission user data associate with a specific data radio bearer; +- Information of NR PDCP PDUs transmitted to the lower layers for retransmission user data associated with a specific data radio bearer. +- Information of the specific events at the corresponding node. +- Information on Radio Link Quality from the corresponding node for user data associated with a specific data radio bearer. +- Information for QoS monitoring from the corresponding node for user data associated with a specific data radio bearer. + +## 5.3 Services expected from the Transport Network Layer + +The NR user plane protocol layer expects the following services from the Transport Network Layer: + +- Transfer of user data. + +## 5.4 Elementary procedures + +NOTE 1: In this section, NR user plane elementary procedures are also applicable to E-UTRA PDCP unless specified otherwise. With this understanding, each instance of NR PDCP can be replaced by E-UTRA PDCP unless specified otherwise. + +### 5.4.1 Transfer of Downlink User Data + +#### 5.4.1.1 Successful operation + +The purpose of the Transfer of Downlink User Data procedure is to provide NR-U specific sequence number information at the transfer of user data carrying a DL NR PDCP PDU from the node hosting the NR PDCP entity to the corresponding node. + +An NR user plane protocol instance making use of the Transfer of Downlink User Data procedure is associated to a single radio bearer only. + +The node hosting the NR PDCP entity shall assign consecutive NR-U sequence numbers to each transferred NR-U packet. A retransmitted NR PDCP PDU shall be assigned a new NR-U sequence number. + +The node hosting the NR PDCP entity indicates to the corresponding node whether this NR-U packet is a retransmission of NR PDCP PDU. + +The node hosting the NR PDCP entity can indicate to the corresponding node to either discard all NR PDCP PDUs up to and including a defined DL discard NR PDCP PDU SN or discard one or a number of blocks of downlink NR PDCP PDUs. + +If the Assistance Information Report Polling Flag is equal to 1, the corresponding node shall, if supported, send the ASSISTANCE INFORMATION DATA to the node hosting the NR PDCP entity. + +The corresponding node shall detect whether an NR-U packet was lost and memorise the respective sequence number after it has declared the respective NR-U packet as being "lost". + +The corresponding node shall transfer the remaining NR PDCP PDUs towards the UE and memorise the highest NR PDCP PDU sequence number of the NR PDCP PDU that was successfully delivered (as defined in TS 36.322 [6] and TS 38.322 [7]) in sequence towards the UE (in case RLC AM is used) and the highest NR PDCP PDU sequence number of the NR PDCP PDU that was transmitted to the lower layers. + +The corresponding node shall send the DL DATA DELIVERY STATUS if the Report Polling Flag is set to 1 or when the NR PDCP PDU with the indicated DL report NR PDCP PDU SN has been successfully delivered, unless a situation of overload at the corresponding node is encountered. The DL DATA DELIVERY STATUS sent as a response to a specific DL report NR PDCP PDU SN shall be sent only when all PDCP PDU SNs up to this DL report NR PDCP PDU have been successfully delivered in-sequence. + +If the Request OutOfSeq Report is set to 1, the corresponding node shall, if supported, include the NR PDCP PDU sequence number successfully delivered out of sequence in the DL DATA DELIVERY STATUS to the node hosting the NR PDCP entity. + +NOTE: The Transfer of Downlink User Data procedure and the associated feedback of lost NR-U packets assist the node hosting the NR PDCP entity in avoiding NR PDCP HFN de-synchronisation. If a deployment decides to not use the Transfer of Downlink User Data procedure, NR PDCP HFN synchronization should be ensured by other means. + +If the User data existence flag is set to 1, the corresponding node assumes that the node hosting the NR PDCP entity has some user data for the concerned data radio bearer. The corresponding node decides whether and when to use DRX for the UE (i.e. the corresponding node may indicate the UE to use DRX even if the flag is set to 1 and the received DL USER DATA frame contains no user data). + +![Diagram illustrating the successful transfer of downlink user data. A 'node hosting NR PDCP' on the left sends 'DL USER DATA' to a 'corresponding node' on the right. Both nodes are represented by rectangles with a horizontal line at their base.](e6df2733626a85205c1db682e6259c46_img.jpg) + +``` + +graph LR + A[node hosting NR PDCP] -- "DL USER DATA" --> B[corresponding node] + +``` + +Diagram illustrating the successful transfer of downlink user data. A 'node hosting NR PDCP' on the left sends 'DL USER DATA' to a 'corresponding node' on the right. Both nodes are represented by rectangles with a horizontal line at their base. + +**Figure 5.4.1.1-1: Successful Transfer of Downlink User Data** + +#### 5.4.1.2 Unsuccessful operation + +Void. + +### 5.4.2 Downlink Data Delivery Status + +#### 5.4.2.1 Successful operation + +The purpose of the Downlink Data Delivery Status procedure is to provide feedback from the corresponding node to the node hosting the NR PDCP entity to allow the node hosting the NR PDCP entity to control the downlink user data flow via the corresponding node for the respective data radio bearer. The corresponding node may also transfer uplink user data for the concerned data radio bearer to the node hosting the NR PDCP entity together with a DL DATA DELIVERY STATUS frame within the same GTP-U PDU. + +The Downlink Data Delivery Status procedure is also used to provide feedback from the corresponding node to the node hosting the NR PDCP entity to allow the node hosting the NR PDCP entity to control the successful delivery of DL control data to the corresponding node. + +When the corresponding node decides to trigger the feedback for Downlink Data Delivery procedure it shall report as specified in section 5.2: + +- in case of RLC AM, the highest NR PDCP PDU sequence number successfully delivered in sequence to the UE among those NR PDCP PDUs received from the node hosting the NR PDCP entity i.e. excludes those retransmission NR PDCP PDUs; + +NOTE 1: If the NR user plane protocol instance is associated a single RLC-AM entity for an MRB, specification text in bullet a) is applicable. + +For all other cases, if the NR user plane protocol instance is associated with an MRB configured with at least one RLC AM entity and RLC-UM, the highest successfully delivered NR PDCP sequence number indicates the combined feedback of the highest NR PDCP sequence number successfully delivered in sequence to all the involved UEs for which the RLC AM entities have been configured, no retransmissions are performed, and the highest NR PDCP sequence number transmitted to the lower layers for PTM. + +- the desired buffer size in bytes for the concerned data radio bearer or for the MRB; +- optionally, the desired data rate in bytes associated with a specific data radio bearer configured for the UE or for the MRB; +- the NR-U packets that were declared as being "lost" by the corresponding node and have not yet been reported to the node hosting the NR PDCP entity within the DL DATA DELIVERY STATUS frame; +- if retransmission NR PDCP PDUs have been delivered, the NR PDCP PDU sequence number associated with the highest NR-U sequence number among the retransmission NR PDCP PDUs successfully delivered to the UE in sequence of NR-U sequence number; +- if retransmission NR PDCP PDUs have been transmitted to the lower layers, the NR PDCP PDU sequence number associated with the highest NR-U sequence number among the retransmission NR PDCP PDUs transmitted to the lower layers in sequence of NR-U sequence number; +- the highest NR PDCP PDU sequence number transmitted to the lower layers among those NR PDCP PDUs received from the node hosting the NR PDCP entity i.e. excludes those retransmission NR PDCP PDUs; + +NOTE 2: If the NR user plane protocol instance is associated with an MRB configured with RLC-UM entities only, the highest NR PDCP PDU sequence number transmitted successfully to all lower layer instances is reported. + +NOTE 3: If a deployment has decided not to use the Transfer of Downlink User Data procedure, d), e) and f) above are not applicable. + +- h) in case of RLC AM, the NR PDCP PDU sequence number successfully delivered out of sequence to the UE among those NR PDCP PDUs received from the node hosting the NR PDCP entity i.e. excludes those retransmission NR PDCP PDUs. + +As soon as the corresponding node detects the successful RACH access by the UE for the corresponding data radio bearer(s), the corresponding node shall send initial DL DATA DELIVERY STATUS frame to the node(s) hosting the NR PDCP entity(ies). The node hosting NR PDCP entity may start sending DL data before receiving the initial DL DATA DELIVERY STATUS frame. In case the DL DATA DELIVERY STATUS frame is sent before any NR PDCP PDU is transferred to lower layers, the information on the highest NR PDCP PDU sequence number successfully delivered in sequence to the UE and the highest NR PDCP PDU sequence number transmitted to the lower layers may not be provided. + +The DL DATA DELIVERY STATUS frame shall also include a final frame indication when this frame is the last DL status report. When receiving such indication, the node hosting the NR PDCP entity considers that no more UL or DL data is expected to be transmitted between the corresponding node and the UE. + +The DL DATA DELIVERY STATUS frame may also include an indication of detected radio link outage or radio link resume for the concerned data radio bearer. When receiving an indication of radio link outage detection, the node hosting the NR PDCP entity considers that traffic delivery over the data radio bearer configured for the UE is unavailable at the corresponding node both in UL and DL. When receiving an indication of radio link resume detection, the node hosting the NR PDCP entity considers that traffic delivery over the data radio bearer configured for the UE is available at the corresponding node both in UL and in DL. When receiving an indication of UL or DL radio link outage detection, the node hosting the NR PDCP entity considers that traffic delivery over the data radio bearer configured for the UE is unavailable at the corresponding node for UL or DL, depending on the indicated outage. When receiving an indication of UL or DL radio link resume detection, the node hosting the NR PDCP entity considers that traffic delivery over the data radio bearer configured for the UE is available at the corresponding node in UL or in DL, depending on the indicated resume. These indications are not applicable to E-UTRA PDCP. + +For report polling triggered reporting, the DL DATA DELIVERY STATUS frame may include the feedback delay result and the NR-U sequence number of the frame where Report Polling Flag is included and that triggered the signalling of the DL DATA DELIVERY STATUS. + +The node hosting the NR PDCP entity, when receiving the DL DATA DELIVERY STATUS frame: + +- regards the desired buffer size under b) and the data rate under c) above as the amount of data to be sent from the hosting node: + - If the value of the desired buffer size is 0, the hosting node shall stop sending any data per bearer. + - If the value of the desired buffer size in b) above is greater than 0, the hosting node may send up to this amount of data per bearer: + - first including the data to be retransmitted; + - then the new data, starting from the last "Highest successfully delivered NR PDCP Sequence Number" for RLC AM if received, or starting from the last "Highest transmitted NR PDCP Sequence Number" for RLC UM if received. + - The value of the desired data rate in c) above is the amount of data desired to be received in a specific amount of time. The amount of time is 1 sec. + - The information of the buffer size in b) above and of the data rate in c) above is valid until the next DL DATA DELIVERY STATUS frame is received. +- is allowed to remove the buffered NR PDCP PDUs of a RLC AM bearer, according to the feedback of successfully delivered NR PDCP PDUs; + +- decides upon the actions necessary to take for NR PDCP PDUs reported other than transmitted and/or successfully delivered. + +In case of RLC AM, after the highest NR PDCP PDU sequence number successfully delivered in sequence is reported to the node hosting the NR PDCP entity, the corresponding node removes the respective NR PDCP PDUs. For RLC UM, the corresponding node may remove the respective NR PDCP PDUs after transmitting to lower layers. + +![Diagram illustrating the Successful Downlink Data Delivery Status. A 'node hosting NR PDCP' on the left and a 'corresponding node' on the right are shown. A horizontal arrow labeled 'DL DATA DELIVERY STATUS' points from the corresponding node to the node hosting NR PDCP. Both nodes are represented by boxes with vertical lines extending downwards to a horizontal bar, indicating a sequence of events or states.](7f17c430b9598e4d748a8041457810b3_img.jpg) + +``` +graph LR; A[node hosting NR PDCP] <--> |DL DATA DELIVERY STATUS| B[corresponding node]; +``` + +Diagram illustrating the Successful Downlink Data Delivery Status. A 'node hosting NR PDCP' on the left and a 'corresponding node' on the right are shown. A horizontal arrow labeled 'DL DATA DELIVERY STATUS' points from the corresponding node to the node hosting NR PDCP. Both nodes are represented by boxes with vertical lines extending downwards to a horizontal bar, indicating a sequence of events or states. + +**Figure 5.4.2.1-1: Successful Downlink Data Delivery Status** + +#### 5.4.2.2 Unsuccessful operation + +Void. + +### 5.4.3 Transfer of Assistance Information + +#### 5.4.3.1 Successful operation + +NOTE 1: In this section, PDCP duplication and delay measurement related information are not applicable to E-UTRA PDCP. + +The purpose of the Transfer of Assistance Information procedure is to provide assistance information to the node hosting the NR PDCP entity. Such information may be taken into consideration by the node hosting the NR PDCP entity for UP management and optimisation procedures. + +An NR user plane protocol instance making use of the Transfer of Assistance Information procedure is associated to a single data radio bearer only. + +The Transfer of Assistance Information procedure may be invoked if + +- the corresponding node decides to send the Radio Quality Assistance Information and/or the PDCP duplication activation suggestion to the node hosting the NR PDCP entity for the concerned data radio bearer or, +- the corresponding node decides to send the Radio Quality Assistance Information to the node hosting the NR PDCP entity for the concerned RLC entity. + +The Transfer of Assistance Information procedure may be invoked if the corresponding node is configured to perform the QoS monitoring and to send the QoS monitoring results to the node hosting the NR PDCP entity for the concerned data radio bearer. + +The ASSISTANCE INFORMATION DATA frame may include one or more Radio Quality Assistance Information. The information shall consist of the information indicated in the Assistance Information Type. + +The ASSISTANCE INFORMATION DATA shall be sent, if supported, when the corresponding node receives a DL USER DATA PDU including the Assistance Information Report Polling Flag set to 1. + +The ASSISTANCE INFORMATION DATA frame may include the PDCP Duplication Activation Suggestion, which informs the node hosting the NR PDCP entity of the suggestion from the corresponding node on whether to activate or not activate DL PDCP duplication. The node hosting the NR PDCP entity may take this information into account to take a decision on whether to activate or not activate PDCP duplication. + +The ASSISTANCE INFORMATION DATA frame may include the UL Delay or/and DL Delay measured by the corresponding node. The node hosting the NR PDCP entity may take this information into account to calculate the whole UL or/and DL delay of RAN. + +The ASSISTANCE INFORMATION DATA frame may include UL Congestion Information and/or DL Congestion information measured by the corresponding node. The node hosting the NR PDCP entity shall, if supported, take this information into account to perform ECN marking in the NG-RAN node, or to further send it to the UPF for ECN marking or information exposure as specified in TS 23.501 [8]. + +![Diagram showing the successful transfer of Assistance Information Data from a corresponding node to a node hosting NR PDCP.](410562339ce067fdc6fa41940c118658_img.jpg) + +``` + +graph LR + A[corresponding node] -- "ASSISTANCE INFORMATION DATA" --> B[node hosting NR PDCP] + +``` + +Diagram showing the successful transfer of Assistance Information Data from a corresponding node to a node hosting NR PDCP. + +Figure 5.4.3.1-1: Successful Transfer of Assistance Information Data + +## 5.5 Elements for the NR user plane protocol + +### 5.5.1 General + +In the present document the structure of frames is specified by using figures similar to figure 5.5.1-1. + +| Bits | | | | | | | | Number of Octets | | | | +|------------------|---|---|---|--------------|---|---------|---|------------------|---------|--|--| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | | +| Field 1 | | | | Field 2 | | | | 1 | Octet 1 | | | +| Field 3 | | | | | | Field 4 | | 2 | Octet 2 | | | +| Field 4 continue | | | | Spare | | | | | Octet 3 | | | +| Spare | | | | Field 5 | | | | 1 | Octet 4 | | | +| Field 6 | | | | | | | | 2 | Octet 5 | | | +| Field 6 continue | | | | Padding Bits | | | | | Octet 6 | | | +| Future Extension | | | | | | | | 0-m | | | | +| Padding | | | | | | | | 0-3 | | | | + +Figure 5.5.1-1: Example frame format + +Unless otherwise indicated, fields which consist of multiple bits within an octet have the most significant bit located at the highest bit position of the field (according to the bit numbers indicated above frame in figure 5.5.1-1). In addition, if a field spans several octets, most significant bits are located in lower numbered octets (right of frame in figure 5.5.1-1). + +The frame is transmitted starting from the lowest numbered octet. Within each octet, the bits are sent according decreasing bit position (bit position 7 first). + +Bits labelled "Spare" should be set to "0" by the sender and should not be checked by the receiver. + +The header part of the frame is always an integer number of octets. The payload part is octet aligned (by adding 'Padding Bits' when needed). The total size of the frame shall not exceed 1018 octets (see TS 29.281 [2]). + +The receiver should be able to remove an additional Future Extension field that may be present. See description of Future Extension field in A.1. + +Padding octets may be added at the end of the frame, see Padding in 5.5.3.24 + +### 5.5.2 Frame format for the NR user plane protocol + +#### 5.5.2.1 DL USER DATA (PDU Type 0) + +This frame format is defined e.g. to allow the corresponding node to detect lost NR-U packets and may be associated with the transfer of a Downlink PDCP PDU. + +The following shows the respective DL USER DATA frame. + +NOTE 1: All information elements defined in Figure 5.5.2.1-1 are also applicable to E-UTRA PDCP. With this understanding, each instance of NR PDCP can be replaced by E-UTRA PDCP. + +| Bits | | | | | | | | Number of Octets | +|-----------------------------------------------|---|---|-------------------------|------------------|--------------------------|--------------------------------------|---------------------|------------------| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | +| PDU Type (=0) | | | | Spare | DL Discard Blocks | DL Flush | Report polling | 1 | +| Spare | | | Request OutOfSeq Report | Report Delivered | User data existence flag | Assistance Info. Report Polling Flag | Retransmission flag | 1 | +| NR-U Sequence Number | | | | | | | | 3 | +| DL discard NR PDCP PDU SN | | | | | | | | 0 or 3 | +| DL discard Number of blocks | | | | | | | | 0 or 1 | +| DL discard NR PDCP PDU SN start (first block) | | | | | | | | 0 or 3 | +| Discarded Block size (first block) | | | | | | | | 0 or 1 | +| ... | | | | | | | | | +| DL discard NR PDCP PDU SN start (last block) | | | | | | | | 0 or 3 | +| Discarded Block size (last block) | | | | | | | | 0 or 1 | +| DL report NR PDCP PDU SN | | | | | | | | 0 or 3 | +| Padding | | | | | | | | 0-3 | + +Figure 5.5.2.1-1: DL USER DATA (PDU Type 0) Format + +#### 5.5.2.2 DL DATA DELIVERY STATUS (PDU Type 1) + +This frame format is defined to transfer feedback to allow the receiving node (i.e. the node that hosts the PDCP entity) to control the downlink user data flow via the sending node (i.e. the corresponding node). + +The following shows the respective DL DATA DELIVERY STATUS frame. The Figure shows an example of how a frame is structured when all optional IEs (i.e. those whose presence is indicated by an associated flag) are present. + +Absence of such an IE changes the position of all subsequent IEs on octet level. + +NOTE 1: All information elements defined in Figure 5.5.2.2-1 are also applicable to E-UTRA PDCP unless specified otherwise in section 5.5.3. With this understanding, each instance of NR PDCP can be replaced by E-UTRA PDCP. + +| Bits | | | | | | | | Number of Octets | +|-----------------------------------------------------------------------------|---------------------|--------------|--------------------------------|------------------------------------|----------------------------------|----------------------------------------|--------------------|---------------------------------------------------------------------------------------| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | +| PDU Type (=1) | | | | Highest Transmitted NR PDCP SN Ind | Highest Delivered NR PDCP SN Ind | Final Frame Ind. | Lost Packet Report | 1 | +| Spare | Feedback Delay Ind. | NR-U SN Ind. | Delivered NR PDCP SN Range Ind | Data rate Ind. | Retransmitted NR PDCP SN Ind | Delivered Retransmitted NR PDCP SN Ind | Cause Report | 1 | +| Desired buffer size for the data radio bearer | | | | | | | | 4 | +| Desired Data Rate | | | | | | | | 0 or 4 | +| Number of lost NR-U Sequence Number ranges reported | | | | | | | | 0 or 1 | +| Start of lost NR-U Sequence Number range | | | | | | | | 0 or (6* Number of reported lost NR-U SN ranges) | +| End of lost NR-U Sequence Number range | | | | | | | | | +| Highest successfully delivered NR PDCP Sequence Number | | | | | | | | 0 or 3 | +| Highest transmitted NR PDCP Sequence Number | | | | | | | | 0 or 3 | +| Cause Value | | | | | | | | 0 or 1 | +| Successfully delivered retransmitted NR PDCP Sequence Number | | | | | | | | 0 or 3 | +| Retransmitted NR PDCP Sequence Number | | | | | | | | 0 or 3 | +| Number of successfully delivered out of sequence PDCP Sequence Number range | | | | | | | | 0 or 1 | +| Start of successfully delivered out of sequence PDCP Sequence Number range | | | | | | | | 0 or (6* Number of successfully delivered out of sequence PDCP Sequence Number range) | +| End of successfully delivered out of sequence PDCP Sequence Number range | | | | | | | | | +| NR-U Sequence Number of Polling Frame | | | | | | | | 0 or 3 | +| Feedback Delay Result | | | | | | | | 0 or 4 | + +| | | +|---------|-----| +| Padding | 0-3 | +|---------|-----| + +Figure 5.5.2.2-1: DL DATA DELIVERY STATUS (PDU Type 1) Format + +#### 5.5.2.3 ASSISTANCE INFORMATION DATA (PDU Type 2) + +This frame format is defined to allow the node hosting the PDCP entity to receive assistance information. + +The following shows the respective ASSISTANCE INFORMATION DATA frame. + +NOTE 1: All information elements defined in Figure 5.5.2.3-1 are also applicable to E-UTRA PDCP unless specified otherwise in section 5.5.3. + +| Bits | | | | | | | | Number of Octets | | +|------------------------------------------------------------------|---|---|---|-----------------|--------------------------------|--------------------------------|----------------------------------------|---------------------------------------------------------------------------------------------------------------------|--| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | +| PDU Type (=2) | | | | PDCP Dupl. Ind. | Assistance Info. Ind. | UL Delay Ind. | DL Delay Ind. | 1 | | +| Spare | | | | | UL Congestion Information Ind. | DL Congestion Information Ind. | PDCP Duplication Activation Suggestion | 1 | | +| Number of Assistance Information Fields | | | | | | | | 0 or 1 | | +| Assistance Information Type | | | | | | | | 0 or (2*Number of Assistance Info Fields + sum of Number of octets for Radio Quality Assistance Information Fields) | | +| Number of octets for Radio Quality Assistance Information Fields | | | | | | | | | | +| Radio Quality Assistance Information | | | | | | | | | | +| UL Delay DU Result | | | | | | | | 0 or 4 | | +| DL Delay DU Result | | | | | | | | 0 or 4 | | +| UL Congestion Information | | | | | | | | 0 or 2 | | +| DL Congestion Information | | | | | | | | 0 or 2 | | + +Figure 5.5.2.3-1: ASSISTANCE INFORMATION DATA (PDU Type 2) Format + +### 5.5.3 Coding of information elements in frames + +NOTE 1: In this section, information elements are also applicable to E-UTRA PDCP unless specified otherwise. With this understanding, each instance of NR PDCP can be replaced by E-UTRA PDCP unless specified otherwise. + +#### 5.5.3.1 PDU Type + +**Description:** The PDU Type indicates the structure of the NR user plane frame. The field takes the value of the PDU Type it identifies; e.g. "0" for PDU Type 0. The PDU type is in bit 4 to bit 7 in the first octet of the frame. + +**Value range:** {0=DL USER DATA, 1=DL DATA DELIVERY STATUS, 2= ASSISTANCE INFORMATION DATA, 3-15=reserved for future PDU type extensions} + +**Field length:** 4 bits + +#### 5.5.3.2 Spare + +**Description:** The spare field is set to "0" by the sender and should not be interpreted by the receiver. This field is reserved for later versions. + +**Value range:** $(0-2^n-1)$ . + +**Field Length:** n bits. + +#### 5.5.3.3 Report polling + +**Description:** This parameter indicates that the node hosting the NR PDCP entity requests providing the downlink delivery status report. + +**Value range:** {0=Downlink Data Delivery Status report not requested, 1= Downlink Data Delivery Status report requested}. + +**Field length:** 1 bit. + +#### 5.5.3.4 NR-U Sequence Number + +**Description:** This parameter indicates the NR-U sequence number as assigned by the node hosting the NR PDCP entity. + +**Value range:** $\{0..2^{24}-1\}$ . + +**Field length:** 3 octets. + +#### 5.5.3.5 Desired buffer size for the data radio bearer + +**Description:** This parameter indicates the desired buffer size in bytes for the concerned data radio bearer as specified in clause 5.4.2.1. + +**Value range:** $\{0..2^{32}-1\}$ . + +**Field length:** 4 octets. + +#### 5.5.3.6 Desired Data Rate + +**Description:** This parameter indicates the amount of data desired to be received in bytes in a specific amount of time (1 s) for a specific data radio bearer established for the UE as specified in clause 5.4.2.1. + +**Value range:** $\{0..2^{32}-1\}$ . + +**Field length:** 4 octets. + +#### 5.5.3.7 DL Flush + +**Description:** This parameter indicates the presence of DL discard NR PDCP PDU SN. + +**Value range:** {0= DL discard NR PDCP PDU SN not present, 1= DL discard NR PDCP PDU SN present}. + +**Field length:** 1 bit. + +#### 5.5.3.8 DL discard NR PDCP PDU SN + +**Description:** This parameter indicates the downlink NR discard PDCP PDU sequence number up to and including which all the NR PDCP PDUs should be discarded. + +**Value range:** {0..218-1}. + +**Field length:** 3 octets. + +#### 5.5.3.9 DL Discard Blocks + +**Description:** This parameter indicates the presence of DL discard Number of blocks, DL discard NR PDCP PDU SN start and Discarded Block size. + +**Value range:** {0= DL discard Number of blocks, DL discard NR PDCP PDU SN start and Discarded Block size not present, 1= DL discard Number of blocks, DL discard NR PDCP PDU SN start and Discarded Block size present}. + +**Field length:** 1 bit. + +#### 5.5.3.10 DL discard NR PDCP PDU SN start + +**Description:** This parameter indicates the starting SN of a downlink NR PDCP PDU block to be discarded. + +**Value range:** {0..218-1}. + +**Field length:** 3 octets. + +#### 5.5.3.11 DL discard Number of blocks + +**Description:** This parameter indicates the number of NR PDCP PDU blocks to be discarded. + +**Value range:** {1..244}. + +**Field length:** 1 octet. + +#### 5.5.3.12 Discarded Block size + +**Description:** This parameter indicates the number of NR PDCP PDUs counted from the starting SN to be discarded. + +**Value range:** {1..255}. + +**Field length:** 1 octet. + +#### 5.5.3.13 Lost Packet Report + +**Description:** This parameter indicates the presence of Number of lost NR-U Sequence Number ranges reported, Start of lost NR-U Sequence Number range and End of lost NR-U Sequence Number range. + +**Value range:** {0= Number of lost NR-U Sequence Number ranges reported, Start of lost NR-U Sequence Number range and End of lost NR-U Sequence Number range not present, 1= Number of lost NR-U Sequence Number ranges reported, Start of lost NR-U Sequence Number range and End of lost NR-U Sequence Number range present}. + +**Field length:** 1 bit. + +#### 5.5.3.14 Final Frame Indication + +**Description:** This parameter indicates whether the frame is the last DL status report as described in clause 5.4.2.1. + +**Value range:** {0=Frame is not final, 1= Frame is final}. + +**Field length:** 1 bit. + +#### 5.5.3.15 Number of lost NR-U Sequence Number ranges reported + +**Description:** This parameter indicates the number of NR-U Sequence Number ranges reported to be lost. + +**Value range:** {1..161}. + +**Field length:** 1 octet. + +#### 5.5.3.16 Start of lost NR-U Sequence Number range + +**Description:** This parameter indicates the start of an NR-U sequence number range reported to be lost. + +**Value range:** {0..224-1}. + +**Field length:** 3 octets. + +#### 5.5.3.17 End of lost NR-U Sequence Number range + +**Description:** This parameter indicates the end of an NR-U sequence number range reported to be lost. + +**Value range:** {0..224-1}. + +**Field length:** 3 octets. + +#### 5.5.3.18 Highest Delivered NR PDCP SN Ind + +**Description:** This parameter indicates the presence of Highest successfully delivered PDCP Sequence Number. + +**Value range:** {0= Highest successfully delivered PDCP Sequence Number not present, 1= Highest successfully delivered PDCP Sequence Number present}. + +**Field length:** 1 bit. + +#### 5.5.3.19 Highest successfully delivered NR PDCP Sequence Number + +**Description:** This parameter indicates feedback about the in-sequence delivery status of NR PDCP PDUs at the corresponding node. + +**Value range:** {0..218-1}. + +**Field length:** 3 octets. + +#### 5.5.3.20 Highest Transmitted NR PDCP SN Ind + +**Description:** This parameter indicates the presence of the Highest transmitted NR PDCP Sequence Number. + +**Value range:** {0= Highest transmitted NR PDCP Sequence Number not present, 1= Highest transmitted NR PDCP Sequence Number present}. + +**Field length:** 1 bit. + +#### 5.5.3.21 Highest transmitted NR PDCP Sequence Number + +**Description:** This parameter indicates the feedback about the transmitted status of NR PDCP PDU sequence at the corresponding node to the lower layers. + +**Value range:** $\{0..2^{18}-1\}$ . + +**Field length:** 3 octets. + +#### 5.5.3.22 Cause Report + +**Description:** This parameter indicates the presence of Cause Value. This information element is not applicable to E-UTRA PDCP. + +**Value range:** $\{0=\text{Cause Value not present}, 1=\text{Cause Value present}\}$ . + +**Field length:** 1 bit. + +#### 5.5.3.23 Cause Value + +**Description:** This parameter indicates specific events reported by the corresponding node. This information element is not applicable to E-UTRA PDCP. + +**Value range:** $\{0=\text{UNKNOWN}, 1=\text{RADIO LINK OUTAGE}, 2=\text{RADIO LINK RESUME}, 3=\text{UL RADIO LINK OUTAGE}, 4=\text{DL RADIO LINK OUTAGE}, 5=\text{UL RADIO LINK RESUME}, 6=\text{DL RADIO LINK RESUME}, 7-228=\text{reserved for future value extensions}, 229-255=\text{reserved for test purposes}\}$ + +**Field length:** 1 octet. + +#### 5.5.3.24 Padding + +**Description:** The padding is included at the end of the frame to ensure that the NR user plane protocol PDU length (including padding and the Future Extension) is $(n*4-2)$ octets, where $n$ is a positive integer. If there is any Future Extension, the padding should be added after the Future Extensions. + +**Field Length:** 0–3 octets. + +#### 5.5.3.28 Void + +Void. + +#### 5.5.3.29 Retransmission flag + +**Description:** This parameter indicates whether the NR PDCP PDU is a retransmission NR-U packet sent by the node hosting the NR PDCP entity to the corresponding node. + +**Value range:** $\{0=\text{Not a retransmission NR-U packet}, 1=\text{Retransmission NR-U packet}\}$ . + +**Field length:** 1 bit. + +#### 5.5.3.30 Delivered Retransmitted NR PDCP SN Ind + +**Description:** This parameter indicates the presence of successfully delivered retransmitted PDCP Sequence Number. + +**Value range:** $\{0=\text{Successfully delivered retransmitted PDCP Sequence Number not present}, 1=\text{Successfully delivered retransmitted PDCP Sequence Number present}\}$ . + +**Field length:** 1 bit. + +#### 5.5.3.31 Retransmitted NR PDCP SN Ind + +**Description:** This parameter indicates the presence of retransmitted NR PDCP Sequence Number. + +**Value range:** {0= Retransmitted NR PDCP Sequence Number not present, 1= Retransmitted NR PDCP Sequence Number present}. + +**Field length:** 1 bit. + +#### 5.5.3.32 Successfully delivered retransmitted NR PDCP Sequence Number + +**Description:** This parameter indicates the NR PDCP PDU sequence number associated with the highest NR-U sequence number among the retransmission NR PDCP PDUs successfully delivered to the UE in sequence of NR-U sequence number. + +**Value range:** {0..218-1}. + +**Field length:** 3 octets. + +#### 5.5.3.33 Retransmitted NR PDCP Sequence Number + +**Description:** This parameter indicates the NR PDCP PDU sequence number associated with the highest NR-U sequence number among the retransmission NR PDCP PDUs transmitted to the lower layers in sequence of NR-U sequence number. + +**Value range:** {0..218-1}. + +**Field length:** 3 octets. + +#### 5.5.3.34 Data Rate Indication + +**Description:** This parameter indicates the presence of the Desired Data Rate. + +**Value range:** {0= Desired Data Rate Information is not present, 1= Desired Data Rate Information is present}. + +**Field length:** 1 bit. + +#### 5.5.3.35 PDCP Duplication Indication + +**Description:** This field indicates the presence of the PDCP Duplication Activation Suggestion. This information element is not applicable to E-UTRA PDCP. + +**Value range:** {0= PDCP Duplication Activation Suggestion not present, 1= PDCP Duplication Activation Suggestion present}. + +**Field length:** 1 bit. + +#### 5.5.3.36 PDCP Duplication Activation Suggestion + +**Description:** This parameter indicates the suggestion given by the corresponding node on whether PDCP duplication should be activated or not. This information element is not applicable to E-UTRA PDCP. + +**Value range:** {0= Do not duplicate, 1= Duplicate}. + +**Field length:** 1 bit. + +#### 5.5.3.37 Number of Assistance Information Field + +**Description:** This field indicates the number of Assistance Information Type and Radio Quality Assistance Information pairs concatenated. + +**Value range:** {1..28-1}. + +**Field length:** 1 octet. + +#### 5.5.3.38 Assistance Information Type + +**Description:** This field describes the type of radio quality assistance information provided, if supported, by the corresponding node to the node hosting the NR PDCP entity. The DL Radio Quality Index is a numerical index expressing the radio quality of the data radio bearer or the RLC entity in DL, where the value 0 represents the lowest quality. The UL Radio Quality Index is a numerical index expressing the radio quality of the data radio bearer or the RLC entity in UL, where the value 0 represents the lowest quality. The averaging window for the Average CQI, Average HARQ Failure, Average HARQ Retransmission, and Average Number of HARQ Transmissions is set by means of configuration. Power Headroom Report is PHR MAC control element reported by as defined in 3GPP TS 36.321[4] and 3GPP TS 38.321[5]. + +**Value range:** {0=UNKNOWN, 1=Average CQI, 2=Average HARQ Failure, 3=Average HARQ Retransmissions, 4= DL Radio Quality Index, 5= UL Radio Quality Index, 6= Power Headroom Report, 7= Average Number of HARQ Transmissions, 8-228=reserved for future value extensions, 229-255=reserved for test purposes}. + +**Field length:** 1 octet. + +#### 5.5.3.39 Radio Quality Assistance Information + +**Description:** This parameter indicates one of the assistance information indicated by the Assistance Information Type. + +**Value range:** {0..28-1}. + +**Field length:** 1 octet. + +#### 5.5.3.40 Assistance Information Report Polling Flag + +**Description:** This parameter indicates that the node hosting the NR PDCP entity requests the corresponding node to send an ASSISTANCE INFORMATION DATA PDU. + +**Value range:** {0= Assistance Information Data not requested, 1= Assistance Information Data requested}. + +**Field length:** 1 bit. + +#### 5.5.3.41 Report Delivered + +**Description:** This parameter indicates the presence of DL report NR PDCP PDU SN. + +**Value range:** {0= DL report NR PDCP PDU SN not present, 1= DL report NR PDCP PDU SN present}. + +**Field length:** 1 bit. + +#### 5.5.3.42 DL report NR PDCP PDU SN + +**Description:** This parameter indicates that the node hosting PDCP entity requests providing the down link delivery status report when the NR PDCP PDU with this sequence number has been successfully delivered. + +**Value range:** {0..224-1}. + +**Field length:** 3 octets. + +#### 5.5.3.43 User data existence flag + +**Description:** This parameter indicates whether the node hosting the NR PDCP entity has some user data for the concerned data radio bearer. + +**Value range:** {0= the node hosting the NR PDCP entity has no more user data for the concerned data radio bearer, 1= the node hosting the NR PDCP entity has some user data for the concerned data radio bearer}. + +**Field length:** 1 bit. + +#### 5.5.3.44 Number of octets for Radio Quality Assistance Information Field + +**Description:** This field indicates the number of octets for Radio Quality Assistance Information exists. For Average CQI, Average HARQ Failure, Average HARQ Retransmissions, DL Radio Quality Index, UL Radio Quality Index, this field shall indicate as “1.” For Average Number of HARQ Transmissions, this field shall indicate as “4”. For Power Headroom Report, this field shall indicate octet length of Power Headroom Report as defined in 3GPP TS 36.321[4] and 3GPP TS 38.321[5]. + +**Value range:** {0..28-1}. + +**Field length:** 1 octets. + +#### 5.5.3.45 Assistance Information Indication + +**Description:** This field indicates the presence of the Number of Assistance Information Fields. + +**Value range:** {0= Number of Assistance Information Fields not present, 1= Number of Assistance Information Fields present}. + +#### 5.5.3.46 UL Delay Indicator + +**Description:** This parameter indicates the presence of the UL Delay DU Result. This information element is not applicable to E-UTRA PDCP. + +**Value range:** {0= UL Delay DU Result not present, 1= UL Delay DU Result present}. + +**Field length:** 1 bit. + +#### 5.5.3.47 DL Delay Indicator + +**Description:** This parameter indicates the presence of the DL Delay DU Result. This information element is not applicable to E-UTRA PDCP. + +**Value range:** {0= DL Delay DU Result not present, 1= DL Delay DU Result present}. + +**Field length:** 1 bit. + +#### 5.5.3.48 UL Delay DU Result + +**Description:** This field indicates UL delay measured at the corresponding node in milliseconds for the concerned DRB over Uu interface. It is encoded as an Unsigned32 binary integer value. The node hosting PDCP entity shall, if supported, use this information to calculate the total UL delay for the concerned DRB and report to the UPF for the purpose of QoS monitoring as specified in [8]. This information element is not applicable to E-UTRA PDCP. + +**Value range:** {0..232-1}. + +**Field length:** 4 octets. + +#### 5.5.3.49 DL Delay DU Result + +**Description:** This field indicates DL delay measured at the corresponding node in milliseconds for the concerned DRB over Uu interface. It is encoded as an Unsigned32 binary integer value. The node hosting PDCP entity shall, if supported, use this information to calculate the total DL delay for the concerned DRB and report to the UPF for the purpose of QoS monitoring as specified in [8]. This information element is not applicable to E-UTRA PDCP. + +**Value range:** {0..232-1}. + +**Field length:** 4 octets. + +#### 5.5.3.50 Delivered NR PDCP SN Range Ind + +**Description:** This field indicates the presence of the Number of successfully delivered out of sequence PDCP Sequence Number range, Start of successfully delivered out of sequence PDCP Sequence Number range and End of successfully delivered out of sequence PDCP Sequence Number range. + +**Value range:** {0= Number of successfully delivered out of sequence PDCP Sequence Number range, Start of successfully delivered out of sequence PDCP Sequence Number range and End of successfully delivered out of sequence PDCP Sequence Number range not present, 1= Number of successfully delivered out of sequence PDCP Sequence Number range, Start of successfully delivered out of sequence PDCP Sequence Number range and End of successfully delivered out of sequence PDCP Sequence Number range present}. + +#### 5.5.3.51 Number of successfully delivered out of sequence PDCP Sequence Number range + +**Description:** This parameter indicates the number of PDCP Sequence Number ranges reported to be successfully delivered out of sequence. + +**Value range:** {1..255}. + +**Field length:** 1 octet. + +#### 5.5.3.52 Start of successfully delivered out of sequence PDCP Sequence Number range + +**Description:** This parameter indicates the start of a PDCN sequence number range reported to be successfully delivered out of sequence. + +**Value range:** {0..218-1}. + +**Field length:** 3 octets. + +#### 5.5.3.53 End of successfully delivered out of sequence PDCP Sequence Number range + +**Description:** This parameter indicates the end of a PDCN sequence number range reported to be successfully delivered out of sequence. + +**Value range:** {0..218-1}. + +**Field length:** 3 octets. + +#### 5.5.3.54 Request OutOfSeq Report + +**Description:** This parameter indicates that the node hosting the NR PDCP entity requests the corresponding node to report the NR PDCP PDU sequence number successfully delivered out of sequence in downlink delivery status report. + +**Value range:** {0= NR PDCP PDU sequence number successfully delivered out of sequence reporting in downlink delivery status report not requested, 1= NR PDCP PDU sequence number successfully delivered out of sequence reporting in downlink delivery status report requested}. + +**Field length:** 1 bit. + +#### 5.5.3.55 NR-U SN Ind. + +**Description:** This parameter indicates the presence of NR-U Sequence Number of the Polling Frame that triggered transmission of the DL DATA DELIVERY STATUS. + +**Value range:** {0= NR-U Sequence Number of Polling Frame not present, 1= NR-U Sequence Number of Polling Frame present}. + +**Field length:** 1 bit. + +#### 5.5.3.56 Feedback Delay Ind. + +**Description:** This parameter indicates the presence of Feedback Delay Result. + +**Value range:** {0= Feedback Delay Result not present, 1= Feedback Delay Result present}. + +**Field length:** 1 bit. + +#### 5.5.3.57 NR-U Sequence Number of Polling Frame + +**Description:** This parameter indicates the NR-U sequence number of the Polling Frame that triggered transmission of the DL DATA DELIVERY STATUS. + +**Value range:** {0..224-1}. + +**Field length:** 3 octets. + +#### 5.5.3.58 Feedback Delay Result + +**Description:** This parameter indicates the feedback delay time measured at the corresponding node in milliseconds from the time of reception of the Polling Frame that triggered transmission of the DL DATA DELIVERY STATUS to the time of transmission of the DL DATA DELIVERY STATUS. It is encoded as an Unsigned32 binary integer value. + +**Value range:** {0..232-1}. + +**Field length:** 4 octets. + +#### 5.5.3.59 UL Congestion Information Indicator + +**Description:** This parameter indicates the presence of UL Congestion Information. + +**Value range:** {0= UL Congestion Information not present, 1= UL Congestion Information present}. + +**Field length:** 1 bit. + +#### 5.5.3.60 DL Congestion Information Indicator + +**Description:** This parameter indicates the presence of DL Congestion Information. + +**Value range:** {0= DL Congestion Information not present, 1= DL Congestion Information present}. + +**Field length:** 1 bit. + +#### 5.5.3.61 UL Congestion Information + +**Description:** For the cases of ECN marking Request, this field indicates the percentage of UL IP packets up to two decimal points that should be ECN marked for a DRB. + +For the case of Congestion Information Request, this field should be interpreted as a percentage of congestion level in UL up to two decimal points for a DRB. + +As an example, value 9574 corresponds to a percentage of 95.74%. + +**Value range:** {0..10000}. + +**Field length:** 2 octets. + +#### 5.5.3.62 DL Congestion Information + +**Description:** For the cases of ECN marking Request, this field indicates the percentage of DL IP packets up to two decimal points that should be ECN marked for a DRB. + +For the case of Congestion Information Request, this field should be interpreted as a percentage of congestion level in DL up to two decimal points for a DRB. + +As an example, value 9574 corresponds to a percentage of 95.74%. + +**Value range:** {0..10000}. + +**Field length:** 2 octets. + +### 5.5.4 Timers + +Not applicable. + +## 5.6 Handling of unknown, unforeseen and erroneous protocol data + +Void. + +# Annex A (informative): Example of using future Extension + +## A.1 Example of using Future Extension field + +| New IE flag 7(E) | New IE flag 6 | New IE flag 5 | New IE flag 4 | New IE flag 3 | New IE flag 2 | New IE flag 1 | New IE flag 0 | 1 Octet New IE Flags | +|------------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|----------------------| +| New IE 1 | | | | | | | | 3 Octets | +| New IE 2 | | | | | | | | 2 Octets | + +Figure X.Y: Example of Future Extension field + +In the Example of the Future Extension field, New IE flag 0 indicates if the New IE 1 is present or not. New IE flag 1 indicates if the new IE 2 is present or not. + +### A.1.1 New IE Flags + +**Description:** The *New IE Flags* IE is only present if at least one new IE is present. The *New IE Flags* IE contains flags indicating which new IEs that are present following the *New IE Flags* IE. The last bit position of the *New IE Flags* IE is used as the Extension Flag to allow the extension of the *New IE Flags* IE in the future. Extension octets of the *New IE Flags* IE shall follow directly after the first octet of the *New IE Flags* IE. When an extension octet of the *New IE Flags* IE is present, then all previous extension octets of the *New IE Flags* IE and the *New IE Flags* IE shall also be present, even if they have all their flag bits indicating no presence of their respective new IEs. + +# Annex B (informative): Change history + +| Change history | | | | | | | | +|----------------|------------|--------------------------------------------------|------|-----|-----|--------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-04 | R3#95b | R3-171173 | - | - | - | TS skeleton | 0.0.0 | +| 2017-04 | R3#95b | R3-171318 | - | - | - | Merged TPs from R3#95b: R3-171346 | 0.0.0 | +| 2017-05 | R3#96 | R3-171743 | - | - | - | Editorial changes | 0.0.2 | +| 2017-06 | R3#ad-hoc2 | | - | - | - | Submission | 0.1.0 | +| 2017-10 | R3#97bis | R3-173978
R3-174222 | - | - | - | Incorporated agreed pCRs from R3#97bis | 0.2.0 | +| 2017-11 | R3#98 | R3-174957
R3-174792
R3-175031
R3-174982 | - | - | - | Incorporated agreed pCRs from R3#98 | 0.3.0 | +| 2017-12 | RP-78 | | | | | TS submitted to RAN plenary for Approval | 1.0.0 | +| 2017-12 | RP-78 | | | | | TS approved by RAN plenary | 15.0.0 | +| 2018-03 | RP-79 | RP-180468 | 0001 | 1 | F | Rapporteur's update to TS38.425 | 15.1.0 | +| 2018-03 | RP-79 | RP-180468 | 0002 | - | F | Corrections to NR UP protocol | 15.1.0 | +| 2018-03 | RP-79 | RP-180468 | 0003 | 1 | B | Data Retransmission Indication | 15.1.0 | +| 2018-03 | RP-79 | RP-180468 | 0006 | 2 | F | Avoiding exceeding the max size of the NR RAN Container | 15.1.0 | +| 2018-03 | RP-79 | RP-180468 | 0010 | 2 | F | Clarification and correction on U-plane for EN-DC | 15.1.0 | +| 2018-03 | RP-79 | RP-180468 | 0014 | 1 | F | Correction of frame structure and Spare extension | 15.1.0 | +| 2018-03 | RP-79 | RP-180468 | 0015 | 1 | F | Triggering of DDDS delivery | 15.1.0 | +| 2018-03 | RP-79 | RP-180468 | 0016 | - | F | Correction to DL Discard | 15.1.0 | +| 2018-03 | RP-79 | RP-180468 | 0017 | 1 | F | Clarifications on UP IE presence | 15.1.0 | +| 2018-06 | RP-80 | RP-181238 | 0022 | 1 | F | Correction on Initial DDDS triggering | 15.2.0 | +| 2018-06 | RP-80 | RP-181238 | 0024 | 1 | F | Clarification of the use of the desired buffer size | 15.2.0 | +| 2018-06 | RP-80 | RP-181238 | 0028 | 1 | F | Correction of Reporting PDCP SN | 15.2.0 | +| 2018-06 | RP-80 | RP-181373 | 0029 | - | F | Correction the max value of one octet | 15.2.0 | +| 2018-06 | RP-80 | RP-181272 | 0032 | 3 | F | Introduction of assistance information for DL PDCP duplication (38.425 Baseline CR covering RAN3 agreements) | 15.2.0 | +| 2018-06 | RP-80 | RP-181239 | 0034 | 1 | F | Final Frame Indication | 15.2.0 | +| 2018-06 | RP-80 | RP-181238 | 0035 | - | F | Correction on padding | 15.2.0 | +| 2018-06 | RP-80 | RP-181238 | 0037 | 1 | F | UL and DL outage | 15.2.0 | +| 2018-06 | RP-80 | RP-181239 | 0039 | 1 | F | Various corrections for the NR UP | 15.2.0 | +| 2018-06 | RP-80 | RP-181239 | 0045 | 1 | F | Rapporteur's update to TS38.425 v15.1.0 | 15.2.0 | +| 2018-06 | RP-80 | RP-181239 | 0047 | - | F | Correction on length for retransmission | 15.2.0 | +| 2018-09 | RP-81 | RP-181922 | 0049 | 4 | F | NR Corrections (38.425 Baseline CR covering RAN3-101 agreements) | 15.3.0 | +| 2018-09 | RP-81 | RP-181920 | 0050 | 2 | F | CR on data existence indication for split bearer | 15.3.0 | +| 2018-09 | RP-81 | RP-181920 | 0051 | 1 | F | CR on Radio Quality Assistance Information for PHR | 15.3.0 | +| 2018-09 | RP-81 | RP-181920 | 0054 | - | F | Correct the range of the DL discard Number of blocks IE | 15.3.0 | +| 2018-09 | RP-81 | RP-181921 | 0057 | 2 | F | Correction on PDCP duplication indication | 15.3.0 | +| 2018-12 | RP-82 | RP-182446 | 0061 | 1 | F | Clarification of the NR UP initialisation | 15.4.0 | +| 2018-12 | RP-82 | RP-182446 | 0066 | - | F | Differentiate RLC AM and UM for user plane | 15.4.0 | +| 2018-12 | RP-82 | RP-182446 | 0067 | - | F | Corrections on DL USER DATA frame | 15.4.0 | +| 2018-12 | RP-82 | RP-182446 | 0068 | - | F | Miscellaneous corrections for User Plane | 15.4.0 | +| 2018-12 | RP-82 | RP-182447 | 0070 | - | F | DDDS polling clarification | 15.4.0 | +| 2018-12 | RP-82 | RP-182447 | 0073 | 1 | F | Retransmission Status in UP | 15.4.0 | +| 2019-03 | RP-83 | RP-190555 | 0078 | 1 | F | Final Frame Indication in NR-UP | 15.5.0 | +| 2019-07 | RP-84 | RP-191394 | 0083 | 2 | F | Clarification on desired buffer size | 15.6.0 | +| 2020-03 | RP-87-e | RP-200425 | 0105 | 2 | B | E2E delay measurement for Qos monitoring for URLLC | 16.0.0 | +| 2020-07 | RP-88-e | RP-201079 | 0102 | 8 | B | Resource efficient PDCP duplication: enhancement 3 | 16.1.0 | +| 2020-07 | RP-88-e | RP-201077 | 0103 | 7 | B | BL CR to 38.425: Support for IAB | 16.1.0 | +| 2020-07 | RP-88-e | RP-201085 | 0107 | - | F | Rapporteur's correction for TS 38.425 | 16.1.0 | +| 2020-09 | RP-89-e | RP-201955 | 0110 | - | A | Correction of Downlink Data Delivery Status | 16.2.0 | +| 2021-03 | RP-91-e | RP-210239 | 0113 | 1 | F | Discard NR PDCP PDUs without PDCP PDU transfer | 16.3.0 | +| 2022-03 | RP-95-e | RP-220217 | 0124 | 5 | B | CR to 38.425: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution | 17.0.0 | +| 2022-03 | RP-95-e | RP-220224 | 0136 | 1 | B | BLCR to TS 38.425: Introduction of MBS | 17.0.0 | +| 2022-09 | RP-97-e | RP-222201 | 0143 | - | F | Correction of F1-U Delay Measurement for QoS Monitoring | 17.1.0 | +| 2022-12 | RP-98-e | RP-222892 | 0140 | 2 | F | Clarification of the desired buffer size in case of retransmissions [DesBufRetrans] | 17.2.0 | +| 2023-03 | RAN#99 | RP-230599 | 0145 | - | F | Correction on W1 interface in TS38.425 | 17.3.0 | +| 2023-12 | RAN#102 | RP-233830 | 0148 | 5 | B | Support for NR XR | 18.0.0 | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|---------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2023-12 | RAN#102 | RP-233844 | 0149 | 2 | F | Correction for HARQ Related Assistance Information in NR User Plane | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38462/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38462/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a93c4d0bda174b0bd353ced9a4097e6ca326bdc6 --- /dev/null +++ b/marked/Rel-18/38_series/38462/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/38462/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38462/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f6fb768ab17825e789a8b4497447e7c8e5fe8767 --- /dev/null +++ b/marked/Rel-18/38_series/38462/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d97ed283ba1829b70c12cd203af25517df9d1564a6390dd43f16d580340ea0d3 +size 6756 diff --git a/marked/Rel-18/38_series/38462/raw.md b/marked/Rel-18/38_series/38462/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..9504146f77acff92b6789d05ee356b2279c00903 --- /dev/null +++ b/marked/Rel-18/38_series/38462/raw.md @@ -0,0 +1,113 @@ + + +# 3GPP TS 38.462 V18.0.0(2024-03) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; E1 signalling transport (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 'P', and the text 'A GLOBAL INITIATIVE' underneath. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 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 7 Void..... 5 + +8 E1 Signalling Transport ..... 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.482 [13]. + +## --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +[1]-[12] Void + +[13] 3GPP TS 37.482: "E1 signalling transport". + +### --- 3 to 7 Void + +## --- 8 E1 Signalling Transport + +See TS 37.482 [13]. \ No newline at end of file diff --git a/marked/Rel-18/38_series/38471/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38471/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..37c6194ed8b647454ac190ba9957cf562dc84a1d --- /dev/null +++ b/marked/Rel-18/38_series/38471/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1eb62e90409bc4ff58dd81318b93a60c80b1cd25cd214cab1f45039772ccfe77 +size 9624 diff --git a/marked/Rel-18/38_series/38471/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38471/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dddb0fb20b4a711b7bad8be82db133003a011fc8 --- /dev/null +++ b/marked/Rel-18/38_series/38471/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1ef8d38ddb6cdf8f9af18a3d3b0f0a98f5b91800082422fb606c012c125ce9b +size 6508 diff --git a/marked/Rel-18/38_series/38471/raw.md b/marked/Rel-18/38_series/38471/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..28edfc3149c4b03ae2c275c7b7168f9e367eba2d --- /dev/null +++ b/marked/Rel-18/38_series/38471/raw.md @@ -0,0 +1,127 @@ + + +# 3GPP TS 38.471 V18.0.0(2024-03) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; F1 layer 1 (Release 18)** + +![5G ADVANCED logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black letters to the right. + +5G ADVANCED logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' in smaller black letters below the logo. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# --- Contents + +- Foreword ..... 4 +- 1 Scope..... 5 +- 2 References..... 5 +- 3 Definitions, symbols and abbreviations ..... 5 + - 3.1 Definitions..... 5 + - 3.2 Abbreviations ..... 5 +- 4 Introduction..... 5 +- Annex A (informative): Change history..... 6** + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the standards allowed to implement Layer 1 on the 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 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". +- [2] 3GPP TS 38.401: "NG-RAN; Architecture Description". +- [3] 3GPP TS 38.300: "NR; Overall description; Stage-2". +- [4] 3GPP TS 37.340: "NR; Multi-connectivity; Overall description; Stage-2". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +gNB-CU: as defined in TS 38.401 [2] + +gNB-DU: as defined in TS 38.401 [2] + +gNB: as defined in TS 38.300 [3] + +en-gNB: as defined in TS 37.340 [4] + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TS 38.411 [1] apply. + +# --- 4 Introduction + +The F1 Layer 1 shall comply with the requirements of clauses 4 through 6 in TS 38.411 [1]. \ No newline at end of file diff --git a/marked/Rel-18/38_series/38508-2/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38508-2/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a54345d9da0622fd4949f3950d2161f4e16bb921 --- /dev/null +++ b/marked/Rel-18/38_series/38508-2/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:daac1efd75878bb1ebf394133f6fd8dcbf4faeac1d31a7ef0f5b8a5025068286 +size 9826 diff --git a/marked/Rel-18/38_series/38508-2/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38508-2/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..800eda03cd9d5342247334b1a21dce2a490f93aa --- /dev/null +++ b/marked/Rel-18/38_series/38508-2/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:767fc7a5d74bd5aef65da3460ecb96f4691ed663157058c9fc965be88aae889b +size 5467 diff --git a/marked/Rel-18/38_series/38508-2/raw.md b/marked/Rel-18/38_series/38508-2/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e49d4ded7d4a29c856c2deb29306b22162431b90 --- /dev/null +++ b/marked/Rel-18/38_series/38508-2/raw.md @@ -0,0 +1,5346 @@ + + +# 3GPP TS 38.508-2 V18.1.0 (2023-12) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; 5GS; User Equipment (UE) conformance specification; Part 2: Common Implementation Conformance Statement (ICS) proforma (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 letters "3GPP" in a stylized, bold, black font. The "3" and "G" are connected at the top. Below the "P" is a red signal icon. Underneath the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, all-caps, 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. + +Keywords +5GS, UE, terminal, testing + +**3GPP** + +Postal address + +3GPP support office address +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + + +**3GPP** + +# Contents + +| | | +|-----------------------------------------------------------------------------------|----------| +| Foreword..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions, symbols and abbreviations..... | 8 | +| 3.1 Definitions..... | 8 | +| 3.2 Symbols..... | 8 | +| 3.3 Abbreviations..... | 8 | +| Annex A (normative):ICS proforma for NR/5GS Generation User Equipment..... | 9 | +| A.1 Guidance for completing the ICS proforma..... | 9 | +| A.1.1 Purposes and structure..... | 9 | +| A.1.2 Abbreviations and conventions..... | 9 | +| A.1.3 Instructions for completing the ICS proforma..... | 10 | +| A.2 Identification of the User Equipment..... | 10 | +| A.2.1 Date of the statement..... | 10 | +| A.2.2 User Equipment Under Test (UEUT) identification..... | 10 | +| A.2.3 Product supplier..... | 11 | +| A.2.4 Client..... | 11 | +| A.2.5 ICS contact person..... | 12 | + +# 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 + +| | | | +|--------------|---------------------------------------------------------------------------------|----| +| A.3 | Identification of the protocol..... | 12 | +| A.4 | ICS proforma tables..... | 12 | +| A.4.1 | UE Implementation Types..... | 12 | +| A.4.2 | UE Service Capabilities..... | 14 | +| A.4.2.1 | 3GPP Standardised UE Service Capabilities..... | 14 | +| A.4.2.1.1 | Bearer Services..... | 14 | +| A.4.3 | Baseline Implementation Capabilities..... | 14 | +| A.4.3.1 | RF Baseline Implementation Capabilities..... | 15 | +| A.4.3.2 | Physical Layer Baseline Implementation Capabilities..... | 24 | +| A.4.3.2A | NR CA Physical Layer Baseline Implementation Capabilities..... | 37 | +| A.4.3.2A.1 | General NR CA capabilities..... | 37 | +| A.4.3.2A.2 | NR Intra-band contiguous CA..... | 38 | +| A.4.3.2A.2.1 | NR Intra-band contiguous CA within FR1..... | 38 | +| A.4.3.2A.2.2 | NR Intra-band contiguous CA within FR2..... | 42 | +| A.4.3.2A.3 | NR Intra-band non-contiguous CA..... | 50 | +| A.4.3.2A.3.1 | NR Intra-band non-contiguous CA within FR1..... | 50 | +| A.4.3.2A.3.2 | NR Intra-band non-contiguous CA within FR2..... | 52 | +| A.4.3.2A.4 | NR Inter-band CA within FR1..... | 66 | +| A.4.3.2A.4.1 | NR Inter-band CA within FR1 (two bands)..... | 66 | +| A.4.3.2A.4.2 | NR Inter-band CA within FR1 (three bands)..... | 73 | +| A.4.3.2A.4.3 | NR Inter-band CA within FR1 (four bands)..... | 76 | +| A.4.3.2A.5 | NR Inter-band CA within FR2..... | 77 | +| A.4.3.2A.5.1 | NR Inter-band CA within FR2 (two bands)..... | 77 | +| A.4.3.2A.6 | NR Inter-band CA between FR1 and FR2..... | 79 | +| A.4.3.2A.6.1 | NR Inter-band CA between FR1 and FR2 (two bands)..... | 79 | +| A.4.3.2A.6.2 | NR Inter-band CA between FR1 and FR2 (three bands)..... | 83 | +| A.4.3.2A.6.3 | NR Inter-band CA between FR1 and FR2 (four bands)..... | 84 | +| A.4.3.2B | NR-DC, EN-DC and NE-DC Physical Layer Baseline Implementation Capabilities..... | 85 | +| A.4.3.2B.1 | NR-DC Physical Layer Baseline Implementation Capabilities..... | 85 | +| A.4.3.2B.1.0 | General NR-DC capabilities..... | 85 | + +| | | | +|-----------------|-----------------------------------------------------------------|-----| +| A.4.3.2B.1.0a | NR-DC within FR1..... | 85 | +| A.4.3.2B.1.0a.1 | NR-DC within FR1 (two bands)..... | 85 | +| A.4.3.2B.1.0b | NR-DC within FR2..... | 86 | +| A.4.3.2B.1.1 | NR-DC between FR1 and FR2..... | 87 | +| A.4.3.2B.1.1.1 | NR-DC between FR1 and FR2 (two bands)..... | 87 | +| A.4.3.2B.2 | EN-DC Physical Layer Baseline Implementation Capabilities..... | 90 | +| A.4.3.2B.2.0 | General EN-DC capabilities..... | 90 | +| A.4.3.2B.2.1 | Intra-band contiguous EN-DC..... | 91 | +| A.4.3.2B.2.2 | Intra-band non-contiguous EN-DC..... | 93 | +| A.4.3.2B.2.3 | Inter-band EN-DC..... | 95 | +| A.4.3.2B.2.3.1 | Inter-band EN-DC within FR1 (two bands)..... | 95 | +| A.4.3.2B.2.3.2 | Inter-band EN-DC within FR1 (three bands)..... | 106 | +| A.4.3.2B.2.3.3 | Inter-band EN-DC within FR1 (four bands)..... | 115 | +| A.4.3.2B.2.3.4 | Inter-band EN-DC within FR1 (five bands)..... | 119 | +| A.4.3.2B.2.3.5 | Inter-band EN-DC within FR1 (six bands)..... | 121 | +| A.4.3.2B.2.3.6 | Inter-band EN-DC including FR2 (two bands)..... | 122 | +| A.4.3.2B.2.3.7 | Inter-band EN-DC including FR2 (three bands)..... | 126 | +| A.4.3.2B.2.3.8 | Inter-band EN-DC including FR2 (four bands)..... | 132 | +| A.4.3.2B.2.3.9 | Inter-band EN-DC including FR2 (five bands)..... | 138 | +| A.4.3.2B.2.3.10 | Void..... | 140 | +| A.4.3.2B.2.3.11 | Inter-band EN-DC including FR1 and FR2 (three bands)..... | 140 | +| A.4.3.2B.2.3.12 | Inter-band EN-DC including FR1 and FR2 (four bands)..... | 141 | +| A.4.3.2B.2.3.13 | Inter-band EN-DC including FR1 and FR2 (five bands)..... | 143 | +| A.4.3.2B.2.3.14 | Inter-band EN-DC including FR1 and FR2 (six bands)..... | 143 | +| A.4.3.2B.3 | NE-DC Physical Layer Baseline Implementation Capabilities..... | 144 | +| A.4.3.2B.3.0 | General NE-DC capabilities..... | 144 | +| A.4.3.2B.3.1 | Inter-band NE-DC within FR1..... | 144 | +| A.4.3.2B.3.1.1 | Inter-band NE-DC within FR1 (two bands)..... | 144 | +| A.4.3.2C | NR SUL Physical Layer Baseline Implementation Capabilities..... | 146 | +| A.4.3.2C.1 | General NR SUL capabilities..... | 146 | + +| | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------|------------| +| A.4.3.2C.2 | SUL band combinations without CA..... | 146 | +| A.4.3.2C.3 | SUL band combinations with CA..... | 147 | +| A.4.3.3 | PDCP Implementation Capabilities..... | 149 | +| A.4.3.4 | RLC Implementation Capabilities..... | 151 | +| A.4.3.5 | MAC Implementation Capabilities..... | 152 | +| A.4.3.6 | Measurement Capabilities..... | 156 | +| A.4.3.7 | General Capabilities..... | 167 | +| A.4.3.8 | Mobility Capabilities..... | 173 | +| A.4.3.9 | Additional capabilities for UE declared capability..... | 177 | +| A.4.3.10 | Sidelink Capabilities..... | 199 | +| A.4.3.11 | High Speed Capabilities..... | 202 | +| A.4.3.12 | RedCap Capabilities..... | 204 | +| A.4.3.13 | Multi-SIM Capabilities..... | 207 | +| A.4.3.14 | MBS Capabilities..... | 208 | +| A.4.4 | Additional information..... | 211 | +| Annex B (informative): Status of NR band and NR CA, NR-DC, EN-DC, NE-DC and NR SUL configurations in 3GPP UE conformance test specifications..... | | 220 | +| Annex C (informative): Change history..... | | 221 | + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +The present document is part 2 of a multi-part deliverable covering the 5G System (5GS) User Equipment (UE) protocol conformance specification, as identified below: + +- 3GPP TS 38.508-1 [11]: "5GS; User Equipment (UE) conformance specification; Part 1: Common test environment ". +- 3GPP TS 38.508-2: **"5GS; User Equipment (UE) conformance specification; Part 2: Common Implementation Conformance Statement (ICS) proforma"** (the present document). + +# 1 Scope + +The present document provides the Implementation Conformance Statement (ICS) proforma for 5G New Radio (NR) User Equipment (UE), in compliance with the relevant requirements. + +Special conformance testing functions can be found in 3GPP TS 38.509 [12] and 3GPP TS 36.509 [14] and the common test environments are included in 3GPP TS 38.508-1 [11] and 3GPP TS 36.508 [13]. + +The present document is valid for UE implemented according to 3GPP Releases starting from Release 15 up to the Release indicated on the cover page of the present document. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 38.523-1: "5GS; UE conformance specification; Part 1: Protocol conformance specification". +- [3] 3GPP TS 38.523-2: "5GS; User Equipment (UE) conformance specification; Part 2: Applicability of protocol test cases". +- [4] 3GPP TS 38.523-3: "5GS; User Equipment (UE) conformance specification; Part 3: Protocol Test Suites". +- [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-2: "NR; User Equipment (UE) conformance specification; Radio transmission and reception; Part 2: Range 2 Standalone". +- [7] 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". +- [8] 3GPP TS 38.521-4: "NR; User Equipment conformance specification; Radio transmission and reception; Part 4: Performance". +- [9] 3GPP TS 38.522: "NR; User Equipment (UE) conformance specification; Applicability of radio transmission, radio reception and radio resource management test cases". +- [10] 3GPP TS 38.533: "NR; User Equipment (UE) conformance specification; Radio resource management". +- [11] 3GPP TS 38.508-1: "5GS; User Equipment (UE) conformance specification; Part 1: Common test environment". + +- [12] 3GPP TS 38.509: "5GS; Special conformance testing functions for UE". +- [13] 3GPP TS 36.508: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRAN); Common Test Environments for User Equipment (UE) Conformance Testing". +- [14] 3GPP TS 36.509: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Special conformance testing functions for User Equipment (UE)". +- [15] 3GPP TS 34.229-2: "Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); User Equipment (UE) conformance specification; Part 2: Implementation Conformance Statement (ICS) specification". +- [16] 3GPP TS 36.523-2: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRAN); User Equipment (UE) conformance specification; Part 2: Implementation Conformance Statement (ICS) proforma specification". +- [17] 3GPP TS 38.306: "NR; User Equipment (UE) radio access capabilities". +- [18] ISO/IEC 9646-7: "Information technology - Open systems interconnection - Conformance testing methodology and framework - Part 7: Implementation Conformance Statements". +- [19] 3GPP TS 38.307: "NR; User Equipments (UEs) supporting a release-independent frequency band". +- [20] 3GPP TS 37.340: "Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Stage 2". +- [21] 3GPP TS 38.300: "NR; NR and NG-RAN Overall Description; Stage 2". +- [22] 3GPP TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3". +- [23] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone". +- [24] 3GPP TS 38.101-2: "NR; User Equipment (UE) radio transmission and reception; Part 2: Range 2 Standalone". +- [25] 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". +- [26] 3GPP TS 23.003: "Numbering, addressing and identification". + +# 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [5] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [5]. + +**Implementation Conformance Statement (ICS):** statement made by the supplier of an implementation or system claimed to conform to a given specification, stating which capabilities have been implemented + +**ICS proforma:** document, in the form of a questionnaire, which when completed for an implementation or system becomes an ICS + +**Implementation extra Information for Testing (IXIT):** A statement made by a supplier or implementer of an UEUT which contains or references all of the information (in addition to that given in the ICS) related to the UEUT and its testing environment, which will enable the test laboratory to run an appropriate test suite against the UEUT + +**IXIT proforma:** A document, in the form of a questionnaire, which when completed for an UEUT becomes an IXIT + +**Protocol Implementation Conformance Statement (PICS):** An ICS for an implementation or system claimed to conform to a given protocol specification + +**Protocol Implementation extra Information for Testing (PIXIT):** An IXIT related to testing for conformance to a given protocol specification + +**Static conformance review:** A review of the extent to which the static conformance requirements are claimed to be supported by the UEUT, by comparing the answers in the ICS(s) with the static conformance requirements expressed in the relevant specification(s) + +## 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]. + +For the purposes of the present document, the following abbreviations apply: + +| | | +|-------|-------------------------------------------------------| +| FFS | For Further Study | +| ICS | Implementation Conformance Statement | +| IXIT | Implementation extra Information for Testing | +| PICS | Protocol Implementation Conformance Statement | +| PIXIT | Protocol Implementation extra Information for Testing | +| SCS | System Conformance Statement | +| TC | Test Case | +| UEUT | User Equipment Under Test | + +# Annex A (normative): ICS proforma for NR/5GS Generation User Equipment + +Notwithstanding the provisions of the copyright clause related to the text of the present document, The Organizational Partners of 3GPP grant that users of the present document may freely reproduce the ICS proforma in this annex so that it can be used for its intended purposes and may further publish the completed ICS. + +## A.1 Guidance for completing the ICS proforma + +### A.1.1 Purposes and structure + +The purpose of this ICS proforma is to provide a mechanism whereby a supplier of an implementation of the requirements defined in relevant specifications may provide information about the implementation in a standardised manner. + +The ICS proforma is subdivided into clauses for the following categories of information: + +- instructions for completing the ICS proforma; +- identification of the implementation; +- identification of the protocol; +- ICS proforma tables (for example: UE implementation types, Teleservices, etc.). + +### A.1.2 Abbreviations and conventions + +The ICS proforma contained in this annex is comprised of information in tabular form in accordance with the guidelines presented in ISO/IEC 9646-7 [18]. + +#### Item column + +The item column contains a number which identifies the item in the table. + +#### Item description column + +The item description column describes in free text each respective item (e.g. parameters, timers, etc.). It implicitly means "is supported by the implementation?". + +#### Reference column + +The reference column gives reference to the relevant 3GPP core specifications. + +#### Release column + +The release column indicates the earliest release from which the capability or option is introduced. + +#### Mnemonic column + +The Mnemonic column contains mnemonic identifiers for each item. + +#### Comments column + +This column is left blank for particular use by the reader of the present document. + +#### References to items + +For each possible item answer (answer in the support column) within the ICS proforma there exists a unique reference, used, for example, in the conditional expressions. It is defined as the table identifier, followed by a solidus character "/", followed by the item number in the table. If there is more than one support column in a table, the columns shall be discriminated by letters (a, b, etc.), respectively. + +### A.1.3 Instructions for completing the ICS proforma + +The supplier of the implementation may complete the ICS proforma in each of the spaces provided. More detailed instructions are given at the beginning of the different clauses of the ICS proforma. + +## --- A.2 Identification of the User Equipment + +Identification of the User Equipment should be filled in so as to provide as much detail as possible regarding version numbers and configuration options. + +The product supplier information and client information should both be filled in if they are different. + +A person who can answer queries regarding information supplied in the ICS should be named as the contact person. + +### A.2.1 Date of the statement + +..... + +### A.2.2 User Equipment Under Test (UEUT) identification + +UEUT name: + +..... + +..... + +Hardware configuration: + +..... + +..... + +..... + +Software configuration: + +..... + +..... + +..... + +### A.2.3 Product supplier + +Name: + +..... + +Address: + +..... + +..... + +..... + +Telephone number: + +..... + +Facsimile number: + +..... + +E-mail address: + +..... + +Additional information: + +..... + +..... + +..... + +### A.2.4 Client + +Name: + +..... + +Address: + +..... + +..... + +..... + +Telephone number: + +..... + +Facsimile number: + +..... + +E-mail address: + +..... + +Additional information: + +..... + +..... + +..... + +### A.2.5 ICS contact person + +Name: + +..... + +Telephone number: + +..... + +Facsimile number: + +..... + +E-mail address: + +..... + +Additional information: + +..... + +..... + +## A.3 Identification of the protocol + +This ICS proforma applies to the 3GPP standards listed in the normative references clause of the present document. + +## A.4 ICS proforma tables + +### A.4.1 UE Implementation Types + +**Table A.4.1-1: UE Radio Technologies** + +| Item | UE Radio Technologies | Ref. | Release | Mnemonic | Comments | +|------|-----------------------|-----------------------|---------|----------|----------| +| 1 | NR FDD | 38.101-1 | Rel-15 | pc_nrFDD | | +| 2 | NR TDD | 38.101-1,
38.101-2 | Rel-15 | pc_nrTDD | | +| 3 | NR sidelink | 38.101-1 | Rel-16 | pc_nrSL | | + +**Table A.4.1-2: UE general functionality** + +| Item | UE Functionality | Ref. | Release | Mnemonic | Comments | +|------|-----------------------|---------------------------------------|---------|--------------------|----------| +| 1 | Multiple NR FDD bands | 38.101-1,
5.2 | Rel-15 | pc_nrFDD_MultiBand | | +| 2 | Multiple NR TDD bands | 38.101-1,
5.2,
38.101-2,
5.2 | Rel-15 | pc_nrTDD_MultiBand | | +| 3 | NR SUL | 38.101-1 | Rel-15 | pc_nrSUL | | +| 4 | NR SDL | 38.101-1 | Rel-15 | pc_nrSDL | | +| 5 | Multiple NR SUL bands | 38.101-1,
5.2 | Rel-15 | pc_nrSUL_MultiBand | | +| 6 | Multiple NR SDL bands | 38.101-1,
5.2 | Rel-15 | pc_nrSDL_MultiBand | | +| 7 | Frequency range FR1 | 38.101-1,
5.1 | Rel-15 | pc_nrFR1 | | +| 8 | Frequency range FR2 | 38.101-2,
5.1 | Rel-15 | pc_nrFR2 | | + +**Table A.4.1-3: RAN-CN Interface Options** + +| Item | UE support of RAN-CN Interface Options | Ref. | Release | Mnemonic | Comments | +|------|----------------------------------------|--------|---------|-----------------|----------| +| 1 | NG-RAN NR | 38.300 | Rel-15 | pc_NG_RAN_NR | Option 2 | +| 2 | EN-DC | 37.340 | Rel-15 | pc_EN_DC | Option 3 | +| 3 | NE-DC | 37.340 | Rel-15 | pc_NE_DC | Option 4 | +| 4 | NG-RAN E-UTRA | 38.300 | Rel-15 | pc_NG_RAN_EUTRA | Option 5 | +| 5 | NGEN-DC | 37.340 | Rel-15 | pc_NGEN_DC | Option 7 | + +**Table A.4.1-4: NSA DC UE Radio Technologies** + +| Item | NSA UE Radio Technologies | Ref. | Release | Mnemonic | Comments | +|------|----------------------------------------|----------------------|---------|------------------------------------|----------| +| 1 | Intra-Band Contiguous EN-DC | 38.101-3,
5.5B.2 | Rel-15 | pc_IntraBand_Contiguous_ENDC | | +| 2 | Intra-Band Non-Contiguous EN-DC | 38.101-3,
5.5B.3 | Rel-15 | pc_IntraBand_NonContiguous_ENDC | | +| 3 | Inter-Band EN-DC within FR1 | 38.101-3,
5.5B.4 | Rel-15 | pc_InterBand_ENDC_WithinFR1 | | +| 4 | Inter-Band EN-DC including FR2 | 38.101-3,
5.5B.5 | Rel-15 | pc_InterBand_ENDC_IncludingFR2 | | +| 5 | Inter-band EN-DC including FR1 and FR2 | 38.101-3,
5.5B.6 | Rel-15 | pc_InterBand_ENDC_IncludingFR1_FR2 | | +| 6 | Inter-band NR-DC between FR1 and FR2 | 38.101-3,
5.5B.7 | Rel-15 | pc_InterBand_NRDC_BetweenFR1_FR2 | | +| 7 | Inter-Band NE-DC within FR1 | 38.101-3,
5.5B.4a | Rel-15 | pc_InterBand_NEDC_WithinFR1 | | + +**Table A.4.1-4A: SA CA UE Radio Technologies** + +| Item | SA UE Radio Technologies | Ref. | Release | Mnemonic | Comments | +|------|-----------------------------------------|---------------------|---------|-----------------------------------------|----------| +| 1 | Intra-Band Contiguous CA within FR1 | 38.101-1,
5.5A.1 | Rel-15 | pc_IntraBand_Contiguous_CA_WithinFR1 | | +| 2 | Intra-Band Non-contiguous CA within FR1 | 38.101-1,
5.5A.2 | Rel-16 | pc_IntraBand_NonContiguous_CA_WithinFR1 | | +| 3 | Intra-Band Contiguous CA within FR2 | 38.101-2,
5.5A.1 | Rel-15 | pc_IntraBand_Contiguous_CA_WithinFR2 | | +| 4 | Intra-Band Non-contiguous CA within FR2 | 38.101-2,
5.5A.2 | Rel-15 | pc_IntraBand_NonContiguous_CA_WithinFR2 | | +| 5 | Inter-Band CA within FR1 | 38.101-1,
5.5A.3 | Rel-15 | pc_InterBand_CA_WithinFR1 | | +| 6 | Inter-Band CA within FR2 | 38.101-2,
5.5A.3 | Rel-16 | pc_InterBand_CA_WithinFR2 | | +| 7 | Inter-band CA between FR1 and FR2 | 38.101-3,
5.5A.1 | Rel-15 | pc_InterBand_CA_BetweenFR1_FR2 | | + +**Table A.4.1-5: 5GS UE Core Technologies** + +| Item | 5GS UE Core Technologies | Ref. | Release | Mnemonic | Comments | +|------|----------------------------------------------------------|-------------------------------------------|---------|--------------|----------------------------------------| +| 1 | UE Supports 5G Core Network | 24.501 | Rel-15 | pc_5GCN | | +| 2 | UE Supports 5G Core Network over non-3GPP Access Network | 24.501, 4.7 | Rel-15 | pc_5GCN_N3AN | | +| 3 | UE Supports only Stand-alone Non-Public Network | 23.501,
5.30.2.3,
38.300,
16.6.1 | Rel-16 | pc_SNPN_only | UEs operating only in SNPn access mode | + +### A.4.2 UE Service Capabilities + +#### A.4.2.1 3GPP Standardised UE Service Capabilities + +##### A.4.2.1.1 Bearer Services + +**Table A.4.2.1.1-1: Definition of Bearer Services** + +| Item | Definition of Bearer Services | Ref. | Release | Mnemonic | Comments | +|------|-------------------------------|------|---------|----------|----------| +| 1 | FFS | | | | | + +### A.4.3 Baseline Implementation Capabilities + +**Table A.4.3-1: Supported protocols** + +| Item | Supported protocols | Ref. | Release | Mnemonic | Comments | +|------|----------------------------------|--------|---------|----------|----------| +| 1 | 5GS Mobility Management | 24.501 | Rel-15 | | | +| 2 | 5GS Session Management | 24.501 | Rel-15 | | | +| 3 | Radio Resource Control | 38.331 | Rel-15 | | | +| 4 | Service Data Adaptation Protocol | 37.324 | Rel-15 | | | +| 5 | Packet Data Convergence Protocol | 38.323 | Rel-15 | | | +| 6 | Radio Link Control | 38.322 | Rel-15 | | | +| 7 | Medium Access Control | 38.321 | Rel-15 | | | +| 8 | Physical Layer | 38.201 | Rel-15 | | | + +**Table A.4.3-2: Special Conformance Testing Functions** + +| Item | Special Conformance Testing Functions | Ref. | Release | Mnemonic | Comments | +|------|---------------------------------------|--------------|---------|----------|----------| +| 1 | UE test loop | 38.509 | Rel-15 | | | +| 2 | UE Power Limit Function (UPLF) | 38.509, 5.11 | Rel-16 | | | + +#### A.4.3.1 RF Baseline Implementation Capabilities + +NOTE: The values indicated in column "Release" for bands are to be understood as the specifications release version in which a band was introduced and not as a mandate that a UE conforming to particular release shall support a particular band. For further guidance to release independent bands see TS 38.307 [19]. + +NOTE: See Annex B for status of completed NR bands and power classes in this version of 3GPP UE conformance test specifications. + +###### **Table A.4.3.1-1: NR FDD FR1 RF Baseline** + +###### **Implementation Capabilities** + +| Item | NR FDD FR1 RF Baseline Implementation Capabilities | Ref. | Release | Mnemonic | Comments | +|----------|---------------------------------------------------------------|---------------|---------|------------------|---------------------| +| 1 | NR Frequency band: 1920-1980 MHz (UL), 2110-2170 MHz (DL) | 38.101-1, 5.2 | Rel-15 | pc_nrBand1_Supp | NR FDD FR1 Band n1 | +| 2 | NR Frequency band: 1850-1910 MHz (UL), 1930-1990 MHz (DL) | 38.101-1, 5.2 | Rel-15 | pc_nrBand2_Supp | NR FDD FR1 Band n2 | +| 3 | NR Frequency band: 1710-1785 MHz (UL), 1805-1880 MHz (DL) | 38.101-1, 5.2 | Rel-15 | pc_nrBand3_Supp | NR FDD FR1 Band n3 | +| 4 | NR Frequency band: 824-849 MHz (UL), 869-894 MHz (DL) | 38.101-1, 5.2 | Rel-15 | pc_nrBand5_Supp | NR FDD FR1 Band n5 | +| 5 | NR Frequency band: 2500-2570 MHz (UL), 2620-2690 MHz (DL) | 38.101-1, 5.2 | Rel-15 | pc_nrBand7_Supp | NR FDD FR1 Band n7 | +| 6 | NR Frequency band: 880-915 MHz (UL), 925-960 MHz (DL) | 38.101-1, 5.2 | Rel-15 | pc_nrBand8_Supp | NR FDD FR1 Band n8 | +| 6a to 6c | Reserved | | | | | +| 6d | NR Frequency band: 699-716 MHz (UL), 729-746 MHz (DL) | 38.101-1, 5.2 | Rel-15 | pc_nrBand12_Supp | NR FDD FR1 Band n12 | +| 6e | NR Frequency band: 777-787 MHz (UL), 746-756 MHz (DL) | 38.101-1, 5.2 | Rel-17 | pc_nrBand13_Supp | NR FDD FR1 Band n13 | +| 6f | NR Frequency band: 788-798 MHz (UL), 758-768 MHz (DL) | 38.101-1, 5.2 | Rel-16 | pc_nrBand14_Supp | NR FDD FR1 Band n14 | +| 6g to 6i | Reserved | | | | | +| 6j | NR Frequency band: 815-830 MHz (UL), 860-875 MHz (DL) | 38.101-1, 5.2 | Rel-16 | pc_nrBand18_Supp | NR FDD FR1 Band n18 | +| 6k | Reserved | | | | | +| 7 | NR Frequency band: 832-862 MHz (UL), 791-821 MHz (DL) | 38.101-1, 5.2 | Rel-15 | pc_nrBand20_Supp | NR FDD FR1 Band n20 | +| 7a to 7c | Reserved | | | | | +| 7d | NR Frequency band: 1626.5-1660.5 MHz (UL), 1525-1559 MHz (DL) | 38.101-1, 5.2 | Rel-17 | pc_nrBand24_Supp | NR FDD FR1 Band n24 | +| 7e | NR Frequency band: 1850-1915 MHz (UL), 1930- 1995 MHz (DL) | 38.101-1, 5.2 | Rel-15 | pc_nrBand25_Supp | NR FDD FR1 Band n25 | +| 7f | NR Frequency band: 814-849 MHz (UL), 859-894 MHz (DL) | 38.101-1, 5.2 | Rel-16 | pc_nrBand26_Supp | NR FDD FR1 Band n26 | +| 7g | Reserved | | | | | +| 8 | NR Frequency band: 703-748 MHz (UL), 758-803 MHz (DL) | 38.101-1, 5.2 | Rel-15 | pc_nrBand28_Supp | NR FDD FR1 Band n28 | +| 8a | Reserved | | | | | +| 8b | NR Frequency band: 2305-2315 MHz (UL), 2350-2360 MHz (DL) | 38.101-1, 5.2 | Rel-16 | pc_nrBand30_Supp | NR FDD FR1 Band n30 | +| 8c to 8d | Reserved | | | | | +| 8e | NR Frequency band: 1920-2010 MHz (UL), 2110-2200 MHz (DL) | 38.101-1, 5.2 | Rel-16 | pc_nrBand65_Supp | NR FDD FR1 Band n65 | +| 9 | NR Frequency band: 1710-1780 MHz (UL), 2110-2200 MHz (DL) | 38.101-1, 5.2 | Rel-15 | pc_nrBand66_Supp | NR FDD FR1 Band n66 | +| 9a to 9c | Reserved | | | | | +| 10 | NR Frequency band: 1695-1710 MHz (UL), 1995-2020 MHz (DL) | 38.101-1, 5.2 | Rel-15 | pc_nrBand70_Supp | NR FDD FR1 Band n70 | +| 11 | NR Frequency band: 663-698 MHz (UL), 617-652 MHz (DL) | 38.101-1, 5.2 | Rel-15 | pc_nrBand71_Supp | NR FDD FR1 Band n71 | + +| | | | | | | +|----------------|--------------------------------------------------------------|---------------|--------|-------------------|----------------------| +| 12
to
13 | Reserved | | | | | +| 14 | NR Frequency band: 1427-1470 MHz (UL),
1475-1518 MHz (DL) | 38.101-1, 5.2 | Rel-15 | pc_nrBand74_Supp | NR FDD FR1 Band n74 | +| 15 | NR Frequency band: 832-862 MHz (UL),
1427-1432 MHz (DL) | 38.101-1, 5.2 | Rel-16 | pc_nrBand91_Supp | NR FDD FR1 Band n91 | +| 16 | NR Frequency band: 832-862 MHz (UL),
1432-1517 MHz (DL) | 38.101-1, 5.2 | Rel-16 | pc_nrBand92_Supp | NR FDD FR1 Band n92 | +| 17 | NR Frequency band: 880-915 MHz (UL),
1427-1432 MHz (DL) | 38.101-1, 5.2 | Rel-16 | pc_nrBand93_Supp | NR FDD FR1 Band n93 | +| 18 | NR Frequency band: 880-915 MHz (UL),
1432-1517 MHz (DL) | 38.101-1, 5.2 | Rel-16 | pc_nrBand94_Supp | NR FDD FR1 Band n94 | +| 19 | NR Frequency band: 874.4-880 MHz (UL),
919.4-925 MHz (DL) | 38.101-1, 5.2 | Rel-17 | pc_nrBand100_Supp | NR FDD FR1 Band n100 | + +**Table A.4.3.1-2: NR TDD FR1 RF Baseline** + +###### **Implementation Capabilities** + +| Item | NR TDD FR1 RF Baseline Implementation Capabilities | Ref. | Release | Mnemonic | Comments | +|----------|----------------------------------------------------|---------------|---------|-------------------|----------------------| +| 0 | NR Frequency band: 2010-2025 MHz (UL / DL) | 38.101-1, 5.2 | Rel-15 | pc_nrBand34_Supp | NR TDD FR1 Band n34 | +| 0a to 0c | Reserved | | | | | +| 1 | NR Frequency band: 2570-2620 MHz (UL / DL) | 38.101-1, 5.2 | Rel-15 | pc_nrBand38_Supp | NR TDD FR1 Band n38 | +| 1a | NR Frequency band: 1880-1920 MHz (UL / DL) | 38.101-1, 5.2 | Rel-15 | pc_nrBand39_Supp | NR TDD FR1 Band n39 | +| 1b | NR Frequency band: 2300-2400 MHz (UL / DL) | 38.101-1, 5.2 | Rel-15 | pc_nrBand40_Supp | NR TDD FR1 Band n40 | +| 2 | NR Frequency band: 2496-2690 MHz (UL / DL) | 38.101-1, 5.2 | Rel-15 | pc_nrBand41_Supp | NR TDD FR1 Band n41 | +| 2a to 2d | Reserved | | | | | +| 2e | NR Frequency band: 5150-5925 MHz (UL / DL) | 38.101-1, 5.2 | Rel-16 | pc_nrBand46_Supp | NR TDD FR1 Band n46 | +| 2f | Reserved | | | | | +| 2g | NR Frequency band: 3550-3700 MHz (UL / DL) | 38.101-1, 5.2 | Rel-16 | pc_nrBand48_Supp | NR TDD FR1 Band n48 | +| 2h | Reserved | | | | | +| 2i | NR Frequency band: 1432-1517 MHz (UL / DL) | 38.101-1, 5.2 | Rel-15 | pc_nrBand50_Supp | NR TDD FR1 Band n50 | +| 2j | NR Frequency band: 1427-1432 MHz (UL / DL) | 38.101-1, 5.2 | Rel-15 | pc_nrBand51_Supp | NR TDD FR1 Band n51 | +| 2k | Reserved | | | | | +| 2l | NR Frequency band: 2483.5-2495 MHz (UL / DL) | 38.101-1, 5.2 | Rel-16 | pc_nrBand53_Supp | NR TDD FR1 Band n53 | +| 3 | NR Frequency band: 3300–4200 MHz (UL / DL) | 38.101-1, 5.2 | Rel-15 | pc_nrBand77_Supp | NR TDD FR1 Band n77 | +| 4 | NR Frequency band: 3300–3800 MHz (UL / DL) | 38.101-1, 5.2 | Rel-15 | pc_nrBand78_Supp | NR TDD FR1 Band n78 | +| 5 | NR Frequency band: 4400–5000 MHz (UL / DL) | 38.101-1, 5.2 | Rel-15 | pc_nrBand79_Supp | NR TDD FR1 Band n79 | +| 6 | Void | | | | | +| 7-11 | Reserved | | | | | +| 12 | NR Frequency band: 5925–7125 MHz (UL / DL) | 38.101-1, 5.2 | Rel-16 | pc_nrBand96_Supp | NR TDD FR1 Band n96 | +| 13 | NR Frequency band: 1900–1910 MHz (UL / DL) | 38.101-1, 5.2 | Rel-17 | pc_nrBand101_Supp | NR TDD FR1 Band n101 | +| 14 | NR Frequency band: 5925 MHz – 6425 MHz | 38.101-1, 5.2 | Rel-16 | pc_nrBand102_Supp | NR TDD FR1 Band n102 | + +**Table A.4.3.1-3: NR TDD FR2 RF Baseline** + +###### **Implementation Capabilities** + +| Item | NR TDD FR2 RF Baseline Implementation Capabilities | Ref. | Release | Mnemonic | Comments | +|------|----------------------------------------------------|---------------|---------|-------------------|----------------------| +| 1 | NR Frequency band: 26500-29500 MHz (UL / DL) | 38.101-2, 5.2 | Rel-15 | pc_nrBand257_Supp | NR TDD FR2 Band n257 | +| 2 | NR Frequency band: 24250-27500 MHz (UL / DL) | 38.101-2, 5.2 | Rel-15 | pc_nrBand258_Supp | NR TDD FR2 Band n258 | +| 2a | NR Frequency band: 39500-43500 MHz (UL / DL) | 38.101-2, 5.2 | Rel-16 | pc_nrBand259_Supp | NR TDD FR2 Band n259 | +| 3 | NR Frequency band: 37000-40000 MHz (UL / DL) | 38.101-2, 5.2 | Rel-15 | pc_nrBand260_Supp | NR TDD FR2 Band n260 | +| 4 | NR Frequency band: 27500-28350 MHz (UL / DL) | 38.101-2, 5.2 | Rel-15 | pc_nrBand261_Supp | NR TDD FR2 Band n261 | + +**Table A.4.3.1-4: NR FR1 PC2 RF Baseline Implementation Capabilities** + +| Item | NR FR1 PC2 RF Baseline Implementation Capabilities | Ref. | Release | Mnemonic | Comments | +|------|-----------------------------------------------------------|-----------------|---------|----------------------|---------------------| +| 0 | NR Frequency band: 2300-2400 MHz (UL / DL) | 38.101-1, 6.2.1 | Rel-16 | pc_nrBand40_PC2_Supp | NR FR1 PC2 Band n40 | +| 1 | NR Frequency band: 2496-2690 MHz (UL / DL) | 38.101-1, 6.2.1 | Rel-15 | pc_nrBand41_PC2_Supp | NR FR1 PC2 Band n41 | +| 2 | NR Frequency band: 3300-4200 MHz (UL / DL) | 38.101-1, 6.2.1 | Rel-15 | pc_nrBand77_PC2_Supp | NR FR1 PC2 Band n77 | +| 3 | NR Frequency band: 3300-3800 MHz (UL / DL) | 38.101-1, 6.2.1 | Rel-15 | pc_nrBand78_PC2_Supp | NR FR1 PC2 Band n78 | +| 4 | NR Frequency band: 4400-5000 MHz (UL / DL) | 38.101-1, 6.2.1 | Rel-15 | pc_nrBand79_PC2_Supp | NR FR1 PC2 Band n79 | +| 5 | NR Frequency band: 2010-2025 MHz | 38.101-1, 6.2.1 | Rel-16 | pc_nrBand34_PC2_Supp | NR FR1 PC2 Band n34 | +| 6 | NR Frequency band: 1880-1920 MHz | 38.101-1, 6.2.1 | Rel-16 | pc_nrBand39_PC2_Supp | NR FR1 PC2 Band n39 | +| 7 | NR Frequency band: 1920-1980 MHz (UL), 2110-2170 MHz (DL) | 38.101-1, 6.2.1 | Rel-17 | pc_nrBand1_PC2_Supp | NR FR1 PC2 Band n1 | +| 8 | NR Frequency band: 1710-1785 MHz (UL), 1805-1880 MHz (DL) | 38.101-1, 6.2.1 | Rel-17 | pc_nrBand3_PC2_Supp | NR FR1 PC2 Band n3 | + +**Table A.4.3.1-4a: NR FR2 PC2 RF Baseline Implementation Capabilities** + +| Item | NR FR2 PC2 RF Baseline Implementation Capabilities | Ref. | Release | Mnemonic | Comments | +|------|----------------------------------------------------|-----------------|---------|----------------------------|----------------------| +| 1 | NR Frequency band: 26500-29500 MHz (UL / DL) | 38.101-2, 6.2.1 | Rel-15 | pc_nrBand257_PC2_Supp
p | NR FR2 PC2 Band n257 | +| 2 | NR Frequency band: 24250-27500 MHz (UL / DL) | 38.101-2, 6.2.1 | Rel-15 | pc_nrBand258_PC2_Supp
p | NR FR2 PC2 Band n258 | +| 3 | NR Frequency band: 27500-28350 MHz (UL / DL) | 38.101-2, 6.2.1 | Rel-15 | pc_nrBand261_PC2_Supp
p | NR FR2 PC2 Band n261 | + +**Table A.4.3.1-4b: NR FR1 PC1 RF Baseline** + +###### **Implementation Capabilities** + +| Item | NR FR1 PC1 RF Baseline
Implementation Capabilities | Ref. | Release | Mnemonic | Comments | +|------|--------------------------------------------------------------|-----------------|---------|-----------------------|-------------------------| +| 1 | NR Frequency band: 788-798 MHz (UL),
758-768 MHz (DL) | 38.101-1, 6.2.1 | Rel-16 | pc_nrBand14_PC1_Supp | NR FR1 PC1
Band n14 | +| 2 | NR Frequency band: 874.4-880 MHz
(UL), 919.4-925 MHz (DL) | 38.101-1, 6.2.1 | Rel-18 | pc_nrBand100_PC1_Supp | NR FR1 PC1
Band n100 | +| 3 | NR Frequency band: 1900-1910 MHz
(UL / DL) | 38.101-1, 6.2.1 | Rel-18 | pc_nrBand101_PC1_Supp | NR FR1 PC1
Band n101 | + +**Table A.4.3.1-4c: NR FR2 PC1 RF Baseline Implementation Capabilities** + +| Item | NR FR2 PC1 RF Baseline
Implementation Capabilities | Ref. | Release | Mnemonic | Comments | +|------|-------------------------------------------------------|-----------------|---------|-----------------------|-------------------------| +| 1 | NR Frequency band: 26500-29500 MHz
(UL / DL) | 38.101-2, 6.2.1 | Rel-15 | pc_nrBand257_PC1_Supp | NR FR2 PC1
Band n257 | +| 2 | NR Frequency band: 24250-27500 MHz
(UL / DL) | 38.101-2, 6.2.1 | Rel-15 | pc_nrBand258_PC1_Supp | NR FR2 PC1
Band n258 | +| 3 | NR Frequency band: 37000-40000 MHz
(UL / DL) | 38.101-2, 6.2.1 | Rel-15 | pc_nrBand260_PC1_Supp | NR FR2 PC1
Band n260 | +| 4 | NR Frequency band: 27500-28350 MHz
(UL / DL) | 38.101-2, 6.2.1 | Rel-15 | pc_nrBand261_PC1_Supp | NR FR2 PC1
Band n261 | + +**Table A.4.3.1-4d: NR FR2 PC4 RF Baseline Implementation Capabilities** + +| Item | NR FR2 PC4 RF Baseline
Implementation Capabilities | Ref. | Release | Mnemonic | Comments | +|------|-------------------------------------------------------|-----------------|---------|-----------------------|-------------------------| +| 1 | NR Frequency band: 26500-29500 MHz
(UL / DL) | 38.101-2, 6.2.1 | Rel-15 | pc_nrBand257_PC4_Supp | NR FR2 PC4
Band n257 | +| 2 | NR Frequency band: 24250-27500 MHz
(UL / DL) | 38.101-2, 6.2.1 | Rel-15 | pc_nrBand258_PC4_Supp | NR FR2 PC4
Band n258 | +| 3 | NR Frequency band: 37000-40000 MHz
(UL / DL) | 38.101-2, 6.2.1 | Rel-15 | pc_nrBand260_PC4_Supp | NR FR2 PC4
Band n260 | +| 4 | NR Frequency band: 27500-28350 MHz
(UL / DL) | 38.101-2, 6.2.1 | Rel-15 | pc_nrBand261_PC4_Supp | NR FR2 PC4
Band n261 | + +**Table A.4.3.1-4e: NR FR1 PC1.5 RF Baseline** + +###### **Implementation Capabilities** + +| Item | NR FR1 PC1.5 RF Baseline Implementation Capabilities | Ref. | Release | Mnemonic | Comments | +|------|------------------------------------------------------|-----------------|---------|------------------------|-----------------------| +| 1 | NR Frequency band: 3300-4200 MHz | 38.101-1, 6.2.1 | Rel-15 | pc_nrBand77_PC1.5_Supp | NR FR1 PC1.5 Band n77 | +| 2 | NR Frequency band: 3300-3800 MHz | 38.101-1, 6.2.1 | Rel-15 | pc_nrBand78_PC1.5_Supp | NR FR1 PC1.5 Band n78 | +| 3 | NR Frequency band: 4400-5000 MHz | 38.101-1, 6.2.1 | Rel-15 | pc_nrBand79_PC1.5_Supp | NR FR1 PC1.5 Band n79 | +| 4 | NR Frequency band: 2496-2690 MHz | 38.101-1, 6.2.1 | Rel-15 | pc_nrBand41_PC1.5_Supp | NR FR1 PC1.5 Band n41 | +| 5 | NR Frequency band: 2010-2025 MHz | 38.101-1, 6.2.1 | Rel-15 | pc_nrBand34_PC1.5_Supp | NR FR1 PC1.5 Band n34 | +| 6 | NR Frequency band: 2300-2400 MHz | 38.101-1, 6.2.1 | Rel-15 | pc_nrBand40_PC1.5_Supp | NR FR1 PC1.5 Band n40 | + +**Table A.4.3.1-4f: NR FR1 maxNumberSRS-Ports-PerResource RF Baseline Implementation Capabilities (Rel-15)** + +| Item | NR Band | UE Physical Layer Baseline Implementation Capabilities | Ref. | Release | Mnemonic | Parameter Type | Supported Value | Supported UE capability | +|------|---------|--------------------------------------------------------|-----------------|---------|------------------------------------------------|----------------|-----------------|-------------------------| +| 1 | n41 | NR_n41 maxNumberSRS-Ports-PerResource | 38.306, 4.2.7.7 | Rel-15 | pc_nrBand41_maxNumberSRS-Ports-PerResource_r15 | enumerated | n1, n2, n4 | | + +**Table A.4.3.1-4g: NR FR1 maxUplinkDutyCycle-PC2-FR1 RF Baseline Implementation Capabilities** + +| Item | NR Band | UE Physical Layer Baseline Implementation Capabilities | Ref. | Release | Mnemonic Parameter Name | Parameter Type | Supported Value | Supported UE capability (NOTE 1) | +|------|---------|--------------------------------------------------------|-----------------|---------|----------------------------------------|----------------|--------------------------|----------------------------------| +| 1 | n41 | NR_n41 maxUplinkDutyCycle-PC2-FR1 | 38.306, 4.2.7.2 | Rel-15 | pc_nrBand41_maxUplinkDutyCycle_PC2_FR1 | enumerated | n60, n70, n80, n90, n100 | | +| 2 | n79 | NR_n79 maxUplinkDutyCycle-PC2-FR1 | 38.306, 4.2.7.2 | Rel-15 | pc_nrBand79_maxUplinkDutyCycle_PC2_FR1 | enumerated | n60, n70, n80, n90, n100 | | + +NOTE 1: The UE supplier shall indicate the supported maxUplinkDutyCycle-PC2-FR1 as per *RF-Parameters* in TS 38.331 Section 6.3.3 UE capability information elements and choose the supported value. + +**Table A.4.3.1-4h: NR FR1 maxUplinkDutyCycle- PC1dot5-MPE-FR1-r16 RF Baseline Implementation Capabilities** + +| Item | NR Band | UE Physical Layer Baseline Implementation Capabilities | Ref. | Release | Mnemonic Parameter Name | Parameter Type | Supported Value | Supported UE capability (NOTE 1) | +|------|---------|--------------------------------------------------------|------------------------|---------|----------------------------------------------------|----------------|-------------------------------------------------------------|----------------------------------| +| 1 | n41 | NR_n41
maxUplinkDutyCycle-PC1dot5-MPE-FR1-r16 | 38.306
,
4.2.7.2 | Rel-16 | pc_nrBand41_maxUplinkDutyCycle_PC1dot5_MPE_FR1_r16 | enumerated | n10, n15, n20, n25, n30, n40, n50, n60, n70, n80, n90, n100 | | +| 2 | n79 | NR_n79
maxUplinkDutyCycle-PC1dot5-MPE-FR1-r16 | 38.306
,
4.2.7.2 | Rel-16 | pc_nrBand79_maxUplinkDutyCycle_PC1dot5_MPE_FR1_r16 | enumerated | n10, n15, n20, n25, n30, n40, n50, n60, n70, n80, n90, n100 | | + +NOTE 1: The UE supplier shall indicate the supported maxUplinkDutyCycle-PC1dot5-MPE-FR1-r16 as per RF-Parameters in TS 38.331 Section 6.3.3 UE capability information elements and choose the supported value. + +**Table A.4.3.1-4i: NR FR2 PC6 RF Baseline Implementation Capabilities** + +| Item | NR FR2 PC4 RF Baseline Implementation Capabilities | Ref. | Release | Mnemonic | Comments | +|------|----------------------------------------------------|-----------------|---------|-----------------------|----------------------| +| 1 | NR Frequency band: 26500-29500 MHz (UL / DL) | 38.101-2, 6.2.1 | Rel-17 | pc_nrBand257_PC6_Supp | NR FR2 PC6 Band n257 | +| 2 | NR Frequency band: 24250-27500 MHz (UL / DL) | 38.101-2, 6.2.1 | Rel-17 | pc_nrBand258_PC6_Supp | NR FR2 PC6 Band n258 | +| 3 | NR Frequency band: 27500-28350 MHz (UL / DL) | 38.101-2, 6.2.1 | Rel-17 | pc_nrBand261_PC6_Supp | NR FR2 PC6 Band n261 | + +**Table A.4.3.1-5: NR SUL FR1 RF Baseline** + +###### **Implementation Capabilities** + +| Item | NR SUL FR1 RF Baseline Implementation Capabilities | Ref. | Release | Mnemonic | Comments | +|----------------|----------------------------------------------------|---------------|---------|------------------|---------------------| +| 1 | NR Frequency band: 1710-1785 MHz (UL) | 38.101-1, 5.2 | Rel-15 | pc_nrBand80_Supp | NR SUL FR1 Band n80 | +| 2 | NR Frequency band: 880-915 MHz (UL) | 38.101-1, 5.2 | Rel-15 | pc_nrBand81_Supp | NR SUL FR1 Band n81 | +| 3 | NR Frequency band: 832-862 MHz (UL) | 38.101-1, 5.2 | Rel-15 | pc_nrBand82_Supp | NR SUL FR1 Band n82 | +| 4 | NR Frequency band: 703-748 MHz (UL) | 38.101-1, 5.2 | Rel-15 | pc_nrBand83_Supp | NR SUL FR1 Band n83 | +| 5 | NR Frequency band: 1920-1980 MHz (UL) | 38.101-1, 5.2 | Rel-15 | pc_nrBand84_Supp | NR SUL FR1 Band n84 | +| 6 | NR Frequency band: 1710-1780 MHz (UL) | 38.101-1, 5.2 | Rel-15 | pc_nrBand86_Supp | NR SUL FR1 Band n86 | +| 6a
to
6b | Reserved | | | | | +| 6c | Reserved | | | | | +| 7 | NR Frequency band: 2010-2025 MHz (UL) | 38.101-1, 5.2 | Rel-16 | pc_nrBand95_Supp | NR SUL FR1 Band n95 | +| 8 | NR Frequency band: 2300 MHz – 2400 MHz (UL) | 38.101-1, 5.2 | Rel-17 | pc_nrBand97_Supp | NR SUL FR1 Band n97 | +| 9 | NR Frequency band: 1626.5-1660.5 MHz (UL) | 38.101-1, 5.2 | Rel-17 | pc_nrBand99_Supp | NR SUL FR1 Band n99 | + +**Table A.4.3.1-6: NR SDL FR1 RF Baseline Implementation Capabilities** + +| Item | NR SDL FR1 RF Baseline Implementation Capabilities | Ref. | Release | Mnemonic | Comments | +|------|----------------------------------------------------|---------------|---------|------------------|---------------------| +| 0 | NR Frequency band: 717-728 MHz (DL) | 38.101-1, 5.2 | Rel-16 | pc_nrBand29_Supp | NR SDL FR1 Band n29 | +| 1 | NR Frequency band: 1432-1517 MHz (DL) | 38.101-1, 5.2 | Rel-15 | pc_nrBand75_Supp | NR SDL FR1 Band n75 | +| 2 | NR Frequency band: 1427-1432 MHz (DL) | 38.101-1, 5.2 | Rel-15 | pc_nrBand76_Supp | NR SDL FR1 Band n76 | + +**Table A.4.3.1-7: UE Power Class implementation Capabilities (for one or more of the supported UE Power Class Implemented Capabilities in Table A.4.3.1-4, Table A.4.3.1-4a, Table A.4.3.1-4b, Table A.4.3.1-4c, Table A.4.3.1-4d and Table A.4.3.1-4e)** + +| Item | UE Power Class implementation Capabilities | Ref. | Release | Mnemonic | Comments | +|------|--------------------------------------------|-----------------|---------|--------------|---------------------------------------------| +| 1 | UE Power Class 1 in FR1 | 38.101-1, 6.2.1 | Rel-16 | pc_FR1_PC1 | Applicable to the bands in Table A.4.3.1-4b | +| 1a | UE Power Class 1 in FR2 | 38.101-2, 6.2.1 | Rel-15 | pc_FR2_PC1 | Applicable to the bands in Table A.4.3.1-4c | +| 2 | UE Power Class 2 in FR1 | 38.101-1, 6.2.1 | Rel-15 | pc_FR1_PC2 | Applicable to the bands in Table A.4.3.1-4 | +| 2a | UE Power Class 2 in FR2 | 38.101-2, 6.2.1 | Rel-15 | pc_FR2_PC2 | Applicable to the bands in Table A.4.3.1-4a | +| 3 | UE Power Class 3 in FR1 | 38.101-1, 6.2.1 | Rel-15 | pc_FR1_PC3 | All applicable FR1 NR bands | +| 3a | UE Power Class 3 in FR2 | 38.101-2, 6.2.1 | Rel-15 | pc_FR2_PC3 | All applicable FR2 NR bands | +| 4 | UE Power Class 4 in FR2 | 38.101-2, 6.2.1 | Rel-15 | pc_FR2_PC4 | Applicable to the bands in Table A.4.3.1-4d | +| 5 | UE Power Class 1.5 in FR1 | 38.101-1, 6.2.1 | Rel-15 | pc_FR1_PC1.5 | Applicable to the bands in Table A.4.3.1-4e | +| 6 | UE Power Class 6 in FR2 | 38.101-2, 6.2.1 | Rel-17 | pc_FR2_PC6 | Applicable to the bands in Table A.4.3.1-4i | + +**Table A.4.3.1-7a: NR FR1 2Rx/4Rx implementation Capabilities** + +| Item | UE 2Rx/4Rx implementation Capabilities | Ref. | Release | Mnemonic | Comments | +|------|----------------------------------------|----------------|---------|----------------|------------------------------------------------------------------------------------------------------------------| +| 1 | UE 2Rx in FR1 | 38.101-1, 7.3 | Rel-15 | pc_FR1_2Rx | If the capability is supported then the Band(s) for which it is supported shall be indicated in Table A.4.3.9-4c | +| 2 | UE FDD 4Rx in FR1 | 38.101-1, 7.3 | Rel-15 | pc_FR1_FDD_4Rx | If the capability is supported then the Band(s) for which it is supported shall be indicated in Table A.4.3.9-4a | +| 3 | UE TDD 4Rx in FR1 | 38.101-1, 7.3 | Rel-15 | pc_FR1_TDD_4Rx | If the capability is supported then the Band(s) for which it is supported shall be indicated in Table A.4.3.9-4b | +| 4 | UE only supports 1Rx in FR1 | 38.101-1, 7.3I | Rel-17 | pc_FR1_1Rx | If the capability is supported then the Band(s) for which it is supported shall be indicated in Table A.4.3.9-4e | + +**Table A.4.3.1-8: Void****Table A.4.3.1-9: NR Sidelink FR1 RF Baseline Implementation Capabilities** + +| Item | NR Sidelink FR1 RF Baseline Implementation Capabilities | Ref. | Release | Mnemonic | Comments | +|------|----------------------------------------------------------------------------|----------------|---------|------------------------|--------------------------| +| 1 | NR Frequency band: 2570-2620 MHz (Transmission), 2570-2620 MHz (Reception) | 38.101-1, 5.2E | Rel-16 | pc_nrBand38_NRS L_Supp | NR Sidelink FR1 Band n38 | +| 2 | NR Frequency band: 5855-5925 MHz (Transmission), 5855-5925 MHz (Reception) | 38.101-1, 5.2E | Rel-16 | pc_nrBand47_NRS L_Supp | NR Sidelink FR1 Band n47 | + +**Table A.4.3.1-10: NR FR2 PC7 RF Baseline Implementation Capabilities** + +| Item | NR FR2 PC7 RF Baseline Implementation Capabilities | Ref. | Release | Mnemonic | Comments | +|------|----------------------------------------------------|-----------------|---------|-------------------------|----------------------| +| 1 | NR Frequency band: 26500-29500 MHz (UL / DL) | 38.101-2, 6.2.1 | Rel-17 | pc_nrBand257_PC7_Supp p | NR FR2 PC7 Band n257 | +| 2 | NR Frequency band: 24250-27500 MHz (UL / DL) | 38.101-2, 6.2.1 | Rel-17 | pc_nrBand258_PC7_Supp p | NR FR2 PC7 Band n258 | +| 3 | NR Frequency band: 27500-28350 MHz (UL / DL) | 38.101-2, 6.2.1 | Rel-17 | pc_nrBand261_PC7_Supp p | NR FR2 PC7 Band n261 | + +#### A.4.3.2 Physical Layer Baseline Implementation Capabilities + +**Table A.4.3.2-1: UE Physical Layer Baseline Implementation Capabilities** + +| Item | UE Physical Layer Baseline Implementation Capabilities | Ref. | Release | Mnemonic | M | If indicated "Yes" the feature shall be implemented and successfully tested for the corresponding release | Comments | +|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|---------|-------------------------------|-----|-----------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------| +| 1 | Support PDSCH reception based on semi-persistent scheduling | 38.306, 4.2.7.10 | Rel-15 | pc_downlinkSPS | No | | | +| 2 | Support 256QAM for PDSCH for FR1 | 38.306, 4.2.7.10 | Rel-15 | pc_pdsch_256QAM_FR1 | CY | | Mandatory for non-RedCap UEs and optional for RedCap UEs. | +| 3 | Support 256QAM for PDSCH for at least one NR FR2 band | 38.306, 4.2.7.2 | Rel-15 | pc_pdsch_256QAM_FR2 | No | | | +| 4 | Support 256QAM for PUSCH for at least one NR FR1 band | 38.306, 4.2.7.2 | Rel-15 | pc_pusch_256QAM_FR1 | No | | | +| 4a | Support 256QAM for PUSCH for at least one NR FR2 band | 38.306, 4.2.7.2 | Rel-15 | pc_pusch_256QAM_FR2 | No | | | +| 5 | Support receiving PDSCH using PDSCH mapping type A with less than seven symbols | 38.306, 4.2.7.10 | Rel-15 | pc_pdsch_MappingTypeA | Yes | Yes | | +| 6 | Support receiving PDSCH using PDSCH mapping type B | 38.306, 4.2.7.10 | Rel-15 | pc_pdsch_MappingTypeB | Yes | | | +| 7 | Support resource allocation Type 0 for PUSCH | 38.306, 4.2.7.10 | Rel-15 | pc_ra_Type0_PUSCH | No | | | +| 8 | Support scaling factor 0.75 is applied to the band in the max data rate calculation | 38.306, 4.2.7 | Rel-15 | pc_scalingFactor0dot75 | | | | +| 9 | Support reconfiguration with sync using a contention free random access on PRACH resources that are associated with CSI-RS resources of the target cell | 38.306, 4.2.7.10 | Rel-15 | pc_csi_RS_CFRA_ForHO | No | | | +| 10 | Support Type 1 PUSCH transmissions with configured grant | 38.306, 4.2.7.10 | Rel-15 | pc_configuredUL_GrantType 1 | No | | | +| 11 | Support Type 2 PUSCH transmissions with configured grant | 38.306, 4.2.7.10 | Rel-15 | pc_configuredUL_GrantType 2 | No | | | +| 12 | Support PDSCH Reception when configured with higher layer parameter aggregationFactorDL > 1 | 38.306, 4.2.7.10 | Rel-15 | pc_pdsch_RepetitionMultiSlots | No | | | +| 13 | Supports supplemental uplink with dynamic switch (DCI based selection of PUSCH carrier) | 38.306, 4.2.7.7 | Rel-15 | pc_dynamicSwitch SUL | No | | | +| 14 | Supports MIMO layers at the UE for PUSCH transmission with codebook precoding. UE indicating support of this feature shall also indicate support of PUSCH codebook coherency subset | 38.306, 4.2.7.8 | Rel-15 | pc_nrMIMO_CB_PUSCH | No | | Set to true if maxNumberMIMO-LayersCB-PUSCH has value different from "oneLayer" | +| 15 | Void | | | | | | | + +| | | | | | | | | +|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|--------|---------------------------------------------|-----|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 16 | Support receiving PDSCH with interleaved VRB-to-PRB mapping | 38.306, 4.2.7.10 | Rel-15 | pc_interleavingVRB_ToPRB_PDSCH | Yes | | | +| 17 | Support dynamic EN-DC power sharing for at least one EN-DC band combination_FR1 only | 38.306, 4.2.7.9 | Rel-15 | pc_dynamicPowerSharingENDC | Yes | | If the UE supports this capability it will dynamically share the power between NR and LTE if P_LTE + P_NR > Pcmax. | +| 18 | Supports up to 10 search spaces in a SCell per BWP | 38.306, 4.2.7.10 | Rel-15 | pc_maxNumberSearchSpaces | No | | | +| 19 | Supports spatial bundling of HARQ-ACK bits carried on PUCCH or PUSCH per PUCCH group. With spatial bundling, two HARQ-ACK bits for a DL MIMO data is bundled into a single bit by logical "AND" operation | 38.306, 4.2.7.10 | Rel-15 | pc_spatialBundlingHARQ_ACK | Yes | | | +| 20 | Support alternative additional DMRS position for co-existence with LTE CRS | 38.306, 4.2.7.5 | Rel-15 | pc_additionalDMRS_DL_Alt | No | | | +| 21 | Supports transmitting PUSCH scheduled by DCI format 0_0 or 0_1 when configured with higher layer parameter aggregationFactorUL > 1 | 38.306, 4.2.7.10 | Rel-15 | pc_pusch_RepetitionMultiSlots | Yes | | | +| 22 | Support beam correspondence without UL beam sweeping | 38.306, 4.2.7.2 | Rel-15 | pc_beamCorrespondenceWithoutUL_BeamSweeping | Yes | | A UE that can fulfil the requirements without UL beam sweeping then set the bit to 1. A UE that can fulfil the requirements with UL beam sweeping then set the bit to 0. | +| 22A | Support beam correspondence based on SSB | 38.306, 4.2.7.2 | Rel-16 | pc_beamCorrespondence_SSBbased | No | | | +| 22B | Support beam correspondence based on CSI-RS | 38.306, 4.2.7.2 | Rel-16 | pc_beamCorrespondence_CSI_RSbased | No | | | + +| | | | | | | | | +|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|--------|------------------------------------------|----|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 23 | The maximum number of spatial multiplexing layer(s) supported by the UE for DL reception is 8 Layers. For single CC standalone NR, it is mandatory with capability signalling to support at least 4 MIMO layers in the bands where 4Rx is specified as mandatory for the given UE and at least 2 MIMO layers in FR2. If absent, the UE doesn't support MIMO on this carrier | 38.306, 4.2.7.6 | Rel-15 | pc_maxNumberMIMO_LayersPDsch_eightLayers | CY | | Set to false if Table A.4.3.2-1/23A or 23B set to true. | +| 23A | The maximum number of spatial multiplexing layer(s) supported by the UE for DL reception is 4 Layers. | 38.306, 4.2.7.6 | Rel-15 | pc_maxNumberMIMO_LayersPDsch_fourLayers | CY | | Set to false if Table A.4.3.2-1/23 or 23B set to true. | +| 23B | The maximum number of spatial multiplexing layer(s) supported by the UE for DL reception is 2 Layers. | 38.306, 4.2.7.6 | Rel-15 | pc_maxNumberMIMO_LayersPDsch_twoLayers | CY | | Set to false if Table A.4.3.2-1/23 or 23A set to true. | +| 24 | Supports DCI and timer based active BWP switching delay type1 | 38.306, 4.2.7.10 | Rel-15 | pc_bwp_SwitchingDelay_Type1 | No | | It is mandatory to report one among BWP switching delay type1 or type 2 as supported | +| 24A | Supports DCI and timer based active BWP switching delay type2 | 38.306, 4.2.7.10 | Rel-15 | pc_bwp_SwitchingDelay_Type2 | No | | It is mandatory to report one among BWP switching delay type1 or type 2 as supported | +| 24B | Supports incremental delay for DCI and timer based active BWP switching type 1 on multiple CCs simultaneously | 38.306, 4.2.7.10 | Rel-16 | pc_bwp_SwitchingMultiCCs_type1_r16 | No | | It is mandatory to report one among incremental delay for DCI and timer based active BWP switching type 1 or type 2 on multiple CCs simultaneously as supported | + +| | | | | | | | | +|-----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|--------|---------------------------------------|-----|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 24C | Supports incremental delay for DCI and timer based active BWP switching type 2 on multiple CCs simultaneously | 38.306, 4.2.7.10 | Rel-16 | pc_bwp_SwitchingMultiCCs_type2_r16 | No | | It is mandatory to report one among incremental delay for DCI and timer based active BWP switching type 1 or type 2 on multiple CCs simultaneously as supported | +| 25A | Support modified MPR behaviour bit 0 | 38.306, 4.2.7.2 | Rel-15 | pc_modifiedMPR_behaviour_bit0 | No | | Applicable to FR2 bands n257, n258, n260 and n261 | +| 25 | Support modified MPR behaviour | 38.306, 4.2.7.2 | Rel-15 | pc_modifiedMPR_behaviour | No | | | +| 26 | Support dynamic switching between resource allocation Types 0 and 1 for PDSCH | 38.306, 4.2.7.10 | Rel-15 | pc_dynamicSwitchRA_Type0_1_PDSCH | No | | | +| 27 | Support dynamic switching between resource allocation Types 0 and 1 for PUSCH | 38.306, 4.2.7.10 | Rel-15 | pc_dynamicSwitchRA_Type0_1_PUSCH | No | | | +| 28 | Support almost contiguous UL CP-OFDM transmissions in FR1 | 38.306, 4.2.7.10 | Rel-15 | pc_almostContiguousCP_OFDM_UL_FR1 | No | | | +| 29 | Support almost contiguous UL CP-OFDM transmissions in FR2 | 38.306, 4.2.7.10 | Rel-15 | pc_almostContiguousCP_OFDM_UL_FR2 | No | | | +| 30 | Support dynamic indication of applicable minimum scheduling restriction by DCI format 0_1 and 1_1, and the minimum scheduling offset for PDSCH and aperiodic CSI-RS triggering offset (K0), and PUSCH (K2), and the extended value range for aperiodic CSI-RS triggering offset | 38.306, 4.2.7.10 | Rel-16 | pc_crossSlotScheduling | No | | | +| 31 | Supports pi/2-BPSK modulation scheme for PUSCH in FR1 | 38.306, 4.2.7.10 | Rel-15 | pc_pusch_halfpiBPSK_FR1 | Yes | | | +| 31a | Supports pi/2-BPSK modulation scheme for PUSCH in FR2 | 38.306, 4.2.7.10 | Rel-15 | pc_pusch_halfpiBPSK_FR2 | Yes | | | +| 32 | Support multi-DCI based multi-TRP and support of fully/partially overlapping PDSCHs in time and non-overlapping in frequency | 38.306, 4.2.7.6 | Rel-16 | pc_multiDCI_MultiTRP_r16 | No | | | +| 33 | Support receiving PDSCH with resource mapping that excludes the REs determined by the higher layer configuration LTE-carrier configuring common RS | 38.306, 4.2.7.2 | Rel-15 | pc_rateMatchingLTE_CRS | Yes | | | +| 34 | Support of BWP operation without bandwidth restriction | 38.306, 4.2.7.2 | Rel-15 | pc_bwp_WithoutRestriction | No | | | +| 35 | Support of receiving SCell dormancy indication on SCell using DCI format 2_6 outside the active time | 38.306, 4.2.7.4 | Rel-16 | pc_scellDormancyOutsideActiveTime_r16 | No | | | + +| | | | | | | | | +|-----|----------------------------------------------------------------------------------------------------------|------------------|--------|-------------------------------------|----|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 36 | Supports pi/2-BPSK modulation scheme for power boosting in FR1 | 38.306, 4.2.7.2 | Rel-15 | pc_powerBoosting_pi2BPSK | No | | | +| 37 | Support of dynamic 1Tx-2Tx UL Tx switching | 38.306, 4.2.7.1 | Rel-16 | pc_ULTxSwitchingBandPair | No | | If the capability is supported then the band pair(s) for which it is supported shall be indicated in Table A.4.3.2A.4.1-3, Table A.4.3.2B.2.3.1-2 and Table A.4.3.2C.2-1 | +| 38 | Support uplink transmission power boost by suspension of in-band emission (IBE) in FR2 | 38.306, 4.2.7.2 | Rel-16 | pc_mpr_PowerBoost_FR2 | No | | | +| 39 | Supports the alternative 64QAM MCS table for PDSCH | 38.306, 4.2.7.10 | Rel-16 | pc_dl_64qam_mcs_tableAlt | No | | | +| 40 | Supports the CQI table with target BLER of 10 -5 | 38.306, 4.2.7.10 | Rel-16 | pc_cqi_tableAlt | No | | | +| 41 | Supports of single DCI based spatial division multiplexing scheme | 38.306, 4.2.7.5 | Rel-16 | pc_singledci_sdm | No | | | +| 42 | Support of BWP adaptation (up to 2 BWPs) with the same numerology for FR1 FDD bands | 38.306, 4.2.7.2 | Rel-15 | pc_bwp_SameNumerology_upto2_FR1_FDD | No | | FR1 FDD bands | +| 42a | Support of BWP adaptation (up to 2 BWPs) with the same numerology for FR1 TDD bands | 38.306, 4.2.7.2 | Rel-15 | pc_bwp_SameNumerology_upto2_FR1_TDD | No | | FR1 TDD bands | +| 42b | Support of BWP adaptation (up to 2 BWPs) with the same numerology for FR2 bands | 38.306, 4.2.7.2 | Rel-15 | pc_bwp_SameNumerology_upto2_FR2 | No | | FR2 bands | +| 43 | Support of BWP adaptation (up to 4 BWPs) with the same numerology for FR1 FDD bands | 38.306, 4.2.7.2 | Rel-15 | pc_bwp_SameNumerology_upto4_FR1_FDD | No | | FR1 FDD bands | +| 43a | Support of BWP adaptation (up to 4 BWPs) with the same numerology for FR1 TDD bands | 38.306, 4.2.7.2 | Rel-15 | pc_bwp_SameNumerology_upto4_FR1_TDD | No | | FR1 TDD bands | +| 43b | Support of BWP adaptation (up to 4 BWPs) with the same numerology for FR2 bands | 38.306, 4.2.7.2 | Rel-15 | pc_bwp_SameNumerology_upto4_FR2 | No | | FR2 bands | +| 44 | Support BWP adaptation up to 4 BWPs with the different numerologies, via DCI and timer for FR1 FDD bands | 38.306, 4.2.7.2 | Rel-15 | pc_bwp_DiffNumerology_FR1_FDD | No | | FR1 FDD bands | +| 44a | Support BWP adaptation up to 4 BWPs with the different numerologies, via DCI and timer for FR1 TDD bands | 38.306, 4.2.7.2 | Rel-15 | pc_bwp_DiffNumerology_FR1_TDD | No | | FR1 TDD bands | +| 44b | Support BWP adaptation up to 4 BWPs with the different numerologies, via DCI and timer for FR2 bands | 38.306, 4.2.7.2 | Rel-15 | pc_bwp_DiffNumerology_FR2 | No | | FR2 bands | + +| | | | | | | | | +|----|-----------------------------------------------------------------------------------------------------------|------------------|--------|---------------------------------|-----|--|------------------------| +| 45 | Support PUSCH repetition type B | 38.306, 4.2.7.7 | Rel-16 | pc_pusch_RepetitionTypeB_r16 | No | | | +| 46 | Support of 2-Step RACH | 38.306, 4.2.7.10 | Rel-16 | pc_twoStepRACH_r16 | No | | | +| 47 | Void | | | | | | | +| 48 | Void | | | | | | | +| 49 | Void | | | | | | | +| 50 | Void | | | | | | | +| 51 | Void | | | | | | | +| 52 | Support monitoring DCI format 1_2 for DL scheduling and monitoring DCI format 0_2 for UL scheduling | 38.306, 4.2.7.10 | Rel-16 | pc_dci_Format1_2And0_2_r16 | No | | | +| 53 | Support of multi-DCI based multi-TRP | 38.306, 4.2.7.6 | Rel-16 | pc_multi_dci_multi_trp | No | | | +| 54 | Support of single DCI based FDMSchemeA | 38.306, 4.2.7.2 | Rel-16 | pc_single_dci_fdmschemeA | No | | | +| 55 | Support of single-DCI based inter-slot TDM | 38.306, 4.2.7.2 | Rel-16 | pc_single_dci_interslot_tdm | No | | | +| 56 | Support of maximum number of TRS resource sets per CC which the UE can track simultaneously is at least 2 | 38.306, 4.2.7.2 | Rel-16 | pc_simultaneous_TRS | No | | | +| 57 | Support of low PAPR DMRS | 38.306, 4.2.7.2 | Rel-16 | pc_lowPAPR_DMRS_pusch_precoding | No | | | +| 58 | Support of UL full power transmission mode of full power | 38.306, 4.2.7.7 | Rel-16 | pc_ul_FullPwrMode_r16 | No | | | +| 59 | Support of UL full power transmission mode of fullpowerMode1 | 38.306, 4.2.7.7 | Rel-16 | pc_ul_FullPwrMode1_r16 | No | | | +| 60 | Support of UL full power transmission mode of fullpowerMode2 | 38.306, 4.2.7.7 | Rel-16 | pc_ul_FullPwrMode2_r16 | No | | | +| 61 | Support of PDSCH processing capability 2 | 38.306, 4.2.7.5 | Rel-16 | pc_pdsch_processing_cap2 | No | | | +| 62 | Support Pre-Emption Indication | 38.306, 4.2.7.10 | Rel-15 | pc_preEmptIndication_DL | No | | | +| 63 | Support of SSB based BFD | 38.306, 4.2.7.2 | Rel-15 | pc_maxNumberSSB_BFD | CY | | | +| 64 | Support of CSI-RS based BFD | 38.306, 4.2.7.2 | Rel-15 | pc_maxNumberCSI_RS_BFD | CY | | | +| 65 | Support of SSB and/or CSI-RS based Link Recovery | 38.306, 4.2.7.2 | Rel-15 | pc_maxNumberCSI_RS_SSB_CBD | CY | | | +| 66 | Support of type II codebook | 38.306, 4.2.7.2 | Rel-15 | pc_typeIIcodebook | No | | | +| 67 | Support of Enhanced Type II codebook with at least 16 ports per CSI-RS resource | 38.306, 4.2.7.2 | Rel-16 | pc_enhanced_typeII_codebook | No | | | +| 68 | Support of TDD NR UL transmission with a 7.5 kHz shift to the LTE raster | 38.101-1, 5.4.2 | Rel-15 | pc_frequencyShift7p5khz_TDD | No | | Mandatory since Rel-16 | +| 69 | Support of FDD NR UL transmission with a 7.5 kHz shift to the LTE raster | 38.101-1, 5.4.2 | Rel-15 | pc_frequencyShift7p5khz_FDD | Yes | | | +| 70 | Void | | | | | | | +| 71 | Support of density of CSI-RS for Channel Measurement Report | 38.306, 4.2.7.2 | Rel-16 | pc_supportedCSI_RS_Density_CMR | No | | | + +| | | | | | | | | +|----|---------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|--------|----------------------------------------|----|--|---------------------------------------------------------------------------------------------------------------| +| 72 | Support of SSB/CSI-RS for L1-SINR measurement | 38.306, 4.2.7.2 | Rel-16 | pc_ssb_csirs_SINR_measurement | No | | | +| 73 | Support of SSB as CMR with dedicated CSI-IM for L1-SINR measurement | 38.306, 4.2.7.2 | Rel-16 | pc_supportedSINR_meas_ssbWithCSI_IM | No | | | +| 74 | Support of SSB as CMR with dedicated NZP IMR for L1-SINR measurement | 38.306, 4.2.7.2 | Rel-16 | pc_supportedSINR_meas_ssbWithNZP_IMR | No | | | +| 75 | Support of CSI-RS as CMR with dedicated NZP IMR configured for L1-SINR measurement | 38.306, 4.2.7.2 | Rel-16 | pc_supportedSINR_meas_csirsWithNZP_IMR | No | | | +| 76 | Support of CSI-RS as CMR without dedicated IMR configured for L1-SINR measurement | 38.306, 4.2.7.2 | Rel-16 | pc_supportedSINR_meas_csi_RSWithoutIMR | No | | | +| 77 | Support of SCell beam failure recovery | 38.306, 4.2.7.2 | Rel-16 | Pc_scellBFR | No | | | +| 78 | Support of the maximum number of activated TCI states per BWP per CC is other than n1, including control and data | 38.306, 4.2.7.2 | Rel-15 | pc_maxNumberActiveTCI_PerBWP | No | | | +| 79 | Support enhanced UL performance for the transient period | 38.306, 4.2.7.2 | Rel-16 | pc_enhancedUL_TransientPeriod_r16 | No | | | +| 80 | Supports the priority indicator field configured in DCI formats 1_1 and 1_2 in a BWP when configured to monitor both DCI formats 1_1 and 1_2 in the BWP | 38.306, 4.2.7.10 | Rel-16 | pc_dci_DL_PriorityIndicator_r16 | No | | | +| 81 | Supports the priority indicator field configured in DCI formats 0_1 and 0_2 in a BWP when configured to monitor both DCI formats 0_1 and 0_2 in the BWP | 38.306, 4.2.7.10 | Rel-16 | pc_dci_UL_PriorityIndicator_r16 | No | | A UE supporting this feature shall also support ul-IntraUE-Mux-r16 and dci-Format1-2And0-2-r16 | +| 82 | Supports restricting data transmission from a given LCH to a configured (sub-) set of dynamic grant priority levels | 38.306, 4.2.6 | Rel-16 | pc_lch_ToGrantPriorityRestriction_r16 | No | | | +| 83 | Supports two PUCCH group in CA with a same numerology across CCs for data and control channel. | 38.306 4.2.7.7 | Rel15 | pc_twoPUCCH_group | No | | | +| 84 | Support of transparent Tx diversity requirements for at least one NR FR1 band | 38.306, 4.2.7.2
38.331, Annex C | Rel-15 | pc_txDiversity_r16 | No | | FR1 only

This capability has been introduced in Rel-16 and is early implementable from Rel-15 onwards. | + +| | | | | | | | | +|----|------------------------------------------------------------------------------------------------------------------------------|------------------|--------|---------------------------------------------------------------------|-----|--|-------------------------------------------------------------------------------------------------------------------------------| +| 85 | Support of repetition of PUSCH transmission scheduled by RAR UL grant and DCI format 0_0 with CRC scrambled by TC-RNTI | 38.306, 4.2.7.2 | Rel-17 | pc_pusch_RepetitionMsg3_r17 | No | | | +| 86 | Support of DL scheduling slot offset (K0) greater than 0 for PDSCH mapping type A. | 38.306, 4.2.7.10 | Rel-15 | pc_dl_SchedulingOffset_PDSCH_TypeA | Yes | | | +| 87 | Support of CQI reporting with 4 bits per subband for NTN and shared spectrum channel access | 38.306, 4.2.7.2 | Rel-17 | pc_cqi_4_BitsSubbandNTN_SharedSpectrumChAccess_r17 | No | | UE supports CQI reporting with 4 bits per subband for NTN and shared spectrum channel access | +| 88 | Support of propagation delay compensation based on legacy TA procedure for NTN and shared spectrum channel access | 38.306, 4.2.7.2 | Rel-17 | pc_ta_BasedPDC_NTN_SharedSpectrumChAccess_r17 | No | | UE supports propagation delay compensation based on legacy TA procedure for NTN and shared spectrum channel access | +| 89 | Support of 8 dynamic slot-level repetitions for group-common PDSCH for multicast for NTN and shared spectrum channel access | 38.306, 4.2.7.2 | Rel-17 | pc_dynamicSlotRepetitionMulticastNTN_SharedSpectrumChAccess_r17_n8 | No | | UE supports 8 dynamic slot-level repetitions for group-common PDSCH for multicast for NTN and shared spectrum channel access | +| 90 | Support of 16 dynamic slot-level repetitions for group-common PDSCH for multicast for NTN and shared spectrum channel access | 38.306, 4.2.7.2 | Rel-17 | pc_dynamicSlotRepetitionMulticastNTN_SharedSpectrumChAccess_r17_n16 | No | | UE supports 16 dynamic slot-level repetitions for group-common PDSCH for multicast for NTN and shared spectrum channel access | +| 91 | Support of NTN features in GSO scenario | 38.306, 4.2.2 | Rel-17 | pc_ntn_ScenarioSupport_r17_GSO | No | | UE supports NTN features in GSO scenario | + +| | | | | | | | | +|-----|---------------------------------------------------------------------------------------------|------------------|--------|---------------------------------------|----|--|-------------------------------------------------------------------------------------------------------------------| +| 92 | Support of NTN features in NGSO scenario | 38.306, 4.2.2 | Rel-17 | pc_ntn_ScenarioSupport_r17_NGSO | No | | UE supports NTN features in NGSO scenario | +| 93 | Support of RSSI measurements and channel occupancy reporting | 38.306, 4.2.7.2a | Rel-16 | pc_rssi_ChannelOccupancyReporting_r16 | No | | | +| 94 | Supports the restriction to 3450 - 3550 MHz and 3700 - 3980 MHz ranges of band n77 | 38.306, 4.2.7.11 | Rel-16 | pc_extendedBand_n77_r16 | No | | Applicable for UE support band n77 and in the USA this band is restricted to 3450 – 3550 MHz and 3700 – 3980 MHz. | +| 95 | Supports the restriction to 3450 - 3650 MHz and 3650 - 3980 MHz ranges of band n77 | 38.306, 4.2.7.11 | Rel-17 | pc_extendedBand_n77_2_r17 | No | | Applicable for UE support band n77 and in Canada this band is restricted to 3450 – 3650 MHz and 3650 – 3980 MHz. | +| 96 | Void | | | | | | | +| 97 | Void | | | | | | | +| 98 | Void | | | | | | | +| 99 | Void | | | | | | | +| 100 | Void | | | | | | | +| 101 | Void | | | | | | | +| 102 | Void | | | | | | | +| 103 | Void | | | | | | | +| 104 | Support of 1024QAM modulation scheme for PDSCH with maximum 2 MIMO layers for FR1 FDD bands | 38.306, 4.2.7.2 | Rel-17 | pc_pdsch_1024QAM_2MIMO_FR1_r17_FDD | No | | FR1 FDD bands | +| 105 | Support of 1024QAM modulation scheme for PDSCH with maximum 2 MIMO layers for FR1 TDD bands | 38.306, 4.2.7.2 | Rel-17 | pc_pdsch_1024QAM_2MIMO_FR1_r17_TDD | No | | FR1 TDD bands | +| 106 | Support of 1024QAM modulation scheme for PDSCH for FR1_FDD bands | 38.306, 4.2.7.2 | Rel-17 | pc_pdsch_1024QAM_FR1_r17_FDD | No | | FR1 FDD bands | +| 107 | Support of 1024QAM modulation scheme for PDSCH for FR1_TDD bands | 38.306, 4.2.7.2 | Rel-17 | pc_pdsch_1024QAM_FR1_r17_TDD | No | | FR1 TDD bands | + +| | | | | | | | | +|-----|-------------------------------------------------------------------------------------------------------------------------------------|------------------|--------|------------------------------------------------------|----|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 108 | Support RTT-based propagation delay compensation for time synchronization of the Uu interface based on CSI-RS for tracking and SRS. | 38.306, 4.2.7.5 | Rel-17 | pc_rtt_BasedPDC_CSI_RS_ForTracking_r17 | No | | A UE supporting this feature shall also indicate support of csi-RS-ForTracking and supportedSRS-Resources as specified in TS 38.331. | +| 109 | Support RTT-based Propagation delay compensation for time synchronization of the Uu interface based on DL PRS and SRS. | 38.306, 4.2.7.5 | Rel-17 | pc_rtt_BasedPDC_PRS_r17 | No | | If UE provides parameter maxNumberPRS-Resource-r17 and optionally parameter maxNumberPRS-ResourceProcessedPerSlot-r17 as described in TS 38.331, consider this as supported, otherwise not supported.

A UE supporting this feature shall also indicate support of supportedSRS-Resources as specified in TS 38.331. | +| 110 | Support propagation delay compensation based on legacy TA procedure for TN and non-shared spectrum channel access. | 38.306, 4.2.7.10 | Rel-17 | pc_ta_BasedPDC_TN_NSS_ChAccess_r17 | No | | | +| 111 | Support Type 1 PUSCH transmissions with configured grant | 38.306 4.2.7.10 | Rel-15 | pc_type1_PUSCH_RepetitionMultiSlots | No | | | +| 112 | Support Type 2 PUSCH transmissions with configured grant | 38.306 4.2.7.10 | Rel-15 | pc_type2_PUSCH_RepetitionMultiSlots | No | | | +| 113 | Support the dynamic indication of the number of repetitions for PUSCH transmission | 38.306 4.2.7.10 | Rel-16 | pc_pusch_RepetitionTypeA_r16 | No | | | +| 114 | Support repetitions for PUCCH format 0, 1, 2, 3 and 4 over multiple PUCCH subslots based on dynamic repetition indication | 38.306 4.2.7.7 | Rel-17 | pc_pucch_Repetition_F0_1_2_3_4_DynamicIndication_r17 | No | | | + +| | | | | | | | | +|-----|----------------------------------------------------------------------------------------------------------------------------------------|---------------------|--------|----------------------------------------|----|--|---------------------------------------------------------------------------------------------------------------------------| +| 115 | Support the increased maximum number of PUSCH Type A repetitions up to 32 | 38.306
4.2.7.2 | Rel-17 | pc_maxNumberPUSCH_TypeA_Repetition_r17 | No | | | +| 116 | Support PUSCH repetitions based on available slots | 38.306
4.2.7.2 | Rel-17 | pc_puschTypeA_RepetitionsAvailSlot_r17 | No | | | +| 117 | Supports TB processing over multi-slot PUSCH without repetition | 38.306
4.2.7.2 | Rel-17 | pc_tb_ProcessingMultiSlotPUSCH_r17 | No | | | +| 118 | Supports repetition of TB processing over multi-slot PUSCH | 38.306
4.2.7.2 | Rel-17 | pc_tb_ProcessingRepMultiSlotPUSCH_r17 | No | | | +| 119 | Support SFN scheme A for PDCCH scheduling SFN Scheme A PDSCH | 38.306,
4.2.7.5 | Rel-17 | pc_sfn_schemeA_r17 | No | | | +| 120 | Support SFN scheme B for PDCCH scheduling SFN Scheme B PDSCH | 38.306,
4.2.7.5 | Rel-17 | pc_sfn_schemeB_r17 | No | | | +| 121 | Support of up to 8 configured SPS configurations in a BWP of a serving cell and up to 32 configured SPS configurations in a cell group | 38.306,
4.2.7.2 | Rel-16 | pc_multi_sps_r16 | No | | The UE can include this feature only if the UE indicates support of downlinkSPS. | +| 122 | Support transmission of two PUCCH formats in TDM in the same slot | 38.306,
4.2.7.10 | Rel-15 | pc_twoPUCCH_AnyOthersInSlot | No | | | +| 123 | Support of unified TCI state operation with joint DL/UL TCI update for intra-cell beam management | 38.306,
4.2.7.2 | Rel-17 | pc_unifiedJointTCI_r17 | No | | | +| 124 | Support of unified TCI state operation with separate DL/UL TCI update for intra-cell beam management | 38.306,
4.2.7.2 | Rel-17 | pc_unifiedSeparateTCI_r17 | No | | | +| 125 | Support of RRC configuration of additional PCI different from serving cell associated with the TCI state and/or QCL-info | 38.306,
4.2.7.2 | Rel-17 | pc_mTRP_InterCell_r17 | No | | | +| 126 | Support of unified TCI with separate DL/UL TCI update for inter-cell beam management | 38.306,
4.2.7.2 | Rel-17 | pc_unifiedSeparateTCI_InterCell_r17 | No | | | +| 127 | Support of dynamic 2Tx-2Tx UL Tx switching | 38.306,
4.2.7.1 | Rel-17 | pc_2Tx_ULTxSwitchingBandPair_r17 | No | | If the capability is supported then the band pair(s) for which it is supported shall be indicated in Table A.4.3.2A.4.1-3 | + +| | | | | | | | | +|-----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|--------|--------------------------------------------|----|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 128 | Indicates whether the UE supports aperiodic CSI-RS for tracking for fast SCell activation, i.e.,
1) Aperiodic CSI-RS for tracking for fast SCell activation is triggered by enhanced SCell activation/deactivation MAC CE;
2) Aperiodic CSI-RS for tracking for fast SCell activation is triggered within the BWP indicated by firstActiveDownlinkBWP-Id for the SCell. | 38.306, 4.2.7.2 | Rel-17 | pc_aperiodicCSIIRS_FastScellActivation_r17 | No | | Includes maxNumberAperiodicCSI-RS-PerCC-r17 and maxNumberAperiodicCSI-RS-AcrossCCs-r17 to indicate the number of RS configurations for fast SCell activation that can be indicated by the MAC CE | +| 129 | Indicates whether the UE supports conditional PSCell addition in EN-DC. The UE supporting this feature shall also support 2 trigger events for same execution condition in conditional PSCell addition in EN-DC. | 38.306, 4.2.7.9 | Rel-17 | pc_condPSCellAdditionENDC_r17 | No | | | +| 130 | Support of conditional PSCell addition in NR-DC | 38.306, 4.2.7.12 | Rel-17 | pc_condPSCellAdditionNRDC_r17 | No | | | +| 131 | Support of activation (with or without RACH) and deactivation on SCG in EN-DC | 38.306, 4.2.7.9 | Rel-17 | pc_scg_ActivationDeactivationENDC_r17 | No | | | +| 132 | Support of activation (with or without RACH) and deactivation on SCG in NR-DC | 38.306, 4.2.7.12 | Rel-17 | pc_scg_ActivationDeactivationNRDC_r17 | No | | | +| 133 | Support of TCI state update and activation by a) MAC-CE+DCI-based TCI state indication (use of DCI formats 1_1/1_2 with DL assignment)
And b) MAC-CE+DCI-based TCI state indication (use of DCI formats 1_1/1_2 without DL assignment) | 38.306, 4.2.7.2 | Rel-17 | pc_unifiedSeparateTCI_multiMAC_CE_r17 | No | | A UE supporting this feature shall also support unifiedSeparateTCI-r17. | +| 134 | Indicates whether UE supports partial frequency sounding for SRS with frequency hopping. | 38.306, 4.2.7.2 | Rel-17 | pc_srs_partialFrequencySounding_r17 | No | | | +| 135 | Indicates whether the UE supports partial frequency sounding for SRS with frequency hopping and start RB location hopping. | 38.306, 4.2.7.2 | Rel-17 | pc_srs_startRB_locationHoppingPartial_r17 | No | | A UE supporting this feature shall also indicate support of pc_srs_partialFrequencySounding_r17 as specified in TS 38.306. | +| 136 | Indicates whether the UE supports PDCCH search space monitoring occasions in any symbol of the slot (pdcch-MonitoringAnyOccasions) | 38.306, 4.2.7.5 | Rel-15 | pc_pdcchMonitoringAnyOccasions | No | | | + +| | | | | | | | | +|-----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|--------|----------------------------------------|----|--|--| +| 137 | Indicates whether the UE supports PDCCH search space monitoring occasions in any symbol of the slot with minimum time separation between two consecutive transmissions of PDCCH with span (pdcch-MonitoringAnyOccasionsWithSpanGap) | 38.306,
4.2.7.5 | Rel-15 | pc_pdcchMonitoringAnyOccasions_SpanGap | No | | | +|-----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|--------|----------------------------------------|----|--|--| + +**Table A.4.3.2-2: UE Physical Layer Baseline      Implementation Capabilities for Shared Spectrum** + +| Item | UE Physical Layer Baseline Implementation Capabilities | Ref. | Release | Mnemonic | M | If indicated "Yes" the feature shall be implemented and successfully tested for the corresponding release | Comments | +|------|-----------------------------------------------------------------------|------------------|---------|---------------------------------------------|----|-----------------------------------------------------------------------------------------------------------|------------------------------------------------------| +| 1 | Support of NR CA with NR shared spectrum channel access | 38.306, 4.2.7.2a | Rel-16 | pc_NRCASharedAccess | No | | Deployment scenario A in Annex B.3 of TS 38.300 [21] | +| 2 | Support of EN-DC with NR shared spectrum channel access | 38.306, 4.2.7.2a | Rel-16 | pc_ENDCNRSharedAccess | No | | Deployment scenario B in Annex B.3 of TS 38.300 [21] | +| 3 | Support of NR standalone shared spectrum channel access | 38.306, 4.2.7.2a | Rel-16 | pc_standaloneNRSharedAccess | No | | Deployment scenario C in Annex B.3 of TS 38.300 [21] | +| 4 | Support of NR shared spectrum channel access with UL in licensed band | 38.306, 4.2.7.2a | Rel-16 | pc_NRSharedAccessULic | No | | Deployment scenario D in Annex B.3 of TS 38.300 [21] | +| 5 | Support of NR-DC with NR shared spectrum channel access | 38.306, 4.2.7.2a | Rel-16 | pc_NRDCSharedAccess | No | | Deployment scenario E in Annex B.3 of TS 38.300 [21] | +| 6 | Support of MIB acquisition on shared spectrum PSCell | 38.306, 4.2.7.2a | Rel-16 | pc_mib_Acquisition_r16 | No | | | +| 7 | Support of SIB1 acquisition for shared spectrum PCell | 38.306, 4.2.7.2a | Rel-16 | pc_sib1_Acquisition_r16 | No | | | +| 8 | Support of UL on dynamic channel access | 38.306, 4.2.7.2a | Rel-16 | pc_ul_DynamicChAccess_r16 | No | | | +| 9 | Support of UL on semi-static channel access | 38.306, 4.2.7.2a | Rel-16 | pc_ul_Semi_StaticChAccess_r16 | No | | | +| 10 | Support of SSB-based RRM for dynamic channel access | 38.306, 4.2.7.2a | Rel-16 | pc_ssb_RRM_DynamicChAccess_r16 | No | | | +| 11 | Support of SSB-based RRM for semi-static channel access | 38.306, 4.2.7.2a | Rel-16 | pc_ssb_RRM_Semi_StaticChAccess_r16 | No | | | +| 12 | Support of SSB-based RLM on dynamic channel access | 38.306, 4.2.7.2a | Rel-16 | pc_ssb_RLM_DynamicChAccess_r16 | No | | | +| 13 | Support of SSB-based RLM on semi-static channel access | 38.306, 4.2.7.2a | Rel-16 | pc_ssb_RLM_Semi_StaticChAccess_r16 | No | | | +| 14 | Support of SSB-based BFD and CBD for dynamic channel access | 38.306, 4.2.7.2a | Rel-16 | pc_ssb_BFD_CBD_dynamicChannelAccess_r16 | No | | | +| 15 | Support of SSB-based BFD and CBD for semi-static channel access | 38.306, 4.2.7.2a | Rel-16 | pc_ssb_BFD_CBD_semi_staticChannelAccess_r16 | No | | | +| 16 | Support of CSI-RS-based RLM for shared spectrum | 38.306, 4.2.7.2a | Rel-16 | pc_csi_RS_RLM_r16 | No | | | +| 17 | Support of CSI-RS-based BFD and CBD for shared spectrum | 38.306, 4.2.7.2a | Rel-16 | pc_csi_RS_BFD_CBD_r16 | No | | | + +| | | | | | | | | +|----|--------------------------------------------------------------------------|------------------|--------|---------------------------------------|----|--|--| +| 18 | Support of CSI-RS based CFRA for shared spectrum | 38.306, 4.2.7.2a | Rel-16 | pc_csi_RS_CFRA_ForHO_r16 | No | | | +| 19 | Support of RSSI measurements and channel occupancy measurement reporting | 38.306, 4.2.7.2a | Rel-16 | pc_rssi_ChannelOccupancyReporting_r16 | No | | | +| 20 | Support of SS-SINR measurements in shared spectrum | 38.306, 4.2.7.14 | Rel-16 | pc_ss_SINR_Meas_r16 | No | | | + +#### A.4.3.2A NR CA Physical Layer Baseline Implementation Capabilities + +NOTE: See Annex B for status of completed NR CA configurations and power classes in this version of 3GPP UE conformance test specifications. + +##### A.4.3.2A.1 General NR CA capabilities + +**Table A.4.3.2A.1-1: Downlink NR CA capabilities (for one or more of the supported NR CA configurations)** + +| Item | DL NR CA capability | Ref. | Mnemonic | Comments | +|------|--------------------------|----------------------------------------------------|-----------------|----------| +| 1 | DL NR CA with 2 carriers | 38.101-1, 5.3A
38.101-2, 5.3A
38.101-3, 5.3A | pc_DL_NR_CA_2CC | | +| 2 | DL NR CA with 3 carriers | 38.101-1, 5.3A
38.101-2, 5.3A
38.101-3, 5.3A | pc_DL_NR_CA_3CC | | +| 3 | DL NR CA with 4 carriers | 38.101-1, 5.3A
38.101-2, 5.3A
38.101-3, 5.3A | pc_DL_NR_CA_4CC | | +| 4 | DL NR CA with 5 carriers | 38.101-1, 5.3A
38.101-2, 5.3A
38.101-3, 5.3A | pc_DL_NR_CA_5CC | | +| 5 | DL NR CA with 6 carriers | 38.101-1, 5.3A
38.101-2, 5.3A
38.101-3, 5.3A | pc_DL_NR_CA_6CC | | +| 6 | DL NR CA with 7 carriers | 38.101-1, 5.3A
38.101-2, 5.3A
38.101-3, 5.3A | pc_DL_NR_CA_7CC | | +| 7 | DL NR CA with 8 carriers | 38.101-1, 5.3A
38.101-2, 5.3A
38.101-3, 5.3A | pc_DL_NR_CA_8CC | | + +**Table A.4.3.2A.1-2: Uplink NR CA capabilities (for one or more of the supported NR CA configurations )** + +| Item | UL NR CA capability | Ref. | Mnemonic | Comments | +|------|--------------------------|----------------------------------------------------|-----------------|----------| +| 1 | UL NR CA with 2 carriers | 38.101-1, 5.3A
38.101-2, 5.3A
38.101-3, 5.3A | pc_UL_NR_CA_2CC | | +| 2 | UL NR CA with 3 carriers | 38.101-1, 5.3A
38.101-2, 5.3A
38.101-3, 5.3A | pc_UL_NR_CA_3CC | | +| 3 | UL NR CA with 4 carriers | 38.101-1, 5.3A
38.101-2, 5.3A
38.101-3, 5.3A | pc_UL_NR_CA_4CC | | +| 4 | UL NR CA with 5 carriers | 38.101-2, 5.3A
38.101-3, 5.3A | pc_UL_NR_CA_5CC | | +| 5 | UL NR CA with 6 carriers | 38.101-2, 5.3A
38.101-3, 5.3A | pc_UL_NR_CA_6CC | | +| 6 | UL NR CA with 7 carriers | 38.101-2, 5.3A
38.101-3, 5.3A | pc_UL_NR_CA_7CC | | +| 7 | UL NR CA with 8 carriers | 38.101-2, 5.3A
38.101-3, 5.3A | pc_UL_NR_CA_8CC | | + +##### A.4.3.2A.2 NR Intra-band contiguous CA + +###### A.4.3.2A.2.1 NR Intra-band contiguous CA within FR1 + +**Table A.4.3.2A.2.1-1: Downlink Bandwidth Class capabilities for NR Intra-band contiguous CA configurations within FR1 (for one or more of the supported configurations in Table A.4.3.2A.2.1-3)** + +| Item | DL NR FR1 Intra-band contiguous CA Bandwidth Class | Ref. | Mnemonic | Comments | +|------|----------------------------------------------------|------------------|--------------------------------------------|----------| +| 1 | DL NR FR1 Intra-band contiguous CA BW Class A | 38.101-1, 5.3A.5 | pc_DL_intra_contiguous_CA_NR_FR1_Classes_A | | +| 2 | DL NR FR1 Intra-band contiguous CA BW Class B | 38.101-1, 5.3A.5 | pc_DL_intra_contiguous_CA_NR_FR1_Classes_B | | +| 3 | DL NR FR1 Intra-band contiguous CA BW Class C | 38.101-1, 5.3A.5 | pc_DL_intra_contiguous_CA_NR_FR1_Classes_C | | +| 4 | DL NR FR1 Intra-band contiguous CA BW Class D | 38.101-1, 5.3A.5 | pc_DL_intra_contiguous_CA_NR_FR1_Classes_D | | +| 5 | DL NR FR1 Intra-band contiguous CA BW Class E | 38.101-1, 5.3A.5 | pc_DL_intra_contiguous_CA_NR_FR1_Classes_E | | +| 6 | void | void | void | | +| 7 | DL NR FR1 Intra-band contiguous CA BW Class G | 38.101-1, 5.3A.5 | pc_DL_intra_contiguous_CA_NR_FR1_Classes_G | | +| 8 | DL NR FR1 Intra-band contiguous CA BW Class H | 38.101-1, 5.3A.5 | pc_DL_intra_contiguous_CA_NR_FR1_Classes_H | | +| 9 | DL NR FR1 Intra-band contiguous CA BW Class I | 38.101-1, 5.3A.5 | pc_DL_intra_contiguous_NR_FR1_CA_Class_I | | +| 10 | DL NR FR1 Intra-band contiguous CA BW Class J | 38.101-1, 5.3A.5 | pc_DL_intra_contiguous_CA_NR_FR1_Classes_J | | +| 11 | DL NR FR1 Intra-band contiguous CA BW Class K | 38.101-1, 5.3A.5 | pc_DL_intra_contiguous_CA_NR_FR1_Classes_K | | +| 12 | DL NR FR1 Intra-band contiguous CA BW Class L | 38.101-1, 5.3A.5 | pc_DL_intra_contiguous_CA_NR_FR1_Classes_L | | +| 13 | DL NR FR1 Intra-band contiguous CA BW Class M | 38.101-1, 5.3A.5 | pc_DL_intra_contiguous_CA_NR_FR1_Classes_M | | +| 14 | DL NR FR1 Intra-band contiguous CA BW Class N | 38.101-1, 5.3A.5 | pc_DL_intra_contiguous_CA_NR_FR1_Classes_N | | + +| | | | | | +|----|-----------------------------------------------|------------------|--------------------------------------------|--| +| 15 | DL NR FR1 Intra-band contiguous CA BW Class O | 38.101-1, 5.3A.5 | pc_DL_intra_contiguous_CA_NR_FR1_Classes_O | | +|----|-----------------------------------------------|------------------|--------------------------------------------|--| + +**Table A.4.3.2A.2.1-2: Uplink Bandwidth Class capabilities for NR Intra-band contiguous CA configurations within FR1 (for one or more of the supported configurations in Table A.4.3.2A.2.1-3)** + +| Item | UL NR FR1 Intra-band contiguous CA Bandwidth Class | Ref. | Mnemonic | Comments | +|------|----------------------------------------------------|------------------|------------------------------------------|----------| +| 1 | UL NR FR1 Intra-band contiguous CA BW Class A | 38.101-1, 5.3A.5 | pc_UL_intra_contiguous_CA_NR_FR1_Class_A | | +| 2 | UL NR FR1 Intra-band contiguous CA BW Class B | 38.101-1, 5.3A.5 | pc_UL_intra_contiguous_CA_NR_FR1_Class_B | | +| 3 | UL NR FR1 Intra-band contiguous CA BW Class C | 38.101-1, 5.3A.5 | pc_UL_intra_contiguous_CA_NR_FR1_Class_C | | +| 4-12 | Void | | | | + +**Table A.4.3.2A.2.1-3: Supported configurations for NR Intra-band contiguous CA within FR1** + +| NR FR1 Intra-band contiguous CA configuration / Item (Note 1, 7) | Release | Supported | Supported CA Bandwidth Class(es) in UL (Note 2,5) | Supported Bandwidth Combination Set(s) (Note 3) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-----------|---------------------------------------------------|-------------------------------------------------| +| CA_n1B | Rel-16 | | | | +| CA_n41C | Rel-15 | | | | +| CA_n48B | Rel-16 | | | | +| CA_n48C | Rel-16 | | | | +| CA_n66B (Note 6) | Rel-16 | | | | +| CA_n77C | Rel-15 | | | | +| CA_n78B | Rel-16 | | | | +| CA_n78C | Rel-15 | | | | +| CA_n79C | Rel-15 | | | | +| Note 1: Notation used for intra-band contiguous CA Bands is according to TS 38.101-1 [23] Table 5.5A.1-1, e.g. 'CA_n77C' indicates CA operation on NR band n77 with DL CA Bandwidth Class C. | | | | | +| Note 2: The UL CA capabilities as per Table A.4.3.2A.2.1-2 can be supported on a single band. The UE supplier shall indicate all supported UL CA Bandwidth Class(es), in uplink of the supported CA Band(s), as per TS 38.101-1 [23] Table 5.5A.1-1. For this release of specification valid choices are 'N', 'nXB' and 'nXC', where nX is the NR band. For example, for CA_n1B, 'N' would mean only DL CA, 'n1B' would mean both DL and UL CA. | | | | | +| Note 3: The UE supplier shall indicate the supported Bandwidth Combination Set(s) as per TS 38.101-1 [23] Table 5.5A.1-1. | | | | | +| Note 4: Void. | | | | | +| Note 5: See UL( table_index ) in Note 1 of Table 4.0-3 and UL_nCC( table_index ) in Note 2 of Table 4.0-3 in TS 38.522 [9]. | | | | | +| Note 6: A UE that supports NR Band n66 (Table A.4.3.1-1) and CA operation in any CA band shall also support the DL CA configurations CA_n66B and CA_n66(2A), as per Note 7, in Table 5.2-1, in TS 38.521-1 [5]. | | | | | +| Note 7: See DL_nCC( table_index ) in Note 4 of Table 4.0-3 in TS 38.522 [9]. | | | | | + +**Table A.4.3.2A.2.1-3a: Supported configurations for NR Intra-band contiguous CA within FR1 with UL MIMO capabilities** + +| NR FR1 Intra-band contiguous CA configuration / Item (Note 1, 6) | Release | Supported | Supported CA Bandwidth Class(es) in UL (Note 2,4) | Supported Bandwidth Combination Set(s) (Note 3) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-----------|---------------------------------------------------|-------------------------------------------------| +| CA_n41C | Rel-15 | | | | +| CA_n78C | Rel-15 | | | | +| Note 1: Notation used for intra-band contiguous CA Bands is according to TS 38.101-1 [23] Table 5.5A.1-1, e.g. 'CA_n77C' indicates CA operation on NR band n77 with DL CA Bandwidth Class C. | | | | | +| Note 2: The UL CA capabilities as per Table A.4.3.2A.2.1-2 can be supported on a single band. The UE supplier shall indicate all supported UL CA Bandwidth Class(es), in uplink of the supported CA Band(s), as per TS 38.101-1 [23] Table 5.5A.1-1. For this release of specification valid choices are 'N', 'nXB' and 'nXC', where nX is the NR band. For example, for CA_n1B, 'N' would mean only DL CA, 'n1B' would mean both DL and UL CA. | | | | | +| Note 3: The UE supplier shall indicate the supported Bandwidth Combination Set(s) as per TS 38.101-1 [23] Table 5.5A.1-1. | | | | | +| Note 4: See UL( table_index ) in Note 1 of Table 4.0-3 and UL_nCC( table_index ) in Note 2 of Table 4.0-3 in TS 38.522 [9]. | | | | | +| Note 5: A UE that supports NR Band n66 (Table A.4.3.1-1) and CA operation in any CA band shall also support the DL CA configurations CA_n66B and CA_n66(2A), as per Note 7, in Table 5.2-1, in TS 38.521-1 [5]. | | | | | +| Note 6: See DL_nCC( table_index ) in Note 4 of Table 4.0-3 in TS 38.522 [9]. | | | | | + +**Table A.4.3.2A.2.1-4: Intra-band contiguous CA PC2 UE RF Baseline Implementation Capabilities** + +| Item | Intra-band contiguous CA PC2 UE RF Baseline Implementation Capabilities | Ref. | Release | Mnemonic | Comments | +|------|-------------------------------------------------------------------------|------------------|---------|------------------------|----------| +| 1 | NR Frequency band: 2496-2690 MHz | 38.101-1, 6.2A.1 | Rel-17 | pc_nrBand41_C_PC2_Supp | CA_n41C | +| 2 | NR Frequency band: 3300-3800 MHz | 38.101-1, 6.2A.1 | Rel-17 | pc_nrBand78_C_PC2_Supp | CA_n78C | + +**Table A.4.3.2A.2.1-5: Intra-band contiguous CA PC1.5 UE RF Baseline Implementation Capabilities** + +| Item | Intra-band contiguous CA PC2 UE RF Baseline Implementation Capabilities | Ref. | Release | Mnemonic | Comments | +|------|-------------------------------------------------------------------------|------------------|---------|--------------------------|----------| +| 1 | NR Frequency band: 2496-2690 MHz | 38.101-1, 6.2A.1 | Rel-17 | pc_nrBand41_C_PC1.5_Supp | CA_n41C | + +###### A.4.3.2A.2.2 NR Intra-band contiguous CA within FR2 + +**Table A.4.3.2A.2.2-1: Downlink Bandwidth Class capabilities for NR Intra-band contiguous CA configurations within FR2 (for one or more of the supported configurations in Table A.4.3.2A.2.2-3)** + +| Item | DL NR FR2 Intra-band contiguous CA Bandwidth Class | Ref. | Mnemonic | Comments | +|------|----------------------------------------------------|------------------|------------------------------------------------------|----------| +| 1 | DL NR FR2 Intra-band contiguous CA BW Class A | 38.101-2, 5.3A.4 | pc_DL_intra_c
ontiguous_CA_
NR_FR2_Clas
s_A | | +| 2 | DL NR FR2 Intra-band contiguous CA BW Class B | 38.101-2, 5.3A.4 | pc_DL_intra_c
ontiguous_CA_
NR_FR2_Clas
s_B | | +| 3 | DL NR FR2 Intra-band contiguous CA BW Class C | 38.101-2, 5.3A.4 | pc_DL_intra_c
ontiguous_CA_
NR_FR2_Clas
s_C | | +| 3a | DL NR FR2 Intra-band contiguous CA BW Class V | 38.101-2, 5.3A.4 | pc_DL_intra_c
ontiguous_CA_
NR_FR2_Clas
s_V | | +| 3b | DL NR FR2 Intra-band contiguous CA BW Class W | 38.101-2, 5.3A.4 | pc_DL_intra_c
ontiguous_CA_
NR_FR2_Clas
s_W | | +| 4 | DL NR FR2 Intra-band contiguous CA BW Class D | 38.101-2, 5.3A.4 | pc_DL_intra_c
ontiguous_CA_
NR_FR2_Clas
s_D | | +| 5 | DL NR FR2 Intra-band contiguous CA BW Class E | 38.101-2, 5.3A.4 | pc_DL_intra_c
ontiguous_CA_
NR_FR2_Clas
s_E | | +| 6 | DL NR FR2 Intra-band contiguous CA BW Class F | 38.101-2, 5.3A.4 | pc_DL_intra_c
ontiguous_CA_
NR_FR2_Clas
s_F | | +| 6a | DL NR FR2 Intra-band contiguous CA BW Class R | 38.101-2, 5.3A.4 | pc_DL_intra_c
ontiguous_CA_
NR_FR2_Clas
s_R | | +| 6b | DL NR FR2 Intra-band contiguous CA BW Class S | 38.101-2, 5.3A.4 | pc_DL_intra_c
ontiguous_CA_
NR_FR2_Clas
s_S | | +| 6c | DL NR FR2 Intra-band contiguous CA BW Class T | 38.101-2, 5.3A.4 | pc_DL_intra_c
ontiguous_CA_
NR_FR2_Clas
s_T | | +| 6d | DL NR FR2 Intra-band contiguous CA BW Class U | 38.101-2, 5.3A.4 | pc_DL_intra_c
ontiguous_CA_
NR_FR2_Clas
s_U | | +| 7 | DL NR FR2 Intra-band contiguous CA BW Class G | 38.101-2, 5.3A.4 | pc_DL_intra_c
ontiguous_CA_
NR_FR2_Clas
s_G | | +| 8 | DL NR FR2 Intra-band contiguous CA BW Class H | 38.101-2, 5.3A.4 | pc_DL_intra_c
ontiguous_CA_
NR_FR2_Clas
s_H | | + +| | | | | | +|----|------------------------------------------------|------------------|-------------------------------------------------------|--| +| 9 | DL NR FR2 Intra-band contiguous CA BW Class I | 38.101-2, 5.3A.4 | pc_DL_intra_c
ontiguous_CA_
NR_FR2_Clas
s_I | | +| 10 | DL NR FR2 Intra-band contiguous CA BW Class J | 38.101-2, 5.3A.4 | pc_DL_intra_c
ontiguous_CA_
NR_FR2_Clas
s_J | | +| 11 | DL NR FR2 Intra-band contiguous CA BW Class K | 38.101-2, 5.3A.4 | pc_DL_intra_c
ontiguous_CA_
NR_FR2_Clas
s_K | | +| 12 | DL NR FR2 Intra-band contiguous CA BW Class L | 38.101-2, 5.3A.4 | pc_DL_intra_c
ontiguous_CA_
NR_FR2_Clas
s_L | | +| 13 | DL NR FR2 Intra-band contiguous CA BW Class M | 38.101-2, 5.3A.4 | pc_DL_intra_c
ontiguous_CA_
NR_FR2_Clas
s_M | | +| 14 | DL NR FR2 Intra-band contiguous CA BW Class O | 38.101-2, 5.3A.4 | pc_DL_intra_c
ontiguous_CA_
NR_FR2_Clas
s_O | | +| 15 | DL NR FR2 Intra-band contiguous CA BW Class P | 38.101-2, 5.3A.4 | pc_DL_intra_c
ontiguous_CA_
NR_FR2_Clas
s_P | | +| 16 | DL NR FR2 Intra-band contiguous CA BW Class Q | 38.101-2, 5.3A.4 | pc_DL_intra_c
ontiguous_CA_
NR_FR2_Clas
s_Q | | +| 17 | DL NR FR2 Intra-band contiguous CA BW Class R2 | 38.101-2, 5.3A.4 | pc_DL_intra_c
ontiguous_CA_
NR_FR2_Clas
s_R2 | | +| 18 | DL NR FR2 Intra-band contiguous CA BW Class R3 | 38.101-2, 5.3A.4 | pc_DL_intra_c
ontiguous_CA_
NR_FR2_Clas
s_R3 | | +| 19 | DL NR FR2 Intra-band contiguous CA BW Class R4 | 38.101-2, 5.3A.4 | pc_DL_intra_c
ontiguous_CA_
NR_FR2_Clas
s_R4 | | +| 20 | DL NR FR2 Intra-band contiguous CA BW Class R5 | 38.101-2, 5.3A.4 | pc_DL_intra_c
ontiguous_CA_
NR_FR2_Clas
s_R5 | | +| 21 | DL NR FR2 Intra-band contiguous CA BW Class R6 | 38.101-2, 5.3A.4 | pc_DL_intra_c
ontiguous_CA_
NR_FR2_Clas
s_R6 | | +| 22 | DL NR FR2 Intra-band contiguous CA BW Class R7 | 38.101-2, 5.3A.4 | pc_DL_intra_c
ontiguous_CA_
NR_FR2_Clas
s_R7 | | + +| | | | | | +|----|-------------------------------------------------|------------------|--------------------------------------------------------|--| +| 23 | DL NR FR2 Intra-band contiguous CA BW Class R8 | 38.101-2, 5.3A.4 | pc_DL_intra_c
ontiguous_CA_
NR_FR2_Clas
s_R8 | | +| 24 | DL NR FR2 Intra-band contiguous CA BW Class R9 | 38.101-2, 5.3A.4 | pc_DL_intra_c
ontiguous_CA_
NR_FR2_Clas
s_R9 | | +| 25 | DL NR FR2 Intra-band contiguous CA BW Class R10 | 38.101-2, 5.3A.4 | pc_DL_intra_c
ontiguous_CA_
NR_FR2_Clas
s_R10 | | +| 26 | DL NR FR2 Intra-band contiguous CA BW Class R11 | 38.101-2, 5.3A.4 | pc_DL_intra_c
ontiguous_CA_
NR_FR2_Clas
s_R11 | | +| 27 | DL NR FR2 Intra-band contiguous CA BW Class R12 | 38.101-2, 5.3A.4 | pc_DL_intra_c
ontiguous_CA_
NR_FR2_Clas
s_R12 | | + +**Table A.4.3.2A.2.2-2: Uplink Bandwidth Class capabilities for NR Intra-band contiguous CA configurations within FR2 (for one or more of the supported configurations in Table A.4.3.2A.2.2-3)** + +| Item | UL NR FR2 Intra-band contiguous CA Bandwidth Class | Ref. | Mnemonic | Comments | +|------|----------------------------------------------------|------------------|------------------------------------------|----------| +| 0 | UL NR FR2 Intra-band contiguous CA BW Class A | 38.101-2, 5.3A.4 | pc_UL_intra_contiguous_CA_NR_FR2_Class_A | | +| 1 | UL NR FR2 Intra-band contiguous CA BW Class B | 38.101-2, 5.3A.4 | pc_UL_intra_contiguous_CA_NR_FR2_Class_B | | +| 2 | UL NR FR2 Intra-band contiguous CA BW Class C | 38.101-2, 5.3A.4 | pc_UL_intra_contiguous_CA_NR_FR2_Class_C | | +| 2a | UL NR FR2 Intra-band contiguous CA BW Class V | 38.101-2, 5.3A.4 | pc_UL_intra_contiguous_CA_NR_FR2_Class_V | | +| 2b | UL NR FR2 Intra-band contiguous CA BW Class W | 38.101-2, 5.3A.4 | pc_UL_intra_contiguous_CA_NR_FR2_Class_W | | +| 3 | UL NR FR2 Intra-band contiguous CA BW Class D | 38.101-2, 5.3A.4 | pc_UL_intra_contiguous_CA_NR_FR2_Class_D | | +| 4 | UL NR FR2 Intra-band contiguous CA BW Class E | 38.101-2, 5.3A.4 | pc_UL_intra_contiguous_CA_NR_FR2_Class_E | | +| 5 | UL NR FR2 Intra-band contiguous CA BW Class F | 38.101-2, 5.3A.4 | pc_UL_intra_contiguous_CA_NR_FR2_Class_F | | +| 5a | UL NR FR2 Intra-band contiguous CA BW Class R | 38.101-2, 5.3A.4 | pc_UL_intra_contiguous_CA_NR_FR2_Class_R | | +| 5b | UL NR FR2 Intra-band contiguous CA BW Class S | 38.101-2, 5.3A.4 | pc_UL_intra_contiguous_CA_NR_FR2_Class_S | | +| 5c | UL NR FR2 Intra-band contiguous CA BW Class T | 38.101-2, 5.3A.4 | pc_UL_intra_contiguous_CA_NR_FR2_Class_T | | +| 5d | UL NR FR2 Intra-band contiguous CA BW Class U | 38.101-2, 5.3A.4 | pc_UL_intra_contiguous_CA_NR_FR2_Class_U | | +| 6 | UL NR FR2 Intra-band contiguous CA BW Class G | 38.101-2, 5.3A.4 | pc_UL_intra_contiguous_CA_NR_FR2_Class_G | | +| 7 | UL NR FR2 Intra-band contiguous CA BW Class H | 38.101-2, 5.3A.4 | pc_UL_intra_contiguous_CA_NR_FR2_Class_H | | +| 8 | UL NR FR2 Intra-band contiguous CA BW Class I | 38.101-2, 5.3A.4 | pc_UL_intra_contiguous_CA_NR_FR2_Class_I | | +| 9 | UL NR FR2 Intra-band contiguous CA BW Class J | 38.101-2, 5.3A.4 | pc_UL_intra_contiguous_CA_NR_FR2_Class_J | | +| 10 | UL NR FR2 Intra-band contiguous CA BW Class K | 38.101-2, 5.3A.4 | pc_UL_intra_contiguous_CA_NR_FR2_Class_K | | +| 11 | UL NR FR2 Intra-band contiguous CA BW Class L | 38.101-2, 5.3A.4 | pc_UL_intra_contiguous_CA_NR_FR2_Class_L | | +| 12 | UL NR FR2 Intra-band contiguous CA BW Class M | 38.101-2, 5.3A.4 | pc_UL_intra_contiguous_CA_NR_FR2_Class_M | | + +| | | | | | +|----|-------------------------------------------------|------------------|--------------------------------------------|--| +| 13 | UL NR FR2 Intra-band contiguous CA BW Class O | 38.101-2, 5.3A.4 | pc_UL_intra_contiguous_CA_NR_FR2_Class_O | | +| 14 | UL NR FR2 Intra-band contiguous CA BW Class P | 38.101-2, 5.3A.4 | pc_UL_intra_contiguous_CA_NR_FR2_Class_P | | +| 15 | UL NR FR2 Intra-band contiguous CA BW Class Q | 38.101-2, 5.3A.4 | pc_UL_intra_contiguous_CA_NR_FR2_Class_Q | | +| 16 | UL NR FR2 Intra-band contiguous CA BW Class R2 | 38.101-2, 5.3A.4 | pc_UL_intra_contiguous_CA_NR_FR2_Class_R2 | | +| 17 | UL NR FR2 Intra-band contiguous CA BW Class R3 | 38.101-2, 5.3A.4 | pc_UL_intra_contiguous_CA_NR_FR2_Class_R3 | | +| 18 | UL NR FR2 Intra-band contiguous CA BW Class R4 | 38.101-2, 5.3A.4 | pc_UL_intra_contiguous_CA_NR_FR2_Class_R4 | | +| 19 | UL NR FR2 Intra-band contiguous CA BW Class R5 | 38.101-2, 5.3A.4 | pc_UL_intra_contiguous_CA_NR_FR2_Class_R5 | | +| 20 | UL NR FR2 Intra-band contiguous CA BW Class R6 | 38.101-2, 5.3A.4 | pc_UL_intra_contiguous_CA_NR_FR2_Class_R6 | | +| 21 | UL NR FR2 Intra-band contiguous CA BW Class R7 | 38.101-2, 5.3A.4 | pc_UL_intra_contiguous_CA_NR_FR2_Class_R7 | | +| 22 | UL NR FR2 Intra-band contiguous CA BW Class R8 | 38.101-2, 5.3A.4 | pc_UL_intra_contiguous_CA_NR_FR2_Class_R8 | | +| 23 | UL NR FR2 Intra-band contiguous CA BW Class R9 | 38.101-2, 5.3A.4 | pc_UL_intra_contiguous_CA_NR_FR2_Class_R9 | | +| 24 | UL NR FR2 Intra-band contiguous CA BW Class R10 | 38.101-2, 5.3A.4 | pc_UL_intra_contiguous_CA_NR_FR2_Class_R10 | | +| 25 | UL NR FR2 Intra-band contiguous CA BW Class R11 | 38.101-2, 5.3A.4 | pc_UL_intra_contiguous_CA_NR_FR2_Class_R11 | | +| 26 | UL NR FR2 Intra-band contiguous CA BW Class R12 | 38.101-2, 5.3A.4 | pc_UL_intra_contiguous_CA_NR_FR2_Class_R12 | | + +**Table A.4.3.2A.2.2-3: Supported configurations for NR Intra-band contiguous CA within FR2** + +| NR FR2 Intra-band contiguous CA configuration / Item (Note 1, 6) | Release | Supported | Supported CA Bandwidth Class(es) in UL (Note 2,5) | Supported Bandwidth Combination Set(s) (Note 3) | +|------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|---------------------------------------------------|-------------------------------------------------| +| CA_n257G | Rel-15 | | | | +| CA_n257H | Rel-15 | | | | +| CA_n257I | Rel-15 | | | | +| CA_n258B | Rel-16 | | | | +| CA_n258C | Rel-16 | | | | +| CA_n258D | Rel-16 | | | | +| CA_n258E | Rel-16 | | | | +| CA_n258F | Rel-16 | | | | +| CA_n258G | Rel-16 | | | | +| CA_n258H | Rel-16 | | | | +| CA_n258I | Rel-16 | | | | +| CA_n258J | Rel-16 | | | | +| CA_n258K | Rel-16 | | | | +| CA_n258L | Rel-16 | | | | +| CA_n258M | Rel-16 | | | | +| CA_n260G | Rel-15 | | | | +| CA_n260H | Rel-15 | | | | +| CA_n260I | Rel-15 | | | | +| CA_n260J | Rel-15 | | | | +| CA_n260K | Rel-15 | | | | +| CA_n260L | Rel-15 | | | | +| CA_n260M | Rel-15 | | | | +| CA_n261G | Rel-15 | | | | +| CA_n261H | Rel-15 | | | | +| CA_n261I | Rel-15 | | | | +| CA_n261J | Rel-15 | | | | +| CA_n261K | Rel-15 | | | | +| CA_n261L | Rel-15 | | | | +| CA_n261M | Rel-15 | | | | +| Note 1: | Notation used for intra-band contiguous CA Bands is according to TS 38.101-2 [24] Table 5.5A.1-1, e.g. 'CA_n257C' indicates CA operation on NR band n257 with DL CA Bandwidth Class C. | | | | +| Note 2: | The UL CA capabilities as per Table A.4.3.2A.2.2-2 can be supported on a single band. The UE supplier shall indicate all supported UL CA Bandwidth Class(es), in uplink of the supported CA Band(s), as per TS 38.101-2 [24] Table 5.5A.1-1. For this release of specification valid choices are 'N', 'nXB' ~ 'nXM' and 'nXO' ~ 'nXQ', where nX is the NR band. For example, for CA_n257C, 'N' would mean only DL CA, 'n257C' would mean both DL and UL CA operation on NR band n257 with CA Bandwidth Class C. | | | | +| Note 3: | The UE supplier shall indicate the supported Bandwidth Combination Set(s) as per TS 38.101-2 [24] Table 5.5A.1-1. | | | | +| Note 4: | Void. | | | | +| Note 5: | See UL( table_index ) in Note 1 of Table 4.0-3 and UL_nCC( table_index ) in Note 2 of Table 4.0-3 in TS 38.522 [9]. | | | | +| Note 6: | See DL_nCC( table_index ) in Note 4 of Table 4.0-3 in TS 38.522 [9]. | | | | + +##### A.4.3.2A.3 NR Intra-band non-contiguous CA + +###### A.4.3.2A.3.1 NR Intra-band non-contiguous CA within FR1 + +**Table A.4.3.2A.3.1-1: Downlink Bandwidth Class capabilities for NR Intra-band non-contiguous CA configurations within FR1 (for one or more of the supported configurations in Table A.4.3.2A.3.1-3)** + +| Item | DL NR FR1 Intra-band non-contiguous CA Bandwidth Class | Ref. | Mnemonic | Comments | +|------|------------------------------------------------------------------|------------------|--------------------------------------------------|----------| +| 1 | DL NR FR1 Intra-band non-contiguous CA BW Class Combination (2A) | 38.101-1, 5.3A.5 | pc_DL_intra_n_on_contiguous_CA_NR_FR1_Class_(2A) | | +| 2 | DL NR FR1 Intra-band non-contiguous CA BW Class Combination (3A) | 38.101-1, 5.3A.5 | pc_DL_intra_n_on_contiguous_CA_NR_FR1_Class_(3A) | | +| 3 | DL NR FR1 Intra-band non-contiguous CA BW Class Combination (4A) | 38.101-1, 5.3A.5 | pc_DL_intra_n_on_contiguous_CA_NR_FR1_Class_(4A) | | + +**Table A.4.3.2A.3.1-1a: Downlink Bandwidth Class capabilities for NR mixed Intra-band contiguous and non-contiguous CA configurations within FR1 (for one or more of the supported configurations in Table A.4.3.2A.3.1-3a)** + +| Item | DL NR FR1 mixed Intra-band contiguous and non-contiguous CA Bandwidth Class | Ref. | Mnemonic | Comments | +|------|----------------------------------------------------------------------------------------|------------------|-------------------------------------------------------------|----------| +| 1 | DL NR FR1 mixed Intra-band contiguous and non-contiguous CA BW Class Combination (A-B) | 38.101-1, 5.3A.5 | pc_DL_intra_contiguous_non_contiguous_CA_NR_FR1_Class_(A-B) | | +| 2 | DL NR FR1 mixed Intra-band contiguous and non-contiguous CA BW Class Combination (A-C) | 38.101-1, 5.3A.5 | pc_DL_intra_contiguous_non_contiguous_CA_NR_FR1_Class_(A-C) | | + +**Table A.4.3.2A.3.1-2: Uplink Bandwidth Class capabilities for NR Intra-band non-contiguous CA configurations within FR1 (for one or more of the supported configurations in Table A.4.3.2A.3.1-3)** + +| Item | UL NR FR1 Intra-band non-contiguous CA Bandwidth Class | Ref. | Mnemonic | Comments | +|------|------------------------------------------------------------------|------------------|--------------------------------------------------|----------| +| 1 | UL NR FR1 Intra-band non-contiguous CA BW Class Combination (2A) | 38.101-1, 5.3A.5 | pc_UL_intra_n_on_contiguous_CA_NR_FR1_Class_(2A) | | + +**Table A.4.3.2A.3.1-2a: Uplink Bandwidth Class capabilities for NR mixed Intra-band contiguous and non-contiguous CA configurations within FR1 (for one or more of the supported configurations in Table A.4.3.2A.3.1-3a)** + +| Item | UL NR FR1 mixed Intra-band contiguous and non-contiguous CA Bandwidth Class | Ref. | Mnemonic | Comments | +|------|--------------------------------------------------------------------------------------|------------------|-----------------------------------------------------------|----------| +| 1 | UL NR FR1 mixed Intra-band contiguous and non-contiguous CA BW Class Combination (B) | 38.101-1, 5.3A.5 | pc_UL_intra_contiguous_non_contiguous_CA_NR_FR1_Class_(B) | | + +**Table A.4.3.2A.3.1-3: Supported configurations for NR Intra-band non-contiguous CA within FR1** + +| NR FR1 Intra-band non-contiguous CA configuration / Item (Note 5) | Release | Supported | Supported CA Bandwidth Class(es) in UL (Note 3) | Supported Bandwidth Combination Set(s) (Note 1) | +|-------------------------------------------------------------------|---------|-----------|-------------------------------------------------|-------------------------------------------------| +| CA_n2(2A) | Rel-17 | | | | +| CA_n48(2A) | Rel-16 | | | | +| CA_n66(2A) (Note 4) | Rel-16 | | | | +| CA_n77(2A) | Rel-17 | | | | +| CA_n71(2A) | Rel-17 | | | | +| CA_n77(2A) | Rel-17 | | | | +| CA_n78(2A) | Rel-17 | | | | + +Note 1: The UE supplier shall indicate the supported Bandwidth Combination Set(s) as per TS 38.101-1 [23] Table 5.5A.2-1. + +Note 2: Void. + +Note 3: See UL(*table\_index*) in Note 1 of Table 4.0-3 and UL\_nCC(*table\_index*) in Note 2 of Table 4.0-3 in TS 38.522 [9]. + +Note 4: A UE that supports NR Band n66 (Table A.4.3.1-1) and CA operation in any CA band shall also support the DL CA configurations CA\_n66B and CA\_n66(2A), as per Note 7, in Table 5.2-1, in TS 38.521-1 [5]. + +Note 5: See DL\_nCC(*table\_index*) in Note 4 of Table 4.0-3 in TS 38.522 [9]. + +**Table A.4.3.2A.3.1-3a: Supported configurations for NR mixed Intra-band contiguous and non-contiguous CA within FR1** + +| NR FR1 mixed Intra-band contiguous and non-contiguous CA configuration / Item | Release | Supported | Supported CA Bandwidth Class(es) in UL (Note 3) | Supported Bandwidth Combination Set(s) (Note 1) | +|-------------------------------------------------------------------------------|---------|-----------|-------------------------------------------------|-------------------------------------------------| +| TBD | | | | | + +###### A.4.3.2A.3.2 NR Intra-band non-contiguous CA within FR2 + +**Table A.4.3.2A.3.2-1: Downlink Bandwidth Class capabilities with single bandwidth class for NR Intra-band non-contiguous CA configurations within FR2 (for one or more of the supported configurations in Table A.4.3.2A.3.2-3)** + +| Item | DL NR FR2 Intra-band non-contiguous CA Bandwidth Class (with single bandwidth class) | Ref. | Mnemonic | Comments | +|------|--------------------------------------------------------------------------------------|------------------|--------------------------------------------------------------|----------| +| 1 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2A) | 38.101-2, 5.3A.4 | pc_DL_intra_n
on_contiguous
_CA_NR_FR2
_Class_(2A) | | +| 2 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (3A) | 38.101-2, 5.3A.4 | pc_DL_intra_n
on_contiguous
_CA_NR_FR2
_Class_(3A) | | +| 3 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (4A) | 38.101-2, 5.3A.4 | pc_DL_intra_n
on_contiguous
_CA_NR_FR2
_Class_(4A) | | +| 4 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (5A) | 38.101-2, 5.3A.4 | pc_DL_intra_n
on_contiguous
_CA_NR_FR2
_Class_(5A) | | +| 5 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (6A) | 38.101-2, 5.3A.4 | pc_DL_intra_n
on_contiguous
_CA_NR_FR2
_Class_(6A) | | +| 6 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (7A) | 38.101-2, 5.3A.4 | pc_DL_intra_n
on_contiguous
_CA_NR_FR2
_Class_(7A) | | +| 7 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (8A) | 38.101-2, 5.3A.4 | pc_DL_intra_n
on_contiguous
_CA_NR_FR2
_Class_(8A) | | +| 8 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (9A) | 38.101-2, 5.3A.4 | pc_DL_intra_n
on_contiguous
_CA_NR_FR2
_Class_(9A) | | +| 9 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (10A) | 38.101-2, 5.3A.4 | pc_DL_intra_n
on_contiguous
_CA_NR_FR2
_Class_(10A) | | +| 10 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2D) | 38.101-2, 5.3A.4 | pc_DL_intra_n
on_contiguous
_CA_NR_FR2
_Class_(2D) | | +| 11 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2G) | 38.101-2, 5.3A.4 | pc_DL_intra_n
on_contiguous
_CA_NR_FR2
_Class_(2G) | | +| 12 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (3G) | 38.101-2, 5.3A.4 | pc_DL_intra_n
on_contiguous
_CA_NR_FR2
_Class_(3G) | | +| 13 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (4G) | 38.101-2, 5.3A.4 | pc_DL_intra_n
on_contiguous
_CA_NR_FR2
_Class_(4G) | | +| 14 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2H) | 38.101-2, 5.3A.4 | pc_DL_intra_n
on_contiguous
_CA_NR_FR2
_Class_(2H) | | + +| | | | | | +|----|------------------------------------------------------------------|------------------|-------------------------------------------------------------|--| +| 15 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2I) | 38.101-2, 5.3A.4 | pc_DL_intra_n
on_contiguous
_CA_NR_FR2
_Class_(2I) | | +| 16 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2O) | 38.101-2, 5.3A.4 | pc_DL_intra_n
on_contiguous
_CA_NR_FR2
_Class_(2O) | | +| 17 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (3O) | 38.101-2, 5.3A.4 | pc_DL_intra_n
on_contiguous
_CA_NR_FR2
_Class_(3O) | | +| 18 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (4O) | 38.101-2, 5.3A.4 | pc_DL_intra_n
on_contiguous
_CA_NR_FR2
_Class_(4O) | | +| 19 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (5O) | 38.101-2, 5.3A.4 | pc_DL_intra_n
on_contiguous
_CA_NR_FR2
_Class_(5O) | | +| 20 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (6O) | 38.101-2, 5.3A.4 | pc_DL_intra_n
on_contiguous
_CA_NR_FR2
_Class_(6O) | | +| 21 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (7O) | 38.101-2, 5.3A.4 | pc_DL_intra_n
on_contiguous
_CA_NR_FR2
_Class_(7O) | | +| 22 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2P) | 38.101-2, 5.3A.4 | pc_DL_intra_n
on_contiguous
_CA_NR_FR2
_Class_(2P) | | +| 23 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (3P) | 38.101-2, 5.3A.4 | pc_DL_intra_n
on_contiguous
_CA_NR_FR2
_Class_(3P) | | +| 24 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (4P) | 38.101-2, 5.3A.4 | pc_DL_intra_n
on_contiguous
_CA_NR_FR2
_Class_(4P) | | +| 25 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2Q) | 38.101-2, 5.3A.4 | pc_DL_intra_n
on_contiguous
_CA_NR_FR2
_Class_(2Q) | | +| 26 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2I) | 38.101-2, 5.3A.4 | pc_DL_intra_n
on_contiguous
_CA_NR_FR2
_Class_(2I) | | + +###### **Table A.4.3.2A.3.2-1a: Downlink Bandwidth Class capabilities with multiple bandwidth classes for NR Intra-band non-contiguous CA configurations within FR2 (for one or more of the supported configurations in Table A.4.3.2A.3.2-3a)** + +| Item | DL NR FR2 Intra-band non-contiguous CA Bandwidth Class (with multiple bandwidth classes) | Ref. | Mnemonic | Comments | +|------|------------------------------------------------------------------------------------------|------------------|---------------------------------------------------|----------| +| 1 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-D) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-D) | | +| 2 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-2D) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-2D) | | +| 3 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-G) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-G) | | +| 4 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-2G) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-2G) | | +| 5 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-3G) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-3G) | | +| 6 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-4G) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-4G) | | +| 7 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-H) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-H) | | +| 8 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-I) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-I) | | +| 9 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-2I) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-2I) | | +| 10 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-J) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-J) | | +| 11 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-K) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-K) | | +| 12 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-O) | | +| 13 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-2O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-2O) | | +| 14 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-3O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-3O) | | +| 15 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-4O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-4O) | | +| 16 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-5O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-5O) | | + +| | | | | | +|----|---------------------------------------------------------------------|------------------|----------------------------------------------------|--| +| 17 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-6O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-6O) | | +| 18 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-7O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-7O) | | +| 19 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-P) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-P) | | +| 20 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-2P) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-2P) | | +| 21 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-3P) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-3P) | | +| 22 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-4P) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-4P) | | +| 23 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-Q) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-Q) | | +| 24 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-2Q) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-2Q) | | +| 25 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2A-D) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2A-D) | | +| 26 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2A-2D) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2A-2D) | | +| 27 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2A-G) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2A-G) | | +| 28 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2A-2G) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2A-2G) | | +| 29 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2A-O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2A-O) | | +| 30 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2A-2O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2A-2O) | | +| 31 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2A-3O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2A-3O) | | + +| | | | | | +|----|---------------------------------------------------------------------|------------------|----------------------------------------------------|--| +| 32 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2A-4O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2A-4O) | | +| 33 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2A-P) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2A-P) | | +| 34 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2A-2P) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2A-2P) | | +| 35 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2A-3P) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2A-3P) | | +| 36 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2A-4P) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2A-4P) | | +| 37 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2A-Q) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2A-Q) | | +| 38 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2A-2Q) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2A-2Q) | | +| 39 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2A-H) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2A-H) | | +| 40 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2A-2H) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2A-2H) | | +| 41 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2A-I) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2A-I) | | +| 42 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (3A-G) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(3A-G) | | +| 43 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (3A-2G) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(3A-2G) | | +| 44 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (3A-O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(3A-O) | | +| 45 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (3A-2O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(3A-2O) | | +| 46 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (3A-3O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(3A-3O) | | + +| | | | | | +|----|---------------------------------------------------------------------|------------------|----------------------------------------------------|--| +| 47 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (3A-4O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(3A-4O) | | +| 48 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (3A-P) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(3A-P) | | +| 49 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (3A-2P) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(3A-2P) | | +| 50 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (3A-Q) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(3A-Q) | | +| 51 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (3A-2Q) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(3A-2Q) | | +| 52 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (4A-G) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(4A-G) | | +| 53 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (4A-2G) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(4A-2G) | | +| 54 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (4A-Q) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(4A-Q) | | +| 55 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (4A-2Q) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(4A-2Q) | | +| 56 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (4A-O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(4A-O) | | +| 57 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (4A-2O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(4A-2O) | | +| 58 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (4A-3O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(4A-3O) | | +| 59 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (4A-4O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(4A-4O) | | +| 60 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (4A-P) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(4A-P) | | + +| | | | | | +|----|---------------------------------------------------------------------|------------------|----------------------------------------------------|--| +| 61 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (4A-2P) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(4A-2P) | | +| 62 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (5A-O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(5A-O) | | +| 63 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (5A-2O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(5A-2O) | | +| 64 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (5A-3O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(5A-3O) | | +| 65 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (5A-4O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(5A-4O) | | +| 66 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (5A-P) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(5A-P) | | +| 67 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (5A-2P) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(5A-2P) | | +| 68 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (6A-O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(6A-O) | | +| 69 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (6A-2O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(6A-2O) | | +| 70 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (6A-3O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(6A-3O) | | +| 71 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (6A-P) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(6A-P) | | +| 72 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (6A-2P) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(6A-2P) | | +| 73 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (7A-O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(7A-O) | | +| 74 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (7A-2O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(7A-2O) | | + +| | | | | | +|----|---------------------------------------------------------------------|------------------|----------------------------------------------------|--| +| 75 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (7A-3O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(7A-3O) | | +| 76 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (8A-O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(8A-O) | | +| 77 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (8A-2O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(8A-2O) | | +| 78 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (D-G) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(D-G) | | +| 79 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (D-2G) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(D-2G) | | +| 80 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (D-H) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(D-H) | | +| 81 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (D-I) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(D-I) | | +| 82 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (D-O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(D-O) | | +| 83 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (D-2O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(D-2O) | | +| 84 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (D-P) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(D-P) | | +| 85 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (D-Q) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(D-Q) | | +| 86 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2D-O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2D-O) | | +| 87 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (E-O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(E-O) | | +| 88 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (E-P) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(E-P) | | +| 89 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (E-Q) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(E-Q) | | +| 90 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (G-H) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(G-H) | | +| 91 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (G-I) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(G-I) | | + +| | | | | | +|-----|---------------------------------------------------------------------|------------------|----------------------------------------------------|--| +| 92 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (G-O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(G-O) | | +| 93 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (G-2O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(G-2O) | | +| 94 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (G-3O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(G-3O) | | +| 95 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (G-4O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(G-4O) | | +| 96 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2G-O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2G-O) | | +| 97 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2G-2O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2G-2O) | | +| 98 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2G-3O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2G-3O) | | +| 99 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2G-4O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2G-4O) | | +| 100 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (3G-O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(3G-O) | | +| 101 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (4G-O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(4G-O) | | +| 102 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (H-I) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(H-I) | | +| 103 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (H-O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(H-O) | | +| 104 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2H-O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2H-O) | | +| 105 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (O-P) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(O-P) | | +| 106 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (O-2P) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(O-2P) | | +| 107 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (O-Q) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(O-Q) | | + +| | | | | | +|-----|-----------------------------------------------------------------------|------------------|------------------------------------------------------|--| +| 108 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (O-2Q) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(O-2Q) | | +| 109 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2O-P) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2O-P) | | +| 110 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2O-2P) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2O-2P) | | +| 111 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2O-Q) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2O-Q) | | +| 112 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2O-2Q) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2O-2Q) | | +| 113 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (P-Q) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(P-Q) | | +| 114 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-D-O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-D-O) | | +| 115 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-D-2O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-D-2O) | | +| 116 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-D-H) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-D-H) | | +| 117 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-G-H) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-G-H) | | +| 118 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-G-I) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-G-I) | | +| 119 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-G-O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-G-O) | | +| 120 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-G-2O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-G-2O) | | +| 121 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-2G-O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-2G-O) | | +| 122 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-2G-2O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-2G-2O) | | + +| | | | | | +|-----|-----------------------------------------------------------------------|------------------|------------------------------------------------------|--| +| 123 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-3G-O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-3G-O) | | +| 124 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-H-I) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-H-I) | | +| 125 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-O-P) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-O-P) | | +| 126 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-O-2P) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-O-2P) | | +| 127 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-O-Q) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-O-Q) | | +| 128 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-O-2Q) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-O-2Q) | | +| 129 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-2O-P) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-2O-P) | | +| 130 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-2O-2P) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-2O-2P) | | +| 131 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-2O-Q) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-2O-Q) | | +| 132 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-2O-2Q) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-2O-2Q) | | +| 133 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (A-P-Q) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(A-P-Q) | | +| 134 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2A-D-O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2A-D-O) | | +| 135 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2A-D-2O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2A-D-2O) | | +| 136 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2A-G-O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2A-G-O) | | + +| | | | | | +|-----|------------------------------------------------------------------------|------------------|-------------------------------------------------------|--| +| 137 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2A-G-2O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2A-G-2O) | | +| 138 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2A-2G-O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2A-2G-O) | | +| 139 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2A-2G-2O) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2A-2G-2O) | | +| 140 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2A-O-P) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2A-O-P) | | +| 141 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2A-O-2P) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2A-O-2P) | | +| 142 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2A-2O-P) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2A-2O-P) | | +| 143 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2A-2O-2P) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2A-2O-2P) | | +| 144 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2A-O-Q) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2A-O-Q) | | +| 145 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2A-O-2Q) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2A-O-2Q) | | +| 146 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2A-2O-Q) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2A-2O-Q) | | +| 147 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (2A-2O-2Q) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(2A-2O-2Q) | | +| 148 | DL NR FR2 Intra-band non-contiguous CA BW Class Combination (3A-O-P) | 38.101-2, 5.3A.4 | pc_DL_intra_non_contiguous_CA_NR_FR2_Class_(3A-O-P) | | + +**Table A.4.3.2A.3.2-2: Uplink Bandwidth Class capabilities with single bandwidth class for NR Intra-band non-contiguous CA configurations within FR2 (for one or more of the supported configurations in Table A.4.3.2A.3.2-3)** + +| Item | UL NR FR2 Intra-band non-contiguous CA Bandwidth Class (with single bandwidth class) | Ref. | Mnemonic | Comments | +|------|--------------------------------------------------------------------------------------|------------------|-------------------------------------------------------------|----------| +| 1 | UL NR FR2 Intra-band non-contiguous CA BW Class Combination (2A) | 38.101-2, 5.3A.4 | pc_UL_intra_n
on_contiguous
_CA_NR_FR2
_Class_(2A) | | +| 2 | UL NR FR2 Intra-band non-contiguous CA BW Class Combination (3A) | 38.101-2, 5.3A.4 | pc_UL_intra_n
on_contiguous
_CA_NR_FR2
_Class_(3A) | | +| 3 | UL NR FR2 Intra-band non-contiguous CA BW Class Combination (G) | 38.101-2, 5.3A.4 | pc_UL_intra_n
on_contiguous
_CA_NR_FR2
_Class_(G) | | +| 4 | UL NR FR2 Intra-band non-contiguous CA BW Class Combination (H) | 38.101-2, 5.3A.4 | pc_UL_intra_n
on_contiguous
_CA_NR_FR2
_Class_(H) | | +| 5 | UL NR FR2 Intra-band non-contiguous CA BW Class Combination (I) | 38.101-2, 5.3A.4 | pc_UL_intra_n
on_contiguous
_CA_NR_FR2
_Class_(I) | | + +**Table A.4.3.2A.3.2-2a: Uplink Bandwidth Class capabilities with multiple bandwidth classes for NR Intra-band non-contiguous CA configurations within FR2 (for one or more of the supported configurations in Table A.4.3.2A.3.2-3a)** + +| Item | UL NR FR2 Intra-band non-contiguous CA Bandwidth Class (with multiple bandwidth classes) | Ref. | Mnemonic | Comments | +|------|------------------------------------------------------------------------------------------|------------------|-------------------------------------------------|----------| +| 1 | UL NR FR2 Intra-band non-contiguous CA BW Class Combination (D) | 38.101-2, 5.3A.4 | pc_UL_intra_non_contiguous_CA_NR_F R2_Class_(D) | | +| 2 | UL NR FR2 Intra-band non-contiguous CA BW Class Combination (E) | 38.101-2, 5.3A.4 | pc_UL_intra_non_contiguous_CA_NR_F R2_Class_(E) | | +| 3 | UL NR FR2 Intra-band non-contiguous CA BW Class Combination (G) | 38.101-2, 5.3A.4 | pc_UL_intra_non_contiguous_CA_NR_F R2_Class_(G) | | +| 4 | UL NR FR2 Intra-band non-contiguous CA BW Class Combination (H) | 38.101-2, 5.3A.4 | pc_UL_intra_non_contiguous_CA_NR_F R2_Class_(H) | | +| 5 | UL NR FR2 Intra-band non-contiguous CA BW Class Combination (I) | 38.101-2, 5.3A.4 | pc_UL_intra_non_contiguous_CA_NR_F R2_Class_(I) | | +| 6 | UL NR FR2 Intra-band non-contiguous CA BW Class Combination (O) | 38.101-2, 5.3A.4 | pc_UL_intra_non_contiguous_CA_NR_F R2_Class_(O) | | +| 7 | UL NR FR2 Intra-band non-contiguous CA BW Class Combination (P) | 38.101-2, 5.3A.4 | pc_UL_intra_non_contiguous_CA_NR_F R2_Class_(P) | | +| 8 | UL NR FR2 Intra-band non-contiguous CA BW Class Combination (Q) | 38.101-2, 5.3A.4 | pc_UL_intra_non_contiguous_CA_NR_F R2_Class_(Q) | | + +**Table A.4.3.2A.3.2-3: Supported configurations with single bandwidth class for NR Intra-band non-contiguous CA within FR2** + +| NR FR2 Intra-band non-contiguous CA configuration / Item (Note 4) | Release | Supported | Supported CA Bandwidth Class(es) in UL (Note 3) | Supported Bandwidth Combination Set(s) (Note 1) | +|-------------------------------------------------------------------------------------------------------------------------------------------|---------|-----------|-------------------------------------------------|-------------------------------------------------| +| CA_n261(2A) | Rel-15 | | | | +| Note 1: The UE supplier shall indicate the supported Bandwidth Combination Set(s) as per TS 38.101-2 [24] Table 5.5A.2-1. | | | | | +| Note 2: Void. | | | | | +| Note 3: See UL( table_index ) in Note 1 of Table 4.0-3 and UL_nCC( table_index ) in Note 2 of Table 4.0-3 in TS 38.522 [9]. | | | | | +| Note 4: See DL_nCC( table_index ) in Note 4 of Table 4.0-3 in TS 38.522 [9]. | | | | | + +**Table A.4.3.2A.3.2-3a: Supported configurations with multiple bandwidth classes for NR Intra-band non-contiguous CA within FR2** + +TBD + +##### A.4.3.2A.4 NR Inter-band CA within FR1 + +###### A.4.3.2A.4.1 NR Inter-band CA within FR1 (two bands) + +**Table A.4.3.2A.4.1-1: Downlink Bandwidth Class Combination capabilities for NR Inter-band CA configuration within FR1 and two bands (for one or more of the supported CA configurations in Table A.4.3.2A.4.1-3)** + +| Item | DL NR FR1 Inter-band CA Bandwidth Class | Ref. | Mnemonic | Comments | +|------|--------------------------------------------------------------------|------------------|-----------------------------------------------|----------| +| 1 | DL NR FR1 Inter-band CA BW Class Combination A-A (two bands) | 38.101-1, 5.3A.5 | pc_DL_inter_band_CA_NR_FR1_2B_Class_A-A | | +| 2 | DL NR FR1 Inter-band CA BW Class Combination A-(2A) (two bands) | 38.101-1, 5.3A.5 | pc_DL_inter_band_CA_NR_FR1_2B_Class_A-(2A) | | +| 3 | DL NR FR1 Inter-band CA BW Class Combination A-B (two bands) | 38.101-1, 5.3A.5 | pc_DL_inter_band_CA_NR_FR1_2B_Class_A-B | | +| 4 | DL NR FR1 Inter-band CA BW Class Combination A-C (two bands) | 38.101-1, 5.3A.5 | pc_DL_inter_band_CA_NR_FR1_2B_Class_A-C | | +| 5 | DL NR FR1 Inter-band CA BW Class Combination (2A)-A (two bands) | 38.101-1, 5.3A.5 | pc_DL_inter_band_CA_NR_FR1_2B_Class_(2A)-A | | +| 6 | DL NR FR1 Inter-band CA BW Class Combination (2A)-(2A) (two bands) | 38.101-1, 5.3A.5 | pc_DL_inter_band_CA_NR_FR1_2B_Class_(2A)-(2A) | | +| 7 | DL NR FR1 Inter-band CA BW Class Combination (2A)-B (two bands) | 38.101-1, 5.3A.5 | pc_DL_inter_band_CA_NR_FR1_2B_Class_(2A)-B | | +| 8 | DL NR FR1 Inter-band CA BW Class Combination B-A (two bands) | 38.101-1, 5.3A.5 | pc_DL_inter_band_CA_NR_FR1_2B_Class_B-A | | +| 9 | DL NR FR1 Inter-band CA BW Class Combination C-A (two bands) | 38.101-1, 5.3A.5 | pc_DL_inter_band_CA_NR_FR1_2B_Class_C-A | | +| 10 | DL NR FR1 Inter-band CA BW Class Combination C-B (two bands) | 38.101-1, 5.3A.5 | pc_DL_inter_band_CA_NR_FR1_2B_Class_C-B | | + +**Table A.4.3.2A.4.1-2: Uplink Bandwidth Class Combination capabilities for NR Inter-band CA within FR1 and two bands (for one or more of the supported CA configurations in Table A.4.3.2A.4.1-3)** + +| Item | UL NR FR1 Inter-band CA Bandwidth Class | Ref. | Mnemonic | Comments | +|------|---------------------------------------------------------------|------------------|--------------------------------------------------|----------| +| 1 | UL NR FR1 Inter-band CA BW Class Combination A-A (two bands) | 38.101-1, 5.3A.5 | pc_UL_inter_band_
_CANR_FR1_2B_
Class_A-A | | +| 2 | UL NR FR1 Inter-band CA BW Class Combination (2A) (two bands) | 38.101-1, 5.3A.5 | pc_UL_inter_band_
_CANR_FR1_2B_
Class_(2A) | | +| 3 | UL NR FR1 Inter-band CA BW Class Combination B (two bands) | 38.101-1, 5.3A.5 | pc_UL_inter_band_
_CANR_FR1_2B_
Class_B | | +| 4 | UL NR FR1 Inter-band CA BW Class Combination C (two bands) | 38.101-1, 5.3A.5 | pc_UL_inter_band_
_CANR_FR1_2B_
Class_C | | + +**Table A.4.3.2A.4.1-3: Supported configurations for NR Inter-band CA within FR1 and two bands** + +| NR FR1
Inter-band
CA
configuration
n / Item
(Note 1, 9) | Release | Supported | Supported CA
Bandwidth
Class(es)
in UL
(Note 2,5) | Supported
Bandwidth
Combination
Set(s)
(Note 3) | Supported
1Tx-2Tx
UL Tx Switch-
ing Band
Pair
(Note 7, 8) | Supported
2Tx-2Tx
UL Tx Switch-
ing Band Pair
(Note 7, 8) | Supported
uplink Tx
Switching-
DL-
Interruption
-r16
(Note 10) | Supported
simultaneous Rx Tx
(Note 11) | +|------------------------------------------------------------------------|---------|-----------|---------------------------------------------------------------|-------------------------------------------------------------|--------------------------------------------------------------------------|-----------------------------------------------------------------------|----------------------------------------------------------------------------------|----------------------------------------------| +| CA_n1A-n3A | Rel-16 | | | | | | | | +| CA_n1A-n28A | Rel-16 | | | | | | | | +| CA_n1(2A)-n3A | Rel-17 | | | | | | | | +| CA_n1(2A)-n5A | Rel-17 | | | | | | | | +| CA_n1A-n8A | Rel-16 | | | | | | | | +| CA_n1(2A)-n8A | Rel-17 | | | | | | | | +| CA_n1A-n77A | Rel-16 | | | | | | Not supported | Yes | +| CA_n1A-n78A | Rel-16 | | | | | | Not supported | Yes | +| CA_n1(2A)-n78A | Rel-17 | | | | | | Not supported | Yes | +| CA_n1A-n78(2A) | Rel-17 | | | | | | Not supported | Yes | +| CA_n1A-n78C | Rel-16 | | | | | | Not supported | Yes | +| CA_n1A-n79A | Rel-16 | | | | | | Not supported | Yes | +| CA_n2A-n5A | Rel-16 | | | | | | | | +| CA_n2A-n14A | Rel-17 | | | | | | | | +| CA_n2A-n48A | Rel-16 | | | | | | | | +| CA_n2A-n48B | Rel-17 | | | | | | | | +| CA_n2A-n66A | Rel-16 | | | | | | | | +| CA_n2A-n77A | Rel-16 | | | | | | | | +| CA_n2A-n77C | Rel-17 | | | | | | | | +| CA_n3A-n5A | Rel-17 | | | | | | | | +| CA_n3(2A)-n5A | Rel-17 | | | | | | | | +| CA_n3A-n8A | Rel-16 | | | | | | | | +| CA_n3(2A)-n8A | Rel-17 | | | | | | | | +| CA_n3A-n28A | Rel-16 | | | | | | | | +| CA_n3A-n41A | Rel-16 | | | | | | Not supported | Yes | +| CA_n3A-n77A | Rel-15 | | | | | Not supported | | CA_n3A-n77A | +| CA_n3A-n77(2A) | Rel-16 | | | | | | Not supported | Yes | +| CA_n3A-n78A | Rel-15 | | | | | | Not supported | Yes | + +| | | | | | | | | | +|-----------------|--------|--|--|--|--|--|---------------|-----| +| CA_n5A-n48A | Rel-17 | | | | | | | | +| CA_n5A-n48B | Rel-17 | | | | | | | | +| CA_n3A-n78(2A) | Rel-17 | | | | | | Not supported | Yes | +| CA_n3(2A)-n78A | Rel-17 | | | | | | Not supported | Yes | +| CA_n5A-n66A | Rel-16 | | | | | | | | +| CA_n5A-n78(2A) | Rel-17 | | | | | | | Yes | +| CA_n5A-n7A | Rel-16 | | | | | | | | +| CA_n5A-n48A | Rel-17 | | | | | | | | +| CA_n5A-n77A | Rel-16 | | | | | | | Yes | +| CA_n5A-n77C | Rel-17 | | | | | | | | +| CA_n5A-n78A | Rel-16 | | | | | | Not supported | Yes | +| CA_n7A-n78A | Rel-16 | | | | | | | Yes | +| CA_n8A-n78A | Rel-15 | | | | | | Not supported | Yes | +| CA_n8A-n78(2A) | Rel-17 | | | | | | Not supported | Yes | +| CA_n14A-n30A | Rel-17 | | | | | | | | +| CA_n14A-n66A | Rel-17 | | | | | | | | +| CA_n14A-n77A | Rel-17 | | | | | | | | +| CA_n20A-n78A | Rel-16 | | | | | | | | +| CA_n24A-n41A | Rel-17 | | | | | | | | +| CA_n24A-n41(2A) | Rel-17 | | | | | | | | +| CA_n24A-n48A | Rel-17 | | | | | | | | +| CA_n24A-n48B | Rel-17 | | | | | | | | +| CA_n24A-n48(2A) | Rel-17 | | | | | | | | +| CA_n24A-n77A | Rel-17 | | | | | | | | +| CA_n24A-n77C | Rel-17 | | | | | | | | +| CA_n25A-n66A | Rel-17 | | | | | | | | +| CA_n25A-n77A | Rel-17 | | | | | | | | +| CA_n25A-n77(2A) | Rel-17 | | | | | | | | +| CA_n25A-n78A | Rel-17 | | | | | | | | + +| | | | | | | | | | +|--------------------------|--------|--|--|--|--|--|---------------|-----| +| CA_n25A-n78(2A) | Rel-17 | | | | | | | | +| CA_n26A-n66A | Rel-17 | | | | | | | | +| CA_n26A-n66(2A) | Rel-17 | | | | | | | | +| CA_n26A-n70A | Rel-17 | | | | | | | | +| CA_n28A-n41A | Rel-16 | | | | | | | Yes | +| CA_n28A-n77A | Rel-16 | | | | | | Not supported | | +| CA_n28A-n77(2A) | Rel-16 | | | | | | Not supported | Yes | +| CA_n28A-n78A | Rel-16 | | | | | | Not supported | Yes | +| CA_n28A-n79A | Rel-17 | | | | | | | Yes | +| CA_n29A-n66A | Rel-16 | | | | | | | | +| CA_n29A-n66B | Rel-16 | | | | | | | | +| CA_n29A-n66(2A) | Rel-16 | | | | | | | | +| CA_n29A-n70A | Rel-16 | | | | | | | | +| CA_n29A-n71A | Rel-17 | | | | | | | | +| CA_n39A-n41A | Rel-16 | | | | | | | | +| CA_n41A-n66A | Rel-17 | | | | | | | | +| CA_n41A-n71A | Rel-16 | | | | | | | Yes | +| CA_n41A-n79A | Rel-16 | | | | | | Not supported | Yes | +| CA_n41C-n79A | Rel-16 | | | | | | Not supported | Yes | +| CA_n48A-n66A (Note 6) | Rel-16 | | | | | | | | +| CA_n48A-n66(2A) (Note 6) | Rel-17 | | | | | | | | +| CA_n48A-n70A | Rel-17 | | | | | | | | +| CA_n48A-n71A | Rel-17 | | | | | | | | +| CA_n48A-n71(2A) | Rel-17 | | | | | | | | +| CA_n48A-n77A | Rel-17 | | | | | | | | +| CA_n48B-n66A | Rel-17 | | | | | | | | +| CA_n48B-n70A | Rel-17 | | | | | | | | +| CA_n48B-n71A | Rel-17 | | | | | | | | + +| | | | | | | | | | +|-----------------------------|--------|--|--|--|--|--|--|--| +| CA_n48(2A)-n66A | Rel-17 | | | | | | | | +| CA_n48(2A)-n66(2A) | Rel-17 | | | | | | | | +| CA_n48(2A)-n70A | Rel-17 | | | | | | | | +| CA_n48(2A)-n71A | Rel-17 | | | | | | | | +| CA_n48(2A)-n71(2A) | Rel-17 | | | | | | | | +| CA_n66A-n70A (Note 6) | Rel-16 | | | | | | | | +| CA_n66B-n70A (Note 6) | Rel-16 | | | | | | | | +| CA_n66(2A)-n70A (Note 6) | Rel-16 | | | | | | | | +| CA_n66A-n71A (Note 6) | Rel-16 | | | | | | | | +| CA_n66A-n71(2A) (Note 6) | Rel-17 | | | | | | | | +| CA_n66B-n71A (Note 6) | Rel-16 | | | | | | | | +| CA_n66(2A)-n71A (Note 6) | Rel-16 | | | | | | | | +| CA_n66(2A)-n71(2A) (Note 6) | Rel-17 | | | | | | | | +| CA_n66A-n77A | Rel-16 | | | | | | | | +| CA_n66A-n77(2A) | Rel-17 | | | | | | | | +| CA_n66A-n78A | Rel-17 | | | | | | | | +| CA_n66A-n78(2A) | Rel-17 | | | | | | | | +| CA_n66A-n77C | Rel-17 | | | | | | | | +| CA_n70A-n71A | Rel-16 | | | | | | | | +| CA_n70A-n71(2A) | Rel-17 | | | | | | | | +| CA_n71A-n77A | Rel-17 | | | | | | | | +| CA_n78A-n79A | Rel-15 | | | | | | | | + +| | | +|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Note 1: | Notation used for inter-band CA Bands is according to TS 38.101-1 [23] Table 5.5A.3.1-1, e.g. 'CA_n1A-n78C' indicates CA operation on NR band n1 and n78 with DL CA Bandwidth Class A and C respectively. | +| Note 2: | The UL CA capabilities as per Table A.4.3.2A.4.1-2 can be supported on a single or multiple CA Band(s). The UE supplier shall indicate all supported UL CA Bandwidth Class(es), in uplink of the supported CA Band(s), as per TS 38.101-1 [23] Table 5.5A.3.1-1. For this release of specification valid choices are 'N', 'nXA-nYA', 'nX(2A)', 'nXB' and 'nXC', where both nX and nY are the NR bands. For example, for CA_n1A-n77A, 'N' would mean only DL CA, 'n1A-n77A' would mean both DL and UL CA. | +| Note 3: | The UE supplier shall indicate the supported Bandwidth Combination Set(s) as per TS 38.101-1 [23] Table 5.5A.3.1-1. | +| Note 4: | Void. | +| Note 5: | See UL( table_index ) in in Note 1 of Table 4.0-3 and UL_nCC( table_index ) in Note 2 of Table 4.0-3 in TS 38.522 [9]. | +| Note 6: | A UE that supports NR Band n66 (Table A.4.3.1-1) and CA operation in any CA band shall also support the DL CA configurations CA_n66B and CA_n66(2A), as per Note 7, in Table 5.2-1, in TS 38.521-1 [5]. | +| Note 7: | The ULTxSwitching capability can be reported on inter-band CA band combinations. The UE supplier shall indicate inter-band CA band pairs on which it supports 1Tx-2Tx or 2Tx-2Tx ULTxSwitching. For this release of specification valid choices are 'N' and 'nX-nY', where both nX and nY are NR bands. For example, for CA_n1A-n77A, 'N' would mean not supporting ULTxSwitching, 'n1-n77' would mean supporting of ULTxSwitching on this band pair. If UE supplier indicates supporting of ULTxSwitching on a band pair, they shall indicate at least one inter-band UL CA configuration on the same band pair in the column "Supported CA Bandwidth Class(es) in UL". The ULTxSwitching is only tested with 2 UL CCs, so UE is allowed to report 'N' by default for CA configuration with > 2 component carriers. | +| Note 8: | See ULTxSwitching( table_index ) and 2Tx_ULTxSwitching( table_index ) in Note 6 of Table 4.0-3 in TS 38.522 [9]. | +| Note 9: | See DL_nCC( table_index ) in Note 4 of Table 4.0-3 in TS 38.522 [9]. | +| Note 10: | A UE that supports ULTxSwitching on a band pair might report the uplinkTxSwitching-DL-Interruption-r16 capability on the same band pair. If UE doesn't report this capability, no DL interruption is allowed during UL Tx switching. For certain band configurations DL interruption is not allowed according to Note 8 in Table 5.2A.2.1-1 of TS 38.101-1 [23], therefore the corresponding entry is prefilled by 'Not Supported'. | +| Note 11: | For configurations with Note 1 in Table 5.2A.2.1-1 of TS 38.521-1 [5], UE capability simultaneousRxBTxInterBandCA is mandatory, therefore the corresponding entry is prefilled with 'Yes'. | + +**Table A.4.3.2A.4.1-4: Inter-band CA within FR1 (two bands) PC2 UE RF Baseline Implementation Capabilities** + +| Item | CA configuration | Inter-band CA within FR1 (two bands) PC2 UE RF Baseline Implementation Capabilities | Ref. | Release | Mnemonic | Comments | +|------|------------------|-------------------------------------------------------------------------------------|-----------------------|---------|------------------------------------------------|----------| +| 1 | CA_n1A-n78A | n1 band: 1920-1980 MHz (UL), 2110-2170 MHz (DL)
n78 band: 3300-3800 MHz | 38.101-1,
6.2A.1.3 | Rel-17 | pc_UL_inter_band
_CA_n1A_n78A_
PC2_Supp | | +| A | CA_n2A-n77A | n2 band: 1850-1910 MHz (UL), 1930-1990 MHz (DL)
n77 band: 3300-4200 MHz | 38.101-1,
6.2A.1.3 | Rel-17 | pc_UL_inter_band
_CA_n2A_n77A_
PC2_Supp | | +| 1B | CA_n3A-n41A | n3 band: 1710-1785 MHz (UL), 1805-1880 MHz (DL)
n41 band: 2496-2690 MHz | 38.101-1,
6.2A.1.3 | Rel-17 | pc_UL_inter_band
_CA_n3A_n41A_
PC2_Supp | | +| 2 | CA_n3A-n78A | n3 band: 1710-1785 MHz (UL), 1805-1880 MHz (DL)
n78 band: 3300-3800 MHz | 38.101-1,
6.2A.1.3 | Rel-17 | pc_UL_inter_band
_CA_n3A_n78A_
PC2_Supp | | +| 2A | CA_n5A-n77A | n5 band: 824-849 MHz (UL), 869-894 MHz (DL)
n77 band: 3300-4200 MHz | 38.101-1,
6.2A.1.3 | Rel-17 | pc_UL_inter_band
_CA_n5A_n77A_
PC2_Supp | | +| 3 | CA_n28A-n41A | n28 band: 703-748 MHz (UL), 758-803 MHz (DL)
n41 band: 2496-2690 MHz | 38.101-1,
6.2A.1.3 | Rel-17 | pc_UL_inter_band
_CA_n28A_n41A_
PC2_Supp | | +| 4 | CA_n28A-n79A | n28 band: 703-748 MHz (UL), 758-803 MHz (DL)
n79 band: 4400-5000 MHz | 38.101-1,
6.2A.1.3 | Rel-17 | pc_UL_inter_band
_CA_n28A_n79A_
PC2_Supp | | +| 5 | CA_n41A-n79A | n41 band: 2496-2690 MHz
n79 band: 4400-5000 MHz | 38.101-1,
6.2A.1.3 | Rel-17 | pc_UL_inter_band
_CA_n41A_n79A_
PC2_Supp | | +| 6 | CA_n66A-n77A | n66 band: 1710-1780 MHz (UL), 2110-2200 MHz (DL)
n77 band: 3300-4200 MHz | 38.101-1,
6.2A.1.3 | Rel-17 | pc_UL_inter_band
_CA_n66A_n77A_
PC2_Supp | | +| 7 | CA_n78A-n79A | n78 band: 3300-3800 MHz
n79 band: 4400-5000 MHz | 38.101-1,
6.2A.1.3 | Rel-18 | pc_UL_inter_band
_CA_n78A_n79A_
PC2_Supp | | + +###### A.4.3.2A.4.2 NR Inter-band CA within FR1 (three bands) + +**Table A.4.3.2A.4.2-1: Downlink Bandwidth Class Combination capabilities for NR Inter-band CA configuration within FR1 and three bands (for one or more of the supported CA configurations in Table A.4.3.2A.4.2-3)** + +| Item | DL NR FR1 Inter-band CA Bandwidth Class | Ref. | Mnemonic | Comments | +|------|---------------------------------------------------------------------|------------------|------------------------------------------------------|----------| +| 1 | DL NR FR1 Inter-band CA BW Class Combination A-A-A (three bands) | 38.101-1, 5.3A.5 | pc_DL_inter_band_CA
_NR_FR1_3B_Class_A
-A-A | | +| 2 | DL NR FR1 Inter-band CA BW Class Combination A-A-(2A) (three bands) | 38.101-1, 5.3A.5 | pc_DL_inter_band_CA
_NR_FR1_3B_Class_A
-A-(2A) | | +| 3 | DL NR FR1 Inter-band CA BW Class Combination A-A-B (three bands) | 38.101-1, 5.3A.5 | pc_DL_inter_band_CA
_NR_FR1_3B_Class_A
-A-B | | +| 4 | DL NR FR1 Inter-band CA BW Class Combination A-(2A)-A (three bands) | 38.101-1, 5.3A.5 | pc_DL_inter_band_CA
_NR_FR1_3B_Class_A
-(2A)-A | | +| 5 | DL NR FR1 Inter-band CA BW Class Combination A-B-A (three bands) | 38.101-1, 5.3A.5 | pc_DL_inter_band_CA
_NR_FR1_3B_Class_A
-B-A | | +| 6 | DL NR FR1 Inter-band CA BW Class Combination A-C-A (three bands) | 38.101-1, 5.3A.5 | pc_DL_inter_band_CA
_NR_FR1_3B_Class_A
-C-A | | +| 7 | DL NR FR1 Inter-band CA BW Class Combination (2A)-A-A (three bands) | 38.101-1, 5.3A.5 | pc_DL_inter_band_CA
_NR_FR1_3B_Class_(
2A)-A-A | | +| 8 | DL NR FR1 Inter-band CA BW Class Combination B-A-A (three bands) | 38.101-1, 5.3A.5 | pc_DL_inter_band_CA
_NR_FR1_3B_Class_B
-A-A | | +| 9 | DL NR FR1 Inter-band CA BW Class Combination C-A-A (three bands) | 38.101-1, 5.3A.5 | pc_DL_inter_band_CA
_NR_FR1_3B_Class_C
-A-A | | + +**Table A.4.3.2A.4.2-2: Uplink Bandwidth Class Combination capabilities for NR Inter-band CA within FR1 and three bands (for one or more of the supported CA configurations in Table A.4.3.2A.4.2-3)** + +| Item | UL NR FR1 Inter-band CA Bandwidth Class | Ref. | Mnemonic | Comments | +|------|-----------------------------------------------------------------|------------------|--------------------------------------------------|----------| +| 1 | UL NR FR1 Inter-band CA BW Class Combination A-A (three bands) | 38.101-1, 5.3A.5 | pc_UL_inter_band
_CA_NR_FR1_3B
_Class_A-A | | +| 2 | UL NR FR1 Inter-band CA BW Class Combination (2A) (three bands) | 38.101-1, 5.3A.5 | pc_UL_inter_band
_CA_NR_FR1_3B
_Class_(2A) | | +| 3 | UL NR FR1 Inter-band CA BW Class Combination C (three bands) | 38.101-1, 5.3A.5 | pc_UL_inter_band
_CA_NR_FR1_3B
_Class_C | | + +**Table A.4.3.2A.4.2-3: Supported configurations for NR Inter-band CA within FR1 and three bands** + +| NR FR1 Inter-band CA configuration / Item (Note 1, 7) | Release | Supported | | | +|-------------------------------------------------------|---------|---------------------------------------------------|-------------------------------------------------|--| +| | | Supported CA Bandwidth Class(es) in UL (Note 2,5) | Supported Bandwidth Combination Set(s) (Note 3) | | +| CA_n1A-n3A-n28A | Rel-16 | | | | +| CA_n1A-n3A-n78A | Rel-16 | | | | +| CA_n1A-n28A-n78A | Rel-16 | | | | +| CA_n2A-n5A-n48A | Rel-17 | | | | +| CA_n2A-n5A-n77A | Rel-17 | | | | +| CA_n2A-n48A-n66A | Rel-17 | | | | +| CA_n3A-n28A-n78A | Rel-16 | | | | +| CA_n2A-n48A-n77A | Rel-17 | | | | +| CA_n2A-n66A-n77A | Rel-17 | | | | +| CA_n3A-n28A-n41A | Rel-17 | | | | +| CA_n3A-n28A-n77A | Rel-16 | | | | +| CA_n5A-n48A-n66A | Rel-17 | | | | +| CA_n5A-n48A-n77A | Rel-17 | | | | +| CA_n5A-n66A-n77A | Rel-17 | | | | +| CA_n25A-n66A-n77 | Rel-17 | | | | +| CA_n25A-n66A-n77(2A) | Rel-17 | | | | +| CA_n25A-n66A-n78 | Rel-17 | | | | +| CA_n25A-n66A-n78(2A) | Rel-17 | | | | +| CA_n26A-n66A-n70A | Rel-17 | | | | +| CA_n26A-n66(2A)-n70A | Rel-17 | | | | +| CA_n28A-n41A-n79A | Rel-17 | | | | +| CA_n29A-n66A-n70A | Rel-16 | | | | +| CA_n41A-n66A-n70A | Rel-16 | | | | +| CA_n48A-n66A-n70A | Rel-17 | | | | +| CA_n48A-n66A-n71A | Rel-17 | | | | +| CA_n48A-n66A-n71(2A) | Rel-17 | | | | +| CA_n48A-n66(2A)-n70A | Rel-17 | | | | +| CA_n48A-n66(2A)-n71A | Rel-17 | | | | +| CA_n48A-n70A-n71A | Rel-17 | | | | +| CA_n48A-n70A-n71(2A) | Rel-17 | | | | +| CA_n48B-n66A-n70A | Rel-17 | | | | +| CA_n48B-n66A-n71A | Rel-17 | | | | +| CA_n48B-n70A-n71A | Rel-17 | | | | +| CA_n48(2A)-n66A-n70A | Rel-17 | | | | +| CA_n48(2A)-n66A-n71A | Rel-17 | | | | +| CA_n48A-n66A-n77A | Rel-17 | | | | +| CA_n48(2A)-n70A-n71A | Rel-17 | | | | +| CA_n66A-n70A-n71A (Note 6) | Rel-16 | | | | +| CA_n66A-n70A-n71(2A) (Note 6) | Rel-17 | | | | +| CA_n66B-n70A-n71A (Note 6) | Rel-16 | | | | +| CA_n66(2A)-n70A-n71A (Note 6) | Rel-16 | | | | + +| | | +|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Note 1: | Notation used for inter-band CA Bands is according to TS 38.101-1 [23] Table 5.5A.3-2, e.g. 'CA_n66B-n70A-n71A' indicates CA operation on NR band n66, n70 and n71 with DL CA Bandwidth Class B, A and A respectively. | +| Note 2: | The UL CA capabilities as per Table A.4.3.2A.4.2-2 can be supported on a single or multiple CA Band(s). The UE supplier shall indicate all supported UL CA Bandwidth Class(es), in uplink of the supported CA Band(s), as per TS 38.101-1 [23] Table 5.5A.1-1. For this release of specification valid choices are 'N', 'nXA-nYA', 'nX(2A)' and 'nXC', where both nX and nY are the NR bands. For example, for CA_n66A-n70A-n71A, 'N' would mean only DL CA, 'n66A-n71A' would mean both DL and UL CA. | +| Note 3: | The UE supplier shall indicate the supported Bandwidth Combination Set(s) as per TS 38.101-1 [23] Table 5.5A.3-2. | +| Note 4: | Void. | +| Note 5: | See UL( table_index ) in Note 1 of Table 4.0-3 and UL_nCC( table_index ) in Note 2 of Table 4.0-3 in TS 38.522 [9]. | +| Note 6: | A UE that supports NR Band n66 (Table A.4.3.1-1) and CA operation in any CA band shall also support the DL CA configurations CA_n66B and CA_n66(2A), as per Note 7, in Table 5.2-1, in TS 38.521-1 [5]. | +| Note 7: | See DL_nCC( table_index ) in Note 4 of Table 4.0-3 in TS 38.522 [9]. | + +**Table A.4.3.2A.4.2-4: Inter-band CA within FR1 (three bands) PC2 UE RF Baseline Implementation Capabilities** + +| Item | CA configuration | Inter-band CA within FR1 (two bands) PC2 UE RF Baseline Implementation Capabilities | Ref. | Release | Mnemonic | Comments | +|------|------------------|--------------------------------------------------------------------------------------------------------------------------------|--------------------|---------|----------------------------------------|----------| +| 1 | CA_n2A-n5A-n77A | n2 band: 1850-1910 MHz (UL), 1930-1990 MHz (DL)
n5 band: 824-849 MHz (UL), 869-894 MHz (DL)
n77 band: 3300-4200 MHz | 38.101-1, 6.2A.1.3 | Rel-17 | pc_UL_inter_band_CA_n2A_n77A_PC2_Supp | | +| 2 | CA_n2A-n5A-n77A | n2 band: 1850-1910 MHz (UL), 1930-1990 MHz (DL)
n5 band: 824-849 MHz (UL), 869-894 MHz (DL)
n77 band: 3300-4200 MHz | 38.101-1, 6.2A.1.3 | Rel-17 | pc_UL_inter_band_CA_n5A_n77A_PC2_Supp | | +| 3 | CA_n2A-n66A-n77A | n2 band: 1850-1910 MHz (UL), 1930-1990 MHz (DL)
n66 band: 1710-1780 MHz (UL), 2110-2200 MHz (DL)
n77 band: 3300-4200 MHz | 38.101-1, 6.2A.1.3 | Rel-17 | pc_UL_inter_band_CA_n2A_n77A_PC2_Supp | | +| 4 | CA_n2A-n66A-n77A | n2 band: 1850-1910 MHz (UL), 1930-1990 MHz (DL)
n66 band: 1710-1780 MHz (UL), 2110-2200 MHz (DL)
n77 band: 3300-4200 MHz | 38.101-1, 6.2A.1.3 | Rel-17 | pc_UL_inter_band_CA_n66A_n77A_PC2_Supp | | +| 5 | CA_n5A-n66A-n77A | n5 band: 824-849 MHz (UL), 869-894 MHz (DL)
n66 band: 1710-1780 MHz (UL), 2110-2200 MHz (DL)
n77 band: 3300-4200 MHz | 38.101-1, 6.2A.1.3 | Rel-17 | pc_UL_inter_band_CA_n5A_n77A_PC2_Supp | | +| 6 | CA_n5A-n66A-n77A | n5 band: 824-849 MHz (UL), 869-894 MHz (DL)
n66 band: 1710-1780 MHz (UL), 2110-2200 MHz (DL)
n77 band: 3300-4200 MHz | 38.101-1, 6.2A.1.3 | Rel-17 | pc_UL_inter_band_CA_n66A_n77A_PC2_Supp | | + +###### A.4.3.2A.4.3 NR Inter-band CA within FR1 (four bands) + +**Table A.4.3.2A.4.3-1: Downlink Bandwidth Class Combination capabilities for NR Inter-band CA configuration within FR1 and four bands (for one or more of the supported CA configurations in Table A.4.3.2A.4.3-3)** + +| Item | DL NR FR1 Inter-band CA Bandwidth Class | Ref. | Mnemonic | Comments | +|------|-------------------------------------------------------------------|---------------------|-----------------------------------------------------|----------| +| 1 | DL NR FR1 Inter-band CA BW Class Combination A-A-A-A (four bands) | 38.101-1,
5.3A.5 | pc_DL_inter_band_CA
_NR_FR1_4B_Class_A
-A-A-A | | +| 2 | DL NR FR1 Inter-band CA BW Class Combination A-A-B-A (four bands) | 38.101-1,
5.3A.5 | pc_DL_inter_band_CA
_NR_FR1_4B_Class_A
-A-B-A | | +| 3 | DL NR FR1 Inter-band CA BW Class Combination A-B-A-A (four bands) | 38.101-1,
5.3A.5 | pc_DL_inter_band_CA
_NR_FR1_4B_Class_A
-B-A-A | | + +**Table A.4.3.2A.4.3-2: Uplink Bandwidth Class Combination capabilities for NR Inter-band CA within FR1 and four bands (for one or more of the supported CA configurations in Table A.4.3.2A.4.3-3)** + +| Item | UL NR FR1 Inter-band CA Bandwidth Class | Ref. | Mnemonic | Comments | +|------|---------------------------------------------------------------|---------------------|-------------------------------------------------|----------| +| 1 | UL NR FR1 Inter-band CA BW Class Combination A-A (four bands) | 38.101-1,
5.3A.5 | pc_UL_inter_band_CA
_NR_FR1_4B_Class_A
-A | | + +**Table A.4.3.2A.4.3-3: Supported configurations for NR Inter-band CA within FR1 and four bands** + +| NR FR1 Inter-band CA configuration / Item (Note 1, 7) | Release | Supported | Supported CA Bandwidth | Supported Bandwidth | +|-------------------------------------------------------|---------|-----------|----------------------------|-----------------------------| +| | | | Class(es) in UL (Note 2,5) | Combination Set(s) (Note 3) | +| CA_n1A-n3A-n28A-n78A | Rel-16 | | | | +| CA_n2A-n5A-n48A-n66A | Rel-17 | | | | +| CA_n2A-n5A-n48A-n77A | Rel-17 | | | | +| CA_n2A-n5A-n66A-n77A | Rel-17 | | | | +| CA_n2A-n48A-n66A-n77A | Rel-17 | | | | +| CA_n5A-n48A-n66A-n77A | Rel-17 | | | | + +Note 1: Notation used for inter-band CA Bands is according to TS 38.101-1 [23] Table 5.5A.3.3-1. + +Note 2: The UL CA capabilities as per Table A.4.3.2A.4.3-2 can be supported on a single or multiple CA Band(s). The UE supplier shall indicate all supported UL CA Bandwidth Class(es), in uplink of the supported CA Band(s), as per TS 38.101-1 [23] Table 5.5A.3.3-1. For this release of specification valid choices are 'N', 'nXA-nYA', 'nX(2A)' and 'nXC', where both nX and nY are the NR bands. For example, for CA\_nXA-nYA-nWA-nZA, 'N' would mean only DL CA, 'nXA-nYA' would mean both DL and UL CA. + +Note 3: The UE supplier shall indicate the supported Bandwidth Combination Set(s) as per TS 38.101-1 [23] Table 5.5A.3.3-1. + +Note 4: Void. + +Note 5: See UL(*table\_index*) in Note 1 of Table 4.0-3 and UL\_nCC(*table\_index*) in Note 2 of Table 4.0-3 in TS 38.522 [9]. + +Note 6: A UE that supports NR Band n66 (Table A.4.3.1-1) and CA operation in any CA band shall also comply with the minimum requirements specified for the DL CA configurations CA\_n66B and CA\_n66(2A) in the current version of the specification as per Note 7, in Table 5.2-1, in TS 38.521-1 [5]. + +Note 7: See DL\_nCC(*table\_index*) in Note 4 of Table 4.0-3 in TS 38.522 [9]. + +##### A.4.3.2A.5 NR Inter-band CA within FR2 + +###### A.4.3.2A.5.1 NR Inter-band CA within FR2 (two bands) + +**Table A.4.3.2A.5.1-1: Downlink Bandwidth Class Combination capabilities for NR Inter-band CA configuration within FR2 and two bands (for one or more of the supported CA configurations in Table A.4.3.2A.5.1-3)** + +| Item | DL NR FR2 Inter-band CA Bandwidth Class | Ref. | Mnemonic | Comments | +|------|--------------------------------------------------------------|------------------|-----------------------------------------|----------| +| 1 | DL NR FR2 Inter-band CA BW Class Combination A-A (two bands) | 38.101-2, 5.3A.4 | pc_DL_inter_band_CA_NR_FR2_2B_Class_A-A | | + +**Table A.4.3.2A.5.1-2: Uplink Bandwidth Class Combination capabilities for NR Inter-band CA within FR2 and two bands (for one or more of the supported CA configurations in Table A.4.3.2A.5.1-3)** + +| Item | UL NR FR2 Inter-band CA Bandwidth Class | Ref. | Mnemonic | Comments | +|------|--------------------------------------------------------------|------------------|-----------------------------------------|----------| +| 1 | UL NR FR2 Inter-band CA BW Class Combination A-A (two bands) | 38.101-2, 5.3A.4 | pc_UL_inter_band_CA_NR_FR2_2B_Class_A-A | | + +**Table A.4.3.2A.5.1-3: Supported configurations for NR Inter-band CA within FR2 and two bands** + +TBD + +##### A.4.3.2A.6 NR Inter-band CA between FR1 and FR2 + +###### A.4.3.2A.6.1 NR Inter-band CA between FR1 and FR2 (two bands) + +**Table A.4.3.2A.6.1-1: Downlink Bandwidth Class Combination capabilities for NR Inter-band CA configuration between FR1 and FR2 and two bands (for one or more of the supported CA configurations in Table A.4.3.2A.6.1-3)** + +| Item | DL NR FR1 and FR2 Inter-band CA Bandwidth Class | Ref. | Mnemonic | Comments | +|------|-------------------------------------------------------------------------|----------------------------------------------------------|------------------------------------------------|----------| +| 1 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-A (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_2B_Class_A-A | | +| 2 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-D (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_2B_Class_A-D | | +| 3 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-E (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_2B_Class_A-E | | +| 4 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-F (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_2B_Class_A-F | | +| 5 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-G (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_2B_Class_A-G | | +| 6 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-H (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_2B_Class_A-H | | +| 7 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-I (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_2B_Class_A-I | | +| 8 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-J (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_2B_Class_A-J | | +| 9 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-K (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_2B_Class_A-K | | +| 10 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-L (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_2B_Class_A-L | | +| 11 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-M (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_2B_Class_A-M | | +| 12 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-(2A) (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_2B_Class_A-(2A) | | +| 13 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-(3A) (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_2B_Class_A-(3A) | | +| 14 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-(4A) (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_2B_Class_A-(4A) | | +| 15 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-(5A) (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_2B_Class_A-(5A) | | +| 16 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-(6A) (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_2B_Class_A-(6A) | | +| 17 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-(7A) (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_2B_Class_A-(7A) | | +| 18 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-(8A) (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_2B_Class_A-(8A) | | +| 19 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-(2G) (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_2B_Class_A-(2G) | | + +| | | | | | +|----|----------------------------------------------------------------------------|----------------------------------------------------------|---------------------------------------------------|--| +| 20 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-(2H) (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_2B_Class_A-(2H) | | +| 21 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-(2I) (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_2B_Class_A-(2I) | | +| 22 | DL NR FR1 and FR2 Inter-band CA BW Class Combination (2A)-A (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_2B_Class_(2A)-A | | +| 23 | DL NR FR1 and FR2 Inter-band CA BW Class Combination (2A)-(2A) (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_2B_Class_(2A)-(2A) | | +| 24 | DL NR FR1 and FR2 Inter-band CA BW Class Combination (2A)-D (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_2B_Class_(2A)-D | | +| 25 | DL NR FR1 and FR2 Inter-band CA BW Class Combination (2A)-G (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_2B_Class_(2A)-G | | +| 26 | DL NR FR1 and FR2 Inter-band CA BW Class Combination (2A)-H (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_2B_Class_(2A)-H | | +| 27 | DL NR FR1 and FR2 Inter-band CA BW Class Combination (2A)-I (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_2B_Class_(2A)-I | | +| 28 | DL NR FR1 and FR2 Inter-band CA BW Class Combination (2A)-J (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_2B_Class_(2A)-J | | +| 29 | DL NR FR1 and FR2 Inter-band CA BW Class Combination (2A)-K (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_2B_Class_(2A)-K | | +| 30 | DL NR FR1 and FR2 Inter-band CA BW Class Combination (2A)-L (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_2B_Class_(2A)-L | | +| 31 | DL NR FR1 and FR2 Inter-band CA BW Class Combination (2A)-M (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_2B_Class_(2A)-M | | +| 32 | DL NR FR1 and FR2 Inter-band CA BW Class Combination C-A (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_2B_Class_C-A | | +| 33 | DL NR FR1 and FR2 Inter-band CA BW Class Combination C-(2A) (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_2B_Class_C-(2A) | | +| 34 | DL NR FR1 and FR2 Inter-band CA BW Class Combination C-D (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_2B_Class_C-D | | +| 35 | DL NR FR1 and FR2 Inter-band CA BW Class Combination C-E (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_2B_Class_C-E | | +| 36 | DL NR FR1 and FR2 Inter-band CA BW Class Combination C-F (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_2B_Class_C-F | | +| 37 | DL NR FR1 and FR2 Inter-band CA BW Class Combination G-H (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_2B_Class_G-H | | +| 38 | DL NR FR1 and FR2 Inter-band CA BW Class Combination G-I (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_2B_Class_G-I | | + +| | | | | | +|----|----------------------------------------------------------------------|----------------------------------------------------------|---------------------------------------------|--| +| 39 | DL NR FR1 and FR2 Inter-band CA BW Class Combination H-I (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_2B_Class_H-I | | +|----|----------------------------------------------------------------------|----------------------------------------------------------|---------------------------------------------|--| + +**Table A.4.3.2A.6.1-2: Uplink Bandwidth Class Combination capabilities for NR Inter-band CA between FR1 and FR2 and two bands (for one or more of the supported CA configurations in Table A.4.3.2A.6.1-3)** + +| Item | UL NR FR1 and FR2 Inter-band CA Bandwidth Class | Ref. | Mnemonic | Comments | +|------|----------------------------------------------------------------------|----------------------------------------------------------|---------------------------------------------|----------| +| 1 | UL NR FR1 and FR2 Inter-band CA BW Class Combination A-A (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_UL_inter_band_CA_NR_FR1_FR2_2B_Class_A-A | | +| 2 | UL NR FR1 and FR2 Inter-band CA BW Class Combination A-D (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_UL_inter_band_CA_NR_FR1_FR2_2B_Class_A-D | | +| 3 | UL NR FR1 and FR2 Inter-band CA BW Class Combination A-G (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_UL_inter_band_CA_NR_FR1_FR2_2B_Class_A-G | | +| 4 | UL NR FR1 and FR2 Inter-band CA BW Class Combination A-H (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_UL_inter_band_CA_NR_FR1_FR2_2B_Class_A-H | | +| 5 | UL NR FR1 and FR2 Inter-band CA BW Class Combination A-I (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_UL_inter_band_CA_NR_FR1_FR2_2B_Class_A-I | | +| 6 | UL NR FR1 and FR2 Inter-band CA BW Class Combination A-J (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_UL_inter_band_CA_NR_FR1_FR2_2B_Class_A-J | | +| 7 | UL NR FR1 and FR2 Inter-band CA BW Class Combination A-K (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_UL_inter_band_CA_NR_FR1_FR2_2B_Class_A-K | | +| 8 | UL NR FR1 and FR2 Inter-band CA BW Class Combination A-L (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_UL_inter_band_CA_NR_FR1_FR2_2B_Class_A-L | | +| 9 | UL NR FR1 and FR2 Inter-band CA BW Class Combination A-M (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_UL_inter_band_CA_NR_FR1_FR2_2B_Class_A-M | | +| 10 | UL NR FR1 and FR2 Inter-band CA BW Class Combination G (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_UL_inter_band_CA_NR_FR1_FR2_2B_Class_G | | +| 11 | UL NR FR1 and FR2 Inter-band CA BW Class Combination H (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_UL_inter_band_CA_NR_FR1_FR2_2B_Class_H | | +| 12 | UL NR FR1 and FR2 Inter-band CA BW Class Combination I (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_UL_inter_band_CA_NR_FR1_FR2_2B_Class_I | | +| 13 | UL NR FR1 and FR2 Inter-band CA BW Class Combination J (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_UL_inter_band_CA_NR_FR1_FR2_2B_Class_J | | +| 14 | UL NR FR1 and FR2 Inter-band CA BW Class Combination K (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_UL_inter_band_CA_NR_FR1_FR2_2B_Class_K | | +| 15 | UL NR FR1 and FR2 Inter-band CA BW Class Combination L (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_UL_inter_band_CA_NR_FR1_FR2_2B_Class_L | | +| 16 | UL NR FR1 and FR2 Inter-band CA BW Class Combination M (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_UL_inter_band_CA_NR_FR1_FR2_2B_Class_M | | + +**Table A.4.3.2A.6.1-3: Supported configurations for NR Inter-band CA between FR1 and FR2 and two bands** + +TBD + +###### A.4.3.2A.6.2 NR Inter-band CA between FR1 and FR2 (three bands) + +**Table A.4.3.2A.6.2-1: Downlink Bandwidth Class Combination capabilities for NR Inter-band CA configuration between FR1 and FR2 and three bands (for one or more of the supported CA configurations in Table A.4.3.2A.6.2-3)** + +| Item | DL NR FR1 and FR2 Inter-band CA Bandwidth Class | Ref. | Mnemonic | Comments | +|------|-----------------------------------------------------------------------------|----------------------------------------------------------|--------------------------------------------------|----------| +| 1 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-A-A (three bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_3B_Class_A-A-A | | +| 2 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-A-D (three bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_3B_Class_A-A-D | | +| 3 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-A-G (three bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_3B_Class_A-A-G | | +| 4 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-A-H (three bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_3B_Class_A-A-H | | +| 5 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-A-I (three bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_3B_Class_A-A-I | | +| 6 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-(2A)-A (three bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_3B_Class_A-(2A)-A | | +| 7 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-(2A)-D (three bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_3B_Class_A-(2A)-D | | +| 8 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-(2A)-G (three bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_3B_Class_A-(2A)-G | | +| 9 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-(2A)-H (three bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_3B_Class_A-(2A)-H | | +| 10 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-(2A)-I (three bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_NR_FR1_FR2_3B_Class_A-(2A)-I | | + +**Table A.4.3.2A.6.2-2: Uplink Bandwidth Class Combination capabilities for NR Inter-band CA between FR1 and FR2 and three bands (for one or more of the supported CA configurations in Table A.4.3.2A.6.2-3)** + +| Item | UL NR FR1 and FR2 Inter-band CA Bandwidth Class | Ref. | Mnemonic | Comments | +|------|------------------------------------------------------------------------|----------------------------------------------------------|-----------------------------------------------------|----------| +| 1 | UL NR FR1 and FR2 Inter-band CA BW Class Combination A-A (three bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_UL_inter_band_CA_
NR_FR1_FR2_3B_Clas
s_A-A | | +| 2 | UL NR FR1 and FR2 Inter-band CA BW Class Combination A-D (three bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_UL_inter_band_CA_
NR_FR1_FR2_3B_Clas
s_A-D | | +| 3 | UL NR FR1 and FR2 Inter-band CA BW Class Combination A-G (three bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_UL_inter_band_CA_
NR_FR1_FR2_3B_Clas
s_A-G | | +| 4 | UL NR FR1 and FR2 Inter-band CA BW Class Combination A-H (three bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_UL_inter_band_CA_
NR_FR1_FR2_3B_Clas
s_A-H | | +| 5 | UL NR FR1 and FR2 Inter-band CA BW Class Combination A-I (three bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_UL_inter_band_CA_
NR_FR1_FR2_3B_Clas
s_A-I | | + +**Table A.4.3.2A.6.2-3: Supported configurations for NR Inter-band CA between FR1 and FR2 and three bands** + +TBD + +###### A.4.3.2A.6.3 NR Inter-band CA between FR1 and FR2 (four bands) + +**Table A.4.3.2A.6.3-1: Downlink Bandwidth Class Combination capabilities for NR Inter-band CA configuration between FR1 and FR2 and four bands (for one or more of the supported CA configurations in Table A.4.3.2A.6.3-3)** + +| Item | DL NR FR1 and FR2 Inter-band CA Bandwidth Class | Ref. | Mnemonic | Comments | +|------|------------------------------------------------------------------------------|----------------------------------------------------------|------------------------------------------------------------|----------| +| 1 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-A-A-A (four bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_
NR_FR1_FR2_4B_Clas
s_A-A-A-A | | +| 2 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-A-A-D (four bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_
NR_FR1_FR2_4B_Clas
s_A-A-A-D | | +| 3 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-A-A-G (four bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_
NR_FR1_FR2_4B_Clas
s_A-A-A-G | | +| 4 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-A-A-H (four bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_
NR_FR1_FR2_4B_Clas
s_A-A-A-H | | +| 5 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-A-A-I (four bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_
NR_FR1_FR2_4B_Clas
s_A-A-A-I | | +| 6 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-A-(2A)-A (four bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_
NR_FR1_FR2_4B_Clas
s_A-A-(2A)-A | | +| 7 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-A-(2A)-D (four bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_
NR_FR1_FR2_4B_Clas
s_A-A-(2A)-D | | +| 8 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-A-(2A)-G (four bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_
NR_FR1_FR2_4B_Clas
s_A-A-(2A)-G | | +| 9 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-A-(2A)-H (four bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_
NR_FR1_FR2_4B_Clas
s_A-A-(2A)-H | | +| 10 | DL NR FR1 and FR2 Inter-band CA BW Class Combination A-A-(2A)-I (four bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_DL_inter_band_CA_
NR_FR1_FR2_4B_Clas
s_A-A-(2A)-I | | + +**Table A.4.3.2A.6.3-2: Uplink Bandwidth Class Combination capabilities for NR Inter-band CA between FR1 and FR2 and four bands (for one or more of the supported CA configurations in Table A.4.3.2A.6.3-3)** + +| Item | UL NR FR1 and FR2 Inter-band CA Bandwidth Class | Ref. | Mnemonic | Comments | +|------|-----------------------------------------------------------------------|----------------------------------------------------------|-----------------------------------------------------|-----------------------------------------------------------------| +| 1 | UL NR FR1 and FR2 Inter-band CA BW Class Combination A-A (four bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5A.1 | pc_UL_inter_band_CA_
NR_FR1_FR2_4B_Clas
s_A-A | Not used in any valid CA configurations in TS 38.101-3 [25] yet | + +**Table A.4.3.2A.6.3-3: Supported configurations for NR Inter-band CA between FR1 and FR2 and four bands** + +TBD + +#### A.4.3.2B NR-DC, EN-DC and NE-DC Physical Layer Baseline Implementation Capabilities + +NOTE: See Annex B for status of completed NR-DC, EN-DC and NE-DC configurations and power classes in this version of 3GPP UE conformance test specifications. + +##### A.4.3.2B.1 NR-DC Physical Layer Baseline Implementation Capabilities + +###### A.4.3.2B.1.0 General NR-DC capabilities + +**Table A.4.3.2B.1.0-1: Downlink NR-DC capabilities (for one or more of the supported NR-DC configurations)** + +| Item | Bandwidth Class | Ref. | Mnemonic | Comments | +|------|---------------------------|----------------|------------------|----------| +| 1 | DL NR-DC with 2 carriers | 38.101-3, 5.5B | pc_DL_NR_DC_2CC | | +| 2 | DL NR-DC with 3 carriers | 38.101-3, 5.5B | pc_DL_NR_DC_3CC | | +| 3 | DL NR-DC with 4 carriers | 38.101-3, 5.5B | pc_DL_NR_DC_4CC | | +| 4 | DL NR-DC with 5 carriers | 38.101-3, 5.5B | pc_DL_NR_DC_5CC | | +| 5 | DL NR-DC with 6 carriers | 38.101-3, 5.5B | pc_DL_NR_DC_6CC | | +| 6 | DL NR-DC with 7 carriers | 38.101-3, 5.5B | pc_DL_NR_DC_7CC | | +| 7 | DL NR-DC with 8 carriers | 38.101-3, 5.5B | pc_DL_NR_DC_8CC | | +| 8 | DL NR-DC with 9 carriers | 38.101-3, 5.5B | pc_DL_NR_DC_9CC | | +| 9 | DL NR-DC with 10 carriers | 38.101-3, 5.5B | pc_DL_NR_DC_10CC | | + +**Table A.4.3.2B.1.0-2: Uplink NR-DC capabilities (for one or more of the supported NR-DC configurations)** + +| Item | Bandwidth Class | Ref. | Mnemonic | Comments | +|------|---------------------------|----------------|------------------|----------| +| 1 | UL NR-DC with 2 carriers | 38.101-3, 5.5B | pc_UL_NR_DC_2CC | | +| 2 | UL NR-DC with 3 carriers | 38.101-3, 5.5B | pc_UL_NR_DC_3CC | | +| 3 | UL NR-DC with 4 carriers | 38.101-3, 5.5B | pc_UL_NR_DC_4CC | | +| 4 | UL NR-DC with 5 carriers | 38.101-3, 5.5B | pc_UL_NR_DC_5CC | | +| 5 | UL NR-DC with 6 carriers | 38.101-3, 5.5B | pc_UL_NR_DC_6CC | | +| 6 | UL NR-DC with 7 carriers | 38.101-3, 5.5B | pc_UL_NR_DC_7CC | | +| 7 | UL NR-DC with 8 carriers | 38.101-3, 5.5B | pc_UL_NR_DC_8CC | | +| 8 | UL NR-DC with 9 carriers | 38.101-3, 5.5B | pc_UL_NR_DC_9CC | | +| 9 | UL NR-DC with 10 carriers | 38.101-3, 5.5B | pc_UL_NR_DC_10CC | | + +###### A.4.3.2B.1.0a NR-DC within FR1 + +###### A.4.3.2B.1.0a.1 NR-DC within FR1 (two bands) + +**Table A.4.3.2B.1.0a.1-1: Downlink NR-DC Bandwidth Class Combination capabilities within FR1 and two bands (for one or more of the supported DC configurations in Table A.4.3.2B.1.0a.1-3)** + +| Item | DL NR-DC FR1 Bandwidth Class (two bands) | Ref. | Mnemonic | Comments | +|------|---------------------------------------------------|----------------|------------------------------|----------| +| 1 | DL NR-DC FR1 BW Class Combination A-A (two bands) | 38.101-1, 5.5B | pc_DL_NR_DC_FR1_2B_Class_A-A | | + +**Table A.4.3.2B.1.0a.1-2: Uplink NR-DC Bandwidth Class Combination capabilities within FR1 and two bands (for one or more of the supported DC configurations in Table A.4.3.2B.1.0a.1-3)** + +| Item | UL NR-DC FR1 Bandwidth Class (two bands) | Ref. | Mnemonic | Comments | +|------|---------------------------------------------------|----------------|------------------------------|----------| +| 1 | UL NR-DC FR1 BW Class Combination A-A (two bands) | 38.101-1, 5.5B | pc_UL_NR_DC_FR1_2B_Class_A-A | | + +**Table A.4.3.2B.1.0a.1-3: Supported NR-DC configurations within FR1 (two bands)** + +| NR FR1 Inter-band NR-DC configuration / Item (Note 1, 6) | Release | Supported | Supported NR-DC Bandwidth Class(es) in UL (Note 2,3) | Supported Bandwidth Combination Set(s) | Supported ULTxSwitching Band Pair (Note 4, 5) | +|----------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|------------------------------------------------------|----------------------------------------|-----------------------------------------------| +| DC_n48A_n70A | Rel-17 | | | | | +| Note 1: | Notation used for inter-band NR-DC Bands is according to TS 38.101-1 [23] Table 5.5B.1-1, e.g. 'DC_n2A-n48C' indicates NR-DC operation on NR band n2 and n48 with DL CA Bandwidth Class A and C respectively. | | | | | +| Note 2: | The UL NR-DC capabilities as per Table A.4.3.2B.1.0a.1-2 can be supported on a single or multiple CA Band(s). The UE supplier shall indicate all supported UL NR-DC Bandwidth Class(es), in uplink of the supported NR-DC Band(s), as per TS 38.101-1 [23] Table 5.5B.1-1. For this release of specification valid choices are 'N', 'nXA-nYA', 'nX(2A)', 'nXB' and 'nXC', where both nX and nY are the NR bands. For example, for DC_n48A-n70A, 'N' would mean only DL NR-DC, 'n48A-n70A' would mean both DL and UL NR-DC. | | | | | +| Note 3: | See UL( table_index ) in Note 1 of Table 4.0-3 and UL_nCC( table_index ) in Note 2 of Table 4.0-3 in TS 38.522 [9]. | | | | | +| Note 4: | The ULTxSwitching capability can be reported on inter-band NR-DC band combinations. The UE supplier shall indicate inter-band NR-DC band pairs on which it supports ULTxSwitching. For this release of specification valid choices are 'N' and 'nX-nY', where both nX and nY are NR bands. For example, for DC_n48A-n70A, 'N' would mean not supporting ULTxSwitching, 'n48-n70' would mean supporting of ULTxSwitching on this band pair. If UE supplier indicates supporting of ULTxSwitching on a band pair, they shall indicate at least one inter-band UL NR-DC configuration on the same band pair in the column "Supported NR-DC Bandwidth Class(es) in UL". The ULTxSwitching is only tested with 2 UL CCs, so UE is allowed to report 'N' by default for NR-DC configuration with > 2 component carriers. | | | | | +| Note 5: | See ULTxSwitching( table_index ) Note 6 of Table 4.0-3 in TS 38.522 [9]. | | | | | +| Note 6: | See DL_nCC( table_index ) in Note 4 of Table 4.0-3 in TS 38.522 [9]. | | | | | + +###### A.4.3.2B.1.0b NR-DC within FR2 + +TBD + +###### A.4.3.2B.1.1 NR-DC between FR1 and FR2 + +###### A.4.3.2B.1.1.1 NR-DC between FR1 and FR2 (two bands) + +**Table A.4.3.2B.1.1.1-1: Downlink NR-DC Bandwidth Class Combination capabilities between FR1 and FR2 and two bands (for one or more of the supported DC configurations in Table A.4.3.2B.1.1.1-2)** + +| Item | DL NR-DC between FR1 and FR2
Bandwidth Class
(two bands) | Ref. | Mnemonic | Comments | +|------|-----------------------------------------------------------------|-----------------------------------------------------------|---------------------------------------------|----------| +| 1 | DL NR-DC FR1 and FR2 BW Class
Combination A-A (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5B.7 | pc_DL_NR_DC_F
R1_FR2_2B_Clas
s_A-A | | +| 2 | DL NR-DC FR1 and FR2 BW Class
Combination A-(2A) (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5B.7 | pc_DL_NR_DC_F
R1_FR2_2B_Clas
s_A-(2A) | | +| 3 | DL NR-DC FR1 and FR2 BW Class
Combination A-(3A) (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5B.7 | pc_DL_NR_DC_F
R1_FR2_2B_Clas
s_A-(3A) | | +| 4 | DL NR-DC FR1 and FR2 BW Class
Combination A-(4A) (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5B.7 | pc_DL_NR_DC_F
R1_FR2_2B_Clas
s_A-(4A) | | +| 5 | DL NR-DC FR1 AND FR2 BW Class
Combination A-D (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5B.7 | pc_DL_NR_DC_F
R1_FR2_2B_Clas
s_A-D | | +| 6 | DL NR-DC FR1 AND FR2 BW Class
Combination A-E (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5. 5B.7 | pc_DL_NR_DC_F
R1_FR2_2B_Clas
s_A-E | | +| 7 | DL NR-DC FR1 AND FR2 BW Class
Combination A-F (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5. 5B.7 | pc_DL_NR_DC_F
R1_FR2_2B_Clas
s_A-F | | +| 8 | DL NR-DC FR1 AND FR2 BW Class
Combination A-G (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5. 5B.7 | pc_DL_NR_DC_F
R1_FR2_2B_Clas
s_A-G | | +| 9 | DL NR-DC FR1 AND FR2 BW Class
Combination A-(2G) (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5. 5B.7 | pc_DL_NR_DC_F
R1_FR2_2B_Clas
s_A-(2G) | | +| 10 | DL NR-DC FR1 AND FR2 BW Class
Combination A-H (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5. 5B.7 | pc_DL_NR_DC_F
R1_FR2_2B_Clas
s_A-H | | +| 11 | DL NR-DC FR1 AND FR2 BW Class
Combination A-I (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5. 5B.7 | pc_DL_NR_DC_F
R1_FR2_2B_Clas
s_A-I | | +| 12 | DL NR-DC FR1 AND FR2 BW Class
Combination A-(2I) (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5. 5B.7 | pc_DL_NR_DC_F
R1_FR2_2B_Clas
s_A-(2I) | | +| 13 | DL NR-DC FR1 AND FR2 BW Class
Combination A-J (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5. 5B.7 | pc_DL_NR_DC_F
R1_FR2_2B_Clas
s_A-J | | +| 14 | DL NR-DC FR1 AND FR2 BW Class
Combination A-K (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5. 5B.7 | pc_DL_NR_DC_F
R1_FR2_2B_Clas
s_A-K | | +| 15 | DL NR-DC FR1 AND FR2 BW Class
Combination A-L (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5. 5B.7 | pc_DL_NR_DC_F
R1_FR2_2B_Clas
s_A-L | | +| 16 | DL NR-DC FR1 AND FR2 BW Class
Combination A-M (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5. 5B.7 | pc_DL_NR_DC_F
R1_FR2_2B_Clas
s_A-M | | +| 17 | DL NR-DC FR1 AND FR2 BW Class
Combination (2A)-A (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5. 5B.7 | pc_DL_NR_DC_F
R1_FR2_2B_Clas
s_(2A)-A | | +| 18 | DL NR-DC FR1 AND FR2 BW Class
Combination (2A)-G (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5. 5B.7 | pc_DL_NR_DC_F
R1_FR2_2B_Clas
s_(2A)-G | | + +| | | | | | +|----|--------------------------------------------------------------|----------------------------------------------------------|---------------------------------------------|--| +| 19 | DL NR-DC FR1 AND FR2 BW Class Combination (2A)-H (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5B.7 | pc_DL_NR_DC_F
R1_FR2_2B_Clas
s_(2A)-H | | +| 20 | DL NR-DC FR1 AND FR2 BW Class Combination (2A)-I (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5B.7 | pc_DL_NR_DC_F
R1_FR2_2B_Clas
s_(2A)-I | | +| 21 | DL NR-DC FR1 AND FR2 BW Class Combination (2A)-J (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5B.7 | pc_DL_NR_DC_F
R1_FR2_2B_Clas
s_(2A)-J | | +| 22 | DL NR-DC FR1 AND FR2 BW Class Combination (2A)-K (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5B.7 | pc_DL_NR_DC_F
R1_FR2_2B_Clas
s_(2A)-K | | +| 23 | DL NR-DC FR1 AND FR2 BW Class Combination (2A)-L (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5B.7 | pc_DL_NR_DC_F
R1_FR2_2B_Clas
s_(2A)-L | | +| 24 | DL NR-DC FR1 AND FR2 BW Class Combination (2A)-M (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5B.7 | pc_DL_NR_DC_F
R1_FR2_2B_Clas
s_(2A)-M | | +| 25 | DL NR-DC FR1 AND FR2 BW Class Combination C-A (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5B.7 | pc_DL_NR_DC_F
R1_FR2_2B_Clas
s_C-A | | +| 26 | DL NR-DC FR1 AND FR2 BW Class Combination C-D (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5B.7 | pc_DL_NR_DC_F
R1_FR2_2B_Clas
s_C-D | | +| 27 | DL NR-DC FR1 AND FR2 BW Class Combination C-E (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5B.7 | pc_DL_NR_DC_F
R1_FR2_2B_Clas
s_C-E | | +| 28 | DL NR-DC FR1 AND FR2 BW Class Combination C-F (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5B.7 | pc_DL_NR_DC_F
R1_FR2_2B_Clas
s_C-F | | + +**Table A.4.3.2B.1.1.1-1a: Uplink NR-DC Bandwidth Class Combination capabilities between FR1 and FR2 and two bands (for one or more of the supported DC configurations in Table A.4.3.2B.1.1.1-2)** + +| Item | UL NR-DC between FR1 and FR2 Bandwidth Class (two bands) | Ref. | Mnemonic | Comments | +|------|-----------------------------------------------------------|----------------------------------------------------------|------------------------------------------|----------| +| 1 | UL NR-DC FR1 and FR2 BW Class Combination A-A (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5B.7 | pc_UL_NR_DC_F
R1_FR2_2B_Clas
s_A-A | | +| 2 | UL NR-DC FR1 and FR2 BW Class Combination A-D (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5B.7 | pc_UL_NR_DC_F
R1_FR2_2B_Clas
s_A-D | | +| 3 | UL NR-DC FR1 and FR2 BW Class Combination A-G (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5B.7 | pc_UL_NR_DC_F
R1_FR2_2B_Clas
s_A-G | | +| 4 | UL NR-DC FR1 and FR2 BW Class Combination A-H (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5B.7 | pc_UL_NR_DC_F
R1_FR2_2B_Clas
s_A-H | | +| 5 | UL NR-DC FR1 and FR2 BW Class Combination A-I (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5B.7 | pc_UL_NR_DC_F
R1_FR2_2B_Clas
s_A-I | | +| 6 | UL NR-DC FR1 and FR2 BW Class Combination A-J (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5B.7 | pc_UL_NR_DC_F
R1_FR2_2B_Clas
s_A-J | | +| 7 | UL NR-DC FR1 and FR2 BW Class Combination A-K (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5B.7 | pc_UL_NR_DC_F
R1_FR2_2B_Clas
s_A-K | | +| 8 | UL NR-DC FR1 and FR2 BW Class Combination A-L (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5B.7 | pc_UL_NR_DC_F
R1_FR2_2B_Clas
s_A-L | | +| 9 | UL NR-DC FR1 and FR2 BW Class Combination A-M (two bands) | 38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3, 5.5B.7 | pc_UL_NR_DC_F
R1_FR2_2B_Clas
s_A-M | | + +**Table A.4.3.2B.1.1.1-2: Supported NR-DC configurations between FR1 and FR2 (two bands)** + +| NR-DC configuration / Item (Note 1) | Release | Supported | Supported DC Bandwidth Class(es) in UL | Supported Bandwidth Combination Set(s) | +|-------------------------------------|---------|-----------|----------------------------------------|----------------------------------------| +| DC_n78A-n257A | Rel-15 | | | | +| DC_n78A-n257G | Rel-15 | | | | +| DC_n78A-n257H | Rel-15 | | | | +| DC_n78A-n257I | Rel-15 | | | | +| DC_n79A-n257A | Rel-15 | | | | +| DC_n79A-n257G | Rel-15 | | | | +| DC_n79A-n257H | Rel-15 | | | | +| DC_n79A-n257I | Rel-15 | | | | + +Note 1: Notation used NR-DC Bands is according to TS 38.101-3 [25] Table 5.5B.7-1, e.g. 'DC\_n78A-n257G' indicates NR-DC operation on NR bands n78 and n257 with DL CA Bandwidth Class A and G respectively. + +##### A.4.3.2B.2 EN-DC Physical Layer + +###### Baseline Implementation Capabilities + +###### A.4.3.2B.2.0 General EN-DC capabilities + +**Table A.4.3.2B.2.0-1: Downlink EN-DC capabilities (for one or more of the supported EN-DC configurations)** + +| Item | Bandwidth Class | Ref. | Mnemonic | Comments | +|------|--------------------------|----------------|-----------------|----------| +| 1 | DL EN-DC with 2 carriers | 38.101-3, 5.5B | pc_DL_EN_DC_2CC | | +| 2 | DL EN-DC with 3 carriers | 38.101-3, 5.5B | pc_DL_EN_DC_3CC | | +| 3 | DL EN-DC with 4 carriers | 38.101-3, 5.5B | pc_DL_EN_DC_4CC | | +| 4 | DL EN-DC with 5 carriers | 38.101-3, 5.5B | pc_DL_EN_DC_5CC | | +| 5 | DL EN-DC with 6 carriers | 38.101-3, 5.5B | pc_DL_EN_DC_6CC | | +| 6 | DL EN-DC with 7 carriers | 38.101-3, 5.5B | pc_DL_EN_DC_7CC | | +| 7 | DL EN-DC with 8 carriers | 38.101-3, 5.5B | pc_DL_EN_DC_8CC | | + +**Table A.4.3.2B.2.0-1A: Downlink EN-DC capabilities (number of NR DL carriers)** + +| Item | Bandwidth Class | Ref. | Mnemonic | Comments | +|------|--------------------------------|----------------|------------------------|----------| +| 1 | DL EN-DC with 1 NR DL carriers | 38.101-3, 5.5B | pc_EN_DC_N
R_DL_1CC | | +| 2 | DL EN-DC with 2 NR DL carriers | 38.101-3, 5.5B | pc_EN_DC_N
R_DL_2CC | | +| 3 | DL EN-DC with 3 NR DL carriers | 38.101-3, 5.5B | pc_EN_DC_N
R_DL_3CC | | +| 4 | DL EN-DC with 4 NR DL carriers | 38.101-3, 5.5B | pc_EN_DC_N
R_DL_4CC | | +| 5 | DL EN-DC with 5 NR DL carriers | 38.101-3, 5.5B | pc_EN_DC_N
R_DL_5CC | | +| 6 | DL EN-DC with 6 NR DL carriers | 38.101-3, 5.5B | pc_EN_DC_N
R_DL_6CC | | +| 7 | DL EN-DC with 7 NR DL carriers | 38.101-3, 5.5B | pc_EN_DC_N
R_DL_7CC | | +| 8 | EN-DC with 8 NR DL carriers | 38.101-3, 5.5B | pc_EN_DC_N
R_DL_8CC | | + +**Table A.4.3.2B.2.0-2: Uplink EN-DC capabilities (for one or more of the supported EN-DC configurations)** + +| Item | Bandwidth Class | Ref. | Mnemonic | Comments | +|------|--------------------------|----------------|-----------------|----------| +| 1 | UL EN-DC with 2 carriers | 38.101-3, 5.5B | pc_UL_EN_DC_2CC | | +| 2 | UL EN-DC with 3 carriers | 38.101-3, 5.5B | pc_UL_EN_DC_3CC | | +| 3 | UL EN-DC with 4 carriers | 38.101-3, 5.5B | pc_UL_EN_DC_4CC | | +| 4 | UL EN-DC with 5 carriers | 38.101-3, 5.5B | pc_UL_EN_DC_5CC | | +| 5 | UL EN-DC with 6 carriers | 38.101-3, 5.5B | pc_UL_EN_DC_6CC | | +| 6 | UL EN-DC with 7 carriers | 38.101-3, 5.5B | pc_UL_EN_DC_7CC | | +| 7 | UL EN-DC with 8 carriers | 38.101-3, 5.5B | pc_UL_EN_DC_8CC | | + +**Table A.4.3.2B.2.0-2A: Uplink EN-DC capabilities (number of NR UL carriers)** + +| Item | Bandwidth Class | Ref. | Mnemonic | Comments | +|------|--------------------------------|----------------|--------------------|----------| +| 1 | UL EN-DC with 1 NR UL carriers | 38.101-3, 5.5B | pc_EN_DC_NR_UL_1CC | | +| 2 | UL EN-DC with 2 NR UL carriers | 38.101-3, 5.5B | pc_EN_DC_NR_UL_2CC | | +| 3 | UL EN-DC with 3 NR UL carriers | 38.101-3, 5.5B | pc_EN_DC_NR_UL_3CC | | +| 4 | UL EN-DC with 4 NR UL carriers | 38.101-3, 5.5B | pc_EN_DC_NR_UL_4CC | | +| 5 | UL EN-DC with 5 NR UL carriers | 38.101-3, 5.5B | pc_EN_DC_NR_UL_5CC | | +| 6 | UL EN-DC with 6 NR UL carriers | 38.101-3, 5.5B | pc_EN_DC_NR_UL_6CC | | +| 7 | UL EN-DC with 7 NR UL carriers | 38.101-3, 5.5B | pc_EN_DC_NR_UL_7CC | | +| 8 | EN-DC with 8 NR UL carriers | 38.101-3, 5.5B | pc_EN_DC_NR_UL_8CC | | + +###### A.4.3.2B.2.1 Intra-band contiguous EN-DC + +**Table A.4.3.2B.2.1-1: Downlink Bandwidth Class Combination capabilities for Intra-band contiguous EN-DC configurations (for one or more of the supported configurations in Table A.4.3.2B.2.1-2)** + +| Item | DL Intra-band contiguous EN-DC Bandwidth Class | Ref. | Mnemonic | Comments | +|------|--------------------------------------------------------|-----------------------------------------|---------------------------------------|----------| +| 1 | DL Intra-band contiguous EN-DC BW Class Combination AA | 36.101, 5.6A.1
38.101-3,
5.3B.1.2 | pc_DL_intra_contiguous_EN_DC_Class_AA | | +| 2 | DL Intra-band contiguous EN-DC BW Class Combination CA | 36.101, 5.6A.1
38.101-3,
5.3B.1.2 | pc_DL_intra_contiguous_EN_DC_Class_CA | | +| 3 | DL Intra-band contiguous EN-DC BW Class Combination DA | 36.101, 5.6A.1
38.101-3,
5.3B.1.2 | pc_DL_intra_contiguous_EN_DC_Class_DA | | + +**Table A.4.3.2B.2.1-1a: Uplink Bandwidth Class Combination capabilities for Intra-band contiguous EN-DC configurations (for one or more of the supported configurations in Table A.4.3.2B.2.1-2)** + +| Item | UL Intra-band contiguous EN-DC Bandwidth Class | Ref. | Mnemonic | Comments | +|------|---------------------------------------------------------|-----------------------------------------|----------------------------------------|----------| +| 1 | UL Intra-band contiguous EN-DC BW Class Combination AA | 36.101, 5.6A.1
38.101-3,
5.3B.1.2 | pc_UL_intra_contiguous_EN_DC_Class_AA | | +| 2 | UL Intra-band contiguous EN-DC BW Class Combination A_A | 36.101, 5.6A.1
38.101-3,
5.3B.1.2 | pc_UL_intra_contiguous_EN_DC_Class_A_A | | + +**Table A.4.3.2B.2.1-2: Supported Intra-band contiguous EN-DC configurations** + +| EN-DC configuration / Item
(Note 1, 3) | Release | Supported | Supported EN-DC Bandwidth Class(es) in UL
(Note 2) | Supported Bandwidth Combination Set(s) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-----------|-------------------------------------------------------|----------------------------------------| +| DC_(n)41AA | Rel-15 | | | | +| DC_(n)71AA | Rel-15 | | | | +| Note 1: Notation used for intra-band contiguous EN-DC Bands is according to TS 38.101-3 [25] Table 5.3B.1.2-1, e.g. 'DC_(n)41AA' indicates contiguous EN-DC operation on E-UTRA band 41 with DL Bandwidth Class A and NR band n41 with DL CA Bandwidth Class A. | | | | | +| Note 2: See UL_nCC( table_index ) in Note 2 of Table 4.0-3 in TS 38.522 [9]. | | | | | +| Note 3: See DL_nCC( table_index ) in Note 4 of Table 4.0-3 in TS 38.522 [9]. | | | | | + +**Table A.4.3.2B.2.1-3: Intra-band contiguous EN-DC PC2 UE RF Baseline Implementation Capabilities** + +| Item | Intra-band contiguous EN-DC PC2 UE RF Baseline Implementation Capabilities | Ref. | Release | Mnemonic | Comments | +|------|----------------------------------------------------------------------------|-----------------------|---------|-------------------------------|------------| +| 1 | LTE Frequency band: 2496-2690 MHz
NR Frequency band: 2496-2690 MHz | 38.101-3,
6.2B.1.1 | Rel-15 | pc_Band41_nrBand41_C_PC2_Supp | DC_(n)41AA | + +**Table A.4.3.2B.2.1-4: Intra-band contiguous EN-DC NR part power class UE RF Baseline Implementation Capabilities (Rel-16 and forward)** + +| Item | EN-DC configuration | UE Physical Layer Baseline Implementation Capabilities | Ref. | Release | Mnemonic | Supported NR part power class | +|------|---------------------|--------------------------------------------------------|--------------------|---------|-------------------------------------------|-------------------------------| +| 1 | DC_(n)41AA | DC_(n)41AA NR part power class | 38.306,
4.2.7.1 | Rel-16 | pc_Band41_nrBand41_C_powerClassNRPart_r16 | | + +**Table A.4.3.2B.2.1-4a: Intra-band contiguous EN-DC maxNumberSRS-Ports-PerResource UE RF Baseline Implementation Capabilities (Rel-15)** + +| Item | EN-DC configuration | UE Physical Layer Baseline Implementation Capabilities | Ref. | Release | Mnemonic | Supported maxNumberSRS-Ports-PerResource | +|------|---------------------|--------------------------------------------------------|-----------------|---------|------------------------------------------------------------|------------------------------------------| +| 1 | DC_(n)41AA | DC_(n)41AA maxNumberSRS-Ports-PerResource on NR band | 38.306, 4.2.7.7 | Rel-15 | pc_Band41_nrBand41_C_maxNumberSRS-Ports-PerResource_NR_r15 | | + +**Table A.4.3.2B.2.1-4b: Intra-band contiguous EN-DC NR part power class UE RF Baseline Implementation Capabilities (Rel-15) (maxNumberSRS-Ports-PerResource=n2 in NR standalone operation mode, maxNumberSRS-Ports-PerResource=n1 for EN-DC on NR band)** + +| Item | EN-DC configuration | UE Physical Layer Baseline Implementation Capabilities | Ref. | Release | Mnemonic | Supported NR part power class | +|------|---------------------|--------------------------------------------------------|---------------|---------|-------------------------------------------|-------------------------------| +| 1 | DC_(n)41AA | DC_(n)41AA NR part power class | 38.101-3, 6.1 | Rel-15 | pc_Band41_nrBand41_C_powerClassNRPart_r15 | | + +###### A.4.3.2B.2.2 Intra-band non-contiguous EN-DC + +**Table A.4.3.2B.2.2-1: Downlink Bandwidth Class Combination capabilities for Intra-band non-contiguous EN-DC configurations (for one or more of the supported configurations in Table A.4.3.2B.2.2-2)** + +| Item | DL Intra-band non-contiguous EN-DC Bandwidth Class | Ref. | Mnemonic | Comments | +|------|---------------------------------------------------------------|--------------------------------------|----------------------------------------------|----------| +| 1 | DL Intra-band non-contiguous EN-DC BW Class Combination A_A | 36.101, 5.6A.1
38.101-3, 5.3B.1.3 | pc_DL_intra_non_contiguous_EN_DC_Class_A_A | | +| 2 | DL Intra-band non-contiguous EN-DC BW Class Combination A_AA | 36.101, 5.6A.1
38.101-3, 5.3B.1.3 | pc_DL_intra_non_contiguous_EN_DC_Class_A_AA | | +| 3 | DL Intra-band non-contiguous EN-DC BW Class Combination A-A_A | 36.101, 5.6A.1
38.101-3, 5.3B.1.3 | pc_DL_intra_non_contiguous_EN_DC_Class_A-A_A | | +| 4 | DL Intra-band non-contiguous EN-DC BW Class Combination C_A | 36.101, 5.6A.1
38.101-3, 5.3B.1.3 | pc_DL_intra_non_contiguous_EN_DC_Class_C_A | | +| 5 | DL Intra-band non-contiguous EN-DC BW Class Combination D_A | 36.101, 5.6A.1
38.101-3, 5.3B.1.3 | pc_DL_intra_non_contiguous_EN_DC_Class_D_A | | + +**Table A.4.3.2B.2.2-1a: Uplink Bandwidth Class Combination capabilities for Intra-band non-contiguous EN-DC configurations (for one or more of the supported configurations in Table A.4.3.2B.2.2-2)** + +| Item | UL Intra-band non-contiguous EN-DC Bandwidth Class | Ref. | Mnemonic | Comments | +|------|-------------------------------------------------------------|-----------------------------------------|---------------------------------------------|----------| +| 1 | UL Intra-band non-contiguous EN-DC BW Class Combination A_A | 36.101, 5.6A.1
38.101-3,
5.3B.1.3 | pc_UL_intra_non_contiguous_EN_D_C_Class_A_A | | +| 2 | UL Intra-band non-contiguous EN-DC BW Class Combination AA | 36.101, 5.6A.1
38.101-3,
5.3B.1.3 | pc_UL_intra_non_contiguous_EN_D_C_Class_AA | | + +**Table A.4.3.2B.2.2-2: Supported Intra-band non-contiguous EN-DC configurations** + +| EN-DC configuration / Item
(Note 1, 3, 4) | Release | Supported | Supported EN-DC Bandwidth Class(es) in UL
(Note 2) | Supported Bandwidth Combination Set(s) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-----------|-------------------------------------------------------|----------------------------------------| +| DC_2A_n2A 6 | Rel-16 | | | | +| DC_41A_n41A | Rel-15 | | | | +| DC_41C_n41A | Rel-15 | | | | +| DC_41D_n41A | Rel-15 | | | | +| DC_66A_n66A 6 | Rel-16 | | | | +| Note 1: Notation used for intra-band non-contiguous EN-DC Bands is according to TS 38.101-3 [25] Table 5.3B.1.3-1, e.g. 'DC_41A_n41A' indicates non-contiguous EN-DC operation on E-UTRA band 41 with DL Bandwidth Class A and NR band n41 with DL CA Bandwidth Class A.
Note 2: See UL_nCC( table_index ) in Note 2 of Table 4.0-3 in TS 38.522 [9].
Note 3: See DL_nCC( table_index ) in Note 4 of Table 4.0-3 in TS 38.522 [9].
Note 4: See DL_NR_nCC( table_index ) in Note 5 of Table 4.0-3 in TS 38.522 [9].
Note 5: Only single switched UL is supported in Rel-15.
Note 6: Only single switched UL is supported. | | | | | + +**Table A.4.3.2B.2.2-3: Intra-band non-contiguous EN-DC PC2 UE RF Baseline Implementation Capabilities** + +| Item | Intra-band non-contiguous EN-DC PC2 UE RF Baseline Implementation Capabilities | Ref. | Release | Mnemonic | Comments | +|------|--------------------------------------------------------------------------------|-----------------------|---------|----------------------------------|-------------| +| 1 | LTE Frequency band: 2496-2690 MHz
NR Frequency band: 2496-2690 MHz | 38.101-3,
6.2B.1.2 | Rel-15 | pc_Band41_nrBand41_NC_C_PC2_Supp | DC_41A_n41A | + +**Table A.4.3.2B.2.2-4: Intra-band non-contiguous EN-DC NR part power class UE RF Baseline Implementation Capabilities (Rel-16 and forward)** + +| Item | EN-DC configuration | UE Physical Layer Baseline Implementation Capabilities | Ref. | Release | Mnemonic | Supported NR part power class | +|------|---------------------|--------------------------------------------------------|--------------------|---------|--------------------------------------------|-------------------------------| +| 1 | DC_41A_n41A | DC_41A_n41A NR part power class | 38.306,
4.2.7.1 | Rel-16 | pc_Band41_nrBand41_NC_powerClassNRPart_r16 | | + +**Table A.4.3.2B.2.2-4a: Intra-band non-contiguous EN-DC maxNumberSRS-Ports-PerResource UE RF Baseline Implementation Capabilities (Rel-15)** + +| Item | EN-DC configuration | UE Physical Layer Baseline Implementation Capabilities | Ref. | Release | Mnemonic | Supported maxNumberSRS-Ports-PerResource | +|------|---------------------|----------------------------------------------------------|--------------------|---------|-----------------------------------------------------------------|------------------------------------------| +| 1 | DC_41A_n41A | DC_41A_n41A
maxNumberSRS-Ports-PerResource on NR band | 38.306,
4.2.7.7 | Rel-15 | pc_Band41_nrBand41_NC_
maxNumberSRS-Ports-PerResource_NR_r15 | | + +**Table A.4.3.2B.2.2-4b: Intra-band non-contiguous EN-DC NR part power class UE RF Baseline Implementation Capabilities (Rel-15) (maxNumberSRS-Ports-PerResource=n2 in NR standalone operation mode, maxNumberSRS-Ports-PerResource=n1 for EN-DC on NR band)** + +| Item | EN-DC configuration | UE Physical Layer Baseline Implementation Capabilities | Ref. | Release | Mnemonic | Supported NR part power class | +|------|---------------------|--------------------------------------------------------|------------------|---------|------------------------------------------------|-------------------------------| +| 1 | DC_41A_n41A | DC_41A_n41A NR part power class | 38.101-3,
6.1 | Rel-15 | pc_Band41_nrBand41_NC_
powerClassNRPart_r15 | | + +###### A.4.3.2B.2.3 Inter-band EN-DC + +###### A.4.3.2B.2.3.1 Inter-band EN-DC within FR1 (two bands) + +**Table A.4.3.2B.2.3.1-1: Downlink Bandwidth Class Combination capabilities for Inter-band EN-DC within FR1 and two bands (for one or more of the supported DC configurations in Table A.4.3.2B.2.3.1-2)** + +| Item | DL inter-band EN-DC within FR1 Bandwidth Class | Ref. | Mnemonic | Comments | +|------|------------------------------------------------------------------------|-----------------------------------------|-------------------------------------------------------|----------| +| 1 | Inter-band EN-DC within FR1 BW Class Combination A_A (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.1 | pc_DL_inter_band
_EN_DC_FR1_2B
_Class_A_A | | +| 2 | Inter-band EN-DC within FR1 BW Class Combination A_(2A) (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.1 | pc_DL_inter_band
_EN_DC_FR1_2B
_Class_A_(2A) | | +| 3 | Inter-band EN-DC within FR1 BW Class Combination A_B (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.1 | pc_DL_inter_band
_EN_DC_FR1_2B
_Class_A_B | | +| 4 | Inter-band EN-DC within FR1 BW Class Combination A_C (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.1 | pc_DL_inter_band
_EN_DC_FR1_2B
_Class_A_C | | +| 5 | Inter-band EN-DC within FR1 BW Class Combination (2A)_A (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.1 | pc_DL_inter_band
_EN_DC_FR1_2B
_Class_(2A)_A | | +| 6 | Inter-band EN-DC within FR1 BW Class Combination (2A)_(2A) (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.1 | pc_DL_inter_band
_EN_DC_FR1_2B
_Class_(2A)_(2A) | | +| 7 | Inter-band EN-DC within FR1 BW Class Combination (2A)_B (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.1 | pc_DL_inter_band
_EN_DC_FR1_2B
_Class_(2A)_B | | +| 8 | Inter-band EN-DC within FR1 BW Class Combination (3A)_A (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.1 | pc_DL_inter_band
_EN_DC_FR1_2B
_Class_(3A)_A | | +| 9 | Inter-band EN-DC within FR1 BW Class Combination B_A (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.1 | pc_DL_inter_band
_EN_DC_FR1_2B
_Class_B_A | | +| 10 | Inter-band EN-DC within FR1 BW Class Combination C_A (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.1 | pc_DL_inter_band
_EN_DC_FR1_2B
_Class_C_A | | +| 11 | Inter-band EN-DC within FR1 BW Class Combination C_(2A) (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.1 | pc_DL_inter_band
_EN_DC_FR1_2B
_Class_C_(2A) | | +| 12 | Inter-band EN-DC within FR1 BW Class Combination C_B (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.1 | pc_DL_inter_band
_EN_DC_FR1_2B
_Class_C_B | | +| 13 | Inter-band EN-DC within FR1 BW Class Combination C_C (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.1 | pc_DL_inter_band
_EN_DC_FR1_2B
_Class_C_C | | +| 14 | Inter-band EN-DC within FR1 BW Class Combination D_A (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.1 | pc_DL_inter_band
_EN_DC_FR1_2B
_Class_D_A | | +| 15 | Inter-band EN-DC within FR1 BW Class Combination D_C (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.1 | pc_DL_inter_band
_EN_DC_FR1_2B
_Class_D_C | | +| 16 | Inter-band EN-DC within FR1 BW Class Combination E_A (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.1 | pc_DL_inter_band
_EN_DC_FR1_2B
_Class_E_A | | +| 17 | Inter-band EN-DC within FR1 BW Class Combination E_C (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.1 | pc_DL_inter_band
_EN_DC_FR1_2B
_Class_E_C | | + +**Table A.4.3.2B.2.3.1-1a: Uplink Bandwidth Class Combination capabilities for Inter-band EN-DC within FR1 and two bands (for one or more of the supported configurations in Table A.4.3.2B.2.3.1-2)** + +| Item | UL inter-band EN-DC within FR1 Bandwidth Class | Ref. | Mnemonic | Comments | +|------|------------------------------------------------------------------------|-----------------------------------------|----------------------------------------------------|----------| +| 1 | UL Inter-band EN-DC within FR1 BW Class Combination A_A (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.1 | pc_UL_inter_band
_EN_DC_FR1_2B
_Class_A_A | | +| 2 | UL Inter-band EN-DC within FR1 BW Class Combination A_B (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.1 | pc_UL_inter_band
_EN_DC_FR1_2B
_Class_A_B | | +| 3 | UL Inter-band EN-DC within FR1 BW Class Combination A_C (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.1 | pc_UL_inter_band
_EN_DC_FR1_2B
_Class_A_C | | +| 4 | UL Inter-band EN-DC within FR1 BW Class Combination (2A)_A (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.1 | pc_UL_inter_band
_EN_DC_FR1_2B
_Class_(2A)_A | | +| 5 | UL Inter-band EN-DC within FR1 BW Class Combination C_A (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.1 | pc_UL_inter_band
_EN_DC_FR1_2B
_Class_C_A | | + +**Table A.4.3.2B.2.3.1-2: Supported Inter-band EN-DC configurations within FR1 (two bands)** + +| EN-DC configuration / Item | Release | Supported | Supported EN-DC Bandwidth Class(es) in UL | Supported ULTxSwitching Band Pair | Supported uplinkTxSwitching -DL-Interruption- r16 (Note 8) | Supported simultaneousRxTx (Note 11) | +|----------------------------|---------|-----------|-------------------------------------------|-----------------------------------|------------------------------------------------------------|--------------------------------------| +| DC_1A_n3A | Rel-16 | | | | | | +| DC_1A_n5A | Rel-16 | | | | | | +| DC_1A_n7A | Rel-16 | | | | | | +| DC_1A_n28A | Rel-15 | | | | | | +| DC_1A_n41A | Rel-16 | | | | | Yes | +| DC_1A_n77A | Rel-15 | | | | Not supported | Yes | +| DC_1A_n78A | Rel-15 | | | | Not supported | Yes | +| DC_1A_n78C | Rel-15 | | | | Not supported | Yes | +| DC_1A-1A_n78A | Rel-17 | | | | Not supported | | +| DC_1A_n79A | Rel-15 | | | | Not supported | Yes | +| DC_2A_n5A | Rel-15 | | | | | | +| DC_2A-2A_n5A | Rel-16 | | | | | | +| DC_2A_n41A | Rel-16 | | | | | | +| DC_2C_n41A | Rel-16 | | | | | | +| DC_2A_n66A | Rel-15 | | | | | | +| DC_2A_n71A | Rel-15 | | | | | | +| DC_2A_n77A | Rel-17 | | | | | | +| DC_2A_n77(2A) | Rel-17 | | | | | | +| DC_2A-2A_n77A | Rel-17 | | | | | | +| DC_2A-2A_n77(2A) | Rel-17 | | | | | | +| DC_2A_n78A | Rel-15 | | | | | | +| DC_3A_n1A | Rel-16 | | | | | | +| DC_3A_n8A | Rel-16 | | | | | | +| DC_3A_n7A | Rel-15 | | | | | | +| DC_3A_n5A | Rel-16 | | | | | | +| DC_3A_n28A | Rel-15 | | | | | | +| DC_3A_n41A | Rel-16 | | | | Not supported | Yes | +| DC_3A_n77A | Rel-15 | | | | Not supported | Yes | +| DC_3A_n78A | Rel-15 | | | | Not supported | Yes | +| DC_3A_n78C | Rel-15 | | | | Not supported | Yes | +| DC_3A_n79A | Rel-15 | | | | Not supported | Yes | +| DC_3A_n82A | Rel-15 | | | | | | +| DC_3C_n77A | Rel-17 | | | | Not supported | | +| DC_3C_n77(2A) | Rel-17 | | | | Not supported | | +| DC_3C_n78A | Rel-15 | | | | Not supported | | +| DC_5A_n2A | Rel-16 | | | | | | +| DC_5A_n66A | Rel-15 | | | | | | +| DC_5A_n77A | Rel-17 | | | | | | +| DC_5A_n77(2A) | Rel-17 | | | | | | +| DC_5A_n78A | Rel-15 | | | | Not supported | Yes | +| DC_5A_n78C | Rel-17 | | | | Not supported | Yes | +| DC_7A_n1A | Rel-16 | | | | | | +| DC_7A_n3A | Rel-16 | | | | | | +| DC_7A_n5A | Rel-16 | | | | | | +| DC_7A_n8A | Rel-16 | | | | | | +| DC_7A_n28A | Rel-15 | | | | | | +| DC_7A_n78A | Rel-15 | | | | | Yes | +| DC_7A_n66A | Rel-15 | | | | | | +| DC_7C_n66A | Rel-15 | | | | | | +| DC_7C_n78A | Rel-15 | | | | | Yes | +| DC_8A_n1A | Rel-16 | | | | | | +| DC_8A_n3A | Rel-16 | | | | | | + +| | | | | | | | +|----------------|--------|--|--|--|---------------|-----| +| DC_8A_n20A | Rel-16 | | | | | | +| DC_8A_n41A | Rel-16 | | | | Not supported | Yes | +| DC_8A_n77A | Rel-15 | | | | Not supported | Yes | +| DC_8A_n77(2A) | Rel-16 | | | | Not supported | Yes | +| DC_8A_n78A | Rel-15 | | | | Not supported | Yes | +| DC_11A_n77A | Rel-15 | | | | Not supported | Yes | +| DC_11A_n78A | Rel-15 | | | | Not supported | Yes | +| DC_11A_n79A | Rel-15 | | | | | Yes | +| DC_12A_n2A | Rel-16 | | | | | | +| DC_12A_n5A | Rel-15 | | | | | | +| DC_12A_n66A | Rel-15 | | | | | | +| DC_12A_n77A | Rel-17 | | | | | | +| DC_12A_n77(2A) | Rel-17 | | | | | | +| DC_12A_n78A | Rel-16 | | | | | | +| DC_13A_n2A | Rel-16 | | | | | | +| DC_13A_n66A | Rel-15 | | | | | | +| DC_13A_n77A | Rel-17 | | | | | | +| DC_14A_n2A | Rel-16 | | | | | | +| DC_14A_n66A | Rel-16 | | | | | | +| DC_14A_n77A | Rel-17 | | | | | | +| DC_14A_n77(2A) | Rel-17 | | | | | | +| DC_18A_n77A | Rel-15 | | | | Not supported | Yes | +| DC_18A_n78A | Rel-15 | | | | Not supported | Yes | +| DC_18A_n79A | Rel-15 | | | | | Yes | +| DC_19A_n1A | Rel-17 | | | | | | +| DC_19A_n77A | Rel-15 | | | | | Yes | +| DC_19A_n77(2A) | Rel-17 | | | | | Yes | +| DC_19A_n78A | Rel-15 | | | | Not supported | Yes | +| DC_19A_n78(2A) | Rel-17 | | | | Not supported | Yes | +| DC_19A_n79A | Rel-15 | | | | Not supported | Yes | +| DC_20A_n1A | Rel-16 | | | | | | +| DC_20A_n3A | Rel-16 | | | | | | +| DC_20A_n7A | Rel-16 | | | | | | +| DC_20A_n8A | Rel-15 | | | | | | +| DC_20A_n28A | Rel-15 | | | | | | +| DC_20A_n78A | Rel-15 | | | | | Yes | +| DC_20A_n83A | Rel-16 | | | | | | +| DC_21A_n1A | Rel-17 | | | | | | +| DC_21A_n28A | Rel-17 | | | | | | +| DC_21A_n77A | Rel-15 | | | | | Yes | +| DC_21A_n77(2A) | Rel-17 | | | | | Yes | +| DC_21A_n78A | Rel-15 | | | | Not supported | Yes | +| DC_21A_n78(2A) | Rel-17 | | | | Not supported | Yes | +| DC_21A_n79A | Rel-15 | | | | Not supported | Yes | +| DC_25A_n41A | Rel-15 | | | | | | +| DC_26A_n41A | Rel-16 | | | | | | +| DC_26A_n77A | Rel-16 | | | | | Yes | +| DC_26A_n78A | Rel-16 | | | | | Yes | +| DC_26A_n79A | Rel-16 | | | | | Yes | +| DC_28A_n3A | Rel-16 | | | | | | +| DC_28A_n5A | Rel-16 | | | | | | +| DC_28A_n7A | Rel-16 | | | | | | +| DC_28A_n51A | Rel-15 | | | | | | +| DC_28A_n77A | Rel-15 | | | | Not supported | Yes | +| DC_28A_n78A | Rel-15 | | | | Not supported | Yes | +| DC_28A_n79A | Rel-15 | | | | | Yes | +| DC_30A_n2A | Rel-16 | | | | | | + +| | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--|--|--|---------------|-----| +| DC_30A_n5A | Rel-15 | | | | | | +| DC_30A_n77A | Rel-17 | | | | | | +| DC_30A_n77(2A) | Rel-17 | | | | | | +| DC_30A_n66A | Rel-15 | | | | | | +| DC_38A_n78A | Rel-15 | | | | | Yes | +| DC_39A_n41A | Rel-16 | | | | Not supported | | +| DC_39A_n79A | Rel-15 | | | | Not supported | Yes | +| DC_40A_n1A | Rel-16 | | | | | | +| DC_40A_n41A | Rel-16 | | | | | | +| DC_40A_n78A | Rel-16 | | | | | | +| DC_40A_n79A | Rel-16 | | | | Not supported | Yes | +| DC_40C_n78A | Rel-16 | | | | | | +| DC_40C_n79A | Rel-16 | | | | Not supported | Yes | +| DC_41A_n28A | Rel-16 | | | | | Yes | +| DC_41A_n77A | Rel-16 | | | | | | +| DC_41A_n78A | Rel-16 | | | | | | +| DC_41A_n79A | Rel-15 | | | | Not supported | Yes | +| DC_42A_n1A | Rel-17 | | | | | | +| DC_42C_n1A | Rel-17 | | | | | | +| DC_42A_n77A | Rel-15 | | | | | | +| DC_42A_n78A | Rel-15 | | | | | | +| DC_42A_n79A | Rel-15 | | | | | | +| DC_48A_n5A | Rel-16 | | | | | | +| DC_48A_n46A | Rel-16 | | | | | | +| DC_48A_n66A | Rel-16 | | | | | | +| DC_66A_n2A | Rel-16 | | | | | | +| DC_66A_n5A | Rel-15 | | | | | | +| DC_66A-66A_n5A | Rel-16 | | | | | | +| DC_66A_n41A | Rel-16 | | | | | | +| DC_66A_n71A | Rel-15 | | | | | | +| DC_66A_n77A | Rel-17 | | | | | | +| DC_66A_n77(2A) | Rel-17 | | | | | | +| DC_66A-n66A_n77A | Rel-17 | | | | | | +| DC_66A-66A_n77(2A
) | Rel-17 | | | | | | +| DC_66A_n78A | Rel-15 | | | | | | +| DC_71A_n2A | Rel-17 | | | | | | +| DC_71A_n66A | Rel-16 | | | | | | +| Note 8: A UE that supports UL Tx Switching on a band pair might report the uplinkTxSwitching-DL-Interruption-r16 capability on the same band pair. If UE doesn't report this capability, no DL interruption is allowed during UL Tx switching. For certain band configurations DL interruption is not allowed according to Note 14 in Table 5.5B.4.1-1 of TS 38.101-3 [25], therefore the corresponding entry is prefilled by 'Not Supported'. | | | | | | | +| Note 9: For configurations with Note 7 in Table 5.5B.4.1-1 of TS 38.521-3 [7], UE capability simultaneousRxTxInterBandENDC is mandatory, therefore the corresponding entry is prefilled with 'Yes'. | | | | | | | + +**Table A.4.3.2B.2.3.1-3: Inter-band EN-DC within FR1 (two bands) PC2 UE RF Baseline Implementation Capabilities** + +| Item | EN-DC configuration | Inter-band EN-DC within FR1 (two bands) PC2 UE RF Baseline Implementation Capabilities | Ref. | Release | Mnemonic | Comments | +|------|---------------------|-------------------------------------------------------------------------------------------------------------|-----------------------|---------|------------------------------|----------| +| 1 | DC_39A_n41A | LTE Frequency band: 1880-1920 MHz
NR Frequency band: 2496-2690 MHz | 38.101-3,
6.2B.1.3 | Rel-16 | pc_Band39_nrBand41_ PC2_Supp | | +| 2 | DC_39A_n79A | LTE Frequency band: 1880-1920 MHz
NR Frequency band: 4400-5000 MHz | 38.101-3,
6.2B.1.3 | Rel-16 | pc_Band39_nrBand79_ PC2_Supp | | +| 3 | DC_41A_n79A | LTE Frequency band: 2496-2690 MHz
NR Frequency band: 4400-5000 MHz | 38.101-3,
6.2B.1.3 | Rel-16 | pc_Band41_nrBand79_ PC2_Supp | | +| 4 | DC_3A_n78A | LTE Frequency band: 1710-1785 MHz (UL), 1805-1880 MHz (DL)
NR Frequency band: 3300-3800 MHz | 38.101-3,
6.2B.1.3 | Rel-16 | pc_Band3_nrBand78_ PC2_Supp | | +| 5 | DC_3A_n41A | LTE Frequency band: 1710-1785 MHz (UL), 1805-1880 MHz (DL)
NR Frequency band: 2496-2690 MHz | 38.101-3,
6.2B.1.3 | Rel-16 | pc_Band3_nrBand41_ PC2_Supp | | +| 6 | DC_1A_n78A | LTE Frequency band: 1920-1980 MHz (UL), 2110- 2170 MHz (DL)
NR Frequency band: 3300-3800 MHz | 38.101-3,
6.2B.1.3 | Rel-17 | pc_Band1_nrBand78_ PC2_Supp | | +| 7 | Void | | | | | | +| 8 | DC_8A_n78A | LTE Frequency band: 703-748 MHz (UL), 758-803 MHz (DL)
NR Frequency band: 3300-3800 MHz | 38.101-3,
6.2B.1.3 | Rel-17 | pc_Band8_nrBand78_ PC2_Supp | | +| 9 | DC_2A_n77A | LTE Frequency band: 1850-1910 MHz (UL), 1930-1990 MHz (DL)
NR Frequency band: 3300-4200 MHz 1 | 38.101-3,
6.2B.1.3 | Rel-17 | pc_Band2_nrBand77_ PC2_Supp | | +| 10 | DC_5A_n77A | LTE Frequency band: 824-849 MHz (UL), 869- 894 MHz (DL)
NR Frequency band: 3300-4200 MHz 1 | 38.101-3,
6.2B.1.3 | Rel-17 | pc_Band5_nrBand77_ PC2_Supp | | +| 11 | DC_13A_n77A | LTE Frequency band: 777-787 MHz (UL), 746-756 MHz (DL)
NR Frequency band: 3300-4200 MHz 1 | 38.101-3,
6.2B.1.3 | Rel-17 | pc_Band13_nrBand77_ PC2_Supp | | +| 12 | DC_66A_n77A | LTE Frequency band: 1710-1780 MHz (UL), 2110-2200 MHz (DL)
NR Frequency band: 3300-4200 MHz 1 | 38.101-3,
6.2B.1.3 | Rel-17 | pc_Band66_nrBand77_ PC2_Supp | | +| 13 | DC_12A_n77A | LTE Frequency band: 699-716 MHz (UL), 729- 746 MHz (DL)
NR Frequency band: 3300-4200 MHz 1 | 38.101-3,
6.2B.1.3 | Rel-17 | pc_Band12_nrBand77_ PC2_Supp | | +| 14 | DC_14A_n77A | LTE Frequency band: 788-798 MHz (UL), 758-768 MHz (DL)
NR Frequency band: 3300-4200 MHz 1 | 38.101-3,
6.2B.1.3 | Rel-17 | pc_Band14_nrBand77_ PC2_Supp | | +| 15 | DC_30A_n77A | LTE Frequency band: 2305-2315 MHz (UL), 2350-2360 MHz (DL)
NR Frequency band: 3300-4200 MHz 1 | 38.101-3,
6.2B.1.3 | Rel-17 | pc_Band30_nrBand77_ PC2_Supp | | +| 16 | DC_28A_n78A | LTE Frequency band: 703-748 MHz (UL), 758- 803 MHz (DL)
NR Frequency band: 3300-3800 MHz | 38.101-3,
6.2B.1.3 | Rel-17 | pc_Band28_nrBand78_ PC2_Supp | | +| 17 | DC_1A_n79A | LTE Frequency band: 1920-1980 MHz (UL), 2110- 2170 MHz (DL)
NR Frequency band: 4400-5000 MHz | 38.101-3,
6.2B.1.3 | Rel-18 | pc_Band1_nrBand79_ PC2_Supp | | +| 18 | DC_3A_n79A | LTE Frequency band: 1710-1785 MHz (UL), 1805-1880 MHz (DL)
NR Frequency band: 4400-5000 MHz | 38.101-3,
6.2B.1.3 | Rel-18 | pc_Band3_nrBand79_ PC2_Supp | | +| 19 | DC_19A_n78A | LTE Frequency band: 830-845 MHz (UL), 875-890 MHz (DL)
NR Frequency band: 3300-3800 MHz | 38.101-3,
6.2B.1.3 | Rel-18 | pc_Band19_nrBand78_ PC2_Supp | | +| 20 | DC_19A_n79A | LTE Frequency band: 830-845 MHz (UL), 875-890 MHz (DL)
NR Frequency band: 4400-5000 MHz | 38.101-3,
6.2B.1.3 | Rel-18 | pc_Band19_nrBand79_ PC2_Supp | | + +| | | | | | | | +|----|-------------|--------------------------------------------------------------------------------------------------------|-----------------------|--------|-----------------------------|--| +| 21 | DC_21A_n78A | LTE Frequency band: 1447.9-1462.9 MHz (UL), 1495.9-1510.9 MHz (DL)
NR Frequency band: 3300-3800 MHz | 38.101-3,
6.2B.1.3 | Rel-18 | pc_Band21_nrBand78_PC2_Supp | | +| 22 | DC_21A_n79A | LTE Frequency band: 1447.9-1462.9 MHz (UL), 1495.9-1510.9 MHz (DL)
NR Frequency band: 4400-5000 MHz | 38.101-3,
6.2B.1.3 | Rel-18 | pc_Band21_nrBand79_PC2_Supp | | + +NOTE 1: In the USA this band is restricted to 3450 – 3550 MHz and 3700 – 3980 MHz + +**Table A.4.3.2B.2.3.1-3a: Inter-band EN-DC within FR1 (two bands) NR part power class UE RF Baseline Implementation Capabilities (Rel-16 and forward)** + +| Item | EN-DC configuration | UE Physical Layer Baseline Implementation Capabilities | Ref. | Release | Mnemonic | Supported NR part power class | +|------|---------------------|--------------------------------------------------------|--------------------|---------|-----------------------------------------|-------------------------------| +| 1 | DC_39A_n41A | DC_39A_n41A NR part power class | 38.306,
4.2.7.1 | Rel-16 | pc_Band39_nrBand41_powerClassNRPart_r16 | | +| 2 | DC_39A_n79A | DC_39A_n79A NR part power class | 38.306,
4.2.7.1 | Rel-16 | pc_Band39_nrBand79_powerClassNRPart_r16 | | +| 3 | DC_41A_n79A | DC_41A_n79A NR part power class | 38.306,
4.2.7.1 | Rel-16 | pc_Band41_nrBand79_powerClassNRPart_r16 | | +| 4 | DC_3A_n78A | DC_3A_n78A NR part power class | 38.306,
4.2.7.1 | Rel-16 | pc_Band3_nrBand78_powerClassNRPart_r16 | | +| 5 | DC_3A_n41A | DC_3A_n41A NR part power class | 38.306,
4.2.7.1 | Rel-16 | pc_Band3_nrBand41_powerClassNRPart_r16 | | +| 6 | DC_1A_n78A | DC_1A_n78A NR part power class | 38.306,
4.2.7.1 | Rel-17 | pc_Band1_nrBand78_powerClassNRPart_r17 | | +| 7 | DC_8A_n78A | DC_8A_n78A NR part power class | 38.306,
4.2.7.1 | Rel-17 | pc_Band8_nrBand78_powerClassNRPart_r17 | | +| 8 | DC_2A_n77A | DC_2A_n77A NR part power class | 38.306,
4.2.7.1 | Rel-17 | pc_Band2_nrBand77_powerClassNRPart_r17 | | +| 9 | DC_5A_n77A | DC_5A_n77A NR part power class | 38.306,
4.2.7.1 | Rel-17 | pc_Band5_nrBand77_powerClassNRPart_r17 | | +| 10 | DC_13A_n77A | DC_13A_n77A NR part power class | 38.306,
4.2.7.1 | Rel-17 | pc_Band13_nrBand77_powerClassNRPart_r17 | | +| 11 | DC_66A_n77A | DC_66A_n77A NR part power class | 38.306,
4.2.7.1 | Rel-17 | pc_Band66_nrBand77_powerClassNRPart_r17 | | +| 12 | DC_12A_n77A | DC_12A_n77A NR part power class | 38.306,
4.2.7.1 | Rel-17 | pc_Band12_nrBand77_powerClassNRPart_r17 | | +| 13 | DC_14A_n77A | DC_14A_n77A NR part power class | 38.306,
4.2.7.1 | Rel-17 | pc_Band14_nrBand77_powerClassNRPart_r17 | | +| 14 | DC_30A_n77A | DC_30A_n77A NR part power class | 38.306,
4.2.7.1 | Rel-17 | pc_Band30_nrBand77_powerClassNRPart_r17 | | + +**Table A.4.3.2B.2.3.1-3b: Inter-band EN-DC within FR1 (two bands) maxNumberSRS-Ports-PerResource UE RF Baseline Implementation Capabilities (Rel-15)** + +| Item | EN-DC configuration | UE Physical Layer Baseline Implementation Capabilities | Ref. | Release | Mnemonic | Supported maxNumberSRS-Ports-PerResource | +|------|---------------------|----------------------------------------------------------|--------------------|---------|----------------------------------------------------------|------------------------------------------| +| 1 | DC_39A_n41A | DC_39A_n41A
maxNumberSRS-Ports-PerResource on NR band | 38.306,
4.2.7.7 | Rel-15 | pc_Band39_nrBand41_maxNumberSRS-Ports-PerResource_NR_r15 | | +| 2 | DC_39A_n79A | DC_39A_n79A
maxNumberSRS-Ports-PerResource on NR band | 38.306,
4.2.7.7 | Rel-15 | pc_Band39_nrBand79_maxNumberSRS-Ports-PerResource_NR_r15 | | +| 3 | DC_41A_n79A | DC_41A_n79A
maxNumberSRS-Ports-PerResource on NR band | 38.306,
4.2.7.7 | Rel-15 | pc_Band41_nrBand79_maxNumberSRS-Ports-PerResource_NR_r15 | | +| 4 | DC_3A_n78A | DC_3A_n78A
maxNumberSRS-Ports-PerResource on NR band | 38.306,
4.2.7.7 | Rel-15 | pc_Band3_nrBand78_maxNumberSRS-Ports-PerResource_NR_r15 | | +| 5 | DC_3A_n41A | DC_3A_n41A
maxNumberSRS-Ports-PerResource on NR band | 38.306,
4.2.7.7 | Rel-15 | pc_Band3_nrBand41_maxNumberSRS-Ports-PerResource_NR_r15 | | +| 6 | DC_1A_n78A | DC_1A_n78A
maxNumberSRS-Ports-PerResource on NR band | 38.306,
4.2.7.7 | Rel-15 | pc_Band1_nrBand78_maxNumberSRS-Ports-PerResource_NR_r15 | | +| 7 | DC_8A_n78A | DC_8A_n78A
maxNumberSRS-Ports-PerResource on NR band | 38.306,
4.2.7.7 | Rel-15 | pc_Band8_nrBand78_maxNumberSRS-Ports-PerResource_NR_r15 | | +| 8 | DC_2A_n77A | DC_2A_n77A
maxNumberSRS-Ports-PerResource on NR band | 38.306,
4.2.7.7 | Rel-15 | pc_Band2_nrBand77_maxNumberSRS-Ports-PerResource_NR_r15 | | +| 9 | DC_5A_n77A | DC_5A_n77A
maxNumberSRS-Ports-PerResource on NR band | 38.306,
4.2.7.7 | Rel-15 | pc_Band5_nrBand77_maxNumberSRS-Ports-PerResource_NR_r15 | | +| 10 | DC_13A_n77A | DC_13A_n77A
maxNumberSRS-Ports-PerResource on NR band | 38.306,
4.2.7.7 | Rel-15 | pc_Band13_nrBand77_maxNumberSRS-Ports-PerResource_NR_r15 | | +| 11 | DC_66A_n77A | DC_66A_n77A
maxNumberSRS-Ports-PerResource on NR band | 38.306,
4.2.7.7 | Rel-15 | pc_Band66_nrBand77_maxNumberSRS-Ports-PerResource_NR_r15 | | + +**Table A.4.3.2B.2.3.1-3c: Inter-band EN-DC within FR1 (two bands) NR part power class UE RF Baseline Implementation Capabilities (Rel-15) (maxNumberSRS-Ports-PerResource=n2 in NR standalone operation mode, maxNumberSRS-Ports-PerResource=n1 for EN-DC on NR band)** + +| Item | EN-DC configuration | UE Physical Layer Baseline Implementation Capabilities | Ref. | Release | Mnemonic | Supported NR part power class | +|------|---------------------|--------------------------------------------------------|---------------|---------|-----------------------------------------|-------------------------------| +| 1 | DC_39A_n41A | DC_39A_n41A NR part power class | 38.101-3, 6.1 | Rel-15 | pc_Band39_nrBand41_powerClassNRPart_r15 | | +| 2 | DC_39A_n79A | DC_39A_n79A NR part power class | 38.101-3, 6.1 | Rel-15 | pc_Band39_nrBand79_powerClassNRPart_r15 | | +| 3 | DC_41A_n79A | DC_41A_n79A NR part power class | 38.101-3, 6.1 | Rel-15 | pc_Band41_nrBand79_powerClassNRPart_r15 | | +| 4 | DC_3A_n78A | DC_3A_n78A NR part power class | 38.101-3, 6.1 | Rel-15 | pc_Band3_nrBand78_powerClassNRPart_r15 | | +| 5 | DC_3A_n41A | DC_3A_n41A NR part power class | 38.101-3, 6.1 | Rel-15 | pc_Band3_nrBand41_powerClassNRPart_r15 | | +| 6 | DC_1A_n78A | DC_1A_n78A NR part power class | 38.101-3, 6.1 | Rel-15 | pc_Band1_nrBand78_powerClassNRPart_r15 | | +| 7 | DC_8A_n78A | DC_8A_n78A NR part power class | 38.101-3, 6.1 | Rel-15 | pc_Band8_nrBand78_powerClassNRPart_r15 | | +| 8 | DC_2A_n77A | DC_2A_n77A NR part power class | 38.101-3, 6.1 | Rel-15 | pc_Band2_nrBand77_powerClassNRPart_r15 | | +| 9 | DC_5A_n77A | DC_5A_n77A NR part power class | 38.101-3, 6.1 | Rel-15 | pc_Band5_nrBand77_powerClassNRPart_r15 | | +| 10 | DC_13A_n77A | DC_13A_n77A NR part power class | 38.101-3, 6.1 | Rel-15 | pc_Band13_nrBand77_powerClassNRPart_r15 | | +| 11 | DC_66A_n77A | DC_66A_n77A NR part power class | 38.101-3, 6.1 | Rel-15 | pc_Band66_nrBand77_powerClassNRPart_r15 | | + +**Table A.4.3.2B.2.3.1-4: UE Power Class implementation Capabilities for inter-band EN-DC within FR1 (two bands)** + +| Item | UE Power Class implementation Capabilities | Ref. | Comments | +|------|--------------------------------------------------------------|--------------------|---------------------------------------------------| +| 1 | UE Power Class 2 for Inter-band EN-DC within FR1 (two bands) | 38.101-3, 6.2B.1.3 | Applicable to the bands in Table A.4.3.2B.2.3.1-3 | +| 2 | UE Power Class 3 for Inter-band EN-DC within FR1 (two bands) | 38.101-3, 6.2B.1.3 | Applicable to the bands in Table A.4.3.2B.2.3.1-2 | + +###### A.4.3.2B.2.3.2 Inter-band EN-DC within FR1 (three bands) + +**Table A.4.3.2B.2.3.2-1: Downlink Bandwidth Class Combination capabilities for Inter-band EN-DC within FR1 and three bands (for one or more of the supported DC configurations in Table A.4.3.2B.2.3.2-2)** + +| Item | DL inter-band EN-DC within FR1 Bandwidth Class | Ref. | Mnemonic | +|------|-------------------------------------------------------------------------|-----------------------------------------|------------------------------------------------------| +| 1 | Inter-band EN-DC within FR1 BW Class Combination A-A_A (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.2 | pc_DL_inter_band
_EN_DC_FR1_3B
_Class_A-A_A | +| 2 | Inter-band EN-DC within FR1 BW Class Combination A-A_B (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.2 | pc_DL_inter_band
_EN_DC_FR1_3B
_Class_A-A_B | +| 3 | Inter-band EN-DC within FR1 BW Class Combination A-A_C (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.2 | pc_DL_inter_band
_EN_DC_FR1_3B
_Class_A-A_C | +| 4 | Inter-band EN-DC within FR1 BW Class Combination A-C_A (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.2 | pc_DL_inter_band
_EN_DC_FR1_3B
_Class_A-C_A | +| 5 | Inter-band EN-DC within FR1 BW Class Combination A-C_C (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.2 | pc_DL_inter_band
_EN_DC_FR1_3B
_Class_A-C_C | +| 6 | Inter-band EN-DC within FR1 BW Class Combination A-D_A (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.2 | pc_DL_inter_band
_EN_DC_FR1_3B
_Class_A-D_A | +| 7 | Inter-band EN-DC within FR1 BW Class Combination A-E_A (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.2 | pc_DL_inter_band
_EN_DC_FR1_3B
_Class_A-E_A | +| 8 | Inter-band EN-DC within FR1 BW Class Combination A_A-A (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.2 | pc_DL_inter_band
_EN_DC_FR1_3B
_Class_A_A-A | +| 9 | Inter-band EN-DC within FR1 BW Class Combination C-A_A (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.2 | pc_DL_inter_band
_EN_DC_FR1_3B
_Class_C-A_A | +| 10 | Inter-band EN-DC within FR1 BW Class Combination C-C_A (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.2 | pc_DL_inter_band
_EN_DC_FR1_3B
_Class_C-C_A | +| 11 | Inter-band EN-DC within FR1 BW Class Combination A_(n)AA (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.2 | pc_DL_inter_band
_EN_DC_FR1_3B
_Class_A_(n)AA | +| 12 | Inter-band EN-DC within FR1 BW Class Combination (2A)-A_A (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.2 | pc_DL_inter_band
_EN_DC_FR1_3B
_Class_(2A)-A_A | +| 13 | Inter-band EN-DC within FR1 BW Class Combination (2A)-C_A (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.2 | pc_DL_inter_band
_EN_DC_FR1_3B
_Class_(2A)-C_A | +| 14 | Inter-band EN-DC within FR1 BW Class Combination A-A_(2A) (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.2 | pc_DL_inter_band
_EN_DC_FR1_3B
_Class_A-A_(2A) | +| 15 | Inter-band EN-DC within FR1 BW Class Combination A-C_(2A) (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.2 | pc_DL_inter_band
_EN_DC_FR1_3B
_Class_A-C_(2A) | + +**Table A.4.3.2B.2.3.2-1a: Uplink Bandwidth Class Combination capabilities for Inter-band EN-DC within FR1 and three bands (for one or more of the supported configurations in Table A.4.3.2B.2.3.2-2)** + +| Item | UL inter-band EN-DC within FR1 Bandwidth Class | Ref. | Mnemonic | Comments | +|------|-------------------------------------------------------------------------|-----------------------------------------|---------------------------------------------------|----------| +| 1 | UL Inter-band EN-DC within FR1 BW Class Combination A_A (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.2 | pc_UL_inter_band
_EN_DC_FR1_3B
_Class_A_A | | +| 2 | UL Inter-band EN-DC within FR1 BW Class Combination C_A (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.2 | pc_UL_inter_band
_EN_DC_FR1_3B
_Class_C_A | | +| 3 | UL Inter-band EN-DC within FR1 BW Class Combination C_B (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.2 | pc_UL_inter_band
_EN_DC_FR1_3B
_Class_C_B | | +| 4 | UL Inter-band EN-DC within FR1 BW Class Combination (n)AA (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.2 | pc_UL_inter_band
_EN_DC_FR1_3B
_Class_(n)AA | | + +**Table A.4.3.2B.2.3.2-2: Supported Inter-band EN-DC configurations within FR1 (three bands)** + +| EN-DC configuration /
Item (Note 1, 3, 5) | Release | Supported | | +|----------------------------------------------|---------|-----------|----------------------------------------------------------------| +| | | Supported | Supported EN-DC
Bandwidth Class(es) in
UL
(Note 2, 4) | +| DC_1A-3A_n28A | Rel-15 | | | +| DC_1A-3A_n41A | Rel-16 | | | +| DC_1A-3A_n77A | Rel-15 | | | +| DC_1A-3A_n78A | Rel-15 | | | +| DC_1A-3C_n77A | Rel-17 | | | +| DC_1A-3C_n77(2A) | Rel-17 | | | +| DC_1A-3C_n78A | Rel-15 | | | +| DC_1A-3C_n78(2A) | Rel-16 | | | +| DC_1A-1A-3A_n78A | Rel-17 | | | +| DC_1A-1A-3C_n78A | Rel-17 | | | +| DC_1A-1A-5A_n78A | Rel-17 | | | +| DC_1A-3A_n79A | Rel-15 | | | +| DC_1A-5A_n78C | Rel-17 | | | +| DC_1A-7A_n3A | Rel-16 | | | +| DC_1A-7A_n28A | Rel-15 | | | +| DC_1A-7A_n78A | Rel-15 | | | +| DC_1A-8A_n3A | Rel-16 | | | +| DC_1A-8A_n77A | Rel-16 | | | +| DC_1A-8A_n77(2A) | Rel-16 | | | +| DC_1A-8A_n78A | Rel-15 | | | +| DC_1A-8A_n78(2A) | Rel-17 | | | +| DC_1A-18A_n77A | Rel-15 | | | +| DC_1A-19A_n77(2A) | Rel-17 | | | +| DC_1A-19A_n78A | Rel-15 | | | +| DC_1A-19A_n78(2A) | Rel-17 | | | +| DC_1A-19A_n79A | Rel-15 | | | +| DC_1A-20A_n3A | Rel-16 | | | +| DC_1A-20A_n8A | Rel-16 | | | +| DC_1A-20A_n28A | Rel-15 | | | +| DC_1A-20A_n78A | Rel-15 | | | +| DC_1A-21A_n28A | Rel-17 | | | +| DC_1A-21A_n77(2A) | Rel-17 | | | +| DC_1A-21A_n78A | Rel-15 | | | +| DC_1A-21A_n78(2A) | Rel-17 | | | +| DC_1A-21A_n79A | Rel-15 | | | +| DC_1A-28A_n3A | Rel-16 | | | +| DC_1A-28A_n5A | Rel-16 | | | +| DC_1A-28A_n78C | Rel-15 | | | +| DC_1A_n28A-n78A | Rel-15 | | | +| DC_1A_n28A-n79A | Rel-17 | | | +| DC_1A-41A_n28A | Rel-17 | | | +| DC_1A-41C_n28A | Rel-17 | | | +| DC_1A-41A_n41A | Rel-16 | | | +| DC_1A-41A_n77A | Rel-15 | | | +| DC_1A-42A_n78A | Rel-15 | | | +| DC_1A-42C_n78A | Rel-15 | | | +| DC_1A-42D_n78A | Rel-15 | | | +| DC_1A-42E_n78A | Rel-15 | | | +| DC_1A-42A_n79A | Rel-15 | | | +| DC_1A-42C_n79A | Rel-15 | | | +| DC_1A-42D_n79A | Rel-15 | | | +| DC_1A-42E_n79A | Rel-15 | | | + +| | | | | +|-------------------|--------|--|--| +| DC_1A_n78A-n79A | Rel-15 | | | +| DC_2A_n5A-n77A | Rel-17 | | | +| DC_2A-13A_n77A | Rel-17 | | | +| DC_2A-2A-14A_n66A | Rel-16 | | | +| DC_2A-14A_n2A | Rel-16 | | | +| DC_2A-14A_n66A | Rel-16 | | | +| DC_2A-66A_n41A | Rel-16 | | | +| DC_2A-66A_n5A | Rel-16 | | | +| DC_2A-66A_n71A | Rel-15 | | | +| DC_2A-66A_n77A | Rel-17 | | | +| DC_2A-(n)71AA | Rel-15 | | | +| DC_3A_n1A-n78A | Rel-17 | | | +| DC_3A_n1A-n79A | Rel-17 | | | +| DC_3A-5A_n78C | Rel-17 | | | +| DC_3A-7A_n1A | Rel-16 | | | +| DC_3A-7A_n5A | Rel-16 | | | +| DC_3A-7A_n8A | Rel-16 | | | +| DC_3A-7A_n28A | Rel-15 | | | +| DC_3A-7A_n78A | Rel-15 | | | +| DC_3A-8A_n1A | Rel-16 | | | +| DC_3A-8A_n28A | Rel-16 | | | +| DC_3A-8A_n77A | Rel-16 | | | +| DC_3A-8A_n77(2A) | Rel-16 | | | +| DC_3A-8A_n78A | Rel-15 | | | +| DC_3A-8A_n78(2A) | Rel-17 | | | +| DC_3A-18A_n77A | Rel-17 | | | +| DC_3A-18A_n78A | Rel-17 | | | +| DC_3A-19A_n1A | Rel-17 | | | +| DC_3A-19A_n77(2A) | Rel-17 | | | +| DC_3A-19A_n78A | Rel-15 | | | +| DC_3A-19A_n78(2A) | Rel-17 | | | +| DC_3A-19A_n79A | Rel-15 | | | +| DC_3A-20A_n1A | Rel-16 | | | +| DC_3A-20A_n8A | Rel-16 | | | +| DC_3A-20A_n28A | Rel-15 | | | +| DC_3A-20A_n78A | Rel-15 | | | +| DC_3A-21A_n1A | Rel-17 | | | +| DC_3A-21A_n28A | Rel-17 | | | +| DC_3A-21A_n77(2A) | Rel-17 | | | +| DC_3A-21A_n78A | Rel-15 | | | +| DC_3A-21A_n78(2A) | Rel-17 | | | +| DC_3A-21A_n79A | Rel-15 | | | +| DC_3A-28A_n78A | Rel-15 | | | +| DC_3A_n28A-n78A | Rel-15 | | | +| DC_3A_n28A-n79A | Rel-17 | | | +| DC_3A-40A_n1A | Rel-16 | | | +| DC_3A-41A_n28A | Rel-17 | | | +| DC_3A-41C_n28A | Rel-17 | | | +| DC_3A-41A_n41A | Rel-17 | | | +| DC_3A-41A_n77A | Rel-17 | | | +| DC_3A-41A_n77(2A) | Rel-17 | | | +| DC_3A-41C_n77A | Rel-17 | | | +| DC_3A-42A_n1A | Rel-17 | | | +| DC_3A-42C_n1A | Rel-17 | | | +| DC_3A-42A_n78A | Rel-15 | | | +| DC_3A-42C_n78A | Rel-15 | | | +| DC_3A-42D_n78A | Rel-15 | | | + +| | | | | +|--------------------|--------|--|--| +| DC_3A-42E_n78A | Rel-15 | | | +| DC_3A-42A_n79A | Rel-15 | | | +| DC_3A-42C_n79A | Rel-15 | | | +| DC_3A-42D_n79A | Rel-15 | | | +| DC_3A-42E_n79A | Rel-15 | | | +| DC_3A_n78A-n79A | Rel-15 | | | +| DC_3C-8A_n77A | Rel-17 | | | +| DC_3C-8A_n77(2A) | Rel-17 | | | +| DC_5A-7A_n78A | Rel-15 | | | +| DC_7A-5A_n78A | Rel-16 | | | +| DC_7A-8A_n1A | Rel-16 | | | +| DC_7A-8A_n3A | Rel-16 | | | +| DC_7A-20A_n1A | Rel-16 | | | +| DC_7A-20A_n3A | Rel-16 | | | +| DC_7A-20A_n8A | Rel-16 | | | +| DC_7A-20A_n28A | Rel-15 | | | +| DC_7A-20A_n78A | Rel-15 | | | +| DC_7A-28A_n5A | Rel-16 | | | +| DC_7A_n28A-n78A | Rel-15 | | | +| DC_7C-5A_n78A | Rel-16 | | | +| DC_7C_n28A-n78A | Rel-16 | | | +| DC_13A_n2A-n77A | Rel-17 | | | +| DC_13A-66A_n2A | Rel-16 | | | +| DC_13A-66A_n77A | Rel-17 | | | +| DC_14A-66A_n2A | Rel-16 | | | +| DC_14A-66A-66A_n2A | Rel-16 | | | +| DC_14A-66A_n66A | Rel-16 | | | +| DC_18A-41C_n3A | Rel-17 | | | +| DC_18A-41A_n77A | Rel-17 | | | +| DC_18A-41C_n77A | Rel-17 | | | +| DC_18A-41A_n78A | Rel-17 | | | +| DC_18A-41C_n78A | Rel-17 | | | +| DC_19A_n1A-n78A | Rel-17 | | | +| DC_19A_n1A-n79A | Rel-17 | | | +| DC_19A-21A_n1A | Rel-17 | | | +| DC_19A-21A_n77(2A) | Rel-17 | | | +| DC_19A-21A_n78A | Rel-15 | | | +| DC_19A-21A_n78(2A) | Rel-17 | | | +| DC_19A-21A_n79A | Rel-15 | | | +| DC_19A-42A_n1A | Rel-17 | | | +| DC_19A-42C_n1A | Rel-17 | | | +| DC_19A-42A_n78A | Rel-15 | | | +| DC_19A-42A_n79A | Rel-15 | | | +| DC_19A-42C_n78A | Rel-15 | | | +| DC_19A-42C_n79A | Rel-15 | | | +| DC_19A_n78A-n79A | Rel-15 | | | +| DC_20A_n28A-n78A | Rel-15 | | | +| DC_21A_n1A-n78A | Rel-17 | | | +| DC_21A_n1A-n79A | Rel-17 | | | +| DC_21A_n28A-n77A | Rel-17 | | | +| DC_21A_n28A-n78A | Rel-17 | | | +| DC_21A_n28A-n79A | Rel-17 | | | +| DC_21A-42A_n1A | Rel-17 | | | +| DC_21A-42C_n1A | Rel-17 | | | +| DC_21A-42A_n78A | Rel-15 | | | +| DC_21A-42C_n78A | Rel-15 | | | +| DC_21A-42A_n79A | Rel-15 | | | + +| | | | | +|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--| +| DC_21A-42C_n79A | Rel-15 | | | +| DC_21A_n78A-n79A | Rel-15 | | | +| DC_28A_n7A-n78A | Rel-16 | | | +| DC_66A_n2A-n77A | Rel-17 | | | +| DC_66A_n5A-n77A | Rel-17 | | | +| DC_66A-(n)71AA | Rel-15 | | | +| Note 1: | Notation used for inter-band EN-DC Bands is according to TS 38.101-3 [25] Table 5.5B.4.2-1, e.g. 'DC_1A-3C_n78A' indicates EN-DC operation on E-UTRA CA configuration CA_1A-3C with E-UTRA DL Bandwidth Classes A, C for the E-UTRA bands 1 and 3 respectively and NR band n78 with NR DL CA Bandwidth Class A. | | | +| Note 2: | See UL_nCC( table_index ) in Note 2 of Table 4.0-3 in TS 38.522 [9]. | | | +| Note 3: | See DL_nCC( table_index ) in Note 4 of Table 4.0-3 in TS 38.522 [9]. | | | +| Note 4: | See UL_NR_nCC( table_index ) in Note 3 of Table 4.0-3 in TS 38.522 [9]. | | | +| Note 5: | See DL_NR_nCC( table_index ) in Note 5 of Table 4.0-3 in TS 38.522 [9]. | | | + +**Table A.4.3.2B.2.3.2-3: Inter-band EN-DC within FR1 (three bands) PC2 UE RF Baseline Implementation Capabilities** + +| Item | EN-DC configuration | Inter-band EN-DC within FR1 (three bands) PC2 UE RF Baseline Implementation Capabilities | Ref. | Release | Mnemonic | Comments | +|------|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------|--------------------------------------|----------| +| 1 | DC_1A-3A_n78A | LTE Frequency band 1: 1920-1980 MHz (UL), 2110- 2170 MHz (DL)
LTE Frequency band 3: 1710-1785 MHz (UL), 1805-1880 MHz (DL)
NR Frequency band n78: 3300-3800 MHz | 38.101-3,
6.2B.1.3 | Rel-18 | pc_Band1_Band3_nrBand78_PCS2_Supp | | +| 2 | DC_1A-3A_n79A | LTE Frequency band 1: 1920-1980 MHz (UL), 2110- 2170 MHz (DL)
LTE Frequency band 3: 1710-1785 MHz (UL), 1805-1880 MHz (DL)
NR Frequency band n79: 4400-5000 MHz | 38.101-3,
6.2B.1.3 | Rel-18 | pc_Band1_Band3_nrBand79_PCS2_Supp | | +| 3 | DC_1A-19A_n78A | LTE Frequency band 1: 1920-1980 MHz (UL), 2110- 2170 MHz (DL)
LTE Frequency band 19: 830-845 MHz (UL), 875-890 MHz (DL)
NR Frequency band n78: 3300-3800 MHz | 38.101-3,
6.2B.1.3 | Rel-18 | pc_Band1_Band19_nrBand78_PCS2_Supp | | +| 4 | DC_1A-19A_n79A | LTE Frequency band 1: 1920-1980 MHz (UL), 2110- 2170 MHz (DL)
LTE Frequency band 19: 830-845 MHz (UL), 875-890 MHz (DL)
NR Frequency band n79: 4400-5000 MHz | 38.101-3,
6.2B.1.3 | Rel-18 | pc_Band1_Band19_nrBand79_PCS2_Supp | | +| 5 | DC_1A-21A_n78A | LTE Frequency band 1: 1920-1980 MHz (UL), 2110- 2170 MHz (DL)
LTE Frequency band 21: 1447.9-1462.9 MHz (UL), 1495.9-1510.9 MHz (DL)
NR Frequency band n78: 3300-3800 MHz | 38.101-3,
6.2B.1.3 | Rel-18 | pc_Band1_Band21_nrBand78_PCS2_Supp | | +| 6 | DC_1A-21A_n79A | LTE Frequency band 1: 1920-1980 MHz (UL), 2110- 2170 MHz (DL)
LTE Frequency band 21: 1447.9-1462.9 MHz (UL), 1495.9-1510.9 MHz (DL)
NR Frequency band n79: 4400-5000 MHz | 38.101-3,
6.2B.1.3 | Rel-18 | pc_Band1_Band21_nrBand79_PCS2_Supp | | +| 7 | DC_1A-42A_n79A | LTE Frequency band 1: 1920-1980 MHz (UL), 2110- 2170 MHz (DL)
LTE Frequency band 42: 3400-3600 MHz
NR Frequency band n79: 4400-5000 MHz | 38.101-3,
6.2B.1.3 | Rel-18 | pc_Band1_Band42_nrBand79_PCS2_Supp | | +| 8 | DC_1A_n78A-n79A | LTE Frequency band 1: 1920-1980 MHz (UL), 2110- 2170 MHz (DL)
NR Frequency band n78: 3300-3800 MHz
NR Frequency band n79: 4400-5000 MHz | 38.101-3,
6.2B.1.3 | Rel-18 | pc_Band1_nrBand78_nrBand79_PCS2_Supp | | +| 9 | DC_3A-19A_n78A | LTE Frequency band 3: 1710-1785 MHz (UL), 1805-1880 MHz (DL)
LTE Frequency band 19: 830-845 MHz (UL), 875-890 MHz (DL)
NR Frequency band n78: 3300-3800 MHz | 38.101-3,
6.2B.1.3 | Rel-18 | pc_Band3_Band19_nrBand78_PCS2_Supp | | + +| | | | | | | | +|----|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------|---------------------------------------|--| +| 10 | DC_3A-19A_n79A | LTE Frequency band 3: 1710-1785 MHz (UL), 1805-1880 MHz (DL)
LTE Frequency band 19: 830-845 MHz (UL), 875-890 MHz (DL)
NR Frequency band n79: 4400-5000 MHz | 38.101-3,
6.2B.1.3 | Rel-18 | pc_Band3_Band19_nrBand79_PCS2_Supp | | +| 11 | DC_3A-21A_n78A | LTE Frequency band 3: 1710-1785 MHz (UL), 1805-1880 MHz (DL)
LTE Frequency band 21: 1447.9-1462.9 MHz (UL), 1495.9-1510.9 MHz (DL)
NR Frequency band n78: 3300-3800 MHz | 38.101-3,
6.2B.1.3 | Rel-18 | pc_Band3_Band21_nrBand78_PCS2_Supp | | +| 12 | DC_3A-21A_n79A | LTE Frequency band 3: 1710-1785 MHz (UL), 1805-1880 MHz (DL)
LTE Frequency band 21: 1447.9-1462.9 MHz (UL), 1495.9-1510.9 MHz (DL)
NR Frequency band n79: 4400-5000 MHz | 38.101-3,
6.2B.1.3 | Rel-18 | pc_Band3_Band21_nrBand79_PCS2_Supp | | +| 13 | DC_3A-42A_n79A | LTE Frequency band 3: 1710-1785 MHz (UL), 1805-1880 MHz (DL)
LTE Frequency band 42: 3400-3600 MHz
NR Frequency band n79: 4400-5000 MHz | 38.101-3,
6.2B.1.3 | Rel-18 | pc_Band3_Band42_nrBand79_PCS2_Supp | | +| 14 | DC_3A_n78A-n79A | LTE Frequency band 3: 1710-1785 MHz (UL), 1805-1880 MHz (DL)
NR Frequency band n78: 3300-3800 MHz
NR Frequency band n79: 4400-5000 MHz | 38.101-3,
6.2B.1.3 | Rel-18 | pc_Band3_nrBand78_nrBand79_PCS2_Supp | | +| 15 | DC_19A-21A_n78A | LTE Frequency band 19: 830-845 MHz (UL), 875-890 MHz (DL)
LTE Frequency band 21: 1447.9-1462.9 MHz (UL), 1495.9-1510.9 MHz (DL)
NR Frequency band n78: 3300-3800 MHz | 38.101-3,
6.2B.1.3 | Rel-18 | pc_Band19_Band21_nrBand78_PCS2_Supp | | +| 16 | DC_19A-21A_n79A | LTE Frequency band 19: 830-845 MHz (UL), 875-890 MHz (DL)
LTE Frequency band 21: 1447.9-1462.9 MHz (UL), 1495.9-1510.9 MHz (DL)
NR Frequency band n79: 4400-5000 MHz | 38.101-3,
6.2B.1.3 | Rel-18 | pc_Band19_Band21_nrBand79_PCS2_Supp | | +| 17 | DC_19A-42A_n79A | LTE Frequency band 19: 830-845 MHz (UL), 875-890 MHz (DL)
LTE Frequency band 42: 3400-3600 MHz
NR Frequency band n79: 4400-5000 MHz | 38.101-3,
6.2B.1.3 | Rel-18 | pc_Band19_Band42_nrBand79_PCS2_Supp | | +| 18 | DC_19A_n78A-n79A | LTE Frequency band 19: 830-845 MHz (UL), 875-890 MHz (DL)
NR Frequency band n78: 3300-3800 MHz
NR Frequency band n79: 4400-5000 MHz | 38.101-3,
6.2B.1.3 | Rel-18 | pc_Band19_nrBand78_nrBand79_PCS2_Supp | | + +| | | | | | | | +|----|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------|--------------------------------------|--| +| 19 | DC_21A-42A_n79A | LTE Frequency band 21: 1447.9-1462.9 MHz (UL), 1495.9-1510.9 MHz (DL)
LTE Frequency band 42: 3400-3600 MHz
NR Frequency band n79: 4400-5000 MHz | 38.101-3,
6.2B.1.3 | Rel-18 | pc_Band21_Band42_nrBand79_PC2_Supp | | +| 20 | DC_21A_n78A-n79A | LTE Frequency band 21: 1447.9-1462.9 MHz (UL), 1495.9-1510.9 MHz (DL)
NR Frequency band n78: 3300-3800 MHz
NR Frequency band n79: 4400-5000 MHz | 38.101-3,
6.2B.1.3 | Rel-18 | pc_Band21_nrBand78_nrBand79_PC2_Supp | | + +###### A.4.3.2B.2.3.3 Inter-band EN-DC within FR1 (four bands) + +**Table A.4.3.2B.2.3.3-1: Downlink Bandwidth Class Combination capabilities for Inter-band EN-DC within FR1 and four bands (for one or more of the supported DC configurations in Table A.4.3.2B.2.3.3-2)** + +| Item | DL inter-band EN-DC within FR1 Bandwidth Class | Ref. | Mnemonic | Comments | +|------|--------------------------------------------------------------------------|-----------------------------------------|------------------------------------------------|----------| +| 1 | Inter-band EN-DC within FR1 BW Class Combination A-A-A_A (four bands) | 36.101, 5.6A.1
38.101-1,
5.5B.4.3 | pc_DL_inter_band_EN_DC_FR1_4B_Class_A-A-A_A | | +| 2 | Inter-band EN-DC within FR1 BW Class Combination A-A-C_A (four bands) | 36.101, 5.6A.1
38.101-1,
5.5B.4.3 | pc_DL_inter_band_EN_DC_FR1_4B_Class_A-A-C_A | | +| 3 | Inter-band EN-DC within FR1 BW Class Combination A-A-D_A (four bands) | 36.101, 5.6A.1
38.101-1,
5.5B.4.3 | pc_DL_inter_band_EN_DC_FR1_4B_Class_A-A-D_A | | +| 4 | Inter-band EN-DC within FR1 BW Class Combination A-C-A_A (four bands) | 36.101, 5.6A.1
38.101-1,
5.5B.4.3 | pc_DL_inter_band_EN_DC_FR1_4B_Class_A-C-A_A | | +| 5 | Inter-band EN-DC within FR1 BW Class Combination A-(2A)-A_A (four bands) | 36.101, 5.6A.1
38.101-1,
5.5B.4.3 | pc_DL_inter_band_EN_DC_FR1_4B_Class_A-(2A)-A_A | | +| 6 | Inter-band EN-DC within FR1 BW Class Combination A-A_A_A (four bands) | 36.101, 5.6A.1
38.101-1,
5.5B.4.3 | pc_DL_inter_band_EN_DC_FR1_4B_Class_A-A_A_A | | +| 7 | Inter-band EN-DC within FR1 BW Class Combination A-C_A_A (four bands) | 36.101, 5.6A.1
38.101-1,
5.5B.4.3 | pc_DL_inter_band_EN_DC_FR1_4B_Class_A-C_A_A | | +| 8 | Inter-band EN-DC within FR1 BW Class Combination A_A_(n)AA (four bands) | 36.101, 5.6A.1
38.101-1,
5.5B.4.3 | pc_DL_inter_band_EN_DC_FR1_4B_Class_A_A_(n)AA | | + +**Table A.4.3.2B.2.3.3-1a: Uplink Bandwidth Class Combination capabilities for Inter-band EN-DC within FR1 and four bands (for one or more of the supported configurations in Table A.4.3.2B.2.3.3-2 )** + +| Item | UL inter-band EN-DC within FR1 Bandwidth Class | Ref. | Mnemonic | Comments | +|------|------------------------------------------------------------------------|-----------------------------------------|---------------------------------------------------|----------| +| 1 | UL Inter-band EN-DC within FR1 BW Class Combination A_A (four bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.3 | pc_UL_inter_band
_EN_DC_FR1_4B
_Class_A_A | | +| 2 | UL Inter-band EN-DC within FR1 BW Class Combination A_B (four bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.3 | pc_UL_inter_band
_EN_DC_FR1_4B
_Class_A_B | | +| 3 | UL Inter-band EN-DC within FR1 BW Class Combination (n)AA (four bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.3 | pc_UL_inter_band
_EN_DC_FR1_4B
_Class_(n)AA | | +| 4 | UL Inter-band EN-DC within FR1 BW Class Combination C_A (four bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.3 | pc_UL_inter_band
_EN_DC_FR1_4B
_Class_C_A | | +| 5 | UL Inter-band EN-DC within FR1 BW Class Combination C_B (four bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.3 | pc_UL_inter_band
_EN_DC_FR1_4B
_Class_C_B | | + +**Table A.4.3.2B.2.3.3-2: Supported Inter-band EN-DC configurations within FR1 (four bands)** + +| EN-DC configuration / Item
(Note 1, 3, 5) | Release | Supported | Supported EN-DC
Bandwidth Class(es) in UL
(Note 2, 4) | +|----------------------------------------------|---------|-----------|-------------------------------------------------------------| +| DC_1A-3A-7A_n28A | Rel-15 | | | +| DC_1A-3A-7A_n78A | Rel-15 | | | +| DC_1A-3A-8A_n77A | Rel-16 | | | +| DC_1A-3A-8A_n77(2A) | Rel-16 | | | +| DC_1A-3A-8A_n78A | Rel-15 | | | +| DC_1A-3A-19A_n77(2A) | Rel-17 | | | +| DC_1A-3A-19A_n78A | Rel-15 | | | +| DC_1A-3A-19A_n78(2A) | Rel-17 | | | +| DC_1A-3A-19A_n79A | Rel-15 | | | +| DC_1A-3A-20A_n28A | Rel-15 | | | +| DC_1A-3A-20A_n78A | Rel-15 | | | +| DC_1A-3A-21A_n77(2A) | Rel-17 | | | +| DC_1A-3A-21A_n78A | Rel-15 | | | +| DC_1A-3A-21A_n78(2A) | Rel-17 | | | +| DC_1A-3A-21A_n79A | Rel-15 | | | +| DC_1A-3A-28A_n78A | Rel-15 | | | +| DC_1A-3A_n28A-n78A | Rel-15 | | | +| DC_1A-3A-42A_n78A | Rel-15 | | | +| DC_1A-3A-42C_n78A | Rel-15 | | | +| DC_1A-3A-42D_n78A | Rel-16 | | | +| DC_1A-3A-42D_n79A | Rel-16 | | | +| DC_1A-3A-42A_n79A | Rel-15 | | | +| DC_1A-3A-42C_n79A | Rel-15 | | | +| DC_1A-3C-8A_n77A | Rel-17 | | | +| DC_1A-3C-8A_n77(2A) | Rel-17 | | | +| DC_1A-7A_n28A-n78A | Rel-15 | | | +| DC_1A-7A-20A_n28A | Rel-15 | | | +| DC_1A-7A-20A_n78A | Rel-15 | | | +| DC_1A-7A-28A_n78A | Rel-16 | | | +| DC_1A-19A-21A_n77(2A) | Rel-17 | | | +| DC_1A-19A-21A_n78A | Rel-15 | | | +| DC_1A-19A-21A_n78(2A) | Rel-17 | | | +| DC_1A-19A-21A_n79A | Rel-15 | | | +| DC_1A-19A-42A_n78A | Rel-15 | | | +| DC_1A-19A-42C_n78A | Rel-15 | | | +| DC_1A-19A-42A_n79A | Rel-15 | | | +| DC_1A-19A-42C_n79A | Rel-15 | | | +| DC_1A-20A_n28A-n78A | Rel-15 | | | +| DC_1A-21A-42A_n78A | Rel-15 | | | +| DC_1A-21A-42C_n78A | Rel-15 | | | +| DC_1A-21A-42A_n79A | Rel-15 | | | +| DC_1A-21A-42C_n79A | Rel-15 | | | +| DC_2A-2A-14A-66A_n66A | Rel-16 | | | +| DC_2A-7A-7A-13A_n66A | Rel-16 | | | +| DC_2A-7A-7A-66A_n66A | Rel-16 | | | +| DC_2A-7A-7A-66A_n78A | Rel-16 | | | +| DC_2A-7A-13A_n66A | Rel-16 | | | +| DC_2A-7A-66A_n66A | Rel-16 | | | +| DC_2A-7C-13A_n66A | Rel-16 | | | +| DC_2A-7C-66A_n66A | Rel-16 | | | +| DC_2A-7C-66A_n78A | Rel-16 | | | +| DC_2A-13A-66A_n77A | Rel-17 | | | + +| | | | | +|-----------------------|--------|--|--| +| DC_2A-14A-66A_n2A | Rel-16 | | | +| DC_2A-14A-66A_n66A | Rel-16 | | | +| DC_2A-14A-66A-66A_n2A | Rel-16 | | | +| DC_2A-66A_n5A-n77A | Rel-17 | | | +| DC_2A-66A-(n)71AA | Rel-15 | | | +| DC_3A-7A-20A_n1A | Rel-16 | | | +| DC_3A-7A-20A_n8A | Rel-16 | | | +| DC_3A-7A-20A_n28A | Rel-15 | | | +| DC_3A-7A-20A_n78A | Rel-15 | | | +| DC_3A-7A-28A_n78A | Rel-15 | | | +| DC_3A-7A_n28A-n78A | Rel-15 | | | +| DC_3A-19A_n1A-n78A | Rel-17 | | | +| DC_3A-19A_n1A-n79A | Rel-17 | | | +| DC_3A-19A-21A_n78A | Rel-15 | | | +| DC_3A-19A-21A_n79A | Rel-15 | | | +| DC_3A-19A-42A_n1A | Rel-17 | | | +| DC_3A-19A-42C_n1A | Rel-17 | | | +| DC_3A-19A-42A_n78A | Rel-15 | | | +| DC_3A-19A-42C_n78A | Rel-15 | | | +| DC_3A-19A-42A_n79A | Rel-15 | | | +| DC_3A-19A-42C_n79A | Rel-15 | | | +| DC_3A-20A_n28A-n78A | Rel-15 | | | +| DC_3A-21A_n1A-n78A | Rel-17 | | | +| DC_3A-21A_n1A-n79A | Rel-17 | | | +| DC_3A-21A-42A_n78A | Rel-15 | | | +| DC_3A-21A-42C_n78A | Rel-15 | | | +| DC_3A-21A-42A_n79A | Rel-15 | | | +| DC_3A-21A-42C_n79A | Rel-15 | | | +| DC_3A-42A_n1A-n78A | Rel-17 | | | +| DC_3A-42C_n1A-n78A | Rel-17 | | | +| DC_3A-42A_n1A-n79A | Rel-17 | | | +| DC_3A-42C_n1A-n79A | Rel-17 | | | +| DC_7A-20A_n28A-n78A | Rel-15 | | | +| DC_13A-66A_n2A-n77A | Rel-17 | | | +| DC_19A-21A_n1A-n78A | Rel-17 | | | +| DC_19A-21A_n1A-n79A | Rel-17 | | | +| DC_19A-21A-42A_n1A | Rel-17 | | | +| DC_19A-21A-42C_n1A | Rel-17 | | | +| DC_19A-21A-42A_n78A | Rel-15 | | | +| DC_19A-21A-42C_n78A | Rel-15 | | | +| DC_19A-21A-42A_n79A | Rel-15 | | | +| DC_19A-21A-42C_n79A | Rel-15 | | | +| DC_19A-42A_n1A-n78A | Rel-17 | | | +| DC_19A-42C_n1A-n78A | Rel-17 | | | +| DC_19A-42A_n1A-n79A | Rel-17 | | | +| DC_19A-42C_n1A-n79A | Rel-17 | | | +| DC_21A-42A_n1A-n78A | Rel-17 | | | +| DC_21A-42C_n1A-n78A | Rel-17 | | | +| DC_21A-42A_n1A-n79A | Rel-17 | | | +| DC_21A-42C_n1A-n79A | Rel-17 | | | + +| | | +|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Note 1: | Notation used for inter-band EN-DC Bands is according to TS 38.101-3 [25] Table 5.5B.4.3-1, e.g. 'DC_2A-7C-13A_n66A' indicates EN-DC operation on E-UTRA CA configuration CA_2A-7C-13A with E-UTRA DL Bandwidth Classes A, C, A for the E-UTRA bands 2, 7 and 13 respectively and NR band n66 with NR DL CA Bandwidth Class A. | +| Note 2: | See UL_nCC( table_index ) in Note 2 of Table 4.0-3 in TS 38.522 [9]. | +| Note 3: | See DL_nCC( table_index ) in Note 4 of Table 4.0-3 in TS 38.522 [9]. | +| Note 4: | See UL_NR_nCC( table_index ) in Note 3 of Table 4.0-3 in TS 38.522 [9]. | +| Note 5: | See DL_NR_nCC( table_index ) in Note 5 of Table 4.0-3 in TS 38.522 [9]. | + +###### A.4.3.2B.2.3.4 Inter-band EN-DC within FR1 (five bands) + +**Table A.4.3.2B.2.3.4-1: Downlink Bandwidth Class Combination capabilities for Inter-band EN-DC within FR1 and five bands (for one or more of the supported DC configurations in Table A.4.3.2B.2.3.4-2)** + +| Item | DL inter-band EN-DC within FR1 Bandwidth Class | Ref. | Mnemonic | Comments | +|------|-------------------------------------------------------------------------|-----------------------------------------|-----------------------------------------------------------|----------| +| 1 | Inter-band EN-DC within FR1 BW Class Combination A-A-A-A_A (five bands) | 36.101, 5.6A.1
38.101-1,
5.5B.4.4 | pc_DL_inter_band
_EN_DC_FR1_5B
_Class_A-A-A-
A_A | | +| 2 | Inter-band EN-DC within FR1 BW Class Combination A-A-A_A-A (five bands) | 36.101, 5.6A.1
38.101-1,
5.5B.4.4 | pc_DL_inter_band
_EN_DC_FR1_5B
_Class_A-A-A_A-
A | | +| 3 | Inter-band EN-DC within FR1 BW Class Combination A-A-A-C_A (five bands) | 36.101, 5.6A.1
38.101-1,
5.5B.4.4 | pc_DL_inter_band
_EN_DC_FR1_5B
_Class_A-A-A-
C_A | | +| 4 | Inter-band EN-DC within FR1 BW Class Combination A-A-C-A_A (five bands) | 36.101, 5.6A.1
38.101-1,
5.5B.4.4 | pc_DL_inter_band
_EN_DC_FR1_5B
_Class_A-A-C-
A_A | | +| 5 | Inter-band EN-DC within FR1 BW Class Combination A-A-C_A-A (five bands) | 36.101, 5.6A.1
38.101-1,
5.5B.4.4 | pc_DL_inter_band
_EN_DC_FR1_5B
_Class_A-A-C_A-
A | | +| 6 | Inter-band EN-DC within FR1 BW Class Combination A-C-A-A_A (five bands) | 36.101, 5.6A.1
38.101-1,
5.5B.4.4 | pc_DL_inter_band
_EN_DC_FR1_5B
_Class_A-C-A-
A_A | | +| 7 | Inter-band EN-DC within FR1 BW Class Combination C-A-A-A_A (five bands) | 36.101, 5.6A.1
38.101-1,
5.5B.4.4 | pc_DL_inter_band
_EN_DC_FR1_5B
_Class_C-A-A-
A_A | | + +**Table A.4.3.2B.2.3.4-1a: Uplink Bandwidth Class Combination capabilities for Inter-band EN-DC within FR1 and five bands (for one or more of the supported configurations in Table A.4.3.2B.2.3.4-2 )** + +| Item | UL inter-band EN-DC within FR1 Bandwidth Class | Ref. | Mnemonic | Comments | +|------|----------------------------------------------------------------------|-----------------------------------------|-------------------------------------------------|----------| +| 1 | UL Inter-band EN-DC within FR1 BW Class Combination A_A (five bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.4 | pc_UL_inter_band
_EN_DC_FR1_5B
_Class_A_A | | +| 2 | UL Inter-band EN-DC within FR1 BW Class Combination A_B (five bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.4 | pc_UL_inter_band
_EN_DC_FR1_5B
_Class_A_B | | +| 3 | UL Inter-band EN-DC within FR1 BW Class Combination C_A (five bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.4 | pc_UL_inter_band
_EN_DC_FR1_5B
_Class_C_A | | +| 4 | UL Inter-band EN-DC within FR1 BW Class Combination C_B (five bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4.4 | pc_UL_inter_band
_EN_DC_FR1_5B
_Class_C_B | | + +**Table A.4.3.2B.2.3.4-2: Supported Inter-band EN-DC configurations within FR1 (five bands)** + +| EN-DC configuration / Item
(Note 1, 3, 5) | Release | Supported EN-DC | | +|----------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|------------------------------------------| +| | | Supported | Bandwidth Class(es) in UL
(Note 2, 4) | +| DC_1A-3A-7A-20A_n28A | Rel-15 | | | +| DC_1A-3A-7A-20A_n78A | Rel-15 | | | +| DC_1A-3A-7A-28A_n78A | Rel-16 | | | +| DC_1A-3A-7A_n28A-n78A | Rel-15 | | | +| DC_1A-3A-19A-42A_n78A | Rel-15 | | | +| DC_1A-3A-19A-42C_n78A | Rel-15 | | | +| DC_1A-3A-19A-42A_n79A | Rel-15 | | | +| DC_1A-3A-19A-42C_n79A | Rel-15 | | | +| DC_1A-3A-20A_n28A-n78A | Rel-15 | | | +| DC_1A-3A-21A-42A_n78A | Rel-15 | | | +| DC_1A-3A-21A-42C_n78A | Rel-15 | | | +| DC_1A-3A-21A-42A_n79A | Rel-15 | | | +| DC_1A-3A-21A-42C_n79A | Rel-15 | | | +| DC_1A-7A-20A_n28A-n78A | Rel-15 | | | +| DC_1A-19A-21A-42A_n78A | Rel-15 | | | +| DC_1A-19A-21A-42C_n78A | Rel-15 | | | +| DC_1A-19A-21A-42A_n79A | Rel-15 | | | +| DC_1A-19A-21A-42C_n79A | Rel-15 | | | +| DC_3A-7A-20A_n28A-n78A | Rel-15 | | | +| DC_3A-19A-21A-42A_n78A | Rel-16 | | | +| DC_3A-19A-21A-42C_n78A | Rel-16 | | | +| DC_3A-19A-21A-42A_n79A | Rel-16 | | | +| DC_3A-19A-21A-42C_n79A | Rel-16 | | | +| DC_3A-19A-42A_n1A-n78A | Rel-17 | | | +| DC_3A-19A-42C_n1A-n78A | Rel-17 | | | +| DC_3A-19A-42A_n1A-n79A | Rel-17 | | | +| DC_3A-19A-42C_n1A-n79A | Rel-17 | | | +| DC_3A-21A-42A_n1A-n78A | Rel-17 | | | +| DC_3A-21A-42C_n1A-n78A | Rel-17 | | | +| DC_3A-21A-42A_n1A-n79A | Rel-17 | | | +| DC_3A-21A-42C_n1A-n79A | Rel-17 | | | +| DC_19A-21A-42A_n1A-n78A | Rel-17 | | | +| DC_19A-21A-42C_n1A-n78A | Rel-17 | | | +| DC_19A-21A-42A_n1A-n79A | Rel-17 | | | +| DC_19A-21A-42C_n1A-n79A | Rel-17 | | | +| Note 1: | Notation used for inter-band EN-DC Bands is according to TS 38.101-3 [25] Table 5.5B.4.4-1, e.g. 'DC_1A-3A-5A-41A_n79A' indicates EN-DC operation on E-UTRA CA configuration CA_1A-3A-5A-41A with E-UTRA DL Bandwidth Classes A for all the E-UTRA bands 1, 3, 5 and 41 and NR band n79 with NR DL CA Bandwidth Class A. | | | +| Note 2: | See UL_nCC( table_index ) in Note 2 of Table 4.0-3 in TS 38.522 [9]. | | | +| Note 3: | See DL_nCC( table_index ) in Note 4 of Table 4.0-3 in TS 38.522 [9]. | | | +| Note 4: | See UL_NR_nCC( table_index ) in Note 3 of Table 4.0-3 in TS 38.522 [9]. | | | +| Note 5: | See DL_NR_nCC( table_index ) in Note 5 of Table 4.0-3 in TS 38.522 [9]. | | | + +###### A.4.3.2B.2.3.5 Inter-band EN-DC within FR1 (six bands) + +**Table A.4.3.2B.2.3.5-1: Downlink Bandwidth Class Combination capabilities for Inter-band EN-DC within FR1 and six bands (for one or more of the supported DC configurations in Table A.4.3.2B.2.3.5-2)** + +| Item | DL inter-band EN-DC within FR1 Bandwidth Class | Ref. | Mnemonic | Comments | +|------|---------------------------------------------------------------------------|-----------------------------------------|-------------------------------------------------------------|----------| +| 1 | EN-DC Inter-band with NR FR1 BW Class Combination A-A-A-A_A-A (six bands) | 36.101, 5.6A.1
38.101-1,
5.5B.4.5 | pc_DL_inter_band
_EN_DC_FR1_6B
_Class_A-A-A-
A_A-A | | +| 2 | EN-DC Inter-band with NR FR1 BW Class Combination A-A-C-A_A-A (six bands) | 36.101, 5.6A.1
38.101-1,
5.5B.4.5 | pc_DL_inter_band
_EN_DC_FR1_6B
_Class_A-A-C-
A_A-A | | +| 3 | EN-DC Inter-band with NR FR1 BW Class Combination A-C-A-A_A-A (six bands) | 36.101, 5.6A.1
38.101-1,
5.5B.4.5 | pc_DL_inter_band
_EN_DC_FR1_6B
_Class_A-C-A-
A_A-A | | +| 4 | EN-DC Inter-band with NR FR1 BW Class Combination A-C-C-A_A-A (six bands) | 36.101, 5.6A.1
38.101-1,
5.5B.4.5 | pc_DL_inter_band
_EN_DC_FR1_6B
_Class_A-C-C-
A_A-A | | + +**Table A.4.3.2B.2.3.5-1a: Uplink Bandwidth Class Combination capabilities for Inter-band EN-DC within FR1 and six bands (for one or more of the supported configurations in Table A.4.3.2B.2.3.5-2)** + +| Item | UL inter-band EN-DC within FR1 Bandwidth Class | Ref. | Mnemonic | Comments | +|------|---------------------------------------------------------------------|-----------------------------------------|-------------------------------------------------|----------| +| 1 | UL Inter-band EN-DC within FR1 BW Class Combination A_A (six bands) | 36.101, 5.6A.1
38.101-1,
5.5B.4.5 | pc_UL_inter_band
_EN_DC_FR1_6B
_Class_A_A | | +| 2 | UL Inter-band EN-DC within FR1 BW Class Combination C_A (six bands) | 36.101, 5.6A.1
38.101-1,
5.5B.4.5 | pc_UL_inter_band
_EN_DC_FR1_6B
_Class_C_A | | + +**Table A.4.3.2B.2.3.5-2: Supported Inter-band EN-DC configurations within FR1 (six bands)** + +| EN-DC configuration / Item
(Note 1, 3, 5) | Release | Supported | Supported EN-DC
Bandwidth Class(es) in UL
(Note 2, 4) | +|----------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-------------------------------------------------------------| +| DC_1A-3A-7A-20A_n28A-n78A | Rel-15 | | | +| Note 1: | Notation used for inter-band EN-DC Bands is according to TS 38.101-3 [25] Table 5.5B.4.5-1, e.g. 'DC_1A-3A-7A-20A_n28A-n78A' indicates EN-DC operation on E-UTRA CA configuration CA_1A-3A-7A-20A with E-UTRA DL Bandwidth Class A for all the E-UTRA bands 1, 3, 7 and 20 and NR CA configuration CA_n28A-n78A with NR DL CA Bandwidth Class A for all the NR bands n28 and n78. | | | +| Note 2: | See UL_nCC( table_index ) in Note 2 of Table 4.0-3 in TS 38.522 [9]. | | | +| Note 3: | See DL_nCC( table_index ) in Note 4 of Table 4.0-3 in TS 38.522 [9]. | | | +| Note 4: | See UL_NR_nCC( table_index ) in Note 3 of Table 4.0-3 in TS 38.522 [9]. | | | +| Note 5: | See DL_NR_nCC( table_index ) in Note 5 of Table 4.0-3 in TS 38.522 [9]. | | | + +A.4.3.2B.2.3.6 Inter-band EN-DC including FR2 (two bands) + +**Table A.4.3.2B.2.3.6-1: Downlink Bandwidth Class Combination capabilities for Inter-band EN-DC including FR2 and two bands (for one or more of the supported DC configurations in Table A.4.3.2B.2.3.6-2)** + +| Item | DL inter-band EN-DC including FR2 Bandwidth Class | Ref. | Mnemonic | Comments | +|------|------------------------------------------------------------------------|-----------------------------------------|----------------------------------------------------|----------| +| 1 | Inter-band EN-DC including FR2 BW Class Combination A_A (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.1 | pc_DL_inter_band
_EN_DC_FR2_2B
_Class_A_A | | +| 2 | Inter-band EN-DC including FR2 BW Class Combination A_B (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.1 | pc_DL_inter_band
_EN_DC_FR2_2B
_Class_A_B | | +| 3 | Inter-band EN-DC including FR2 BW Class Combination A_C (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.1 | pc_DL_inter_band
_EN_DC_FR2_2B
_Class_A_C | | +| 4 | Inter-band EN-DC including FR2 BW Class Combination A_D (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.1 | pc_DL_inter_band
_EN_DC_FR2_2B
_Class_A_D | | +| 5 | Inter-band EN-DC including FR2 BW Class Combination A_E (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.1 | pc_DL_inter_band
_EN_DC_FR2_2B
_Class_A_E | | +| 6 | Inter-band EN-DC including FR2 BW Class Combination A_F (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.1 | pc_DL_inter_band
_EN_DC_FR2_2B
_Class_A_F | | +| 7 | Inter-band EN-DC including FR2 BW Class Combination A_G (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.1 | pc_DL_inter_band
_EN_DC_FR2_2B
_Class_A_G | | +| 8 | Inter-band EN-DC including FR2 BW Class Combination A_H (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.1 | pc_DL_inter_band
_EN_DC_FR2_2B
_Class_A_H | | +| 9 | Inter-band EN-DC including FR2 BW Class Combination A_I (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.1 | pc_DL_inter_band
_EN_DC_FR2_2B
_Class_A_I | | +| 10 | Inter-band EN-DC including FR2 BW Class Combination A_J (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.1 | pc_DL_inter_band
_EN_DC_FR2_2B
_Class_A_J | | +| 11 | Inter-band EN-DC including FR2 BW Class Combination A_K (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.1 | pc_DL_inter_band
_EN_DC_FR2_2B
_Class_A_K | | +| 12 | Inter-band EN-DC including FR2 BW Class Combination A_L (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.1 | pc_DL_inter_band
_EN_DC_FR2_2B
_Class_A_L | | +| 13 | Inter-band EN-DC including FR2 BW Class Combination A_M (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.1 | pc_DL_inter_band
_EN_DC_FR2_2B
_Class_A_M | | +| 14 | Inter-band EN-DC including FR2 BW Class Combination A_O (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.1 | pc_DL_inter_band
_EN_DC_FR2_2B
_Class_A_O | | +| 15 | Inter-band EN-DC including FR2 BW Class Combination A_P (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.1 | pc_DL_inter_band
_EN_DC_FR2_2B
_Class_A_P | | +| 16 | Inter-band EN-DC including FR2 BW Class Combination A_Q (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.1 | pc_DL_inter_band
_EN_DC_FR2_2B
_Class_A_Q | | +| 17 | Inter-band EN-DC including FR2 BW Class Combination (2A)_A (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.1 | pc_DL_inter_band
_EN_DC_FR2_2B
_Class_(2A)_A | | +| 18 | Inter-band EN-DC including FR2 BW Class Combination C_A (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.1 | pc_DL_inter_band
_EN_DC_FR2_2B
_Class_C_A | | +| 19 | Inter-band EN-DC including FR2 BW Class Combination C_E (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.1 | pc_DL_inter_band
_EN_DC_FR2_2B
_Class_C_E | | + +| | | | | | +|----|---------------------------------------------------------------------|-----------------------------------------|-------------------------------------------------|--| +| 20 | Inter-band EN-DC including FR2 BW Class Combination C_F (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.1 | pc_DL_inter_band
_EN_DC_FR2_2B
_Class_C_F | | +| 21 | Inter-band EN-DC including FR2 BW Class Combination D_A (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.1 | pc_DL_inter_band
_EN_DC_FR2_2B
_Class_D_A | | +| 22 | Inter-band EN-DC including FR2 BW Class Combination E_A (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.1 | c_DL_inter_band_
EN_DC_FR2_2B_
Class_E_A | | + +**Table A.4.3.2B.2.3.6-1a: Uplink Bandwidth Class Combination capabilities for Inter-band EN-DC including FR2 and two bands (for one or more of the supported DC configurations in Table A.4.3.2B.2.3.6-2)** + +| Item | UL inter-band EN-DC including FR2 Bandwidth Class | Ref. | Mnemonic | Comments | +|------|------------------------------------------------------------------------|-----------------------------------------|-------------------------------------------------|----------| +| 1 | UL Inter-band EN-DC including FR2 BW Class Combination A_A (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.1 | pc_UL_inter_band
_EN_DC_FR2_2B
_Class_A_A | | +| 2 | UL Inter-band EN-DC including FR2 BW Class Combination A_D (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.1 | pc_UL_inter_band
_EN_DC_FR2_2B
_Class_A_D | | +| 3 | UL Inter-band EN-DC including FR2 BW Class Combination A_G (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.1 | pc_UL_inter_band
_EN_DC_FR2_2B
_Class_A_G | | +| 4 | UL Inter-band EN-DC including FR2 BW Class Combination A_H (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.1 | pc_UL_inter_band
_EN_DC_FR2_2B
_Class_A_H | | +| 5 | UL Inter-band EN-DC including FR2 BW Class Combination A_I (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.1 | pc_UL_inter_band
_EN_DC_FR2_2B
_Class_A_I | | +| 6 | UL Inter-band EN-DC including FR2 BW Class Combination A_J (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.1 | pc_UL_inter_band
_EN_DC_FR2_2B
_Class_A_J | | +| 7 | UL Inter-band EN-DC including FR2 BW Class Combination A_K (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.1 | pc_UL_inter_band
_EN_DC_FR2_2B
_Class_A_K | | +| 8 | UL Inter-band EN-DC including FR2 BW Class Combination A_L (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.1 | pc_UL_inter_band
_EN_DC_FR2_2B
_Class_A_L | | +| 9 | UL Inter-band EN-DC including FR2 BW Class Combination A_M (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.1 | pc_UL_inter_band
_EN_DC_FR2_2B
_Class_A_M | | + +**Table A.4.3.2B.2.3.6-2: Supported Inter-band EN-DC configurations including FR2 (two bands)** + +| EN-DC configuration / Item
(Note 1, 3, 5) | Release | Supported EN-DC | | +|----------------------------------------------|---------|-----------------|------------------------------------------| +| | | Supported | Bandwidth Class(es) in UL
(Note 2, 4) | +| DC_1A_n257A | Rel-15 | | | +| DC_1A_n257G | Rel-16 | | | +| DC_1A_n257H | Rel-16 | | | +| DC_1A_n257I | Rel-16 | | | +| DC_1A_n257J | Rel-16 | | | +| DC_2A_n257A | Rel-15 | | | +| DC_2A_n260A | Rel-15 | | | +| DC_2A-2A_n260A | Rel-15 | | | +| DC_3A_n257A | Rel-15 | | | +| DC_3A_n257G | Rel-16 | | | +| DC_3A_n257H | Rel-16 | | | +| DC_3A_n257I | Rel-16 | | | +| DC_5A_n257A | Rel-15 | | | +| DC_5A_n260A | Rel-15 | | | +| DC_5A_n261A | Rel-15 | | | +| DC_7A_n257A | Rel-15 | | | +| DC_7A-7A_n257A | Rel-15 | | | +| DC_8A_n257A | Rel-15 | | | +| DC_12A_n260A | Rel-15 | | | +| DC_13A_n257A | Rel-15 | | | +| DC_14A_n260A | Rel-16 | | | +| DC_14A_n260G | Rel-16 | | | +| DC_14A_n260H | Rel-16 | | | +| DC_14A_n260I | Rel-16 | | | +| DC_18A_n257A | Rel-15 | | | +| DC_18A_n257I | Rel-16 | | | +| DC_19A_n257A | Rel-15 | | | +| DC_19A_n257G | Rel-16 | | | +| DC_19A_n257H | Rel-16 | | | +| DC_19A_n257I | Rel-16 | | | +| DC_20A_n257A | Rel-17 | | | +| DC_21A_n257A | Rel-15 | | | +| DC_21A_n257G | Rel-16 | | | +| DC_21A_n257H | Rel-16 | | | +| DC_21A_n257I | Rel-16 | | | +| DC_30A_n260A | Rel-15 | | | +| DC_66A-66A_n257A | Rel-15 | | | +| DC_66A_n260A | Rel-15 | | | +| DC_66A_n261A | Rel-15 | | | +| DC_66A_n261G | Rel-15 | | | +| DC_66A_n261H | Rel-15 | | | +| DC_66A_n261I | Rel-15 | | | +| DC_66A_n261J | Rel-15 | | | +| DC_66A_n261K | Rel-15 | | | +| DC_66A_n261L | Rel-15 | | | +| DC_66A_n261M | Rel-15 | | | + +| | | +|---------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Note 1: | Notation used for inter-band EN-DC Bands is according to TS 38.101-3 [25] Table 5.5B.5.1-1, e.g. 'DC_1A_n257A' indicates EN-DC operation on E-UTRA band 1 with E-UTRA DL Bandwidth Class A and NR band n257 with NR DL CA Bandwidth Class A. | +| Note 2: | See UL_nCC( table_index ) in Note 2 of Table 4.0-3 in TS 38.522 [9]. | +| Note 3: | See DL_nCC( table_index ) in Note 4 of Table 4.0-3 in TS 38.522 [9]. | +| Note 4: | See UL_NR_nCC( table_index ) in Note 3 of Table 4.0-3 in TS 38.522 [9]. | +| Note 5: | See DL_NR_nCC( table_index ) in Note 5 of Table 4.0-3 in TS 38.522 [9]. | + +###### A.4.3.2B.2.3.7 Inter-band EN-DC including FR2 (three bands) + +**Table A.4.3.2B.2.3.7-1: Downlink Bandwidth Class Combination capabilities for Inter-band EN-DC including FR2 and three bands (for one or more of the supported DC configurations in Table A.4.3.2B.2.3.7-2)** + +| Item | DL inter-band EN-DC including FR2 Bandwidth Class | Ref. | Mnemonic | Comments | +|------|-------------------------------------------------------------------------|-----------------------------------------|---------------------------------------------------|----------| +| 1 | Inter-band EN-DC including FR2 BW Class Combination A-A_A (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.2 | pc_DL_inter_band
_EN_DC_FR2_3B
_Class_A-A_A | | +| 2 | Inter-band EN-DC including FR2 BW Class Combination A-A_G (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.2 | pc_DL_inter_band
_EN_DC_FR2_3B
_Class_A-A_G | | +| 3 | Inter-band EN-DC including FR2 BW Class Combination A-A_H (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.2 | pc_DL_inter_band
_EN_DC_FR2_3B
_Class_A-A_H | | +| 4 | Inter-band EN-DC including FR2 BW Class Combination A-A_I (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.2 | pc_DL_inter_band
_EN_DC_FR2_3B
_Class_A-A_I | | +| 5 | Inter-band EN-DC including FR2 BW Class Combination A-C_A (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.2 | pc_DL_inter_band
_EN_DC_FR2_3B
_Class_A-C_A | | +| 6 | Inter-band EN-DC including FR2 BW Class Combination A-C_G (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.2 | pc_DL_inter_band
_EN_DC_FR2_3B
_Class_A-C_G | | +| 7 | Inter-band EN-DC including FR2 BW Class Combination A-C_H (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.2 | pc_DL_inter_band
_EN_DC_FR2_3B
_Class_A-C_H | | +| 8 | Inter-band EN-DC including FR2 BW Class Combination A-C_I (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.2 | pc_DL_inter_band
_EN_DC_FR2_3B
_Class_A-C_I | | +| 9 | Inter-band EN-DC including FR2 BW Class Combination A-D_A (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.2 | pc_DL_inter_band
_EN_DC_FR2_3B
_Class_A-D_A | | +| 10 | Inter-band EN-DC including FR2 BW Class Combination A-D_G (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.2 | pc_DL_inter_band
_EN_DC_FR2_3B
_Class_A-D_G | | +| 11 | Inter-band EN-DC including FR2 BW Class Combination A-D_H (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.2 | pc_DL_inter_band
_EN_DC_FR2_3B
_Class_A-D_H | | +| 12 | Inter-band EN-DC including FR2 BW Class Combination A-D_I (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.2 | pc_DL_inter_band
_EN_DC_FR2_3B
_Class_A-D_I | | +| 13 | Inter-band EN-DC including FR2 BW Class Combination A-E_A (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.2 | pc_DL_inter_band
_EN_DC_FR2_3B
_Class_A-E_A | | +| 14 | Inter-band EN-DC including FR2 BW Class Combination A-E_G (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.2 | pc_DL_inter_band
_EN_DC_FR2_3B
_Class_A-E_G | | +| 15 | Inter-band EN-DC including FR2 BW Class Combination A-E_H (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.2 | pc_DL_inter_band
_EN_DC_FR2_3B
_Class_A-E_H | | +| 16 | Inter-band EN-DC including FR2 BW Class Combination A-E_I (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.2 | pc_DL_inter_band
_EN_DC_FR2_3B
_Class_A-E_I | | + +**Table A.4.3.2B.2.3.7-1a: Uplink Bandwidth Class Combination capabilities for Inter-band EN-DC including FR2 and three bands (for one or more of the supported DC configurations in Table A.4.3.2B.2.3.7-2)** + +| Item | UL inter-band EN-DC including FR2 Bandwidth Class | Ref. | Mnemonic | Comments | +|------|--------------------------------------------------------------------------|-----------------------------------------|-------------------------------------------------|----------| +| 1 | UL Inter-band EN-DC including FR2 BW Class Combination A_A (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.2 | pc_UL_inter_band
_EN_DC_FR2_3B
_Class_A_A | | +| 2 | UL Inter-band EN-DC including FR2 BW Class Combination A_D (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.2 | pc_UL_inter_band
_EN_DC_FR2_3B
_Class_A_D | | +| 3 | UL Inter-band EN-DC including FR2 BW Class Combination A_G (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.2 | pc_UL_inter_band
_EN_DC_FR2_3B
_Class_A_G | | +| 4 | UL Inter-band EN-DC including FR2 BW Class Combination A_H (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.2 | pc_UL_inter_band
_EN_DC_FR2_3B
_Class_A_H | | +| 5 | UL Inter-band EN-DC including FR2 BW Class Combination A_I (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.2 | pc_UL_inter_band
_EN_DC_FR2_3B
_Class_A_I | | +| 6 | UL Inter-band EN-DC including FR2 BW Class Combination A_J (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.2 | pc_UL_inter_band
_EN_DC_FR2_3B
_Class_A_J | | +| 7 | UL Inter-band EN-DC including FR2 BW Class Combination A_K (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.2 | pc_UL_inter_band
_EN_DC_FR2_3B
_Class_A_K | | +| 8 | UL Inter-band EN-DC including FR2 BW Class Combination A_L (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.2 | pc_UL_inter_band
_EN_DC_FR2_3B
_Class_A_L | | +| 9 | UL Inter-band EN-DC including FR2 BW Class Combination A_M (three bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.2 | pc_UL_inter_band
_EN_DC_FR2_3B
_Class_A_M | | + +**Table A.4.3.2B.2.3.7-2: Supported Inter-band EN-DC configurations including FR2 (three bands)** + +| EN-DC configuration / Item
(Note 1, 3, 5) | Release | Supported EN-DC | | +|----------------------------------------------|---------|-----------------|------------------------------------------| +| | | Supported | Bandwidth Class(es) in UL
(Note 2, 4) | +| DC_1A-3A_n257A | Rel-15 | | | +| DC_1A-3A_n257G | Rel-16 | | | +| DC_1A-3A_n257H | Rel-16 | | | +| DC_1A-3A_n257I | Rel-16 | | | +| DC_1A-18A_n257A | Rel-15 | | | +| DC_1A-18A_n257I | Rel-16 | | | +| DC_1A-19A_n257A | Rel-15 | | | +| DC_1A-19A_n257G | Rel-16 | | | +| DC_1A-19A_n257H | Rel-16 | | | +| DC_1A-19A_n257I | Rel-16 | | | +| DC_1A-21A_n257A | Rel-15 | | | +| DC_1A-21A_n257G | Rel-16 | | | +| DC_1A-21A_n257H | Rel-16 | | | +| DC_1A-21A_n257I | Rel-16 | | | +| DC_1A-41A_n257A | Rel-15 | | | +| DC_1A-41A_n257I | Rel-16 | | | +| DC_1A-42A_n257A | Rel-15 | | | +| DC_1A-42A_n257G | Rel-16 | | | +| DC_1A-42A_n257H | Rel-16 | | | +| DC_1A-42A_n257I | Rel-16 | | | +| DC_1A-42C_n257A | Rel-15 | | | +| DC_1A-42D_n257A | Rel-15 | | | +| DC_1A-42D_n257G | Rel-16 | | | +| DC_1A-42D_n257H | Rel-16 | | | +| DC_1A-42D_n257I | Rel-16 | | | +| DC_1A-42E_n257A | Rel-15 | | | +| DC_1A-42E_n257G | Rel-16 | | | +| DC_1A-42E_n257H | Rel-16 | | | +| DC_1A-42E_n257I | Rel-16 | | | +| DC_2A-2A-14A_n260A | Rel-16 | | | +| DC_2A-2A-14A_n260G | Rel-16 | | | +| DC_2A-2A-14A_n260H | Rel-16 | | | +| DC_2A-2A-14A_n260I | Rel-16 | | | +| DC_2A-2A-14A_n260J | Rel-16 | | | +| DC_2A-2A-14A_n260K | Rel-16 | | | +| DC_2A-2A-14A_n260L | Rel-16 | | | +| DC_2A-2A-14A_n260M | Rel-16 | | | +| DC_2A-5A_n257A | Rel-15 | | | +| DC_2A-5A_n260A | Rel-15 | | | +| DC_2A-12A_n260A | Rel-15 | | | +| DC_2A-14A_n260A | Rel-16 | | | +| DC_2A-14A_n260G | Rel-16 | | | +| DC_2A-14A_n260H | Rel-16 | | | +| DC_2A-14A_n260I | Rel-16 | | | +| DC_2A-14A_n260A | Rel-16 | | | +| DC_2A-30A_n260A | Rel-15 | | | +| DC_2A-66A_n257A | Rel-15 | | | +| DC_2A-66A_n260A | Rel-15 | | | +| DC_3A-18A_n257A | Rel-16 | | | +| DC_3A-18A_n257I | Rel-16 | | | +| DC_3A-19A_n257A | Rel-15 | | | +| DC_3A-19A_n257G | Rel-16 | | | + +| | | | | +|----------------------|--------|--|--| +| DC_3A-19A_n257H | Rel-16 | | | +| DC_3A-19A_n257I | Rel-16 | | | +| DC_3A-21A_n257A | Rel-15 | | | +| DC_3A-21A_n257G | Rel-16 | | | +| DC_3A-21A_n257H | Rel-16 | | | +| DC_3A-21A_n257I | Rel-16 | | | +| DC_3A-41A_n257A | Rel-15 | | | +| DC_3A-41A_n257I | Rel-16 | | | +| DC_3A-42A_n257A | Rel-15 | | | +| DC_3A-42A_n257G | Rel-16 | | | +| DC_3A-42A_n257H | Rel-16 | | | +| DC_3A-42A_n257I | Rel-16 | | | +| DC_3A-42C_n257A | Rel-15 | | | +| DC_3A-42C_n257G | Rel-16 | | | +| DC_3A-42C_n257H | Rel-16 | | | +| DC_3A-42C_n257I | Rel-16 | | | +| DC_3A-42D_n257A | Rel-15 | | | +| DC_3A-42D_n257G | Rel-16 | | | +| DC_3A-42D_n257H | Rel-16 | | | +| DC_3A-42D_n257I | Rel-16 | | | +| DC_3A-42E_n257A | Rel-15 | | | +| DC_3A-42E_n257G | Rel-16 | | | +| DC_3A-42E_n257H | Rel-16 | | | +| DC_3A-42E_n257I | Rel-16 | | | +| DC_5A-7A_n257A | Rel-15 | | | +| DC_5A-30A_n260A | Rel-15 | | | +| DC_5A-66A_n257A | Rel-15 | | | +| DC_5A-66A_n260A | Rel-15 | | | +| DC_12A-30A_n260A | Rel-15 | | | +| DC_12A-66A_n260A | Rel-15 | | | +| DC_14A-30A_n260A | Rel-16 | | | +| DC_14A-30A_n260G | Rel-16 | | | +| DC_14A-30A_n260H | Rel-16 | | | +| DC_14A-30A_n260I | Rel-16 | | | +| DC_14A-30A_n260J | Rel-16 | | | +| DC_14A-30A_n260K | Rel-16 | | | +| DC_14A-30A_n260L | Rel-16 | | | +| DC_14A-30A_n260M | Rel-16 | | | +| DC_14A-66A_n260A | Rel-16 | | | +| DC_14A-66A_n260G | Rel-16 | | | +| DC_14A-66A_n260H | Rel-16 | | | +| DC_14A-66A_n260I | Rel-16 | | | +| DC_14A-66A_n260J | Rel-16 | | | +| DC_14A-66A_n260K | Rel-16 | | | +| DC_14A-66A_n260L | Rel-16 | | | +| DC_14A-66A_n260M | Rel-16 | | | +| DC_14A-66A-66A_n260A | Rel-16 | | | +| DC_14A-66A-66A_n260G | Rel-16 | | | +| DC_14A-66A-66A_n260H | Rel-16 | | | +| DC_14A-66A-66A_n260I | Rel-16 | | | +| DC_14A-66A-66A_n260J | Rel-16 | | | +| DC_14A-66A-66A_n260K | Rel-16 | | | +| DC_14A-66A-66A_n260L | Rel-16 | | | +| DC_14A-66A-66A_n260M | Rel-16 | | | +| DC_19A-21A_n257A | Rel-15 | | | +| DC_19A-21A_n257G | Rel-16 | | | + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--|--| +| DC_19A-21A_n257H | Rel-16 | | | +| DC_19A-21A_n257I | Rel-16 | | | +| DC_19A-42A_n257A | Rel-15 | | | +| DC_19A-42A_n257G | Rel-16 | | | +| DC_19A-42A_n257H | Rel-16 | | | +| DC_19A-42A_n257I | Rel-16 | | | +| DC_19A-42C_n257A | Rel-15 | | | +| DC_19A-42C_n257G | Rel-16 | | | +| DC_19A-42C_n257H | Rel-16 | | | +| DC_19A-42C_n257I | Rel-16 | | | +| DC_21A-42A_n257A | Rel-15 | | | +| DC_21A-42A_n257G | Rel-16 | | | +| DC_21A-42A_n257H | Rel-16 | | | +| DC_21A-42A_n257I | Rel-16 | | | +| DC_21A-42C_n257A | Rel-15 | | | +| DC_21A-42C_n257G | Rel-16 | | | +| DC_21A-42C_n257H | Rel-16 | | | +| DC_21A-42C_n257I | Rel-16 | | | +|

Note 1: Notation used for inter-band EN-DC Bands is according to TS 38.101-3 [25] Table 5.5B.5.2-1, e.g. 'DC_1A-3A_n257A' indicates EN-DC operation on E-UTRA CA configuration CA_1A-3A with E-UTRA DL Bandwidth Class A for both the E-UTRA bands 1 and 3 and NR band n257 with NR DL CA Bandwidth Class A.

Note 2: See UL_nCC(table_index) in Note 2 of Table 4.0-3 in TS 38.522 [9].

Note 3: See DL_nCC(table_index) in Note 4 of Table 4.0-3 in TS 38.522 [9].

Note 4: See UL_NR_nCC(table_index) in Note 3 of Table 4.0-3 in TS 38.522 [9].

Note 5: See DL_NR_nCC(table_index) in Note 5 of Table 4.0-3 in TS 38.522 [9].

| | | | + +###### A.4.3.2B.2.3.8 Inter-band EN-DC including FR2 (four bands) + +**Table A.4.3.2B.2.3.8-1: Downlink Bandwidth Class Combination capabilities for Inter-band EN-DC including FR2 and four bands (for one or more of the supported DC configurations in Table A.4.3.2B.2.3.8-2)** + +| Item | DL inter-band EN-DC including FR2 Bandwidth Class | Ref. | Mnemonic | Comments | +|------|--------------------------------------------------------------------------|-----------------------------------------|-----------------------------------------------------|----------| +| 1 | Inter-band EN-DC including FR2 BW Class Combination A-A-A_A (four bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.3 | pc_DL_inter_band
_EN_DC_FR2_4B
_Class_A-A-A_A | | +| 2 | Inter-band EN-DC including FR2 BW Class Combination A-A-A_G (four bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.3 | pc_DL_inter_band
_EN_DC_FR2_4B
_Class_A-A-A_G | | +| 3 | Inter-band EN-DC including FR2 BW Class Combination A-A-A_H (four bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.3 | pc_DL_inter_band
_EN_DC_FR2_4B
_Class_A-A-A_H | | +| 4 | Inter-band EN-DC including FR2 BW Class Combination A-A-A_I (four bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.3 | pc_DL_inter_band
_EN_DC_FR2_4B
_Class_A-A-A_I | | +| 5 | Inter-band EN-DC including FR2 BW Class Combination A-A-C_A (four bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.3 | pc_DL_inter_band
_EN_DC_FR2_4B
_Class_A-A-C_A | | +| 6 | Inter-band EN-DC including FR2 BW Class Combination A-A-C_G (four bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.3 | pc_DL_inter_band
_EN_DC_FR2_4B
_Class_A-A-C_G | | +| 7 | Inter-band EN-DC including FR2 BW Class Combination A-A-C_H (four bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.3 | pc_DL_inter_band
_EN_DC_FR2_4B
_Class_A-A-C_H | | +| 8 | Inter-band EN-DC including FR2 BW Class Combination A-A-C_I (four bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.3 | pc_DL_inter_band
_EN_DC_FR2_4B
_Class_A-A-C_I | | +| 9 | Inter-band EN-DC including FR2 BW Class Combination A-A-D_G (four bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.3 | pc_DL_inter_band
_EN_DC_FR2_4B
_Class_A-A-D_G | | +| 10 | Inter-band EN-DC including FR2 BW Class Combination A-A-D_H (four bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.3 | pc_DL_inter_band
_EN_DC_FR2_4B
_Class_A-A-D_H | | +| 11 | Inter-band EN-DC including FR2 BW Class Combination A-A-D_I (four bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.3 | pc_DL_inter_band
_EN_DC_FR2_4B
_Class_A-A-D_I | | +| 12 | Inter-band EN-DC including FR2 BW Class Combination A-A-A_J (four bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.3 | pc_DL_inter_band
_EN_DC_FR2_4B
_Class_A-A-A_J | | +| 13 | Inter-band EN-DC including FR2 BW Class Combination A-A-A_K (four bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.3 | pc_DL_inter_band
_EN_DC_FR2_4B
_Class_A-A-A_K | | +| 14 | Inter-band EN-DC including FR2 BW Class Combination A-A-A_L (four bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.3 | pc_DL_inter_band
_EN_DC_FR2_4B
_Class_A-A-A_L | | +| 15 | Inter-band EN-DC including FR2 BW Class Combination A-A-A_M (four bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.3 | pc_DL_inter_band
_EN_DC_FR2_4B
_Class_A-A-A_M | | + +**Table A.4.3.2B.2.3.8-1a: Uplink Bandwidth Class Combination capabilities for Inter-band EN-DC including FR2 and four bands (for one or more of the supported DC configurations in Table A.4.3.2B.2.3.8-2)** + +| Item | UL inter-band EN-DC including FR2 Bandwidth Class | Ref. | Mnemonic | Comments | +|------|-------------------------------------------------------------------------|-----------------------------------------|-------------------------------------------------|----------| +| 1 | UL Inter-band EN-DC including FR2 BW Class Combination A_A (four bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.3 | pc_UL_inter_band
_EN_DC_FR2_4B
_Class_A_A | | +| 2 | UL Inter-band EN-DC including FR2 BW Class Combination A_D (four bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.3 | pc_UL_inter_band
_EN_DC_FR2_4B
_Class_A_D | | +| 3 | UL Inter-band EN-DC including FR2 BW Class Combination A_G (four bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.3 | pc_UL_inter_band
_EN_DC_FR2_4B
_Class_A_G | | +| 4 | UL Inter-band EN-DC including FR2 BW Class Combination A_H (four bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.3 | pc_UL_inter_band
_EN_DC_FR2_4B
_Class_A_H | | +| 5 | UL Inter-band EN-DC including FR2 BW Class Combination A_I (four bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.3 | pc_UL_inter_band
_EN_DC_FR2_4B
_Class_A_I | | +| 6 | UL Inter-band EN-DC including FR2 BW Class Combination A_J (four bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.3 | pc_UL_inter_band
_EN_DC_FR2_4B
_Class_A_J | | +| 7 | UL Inter-band EN-DC including FR2 BW Class Combination A_K (four bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.3 | pc_UL_inter_band
_EN_DC_FR2_4B
_Class_A_K | | +| 8 | UL Inter-band EN-DC including FR2 BW Class Combination A_L (four bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.3 | pc_UL_inter_band
_EN_DC_FR2_4B
_Class_A_L | | +| 9 | UL Inter-band EN-DC including FR2 BW Class Combination A_M (four bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.3 | pc_UL_inter_band
_EN_DC_FR2_4B
_Class_A_M | | + +**Table A.4.3.2B.2.3.8-2: Supported Inter-band EN-DC configurations including FR2 (four bands)** + +| EN-DC configuration / Item
(Note 1, 3, 5) | Release | Supported EN-DC | | +|----------------------------------------------|---------|-----------------|------------------------------------------| +| | | Supported | Bandwidth Class(es) in UL
(Note 2, 4) | +| DC_1A-3A-18A_n257A | Rel-16 | | | +| DC_1A-3A-18A_n257I | Rel-16 | | | +| DC_1A-3A-19A_n257A | Rel-15 | | | +| DC_1A-3A-19A_n257G | Rel-16 | | | +| DC_1A-3A-19A_n257H | Rel-16 | | | +| DC_1A-3A-19A_n257I | Rel-16 | | | +| DC_1A-3A-21A_n257A | Rel-15 | | | +| DC_1A-3A-21A_n257G | Rel-16 | | | +| DC_1A-3A-21A_n257H | Rel-16 | | | +| DC_1A-3A-21A_n257I | Rel-16 | | | +| DC_1A-3A-41A_n257A | Rel-16 | | | +| DC_1A-3A-41A_n257I | Rel-16 | | | +| DC_1A-3A-42A_n257A | Rel-15 | | | +| DC_1A-3A-42A_n257G | Rel-16 | | | +| DC_1A-3A-42A_n257H | Rel-16 | | | +| DC_1A-3A-42A_n257I | Rel-16 | | | +| DC_1A-3A-42C_n257A | Rel-15 | | | +| DC_1A-3A-42C_n257G | Rel-16 | | | +| DC_1A-3A-42C_n257H | Rel-16 | | | +| DC_1A-3A-42C_n257I | Rel-16 | | | +| DC_1A-3A-42D_n257A | Rel-16 | | | +| DC_1A-3A-42D_n257G | Rel-16 | | | +| DC_1A-3A-42D_n257H | Rel-16 | | | +| DC_1A-3A-42D_n257I | Rel-16 | | | +| DC_1A-19A-21A_n257A | Rel-15 | | | +| DC_1A-19A-21A_n257G | Rel-16 | | | +| DC_1A-19A-21A_n257H | Rel-16 | | | +| DC_1A-19A-21A_n257I | Rel-16 | | | +| DC_1A-19A-42A_n257A | Rel-15 | | | +| DC_1A-19A-42A_n257G | Rel-16 | | | +| DC_1A-19A-42A_n257H | Rel-16 | | | +| DC_1A-19A-42A_n257I | Rel-16 | | | +| DC_1A-19A-42C_n257A | Rel-15 | | | +| DC_1A-19A-42C_n257G | Rel-16 | | | +| DC_1A-19A-42C_n257H | Rel-16 | | | +| DC_1A-19A-42C_n257I | Rel-16 | | | +| DC_1A-21A-42A_n257A | Rel-15 | | | +| DC_1A-21A-42A_n257G | Rel-16 | | | +| DC_1A-21A-42A_n257H | Rel-16 | | | +| DC_1A-21A-42A_n257I | Rel-16 | | | +| DC_1A-21A-42C_n257A | Rel-15 | | | +| DC_1A-21A-42C_n257G | Rel-16 | | | +| DC_1A-21A-42C_n257H | Rel-16 | | | +| DC_1A-21A-42C_n257I | Rel-16 | | | +| DC_2A-2A-14A-66A_n260A | Rel-16 | | | +| DC_2A-2A-14A-66A_n260G | Rel-16 | | | +| DC_2A-2A-14A-66A_n260H | Rel-16 | | | +| DC_2A-2A-14A-66A_n260I | Rel-16 | | | +| DC_2A-2A-14A-66A_n260J | Rel-16 | | | +| DC_2A-2A-14A-66A_n260K | Rel-16 | | | +| DC_2A-2A-14A-66A_n260L | Rel-16 | | | +| DC_2A-2A-14A-66A_n260M | Rel-16 | | | + +| | | | | +|--------------------------|--------|--|--| +| DC_2A-14A-30A_n260A | Rel-16 | | | +| DC_2A-14A-30A_n260G | Rel-16 | | | +| DC_2A-14A-30A_n260H | Rel-16 | | | +| DC_2A-14A-30A_n260I | Rel-16 | | | +| DC_2A-14A-30A_n260J | Rel-16 | | | +| DC_2A-14A-30A_n260K | Rel-16 | | | +| DC_2A-14A-30A_n260L | Rel-16 | | | +| DC_2A-14A-30A_n260M | Rel-16 | | | +| DC_2A-14A-66A_n260A | Rel-16 | | | +| DC_2A-14A-66A_n260G | Rel-16 | | | +| DC_2A-14A-66A_n260H | Rel-16 | | | +| DC_2A-14A-66A_n260I | Rel-16 | | | +| DC_2A-14A-66A_n260J | Rel-16 | | | +| DC_2A-14A-66A_n260K | Rel-16 | | | +| DC_2A-14A-66A_n260L | Rel-16 | | | +| DC_2A-14A-66A_n260M | Rel-16 | | | +| DC_2A-14A-66A-66A_n260A | Rel-16 | | | +| DC_2A-14A-66A-66A_n260G | Rel-16 | | | +| DC_2A-14A-66A-66A_n260H | Rel-16 | | | +| DC_2A-14A-66A-66A_n260I | Rel-16 | | | +| DC_2A-14A-66A-66A_n260J | Rel-16 | | | +| DC_2A-14A-66A-66A_n260K | Rel-16 | | | +| DC_2A-14A-66A-66A_n260L | Rel-16 | | | +| DC_2A-14A-66A-66A_n260M | Rel-16 | | | +| DC_3A-19A-21A_n257A | Rel-15 | | | +| DC_3A-19A-42A_n257A | Rel-15 | | | +| DC_3A-19A-42A_n257G | Rel-16 | | | +| DC_3A-19A-42A_n257H | Rel-16 | | | +| DC_3A-19A-42A_n257I | Rel-16 | | | +| DC_3A-19A-42C_n257A | Rel-15 | | | +| DC_3A-19A-42C_n257G | Rel-16 | | | +| DC_3A-19A-42C_n257H | Rel-16 | | | +| DC_3A-19A-42C_n257I | Rel-16 | | | +| DC_3A-21A-42A_n257A | Rel-15 | | | +| DC_3A-21A-42A_n257G | Rel-16 | | | +| DC_3A-21A-42A_n257H | Rel-16 | | | +| DC_3A-21A-42A_n257I | Rel-16 | | | +| DC_3A-21A-42C_n257A | Rel-15 | | | +| DC_3A-21A-42C_n257G | Rel-16 | | | +| DC_3A-21A-42C_n257H | Rel-16 | | | +| DC_3A-21A-42C_n257I | Rel-16 | | | +| DC_14A-30A-66A_n260A | Rel-16 | | | +| DC_14A-30A-66A_n260G | Rel-16 | | | +| DC_14A-30A-66A_n260H | Rel-16 | | | +| DC_14A-30A-66A_n260I | Rel-16 | | | +| DC_14A-30A-66A_n260J | Rel-16 | | | +| DC_14A-30A-66A_n260K | Rel-16 | | | +| DC_14A-30A-66A_n260L | Rel-16 | | | +| DC_14A-30A-66A_n260M | Rel-16 | | | +| DC_14A-30A-66A-66A_n260A | Rel-16 | | | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--|--| +| DC_14A-30A-66A-66A_n260
G | Rel-16 | | | +| DC_14A-30A-66A-66A_n260
H | Rel-16 | | | +| DC_14A-30A-66A-66A_n260
I | Rel-16 | | | +| DC_14A-30A-66A-66A_n260
J | Rel-16 | | | +| DC_14A-30A-66A-66A_n260
K | Rel-16 | | | +| DC_14A-30A-66A-66A_n260
L | Rel-16 | | | +| DC_14A-30A-66A-66A_n260
M | Rel-16 | | | +| DC_19A-21A-42A_n257A | Rel-15 | | | +| DC_19A-21A-42A_n257G | Rel-16 | | | +| DC_19A-21A-42A_n257H | Rel-16 | | | +| DC_19A-21A-42A_n257I | Rel-16 | | | +| DC_19A-21A-42C_n257A | Rel-15 | | | +| DC_19A-21A-42C_n257G | Rel-16 | | | +| DC_19A-21A-42C_n257H | Rel-16 | | | +| DC_19A-21A-42C_n257I | Rel-16 | | | +|

Note 1: Notation used for inter-band EN-DC Bands is according to TS 38.101-3 [25] Table 5.5B.5.3-1, e.g. 'DC_1A-3A-19A_n257A' indicates EN-DC operation on E-UTRA CA configuration CA_1A-3A-19A with E-UTRA DL Bandwidth Class A for all the E-UTRA bands 1, 3 and 19 and NR band n257 with NR DL CA Bandwidth Class A.

Note 2: See UL_nCC(table_index) in Note 2 of Table 4.0-3 in TS 38.522 [9].

Note 3: See DL_nCC(table_index) in Note 4 of Table 4.0-3 in TS 38.522 [9].

Note 4: See UL_NR_nCC(table_index) in Note 3 of Table 4.0-3 in TS 38.522 [9].

Note 5: See DL_NR_nCC(table_index) in Note 5 of Table 4.0-3 in TS 38.522 [9].

| | | | + +###### A.4.3.2B.2.3.9 Inter-band EN-DC including FR2 (five bands) + +**Table A.4.3.2B.2.3.9-1: Downlink Bandwidth Class Combination capabilities for Inter-band EN-DC including FR2 and five bands (for one or more of the supported DC configurations in Table A.4.3.2B.2.3.9-2)** + +| Item | DL inter-band EN-DC including FR2 Bandwidth Class | Ref. | Mnemonic | Comments | +|------|----------------------------------------------------------------------------|-----------------------------------------|-----------------------------------------------------------|----------| +| 1 | Inter-band EN-DC including FR2 BW Class Combination A-A-A-A_A (five bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.4 | pc_DL_inter_band
_EN_DC_FR2_5B
_Class_A-A-A-
A_A | | +| 2 | Inter-band EN-DC including FR2 BW Class Combination A-A-A-A_G (five bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.4 | pc_DL_inter_band
_EN_DC_FR2_5B
_Class_A-A-A-
A_G | | +| 3 | Inter-band EN-DC including FR2 BW Class Combination A-A-A-A_H (five bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.4 | pc_DL_inter_band
_EN_DC_FR2_5B
_Class_A-A-A-
A_H | | +| 4 | Inter-band EN-DC including FR2 BW Class Combination A-A-A-A_I (five bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.4 | pc_DL_inter_band
_EN_DC_FR2_5B
_Class_A-A-A-
A_I | | +| 5 | Inter-band EN-DC including FR2 BW Class Combination A-A-A-C_A (five bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.4 | pc_DL_inter_band
_EN_DC_FR2_5B
_Class_A-A-A-
C_A | | +| 6 | Inter-band EN-DC including FR2 BW Class Combination A-A-A-C_G (five bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.4 | pc_DL_inter_band
_EN_DC_FR2_5B
_Class_A-A-A-
C_G | | +| 7 | Inter-band EN-DC including FR2 BW Class Combination A-A-A-C_H (five bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.4 | pc_DL_inter_band
_EN_DC_FR2_5B
_Class_A-A-A-
C_H | | +| 8 | Inter-band EN-DC including FR2 BW Class Combination A-A-A-C_I (five bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.4 | pc_DL_inter_band
_EN_DC_FR2_5B
_Class_A-A-A-
C_I | | +| 9 | Inter-band EN-DC including FR2 BW Class Combination A-A-A-A_J (five bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.4 | pc_DL_inter_band
_EN_DC_FR2_5B
_Class_A-A-A-
A_J | | +| 10 | Inter-band EN-DC including FR2 BW Class Combination A-A-A-A_K (five bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.4 | pc_DL_inter_band
_EN_DC_FR2_5B
_Class_A-A-A-
A_K | | +| 11 | Inter-band EN-DC including FR2 BW Class Combination A-A-A-A_L (five bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.4 | pc_DL_inter_band
_EN_DC_FR2_5B
_Class_A-A-A-
A_L | | +| 12 | Inter-band EN-DC including FR2 BW Class Combination A-A-A-A_M (five bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.4 | pc_DL_inter_band
_EN_DC_FR2_5B
_Class_A-A-A-
A_M | | + +**Table A.4.3.2B.2.3.9-1a: Uplink Bandwidth Class Combination capabilities for Inter-band EN-DC including FR2 and five bands (for one or more of the supported DC configurations in Table A.4.3.2B.2.3.9-2)** + +| Item | UL inter-band EN-DC including FR2 Bandwidth Class | Ref. | Mnemonic | Comments | +|------|----------------------------------------------------------------------|-----------------------------------------|-------------------------------------------------|----------| +| 1 | Inter-band EN-DC including FR2 BW Class Combination A_A (five bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.4 | pc_UL_inter_band
_EN_DC_FR2_5B
_Class_A_A | | +| 2 | Inter-band EN-DC including FR2 BW Class Combination A_D (five bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.4 | pc_UL_inter_band
_EN_DC_FR2_5B
_Class_A_D | | +| 3 | Inter-band EN-DC including FR2 BW Class Combination A_G (five bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.4 | pc_UL_inter_band
_EN_DC_FR2_5B
_Class_A_G | | +| 4 | Inter-band EN-DC including FR2 BW Class Combination A_H (five bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.4 | pc_UL_inter_band
_EN_DC_FR2_5B
_Class_A_H | | +| 5 | Inter-band EN-DC including FR2 BW Class Combination A_I (five bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.4 | pc_UL_inter_band
_EN_DC_FR2_5B
_Class_A_I | | +| 6 | Inter-band EN-DC including FR2 BW Class Combination A_J (five bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.4 | pc_UL_inter_band
_EN_DC_FR2_5B
_Class_A_J | | +| 7 | Inter-band EN-DC including FR2 BW Class Combination A_K (five bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.4 | pc_UL_inter_band
_EN_DC_FR2_5B
_Class_A_K | | +| 8 | Inter-band EN-DC including FR2 BW Class Combination A_L (five bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.4 | pc_UL_inter_band
_EN_DC_FR2_5B
_Class_A_L | | +| 9 | Inter-band EN-DC including FR2 BW Class Combination A_M (five bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.4 | pc_UL_inter_band
_EN_DC_FR2_5B
_Class_A_M | | +| 10 | Inter-band EN-DC including FR2 BW Class Combination C_A (five bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.4 | pc_UL_inter_band
_EN_DC_FR2_5B
_Class_C_A | | +| 11 | Inter-band EN-DC including FR2 BW Class Combination C_G (five bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.4 | pc_UL_inter_band
_EN_DC_FR2_5B
_Class_C_G | | +| 12 | Inter-band EN-DC including FR2 BW Class Combination C_H (five bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.4 | pc_UL_inter_band
_EN_DC_FR2_5B
_Class_C_H | | +| 13 | Inter-band EN-DC including FR2 BW Class Combination C_I (five bands) | 36.101, 5.6A.1
38.101-3,
5.5B.5.4 | pc_UL_inter_band
_EN_DC_FR2_5B
_Class_C_I | | + +**Table A.4.3.2B.2.3.9-2: Supported Inter-band EN-DC configurations including FR2 (five bands)** + +| EN-DC configuration / Item
(Note 1, 3, 5) | Release | Supported EN-DC | | +|----------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|------------------------------------------| +| | | Supported | Bandwidth Class(es) in UL
(Note 2, 4) | +| DC_1A-3A-19A-42A_n257A | Rel-15 | | | +| DC_1A-3A-19A-42A_n257G | Rel-16 | | | +| DC_1A-3A-19A-42C_n257A | Rel-15 | | | +| DC_1A-3A-19A-42C_n257G | Rel-16 | | | +| DC_1A-3A-19A-42C_n257H | Rel-16 | | | +| DC_1A-3A-19A-42C_n257I | Rel-16 | | | +| DC_1A-3A-21A-42A_n257A | Rel-15 | | | +| DC_1A-3A-21A-42C_n257A | Rel-15 | | | +| DC_1A-3A-21A-42C_n257G | Rel-16 | | | +| DC_1A-3A-21A-42C_n257H | Rel-16 | | | +| DC_1A-3A-21A-42C_n257I | Rel-16 | | | +| DC_1A-19A-21A-42A_n257A | Rel-15 | | | +| DC_1A-19A-21A-42A_n257G | Rel-16 | | | +| DC_1A-19A-21A-42A_n257H | Rel-16 | | | +| DC_1A-19A-21A-42A_n257I | Rel-16 | | | +| DC_1A-19A-21A-42C_n257A | Rel-15 | | | +| DC_1A-19A-21A-42C_n257G | Rel-16 | | | +| DC_1A-19A-21A-42C_n257H | Rel-16 | | | +| DC_1A-19A-21A-42C_n257I | Rel-16 | | | +| DC_2A-14A-30A-66A_n260A | Rel-16 | | | +| DC_2A-14A-30A-66A_n260G | Rel-16 | | | +| DC_2A-14A-30A-66A_n260H | Rel-16 | | | +| DC_2A-14A-30A-66A_n260I | Rel-16 | | | +| DC_2A-14A-30A-66A_n260J | Rel-16 | | | +| DC_2A-14A-30A-66A_n260K | Rel-16 | | | +| DC_2A-14A-30A-66A_n260L | Rel-16 | | | +| DC_2A-14A-30A-66A_n260M | Rel-16 | | | +| Note 1: | Notation used for inter-band EN-DC Bands is according to TS 38.101-3 [25] Table 5.5B.5.4-1, e.g. 'DC_1A-3A-19A-42A_n257A' indicates EN-DC operation on E-UTRA CA configuration CA_1A-3A-19A-42A with E-UTRA DL Bandwidth Class A for all the E-UTRA bands 1, 3, 19 and 42 and NR band n257 with NR DL CA Bandwidth Class A. | | | +| Note 2: | See UL_nCC( table_index ) in Note 2 of Table 4.0-3 in TS 38.522 [9]. | | | +| Note 3: | See DL_nCC( table_index ) in Note 4 of Table 4.0-3 in TS 38.522 [9]. | | | +| Note 4: | See UL_NR_nCC( table_index ) in Note 3 of Table 4.0-3 in TS 38.522 [9]. | | | +| Note 5: | See DL_NR_nCC( table_index ) in Note 5 of Table 4.0-3 in TS 38.522 [9]. | | | + +A.4.3.2B.2.3.10 Void + +A.4.3.2B.2.3.11 Inter-band EN-DC including FR1 and FR2 (three bands) + +**Table A.4.3.2B.2.3.11-1: Downlink Bandwidth Class Combination capabilities for Inter-band EN-DC including FR1 and FR2, and three bands (for one or more of the supported DC configurations in Table A.4.3.2B.2.3.11-2)** + +| Item | DL inter-band EN-DC including FR1 and FR2 Bandwidth Class | Ref. | Mnemonic | Comments | +|------|---------------------------------------------------------------------------------|---------------------------------------------------------------------------------|-----------------------------------------------------------|----------| +| 1 | Inter-band EN-DC including FR1 and FR2 BW Class Combination A_A-A (three bands) | 36.101, 5.6A.1
38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3,
5.5B.6.2 | pc_DL_inter_band
_EN_DC_FR1_F
R2_3B_Class_A_
A-A | | + +**Table A.4.3.2B.2.3.11-1a: Uplink Bandwidth Class Combination capabilities for Inter-band EN-DC including FR1 and FR2, and three bands (for one or more of the supported DC configurations in Table A.4.3.2B.2.3.11-2)** + +| Item | UL inter-band EN-DC including FR1 and FR2 Bandwidth Class | Ref. | Mnemonic | Comments | +|------|----------------------------------------------------------------------------------|---------------------------------------------------------------------------------|---------------------------------------------------------|----------| +| 1 | UL Inter-band EN-DC including FR1 and FR2 BW Class Combination A_A (three bands) | 36.101, 5.6A.1
38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3,
5.5B.6.2 | pc_UL_inter_band
_EN_DC_FR1_F
R2_3B_Class_A_
A | | + +**Table A.4.3.2B.2.3.11-2: Supported Inter-band EN-DC configurations including FR1 and FR2 (three bands)** + +| EN-DC configuration / Item | Release | Supported | Supported EN-DC Bandwidth Class(es) in UL | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-----------|-------------------------------------------| +| DC_1A_n78A-n257A | Rel-15 | | | +| DC_1A_n79A-n257A | Rel-15 | | | +| DC_3A_n78A-n257A | Rel-15 | | | +| DC_3A_n79A-n257A | Rel-15 | | | +| DC_19A_n78A-n257A | Rel-15 | | | +| DC_19A_n79A-n257A | Rel-15 | | | +| Note 1: Notation used for inter-band EN-DC Bands is according to TS 38.101-3 [25] Table 5.5B.6.2-1, e.g. 'DC_1A_n78A-n257A' indicates EN-DC operation on E-UTRA band 1 with E-UTRA DL Bandwidth Class A and NR CA configuration CA_n78A-n257A on NR band n78 and n257 both with NR DL CA Bandwidth Class A. | | | | + +###### A.4.3.2B.2.3.12 Inter-band EN-DC including FR1 and FR2 (four bands) + +**Table A.4.3.2B.2.3.12-1: Downlink Bandwidth Class Combination capabilities for Inter-band EN-DC including FR1 and FR2, and four bands (for one or more of the supported DC configurations in Table A.4.3.2B.2.3.12-2)** + +| Item | DL inter-band EN-DC including FR1 and FR2 Bandwidth Class | Ref. | Mnemonic | Comments | +|------|----------------------------------------------------------------------------------|---------------------------------------------------------------------------------|-------------------------------------------------------------|----------| +| 1 | Inter-band EN-DC including FR1 and FR2 BW Class Combination A-A_A-A (four bands) | 36.101, 5.6A.1
38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3,
5.5B.6.3 | pc_DL_inter_band
_EN_DC_FR1_F
R2_4B_Class_A-
A_A-A | | +| 2 | Inter-band EN-DC including FR1 and FR2 BW Class Combination A-A_A-G (four bands) | 36.101, 5.6A.1
38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3,
5.5B.6.3 | pc_DL_inter_band
_EN_DC_FR1_F
R2_4B_Class_A-
A_A-G | | +| 3 | Inter-band EN-DC including FR1 and FR2 BW Class Combination A-A_A-H (four bands) | 36.101, 5.6A.1
38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3,
5.5B.6.3 | pc_DL_inter_band
_EN_DC_FR1_F
R2_4B_Class_A-
A_A-H | | +| 4 | Inter-band EN-DC including FR1 and FR2 BW Class Combination A-A_A-I (four bands) | 36.101, 5.6A.1
38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3,
5.5B.6.3 | pc_DL_inter_band
_EN_DC_FR1_F
R2_4B_Class_A-
A_A-I | | + +**Table A.4.3.2B.2.3.12-1a: Uplink Bandwidth Class Combination capabilities for Inter-band EN-DC including FR1 and FR2, and four bands (for one or more of the supported DC configurations in Table A.4.3.2B.2.3.12-2)** + +| Item | UL inter-band EN-DC including FR1 and FR2 Bandwidth Class | Ref. | Mnemonic | Comments | +|------|-----------------------------------------------------------------------------------|---------------------------------------------------------------------------------|-----------------------------------------------------------|----------| +| 1 | UL Inter-band EN-DC including FR1 and FR2 BW Class Combination A_A (four bands) | 36.101, 5.6A.1
38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3,
5.5B.6.3 | pc_UL_inter_band
_EN_DC_FR1_F
R2_4B_Class_A_
A | | +| 2 | UL Inter-band EN-DC including FR1 and FR2 BW Class Combination A_G (four bands) | 36.101, 5.6A.1
38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3,
5.5B.6.3 | pc_UL_inter_band
_EN_DC_FR1_F
R2_4B_Class_A_
G | | +| 3 | UL Inter-band EN-DC including FR1 and FR2 BW Class Combination A_H (four bands) | 36.101, 5.6A.1
38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3,
5.5B.6.3 | pc_UL_inter_band
_EN_DC_FR1_F
R2_4B_Class_A_
H | | +| 4 | UL Inter-band EN-DC including FR1 and FR2 BW Class Combination A_I (four bands) | 36.101, 5.6A.1
38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3,
5.5B.6.3 | pc_UL_inter_band
_EN_DC_FR1_F
R2_4B_Class_A_
I | | +| 5 | UL Inter-band EN-DC including FR1 and FR2 BW Class Combination A_A-A (four bands) | 36.101, 5.6A.1
38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3,
5.5B.6.3 | pc_UL_inter_band
_EN_DC_FR1_F
R2_4B_Class_A_
A-A | | +| 6 | UL Inter-band EN-DC including FR1 and FR2 BW Class Combination A_A-G (four bands) | 36.101, 5.6A.1
38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3,
5.5B.6.3 | pc_UL_inter_band
_EN_DC_FR1_F
R2_4B_Class_A_
A-G | | +| 7 | UL Inter-band EN-DC including FR1 and FR2 BW Class Combination A_A-H (four bands) | 36.101, 5.6A.1
38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3,
5.5B.6.3 | pc_UL_inter_band
_EN_DC_FR1_F
R2_4B_Class_A_
A-H | | +| 8 | UL Inter-band EN-DC including FR1 and FR2 BW Class Combination A_A-I (four bands) | 36.101, 5.6A.1
38.101-1, 5.3A.5
38.101-2, 5.3A.4
38.101-3,
5.5B.6.3 | pc_UL_inter_band
_EN_DC_FR1_F
R2_4B_Class_A_
A-I | | + +**Table A.4.3.2B.2.3.12-2: Supported Inter-band EN-DC configurations including FR1 and FR2 (four bands)** + +| EN-DC configuration / Item | Release | Supported | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-----------|-------------------------------------------| +| | | Supported | Supported EN-DC Bandwidth Class(es) in UL | +| DC_1A-3A_n78A-n257A | Rel-15 | | | +| DC_1A-3A_n78A-n257G | Rel-16 | | | +| DC_1A-3A_n78A-n257H | Rel-16 | | | +| DC_1A-3A_n78A-n257I | Rel-16 | | | +| Note 1: Notation used for inter-band EN-DC Bands is according to TS 38.101-3 [25] Table 5.5B.6.3-1, e.g. 'DC_1A-3A_n78A-n257G' indicates EN-DC operation on E-UTRA CA configuration CA_1A-3A with E-UTRA DL Bandwidth Class A for all the E-UTRA bands 1 and 3 and NR bands n78 and n257 with NR DL CA Bandwidth Class A and G respectively. | | | | + +###### A.4.3.2B.2.3.13 Inter-band EN-DC including FR1 and FR2 (five bands) + +**Table A.4.3.2B.2.3.13-1: Downlink Bandwidth Class Combination capabilities for Inter-band EN-DC including FR1 and FR2, and five bands (for one or more of the supported DC configurations in Table A.4.3.2B.2.3.13-2)** + +| Item | DL inter-band EN-DC including FR1 and FR2 Bandwidth Class | Ref. | Mnemonic | Comments | +|------|-----------------------------------------------------------|------|----------|----------| +| 1 | TBD | TBD | TBD | | + +**Table A.4.3.2B.2.3.13-1a: Uplink Bandwidth Class Combination capabilities for Inter-band EN-DC including FR1 and FR2, and five bands (for one or more of the supported DC configurations in Table A.4.3.2B.2.3.13-2)** + +| Item | UL inter-band EN-DC including FR1 and FR2 Bandwidth Class | Ref. | Mnemonic | Comments | +|------|-----------------------------------------------------------|------|----------|----------| +| 1 | TBD | TBD | TBD | | + +**Table A.4.3.2B.2.3.13-2: Supported Inter-band EN-DC configurations including FR1 and FR2 (five bands)** + +| EN-DC configuration / Item | Release | Supported | | +|----------------------------|---------|-----------|-------------------------------------------| +| | | Supported | Supported EN-DC Bandwidth Class(es) in UL | +| TBD | TBD | | | + +###### A.4.3.2B.2.3.14 Inter-band EN-DC including FR1 and FR2 (six bands) + +**Table A.4.3.2B.2.3.14-1: Downlink Bandwidth Class Combination capabilities for Inter-band EN-DC including FR1 and FR2, and six bands (for one or more of the supported DC configurations in Table A.4.3.2B.2.3.14-2)** + +| Item | DL inter-band EN-DC including FR1 and FR2 Bandwidth Class | Ref. | Mnemonic | Comments | +|------|-----------------------------------------------------------|------|----------|----------| +| 1 | TBD | TBD | TBD | | + +**Table A.4.3.2B.2.3.14-1a: Uplink Bandwidth Class Combination capabilities for Inter-band EN-DC including FR1 and FR2, and six bands (for one or more of the supported DC configurations in Table A.4.3.2B.2.3.14-2)** + +| Item | UL inter-band EN-DC including FR1 and FR2 Bandwidth Class | Ref. | Mnemonic | Comments | +|------|-----------------------------------------------------------|------|----------|----------| +| 1 | TBD | TBD | TBD | | + +**Table A.4.3.2B.2.3.14-2: Supported Inter-band EN-DC configurations including FR1 and FR2 (six bands)** + +| EN-DC configuration / Item | Release | Supported | Supported EN-DC Bandwidth Class(es) in UL | +|----------------------------|---------|-----------|-------------------------------------------| +| TBD | TBD | | | + +##### A.4.3.2B.3 NE-DC Physical Layer Baseline Implementation Capabilities + +###### A.4.3.2B.3.0 General NE-DC capabilities + +**Table A.4.3.2B.3.0-1: Downlink NE-DC capabilities (for one or more of the supported NE-DC configurations)** + +| Item | Bandwidth Class | Ref. | Comments | +|------|--------------------------|----------------|----------| +| 1 | DL NE-DC with 2 carriers | 38.101-3, 5.5B | | +| 2 | DL NE-DC with 3 carriers | 38.101-3, 5.5B | | +| 3 | DL NE-DC with 4 carriers | 38.101-3, 5.5B | | +| 4 | DL NE-DC with 5 carriers | 38.101-3, 5.5B | | +| 5 | DL NE-DC with 6 carriers | 38.101-3, 5.5B | | + +**Table A.4.3.2B.3.0-1A: Downlink NE-DC capabilities (number of NR DL carriers)** + +| Item | Bandwidth Class | Ref. | Comments | +|------|--------------------------------|----------------|----------| +| 1 | DL NE-DC with 1 NR DL carriers | 38.101-3, 5.5B | | + +**Table A.4.3.2B.3.0-2: Uplink NE-DC capabilities (for one or more of the supported NE-DC configurations)** + +| Item | Bandwidth Class | Ref. | Comments | +|------|--------------------------|----------------|----------| +| 1 | UL NE-DC with 2 carriers | 38.101-3, 5.5B | | + +**Table A.4.3.2B.3.0-2A: Uplink NE-DC capabilities (number of NR UL carriers)** + +| Item | Bandwidth Class | Ref. | Comments | +|------|--------------------------------|----------------|----------| +| 1 | UL NE-DC with 1 NR UL carriers | 38.101-3, 5.5B | | + +###### A.4.3.2B.3.1 Inter-band NE-DC within FR1 + +###### A.4.3.2B.3.1.1 Inter-band NE-DC within FR1 (two bands) + +**Table A.4.3.2B.3.1.1-1: Downlink Bandwidth Class Combination capabilities for Inter-band NE-DC within FR1 and two bands (for one or more of the supported DC configurations in Table A.4.3.2B.3.1.1-2)** + +| Item | DL inter-band NE-DC within FR1 Bandwidth Class | Ref. | Mnemonic | Comments | +|------|---------------------------------------------------------------------|------------------------------------------|----------------------------------------------------|----------| +| 1 | Inter-band NE-DC within FR1 BW Class Combination A_A (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4a.1 | pc_DL_inter_band
_NE_DC_FR1_2B
_Class_A_A | | +| 2 | Inter-band NE-DC within FR1 BW Class Combination (2A)_A (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4a.1 | pc_DL_inter_band
_NE_DC_FR1_2B
_Class_(2A)_A | | +| 3 | Inter-band NE-DC within FR1 BW Class Combination A_C (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4a.1 | pc_DL_inter_band
_NE_DC_FR1_2B
_Class_A_C | | +| 4 | Inter-band NE-DC within FR1 BW Class Combination A_(2A) (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4a.1 | pc_DL_inter_band
_NE_DC_FR1_2B
_Class_A_(2A) | | + +**Table A.4.3.2B.3.1.1-1a: Uplink Bandwidth Class Combination capabilities for Inter-band NE-DC within FR1 and two bands (for one or more of the supported configurations in Table A.4.3.2B.3.1.1-2)** + +| Item | UL inter-band NE-DC within FR1 Bandwidth Class | Ref. | Mnemonic | Comments | +|------|---------------------------------------------------------------------|------------------------------------------|-------------------------------------------------|----------| +| 1 | UL Inter-band NE-DC within FR1 BW Class Combination A_A (two bands) | 36.101, 5.6A.1
38.101-3,
5.5B.4a.1 | pc_UL_inter_band
_NE_DC_FR1_2B
_Class_A_A | | + +**Table A.4.3.2B.3.1.1-2: Supported Inter-band NE-DC configurations within FR1 (two bands)** + +| NE-DC configuration / Item (Note 1) | Release | Supported | Supported NE-DC Bandwidth Class(es) in UL | Supported Bandwidth Combination Set(s) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-----------|-------------------------------------------|----------------------------------------| +| DC_n28A_3A | Rel-17 | | | | +| DC_n28A_3C | Rel-17 | | | | +| DC_n28A_39A | Rel-17 | | | | +| DC_n28A_39C | Rel-17 | | | | +| NOTE 1: Notation used for inter-band NE-DC Bands is according to TS 38.101-3 [25] Table 5.5B.4a.1-1, e.g. 'DC_n28A_3A' indicates NE-DC operation on NR band n28 with NR DL Bandwidth Class A and E-UTRA band 3 with E-UTRA DL CA Bandwidth Class A. | | | | | + +**Table A.4.3.2B.3.1.1-3: Inter-band NE-DC within FR1 (two bands) PC3 UE RF Baseline Implementation Capabilities** + +| Item | NE-DC configuration | Inter-band NE-DC within FR1 (two bands) PC3 UE RF Baseline Implementation Capabilities | Ref. | Release | Mnemonic | Comments | +|------|----------------------------|-------------------------------------------------------------------------------------------------------------------------|------------------------|---------|-----------------------------|----------| +| 1 | DC_n28A_3A
DC_n28A_3C | NR Frequency band: 703–748 MHz (UL), 758 MHz–803 MHz (DL)
LTE Frequency band: 1710–1785 MHz (UL), 1805–1880 MHz (DL) | 38.101-3,
6.2B.1.3a | Rel-17 | pc_nrBand28_Band3_PC3_Supp | | +| 2 | DC_n28A_39A
DC_n28A_39C | NR Frequency band: 703–748 MHz (UL), 758 MHz–803 MHz (DL)
LTE Frequency band: 1880–1920 MHz | 38.101-3,
6.2B.1.3a | Rel-17 | pc_nrBand28_Band39_PC3_Supp | | + +**Table A.4.3.2B.3.1.1-3a: Inter-band NE-DC within FR1 (two bands) NR part power class UE RF Baseline Implementation Capabilities** + +| Item | EN-DC configuration | UE Physical Layer Baseline Implementation Capabilities | Ref. | Release | Mnemonic | Supported NR part power class | +|------|----------------------------|--------------------------------------------------------------------|--------------------|---------|-----------------------------------------|-------------------------------| +| 1 | DC_n28A_3A
DC_n28A_3C | DC_n28A_3A NR part power class
DC_n28A_3C NR part power class | 38.306,
4.2.7.1 | Rel-16 | pc_nrBand28_Band3_powerClassNRPart_r16 | | +| 2 | DC_n28A_39A
DC_n28A_39C | DC_n28A_39A NR part power class
DC_n28A_39C NR part power class | 38.306,
4.2.7.1 | Rel-16 | pc_nrBand28_Band39_powerClassNRPart_r16 | | + +**Table A.4.3.2B.3.1.1-4: UE Power Class implementation Capabilities for inter-band NE-DC within FR1 (two bands)** + +| Item | UE Power Class implementation Capabilities | Ref. | Comments | +|------|--------------------------------------------------------------|------------------------|---------------------------------------------------| +| 1 | UE Power Class 3 for Inter-band NE-DC within FR1 (two bands) | 38.101-3,
6.2B.1.3a | Applicable to the bands in Table A.4.3.2B.3.1.1-3 | + +#### A.4.3.2C NR SUL Physical Layer Baseline Implementation Capabilities + +NOTE: See Annex B for status of completed NR SUL configurations in this version of 3GPP UE conformance test specifications. + +##### A.4.3.2C.1 General NR SUL capabilities + +**Table A.4.3.2C.1-1: Uplink NR SUL capabilities (for one or more of the supported NR SUL configurations)** + +| Item | Bandwidth Class | Ref. | Comments | +|------|---------------------------|----------------|----------| +| 1 | UL NR SUL with 2 carriers | 38.101-1, 5.5C | | +| 2 | UL NR SUL with 3 carriers | 38.101-1, 5.5C | | + +##### A.4.3.2C.2 SUL band combinations without CA + +Table A.4.3.2C.2-1: Supported SUL configurations without CA + +| SUL configuration / Item (Note 1) | Release | Supported | | Supported Bandwidth Combination Set(s) | Supported ULTxSwitching Band Pair (Note 2, 3) | +|-----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|--|----------------------------------------|-----------------------------------------------| +| | | | | | | +| SUL_n41A-n83A | Rel-17 | | | | | +| SUL_n78A-n80A | Rel-15 | | | | | +| SUL_n78A-n84A | Rel-15 | | | | | +| SUL_n79A-n83A | Rel-17 | | | | | +| Note 1: | Notation used for SUL configurations is according to TS 38.101-1 [23] Table 5.5C-1, e.g. 'SUL_n78A-n80A' indicates SUL operation on NR bands n78 and n80 with UL CA Bandwidth Class A on both bands. | | | | | +| Note 2: | The ULTxSwitching capability can be reported on SUL band combinations. The UE supplier shall indicate SUL band pairs on which it supports ULTxSwitching. For this release of specification valid choices are 'N' and 'nX-nY', where both nX and nY are NR bands. For example, for SUL_n78A-n80A, N would mean not supporting ULTxSwitching, 'n78-n80' would mean supporting of ULTxSwitching on this band pair. The ULTxSwitching is only tested with 2 UL CCs, so UE is allowed to report 'N' by default for SUL configuration with > 2 component carriers. | | | | | +| Note 3: | ULSwitching(Table A.4.3.2C.2-1) shall return all supported SUL Configurations where at least one SUL band pair was declared in column "Supported ULTxSwitching Band Pair". | | | | | + +##### A.4.3.2C.3 SUL band combinations with CA + +Table A.4.3.2C.3-1: Supported SUL configurations with Intra-band non-contiguous CA + +| NR SUL with CA configuration / Item (Note 1) | Release | Supported | | Supported SUL configuration in UL | Supported Bandwidth Combination Set(s) | Supported ULTxSwitching Band Pair (Note 2, 3) | +|----------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|--|-----------------------------------|----------------------------------------|-----------------------------------------------| +| | | | | | | | +| TBD | TBD | | | | | | +| Note 1: | Notation used for SUL configurations is according to TS 38.101-1 [23] Table 5.5C-2. | | | | | | +| Note 2: | The ULTxSwitching capability can be reported on SUL band combinations. The UE supplier shall indicate SUL band pairs on which it supports ULTxSwitching. For this release of specification valid choices are 'N' and 'nX-nY', where both nX and nY are NR bands. For example, for SUL_n78A-n80A, N would mean not supporting ULTxSwitching, 'n78-n80' would mean supporting of ULTxSwitching on this band pair. | | | | | | +| Note 3: | ULSwitching(Table A.4.3.2C.2-1) shall return all supported SUL Configurations where at least one SUL band pair was declared in column "Supported ULTxSwitching Band Pair". | | | | | | + +**Table A.4.3.2C.3-2: Supported SUL****configurations with Intra-band contiguous CA** + +| NR SUL configuration / Item (Note 1) | Release | Supported | | Supported Bandwidth Combination Set(s) | Supported ULTxSwitching Band Pair (Note 2, 3) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-----------|-----------------------------------|----------------------------------------|-----------------------------------------------| +| | | | Supported SUL configuration in UL | | | +| CA_n41C-n83A | Rel-17 | | | | | +| CA_n78C-n80A | Rel-17 | | | | | +| CA_n78C-n84A | Rel-17 | | | | | +| CA_n79C-n83A | Rel-17 | | | | | +| Note 1: Notation used for SUL configurations is according to TS 38.101-1 [23] Table 5.5C-3. e.g. 'CA_n41C-n83A' indicates SUL operation on NR bands n41 and n83 with DL CA Bandwidth Class C on band n41. | | | | | | +| Note 2: The ULTxSwitching capability can be reported on SUL band combinations. The UE supplier shall indicate SUL band pairs on which it supports ULTxSwitching. For this release of specification valid choices are 'N' and 'nX-nY', where both nX and nY are NR bands. For example, for SUL_n78A-n80A, N would mean not supporting ULTxSwitching, 'n78-n80' would mean supporting of ULTxSwitching on this band pair. | | | | | | +| Note 3: ULSwitching(Table A.4.3.2C.2-1) shall return all supported SUL Configurations where at least one SUL band pair was declared in column "Supported ULTxSwitching Band Pair". | | | | | | + +**Table A.4.3.2C.3-3: Supported SUL configurations with Inter-band CA** + +| NR SUL configuration / Item (Note 1) | Release | Supported | | Supported Bandwidth Combination Set(s) | Supported ULTxSwitching Band Pair (Note 2, 3) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-----------|-----------------------------------|----------------------------------------|-----------------------------------------------| +| | | | Supported SUL configuration in UL | | | +| CA_n1A_n78A-n80A | Rel-17 | | | | | +| CA_n1A_n78A-n84A | Rel-17 | | | | | +| CA_n3A_n78A-n80A | Rel-17 | | | | | +| CA_n28A_n41A-n83A | Rel-17 | | | | | +| CA_n28A_n79A-n83A | Rel-17 | | | | | +| Note 1: Notation used for SUL configurations is according to TS 38.101-1 [23] Table 5.5C-4. e.g. 'CA_n1A_n78A-n84A' indicates SUL operation on NR bands n1, n78 and n84 with DL CA Bandwidth Class A on bands n1 and n78. | | | | | | +| Note 2: The ULTxSwitching capability can be reported on SUL band combinations. The UE supplier shall indicate SUL band pairs on which it supports ULTxSwitching. For this release of specification valid choices are 'N' and 'nX-nY', where both nX and nY are NR bands. For example, for SUL_n78A-n80A, N would mean not supporting ULTxSwitching, 'n78-n80' would mean supporting of ULTxSwitching on this band pair. | | | | | | +| Note 3: ULSwitching(Table A.4.3.2C.2-1) shall return all supported SUL Configurations where at least one SUL band pair was declared in column "Supported ULTxSwitching Band Pair". | | | | | | + + + +#### A.4.3.3 PDCP Implementation Capabilities + +**Table A.4.3.3-1: UE PDCP Implementation Capabilities** + +| Item | UE PDCP Implementation Capabilities | Ref. | Release | Mnemonic | M | If indicated "Yes" the feature shall be implemented and successfully tested for the corresponding release | Comments | +|------|----------------------------------------------------------------|-------------------------------|---------|---------------------------------------|-----|-----------------------------------------------------------------------------------------------------------|--------------------------------------------------------------| +| 1 | Support 12 bit length of PDCP sequence number | 38.306, 4.2.4 | Rel-15 | pc_shortSN | Yes | Yes (for RedCap UE) | This PICS shall always be true for RedCap UE. | +| 1A | Support of 18 bit length of PDCP sequence number | 38.822, 4.2, 38.306, 4.2.21.3 | Rel-15 | pc_longSN | No | Yes (for non-RedCap UE) | This PICS shall always be true for non-RedCap UE. | +| 2 | Supports Out of order delivery of data to upper layers by PDCP | 38.306, 4.2.4 | Rel-15 | pc_outOfOrderDelivery | No | | | +| 3 | Support CA-based PDCP duplication over MCG or SCG DRB | 38.306, 4.2.4 | Rel-15 | pc_pdcp_DuplicationMCG_OrSCG_DRB | No | | | +| 4 | Support PDCP duplication over split DRB | 38.306, 4.2.4 | Rel-15 | pc_pdcp_DuplicationSplitDRB | No | | | +| 5 | Support PDCP duplication with more than two RLC entities | 38.306, 4.2.4 | Rel-16 | pc_pdcp_DuplicationMoreThanTwoRLC_r16 | No | | specifically for TSC (time sensitive communication) services | +| 6 | Support PDCP duplication over split SRB1/2 | 38.306, 4.2.4 | Rel-15 | pc_pdcp_DuplicationSplitSRB | No | | | + +| | | | | | | | | +|----|--------------------------------------------------------------------|---------------|--------|----------------------------------|----|--|--------------------------------------------------------------| +| 7 | Support EHC (Ethernet header compression) | 38.306, 4.2.4 | Rel-16 | pc_NR_ehc_r16 | No | | specifically for TSC (time sensitive communication) services | +| 8 | Support UDC (Uplink data compression) | 38.306, 4.2.4 | Rel-17 | pc_NR_udc_r17 | No | | | +| 9 | Support standard Dictionary | 38.306, 4.2.4 | Rel-17 | pc_NR_udc_standardDictionary_r17 | No | | | +| 10 | Support continuation of uplink data compression protocol operation | 38.306, 4.2.4 | Rel-17 | pc_NR_udc_continueUDC_r17 | No | | | + +#### A.4.3.4 RLC Implementation Capabilities + +Table A.4.3.4-1: UE RLC Implementation Capabilities + +| Item | UE RLC Implementation Capabilities | Ref. | Release | Mnemonic | M | If indicated "Yes" the feature shall be implemented and successfully tested for the corresponding release | Comments | +|------|----------------------------------------------------------|------------------|---------|-------------------|-----|-----------------------------------------------------------------------------------------------------------|---------------------------------------------------| +| 1A | Support RLC AM with 18 bit length of RLC sequence number | 38.306, 4.2.21.4 | Rel-15 | pc_am_WithLongSN | No | Yes (for non-RedCap UE) | This PICS shall always be true for non-RedCap UE. | +| 1 | Support RLC AM with 12 bit length of RLC sequence number | 38.306, 4.2.5 | Rel-15 | pc_am_WithShortSN | Yes | Yes (for RedCap UE) | This PICS shall always be true for RedCap UE. | +| 2 | Support RLC UM with 12 bit length of RLC sequence number | 38.306, 4.2.5 | Rel-15 | pc_um_WithLongSN | Yes | | | +| 3 | Support RLC UM with 6 bit length of RLC sequence number | 38.306, 4.2.5 | Rel-15 | pc_um_WithShortSN | Yes | | | + +#### A.4.3.5 MAC Implementation Capabilities + +**Table A.4.3.5-1: UE MAC Implementation Capabilities** + +| Item | UE MAC Implementation Capabilities | Ref. | Release | Mnemonic | M | If indicated "Yes" the feature shall be implemented and successfully tested for the corresponding release | Comments | +|------|---------------------------------------------------------------------------------------------------------------------|---------------|---------|----------------------------------------|-----|-----------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------| +| 1 | Support long DRX cycle | 38.306, 4.2.6 | Rel-15 | pc_longDRX_Cycle | Yes | | | +| 2 | Support short DRX cycle | 38.306, 4.2.6 | Rel-15 | pc_shortDRX_Cycle | Yes | | | +| 3 | Support skipping of UL transmission for an uplink grant indicated on PDCCH if no data is available for transmission | 38.306, 4.2.6 | Rel-15 | pc_skipUplinkTxDynamic | No | | | +| 4 | Supports the logicalChannelSR-DelayTimer | 38.306, 4.2.6 | Rel-15 | pc_logicalChannelSR_DelayTimer | No | | | +| 5 | Supports DRX adaptation | 38.306, 4.2.6 | Rel-16 | pc_DRX_Adaptation | No | | | +| 6 | Support LCH-based prioritization | 38.306, 4.2.6 | Rel-16 | pc_lch_PriorityBasedPrioritization_r16 | No | | | +| 7 | Supports autonomous transmission of the MAC PDU generated for a deprioritized configured uplink grant | 38.306, 4.2.6 | Rel-16 | pc_autonomousTransmission_r16 | No | | | +| 8 | Supports the bit rate recommendation message from the gNB to the UE as specified in TS 38.321 | 38.306, 4.2.6 | Rel-15 | pc_recommendedBitRate | No | | | +| 9 | Supports the bit rate recommendation query message from the UE to the gNB as specified in TS 38.321. | 38.306, 4.2.6 | Rel-15 | pc_recommendedBitRateQuery | No | | This field is only applicable if the UE supports pc_recommendedBitRate. | +| 10 | Support PUSCH transmissions on multiple configured uplink grants | 38.306, 4.2.6 | Rel-16 | pc_multipleConfiguredGrants_r16 | No | | | +| 11 | Support the selection of logical channels for each UL grant based on RRC configured restriction | 38.306, 4.2.6 | Rel-15 | pc_lcp_Restriction | No | | | + +| | | | | | | | | +|----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|--------|----------------------------------------|----|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 12 | Support direct NR SCG SCell activation, as specified in TS 38.321, upon SCell addition and upon reconfiguration with sync of the SCG, both performed via an RRCReconfiguration message received via SRB3 or contained in an RRC(Connection)Reconfiguration message received via SRB1, as specified in TS 38.331 and TS 36.331 | 38.306, 4.2.6 | Rel-16 | pc_directSCG_SCellActivation_r16 | No | | A UE indicating support of directSCG-SCellActivation-r16 shall indicate support of EN-DC or support of NGEN-DC as specified in TS 36.331 or support of NR-DC as specified in TS 38.331. | +| 13 | Support direct NR MCG SCell activation, as specified in TS 38.321, upon SCell addition, upon reconfiguration with sync of the MCG, as specified in TS 38.331. | 38.306, 4.2.6 | Rel-16 | pc_directMCG_SCellActivation_r16 | No | | | +| 14 | Support direct NR MCG SCell activation, as specified in TS 38.321, upon reception of an RRCResume message, as specified in TS 38.331. | 38.306, 4.2.6 | Rel-16 | pc_directMCG_SCellActivationResume_r16 | No | | | +| 15 | Support direct NR SCG SCell activation, as specified in TS 38.321:
- upon reception of an RRCReconfiguration included in an RRCConnectionResume message, as specified in TS 38.331 and TS 36.331, if the UE indicates support of EN-DC or NGEN-DC, and support of resumeWithSCG-Config-r16 as specified in TS 36.331,
- upon reception of an RRCReconfiguration included in an RRCResume message, as specified in TS 38.331, if the UE indicates support of NR-DC and of resumeWithSCG-Config-r16 as specified in TS 38.331. | 38.306, 4.2.6 | Rel-16 | pc_directSCG_SCellActivationResume_r16 | No | | A UE indicating support of directSCG-SCellActivationResume-r16 shall indicate support of EN-DC or NGEN-DC and support of resumeWithSCG-Config-r16 as specified in TS 36.331 or indicate support of NR-DC and of resumeWithSCG-Config-r16 as specified in TS 38.331. | + +| | | | | | | | | +|----|----------------------------------------------------------------------------------------------------------------------------------|------------------|--------|---------------------|----|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 16 | Support services with survival time requirement using configured grant resource and PDCP duplication, as specified in TS 38.321. | 38.306,
4.2.6 | Rel-17 | pc_survivalTime_r17 | No | | A UE supporting this feature shall support pdcp-DuplicationMCG-orSCG-DRB or pdcp-DuplicationSplitDRB. A UE supporting this feature shall also support configuredUL-GrantType1-v1650 or configuredUL-GrantType2-v1650. | +|----|----------------------------------------------------------------------------------------------------------------------------------|------------------|--------|---------------------|----|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +#### A.4.3.6 Measurement Capabilities + +**Table A.4.3.6-1: UE Measurement Capabilities** + +| Item | UE Measurement Capabilities | Ref. | Release | Mnemonic | M | If indicated "Yes" the feature shall be implemented and successfully tested for the corresponding release | Comments | +|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------|---------------------------------|-----|-----------------------------------------------------------------------------------------------------------|----------| +| 1 | Support NR measurements and events A triggered reporting | 38.306, 4.2.9 | Rel-15 | pc_eventA_MeasAndReport | Yes | | | +| 2 | Support two independent measurement gap configurations for FR1 and FR2 | 38.306, 4.2.9 | Rel-15 | pc_independentGapConfig | No | | | +| 3 | Support NR intra-frequency and inter-frequency measurements and at least periodical reporting | 38.306, 4.2.9 | Rel-15 | pc_intraAndInterF_MeasAndReport | Yes | | | +| 4 | Support CSI-RSRP and CSI-RSRQ measurement as specified in TS38.215 [21], where CSI-RS resource is configured with an associated SS/PBCH | 38.306, 4.2.9 | Rel-15 | pc_csi_RSRP_AndRSRQ_MeasWithSSB | No | | | +| 5 | Support inter-RAT E-UTRA measurements and events B triggered reporting | 38.306, 4.2.9 | Rel-15 | pc_eventB_MeasAndReport | Yes | | | +| 6 | Support SS-SINR measurements | 38.306, 4.2.9 | Rel-15 | pc_ss_SINR_Meas | No | | | +| 7 | Support acquisition of relevant information from a neighbouring E-UTRA cell by reading the SI of the neighbouring cell and reporting the acquired information to the network as specified in TS 38.331 [9] when the EN-DC is not configured. | 38.306, 4.2.9 | Rel-15 | pc_eutra_CGI_Reporting | Yes | | | +| 7a | Support acquisition of relevant information from a neighbouring E-UTRA cell by reading the SI of the neighbouring cell using autonomous gap and reporting the acquired information to the network as specified in TS 38.331 [9] when MR-DC is not configured | 38.306,4.2.9 | Rel-16 | pc_eutra_AutonomousGaps_r16 | No | | | + +| | | | | | | | | +|----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|--------|---------------------------|-----|--|--| +| 8 | Support acquisition of relevant information from a neighbouring intra-frequency or inter-frequency NR cell by reading the SI of the neighbouring cell and reporting the acquired information to the network as specified in TS 38.331 [9] when EN-DC is not configured. | 38.306, 4.2.9 | Rel-15 | pc_nr_CGI Reporting | Yes | | | +| 8a | Support acquisition of relevant information from a neighbouring NR cell by reading the SI of the neighbouring cell using autonomous gap and reporting the acquired information to the network as specified in TS 38.331 [9] when MR-DC is not configured. | 38.306, 4.2.9 | Rel-16 | pc_nr_Autonomous Gaps_r16 | No | | | +| 9 | Support acquisition of relevant information from a neighbouring intra-frequency or inter-frequency NR cell by reading the SI of the neighbouring cell and reporting the acquired information to the network as specified in TS 38.331 [9] when the EN-DC is configured. | 38.306, 4.2.9 | Rel-15 | pc_nr_CGI Reporting_ENDC | Yes | | | +| 10 | Support shorter measurement gap length (i.e. gp2 and gp3 ) for independent measurement gap configuration on FR1 and per-UE gap in (NG)EN-DC. | 36.331, 6.3.6 | Rel-15 | pc_gp2_gp3_en_dc | No | | | +| 11 | Support NR supports gap pattern 4 for independent measurement gap configuration on FR1 and per-UE gap in (NG)EN-DC | 36.331, 6.3.6 | Rel-15 | pc_gp4_en_dc | No | | | +| 12 | Support NR supports gap pattern 5 for independent measurement gap configuration on FR1 and per-UE gap in (NG)EN-DC | 36.331, 6.3.6 | Rel-15 | pc_gp5_en_dc | No | | | +| 13 | Support NR supports gap pattern 6 for independent measurement gap configuration on FR1 and per-UE gap in (NG)EN-DC | 36.331, 6.3.6 | Rel-15 | pc_gp6_en_dc | No | | | + +| | | | | | | | | +|----|---------------------------------------------------------------------------------------------------------------------|---------------|--------|---------------|----|--|--| +| 14 | Support NR supports gap pattern 7 for independent measurement gap configuration on FR1 and per-UE gap in (NG)EN-DC | 36.331, 6.3.6 | Rel-15 | pc_gp7_en_dc | No | | | +| 15 | Support NR supports gap pattern 8 for independent measurement gap configuration on FR1 and per-UE gap in (NG)EN-DC | 36.331, 6.3.6 | Rel-15 | pc_gp8_en_dc | No | | | +| 16 | Support NR supports gap pattern 9 for independent measurement gap configuration on FR1 and per-UE gap in (NG)EN-DC | 36.331, 6.3.6 | Rel-15 | pc_gp9_en_dc | No | | | +| 17 | Support NR supports gap pattern 10 for independent measurement gap configuration on FR1 and per-UE gap in (NG)EN-DC | 36.331, 6.3.6 | Rel-15 | pc_gp10_en_dc | No | | | +| 18 | Support NR supports gap pattern 11 for independent measurement gap configuration on FR1 and per-UE gap in (NG)EN-DC | 36.331, 6.3.6 | Rel-15 | pc_gp11_en_dc | No | | | +| 19 | Support measurement gap pattern 2 configured by NR RRC. | 38.306, 4.2.9 | Rel-15 | pc_gp2_nr | No | | | +| 20 | Support measurement gap pattern 3 configured by NR RRC. | 38.306, 4.2.9 | Rel-15 | pc_gp3_nr | No | | | +| 21 | Support measurement gap pattern 4 configured by NR RRC. | 38.306, 4.2.9 | Rel-15 | pc_gp4_nr | No | | | +| 22 | Support measurement gap pattern 5 configured by NR RRC. | 38.306, 4.2.9 | Rel-15 | pc_gp5_nr | No | | | +| 23 | Support measurement gap pattern 6 configured by NR RRC. | 38.306, 4.2.9 | Rel-15 | pc_gp6_nr | No | | | +| 24 | Support measurement gap pattern 7 configured by NR RRC. | 38.306, 4.2.9 | Rel-15 | pc_gp7_nr | No | | | +| 25 | Support measurement gap pattern 8 configured by NR RRC. | 38.306, 4.2.9 | Rel-15 | pc_gp8_nr | No | | | +| 26 | Support measurement gap pattern 9 configured by NR RRC. | 38.306, 4.2.9 | Rel-15 | pc_gp9_nr | No | | | +| 27 | Support measurement gap pattern 10 configured by NR RRC. | 38.306, 4.2.9 | Rel-15 | pc_gp10_nr | No | | | + +| | | | | | | | | +|----|--------------------------------------------------------------------------------------------------------------------------------------------|---------------|--------|-------------------------------------|----|--|--| +| 28 | Support measurement gap pattern 11 configured by NR RRC. | 38.306, 4.2.9 | Rel-15 | pc_gp11_nr | No | | | +| 29 | Support measurement gap pattern 12 configured by NR RRC. | 38.306, 4.2.9 | Rel-15 | pc_gp12_nr | No | | | +| 30 | Support measurement gap pattern 15 configured by NR RRC. | 38.306, 4.2.9 | Rel-15 | pc_gp15_nr | No | | | +| 31 | Support measurement gap pattern 16 configured by NR RRC. | 38.306, 4.2.9 | Rel-15 | pc_gp16_nr | No | | | +| 32 | Support measurement gap pattern 17 configured by NR RRC. | 38.306, 4.2.9 | Rel-15 | pc_gp17_nr | No | | | +| 34 | Support measurement gap pattern 18 configured by NR RRC. | 38.306, 4.2.9 | Rel-15 | pc_gp18_nr | No | | | +| 35 | Support measurement gap pattern 19 configured by NR RRC. | 38.306, 4.2.9 | Rel-15 | pc_gp19_nr | No | | | +| 36 | Support measurement gap pattern 20 configured by NR RRC. | 38.306, 4.2.9 | Rel-15 | pc_gp20_nr | No | | | +| 37 | Support measurement gap pattern 21 configured by NR RRC. | 38.306, 4.2.9 | Rel-15 | pc_gp21_nr | No | | | +| 38 | Support measurement gap pattern 22 configured by NR RRC. | 38.306, 4.2.9 | Rel-15 | pc_gp22_nr | No | | | +| 39 | Support measurement gap pattern 23 configured by NR RRC. | 38.306, 4.2.9 | Rel-15 | pc_gp23_nr | No | | | +| 40 | Support CSI-RSRP and CSI-RSRQ measurement as specified in TS38.215 [21], where CSI-RS resource is configured without an associated SS/PBCH | 38.306, 4.2.9 | Rel-15 | pc_csi_RSRP_And_RSRQ_MeasWithoutSSB | No | | | + +| | | | | | | | | +|-----|----------------------------------------------------|----------------|--------|-----------------------|-----|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 41 | Support CSI-RS based Radio Link Monitoring for FR1 | 38.306, 4.2.9 | Rel-15 | pc_CSI_RS_RLM_FR1 | Yes | | If the UE supports this feature, the UE needs to report maxNumberRes ource-CSI-RS-RLM in its capability report. If the UE doesn't support CSI-RS based RLM, it will not include this IE in its capability report. | +| 41a | Support CSI-RS based Radio Link Monitoring for FR2 | 38.306, 4.2.9 | Rel-15 | pc_CSI_RS_RLM_FR2 | Yes | | If the UE supports this feature, the UE needs to report maxNumberRes ource-CSI-RS-RLM in its capability report. If the UE doesn't support CSI-RS based RLM, it will not include this IE in its capability report. | +| 42 | Support of E-UTRA RS-SINR measurements | 38.306, 4.2.10 | Rel-15 | pc_RS_SINR_Meas EUTRA | No | | | + +| | | | | | | | | +|----|-------------------------------------------------------------------------------------|---------------|--------|---------------------------------|----|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 43 | Support of SFTD measurements between a E-UTRA PCell and an NR PSCell in FDD | 38.306, 4.2.9 | Rel-15 | pc_SFTD_MeasPS
Cell_MRDC_FDD | No | | The SFTD measurement support should be indicated in MRDC capabilities for EN-DC. The support needs to be declared for FDD and TDD separately | +| 44 | Support of SFTD measurements between a E-UTRA PCell and an NR PSCell in TDD | 38.306, 4.2.9 | Rel-15 | pc_SFTD_MeasPS
Cell_MRDC_TDD | No | | The SFTD measurement support should be indicated in MRDC capabilities for EN-DC. The support needs to be declared for FDD and TDD separately | +| 45 | Support of relaxed RRM measurements of neighbour cells in RRC_IDLE/RRC_INACTIVE | 38.306, 5.6 | Rel-16 | pc_Relaxed_Measurement | No | | | +| 46 | Support of SFTD measurements between a E-UTRA PCell and an NR neighbour cell in FDD | 38.306, 4.2.9 | Rel-15 | pc_SFTD_MeasNR
_Cell_FDD | No | |

The support needs to be declared for FDD and TDD separately

The SFTD measurement support can only be indicated in MRDC capabilities for EN-DC

| + +| | | | | | | | | +|----|-----------------------------------------------------------------------------------------------------------------------|---------------|--------|-----------------------------|----|--|------------------------------------------------------------------------------------------------------------------------------------------------------| +| 47 | Support of SFTD measurements between a E-UTRA PCell and an NR neighbour cell in TDD | 38.306, 4.2.9 | Rel-15 | pc_SFTD_MeasNR_Cell_TDD | No | | The support needs to be declared for FDD and TDD separately

The SFTD measurement support can only be indicated in MRDC capabilities for EN-DC | +| 48 | Support of SFTD measurements between a NR PCell and an NR neighbour cell in FDD | 38.306, 4.2.9 | Rel-15 | pc_SFTD_MeasNR_Neigh_FDD | No | | The support needs to be declared for FDD and TDD separately | +| 49 | Support of SFTD measurements between a NR PCell and an NR neighbour cell in TDD | 38.306, 4.2.9 | Rel-15 | pc_SFTD_MeasNR_Neigh_TDD | No | | The support needs to be declared for FDD and TDD separately | +| 50 | Support of SFTD measurements between a NR PCell and an NR PSCell in FDD | 38.306, 4.2.9 | Rel-15 | pc_SFTD_MeasPSCell_NRDC_FDD | No | | The SFTD measurement support should be indicated in UE-NR-Capability | +| 51 | Support of SFTD measurements between a NR PCell and an NR PSCell in TDD | 38.306, 4.2.9 | Rel-15 | pc_SFTD_MeasPSCell_NRDC_TDD | No | | The SFTD measurement support should be indicated in UE-NR-Capability | +| 52 | Support of acquisition of CGI related information from a neighbouring intra-frequency or inter-frequency NPN CAG cell | 38.306, 4.2.9 | Rel-16 | pc_nr_CGI_Reporting_NPN_r16 | No | | | + +| | | | | | | | | +|-----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|--------|---------------------------------|-----|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 53 | Supports periodic EUTRA measurement and reporting. | 38.306, 4.2.9 | Rel-15 | pc_periodicEUTRA_MeasAndReport | Yes | | | +| 54 | Support configuration of NR SSB measurements in RRC_IDLE/RRC_INACTIVE and reporting of the corresponding results upon network request as specified in TS 38.331 [9] | 38.306, 4.2.9 | Rel-16 | pc_idleInactiveNR_MeasReport | No | | | +| 55 | Support configuration of E-UTRA measurements in RRC_IDLE/RRC_INACTIVE and reporting of the corresponding results upon network request as specified in TS 38.331 [9] | 38.306, 4.2.9 | Rel-16 | pc_idleInactiveEUTRA_MeasReport | No | | | +| 56 | Support SRS-RSRP measurements between a NR Pcell and an interfering UE, upon network request as specified in 38.331 [9] | 38.306, 4.2.9 | Rel-16 | pc_nr_CLI_Reportin
g_r16 | No | | If the UE supports this feature, the UE needs to report maxNumberCLI-SRS-RSRP-r16 and maxNumberPerSlotCLI-SRS-RSRP-r16
If the UE doesn't support CLI SRS-RSRP measurement, it will not include this IE in its capability report. | +| 56A | Support SRS-RSRP measurements and periodical reporting and measurement event triggering based on SRS-RSRP | 38.306, 4.2.9 | Rel-16 | pc_cli_SRS_RSRP_Meas_r16 | No | | If the UE supports this feature, the UE needs to report maxNumberCLI-SRS-RSRP-r16 and maxNumberPerSlotCLI-SRS-RSRP-r16 | + +| | | | | | | | | +|-----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|--------|-----------------------------|-----|--|--------------------------------------------------------------------------------------| +| 56B | Support CLI RSSI measurements and periodical reporting and measurement event triggering | 38.306, 4.2.9 | Rel-16 | pc_cli_RSSI_Meas_r16 | No | | If the UE supports this feature, the UE needs to report maxNumberCLI-RSSI-r16 | +| 57 | Support acquisition of relevant information from a neighbouring E-UTRA cell by reading the SI of the neighbouring cell and reporting the acquired information to the network as specified in TS 38.331 [9] when the NE-DC is configured. | 38.306, 4.2.9 | Rel-15 | pc_eutra_CGI_Reporting_NEDC | No | | | +| 58 | Support acquisition of relevant information from a neighbouring E-UTRA cell by reading the SI of the neighbouring cell and reporting the acquired information to the network as specified in TS 38.331 [9] when the NR-DC is configured wherein MN and SN have different DRX cycles, or on-duration configured by MN does not contain on-duration configured by SN if the DRX cycles are the same. | 38.306, 4.2.9 | Rel-15 | pc_eutra_CGI_Reporting_NRDC | No | | | +| 59 | Support acquisition of relevant information from a neighbouring intra-frequency or inter-frequency NR cell by reading the SI of the neighbouring cell and reporting the acquired information to the network as specified in TS 38.331 [9] when the NE-DC is configured. | 38.306, 4.2.9 | Rel-15 | pc_nr_CGI_Reporting_NEDC | Yes | | | + +| | | | | | | | | +|----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|--------|-----------------------------------------|-----|--|--| +| 60 | Support acquisition of relevant information from a neighbouring intra-frequency or inter-frequency NR cell by reading the SI of the neighbouring cell and reporting the acquired information to the network as specified in TS 38.331 [9] when the NR-DC is configured wherein MN and SN have different DRX cycles, or on-duration configured by MN does not contain on-duration configured by SN if the DRX cycles are the same. | 38.306, 4.2.9 | Rel-15 | pc_nr_CGIReporting_NRDC | Yes | | | +| 61 | Supports performing eNB-configured SSB-based RRM measurements for EN-DC configured NR FR1 carrier(s) in RRC_IDLE and reporting them when requested by the eNB while resuming from RRC_IDLE or in RRC_CONNECTED, as specified in TS 36.331 [5]. | 36.306, 4.3.6.41 | Rel-16 | pc_nrIdleInactiveNR FR1_MeasReport | No | | | +| 62 | Supports performing eNB-configured SSB-based RRM measurements for EN-DC configured NR FR2 carrier(s) in RRC_IDLE and reporting them when requested by the eNB while resuming from RRC_IDLE or in RRC_CONNECTED, as specified in TS 36.331 [5]. | 36.306, 4.3.6.42 | Rel-16 | pc_nrIdleInactiveNR FR2_MeasReport | No | | | +| 63 | Support more than 1 per-UE measurement gap configurations. | 38.306, 4.2.9 | Rel-17 | pc_concurrentPerUE_OnlyMeasGap_r17 | No | | | +| 64 | Support all concurrent gap combination configurations as specified in TS 38.133 [5] including support of more than 1 per-UE measurement gap configurations. | 38.306, 4.2.9 | Rel-17 | pc_concurrentPerUE_PerFRCombMeasGap_r17 | No | | | +| 65 | Support the configurations of E-UTRAN measurement objectives associated with more than 1 concurrent measurement gaps. | 38.306, 4.2.9 | Rel-17 | pc_concurrentMeasGapEUTRA_r17 | No | | | + +| | | | | | | | | +|----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|--------|-------------------------------------------------|----|--|--| +| 66 | Support reporting of the NCSG and measurement gap requirement information for E-UTRA target bands in the UE response to a network configuration RRC message as specified in TS 38.331 [9]. | 38.306, 4.2.9 | Rel-17 | pc_eutra_NeedForGapNCSG_Reporting_r17 | No | | | +| 67 | Support two independent measurement gap configurations for FR1 and FR2 for PRS measurement. | 38.306, 4.2.9 | Rel-17 | pc_independentGapConfigPRS_r17 | No | | | +| 68 | Support NR-only NCSG patterns. | 38.306, 4.2.9 | Rel-17 | pc_ncsg_MeasGapNR_Patterns_r17 | No | | | +| 69 | Support NCSG patterns. | 38.306, 4.2.9 | Rel-17 | pc_ncsg_MeasGapPatterns_r17 | No | | | +| 70 | Support per-FR NCSG. | 38.306, 4.2.9 | Rel-17 | pc_ncsg_MeasGapPerFR_r17 | No | | | +| 71 | Support performing measurement with NCSG based on flag deriveSSB-IndexFromCell-inter and meeting the following requirements that the scheduling restriction in FR2 serving cell during NCSG ML is on SSB symbol level. | 38.306, 4.2.9 | Rel-17 | pc_ncsg_SymbolLevelScheduleRestrictionInter_r17 | No | | | +| 72 | Support reporting of the NCSG and measurement gap requirement information for SSB based measurement in the UE response to a network configuration RRC message. | 38.306, 4.2.9 | Rel-17 | pc_nr_NeedForGapNCSG_Reporting_r17 | No | | | +| 73 | Support the preconfigured measurement gap with UE-autonomous mechanism for activation and deactivation. | 38.306, 4.2.9 | Rel-17 | pc_preconfiguredUE_AutonomousMeasGap_r17 | No | | | +| 74 | Support the preconfigured measurement gap with network-controlled mechanism for activation and deactivation. | 38.306, 4.2.9 | Rel-17 | pc_preconfiguredNW_ControlledMeasGap_r17 | No | | | +| 75 | Support of SFTD measurements between the NR PCell and a configured E-UTRA PSCell | 38.306, 4.2.9 | Rel-15 | pc_SFTD_MeasPSCell_NEDC | No | | | + +| | | | | | | | | +|----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|--------|-----------------------------------------|----|--|---------------------------------------------------------------------------------------------------------------------------| +| 76 | Support of location-based triggered measurement reporting (i.e., event D1) as specified in TS 38.331 [9]. | 38.306, 4.2.9 | Rel-17 | pc_eventD1_MeasReportTrigger_r17 | CY | | If UE supports this feature then UE needs to support locationBasedCondHandover-r17 in any NTN band. | +| 77 | Support of Rel-17 relaxed RRM measurements of neighbour cells in RRC_IDLE/RRC_INACTIVE | 38.306, 5.6 | Rel-17 | pc_Relaxed_Measurement_r17 | No | | | +| 78 | Support of Rel-17 BFD relaxation criteria | 38.306, 4.2.7.2 | Rel-17 | pc_bfd-Relaxation_r17 | No | | | +| 79 | Support of Rel-17 RLM relaxation criteria | 38.306, 4.2.7.2 | Rel-17 | pc_rlm-Relaxation_r17 | No | | | +| 80 | Indicates the support of simultaneous transmission and reception in TDD-TDD and TDD-FDD inter-band NR CA. If this field is included in ca-ParametersNR-ForDC, it indicates the UE supports simultaneous transmission and reception between any UL/DL band pair within a cell group and across MCG and SCG in TDD-TDD and TDD-FDD inter-band NR-DC. | 38.306, 4.2.7 | Rel-17 | pc_simultaneous_RxTx_InterBandCA | No | | If the capability is supported then the band pair(s) for which it is supported shall be indicated in Table A.4.3.2A.4.1-3 | +| 81 | Indicates whether the UE can perform inter-frequency SSB based measurements without measurement gaps if the SSB is completely contained in the active BWP of the UE as specified in TS 38.133 [5]. If this parameter is indicated for FR1 and FR2 differently, each indication corresponds to the frequency range of cells to be measured. | 38.306, 4.2.9 | Rel-16 | pc_interFrequencyMeasurements_NoGap_r16 | No | | | +| 82 | Indicates whether the UE supports 2 parallel measurement gaps for NTN SSB based RRM measurements | 38.306, 4.2.9 | Rel-17 | pc_parallelMeasGap_r17 | No | | If a UE supports this feature, then it supports r17 NTN | + +#### A.4.3.7 General Capabilities + +**Table A.4.3.7-1: UE General Capabilities** + +| Item | UE General Capabilities | Ref. | Release | Mnemonic | M | If indicated "Yes" the feature shall be implemented and successfully tested for the corresponding release | Comments | +|------|---------------------------------------------------------------------------------------------------------|-------------------------------|---------|-------------------------------------|-----|-----------------------------------------------------------------------------------------------------------|-------------------------------------------------| +| 1 | Support UL transmission via either MCG path or SCG path for the split SRB as specified in TS 37.340[20] | 38.306, 4.2.2 | Rel-15 | pc_splitSRB_WithOneUL_Path | No | | | +| 2 | Support UL transmission via both MCG path and SCG path for the split DRB as specified in TS 37.340[20] | 38.306, 4.2.2 | Rel-15 | pc_splitDRB_withUL_Both_MCG_SCG | Yes | | | +| 3 | Support direct SRB between the SN and the UE as specified in TS 37.340[20] | 38.306, 4.2.2 | Rel-15 | pc_srb3 | Yes | | | +| 4 | Support of reflective QoS | 38.306, 4.2.2 | Rel-15 | pc_as_ReflectiveQoS | No | | | +| 5 | Support of NAS reflective QoS | 24.501, 6.2.5.1.4.1, 9.11.4.1 | Rel-15 | pc_nas_ReflectiveQoS | No | | | +| 6 | Support of SMS over NAS | 24.501, 5.5.1.2 | Rel-15 | pc_sms_over_NAS | No | | | +| 7 | Support of CMAS message on NR | 38.331, 5.2.2.2.2 | Rel-15 | pc_CMAS_NR | No | | | +| 8 | Support of ETWS message on NR | 38.331, 5.2.2.2.2 | Rel-15 | pc_ETWS_NR | No | | | +| 9 | The UE supports additional UE-requested PDU establishment | 24.501, 6.4.1.5 | Rel-15 | pc_Additional_PDU_establishment | No | | pc_ExpectedNumberOfPDUSessionsAtRegistration +1 | +| 10 | The UE includes the SM PDU DN request container IE in the PDU SESSION ESTABLISHMENT REQUEST message | 24.501, 6.4.1.2 | Rel-15 | pc_SM_PDU_DN_RequestContainer | No | | | +| 11 | Support of emergency services fallback in NR connected to 5GCN | 24.501 | Rel-15 | pc_NR_5GC_EmergencyService_fallback | No | | | +| 12 | Support of EPS fallback | 24.501, | Rel-15 | pc_EPS_fallback | No | | | +| 13 | Support of UE requested PDU session modification | 24.501, 6.4.2.2 | Rel-15 | pc_MO_PDU_Session_Modification | Yes | | | + +| | | | | | | | | +|----|--------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------|-----------------------------------------|-----|--|-------------------------------------------------------------------------------------------------------------| +| 14 | Support of emergency services in NR connected to 5GCN | 24.501 | Rel-15 | pc_NR_5GC_EmergencyServices | No | | | +| 15 | Support of voiceFallbackIndication | 38.306, 4.2.13 | Rel-16 | pc_voiceFallbackIndication | No | | | +| 16 | Support provision of referenceTimeInfo | 38.306, 4.2.2 | Rel-16 | pc_referenceTimeProvision_r16 | No | | specifically for TSC (time sensitive communication) services | +| 17 | Support of RACS | 24.501, 9.11.3.1 | Rel-16 | pc_5GC_RACS | No | | | +| 18 | Support of RRC message Segmentation in the UL | 38.306, 5.4 | Rel-16 | pc_NR_UL_Segmentation | No | | UE supports segmentation of UECapabilityInformation message, IF size > maximum supported size of a PDCP SDU | +| 19 | Support of RRC_INACTIVE as specified in TS 38.331 [9]. | 38.306, 4.2.2 | Rel-15 | pc_inactiveState | Yes | | | +| 20 | Support of UE local release when the security check is successful but SOR Transparent container indicates ACK has been NOT requested | 23.122 clause C.2 | Rel-15 | pc_SOR_ACKNotReqLocalRel | No | | | +| 21 | Support of RRC connection release with deprioritisation | 38.306, 5.3 | Rel-15 | pc_NR_RRC_Release_With_Deprioritisation | No | | | +| 22 | Support of RRC connection establishment failure with temporary offset | 38.306, 5.3 | Rel-15 | pc_NR_RRC_ConEstFail_With_TempOffset | No | | | +| 23 | Support of Closed Access Group | 24.501, 9.11.3.1 | Rel-16 | pc_CAG | No | | | +| 24 | Support of Stand-alone Non-Public Network | 23.501, 3.1 | Rel-16 | pc_SNPN | No | | | + +| | | | | | | | | +|----|---------------------------------------------------------------------------------------------------|------------------|--------|---------------------------------------|----|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 25 | Support of test function SET UL MESSAGE for using a preconfigured UE capability container over NR | 38.509, 5.9 | Rel-16 | pc_Set_UE_Cap_Info_NR | No | | This test function is mandatory for UEs supporting UL RRC segmentation and whose maximum UECapabilityInformation message size is less than the allowed maximum supported size of a PDCP SDU. | +| 26 | Support of network slice-specific authentication and authorization | 24.501, 9.11.3.1 | Rel-16 | pc_5GC_NSSAA | No | | | +| 27 | Support of EAP-AKA' as EAP method for network slice-specific authentication and authorization | 24.501, 5.4.7 | Rel-16 | pc_5GC_NSSAA_EAP_AKA_Prime | No | | | +| 28 | Support reduced control plane latency as defined in TS 38.331 [9] | 38.306, 4.2.2 | Rel-15 | pc_reducedCP_Latency | No | | | +| 29 | Support of release preference assistance information | 38.306, 4.2.2 | Rel-16 | pc_releasePreference_r16 | No | | | +| 30 | Support of user initiated SNPN reselection in automatic mode | 23.122 | Rel-16 | pc_UserInitiated_SNPN_Reselection | No | | | +| 31 | Support of autonomous search function to detect CAG cells on serving and non-serving frequencies | 38.304, 5.2.4.10 | Rel-16 | pc_Autonomous_search_function_n_r_CAG | No | | | +| 32 | Support IMS voice over NR | 38.306, 4.2.13 | Rel-15 | pc_voiceOverNR | No | | A UE supporting IMS voice over NR shall support: - IMS emergency call over NR, and - IMS voice over E-UTRA/EPC if it supports E-UTRA/EPC. | + +| | | | | | | | | +|----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|--------|---------------------------------------|----|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 33 | Support of V2X communication | 24.501,
9.11.3.1 | Rel-16 | pc_V2X | No | | UE support V2X communication over NR-Uu and/or NR-PC5. | +| 34 | Support of V2X communication over NR-PC5 | 24.501,
9.11.3.1 | Rel-16 | pc_V2XCNPC5 | No | | | +| 35 | Support of Manufacturer assigned Radio Capability ID | 23.501,
5.9.10 | Rel-16 | pc_5GC_RACS_Manufacturer_URCID | No | | UE support of Manufacturer assigned radio capability ID | +| 36 | Support of 3GPP PS data off | 24.501,
6.2.10 | Rel-15 | pc_PS_data_off | No | | UE support of 3GPP PS data off | +| 37 | Support of Network Slice Simultaneous Registration Group | 24.501,
9.11.3.82 | Rel-17 | pc_5GC_NSSRG | No | | | +| 38 | Support of slice reselection information in SIB and on RRC release for slice based cell reselection in RRC_IDLE and RRC_INACTIVE | 38.306,
4.2.2 | Rel-17 | pc_sliceInfoforCellReselection_r17 | No | | | +| 39 | Support of reception of segmented DL RRC messages | 38.306,
4.2.2 | Rel-16 | pc_NR_dl_DedicatedMessageSegmentation | No | | The SS initiates the DL Dedicated Message Segment transfer procedure IF the encoded RRCReconfiguration or RRCResume message PDU size > maximum PDCP SDU size. | +| 40 | Support of unified access control configuration in the list of subscriber data, indicating for which access identities (see 3GPP TS 24.501 [64]) the ME is configured, when the MS accesses an SNPN | 23.122,
4.9.3.0,
24.501
4.5.2A | Rel-16 | pc_SNPN_access_control_configuration | No | | | + +| | | | | | | | | +|----|------------------------------------------------------------------------------------|--------------------------------|--------|---------------------------------------|----|--|------------------------------------------------------------------------------------------------------------------| +| 41 | Support of polarization signalling in NR NTN | 38.306, 5.4 | Rel-17 | pc_Polarization_Signalling_NR_NTN | No | | UE supports polarization signalling in NR NTN | +| 42 | Supports receiving paging early indication and UE subgrouping indication with UEID | 38.306, 4.2.2 | Rel-17 | pc_pei_SubgroupingSupportBandList_r17 | No | | | +| 43 | Support of Rel-17 extended DRX cycle up to 10485.76 seconds | 38.306, 5.8
24.501, 5.3.16 | Rel-17 | pc_NR_eDRX | No | | | +| 44 | Support of (re-)configuration of an SCG during the resume procedure. | 38.306, 4.2.2 | Rel-16 | pc_resumeWithSCG_Config_r16 | No | | | +| 45 | Support of slice-based RACH prioritisation | 38.306, 5.4 | Rel-17 | pc_Slice_RACH_Prioritisation | No | | | +| 46 | Support of slice-based RACH partitioning | 38.306, 5.4 | Rel-17 | pc_Slice_RACH_Partitioning | No | | | +| 47 | Support of RACH prioritisation for Access Identity 1 | 38.306, 5.4 | Rel-17 | pc_Accl1_RACH_Prioritisation | No | | US supporting this shall also support MPS (Access ID 1) | +| 48 | Support of ATSSS and MA PDU session | 24.501, 6.4.1.2 | Rel-16 | pc_5GC_ATSSS | No | | | +| 49 | Support gNB-side RTT-based PDC | 38.306, 4.2.2 | Rel-17 | pc_gNB_SideRTT_BasedPDC_r17 | No | | A UE supporting this feature shall also support rtt-BasedPDC-CSI-RS-ForTracking-r17 and/or rtt-BasedPDC-PRS-r17. | +| 50 | Support of user plane integrity protection with EPS | 24.301, 5.5.1
33.401, 7.3.3 | Rel-17 | pc_EPS_UPIP | No | | A UE supporting this feature shall also support EN-DC | +| 51 | Support of UAS Services | 24.501, 3.1, 4.22 | Rel-17 | pc_UAS | No | | A UE supporting UAS services | + +| | | | | | | | | +|----|------------------------------------------------------------------------------------|--------------------------------|--------|----------------------------------|----|--|----------------------------------------------------------------------------------------------| +| 52 | Support of accessing SNPN using credentials from a Credentials Holder | 23.501
3.2,
5.30.2.9 | Rel-17 | pc_accessing_SN
PN_usingCH | No | | UE supports access using credentials assigned by a Credentials Holder separate from the SNPN | +| 53 | Support of Onboarding Stand-alone Non-Public Network | 23.501
5.30.2.10 | Rel-17 | pc_onboarding_S
NPN | No | | | +| 54 | Support of EAP-AKA' as EAP method for PDU session authentication and authorization | 24.501,
6.3.1 | Rel-15 | pc_5GC_PDU_EA
P_AKA_Prime | No | | | +| 55 | Support of relaxed cell reselection on GEO. | 38.306.
5.4 | Rel-17 | pc_relaxedCellRe
selectionGEO | No | | | +| 56 | Support of emergency services in NR connected to 5GCN in SNPN Access mode | 23.501,
5.16.4.1 | Rel-17 | pc_SNPN_Emerg
encyService | No | | | +| 57 | Support of PLMN access in SNPN Access mode | 23.122,
5.2.8 | Rel-17 | pc_SNPN_PLMN | No | | | +| 58 | Support of being configured for No E-UTRA Disabling In 5GS | 24.301,
4.5 | Rel-17 | pc_no_eutra_disa
ble_5GS | No | | | +| 59 | Support of MICO mode | 24.501,
5.3.6,
5.5.1.2.2 | Rel-15 | pc_MICO_Mode | No | | A UE supporting MICO mode | + +#### A.4.3.8 Mobility Capabilities + +**Table A.4.3.8-1: UE Mobility Capabilities** + +| Item | UE Mobility Capabilities | Ref. | Release | Mnemonic | M | If indicated "Yes" the feature shall be implemented and successfully tested for the corresponding release | Comments | +|------|----------------------------------------------------------------------------------------------------------------|-------------------|---------|----------------------------------|-----|-----------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------| +| 1 | Support inter-RAT Handover to EUTRA connected to EPC | 38.306, 4.2.9 | Rel-15 | pc_interRAT_EUTRA_Handover | Yes | | | +| 2 | Support inter-frequency Handover from the corresponding duplex mode or from the corresponding frequency range. | 38.306, 4.2.9 | Rel-15 | pc_handoverInterF | Yes | | | +| 3 | Support Handover between FR1 and FR2 | 38.306, 4.2.9 | Rel-15 | pc_FR1toFR2_Handover | Yes | | | +| 4 | Support Handover between FDD and TDD | 38.306, 4.2.9 | Rel-15 | pc_FDDtoTDD_Handover | Yes | | | +| 5 | Support inter-RAT Handover to E-UTRA connected to 5GC | 38.306, 4.2.9 | Rel-15 | pc_interRAT_eLTE_Handover | Yes | | | +| 6 | Support inter-RAT Handover to NR FR1 TDD from EUTRA connected to EPC | 36.306, 4.3.34.9 | Rel-15 | pc_eutra_EPC_HO_ToNR_TDD_FR1_r15 | Yes | | | +| 7 | Support inter-RAT Handover to NR FR1 FDD from EUTRA connected to EPC | 36.306, 4.3.34.8 | Rel-15 | pc_eutra_EPC_HO_ToNR_FDD_FR1_r15 | Yes | | | +| 8 | Support inter-RAT Handover to NR FR2 TDD from EUTRA connected to EPC | 36.306, 4.3.34.11 | Rel-15 | pc_eutra_EPC_HO_ToNR_TDD_FR2_r15 | Yes | | | +| 9 | Support intra-frequency DAPS handover | 38.306, 4.2.7.5 | Rel-16 | pc_intraFreqDAPS_r16 | No | | It is mandated if the UE supports asynchronous intra-frequency DAPS handover | +| 10 | Support inter-RAT Handover from NR to EN-DC | 38.306, 4.2.10 | Rel-16 | pc_interRAT_NR_ToENDC | CY | | It is mandated if the UE supports EN-DC. | +| 11 | Support conditional handover | 38.306, 4.2.7.2 | Rel-16 | pc_condHandover_r16 | No | | | + +| | | | | | | | | +|----|----------------------------------------------------------------------------------------------------------------------------------------------|------------------|--------|-------------------------------------|----|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 12 | Support conditional handover during re-establishment procedure when the selected cell is configured as candidate cell for condition handover | 38.306, 4.2.7.2 | Rel-16 | pc_condHandoverFailure_r16 | No | | | +| 13 | Support 2 trigger events for same execution condition of conditional handover | 38.306, 4.2.7.2 | Rel-16 | pc_condHandoverTwoTriggerEvents_r16 | CY | | It is mandated if the UE supports condHandover-r16 . | +| 14 | Support inter-RAT Handover from NR to UTRA-FDD CELL_DCH CS | 38.306, 4.2.9 | Rel-16 | pc_handoverUTRA_FDD_r16 | No | | | +| 15 | Support inter-frequency DAPS handover | 38.306, 4.2.7.4 | Rel-16 | pc_interFreqDAPS_r16 | No | | It is mandated if the UE supports asynchronous inter-frequency DAPS handover or supports different SCSs in source PCell and inter-frequency target PCell in DAPS handover | +| 16 | UE supports asynchronous intra-frequency DAPS handover | 38.306, 4.2.7.5 | Rel-16 | pc_intraFreqAsyncDAPS_r16 | No | | | +| 17 | UE supports asynchronous inter-frequency DAPS handover | 38.306, 4.2.7.5 | Rel-16 | pc_interFreqAsyncDAPS_r16 | No | | | +| 18 | UE supports different SCSs in source PCell and inter-frequency target PCell in DAPS handover | 38.306, 4.2.7.5 | Rel-16 | pc_inteFreqDiffSCS_DAPS_r16 | No | | | +| 19 | Support conditional PSCell change | 38.306, 4.2.7.2 | Rel-16 | pc_condPSCellChange_r16 | No | | | +| 20 | Support handover from 5GS to EPC/ePDG | 24.302, 7.2.2.1 | Rel-15 | pc_HO_from_5GS_to_EPC_ePDG | No | | | +| 21 | Support handover from EPC/ePDG to 5GS | 23.502, 4.11.4.1 | Rel-15 | pc_HO_from_EPC_ePDG_to_5GS | No | | | +| 22 | Support Handover from EPS to 5GC-N3IWF | 23.502, 4.11.3.1 | Rel-15 | pc_HO_from_EPS_to_5GC_N3IWF | No | | | + +| | | | | | | | | +|----|------------------------------------------------------------------------------------|---------------------|--------|-----------------------------------------|----|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 23 | Support Handover from 5GC-N3IWF to EPS | 23.502,
4.11.3.2 | Rel-15 | pc_HO_from_5GC_N3IWF_to_EPS | No | | | +| 24 | Support Handover of a PDU Session procedure from untrusted non-3GPP to 3GPP access | 23.502,
4.9.2.1 | Rel-15 | pc_HO_from_5GC_N3IWF_to_5GC | No | | | +| 25 | Support Handover of a PDU Session procedure from 3GPP to untrusted non-3GPP access | 23.502,
4.9.2.2 | Rel-15 | pc_HO_from_5GC_to_5GC_N3IWF | No | | | +| 26 | Supports location based conditional handover, i.e., CondEvent D1 | 38.306,
4.2.7.2 | Rel-17 | pc_locationBasedConditionalHandover_r17 | No | | A UE supporting this feature shall also indicate the support of condHandover-r16 for NTN bands and the support of nonTerrestrialNetwork-r17. UE shall set the capability value consistently for all FDD-FR1 NTN bands. | +| 27 | Support time based conditional handover, i.e., CondEvent T1 | 38.306,
4.2.7.2 | Rel-17 | pc_timeBasedConditionalHandover_r17 | No | | A UE supporting this feature shall also indicate the support of condHandover-r16 for NTN bands and the support of nonTerrestrialNetwork-r17. UE shall set the capability value consistently for all FDD-FR1 NTN bands. | + +#### A.4.3.9 Additional capabilities for UE declared capability + +**Table A.4.3.9-1: UE declared capabilities** + +| Item | UE declared capabilities | Ref. | Release | Mnemonic | Comments | +|------|----------------------------------------------------------------------------------|-------------|---------|--------------------------|------------------------------------------------------------------------------------------------------| +| 1 | Enhanced Type 1 Receiver for NR | 38.101-4, 5 | Rel-15 | pc_nr_enh_type1_receiver | Support for Enhanced Type 1 Receiver (SU-MIMO Interference Mitigation advanced receiver) | +| 2 | Vehicular UE | 38.101-1, 3 | Rel-15 | pc_nr_vehicular_ue | | +| 3 | MMSE-IRC (Minimum Mean Square Error - Interference Rejection Combining) receiver | 38.101-4, 5 | Rel-15 | pc_nr_mmse_irc_receiver | Support of MMSE-IRC processing for scenarios with inter-cell and intra-cell inter-user interference. | + +**Table A.4.3.9-2: UE declared multi-band peak EIRP relaxation factors for Rel-15 FR2 power class 3 UE** + +| Item | Supported FR2 bands set | Ref. | Release | peak EIRP relaxation factor per band, MB p (dB) (Note 1) | peak EIRP relaxation factor per band, MB p (dB) (Note 1) | peak EIRP relaxation factor per band, MB p (dB) (Note 1) | peak EIRP relaxation factor per band, MB p (dB) (Note 1) | Maximum sum of MB p , ΣMB p (dB) (Note 2) | Comments | +|------|-------------------------|-------------------|---------|---------------------------------------------------------------------|---------------------------------------------------------------------|---------------------------------------------------------------------|---------------------------------------------------------------------|-----------------------------------------------------------------|------------------------------| +| | | | | n257 | n258 | n260 | n261 | | | +| 1 | n257, n258 | 38.101-2, 6.2.1.3 | Rel-15 | | | N/A | N/A | 1.3 | | +| 2 | n257, n260 | 38.101-2, 6.2.1.3 | Rel-15 | | N/A | | N/A | 1.0 | | +| 3 | n258, n260 | 38.101-2, 6.2.1.3 | Rel-15 | N/A | | | N/A | 1.0 | | +| 4 | n258, n261 | 38.101-2, 6.2.1.3 | Rel-15 | N/A | | N/A | | 1.0 | | +| 5 | n260, n261 | 38.101-2, 6.2.1.3 | Rel-15 | N/A | N/A | | | 0.0 | No relaxation factor allowed | +| 6 | n257, n258, n260 | 38.101-2, 6.2.1.3 | Rel-15 | | | | N/A | 1.7 | | +| 7 | n257, n258, n261 | 38.101-2, 6.2.1.3 | Rel-15 | | | N/A | | 1.7 | | +| 8 | n257, n260, n261 | 38.101-2, 6.2.1.3 | Rel-15 | | N/A | | | 0.5 | | +| 9 | n258, n260, n261 | 38.101-2, 6.2.1.3 | Rel-15 | N/A | | | | 1.5 | | +| 10 | n257, n258, n260, n261 | 38.101-2, 6.2.1.3 | Rel-15 | | | | | 1.7 | | +| 11 | n257, n261 | 38.101-2, 6.2.1.3 | Rel-15 | | N/A | N/A | | 0.0 | No relaxation factor allowed | + +Note 1: UE vendor to fill in the needed relaxation factor per band that is ≥0 for Rel-15 UE supporting only Rel-15 FR2 bands. One row to be filled in, the one matching the supported FR2 bands of the UE as declared in Table A.4.3.1-3. + +Note 2: Max allowed sum of MBp over all supported FR2 bands as defined in TS 38.521-2 clause 6.2.1.1.3.3 + +**Table A.4.3.9-3: UE declared multi-band peak EIRP Spherical coverage relaxation factors for Rel-15 FR2 power class 3 UE** + +| Item | Supported FR2 bands set | Ref. | Release | EIRP Spherical coverage relaxation factor per band, MB s (dB) (Note 1) | EIRP Spherical coverage relaxation factor per band, MB s (dB) (Note 1) | EIRP Spherical coverage relaxation factor per band, MB s (dB) (Note 1) | EIRP Spherical coverage relaxation factor per band, MB s (dB) (Note 1) | Maximum sum of MB s , $\sum$ MB s (dB) (Note 2) | Comments | +|------|-------------------------|-------------------|---------|-----------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|-----------------------------------------------------------------------|--------------------------------------------| +| | | | | n257 | n258 | n260 | n261 | | | +| 1 | n257, n258 | 38.101-2, 6.2.1.3 | Rel-15 | | | N/A | N/A | 1.25 | | +| 2 | n257, n260 | 38.101-2, 6.2.1.3 | Rel-15 | | N/A | | N/A | 0.75 | Maximum 0.4 dB relaxation allowed for n260 | +| 3 | n258, n260 | 38.101-2, 6.2.1.3 | Rel-15 | N/A | | | N/A | 0.75 | Maximum 0.4 dB relaxation allowed for n260 | +| 4 | n258, n261 | 38.101-2, 6.2.1.3 | Rel-15 | N/A | | N/A | | 1.25 | | +| 5 | n260, n261 | 38.101-2, 6.2.1.3 | Rel-15 | N/A | N/A | | | 0.75 | No relaxation allowed for n260 | +| 6 | n257, n258, n260 | 38.101-2, 6.2.1.3 | Rel-15 | | | | N/A | 1.75 | Maximum 0.4 dB relaxation allowed for n260 | +| 7 | n257, n258, n261 | 38.101-2, 6.2.1.3 | Rel-15 | | | N/A | | 1.75 | | +| 8 | n257, n260, n261 | 38.101-2, 6.2.1.3 | Rel-15 | | N/A | | | 1.25 | Maximum 0.4 dB relaxation allowed for n260 | +| 9 | n258, n260, n261 | 38.101-2, 6.2.1.3 | Rel-15 | N/A | | | | 1.25 | Maximum 0.4 dB relaxation allowed for n260 | +| 10 | n257, n258, n260, n261 | 38.101-2, 6.2.1.3 | Rel-15 | | | | | 1.75 | Maximum 0.4 dB relaxation allowed for n260 | +| 11 | n257, n261 | 38.101-2, 6.2.1.3 | Rel-15 | | N/A | N/A | | 0.0 | No relaxation factor allowed | + +| | | +|---------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Note 1: | UE vendor to fill in the needed relaxation factor per band that is $\geq 0$ for Rel-15 UE supporting only Rel-15 FR2 bands. One row to be filled in, the one matching the supported FR2 bands of the UE as declared in Table A.4.3.1-3 | +| Note 2: | Max allowed sum of MBs over all supported FR2 bands as defined in TS 38.521-2 clause 6.2.1.1.3.3 | + +**Table A.4.3.9-4a: FDD 4 Rx antenna ports Capabilities** + +| Item | Band | Ref. | Release | Comments | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-----------------|---------|------------------------------------------------| +| 1 | FDD Band n1 | 38.101-1, 7.3.2 | Rel-15 | | +| 2 | FDD Band n2 | 38.101-1, 7.3.2 | Rel-15 | | +| 3 | FDD Band n3 | 38.101-1, 7.3.2 | Rel-15 | | +| ... | | | | | +| 7 | FDD Band n7 | 38.101-1, 7.3.2 | Rel-15 | NOTE 2 | +| 8 | FDD Band n8 | 38.101-1.7.3.2 | Rel-17 | 4 Rx operation is targeted for FWA form factor | +| ... | | | | | +| 28 | FDD Band n28 | 38.101-1, 7.3.2 | Rel-16 | 4 Rx operation is targeted for FWA form factor | +| ... | | | | | +| 30 | FDD Band n30 | 38.101-1, 7.3.2 | Rel-16 | | +| ... | | | | | +| 66 | FDD Band n66 | 38.101-1, 7.3.2 | Rel-15 | | +| ... | | | | | +| 70 | FDD Band n70 | 38.101-1, 7.3.2 | Rel-15 | | +| 71 | FDD Band n71 | 38.101-1, 7.3.2 | Rel-16 | 4 Rx operation is targeted for FWA form factor | +| NOTE 1: At least one band from those listed in the present table needs to be supported if UE has indicated support of the capability defined in Table A.4.3.1-7a/2. | | | | | +| NOTE 2: Support of 4 Rx for this band is mandatory for non-vehicular UEs i.e. if support has NOT been indicated to the capability specified in Table A.4.3.9-1/2. | | | | | + +**Table A.4.3.9-4b: TDD 4 Rx antenna ports Capabilities** + +| Item | Band | Ref. | Release | Comments | +|------|--------------|-----------------|---------|----------| +| 34 | TDD Band n34 | 38.101-1, 7.3.2 | Rel-15 | | +| ... | | | | | +| 38 | TDD Band n38 | 38.101-1, 7.3.2 | Rel-15 | NOTE 2 | +| 39 | TDD Band n39 | 38.101-1, 7.3.2 | Rel-15 | | +| ... | | | | | +| 40 | TDD Band n40 | 38.101-1, 7.3.2 | Rel-15 | | +| 41 | TDD Band n41 | 38.101-1, 7.3.2 | Rel-15 | NOTE 2 | +| ... | | | | | +| 48 | TDD Band n48 | 38.101-1, 7.3.2 | Rel-16 | NOTE 2 | +| ... | | | | | +| 77 | TDD Band n77 | 38.101-1, 7.3.2 | Rel-15 | NOTE 2 | +| 78 | TDD Band n78 | 38.101-1, 7.3.2 | Rel-15 | NOTE 2 | +| 79 | TDD Band n79 | 38.101-1, 7.3.2 | Rel-15 | NOTE 2 | + +NOTE 1: At least one band from those listed in the present table needs to be supported if UE has indicated support of the capability defined in Table A.4.3.1-7a/3. + +NOTE 2: Support of 4 Rx for this band is mandatory for non-vehicular UEs i.e. if support has NOT been indicated to the capability specified in Table A.4.3.9-1/2. + +###### **Table A.4.3.9-4c: 2 Rx antenna ports Capabilities** + +| Item | Band | Ref. | Comments | +|------|--------------|-----------------|----------| +| 1 | FDD Band n1 | 38.101-1, 7.3.2 | | +| 2 | FDD Band n2 | 38.101-1, 7.3.2 | | +| 3 | FDD Band n3 | 38.101-1, 7.3.2 | | +| 4 | FDD Band n5 | 38.101-1, 7.3.2 | | +| 5 | FDD Band n7 | 38.101-1, 7.3.2 | NOTE 2 | +| 6 | FDD Band n8 | 38.101-1, 7.3.2 | | +| 7 | FDD Band n12 | 38.101-1, 7.3.2 | | +| 7b | FDD Band n14 | 38.101-1, 7.3.2 | | +| 8 | FDD Band n20 | 38.101-1, 7.3.2 | | +| 8d | FDD Band n24 | 38.101-1, 7.3.2 | | +| 9 | FDD Band n25 | 38.101-1, 7.3.2 | | +| 9a | FDD Band n26 | 38.101-1, 7.3.2 | | +| 10 | FDD Band n28 | 38.101-1, 7.3.2 | | +| 10a | SDL Band n29 | 38.101-1, 7.3.2 | | +| 10b | FDD Band n30 | 38.101-1, 7.3.2 | | +| 11 | TDD Band n34 | 38.101-1, 7.3.2 | | +| 12 | TDD Band n38 | 38.101-1, 7.3.2 | NOTE 2 | +| 13 | TDD Band n39 | 38.101-1, 7.3.2 | | +| 14 | TDD Band n40 | 38.101-1, 7.3.2 | | +| 15 | TDD Band n41 | 38.101-1, 7.3.2 | NOTE 2 | +| 16 | TDD Band n48 | 38.101-1, 7.3.2 | | +| 17 | TDD Band n50 | 38.101-1, 7.3.2 | | +| 18 | TDD Band n51 | 38.101-1, 7.3.2 | | +| 18a | Reserved | | | +| 18b | TDD Band n53 | 38.101-1, 7.3.2 | | +| 19 | FDD Band n65 | 38.101-1, 7.3.2 | | +| 20 | FDD Band n66 | 38.101-1, 7.3.2 | | +| 21 | FDD Band n70 | 38.101-1, 7.3.2 | | +| 22 | FDD Band n71 | 38.101-1, 7.3.2 | | +| 23 | FDD Band n74 | 38.101-1, 7.3.2 | | +| 24 | TDD Band n77 | 38.101-1, 7.3.2 | NOTE 2 | +| 25 | TDD Band n78 | 38.101-1, 7.3.2 | NOTE 2 | +| 26 | TDD Band n79 | 38.101-1, 7.3.2 | NOTE 2 | +| 27 | FDD Band n91 | 38.101-1, 7.3.2 | | +| 28 | FDD Band n92 | 38.101-1, 7.3.2 | | +| 29 | FDD Band n93 | 38.101-1, 7.3.2 | | + +| | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|-----------------|--| +| 30 | FDD Band n94 | 38.101-1, 7.3.2 | | +| 31 | FDD Band n100 | 38.101-1, 7.3.2 | | +| 32 | TDD Band n101 | 38.101-1, 7.3.2 | | +|

NOTE 1: At least one band from those listed in the present table needs to be supported if UE has indicated support of the capability defined in Table A.4.3.1-7a/1.

NOTE 2: Support of 2 Rx for this band is allowed only for vehicular UEs i.e. if support has been indicated to the capability specified in Table A.4.3.9-1/2.

| | | | + +###### **Table A.4.3.9-4d: Enhanced transient capabilities** + +| Item | Band | Ref | Release | enhanced | enhanced | enhanced | Comments | +|------|--------------|--------------------|---------|-------------------------------------|-------------------------------------|-------------------------------------|----------| +| | | | | transient
capability
per band | transient
capability
per band | transient
capability
per band | | +| | | | | 2us | 4us | 7us | | +| 1 | FDD Band n1 | 38.101-1, 6.4.2.1a | Rel-16 | | | | | +| 2 | FDD Band n2 | 38.101-1, 6.4.2.1a | Rel-16 | | | | | +| 3 | FDD Band n3 | 38.101-1, 6.4.2.1a | Rel-16 | | | | | +| 4 | FDD Band n5 | 38.101-1, 6.4.2.1a | Rel-16 | | | | | +| 5 | FDD Band n7 | 38.101-1, 6.4.2.1a | Rel-16 | | | | | +| 6 | FDD Band n8 | 38.101-1, 6.4.2.1a | Rel-16 | | | | | +| 7 | FDD Band n12 | 38.101-1, 6.4.2.1a | Rel-16 | | | | | +| 8 | FDD Band n14 | 38.101-1, 6.4.2.1a | Rel-16 | | | | | +| 9 | FDD Band n20 | 38.101-1, 6.4.2.1a | Rel-16 | | | | | +| 10 | FDD Band n24 | 38.101-1, 6.4.2.1a | Rel-16 | | | | | +| 11 | FDD Band n25 | 38.101-1, 6.4.2.1a | Rel-16 | | | | | +| 12 | FDD Band n26 | 38.101-1, 6.4.2.1a | Rel-16 | | | | | +| 13 | FDD Band n28 | 38.101-1, 6.4.2.1a | Rel-16 | | | | | +| 14 | FDD Band n30 | 38.101-1, 6.4.2.1a | Rel-16 | | | | | +| 15 | TDD Band n34 | 38.101-1, 6.4.2.1a | Rel-16 | | | | | +| 16 | TDD Band n38 | 38.101-1, 6.4.2.1a | Rel-16 | | | | | +| 17 | TDD Band n39 | 38.101-1, 6.4.2.1a | Rel-16 | | | | | +| 18 | TDD Band n40 | 38.101-1, 6.4.2.1a | Rel-16 | | | | | +| 19 | TDD Band n41 | 38.101-1, 6.4.2.1a | Rel-16 | | | | | +| 20 | TDD Band n46 | 38.101-1, 6.4.2.1a | Rel-16 | | | | | +| 21 | TDD Band n48 | 38.101-1, 6.4.2.1a | Rel-16 | | | | | +| 22 | TDD Band n50 | 38.101-1, 6.4.2.1a | Rel-16 | | | | | +| 23 | TDD Band n51 | 38.101-1, 6.4.2.1a | Rel-16 | | | | | +| 24 | TDD Band n53 | 38.101-1, 6.4.2.1a | Rel-16 | | | | | +| 25 | FDD Band n65 | 38.101-1, 6.4.2.1a | Rel-16 | | | | | +| 26 | FDD Band n66 | 38.101-1, 6.4.2.1a | Rel-16 | | | | | +| 27 | FDD Band n70 | 38.101-1, 6.4.2.1a | Rel-16 | | | | | +| 28 | FDD Band n71 | 38.101-1, 6.4.2.1a | Rel-16 | | | | | +| 29 | FDD Band n74 | 38.101-1, 6.4.2.1a | Rel-16 | | | | | +| 30 | TDD Band n77 | 38.101-1, 6.4.2.1a | Rel-16 | | | | | +| 31 | TDD Band n78 | 38.101-1, 6.4.2.1a | Rel-16 | | | | | +| 32 | TDD Band n79 | 38.101-1, 6.4.2.1a | Rel-16 | | | | | +| 33 | TDD Band n96 | 38.101-1, 6.4.2.1a | Rel-16 | | | | | + +NOTE 1: At least one band from those listed in the present table needs to be supported with enhanced transient capability of 2us, 4us or 7us if UE has indicated support of the capability defined in Table A.4.3.2-1/79. + +NOTE 2: Indicate transient capability for each band by ticking the cell corresponding to the smallest enhanced transient capability that the UE supports for that band. + +**Table A.4.3.9-4e: 1 Rx antenna ports Capabilities** + +| Item | Band | Ref. | Comments | +|------|---------------|------------------|----------| +| 1 | FDD Band n1 | 38.101-1, 7.31.2 | | +| 2 | FDD Band n2 | 38.101-1, 7.31.2 | | +| 3 | FDD Band n3 | 38.101-1, 7.31.2 | | +| 4 | FDD Band n5 | 38.101-1, 7.31.2 | | +| 5 | FDD Band n8 | 38.101-1, 7.31.2 | | +| 6 | FDD Band n12 | 38.101-1, 7.31.2 | | +| 7 | FDD Band n13 | 38.101-1, 7.31.2 | | +| 8 | FDD Band n14 | 38.101-1, 7.31.2 | | +| 9 | FDD Band n18 | 38.101-1, 7.31.2 | | +| 10 | FDD Band n20 | 38.101-1, 7.31.2 | | +| 11 | FDD Band n24 | 38.101-1, 7.31.2 | | +| 12 | FDD Band n25 | 38.101-1, 7.31.2 | | +| 13 | FDD Band n26 | 38.101-1, 7.31.2 | | +| 14 | FDD Band n28 | 38.101-1, 7.31.2 | | +| 15 | FDD Band n30 | 38.101-1, 7.31.2 | | +| 16 | TDD Band n34 | 38.101-1, 7.31.2 | | +| 17 | TDD Band n39 | 38.101-1, 7.31.2 | | +| 18 | TDD Band n40 | 38.101-1, 7.31.2 | | +| 19 | TDD Band n50 | 38.101-1, 7.31.2 | | +| 20 | TDD Band n51 | 38.101-1, 7.31.2 | | +| 21 | TDD Band n53 | 38.101-1, 7.31.2 | | +| 22 | FDD Band n65 | 38.101-1, 7.31.2 | | +| 23 | FDD Band n66 | 38.101-1, 7.31.2 | | +| 24 | FDD Band n70 | 38.101-1, 7.31.2 | | +| 25 | FDD Band n71 | 38.101-1, 7.31.2 | | +| 26 | FDD Band n74 | 38.101-1, 7.31.2 | | +| 27 | FDD Band n85 | 38.101-1, 7.31.2 | | +| 28 | FDD Band n91 | 38.101-1, 7.31.2 | | +| 29 | FDD Band n92 | 38.101-1, 7.31.2 | | +| 30 | FDD Band n93 | 38.101-1, 7.31.2 | | +| 31 | FDD Band n94 | 38.101-1, 7.31.2 | | +| 32 | FDD Band n100 | 38.101-1, 7.31.2 | NOTE 2 | +| 33 | TDD Band n101 | 38.101-1, 7.31.2 | | +| 34 | TDD Band n104 | 38.101-1, 7.31.2 | | + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOTE 1: At least one band from those listed in the present table needs to be supported if UE has indicated support of the capability defined in Table A.4.3.1-7a/1.
NOTE 2: HD-FDD is not supported. | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table A.4.3.9-5: Beam Peak Search Vendor Declarations with respect to test frequency range for single CC** + +| Item | Band | Intent | Ref. | Release | Comments | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----------------------------------------------------------------------------------------------------------|-------------------------|---------|----------| +| 1 | n257 | n257 single CC beam peak is leveraged from mid to low and high channels | 38.521-2, K.1.1 & K.1.2 | Rel-15 | NOTE 1 | +| 2 | n258 | n258 single CC beam peak is leveraged from mid to low and high channels | 38.521-2, K.1.1 & K.1.2 | Rel-15 | NOTE 1. | +| 3 | n260 | n260 single CC beam peak is leveraged from mid to low and high channels | 38.521-2, K.1.1 & K.1.2 | Rel-15 | NOTE 1 | +| 4 | n261 | n261 single CC beam peak is leveraged from mid to low and high channels | 38.521-2, K.1.1 & K.1.2 | Rel-15 | NOTE 1 | +| 5 | n261 | n261 single CC beam peak is leveraged from n257 single CC mid channel to n261 low, mid and high channels | 38.521-2, K.1.1 & K.1.2 | Rel-15 | NOTE 2 | +| NOTE 1: The beam peak searches shall be performed for every test frequency range by default unless the device manufacturer explicitly declares that the beam peak at the mid test frequency range is applicable for the remaining (low, high) test frequency ranges. | | | | | | +| NOTE 2: Beam peak search results can be re-used from bands that completely contain the target bands if explicitly declared by the manufacturer. | | | | | | + +**Table A.4.3.9-6: Beam Peak Search Vendor Declarations with respect to test frequency range for different CA BW classes** + +| Item | Bands | NR CA bandwidth class | Intent | Ref. | Release | Comments | +|------|------------------------|------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|---------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | n257, n258, n260, n261 | A, B, C, D, E, F, G, H, I, J, K, L, M, O, P, Q | The beam peak is leveraged from a reference (frequency band, CBW) or (frequency band combination, CA BW class) to a group of other intra-band contiguous combinations and CA BW classes | 38.521-2, K.1.1 & K.1.2 | Rel-15 | A beam peak search shall be performed for every intra-band contiguous combination and CA BW class by default unless the device manufacturer explicitly declares that the beam peak for a reference (frequency band, CBW) or (frequency band combination, CA BW class) is applicable for a group of other intra-band contiguous combinations and CA BW classes. | + +**Table A.4.3.9-7: Beam Peak Search Vendor Declarations with respect to modulation for single CC** + +| Item | Band | Intent | Ref. | Release | Comments | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-------------------------------------------------------------------------------|-------------------------|---------|----------| +| 1 | n257 | n257 single CC beam peak is leveraged from QPSK modulation to 16QAM and 64QAM | 38.521-2, K.1.1 & K.1.2 | Rel-15 | NOTE 1 | +| 2 | n258 | n258 single CC beam peak is leveraged from QPSK modulation to 16QAM and 64QAM | 38.521-2, K.1.1 & K.1.2 | Rel-15 | NOTE 1 | +| 3 | n260 | n260 single CC beam peak is leveraged from QPSK modulation to 16QAM and 64QAM | 38.521-2, K.1.1 & K.1.2 | Rel-15 | NOTE 1 | +| 4 | n261 | n261 single CC beam peak is leveraged from QPSK modulation to 16QAM and 64QAM | 38.521-2, K.1.1 & K.1.2 | Rel-15 | NOTE 1 | +| NOTE 1: The beam peak searches shall be performed for every modulation by default unless the device manufacturer explicitly declares that the beam peak at the QPSK modulation is applicable for the remaining 16QAM and 64QAM modulations. | | | | | | + +**Table A.4.3.9-8: Beam Peak Search Vendor Declarations with respect to waveform for single CC** + +| Item | Band | Intent | Reference Waveform | Ref. | Release | Comments | +|------|------|-----------------------------------------------------------------------------------------|-----------------------|-----------------|---------|----------| +| 1 | n257 | n257 single CC beam peak is leveraged from the reference waveform to the other waveform | CP-OFDM or DFT-s-OFDM | 38.521-2, K.1.1 | Rel-15 | NOTE 1 | +| 2 | n258 | n258 single CC beam peak is leveraged from the reference waveform to the other waveform | CP-OFDM or DFT-s-OFDM | 38.521-2, K.1.1 | Rel-15 | NOTE 1 | +| 3 | n260 | n260 single CC beam peak is leveraged from the reference waveform to the other waveform | CP-OFDM or DFT-s-OFDM | 38.521-2, K.1.1 | Rel-15 | NOTE 1 | +| 4 | n261 | n261 single CC beam peak is leveraged from the reference waveform to the other waveform | CP-OFDM or DFT-s-OFDM | 38.521-2, K.1.1 | Rel-15 | NOTE 1 | + +NOTE 1: The beam peak searches shall be performed for every waveform by default unless the device manufacturer explicitly declares that the beam peak from one waveform is applicable for the other waveform. + +**Table A.4.3.9-9: Reference Point Vendor Declaration for grey-box test approach** + +| Item | Band | Positioning Reference Point: Offset (x/y/z) from geometric centre of DUT [cm] | Minimum QZ required to contain all active antennas within the quiet zone | Ref. | Release | +|-----------------------------------------------------------------------------------------------------------|------|-------------------------------------------------------------------------------|--------------------------------------------------------------------------|----------------------|---------| +| 1 | n257 | | | 38.508-1,
B.2.2.2 | Rel-15 | +| 2 | n258 | | | 38.508-1,
B.2.2.2 | Rel-15 | +| 3 | n260 | | | 38.508-1,
B.2.2.2 | Rel-15 | +| 4 | n261 | | | 38.508-1,
B.2.2.2 | Rel-15 | +| NOTE: The available QZ sizes are defined in TS 38.508-1, Clause B.2.2.2, i.e., 20cm, 30cm, 40cm, and 55cm | | | | | | + +**Table A.4.3.9-10: Vendor Declarations with respect to PC3 antenna configuration** + +| Item | Band | Intent | Ref. | Release | Comments | +|------|------|-----------------------------------------------------------------------------------------------|---------------------|---------|----------| +| 1a | n257 | n257 PC3 measurement grids can be relaxed based on 4x2 worst case antenna array configuration | 38.521-2, M.2 – M.4 | Rel-15 | NOTE 1 | +| 2a | n258 | n258 PC3 measurement grids can be relaxed based on 4x2 worst case antenna array configuration | 38.521-2, M.2 – M.4 | Rel-15 | NOTE 1 | +| 3a | n259 | n259 PC3 measurement grids can be relaxed based on 4x2 worst case antenna array configuration | 38.521-2, M.2 – M.4 | Rel-16 | NOTE 1 | +| 4a | n260 | n260 PC3 measurement grids can be relaxed based on 4x2 worst case antenna array configuration | 38.521-2, M.2 – M.4 | Rel-15 | NOTE 1 | +| 5a | n261 | n261 PC3 measurement grids can be relaxed based on 4x2 worst case antenna array configuration | 38.521-2, M.2 – M.4 | Rel-15 | NOTE 1 | +| 1b | n257 | n257 PC3 measurement grids can be relaxed based on 6x2 worst case antenna array configuration | 38.521-2, M.2 – M.4 | Rel-15 | NOTE 2 | + +| | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----------------------------------------------------------------------------------------------|---------------------|--------|--------| +| 2b | n258 | n258 PC3 measurement grids can be relaxed based on 6x2 worst case antenna array configuration | 38.521-2, M.2 – M.4 | Rel-15 | NOTE 2 | +| 3b | n259 | n259 PC3 measurement grids can be relaxed based on 6x2 worst case antenna array configuration | 38.521-2, M.2 – M.4 | Rel-16 | NOTE 2 | +| 4b | n260 | n260 PC3 measurement grids can be relaxed based on 6x2 worst case antenna array configuration | 38.521-2, M.2 – M.4 | Rel-15 | NOTE 2 | +| 5b | n261 | n261 PC3 measurement grids can be relaxed based on 6x2 worst case antenna array configuration | 38.521-2, M.2 – M.4 | Rel-15 | NOTE 2 | +| NOTE 1: The fine PC3 measurement grids based on the 8x2 worst case configuration shall be applied by default unless the device manufacturer explicitly declares that all antenna arrays with $M \times N$ ( $M \geq N$ ) comply with $M \leq 4$ and $N \leq 2$ for each band. | | | | | | +| NOTE 2: The fine PC3 measurement grids based on the 8x2 worst case configuration shall be applied by default unless the device manufacturer explicitly declares that all antenna arrays with $M \times N$ ( $M \geq N$ ) comply with $4 < M \leq 6$ and $N \leq 2$ for each band. | | | | | | + +**Table A.4.3.9-10a: Vendor Declarations with respect to PC5 antenna configuration** + +| Item | Band | Intent | Ref. | Release | Comments | +|------|------|-----------------------------------------------------------------------------------------------|---------------------|---------|----------| +| 1 | n257 | n257 PC5 measurement grids can be relaxed based on 6x6 worst case antenna array configuration | 38.521-2, M.2 – M.4 | Rel-15 | NOTE 1 | +| 2 | n258 | n258 PC5 measurement grids can be relaxed based on 6x6 worst case antenna array configuration | 38.521-2, M.2 – M.4 | Rel-15 | NOTE 1 | + +NOTE 1: The fine PC5 measurement grids based on the 12x12 worst case configuration shall be applied by default unless the device manufacturer explicitly declares that all antenna arrays with $M \times N$ ( $M \geq N$ ) comply with $M \leq 6$ and $N \leq 6$ for each band. + +**Table A.4.3.9-11: Antenna Aperture Vendor Declaration** + +| Item | Band | Antenna Aperture Declaration | Ref. | Release | +|------|------|---------------------------------------------------------------------------------------------|---------------|---------| +| 1 | n257 | Maximum radiating aperture of any of the panels integrated in the DUTs is $\leq 5\text{cm}$ | 38.508-1, B.2 | Rel-15 | +| 2 | n258 | Maximum radiating aperture of any of the panels integrated in the DUTs is $\leq 5\text{cm}$ | 38.508-1, B.2 | Rel-15 | +| 3 | n260 | Maximum radiating aperture of any of the panels integrated in the DUTs is $\leq 5\text{cm}$ | 38.508-1, B.2 | Rel-15 | +| 4 | n261 | Maximum radiating aperture of any of the panels integrated in the DUTs is $\leq 5\text{cm}$ | 38.508-1, B.2 | Rel-15 | + +**Table A.4.3.9-12: NR FR1 UL MIMO Capabilities** + +| Item | RF Baseline Implementation Capabilities | Ref. | Comments | +|-----------------|-----------------------------------------------------|----------------|--------------------| +| 1 | NR Frequency band: 1920-1980 MHz, 2110-2170 MHz | 38.101-1, 5.2D | NR FDD FR1 Band 1 | +| 2 | NR Frequency band: 1850-1910 MHz, 1930-1990 MHz | 38.101-1, 5.2D | NR FDD FR1 Band 2 | +| 3 | NR Frequency band: 1710-1785 MHz, 1805-1880 MHz | 38.101-1, 5.2D | NR FDD FR1 Band 3 | +| ... | | | | +| 7 | NR Frequency band: 832-862 MHz, 791-821 MHz | 38.101-1, 5.2D | NR FDD FR1 Band 7 | +| 8 | NR Frequency band: 880-915 MHz, 925-960 MHz | 38.101-1, 5.2D | NR FDD FR1 Band 8 | +| ... | | | | +| 24 | NR Frequency band: 1626.5-1660.5 MHz, 1525-1559 MHz | 38.101-1, 5.2D | NR FDD FR1 Band 24 | +| 25 | NR Frequency band: 1850-1915 MHz, 1930-1995 MHz | 38.101-1, 5.2D | NR FDD FR1 Band 25 | +| ... | | | | +| 30 1 | NR Frequency band: 2305-2315 MHz, 2350-2360 MHz | 38.101-1, 5.2D | NR FDD FR1 Band 30 | +| ... | | | | +| 34 | NR Frequency band: 2010-2025 MHz | 38.101-1, 5.2D | NR TDD FR1 Band 34 | +| ... | | | | +| 38 | NR Frequency band: 2570-2620 MHz | 38.101-1, 5.2D | NR TDD FR1 Band 38 | +| 39 | NR Frequency band: 1880-1920 MHz | 38.101-1, 5.2D | NR TDD FR1 Band 39 | +| 40 | NR Frequency band: 2300-2400 MHz | 38.101-1, 5.2D | NR TDD FR1 Band 40 | +| 41 | NR Frequency band: 2496-2690 MHz | 38.101-1, 5.2D | NR TDD FR1 Band 41 | +| ... | | | | +| 46 | NR Frequency band: 5150-5925 MHz | 38.101-1, 5.2D | NR TDD FR1 Band 46 | +| ... | | | | +| 48 | NR Frequency band: 3550-3700 MHz | 38.101-1, 5.2D | NR TDD FR1 Band 48 | +| ... | | | | +| 66 | NR Frequency band: 1710-1780, 2110-2200 MHz | 38.101-1, 5.2D | NR FDD FR1 Band 66 | +| ... | | | | +| 70 | NR Frequency band: 1695-1710, 1995-2020 MHz | 38.101-1, 5.2D | NR FDD FR1 Band 70 | +| 71 2 | NR Frequency band: 663-698 MHz, 617-652 MHz | 38.101-1, 5.2D | NR FDD FR1 Band 71 | +| ... | | | | +| 77 | NR Frequency band: 3300-4200 MHz | 38.101-1, 5.2D | NR TDD FR1 Band 77 | +| 78 | NR Frequency band: 3300-3800 MHz | 38.101-1, 5.2D | NR TDD FR1 Band 78 | +| 79 | NR Frequency band: 4400-5000 MHz | 38.101-1, 5.2D | NR TDD FR1 Band 79 | +| 80 | NR Frequency band: 1710-1785 MHz | 38.101-1, 5.2D | NR TDD FR1 Band 80 | +| 84 | NR Frequency band: 1920-1980 MHz | 38.101-1, 5.2D | NR TDD FR1 Band 84 | +| 95 | NR Frequency band: 2010-2025 MHz | 38.101-1, 5.2D | NR SUL FR1 Band 95 | +| 97 | NR Frequency band: 2300-2400 MHz | 38.101-1, 5.2D | NR SUL FR1 Band 97 | + +| | | | | +|--------------------------------------------------------------------------------------------------------|--------------------------------------|----------------|--------------------| +| 98 | NR Frequency band: 1880–1920 MHz | 38.101-1, 5.2D | NR SUL FR1 Band 98 | +| 99 | NR Frequency band: 1626.5–1660.5 MHz | 38.101-1, 5.2D | NR SUL FR1 Band 99 | +| NOTE 1: Uplink transmission is not allowed at this band for UE with external vehicle-mounted antennas. | | | | +| NOTE 2: UL MIMO is targeted for FWA form factor. | | | | + +**Table A.4.3.9-13: NR FR2 UL MIMO Capabilities** + +| Item | RF Baseline Implementation Capabilities | Ref. | Comments | +|------|-----------------------------------------|----------------|---------------------| +| 257 | NR Frequency band: 26500-29500 MHz | 38.101-2, 5.2D | NR TDD FR2 Band 257 | +| 258 | NR Frequency band: 24250-27500 MHz | 38.101-2, 5.2D | NR TDD FR2 Band 258 | +| 259 | NR Frequency band: 39500-43500 MHz | 38.101-2, 5.2D | NR TDD FR2 Band 259 | +| 260 | NR Frequency band: 37000–40000 MHz | 38.101-2, 5.2D | NR TDD FR2 Band 260 | +| 261 | NR Frequency band: 27500–28350 MHz | 38.101-2, 5.2D | NR TDD FR2 Band 261 | + +#### A.4.3.10 Sidelink Capabilities + +**Table A.4.3.10-1: NR Sidelink Capabilities** + +| Item | UE Sidelink Capabilities | Ref. | Release | Mnemonic | M | If indicated "Yes" the feature shall be implemented and successfully tested for the corresponding release | Comments | +|------|-------------------------------------------------------------------------------|--------------------|---------|-----------------------------------|----|-----------------------------------------------------------------------------------------------------------|----------| +| 1 | Support transmitting NR sidelink mode 1 scheduled by Uu | 38.306, 4.2.16.1.6 | Rel-16 | pc_NR_sl_TransmissionMode1_r16 | No | | | +| 2 | Support of NR sidelink transmission mode 2 | 38.306, 4.2.16.1.6 | Rel-16 | pc_NR_sl_TransmissionMode2_r16 | No | | | +| 3 | Support of sidelink CSI report with 2 antenna ports | 38.306, 4.2.16.1.6 | Rel-16 | pc_NR_sl_csi_rs_portssidelink_p2 | No | | | +| 4 | Support of out of order delivery of data to upper layers by PDCP for sidelink | 38.306, 4.2.16.1.2 | Rel-16 | pc_outOfOrderDeliverySidelink_r16 | No | | | +| 5 | Support of AM DRB with 18 bit length of RLC sequence number for sidelink | 38.306, 4.2.16.1.3 | Rel-16 | pc_amWithLongSN_Sidelink_r16 | No | | | +| 6 | Support of UM DRB with 12 bit length of RLC sequence number for sidelink | 38.306, 4.2.16.1.3 | Rel-16 | pc_umWithLongSN_Sidelink_r16 | No | | | +| 7 | supports receiving 5 PSFCH resources in a slot | 38.306, 4.2.16.1.6 | Rel-16 | pc_psfch_RxNumber_n5 | No | | | +| 8 | supports receiving 15 PSFCH resources in a slot | 38.306, 4.2.16.1.6 | Rel-16 | pc_psfch_RxNumber_n15 | No | | | +| 9 | supports receiving 25 PSFCH resources in a slot | 38.306, 4.2.16.1.6 | Rel-16 | pc_psfch_RxNumber_n25 | No | | | +| 10 | supports receiving 32 PSFCH resources in a slot | 38.306, 4.2.16.1.6 | Rel-16 | pc_psfch_RxNumber_n32 | No | | | +| 11 | supports receiving 35 PSFCH resources in a slot | 38.306, 4.2.16.1.6 | Rel-16 | pc_psfch_RxNumber_n35 | No | | | +| 12 | supports receiving 45 PSFCH resources in a slot | 38.306, 4.2.16.1.6 | Rel-16 | pc_psfch_RxNumber_n45 | No | | | +| 13 | supports receiving 50 PSFCH resources in a slot | 38.306, 4.2.16.1.6 | Rel-16 | pc_psfch_RxNumber_n50 | No | | | +| 14 | supports receiving 64 PSFCH resources in a slot | 38.306, 4.2.16.1.6 | Rel-16 | pc_psfch_RxNumber_n64 | No | | | +| 15 | supports transmitting 4 PSFCH resources in a slot | 38.306, 4.2.16.1.6 | Rel-16 | pc_psfch_TxNumber_n4 | No | | | + +| | | | | | | | | +|----|-----------------------------------------------------------------------|--------------------|--------|-------------------------------|----|--|--| +| 16 | supports transmitting 8 PSFCH resources in a slot | 38.306, 4.2.16.1.6 | Rel-16 | pc_psfch_TxNumber_n8 | No | | | +| 17 | supports transmitting 16 PSFCH resources in a slot | 38.306, 4.2.16.1.6 | Rel-16 | pc_psfch_TxNumber_n16 | No | | | +| 18 | supports 16 SL HARQ processes for NR PSSCH reception across all links | 38.306, 4.2.16.1.6 | Rel-16 | pc_harq_RxProcessSidelink_n16 | No | | | +| 19 | supports 24 SL HARQ processes for NR PSSCH reception across all links | 38.306, 4.2.16.1.6 | Rel-16 | pc_harq_RxProcessSidelink_n24 | No | | | +| 20 | supports 32 SL HARQ processes for NR PSSCH reception across all links | 38.306, 4.2.16.1.6 | Rel-16 | pc_harq_RxProcessSidelink_n32 | No | | | +| 21 | supports 48 SL HARQ processes for NR PSSCH reception across all links | 38.306, 4.2.16.1.6 | Rel-16 | pc_harq_RxProcessSidelink_n48 | No | | | +| 22 | supports 64 SL HARQ processes for NR PSSCH reception across all links | 38.306, 4.2.16.1.6 | Rel-16 | pc_harq_RxProcessSidelink_n64 | No | | | +| 23 | Support of NR L2 sidelink relay UE operation | 38.306, 4.2.16.1.1 | Rel-17 | pc_relayUE-Operation-L2-r17 | No | | | +| 24 | Support of NR L2 sidelink remote UE operation | 38.306, 4.2.16.1.1 | Rel-17 | pc_remoteUE-Operation-L2-r17 | No | | | + +#### A.4.3.11 High Speed Capabilities + +**Table A.4.3.11-1: High Speed Capabilities** + +| Item | UE High Speed Capabilities | Ref. | Release | Mnemonic | M | If indicated "Yes" the feature shall be implemented and successfully tested for the corresponding release | Comments | +|------|-------------------------------------------------------------------------------------------------------------------|-----------------|---------|---------------------------------|----|-----------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Support the enhanced intra-NR and inter-RAT E-UTRAN measurement requirements to support high speed up to 500 km/h | 38.306, 4.2.19 | Rel-16 | pc_hst_meas_enh_r16 | No | | | +| 2 | Support the enhanced demodulation processing for HST-SFN joint transmission scheme with velocity up to 500km/h | 38.306, 4.2.19 | Rel-16 | pc_hst_demod_enh_r16 | No | | | +| 3 | Support the enhanced intra-NR RRM requirements to support high speed up to 500 km/h | 38.306, 4.2.19 | Rel-16 | pc_hst_intraNR_meas_enh_r16 | No | | This PICS can only be set to true when pc_hst_meas_enh_r16 is set to false.
Up to one PICS between pc_hst_intraNR_meas_enh_r16 and pc_hst_interRAT_meas_enh_r16 can be set to true | +| 4 | Supports the enhanced inter-RAT E-UTRAN RRM requirements to support high speed up to 500 km/h | 38.306, 4.2.19 | Rel-16 | pc_hst_interRAT_meas_enh_r16 | No | | This PICS can only be set to true when pc_hst_meas_enh_r16 is set to false.
Up to one PICS between pc_hst_intraNR_meas_enh_r16 and pc_hst_interRAT_meas_enh_r16 can be set to true | +| 5 | Support for enhanced inter-RAT NR measurement requirements in high-speed scenario | 36.306,4.3.33.7 | Rel-16 | pc_hst_interRAT_NR_meas_enh_r16 | No | | | + +| | | | | | | | | +|----|--------------------------------------------------------------------------------------------------------------------------------|-----------------|--------|-------------------------------------------------|----|--|-----------------------------------------------------------------------------------------------------------------------------------------------| +| 6 | Supports the enhanced RRM requirements for carrier aggregation to support high speed up to 500 km/h | 38.306, 4.2.19 | Rel-17 | pc_hst_RRM_CA_enh_r17 | No | | FR1 only
UE indicating support of this feature shall indicate support of measurementEnhancement-r16 or intraNR-MeasurementEnhancement-r16. | +| 7 | Supports the enhanced RRM requirements for inter-frequency measurements in connected mode to support high speed up to 500 km/h | 38.306, 4.2.19 | Rel-17 | pc_hst_RRM_interfreq_meas_enh_r17 | No | | FR1 only
UE indicating support of this feature shall indicate support of measurementEnhancement-r16 or intraNR-MeasurementEnhancement-r16. | +| 8 | Support the enhanced RRM requirements for inter-frequency IDLE/INACTIVE measurements to support high speed up to 500 km/h | 38.306, 5.6 | Rel-17 | pc_hst_RRM_interfreq_idle_inactive_meas_enh_r17 | No | | FR1 only
UE indicating support of this feature shall indicate support of measurementEnhancement-r16 or intraNR-MeasurementEnhancement-r16. | +| 9 | Indicates whether the UE supports one shot large UL timing adjustment. | 38.306, 4.2.7.2 | Rel-17 | pc_hst_oneStep_UL_Timing_adj_r17 | No | | FR2 only | +| 10 | Support the enhanced intra-NR RRM requirements to support high-speed up to 350 km/h for FR2 | 38.306, 4.2.7.2 | Rel-17 | pc_hst_MeasFlagFR2_r17 | No | | FR2 only
UE indicating support of this feature shall indicate support of ue-PowerClass-v1700 set to 'pc6'. | + +#### A.4.3.12 RedCap Capabilities + +According to TS 38.306 [17] clause 4.2.21: + +CA, MR-DC, DAPS, CPAC and IAB (i.e the RedCap IE is not expected to act as IAB mode) related UE features and corresponding capabilities are not supported by the RedCap UEs. + +- PICS associated to the following features are as below: + - CA: PICS defined in clause A.4.3.2A; + +- MR-DC: PICS defined in clause A.4.3.2B; +- DAPS: PICS include pc\_intraFreqDAPS\_r16, interFreqDAPS\_r16 and other DAPS related PICS; +- CPAC: PICS include pc\_condPSCellChange\_r16 and other CPAC related PICS. +- UE features and corresponding capabilities related to more than 2 UE Rx branches or more than 2 DL MIMO layers, as well as UE features and capabilities related to more than 1 UE Tx branches or more than 1 UL MIMO layers are not supported by RedCap UE. +- For FR1, 1 DL MIMO layer if 1 Rx branch is supported, and 2 DL MIMO layers if 2 Rx branches are supported. +- For FR2, either 1 or 2 DL MIMO layers can be supported, while 2 Rx branches are always supported. + +**Table A.4.3.12-1: RedCap UE Capabilities** + +| Item | UE Capabilities | Ref. | Release | Mnemonic | M | If indicated "Yes" the feature shall be implemented and successfully tested for the corresponding release | Comments | +|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------|------------------------------------------|----|-----------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Support of 16 DRBs for RedCap UEs. | 38.306, 4.2.21.2 | Rel-17 | pc_supportOf16DRB_RedCap_r17 | No | | | +| 2 | Support of RedCap. | 38.306, 4.2.21.2 | Rel-17 | pc_supportOfRedCap_r17 | No | | This PICS shall always be true for RedCap UE. | +| 3 | Void | | | | | | | +| 4 | Void | | | | | | | +| 5 | Support of Half-duplex FDD operation (instead of full-duplex FDD operation) type A for RedCap UE. | 38.306 4.2.21.6.1 | Rel-17 | pc_halfDuplexFDD_TypeA_RedCap_r17 | No | | FDD FR1 only | +| 6 | Support of relaxed RRM measurements in RRC_CONNECTED for RedCap UE. | 38.306 4.2.21.5 | Rel-17 | pc_rrm_RelaxationRRC_ConnectedRedCap_r17 | No | | | +| 7 | Support of initiating UE Assistance Information procedure immediately upon change of its fulfilment status for RRM measurement relaxation criterion for connected mode. | TS 38.331 5.7.4.2 | Rel-17 | pc_UAI_rrm_RelaxationRRC_ConnectedRedCap | No | | The UE will initiate UE Assistance Information procedure immediately upon change of its fulfilment status for RRM measurement relaxation criterion for connected mode.
It is only applicable for RedCap UE. | +| 8 | Support of Rel-17 relaxed RRM measurements of neighbour cells in RRC_IDLE/RRC_INACTIVE | 38.306, 5.6 | Rel-17 | pc_Relaxed_Measurement_RedCap_r17 | No | | It is optional for RedCap UE to support Rel-17 relaxed RRM measurements of neighbour cells in RRC_IDLE/RRC_INACTIVE | + + + +#### A.4.3.13 Multi-SIM Capabilities + +**Table A.4.3.13-1: Multi-SIM Capabilities** + +| Item | UE Sidelink Capabilities | Ref. | Release | Mnemonic | M | If indicated "Yes" the feature shall be implemented and successfully tested for the corresponding release | Comments | +|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|---------|----------------------------|----|-----------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Support one or more Multi-SIM features include N1 NAS signalling connection release/Paging indication for voice services/Reject paging request/Paging restriction/IMSI offset and so on. | 24.501, 4.25 | Rel-17 | pc_5GC_MUSIM | No | | | +| 2 | Support of Multi-SIM N1 NAS signalling connection release | 24.501, 4.25 | Rel-17 | pc_5GC_MUSIM_NCR | No | | | +| 3 | Support of Multi-SIM Paging indication for voice services | 24.501, 4.25 | Rel-17 | pc_5GC_MUSIM_PIV | No | | | +| 4 | Support of Multi-SIM Reject paging request | 24.501, 4.25 | Rel-17 | pc_5GC_MUSIM_RPR | No | | | +| 5 | Support of Multi-SIM Paging restriction | 24.501, 4.25 | Rel-17 | pc_5GC_MUSIM_PR | No | | A UE support Paging restriction shall support:
- N1 NAS signalling connection release or
- Reject paging request or
- both of them | +| 6 | Support providing MUSIM assistance information with MUSIM gap preference and related MUSIM gap configuration | 38.306 4.2.2 | Rel-17 | pc_musim_GapPreference_r17 | No | | UE supporting this feature supports 3 periodic gaps and 1 aperiodic gap. | +| 7 | Support providing MUSIM assistance information with indication of leaving RRC_CONNECTED state | 38.306 4.2.2 | Rel-17 | pc_musimLeaveConnected_r17 | No | | | + +| | | | | | | | | +|---|----------------------------------------------|--------------|--------|--------------------------|----|--|--| +| 8 | Support of MUSIM test function SET MUSIM UAI | 38.509, 5.13 | Rel-17 | pc_Set_MUSIM_UAI_Info_NR | No | | | +|---|----------------------------------------------|--------------|--------|--------------------------|----|--|--| + +#### A.4.3.14 MBS Capabilities + +**Table A.4.3.14-1: MBS Capabilities** + +| Item | UE Sidelink Capabilities | Ref. | Release | Mnemonic | M | If indicated "Yes" the feature shall be implemented and successfully tested for the corresponding release | Comments | +|------|--------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------|--------------------------------------|----|-----------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------| +| 1 | Support of broadcast reception. | 38.3 06, 5.10 | Rel-17 | pc_Broadcast_reception | No | | | +| 2 | Support of dynamic scheduling for multicast for PCell. | 38.3 06, 4.2, 7.5 | Rel-17 | pc_dynamicMulticastPCell_r17 | No | | | +| 3 | Support of ACK/NACK based HARQ-ACK feedback and RRC-based enabling/disabling ACK/NACK-based feedback for dynamic scheduling for multicast. | 38.3 06, 4.2, 7.4 | Rel-17 | pc_ack_NACK_FeedbackForMulticast_r17 | No | | This PICS can only be set to true when pc_dynamicMulticastPCell_r17 is set to true. | +| 4 | Support of PTP retransmission for multicast on the same cell as multicast initial transmission. | 38.3 06, 4.2, 7.4 | Rel-17 | pc_ptp_Retx_Multicast_r17 | No | | This PICS can only be set to true when pc_ack_NACK_FeedbackForMulticast_r17 is set to true. | +| 5 | Support of NACK-only based HARQ-ACK feedback for multicast with ACK/NACK transforming | 38.3 06, 4.2, 7.4 | Rel-17 | pc_nack_OnlyFeedbackForMulticast_r17 | No | | This PICS can only be set to true when pc_ack_NACK_FeedbackForMulticast_r17 is set to true. | + +| | | | | | | | | +|----|-------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------|------------------------------------------------------|----|--|---------------------------------------------------------------------------------------------------------------------------------------| +| 6 | Support of NACK-only based HARQ-ACK feedback for multicast corresponding to a specific sequence or a PUCCH transmission | 38.3 06, 4.2. 7.4 | Rel-1 7 | pc_nack_OnlyFeedbackSpecificResourceForMulticast_r17 | No | | This PICS can only be set to true when pc_nack_OnlyFeedbackForMulticast_r17 is set to true. | +| 7 | Support of multiplexing HARQ-ACK for unicast and for multicast with the same priority and different HARQ-ACK codebook types in a PUCCH or in a PUSCH. | 38.3 06, 4.2. 7.4 | Rel-1 7 | pc_mux_HARQ_ACK_UnicastMulticast_r17 | No | | | +| 8 | Support of DCI format 4_2 with CRC scrambled with G-RNTI for multicast. | 38.3 06, 4.2. 7.2 | Rel-1 7 | pc_dynamicMulticastDCI_Format4_2_r17 | No | | This PICS can only be set to true when pc_dynamicMulticastPCell_r17 is set to true. | +| 9 | Support of DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2. | 38.3 06, 4.2. 7.2 | Rel-1 7 | pc_ack_NACK_FeedbackForMulticastWithDCI_Enabler_r17 | No | | This PICS can only be set to true when pc_dynamicMulticastDCI_Format4_2_r17 and pc_ack_NACK_FeedbackForMulticast_r17 are set to true. | +| 10 | Support of DCI-based enabling/disabling NACK-only based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2. | 38.3 06, 4.2. 7.2 | Rel-1 7 | pc_nack_OnlyFeedbackForMulticastWithDCI_Enabler_r17 | No | | This PICS can only be set to true when pc_dynamicMulticastDCI_Format4_2_r17 and pc_nack_OnlyFeedbackForMulticast_r17 are set to true. | + +| | | | | | | | | +|----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------|------------------------------------------|----|--|-------------------------------------------------------------------------------------------------| +| 11 | Support of MBS reception via broadcast in RRC_CONNECTED on one frequency indicated in an MBSSInterestIndication message, when an SCell is configured and activated on that frequency | 38.3 06, 4.2. 7.6 | Rel-1 7 | pc_broadcastSCell_r17 | No | | | +| 12 | Support of SPS group-common PDSCH for multicast on PCell. | 38.3 06, 4.2. 7.5 | Rel-1 7 | pc_sps_Multicast_r17 | No | | This PICS can only be set to true when pc_dynamicMulticastPCell_r17 is set to true. | +| 13 | Support of ACK/NACK based HARQ-ACK feedback and RRC-based enabling/disabling ACK/NACK-based feedback for SPS group-common PDSCH for multicast. | 38.3 06, 4.2. 7.4 | Rel-1 7 | pc_ack_NACK_FeedbackForSPS_Multicast_r17 | No | | This PICS can only be set to true when pc_sps_Multicast_r17 is set to true. | +| 14 | Support of PTP retransmission associated with CS-RNTI for SPS multicast on the cell same as multicast initial transmission. | 38.3 06, 4.2. 7.4 | Rel-1 7 | pc_ptp_Retx_SPS_Multicast_r17 | No | | This PICS can only be set to true when pc_ack_NACK_FeedbackForSPS_Multicast_r17 is set to true. | +| 15 | Support of unicast PDCCH scrambled with CS-RNTI to release SPS group-common PDSCH. | 38.3 06, 4.2. 7.2 | Rel-1 7 | pc_releaseSPS_MulticastWithCS_RNTI_r17 | No | | This PICS can only be set to true when pc_sps_Multicast_r17 is set to true. | + +| | | | | | | | | +|----|-----------------------------------------------------------|-------------------|---------|------------------------|-----|--|--------------------------------------------------------------------------------------------------------------| +| 16 | Maximum number of G-RNTIs for multicast is more than one. | 38.3 06, 4.2. 7.2 | Rel-1 7 | pc_maxNumberG_RNTI_r17 | N o | | If the maximum number of G-RNTIs for multicast is more than one, then pc_maxNumberG_RNTI_r17 is set to true. | +|----|-----------------------------------------------------------|-------------------|---------|------------------------|-----|--|--------------------------------------------------------------------------------------------------------------| + +### A.4.4 Additional information + +**Table A.4.4-1: Additional information** + +| Item | Additional information | Ref. | Release | Mnemonic | Comments | +|------|----------------------------------------------------------------------|-------------------------------------|---------|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Support of ICMP or ICMP IPv6 | RFC 792 OR
RFC 4443,
RFC 4884 | NA | pc_IP_Ping | UE supports ICMP or ICMPv6 protocol to enable IP Ping Operation | +| 2 | Support of IMS | 24.229, Annex U | Rel-15 | pc IMS_5GS | | +| 3 | Support of rachReport | 38.306, 4.2.17 | Rel-16 | pc_rachReport_r16 | UE supports delivery of rachReport upon request from the network. | +| 4 | Support of GNSS | 38.306, 4.2.18 | Rel-16 | pc_GNSS_location_r16 | UE is equipped with a GNSS or A-GNSS receiver that may be used to provide detailed location information along with SON or MDT related measurements in RRC_CONNECTED, RRC_IDLE and RRC_INACTIVE. | +| 5 | Support of UL PDCP Packet Average Delay | 38.306, 4.2.18 | Rel-16 | pc_PDCP_Delay_r16 | UE supports UL PDCP Packet Average Delay measurement and reporting in RRC_CONNECTED state | +| 6 | Support logged MDT | 38.306, 4.2.18 | Rel-16 | pc_loggedMeasurements_r16 | UE supports logged measurements in RRC_IDLE and RRC_INACTIVE. A UE that supports logged measurements shall support both periodical logging and event-triggered logging. The memory size of MDT logged measurements is 64KB. | +| 7 | Support of uncompensated barometric pressure measurement reporting | 38.306, 4.2.18 | Rel-16 | pc_barometer_r16 | UE supports uncompensated barometric pressure measurement reporting upon request from the network. | +| 8 | Support of orientation information reporting | 38.306, 4.2.18 | Rel-16 | pc_orientation_r16 | UE supports orientation information reporting upon request from the network. | +| 9 | Support of speed information reporting | 38.306, 4.2.18 | Rel-16 | pc_speed_r16 | UE supports speed information reporting upon request from the network. | +| 10 | Support of Bluetooth measurements in RRC_CONNECTED state | 38.306, 4.2.18 | Rel-16 | pc_immMeasBT_r16 | UE supports Bluetooth measurements in RRC_CONNECTED state. | +| 11 | Support of WLAN measurements in RRC_CONNECTED state | 38.306, 4.2.18 | Rel-16 | pc_immMeasWLAN_r16 | UE supports WLAN measurements in RRC_CONNECTED state. | +| 12 | Support of Bluetooth measurements in RRC_IDLE and RRC_INACTIVE state | 38.306, 4.2.18 | Rel-16 | pc_loggedMeasBT_r16 | UE supports Bluetooth measurements in RRC_IDLE and RRC_INACTIVE state. | +| 13 | Support of WLAN measurements in RRC_IDLE and RRC_INACTIVE state | 38.306, 4.2.18 | Rel-16 | pc_loggedMeasWLAN_r16 | UE supports WLAN measurements in RRC_IDLE and RRC_INACTIVE state. | + +| Item | Additional information | Ref. | Release | Mnemonic | Comments | +|------|------------------------------------------------------------------------------------------------------|-----------------|---------|---------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| 14 | Support of SDT in RRC_INACTIVE state via Random Access Procedure | 38.306, 4.2.2 | Rel-17 | pc_ra_SDT_r17 | UE supports SDT via Random Access procedure in RRC_INACTIVE state | +| 15 | Support of SRB SDT in RRC_INACTIVE state | 38.306, 4.2.2 | Rel-17 | pc_srb_SDT_r17 | UE supports SRB SDT in RRC_INACTIVE state | +| 16 | Support of SDT in RRC_INACTIVE state via Configured Grant Type 1 | 38.306, 4.2.7.2 | Rel-17 | pc_cg_SDT_r17 | UE supports SDT via Configured Grant Type 1 in RRC_INACTIVE state | +| 17 | Support of NR NTN access | 38.306, 4.2.2 | Rel-17 | pc_nonTerrestrialNetwork_r17 | UE supports NR NTN access. | +| 18 | Support of RRC INACTIVE state in NTN | 38.331, 6.3.3 | Rel-17 | pc_inactiveStateNTN_r17 | UE supports RRC INACTIVE state in NTN | +| 19 | Support of RA-SDT in NTN | 38.331, 6.3.3 | Rel-17 | pc_ra_SDT_NTN_r17 | UE supports RA-SDT in NTN | +| 20 | Support of SRB-SDT in NTN | 38.331, 6.3.3 | Rel-17 | pc_srb_SDT_NTN_r17 | UE supports SRB-SDT in NTN | +| 21 | Support of storage and delivery of multiple CEF reports | 38.306, 4.2.18 | Rel-17 | pc_multiple_CEF_Report_r17 | UE supports the storage and delivery of multiple CEF reports upon request from the network | +| 22 | Support of the storage of Early Measurement Logging in logged measurements. | 38.306, 4.2.18 | Rel-17 | pc_earlyMeasLog_r17 | UE supports the storage of Early Measurement Logging in logged measurements and the reporting upon request from the network as specified in TS 38.331 | +| 23 | Support of IDC problem detection | 38.331, 6.2.2 | Rel-17 | pc_inDeviceCoexDetected_r17 | UE supports that measurement logging is suspended due to IDC problem detection | +| 24 | Support of delivery of on-Demand SI information upon request from the network | 38.306, 4.2.17 | Rel-17 | pc_onDemandSI_Report_r17 | | +| 25 | Support of the storage and delivery of 2-step RACH related information upon request from the network | 38.306, 4.2.17 | Rel-17 | pc_twoStepRACH_Report_r17 | | +| 26 | Support of mpsPriorityIndication on RRC release with redirect | 38.306, 4.2.2 | Rel-16 | pc_NR_mpsPriorityIndication_r16 | UE supports mpsPriorityIndication on RRC release with redirect as specified in TS 38.331 | +| 27 | Support of RLF-Report for conditional handover | 38.306, 4.2.17 | Rel-17 | pc_rlfReportCHO_r17 | UE supports RLF-Report for conditional handover. | +| 28 | Support of RLF-Report for DAPS handover. | 38.306, 4.2.17 | Rel-17 | pc_rlfReportDAPS_r17 | UE supports RLF-Report for DAPS handover. | +| 29 | Support of the storage and delivery of Successful Handover Report. | 38.306, 4.2.17 | Rel-17 | pc_success_HO_Report_r17 | UE supports the storage and delivery of Successful Handover Report. | + +###### **Table A.4.4-2: Definition of UE implementation capabilities** + +| Item | Definition of UE implementation capabilities | Ref. | Release | Mnemonic | Comments | +|------|------------------------------------------------------------------------------------------------------------------|--------------------|---------|-------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Void | | | | | +| 2 | Void | | | | | +| 3 | Number of UE-requested PDU session establishments after REGISTRATION during the same signalling connection | 24.501 | Rel-15 | pc_noOf_PDUsSame Connection | If the UE requires an external trigger to establish a PDU session, this value shall be set to 0 | +| 4 | Number of UE-requested PDU session establishments after REGISTRATION in a new signalling connection | 24.501 | Rel-15 | pc_noOf_PDUsNewCo nnection | If the UE requires an external trigger to establish a PDU session, this value shall be set to 0 | +| 5 | Number of UE-requested PDN connection establishments after ATTACH during the same signalling connection | 24.301 | Rel-15 | pc_noOf_PDNsSame Connection | If the UE requires an external trigger to establish a PDN connection, this value shall be set to 0 | +| 6 | Number of UE-requested PDN connection establishments after ATTACH in a new signalling connection | 24.301 | Rel-15 | pc_noOf_PDNsNewCo nnection | If the UE requires an external trigger to establish a PDN connection, this value shall be set to 0 | +| 7 | Void | | | | | +| 8 | Support of Emergency PDU session transfer from N1 mode to S1 mode when network does not support N26 interface | TS 24.501, 6.1.4.2 | Rel-15 | pc_TransferEmergenc yPDUN1toS1noN26 | Will the UE attempt to transfer an existing Emergency PDU session upon inter-system change from N1 mode to S1 mode in EMM-IDLE mode if the network does not support N26 interface | +| 9 | Support of Emergency PDN connection transfer from S1 mode to N1 mode when network does not support N26 interface | TS 24.501, 6.1.4.2 | Rel-15 | pc_TransferEmergenc yPDUS1toN1noN26 | Will the UE attempt to transfer an existing Emergency PDN connection upon inter-system change from S1 mode to N1 mode in EMM-IDLE mode if the network does not support N26 interface | +| 10 | Support of UE's usage setting as data centric | TS 24.501, 4.3.1 | Rel-15 | pc_data_centric | UE supports to be configured to consistently behave as a Data centric UE. | + +| Item | Definition of UE implementation capabilities | Ref. | Release | Mnemonic | Comments | +|------|----------------------------------------------------------------------------------------|--------------------|---------|---------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 11 | Support of join in MBS multicast session by sending a PDU Session Modification Request | TS 23.247
7.2.1 | Rel-17 | pc_Join_MBS_by_PDU_Modification | If
pc_Join_MBS_by_PDU_Modification,
UE join in MBS multicast session by sending a PDU Session Modification Request, else UE join in MBS multicast session by sending a PDU Session Establishment Request | + +###### **Table A.4.4-2A: UE APN/DNN Implementation details** + +| Parameter Name | Parameter Type | Supported Value | Comments | +|------------------------------|----------------|------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| pc_APN_Default_Configuration | enumerated | none, internet, ims, urllc, miot, v2x, ethernet, mbs | The DNN/APN configuration specified in TS 38.508-1 [2], Table 4.8.4-1 which is to be used for the default DNN/APN.
The value provided shall match one of the DNN/APN types if a Default DNN will be established, e.g. internet, ims, etc. or shall be set to none if the UE will not establish default DNN/APN. | +| pc_APN_ID_Internet | charstring | | APN/DNN ID of type Internet (NOTE 1)

The APN/DNN Network Identifier portion of the Access Point / Data Network Name, as defined in TS 23.003 [26], subclause 9.1

OR "none" if the UE will not establish PDN/PDU of type Internet

If the provided value is different to "none" then for this APN/DNN the DNN/APN configuration of type "Internet" as specified in TS 38.508-1 [2], Table 4.8.4-1 applies. | +| pc_APN_ID_IMS | charstring | | APN/DNN ID of type IMS (NOTE 1)

The APN/DNN Network Identifier portion of the Access Point / Data Network Name, as defined in TS 23.003 [26], subclause 9.1

OR "none" if the UE will not establish PDN/PDU of type IMS

If the provided value is different to "none" then for this APN/DNN the DNN/APN configuration of type "IMS" as specified in TS 38.508-1 [2], Table 4.8.4-1 applies. | +| pc_APN_ID_URLLC | charstring | | APN/DNN ID of type URLLC (NOTE 1)

The APN/DNN Network Identifier portion of the Access Point / Data Network Name, as defined in TS 23.003 [26], subclause 9.1

OR "none" if the UE will not establish PDN/PDU of type URLLC

If the provided value is different to "none" then for this APN/DNN the DNN/APN configuration of type "URLLC" as specified in TS 38.508-1 [2], Table 4.8.4-1 applies. | +| pc_APN_ID_MIoT | charstring | | APN/DNN ID of type MIoT (NOTE 1)

The APN/DNN Network Identifier portion of the Access Point / Data Network Name, as defined in TS 23.003 [26], subclause 9.1

OR "none" if the UE will not establish PDN/PDU of | + +| | | | | +|--------------------|------------|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | type MIoT

If the provided value is different to "none" then for this APN/DNN the DNN/APN configuration of type "MIoT" as specified in TS 38.508-1 [2], Table 4.8.4-1 applies. | +| pc_APN_ID_V2X | charstring | | APN/DNN ID of type V2X
(NOTE 1)

The APN/DNN Network Identifier portion of the Access Point / Data Network Name, as defined in TS 23.003 [26], subclause 9.1

OR "none" if the UE will not establish PDN/PDU of type V2X

If the provided value is different to "none" then for this APN/DNN the DNN/APN configuration of type "V2X" as specified in TS 38.508-1 [2], Table 4.8.4-1 applies. | +| pc_APN_ID_Ethernet | charstring | | APN/DNN ID of type Ethernet
(NOTE 1)

The APN/DNN Network Identifier portion of the Access Point / Data Network Name, as defined in TS 23.003 [26], subclause 9.1

OR "none" if the UE will not establish PDN/PDU of type Ethernet

If the provided value is different to "none" then for this APN/DNN the DNN/APN configuration of type "Ethernet" as specified in TS 38.508-1 [2], Table 4.8.4-1 applies. | +| pc_APN_ID_MBS | charstring | | APN/DNN ID of type MBS
(NOTE 1)

The APN/DNN Network Identifier portion of the Access Point / Data Network Name, as defined in TS 23.003 [26], subclause 9.1

OR "none" if the UE will not establish PDN/PDU of type MBS

If the provided value is different to "none" then for this APN/DNN the DNN/APN configuration of type "MBS" as specified in TS 38.508-1 [2], Table 4.8.4-1 applies. | + +NOTE 1: For each UE, the APN/DNN IDs which will be used during for PDN/PDU establishment shall be provided. These shall cover both: The APN/DNN IDs which the UE will provide itself in the PDN/PDU establishment request, and, An APN/DNN ID which the UE will prefer to be assigned by the SS in the case of Default APN/DNN, if the UE utilises Provided and/or Default APN/DNN. + +# Annex B (informative): Status of NR band and NR CA, NR-DC, EN-DC, NE-DC and NR SUL configurations in 3GPP UE conformance test specifications + +See attached document "PRD21 5G NR bands and CADC configurations list v1.7.0.zip" for the status of NR and V2X bands and its power classes, and NR-DC, EN-DC, NE-DC, NR SUL and V2X configurations and its power classes in the version of 3GPP UE conformance test specifications as indicated in the header of this document. + +# Annex C (informative): Change history + +| Change history | | | | | | | | +|----------------|--------------------|-----------|------|-----|-----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-12 | RAN5#77 | R5-176852 | - | - | - | Introduction of TS 38.508-2 | 0.1.0 | +| 2018-04 | RAN5#2-5G-NR Adhoc | R5-182069 | - | - | - | Addition of several required PICS | 0.2.1 | +| 2018-05 | RAN5#79 | R5-183271 | - | - | - | Addition of Missing PICS | 1.0.0 | +| 2018-06 | RAN#80 | RP-181208 | - | - | - | put under revision control as v15.0.0 with small editorial changes | 15.0.0 | +| 2018-09 | RAN#81 | R5-185161 | 0001 | 1 | F | Addition of PICS | 15.1.0 | +| 2018-12 | RAN#82 | R5-187040 | 0010 | - | F | Addition of new band into RF baseline implementation capabilities | 15.2.0 | +| 2018-12 | RAN#82 | R5-187777 | 0011 | 1 | F | Addition of PICS | 15.2.0 | +| 2019-03 | RAN#83 | R5-192365 | 0020 | 1 | F | Introduction of Physical Layer Baseline Implementation Capabilities for NR CA, NR DC and EN-DC | 15.3.0 | +| 2019-03 | RAN#83 | R5-192706 | 0019 | 1 | F | Introduction of Non 3GPP Access over WLAN PICS | 15.3.0 | +| 2019-03 | RAN#83 | R5-192746 | 0017 | 1 | F | Addition of Capability for test cases | 15.3.0 | +| 2019-03 | RAN#83 | R5-192747 | 0018 | 1 | F | PICS Update | 15.3.0 | +| 2019-03 | RAN#83 | R5-192748 | 0021 | 1 | F | Add UE capability PDU | 15.3.0 | +| 2019-06 | RAN#84 | R5-193576 | 0027 | - | F | Update of Clause 2 References of 38.508-2 | 15.4.0 | +| 2019-06 | RAN#84 | R5-193577 | 0028 | - | F | Introduction of Table A.4.3.2.A.2.1-3 configuration for FR1 Intra-band contiguous CA | 15.4.0 | +| 2019-06 | RAN#84 | R5-193756 | 0030 | - | F | Addition of UE capability for mobility | 15.4.0 | +| 2019-06 | RAN#84 | R5-195137 | 0036 | 1 | F | Addition of ICS for FR2 Multiband Relaxation declaration | 15.4.0 | +| 2019-06 | RAN#84 | R5-195331 | 0031 | 1 | F | PICS update | 15.4.0 | +| 2019-06 | RAN#84 | R5-195428 | 0035 | 2 | F | Resubmission: Addition of optional UE capabilities for Demod | 15.4.0 | +| 2019-06 | RAN#84 | R5-195052 | 0029 | 1 | F | Addition of CA_n41C CA_n66B and CA_n71B | 16.0.0 | +| 2019-09 | RAN#85 | R5-197225 | 0037 | 1 | F | Addition and Update of PICS | 16.1.0 | +| 2019-09 | RAN#85 | R5-197440 | 0038 | 1 | F | Addition of NR FR1 intraband non-contiguous and interband CA tables with combinations CA_66(2A), CA_n66A-n70A, CA_n66A-n71A, CA_n70A-n71A, CA_n66B-n70A, CA_n66(2A)-n70A, CA_n66(2A)-n71A to 38.508-2 | 16.1.0 | +| 2019-09 | RAN#85 | R5-197442 | 0045 | - | F | Updates of SA and NSA information | 16.1.0 | +| 2019-09 | RAN#85 | R5-197510 | 0044 | 1 | F | Update to 38.508-2 for 4Rx handling | 16.1.0 | +| 2019-12 | RAN#86 | R5-198169 | 0049 | - | F | Introduction of UE capabilities for Rel-16 NR CA and EN-DC configurations | 16.2.0 | +| 2019-12 | RAN#86 | R5-198349 | 0051 | - | F | Addition of NR FR1 intraband non-contiguous and interband CA tables with combinations CA_n66B-n71A, CA_n66A-n70A-n71A, CA_n66B-n70A-n71A, CA_n66(2A)-n70A-n71A to 38.508-2 | 16.2.0 | +| 2019-12 | RAN#86 | R5-198873 | 0047 | 1 | F | Add GAP pattern to PICS | 16.2.0 | +| 2019-12 | RAN#86 | R5-198963 | 0048 | 1 | F | Introduction of UE capabilities for Rel-15 NR CA, NR DC and EN-DC configurations | 16.2.0 | +| 2019-12 | RAN#86 | R5-198964 | 0050 | 1 | F | Introduction of UE capabilities for new Rel-16 NR bands and new SDL band n29 associated NR CA configuration CA_n29A-n66A | 16.2.0 | +| 2019-12 | RAN#86 | R5-199076 | 0056 | 2 | F | Addition of new PICS needed for testing | 16.2.0 | +| 2019-12 | RAN#86 | R5-199305 | 0052 | 1 | F | Update to 38.508-2 regarding 4Rx antenna ports capability | 16.2.0 | +| 2019-12 | RAN#86 | R5-199312 | 0058 | - | F | Correction to n66 intra-band CA Physical Layer Baseline Implementation Capabilities | 16.2.0 | +| 2019-12 | RAN#86 | R5-199462 | 0054 | 2 | F | EN-DC bands Implementation Conformance Statement (ICS) proforma Updates | 16.2.0 | +| 2019-12 | RAN#86 | R5-199482 | 0053 | 1 | F | Physical Layer Baseline Implementation Capabilities for Beam Correspondence | 16.2.0 | +| 2020-03 | RAN#87 | R5-200558 | 0065 | - | F | Beam Correspondence Mnemonic name update | 16.3.0 | +| 2020-03 | RAN#87 | R5-200592 | 0067 | - | F | Corrections on categories of NR DC and EN-DC physical layer capabilities in 38.508-2 | 16.3.0 | +| 2020-03 | RAN#87 | R5-200598 | 0068 | - | F | Introduction on supported inter-band EN-DC configurations in 38.508-2 | 16.3.0 | +| 2020-03 | RAN#87 | R5-200636 | 0070 | - | F | Corrections and Addition of NR PICS | 16.3.0 | +| 2020-03 | RAN#87 | R5-200903 | 0059 | 1 | F | Additional UE Power Class declaration | 16.3.0 | +| 2020-03 | RAN#87 | R5-200923 | 0062 | 1 | F | Introduction of UE capabilities for n95 SUL band | 16.3.0 | +| 2020-03 | RAN#87 | R5-200969 | 0066 | 1 | F | Corrections on categories of NR CA physical layer capabilities in 38.508-2 | 16.3.0 | +| 2020-03 | RAN#87 | R5-200970 | 0069 | 1 | F | Adding modified MPR behaviour to physical layer capabilities | 16.3.0 | +| 2020-03 | RAN#87 | R5-201062 | 0064 | 1 | F | Introduction of UE capabilities for Rel-16 EN-DC configurations | 16.3.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|---------------------------------------------------------------------------------------------------------------------------|--------| +| 2020-03 | RAN#87 | R5-201123 | 0060 | 1 | F | Correction to NR TC PICS | 16.3.0 | +| 2020-06 | RAN#88 | R5-201923 | 0075 | - | F | Addition of TDD-TDD PC2 inter-band EN-DC UE RF Baseline implementation Capabilities declaration | 16.4.0 | +| 2020-06 | RAN#88 | R5-202108 | 0077 | - | F | Updates on UE capability for Rel-15 NR CA configuration | 16.4.0 | +| 2020-06 | RAN#88 | R5-202226 | 0079 | - | F | Update NR intra-band contiguous CA implementation capabilities in 38.508-2 | 16.4.0 | +| 2020-06 | RAN#88 | R5-202228 | 0080 | - | F | Update RF baseline implementation capabilities in 38.508-2 | 16.4.0 | +| 2020-06 | RAN#88 | R5-202446 | 0082 | - | F | Addition of EN-DC configurations DC_41C_n41A and DC_41D_n41A | 16.4.0 | +| 2020-06 | RAN#88 | R5-202709 | 0078 | 1 | F | Update ICS proforma tables for UE implementation types in A.4.1 of 38.508-2 | 16.4.0 | +| 2020-06 | RAN#88 | R5-202871 | 0074 | 1 | F | Introduction of several new NR 2CA and 3CA combinations | 16.4.0 | +| 2020-06 | RAN#88 | R5-203113 | 0076 | 2 | F | Additions and corrections to PICS | 16.4.0 | +| 2020-09 | RAN#89 | R5-203279 | 0085 | - | F | n26 Implementation baseline capabilities in 38.508-2 | 16.5.0 | +| 2020-09 | RAN#89 | R5-203457 | 0088 | - | F | Fixing References | 16.5.0 | +| 2020-09 | RAN#89 | R5-203463 | 0089 | - | F | Addition of PICS for CSI-RS measurement without associated SSB | 16.5.0 | +| 2020-09 | RAN#89 | R5-203632 | 0090 | - | F | Introduction of UE capabilities for additional Rel-15 band EN-DC inter-band configurations | 16.5.0 | +| 2020-09 | RAN#89 | R5-203635 | 0091 | - | F | Introduction of UE capabilities for additional Rel-16 EN-DC inter-band configurations | 16.5.0 | +| 2020-09 | RAN#89 | R5-203911 | 0094 | - | F | Update of A.4.3.2A for intra-band contiguous CA capabilities | 16.5.0 | +| 2020-09 | RAN#89 | R5-203912 | 0095 | - | F | Update of A.4.3.2A.3 for intra-band non-contiguous CA capabilities | 16.5.0 | +| 2020-09 | RAN#89 | R5-203914 | 0097 | - | F | Update of A.4.3.2B for NR-DC capabilities | 16.5.0 | +| 2020-09 | RAN#89 | R5-203917 | 0100 | - | F | Update of A.4.3.2B.2.3 for inter-band EN-DC including FR2 capabilities | 16.5.0 | +| 2020-09 | RAN#89 | R5-204332 | 0108 | - | F | Adding new ICS for handling inter-system change S1-N1 and aligning PDN and PDU handling | 16.5.0 | +| 2020-09 | RAN#89 | R5-204511 | 0109 | 1 | F | Addition of UE capability for voiceFallbackIndicationEPS-r16 | 16.5.0 | +| 2020-09 | RAN#89 | R5-204544 | 0106 | 1 | F | Addition and update of PICS | 16.5.0 | +| 2020-09 | RAN#89 | R5-204710 | 0105 | 1 | F | CR to 38.508-2 to allow vendor declarations related to beam peak searches | 16.5.0 | +| 2020-09 | RAN#89 | R5-204759 | 0102 | 1 | F | Addition of PICS for intra-band EN-DC PC2 | 16.5.0 | +| 2020-09 | RAN#89 | R5-204801 | 0084 | 1 | F | Introduction of Rel-16 inter-band EN-DC configurations within FR1 for physical layer baseline implementation capabilities | 16.5.0 | +| 2020-09 | RAN#89 | R5-204802 | 0096 | 1 | F | Update of A.4.3.2A.4 for inter-band CA within FR1 capabilities | 16.5.0 | +| 2020-09 | RAN#89 | R5-204803 | 0098 | 1 | F | Update of A.4.3.2B.2 for intra-band EN-DC capabilities | 16.5.0 | +| 2020-09 | RAN#89 | R5-204804 | 0099 | 1 | F | Update of A.4.3.2B.2.3 for inter-band EN-DC including FR1 and FR2 capabilities | 16.5.0 | +| 2020-09 | RAN#89 | R5-204805 | 0101 | 1 | F | Update of A.4.3.2B.2.3 for inter-band EN-DC within FR1 capabilities | 16.5.0 | +| 2020-09 | RAN#89 | R5-204806 | 0104 | 1 | F | Introduction of UE capabilities for Rel-16 EN-DC configurations | 16.5.0 | +| 2020-09 | RAN#89 | R5-204853 | 0086 | 1 | F | Added UE Phy layer capability into 38.508-2 from 38.306 | 16.5.0 | +| 2020-09 | RAN#89 | R5-204902 | 0087 | 1 | F | Updated table A.4.3.9-4 - 4 Rx antenna ports capabilities | 16.5.0 | +| 2020-09 | RAN#89 | R5-204903 | 0092 | 1 | F | Introduction and correction of general capabilities and some band-combo information for EN-DC | 16.5.0 | +| 2020-09 | RAN#89 | R5-204904 | 0107 | 1 | F | Add new PICS | 16.5.0 | +| 2020-12 | RAN#90 | R5-205053 | 0110 | - | F | ICS for iRAT RS-SINR and SFTD measurements | 16.6.0 | +| 2020-12 | RAN#90 | R5-205612 | 0117 | - | F | Addition of UE capabilities for Rel-16 UE power saving in NR | 16.6.0 | +| 2020-12 | RAN#90 | R5-205640 | 0118 | - | F | Addition of PC2 EN-DC DC_3A-n78A into RF Baseline implementation Capabilities | 16.6.0 | +| 2020-12 | RAN#90 | R5-205695 | 0120 | - | F | Addition of ICS for UE support PUSCH Pi2 BPSK | 16.6.0 | +| 2020-12 | RAN#90 | R5-205707 | 0121 | - | F | Revise ICS Proforma Tables for Remaining n14, n29, and n30 Capabilities | 16.6.0 | +| 2020-12 | RAN#90 | R5-205773 | 0123 | - | F | Correction to baseline implementation capabilities for a few Rel-16 inter-band EN-DC configurations | 16.6.0 | +| 2020-12 | RAN#90 | R5-205774 | 0124 | - | F | Addition of baseline implementation capabilities for Rel-15 EN-DC inter-band configuration DC_3A_n7A | 16.6.0 | +| 2020-12 | RAN#90 | R5-205941 | 0127 | - | F | Update for Flexible PDU-PDN - ICS definitions new and removal | 16.6.0 | +| 2020-12 | RAN#90 | R5-206023 | 0129 | - | F | Update of A.4.1 for UE implementation types | 16.6.0 | +| 2020-12 | RAN#90 | R5-206024 | 0130 | - | F | Update of A.4.3.1 for UE power class implementation capabilities | 16.6.0 | +| 2020-12 | RAN#90 | R5-206025 | 0131 | - | F | Update of A.4.3.2A.2 for implementation capabilities of NR intra-band contiguous CA | 16.6.0 | +| 2020-12 | RAN#90 | R5-206026 | 0132 | - | F | Update of A.4.3.2A.3 for implementation capabilities of NR intra-band non-contiguous CA | 16.6.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------------|--------| +| 2020-12 | RAN#90 | R5-206027 | 0133 | - | F | Update of A.4.3.2B for NR-DC implementation capabilities | 16.6.0 | +| 2020-12 | RAN#90 | R5-206310 | 0115 | 1 | F | Addition and update of PICS | 16.6.0 | +| 2020-12 | RAN#90 | R5-206395 | 0112 | 1 | F | Adding UE capabilities for IIoT test | 16.6.0 | +| 2020-12 | RAN#90 | R5-206404 | 0138 | 1 | F | Add UE capability for NR MobEnc TCs | 16.6.0 | +| 2020-12 | RAN#90 | R5-206410 | 0137 | 1 | F | Add UE capability for NR V2X TCs | 16.6.0 | +| 2020-12 | RAN#90 | R5-206414 | 0139 | 1 | F | Adding UE capabilities for eMIMO | 16.6.0 | +| 2020-12 | RAN#90 | R5-206421 | 0116 | 1 | F | Addition of PICS for Rel-16 RACS | 16.6.0 | +| 2020-12 | RAN#90 | R5-206428 | 0111 | 1 | F | Addition of UE capability for nr-HO-ToEN-DC-r16 | 16.6.0 | +| 2020-12 | RAN#90 | R5-206634 | 0114 | 1 | F | Addition of EN-DC capabilities of number of NR DL or number of NR UL carriers | 16.6.0 | +| 2020-12 | RAN#90 | R5-206635 | 0125 | 1 | F | Correction to Enhanced Type X receiver PICS | 16.6.0 | +| 2020-12 | RAN#90 | R5-206636 | 0126 | 1 | F | Addition of PICS for LTE CRS rate matching capability | 16.6.0 | +| 2020-12 | RAN#90 | R5-206637 | 0128 | 1 | F | Addition of PICS for intra-frequency measurements with gap | 16.6.0 | +| 2020-12 | RAN#90 | R5-206716 | 0122 | 1 | F | Addition of baseline implementation capabilities for a few Rel-16 EN-DC inter-band configurations | 16.6.0 | +| 2020-12 | RAN#90 | R5-206717 | 0134 | 1 | F | Introduction of UE capabilities for additional Rel-16 EN-DC inter-band configurations | 16.6.0 | +| 2020-12 | RAN#90 | R5-206771 | 0119 | 1 | F | Addition of PC2 UE RF Baseline Implementation Capabilities for DC_3A_n41A | 16.6.0 | +| 2021-03 | RAN#91 | R5-210081 | 0141 | - | F | Introduction of Additional capabilities for NR Band n53 | 16.7.0 | +| 2021-03 | RAN#91 | R5-210483 | 0148 | - | F | Correction of core spec Ref. for 4 Rx antenna ports Capabilities | 16.7.0 | +| 2021-03 | RAN#91 | R5-210484 | 0149 | - | F | Addition of PUSCH HalfPi BPSK capability in FR2 | 16.7.0 | +| 2021-03 | RAN#91 | R5-210566 | 0150 | - | F | Update on manufacturer declaration required for Receiver Beam Peak Search | 16.7.0 | +| 2021-03 | RAN#91 | R5-211001 | 0160 | - | F | Update to NR FR1 2Rx-4Rx implementation Capabilities | 16.7.0 | +| 2021-03 | RAN#91 | R5-211108 | 0163 | - | F | Corrections to subclauses in 38.508-2 with appropriate subclause level and heading styles | 16.7.0 | +| 2021-03 | RAN#91 | R5-211229 | 0169 | - | F | Add n26 to 2Rx capabilities declaration | 16.7.0 | +| 2021-03 | RAN#91 | R5-211376 | 0147 | 1 | F | Addition and update of PICS | 16.7.0 | +| 2021-03 | RAN#91 | R5-211449 | 0164 | 1 | F | Correction of Table A.4.3.2B.2.3.12-1 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211457 | 0154 | 1 | F | Add UE capability for NR MobEnc | 16.7.0 | +| 2021-03 | RAN#91 | R5-211463 | 0144 | 1 | F | Adding scell dormancy indication outside active time to physical layer baseline implementation capabilities | 16.7.0 | +| 2021-03 | RAN#91 | R5-211469 | 0143 | 1 | F | Introduction of common implementation conformance statements for R16 NR SON and MDT | 16.7.0 | +| 2021-03 | RAN#91 | R5-211492 | 0153 | 1 | F | Introduction of general capability for NR to UTRA-FDD CELL_DCH CS handover | 16.7.0 | +| 2021-03 | RAN#91 | R5-211674 | 0162 | 1 | F | Introduction of UE capabilities for Rel-15 EN-DC FR2 configuration CA_n261(2A) | 16.7.0 | +| 2021-03 | RAN#91 | R5-211815 | 0142 | 1 | F | Addition of common ICS in A.4.3.11 for Rel-16 HST | 16.7.0 | +| 2021-03 | RAN#91 | R5-211858 | 0140 | 1 | F | Update of UE capabilities for EN-DC configurations | 16.7.0 | +| 2021-03 | RAN#91 | R5-211859 | 0145 | 1 | F | Update of Table A.4.3.2B.2.3.2-2 (DC_1A-8A_n78A, DC_3A-8A_n78A) | 16.7.0 | +| 2021-03 | RAN#91 | R5-211860 | 0146 | 1 | F | Update of Table A.4.3.2B.2.3.3-2 (DC_1A-3A-8A_n78A) | 16.7.0 | +| 2021-03 | RAN#91 | R5-211861 | 0161 | 1 | F | Introduction of UE capabilities for Rel-15 EN-DC FR1 configurations | 16.7.0 | +| 2021-03 | RAN#91 | R5-211862 | 0165 | 1 | F | Addition of PICS powerBoosting-pi2BPSK | 16.7.0 | +| 2021-03 | RAN#91 | R5-211904 | 0170 | 1 | F | Updating UE capability for Rel-16 NR inter-band CA configurations for band n1 | 16.7.0 | +| 2021-03 | RAN#91 | R5-211910 | 0155 | 1 | F | Adding PICS for UL switching | 16.7.0 | +| 2021-03 | RAN#91 | R5-211839 | 0159 | 1 | F | Adding PICS for SUL with DL CA configurations | 17.0.0 | +| 2021-06 | RAN#92 | R5-212120 | 0174 | - | F | Updating UE capabilities for Rel-17 EN-DC band combinations within FR1 | 17.1.0 | +| 2021-06 | RAN#92 | R5-212136 | 0175 | - | F | Updating UE capabilities for R17 NR inter-band CA configurations in FR1 | 17.1.0 | +| 2021-06 | RAN#92 | R5-212199 | 0177 | - | F | Update of Table A.4.3.2B.2.3.6-2 - DC_8A_n257A | 17.1.0 | +| 2021-06 | RAN#92 | R5-212568 | 0180 | - | F | Corrections to Table A.4.3.2A.4.1-3 for NR Inter-band CA within FR1 and two bands | 17.1.0 | +| 2021-06 | RAN#92 | R5-212830 | 0188 | - | F | Correction of A.4.1 for UE implementation types for SA CA UE radio technologies | 17.1.0 | +| 2021-06 | RAN#92 | R5-212831 | 0189 | - | F | Correction of A.4.3.9 for additional capabilities for UE declared capability | 17.1.0 | +| 2021-06 | RAN#92 | R5-212834 | 0191 | - | F | Update of A.4.3.2A.2.2 for capabilities for NR intra-band contiguous CA within FR2 | 17.1.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|--------------------------------------------------------------------------------------------------------|--------| +| 2021-06 | RAN#92 | R5-212835 | 0192 | - | F | Update of A.4.3.2A.3.1 for capabilities for NR intra-band non-contiguous CA within FR1 | 17.1.0 | +| 2021-06 | RAN#92 | R5-212836 | 0193 | - | F | Update of A.4.3.2A.4.1 for capabilities for NR inter-band CA within FR1 | 17.1.0 | +| 2021-06 | RAN#92 | R5-212837 | 0194 | - | F | Update of A.4.3.2B.1 for capabilities for NR-DC | 17.1.0 | +| 2021-06 | RAN#92 | R5-212838 | 0195 | - | F | Update of A.4.3.2B.2.3.8 for capabilities for EN-DC including FR2 | 17.1.0 | +| 2021-06 | RAN#92 | R5-212854 | 0197 | - | F | Addition of suffix for Mnemonic pc_pusch_halfpiBPSK to differentiate FR1 and FR2 | 17.1.0 | +| 2021-06 | RAN#92 | R5-212855 | 0198 | - | F | Addition of ENDC NR part power class parameter | 17.1.0 | +| 2021-06 | RAN#92 | R5-212931 | 0200 | - | F | Addition of PICS for NR sidelink RF testing | 17.1.0 | +| 2021-06 | RAN#92 | R5-212938 | 0201 | - | F | Adding PICS for eMIMO single DCI based SDM | 17.1.0 | +| 2021-06 | RAN#92 | R5-212947 | 0202 | - | F | Adding PICS for URLLC low BLER | 17.1.0 | +| 2021-06 | RAN#92 | R5-212987 | 0204 | - | F | Introducing Rel-16 CA configuration CA_n28A-n41A | 17.1.0 | +| 2021-06 | RAN#92 | R5-213006 | 0205 | - | F | Introducing Rel-17 new SUL or CA configurations | 17.1.0 | +| 2021-06 | RAN#92 | R5-213191 | 0210 | - | F | Introduce PICS for NR URLLC | 17.1.0 | +| 2021-06 | RAN#92 | R5-213258 | 0215 | - | F | Addition of PC2 EN-DC DC_1A-n78A into RF Baseline implementation Capabilities | 17.1.0 | +| 2021-06 | RAN#92 | R5-213374 | 0217 | - | F | Introduce PICS for 2-step RACH | 17.1.0 | +| 2021-06 | RAN#92 | R5-213406 | 0218 | - | F | Addition of capability for NR Sidelink Transmission Mode 2 | 17.1.0 | +| 2021-06 | RAN#92 | R5-213453 | 0179 | 1 | F | Addition of Emergency PDU-PDN transfer capabilities | 17.1.0 | +| 2021-06 | RAN#92 | R5-213454 | 0216 | 1 | F | Corrections and Addition of NR PICS | 17.1.0 | +| 2021-06 | RAN#92 | R5-213552 | 0173 | 1 | F | Add new UE capability for Rel-16 NR Mobility Enhancement | 17.1.0 | +| 2021-06 | RAN#92 | R5-213575 | 0185 | 1 | F | Addition of PICS for Rel-16 NPN | 17.1.0 | +| 2021-06 | RAN#92 | R5-213581 | 0184 | 1 | F | Addition of PICS for Test function for RACS | 17.1.0 | +| 2021-06 | RAN#92 | R5-213602 | 0182 | 1 | F | Update of Additional information | 17.1.0 | +| 2021-06 | RAN#92 | R5-213642 | 0183 | 1 | F | Addition of common ICS in A.4.3.7 for Rel-16 NSSAA | 17.1.0 | +| 2021-06 | RAN#92 | R5-213646 | 0209 | 1 | F | Addition of PICS for SST handling | 17.1.0 | +| 2021-06 | RAN#92 | R5-213835 | 0212 | 1 | F | CR to 38.508-2 on Optional 4x2 PC3 Antenna Array Configuration | 17.1.0 | +| 2021-06 | RAN#92 | R5-213965 | 0181 | 1 | F | Addition of CA_n41C-n79A | 17.1.0 | +| 2021-06 | RAN#92 | R5-213966 | 0186 | 1 | F | Addition of A.4.3.2A.5 for capabilities for NR inter-band CA within FR2 | 17.1.0 | +| 2021-06 | RAN#92 | R5-213967 | 0187 | 1 | F | Addition of A.4.3.2A.6 for capabilities for NR inter-band CA between FR1 and FR2 | 17.1.0 | +| 2021-06 | RAN#92 | R5-213968 | 0190 | 1 | F | Update of A.4.3.2A.2.1 for capabilities for NR intra-band contiguous CA within FR1 | 17.1.0 | +| 2021-06 | RAN#92 | R5-213969 | 0206 | 1 | F | Introduction of CA_n48(2A) | 17.1.0 | +| 2021-06 | RAN#92 | R5-214020 | 0172 | 1 | F | Updating A.4.3.2C for Rel-17 SUL combinations | 17.1.0 | +| 2021-06 | RAN#92 | R5-214027 | 0178 | 1 | F | UL power boosting via suspended IBE requirements | 17.1.0 | +| 2021-06 | RAN#92 | R5-214044 | 0213 | 1 | F | CR to 38.508-2 on larger quiet zone with grey-box approach | 17.1.0 | +| 2021-09 | RAN#93 | R5-214334 | 0220 | - | F | Introduction of ICS for NR-U | 17.2.0 | +| 2021-09 | RAN#93 | R5-214441 | 0221 | - | F | Corrections and Addition of NR PICS | 17.2.0 | +| 2021-09 | RAN#93 | R5-214565 | 0222 | - | F | Addition of PICS for relaxed RRM measurement | 17.2.0 | +| 2021-09 | RAN#93 | R5-214771 | 0226 | - | F | Correction to NR capability | 17.2.0 | +| 2021-09 | RAN#93 | R5-214934 | 0227 | - | F | Introduce PICS for NR URLLC | 17.2.0 | +| 2021-09 | RAN#93 | R5-215078 | 0232 | - | F | Addition of PICS for V2X SL-MIMO test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-215095 | 0233 | - | F | Adding PICS for eMIMO demod test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-215135 | 0236 | - | F | Addition of capability for NR Sidelink Transmission Mode 2 | 17.2.0 | +| 2021-09 | RAN#93 | R5-215161 | 0237 | - | F | Addition of PICS for Rel-16 release preference assistance information | 17.2.0 | +| 2021-09 | RAN#93 | R5-215184 | 0238 | - | F | Addition of UE capability for low PAPR DMRS | 17.2.0 | +| 2021-09 | RAN#93 | R5-215281 | 0241 | - | F | Introduction of CA_n71(2A) | 17.2.0 | +| 2021-09 | RAN#93 | R5-215310 | 0242 | - | F | Introduction of UE capabilities for R17 SUL band n97 | 17.2.0 | +| 2021-09 | RAN#93 | R5-215357 | 0244 | - | F | Updating UE capability for NR inter-band EN-DC configurations | 17.2.0 | +| 2021-09 | RAN#93 | R5-215581 | 0255 | - | F | CR on Antenna Aperture Declarations | 17.2.0 | +| 2021-09 | RAN#93 | R5-215838 | 0228 | 1 | F | Addition of PICS for inter-RAT SFTD measurements | 17.2.0 | +| 2021-09 | RAN#93 | R5-215839 | 0245 | 1 | F | Update of A.4.3.2A.4.1 for implementation capabilities for NR inter-band CA within FR1 for two bands | 17.2.0 | +| 2021-09 | RAN#93 | R5-215840 | 0246 | 1 | F | Update of A.4.3.2A.4.2 for implementation capabilities for NR inter-band CA within FR1 for three bands | 17.2.0 | +| 2021-09 | RAN#93 | R5-215841 | 0247 | 1 | F | Update of A.4.3.2A.3.1 for implementation capabilities for NR intra-band non-contiguous CA within FR1 | 17.2.0 | +| 2021-09 | RAN#93 | R5-215842 | 0248 | 1 | F | Update of A.4.3.2A.3.2 for implementation capabilities for NR intra-band non-contiguous CA within FR2 | 17.2.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2021-09 | RAN#93 | R5-215843 | 0249 | 1 | F | Update of A.4.3.2A.2.1 for implementation capabilities for NR intra-band contiguous CA within FR1 | 17.2.0 | +| 2021-09 | RAN#93 | R5-215844 | 0250 | 1 | F | Update of A.4.3.2A.2.2 for implementation capabilities for NR intra-band contiguous CA within FR2 | 17.2.0 | +| 2021-09 | RAN#93 | R5-215930 | 0229 | 1 | F | Addition of PICs for Mob_Enh TCs | 17.2.0 | +| 2021-09 | RAN#93 | R5-215933 | 0225 | 1 | F | Introduction of UE capabilities for UL full power Tx rel-16 for UL MIMO | 17.2.0 | +| 2021-09 | RAN#93 | R5-215943 | 0231 | 1 | F | Addition of PICs for NR HST TCs | 17.2.0 | +| 2021-09 | RAN#93 | R5-215951 | 0234 | 1 | F | Addition of PICs for URLLC test cases | 17.2.0 | +| 2021-09 | RAN#93 | R5-215961 | 0239 | 1 | B | Introduction of n24 and n99 | 17.2.0 | +| 2021-09 | RAN#93 | R5-215982 | 0235 | 1 | F | Update of PC2 EN-DC configuration into 38.508-2 | 17.2.0 | +| 2021-09 | RAN#93 | R5-216028 | 0224 | 1 | F | Correction to Physical Layer Baseline Implementation Capabilities | 17.2.0 | +| 2021-09 | RAN#93 | R5-216106 | 0251 | 1 | F | Editorial corrections of A.4.3.2B.2.3.1 for inter-band EN-DC within FR1 | 17.2.0 | +| 2021-09 | RAN#93 | R5-216115 | 0219 | 1 | F | Updating UE capabilities for Rel-17 CA,DC,SUL band combinations within FR1 into TS 38.508-2 | 17.2.0 | +| 2021-09 | RAN#93 | R5-216257 | 0223 | 1 | F | Introduction of common implementation conformance statements for Multi configured uplink grants in NR IIoT | 17.2.0 | +| 2021-09 | RAN#93 | R5-216258 | 0253 | 1 | F | Addition of PIC for MIoT SST | 17.2.0 | +| 2021-09 | RAN#93 | R5-216271 | 0254 | 1 | F | Addition of PIC for V2X SST | 17.2.0 | +| 2021-12 | RAN#94 | R5-216465 | 0256 | - | F | Introduction of PC1.5 n79 ICS | 17.3.0 | +| 2021-12 | RAN#94 | R5-216466 | 0257 | - | F | Introduction of PC2 n34 ICS | 17.3.0 | +| 2021-12 | RAN#94 | R5-216467 | 0258 | - | F | Introduction of PC2 n39 ICS | 17.3.0 | +| 2021-12 | RAN#94 | R5-216554 | 0260 | - | F | Addition of Power Class 1.5 implementation capability for n77 and n78 | 17.3.0 | +| 2021-12 | RAN#94 | R5-217009 | 0263 | - | F | Add UE capability for NR MobEnh | 17.3.0 | +| 2021-12 | RAN#94 | R5-217260 | 0269 | - | F | Introduction of 9 new FR1 CA combos | 17.3.0 | +| 2021-12 | RAN#94 | R5-217299 | 0270 | - | F | Addition of physical baseline implementation capabilities for Rel-15 EN-DC configurations | 17.3.0 | +| 2021-12 | RAN#94 | R5-217318 | 0271 | - | F | Addition of ICS for UE type II PMI reporting capability | 17.3.0 | +| 2021-12 | RAN#94 | R5-217352 | 0272 | - | F | Update of A.4.3.1 for implementation capabilities for NR bands | 17.3.0 | +| 2021-12 | RAN#94 | R5-217353 | 0273 | - | F | Update of A.4.3.2A.2 for supported configurations for NR intra-band contiguous CA | 17.3.0 | +| 2021-12 | RAN#94 | R5-217354 | 0274 | - | F | Update of A.4.3.2A.3 for supported configurations for NR intra-band non-contiguous CA | 17.3.0 | +| 2021-12 | RAN#94 | R5-217355 | 0275 | - | F | Update of A.4.3.2A.4 for supported configurations for NR inter-band CA | 17.3.0 | +| 2021-12 | RAN#94 | R5-217356 | 0276 | - | F | Update of A.4.3.2B.2.1 for supported bandwidth classes for intra-band contiguous EN-DC configurations | 17.3.0 | +| 2021-12 | RAN#94 | R5-217357 | 0277 | - | F | Update of A.4.3.2B.2.2 for supported bandwidth classes for intra-band non-contiguous EN-DC configurations | 17.3.0 | +| 2021-12 | RAN#94 | R5-217358 | 0278 | - | F | Update of A.4.3.2B.2.3.1 to A.4.3.2B.2.3.5 for supported inter-band EN-DC configurations within FR1 | 17.3.0 | +| 2021-12 | RAN#94 | R5-217619 | 0281 | - | F | Addition of capabilities for R16 EN-DC FR2 configurations with n260 | 17.3.0 | +| 2021-12 | RAN#94 | R5-217715 | 0283 | - | F | Addition of PICs for NPN | 17.3.0 | +| 2021-12 | RAN#94 | R5-217745 | 0284 | - | F | Updating UE capabilities for Rel-16 DC band combinations within FR1 into TS 38.508-2 | 17.3.0 | +| 2021-12 | RAN#94 | R5-217802 | 0266 | 1 | F | Introduce and update PICs | 17.3.0 | +| 2021-12 | RAN#94 | R5-217889 | 0264 | 1 | F | Addition of NR V2X Capability | 17.3.0 | +| 2021-12 | RAN#94 | R5-218222 | 0279 | 1 | F | Update of A.4.3.2B.2.3.6 to A.4.3.2B.2.3.9 for supported inter-band EN-DC configurations including FR2 | 17.3.0 | +| 2021-12 | RAN#94 | R5-218307 | 0280 | 1 | F | Addition of PICs for enhanced type II CSI | 17.3.0 | +| 2021-12 | RAN#94 | R5-218453 | 0268 | 1 | F | Introduction_of_UE_capabilities_for_new_EN-DC_comb_within_FR1 | 17.3.0 | +| 2022-03 | RAN#95 | R5-220199 | 0289 | - | F | Update Physical Layer Baseline Implementation Capabilities for NE-DC | 17.4.0 | +| 2022-03 | RAN#95 | R5-220205 | 0290 | - | F | Addition of NR CA Physical Layer Baseline Implementation Capabilities for R16 CA_n3A-n41A | 17.4.0 | +| 2022-03 | RAN#95 | R5-220210 | 0291 | - | F | Addition of NR FR1 PC1.5 RF Baseline Implementation Capabilities for n41 | 17.4.0 | +| 2022-03 | RAN#95 | R5-220312 | 0292 | - | F | Introduction of Rel-16 inter-band EN-DC two band configurations within FR1 for physical layer baseline implementation capabilities | 17.4.0 | +| 2022-03 | RAN#95 | R5-220533 | 0293 | - | F | Editorial correction to UE declaration of Bandwidth Class and BCS information | 17.4.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|--------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2022-03 | RAN#95 | R5-220633 | 0294 | - | F | Introduction_of_UE_capabilities_for_new_EN-DC_comb_within_FR1 | 17.4.0 | +| 2022-03 | RAN#95 | R5-220666 | 0295 | - | F | Correction typo for Table A.4.3.2B.2.3.1-3a and Table A.4.3.8-1 | 17.4.0 | +| 2022-03 | RAN#95 | R5-220750 | 0296 | - | F | Correction to PICS for PS TCs | 17.4.0 | +| 2022-03 | RAN#95 | R5-220776 | 0297 | - | F | Update of PC2 DC_8A-n78A Baseline Implementation Capabilities | 17.4.0 | +| 2022-03 | RAN#95 | R5-220850 | 0298 | - | F | Addition of new RACS PICS | 17.4.0 | +| 2022-03 | RAN#95 | R5-220864 | 0299 | - | F | Introducing Rel-17 2 band CA configurations for n24 and n41 to clause A.4.3.2A.4.1 | 17.4.0 | +| 2022-03 | RAN#95 | R5-220865 | 0300 | - | F | Introducing Rel-17 2 band CA configurations for n24 and n48 to clause A.4.3.2A.4.1 | 17.4.0 | +| 2022-03 | RAN#95 | R5-220866 | 0301 | - | F | Introducing Rel-17 2 band CA configurations for n24 and n77 to clause A.4.3.2A.4.1 | 17.4.0 | +| 2022-03 | RAN#95 | R5-220973 | 0303 | - | F | Addition of physical baseline implementation capabilities for Rel-16 EN-DC configurations | 17.4.0 | +| 2022-03 | RAN#95 | R5-221005 | 0305 | - | F | Addition of PICs for FR2 CSI-RS based RLM | 17.4.0 | +| 2022-03 | RAN#95 | R5-221006 | 0306 | - | F | UE capabilities for completed NR CA configurations CA_n5A-n7A, CA_n5A-n78A and CA_n7A-n78A | 17.4.0 | +| 2022-03 | RAN#95 | R5-221047 | 0307 | - | F | Addition of A.4.3.2B.2.3.7 for DC_3A-42D_n257A and DC_3A-42E_n257A | 17.4.0 | +| 2022-03 | RAN#95 | R5-221054 | 0308 | - | F | Correction of A.4.3.2B.2 for intra-band contiguous and non-contiguous EN-DC | 17.4.0 | +| 2022-03 | RAN#95 | R5-221055 | 0309 | - | F | Correction of A.4.3.2B.2.3.4 for supported inter-band EN-DC configurations within FR1 | 17.4.0 | +| 2022-03 | RAN#95 | R5-221056 | 0310 | - | F | Removal of supported BCS for inter-band EN-DC configurations including FR1 and FR2 | 17.4.0 | +| 2022-03 | RAN#95 | R5-221057 | 0311 | - | F | Removal of supported BCS for inter-band EN-DC configurations including FR2 | 17.4.0 | +| 2022-03 | RAN#95 | R5-221058 | 0312 | - | F | Removal of supported BCS for inter-band EN-DC configurations within FR1 | 17.4.0 | +| 2022-03 | RAN#95 | R5-221330 | 0317 | - | F | Introduction of UE capabilities for Rel-17 EN-DC configurations | 17.4.0 | +| 2022-03 | RAN#95 | R5-221427 | 0287 | 1 | F | Introduction of common implementation conformance statements for NE-DC | 17.4.0 | +| 2022-03 | RAN#95 | R5-221428 | 0315 | 1 | F | Introduce and update PICS | 17.4.0 | +| 2022-03 | RAN#95 | R5-221585 | 0314 | 1 | F | Addition of new PICS for URLLC | 17.4.0 | +| 2022-03 | RAN#95 | R5-221673 | 0285 | 1 | F | Addition of PICS for frequencyShift7p5khz | 17.4.0 | +| 2022-03 | RAN#95 | R5-221674 | 0313 | 1 | F | Update of A.4.3.9 for Additional capabilities for UE declared capability | 17.4.0 | +| 2022-03 | RAN#95 | R5-221793 | 0316 | 1 | F | Addition of Condition for FR1 DL Interruptions test cases applicability | 17.4.0 | +| 2022-03 | RAN#95 | R5-221830 | 0304 | 1 | F | Addition of physical implementation capability for L1-SINR measurement | 17.4.0 | +| 2022-03 | RAN#95 | R5-221853 | 0286 | 1 | F | Addition of UE capability for maximum number of activated TCI states | 17.4.0 | +| 2022-03 | RAN#95 | R5-221875 | 0288 | 1 | F | Introduction of new R17 NR inter-band CA configurations in FR1 | 17.4.0 | +| 2022-03 | RAN#95 | R5-221876 | 0302 | 1 | F | Addition of applicability tables of several NR CA combinations to FR1 inter-band configurations | 17.4.0 | +| 2022-03 | RAN#95 | R5-221911 | 0318 | 1 | F | Add_UE_capability_enhancedUL-TransientPeriod | 17.4.0 | +| 2022-06 | RAN#96 | R5-222266 | 0320 | - | F | Addition of new PICS for 3GPP PS Data off | 17.5.0 | +| 2022-06 | RAN#96 | R5-222284 | 0321 | - | F | Introduction of Rel-16 inter-band EN-DC three band configurations within FR1 for physical layer baseline implementation capabilities | 17.5.0 | +| 2022-06 | RAN#96 | R5-222459 | 0322 | - | F | Addition of UE capability for NSSRG | 17.5.0 | +| 2022-06 | RAN#96 | R5-222573 | 0323 | - | F | Addition of CA_n29A-n71A applicability | 17.5.0 | +| 2022-06 | RAN#96 | R5-222618 | 0324 | - | F | Addition of PICS for NR SL Demod TCs | 17.5.0 | +| 2022-06 | RAN#96 | R5-222695 | 0326 | - | F | Addition of table for NR UL MIMO Capabilities | 17.5.0 | +| 2022-06 | RAN#96 | R5-222817 | 0327 | - | F | Add PICS for PUCCH Scell | 17.5.0 | +| 2022-06 | RAN#96 | R5-222827 | 0328 | - | F | Add PICS for RedCap test | 17.5.0 | +| 2022-06 | RAN#96 | R5-222877 | 0329 | - | F | Limiting MBR relaxation reporting to Rel-15 only | 17.5.0 | +| 2022-06 | RAN#96 | R5-222950 | 0332 | - | F | Introduce and update PICS | 17.5.0 | +| 2022-06 | RAN#96 | R5-223046 | 0334 | - | F | Update of ICS baseline for CA configurations | 17.5.0 | +| 2022-06 | RAN#96 | R5-223105 | 0336 | - | F | Add PICS for MBS test | 17.5.0 | +| 2022-06 | RAN#96 | R5-223127 | 0338 | - | F | Introducing R17 band configuration DC_20A_n257A | 17.5.0 | +| 2022-06 | RAN#96 | R5-223157 | 0339 | - | F | Introduction of UE capabilities for additional Rel-17 EN-DC configurations with PC2 band | 17.5.0 | +| 2022-06 | RAN#96 | R5-223164 | 0341 | - | F | Introduction of UE capabilities for 3 band EN-DC configurations | 17.5.0 | +| 2022-06 | RAN#96 | R5-223212 | 0343 | - | F | Introduction of UE capabilities for additional Rel-17 NR CA and EN- | 17.5.0 | + +| | | | | | | | | +|--|--|--|--|--|--|-------------------|--| +| | | | | | | DC configurations | | +|--|--|--|--|--|--|-------------------|--| + +| | | | | | | | | +|---------|--------|-----------|------|---|---|---------------------------------------------------------------------------------------------------------------------|--------| +| 2022-06 | RAN#96 | R5-223253 | 0348 | - | F | Correction pc_dynamicPowerSharing to align with 38.306 | 17.5.0 | +| 2022-06 | RAN#96 | R5-223301 | 0350 | - | F | Removal of redundant condition for FR1 DL Interruptions test cases applicability | 17.5.0 | +| 2022-06 | RAN#96 | R5-223401 | 0333 | 1 | F | Addition of Measurement Capabilities for Idle/Inactive measurements testcase | 17.5.0 | +| 2022-06 | RAN#96 | R5-223654 | 0337 | 1 | F | Introduction of UE capabilities for 2 band EN-DC configurations | 17.5.0 | +| 2022-06 | RAN#96 | R5-223721 | 0325 | 1 | F | Addition of PICS for NR HST RRM TCs | 17.5.0 | +| 2022-06 | RAN#96 | R5-223733 | 0335 | 1 | F | Addition of UE capabilities for Rel-17 NR inter-band EN-DC configurations including n1 | 17.5.0 | +| 2022-06 | RAN#96 | R5-223772 | 0340 | 1 | F | Addition of PICS for TxD | 17.5.0 | +| 2022-06 | RAN#96 | R5-223797 | 0319 | 1 | F | Alignment of EN-DC Physical Layer Baseline Implementation Capabilities with 38.521-3 | 17.5.0 | +| 2022-06 | RAN#96 | R5-223798 | 0344 | 1 | F | Correction to A.4.3.2C for NR SUL physical layer baseline implementation capabilities | 17.5.0 | +| 2022-06 | RAN#96 | R5-223799 | 0345 | 1 | F | Editorial correction to A.4.3.1 for RF baseline implementation capabilities | 17.5.0 | +| 2022-06 | RAN#96 | R5-223800 | 0346 | 1 | F | Editorial correction to A.4.3.9 for Additional capabilities for UE declared capability | 17.5.0 | +| 2022-06 | RAN#96 | R5-223801 | 0347 | 1 | F | Update to A.4.1 for addition of inter-band NE-DC within FR1 for NSA DC UE radio technologies | 17.5.0 | +| 2022-09 | RAN#97 | R5-223988 | 0351 | - | F | Update of A.4.3.2B.2.0 for EN-DC capabilities | 17.6.0 | +| 2022-09 | RAN#97 | R5-224178 | 0354 | - | F | Introduction of configurations for Inter-band NR-DC within FR1 | 17.6.0 | +| 2022-09 | RAN#97 | R5-224267 | 0359 | - | F | Add UE new message 3 repetition implementation capability | 17.6.0 | +| 2022-09 | RAN#97 | R5-224272 | 0360 | - | F | Introduction of PC2 inter-band CA ICS for UL CA_n1A-n78A | 17.6.0 | +| 2022-09 | RAN#97 | R5-224288 | 0361 | - | F | Addition of PICS for NR Multi-SIM devices | 17.6.0 | +| 2022-09 | RAN#97 | R5-224331 | 0362 | - | F | Addition of new PICS for SDT feature | 17.6.0 | +| 2022-09 | RAN#97 | R5-224593 | 0368 | - | F | Addition of UE capability for slice based cell reselection | 17.6.0 | +| 2022-09 | RAN#97 | R5-224833 | 0371 | - | F | Addition of PC2 PICS for CA_41C | 17.6.0 | +| 2022-09 | RAN#97 | R5-225041 | 0377 | - | F | Update description for release column | 17.6.0 | +| 2022-09 | RAN#97 | R5-225055 | 0378 | - | F | Addition of 4Rx ICS Capability to FDD band n8 | 17.6.0 | +| 2022-09 | RAN#97 | R5-225187 | 0379 | - | F | Addition of PICS for CLI test cases | 17.6.0 | +| 2022-09 | RAN#97 | R5-225242 | 0382 | - | F | Update of RF Baseline Implementation Capabilities for PC2 UE on FDD band | 17.6.0 | +| 2022-09 | RAN#97 | R5-225270 | 0358 | 1 | F | Editorial correction for Table A.4.3.7-1 and Table A.4.4-2 | 17.6.0 | +| 2022-09 | RAN#97 | R5-225301 | 0363 | 1 | F | Addition of PICS for "SNPN Only" UE | 17.6.0 | +| 2022-09 | RAN#97 | R5-225369 | 0365 | 1 | F | Addition of new PICS dl-SchedulingOffset-PDSCH-TypeA | 17.6.0 | +| 2022-09 | RAN#97 | R5-225370 | 0367 | 1 | F | Add PICS for Rel-15 Inter-system mobility between untrusted Non-3GPP and 3GPP system | 17.6.0 | +| 2022-09 | RAN#97 | R5-225371 | 0383 | 1 | F | Addition of PICS for RRC DL segmentation | 17.6.0 | +| 2022-09 | RAN#97 | R5-225685 | 0356 | 1 | F | Update RF Baseline Implementation Capabilities for PC1.5 duty cycle | 17.6.0 | +| 2022-09 | RAN#97 | R5-225688 | 0355 | 1 | F | Update RF Baseline Implementation Capabilities for PC2 duty cycle | 17.6.0 | +| 2022-09 | RAN#97 | R5-225700 | 0353 | 1 | F | Introduction of DC_3A-7A-20A_n8A for physical layer baseline implementation capabilities | 17.6.0 | +| 2022-09 | RAN#97 | R5-225701 | 0366 | 1 | F | Addition of test capability for FR2 EN-DC TX Test Cases 5CC to 7CCs | 17.6.0 | +| 2022-09 | RAN#97 | R5-225717 | 0357 | 1 | F | Removing of n89, n91, n92, n93 and n94 from A.4.3.1 | 17.6.0 | +| 2022-09 | RAN#97 | R5-225732 | 0372 | 1 | F | Addition of applicability statement for many 4CA NR combinations | 17.6.0 | +| 2022-09 | RAN#97 | R5-225767 | 0380 | 1 | F | Update PICS for RedCap UE | 17.6.0 | +| 2022-09 | RAN#97 | R5-225783 | 0375 | 1 | F | Corrections on 2 Rx antenna ports capabilities for band n29 | 17.6.0 | +| 2022-09 | RAN#97 | R5-225840 | 0381 | 1 | F | Introduction of new UE ICS for UPLF test mode | 17.6.0 | +| 2022-12 | RAN#98 | R5-225963 | 0384 | | F | Additional UE declared capabilities for new NR bands n91, n92, n93 and n94 | 17.7.0 | +| 2022-12 | RAN#98 | R5-226399 | 0388 | | F | Updates for NR CA_n2A-n77A, CA_n5A-n77A, CA_n66A-n77A | 17.7.0 | +| 2022-12 | RAN#98 | R5-226625 | 0394 | | F | Update to Table A.4.3.2A.4.1-4: Inter-band CA within FR1 (two bands) PC2 UE RF Baseline Implementation Capabilities | 17.7.0 | +| 2022-12 | RAN#98 | R5-226740 | 0398 | | F | Clean-up pending bands for R15 configurations | 17.7.0 | +| 2022-12 | RAN#98 | R5-226741 | 0399 | | F | Clean-up pending bands for R16 configurations | 17.7.0 | +| 2022-12 | RAN#98 | R5-226847 | 0404 | | F | Introducing SUL bands into NR FR1 UL MIMO Capabilities table | 17.7.0 | +| 2022-12 | RAN#98 | R5-227276 | 0414 | | F | Introduction of CA_n48A-n77A and CA_n71A-n77A baseline capabilities | 17.7.0 | +| 2022-12 | RAN#98 | R5-227336 | 0417 | | F | Updates to SET UL Message PICS | 17.7.0 | +| 2022-12 | RAN#98 | R5-227411 | 0387 | 1 | F | Addition of PICS for R15 SON_MDT | 17.7.0 | + +| | | | | | | | | +|---------|---------|-----------|------|---|---|--------------------------------------------------------------------------------------------------------------------|--------| +| 2022-12 | RAN#98 | R5-227450 | 0391 | 1 | F | Addition of PICS for SNPN UEs supporting access identities definition | 17.7.0 | +| 2022-12 | RAN#98 | R5-227472 | 0409 | 1 | F | Addition of ethernet DNN-APN configuration set to PICS for EHC in 38.508-2 | 17.7.0 | +| 2022-12 | RAN#98 | R5-227475 | 0418 | | F | Addition of MAC implementation capabilities | 17.7.0 | +| 2022-12 | RAN#98 | R5-227481 | 0390 | 1 | F | Addition of new PICS for NTN feature | 17.7.0 | +| 2022-12 | RAN#98 | R5-227500 | 0413 | 1 | F | Addition of PICS for UE power saving enhancements | 17.7.0 | +| 2022-12 | RAN#98 | R5-227513 | 0411 | 1 | F | Addition of PICS for MBS TC | 17.7.0 | +| 2022-12 | RAN#98 | R5-227521 | 0405 | 1 | F | Addition of RedCap capabilities | 17.7.0 | +| 2022-12 | RAN#98 | R5-227548 | 0393 | 1 | F | Addition of PICS for support of (re-)configuration of an SCG during the resume procedure | 17.7.0 | +| 2022-12 | RAN#98 | R5-227549 | 0410 | 1 | F | Addition of UE capability clauses for idle mode measurements ENDC testcases | 17.7.0 | +| 2022-12 | RAN#98 | R5-227585 | 0415 | 1 | F | Addition of PICS for NR unlicensed | 17.7.0 | +| 2022-12 | RAN#98 | R5-227588 | 0407 | 1 | F | RedCap UE capability for Legacy test cases | 17.7.0 | +| 2022-12 | RAN#98 | R5-227597 | 0401 | 1 | F | Additional ICS for extendedBand-n77-r16 | 17.7.0 | +| 2022-12 | RAN#98 | R5-227598 | 0402 | 1 | F | Additional ICS for extendedBand-n77-2-r17 | 17.7.0 | +| 2022-12 | RAN#98 | R5-227603 | 0389 | 1 | F | Addition of test capability for PDCP UDC | 17.7.0 | +| 2022-12 | RAN#98 | R5-227707 | 0396 | 1 | F | Addition of PICS for NR-U | 17.7.0 | +| 2022-12 | RAN#98 | R5-227708 | 0395 | 1 | F | Addition of PICS for Redcap CSI test cases | 17.7.0 | +| 2022-12 | RAN#98 | R5-227709 | 0397 | 1 | F | Addition of DL1024QAM PICS | 17.7.0 | +| 2022-12 | RAN#98 | R5-227710 | 0386 | 1 | F | Addition of common ICS in A.4.3.11 for Rel-17 HST enh | 17.7.0 | +| 2022-12 | RAN#98 | R5-227893 | 0406 | 1 | F | Applicability for new Rel-16 FR2 RF requirements enhancements test cases | 17.7.0 | +| 2022-12 | RAN#98 | R5-227894 | 0385 | 1 | F | Addition of PICS for RedCap RRM TCs | 17.7.0 | +| 2023-03 | RAN#99 | R5-230077 | 0419 | - | F | Adding NR bands n100, n101 into RF Baseline Implementation Capabilities | 17.8.0 | +| 2023-03 | RAN#99 | R5-230078 | 0420 | - | F | Additional UE declared capabilities for new NR bands n100, n101 | 17.8.0 | +| 2023-03 | RAN#99 | R5-230097 | 0421 | - | F | Clean-up mislabeling of FDD bands as TDD bands | 17.8.0 | +| 2023-03 | RAN#99 | R5-230342 | 0429 | - | F | Addition of test capability for PDCP UDC | 17.8.0 | +| 2023-03 | RAN#99 | R5-230647 | 0432 | - | F | Update the pc_maxNumberMIMO_LayersPD SCH | 17.8.0 | +| 2023-03 | RAN#99 | R5-230775 | 0437 | - | F | Update to BWP adaptation PICS | 17.8.0 | +| 2023-03 | RAN#99 | R5-230803 | 0439 | - | F | Editorial correction to pics naming convention | 17.8.0 | +| 2023-03 | RAN#99 | R5-230891 | 0442 | - | F | Update for 38.508-2 for DC_71A_n66A and DC_12A_n2A | 17.8.0 | +| 2023-03 | RAN#99 | R5-231024 | 0445 | - | F | Addition of PICS for measurement gap enhancements | 17.8.0 | +| 2023-03 | RAN#99 | R5-231270 | 0447 | - | F | Addition of new PICS for RAN enhancements for NR Slicing | 17.8.0 | +| 2023-03 | RAN#99 | R5-231401 | 0436 | 1 | F | Add Handover Capabilities for 5GC-N3IWF | 17.8.0 | +| 2023-03 | RAN#99 | R5-231441 | 0426 | 1 | F | Addition of PICS for support of multiple CEF reports | 17.8.0 | +| 2023-03 | RAN#99 | R5-231458 | 0422 | 1 | F | Addition of PICS for ATSSS devices | 17.8.0 | +| 2023-03 | RAN#99 | R5-231473 | 0431 | 1 | F | Addition of PICS for MBS TC | 17.8.0 | +| 2023-03 | RAN#99 | R5-231513 | 0433 | 1 | F | Addition of PICS for NR MUSIM RRC features | 17.8.0 | +| 2023-03 | RAN#99 | R5-231525 | 0434 | 1 | F | Addition of Rel-17 IIoT_ URLLC capabilities | 17.8.0 | +| 2023-03 | RAN#99 | R5-231558 | 0430 | 1 | F | Addition of UE capability for IDC mechanism and early measurements | 17.8.0 | +| 2023-03 | RAN#99 | R5-231572 | 0435 | 1 | F | Add Measurement Capabilities for SFTD | 17.8.0 | +| 2023-03 | RAN#99 | R5-231586 | 0449 | 1 | F | Addition of PICS for RedCap UE | 17.8.0 | +| 2023-03 | RAN#99 | R5-231605 | 0428 | 1 | F | Addition of UE capability for new EN-DC comb within FR1 | 17.8.0 | +| 2023-03 | RAN#99 | R5-231606 | 0427 | 1 | F | Addition of UE capability for new 3CC EN-DC comb within FR1 | 17.8.0 | +| 2023-03 | RAN#99 | R5-231607 | 0438 | 1 | F | Adding n259 to Optional 4x2 PC3 Antenna Array Configuration | 17.8.0 | +| 2023-03 | RAN#99 | R5-231635 | 0425 | 1 | F | Introduction of CA_n41A-n66A. | 17.8.0 | +| 2023-03 | RAN#99 | R5-231636 | 0446 | 1 | F | Introduction of CA_n41A-n71A. | 17.8.0 | +| 2023-03 | RAN#99 | R5-231777 | 0424 | 1 | F | CR on Optional 6x6 PC5 Antenna Array Configuration | 17.8.0 | +| 2023-03 | RAN#99 | R5-231797 | 0441 | 1 | F | Update for 38.508-2 for DC_71A_n2A | 17.8.0 | +| 2023-03 | RAN#99 | R5-231853 | 0440 | 1 | F | Addition of NR-U capabilities | 17.8.0 | +| 2023-03 | RAN#99 | R5-231974 | 0444 | 2 | F | Introduction of informative Annex for status of NR bands, and NR CA, NR-DC, EN-DC, NE-DC and NR SUL configurations | 17.8.0 | +| 2023-03 | RAN#99 | R5-231974 | 0444 | 2 | F | added attachment "PRD21 5G NR bands and CADC configurations list v1.4.0" | 17.8.1 | +| 2023-06 | RAN#100 | R5-232058 | 0450 | - | F | Correction to DAPS PICS | 17.9.0 | +| 2023-06 | RAN#100 | R5-232108 | 0451 | - | F | Introduction of CA_n28A-n78A for physical layer baseline implementation capabilities | 17.9.0 | +| 2023-06 | RAN#100 | R5-232189 | 0452 | - | F | Addition of new PICS for Enhancement of data collection for | 17.9.0 | + +| | | | | | | | | +|--|--|--|--|--|--|--------------------------|--| +| | | | | | | SON/MDT in NR standalone | | +|--|--|--|--|--|--|--------------------------|--| + +| | | | | | | | | +|---------|---------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------|---------| +| 2023-06 | RAN#100 | R5-232238 | 0453 | - | F | Addition and support of power class 6 UEs for HST FR2 | 17.9.0 | +| 2023-06 | RAN#100 | R5-232239 | 0454 | - | F | Update inter-band NR CA 3DL configurations of CA_n2A-n5A-n77A, CA_n2A-n66A-n77A, and CA_n5A-n66A-n77A | 17.9.0 | +| 2023-06 | RAN#100 | R5-232320 | 0456 | - | F | Update of MAC implementation capabilities | 17.9.0 | +| 2023-06 | RAN#100 | R5-232362 | 0457 | - | F | Addition of UE capability for new 2CC and 3CC EN-DC comb within FR2 | 17.9.0 | +| 2023-06 | RAN#100 | R5-232363 | 0458 | - | F | Addition of UE capability for new EN-DC comb within FR2 | 17.9.0 | +| 2023-06 | RAN#100 | R5-232498 | 0460 | - | F | Addition of PICS for NR cov enh SIG TCs | 17.9.0 | +| 2023-06 | RAN#100 | R5-232624 | 0461 | - | F | Update 38.508-2 for CA_n2A-n5A and CA_n2A-n48A | 17.9.0 | +| 2023-06 | RAN#100 | R5-232655 | 0462 | - | F | Update of ICS baseline for CA_n3A-n8A | 17.9.0 | +| 2023-06 | RAN#100 | R5-232731 | 0464 | - | F | Addition of NR FR1 bands with UL MIMO capabilities | 17.9.0 | +| 2023-06 | RAN#100 | R5-232793 | 0466 | - | F | Addition of CA_n39A-n41A RF Baseline Implementation Capabilities | 17.9.0 | +| 2023-06 | RAN#100 | R5-232798 | 0468 | - | F | Addition of R17 new CA PC3 config RF Baseline Implementation Capabilities | 17.9.0 | +| 2023-06 | RAN#100 | R5-232822 | 0469 | - | F | Update NR band and CADC configs status in ICS Annex B | 17.9.0 | +| 2023-06 | RAN#100 | R5-232837 | 0470 | - | F | Adding ICS for UE MMSE-IRC receiver capability | 17.9.0 | +| 2023-06 | RAN#100 | R5-232875 | 0472 | - | F | Introduction of CA_n5A-n66A and CA_n41A-n66A-n71A. | 17.9.0 | +| 2023-06 | RAN#100 | R5-232929 | 0474 | - | F | Capability of REL17 Relaxed measurements in IDLE for RedCap | 17.9.0 | +| 2023-06 | RAN#100 | R5-232947 | 0475 | - | F | Addition of PICS for MBS TC | 17.9.0 | +| 2023-06 | RAN#100 | R5-232965 | 0476 | - | F | Add PICS for EPS UPIP | 17.9.0 | +| 2023-06 | RAN#100 | R5-233031 | 0477 | - | F | Adding PICS for enhanced beam correspondence | 17.9.0 | +| 2023-06 | RAN#100 | R5-233034 | 0478 | - | F | Adding PICS of PC7 | 17.9.0 | +| 2023-06 | RAN#100 | R5-233054 | 0480 | - | F | Addition of PICS for NR feMIMO test cases | 17.9.0 | +| 2023-06 | RAN#100 | R5-233188 | 0481 | - | F | Editorial correction to Table A.4.3.2A.2.1-4 | 17.9.0 | +| 2023-06 | RAN#100 | R5-233189 | 0482 | - | F | Additional support value to maxNumberSRS-Ports-PerResource element | 17.9.0 | +| 2023-06 | RAN#100 | R5-233202 | 0483 | - | F | Addition of PICS for UE support of Uncrewed Aerial Systems | 17.9.0 | +| 2023-06 | RAN#100 | R5-233320 | 0463 | 1 | F | Addition of PICS for support of mpsPriorityIndication on RRC release with redirect | 17.9.0 | +| 2023-06 | RAN#100 | R5-233471 | 0459 | 1 | F | Addition of PICS for Rel-17 eNPN | 17.9.0 | +| 2023-06 | RAN#100 | R5-233502 | 0479 | 1 | F | Adding PICS for DL interruption | 17.9.0 | +| 2023-06 | RAN#100 | R5-233505 | 0471 | 1 | F | Addition of PICS for CLI test case | 17.9.0 | +| 2023-06 | RAN#100 | R5-233508 | 0455 | 1 | F | Update inter-band NR CA PC2 configurations of CA_n2A-n77A, CA_n5A-n77A, and CA_n66A-n77A | 17.9.0 | +| 2023-06 | RAN#100 | R5-233509 | 0467 | 1 | F | Addition of R17 new CA PC2 configs RF Baseline Implementation Capabilities | 17.9.0 | +| 2023-06 | RAN#100 | R5-233529 | 0465 | 2 | F | Update of physical layer baseline capabilities for CA_n28A-n78A | 17.9.0 | +| 2023-06 | RAN#100 | R5-233735 | 0473 | 2 | F | Update of Table A.4.3.2B.2.3.2-2 and A.4.3.2B.2.3.3-2 for new 3/4 band EN-DC comb | 17.9.0 | +| 2023-09 | RAN#101 | R5-233904 | 0486 | - | F | Addition of PICS for MUSIM Test Function | 17.10.0 | +| 2023-09 | RAN#101 | R5-233945 | 0487 | - | F | Introduction of CA_n20A-n78A for physical layer baseline implementation capabilities | 17.10.0 | +| 2023-09 | RAN#101 | R5-233964 | 0488 | - | F | Adding RF Baseline Implementation Capabilities for the new NR band n13 | 17.10.0 | +| 2023-09 | RAN#101 | R5-234009 | 0490 | - | F | Addition of PICS for Rel-16 SPS test cases | 17.10.0 | +| 2023-09 | RAN#101 | R5-234053 | 0491 | - | F | Update baseline capability for DC_48A_n46A | 17.10.0 | +| 2023-09 | RAN#101 | R5-234077 | 0492 | - | F | Addition of UE capability for new EN-DC combos within FR2 | 17.10.0 | +| 2023-09 | RAN#101 | R5-234103 | 0493 | - | F | New Additional information for MDT enhance | 17.10.0 | +| 2023-09 | RAN#101 | R5-234193 | 0495 | - | F | Update for inter-band NR CA_n2A-n66A | 17.10.0 | +| 2023-09 | RAN#101 | R5-234195 | 0496 | - | F | Update inter-band NR CA 3DL configurations with additional band combos | 17.10.0 | +| 2023-09 | RAN#101 | R5-234202 | 0497 | - | F | Update inter-band NR CA PC2 3DL 2UL configurations | 17.10.0 | +| 2023-09 | RAN#101 | R5-234336 | 0502 | - | F | Addition of HighSpeedMeasFlagFR2-r17 UE capability for PC6 devices | 17.10.0 | +| 2023-09 | RAN#101 | R5-234426 | 0505 | - | F | Addition of PICS for RRM enh TCs | 17.10.0 | +| 2023-09 | RAN#101 | R5-234448 | 0506 | - | F | Addition of several NR CA combos to supported configurations tables | 17.10.0 | +| 2023-09 | RAN#101 | R5-234461 | 0507 | - | F | Add pics for MBS new TC. | 17.10.0 | +| 2023-09 | RAN#101 | R5-234478 | 0508 | - | F | Add new pics for the capability of transmission two PUCCH formats in TDM in the same slot | 17.10.0 | +| 2023-09 | RAN#101 | R5-234479 | 0509 | - | F | Add new pics for PDU session authentication and authorization using EAP_AKA_Prime | 17.10.0 | +| 2023-09 | RAN#101 | R5-234504 | 0510 | - | F | Addition of R17 new EN-DC PC2 config RF Baseline Implementation | 17.10.0 | + +| | | | | | | | | +|--|--|--|--|--|--|----------------------------|--| +| | | | | | | Capability for DC_28A_n78A | | +|--|--|--|--|--|--|----------------------------|--| + +| | | | | | | | | +|---------|---------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------------------------------------------------|---------| +| 2023-09 | RAN#101 | R5-234633 | 0511 | - | F | Introduction of UE capabilities for additional Rel-17 EN-DC configurations with PC2 band | 17.10.0 | +| 2023-09 | RAN#101 | R5-234691 | 0514 | - | F | Update of A.4.3.2B.2.3 for new EN-DC capabilities within FR1 | 17.10.0 | +| 2023-09 | RAN#101 | R5-234785 | 0520 | - | F | Addition of PICS indication for simultaneous RxTx capability | 17.10.0 | +| 2023-09 | RAN#101 | R5-235281 | 0484 | 1 | F | Correction of Annex A | 17.10.0 | +| 2023-09 | RAN#101 | R5-235339 | 0485 | 1 | F | Addition of PICS for NTN test cases | 17.10.0 | +| 2023-09 | RAN#101 | R5-235358 | 0527 | - | F | Addition of PICS of Emergency Services and PLMN access in SNPN mode for Rel-17 eNPN | 17.10.0 | +| 2023-09 | RAN#101 | R5-235374 | 0515 | 1 | F | Addition of Sidelink Capabilities for NR sidelink U2N Relay | 17.10.0 | +| 2023-09 | RAN#101 | R5-235608 | 0501 | 1 | F | Addition of UE capability for CA_n28A-n77A | 17.10.0 | +| 2023-09 | RAN#101 | R5-235609 | 0525 | 1 | F | Corrections on notation for SUL Physical Layer Baseline Implementation Capabilities | 17.10.0 | +| 2023-09 | RAN#101 | R5-235610 | 0513 | 1 | F | Addition of PICS for Shared Spectrum | 17.10.0 | +| 2023-09 | RAN#101 | R5-235611 | 0521 | 1 | F | Addition of PICS for unified TCI state switch delay | 17.10.0 | +| 2023-09 | RAN#101 | R5-235612 | 0526 | 1 | F | Introduction Rel-17 Relaxed measurements capabilities for power saving enhancement | 17.10.0 | +| 2023-09 | RAN#101 | R5-235613 | 0522 | 1 | F | Addition of PICS for 2Tx switching | 17.10.0 | +| 2023-09 | RAN#101 | R5-235614 | 0503 | 1 | F | Addition of UE capability indicating supporting aperiodic CSI-RS for tracking for fast SCell activation and conditional PSCell addition in ENDC | 17.10.0 | +| 2023-09 | RAN#101 | R5-235615 | 0500 | 1 | F | Addition of UE capability for CA_n3A-n77A | 17.10.0 | +| 2023-09 | RAN#101 | R5-235616 | 0518 | 1 | F | Update NR band and CADC configs status in ICS Annex B | 17.10.0 | +| 2023-09 | RAN#101 | R5-235845 | 0519 | 1 | F | Addition of UE capability indicating support of simultaneous transmission and reception in TDD-TDD and TDD-FDD inter-band NR CA | 17.10.0 | +| 2023-09 | RAN#101 | R5-235846 | 0504 | 1 | F | Editorial updates to 38.508-2 tables | 17.10.0 | +| 2023-09 | RAN#101 | R5-234293 | 0499 | - | F | Addition of R18 new NR-CA PC2 configs RF Baseline Implementation Capabilities | 18.0.0 | +| 2023-09 | RAN#101 | R5-234741 | 0516 | - | F | Addition of PC1.5 n34 and n40 ICS | 18.0.0 | +| 2023-09 | RAN#101 | R5-234752 | 0517 | - | F | Deletion of NonCB ICS | 18.0.0 | +| 2023-09 | RAN#101 | R5-235120 | 0524 | - | F | Addition of n8 with UL MIMO capabilities | 18.0.0 | +| 2023-09 | RAN#101 | R5-235607 | 0498 | 1 | F | Addition of R18 new NR-DC PC2 configs RF Baseline Implementation Capabilities | 18.0.0 | +| 2023-12 | RAN#102 | R5-236090 | 0532 | | F | Introduction of railway bands n100 and n101 PC1 for physical layer baseline implementation capabilities | 18.1.0 | +| 2023-12 | RAN#102 | R5-236211 | 0535 | | F | Correction of HighSpeedMeasFlagFR2-r17 UE capability | 18.1.0 | +| 2023-12 | RAN#102 | R5-236301 | 0537 | | F | Renaming of pc_pusch_RepetitionCRC_r17 | 18.1.0 | +| 2023-12 | RAN#102 | R5-236306 | 0538 | | F | Clarification of the UE implementation related PICS | 18.1.0 | +| 2023-12 | RAN#102 | R5-236349 | 0539 | | F | Addition of several EN-DC combos to supported configurations tables | 18.1.0 | +| 2023-12 | RAN#102 | R5-236368 | 0541 | | F | Update additional ENDC inter-band configurations | 18.1.0 | +| 2023-12 | RAN#102 | R5-236375 | 0543 | | F | Update additional NR CA two band configurations | 18.1.0 | +| 2023-12 | RAN#102 | R5-236402 | 0544 | | F | Update of A.4.3.2B.2.3 for new EN-DC capabilities within FR1 | 18.1.0 | +| 2023-12 | RAN#102 | R5-236671 | 0550 | | F | Update NR band and CADC configs status in ICS Annex B | 18.1.0 | +| 2023-12 | RAN#102 | R5-236678 | 0551 | | F | Addition of PICS for RedCap RRM TCs | 18.1.0 | +| 2023-12 | RAN#102 | R5-236787 | 0552 | | F | Addition of PICS for ING_5GS feature | 18.1.0 | +| 2023-12 | RAN#102 | R5-236874 | 0553 | | F | Addition of physical layer baseline capabilities for MR-DC enhancements | 18.1.0 | +| 2023-12 | RAN#102 | R5-236901 | 0554 | | F | Addition of supported intra-band contiguous CA configurations with UL MIMO | 18.1.0 | +| 2023-12 | RAN#102 | R5-236931 | 0555 | | F | Adding new FR2 CA BW class capabilities to A.4.3.2A.3.2 for intra-band contiguous CA | 18.1.0 | +| 2023-12 | RAN#102 | R5-237025 | 0556 | | F | Introduction of measurement with no gap capability | 18.1.0 | +| 2023-12 | RAN#102 | R5-237068 | 0557 | | F | Adding PICS for PC2 UL CA configuration CA_n78C | 18.1.0 | +| 2023-12 | RAN#102 | R5-237134 | 0559 | | F | CR to implement 6x2 Grids | 18.1.0 | +| 2023-12 | RAN#102 | R5-237327 | 0534 | 1 | F | Correction to condition of FR2 PICS | 18.1.0 | +| 2023-12 | RAN#102 | R5-237328 | 0546 | 1 | F | Addition of new PICS for MICO mode support | 18.1.0 | +| 2023-12 | RAN#102 | R5-237329 | 0548 | 1 | F | Correction to PICS for NR mpsPriorityIndication support | 18.1.0 | +| 2023-12 | RAN#102 | R5-237395 | 0533 | 1 | F | Addition of PICS for NR feMIMO test cases | 18.1.0 | +| 2023-12 | RAN#102 | R5-237396 | 0540 | 1 | F | Addition of PICS for SRS partial sounding | 18.1.0 | +| 2023-12 | RAN#102 | R5-237605 | 0545 | 1 | F | Addition of R18 new EN-DC PC2 config RF Baseline Implementation Capability for n78 and n79 | 18.1.0 | +| 2023-12 | RAN#102 | R5-237606 | 0528 | 1 | F | Addition of UE capability for new R16 NR CA configurations | 18.1.0 | + +| | | | | | | | | +|---------|---------|-----------|------|---|---|-----------------------------------------------------------------------------------------------------------------------|--------| +| 2023-12 | RAN#102 | R5-237607 | 0530 | 1 | F | Introduction of CA_n1A-n3A-n28A-n78A for physical layer baseline implementation capabilities | 18.1.0 | +| 2023-12 | RAN#102 | R5-237608 | 0529 | 1 | F | Addition of UE capability for new R17 NR CA configurations | 18.1.0 | +| 2023-12 | RAN#102 | R5-237609 | 0531 | 1 | F | Introduction of CA_n25A-n66A-n77(2A) and CA_n25A-n66A-n78(2A) for physical layer baseline implementation capabilities | 18.1.0 | +| 2023-12 | RAN#102 | R5-237610 | 0542 | 1 | F | Updates for NR CA four band configurations | 18.1.0 | +| 2023-12 | RAN#102 | R5-237611 | 0560 | 1 | F | Addition of parallel measurement gap PICS for NTN | 18.1.0 | +| 2023-12 | RAN#102 | R5-237612 | 0549 | 1 | F | Addition of PC1.5 CA_n41C ICS | 18.1.0 | +| 2023-12 | RAN#102 | R5-237613 | 0561 | 1 | F | Addition of scheduling restrictions PICS | 18.1.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38523-2/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38523-2/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..186fcb1b9980036e006f671fe7c5da89a5d70308 --- /dev/null +++ b/marked/Rel-18/38_series/38523-2/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:66a8d22f98e41630a16620c70a21630e74a292e179c141c3a2b8710b013a6174 +size 9765 diff --git a/marked/Rel-18/38_series/38523-2/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38523-2/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..332864e82faa3d4bcd9405784f5ee0a25a536131 --- /dev/null +++ b/marked/Rel-18/38_series/38523-2/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:703fe17b707f6fcd2eace385e1d776114b8bf171112ac3ac1c07e60910d7bc29 +size 6421 diff --git a/marked/Rel-18/38_series/38523-2/raw.md b/marked/Rel-18/38_series/38523-2/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a436bf7ea4feb21ac5f60d66a428b824be50b845 --- /dev/null +++ b/marked/Rel-18/38_series/38523-2/raw.md @@ -0,0 +1,3050 @@ + + +# 3GPP TS 38.523-2 V18.2.0 (2025-03) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; 5GS; User Equipment (UE) conformance specification; Part 2: Applicability of protocol test cases (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' in smaller letters below the logo. + +3GPP logo + +## --- **Keywords** + +--- + +5GS, UE, terminal, testing + +## **3GPP** + +### --- **Postal address** + +### --- **3GPP support office address** + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + +--- + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2025, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## --- Contents + +| | | +|-----------------------------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions, symbols and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Symbols..... | 6 | +| 3.3 Abbreviations ..... | 6 | +| 4 Recommended Test Case Applicability ..... | 7 | +| 4.0 Introduction ..... | 7 | +| 4.1 Protocol conformance test cases applicability ..... | 8 | +| 4.2 Protocol conformance test cases applicability conditions..... | 68 | +| 4.3 Protocol conformance test cases applicability for Vertical UEs ..... | 84 | +| 4.3.1 SNPN-only UEs..... | 84 | +| Annex A (informative): Rel-16 and later test cases completed for RedCap UEs..... | 88 | +| Annex B (informative): Change history ..... | 89 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +The present document is part 2 of a multi-part deliverable covering the 5G System (5GS) User Equipment (UE) protocol conformance specification, as identified below: + +- 3GPP TS 38.523-1 [2]: "5GS; User Equipment (UE) conformance specification; Part 1: Protocol". +- **3GPP TS 38.523-2: "5GS; User Equipment (UE) conformance specification; Part 2: Applicability of protocol test cases" (the present document).** +- 3GPP TS 38.523-3 [3]: "5GS; User Equipment (UE) conformance specification; Part 3: Protocol Test Suites". + +# 1 Scope + +The present document provides the applicability of protocol test cases proforma for 5G New Radio (NR) User Equipment (UE), in compliance with the relevant requirements. + +The present document specifies the recommended applicability statement for the test cases included in 3GPP TS 38.523-1 [2] and 3GPP TS 38.523-3 [3]. These applicability statements are based on the features implemented in the UE. + +Special conformance testing functions can be found in 3GPP TS 38.509 [5] and 3GPP TS 36.509 [7] and the common test environments are included in 3GPP TS 38.508-1 [4] and 3GPP TS 36.508 [6]. + +The present document is valid for UE implemented according to 3GPP Releases starting from Release 15 up to the Release indicated on the cover page of the present document. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 38.523-1: "5GS; User Equipment (UE) conformance specification; Part 1: Protocol". +- [3] 3GPP TS 38.523-3: "5GS; User Equipment (UE) conformance specification; Part 3: Protocol Test Suites". +- [4] 3GPP TS 38.508-1: "5GS; User Equipment (UE) conformance specification; Part 1: Common test environment". +- [5] 3GPP TS 38.508-2: "5GS; User Equipment (UE) conformance specification; Part 2: Common Implementation Conformance Statement (ICS) proforma". +- [6] 3GPP TS 38.509: "5GS; Special conformance testing functions for User Equipment (UE)". +- [7] 3GPP TS 36.508: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRAN); Common Test Environments for User Equipment (UE) Conformance Testing". +- [8] 3GPP TS 36.509: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Special conformance testing functions for User Equipment (UE)". +- [9] 3GPP TS 34.229-2: "Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); User Equipment (UE) conformance specification; Part 2: Implementation Conformance Statement (ICS) specification". +- [10] 3GPP TS 36.523-2: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRAN); User Equipment (UE) conformance specification; Part 2: Implementation Conformance Statement (ICS) proforma specification". +- [11] 3GPP TS 34.123-2: "User Equipment (UE) conformance specification; Part 2: Implementation Conformance Statement (ICS) proforma specification". + +# 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [5] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [5]. + +**Implementation Conformance Statement (ICS):** statement made by the supplier of an implementation or system claimed to conform to a given specification, stating which capabilities have been implemented + +**ICS proforma:** document, in the form of a questionnaire, which when completed for an implementation or system becomes an ICS + +**Implementation extra Information for Testing (IXIT):** A statement made by a supplier or implementer of an UEUT which contains or references all of the information (in addition to that given in the ICS) related to the UEUT and its testing environment, which will enable the test laboratory to run an appropriate test suite against the UEUT + +**IXIT proforma:** A document, in the form of a questionnaire, which when completed for an UEUT becomes an IXIT + +**Protocol Implementation Conformance Statement (PICS):** An ICS for an implementation or system claimed to conform to a given protocol specification + +**Protocol Implementation extra Information for Testing (PIXIT):** An IXIT related to testing for conformance to a given protocol specification + +**Static conformance review:** A review of the extent to which the static conformance requirements are claimed to be supported by the UEUT, by comparing the answers in the ICS(s) with the static conformance requirements expressed in the relevant specification(s) + +## 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]. + +For the purposes of the present document, the following abbreviations apply: + +| | | +|-------|-------------------------------------------------------| +| FFS | For Further Study | +| ICS | Implementation Conformance Statement | +| IXIT | Implementation extra Information for Testing | +| PICS | Protocol Implementation Conformance Statement | +| PIXIT | Protocol Implementation extra Information for Testing | +| SCS | System Conformance Statement | +| TC | Test Case | +| UEUT | User Equipment Under Test | + +# 4 Recommended Test Case Applicability + +## 4.0 Introduction + +The applicability of each individual test is identified in subclause 4.1. This is just a recommendation based on the purpose for which the test case was written. + +The applicability of every test is formally expressed by the use of Boolean expressions that are based on parameters (ICS). The parameters (ICS) included in TS 38.508-2 [5] are used in the test case applicability condition without reference. Parameters (ICS) specified in 3GPP TS 36.523-2 [10] and 3GPP TS 34.229-2 [9] shall be referred with proper reference. The parameters (ICS) shall be set according to the capabilities of the UE on the operating band / band combination under test. + +Additional information related to the Test Case (TC), e.g. affecting its dynamic behaviour or its execution may be provided as well. + +The columns in subclause 4.1 have the following meaning: + +### Clause + +The clause column indicates the clause number in TS 38.523-1 [2] that contains the test body. + +### Title + +The title column describes the name of the test and contains the clause title of the clause in TS 38.523-1 [2] that contains the test body. + +### Release + +The release column indicates the earliest release from which the test case is applicable. In some specific cases it may indicate the release(s) for which the TC is **only** applicable. + +Note: Some exceptions to this interpretation may be indicated in Notes in column 'Number of TC Executions'. + +### Applicability - Condition + +The following notations are used for the applicability column: + +- | | | +|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| R | recommended - the test case is recommended | +| O | optional – the test case is optional | +| N/A | not applicable - in the given context, the test case is not recommended. | +| C i | conditional - the test is recommended ("R") or not ("N/A") depending on the support of other items. "i" is an integer identifying a unique conditional status expression which is defined immediately following the table. For nested conditional expressions, the syntax "IF ... THEN (IF ... THEN ... ELSE...) ELSE ..." is used to avoid ambiguities. | + +NOTE: The conditions are defined in subclause 4.2. + +### Applicability - Comments + +This column contains a verbal description of the condition. + +### Additional Information - Specific ICS + +This column contains the mnemonics of ICS(s) affecting the dynamic behaviour of the TC. + +### Additional Information - Specific IXIT + +This column contains the mnemonics of IXIT(s) affecting the dynamic behaviour of the TC. + +### Additional Information - Number of TC Executions + +This column contains, wherever applicable, the recommended for certification purposes number of TC executions. It may contain also other information e.g. exceptions to the release applicable to the test. Clarifying notes are listed at the end of the same Table. + +### Additional Information - Release other RAT + +In regard to a particular test case, this column provides information on the release which is used by the simulated network in the other (i.e. non 5GS) RAT(s) where applicable. For each applicable RAT the release shall be indicated in the format 'Rel-X RAT'. When multiple RATs are applicable the entries per RAT shall be separated by a comma. When a value for a 3GPP RAT is not provided but the RAT is in the scope of the test case then for this RAT the release indicated in the Release column applies (per default). + +Note: Void. + +## 4.1 Protocol conformance test cases applicability + +**Table 4.1-1a: Applicability of Protocol conformance Idle mode test cases, ref. TS 38.523-1 [2]** + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-------------------------|------------------------------------------------------------------------------------| +| 6 | Idle mode operations | | | | +| 6.1 | NR idle mode operations | | | | +| 6.1.1 | NG-RAN Only PLMN Selection | | | | +| 6.1.1.1 | PLMN selection of RPLMN, HPLMN/EHPLMN, UPLMN and OPLMN / Automatic mode | Rel-15 | C21 | UEs supporting 5G Core | +| 6.1.1.2 | PLMN selection of "Other PLMN/access technology combinations" / Automatic mode | Rel-15 | C21 | UEs supporting 5G Core | +| 6.1.1.3 | Cell reselection of ePLMN in manual mode | Rel-15 | C21 | UEs supporting 5G Core | +| 6.1.1.4 | PLMN selection in shared network environment / Automatic mode | Rel-15 | C21 | UEs supporting 5G Core | +| 6.1.1.4a | PLMN selection in shared network environment / Automatic mode / Cells broadcasting multiple PLMN IDs with unique TAC's, RAN areas, and cell identities | Rel-15 | C21 | UEs supporting 5G Core | +| 6.1.1.5 | PLMN selection of RPLMN, HPLMN/EHPLMN, UPLMN and OPLMN / Automatic mode / User reselection | Rel-15 | C36 | UEs supporting 5G Core and user initiated PLMN reselection in automatic mode on NR | +| 6.1.1.6 | PLMN selection / Periodic reselection / MinimumPeriodicSearchTimer | Rel-15 | C34 | UEs supporting 5G Core and MinimumPeriodicSearchTimer | +| 6.1.1.7 | PLMN selection of RPLMN or (E)HPLMN; Automatic mode | Rel-15 | C21 | UEs supporting 5G Core | +| 6.1.1.8 | PLMN selection of RPLMN or (E)HPLMN; Manual mode | Rel-15 | C91 | UEs supporting 5G Core and ManualModeNetworkSelectionException | +| 6.1.2 | NG-RAN Only Cell Selection | | | | +| 6.1.2.1 | Cell selection / Qrxlevmin & Cell reselection (Intra NR) | Rel-15 | C21 | UEs supporting 5G Core | +| 6.1.2.2 | Cell selection / Qqualmin / Intra NR / Serving cell becomes non-suitable (Srxlev > 0, Squal < 0) | Rel-15 | C21 | UEs supporting 5G Core | +| 6.1.2.3 | Cell selection / Intra NR / Serving cell becomes non-suitable (S<0, MIB Indicated barred) | Rel-15 | C21 | UEs supporting 5G Core | +| 6.1.2.3a | Intra frequency reselection not allowed | Rel-15 | C21 | UEs supporting 5G Core | +| 6.1.2.4 | Cell reselection for interband operation | Rel-15 | C37 | UEs supporting 5G Core and more than 1 FDD or TDD NR band | +| 6.1.2.5 | Cell reselection for interband operation using Pcompensation / Between FDD and TDD | Rel-15 | C38 | UEs supporting 5G Core and NR FDD and NR TDD | +| 6.1.2.7 | Cell reselection / Equivalent PLMN | Rel-15 | C21 | UEs supporting 5G Core | +| 6.1.2.8 | Cell reselection / Equivalent PLMN / Single Frequency operation | Rel-15 | C21 | UEs supporting 5G Core | +| 6.1.2.9 | Cell reselection using Qhyst, Qoffset and Treselection | Rel-15 | C21 | UEs supporting 5G Core | +| 6.1.2.11 | Area Specific SIBs using systemInformationAreaID | Rel-15 | C21 | UEs supporting 5G Core | + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|--------------|---------------------------------------------------------------------------------------------------------------------------------------------|---------|-------------------------|-----------------------------------------------------------------------------------| +| 6.1.2.12 | Cell reselection using cell status and cell reservations / cellReservedForOtherUse | Rel-15 | C21 | UEs supporting 5G Core | +| 6.1.2.13 | Cell reselection using cell status and cell reservations / Access Identity 0, 1, 2 and 12 to 14 - cellReservedForOperatorUse | Rel-15 | C21 | UEs supporting 5G Core | +| 6.1.2.14 | Cell reselection using cell status and cell reservations / Access Identity 11 or 15 - cellReservedForOperatorUse | Rel-15 | C21 | UEs supporting 5G Core | +| 6.1.2.15 | Cell reselection in shared network environment | Rel-15 | C21 | UEs supporting 5G Core | +| 6.1.2.15a | Cell reselection in shared network environment / Cells broadcasting multiple PLMN IDs with unique TAC's, RAN areas, and cell identities | Rel-15 | C21 | UEs supporting 5G Core | +| 6.1.2.16 | Inter-frequency cell reselection (equal priority) | Rel-15 | C21 | UEs supporting 5G Core | +| 6.1.2.17 | Cell reselection / Cell-specific reselection parameters provided by the network in a neighbouring cell list | Rel-15 | C21 | UEs supporting 5G Core | +| 6.1.2.18 | Cell reselection, Sintrasearch, Snonintrasearch | Rel-15 | C21 | UEs supporting 5G Core | +| 6.1.2.18a | Void | | | | +| 6.1.2.18b | Void | | | | +| 6.1.2.19 | Speed dependent cell reselection | Rel-15 | C21 | UEs supporting 5G Core | +| 6.1.2.20 | Inter-frequency cell reselection according to cell reselection priority provided by SIBs | Rel-15 | C21 | UEs supporting 5G Core | +| 6.1.2.21 | Cell reselection, SIntraSearchQ and SnonIntraSearchQ | Rel-15 | C21 | UEs supporting 5G Core | +| 6.1.2.22 | Inter-frequency cell reselection based on common priority information with parameters ThreshX, HighQ, ThreshX, LowQ and ThreshServing, LowQ | Rel-15 | C21 | UEs supporting 5G Core | +| 6.1.2.23 | Cell reselection / MFBI | Rel-15 | C21 | UEs supporting 5G Core | +| 6.1.2.24 | Slice-based cell reselection / Re-selection priorities provided by SIB16 | Rel-17 | C240 | UEs supporting 5G Core and slice based cell reselection | +| 6.1.2.25 | Slice-based cell reselection / Re-derive reselection priority for frequency | Rel-17 | C240 | UEs supporting 5G Core and slice based cell reselection | +| 6.1.2.26 | Cell Selection / RedCap | Rel-17 | C212 | UEs supporting 5G Core and RedCap | +| 6.1.2.27 | Cell reselection / inter-frequency / RedCap | Rel-17 | C212 | UEs supporting 5G Core and RedCap | +| 6.1.2.28 | Cell selection / NES mode | Rel-18 | C395 | UEs supporting 5G Core and Cell DTX or Cell DRX operation by RRC configuration | +| 6.1.2.29 | Cell Selection / RedCap / halfDuplexRedCapAllowed | Rel-17 | C332 | UEs supporting 5G Core and RedCap and halfDuplexFDD | +| 6.1.2.30 | Cell Selection / RedCap / halfDuplexRedCapAllowed / MFBI | Rel-17 | C332 | UEs supporting 5G Core and RedCap and halfDuplexFDD | +| 6.1.2.31 | Cell reselection / 2Rx XR / Serving cell becomes barred | Rel-18 | C356 | UEs supporting 5G Core and is 2Rx XR UE | +| 6.1.2.32 | Cell reselection / 2Rx XR / Intra frequency reselection not allowed | Rel-18 | C356 | UEs supporting 5G Core and is 2Rx XR UE | +| 6.1.2.33 | Cell reselection / 2Rx XR / Access not allowed | Rel-18 | C356 | UEs supporting 5G Core and is 2Rx XR UE | +| 6.1.2.34 | Cell Selection / eRedCap | Rel-18 | C380 | UEs supporting 5G Core and eRedCap | +| 6.1.2.35 | Cell Selection / eRedCap / emergency call | Rel-18 | C381 | UEs supporting 5G Core and eRedCap and emergency services in NR connected to 5GCN | +| 6.1.2.36 | Cell reselection / inter-frequency / eRedCap | Rel-18 | C380 | UEs supporting 5G Core and eRedCap | +| 6.1.2.37 | Cell Selection / eRedCap / halfDuplexRedCapAllowed | Rel-18 | C402 | UEs supporting 5G Core and eRedCap and halfDuplexFDD | +| 6.1.2.38 | Cell Selection / eRedCap / halfDuplexRedCapAllowed / MFBI | Rel-18 | C402 | UEs supporting 5G Core and eRedCap and halfDuplexFDD | +| 6.2 | Multi-mode environment | | | | +| 6.2.1 | Inter-RAT PLMN selection | | | | +| 6.2.1.1 | Inter-RAT PLMN Selection / Selection of correct RAT for OPLMN / Automatic mode | Rel-15 | C32 | UEs supporting 5G Core and E-UTRA | +| 6.2.1.2 | Inter-RAT PLMN Selection / Selection of correct RAT for UPLMN / Automatic mode | Rel-15 | C32 | UEs supporting 5G Core and E-UTRA | +| 6.2.1.3 | Inter-RAT PLMN Selection / Selection of correct PLMN and RAT in shared network environment / Automatic mode | Rel-15 | C32 | UEs supporting 5G Core and E-UTRA | +| 6.2.1.4 | Inter-RAT PLMN Selection / Selection of correct RAT from the OPLMN list / Manual mode | Rel-15 | C32 | UEs supporting 5G Core and E-UTRA | +| 6.2.1.5 | Inter-RAT Background HPLMN Search / Search for correct RAT for HPLMN / Automatic mode | Rel-15 | C32 | UEs supporting 5G Core and E-UTRA | +| 6.2.2 | Inter-RAT Cell Selection | | | | +| 6.2.2.1 | Inter-RAT cell selection / From NR RRC_IDLE to EUTRA_Idle / Serving cell becomes non-suitable | Rel-15 | C32 | UEs supporting 5G Core and E-UTRA | + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-------------------------|-----------------------------------------------------------------------------------| +| 6.2.2.2 | Inter-RAT cell selection / From E-UTRA_Idle to NR RRC_IDLE / Serving cell becomes non-suitable | Rel-15 | C32 | UEs supporting 5G Core and E-UTRA | +| 6.2.3 | Inter-RAT Cell Reselection | | | | +| 6.2.3.1 | Inter-RAT cell reselection / From E-UTRA_IDLE to NR RRC_IDLE (lower priority & higher priority, Srxlev based) | Rel-15 | C32 | UEs supporting 5G Core and E-UTRA | +| 6.2.3.2 | Inter-RAT cell reselection / From E-UTRA_IDLE to NR RRC_IDLE (lower priority & higher priority, Squal based) | Rel-15 | C32 | UEs supporting 5G Core and E-UTRA | +| 6.2.3.3 | Inter-RAT cell reselection / From NR RRC_IDLE to E-UTRA_IDLE (lower priority & higher priority, Srxlev based) | Rel-15 | C32 | UEs supporting 5G Core and E-UTRA | +| 6.2.3.4 | Inter-RAT cell reselection / From NR RRC_IDLE to E-UTRA_IDLE (lower priority & higher priority, Squal based) | Rel-15 | C32 | UEs supporting 5G Core and E-UTRA | +| 6.2.3.5 | Inter-RAT cell reselection / From NR RRC_IDLE to E-UTRA_IDLE according to RAT priority provided by dedicated signalling (RRRelease) | Rel-15 | C32 | UEs supporting 5G Core and E-UTRA | +| 6.2.3.6 | Inter-RAT cell reselection / From E-UTRA_IDLE to NR RRC_IDLE according to RAT priority provided by dedicated signalling (RRConnRelease) | Rel-15 | C32 | UEs supporting 5G Core and E-UTRA | +| 6.2.3.7 | Inter-RAT cell reselection / From NR RRC_IDLE to E-UTRA RRC_IDLE, Snonintrasearch | Rel-15 | C32 | UEs supporting 5G Core and E-UTRA | +| 6.2.3.8 | Inter-RAT cell reselection / From E-UTRA RRC_IDLE to NR RRC_IDLE, Snonintrasearch | Rel-15 | C32 | UEs supporting 5G Core and E-UTRA | +| 6.2.3.9 | Void | | | | +| 6.2.3.10 | Inter-RAT cell reselection / From E-UTRA_IDLE to NR RRC_IDLE / schedulingInfoList-v12j0 | Rel-15 | C32 | UEs supporting 5G Core and E-UTRA | +| 6.2.3.11 | Inter-RAT cell reselection / From E-UTRA_IDLE to NR RRC_IDLE / schedulingInfoListExt-r12 | Rel-15 | C32 | UEs supporting 5G Core and E-UTRA | +| 6.3 | 5GS Steering of Roaming | | | | +| 6.3.1 | Steering of Roaming | | | | +| 6.3.1.1 | Steering of UE in roaming during registration/security check successful using List Type 1 | Rel-15 | C21 | UEs supporting 5G Core | +| 6.3.1.2 | Steering of UE in roaming during registration/security check successful but SOR Transparent container indicates ACK has been NOT been requested | Rel-15 | C21 | UEs supporting 5G Core | +| 6.3.1.3 | Steering of UE in roaming during registration/security check unsuccessful/Automatic mode | Rel-15 | C21 | UEs supporting 5G Core | +| 6.3.1.4 | Steering of UE in roaming during registration/security check unsuccessful/Manual mode | Rel-15 | C21 | UEs supporting 5G Core | +| 6.3.1.5 | Steering of UE in roaming during registration/UE configured to receive Steering of Roaming information but does not receive Steering of Roaming from Network | Rel-15 | C21 | UEs supporting 5G Core | +| 6.3.1.7 | Steering of UE in roaming during registration/security check unsuccessful but emergency service pending to be activated | Rel-15 | C92 | UEs supporting 5G Core and emergency services in NR connected to 5GCN | +| 6.3.1.8 | Steering of UE in roaming after registration/Automatic PLMN selection mode | Rel-15 | C21 | UEs supporting 5G Core | +| 6.3.1.9 | Steering of UE in roaming after registration/Manual PLMN selection mode | Rel-15 | C21 | UEs supporting 5G Core | +| 6.3.1.10 | Steering of UE in roaming during mobility update registration | Rel-15 | C21 | UEs supporting 5G Core | +| 6.3.2 | Steering of Roaming with using SOR-CMCI | | | | +| 6.3.2.1 | Steering of UE in roaming after registration / SOR-CMCI rule / DNN of the PDU session / DL NAS transport | Rel-17 | C21B | UEs supporting 5G Core and steering of roaming connected mode control information | +| 6.3.2.2 | Steering of UE in roaming after registration / SOR-CMCI rule / MMTEL voice call / DL NAS transport | Rel-17 | C234A | NR and NG.114 and steering of roaming connected mode control information | +| 6.3.2.3 | Steering of UE in roaming after registration / SOR-CMCI rule / match all / DL NAS transport | Rel-17 | C21B | UEs supporting 5G Core and steering of roaming connected mode control information | + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|--------------|---------------------------------------------------------------------------------------------------------------------------------|---------------|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 6.3.2.4 | Steering of UE in roaming after registration / SOR-CMCI rule / DNN of the PDU session / update Tsor-cm Timer / DL NAS transport | Rel-17 | C21B | UEs supporting 5G Core and steering of roaming connected mode control information | +| 6.3.2.5 | Steering of UE in roaming after registration / SOR-CMCI rule / DNN of the PDU session / store SOR-CMCI in ME / DL NAS transport | Rel-17 | C21B | UEs supporting 5G Core and steering of roaming connected mode control information | +| 6.3.2.6 | Steering of UE in roaming after registration / SOR-CMCI rule / match all / Emergency call / DL NAS transport | Rel-17 | C92A | UEs supporting 5G Core and emergency services in NR connected to 5GCN and steering of roaming connected mode control information | +| 6.3 | Steering of Roaming in SNPN | Rel-17 | | | +| 6.3.3.1 | Steering of Roaming in SNPN / During registration / Security check successful / Without SOR Transparent container ACK request | Rel-17 | C338 | UEs supporting 5G Core and access SNPN using credentials assigned by a Credentials Holder separate from the SNPN and steering of roaming SNPN selection information | +| 6.3.3.2 | Steering of Roaming in SNPN / After registration / Security check successful | Rel-17 | C338 | UEs supporting 5G Core and access SNPN using credentials assigned by a Credentials Holder separate from the SNPN and steering of roaming SNPN selection information | +| 6.3.3.3 | Steering of Roaming in SNPN / After registration / SOR-CMCI rule / match all | Rel-17 | C339 | UEs supporting 5G Core and access SNPN using credentials assigned by a Credentials Holder separate from the SNPN and Steering of Roaming Connected Mode Control Information | +| 6.3.3.4 | Steering of Roaming in SNPN / After registration / SOR-CMCI rule / match all / Emergency call | Rel-17 | C340 | UEs supporting 5G Core and access SNPN using credentials assigned by a Credentials Holder separate from the SNPN and emergency services in NR connected to 5GCN in SNPN Access mode and Steering of Roaming Connected Mode Control Information | +| 6.4 | UE Procedures in RRC_INACTIVE state | | | | +| 6.4.1 | NG-RAN Only PLMN Selection in RRC_INACTIVE state | | | | +| 6.4.1.1 | PLMN Selection / Higher priority/HPLMN in Automatic PLMN Selection mode | Rel-15 | C109 | UEs supporting 5G Core and RRC_INACTIVE | +| 6.4.1.2 | Cell reselection of ePLMN in manual mode | Rel-15 | C109 | UEs supporting 5G Core and RRC_INACTIVE | +| 6.4.2 | Cell Selection / Qrxlevmin & Cell Reselection (Intra NR in RRC_INACTIVE state) | | | | +| 6.4.2.1 | Cell Selection / Qrxlevmin & Cell Reselection (Intra NR in RRC_INACTIVE state) | Rel-15 | C109 | UEs supporting 5G Core and RRC_INACTIVE | +| 6.4.2.2 | Inter-frequency cell reselection according to cell reselection priority provided by SIBs in RRC_INACTIVE state | Rel-15 | C109 | UEs supporting 5G Core and RRC_INACTIVE | +| 6.4.2.3 | Slice-based cell reselection in RRC_INACTIVE state / Re-selection priorities provided by SIB16 | Rel-17 | C241 | UEs supporting 5G Core and RRC_INACTIVE and slice based cell reselection | +| 6.4.2.4 | Void | | | | +| 6.4.2.5 | Void | | | | +| 6.4.3 | Inter-RAT Cell Reselection | | | | +| 6.4.3.1 | Inter-RAT cell reselection From NR RRC_INACTIVE to E-UTRA RRC_IDLE (lower priority & higher priority, Srlexv based) | Rel-15 | C110 | UEs supporting 5G Core and E-UTRA and RRC_INACTIVE | +| 6.5 | SNPN and CAG Selection | | | | +| 6.5.1 | SNPN Only Selection | | | | +| 6.5.1.1 | SNPN Selection in Manual Mode | Rel-16 | C131 | UEs supporting 5G Core and SNPN | +| 6.5.1.2 | SNPN Selection in Automatic Mode | Rel-16 | C131 | UEs supporting 5G Core and SNPN | +| 6.5.1.3 | SNPN / User Reselection in Automatic Mode | Rel-16 | C167 | UEs supporting 5G Core and SNPN and user initiated SNPN reselection in automatic mode on NR | +| 6.5.2 | CAG (Closed Access Group) | | | | +| 6.5.2.1 | CAG Selection in Manual Mode | Rel-16 | C132 | UEs supporting 5G Core and CAG | +| 6.5.2.2 | CAG Selection in Automatic Mode | Rel-16 | C132 | UEs supporting 5G Core and CAG | +| 6.5.2.3 | CAG / Limited Service / No Suitable cell | Rel-16 | C132 | UEs supporting 5G Core and CAG | +| 6.5.2.4 | CAG / cell reselection / Within allowed CAG/ non-CAG cell to CAG cell | Rel-16 | C168 | UEs supporting 5G Core and CAG and Autonomous search function on NR | +| 6.5.2.5 | Void | | | | +| 6.5.2.6 | CAG / Cell Reservation | Rel-16 | C132 | UEs supporting 5G Core and CAG | +| 6.5.3 | SNPN Selection | | | | +| 6.5.3.1 | SNPN Selection in Manual Mode / Using credentials from a credentials holder | Rel-17 | C304 | UEs supporting 5G Core and access using credentials assigned by a Credentials Holder separate from the SNPN | +| 6.5.3.2 | SNPN Selection in Manual Mode / Onboarding services in SNPN | Rel-17 | C305 | UEs supporting 5G Core and onboarding services in SNPN | +| 6.5.3.3 | SNPN Selection in Manual Mode / Switch to | Rel-17 | C306 | UEs supporting 5G Core and emergency services | + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|--------------|--------------------------------------------------------------------------------------------------------------|---------|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Automatic Mode | | | in SNPN | +| 6.5.3.4 | SNPN Selection in Automatic Mode / Onboarding services in SNPN | Rel-17 | C305 | UEs supporting 5G Core and onboarding services in SNPN | +| 6.5.3.5 | SNPN Selection in Automatic Mode / Using credentials from a credentials holder | Rel-17 | C304 | UEs supporting 5G Core and accessing SNPN using credentials assigned by a Credentials Holder separate from the SNPN | +| 6.5.3.6 | SNPN / Limited service / No valid subscriber data | Rel-17 | C305 | UEs supporting 5G Core and Onboarding SNPN (hence supports Default UE Credentials) | +| 6.5.3.7 | SNPN / User Reselection in Automatic Mode / Using credentials from a credentials holder | Rel-17 | C307 | UEs supporting 5G Core and accessing SNPN using credentials from a Credentials Holder and user initiated SNPN reselection in automatic mode on NR | +| 6.5.3.8 | SNPN / cell reselection for IMS emergency services | Rel-17 | C306 | UEs supporting 5G Core and emergency services in NR connected to 5GCN in SNPN Access mode | +| 6.5.3.9 | SNPN / cell reselection / SNPN to PLMN | Rel-17 | C308 | UEs supporting 5G Core and PLMN access in SNPN Access mode and emergency services in NR connected to 5GCN in SNPN Access mode And IMS voice over NR | +| 6.5.3.10 | SNPN Selection in Automatic Mode / Selecting equivalent SNPN | Rel-18 | C413 | UEs supporting 5G Core and SNPN and equivalent SNPNs for cell (re)selection | +| 6.6 | NR Shared Spectrum idle mode operations | | | | +| 6.6.1 | NR Shared Spectrum cell selection | | | | +| 6.6.1.1 | Cell selection / next strongest cell / Intra frequency reselection not allowed | Rel-16 | C217 | UEs supporting 5G Core and NR standalone shared spectrum channel access | +| 6.6.1.2 | Cell selection / next strongest cell / Intra frequency reselection not allowed / RRC Inactive | Rel-16 | C247 | UEs supporting 5G Core and NR standalone shared spectrum channel access and RRC_INACTIVE | +| 6.6.2 | NR Shared Spectrum cell reselection | | | | +| 6.6.2.1 | Cell reselection / next best cell / intra frequency | Rel-16 | C217 | UEs supporting 5G Core and NR standalone shared spectrum channel access | +| 6.6.2.2 | Cell reselection / next best cell not suitable / inter frequency | Rel-16 | C217 | UEs supporting 5G Core and NR standalone shared spectrum channel access | +| 6.6.2.3 | Cell reselection / next best cell / intra frequency / RRC Inactive | Rel-16 | C247 | UEs supporting 5G Core and NR standalone shared spectrum channel access and RRC_INACTIVE | +| 6.6.2.4 | Cell reselection / next best cell not suitable / inter frequency / RRC Inactive | Rel-16 | C247 | UEs supporting 5G Core and NR standalone shared spectrum channel access and RRC_INACTIVE | +| 6.7 | Non-Terrestrial Network | | | | +| 6.7.1 | NTN idle mode operations | | | | +| 6.7.1.1 | NR NTN / Cell Selection / GNSS location | Rel-17 | C309 | UEs supporting 5G Core and NR NTN access | +| 6.7.1.2 | NR NTN / Cell Selection / MultiTAC / trackingAreaList-r17 | Rel-17 | C309 | UEs supporting 5G Core and NR NTN access | +| 6.7.1.3 | NR NTN / Cell Selection / Serving cell becomes non-suitable (CellBarredNTN) | Rel-17 | C309 | UEs supporting 5G Core and NR NTN access | +| 6.7.1.4 | NR -NTN / PLMN selection / Periodic reselection / MinimumPeriodicSearchTimer test case | Rel-17 | C309 | UEs supporting 5G Core and NR NTN access | +| 6.7.1.5 | NR NTN / Cell reselection, Sintrasearch, Snonintrasearch / location based measurements | Rel-17 | C333 | UEs supporting 5G Core and NR NTN access and Location-based measurement initiation for NTN while in RRC_IDLE/RRC_INACTIVE and NTN features in NGSO scenario | +| 6.7.1.6 | NR NTN / Cell reselection, Sintrasearch, Snonintrasearch / time based measurements | Rel-17 | C334 | UEs supporting 5G Core and NR NTN access and Time-based measurement initiation for NTN while in RRC_IDLE/RRC_INACTIVE and NTN features in NGSO scenario | +| 6.7.1.7 | NR NTN Enhancements / Cell reselection, Sintrasearch, Snonintrasearch / location based measurements | Rel-18 | C407 | UEs supporting 5G Core and NR NTN access and Earth Moving Cell | +| 6.7.2 | NTN in RRC_INACTIVE state | | | | +| 6.7.2.1 | NR NTN / Cell reselection, Sintrasearch, Snonintrasearch in RRC_Inactive state / location based measurements | Rel-17 | C346 | UEs supporting 5G Core and NR NTN access and Location-based measurement initiation for NTN while in RRC_IDLE/RRC_INACTIVE and RRC_INACTIVE and NTN features in NGSO scenario | +| 6.7.2.2 | NR NTN / Cell reselection, Sintrasearch, Snonintrasearch in RRC_Inactive state / time based measurements | Rel-17 | C347 | UEs supporting 5G Core and NR NTN access and Time-based measurement initiation for NTN while in RRC_IDLE/RRC_INACTIVE and RRC_INACTIVE and NTN features in NGSO scenario | + +**Table 4.1-1b: Additional Information of Applicability of Protocol conformance Idle mode test cases, ref. TS 38.523-1 [2]** + +| Clause | Specific ICS | Specific IXIT | Number of TC Executions | Release other RAT | +|--------------|---------------------------------------------------------------------------|----------------------------------------|----------------------------------------------------------------------------------------------------|-------------------| +| 6 | | | | | +| 6.1 | | | | | +| 6.1.1.4a | | | If test case 6.1.1.4 has been executed, then test case 6.1.1.4a need not to be executed (Note 1) | | +| 6.1.2.8 | | | If test case 6.1.2.7 has been executed then test case 6.1.2.8 needs not to be executed | | +| 6.1.2.15a | | | If test case 6.1.2.15 has been executed, then test case 6.1.2.15a need not to be executed (Note 1) | | +| 6.1.2.23 | | px_NR_OverlappingNotSupportedBand_MFBI | | | +| 6.1.2.30 | pc_halfDuplexFDD_TypeA_RedCap_MFBI | px_NR_OverlappingSupportedBand_MFBI | | | +| 6.1.2.34 | pc_supportOf1Rxbranch_eRedCap_r18,
pc_supportOf2Rxbranches_eRedCap_r18 | | | | +| 6.2 | | | | | +| 6.2.1 | | | | | +| 6.2.1.1 | | | | Rel-15 E-UTRA | +| 6.2.1.2 | | | | Rel-15 E-UTRA | +| 6.2.1.3 | | | | Rel-15 E-UTRA | +| 6.2.1.4 | [10]
pc_Available_PLMNs_AcT_Ind | | | Rel-15 E-UTRA | +| 6.2.1.5 | | | | Rel-15 E-UTRA | +| 6.2.2 | | | | | +| 6.2.3 | | | | | +| 6.2.3.1 | | | | Rel-15 E-UTRA | +| 6.2.3.2 | | | | Rel-15 E-UTRA | +| 6.2.3.3 | | | | Rel-15 E-UTRA | +| 6.2.3.4 | | | | Rel-15 E-UTRA | +| 6.2.3.5 | | | | Rel-15 E-UTRA | +| 6.2.3.6 | | | | Rel-15 E-UTRA | +| 6.2.3.7 | | | | Rel-15 E-UTRA | +| 6.2.3.8 | | | | Rel-15 E-UTRA | +| 6.3 | | | | | +| 6.3.1 | | | | | +| 6.3.1.2 | pc_SOR_ACKNotReqLocalRel | | | | +| 6.4 | | | | | +| 6.4.1 | | | | | +| 6.4.2 | | | | | +| 6.4.3 | | | | | +| 6.4.3.1 | | | | Rel-15 E-UTRA | + +Note 1: The two TCs verify the same core spec requirement(s) however in a different cell configuration to address different network deployments i.e., Cells broadcasting multiple PLMN IDs with unique TAC's, RAN areas, and cell identities + +**Table 4.1-2a: Applicability of Protocol conformance Layer 2 test cases, ref. TS 38.523-1 [2]** + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-------------------------|-----------------------| +| 7 | Layer 2 | | | | +| 7.1 | NR Layer 2 | | | | +| 7.1.1 | MAC | | | | +| 7.1.1.1 | Random Access Procedures | | | | +| 7.1.1.1.1 | Correct selection of RACH parameters / Random access preamble and PRACH resource explicitly signalled to the UE by RRC / contention free random access procedure | Rel-15 | R | UEs supporting 5GS | +| 7.1.1.1.1a | Correct selection of RACH parameters / Random access preamble and PRACH resource explicitly signalled to the UE by | Rel-15 | R | UEs supporting 5GS | + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------| +| | PDCCH Order / contention free random access procedure | | | | +| 7.1.1.1.2 | Random access procedure / Successful / C-RNTI Based / Preamble selected by MAC itself | Rel-15 | R | UEs supporting 5GS | +| 7.1.1.1.3 | Random access procedure / Successful / SI request | Rel-15 | C21 | UEs supporting 5G Core | +| 7.1.1.1.4 | Random access procedure / Successful / Beam Failure / Preamble selected by MAC itself / non-Contention Free RACH procedure | Rel-15 | R | UEs supporting 5GS | +| 7.1.1.1.5 | Random access procedure / Successful / Supplementary Uplink | Rel-15 | C28 | UEs supporting 5GS and NR SUL and supplemental uplink with dynamic switch | +| 7.1.1.1.6 | Random access procedure / Successful / Temporary C-RNTI Based / Preamble selected by MAC itself | Rel-15 | R | UEs supporting 5GS | +| 7.1.1.1.7 | Random access procedure / 2-step RACH / RA_TYPE selection | Rel-16 | C135 | UEs supporting 2-Step RACH | +| 7.1.1.1.8 | Correct selection of RACH parameters / 2-step RACH/MSGA and PRACH resource explicitly signalled to the UE by RRC / contention free random access procedure | Rel-16 | C135 | UEs supporting 2-Step RACH | +| 7.1.1.1.9 | Random access procedure / Successful / 2-step RACH/C-RNTI Based / Preamble selected by MAC itself | Rel-16 | C135 | UEs supporting 2-Step RACH | +| 7.1.1.1.9a | Random access procedure / 2-step RACH / Successful / RRC_IDLE | Rel-16 | C135A | UEs supporting 5G Core and 2-Step RACH | +| 7.1.1.1.10 | Random access procedure / 2-step RACH/not complete/ RA_TYPE to 4-stepRA | Rel-16 | C135 | UEs supporting 2-Step RACH | +| 7.1.1.1.10a | Random access procedure / 2-step RACH/ Fallback for CBRA | Rel-16 | C135A | UEs supporting 5G Core and 2-Step RACH | +| 7.1.1.1.11 | Random access procedure / Successful / Slice specific RACH configuration | Rel-17 | C262 | UEs supporting slice-based RACH partitioning and slice-based RACH prioritisation | +| 7.1.1.1.12 | Random access procedure / Successful / ra-PrioritizationForSlicing | Rel-17 | C263 | UEs supporting slice-based RACH partitioning, slice-based RACH prioritisation and RACH prioritisation for Access Identity 1 | +| 7.1.1.1.13 | Random access procedure / Successful / Slice specific RACH configuration / 2-step RACH | Rel-17 | C264 | UEs supporting 2-Step RACH, slice-based RACH partitioning and slice-based RACH prioritisation | +| 7.1.1.1.14 | Random access procedure / Successful / ra-PrioritizationForSlicingTwoStep / 2-step RACH | Rel-17 | C265 | UEs supporting 2-Step RACH, slice-based RACH partitioning, slice-based RACH prioritisation and RACH prioritisation for Access Identity 1 | +| 7.1.1.1.15 | Random access procedure / RedCap UE / SI request | Rel-17 | C212 | UEs supporting 5G Core and RedCap | +| 7.1.1.1.16 | Random access procedure / RedCap UE identification / Msg3-based / CCCH1 | Rel-17 | C212a | UEs supporting 5G Core and RedCap and RRC_INACTIVE | +| 7.1.1.1.17 | Random access procedure / RedCap UE identification | Rel-17 | C212 | UEs supporting 5G Core and RedCap | +| 7.1.1.1.18 | Random access procedure / Msg3 repetition indication / Random access resources selection | Rel-17 | C211 | UEs supporting 5G Core and repetition of Message 3 PUSCH | +| 7.1.1.1.19 | Random access procedure / Successful / Beam Failure / Unified TCI | Rel-17 | C311 | UEs supporting 5GS and unified TCI state operation with joint DL/UL TCI update for intra-cell beam management | +| 7.1.1.1.20 | Random access procedure / Msg1 repetition / Contention-based | Rel-18 | C414 | UEs supporting 5G Core and PRACH repetition | +| 7.1.1.1.21 | Random access procedure / Msg1 repetition / Msg1-based SI request | Rel-18 | C414 | UEs supporting 5G Core and PRACH repetition | +| 7.1.1.1.22 | Random access procedure / Msg1 repetition / BWP only configured with RACH resource for coverage enhancement | Rel-18 | C351 | UEs supporting 5GS and PRACH repetition | +| 7.1.1.1.24 | Random access procedure / eRedCap UE identification / Msg3-based / CCCH1 | Rel-18 | C389 | UEs supporting 5G Core and eRedCap and RRC_INACTIVE | +| 7.1.1.1.25 | Random access procedure / eRedCap UE identification / Msg1-based / Contention based / Msg3-based / CCCH / Correct handling of contention Resolution with large bandwidth | Rel-18 | C380 | UEs supporting 5G Core and eRedCap | +| 7.1.1.1.26 | Random access procedure / eRedCap UE identification / Msg1-based / Contention free random access procedure | Rel-18 | C380 | UEs supporting 5G Core and eRedCap | +| 7.1.1.1.27 | Random access procedure / eRedCap UE / SI request | Rel-18 | C380 | UEs supporting 5G Core and eRedCap | +| 7.1.1.1.29 | Random access procedure / Successful / LTM cell switch / DL assignment on the PDCCH / | Rel-18 | C405 | UEs supporting 5G Core and unified TCI with joint DL/UL TCI-state indication and MAC-CE | + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|------------------|---------------------------------------------------------------------------------------------------------------------|---------|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | UL grant | | | activated joint LTM TCI states and TA indication in cell switch command and RACH-Less LTM with dynamic grant | +| 7.1.1.1.31 | NR NTN Enhancements / Random access procedure / Coverage Enhancement | Rel-18 | C408 | UEs supporting 5G Core and NR NTN access and Msg4 HARQ Repetition | +| 7.1.1.2 | Downlink Data Transfer | | | | +| 7.1.1.2.1 | Correct Handling of DL MAC PDU / Assignment / HARQ process | Rel-15 | R | UEs supporting 5GS | +| 7.1.1.2.2 | Correct Handling of DL HARQ process PDSCH Aggregation | Rel-15 | C20 | UEs supporting 5GS and PDSCH aggregation | +| 7.1.1.2.3 | Correct HARQ process handling / CCCH | Rel-15 | R | UEs supporting 5GS | +| 7.1.1.2.4 | Correct HARQ process handling / BCCH | Rel-15 | R | UEs supporting 5GS | +| 7.1.1.2.5 | Correct HARQ process handling / DL grant prioritization | Rel-16 | C179 | UEs supporting DCI DL Priority Indicator | +| 7.1.1.2.6 | Correct HARQ process handling / dynamic PUCCH repetition indication | Rel-17 | C287 | UEs supporting dynamic indication of PUCCH repetition | +| 7.1.1.2.7 | Correct HARQ process handling / Unified TCI Activation | Rel-17 | C312 | UEs supporting 5GS and unified separate TCI with multi-MAC-CE | +| 7.1.1.2.8 | Multi-cell PDSCH scheduling with a single DCI / FDRA field based | | | | +| 7.1.1.2.8.1 | Multi-cell PDSCH scheduling with a single DCI / FDRA field based / Intra-band Contiguous CA | Rel-18 | C362 | UEs supporting 5G Core and intra-band contiguous CA and DL NR CA with 2 carriers and DCI format 1_3 with same SCS between scheduling cell and cells in the set and co-scheduled cell indication scheme based on FDRA field of DCI format 1_3 | +| 7.1.1.2.8.2 | Multi-cell PDSCH scheduling with a single DCI / FDRA field based / Inter-band CA | Rel-18 | C363 | UEs supporting 5G Core and inter-band CA and DL NR CA with 2 carriers and DCI format 1_3 with same SCS between scheduling cell and cells in the set and co-scheduled cell indication scheme based on FDRA field of DCI format 1_3 | +| 7.1.1.2.8.3 | Multi-cell PDSCH scheduling with a single DCI / FDRA field based / Intra-band non-Contiguous CA | Rel-18 | C364 | UEs supporting 5G Core and intra-band non-contiguous CA and DL NR CA with 2 carriers and DCI format 1_3 with same SCS between scheduling cell and cells in the set and co-scheduled cell indication scheme based on FDRA field of DCI format 1_3 | +| 7.1.1.2.9 | Multi-cell PDSCH scheduling with a single DCI / Scheduled cell indicator field based | | | | +| 7.1.1.2.9.1 | Multi-cell PDSCH scheduling with a single DCI / Scheduled cell indicator field based / Intra-band Contiguous CA | Rel-18 | C365 | UEs supporting 5G Core and intra-band contiguous CA and DL NR CA with 2 carriers and DCI format 1_3 with same SCS between scheduling cell and cells in the set and co-scheduled cell indication scheme based on Scheduled cells indicator field of DCI format 1_3 | +| 7.1.1.2.9.2 | Multi-cell PDSCH scheduling with a single DCI / Scheduled cell indicator field based / Inter-band CA | Rel-18 | C366 | UEs supporting 5G Core and inter-band CA and DL NR CA with 2 carriers and DCI format 1_3 with same SCS between scheduling cell and cells in the set and co-scheduled cell indication scheme based on Scheduled cells indicator field of DCI format 1_3 | +| 7.1.1.2.9.3 | Multi-cell PDSCH scheduling with a single DCI / Scheduled cell indicator field based / Intra-band non-Contiguous CA | Rel-18 | C367 | UEs supporting 5G Core and intra-band non-contiguous CA and DL NR CA with 2 carriers and DCI format 1_3 with same SCS between scheduling cell and cells in the set and co-scheduled cell indication scheme based on Scheduled cells indicator field of DCI format 1_3 | +| 7.1.1.3 | Uplink Data Transfer | | | | +| 7.1.1.3.1 | Correct Handling of UL MAC PDU / Assignment / HARQ process | Rel-15 | R | UEs supporting 5GS | +| 7.1.1.3.2 | Logical channel prioritization handling | Rel-15 | C02 | UEs supporting 5GS and RLC UM Mode | +| 7.1.1.3.2b | Logical channel prioritization handling with Mapping restrictions | Rel-15 | C175 | UEs supporting 5GS and selection of logical channels for each UL grant based on RRC configured restriction | +| 7.1.1.3.3 | Correct handling of MAC control information / Scheduling requests | Rel-15 | C53 | UEs supporting 5GS and Logical Channel SR-Delay Timer | +| 7.1.1.3.4 | Correct handling of MAC control information / Buffer status / UL data arrive in the UE Tx buffer / Regular BSR | Rel-15 | R | UEs supporting 5GS | +| 7.1.1.3.5 | Correct handling of MAC control information / Buffer Status / UL resources are allocated / Padding BSR | Rel-15 | R | UEs supporting 5GS | +| 7.1.1.3.6 | Correct handling of MAC control information / Buffer status / Periodic BSR timer expires | Rel-15 | R | UEs supporting 5GS | + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|-------------------|------------------------------------------------------------------------------------------------------------------------------------|---------|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------| +| 7.1.1.3.7 | UE power headroom reporting / Periodic reporting / DL pathloss change reporting | Rel-15 | R | UEs supporting 5GS | +| 7.1.1.3.8 | UE power headroom reporting / SCell activation / DL pathloss change reporting | | | | +| 7.1.1.3.8.1 | UE power headroom reporting / SCell activation / DL pathloss change reporting / Intra-band Contiguous CA | Rel-15 | C81 | UEs supporting 5GCore and intra-band contiguous CA and UL NR CA with 2 carriers | +| | | | C81A | UEs supporting EN-DC and intra-band contiguous CA and EN-DC with 2 NR UL carriers | +| 7.1.1.3.8.2 | UE power headroom reporting / SCell activation / DL pathloss change reporting / Inter-band CA | Rel-15 | C82 | UEs supporting 5GCore and inter-band CA and UL NR CA with 2 carriers | +| | | | C82A | UEs supporting EN-DC and inter-band CA and EN-DC with 2 NR UL carriers | +| 7.1.1.3.8.3 | UE power headroom reporting / SCell activation / DL pathloss change reporting / Intra-band non Contiguous CA | Rel-15 | C83 | UEs supporting 5GCore and intra-band non-contiguous CA and UL NR CA with 2 carriers | +| | | | C83A | UEs supporting EN-DC and intra-band non-contiguous CA and EN-DC with 2 NR UL carriers | +| 7.1.1.3.9 | Correct Handling of UL HARQ process / PUSCH Repetition Type A / PUSCH Aggregation | Rel-15 | C51 | UEs supporting 5GS and PUSCH aggregation | +| 7.1.1.3.10 | Correct Handling of HARQ process / Multiple CORESETPoolIndex | Rel-16 | C107 | UEs supporting 5GS and multi-DCI based Multi-TRP | +| 7.1.1.3.11 | Correct handling of UL grant prioritization | Rel-16 | C114 | UEs supporting 5GS and LCH-based UL grant prioritization | +| 7.1.1.3.12 | Correct Handling of UL HARQ process / PUSCH Repetition Type B | Rel-16 | C134 | UEs supporting PUSCH repetition type B | +| 7.1.1.3.13 | Logical channel prioritization handling with Mapping restrictions / physical layer priority | Rel-16 | C180 | UEs supporting DCI UL Priority Indicator and LCH grant prioritisation | +| 7.1.1.3.14 | Correct Handling of UL HARQ process / PUSCH Repetition Type A enhancement | | | | +| 7.1.1.3.14.1 | Correct Handling of UL HARQ process / PUSCH Repetition Type A enhancement / Increased maximum repetition number / dynamic grant | Rel-17 | C288 | UEs supporting increased maximum number of PUSCH Type A repetitions and dynamic indication of the number of repetitions for PUSCH | +| 7.1.1.3.14.2 | Correct Handling of UL HARQ process / PUSCH Repetition Type A enhancement / Increased maximum repetition number / configured grant | Rel-17 | C289 | UEs supporting increased maximum number of PUSCH Type A repetitions and PUSCH transmissions with configured grant | +| 7.1.1.3.14.3 | Correct Handling of UL HARQ process / PUSCH Repetition Type A enhancement / repetition based on available slots / dynamic grant | Rel-17 | C290 | UEs supporting PUSCH repetitions based on available slots and dynamic indication of the number of repetitions for PUSCH | +| 7.1.1.3.14.4 | Correct Handling of UL HARQ process / PUSCH Repetition Type A enhancement / repetition based on available slots / configured grant | Rel-17 | C291 | UEs supporting PUSCH repetitions based on available slots and PUSCH transmissions with configured grant | +| 7.1.1.3.15 | Correct Handling of UL HARQ process / TBoMS procedure | | | | +| 7.1.1.3.15.1 | Correct Handling of UL HARQ process / TBoMS procedure / DG and CG based transmission | Rel-17 | C292 | UEs supporting TB processing over multi-slot PUSCH | +| 7.1.1.3.15.2 | Correct Handling of UL HARQ process / TBoMS procedure / Repetition of TBoMS | Rel-17 | C293 | UEs supporting repetition of TB processing over multi-slot PUSCH | +| 7.1.1.3.16 | Correct Handling of UL grant / DRB configured with survival time | | | | +| 7.1.1.3.16.1 | Correct Handling of UL grant / DRB configured with survival time / Split DRB | Rel-17 | C256 | UEs supporting services with survival time and NR-DC and PDCP-duplication over split DRB | +| 7.1.1.3.16.2 | Correct Handling of UL grant / DRB configured with survival time / MCG or SCG DRB / Intra-band contiguous CA | Rel-17 | C257 | UEs supporting services with survival time and intra-band contiguous CA and CA-based PDCP duplication over MCG or SCG DRB | +| 7.1.1.3.16.3 | Correct Handling of UL grant / DRB configured with survival time / MCG or SCG DRB / Intra-band non-contiguous CA | Rel-17 | C258 | UEs supporting services with survival time and intra-band non-contiguous CA and CA-based PDCP duplication over MCG or SCG DRB | +| 7.1.1.3.16.4 | Correct Handling of UL grant / DRB configured with survival time / MCG or SCG DRB / Inter-band CA | Rel-17 | C259 | UEs supporting services with survival time and inter-band CA and CA-based PDCP duplication over MCG or SCG DRB | +| 7.1.1.3.17 | Correct Handling of UL HARQ process / PUSCH Repetition / Multi-TRP | | | | +| 7.1.1.3.17.1 | Correct Handling of UL HARQ process / | Rel-17 | C330 | UEs supporting 5GS and multi-TRP PUSCH | + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|-------------------|----------------------------------------------------------------------------------------------------------------------|---------|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | PUSCH Repetition / Multi-TRP / PUSCH Repetition Type A / dynamic grant | | | repetition type A | +| 7.1.1.3.17.2 | Correct Handling of UL HARQ process / PUSCH Repetition / Multi-TRP / PUSCH Repetition Type B / dynamic grant | Rel-17 | C331 | UEs supporting 5GS and multi-TRP PUSCH repetition type B | +| 7.1.1.3.18 | Correct handling of MAC control information / Buffer status / UL data arrive in the UE Tx buffer / Refined BSR | Rel-18 | C357 | UEs supporting 5G Core and using the refined buffer size table for BSR | +| 7.1.1.3.19 | Correct handling of MAC control information / Buffer Status / UL resources are allocated / Refined BSR / Padding BSR | Rel-18 | C357 | UEs supporting 5G Core and using the refined buffer size table for BSR | +| 7.1.1.3.20 | Correct handling of MAC control information / Delay Status / Delay status reporting | Rel-18 | C352 | UEs supporting 5GS and delay status reporting | +| 7.1.1.3.20a | Correct handling of MAC control information / Delay Status / Refined delay status reporting | Rel-18 | C398 | UEs supporting 5GS and delay status reporting and refined buffer size table | +| 7.1.1.3.21 | Correct handling of MAC control information / Delay Status / Triggering scheduling request | Rel-18 | C352 | UEs supporting 5GS and delay status reporting | +| 7.1.1.3.26 | Multi-cell PUSCH scheduling with a single DCI / FDRA field based | | | | +| 7.1.1.3.26.1 | Multi-cell PUSCH scheduling with a single DCI / FDRA field based / Intra-band Contiguous CA | Rel-18 | C386 | UEs supporting 5G Core and intra-band contiguous CA and UL NR CA with 2 carriers and DCI format 0_3 with same SCS between scheduling cell and cells in the set and co-scheduled cell indication scheme based on FDRA field of DCI format 0_3 | +| 7.1.1.3.26.2 | Multi-cell PUSCH scheduling with a single DCI / FDRA field based / Inter-band CA | Rel-18 | C387 | UEs supporting 5G Core and inter-band CA and UL NR CA with 2 carriers and DCI format 0_3 with same SCS between scheduling cell and cells in the set and co-scheduled cell indication scheme based on FDRA field of DCI format 0_3 | +| 7.1.1.3.26.3 | Multi-cell PUSCH scheduling with a single DCI / FDRA field based / Intra-band non-Contiguous CA | Rel-18 | C388 | UEs supporting 5G Core and intra-band non-contiguous CA and UL NR CA with 2 carriers and DCI format 0_3 with same SCS between scheduling cell and cells in the set and co-scheduled cell indication scheme based on FDRA field of DCI format 0_3 | +| 7.1.1.3.28 | Correct handling of MAC control information / LTM Cell Switch Command / UL transmission without random access | Rel-18 | C406 | UEs supporting NR-DC and unified TCI with joint DL/UL TCI-state indication and MAC-CE activated joint LTM TCI states and UE-based TA measurement by indicating the maximum number of candidate cells that the UE maintains the TA for and RACH-Less LTM with dynamic grant | +| 7.1.1.4 | Transport Size Selection | | | | +| 7.1.1.4.1 | DL-SCH Transport Block Size Selection | | | | +| 7.1.1.4.1.1 | DL-SCH Transport Block Size selection / DCI format 1_0 | Rel-15 | R | UEs supporting 5GS | +| 7.1.1.4.1.2 | Void | | | | +| 7.1.1.4.1.3 | DL-SCH transport block size selection / DCI format 1_1 / RA type 0/RA Type 1 / 2 Codewords enabled | Rel-15 | C64 | UEs supporting 5GS and The maximum number of spatial multiplexing layer(s) supported by the UE for DL reception is 8 Layers. For single CC standalone NR, it is mandatory with capability signalling to support at least 4 MIMO layers in the bands where 4Rx is specified as mandatory for the given UE and at least 2 MIMO layers in FR2. If absent, the UE doesn't support MIMO on this carrier | +| 7.1.1.4.1.4 | DL-SCH transport block size selection / DCI format 1_1 / RA type 0/RA Type 1 / 2 Codewords enabled / 256QAM | Rel-15 | C65 | UEs supporting 5GS and The maximum number of spatial multiplexing layer(s) supported by the UE for DL reception is 8 Layers. For single CC standalone NR, it is mandatory with capability signalling to support at least 4 MIMO layers in the bands where 4Rx is specified as mandatory for the given UE and at least 2 MIMO layers in FR2. If absent, the UE doesn't support MIMO on this carrier and 256QAM for PUSCH | +| 7.1.1.4.1.5 | DL-SCH transport block size selection / DCI format 1_2 | Rel-16 | C146 | UEs supporting monitoring DCI format 1_2 for DL scheduling and monitoring DCI format 0_2 for UL scheduling | +| 7.1.1.4.2 | UL-SCH Transport Block Size Selection | | | | +| 7.1.1.4.2.1 | UL-SCH Transport Block Size selection / DCI format 0_0 / Transform precoding disabled | Rel-15 | R | UEs supporting 5GS | +| 7.1.1.4.2.2 | Void | | | | +| 7.1.1.4.2.3 | UL-SCH transport block size selection / DCI | Rel-15 | R | UEs supporting 5GS | + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|---------|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | format 0_1 / RA type 0/RA Type 1 / Transform precoding disabled | | | | +| 7.1.1.4.2.4 | UL-SCH transport block size selection / DCI format 0_0 / Transform precoding and 256QAM / Transform precoding disabled | Rel-15 | C11 | UEs supporting 5GS and 256QAM for PDSCH for FR1/FR2 | +| 7.1.1.4.2.5 | UL-SCH Transport Block Size selection / DCI format 0_0 / Transform precoding and 64QAM | Rel-15 | R | UEs supporting 5GS | +| 7.1.1.4.2.6 | UL-SCH Transport Block Size selection / DCI format 0_2 | Rel-16 | C146 | UEs supporting monitoring DCI format 1_2 for DL scheduling and monitoring DCI format 0_2 for UL scheduling | +| 7.1.1.4.2.7 | UL-SCH Transport Block Size selection / TBoMS procedure | Rel-17 | C292 | UEs supporting TB processing over multi-slot PUSCH | +| 7.1.1.5 | Discontinuous reception | | | | +| 7.1.1.5.1 | DRX operation / Short cycle not configured / Parameters configured by RRC | Rel-15 | C03 | UEs supporting 5GS and long DRX cycle | +| 7.1.1.5.2 | DRX operation / Short cycle not configured / Long DRX command MAC control element reception | Rel-15 | C03 | UEs supporting 5GS and long DRX cycle | +| 7.1.1.5.3 | DRX operation / Short cycle configured / Parameters configured by RRC | Rel-15 | C04 | UEs supporting 5GS and short DRX cycle | +| 7.1.1.5.4 | DRX operation / Short cycle configured / DRX command MAC control element reception | Rel-15 | C04 | UEs supporting 5GS and short DRX cycle | +| 7.1.1.5.5 | DRX operation / Short cycle configured / Long DRX command MAC control element reception | Rel-15 | C70 | UEs supporting 5GS and long DRX cycle and short DRX cycle | +| 7.1.1.5.6 | NR NTN / DRX operation / Short cycle not configured / HARQ RTT | Rel-17 | C309 | UEs supporting 5G Core and NR NTN access | +| 7.1.1.5.7 | Non-Integer DRX operation / Short cycle not configured / Parameters configured by RRC | Rel-18 | C353 | UEs supporting 5G Core and non-integer DRX cycle | +| 7.1.1.5.8 | Non-Integer DRX operation / Short cycle configured / Parameters configured by RRC | Rel-18 | C353 | UEs supporting 5G Core and non-integer DRX cycle | +| 7.1.1.5.10 | NR NTN / DRX operation / Short cycle not configured / Correct HARQ process handling / HARQ feedback disabled / HARQ modeB | Rel-17 | C348 | UEs supporting 5G Core and NR NTN access and ((HARQ Mode B and the corresponding LCP restrictions for uplink transmission) or (disabled HARQ feedback for downlink transmission)) | +| 7.1.1.6 | Semi-Persistent Scheduling | | | | +| 7.1.1.6.1 | Correct handling of DL assignment / Semi-persistent case | Rel-15 | C17 | UEs supporting 5GS and PDSCH reception based on semi-persistent scheduling | +| 7.1.1.6.2 | Correct handling of UL grant / configured grant Type 1 | Rel-15 | C18 | UEs supporting 5GS and Type 1 PUSCH transmissions with configured grant | +| 7.1.1.6.3 | Correct handling of UL grant / configured grant Type 2 | Rel-15 | C19 | UEs supporting 5GS and Type 2 PUSCH transmissions with configured grant | +| 7.1.1.6.4 | Correct handling of DL assignment / Multi Semi-persistent configuration | Rel-16 | C113 | UEs supporting 5G Core and PDSCH reception based on semi-persistent scheduling and up to 8 configured SPS configurations in a BWP of a serving cell and up to 32 configured SPS configurations in a cell group | +| 7.1.1.6.5 | Correct handling of UL grant / Multi configured uplink grants | Rel-16 | C142 | UEs supporting 5G Core and Type 1 PUSCH transmissions with configured grant and up to 12 configured/active configured grant configurations in a BWP of a serving cell. | +| 7.1.1.6.6 | Correct handling of UL grant / Multiple CG PUSCH occasions per CG period / Configured grant Type 1 | Rel-18 | C354 | UEs supporting 5G Core and Type 1 PUSCH transmissions with configured grant and multi-PUSCHs for configured grant | +| 7.1.1.6.7 | Correct handling of UL grant / Multiple CG PUSCH occasions per CG period / Configured grant Type 2 | Rel-18 | C355 | UEs supporting 5G Core and Type 2 PUSCH transmissions with configured grant and multi-PUSCHs for configured grant | +| 7.1.1.6.8 | Correct handling of UL grant / Unused transmission occasion / Configured grant type 1 | Rel-18 | C399 | UEs supporting 5GS and Type 1 PUSCH transmissions with configured grant and multiplexing of the unused transmission occasions on a CG-PUSCH | +| 7.1.1.7 | Activation/Deactivation of SCells | | | | +| 7.1.1.7.1 | Activation/Deactivation of SCells / Activation/Deactivation MAC control element reception / sCellDeactivationTimer | | | | +| 7.1.1.7.1.1 | Activation/Deactivation of SCells / Activation/Deactivation MAC control element reception / sCellDeactivationTimer / Intra-band Contiguous CA | Rel-15 | C44 | UEs supporting 5GS and intra-band contiguous CA | +| | | | C44A | UEs supporting EN-DC and intra-band contiguous CA and EN-DC with 2 NR DL carriers | +| 7.1.1.7.1.2 | Activation/Deactivation of SCells / | Rel-15 | C45 | UEs supporting 5GS and inter-band CA | + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Activation/Deactivation MAC control element reception / sCellDeactivationTimer / Inter-band CA | | | | +| | | | C45A | UEs supporting EN-DC and inter-band CA and EN-DC with 2 NR DL carriers | +| 7.1.1.7.1.3 | Activation/Deactivation of SCells / Activation/Deactivation MAC control element reception / sCellDeactivationTimer / Intra-band non-Contiguous CA | Rel-15 | C46 | UEs supporting 5GS and intra-band non-contiguous CA | +| | | | C46A | UEs supporting EN-DC and intra-band non-contiguous CA and EN-DC with 2 NR DL carriers | +| 7.1.1.7.2 | Activation/Deactivation of SCells / Multi-cell PDSCH scheduling with a single DCI / Search space for single DCI is only configured in scheduling cell / sCellDeactivationTimer | | | | +| 7.1.1.7.2.1 | Activation/Deactivation of SCells / Multi-cell PDSCH scheduling with a single DCI / Search space for single DCI is only configured in scheduling cell / sCellDeactivationTimer / Intra-band Contiguous CA | Rel-18 | C368 | UEs supporting 5G Core and intra-band contiguous CA and DL NR CA with 2 carriers and DCI format 1_3 with same SCS between scheduling cell and cells in the set | +| 7.1.1.7.2.2 | Activation/Deactivation of SCells / Multi-cell PDSCH scheduling with a single DCI / Search space for single DCI is only configured in scheduling cell / sCellDeactivationTimer / Inter-band CA | Rel-18 | C369 | UEs supporting 5G Core and inter-band CA and DL NR CA with 2 carriers and DCI format 1_3 with same SCS between scheduling cell and cells in the set | +| 7.1.1.7.2.3 | Activation/Deactivation of SCells / Multi-cell PDSCH scheduling with a single DCI / Search space for single DCI is only configured in scheduling cell / sCellDeactivationTimer / Intra-band non-Contiguous CA | Rel-18 | C370 | UEs supporting 5G Core and intra-band non-contiguous CA and DL NR CA with 2 carriers and DCI format 1_3 with same SCS between scheduling cell and cells in the set | +| 7.1.1.7.3 | Activation/Deactivation of SCells / Multi-cell PUSCH scheduling with a single DCI / Search space for single DCI is only configured in scheduling cell / sCellDeactivationTimer | | | | +| 7.1.1.7.3.1 | Activation/Deactivation of SCells / Multi-cell PUSCH scheduling with a single DCI / Search space for single DCI is only configured in scheduling cell / sCellDeactivationTimer / Intra-band Contiguous CA | Rel-18 | C371 | UEs supporting 5G Core and intra-band contiguous CA and UL NR CA with 2 carriers and DCI format 0_3 with same SCS between scheduling cell and cells in the set | +| 7.1.1.7.3.2 | Activation/Deactivation of SCells / Multi-cell PUSCH scheduling with a single DCI / Search space for single DCI is only configured in scheduling cell / sCellDeactivationTimer / Inter-band CA | Rel-18 | C372 | UEs supporting 5G Core and inter-band CA and UL NR CA with 2 carriers and DCI format 0_3 with same SCS between scheduling cell and cells in the set | +| 7.1.1.7.3.3 | Activation/Deactivation of SCells / Multi-cell PUSCH scheduling with a single DCI / Search space for single DCI is only configured in scheduling cell / sCellDeactivationTimer / Intra-band non-Contiguous CA | Rel-18 | C373 | UEs supporting 5G Core and intra-band non-contiguous CA and UL NR CA with 2 carriers and DCI format 0_3 with same SCS between scheduling cell and cells in the set | +| 7.1.1.7.4 | Activation/Deactivation of SCells / Multi-cell PDSCH scheduling with a single DCI / Search space for single DCI is not only configured in scheduling cell / sCellDeactivationTimer | | | | +| 7.1.1.7.4.1 | Activation/Deactivation of SCells / Multi-cell PDSCH scheduling with a single DCI / Search space for single DCI is not only configured in scheduling cell / sCellDeactivationTimer / Intra-band Contiguous CA | Rel-18 | C374 | UEs supporting 5G Core and intra-band contiguous CA and DL NR CA with 2 carriers and DCI format 1_3 with same SCS between scheduling cell and cells in the set and search space set configurations for DCI format 1_3 for the set of cells with the same searchSpaceId are provided on both the scheduling cell and a serving cell in the set of cells with the scheduling cell being in the set of cells. | +| 7.1.1.7.4.2 | Activation/Deactivation of SCells / Multi-cell PDSCH scheduling with a single DCI / Search space for single DCI is not only configured in scheduling cell / sCellDeactivationTimer / Inter-band CA | Rel-18 | C375 | UEs supporting 5G Core and inter-band CA and DL NR CA with 2 carriers and DCI format 1_3 with same SCS between scheduling cell and cells in the set and search space set configurations for DCI format 1_3 for the set of cells with the same searchSpaceId are provided on both the scheduling cell and a serving cell in the set of cells with the scheduling cell being in | + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | | the set of cells. | +| 7.1.1.7.4.3 | Activation/Deactivation of SCells / Multi-cell PDSCH scheduling with a single DCI / Search space for single DCI is not only configured in scheduling cell / sCellDeactivationTimer / Intra-band non-Contiguous CA | Rel-18 | C376 | UEs supporting 5G Core and intra-band non-contiguous CA and DL NR CA with 2 carriers and DCI format 1_3 with same SCS between scheduling cell and cells in the set and search space set configurations for DCI format 1_3 for the set of cells with the same searchSpaceld are provided on both the scheduling cell and a serving cell in the set of cells with the scheduling cell being in the set of cells. | +| 7.1.1.7.5 | Activation/Deactivation of SCells / Multi-cell PUSCH scheduling with a single DCI / Search space for single DCI is not only configured in scheduling cell / sCellDeactivationTimer | | | | +| 7.1.1.7.5.1 | Activation/Deactivation of SCells / Multi-cell PUSCH scheduling with a single DCI / Search space for single DCI is not only configured in scheduling cell / sCellDeactivationTimer/ Intra-band Contiguous CA | Rel-18 | C377 | UEs supporting 5G Core and intra-band contiguous CA and UL NR CA with 2 carriers and DCI format 0_3 with same SCS between scheduling cell and cells in the set and search space set configurations for DCI format 0_3 for the set of cells with the same searchSpaceld are provided on both the scheduling cell and a serving cell in the set of cells with the scheduling cell being in the set of cells. | +| 7.1.1.7.5.2 | Activation/Deactivation of SCells / Multi-cell PUSCH scheduling with a single DCI / Search space for single DCI is not only configured in scheduling cell / sCellDeactivationTimer/ Inter-band CA | Rel-18 | C378 | UEs supporting 5G Core and inter-band CA and UL NR CA with 2 carriers and DCI format 0_3 with same SCS between scheduling cell and cells in the set and search space set configurations for DCI format 0_3 for the set of cells with the same searchSpaceld are provided on both the scheduling cell and a serving cell in the set of cells with the scheduling cell being in the set of cells. | +| 7.1.1.7.5.3 | Activation/Deactivation of SCells / Multi-cell PUSCH scheduling with a single DCI / Search space for single DCI is not only configured in scheduling cell / sCellDeactivationTimer / Intra-band non-Contiguous CA | Rel-18 | C379 | UEs supporting 5G Core and intra-band non-contiguous CA and UL NR CA with 2 carriers and DCI format 0_3 with same SCS between scheduling cell and cells in the set and search space set configurations for DCI format 0_3 for the set of cells with the same searchSpaceld are provided on both the scheduling cell and a serving cell in the set of cells with the scheduling cell being in the set of cells. | +| 7.1.1.8 | Bandwidth Part (BWP) operation | | | | +| 7.1.1.8.1 | Bandwidth Part (BWP) operation UL/DL | Rel-15 | C66 | UEs supporting 5GS and (DCI and timer based active BWP switching delay type1 or type2) and ((BWP adaptation upto2 NR FR1 FDD or NR FR1 TDD or NR FR2) or (BWP adaptation up to 4 NR FR1 FDD or NR FR1 TDD or NR FR2)) | +| 7.1.1.8.3 | Separate BWP / IDLE / RedCap | Rel-17 | C212 | UEs supporting 5G Core and RedCap | +| 7.1.1.8.4 | Separate BWP / RedCap-specific initial DL BWP without CORESET#0 / NCD-SSB | Rel-17 | C212 | UEs supporting 5G Core and RedCap | +| 7.1.1.8.5 | Separate BWP / IDLE / eRedCap | Rel-18 | C380 | UEs supporting 5G Core and eRedCap | +| 7.1.1.8.6 | Separate BWP / RedCap-specific initial DL BWP without CORESET#0 / NCD-SSB /eRedCap | Rel-18 | C380 | UEs supporting 5G Core and eRedCap | +| 7.1.1.9 | MAC Reconfiguration and Reset | | | | +| 7.1.1.9.1 | MAC Reset | Rel-15 | R | UEs supporting 5GS | +| 7.1.1.10 | Other Procedures | | | | +| 7.1.1.10.1 | DataInactivityTimer expiry | Rel-15 | C21 | UEs supporting 5G Core | +| 7.1.1.10.2 | Recommended Bit Rate | Rel-15 | C100 | UEs supporting 5G Core and MTSI speech and bit rate recommendation query message | +| 7.1.1.10.3 | NR CA / LBT failure on SCell / MAC CE indication | Rel-16 | C300 | UEs supporting 5G Core and NR CA with NR shared spectrum channel access and UL NR CA with 2 carriers and UL LBT Failure Detection and Recovery | +| 7.1.1.10.4 | NR NTN / UE specific TA report / UE specific Koffset | Rel-17 | C321 | UEs supporting 5G Core and NR NTN access and UE reporting of information related to TA pre-compensation and reception of UE-specific K_offset | +| 7.1.1.11 | NR Dual Connectivity | | | | +| 7.1.1.11.1 | DC power headroom reporting / PSCell activation and DL pathloss change reporting | Rel-15 | C80 | UEs supporting NR-DC | +| 7.1.1.12 | UE Power Saving | | | | +| 7.1.1.12.1 | Void | | | | + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|-------------------|----------------------------------------------------------------------------------------------|---------|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------| +| 7.1.1.12.3 | DRX adaptation / UE wakeup indication | Rel-16 | C103 | UEs supporting 5GS and Long DRX Cycle and DRX adaptation | +| 7.1.1.12.4.1 | DRX adaptation / SCell dormancy indication / Intra-band Contiguous CA | Rel-16 | C118 | UEs supporting 5GS and Long DRX Cycle and DRX adaptation and SCell Dormancy indication outside active time and intra-band contiguous CA | +| 7.1.1.12.4.2 | DRX adaptation / SCell dormancy indication / Intra-band non Contiguous CA | Rel-16 | C119 | UEs supporting 5GS and Long DRX Cycle and DRX adaptation and SCell Dormancy indication outside active time and intra-band non-contiguous CA | +| 7.1.1.12.4.3 | DRX adaptation / SCell dormancy indication / Inter-band CA | Rel-16 | C120 | UEs supporting 5GS and Long DRX Cycle and DRX adaptation and SCell Dormancy indication outside active time and inter-band CA | +| 7.1.1.13 | SDT | | | | +| 7.1.1.13.1 | RA Based SDT / 2-step RACH / Successful | Rel-17 | C232 | UEs Supporting 2-Step RACH and Random access SDT | +| 7.1.1.13.2 | RA Based SDT / 4-step RACH / Successful | Rel-17 | C233 | UEs supporting Random Access SDT | +| 7.1.1.13.3 | RA Based SDT / 2-step RACH / not complete / RA_TYPE to 4-stepRA | Rel-17 | C232 | UEs Supporting 2-Step RACH and Random access SDT | +| 7.1.1.13.4 | RA Based SDT / 4-step RA based SDT / Time Alignment Timer expiry | Rel-17 | C233 | UEs supporting Random Access SDT | +| 7.1.1.13.5 | RA Based SDT/ CG Based SDT/ cg-SDT- TimeAlignmentTimer | Rel-17 | C269 | UEs supporting 5G Core and SDT via Configured Grant Type 1 in RRC_INACTIVE state. | +| 7.1.1.13.6 | RA Based MT-SDT / 2-step RACH/ Success | Rel-18 | C412 | UEs supporting 5G Core and 2-step RACH and Random access MT-SDT. | +| 7.1.1.13.7 | RA Based MT-SDT / 4-step RACH/ Success | Rel-18 | C396 | UEs supporting 5G Core and Random access MT-SDT | +| 7.1.1.13.8 | RA Based MT-SDT / 4-Step RACH /RACH resources instead of CG resources / Success | Rel-18 | C397 | UEs supporting 5G Core and MT-SDT via Configured Grant Type 1 | +| 7.1.1.14 | Network energy saving | | | | +| 7.1.1.14.1 | DTX/DRX adaptation | | | | +| 7.1.1.14.1.1 | Cell DTX operation / Correct handling of DL assignment / (De)activation by RRC configuration | Rel-18 | C358 | UEs supporting 5GS and Long DRX Cycle and Cell DTX operation by RRC configuration | +| 7.1.1.14.1.2 | Cell DTX operation / Correct handling of DL assignment / (De)activation by DCI format 2_9 | Rel-18 | C359 | UEs supporting 5GS and Long DRX Cycle and Cell DTX configuration activation and deactivation via DCI 2_9 | +| 7.1.1.14.1.3 | Cell DRX operation / Correct handling of UL grant / (De)activation by RRC configuration | Rel-18 | C360 | UEs supporting 5GS and Cell DRX operation by RRC configuration | +| 7.1.1.14.1.4 | Cell DRX operation / Correct handling of UL grant / (De)activation by DCI format 2_9 | Rel-18 | C361 | UEs supporting 5GS and Cell DRX configuration activation and deactivation via DCI 2_9 | +| 7.1.1.14.2 | NES spatial domain adaptations | | | | +| 7.1.1.14.2.1 | NES spatial domain Type 1 adaptation / Periodic CSI reporting | Rel-18 | C400 | UEs supporting 5G Core and spatial domain adaptation with CSI feedback | +| 7.1.1.14.2.3 | NES Power domain adaptation / Semi-Periodic CSI reporting | Rel-18 | C401 | UEs supporting 5G Core and power domain adaptation with CSI feedback | +| 7.1.2 | RLC | | | | +| 7.1.2.2 | RLC Unacknowledged Mode | | | | +| 7.1.2.2.1 | UM RLC / Segmentation and reassembly / 6-bit SN / Segmentation Info (SI) field | Rel-15 | C05 | UEs supporting 5GS and RLC UM with 6-bit length of RLC sequence number | +| 7.1.2.2.2 | UM RLC / Segmentation and reassembly / 12-bit SN / Segmentation Info (SI) field | Rel-15 | C06 | UEs supporting 5GS and RLC UM with 12-bit length of RLC sequence number | +| 7.1.2.2.3 | UM RLC / 6-bit SN / Correct use of sequence numbering | Rel-15 | C05 | UEs supporting 5GS and RLC UM with 6-bit length of RLC sequence number | +| 7.1.2.2.4 | UM RLC / 12-bit SN / Correct use of sequence numbering | Rel-15 | C06 | UEs supporting 5GS and RLC UM with 12-bit length of RLC sequence number | +| 7.1.2.2.5 | UM RLC / Receive Window operation and t-Reassembly expiry | Rel-15 | C02 | UEs supporting 5GS and RLC UM Mode | +| 7.1.2.2.5a | NR NTN / UM RLC / t-Reassembly expiry / t-ReassemblyExt-r17 configured | Rel-17 | C322 | UEs supporting 5G Core and NR NTN access and RLC UM Mode | +| 7.1.2.2.6 | UM RLC / RLC re-establishment procedure | Rel-15 | C02 | UEs supporting 5GS and RLC UM Mode | +| 7.1.2.3 | RLC Acknowledged Mode | | | | +| 7.1.2.3.1 | AM RLC / 12-bit SN / Segmentation and reassembly / Segmentation Info (SI) field | Rel-15 | C07 | UEs supporting 5GS and RLC AM with 12-bit length of RLC sequence number | +| 7.1.2.3.2 | AM RLC / 18-bit SN / Segmentation and reassembly / Segmentation Info (SI) field | Rel-15 | C07A | UEs supporting 5GS and RLC AM with 18-bit length of RLC sequence number | +| 7.1.2.3.3 | AM RLC / 12-bit SN / Correct use of sequence numbering | Rel-15 | C07 | UEs supporting 5GS and RLC AM with 12-bit length of RLC sequence number | +| 7.1.2.3.4 | AM RLC / 18-bit SN / Correct use of sequence numbering | Rel-15 | C07A | UEs supporting 5GS and RLC and RLC AM with 18-bit length of RLC sequence number | +| 7.1.2.3.5 | AM RLC / 12-bit SN / Control of transmit window / Control of receive window | Rel-15 | C07 | UEs supporting 5GS and RLC AM with 12-bit length of RLC sequence number | + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-------------------------|-------------------------------------------------------------------------------------------| +| 7.1.2.3.5a | AM RLC / 18-bit SN / Control of transmit window / Control of receive window | Rel-15 | C07A | UEs supporting 5GS and RLC AM with 18-bit length of RLC sequence number | +| 7.1.2.3.6 | AM RLC / Polling for status | Rel-15 | R | UEs supporting 5GS | +| 7.1.2.3.7 | AM RLC / Receiver status triggers | Rel-15 | R | UEs supporting 5GS | +| 7.1.2.3.8 | AM RLC / Reconfiguration of RLC parameters by upper layers | Rel-15 | R | UEs supporting 5GS | +| 7.1.2.3.9 | AM RLC / Reassembling of AMD PDUs | Rel-15 | R | UEs supporting 5GS | +| 7.1.2.3.9a | NR NTN / AM RLC / t-Reassembly expiry / t-ReassemblyExt-r17 configured | Rel-17 | C309 | UEs supporting 5G Core and NR NTN access | +| 7.1.2.3.10 | AM RLC / Re-transmission of RLC PDU with and without re-segmentation | Rel-15 | R | UEs supporting 5GS | +| 7.1.2.3.11 | AM RLC / RLC re-establishment procedure | Rel-15 | R | UEs supporting 5GS | +| 7.1.3 | PDCP | | | | +| 7.1.3.1 | Maintenance of PDCP sequence numbers for radio bearers | | | | +| 7.1.3.1.1 | Maintenance of PDCP sequence numbers / User plane / 12-bit SN | Rel-15 | C08 | UEs supporting 5GS and 12-bit length of PDCP sequence number | +| 7.1.3.1.2 | Maintenance of PDCP sequence numbers / User plane / 18-bit SN | Rel-15 | C08A | UEs supporting 5GS and 18-bit length of PDCP sequence number | +| 7.1.3.2 | PDCP Integrity protection | | | | +| 7.1.3.2.1 | Integrity protection / Correct functionality of integrity algorithm SNOW3G / SRB / DRB | Rel-15 | R | UEs supporting 5GS | +| 7.1.3.2.2 | Integrity protection / Correct functionality of integrity algorithm AES / SRB / DRB | Rel-15 | R | UEs supporting 5GS | +| 7.1.3.2.3 | Integrity protection / Correct functionality of integrity algorithm ZUC / SRB / DRB | Rel-15 | C09 | UEs supporting 5GS and ZUC algorithm | +| 7.1.3.2.6 | Integrity protection / Correct functionality of UP integrity protection / multiple DRBs | Rel-17 | C286 | UEs supporting EN-DC and user plane integrity protection with EPS | +| 7.1.3.3 | PDCP Ciphering and deciphering | | | | +| 7.1.3.3.1 | Ciphering and deciphering / Correct functionality of encryption algorithm SNOW3G / SRB / DRB | Rel-15 | R | UEs supporting 5GS | +| 7.1.3.3.2 | Ciphering and deciphering / Correct functionality of encryption algorithm AES / SRB / DRB | Rel-15 | R | UEs supporting 5GS | +| 7.1.3.3.3 | Ciphering and deciphering / Correct functionality of encryption algorithm ZUC / SRB / DRB | Rel-15 | C09 | UEs supporting 5GS and ZUC algorithm | +| 7.1.3.4 | PDCP Handover | | | | +| 7.1.3.4.1 | PDCP handover / Lossless handover / PDCP sequence number maintenance / PDCP status report to convey the information on missing or acknowledged PDCP SDUs at handover / In-order delivery and duplicate elimination in the downlink | Rel-15 | R | UEs supporting 5GS | +| 7.1.3.4.2 | PDCP handover / Non-lossless handover / PDCP sequence number maintenance | Rel-15 | R | UEs supporting 5GS | +| 7.1.3.4.3 | PDCP handover / DAPS handover / Status reporting / Intra-frequency | Rel-16 | C101 | UEs supporting 5G Core and intra-frequency DAPS handover | +| 7.1.3.4.4 | PDCP handover / DAPS handover / Status reporting / Inter-frequency | | | | +| 7.1.3.4.4.1 | PDCP handover / DAPS handover / Status reporting / Inter-frequency / Intra-band non-contiguous | Rel-16 | C130 | UEs supporting 5G Core and inter-frequency DAPS handover on intra-band non-contiguous BC | +| 7.1.3.4.4.2 | PDCP handover / DAPS handover / Status reporting / Inter-frequency / Intra-band contiguous | Rel-16 | C130A | UEs supporting 5G Core and inter-frequency DAPS handover on intra-band contiguous BC | +| 7.1.3.5 | PDCP other | | | | +| 7.1.3.5.1 | PDCP Discard | Rel-15 | C02 | UEs supporting 5GS and RLC UM Mode | +| 7.1.3.5.1a | NR NTN / PDCP Discard / discardTimerExt2 configured | Rel-17 | C322 | UEs supporting 5G Core and NR NTN access and RLC UM Mode | +| 7.1.3.5.2 | PDCP Uplink Routing / Split DRB | Rel-15 | C10 | UEs supporting EN-DC and UL transmission via both MCG path and SCG path for the split DRB | +| | | | C97 | UEs supporting NR-DC and UL transmission via both MCG path and SCG path for the split DRB | +| | | | C194 | UEs supporting NE-DC and UL transmission via both MCG path and SCG path for the split DRB | +| 7.1.3.5.3 | PDCP Data Recovery | Rel-15 | C01 | UEs supporting EN-DC | +| | | | C80 | UEs supporting NR-DC | +| 7.1.3.5.4 | PDCP reordering / Maximum re-ordering delay below t-Reordering / t-Reordering timer operations | Rel-15 | R | UEs supporting 5GS | +| 7.1.3.5.5 | PDCP Duplication | Rel-15 | C62 | UEs supporting EN-DC and PDCP duplication | + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|----------------|------------------------------------------------------------------------------------------------------------------------|---------|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | | over split DRB | +| | | | C98 | UEs supporting NR-DC and PDCP duplication over split DRB | +| 7.1.3.5.6.1 | PDCP Duplication / 3 RLC entities / Intra-band Contiguous CA | Rel-16 | C104 | UEs supporting 5G Core and Intra-band contiguous CA and DL and UL NR CA with 3 carriers and PDCP duplication with more than two RLC entities | +| 7.1.3.5.6.2 | PDCP Duplication / 3 RLC entities / Intra-band non-Contiguous CA | Rel-16 | C181 | UEs supporting 5G Core and Intra-band non-contiguous CA and DL and UL NR CA with 3 carriers and PDCP duplication with more than two RLC entities | +| 7.1.3.5.7 | Ethernet header compression and decompression / Correct functionality of ethernet header compression and decompression | Rel-16 | C105 | UEs supporting 5GS and RLC UM Mode and PDCP ethernet header compression | +| 7.1.3.5.12 | PDCP SN gap report / Receive operation | Rel-18 | C410 | UEs supporting 5G Core and PDCP SN gap reporting | +| 7.1.3.6 | PDCP UDC | | | | +| 7.1.3.6.1 | PDCP UDC / No dictionary | Rel-17 | C235 | UEs supporting 5GS and uplink data compression operation | +| 7.1.3.6.2 | PDCP UDC / Pre-defined dictionary | Rel-17 | C236 | UEs supporting 5GS and uplink data compression operation and UL data compression with SIP static dictionary | +| 7.1.3.6.3 | PDCP UDC / checksum error / Reset | Rel-17 | C235 | UEs supporting 5GS and uplink data compression operation | +| 7.1.3.6.4 | PDCP UDC/ Handover/ Intra-frequency | Rel-17 | C271 | UEs supporting 5GS and uplink data compression operation and continuation of uplink data compression protocol operation | +| 7.1.3.6.5 | PDCP UDC/ Handover/ Inter-frequency | Rel-17 | C271 | UEs supporting 5GS and uplink data compression operation and continuation of uplink data compression protocol operation | +| 7.1.3.6.6 | PDCP UDC/ RRC resume | Rel-17 | C271 | UEs supporting 5GS and uplink data compression operation and continuation of uplink data compression protocol operation | +| 7.1.3.6.7 | PDCP UDC/ RRC reestablishment | Rel-17 | C271 | UEs supporting 5GS and uplink data compression operation and continuation of uplink data compression protocol operation | +| 7.1.3.6.8 | PDCP UDC/ PSCell addition / SCG DRB with UDC configuration/ NR-DC | Rel-17 | C272 | UEs supporting NR-DC and uplink data compression operation | +| 7.1.3.6.9 | PDCP UDC/ PSCell addition / SCG DRB with UDC configuration/ NE-DC | Rel-17 | C273 | UEs supporting NE-DC and uplink data compression operation | +| 7.1.4 | SDAP | | | | +| 7.1.4.1 | SDAP Data Transfer and PDU Header Handling UL/DL | Rel-15 | C21A | UEs supporting 5G Core and reflective QoS | +| 7.1.4.2 | SDAP Data Transfer handling without Header UL/DL | Rel-15 | C21 | UEs supporting 5G Core | + +**Table 4.1-2b: Additional Information of Applicability of Protocol conformance Layer 2 test cases, ref. TS 38.523-1 [2]** + +| Clause | Specific ICS | Specific IXIT | Number of TC Executions | Release other RAT | +|------------------|------------------------------------------------------------------------------------|---------------------------------|-------------------------|-------------------| +| 7 | | | | | +| 7.1 | | | | | +| 7.1.1 | | | | | +| 7.1.1.1 | | | | | +| 7.1.1.1.4 | pc_csi_RS_CFRA_ForHO,
pc_maxNumberCSI_RS_BFD,
pc_maxNumberCSI_RS_SSB_
CBD | | | | +| 7.1.1.2 | | | | | +| 7.1.1.2.8 | | | | | +| 7.1.1.2.8.1 | pc_dl_SchedulingOffset_PDS
CH_TypeA | px_harqFeedbackType_DCI_
1_3 | | | +| 7.1.1.2.8.2 | pc_dl_SchedulingOffset_PDS
CH_TypeA | px_harqFeedbackType_DCI_
1_3 | | | +| 7.1.1.2.8.3 | pc_dl_SchedulingOffset_PDS
CH_TypeA | px_harqFeedbackType_DCI_
1_3 | | | +| 7.1.1.2.9 | | | | | +| 7.1.1.2.9.1 | pc_dl_SchedulingOffset_PDS
CH_TypeA | px_harqFeedbackType_DCI_
1_3 | | | + +| | | | | | +|-------------|----------------------------------------|---------------------------------|--|--| +| 7.1.1.2.9.2 | pc_dl_SchedulingOffset_PDS
CH_TypeA | px_harqFeedbackType_DCI_
1 3 | | | +| 7.1.1.2.9.3 | pc_dl_SchedulingOffset_PDS
CH_TypeA | px_harqFeedbackType_DCI_
1 3 | | | + +| | | | | | +|------------------|----------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|--|--| +| 7.1.1.3 | | | | | +| 7.1.1.3.2b | pc_configuredUL_GrantType1 | | | | +| 7.1.1.4 | | | | | +| 7.1.1.4.1 | | | | | +| 7.1.1.4.1.3 | pc_dynamicSwitchRA_Type0_1_PDSCH | | | | +| 7.1.1.4.1.4 | pc_dynamicSwitchRA_Type0_1_PDSCH | | | | +| 7.1.1.4.2 | | | | | +| 7.1.1.4.2.3 | pc_dynamicSwitchRA_Type0_1_PUSCH | | | | +| 7.1.1.4.2.4 | pc_dynamicSwitchRA_Type0_1_PUSCH | | | | +| 7.1.1.6 | | | | | +| 7.1.1.6.4 | pc_um_WithShortSN | | | | +| 7.1.1.7 | | | | | +| 7.1.1.7.1 | | | | | +| 7.1.1.7.1.1 | pc_UL_NR_CA_2CC or pc_EN_DC_NR_UL_2CC | | | | +| 7.1.1.7.1.2 | pc_UL_NR_CA_2CC or pc_EN_DC_NR_UL_2CC | | | | +| 7.1.1.7.1.3 | pc_UL_intra_non_contiguous_CA_NR_FR1_Class_(2A) or pc_UL_intra_non_contiguous_CA_NR_FR2_Class_(2A) | | | | +| 7.1.1.7.2 | | | | | +| 7.1.1.7.2.1 | | px_harqFeedbackType_DCI_1_3
px_coScheduledCellIndicationScheme_DCI_1_3 | | | +| 7.1.1.7.2.2 | | px_harqFeedbackType_DCI_1_3
px_coScheduledCellIndicationScheme_DCI_1_3 | | | +| 7.1.1.7.2.3 | | px_harqFeedbackType_DCI_1_3
px_coScheduledCellIndicationScheme_DCI_1_3 | | | +| 7.1.1.7.3 | | | | | +| 7.1.1.7.3.1 | pc_multiCell_PDSCH_DCI_1_3_SameSCS_r18 | px_harqFeedbackType_DCI_1_3
px_coScheduledCellIndicationScheme_DCI_1_3
px_coScheduledCellIndicationScheme_DCI_0_3 | | | +| 7.1.1.7.3.2 | pc_multiCell_PDSCH_DCI_1_3_SameSCS_r18 | px_harqFeedbackType_DCI_1_3
px_coScheduledCellIndicationScheme_DCI_1_3
px_coScheduledCellIndicationScheme_DCI_0_3 | | | +| 7.1.1.7.3.3 | pc_multiCell_PDSCH_DCI_1_3_SameSCS_r18 | px_harqFeedbackType_DCI_1_3
px_coScheduledCellIndicationScheme_DCI_1_3
px_coScheduledCellIndicationScheme_DCI_0_3 | | | +| 7.1.1.7.4 | | | | | +| 7.1.1.7.4.1 | | px_harqFeedbackType_DCI_1_3
px_coScheduledCellIndicationScheme_DCI_1_3 | | | +| 7.1.1.7.4.2 | | px_harqFeedbackType_DCI_1_3
px_coScheduledCellIndicationScheme_DCI_1_3 | | | +| 7.1.1.7.4.3 | | px_harqFeedbackType_DCI_1_3
px_coScheduledCellIndicationScheme_DCI_1_3 | | | +| 7.1.1.7.5 | | | | | + +| | | | | | +|-----------------|----------------------------------------|-------------------------------------------------------------------------------------------------------------------------|--|---------------| +| 7.1.1.7.5.1 | pc_multiCell_PDSCH_DCI_1_3_SameSCS_r18 | px_harqFeedbackType_DCI_1_3
px_coScheduledCellIndicationScheme_DCI_1_3
px_coScheduledCellIndicationScheme_DCI_0_3 | | | +| 7.1.1.7.5.2 | pc_multiCell_PDSCH_DCI_1_3_SameSCS_r18 | px_harqFeedbackType_DCI_1_3
px_coScheduledCellIndicationScheme_DCI_1_3
px_coScheduledCellIndicationScheme_DCI_0_3 | | | +| 7.1.1.7.5.3 | pc_multiCell_PDSCH_DCI_1_3_SameSCS_r18 | px_harqFeedbackType_DCI_1_3
px_coScheduledCellIndicationScheme_DCI_1_3
px_coScheduledCellIndicationScheme_DCI_0_3 | | | +| 7.1.1.12 | | | | | +| 7.1.1.12.3 | | | | Rel-15 E-UTRA | +| 7.1.1.13 | | | | | +| 7.1.1.13.1 | pc_logicalChannelSR_DelayTimer | | | | +| 7.1.1.13.2 | pc_logicalChannelSR_DelayTimer | | | | +| 7.1.1.13.5 | pc_ra_SDT_r17 | | | | +| 7.1.2 | | | | | +| 7.1.2.2 | | | | | +| 7.1.2.2.5 | pc_um_WithShortSN | | | | +| 7.1.2.2.6 | pc_um_WithShortSN | | | | +| 7.1.3 | | | | | +| 7.1.3.2.1 | pc_srb3 | | | | +| | | | | | +| | | | | | +| | | | | | + +Table 4.1-3a: Applicability of Protocol conformance RRC test cases, ref. TS 38.523-1 [2] + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|------------|---------------------------------------------------------------------------------------------------------------|-----------------------|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 8 | RRc | | | | +| 8.1 | NR RRc | | | | +| 8.1.1 | RRc connection management procedures | | | | +| 8.1.1.1 | Paging | | | | +| 8.1.1.1.1 | RRc / Paging for connection / Multiple paging records | Rel-15 | C21 | UEs supporting 5G Core | +| 8.1.1.1.2 | RRc / Paging for connection / Shared network environment | Rel-15 | C21 | UEs supporting 5G Core | +| 8.1.1.1a | Paging Early Indication and Subgrouping | | | | +| 8.1.1.1a.1 | Paging Early Indication with Subgrouping / RRc_IDLE / lastUsedCellOnly not configured / Subgroup ID selection | Rel-17 | C224 | UEs supporting 5G Core and PEI | +| 8.1.1.1a.2 | Paging Early Indication with Subgrouping / RRc_INACTIVE / lastUsedCellOnly configured | Rel-17 | C239 | UEs supporting 5G Core and RRc_INACTIVE and PEI | +| 8.1.1.1a.3 | Paging Early Indication without Subgrouping / RRc_IDLE | Rel-17 | C224 | UEs supporting 5G Core and PEI | +| 8.1.1.2 | RRc connection establishment | | | | +| 8.1.1.2.1 | RRc connection establishment / Return to idle state after T300 expiry | Rel-15 | C21 | UEs supporting 5G Core | +| 8.1.1.2.2 | Void | | | | +| 8.1.1.2.3 | RRc connection establishment / RRc Reject with wait time | Rel-15 | C21 | UEs supporting 5G Core | +| 8.1.1.2.4 | RRc connection establishment / Extended value, spare fields and non-critical extensions in SI | Rel-15 to Rel-17 only | C21 | UEs supporting 5G Core | +| 8.1.1.2.5 | RRc connection establishment / MUSIM / early indication | Rel-18 | C384 | UEs supporting 5G Core and providing MUSIM assistance information with temporary capability restriction and capability restriction indication and Indicating to the Network A that its capabilities are temporarily restricted in RRcSetupComplete message while the UE is already in RRc_CONNECTED state in Network B. | +| 8.1.1.3 | RRc release | | | | +| 8.1.1.3.1 | RRc connection release / Redirection to another NR frequency | Rel-15 | C21 | UEs supporting 5G Core | +| 8.1.1.3.2 | RRc connection release / Redirection from NR to E-UTRA | Rel-15 | C32 | UEs supporting 5G Core and E-UTRA | +| 8.1.1.3.3 | RRc connection release / Success / With priority information | Rel-15 | C21 | UEs supporting 5G Core | +| 8.1.1.3.4 | RRc connection release / Success / With priority information / E-UTRA | Rel-15 | C26 | UEs supporting 5GS and E-UTRA | +| 8.1.1.3.5 | Void | | | | +| 8.1.1.3.6 | Void | | | | +| 8.1.1.3.7 | RRc connection release / Success / Deprioritisation / Frequency / T325 expiry | Rel-15 | C133 | UEs supporting 5G Core and RRc connection release with Deprioritisation | +| 8.1.1.3.7a | RRc connection release / Success / Deprioritisation / NR / T325 expiry | Rel-15 | C148 | UEs supporting 5G Core and E-UTRA and RRc connection release with Deprioritisation | +| 8.1.1.3.7b | RRc connection release / Success / Deprioritisation / Deletion of Stored deprioritisation request | Rel-15 | C161 | UEs supporting 5G Core and RRc connection release with Deprioritisation and ManualModeNetworkSelectionException | +| 8.1.1.3.8 | RRc connection release / Redirection to another NR frequency / MPS Priority Indication | Rel-16 | C274 | UEs supporting 5G Core and RRc Connection release with MPS priority indication | + +| | | | | | +|-------------|----------------------------------------------------------------------------------------------------------------|--------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 8.1.1.3.9 | RRc connection release / Success / With slice specific cell reselection information | Rel-17 | C240 | UEs supporting 5G Core and slice based cell reselection | +| 8.1.1.3.10 | RRc connection release / Redirection from NR to E-UTRA / MPS Priority Indication | Rel-16 | C314 | UEs supporting 5G Core and E-UTRA and RRc Connection release with MPS priority indication | +| 8.1.1.4 | RRc resume | | | | +| 8.1.1.4.1 | RRc resume / Suspend-Resume / RNA update / Success | Rel-15 | C109 | UEs supporting 5G Core and RRc_INACTIVE | +| 8.1.1.4.2 | RRc resume / Suspend-Resume / RRc setup / T319 expiry | Rel-15 | C109 | UEs supporting 5G Core and RRc_INACTIVE | +| 8.1.1.4.3 | Void | | | | +| 8.1.1.4.4 | RRc resume / Suspend-Resume / RRc reconfiguration / Active MCG SCell addition / Intra-band Contiguous CA | Rel-16 | C154 | UEs supporting 5G Core and intra-band contiguous CA and RRc_INACTIVE and direct NR MCG SCell activation | +| 8.1.1.4.5 | RRc resume / Suspend-Resume / RRc reconfiguration / Active MCG SCell addition / Intra-band non-Contiguous CA | Rel-16 | C155 | UEs supporting 5G Core and intra-band non-contiguous CA and RRc_INACTIVE and direct NR MCG SCell activation | +| 8.1.1.4.6 | RRc resume / Suspend-Resume / RRc reconfiguration / Active MCG SCell addition / Inter-band CA | Rel-16 | C156 | UEs supporting 5G Core and inter-band CA and RRc_INACTIVE and direct NR MCG SCell activation | +| 8.1.1.4.7 | RRc resume / Suspend-Resume / RRc reconfiguration / Active SCG SCell addition / Intra-band Contiguous CA | Rel-16 | C221 | UEs supporting 5G Core and intra-band contiguous CA and RRc_INACTIVE and direct NR SCG SCell activation and NR-DC | +| 8.1.1.4.8 | RRc resume / Suspend-Resume / RRc reconfiguration / Active SCG SCell addition / Intra-band non-Contiguous CA | Rel-16 | C222 | UEs supporting 5G Core and intra-band non-contiguous CA and RRc_INACTIVE and direct NR SCG SCell activation and NR-DC | +| 8.1.1.4.9 | RRc resume / Suspend-Resume / RRc reconfiguration / Active SCG SCell addition / Inter-band CA | Rel-16 | C223 | UEs supporting 5G Core and inter-band CA and RRc_INACTIVE and direct NR SCG SCell activation and NR-DC | +| 8.1.1.4.10 | RRc resume / MUSIM / early indication | Rel-18 | C392 | UEs supporting 5G Core and RRc_INACTIVE and providing MUSIM assistance information with temporary capability restriction and capability restriction indication and Indicating to the Network A that its capabilities are temporarily restricted in RRcResumeComplete message while the UE is already in RRc_CONNECTED state in Network B. | +| 8.1.2 | RRc reconfiguration | | | | +| 8.1.2.1 | Radio bearer establishment / reconfiguration / release | | | | +| 8.1.2.1.1 | RRc reconfiguration / DRB / SRB / Establishment / Modification / Release / Success | Rel-15 | C21 | UEs supporting 5G Core | +| 8.1.2.1.2 | RRc reconfiguration / RRc bearer establishment / uplinkTxDirectCurrentList | Rel-15 | C21 | UEs supporting 5G Core | +| 8.1.2.1.3 | Void | | | | +| 8.1.2.1.4 | RRc reconfiguration / Dedicated RLF timer | Rel-15 | C21 | UEs supporting 5GCore | +| 8.1.2.1.5 | NR CA / RRc reconfiguration / SCell addition / modification / release / Success | | | | +| 8.1.2.1.5.1 | NR CA / RRc reconfiguration / SCell addition / modification / release / Success / Intra-band Contiguous CA | Rel-15 | C41 | UEs supporting 5G Core and intra-band contiguous CA | +| 8.1.2.1.5.2 | NR CA / RRc reconfiguration / SCell addition / modification / release / Success / Inter-band CA | Rel-15 | C42 | UEs supporting 5G Core and inter-band CA | +| 8.1.2.1.5.3 | NR CA / RRc reconfiguration / SCell addition / modification / release / Success / Intra-band non-contiguous CA | Rel-15 | C43 | UEs supporting 5G Core and intra-band non-contiguous CA | + +| | | | | | +|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|------|--------------------------------------------------------------------------------------------| +| 8.1.2.1.5.4 | NR CA / RRC reconfiguration / SCell addition / modification / release / Success / Active MCG SCell addition / Intra-band Contiguous CA | Rel-16 | C226 | UEs supporting 5G Core and direct NR MCG SCell activation and intra-band contiguous CA | +| 8.1.2.1.5.5 | NR CA / RRC reconfiguration / SCell addition / modification / release / Success / Active MCG SCell addition / Intra-band non-contiguous CA | Rel-16 | C227 | UEs supporting 5G Core and direct NR MCG SCell activation and intra-band non-contiguous CA | +| 8.1.2.1.5.6 | NR CA / RRC reconfiguration / SCell addition / modification / release / Success / Active MCG SCell addition / Inter-band CA | Rel-16 | C228 | UEs supporting 5G Core and direct NR MCG SCell activation and inter-band CA | +| 8.1.2.1.6 | RRC reconfiguration/ MUSIM / MUSIM- gap / Addition / Modification / Release | Rel-17 | C246 | UEs supporting 5G Core and MUSIM gap feature | +| 8.1.3 | Measurement configuration control and reporting | | | | +| 8.1.3.1 | Intra NR measurements | | | | +| 8.1.3.1.1 | Measurement configuration control and reporting / Intra NR measurements / Event A1 / Event A2 | Rel-15 | C21 | UEs supporting 5G Core | +| 8.1.3.1.2 | Measurement configuration control and reporting / Event A3 / Measurement of Neighbour NR cell / Intra-frequency measurements | Rel-15 | C21 | UEs supporting 5G Core | +| 8.1.3.1.3 | Measurement configuration control and reporting / Event A3 / Measurement of Neighbour NR cell / Inter-frequency measurements | Rel-15 | C21 | UEs supporting 5G Core | +| 8.1.3.1.4 | Measurement configuration control and reporting / Event A3 / Measurement of Neighbour NR cell / Inter-band measurements | Rel-15 | C94 | UEs supporting 5G Core and multiple NR bands | +| 8.1.3.1.5 | Measurement configuration control and reporting / Event A4 / Measurement of Neighbour NR cell / Intra-frequency measurements | Rel-15 | C21 | UEs supporting 5G Core | +| 8.1.3.1.6 | Measurement configuration control and reporting / Event A4 / Measurement of Neighbour NR cell / Inter-frequency measurements | Rel-15 | C21 | UEs supporting 5G Core | +| 8.1.3.1.7 | Measurement configuration control and reporting / Event A4 / Measurement of Neighbour NR cell / Inter-band measurements | Rel-15 | C94 | UEs supporting 5G Core and multiple NR bands | +| 8.1.3.1.8 | Measurement configuration control and reporting / Event A5 / Measurement of Neighbour NR cell / Intra-frequency measurements | Rel-15 | C21 | UEs supporting 5G Core | +| 8.1.3.1.9 | Measurement configuration control and reporting / Event A5 / Measurement of Neighbour NR cell / Inter-frequency measurements | Rel-15 | C21 | UEs supporting 5G Core | +| 8.1.3.1.10 | Measurement configuration control and reporting / Event A5 / Measurement of Neighbour NR cell / Inter-band measurements | Rel-15 | C94 | UEs supporting 5G Core and multiple NR bands | +| 8.1.3.1.11 | Measurement configuration control and reporting / Intra NR measurements / Two simultaneous events A3 (intra and inter-frequency measurements) / RSRQ based measurements | Rel-15 | C21 | UEs supporting 5GCore | +| 8.1.3.1.12 | Measurement configuration control and reporting / Intra NR measurements / Two simultaneous events A5 (intra and inter-frequency measurements) / SINR based measurements | Rel-15 | C40 | UEs supporting 5G Core and SS-SINR measurements | + +| | | | | | +|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------|--------|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 8.1.3.1.13 | Measurement configuration control and reporting / SS/PBCH block based / CSI-RS based intra-frequency measurements / Measurement of Neighbour NR cell | Rel-15 | C52 | UEs supporting 5G Core and NR measurements and Event A triggered reporting and (NR Intra-frequency and Inter frequency measurements and at least periodical reporting) and CSI-RSRP and CSI-RSRQ measurement | +| 8.1.3.1.14 | Void | | | | +| 8.1.3.1.14A | Measurement configuration control and reporting / SS/PBCH block based / CSI-RS based inter-frequency measurements / Measurement of Neighbour NR cell | Rel-15 | C52 | UEs supporting 5G Core and NR measurements and Event A triggered reporting and (NR Intra-frequency and Inter frequency measurements and at least periodical reporting) and CSI-RSRP and CSI-RSRQ measurement | +| 8.1.3.1.15 | Void | | | | +| 8.1.3.1.15A | Measurement configuration control and reporting / Intra NR measurements / Exclude-listed cells | Rel-15 | C21 | UEs supporting 5G Core | +| 8.1.3.1.16 | Measurement configuration control and reporting / Intra NR measurements / Allow-listed cells | Rel-15 | C21 | UEs supporting 5G Core | +| 8.1.3.1.17 | NR CA / Measurement configuration control and reporting / Intra NR measurements / Event A6 | | | | +| 8.1.3.1.17.1 | NR CA / Measurement configuration control and reporting / Intra NR measurements / Event A6 / Intra-band Contiguous CA | Rel-15 | C41 | UEs supporting 5G Core and intra-band contiguous CA | +| 8.1.3.1.17.2 | NR CA / Measurement configuration control and reporting / Intra NR measurements / Event A6 / Inter-band CA | Rel-15 | C42 | UEs supporting 5G Core and inter-band CA | +| 8.1.3.1.17.3 | NR CA / Measurement configuration control and reporting / Intra NR measurements / Event A6 / Intra-band non-Contiguous CA | Rel-15 | C43 | UEs supporting 5G Core and intra-band non-contiguous CA | +| 8.1.3.1.18 | NR CA / Measurement configuration control and reporting / Intra NR measurements / Additional measurement reporting | | | | +| 8.1.3.1.18.1 | NR CA / Measurement configuration control and reporting / Intra NR measurements / Additional measurement reporting / Intra-band Contiguous CA | Rel-15 | C41 | UEs supporting 5G Core and intra-band contiguous CA | +| 8.1.3.1.18.2 | NR CA / Measurement configuration control and reporting / Intra NR measurements / Additional measurement reporting / Inter-band CA | Rel-15 | C42 | UEs supporting 5G Core and inter-band CA | +| 8.1.3.1.18.3 | NR CA / Measurement configuration control and reporting / Intra NR measurements / Additional measurement reporting / Intra-band non-Contiguous CA | Rel-15 | C43 | UEs supporting 5G Core and intra-band non-contiguous CA | +| 8.1.3.1.19 | Measurement configuration control and reporting / Inter-frequency measurements/ SFTD | Rel-15 | C150 | UEs supporting 5G Core and SFTD measurements between NR PCell and NR neighbour cell | +| 8.1.3.1.20 | Measurement configuration control and reporting / Measurement Gaps / gapFR1 | Rel-15 | C49 | UE supporting 5G Core and two independent measurement gap configurations for FR1 and FR2 | +| 8.1.3.1.21 | Measurement configuration control and reporting / Measurement Gaps / gapFR2 | Rel-15 | C49 | UE supporting 5G Core and two independent measurement gap configurations for FR1 and FR2 | +| 8.1.3.1.23 | Measurement configuration control and reporting / Intra NR measurements / Periodic reporting / Continuation of the measurements after RRC Resume | Rel-15 | C21 | UEs supporting 5G Core | + +| | | | | | +|------------|---------------------------------------------------------------------------------------------------------------------------------------------|--------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 8.1.3.1.24 | Measurement configuration control and reporting for voice / QoE | Rel-17 | C349 | UEs supporting 5G Core and NR QoE Measurement Collection for MTSI services | +| 8.1.3.1.25 | Measurement configuration control and reporting for video / QoE | Rel-17 | C350 | UEs supporting 5G Core and NR QoE Measurement Collection for MTSI services and MTSI video | +| 8.1.3.1.26 | NR NTN / Measurement configuration control and reporting / Event D1 / Measurement of Neighbour NR cell | Rel-17 | C323 | UEs supporting 5G Core and NR NTN access and Event D1 and NTN features in NGSO scenario | +| 8.1.3.1.27 | NR NTN Enhancements / Measurement configuration control and reporting / Event D2 | Rel-18 | C409 | UEs supporting 5G Core and NR NTN access and Event D2 | +| 8.1.3.2 | Inter-RAT measurements | | | | +| 8.1.3.2.1 | Measurement configuration control and reporting / Inter-RAT measurements / Event B1 / Measurement of E-UTRA cells | Rel-15 | C31 | UEs supporting 5G Core and Inter-RAT E-UTRA measurements and Event B triggered reporting | +| 8.1.3.2.2 | Measurement configuration control and reporting / Inter-RAT measurements / Event B2 / Measurement of E-UTRA cells | Rel-15 | C31 | UEs supporting 5G Core and Inter-RAT E-UTRA measurements and Event B triggered reporting | +| 8.1.3.2.3 | Measurement configuration control and reporting / Inter-RAT measurements / Event B2 / Measurement of E-UTRA cells / RSRQ based measurements | Rel-15 | C31 | UEs supporting 5G Core and Inter-RAT E-UTRA measurements and Event B triggered reporting | +| 8.1.3.2.4 | Measurement configuration control and reporting / Inter-RAT measurements / Event B2 / Measurement of E-UTRA cells / SINR based measurements | Rel-15 | C50 | UEs supporting 5G Core and Inter-RAT E-UTRA measurements and Event B triggered reporting and E-UTRA RS-SINR measurements | +| 8.1.3.2.5 | Void | | | | +| 8.1.3.2.6 | Measurement configuration control and reporting / Inter-RAT measurements / Event B1 / NR to UTRA | Rel-16 | C127 | UEs supporting 5G Core and UTRA and NR to UTRA-FDD CELL_DCH CS handover | +| 8.1.3.2.7 | Measurement configuration control and reporting / Inter-RAT measurements / Event B2 / NR to UTRA | Rel-16 | C127 | UEs supporting 5G Core and UTRA and NR to UTRA-FDD CELL_DCH CS handover | +| 8.1.3.2.8 | Measurement configuration control and reporting / Inter-RAT measurements / Periodic reporting / NR to UTRA | Rel-16 | C127 | UEs supporting 5G Core and UTRA and NR to UTRA-FDD CELL_DCH CS handover | +| 8.1.3.3 | Measurement for self-optimized networks | | | | +| 8.1.3.3.1 | Measurement configuration control and reporting / CGI reporting of NR cell | Rel-15 | C59 | UEs supporting 5G Core and Support acquisition of relevant information from a neighbouring intra-frequency or inter-frequency NR cell by reading the SI of the neighbouring cell and reporting the acquired information to the network as specified in TS 38.331 [9] when EN-DC is not configured. | +| 8.1.3.3.2 | Measurement configuration control and reporting / CGI reporting of E-UTRA cell | Rel-15 | C60 | UEs supporting 5G Core and Support acquisition of relevant information from a neighbouring E-UTRA cell by reading the SI of the neighbouring cell and reporting the acquired information to the network as specified in TS 38.331 [9] when the EN-DC is not configured. | +| 8.1.3.4 | Measurement relaxation | | | | +| 8.1.3.4.1 | Void | | | | +| 8.1.4 | Handover | | | | +| 8.1.4.1 | Intra NR handover | | | | +| 8.1.4.1.1 | Void | | | | +| 8.1.4.1.2 | Intra NR handover / Success / Inter-frequency | Rel-15 | C21 | UEs supporting 5G Core | +| 8.1.4.1.3 | Void | | | | +| 8.1.4.1.4 | Void | | | | +| 8.1.4.1.5 | Intra NR handover / Failure / Re-establishment successful | Rel-15 | C21 | UEs supporting 5G Core | + +| | | | | | +|-------------|----------------------------------------------------------------------------------------------------------------------|--------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 8.1.4.1.6 | Intra NR handover / Failure / Re-establishment failure | Rel-15 | C21 | UEs supporting 5G Core | +| 8.1.4.1.7 | NR CA / Intra NR handover / Success / PCell Change and SCell addition / SCell release | | | | +| 8.1.4.1.7.1 | NR CA / Intra NR handover / Success / PCell Change and SCell addition / SCell release / Intra-band Contiguous CA | Rel-15 | C41 | UEs supporting 5G Core and intra-band contiguous CA | +| 8.1.4.1.7.2 | NR CA / Intra NR handover / Success / PCell Change and SCell addition / SCell release / Inter-band CA | Rel-15 | C42 | UEs supporting 5G Core and inter-band CA | +| 8.1.4.1.7.3 | NR CA / Intra NR handover / Success / PCell Change and SCell addition / SCell release / Intra-band non-contiguous CA | Rel-15 | C43 | UEs supporting 5G Core and intra-band non-contiguous CA | +| 8.1.4.1.8 | NR CA / Intra NR handover / Success / PCell Change / SCell no Change | | | | +| 8.1.4.1.8.1 | NR CA / Intra NR handover / Success / PCell Change / SCell no Change / Intra-band Contiguous CA | Rel-15 | C41 | UEs supporting 5G Core and intra-band contiguous CA | +| 8.1.4.1.8.2 | NR CA / Intra NR handover / Success / PCell Change / SCell no Change / Inter-band CA | Rel-15 | C42 | UEs supporting 5G Core and inter-band CA | +| 8.1.4.1.8.3 | NR CA / Intra NR handover / Success / PCell Change / SCell no Change / Intra-band non-contiguous CA | Rel-15 | C43 | UEs supporting 5G Core and intra-band non-contiguous CA | +| 8.1.4.1.9 | NR CA / Intra NR handover / Failure / Re-establishment successful | | | | +| 8.1.4.1.9.1 | NR CA / Intra NR handover / Failure / Re-establishment successful / Intra-band Contiguous CA | Rel-15 | C41 | UEs supporting 5G Core and intra-band contiguous CA | +| 8.1.4.1.9.2 | NR CA / Intra NR handover / Failure / Re-establishment successful / Inter-band CA | Rel-15 | C42 | UEs supporting 5G Core and inter-band CA | +| 8.1.4.1.9.3 | NR CA / Intra NR handover / Failure / Re-establishment successful / Intra-band non-contiguous CA | Rel-15 | C43 | UEs supporting 5G Core and intra-band non-contiguous CA | +| 8.1.4.1.10 | eCall Only mode / Intra NR handover / Success / Inter-frequency | Rel-16 | C184 | UEs supporting 5G Core and IMS eCall Only type of emergency services over 5GS and Automatic type of eCall initiation | +| 8.1.4.2 | Inter-RAT handover | | | | +| 8.1.4.2.1 | Inter-RAT handover from NR | | | | +| 8.1.4.2.1.1 | Inter-RAT handover / From NR to E-UTRA / Success | Rel-15 | C32 | UEs supporting 5G Core and E-UTRA | +| 8.1.4.2.1.2 | Inter-RAT handover / From NR to EN-DC / Success | Rel-16 | C96 | UEs supporting 5G Core and EN-DC and inter-RAT Handover from NR to EN-DC | +| 8.1.4.2.2 | Inter-RAT handover to NR | | | | +| 8.1.4.2.2.1 | Inter-RAT handover / From E-UTRA to NR / Success | Rel-15 | C99 | UEs supporting 5GS and E-UTRA and (inter-RAT Handover to NR FR1 TDD from EUTRA connected to EPC or inter-RAT Handover to NR FR1 FDD from EUTRA connected to EPC or inter-RAT Handover to NR FR2 TDD from EUTRA connected to EPC) | +| 8.1.4.3 | DAPS handover | | | | +| 8.1.4.3.1 | DAPS handover with key change / Success / Intra-frequency | Rel-16 | C101 | UEs supporting 5G Core and intra-frequency DAPS handover | +| 8.1.4.3.2 | DAPS handover / HO Failure and source link available / HO Success and RLF in source / Intra-frequency | Rel-16 | C101 | UEs supporting 5G Core and intra-frequency DAPS handover | +| 8.1.4.3.4 | DAPS handover with key change / Success / Inter-frequency | | | | +| 8.1.4.3.4.1 | DAPS handover with key change / Success / Inter-frequency / Intra-band non-contiguous | Rel-16 | C130 | UEs supporting 5G Core and inter-frequency DAPS handover on intra-band non-contiguous BC | + +| | | | | | +|-------------|-----------------------------------------------------------------------------------------------------------------------------------|--------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 8.1.4.3.4.2 | DAPS handover with key change / Success / Inter-frequency / Intra-band contiguous | Rel-16 | C130A | UEs supporting 5G Core and inter-frequency DAPS handover on intra-band contiguous BC | +| 8.1.4.3.5 | DAPS handover / HO Failure and source link available / HO Success and RLF in source / Inter-frequency | | | | +| 8.1.4.3.5.1 | DAPS handover / HO Failure and source link available / HO Success and RLF in source / Inter-frequency / Intra-band non-contiguous | Rel-16 | C130 | UEs supporting 5G Core and inter-frequency DAPS handover on intra-band non-contiguous BC | +| 8.1.4.3.5.2 | DAPS handover / HO Failure and source link available / HO Success and RLF in source / Inter-frequency / Intra-band contiguous | Rel-16 | C130A | UEs supporting 5G Core and inter-frequency DAPS handover on intra-band contiguous BC | +| 8.1.4.4 | Conditional handover | | | | +| 8.1.4.4.1 | Conditional handover / Success / A3 / A5 / A3+A5 | Rel-16 | C116 | UEs supporting 5G Core and conditional handover and supporting 2 trigger events for same execution condition | +| 8.1.4.4.2 | Conditional handover / modify conditional handover configuration | Rel-16 | C115 | UEs supporting 5G Core and conditional handover | +| 8.1.4.4.3 | Conditional handover / Failure | Rel-16 | C117 | UEs supporting 5G Core and conditional handover and conditional handover during re-establishment procedure when the selected cell is configured as candidate cell for condition handover | +| 8.1.4.4.4 | Conditional handover / legacy Handover / legacy Handover Failure | Rel-16 | C115 | UEs supporting 5G Core and conditional handover | +| 8.1.4.4.5 | NR NTN / Conditional handover / Success / CondEventA4 | Rel-17 | C335 | UEs supporting 5G Core and NR NTN access and Event A4 based conditional handover in NTN bands | +| 8.1.4.4.6 | NR NTN / Conditional handover / Success / CondEventT1 | Rel-17 | C336 | UEs supporting 5G Core and NR NTN access and time based conditional handover | +| 8.1.4.4.7 | NR NTN / Conditional handover / Success / CondEventD1 | Rel-17 | C337 | UEs supporting 5G Core and NR NTN access and location based conditional handover and NTN features in NGSO scenario | +| 8.1.5 | RRc others | | | | +| 8.1.5.1 | UE capability transfer | | | | +| 8.1.5.1.1 | UE Capability transfer / Success | Rel-15 | C21 | UEs supporting 5G Core | +| 8.1.5.2 | SI change / On-demand SIB | | | | +| 8.1.5.2.1 | Void | | | | +| 8.1.5.2.2 | SI change / Notification of BCCH modification / Short message for SI update in NR RRC_CONNECTED state | Rel-15 | C21 | UEs supporting 5G Core | +| 8.1.5.2.3 | eDRX / IDLE / Paging for notification of BCCH modification | Rel-17 | C210 | UEs supporting 5G Core and eDRX in RRC_IDLE | +| 8.1.5.3 | PWS notification | | | | +| 8.1.5.3.1 | PWS notification / PWS reception in NR RRC_IDLE state | Rel-15 | C35 | UEs supporting 5G Core and (ETWS reception or CMAS reception) | +| 8.1.5.3.2 | PWS notification / PWS reception in NR RRC_INACTIVE state | Rel-15 | C111 | UEs supporting 5G Core and (ETWS reception or CMAS reception) and RRC_INACTIVE | +| 8.1.5.3.3 | PWS notification / PWS reception in NR RRC_CONNECTED state | Rel-15 | C35 | UEs supporting 5G Core and (ETWS reception or CMAS reception) | +| 8.1.5.3.4 | PWS notification / PWS reception using dedicatedSystemInformationDelivery | Rel-15 | C35 | UEs supporting 5G Core and (ETWS reception or CMAS reception) | +| 8.1.5.4 | Counter check | | | | +| 8.1.5.4.1 | Counter check / Reception of CounterCheck message by the UE | Rel-15 | C21 | UEs supporting 5G Core | +| 8.1.5.5 | Redirection to NR | | | | +| 8.1.5.5.1 | Redirection to NR / From E-UTRA / Success | Rel-15 | C32 | UEs supporting 5G Core and E-UTRA | + +| | | | | | +|-------------|----------------------------------------------------------------------------------------------------------------------------|--------|-------|----------------------------------------------------------------------------------------------------------------------------------------| +| 8.1.5.5.2 | Redirection to NR / From E-UTRA / MPS Priority Indication / Success | Rel-16 | C344 | UEs supporting 5G Core and E-UTRA and RRC Connection release with MPS priority indication | +| 8.1.5.6 | Radio link failure | | | | +| 8.1.5.6.1 | Radio link failure / RRC connection re-establishment success | Rel-15 | C21 | UEs supporting 5G Core | +| 8.1.5.6.2 | Void | | | | +| 8.1.5.6.3 | Radio link failure / T311 expiry | Rel-15 | C21 | UEs supporting 5G Core | +| 8.1.5.6.4 | Void | | | | +| 8.1.5.6.5 | NR CA / No Radio Link Failure on SCell / RRC Connection Continues on Pcell | | | | +| 8.1.5.6.5.1 | NR CA / No Radio Link Failure on SCell / RRC Connection Continues on PCell / Intra-band Contiguous CA | Rel-15 | C41 | UEs supporting 5G Core and intra-band contiguous CA | +| 8.1.5.6.5.2 | NR CA / No Radio Link Failure on SCell / RRC Connection Continues on PCell / Inter-band CA | Rel-15 | C42 | UEs supporting 5G Core and inter-band CA | +| 8.1.5.6.5.3 | NR CA / No Radio Link Failure on SCell / RRC Connection Continues on PCell / Intra-band non-Contiguous CA | Rel-15 | C43 | UEs supporting 5G Core and intra-band non-contiguous CA | +| 8.1.5.6.6 | Radio link failure / Shared spectrum / LBT Failure | | | | +| 8.1.5.6.6.1 | Radio link failure / LBT Failure | Rel-16 | C217A | UEs supporting 5G Core and NR standalone shared spectrum channel access and UL LBT Failure Detection and Recovery | +| 8.1.5.7 | Failure information | | | | +| 8.1.5.7.1 | Failure information / RLC failure / MCG | | | | +| 8.1.5.7.1.1 | Failure information / RLC failure / MCG / Intra-band Contiguous CA | Rel-15 | C72 | UEs supporting 5G Core and intra-band contiguous CA and CA-based PDCP duplication over MCG or SCG DRB and UL NR CA with 2 carriers | +| 8.1.5.7.1.2 | Failure information / RLC failure / MCG / Inter-band CA | Rel-15 | C73 | UEs supporting 5G Core and inter-band CA and CA-based PDCP duplication over MCG or SCG DRB and UL NR CA with 2 carriers | +| 8.1.5.7.1.3 | Failure information / RLC failure / MCG / Intra-band non Contiguous CA | Rel-15 | C74 | UEs supporting 5G Core and intra-band non-contiguous CA and CA-based PDCP duplication over MCG or SCG DRB and UL NR CA with 2 carriers | +| 8.1.5.8 | Processing delay | | | | +| 8.1.5.8.1 | Processing delay / RRC_Idle to RRC_Connected / RRC_Inactive to RRC_Connected / Success / Latency check | Rel-15 | C21 | UEs supporting 5G Core | +| 8.1.5.8.2 | Processing delay / RRC_Inactive to RRC_Connected / Success / Latency check / SCell addition | | | | +| 8.1.5.8.2.1 | Processing delay / RRC_Inactive to RRC_Connected / Success / Latency check / SCell addition / Intra-band Contiguous CA | Rel-15 | C41 | UEs supporting 5G Core and intra-band contiguous CA | +| 8.1.5.8.2.2 | Processing delay / RRC_Inactive to RRC_Connected / Success / Latency check / SCell addition / Inter-band CA | Rel-15 | C42 | UEs supporting 5G Core and inter-band CA | +| 8.1.5.8.2.3 | Processing delay / RRC_Inactive to RRC_Connected / Success / Latency check / SCell addition / Intra-band non-Contiguous CA | Rel-15 | C43 | UEs supporting 5G Core and intra-band non-contiguous CA | +| 8.1.5.9 | Message Segment transfer | | | | +| 8.1.5.9.1 | UECapabilityInformation / UL segment transfer | Rel-16 | C129 | UEs supporting 5G Core and RRC message segmentation in the UL | +| 8.1.5.9.2 | RRC reconfiguration / DL segment transfer | Rel-16 | C207 | UEs supporting 5G core and reception of segmented DL RRC messages. | +| 8.1.5.9.3 | RRC resume / DL segment transfer | Rel-16 | C207 | UEs supporting 5G core and reception of segmented DL RRC messages. | +| 8.1.5.10 | UE Assistance Information | | | | + +| | | | | | +|-------------|----------------------------------------------------------------------------------------------------|--------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 8.1.5.10.1 | UE Assistance Information/ Release Preference | Rel-16 | C145 | UEs supporting 5G Core and release preference assistance information | +| 8.1.5.10.2 | UE Assistance Information / MUSIM | Rel-17 | C294 | UEs supporting 5G Core and Multi-SIM features and MUSIM related assistance information | +| 8.1.5.10.3 | UE Assistance Information / MUSIM / Leaving RRC_CONNECTED / T346g expires | Rel-17 | C245 | UEs supporting 5G Core and Multi-SIM features and release preference assistance information | +| 8.1.5.10.4 | UE Assistance Information / RRM measurement relaxation / RedCap | Rel-17 | C209 | UEs supporting 5G Core and RedCap and relaxed RRM measurements in RRC_CONNECTED and initiating UE Assistance Information procedure immediately upon change of its fulfilment status for RRM measurement relaxation criterion for connected mode. | +| 8.1.5.10.5 | UE Assistance Information / MUSIM / musim-cellToAffectList | Rel-18 | C393 | UEs supporting 5G Core and providing MUSIM assistance information with temporary capability restriction and capability restriction indication and Transmitting R18 MUSIM related UEAssistanceInformation message once the UE is allowed to do so after triggered by RRCReconfiguration | +| 8.1.5.10.6 | UE Assistance Information / MUSIM / musim-AffectedBandsList / musim-AvoidedBandsList / musim-MaxCC | Rel-18 | C393 | UEs supporting 5G Core and providing MUSIM assistance information with temporary capability restriction and capability restriction indication and Transmitting R18 MUSIM related UEAssistanceInformation message once the UE is allowed to do so after triggered by RRCReconfiguration | +| 8.1.5.10.7 | UE Assistance Information / UL Traffic Information | Rel-18 | C411 | UEs supporting 5G Core and sending UE assistance information with UL traffic information, including at least one of jitter range, burst arrival time, data burst periodicity and PDU Set and PSI identification. | +| 8.1.5.10.8 | UE Assistance Information / IDC mechanism | Rel-16 | C345 | UEs supporting 5G core and FR1 Band n40 and FR1 Band n41 and WLAN and reporting affected NR carrier frequencies in IDC assistance information when detecting IDC problem. | +| 8.1.5.10.9 | UE Assistance Information / IDC / FDM assistance configuration | Rel-18 | C403 | UEs supporting 5G Core and FR1 Band n40 and FR1 Band n41 and WLAN and reporting affected NR carrier frequency ranges in IDC assistance information | +| 8.1.5.10.10 | UE Assistance Information / IDC / TDM assistance configuration | Rel-18 | C404 | UEs supporting 5G Core and FR1 Band n40 and FR1 Band n41 and WLAN and reporting IDC TDM assistance information | +| 8.1.5.11 | Idle/Inactive Measurements | | | | +| 8.1.5.11.1 | Idle/Inactive Measurements / Idle mode / SIB11 configuration / Measurement of NR cells | Rel-16 | C190 | UEs supporting 5G Core and Idle/Inactive Measurements | +| 8.1.5.11.2 | Idle/Inactive Measurements / Idle mode / RRCRelease configuration / Measurement of NR cells | Rel-16 | C190 | UEs supporting 5G Core and Idle/Inactive Measurements | +| 8.1.5.11.3 | Idle/Inactive measurements / Inactive mode / SIB11 configuration / Measurement of NR cells | Rel-16 | C192 | UEs supporting 5G Core and RRC_INACTIVE and Idle/Inactive Measurements | +| 8.1.5.11.4 | Idle/Inactive measurements / Inactive mode / RRCRelease configuration / Measurement of NR cells | Rel-16 | C192 | UEs supporting 5G Core and RRC_INACTIVE and Idle/Inactive Measurements | +| 8.1.5.12 | Partial Sounding | | | | +| 8.1.5.12.1 | Partial Sounding / RRC_CONNECTED / RRCReconfiguration | Rel-17 | C315 | UEs supporting 5G Core and partial frequency sounding for SRS with frequency hopping | +| 8.1.5.13 | Small Data Transmission | | | | +| 8.1.5.13.1 | RRC SDT/CG based SDT/Success | Rel-17 | C269 | UEs supporting 5G Core and SDT via Configured Grant Type 1 in RRC_INACTIVE state | + +| | | | | | +|--------------|------------------------------------------------------------------------------------------------------------------|--------|------|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| 8.1.5.13.2 | RRC SDT / CG based SDT ongoing / Data on non-SDT Radio Bearers | Rel-17 | C317 | UEs supporting 5G Core and SDT via Configured Grant Type 1 in RRC_INACTIVE state and SMS over NAS | +| 8.1.5.13.3 | RRC SDT / CG based SDT / SDT-SRB2-Indication | Rel-17 | C328 | UEs supporting 5G Core and SRB SDT and SDT via Configured Grant Type 1 in RRC_INACTIVE state and SMS over NAS | +| 8.1.5.13.4 | RRC MT SDT / CG based SDT / Success | Rel-18 | C385 | UEs supporting 5G Core and MT-SDT via Configured Grant Type 1 in RRC_INACTIVE state | +| 8.1.5.14 | Non-Terrestrial Network | | | | +| 8.1.5.14.1 | NR NTN / SIB19 / T430 with the timer value set to ntn-UISyncValidityDuration / T430 Expiry | Rel-17 | C309 | UEs supporting 5G Core and NR NTN access | +| 8.1.6 | SON and MDT support for NR | | | | +| 8.1.6.1 | Intra NR MDT | | | | +| 8.1.6.1.1 | Immediate MDT | | | | +| 8.1.6.1.1.1 | Immediate MDT / Measurement reporting / Location information | Rel-16 | C126 | UEs supporting 5G Core and equipped with a GNSS or A-GNSS receiver to provide detailed location information | +| 8.1.6.1.1.2 | Immediate MDT / Measurement / Latency metrics for UL PDCP Packet Delay per DRB | Rel-16 | C122 | UEs supporting 5G Core and UL PDCP Packet Delay per DRB | +| 8.1.6.1.2 | Logged MDT | | | | +| 8.1.6.1.2.1 | Logged MDT / RRC_IDLE / Logging and reporting / Intra-frequency measurement | Rel-16 | C123 | UEs supporting 5G core and logged measurements in RRC_IDLE and RRC_INACTIVE | +| 8.1.6.1.2.2 | Logged MDT / RRC_INACTIVE / Logging and reporting / Inter-frequency measurement | Rel-16 | C125 | UEs supporting 5G core and RRC_INACTIVE and logged measurements in RRC_IDLE and RRC_INACTIVE | +| 8.1.6.1.2.3 | Logged MDT / RRC_IDLE / Logging and reporting / Limiting area scope | Rel-16 | C123 | UEs supporting 5G core and logged measurements in RRC_IDLE and RRC_INACTIVE | +| 8.1.6.1.2.4 | logged MDT/ RRC_IDLE / Logging and reporting / periodic measurement trigger | Rel-16 | C123 | UEs supporting 5G core and logged measurements in RRC_IDLE and RRC_INACTIVE | +| 8.1.6.1.2.5 | logged MDT/ RRC_IDLE / Logging and reporting / event-based trigger | Rel-16 | C123 | UEs supporting 5G core and logged measurements in RRC_IDLE and RRC_INACTIVE | +| 8.1.6.1.2.6 | logged MDT/ RRC_IDLE / Logging and reporting / event-based trigger / out-of-coverage | Rel-16 | C123 | UEs supporting 5G core and logged measurements in RRC_IDLE and RRC_INACTIVE | +| 8.1.6.1.2.7 | Logged MDT / RRC_IDLE / Logging and reporting / Reporting at NR re-establishment | Rel-16 | C123 | UEs supporting 5G core and logged measurements in RRC_IDLE and RRC_INACTIVE | +| 8.1.6.1.2.8 | Logged MDT / Logging and reporting / Reporting at RRC reconfiguration | Rel-16 | C123 | UEs supporting 5G core and logged measurements in RRC_IDLE and RRC_INACTIVE | +| 8.1.6.1.2.9 | Logged MDT / Location information | Rel-16 | C124 | UEs supporting 5G core and logged measurements in RRC_IDLE and RRC_INACTIVE and equipped with a GNSS receiver to provide detailed location information. | +| 8.1.6.1.2.10 | Logged MDT / Maintaining logged measurement configuration / UE mobility | Rel-16 | C123 | UEs supporting 5G core and logged measurements in RRC_IDLE and RRC_INACTIVE | +| 8.1.6.1.2.11 | Logged MDT / Maintaining logged measurement configuration / UE state transitions | Rel-16 | C123 | UEs supporting 5G core and logged measurements in RRC_IDLE and RRC_INACTIVE | +| 8.1.6.1.2.12 | Logged MDT / Release of logged MDT measurement configuration / Expire of duration timer | Rel-16 | C123 | UEs supporting 5G core and logged measurements in RRC_IDLE and RRC_INACTIVE | +| 8.1.6.1.2.13 | Logged MDT / Release of logged MDT measurement configuration / Reception of new logged measurement configuration | Rel-16 | C123 | UEs supporting 5G core and logged measurements in RRC_IDLE and RRC_INACTIVE | + +| | | | | | +|--------------|---------------------------------------------------------------------------------------------------------|--------|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 8.1.6.1.2.14 | Logged MDT / RRC_IDLE / Logging and reporting / IDC mechanism | Rel-17 | C266 | UEs supporting 5G core and logged measurements in RRC_IDLE and RRC_INACTIVE and FR1 Band n40 and WLAN, and reporting of affected NR carrier frequencies in IDC assistance information, and transmitting UEAssistanceInformation message with IDC-Assistance-r16 in RRC_CONNECTED when an IDC problem is detected in RRC_IDLE | +| 8.1.6.1.2.15 | Logged MDT / RRC_IDLE / early measurements | Rel-17 | C267 | UEs supporting 5G core and logged measurements in RRC_IDLE and RRC_INACTIVE and early measurements | +| 8.1.6.1.2.16 | Logged MDT / RRC_IDLE / sig-based logged MDT | Rel-17 | C123 | UEs supporting 5G core and logged measurements in RRC_IDLE and RRC_INACTIVE | +| 8.1.6.1.3 | Radio Link Failure report | | | | +| 8.1.6.1.3.1 | Radio Link Failure / Reporting of Intra-frequency measurements | Rel-16 | C21 | UEs supporting 5G Core | +| 8.1.6.1.3.2 | Radio Link Failure / Reporting of Inter-frequency measurements | Rel-16 | C21 | UEs supporting 5G Core | +| 8.1.6.1.3.3 | Radio Link Failure / Reporting at RRC connection establishment and reestablishment | Rel-16 | C21 | UEs supporting 5G Core | +| 8.1.6.1.3.4 | Radio Link Failure / Reporting at NR handover | Rel-16 | C21 | UEs supporting 5G Core | +| 8.1.6.1.3.5 | Radio Link Failure / Location information | Rel-16 | C126 | UEs supporting 5G Core and equipped with a GNSS or A-GNSS receiver to provide detailed location information | +| 8.1.6.1.3.6 | Radio Link Failure / RACH failure report | Rel-16 | C21 | UEs supporting 5G Core | +| 8.1.6.1.3.7 | Radio Link Failure / Logging and reporting / Reporting at intra NR handover / PLMN list | Rel-16 | C21 | UEs supporting 5G Core | +| 8.1.6.1.3.8 | Radio Link Failure / Logging and reporting / Event A3 / CHO | Rel-17 | C301 | UEs supporting 5G Core and RLF-Report for conditional handover | +| 8.1.6.1.3.9 | Radio Link Failure / Logging and reporting / Event A5 / CHO | Rel-17 | C301 | UEs supporting 5G Core and RLF-Report for conditional handover | +| 8.1.6.1.3.10 | Radio Link Failure / Logging and reporting / DAPS HO | Rel-17 | C302 | UEs supporting 5G Core and RLF-Report for DAPS handover. | +| 8.1.6.1.3.11 | Radio Link Failure / Logging and reporting / Successful Handovers Reports | Rel-17 | C303 | UEs supporting 5G Core and the storage and delivery of Successful Handover Report. | +| 8.1.6.1.4 | Connection Establishment Failure | | | | +| 8.1.6.1.4.1 | Connection Establishment Failure / Logging and reporting / T300 expiry | Rel-16 | C21 | UEs supporting 5G Core | +| 8.1.6.1.4.2 | Connection Establishment Failure / Logging and reporting / RRC Resume | Rel-16 | C109 | UEs supporting 5G Core and RRC_INACTIVE. | +| 8.1.6.1.4.3 | Connection Establishment Failure / Logging and reporting / Reporting at intra-NR handover | Rel-16 | C21 | UEs supporting 5G Core | +| 8.1.6.1.4.4 | Connection Establishment Failure / Logging and reporting / Reporting at RRC connection re-establishment | Rel-16 | C21 | UEs supporting 5G Core | +| 8.1.6.1.4.5 | Connection Establishment Failure / Logging and reporting / Location Information | Rel-16 | C126 | UEs supporting 5G Core and equipped with a GNSS or A-GNSS receiver to provide detailed location information. | +| 8.1.6.1.4.6 | Connection Establishment Failure / Logging and reporting / Reporting of Intra-frequency measurements | Rel-16 | C21 | UEs supporting 5G Core. | +| 8.1.6.1.4.7 | Connection Establishment Failure / Logging and reporting / Reporting of Inter-frequency measurements | Rel-16 | C21 | UEs supporting 5G Core | +| 8.1.6.1.4.8 | Connection Establishment Failure / Logging and reporting / RACH failure report | Rel-16 | C136 | UEs supporting 5G Core and delivery of rachReport upon request from the network | + +| | | | | | +|-------------|----------------------------------------------------------------------------------------------------------------|--------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 8.1.6.1.4.9 | Connection Establishment Failure / Logging and reporting / T300 expiry / Multiple CEF reports | Rel-17 | C250 | UEs supporting 5G Core and storage and delivery of multiple CEF report upon request from the network | +| 8.1.6.2 | Inter-RAT MDT | | | | +| 8.1.6.2.1 | Inter-RAT MDT / Immediate MDT / Periodic reporting of E-UTRAN/ Location information | Rel-16 | C143 | UEs supporting 5G Core and E-UTRA and standalone GNSS receiver to provide detailed location information | +| 8.1.6.2.2 | Inter-RAT MDT / Logged MDT / E-UTRA Inter-RAT measurement, logging and reporting | Rel-16 | C144 | UEs supporting 5G Core and E-UTRA and logged measurements in RRC_IDLE and RRC_INACTIVE | +| 8.1.6.2.3 | Inter-RAT MDT / Radio Link Failure / Reporting at E-UTRA Inter-RAT handover | Rel-16 | C32a | UEs supporting 5G Core and E-UTRA and logged MDT | +| 8.1.6.2.4 | Inter-RAT MDT / Connection Establishment Failure / Logging and reporting / Reporting of E-UTRA measurement | Rel-16 | C32a | UEs supporting 5G Core and E-UTRA and logged MDT | +| 8.1.6.3 | Inter-System MDT | | | | +| 8.1.6.3.1 | Inter-System MDT / Immediate MDT | | | | +| 8.1.6.3.1.1 | Inter-System MDT / Immediate MDT / Measurement reporting / Bluetooth measurement collection | Rel-16 | C140 | UEs supporting 5G core and Bluetooth Measurement Collection in Immediate MDT | +| 8.1.6.3.1.2 | Inter-System MDT / Immediate MDT / Measurement reporting / WLAN measurement collection | Rel-16 | C141 | UEs supporting 5G core and WLAN Measurement Collection in Immediate MDT | +| 8.1.6.3.1.3 | Inter-System MDT / Immediate MDT / Measurement reporting / Sensor measurement collection | Rel-16 | C139 | UEs supporting 5G Core and collection of sensor information such as Barometric pressure, UE speed, and UE orientation information as defined in TS 37.355. | +| 8.1.6.3.2 | Inter-System MDT / Logged MDT | | | | +| 8.1.6.3.2.1 | Inter-System MDT / Logged MDT / Logging and reporting / Bluetooth measurement collection | Rel-16 | C137 | UEs supporting 5G Core and logged MDT and Bluetooth measurements in RRC_IDLE and RRC_INACTIVE state | +| 8.1.6.3.2.2 | Inter-System MDT / Logged MDT / Logging and reporting / WLAN measurement collection | Rel-16 | C138 | UEs supporting 5G Core and logged MDT and WLAN measurements in RRC_IDLE and RRC_INACTIVE state | +| 8.1.6.3.2.3 | Inter-System MDT / Logged MDT / Logging and reporting / Sensor measurement collection | Rel-16 | C139a | UEs supporting 5G Core and collection of sensor information such as Barometric pressure, UE speed, and UE orientation information as defined in TS 37.355 and logged MDT. | +| 8.1.6.3.3 | Inter-System MDT / Radio Link Failure | | | | +| 8.1.6.3.3.1 | Inter-System MDT / Radio Link Failure / Logging and reporting / Bluetooth measurement collection | Rel-16 | C137 | UEs supporting 5G Core and logged MDT and Bluetooth measurements in RRC_IDLE and RRC_INACTIVE state | +| 8.1.6.3.3.2 | Inter-System MDT / Radio Link Failure / Logging and reporting / WLAN measurement collection | Rel-16 | C138 | UEs supporting 5G Core and logged MDT and WLAN measurements in RRC_IDLE and RRC_INACTIVE state | +| 8.1.6.3.3.3 | Inter-System MDT / Radio Link Failure / Logging and reporting / Sensor measurement collection | Rel-16 | C139a | UEs supporting 5G Core and collection of sensor information such as Barometric pressure, UE speed, and UE orientation information as defined in TS 37.355 and logged MDT. | +| 8.1.6.3.4 | Inter-System MDT / Connection Establishment Failure | | | | +| 8.1.6.3.4.1 | Inter-System MDT / Connection Establishment Failure / Logging and reporting / Bluetooth measurement collection | Rel-16 | C137 | UEs supporting 5G Core and logged MDT and Bluetooth measurements in RRC_IDLE and RRC_INACTIVE state | +| 8.1.6.3.4.2 | Inter-System MDT / Connection Establishment Failure / Logging and reporting / WLAN measurement collection | Rel-16 | C138 | UEs supporting 5G Core and logged MDT and WLAN measurements in RRC_IDLE and RRC_INACTIVE state | + +| | | | | | +|-------------|------------------------------------------------------------------------------------------------------------------------------------------------|--------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 8.1.6.3.4.3 | Inter-System MDT / Connection Establishment Failure / Logging and reporting / Sensor measurement collection | Rel-16 | C139a | UEs supporting 5G Core and collection of sensor information such as Barometric pressure, UE speed, and UE orientation information as defined in TS 37.355 and logged MDT. | +| 8.1.6.4 | SON / RACH Optimisation | | | | +| 8.1.6.4.1 | SON / RACH logging and reporting | Rel-16 | C136 | UEs supporting 5G Core and delivery of rachReport upon request from the network. | +| 8.1.6.4.2 | SON / RACH logging and reporting / logging of on-demand SI | Rel-17 | C278 | UEs supporting 5G Core and delivery of on-Demand SI information upon request from the network. | +| 8.1.6.4.3 | SON / RACH logging and reporting / 2-step RACH report | Rel-17 | C279 | UEs supporting 5G Core and delivery of delivery of 2-step RACH related information upon request from the network. | +| 8.1.6.4.4 | SON / RACH logging and reporting / fallback to 4-step RA | Rel-17 | C279 | UEs supporting 5G Core and delivery of delivery of 2-step RACH related information upon request from the network. | +| 8.1.7 | Non-public networks | | | | +| 8.1.7.1 | Measurement for self-optimized networks | | | | +| 8.1.7.1.1 | Measurement configuration control and reporting / CGI reporting of NR NPN cell | Rel-16 | C169 | UEs supporting 5G Core and CAG and acquisition of CGI information from neighbour NR NPN cell | +| 8.1.7.2 | RRC connection establishment | | | | +| 8.1.7.2.1 | RRC connection establishment / RRC setup complete with onboarding request | Rel-17 | C305 | UEs supporting 5G Core and onboarding services in SNPN | +| 8.1.8 | Shared spectrum access | | | | +| 8.1.8.1 | Measurement configuration control and reporting for Shared spectrum | | | | +| 8.1.8.1.1 | Measurement configuration control and reporting for Shared spectrum / RMTC / RSSI measurements / Channel Occupancy reporting / intra-frequency | Rel-16 | C218 | UEs supporting 5G Core and NR standalone shared spectrum channel access and RSSI measurements and channel occupancy reporting | +| 8.1.8.1.2 | Measurement configuration control and reporting for Shared spectrum / RMTC / RSSI measurements / Channel Occupancy reporting / inter-frequency | Rel-16 | C218 | UEs supporting 5G Core and NR standalone shared spectrum channel access and RSSI measurements and channel occupancy reporting | +| 8.1.8.1.3 | NR CA / Measurement configuration control and reporting for Shared spectrum / RMTC / Event A2 / inter-frequency | Rel-16 | C318 | UEs supporting 5G Core and NR CA with NR shared spectrum channel access | +| 8.1.8.2 | Paging monitoring | | | | +| 8.1.8.2.1 | Paging monitoring / multiple PDCCH monitoring occasions / Short message indication / stopPagingMonitoring | Rel-16 | C217 | UEs supporting 5G Core and NR standalone shared spectrum channel access | +| 8.1.8.2.2 | Paging monitoring / multiple PDCCH monitoring occasions / Short message indication / stopPagingMonitoring / RRC inactive | Rel-16 | C247 | UEs supporting 5G Core and NR standalone shared spectrum channel access and RRC_INACTIVE | +| 8.2 | MR-DC RRC | | | | +| 8.2.1 | UE Capability | | | | +| 8.2.1.1 | UE capability transfer / Success | | | | +| 8.2.1.1.1 | UE capability transfer / Success / EN-DC | Rel-15 | C01 | UEs supporting EN-DC | +| 8.2.1.1.2 | UE capability transfer / Success / NE-DC | Rel-15 | C160 | UEs supporting NE-DC | +| 8.2.1.2 | Void | | | | +| 8.2.2 | Radio Bearer Addition, Modification and Release | | | | +| 8.2.2.1 | Radio Bearer Addition, Modification and Release / SRB | | | | + +| | | | | | +|-----------|----------------------------------------------------------------------------------------------------------|--------|------|-------------------------------------------------------------------------------------------------------| +| 8.2.2.1.1 | SRB3 Establishment, Reconfiguration and Release / NR addition, modification and release / EN-DC | Rel-15 | C22 | UEs supporting EN-DC and SRB3 | +| 8.2.2.1.2 | SRB3 Establishment, Reconfiguration and Release / NR addition, modification and release / NR-DC | Rel-15 | C86 | UEs supporting NR-DC and SRB3 | +| 8.2.2.2 | Split SRB Establishment and Release | | | | +| 8.2.2.2.1 | Split SRB Establishment and Release / EN-DC | Rel-15 | C61 | UEs supporting EN-DC and PDCP duplication over split SRB1/2 | +| 8.2.2.2.2 | Split SRB Establishment and Release / NR-DC | Rel-15 | C195 | UEs supporting NR-DC and PDCP duplication over split SRB1/2 | +| 8.2.2.2.3 | Split SRB Establishment and Release / NE-DC | Rel-15 | C196 | UEs supporting NE-DC and PDCP duplication over split SRB1/2 | +| 8.2.2.3 | Simultaneous SRB3 and Split SRB / Sequential message flow on SRB3 and Split SRB | | | | +| 8.2.2.3.1 | Simultaneous SRB3 and Split SRB / Sequential message flow on SRB3 and Split SRB with one UL path / EN-DC | Rel-15 | C23 | UEs supporting EN-DC and SRB3 and (UL transmission via either MCG path or SCG path for the split SRB) | +| 8.2.2.3.2 | Simultaneous SRB3 and Split SRB / Sequential message flow on SRB3 and Split SRB with one UL path / NR-DC | Rel-15 | C157 | UEs supporting NR-DC and SRB3 and (UL transmission via either MCG path or SCG path for the split SRB) | +| 8.2.2.4 | PSCell Addition, Modification and Release / SCG DRB | | | | +| 8.2.2.4.1 | PSCell addition, modification and release / SCG DRB / EN-DC | Rel-15 | C01 | UEs supporting EN-DC | +| 8.2.2.4.2 | PSCell addition, modification and release / SCG DRB / NR-DC | Rel-15 | C80 | UEs supporting NR-DC | +| 8.2.2.4.3 | PSCell addition, modification and release / SCG DRB / NE-DC | Rel-15 | C160 | UEs supporting NE-DC | +| 8.2.2.5 | PSCell Addition, Modification and Release / Split DRB | | | | +| 8.2.2.5.1 | PSCell addition, modification and release / Split DRB / EN-DC | Rel-15 | C01 | UEs supporting EN-DC | +| 8.2.2.5.2 | PSCell addition, modification and release / Split DRB / NR-DC | Rel-15 | C80 | UEs supporting NR-DC | +| 8.2.2.5.3 | PSCell addition, modification and release / Split DRB / NE-DC | Rel-15 | C160 | UEs supporting NE-DC | +| 8.2.2.6 | Bearer Modification / MCG DRB | | | | +| 8.2.2.6.1 | Bearer Modification / MCG DRB / SRB / PDCP version change / EN-DC | Rel-15 | C01 | UEs supporting EN-DC | +| 8.2.2.7 | Bearer Modification / Handling for bearer type change without security key change | | | | +| 8.2.2.7.1 | Bearer Modification / Handling for bearer type change without security key change / EN-DC | Rel-15 | C01 | UEs supporting EN-DC | +| 8.2.2.7.2 | Bearer Modification / Handling for bearer type change without security key change / NR-DC | Rel-15 | C80 | UEs supporting NR-DC | +| 8.2.2.7.3 | Bearer Modification / Handling for bearer type change without security key change / NE-DC | Rel-15 | C160 | UEs supporting NE-DC | +| 8.2.2.8 | Bearer Modification / Handling for bearer type change with security key change | | | | +| 8.2.2.8.1 | Bearer Modification / Handling for bearer type change with security key change / EN-DC | Rel-15 | C01 | UEs supporting EN-DC | +| 8.2.2.8.2 | Bearer Modification / Handling for bearer type change with security key change / NR-DC | Rel-15 | C80 | UEs supporting NR-DC | +| 8.2.2.8.3 | Bearer Modification / Handling for bearer type change with security key change / NE-DC | Rel-15 | C160 | UEs supporting NE-DC | +| 8.2.2.9 | Bearer Modification / Uplink data path / Split DRB Reconfiguration | | | | + +| | | | | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------|--------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 8.2.2.9.1 | Bearer Modification / Uplink data path / Split DRB Reconfiguration / EN-DC | Rel-15 | C01 | UEs supporting EN-DC | +| 8.2.2.9.2 | Bearer Modification / Uplink data path / Split DRB Reconfiguration / NR-DC | Rel-15 | C80 | UEs supporting NR-DC | +| 8.2.2.9.3 | Bearer Modification / Uplink data path / Split DRB Reconfiguration / NE-DC | Rel-15 | C160 | UEs supporting NE-DC | +| 8.2.3 | Measurement Configuration Control and Reporting / Handovers | | | | +| 8.2.3.1 | Measurement configuration control and reporting / Inter-RAT measurements / Event B1 / Measurement of NR cells | | | | +| 8.2.3.1.1 | Measurement configuration control and reporting / Inter-RAT measurements / Event B1 / Measurement of NR cells / EN-DC | Rel-15 | C01 | UEs supporting EN-DC | +| 8.2.3.1.2 | Measurement configuration control and reporting / Inter-RAT measurements / Event B1 / Measurement of NR cells / NE-DC | Rel-15 | C160 | UEs supporting NE-DC | +| 8.2.3.2 | Measurement configuration control and reporting / Inter-RAT measurements / Event B1 / Measurement of NR cells / RSRQ based measurements | | | | +| 8.2.3.2.1 | Measurement configuration control and reporting / Inter-RAT measurements / Event B1 / Measurement of NR cells / RSRQ based measurements / EN-DC | Rel-15 | C01 | UEs supporting EN-DC | +| 8.2.3.2.2 | Measurement configuration control and reporting / Inter-RAT measurements / Event B1 / Measurement of NR cells / RSRQ based measurements / NE-DC | Rel-15 | C160 | UEs supporting NE-DC | +| 8.2.3.3 | Measurement configuration control and reporting / Inter-RAT measurements / Periodic reporting / Measurement of NR cells | | | | +| 8.2.3.3.1 | Measurement configuration control and reporting / Inter-RAT measurements / Periodic reporting / Measurement of NR cells / EN-DC | Rel-15 | C01 | UEs supporting EN-DC | +| 8.2.3.4 | Measurement configuration control and reporting / Event A1 / Measurement of NR PSCell | | | | +| 8.2.3.4.1 | Measurement configuration control and reporting / Event A1 / Measurement of NR PSCell / EN-DC | Rel-15 | C13 | UEs supporting EN-DC and NR measurements and Event A triggered reporting | +| 8.2.3.4.2 | Measurement configuration control and reporting / Event A1 / Measurement of E-UTRA PSCell / NE-DC | Rel-15 | C160 | UEs supporting NE-DC. | +| 8.2.3.5 | Measurement configuration control and reporting / Event A2 / Measurement of NR PSCell | | | | +| 8.2.3.5.1 | Measurement configuration control and reporting / Event A2 / Measurement of NR PSCell / EN-DC | Rel-15 | C14 | UEs supporting EN-DC and NR measurements and Event A triggered reporting and (NR Intra-frequency and NR-Inter frequency measurements and at least periodical reporting) | +| 8.2.3.5.2 | Measurement configuration control and reporting / Event A2 / Measurement of E-UTRA PSCell / NE-DC | Rel-15 | C160 | UEs supporting NE-DC. | +| 8.2.3.6 | Measurement configuration control and reporting / Event A3 / Measurement of Neighbour NR cells | | | | +| 8.2.3.6.1 | Measurement configuration control and reporting / Event A3 / Measurement of Neighbour NR cells / Intra-frequency measurements / EN-DC | Rel-15 | C14 | UEs supporting EN-DC and NR measurements and Event A triggered reporting and (NR intra-frequency and inter-frequency measurements and at least periodical reporting) | + +| | | | | | +|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 8.2.3.6.1a | Measurement configuration control and reporting / Event A3 / Measurement of Neighbour NR cell / Inter-frequency measurements / EN-DC | Rel-15 | C14 | UEs supporting EN-DC and NR measurements and Event A triggered reporting and (NR intra-frequency and inter-frequency measurements and at least periodical reporting) | +| 8.2.3.6.1b | Measurement configuration control and reporting / Event A3 / Measurement of Neighbour NR cell / Inter-band measurements / EN-DC | Rel-15 | C93 | UEs supporting EN-DC and NR measurements and Event A triggered reporting and (NR Intra-frequency and NR-Inter frequency measurements and at least periodical reporting) and multiple NR bands. | +| 8.2.3.6.2 | Measurement configuration control and reporting / Event A3 / Measurement of Neighbour E-UTRA and NR cells / Intra-frequency measurements / NE-DC | Rel-15 | C182 | UEs supporting NE-DC and NR measurements and Event A triggered reporting and (NR intra-frequency and inter-frequency measurements and at least periodical reporting). | +| 8.2.3.6.2a | Measurement configuration control and reporting / Event A3 / Measurement of Neighbour E-UTRA and NR cell / Inter-frequency measurements / NE-DC | Rel-15 | C182 | UEs supporting NE-DC and NR measurements and Event A triggered reporting and (NR intra-frequency and inter-frequency measurements and at least periodical reporting) and multiple NR bands. | +| 8.2.3.6.2b | Measurement configuration control and reporting / Event A3 / Measurement of Neighbour E-UTRA and NR cell / Inter-band measurements / NE-DC | Rel-15 | C183 | UEs supporting NE-DC and NR measurements and Event A triggered reporting and (NR intra-frequency and inter-frequency measurements and at least periodical reporting) and multiple NR bands. | +| 8.2.3.7 | Measurement configuration control and reporting / Event A4 (intra-frequency, inter-frequency and inter-band measurements) / Measurement of Neighbour NR cell | | | | +| 8.2.3.7.1 | Measurement configuration control and reporting / Event A4 / Measurement of Neighbour NR cell / Intra-frequency measurements / EN-DC | Rel-15 | C14 | UEs supporting EN-DC and NR measurements and Event A triggered reporting and (NR intra-frequency and inter-frequency measurements and at least periodical reporting) | +| 8.2.3.7.1a | Measurement configuration control and reporting / Event A4 / Measurement of Neighbour NR cell / Inter-frequency measurements / EN-DC | Rel-15 | C14 | UEs supporting EN-DC and NR measurements and Event A triggered reporting and (NR intra-frequency and inter-frequency measurements and at least periodical reporting) | +| 8.2.3.7.1b | Measurement configuration control and reporting / Event A4 / Measurement of Neighbour NR cell / Inter-band measurements / EN-DC | Rel-15 | C93 | UEs supporting EN-DC and NR measurements and Event A triggered reporting and (NR Intra-frequency and NR-Inter frequency measurements and at least periodical reporting) and multiple NR bands. | +| 8.2.3.7.2 | Measurement configuration control and reporting / Event A4 / Measurement of Neighbour E-UTRA and NR cells / Intra-frequency measurements / NE-DC | Rel-15 | C182 | UEs supporting NE-DC and NR measurements and Event A triggered reporting and (NR intra-frequency and inter-frequency measurements and at least periodical reporting). | +| 8.2.3.7.2a | Measurement configuration control and reporting / Event A4 / Measurement of Neighbor E-UTRA and NR cells / Inter-frequency measurements / NE-DC | Rel-15 | C182 | UEs supporting NE-DC and NR measurements and Event A triggered reporting and (NR intra-frequency and inter-frequency measurements and at least periodical reporting) | +| 8.2.3.7.2b | Measurement configuration control and reporting / Event A4 / Measurement of Neighbor E-UTRA and NR cells / Inter-band measurements / NE-DC | Rel-15 | C183 | UEs supporting NE-DC and NR measurements and Event A triggered reporting and (NR intra-frequency and inter-frequency measurements and at least periodical reporting) and multiple NR bands. | +| 8.2.3.8 | Measurement configuration control and reporting / Event A5 / Measurement of Neighbour NR cell | | | | + +| | | | | | +|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 8.2.3.8.1 | Measurement configuration control and reporting / Event A5 / Measurement of Neighbour NR cell / Intra-frequency measurements / EN-DC | Rel-15 | C14 | UEs supporting EN-DC and NR measurements and Event A triggered reporting and (NR intra-frequency and inter-frequency measurements and at least periodical reporting) | +| 8.2.3.8.1a | Measurement configuration control and reporting / Event A5 / Measurement of Neighbour NR cell / Inter-frequency measurements / EN-DC | Rel-15 | C14 | UEs supporting EN-DC and NR measurements and Event A triggered reporting and (NR intra-frequency and inter-frequency measurements and at least periodical reporting) | +| 8.2.3.8.1b | Measurement configuration control and reporting / Event A5 / Measurement of Neighbour NR cell / Inter-band measurements / EN-DC | Rel-15 | C93 | UEs supporting EN-DC and NR measurements and Event A triggered reporting and (NR Intra-frequency and NR-Inter frequency measurements and at least periodical reporting) and multiple NR bands. | +| 8.2.3.8.2 | Measurement configuration control and reporting / Event A5 / Measurement of Neighbour E-UTRA and NR cells / Intra-frequency measurements / NE-DC | Rel-15 | C182 | UEs supporting NE-DC and NR measurements and Event A triggered reporting and (NR intra-frequency and inter-frequency measurements and at least periodical reporting). | +| 8.2.3.8.2a | Measurement configuration control and reporting / Event A5 / Measurement of Neighbor E-UTRA and NR cells / Inter-frequency measurements / NE-DC | Rel-15 | C182 | UEs supporting NE-DC and NR measurements and Event A triggered reporting and (NR intra-frequency and inter-frequency measurements and at least periodical reporting) | +| 8.2.3.8.2b | Measurement configuration control and reporting / Event A5 / Measurement of Neighbor E-UTRA and NR cells / Inter-band measurements / NE-DC | Rel-15 | C183 | UEs supporting NE-DC and NR measurements and Event A triggered reporting and (NR intra-frequency and inter-frequency measurements and at least periodical reporting) and multiple NR bands. | +| 8.2.3.9 | Measurement configuration control and reporting / SS/PBCH block based / CSI-RS based intra-frequency measurements / Measurement of Neighbour NR cell | | | | +| 8.2.3.9.1 | Measurement configuration control and reporting / SS/PBCH block based / CSI-RS based intra-frequency measurements / Measurement of Neighbour NR Cell / EN-DC | Rel-15 | C15 | UEs supporting EN-DC and NR measurements and Event A triggered reporting and (NR Intra-frequency and Inter frequency measurements and at least periodical reporting) and CSI-RSRP and CSI-RSRQ measurement | +| 8.2.3.10 | Measurement configuration control and reporting / SS/PBCH block based / CSI-RS based inter-frequency measurements / Measurement of Neighbour NR cell | | | | +| 8.2.3.10.1 | Measurement configuration control and reporting / SS/PBCH block based / CSI-RS based inter-frequency measurements / Measurement of Neighbour NR Cell / EN-DC | Rel-15 | C15 | UEs supporting EN-DC and NR measurements and Event A triggered reporting and (NR Intra-frequency and Inter frequency measurements) and CSI-RSRP and CSI-RSRQ measurement | +| 8.2.3.11 | Measurement configuration control and reporting / Measurement Gaps | | | | +| 8.2.3.11.1 | Measurement configuration control and reporting / Measurement Gaps / NR FR1 / EN-DC | Rel-15 | C24 | UEs supporting EN-DC and (NR intra-frequency and inter-frequency measurements and at least periodical reporting) and (two independent measurement gap configurations for FR1 and FR2) and Inter-Band EN-DC within FR1 | + +| | | | | | +|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 8.2.3.11.2 | Measurement configuration control and reporting / Measurement Gaps / NR FR2 / EN-DC | Rel-15 | C25 | UEs supporting EN-DC and (NR intra-frequency and inter-frequency measurements and at least periodical reporting) and (two independent measurement gap configurations for FR1 and FR2) and Inter-Band EN-DC including FR2 | +| 8.2.3.11.3 | Measurement configuration control and reporting / Measurement Gaps / NR-DC | Rel-15 | C149 | UEs supporting NR-DC and two independent measurement gap configurations for FR1 and FR2 | +| 8.2.3.12 | Measurement configuration control and reporting / Inter-RAT measurements / Event B2 / Measurement of NR cells | | | | +| 8.2.3.12.1 | Measurement configuration control and reporting / Inter-RAT measurements / Event B2 / Measurement of NR cells / EN-DC | Rel-15 | C01 | UEs supporting EN-DC | +| 8.2.3.12.2 | Measurement configuration control and reporting / Inter-RAT measurements / Event B2 / Measurement of E-UTRA cells / NE-DC | Rel-15 | C206 | UEs supporting NE-DC and Inter-RAT E-UTRA measurements and Event B triggered reporting | +| 8.2.3.13 | PCell Handover with SCG change / Reconfiguration with sync / SCG DRB | | | | +| 8.2.3.13.1 | PCell Handover with SCG change / Reconfiguration with sync / SCG DRB / EN-DC | Rel-15 | C01 | UEs supporting EN-DC | +| 8.2.3.13.2 | PCell Handover with SCG change on same PSCell / mobilityControlInfoSCG / SCG DRB / NE-DC | Rel-15 | C160 | UEs supporting NE-DC | +| 8.2.3.14 | SCG change / Reconfiguration with sync / Split DRB | | | | +| 8.2.3.14.1 | SCG change / Reconfiguration with sync / Split DRB / EN-DC | Rel-15 | C01 | UEs supporting EN-DC | +| 8.2.3.14.2 | SCG change / Reconfiguration with sync / Split DRB / NR-DC | Rel-15 | C80 | UEs supporting NR-DC | +| 8.2.3.14.3 | SCG change with HO /mobilityControlInfoSCG / Split DRB / NE-DC | Rel-15 | C160 | UEs supporting NE-DC | +| 8.2.3.15 | Measurement configuration control and reporting / Two simultaneous events A2 and A3 (intra-frequency measurements) / Measurement of Neighbour NR cells | | | | +| 8.2.3.15.1 | Measurement configuration control and reporting / Two simultaneous events A2 and A3 (intra-frequency measurements) / Measurement of Neighbour NR cells / EN-DC | Rel-15 | C14 | UEs supporting EN-DC and NR measurements and Event A triggered reporting and (NR Intra-frequency and NR-Inter frequency measurements and at least periodical reporting) | +| 8.2.3.16 | Measurement configuration control and reporting / SRB3 | | | | +| 8.2.3.16.1 | Measurement configuration control and reporting / SRB3 / Intra NR measurements / EN-DC | Rel-15 | C71 | UEs supporting EN-DC and SRB3 and NR intra-frequency and inter-frequency measurements and at least periodical reporting | +| 8.2.3.16.2 | Measurement configuration control and reporting / SRB3 / Intra NR measurements / NR-DC | Rel-15 | C87 | UEs supporting NR-DC and SRB3 and NR intra-frequency and inter-frequency measurements and at least periodical reporting | +| 8.2.3.17 | Measurement configuration control and reporting / SFTD | | | | +| 8.2.3.17.1 | Measurement configuration control and reporting / SFTD / EN-DC | Rel-15 | C151 | UEs supporting EN-DC and SFTD measurement between E-UTRA PCell and an NR neighbour cell, and SFTD measurement between E-UTRA PCell and NR PSCell | + +| | | | | | +|-------------|---------------------------------------------------------------------------------------------------------------------------------|--------|-------|------------------------------------------------------------------------------------------------------------------------------------------| +| 8.2.3.17.2 | Measurement configuration control and reporting / SFTD / NR-DC | Rel-15 | C152 | UEs supporting NR-DC and SFTD measurement between NR PCell and an NR neighbour cell, and SFTD measurement between NR PCell and NR PSCell | +| 8.2.3.17.3 | Measurement configuration control and reporting / SFTD / NE-DC | Rel-15 | C268 | UEs supporting NE-DC and SFTD measurement between NR PCell and E-UTRA PSCell | +| 8.2.3.18 | Conditional PSCell change | | | | +| 8.2.3.18.1 | Conditional PSCell change / Success / EN-DC | Rel-16 | C153 | UEs supporting EN-DC and Conditional PSCell change | +| 8.2.3.18.2 | Conditional PSCell change / Failure / EN-DC | Rel-16 | C153 | UEs supporting EN-DC and Conditional PSCell change | +| 8.2.3.18.3 | Conditional PSCell change / PCell change / PSCell change / EN-DC | Rel-16 | C153 | UEs supporting EN-DC and Conditional PSCell change | +| 8.2.3.18.4 | MN initiated inter-SN Conditional PSCell change / Success / EN-DC | Rel-17 | C153A | UEs supporting EN-DC and MN initiated conditional PSCell change | +| 8.2.3.18.5 | MN initiated inter-SN Conditional PSCell change / Success / NR-DC | Rel-17 | C153B | UEs supporting NR-DC and MN initiated conditional PSCell change | +| 8.2.3.18.6 | SN initiated inter-SN Conditional PSCell change / Success / EN-DC | Rel-17 | C153C | UEs supporting EN-DC and SN initiated conditional PSCell change | +| 8.2.3.18.7 | SN initiated inter-SN Conditional PSCell change / Success / NR-DC | Rel-17 | C153D | UEs supporting NR-DC and SN initiated conditional PSCell change | +| 8.2.4 | Carrier Aggregation | | | | +| 8.2.4.1 | NR CA / NR SCell addition / modification / release / Success | | | | +| 8.2.4.1.1 | NR CA / NR SCell addition / modification / release / Success / EN-DC | | | | +| 8.2.4.1.1.1 | NR CA / NR SCell addition / modification / release / Success / EN-DC / Intra-band Contiguous CA | Rel-15 | C67 | UEs supporting EN-DC and Intra-Band Contiguous CA and EN-DC with 2 NR DL carriers | +| 8.2.4.1.1.2 | NR CA / NR SCell addition / modification / release / Success / EN-DC / Intra-band non-Contiguous CA | Rel-15 | C68 | UEs supporting EN-DC and Intra-Band Non-Contiguous CA and EN-DC with 2 NR DL carriers | +| 8.2.4.1.1.3 | NR CA / NR SCell addition / modification / release / Success / EN-DC / Inter-band CA | Rel-15 | C69 | UEs supporting EN-DC and Inter-Band CA and EN-DC with 2 NR DL carriers | +| 8.2.4.1.1.4 | NR CA / NR SCell addition / modification / release / Success / EN-DC / Active SCG SCell addition / Intra-band Contiguous CA | Rel-16 | C199 | UEs supporting EN-DC, direct NR SCG SCell activation and Intra-Band Contiguous CA | +| 8.2.4.1.1.5 | NR CA / NR SCell addition / modification / release / Success / EN-DC / Active SCG SCell addition / Intra-band non-Contiguous CA | Rel-16 | C200 | UEs supporting EN-DC, direct NR SCG SCell activation and Intra-Band Non-Contiguous CA | +| 8.2.4.1.1.6 | NR CA / NR SCell addition / modification / release / Success / EN-DC / Active SCG SCell addition / Inter-band CA | Rel-16 | C201 | UEs supporting EN-DC, direct NR SCG SCell activation and Inter-Band CA | +| 8.2.4.1.2 | NR CA / NR SCell addition / modification / release / Success / NR-DC / Active SCG SCell addition | | | | +| 8.2.4.1.2.1 | NR CA / NR SCell addition / modification / release / Success / NR-DC / Active SCG SCell addition / Intra-band Contiguous CA | Rel-16 | C202 | UEs supporting NR-DC, direct NR SCG SCell activation and intra-band contiguous CA | +| 8.2.4.1.2.2 | NR CA / NR SCell addition / modification / release / Success / NR-DC / Active SCG SCell addition / Intra-band non-contiguous CA | Rel-16 | C203 | UEs supporting NR-DC, direct NR SCG SCell activation and intra-band non-contiguous CA | +| 8.2.4.1.2.3 | NR CA / NR SCell addition / modification / release / Success / NR-DC / Active SCG SCell addition / Inter-band CA | Rel-16 | C204 | UEs supporting NR-DC, direct NR SCG SCell activation and inter-band CA | +| 8.2.4.2 | NR CA / Simultaneous PSCell and SCell addition / PSCell and SCell change / CA Release | | | | + +| | | | | | +|-------------|------------------------------------------------------------------------------------------------------------------------------|--------|------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| 8.2.4.2.1 | NR CA / Simultaneous PSCell and SCell addition / PSCell and SCell change / CA Release / EN-DC | | | | +| 8.2.4.2.1.1 | NR CA / Simultaneous PSCell and SCell addition / PSCell and SCell change / CA Release / EN-DC / Intra-band Contiguous CA | Rel-15 | C67 | UEs supporting EN-DC and Intra-Band Contiguous CA and EN-DC with 2 NR DL carriers | +| 8.2.4.2.1.2 | NR CA / Simultaneous PSCell and SCell addition / PSCell and SCell change / CA Release / EN-DC / Intra-band non-Contiguous CA | Rel-15 | C68 | UEs supporting EN-DC and Intra-Band Non-Contiguous CA and EN-DC with 2 NR DL carriers | +| 8.2.4.2.1.3 | NR CA / Simultaneous PSCell and SCell addition / PSCell and SCell change / CA Release / EN-DC / Inter-band CA | Rel-15 | C69 | UEs supporting EN-DC and Inter-Band CA and EN-DC with 2 NR DL carriers | +| 8.2.4.3 | NR CA / SCell change / Intra-NR measurement event A6 / SRB3 | | | | +| 8.2.4.3.1 | NR CA / SCell change / Intra-NR measurement event A6 / SRB3 / EN-DC | | | | +| 8.2.4.3.1.1 | NR CA / SCell change / Intra-NR measurement event A6 / SRB3 / EN-DC / Intra-band Contiguous CA | Rel-15 | C55 | UEs supporting EN-DC and NR measurements and Event A triggered reporting and intra-band contiguous CA and EN-DC with 2 NR DL carriers and SRB3 | +| 8.2.4.3.1.2 | NR CA / SCell change / Intra-NR measurement event A6 / SRB3 / EN-DC / Intra-band non-Contiguous CA | Rel-15 | C57 | UEs supporting EN-DC and NR measurements and Event A triggered reporting and intra-band non-contiguous CA and EN-DC with 2 NR DL carriers and SRB3 | +| 8.2.4.3.1.3 | NR CA / SCell change / Intra-NR measurement event A6 / SRB3 / EN-DC / Inter-band CA | Rel-15 | C56 | UEs supporting EN-DC and NR measurements and Event A triggered reporting and inter-band CA and EN-DC with 2 NR DL carriers and SRB3 | +| 8.2.5 | Reconfiguration Failure / Radio link failure | | | | +| 8.2.5.1 | Radio link failure / PSCell addition failure | | | | +| 8.2.5.1.1 | Radio link failure / Random access problem / EN-DC | Rel-15 | C01 | UEs supporting EN-DC | +| 8.2.5.1.2 | Radio link failure / Random access problem / NR-DC | Rel-15 | C80 | UEs supporting NR-DC | +| 8.2.5.2 | Radio link failure / PSCell out of sync indication | | | | +| 8.2.5.2.1 | Radio link failure / PSCell out of sync indication / EN-DC | Rel-15 | C01 | UEs supporting EN-DC | +| 8.2.5.2.2 | Radio link failure / PSCell out of sync indication / NR-DC | Rel-15 | C80 | UEs supporting NR-DC | +| 8.2.5.3 | Radio link failure / rlc-MaxNumRetx failure | | | | +| 8.2.5.3.1 | Radio link failure / rlc-MaxNumRetx failure / EN-DC | Rel-15 | C01 | UEs supporting EN-DC | +| 8.2.5.3.2 | Radio link failure / rlc-MaxNumRetx failure / NR-DC | Rel-15 | C80 | UEs supporting NR-DC | +| 8.2.5.3.3 | Radio link failure / rlc-MaxNumRetx failure / NE-DC | Rel-15 | C160 | UEs supporting NE-DC | +| 8.2.5.4 | Reconfiguration failure / SCG change failure | | | | +| 8.2.5.4.1 | Reconfiguration failure / SCG change failure / EN-DC | Rel-15 | C01 | UEs supporting EN-DC | +| 8.2.5.4.2 | Reconfiguration failure / SCG change failure / NR-DC | Rel-15 | C80 | UEs supporting NR-DC | +| 8.2.5.5 | Reconfiguration failure / SCG Reconfiguration failure / SRB3 | | | | +| 8.2.5.5.1 | Void | | | | +| 8.2.5.6 | Reconfiguration failure / SCG Reconfiguration failure / SRB1 | | | | + +| | | | | | +|-------------|-------------------------------------------------------------------------------------|--------|------|--------------------------------------------------------------------------------------------------------------------------------------------------| +| 8.2.5.6.1 | Void | | | | +| 8.2.5.7 | Radio link failure / Shared spectrum / LBT Failure | | | | +| 8.2.5.7.1 | Radio link failure / LBT Failure / EN-DC | Rel-16 | C243 | UEs supporting 5G Core and EN-DC with NR shared spectrum channel access and UL LBT Failure Detection and Recovery | +| 8.2.5.7.2 | Radio link failure / LBT Failure / NR-DC | Rel-16 | C244 | UEs supporting 5G Core and NR-DC with NR shared spectrum channel access and UL LBT Failure Detection and Recovery | +| 8.2.6 | MR-DC RRC others | | | | +| 8.2.6.1 | Failure information / RLC failure / SCG | | | | +| 8.2.6.1.1 | Failure information / RLC failure / SCG / EN-DC | | | | +| 8.2.6.1.1.1 | Failure information / RLC failure / SCG / EN-DC / Intra-band Contiguous CA | Rel-15 | C75 | UEs supporting EN-DC and SRB3 and intra-band contiguous CA and CA-based PDCP duplication over MCG or SCG DRB and EN-DC with 2 NR UL carriers | +| 8.2.6.1.1.2 | Failure information / RLC failure / SCG / EN-DC / Inter-band CA | Rel-15 | C76 | UEs supporting EN-DC and SRB3 and inter-band CA and CA-based PDCP duplication over MCG or SCG DRB and EN-DC with 2 NR UL carriers | +| 8.2.6.1.1.3 | Failure information / RLC failure / SCG / EN-DC / Intra-band non Contiguous CA | Rel-15 | C77 | UEs supporting EN-DC and SRB3 and intra-band non-contiguous CA and CA-based PDCP duplication over MCG or SCG DRB and EN-DC with 2 NR UL carriers | +| 8.2.6.1.2 | Failure information / RLC failure / SCG / NR-DC | | | | +| 8.2.6.1.2.1 | Failure information / RLC failure / SCG / NR-DC / Intra-band Contiguous CA | Rel-15 | C88 | UEs supporting NR-DC and SRB3 and intra-band contiguous CA and CA-based PDCP duplication over MCG or SCG DRB and UL NR CA with 2 carriers | +| 8.2.6.1.2.2 | Failure information / RLC failure / SCG / NR-DC / Inter-band CA | Rel-15 | C89 | UEs supporting NR-DC and SRB3 and inter-band CA and CA-based PDCP duplication over MCG or SCG DRB and UL NR CA with 2 carriers | +| 8.2.6.1.2.3 | Failure information / RLC failure / SCG / NR-DC / Intra-band non Contiguous CA | Rel-15 | C90 | UEs supporting NR-DC and SRB3 and intra-band non-contiguous CA and CA-based PDCP duplication over MCG or SCG DRB and UL NR CA with 2 carriers | +| 8.2.6.2 | Processing delay | | | | +| 8.2.6.2.1 | Processing delay / PSCell addition / SCG DRB / Success / Latency check / EN-DC | Rel-15 | C01 | UEs supporting EN-DC | +| 8.2.6.2.2 | Processing delay / Latency check / NR-DC | Rel-15 | C80 | UEs supporting NR-DC | +| 8.2.6.2.4 | Processing delay / RRC_INACTIVE / Latency check / NR-DC | Rel-16 | C229 | UEs supporting 5G Core and NR-DC and RRC_INACTIVE and (re-)configuration of an SCG during the resume procedure. | +| 8.2.6.3 | Idle/Inactive measurements | | | | +| 8.2.6.3.1 | Idle/Inactive measurements / Idle mode / EN-DC / SIB5 & SIB24 configuration | Rel-16 | C225 | UEs supporting EN-DC and Idle/Inactive Measurements | +| 8.2.6.3.2 | Idle/Inactive measurements / Idle mode / EN-DC / RRCConnectionRelease configuration | Rel-16 | C225 | UEs supporting EN-DC and Idle/Inactive Measurements | +| 8.2.6.3.3 | Idle/Inactive measurements / Inactive mode / NE-DC / SIB11 configuration | Rel-16 | C193 | UEs supporting 5G Core, E-UTRA, RRC_INACTIVE and Idle/Inactive Measurements | +| 8.2.6.3.4 | Idle/Inactive measurements / Inactive mode / NE-DC / RRCRelease configuration | Rel-16 | C193 | UEs supporting 5G Core, E-UTRA, RRC_INACTIVE and Idle/Inactive Measurements | +| 8.2.6.3.5 | Idle/Inactive Measurements / Idle mode / NE-DC / SIB11 configuration | Rel-16 | C191 | UEs supporting 5G Core, E-UTRA and Idle/Inactive Measurements | +| 8.2.6.3.6 | Idle/Inactive Measurements / Idle mode / NE-DC / RRCRelease configuration | Rel-16 | C191 | UEs supporting 5G Core, E-UTRA and Idle/Inactive Measurements | + +| | | | | | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------------|--------|------|-----------------------------------------------------------------------------------------------------------------| +| 8.2.6.4 | UPIP / RRC connection | | | | +| 8.2.6.4.1 | UPIP / RRC connection establishment / Success / Reception of SecurityModeCommand by the UE | Rel-17 | C286 | UEs supporting EN-DC and user plane integrity protection with EPS | +| 8.2.6.4.2 | UPIP / RRC connection re-establishment / Reception of the RRCConnection Reestablishment by UE | Rel-17 | C286 | UEs supporting EN-DC and user plane integrity protection with EPS | +| 8.2.6.4.3 | UPIP / RRC connection reconfiguration / Handover / Success / Reception of RRCConnectionReconfiguration including mobilityControlInfo by UE | Rel-17 | C286 | UEs supporting EN-DC and user plane integrity protection with EPS | +| 8.2.6.4.4 | UPIP / Inter-RAT mobility - Handover to E-UTRA - Reception of RRCConnection Reconfiguration by UE | Rel-17 | C286 | UEs supporting EN-DC and user plane integrity protection with EPS | +| 8.2.7 | RRC resume | | | | +| 8.2.7.1 | RRC resume / EN-DC | | | | +| 8.2.7.2 | RRC resume / NR-DC | | | | +| 8.2.7.2.1 | RRC Resume / Suspend-Resume / RRC reconfiguration / NR-DC / Resume with SCG | Rel-16 | C229 | UEs supporting 5G Core and NR-DC and RRC_INACTIVE and (re-)configuration of an SCG during the resume procedure. | +| 8.2.7.3.1 | RRC Resume / Suspend-Resume / RRC reconfiguration / NE-DC / Resume with SCG | Rel-16 | C255 | UEs supporting 5G Core and NE-DC and RRC_INACTIVE and (re-)configuration of an SCG during the resume procedure. | + +**Table 4.1-3b: Additional Information of Applicability of Protocol conformance RRC test cases, ref. TS 38.523-1 [2]** + +| Clause | Specific ICS | Specific IEXIT | Number of TC Executions | Release other RAT | +|----------------|--------------------------|----------------|----------------------------------------------------------------------------|-------------------| +| 8.1.1 | | | | | +| 8.1.1.1 | | | | | +| 8.1.1.1.1 | pc_inactiveState | | | | +| 8.1.1.1.2 | pc_inactiveState | | | | +| 8.1.1.3 | | | | | +| 8.1.1.3.2 | | | | Rel-15 E-UTRA | +| 8.1.1.3.4 | | | | Rel-15 E-UTRA | +| 8.1.1.3.7a | | | | Rel-15 E-UTRA | +| 8.1.2 | | | | | +| 8.1.2.1 | | | | | +| 8.1.2.1.6 | pc_Set_MUSIM_UAI_Info_NR | | | | +| 8.1.3 | | | | | +| 8.1.3.1 | | | | | +| 8.1.3.1.2 | | | | | +| 8.1.3.1.3 | | | If 8.1.3.1.2 is executed this test case is optional (Note 2) | | +| 8.1.3.1.4 | | | If 8.1.3.1.2 or 8.1.3.1.3 is executed this test case is optional (Note 2) | | +| 8.1.3.1.5 | | | If 8.1.3.1.6 is executed this test case is optional (Note 2) | | +| 8.1.3.1.6 | | | | | +| 8.1.3.1.7 | | | If 8.1.3.1.5 or 8.1.3.1.6 is executed this test case is optional (Note 2) | | +| 8.1.3.1.8 | | | If 8.1.3.1.9 or 8.1.3.1.10 is executed this test case is optional (Note 2) | | +| 8.1.3.1.9 | | | If 8.1.3.1.10 is executed this test case is optional (Note 2) | | +| 8.1.3.1.10 | | | | | +| 8.1.3.1.23 | pc_inactiveState | | | | +| 8.1.3.2 | | | | | +| 8.1.3.2.6 | | | | Rel-16 UTRA | +| 8.1.3.2.7 | | | | Rel-16 UTRA | +| 8.1.4 | | | | | + +| | | | | | +|------------------|-----------------------|------------------------------------------------------------------------|----------------------------------------------------------------------------|---------------| +| 8.1.4.1 | | | | | +| 8.1.4.1.2 | | px_NAS_5GC_CipheringAlgo
rithm
px_NAS_5GC_IntegrityAlgo
rithm | | | +| 8.1.4.1.10 | | | Note 4 | | +| 8.1.4.2 | | | | | +| 8.1.4.2.1 | | | | | +| 8.1.4.2.1.1 | | | | Rel-15 E-UTRA | +| 8.1.4.2.1.2 | | | | Rel-16 EN-DC | +| 8.1.4.2.2 | | | | | +| 8.1.4.2.2.1 | | | | Rel-15 E-UTRA | +| 8.1.4.3 | | | | | +| 8.1.4.3.4 | | | | | +| 8.1.4.3.4.1 | | | If 8.1.4.3.4.2 is executed
this test case is optional | | +| 8.1.4.3.4.2 | | | If 8.1.4.3.4.1 is executed
this test case is optional | | +| 8.1.4.3.5 | | | | | +| 8.1.4.3.5.1 | | | If 8.1.4.3.5.2 is executed
this test case is optional | | +| 8.1.4.3.5.2 | | | If 8.1.4.3.5.1 is executed
this test case is optional | | +| 8.1.5 | | | | | +| 8.1.5.1 | | | | | +| 8.1.5.1.1 | | | If 8.2.1.1.2 is executed
this test case is optional | | +| 8.1.5.7 | | | | | +| 8.1.5.7.1 | | | | | +| 8.1.5.7.1.1 | | | If 8.1.5.7.1.2 or
8.1.5.7.1.3 is executed
this test case is optional | | +| 8.1.5.7.1.2 | | | If 8.1.5.7.1.1 or
8.1.5.7.1.3 is executed
this test case is optional | | +| 8.1.5.7.1.3 | | | If 8.1.5.7.1.1 or
8.1.5.7.1.2 is executed
this test case is optional | | +| 8.1.5.8 | | | | | +| 8.1.5.8.1 | pc_inactiveState | | | | +| 8.1.5.8.2 | | | | | +| 8.1.5.8.2.1 | pc_inactiveState | | If 8.1.5.8.2.2 or
8.1.5.8.2.3 is executed
this test case is optional | | +| 8.1.5.8.2.2 | pc_inactiveState | | If 8.1.5.8.2.1 or
8.1.5.8.2.3 is executed
this test case is optional | | +| 8.1.5.8.2.3 | pc_inactiveState | | If 8.1.5.8.2.1 or
8.1.5.8.2.2 is executed
this test case is optional | | +| 8.1.5.9 | | | | | +| 8.1.5.9.1 | pc_Set_UE_Cap_Info_NR | | | | +| 8.1.6 | | | | | +| 8.1.6.1 | | | | | +| 8.1.6.1.3 | | | | | +| 8.1.6.1.3.1 | | | If 8.1.6.1.3.5 is executed
this test case is optional. | | +| 8.1.6.2 | | | | | +| 8.1.6.2.1 | | | | Rel-15 E-UTRA | +| 8.1.6.2.2 | | | | Rel-15 E-UTRA | +| 8.1.6.2.3 | | | | Rel-15 E-UTRA | +| 8.1.6.2.4 | | | | Rel-15 E-UTRA | +| 8.2.1 | | | | | +| 8.2.2 | | | | | +| 8.2.2.1 | | | | | +| 8.2.2.1.1 | | | Only executed if test
case 8.2.2.3.1 is not
applicable (Note 1) | | +| 8.2.2.1.2 | | | Only executed if test
case 8.2.2.3.2 is not
applicable (Note 1) | | +| 8.2.3 | | | | | +| 8.2.3.6 | | | | | +| 8.2.3.6.1 | | | | | + +| | | | | | +|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|----------------------------------------------------------------------------|---------------| +| 8.2.3.6.1a | | | If 8.2.3.6.1 is executed this test case is optional (Note 3) | | +| 8.2.3.6.1b | | | If 8.2.3.6.1 or 8.2.3.6.1a is executed this test case is optional (Note 3) | | +| 8.2.3.7 | | | | | +| 8.2.3.7.1 | | | | | +| 8.2.3.7.1a | | | If 8.2.3.7.1 is executed this test case is optional (Note 3) | | +| 8.2.3.7.1b | | | If 8.2.3.7.1 or 8.2.3.7.1a is executed this test case is optional (Note 3) | | +| 8.2.3.8 | | | | | +| 8.2.3.8.1 | | | | | +| 8.2.3.8.1a | | | If 8.2.3.8.1 is executed this test case is optional (Note 3) | | +| 8.2.3.8.1b | | | If 8.2.3.8.1 or 8.2.3.8.1a is executed this test case is optional (Note 3) | | +| 8.2.4 | | | | | +| 8.2.4.1 | | | | | +| 8.2.4.1.1 | | | | | +| 8.2.4.1.1.4 | | | | Rel-15 E-UTRA | +| 8.2.4.1.1.5 | | | | Rel-15 E-UTRA | +| 8.2.4.1.1.6 | | | | Rel-15 E-UTRA | +| 8.2.6 | | | | | +| 8.2.6.1 | | | | | +| 8.2.6.1.1 | | | | | +| 8.2.6.1.1.1 | | | If 8.2.6.1.1.2 or 8.2.6.1.1.3 is executed this test case is optional | | +| 8.2.6.1.1.2 | | | If 8.2.6.1.1.1 or 8.2.6.1.1.3 is executed this test case is optional | | +| 8.2.6.1.1.3 | | | If 8.2.6.1.1.1 or 8.2.6.1.1.2 is executed this test case is optional | | +| 8.2.6.1.2 | | | | | +| 8.2.6.1.2.1 | | | If 8.2.6.1.2.2 or 8.2.6.1.2.3 is executed this test case is optional | | +| 8.2.6.1.2.2 | | | If 8.2.6.1.2.1 or 8.2.6.1.2.3 is executed this test case is optional | | +| 8.2.6.1.2.3 | | | If 8.2.6.1.2.1 or 8.2.6.1.2.2 is executed this test case is optional | | +| 8.2.6.2 | | | | | +| 8.2.6.2.4 | pc_reducedCP_Latency | | | | +| Note 1: | Test cases 8.2.2.3.1 also verifies the core requirements covered by test case 8.2.2.1.1 but it is not applicable to all UE. Test case 8.2.2.3.2 and 8.2.2.1.2 are also in the same situation. | | | | +| Note 2: | Only one among the three intra-frequency, inter-frequency and inter-band variants is required to be executed making sure all three variants are tested at least once across measurement events A3/A4/A5. | | | | +| Note 3: | Only intra frequency among the three (intra-frequency, inter-frequency and inter-band) variants is required to be executed for measurement events A3/A4/A5 based on initial market requirements. May change in future similar to Note 2. | | | | +| Note 4: | This test case can optionally be executed from Release 15 onwards. | | | | + +**Table 4.1-4a: Applicability of Protocol conformance Mobility and Session management test cases, ref. TS 38.523-1 [2]** + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|--------------|-------------------------------------------------|---------|-------------------------|-----------------------| +| 9 | Mobility management | | | | +| 9.1 | 5GS mobility management | | | | +| 9.1.1 | Primary authentication and key agreement | | | | + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------------------|-----------------------------------------------| +| 9.1.1.1 | EAP based primary authentication and key agreement / EAP-AKA' related procedures | Rel-15 | C21 | UEs supporting 5G Core | +| 9.1.1.2 | EAP based primary authentication and key agreement / Reject | Rel-15 | C21 | UEs supporting 5G Core | +| 9.1.1.3 | EAP based primary authentication and key agreement / EAP message transport / Abnormal | Rel-15 | C21 | UEs supporting 5G Core | +| 9.1.1.4 | 5G AKA based primary authentication and key agreement / 5G-AKA related procedures | Rel-15 | C21 | UEs supporting 5G Core | +| 9.1.1.5 | 5G AKA based primary authentication and key agreement / Reject | Rel-15 | C21 | UEs supporting 5G Core | +| 9.1.1.6 | 5G AKA based primary authentication and key agreement / Abnormal | Rel-15 | C21 | UEs supporting 5G Core | +| 9.1.2 | Security mode control | | | | +| 9.1.2.1 | NAS security mode command | Rel-15 | C21 | UEs supporting 5G Core | +| 9.1.2.2 | Protection of initial NAS signalling messages | Rel-15 | C21 | UEs supporting 5G Core | +| 9.1.2.3 | Integrity protection / Correct functionality of 5G NAS integrity algorithm / SNOW3G | Rel-15 | C21 | UEs supporting 5G Core | +| 9.1.2.4 | Integrity protection / Correct functionality of 5G NAS integrity algorithm / AES | Rel-15 | C21 | UEs supporting 5G Core | +| 9.1.2.5 | Integrity protection / Correct functionality of 5G NAS integrity algorithm / ZUC | Rel-15 | C84 | UEs supporting 5G Core and ZUC algorithm | +| 9.1.2.6 | Ciphering and deciphering / Correct functionality of 5G NAS encryption algorithm / SNOW3G | Rel-15 | C21 | UEs supporting 5G Core | +| 9.1.2.7 | Ciphering and deciphering / Correct functionality of 5G NAS encryption algorithm / AES | Rel-15 | C21 | UEs supporting 5G Core | +| 9.1.2.8 | Ciphering and deciphering / Correct functionality of 5G NAS encryption algorithm / ZUC | Rel-15 | C84 | UEs supporting 5G Core and ZUC algorithm | +| 9.1.3 | Identification | | | | +| 9.1.3.1 | Identification procedure | Rel-15 | C21 | UEs supporting 5G Core | +| 9.1.4 | Generic UE configuration update | | | | +| 9.1.4.1 | Generic UE configuration update / New 5G-GUTI, NITZ, registration requested, network slicing indication, new allowed NSSAI / Acknowledgement from the UE | Rel-15 | C21 | UEs supporting 5G Core | +| 9.1.4.2 | UAS / Generic UE configuration update / Revocation | Rel-17 | C310 | UEs supporting 5G Core and UAS | +| 9.1.5 | Registration | | | | +| 9.1.5.1 | Initial registration | | | | +| 9.1.5.1.1 | Initial registration / Success / 5G-GUTI reallocation, last visited TAI | Rel-15 | C21 | UEs supporting 5G Core | +| 9.1.5.1.2 | Initial registration / 5GS services / Equivalent PLMN list handling | Rel-15 | C21 | UEs supporting 5G Core | +| 9.1.5.1.3 | Initial registration / 5GS services / NSSAI handling | Rel-15 | C21 | UEs supporting 5G Core | +| 9.1.5.1.3a | Initial registration / 5GS services / NSSAI handling / NSSAI storage | Rel-15 | C21 | UEs supporting 5G Core | +| 9.1.5.1.4 | Initial registration / 5GS services / MICO mode / TAI list handling | Rel-15 | C313 | UEs supporting 5G Core and MICO mode | +| 9.1.5.1.5 | Initial registration / Abnormal / Failure after 5 attempts | Rel-15 | C21 | UEs supporting 5G Core | +| 9.1.5.1.6 | Initial registration / Rejected / Illegal UE | Rel-15 | C21 | UEs supporting 5G Core | +| 9.1.5.1.7 | Void | | | | +| 9.1.5.1.8 | Initial registration / Rejected / Serving network not authorized | Rel-15 | C21 | UEs supporting 5G Core | +| 9.1.5.1.9 | Initial registration / Abnormal / Change of cell into a new tracking area | Rel-15 | C21 | UEs supporting 5G Core | +| 9.1.5.1.10 | Initial registration / Rejected / PLMN not allowed | Rel-15 | C21 | UEs supporting 5G Core | +| 9.1.5.1.11 | Initial registration / Rejected / Tracking area not allowed | Rel-15 | C21 | UEs supporting 5G Core | +| 9.1.5.1.12 | Initial registration / Rejected / Roaming not allowed in this tracking area | Rel-15 | C21 | UEs supporting 5G Core | +| 9.1.5.1.13 | Initial registration / Rejected / No suitable cells in tracking area | Rel-15 | C21 | UEs supporting 5G Core | +| 9.1.5.1.14 | Initial registration / Rejected / Congestion / Abnormal / T3346 | Rel-15 | C21 | UEs supporting 5G Core | +| 9.1.5.1.15 | Initial registration / Success / Extended and spare fields in Registration Accept message | Rel-15 to Rel-17 only | C21 | UEs supporting 5G Core | +| 9.1.5.1.16 | Initial Registration / Success / MUSIM | Rel-17 | C219 | UEs supporting 5G Core and Multi-SIM features | +| 9.1.5.1.17 | Initial registration / Success / UAS | Rel-17 | C310 | UEs supporting 5G Core and UAS | + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-------------------------|-------------------------------------------------------------------------------| +| 9.1.5.2 | Mobility and periodic registration update | | | | +| 9.1.5.2.1 | Mobility registration update / TAI list handling | Rel-15 | C21 | UEs supporting 5G Core | +| 9.1.5.2.2 | Periodic registration update / Accepted | Rel-15 | C21 | UEs supporting 5G Core | +| 9.1.5.2.4 | Mobility registration update / The lower layer requests NAS signalling connection recovery | Rel-15 | C21 | UEs supporting 5G Core | +| 9.1.5.2.5 | Void | | | | +| 9.1.5.2.7 | Mobility and periodic registration update / Rejected / UE identity cannot be derived by the network | Rel-15 | C21 | UEs supporting 5G Core | +| 9.1.5.2.8 | Mobility and periodic registration update / Rejected / Implicitly de-registered | Rel-15 | C21 | UEs supporting 5G Core | +| 9.1.5.2.9 | Void | | | | +| 9.1.5.2.10 | Mobility registration update / MUSIM / NAS signalling connection release | Rel-17 | C242 | UEs supporting 5G Core and Multi-SIM N1 NAS signalling connection release | +| 9.1.5.2.11 | UAS / Mobility and periodic registration update / UUAA / Rejected | Rel-17 | C310 | UEs supporting 5G Core and UAS | +| 9.1.6 | De-registration | | | | +| 9.1.6.1 | UE-initiated de-registration | | | | +| 9.1.6.1.1 | UE-initiated de-registration / Switch off / Abnormal / De-registration and 5GMM common procedure collision | Rel-15 | C21 | UEs supporting 5G Core | +| 9.1.6.1.2 | UE-initiated de-registration / Normal de-registration / Abnormal / Transmission failure without TAI change from lower layers, de-registration and 5GMM common procedure collision, T3521 timeout | Rel-15 | C21 | UEs supporting 5G Core | +| 9.1.6.1.3 | UE-initiated de-registration / Abnormal / Change of cell into a new tracking area | Rel-15 | C21 | UEs supporting 5G Core | +| 9.1.6.1.4 | Void | | | | +| 9.1.6.2 | Network-initiated de-registration | | | | +| 9.1.6.2.1 | Network-initiated de-registration / De-registration for 3GPP access / Re-registration required | Rel-15 | C21 | UEs supporting 5G Core | +| 9.1.6.2.2 | Network-initiated de-registration / De-registration for 3GPP access / Re-registration not required | Rel-15 | C21 | UEs supporting 5G Core | +| 9.1.6.2.3 | UAS / De-registration / UE-initiated / Network-initiated | Rel-17 | C310 | UEs supporting 5G Core and UAS | +| 9.1.7 | Service request | | | | +| 9.1.7.1 | Service request / Idle mode uplink user data transport / Rejected / Restricted service area, abnormal / T3517, T3525 | Rel-15 | C21 | UEs supporting 5G Core | +| 9.1.7.2 | Service request / Connected mode user data transport / Abnormal / T3517 | Rel-15 | C21 | UEs supporting 5G Core | +| 9.1.7.3 | Service request / MUSIM / NAS signalling connection release | Rel-17 | C242 | UEs supporting 5G Core and Multi-SIM N1 NAS signalling connection release | +| 9.1.7.4 | Service request / MUSIM / Rejection of paging | Rel-17 | C220 | UEs supporting 5G Core and Multi-SIM Reject paging request | +| 9.1.8 | SMS over NAS | | | | +| 9.1.8.1 | SMS over NAS / MO and MT SMS over NAS / Idle mode | Rel-15 | C33 | UEs supporting 5G Core and SMS over NAS and UE configured to not use SMSoIP | +| 9.1.8.2 | SMS over NAS / Multiple MO and MT SMS over NAS / Connected mode | Rel-15 | C33 | UEs supporting 5G Core and SMS over NAS and UE configured to not use SMSoIP | +| 9.1.9 | RACS | | | | +| 9.1.9.1 | RACS / Network assigned UE radio capability ID | Rel-16 | C108 | UEs supporting 5G Core and RACS | +| 9.1.9.2 | RACS / UE configuration update / UE radio capability ID | Rel-16 | C108 | UEs supporting 5G Core and RACS | +| 9.1.9.3 | RACS / PLMN change within registration area / From NW assigned to Manufacturer assigned UE Radio Capability ID | Rel-16 | C177 | UEs supporting 5G Core and RACS and Manufacturer assigned Radio Capability ID | +| 9.1.9.4 | RACS / USIM change / Handling of URCID | Rel-16 | C108 | UEs supporting 5G Core and RACS | +| 9.1.9.5 | RACS / Handling of delete indication for NW assigned UE radio capability ID | Rel-16 | C108 | UEs supporting 5G Core and RACS | +| 9.1.9.6 | RACS / Change in radio capability / NW assigned URCID | Rel-16 | C108 | UEs supporting 5G Core and RACS | +| 9.1.9.7 | RACS / Inter-system mobility registration update / Handling of UE radio capability ID | Rel-16 | C178 | UEs supporting 5G Core and E-UTRA and RACS | +| 9.1.10 | Network slice-specific authentication and authorization | | | | +| 9.1.10.1 | NSSAA / EAP message transport / Success | Rel-16 | C147 | UEs supporting 5G Core and NSSAA and EAP-AKA' for NSSAA | +| 9.1.10.2 | NSSAA / EAP message transport / Abnormal | Rel-16 | C147 | UEs supporting 5G Core and NSSAA and EAP- | + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|---------------|-----------------------------------------------------------------------------------|---------|-------------------------|---------------------------------------------------------------------------| +| 9.1.10.3 | NSSAA / Initial registration / Rejected NSSAI, pending NSSAI | Rel-16 | C147 | AKA' for NSSAA
UEs supporting 5G Core and NSSAA and EAP-AKA' for NSSAA | +| 9.1.10.4 | NSSAA / Initial registration / Reject | Rel-16 | C147 | UEs supporting 5G Core and NSSAA and EAP-AKA' for NSSAA | +| 9.1.10.6 | NSSAA / UE configuration update / Rejected NSSAI | Rel-16 | C147 | UEs supporting 5G Core and NSSAA and EAP-AKA' for NSSAA | +| 9.1.11 | SNPN / Mobility management aspects | | | | +| 9.1.11.1 | SNPN / Initial registration / Rejected / Temporarily not authorized for this SNPN | Rel-16 | C131 | UEs supporting 5G Core and SNPN | +| 9.1.11.2 | SNPN / Initial registration / Rejected / Permanently not authorized for this SNPN | Rel-16 | C131 | UEs supporting 5G Core and SNPN | + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 9.1.11.3 | SNPN / EAP based primary authentication and key agreement / EAP-AKA' related procedures | Rel-16 | C131 | UEs supporting 5G Core and SNPN | +| 9.1.11.4 | SNPN / Initial registration / Rejected / Tracking area not allowed / Access to an SNPN using credentials from a credentials holder | Rel-17 | C304 | UEs supporting 5G Core and accessing SNPN using credentials assigned by a Credentials Holder separate from the SNPN | +| 9.1.11.5 | SNPN / Initial registration / Rejected / Illegal ME / Access to an SNPN for onboarding services | Rel-17 | C305 | UEs supporting 5G Core and Onboarding SNPN (hence supports Default UE Credentials) | +| 9.1.11.6 | SNPN / EAP-AKA' related procedures / UE handling EAP-failure message / Register for onboarding services and access to an SNPN using credentials from a credentials holder | Rel-17 | C341 | UEs supporting 5G Core and accessing SNPN using credentials assigned by a Credentials Holder separate from the SNPN and Onboarding SNPN (hence supports Default UE Credentials) | +| 9.1.11.7 | SNPN / 5G AKA based primary authentication and key agreement procedure / Authentication not accepted by the network / Register for onboarding services and access to an SNPN using credentials from a credentials holder | Rel-17 | C341 | UEs supporting 5G Core and accessing SNPN using credentials assigned by a Credentials Holder separate from the SNPN and Onboarding SNPN (hence supports Default UE Credentials) | +| 9.1.12 | NSAC / Mobility management aspects | | | | +| 9.1.12.1 | NSAC / Initial registration / Back-off timer | Rel-17 | C329 | UEs supporting 5G Core and UE supporting extended rejected NSSAI | +| 9.1.12.2 | NSAC / Initial registration / Back-off timer is not provided or zero | Rel-17 | C329 | UEs supporting 5G Core and UE supporting extended rejected NSSAI | +| 9.1.12.3 | NSAC / Initial registration / Rejected / equivalent PLMNs | Rel-17 | C329 | UEs supporting 5G Core and UE supporting extended rejected NSSAI | +| 9.1.12.4 | NSAC / Generic UE configuration update / Rejected NSSAI | Rel-17 | C329 | UEs supporting 5G Core and UE supporting extended rejected NSSAI | +| 9.1.12.5 | NSAC / De-registration / 5GMM cause value #62 and rejected NSSAI | Rel-17 | C329 | UEs supporting 5G Core and UE supporting extended rejected NSSAI | +| 9.1.13 | NSSRG / Mobility management aspects | | | | +| 9.1.13.1 | NSSRG / Initial registration | Rel-17 | C230 | UEs supporting 5G Core and NSSRG | +| 9.1.13.2 | NSSRG / Generic UE configuration update | Rel-17 | C230 | UEs supporting 5G Core and NSSRG | +| 9.1.14 | Paging Early Indication with Paging Subgrouping Assistance | | | | +| 9.1.14.1 | Paging Early Indication with Paging Subgrouping Assistance / Registration / provision and deletion of PEIPS assistance information | Rel-17 | C224A | UEs supporting 5G Core and PEI and PEIPS | +| 9.2 | 5GS Non-3GPP Access Mobility Management | | | | +| 9.2.1 | Primary authentication and key agreement procedure | | | | +| 9.2.1.1 | EAP based primary authentication and key agreement | Rel-15 | C29 | UEs supporting 5G core over non-3GPP Access Network and WLAN | +| 9.2.1.2 | 5G AKA based primary authentication and key agreement | Rel-15 | C29 | UEs supporting 5G core over non-3GPP Access Network and WLAN | +| 9.2.2 | Security Mode Control | | | | +| 9.2.2.1 | NAS security mode command | Rel-15 | C29 | UEs supporting 5G core over non-3GPP Access Network and WLAN | +| 9.2.2.2 | Protection of initial NAS signalling messages | Rel-15 | C29 | UEs supporting 5G core over non-3GPP Access Network and WLAN | +| 9.2.3 | Void | | | | +| 9.2.4 | Generic UE configuration | | | | +| 9.2.4.1 | Generic UE configuration update | Rel-15 | C29 | UEs supporting 5G core over non-3GPP Access Network and WLAN | +| 9.2.5 | Registration | | | | +| 9.2.5.1 | Initial Registration | | | | +| 9.2.5.1.1 | Initial registration / Success / 5G-GUTI reallocation, Last visited TAI | Rel-15 | C29 | UEs supporting 5G core over non-3GPP Access Network and WLAN | +| 9.2.5.1.2 | Initial registration / 5GS services / NSSAI handling | Rel-15 | C29 | UEs supporting 5G core over non-3GPP Access Network and WLAN | +| 9.2.5.1.3 | Void | | | | +| 9.2.5.1.4 | Initial registration / Rejected / Congestion / Abnormal cases / T3346 | Rel-15 | C29 | UEs supporting 5G core over non-3GPP Access Network and WLAN | +| 9.2.5.2 | Mobility Registration | | | | +| 9.2.5.2.1 | Void | | | | +| 9.2.5.2.2 | Mobility registration update/Change of SMS over NAS capability | Rel-15 | C29 | UEs supporting 5G core over non-3GPP Access Network and WLAN | +| 9.2.6 | De-registration | | | | +| 9.2.6.1 | UE-initiated de-registration | | | | +| 9.2.6.1.1 | UE-initiated de-registration / switch off | Rel-15 | C29 | UEs supporting 5G core over non-3GPP Access Network and WLAN | +| 9.2.6.2 | Network-initiated de-registration | | | | +| 9.2.6.2.1 | Network-initiated de-registration / De-registration for Non-3GPP access / Re- | Rel-15 | C29 | UEs supporting 5G core over non-3GPP Access Network and WLAN | + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|---------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | registration required | | | | +| 9.2.6.2.2 | Network-initiated de-registration / De-registration for Non 3GPP access / Re-registration not required | Rel-15 | C29 | UEs supporting 5G core over non-3GPP Access Network and WLAN | +| 9.2.7 | Service request | | | | +| 9.2.7.1 | Service request / IDLE mode uplink user data transport / Rejected / Restricted service area, Abnormal / T3517 | Rel-15 | C29 | UEs supporting 5G core over non-3GPP Access Network and WLAN | +| 9.2.7.2 | Service request / CMM CONNECTED mode/uplink user data transport / Abnormal / T3517 | Rel-15 | C58 | UEs supporting 5G core over non-3GPP Access Network, WLAN and (ICMP or ICMP IPv6) | +| 9.2.8 | SMS over NAS | | | | +| 9.2.8.1 | SMS over NAS / MO SMS over NAS - 5GMM-Idle mode | Rel-15 | C30 | UEs supporting 5G core over non-3GPP Access Network and SMS over NAS and WLAN | +| 9.3 | Inter-system mobility | | | | +| 9.3.1 | 5GS-EPC Inter-system mobility | | | | +| 9.3.1.1 | Inter-system mobility registration update / Single-registration mode with N26 / 5GMM-IDLE / 5GC to EPC | Rel-15 | C26 | UEs supporting 5GS and E-UTRA | +| 9.3.1.2 | Inter-system mobility registration update / Single-registration mode with N26 / 5GMM-IDLE / EPC to 5GC | Rel-15 | C26 | UEs supporting 5GS and E-UTRA | +| 9.3.1.3 | Inter-system mobility and periodic registration update / Rejected / Single-registration mode with N26 / Handling of EPC relevant parameters | Rel-15 | C26 | UEs supporting 5GS and E-UTRA | +| 9.3.1.4 | NSAC / interworking with EPC | Rel-17 | C260 | UEs supporting 5GS and E-UTRA and NSSRG and UE supporting extended rejected NSSAI | +| 9.3.1.5 | Inter-system mobility registration update / Single registration mode with N26 interface / No E-UTRA Disabling In 5GS / attach attempt counter is equal to 5 /Success | Rel-17 | C324 | UEs supporting 5G Core and E-UTRA and No E-UTRA Disabling In 5GS and disabling E-UTRA capability when attach attempt counter or tracking area updating attempt counter is equal to 5 | +| 9.3.1.6 | Inter-system mobility registration update / Single registration mode with N26 interface / No E-UTRA Disabling In 5GS / tracking area updating attempt counter is equal to 5 / Success | Rel-17 | C324 | UEs supporting 5G Core and E-UTRA and No E-UTRA Disabling In 5GS and disabling E-UTRA capability when attach attempt counter or tracking area updating attempt counter is equal to 5 | +| 9.4 | Non-Terrestrial Network | | | | +| 9.4.1 | 5GS mobility management for Non-Terrestrial Network | | | | +| 9.4.1.1 | NR NTN / GNSS position reporting / reject cause #78 "PLMN not allowed to operate at the present UE location" | Rel-17 | C309 | UEs supporting 5G Core and NR NTN access | +| 9.4.1.2 | NR NTN / Mobility registration update / supported TACs not part of UE registration area | Rel-17 | C309 | UEs supporting 5G Core and NR NTN access | +| 9.4.1.3 | NR NTN / TAI(s) not allowed / forbidden TAI(s) in the Registration Accept message | Rel-17 | C309 | UEs supporting 5G Core and NR NTN access | +| 10 | Session management | | | | +| 10.1 | 5GS session management | | | | +| 10.1.1 | PDU session authentication and authorization | | | | +| 10.1.1.1 | PDU session authentication and authorization / During the UE-requested PDU session procedure | Rel-15 | C39A | UEs supporting 5G Core and additional UE-requested PDU establishment and support of EAP-AKA' as EAP method for PDU session authentication and authorization | +| 10.1.1.2 | PDU session authentication and authorization / After the UE-requested PDU session procedure | Rel-15 | C39A | UEs supporting 5G Core and additional UE-requested PDU establishment and support of EAP-AKA' as EAP method for PDU session authentication and authorization | +| 10.1.2 | Network-requested PDU session modification | | | | +| 10.1.2.1 | Network-requested PDU session modification / Accepted | Rel-15 | C21 | UEs supporting 5G Core | +| 10.1.2.2 | Network-requested PDU session modification / Abnormal / PDU session in state PDU SESSION INACTIVE | Rel-15 | C39 | UEs supporting 5G Core and additional UE-requested PDU establishment | +| 10.1.2.3 | Network-requested PDU session modification / new P-CSCF address / Initial IMS registration | Rel-15 | C325 | UEs supporting 5G Core and capable of being configured to initiate P-CSCF Discovery via PCO | +| 10.1.3 | Network-requested PDU session release | | | | +| 10.1.3.1 | Void | | | | +| 10.1.3.2 | Network-requested PDU session release / Insufficient resources, insufficient resources for specific slice and DNN, abnormal / Invalid PDU | Rel-15 | C39 | UEs supporting 5G Core and additional UE-requested PDU establishment | + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|---------------|----------------------------------------------------------------------------------------------------------------------------|---------|-------------------------|---------------------------------------------------------------------------------------------------------------------| +| | session identity | | | | +| 10.1.3.3 | Network-requested PDU session release / reactivation requested / new P-CSCF address / Initial IMS registration | Rel-15 | C325 | UEs supporting 5G Core and capable of being configured to initiate P-CSCF Discovery via PCO | +| 10.1.4 | UE-requested PDU session establishment | | | | +| 10.1.4.1 | UE-requested PDU session establishment / Abnormal / T3580 | Rel-15 | C39 | UEs supporting 5G Core and additional UE-requested PDU establishment | +| 10.1.4.2 | UAS / UE requested PDU session establishment / UUAA / Release | Rel-17 | C310 | UEs supporting 5G Core and UAS | +| 10.1.4.3 | UAS / UE requested PDU session establishment / UUAA / C2 authorisation / Modification / Release | Rel-17 | C310 | UEs supporting 5G Core and UAS | +| 10.1.5 | UE-requested PDU session modification | | | | +| 10.1.5.1 | UE-requested PDU session modification | Rel-15 | C63 | UEs supporting 5G Core and UE requested PDU session modification procedure | +| 10.1.6 | UE-requested PDU session release | | | | +| 10.1.6.1 | UE-requested PDU session release / Abnormal / Collision with network-requested PDU session modification procedure | Rel-15 | C21 | UEs supporting 5G Core | +| 10.1.6.2 | UE-requested PDU session release / Abnormal / Collision with network-requested PDU session release procedure | Rel-15 | C21 | UEs supporting 5G Core | +| 10.1.7 | Network-requested PDU session release | | | | +| 10.1.7.1 | Void | | | | +| 10.1.8 | S-NSSAI based congestion control | | | | +| 10.1.8.1 | PDU session establishment reject / Maximum number of PDU sessions reached / Back-off timer is neither zero nor deactivated | Rel-15 | C39 | UEs supporting 5G Core and additional UE-requested PDU establishment | +| 10.1.8.2 | PDU session establishment reject / Maximum number of PDU sessions reached / Back-off timer is deactivated | Rel-16 | C39 | UEs supporting 5G Core and additional UE-requested PDU establishment | +| 10.1.8.3 | PDU session establishment reject / Maximum number of PDU sessions reached / Back-off timer is zero or not included | Rel-15 | C39 | UEs supporting 5G Core and additional UE-requested PDU establishment | +| 10.1.8.4 | 5GSM message not forwarded / Back-off timer | Rel-15 | C39 | UEs supporting 5G Core and additional UE-requested PDU establishment | +| 10.1.8.5 | Maximum number of PDU sessions reached / Emergency service | Rel-15 | C261 | UEs supporting 5G Core and additional UE-requested PDU establishment and emergency services in NR connected to 5GCN | +| 10.2 | EN-DC session management | | | | +| 10.2.1 | Network initiated procedures | | | | +| 10.2.1.1 | Default EPS bearer context activation | Rel-15 | C01 | UEs supporting EN-DC | +| 10.2.1.2 | Dedicated EPS bearer context activation | Rel-15 | C01 | UEs supporting EN-DC | +| 10.2.2 | UE initiated procedures | | | | +| 10.2.2.1 | EPS bearer resource allocation / modification | Rel-15 | C16 | UEs supporting EN-DC and UE requested bearer resource allocation and modification procedures | +| 10.3 | 5GS Non-3GPP Access Session Management | | | | +| 10.3.1 | PDU session authentication and authorization | | | | +| 10.3.1.1 | PDU session authentication and authorization / during the UE-requested PDU session procedure | Rel-15 | C159 | UEs supporting 5G core over non-3GPP Access Network and WLAN and additional UE-requested PDU establishment | +| 10.3.2 | Network-requested PDU session modification | | | | +| 10.3.2.1 | Network-requested PDU session modification /Accepted/Rejected | Rel-15 | C29 | UEs supporting 5G core over non-3GPP Access Network and WLAN | +| 10.3.3 | Network-requested PDU session Release | | | | +| 10.3.3.1 | Network-requested PDU session release / accepted/ with and without reactivation | Rel-15 | C29 | UEs supporting 5G core over non-3GPP Access Network and WLAN | +| 10.3.4 | UE-requested PDU session establishment | | | | +| 10.3.4.1 | UE-requested PDU session establishment / Abnormal / T3580 | Rel-15 | C29 | UEs supporting 5G core over non-3GPP Access Network and WLAN | +| 10.3.5 | UE-requested PDU session modification | | | | +| 10.3.5.1 | UE-requested PDU session modification/Success | Rel-15 | C29 | UEs supporting 5G core over non-3GPP Access Network and WLAN | +| 10.3.6 | UE-requested PDU session release | | | | +| 10.3.6.1 | UE-requested PDU session release / Abnormal / Collision with network-requested PDU session | Rel-15 | C29 | UEs supporting 5G core over non-3GPP Access Network and WLAN | + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | modification procedure | | | | +| 10.4 | ATSSS session management | | | | +| 10.4.1 | UE-requested MA PDU session management | | | | +| 10.4.1.1 | UE-requested MA PDU session establishment / ATSSS / Registered to same PLMNs over 3GPP and non-3GPP accesses simultaneously / Success | Rel-16 | C251 | UEs supporting 5G Core and 5G core over non-3GPP Access Network and WLAN and additional UE-requested PDU establishment and ATSSS | +| 10.4.1.2 | UE-requested MA PDU session establishment / ATSSS / Registered to same PLMNs over 3GPP and non-3GPP accesses simultaneously / Success | Rel-16 | C251 | UEs supporting 5G Core and 5G core over non-3GPP Access Network and WLAN and additional UE-requested PDU establishment and ATSSS | +| 10.4.1.3 | UE-requested MA PDU session establishment / ATSSS / Registered to different PLMNs over 3GPP and non-3GPP accesses simultaneously/ Success | Rel-16 | C251 | UEs supporting 5G Core and 5G core over non-3GPP Access Network and WLAN and additional UE-requested PDU establishment and ATSSS | +| 10.4.1.4 | UE-requested MA PDU session establishment / ATSSS / Registered to different PLMNs over 3GPP and non-3GPP accesses asynchronously / Success | Rel-16 | C251 | UEs supporting 5G Core and 5G core over non-3GPP Access Network and WLAN and additional UE-requested PDU establishment and ATSSS | +| 10.4.2 | Network-requested MA PDU session management | | | | +| 10.4.2.2 | Network-requested MA PDU session release / ATSSS / Accepted | Rel-16 | C251 | UEs supporting 5G Core and 5G core over non-3GPP Access Network and WLAN and additional UE-requested PDU establishment and ATSSS | +| 10.4.1.5 | UE-requested MA PDU session modification / ATSSS / Success | Rel-17 | C275 | UEs supporting 5G Core and 5G core over non-3GPP Access Network and WLAN and additional UE-requested PDU establishment and ATSSS | +| 10.4.1.6 | UE-requested MA PDU session modification / ATSSS / Abnormal / MA PDU session is not allowed | Rel-17 | C275 | UEs supporting 5G Core and 5G core over non-3GPP Access Network and WLAN and additional UE-requested PDU establishment and ATSSS | +| 10.5 | ATSSS with PDN connection as a user-plane resource | | | | +| 10.5.1 | UE-requested MA PDU session establishment | | | | +| 10.5.1.1 | UE-requested MA PDU session establishment / ATSSS / UE establishing PDN connection as a user-plane resource of an MA PDU session to be established / Success | Rel-17 | C326 | UEs supporting 5G Core and E-UTRA and additional UE-requested PDU establishment and ATSSS | +| 10.5.1.2 | UE-requested MA PDU session establishment / ATSSS / UE establishing a PDN connection as a user-plane resource of an already established MA PDU session / Success | Rel-17 | C327 | UEs supporting 5G Core and 5G core over non-3GPP Access Network and E-UTRA and WLAN and additional UE-requested PDU establishment and ATSSS | +| 10.5.2 | Release of user-plane resources | | | | +| 10.5.2.1 | UE-requested user-plane resource(s) release/ ATSSS / Accepted | Rel-17 | C319 | UEs supporting 5G Core and E-UTRA and 5G core over non-3GPP Access Network and WLAN and R17 ATSSS of establishing a PDN connection as the user plane resource of an MA PDU session in 5GS | +| 10.5.2.2 | Network-requested user-plane resource(s) release/ ATSSS / Accepted | Rel-17 | C319 | UEs supporting 5G Core and E-UTRA and 5G core over non-3GPP Access Network and WLAN and R17 ATSSS of establishing a PDN connection as the user plane resource of an MA PDU session in 5GS | + +**Table 4.1-4b: Additional Information of Applicability of Protocol conformance Mobility and Session Management test cases, ref. TS 38.523-1 [2]** + +| Clause | Specific ICS | Specific IUIT | Number of TC Executions | Release other RAT | +|----------------|------------------------------|---------------|-------------------------|-------------------| +| 9 | | | | | +| 9.1 | | | | | +| 9.1.6 | | | | | +| 9.1.6.1 | | | | | +| 9.1.6.1.1 | [10] pc_USIM_Removal | | | | +| 9.2 | | | | | +| 9.2.6 | | | | | +| 9.2.6.1 | | | | | +| 9.2.6.1.1 | [10] pc_USIM_Removal | | | | +| 9.2.7 | | | | | +| 9.2.7.2 | [10] pc_IPv4
[10] pc_IPv6 | | | | + +| | | | | | +|--------------|--|--|--|---------------| +| 9.3 | | | | | +| 9.3.1 | | | | | +| 9.3.1.1 | | | | Rel-15 E-UTRA | +| 9.3.1.2 | | | | Rel-15 E-UTRA | +| 9.3.1.3 | | | | Rel-15 E-UTRA | +| 10 | | | | | +| 10.1 | | | | | + +Table 4.1-5a: Applicability of Protocol conformance Multi-layer test cases, ref. TS 38.523-1 [2] + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 11 | Multi-layer and Services | | | | +| 11.1 | 5GS / EPS Fallback | | | | +| 11.1.1 | MO MMTEL voice call setup from NR RRC_IDLE / EPS Fallback with redirection / Single registration mode with N26 interface / Success | Rel-15 | C54 | UEs supporting 5G Core and E-UTRA and EPS IMS Voice (VoLTE in GSMA PRD IR.92: "IMS Profile for Voice and SMS") and EPS fallback | +| 11.1.1a | MO MMTEL enhanced voice service call setup from NR RRC_IDLE / EPS Fallback with redirection / Single registration mode with N26 interface / Success | Rel-15 | C173 | UEs supporting 5G Core and E-UTRA and NG.114 | +| 11.1.2 | MO MMTEL voice call setup from NR RRC_IDLE / EPS Fallback with redirection / Single registration mode without N26 interface / Success | Rel-15 | C54 | UEs supporting 5G Core and E-UTRA and EPS IMS Voice (VoLTE in GSMA PRD IR.92: "IMS Profile for Voice and SMS") and EPS fallback | +| 11.1.3 | MO MMTEL voice call setup from NR RRC_CONNECTED / EPS Fallback with handover / Single registration mode with N26 interface / Success | Rel-15 | C54 | UEs supporting 5G Core and E-UTRA and EPS IMS Voice (VoLTE in GSMA PRD IR.92: "IMS Profile for Voice and SMS") and EPS fallback | +| 11.1.3a | MO MMTEL enhanced voice service call setup from NR RRC_CONNECTED / EPS Fallback with handover / Single registration mode with N26 interface / Success | Rel-15 | C173 | UEs supporting 5G Core and E-UTRA and NG.114 | +| 11.1.4 | MO MMTEL voice call setup from NR RRC_CONNECTED / EPS Fallback with redirection / Single registration mode with N26 interface / E-UTRAN cell selection using cell status barred / Success | Rel-15 | C54 | UEs supporting 5G Core and E-UTRA and EPS IMS Voice (VoLTE in GSMA PRD IR.92: "IMS Profile for Voice and SMS") and EPS fallback | +| 11.1.5 | MO MMTEL voice call setup from NR RRC_CONNECTED / EPS Fallback with redirection / Single registration mode without N26 interface / E-UTRAN cell selection using cell status reservation / Success | Rel-15 | C54 | UEs supporting 5G Core and E-UTRA and EPS IMS Voice (VoLTE in GSMA PRD IR.92: "IMS Profile for Voice and SMS") and EPS fallback | +| 11.1.6 | MT MMTEL voice call setup from NR RRC_IDLE / EPS Fallback with redirection / Single registration mode without N26 interface / Success | Rel-15 | C54 | UEs supporting 5G Core and E-UTRA and EPS IMS (VoLTE in GSMA PRD IR.92: "IMS Profile for Voice and SMS") Voice and EPS fallback | +| 11.1.7 | Emergency call setup from NR RRC_IDLE / Emergency Services Fallback to EPS with redirection / Single registration mode with N26 interface / Success | Rel-15 | C173 | UEs supporting 5G Core and E-UTRA and NG.114 | +| 11.1.8 | MO MMTEL voice call setup from NR RRC_CONNECTED / EPS Fallback with handover / Single registration mode with N26 interface / voiceFallbackIndication | Rel-16 | C95 | UEs supporting 5G Core and E-UTRA and EPS IMS (VoLTE in GSMA PRD IR.92: "IMS Profile for Voice and SMS") Voice and EPS fallback and voiceFallbackIndication | +| 11.1.9 | MO MMTEL voice call setup from NR RRC_IDLE / EPS Fallback with redirection / Single registration mode with N26 interface / voiceFallbackIndication | Rel-16 | C95 | UEs supporting 5G Core and E-UTRA and EPS IMS (VoLTE in GSMA PRD IR.92: "IMS Profile for Voice and SMS") Voice and EPS fallback and voiceFallbackIndication | +| 11.1.10 | Void | | | | +| 11.2 | 5G-SRVCC | | | | +| 11.2.1 | 5G-SRVCC from NG-RAN to 3GPP UTRAN | Rel-16 | C127 | UEs supporting 5G Core and UTRA and NR to UTRA-FDD CELL_DCH CS handover | +| 11.3 | Unified Access Control (UAC) | | | | +| 11.3.1 | UAC / Access Identity 0 / 0% access probability / MTSI MO speech call / SMSIoP | Rel-15 | C78 | UEs supporting 5G Core and Initiating session and IMS voice over NR and MTSI speech and SMS over IP | +| 11.3.1a | UAC / Access Identity 0 / 0% access probability / Uplink user data transfer / RRC_INACTIVE | Rel-15 | C109A | UEs supporting 5G Core and RRC_INACTIVE and UE's usage setting as data centric | + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 11 | Multi-layer and Services | | | | +| 11.3.2 | UAC / Access Identity 0 / 0% access probability / Paging for MT access/Emergency call | Rel-15 | C92 | UEs supporting 5G Core and emergency services in NR connected to 5GCN | +| 11.3.3 | UAC / Access Identity 0 / AC8 / RRC_INACTIVE / RNA update / RRC resume | Rel-15 | C109 | UEs supporting 5G Core and RRC_INACTIVE | +| 11.3.4 | UAC / Access Identity 0 / Registration procedure for mobility and periodic registration update / Barring per PLMN / Implicit AC barring list | Rel-15 | C21 | UEs supporting 5G Core | +| 11.3.5 | UAC / Access Identity 1 / New cell not in the country of its HPLMN/EHPLMN 0% access probability / MPS indicator / HPLMN/0%/100% accessibility AC5 / MMTEL-Video call | Rel-15 | C79 | UEs supporting 5G Core and Initiating session and MTSI video and MTSI video H.265 MP MT Level 3.1 and MTSI video H.264 CHP Level 3.1 and H.264 CBP Level 3.1 and NG114 v1.0 | +| 11.3.6 | UAC / Access Identity 2 / New cell not in the country of its HPLMN/EHPLMN 0% access probability / MCS indicator / HPLMN/0%/100% accessibility AC7 / RRC_INACTIVE | Rel-15 | C21 | UEs supporting 5G Core | +| 11.3.6a | UAC / Access Identity 2 / MCS indicator / SNPN / 0% / 100% accessibility AC7 / RRC_INACTIVE | Rel-16 | C231 | UEs supporting 5G Core and SNPN and configuration of access identities in the list of subscriber data | +| 11.3.7 | UAC / Access Identity 11..15 / High priority access / HPLMN/0% accessibility AC2 / Emergency call | Rel-15 | C92 | UEs supporting 5G Core and emergency services in NR connected to 5GCN | +| 11.3.8 | UAC / Access Identity 0 / NR RRC_IDLE / Cell re-selection while T390 is running | Rel-15 | C21 | UEs supporting 5G Core | +| 11.3.9 | UAC / Access Identity 0 / ODAC / PLMN / RPLMN / not EPLMN | Rel-15 | C21 | UEs supporting 5G Core | +| 11.3.9a | UAC / Access Identity 0 / ODAC / SNPN / RSNPN / new SNPN | Rel-16 | C131 | UEs supporting 5G Core and SNPN | +| 11.3.10 | UAC / Access Identity 0 / AC9 / 0% access probability / SIP Re-registration | Rel-16 | C198 | UEs supporting 5G Core and IMS security | +| 11.3.11 | UAC / Access Identity 1 / 0% access probability / release with redirect with mpsPriorityIndication / RRC_INACTIVE | Rel-16 | C274A | UEs supporting 5G Core and RRC Connection release with MPS priority indication AND RRC_INACTIVE | +| 11.3.12 | UAC / Access Identity 0 / AC7 / 0% access probability / Uplink user data transfer | Rel-15 | C21 | UEs supporting 5G Core | +| 11.4 | Emergency Services | | | | +| 11.4.1 | 5GMM-REGISTERED.NORMAL-SERVICE / 5GMM-IDLE / Emergency call / Utilising emergency number stored on the USIM / New emergency PDU session / Network failing the authentication check (5G AKA) | Rel-15 | C92 | UEs supporting 5G Core and emergency services in NR connected to 5GCN | +| 11.4.1a | 5GMM-REGISTERED.NORMAL-SERVICE / 5GMM-IDLE / Emergency call / Utilising emergency number stored on the USIM / New emergency PDU session / PEIPS assistance information | Rel-17 | C224A | UEs supporting 5G Core and PEI and PEIPS | +| 11.4.2 | 5GMM-DEREGISTERED.LIMITED-SERVICE / Emergency call / Utilisation of emergency numbers stored on the ME / Initial registration for emergency services / Handling of forbidden PLMNs | Rel-15 | C92 | UEs supporting 5G Core and emergency services in NR connected to 5GCN | +| 11.4.3 | 5GMM-DEREGISTERED.NO-SUPI / Emergency call / Utilisation of emergency numbers stored on the ME / Initial registration for emergency services | Rel-15 | C238 | UEs supporting 5G Core and emergency services in NR connected to 5GCN and test execution with No USIM | +| 11.4.4 | 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE T3346 running / Emergency call establishment / 5GMM-REGISTERED.NORMAL-SERVICE / Emergency call establishment before T3396 expiry | Rel-15 | C92 | UEs supporting 5G Core and emergency services in NR connected to 5GCN | +| 11.4.5 | 5GMM-REGISTERED.LIMITED-SERVICE / 5GMM-IDLE / Emergency call establishment | Rel-15 | C92 | UEs supporting 5G Core and emergency services in NR connected to 5GCN | + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 11 | Multi-layer and Services | | | | +| | and release / Handling of 5GS forbidden tracking areas for roaming | | | | +| 11.4.6 | 5GMM-REGISTERED.NON-ALLOWED-SERVICE / Emergency call establishment and release / Handling of non-allowed tracking areas | Rel-15 | C92 | UEs supporting 5G Core and emergency services in NR connected to 5GCN | +| 11.4.7 | Handling of Local and Extended emergency numbers / Mobility | Rel-15 | C92 | UEs supporting 5G Core and emergency services in NR connected to 5GCN | +| 11.4.8 | Handling of Local and extended emergency numbers / Switch-off and maximum local numbers storage | Rel-15 | C92 | UEs supporting 5G Core and emergency services in NR connected to 5GCN | +| 11.4.9 | 5GMM-DEREGISTERED.LIMITED-SERVICE No suitable cells in tracking area / Emergency call establishment and release | Rel-15 | C92 | UEs supporting 5G Core and emergency services in NR connected to 5GCN | +| 11.4.10 | Void | | | | +| 11.4.10a | 5GMM-REGISTERED.NORMAL-SERVICE / N26 interface not supported / N1 mode to S1 mode transfer of an existing emergency PDU session | Rel-15 | C85B | UEs supporting 5G core and Emergency PDU session transfer from N1 mode to S1 mode when network does not support N26 interface, and, E-UTRA and EPS IMS emergency call (VoLTE in GSMA PRD IR.92: "IMS Profile for Voice and SMS") and IMS voice over NR | +| 11.4.11 | 5GMM-REGISTERED.NORMAL-SERVICE / N26 interface not supported / S1 mode to N1 mode transfer of an existing emergency PDN connection | Rel-15 | C85A | UEs supporting 5G core and Emergency PDN connection transfer from S1 mode to N1 mode when network does not support N26 interface, and, E-UTRA and EPS IMS emergency call (VoLTE in GSMA PRD IR.92: "IMS Profile for Voice and SMS") and emergency services in NR connected to 5GCN | +| 11.4.12 | 5GMM-REGISTERED.NORMAL-SERVICE / 5GMM-IDLE / Emergency call / Disabling N1 mode / Emergency call establishment over EPS / Success | Rel-15 | C176 | UEs supporting 5G Core and E-UTRA and EPS IMS emergency call (VoLTE in GSMA PRD IR.92: "IMS Profile for Voice and SMS") | +| 11.4.13 | 5GMM-REGISTERED.NORMAL-SERVICE / 5GMM-IDLE / Emergency call / obtaining new IP address different than the IP address | Rel-15 | C92 | UEs supporting 5G Core and emergency services in NR connected to 5GCN | +| 11.4.14 | 5GMM-REGISTERED.NORMAL-SERVICE / 5GMM-IDLE / Emergency call /Deregistration upon emergency registration expiration | Rel-15 | C92 | UEs supporting 5G Core and emergency services in NR connected to 5GCN | +| 11.4.15 | 5GMM-REGISTERED.NORMAL-SERVICE / 5GMM-IDLE / Emergency call / SNPN | Rel-17 | C306 | UEs supporting 5G Core and emergency services in NR connected to 5GCN in SNPN Access mode | +| 11.5 | eCall over IMS | | | | +| 11.5.1 | eCall Only mode / T3444 / eCall inactivity procedure / Removal of eCall only restriction after an eCall over IMS / 5GS to EPS | Rel-16 | C170 | UEs supporting 5G Core and E-UTRA and IMS eCall Only type of emergency services over 5GS and Manual type of eCall initiation | +| 11.5.2 | eCall Only mode / T3445 / eCall inactivity procedure / Removal of eCall only restriction after a call to URI for test service / 5GS to EPS | Rel-16 | C171 | UEs supporting 5G Core and E-UTRA and IMS eCall Only type of emergency services over 5GS and Manual type of eCall initiation and capable of triggering a Test eCall | +| 11.5.3 | eCall Only mode / 5GS supports IMS voice over PS session / 5GS does not support emergency service / eCall over EPS / eCall failure if EPS and CS domain are not available | Rel-16 | C197 | UEs supporting 5G Core and E-UTRA and IMS eCall Only type of emergency services over 5GS and Automatic type of eCall initiation | +| 11.5.4 | eCall Only mode / 5GS supports IMS voice over PS session / 5GS supports emergency service / eCall over IMS is supported on 5GS / RACH failure in NR cell / eCall over EPS | Rel-16 | C197 | UEs supporting 5G Core and E-UTRA and IMS eCall Only type of emergency services over 5GS and Automatic type of eCall initiation | +| 11.5.5 | eCall Only mode / Limited service state / Call to URI for test service should not be attempted / eCall over IMS should be attempted / 5GS | Rel-16 | C174 | UEs supporting 5G Core and IMS eCall Only type of emergency services over 5GS and Manual type of eCall initiation and capable of triggering a Test eCall | +| 11.5.6 | eCall capable / 5GS supports IMS voice over PS session / 5GS supports emergency service / eCall over IMS is not supported / eCall using the CS domain / emergency call over IMS if eCall using the CS domain is not available / UTRA | Rel-16 | C185 | UEs supporting 5G Core and UTRA and IMS eCall type of emergency services over 5GS and Automatic type of eCall initiation and emergency services in NR connected to 5GCN | +| 11.5.7 | eCall Only mode / SRVCC Handover to CS domain / UTRAN / MSD Update / Success / 5GS | Rel-16 | C186 | UEs supporting 5G Core and UTRA and IMS eCall Only type of emergency services over 5GS and Manual type of eCall initiation and NR to UTRA-FDD CELL_DCH CS handover | +| 11.5.8 | eCall Only mode / 5GS supports IMS voice over PS session / 5GS supports emergency | Rel-16 | C188 | UEs supporting 5G Core and (UTRA OR GERAN) and IMS eCall Only type of emergency | + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 11 | Multi-layer and Services | | | | +| | service / eCall over IMS is supported / RACH failure in NR cell / eCall using the CS domain | | | services over 5GS and Automatic type of eCall initiation | +| 11.5.9 | eCall only mode / Manual initiation / Emergency registration / Abnormal case / IM CN sends a 486 (Busy Here) / UE performs eCall in CS domain / UTRAN or GERAN / 5GS | Rel-16 | C187 | UEs supporting 5G Core and (UTRA OR GERAN) and IMS eCall Only type of emergency services over 5GS and Manual type of eCall initiation | +| 11.5.10 | eCall only mode / Automatic initiation / Emergency registration / Abnormal case / IM CN sends a 600 (Busy Everywhere) / UE performs eCall in CS domain / UTRAN or GERAN / 5GS | Rel-16 | C188 | UEs supporting 5G Core and (UTRA OR GERAN) and IMS eCall Only type of emergency services over 5GS and Automatic type of eCall initiation | +| 11.5.11 | eCall only mode / Automatic initiation / Emergency registration / Abnormal case / IM CN sends a 603 (Decline) / UE performs eCall in CS domain / UTRAN or GERAN / 5GS | Rel-16 | C188 | UEs supporting 5G Core and (UTRA OR GERAN) and IMS eCall Only type of emergency services over 5GS and Automatic type of eCall initiation | +| 11.5.12 | eCall Only mode / 5GS supports IMS voice over PS session / 5GS supports emergency service / eCall over IMS is not supported on 5GS / eCall over EPS | Rel-16 | C197 | UEs supporting 5G Core and E-UTRA and IMS eCall Only type of emergency services over 5GS and Automatic type of eCall initiation | +| 11.5.13 | eCall over IMS / Manual initiation / MSD transfer Failure / UE performs eCall in CS domain after Timer expiry / UTRAN or GERAN / 5GS | Rel-16 | C189 | UEs supporting 5G Core and (UTRA OR GERAN) and eCall type of emergency services over 5GS and Manual type of eCall initiation | +| 11.5.14 | eCall Only mode / 5GS supports IMS voice over PS session / 5GS does not support emergency service / eCall using CS domain | Rel-16 | C188 | UEs supporting 5G Core and (UTRA OR GERAN) and IMS eCall Only type of emergency services over 5GS and Automatic type of eCall initiation | +| 11.6 | 3GPP PS Data Off | | | | +| 11.6.1 | Data Off / MO Voice Call | Rel-15 | C162 | UEs supporting 5G Core and NG.114 and 3GPP PS data off | +| 11.6.2 | Data Off / MO Video Call | Rel-15 | C172 | UEs supporting 5G Core and NG.114 and 3GPP PS data off and MTSI video | +| 11.6.3 | Data Off / SMSoIP | Rel-15 | C162A | UEs supporting 5G Core and NG.114 and 3GPP PS data off and SMS over IP | +| 11.7 | eDRX | | | | +| 11.7.1 | eDRX / IDLE | Rel-17 | C210 | UEs supporting 5G Core and eDRX in RRC_IDLE | +| 11.7.2 | eDRX / Inactive / RAN-initiated paging | Rel-17 | C210A | UEs supporting 5G Core and eDRX in RRC_IDLE and RRC_INACTIVE and eDRX in RRC_INACTIVE with values of 256, 512 and 1024 radio frames | +| 11.7.3 | eDRX / Inactive / CN-initiated paging / eDRX Allowed / Not Allowed | Rel-17 | C210A | UEs supporting 5G Core and eDRX in RRC_IDLE and RRC_INACTIVE and eDRX in RRC_INACTIVE with values of 256, 512 and 1024 radio frames. | +| 11.7.4 | eDRX / Inactive / CN-initiated paging / RAN-initiated paging | Rel-18 | C382 | UEs supporting 5G Core and eDRX in RRC_IDLE and eDRX in RRC_INACTIVE with values above 1024 radio frames and RRC_INACTIVE | +| 11.7.5 | eDRX / Inactive / RAN-initiated paging / Correct using ran-ExtendedPagingCycleConfig-r18 and ran-ExtendedPagingCycle-r17 | Rel-18 | C383 | UEs supporting 5G Core and eDRX in RRC_IDLE and eDRX in RRC_INACTIVE with values above 1024 radio frames and eDRX in RRC_INACTIVE with values of 256, 512 and 1024 radio frames and RRC_INACTIVE | +| 11.8 | Inter-system mobility between untrusted Non-3GPP and 3GPP system | | | | +| 11.8.1 | Inter-system mobility between untrusted Non-3GPP and 3GPP system/Handover from NR to N3IWF/5GC | Rel-15 | C276 | UEs supporting 5G Core and handover from 5G Core Network to 5G Core over non-3GPP Access Network and WLAN | +| 11.8.2 | Inter-system mobility between untrusted Non-3GPP and 3GPP system/Handover from N3IWF/5GC to NR / UE in 5GMM-DEREGISTERED states | Rel-15 | C248 | UEs supporting 5G Core and handover from 5G Core over non-3GPP Access Network to 5G Core Network and WLAN | +| 11.8.3 | Inter-system mobility between untrusted Non-3GPP and 3GPP system/Handover from E-UTRAN/EPC to N3IWF/5GC | Rel-15 | C277 | UEs supporting 5G Core and handover from EPC Network to 5G Core over non-3GPP Access Network and WLAN | +| 11.8.4 | Inter-system mobility between untrusted Non-3GPP and 3GPP system/Handover from N3IWF/5GC to E-UTRAN/EPC | Rel-15 | C249 | UEs supporting 5G Core and handover from 5G Core over non-3GPP Access Network to EPC Network and WLAN | +| 11.8.5 | Inter-system mobility between untrusted Non-3GPP and 3GPP system/Handover from 5GS to EPC/ePDG | Rel-15 | C208 | UEs supporting 5G Core and IMS and handover from 5G Core to EPC over non-3GPP Access Network and GSMA PRD IR.51: "IMS Profile for Voice, Video and SMS over Wi-Fi" and WLAN. | + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 11 | Multi-layer and Services | | | | +| 11.8.6 | Inter-system mobility between untrusted Non-3GPP and 3GPP system/Handover from EPC/ePDG to 5GS/ UE in 5GMM-DEREGISTERED and EMM-DEREGISTERED states | Rel-15 | C237 | UEs supporting WLAN and GSMA PRD IR.51: "IMS Profile for Voice, Video and SMS over Wi-Fi" and handover from EPC over non-3GPP Access Network to 5G Core and IMS and 5G Core. | +| 11.9 | Inter-system mobility with established MA PDU session in 5GS | | | | +| 11.9.1 | Inter-system mobility with established MA PDU session in 5GS/ATSSS/Single-registration mode with N26/establishing a PDN connection as the user plane resource of an MA PDU session is supported/Handover from NR/5GC to E-UTRAN/EPC | Rel-17 | C319 | UEs supporting 5G Core and E-UTRA and 5G core over non-3GPP Access Network and WLAN and R17 ATSSS of establishing a PDN connection as the user plane resource of an MA PDU session in 5GS | +| 11.9.2 | Inter-system mobility with established MA PDU session in 5GS/ATSSS/Single-registration mode with N26/establishing a PDN connection as the user plane resource of an MA PDU session is not supported/Handover from NR/5GC to E-UTRAN/EPC/ | Rel-17 | C320 | UEs supporting 5G Core and E-UTRA and 5G core over non-3GPP Access Network and WLAN and R16 ATSSS | +| 11.9.3 | Inter-system mobility with established MA PDU session in 5GS/ATSSS/Single-registration mode without N26/establishing a PDN connection as the user plane resource of an MA PDU session is supported/Handover from NR/5GC to E-UTRAN/EPC | Rel-17 | C319 | UEs supporting 5G Core and E-UTRA and 5G core over non-3GPP Access Network and WLAN and R17 ATSSS of establishing a PDN connection as the user plane resource of an MA PDU session in 5GS | +| 11.9.4 | Inter-system mobility with established MA PDU session in 5GS/ATSSS/Single-registration mode without N26/establishing a PDN connection as the user plane resource of an MA PDU session is not supported/Handover from NR/5GC to E-UTRAN/EPC/ | Rel-17 | C320 | UEs supporting 5G Core and E-UTRA and 5G core over non-3GPP Access Network and WLAN and R16 ATSSS | + +**Table 4.1-5b: Additional Information of Applicability of Protocol conformance Multi-layer test cases, ref. TS 38.523-1 [2]** + +| Clause | Specific ICS | Specific Ixit | Number of TC Executions | Release other RAT | +|-------------|------------------|----------------------|-------------------------|-------------------| +| 11 | | | | | +| 11.1 | | | | | +| 11.1.1 | | | | Rel-15 E-UTRA | +| 11.1.2 | | | | Rel-15 E-UTRA | +| 11.1.3 | | | | Rel-15 E-UTRA | +| 11.1.4 | | | | Rel-15 E-UTRA | +| 11.1.5 | | | | Rel-15 E-UTRA | +| 11.1.6 | | | | Rel-15 E-UTRA | +| 11.1.7 | | | | Rel-15 E-UTRA | +| 11.1.8 | | | | Rel-16 E-UTRA | +| 11.1.9 | | | | Rel-16 E-UTRA | +| 11.2 | | | | | +| 11.2.1 | | | | Rel-16 UTRA | +| 11.3 | | | | | +| 11.3.1 | pc_inactiveState | | | | +| 11.3.6 | pc_inactiveState | | | | +| 11.3.6a | pc_inactiveState | | | | +| 11.4 | | | | | +| 11.4.10a | | | | Rel-15 E-UTRA | +| 11.4.11 | | | | Rel-15 E-UTRA | +| 11.5 | | | | | +| 11.5.1 | | | Note 1 | Rel-15 E-UTRA | +| 11.5.2 | | | Note 1 | Rel-15 E-UTRA | +| 11.5.3 | | | Note 1 | Rel-15 E-UTRA | +| 11.5.4 | | | Note 1 | Rel-15 E-UTRA | +| 11.5.5 | | | Note 1 | | +| 11.5.6 | | | Note 1 | | +| 11.5.7 | | | | Rel-16 UTRA | +| 11.5.8 | | px_NR_RATComb_Tested | Note 1 | Rel-9 UTRA | +| 11.5.9 | | px_NR_RATComb_Tested | Note 1 | Rel-9 UTRA | +| 11.5.10 | | px_NR_RATComb_Tested | Note 1 | Rel-9 UTRA | +| 11.5.11 | | px_NR_RATComb_Tested | Note 1 | Rel-9 UTRA | + +| | | | | | +|----------------------------------------------------------------------------|--|----------------------|--------|---------------| +| 11.5.12 | | | Note 1 | Rel-15 E-UTRA | +| 11.5.13 | | px NR RATComb Tested | Note 1 | Rel-9 UTRA | +| 11.5.14 | | px NR RATComb Tested | Note 1 | Rel-9 UTRA | +| Note 1: This test case can optionally be executed from Release 15 onwards. | | | | | + +Table 4.1-6a: Applicability of Protocol conformance NR sidelink test cases, ref. TS 38.523-1 [2] + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|-----------------|------------------------------------------------------------------------------------------------------------------------------------|---------|-------------------------|---------------------------------------------------------------| +| 12 | NR sidelink | | | | +| 12.1 | PC5-only operation | | | | +| 12.1.1 | PC5-only operation / Sidelink communication | | | | +| 12.1.1.1 | PC5-only operation / Sidelink communication / Transmission | Rel-16 | C128 | UE supporting 5G core and NR sidelink | +| 12.1.1.2 | PC5-only operation / Sidelink communication / Reception | Rel-16 | C128 | UE supporting 5G core and NR sidelink | +| 12.1.2 | PC5-only operation / Sidelink synchronization related procedure | | | | +| 12.1.2.1 | PC5-only operation / Sidelink synchronization related procedure / Synchronization reference source (re-)selection | Rel-16 | C128 | UE supporting 5G core and NR sidelink | +| 12.1.2.2 | PC5-only operation / Sidelink synchronization related procedure / SL-SSB transmission Initiation and Cease | Rel-16 | C128 | UE supporting 5G core and NR sidelink | +| 12.1.3 | PC5-only operation / Measurement configuration and reporting via PC5 RRC | | | | +| 12.1.3.1 | PC5-only operation / Measurement configuration and reporting via PC5 RRC / PSBCH-RSRP measurement configuration | Rel-16 | C128 | UE supporting 5G core and NR sidelink | +| 12.1.3.2 | PC5-only operation / Measurement configuration and reporting via PC5 RRC / PSBCH-RSRP measurement reporting / Event S1 and S2 | Rel-16 | C128 | UE supporting 5G core and NR sidelink | +| 12.1.3.3 | PC5-only operation / Measurement configuration and reporting via PC5 RRC / PSBCH-RSRP measurement reporting / Periodical reporting | Rel-16 | C128 | UE supporting 5G core and NR sidelink | +| 12.1.4 | PC5-only operation / Sidelink Reconfiguration via PC5 RRC | | | | +| 12.1.4.1 | PC5-only operation / Sidelink Reconfiguration via PC5 RRC / SL DRB management / initiating UE side | Rel-16 | C128 | UE supporting 5G core and NR sidelink | +| 12.1.4.2 | PC5-only operation / Sidelink Reconfiguration via PC5 RRC / SL DRB management / Peer UE side | Rel-16 | C128 | UE supporting 5G core and NR sidelink | +| 12.1.5 | PC5-only operation / Sidelink CSI reporting | | | | +| 12.1.5.1 | PC5-only operation / Sidelink CSI reporting / Configuration | Rel-16 | C163 | UE supporting 5G core and NR sidelink and Sidelink CSI report | +| 12.1.5.2 | PC5-only operation / Sidelink CSI reporting / Reporting | Rel-16 | C163 | UE supporting 5G core and NR sidelink and Sidelink CSI report | +| 12.1.6 | PC5-only operation / Sidelink failure | | | | +| 12.1.6.1 | PC5-only operation / Sidelink failure / PC5 RRC reconfiguration failure / Initiating UE side | Rel-16 | C128 | UE supporting 5G core and NR sidelink | +| 12.1.6.2 | PC5-only operation / Sidelink failure / PC5 RRC reconfiguration failure / Peer UE side | Rel-16 | C128 | UE supporting 5G core and NR sidelink | +| 12.1.6.3 | PC5-only operation / Sidelink failure / Sidelink radio link failure / Transmission side | Rel-16 | C128 | UE supporting 5G core and NR sidelink | +| 12.1.6.4 | PC5-only operation / Sidelink failure / Sidelink radio link failure / Reception side | Rel-16 | C128 | UE supporting 5G core and NR sidelink | +| 12.1.7 | PC5-only operation / Sidelink UE capability transfer via PC5 RRC | | | | +| 12.1.7.1 | PC5-only operation / Sidelink UE capability transfer via PC5 RRC / One-way and two-way transfer | Rel-16 | C128 | UE supporting 5G core and NR sidelink | +| 12.1.8 | PC5-only operation / MAC | | | | +| 12.1.8.1 | PC5-only operation / MAC / SL-SCH data transmission | | | | +| 12.1.8.1.1 | PC5-only operation / MAC / SL-SCH data transmission / Selected sidelink grant | Rel-16 | C128 | UE supporting 5G core and NR sidelink | +| 12.1.8.2 | PC5-only operation / MAC / SL-SCH data reception | | | | +| 12.1.8.2.1 | PC5-only operation / MAC / SL-SCH data | Rel-16 | C128 | UE supporting 5G core and NR sidelink | + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|------------------|--------------------------------------------------------------------------------------------------------------------------------------------|---------|-------------------------|-----------------------------------------------------------| +| 12 | NR sidelink | | | | +| | reception / ACK-NACK HARQ | | | | +| 12.1.8.2.2 | PC5-only operation / MAC / SL-SCH data reception / NACK-only HARQ | Rel-16 | C128 | UE supporting 5G core and NR sidelink | +| 12.1.8.2.3 | PC5-only operation / MAC / SL-SCH data reception / SL-SCH Transport block size selection | Rel-16 | C128 | UE supporting 5G core and NR sidelink | +| 12.1.8.2.4 | PC5-only operation / MAC / SL-SCH data reception / SL-SCH Transport block size selection for SL MIMO | Rel-16 | C390 | UE supporting 5G core and NR sidelink and SL-MIMO | +| 12.1.10 | PC5-only operation / PDCP | | | | +| 12.1.10.1 | PC5-only operation / PDCP / data transfer | | | | +| 12.1.10.1.1 | PC5-only operation / PDCP / data transfer / PDCP SN numbering / 12 bits SN | Rel-16 | C128 | UE supporting 5G core and NR sidelink | +| 12.1.10.1.2 | PC5-only operation / PDCP / data transfer / PDCP SN numbering / 18 bits SN | Rel-16 | C128 | UE supporting 5G core and NR sidelink | +| 12.1.10.1.3 | PC5-only operation / PDCP / data transfer / reordering | Rel-16 | C128 | UE supporting 5G core and NR sidelink | +| 12.1.11 | PC5-only operation / SDAP | | | | +| 12.1.11.1 | PC5-only operation / SDAP / data transfer | | | | +| 12.1.11.1.1 | PC5-only operation / SDAP / data transfer / QoS flow to SL DRB mapping / transmission side | Rel-16 | C128 | UE supporting 5G core and NR sidelink | +| 12.1.11.1.2 | PC5-only operation / SDAP / data transfer / reception side | Rel-16 | C128 | UE supporting 5G core and NR sidelink | +| 12.2 | Inter-carrier concurrent operation | | | | +| 12.2.1 | Inter-carrier concurrent operation / Sidelink communication | | | | +| 12.2.1.1 | Inter-carrier concurrent operation / Sidelink communication / RRC_IDLE / Transmission | Rel-16 | C106 | UE supporting 5G core and NR sidelink mode 1 transmission | +| 12.2.1.2 | Inter-carrier concurrent operation / Sidelink communication / RRC_IDLE / Reception | Rel-16 | C106 | UE supporting 5G core and NR sidelink mode 1 transmission | +| 12.2.1.3 | Inter-carrier concurrent operation / Sidelink communication / RRC_CONNECTED / Transmission / Network scheduling | Rel-16 | C106 | UE supporting 5G core and NR sidelink mode 1 transmission | +| 12.2.1.4 | Inter-carrier concurrent operation / Sidelink communication / RRC_CONNECTED / Transmission / Resource sensing | Rel-16 | C106 | UE supporting 5G core and NR sidelink mode 1 transmission | +| 12.2.1.5 | Inter-carrier concurrent operation / Sidelink communication / RRC_CONNECTED / Transmission / Exceptional pool | Rel-16 | C106 | UE supporting 5G core and NR sidelink mode 1 transmission | +| 12.2.1.6 | Inter-carrier concurrent operation / Sidelink communication / RRC_CONNECTED / Reception | Rel-16 | C106 | UE supporting 5G core and NR sidelink mode 1 transmission | +| 12.2.2 | Inter-carrier concurrent operation / Sidelink synchronization related procedure | | | | +| 12.2.2.1 | Inter-carrier concurrent operation / Sidelink synchronization related procedure / Synchronization reference source (re-)selection | Rel-16 | C106 | UE supporting 5G core and NR sidelink mode 1 transmission | +| 12.2.2.2 | Inter-carrier concurrent operation / Sidelink synchronization related procedure / SL-SSB transmission Initiation and Cease | Rel-16 | C106 | UE supporting 5G core and NR sidelink mode 1 transmission | +| 12.2.3 | Inter-carrier concurrent operation / Measurement configuration and reporting via Uu RRC | | | | +| 12.2.3.1 | Inter-carrier concurrent operation / Measurement configuration and reporting via Uu RRC / CBR measurement reporting / Event C1 and C2 | Rel-16 | C106 | UE supporting 5G core and NR sidelink mode 1 transmission | +| 12.2.3.2 | Inter-carrier concurrent operation / Measurement configuration and reporting via Uu RRC / CBR measurement reporting / Periodical reporting | Rel-16 | C106 | UE supporting 5G core and NR sidelink mode 1 transmission | +| 12.2.4 | Inter-carrier concurrent operation / Sidelink Reconfiguration via Uu RRC | | | | +| 12.2.4.1 | Inter-carrier concurrent operation / Sidelink Reconfiguration via Uu RRC / SL DRB management / transmission side | Rel-16 | C106 | UE supporting 5G core and NR sidelink mode 1 transmission | +| 12.2.5 | Inter-carrier concurrent operation / Measurement configuration and reporting via PC5 RRC | | | | +| 12.2.5.1 | Inter-carrier concurrent operation / Measurement configuration and reporting via | Rel-16 | C106 | UE supporting 5G core and NR sidelink mode 1 transmission | + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|---------|-------------------------|-----------------------------------------------------------------------------------| +| 12 | NR sidelink | | | | +| | PC5 RRC / SL-RSRP measurement configuration | | | | +| 12.2.5.2 | Inter-carrier concurrent operation / Measurement configuration and reporting via PC5 RRC / SL-RSRP measurement reporting / Event S1 and S2 | Rel-16 | C106 | UE supporting 5G core and NR sidelink mode 1 transmission | +| 12.2.5.3 | Inter-carrier concurrent operation / Measurement configuration and reporting via PC5 RRC / PSBCH-RSRP measurement reporting / Periodical reporting | Rel-16 | C106 | UE supporting 5G core and NR sidelink mode 1 transmission | +| 12.2.6 | Inter-carrier concurrent operation / Sidelink Reconfiguration via PC5 RRC | | | | +| 12.2.6.1 | Inter-carrier concurrent operation / Sidelink Reconfiguration via PC5 RRC / SL DRB management / Initiating UE side | Rel-16 | C106 | UE supporting 5G core and NR sidelink mode 1 transmission | +| 12.2.6.2 | Inter-carrier concurrent operation / Sidelink Reconfiguration via PC5 RRC / SL DRB management / Peer UE side | Rel-16 | C106 | UE supporting 5G core and NR sidelink mode 1 transmission | +| 12.2.7 | Inter-carrier concurrent operation / Sidelink CSI reporting | | | | +| 12.2.7.1 | Inter-carrier concurrent operation / Sidelink CSI reporting / Configuration | Rel-16 | C164 | UE supporting 5G core and NR sidelink mode 1 transmission and Sidelink CSI report | +| 12.2.7.2 | Inter-carrier concurrent operation / Measurement configuration and reporting via PC5 RRC / SL-RSRP measurement reporting / Event S1 and S2 | Rel-16 | C164 | UE supporting 5G core and NR sidelink mode 1 transmission and Sidelink CSI report | +| 12.2.8 | Inter-carrier concurrent operation / Sidelink failure | | | | +| 12.2.8.1 | Inter-carrier concurrent operation / Sidelink CSI reporting / Reporting | Rel-16 | C106 | UE supporting 5G core and NR sidelink mode 1 transmission | +| 12.2.8.2 | Inter-carrier concurrent operation / Sidelink failure / PC5 RRC Reconfiguration Failure / Peer UE side | Rel-16 | C106 | UE supporting 5G core and NR sidelink mode 1 transmission | +| 12.2.8.3 | Inter-carrier concurrent operation / Sidelink failure / Sidelink radio link failure / transmission side | Rel-16 | C106 | UE supporting 5G core and NR sidelink mode 1 transmission | +| 12.2.9 | Inter-carrier concurrent operation / Sidelink UE capability transfer via PC5 RRC | | | | +| 12.2.9.1 | Inter-carrier concurrent operation / Sidelink UE capability transfer via PC5 RRC / One-way and two-way transfer | Rel-16 | C106 | UE supporting 5G core and NR sidelink mode 1 transmission | +| 12.2.10 | Inter-concurrent operation / MAC | | | | +| 12.2.10.1 | Inter-concurrent operation / MAC / SL-SCH data transmission | | | | +| 12.2.10.1.1 | Inter-concurrent operation / MAC / SL-SCH data transmission / Dynamic sidelink grant | Rel-16 | C106 | UE supporting 5G core and NR sidelink mode 1 transmission | +| 12.2.10.1.2 | Inter-concurrent operation / MAC / SL-SCH data transmission / Configured sidelink grant | Rel-16 | C106 | UE supporting 5G core and NR sidelink mode 1 transmission | +| 12.2.10.1.3 | Inter-concurrent operation / MAC / SL-SCH data transmission / Selected sidelink grant | Rel-16 | C106 | UE supporting 5G core and NR sidelink mode 1 transmission | +| 12.2.10.2 | Inter-concurrent operation / MAC / SL-SCH data reception | | | | +| 12.2.10.2.1 | Inter-concurrent operation / MAC / SL-SCH data reception / ACK-NACK HARQ | Rel-16 | C106 | UE supporting 5G core and NR sidelink mode 1 transmission | +| 12.2.10.2.2 | Inter-concurrent operation / MAC / SL-SCH data reception / NACK-only HARQ | Rel-16 | C106 | UE supporting 5G core and NR sidelink mode 1 transmission | +| 12.2.10.2.3 | Inter-concurrent operation / MAC / SL-SCH data reception / SL-SCH Transport block size selection | Rel-16 | C106 | UE supporting 5G core and NR sidelink mode 1 transmission | +| 12.2.10.2.4 | Inter-concurrent operation / MAC / SL-SCH data reception / SL-SCH Transport block size selection for SL MIMO | Rel-16 | C391 | UE supporting 5G core and NR sidelink mode 1 transmission and SL-MIMO | +| 12.2.10.3 | Inter-concurrent operation / MAC / Uu procedures related to sidelink | | | | +| 12.2.10.3.1 | Inter-concurrent operation / MAC / Uu procedures related to sidelink / Sidelink buffer status reporting and scheduling request | Rel-16 | C106 | UE supporting 5G core and NR sidelink mode 1 transmission | +| 12.3 | Sidelink Relay | | | | +| 12.3.1 | L2 UE-to-Network Relay | | | | +| 12.3.1.1 | Remote UE | | | | +| 12.3.1.1.1 | Sidelink Relay / L2 U2N / Remote UE / Sidelink Synchronization / Synchronization Reference | Rel-17 | C342 | UE supporting 5G core and NR L2 sidelink remote UE operation | + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|-----------------|--------------------------------------------------------------------------------------------------------------------|---------|-------------------------|------------------------------------------------------------------------------| +| 12 | NR sidelink | | | | +| | Source (Re-) Selection | | | | +| 12.3.1.1.2 | Sidelink Relay / L2 U2N / Remote UE / 5G ProSe Direct Discovery / Monitoring | Rel-17 | C342 | UE supporting 5G core and NR L2 sidelink remote UE operation | +| 12.3.1.1.3 | Sidelink Relay / L2 U2N / Remote UE / 5G ProSe Direct Discovery / Discoverer | Rel-17 | C342 | UE supporting 5G core and NR L2 sidelink remote UE operation | +| 12.3.1.1.4 | Sidelink Relay / L2 U2N / Remote UE / 5G ProSe Direct Discovery / Direct Discovery Update | Rel-17 | C342 | UE supporting 5G core and NR L2 sidelink remote UE operation | +| 12.3.1.1.7 | Sidelink Relay / L2 U2N / Remote UE / Direct link establishment, reject and release | Rel-17 | C342 | UE supporting 5G core and NR L2 sidelink remote UE operation | +| 12.3.1.1.8 | Sidelink Relay / L2 U2N / Remote UE / Paging | Rel-17 | C342 | UE supporting 5G core and NR L2 sidelink remote UE operation | +| 12.3.1.1.9 | Sidelink Relay / L2 U2N / Remote UE / RRC reconfiguration / L2 U2N Remote UE configuration | Rel-17 | C342 | UE supporting 5G core and NR L2 sidelink remote UE operation | +| 12.3.1.1.11 | Sidelink Relay / L2 U2N / Remote UE / Radio link failure related actions | Rel-17 | C342 | UE supporting 5G core and NR L2 sidelink remote UE operation | +| 12.3.1.1.12 | Sidelink Relay / L2 U2N / Remote UE / Measurement configuration control and reporting / Event X1 | Rel-17 | C342 | UE supporting 5G core and NR L2 sidelink remote UE operation | +| 12.3.1.1.13 | Sidelink Relay / L2 U2N / Remote UE / Measurement configuration control and reporting / Event X2 | Rel-17 | C342 | UE supporting 5G core and NR L2 sidelink remote UE operation | +| 12.3.1.1.14 | Sidelink Relay / L2 U2N / Remote UE / Measurement configuration control and reporting / Event Y1 | Rel-17 | C342 | UE supporting 5G core and NR L2 sidelink remote UE operation | +| 12.3.1.1.15 | Sidelink Relay / L2 U2N / Remote UE / Measurement configuration control and reporting / Event Y2 | Rel-17 | C342 | UE supporting 5G core and NR L2 sidelink remote UE operation | +| 12.3.1.1.16 | Sidelink Relay / L2 U2N / Remote UE / Measurement configuration control and reporting / Periodical reporting | Rel-17 | C342 | UE supporting 5G core and NR L2 sidelink remote UE operation | +| 12.3.1.1.17 | Sidelink Relay / L2 U2N / Remote UE / RRC reconfiguration / PC5 Relay RLC channel configuration | Rel-17 | C342 | UE supporting 5G core and NR L2 sidelink remote UE operation | +| 12.3.1.1.18 | Sidelink Relay / L2 U2N / Remote UE / Sidelink radio link failure related actions | Rel-17 | C342 | UE supporting 5G core and NR L2 sidelink remote UE operation | +| 12.3.1.1.19 | Sidelink Relay / L2 U2N / Remote UE / Selection of NR Sidelink U2N Relay UE | Rel-17 | C342 | UE supporting 5G core and NR L2 sidelink remote UE operation | +| 12.3.1.1.20 | Sidelink Relay / L2 U2N / Remote UE / Reselection of NR Sidelink U2N Relay UE | Rel-17 | C342 | UE supporting 5G core and NR L2 sidelink remote UE operation | +| 12.3.1.2 | Relay UE | | | | +| 12.3.1.2.1 | Sidelink Relay / L2 U2N / Relay UE / Sidelink Synchronization / SLSS Transmission | Rel-17 | C343 | UE supporting 5G core and NR L2 sidelink relay UE operation | +| 12.3.1.2.2 | Sidelink Relay / L2 U2N / Relay UE / 5G ProSe U2N Relay Discovery / Announcing | Rel-17 | C343 | UE supporting 5G core and NR L2 sidelink relay UE operation | +| 12.3.1.2.3 | Sidelink Relay / L2 U2N / Relay UE / 5G ProSe U2N Relay Discovery / Discoveree | Rel-17 | C343 | UE supporting 5G core and NR L2 sidelink relay UE operation | +| 12.3.1.2.4 | Sidelink Relay / L2 U2N / Relay UE / Direct link establishment, reject and release | Rel-17 | C343 | UE supporting 5G core and NR L2 sidelink relay UE operation | +| 12.3.1.2.6 | Sidelink Relay / L2 U2N / Relay UE / Paging transmission | Rel-17 | C343 | UE supporting 5G core and NR L2 sidelink relay UE operation | +| 12.3.1.2.7 | Sidelink Relay / L2 U2N / Relay UE / RRC connection establishment triggered by Remote UE | Rel-17 | C343 | UE supporting 5G core and NR L2 sidelink relay UE operation | +| 12.3.1.2.8 | Sidelink Relay / L2 U2N / Relay UE / RRC connection establishment triggered by Remote UE / Emergency | Rel-17 | C343 | UE supporting 5G core and NR L2 sidelink relay UE operation | +| 12.3.1.2.9 | Sidelink Relay / L2 U2N / Relay UE / RRC connection establishment triggered by Remote UE / Rejected / T300 expired | Rel-17 | C343 | UE supporting 5G core and NR L2 sidelink relay UE operation | +| 12.3.1.2.10 | Sidelink Relay / L2 U2N / Relay UE / RRC connection resume triggered by Remote UE | Rel-17 | C394 | UE supporting 5G core and NR L2 sidelink relay UE operation and RRC_INACTIVE | +| 12.3.1.2.11 | Sidelink Relay / L2 U2N / Relay UE / RRC reconfiguration / Uu Relay RLC channel configuration | Rel-17 | C343 | UE supporting 5G core and NR L2 sidelink relay UE operation | +| 12.3.1.2.12 | Sidelink Relay / L2 U2N / Relay UE / RRC reconfiguration / PC5 Relay RLC channel configuration | Rel-17 | C343 | UE supporting 5G core and NR L2 sidelink relay UE operation | +| 12.3.1.2.13 | Sidelink Relay / L2 U2N / Relay UE / RRC reconfiguration / L2 U2N Relay UE configuration | Rel-17 | C343 | UE supporting 5G core and NR L2 sidelink relay UE operation | + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|-------------|----------------------------------------------------------------------------------|---------|-------------------------|-------------------------------------------------------------| +| 12 | NR sidelink | | | | +| 12.3.1.2.14 | Sidelink Relay / L2 U2N / Relay UE / Radio link failure related actions | Rel-17 | C343 | UE supporting 5G core and NR L2 sidelink relay UE operation | +| 12.3.1.2.15 | Sidelink Relay / L2 U2N / Relay UE / Sidelink RRC reconfiguration | Rel-17 | C343 | UE supporting 5G core and NR L2 sidelink relay UE operation | +| 12.3.1.2.16 | Sidelink Relay / L2 U2N / Relay UE / Sidelink radio link failure related actions | Rel-17 | C343 | UE supporting 5G core and NR L2 sidelink relay UE operation | + +**Table 4.1-6b: Additional Information of Applicability of Protocol conformance NR sidelink test cases, ref. TS 38.523-1 [2]** + +| Clause | Specific ICS | Specific IEXIT | Number of TC Executions | Release other RAT | +|------------------|--------------|---------------------------------|-------------------------|-------------------| +| 12.1.10 | | | | | +| 12.1.10.1 | | | | | +| 12.1.10.1.3 | | px_NR_SidelinkPDCP_ReorderTimer | | | + +**Table 4.1-7a: Applicability of Protocol conformance NR V2X layer test cases, ref. TS 38.523-1 [2]** + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|-------------|-------------------------------------------------------------------------------------------|---------|-------------------------|-----------------------------------------------------------| +| 13 | V2X layer | | | | +| 13.1 | V2X policy provisioning | | | | +| 13.1.1 | V2X policy provisioning / Precedence / Validity timer expires / geographical area changes | Rel-16 | C166 | UE supporting 5G Core and V2X communication over NR-PC5 | +| 13.2 | PC5 unicast | | | | +| 13.2.1 | PC5 unicast / link establishment / Reject / Conflict Layer 2 ID | Rel-16 | C128 | UE supporting 5G core and NR sidelink | +| 13.2.2 | PC5 unicast / link Security Mode | Rel-16 | C128 | UE supporting 5G core and NR sidelink | +| 13.2.3 | PC5 unicast / link modification | Rel-16 | C128 | UE supporting 5G core and NR sidelink | +| 13.2.4 | PC5 unicast / link Release / Reestablish PC5 unicast link to same UE | Rel-16 | C128 | UE supporting 5G core and NR sidelink | +| 13.2.5 | PC5 unicast / link identifier update | Rel-16 | C128 | UE supporting 5G core and NR sidelink transmission mode 2 | +| 13.2.6 | PC5 unicast / link keep alive | Rel-16 | C128 | UE supporting 5G core and NR sidelink | + +**Table 4.1-7b: Additional Information of Applicability of Protocol conformance NR V2X layer test cases, ref. TS 38.523-1 [2]** + +| Clause | Specific ICS | Specific IEXIT | Number of TC Executions | Release other RAT | +|------------|--------------|----------------|-------------------------|-------------------| +| TBD | | | | | + +**Table 4.1-8a: Applicability of Protocol conformance NR MBS test cases, ref. TS 38.523-1 [2]** + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|-----------------|---------------------------------------------------------------------------------------------------------------------------|---------|-------------------------|-------------------------------------------------------------------------------------| +| 14 | MBS | | | | +| 14.1 | MBS Broadcast | | | | +| 14.1.1 | MBS Broadcast/ MCCH Information Acquisition | | | | +| 14.1.1.1 | MBS Broadcast/ MCCH Information Acquisition/ entering the cell providing SIB20 | Rel-17 | C213 | UE supporting 5G Core and broadcast reception. | +| 14.1.1.2 | MBS Broadcast/ MCCH Information Acquisition/ becoming interested to receive MBS broadcast services | Rel-17 | C213 | UE supporting 5G Core and broadcast reception. | +| 14.1.1.3 | MBS Broadcast/ MCCH Information Acquisition/ MCCH Information change notification | Rel-17 | C213 | UE supporting 5G Core and broadcast reception. | +| 14.1.1.4 | MBS Broadcast/ MCCH Information Acquisition/ receiving SIB20 of an SCell via dedicated signalling | | | | +| 14.1.1.4.1 | MBS Broadcast/ MCCH Information Acquisition/ receiving SIB20 of an SCell via dedicated signalling / Intra-band Contiguous | Rel-17 | C280 | UE supporting 5G Core and broadcast reception on SCell and Intra-band Contiguous CA | + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------|---------|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 14 | MBS | | | | +| | CA | | | | +| 14.1.1.4.2 | MBS Broadcast/ MCCH Information Acquisition/ receiving SIB20 of an SCell via dedicated signalling / Inter-band CA | Rel-17 | C281 | UE supporting 5G Core and broadcast reception on SCell and Inter-band CA | +| 14.1.1.4.3 | MBS Broadcast/ MCCH Information Acquisition/ receiving SIB20 of an SCell via dedicated signalling / Intra-band non Contiguous CA | Rel-17 | C282 | UE supporting 5G Core and broadcast reception on SCell and Intra-band non-Contiguous CA | +| 14.1.1.5 | MBS Broadcast/ MCCH Information Acquisition/ Multiple beams | Rel-17 | C213 | UE supporting 5G Core and broadcast reception. | +| 14.1.2 | MBS Broadcast/ Service Continuity | | | | +| 14.1.2.1 | MBS Broadcast/ Service Continuity/ Cell reselection/ frequency prioritization | Rel-17 | C213 | UE supporting 5G Core and broadcast reception. | +| 14.1.2.2 | MBS Broadcast/ Service Continuity/ Handover/ MBS Interest Indication/ inter-frequency | Rel-17 | C213 | UE supporting 5G Core and broadcast reception. | +| 14.1.2.3 | MBS Broadcast/ Service Continuity/ Handover/ MBS Interest Indication/ intra-frequency | Rel-17 | C213 | UE supporting 5G Core and broadcast reception. | +| 14.1.3 | MBS Broadcast/ MAC | | | | +| 14.1.3.1 | MBS Broadcast/ MAC/ Correct HARQ process handling | Rel-17 | C213 | UE supporting 5G Core and broadcast reception. | +| 14.1.3.2 | MBS Broadcast/ MAC/ DRX operation | Rel-17 | C213 | UE supporting 5G Core and broadcast reception. | +| 14.2 | MBS Multicast | | | | +| 14.2.1 | MBS Multicast/ MAC | | | | +| 14.2.1.1 | MBS Multicast/ MAC / DL Data Transfer | | | | +| 14.2.1.1.1 | MBS Multicast / MAC / DL Data Transfer / PTM transmission / PTP transmission / DCI format 4_1 | Rel-17 | C214 | UE supporting 5G Core and dynamic scheduling for multicast for PCell | +| 14.2.1.1.2 | MBS Multicast / MAC / DL Data Transfer/ PTM transmission/ DCI format 4_2 | Rel-17 | C283 | UE supporting 5G Core and dynamic scheduling for multicast for PCell and DCI formate 4_2 | +| 14.2.1.1.3 | MBS Multicast / MAC / DL Data Transfer/ PTM transmission / PTP transmission / Multiple G-RNTIs | Rel-17 | C295 | UE supporting 5G Core and dynamic scheduling for multicast for PCell and Multiple G-RNTIs. | +| 14.2.1.1.4 | MBS Multicast/ MAC / DL Data Transfer/ PTM retransmission for multicast/ RRC-based enabling-disabling HARQ feedback for Multicast / ACK-NACK | Rel-17 | C215 | UE supporting 5G Core and dynamic scheduling for multicast for PCell and ACK/NACK based HARQ-ACK feedback and RRC-based enabling/disabling ACK/NACK-based feedback for dynamic scheduling for multicast | +| 14.2.1.1.5 | MBS Multicast/ MAC / DL Data Transfer/ PTP retransmission for multicast/ RRC-based enabling-disabling HARQ feedback for Multicast/ ACK-NACK | Rel-17 | C216 | UE supporting 5G Core and dynamic scheduling for multicast for PCell and ACK/NACK based HARQ-ACK feedback and RRC-based enabling/disabling ACK/NACK-based feedback for dynamic scheduling for multicast and PTP retransmission for multicast on the same cell as multicast initial transmission | +| 14.2.1.1.6 | MBS Multicast/ MAC / DL Data Transfer/ PTM retransmission for multicast/ DCI-based enabling-disabling HARQ feedback for Multicast/ ACK-NACK | Rel-17 | C284 | UE supporting 5G Core and dynamic scheduling for multicast for PCell and DCI formate 4-2 and DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2 | +| 14.2.1.1.7 | MBS Multicast/ MAC / DL Data Transfer/ RRC-based enabling-disabling HARQ feedback for Multicast / NACK-only | Rel-17 | C252 | UE supporting 5G Core and dynamic scheduling for multicast for PCell and NACK-only based HARQ-ACK feedback for multicast with ACK/NACK transforming | +| 14.2.1.1.8 | MBS Multicast/ MAC / DL Data Transfer/ Multiplex multicast HARQ-ACK information with unicast HARQ-ACK information | Rel-17 | C253 | UE supporting 5G Core and dynamic scheduling for multicast for PCell and ACK/NACK based HARQ-ACK feedback and RRC-based enabling/disabling ACK/NACK-based feedback for dynamic scheduling for multicast and multiplexing HARQ-ACK for unicast and for multicast with the same priority and different HARQ-ACK codebook types in a PUCCH or in a PUSCH | +| 14.2.1.1.9 | MBS Multicast/ MAC / DL Data Transfer/ DCI-based enabling-disabling HARQ feedback for Multicast/ NACK-only | Rel-17 | C285 | UE supporting 5G Core and dynamic scheduling for multicast for PCell and DCI formate 4-2 and DCI-based enabling/disabling NACK-only based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2 | +| 14.2.1.2 | MBS Multicast/ MAC/ DRX operation | | | | +| 14.2.1.2.1 | MBS Multicast/ MAC/ DRX operation/ PTM transmission / PTP transmission | Rel-17 | C214 | UE supporting 5G Core and dynamic scheduling for multicast for PCell | +| 14.2.1.2.2 | MBS Multicast/ MAC/ DRX operation/ PTM retransmission for multicast | Rel-17 | C215 | UE supporting 5G Core and dynamic scheduling for multicast for PCell and ACK/NACK based | + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|-----------------|------------------------------------------------------------------------------------------------------------|---------|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 14 | MBS | | | | +| | | | | HARQ-ACK feedback and RRC-based enabling/disabling ACK/NACK-based feedback for dynamic scheduling for multicast | +| 14.2.1.2.3 | MBS Multicast/ MAC/ DRX operation/ PTP retransmission for multicast | Rel-17 | C216 | UE supporting 5G Core and dynamic scheduling for multicast for PCell and ACK/NACK based HARQ-ACK feedback and RRC-based enabling/disabling ACK/NACK-based feedback for dynamic scheduling for multicast and PTP retransmission for multicast on the same cell as multicast initial transmission | +| 14.2.1.3 | MBS Multicast/ MAC/ SPS | | | | +| 14.2.1.3.1 | MBS Multicast/ MAC/ SPS/ PTM transmission | Rel-17 | C296 | UE supporting 5G Core and dynamic scheduling for multicast for PCell and SPS group common PDSCH for multicast on PCell. | +| 14.2.1.3.2 | MBS Multicast/ MAC/ SPS/ PTM retransmission for multicast | Rel-17 | C297 | UE supporting 5G Core and dynamic scheduling for multicast for PCell and SPS group-common PDSCH for multicast on PCell and ACK/NACK based HARQ-ACK feedback and RRC-based enabling/disabling ACK/NACK-based feedback for SPS group-common PDSCH for multicast. | +| 14.2.1.3.3 | MBS Multicast/ MAC/ SPS/ PTP retransmission for multicast | Rel-17 | C298 | UE supporting 5G Core and dynamic scheduling for multicast for PCell and SPS group-common PDSCH for multicast on PCell and ACK/NACK based HARQ-ACK feedback and RRC-based enabling/disabling ACK/NACK-based feedback for SPS group-common PDSCH for multicast and PTP retransmission associated with CS-RNTI for SPS multicast on the cell same as multicast initial transmission. | +| 14.2.1.3.4 | MBS Multicast/ MAC/ SPS/ CS-RNTI release | Rel-17 | C299 | UE supporting 5G Core and dynamic scheduling for multicast for PCell and SPS group-common PDSCH for multicast on PCell and unicast PDCCH scrambled with CS-RNTI to release SPS group-common PDSCH. | +| 14.2.2 | MBS Multicast/ RLC | | | | +| 14.2.2.1 | MBS Multicast/ UM RLC / 6bit SN /Correct set initial value for UM receive state variable/ PTM | Rel-17 | C214 | UE supporting 5G Core and dynamic scheduling for multicast for PCell | +| 14.2.2.2 | MBS Multicast/ UM RLC / 12bit SN /Correct set initial value for UM receive state variable/ PTM | Rel-17 | C214 | UE supporting 5G Core and dynamic scheduling for multicast for PCell | +| 14.2.3 | MBS Multicast / PDCP | | | | +| 14.2.3.1 | MBS Multicast / PDCP/ PDCP HFN and SN maintenance / Non-Lossless handover / 12 bit SN | Rel-17 | C214 | UE supporting 5G Core and dynamic scheduling for multicast for PCell | +| 14.2.3.2 | MBS Multicast / PDCP/ PDCP HFN and SN maintenance / Non-Lossless handover / 18 bit SN | Rel-17 | C214 | UE supporting 5G Core and dynamic scheduling for multicast for PCell | +| 14.2.3.3 | MBS Multicast / PDCP/ PDCP HFN and SN maintenance /Lossless handover/ PDCP status report / 12 bit SN | Rel-17 | C214 | UE supporting 5G Core and dynamic scheduling for multicast for PCell | +| 14.2.3.4 | MBS Multicast / PDCP/ PDCP HFN and SN maintenance /Lossless handover/ PDCP status report / 18 bit SN | Rel-17 | C214 | UE supporting 5G Core and dynamic scheduling for multicast for PCell | +| 14.2.4 | MBS Multicast / RRC | | | | +| 14.2.4.1 | MBS Multicast / RRC / Paging | | | | +| 14.2.4.1.1 | MBS Multicast / RRC / Paging for group notification / RRC IDLE | Rel-17 | C214 | UE supporting 5G Core and dynamic scheduling for multicast for PCell | +| 14.2.4.1.2 | MBS Multicast / RRC / Paging for group notification / RRC INACTIVE | Rel-17 | C254 | UE supporting 5G Core and dynamic scheduling for multicast for PCell and RRC INACTIVE | +| 14.2.4.2 | MBS Multicast / RRC / MRB Reconfiguration | | | | +| 14.2.4.2.1 | MBS Multicast / RRC / MRB Reconfiguration / Establishment / Modification / Release / Success | Rel-17 | C214 | UE supporting 5G Core and dynamic scheduling for multicast for PCell | +| 14.2.4.3 | MBS Multicast/ RRC/ Handover | | | | +| 14.2.4.3.1 | MBS Multicast/ RRC/ Handover between multicast supporting cell / Success | Rel-17 | C214 | UE supporting 5G Core and dynamic scheduling for multicast for PCell | +| 14.2.4.3.2 | MBS Multicast / RRC / Handover between multicast supporting cell / Failure/ Re-establishment successful | Rel-17 | C214 | UE supporting 5G Core and dynamic scheduling for multicast for PCell | +| 14.2.4.3.3 | MBS Multicast/ RRC/ Handover between Multicast-supporting cell and Multicast non-supporting cell / Success | Rel-17 | C214 | UE supporting 5G Core and dynamic scheduling for multicast for PCell | +| 14.2.5 | MBS Multicast/ Session management | | | | +| 14.2.5.1 | MBS Multicast/ Session management / | | | | + +| Clause | TC Title | Release | Applicability Condition | Applicability Comment | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-------------------------|----------------------------------------------------------------------| +| 14 | MBS | | | | +| | Network-requested PDU session modification | | | | +| 14.2.5.1.1 | MBS Multicast/ Session management / Network-requested PDU session modification / Remove UE from multicast MBS session | Rel-17 | C214 | UE supporting 5G Core and dynamic scheduling for multicast for PCell | +| 14.2.5.1.2 | MBS Multicast/ Session management / Network-requested PDU session modification / MBS service area update | Rel-17 | C214 | UE supporting 5G Core and dynamic scheduling for multicast for PCell | +| 14.2.5.2 | MBS Multicast/ Session management / UE-requested PDU session establishment / UE-requested PDU session modification | | | | +| 14.2.5.2.1 | MBS Multicast/ Session management / UE-requested PDU session establishment / UE-requested PDU session modification / Join MBS multicast session / Accepted | Rel-17 | C214 | UE supporting 5G Core and dynamic scheduling for multicast for PCell | +| 14.2.5.2.2 | MBS Multicast/ Session management / UE-requested PDU session establishment / UE-requested PDU session modification / Join MBS multicast session / Rejected / User is outside of local MBS service area | Rel-17 | C214 | UE supporting 5G Core and dynamic scheduling for multicast for PCell | +| 14.2.5.2.3 | MBS Multicast/ Session management / UE-requested PDU session establishment / UE-requested PDU session modification / Join MBS multicast session / Rejected / MBS session has not started or will not start soon | Rel-17 | C214 | UE supporting 5G Core and dynamic scheduling for multicast for PCell | +| 14.2.5.2.4 | MBS Multicast/ Session management / UE-requested PDU session modification / Leave MBS multicast session / Accepted | Rel-17 | C214 | UE supporting 5G Core and dynamic scheduling for multicast for PCell | + +**Table 4.1-8b: Additional Information of Applicability of Protocol conformance NR MBS test cases, ref. TS 38.523-1 [2]** + +| Clause | Specific ICS | Specific IXT | Number of TC Executions | Release other RAT | +|-----------------|--------------------------------------|--------------|-------------------------|-------------------| +| 14 | | | | | +| 14.1 | | | | | +| 14.1.1 | | | | | +| 14.1.1.1 | pc_inactiveState | | | | +| 14.1.2 | | | | | +| 14.1.2.1 | pc_inactiveState | | | | +| 14.1.3 | | | | | +| 14.1.3.2 | pc_inactiveState | | | | +| 14.2.1 | | | | | +| 14.2.1.1 | | | | | +| 14.2.1.1.7 | pc_mux_HARQ_ACK_UnicastMulticast_r17 | | | | + +## 4.2 Protocol conformance test cases applicability conditions + +**Table 4.2-1: Applicability of Protocol conformance test cases Conditions** + +| Condition | Test case Selection Expression | Comment | +|-----------|--------------------------------|---------| +|-----------|--------------------------------|---------| + +| Condition | Test case Selection Expression | Comment | +|-----------|------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| C01 | IF A.4.1-3/2 THEN R ELSE N/A | UEs supporting EN-DC | +| C02 | IF A.4.3.4-1/2 OR A.4.3.4-1/3 THEN R ELSE N/A | UEs supporting 5GS and RLC UM Mode | +| C03 | IF A.4.3.5-1/1 THEN R ELSE N/A | UEs supporting 5GS and Long DRX Cycle | +| C04 | IF A.4.3.5-1/2 THEN R ELSE N/A | UEs supporting 5GS and short DRX cycle | +| C05 | IF A.4.3.4-1/3 THEN R ELSE N/A | UEs supporting 5GS and RLC UM with 6-bit length of RLC sequence number | +| C06 | IF A.4.3.4-1/2 THEN R ELSE N/A | UEs supporting 5GS and RLC UM with 12-bit length of RLC sequence number | +| C07 | IF A.4.3.4-1/1 THEN R ELSE N/A | UEs supporting 5GS and RLC AM with 12-bit length of RLC sequence number | +| C07A | IF A.4.3.4-1/1A THEN R ELSE N/A | UEs supporting 5GS and RLC AM with 18-bit length of RLC sequence number | +| C08 | IF A.4.3.3-1/1 THEN R ELSE N/A | UEs supporting 5GS and 12-bit length of PDCP sequence number | +| C08A | IF A.4.3.3-1/1A THEN R ELSE N/A | UEs supporting 5GS and 18-bit length of PDCP sequence number | +| C09 | IF [10] A.4.4-1/99 THEN R ELSE N/A | UEs supporting 5GS and ZUC Algorithm | +| C10 | IF A.4.1-3/2 AND A.4.3.7-1/2 THEN R ELSE N/A | UEs supporting EN-DC and UL transmission via both MCG path and SCG path for the split DRB | +| C11 | IF A.4.3.2-1/2 OR A.4.3.2-1/3 THEN R ELSE N/A | UEs supporting 5GS and 256QAM for PDSCH for FR1/FR2 | +| C12 | Void | | +| C13 | IF A.4.1-3/2 AND A.4.3.6-1/1 THEN R ELSE N/A | UEs supporting EN-DC and NR measurements and Event A triggered reporting | +| C14 | IF A.4.1-3/2 AND A.4.3.6-1/1 AND A.4.3.6-1/3 THEN R ELSE N/A | UEs supporting EN-DC and NR measurements and Event A triggered reporting and (NR Intra-frequency and NR-Inter frequency measurements and at least periodical reporting) | +| C15 | IF A.4.1-3/2 AND A.4.3.6-1/1 AND A.4.3.6-1/3 AND (A.4.3.6-1/4 OR A.4.3.6-1/40) THEN R ELSE N/A | UEs supporting EN-DC and NR measurements and Event A triggered reporting and (NR Intra-frequency and Inter frequency measurements and at least periodical reporting) and CSI-RSRP and CSI-RSRQ measurement | +| C16 | IF A.4.1-3/2 AND [10] A.4.4-1/18 AND [10] A.4.4-1/19 THEN R ELSE N/A | UEs supporting EN-DC and UE requested bearer resource allocation and modification procedures | +| C17 | IF A.4.3.2-1/1 THEN R ELSE N/A | UEs supporting 5GS and PDSCH reception based on semi-persistent scheduling | +| C18 | IF A.4.3.2-1/10 THEN R ELSE N/A | UEs supporting 5GS and Type 1 PUSCH transmissions with configured grant | +| C19 | IF A.4.3.2-1/11 THEN R ELSE N/A | UEs supporting 5GS and Type 2 PUSCH transmissions with configured grant | +| C20 | IF A.4.3.2-1/12 THEN R ELSE N/A | UEs supporting 5GS and PDSCH aggregation | +| C21 | IF A.4.1-5/1 THEN R ELSE N/A | UEs supporting 5G Core | +| C21A | IF A.4.1-5/1 AND A.4.3.7-1/4 THEN R ELSE N/A | UEs supporting 5G Core and reflective QoS | +| C21B | IF A.4.1-5/1 AND A.4.3.7-1/63 THEN R ELSE N/A | UEs supporting 5G Core and steering of roaming connected mode control information | +| C22 | IF A.4.1-3/2 AND A.4.3.7-1/3 THEN R ELSE N/A | UEs supporting EN-DC and SRB3 | +| C23 | IF A.4.1-3/2 AND A.4.3.7-1/3 AND A.4.3.7-1/1 THEN R ELSE N/A | UEs supporting EN-DC and SRB3 and (UL transmission via either MCG path or SCG path for the split SRB) | +| C24 | IF A.4.1-3/2 AND A.4.3.6-1/3 AND A.4.3.6-1/2 AND A.4.1-4/3 THEN R ELSE N/A | UEs supporting EN-DC and (NR intra-frequency and inter-frequency measurements and at least periodical reporting) and (two independent measurement gap configurations for FR1 and FR2) and Inter-Band EN-DC within FR1 | +| C25 | IF A.4.1-3/2 AND A.4.3.6-1/3 AND A.4.3.6-1/2 AND A.4.1-4/4 THEN R ELSE N/A | UEs supporting EN-DC and (NR intra-frequency and inter-frequency measurements and at least periodical reporting) and (two independent measurement gap configurations for FR1 and FR2) and Inter-Band EN-DC including FR2 | +| C26 | IF [10] A.4.1-1/1 OR [10] A.4.1-1/2 THEN R ELSE N/A | UEs supporting 5GS and E-UTRA | +| C27 | Void | | +| C28 | IF A.4.1-5/1 AND A.4.1-2/3 AND A.4.3.2-1/13 THEN R ELSE N/A | UEs supporting 5GS and NR SUL and supplemental uplink with dynamic switch | +| C29 | IF A.4.1-5/2 AND [10] A.4.1-1/5 THEN R ELSE N/A | UEs supporting 5G core over non-3GPP Access Network and WLAN | +| C30 | IF A.4.1-5/2 AND A.4.3.7-1/6 AND [10] A.4.1-1/5 THEN R ELSE N/A | UEs supporting 5G core over non-3GPP Access Network and SMS over NAS and WLAN | +| C31 | IF A.4.1-5/1 AND A.4.3.6-1/5 THEN R ELSE N/A | UEs supporting 5G Core and Inter-RAT E-UTRA measurements and Event B triggered reporting | +| C32 | IF A.4.1-5/1 AND ([10] A.4.1-1/1 OR [10] A.4.1-1/2) THEN R ELSE N/A | UEs supporting 5G Core and E-UTRA | +| C32a | IF A.4.1-5/1 AND ([10] A.4.1-1/1 OR [10] A.4.1-1/2) AND A.4.4-1/6 THEN R ELSE N/A | UEs supporting 5G Core and E-UTRA and logged MDT | +| C33 | IF A.4.1-5/1 AND A.4.3.7-1/6 AND NOT [10] A.4.4-2/32 THEN R ELSE N/A | UEs supporting 5G Core and SMS over NAS and UE configured to not use SMSolP | +| C34 | IF A.4.1-5/1 AND [10] A.4.4-1/84 THEN R ELSE N/A | UEs supporting 5G Core and MinimumPeriodicSearchTimer | +| C35 | IF A.4.1-5/1 AND (A.4.3.7-1/8 OR A.4.3.7-1/7) THEN R ELSE N/A | UEs supporting 5G Core and (ETWS reception or CMAS reception) | +| C36 | IF A.4.1-5/1 AND [10] A.4.4-1/69 THEN R ELSE N/A | UEs supporting 5G Core and user initiated PLMN reselection in | + +| Condition | Test case Selection Expression | Comment | +|-----------|---------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | automatic mode on NR | +| C37 | IF A.4.1-5/1 AND (A.4.1-2/1 OR A.4.1-2/2) THEN R ELSE N/A | UEs supporting 5G Core and more than 1 FDD or TDD NR band | +| C38 | IF A.4.1-5/1 AND A.4.1-1/1 AND A.4.1-1/2 THEN R ELSE N/A | UEs supporting 5G Core and NR FDD and NR TDD | +| C39 | IF A.4.1-5/1 AND A.4.3.7-1/9 THEN R ELSE N/A | UEs supporting 5G Core and additional UE-requested PDU establishment | +| C39A | IF A.4.1-5/1 AND A.4.3.7-1/9 AND A.4.3.7-1/54 THEN R ELSE N/A | UEs supporting 5G Core and additional UE-requested PDU establishment and support of EAP-AKA' as EAP method for PDU session authentication and authorization | +| C40 | IF A.4.1-5/1 AND A.4.3.6-1/6 THEN R ELSE N/A | UEs supporting 5G Core and SS-SINR measurements | +| C41 | IF A.4.1-5/1 AND (A.4.1-4A/1 OR A.4.1-4A/3) THEN R ELSE N/A | UEs supporting 5G Core and intra-band contiguous CA | +| C42 | IF A.4.1-5/1 AND (A.4.1-4A/5 OR A.4.1-4A/6 OR A.4.1-4A/7) THEN R ELSE N/A | UEs supporting 5G Core and inter-band CA | +| C43 | IF A.4.1-5/1 AND (A.4.1-4A/2 OR A.4.1-4A/4) THEN R ELSE N/A | UEs supporting 5G Core and intra-band non-contiguous CA | +| C44 | IF (A.4.1-4A/1 OR A.4.1-4A/3) THEN R ELSE N/A | UEs supporting 5GS and intra-band contiguous CA | +| C44A | IF A.4.1-3/2 AND (A.4.1-4A/1 OR A.4.1-4A/3) AND A.4.3.2B.2.0-1A/2 THEN R ELSE N/A | UEs supporting EN-DC and intra-band contiguous CA and EN-DC with 2 NR DL carriers | +| C45 | IF (A.4.1-4A/5 OR A.4.1-4A/6 OR A.4.1-4A/7) THEN R ELSE N/A | UEs supporting 5GS and inter-band CA | +| C45A | IF A.4.1-3/2 AND (A.4.1-4A/5 OR A.4.1-4A/6 OR A.4.1-4A/7) AND A.4.3.2B.2.0-1A/2 THEN R ELSE N/A | UEs supporting EN-DC and inter-band contiguous CA and EN-DC with 2 NR DL carriers | +| C46 | IF (A.4.1-4A/2 OR A.4.1-4A/4) THEN R ELSE N/A | UEs supporting 5GS and intra-band non-contiguous CA | +| C46A | IF A.4.1-3/2 AND (A.4.1-4A/2 OR A.4.1-4A/4) AND A.4.3.2B.2.0-1A/2 THEN R ELSE N/A | UEs supporting EN-DC and intra-band non-contiguous CA and EN-DC with 2 NR DL carriers | +| C47 | Void | | +| C48 | Void | | +| C49 | IF A.4.1-5/1 AND A.4.3.6-1/2 THEN R ELSE N/A | UE supporting 5G Core and two independent measurement gap configurations for FR1 and FR2 | +| C50 | IF A.4.1-5/1 AND A.4.3.6-1/5 AND A.4.3.6-1/42 THEN R ELSE N/A | UEs supporting 5G Core and Inter-RAT E-UTRA measurements and Event B triggered reporting and E-UTRA RS-SINR measurements | +| C51 | IF A.4.3.2-1/21 THEN R ELSE N/A | UEs supporting 5GS and PUSCH aggregation | +| C52 | IF A.4.1-5/1 AND A.4.3.6-1/1 AND A.4.3.6-1/3 AND (A.4.3.6-1/4 OR A.4.3.6-1/40) THEN R ELSE N/A | UEs supporting 5G Core and NR measurements and Event A triggered reporting and (NR Intra-frequency and Inter frequency measurements and at least periodical reporting) and CSI-RSRP and CSI-RSRQ measurement | +| C53 | IF A.4.3.5-1/4 THEN R ELSE N/A | UEs supporting 5GS and Logical Channel SR-Delay Timer | +| C54 | IF A.4.1-5/1 AND ([10] A.4.1-1/1 OR [10] A.4.1-1/2) AND [10] A.4.4-1/33 AND A.4.3.7-1/12 THEN R ELSE N/A | UEs supporting 5G Core and E-UTRA and EPS IMS Voice (VoLTE in GSMA PRD IR.92: "IMS Profile for Voice and SMS") and EPS fallback | +| C55 | IF A.4.1-3/2 AND A.4.3.6-1/1 AND (A.4.1-4A/1 OR A.4.1-4A/3) AND A.4.3.2B.2.0-1A/2 AND A.4.3.7-1/3 THEN R ELSE N/A | UEs supporting EN-DC and NR measurements and Event A triggered reporting and intra-band contiguous CA and EN-DC with 2 NR DL carriers and SRB3 | +| C56 | IF A.4.1-3/2 AND A.4.3.6-1/1 AND (A.4.1-4A/5 OR A.4.1-4A/6 OR A.4.1-4A/7) AND A.4.3.2B.2.0-1A/2 AND A.4.3.7-1/3 THEN R ELSE N/A | UEs supporting EN-DC and NR measurements and Event A triggered reporting and inter-band CA and EN-DC with 2 NR DL carriers and SRB3 | +| C57 | IF A.4.1-3/2 AND A.4.3.6-1/1 AND (A.4.1-4A/2 OR A.4.1-4A/4) AND A.4.3.2B.2.0-1A/2 AND A.4.3.7-1/3 THEN R ELSE N/A | UEs supporting EN-DC and NR measurements and Event A triggered reporting and intra-band non-contiguous CA and EN-DC with 2 NR DL carriers and SRB3 | +| C58 | IF A.4.1-5/2 AND [10] A.4.1-1/5.AND A.4.4-1/1 | UEs supporting 5G core over non-3GPP Access Network, WLAN and (ICMP or ICMP IPv6) | +| C59 | IF A.4.1-5/1 AND A.4.3.6-1/8 THEN R ELSE N/A | UEs supporting 5G Core and Support acquisition of relevant information from a neighbouring intra-frequency or inter-frequency NR cell by reading the SI of the neighbouring cell and reporting the acquired information to the network as specified in TS 38.331 [9] when EN-DC is not configured | +| C60 | IF A.4.1-5/1 AND A.4.3.6-1/7 THEN R ELSE N/A | UEs supporting 5G Core and Support acquisition of relevant information from a neighbouring E-UTRA cell by reading the SI of the neighbouring cell and reporting the acquired information to the network as specified in TS 38.331 [9] when the EN-DC is not configured | +| C61 | IF A.4.1-3/2 AND A.4.3.3-1/6 THEN R ELSE N/A | UEs supporting EN-DC and PDCP duplication over split SRB1/2 | +| C62 | IF A.4.1-3/2 AND A.4.3.3-1/4 THEN R ELSE N/A | UEs supporting EN-DC and PDCP duplication over split DRB | +| C63 | IF A.4.1-5/1 AND A.4.3.7-1/13 THEN R ELSE N/A | UEs supporting 5G Core and UE requested PDU session modification procedure | +| C64 | IF A.4.3.2-1/23 THEN R ELSE N/A | UEs supporting 5GS and The maximum number of spatial multiplexing layer(s) supported by the UE for DL reception is 8 Layers. For single CC standalone NR, it is mandatory with capability signalling to support at least 4 MIMO layers in the bands where 4Rx is specified as mandatory for the given UE and at least 2 MIMO layers in FR2. If absent, the UE doesn't support | + +| Condition | Test case Selection Expression | Comment | +|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | MIMO on this carrier | +| C65 | IF A.4.3.2-1/23 AND A.4.3.2-1/4 THEN R ELSE N/A | UEs supporting 5GS and The maximum number of spatial multiplexing layer(s) supported by the UE for DL reception is 8 Layers. For single CC standalone NR, it is mandatory with capability signalling to support at least 4 MIMO layers in the bands where 4Rx is specified as mandatory for the given UE and at least 2 MIMO layers in FR2. If absent, the UE doesn't support MIMO on this carrier | +| C66 | IF (A.4.3.2-1/24 OR A.4.3.2-1/24A) AND (A.4.3.2-1/42 OR A.4.3.2-1/42a OR A.4.3.2-1/42b OR A.4.3.2-1/43 OR A.4.3.2-1/43a OR A.4.3.2-1/43b) THEN R ELSE N/A | UEs supporting 5GS and (DCI and timer based active BWP switching delay type1 or type2) and ((BWP adaptation up to 2 NR FR1 FDD or NR FR1 TDD or NR FR2) or (BWP adaptation up to 4 NR FR1 FDD or NR FR1 TDD or NR FR2)) | +| C67 | IF A.4.1-3/2 AND (A.4.1-4A/1 OR A.4.1-4A/3) AND A.4.3.2B.2.0-1A/2 THEN R ELSE N/A | UEs supporting EN-DC and Intra-Band Contiguous CA and EN-DC with 2 NR DL carriers | +| C68 | IF A.4.1-3/2 AND (A.4.1-4A/2 OR A.4.1-4A/4) AND A.4.3.2B.2.0-1A/2 THEN R ELSE N/A | UEs supporting EN-DC and Intra-Band Non-Contiguous CA and EN-DC with 2 NR DL carriers | +| C69 | IF A.4.1-3/2 AND (A.4.1-4A/5 OR A.4.1-4A/6 OR A.4.1-4A/7) AND A.4.3.2B.2.0-1A/2 THEN R ELSE N/A | UEs supporting EN-DC and Inter-Band CA and EN-DC with 2 NR DL carriers | +| C70 | IF A.4.3.5-1/1 AND A.4.3.5-1/2 THEN R ELSE N/A | UEs supporting 5GS and Long DRX Cycle and Short DRX Cycle | +| C71 | IF A.4.1-3/2 AND A.4.3.7-1/3 AND A.4.3.6-1/3 THEN R ELSE N/A | UEs supporting EN-DC and SRB3 and NR intra-frequency and inter-frequency measurements and at least periodical reporting | +| C72 | IF A.4.1-5/1 AND (A.4.1-4A/1 OR A.4.1-4A/3) AND A.4.3.3-1/3 AND A.4.3.2A.1-2/1 THEN R ELSE N/A | UEs supporting 5G Core and intra-band contiguous CA and CA-based PDCP duplication over MCG or SCG DRB and UL NR CA with 2 carriers | +| C73 | IF A.4.1-5/1 AND (A.4.1-4A/5 OR A.4.1-4A/6 OR A.4.1-4A/7) AND A.4.3.3-1/3 AND A.4.3.2A.1-2/1 THEN R ELSE N/A | UEs supporting 5G Core and inter-band CA and CA-based PDCP duplication over MCG or SCG DRB and UL NR CA with 2 carriers | +| C74 | IF A.4.1-5/1 AND (A.4.1-4A/2 OR A.4.1-4A/4) AND A.4.3.3-1/3 AND A.4.3.2A.1-2/1 THEN R ELSE N/A | UEs supporting 5G Core and intra-band non-contiguous CA and CA-based PDCP duplication over MCG or SCG DRB and UL NR CA with 2 carriers | +| C75 | IF A.4.1-3/2 AND A.4.3.7-1/3 AND (A.4.1-4A/1 OR A.4.1-4A/3) AND A.4.3.3-1/3 AND A.4.3.2B.2.0-2A/2 THEN R ELSE N/A | UEs supporting EN-DC and SRB3 and intra-band contiguous CA and CA-based PDCP duplication over MCG or SCG DRB and EN-DC with 2 NR UL carriers | +| C76 | IF A.4.1-3/2 AND A.4.3.7-1/3 AND (A.4.1-4A/5 OR A.4.1-4A/6 OR A.4.1-4A/7) AND A.4.3.3-1/3 AND A.4.3.2B.2.0-2A/2 THEN R ELSE N/A | UEs supporting EN-DC and SRB3 and inter-band CA and CA-based PDCP duplication over MCG or SCG DRB and EN-DC with 2 NR UL carriers | +| C77 | IF A.4.1-3/2 AND A.4.3.7-1/3 AND (A.4.1-4A/2 OR A.4.1-4A/4) AND A.4.3.3-1/3 AND A.4.3.2B.2.0-2A/2 THEN R ELSE N/A | UEs supporting EN-DC and SRB3 and intra-band non-contiguous CA and CA-based PDCP duplication over MCG or SCG DRB and EN-DC with 2 NR UL carriers | +| C78 | IF A.4.1-5/1 AND A.4.3.7-1/32 AND [9] A.3A/50 AND [9] A.4/2B AND [9] A.15/1 AND [9] A.3A/61 THEN R ELSE N/A | UEs supporting 5G Core and IMS voice over NR and Initiating session and MTSI speech and SMS over IP | +| C79 | IF A.4.1-5/1 AND [9] A.3A/50 AND [9] A.4/2B AND [9] A.15/3 AND [9] A.15/11 AND [9] A.15/12 AND [9] A.15/13 AND [9] A.21/1 THEN R ELSE N/A | UEs supporting 5G Core and Initiating session and MTSI video and MTSI video H.265 MP MT Level 3.1 and MTSI video H.264 CHP Level 3.1 and H.264 CBP Level 3.1 and NG114 v1.0 | +| C80 | IF A.4.1-4/6 THEN R ELSE N/A | UEs supporting NR-DC | +| C81 | IF A.4.1-5/1 AND (A.4.1-4A/1 OR A.4.1-4A/3) AND A.4.3.2A.1-2/1 THEN R ELSE N/A | UEs supporting 5G Core and intra-band contiguous CA and UL NR CA with 2 carriers | +| C81A | IF A.4.1-3/2 AND A.4.1-4/1 AND A.4.3.2B.2.0-2A/2 THEN R ELSE N/A | UEs supporting EN-DC and intra-band contiguous CA and EN-DC with 2 NR UL carriers | +| C82 | IF A.4.1-5/1 AND (A.4.1-4A/5 OR A.4.1-4A/6 OR A.4.1-4A/7) AND A.4.3.2A.1-2/1 THEN R ELSE N/A | UEs supporting 5G Core and inter-band CA and UL NR CA with 2 carriers | +| C82A | IF A.4.1-3/2 AND (A.4.1-4/3 OR A.4.1-4/4 OR A.4.1-4/5) AND A.4.3.2B.2.0-2A/2 THEN R ELSE N/A | UEs supporting EN-DC and inter-band CA and EN-DC with 2 NR UL carriers | +| C83 | IF A.4.1-5/1 AND (A.4.1-4A/2 OR A.4.1-4A/4) AND A.4.3.2A.1-2/1 THEN R ELSE N/A | UEs supporting 5G Core and intra-band non-contiguous CA and UL NR CA with 2 carriers | +| C83A | IF A.4.1-3/2 AND A.4.1-4/2 AND A.4.3.2B.2.0-2A/2 THEN R ELSE N/A | UEs supporting EN-DC and intra-band non-contiguous CA and EN-DC with 2 NR UL carriers | +| C84 | IF A.4.1-5/1 AND [10] A.4.4-1/99 THEN R ELSE N/A | UEs supporting 5G Core and ZUC algorithm | +| C85 | Void | | +| C85A | IF (A.4.1-5/1 AND A.4.4-2/9) AND ([10] A.4.1-1/1 OR [10] A.4.1-1/2) AND [10] A.4.2.1.1-1/4 AND A.4.3.7-1/14 THEN R ELSE N/A | UEs supporting 5G core and Emergency PDN connection transfer from S1 mode to N1 mode when network does not support N26 interface, and, E-UTRA and EPS IMS emergency call (VoLTE in GSMA PRD IR.92: "IMS Profile for Voice and SMS") and emergency services in NR connected to 5GCN | +| C85B | IF (A.4.1-5/1 AND A.4.4-2/8) AND ([10] A.4.1-1/1 OR [10] A.4.1-1/2) AND [10] A.4.2.1.1-1/4 AND A.4.3.7-1/32 THEN R ELSE N/A | UEs supporting 5G core and Emergency PDU session transfer from N1 mode to S1 mode when network does not support N26 interface, and, E-UTRA and EPS IMS emergency call (VoLTE in GSMA PRD IR.92: "IMS Profile for Voice and SMS") and IMS voice over NR | +| C86 | IF A.4.1-4/6 AND A.4.3.7-1/3 THEN R ELSE N/A | UEs supporting NR-DC and SRB3 | +| C87 | IF A.4.1-4/6 AND A.4.3.7-1/3 AND A.4.3.6-1/3 THEN R ELSE N/A | UEs supporting NR-DC and SRB3 and NR intra-frequency and inter-frequency measurements and at least periodical reporting | +| C88 | IF A.4.1-4/6 AND A.4.3.7-1/3 AND (A.4.1-4A/1 OR A.4.1-4A/3) AND A.4.3.3-1/3 AND A.4.3.2A.1-2/1 THEN R ELSE | UEs supporting NR-DC and SRB3 and intra-band contiguous CA and CA-based PDCP duplication over MCG or SCG DRB and UL | + +| Condition | Test case Selection Expression | Comment | +|-----------|------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | N/A | NR CA with 2 carriers | +| C89 | IF A.4.1-4/6 AND A.4.3.7-1/3 AND (A.4.1-4A/5 OR A.4.1-4A/6 OR A.4.1-4A/7) AND A.4.3.3-1/3 AND A.4.3.2A.1-2/1 THEN R ELSE N/A | UEs supporting NR-DC and SRB3 and inter-band CA and CA-based PDCP duplication over MCG or SCG DRB and UL NR CA with 2 carriers | +| C90 | IF A.4.1-4/6 AND A.4.3.7-1/3 AND (A.4.1-4A/2 OR A.4.1-4A/4) AND A.4.3.3-1/3 AND A.4.3.2A.1-2/1 THEN R ELSE N/A | UEs supporting NR-DC and SRB3 and intra-band non-contiguous CA and CA-based PDCP duplication over MCG or SCG DRB and UL NR CA with 2 carriers | +| C91 | IF A.4.1-5/1 AND [10] A.4.4-1/98 THEN R ELSE N/A | UEs supporting 5G Core and ManualModeNetworkSelectionException | +| C92 | IF A.4.1-5/1 AND A.4.3.7-1/14 THEN R ELSE N/A | UEs supporting 5G Core and emergency services in NR connected to 5GCN | +| C92A | IF A.4.1-5/1 AND A.4.3.7-1/14 AND A.4.3.7-1/63 THEN R ELSE N/A | UEs supporting 5G Core and emergency services in NR connected to 5GCN and steering of roaming connected mode control information | +| C93 | IF A.4.1-3/2 AND A.4.3.6-1/1 AND A.4.3.6-1/3 AND (A.4.1-2/1 OR A.4.1-2/2 OR (A.4.1-1/1 AND A.4.1-1/2)) THEN R ELSE N/A | UEs supporting EN-DC and NR measurements and Event A triggered reporting and (NR Intra-frequency and NR-Inter frequency measurements and at least periodical reporting) and multiple NR bands | +| C94 | IF A.4.1-5/1 AND (A.4.1-2/1 OR A.4.1-2/2 OR (A.4.1-1/1 AND A.4.1-1/2)) THEN R ELSE N/A | UEs supporting 5G Core and multiple NR bands | +| C95 | IF A.4.1-5/1 AND ([10] A.4.1-1/1 OR [10] A.4.1-1/2) AND [10] A.4.4-1/33 AND A.4.3.7-1/12 AND A.4.3.7-1/15 THEN R ELSE N/A | UEs supporting 5G Core and E-UTRA and EPS IMS Voice (VoLTE in GSMA PRD IR.92: "IMS Profile for Voice and SMS") and EPS fallback and voiceFallbackIndication | +| C96 | IF A.4.1-5/1 AND A.4.1-3/2 AND A.4.3.8-1/10 THEN R ELSE N/A | UEs supporting 5G Core and EN-DC and inter-RAT Handover from NR to EN-DC | +| C97 | IF A.4.1-4/6 AND A.4.3.7-1/2 THEN R ELSE N/A | UEs supporting NR-DC and UL transmission via both MCG path and SCG path for the split DRB | +| C98 | IF A.4.1-4/6 AND A.4.3.3-1/4 THEN R ELSE N/A | UEs supporting NR-DC and PDCP duplication over split DRB | +| C99 | IF A.4.1-5/1 AND ([10] A.4.1-1/1 OR [10] A.4.1-1/2) AND (A.4.3.8-1/6 OR A.4.3.8-1/7 OR A.4.3.8-1/8) THEN R ELSE N/A | UEs supporting 5G Core and E-UTRA and (inter-RAT Handover to NR FR1 TDD from EUTRA connected to EPC or inter-RAT Handover to NR FR1 FDD from EUTRA connected to EPC or inter-RAT Handover to NR FR2 TDD from EUTRA connected to EPC) | +| C100 | IF A.4.1-5/1 AND [9] A.15/1 AND A.4.3.5-1/9 THEN R ELSE N/A | UEs supporting 5G Core and MTSI speech and bit rate recommendation query message | +| C101 | IF A.4.1-5/1 AND A.4.3.8-1/9 THEN R ELSE N/A | UEs supporting 5G Core and intra-frequency DAPS handover | +| C102 | Void | | +| C103 | IF A.4.3.5-1/1 AND A.4.3.5-1/5 THEN R ELSE N/A | UEs supporting 5GS and Long DRX Cycle and DRX adaptation | +| C104 | IF (A.4.1-4A/1 OR A.4.1-4A/3) AND A.4.3.2A.1-1/2 AND A.4.3.2A.1-2/2 AND A.4.3.3-1/5 THEN R ELSE N/A | UEs supporting 5G Core and Intra-band contiguous CA and DL and UL NR CA with 3 carriers and PDCP duplication with more than two RLC entities | +| C105 | IF (A.4.3.4-1/2 OR A.4.3.4-1/3) AND A.4.3.3-1/7 THEN R ELSE N/A | UEs supporting 5GS and RLC UM mode and PDCP ethernet header compression | +| C106 | IF A.4.1-5/1 AND A.4.3.10-1/1 THEN R ELSE N/A | UE supporting 5G core and NR sidelink mode 1 transmission | +| C107 | IF A.4.3.2-1/32 THEN R ELSE N/A | UE's supporting multi-DCI based multi-TRP | +| C108 | IF A.4.1-5/1 AND A.4.3.7-1/17 THEN R ELSE N/A | UEs supporting 5G Core and RACS | +| C109 | IF A.4.1-5/1 AND A.4.3.7-1/19 THEN R ELSE N/A | UEs supporting 5G Core and RRC_INACTIVE | +| C109A | IF A.4.1-5/1 AND A.4.3.7-1/19 AND A.4.4-2/10 THEN R ELSE N/A | UEs supporting 5G Core and RRC_INACTIVE and UE's usage setting as data centric | +| C110 | IF A.4.1-5/1 AND ([10] A.4.1-1/1 OR [10] A.4.1-1/2) AND A.4.3.7-1/19 THEN R ELSE N/A | UEs supporting 5G Core and E-UTRA and RRC_INACTIVE | +| C111 | IF A.4.1-5/1 AND (A.4.3.7-1/8 OR A.4.3.7-1/7) AND A.4.3.7-1/19 THEN R ELSE N/A | UEs supporting 5G Core and (ETWS reception or CMAS reception) and RRC_INACTIVE | +| C112 | Void | | + +| Condition | Test case Selection Expression | Comment | +|-----------|--------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| C113 | IF A.4.1-5/1 AND A.4.3.2-1/1 AND A.4.3.2-1/121 THEN R ELSE N/A | UEs supporting 5G Core and PDsch reception based on semi-persistent scheduling and up to 8 configured SPS configurations in a BWP of a serving cell and up to 32 configured SPS configurations in a cell group | +| C114 | IF A.4.1-5/1 AND A.4.3.5-1/6 THEN R ELSE N/A | UEs supporting 5GS and LCH-based UL grant prioritization | +| C115 | IF A.4.1-5/1 AND A.4.3.8-1/11 THEN R ELSE N/A | UEs supporting 5G Core and conditional handover | +| C116 | IF A.4.1-5/1 AND A.4.3.8-1/11 AND A.4.3.8-1/13 THEN R ELSE N/A | UEs supporting 5G Core and conditional handover and supporting 2 trigger events for same execution condition | +| C117 | IF A.4.1-5/1 AND A.4.3.8-1/11 AND A.4.3.8-1/12 THEN R ELSE N/A | UEs supporting 5G Core and conditional handover and conditional handover during re-establishment procedure when the selected cell is configured as candidate cell for condition handover | +| C118 | IF A.4.3.5-1/1 AND A.4.3.5-1/5 AND A.4.3.2-1/35 AND (A.4.1-4A/1 OR A.4.1-4A/3) THEN R ELSE N/A | UEs supporting 5GS and Long DRX Cycle and DRX adaptation and SCell Dormancy indication outside active time and intra-band contiguous CA | +| C119 | IF A.4.3.5-1/1 AND A.4.3.5-1/5 AND A.4.3.2-1/35 AND (A.4.1-4A/2 OR A.4.1-4A/4) THEN R ELSE N/A | UEs supporting 5GS and Long DRX Cycle and DRX adaptation and SCell Dormancy indication outside active time and intra-band non-contiguous CA | +| C120 | IF A.4.3.5-1/1 AND A.4.3.5-1/5 AND A.4.3.2-1/35 AND (A.4.1-4A/5 OR A.4.1-4A/6 OR A.4.1-4A/7) THEN R ELSE N/A | UEs supporting 5GS and Long DRX Cycle and DRX adaptation and SCell Dormancy indication outside active time and inter-band CA | +| C121 | Void | | +| C122 | IF A.4.1-5/1 AND A.4.4-1/5 THEN R ELSE N/A | UEs supporting 5G Core and UL PDCP Packet Delay per DRB | +| C123 | IF A.4.1-5/1 AND A.4.4-1/6 THEN R ELSE N/A | UEs supporting 5G core and logged measurements in RRC_IDLE and RRC_INACTIVE | +| C124 | IF A.4.1-5/1 AND A.4.4-1/4 AND A.4.4-1/6 THEN R ELSE N/A | UEs supporting 5G core and logged measurements in RRC_IDLE and RRC_INACTIVE and equipped with a GNSS receiver to provide detailed location information | +| C125 | IF A.4.1-5/1 AND A.4.4-1/6 AND A.4.3.7-1/19 THEN R ELSE N/A | UEs supporting 5G core and RRC_INACTIVE and logged measurements in RRC_IDLE and RRC_INACTIVE | +| C126 | IF A.4.1-5/1 AND A.4.4-1/4 THEN R ELSE N/A | UEs supporting 5G Core and equipped with a GNSS or A-GNSS receiver to provide detailed location information | +| C127 | IF A.4.1-5/1 AND [10] A.4.1-1/6 AND A.4.3.8-1/11 THEN R ELSE N/A | UEs supporting 5G Core and UTRA and NR to UTRA-FDD CELL_DCH CS handover | +| C128 | IF A.4.1-5/1 AND A.4.1-1/3 THEN R ELSE N/A | UE supporting 5G core and NR sidelink | +| C129 | IF A.4.1-5/1 AND A.4.3.7-1/18 THEN R ELSE N/A | UEs supporting 5G Core and RRC message Segmentation in the UL | +| C130 | IF A.4.1-5/1 AND A.4.3.8-1/15 AND A.4.3.8-1/48 THEN R ELSE N/A | UEs supporting 5G Core and inter-frequency DAPS handover on intra-band non-contiguous BC | +| C130A | IF A.4.1-5/1 AND A.4.3.8-1/15 AND A.4.3.8-1/47 THEN R ELSE N/A | UEs supporting 5G Core and inter-frequency DAPS handover on intra-band contiguous BC | +| C131 | IF A.4.1-5/1 AND A.4.3.7-1/24 THEN R ELSE N/A | UEs supporting 5G Core and SNPN | +| C132 | IF A.4.1-5/1 AND A.4.3.7-1/23 THEN R ELSE N/A | UEs supporting 5G Core and CAG | +| C133 | IF A.4.1-5/1 AND A.4.3.7-1/21 THEN R ELSE N/A | UEs supporting 5G Core and RRC connection release with Deprioritisation | +| C134 | IF A.4.3.2-1/45 THEN R ELSE N/A | UEs supporting PUSCH repetition type B | +| C135 | IF A.4.3.2-1/46 THEN R ELSE N/A | UEs supporting 2-Step RACH | +| C135A | IF A.4.1-5/1 AND A.4.3.2-1/46 THEN R ELSE N/A | UEs supporting 5G Core and 2-Step RACH | + +| Condition | Test case Selection Expression | Comment | +|-----------|----------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| C136 | IF A.4.1-5/1 AND A.4.4-1/3 THEN R ELSE N/A | UEs supporting 5G Core and delivery of rachReport upon request from the network | +| C137 | IF A.4.1-5/1 AND A.4.4-1/6 AND A.4.4-1/12 THEN R ELSE N/A | UEs supporting 5G core and logged MDT and Bluetooth measurements in RRC_IDLE and RRC_INACTIVE state | +| C138 | IF A.4.1-5/1 AND A.4.4-1/6 AND A.4.4-1/13 THEN R ELSE N/A | UEs supporting 5G core and logged MDT and WLAN measurements in RRC_IDLE and RRC_INACTIVE state | +| C139 | IF A.4.1-5/1 AND (A.4.4-1/7 OR A.4.4-1/8 OR A.4.4-1/9) THEN R ELSE N/A | UEs supporting 5G Core and collection of sensor information such as Barometric pressure, UE speed, and UE orientation information as defined in TS 37.355 | +| C139a | IF A.4.1-5/1 AND (A.4.4-1/7 OR A.4.4-1/8 OR A.4.4-1/9) AND A.4.4-1/6 THEN R ELSE N/A | UEs supporting 5G Core and collection of sensor information such as Barometric pressure, UE speed, and UE orientation information as defined in TS 37.355 and logged MDT | +| C140 | IF A.4.1-5/1 AND A.4.4-1/10 THEN R ELSE N/A | UEs supporting 5G core and Bluetooth Measurement Collection in Immediate MDT | +| C141 | IF A.4.1-5/1 AND A.4.4-1/11 THEN R ELSE N/A | UEs supporting 5G core and WLAN Measurement Collection in Immediate MDT | +| C142 | IF A.4.1-5/1 AND A.4.3.2-1/10 AND A.4.3.2-1/230 THEN R ELSE N/A | UEs supporting 5G Core and Type 1 PUSCH transmissions with configured grant and up to 12 configured/active configured grant configurations in a BWP of a serving cell. | +| C143 | IF A.4.1-5/1 AND ([10] A.4.1-1/1 OR [10] A.4.1-1/2) AND A.4.4-1/4 THEN R ELSE N/A | UEs supporting 5G Core and E-UTRA and standalone GNSS receiver to provide detailed location information | +| C144 | IF A.4.1-5/1 AND ([10] A.4.1-1/1 OR [10] A.4.1-1/2) AND A.4.4-1/6 THEN R ELSE N/A | UEs supporting 5G Core and E-UTRA and logged measurements in RRC_IDLE and RRC_INACTIVE | +| C145 | IF A.4.1-5/1 AND A.4.3.7-1/29 THEN R ELSE N/A | UEs supporting 5G Core and release preference assistance information | +| C146 | IF A.4.3.2-1/52 THEN R ELSE N/A | UEs supporting monitoring DCI format 1_2 for DL scheduling and monitoring DCI format 0_2 for UL scheduling | +| C146a | Void | C | +| C147 | IF A.4.1-5/1 AND A.4.3.7-1/26 AND A.4.3.7-1/27 THEN R ELSE N/A | UEs supporting 5G Core and NSSAA and EAP-AKA' for NSSAA | +| C148 | IF A.4.1-5/1 AND ([10] A.4.1-1/1 OR [10] A.4.1-1/2) AND A.4.3.7-1/21 THEN R ELSE N/A | UEs supporting 5G Core and E-UTRA and RRC connection release with Deprioritisation | +| C149 | IF A.4.1-4/6 AND A.4.3.6-1/2 THEN R ELSE N/A | UEs supporting NR-DC and two independent measurement gap configurations for FR1 and FR2 | +| C150 | IF A.4.1-5/1 AND (A.4.3.6-1/48 OR A.4.3.6-1/49) THEN R ELSE N/A | UEs supporting 5G Core and SFTD measurements between NR PCell and NR neighbour cell | +| C151 | IF A.4.1-3/2 AND (A.4.3.6-1/43 OR A.4.3.6-1/44) AND (A.4.3.6-1/46 OR A.4.3.6-1/47) THEN R ELSE N/A | UEs supporting EN-DC and SFTD measurement between E-UTRA PCell and an NR neighbour cell, and SFTD measurement between E-UTRA PCell and NR PSCell | +| C152 | IF A.4.1-4/6 AND (A.4.3.6-1/48 OR A.4.3.6-1/49) AND (A.4.3.6-1/50 OR A.4.3.6-1/51) THEN R ELSE N/A | UEs supporting NR-DC and SFTD measurement between NR PCell and an NR neighbour cell, and SFTD measurement between NR PCell and NR PSCell | +| C153 | IF A.4.1-3/2 AND A.4.3.8-1/19 THEN R ELSE N/A | UEs supporting EN-DC and conditional PSCell change | +| C153A | IF A.4.1-3/2 AND (A.4.3.8-1/29 OR A.4.3.8-1/30 OR A.4.3.8-1/31) | UEs supporting EN-DC and MN initiated conditional PSCell change | +| C153B | IF A.4.1-3/1 AND A.4.3.8-1/28 | UEs supporting NR-DC and MN initiated conditional PSCell change | +| C153C | IF A.4.1-3/2 AND (A.4.3.8-1/33 OR A.4.3.8-1/34 OR A.4.3.8-1/35) | UEs supporting EN-DC and SN initiated conditional PSCell change | +| C153D | IF A.4.1-3/1 AND A.4.3.8-1/32 | UEs supporting NR-DC and SN initiated conditional PSCell change | +| C154 | IF A.4.1-5/1 AND (A.4.1-4A/1 OR A.4.1-4A/3) AND A.4.3.7-1/19 AND A.4.3.5-1/14 THEN R ELSE N/A | UEs supporting 5G Core and intra-band contiguous CA and RRC_INACTIVE and direct NR MCG SCell activation | +| C155 | IF A.4.1-5/1 AND (A.4.1-4A/2 OR A.4.1-4A/4) AND A.4.3.7-1/19 AND A.4.3.5-1/14 THEN R ELSE N/A | UEs supporting 5G Core and intra-band non-contiguous CA and RRC_INACTIVE and direct NR MCG SCell activation | +| C156 | IF A.4.1-5/1 AND (A.4.1-4A/5 OR A.4.1-4A/6) AND A.4.3.7-1/19 AND A.4.3.5-1/14 THEN R ELSE N/A | UEs supporting 5G Core and inter-band CA and RRC_INACTIVE- and direct NR MCG SCell activation | +| C157 | IF A.4.1-4/6 AND A.4.3.7-1/3 AND A.4.3.7-1/1 THEN R ELSE N/A | UEs supporting NR-DC and SRB3 and (UL transmission via either MCG path or SCG path for the split SRB) | +| C158 | Void | | + +| Condition | Test case Selection Expression | Comment | +|-----------|--------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| C159 | IF A.4.1-5/2 AND [10] A.4.1-1/5 THEN R ELSE N/A | UEs supporting 5G core over non-3GPP Access Network and WLAN and additional UE-requested PDU establishment | +| C160 | IF A.4.1-3/3 THEN R ELSE N/A | UEs supporting NE-DC | +| C161 | IF A.4.1-5/1 AND A.4.3.7-1/21 AND [10] A.4.4-1/98 THEN R ELSE N/A | UEs supporting 5G Core and RRC connection release with Deprioritisation and ManualModeNetworkSelectionException | +| C162 | IF A.4.1-5/1 AND [9] A.21/3 AND [9] A.12/69 THEN R ELSE N/A | UEs supporting 5G Core and NG.114 and 3GPP PS data off | +| C162A | IF A.4.1-5/1 AND [9] A.21/3 AND [9] A.12/69 AND [9] A.3A/61 THEN R ELSE N/A | UEs supporting 5G Core and NG.114 and 3GPP PS data off and SMS over IP | +| C163 | IF A.4.1-5/1 AND A.4.1-1/3 AND A.4.3.10-1/3 THEN R ELSE N/A | UE supporting 5G core and NR sidelink and Sidelink CSI report | +| C164 | IF A.4.1-5/1 AND A.4.3.10-1/1 AND A.4.3.10-1/3 THEN R ELSE N/A | UE supporting 5G core and NR sidelink mode 1 transmission and Sidelink CSI report | +| C165 | Void | | +| C166 | IF A.4.1-5/1 AND A.4.3.7-1/34 THEN R ELSE N/A | UE supporting 5G Core and V2X communication over NR-PC5 | +| C167 | IF A.4.1-5/1 AND A.4.3.7-1/24 AND A.4.3.7-1/30 THEN R ELSE N/A | UEs supporting 5G Core and SNPN and user initiated SNPN reselection in automatic mode on NR | +| C168 | IF A.4.1-5/1 AND A.4.3.7-1/23 AND A.4.3.7-1/31 THEN R ELSE N/A | UEs supporting 5G Core and CAG and Autonomous search function on NR | +| C169 | IF A.4.1-5/1 AND A.4.3.7-1/23 AND A.4.3.6-1/52 THEN R ELSE N/A | UEs supporting 5G Core and CAG and acquisition of CGI information from neighbour NR NPN cell | +| C170 | IF A.4.1-5/1 AND ([10] A.4.1-1/1 OR [10] A.4.1-1/2) AND [9]A.12/64 AND [11]A.10/16 THEN R ELSE N/A | UEs supporting 5G Core and E-UTRA and IMS eCall Only type of emergency services over 5GS and Manual type of eCall initiation | +| C171 | IF A.4.1-5/1 AND ([10] A.4.1-1/1 OR [10] A.4.1-1/2) AND [9]A.12/64 AND [11]A.10/16 AND [11]A.10/19 THEN R ELSE N/A | UEs supporting 5G Core and E-UTRA and IMS eCall Only type of emergency services over 5GS and Manual type of eCall initiation and capable of triggering a Test eCall | +| C172 | IF A.4.1-5/1 AND [9] A.21/3 AND [9] A.12/69 AND [9] A.15/3 THEN R ELSE N/A | UEs supporting 5G Core and NG.114 and 3GPP PS data off and MTSI video | +| C173 | IF A.4.1-5/1 AND ([10] A.4.1-1/1 OR [10] A.4.1-1/2) AND [9] A.21/3 | UEs supporting 5G Core and E-UTRA and NG.114 | +| C174 | IF A.4.1-5/1 AND [9]A.12/64 AND [11] A.10/16 AND [11] A.10/19 THEN R ELSE N/A | UEs supporting 5G Core and IMS eCall Only type of emergency services over 5GS and Manual type of eCall initiation and capable of triggering a Test eCall | +| C175 | IF A.4.3.5-1/11 THEN R ELSE N/A | UEs supporting 5GS and selection of logical channels for each UL grant based on RRC configured restriction | +| C176 | IF A.4.1-5/1 AND ([10] A.4.1-1/1 OR [10] A.4.1-1/2) AND [10] A.4.2.1.1-1/4 THEN R ELSE N/A | UEs supporting 5G Core and E-UTRA and EPS IMS emergency call (VoLTE in GSMA PRD IR.92: "IMS Profile for Voice and SMS") | +| C177 | IF A.4.1-5/1 AND A.4.3.7-1/17 AND A.4.3.7-1/35 THEN R ELSE N/A | UEs supporting 5G Core and RACS and Manufacturer assigned Radio Capability ID | +| C178 | IF A.4.1-5/1 AND ([10] A.4.1-1/1 OR [10] A.4.1-1/2) AND A.4.3.7-1/17 AND [10]A.4.4-1/215 THEN R ELSE N/A | UEs supporting 5G Core and E-UTRA and RACS | +| C179 | IF A.4.3.2-1/80 THEN R ELSE N/A | UEs supporting DCI DL Priority Indicator | +| C180 | IF A.4.3.2-1/81 AND A.4.3.2-1/82 THEN R ELSE N/A | UEs supporting DCI UL Priority Indicator and LCH grant prioritisation | +| C181 | IF (A.4.1-4A/2 OR A.4.1-4A/4) AND A.4.3.2A.1-1/2 AND A.4.3.2A.1-2/2 AND A.4.3.3-1/5 THEN R ELSE N/A | UEs supporting 5G Core and Intra-band non-contiguous CA and DL and UL NR CA with 3 carriers and PDCP duplication with more than two RLC entities | +| C182 | IF A.4.1-3/3 AND A.4.3.6-1/1 AND A.4.3.6-1/3 THEN R | UEs supporting NE-DC and NR measurements and Event A triggered reporting and (NR intra-frequency and inter-frequency | + +| Condition | Test case Selection Expression | Comment | +|-----------|------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | ELSE N/A | measurements and at least periodical reporting). | +| C183 | IF A.4.1-3/3 AND A.4.3.6-1/1 AND A.4.3.6-1/3 AND (A.4.1-2/1 OR A.4.1-2/2 OR (A.4.1-1/1 AND A.4.1-1/2)) THEN R ELSE N/A | UEs supporting NE-DC and NR measurements and Event A triggered reporting and (NR intra-frequency and inter-frequency measurements and at least periodical reporting) and multiple NR bands | +| C184 | IF A.4.1-5/1 AND [9]A.12/64 AND [11]A.10/17 THEN R ELSE N/A | UEs supporting 5G Core and IMS eCall Only type of emergency services over 5GS and Automatic type of eCall initiation | +| C185 | IF A.4.1-5/1 AND [10] A.4.1-1/6 AND [9] A.12/63 AND [11] A.10/17 AND A.4.3.7-1/14 THEN R ELSE N/A | UEs supporting 5G Core and UTRA and IMS eCall type of emergency services over 5GS and Automatic type of eCall initiation and emergency services in NR connected to 5GCN | +| C186 | IF A.4.1-5/1 AND [10] A.4.1-1/6 AND [9] A.12/64 AND [11] A.10/16 AND A.4.3.8-1/14 THEN R ELSE N/A | UEs supporting 5G Core and UTRA and IMS eCall Only type of emergency services over 5GS and Manual type of eCall initiation and NR to UTRA-FDD CELL_DCH CS handover | +| C187 | IF A.4.1-5/1 AND ([10] A.4.1-1/6 OR [10] A.4.1-1/7) AND [9] A.12/64 AND [11] A.10/16 THEN R ELSE N/A | UEs supporting 5G Core and (UTRA OR GERAN) and IMS eCall Only type of emergency services over 5GS and Manual type of eCall initiation | +| C188 | IF A.4.1-5/1 AND ([10] A.4.1-1/6 OR [10] A.4.1-1/7) AND [9] A.12/64 AND [11] A.10/17 THEN R ELSE N/A | UEs supporting 5G Core and (UTRA OR GERAN) and IMS eCall Only type of emergency services over 5GS and Automatic type of eCall initiation | +| C189 | IF A.4.1-5/1 AND ([10] A.4.1-1/6 OR [10] A.4.1-1/7) AND [9] A.12/63 AND [11] A.10/16 THEN R ELSE N/A | UEs supporting 5G Core and (UTRA OR GERAN) and eCall type of emergency services over 5GS and Manual type of eCall initiation | +| C190 | IF A.4.1-5/1 AND A.4.3.6-1/54 THEN R ELSE N/A | UEs supporting 5G Core and Idle/Inactive Measurements | +| C191 | IF A.4.1-5/1 AND ([10] A.4.1-1/1 OR [10] A.4.1-1/2) AND A.4.3.6-1/55 THEN R ELSE N/A | UEs supporting 5G Core and E-UTRA and Idle/Inactive Measurements | +| C192 | IF A.4.1-5/1 AND A.4.3.7-1/19 AND A.4.3.6-1/54 THEN R ELSE N/A | UEs supporting 5G Core and RRC_INACTIVE and Idle/Inactive Measurements | +| C193 | IF A.4.1-5/1 AND A.4.3.7-1/19 AND ([10] A.4.1-1/1 OR [10] A.4.1-1/2) AND A.4.3.6-1/55 THEN R ELSE N/A | UEs supporting 5G Core and RRC_INACTIVE and E-UTRA and Idle/Inactive Measurements | +| C194 | IF A.4.1-3/3 AND A.4.3.7-1/2 THEN R ELSE N/A | UEs supporting NE-DC and UL transmission via both MCG path and SCG path for the split DRB | +| C195 | IF A.4.1-4/6 AND A.4.3.3-1/6 THEN R ELSE N/A | UEs supporting NR-DC and PDCP duplication over split SRB1/2 | +| C196 | IF A.4.1-3/3 AND A.4.3.3-1/6 THEN R ELSE N/A | UEs supporting NE-DC and PDCP duplication over split SRB1/2 | +| C197 | IF A.4.1-5/1 AND ([10] A.4.1-1/1 OR [10] A.4.1-1/2) AND [9]A.12/64 AND [11]A.10/17 THEN R ELSE N/A | UEs supporting 5G Core and E-UTRA and IMS eCall Only type of emergency services over 5GS and Automatic type of eCall initiation | +| C198 | IF A.4.1-5/1 AND [9] A.6a/2 THEN R ELSE N/A | UEs supporting 5G Core and IMS security | +| C199 | IF A.4.1-3/2 AND A.4.3.5-1/12 AND (A.4.1-4A/1 OR A.4.1-4A/3) THEN R ELSE N/A | UEs supporting EN-DC, direct NR SCG SCell activation and Intra-Band Contiguous CA | +| C200 | IF A.4.1-3/2 AND A.4.3.5-1/12 AND (A.4.1-4A/2 OR A.4.1-4A/4) THEN R ELSE N/A | UEs supporting EN-DC, direct NR SCG SCell activation and Intra-Band Non-Contiguous CA | +| C201 | IF A.4.1-3/2 AND A.4.3.5-1/12 AND (A.4.1-4A/5 OR A.4.1-4A/6 OR A.4.1-4A/7) THEN R ELSE N/A | UEs supporting EN-DC, direct NR SCG SCell activation and Inter-Band CA | +| C202 | IF A.4.1-4/6 AND A.4.3.5-1/12 AND (A.4.1-4A/1 OR A.4.1-4A/3) THEN R ELSE N/A | UEs supporting NR-DC, direct NR SCG SCell activation and intra-band contiguous CA | +| C203 | IF A.4.1-4/6 AND A.4.3.5-1/12 AND (A.4.1-4A/2 OR A.4.1-4A/4) THEN R ELSE N/A | UEs supporting NR-DC, direct NR SCG SCell activation and intra-band non-contiguous CA | +| C204 | IF A.4.1-4/6 AND A.4.3.5-1/12 AND (A.4.1-4A/5 OR A.4.1-4A/6 OR A.4.1-4A/7) THEN R ELSE N/A | UEs supporting NR-DC, direct NR SCG SCell activation and inter-band CA | +| C205 | Void | | +| C206 | IF A.4.1-3/3 AND A.4.3.6-1/5 THEN R ELSE N/A | UEs supporting NE-DC and Inter-RAT E-UTRA measurements and Event B triggered reporting | + +| Condition | Test case Selection Expression | Comment | +|-----------|-------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| C207 | IF A.4.1-5/1 AND A.4.3.7-1/39 THEN R ELSE N/A | UEs supporting 5G core and reception of segmented DL RRC messages. | +| C208 | IF A.4.1-5/1 AND A.4.4-1/2 AND A.4.3.8-1/20 AND [10] A.4.1-1/5 AND [10] A.4.4-1/117 THEN R ELSE N/A | UEs supporting 5G Core and IMS and handover from 5G Core to EPC over non-3GPP Access Network and GSMA PRD IR.51: "IMS Profile for Voice, Video and SMS over Wi-Fi" and WLAN. | +| C209 | IF A.4.1-5/1 AND A.4.3.12-1/2 AND A.4.3.12-1/6 AND A.4.3.12-1/7 THEN R ELSE N/A | UEs supporting 5G Core and RedCap and relaxed RRM measurements in RRC_CONNECTED and initiating UE Assistance Information procedure immediately upon change of its fulfilment status for RRM measurement relaxation criterion for connected mode. | +| C210 | IF A.4.1-5/1 AND A.4.3.7-1/43 THEN R ELSE N/A | UEs supporting 5G Core and eDRX in RRC_IDLE | +| C210A | IF A.4.1-5/1 AND A.4.3.7-1/43 AND A.4.3.7-1/19 AND A.4.3.7-1/68 THEN R ELSE N/A | UEs supporting 5G Core and eDRX in RRC_IDLE and RRC_INACTIVE and eDRX in RRC_INACTIVE with values of 256, 512 and 1024 radio frames | +| C211 | IF A.4.1-5/1 AND A.4.3.2-1/85 THEN R ELSE N/A | UEs supporting 5G Core and repetition of Message 3 PUSCH | +| C212 | IF A.4.1-5/1 AND A.4.3.12-1/2 THEN R ELSE N/A | UEs supporting 5G Core and RedCap | +| C212a | IF A.4.1-5/1 AND A.4.3.12-1/2 AND A.4.3.7-1/19 THEN R ELSE N/A | UEs supporting 5G Core and RedCap and RRC_INACTIVE | +| C213 | IF A.4.1-5/1 AND A.4.3.14-1/1 THEN R ELSE N/A | UE supporting 5G Core and broadcast reception | +| C214 | IF A.4.1-5/1 AND A.4.3.14-1/2 THEN R ELSE N/A | UE supporting 5G Core and dynamic scheduling for multicast for PCell | +| C215 | IF A.4.1-5/1 AND A.4.3.14-1/2 AND A.4.3.14-1/3 THEN R ELSE N/A | UE supporting 5G Core and dynamic scheduling for multicast for PCell and ACK/NACK based HARQ-ACK feedback and RRC-based enabling/disabling ACK/NACK-based feedback for dynamic scheduling for multicast | +| C216 | IF A.4.1-5/1 AND A.4.3.14-1/2 AND A.4.3.14-1/3 AND A.4.3.14-1/4 THEN R ELSE N/A | UE supporting 5G Core and dynamic scheduling for multicast for PCell and ACK/NACK based HARQ-ACK feedback and RRC-based enabling/disabling ACK/NACK-based feedback for dynamic scheduling for multicast and PTP retransmission for multicast on the same cell as multicast initial transmission | +| C217 | IF A.4.1-5/1 AND A.4.3.2-2/3 THEN R ELSE N/A | UEs supporting 5G Core and NR standalone shared spectrum channel access | +| C217A | IF A.4.1-5/1 AND A.4.3.2-2/3 AND A.4.3.5-1/17 THEN R ELSE N/A | UEs supporting 5G Core and NR standalone shared spectrum channel access and UL LBT Failure Detection and Recovery | +| C218 | IF A.4.1-5/1 AND A.4.3.2-2/3 AND A.4.3.2-2/19 THEN R ELSE N/A | UEs supporting 5G Core and NR standalone shared spectrum channel access and RSSI measurements and channel occupancy reporting | +| C219 | IF A.4.1-5/1 AND A.4.3.13-1/1 THEN R ELSE N/A | UEs supporting 5G Core and Multi-SIM features | +| C220 | IF A.4.1-5/1 AND A.4.3.13-1/4 THEN R ELSE N/A | UEs supporting 5G Core and Multi-SIM Reject paging request | +| C221 | IF A.4.1-5/1 AND (A.4.1-4A/1 OR A.4.1-4A/3) AND A.4.3.7-1/19 AND A.4.3.5-1/15 AND A.4.1-4/6 THEN R ELSE N/A | UEs supporting 5G Core and intra-band contiguous CA and RRC_INACTIVE and direct NR SCG SCell activation and NR-DC | +| C222 | IF A.4.1-5/1 AND (A.4.1-4A/2 OR A.4.1-4A/4) AND A.4.3.7-1/19 AND A.4.3.5-1/15 AND A.4.1-4/6 THEN R ELSE N/A | UEs supporting 5G Core and intra-band non-contiguous CA and RRC_INACTIVE and direct NR SCG SCell activation and NR-DC | +| C223 | IF A.4.1-5/1 AND (A.4.1-4A/5 OR A.4.1-4A/6) AND A.4.3.7-1/19 AND A.4.3.5-1/15 AND A.4.1-4/6 THEN R ELSE N/A | UEs supporting 5G Core and inter-band CA and RRC_INACTIVE and direct NR SCG SCell activation and NR-DC | +| C224 | IF A.4.1-5/1 AND A.4.3.7-1/42 THEN R ELSE N/A | UEs supporting 5G Core and PEI | +| C224A | IF A.4.1-5/1 AND A.4.3.7-1/42 AND A.4.3.7-1/61 THEN R ELSE N/A | UEs supporting 5G Core and PEI and PEIPS | +| C225 | IF A.4.1-3/2 AND (A.4.3.6-1/61 OR A.4.3.6-1/62) THEN R ELSE N/A | UEs supporting EN-DC and Idle/Inactive Measurements | +| C226 | IF A.4.1-5/1 AND A.4.3.5-1/13 AND (A.4.1-4A/1 OR A.4.1- | UEs supporting 5G Core and direct NR MCG SCell activation and | + +| Condition | Test case Selection Expression | Comment | +|-----------|-----------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 4A/3) THEN R ELSE N/A | intra-band contiguous CA | +| C227 | IF A.4.1-5/1 AND A.4.3.5-1/13 AND (A.4.1-4A/2 OR A.4.1-4A/4) THEN R ELSE N/A | UEs supporting 5G Core and direct NR MCG SCell activation and intra-band non-contiguous CA | +| C228 | IF A.4.1-5/1 AND A.4.3.5-1/13 AND (A.4.1-4A/5 OR A.4.1-4A/6 OR A.4.1-4A/7) THEN R ELSE N/A | UEs supporting 5G Core and direct NR MCG SCell activation and inter-band CA | +| C229 | IF A.4.1-5/1 AND A.4.1-4/6 AND A.4.3.7-1/19 AND A.4.3.7-1/44 THEN R ELSE N/A | UEs supporting 5G Core and NR-DC and RRC_INACTIVE and (re-)configuration of an SCG during the resume procedure. | +| C230 | IF A.4.1-5/1 AND A.4.3.7-1/37 THEN R ELSE N/A | UEs supporting 5G Core and NSSRG | +| C231 | IF A.4.1-5/1 AND A.4.3.7-1/24 AND A.4.3.7-1/40 THEN R ELSE N/A | UEs supporting 5G Core and SNPN and configuration of access identities in the list of subscriber data | +| C232 | IF A.4.3.2-1/46 AND A.4.4-1/14 THEN R ELSE N/A | UEs Supporting 2-Step RACH and Random access SDT | +| C233 | IF A.4.4-1/14 THEN R ELSE N/A | UEs Supporting Random access SDT | +| C234 | Void | | +| C234A | IF [9] A.18/5 AND [9] A.21/3 AND A.4.3.7-1/63 THEN R ELSE N/A | NR and NG.114 and steering of roaming connected mode control information | +| C235 | IF A.4.3.3-1/8 THEN R ELSE N/A | UEs supporting 5GS and uplink data compression operation | +| C236 | IF A.4.3.3-1/8 and A.4.3.3-1/9 THEN R ELSE N/A | UEs supporting 5GS and uplink data compression operation and UL data compression with SIP static dictionary | +| C237 | IF [10] A.4.4-1/117 AND [10] A.4.1-1/5 AND A.4.3.8-1/21 AND A.4.4-1/2 AND A.4.1-5/1 THEN R ELSE N/A | UEs supporting WLAN and GSMA PRD IR.51: "IMS Profile for Voice, Video and SMS over Wi-Fi" and handover from EPC over non-3GPP Access Network to 5G Core and IMS and 5G Core | +| C238 | IF A.4.1-5/1 AND A.4.3.7-1/14 AND [11] A.20/90 THEN R ELSE N/A | UEs supporting 5G Core and emergency services in NR connected to 5GCN and test execution with No USIM | +| C239 | IF A.4.1-5/1 AND A.4.3.7-1/42 AND A.4.3.7-1/19 THEN R ELSE N/A | UEs supporting 5G Core and RRC_INACTIVE and PEI | + +| Condition | Test case Selection Expression | Comment | +|-----------|----------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| C240 | IF A.4.1-5/1 AND A.4.3.7-1/38 THEN R ELSE N/A | UEs supporting 5G Core and slice based cell reselection | +| C241 | IF A.4.1-5/1 AND A.4.3.7-1/19 AND A.4.3.7-1/38 THEN R ELSE N/A | UEs supporting 5G Core and RRC_INACTIVE and slice based cell reselection | +| C242 | IF A.4.1-5/1 AND A.4.3.13-1/2 THEN R ELSE N/A | UEs supporting 5G Core and Multi-SIM N1 NAS signalling connection release | +| C243 | IF A.4.1-5/1 AND A.4.3.2-2/2 AND A.4.3.5-1/17 THEN R ELSE N/A | UEs supporting 5G Core and EN-DC with NR shared spectrum channel access and UL LBT Failure Detection and Recovery | +| C244 | IF A.4.1-5/1 AND A.4.3.2-2/5 AND A.4.3.5-1/17 THEN R ELSE N/A | UEs supporting 5G Core and NR-DC with NR shared spectrum channel access and UL LBT Failure Detection and Recovery | +| C245 | IF A.4.1-5/1 AND A.4.3.13-1/1 AND A.4.3.7-1/29 THEN R ELSE N/A | UEs supporting 5G Core and Multi-SIM features and release preference assistance information | +| C246 | IF A.4.1-5/1 AND A.4.3.13-1/6 THEN R ELSE N/A | UEs supporting 5G Core and MUSIM gap feature. | +| C247 | IF A.4.1-5/1 AND A.4.3.2-2/3 AND A.4.3.7-1/19 THEN R ELSE N/A | UEs supporting 5G Core and NR standalone shared spectrum channel access and RRC_INACTIVE | +| C248 | IF A.4.1-5/1 AND A.4.3.8-1/24 AND [10] A.4.1-1/5 AND THEN R ELSE N/A | UEs supporting 5G Core and handover from 5G Core over non-3GPP Access Network to 5G Core Network and WLAN | +| C249 | IF A.4.1-5/1 AND A.4.3.8-1/23 AND [10] A.4.1-1/5 THEN R ELSE N/A | UEs supporting 5G Core and handover from 5G Core over non-3GPP Access Network to EPC Network and WLAN | +| C250 | IF A.4.1-5/1 AND A.4.4-1/21 THEN R ELSE N/A | UEs supporting 5G Core and storage and delivery of multiple CEF report upon request from the network | +| C251 | IF A.4.1-5/1 AND A.4.1-5/2 AND [10] A.4.1-1/5 AND A.4.3.7-1/9 and A.4.3.7-1/48 THEN R ELSE N/A | UEs supporting 5G Core and 5G core over non-3GPP Access Network and WLAN and additional UE-requested PDU establishment and ATSSS | +| C252 | IF A.4.1-5/1 AND A.4.3.14-1/2 AND A.4.3.14-1/5 THEN R ELSE N/A | UE supporting 5G Core and dynamic scheduling for multicast for PCell and NACK-only based HARQ-ACK feedback for multicast with ACK/NACK transforming | +| C253 | IF A.4.1-5/1 AND A.4.3.14-1/2 AND A.4.3.14-1/3 AND A.4.3.14-1/7 THEN R ELSE N/A | UE supporting 5G Core and dynamic scheduling for multicast for PCell and ACK/NACK based HARQ-ACK feedback and RRC-based enabling/disabling ACK/NACK-based feedback for dynamic scheduling for multicast and multiplexing HARQ-ACK for unicast and for multicast with the same priority and different HARQ-ACK codebook types in a PUCCH or in a PUSCH | +| C254 | IF A.4.1-5/1 AND A.4.3.14-1/2 AND A.4.3.7-1/19 THEN R ELSE N/A | UE supporting 5G Core and dynamic scheduling for multicast for PCell and RRC_INACTIVE | +| C255 | IF A.4.1-3/3 AND A.4.3.7-1/19 AND A.4.3.7-1/44 THEN R ELSE N/A | UEs supporting NE-DC and RRC_INACTIVE and (re-)configuration of an SCG during the resume procedure. | +| C256 | IF A.4.3.5-1/16 AND A.4.1-4/6 AND A.4.3.3-1/4 THEN R ELSE N/A | UEs supporting services with survival time and NR-DC and PDCP-duplication over split DRB | +| C257 | IF A.4.3.5-1/16 AND (A.4.1-4A/1 OR A.4.1-4A/3) AND A.4.3.3-1/3 THEN R ELSE N/A | UEs supporting services with survival time and intra-band contiguous CA and CA-based PDCP duplication over MCG or SCG DRB | +| C258 | IF A.4.3.5-1/16 AND (A.4.1-4A/2 OR A.4.1-4A/4) AND A.4.3.3-1/3 THEN R ELSE N/A | UEs supporting services with survival time and intra-band non-contiguous CA and CA-based PDCP duplication over MCG or SCG DRB | +| C259 | IF A.4.3.5-1/16 AND (A.4.1-4A/5 OR A.4.1-4A/6 OR A.4.1-4A/7) AND A.4.3.3-1/3 THEN R ELSE N/A | UEs supporting services with survival time and inter-band CA and CA-based PDCP duplication over MCG or SCG DRB | +| C260 | IF ([10] A.4.1-1/1 OR [10] A.4.1-1/2) AND A.4.3.7-1/37 AND A.4.3.7-1/64 THEN R ELSE N/A | UEs supporting 5GS and E-UTRA and NSSRG and UE supporting extended rejected NSSAI. | +| C261 | IF A.4.1-5/1 AND A.4.3.7-1/9 AND A.4.3.7-1/14 THEN R ELSE N/A | UEs supporting 5G Core and additional UE-requested PDU establishment and emergency services in NR connected to 5GCN | +| C262 | IF A.4.3.7-1/45 AND A.4.3.7-1/46 THEN R ELSE N/A | UEs supporting slice-based RACH partitioning and slice-based RACH prioritisation | +| C263 | IF A.4.3.7-1/45 AND A.4.3.7-1/46 AND A.4.3.7-1/47 THEN R ELSE N/A | UEs supporting slice-based RACH partitioning, slice-based RACH prioritisation and RACH prioritisation for Access Identity 1 | +| C264 | IF A.4.3.2-1/46 AND A.4.3.7-1/45 AND A.4.3.7-1/46 THEN R ELSE N/A | UEs supporting 2-Step RACH, slice-based RACH partitioning and slice-based RACH prioritisation | +| C265 | IF A.4.3.2-1/46 AND A.4.3.7-1/45 AND A.4.3.7-1/46 AND A.4.3.7-1/47 THEN R ELSE N/A | UEs supporting 2-Step RACH, slice-based RACH partitioning, slice-based RACH prioritisation and RACH prioritisation for Access Identity 1 | +| C266 | IF A.4.1-5/1 AND A.4.4-1/6 AND [10] A.4.1-1/5 AND A.4.3.7-1/67 AND A.4.3.1-2/1b AND A.4.4-2/13 THEN R ELSE N/A | UEs supporting 5G core and logged measurements in RRC_IDLE and RRC_INACTIVE and FR1 Band n40 and WLAN, and reporting of affected NR carrier frequencies in IDC assistance information, and transmitting UEAssistanceInformation message with IDC-Assistance-r16 in RRC_CONNECTED when an IDC problem is detected in RRC_IDLE | +| C267 | IF A.4.1-5/1 AND A.4.4-1/6 AND A.4.4-1/22 THEN R ELSE N/A | UEs supporting 5G core and logged measurements in RRC_IDLE and RRC_INACTIVE and early measurements | +| C268 | IF A.4.1-3/3 AND A.4.3.6-1/75 THEN R ELSE N/A | UEs supporting NE-DC and SFTD measurement between NR PCell and E-UTRA PCell | +| C269 | IF A.4.1-5/1 AND A.4.4-1/16 THEN R ELSE N/A | UEs supporting 5G Core and SDT via Configured Grant Type 1 in RRC_INACTIVE state | +| C270 | Void | | + +| Condition | Test case Selection Expression | Comment | +|-----------|-----------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| C271 | IF A.4.3.3-1/8 and A.4.3.3-1/10 THEN R ELSE N/A | UEs supporting 5GS and uplink data compression operation and continuation of uplink data compression protocol operation | +| C272 | IF A.4.1-4/6 and A.4.3.3-1/8 THEN R ELSE N/A | UEs supporting NR-DC and uplink data compression operation | +| C273 | IF A.4.1-3/3 and A.4.3.3-1/8 THEN R ELSE N/A | UEs supporting NE-DC and uplink data compression operation | +| C274 | IF A.4.1-5/1 AND A.4.4-1/26 THEN R ELSE N/A | UEs supporting 5G Core and RRC Connection release with MPS priority indication | +| C274A | IF A.4.1-5/1 AND A.4.4-1/26 AND A.4.3.7-1/19 THEN R ELSE N/A | UEs supporting 5G Core and RRC Connection release with MPS priority indication AND RRC_INACTIVE | +| C275 | IF A.4.1-5/1 AND A.4.1-5/2 AND [10] A.4.1-1/5 AND A.4.3.7-1/13 and A.4.3.7-1/48 THEN R ELSE N/A | UEs supporting 5G Core and 5G core over non-3GPP Access Network and WLAN and UE-requested PDU modification and ATSSS | +| C276 | IF A.4.1-5/1 AND A.4.3.8-1/25 AND [10] A.4.1-1/5 AND THEN R ELSE N/A | UEs supporting 5G Core and handover from 5G Core Network to 5G Core over non-3GPP Access Network and WLAN | +| C277 | IF A.4.1-5/1 AND A.4.3.8-1/22 AND [10] A.4.1-1/5 THEN R ELSE N/A | UEs supporting 5G Core and handover from EPC Network to 5G Core over non-3GPP Access Network and WLAN | +| C278 | IF A.4.1-5/1 AND A.4.4-1/24 THEN R ELSE N/A | UEs supporting 5G Core and delivery of delivery of 2-step RACH related information upon request from the network | +| C279 | IF A.4.1-5/1 AND A.4.4-1/25 THEN R ELSE N/A | UEs supporting 5G Core and delivery of delivery of 2-step RACH related information upon request from the network. | +| C280 | IF A.4.1-5/1 AND A.4.3.14-1/11 AND (A.4.1-4A/1 OR A.4.1-4A/3) THEN R ELSE N/A | UE supporting 5G Core and broadcast reception on SCell and Intra-band Contiguous CA | +| C281 | IF A.4.1-5/1 AND A.4.3.14-1/11 AND (A.4.1-4A/5 OR A.4.1-4A/6 OR A.4.1-4A/7) THEN R ELSE N/A | UE supporting 5G Core and broadcast reception on SCell and Inter-band CA | +| C282 | IF A.4.1-5/1 AND A.4.3.14-1/11 AND (A.4.1-4A/2 OR A.4.1-4A/4) THEN R ELSE N/A | UE supporting 5G Core and broadcast reception on SCell and Intra-band non Contiguous CA | +| C283 | IF A.4.1-5/1 AND A.4.3.14-1/2 AND A.4.3.14-1/8 THEN R ELSE N/A | UE supporting 5G Core and dynamic scheduling for multicast for PCell and DCI format 4_2 | +| C284 | IF A.4.1-5/1 AND A.4.3.14-1/2 AND A.4.3.14-1/8 AND A.4.3.14-1/9 THEN R ELSE N/A | UE supporting 5G Core and dynamic scheduling for multicast for PCell and DCI format 4-2 and DCI-based enabling/disabling ACK/NACK based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2 | +| C285 | IF A.4.1-5/1 AND A.4.3.14-1/2 AND A.4.3.14-1/8 AND A.4.3.14-1/10 THEN R ELSE N/A | UE supporting 5G Core and dynamic scheduling for multicast for PCell and DCI format 4-2 and DCI-based enabling/disabling NACK-only based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2 | +| C286 | IF A.4.1-3/2 AND A.4.3.7-1/50 THEN R ELSE N/A | UEs supporting EN-DC and user plane integrity protection with EPS | +| C287 | IF A.4.3.2-1/114 THEN R ELSE N/A | UEs supporting dynamic indication of PUCCH repetition | +| C288 | IF A.4.3.2-1/115 AND A.4.3.2-1/113 THEN R ELSE N/A | UEs supporting increased maximum number of PUSCH Type A repetitions and dynamic indication of the number of repetitions for PUSCH | +| C289 | IF A.4.3.2-1/115 AND (A.4.3.2-1/111 OR A.4.3.2-1/112) THEN R ELSE N/A | UEs supporting increased maximum number of PUSCH Type A repetitions and PUSCH transmissions with configured grant | +| C290 | IF A.4.3.2-1/116 AND A.4.3.2-1/113 THEN R ELSE N/A | UEs supporting PUSCH repetitions based on available slots and dynamic indication of the number of repetitions for PUSCH | +| C291 | IF A.4.3.2-1/116 AND (A.4.3.2-1/111 OR A.4.3.2-1/112) THEN R ELSE N/A | UEs supporting PUSCH repetitions based on available slots and PUSCH transmissions with configured grant | +| C292 | IF A.4.3.2-1/117 THEN R ELSE N/A | UEs supporting TB processing over multi-slot PUSCH | +| C293 | IF A.4.3.2-1/118 THEN R ELSE N/A | UEs supporting repetition of TB processing over multi-slot PUSCH | +| C294 | IF A.4.1-5/1 AND A.4.3.13-1/1 AND A.4.3.13-1/6 AND A.4.3.13-1/7 THEN R ELSE N/A | UEs supporting 5G Core and Multi-SIM features and MUSIM related assistance information | +| C295 | IF A.4.1-5/1 AND A.4.3.14-1/2 AND A.4.3.14-1/16 THEN R ELSE N/A | UE supporting 5G Core and dynamic scheduling for multicast for PCell and Multiple G-RNTIs. | +| C296 | IF A.4.1-5/1 AND A.4.3.14-1/2 AND A.4.3.14-1/12 THEN R ELSE N/A | UE supporting 5G Core and dynamic scheduling for multicast for PCell and SPS group-common PDSCH for multicast on PCell. | +| C297 | IF A.4.1-5/1 AND A.4.3.14-1/2 AND A.4.3.14-1/12 AND A.4.3.14-1/13 THEN R ELSE N/A | UE supporting 5G Core and dynamic scheduling for multicast for PCell and SPS group-common PDSCH for multicast on PCell and ACK/NACK based HARQ-ACK feedback and RRC-based enabling/disabling ACK/NACK-based feedback for SPS group-common PDSCH for multicast. | +| C298 | IF A.4.1-5/1 AND A.4.3.14-1/2 AND A.4.3.14-1/12 AND A.4.3.14-1/13 AND A.4.3.14-1/14 THEN R ELSE N/A | UE supporting 5G Core and dynamic scheduling for multicast for PCell and SPS group-common PDSCH for multicast on PCell and ACK/NACK based HARQ-ACK feedback and RRC-based enabling/disabling ACK/NACK-based feedback for SPS group-common PDSCH for multicast and PTP retransmission associated with CS-RNTI for SPS multicast on the cell same as multicast initial transmission. | +| C299 | IF A.4.1-5/1 AND A.4.3.14-1/2 AND A.4.3.14-1/12 AND A.4.3.14-1/15 THEN R ELSE N/A | UE supporting 5G Core and dynamic scheduling for multicast for PCell and SPS group-common PDSCH for multicast on PCell and unicast PDCCH scrambled with CS-RNTI to release SPS group-common PDSCH. | +| C300 | IF A.4.1-5/1 AND A.4.3.2-2/1 AND A.4.3.2A.1-2/1 AND A.4.3.5-1/17 THEN R ELSE N/A | UEs supporting 5G Core and NR CA with NR shared spectrum channel access and UL NR CA with 2 carriers and UL LBT | + +| Condition | Test case Selection Expression | Comment | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | Failure Detection and Recovery | +| C301 | IF A.4.1-5/1 AND A.4.4-1/27 THEN R ELSE N/A | UEs supporting 5G Core and RLF-Report for conditional handover | +| C302 | IF A.4.1-5/1 AND A.4.4-1/28 THEN R ELSE N/A | UEs supporting 5G Core and RLF-Report for DAPS handover. | +| C303 | IF A.4.1-5/1 AND A.4.4-1/29 THEN R ELSE N/A | UEs supporting 5G Core and the storage and delivery of Successful Handover Report. | +| C304 | IF A.4.1-5/1 AND A.4.3.7-1/52 THEN R ELSE N/A | UEs supporting 5G Core and access SNPN using credentials assigned by a Credentials Holder separate from the SNPN | +| C305 | IF A.4.1-5/1 AND A.4.3.7-1/53 THEN R ELSE N/A | UEs supporting 5G Core and onboarding services in SNPN(hence supports Default UE Credentials) | +| C306 | IF A.4.1-5/1 AND A.4.3.7-1/56 THEN R ELSE N/A | UEs supporting 5G Core and emergency services in SNPN | +| C307 | IF A.4.1-5/1 AND A.4.3.7-1/52 AND A.4.3.7-1/30 THEN R ELSE N/A | UEs supporting 5G Core and accessing SNPN using credentials from a Credentials Holder and user initiated SNPN reselection in automatic mode on NR. | +| C308 | IF A.4.1-5/1 AND A.4.3.7-1/56 AND A.4.3.7-1/57 AND A.4.3.7-1/32 THEN R ELSE N/A | UEs supporting 5G Core and PLMN access in SNPN Access mode and emergency services in NR connected to 5GCN in SNPN Access mode And IMS voice over NR | +| C309 | IF A.4.1-5/1 AND A.4.4-1/17 THEN R ELSE N/A | UEs supporting 5G Core and NR NTN access | +| C310 | IF A.4.1-5/1 AND A.4.3.7-1/51 THEN R ELSE N/A | UEs supporting 5G Core and UAS | +| C311 | IF A.4.3.2-1/123 THEN R ELSE N/A | UEs supporting 5GS and unified TCI state operation with joint DL/UL TCI update for intra-cell beam management | +| C312 | IF A.4.3.2-1/133 THEN R ELSE N/A | UEs supporting 5GS and unified separate TCI with multi-MAC-CE | +| C313 | IF A.4.1-5/1 AND A.4.3.7-1/59 THEN R ELSE N/A | UEs supporting 5G Core and MICO mode | +| C314 | IF A.4.1-5/1 AND ([10] A.4.1-1/1 OR [10] A.4.1-1/2) AND A.4.4-1/26 THEN R ELSE N/A | UEs supporting 5G Core and E-UTRA and RRC Connection release with MPS priority indication | +| C315 | IF A.4.1-5/1 AND A.4.3.2-1/134 THEN R ELSE N/A | UEs supporting 5G Core and partial frequency sounding for SRS with frequency hopping. | +| C316 | Void | | +| C317 | IF A.4.1-5/1 AND A.4.4-1/16 AND A.4.3.7-1/6 THEN R ELSE N/A | UEs supporting 5G Core and SDT via Configured Grant Type 1 in RRC_INACTIVE state and SMS over NAS | +| C318 | IF A.4.1-5/1 AND A.4.3.2-2/1 THEN R ELSE N/A | UEs supporting 5G Core and NR CA with NR shared spectrum channel access | +| C319 | IF A.4.1-5/1 AND ([10] A.4.1-1/1 OR [10] A.4.1-1/2) AND A.4.1-5/2 AND [10] A.4.1-1/5 AND A.4.3.7-1/13 AND A.4.3.7-1/60 THEN R ELSE N/A | UEs supporting 5G Core and E-UTRA and 5G core over non-3GPP Access Network and WLAN and R17 ATSSS of establishing a PDN connection as the user plane resource of an MA PDU session in 5GS | +| C320 | IF A.4.1-5/1 AND ([10] A.4.1-1/1 OR [10] A.4.1-1/2) AND A.4.1-5/2 AND [10] A.4.1-1/5 AND A.4.3.7-1/13 AND A.4.3.7-1/48 THEN R ELSE N/A | UEs supporting 5G Core and E-UTRA and 5G core over non-3GPP Access Network and WLAN and R16 ATSSS | +| C321 | IF A.4.1-5/1 AND A.4.4-1/17 AND A.4.3.2-1/138 AND A.4.3.2-1/141 THEN R ELSE N/A | UEs supporting 5G Core and NR NTN access and UE reporting of information related to TA pre-compensation and reception of UE-specific K_offset | +| C322 | IF A.4.1-5/1 AND A.4.4-1/17 AND (A.4.3.4-1/2 OR A.4.3.4-1/3) THEN R ELSE N/A | UEs supporting 5G Core and NR NTN access and RLC UM Mode | +| C323 | IF A.4.1-5/1 AND A.4.4-1/17 AND A.4.3.6-1/76 AND A.4.3.2-1/92 THEN R ELSE N/A | UE supporting 5G Core and NR NTN access and UE supporting location-based triggered measurement reporting (i.e., event D1) and NTN features in NGSO scenario | +| C324 | IF A.4.1-5/1 AND ([10] A.4.1-1/1 OR [10] A.4.1-1/2) AND A.4.3.7-1/58 AND A.4.3.7-1/66 THEN R ELSE N/A | UEs supporting 5G Core and E-UTRA and No E-UTRA Disabling In 5GS and disabling E-UTRA capability when attach attempt counter or tracking area updating attempt counter is equal to 5 | +| C325 | IF A.4.1-5/1 AND [9] A.12/5 THEN R ELSE N/A | UEs supporting 5G Core and capable of being configured to initiate P-CSCF Discovery via PCO | +| C326 | IF A.4.1-5/1 AND ([10] A.4.1-1/1 OR [10] A.4.1-1/2) AND A.4.3.7-1/9 AND A.4.3.7-1/48 | UEs supporting 5G Core and E-UTRA and additional UE-requested PDU establishment and ATSSS | +| C327 | IF A.4.1-5/1 AND A.4.1-5/2 AND ([10] A.4.1-1/1 OR [10] A.4.1-1/2) AND [10] A.4.1-1/5 AND A.4.3.7-1/9 AND A.4.3.7-1/48 | UEs supporting 5G Core and 5G core over non-3GPP Access Network and E-UTRA and WLAN and additional UE-requested PDU establishment and ATSSS | +| C328 | IF A.4.1-5/1 AND A.4.4-1/15 AND A.4.4-1/16 AND A.4.3.7-1/6 THEN R ELSE N/A | UEs supporting 5G Core and SRB SDT and SDT via Configured Grant Type 1 in RRC_INACTIVE state and SMS over NAS | +| C329 | IF A.4.1-5/1 AND A.4.3.7-1/64 THEN R ELSE N/A | UEs supporting 5G Core and UE supporting extended rejected NSSAI | +| C330 | IF A.4.3.2-1/143 THEN R ELSE N/A | UEs supporting 5GS and multi-TRP PUSCH repetition type A | +| C331 | IF A.4.3.2-1/144 THEN R ELSE N/A | UEs supporting 5GS and multi-TRP PUSCH repetition type B | +| C332 | IF A.4.1-5/1 AND A.4.3.12-1/2 AND A.4.3.12-1/5 THEN R ELSE N/A | UEs supporting 5G Core and RedCap and halfDuplexFDD | +| C333 | IF A.4.1-5/1 AND A.4.4-1/17 AND A.4.3.6-1/84 AND A.4.3.2-1/92 THEN R ELSE N/A | UEs supporting 5G Core and NR NTN access and Location-based measurement initiation for NTN while in RRC_IDLE/RRC_INACTIVE and NTN features in NGSO scenario | +| C334 | IF A.4.1-5/1 AND A.4.4-1/17 AND A.4.3.6-1/83 AND A.4.3.2-1/92 THEN R ELSE N/A | UEs supporting 5G Core and NR NTN access and Time-based measurement initiation for NTN while in RRC_IDLE/RRC_INACTIVE and NTN features in NGSO scenario | + +| Condition | Test case Selection Expression | Comment | +|-----------|------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| C335 | IF A.4.1-5/1 AND A.4.4-1/17 AND A.4.3.8-1/36 THEN R
ELSE N/A | UEs supporting 5G Core and NR NTN access and Event A4 based conditional handover in NTN bands | +| C336 | IF A.4.1-5/1 AND A.4.4-1/17 AND A.4.3.8-1/27 THEN R
ELSE N/A | UEs supporting 5G Core and NR NTN access and time based conditional handover | +| C337 | IF A.4.1-5/1 AND A.4.4-1/17 AND A.4.3.8-1/26 AND A.4.3.2-1/92 THEN R ELSE N/A | UEs supporting 5G Core and NR NTN access and location based conditional handover and NTN features in NGSO scenario | +| C338 | IF A.4.1-5/1 AND A.4.3.7-1/52 AND A.4.3.7-1/62 THEN R
ELSE N/A | UEs supporting 5G Core and access SNPN using credentials assigned by a Credentials Holder separate from the SNPN and steering of roaming SNPN selection information | +| C339 | IF A.4.1-5/1 AND A.4.3.7-1/52 AND A.4.3.7-1/63 THEN R
ELSE N/A | UEs supporting 5G Core and access SNPN using credentials assigned by a Credentials Holder separate from the SNPN and Steering of Roaming Connected Mode Control Information | +| C340 | IF A.4.1-5/1 AND A.4.3.7-1/52 AND A.4.3.7-1/56 AND A.4.3.7-1/63 THEN R ELSE N/A | UEs supporting 5G Core and access SNPN using credentials assigned by a Credentials Holder separate from the SNPN and emergency services in NR connected to 5GCN in SNPN Access mode and Steering of Roaming Connected Mode Control Information | +| C341 | IF A.4.1-5/1 AND A.4.3.7-1/52 AND A.4.3.7-1/53 THEN R
ELSE N/A | UEs supporting 5G Core and accessing SNPN using credentials assigned by a Credentials Holder separate from the SNPN and Onboarding SNPN (hence supports Default UE Credentials) | +| C342 | IF A.4.1-5/1 AND A.4.3.10-1/24 THEN R ELSE N/A | UE supporting 5G core and NR L2 sidelink remote UE operation | +| C343 | IF A.4.1-5/1 AND A.4.3.10-1/23 THEN R ELSE N/A | UE supporting 5G core and NR L2 sidelink relay UE operation | +| C344 | IF A.4.1-5/1 AND ([10] A.4.1-1/1 OR [10] A.4.1-1/2) AND [10] A.4.4-1/248 THEN R ELSE N/A | UEs supporting 5G Core and E-UTRA and RRC Connection release with MPS priority indication | +| C345 | IF A.4.1-5/1 AND A.4.3.1-2/1b AND A.4.3.1-2/2 AND [10] A.4.1-1/5 AND A.4.3.7-1/67 THEN R ELSE N/A | UEs supporting 5G core and FR1 Band n40 and FR1 Band n41 and WLAN and reporting affected NR carrier frequencies in IDC assistance information when detecting IDC problem. | +| C346 | IF A.4.1-5/1 AND A.4.4-1/17 AND A.4.3.6-1/84 AND A.4.3.7-1/19 AND A.4.3.2-1/92 THEN R ELSE N/A | UEs supporting 5G Core and NR NTN access and Location-based measurement initiation for NTN while in RRC_IDLE/RRC_INACTIVE and RRC_INACTIVE and NTN features in NGSO scenario | +| C347 | IF A.4.1-5/1 AND A.4.4-1/17 AND A.4.3.6-1/83 AND A.4.3.7-1/19 AND A.4.3.2-1/92 THEN R ELSE N/A | UEs supporting 5G Core and NR NTN access and Time-based measurement initiation for NTN while in RRC_IDLE/RRC_INACTIVE and RRC_INACTIVE and NTN features in NGSO scenario | +| C348 | IF A.4.1-5/1 AND A.4.4-1/17 AND (A.4.3.5-1/20 OR A.4.3.5-1/18) THEN R ELSE N/A | UEs supporting 5G Core and NR NTN access and ((HARQ Mode B and the corresponding LCP restrictions for uplink transmission) or (disabled HARQ feedback for downlink transmission)) | +| C349 | IF A.4.1-5/1 AND A.4.3.15-1/1 THEN R ELSE N/A | UEs supporting 5G Core and NR QoE Measurement Collection for MTSI services | +| C350 | IF A.4.1-5/1 AND A.4.3.15-1/1 AND [9] A.15/3 THEN R
ELSE N/A | UEs supporting 5G Core and NR QoE Measurement Collection for MTSI services and MTSI video | +| C351 | IF A.4.3.2-1/160 THEN R ELSE N/A | UEs supporting 5GS and PRACH repetition | +| C352 | IF A.4.1-5/1 AND A.4.3.5-1/22 THEN R ELSE N/A | UEs supporting 5G Core and delay status reporting | +| C353 | IF A.4.1-5/1 AND A.4.3.5-1/23 THEN R ELSE N/A | UEs supporting 5G Core and non-integer DRX cycle | +| C354 | IF A.4.1-5/1 AND A.4.3.2-1/10 AND A.4.3.2-1/159 THEN R
ELSE N/A | UEs supporting 5G Core and Type 1 PUSCH transmissions with configured grant and multi-PUSCHs for configured grant | +| C355 | IF A.4.1-5/1 AND A.4.3.2-1/11 AND A.4.3.2-1/159 THEN R
ELSE N/A | UEs supporting 5G Core and Type 2 PUSCH transmissions with configured grant and multi-PUSCHs for configured grant | +| C356 | IF A.4.1-5/1 AND A.4.3.2-1/161 THEN R ELSE N/A | UEs supporting 5G Core and is 2Rx XR UE | +| C357 | IF A.4.1-5/1 AND A.4.3.5-1/21 THEN R ELSE N/A | UEs supporting 5G Core and using the refined buffer size table for BSR | +| C358 | IF A.4.1-5/1 AND A.4.3.5-1/1 AND A.4.3.2-1/187 THEN R
ELSE N/A | UEs supporting 5G Core and Long DRX Cycle and Cell DTX operation by RRC configuration | +| C359 | IF A.4.1-5/1 AND A.4.3.5-1/1 AND A.4.3.2-1/189 AND A.4.3.2-1/187 THEN R ELSE N/A | UEs supporting 5G Core and Long DRX Cycle and Cell DTX configuration activation and deactivation via DCI 2_9 | +| C360 | IF A.4.1-5/1 AND A.4.3.2-1/188 THEN R ELSE N/A | UEs supporting 5G Core and Cell DRX operation by RRC configuration | +| C361 | IF A.4.1-5/1 AND A.4.3.2-1/189 AND A.4.3.2-1/188 THEN R
ELSE N/A | UEs supporting 5G Core and Cell DRX configuration activation and deactivation via DCI 2_9 | +| C362 | IF (A.4.1-4A/1 OR A.4.1-4A/3) AND A.4.3.2A.1-1/1 AND A.4.3.2-1/162 AND A.4.3.2-1/164 THEN R ELSE N/A | UEs supporting 5G Core and intra-band contiguous CA and DL NR CA with 2 carriers and DCI format 1_3 with same SCS between scheduling cell and cells in the set and co-scheduled cell indication scheme based on FDRA field of DCI format 1_3 | +| C363 | IF (A.4.1-4A/5 OR A.4.1-4A/6) AND A.4.3.2A.1-1/1 AND A.4.3.2-1/162 AND A.4.3.2-1/164 THEN R ELSE N/A | UEs supporting 5G Core and inter-band CA and DL NR CA with 2 carriers and DCI format 1_3 with same SCS between scheduling cell and cells in the set and co-scheduled cell indication scheme based on FDRA field of DCI format 1_3 | +| C364 | IF (A.4.1-4A/2 OR A.4.1-4A/4) AND A.4.3.2A.1-1/1 AND A.4.3.2-1/162 AND A.4.3.2-1/164 THEN R ELSE N/A | UEs supporting 5G Core and intra-band non-contiguous CA and DL NR CA with 2 carriers and DCI format 1_3 with same SCS between scheduling cell and cells in the set and co-scheduled cell indication scheme based on FDRA field of DCI format 1_3 | +| C365 | IF (A.4.1-4A/1 OR A.4.1-4A/3) AND A.4.3.2A.1-1/1 AND A.4.3.2-1/162 AND A.4.3.2-1/165 THEN R ELSE N/A | UEs supporting 5G Core and intra-band contiguous CA and DL NR CA with 2 carriers and DCI format 1_3 with same SCS | + +| Condition | Test case Selection Expression | Comment | +|-----------|------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | between scheduling cell and cells in the set and co-scheduled cell indication scheme based on Scheduled cells indicator field of DCI format 1_3 | +| C366 | IF (A.4.1-4A/5 OR A.4.1-4A/6) AND A.4.3.2A.1-1/1 AND A.4.3.2-1/162 AND A.4.3.2-1/165 THEN R ELSE N/A | UEs supporting 5G Core and inter-band CA and DL NR CA with 2 carriers and DCI format 1_3 with same SCS between scheduling cell and cells in the set and co-scheduled cell indication scheme based on Scheduled cells indicator field of DCI format 1_3 | +| C367 | IF (A.4.1-4A/2 OR A.4.1-4A/4) AND A.4.3.2A.1-1/1 AND A.4.3.2-1/162 AND A.4.3.2-1/165 THEN R ELSE N/A | UEs supporting 5G Core and intra-band non-contiguous CA and DL NR CA with 2 carriers and DCI format 1_3 with same SCS between scheduling cell and cells in the set and co-scheduled cell indication scheme based on Scheduled cells indicator field of DCI format 1_3 | +| C368 | IF (A.4.1-4A/1 OR A.4.1-4A/3) AND A.4.3.2A.1-1/1 AND A.4.3.2-1/162 THEN R ELSE N/A | UEs supporting 5G Core and intra-band contiguous CA and DL NR CA with 2 carriers and DCI format 1_3 with same SCS between scheduling cell and cells in the set | +| C369 | IF (A.4.1-4A/5 OR A.4.1-4A/6) AND A.4.3.2A.1-1/1 AND A.4.3.2-1/162 THEN R ELSE N/A | UEs supporting 5G Core and inter-band CA and DL NR CA with 2 carriers and DCI format 1_3 with same SCS between scheduling cell and cells in the set | +| C370 | IF (A.4.1-4A/2 OR A.4.1-4A/4) AND A.4.3.2A.1-1/1 AND A.4.3.2-1/162 THEN R ELSE N/A | UEs supporting 5G Core and intra-band non-contiguous CA and DL NR CA with 2 carriers and DCI format 1_3 with same SCS between scheduling cell and cells in the set | +| C371 | IF (A.4.1-4A/1 OR A.4.1-4A/3) AND A.4.3.2A.1-2/1 AND A.4.3.2-1/163 THEN R ELSE N/A | UEs supporting 5G Core and intra-band contiguous CA and UL NR CA with 2 carriers and DCI format 0_3 with same SCS between scheduling cell and cells in the set | +| C372 | IF (A.4.1-4A/5 OR A.4.1-4A/6) AND A.4.3.2A.1-2/1 AND A.4.3.2-1/163 THEN R ELSE N/A | UEs supporting 5G Core and inter-band CA and UL NR CA with 2 carriers and DCI format 0_3 with same SCS between scheduling cell and cells in the set | +| C373 | IF (A.4.1-4A/2 OR A.4.1-4A/4) AND A.4.3.2A.1-2/1 AND A.4.3.2-1/163 THEN R ELSE N/A | UEs supporting 5G Core and intra-band non-contiguous CA and UL NR CA with 2 carriers and DCI format 0_3 with same SCS between scheduling cell and cells in the set | +| C374 | IF (A.4.1-4A/1 OR A.4.1-4A/3) AND A.4.3.2A.1-1/1 AND A.4.3.2-1/162 AND A.4.3.2-1/168 THEN R ELSE N/A | UEs supporting 5G Core and intra-band contiguous CA and DL NR CA with 2 carriers and DCI format 1_3 with same SCS between scheduling cell and cells in the set and search space set configurations for DCI format 1_3 for the set of cells with the same searchSpaceId are provided on both the scheduling cell and a serving cell in the set of cells with the scheduling cell being in the set of cells. | +| C375 | IF (A.4.1-4A/5 OR A.4.1-4A/6) AND A.4.3.2A.1-1/1 AND A.4.3.2-1/162 AND A.4.3.2-1/168 THEN R ELSE N/A | UEs supporting 5G Core and inter-band CA and DL NR CA with 2 carriers and DCI format 1_3 with same SCS between scheduling cell and cells in the set and search space set configurations for DCI format 1_3 for the set of cells with the same searchSpaceId are provided on both the scheduling cell and a serving cell in the set of cells with the scheduling cell being in the set of cells. | +| C376 | IF (A.4.1-4A/2 OR A.4.1-4A/4) AND A.4.3.2A.1-1/1 AND A.4.3.2-1/162 AND A.4.3.2-1/168 THEN R ELSE N/A | UEs supporting 5G Core and intra-band non-contiguous CA and DL NR CA with 2 carriers and DCI format 1_3 with same SCS between scheduling cell and cells in the set and search space set configurations for DCI format 1_3 for the set of cells with the same searchSpaceId are provided on both the scheduling cell and a serving cell in the set of cells with the scheduling cell being in the set of cells. | +| C377 | IF (A.4.1-4A/1 OR A.4.1-4A/3) AND A.4.3.2A.1-2/1 AND A.4.3.2-1/163 AND A.4.3.2-1/169 THEN R ELSE N/A | UEs supporting 5G Core and intra-band contiguous CA and UL NR CA with 2 carriers and DCI format 0_3 with same SCS between scheduling cell and cells in the set and search space set configurations for DCI format 0_3 for the set of cells with the same searchSpaceId are provided on both the scheduling cell and a serving cell in the set of cells with the scheduling cell being in the set of cells. | +| C378 | IF (A.4.1-4A/5 OR A.4.1-4A/6) AND A.4.3.2A.1-2/1 AND A.4.3.2-1/163 AND A.4.3.2-1/169 THEN R ELSE N/A | UEs supporting 5G Core and inter-band CA and UL NR CA with 2 carriers and DCI format 0_3 with same SCS between scheduling cell and cells in the set and search space set configurations for DCI format 0_3 for the set of cells with the same searchSpaceId are provided on both the scheduling cell and a serving cell in the set of cells with the scheduling cell being in the set of cells. | +| C379 | IF (A.4.1-4A/2 OR A.4.1-4A/4) AND A.4.3.2A.1-2/1 AND A.4.3.2-1/163 AND A.4.3.2-1/169 THEN R ELSE N/A | UEs supporting 5G Core and intra-band non-contiguous CA and UL NR CA with 2 carriers and DCI format 0_3 with same SCS between scheduling cell and cells in the set and search space set configurations for DCI format 0_3 for the set of cells with the same searchSpaceId are provided on both the scheduling cell and a serving cell in the set of cells with the scheduling cell being in the set of cells. | +| C380 | IF A.4.1-5/1 AND A.4.3.12A-1/1 THEN R ELSE N/A | UEs supporting 5G Core and eRedCap | +| C381 | IF A.4.1-5/1 AND A.4.3.12A-1/1 AND A.4.3.7-1/14 THEN R | UEs supporting 5G Core and eRedCap and emergency services | + +| Condition | Test case Selection Expression | Comment | +|-----------|--------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | ELSE N/A | in NR connected to 5GCN | +| C382 | IF A.4.1-5/1 AND A.4.3.7-1/43 AND A.4.3.7-1/69 AND A.4.3.7-1/19 THEN R ELSE N/A | UEs supporting 5G Core and eDRX in RRC_IDLE and eDRX in RRC_INACTIVE with values above 1024 radio frames and RRC_INACTIVE | +| C383 | IF A.4.1-5/1 AND A.4.3.7-1/43 AND A.4.3.7-1/69 AND A.4.3.7-1/68 AND A.4.3.7-1/19 THEN R ELSE N/A | UEs supporting 5G Core and eDRX in RRC_IDLE and eDRX in RRC_INACTIVE with values above 1024 radio frames and eDRX in RRC_INACTIVE with values of 256, 512 and 1024 radio frames and RRC_INACTIVE | +| C384 | IF A.4.1-5/1 AND A.4.3.13-1/9 AND A.4.3.13-1/10 THEN R ELSE N/A | UEs supporting 5G Core and providing MUSIM assistance information with temporary capability restriction and capability restriction indication and Indicating to the Network A that its capabilities are temporarily restricted in RRCSetupComplete message while the UE is already in RRC_CONNECTED state in Network B. | +| C385 | IF A.4.1-5/1 AND A.4.4-1/16 THEN R ELSE N/A | UEs supporting 5G Core and MT SDT via Configured Grant Type 1 in RRC_INACTIVE state | +| C386 | IF A.4.1-5/1 AND (A.4.1-4A/1 OR A.4.1-4A/3) AND A.4.3.2A.1-2/1 AND A.4.3.2-1/163 AND A.4.3.2-1/166 THEN R ELSE N/A | UEs supporting 5G Core and intra-band contiguous CA and UL NR CA with 2 carriers and DCI format 0_3 with same SCS between scheduling cell and cells in the set and co-scheduled cell indication scheme based on FDRA field of DCI format 0_3 | +| C387 | IF A.4.1-5/1 AND (A.4.1-4A/5 OR A.4.1-4A/6) AND A.4.3.2A.1-2/1 AND A.4.3.2-1/163 AND A.4.3.2-1/166 THEN R ELSE N/A | UEs supporting 5G Core and inter-band CA and UL NR CA with 2 carriers and DCI format 0_3 with same SCS between scheduling cell and cells in the set and co-scheduled cell indication scheme based on FDRA field of DCI format 0_3 | +| C388 | IF A.4.1-5/1 AND (A.4.1-4A/2 OR A.4.1-4A/4) AND A.4.3.2A.1-2/1 AND A.4.3.2-1/163 AND A.4.3.2-1/166 THEN R ELSE N/A | UEs supporting 5G Core and intra-band non-contiguous CA and UL NR CA with 2 carriers and DCI format 0_3 with same SCS between scheduling cell and cells in the set and co-scheduled cell indication scheme based on FDRA field of DCI format 0_3 | +| C389 | IF A.4.1-5/1 AND A.4.3.12A-1/1 AND A.4.3.7-1/19 THEN R ELSE N/A | UEs supporting 5G Core and eRedCap and RRC_INACTIVE | +| C390 | IF A.4.1-5/1 AND A.4.1-1/3 AND A.4.3.10-1/25 THEN R ELSE N/A | UE supporting 5G Core and NR sidelink and SL-MIMO | +| C391 | IF A.4.1-5/1 AND A.4.3.10-1/1 AND A.4.3.10-1/25 THEN R ELSE N/A | UE supporting 5G Core and NR sidelink mode 1 transmission and SL-MIMO | +| C392 | IF A.4.1-5/1 AND A.4.3.7-1/19 AND A.4.3.13-1/9 AND A.4.3.13-1/11 THEN R ELSE N/A | UEs supporting 5G Core and RRC_INACTIVE and providing MUSIM assistance information with temporary capability restriction and capability restriction indication and Indicating to the Network A that its capabilities are temporarily restricted in RRCResumeComplete message while the UE is already in RRC_CONNECTED state in Network B. | +| C393 | IF A.4.1-5/1 AND A.4.3.13-1/9 AND A.4.3.13-1/12 THEN R ELSE N/A | UEs supporting 5G Core and providing MUSIM assistance information with temporary capability restriction and capability restriction indication and Transmitting R18 MUSIM related UEAssistanceInformation message once the UE is allowed to do so after triggered by RRCReconfiguration | +| C394 | IF A.4.1-5/1 AND A.4.3.10-1/23 AND A.4.3.7-1/19 THEN R ELSE N/A | UE supporting 5G Core and NR L2 sidelink relay UE operation and RRC_INACTIVE | +| C395 | IF A.4.1-5/1 AND (A.4.3.2-1/187 OR A.4.3.2-1/188) THEN R ELSE N/A | UEs supporting 5G Core and Cell DTX or Cell DRX operation by RRC configuration | +| C396 | IF A.4.1-5/1 AND A.4.4-1/30 THEN R ELSE N/A | UEs supporting 5G Core and Random access MT-SDT | +| C397 | IF A.4.1-5/1 AND A.4.4-1/31 THEN R ELSE N/A | UEs supporting 5G Core and MT-SDT via Configured Grant Type 1 | +| C398 | IF A.4.1-5/1 AND A.4.3.5-1/22 AND A.4.3.5-1/21 THEN R ELSE N/A | UEs supporting 5GS and delay status reporting and refined buffer size table | +| C399 | IF A.4.1-5/1 AND A.4.3.2-1/10 AND A.4.3.2-1/217 THEN R ELSE N/A | UEs supporting 5GS and Type 1 PUSCH transmissions with configured grant and multiplexing of the unused transmission occasions on a CG-PUSCH | +| C400 | IF A.4.1-5/1 AND A.4.3.2-1/218 THEN R ELSE N/A | UEs supporting 5G Core and spatial domain adaptation with CSI feedback | +| C401 | IF A.4.1-5/1 AND A.4.3.2-1/219 THEN R ELSE N/A | UEs supporting 5G Core and power domain adaptation with CSI feedback | +| C402 | IF A.4.1-5/1 AND A.4.3.12A-1/1 AND A.4.3.12-1/5 THEN R ELSE N/A | UEs supporting 5G Core and eRedCap and halfDuplexFDD | +| C403 | IF A.4.1-5/1 AND A.4.3.1-2/1b AND A.4.3.1-2/2 AND [10] A.4.1-1/5 AND A.4.3.7-1/70 THEN R ELSE N/A | UEs supporting 5G Core and FR1 Band n40 and FR1 Band n41 and WLAN and reporting affected NR carrier frequency ranges in IDC assistance information | +| C404 | IF A.4.1-5/1 AND A.4.3.1-2/1b AND A.4.3.1-2/2 AND [10] A.4.1-1/5 AND A.4.3.7-1/76 THEN R ELSE N/A | UEs supporting 5G Core and FR1 Band n40 and FR1 Band n41 and WLAN and reporting IDC TDM assistance information | +| C405 | IF A.4.1-5/1 AND A.4.3.2-1/175 AND A.4.3.2-1/178 AND A.4.3.2-1/181 AND A.4.3.6-1/102 THEN R ELSE N/A | UEs supporting 5G Core and unified TCI with joint DL/UL TCI-state indication and MAC-CE activated joint LTM TCI states and TA indication in cell switch command and RACH-Less LTM with dynamic grant | +| C406 | IF A.4.1-4/6 AND A.4.3.2-1/175 AND A.4.3.2-1/178 AND A.4.3.2-1/182 AND A.4.3.6-1/102 THEN R ELSE N/A | UEs supporting NR-DC and unified TCI with joint DL/UL TCI-state indication and MAC-CE activated joint LTM TCI states and UE-based TA measurement by indicating the maximum number | + +| Condition | Test case Selection Expression | Comment | +|-----------|----------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | of candidate cells that the UE maintains the TA for and RACH-Less LTM with dynamic grant | +| C407 | IF A.4.1-5/1 AND A.4.4.1/17 AND A.4.3.6/119 THEN R ELSE N/A | UEs supporting 5G Core and NR NTN access and Earth Moving Cell | +| C408 | IF A.4.1-5/1 AND A.4.4.1/17 AND A.4.3.2/234 THEN R ELSE N/A | UEs supporting 5G Core and NR NTN access and Msg4 HARQ Repetition | +| C409 | IF A.4.1-5/1 AND A.4.4.1/17 AND A.4.3.8/50 THEN R ELSE N/A | UEs supporting 5G Core and NR NTN access and Event D2 | +| C410 | IF A.4.1-5/1 AND A.4.3.3-1/11 THEN R ELSE N/A | UEs supporting 5G Core and PDCP SN gap reporting | +| C411 | IF A.4.1-5/1 AND A.4.3.7-1/77 THEN R ELSE N/A | UEs supporting 5G Core and sending UE assistance information with UL traffic information, including at least one of jitter range, burst arrival time, data burst periodicity and PDU Set and PSI identification. | +| C412 | IF A.4.1-5/1 AND A.4.3.2-1/46 AND A.4.4-1/30 THEN R ELSE N/A | UEs supporting 5G Core and 2-step RACH and Random access MT-SDT | +| C413 | IF A.4.1-5/1 AND A.4.3.7-1/24 AND A.4.3.7-1/78 THEN R ELSE N/A | UEs supporting 5G Core and SNPN and equivalent SNPNs for cell (re)selection | +| C414 | IF A.4.1-5/1 AND A.4.3.2-1/160 THEN R ELSE N/A | UEs supporting 5G Core and PRACH repetition | + +## 4.3 Protocol conformance test cases applicability for Vertical UEs + +### 4.3.1 SNPN-only UEs + +Test cases applicable to SNPN-only UEs (A.4.1-5/3) are listed in Table 4.3.1-1. The Applicability - Condition of each individual test is as identified in subclause 4.1. + +**Table 4.3.1-1: Protocol conformance test cases applicable to SNPN-only UEs** + +| Clause | Comment | +|------------|------------------------------------------| +| 6.1.2.1 | | +| 6.1.2.2 | | +| 6.1.2.3 | | +| 6.1.2.4 | | +| 6.1.2.5 | | +| 6.1.2.7 | | +| 6.1.2.11 | | +| 6.1.2.16 | | +| 6.1.2.17 | | +| 6.1.2.18 | | +| 6.1.2.19 | | +| 6.1.2.20 | | +| 6.1.2.21 | | +| 6.1.2.22 | | +| 6.1.2.23 | | +| 6.3.3.1 | applicable to SNPN-only UEs since Rel-17 | +| 6.3.3.2 | applicable to SNPN-only UEs since Rel-17 | +| 6.3.3.3 | applicable to SNPN-only UEs since Rel-17 | +| 6.3.3.4 | applicable to SNPN-only UEs since Rel-17 | +| 6.4.2.1 | | +| 6.4.2.2 | | +| 6.5.1.1 | | +| 6.5.1.2 | | +| 6.5.1.3 | | +| 6.5.3.1 | applicable to SNPN-only UEs since Rel-17 | +| 6.5.3.2 | applicable to SNPN-only UEs since Rel-17 | +| 6.5.3.3 | applicable to SNPN-only UEs since Rel-17 | +| 6.5.3.4 | applicable to SNPN-only UEs since Rel-17 | +| 6.5.3.5 | applicable to SNPN-only UEs since Rel-17 | +| 6.5.3.6 | applicable to SNPN-only UEs since Rel-17 | +| 6.5.3.7 | applicable to SNPN-only UEs since Rel-17 | +| 6.5.3.8 | applicable to SNPN-only UEs since Rel-17 | +| 7.1.1.1.1 | | +| 7.1.1.1.1a | | +| 7.1.1.1.2 | | +| 7.1.1.1.3 | | + +| Clause | Comment | +|-------------|---------| +| 7.1.1.1.4 | | +| 7.1.1.1.5 | | +| 7.1.1.1.6 | | +| 7.1.1.2.1 | | +| 7.1.1.2.2 | | +| 7.1.1.2.3 | | +| 7.1.1.2.4 | | +| 7.1.1.3.1 | | +| 7.1.1.3.2 | | +| 7.1.1.3.2b | | +| 7.1.1.3.3 | | +| 7.1.1.3.4 | | +| 7.1.1.3.5 | | +| 7.1.1.3.6 | | +| 7.1.1.3.7 | | +| 7.1.1.3.8.1 | | +| 7.1.1.3.8.2 | | +| 7.1.1.3.8.3 | | +| 7.1.1.3.9 | | +| 7.1.1.4.1.1 | | +| 7.1.1.4.1.3 | | +| 7.1.1.4.1.4 | | +| 7.1.1.4.2.1 | | +| 7.1.1.4.2.3 | | +| 7.1.1.4.2.4 | | +| 7.1.1.4.2.5 | | +| 7.1.1.5.1 | | +| 7.1.1.5.2 | | +| 7.1.1.5.3 | | +| 7.1.1.5.4 | | +| 7.1.1.5.5 | | +| 7.1.1.6.1 | | +| 7.1.1.6.2 | | +| 7.1.1.6.3 | | +| 7.1.1.7.1.1 | | +| 7.1.1.7.1.2 | | +| 7.1.1.7.1.3 | | +| 7.1.1.8.1 | | +| 7.1.1.9.1 | | +| 7.1.1.10.1 | | +| 7.1.1.11.1 | | +| 7.1.2.2.1 | | +| 7.1.2.2.2 | | +| 7.1.2.2.3 | | +| 7.1.2.2.4 | | +| 7.1.2.2.5 | | +| 7.1.2.2.6 | | +| 7.1.2.3.1 | | +| 7.1.2.3.2 | | +| 7.1.2.3.3 | | +| 7.1.2.3.4 | | +| 7.1.2.3.5 | | +| 7.1.2.3.5a | | +| 7.1.2.3.6 | | +| 7.1.2.3.7 | | +| 7.1.2.3.8 | | +| 7.1.2.3.9 | | +| 7.1.2.3.10 | | +| 7.1.2.3.11 | | +| 7.1.3.1.1 | | +| 7.1.3.1.2 | | +| 7.1.3.2.1 | | +| 7.1.3.2.2 | | +| 7.1.3.2.3 | | +| 7.1.3.3.1 | | +| 7.1.3.3.2 | | +| 7.1.3.3.3 | | +| 7.1.3.4.1 | | +| 7.1.3.4.2 | | +| 7.1.3.5.1 | | +| 7.1.3.5.2 | | + +| Clause | Comment | +|--------------|------------------------------------------| +| 7.1.3.5.3 | | +| 7.1.3.5.4 | | +| 7.1.3.5.5 | | +| 7.1.4.1 | | +| 7.1.4.2 | | +| 8.1.1.1.1 | | +| 8.1.1.2.1 | | +| 8.1.1.2.3 | | +| 8.1.1.3.1 | | +| 8.1.1.3.3 | | +| 8.1.1.3.7 | | +| 8.1.1.4.1 | | +| 8.1.1.4.2 | | +| 8.1.2.1.1 | | +| 8.1.2.1.2 | | +| 8.1.2.1.4 | | +| 8.1.2.1.5.1 | | +| 8.1.2.1.5.2 | | +| 8.1.2.1.5.3 | | +| 8.1.3.1.1 | | +| 8.1.3.1.2 | | +| 8.1.3.1.3 | | +| 8.1.3.1.4 | | +| 8.1.3.1.5 | | +| 8.1.3.1.6 | | +| 8.1.3.1.7 | | +| 8.1.3.1.8 | | +| 8.1.3.1.9 | | +| 8.1.3.1.10 | | +| 8.1.3.1.11 | | +| 8.1.3.1.12 | | +| 8.1.3.1.13 | | +| 8.1.3.1.14A | | +| 8.1.3.1.15A | | +| 8.1.3.1.16 | | +| 8.1.3.1.17.1 | | +| 8.1.3.1.17.2 | | +| 8.1.3.1.17.3 | | +| 8.1.3.1.18.1 | | +| 8.1.3.1.18.2 | | +| 8.1.3.1.18.3 | | +| 8.1.3.1.19 | | +| 8.1.3.1.20 | | +| 8.1.3.1.21 | | +| 8.1.3.1.23 | | +| 8.1.4.1.2 | | +| 8.1.4.1.5 | | +| 8.1.4.1.6 | | +| 8.1.4.1.7.1 | | +| 8.1.4.1.7.2 | | +| 8.1.4.1.7.3 | | +| 8.1.4.1.8.1 | | +| 8.1.4.1.8.2 | | +| 8.1.4.1.8.3 | | +| 8.1.4.1.9.1 | | +| 8.1.4.1.9.2 | | +| 8.1.4.1.9.3 | | +| 8.1.5.1.1 | | +| 8.1.5.2.2 | | +| 8.1.5.3.1 | applicable to SNPN-only UEs since Rel-17 | +| 8.1.5.3.2 | applicable to SNPN-only UEs since Rel-17 | +| 8.1.5.3.3 | applicable to SNPN-only UEs since Rel-17 | +| 8.1.5.3.4 | applicable to SNPN-only UEs since Rel-17 | +| 8.1.5.4.1 | | +| 8.1.5.6.1 | | +| 8.1.5.6.3 | | +| 8.1.5.6.5.1 | | +| 8.1.5.6.5.2 | | +| 8.1.5.6.5.3 | | +| 8.1.5.7.1.1 | | +| 8.1.5.7.1.2 | | + +| Clause | Comment | +|-------------|------------------------------------------| +| 8.1.5.7.1.3 | | +| 8.1.5.8.1 | | +| 8.1.5.8.2.1 | | +| 8.1.5.8.2.2 | | +| 8.1.5.8.2.3 | | +| 8.1.7.2.1 | applicable to SNPN-only UEs since Rel-17 | +| 8.2.2.1.2 | | +| 8.2.2.2.2 | | +| 8.2.2.3.2 | | +| 8.2.2.4.2 | | +| 8.2.2.5.2 | | +| 8.2.2.7.2 | | +| 8.2.2.8.2 | | +| 8.2.2.9.2 | | +| 8.2.3.11.3 | | +| 8.2.3.14.2 | | +| 8.2.3.16.2 | | +| 8.2.3.17.2 | | +| 8.2.5.1.2 | | +| 8.2.5.2.2 | | +| 8.2.5.3.2 | | +| 8.2.5.4.2 | | +| 8.2.6.1.2.1 | | +| 8.2.6.1.2.2 | | +| 8.2.6.1.2.3 | | +| 8.2.6.2.2 | | +| 9.1.1.1 | | +| 9.1.1.2 | | +| 9.1.1.3 | | +| 9.1.1.4 | | +| 9.1.1.5 | | +| 9.1.1.6 | | +| 9.1.2.1 | | +| 9.1.2.2 | | +| 9.1.2.3 | | +| 9.1.2.4 | | +| 9.1.2.5 | | +| 9.1.2.6 | | +| 9.1.2.7 | | +| 9.1.2.8 | | +| 9.1.3.1 | | +| 9.1.4.1 | | +| 9.1.5.1.3 | | +| 9.1.5.1.3a | | +| 9.1.5.1.4 | | +| 9.1.5.1.5 | | +| 9.1.5.1.9 | | +| 9.1.5.1.11 | | +| 9.1.5.1.12 | | +| 9.1.5.1.13 | | +| 9.1.5.2.1 | | +| 9.1.5.2.2 | | +| 9.1.5.2.4 | | +| 9.1.5.2.7 | | +| 9.1.5.2.8 | | +| 9.1.6.1.1 | | +| 9.1.6.1.2 | | +| 9.1.6.1.3 | | +| 9.1.6.2.1 | | +| 9.1.6.2.2 | | +| 9.1.7.1 | | +| 9.1.7.2 | | +| 9.1.8.1 | | +| 9.1.8.2 | | +| 9.1.11.1 | | +| 9.1.11.2 | | +| 9.1.11.3 | | +| 9.1.11.4 | applicable to SNPN-only UEs since Rel-17 | +| 9.1.11.5 | applicable to SNPN-only UEs since Rel-17 | +| 9.1.11.6 | applicable to SNPN-only UEs since Rel-17 | +| 9.1.11.7 | applicable to SNPN-only UEs since Rel-17 | + +| Clause | Comment | +|------------------------------------------------------------------------------------------------------------------|------------------------------------------| +| 10.1.1.1 | | +| 10.1.1.2 | | +| 10.1.2.1 | | +| 10.1.2.2 | | +| 10.1.3.2 | | +| 10.1.4.1 | | +| 10.1.5.1 | | +| 10.1.6.1 | | +| 10.1.6.2 | | +| 11.3.1a | | +| 11.3.3 | | +| 11.3.4 | | +| 11.3.6a | | +| 11.3.8 | | +| 11.3.9a | | +| 11.4.15 | applicable to SNPN-only UEs since Rel-17 | +| Note: all the above test cases are applicable for Rel-16 SNPN-only UEs unless other specified in comment column. | | + +## Annex A (informative): Rel-16 and later test cases completed for RedCap UEs + +Currently for RedCap UEs that set the PICS complying with TS 38.508-2 [5] clause A.4.3.12, Rel-15 test cases and Rel-17 RedCap specific test cases are applicable. + +In the current version of the specification, Rel-16 and later test cases listed in Table A-1 have been fully analysed and confirmed to be completed for execution against RedCap UEs. Applicability of other Rel-16 and later test cases are under further study. + +**Table A-1: Rel-16 and later test cases completed for RedCap UEs** + +| Clause | Release | Feature | +|--------------|---------|-----------------------------------------------| +| 7.1.1.1.7 | Rel-16 | 2-step RACH for NR | +| 7.1.1.1.8 | Rel-16 | 2-step RACH for NR | +| 7.1.1.1.9 | Rel-16 | 2-step RACH for NR | +| 7.1.1.1.9a | Rel-16 | 2-step RACH for NR | +| 7.1.1.1.10 | Rel-16 | 2-step RACH for NR | +| 7.1.1.1.10a | Rel-16 | 2-step RACH for NR | +| 7.1.1.1.18 | Rel-17 | NR coverage enhancements | +| 7.1.1.2.6 | Rel-17 | NR coverage enhancements | +| 7.1.1.3.14.1 | Rel-17 | NR coverage enhancements | +| 7.1.1.3.14.2 | Rel-17 | NR coverage enhancements | +| 7.1.1.3.14.3 | Rel-17 | NR coverage enhancements | +| 7.1.1.3.14.4 | Rel-17 | NR coverage enhancements | +| 7.1.1.3.15.1 | Rel-17 | NR coverage enhancements | +| 7.1.1.3.15.2 | Rel-17 | NR coverage enhancements | +| 7.1.1.4.1.5 | Rel-16 | Physical Layer Enhancements for NR URLLC | +| 7.1.1.4.2.6 | Rel-16 | Physical Layer Enhancements for NR URLLC | +| 7.1.1.4.2.7 | Rel-17 | NR coverage enhancements | +| 7.1.1.12.3 | Rel-16 | UE Power Saving in NR | +| 7.1.1.13.1 | Rel-17 | NR small data transmissions in INACTIVE state | +| 7.1.1.13.2 | Rel-17 | NR small data transmissions in INACTIVE state | +| 7.1.1.13.3 | Rel-17 | NR small data transmissions in INACTIVE state | +| 7.1.1.13.4 | Rel-17 | NR small data transmissions in INACTIVE state | +| 7.1.1.13.5 | Rel-17 | NR small data transmissions in INACTIVE state | +| 8.1.1.1a.1 | Rel-17 | UE power saving enhancements for NR | +| 8.1.1.1a.2 | Rel-17 | UE power saving enhancements for NR | +| 8.1.1.1a.3 | Rel-17 | UE power saving enhancements for NR | +| 8.1.5.10.1 | Rel-16 | UE Power Saving in NR | +| 8.1.5.13.1 | Rel-17 | NR small data transmissions in INACTIVE state | +| 8.1.5.13.2 | Rel-17 | NR small data transmissions in INACTIVE state | +| 8.1.5.13.3 | Rel-17 | NR small data transmissions in INACTIVE state | +| 9.1.14.1 | Rel-17 | UE power saving enhancements for NR | +| 11.4.1a | Rel-17 | UE power saving enhancements for NR | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38741/06ccd604e7eac77c7a5a323b6a913f15_img.jpg b/marked/Rel-18/38_series/38741/06ccd604e7eac77c7a5a323b6a913f15_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e23613cf9e124bc8ec4c54d1263bbabc880bd09e --- /dev/null +++ b/marked/Rel-18/38_series/38741/06ccd604e7eac77c7a5a323b6a913f15_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:edf3de7c4bda24fa0d7ca12393b2d5dd3c6f92301e48538b253f823aa3e3edb0 +size 41573 diff --git a/marked/Rel-18/38_series/38741/07b56a8a7752e22a6fc5e9a5d2de5caa_img.jpg b/marked/Rel-18/38_series/38741/07b56a8a7752e22a6fc5e9a5d2de5caa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ee135096953cb1428814658e64f9bb6760ebb593 --- /dev/null +++ b/marked/Rel-18/38_series/38741/07b56a8a7752e22a6fc5e9a5d2de5caa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b31dc21e4eb6aaabf4e99f4798027fb8a3e78503641c68fd6e2ed9d527691d43 +size 11414 diff --git a/marked/Rel-18/38_series/38741/09ab686699bb9597b8025e78fb390069_img.jpg b/marked/Rel-18/38_series/38741/09ab686699bb9597b8025e78fb390069_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..556ba67ac258369251f034c84c3b7643eeb8aaad --- /dev/null +++ b/marked/Rel-18/38_series/38741/09ab686699bb9597b8025e78fb390069_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ab9c28c38e8a68308f2ce35f46028f02bc3fe77e506fc9feca37c5698bb1c20 +size 32966 diff --git a/marked/Rel-18/38_series/38741/0a8d173734e4e46c344178e8d21bcbc3_img.jpg b/marked/Rel-18/38_series/38741/0a8d173734e4e46c344178e8d21bcbc3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0f7bc8ec4e3819beb4d5a212b6012869c0519c63 --- /dev/null +++ b/marked/Rel-18/38_series/38741/0a8d173734e4e46c344178e8d21bcbc3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:87ee878acdbb57eb80a91816e030b1cad9c66e246157cc79a6e014dc05ccf3a8 +size 9771 diff --git a/marked/Rel-18/38_series/38741/0bd23f00e0632855cfef9274f1ab93d8_img.jpg b/marked/Rel-18/38_series/38741/0bd23f00e0632855cfef9274f1ab93d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6811442018b0e2c62ea215f76bcd4bd75f738c8c --- /dev/null +++ b/marked/Rel-18/38_series/38741/0bd23f00e0632855cfef9274f1ab93d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ea0d1a2da8f0ebdfc6a5e8433e45ca3ee4e96c375c237bc54d445384983aa50 +size 11034 diff --git a/marked/Rel-18/38_series/38741/1145fc59efdc7dacc8d3c715d7ff3248_img.jpg b/marked/Rel-18/38_series/38741/1145fc59efdc7dacc8d3c715d7ff3248_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4537c545b8e07096b10708f459214a3f23882e5c --- /dev/null +++ b/marked/Rel-18/38_series/38741/1145fc59efdc7dacc8d3c715d7ff3248_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e48a26c1cb73219725b3dd2a71712843e465b5d01f6a613d9679e24c4d03d268 +size 12584 diff --git a/marked/Rel-18/38_series/38741/155bd5ec49c26532be9f04b06904002e_img.jpg b/marked/Rel-18/38_series/38741/155bd5ec49c26532be9f04b06904002e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e4545c3ee136c3018b3b2f545c1ba1b3a0c7e1e --- /dev/null +++ b/marked/Rel-18/38_series/38741/155bd5ec49c26532be9f04b06904002e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:760260e055ff4aedd9ab980d56bb2fa71e28b458e05b8fe6fc0730a265b3784a +size 60258 diff --git a/marked/Rel-18/38_series/38741/17cd95aa220e50963bf6eb9818e33163_img.jpg b/marked/Rel-18/38_series/38741/17cd95aa220e50963bf6eb9818e33163_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c4ac81bcaf84855352a9b25e410f5eafbb196206 --- /dev/null +++ b/marked/Rel-18/38_series/38741/17cd95aa220e50963bf6eb9818e33163_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba3fb76df4536aa1f78053f5d7c8cf2f71eb94004f8aab489cf310d18931ec11 +size 25832 diff --git a/marked/Rel-18/38_series/38741/1a6a826cc13d4e964b7bda69508d78e6_img.jpg b/marked/Rel-18/38_series/38741/1a6a826cc13d4e964b7bda69508d78e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a67e380c79634f88987b30a4672223844f5476a9 --- /dev/null +++ b/marked/Rel-18/38_series/38741/1a6a826cc13d4e964b7bda69508d78e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3514a9d7a7addefb3a2ff0c52182d34fcebce0420817305a32a8b9f02c914ed1 +size 10345 diff --git a/marked/Rel-18/38_series/38741/1b1bb497e39fcc025a3fc8bd4fc78d9a_img.jpg b/marked/Rel-18/38_series/38741/1b1bb497e39fcc025a3fc8bd4fc78d9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..04dadd37239d28ce6a280f0f2f005633497cc2a8 --- /dev/null +++ b/marked/Rel-18/38_series/38741/1b1bb497e39fcc025a3fc8bd4fc78d9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba854d7e9c41d33d105215d17fb3e6b4aeac279f4d13d17a054d14bf44d38634 +size 48778 diff --git a/marked/Rel-18/38_series/38741/1c427123350e0e73e2a109b79069314b_img.jpg b/marked/Rel-18/38_series/38741/1c427123350e0e73e2a109b79069314b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..17753b7bf92b8741cfd02a1bcf041c17044cf0c0 --- /dev/null +++ b/marked/Rel-18/38_series/38741/1c427123350e0e73e2a109b79069314b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6445ca811abeed58eb6fc839e7a5c0057b05fbe16e4900435e06ea58e514bfe0 +size 30600 diff --git a/marked/Rel-18/38_series/38741/2208043dc0f4fadcc7e33697806083c3_img.jpg b/marked/Rel-18/38_series/38741/2208043dc0f4fadcc7e33697806083c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4506b116d0045f1fd0583a1555d20dc69d428609 --- /dev/null +++ b/marked/Rel-18/38_series/38741/2208043dc0f4fadcc7e33697806083c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f45aa780667abe1e9fd79719ae94a1bb8e4c3fa1fd9cfbbb5ece145615b4baaf +size 9760 diff --git a/marked/Rel-18/38_series/38741/28487ff44b62fdcb48c6f38153c35495_img.jpg b/marked/Rel-18/38_series/38741/28487ff44b62fdcb48c6f38153c35495_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d77b1b1371f3c371b2f3d90b909a1a6f047cd5fa --- /dev/null +++ b/marked/Rel-18/38_series/38741/28487ff44b62fdcb48c6f38153c35495_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6eec31bbcd469bde3dd3e0597c81f882a4c18eb446c5566bfba8e4143acdd306 +size 11505 diff --git a/marked/Rel-18/38_series/38741/35a929c866c4c49f4aa4e7103b8a0b9b_img.jpg b/marked/Rel-18/38_series/38741/35a929c866c4c49f4aa4e7103b8a0b9b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a77b22c13ee430e4cff4367040fa91e0a8df28c0 --- /dev/null +++ b/marked/Rel-18/38_series/38741/35a929c866c4c49f4aa4e7103b8a0b9b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:63df1ca5860437c127885a4be92049b4bf53204e86f9285da372993ea6daed01 +size 13754 diff --git a/marked/Rel-18/38_series/38741/3d827c43b44a567da971c01073295d3d_img.jpg b/marked/Rel-18/38_series/38741/3d827c43b44a567da971c01073295d3d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a4d9bda806f8c9666c8040e01fe32b645910188 --- /dev/null +++ b/marked/Rel-18/38_series/38741/3d827c43b44a567da971c01073295d3d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0879b3e92e4d9e95db69963ac33db46f77ede994edc7d77b13e977f93b15ec1f +size 12715 diff --git a/marked/Rel-18/38_series/38741/3e0c2bf6c51c575d096c7fc95c1e8454_img.jpg b/marked/Rel-18/38_series/38741/3e0c2bf6c51c575d096c7fc95c1e8454_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..12689110e324012f4afb7d6b84b5f83bd4a5b272 --- /dev/null +++ b/marked/Rel-18/38_series/38741/3e0c2bf6c51c575d096c7fc95c1e8454_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5fb1ab898bdd83ae817784216e37bc6defbf949264f38d3d74fcc62255565969 +size 40441 diff --git a/marked/Rel-18/38_series/38741/411fa16c3211377525ba37c57784fee0_img.jpg b/marked/Rel-18/38_series/38741/411fa16c3211377525ba37c57784fee0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c567684e89ebcb56e11a16751b600068b93c2eb --- /dev/null +++ b/marked/Rel-18/38_series/38741/411fa16c3211377525ba37c57784fee0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ee9f1bfec05aaf86334ed2febf5c3354c9324a0dccde552e95aea2823caf2ea +size 35850 diff --git a/marked/Rel-18/38_series/38741/484cfbdc05aee471306eeb11c0ee2543_img.jpg b/marked/Rel-18/38_series/38741/484cfbdc05aee471306eeb11c0ee2543_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9fd9bc085aef103691b9e45f1ffff8254ecb93ec --- /dev/null +++ b/marked/Rel-18/38_series/38741/484cfbdc05aee471306eeb11c0ee2543_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aad6608a35c0aa1ac91cd0ced8e08af103ebc88d4b0ffc7063a1515039ef2261 +size 54252 diff --git a/marked/Rel-18/38_series/38741/4a8166688ed7276efb173f550ba47eb4_img.jpg b/marked/Rel-18/38_series/38741/4a8166688ed7276efb173f550ba47eb4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b3bd5499befd24cd601e64a569405d6bd6358792 --- /dev/null +++ b/marked/Rel-18/38_series/38741/4a8166688ed7276efb173f550ba47eb4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e26a639c43d9d3ea80f3911d0eb5e729013bd4e910367cceddc36104753bec0 +size 9712 diff --git a/marked/Rel-18/38_series/38741/4dfe30ac5a87d018364a0ac42ea533fe_img.jpg b/marked/Rel-18/38_series/38741/4dfe30ac5a87d018364a0ac42ea533fe_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b041ff758509714ba7482fef4a5b23e9ad47f18 --- /dev/null +++ b/marked/Rel-18/38_series/38741/4dfe30ac5a87d018364a0ac42ea533fe_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5766f2847447703e4c46806fe6ded4b8d2d359207b5ed0d25b9823bd060261c9 +size 44888 diff --git a/marked/Rel-18/38_series/38741/4e7f11ebd82a34bb69e271477038b901_img.jpg b/marked/Rel-18/38_series/38741/4e7f11ebd82a34bb69e271477038b901_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0dd34e9094ddfa3863dfc4223e0b00e5692ebf43 --- /dev/null +++ b/marked/Rel-18/38_series/38741/4e7f11ebd82a34bb69e271477038b901_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7053e7662e171157a0337df7bfb5117cef4750d578665615935600a2b2d2ad4c +size 34979 diff --git a/marked/Rel-18/38_series/38741/595d7ce1dd65a29378ac2c96922a866a_img.jpg b/marked/Rel-18/38_series/38741/595d7ce1dd65a29378ac2c96922a866a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d2b9902fbd7bce9170109bc760203b09419460c4 --- /dev/null +++ b/marked/Rel-18/38_series/38741/595d7ce1dd65a29378ac2c96922a866a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd98c5819e1c62d8538581a4636fbc2728f5c28fcda46e5426875ff6e21dfead +size 12715 diff --git a/marked/Rel-18/38_series/38741/5adf12d50dfea82178ca002a2c48641b_img.jpg b/marked/Rel-18/38_series/38741/5adf12d50dfea82178ca002a2c48641b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56ba716b2cdfa0d619660f8124f30c145532b9c6 --- /dev/null +++ b/marked/Rel-18/38_series/38741/5adf12d50dfea82178ca002a2c48641b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6957d8978869a24a8b9addd9276f7a91b8f86f5ec6a2a069578da00647ee57d4 +size 35535 diff --git a/marked/Rel-18/38_series/38741/5c962f53272b4722e5d88f049e25084f_img.jpg b/marked/Rel-18/38_series/38741/5c962f53272b4722e5d88f049e25084f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ec72784d75f0d847da7cab3b120e9370abd5c40 --- /dev/null +++ b/marked/Rel-18/38_series/38741/5c962f53272b4722e5d88f049e25084f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:189af8f428c566bf4a65df8a63a58c3eb4ee8e5de2e4a5682886b462fe36bb9b +size 9871 diff --git a/marked/Rel-18/38_series/38741/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38741/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64135c1ca73b38789cb7f0c2067e38237bb3380f --- /dev/null +++ b/marked/Rel-18/38_series/38741/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f69cfc7af616fe9b909efafe8e3b8f1d9056ff3dea9bd1e9f6086b68c065a71e +size 9822 diff --git a/marked/Rel-18/38_series/38741/62ad98a4bc47922b5cf47de04571dae8_img.jpg b/marked/Rel-18/38_series/38741/62ad98a4bc47922b5cf47de04571dae8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77117ef97b8ea134d748260ecf8bb949d5a2a66b --- /dev/null +++ b/marked/Rel-18/38_series/38741/62ad98a4bc47922b5cf47de04571dae8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9bace61f86392cf898b26fdddeb38822f9df2c3a8bc8d193554f3814a651548f +size 45822 diff --git a/marked/Rel-18/38_series/38741/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38741/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2c06bcfe0bda2f34298d15c8a967b6e793d41d9 --- /dev/null +++ b/marked/Rel-18/38_series/38741/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bfc8d6a462ea78987af56cd55f45525bba81ad1c5d0ae1da9766da6271e332c3 +size 5684 diff --git a/marked/Rel-18/38_series/38741/65a9654ccb3d0d452378b0f4c0c392f7_img.jpg b/marked/Rel-18/38_series/38741/65a9654ccb3d0d452378b0f4c0c392f7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d6b35ddc19ab2970c2ee108bf543a81450ea96b7 --- /dev/null +++ b/marked/Rel-18/38_series/38741/65a9654ccb3d0d452378b0f4c0c392f7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14473acd66de813bcb7084388a8888d0d9ef56d4c2f52acec1000ba576e6b287 +size 41222 diff --git a/marked/Rel-18/38_series/38741/6682c4376efdda007851175f3014eca3_img.jpg b/marked/Rel-18/38_series/38741/6682c4376efdda007851175f3014eca3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e66b55c668c3e4aa23f3b15ef5edf4b2b164acb6 --- /dev/null +++ b/marked/Rel-18/38_series/38741/6682c4376efdda007851175f3014eca3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc83e52220338079fdb3c1e344e9f8ddbdbbf089c8793d3e35b0e8f553539e4c +size 12485 diff --git a/marked/Rel-18/38_series/38741/67518cfe156890dac13b5e67abd10dc1_img.jpg b/marked/Rel-18/38_series/38741/67518cfe156890dac13b5e67abd10dc1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..746b760fb028afb97a8489ee71ff978182df9fc6 --- /dev/null +++ b/marked/Rel-18/38_series/38741/67518cfe156890dac13b5e67abd10dc1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ff56e2c2cc81c7199d0051b67452396734889cfd40437c50382ac06c9b4f89ff +size 44746 diff --git a/marked/Rel-18/38_series/38741/6ba2b00e9434aa86af566824b1c1446b_img.jpg b/marked/Rel-18/38_series/38741/6ba2b00e9434aa86af566824b1c1446b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..08b4f057d6ac4c8e162cefb350ef1bc7005d2d89 --- /dev/null +++ b/marked/Rel-18/38_series/38741/6ba2b00e9434aa86af566824b1c1446b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ee3b7d98cc2fa67804edb232d9ef636200a417d4f861ddcce7a540436fa16ef +size 13679 diff --git a/marked/Rel-18/38_series/38741/723827e0738d2743c3b3423760a5c48e_img.jpg b/marked/Rel-18/38_series/38741/723827e0738d2743c3b3423760a5c48e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..813fe86413f784cdad7327155143560971391606 --- /dev/null +++ b/marked/Rel-18/38_series/38741/723827e0738d2743c3b3423760a5c48e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a3de8aa13a36f1ed5ec734274e38fd246d85e3e177b7a6e1e92f2d5abc82fb18 +size 44665 diff --git a/marked/Rel-18/38_series/38741/7ede87328f6b696dcffa65ebc4570cc8_img.jpg b/marked/Rel-18/38_series/38741/7ede87328f6b696dcffa65ebc4570cc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3083c4fa1841da32cf79c47ad70384011456b5ee --- /dev/null +++ b/marked/Rel-18/38_series/38741/7ede87328f6b696dcffa65ebc4570cc8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d34e765f8191b335c0bc70ff961df6350c3370f2e8b223143a15a0c398bb4cb4 +size 14062 diff --git a/marked/Rel-18/38_series/38741/812b773680b611c18d49243e102b895a_img.jpg b/marked/Rel-18/38_series/38741/812b773680b611c18d49243e102b895a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4abd6b14a7ce5ec00fc5183da917a3813927e39e --- /dev/null +++ b/marked/Rel-18/38_series/38741/812b773680b611c18d49243e102b895a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d88883c8e5e36a2ee7ff77bc01770c895399ca98ac00e44f8911b61c05dd70a5 +size 35687 diff --git a/marked/Rel-18/38_series/38741/865a630eb1b708bd28250dfeb33dd8f1_img.jpg b/marked/Rel-18/38_series/38741/865a630eb1b708bd28250dfeb33dd8f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fea1f5916f9edbf1a5c7d4a0f18cdb943170fb67 --- /dev/null +++ b/marked/Rel-18/38_series/38741/865a630eb1b708bd28250dfeb33dd8f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:33c6eb5213c578c0d225fc7fecec7ef03ed43a1e330dabbd40e2cc7d8bc017b2 +size 13116 diff --git a/marked/Rel-18/38_series/38741/88362167d90777ecb0aeb145832e78c2_img.jpg b/marked/Rel-18/38_series/38741/88362167d90777ecb0aeb145832e78c2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13061eb6689e6e5ed06c77b06b367297532efa66 --- /dev/null +++ b/marked/Rel-18/38_series/38741/88362167d90777ecb0aeb145832e78c2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b468dfa41a7c693693613f15a1bb1cc142102beb649de33530ce26f86f64a773 +size 9749 diff --git a/marked/Rel-18/38_series/38741/99938fa8d7d80af041634eba601e418b_img.jpg b/marked/Rel-18/38_series/38741/99938fa8d7d80af041634eba601e418b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..44d527e8e20c5f95f28afee3b020030683799f20 --- /dev/null +++ b/marked/Rel-18/38_series/38741/99938fa8d7d80af041634eba601e418b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:134fd26317de7d715a76f5292755e6a20da3d2081a37604f1bb94fb229e6e8a5 +size 18395 diff --git a/marked/Rel-18/38_series/38741/a1a474be12b8992842992294b1d18592_img.jpg b/marked/Rel-18/38_series/38741/a1a474be12b8992842992294b1d18592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92ff4009c7b436302ee9f6fa8f468fc8bc6ddfa6 --- /dev/null +++ b/marked/Rel-18/38_series/38741/a1a474be12b8992842992294b1d18592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6213f32bc7ffba174f7bc0f5573427c560b729d0cc5155a7d074a553677ddcf1 +size 42150 diff --git a/marked/Rel-18/38_series/38741/a289b64f80c6df506c0c55d553fc4496_img.jpg b/marked/Rel-18/38_series/38741/a289b64f80c6df506c0c55d553fc4496_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eda51f398aa5ede7fde96b54eb49f75e1e609069 --- /dev/null +++ b/marked/Rel-18/38_series/38741/a289b64f80c6df506c0c55d553fc4496_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd6823bdc479887a3d6328146e1b7b1d234c23b2e692461517ed809f7fbf6489 +size 37858 diff --git a/marked/Rel-18/38_series/38741/a2f89834a149b852721f8887349fd6fa_img.jpg b/marked/Rel-18/38_series/38741/a2f89834a149b852721f8887349fd6fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c4291b7c623183379071c4f863d0f255b8d84744 --- /dev/null +++ b/marked/Rel-18/38_series/38741/a2f89834a149b852721f8887349fd6fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f3bd106306c9b8a9417d8d42d072070cdb9932d7cd6902df20225615b5c34f84 +size 10952 diff --git a/marked/Rel-18/38_series/38741/a3c02bfac05114bb808134408d67f20b_img.jpg b/marked/Rel-18/38_series/38741/a3c02bfac05114bb808134408d67f20b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8217cb9751c7f75e851eb07f3c0655f03ea06a7 --- /dev/null +++ b/marked/Rel-18/38_series/38741/a3c02bfac05114bb808134408d67f20b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c83f8d9fd09e958519b9279ae44807f72f11f1388f0926d7697a8977c5c747ae +size 13770 diff --git a/marked/Rel-18/38_series/38741/a430996a9e8993deb0c6b25da234744b_img.jpg b/marked/Rel-18/38_series/38741/a430996a9e8993deb0c6b25da234744b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..57f0073da9b7f03aa36a6bae4e29728030cfd55f --- /dev/null +++ b/marked/Rel-18/38_series/38741/a430996a9e8993deb0c6b25da234744b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:07885edb9b53a4e0ea27b5f3885d56b63c2135f60d6122b34a865e8c676efb29 +size 10282 diff --git a/marked/Rel-18/38_series/38741/b2e1c48ea85ca7aef5ab959221c8ff6b_img.jpg b/marked/Rel-18/38_series/38741/b2e1c48ea85ca7aef5ab959221c8ff6b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6729c6e3c0ab22eb92c82a0dd882ef4c85dd35c --- /dev/null +++ b/marked/Rel-18/38_series/38741/b2e1c48ea85ca7aef5ab959221c8ff6b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0876e167bce6ee1ccef87884f6790878c8c2ce16f1dd46519e5f38c05bee4463 +size 10430 diff --git a/marked/Rel-18/38_series/38741/bd998e32488e42e7ab0d3c170c1eff26_img.jpg b/marked/Rel-18/38_series/38741/bd998e32488e42e7ab0d3c170c1eff26_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07e72a9cc6a449dcdf9ffdf10a01788e8a4d2e64 --- /dev/null +++ b/marked/Rel-18/38_series/38741/bd998e32488e42e7ab0d3c170c1eff26_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f49c6cfead6bce93a361dcb65acb67fe273aa4f97779277d1409021e29356964 +size 9075 diff --git a/marked/Rel-18/38_series/38741/c260fa717b624233542a7116e022e771_img.jpg b/marked/Rel-18/38_series/38741/c260fa717b624233542a7116e022e771_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cfa25b38d6c2cd8bdd34cdc901179a3b06765707 --- /dev/null +++ b/marked/Rel-18/38_series/38741/c260fa717b624233542a7116e022e771_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a1d9bbb4b158605c62b3300c8e8173a64533f037158a6878705d7c784f17a43 +size 13382 diff --git a/marked/Rel-18/38_series/38741/ca80b99f7e1d6e6b854f22190f2e14d8_img.jpg b/marked/Rel-18/38_series/38741/ca80b99f7e1d6e6b854f22190f2e14d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e3d9316ce821700084b05c23a994471c865af97 --- /dev/null +++ b/marked/Rel-18/38_series/38741/ca80b99f7e1d6e6b854f22190f2e14d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:10902b637b3ce076201e6256fbe00d51aef3719f7fbeeac1e2f9035cdd7411b3 +size 43385 diff --git a/marked/Rel-18/38_series/38741/cbc4516eb885829fe8c9dabc0946dcbe_img.jpg b/marked/Rel-18/38_series/38741/cbc4516eb885829fe8c9dabc0946dcbe_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc2ba2ed280f93d14a1296b03a00c00cbb2bd16a --- /dev/null +++ b/marked/Rel-18/38_series/38741/cbc4516eb885829fe8c9dabc0946dcbe_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8bc96983657d72d2e655c2650124054f7292d88df29efe0e1028dfe3192ccc1a +size 8702 diff --git a/marked/Rel-18/38_series/38741/cc8bec39d25eb0aafb5382c05f0d5deb_img.jpg b/marked/Rel-18/38_series/38741/cc8bec39d25eb0aafb5382c05f0d5deb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..85b5da7dc9bcb4298191e37736b528cc0f33ddbc --- /dev/null +++ b/marked/Rel-18/38_series/38741/cc8bec39d25eb0aafb5382c05f0d5deb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8e25a263db878563e88e6b64dcd45d9a2a08795d881c812205c49e34bd1b8f1 +size 8076 diff --git a/marked/Rel-18/38_series/38741/d00a096e2b5e638235ecd1834e48f706_img.jpg b/marked/Rel-18/38_series/38741/d00a096e2b5e638235ecd1834e48f706_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d2779349c25b5de47f8ee4d11d6fc10661928795 --- /dev/null +++ b/marked/Rel-18/38_series/38741/d00a096e2b5e638235ecd1834e48f706_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:73bf196b3dbee1e4e7e2c0cf429df0cf5580a8dbcceea21de076ef585131c02d +size 14562 diff --git a/marked/Rel-18/38_series/38741/d29d72755dd131d215d854aaf90fea3e_img.jpg b/marked/Rel-18/38_series/38741/d29d72755dd131d215d854aaf90fea3e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bdb1d753c2356b015251b9824ce1cb5ed9ea13cb --- /dev/null +++ b/marked/Rel-18/38_series/38741/d29d72755dd131d215d854aaf90fea3e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6811293e0f2c421103b16887800b80ed52c405a074279c48d19168c792c696b3 +size 13401 diff --git a/marked/Rel-18/38_series/38741/dc0cec98faa3ead994c1b171cb56265d_img.jpg b/marked/Rel-18/38_series/38741/dc0cec98faa3ead994c1b171cb56265d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..825e237e5017077fc95d75eccbe0b1f6d00ac732 --- /dev/null +++ b/marked/Rel-18/38_series/38741/dc0cec98faa3ead994c1b171cb56265d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b46aab81ea53e715bbf30ea9fa61073937d87db19589082de973d2ba419fac72 +size 8009 diff --git a/marked/Rel-18/38_series/38741/df7cb4ea9bd6c3f445f3e264773b125f_img.jpg b/marked/Rel-18/38_series/38741/df7cb4ea9bd6c3f445f3e264773b125f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e3a285f951a3c2921323ec8f07f58fa57dcc0f4 --- /dev/null +++ b/marked/Rel-18/38_series/38741/df7cb4ea9bd6c3f445f3e264773b125f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:06b9fbd41e7aad4ff4a6cde2b8880dc3db31b5f4b8a47f533f5c5d87f58a09be +size 13550 diff --git a/marked/Rel-18/38_series/38741/dfd60da6d5e7618f3122c129506e105e_img.jpg b/marked/Rel-18/38_series/38741/dfd60da6d5e7618f3122c129506e105e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b0bae27cf70759d7354dd6a92988836f70a75c0e --- /dev/null +++ b/marked/Rel-18/38_series/38741/dfd60da6d5e7618f3122c129506e105e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fddccbf23454a88e84f89b78459fafdc4ff385109a78d95d5e8633336699aa26 +size 10991 diff --git a/marked/Rel-18/38_series/38741/dffef2e70b14b1e00e5a5e1b8b34d722_img.jpg b/marked/Rel-18/38_series/38741/dffef2e70b14b1e00e5a5e1b8b34d722_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b034886816d54436430a8035a402fc6f68bcb7d --- /dev/null +++ b/marked/Rel-18/38_series/38741/dffef2e70b14b1e00e5a5e1b8b34d722_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51edc9440ce1a2c6393502ae33a44937f090eb9ae85c550d9ac11cbbca080882 +size 15191 diff --git a/marked/Rel-18/38_series/38741/e95f47f7a4c01c8889d6d46919b4c73d_img.jpg b/marked/Rel-18/38_series/38741/e95f47f7a4c01c8889d6d46919b4c73d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a1bc26857595f4665b1d2e87bf6200d25b6bf3a0 --- /dev/null +++ b/marked/Rel-18/38_series/38741/e95f47f7a4c01c8889d6d46919b4c73d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3819277c4c19e7cb76186484ffec9b7b08887bf8887fdd916adf744693444497 +size 9821 diff --git a/marked/Rel-18/38_series/38741/ebb257e664fc85a1eb4d6534842794bb_img.jpg b/marked/Rel-18/38_series/38741/ebb257e664fc85a1eb4d6534842794bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad9a215a11f545b214235c19dc26b807736f34cf --- /dev/null +++ b/marked/Rel-18/38_series/38741/ebb257e664fc85a1eb4d6534842794bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc8c0a51c78aa00405ecb6c8f39c955cc8f52916a5e205afbb6c7c4c12eac888 +size 38532 diff --git a/marked/Rel-18/38_series/38741/ef075538e1af84d8c6631c84087faeab_img.jpg b/marked/Rel-18/38_series/38741/ef075538e1af84d8c6631c84087faeab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7931746a32e512d865ea81acca01a645d2998c69 --- /dev/null +++ b/marked/Rel-18/38_series/38741/ef075538e1af84d8c6631c84087faeab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a3d774ebd7d0b571368e6e0f6f6f55f5492dc17c8b30b55de1d32ef494ab397 +size 8957 diff --git a/marked/Rel-18/38_series/38741/ef177a7090c8da3fcd9beb78e78fd68f_img.jpg b/marked/Rel-18/38_series/38741/ef177a7090c8da3fcd9beb78e78fd68f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92cac4a4f2b23ab40c4a02f90fcf0a43eb35e351 --- /dev/null +++ b/marked/Rel-18/38_series/38741/ef177a7090c8da3fcd9beb78e78fd68f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ee48049edc7dc04d11c3052c785fc585b17b9ab9773277e900c17be3b7f1fab +size 9513 diff --git a/marked/Rel-18/38_series/38741/ef25c3cf1fdb334fc8679e85ab5265ca_img.jpg b/marked/Rel-18/38_series/38741/ef25c3cf1fdb334fc8679e85ab5265ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed65e6e8455c609048cae732cb7a96efd497a13f --- /dev/null +++ b/marked/Rel-18/38_series/38741/ef25c3cf1fdb334fc8679e85ab5265ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:77f014625b0391009d740a9c24a185c666236abcb423e5be759d1da753de7b1b +size 11081 diff --git a/marked/Rel-18/38_series/38741/f85bf99d372e735d228361bf4d3cf7e6_img.jpg b/marked/Rel-18/38_series/38741/f85bf99d372e735d228361bf4d3cf7e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8e00211a683f08c0fa77ffcd75351a9581a16ddf --- /dev/null +++ b/marked/Rel-18/38_series/38741/f85bf99d372e735d228361bf4d3cf7e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a467710d9eafe449ae00d9fb2879c992716ad437707f0f3379e23411c32f73a5 +size 42856 diff --git a/marked/Rel-18/38_series/38741/fbfbbc91a80a21fc8d0ff7ba9e5865e3_img.jpg b/marked/Rel-18/38_series/38741/fbfbbc91a80a21fc8d0ff7ba9e5865e3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c426e7da39d6c27625ab17e35ec8e700640d5825 --- /dev/null +++ b/marked/Rel-18/38_series/38741/fbfbbc91a80a21fc8d0ff7ba9e5865e3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c1e9f3f9b2108540d76a043c8d52ab9aa3129d28354dfdf092ac6ef7457581d6 +size 34503 diff --git a/marked/Rel-18/38_series/38741/fc857414626a8d94d132e12d9afe52a4_img.jpg b/marked/Rel-18/38_series/38741/fc857414626a8d94d132e12d9afe52a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ced1fed6542ad423a6f2bdb4049246a245d82996 --- /dev/null +++ b/marked/Rel-18/38_series/38741/fc857414626a8d94d132e12d9afe52a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a748dd6b20d667ca6b95f1998c86da1df10b2cd83d9e8aca304224e469d6e137 +size 12533 diff --git a/marked/Rel-18/38_series/38741/fe753d01ad5fe6cf150018c958173c6d_img.jpg b/marked/Rel-18/38_series/38741/fe753d01ad5fe6cf150018c958173c6d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56a16544af331ce4fb58a37b1f774d50f150b675 --- /dev/null +++ b/marked/Rel-18/38_series/38741/fe753d01ad5fe6cf150018c958173c6d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a69d846efb2c5b7f777eb9ed10441fef58b48ad4539b577fd3f99cbf624230f3 +size 11306 diff --git a/marked/Rel-18/38_series/38741/fed39b841ae2dce01088b84bfc1e2789_img.jpg b/marked/Rel-18/38_series/38741/fed39b841ae2dce01088b84bfc1e2789_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..050f17f5b718f0fb814ce1c9233adc369d87abd8 --- /dev/null +++ b/marked/Rel-18/38_series/38741/fed39b841ae2dce01088b84bfc1e2789_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb52515c90e2cc9e2510c3af2bbafd1162fc5441c066a22f17a7f419ce085d55 +size 41417 diff --git a/marked/Rel-18/38_series/38741/raw.md b/marked/Rel-18/38_series/38741/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..109024c9c15ffb496cfcccf280b8020718ad67b0 --- /dev/null +++ b/marked/Rel-18/38_series/38741/raw.md @@ -0,0 +1,1260 @@ + + +# 3GPP TR 38.741 V18.0.0 (2023-12) + +*Technical Report* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Non-Terrestrial Networks (NTN) L-/S-band for NR; (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' in black with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black text to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon, and below the entire logo is the text 'A GLOBAL INITIATIVE' in small, black, uppercase letters. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|-----------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions of terms, symbols and abbreviations..... | 6 | +| 3.1 Terms..... | 6 | +| 3.2 Symbols..... | 6 | +| 3.3 Abbreviations ..... | 7 | +| 4 Background ..... | 8 | +| 5 Regulations..... | 8 | +| 5.1 FCC ..... | 8 | +| 5.1.1 47 CFR § 25.202..... | 8 | +| 5.1.2 47 CFR § 25.216..... | 8 | +| 5.2 ETSI ..... | 9 | +| 5.2.1 ETSI EN 301 441 ..... | 9 | +| 6 NR..... | 11 | +| 6.1 Band plan and system parameters ..... | 11 | +| 6.2 UE requirements..... | 12 | +| 6.2.1 UE transmitter characteristics..... | 13 | +| 6.2.1.1 Maximum output power..... | 13 | +| 6.2.1.2 MPR/A-MPR ..... | 13 | +| 6.2.1.2.1 Maximum power reduction ..... | 13 | +| 6.2.1.2.2 Additional maximum power reduction (company #1) ..... | 13 | +| 6.2.1.2.2.3 Power back-off results for FCC..... | 17 | +| 6.2.1.2.2.3.1 5MHz channel..... | 17 | +| 6.2.1.2.3 Additional maximum power reduction (company #2) ..... | 22 | +| 6.2.1.2.4 Additional maximum power reduction (company #3) ..... | 24 | +| 6.2.1.2.5 Harmonised A-MPR values ..... | 25 | +| 6.2.1.3 Emission requirements and NS values..... | 26 | +| 6.2.1.3a NS values and associated A-MPR ..... | 27 | +| 6.2.1.4 UE co-existence requirements ..... | 32 | +| 6.2.2 UE receiver characteristics ..... | 32 | +| 6.2.2.1 Reference sensitivity..... | 32 | +| 6.2.2.2 In-band blocking ..... | 33 | +| 6.2.2.3 Out-of-band blocking..... | 33 | +| 6.2.3 UE RRM requirements ..... | 33 | +| 6.3 SAN requirements ..... | 33 | +| Annex A (informative): Change history..... | 34 | + +# Foreword + +This Technical Specification/Report has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# 1 Scope + +The present document is a technical report for the work item of the NTN L-S-band. + +# 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.108: "NR; Satellite Access Node radio transmission and reception" + +# 3 Definitions of terms, symbols and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**Non-terrestrial networks:** Networks, or segments of networks, using an airborne or space-borne vehicle to embark a transmission equipment relay node or base station. + +**Satellite:** A space-borne vehicle embarking a bent pipe payload or a regenerative payload telecommunication transmitter, placed into Low-Earth Orbit (LEO), Medium-Earth Orbit (MEO), or Geostationary Earth Orbit (GEO). + +**Satellite Access Node:** see definition in TS 38.108 [2]. + +**UE transmission bandwidth configuration:** Set of resource blocks located within the UE channel bandwidth which may be used for transmitting or receiving by the UE. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------| +| $\Delta F_{\text{Global}}$ | Granularity of the global frequency raster | +| $\Delta F_{\text{Raster}}$ | Band dependent channel raster granularity | +| $BW_{\text{Channel}}$ | Channel bandwidth | +| $BW_{\text{interferer}}$ | Bandwidth of the interferer | +| $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 | +| $F_{\text{Interferer}}$ | Frequency of the interferer | +| $F_{\text{Interferer}}$ (offset) | Frequency offset of the interferer (between the center frequency of the interferer and the carrier frequency of the carrier measured) | + +| | | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------| +| $F_{\text{Ioffset}}$ | Frequency offset of the interferer (between the center frequency of the interferer and the closest edge of the carrier measured) | +| $F_{\text{OoB}}$ | The boundary between the NR out of band emission and spurious emission domains | +| $F_{\text{REF}}$ | RF reference frequency | +| $F_{\text{REF-Offs}}$ | Offset used for calculating $F_{\text{REF}}$ | +| $F_{\text{uw}}$ (offset) | The frequency separation of the center frequency of the carrier closest to the interferer and the center frequency of the interferer | +| $N_{\text{RB}}$ | Transmission bandwidth configuration, expressed in units of resource blocks | +| $N_{\text{REF}}$ | NR Absolute Radio Frequency Channel Number (NR-ARFCN) | +| $N_{\text{REF-Offs}}$ | Offset used for calculating $N_{\text{REF}}$ | +| $P_{\text{Interferer}}$ | Modulated mean power of the interferer | +| $P_{\text{uw}}$ | Power of an unwanted DL signal | + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|------------|------------------------------------------------------------------------| +| ACLR | Adjacent Channel Leakage Ratio | +| ACS | Adjacent Channel Selectivity | +| A-MPR | Additional Maximum Power Reduction | +| BW | Bandwidth | +| BWP | Bandwidth Part | +| CP-OFDM | Cyclic Prefix-OFDM | +| CW | Continuous Wave | +| DFT-s-OFDM | Discrete Fourier Transform-spread-OFDM | +| EIRP | Equivalent Isotropically Radiated Power | +| EVM | Error Vector Magnitude | +| FR | Frequency Range | +| FRC | Fixed Reference Channel | +| GEO | Geosynchronous Earth Orbit | +| GSCN | Global Synchronization Channel Number | +| IBB | In-band Blocking | +| ITU-R | Radiocommunication Sector of the International Telecommunication Union | +| LEO | Low Earth Orbiting | +| MOP | Maximum Output Power | +| MPR | Allowed maximum power reduction | +| MSD | Maximum Sensitivity Degradation | +| NR | New Radio | +| NR-ARFCN | NR Absolute Radio Frequency Channel Number | +| NS | Network Signalling | +| NTN | Non-Terrestrial Network | +| OOB | Out-of-band | +| PRB | Physical Resource Block | +| QAM | Quadrature Amplitude Modulation | +| RAN | Radio Access Network | +| RE | Resource Element | +| REFSENS | REference SENSitivity | +| RF | Radio Frequency | +| RMS | Root Mean Square (value) | +| RX | Receiver | +| SAN | Satellite Access Node | +| SC | Single Carrier | +| SCS | Subcarrier spacing | +| SEM | Spectrum Emission Mask | +| SNR | Signal-to-Noise Ratio | +| SS | Synchronization Symbol | +| TN | Terrestrial Network | +| TX | Transmitter | +| UE | User Equipment | + +# --- 4 Background + +3GPP RAN#86 meeting approved the Rel-17 WI that aimed to enable support of the 5G/NR radio access technology for non-terrestrial satellite deployments. One of the WI objectives was to define and introduce the corresponding bands into the 3GPP specifications. The outcome of these discussions was two NTN bands – L-band and S-band – which were added as bands n255 and n256, respectively. At the same time there exist other satellite deployments, some of which use mixed L-/S-band pairing, whereupon the UL part is on the L-band, while the DL part is on the S-band. To limit the overall workload in Rel-17, it was decided by RAN WG4 to focus on L- and S-bands with the common understanding that other potential NTN bands should follow the "normal" process of submitting a new spectrum WI. + +3GPP RAN#98 meeting agreed a new spectrum WI to add support for a new NTN band with the DL part on the S-band (2500MHz) and the UL part on the L-band (1600MHz). + +# --- 5 Regulations + +NOTE: The purpose of this section is to collect information from existing regulatory documents concerning regulatory rules applicable to this NTN L-/S-band. + +## 5.1 FCC + +### 5.1.1 47 CFR § 25.202 + +According to paragraph (a)(4)(i), the following frequencies are available for use by the 1.6/2.4 GHz Mobile-Satellite Service: + +- 1610-1626.5 MHz: User-to-Satellite Link +- 1613.8-1626.5 MHz: Satellite-to-User Link (secondary) +- 2483.5-2500 MHz: Satellite-to-User Link + +According to paragraph (f) on emission limitations, except for SDARS terrestrial repeaters and as provided for in paragraph (i), the mean power of emissions shall be attenuated below the mean output power of the transmitter in accordance with the schedule set forth in paragraphs (f)(1) through (f)(4) of this section: + +- (1) In any 4 kHz band, the center frequency of which is removed from the assigned frequency by more than 50 percent up to and including 100 percent of the authorized bandwidth: 25 dB; +- (2) In any 4 kHz band, the center frequency of which is removed from the assigned frequency by more than 100 percent up to and including 250 percent of the authorized bandwidth: 35 dB; +- (3) In any 4 kHz band, the center frequency of which is removed from the assigned frequency by more than 250 percent of the authorized bandwidth: An amount equal to 43 dB plus 10 times the logarithm (to the base 10) of the transmitter power in watts; +- (4) In any event, when an emission outside of the authorized bandwidth causes harmful interference, the Commission may, at its discretion, require greater attenuation than specified in paragraphs (f) (1), (2) and (3) of this section. + +### 5.1.2 47 CFR § 25.216 + +(c) The e.i.r.p. density of emissions from mobile earth stations placed in service after July 21, 2002 with assigned uplink frequencies between 1610 MHz and 1660.5 MHz shall not exceed –70 dBW/MHz, averaged over any 2 millisecond active transmission interval, in the band 1559-1605 MHz. The e.i.r.p. of discrete emissions of less than 700 Hz bandwidth from such stations shall not exceed –80 dBW, averaged over any 2 millisecond active transmission interval, in the 1559-1605 MHz band. + +## 5.2 ETSI + +### 5.2.1 ETSI EN 301 441 + +**Table 5.2.1-1: Mobile Satellite Service frequency bands** + +| MES | MSS frequency bands | +|----------|---------------------| +| Transmit | 1610 – 1626.5 MHz | +| Receive | 1613.8 – 1626.5 MHz | +| Receive | 2483.5 – 2500 MHz | + +**Table 5.2.1-2: Maximum unwanted emissions outside the band 1610 MHz to 1626.5 MHz and the band 1626.5 MHz to 1628.5MHz.** + +| Frequency (MHz) | Carrier-on | | | +|------------------|------------|-----------------------|--------------------| +| | EIRP (dBW) | Measurement bandwidth | Measurement method | +| 0.1 to 30 | -66 | 10 kHz | Peak-hold | +| 30 to 1 000 | -66 | 100 kHz | Peak-hold | +| 1000 to 1559 | -60 | 1 MHz | Average | +| 1559 to 1580.42 | -70 | 1 MHz | Average | +| 1580.42 to 1605 | -70 | 1 MHz | Average | +| 1605 to 1610 | -70 to -10 | 1 MHz | Average | +| 1610 to 1626.5 | N/A | N/A | N/A | +| 1626.5 to 1628.5 | N/A | N/A | N/A | +| 1628.5 to 1631.5 | -60 | 30 kHz | Average | +| 1631.5 to 1636.5 | -60 | 100 kHz | Average | +| 1636.5 to 1646.5 | -60 | 300 kHz | Average | +| 1646.5 to 1666.5 | -60 | 1 MHz | Average | +| 1666.5 to 2200 | -60 | 3 MHz | Average | +| 2200 to 12750 | -60 | 3 MHz | Peak-hold | + +NOTE 1: In the sub-band 1 573,42 MHz to 1 580,42 MHz, the average measurement time is 20 ms. + +NOTE 2: Linearly interpolated in dBW vs. frequency offset. + +**Table 5.2.1-3: Maximum unwanted emissions within the band 1610MHz to 1 626.5MHz and the band 1626.5 MHz to 1628.5MHz of MES operating such that the nominated bandwidth is entirely or partially contained in the frequency band 1618.25 MHz to 1626.5MHz.** + +| Frequency offset (kHz) | Carrier-on | | | +|------------------------|--------------|-----------------------|--------------------| +| | EIRP (dBW) | Measurement bandwidth | Measurement method | +| 0 to 160 | -35 | 30 kHz | Average | +| 160 to 225 | -35 to -38.5 | 30 kHz | Average | +| 225 to 650 | -38.5 to -45 | 30 kHz | Average | +| 650 to 1365 | -45 | 30 kHz | Average | +| 1365 to 1800 | -53 to -56 | 30 kHz | Average | +| 1800 to 16500 | -56 | 30 kHz | Average | + +NOTE 1: Frequency offset is determined from: i) the nearest edge of the nominated bandwidth of the nominal carrier closest to the MSS system operating in another operational band within the band 1 610 MHz to 1 626,5 MHz. The frequency offset is measured in the direction of the adjacent MSS system; ii) the upper edge of the nominated bandwidth of the carrier under test for emissions within the band 1626.5MHz to 1628.5MHz. + +NOTE 2: The measurement bandwidth used may be 3 kHz if the unwanted EIRP limits are reduced correspondingly. + +NOTE 3: Linearly interpolated in dBW vs. frequency offset. + +**Table 5.2.1-4: Maximum unwanted emissions within the band 1610MHz to 1626.5 MHz and the band 1626.5MHz to 1628.5MHz of MES operating such that the nominated bandwidth is entirely contained in the frequency band 1610MHz to 1618.25MHz.** + +| Frequency offset (kHz) | Carrier-on | | | +|------------------------|------------|-----------------------|--------------------| +| | EIRP (dBW) | Measurement bandwidth | Measurement method | +| 0 to 160 | -32 | 30 kHz | Average | +| 160 to 2300 | -32 to -56 | 30 kHz | Average | +| 2300 to 18500 | -56 | 30 kHz | Average | + +NOTE 1: Frequency offset is determined from: i) the nearest edge of the nominated bandwidth of the nominal carrier closest to the MSS system operating in another operational band within the band 1 610 to 1 626,5 MHz The frequency offset is measured in the direction of the adjacent MSS system; ii) the upper edge of the nominated bandwidth of the carrier under test for emissions within the band 1626.5 to 1628.5MHz. + +NOTE 2: The measurement bandwidth used may be 3 kHz if the unwanted EIRP limits are reduced correspondingly. + +NOTE 3: Linearly interpolated in dBW vs. frequency offset. + +**Table 5.2.1-5: Maximum unwanted emissions of MES carriers within the operational band of CDMA carriers.** + +| Frequency offset (kHz) | Carrier-on | | | +|------------------------|------------|-----------------------|--------------------| +| | EIRP (dBW) | Measurement bandwidth | Measurement method | +| 0 to 70 | -6 to -20 | 30 kHz | Average | +| 70 to 600 | -20 to -28 | 30 kHz | Average | +| 600 to 2000 | -28 to -45 | 30 kHz | Average | +| 2000 to 5000 | -45 to -69 | 30 kHz | Average | +| 5000 to 16500 | -69 | 30 kHz | Average | + +NOTE 1: Frequency offset is determined from edge of nominated bandwidth. + +NOTE 2: Linearly interpolated in dBW vs. frequency offset. + +The frequency offset and relative power level of the adjacent signal compared to the wanted signal shall take the values given in table 5.2.1-6. The adjacent signal shall occupy the same bandwidth as the wanted signal where BW is the wanted signal occupied bandwidth. There shall be no more than 0.5dB degradation in the receiver signal to noise ratio under these conditions. + +**Table 5.2.1-6: Adjacent Channel frequency and power level** + +| Signal | Centre frequency offset from wanted signal | Power level relative to wanted signal | +|-----------------|--------------------------------------------|---------------------------------------| +| Adjacent signal | Signal bandwidth | 12 dB | + +Receiver blocking characteristics are to prevent high power signals outside the receive frequency band from blocking the reception of signals inside the receive frequency band. The blocking characteristic is a measure of the receiver's ability to receive a wanted signal at its assigned channel frequency in the presence of an unwanted interferer on frequencies other than those of the spurious response or the adjacent channels, without this unwanted input signal causing a degradation of the performance of the receiver beyond a specified limit. Receiver blocking is specified for in-band signals. In-band signals are signals in the range: + +BEL-10MHz to BEU +10 MHz, where BEL and BEU are the lower and upper edges of the operating band respectively. + +The receiver performance degradation, in terms of signal to noise ratio, shall not exceed 1dB when the unwanted signal as specified in Table 5.2.1-7 is present. + +Table 5.2.1-7: Test parameters for in-band blocking characteristics + +| Interfering Signal | In-band Frequency Range (MHz) | Frequency offset from wanted carrier (MHz) | Level (dBm) | +|--------------------|---------------------------------------------------|--------------------------------------------|-------------| +| CW | BE L -10MHz to BE U +10 MHz | 5 | -40 | + +# 6 NR + +## 6.1 Band plan and system parameters + +Table 6.1-1: NTN L-/S-band n254 + +| NTN satellite operating band | Uplink (UL) operating band
Satellite Access Node receive / UE transmit
$F_{UL,low} - F_{UL,high}$ | Downlink (DL) operating band
Satellite Access Node transmit / UE receive
$F_{DL,low} - F_{DL,high}$ | Duplex mode | +|------------------------------|---------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|-------------| +| n254 | 1610 – 1626.5 MHz | 2483.5 – 2500 MHz | FDD | + +NOTE: NTN satellite bands are numbered in descending order from n256. + +Table 6.1-2: NTN L-/S-band n254 channel bandwidths + +| NTN satellite band | SCS kHz | UE Channel bandwidth (MHz) | | | | +|--------------------|---------|----------------------------|----|----|--| +| | | 5 | 10 | 15 | | +| n254 | 15 | 5 | 10 | 15 | | +| | 30 | | 10 | 15 | | +| | 60 | | 10 | 15 | | + +Table 6.1-3: NTN L-/S-band n254 applicable NR-ARFCN + +| NTN satellite operating band | $\Delta F_{Raster}$ (kHz) | Uplink Range of N REF
(First – – Last) | Downlink Range of N REF
(First – – Last) | +|------------------------------|---------------------------|------------------------------------------------------------------|--------------------------------------------------------------------| +| n254 | 100 | 322000 – <20> – 325300 | 496700 – <20> – 500000 | + +NOTE: 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. + +Table 6.1-4: NTN L-/S-band n254 applicable SS raster entries + +| NTN satellite operating band | SS Block SCS | SS Block pattern 1 | Range of GSCN
(First – – Last) | +|------------------------------|--------------|-------------------------------|-----------------------------------------------| +| n254 | 15kHz | Case A | 6215 – <1> – 6244 | +| | 30 kHz | Case C | 6218 – <1> – 6241 | + +NOTE: SS Block pattern is defined in clause 4.1 in 3GPP TS 38.213 [7]. + +Table 6.1-5: NTN L-/S-band asymmetric UL and DL channel bandwidth combinations + +| NR Band | Channel bandwidths for UL (MHz) | Channel bandwidths for DL (MHz) | Asymmetric channel bandwidth combination set | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|---------------------------------|----------------------------------------------| +| n254 | 5 | 10,15 | 0 | +| | 10 | 15 | 0 | +| NOTE 1: The assignment of the paired UL and DL channels are subject to a TX-RX separation as specified in clause 5.4.4.
NOTE 2: As indicated in TS38.306 [15], it is mandatory for UEs to support asymmetric channel BCS0 if there is an asymmetric BCS0 defined for the band. | | | | + +Table 6.1-6: NTN L-/S-band UE TX-RX frequency separation + +| NTN Satellite Operating Band | TX – RX carrier centre frequency separation | +|------------------------------|---------------------------------------------| +| n254 | 862 – 885 MHz | + +## 6.2 UE requirements + +Table 6.2-1 and 6.2-2 below summarise UE Tx and Rx requirements indicating which requirements are specific for this band and, if so, are captured in the corresponding sub-clauses of this TR. + +Table 6.2-1: NTN L-/S-band TX requirements + +| Tx requirements | | +|------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| +| 6.2.1 Maximum output power | clause 6.2.1.1 | +| 6.2.2 MPR | clause 6.2.1.2 | +| 6.2.3 A-MPR | clause 6.2.1.3 | +| 6.2.4 Configured transmitted power | reuse TS 38.101-5 requirement | +| 6.3.1 Minimum output power | reuse TS 38.101-5 requirement | +| 6.3.2 Transmit OFF power | reuse TS 38.101-5 requirement | +| 6.3.3 Transmit ON/OFF time mask | reuse TS 38.101-5 requirement | +| 6.3.4 Power control | reuse TS 38.101-5 requirement | +| 6.4.1 Frequency error | reuse TS 38.101-5 requirement | +| 6.4.2 Transmit modulation quality | reuse TS 38.101-5 requirement | +| 6.5.1 Occupied bandwidth | reuse TS 38.101-5 requirement | +| 6.5.2 Out of band emission | reuse TS 38.101-5 requirement | +| 6.5.3 Spurious emission | additional spurious emission in clause 6.2.1.3
co-existence requirement in clause 6.2.1.4
for other requirements reuse TS 38.101-5 requirement | +| 6.5.4 Transmit intermodulation | reuse TS 38.101-5 requirement | + +Table 6.2-2: NTN L-/S-band RX requirements + +| Rx requirement | | +|-------------------------------------|------------------------------------------------------------------------------| +| 7.3 Reference sensitivity | clause 6.2.2.1 | +| 7.4 Maximum input level | reuse TS 38.101-5 requirement | +| 7.5 Adjacent channel selectivity | reuse TS 38.101-5 requirement | +| 7.6 Blocking characteristics | in-band blocking in clause 6.2.2.2
out-of-band blocking in clause 6.2.2.3 | +| 7.7 Spurious response | reuse TS 38.101-5 requirement | +| 7.8 Intermodulation characteristics | reuse TS 38.101-5 requirement | +| 7.9 Spurious emissions | reuse TS 38.101-5 requirement | + +### 6.2.1 UE transmitter characteristics + +#### 6.2.1.1 Maximum output power + +**Table 6.2.1.1-1: NTN L-/S-band n254 Power Class** + +| NR satellite band | Class 3 (dBm) | Tolerance (dB) | +|-------------------|---------------|----------------| +| n254 | 23 | ±2 | + +NOTE 1: $P_{\text{PowerClass}}$ is the maximum UE power specified without taking into account the tolerance +NOTE 2: Power class 3 is default power class unless otherwise stated + +#### 6.2.1.2 MPR/A-MPR + +##### 6.2.1.2.1 Maximum power reduction + +Maximum power reduction for the NTN L-/S-band is the same as for other NTN bands, such as L-band n255 and S-band n256. + +**Table 6.2.1.2.1-1: Maximum power reduction (MPR) for power class 3.** + +| Modulation | | MPR (dB) | | | +|------------|----------------------------|---------------------|----------------------|----------------------| +| | | Edge RB allocations | Outer RB allocations | Inner RB allocations | +| DFT-s-OFDM | Pi/2 BPSK | $\leq 3.5^1$ | $\leq 1.2^1$ | $\leq 0.2^1$ | +| | | $\leq 0.5^2$ | $\leq 0.5^2$ | $0^2$ | +| | Pi/2 BPSK w Pi/2 BPSK DMRS | $\leq 0.5^2$ | $0^2$ | $0^2$ | +| | QPSK | $\leq 1$ | | 0 | +| | 16 QAM | $\leq 2$ | | $\leq 1$ | +| | 64 QAM | $\leq 2.5$ | | | +| CP-OFDM | 256 QAM | $\leq 4.5$ | | | +| | QPSK | $\leq 3$ | | $\leq 1.5$ | +| | 16 QAM | $\leq 3$ | | $\leq 2$ | +| | 64 QAM | $\leq 3.5$ | | | +| | 256 QAM | $\leq 6.5$ | | | + +NOTE 1: Applicable for UE operating in TDD mode with Pi/2 BPSK modulation and UE indicates support for UE capability *powerBoosting-pi2BPSK* and if the IE *powerBoostPi2BPSK* is set to 1 and 40 % or less slots in radio frame are used for UL transmission for bands n40, n41, n77, n78 and n79. The reference power of 0 dB MPR is 26 dBm. +NOTE 2: Applicable for UE operating in FDD mode, or in TDD mode in bands other than n40, n41, n77, n78 and n79 with Pi/2 BPSK modulation and if the IE *powerBoostPi2BPSK* is set to 0 and if more than 40 % of slots in radio frame are used for UL transmission for bands n40, n41, n77, n78 and n79. + +##### 6.2.1.2.2 Additional maximum power reduction (company #1) + +Maximum power reduction for the NTN L-/S-band is the same as for other NTN bands, such as L-band n255 and S-band n256. + +###### 6.2.1.2.2.1 Configuration cases + +For the power back-off simulations the following common parameters are assumed: + +- Tx power: PC3 +23dBm +- LO placement: always in the centre of the carrier +- Regulations: ETSI and FCC + +The following channel sizes with centre frequencies are considered: + +- NR 5MHz channel at the following centre frequencies: + - a) Fc=1612.5MHz + - b) Fc=1613.9MHz + - c) Fc=1615.5MHz + - d) Fc=1620.5MHz + - e) Fc=1622.4MHz + - f) Fc=1624MHz + +- NR 10MHz channel at the following centre frequencies: + - a) Fc=1615MHz. + - b) Fc=1620MHz + - c) Fc=1621.5MHz + +- NR 15MHz channel at the following centre frequencies: + - a) Fc=1617.5MHz + - b) Fc=1619MHz + +![Diagram showing various NR channel widths (5 MHz, 10 MHz, 15 MHz) and their center frequencies (Fc) within a 1610 MHz to 1626.5 MHz frequency band. The diagram includes labels for Fc values such as 1612.5 MHz, 1613.9 MHz, 1615.5 MHz, 1615 MHz, 1617.5 MHz, 1619 MHz, 1620.5 MHz, 1620 MHz, 1621.5 MHz, 1622.4 MHz, and 1624 MHz. Vertical dashed lines mark the 1610 MHz, 1618 MHz, and 1626.5 MHz boundaries.](411fa16c3211377525ba37c57784fee0_img.jpg) + +The diagram illustrates the frequency spectrum for A-MPR simulations, spanning from 1610 MHz to 1626.5 MHz. It shows the placement of various channel widths: 5 MHz, 10 MHz, and 15 MHz. The center frequencies (Fc) for these channels are as follows: + +- 5 MHz channels: Fc = 1612.5 MHz, Fc = 1613.9 MHz, Fc = 1615.5 MHz, Fc = 1620.5 MHz, Fc = 1622.4 MHz, Fc = 1624 MHz. +- 10 MHz channels: Fc = 1615 MHz, Fc = 1620.1 MHz, Fc = 1621.5 MHz. +- 15 MHz channels: Fc = 1617.5 MHz, Fc = 1619 MHz. + +Vertical dashed lines indicate the boundaries at 1610 MHz, 1618 MHz, and 1626.5 MHz. + +Diagram showing various NR channel widths (5 MHz, 10 MHz, 15 MHz) and their center frequencies (Fc) within a 1610 MHz to 1626.5 MHz frequency band. The diagram includes labels for Fc values such as 1612.5 MHz, 1613.9 MHz, 1615.5 MHz, 1615 MHz, 1617.5 MHz, 1619 MHz, 1620.5 MHz, 1620 MHz, 1621.5 MHz, 1622.4 MHz, and 1624 MHz. Vertical dashed lines mark the 1610 MHz, 1618 MHz, and 1626.5 MHz boundaries. + +Figure 6.2.1.2.2.1-1: Considered channels for A-MPR simulations. + +6.2.1.2.2.2 Power back-off results for ETSI + +6.2.1.2.2.2.1 5MHz channel + +![Heatmap for DFT-s-OFDM PI2BPSK at Fc=1612.5MHz. The plot shows power back-off values for RBStart (0 to 25) and LCRB (0 to 25). The color scale ranges from 0 to 2.5. Most values are low, with some higher values at the edges.](0a8d173734e4e46c344178e8d21bcbc3_img.jpg) + +Heatmap for DFT-s-OFDM PI2BPSK at Fc=1612.5MHz. The plot shows power back-off values for RBStart (0 to 25) and LCRB (0 to 25). The color scale ranges from 0 to 2.5. Most values are low, with some higher values at the edges. + +![Heatmap for DFT-s-OFDM QPSK at Fc=1612.5MHz. The plot shows power back-off values for RBStart (0 to 25) and LCRB (0 to 25). The color scale ranges from 0 to 3.5. There is a more pronounced diagonal pattern of higher values compared to the PI2BPSK plot.](fe753d01ad5fe6cf150018c958173c6d_img.jpg) + +Heatmap for DFT-s-OFDM QPSK at Fc=1612.5MHz. The plot shows power back-off values for RBStart (0 to 25) and LCRB (0 to 25). The color scale ranges from 0 to 3.5. There is a more pronounced diagonal pattern of higher values compared to the PI2BPSK plot. + +![Heatmap for CP-OFDM QPSK at Fc=1612.5MHz. The plot shows power back-off values for RBStart (0 to 25) and LCRB (0 to 25). The color scale ranges from 0 to 6. This plot shows a very strong diagonal pattern of high power back-off values.](1145fc59efdc7dacc8d3c715d7ff3248_img.jpg) + +Heatmap for CP-OFDM QPSK at Fc=1612.5MHz. The plot shows power back-off values for RBStart (0 to 25) and LCRB (0 to 25). The color scale ranges from 0 to 6. This plot shows a very strong diagonal pattern of high power back-off values. + +Figure 6.2.1.2.2.2.1-1: Power back-off values for the 5MHz channel at Fc=1612.5MHz. + +![Heatmap for DFT-s-OFDM PI2BPSK at Fc=1613.9MHz. The plot shows power back-off values for RBStart (0 to 25) and LCRB (0 to 25). The color scale ranges from 0 to 1. The values are mostly low.](cc8bec39d25eb0aafb5382c05f0d5deb_img.jpg) + +Heatmap for DFT-s-OFDM PI2BPSK at Fc=1613.9MHz. The plot shows power back-off values for RBStart (0 to 25) and LCRB (0 to 25). The color scale ranges from 0 to 1. The values are mostly low. + +![Heatmap for DFT-s-OFDM QPSK at Fc=1613.9MHz. The plot shows power back-off values for RBStart (0 to 25) and LCRB (0 to 25). The color scale ranges from 0 to 2.5. A diagonal pattern of higher values is visible.](4a8166688ed7276efb173f550ba47eb4_img.jpg) + +Heatmap for DFT-s-OFDM QPSK at Fc=1613.9MHz. The plot shows power back-off values for RBStart (0 to 25) and LCRB (0 to 25). The color scale ranges from 0 to 2.5. A diagonal pattern of higher values is visible. + +![Heatmap for CP-OFDM QPSK at Fc=1613.9MHz. The plot shows power back-off values for RBStart (0 to 25) and LCRB (0 to 25). The color scale ranges from 0 to 4. A strong diagonal pattern of high values is visible.](28487ff44b62fdcb48c6f38153c35495_img.jpg) + +Heatmap for CP-OFDM QPSK at Fc=1613.9MHz. The plot shows power back-off values for RBStart (0 to 25) and LCRB (0 to 25). The color scale ranges from 0 to 4. A strong diagonal pattern of high values is visible. + +Figure 6.2.1.2.2.2.1-2: Power back-off values for the 5MHz channel at Fc=1613.9MHz. + +![Heatmap for DFT-s-OFDM PI2BPSK at Fc=1615.5MHz. The plot shows power back-off values for RBStart (0 to 25) and LCRB (0 to 25). The color scale ranges from 0 to 0.5. The values are mostly low.](5c962f53272b4722e5d88f049e25084f_img.jpg) + +Heatmap for DFT-s-OFDM PI2BPSK at Fc=1615.5MHz. The plot shows power back-off values for RBStart (0 to 25) and LCRB (0 to 25). The color scale ranges from 0 to 0.5. The values are mostly low. + +![Heatmap for DFT-s-OFDM QPSK at Fc=1615.5MHz. The plot shows power back-off values for RBStart (0 to 25) and LCRB (0 to 25). The color scale ranges from 0 to 1. A diagonal pattern of higher values is visible.](a2f89834a149b852721f8887349fd6fa_img.jpg) + +Heatmap for DFT-s-OFDM QPSK at Fc=1615.5MHz. The plot shows power back-off values for RBStart (0 to 25) and LCRB (0 to 25). The color scale ranges from 0 to 1. A diagonal pattern of higher values is visible. + +![Heatmap for CP-OFDM QPSK at Fc=1615.5MHz. The plot shows power back-off values for RBStart (0 to 25) and LCRB (0 to 25). The color scale ranges from 0 to 3. A strong diagonal pattern of high values is visible.](c260fa717b624233542a7116e022e771_img.jpg) + +Heatmap for CP-OFDM QPSK at Fc=1615.5MHz. The plot shows power back-off values for RBStart (0 to 25) and LCRB (0 to 25). The color scale ranges from 0 to 3. A strong diagonal pattern of high values is visible. + +Figure 6.2.1.2.2.2.1-3: Power back-off values for the 5MHz channel at Fc=1615.5MHz. + +![Heatmap for DFT-s-OFDM PI2BPSK at Fc=1620.5MHz. The plot shows power back-off values for RBStart (0 to 25) and LCRB (0 to 25). The color scale ranges from 0 to 0.5. The values are mostly low.](88362167d90777ecb0aeb145832e78c2_img.jpg) + +Heatmap for DFT-s-OFDM PI2BPSK at Fc=1620.5MHz. The plot shows power back-off values for RBStart (0 to 25) and LCRB (0 to 25). The color scale ranges from 0 to 0.5. The values are mostly low. + +![Heatmap for DFT-s-OFDM QPSK at Fc=1620.5MHz. The plot shows power back-off values for RBStart (0 to 25) and LCRB (0 to 25). The color scale ranges from 0 to 1. A diagonal pattern of higher values is visible.](dfd60da6d5e7618f3122c129506e105e_img.jpg) + +Heatmap for DFT-s-OFDM QPSK at Fc=1620.5MHz. The plot shows power back-off values for RBStart (0 to 25) and LCRB (0 to 25). The color scale ranges from 0 to 1. A diagonal pattern of higher values is visible. + +![Heatmap for CP-OFDM QPSK at Fc=1620.5MHz. The plot shows power back-off values for RBStart (0 to 25) and LCRB (0 to 25). The color scale ranges from 0 to 3. A strong diagonal pattern of high values is visible.](d29d72755dd131d215d854aaf90fea3e_img.jpg) + +Heatmap for CP-OFDM QPSK at Fc=1620.5MHz. The plot shows power back-off values for RBStart (0 to 25) and LCRB (0 to 25). The color scale ranges from 0 to 3. A strong diagonal pattern of high values is visible. + +Figure 6.2.1.2.2.2.1-4: Power back-off values for the 5MHz channel at Fc=1620.5MHz. + +![Heatmap for DFT-s-OFDM PI2BPSK at Fc=1622.4MHz, BW=5MHz, SCS=15kHz. The plot shows power back-off values across RBStart (0 to 25) and LCRB (0 to 25). The color scale ranges from 0 to 1.](cbc4516eb885829fe8c9dabc0946dcbe_img.jpg) + +Heatmap for DFT-s-OFDM PI2BPSK at Fc=1622.4MHz, BW=5MHz, SCS=15kHz. The plot shows power back-off values across RBStart (0 to 25) and LCRB (0 to 25). The color scale ranges from 0 to 1. + +![Heatmap for DFT-s-OFDM QPSK at Fc=1622.4MHz, BW=5MHz, SCS=15kHz. The plot shows power back-off values across RBStart (0 to 25) and LCRB (0 to 25). The color scale ranges from 0 to 1.](e95f47f7a4c01c8889d6d46919b4c73d_img.jpg) + +Heatmap for DFT-s-OFDM QPSK at Fc=1622.4MHz, BW=5MHz, SCS=15kHz. The plot shows power back-off values across RBStart (0 to 25) and LCRB (0 to 25). The color scale ranges from 0 to 1. + +![Heatmap for CP-OFDM QPSK at Fc=1622.4MHz, BW=5MHz, SCS=15kHz. The plot shows power back-off values across RBStart (0 to 25) and LCRB (0 to 25). The color scale ranges from 0 to 3.](fc857414626a8d94d132e12d9afe52a4_img.jpg) + +Heatmap for CP-OFDM QPSK at Fc=1622.4MHz, BW=5MHz, SCS=15kHz. The plot shows power back-off values across RBStart (0 to 25) and LCRB (0 to 25). The color scale ranges from 0 to 3. + +Figure 6.2.1.2.2.2.1-5: Power back-off values for the 5MHz channel at Fc=1622.4MHz. + +![Heatmap for DFT-s-OFDM PI2BPSK at Fc=1624MHz, BW=5MHz, SCS=15kHz. The plot shows power back-off values across RBStart (0 to 25) and LCRB (0 to 25). The color scale ranges from 0 to 1.5.](a430996a9e8993deb0c6b25da234744b_img.jpg) + +Heatmap for DFT-s-OFDM PI2BPSK at Fc=1624MHz, BW=5MHz, SCS=15kHz. The plot shows power back-off values across RBStart (0 to 25) and LCRB (0 to 25). The color scale ranges from 0 to 1.5. + +![Heatmap for DFT-s-OFDM QPSK at Fc=1624MHz, BW=5MHz, SCS=15kHz. The plot shows power back-off values across RBStart (0 to 25) and LCRB (0 to 25). The color scale ranges from 0 to 1.5.](0bd23f00e0632855cfef9274f1ab93d8_img.jpg) + +Heatmap for DFT-s-OFDM QPSK at Fc=1624MHz, BW=5MHz, SCS=15kHz. The plot shows power back-off values across RBStart (0 to 25) and LCRB (0 to 25). The color scale ranges from 0 to 1.5. + +![Heatmap for CP-OFDM QPSK at Fc=1624MHz, BW=5MHz, SCS=15kHz. The plot shows power back-off values across RBStart (0 to 25) and LCRB (0 to 25). The color scale ranges from 0 to 3.](865a630eb1b708bd28250dfeb33dd8f1_img.jpg) + +Heatmap for CP-OFDM QPSK at Fc=1624MHz, BW=5MHz, SCS=15kHz. The plot shows power back-off values across RBStart (0 to 25) and LCRB (0 to 25). The color scale ranges from 0 to 3. + +Figure 6.2.1.2.2.2.1-6: Power back-off values for the 5MHz channel at Fc=1624MHz. + +###### 6.2.1.2.2.2.2 + +###### 10MHz channel + +![Heatmap for DFT-s-OFDM PI2BPSK at Fc=1615MHz, BW=10MHz, SCS=15kHz. The plot shows power back-off values across RBStart (0 to 50) and LCRB (0 to 50). The color scale ranges from 0 to 6.](6ba2b00e9434aa86af566824b1c1446b_img.jpg) + +Heatmap for DFT-s-OFDM PI2BPSK at Fc=1615MHz, BW=10MHz, SCS=15kHz. The plot shows power back-off values across RBStart (0 to 50) and LCRB (0 to 50). The color scale ranges from 0 to 6. + +![Heatmap for DFT-s-OFDM QPSK at Fc=1615MHz, BW=10MHz, SCS=15kHz. The plot shows power back-off values across RBStart (0 to 50) and LCRB (0 to 50). The color scale ranges from 0 to 7.](a3c02bfac05114bb808134408d67f20b_img.jpg) + +Heatmap for DFT-s-OFDM QPSK at Fc=1615MHz, BW=10MHz, SCS=15kHz. The plot shows power back-off values across RBStart (0 to 50) and LCRB (0 to 50). The color scale ranges from 0 to 7. + +![Heatmap for CP-OFDM QPSK at Fc=1615MHz, BW=10MHz, SCS=15kHz. The plot shows power back-off values across RBStart (0 to 50) and LCRB (0 to 50). The color scale ranges from 0 to 12.5.](d00a096e2b5e638235ecd1834e48f706_img.jpg) + +Heatmap for CP-OFDM QPSK at Fc=1615MHz, BW=10MHz, SCS=15kHz. The plot shows power back-off values across RBStart (0 to 50) and LCRB (0 to 50). The color scale ranges from 0 to 12.5. + +Figure 6.2.1.2.2.2.2-1: Power back-off values for the 10MHz channel at Fc=1615MHz. + +![Heatmap for DFT-s-OFDM PI2BPSK at Fc=1620MHz, BW=10MHz, SCS=15kHz. The plot shows power back-off values across RBStart (0 to 50) and LCRB (0 to 50). The color scale ranges from 0 to 2.](595d7ce1dd65a29378ac2c96922a866a_img.jpg) + +Heatmap for DFT-s-OFDM PI2BPSK at Fc=1620MHz, BW=10MHz, SCS=15kHz. The plot shows power back-off values across RBStart (0 to 50) and LCRB (0 to 50). The color scale ranges from 0 to 2. + +![Heatmap for DFT-s-OFDM QPSK at Fc=1620MHz, BW=10MHz, SCS=15kHz. The plot shows power back-off values across RBStart (0 to 50) and LCRB (0 to 50). The color scale ranges from 0 to 3.](35a929c866c4c49f4aa4e7103b8a0b9b_img.jpg) + +Heatmap for DFT-s-OFDM QPSK at Fc=1620MHz, BW=10MHz, SCS=15kHz. The plot shows power back-off values across RBStart (0 to 50) and LCRB (0 to 50). The color scale ranges from 0 to 3. + +![Heatmap for CP-OFDM QPSK at Fc=1620MHz, BW=10MHz, SCS=15kHz. The plot shows power back-off values across RBStart (0 to 50) and LCRB (0 to 50). The color scale ranges from 0 to 4.](dffef2e70b14b1e00e5a5e1b8b34d722_img.jpg) + +Heatmap for CP-OFDM QPSK at Fc=1620MHz, BW=10MHz, SCS=15kHz. The plot shows power back-off values across RBStart (0 to 50) and LCRB (0 to 50). The color scale ranges from 0 to 4. + +Figure 6.2.1.2.2.2.2-2: Power back-off values for the 10MHz channel at Fc=1620MHz. + +![Three heatmaps showing power back-off values for a 10MHz channel at Fc=1621.5MHz. The plots are for DFT-s-OFDM PI2BPSK, DFT-s-OFDM QPSK, and CP-OFDM QPSK. The x-axis is RBStart (0 to 50) and the y-axis is LCRB (0 to 50). The color scale represents power back-off values from 0 to 4 dB.](fed39b841ae2dce01088b84bfc1e2789_img.jpg) + +Three heatmaps showing power back-off values for a 10MHz channel at Fc=1621.5MHz. The plots are for DFT-s-OFDM PI2BPSK, DFT-s-OFDM QPSK, and CP-OFDM QPSK. The x-axis is RBStart (0 to 50) and the y-axis is LCRB (0 to 50). The color scale represents power back-off values from 0 to 4 dB. + +Figure 6.2.1.2.2.2.2-3: Power back-off values for the 10MHz channel at Fc=1621.5MHz. + +###### 6.2.1.2.2.2.3 15MHz channel + +![Three heatmaps showing power back-off values for a 15MHz channel at Fc=1617.5MHz. The plots are for DFT-s-OFDM PI2BPSK, DFT-s-OFDM QPSK, and CP-OFDM QPSK. The x-axis is RBStart (0 to 70) and the y-axis is LCRB (0 to 70). The color scale represents power back-off values from 0 to 13.5 dB.](62ad98a4bc47922b5cf47de04571dae8_img.jpg) + +Three heatmaps showing power back-off values for a 15MHz channel at Fc=1617.5MHz. The plots are for DFT-s-OFDM PI2BPSK, DFT-s-OFDM QPSK, and CP-OFDM QPSK. The x-axis is RBStart (0 to 70) and the y-axis is LCRB (0 to 70). The color scale represents power back-off values from 0 to 13.5 dB. + +Figure 6.2.1.2.2.2.3-1: Power back-off values for the 15MHz channel at Fc=1617.5MHz. + +![Three heatmaps showing power back-off values for a 15MHz channel at Fc=1619MHz. The plots are for DFT-s-OFDM PI2BPSK, DFT-s-OFDM QPSK, and CP-OFDM QPSK. The x-axis is RBStart (0 to 70) and the y-axis is LCRB (0 to 70). The color scale represents power back-off values from 0 to 11 dB.](67518cfe156890dac13b5e67abd10dc1_img.jpg) + +Three heatmaps showing power back-off values for a 15MHz channel at Fc=1619MHz. The plots are for DFT-s-OFDM PI2BPSK, DFT-s-OFDM QPSK, and CP-OFDM QPSK. The x-axis is RBStart (0 to 70) and the y-axis is LCRB (0 to 70). The color scale represents power back-off values from 0 to 11 dB. + +Figure 6.2.1.2.2.2.3-2: Power back-off values for the 15MHz channel at Fc=1619MHz. + +###### 6.2.1.2.2.3 Power back-off results for FCC + +###### 6.2.1.2.2.3.1 5MHz channel + +![Heatmap for DFT-s-OFDM PI2BPSK at Fc=1612.5MHz. The plot shows power back-off values for a 5MHz channel with 15kHz subcarrier spacing. The x-axis is RBStart (0 to 25) and the y-axis is LCRB (0 to 25). The color scale ranges from 0 to 2.5. Most of the plot area is grey, with a few small colored blocks at low RBStart and LCRB values.](1a6a826cc13d4e964b7bda69508d78e6_img.jpg) + +Heatmap for DFT-s-OFDM PI2BPSK at Fc=1612.5MHz. The plot shows power back-off values for a 5MHz channel with 15kHz subcarrier spacing. The x-axis is RBStart (0 to 25) and the y-axis is LCRB (0 to 25). The color scale ranges from 0 to 2.5. Most of the plot area is grey, with a few small colored blocks at low RBStart and LCRB values. + +![Heatmap for DFT-s-OFDM QPSK at Fc=1612.5MHz. Similar to the first plot, but with more colored blocks scattered across the RBStart and LCRB grid. The color scale ranges from 0 to 3.](ef25c3cf1fdb334fc8679e85ab5265ca_img.jpg) + +Heatmap for DFT-s-OFDM QPSK at Fc=1612.5MHz. Similar to the first plot, but with more colored blocks scattered across the RBStart and LCRB grid. The color scale ranges from 0 to 3. + +![Heatmap for CP-OFDM QPSK at Fc=1612.5MHz. This plot shows a dense triangular pattern of colored blocks, starting from the top-left and descending towards the bottom-right. The color scale ranges from 0 to 6.](df7cb4ea9bd6c3f445f3e264773b125f_img.jpg) + +Heatmap for CP-OFDM QPSK at Fc=1612.5MHz. This plot shows a dense triangular pattern of colored blocks, starting from the top-left and descending towards the bottom-right. The color scale ranges from 0 to 6. + +Figure 6.2.1.2.2.3.1-1: Power back-off values for the 5MHz channel at Fc=1612.5MHz. + +![Heatmap for DFT-s-OFDM PI2BPSK at Fc=1613.9MHz. The plot shows power back-off values for a 5MHz channel. The color scale ranges from 0 to 1. Most of the plot area is grey, with a few small colored blocks at low RBStart and LCRB values.](dc0cec98faa3ead994c1b171cb56265d_img.jpg) + +Heatmap for DFT-s-OFDM PI2BPSK at Fc=1613.9MHz. The plot shows power back-off values for a 5MHz channel. The color scale ranges from 0 to 1. Most of the plot area is grey, with a few small colored blocks at low RBStart and LCRB values. + +![Heatmap for DFT-s-OFDM QPSK at Fc=1613.9MHz. Similar to the first plot, but with more colored blocks scattered across the RBStart and LCRB grid. The color scale ranges from 0 to 2.5.](ef177a7090c8da3fcd9beb78e78fd68f_img.jpg) + +Heatmap for DFT-s-OFDM QPSK at Fc=1613.9MHz. Similar to the first plot, but with more colored blocks scattered across the RBStart and LCRB grid. The color scale ranges from 0 to 2.5. + +![Heatmap for CP-OFDM QPSK at Fc=1613.9MHz. This plot shows a dense triangular pattern of colored blocks, similar to the one at 1612.5MHz. The color scale ranges from 0 to 4.](07b56a8a7752e22a6fc5e9a5d2de5caa_img.jpg) + +Heatmap for CP-OFDM QPSK at Fc=1613.9MHz. This plot shows a dense triangular pattern of colored blocks, similar to the one at 1612.5MHz. The color scale ranges from 0 to 4. + +Figure 6.2.1.2.2.1-2: Power back-off values for the 5MHz channel at Fc=1613.9MHz. + +![Heatmap for DFT-s-OFDM PI2BPSK at Fc=1615.5MHz. The plot shows power back-off values for a 5MHz channel. The color scale ranges from 0 to 0.5. Most of the plot area is grey, with a few small colored blocks at low RBStart and LCRB values.](ef075538e1af84d8c6631c84087faeab_img.jpg) + +Heatmap for DFT-s-OFDM PI2BPSK at Fc=1615.5MHz. The plot shows power back-off values for a 5MHz channel. The color scale ranges from 0 to 0.5. Most of the plot area is grey, with a few small colored blocks at low RBStart and LCRB values. + +![Heatmap for DFT-s-OFDM QPSK at Fc=1615.5MHz. Similar to the first plot, but with more colored blocks scattered across the RBStart and LCRB grid. The color scale ranges from 0 to 1.](b2e1c48ea85ca7aef5ab959221c8ff6b_img.jpg) + +Heatmap for DFT-s-OFDM QPSK at Fc=1615.5MHz. Similar to the first plot, but with more colored blocks scattered across the RBStart and LCRB grid. The color scale ranges from 0 to 1. + +![Heatmap for CP-OFDM QPSK at Fc=1615.5MHz. This plot shows a dense triangular pattern of colored blocks. The color scale ranges from 0 to 3.](6682c4376efdda007851175f3014eca3_img.jpg) + +Heatmap for CP-OFDM QPSK at Fc=1615.5MHz. This plot shows a dense triangular pattern of colored blocks. The color scale ranges from 0 to 3. + +Figure 6.2.1.2.2.3.1-3: Power back-off values for the 5MHz channel at Fc=1615.5MHz. + +![Heatmap for DFT-s-OFDM PI2BPSK at Fc=1620.5MHz. The plot shows power back-off values for a 5MHz channel. The color scale ranges from 0 to 0.5. Most of the plot area is grey, with a few small colored blocks at low RBStart and LCRB values.](bd998e32488e42e7ab0d3c170c1eff26_img.jpg) + +Heatmap for DFT-s-OFDM PI2BPSK at Fc=1620.5MHz. The plot shows power back-off values for a 5MHz channel. The color scale ranges from 0 to 0.5. Most of the plot area is grey, with a few small colored blocks at low RBStart and LCRB values. + +![Heatmap for DFT-s-OFDM QPSK at Fc=1620.5MHz. Similar to the first plot, but with more colored blocks scattered across the RBStart and LCRB grid. The color scale ranges from 0 to 1.](2208043dc0f4fadcc7e33697806083c3_img.jpg) + +Heatmap for DFT-s-OFDM QPSK at Fc=1620.5MHz. Similar to the first plot, but with more colored blocks scattered across the RBStart and LCRB grid. The color scale ranges from 0 to 1. + +![Heatmap for CP-OFDM QPSK at Fc=1620.5MHz. This plot shows a dense triangular pattern of colored blocks. The color scale ranges from 0 to 3.](3d827c43b44a567da971c01073295d3d_img.jpg) + +Heatmap for CP-OFDM QPSK at Fc=1620.5MHz. This plot shows a dense triangular pattern of colored blocks. The color scale ranges from 0 to 3. + +Figure 6.2.1.2.2.3.1-4: Power back-off values for the 5MHz channel at Fc=1620.5MHz. + +![Three heatmaps showing power back-off values for a 5MHz channel at Fc=1624MHz. The first heatmap is for 'Allocations not covered by regions other than MPR Outer' with a color scale from 0 to 0.5. The second is for 'DFT-s-OFDM QPSK fc=1624MHz BW=5MHz SCS=15kHz' with a color scale from 0 to 1. The third is for 'CP-OFDM QPSK fc=1624MHz BW=5MHz SCS=15kHz' with a color scale from 0 to 3. All plots have RBStart (0-25) on the x-axis and LCRB (0-25) on the y-axis.](1c427123350e0e73e2a109b79069314b_img.jpg) + +Three heatmaps showing power back-off values for a 5MHz channel at Fc=1624MHz. The first heatmap is for 'Allocations not covered by regions other than MPR Outer' with a color scale from 0 to 0.5. The second is for 'DFT-s-OFDM QPSK fc=1624MHz BW=5MHz SCS=15kHz' with a color scale from 0 to 1. The third is for 'CP-OFDM QPSK fc=1624MHz BW=5MHz SCS=15kHz' with a color scale from 0 to 3. All plots have RBStart (0-25) on the x-axis and LCRB (0-25) on the y-axis. + +Figure 6.2.1.2.2.3.1-5: Power back-off values for the 5MHz channel at Fc=1624MHz. + +###### 6.2.1.2.2.3.2 10MHz channel + +![Three heatmaps showing power back-off values for a 10MHz channel at Fc=1615MHz. The first heatmap is for 'DFT-s-OFDM PI2BPSK fc=1615MHz BW=10MHz SCS=15kHz' with a color scale from 0 to 6. The second is for 'DFT-s-OFDM QPSK fc=1615MHz BW=10MHz SCS=15kHz' with a color scale from 0 to 7.5. The third is for 'CP-OFDM QPSK fc=1615MHz BW=10MHz SCS=15kHz' with a color scale from 0 to 12.5. All plots have RBStart (0-50) on the x-axis and LCRB (0-50) on the y-axis.](3e0c2bf6c51c575d096c7fc95c1e8454_img.jpg) + +Three heatmaps showing power back-off values for a 10MHz channel at Fc=1615MHz. The first heatmap is for 'DFT-s-OFDM PI2BPSK fc=1615MHz BW=10MHz SCS=15kHz' with a color scale from 0 to 6. The second is for 'DFT-s-OFDM QPSK fc=1615MHz BW=10MHz SCS=15kHz' with a color scale from 0 to 7.5. The third is for 'CP-OFDM QPSK fc=1615MHz BW=10MHz SCS=15kHz' with a color scale from 0 to 12.5. All plots have RBStart (0-50) on the x-axis and LCRB (0-50) on the y-axis. + +Figure 6.2.1.2.2.3.2-1: Power back-off values for the 10MHz channel at Fc=1615MHz. + +![Three heatmaps showing power back-off values for a 10MHz channel at Fc=1620MHz. The first heatmap is for 'DFT-s-OFDM PI2BPSK fc=1620MHz BW=10MHz SCS=15kHz' with a color scale from 0 to 1.5. The second is for 'DFT-s-OFDM QPSK fc=1620MHz BW=10MHz SCS=15kHz' with a color scale from 0 to 2. The third is for 'CP-OFDM QPSK fc=1620MHz BW=10MHz SCS=15kHz' with a color scale from 0 to 4. All plots have RBStart (0-50) on the x-axis and LCRB (0-50) on the y-axis.](09ab686699bb9597b8025e78fb390069_img.jpg) + +Three heatmaps showing power back-off values for a 10MHz channel at Fc=1620MHz. The first heatmap is for 'DFT-s-OFDM PI2BPSK fc=1620MHz BW=10MHz SCS=15kHz' with a color scale from 0 to 1.5. The second is for 'DFT-s-OFDM QPSK fc=1620MHz BW=10MHz SCS=15kHz' with a color scale from 0 to 2. The third is for 'CP-OFDM QPSK fc=1620MHz BW=10MHz SCS=15kHz' with a color scale from 0 to 4. All plots have RBStart (0-50) on the x-axis and LCRB (0-50) on the y-axis. + +Figure 6.2.1.2.2.3.2-2: Power back-off values for the 10MHz channel at Fc=1620MHz. + +![Three heatmaps showing power back-off values for a 10MHz channel at Fc=1621.5MHz. The first heatmap is for 'DFT-s-OFDM PI2BPSK fc=1621.5MHz BW=10MHz SCS=15kHz' with a color scale from 0 to 1.5. The second is for 'DFT-s-OFDM QPSK fc=1621.5MHz BW=10MHz SCS=15kHz' with a color scale from 0 to 2. The third is for 'CP-OFDM QPSK fc=1621.5MHz BW=10MHz SCS=15kHz' with a color scale from 0 to 3. All plots have RBStart (0-50) on the x-axis and LCRB (0-50) on the y-axis.](4e7f11ebd82a34bb69e271477038b901_img.jpg) + +Three heatmaps showing power back-off values for a 10MHz channel at Fc=1621.5MHz. The first heatmap is for 'DFT-s-OFDM PI2BPSK fc=1621.5MHz BW=10MHz SCS=15kHz' with a color scale from 0 to 1.5. The second is for 'DFT-s-OFDM QPSK fc=1621.5MHz BW=10MHz SCS=15kHz' with a color scale from 0 to 2. The third is for 'CP-OFDM QPSK fc=1621.5MHz BW=10MHz SCS=15kHz' with a color scale from 0 to 3. All plots have RBStart (0-50) on the x-axis and LCRB (0-50) on the y-axis. + +Figure 6.2.1.2.2.3.2-3: Power back-off values for the 10MHz channel at Fc=1621.5MHz. + +###### 6.2.1.2.2.3.3 15MHz channel + +![Figure 6.2.1.2.2.3.3-1: Power back-off values for the 15MHz channel at Fc=1617.5MHz. The figure contains three heatmaps: DFT-s-OFDM PI2BPSK, DFT-s-OFDM QPSK, and CP-OFDM QPSK. Each plot shows LCRB (0 to 70) on the y-axis and RBStart (0 to 70) on the x-axis. The color scale represents power back-off values in dB, ranging from 0 to 8.5 for DFT-s-OFDM and 0 to 13.5 for CP-OFDM. The plots show that power back-off is generally higher for CP-OFDM and lower for DFT-s-OFDM, with values decreasing as RBStart increases.](f85bf99d372e735d228361bf4d3cf7e6_img.jpg) + +Figure 6.2.1.2.2.3.3-1: Power back-off values for the 15MHz channel at Fc=1617.5MHz. The figure contains three heatmaps: DFT-s-OFDM PI2BPSK, DFT-s-OFDM QPSK, and CP-OFDM QPSK. Each plot shows LCRB (0 to 70) on the y-axis and RBStart (0 to 70) on the x-axis. The color scale represents power back-off values in dB, ranging from 0 to 8.5 for DFT-s-OFDM and 0 to 13.5 for CP-OFDM. The plots show that power back-off is generally higher for CP-OFDM and lower for DFT-s-OFDM, with values decreasing as RBStart increases. + +Figure 6.2.1.2.2.3.3-1: Power back-off values for the 15MHz channel at Fc=1617.5MHz. + +![Figure 6.2.1.2.2.3.3-2: Power back-off values for the 15MHz channel at Fc=1619MHz. The figure contains three heatmaps: DFT-s-OFDM PI2BPSK, DFT-s-OFDM QPSK, and CP-OFDM QPSK. Each plot shows LCRB (0 to 70) on the y-axis and RBStart (0 to 70) on the x-axis. The color scale represents power back-off values in dB, ranging from 0 to 6 for DFT-s-OFDM and 0 to 11 for CP-OFDM. The plots show that power back-off is generally lower than at Fc=1617.5MHz, with values decreasing as RBStart increases.](ca80b99f7e1d6e6b854f22190f2e14d8_img.jpg) + +Figure 6.2.1.2.2.3.3-2: Power back-off values for the 15MHz channel at Fc=1619MHz. The figure contains three heatmaps: DFT-s-OFDM PI2BPSK, DFT-s-OFDM QPSK, and CP-OFDM QPSK. Each plot shows LCRB (0 to 70) on the y-axis and RBStart (0 to 70) on the x-axis. The color scale represents power back-off values in dB, ranging from 0 to 6 for DFT-s-OFDM and 0 to 11 for CP-OFDM. The plots show that power back-off is generally lower than at Fc=1617.5MHz, with values decreasing as RBStart increases. + +Figure 6.2.1.2.2.3.3-2: Power back-off values for the 15MHz channel at Fc=1619MHz. + +###### 6.2.1.2.2.4 Summary of the power back-off values + +Presented power back-off values can be summarised as follows: + +- NR channels placed at the leftmost edge of the band might need power back-off, exact value of which depends on the number of the scheduled RBs and their location. Results are the same for both FCC and ETSI requirements because the main limiting factor is the out-of-band emission requirements, which are the same for both regulatory domains. In other words, even though ETSI has additional in-band emission requirements for 1610-1618MHz, they do not impact results. 6.2.1.2.2.4-1 illustrates power spectrum of the fully allocated 5MHz channel right at the lower edge of the band showing that unless power back-off is applied out of band emission requirements will be violated. +- As somewhat anticipated, RBs scheduled at the centre of the NR channel do not require any power back-off; but RBs scheduled at the leftmost edge of the configured NR channel do require power back-off to meet out-of-band emission requirements. Similarly, power back-off is needed when all RBs are scheduled to mitigate emissions coming from the full-channel transmissions. +- In case of the 5MHz channel, once the channel is shifted farther from the left edge of the band where the GNSS services are, the required power back-off goes down a lot and is caused mostly by the in-band emission requirements. For instance, if the 5MHz NR channel is shifted by 1.4MHz from the lower edge, then small RB allocations will not require any power back-off at all. Some of the channel edge allocations might need power back-off, but it does not exceed baseline MPR. For both FCC and ETSI regulations the switching point is around the center frequency of 1615.7MHz, after which power back-off values remain limited to the basic MPR requirements for any configuration case. +- The 5MHz channel placed at the rightmost edge of the band may need some A-MPR for the RBs scheduled at the right edge of the channel under the ETSI regulations because the latter have out-of-band emission requirements for higher frequencies. 6.2.1.2.2.4-2 shows the power spectrum plot for the right-most channel, from which one can see that unless a UE applies power back-off the ETSI out-of-band emission requirements can be violated. Nevertheless, once the channel is shifted away from the upper edge by 1.6MHz, no A-MPR is + +needed at least for small allocations. And under the FCC regulations no A-MPR is needed even for the right-most channel because there are no out-of-band emission requirements for higher frequencies. + +- As for the 10 and 15MHz channels, even if we shift the channel to the right from the leftmost band edge, some configuration cases would still require A-MPR irrespective of whether it is ETSI or FCC requirements. As in cases for other channels at the band edge, A-MPR is needed mostly for the case when all RBs are scheduled. The only difference between FCC and ETSI power back-off values is that FCC will trigger lower A-MPR because there are no out-of-band emission requirements for upper frequencies and no in-band emission requirements. + +![Figure 6.2.1.2.2.4-1: Power spectrum plot for the CP-OFDM 5MHz fully allocated transmission (Fc=1612.5MHz).](723827e0738d2743c3b3423760a5c48e_img.jpg) + +This graph shows the power spectrum for a 5MHz CP-OFDM transmission at a center frequency of 1612.5MHz. The y-axis represents 'Power in dBm/MHz' from -50 to 10, and the x-axis represents 'Frequency (MHz)' from -30 to 30. A blue curve shows the power density, with a flat region between -5 MHz and 5 MHz. A red shaded area highlights the power back-off requirement around this flat region. A text annotation with an arrow pointing to the flat region states: 'For fully allocated channel the flat region creates power back-off need around this area'. A label 'MBW: 1MHz' is in the top right corner. + +Figure 6.2.1.2.2.4-1: Power spectrum plot for the CP-OFDM 5MHz fully allocated transmission (Fc=1612.5MHz). + +**Figure 6.2.1.2.2.4-1: Power spectrum plot for the CP-OFDM 5MHz fully allocated transmission (Fc=1612.5MHz).** + +![Figure 6.2.1.2.2.4-2: Power spectrum plot for the CP-OFDM 5MHz fully allocated transmission (Fc=1624MHz).](812b773680b611c18d49243e102b895a_img.jpg) + +This graph shows the power spectrum for a 5MHz CP-OFDM transmission at a center frequency of 1624MHz. The y-axis represents 'Power in dBm/MHz' from -60 to 10, and the x-axis represents 'Frequency (MHz)' from -30 to 30. A blue curve shows the power density, with a flat region between -5 MHz and 5 MHz. Red shaded areas highlight the power back-off requirements at the band edges and around the flat region. The power back-off is more pronounced at the lower band edge. + +Figure 6.2.1.2.2.4-2: Power spectrum plot for the CP-OFDM 5MHz fully allocated transmission (Fc=1624MHz). + +**Figure 6.2.1.2.2.4-2: Power spectrum plot for the CP-OFDM 5MHz fully allocated transmission (Fc=1624MHz).** + +If an operator decides to ensure lower power back-off, then one of the possible approaches is to rely upon 5MHz channels and to configure them with offsets from the lower/upper band edges. Then to avoid wasting 1.4/1.6MHz at the edges of the band it is possible to deploy other technologies, such as LTE CatM and NB-IOT. Figure 6.2.1.2.2.4-3 shows an exemplary allocation of channels, where an operator may consider one LTE CatM channel or seven NB-IOT channels at the lower edge of the band. For the upper edge, either eight NB-IOT channels can be configured, or one LTE CatM channel can be combined with one NB-IOT channel. + +![Figure 6.2.1.2.2.4-3: Exemplary allocations of channels at the edges of the band.](7ede87328f6b696dcffa65ebc4570cc8_img.jpg) + +This diagram illustrates channel allocations at the edges of a 16.5MHz band. The band is divided into two 5MHz NR channels with a gap in between. At the lower edge, a 1.4MHz block is allocated to LTE CatM and NB-IOT (7 x 200kHz). At the upper edge, a 1.6MHz block is allocated to LTE CatM and NB-IOT (8 x 200kHz). The diagram shows the relative positions of these allocations within the 16.5MHz band. + +Figure 6.2.1.2.2.4-3: Exemplary allocations of channels at the edges of the band. + +**Figure 6.2.1.2.2.4-3: Exemplary allocations of channels at the edges of the band.** + +##### 6.2.1.2.3 Additional maximum power reduction (company #2) + +This sub-clause contains additional simulations to evaluate the magnitude of A-MPR. The simulations assumptions are as presented below: + +- PA calibration point: ACLR of 30 dBc is met with DFT-s-OFDM waveform with StartRB = 0, $L\_CRB = 100$ +- IQ-image: -28 dBc +- LO-leakage: -28 dBc +- CIM3: -60 dBc +- Additional requirements: NR ACLR, SEM, Spurious emissions, EVM, Additional out of band bands emissions from ETSI EN 301 441 + +###### 6.2.1.2.3.1 5MHz channel + +![Figure 6.2.1.2.3.1-1: Power back-off values for the 5MHz channel at Fc=1612.5MHz. The figure contains three heatmaps for SCFDM BPSK, SCFDM QPSK, and CPOFDM QPSK. The x-axis is RBstart (0 to 25) and the y-axis is L_CRB (0 to 25). The color scale for SCFDM BPSK ranges from 0 to 2.5, for SCFDM QPSK from 0 to 4, and for CPOFDM QPSK from 0 to 5. CPOFDM QPSK shows a large area of high power back-off values, while SCFDM BPSK shows very low values.](5adf12d50dfea82178ca002a2c48641b_img.jpg) + +Figure 6.2.1.2.3.1-1: Power back-off values for the 5MHz channel at Fc=1612.5MHz. The figure contains three heatmaps for SCFDM BPSK, SCFDM QPSK, and CPOFDM QPSK. The x-axis is RBstart (0 to 25) and the y-axis is L\_CRB (0 to 25). The color scale for SCFDM BPSK ranges from 0 to 2.5, for SCFDM QPSK from 0 to 4, and for CPOFDM QPSK from 0 to 5. CPOFDM QPSK shows a large area of high power back-off values, while SCFDM BPSK shows very low values. + +Figure 6.2.1.2.3.1-1: Power back-off values for the 5MHz channel at Fc=1612.5MHz. + +![Figure 6.2.1.2.3.1-2: Power back-off values for the 5MHz channel at Fc=1615.5MHz. The figure contains three heatmaps for SCFDM BPSK, SCFDM QPSK, and CPOFDM QPSK. The x-axis is RBstart (0 to 25) and the y-axis is L_CRB (0 to 25). The color scale for SCFDM BPSK ranges from 0 to 0.06, for SCFDM QPSK from 0 to 1.5, and for CPOFDM QPSK from 0 to 2.5. CPOFDM QPSK shows high power back-off values, while SCFDM BPSK shows very low values.](fbfbbc91a80a21fc8d0ff7ba9e5865e3_img.jpg) + +Figure 6.2.1.2.3.1-2: Power back-off values for the 5MHz channel at Fc=1615.5MHz. The figure contains three heatmaps for SCFDM BPSK, SCFDM QPSK, and CPOFDM QPSK. The x-axis is RBstart (0 to 25) and the y-axis is L\_CRB (0 to 25). The color scale for SCFDM BPSK ranges from 0 to 0.06, for SCFDM QPSK from 0 to 1.5, and for CPOFDM QPSK from 0 to 2.5. CPOFDM QPSK shows high power back-off values, while SCFDM BPSK shows very low values. + +Figure 6.2.1.2.3.1-2: Power back-off values for the 5MHz channel at Fc=1615.5MHz. + +![Figure 6.2.1.2.3.1-3: Power back-off values for the 5MHz channel at Fc=1620.5MHz. The figure contains two heatmaps for SCFDM QPSK and CPOFDM QPSK. The x-axis is RBstart (0 to 25) and the y-axis is L_CRB (0 to 25). The color scale for SCFDM QPSK ranges from 0 to 0.8, and for CPOFDM QPSK from 0 to 2.5. CPOFDM QPSK shows high power back-off values, while SCFDM QPSK shows lower values.](17cd95aa220e50963bf6eb9818e33163_img.jpg) + +Figure 6.2.1.2.3.1-3: Power back-off values for the 5MHz channel at Fc=1620.5MHz. The figure contains two heatmaps for SCFDM QPSK and CPOFDM QPSK. The x-axis is RBstart (0 to 25) and the y-axis is L\_CRB (0 to 25). The color scale for SCFDM QPSK ranges from 0 to 0.8, and for CPOFDM QPSK from 0 to 2.5. CPOFDM QPSK shows high power back-off values, while SCFDM QPSK shows lower values. + +Figure 6.2.1.2.3.1-3: Power back-off values for the 5MHz channel at Fc=1620.5MHz. + +![Three heatmaps showing power back-off values for a 5MHz channel at Fc=1624MHz for SCFDMA BPSK, SCFDMA QPSK, and CPOFDM QPSK. The x-axis is RBstart (0-25) and the y-axis is L_CRB (0-25). The color scale for SCFDMA BPSK ranges from 0 to 0.6, for SCFDMA QPSK from 0 to 1, and for CPOFDM QPSK from 0 to 2.5.](a289b64f80c6df506c0c55d553fc4496_img.jpg) + +Three heatmaps showing power back-off values for a 5MHz channel at Fc=1624MHz for SCFDMA BPSK, SCFDMA QPSK, and CPOFDM QPSK. The x-axis is RBstart (0-25) and the y-axis is L\_CRB (0-25). The color scale for SCFDMA BPSK ranges from 0 to 0.6, for SCFDMA QPSK from 0 to 1, and for CPOFDM QPSK from 0 to 2.5. + +Figure 6.2.1.2.3.1-4: Power back-off values for the 5MHz channel at Fc=1624MHz. + +###### 6.2.1.2.3.2 10MHz channel + +![Three heatmaps showing power back-off values for a 10MHz channel at Fc=1615MHz for SCFDMA BPSK, SCFDMA QPSK, and CPOFDM QPSK. The x-axis is RBstart (0-50) and the y-axis is L_CRB (0-50). The color scale for SCFDMA BPSK ranges from 0 to 3.5, for SCFDMA QPSK from 0 to 5, and for CPOFDM QPSK from 0 to 7.](65a9654ccb3d0d452378b0f4c0c392f7_img.jpg) + +Three heatmaps showing power back-off values for a 10MHz channel at Fc=1615MHz for SCFDMA BPSK, SCFDMA QPSK, and CPOFDM QPSK. The x-axis is RBstart (0-50) and the y-axis is L\_CRB (0-50). The color scale for SCFDMA BPSK ranges from 0 to 3.5, for SCFDMA QPSK from 0 to 5, and for CPOFDM QPSK from 0 to 7. + +Figure 6.2.1.2.3.2-1: Power back-off values for the 5MHz channel at Fc=1615MHz. + +![Three heatmaps showing power back-off values for a 5MHz channel at Fc=1621.5MHz for SCFDMA BPSK, SCFDMA QPSK, and CPOFDM QPSK. The x-axis is RBstart (0-50) and the y-axis is L_CRB (0-50). The color scale for SCFDMA BPSK ranges from 0 to 2, for SCFDMA QPSK from 0 to 2.5, and for CPOFDM QPSK from 0 to 4.5.](ebb257e664fc85a1eb4d6534842794bb_img.jpg) + +Three heatmaps showing power back-off values for a 5MHz channel at Fc=1621.5MHz for SCFDMA BPSK, SCFDMA QPSK, and CPOFDM QPSK. The x-axis is RBstart (0-50) and the y-axis is L\_CRB (0-50). The color scale for SCFDMA BPSK ranges from 0 to 2, for SCFDMA QPSK from 0 to 2.5, and for CPOFDM QPSK from 0 to 4.5. + +Figure 6.2.1.2.3.2-2: Power back-off values for the 5MHz channel at Fc=1621.5MHz. + +###### 6.2.1.2.3.3 15MHz channel + +![Figure 6.2.1.2.3.3-1: Power back-off values for the 5MHz channel at Fc=1617.5MHz. The figure contains three heatmaps: SCFDMA BPSK, SCFDMA QPSK, and CPOFDM QPSK. Each plot shows Power back-off (PBO) in dB on the y-axis (0 to 80) against RBstart on the x-axis (0 to 80). The color scale indicates the PBO value, ranging from 0 (blue) to 6 (yellow) for BPSK, 0 to 5 for QPSK, and 0 to 7 for CPOFDM QPSK. The plots show that power back-off is generally higher for lower RBstart values and decreases as RBstart increases.](06ccd604e7eac77c7a5a323b6a913f15_img.jpg) + +Figure 6.2.1.2.3.3-1: Power back-off values for the 5MHz channel at Fc=1617.5MHz. The figure contains three heatmaps: SCFDMA BPSK, SCFDMA QPSK, and CPOFDM QPSK. Each plot shows Power back-off (PBO) in dB on the y-axis (0 to 80) against RBstart on the x-axis (0 to 80). The color scale indicates the PBO value, ranging from 0 (blue) to 6 (yellow) for BPSK, 0 to 5 for QPSK, and 0 to 7 for CPOFDM QPSK. The plots show that power back-off is generally higher for lower RBstart values and decreases as RBstart increases. + +Figure 6.2.1.2.3.3-1: Power back-off values for the 5MHz channel at Fc=1617.5MHz. + +![Figure 6.2.1.2.3.3-2: Power back-off values for the 5MHz channel at Fc=1619MHz. The figure contains three heatmaps: SCFDMA BPSK, SCFDMA QPSK, and CPOFDM QPSK. Each plot shows Power back-off (PBO) in dB on the y-axis (0 to 80) against RBstart on the x-axis (0 to 80). The color scale indicates the PBO value, ranging from 0 (blue) to 3.5 (yellow) for BPSK, 0 to 4.5 for QPSK, and 0 to 7 for CPOFDM QPSK. The plots show that power back-off is generally higher for lower RBstart values and decreases as RBstart increases.](a1a474be12b8992842992294b1d18592_img.jpg) + +Figure 6.2.1.2.3.3-2: Power back-off values for the 5MHz channel at Fc=1619MHz. The figure contains three heatmaps: SCFDMA BPSK, SCFDMA QPSK, and CPOFDM QPSK. Each plot shows Power back-off (PBO) in dB on the y-axis (0 to 80) against RBstart on the x-axis (0 to 80). The color scale indicates the PBO value, ranging from 0 (blue) to 3.5 (yellow) for BPSK, 0 to 4.5 for QPSK, and 0 to 7 for CPOFDM QPSK. The plots show that power back-off is generally higher for lower RBstart values and decreases as RBstart increases. + +Figure 6.2.1.2.3.3-2: Power back-off values for the 5MHz channel at Fc=1619MHz. + +##### 6.2.1.2.4 Additional maximum power reduction (company #3) + +This section presents results from the power back-off measurements taken for the left-most 5, 10 and 15MHz channels following the out-of-band emission requirements that are common for both the ETSI and FCC: + +- PC3 PA calibrated for 4dB post PA losses, 30dB ACLR at MPR1 for 20MHz DFT-s-OFDM QPSK +- Fully allocated waveform for QPSK DFT-s-OFDM and CP-OFDM +- Measurement every 0.5MHz in the slope and peak in 1MHz for the -40dBm/MHz floor. + +Measurements results are presented in Table 6.2.1.2.4-1 below, for which the following summary can be made: + +- For the 5MHz channel: + - Back-off is needed for emissions at 3.5MHz offset + - MPR is not sufficient for DFT-s-OFDM but is sufficient for CP-OFDM up to 4.5MHz offset + - Maximum back-off is needed to meet -40dBm/MHz floor at 5MHz offset at: + - 2.0dB for DFT-s-OFDM + - 5.5dB for CP-OFDM. +- For the 10MHz channel: + - Back-off is needed for emissions at 2.5MHz offset + - MPR is sufficient up to 3MHz offset for DFT-s-OFDM and CP-OFDM + - Maximum back-off is needed to meet -40dBm/MHz floor at 5MHz offset at: + +- 6.0dB for DFT-s-OFDM +- 8.3dB for CP-OFDM. +- For the 15MHz channel: + - Back-off is needed for emissions at 2.5MHz offset + - MPR is sufficient up to 3MHz offset for DFT-s-OFDM and CP-OFDM + - Maximum back-off is needed to meet -40dBm/MHz floor at 5MHz offset at: + - 5.2dB for DFT-s-OFDM + - 8.5dB for CP-OFDM. + +**Table 6.2.1.2.4-1: Back-off measurement results for frequencies with issues** + +| Freq. (MHz) | Mask (dBm/MHz) | CBW (MHz) | | | | | | back-off (dB) | | | | | | Margin at MPR | | | | | | +|-------------|----------------|-----------|-----|-----|-----|-----|-----|---------------|-----|-----|-----|-----|-----|---------------|--|--|--|--|--| +| | | 5 | | 10 | | 15 | | 5 | | 10 | | 15 | | | | | | | | +| | | DFT | CP | DFT | CP | DFT | CP | DFT | CP | DFT | CP | DFT | CP | | | | | | | +| 1607.5 | -10 | 0.0 | 0.0 | 0.0 | 1.1 | 0.0 | 0.8 | 7 | 9 | 6 | 8 | 8 | 9 | | | | | | | +| 1607 | -16 | 0.7 | 1.6 | 0.8 | 2.4 | 0.5 | 2.3 | 2 | 6 | 1 | 3 | 2 | 3 | | | | | | | +| 1606.5 | -22 | 1.1 | 1.9 | 2.2 | 3.8 | 1.8 | 3.8 | 0 | 4 | -5 | -3 | -3 | -2 | | | | | | | +| 1606 | -28 | 1.2 | 2.4 | 3.3 | 5.1 | 3.1 | 5.0 | 0 | 3 | -10 | -8 | -9 | -8 | | | | | | | +| 1605.5 | -34 | 0.8 | 2.8 | 4.6 | 6.4 | 4.2 | 6.4 | 1 | 1 | -15 | -13 | -15 | -13 | | | | | | | +| 1605 | -40 | 2.0 | 5.5 | 5.7 | 8.3 | 5.2 | 8.5 | -2 | -4 | -20 | -17 | -20 | -19 | | | | | | | +| 1604.9 | -40 | 2.0 | 5.3 | 6.0 | 8.2 | 5.2 | 8.4 | -7 | -10 | -20 | -18 | -20 | -19 | | | | | | | + +##### 6.2.1.2.5 Harmonised A-MPR values + +Tables 6.2.1.2.5-1 - 6.2.1.2.5-3 below present "harmonised" A-MPR values for 5, 10 and 15MHz channels at reference frequencies considered for the power back-off simulations and measurements. For the sake of simplicity only "full" RB allocation cases are used to compare results from different sources. + +**Table 6.2.1.2.5-1: Harmonised A-MPR values for the 5MHz channel.** + +| | 5MHz channel center frequency | | | | | | | | | | | | | | | | | | +|------------------------|-------------------------------|-----|-----|-----------|-----|----|-----------|-----|-----|-----------|-----|-----|-----------|-----|----|---------|-----|-----| +| | 1612.5MHz | | | 1613.9MHz | | | 1615.5MHz | | | 1620.5MHz | | | 1622.4MHz | | | 1624MHz | | | +| | CP | DFT | | CP | DFT | | CP | DFT | | CP | DFT | | CP | DFT | | CP | DFT | | +| | QP | QP | PI | QP | QP | PI | QP | QP | PI | QP | QP | PI | QP | QP | PI | QP | QP | PI | +| ETSI regulatory domain | | | | | | | | | | | | | | | | | | | +| #1 | 6 | 3.5 | 2.5 | 4 | 2.5 | 1 | 3 | 1 | 0.5 | 3 | 1 | 0.5 | 3 | 1 | 1 | 3 | 1.5 | 1.5 | +| #2 | 6 | 4 | 3 | - | - | - | 3 | 1.5 | 0.1 | 3 | 0.8 | - | - | - | - | 3 | 1.2 | 0.7 | +| #3 | 5.5 | 2 | | | | | | | | | | | | | | | | | +| => | 6 | 4 | 3 | 4 | 2.5 | 1 | | | | | | | 3 | 1 | 1 | 3 | 1.5 | 1.5 | +| FCC regulatory domain | | | | | | | | | | | | | | | | | | | +| #1 | 6 | 3.5 | 2.5 | 4 | 2.5 | 1 | 3 | 1 | 0.5 | 3 | 1 | 0.5 | | | | 3 | 1 | 0.5 | +| #3 | 5.5 | 2 | | | | | | | | | | | | | | | | | +| => | 6 | 4 | 3 | 4 | 2.5 | 1 | | | | | | | | | | 3 | 1 | 0.5 | + +Table 6.2.1.2.5-2: Harmonised A-MPR values for the 10MHz channel. + +| | 10MHz channel center frequency | | | | | | | | | +|-------------------------------|--------------------------------|------------|-----------|-----------------|------------|-----------|-----------------|------------|-----------| +| | 1615MHz | | | 1620MHz | | | 1621.5MHz | | | +| | CP-OFDM
QPSK | DFT-s-OFDM | | CP-OFDM
QPSK | DFT-s-OFDM | | CP-OFDM
QPSK | DFT-s-OFDM | | +| | | QPSK | PI/2 BPSK | | QPSK | PI/2 BPSK | | QPSK | PI/2 BPSK | +| ETSI regulatory domain | | | | | | | | | | +| #1 | 12.5 | 7 | 6 | 4 | 3 | 2 | 4 | 2.5 | 2 | +| #2 | 7.5 | 5 | 3.5 | | | | 4.5 | 2.5 | 2 | +| #3 | 7 | 5 | | | | | | | | +| => | 9 | 6 | 4 | 4.5 | 3 | 2 | 4.5 | 2.5 | 2 | +| FCC regulatory domain | | | | | | | | | | +| #1 | 12.5 | 7 | 6 | 4 | 2 | 1.5 | 3 | 2 | 1.5 | +| #3 | 7 | 5 | | | | | | | | +| => | 9 | 6 | 4 | 4 | 2 | 1.5 | 3 | 2 | 1.5 | + +Table 6.2.1.2.5-3: Harmonised A-MPR values for the 15MHz channel. + +| | 15MHz channel center frequency | | | | | | | +|-------------------------------|--------------------------------|------------|-----------|-----------------|------------|-----------|--| +| | 1617.5MHz | | | 1619MHz | | | | +| | CP-OFDM
QPSK | DTF-s-OFDM | | CP-OFDM
QPSK | DTF-s-OFDM | | | +| | | QPSK | PI/2 BPSK | | QPSK | PI/2 BPSK | | +| ETSI regulatory domain | | | | | | | | +| #1 | 13.5 | 11.5 | 11.5 | 11 | 9.5 | 7.5 | | +| #2 | 7.5 | 5 | 6.5 | 7 | 4.5 | 3.5 | | +| #3 | 8.5 | 5.5 | | | | | | +| => | 10 | 7 | 6.5 | 9 | 6 | 5.5 | | +| FCC regulatory domain | | | | | | | | +| #1 | 13.5 | 9.5 | 9 | 11 | 8.5 | 6 | | +| #3 | 8.5 | 5.5 | | | | | | +| => | 10 | 7 | 6.5 | 9 | 6 | 5.5 | | + +#### 6.2.1.3 Emission requirements and NS values + +There are three additional NS values defined for this band as summarised in Table 6.2.1.3-1 below: + +- NS\_03N is for the FCC regulatory domain. Since FCC does not introduce any special in-band emission requirements for sub-ranges, same requirements will be applicable for the whole range and for all the channel sizes. +- ETSI regulations have different in-band emission masks depending on the operating sub-range, so two NS flags are needed to differentiate between them. +- NS\_04N applicable range is limited to 1610-1618.25MHz according to the ETSI requirements. And since the total spectrum block size is 8.25MHz, it can accommodate only 5MHz standard NR channel, i.e. the applicable NR channel size is 5MHz. +- NS\_04N is for the ETSI range 1618.25-1626.5MHz, which can also accommodate only 5MHz standard NR channel. However, ETSI document also clarifies that the same in-band emission requirements will apply if the channel is partially configured in that range. It means that any 10 and 15MHz channel configured in 1610-1626.5MHz range will inevitably fall into the 1618.25-1626.5MHz range and thus they will follow NS\_04N requirements. + +Table 6.2.1.3-1: NTN L/S-band NS values + +| Regulatory domain | NS value | Applicable range (MHz) | Applicable channel (MHz) | +|-------------------|----------|------------------------|--------------------------| +| FCC | NS_03N | 1610-1626.5 | 5, 10, 15 | +| ETSI | NS_04N | 1610-1618.25 | 5 | +| | NS_05N | 1618.25-1626.5 | 5 | +| | | 1610-1626.5 | 10, 15 | + +Mapping between values of additionalSpectrumEmission and NS values is given in the Table 6.2.3.1-2 below. + +**Table 6.2.1.3-2: Mapping of network signalling label** + +| NR satellite band | Value of additionalSpectrumEmission | | | | | | | | +|-------------------|-------------------------------------|--------|--------|--------|---|---|---|---| +| | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | +| n254 | NS_01 | NS_03N | NS_04N | NS_05N | | | | | + +##### 6.2.1.3a NS values and associated A-MPR + +For the 5MHz channel, Figure 6.2.1.3a-1 below presents a graphical summary of the required power back-off values for different 5MHz channels: + +- The 5MHz channel right at the lower edge of the band requires power back-off even for small RB allocations irrespective of the fact whether it is FCC or ETSI regulations. If the channel is shifted by 1.4MHz, then at least small RB allocations will not require power back-off exceeding baseline MPR requirements. Shifting the 5MHz channel beyond the 1615.7MHz centre frequency results in no A-MPR at all. +- As for the upper edge of the band, the 5MHz channel under the FCC regulations will not require any additional A-MPR requirements even if it is right at the edge because there are no out-of-band emission requirements for the upper frequencies. However, with the ETSI regulations we will need to provide offset of 1.6MHz, upon which we will not be exceeding baseline MPR requirements. +- Because of the same regulations for the lower frequencies, A-MPR values can be the same for NS\_03N (FCC) and NS\_04N (ETSI lower range) at centre frequencies $1612.5 \leq f_c < 1615.7$ MHz. Furthermore, it is possible to split A-MPR values into two regions – $1612.5 \leq f_c < 1613.9$ MHz and $1613.9 \leq f_c < 1615.7$ MHz – whereupon the second region will not require A-MPR for small RB allocations. +- There is no need for A-MPR for NS\_03N (FCC) at centre frequencies above 1615.7MHz, but NS\_05N (ETSI upper range) requires A-MPR for center frequencies at $1622.4 < f_c \leq 1624$ MHz. + +![Figure 6.2.1.3a-1: Summary of required power back-off regions for the 5MHz channel for FCC (top) and ETSI (bottom) regulations. The figure consists of two horizontal timelines representing frequency ranges from 1610 MHz (F_lower) to 1626.5 MHz (F_upper). The top timeline for FCC regulations shows power back-off regions starting at F_lower and extending to the right. The bottom timeline for ETSI regulations shows power back-off regions starting at F_lower and extending to the right, with a different pattern for the upper edge of the band. Both timelines include markers for 1612.5 MHz, 1613.9 MHz, 1615.7 MHz, 1622.4 MHz, and 1624 MHz. Formulas for Fc are provided: F_lower + 5/2 <= Fc <= F_lower + 5/2 + 1.4 [MHz] and F_lower + 5/2 + 1.4 <= Fc <= F_lower + 5/2 + 3.2 [MHz] for the lower edge, and F_upper - 5/2 - 1.6 <= Fc <= F_upper - 5/2 [MHz] for the upper edge.](155bd5ec49c26532be9f04b06904002e_img.jpg) + +Figure 6.2.1.3a-1: Summary of required power back-off regions for the 5MHz channel for FCC (top) and ETSI (bottom) regulations. The figure consists of two horizontal timelines representing frequency ranges from 1610 MHz (F\_lower) to 1626.5 MHz (F\_upper). The top timeline for FCC regulations shows power back-off regions starting at F\_lower and extending to the right. The bottom timeline for ETSI regulations shows power back-off regions starting at F\_lower and extending to the right, with a different pattern for the upper edge of the band. Both timelines include markers for 1612.5 MHz, 1613.9 MHz, 1615.7 MHz, 1622.4 MHz, and 1624 MHz. Formulas for Fc are provided: F\_lower + 5/2 <= Fc <= F\_lower + 5/2 + 1.4 [MHz] and F\_lower + 5/2 + 1.4 <= Fc <= F\_lower + 5/2 + 3.2 [MHz] for the lower edge, and F\_upper - 5/2 - 1.6 <= Fc <= F\_upper - 5/2 [MHz] for the upper edge. + +**Figure 6.2.1.3a-1: Summary of required power back-off regions for the 5MHz channel for FCC (top) and ETSI (bottom) regulations.** + +For the 10MHz channel: + +- For the channel right at the lower edge of the band, A-MPR might be needed even for small RB allocations at the channel edges because of the strict out-of-band emission requirements. Shifting the channel farther away from the lower edge basically improves A-MPR with the switching point at the centre frequency of around 1620.1MHz (i.e. 1.4MHz offset from the upper edge), after which at least for the ETSI requirements emission requirements from the upper frequencies start influencing allocations at the channel's upper edge. Based on that A-MPR values can be considered the same for NS\_03N (FCC) and NS\_05N (ETSI) for the centre frequencies at $1615 \leq f_c < 1620.1\text{MHz}$ . +- For the channel right at the upper edge of the band, A-MPR is generally not needed for small allocations under the FCC regulations, which is reflected in the corresponding A-MPR for NS\_03 for the channel at 1621.5MHz. However, with NS\_05N (ETSI) A-MPR is still required because of the out-of-band emission requirements for upper frequencies. +- As can be seen from Figure 6.2.1.3a-2 below, the only major difference between the FCC and ETSI A-MPR regions is that the former can have optimised 10MHz channel placed right at the upper edge of the band. + +![Figure 6.2.1.3a-2: Summary of required power back-off regions for the 10MHz channel for FCC (top) and ETSI (bottom) regulations. The figure consists of two horizontal diagrams. The top diagram (FCC) shows a 16.5 MHz band from 1610 MHz (F_lower) to 1626.5 MHz (F_upper). A 10 MHz channel is shown with its occupied frequency range. The A-MPR region is defined by the formula: F_lower + 10/2 ≤ F_c < F_upper - 10/2 - 1.4 [MHz]. The ETSI diagram (bottom) shows the same band and channel, but the A-MPR region is defined by the formula: F_upper - 10/2 - 1.4 ≤ F_c ≤ F_upper - 10/2 [MHz].](484cfbdc05aee471306eeb11c0ee2543_img.jpg) + +The figure displays two frequency band diagrams for a 10 MHz channel within a 16.5 MHz total band. The band spans from $F\_lower = 1610\text{ MHz}$ to $F\_upper = 1626.5\text{ MHz}$ . Key frequency markers include 1615 MHz, 1620.1 MHz, and 1621.5 MHz. + +**Top Diagram (FCC Regulations):** The A-MPR region is indicated by a horizontal line above the channel's occupied frequency range. The formula for this region is $F\_lower + 10/2 \leq F_c < F\_upper - 10/2 - 1.4\text{ [MHz]}$ . This region starts at 1615 MHz and ends at 1620.1 MHz. + +**Bottom Diagram (ETSI Regulations):** The A-MPR region is indicated by a horizontal line above the channel's occupied frequency range. The formula for this region is $F\_upper - 10/2 - 1.4 \leq F_c \leq F\_upper - 10/2\text{ [MHz]}$ . This region starts at 1620.1 MHz and ends at 1621.5 MHz. + +Figure 6.2.1.3a-2: Summary of required power back-off regions for the 10MHz channel for FCC (top) and ETSI (bottom) regulations. The figure consists of two horizontal diagrams. The top diagram (FCC) shows a 16.5 MHz band from 1610 MHz (F\_lower) to 1626.5 MHz (F\_upper). A 10 MHz channel is shown with its occupied frequency range. The A-MPR region is defined by the formula: F\_lower + 10/2 ≤ F\_c < F\_upper - 10/2 - 1.4 [MHz]. The ETSI diagram (bottom) shows the same band and channel, but the A-MPR region is defined by the formula: F\_upper - 10/2 - 1.4 ≤ F\_c ≤ F\_upper - 10/2 [MHz]. + +**Figure 6.2.1.3a-2: Summary of required power back-off regions for the 10MHz channel for FCC (top) and ETSI (bottom) regulations.** + +For the 15MHz channel, more or less same A-MPR is needed for NS\_03N (FCC) and NS\_05N (ETSI) irrespective of the fact where exactly the channel is configured and whether it is under the FCC or ETSI regulations. + +![Five plots showing A-MPR regions for 5, 10, and 15 MHz channels. Each plot shows LCRB vs RBStart with regions A1 through A6. The 5 MHz plots show regions A1, A2, A3. The 10 MHz plots show regions A1, A2, A4, A5, A6. The 15 MHz plot shows regions A1, A2, A4, A5, A6.](1b1bb497e39fcc025a3fc8bd4fc78d9a_img.jpg) + +Five plots showing A-MPR regions for 5, 10, and 15 MHz channels. Each plot shows LCRB vs RBStart with regions A1 through A6. The 5 MHz plots show regions A1, A2, A3. The 10 MHz plots show regions A1, A2, A4, A5, A6. The 15 MHz plot shows regions A1, A2, A4, A5, A6. + +Figure 6.2.1.3a-3: A-MPR regions for NS\_03N (5, 10 and 15MHz channels). + +Table 6.2.1.3a-1: A-MPR values for NS\_03N (FCC) + +| Channel BW | Carrier Center Frequency | RB_start*12*SCS (MHz) | LCRB*12*SCS (MHz) | A-MPR | +|------------|--------------------------|-----------------------|-------------------|-------| +| 5MHz | 1612.5 <= fc < 1613.9 | <= 0.36 | <= 0.36 | A1 | +| | | | >= 2.88 | A2 | +| | 1613.9 <= fc < 1615.7 | | >= 3.24 | A3 | +| 10MHz | 1615 <= fc < 1620.1 | <= 1.8 | <= 5.04 | A4 | +| | | <= 1.8 | > 5.04 | A5 | +| | | > 7.2 | > 0 | A6 | +| | | > 1.8 | >= 2.88 | A2 | +| | 1620.1 <= fc < 1621.5 | | <= 6.48 | A6 | +| | | <= 0.36 | <= 0.36 | A1 | +| 15MHz | fc = 1621.5 | | >= 7.2 | A1 | +| | all | <= 3.6 | <= 5.04 | A4 | +| | | <= 3.6 | > 5.04 | A5 | +| | | > 10.44 | | A6 | +| | | > 3.6 | >= 4.32 | A2 | + +| | Modulation | A1 | A2 | A3 | A4 | A5 | A6 | +|------------|------------|-------|-------|-------|-------|--------|-------| +| DFT-s-OFDM | Pi/2 BPSK | [2.5] | [3.0] | [1.0] | [4.0] | [6.5] | [1.5] | +| | QPSK | [2.5] | [4.0] | [2.5] | [6.0] | [7.0] | [2.0] | +| | 16QAM | [2.5] | [4.0] | [2.5] | [6.0] | [7.0] | [2.0] | +| | 64QAM | | [4.0] | [2.5] | [6.0] | [7.0] | [2.0] | +| CP-OFDM | 256QAM | | | | | | | +| | QPSK | [3.5] | [6.0] | [4.0] | [8.0] | [10.0] | [4.0] | +| | 16QAM | [3.5] | [6.0] | [4.0] | [8.0] | [10.0] | [4.0] | +| | 64QAM | [3.5] | [6.0] | [4.0] | [8.0] | [10.0] | [4.0] | +| | 256QAM | | [6.0] | | [8.0] | [10.0] | | + +![Figure 6.2.1.3a-4: A-MPR regions for NS_04N (5MHz channels). The figure contains two plots. The left plot shows A-MPR regions A1 (blue), A2 (green), and A3 (yellow) for DFT-s-OFDM. The right plot shows A-MPR regions A1 (blue), A2 (green), and A3 (yellow) for CP-OFDM. Both plots have RBStart on the x-axis (0 to 20) and LCRB on the y-axis (0 to 25). The regions are defined by a series of steps that decrease as RBStart increases.](99938fa8d7d80af041634eba601e418b_img.jpg) + +Figure 6.2.1.3a-4: A-MPR regions for NS\_04N (5MHz channels). The figure contains two plots. The left plot shows A-MPR regions A1 (blue), A2 (green), and A3 (yellow) for DFT-s-OFDM. The right plot shows A-MPR regions A1 (blue), A2 (green), and A3 (yellow) for CP-OFDM. Both plots have RBStart on the x-axis (0 to 20) and LCRB on the y-axis (0 to 25). The regions are defined by a series of steps that decrease as RBStart increases. + +Figure 6.2.1.3a-4: A-MPR regions for NS\_04N (5MHz channels). + +Table 6.2.1.3a-2: A-MPR values for NS\_04N (ETSI lower sub-range) + +| Channel BW | Carrier Center Frequency | RB_start*12*SCS (MHz) | LCRB*12*SCS (MHz) | A-MPR | +|------------|--------------------------|-----------------------|-------------------|-------| +| 5MHz | 1612.5 <= fc < 1613.9 | <= 0.36 | <= 0.36 | A1 | +| | | | >= 2.88 | A2 | +| | 1613.9 <= fc < 1615.7 | | >= 3.24 | A3 | + +| | Modulation | A1 | A2 | A3 | +|------------|------------|-------|-------|-------| +| DFT-s-OFDM | Pi/2 BPSK | [2.5] | [3.0] | [1.0] | +| | QPSK | [2.5] | [4.0] | [2.5] | +| | 16QAM | [2.5] | [4.0] | [2.5] | +| | 64QAM | | [4.0] | [2.5] | +| CP-OFDM | 256QAM | | | | +| | QPSK | [3.5] | [6.0] | [4.0] | +| | 16QAM | [3.5] | [6.0] | [4.0] | +| | 64QAM | [3.5] | [6.0] | [4.0] | +| | 256QAM | | [6.0] | | + +![Three plots showing A-MPR regions for 5, 10, and 15 MHz channels. Each plot shows LCRB on the y-axis and RBStart on the x-axis, with regions A1, A2, A3, A4, A5, and A6 shaded in different colors (yellow, green, blue, orange).](4dfe30ac5a87d018364a0ac42ea533fe_img.jpg) + +The figure consists of three subplots, each titled 'MPR Regions', showing the A-MPR regions for different channel bandwidths (5 MHz, 10 MHz, and 15 MHz). The x-axis represents RBStart and the y-axis represents LCRB. The regions are defined by specific constraints on RBStart and LCRB, and are labeled A1 through A6. + +- 5 MHz Channel:** The plot shows regions A1 (yellow), A3 (orange), and A4 (green). The x-axis ranges from 0 to 20, and the y-axis ranges from 0 to 25. +- 10 MHz Channel:** The left plot shows regions A5 (green), A2 (yellow), A4 (green), and A6 (orange). The right plot shows regions A6 (green), A1 (blue), and A6 (yellow). The x-axis ranges from 0 to 50, and the y-axis ranges from 0 to 50. +- 15 MHz Channel:** The plot shows regions A5 (green), A2 (yellow), A4 (green), and A6 (orange). The x-axis ranges from 0 to 70, and the y-axis ranges from 0 to 70. + +Three plots showing A-MPR regions for 5, 10, and 15 MHz channels. Each plot shows LCRB on the y-axis and RBStart on the x-axis, with regions A1, A2, A3, A4, A5, and A6 shaded in different colors (yellow, green, blue, orange). + +Figure 6.2.1.3a-5: A-MPR regions for NS\_05N (5, 10 and 15MHz channels). + +Table 6.2.1.3a-3: A-MPR values for NS\_05N (ETSI upper sub-range) + +| Channel BW | Carrier Center Frequency | RB_start*12*SCS (MHz) | LCRB*12*SCS (MHz) | A-MPR | +|------------|--------------------------|-----------------------|-------------------|-------| +| 5MHz | 1622.4 < fc <= 1624 | <= 3.6 | > 0.36 | A3 | +| | | | >= 2.88 | A1 | +| 10MHz | 1615 <= fc < 1620.1 | <= 1.8 | <= 5.04 | A4 | +| | | <= 1.8 | > 5.04 | A5 | +| | | > 7.2 | > 0 | A6 | +| | | > 1.8 | >= 2.88 | A2 | +| | 1620.1 <= fc <= 1621.5 | | <= 7.2 | A6 | +| | | <= 0.36 | <= 0.36 | A1 | +| | | > 7.2 | > 0 | A6 | +| | | | | | +| 15MHz | all | <= 3.6 | <= 5.04 | A4 | +| | | <= 3.6 | > 5.04 | A5 | +| | | > 10.44 | | A6 | +| | | > 3.6 | >= 4.32 | A2 | + +| | Modulation | A1 | A2 | A3 | A4 | A5 | A6 | +|------------|------------|-------|-------|-------|-------|--------|-------| +| DFT-s-OFDM | Pi/2 BPSK | [1.5] | [5.0] | [1.5] | [6.5] | [6.5] | [2.0] | +| | QPSK | [1.5] | [5.0] | [1.5] | [6.5] | [7.0] | [2.5] | +| | 16QAM | [1.5] | [5.0] | [1.5] | [6.5] | [7.0] | [2.5] | +| | 64QAM | | [5.0] | | [6.5] | [7.0] | [2.5] | +| CP-OFDM | 256QAM | | | | | | | +| | QPSK | [3.0] | [6.5] | | [8.0] | [10.0] | [4.5] | +| | 16QAM | [3.0] | [6.5] | | [8.0] | [10.0] | [4.5] | +| | 64QAM | [3.0] | [6.5] | | [8.0] | [10.0] | [4.5] | +| | 256QAM | | [6.5] | | [8.0] | [10.0] | | + +#### 6.2.1.4 UE co-existence requirements + +Table 6.2.1.4-1: Requirements for spurious emissions for UE co-existence + +| NR NTN satellite Band | Spurious emission for UE co-existence | | | | | | | +|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---|----------------------|---------------------|-----------|------| +| | Protected band | Frequency range (MHz) | | | Maximum Level (dBm) | MBW (MHz) | NOTE | +| n254 | NR Band n1, n2, n3, n5, n7, n8, n12, n13, n14, n18, n20, n24, n25, n26, n28, n29, n30, n34, n38, n39, n40, n41, n48, n50, n51, n53, n54, n65, n66, n67, n70, n71, n74, n75, n76, n77, n78, n85, n90, n91, n92, n93, n94, n100, n101, n105, n255, n256 | F DL_low | - | F DL_high | -50 | 1 | | +| | E-UTRA Band 31, 54, 72, 73, 87, 88, 103 | F DL_low | - | F DL_high | -50 | 1 | | +| | NR Band n79, n104 | F DL_low | - | F DL_high | -50 | 1 | 2 | + +### 6.2.2 UE receiver characteristics + +#### 6.2.2.1 Reference sensitivity + +For band n254, band n53 REFSENS is re-used with additional 0.5dB insertion loss. The corresponding band n254 REFSENS values are presented in Table 6.2.2.1-1 below. + +Table 6.2.2.1-1: NTN L-/S-band two antenna port reference sensitivity QPSK PREFSENS + +| Operating Band | SCS kHz | Operating band / SCS / Channel bandwidth | | | | | | | | | | +|----------------|---------|------------------------------------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------| +| | | 5 MHz (dBm) | 10 MHz (dBm) | 15 MHz (dBm) | 20 MHz (dBm) | 25 MHz (dBm) | 30 MHz (dBm) | 35 MHz (dBm) | 40 MHz (dBm) | 45 MHz (dBm) | 50 MHz (dBm) | +| n254 | 15 | -99.5 | -96.3 | -94.5 | | | | | | | | +| | 30 | | -96.6 | -94.6 | | | | | | | | +| | 60 | | -97.0 | -94.9 | | | | | | | | + +#### 6.2.2.2 In-band blocking + +**Table 6.2.2.2-1: NTN L-/S-band in-band blocking** + +| Operating Band | Parameter | Unit | Case 1 | Case 2 | +|----------------|----------------------------------|------|----------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------| +| | $P_{\text{interferer}}$ | dBm | -56 | -44 | +| n254 | $F_{\text{interferer}}$ (offset) | MHz | $-BW_{\text{Channel}}/2 - F_{\text{Ioffset, case 1}}$
and
$BW_{\text{Channel}}/2 + F_{\text{Ioffset, case 1}}$ | $\leq -BW_{\text{Channel}}/2 - F_{\text{Ioffset, case 2}}$
and
$\geq BW_{\text{Channel}}/2 + F_{\text{Ioffset, case 2}}$ | +| | $F_{\text{interferer}}$ | MHz | NOTE 2 | $F_{\text{DL\_low}} - 15$
to
$F_{\text{DL\_high}} + 15$ | + +NOTE 1: The absolute value of the interferer offset $F_{\text{interferer}}$ (offset) shall be further adjusted to $(\lceil |F_{\text{interferer}}| / SCS \rceil + 0.5) SCS$ MHz with SCS the sub-carrier spacing of the wanted signal in MHz. The interferer is an NR signal with 15 kHz SCS. + +NOTE 2: For each carrier frequency, the requirement applies for two interferer carrier frequencies: a: $-BW_{\text{Channel}}/2 - F_{\text{Ioffset, case 1}}$ ; b: $BW_{\text{Channel}}/2 + F_{\text{Ioffset, case 1}}$ + +#### 6.2.2.3 Out-of-band blocking + +For band n254, same out-of-band blocking requirements as for the band n53 are re-used, whereupon Range 3 exception is adjusted accordingly accounting for the fact that band n254 upper bound is at 2500MHz. + +**Table 6.2.2.3-1: Out of-band blocking requirements.** + +| Operating Band | Parameter | Unit | Range 1 | Range 2 | Range 3 | +|----------------|------------------------------|------|-----------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------| +| | $P_{\text{interferer}}$ | dBm | -44 | -30 | -15 | +| n254 | $F_{\text{interferer}}$ (CW) | MHz | $-60 < f - F_{\text{DL\_low}} < -15$
or
$15 < f - F_{\text{DL\_high}} < 60$ | $-85 < f - F_{\text{DL\_low}} \leq -60$
or
$60 \leq f - F_{\text{DL\_high}} < 85$ | $1 \leq f \leq F_{\text{DL\_low}} - 85$
or
$F_{\text{DL\_high}} + 85 \leq f \leq 12750$ | + +NOTE: Band n254 power level of the interferer ( $P_{\text{interferer}}$ ) for Range 3 shall be modified to -20 dBm for $F_{\text{interferer}} > 2585$ MHz and $F_{\text{interferer}} < 2775$ MHz. + +### 6.2.3 UE RRM requirements + +There are no RRM specific requirements associated with this band. + +## 6.3 SAN requirements + +There are no SAN RF specific requirements associated with this band. + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|-------------|------------|----|-----|-----|---------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2023-05 | RAN4#107 | R4-2309600 | | | | TR skeleton | 0.0.0 | +| 2023-08 | RAN4#108 | R4-2314707 | | | | Implementation of TPs agreed at RAN4#107 meeting | 0.1.0 | +| 2023-10 | RAN4#108bis | | | | | Implementation of agreements made at RAN4#108 meeting | 0.2.0 | +| 2023-10 | RAN4#108bis | R4-2311218 | | | | TP containing power back-off values | 0.2.0 | +| 2023-10 | RAN4#108bis | R4-2315365 | | | | TP containing summary of the NS values | 0.2.1 | +| 2023-10 | RAN4#108bis | R4-2315369 | | | | TP containing summary of the RRM requirements | 0.2.1 | +| 2023-10 | RAN4#108bis | R4-2316134 | | | | TP containing further clarifications for the REFSENS values | 0.2.1 | +| 2023-11 | RAN4#109 | R4-2321805 | | | | TP with editorial corrections for terms, symbols and acronyms | 0.3.0 | +| 2023-11 | RAN4#109 | R4-2321806 | | | | TP with further clarifications for Rx and Tx requirements | 0.3.0 | +| 2023-11 | RAN4#109 | R4-2321807 | | | | TP with additional A-MPR simulations and measurements | 0.3.0 | +| 2023-11 | RAN4#109 | R4-2320649 | | | | TP with additional A-MPR simulations | 0.3.0 | +| 2023-11 | RAN4#109 | R4-2321808 | | | | TP with a summary of A-MPR values | 0.3.0 | +| 2023-12 | RAN#102 | RP-233309 | | | | TR for RAN plenary 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/38858/0d9149a10167a487a93c349f5d848b7d_img.jpg b/marked/Rel-18/38_series/38858/0d9149a10167a487a93c349f5d848b7d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..312a2b17f6dc04ef559bf9ecdfcd6aaa24f1ab9b --- /dev/null +++ b/marked/Rel-18/38_series/38858/0d9149a10167a487a93c349f5d848b7d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75b197e1e7df280fb65a8747df91dfb955641e079638619afc421f9057a049e1 +size 33056 diff --git a/marked/Rel-18/38_series/38858/1dad8c32864c128e058d2bb26f34c378_img.jpg b/marked/Rel-18/38_series/38858/1dad8c32864c128e058d2bb26f34c378_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b6bb2c247e0eae6c3c3480d90bf0c54e504a3d39 --- /dev/null +++ b/marked/Rel-18/38_series/38858/1dad8c32864c128e058d2bb26f34c378_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9bd7a1b5e80427d97970e1f237494cf9df2edc49b54b28680cee69e47ab5544b +size 109901 diff --git a/marked/Rel-18/38_series/38858/2785e0afc1cc382b8b668164369fb1d4_img.jpg b/marked/Rel-18/38_series/38858/2785e0afc1cc382b8b668164369fb1d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a130bee87a8f4bddc38348ffde35997dd4364d85 --- /dev/null +++ b/marked/Rel-18/38_series/38858/2785e0afc1cc382b8b668164369fb1d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e051f4d7cd9c8026c88ade6a90285577279db8ab50a3edb0b067033398e07db2 +size 20612 diff --git a/marked/Rel-18/38_series/38858/29aa6165ccf449dee0b4335676fa7b1a_img.jpg b/marked/Rel-18/38_series/38858/29aa6165ccf449dee0b4335676fa7b1a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..140cd2020aa230aa3d3e06ca4377520a67f3b09d --- /dev/null +++ b/marked/Rel-18/38_series/38858/29aa6165ccf449dee0b4335676fa7b1a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e347c80a8b141c2ad0ab7ef04195fb410000364ca62ecc20057f1e103e28a5d9 +size 42817 diff --git a/marked/Rel-18/38_series/38858/33d95af6c9ade7cf0415756cc5ea9803_img.jpg b/marked/Rel-18/38_series/38858/33d95af6c9ade7cf0415756cc5ea9803_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1d4587c8a8decb867f43038e483676b16adbb80 --- /dev/null +++ b/marked/Rel-18/38_series/38858/33d95af6c9ade7cf0415756cc5ea9803_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c7a8fe39348c281768033994ecddb05975b5bc54a87247b0b91c20c16dd0928 +size 23451 diff --git a/marked/Rel-18/38_series/38858/393809f56a51b00ce58ce3bc686803b9_img.jpg b/marked/Rel-18/38_series/38858/393809f56a51b00ce58ce3bc686803b9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1aaa8872bfc2c4357f0c674ca6de5e65d2d73616 --- /dev/null +++ b/marked/Rel-18/38_series/38858/393809f56a51b00ce58ce3bc686803b9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d47c286cfb5213db5997048c943e4d64a5414250185605f1dea6eadfa0eca347 +size 22134 diff --git a/marked/Rel-18/38_series/38858/3a6347f9ba293dba971fe22b739bdeef_img.jpg b/marked/Rel-18/38_series/38858/3a6347f9ba293dba971fe22b739bdeef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c374cc1e171c0a11fe61b26c3597d427d474688 --- /dev/null +++ b/marked/Rel-18/38_series/38858/3a6347f9ba293dba971fe22b739bdeef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a89bff3a9f81f2cc12f63adbff99e7b8da28bfbefe493029297478a1ecff3c1e +size 19325 diff --git a/marked/Rel-18/38_series/38858/45f6ef490318427c69f507d3fd26bcc5_img.jpg b/marked/Rel-18/38_series/38858/45f6ef490318427c69f507d3fd26bcc5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fbe63301fe2a0bf076dbcae4be4f069d2432533c --- /dev/null +++ b/marked/Rel-18/38_series/38858/45f6ef490318427c69f507d3fd26bcc5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2784c43ae7edcf68e8436670ffa5bb50d5ba23c3306e72a1651d37066adcd209 +size 65514 diff --git a/marked/Rel-18/38_series/38858/4b48a3fdfe130217b1ff29b9b0592a45_img.jpg b/marked/Rel-18/38_series/38858/4b48a3fdfe130217b1ff29b9b0592a45_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a1a4c7cf4cb0aad7dd8807a6550c3d738d2ab4a --- /dev/null +++ b/marked/Rel-18/38_series/38858/4b48a3fdfe130217b1ff29b9b0592a45_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c3e9126ab643db3935f507f8e26b56a98f543585ae35dd8aa179b88f41d49595 +size 40997 diff --git a/marked/Rel-18/38_series/38858/4c5a5c93221c0a5b9f6d1b0d4bdcfe81_img.jpg b/marked/Rel-18/38_series/38858/4c5a5c93221c0a5b9f6d1b0d4bdcfe81_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc91f7734eb1cdbc815afab8ef9682f915ffc199 --- /dev/null +++ b/marked/Rel-18/38_series/38858/4c5a5c93221c0a5b9f6d1b0d4bdcfe81_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7fcfa715c42c2762b8eb7a5e734718868b4c4a7ef5616bc0cad0fc910edb9658 +size 43084 diff --git a/marked/Rel-18/38_series/38858/4e953ed2839e2e77fd0c293cd76c3de9_img.jpg b/marked/Rel-18/38_series/38858/4e953ed2839e2e77fd0c293cd76c3de9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61c94656614c275f3920094bd689f7858678194e --- /dev/null +++ b/marked/Rel-18/38_series/38858/4e953ed2839e2e77fd0c293cd76c3de9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94425ef4f707c80d3b4f7a4d97af11cc89c25768bbb7c044fa198153b55460d1 +size 41323 diff --git a/marked/Rel-18/38_series/38858/4f6c3a94eee3c535b8899f9806014d44_img.jpg b/marked/Rel-18/38_series/38858/4f6c3a94eee3c535b8899f9806014d44_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aec2842067fc6c42a5f6fe23af77a204a850b44a --- /dev/null +++ b/marked/Rel-18/38_series/38858/4f6c3a94eee3c535b8899f9806014d44_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f03fe6835f2eb81d083f190642478c5c3bfce9cc9bdfdeb4d7f1df3f5c2df053 +size 51063 diff --git a/marked/Rel-18/38_series/38858/4faf621bddd7d6e9f24a27325de96015_img.jpg b/marked/Rel-18/38_series/38858/4faf621bddd7d6e9f24a27325de96015_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f6008835ccd228785e179ea98a9d8f76593bbc59 --- /dev/null +++ b/marked/Rel-18/38_series/38858/4faf621bddd7d6e9f24a27325de96015_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5c07edae61307605064cd2845643c880ccd3de52a9056551ba70a4a0c5a2d20 +size 36632 diff --git a/marked/Rel-18/38_series/38858/55649f88568b3835d933b30ca8e00279_img.jpg b/marked/Rel-18/38_series/38858/55649f88568b3835d933b30ca8e00279_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..521f23b5368959da620fa02afe43b1f92b0af114 --- /dev/null +++ b/marked/Rel-18/38_series/38858/55649f88568b3835d933b30ca8e00279_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d9986f9ef1c527aafc314e1110e009a41f8d75aa2285cafb0254083eeb9674c +size 25147 diff --git a/marked/Rel-18/38_series/38858/5b492020399ae8fbcc9714c8d83aebca_img.jpg b/marked/Rel-18/38_series/38858/5b492020399ae8fbcc9714c8d83aebca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0947bbc6e43bb949f104b9509cafa78d94e8746e --- /dev/null +++ b/marked/Rel-18/38_series/38858/5b492020399ae8fbcc9714c8d83aebca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d840858e1856de25765fb3fcf751033d11bbf661d83b7ef918b7bad413800578 +size 34230 diff --git a/marked/Rel-18/38_series/38858/5d88a496799eb6e06d3d697bf071b8f3_img.jpg b/marked/Rel-18/38_series/38858/5d88a496799eb6e06d3d697bf071b8f3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..841006ae47c14a30dde191e1078500de95d70bcf --- /dev/null +++ b/marked/Rel-18/38_series/38858/5d88a496799eb6e06d3d697bf071b8f3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1961e81fae43353a880db67770b66dcb8cac1a925d53b6c53957494eaba6f606 +size 59999 diff --git a/marked/Rel-18/38_series/38858/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38858/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1110e0a5f461e48122c9409d07fc58858cab393 --- /dev/null +++ b/marked/Rel-18/38_series/38858/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e176924c50027f7cc80a238c1350d1307c64e4251ab93fee8aa94f541714db11 +size 9562 diff --git a/marked/Rel-18/38_series/38858/6127ca80a1bc3d6a86b357a6ac43cb98_img.jpg b/marked/Rel-18/38_series/38858/6127ca80a1bc3d6a86b357a6ac43cb98_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df2e1aa3f38c318f5589a371a3050d780f79fc93 --- /dev/null +++ b/marked/Rel-18/38_series/38858/6127ca80a1bc3d6a86b357a6ac43cb98_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:41889fa2b685d907c2ffabdbf5f2f84993ed68e6dab21992003d29364a835fe7 +size 33043 diff --git a/marked/Rel-18/38_series/38858/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38858/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d3c4220d05a672c16ef4c54e62cbcec83aa6f083 --- /dev/null +++ b/marked/Rel-18/38_series/38858/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50e9fb41e1f987810714a1cea13bcc1e928aedbb94f9bb40e4ac2e8e9105c0c1 +size 5462 diff --git a/marked/Rel-18/38_series/38858/7adece84bcb18fcd9f28c138beb9d4d9_img.jpg b/marked/Rel-18/38_series/38858/7adece84bcb18fcd9f28c138beb9d4d9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15d5a9ef2aeb4356c2b1fc41dfca4f00fbbc628e --- /dev/null +++ b/marked/Rel-18/38_series/38858/7adece84bcb18fcd9f28c138beb9d4d9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0cb5763eccc491e79591aa4be8bfc347118abaddc920ee52688b250fe367020b +size 34175 diff --git a/marked/Rel-18/38_series/38858/870febccb98ab2774dee3ad16c85b0ac_img.jpg b/marked/Rel-18/38_series/38858/870febccb98ab2774dee3ad16c85b0ac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1881ae9d78b7fb7bbaf9c625ff0abc944a5e0507 --- /dev/null +++ b/marked/Rel-18/38_series/38858/870febccb98ab2774dee3ad16c85b0ac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d5363718c54c9ef77bc1f61492575644c1da181291a1fb70f2e64dc099ab3d75 +size 64816 diff --git a/marked/Rel-18/38_series/38858/94edd4dad9a6d1f95e2ab1822c06bf1a_img.jpg b/marked/Rel-18/38_series/38858/94edd4dad9a6d1f95e2ab1822c06bf1a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d291568f20a09a7efdcd9974e9e512106af88c9d --- /dev/null +++ b/marked/Rel-18/38_series/38858/94edd4dad9a6d1f95e2ab1822c06bf1a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:954f5ec6c04f4f71bd42bc04b6017fde41b38dfceb69d50c01a603c14841dd06 +size 141838 diff --git a/marked/Rel-18/38_series/38858/989009560da743352b1416921a20e624_img.jpg b/marked/Rel-18/38_series/38858/989009560da743352b1416921a20e624_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b26c06f596a5c8b6a1b8ab914d619b287f5a53a --- /dev/null +++ b/marked/Rel-18/38_series/38858/989009560da743352b1416921a20e624_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7058da46ee1458d715c764344b05c7d2bed1cfaa707353c197d6ab1ee7b620ca +size 75395 diff --git a/marked/Rel-18/38_series/38858/9c12d7993e786817c8c569e6f2d5a0a9_img.jpg b/marked/Rel-18/38_series/38858/9c12d7993e786817c8c569e6f2d5a0a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db00ac2018ba1dc742a5e16a97dfc266ded04f62 --- /dev/null +++ b/marked/Rel-18/38_series/38858/9c12d7993e786817c8c569e6f2d5a0a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8abdc98459e0c7d8fc7f57e142dc86d241df592322aae88305dfa7fb74bdc1e0 +size 76461 diff --git a/marked/Rel-18/38_series/38858/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-18/38_series/38858/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..332ab62ea6f77a83ac1fc74b27148c6b15089720 --- /dev/null +++ b/marked/Rel-18/38_series/38858/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:77152a20e263ee2baa82e74d589ed79a62e021681450742d80fcef5acc7e8b1d +size 13154 diff --git a/marked/Rel-18/38_series/38858/b06daabf0756b0c89478f311255358bc_img.jpg b/marked/Rel-18/38_series/38858/b06daabf0756b0c89478f311255358bc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ac1d4bcad6381c4561d0bf1d8a3092e68659ec4 --- /dev/null +++ b/marked/Rel-18/38_series/38858/b06daabf0756b0c89478f311255358bc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94da4bc833aa1dccfedbd322ff1a9a43f3231e325cae538df9854b484330cdc8 +size 19563 diff --git a/marked/Rel-18/38_series/38858/bdee2715697a4142d16a360549fa7c7f_img.jpg b/marked/Rel-18/38_series/38858/bdee2715697a4142d16a360549fa7c7f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2685e11727c3dbd7c458421a1b8903134d83aa9a --- /dev/null +++ b/marked/Rel-18/38_series/38858/bdee2715697a4142d16a360549fa7c7f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83d75a1769996038118953ca250616e7d9f8329fe09569103146c82ac2435944 +size 43187 diff --git a/marked/Rel-18/38_series/38858/bf4c705bba1ea48c6e9cace4844d01c4_img.jpg b/marked/Rel-18/38_series/38858/bf4c705bba1ea48c6e9cace4844d01c4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d7e0d4896ecbb488a03c32f759cc82f42e8e6e34 --- /dev/null +++ b/marked/Rel-18/38_series/38858/bf4c705bba1ea48c6e9cace4844d01c4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:356834d081af1766d67c9b1fe10f17c708c17737fdf6ddeb42c3f430a964d3c1 +size 71940 diff --git a/marked/Rel-18/38_series/38858/c327245fb6a613288de330f6f5afa783_img.jpg b/marked/Rel-18/38_series/38858/c327245fb6a613288de330f6f5afa783_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..996b1e6fcaf198cc4b673c20a0d08070beba24a7 --- /dev/null +++ b/marked/Rel-18/38_series/38858/c327245fb6a613288de330f6f5afa783_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5636d94d2f010d5f716c80e67f1ef681842cf9fb9660f6d139e1b53d7bc25af8 +size 66128 diff --git a/marked/Rel-18/38_series/38858/cb2548913628a6332ad07b161877fecf_img.jpg b/marked/Rel-18/38_series/38858/cb2548913628a6332ad07b161877fecf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3d5cc4cd3710e0d6b3e757274a0298de3df07d2b --- /dev/null +++ b/marked/Rel-18/38_series/38858/cb2548913628a6332ad07b161877fecf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f28bc268cf9ee83dd953b2476d283b4e12d1c2b5e6bd8031f61c3f06f4a074ac +size 75643 diff --git a/marked/Rel-18/38_series/38858/ce8b1b60587224b653aaef31adb64ac4_img.jpg b/marked/Rel-18/38_series/38858/ce8b1b60587224b653aaef31adb64ac4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df6b6d0d00f2a229c3bd0dcfeeb2ef6817eaa3a9 --- /dev/null +++ b/marked/Rel-18/38_series/38858/ce8b1b60587224b653aaef31adb64ac4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3a896e7205c5f1c0eaf1ccc47cd1091f621342e5749091ec55cc578288e58c3e +size 65025 diff --git a/marked/Rel-18/38_series/38858/cf8d9315f7f99ef87b4040c7312c5c6f_img.jpg b/marked/Rel-18/38_series/38858/cf8d9315f7f99ef87b4040c7312c5c6f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..750c7846ce44b2ea8b35deff168955ea804627ac --- /dev/null +++ b/marked/Rel-18/38_series/38858/cf8d9315f7f99ef87b4040c7312c5c6f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c009434c9652ef416d800a9c915b4edc2304711dc75516eb3d8ce36eadd33e7 +size 24543 diff --git a/marked/Rel-18/38_series/38858/e4c1d52d98aeae48bc84361381836c4c_img.jpg b/marked/Rel-18/38_series/38858/e4c1d52d98aeae48bc84361381836c4c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9465aa8575f90a58d53330e89e420e22422e9ad5 --- /dev/null +++ b/marked/Rel-18/38_series/38858/e4c1d52d98aeae48bc84361381836c4c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0006597cbcbb75cacd3e316d5edc99646abd62a4e0c409f8cec500e3650463cc +size 110409 diff --git a/marked/Rel-18/38_series/38858/e8f4bfb5095e82627472029c18c4effb_img.jpg b/marked/Rel-18/38_series/38858/e8f4bfb5095e82627472029c18c4effb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..14a31491b781b3223d530746d2ab483071debe2a --- /dev/null +++ b/marked/Rel-18/38_series/38858/e8f4bfb5095e82627472029c18c4effb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:46e7ab81e74d29266a467c01293af594822b6e33a24505d7c727362d6dac62bc +size 25391 diff --git a/marked/Rel-18/38_series/38858/efcb7264b716b845a750e9090562f601_img.jpg b/marked/Rel-18/38_series/38858/efcb7264b716b845a750e9090562f601_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..482a7f283350f22437e08bd1588b2c8874fcec31 --- /dev/null +++ b/marked/Rel-18/38_series/38858/efcb7264b716b845a750e9090562f601_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb67c7eddc0cd0dca2d83281fdcb31fb2574d37205c0ee9bad459ef2cd7bc0ed +size 62332 diff --git a/marked/Rel-18/38_series/38858/f296a66479e113c37204a53a2133c094_img.jpg b/marked/Rel-18/38_series/38858/f296a66479e113c37204a53a2133c094_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15cefc451bd16ad63c0874c2f2c73def3177ddb9 --- /dev/null +++ b/marked/Rel-18/38_series/38858/f296a66479e113c37204a53a2133c094_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d96a7b8161a5cd2c66317ca3eb35d7dcd6e10602fbbf77cce44bd81536b1651 +size 40130 diff --git a/marked/Rel-18/38_series/38858/f3a212725e08adb7b81020a6d010ee05_img.jpg b/marked/Rel-18/38_series/38858/f3a212725e08adb7b81020a6d010ee05_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..46ca8ce72e8be22e2f87fa8b237f14f6f52a9187 --- /dev/null +++ b/marked/Rel-18/38_series/38858/f3a212725e08adb7b81020a6d010ee05_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:21ead6efd7ffc392dee89e084ccfe1dea67fcbcd857b280d009da92bdd03931c +size 211650 diff --git a/marked/Rel-18/38_series/38858/f40b62ac3beebf7c156d65b3f9a7da86_img.jpg b/marked/Rel-18/38_series/38858/f40b62ac3beebf7c156d65b3f9a7da86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..237f65df71e9ce57633c739a6c7581e572567273 --- /dev/null +++ b/marked/Rel-18/38_series/38858/f40b62ac3beebf7c156d65b3f9a7da86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c6c9fe78902707ee47d04da3a43619af574db30c6b3d765d594767f6f76b28d7 +size 76157 diff --git a/marked/Rel-18/38_series/38858/f603c6acdc3f09cfd451a07b47c4730f_img.jpg b/marked/Rel-18/38_series/38858/f603c6acdc3f09cfd451a07b47c4730f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..31603fdcccca5fd33350b0a6c1517eb4854f59fb --- /dev/null +++ b/marked/Rel-18/38_series/38858/f603c6acdc3f09cfd451a07b47c4730f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c190e5a123e4f920b7809ae64f125a24e474d8b4ef98cfede4c8f9db8658dcda +size 123086 diff --git a/marked/Rel-18/38_series/38858/f79cb254efa2e37d7facb055cf90086e_img.jpg b/marked/Rel-18/38_series/38858/f79cb254efa2e37d7facb055cf90086e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22ba860ed1f02ed25fb0a0e15b9838440fbf581d --- /dev/null +++ b/marked/Rel-18/38_series/38858/f79cb254efa2e37d7facb055cf90086e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f77b74aefc2ffa9722f47c4f16a0abad42e2109839feff42f72ae4e2fc19a503 +size 10792 diff --git a/marked/Rel-18/38_series/38858/f9a7651f6e25578aded68c3bce114452_img.jpg b/marked/Rel-18/38_series/38858/f9a7651f6e25578aded68c3bce114452_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..48303f7fc51f6999ae21c1d20f73a45d6fcb162f --- /dev/null +++ b/marked/Rel-18/38_series/38858/f9a7651f6e25578aded68c3bce114452_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a66453788530d1f6f968dd27c1b09410bb230d2c1351e3e9abafa6615599272a +size 20165 diff --git a/marked/Rel-18/38_series/38858/raw.md b/marked/Rel-18/38_series/38858/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0781b67eb247b8febbd9746fb0e46079d9640bfb --- /dev/null +++ b/marked/Rel-18/38_series/38858/raw.md @@ -0,0 +1,8183 @@ + + +# 3GPP TR 38.858 V18.0.0 (2023-12) + +*Technical Report* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on Evolution of NR Duplex Operation (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller text to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the letters is a red signal wave icon, and below that, the text 'A GLOBAL INITIATIVE' in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## ***Copyright Notification*** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# --- Contents + +| | | +|-------------------------------------------------------------------------------------------------|-----| +| Foreword..... | 9 | +| 1 Scope..... | 11 | +| 2 References..... | 11 | +| 3 Definitions of terms, symbols and abbreviations..... | 14 | +| 3.1 Terms..... | 14 | +| 3.2 Symbols..... | 14 | +| 3.3 Abbreviations..... | 14 | +| 4 Introduction..... | 15 | +| 5 Objectives of study..... | 15 | +| 6 Subband non-overlapping full duplex (SBFD)..... | 16 | +| 6.1 General aspects of SBFD schemes..... | 16 | +| 6.1.1 SBFD Operations..... | 16 | +| 6.1.1.1 Semi-static configuration of SBFD subbands..... | 17 | +| 6.1.1.2 SBFD operation in symbols configured as DL in TDD-UL-DL-ConfigCommon ..... | 18 | +| 6.1.1.3 SBFD operation in symbols configured as flexible in TDD-UL-DL-ConfigCommon ..... | 18 | +| 6.1.2 Impact and potential enhancements for transmissions and receptions..... | 19 | +| 6.2 Inter-UE CLI handling schemes specific for SBFD..... | 23 | +| 7 Performance evaluation and its feasibility for SBFD..... | 24 | +| 7.1 Deployment scenarios..... | 24 | +| 7.2 Evaluation methodologies..... | 25 | +| 7.2.1 System level simulation..... | 25 | +| 7.2.2 Link level evaluation..... | 26 | +| 7.3 Performance evaluation results for semi-static SBFD..... | 29 | +| 7.3.1 System level simulation results..... | 29 | +| 7.3.1.1 SBFD Deployment Case 1 (FR1)..... | 29 | +| 7.3.1.1.1 Indoor office (FR1)..... | 29 | +| 7.3.1.1.2 Urban Macro (FR1)..... | 35 | +| 7.3.1.1.3 Dense Urban Macro layer (FR1)..... | 50 | +| 7.3.1.1.4 Dense Urban with 2-layer (FR1)..... | 59 | +| 7.3.1.2 SBFD Deployment Case 1 (FR2-1)..... | 60 | +| 7.3.1.2.1 Indoor office (FR2-1)..... | 60 | +| 7.3.1.2.2 Dense Urban Macro layer (FR2-1)..... | 65 | +| 7.3.1.3 SBFD Deployment Case 3-2 (FR1)..... | 77 | +| 7.3.1.3.1 2-layer Scenario B (FR1)..... | 77 | +| 7.3.1.4 SBFD Deployment Case 4 (FR1)..... | 81 | +| 7.3.1.4.1 Urban Macro (0% grid shift)..... | 81 | +| 7.3.1.4.2 Urban Macro (100% grid shift)..... | 93 | +| 7.3.2 Link level evaluation results..... | 105 | +| 7.3.2.1 FR1..... | 105 | +| 7.3.2.1.1 Scheme-1 (PUSCH repetition type A without joint channel estimation)..... | 105 | +| 7.3.2.1.2 Scheme-2 (SBFD with TBoMS PUSCH without joint channel estimation)..... | 106 | +| 7.3.2.1.3 Scheme-3 (PUSCH repetition type A with joint channel estimation)..... | 107 | +| 7.3.2.1.4 Scheme-4 (SBFD with TBoMS PUSCH with joint channel estimation)..... | 107 | +| 7.3.2.2 FR2-1..... | 108 | +| 7.3.2.2.1 Scheme-1 (PUSCH repetition type A without joint channel estimation)..... | 108 | +| 7.3.2.2.2 Scheme-2 (SBFD with TBoMS PUSCH without joint channel estimation)..... | 108 | +| 7.3.2.2.3 Scheme-3 (PUSCH repetition type A with joint channel estimation)..... | 108 | +| 7.3.2.2.4 Scheme-4 (SBFD with TBoMS PUSCH with joint channel estimation)..... | 109 | +| 7.4 Performance evaluation results of schemes for SBFD..... | 109 | +| 7.4.1 Dynamic SBFD..... | 109 | +| 7.4.1.1 Indoor office (FR1)..... | 110 | +| 7.4.1.1.1 Dynamic SBFD vs. dynamic TDD..... | 110 | +| 7.4.1.1.2 Dynamic SBFD vs. semi-static SBFD..... | 113 | +| 7.4.1.2 Urban Macro (FR1)..... | 116 | + +| | | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 7.4.1.2.1 | Dynamic SBFD vs. dynamic TDD..... | 116 | +| 7.4.1.2.2 | Dynamic SBFD vs. semi-static SBFD..... | 119 | +| 7.4.2 | Inter-gNB CLI handling schemes..... | 122 | +| 7.4.2.1 | Inter-gNB CLI handling scheme 1: Spatial Domain Coordination Scheme for gNB Tx-Beam Nulling..... | 122 | +| 7.4.2.1.1 | Reference scheme for performance comparison..... | 122 | +| 7.4.2.1.2 | Proposed scheme..... | 122 | +| 7.4.2.1.3 | Performance evaluation or analysis..... | 122 | +| 7.4.2.1.4 | Specification impact of the proposed scheme..... | 124 | +| 7.4.2.2 | Inter-gNB CLI handling scheme 2: UL Resource Muting-based scheme for measuring the gNB-to-gNB CLI interference covariance matrix..... | 124 | +| 7.4.2.2.1 | Reference scheme for performance comparison..... | 124 | +| 7.4.2.2.2 | Proposed scheme..... | 125 | +| 7.4.2.2.3 | Performance evaluation or analysis..... | 125 | +| 7.4.2.2.4 | Specification impact of the proposed scheme..... | 127 | +| 7.4.3 | Inter-UE CLI handling schemes..... | 127 | +| 7.4.3.1 | Inter-UE CLI handling scheme 1: Coordinated scheduling..... | 127 | +| 7.4.3.1.1 | Reference scheme for performance comparison..... | 127 | +| 7.4.3.1.2 | Proposed scheme..... | 128 | +| 7.4.3.1.3 | Performance evaluation or analysis..... | 128 | +| 7.4.3.1.4 | Specification impact of the proposed scheme..... | 130 | +| 7.4.4 | Inter-gNB and Inter-UE CLI handling schemes..... | 131 | +| 7.4.4.1 | Inter-gNB and Inter-UE CLI handling scheme 1: Spatial Domain Coordination Scheme for gNB Tx-Beam Nulling and UL Resource Muting-based scheme for measuring the gNB-to-gNB CLI interference covariance matrix..... | 131 | +| 7.4.4.1.1 | Reference scheme for performance comparison..... | 131 | +| 7.4.4.1.2 | Proposed scheme..... | 131 | +| 7.4.4.1.3 | Performance evaluation or analysis..... | 131 | +| 7.4.4.1.4 | Specification impact of the proposed scheme..... | 132 | +| 8 | Potential enhancements and analysis for dynamic/flexible TDD..... | 132 | +| 8.1 | Deployment scenarios..... | 132 | +| 8.2 | Evaluation methodologies..... | 133 | +| 8.2.1 | System level simulation..... | 133 | +| 8.3 | Inter-gNB CLI handling schemes..... | 134 | +| 8.3.1 | gNB-to-gNB co-channel CLI measurement and/or channel measurement..... | 134 | +| 8.3.1.1 | Description..... | 134 | +| 8.3.1.2 | Performance evaluation or analysis..... | 135 | +| 8.3.1.3 | Specification impact..... | 136 | +| 8.3.1A | Inter-gNB CLI scheme 1A: UL Resource Muting-based scheme for measuring the gNB-to-gNB CLI interference covariance matrix..... | 136 | +| 8.3.1A.1 | Reference scheme for performance comparison..... | 136 | +| 8.3.1A.2 | Proposed Scheme..... | 136 | +| 8.3.1A.3 | Performance evaluation or analysis..... | 137 | +| 8.3.1A.4 | Specification impact of the proposed scheme..... | 141 | +| 8.3.2 | Coordinated scheduling for time/frequency resources between gNBs..... | 141 | +| 8.3.2.1 | Description..... | 141 | +| 8.3.2.2 | Performance evaluation or analysis..... | 141 | +| 8.3.2.3 | Specification impact..... | 141 | +| 8.3.2A | Inter-gNB CLI scheme 2A: Time domain scheme using UL slot(s) aligned between gNBs..... | 141 | +| 8.3.2A.1 | Reference scheme for performance comparison..... | 141 | +| 8.3.2A.2 | Proposed scheme..... | 142 | +| 8.3.2A.3 | Performance evaluation or analysis..... | 142 | +| 8.3.2A.4 | Specification impact of the proposed scheme..... | 143 | +| 8.3.2B | Inter-gNB CLI scheme 2B: Frequency domain coordination scheme..... | 143 | +| 8.3.2B.1 | Reference scheme for performance comparison..... | 143 | +| 8.3.2B.2 | Proposed scheme..... | 143 | +| 8.3.2B.3 | Performance evaluation or analysis..... | 144 | +| 8.3.2B.4 | Specification impact of the proposed scheme..... | 145 | +| 8.3.3 | Spatial domain coordination method..... | 145 | +| 8.3.3.1 | Description..... | 145 | +| 8.3.3.2 | Performance evaluation or analysis..... | 146 | + +| | | | +|-----------|---------------------------------------------------------------------------------------------|-----| +| 8.3.3.3 | Specification impact..... | 146 | +| 8.3.3A | Inter-gNB CLI scheme 3A: Spatial domain coordination scheme for gNB Tx-Beam nulling..... | 146 | +| 8.3.3A.1 | Reference scheme for performance comparison..... | 146 | +| 8.3.3A.2 | Proposed Scheme..... | 147 | +| 8.3.3A.3 | Performance evaluation or analysis..... | 147 | +| 8.3.3A.4 | Specification impact of the proposed scheme..... | 148 | +| 8.3.4 | UE and gNB transmission and reception timing..... | 148 | +| 8.3.4.1 | Description..... | 148 | +| 8.3.5 | Power control based solution..... | 148 | +| 8.3.5.1 | Description..... | 148 | +| 8.3.5.2 | Performance evaluation or analysis..... | 149 | +| 8.3.5.3 | Specification impact..... | 149 | +| 8.3.5A | Inter-gNB CLI scheme 5A: Power control scheme based on gNB Tx power adjustment..... | 149 | +| 8.3.5A.1 | Reference scheme for performance comparison..... | 149 | +| 8.3.5A.2 | Proposed scheme..... | 149 | +| 8.3.5A.3 | Performance evaluation or analysis..... | 149 | +| 8.3.5A.4 | Specification impact of the proposed scheme..... | 152 | +| 8.3.5B | Inter-gNB CLI scheme 5B: Power control scheme based on UE Tx power adjustment..... | 152 | +| 8.3.5B.1 | Reference scheme for performance comparison..... | 152 | +| 8.3.5B.2 | Proposed Scheme..... | 153 | +| 8.3.5B.3 | Performance evaluation or analysis..... | 153 | +| 8.3.5B.4 | Specification impact of the proposed scheme..... | 156 | +| 8.4 | Inter-UE CLI handling schemes..... | 156 | +| 8.4.1 | UE-to-UE co-channel CLI measurement and reporting..... | 156 | +| 8.4.1.1 | Description..... | 156 | +| 8.4.1.2 | Performance evaluation or analysis..... | 157 | +| 8.4.1.3 | Specification impact..... | 157 | +| 8.4.2 | Coordinated scheduling for time/frequency resources between gNBs..... | 157 | +| 8.4.2.1 | Description..... | 157 | +| 8.4.2.2 | Performance evaluation or analysis..... | 158 | +| 8.4.2.3 | Specification impact..... | 158 | +| 8.4.3 | Spatial domain coordination method..... | 158 | +| 8.4.3.1 | Description..... | 158 | +| 8.4.3.2 | Performance evaluation or analysis..... | 158 | +| 8.4.4 | UE and gNB transmission and reception timing..... | 158 | +| 8.4.4.1 | Description..... | 158 | +| 8.4.5 | Power control based solution..... | 158 | +| 8.4.5.1 | Description..... | 158 | +| 8.4.5.2 | Performance evaluation or analysis..... | 158 | +| 8.4.5.3 | Specification impact..... | 158 | +| 9 | Implementation feasibility of SBFD..... | 159 | +| 9.1 | Background for analysis..... | 159 | +| 9.2.1 | Self-interference analysis..... | 162 | +| 9.2.1.1 | Summary table for self-interference analysis..... | 162 | +| 9.2.1.2 | Feasibility study on self-interference..... | 167 | +| 9.2.1.2.1 | Samsung..... | 167 | +| 9.2.1.2.2 | Ericsson..... | 173 | +| 9.2.1.2.3 | Huawei..... | 176 | +| 9.2.1.2.4 | Qualcomm..... | 177 | +| 9.2.1.2.5 | CATT..... | 180 | +| 9.2.1.2.6 | Nokia..... | 181 | +| 9.2.1.3 | Conclusion..... | 184 | +| 9.2.2 | Co-channel inter-sub-band co-site inter-sector interference analysis..... | 184 | +| 9.2.2.1 | Summary table for co-channel inter-sub-band co-site inter-sector interference analysis..... | 184 | +| 9.2.2.2 | Feasibility study on co-channel inter-sub-band co-site inter-sector interference..... | 189 | +| 9.2.2.2.1 | Samsung..... | 189 | +| 9.2.2.2.2 | Ericsson..... | 190 | +| 9.2.2.2.3 | Huawei..... | 193 | +| 9.2.2.2.4 | Nokia..... | 194 | +| 9.2.2.3 | Conclusion..... | 194 | +| 9.2.3 | Co-channel inter-sub-band inter-site interference analysis..... | 195 | + +| | | | +|-----------|-----------------------------------------------------------------------------------------------|-----| +| 9.2.4 | Summary..... | 195 | +| 9.3 | Feasibility of FR1 medium range BS aspects..... | 195 | +| 9.3.1 | Self-interference analysis..... | 195 | +| 9.3.1.1 | Summary table for self-interference analysis..... | 195 | +| 9.3.1.2 | Feasibility study on self-interference..... | 199 | +| 9.3.1.2.1 | Nokia..... | 199 | +| 9.3.1.2.2 | Ericsson..... | 199 | +| 9.3.1.2.3 | ZTE..... | 200 | +| 9.3.1.2.4 | Samsung..... | 200 | +| 9.3.1.2.5 | Huawei..... | 200 | +| 9.3.1.3 | Conclusion..... | 200 | +| 9.3.2 | Co-channel inter-sub-band co-site inter-sector interference analysis..... | 201 | +| 9.3.2.1 | Summary table for co-channel inter-subband co-site inter-sector interference analysis..... | 201 | +| 9.3.2.2 | Feasibility study on co-channel inter-subband co-site inter-sector interference analysis..... | 203 | +| 9.3.2.2.1 | Nokia..... | 203 | +| 9.3.2.2.2 | Ericsson..... | 203 | +| 9.3.2.2.3 | Samsung..... | 204 | +| 9.3.2.3 | Conclusion..... | 204 | +| 9.3.3 | Co-channel inter-sub-band inter-site interference analysis..... | 204 | +| 9.3.4 | Summary..... | 204 | +| 9.4 | Feasibility of FR1 local area BS aspects..... | 205 | +| 9.4.1 | Self-interference analysis..... | 205 | +| 9.4.1.1 | Summary table for self-interference analysis..... | 205 | +| 9.4.1.2 | Feasibility study on self-interference..... | 209 | +| 9.4.1.2.1 | Ericsson..... | 209 | +| 9.4.1.2.2 | CATT..... | 209 | +| 9.4.1.2.3 | Nokia..... | 210 | +| 9.4.1.2.4 | ZTE..... | 210 | +| 9.4.1.2.5 | Huawei..... | 210 | +| 9.4.1.3 | Conclusion..... | 210 | +| 9.4.2 | Co-channel inter-sub-band inter-site interference analysis..... | 210 | +| 9.4.3 | Summary..... | 210 | +| 9.5 | Feasibility of FR2-1 BS aspects..... | 211 | +| 9.5.1 | Self-interference analysis..... | 211 | +| 9.5.1.1 | Summary table for self-interference analysis..... | 211 | +| 9.5.1.2 | Feasibility study on self-interference..... | 213 | +| 9.5.1.2.1 | Samsung..... | 213 | +| 9.5.1.2.2 | Huawei..... | 215 | +| 9.5.1.2.3 | Qualcomm..... | 215 | +| 9.5.1.2.4 | Ericsson..... | 217 | +| 9.5.1.2.5 | Nokia..... | 218 | +| 9.5.1.3 | Conclusion..... | 219 | +| 9.5.2 | Co-channel inter-sub-band co-site inter-sector interference analysis..... | 219 | +| 9.5.2.1 | Summary table for co-channel inter-sub-band co-site inter-sector interference analysis..... | 219 | +| 9.5.2.2 | Feasibility study on co-channel inter-sub-band co-site inter-sector interference..... | 221 | +| 9.5.2.2.1 | Samsung..... | 221 | +| 9.5.2.2.2 | Huawei..... | 221 | +| 9.5.2.2.3 | Ericsson..... | 221 | +| 9.5.2.3 | Conclusion..... | 223 | +| 9.5.3 | Co-channel inter-sub-band inter-site interference analysis..... | 223 | +| 9.5.4 | Summary..... | 223 | +| 9.6 | FR1 Feasibility of UE aspects..... | 223 | +| 9.6.1 | Interference analysis..... | 223 | +| 9.6.1.1 | General..... | 223 | +| 9.6.1.2 | UE-UE co-channel inter-subband CLI modeling..... | 224 | +| 9.6.1.2.1 | Overview and analysis framework..... | 224 | +| 9.6.1.2.2 | UE co-channel Tx model..... | 224 | +| 9.6.1.2.3 | UE co-channel Rx model..... | 225 | +| 9.6.1.3 | UE-UE adjacent channel CLI modelling..... | 226 | +| 9.6.1.3.1 | Overview..... | 226 | +| 9.6.1.3.2 | UE adjacent channel Tx model..... | 226 | + +| | | | +|-----------|----------------------------------------------------------------------------------------|-----| +| 9.6.1.3.3 | UE adjacent channel Rx model..... | 226 | +| 9.6.2 | Summary..... | 227 | +| 9.7 | FR2-1 Feasibility of UE aspects..... | 227 | +| 9.7.1 | Interference analysis..... | 227 | +| 9.7.1.1 | UE-UE co-channel inter-subband CLI modeling..... | 227 | +| 9.7.1.1.1 | Receiver aspects..... | 227 | +| 9.7.1.1.2 | Transmitter aspects..... | 228 | +| 9.7.1.2 | UE-UE adjacent channel CLI modeling..... | 228 | +| 9.7.1.2.1 | Receiver aspects..... | 228 | +| 9.7.1.2.2 | Transmitter aspects..... | 229 | +| 9.7.2 | Summary..... | 229 | +| 10 | Impact on RF requirements..... | 229 | +| 10.1 | Impact on BS RF requirements..... | 229 | +| 10.1.1 | General..... | 229 | +| 10.1.2 | Impact on BS TX requirements..... | 230 | +| 10.1.2.1 | Base Station output power and radiated transmit power..... | 230 | +| 10.1.2.2 | Output power dynamics..... | 230 | +| 10.1.2.3 | Transmit ON/OFF power..... | 230 | +| 10.1.2.4 | Transmitted signal quality..... | 230 | +| 10.1.2.5 | Unwanted emissions..... | 230 | +| 10.1.2.6 | Transmitter intermodulation..... | 231 | +| 10.1.3 | Impact on BS RX requirements..... | 231 | +| 10.1.3.1 | Reference sensitivity level and OTA sensitivity..... | 231 | +| 10.1.3.2 | Dynamic range..... | 231 | +| 10.1.3.3 | In-band selectivity and blocking..... | 231 | +| 10.1.3.4 | Out-of-band blocking..... | 232 | +| 10.1.3.5 | Receiver spurious emissions..... | 232 | +| 10.1.3.6 | Receiver intermodulation..... | 232 | +| 10.1.3.7 | In-channel selectivity..... | 232 | +| 10.1.4 | Potentially new requirements for SBFD operation..... | 232 | +| 10.1.4.1 | Transmitter transient period..... | 232 | +| 10.1.4.2 | In-channel adjacent subband leakage ratio..... | 232 | +| 10.1.4.3 | In-channel adjacent subband Blocking and adjacent subband selectivity..... | 232 | +| 10.2 | Impact on UE RF requirements..... | 233 | +| 11 | Adjacent channel co-existence evaluation results..... | 233 | +| 11.1 | Introduction..... | 233 | +| 11.2 | Summary of all simulation results..... | 234 | +| 11.3 | Conclusion..... | 236 | +| 11.3.1 | Case 1: aggressor SBFD DU victim NR TDD DL..... | 236 | +| 11.3.2 | Case 2: aggressor SBFD DU victim NR TDD UL..... | 236 | +| 11.3.3 | Case 3: aggressor NR TDD DL victim SBFD DU..... | 237 | +| 11.3.4 | Case 4: aggressor NR TDD UL victim SBFD DU..... | 238 | +| 11.3.5 | General remarks on coexistence findings..... | 239 | +| 12 | Regulatory aspects for deploying the duplex enhancements in TDD unpaired spectrum..... | 239 | +| 12.1 | ITU Region 1..... | 239 | +| 12.1.1 | Europe..... | 239 | +| 12.2 | ITU Region 2..... | 240 | +| 12.2.1 | North America..... | 240 | +| 12.3 | ITU Region 3..... | 240 | +| 12.3.1 | Australia..... | 240 | +| 12.3.2 | China..... | 240 | +| 12.3.3 | India..... | 241 | +| 12.3.4 | Japan..... | 241 | +| 12.3.5 | Korea..... | 241 | +| 12.3.6 | New Zealand..... | 241 | +| 12.4 | Summary..... | 241 | +| 13 | Conclusions and recommendations..... | 242 | +| 13.1 | SBFD..... | 242 | +| 13.1.1 | RAN1..... | 242 | + +| | | | +|-----------------------------------------------------------------------------|-----------------------------------------------------------|------------| +| 13.1.1.1 | UPT performance..... | 242 | +| 13.1.1.2 | Coverage performance..... | 250 | +| 13.1.1.3 | SBFD operation scheme..... | 250 | +| 13.1.1.4 | CLI handling scheme..... | 251 | +| 13.1.2 | RAN4..... | 251 | +| 13.2 | Dynamic/flexible TDD..... | 251 | +| Annex <A>: Evaluation methodologies..... | | 253 | +| Annex <B>: System level simulation..... | | 253 | +| B.1 | System level simulation assumptions..... | 253 | +| B.2 | System level simulation results for semi-static SBFD..... | 253 | +| B.3 | System level simulation results of schemes for SBFD..... | 253 | +| B.4 | System level simulation results for dynamic TDD..... | 253 | +| Annex <C>: System level simulation calibration..... | | 253 | +| Annex <D>: Link level evaluation for coverage performance..... | | 253 | +| Annex <E>: Adjacent channel co-existence evaluation..... | | 253 | +| Annex <X>: Change history..... | | 254 | + +--- + +# 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 results and findings from the study item "Study on Evolution of NR Duplex Operation" [2]. The purpose of this TR is to document the follows for evolution of NR duplex operation: + +- applicable and relevant deployment scenarios. +- evaluation methodology and assumptions. +- possible schemes/enhancements, feasibility and performance evaluation results of subband non-overlapping full duplex and dynamic/flexible TDD. +- summary of the regulatory aspects that have to be considered for deploying the identified duplex enhancements in TDD unpaired spectrum. + +This activity involves the Radio Access work area of the 3GPP studies and has potential impacts both on the Mobile Equipment and Access Network of the 3GPP systems. + +--- + +# 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-213591, New SI: Study on evolution of NR duplex operation. +- [3] 3GPP TR 38.901: "Study on channel model for frequencies from 0.5 to 100 GHz". +- [4] 3GPP TR 36.843: "Study on LTE Device to Device Proximity Services; Radio Aspects". +- [5] 3GPP TR 38.802: "Study on New Radio Access Technology Physical Layer Aspects". +- [6] 3GPP TR 36.873: "3D channel model for LTE". +- [7] 3GPP TR 36.814: "Further advancements for E-UTRA physical layer aspects". +- [8] 3GPP TR 36.889: "Study on Licensed-Assisted Access to Unlicensed Spectrum". +- [9] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone". +- [10] 3GPP TS 38.101-2: "NR; User Equipment (UE) radio transmission and reception; Part 2: Range 2 Standalone". +- [11] Report ITU-R M.2412: "Guidelines for evaluation of radio interface technologies for IMT-2020". +- [12] RP-180524, Summary of calibration results for IMT-2020 self evaluation. +- [13] 3GPP TR 38.830: "Study on NR coverage enhancements". +- [14] R1-2304212, Summary on SLS calibration results for NR duplex evolution +- [15] R1-2307274, On evaluations for NR duplex evolution, Apple +- [16] R1-2307083, SBFD evaluation results, CATT + +- [17] R1-2307192, Evaluation on NR duplex evolution, CMCC +- [18] R1-2307324, Evaluation of NR duplex evolution, Ericsson +- [19] R1-2308336, Discussion on evaluation and methodologies on evolution of NR duplex operation, Huawei, HiSilicon +- [20] R1-2306695, Discussion on evaluations on NR duplex evolution, InterDigital, Inc. +- [21] R1-2306885, Study on Evaluation for NR duplex evolution, LG Electronics +- [22] R1-2306814, Discussion on evaluation of NR duplex evolution, MediaTek Inc. +- [23] R1-2306400, Discussion for Evaluation on NR duplex evolution, New H3C Technologies Co., Ltd. +- [24] R1-2306874, On the evaluation methodology for NR duplexing enhancements, Nokia, Nokia Shanghai Bell +- [25] R1-2307571, Discussion on evaluation on NR duplex evolution, OPPO +- [26] R1-2307922, On Deployment scenarios and evaluation Methodology for NR duplex evolution, Qualcomm Incorporated +- [27] R1-2306642, Discussion on evaluation on NR duplex evolution, Spreadtrum Communications, BUPT, New H3C +- [28] R1-2307674, Discussion on evaluation for NR duplex evolution, Samsung +- [29] R1-2307817, Evaluation of NR duplex evolution, Sharp +- [30] R1-2306906, SBFD System Level Simulation Results, Sony +- [31] R1-2307381, Discussion on evaluation on NR duplex evolution, Xiaomi +- [32] R1-2306981, Prototype and Simulation Results for SBFD, ZTE +- [33] R1-2306746, Evaluation on NR duplex evolution, vivo +- [34] R1-2308001, LLS for evaluation of coverage performance in TDD and SBFD systems, CEWiT +- [35] R1-2308101, Evaluation on NR duplex operation, China Unicom, Huawei, HiSilicon +- [36] R1-2307471, Discussion on evaluation on NR duplex evolution, NTT DOCOMO, INC. +- [37] R1-2307330, Discussion on evaluation on NR duplex evolution, Panasonic +- [38] R1-2307159, Evaluation on NR duplex evolution, Fujitsu +- [39] R1-2306835, Evaluations on NR Duplex Evolution, Intel Corporation +- [40] R1-2307084, Discussion on subband non-overlapping full duplex, CATT +- [41] R1-2307325, Subband non-overlapping full duplex, Ericsson +- [42] R1-2307619, Field test for dynamic/flexible TDD, China Telecom, ZTE +- [43] R1-2306983, Discussion of enhancements on dynamic/flexible TDD, ZTE, China Telecom +- [44] R1-2307326, Potential enhancements of dynamic TDD, Ericsson +- [45] R1-2305035, SBFD System Level Simulation Results, Sony +- [46] R4-2214376, Reply LS on interference modelling for duplex evolution, Samsung, CMCC, Qualcomm +- [47] R4-2220244, WF for the feasibility from BS aspect, Samsung + +- [48] R4-2300690, Further considerations on SBFD BS RF aspects, Nokia, Nokia Shanghai Bell +- [49] R4-2305917, WF on implementation feasibility of SBFD: Co-channel Co-site/inter-site interference, Ericsson +- [50] R4-2219633, BS RF feasibility considerations, Ericsson +- [51] ECC Report 281, Analysis of the suitability of the regulatory technical conditions for 5G MFCN operation in the 3400-3800 MHz band, approved 6 July 2018. Online available: +- [52] ECC Recommendation(20)03, Frame structures to facilitate cross-border coordination of TDD MFCN in the frequency band 3400-3800 MHz, approved 23 October 2020. Online available: +- [53] ECC Report 331, Efficient usage of the spectrum at the border of CEPT countries between TDD MFCN in the frequency band 3400- 3800 MHz, approved 05 November 2021. Online available: +- [54] ECC Decision(11)06, Harmonised frequency arrangements and least restrictive technical conditions (LRTC) for mobile/fixed communications networks (MFCN) operating in the band 3400-3800 MHz, amended 26 October 2018. Online available: +- [55] FCC-21-32, "FCC Opens 100 Megahertz of Mid-Band Spectrum for 5G," March 2021. Online available: +- [56] FCC, "Part 27 – Miscellaneous Wireless Communications Services," last amended on August 7, 2023. Online available: +- [57] FCC, "Part 96 – Citizens Broadband Radio Service," last amended on August 7, 2023. Online available: +- [58] FCC-20-22, "Expanding Flexible Use of the 3.7 to 4.2 GHz Band," March 3, 2020. Online available: +- [59] OnGo Alliance, "CBRS Coexistence Technical Specifications," OnGo-TS-2001 V4.1.0, March 8, 2022. Online available: [https://ongoalliance.org/wp-content/uploads/2022/03/OnGo-TS-2001\\_v4.1.0\\_-Published-March-08-2022.pdf](https://ongoalliance.org/wp-content/uploads/2022/03/OnGo-TS-2001_v4.1.0_-Published-March-08-2022.pdf) +- [60] ISED, "Decision on the Technical and Policy Framework for the 3650-4200 MHz Band and Changes to the Frequency Allocation of the 3500-3650 MHz Band," May 2021. Online available: +- [61] MSIT, "Ministry of Science and ICT Announcement No. 2018-235," May 4, 2018. Online available: +- [62] MSIT, "Enforcement Decree Of The Radio Waves Act," June 7, 2023. Online available: +- [63] Radio Spectrum Management, “Technical Arrangement of the 3.5 GHz Band,” June 2019. Online available: +- [64] 3GPP TR 36.942: "Radio Frequency (RF) system scenarios". +- [65] 3GPP TS 38.213: "NR;Physical layer procedures for control". + +- [66] 3GPP TR 38.803: "Study on new radio access technology: Radio Frequency (RF) and co-existence aspects". +- [67] R4-2216404, SBFD gNB Radio and antenna considerations, Ericsson +- [68] R4-2301885, BS RF feasibility considerations, Ericsson +- [69] R4-2321079, Simulation results for SBFD coexistence, CMCC + +## 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]. + +| | | +|------|--------------------------------------------| +| ACIR | Adjacent Channel Interference Ratio | +| ACLR | Adjacent Channel Leakage Ratio | +| ACS | Adjacent Channel Selectivity | +| AOA | Azimuth angle Of Arrival | +| AOD | Azimuth angle Of Departure | +| AS | Angular Spread | +| ASA | Azimuth angle Spread of Arrival | +| ASD | Azimuth angle Spread of Departure | +| CDF | Cumulative Distribution Function | +| CLI | Cross link interference | +| EIRP | Effective Isotropic Radiated Power | +| IBE | In-Band Emission | +| ICS | In Channel Selectivity | +| ISD | Intersite Distance | +| LOS | Line Of Sight | +| MIMO | Multiple-Input-Multiple-Output | +| NLOS | Non-LOS | +| O2I | Outdoor-to-Indoor | +| O2O | Outdoor-to-Outdoor | +| OFDM | Orthogonal Frequency-Division Multiplexing | +| PRB | Physical Resource Block | +| RMa | Rural Macro | +| RSI | Ratio of self-interference | +| RSRP | Reference Signal Received Power | +| RU | Resource Utilization | +| Rx | Receiver | +| SBFD | Subband non-overlapping Full Duplex | +| SI | Self-Interference | +| SINR | Signal-to-Interference-plus-Noise Ratio | +| SLS | System Level Simulation | + +| | | +|-------|-------------------------------------| +| TBoMS | TB processing over multi-slot PUSCH | +| TRP | Transmission Reception Point | +| Tx | Transmitter | +| TxRU | Transceiver Unit | +| UMa | Urban Macro | +| UMi | Urban Micro | +| UPT | User Perceived Throughput | +| ZOA | Zenith angle Of Arrival | +| ZOD | Zenith angle Of Departure | +| ZSA | Zenith angle Spread of Arrival | +| ZSD | Zenith angle Spread of Departure | + +--- + +## 4 Introduction + +TDD is widely used in commercial NR deployments. In TDD, the time domain resource is split between downlink and uplink. Allocation of a limited time duration for the uplink in TDD would result in reduced coverage, increased latency and reduced capacity. As a possible enhancement on this limitation of the conventional TDD operation, it would be worth studying the feasibility of allowing the simultaneous existence of downlink and uplink, a.k.a. full duplex, or more specifically, subband non-overlapping full duplex at the gNB side within a conventional TDD band. + +The NR TDD specifications allow the dynamic/flexible allocation of downlink and uplink in time and CLI handling and RIM for NR were introduced in Rel-16. Nevertheless, further study may be required for CLI handling between the gNBs of the same or different operators to enable the dynamic/flexible TDD in commercial networks. The inter-gNB CLI may be due to either adjacent-channel CLI or co-channel-CLI, or both, depending on the deployment scenario. One of the problems not addressed in the previous releases is gNB-to-gNB CLI. + +This study aims to identify the feasibility and solutions of duplex evolution in the areas outlined above to provide enhanced UL coverage, reduced latency, improved system capacity, and improved configuration flexibility for NR TDD operations in unpaired spectrum. In addition, the regulatory aspects need to be examined for deploying identified duplex enhancements in TDD unpaired spectrum considering potential constraints. + +--- + +## 5 Objectives of study + +The objective of this study is to identify and evaluate the potential enhancements to support duplex evolution for NR TDD in unpaired spectrum. + +In this study, the followings are assumed: + +- Duplex enhancement at the gNB side +- Half duplex operation at the UE side +- No restriction on frequency ranges + +The detailed objectives are as follows: + +- Identify applicable and relevant deployment scenarios (RAN1). +- Develop evaluation methodology for duplex enhancement (RAN1). +- Study the subband non-overlapping full duplex and potential enhancements on dynamic/flexible TDD (RAN1, RAN4). + - Identify possible schemes and evaluate their feasibility and performances (RAN1). + - Study inter-gNB and inter-UE CLI handling and identify solutions to manage them (RAN1). + - Consider intra-subband CLI and inter-subband CLI in case of the subband non-overlapping full duplex. + - Study the performance of the identified schemes as well as the impact on legacy operation assuming their co-existence in co-channel and adjacent channels (RAN1). + +- Study the feasibility of and impact on RF requirements considering adjacent-channel co-existence with the legacy operation (RAN4). +- Study the feasibility of and impact on RF requirements considering the self-interference, the inter-subband CLI, and the inter-operator CLI at gNB and the inter-subband CLI and inter-operator CLI at UE (RAN4). +- Note: RAN4 should be involved early to provide necessary information to RAN1 as needed and to study the feasibility aspects due to high impact in antenna/RF and algorithm design, which include antenna isolation, TX IM suppression in the RX part, filtering and digital interference suppression. +- Summarize the regulatory aspects that have to be considered for deploying the identified duplex enhancements in TDD unpaired spectrum (RAN4). + +Note: For potential enhancements on dynamic/flexible TDD, utilize the outcome of discussion in Rel-15 and Rel-16 while avoiding the repetition of the same discussion. + +## 6 Subband non-overlapping full duplex (SBFD) + +### 6.1 General aspects of SBFD schemes + +#### 6.1.1 SBFD Operations + +For discussion purpose, for SBFD operation within a TDD carrier, a SBFD subband consists of 1 RB or a set of consecutive RBs for the same transmission direction. For discussion purpose, SBFD symbol is defined as symbol with subbands that gNB would use for SBFD operation. + +SBFD operation within a TDD carrier is studied and SBFD scheme within a single configured DL and UL BWP pair with aligned center frequencies is the baseline. + +The maximum number of UL subbands for SBFD operation in an SBFD symbol (excluding legacy UL symbol) within a TDD carrier is one for the study in RAN1. The UL subband can be located at one side of the carrier or can be located at the middle part of the carrier + +Whether SBFD operation in SSB symbols is supported or not is studied in RAN1. RAN1 studied whether UL subband can be configured in SSB symbol and agreed that an UL subband can be configured in an SSB symbol, where SSB is from serving cell perspective which can be CD-SSB or NCD-SSB. If SBFD-aware UEs are not allowed to transmit in the SSB symbol but is allowed to receive within the DL BWP in the SSB symbol, negative impact on SSB detection and measurement can be avoided but UL performance may be degraded due to fewer UL opportunities. If SBFD-aware UE is allowed to transmit in the SSB symbol, the UE may only transmit UL in an UL subband depending on gNB scheduling, configuration, UE measurement or priority rule. There may be negative impact on SSB detection and measurement if the SBFD-aware UE is requested to transmit in the SSB symbol. + +Whether or not a slot can consist of both SBFD and non-SBFD symbols is studied in RAN1 including benefits, use cases, scheduling flexibility, implementation complexity and compatibility with legacy TDD DL/UL configuration. One motivation for allowing that a slot can consist of both SBFD and non-SBFD symbols is for compatibility with symbol-level TDD UL/DL configuration. Frequent transition between SBFD and non-SBFD symbols may increase the implementation complexity and interruptions of transmissions/receptions during transition. At least for semi-static SBFD, in order to avoid frequent transition between SBFD and non-SBFD symbols, potential limitation on the maximum number of transition points between SBFD and non-SBFD symbols can be considered from SBFD subband configuration perspective. Maximum of two transition points including one transition point from non-SBFD symbols to SBFD symbols and one transition point from SBFD symbols to non-SBFD symbols within a TDD UL/DL pattern period can be considered as a starting point where the transition point can be aligned with slot boundary or within a slot. A guard period between SBFD and non-SBFD symbols may or may not be required at gNB and/or UE side depending on gNB/UE implementation and/or SBFD operation. + +The time and frequency location of subbands within a TDD carrier are not fixed in the specification. Regarding whether to inform the UE of the time and/or frequency location of subbands that gNB would use for SBFD operation, the following options are studied with Option 4 prioritized at least for RRC\_CONNECTED state. + +- SBFD operation Option 1: + - Time and frequency locations of subbands for SBFD operation are not known to UEs. + - UE behaviors follow existing specifications without introducing new UE behaviors for SBFD operation at gNB side. +- SBFD operation Option 2: + - Time and frequency locations of subbands for SBFD operation are not known to UEs. + - UE behaviors for non-SBFD aware UEs follow existing specifications. + - From RAN1 perspective, new UE behaviors can be introduced for SBFD aware UEs +- SBFD operation Option 3: + - Only time location of subbands for SBFD operation is known to SBFD aware UEs. + - UE behaviors for non-SBFD aware UEs follow existing specifications. + - From RAN1 perspective, new UE behaviors can be introduced for SBFD aware UEs based on the time location of subbands for SBFD operation +- SBFD operation Option 4: + - Both time and frequency locations of subbands for SBFD operation are known to SBFD aware UEs. + - UE behaviors for non-SBFD aware UEs follow existing specifications. + - From RAN1 perspective, new UE behaviors can be introduced for SBFD aware UEs based on the time and frequency locations of subbands for SBFD operation. + +Among the four options, SBFD operation Option 4 is agreed as the baseline for SBFD operation at least for RRC\_CONNECTED state. + +Random access in SBFD symbols is studied in RAN1. If random access is allowed in SBFD symbols for SBFD-aware UEs, it may potentially reduce the random access latency, reduce the PRACH collision probability and/or improve the coverage of PRACH and Msg3. These aspects were not fully evaluated in RAN1. PRACH and Msg3 transmissions in UL subband in SBFD symbols may cause UE-to-UE CLI. The system performance impact is not evaluated in RAN1. Specification impact is expected to allow random access in SBFD symbols at least for PRACH and Msg3 transmissions in symbols configured as DL in *TDD-UL-DL-ConfigCommon*. + +#### 6.1.1.1 Semi-static configuration of SBFD subbands + +For indication of subband locations for SBFD operation, semi-static configuration of subband time and frequency location is studied as baseline. + +For semi-static configuration of subband time locations for SBFD operation, it is agreed that explicit configuration of SBFD subband time locations within a period is the baseline. + +For semi-static configuration of subband frequency locations for SBFD operation, at least explicit indication of frequency location of UL subband is required. At least for semi-static SBFD, the following two options are viable solutions for frequency location configuration of DL subband(s) and guardband(s) if any. + +- Option 1: Frequency locations of DL subband(s) are explicitly configured. Guardband(s) if any are implicitly derived as the RBs which are not within UL subband or DL subband(s). +- Option 2: The number of RBs for guardband(s), if any, is explicitly configured. DL subband(s) are implicitly derived as RBs which are not within UL subband or guardband(s). + +For semi-static SBFD, a SBFD aware UE does not transmit UL channels/signals or receive DL channels/signals on the guardband(s) that the UE is aware of. + +Furthermore, for the purpose of RAN1 study, the understanding is that for semi-static configuration of subband frequency locations for SBFD operation, frequency location of UL/DL subband is with reference to CRB grid. For semi-static configuration of subband location, same subband frequency resources across different SBFD symbols are considered as baseline. + +#### 6.1.1.2 SBFD operation in symbols configured as DL in *TDD-UL-DL-ConfigCommon* + +For a SBFD aware UE semi-statically configured with UL subband in a SBFD symbol configured as DL in *TDD-UL-DL-ConfigCommon*, the following is agreed as baseline in the RAN1 study: + +- UL transmissions within UL subband are allowed in the symbol +- UL transmissions outside UL subband are not allowed in the symbol +- Frequency locations of DL subband(s) are known to the SBFD aware UE + - The frequency location of DL subband(s) can be explicitly indicated or implicitly derived +- DL receptions within DL subband(s) are allowed in the symbol +- Note: UL transmissions are within active UL BWP and DL receptions are within active DL BWP in the symbol + +In addition, whether DL receptions outside semi-statically configured DL subband(s) are allowed or not in a symbol configured as DL in *TDD-UL-DL-ConfigCommon* for SBFD aware UEs are studied based on the following options: + +- Option 1 (semi-static SBFD): DL receptions outside semi-statically configured DL subband(s) are not allowed +- Option 2: (dynamic SBFD): DL receptions outside semi-statically configured DL subband(s) are allowed + +#### 6.1.1.3 SBFD operation in symbols configured as flexible in *TDD-UL-DL-ConfigCommon* + +For SBFD operation in a symbol configured as flexible in *TDD-UL-DL-ConfigCommon*, the following alternatives are studied for SBFD aware UEs, + +Alt 1: + +- UL transmissions within UL subband are allowed in the symbol +- UL transmissions outside UL subband are not allowed in the symbol +- Frequency locations of DL subband(s) are known to the SBFD aware UE +- DL receptions within DL subband(s) are allowed in the symbol +- FFS: Whether DL receptions outside DL subband(s) are allowed or not in the symbol + +Alt 2: + +- UL transmissions within UL subband are allowed in the symbol +- The RBs outside the UL subband can be used as either UL, or DL excluding guardband(s) if used, in the symbol from gNB's perspective, and the transmission direction for all those RBs is the same + - FFS: SBFD aware UE behaviours + - FFS: Whether or not signalling of guardband(s) is needed +- FFS: Whether or not the symbol can be converted to a DL-only symbol +- Frequency locations of DL subband(s) are known to the SBFD aware UE +- DL receptions within DL subband(s) are allowed in the symbol + +Note: UL transmissions are within active UL BWP and DL receptions are within active DL BWP in the symbol for both options. For all RBs outside the UL subband, UE cannot use separate RBs for DL and UL simultaneously. + +In addition, whether DL receptions outside semi-statically configured DL subband(s) and UL transmissions outside semi-statically configured UL subband are allowed or not in a symbol configured as flexible in *TDD-UL-DL-ConfigCommon* for SBFD aware UEs are studied based on the following options: + +- Option 1 (semi-static): DL receptions outside semi-statically configured DL subband(s) are not allowed and UL transmissions outside semi-statically configured UL subband are not allowed +- Option 2 (dynamic SBFD): DL receptions outside semi-statically configured DL subband(s) are allowed + - UL transmissions outside the semi-statically configured UL subbands are not allowed +- Option 3 (dynamic SBFD): DL receptions outside semi-statically configured DL subband(s) are allowed + - UL transmissions outside the semi-statically configured UL subbands are allowed + +#### 6.1.1.4 Dynamic SBFD + +For dynamic SBFD, the following observations are agreed. + +- Compared to semi-static SBFD, dynamic SBFD can better adapt to the UL/DL resource requirements based on UL/DL traffic loads. +- Dynamic SBFD may increase gNB implementation complexity due to dynamic antenna/panels switching and filters/RF tuning, may incur loss of resources due to transition time, may increase inter-gNB CLI, may increase scheduling complexity, and can result in additional specification impact on top of semi-static SBFD +- UE implementation complexity may be increased if the UE supports dynamic SBFD and dynamic SBFD may result in increased UE-to-UE CLI + +If dynamic SBFD is supported, the following options can be considered. + +- Option 1: Dynamic SBFD is achieved by scheduling DCI which is used to schedule DL receptions outside semi-statically configured SBFD DL subband and/or UL transmission outside semi-statically configured SBFD UL subband. +- Option 2: Dynamic SBFD is achieved by non-scheduling DCI which indicates whether a symbol is SBFD symbol or not. +- Option 3: Dynamic SBFD is achieved by MAC-CE which indicates whether a symbol is SBFD symbol or not. + +Note 1: Whether or not dynamic SBFD is beneficial from a performance and complexity perspective is a separate discussion. + +Note 2: The possibility of introducing flexible subband type for Option 1 to achieve DL receptions outside semi-statically configured SBFD DL subband and/or UL transmission outside semi-statically configured SBFD UL subband is not precluded. + +Note 3: None of the above options imply that there is a dynamic change in the DL/UL subband sizes. + +## 6.1.2 Impact and potential enhancements for transmissions and receptions + +Impact and potential enhancements for UL transmissions and DL receptions across SBFD symbols and non-SBFD symbols, including at least the following, are studied: + +- PDCCH, scheduled/configured PUCCH/PUSCH/PDSCH, without repetition in SBFD symbols and non-SBFD symbols +- Scheduled/configured SRS/CSI-RS in SBFD symbols and non-SBFD symbols +- Scheduled/configured TBoMS across SBFD symbols and non-SBFD symbols with or without repetition +- Multi-PUSCH/PDSCH scheduled by a single DCI in SBFD symbols and non-SBFD symbols +- Scheduled/configured PDSCH/PUSCH/PUCCH with repetitions across SBFD symbols and non-SBFD symbols + +Note: Inter-slot/intra-slot/inter-repetition/inter-group frequency hopping with DMRS bundling of PUSCH/PUCCH, if applicable, is considered. + +Examples of potential enhancements include: + +- Resource allocation in frequency domain including frequency hopping +- Resource allocation in time domain +- Power domain +- Spatial domain + +RAN1 studied the impact and benefits of potential enhancements to resource allocation in frequency-domain for SBFD operation, considering unaligned boundaries between resource block group(s)/reporting subband(s) and SBFD subbands, including at least the following: + +- RBG for PDSCH RA type 0 +- CSI reporting configuration +- CSI-RS resource configuration +- PRG of PDSCH + +For resource allocation in frequency-domain in case of unaligned boundaries between RBG and SBFD subbands, RAN1 studied whether or not the part of the DL RBG inside/outside the DL subband and the part of the UL RBG inside/outside the UL subband can be used. It is agreed that for SBFD-aware UEs, the part of the DL RBG inside the DL subband can be used and the part of the UL RBG inside the UL subband can be used for better resource utilization. It is agreed that the part of the RBG outside the DL subband cannot be used for DL reception and the part of the RBG outside the UL subband cannot be used for UL transmission at least for semi-static SBFD. + +For semi-static SBFD, for a CSI reporting subband which overlaps with SBFD subband boundaries, it is agreed that CSI report is derived based on CSI-RS resources excluding CSI-RS resources outside DL subband(s) for SBFD-aware UE. + +For semi-static SBFD, for a CSI-RS resource which overlaps with SBFD subband boundaries, it is agreed that only CSI-RS resources within DL subband(s) are valid for SBFD-aware UE. + +For SBFD-aware UEs, at least the following issues for PDSCH are studied: + +- PRG(s) with size of 2 and 4 that overlaps with subband boundary +- Wideband precoder in case of non-contiguous DL subbands + +For a PRG that overlaps with subband boundary, if the part of DL PRG inside the DL subband can be used, better scheduling flexibility and resource utilization can be achieved, however degraded channel estimation quality in the partial PRG is expected compared to a PRG due to limited RBs in the partial PRG. It is noted that UE complexity could increase if this feature is supported. + +If PRG is determined as wideband, the following two options are studied. + +- Option 1: non-contiguous frequency resources across two DL subbands but contiguous frequency resource within each DL subband can be allocated +- Option 2: non-contiguous frequency resources across two DL subbands cannot be allocated + +It is agreed that Option 1 can achieve better scheduling flexibility and higher DL data rate. Compared with Option 2, Option 1 requires UE to handle two non-contiguous segments of contiguous RBs that may increase UE complexity for channel estimation. + +Frequency resource allocation for CSI-RS across downlink subbands for SBFD-aware UEs are studied considering the following options: + +- Option 1: Two contiguous CSI-RS resources that are linked + +- Option 2: One CSI-RS resource + - Option 2-1: Non-contiguous CSI-RS resource allocation + - Option 2-2: One contiguous CSI-RS resource allocation with non-contiguous CSI-RS resource derived by excluding frequency resources outside DL subband (s) + +For all the options, there is no impact on CSI-RS sequence generation. Option 1 requires additional signalling to link two CSI-RS resources in two DL subbands. Option 2-1 requires new RRC structure to configure non-contiguous RBs for one CSI-RS resource, which may require additional signalling overhead. Option 2-2 can reuse the existing signalling design for CSI-RS resource configuration. Option 2-2 can be used to resolve the potential unaligned boundaries between CSI-RS resource configuration and SBFD subbands. Further discussion is required on the UE complexity due to UE capability of maximum number of configured CSI-RS resources and/or processing non-contiguous CSI-RS. + +For UL transmissions and DL receptions across SBFD symbols and non-SBFD symbols in different slots (each transmission/reception within a slot has either all SBFD or all non-SBFD symbols), the following options are studied for SBFD-aware UEs: + +- Option 1: The transmissions/receptions are restricted to SBFD symbols only or non-SBFD symbols only +- Option 2: The transmissions/receptions can be in SBFD symbols and non-SBFD symbols + +UL transmissions and DL receptions across SBFD symbols and non-SBFD symbols include the following: + +- PDSCH/PUSCH/PUCCH repetitions +- SPS PDSCH/CG PUSCH +- TBoMS +- Multi-PUSCH/PDSCH scheduled by a single DCI +- Periodic/semi-persistent SRS/CSI-RS/PUCCH +- PDCCH + +Option 1 can be achieved by gNB configuration or scheduling to ensure that all transmission/reception occasions are confined to either SBFD symbols or non-SBFD symbols. Alternatively, Option 1 can be achieved by additional indication or rules to determine the transmission/reception occasions are valid within one symbol type and are invalid within the other symbol type. The frequency resources, power control and beam/spatial relation for all the transmission/reception occasions can be the same for Option 1 but may be different for Option 2. If different, it may require additional specification efforts. Option 1 may or may not increase the transmission/reception latency if the transmission/reception in the other symbol type is postponed and may degrade the performance if the transmission/reception in the other symbol type is dropped. Option 2 may or may not reduce the transmission/reception latency and improve coverage. + +For UL transmissions and DL receptions across SBFD symbols and non-SBFD symbols in different slots (each transmission/reception within a slot has either all SBFD or all non-SBFD symbols), if the transmissions/receptions can be in SBFD symbols and non-SBFD symbols with different available resources, at least the following frequency resource allocation options for PDSCH, CSI-RS, PUSCH, PUCCH, SRS for SBFD-aware UE are studied. + +- Option 1: Separate FDRA determination for SBFD slots and non-SBFD slots. + - Option 1-1: Separate FDRA configurations/indications for SBFD slots and non-SBFD slots + - Option 1-2: Separate frequency resources determined for SBFD slots and non-SBFD slots based on single FDRA configuration/indication + - Option 1-3: single FDRA configuration/indication and RB offset(s) +- Option 2: Perform rate matching or puncturing on the RBs outside DL/UL subbands for DL/UL channels/signals. + +- Option 3: A DL/UL channel/signal overlapping with RBs outside DL/UL subbands in a SBFD slot is dropped or postponed. + +Note: Different options can be studied for different signals/channels. + +RAN1 studied whether the transmission/reception occasion of a physical channel/signal can be mapped to SBFD and non-SBFD symbols within a slot for a UE, and whether a UE can transmit/receive in the occasion mapped to SBFD symbols and non-SBFD symbols including: + +- Use-case(s) including the locations and number of transition points of the SBFD and non-SBFD symbols in the slot. +- Potential benefits if any +- Phase continuity +- Potential interruption of transmissions/receptions during transition +- Required guard time if any +- Potential impact on performance +- Impact on link adaptation, channel estimation, and other procedures +- UL transmission timing if any +- Implementation complexity +- Applicability for SBFD aware UE and non-SBFD aware UEs +- NOTE: There are more than one scenario where a transmission overlaps SBFD and non-SBFD symbols and some may or may not face the aspects listed above +- NOTE: This study doesn't mean RAN1 agreement on a slot consisting of SBFD and non-SBFD symbols. + +For a physical channel/signal occasion mapped to SBFD and non-SBFD symbols within a slot if any, the following options for UE transmission/reception can be considered in the normative stage. + +- Option 1: UE does not transmit or receive the physical channel/signal within the slot. +- Option 2: UE can transmit or receive the physical channel/signal within the slot only under certain conditions. + - The conditions may depend on at least the following: whether or not phase continuity can be maintained across SBFD and non-SBFD symbols, whether or not there are same or different transmission/reception parameters e.g. power control, spatial/QCL, UL timing etc. applied in SBFD and non-SBFD symbols, and whether or not there is a guard period between the SBFD and non-SBFD symbols, etc. +- Other options are not precluded. + +For SBFD-aware UEs, the following options are studied for CSI report associated with periodic/semi-persistent CSI-RS, in case the periodicity is such that CSI-RS instances occur in both SBFD symbols and non-SBFD symbols in different slots (each CSI-RS resource within a slot has either all SBFD or all non-SBFD symbols): + +- Option 1: two *CSI-ReportConfigs*, where one is associated with SBFD symbols and the other is associated with non-SBFD symbols + - Option 1-1: One *CSI-ReportConfig* is associated with a CSI-RS restricted to SBFD symbols only and the second *CSI-ReportConfig* is associated with a second CSI-RS restricted to non-SBFD symbols only; + - Option 1-2: Both *CSI-ReportConfigs* are associated with the same CSI-RS. The CSI report associated with one *CSI-ReportConfig* is derived based on CSI-RS instances in SBFD symbols only. The CSI report associated with the second *CSI-ReportConfig* is derived based on CSI-RS instances in non-SBFD symbols only. +- Option 2: one *CSI-ReportConfig* associated with both SBFD symbols and non-SBFD symbols + +- Option 2-1: One *CSI-ReportConfig* is associated with two CSI-RSs which are restricted to SBFD symbols and non-SBFD symbols respectively. Separate CSI measurements are derived based on the first and second CSI-RSs respectively. +- Option 2-2: One *CSI-ReportConfig* is associated with one CSI-RS. The CSI report is derived based on CSI-RS which can be in SBFD symbols or non-SBFD symbols in different time instances. + +Note that whether the CSI-RS resource can be used for SBFD and non-SBFD symbols may depend on, e.g., gNB implementation of same/different antenna configuration in both symbols. + +Option 1-1 can be supported according to existing specification by gNB configuration of appropriate periodicities to ensure that the CSI-RS associated with each *CSI-ReportConfig* is confined to either SBFD symbols or non-SBFD symbols only. But it may restrict the gNB configuration flexibility and enhancements can be considered by additional indication or rules to determine the CSI-RS is valid within one symbol type and is invalid in the other symbol type. + +Option 2-2 can be supported according to existing specification to configure measurement restriction so that UE would not average CSI measurements across SBFD and non-SBFD symbols. + +For SRS, PUCCH and PUSCH on SBFD symbols and non-SBFD symbols in different slots, it may be beneficial to have separate resources, FH parameters, UL power control parameters and/or beam/spatial relation. + +gNB can configure a CORESET and a search space in a way such that the MOs of the search space occur in either SBFD or non-SBFD symbols, or the MOs of the search space occur in both SBFD and non-SBFD symbols but the associated CORESET does not overlap the boundary of a DL subband in SBFD symbols. + +If it is agreed to be beneficial that a CORESET and a search space are configured that the MOs of the search space occur in both SBFD and non-SBFD symbols and the associated CORESET overlaps the boundary of a DL subband in SBFD symbols, at least the following options can be considered for SBFD-aware UE: + +- Option 1: Separate valid resources for the CORESET in SBFD symbols and in non-SBFD symbols. +- Option 2: Rate matching or puncturing on the REG(s) of a PDCCH outside DL subband(s). +- Option 3: UE does not monitor a PDCCH candidate if it is mapped to one or more REs that overlap with REs outside DL subband(s). +- Option 4: Drop search space(s) when the associated CORESET overlaps with RBs outside DL subband(s) +- Option 5: Separate search spaces associated with a CORESET in SBFD and non-SBFD symbols + +Note: These options are applicable to at least USS. + +### 6.1.3 BS self-interference due to time misalignment + +Time misalignment at gNB between UL receptions and DL transmissions due to configuration of non-zero $N_{TA,offset}$ at UE can lead to increased interference assuming no gNB transmit chain impairments and no filtering of DL subband(s) in the gNB Rx chain. + +Simulation results from one source [41] show that the increase of self-interference on the UL subband due to misaligned timing between UL reception and DL transmission at the gNB can be quite small ( $\sim 1\text{dB}$ ) when impairments in the gNB transmit chains and filtering of DL subbands in the gNB Rx chains are considered. Filtering that suppresses self-interference from DL subbands in the gNB Rx chains could incur some switching time/delay to bypass the filter in UL symbols and could introduce some insertion loss. + +## 6.2 Inter-UE CLI handling schemes specific for SBFD + +For inter-UE inter-subband CLI measurement, at least the following methods are studied: + +- Method#1: victim UE measures RSSI within DL subband +- Method#2: victim UE measures RSRP of aggressor UE within UL subband +- Method#3: victim UE measures RSSI within UL subband + +- Note: the restriction in Rel-16 that CLI is only measured within DL BWP does not forbid UE to measure CLI in UL subband when UL subband is confined within DL BWP. + +For UE-to-UE CLI-RSSI measurement/report across downlink subbands, the following methods are studied. Note that Alt #1 and Alt #2 are supported in existing specifications. + +- Alt #1: separate CLI-RSSI measurement resources/reports in each DL subband +- Alt #2: CLI-RSSI measure/report in one DL subband only +- Alt #3: CLI-RSSI measurement/report based on non-contiguous CLI-RSSI resource across downlink subbands + +Alt #1 allows flexible configuration of measurement reporting in one DL subband or two DL subbands but it consumes multiple CLI-RSSI measurement resources from the UE capability budget. Alt #2 restricts gNB configuration flexibility and does not account for whether or not the CLI is asymmetric across two DL subbands. This method does not consume multiple CLI-RSSI measurement resources from UE capability point of view. Alt #3 requires additional specification efforts to support non-contiguous CLI-RSSI resource allocation across downlink subbands. This method is similar to non-contiguous CSI-RS resource allocation. A single CLI-RSSI report based on non-contiguous CLI-RSSI resource may be sufficient. This method does not consume multiple CLI-RSSI measurement resources from UE capability point of view. Note that it does not imply whether L1 or L2 based measurement is supported. + +Method #2 and Method #3 can be used for identifying the aggressor UE(s) if orthogonal resources are allocated for different aggressor UE(s). Method #2 and #3 can at least provide higher interference signal strength than inter-subband interference leakage based measurements in Method #1. Furthermore, such measurement is not subject to inter-cell DL interference. It is feasible for UE to measure RSRP/RSSI within UL subband if within active DL BWP and receive DL in DL subband(s) simultaneously similar as simultaneous RSRP/RSSI measurement and DL reception in Rel-16. The existing CLI measurement and report framework can be reused to support RSRP/RSSI measurements within UL subband when UL subband is confined within active DL BWP. + +## 7 Performance evaluation and its feasibility for SBFD + +### 7.1 Deployment scenarios + +The following deployment cases are considered for evaluation: + +- SBFD Deployment Case 1 (Non-coexistence case with single SBFD subband configuration): One single operator using one single carrier is considered. All the cells belonging to the operator use SBFD operation with the same SBFD subband configuration. +- SBFD Deployment Case 2 (Non-coexistence case with multiple SBFD subband configurations): One single operator using one single carrier is considered. All the cells belonging to the operator use SBFD operation, but different cells may use different SBFD subband configurations. +- SBFD Deployment Case 3 (Co-channel co-existence case): One single operator using one single carrier is considered. Among the cells belonging to the operator, some of them use legacy static TDD operation while the others use SBFD operation with the same SBFD subband configuration. + - Deployment Case 3-1: Only 1-layer is considered + - Deployment Case 3-2: 2-layer is considered. Layer 1 uses legacy static TDD operation, Layer 2 uses SBFD operation. All the gNBs in Layer 2 use the same SBFD subband configuration. +- SBFD Deployment Case 4 (Adjacent-channel co-existence case): Two operators each using one carrier are considered and the two carriers are adjacent carriers. One operator uses legacy static TDD operation while the other operator uses SBFD operation with the same SBFD subband configuration. + +Note that SBFD subband configuration is from gNB perspective. + +For SBFD Deployment Case 1, the following scenarios are considered: + +- FR1 + - 1-layer scenario + +- Indoor office +- Urban Macro +- (Optional) Dense Urban Macro layer +- 2-layer scenario + - (Optional) Dense Urban with 2-layer +- FR2-1 + - 1-layer scenario + - Indoor office + - Dense Urban Macro layer + - (Optional) Dense Urban Micro layer + +For SBFD Deployment Case 3-2, the following scenarios are considered: + +- FR1 + - 2-layer Scenario B + - Layer 1: Urban Macro + - Layer 2: + - Baseline: Indoor office + - Optional: Indoor factory + +For SBFD Deployment Case 4, the following scenarios are considered: + +- FR1 + - 1-layer scenario + - Urban Macro, considering 0% and 100% grid shift between two networks. +- FR2-1 + - 1-layer scenario + - Dense Urban Macro layer, considering 0% and 100% grid shift between two networks. + +The layouts and UE distributions for these scenarios can be found in Annex A.1. + +## 7.2 Evaluation methodologies + +### 7.2.1 System level simulation + +#### Interference Modelling + +The modelling methods for the following interference types can be found in Annex A.2. + +- gNB Self-Interference (SI) +- co-site inter-sector co-channel inter-subband CLI +- inter-site gNB-gNB co-channel inter-subband CLI +- UE-UE co-channel inter-subband CLI +- inter-site gNB-gNB adjacent-channel CLI + +- co-site gNB-gNB adjacent-channel CLI +- UE-UE adjacent-channel CLI + +### **Channel model** + +The details of gNB-UE channel model, gNB-gNB channel model, and UE-UE channel model can be found in Annex A.3. + +For gNB-gNB and UE-UE channel model in RAN1 SLS, large scale fading (e.g., path loss, penetration loss, shadowing) should be modelled, and companies are encouraged to report whether small scale fading (e.g., fast fading including antenna gain) is also modelled. Antenna gain is calculated based on the LOS direction instead on the multi-path directions if small scale fading is not modelled. + +### **Performance metrics** + +The following metrics are considered. The detailed definitions can be found in Annex A.4. + +- UPT related performance metrics + - Mean/5%/50%/95% Average-UPT, Average-UPT CDF + - Mean/5%/50%/95% Tail-UPT, Tail-UPT CDF + - Mean/5%/50%/95% Median-UPT, Median-UPT CDF +- Latency related performance metrics + - Baseline: Mean/5%/50%/95% Packet-Latency, Packet-Latency CDF + - Optional: Mean/5%/50%/95% UE-Average-Latency, UE-Average-Latency CDF +- Unfinished/dropped Packet Rate +- RU + - Type-1 RU + - Type-2 RU + +### **gNB Antenna configuration** + +The detailed gNB antenna configurations for SBFD evaluation can be found in Annex A.5. + +### **Traffic model** + +FTP model 3 is used and the details can be found in Annex A.6. + +### **SBFD subband and slot configurations** + +The following SBFD subband configurations are considered for SBFD evaluation: + +- SBFD Subband configuration#1 with {DUD} pattern, which means one SBFD slot consists of one UL subband at the center of the channel bandwidth and two DL subbands at two sides of the channel bandwidth. +- SBFD Subband configuration#2 with {DU} pattern, which means one SBFD slot consists of one UL subband at one side of the channel bandwidth and one DL subband at the other side of the channel bandwidth. + +The detailed SBFD subband configurations as well as the SBFD/legacy TDD slot configurations for evaluation can be found in Annex A.7. + +### **SLS assumptions** + +The SLS assumptions common to SBFD and dynamic/flexible TDD can be found in Table B.1-1 in Annex B. + +The SLS assumptions specific to SBFD Deployment Case 1 can be found in Table B.1-2 in Annex B. + +The SLS assumptions specific to SBFD Deployment Case 3-2 can be found in Table B.1-3 in Annex B. + +The SLS assumptions specific to SBFD Deployment Case 4 can be found in Table B.1-4 in Annex B. + +The SLS assumptions for interference modelling can be found in Table B.1-6 in Annex B. + +## 7.2.2 Link level evaluation + +Link level evaluation is performed to evaluate coverage performance of SBFD. It is up to companies to use SLS as a tool to evaluate coverage performance of SBFD, and it is also up to companies to perform link level evaluation for other purposes. + +For link level evaluation of coverage performance, RAN1 focuses on Urban Macro scenario for FR1 and Dense Urban Macro Layer scenario for FR2-1. Regarding the target uplink channel for coverage evaluation, RAN1 focuses on PUSCH with 1Mbps target data rate for FR1 and 5Mbps target data rate for FR2-1. + +For link level evaluation of coverage performance, single slot PUSCH transmission is assumed for baseline legacy TDD, and the following schemes of coverage enhancement can be assumed for SBFD: + +- Scheme-1: SBFD with PUSCH repetition type A +- Scheme-2: SBFD with TBoMS PUSCH +- Scheme-3: SBFD with PUSCH repetition type A and joint channel estimation +- Scheme-4: SBFD with TBoMS PUSCH and joint channel estimation +- For Scheme-3 and Scheme-4, two options are considered: + - Option 1 (baseline): joint channel estimation is applied only for the same symbol type + - Option 2: joint channel estimation is applied across SBFD and non-SBFD slots + +For link level evaluation of coverage performance, MPL, MCL and MIL defined in TR38.830 are used as the performance metrics. Similar evaluation methodology as defined in TR38.830 (i.e., LLS + Link budget analysis) can be used, and the performance metrics are obtained using link budget analysis and TDD/SBFD required SINR for target data rate. + +For link level simulation of coverage performance, RAN1 should consider self-interference, co-site inter-sector interference, inter-site gNB-gNB co-channel inter-subband CLI and UE-gNB interference in SBFD system and consider UE-gNB interference in TDD system. The following modelling methods can be considered. + +### Option-1: + +- The modelling method is as below: + - For TDD UL slot, additive white Gaussian noise with variance of $\sigma^2$ is generated, where $\sigma^2$ is UE-gNB interference and $\sigma^2$ is noise (in linear scale). + - For SBFD slot, additive white Gaussian noise with variance of $\sigma^2$ is generated, where $\sigma^2$ , $\sigma^2$ , $\sigma^2$ are self-interference, co-site inter-sector interference, inter-site gNB-gNB co-channel inter-subband CLI and UE-gNB interference (in linear scale), respectively + - Companies are encouraged to report the details of deriving $\sigma^2$ and $\sigma^2$ . Some examples are as below: + - Example-1: $\sigma^2$ and $\sigma^2$ are derived based on a certain assumption of the topology of gNBs and UEs. In this example, the interference is pre-receiver interference. + - Note: link budget analysis can be applied in this example + - Example-2: $\sigma^2$ is derived based on statistic in SLS, and then $\sigma^2$ is used in LLS to increase the Gaussian noise power in SBFD symbol compared to TDD UL symbol. In this example, the interference is post-receiver interference. + - Example-3: $\sigma^2$ and $\sigma^2$ can be derived based on statistic in SLS. In this example, the interference is post-receiver interference. + +- Companies are encouraged to report the RU assumption for the interference. +- Note: For simplicity, the interference is independently updated/generated in each slot. +- Note: Companies are encouraged to report whether and how channel estimation and interference estimation will be impacted by and . +- Based on the modelling method, the following high-level evaluation method can be used as an example for coverage performance evaluation: + - Step 1: For legacy TDD system, assume the SNR in UL only slot is , perform LLS to get the required SNR () with which UE can achieve a certain bit rate in UL + - Step 2: For SBFD system with frame structure XXXXU, assume the SNR in UL only slot is and the SNR in SBFD slot is . Perform LLS to get the required SNR () with which UE can achieve a certain bit rate in UL for a given SBFD coverage enhancement scheme (e.g., SBFD with PUSCH repetition type A, etc.) + - Step 3: Use Link budget template to obtain MPL, MCL and MIL for legacy TDD and SBFD. + - For legacy TDD, the required SNR () obtained in Step 1 is used to calculate MPL, MCL, MIL. + - For SBFD, the required SNR () obtained in Step 2 is used to calculate MPL, MCL, MIL. + +### Option-2: + +- The UE-gNB interference and inter-site gNB-gNB co-channel inter-subband CLI in LLS coverage evaluation are explicitly modelled based on a given topology of aggressor UEs and gNBs. The UE-gNB and gNB-gNB fast fading channels are explicitly modelled in LLS. The signal model is as follows + - + - is the received signal vector at the victim gNB + - is the channel matrix from target UE to gNB, is the transmitted signal of the target user + - , , are the channel matrix and transmitted signal of the UE in the same cell as the target user + - and are the channel matrix and transmitted signal of the UEs in the adjacent cell + - , and are the channel matrix, the precoding matrix, and leakage CLI signal from aggressor gNB to the victim gNB. + - The power of the signal and interference is included in the channel matrix respectively + - and are the self-interference vector of the co-site sectors and the thermal noise signal vector on the receiving antennas +- Companies are encouraged to report the topology of gNBs and UEs to derive the detailed signals and interferences above. One example is as below + +![Diagram illustrating a network topology for interference evaluation. A central green hexagon represents the 'victim' gNB, labeled with the number 7. Surrounding it are several other hexagons representing 'aggressor' gNBs. Red hexagons represent 'Interfering UE' (User Equipment) and blue hexagons represent 'Target UE'. Arrows indicate signal flow from UEs to gNBs. The diagram shows a central victim gNB (7) surrounded by aggressor gNBs (6, 5, 4, 3, 2, 1). Interfering UEs (5, 1) and Target UEs (4, 3) are shown with arrows pointing to the victim gNB. The diagram also includes labels for 'aggressor' and 'victim' gNBs, and 'Interfering UE' and 'Target UE'.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +Diagram illustrating a network topology for interference evaluation. A central green hexagon represents the 'victim' gNB, labeled with the number 7. Surrounding it are several other hexagons representing 'aggressor' gNBs. Red hexagons represent 'Interfering UE' (User Equipment) and blue hexagons represent 'Target UE'. Arrows indicate signal flow from UEs to gNBs. The diagram shows a central victim gNB (7) surrounded by aggressor gNBs (6, 5, 4, 3, 2, 1). Interfering UEs (5, 1) and Target UEs (4, 3) are shown with arrows pointing to the victim gNB. The diagram also includes labels for 'aggressor' and 'victim' gNBs, and 'Interfering UE' and 'Target UE'. + +- Based on the above modelling, the following high-level evaluation method can be used as an example for coverage performance evaluation: + +- Step 1: For legacy TDD system, perform LLS to get the required SNR ( $\gamma$ ) with which UE can achieve a certain bit rate in UL +- Step 2: For SBFD system with frame structure XXXXU, perform LLS to get the required SNR ( $\gamma$ ) with which UE can achieve a certain bit rate in UL for a given SBFD coverage enhancement scheme (e.g., SBFD with PUSCH repetition type A, etc.) +- Step 3: Use Link budget template to obtain MPL, MCL and MIL for legacy TDD and SBFD. + - For legacy TDD, the required SNR ( $\gamma$ ) obtained in Step 1 is used to calculate MPL, MCL, MIL. + - For SBFD, the required SNR ( $\gamma$ ) obtained in Step 2 is used to calculate MPL, MCL, MIL. + +For the two options above, self-interference can be modelled as additive white gaussian noise with fixed INR = - 6 dB targeting 1 dB desense similar to SLS, and co-site inter-sector interference can be modelled as additive white gaussian noise with fixed INR = - X dB based on assumption of co-site isolation . + +The link level simulation assumptions for coverage evaluation are provided in Annex D.1. The link budget template for coverage evaluation is provided in Annex D.2. + +## 7.3 Performance evaluation results for semi-static SBFD + +### 7.3.1 System level simulation results + +The detailed evaluation assumptions and results for all sub-cases for semi-static SBFD is provided in Annex B.2. + +For summary of the observations in this section, the following rule is adopted + +- For each-sub-case, 4 median values of all evaluation results for each traffic load are derived + - For mean DL average-UPT gain, a median value (X\_mean\_DL) is derived + - For 5% DL average-UPT gain, a median value (X\_5%\_DL) is derived + - For mean UL average-UPT gain, a median value (X\_mean\_UL) is derived + - For 5% UL average-UPT gain, a median value (X\_5%\_UL) is derived + +Note 1: The gain is expressed as X%=SBFD performance/TDD performance – 1. NAN is used in case both the SBFD performance and TDD performance are equal to zero. + +Note 2: To derive a median value, NAN is ignored, i.e., median value is derived from the numbers excluding NAN. + +Note 3: The samples are sorted in ascending order, if the number of samples are odd, the median value is the middle one, and if the number of samples are even, the median value is the average value of the two values in the middle part. + +Note 4: The median values of semi-static SBFD evaluation results in the summary of observation in section 7.3.1 are derived including results with CLI handling schemes, while the median values of semi-static SBFD evaluation results in the conclusion in section 13.1.1.1 are derived excluding results with CLI handling schemes + +### 7.3.1.1 SBFD Deployment Case 1 (FR1) + +#### 7.3.1.1.1 Indoor office (FR1) + +21 sources provided the SLS evaluation results for Indoor office (FR1) in SBFD Deployment Case 1. The evaluation results are categorized into 14 sub-cases as in Table 7.3.1.1.1-1~Table 7.3.1.1.1-2 based on the different key assumptions. Each sub-case is based on one combination of key assumptions. + +**Table 7.3.1.1.1-1: Sub-cases for indoor office (FR1) with twice area&same TxRUs in SBFD Deployment Case 1.** + +| | | | | | | | | | +|--|-----------------------------|-----------------------------|-----------------------------|-----------------------------|-----------------------------|-----------------------------|-----------------------------|-----------------------------| +| | SBFD#1_
InH_FR1_ | SBFD#1_
InH_FR1_ | SBFD#1_
InH_FR1_ | SBFD#1_
InH_FR1_ | SBFD#1_
InH_FR1_ | SBFD#1_
InH_FR1_ | SBFD#1_
InH_FR1_ | SBFD#1_
InH_FR1_ | +|--|-----------------------------|-----------------------------|-----------------------------|-----------------------------|-----------------------------|-----------------------------|-----------------------------|-----------------------------| + +| | | Sub#1 | Sub#2 | Sub#3 | Sub#4 | Sub#9 | Sub#10 | Sub#11 | Sub#12 | +|----------------------------|------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|-----------------|------------------------|-----------------|-----------------| +| SBFD slot configuration | Alt-4: {DDDSU} vs. {XXXXX} | O | O | | | | | | | +| | Alt-2: {DDDSU} vs. {XXXUX} | | | O | O | | | | | +| | Alt-1: {DDDSU} vs. {DXXXU} | | | | | O | O | | | +| | Alt-3: {DDSUU} vs. {XXXUX} | | | | | | | O | O | +| SBFD antenna configuration | Twice area&same TxRUs (Option 2) | O | O | O | O | O | O | O | O | +| | Same area&same TxRUs (Option 1) | | | | | | | | | +| | Same area&half TxRUs (Option 3) | | | | | | | | | +| Packet Size | Option 1: DL: 4Kbytes, UL: 1Kbytes | O | | O | | O | | O | | +| | Option 2: DL: 0.5Mbytes, UL: 0.125Mbytes | | O | | O | | O | | O | +| Sources | | 14 sources ([16], [17], [18], [19], [39], [24], [25], [26], [27], [28], [29], [31], [32], [33]) | 16 sources ([16], [17], [18], [19], [39], [23], [24], [25], [26], [27], [28], [29], [45], [31], [32], [33]) | 15 sources ([16], [17], [18], [19], [20], [21], [24], [25], [26], [27], [28], [29], [31], [32], [33]) | 18 sources ([16], [17], [18], [19], [20], [21], [22], [23], [24], [25], [26], [27], [28], [29], [45], [31], [32], [33]) | 1 source ([19]) | 2 sources ([19], [31]) | 1 source ([18]) | 1 source ([18]) | + +Table 7.3.1.1.1-2: Sub-cases for indoor office (FR1) with same area&half TxRUs in SBFD Deployment Case 1. + +| | | SBFD#1_InH_FR1_Sub #5 | SBFD#1_InH_FR1_Sub #6 | SBFD#1_InH_FR1_Sub #7 | SBFD#1_InH_FR1_Sub #8 | SBFD#1_InH_FR1_Sub #13 | SBFD#1_InH_FR1_Sub #14 | +|----------------------------|------------------------------------------|-----------------------|-----------------------|-----------------------|-----------------------|------------------------|------------------------| +| SBFD slot configuration | Alt-4: {DDDSU} vs. {XXXXX} | O | O | | | | | +| | Alt-2: {DDDSU} vs. {XXXUX} | | | O | O | | | +| | Alt-1: {DDDSU} vs. {DXXXU} | | | | | | | +| | Alt-3: {DDSUU} vs. {XXXUX} | | | | | O | O | +| SBFD antenna configuration | Twice area&same TxRUs (Option 2) | | | | | | | +| | Same area&same TxRUs (Option 1) | | | | | | | +| | Same area&half TxRUs (Option 3) | O | O | O | O | O | O | +| Packet Size | Option 1: DL: 4Kbytes, UL: 1Kbytes | O | | O | | O | | +| | Option 2: DL: 0.5Mbytes, UL: 0.125Mbytes | | O | | O | | O | +| Sources | | 1 source ([18]) | 1 source ([18]) | 1 source ([18]) | 1 source ([18]) | 1 source ([18]) | 1 source ([18]) | + +#### 7.3.1.1.1.1 Summary of the observations + +For Indoor office (FR1) in SBFD deployment case 1, assuming SBFD antenna configuration option-2 (twice area and same TxRUs): + +- In case of using SBFD Alt 4 and large packet size, (SBFD#1\_InH\_FR1\_Sub#2, 16 sources) + +- Semi-static SBFD provides mean and 5% DL Average-UPT gain of {1.86%, 1.73%} at low load level, mean DL Average-UPT gain of 2.21% and 5% DL Average-UPT loss of -1.19% at medium load level, mean and 5% DL Average-UPT gain of {2.73%, 0.54%} at high load level. +- Semi-static SBFD provides mean and 5% UL Average-UPT gain of {10.78%, 14.13%} at low load level, mean and 5% UL Average-UPT gain of {13.38%, 19.91%} at medium load level, mean and 5% UL Average-UPT gain of {13.75%, 17.70%} at high load level. +- All results assumed 24dBm BS transmission power. +- With piecewise noise figure model assumed by 6 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {2.23%, 2.67%} at low load level, mean DL Average-UPT gain of 3.23% and 5% DL Average-UPT loss of -1.19% at medium load level, mean and 5% DL Average-UPT gain of {4.04%, 2.33%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {7.83%, 7.44%} at low load level, mean and 5% UL Average-UPT gain of {7.56%, 5.57%} at medium load level, mean and 5% UL Average-UPT gain of {7.03%, 2.93%} at high load level. +- With flat noise figure model assumed by 10 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {1.29%, 1.55%} at low load level, mean and 5% DL Average-UPT gain of {1.40%, 0.68%} at medium load level, mean and 5% DL Average-UPT loss of {-1.38%, -3.27%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {14.37%, 23.18%} at low load level, mean and 5% UL Average-UPT gain of {16.54%, 30.18%} at medium load level, mean and 5% UL Average-UPT gain of {14.78%, 28.75%} at high load level. +- In case of using SBFD Alt 4 and small packet size, (SBFD#1\_InH\_FR1\_Sub#1, 15 sources) + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {9.56%, 10.50%} at low load level, mean and 5% DL Average-UPT gain of {9.35%, 12.71%} at medium load level, mean and 5% DL Average-UPT gain of {8.58%, 8.79%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {101.83%, 107.58%} at low load level, mean and 5% UL Average-UPT gain of {97.42%, 105.44%} at medium load level, mean and 5% UL Average-UPT gain of {93.85%, 106.52%} at high load level. + - All results assumed 24dBm BS transmission power. + - With piecewise noise figure model assumed by 6 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {7.85%, 6.96%} at low load level, mean and 5% DL Average-UPT gain of {8.45%, 10.07%} at medium load level, mean and 5% DL Average-UPT gain of {7.22%, 4.58%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {90.83%, 88.23%} at low load level, mean and 5% UL Average-UPT gain of {85.42%, 78.21%} at medium load level, mean and 5% UL Average-UPT gain of {92.42%, 77.63%} at high load level. + - With flat noise figure model assumed by 8 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {11.73%, 14.94%} at low load level, mean and 5% DL Average-UPT gain of {9.96%, 13.96%} at medium load level, mean and 5% DL Average-UPT gain of {10.01%, 9.45%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {102.15%, 116.42%} at low load level, mean and 5% UL Average-UPT gain of {106.09%, 113.81%} at medium load level, mean and 5% UL Average-UPT gain of {96.00%, 112.13%} at high load level. +- In case of using SBFD Alt 2 and large packet size, (SBFD#1\_InH\_FR1\_Sub#4, 18 sources) + +- Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-20.38%, -22.88%} at low load level, mean and 5% DL Average-UPT loss of {-26.30%, -29.57%} at medium load level, mean and 5% DL Average-UPT loss of {-33.95%, -53.83%} at high load level. +- Semi-static SBFD provides mean and 5% UL Average-UPT gain of {78.53%, 81.03%} at low load level, mean and 5% UL Average-UPT gain of {93.92%, 106.39%} at medium load level, mean and 5% UL Average-UPT gain of {113.75%, 150.17%} at high load level. +- All results assumed 24dBm BS transmission power. +- With piecewise noise figure model assumed by 7 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-21.90%, -25.03%} at low load level, mean and 5% DL Average-UPT loss of {-27.62%, -32.51%} at medium load level, mean and 5% DL Average-UPT loss of {-36.28%, -62.34%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {79.44%, 87.12%} at low load level, mean and 5% UL Average-UPT gain of {100.49%, 119.09%} at medium load level, mean and 5% UL Average-UPT gain of {112.40%, 164.39%} at high load level. +- With flat noise figure model assumed by 11 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-19.59%, -22.62%} at low load level, mean and 5% DL Average-UPT loss of {-26.02%, -26.62%} at medium load level, mean and 5% DL Average-UPT loss of {-31.68%, -51.19%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {77.61%, 78.58%} at low load level, mean and 5% UL Average-UPT gain of {92.49%, 102.96%} at medium load level, mean and 5% UL Average-UPT gain of {115.09%, 142.11%} at high load level. +- In case of using SBFD Alt 2 and small packet size, (SBFD#1\_InH\_FR1\_Sub#3, 15 sources) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.52%, -0.35%} at low load level, mean and 5% DL Average-UPT loss of {-1.19%, -1.66%} at medium load level, mean and 5% DL Average-UPT loss of {-6.26%, -17.59%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {99.50%, 116.24%} at low load level, mean and 5% UL Average-UPT gain of {98.83%, 110.00%} at medium load level, mean and 5% UL Average-UPT gain of {104.00%, 127.81%} at high load level. + - All results assumed 24dBm BS transmission power. + - With piecewise noise figure model assumed by 6 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.01%, -0.49%} at low load level, mean and 5% DL Average-UPT loss of {-1.36%, -2.19%} at medium load level, mean and 5% DL Average-UPT loss of {-7.54%, -32.09%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {88.28%, 88.47%} at low load level, mean and 5% UL Average-UPT gain of {89.15%, 83.93%} at medium load level, mean and 5% UL Average-UPT gain of {96.75%, 110.59%} at high load level. + - With flat noise figure model assumed by 9 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.55%, -0.12%} at low load level, mean and 5% DL Average-UPT loss of {-0.71%, -0.86%} at medium load level, mean and 5% DL Average-UPT loss of {-4.20%, -14.29%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {107.99%, 116.73%} at low load level, mean and 5% UL Average-UPT gain of {108.38%, 119.09%} at medium load level, mean and 5% UL Average-UPT gain of {108.64%, 150.39%} at high load level. +- In case of using SBFD Alt 1 and large packet size, (SBFD#1\_InH\_FR1\_Sub#10, 2 sources) + +- Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-16.56%, -23.77%} at low load level, mean and 5% DL Average-UPT loss of {-16.83%, -12.87%} at medium load level, mean and 5% DL Average-UPT loss of {-23.81%, -33.56%} at high load level. +- Semi-static SBFD provides mean and 5% UL Average-UPT gain of {62.76%, 63.09%} at low load level, mean and 5% UL Average-UPT gain of {83.94%, 104.76%} at medium load level, mean and 5% UL Average-UPT gain of {121.26%, 158.32%} at high load level. +- All results assumed 24dBm BS transmission power. +- All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 1 and small packet size, (SBFD#1\_InH\_FR1\_Sub#9, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.56%, -0.38%} at low load level, mean and 5% DL Average-UPT loss of {-0.56%, -1.81%} at medium load level, mean and 5% DL Average-UPT loss of {-3.12%, -16.65%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {73.07%, 74.00%} at low load level, mean and 5% UL Average-UPT gain of {69.25%, 68.49%} at medium load level, mean and 5% UL Average-UPT gain of {64.83%, 57.21%} at high load level. + - All results assumed 24dBm BS transmission power. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 3 and large packet size, (SBFD#1\_InH\_FR1\_Sub#12, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-2.08%, -3.08%} at low load level, mean and 5% DL Average-UPT loss of {-6.95%, -11.09%} at medium load level, mean and 5% DL Average-UPT loss of {-23.62%, -42.40%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {14.64%, 10.72%} at low load level, mean and 5% UL Average-UPT gain of {11.40%, 9.45%} at medium load level, mean UL Average-UPT gain of 5.42% and 5% UL Average-UPT loss of -22.57% at high load level. + - All results assumed 24dBm BS transmission power. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 3 and small packet size, (SBFD#1\_InH\_FR1\_Sub#11, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {9.33%, 11.11%} at low load level, mean and 5% DL Average-UPT gain of {7.83%, 4.08%} at medium load level, mean DL Average-UPT gain of 3.96% and 5% DL Average-UPT loss of -31.24% at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {77.95%, 79.21%} at low load level, mean and 5% UL Average-UPT gain of {62.90%, 46.41%} at medium load level, mean and 5% UL Average-UPT gain of {58.34%, 10.03%} at high load level. + - All results assumed 24dBm BS transmission power. + - All results assumed piecewise linear noise figure model. + +**For Indoor office (FR1) in SBFD deployment case 1, assuming SBFD antenna configuration option-3 (same area and half TxRUs):** + +- In case of using SBFD Alt 4 and large packet size, (SBFD#1\_InH\_FR1\_Sub#6, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-6.26%, -10.28%} at low load level, mean and 5% DL Average-UPT loss of {-31.34%, -47.92%} at medium load level, mean and 5% DL Average-UPT loss of {-65.01%, -83.91%} at high load level. + +- Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-0.02%, -7.06%} at low load level, mean and 5% UL Average-UPT loss of {-27.02%, -46.02%} at medium load level, mean and 5% UL Average-UPT loss of {-56.41%, -70.49%} at high load level. +- All results assumed 24dBm BS transmission power. +- All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 4 and small packet size, (SBFD#1\_InH\_FR1\_Sub#5, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {5.06%, 5.85%} at low load level, mean and 5% DL Average-UPT gain of {3.77%, 2.66%} at medium load level, mean and 5% DL Average-UPT loss of {-14.55%, -88.16%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {106.99%, 109.86%} at low load level, mean and 5% UL Average-UPT gain of {98.38%, 79.28%} at medium load level, mean UL Average-UPT gain of 53.93% and 5% UL Average-UPT loss of -69.72% at high load level. + - All results assumed 24dBm BS transmission power. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 2 and large packet size, (SBFD#1\_InH\_FR1\_Sub#8, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-27.35%, -33.40%} at low load level, mean and 5% DL Average-UPT loss of {-66.13%, -85.90%} at medium load level, mean and 5% DL Average-UPT loss of {-83.45%, -91.21%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {75.14%, 73.46%} at low load level, mean and 5% UL Average-UPT gain of {91.91%, 111.93%} at medium load level, mean and 5% UL Average-UPT gain of {141.73%, 473.00%} at high load level. + - All results assumed 24dBm BS transmission power. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 2 and small packet size, (SBFD#1\_InH\_FR1\_Sub#7, one source) + - Semi-static SBFD provides mean DL Average-UPT gain of 0.12% and 5% DL Average-UPT loss of -0.22% at low load level, mean and 5% DL Average-UPT loss of {-8.88%, -35.28%} at medium load level, mean and 5% DL Average-UPT loss of {-34.51%, -98.98%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {99.34%, 101.26%} at low load level, mean and 5% UL Average-UPT gain of {96.82%, 91.88%} at medium load level, mean and 5% UL Average-UPT gain of {96.58%, 118.43%} at high load level. + - All results assumed 24dBm BS transmission power. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 3 and large packet size, (SBFD#1\_InH\_FR1\_Sub#14, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-7.13%, -10.61%} at low load level, mean and 5% DL Average-UPT loss of {-37.85%, -56.81%} at medium load level, mean and 5% DL Average-UPT loss of {-72.59%, -86.25%} at high load level. + - Semi-static SBFD provides mean UL Average-UPT gain of 4.35% and 5% UL Average-UPT loss of -1.99% at low load level, mean and 5% UL Average-UPT loss of {-21.11%, -40.38%} at medium load level, mean and 5% UL Average-UPT loss of {-58.69%, -80.22%} at high load level. + - All results assumed 24dBm BS transmission power. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 3 and small packet size, (SBFD#1\_InH\_FR1\_Sub#13, one source) + +- Semi-static SBFD provides mean and 5% DL Average-UPT gain of {9.29%, 11.82%} at low load level, mean and 5% DL Average-UPT loss of {-4.91%, -50.44%} at medium load level, mean and 5% DL Average-UPT loss of {-17.52%, -96.07%} at high load level. +- Semi-static SBFD provides mean and 5% UL Average-UPT gain of {77.87%, 79.14%} at low load level, mean UL Average-UPT gain of 38.01% and 5% UL Average-UPT loss of -75.99% at medium load level, mean UL Average-UPT gain of 30.35% and 5% UL Average-UPT loss of -90.42% at high load level. +- All results assumed 24dBm BS transmission power. +- All results assumed piecewise linear noise figure model. + +### 7.3.1.1.2 Urban Macro (FR1) + +21 sources provided the SLS evaluation results for Urban Macro (FR1) in SBFD Deployment Case 1. The evaluation results are categorized into 24 sub-cases as in Table 7.3.1.1.2-1~Table 7.3.1.1.2-6 based on the different key assumptions. Each sub-case is based on one combination of key assumptions. + +**Table 7.3.1.1.2-1: Sub-cases for urban macro (FR1) with no less than 93dB inter-sector isolation and Twice area&same TxRUs in SBFD deployment Case 1.** + +| | | SBFD#1_U
MA_FR1_S
ub#1 | SBFD#1_U
MA_FR1_S
ub#2 | SBFD#1_U
MA_FR1_S
ub#3 | SBFD#1_U
MA_FR1_S
ub#4 | SBFD#1_U
MA_FR1_S
ub#20 | SBFD#1_U
MA_FR1_S
ub#21 | +|------------------------------------------------------------|------------------------------------------------|----------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|------------------------------------|-------------------------------| +| Co-site:
Spatial
isolation +
digital
isolation | Opt 1:>=93dB | O | O | O | O | O | O | +| | Opt 2: < 93dB | | | | | | | +| | Opt 3: 93dB | | | | | | | +| SBFD
slot
config
uration | Alt-4: {DDDSU}
vs. {XXXXX} | O | O | | | | | +| | Alt-2: {DDDSU}
vs. {XXXXU} | | | O | O | | | +| | Alt-1: {DDDSU}
vs. {DXXXU} | | | | | O | | +| | Alt-3: {DDSUU}
vs. {XXXXU} | | | | | | O | +| SBFD
antenn
a
config
uration | Twice
area&same
TxRUs (Option
2) | O | O | O | O | O | O | +| | Same
area&same
TxRUs (Option
1) | | | | | | | +| | Same area&half
TxRUs (Option
3) | | | | | | | +| Packet
Size | Option 1: DL:
4Kbytes, UL:
1Kbytes | O | | O | | | | +| | Option 2: DL:
0.5Mbytes, UL:
0.125Mbytes | | O | | O | O | O | +| Sources | | 11 sources
([16], [17],
[38], [24], [37],
[26], [28], [29],
[31], [32],
[33]) | 13 sources
([16], [17],
[18], [38], [19],
[24], [26], [27],
[28], [29], [30],
[31], [33]) | 11 sources
([16], [17],
[38], [21], [37],
[26], [28], [29],
[31], [32],
[33]) | 16 sources
([16], [17],
[36], [18], [38],
[19], [20], [21],
[24], [26], [27],
[28], [29], [30],
[31], [33]) | 3 sources
([19], [31],
[22]) | 1 source
([18]) | + +**Table 7.3.1.1.2-2: Sub-cases for urban macro (FR1) with less than 93dB inter-sector isolation and Twice area&same TxRUs in SBFD deployment Case 1.** + +| | | SBFD#1_UMA_F
R1_Sub#5 | SBFD#1_UMA_F
R1_Sub#6 | SBFD#1_UMA_F
R1_Sub#7 | SBFD#1_UMA_F
R1_Sub#8 | +|------------------------------------------------------------|---------------------------------------------|---------------------------------|---------------------------------|---------------------------|---------------------------------------| +| Co-site:
Spatial
isolation +
digital
isolation | Opt 1: >=93dB | | | | | +| | Opt 2: < 93dB | O | O | O | O | +| | Opt 3: 93dB | | | | | +| SBFD slot
configurati
on | Alt-4: {DDDSU} vs.
{XXXXX} | O | O | | | +| | Alt-2: {DDDSU} vs.
{XXXXU} | | | O | O | +| | Alt-1: {DDDSU} vs.
{DXXXU} | | | | | +| | Alt-3: {DDSUU} vs.
{XXXXU} | | | | | +| SBFD
antenna
configurati
on | Twice area&same
TxRUs (Option 2) | O | O | O | O | +| | Same area&same TxRUs
(Option 1) | | | | | +| | Same area&half TxRUs
(Option 3) | | | | | +| Packet
Size | Option 1: DL: 4Kbytes,
UL: 1Kbytes | O | | O | | +| | Option 2: DL: 0.5Mbytes,
UL: 0.125Mbytes | | O | | O | +| Sources | | 3 sources ([39],
[24], [26]) | 3 sources ([39],
[24], [26]) | 2 sources ([21],
[26]) | 4 sources ([20],
[21], [24], [26]) | + +**Table 7.3.1.1.2-3: Sub-cases for urban macro (FR1) with 93dB inter-sector isolation and Twice area&same TxRUs in SBFD deployment Case 1.** + +| | | SBFD#1_UMA_F
R1_Sub#9 | SBFD#1_UMA_F
R1_Sub#10 | SBFD#1_UMA_F
R1_Sub#11 | SBFD#1_UMA_F
R1_Sub#12 | +|------------------------------------------------------------|---------------------------------------------|---------------------------------|---------------------------------------|---------------------------------|------------------------------------------------------| +| Co-site:
Spatial
isolation +
digital
isolation | Opt 1: >=93dB | | | | | +| | Opt 2: < 93dB | | | | | +| | Opt 3: 93dB | O | O | O | O | +| SBFD slot
configurat
ion | Alt-4: {DDDSU} vs.
{XXXXX} | O | O | | | +| | Alt-2: {DDDSU} vs.
{XXXXU} | | | O | O | +| | Alt-1: {DDDSU} vs.
{DXXXU} | | | | | +| | Alt-3: {DDSUU} vs.
{XXXXU} | | | | | +| SBFD
antenna
configurat
ion | Twice area&same TxRUs
(Option 2) | O | O | O | O | +| | Same area&same TxRUs
(Option 1) | | | | | +| | Same area&half TxRUs
(Option 3) | | | | | +| Packet
Size | Option 1: DL: 4Kbytes,
UL: 1Kbytes | O | | O | | +| | Option 2: DL: 0.5Mbytes,
UL: 0.125Mbytes | | O | | O | +| Sources | | 3 sources ([24],
[28], [29]) | 4 sources ([18],
[24], [28], [29]) | 3 sources ([21],
[28], [29]) | 6 sources ([18],
[20], [21], [24], [28],
[29]) | + +**Table 7.3.1.1.2-4: Sub-cases for urban macro (FR1) with no less than 93dB inter-sector isolation and Same area&same TxRUs in SBFD deployment Case 1.** + +| | | SBFD#1_UMA_F
R1_Sub#13 | SBFD#1_UMA_F
R1_Sub#14 | SBFD#1_UMA_F
R1_Sub#17 | SBFD#1_UMA_F
R1_Sub#18 | +|----------|---------------|---------------------------|---------------------------|---------------------------|---------------------------| +| Co-site: | Opt 1: >=93dB | O | O | O | O | + +| | | | | | | +|---------------------------------------|------------------------------------------|-----------------|-----------------|-----------------|-----------------| +| Spatial isolation + digital isolation | Opt 2: < 93dB | | | | | +| | Opt 3: 93dB | | | | | +| SBFD slot configuration | Alt-4: {DDDSU} vs. {XXXXX} | O | O | | | +| | Alt-2: {DDDSU} vs. {XXXU} | | | O | O | +| | Alt-1: {DDDSU} vs. {DXXXU} | | | | | +| | Alt-3: {DDSUU} vs. {XXXU} | | | | | +| SBFD antenna configuration | Twice area&same TxRUs (Option 2) | | | | | +| | Same area&same TxRUs (Option 1) | O | O | O | O | +| | Same area&half TxRUs (Option 3) | | | | | +| Packet Size | Option 1: DL: 4Kbytes, UL: 1Kbytes | O | | O | | +| | Option 2: DL: 0.5Mbytes, UL: 0.125Mbytes | | O | | O | +| Sources | | 1 source ([28]) | 1 source ([28]) | 1 source ([28]) | 1 source ([28]) | + +Table 7.3.1.1.2-5: Sub-cases for urban macro (FR1) with no less than 93dB inter-sector isolation and Same area&half TxRUs in SBFD deployment Case 1. + +| | | SBFD#1_UMA_F R1_Sub#15 | SBFD#1_UMA_F R1_Sub#16 | SBFD#1_UMA_F R1_Sub#19 | SBFD#1_UMA_F R1_Sub#22 | +|------------------------------------------------|------------------------------------------|------------------------|------------------------|------------------------|------------------------| +| Co-site: Spatial isolation + digital isolation | Opt 1:>=93dB | O | O | O | O | +| | Opt 2: < 93dB | | | | | +| | Opt 3: 93dB | | | | | +| SBFD slot configuration | Alt-4: {DDDSU} vs. {XXXXX} | O | O | | | +| | Alt-2: {DDDSU} vs. {XXXU} | | | O | | +| | Alt-1: {DDDSU} vs. {DXXXU} | | | | | +| | Alt-3: {DDSUU} vs. {XXXU} | | | | O | +| SBFD antenna configuration | Twice area&same TxRUs (Option 2) | | | | | +| | Same area&same TxRUs (Option 1) | | | | | +| | Same area&half TxRUs (Option 3) | O | O | O | O | +| Packet Size | Option 1: DL: 4Kbytes, UL: 1Kbytes | O | | | | +| | Option 2: DL: 0.5Mbytes, UL: 0.125Mbytes | | O | O | O | +| Sources | | 1 source ([24]) | 2 sources ([18], [24]) | 1 source ([18]) | 1 source ([18]) | + +Table 7.3.1.1.2-6: Sub-cases for urban macro (FR1) with less than 93dB inter-sector isolation and Same area&half TxRUs in SBFD deployment Case 1. + +| | | SBFD#1_UMA_FR1_Sub#23 | SBFD#1_UMA_FR1_Sub#24 | +|------------------------------------------------|----------------------------------|-----------------------|-----------------------| +| Co-site: Spatial isolation + digital isolation | Opt 1:>=93dB | | | +| | Opt 2: < 93dB | O | O | +| | Opt 3: 93dB | | | +| SBFD slot configuration | Alt-4: {DDDSU} vs. {XXXXX} | O | O | +| | Alt-2: {DDDSU} vs. {XXXU} | | | +| | Alt-1: {DDDSU} vs. {DXXXU} | | | +| | Alt-3: {DDSUU} vs. {XXXU} | | | +| SBFD antenna configuration | Twice area&same TxRUs (Option 2) | | | +| | Same area&same TxRUs (Option 1) | | | + +| | | | | +|-------------|------------------------------------------|-----------------|-----------------| +| Packet Size | Same area&half TxRUs (Option 3) | O | O | +| | Option 1: DL: 4Kbytes, UL: 1Kbytes | O | | +| | Option 2: DL: 0.5Mbytes, UL: 0.125Mbytes | | O | +| Sources | | 1 source ([24]) | 1 source ([24]) | + +#### 7.3.1.1.2.1 + +#### Summary of the observations + +**For Urban Macro (FR1) in SBFD deployment case 1, if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is no less than 93 dB, assuming SBFD antenna configuration option-2 (twice area and same TxRUs):** + +- In case of using SBFD Alt 4 and large packet size, (SBFD#1\_UMA\_FR1\_Sub#2, 13 sources) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-9.30%, -21.05%} at low load level, mean and 5% DL Average-UPT loss of {-29.11%, -73.35%} at medium load level, mean and 5% DL Average-UPT loss of {-32.70%, -89.16%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {24.91%, 187.62%} at low load level, mean UL Average-UPT gain of 7.50% and 5% UL Average-UPT loss of -45.51% at medium load level, mean and 5% UL Average-UPT loss of {-1.49%, -67.13%} at high load level. +- With 49dBm BS transmission power assumed by 2 sources, + - Semi-static SBFD provides mean DL Average-UPT gain of 3.68% and 5% DL Average-UPT loss of -1.71% at low load level, mean DL Average-UPT gain of 1.34% and 5% DL Average-UPT loss of -6.96% at medium load level, mean and 5% DL Average-UPT loss of {-6.16%, -9.52%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {19.94%, 187.62%} at low load level, mean and 5% UL Average-UPT gain of {18.27%, 61.62%} at medium load level, mean and 5% UL Average-UPT gain of {3.92%, 25.42%} at high load level. +- With 53dBm BS transmission power assumed by 11 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-13.84%, -29.50%} at low load level, mean and 5% DL Average-UPT loss of {-30.61%, -83.93%} at medium load level, mean and 5% DL Average-UPT loss of {-33.20%, -99.25%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {39.19%, 177.16%} at low load level, mean UL Average-UPT gain of 2.99% and 5% UL Average-UPT loss of -63.84% at medium load level, mean and 5% UL Average-UPT loss of {-28.58%, -86.80%} at high load level. +- With piecewise noise figure model assumed by 5 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-13.84%, -36.84%} at low load level, mean and 5% DL Average-UPT loss of {-29.46%, -91.20%} at medium load level, mean and 5% DL Average-UPT loss of {-32.55%, -99.25%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {43.03%, 205.22%} at low load level, mean and 5% UL Average-UPT gain of {18.27%, 26.39%} at medium load level, mean UL Average-UPT gain of 3.92% and 5% UL Average-UPT loss of -26.89% at high load level. +- With flat noise figure model assumed by 8 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-7.08%, -9.59%} at low load level, mean and 5% DL Average-UPT loss of {-28.76%, -55.96%} at medium load level, mean and 5% DL Average-UPT loss of {-32.86%, -84.60%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {24.20%, 142.32%} at low load level, mean UL Average-UPT gain of 2.99% and 5% UL Average-UPT loss of -76.26% at medium load level, mean and 5% UL Average-UPT loss of {-6.71%, -81.94%} at high load level. +- In case of using SBFD Alt 4 and small packet size, (SBFD#1\_UMA\_FR1\_Sub#1, 11 sources) + +- Semi-static SBFD provides mean DL Average-UPT gain of 6.57% and 5% DL Average-UPT loss of -5.53% at low load level, mean and 5% DL Average-UPT loss of {-3.78%, -58.81%} at medium load level, mean and 5% DL Average-UPT loss of {-18.36%, -79.38%} at high load level. +- Semi-static SBFD provides mean and 5% UL Average-UPT gain of {82.43%, 110.52%} at low load level, mean and 5% UL Average-UPT gain of {68.52%, 68.75%} at medium load level, mean UL Average-UPT gain of 56.45% and 5% UL Average-UPT loss of -0.74% at high load level. +- With 49dBm BS transmission power assumed by 2 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {10.07%, 4.11%} at low load level, mean and 5% DL Average-UPT gain of {8.01%, 2.46%} at medium load level, mean DL Average-UPT gain of 4.67% and 5% DL Average-UPT loss of -1.56% at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {60.88%, 172.72%} at low load level, mean and 5% UL Average-UPT gain of {67.73%, 205.77%} at medium load level, mean and 5% UL Average-UPT gain of {62.22%, 90.00%} at high load level. +- With 53dBm BS transmission power assumed by 9 sources, + - Semi-static SBFD provides mean DL Average-UPT gain of 3.72% and 5% DL Average-UPT loss of -14.71% at low load level, mean and 5% DL Average-UPT loss of {-6.34%, -82.48%} at medium load level, mean and 5% DL Average-UPT loss of {-19.93%, -94.86%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {97.24%, 59.02%} at low load level, mean and 5% UL Average-UPT gain of {69.31%, 24.51%} at medium load level, mean UL Average-UPT gain of 45.04% and 5% UL Average-UPT loss of -53.96% at high load level. +- With piecewise noise figure model assumed by 4 sources, + - Semi-static SBFD provides mean DL Average-UPT gain of 1.31% and 5% DL Average-UPT loss of -27.45% at low load level, mean and 5% DL Average-UPT loss of {-6.97%, -46.00%} at medium load level, mean and 5% DL Average-UPT loss of {-17.63%, -79.38%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {56.80%, 63.10%} at low load level, mean and 5% UL Average-UPT gain of {65.28%, 122.21%} at medium load level, mean and 5% UL Average-UPT gain of {66.48%, 27.66%} at high load level. +- With flat noise figure model assumed by 7 sources, + - Semi-static SBFD provides mean DL Average-UPT gain of 6.57% and 5% DL Average-UPT loss of -5.53% at low load level, mean and 5% DL Average-UPT loss of {-3.78%, -65.89%} at medium load level, mean and 5% DL Average-UPT loss of {-18.36%, -80.66%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {124.33%, 166.36%} at low load level, mean and 5% UL Average-UPT gain of {80.29%, 61.67%} at medium load level, mean UL Average-UPT gain of 47.86% and 5% UL Average-UPT loss of -27.38% at high load level. +- In case of using SBFD Alt 2 and large packet size, (SBFD#1\_UMA\_FR1\_Sub#4, 16 sources) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-27.19%, -28.35%} at low load level, mean and 5% DL Average-UPT loss of {-35.32%, -63.90%} at medium load level, mean and 5% DL Average-UPT loss of {-47.44%, -88.60%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {76.39%, 185.78%} at low load level, mean and 5% UL Average-UPT gain of {61.29%, 84.38%} at medium load level, mean and 5% UL Average-UPT gain of {40.66%, 45.76%} at high load level. +- With 49dBm BS transmission power assumed by 3 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-24.91%, -22.63%} at low load level, mean and 5% DL Average-UPT loss of {-26.84%, -25.35%} at medium load level, mean and 5% DL Average-UPT loss of {-38.93%, -48.20%} at high load level. + +- Semi-static SBFD provides mean and 5% UL Average-UPT gain of {65.03%, 85.69%} at low load level, mean and 5% UL Average-UPT gain of {65.06%, 84.94%} at medium load level, mean and 5% UL Average-UPT gain of {84.91%, 82.87%} at high load level. +- With 53dBm BS transmission power assumed by 13 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-30.04%, -43.32%} at low load level, mean and 5% DL Average-UPT loss of {-41.24%, -78.80%} at medium load level, mean and 5% DL Average-UPT loss of {-51.79%, -96.42%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {79.58%, 201.71%} at low load level, mean and 5% UL Average-UPT gain of {50.99%, 55.93%} at medium load level, mean and 5% UL Average-UPT gain of {37.53%, 12.23%} at high load level. +- With piecewise noise figure model assumed by 6 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-30.74%, -32.84%} at low load level, mean and 5% DL Average-UPT loss of {-39.08%, -67.21%} at medium load level, mean and 5% DL Average-UPT loss of {-49.17%, -87.99%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {78.28%, 203.20%} at low load level, mean and 5% UL Average-UPT gain of {65.06%, 84.38%} at medium load level, mean and 5% UL Average-UPT gain of {69.84%, 45.76%} at high load level. +- With flat noise figure model assumed by 10 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-24.26%, -28.35%} at low load level, mean and 5% DL Average-UPT loss of {-28.92%, -63.90%} at medium load level, mean and 5% DL Average-UPT loss of {-46.90%, -88.60%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {63.70%, 91.38%} at low load level, mean and 5% UL Average-UPT gain of {50.99%, 92.70%} at medium load level, mean and 5% UL Average-UPT gain of {29.24%, 39.57%} at high load level. +- In case of using SBFD Alt 2 and small packet size, (SBFD#1\_UMA\_FR1\_Sub#3, 11 sources) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-2.97%, -10.48%} at low load level, mean and 5% DL Average-UPT loss of {-12.07%, -20.27%} at medium load level, mean and 5% DL Average-UPT loss of {-25.51%, -67.20%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {124.08%, 217.78%} at low load level, mean and 5% UL Average-UPT gain of {107.91%, 173.91%} at medium load level, mean and 5% UL Average-UPT gain of {102.27%, 198.00%} at high load level. +- With 49dBm BS transmission power assumed by 3 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.45%, -0.48%} at low load level, mean and 5% DL Average-UPT loss of {-2.92%, -7.36%} at medium load level, mean and 5% DL Average-UPT loss of {-8.00%, -14.14%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {171.01%, 284.55%} at low load level, mean and 5% UL Average-UPT gain of {191.42%, 294.35%} at medium load level, mean and 5% UL Average-UPT gain of {273.75%, 449.24%} at high load level. +- With 53dBm BS transmission power assumed by 8 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-3.06%, -21.06%} at low load level, mean and 5% DL Average-UPT loss of {-14.45%, -63.71%} at medium load level, mean and 5% DL Average-UPT loss of {-30.84%, -87.41%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {113.78%, 129.22%} at low load level, mean and 5% UL Average-UPT gain of {104.04%, 85.71%} at medium load level, mean and 5% UL Average-UPT gain of {88.93%, 105.88%} at high load level. +- With piecewise noise figure model assumed by 3 sources, + +- Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-4.92%, -6.03%} at low load level, mean and 5% DL Average-UPT loss of {-6.40%, -8.09%} at medium load level, mean and 5% DL Average-UPT loss of {-8.00%, -14.14%} at high load level. +- Semi-static SBFD provides mean and 5% UL Average-UPT gain of {163.16%, 284.55%} at low load level, mean and 5% UL Average-UPT gain of {194.80%, 294.35%} at medium load level, mean and 5% UL Average-UPT gain of {273.75%, 449.24%} at high load level. +- With flat noise figure model assumed by 8 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-2.97%, -10.48%} at low load level, mean and 5% DL Average-UPT loss of {-12.07%, -54.68%} at medium load level, mean and 5% DL Average-UPT loss of {-30.84%, -87.41%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {124.08%, 173.71%} at low load level, mean and 5% UL Average-UPT gain of {104.04%, 85.71%} at medium load level, mean and 5% UL Average-UPT gain of {82.90%, 112.75%} at high load level. +- In case of using SBFD Alt 1 and large packet size, (SBFD#1\_UMA\_FR1\_Sub#20, 3 sources) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-24.66%, -46.49%} at low load level, mean and 5% DL Average-UPT loss of {-36.48%, -75.94%} at medium load level, mean and 5% DL Average-UPT loss of { -49.92%, -89.89%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {73.08%, 126.00%} at low load level, mean and 5% UL Average-UPT gain of {53.84%, 90.91%} at medium load level, mean and 5% UL Average-UPT gain of {40.29%, 55.81%} at high load level. + - All results assumed 53dBm BS transmission power. +- With piecewise linear noise figure model assumed by 2 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-25.31%, -47.45%} at low load level, mean and 5% DL Average-UPT loss of {-37.25%, -79.50%} at medium load level, mean and 5% DL Average-UPT loss of {-49.59%, -91.49%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {73.88%, 126.00%} at low load level, mean and 5% UL Average-UPT gain of {55.03%, 90.91%} at medium load level, mean and 5% UL Average-UPT gain of {38.17%, 55.81%} at high load level. +- With flat noise figure model assumed by one source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-22.96%, -26.39%} at low load level, mean and 5% DL Average-UPT loss of {-30.55%, -33.06%} at medium load level, mean and 5% DL Average-UPT loss of {-44.26%, -52.49%} at high load level. + - Semi-static SBFD provides mean UL Average-UPT gain of 89.48% at low load level, mean UL Average-UPT gain of 83.88% at medium load level, mean UL Average-UPT gain of 62.00% at high load level. +- In case of using SBFD Alt 3 and large packet size, (SBFD#1\_UMA\_FR1\_Sub#21, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-3.04%, -4.46%} at low load level, mean and 5% DL Average-UPT loss of {-10.52%, -19.57%} at medium load level, mean and 5% DL Average-UPT loss of {-28.35%, -50.47%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {6.07%, 50.99%} at low load level, mean and 5% UL Average-UPT loss of {-22.78%, -40.82%} at medium load level, mean and 5% UL Average-UPT loss of {-53.08%, -74.52%} at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. + +**For Urban Macro (FR1) in SBFD deployment case 1, if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is less than 93 dB, assuming SBFD antenna configuration option-2 (twice area and same TxRUs):** + +- In case of using SBFD Alt 4 and large packet size, (SBFD#1\_UMA\_FR1\_Sub#6, 3 sources) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-25.06%, -75.30%} at low load level, mean and 5% DL Average-UPT loss of {-40.50%, -94.59%} at medium load level, mean and 5% DL Average-UPT loss of {-45.29%, -97.64%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-30.99%, -100.00%} at low load level, mean and 5% UL Average-UPT loss of {-74.48%, -100.00%} at medium load level, mean and 5% UL Average-UPT loss of {-86.16%, -100.00%} at high load level. + - All results assumed 53dBm BS transmission power. + - With piecewise noise figure model assumed by 2 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-23.55%, -76.41%} at low load level, mean and 5% DL Average-UPT loss of {-35.15%, -90.70%} at medium load level, mean and 5% DL Average-UPT loss of {-33.37%, -97.64%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-40.23%, -100.00%} at low load level, mean and 5% UL Average-UPT loss of {-90.54%, -100.00%} at medium load level, mean and 5% UL Average-UPT loss of {-99.79%, -100.00%} at high load level. + - With flat noise figure model assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-26.58%, -54.99%} at low load level, mean and 5% DL Average-UPT loss of {-45.86%, -99.90%} at medium load level, mean and 5% DL Average-UPT loss of {-57.21%, -100.00%} at high load level. + - Semi-static SBFD provides mean UL Average-UPT loss of -21.76% at low load level, mean UL Average-UPT loss of -58.42% at medium load level, mean UL Average-UPT loss of -72.53% at high load level. +- In case of using SBFD Alt 4 and small packet size, (SBFD#1\_UMA\_FR1\_Sub#5, 3 sources)) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-14.55%, -78.16%} at low load level, mean and 5% DL Average-UPT loss of {-15.11%, -98.06%} at medium load level, mean and 5% DL Average-UPT loss of {-20.87%, -99.62%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-6.50%, -98.32%} at low load level, mean and 5% UL Average-UPT loss of {-27.59%, -100.00%} at medium load level, mean and 5% UL Average-UPT loss of {-43.73%, -100.00%} at high load level. + - All results assumed 53dBm BS transmission power. + - With piecewise noise figure model assumed by 2 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-14.70%, -78.31%} at low load level, mean and 5% DL Average-UPT loss of {-15.15%, -98.17%} at medium load level, mean and 5% DL Average-UPT loss of {-16.41%, -99.62%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-97.20%, -100.00%} at low load level, mean and 5% UL Average-UPT loss of {-99.99%, -100.00%} at medium load level, mean and 5% UL Average-UPT loss of {-100.00%, -100.00%} at high load level. + - With flat noise figure model assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-2.22%, -66.20%} at low load level, mean and 5% DL Average-UPT loss of {-10.77%, -97.58%} at medium load level, mean and 5% DL Average-UPT loss of {-25.33%, -99.96%} at high load level. + - Semi-static SBFD provides mean UL Average-UPT gain of 84.20% and 5% UL Average-UPT loss of -96.64% at low load level, mean UL Average-UPT gain of 44.81% and 5% UL Average-UPT loss of + +-100.00% at medium load level, mean UL Average-UPT gain of 12.55% and 5% UL Average-UPT loss of -100.00% at high load level. + +- In case of using SBFD Alt 2 and large packet size, (SBFD#1\_UMA\_FR1\_Sub#8, 4 sources) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-32.72%, -73.00%} at low load level, mean and 5% DL Average-UPT loss of {-50.26%, -96.20%} at medium load level, mean and 5% DL Average-UPT loss of {-52.78%, -99.73%} at high load level. + - Semi-static SBFD provides mean UL Average-UPT gain of 1.27% and 5% UL Average-UPT loss of -31.07% at low load level, mean and 5% UL Average-UPT loss of {-37.96%, -26.68%} at medium load level, mean UL Average-UPT loss of -35.17% and 5% UL Average-UPT gain of 14.21% at high load level. + - With 49dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-25.89%, -23.78%} at low load level, mean and 5% DL Average-UPT loss of {-26.81%, -27.63%} at medium load level, mean and 5% DL Average-UPT loss of {-44.31%, -68.80%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {61.34%, 74.19%} at low load level, mean and 5% UL Average-UPT gain of {62.78%, 80.04%} at medium load level, mean and 5% UL Average-UPT gain of {85.69%, 106.93%} at high load level. + - With 53dBm BS transmission power assumed by 3 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-36.30%, -78.08%} at low load level, mean and 5% DL Average-UPT loss of {-50.30%, -96.31%} at medium load level, mean and 5% DL Average-UPT loss of {-52.80%, -99.73%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-11.46%, -37.51%} at low load level, mean and 5% UL Average-UPT loss of {-41.90%, -48.04%} at medium load level, mean and 5% UL Average-UPT loss of {-35.31%, -57.83%} at high load level. + - With piecewise noise figure model assumed by 2 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-39.88%, -83.15%} at low load level, mean and 5% DL Average-UPT loss of {-50.26%, -96.20%} at medium load level, mean and 5% DL Average-UPT loss of {-52.78%, -99.73%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-24.20%, -37.51%} at low load level, mean and 5% UL Average-UPT loss of {-45.84%, -48.04%} at medium load level, mean and 5% UL Average-UPT loss of {-35.17%, -57.83%} at high load level. + - With flat noise figure model assumed by 2 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-24.18%, -65.10%} at low load level, mean and 5% DL Average-UPT loss of {-41.07%, -95.57%} at medium load level, mean and 5% DL Average-UPT loss of {-55.20%, -97.15%} at high load level. + - Semi-static SBFD provides mean UL Average-UPT gain of 8.33% and 5% UL Average-UPT loss of -24.64% at low load level, mean and 5% UL Average-UPT loss of {-29.27%, -5.32%} at medium load level, mean UL Average-UPT loss of -27.64% and 5% UL Average-UPT gain of 86.25% at high load level. +- In case of using SBFD Alt 2 and small packet size, (SBFD#1\_UMA\_FR1\_Sub#7, 2 sources) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-4.92%, -31.96%} at low load level, mean and 5% DL Average-UPT loss of {-8.73%, -49.07%} at medium load level, mean and 5% DL Average-UPT loss of {-16.36%, -51.65%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {150.16%, 97.81%} at low load level, mean and 5% UL Average-UPT gain of {150.17%, 109.19%} at medium load level, mean and 5% UL Average-UPT gain of {225.08%, 261.07%} at high load level. + - With 49dBm BS transmission power assumed by 1 source, + +- Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.16%, -0.30%} at low load level, mean and 5% DL Average-UPT gain of {0.01%, 0.07%} at medium load level, mean and 5% DL Average-UPT loss of {-0.20%, -3.34%} at high load level. +- Semi-static SBFD provides mean and 5% UL Average-UPT gain of {213.37%, 288.43%} at low load level, mean and 5% UL Average-UPT gain of {250.61%, 318.39%} at medium load level, mean and 5% UL Average-UPT gain of {421.95%, 622.15%} at high load level. +- With 53dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-9.69%, -63.62%} at low load level, mean and 5% DL Average-UPT loss of {-17.48%, -98.20%} at medium load level, mean and 5% DL Average-UPT loss of {-32.51%, -99.96%} at high load level. + - Semi-static SBFD provides mean UL Average-UPT gain of 86.94% and 5% UL Average-UPT loss of -92.81% at low load level, mean UL Average-UPT gain of 49.72% and 5% UL Average-UPT loss of -100.00% at medium load level, mean UL Average-UPT gain of 28.21% and 5% UL Average-UPT loss of -100.00% at high load level. +- With piecewise noise figure model assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.16%, -0.30%} at low load level, mean and 5% DL Average-UPT gain of {0.01%, 0.07%} at medium load level, mean and 5% DL Average-UPT loss of {-0.20%, -3.34%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {213.37%, 288.43%} at low load level, mean and 5% UL Average-UPT gain of {250.61%, 318.39%} at medium load level, mean and 5% UL Average-UPT gain of {421.95%, 622.15%} at high load level. +- With flat noise figure model assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-9.69%, -63.62%} at low load level, mean and 5% DL Average-UPT loss of {-17.48%, -98.20%} at medium load level, mean and 5% DL Average-UPT loss of {-32.51%, -99.96%} at high load level. + - Semi-static SBFD provides mean UL Average-UPT gain of 86.94% and 5% UL Average-UPT loss of -92.81% at low load level, mean UL Average-UPT gain of 49.72% and 5% UL Average-UPT loss of -100.00% at medium load level, mean UL Average-UPT gain of 28.21% and 5% UL Average-UPT loss of -100.00% at high load level. + +**For Urban Macro (FR1) in SBFD deployment case 1, if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is equal to 93 dB, assuming SBFD antenna configuration option-2 (twice area and same TxRUs):** + +- In case of using SBFD Alt 4 and large packet size, (SBFD#1\_UMA\_FR1\_Sub#10, 4 sources) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-8.47%, -4.26%} at low load level, mean and 5% DL Average-UPT loss of {-34.75%, -88.67%} at medium load level, mean and 5% DL Average-UPT loss of {-32.86%, -84.60%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {8.54%, 187.62%} at low load level, mean and 5% UL Average-UPT loss of {-23.92%, -45.51%} at medium load level, mean and 5% UL Average-UPT loss of {-78.23%, -69.03%} at high load level. +- With 49dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean DL Average-UPT gain of 3.68% and 5% DL Average-UPT loss of -1.71% at low load level, mean DL Average-UPT gain of 1.34% and 5% DL Average-UPT loss of -6.96% at medium load level, mean and 5% DL Average-UPT loss of {-6.16%, -9.52%} at high load level. + +- Semi-static SBFD provides mean and 5% UL Average-UPT gain of {19.94%, 187.62%} at low load level, mean and 5% UL Average-UPT gain of {18.27%, 61.62%} at medium load level, mean and 5% UL Average-UPT gain of {3.92%, 15.25%} at high load level. +- With 53dBm BS transmission power assumed by 3 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-12.98%, -36.25%} at low load level, mean and 5% DL Average-UPT loss of {-35.25%, -89.94%} at medium load level, mean and 5% DL Average-UPT loss of {-35.43%, -91.92%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {6.79%, 178.37%} at low load level, mean and 5% UL Average-UPT loss of {-33.17%, -56.47%} at medium load level, mean and 5% UL Average-UPT loss of {-80.07%, -77.91%} at high load level. +- With piecewise noise figure model assumed by 3 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-9.91%, -34.97%} at low load level, mean and 5% DL Average-UPT loss of {-22.08%, -56.71%} at medium load level, mean and 5% DL Average-UPT loss of {-28.96%, -72.54%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {12.95%, 205.22%} at low load level, mean and 5% UL Average-UPT loss of {-33.17%, -27.17%} at medium load level, mean and 5% UL Average-UPT loss of {-80.07%, -77.91%} at high load level. +- With flat noise figure model assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-8.47%, -4.26%} at low load level, mean and 5% DL Average-UPT loss of {-35.75%, -88.67%} at medium load level, mean and 5% DL Average-UPT loss of {-32.86%, -84.60%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-2.10%, -3.71%} at low load level, mean and 5% UL Average-UPT loss of {-21.83%, -76.26%} at medium load level, mean and 5% UL Average-UPT loss of {-6.71%, -65.23%} at high load level. +- In case of using SBFD Alt 4 and small packet size, (SBFD#1\_UMA\_FR1\_Sub#9, 3 sources) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-2.59%, -37.98%} at low load level, mean and 5% DL Average-UPT loss of {-6.88%, -48.89%} at medium load level, mean and 5% DL Average-UPT loss of {-17.55%, -78.27%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {34.65%, 18.12%} at low load level, mean UL Average-UPT gain of 18.85% and 5% UL Average-UPT loss of -13.03% at medium load level, mean and 5% UL Average-UPT loss of {-1.33%, -38.49%} at high load level. +- With 49dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {10.07%, 4.11%} at low load level, mean and 5% DL Average-UPT gain of {8.01%, 2.46%} at medium load level, mean DL Average-UPT gain of 4.67% and 5% DL Average-UPT loss of -1.56% at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {52.72%, 153.85%} at low load level, mean and 5% UL Average-UPT gain of {62.84%, 205.77%} at medium load level, mean and 5% UL Average-UPT gain of {62.22%, 56.00%} at high load level. +- With 53dBm BS transmission power assumed by 2 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-13.66%, -80.08%} at low load level, mean and 5% DL Average-UPT loss of {-21.04%, -99.71%} at medium load level, mean and 5% DL Average-UPT loss of {-26.19%, -99.82%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {16.58%, 12.69%} at low load level, mean and 5% UL Average-UPT loss of {-25.15%, -50.57%} at medium load level, mean and 5% UL Average-UPT loss of {-64.88%, -76.18%} at high load level. +- With piecewise noise figure model assumed by 2 sources, + +- Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-13.66%, -80.08%} at low load level, mean and 5% DL Average-UPT loss of {-21.04%, -99.71%} at medium load level, mean and 5% DL Average-UPT loss of {-26.19%, -99.82%} at high load level. +- Semi-static SBFD provides mean and 5% UL Average-UPT gain of {16.58%, 23.55%} at low load level, mean and 5% UL Average-UPT loss of {-25.15%, -50.57%} at medium load level, mean and 5% UL Average-UPT loss of {-64.88%, -76.18%} at high load level. +- With flat noise figure model assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {8.48%, 9.73%} at low load level, mean and 5% DL Average-UPT gain of {7.29%, 1.93%} at medium load level, mean and 5% DL Average-UPT loss of {-8.90%, -56.71%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {58.09%, 12.69%} at low load level, mean and 5% UL Average-UPT gain of {69.31%, 24.51%} at medium load level, mean UL Average-UPT gain of 73.84% and 5% UL Average-UPT loss of -0.80% at high load level. +- In case of using SBFD Alt 2 and large packet size, (SBFD#1\_UMA\_FR1\_Sub#12, 6 sources) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-25.79%, -25.50%} at low load level, mean and 5% DL Average-UPT loss of {-35.29%, -57.92%} at medium load level, mean and 5% DL Average-UPT loss of {-51.62%, -81.73%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {63.70%, 203.20%} at low load level, mean and 5% UL Average-UPT gain of {44.06%, 55.93%} at medium load level, mean and 5% UL Average-UPT gain of {40.66%, 42.37%} at high load level. +- With 49dBm BS transmission power assumed by 2 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-24.46%, -18.45%} at low load level, mean and 5% DL Average-UPT loss of {-26.06%, -22.52%} at medium load level, mean and 5% DL Average-UPT loss of {-36.64%, -46.71%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {70.44%, 168.72%} at low load level, mean and 5% UL Average-UPT gain of {82.75%, 90.72%} at medium load level, mean and 5% UL Average-UPT gain of {84.72%, 76.60%} at high load level. +- With 53dBm BS transmission power assumed by 4 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-27.81%, -65.65%} at low load level, mean and 5% DL Average-UPT loss of {-35.32%, -91.02%} at medium load level, mean and 5% DL Average-UPT loss of {-51.93%, -94.29%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {41.26%, 203.20%} at low load level, mean and 5% UL Average-UPT gain of {22.86%, 29.85%} at medium load level, mean and 5% UL Average-UPT gain of {28.83%, 12.23%} at high load level. +- With piecewise noise figure model assumed by 4 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-25.79%, -25.50%} at low load level, mean and 5% DL Average-UPT loss of {-35.32%, -48.29%} at medium load level, mean and 5% DL Average-UPT loss of {-51.62%, -69.87%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {63.92%, 224.13%} at low load level, mean and 5% UL Average-UPT gain of {44.06%, 55.93%} at medium load level, mean and 5% UL Average-UPT gain of {40.66%, 12.23%} at high load level. +- With flat noise figure model assumed by 2 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-21.71%, -48.08%} at low load level, mean and 5% DL Average-UPT loss of {-31.79%, -74.47%} at medium load level, mean and 5% DL Average-UPT loss of {-46.66%, -88.01%} at high load level. + +- Semi-static SBFD provides mean and 5% UL Average-UPT gain of {34.39%, 23.63%} at low load level, mean and 5% UL Average-UPT gain of {33.60%, 63.75%} at medium load level, mean and 5% UL Average-UPT gain of {48.45%, 104.08%} at high load level. +- In case of using SBFD Alt 2 and small packet size, (SBFD#1\_UMA\_FR1\_Sub#11, 3 sources) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.04%, -0.30%} at low load level, mean and 5% DL Average-UPT loss of {-2.62%, -5.88%} at medium load level, mean and 5% DL Average-UPT loss of {-12.55%, -23.21%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {71.55%, 273.08%} at low load level, mean and 5% UL Average-UPT gain of {89.49%, 238.46%} at medium load level, mean and 5% UL Average-UPT gain of {102.27%, 198.00%} at high load level. + - With 49dBm BS transmission power assumed by 2 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-4.85%, -7.36%} at low load level, mean and 5% DL Average-UPT loss of {-6.44%, -8.04%} at medium load level, mean and 5% DL Average-UPT loss of {-8.30%, -13.98%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {142.50%, 280.75%} at low load level, mean and 5% UL Average-UPT gain of {169.89%, 278.00%} at medium load level, mean and 5% UL Average-UPT gain of {261.95%, 410.81%} at high load level. + - With 53dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.04%, -0.14%} at low load level, mean and 5% DL Average-UPT loss of {-2.62%, -5.88%} at medium load level, mean and 5% DL Average-UPT loss of {-12.55%, -47.39%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {53.37%, 35.78%} at low load level, mean and 5% UL Average-UPT gain of {59.74%, 39.45%} at medium load level, mean and 5% UL Average-UPT gain of {82.90%, 139.75%} at high load level. + - With piecewise noise figure model assumed by 2 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-4.85%, -7.36%} at low load level, mean and 5% DL Average-UPT loss of {-6.44%, -8.04%} at medium load level, mean and 5% DL Average-UPT loss of {-8.30%, -13.98%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {142.50%, 280.75%} at low load level, mean and 5% UL Average-UPT gain of {169.89%, 278.00%} at medium load level, mean and 5% UL Average-UPT gain of {261.95%, 410.81%} at high load level. + - With flat noise figure model assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.04%, -0.14%} at low load level, mean and 5% DL Average-UPT loss of {-2.62%, -5.88%} at medium load level, mean and 5% DL Average-UPT loss of {-12.55%, -47.39%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {53.37%, 35.78%} at low load level, mean and 5% UL Average-UPT gain of {59.74%, 39.45%} at medium load level, mean and 5% UL Average-UPT gain of {82.90%, 139.75%} at high load level. + +**For Urban Macro (FR1) in SBFD deployment case 1, if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is no less than 93 dB, assuming SBFD antenna configuration option-1 (same area and same TxRUs):** + +- In case of using SBFD Alt 4 and large packet size, (SBFD#1\_UMA\_FR1\_Sub#14, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-17.12%, -32.56%} at low load level, mean and 5% DL Average-UPT loss of {-19.99%, -43.09%} at medium load level, mean and 5% DL Average-UPT loss of {-22.55%, -42.12%} at high load level. + +- Semi-static SBFD provides mean UL Average-UPT gain of 0.66% and 5% UL Average-UPT loss of -4.76% at low load level, mean UL Average-UPT loss of -0.34% and 5% UL Average-UPT gain of 11.02% at medium load level, mean and 5% UL Average-UPT loss of {-22.78%, -7.62%} at high load level. +- All results assumed 49dBm BS transmission power. +- All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 4 and small packet size, (SBFD#1\_UMA\_FR1\_Sub#13, one source) + - Semi-static SBFD provides mean DL Average-UPT gain of 3.92% and 5% DL Average-UPT loss of -5.64% at low load level, mean DL Average-UPT gain of 3.48% and 5% DL Average-UPT loss of -34.76% at medium load level, mean and 5% DL Average-UPT loss of {-3.13%, -33.58%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {35.05%, 53.84%} at low load level, mean UL Average-UPT gain of 48.41% and 5% UL Average-UPT loss of -8.65% at medium load level, mean UL Average-UPT gain of 58.24% and 5% UL Average-UPT loss of -20.00% at high load level. + - All results assumed 49dBm BS transmission power. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 2 and large packet size, (SBFD#1\_UMA\_FR1\_Sub#18, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-32.67%, -37.79%} at low load level, mean and 5% DL Average-UPT loss of {-39.98%, -43.31%} at medium load level, mean and 5% DL Average-UPT loss of {-37.88%, -51.55%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {55.50%, 65.72%} at low load level, mean and 5% UL Average-UPT gain of {78.31%, 57.36%} at medium load level, mean and 5% UL Average-UPT gain of {44.70%, 36.44%} at high load level. + - All results assumed 49dBm BS transmission power. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 2 and small packet size, (SBFD#1\_UMA\_FR1\_Sub#17, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-19.03%, -23.11%} at low load level, mean and 5% DL Average-UPT loss of {-22.53%, -30.41%} at medium load level, mean and 5% DL Average-UPT loss of {-23.93%, -41.33%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {53.77%, 112.50%} at low load level, mean and 5% UL Average-UPT gain of {71.15%, 47.11%} at medium load level, mean and 5% UL Average-UPT gain of {53.98%, 36.00%} at high load level. + - All results assumed 49dBm BS transmission power. + - All results assumed piecewise linear noise figure model. + +**For Urban Macro (FR1) in SBFD deployment case 1, if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is no less than 93 dB, assuming SBFD antenna configuration option-3 (same area and half TxRUs):** + +- In case of using SBFD Alt 4 and large packet size, (SBFD#1\_UMA\_FR1\_Sub#16, 2 sources) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-29.41%, -84.37%} at low load level, mean and 5% DL Average-UPT loss of {-43.59%, -95.99%} at medium load level, mean and 5% DL Average-UPT loss of {-44.77%, -99.71%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-15.22%, -25.96%} at low load level, mean and 5% UL Average-UPT loss of {-67.43%, -84.89%} at medium load level, mean and 5% UL Average-UPT loss of {-89.48%, -98.72%} at high load level. + +- All results assumed 53dBm BS transmission power. +- All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 4 and small packet size, (SBFD#1\_UMA\_FR1\_Sub#15, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-21.94%, -95.63%} at low load level, mean and 5% DL Average-UPT loss of {-26.19%, -99.79%} at medium load level, mean and 5% DL Average-UPT loss of {-31.79%, -99.87%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-25.88%, -64.29%} at low load level, mean and 5% UL Average-UPT loss of {-64.23%, -90.88%} at medium load level, mean and 5% UL Average-UPT loss of {-87.56%, -95.32%} at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 2 and large packet size, (SBFD#1\_UMA\_FR1\_Sub#22, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-10.90%, -27.44%} at low load level, mean and 5% DL Average-UPT loss of {-25.51%, -46.79%} at medium load level, mean and 5% DL Average-UPT loss of {-51.28%, -74.36%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-7.03%, -18.27%} at low load level, mean and 5% UL Average-UPT loss of {-39.72%, -75.03%} at medium load level, mean and 5% UL Average-UPT loss of {-65.29%, -89.98%} at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 2 and small packet size, (SBFD#1\_UMA\_FR1\_Sub#19, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-28.40%, -41.34%} at low load level, mean and 5% DL Average-UPT loss of {-49.56%, -70.25%} at medium load level, mean and 5% DL Average-UPT loss of {-71.29%, -85.46%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {52.70%, 57.19%} at low load level, mean UL Average-UPT gain of 18.33% and 5% UL Average-UPT loss of -44.05% at medium load level, mean UL Average-UPT gain of 10.80% and 5% UL Average-UPT loss of -48.58% at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. + +**For Urban Macro (FR1) in SBFD deployment case 1, if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is less than 93 dB, assuming SBFD antenna configuration option-3 (same area&half TxRUs):** + +- In case of using SBFD Alt 4 and large packet size, (SBFD#1\_UMA\_FR1\_Sub#24, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-34.46%, -86.28%} at low load level, mean and 5% DL Average-UPT loss of {-41.74%, -95.17%} at medium load level, mean and 5% DL Average-UPT loss of {-40.02%, -99.15%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-65.98%, -100.00%} at low load level, mean and 5% UL Average-UPT loss of {-96.66%, -100.00%} at medium load level, mean and 5% UL Average-UPT loss of {-99.92%, -100.00%} at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 4 and small packet size, (SBFD#1\_UMA\_FR1\_Sub#23, one source) + +- Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-18.09%, -85.84%} at low load level, mean and 5% DL Average-UPT loss of {-18.70%, -99.58%} at medium load level, mean and 5% DL Average-UPT loss of {-21.93%, -99.70%} at high load level. +- Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-99.38%, -100.00%} at low load level, mean and 5% UL Average-UPT loss of {-100.00%, -100.00%} at medium load level, mean and 5% UL Average-UPT loss of {-100.00%, -100.00%} at high load level. +- All results assumed 53dBm BS transmission power. +- All results assumed piecewise linear noise figure model. + +### 7.3.1.1.3 Dense Urban Macro layer (FR1) + +8 sources provided the SLS evaluation results for Dense Urban Macro layer (FR1) in SBFD Deployment Case 1. The evaluation results are categorized into 17 sub-cases as in Table 7.3.1.1.3-1~Table 7.3.1.1.3-5 based on the different key assumptions. Each sub-case is based on one combination of key assumptions. + +**Table 7.3.1.1.3-1: Sub-cases for dense urban macro layer (FR1) with no less than 93dB inter-sector isolation and Twice area&same TxRUs in SBFD deployment Case 1.** + +| | | SBFD#1_DU
Macro_FR1_
Sub#1 | SBFD#1_DU
Macro_FR1_
Sub#2 | SBFD#1_DU
Macro_FR1_
Sub#3 | SBFD#1_DU
Macro_FR1_
Sub#4 | SBFD#1_DU
Macro_FR1_
Sub#15 | +|---------------------------------------------------------------|------------------------------------------|------------------------------------|------------------------------------------------|----------------------------------|------------------------------------------|-----------------------------------| +| Co-site:
Spatial
isolation
+
digital
isolation | Opt 1:>=93dB | ○ | ○ | ○ | ○ | ○ | +| | Opt 2: < 93dB | | | | | | +| | Opt 3: 93dB | | | | | | +| SBFD
slot
configu
ration | Alt-4: {DDDSU} vs. {XXXXX} | ○ | ○ | | | | +| | Alt-2: {DDDSU} vs. {XXXXU} | | | ○ | ○ | | +| | Alt-1: {DDDSU} vs. {DXXXU} | | | | | ○ | +| | Alt-3: {DDSUU} vs. {XXXU} | | | | | | +| SBFD
antenn
a
configu
ration | Twice area&same TxRUs (Option 2) | ○ | ○ | ○ | ○ | ○ | +| | Same area&same TxRUs (Option 1) | | | | | | +| | Same area&half TxRUs (Option 3) | | | | | | +| Packet
Size | Option 1: DL: 4Kbytes, UL: 1Kbytes | ○ | | ○ | | | +| | Option 2: DL: 0.5Mbytes, UL: 0.125Mbytes | | ○ | | ○ | ○ | +| Sources | | 4 sources ([17], [24], [32], [33]) | 6 sources ([17], [19], [24], [28], [32], [33]) | 2 sources ([17], [32]) | 5 sources ([17], [19], [22], [28], [32]) | 1 source ([19]) | + +**Table 7.3.1.1.3-2: Sub-cases for dense urban macro layer (FR1) with less than 93dB inter-sector isolation and Twice area&same TxRUs in SBFD deployment Case 1.** + +| | | SBFD#1_DUMac
ro_FR1_Sub#5 | SBFD#1_DUMac
ro_FR1_Sub#6 | SBFD#1_DUMac
ro_FR1_Sub#7 | SBFD#1_DUMac
ro_FR1_Sub#8 | +|---------------------------------------------------------------|----------------------------|------------------------------|------------------------------|------------------------------|------------------------------| +| Co-site:
Spatial
isolation
+
digital
isolation | Opt 1:>=93dB | | | | | +| | Opt 2: < 93dB | ○ | ○ | ○ | ○ | +| | Opt 3: 93dB | | | | | +| SBFD
slot
configura
tion | Alt-4: {DDDSU} vs. {XXXXX} | ○ | ○ | | | +| | Alt-2: {DDDSU} vs. {XXXXU} | | | ○ | ○ | +| | Alt-1: {DDDSU} vs. {DXXXU} | | | | | +| | Alt-3: {DDSUU} vs. {XXXU} | | | | | + +| | | | | | | +|----------------------------|------------------------------------------|------------------------|------------------------|-----------------|-----------------| +| SBFD antenna configuration | Twice area&same TxRUs (Option 2) | O | O | O | O | +| | Same area&same TxRUs (Option 1) | | | | | +| | Same area&half TxRUs (Option 3) | | | | | +| Packet Size | Option 1: DL: 4Kbytes, UL: 1Kbytes | O | | O | | +| | Option 2: DL: 0.5Mbytes, UL: 0.125Mbytes | | O | | O | +| Sources | | 2 sources ([24], [25]) | 2 sources ([24], [25]) | 1 source ([25]) | 1 source ([25]) | + +Table 7.3.1.1.3-3: Sub-cases for dense urban macro layer (FR1) with 93dB inter-sector isolation and Twice area&same TxRUs in SBFD deployment Case 1. + +| | | SBFD#1_DUMacro_FR1_Sub#9 | SBFD#1_DUMacro_FR1_Sub#10 | SBFD#1_DUMacro_FR1_Sub#11 | SBFD#1_DUMacro_FR1_Sub#12 | +|------------------------------------------------|------------------------------------------|--------------------------|------------------------------|---------------------------|------------------------------| +| Co-site: Spatial isolation + digital isolation | Opt 1:>=93dB | | | | | +| | Opt 2: < 93dB | | | | | +| | Opt 3: 93dB | O | O | O | O | +| SBFD slot configuration | Alt-4: {DDDSU} vs. {XXXXX} | O | O | | | +| | Alt-2: {DDDSU} vs. {XXXXU} | | | O | O | +| | Alt-1: {DDDSU} vs. {DXXXU} | | | | | +| | Alt-3: {DDSUU} vs. {XXXXU} | | | | | +| SBFD antenna configuration | Twice area&same TxRUs (Option 2) | O | O | O | O | +| | Same area&same TxRUs (Option 1) | | | | | +| | Same area&half TxRUs (Option 3) | | | | | +| Packet Size | Option 1: DL: 4Kbytes, UL: 1Kbytes | O | | O | | +| | Option 2: DL: 0.5Mbytes, UL: 0.125Mbytes | | O | | O | +| Sources | | 2 sources ([24], [32]) | 3 sources ([24], [28], [32]) | 1 source ([32]) | 3 sources ([22], [28], [32]) | + +Table 7.3.1.1.3-4: Sub-cases for dense urban macro layer (FR1) with no less than 93dB inter-sector isolation and Same area&half TxRUs in SBFD deployment Case 1. + +| | | SBFD#1_DUMacro_FR1_Sub#13 | SBFD#1_DUMacro_FR1_Sub#14 | +|------------------------------------------------|------------------------------------------|---------------------------|---------------------------| +| Co-site: Spatial isolation + digital isolation | Opt 1:>=93dB | O | O | +| | Opt 2: < 93dB | | | +| | Opt 3: 93dB | | | +| SBFD slot configuration | Alt-4: {DDDSU} vs. {XXXXX} | O | O | +| | Alt-2: {DDDSU} vs. {XXXXU} | | | +| | Alt-1: {DDDSU} vs. {DXXXU} | | | +| | Alt-3: {DDSUU} vs. {XXXXU} | | | +| SBFD antenna configuration | Twice area&same TxRUs (Option 2) | | | +| | Same area&same TxRUs (Option 1) | | | +| | Same area&half TxRUs (Option 3) | O | O | +| Packet Size | Option 1: DL: 4Kbytes, UL: 1Kbytes | O | | +| | Option 2: DL: 0.5Mbytes, UL: 0.125Mbytes | | O | +| Sources | | 1 source ([24]) | 1 source ([24]) | + +**Table 7.3.1.1.3-5: Sub-cases for dense urban macro layer (FR1) with less than 93dB inter-sector isolation and Same area&half TxRUs in SBFD deployment Case 1.** + +| | | SBFD#1_DUMacro_FR1_Sub#16 | SBFD#1_DUMacro_FR1_Sub#17 | +|------------------------------------------------------------|---------------------------------------------|---------------------------|---------------------------| +| Co-site:
Spatial
isolation +
digital
isolation | Opt 1: >=93dB | | | +| | Opt 2: < 93dB | O | O | +| | Opt 3: 93dB | | | +| SBFD slot
configuration | Alt-4: {DDDSU} vs. {XXXXX} | O | O | +| | Alt-2: {DDDSU} vs. {XXXXU} | | | +| | Alt-1: {DDDSU} vs. {DXXXU} | | | +| | Alt-3: {DDSUU} vs. {XXXXU} | | | +| SBFD
antenna
configuration | Twice area&same TxRUs
(Option 2) | | | +| | Same area&same TxRUs
(Option 1) | | | +| | Same area&half TxRUs
(Option 3) | O | O | +| Packet Size | Option 1: DL: 4Kbytes, UL:
1Kbytes | O | | +| | Option 2: DL: 0.5Mbytes, UL:
0.125Mbytes | | O | +| Sources | | 1 source ([24]) | 1 source ([24]) | + +### 7.3.1.1.3.1 Summary of the observations + +**For Dense Urban Macro (FR1) in SBFD deployment case 1, if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is no less than 93 dB, assuming SBFD antenna configuration option-2 (twice area and same TxRUs):** + +- In case of using SBFD Alt 4 and large packet size, (SBFD#1\_DUMacro\_FR1\_Sub#2, 6 sources) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.17%, -5.91%} at low load level, mean and 5% DL Average-UPT loss of {-9.81%, -19.72%} at medium load level, mean and 5% DL Average-UPT loss of {-11.35%, -35.57%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {23.43%, 52.17%} at low load level, mean and 5% UL Average-UPT gain of {5.71%, 55.17%} at medium load level, mean and 5% UL Average-UPT loss of {-41.66%, -65.00%} at high load level. +- With 44dBm BS transmission power assumed by 6 sources, + - Semi-static SBFD provides mean DL Average-UPT gain of 0.27% and 5% DL Average-UPT loss of -2.10% at low load level, mean and 5% DL Average-UPT loss of {-5.57%, -19.72%} at medium load level, mean and 5% DL Average-UPT loss of {-15.24%, -23.72%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {23.43%, 52.17%} at low load level, mean and 5% UL Average-UPT gain of {5.71%, 55.17%} at medium load level, mean and 5% UL Average-UPT loss of {-41.66%, -65.00%} at high load level. +- With 53dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-3.74%, -6.69%} at low load level, mean and 5% DL Average-UPT loss of {-10.57%, -26.55%} at medium load level, mean and 5% DL Average-UPT loss of {-10.04%, -46.83%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {24.96%, 33.42%} at low load level, mean UL Average-UPT loss of -6.29% and 5% UL Average-UPT gain of 12.08% at medium load level, mean UL Average-UPT loss of -22.96% and 5% UL Average-UPT gain of 58.52% at high load level. +- With piecewise noise figure model assumed by 4 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-3.74%, -7.03%} at low load level, mean and 5% DL Average-UPT loss of {-10.57%, -23.62%} at medium load level, mean and 5% DL Average-UPT loss of {-13.29%, -46.83%} at high load level. + +- Semi-static SBFD provides mean and 5% UL Average-UPT gain of {31.07%, 55.80%} at low load level, mean and 5% UL Average-UPT gain of {10.25%, 56.03%} at medium load level, mean and 5% UL Average-UPT loss of {-19.15%, -19.51%} at high load level. +- With flat noise figure model assumed by 2 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {3.50%, 10.36%} at low load level, mean and 5% DL Average-UPT loss of {-0.59%, -9.57%} at medium load level, mean and 5% DL Average-UPT loss of {-4.16%, -15.13%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {14.37%, 15.51%} at low load level, mean and 5% UL Average-UPT loss of {-33.82%, -86.83%} at medium load level, mean and 5% UL Average-UPT loss of {-63.77%, -96.97%} at high load level. +- In case of using SBFD Alt 4 and small packet size, (SBFD#1\_DUMacro\_FR1\_Sub#1, 4 sources) + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {2.20%, 0.56%} at low load level, mean and 5% DL Average-UPT loss of {-3.71%, -19.82%} at medium load level, mean and 5% DL Average-UPT loss of {-9.15%, -36.87%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {54.57%, 68.20%} at low load level, mean UL Average-UPT gain of 40.00% and 5% UL Average-UPT loss of -1.49% at medium load level, mean UL Average-UPT gain of 28.46% and 5% UL Average-UPT loss of -78.76% at high load level. + - All results assumed 44dBm BS transmission power. + - With piecewise noise figure model assumed by 2 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {2.26%, 2.00%} at low load level, mean and 5% DL Average-UPT loss of {-1.83%, -14.84%} at medium load level, mean and 5% DL Average-UPT loss of {-6.28%, -59.31%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {38.70%, 45.98%} at low load level, mean and 5% UL Average-UPT gain of {23.72%, 5.47%} at medium load level, mean UL Average-UPT gain of 1.43% and 5% UL Average-UPT loss of -39.68% at high load level. + - With flat noise figure model assumed by 2 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {2.20%, 0.56%} at low load level, mean and 5% DL Average-UPT loss of {-7.81%, -19.82%} at medium load level, mean and 5% DL Average-UPT loss of {-15.98%, -36.87%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {134.88%, 68.20%} at low load level, mean UL Average-UPT gain of 102.98% and 5% UL Average-UPT loss of -73.63% at medium load level, mean UL Average-UPT gain of 37.50% and 5% UL Average-UPT loss of -98.41% at high load level. +- In case of using SBFD Alt 2 and large packet size, (SBFD#1\_DUMacro\_FR1\_Sub#4, 5 sources) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-26.93%, -29.63%} at low load level, mean and 5% DL Average-UPT loss of {-33.34%, -43.91%} at medium load level, mean and 5% DL Average-UPT loss of {-38.22%, -65.45%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {76.65%, 104.36%} at low load level, mean and 5% UL Average-UPT gain of {70.38%, 153.45%} at medium load level, mean and 5% UL Average-UPT gain of {68.10%, 158.13%} at high load level. + - With 44dBm BS transmission power assumed by 4 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-24.43%, -27.42%} at low load level, mean and 5% DL Average-UPT loss of {-31.50%, -38.80%} at medium load level, mean and 5% DL Average-UPT loss of {-37.69%, -58.27%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {81.60%, 94.55%} at low load level, mean and 5% UL Average-UPT gain of {79.59%, 146.37%} at medium load level, mean and 5% UL Average-UPT gain of {62.27%, 84.53%} at high load level. + +- With 53dBm BS transmission power assumed by 2 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-28.37%, -29.63%} at low load level, mean and 5% DL Average-UPT loss of {-33.34%, -43.91%} at medium load level, mean and 5% DL Average-UPT loss of {-38.22%, -65.48%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {76.65%, 131.60%} at low load level, mean and 5% UL Average-UPT gain of {67.95%, 163.66%} at medium load level, mean and 5% UL Average-UPT gain of {72.06%, 400.24%} at high load level. +- With piecewise noise figure model assumed by 4 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-27.65%, -30.16%} at low load level, mean and 5% DL Average-UPT loss of {-35.62%, -43.96%} at medium load level, mean and 5% DL Average-UPT loss of {-41.30%, -65.47%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {76.42%, 103.47%} at low load level, mean and 5% UL Average-UPT gain of {69.16%, 146.37%} at medium load level, mean and 5% UL Average-UPT gain of {62.27%, 152.75%} at high load level. +- With flat noise figure model assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-21.71%, -24.15%} at low load level, mean and 5% DL Average-UPT loss of {-25.10%, -33.59%} at medium load level, mean and 5% DL Average-UPT loss of {-30.98%, -43.57%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {87.02%, 317.73%} at low load level, mean and 5% UL Average-UPT gain of {88.79%, 282.04%} at medium load level, mean and 5% UL Average-UPT gain of {96.35%, 261.98%} at high load level. +- In case of using SBFD Alt 2 and small packet size, (SBFD#1\_DUMacro\_FR1\_Sub#3, 2 sources) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-1.47%, -1.71%} at low load level, mean and 5% DL Average-UPT loss of {-3.67%, -8.03%} at medium load level, mean and 5% DL Average-UPT loss of {-11.54%, -39.66%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {76.56%, 91.88%} at low load level, mean and 5% UL Average-UPT gain of {70.73%, 79.28%} at medium load level, mean and 5% UL Average-UPT gain of {64.03%, 61.55%} at high load level. +- All results assumed 44dBm BS transmission power. +- With piecewise noise figure model assumed by 1 source, + - Semi-static SBFD provides mean DL Average-UPT gain of 0.02% and 5% DL Average-UPT loss of -0.31% at low load level, mean and 5% DL Average-UPT loss of {-2.64%, -8.30%} at medium load level, mean and 5% DL Average-UPT loss of {-12.52%, -57.22%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {102.17%, 115.37%} at low load level, mean and 5% UL Average-UPT gain of {103.30%, 108.38%} at medium load level, mean and 5% UL Average-UPT gain of {101.51%, 83.27%} at high load level. +- With flat noise figure model assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-2.96%, -3.11%} at low load level, mean and 5% DL Average-UPT loss of {-4.71%, -7.75%} at medium load level, mean and 5% DL Average-UPT loss of {-10.56%, -22.09%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {50.96%, 68.38%} at low load level, mean and 5% UL Average-UPT gain of {38.17%, 50.18%} at medium load level, mean and 5% UL Average-UPT gain of {26.54%, 39.84%} at high load level. +- In case of using SBFD Alt 1 and large packet size, (SBFD#1\_DUMacro\_FR1\_Sub#15, one source) + +- Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-20.97%, -20.19%} at low load level, mean and 5% DL Average-UPT loss of {-32.69%, -48.13%} at medium load level, mean and 5% DL Average-UPT loss of {-39.65%, -68.87%} at high load level. +- Semi-static SBFD provides mean and 5% UL Average-UPT gain of {59.23%, 74.12%} at low load level, mean and 5% UL Average-UPT gain of {48.89%, 128.38%} at medium load level, mean and 5% UL Average-UPT gain of {46.80%, 70.45%} at high load level. +- With 44dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-26.66%, -20.19%} at low load level, mean and 5% DL Average-UPT loss of {-37.51%, -49.79%} at medium load level, mean and 5% DL Average-UPT loss of {-44.97%, -70.69%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {59.23%, 79.17%} at low load level, mean and 5% UL Average-UPT gain of {48.89%, 128.38%} at medium load level, mean UL Average-UPT gain of 30.46% and 5% UL Average-UPT loss of -100.00% at high load level. +- With 53dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-19.41%, -19.03%} at low load level, mean and 5% DL Average-UPT loss of {-25.48%, -35.82%} at medium load level, mean and 5% DL Average-UPT loss of {-30.41%, -43.76%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {56.45%, 59.02%} at low load level, mean and 5% UL Average-UPT gain of {50.25%, 94.50%} at medium load level, mean and 5% UL Average-UPT gain of {54.44%, 308.33%} at high load level. +- All results assumed piecewise linear noise figure model. + +**For Dense Urban Macro (FR1) in SBFD deployment case 1, if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is less than 93 dB, assuming SBFD antenna configuration option-2 (twice area and same TxRUs):** + +- In case of using SBFD Alt 4 and large packet size, (SBFD#1\_DUMacro\_FR1\_Sub#6, 2 sources) + - Semi-static SBFD provides mean DL Average-UPT gain of 1.28% and 5% DL Average-UPT loss of -9.75% at low load level, mean and 5% DL Average-UPT loss of {-6.55%, -43.78%} at medium load level, mean and 5% DL Average-UPT loss of {-9.44%, -43.98%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {23.83%, 218.13%} at low load level, mean UL Average-UPT gain of 1.23% and 5% UL Average-UPT loss of -2.78% at medium load level, mean and 5% UL Average-UPT loss of {-25.72%, -98.15%} at high load level. +- With 44dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.44%, -7.67%} at low load level, mean and 5% DL Average-UPT loss of {-9.73%, -42.45%} at medium load level, mean and 5% DL Average-UPT loss of {-18.48%, -72.06%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {2.74%, 218.13%} at low load level, mean and 5% UL Average-UPT loss of {-48.72%, -2.78%} at medium load level, mean and 5% UL Average-UPT loss of {-92.91%, -98.15%} at high load level. +- With 53dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean DL Average-UPT gain of 3.01% and 5% DL Average-UPT loss of -11.84% at low load level, mean and 5% DL Average-UPT loss of {-3.38%, -45.10%} at medium load level, mean and 5% DL Average-UPT loss of {-0.40%, -15.89%} at high load level. + - Semi-static SBFD provides mean UL Average-UPT gain of 44.92% at low load level, mean UL Average-UPT gain of 51.18% at medium load level, mean UL Average-UPT gain of 41.46% at high load level. +- With piecewise noise figure model assumed by 1 source, + +- Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.44%, -7.67%} at low load level, mean and 5% DL Average-UPT loss of {-9.73%, -42.45%} at medium load level, mean and 5% DL Average-UPT loss of {-18.48%, -72.06%} at high load level. +- Semi-static SBFD provides mean and 5% UL Average-UPT gain of {2.74%, 218.13%} at low load level, mean and 5% UL Average-UPT loss of {-48.72%, -2.78%} at medium load level, mean and 5% UL Average-UPT loss of {-92.91%, -98.15%} at high load level. +- With flat noise figure model assumed by 1 source, + - Semi-static SBFD provides mean DL Average-UPT gain of 3.01% and 5% DL Average-UPT loss of -11.84% at low load level, mean and 5% DL Average-UPT loss of {-3.38%, -45.10%} at medium load level, mean and 5% DL Average-UPT loss of {-0.40%, -15.89%} at high load level. + - Semi-static SBFD provides mean UL Average-UPT gain of 44.92% at low load level, mean UL Average-UPT gain of 51.18% at medium load level, mean UL Average-UPT gain of 41.46% at high load level. +- In case of using SBFD Alt 4 and small packet size, (SBFD#1\_DUMacro\_FR1\_Sub#5, 2 sources) + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {10.48%, 9.79%} at low load level, mean and 5% DL Average-UPT loss of {-4.97%, -34.52%} at medium load level, mean and 5% DL Average-UPT loss of {-8.04%, -98.65%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {61.66%, 52.56%} at low load level, mean and 5% UL Average-UPT loss of {-58.08%, -98.95%} at medium load level, mean and 5% UL Average-UPT loss of {-93.98%, -93.67%} at high load level. +- With 44dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {2.34%, 2.61%} at low load level, mean and 5% DL Average-UPT loss of {-4.97%, -34.52%} at medium load level, mean and 5% DL Average-UPT loss of {-8.04%, -98.65%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {32.87%, 27.49%} at low load level, mean and 5% UL Average-UPT loss of {-58.08%, -98.95%} at medium load level, mean and 5% UL Average-UPT loss of {-93.98%, -93.67%} at high load level. +- With 53dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {18.62%, 16.98%} at low load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {90.46%, 77.63%} at low load level. +- With piecewise noise figure model assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {2.34%, 2.61%} at low load level, mean and 5% DL Average-UPT loss of {-4.97%, -34.52%} at medium load level, mean and 5% DL Average-UPT loss of {-8.04%, -98.65%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {32.87%, 27.49%} at low load level, mean and 5% UL Average-UPT loss of {-58.08%, -98.95%} at medium load level, mean and 5% UL Average-UPT loss of {-93.98%, -93.67%} at high load level. +- With flat noise figure model assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {18.62%, 16.98%} at low load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {90.46%, 77.63%} at low load level. +- In case of using SBFD Alt 2 and large packet size, (SBFD#1\_DUMacro\_FR1\_Sub#8, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-17.60%, -31.07%} at low load level, mean and 5% DL Average-UPT loss of {-27.16%, -59.90%} at medium load level, mean and 5% DL Average-UPT loss of {-26.08%, -39.40%} at high load level. + +- Semi-static SBFD provides mean UL Average-UPT gain of 103.52% at low load level, mean UL Average-UPT gain of 114.71% at medium load level, mean UL Average-UPT gain of 85.64% at high load level. +- All results assumed 53dBm BS transmission power. +- All results assumed 5dBs flat noise figure model. +- In case of using SBFD Alt 2 and small packet size, (SBFD#1\_DUMacro\_FR1\_Sub#7, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {10.06%, 7.52%} at low load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {90.66%, 75.51%} at low load level. + - All results assumed 53dBm BS transmission power. + - All results assumed 5dBs flat noise figure model. + +**For Dense Urban Macro (FR1) in SBFD deployment case 1, if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is equal to 93 dB, assuming SBFD antenna configuration option-2 (twice area and same TxRUs):** + +- In case of using SBFD Alt 4 and large packet size, (SBFD#1\_DUMacro\_FR1\_Sub#10, 3 sources) + - Semi-static SBFD provides mean DL Average-UPT gain of 1.18% and 5% DL Average-UPT loss of -1.49% at low load level, mean and 5% DL Average-UPT loss of {-1.58%, -5.34%} at medium load level, mean and 5% DL Average-UPT loss of {-6.07%, -10.59%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {28.96%, 52.17%} at low load level, mean and 5% UL Average-UPT gain of {21.52%, 55.17%} at medium load level, mean and 5% UL Average-UPT gain of {17.32%, 25.98%} at high load level. + - All results assumed 44dBm BS transmission power. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 4 and small packet size, (SBFD#1\_DUMacro\_FR1\_Sub#9, 2 sources) + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {2.26%, 2.00%} at low load level, mean and 5% DL Average-UPT loss of {-1.83%, -14.84%} at medium load level, mean and 5% DL Average-UPT loss of {-6.28%, -59.31%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {38.70%, 45.98%} at low load level, mean and 5% UL Average-UPT gain of {23.72%, 5.47%} at medium load level, mean UL Average-UPT gain of 1.43% and 5% UL Average-UPT loss of -39.68% at high load level. + - All results assumed 44dBm BS transmission power. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 2 and large packet size, (SBFD#1\_DUMacro\_FR1\_Sub#12, 3 sources) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-21.92%, -33.05%} at low load level, mean and 5% DL Average-UPT loss of {-21.92%, -32.35%} at medium load level, mean and 5% DL Average-UPT loss of {-28.36%, -51.08%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {123.47%, 104.36%} at low load level, mean and 5% UL Average-UPT gain of {112.72%, 139.28%} at medium load level, mean and 5% UL Average-UPT gain of {123.71%, 147.37%} at high load level. + - With 44dBm BS transmission power assumed by 2 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-20.14%, -28.34%} at low load level, mean and 5% DL Average-UPT loss of {-17.89%, -26.80%} at medium load level, mean and 5% DL Average-UPT loss of {-27.30%, -40.43%} at high load level. + +- Semi-static SBFD provides mean and 5% UL Average-UPT gain of {107.07%, 83.10%} at low load level, mean and 5% UL Average-UPT gain of {105.22%, 121.37%} at medium load level, mean and 5% UL Average-UPT gain of {98.10%, 84.53%} at high load level. +- With 53dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-28.45%, -45.94%} at low load level, mean and 5% DL Average-UPT loss of {-44.82%, -72.72%} at medium load level, mean and 5% DL Average-UPT loss of {-75.97%, -90.92%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {143.65%, 357.85%} at low load level, mean and 5% UL Average-UPT gain of {145.40%, 392.89%} at medium load level, mean and 5% UL Average-UPT gain of {123.71%, 400.24%} at high load level. +- All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 2 and small packet size, (SBFD#1\_DUMacro\_FR1\_Sub#11, one source) + - Semi-static SBFD provides mean DL Average-UPT gain of 0.02% and 5% DL Average-UPT loss of -0.31% at low load level, mean and 5% DL Average-UPT loss of {-2.64%, -8.30%} at medium load level, mean and 5% DL Average-UPT loss of {-12.52%, -57.22%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {102.17%, 115.37%} at low load level, mean and 5% UL Average-UPT gain of {103.30%, 108.38%} at medium load level, mean and 5% UL Average-UPT gain of {101.51%, 83.27%} at high load level. + - All results assumed 44dBm BS transmission power. + - All results assumed piecewise linear noise figure model. + +**For Dense Urban Macro (FR1) in SBFD deployment case 1, if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is no less than 93 dB, assuming SBFD antenna configuration option-3 (same area and half TxRUs):** + +- In case of using SBFD Alt 4 and large packet size, (SBFD#1\_DUMacro\_FR1\_Sub#14, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-3.58%, -23.19%} at low load level, mean and 5% DL Average-UPT loss of {-15.02%, -48.84%} at medium load level, mean and 5% DL Average-UPT loss of {-29.97%, -87.47%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {6.83%, 235.36%} at low load level, mean UL Average-UPT loss of -25.62% and 5% UL Average-UPT gain of 92.06% at medium load level, mean and 5% UL Average-UPT loss of {-71.49%, -92.57%} at high load level. + - All results assumed 44dBm BS transmission power. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 4 and small packet size, (SBFD#1\_DUMacro\_FR1\_Sub#13, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {2.33%, 3.14%} at low load level, mean and 5% DL Average-UPT loss of {-10.01%, -62.19%} at medium load level, mean and 5% DL Average-UPT loss of {-19.95%, -99.32%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {47.30%, 76.21%} at low load level, mean and 5% UL Average-UPT loss of {-4.00%, -92.35%} at medium load level, mean and 5% UL Average-UPT loss of {-66.35%, -87.94%} at high load level. + - All results assumed 44dBm BS transmission power. + - All results assumed piecewise linear noise figure model. + +**For Dense Urban Macro (FR1) in SBFD deployment case 1, if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is less than 93 dB, assuming SBFD antenna configuration option-3 (same area and half TxRUs):** + +- In case of using SBFD Alt 4 and large packet size, (SBFD#1\_DUMacro\_FR1\_Sub#17, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-4.31%, -24.92%} at low load level, mean and 5% DL Average-UPT loss of {-21.39%, -60.56%} at medium load level, mean and 5% DL Average-UPT loss of {-30.25%, -88.66%} at high load level. + - Semi-static SBFD provides mean UL Average-UPT loss of -16.79% and 5% UL Average-UPT gain of 137.56% at low load level, mean and 5% UL Average-UPT loss of {-70.48%, -84.13%} at medium load level, mean and 5% UL Average-UPT loss of {-97.03%, -99.51%} at high load level. + - All results assumed 44dBm BS transmission power. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 4 and small packet size, (SBFD#1\_DUMacro\_FR1\_Sub#16, one source) + - Semi-static SBFD provides mean DL Average-UPT gain of 0.10% and 5% DL Average-UPT loss of -0.02% at low load level, mean and 5% DL Average-UPT loss of {-9.52%, -52.96%} at medium load level, mean and 5% DL Average-UPT loss of {-18.78%, -99.23%} at high load level. + - Semi-static SBFD provides mean UL Average-UPT gain of 20.04% and 5% UL Average-UPT loss of -10.89% at low load level, mean and 5% UL Average-UPT loss of {-84.66%, -99.57%} at medium load level, mean and 5% UL Average-UPT loss of {-96.92%, -94.41%} at high load level. + - All results assumed 44dBm BS transmission power. + - All results assumed piecewise linear noise figure model. + +#### 7.3.1.1.4 Dense Urban with 2-layer (FR1) + +One source provided the SLS evaluation results for Dense Urban with 2-layer (FR1) in SBFD Deployment Case 1. The evaluation results are categorized into 2 sub-cases as in Table 7.3.1.1.4-1 based on the different key assumptions. Each sub-case is based on one combination of key assumptions. + +**Table 7.3.1.1.4-1: Sub-cases for dense urban with 2-layer (FR1) with 93dB inter-sector isolation value and Twice area&same TxRUs in SBFD deployment Case 1.** + +| | | SBFD#1_DU2Layer_FR1_Sub#1 | SBFD#1_DU2Layer_FR1_Sub#2 | +|------------------------------------------------|------------------------------------------|---------------------------|---------------------------| +| Co-site: Spatial isolation + digital isolation | Opt 1: >=93dB | | | +| | Opt 2: < 93dB | | | +| | Opt 3: 93dB | O | O | +| SBFD slot configuration | Alt-4: {DDDSU} vs. {XXXXX} | | | +| | Alt-2: {DDDSU} vs. {XXXXU} | O | O | +| | Alt-1: {DDDSU} vs. {DXXXU} | | | +| | Alt-3: {DDSUU} vs. {XXXXU} | | | +| SBFD antenna configuration | Twice area&same TxRUs (Option 2) | O | O | +| | Same area&same TxRUs (Option 1) | | | +| | Same area&half TxRUs (Option 3) | | | +| Packet Size | Option 1: DL: 4Kbytes, UL: 1Kbytes | O | | +| | Option 2: DL: 0.5Mbytes, UL: 0.125Mbytes | | O | +| Sources | | 1 source ([32]) | 1 source ([32]) | + +#### 7.3.1.1.4.1 Summary of the observations + +**For Dense Urban with 2-layer (FR1) in SBFD deployment case 1, if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is equal to 93 dB, assuming SBFD antenna configuration option-2 (twice area and same TxRUs):** + +- In case of using SBFD Alt 2 and small packet size, (SBFD#1\_DU2Layer\_FR1\_Sub#1, one source) + +- For Layer-1: + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {0.95%, 1.94%} at low load level, mean and 5% DL Average-UPT loss of {-4.62%, -28.72%} at medium load level, mean and 5% DL Average-UPT loss of {-11.66%, -27.50%} at high load level. + - Semi-static SBFD provides mean UL Average-UPT gain of 7.23% and no change on 5% UL Average-UPT at low load level, mean UL Average-UPT gain of 7.85% and no change on 5% UL Average-UPT at medium load level, mean and 5% UL Average-UPT gain of {22.27%, 25.00%} at high load level. + - All results assumed 49dBm BS transmission power. + - All results assumed piecewise linear noise figure model. +- For Layer-2: + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {0.89%, 1.50%} at low load level, mean and 5% DL Average-UPT loss of {-5.05%, -71.48%} at medium load level, mean and 5% DL Average-UPT loss of {-8.19%, -8.70%} at high load level. + - Semi-static SBFD provides mean UL Average-UPT gain of 11.51% and no change on 5% UL Average-UPT at low load level, mean UL Average-UPT gain of 13.00% and no change on 5% UL Average-UPT at medium load level, mean and 5% UL Average-UPT gain of {27.80%, 152.83%} at high load level. + - All results assumed 38dBm BS transmission power. + - All results assumed 5dBs flat noise figure model. +- In case of using SBFD Alt 2 and large packet size, ( SBFD#1\_DU2Layer\_FR1\_Sub#2, one source) + - For Layer-1: + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-30.39%, -38.60%} at low load level, mean and 5% DL Average-UPT loss of {-32.29%, -37.43%} at medium load level, mean and 5% DL Average-UPT loss of {-38.93%, -56.48%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {10.42%, 18.09%} at low load level, mean and 5% UL Average-UPT gain of {10.74%, 5.24%} at medium load level, mean and 5% UL Average-UPT gain of {10.93%, 6.34%} at high load level. + - All results assumed 49dBm BS transmission power. + - All results assumed piecewise linear noise figure model. + - For Layer-2: + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-29.87%, -33.60%} at low load level, mean and 5% DL Average-UPT loss of {-30.82%, -30.19%} at medium load level, mean and 5% DL Average-UPT loss of {-37.65%, -52.08%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {14.54%, 23.62%} at low load level, mean and 5% UL Average-UPT gain of {13.25%, 10.50%} at medium load level, mean and 5% UL Average-UPT gain of {13.42%, 3.22%} at high load level. + - All results assumed 38dBm BS transmission power. + - All results assumed 5dBs flat noise figure model. + +### 7.3.1.2 SBFD Deployment Case 1 (FR2-1) + +#### 7.3.1.2.1 Indoor office (FR2-1) + +6 sources provided the SLS evaluation results for Indoor office (FR2-1) in SBFD Deployment Case 1. The evaluation results are categorized into 12 sub-cases as in Table 7.3.1.2.1-1~Table 7.3.1.2.1-2 based on the different key assumptions. Each sub-case is based on one combination of key assumptions. + +**Table 7.3.1.2.1-1: Sub-cases for indoor office (FR2-1) with Twice area&same TxRUs in SBFD deployment Case 1.** + +| | | SBFD#1_I
nH_FR2_S
ub#1 | SBFD#1_I
nH_FR2_S
ub#2 | SBFD#1_I
nH_FR2_S
ub#3 | SBFD#1_I
nH_FR2_S
ub#4 | SBFD#1_I
nH_FR2_S
ub#9 | SBFD#1_I
nH_FR2_S
ub#10 | +|------------------------------------------|------------------------------------------|------------------------------------------|------------------------------------------|------------------------------|------------------------------|------------------------------|-------------------------------| +| SBFD
slot
configu
ration | Alt-4: {DDDSU} vs. {XXXXX} | O | O | | | | | +| | Alt-2: {DDDSU} vs. {XXXXU} | | | O | O | | | +| | Alt-1: {DDDSU} vs. {DXXXU} | | | | | | | +| | Alt-3: {DDSUU} vs. {XXXXU} | | | | | O | O | +| SBFD
antenn
a
configu
ration | Twice area&same TxRUs (Option 2) | O | O | O | O | O | O | +| | Same area&same TxRUs (Option 1) | | | | | | | +| | Same area&half TxRUs (Option 3) | | | | | | | +| Packet
Size | Option 1: DL: 4Kbytes, UL: 1Kbytes | O | | O | | O | | +| | Option 2: DL: 0.5Mbytes, UL: 0.125Mbytes | | O | | O | | O | +| Sources | | 5 sources ([18], [24], [26], [32], [28]) | 5 sources ([18], [39], [24], [26], [28]) | 3 sources ([18], [32], [28]) | 2 sources ([18], [28]) | 1 source ([18]) | 1 source ([18]) | + +**Table 7.3.1.2.1-2: Sub-cases for indoor office (FR2-1) with Twice area&half TxRUs in SBFD deployment Case 1.** + +| | | SBFD#1_I
nH_FR2_S
ub#5 | SBFD#1_I
nH_FR2_S
ub#6 | SBFD#1_I
nH_FR2_S
ub#7 | SBFD#1_I
nH_FR2_S
ub#8 | SBFD#1_I
nH_FR2_S
ub#11 | SBFD#1_I
nH_FR2_S
ub#12 | +|------------------------------------------|------------------------------------------|------------------------------|------------------------------|------------------------------|------------------------------|-------------------------------|-------------------------------| +| SBFD
slot
configu
ration | Alt-4: {DDDSU} vs. {XXXXX} | O | O | | | | | +| | Alt-2: {DDDSU} vs. {XXXXU} | | | O | O | | | +| | Alt-1: {DDDSU} vs. {DXXXU} | | | | | | | +| | Alt-3: {DDSUU} vs. {XXXXU} | | | | | O | O | +| SBFD
antenn
a
configu
ration | Twice area&same TxRUs (Option 2) | | | | | | | +| | Same area&same TxRUs (Option 1) | | | | | | | +| | Same area&half TxRUs (Option 3) | O | O | O | O | O | O | +| Packet
Size | Option 1: DL: 4Kbytes, UL: 1Kbytes | O | | O | | O | | +| | Option 2: DL: 0.5Mbytes, UL: 0.125Mbytes | | O | | O | | O | +| Sources | | 1 source ([18]) | 1 source ([18]) | 1 source ([18]) | 1 source ([18]) | 1 source ([18]) | 1 source ([18]) | + +**7.3.1.2.1.1 Summary of the observations** + +**For Indoor office (FR2-1) in SBFD deployment case 1, assuming SBFD antenna configuration option-2 (twice area and same TxRUs):** + +- In case of using SBFD Alt 4 and large packet size, (SBFD#1\_InH\_FR2\_Sub#2, 5 sources) + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {3.63%, 6.03%} at low load level, mean and 5% DL Average-UPT gain of {3.36%, 6.67%} at medium load level, mean and 5% DL Average-UPT gain of {3.60%, 3.35%} at high load level. + +- Semi-static SBFD provides mean and 5% UL Average-UPT gain of {16.60%, 38.79%} at low load level, mean and 5% UL Average-UPT gain of {22.22%, 71.05%} at medium load level, mean and 5% UL Average-UPT gain of {20.61%, 86.18%} at high load level. +- All results assumed 23dBm BS transmission power. +- With piecewise noise figure model assumed by 4 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {3.67%, 4.39%} at low load level, mean and 5% DL Average-UPT gain of {3.41%, 5.59%} at medium load level, mean and 5% DL Average-UPT gain of {4.12%, 6.12%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {11.29%, 55.28%} at low load level, mean and 5% UL Average-UPT gain of {10.72%, 52.24%} at medium load level, mean and 5% UL Average-UPT gain of {6.56%, 45.48%} at high load level. +- With flat noise figure model assumed by 1 source, + - Semi-static SBFD provides mean DL Average-UPT loss of -0.06% and 5% DL Average-UPT gain of 8.34% at low load level, mean and 5% DL Average-UPT gain of {3.36%, 10.16%} at medium load level, mean DL Average-UPT gain of 3.60% and 5% DL Average-UPT loss of -18.35% at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {16.60%, 38.79%} at low load level, mean and 5% UL Average-UPT gain of {23.31%, 71.05%} at medium load level, mean and 5% UL Average-UPT gain of {26.70%, 218.99%} at high load level. +- In case of using SBFD Alt 4 and small packet size, (SBFD#1\_InH\_FR2\_Sub#1, 5 sources) + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {4.84%, 5.18%} at low load level, mean and 5% DL Average-UPT gain of {7.57%, 4.45%} at medium load level, mean DL Average-UPT gain of 5.95% and 5% DL Average-UPT loss of -10.25% at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {55.30%, 50.71%} at low load level, mean and 5% UL Average-UPT gain of {54.71%, 46.45%} at medium load level, mean and 5% UL Average-UPT gain of {72.66%, 59.26%} at high load level. +- All results assumed 23dBm BS transmission power. +- With piecewise noise figure model assumed by 4 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {4.82%, 5.26%} at low load level, mean and 5% DL Average-UPT gain of {6.04%, 4.62%} at medium load level, mean DL Average-UPT gain of 3.58% and 5% DL Average-UPT loss of -2.23% at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {62.52%, 67.02%} at low load level, mean and 5% UL Average-UPT gain of {78.46%, 67.73%} at medium load level, mean and 5% UL Average-UPT gain of {89.26%, 61.78%} at high load level. +- With flat noise figure model assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {7.77%, 5.18%} at low load level, mean DL Average-UPT gain of 8.42% and 5% DL Average-UPT loss of -5.02% at medium load level, mean DL Average-UPT gain of 8.31% and 5% DL Average-UPT loss of -18.27% at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {31.68%, 33.23%} at low load level, mean and 5% UL Average-UPT gain of {35.09%, 37.99%} at medium load level, mean and 5% UL Average-UPT gain of {42.88%, 56.74%} at high load level. +- In case of using SBFD Alt 2 and large packet size, (SBFD#1\_InH\_FR2\_Sub#4, 2 sources) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-20.17%, -17.57%} at low load level, mean and 5% DL Average-UPT loss of {-22.04%, -24.52%} at medium load level, mean and 5% DL Average-UPT loss of {-31.45%, -35.47%} at high load level. + +- Semi-static SBFD provides mean and 5% UL Average-UPT gain of {86.16%, 112.95%} at low load level, mean and 5% UL Average-UPT gain of {86.17%, 109.87%} at medium load level, mean and 5% UL Average-UPT gain of {114.49%, 227.77%} at high load level. +- All results assumed 23dBm BS transmission power. +- All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 2 and small packet size, (SBFD#1\_InH\_FR2\_Sub#3, 3 sources) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-4.40%, -22.33%} at low load level, mean and 5% DL Average-UPT loss of {-6.90%, -30.02%} at medium load level, mean and 5% DL Average-UPT loss of {-22.06%, -40.37%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {78.57%, 84.98%} at low load level, mean and 5% UL Average-UPT gain of {91.25%, 102.86%} at medium load level, mean and 5% UL Average-UPT gain of {149.67%, 201.41%} at high load level. + - All results assumed 23dBm BS transmission power. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 3 and large packet size, (SBFD#1\_InH\_FR2\_Sub#10, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {2.01%, 2.16%} at low load level, mean and 5% DL Average-UPT gain of {1.08%, 0.21%} at medium load level, mean DL Average-UPT loss of -0.53% and 5% DL Average-UPT gain of 1.74% at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {4.91%, 4.03%} at low load level, mean and 5% UL Average-UPT gain of {4.04%, 2.13%} at medium load level, mean UL Average-UPT gain of 1.08% and 5% UL Average-UPT loss of -15.87% at high load level. + - All results assumed 23dBm BS transmission power. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 3 and small packet size, (SBFD#1\_InH\_FR2\_Sub#9, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {9.31%, 11.40%} at low load level, mean and 5% DL Average-UPT gain of {8.65%, 9.41%} at medium load level, mean DL Average-UPT gain of 7.22% and 5% DL Average-UPT loss of -0.02% at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {75.66%, 77.73%} at low load level, mean and 5% UL Average-UPT gain of {67.85%, 58.91%} at medium load level, mean and 5% UL Average-UPT gain of {57.04%, 38.33%} at high load level. + - All results assumed 23dBm BS transmission power. + - All results assumed piecewise linear noise figure model. + +**For Indoor office (FR2-1) in SBFD deployment case 1, assuming SBFD antenna configuration option-3 (same area&half TxRUs):** + +- In case of using SBFD Alt 4 and large packet size, (SBFD#1\_InH\_FR2\_Sub#6, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {0.37%, 0.26%} at low load level, mean and 5% DL Average-UPT loss of {-1.07%, -3.62%} at medium load level, mean and 5% DL Average-UPT loss of {-6.74%, -12.44%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-1.48%, -3.12%} at low load level, mean and 5% UL Average-UPT loss of {-4.92%, -10.40%} at medium load level, mean and 5% UL Average-UPT loss of {-16.18%, -37.67%} at high load level. + - All results assumed 23dBm BS transmission power. + +- All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 4 and small packet size, (SBFD#1\_InH\_FR2\_Sub#5, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {4.95%, 5.39%} at low load level, mean and 5% DL Average-UPT gain of {4.48%, 4.44%} at medium load level, mean DL Average-UPT gain of 2.68% and 5% DL Average-UPT loss of -6.85% at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {105.27%, 107.80%} at low load level, mean and 5% UL Average-UPT gain of {100.82%, 94.52%} at medium load level, mean and 5% UL Average-UPT gain of {81.60%, 24.38%} at high load level. + - All results assumed 23dBm BS transmission power. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 2 and large packet size, (SBFD#1\_InH\_FR2\_Sub#8, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-22.44%, -24.05%} at low load level, mean and 5% DL Average-UPT loss of {-28.75%, -36.28%} at medium load level, mean and 5% DL Average-UPT loss of {-46.44%, -56.80%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {75.58%, 75.55%} at low load level, mean and 5% UL Average-UPT gain of {85.55%, 90.43%} at medium load level, mean and 5% UL Average-UPT gain of {121.09%, 231.26%} at high load level. + - All results assumed 23dBm BS transmission power. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 2 and small packet size, (SBFD#1\_InH\_FR2\_Sub#7, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-22.39%, -23.45%} at low load level, mean and 5% DL Average-UPT loss of {-28.83%, -35.88%} at medium load level, mean and 5% DL Average-UPT loss of {-46.61%, -57.00%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {75.49%, 75.30%} at low load level, mean and 5% UL Average-UPT gain of {85.45%, 91.89%} at medium load level, mean and 5% UL Average-UPT gain of {121.18%, 236.14%} at high load level. + - All results assumed 23dBm BS transmission power. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 3 and large packet size, (SBFD#1\_InH\_FR2\_Sub#12, one source) + - Semi-static SBFD provides mean DL Average-UPT gain of 1.14% and 5% DL Average-UPT loss of -0.21% at low load level, mean and 5% DL Average-UPT loss of {-2.00%, -4.74%} at medium load level, mean and 5% DL Average-UPT loss of {-10.19%, -18.04%} at high load level. + - Semi-static SBFD provides mean UL Average-UPT gain of 2.06% and 5% UL Average-UPT loss of -0.48% at low load level, mean UL Average-UPT gain of 0.15% and 5% UL Average-UPT loss of -4.04% at medium load level, mean and 5% UL Average-UPT loss of {-6.36%, -27.69%} at high load level. + - All results assumed 23dBm BS transmission power. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 3 and small packet size, (SBFD#1\_InH\_FR2\_Sub#11, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {9.34%, 10.84%} at low load level, mean and 5% DL Average-UPT gain of {8.50%, 9.14%} at medium load level, mean DL Average-UPT gain of 5.43% and 5% DL Average-UPT loss of -8.55% at high load level. + +- Semi-static SBFD provides mean and 5% UL Average-UPT gain of {75.60%, 77.12%} at low load level, mean and 5% UL Average-UPT gain of {67.59%, 57.57%} at medium load level, mean and 5% UL Average-UPT gain of {55.14%, 22.73%} at high load level. +- All results assumed 23dBm BS transmission power. +- All results assumed piecewise linear noise figure model. + +### 7.3.1.2.2 Dense Urban Macro layer (FR2-1) + +7 sources provided the SLS evaluation results for Dense Urban Macro (FR2-1) in SBFD Deployment Case 1. The evaluation results are categorized into 21 sub-cases as in Table 7.3.1.2.2-1~Table 7.3.1.2.2-6 based on the different key assumptions. Each sub-case is based on one combination of key assumptions. + +**Table 7.3.1.2.2-1: Sub-cases for dense urban macro (FR2-1) with no less than 98dB inter-sector isolation and Twice area&same TxRUs in SBFD deployment Case 1.** + +| | | SBFD#1_DU
Macro_FR2_
Sub#1 | SBFD#1_DU
Macro_FR2_
Sub#2 | SBFD#1_DU
Macro_FR2_
Sub#3 | SBFD#1_DU
Macro_FR2_
Sub#4 | SBFD#1_DU
Macro_FR2_
Sub#17 | +|---------------------------------------------------------------|------------------------------------------|----------------------------------|------------------------------------|----------------------------------|----------------------------------|-----------------------------------| +| Co-site:
Spatial
isolation
+
digital
isolation | Opt 1: >=98dB | O | O | O | O | O | +| | Opt 2: < 98dB | | | | | | +| | Opt 3: 98dB | | | | | | +| SBFD
slot
configu
ration | Alt-4: {DDDSU} vs. {XXXXX} | O | O | | | | +| | Alt-2: {DDDSU} vs. {XXXXU} | | | O | O | | +| | Alt-1: {DDDSU} vs. {DXXXU} | | | | | | +| | Alt-3: {DDSUU} vs. {XXXXU} | | | | | O | +| SBFD
antenn
a
configu
ration | Twice area&same TxRUs (Option 2) | O | O | O | O | O | +| | Same area&same TxRUs (Option 1) | | | | | | +| | Same area&half TxRUs (Option 3) | | | | | | +| Packet
Size | Option 1: DL: 4Kbytes, UL: 1Kbytes | O | | O | | | +| | Option 2: DL: 0.5Mbytes, UL: 0.125Mbytes | | O | | O | O | +| Sources | | 3 sources ([24], [26], [28]) | 4 sources ([18], [24], [26], [28]) | 1 source ([28]) | 3 sources ([18], [28], [36]) | 1 source ([18]) | + +**Table 7.3.1.2.2-2: Sub-cases for dense urban macro (FR2-1) with less than 98dB inter-sector isolation and Twice area&same TxRUs in SBFD deployment Case 1.** + +| | | SBFD#1_DUMacro_FR
2_Sub#5 | SBFD#1_DUMacro_FR
2_Sub#6 | SBFD#1_DUMacro_FR
2_Sub#20 | +|---------------------------------------------------------------|----------------------------------|------------------------------|------------------------------|-------------------------------| +| Co-site:
Spatial
isolation
+
digital
isolation | Opt 1: >=98dB | | | | +| | Opt 2: < 98dB | O | O | O | +| | Opt 3: 98dB | | | | +| SBFD
slot
configuratio
n | Alt-4: {DDDSU} vs. {XXXXX} | O | O | | +| | Alt-2: {DDDSU} vs. {XXXXU} | | | | +| | Alt-1: {DDDSU} vs. {DXXXU} | | | | +| | Alt-3: {DDSUU} vs. {XXXXU} | | | O | +| SBFD
antenna | Twice area&same TxRUs (Option 2) | O | O | O | + +| | | | | | +|---------------|------------------------------------------|-----------------|------------------------------|-----------------| +| configuration | Same area&same TxRUs (Option 1) | | | | +| | Same area&half TxRUs (Option 3) | | | | +| Packet Size | Option 1: DL: 4Kbytes, UL: 1Kbytes | O | | | +| | Option 2: DL: 0.5Mbytes, UL: 0.125Mbytes | | O | O | +| Sources | | 1 source ([24]) | 3 sources ([18], [39], [24]) | 1 source ([18]) | + +Table 7.3.1.2.2-3: Sub-cases for dense urban macro (FR2-1) with 98dB inter-sector isolation and Twice area&same TxRUs in SBFD deployment Case 1. + +| | | SBFD#1_DUMa cro_FR2_Sub#7 | SBFD#1_DUMa cro_FR2_Sub#8 | SBFD#1_DUMa cro_FR2_Sub#9 | SBFD#1_DUMa cro_FR2_Sub#10 | +|------------------------------------------------|------------------------------------------|---------------------------|------------------------------------|---------------------------|----------------------------| +| Co-site: Spatial isolation + digital isolation | Opt 1:>=98dB | | | | | +| | Opt 2: < 98dB | | | | | +| | Opt 3: 98dB | O | O | O | O | +| SBFD slot configuration | Alt-4: {DDDSU} vs. {XXXXX} | O | O | | | +| | Alt-2: {DDDSU} vs. {XXXXU} | | | O | O | +| | Alt-1: {DDDSU} vs. {DXXXU} | | | | | +| | Alt-3: {DDSUU} vs. {XXXXU} | | | | | +| SBFD antenna configuration | Twice area&same TxRUs (Option 2) | O | O | O | O | +| | Same area&same TxRUs (Option 1) | | | | | +| | Same area&half TxRUs (Option 3) | | | | | +| Packet Size | Option 1: DL: 4Kbytes, UL: 1Kbytes | O | | O | | +| | Option 2: DL: 0.5Mbytes, UL: 0.125Mbytes | | O | | O | +| Sources | | 2 sources ([24], [26]) | 4 sources ([18], [24], [26], [28]) | 1 source ([28]) | 2 sources ([18], [28]) | + +Table 7.3.1.2.2-4: Sub-cases for dense urban macro (FR2-1) with no less than 98dB inter-sector isolation and Same area&same TxRUs in SBFD deployment Case 1. + +| | | SBFD#1_DUMa cro_FR2_Sub#11 | SBFD#1_DUMa cro_FR2_Sub#12 | SBFD#1_DUMa cro_FR2_Sub#14 | SBFD#1_DUMa cro_FR2_Sub#15 | +|------------------------------------------------|------------------------------------|----------------------------|----------------------------|----------------------------|----------------------------| +| Co-site: Spatial isolation + digital isolation | Opt 1:>=98dB | O | O | O | O | +| | Opt 2: < 98dB | | | | | +| | Opt 3: 98dB | | | | | +| SBFD slot configuration | Alt-4: {DDDSU} vs. {XXXXX} | O | O | | | +| | Alt-2: {DDDSU} vs. {XXXXU} | | | O | O | +| | Alt-1: {DDDSU} vs. {DXXXU} | | | | | +| | Alt-3: {DDSUU} vs. {XXXXU} | | | | | +| SBFD antenna configuration | Twice area&same TxRUs (Option 2) | | | | | +| | Same area&same TxRUs (Option 1) | O | O | O | O | +| | Same area&half TxRUs (Option 3) | | | | | +| Packet Size | Option 1: DL: 4Kbytes, UL: 1Kbytes | O | | O | | + +| | | | | | | +|---------|---------------------------------------------|-----------------|-----------------|-----------------|-----------------| +| | Option 2: DL: 0.5Mbytes,
UL: 0.125Mbytes | | O | | O | +| Sources | | 1 source ([28]) | 1 source ([28]) | 1 source ([28]) | 1 source ([28]) | + +**Table 7.3.1.2.2-5: Sub-cases for dense urban macro (FR2-1) with no less than 98dB inter-sector isolation and Same area&half TxRUs in SBFD deployment Case 1.** + +| | | SBFD#1_DUMacro_F
R2_Sub#13 | SBFD#1_DUMacro_F
R2_Sub#16 | SBFD#1_DUMacro_F
R2_Sub#18 | +|------------------------------------------------------------|---------------------------------------------|-------------------------------|-------------------------------|-------------------------------| +| Co-site:
Spatial
isolation +
digital
isolation | Opt 1:>=98dB | O | O | O | +| | Opt 2: < 98dB | | | | +| | Opt 3: 98dB | | | | +| SBFD slot
configuratio
n | Alt-4: {DDDSU} vs.
{XXXXX} | O | | | +| | Alt-2: {DDDSU} vs.
{XXXXU} | | O | | +| | Alt-1: {DDDSU} vs.
{DXXXU} | | | | +| | Alt-3: {DDSUU} vs.
{XXXXU} | | | O | +| SBFD
antenna
configuratio
n | Twice area&same TxRUs
(Option 2) | | | | +| | Same area&same TxRUs
(Option 1) | | | | +| | Same area&half TxRUs
(Option 3) | O | O | O | +| Packet Size | Option 1: DL: 4Kbytes,
UL: 1Kbytes | | | | +| | Option 2: DL: 0.5Mbytes,
UL: 0.125Mbytes | O | O | O | +| Sources | | 1 source ([18]) | 1 source ([18]) | 1 source ([18]) | + +**Table 7.3.1.2.2-6: Sub-cases for Dense Urban Macro (FR2-1) with less than 98dB inter-sector isolation and Same area&half TxRUs in SBFD Deployment Case 1.** + +| | | SBFD#1_DUMacro_FR2_Sub#
19 | SBFD#1_DUMacro_FR2_Sub#
21 | +|------------------------------------------------------------|---------------------------------------------|-------------------------------|-------------------------------| +| Co-site:
Spatial
isolation +
digital
isolation | Opt 1:>=98dB | | | +| | Opt 2: < 98dB | O | O | +| | Opt 3: 98dB | | | +| SBFD slot
configuratio
n | Alt-4: {DDDSU} vs. {XXXXX} | O | | +| | Alt-2: {DDDSU} vs. {XXXXU} | | | +| | Alt-1: {DDDSU} vs. {DXXXU} | | | +| | Alt-3: {DDSUU} vs. {XXXXU} | | O | +| SBFD
antenna
configuratio
n | Twice area&same TxRUs (Option
2) | | | +| | Same area&same TxRUs (Option
1) | | | +| | Same area&half TxRUs (Option 3) | O | O | +| Packet Size | Option 1: DL: 4Kbytes, UL:
1Kbytes | | | +| | Option 2: DL: 0.5Mbytes, UL:
0.125Mbytes | O | O | +| Sources | | 1 source ([18]) | 1 source ([18]) | + +#### 7.3.1.2.2.1 Summary of the observations + +For Dense Urban Macro (FR2-1) in SBFD deployment case 1, if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is no less than 98 dB, assuming SBFD antenna configuration option-2 (twice area and same TxRUs): + +- In case of using SBFD Alt 4 and large packet size, (SBFD#1\_DUMacro\_FR2\_Sub#2, 4 sources) + +- Semi-static SBFD provides mean and 5% DL Average-UPT gain of {2.45%, 2.30%} at low load level, mean and 5% DL Average-UPT gain of {2.18%, 1.17%} at medium load level, mean DL Average-UPT gain of 1.48% and 5% DL Average-UPT loss of -1.37% at high load level. +- Semi-static SBFD provides mean and 5% UL Average-UPT gain of {37.31%, 19.44%} at low load level, mean and 5% UL Average-UPT gain of {30.11%, 30.93%} at medium load level, mean and 5% UL Average-UPT gain of {3.11%, 11.76%} at high load level. +- With 40dBm BS transmission power assumed by 3 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {3.62%, 5.85%} at low load level, mean and 5% DL Average-UPT gain of {2.85%, 4.40%} at medium load level, mean and 5% DL Average-UPT gain of {1.50%, 2.66%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {39.65%, 19.44%} at low load level, mean and 5% UL Average-UPT gain of {30.11%, 30.93%} at medium load level, mean and 5% UL Average-UPT gain of {3.11%, 11.76%} at high load level. +- With 30dBm BS transmission power assumed by 2 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-1.62%, -2.14%} at low load level, mean and 5% DL Average-UPT loss of {-1.64%, -4.25%} at medium load level, mean and 5% DL Average-UPT loss of {-2.69%, -5.66%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {18.41%, 147.57%} at low load level, mean and 5% UL Average-UPT gain of {17.05%, 137.24%} at medium load level, mean and 5% UL Average-UPT gain of {16.99%, 211.48%} at high load level. +- With piecewise noise figure model assumed by 3 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {3.56%, 2.90%} at low load level, mean and 5% DL Average-UPT gain of {2.75%, 3.60%} at medium load level, mean and 5% DL Average-UPT gain of {1.60%, 2.60%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {36.23%, 18.52%} at low load level, mean and 5% UL Average-UPT gain of {18.49%, 28.87%} at medium load level, mean UL Average-UPT loss of -17.88% and 5% UL Average-UPT gain of 10.78% at high load level. +- With flat noise figure model assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-4.58%, -5.84%} at low load level, mean and 5% DL Average-UPT loss of {-4.87%, -7.25%} at medium load level, mean and 5% DL Average-UPT loss of {-6.98%, -5.34%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {38.40%, 297.77%} at low load level, mean and 5% UL Average-UPT gain of {46.15%, 315.00%} at medium load level, mean and 5% UL Average-UPT gain of {59.95%, 460.29%} at high load level. +- In case of using SBFD Alt 4 and small packet size, (SBFD#1\_DUMacro\_FR2\_Sub#1, 3 sources) + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {4.69%, 4.20%} at low load level, mean and 5% DL Average-UPT gain of {2.57%, 1.27%} at medium load level, mean DL Average-UPT gain of 0.90% and 5% DL Average-UPT loss of -7.41% at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {57.78%, 65.51%} at low load level, mean and 5% UL Average-UPT gain of {49.40%, 63.03%} at medium load level, mean and 5% UL Average-UPT gain of {41.22%, 96.07%} at high load level. + - With 40dBm BS transmission power assumed by 2 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {7.62%, 4.63%} at low load level, mean and 5% DL Average-UPT gain of {6.88%, 2.70%} at medium load level, mean DL Average-UPT gain of 9.36% and 5% DL Average-UPT loss of -1.79% at high load level. + +- Semi-static SBFD provides mean and 5% UL Average-UPT gain of {60.57%, 128.85%} at low load level, mean and 5% UL Average-UPT gain of {54.25%, 2110.09%} at medium load level, mean and 5% UL Average-UPT gain of {44.80%, 73.51%} at high load level. +- With 30dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean DL Average-UPT gain of 2.92% and 5% DL Average-UPT loss of -32.44% at low load level, mean DL Average-UPT gain of 1.88% and 5% DL Average-UPT loss of -33.97% at medium load level, mean DL Average-UPT gain of 0.90% and 5% DL Average-UPT loss of -35.11% at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {32.58%, 65.51%} at low load level, mean and 5% UL Average-UPT gain of {34.88%, 63.03%} at medium load level, mean and 5% UL Average-UPT gain of {41.22%, 131.63%} at high load level. +- With piecewise noise figure model assumed by 2 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {7.62%, 4.63%} at low load level, mean and 5% DL Average-UPT gain of {6.88%, 2.70%} at medium load level, mean DL Average-UPT gain of 9.36% and 5% DL Average-UPT loss of -1.79% at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {60.57%, 128.85%} at low load level, mean and 5% UL Average-UPT gain of {54.25%, 2110.09%} at medium load level, mean and 5% UL Average-UPT gain of {44.80%, 73.51%} at high load level. +- With flat noise figure model assumed by 1 source, + - Semi-static SBFD provides mean DL Average-UPT gain of 2.92% and 5% DL Average-UPT loss of -32.44% at low load level, mean DL Average-UPT gain of 1.88% and 5% DL Average-UPT loss of -33.97% at medium load level, mean DL Average-UPT gain of 0.90% and 5% DL Average-UPT loss of -35.11% at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {32.58%, 65.51%} at low load level, mean and 5% UL Average-UPT gain of {34.88%, 63.03%} at medium load level, mean and 5% UL Average-UPT gain of {41.22%, 131.63%} at high load level. +- In case of using SBFD Alt 2 and large packet size, (SBFD#1\_DUMacro\_FR2\_Sub#4, 3 sources) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-20.50%, -22.48%} at low load level, mean and 5% DL Average-UPT loss of {-28.49%, -47.88%} at medium load level, mean and 5% DL Average-UPT loss of {-37.91%, -49.87%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {79.47%, 75.86%} at low load level, mean and 5% UL Average-UPT gain of {96.75%, 139.31%} at medium load level, mean and 5% UL Average-UPT gain of {123.96%, 100.01%} at high load level. +- With 40dBm BS transmission power assumed by 3 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-18.28%, -14.11%} at low load level, mean and 5% DL Average-UPT loss of {-24.88%, -37.94%} at medium load level, mean and 5% DL Average-UPT loss of {-34.65%, -43.15%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {92.16%, 73.12%} at low load level, mean and 5% UL Average-UPT gain of {110.62%, 118.62%} at medium load level, mean and 5% UL Average-UPT gain of {108.92%, 90.69%} at high load level. +- With 30dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-21.90%, -22.69%} at low load level, mean and 5% DL Average-UPT loss of {-29.27%, -47.90%} at medium load level, mean and 5% DL Average-UPT loss of {-38.75%, -52.11%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {79.47%, 80.11%} at low load level, mean and 5% UL Average-UPT gain of {96.75%, 164.50%} at medium load level, mean and 5% UL Average-UPT gain of {123.96%, 236.80%} at high load level. + +- With piecewise noise figure model assumed by 2 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-18.98%, -14.11%} at low load level, mean and 5% DL Average-UPT loss of {-24.88%, -37.94%} at medium load level, mean and 5% DL Average-UPT loss of {-34.65%, -43.15%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {94.10%, 73.12%} at low load level, mean and 5% UL Average-UPT gain of {118.86%, 123.89%} at medium load level, mean and 5% UL Average-UPT gain of {127.40%, 90.69%} at high load level. +- With flat noise figure model assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-20.50%, -22.81%} at low load level, mean and 5% DL Average-UPT loss of {-30.98%, -48.39%} at medium load level, mean and 5% DL Average-UPT loss of {-41.43%, -72.28%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {67.69%, 182.20%} at low load level, mean and 5% UL Average-UPT gain of {70.59%, 139.31%} at medium load level, mean and 5% UL Average-UPT gain of {75.42%, 127.60%} at high load level. +- In case of using SBFD Alt 2 and small packet size, (SBFD#1\_DUMacro\_FR2\_Sub#3, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.39%, -6.73%} at low load level, mean and 5% DL Average-UPT loss of {-0.70%, -11.41%} at medium load level, mean and 5% DL Average-UPT loss of {-2.52%, -12.91%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {87.97%, 281.48%} at low load level, mean and 5% UL Average-UPT gain of {73.84%, 227.27%} at medium load level, mean and 5% UL Average-UPT gain of {86.64%, 201.89%} at high load level. + - All results assumed 40dBm BS transmission power. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 3 and large packet size, (SBFD#1\_DUMacro\_FR2\_Sub#17, one source) + - Semi-static SBFD provides mean DL Average-UPT gain of 1.79% and 5% DL Average-UPT loss of -0.21% at low load level, mean DL Average-UPT gain of 0.40% and 5% DL Average-UPT loss of -3.25% at medium load level, mean and 5% DL Average-UPT loss of {-1.30%, -6.70%} at high load level. + - Semi-static SBFD provides mean UL Average-UPT gain of 0.14% and 5% UL Average-UPT loss of -1.49% at low load level, mean and 5% UL Average-UPT loss of {-7.88%, -30.04%} at medium load level, mean and 5% UL Average-UPT loss of {-20.38%, -32.17%} at high load level. + - With 40dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {1.94%, 0.08%} at low load level, mean DL Average-UPT gain of 0.66% and 5% DL Average-UPT loss of -0.57% at medium load level, mean and 5% DL Average-UPT loss of {-0.85%, -5.18%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-0.93%, -3.12%} at low load level, mean and 5% UL Average-UPT loss of {-12.70%, -40.85%} at medium load level, mean and 5% UL Average-UPT loss of {-30.32%, -43.32%} at high load level. + - With 30dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean DL Average-UPT gain of 1.64% and 5% DL Average-UPT loss of -0.51% at low load level, mean DL Average-UPT gain of 0.13% and 5% DL Average-UPT loss of -5.93% at medium load level, mean and 5% DL Average-UPT loss of {-1.75%, -8.22%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {1.21%, 0.15%} at low load level, mean and 5% UL Average-UPT loss of {-3.06%, -19.23%} at medium load level, mean and 5% UL Average-UPT loss of {-10.43%, -21.02%} at high load level. + - All results assumed piecewise linear noise figure model. + +**For Dense Urban Macro (FR2-1) in SBFD deployment case 1, if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is less than 98 dB, assuming SBFD antenna configuration option-2 (twice area and same TxRUs):** + +- In case of using SBFD Alt 4 and large packet size, (SBFD#1\_DUMacro\_FR2\_Sub#6, 3 sources) + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {1.48%, 2.17%} at low load level, mean and 5% DL Average-UPT gain of {1.65%, 0.70%} at medium load level, mean DL Average-UPT gain of 1.23% and 5% DL Average-UPT loss of -2.28% at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {8.88%, 159.27%} at low load level, mean UL Average-UPT loss of -31.13% and 5% UL Average-UPT gain of 127.28% at medium load level, mean and 5% UL Average-UPT loss of {-74.61%, -52.69%} at high load level. + - With 40dBm BS transmission power assumed by 3 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {1.66%, 2.94%} at low load level, mean and 5% DL Average-UPT gain of {2.00%, 2.83%} at medium load level, mean and 5% DL Average-UPT gain of {1.56%, 0.60%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {24.81%, 327.66%} at low load level, mean UL Average-UPT loss of -25.98% and 5% UL Average-UPT gain of 320.63% at medium load level, mean and 5% UL Average-UPT loss of {-86.40%, -28.91%} at high load level. + - With 30dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {1.31%, 1.39%} at low load level, mean DL Average-UPT gain of 1.30% and 5% DL Average-UPT loss of -1.43% at medium load level, mean DL Average-UPT gain of 0.90% and 5% DL Average-UPT loss of -5.16% at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-7.04%, -9.12%} at low load level, mean and 5% UL Average-UPT loss of {-36.28%, -66.06%} at medium load level, mean and 5% UL Average-UPT loss of {-62.81%, -76.47%} at high load level. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 4 and small packet size, (SBFD#1\_DUMacro\_FR2\_Sub#5, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {4.60%, 4.95%} at low load level, mean DL Average-UPT gain of 1.76% and 5% DL Average-UPT loss of -1.62% at medium load level, mean and 5% DL Average-UPT loss of {-0.62%, -10.72%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {47.36%, 143.55%} at low load level, mean UL Average-UPT loss of -12.79% and 5% UL Average-UPT gain of 511.72% at medium load level, mean and 5% UL Average-UPT loss of {-93.42%, -76.65%} at high load level. + - All results assumed 40dBm BS transmission power. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 3 and large packet size, (SBFD#1\_DUMacro\_FR2\_Sub#20, one source) + - Semi-static SBFD provides mean DL Average-UPT gain of 1.75% and 5% DL Average-UPT loss of -0.11% at low load level, mean DL Average-UPT gain of 0.33% and 5% DL Average-UPT loss of -3.11% at medium load level, mean and 5% DL Average-UPT loss of {-1.60%, -6.75%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-4.19%, -6.34%} at low load level, mean and 5% UL Average-UPT loss of {-25.45%, -60.23%} at medium load level, mean and 5% UL Average-UPT loss of {-48.14%, -64.61%} at high load level. + - With 40dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean DL Average-UPT gain of 1.86% and 5% DL Average-UPT loss of -0.07% at low load level, mean DL Average-UPT gain of 0.57% and 5% DL Average-UPT loss of + +- 1.19% at medium load level, mean and 5% DL Average-UPT loss of {-0.94%, -2.48%} at high load level. +- Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-6.89%, -9.53%} at low load level, mean and 5% UL Average-UPT loss of {-36.17%, -73.81%} at medium load level, mean and 5% UL Average-UPT loss of {-63.58%, -82.79%} at high load level. +- With 30dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean DL Average-UPT gain of 1.63% and 5% DL Average-UPT loss of -0.15% at low load level, mean DL Average-UPT gain of 0.09% and 5% DL Average-UPT loss of -5.03% at medium load level, mean and 5% DL Average-UPT loss of {-2.27%, -11.01%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-1.49%, -3.16%} at low load level, mean and 5% UL Average-UPT loss of {-14.73%, -46.66%} at medium load level, mean and 5% UL Average-UPT loss of {-32.70%, -46.43%} at high load level. +- All results assumed piecewise linear noise figure model. + +**For Dense Urban Macro (FR2-1) in SBFD deployment case 1, if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is equal to 98 dB, assuming SBFD antenna configuration option-2 (twice area and same TxRUs):** + +- In case of using SBFD Alt 4 and large packet size, (SBFD#1\_DUMacro\_FR2\_Sub#8, 4 sources) + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {1.33%, 1.71%} at low load level, mean DL Average-UPT gain of 1.60% and 5% DL Average-UPT loss of -1.26% at medium load level, mean DL Average-UPT gain of 1.36% and 5% DL Average-UPT loss of -5.34% at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {36.23%, 18.52%} at low load level, mean and 5% UL Average-UPT gain of {18.49%, 28.87%} at medium load level, mean UL Average-UPT loss of -17.88% and 5% UL Average-UPT gain of 10.78% at high load level. +- With 40dBm BS transmission power assumed by 3 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {3.56%, 2.90%} at low load level, mean and 5% DL Average-UPT gain of {2.75%, 3.60%} at medium load level, mean and 5% DL Average-UPT gain of {1.36%, 2.60%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {36.23%, 18.52%} at low load level, mean and 5% UL Average-UPT gain of {18.49%, 28.87%} at medium load level, mean UL Average-UPT loss of -17.88% and 5% UL Average-UPT gain of 10.78% at high load level. +- With 30dBm BS transmission power assumed by 2 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-1.62%, -2.14%} at low load level, mean and 5% DL Average-UPT loss of {-1.64%, -4.25%} at medium load level, mean and 5% DL Average-UPT loss of {-2.69%, -5.66%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {18.41%, 147.57%} at low load level, mean and 5% UL Average-UPT gain of {17.05%, 136.99%} at medium load level, mean and 5% UL Average-UPT gain of {16.99%, 211.48%} at high load level. +- With piecewise noise figure model assumed by 3 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {2.45%, 2.30%} at low load level, mean and 5% DL Average-UPT gain of {2.18%, 1.17%} at medium load level, mean DL Average-UPT gain of 1.48% and 5% DL Average-UPT loss of -1.69% at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {17.32%, 7.95%} at low load level, mean UL Average-UPT gain of 3.22% and 5% UL Average-UPT loss of -5.83% at medium load level, mean and 5% UL Average-UPT loss of {-21.92%, -13.28%} at high load level. + +- With flat noise figure model assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-4.58%, -5.84%} at low load level, mean and 5% DL Average-UPT loss of {-4.87%, -7.25%} at medium load level, mean and 5% DL Average-UPT loss of {-6.98%, -5.34%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {38.40%, 297.77%} at low load level, mean and 5% UL Average-UPT gain of {46.15%, 314.51%} at medium load level, mean and 5% UL Average-UPT gain of {59.95%, 460.29%} at high load level. +- In case of using SBFD Alt 4 and small packet size, (SBFD#1\_DUMacro\_FR2\_Sub#7, 2 sources) + - Semi-static SBFD provides mean DL Average-UPT gain of 3.81% and 5% DL Average-UPT loss of -13.68% at low load level, mean DL Average-UPT gain of 2.22% and 5% DL Average-UPT loss of -16.35% at medium load level, mean DL Average-UPT gain of 0.60% and 5% DL Average-UPT loss of -21.26% at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {45.18%, 133.83%} at low load level, mean and 5% UL Average-UPT gain of {46.98%, 2114.33%} at medium load level, mean and 5% UL Average-UPT gain of {40.03%, 113.85%} at high load level. +- With 40dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {4.69%, 5.07%} at low load level, mean and 5% DL Average-UPT gain of {2.57%, 1.27%} at medium load level, mean DL Average-UPT gain of 0.31% and 5% DL Average-UPT loss of -7.41% at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {57.78%, 202.15%} at low load level, mean and 5% UL Average-UPT gain of {59.09%, 4165.63%} at medium load level, mean and 5% UL Average-UPT gain of {38.85%, 96.07%} at high load level. +- With 30dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean DL Average-UPT gain of 2.92% and 5% DL Average-UPT loss of -32.44% at low load level, mean DL Average-UPT gain of 1.88% and 5% DL Average-UPT loss of -33.97% at medium load level, mean DL Average-UPT gain of 0.90% and 5% DL Average-UPT loss of -35.11% at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {32.58%, 65.51%} at low load level, mean and 5% UL Average-UPT gain of {34.88%, 63.03%} at medium load level, mean and 5% UL Average-UPT gain of {41.22%, 131.63%} at high load level. +- With piecewise noise figure model assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {4.69%, 5.07%} at low load level, mean and 5% DL Average-UPT gain of {2.57%, 1.27%} at medium load level, mean DL Average-UPT gain of 0.31% and 5% DL Average-UPT loss of -7.41% at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {57.78%, 202.15%} at low load level, mean and 5% UL Average-UPT gain of {59.09%, 4165.63%} at medium load level, mean and 5% UL Average-UPT gain of {38.85%, 96.07%} at high load level. +- With flat noise figure model assumed by 1 source, + - Semi-static SBFD provides mean DL Average-UPT gain of 2.92% and 5% DL Average-UPT loss of -32.44% at low load level, mean DL Average-UPT gain of 1.88% and 5% DL Average-UPT loss of -33.97% at medium load level, mean DL Average-UPT gain of 0.90% and 5% DL Average-UPT loss of -35.11% at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {32.58%, 65.51%} at low load level, mean and 5% UL Average-UPT gain of {34.88%, 63.03%} at medium load level, mean and 5% UL Average-UPT gain of {41.22%, 131.63%} at high load level. +- In case of using SBFD Alt 2 and large packet size, (SBFD#1\_DUMacro\_FR2\_Sub#10, 2 sources) + +- Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-21.90%, -22.48%} at low load level, mean and 5% DL Average-UPT loss of {-28.49%, -47.88%} at medium load level, mean and 5% DL Average-UPT loss of {-37.91%, -49.87%} at high load level. +- Semi-static SBFD provides mean and 5% UL Average-UPT gain of {79.47%, 75.86%} at low load level, mean and 5% UL Average-UPT gain of {96.75%, 149.84%} at medium load level, mean and 5% UL Average-UPT gain of {123.96%, 100.01%} at high load level. +- With 40dBm BS transmission power assumed by 2 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-18.93%, -14.01%} at low load level, mean and 5% DL Average-UPT loss of {-24.88%, -37.94%} at medium load level, mean and 5% DL Average-UPT loss of {-34.65%, -43.15%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {92.16%, 71.27%} at low load level, mean and 5% UL Average-UPT gain of {110.62%, 121.31%} at medium load level, mean and 5% UL Average-UPT gain of {108.92%, 83.83%} at high load level. +- With 30dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-21.90%, -22.69%} at low load level, mean and 5% DL Average-UPT loss of {-29.27%, -47.90%} at medium load level, mean and 5% DL Average-UPT loss of {-38.75%, -52.11%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {79.47%, 80.11%} at low load level, mean and 5% UL Average-UPT gain of {96.75%, 164.50%} at medium load level, mean and 5% UL Average-UPT gain of {123.96%, 236.80%} at high load level. +- All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 2 and small packet size, (SBFD#1\_DUMacro\_FR2\_Sub#9, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.39%, -6.73%} at low load level, mean and 5% DL Average-UPT loss of {-0.70%, -11.41%} at medium load level, mean and 5% DL Average-UPT loss of {-2.52%, -12.91%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {87.97%, 281.48%} at low load level, mean and 5% UL Average-UPT gain of {73.84%, 227.27%} at medium load level, mean and 5% UL Average-UPT gain of {86.64%, 201.89%} at high load level. +- All results assumed 40dBm BS transmission power. +- All results assumed piecewise linear noise figure model. + +**For Dense Urban Macro (FR2-1) in SBFD deployment case 1, if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is no less than 98 dB, assuming SBFD antenna configuration option-1 (same area and same TxRUs):** + +- In case of using SBFD Alt 4 and large packet size, (SBFD#1\_DUMacro\_FR2\_Sub#12, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-1.81%, -15.60%} at low load level, mean and 5% DL Average-UPT loss of {-11.70%, -15.54%} at medium load level, mean and 5% DL Average-UPT loss of {-17.11%, -13.65%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {23.93%, 13.43%} at low load level, mean and 5% UL Average-UPT gain of {7.54%, 27.84%} at medium load level, mean and 5% UL Average-UPT gain of {3.92%, 3.92%} at high load level. +- All results assumed 40dBm BS transmission power. +- All results assumed piecewise linear noise figure model. + +**For Dense Urban Macro (FR2-1) in SBFD deployment case 1, if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is no less than 98 dB, assuming SBFD antenna configuration option-3 (same area and half TxRUs):** + +- In case of using SBFD Alt 4 and large packet size, (SBFD#1\_DUMacro\_FR2\_Sub#13, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.79%, -12.42%} at low load level, mean and 5% DL Average-UPT loss of {-3.04%, -15.95%} at medium load level, mean and 5% DL Average-UPT loss of {-7.85%, -26.62%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-6.88%, -8.38%} at low load level, mean and 5% UL Average-UPT loss of {-27.86%, -53.69%} at medium load level, mean and 5% UL Average-UPT loss of {-49.83%, -64.22%} at high load level. + - With 40dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.25%, -9.45%} at low load level, mean and 5% DL Average-UPT loss of {-1.84%, -6.23%} at medium load level, mean and 5% DL Average-UPT loss of {-6.36%, -19.62%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-9.19%, -10.74%} at low load level, mean and 5% UL Average-UPT loss of {-38.73%, -63.49%} at medium load level, mean and 5% UL Average-UPT loss of {-67.05%, -79.95%} at high load level. + - With 30dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-1.32%, -15.39%} at low load level, mean and 5% DL Average-UPT loss of {-4.25%, -25.67%} at medium load level, mean and 5% DL Average-UPT loss of {-9.33%, -33.61%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-4.58%, -6.01%} at low load level, mean and 5% UL Average-UPT loss of {-17.00%, -43.88%} at medium load level, mean and 5% UL Average-UPT loss of {-32.60%, -48.50%} at high load level. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 2 and large packet size, (SBFD#1\_DUMacro\_FR2\_Sub#16, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-23.55%, -32.38%} at low load level, mean and 5% DL Average-UPT loss of {-32.80%, -56.47%} at medium load level, mean and 5% DL Average-UPT loss of {-44.61%, -64.38%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {72.46%, 71.84%} at low load level, mean and 5% UL Average-UPT gain of {80.46%, 139.90%} at medium load level, mean and 5% UL Average-UPT gain of {94.06%, 135.24%} at high load level. + - With 40dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-23.03%, -29.10%} at low load level, mean and 5% DL Average-UPT loss of {-31.51%, -52.80%} at medium load level, mean and 5% DL Average-UPT loss of {-43.18%, -62.44%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {70.36%, 70.65%} at low load level, mean and 5% UL Average-UPT gain of {71.61%, 129.90%} at medium load level, mean and 5% UL Average-UPT gain of {74.83%, 68.91%} at high load level. + - With 30dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-24.07%, -35.66%} at low load level, mean and 5% DL Average-UPT loss of {-34.08%, -60.13%} at medium load level, mean and 5% DL Average-UPT loss of {-46.05%, -66.31%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {74.56%, 73.03%} at low load level, mean and 5% UL Average-UPT gain of {89.31%, 149.90%} at medium load level, mean and 5% UL Average-UPT gain of {113.28%, 201.57%} at high load level. + +- All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 3 and large packet size, (SBFD#1\_DUMacro\_FR2\_Sub#18, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.37%, -14.23%} at low load level, mean and 5% DL Average-UPT loss of {-4.47%, -21.42%} at medium load level, mean and 5% DL Average-UPT loss of {-10.64%, -29.20%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-2.77%, -4.62%} at low load level, mean and 5% UL Average-UPT loss of {-12.73%, -38.10%} at medium load level, mean and 5% UL Average-UPT loss of {-27.17%, -38.49%} at high load level. +- With 40dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean DL Average-UPT gain of 0.48% and 5% DL Average-UPT loss of -10.81% at low load level, mean and 5% DL Average-UPT loss of {-2.92%, -11.51%} at medium load level, mean and 5% DL Average-UPT loss of {-8.90%, -21.97%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-3.94%, -6.46%} at low load level, mean and 5% UL Average-UPT loss of {-17.98%, -47.31%} at medium load level, mean and 5% UL Average-UPT loss of {-37.41%, -50.01%} at high load level. +- With 30dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-1.22%, -17.64%} at low load level, mean and 5% DL Average-UPT loss of {-6.03%, -31.33%} at medium load level, mean and 5% DL Average-UPT loss of {-12.38%, -36.42%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-1.61%, -2.77%} at low load level, mean and 5% UL Average-UPT loss of {-7.49%, -28.89%} at medium load level, mean and 5% UL Average-UPT loss of {-16.94%, -26.98%} at high load level. +- All results assumed piecewise linear noise figure model. + +**For Dense Urban Macro (FR2-1) in SBFD deployment case 1, if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is less than 98 dB, assuming SBFD antenna configuration option-3 (same area and half TxRUs):** + +- In case of using SBFD Alt 4 and large packet size, (SBFD#1\_DUMacro\_FR2\_Sub#19, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.81%, -11.82%} at low load level, mean and 5% DL Average-UPT loss of {-3.47%, -17.77%} at medium load level, mean and 5% DL Average-UPT loss of {-8.28%, -27.81%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-15.79%, -20.54%} at low load level, mean and 5% UL Average-UPT loss of {-59.80%, -83.19%} at medium load level, mean and 5% UL Average-UPT loss of {-81.69%, -89.47%} at high load level. +- With 40dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.29%, -8.67%} at low load level, mean and 5% DL Average-UPT loss of {-2.21%, -8.04%} at medium load level, mean and 5% DL Average-UPT loss of {-6.53%, -20.54%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-21.45%, -27.46%} at low load level, mean and 5% UL Average-UPT loss of {-77.57%, -97.33%} at medium load level, mean and 5% UL Average-UPT loss of {-95.48%, -99.73%} at high load level. +- With 30dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-1.33%, -14.96%} at low load level, mean and 5% DL Average-UPT loss of {-4.73%, -27.51%} at medium load level, mean and 5% DL Average-UPT loss of {-10.03%, -35.08%} at high load level. + +- Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-10.14%, -13.62%} at low load level, mean and 5% UL Average-UPT loss of {-42.02%, -69.06%} at medium load level, mean and 5% UL Average-UPT loss of {-67.91%, -79.22%} at high load level. +- All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 2 and large packet size, (SBFD#1\_DUMacro\_FR2\_Sub#21, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.43%, -13.54%} at low load level, mean and 5% DL Average-UPT loss of {-6.18%, -31.25%} at medium load level, mean and 5% DL Average-UPT loss of {-10.96%, -28.15%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-7.08%, -9.60%} at low load level, mean and 5% UL Average-UPT loss of {-19.47%, -51.65%} at medium load level, mean and 5% UL Average-UPT loss of {-53.26%, -68.67%} at high load level. +- With 40dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean DL Average-UPT gain of 0.42% and 5% DL Average-UPT loss of -10.44% at low load level , mean and 5% DL Average-UPT loss of {-9.11%, -20.62%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-9.83%, -12.97%} at low load level, mean and 5% UL Average-UPT loss of {-68.26%, -88.15%} at high load level. +- With 30dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-1.27%, -16.64%} at low load level, mean and 5% DL Average-UPT loss of {-6.18%, -31.25%} at medium load level, mean and 5% DL Average-UPT loss of {-12.80%, -35.67%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-4.33%, -6.22%} at low load level, mean and 5% UL Average-UPT loss of {-19.47%, -51.65%} at medium load level, mean and 5% UL Average-UPT loss of {-38.26%, -49.19%} at high load level. +- All results assumed piecewise linear noise figure model. + +### 7.3.1.3 SBFD Deployment Case 3-2 (FR1) + +#### 7.3.1.3.1 2-layer Scenario B (FR1) + +3 sources provided the SLS evaluation results for 2-layer Scenario B (FR1) in SBFD Deployment Case 3-2. The evaluation results are categorized into 12 sub-cases as in Table 7.3.1.3.1-1~ Table 7.3.1.3.1-2 based on the different key assumptions. Each sub-case is based on one combination of key assumptions. + +**Table 7.3.1.3.1-1: Sub-cases for 2-layer scenario B (FR1) with Twice area&same TxRUs in SBFD deployment Case 3-2.** + +| | | SBFD#3-
2_Scenario
B_FR1_Su
b#1 | SBFD#3-
2_Scenario
B_FR1_Su
b#2 | SBFD#3-
2_Scenario
B_FR1_Su
b#3 | SBFD#3-
2_Scenario
B_FR1_Su
b#4 | SBFD#3-
2_Scenario
B_FR1_Su
b#9 | SBFD#3-
2_Scenario
B_FR1_Su
b#10 | +|------------------------------------------|------------------------------------------|------------------------------------------|------------------------------------------|------------------------------------------|------------------------------------------|------------------------------------------|-------------------------------------------| +| SBFD
slot
configu
ration | Alt-4: {DDDSU}
vs. {XXXXX} | O | O | | | | | +| | Alt-2: {DDDSU}
vs. {XXXXU} | | | O | O | | | +| | Alt-1: {DDDSU}
vs. {DXXXU} | | | | | | | +| | Alt-3: {DDSUU}
vs. {XXXXU} | | | | | O | O | +| SBFD
antenn
a
configu
ration | Twice area&same
TxRUs (Option 2) | O | O | O | O | O | O | +| | Same area&same
TxRUs (Option 1) | | | | | | | +| | Same area&half
TxRUs (Option 3) | | | | | | | +| Packet
Size | Option 1: DL:
4Kbytes, UL:
1Kbytes | O | | O | | O | | + +| | | | | | | | | +|---------|------------------------------------------|------------------------|------------------------------|------------------------|------------------------------|-----------------|-----------------| +| | Option 2: DL: 0.5Mbytes, UL: 0.125Mbytes | | O | | O | | O | +| Sources | | 2 sources ([18], [32]) | 3 sources ([18], [28], [32]) | 2 sources ([18], [32]) | 3 sources ([18], [28], [32]) | 1 source ([18]) | 1 source ([18]) | + +**Table 7.3.1.3.1-2: Sub-cases for 2-layer scenario B (FR1) with Same area&half TxRUs in SBFD deployment Case 3-2.** + +| | | SBFD#3-2_Scenario B_FR1_Su b#5 | SBFD#3-2_Scenario B_FR1_Su b#6 | SBFD#3-2_Scenario B_FR1_Su b#7 | SBFD#3-2_Scenario B_FR1_Su b#8 | SBFD#3-2_Scenario B_FR1_Su b#11 | SBFD#3-2_Scenario B_FR1_Su b#12 | +|----------------------------|------------------------------------------|--------------------------------|--------------------------------|--------------------------------|--------------------------------|---------------------------------|---------------------------------| +| SBFD slot configuration | Alt-4: {DDDSU} vs. {XXXXX} | O | O | | | | | +| | Alt-2: {DDDSU} vs. {XXXUX} | | | O | O | | | +| | Alt-1: {DDDSU} vs. {DXXXU} | | | | | | | +| | Alt-3: {DDSUU} vs. {XXXUX} | | | | | O | O | +| SBFD antenna configuration | Twice area&same TxRUs (Option 2) | | | | | | | +| | Same area&same TxRUs (Option 1) | | | | | | | +| | Same area&half TxRUs (Option 3) | O | O | O | O | O | O | +| Packet Size | Option 1: DL: 4Kbytes, UL: 1Kbytes | O | | O | | O | | +| | Option 2: DL: 0.5Mbytes, UL: 0.125Mbytes | | O | | O | | O | +| Sources | | 1 source ([18]) | 1 source ([18]) | 1 source ([18]) | 1 source ([18]) | 1 source ([18]) | 1 source ([18]) | + +#### 7.3.1.3.1.1 + +#### Summary of the observations + +**For the indoor layer of 2-layer Scenario B (FR1) in SBFD deployment case 3-2, assuming SBFD antenna configuration option-2 (twice area and same TxRUs):** + +- In case of using SBFD Alt 4 and large packet size, (SBFD#3-2\_ScenarioB\_FR1\_Sub#2, 3 sources) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-5.38%, -10.49%} at low load level, mean and 5% DL Average-UPT loss of {-7.29%, -11.87%} at medium load level, mean and 5% DL Average-UPT loss of {-9.20%, -12.30%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {3.90%, 17.83%} at low load level, mean and 5% UL Average-UPT gain of {3.38%, 68.34%} at medium load level, mean and 5% UL Average-UPT gain of {14.78%, 71.07%} at high load level. +- With 49dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {1.95%, 3.08%} at low load level, mean and 5% DL Average-UPT gain of {7.70%, 5.04%} at medium load level, mean and 5% DL Average-UPT gain of {6.27%, 5.13%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {3.90%, 33.80%} at low load level, mean and 5% UL Average-UPT gain of {3.38%, 95.10%} at medium load level, mean and 5% UL Average-UPT gain of {14.78%, 104.80%} at high load level. +- With 53dBm BS transmission power assumed by 2 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-13.83%, -17.76%} at low load level, mean and 5% DL Average-UPT loss of {-20.93%, -27.00%} at medium load level, mean and 5% DL Average-UPT loss of {-32.27%, -44.06%} at high load level. + +- Semi-static SBFD provides mean UL Average-UPT gain of 20.99% and 5% UL Average-UPT loss of -3.91% at low load level, mean UL Average-UPT gain of 13.68% and 5% UL Average-UPT loss of -7.48% at medium load level, mean UL Average-UPT gain of 2.02% and 5% UL Average-UPT loss of -10.77% at high load level. +- All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 4 and small packet size, (SBFD#3-2\_ScenarioB\_FR1\_Sub#1, 2 sources) + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {5.69%, 6.87%} at low load level, mean and 5% DL Average-UPT gain of {5.29%, 3.42%} at medium load level, mean and 5% DL Average-UPT loss of {-2.27%, -50.93%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {91.80%, 93.70%} at low load level, mean and 5% UL Average-UPT gain of {89.00%, 26.42%} at medium load level, mean UL Average-UPT gain of 78.10% and 5% UL Average-UPT loss of -37.25% at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 2 and large packet size, (SBFD#3-2\_ScenarioB\_FR1\_Sub#4, 3 sources) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-24.90%, -28.72%} at low load level, mean and 5% DL Average-UPT loss of {-28.31%, -32.62%} at medium load level, mean and 5% DL Average-UPT loss of {-36.34%, -51.41%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {91.29%, 41.77%} at low load level, mean and 5% UL Average-UPT gain of {116.68%, 106.71%} at medium load level, mean and 5% UL Average-UPT gain of {123.40%, 174.07%} at high load level. + - With 49dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-24.90%, -24.40%} at low load level, mean and 5% DL Average-UPT loss of {-24.30%, -29.50%} at medium load level, mean and 5% DL Average-UPT loss of {-31.98%, -33.13%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {64.90%, 23.40%} at low load level, mean and 5% UL Average-UPT gain of {69.90%, 63.80%} at medium load level, mean and 5% UL Average-UPT gain of {123.40%, 134.00%} at high load level. + - With 53dBm BS transmission power assumed by 2 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-24.94%, -29.07%} at low load level, mean and 5% DL Average-UPT loss of {-32.95%, -38.72%} at medium load level, mean and 5% DL Average-UPT loss of {-46.67%, -64.24%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {99.22%, 67.37%} at low load level, mean and 5% UL Average-UPT gain of {118.06%, 126.09%} at medium load level, mean and 5% UL Average-UPT gain of {152.63%, 349.09%} at high load level. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 2 and small packet size, (SBFD#3-2\_ScenarioB\_FR1\_Sub#3, 2 sources) + - Semi-static SBFD provides mean DL Average-UPT gain of 0.43% and 5% DL Average-UPT loss of -0.01% at low load level, mean and 5% DL Average-UPT loss of {-1.58%, -7.82%} at medium load level, mean and 5% DL Average-UPT loss of {-13.98%, -80.99%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {99.80%, 104.37%} at low load level, mean and 5% UL Average-UPT gain of {102.60%, 91.69%} at medium load level, mean and 5% UL Average-UPT gain of {110.12%, 218.36%} at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. + +- In case of using SBFD Alt 3 and large packet size, (SBFD#3-2\_ScenarioB\_FR1\_Sub#10, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-29.99%, -34.28%} at low load level, mean and 5% DL Average-UPT loss of {-45.57%, -53.32%} at medium load level, mean and 5% DL Average-UPT loss of {-66.40%, -82.87%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {106.57%, 107.83%} at low load level, mean and 5% UL Average-UPT gain of {136.02%, 121.56%} at medium load level, mean and 5% UL Average-UPT gain of {214.26%, 595.02%} at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 3 and small packet size, (SBFD#3-2\_ScenarioB\_FR1\_Sub#9, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {0.01%, 0.05%} at low load level, mean and 5% DL Average-UPT loss of {-3.43%, -12.98%} at medium load level, mean and 5% DL Average-UPT loss of {-20.55%, -90.02%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {97.92%, 97.44%} at low load level, mean and 5% UL Average-UPT gain of {95.33%, 64.08%} at medium load level, mean and 5% UL Average-UPT gain of {112.45%, 390.09%} at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. + +**For the indoor layer of 2-layer Scenario B (FR1) in SBFD deployment case 3-2, assuming SBFD antenna configuration option-3 (same area and half TxRUs):** + +- In case of using SBFD Alt 4 and large packet size, (SBFD#3-2\_ScenarioB\_FR1\_Sub#6, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-32.38%, -39.86%} at low load level, mean and 5% DL Average-UPT loss of {-66.56%, -82.02%} at medium load level, mean and 5% DL Average-UPT loss of {-83.49%, -93.01%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-28.38%, -46.89%} at low load level, mean and 5% UL Average-UPT loss of {-62.19%, -95.47%} at medium load level, mean and 5% UL Average-UPT loss of {-75.57%, -96.98%} at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 4 and small packet size, (SBFD#3-2\_ScenarioB\_FR1\_Sub#5, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.01%, -0.57%} at low load level, mean and 5% DL Average-UPT loss of {-11.38%, -43.00%} at medium load level, mean and 5% DL Average-UPT loss of {-31.72%, -98.56%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {80.17%, 68.09%} at low load level, mean UL Average-UPT gain of 57.19% and 5% UL Average-UPT loss of -81.13% at medium load level, mean UL Average-UPT gain of 23.14% and 5% UL Average-UPT loss of -99.84% at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 4 and large packet size, (SBFD#3-2\_ScenarioB\_FR1\_Sub#8, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-35.08%, -42.90%} at low load level, mean and 5% DL Average-UPT loss of {-67.59%, -82.61%} at medium load level, mean and 5% DL Average-UPT loss of {-83.50%, -92.95%} at high load level. + +- Semi-static SBFD provides mean and 5% UL Average-UPT gain of {75.31%, 69.76%} at low load level, mean and 5% UL Average-UPT gain of {82.42%, 50.07%} at medium load level, mean and 5% UL Average-UPT gain of {108.56%, 249.80%} at high load level. +- All results assumed 53dBm BS transmission power. +- All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 2 and small packet size, (SBFD#3-2\_ScenarioB\_FR1\_Sub#7, one source) + - Semi-static SBFD provides no change on mean DL Average-UPT and mean DL Average-UPT loss of -0.26% at low load level, mean and 5% DL Average-UPT loss of {-13.54%, -53.24%} at medium load level, mean and 5% DL Average-UPT loss of {-33.96%, -98.78%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {96.59%, 91.54%} at low load level, mean and 5% UL Average-UPT gain of {91.33%, 60.84%} at medium load level, mean and 5% UL Average-UPT gain of {100.19%, 361.46%} at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 3 and large packet size, (SBFD#3-2\_ScenarioB\_FR1\_Sub#12, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-40.55%, -49.05%} at low load level, mean and 5% DL Average-UPT loss of {-75.09%, -88.96%} at medium load level, mean and 5% DL Average-UPT loss of {-86.87%, -94.10%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {90.35%, 84.63%} at low load level, mean and 5% UL Average-UPT gain of {101.55%, 69.72%} at medium load level, mean and 5% UL Average-UPT gain of {139.85%, 321.99%} at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 3 and small packet size, (SBFD#3-2\_ScenarioB\_FR1\_Sub#11, one source) + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.05%, -0.15%} at low load level, mean and 5% DL Average-UPT loss of {-17.79%, -64.68%} at medium load level, mean and 5% DL Average-UPT loss of {-37.35%, -99.25%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {97.31%, 91.21%} at low load level, mean and 5% UL Average-UPT gain of {93.16%, 62.62%} at medium load level, mean and 5% UL Average-UPT gain of {105.90%, 379.10%} at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. + +### 7.3.1.4 SBFD Deployment Case 4 (FR1) + +#### 7.3.1.4.1 Urban Macro (0% grid shift) + +4 sources provided the SLS evaluation results for Urban Macro (FR1) with 0% grid shift in SBFD Deployment Case 4. The evaluation results are categorized into 13 sub-cases as in Table 7.3.1.4.1-1~Table 7.3.1.4.1-5 based on the different key assumptions. Each sub-case is based on one combination of key assumptions. + +**Table 7.3.1.4.1-1: Sub-cases for urban macro (FR1) with 0% grid shift with no less than 93dB inter-sector isolation, no less than 93dB adjacent-channel isolation, and Twice area&same TxRUs in SBFD deployment Case 4.** + +| | | SBFD#4_UMA_FR1
_0%_Sub#1 | SBFD#4_UMA_FR1
_0%_Sub#2 | SBFD#4_UMA_FR1
_0%_Sub#3 | +|--------------------------------------------|---------------|-----------------------------|-----------------------------|-----------------------------| +| Co-site co-channel:
Spatial isolation + | Opt 1: ≥ 93dB | ○ | ○ | ○ | +| | Opt 2: < 93dB | | | | + +| | | | | | +|------------------------------------------------------------------|------------------------------------------|-----------------|------------------------------|------------------------------| +| digital isolation
Co-site adjacent-channel: Spatial isolation | Opt 3: 93dB | | | | +| | Opt 1: >= 93dB | O | O | O | +| | Opt 2: < 93dB | | | | +| | Opt 3: 93dB | | | | +| SBFD slot configuration | Alt-4: {DDDSU} vs. {XXXXX} | O | O | | +| | Alt-2: {DDDSU} vs. {XXXU} | | | O | +| | Alt-1: {DDDSU} vs. {DXXXU} | | | | +| | Alt-3: {DDSUU} vs. {XXXU} | | | | +| SBFD antenna configuration | Twice area&same TxRUs (Option 2) | O | O | O | +| | Same area&same TxRUs (Option 1) | | | | +| | Same area&half TxRUs (Option 3) | | | | +| Packet Size | Option 1: DL: 4Kbytes, UL: 1Kbytes | O | | | +| | Option 2: DL: 0.5Mbytes, UL: 0.125Mbytes | | O | O | +| Sources | | 1 source ([26]) | 3 sources ([18], [26], [28]) | 3 sources ([18], [22], [28]) | + +Table 7.3.1.4.1-2: Sub-cases for urban macro (FR1) with 0% grid shift with less than 93dB inter-sector isolation, less than 93dB adjacent-channel isolation, and Twice area&same TxRUs in SBFD deployment Case 4. + +| | | SBFD#4_UMA_FR1_0%_Sub#4 | SBFD#4_UMA_FR1_0%_Sub#5 | SBFD#4_UMA_FR1_0%_Sub#12 | +|-----------------------------------------------------------|------------------------------------------|-------------------------|-------------------------|--------------------------| +| Co-site co-channel: Spatial isolation + digital isolation | Opt 1: >= 93dB | | | | +| | Opt 2: < 93dB | O | O | O | +| | Opt 3: 93dB | | | | +| Co-site adjacent-channel: Spatial isolation | Opt 1: >= 93dB | | | | +| | Opt 2: < 93dB | O | O | O | +| | Opt 3: 93dB | | | | +| SBFD slot configuration | Alt-4: {DDDSU} vs. {XXXXX} | O | | | +| | Alt-2: {DDDSU} vs. {XXXU} | | O | | +| | Alt-1: {DDDSU} vs. {DXXXU} | | | | +| | Alt-3: {DDSUU} vs. {XXXU} | | | O | +| SBFD antenna configuration | Twice area&same TxRUs (Option 2) | O | O | O | +| | Same area&same TxRUs (Option 1) | | | | +| | Same area&half TxRUs (Option 3) | | | | +| Packet Size | Option 1: DL: 4Kbytes, UL: 1Kbytes | | | | +| | Option 2: DL: 0.5Mbytes, UL: 0.125Mbytes | O | O | O | +| Sources | | 1 source ([18]) | 1 source ([18]) | 1 source ([18]) | + +Table 7.3.1.4.1-3: Sub-cases for urban macro (FR1) with 0% grid shift with 93dB inter-sector isolation, 93dB adjacent-channel isolation, and Twice area&same TxRUs in SBFD deployment Case 4. + +| | | SBFD#4_UMA_FR1_0%_Sub#6 | SBFD#4_UMA_FR1_0%_Sub#7 | +|-----------------------------------------------------------|----------------|-------------------------|-------------------------| +| Co-site co-channel: Spatial isolation + digital isolation | Opt 1: >= 93dB | | | +| | Opt 2: < 93dB | | | +| | Opt 3: 93dB | O | O | +| Co-site adjacent-channel: Spatial isolation | Opt 1: >= 93dB | | | +| | Opt 2: < 93dB | | | +| | Opt 3: 93dB | O | O | + +| | | | | +|----------------------------|------------------------------------------|------------------------|------------------------| +| SBFD slot configuration | Alt-4: {DDDSU} vs. {XXXXX} | O | | +| | Alt-2: {DDDSU} vs. {XXXXU} | | O | +| | Alt-1: {DDDSU} vs. {DXXXU} | | | +| | Alt-3: {DDSUU} vs. {XXXXU} | | | +| SBFD antenna configuration | Twice area&same TxRUs (Option 2) | O | O | +| | Same area&same TxRUs (Option 1) | | | +| | Same area&half TxRUs (Option 3) | | | +| Packet Size | Option 1: DL: 4Kbytes, UL: 1Kbytes | | | +| | Option 2: DL: 0.5Mbytes, UL: 0.125Mbytes | O | O | +| Sources | | 2 sources ([18], [28]) | 2 sources ([18], [28]) | + +**Table 7.3.1.4.1-4: Sub-cases for urban macro (FR1) with 0% grid shift with no less than 93dB inter-sector isolation, no less than 93dB adjacent-channel isolation, and Same area&half TxRUs in SBFD deployment Case 4.** + +| | | SBFD#4_UMA_FR1_0%_Sub#8 | SBFD#4_UMA_FR1_0%_Sub#9 | +|-----------------------------------------------------------|------------------------------------------|-------------------------|-------------------------| +| Co-site co-channel: Spatial isolation + digital isolation | Opt 1:>= 93dB | O | O | +| | Opt 2: < 93dB | | | +| | Opt 3: 93dB | | | +| Co-site adjacent-channel: Spatial isolation | Opt 1:>= 93dB | O | O | +| | Opt 2: < 93dB | | | +| | Opt 3: 93dB | | | +| SBFD slot configuration | Alt-4: {DDDSU} vs. {XXXXX} | O | | +| | Alt-2: {DDDSU} vs. {XXXXU} | | O | +| | Alt-1: {DDDSU} vs. {DXXXU} | | | +| | Alt-3: {DDSUU} vs. {XXXXU} | | | +| SBFD antenna configuration | Twice area&same TxRUs (Option 2) | | | +| | Same area&same TxRUs (Option 1) | | | +| | Same area&half TxRUs (Option 3) | O | O | +| Packet Size | Option 1: DL: 4Kbytes, UL: 1Kbytes | | | +| | Option 2: DL: 0.5Mbytes, UL: 0.125Mbytes | O | O | +| Sources | | 1 source ([18]) | 1 source ([18]) | + +**Table 7.3.1.4.1-5: Sub-cases for urban macro (FR1) with 0% grid shift with less than 93dB inter-sector isolation, less than 93dB adjacent-channel isolation, and Same area&half TxRUs in SBFD deployment Case 4.** + +| | | SBFD#4_UMA_FR1_0%_Sub#10 | SBFD#4_UMA_FR1_0%_Sub#11 | SBFD#4_UMA_FR1_0%_Sub#13 | +|-----------------------------------------------------------|----------------------------|--------------------------|--------------------------|--------------------------| +| Co-site co-channel: Spatial isolation + digital isolation | Opt 1:>= 93dB | | | | +| | Opt 2: < 93dB | O | O | O | +| | Opt 3: 93dB | | | | +| Co-site adjacent-channel: Spatial isolation | Opt 1:>= 93dB | | | | +| | Opt 2: < 93dB | O | O | O | +| | Opt 3: 93dB | | | | +| SBFD slot configuration | Alt-4: {DDDSU} vs. {XXXXX} | O | | | +| | Alt-2: {DDDSU} vs. {XXXXU} | | O | | + +| | | | | | +|----------------------------|------------------------------------------|-----------------|-----------------|-----------------| +| | Alt-1: {DDDSU} vs. {DXXXU} | | | | +| | Alt-3: {DDSUU} vs. {XXXUU} | | | ○ | +| SBFD antenna configuration | Twice area&same TxRUs (Option 2) | | | | +| | Same area&same TxRUs (Option 1) | | | | +| | Same area&half TxRUs (Option 3) | ○ | ○ | ○ | +| Packet Size | Option 1: DL: 4Kbytes, UL: 1Kbytes | | | | +| | Option 2: DL: 0.5Mbytes, UL: 0.125Mbytes | ○ | ○ | ○ | +| Sources | | 1 source ([18]) | 1 source ([18]) | 1 source ([18]) | + +#### 7.3.1.4.1.1 Summary of the observations + +**For Urban Macro (FR1) with 0% grid shift in SBFD deployment case 4, if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is no less than 93 dB and spatial isolation for co-site adjacent-channel CLI is no less than 93dB, assuming SBFD antenna configuration option-2 (twice area and same TxRUs):** + +- In case of using SBFD Alt 4 and small packet size, (SBFD#4\_UMA\_FR1\_0%\_Sub#1, one source) + - For operator 1 (Legacy TDD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-1.41%, -8.11%} at low load level, mean and 5% DL Average-UPT loss of {-2.80%, -32.53%} at medium load level, mean and 5% DL Average-UPT loss of {-4.72%, -57.91%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-3.96%, -72.64%} at low load level, mean and 5% UL Average-UPT loss of {-9.29%, -99.91%} at medium load level, mean and 5% UL Average-UPT loss of {-12.25%, -100.00%} at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed 5dBs flat noise figure model. + - For operator 2 (SBFD operator): + - Semi-static SBFD provides mean DL Average-UPT gain of 6.76% and 5% DL Average-UPT loss of -12.25% at low load level, mean DL Average-UPT gain of 4.99% and 5% DL Average-UPT loss of -33.75% at medium load level, mean DL Average-UPT gain of 3.50% and 5% DL Average-UPT loss of -52.59% at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {154.62%, 24.88%} at low load level, mean UL Average-UPT gain of 136.82% and 5% UL Average-UPT loss of -51.79% at medium load level, mean UL Average-UPT gain of 126.52% and 5% UL Average-UPT loss of -99.29% at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed 5dBs flat noise figure model. +- In case of using SBFD Alt 4 and large packet size, (SBFD#4\_UMA\_FR1\_0%\_Sub#2, 3 sources) + - For operator 1 (Legacy TDD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-6.46%, -29.43%} at low load level, mean and 5% DL Average-UPT loss of {-6.73%, -39.73%} at medium load level, mean and 5% DL Average-UPT loss of {-5.22%, -53.81%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-16.16%, -16.18%} at low load level, mean UL Average-UPT loss of -24.42% and no change on 5% UL Average-UPT at medium load level, mean UL Average-UPT loss of -27.10% and no change on 5% UL Average-UPT at high load level. + +- With 49dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.28%, -0.25%} at low load level, mean and 5% DL Average-UPT loss of {-3.27%, -4.47%} at medium load level, mean and 5% DL Average-UPT loss of {-4.36%, -7.14%} at high load level. + - Semi-static SBFD provides no change on mean UL Average-UPT and 5%UL Average-UPT loss of -0.92% at low load level, mean UL Average-UPT loss of -0.14% and no change on 5% UL Average-UPT at medium load level, mean UL Average-UPT loss of -0.27% and no change on 5% UL Average-UPT at high load level. +- With 53dBm BS transmission power assumed by 2 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-12.31%, -56.62%} at low load level, mean and 5% DL Average-UPT loss of {-9.95%, -70.08%} at medium load level, mean and 5% DL Average-UPT loss of {-5.91%, -98.83%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-17.45%, -31.44%} at low load level, mean UL Average-UPT loss of -28.31% and no change on 5% UL Average-UPT at medium load level, mean UL Average-UPT loss of -31.18% and no change on 5% UL Average-UPT at high load level. +- With piecewise noise figure model assumed by 2 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.44%, -1.25%} at low load level, mean and 5% DL Average-UPT loss of {-3.39%, -6.93%} at medium load level, mean and 5% DL Average-UPT loss of {-4.45%, -7.97%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-7.43%, -16.18%} at low load level, mean and 5% UL Average-UPT loss of {-30.66%, -46.23%} at medium load level, mean and 5% UL Average-UPT loss of {-39.94%, -49.99%} at high load level. +- With flat noise figure model assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-14.30%, -59.48%} at low load level, mean and 5% DL Average-UPT loss of {-12.19%, -72.78%} at medium load level, mean and 5% DL Average-UPT loss of {-9.88%, -99.28%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-24.30%, -50.00%} at low load level, mean UL Average-UPT loss of -24.42% and no change on 5% UL Average-UPT at medium load level, mean UL Average-UPT loss of -27.10% and no change on 5% UL Average-UPT at high load level. +- For operator 2 (SBFD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-11.54%, -39.64%} at low load level, mean and 5% DL Average-UPT loss of {-13.46%, -50.44%} at medium load level, mean and 5% DL Average-UPT loss of {-13.37%, -68.58%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {21.09%, 47.60%} at low load level, mean UL Average-UPT gain of 18.52% and no change on 5% UL Average-UPT at medium load level, mean UL Average-UPT gain of 3.27% and 5% UL Average-UPT loss of -19.36% at high load level. +- With 49dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {1.73%, 13.28%} at low load level, mean DL Average-UPT loss of -0.59% and 5% DL Average-UPT gain of 0.70% at medium load level, mean and 5% DL Average-UPT loss of {-5.89%, -9.82%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {19.86%, 133.94%} at low load level, mean and 5% UL Average-UPT gain of {5.54%, 59.70%} at medium load level, mean and 5% UL Average-UPT loss of {-18.22%, -38.71%} at high load level. +- With 53dBm BS transmission power assumed by 2 sources, + +- Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-20.14%, -72.69%} at low load level, mean and 5% DL Average-UPT loss of {-16.12%, -78.74%} at medium load level, mean and 5% DL Average-UPT loss of {-14.72%, -100.00%} at high load level. +- Semi-static SBFD provides mean UL Average-UPT gain of 22.32% and no change on 5% UL Average-UPT at low load level, mean UL Average-UPT gain of 31.50% and no change on 5% UL Average-UPT at medium load level, mean UL Average-UPT gain of 24.75% and no change on 5% UL Average-UPT at high load level. +- With piecewise noise figure model assumed by 2 sources, + - Semi-static SBFD provides mean DL Average-UPT loss of -0.60% and 5% DL Average-UPT gain of 3.34% at low load level, mean and 5% DL Average-UPT loss of {-5.70%, -10.72%} at medium load level, mean and 5% DL Average-UPT loss of {-12.29%, -23.48%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {3.50%, 114.57%} at low load level, mean and 5% UL Average-UPT loss of {-36.04%, -18.46%} at medium load level, mean and 5% UL Average-UPT loss of {-55.59%, -69.36%} at high load level. +- With flat noise figure model assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-21.94%, -73.15%} at low load level, mean and 5% DL Average-UPT loss of {-19.03%, -78.79%} at medium load level, mean and 5% DL Average-UPT loss of {-13.37%, -100.00%} at high load level. + - Semi-static SBFD provides mean UL Average-UPT gain of 34.56% and 5% UL Average-UPT loss of -50.00% at low load level, mean UL Average-UPT gain of 37.20% and no change on 5% UL Average-UPT at medium load level, mean UL Average-UPT gain of 34.05% and no change on 5% UL Average-UPT at high load level. +- In case of using SBFD Alt 2 and large packet size, (SBFD#4\_UMA\_FR1\_0%\_Sub#3, 3 sources) + - For operator 1 (Legacy TDD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.45%, -1.52%} at low load level, mean and 5% DL Average-UPT loss of {-2.12%, -2.25%} at medium load level, mean and 5% DL Average-UPT loss of {-3.39%, -4.86%} at high load level. + - Semi-static SBFD provides mean UL Average-UPT loss of -0.01% and 5% UL Average-UPT gain of 0.07% at low load level, mean and 5% UL Average-UPT gain of {0.04%, 0.10%} at medium load level, mean and 5% UL Average-UPT gain of {0.13%, 2.08%} at high load level. + - With 49dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.46%, -1.07%} at low load level, mean and 5% DL Average-UPT loss of {-3.27%, -5.17%} at medium load level, mean and 5% DL Average-UPT loss of {-5.21%, -5.63%} at high load level. + - Semi-static SBFD provides no change on mean and 5% UL Average-UPT at all load levels. + - With 53dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.43%, -1.98%} at low load level, mean DL Average-UPT loss of -0.97% and 5% DL Average-UPT gain of 0.67% at medium load level, mean and 5% DL Average-UPT loss of {-1.57%, -4.09%} at high load level. + - Semi-static SBFD provides mean UL Average-UPT loss of -0.01% and 5% UL Average-UPT gain of 0.15% at low load level, mean and 5% UL Average-UPT gain of {0.09%, 0.19%} at medium load level, mean and 5% UL Average-UPT gain of {0.26%, 4.16%} at high load level. + - All results assumed piecewise linear noise figure model. + - For operator 2 (SBFD operator): + +- Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-22.97%, -27.07%} at low load level, mean and 5% DL Average-UPT loss of {-21.22%, -52.53%} at medium load level, mean and 5% DL Average-UPT loss of {-26.20%, -65.36%} at high load level. +- Semi-static SBFD provides mean and 5% UL Average-UPT gain of {59.89%, 168.31%} at low load level, mean and 5% UL Average-UPT gain of {26.32%, 37.37%} at medium load level, mean and 5% UL Average-UPT gain of {23.29%, 24.69%} at high load level. +- With 49dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-23.57%, -19.09%} at low load level, mean and 5% DL Average-UPT loss of {-21.22%, -24.50%} at medium load level, mean and 5% DL Average-UPT loss of {-26.20%, -30.61%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {117.84%, 212.84%} at low load level, mean and 5% UL Average-UPT gain of {110.49%, 71.64%} at medium load level, mean and 5% UL Average-UPT gain of {45.59%, 45.16%} at high load level. +- With 53dBm BS transmission power assumed by 2 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-18.43%, -46.70%} at low load level, mean and 5% DL Average-UPT loss of {-25.83%, -59.31%} at medium load level, mean and 5% DL Average-UPT loss of {-34.38%, -66.73%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {36.33%, 123.77%} at low load level, mean and 5% UL Average-UPT gain of {19.56%, 3.10%} at medium load level, mean and 5% UL Average-UPT gain of {18.03%, 4.23%} at high load level. +- With piecewise noise figure model assumed by 2 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-23.27%, -23.08%} at low load level, mean and 5% DL Average-UPT loss of {-29.59%, -38.52%} at medium load level, mean and 5% DL Average-UPT loss of {-40.53%, -49.36%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {88.87%, 168.31%} at low load level, mean and 5% UL Average-UPT gain of {68.41%, 37.37%} at medium load level, mean and 5% UL Average-UPT gain of {34.44%, 24.69%} at high load level. +- With flat noise figure model assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-13.88%, -66.34%} at low load level, mean and 5% DL Average-UPT loss of {-13.70%, -66.10%} at medium load level, mean and 5% DL Average-UPT loss of {-13.88%, -65.36%} at high load level. + - Semi-static SBFD provides mean UL Average-UPT gain of 12.77% at low load level, mean UL Average-UPT gain of 12.80% at medium load level, mean UL Average-UPT gain of 12.77% at high load level. + +**For Urban Macro (FR1) with 0% grid shift in SBFD deployment case 4, if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is less than 93 dB and spatial isolation for co-site adjacent-channel CLI is less than 93dB, assuming SBFD antenna configuration option-2 (twice area and same TxRUs):** + +- In case of using SBFD Alt 4 and large packet size, (SBFD#4\_UMA\_FR1\_0%\_Sub#4, one source) + - For operator 1 (Legacy TDD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.49%, -0.92%} at low load level, mean and 5% DL Average-UPT loss of {-0.56%, -1.58%} at medium load level, mean and 5% DL Average-UPT gain of {0.01%, 1.75%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-14.55%, -31.51%} at low load level, mean and 5% UL Average-UPT loss of {-58.85%, -90.20%} at medium load level, mean and 5% UL Average-UPT loss of {-78.07%, -99.85%} at high load level. + +- All results assumed 53dBm BS transmission power. +- All results assumed piecewise linear noise figure model. +- For operator 2 (SBFD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-2.23%, -2.66%} at low load level, mean and 5% DL Average-UPT loss of {-3.85%, -7.37%} at medium load level, mean and 5% DL Average-UPT loss of {-3.51%, -9.28%} at high load level. + - Semi-static SBFD provides mean UL Average-UPT loss of -29.52% and 5% UL Average-UPT gain of 71.75% at low load level, mean and 5% UL Average-UPT loss of {-97.10%, -97.98%} at medium load level, mean and 5% UL Average-UPT loss of {-99.90%, -100.00%} at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 2 and large packet size, (SBFD#4\_UMA\_FR1\_0%\_Sub#5, one source) + - For operator 1 (Legacy TDD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.28%, -0.32%} at low load level, mean and 5% DL Average-UPT loss of {-0.35%, -1.67%} at medium load level, mean DL Average-UPT loss of -0.41% and 5% DL Average-UPT gain of 3.70% at high load level. + - Semi-static SBFD provides mean UL Average-UPT gain of 0.05% and 5% UL Average-UPT loss of -0.63% at low load level, mean UL Average-UPT loss of -0.10% and 5% UL Average-UPT gain of 0.30% at medium load level, mean UL Average-UPT gain of 0.10% and 5% UL Average-UPT loss of -1.88% at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. + - For operator 2 (SBFD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-22.51%, -26.69%} at low load level, mean and 5% DL Average-UPT loss of {-36.59%, -48.65%} at medium load level, mean and 5% DL Average-UPT loss of {-52.81%, -65.54%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {45.47%, 113.30%} at low load level, mean UL Average-UPT gain of 7.39% and 5% UL Average-UPT loss of -0.45% at medium load level, mean and 5% UL Average-UPT gain of {4.34%, 3.71%} at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 3 and large packet size, (SBFD#4\_UMA\_FR1\_0%\_Sub#12, one source) + - For operator 1 (Legacy TDD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.27%, -1.40%} at low load level, mean and 5% DL Average-UPT loss of {-0.50%, -0.04%} at medium load level, mean DL Average-UPT loss of -0.52% and 5% DL Average-UPT gain of 3.88% at high load level. + - Semi-static SBFD provides mean UL Average-UPT gain of 0.07% and 5% UL Average-UPT loss of -1.07% at low load level, mean and 5% UL Average-UPT loss of {-0.23%, -0.35%} at medium load level, mean and 5% UL Average-UPT gain of {0.02%, 2.41%} at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. + - For operator 2 (SBFD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-22.51%, -26.69%} at low load level, mean and 5% DL Average-UPT loss of {-36.59%, -48.65%} at medium load level, mean and 5% DL Average-UPT loss of {-52.81%, -65.54%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {45.47%, 113.30%} at low load level, mean UL Average-UPT gain of 7.39% and 5% UL Average-UPT loss of -0.45% at medium load level, mean and 5% UL Average-UPT gain of {4.34%, 3.71%} at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. + +- Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-27.03%, -31.10%} at low load level, mean and 5% DL Average-UPT loss of {-43.97%, -60.37%} at medium load level, mean and 5% DL Average-UPT loss of {-60.54%, -72.49%} at high load level. +- Semi-static SBFD provides mean and 5% UL Average-UPT gain of {51.15%, 109.81%} at low load level, mean and 5% UL Average-UPT gain of {7.13%, 0.59%} at medium load level, mean and 5% UL Average-UPT gain of {4.09%, 3.93%} at high load level. +- All results assumed 53dBm BS transmission power. +- All results assumed piecewise linear noise figure model. + +**For Urban Macro (FR1) with 0% grid shift in SBFD deployment case 4, if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is equal to 93 dB and spatial isolation for co-site adjacent-channel CLI is equal to 93dB, assuming SBFD antenna configuration option-2 (twice area and same TxRUs):** + +- In case of using SBFD Alt 4 and large packet size, (SBFD#4\_UMA\_FR1\_0%\_Sub#6, 2 sources) + - For operator 1 (Legacy TDD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.44%, -1.25%} at low load level, mean and 5% DL Average-UPT loss of {-3.39%, -6.93%} at medium load level, mean and 5% DL Average-UPT loss of {-4.45%, -7.97%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-7.43%, -16.18%} at low load level, mean and 5% UL Average-UPT loss of {-30.66%, -46.23%} at medium load level, mean and 5% UL Average-UPT loss of {-39.94%, -49.99%} at high load level. + - With 49dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.28%, -0.25%} at low load level, mean and 5% DL Average-UPT loss of {-3.27%, -4.47%} at medium load level, mean and 5% DL Average-UPT loss of {-4.36%, -7.14%} at high load level. + - Semi-static SBFD provides no change on mean UL Average-UPT and 5% UL Average-UPT loss of -0.92% at low load level, mean UL Average-UPT loss of -0.14% and no change on 5% UL Average-UPT at medium load level, mean UL Average-UPT loss of -0.27% and no change on 5% UL Average-UPT at high load level. + - With 53dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.60%, -2.24%} at low load level, mean and 5% DL Average-UPT loss of {-3.51%, -9.38%} at medium load level, mean and 5% DL Average-UPT loss of {-4.53%, -8.80%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-14.87%, -31.44%} at low load level, mean and 5% UL Average-UPT loss of {-61.19%, -92.47%} at medium load level, mean and 5% UL Average-UPT loss of {-79.61%, -99.98%} at high load level. + - All results assumed piecewise linear noise figure model. +- For operator 2 (SBFD operator): + - Semi-static SBFD provides mean DL Average-UPT loss of -0.60% and 5% DL Average-UPT gain of 3.34% at low load level, mean and 5% DL Average-UPT loss of {-5.70%, -10.72%} at medium load level, mean and 5% DL Average-UPT loss of {-12.29%, -23.48%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {3.50%, 114.57%} at low load level, mean and 5% UL Average-UPT loss of {-36.04%, -18.46%} at medium load level, mean and 5% UL Average-UPT loss of {-55.59%, -69.36%} at high load level. +- With 49dBm BS transmission power assumed by 1 source, + +- Semi-static SBFD provides mean and 5% DL Average-UPT gain of {1.73%, 13.28%} at low load level, mean DL Average-UPT loss of -0.59% and 5% DL Average-UPT gain of 0.70% at medium load level, mean and 5% DL Average-UPT loss of {-5.89%, -9.82%} at high load level. +- Semi-static SBFD provides mean and 5% UL Average-UPT gain of {19.86%, 133.94%} at low load level, mean and 5% UL Average-UPT gain of {5.54%, 59.70%} at medium load level, mean and 5% UL Average-UPT loss of {-18.22%, -38.71%} at high load level. +- With 53dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-2.94%, -6.59%} at low load level, mean and 5% DL Average-UPT loss of {-10.81%, -22.15%} at medium load level, mean and 5% DL Average-UPT loss of {-18.70%, -37.15%} at high load level. + - Semi-static SBFD provides mean UL Average-UPT loss of -12.85% and 5% UL Average-UPT gain of 95.20% at low load level, mean and 5% UL Average-UPT loss of {-77.63%, -96.62%} at medium load level, mean and 5% UL Average-UPT loss of {-92.97%, -100.00%} at high load level. +- All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 2 and large packet size, (SBFD#4\_UMA\_FR1\_0%\_Sub#7, 2 sources) + - For operator 1 (Legacy TDD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.45%, -1.52%} at low load level, mean and 5% DL Average-UPT loss of {-2.12%, -2.25%} at medium load level, mean and 5% DL Average-UPT loss of {-3.39%, -4.86%} at high load level. + - Semi-static SBFD provides mean UL Average-UPT loss of -0.01% and 5% UL Average-UPT gain of 0.07% at low load level, mean and 5% UL Average-UPT gain of {0.04%, 0.10%} at medium load level, mean and 5% UL Average-UPT gain of {0.13%, 2.08%} at high load level. + - With 49dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.46%, -1.07%} at low load level, mean and 5% DL Average-UPT loss of {-3.27%, -5.17%} at medium load level, mean and 5% DL Average-UPT loss of {-5.21%, -5.63%} at high load level. + - Semi-static SBFD provides no change on mean and 5% UL Average-UPT at all load levels. + - With 53dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.43%, -1.98%} at low load level, mean DL Average-UPT loss of -0.97% and 5% DL Average-UPT gain of 0.67% at medium load level, mean and 5% DL Average-UPT loss of {-1.57%, -4.09%} at high load level. + - Semi-static SBFD provides mean UL Average-UPT loss of -0.01% and 5% UL Average-UPT gain of 0.15% at low load level, mean and 5% UL Average-UPT gain of {0.09%, 0.19%} at medium load level, mean and 5% UL Average-UPT gain of {0.26%, 4.16%} at high load level. + - All results assumed piecewise linear noise figure model. +- For operator 2 (SBFD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-23.27%, -23.08%} at low load level, mean and 5% DL Average-UPT loss of {-29.59%, -38.52%} at medium load level, mean and 5% DL Average-UPT loss of {-40.53%, -49.36%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {88.87%, 168.31%} at low load level, mean and 5% UL Average-UPT gain of {68.41%, 37.37%} at medium load level, mean and 5% UL Average-UPT gain of {34.44%, 24.69%} at high load level. +- With 49dBm BS transmission power assumed by 1 source, + +- Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-23.57%, -19.09%} at low load level, mean and 5% DL Average-UPT loss of {-21.22%, -24.50%} at medium load level, mean and 5% DL Average-UPT loss of {-26.20%, -30.61%} at high load level. +- Semi-static SBFD provides mean and 5% UL Average-UPT gain of {117.84%, 212.84%} at low load level, mean and 5% UL Average-UPT gain of {110.49%, 71.64%} at medium load level, mean and 5% UL Average-UPT gain of {45.59%, 45.16%} at high load level. +- With 53dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-22.97%, -27.07%} at low load level, mean and 5% DL Average-UPT loss of {-37.96%, -52.53%} at medium load level, mean and 5% DL Average-UPT loss of {-54.87%, -68.11%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {59.89%, 123.77%} at low load level, mean and 5% UL Average-UPT gain of {26.32%, 3.10%} at medium load level, mean and 5% UL Average-UPT gain of {23.29%, 4.23%} at high load level. +- All results assumed piecewise linear noise figure model. + +**For Urban Macro (FR1) with 0% grid shift in SBFD deployment case 4, if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is no less than 93 dB and spatial isolation for co-site adjacent-channel CLI is no less than 93dB, assuming SBFD antenna configuration option-3 (same area and half TxRUs):** + +- In case of using SBFD Alt 4 and large packet size, (SBFD#4\_UMA\_FR1\_0%\_Sub#8, one sources) + - For operator 1 (Legacy TDD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.69%, -3.09%} at low load level, mean and 5% DL Average-UPT loss of {-3.06%, -5.65%} at medium load level, mean and 5% DL Average-UPT loss of {-3.86%, -10.53%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-17.62%, -37.98%} at low load level, mean and 5% UL Average-UPT loss of {-66.78%, -96.77%} at medium load level, mean and 5% UL Average-UPT loss of {-81.96%, -100.00%} at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. + - For operator 2 (SBFD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-10.17%, -28.57%} at low load level, mean and 5% DL Average-UPT loss of {-28.19%, -54.57%} at medium load level, mean and 5% DL Average-UPT loss of {-46.36%, -70.80%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-26.66%, -11.10%} at low load level, mean and 5% UL Average-UPT loss of {-83.96%, -99.51%} at medium load level, mean and 5% UL Average-UPT loss of {-95.28%, -100.00%} at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 2 and large packet size, (SBFD#4\_UMA\_FR1\_0%\_Sub#9, one source) + - For operator 1 (Legacy TDD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.43%, -1.96%} at low load level, mean DL Average-UPT loss of -0.65% and 5% DL Average-UPT gain of 1.78% at medium load level, mean and 5% DL Average-UPT loss of {-1.22%, -5.64%} at high load level. + +- Semi-static SBFD provides mean and 5% UL Average-UPT gain of {0.03%, 0.17%} at low load level, mean and 5% UL Average-UPT gain of {0.08%, 0.69%} at medium load level, mean UL Average-UPT gain of 0.04% and 5% UL Average-UPT loss of -2.05% at high load level. +- All results assumed 53dBm BS transmission power. +- All results assumed piecewise linear noise figure model. +- For operator 2 (SBFD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-29.62%, -46.06%} at low load level, mean and 5% DL Average-UPT loss of {-54.61%, -78.60%} at medium load level, mean and 5% DL Average-UPT loss of {-71.00%, -83.92%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {37.55%, 8.07%} at low load level, mean UL Average-UPT gain of 4.32% and 5% UL Average-UPT loss of -42.63% at medium load level, mean and 5% UL Average-UPT loss of {-3.31%, -49.99%} at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. + +**For Urban Macro (FR1) with 0% grid shift in SBFD deployment case 4, if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is less than 93 dB and spatial isolation for co-site adjacent-channel CLI is less than 93dB, assuming SBFD antenna configuration option-3 (same area and half TxRUs):** + +- In case of using SBFD Alt 4 and large packet size, (SBFD#4\_UMA\_FR1\_0%\_Sub#10, one source) + - For operator 1 (Legacy TDD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.58%, -1.63%} at low load level, mean DL Average-UPT loss of -0.47% and 5% DL Average-UPT gain of 0.45% at medium load level, mean DL Average-UPT loss of -0.14% and 5% DL Average-UPT gain of 3.06% at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-17.39%, -38.18%} at low load level, mean and 5% UL Average-UPT loss of {-64.89%, -95.56%} at medium load level, mean and 5% UL Average-UPT loss of {-80.91%, -100.00%} at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. + - For operator 2 (SBFD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-9.28%, -25.68%} at low load level, mean and 5% DL Average-UPT loss of {-21.14%, -42.57%} at medium load level, mean and 5% DL Average-UPT loss of {-35.37%, -57.74%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-42.07%, -15.62%} at low load level, mean and 5% UL Average-UPT loss of {-98.64%, -99.60%} at medium load level, mean and 5% UL Average-UPT loss of {-99.97%, -100.00%} at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 2 and large packet size, (SBFD#4\_UMA\_FR1\_0%\_Sub#11, one source) + - For operator 1 (Legacy TDD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.59%, -4.43%} at low load level, mean and 5% DL Average-UPT loss of {-0.27%, -5.46%} at medium load level, mean DL Average-UPT loss of -0.25% and 5% DL Average-UPT gain of 5.18% at high load level. + - Semi-static SBFD provides mean UL Average-UPT loss of -0.24% and 5% UL Average-UPT gain of 19.56% at low load level, mean UL Average-UPT loss of -0.54% and 5% UL Average-UPT gain of + +- 4.11% at medium load level, mean UL Average-UPT loss of -1.30% and 5% UL Average-UPT gain of 3.01% at high load level. +- All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. + - For operator 2 (SBFD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-29.43%, -49.38%} at low load level, mean and 5% DL Average-UPT loss of {-53.90%, -77.83%} at medium load level, mean and 5% DL Average-UPT loss of {-70.16%, -81.84%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {25.53%, 5.73%} at low load level, mean and 5% UL Average-UPT loss of {-9.40%, -48.86%} at medium load level, mean and 5% UL Average-UPT loss of {-17.01%, -48.94%} at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. + - In case of using SBFD Alt 3 and large packet size, (SBFD#4\_UMA\_FR1\_0%\_Sub#13, one source) + - For operator 1 (Legacy TDD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.21%, -0.42%} at low load level, mean DL Average-UPT loss of -0.27% and 5% DL Average-UPT gain of 0.64% at medium load level, mean DL Average-UPT loss of -0.02% and 5% DL Average-UPT gain of 0.73% at high load level. + - Semi-static SBFD provides mean UL Average-UPT gain of 0.12% and 5% UL Average-UPT loss of -0.97% at low load level, mean UL Average-UPT loss of -0.24% and 5% UL Average-UPT gain of 0.57% at medium load level, mean UL Average-UPT gain of 0.22% and 5% UL Average-UPT loss of -2.55% at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. + - For operator 2 (SBFD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-33.45%, -49.00%} at low load level, mean and 5% DL Average-UPT loss of {-60.15%, -82.06%} at medium load level, mean and 5% DL Average-UPT loss of {-74.54%, -85.64%} at high load level. + - Semi-static SBFD provides mean UL Average-UPT gain of 28.53% and 5% UL Average-UPT loss of -0.51% at low load level, mean and 5% UL Average-UPT loss of {-10.38%, -43.42%} at medium load level, mean and 5% UL Average-UPT loss of {-18.47%, -49.26%} at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. + +#### 7.3.1.4.2 Urban Macro (100% grid shift) + +5 sources provided the SLS evaluation results for Urban Macro (FR1) with 100% grid shift in SBFD Deployment Case 4. The evaluation results are categorized into 13 sub-cases as in Table 7.3.1.4.2-1~ Table 7.3.1.4.2-5 based on the different key assumptions. Each sub-case is based on one combination of key assumptions. + +**Table 7.3.1.4.2-1: Sub-cases for urban macro (FR1) with 100% grid shift, no less than 93dB inter-sector isolation, Twice area&same TxRUs in SBFD deployment Case 4.** + +| | | SBFD#4_UMA_FR1_10
0%_Sub#1 | SBFD#4_UMA_FR1_10
0%_Sub#2 | SBFD#4_UMA_FR1_10
0%_Sub#3 | +|-------------------------------------------------|----------------|-------------------------------|-------------------------------|-------------------------------| +| Co-site co-channel: Spatial isolation + digital | Opt 1: >= 93dB | O | O | O | +| | Opt 2: < 93dB | | | | + +| | | | | | +|-----------------------------------|------------------------------------------|-----------------|------------------------------------|------------------------------------| +| isolation | Opt 3: 93dB | | | | +| SBFD slot configuration | Alt-4: {DDDSU} vs. {XXXXX} | O | O | | +| | Alt-2: {DDDSU} vs. {XXXXU} | | | O | +| | Alt-1: {DDDSU} vs. {DXXXU} | | | | +| | Alt-3: {DDSUU} vs. {XXXU} | | | | +| SBFD antenna configuration | Twice area&same TxRUs (Option 2) | O | O | O | +| | Same area&same TxRUs (Option 1) | | | | +| | Same area&half TxRUs (Option 3) | | | | +| Packet Size | Option 1: DL: 4Kbytes, UL: 1Kbytes | O | | | +| | Option 2: DL: 0.5Mbytes, UL: 0.125Mbytes | | O | O | +| Sources | | 1 source ([26]) | 4 sources ([18], [26], [28], [32]) | 4 sources ([18], [22], [28], [32]) | + +**Table 7.3.1.4.2-2: Sub-cases for urban macro (FR1) with 100% grid shift, less than 93dB inter-sector isolation, Twice area&same TxRUs in SBFD deployment Case 4.** + +| | | SBFD#4_UMA_FR1_10 0%_Sub#4 | SBFD#4_UMA_FR1_10 0%_Sub#5 | SBFD#4_UMA_FR1_10 0%_Sub#12 | +|------------------------------------------------------------------|------------------------------------------|-----------------------------------|-----------------------------------|------------------------------------| +| Co-site co-channel: Spatial isolation + digital isolation | Opt 1:>= 93dB | | | | +| | Opt 2: < 93dB | O | O | O | +| | Opt 3: 93dB | | | | +| SBFD slot configuration | Alt-4: {DDDSU} vs. {XXXXX} | O | | | +| | Alt-2: {DDDSU} vs. {XXXXU} | | O | | +| | Alt-1: {DDDSU} vs. {DXXXU} | | | | +| | Alt-3: {DDSUU} vs. {XXXU} | | | O | +| SBFD antenna configuration | Twice area&same TxRUs (Option 2) | O | O | O | +| | Same area&same TxRUs (Option 1) | | | | +| | Same area&half TxRUs (Option 3) | | | | +| Packet Size | Option 1: DL: 4Kbytes, UL: 1Kbytes | | | | +| | Option 2: DL: 0.5Mbytes, UL: 0.125Mbytes | O | O | O | +| Sources | | 1 source ([18]) | 1 source ([18]) | 1 source ([18]) | + +**Table 7.3.1.4.2-3: Sub-cases for urban macro (FR1) with 100% grid shift, 93dB inter-sector isolation, Twice area&same TxRUs in SBFD deployment Case 4.** + +| | | SBFD#4_UMA_FR1_100%_Sub#6 | SBFD#4_UMA_FR1_100%_Sub#7 | +|------------------------------------------------------------------|----------------------------|----------------------------------|----------------------------------| +| Co-site co-channel: Spatial isolation + digital isolation | Opt 1:>= 93dB | | | +| | Opt 2: < 93dB | | | +| | Opt 3: 93dB | O | O | +| SBFD slot configuration | Alt-4: {DDDSU} vs. {XXXXX} | O | | +| | Alt-2: {DDDSU} vs. {XXXXU} | | O | + +| | | | | +|----------------------------|------------------------------------------|------------------------|------------------------| +| | Alt-1: {DDDSU}
vs. {DXXXU} | | | +| | Alt-3: {DDSUU}
vs. {XXXXU} | | | +| SBFD antenna configuration | Twice area&same TxRUs (Option 2) | O | O | +| | Same area&same TxRUs (Option 1) | | | +| | Same area&half TxRUs (Option 3) | | | +| Packet Size | Option 1: DL: 4Kbytes, UL: 1Kbytes | | | +| | Option 2: DL: 0.5Mbytes, UL: 0.125Mbytes | O | O | +| Sources | | 2 sources ([18], [28]) | 2 sources ([18], [28]) | + +Table 7.3.1.4.2-4: Sub-cases for urban macro (FR1) with 100% grid shift, no less than 93dB inter-sector isolation, Same area&half TxRUs in SBFD deployment Case 4. + +| | | SBFD#4_UMA_FR1_100%_Sub#8 | SBFD#4_UMA_FR1_100%_Sub#9 | +|-----------------------------------------------------------|------------------------------------------|---------------------------|---------------------------| +| Co-site co-channel: Spatial isolation + digital isolation | Opt 1:>= 93dB | O | O | +| | Opt 2: < 93dB | | | +| | Opt 3: 93dB | | | +| SBFD slot configuration | Alt-4: {DDDSU}
vs. {XXXXX} | O | | +| | Alt-2: {DDDSU}
vs. {XXXXU} | | O | +| | Alt-1: {DDDSU}
vs. {DXXXU} | | | +| | Alt-3: {DDSUU}
vs. {XXXXU} | | | +| SBFD antenna configuration | Twice area&same TxRUs (Option 2) | | | +| | Same area&same TxRUs (Option 1) | | | +| | Same area&half TxRUs (Option 3) | O | O | +| Packet Size | Option 1: DL: 4Kbytes, UL: 1Kbytes | | | +| | Option 2: DL: 0.5Mbytes, UL: 0.125Mbytes | O | O | +| Sources | | 1 source ([18]) | 1 source ([18]) | + +Table 7.3.1.4.2-5: Sub-cases for urban macro (FR1) with 100% grid shift, less than 93dB inter-sector isolation, Same area&half TxRUs in SBFD deployment Case 4. + +| | | SBFD#4_UMA_FR1_100%_Sub#10 | SBFD#4_UMA_FR1_100%_Sub#11 | SBFD#4_UMA_FR1_100%_Sub#13 | +|-----------------------------------------------------------|----------------------------------|----------------------------|----------------------------|----------------------------| +| Co-site co-channel: Spatial isolation + digital isolation | Opt 1:>= 93dB | | | | +| | Opt 2: < 93dB | O | O | O | +| | Opt 3: 93dB | | | | +| SBFD slot configuration | Alt-4: {DDDSU}
vs. {XXXXX} | O | | | +| | Alt-2: {DDDSU}
vs. {XXXXU} | | O | | +| | Alt-1: {DDDSU}
vs. {DXXXU} | | | | +| | Alt-3: {DDSUU}
vs. {XXXXU} | | | O | +| SBFD antenna configuration | Twice area&same TxRUs (Option 2) | | | | +| | Same area&same TxRUs (Option 1) | | | | +| | Same area&half | O | O | O | + +| | | | | | +|--------------------|---------------------------------------------------------|-----------------|-----------------|-----------------| +| | TxRUs (Option 3) | | | | +| Packet Size | Option 1: DL:
4Kbytes, UL:
1Kbytes | | | | +| | Option 2: DL:
0.5Mbytes, UL:
0.125Mbytes | ○ | ○ | ○ | +| Sources | | 1 source ([18]) | 1 source ([18]) | 1 source ([18]) | + +#### 7.3.1.4.2.1 Summary of the observations + +**For Urban Macro (FR1) with 100% grid shift in SBFD deployment case 4, if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is no less than 93 dB, assuming SBFD antenna configuration option-2 (twice area and same TxRUs):** + +- In case of using SBFD Alt 4 and small packet size, (SBFD#4\_UMA\_FR1\_100%\_Sub#1, one source) + - For operator 1 (Legacy TDD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-1.64%, -15.66%} at low load level, mean and 5% DL Average-UPT loss of {-3.03%, -40.75%} at medium load level, mean and 5% DL Average-UPT loss of {-4.98%, -67.49%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-12.11%, -81.58%} at low load level, mean and 5% UL Average-UPT loss of {-18.27%, -100.00%} at medium load level, mean and 5% UL Average-UPT loss of {-23.70%, -50.00%} at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed 5dBs flat noise figure model. + - For operator 2 (SBFD operator): + - Semi-static SBFD provides mean DL Average-UPT gain of 8.14% and 5% DL Average-UPT loss of -14.65% at low load level, mean DL Average-UPT gain of 6.70% and 5% DL Average-UPT loss of -33.79% at medium load level, mean DL Average-UPT gain of 5.51% and 5% DL Average-UPT loss of -53.85% at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {150.98%, 31.98%} at low load level, mean UL Average-UPT gain of 131.63% and 5% UL Average-UPT loss of -62.46% at medium load level, mean UL Average-UPT gain of 113.16% and 5% UL Average-UPT loss of -49.98% at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed 5dBs flat noise figure model. +- In case of using SBFD Alt 4 and large packet size, (SBFD#4\_UMA\_FR1\_100%\_Sub#2, 4 sources) + - For operator 1 (Legacy TDD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.35%, -2.64%} at low load level, mean and 5% DL Average-UPT loss of {-3.31%, -9.41%} at medium load level, mean and 5% DL Average-UPT loss of {-5.38%, -7.68%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-13.50%, -24.39%} at low load level, mean and 5% UL Average-UPT loss of {-21.26%, -0.53%} at medium load level, mean and 5% UL Average-UPT loss of {-16.74%, -0.90%} at high load level. + - With 49dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.35%, -0.16%} at low load level, mean and 5% DL Average-UPT loss of {-2.56%, -4.62%} at medium load level, mean and 5% DL Average-UPT loss of {-3.36%, -5.77%} at high load level. + +- Semi-static SBFD provides no change on mean UL Average-UPT and mean UL Average-UPT loss of -0.79% at low load level, mean and 5% UL Average-UPT loss of {-0.27%, -0.53%} at medium load level, mean and 5% UL Average-UPT loss of {-0.60%, -0.90%} at high load level. +- With 53dBm BS transmission power assumed by 2 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-7.38%, -29.61%} at low load level, mean and 5% DL Average-UPT loss of {-8.14%, -38.48%} at medium load level, mean and 5% DL Average-UPT loss of {-8.47%, -53.30%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-20.43%, -62.20%} at low load level, mean and 5% UL Average-UPT loss of {-37.37%, -43.95%} at medium load level, mean and 5% UL Average-UPT loss of {-46.03%, -49.77%} at high load level. +- With piecewise noise figure model assumed by 2 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.35%, -1.40%} at low load level, mean and 5% DL Average-UPT loss of {-2.94%, -7.02%} at medium load level, mean and 5% DL Average-UPT loss of {-4.37%, -6.72%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-6.75%, -12.59%} at low load level, mean and 5% UL Average-UPT loss of {-26.88%, -44.22%} at medium load level, mean and 5% UL Average-UPT loss of {-37.96%, -50.22%} at high load level. +- With flat noise figure model assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-14.40%, -56.57%} at low load level, mean and 5% DL Average-UPT loss of {-12.97%, -67.55%} at medium load level, mean and 5% DL Average-UPT loss of {-11.57%, -98.92%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-27.36%, -100.00%} at low load level, mean UL Average-UPT loss of -21.26% and no change on 5% UL Average-UPT at medium load level, mean UL Average-UPT loss of -16.74% and no change on 5% UL Average-UPT at high load level. +- For operator 2 (SBFD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.85%, -3.79%} at low load level, mean and 5% DL Average-UPT loss of {-5.76%, -13.28%} at medium load level, mean and 5% DL Average-UPT loss of {-10.65%, -22.06%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {21.64%, 32.42%} at low load level, mean and 5% UL Average-UPT gain of {13.37%, 10.67%} at medium load level, mean and 5% UL Average-UPT loss of {-11.43%, -3.28%} at high load level. + - With 49dBm BS transmission power assumed by 2 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {4.89%, 2.11%} at low load level, mean and 5% DL Average-UPT loss of {-1.69%, -4.04%} at medium load level, mean and 5% DL Average-UPT loss of {-4.00%, -6.91%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {21.64%, 32.42%} at low load level, mean and 5% UL Average-UPT gain of {13.37%, 38.67%} at medium load level, mean UL Average-UPT loss of -11.43% and 5% UL Average-UPT gain of 11.31% at high load level. + - With 53dBm BS transmission power assumed by 2 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-13.13%, -37.88%} at low load level, mean and 5% DL Average-UPT loss of {-15.07%, -47.73%} at medium load level, mean and 5% DL Average-UPT loss of {-16.61%, -67.30%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {18.52%, 14.39%} at low load level, mean and 5% UL Average-UPT loss of {-7.47%, -45.62%} at medium load level, mean and 5% UL Average-UPT loss of {-19.90%, -49.98%} at high load level. + - With piecewise noise figure model assumed by 3 sources, + +- Semi-static SBFD provides mean DL Average-UPT gain of 0.92% and 5% DL Average-UPT loss of -3.63% at low load level, mean and 5% DL Average-UPT loss of {-2.78%, -6.96%} at medium load level, mean and 5% DL Average-UPT loss of {-6.16%, -9.52%} at high load level. +- Semi-static SBFD provides mean and 5% UL Average-UPT gain of {19.66%, 50.68%} at low load level, mean and 5% UL Average-UPT gain of {6.51%, 21.34%} at medium load level, mean and 5% UL Average-UPT loss of {-40.50%, -6.56%} at high load level. +- With flat noise figure model assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-23.63%, -72.14%} at low load level, mean and 5% DL Average-UPT loss of {-21.39%, -75.87%} at medium load level, mean and 5% DL Average-UPT loss of {-18.08%, -100.00%} at high load level. + - Semi-static SBFD provides mean UL Average-UPT gain of 41.11% and 5% UL Average-UPT loss of -100.00% at low load level, mean UL Average-UPT gain of 53.47% and no change on 5% UL Average-UPT at medium load level, mean UL Average-UPT gain of 50.89% and no change on 5% UL Average-UPT at high load level. +- In case of using SBFD Alt 2 and large packet size, (SBFD#4\_UMA\_FR1\_100%\_Sub#3, 4 sources) + - For operator 1 (Legacy TDD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.30%, -0.16%} at low load level, mean and 5% DL Average-UPT loss of {-1.61%, -3.59%} at medium load level, mean and 5% DL Average-UPT loss of {-3.21%, -3.92%} at high load level. + - Semi-static SBFD provides no change on mean and 5% UL Average-UPT for all load levels. + - With 49dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.30%, -0.16%} at low load level, mean and 5% DL Average-UPT loss of {-2.67%, -3.59%} at medium load level, mean and 5% DL Average-UPT loss of {-4.17%, -3.79%} at high load level. + - Semi-static SBFD provides no change on mean and 5% UL Average-UPT at all load levels. + - With 53dBm BS transmission power assumed by 2 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.35%, -1.87%} at low load level, mean and 5% DL Average-UPT loss of {-1.59%, -4.64%} at medium load level, mean and 5% DL Average-UPT loss of {-3.09%, -3.95%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {0.02%, 1.20%} at low load level, mean and 5% UL Average-UPT gain of {0.04%, 0.78%} at medium load level, mean UL Average-UPT gain of 0.01% and 5% UL Average-UPT loss of -1.50% at high load level. + - All results assumed piecewise linear noise figure model. + - For operator 2 (SBFD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-22.30%, -21.49%} at low load level, mean and 5% DL Average-UPT loss of {-24.57%, -31.46%} at medium load level, mean and 5% DL Average-UPT loss of {-25.84%, -51.80%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {90.01%, 94.35%} at low load level, mean and 5% UL Average-UPT gain of {94.07%, 58.67%} at medium load level, mean and 5% UL Average-UPT gain of {36.70%, 38.16%} at high load level. + - With 49dBm BS transmission power assumed by 2 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-24.13%, -15.39%} at low load level, mean and 5% DL Average-UPT loss of {-24.57%, -17.56%} at medium load level, mean and 5% DL Average-UPT loss of {-25.84%, -33.07%} at high load level. + +- Semi-static SBFD provides mean and 5% UL Average-UPT gain of {101.42%, 94.35%} at low load level, mean and 5% UL Average-UPT gain of {95.42%, 66.67%} at medium load level, mean and 5% UL Average-UPT gain of {46.12%, 52.46%} at high load level. +- With 53dBm BS transmission power assumed by 2 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-18.21%, -45.92%} at low load level, mean and 5% DL Average-UPT loss of {-23.60%, -47.81%} at medium load level, mean and 5% DL Average-UPT loss of {-31.85%, -60.56%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {43.40%, 75.77%} at low load level, mean and 5% UL Average-UPT gain of {19.46%, 5.71%} at medium load level, mean and 5% UL Average-UPT gain of {16.70%, 3.15%} at high load level. +- With piecewise noise figure model assumed by 3 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-23.21%, -18.44%} at low load level, mean and 5% DL Average-UPT loss of {-24.64%, -24.51%} at medium load level, mean and 5% DL Average-UPT loss of {-26.76%, -47.06%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {95.72%, 107.56%} at low load level, mean and 5% UL Average-UPT gain of {94.75%, 62.67%} at medium load level, mean and 5% UL Average-UPT gain of {41.41%, 45.31%} at high load level. +- With flat noise figure model assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-14.13%, -66.67%} at low load level, mean and 5% DL Average-UPT loss of {-13.05%, -53.06%} at medium load level, mean and 5% DL Average-UPT loss of {-13.25%, -51.80%} at high load level. + - Semi-static SBFD provides mean UL Average-UPT gain of 20.00% and no change on 5% UL Average-UPT at low load level, mean UL Average-UPT gain of 5.99% and no change on 5% UL Average-UPT at medium load level, mean UL Average-UPT gain of 5.99% and no change on 5% UL Average-UPT at high load level. + +**For Urban Macro (FR1) with 100% grid shift in SBFD deployment case 4, if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is less than 93 dB, assuming SBFD antenna configuration option-2 (twice area and same TxRUs):** + +- In case of using SBFD Alt 4 and large packet size, (SBFD#4\_UMA\_FR1\_100%\_Sub#4, one source) + - For operator 1 (Legacy TDD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.57%, -2.36%} at low load level, mean and 5% DL Average-UPT loss of {-1.82%, -3.83%} at medium load level, mean and 5% DL Average-UPT loss of {-0.47%, -0.80%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-12.52%, -27.69%} at low load level, mean and 5% UL Average-UPT loss of {-51.61%, -86.04%} at medium load level, mean and 5% UL Average-UPT loss of {-73.56%, -99.04%} at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. + - For operator 2 (SBFD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-2.02%, -1.86%} at low load level, mean and 5% DL Average-UPT loss of {-4.42%, -12.07%} at medium load level, mean and 5% DL Average-UPT loss of {-3.75%, -12.26%} at high load level. + - Semi-static SBFD provides mean UL Average-UPT loss of -14.91% and 5% UL Average-UPT gain of 118.16% at low load level, mean and 5% UL Average-UPT loss of {-89.10%, -94.81%} at medium load level, mean and 5% UL Average-UPT loss of {-99.26%, -100.00%} at high load level. + +- All results assumed 53dBm BS transmission power. +- All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 2 and large packet size, (SBFD#4\_UMA\_FR1\_100%\_Sub#5, one source) + - For operator 1 (Legacy TDD operator): + - Semi-static SBFD provides mean DL Average-UPT loss of -0.27% and 5% DL Average-UPT gain of 0.10% at low load level, mean and 5% DL Average-UPT loss of {-1.23%, -3.47%} at medium load level, mean DL Average-UPT gain of 0.14% and 5% DL Average-UPT loss of -5.10% at high load level. + - Semi-static SBFD provides mean UL Average-UPT loss of -0.25% and 5% UL Average-UPT gain of 12.81% at low load level, mean UL Average-UPT gain of 0.22% and 5% UL Average-UPT loss of -0.23% at medium load level, mean UL Average-UPT loss of -1.99% and 5% UL Average-UPT gain of 6.14% at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. + - For operator 2 (SBFD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-21.93%, -24.74%} at low load level, mean and 5% DL Average-UPT loss of {-32.89%, -41.14%} at medium load level, mean and 5% DL Average-UPT loss of {-48.16%, -67.55%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {57.13%, 141.70%} at low load level, mean and 5% UL Average-UPT gain of {14.58%, 10.73%} at medium load level, mean UL Average-UPT gain of 5.58% and 5% UL Average-UPT loss of -0.43% at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 3 and large packet size, (SBFD#4\_UMA\_FR1\_100%\_Sub#12, one source) + - For operator 1 (Legacy TDD operator): + - Semi-static SBFD provides mean DL Average-UPT loss of -0.21% and 5% DL Average-UPT gain of 1.77% at low load level, mean and 5% DL Average-UPT loss of {-1.55%, -2.81%} at medium load level, mean and 5% DL Average-UPT loss of {-0.84%, -5.98%} at high load level. + - Semi-static SBFD provides mean UL Average-UPT loss of -0.36% and 5% UL Average-UPT gain of 11.81% at low load level, mean UL Average-UPT loss of -0.60% and 5% UL Average-UPT gain of 15.27% at medium load level, mean UL Average-UPT loss of -4.04% and 5% UL Average-UPT gain of 11.05% at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. + - For operator 2 (SBFD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-26.35%, -28.62%} at low load level, mean and 5% DL Average-UPT loss of {-39.58%, -49.07%} at medium load level, mean and 5% DL Average-UPT loss of {-56.22%, -72.83%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {64.82%, 134.95%} at low load level, mean and 5% UL Average-UPT gain of {14.42%, 8.36%} at medium load level, mean UL Average-UPT gain of 5.10% and 5% UL Average-UPT loss of -0.66% at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. + +**For Urban Macro (FR1) with 100% grid shift in SBFD deployment case 4, if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is equal to 93 dB, assuming SBFD antenna configuration option-2 (twice area and same TxRUs):** + +- In case of using SBFD Alt 4 and large packet size, (SBFD#4\_UMA\_FR1\_100%\_Sub#6, 2 sources) + - For operator 1 (Legacy TDD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.35%, -1.40%} at low load level, mean and 5% DL Average-UPT loss of {-2.94%, -7.02%} at medium load level, mean and 5% DL Average-UPT loss of {-4.37%, -6.72%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-6.75%, -12.59%} at low load level, mean and 5% UL Average-UPT loss of {-26.88%, -44.22%} at medium load level, mean and 5% UL Average-UPT loss of {-37.96%, -50.22%} at high load level. + - With 49dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.35%, -0.16%} at low load level, mean and 5% DL Average-UPT loss of {-2.56%, -4.62%} at medium load level, mean and 5% DL Average-UPT loss of {-3.36%, -5.77%} at high load level. + - Semi-static SBFD provides no change on mean UL Average-UPT and mean UL Average-UPT loss of -0.79% at low load level, mean and 5% UL Average-UPT loss of {-0.27%, -0.53%} at medium load level, mean and 5% UL Average-UPT loss of {-0.60%, -0.90%} at high load level. + - With 53dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.35%, -2.64%} at low load level, mean and 5% DL Average-UPT loss of {-3.31%, -9.41%} at medium load level, mean and 5% DL Average-UPT loss of {-5.38%, -7.68%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-13.50%, -24.39%} at low load level, mean and 5% UL Average-UPT loss of {-53.48%, -87.91%} at medium load level, mean and 5% UL Average-UPT loss of {-75.32%, -99.53%} at high load level. + - All results assumed piecewise linear noise figure model. + - For operator 2 (SBFD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {3.11%, 2.27%} at low load level, mean and 5% DL Average-UPT loss of {-5.76%, -13.28%} at medium load level, mean and 5% DL Average-UPT loss of {-10.65%, -22.06%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {9.77%, 89.73%} at low load level, mean and 5% UL Average-UPT loss of {-30.95%, -17.62%} at medium load level, mean and 5% UL Average-UPT loss of {-65.59%, -53.26%} at high load level. + - With 49dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT gain of {8.86%, 8.16%} at low load level, mean and 5% DL Average-UPT loss of {-2.78%, -6.96%} at medium load level, mean and 5% DL Average-UPT loss of {-6.16%, -9.52%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {23.63%, 50.68%} at low load level, mean and 5% UL Average-UPT gain of {6.51%, 56.00%} at medium load level, mean and 5% UL Average-UPT loss of {-40.50%, -6.56%} at high load level. + - With 53dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-2.63%, -3.63%} at low load level, mean and 5% DL Average-UPT loss of {-8.74%, -19.60%} at medium load level, mean and 5% DL Average-UPT loss of {-15.14%, -34.60%} at high load level. + +- Semi-static SBFD provides mean UL Average-UPT loss of -4.08% and 5% UL Average-UPT gain of 128.79% at low load level, mean and 5% UL Average-UPT loss of {-68.40%, -91.25%} at medium load level, mean and 5% UL Average-UPT loss of {-90.69%, -99.95%} at high load level. +- All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 2 and large packet size, (SBFD#4\_UMA\_FR1\_100%\_Sub#7, 2 sources) + - For operator 1 (Legacy TDD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.30%, -0.16%} at low load level, mean and 5% DL Average-UPT loss of {-1.61%, -3.59%} at medium load level, mean and 5% DL Average-UPT loss of {-3.21%, -3.92%} at high load level. + - Semi-static SBFD provides no change on mean and 5% UL Average-UPT for all load levels. + - With 49dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.30%, -0.16%} at low load level, mean and 5% DL Average-UPT loss of {-2.67%, -3.59%} at medium load level, mean and 5% DL Average-UPT loss of {-4.17%, -3.79%} at high load level. + - Semi-static SBFD provides no change on mean and 5% UL Average-UPT at all load levels. + - With 53dBm BS transmission power assumed by 2 sources, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.35%, -1.87%} at low load level, mean and 5% DL Average-UPT loss of {-1.59%, -4.64%} at medium load level, mean and 5% DL Average-UPT loss of {-3.09%, -3.95%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {0.02%, 1.20%} at low load level, mean and 5% UL Average-UPT gain of {0.04%, 0.78%} at medium load level, mean UL Average-UPT gain of 0.01% and 5% UL Average-UPT loss of -1.50% at high load level. + - All results assumed piecewise linear noise figure model. + - For operator 2 (SBFD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-24.13%, -15.39%} at low load level, mean and 5% DL Average-UPT loss of {-24.72%, -17.56%} at medium load level, mean and 5% DL Average-UPT loss of {-25.84%, -33.07%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {101.42%, 120.78%} at low load level, mean and 5% UL Average-UPT gain of {95.42%, 58.67%} at medium load level, mean and 5% UL Average-UPT gain of {36.70%, 38.16%} at high load level. + - With 49dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-24.13%, -15.07%} at low load level, mean and 5% DL Average-UPT loss of {-24.64%, -17.54%} at medium load level, mean and 5% DL Average-UPT loss of {-25.84%, -33.01%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {127.81%, 85.73%} at low load level, mean and 5% UL Average-UPT gain of {100.78%, 62.67%} at medium load level, mean and 5% UL Average-UPT gain of {41.41%, 45.31%} at high load level. + - With 53dBm BS transmission power assumed by 1 source, + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-22.30%, -25.18%} at low load level, mean and 5% DL Average-UPT loss of {-34.16%, -42.56%} at medium load level, mean and 5% DL Average-UPT loss of {-50.45%, -69.33%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {66.80%, 151.54%} at low load level, mean and 5% UL Average-UPT gain of {32.94%, 11.43%} at medium load level, mean and 5% UL Average-UPT gain of {27.41%, 6.30%} at high load level. + +- All results assumed piecewise linear noise figure model. + +**For Urban Macro (FR1) with 100% grid shift in SBFD deployment case 4, if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is no less than 93 dB, assuming SBFD antenna configuration option-3 (same area and half TxRUs):** + +- In case of using SBFD Alt 4 and large packet size, (SBFD#4\_UMA\_FR1\_100%\_Sub#8, one source) + - For operator 1 (Legacy TDD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.85%, -4.09%} at low load level, mean and 5% DL Average-UPT loss of {-3.86%, -8.37%} at medium load level, mean and 5% DL Average-UPT loss of {-5.78%, -10.32%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-15.39%, -35.58%} at low load level, mean and 5% UL Average-UPT loss of {-60.53%, -94.72%} at medium load level, mean and 5% UL Average-UPT loss of {-80.17%, -100.00%} at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. + - For operator 2 (SBFD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-9.17%, -27.31%} at low load level, mean and 5% DL Average-UPT loss of {-24.55%, -46.85%} at medium load level, mean and 5% DL Average-UPT loss of {-41.86%, -71.47%} at high load level. + - Semi-static SBFD provides mean UL Average-UPT loss of -18.90% and 5% UL Average-UPT gain of 8.58% at low load level, mean and 5% UL Average-UPT loss of {-78.70%, -98.48%} at medium load level, mean and 5% UL Average-UPT loss of {-93.51%, -100.00%} at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 2 and large packet size, (SBFD#4\_UMA\_FR1\_100%\_Sub#9, one source) + - For operator 1 (Legacy TDD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.68%, -3.65%} at low load level, mean and 5% DL Average-UPT loss of {-2.41%, -8.91%} at medium load level, mean and 5% DL Average-UPT loss of {-4.31%, -9.32%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-0.11%, -0.03%} at low load level, mean and 5% UL Average-UPT loss of {-0.25%, -0.19%} at medium load level, mean and 5% UL Average-UPT loss of {-0.46%, -2.52%} at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. + - For operator 2 (SBFD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-28.40%, -43.04%} at low load level, mean and 5% DL Average-UPT loss of {-49.73%, -71.00%} at medium load level, mean and 5% DL Average-UPT loss of {-68.63%, -84.97%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {44.21%, 20.49%} at low load level, mean UL Average-UPT gain of 9.13% and 5% UL Average-UPT loss of -44.46% at medium load level, mean and 5% UL Average-UPT loss of {-0.53%, -51.86%} at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. + +**For Urban Macro (FR1) with 100% grid shift in SBFD deployment case 4, if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is less than 93 dB, assuming SBFD antenna configuration option-3 (same area and half TxRUs):** + +- In case of using SBFD Alt 4 and large packet size, (SBFD#4\_UMA\_FR1\_100%\_Sub#10, one source) + - For operator 1 (Legacy TDD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.81%, -3.88%} at low load level, mean and 5% DL Average-UPT loss of {-1.97%, -6.26%} at medium load level, mean and 5% DL Average-UPT loss of {-1.44%, -5.50%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-15.01%, -34.63%} at low load level, mean and 5% UL Average-UPT loss of {-58.84%, -93.05%} at medium load level, mean and 5% UL Average-UPT loss of {-78.87%, -99.99%} at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. + - For operator 2 (SBFD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-8.49%, -23.98%} at low load level, mean and 5% DL Average-UPT loss of {-19.54%, -41.04%} at medium load level, mean and 5% DL Average-UPT loss of {-32.15%, -61.01%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT loss of {-29.41%, -0.27%} at low load level, mean and 5% UL Average-UPT loss of {-94.71%, -98.95%} at medium load level, mean and 5% UL Average-UPT loss of {-99.78%, -100.00%} at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 2 and large packet size, (SBFD#4\_UMA\_FR1\_100%\_Sub#11, one source) + - For operator 1 (Legacy TDD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.72%, -3.26%} at low load level, mean and 5% DL Average-UPT loss of {-2.02%, -5.91%} at medium load level, mean and 5% DL Average-UPT loss of {-3.03%, -10.86%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {0.12%, 0.08%} at low load level, mean UL Average-UPT loss of -0.25% and 5% UL Average-UPT gain of 1.43% at medium load level, mean UL Average-UPT loss of -0.60% and 5% UL Average-UPT gain of 1.34% at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. + - For operator 2 (SBFD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-27.94%, -41.25%} at low load level, mean and 5% DL Average-UPT loss of {-48.65%, -69.41%} at medium load level, mean and 5% DL Average-UPT loss of {-67.26%, -84.37%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {34.62%, 11.73%} at low load level, mean and 5% UL Average-UPT loss of {-6.35%, -44.50%} at medium load level, mean and 5% UL Average-UPT loss of {-18.07%, -52.72%} at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. +- In case of using SBFD Alt 3 and large packet size, (SBFD#4\_UMA\_FR1\_100%\_Sub#13, one source) + +- For operator 1 (Legacy TDD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-0.68%, -2.18%} at low load level, mean and 5% DL Average-UPT loss of {-2.12%, -6.56%} at medium load level, mean and 5% DL Average-UPT loss of {-3.27%, -12.27%} at high load level. + - Semi-static SBFD provides mean UL Average-UPT gain of 0.21% and 5% UL Average-UPT loss of -0.49% at low load level, mean and 5% UL Average-UPT loss of {-0.22%, -0.14%} at medium load level, mean and 5% UL Average-UPT loss of {-0.60%, -0.09%} at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. +- For operator 2 (SBFD operator): + - Semi-static SBFD provides mean and 5% DL Average-UPT loss of {-32.32%, -46.51%} at low load level, mean and 5% DL Average-UPT loss of {-55.11%, -76.17%} at medium load level, mean and 5% DL Average-UPT loss of {-72.61%, -86.84%} at high load level. + - Semi-static SBFD provides mean and 5% UL Average-UPT gain of {40.17%, 9.80%} at low load level, mean and 5% UL Average-UPT loss of {-6.72%, -45.00%} at medium load level, mean and 5% UL Average-UPT loss of {-18.29%, -52.48%} at high load level. + - All results assumed 53dBm BS transmission power. + - All results assumed piecewise linear noise figure model. + +## 7.3.2 Link level evaluation results + +### 7.3.2.1 FR1 + +#### 7.3.2.1.1 Scheme-1 (PUSCH repetition type A without joint channel estimation) + +For coverage performance evaluation of SBFD in FR1, 11 sources ([34], [17], [36], [18], [19], [20], [25], [26], [28], [31], [32]) provided 36 samples for evaluation results, assuming PUSCH repetition type A without joint channel estimation for SBFD(XXXXU), and single slot PUSCH transmission for legacy TDD (DDDSU). The following is observed: + +- 6 samples (sample 1, 2, 3, 25, 26, 33) from 3 sources ([34], [36], [28]) are based on evaluation method option-1 (Example-1) + - 3 samples (sample 3, 25, 33) from 3 sources ([34], [36], [28]) show a MCL gain of {3.40~5.82}dB for SBFD, assuming INR of co-site inter-sector interference as {-5.44~-10.30}dB, total INR of all inter-site gNB-gNB CLI as {-3.40~15.40}dB, total INR of all UE-gNB interference as {-19.70~37.76}dB + - 3 samples (sample 1, 2, 26) from one source ([36]) show a MCL gain of {0.00~0.90}dB for SBFD, assuming INR of co-site inter-sector interference as {-5.50~19.40}dB, total INR of all inter-site gNB-gNB CLI as {-3.40~1.40}dB, total INR of all UE-gNB interference as {-14.90~19.70}dB +- 15 samples (sample 4, 5, 6, 7, 8, 9, 27, 28, 29, 30, 31, 32, 34, 35, 36) from 5 sources ([17], [25], [28], [31], [32]) are based on evaluation method option-1 (Example-2) + - 5 samples (sample 4, 7, 27, 30, 34) from 5 sources ([17], [25], [28], [31], [32]) show a MCL gain of {4.91~6.93}dB for SBFD, assuming low load with $\Delta$ as {0.14~1.14}dB + - 5 samples (sample 5, 8, 28, 31, 35) from 5 sources ([17], [25], [28], [31], [32]) show a MCL gain of {4.71~6.44}dB for SBFD, assuming medium load with $\Delta$ as {0.28~1.46}dB + - 5 samples (sample 6, 9, 29, 32, 36) from 5 sources ([17], [25], [28], [31], [32]) show a MCL gain of {3.38~6.38}dB for SBFD, assuming high load with $\Delta$ as {1.45~2.47}dB +- 9 samples (sample 10, 11, 12, 13, 14, 15, 16, 17, 18) from 2 sources ([18], [26]) are based on evaluation method option-1 (Example-3) + +- Two samples (sample 10, 13) from two sources ([26], [18]) show a MCL gain of {4.30~5.30}dB for SBFD, assuming low load +- Two samples (sample 11, 14) from two sources ([26], [18]) show a MCL gain of {1.2~4.68}dB for SBFD, assuming medium load +- Two samples (sample 12, 15) from two sources ([26], [18]) show a MCL gain of {0.48~4.74}dB for SBFD, assuming high load +- One samples (sample 16) from one source ([18]) show a MCL gain of 1.9dB for SBFD, assuming low load and randomly draw a new interference level once per group of 4 SBFD slots based on the interference CDF for SBFD slots +- One samples (sample 17) from one source ([18]) show a MCL gain of 0.65dB for SBFD, assuming low load and randomly draw a new interference level once per group of 4 SBFD slots based on the interference CDF for SBFD slots +- One samples (sample 18) from one source ([18]) show a MCL gain of 0.21dB for SBFD, assuming low load and randomly draw a new interference level once per group of 4 SBFD slots based on the interference CDF for SBFD slots +- Note: RAN1 agreed that interference samples should be independently updated/generated in each slot. However, samples 16-18 are based on new interference one per group of 4 slots. +- 4 samples (sample 21, 22, 23, 24) from one source ([19]) are based on evaluation method option-2 + - One sample (sample 21) from one source ([19]) show a MCL gain of 3.20dB for SBFD, assuming 4 aggressor inter-site gNBs with 5dB INR for each inter-site gNB-gNB CLI, 4 aggressor UEs with 0dB INR for each UE-gNB interference, without UL resource muting + - One sample (sample 23) from one source ([19]) show a MCL gain of 6.70 dB for SBFD, assuming 4 aggressor inter-site gNBs with 5dB INR for each inter-site gNB-gNB CLI, 4 aggressor UEs with 0dB INR for each UE-gNB interference, with UL resource muting + - One sample (sample 22) from one source ([19]) shows a MCL gain of 0.50dB for SBFD, assuming 4 aggressor inter-site gNBs with 20dB INR for each inter-site gNB-gNB CLI, 4 aggressor UEs with 5dB INR for each UE-gNB interference, without UL resource muting + - One sample (sample 24) from one source ([19]) shows a MCL gain of 3.70dB for SBFD, assuming 4 aggressor inter-site gNBs with 20dB INR for each inter-site gNB-gNB CLI, 4 aggressor UEs with 5dB INR for each UE-gNB interference, with UL resource muting + +#### 7.3.2.1.2 Scheme-2 (SBFD with TBoMS PUSCH without joint channel estimation) + +For coverage performance evaluation of SBFD in FR1, 4 sources ([17], [28], [31], [32]) provided 13 samples for evaluation results, assuming SBFD with TBoMS PUSCH without joint channel estimation for SBFD(XXXXU), and single slot PUSCH transmission for legacy TDD (DDDSU). The following is observed: + +- One sample (sample 10) from one source ([28]) are based on evaluation method option-1 (Example-1) + - One sample (sample 10) from one source ([28]) show a MCL gain of 5.73dB for SBFD, assuming INR of co-site inter-sector interference as -5.44dB, total INR of all inter-site gNB-gNB CLI as 15.40dB, total INR of all UE-gNB interference as 23.30dB +- 12 samples (sample 1, 2, 3, 4, 5, 6, 7, 8, 9, 11, 12, 13) from 4 sources ([17], [28], [31], [32]) are based on evaluation method option-1 (Example-2) + - 4 samples (sample 1, 4, 7, 11) from 4 sources ([17], [28], [31], [32]) show a MCL gain of {4.40~6.12}dB for SBFD, assuming low load with $\Delta$ as {0.14~1.14}dB + - 4 samples (sample 2, 5, 8, 12) from 4 sources ([17], [28], [31], [32]) show a MCL gain of {4.00~5.79}dB for SBFD, assuming medium load with $\Delta$ as {0.43~1.46}dB + - 3 samples (sample 3, 6, 13) from 3 sources ([17], [28], [32]) show a MCL gain of {3.06~4.72}dB for SBFD, assuming high load with $\Delta$ as {1.45~2.19}dB + +- One sample (sample 9) from one source ([31]) show a MCL gain of 2.83dB for SBFD, assuming high load with $\Delta$ as 2.47dB + +### 7.3.2.1.3 Scheme-3 (PUSCH repetition type A with joint channel estimation) + +For coverage performance evaluation of SBFD in FR1, 5 sources ([17], [26], [28], [31], [32]) provided 16 samples for evaluation results, assuming PUSCH repetition type A with joint channel estimation for SBFD(XXXXU), and single slot PUSCH transmission for legacy TDD (DDDSU). The following is observed: + +- One sample (sample 11) from one source ([28]) are based on evaluation method option-1 (Example-1) + - One sample (sample 11) from one source ([28]) show a MCL gain of 6.26dB for SBFD, assuming INR of co-site inter-sector interference as -5.44dB, total INR of all inter-site gNB-gNB CLI as 15.40dB, total INR of all UE-gNB interference as 23.30dB +- 12 samples (sample 2, 3, 4, 5, 6, 7, 8, 9, 10, 12, 13, 14) from 4 sources ([17], [28], [31], [32]) are based on evaluation method option-1 (Example-2) + - 4 samples (sample 2, 5, 8, 12) from 4 sources ([17], [28], [31], [32]) show a MCL gain of {5.76~6.75}dB for SBFD, assuming low load with $\Delta$ as {0.14~1.14}dB + - 4 samples (sample 3, 6, 9, 13) from 4 sources ([17], [28], [31], [32]) show a MCL gain of {5.50~6.66}dB for SBFD, assuming medium load with $\Delta$ as {0.28~1.46}dB + - 4 samples (sample 4, 7, 10, 14) from 4 sources ([17], [28], [31], [32]) show a MCL gain of {4.23~5.94}dB for SBFD, assuming high load with $\Delta$ as {1.45~2.47}dB +- 3 samples (sample 15, 16, 17) from one source ([26]) are based on evaluation method option-1 (Example-3) + - One sample (sample 15) from one source ([26]) show a MCL gain of 5.88dB for SBFD, assuming low load + - One sample (sample 16) from one source ([26]) show a MCL gain of 5.50dB for SBFD, assuming medium load + - One sample (sample 17) from one source ([26]) show a MCL gain of 4.77dB for SBFD, assuming high load + +### 7.3.2.1.4 Scheme-4 (SBFD with TBoMS PUSCH with joint channel estimation) + +For coverage performance evaluation of SBFD in FR1, 5 sources ([17], [26], [28], [31], [32]) provided 16 samples for evaluation results, assuming SBFD with TBoMS PUSCH with joint channel estimation for SBFD(XXXXU), and single slot PUSCH transmission for legacy TDD (DDDSU). The following is observed: + +- One sample (sample 11) from one source ([28]) are based on evaluation method option-1 (Example-1) + - One sample (sample 11) from one source ([28]) show a MCL gain of 5.96dB for SBFD, assuming INR of co-site inter-sector interference as -5.44dB, total INR of all inter-site gNB-gNB CLI as 15.40dB, total INR of all UE-gNB interference as 23.30dB +- 12 samples (sample 2, 3, 4, 5, 6, 7, 8, 9, 10, 12, 13, 14) from 4 sources ([17], [28], [31], [32]) are based on evaluation method option-1 (Example-2) + - 4 samples (sample 2, 5, 8, 12) from 4 sources ([17], [28], [31], [32]) show a MCL gain of {5.19~6.35}dB for SBFD, assuming low load with $\Delta$ as {0.14~1.14}dB + - 4 samples (sample 3, 6, 9, 13) from 4 sources ([17], [28], [31], [32]) show a MCL gain of {5.07~5.99}dB for SBFD, assuming medium load with $\Delta$ as {0.43~1.46}dB + - 4 samples (sample 4, 7, 10, 14) from 4 sources ([17], [28], [31], [32]) show a MCL gain of {4.16~5.15}dB for SBFD, assuming high load with $\Delta$ as {1.45~2.47}dB +- 3 samples (sample 15, 16, 17) from one source ([26]) are based on evaluation method option-1 (Example-3) + - One sample (sample 15) from one source ([26]) show a MCL gain of 6.88dB for SBFD, assuming low load + - One sample (sample 16) from one source ([26]) show a MCL gain of 6.10dB for SBFD, assuming medium load + +- One sample (sample 17) from one source ([26]) show a MCL gain of 5.30dB for SBFD, assuming high load + +### 7.3.2.2 FR2-1 + +#### 7.3.2.2.1 Scheme-1 (PUSCH repetition type A without joint channel estimation) + +For coverage performance evaluation of SBFD in FR2-1, 4 sources ([36], [20], [28], [32]) provided 10 samples for evaluation results, assuming PUSCH repetition type A without joint channel estimation for SBFD(XXXXU), and single slot PUSCH transmission for legacy TDD (DDDSU). The following is observed: + +- 5 samples (sample 1, 2, 5, 6, 10) from 2 sources ([36], [28]) are based on evaluation method option-1 (Example-1) + - 5 samples (sample 1, 2, 5, 6, 10) from 2 sources ([36], [28]) show a MCL gain of {6.10~8.46}dB for SBFD, assuming INR of co-site inter-sector interference as {-0.25~22.00}dB, total INR of all inter-site gNB-gNB CLI as {-16.15~42.00}dB, total INR of all UE-gNB interference as {-3.50~22.44}dB +- 3 samples (sample 7, 8, 9) from one source ([32]) are based on evaluation method option-1 (Example-2) + - One sample (sample 7) from one source ([32]) show a MCL gain of 6.92dB for SBFD, assuming low load with $\Delta$ as 0.22dB + - One sample (sample 8) from one source ([32]) show a MCL gain of 6.26dB for SBFD, assuming medium load with $\Delta$ as 1.02dB + - One sample (sample 9) from one source ([32]) show a MCL gain of 5.86dB for SBFD, assuming high load with $\Delta$ as 1.51dB + +#### 7.3.2.2.2 Scheme-2 (SBFD with TBoMS PUSCH without joint channel estimation) + +For coverage performance evaluation of SBFD in FR2-1, 2 sources ([28], [32]) provided 4 samples for evaluation results, assuming SBFD with TBoMS PUSCH without joint channel estimation for SBFD(XXXXU), and single slot PUSCH transmission for legacy TDD (DDDSU). The following is observed: + +- One sample (sample 4) from one source ([28]) are based on evaluation method option-1 (Example-1) + - One sample (sample 4) from one source ([28]) show a MCL gain of 7.66dB for SBFD, assuming INR of co-site inter-sector interference as -1.17dB, total INR of all inter-site gNB-gNB CLI as -16.15dB, total INR of all UE-gNB interference as 22.44dB +- 3 samples (sample 1, 2, 3) from one source ([32]) are based on evaluation method option-1 (Example-2) + - One sample (sample 1) from one source ([32]) show a MCL gain of 5.63dB for SBFD, assuming low load with $\Delta$ as 0.22dB + - One sample (sample 2) from one source ([32]) show a MCL gain of 4.94dB for SBFD, assuming medium load with $\Delta$ as 1.02dB + - One sample (sample 3) from one source ([32]) show a MCL gain of 4.49dB for SBFD, assuming high load with $\Delta$ as 1.51dB + +#### 7.3.2.2.3 Scheme-3 (PUSCH repetition type A with joint channel estimation) + +For coverage performance evaluation of SBFD in FR2-1, 2 sources ([28], [32]) provided 4 samples for evaluation results, assuming PUSCH repetition type A with joint channel estimation for SBFD(XXXXU), and single slot PUSCH transmission for legacy TDD (DDDSU). The following is observed: + +- One sample (sample 4) from one source ([28]) are based on evaluation method option-1 (Example-1) + - One sample (sample 4) from one source ([28]) show a MCL gain of 8.76dB for SBFD, assuming INR of co-site inter-sector interference as -1.17dB, total INR of all inter-site gNB-gNB CLI as -16.15dB, total INR of all UE-gNB interference as 22.44dB +- 3 samples (sample 1, 2, 3) from one source ([32]) are based on evaluation method option-1 (Example-2) + +- One sample (sample 1) from one source ([32]) show a MCL gain of 7.01dB for SBFD, assuming low load with $\Delta$ as 0.22dB +- One sample (sample 2) from one source ([32]) show a MCL gain of 6.98dB for SBFD, assuming medium load with $\Delta$ as 1.02dB +- One sample (sample 3) from one source ([32]) show a MCL gain of 6.59dB for SBFD, assuming high load with $\Delta$ as 1.51dB + +#### 7.3.2.2.4 Scheme-4 (SBFD with TBoMS PUSCH with joint channel estimation) + +For coverage performance evaluation of SBFD in FR2-1, 2 sources ([28], [32]) provided 4 samples for evaluation results, assuming SBFD with TBoMS PUSCH with joint channel estimation for SBFD(XXXXU), and single slot PUSCH transmission for legacy TDD (DDDSU). The following is observed: + +- One sample (sample 4) from one source ([28]) are based on evaluation method option-1 (Example-1) + - One sample (sample 4) from one source ([28]) show a MCL gain of 7.82dB for SBFD, assuming INR of co-site inter-sector interference as -1.17dB, total INR of all inter-site gNB-gNB CLI as -16.15dB, total INR of all UE-gNB interference as 22.44dB +- 3 samples (sample 1, 2, 3) from one source ([32]) are based on evaluation method option-1 (Example-2) + - One sample (sample 1) from one source ([32]) show a MCL gain of 6.44dB for SBFD, assuming low load with $\Delta$ as 0.22dB + - One sample (sample 2) from one source ([32]) show a MCL gain of 5.81dB for SBFD, assuming medium load with $\Delta$ as 1.02dB + - One sample (sample 3) from one source ([32]) show a MCL gain of 5.38dB for SBFD, assuming high load with $\Delta$ as 1.51dB + +## 7.4 Performance evaluation results of schemes for SBFD + +### 7.4.1 Dynamic SBFD + +The detailed evaluation assumptions and results for dynamic SBFD compared to semi-static SBFD or dynamic TDD is provided in Annex B.3.1. + +UPT and latency gain/increase of dynamic SBFD compared to baseline (dynamic TDD or semi-static SBFD) for Indoor office (FR1) and Urban Macro (FR1) are summarized in sub-sections 7.4.1.1 and 7.4.1.2 respectively. For UPT, the gain is calculated as: $\text{Gain (\%)} = \text{dynamic SBFD UPT} / \text{baseline UPT} - 1$ . For Latency, the increase is calculated as: $\text{Increase (\%)} = \text{dynamic SBFD latency} / \text{baseline latency} - 1$ . + +Evaluation results of dynamic SBFD for Dense Urban Macro layer (FR1) from one source can be found in Annex B.3.1.3. + +For dynamic SBFD Option 2 (“dSBFD Opt 2” in Annex B.3.1), an ‘X’ symbol can be used as either an SBFD symbol or a full DL symbol. For dynamic SBFD Option 3 (“dSBFD Opt 3” in Annex B.3.1), an ‘X’ symbol can be used as an SBFD symbol, a full DL symbol or a full UL symbol. + +For dynamic SBFD, [40] and [33] determine whether an ‘X’ symbol is used as an SBFD symbol or a non-SBFD symbol (full DL symbol for dynamic SBFD Option 2 or full DL/UL symbol for dynamic SBFD Option 3) based on the required resources for DL/UL traffic per 5 slots. [41] determines whether an ‘X’ symbol is used as an SBFD symbol or a non-SBFD symbol (full DL symbol for dynamic SBFD Option 2 or full DL/UL symbol for dynamic SBFD Option 3) based on the DL/UL traffic availability per slot. [24] determines whether an ‘X’ symbol is used as an SBFD symbol or a non-SBFD symbol (full DL symbol for dynamic SBFD Option 2 or full DL/UL symbol for dynamic SBFD Option 3) based on the required resources for DL/UL traffic per slot. [21] determines whether an ‘X’ symbol is used as an SBFD symbol or a non-SBFD symbol (full DL symbol for dynamic SBFD Option 2) based on the required resources for DL/UL traffic and condition for BS-to-BS/UE-to-UE CLI handling per slot. + +For dynamic TDD, [40] and [33] determine whether an ‘F’ symbol is used as a DL symbol or an UL symbol based on the required resources for DL/UL traffic per 5 slots. [41] determines whether an ‘F’ symbol is used as a DL symbol or an UL symbol based on the DL/UL traffic availability per slot. + +For dynamic TDD, [40] does not assume gNB-gNB co-channel inter-PRB CLI modelling. [33] and [41] assume gNB-gNB co-channel inter-PRB CLI modelling. The power of gNB-gNB co-channel inter-PRB CLI experienced by the victim gNB on each receiver chain at one UL RB is calculated in the similar way as for SBFD, refer to Annex A.2.3. + +[21] assumes inter-cell coordinated scheduling for BS-to-BS/UE-to-UE CLI handling where switching from an SBFD symbol to non-SBFD symbol is done only when the expected BS-to-BS/UE-to-UE CLI values are lower than certain thresholds for both Indoor office (FR1) and Urban Macro (FR1). [33] assumes no CLI handling for Indoor office (FR1), and assumes no CLI handling and CLI handling for Urban Macro (FR1) and Dense Urban Macro layer (FR1), where only intra-cell coordinated scheduling for UE-UE CLI that is only one transmission direction (either DL or UL) is scheduled within the same cluster and different clusters can have same or different transmission directions for the evaluations with CLI handling. [41], [40] and [24] assume no CLI handling in the evaluations. + +### 7.4.1.1 Indoor office (FR1) + +5 sources provided the SLS evaluation results of dynamic SBFD for Indoor office (FR1). + +#### 7.4.1.1.1 Dynamic SBFD vs. dynamic TDD + +In this sub-section, UPT and latency gain/increase of dynamic SBFD compared to dynamic TDD for indoor office (FR1) are provided. Evaluation results of different slot configurations are summarized in 7.4.1.1.1.1 and 7.4.1.1.1.2 respectively. + +Evaluation results of slot configuration {DXXXU} for dynamic SBFD and {FFFFU} for dynamic TDD from one source can be found in the attached document "B.3.1\_Dynamic SBFD.zip". + +##### 7.4.1.1.1.1 Slot configuration {XXXU} vs. {FFFFU} + +In this sub-section, slot configurations {XXXU} and {FFFFU} are assumed for dynamic SBFD and dynamic TDD respectively. + +Large packet size is assumed for results in Table 7.4.1.1.1.1-1 and Table 7.4.1.1.1.1-2, and small packet size is assumed for results in Table 7.4.1.1.1.1-3. + +Dynamic SBFD Option 2 is assumed for results in Table 7.4.1.1.1.1-1, and dynamic SBFD Option 3 is assumed for results in Table 7.4.1.1.1.1-2 and 7.4.1.1.1.1-3. + +**Table 7.4.1.1.1.1-1: Indoor (FR1) dynamic SBFD vs. dynamic TDD, {XXXU} vs. {FFFFU} (dynamic SBFD Option 2, large packet size)** + +| | | [41] | | | [40] | | | +|----------------------------|------|----------|-------------|-----------|----------|-------------|-----------| +| | | Low load | Medium load | High load | Low load | Medium load | High load | +| DL average-UPT gain | Mean | -1.31% | -12.14% | -36.16% | 5.94% | 4.86% | 3.19% | +| | 5% | -1.66% | -17.87% | -85.59% | 3.19% | 2.81% | 2.24% | +| | 50% | -1.30% | -12.58% | -36.68% | 7.51% | 5.65% | 4.25% | +| | 95% | -1.64% | -8.22% | -20.23% | 4.07% | 7.71% | 3.06% | +| UL average-UPT gain | Mean | -39.65% | -28.86% | -7.17% | 5.17% | 5.35% | 3.79% | +| | 5% | -39.85% | -24.59% | 1.05% | 6.35% | 7.43% | 3.41% | +| | 50% | -39.81% | -28.89% | -4.43% | 5.81% | 5.09% | 3.42% | +| | 95% | -39.36% | -31.00% | -16.02% | 8.17% | 9.19% | 4.29% | +| DL packet-Latency increase | Mean | 1.47% | 20.31% | 245.32% | -6.94% | -5.05% | -4.38% | +| | 5% | 0.61% | 6.64% | 23.56% | -3.95% | -3.89% | -4.97% | +| | 50% | 1.59% | 16.49% | 76.06% | -5.23% | -5.39% | -4.10% | +| | 95% | 1.66% | 28.59% | 440.60% | -9.05% | -4.24% | -4.15% | +| UL packet-Latency increase | Mean | 61.56% | 30.97% | -5.58% | -4.16% | -4.64% | -3.00% | +| | 5% | 56.25% | 66.85% | 22.50% | 22.22% | 23.51% | 10.33% | +| | 50% | 79.61% | 29.95% | 0.67% | -5.30% | -7.89% | -4.87% | +| | 95% | 36.84% | 24.10% | -9.41% | -7.17% | -8.58% | -5.34% | + +**Table 7.4.1.1.1.1-2: Indoor (FR1) dynamic SBFD vs. dynamic TDD, {XXXU} vs. {FFFFU} (dynamic SBFD Option 3, large packet size)** + +| | | [41] | | [40] | | [33] | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|----------|-------------|----------|-------------|----------|-------------| +| | | Low load | Medium load | Low load | Medium load | Low load | Medium load | +| Simple description of key assumptions (RSI based on 1dB desense, Twice area & same TxRUs (Option 2), dynamic SBFD slot configuration {XXXU}, dynamic TDD slot configuration {FFFFU}, dynamic SBFD Option 3, DL: 0.5Mbytes, UL: 0.125Mbytes) | | | | | | | | + +| | | Low load | Medium load | High load | Low load | Medium load | High load | Low load | Medium load | High load | +|----------------------------|------|----------|-------------|-----------|----------|-------------|-----------|----------|-------------|-----------| +| DL average-UPT gain | Mean | -0.87% | -9.72% | -32.33% | -3.37% | -3.69% | -1.10% | 17.98% | 19.56% | 21.95% | +| | 5% | -0.63% | -14.56% | -81.86% | -3.87% | -4.46% | -1.45% | 15.14% | 19.32% | 64.10% | +| | 50% | -0.99% | -10.09% | -32.90% | -2.88% | -3.34% | -0.23% | 20.37% | 15.01% | 24.03% | +| | 95% | -1.31% | -6.70% | -18.02% | -1.40% | -3.92% | -1.77% | 18.41% | 20.38% | 19.01% | +| UL average-UPT gain | Mean | 0.09% | -0.81% | 8.10% | 6.48% | 6.74% | 5.02% | 2.74% | 5.18% | -0.90% | +| | 5% | -0.27% | -0.08% | 20.52% | 9.47% | 10.53% | 8.02% | 9.91% | 5.53% | -16.16% | +| | 50% | 0.31% | -0.65% | 10.63% | 7.13% | 5.55% | 5.46% | 2.26% | 4.92% | 0.63% | +| | 95% | 0.12% | -1.01% | 3.38% | 11.39% | 11.75% | 8.45% | 0.57% | 5.28% | 5.27% | +| DL packet-Latency increase | Mean | 1.03% | 16.27% | 201.71% | 1.90% | 4.06% | 2.03% | -14.70% | -19.94% | -46.50% | +| | 5% | 0.29% | 4.59% | 19.71% | 5.26% | 5.44% | 1.25% | -17.03% | -13.59% | -13.12% | +| | 50% | 1.02% | 13.04% | 63.14% | 3.77% | 3.70% | 1.99% | -15.76% | -15.75% | -22.29% | +| | 95% | 1.39% | 23.22% | 365.92% | -0.47% | 4.86% | 3.25% | -16.74% | -26.61% | -68.01% | +| UL packet-Latency increase | Mean | -0.65% | -2.56% | -21.63% | -4.68% | -7.72% | -5.58% | -2.57% | -3.79% | 18.08% | +| | 5% | 0.00% | 4.56% | 6.49% | 21.85% | 18.83% | 4.80% | -1.54% | -4.90% | -13.08% | +| | 50% | 0.59% | -0.72% | -12.75% | -7.03% | -11.08% | -5.82% | -2.88% | -7.36% | 6.58% | +| | 95% | -3.70% | -6.43% | -27.26% | -9.72% | -11.62% | -9.98% | -0.26% | 5.66% | 61.65% | + +Evaluation results of dynamic SBFD Option 3 assuming small packet size are summarized in Table 7.4.1.1.1.3. + +**Table 7.4.1.1.1.3: Indoor (FR1) dynamic SBFD vs. dynamic TDD, {XXXXU} vs. {FFFFU} (dynamic SBFD Option 3, small packet size)** + +| Simple description of key assumptions (RSI based on 1dB desense, Twice area & same TxRUs (Option 2), dynamic SBFD slot configuration {XXXXU}, dynamic TDD slot configuration {FFFFU}, dynamic SBFD Option 3, DL: 4Kbytes, UL: 1Kbytes) | | [33] | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----------|-------------|-----------| +| | | Low load | Medium load | High load | +| DL average-UPT gain | Mean | -10.87% | -10.65% | -8.82% | +| | 5% | -8.25% | -8.85% | 3.45% | +| | 50% | -10.73% | -10.84% | -10.90% | +| | 95% | -12.77% | -12.61% | -13.99% | +| UL average-UPT gain | Mean | 36.25% | 32.65% | 35.79% | +| | 5% | 31.05% | 22.41% | 20.32% | +| | 50% | 36.60% | 32.62% | 36.05% | +| | 95% | 40.13% | 43.42% | 46.51% | +| DL packet-Latency increase | Mean | 1.12% | -2.68% | -10.37% | +| | 5% | 47.14% | 44.08% | 36.76% | +| | 50% | 4.33% | 4.62% | 2.22% | +| | 95% | -4.67% | -9.82% | -20.20% | +| UL packet-Latency increase | Mean | -17.96% | -15.02% | -14.51% | +| | 5% | -44.39% | -43.08% | -44.22% | +| | 50% | -18.78% | -18.06% | -20.75% | +| | 95% | -1.15% | 6.91% | 25.14% | + +#### 7.4.1.1.1.2 Slot configuration {XXXXX} vs. {FFFFF} + +In this sub-section, slot configurations {XXXXX} and {FFFFF} are assumed for dynamic SBFD and dynamic TDD respectively. + +**Table 7.4.1.1.2-1: Indoor (FR1) dynamic SBFD vs. dynamic TDD, {XXXXX} vs. {FFFFF} (dynamic SBFD Option 3, large & small packet size)** + +| Simple description of key assumptions (RSI based on 1dB desense, Twice area & same TxRUs (Option 2), dynamic SBFD slot configuration {XXXXX}, dynamic TDD slot configuration {FFFFF}, dynamic SBFD Option 3) | | [33] | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|--------------------------|-------------|-----------|--------------------------------|-------------|-----------| +| | | DL: 4Kbytes, UL: 1Kbytes | | | DL: 0.5Mbytes, UL: 0.125Mbytes | | | +| | | Low load | Medium load | High load | Low load | Medium load | High load | +| DL average-UPT gain | Mean | -11.54% | -10.88% | -11.72% | 0.95% | 5.48% | 12.45% | + +| | | | | | | | | +|-----------------------------------|-------------|---------|---------|---------|---------|---------|---------| +| | 5% | -8.92% | -7.40% | -7.54% | 1.32% | 17.72% | 20.94% | +| | 50% | -11.27% | -10.37% | -11.08% | -0.14% | 6.75% | 13.26% | +| | 95% | -14.55% | -15.23% | -16.60% | 0.87% | 0.73% | 2.94% | +| UL average-UPT gain | Mean | 133.75% | 119.72% | 97.79% | 1.62% | 8.01% | 18.29% | +| | 5% | 131.64% | 123.78% | 119.00% | 1.24% | 7.95% | 31.10% | +| | 50% | 133.85% | 117.77% | 93.81% | 1.74% | 7.29% | 17.33% | +| | 95% | 136.94% | 121.71% | 91.61% | 1.35% | 9.02% | 18.06% | +| DL packet-Latency increase | Mean | -19.49% | -23.84% | -20.91% | -2.75% | -8.67% | -18.01% | +| | 5% | 48.80% | 44.41% | 38.24% | 0.15% | -0.63% | -2.94% | +| | 50% | 8.56% | 8.50% | 9.37% | 0.41% | -7.83% | -13.51% | +| | 95% | -58.34% | -62.36% | -57.60% | -10.32% | -14.08% | -27.30% | +| UL packet-Latency increase | Mean | -54.51% | -49.12% | -44.38% | -4.33% | -10.80% | -23.71% | +| | 5% | -57.28% | -57.31% | -55.37% | -0.17% | -3.21% | -6.28% | +| | 50% | -61.17% | -57.24% | -47.15% | 0.10% | -10.05% | -20.78% | +| | 95% | -34.61% | -28.36% | -41.62% | -15.75% | 3.59% | -27.26% | + +#### 7.4.1.1.1.3 Summary of the Observations + +For the following observations, UPT gain in the range of {-5%, 5%} is considered as similar UPT. + +For indoor scenario (FR1), for dynamic SBFD compared to dynamic TDD: + +- For slot configurations {XXXXU} for dynamic SBFD and {FFFFU} for dynamic TDD, + - In case of large packet size and dynamic SBFD option 2, based on results from 2 sources, + - dynamic SBFD has lower or higher mean and 5% UL Average-UPT for low and medium load levels and similar or lower mean and 5% UL Average-UPT for high load level, + - and dynamic SBFD has similar or higher mean DL Average-UPT for low load level, similar 5% DL Average-UPT for low load level, and similar or lower mean and 5% DL Average-UPT for medium and high load levels. + - In case of large packet size and dynamic SBFD option 3, based on results from 3 sources, + - dynamic SBFD has similar or higher mean and 5% UL Average-UPT for low and medium load levels, and higher, similar or lower mean and 5% UL Average-UPT for high load level, + - and dynamic SBFD has similar or higher mean and 5% DL Average-UPT for low load level, and similar, higher or lower mean and 5% DL Average-UPT for medium and high load levels. + - In case of small packet size and dynamic SBFD option 3, based on results from 1 source, + - dynamic SBFD has higher mean and 5% UL Average-UPT for all load levels, + - and dynamic SBFD has similar or lower mean and 5% DL Average-UPT for all load levels. +- For slot configurations {XXXXX} for dynamic SBFD and {FFFFF} for dynamic TDD, + - In case of large packet size and dynamic SBFD option 3, based on results from 1 source, + - dynamic SBFD has similar mean and 5% UL Average-UPT for low load level and higher mean and 5% UL Average-UPT for medium and high load levels, + - and dynamic SBFD has similar mean and 5% DL Average-UPT for low load level and higher mean and 5% DL Average-UPT for medium and high load levels. + - In case of small packet size and dynamic SBFD option 3, based on results from 1 source, + - dynamic SBFD has higher mean and 5% UL Average-UPT for all load levels, + +- and dynamic SBFD has lower mean and 5% DL Average-UPT for all load levels. + +#### 7.4.1.1.2 Dynamic SBFD vs. semi-static SBFD + +In this sub-section, UPT and latency gain/increase of dynamic SBFD compared to semi-static SBFD for indoor office (FR1) are provided. Evaluation results of different SBFD slot configurations are summarized in 7.4.1.1.2.1 and 7.4.1.1.2.2 respectively. + +##### 7.4.1.1.2.1 SBFD slot configuration {XXXXU} + +In this sub-section, SBFD slot configuration {XXXXU} is assumed. + +Large packet size is assumed for results in Table 7.4.1.1.2.1-1 and Table 7.4.1.1.2.1-2, and small packet size is assumed for results in Table 7.4.1.1.2.1-3. + +Dynamic SBFD Option 2 is assumed for results in Table 7.4.1.1.2.1-1, and dynamic SBFD Option 3 is assumed for results in Table 7.4.1.1.2.1-2 and 7.4.1.1.2.1-3. + +**Table 7.4.1.1.2.1-1: Indoor (FR1) dynamic SBFD vs. semi-static SBFD, {XXXXU} (dynamic SBFD Option 2, large packet size)** + +| Simple description of key assumptions (RSI based on 1dB desense, Twice area & same TxRUs (Option 2), SBFD slot configuration {XXXXU}, dynamic SBFD Option 2, DL: 0.5Mbytes, UL: 0.125Mbytes) | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----------|-------------|-----------|----------|-------------|-----------|----------|-------------|-----------| +| | | [21] | | | [24] | | | [41] | | | +| | | Low load | Medium load | High load | Low load | Medium load | High load | Low load | Medium load | High load | +| DL average-UPT gain | Mean | 34.80% | 35.10% | 51.60% | 34.85% | 44.29% | 50.40% | 32.31% | 45.05% | 47.33% | +| | 5% | 35.40% | 37.30% | 35.50% | 35.32% | 67.12% | 144.63% | 31.98% | 65.72% | -40.59% | +| | 50% | 34.50% | 35.60% | 53.40% | 34.83% | 43.50% | 58.37% | 31.78% | 46.97% | 70.82% | +| | 95% | | | | 34.36% | 36.27% | 28.61% | 32.89% | 31.93% | 39.76% | +| UL average-UPT gain | Mean | -16.10% | -25.00% | -37.50% | -0.06% | 0.12% | 0.27% | -4.49% | -29.04% | -43.12% | +| | 5% | -16.40% | -27.30% | -45.80% | -0.05% | -0.55% | -0.30% | -7.22% | -37.08% | -58.33% | +| | 50% | -15.90% | -25.60% | -38.40% | 0.02% | 0.49% | 0.46% | -4.62% | -30.00% | -44.10% | +| | 95% | | | | -0.04% | -0.04% | 0.39% | -2.61% | -20.12% | -32.18% | +| DL packet-Latency increase | Mean | -25.93% | -26.47% | -29.79% | -26.49% | -37.78% | -57.68% | -24.31% | -39.14% | -31.32% | +| | 5% | -25.00% | -25.00% | -20.00% | -27.43% | -26.16% | -24.23% | -26.96% | -23.70% | -26.11% | +| | 50% | -22.22% | -25.00% | -32.14% | -25.19% | -34.30% | -39.31% | -23.82% | -34.35% | -27.25% | +| | 95% | | | | -26.38% | -44.11% | -67.34% | -25.48% | -41.73% | -36.67% | +| UL packet-Latency increase | Mean | 21.21% | 35.71% | 69.74% | 0.31% | 0.17% | 0.19% | 6.03% | 50.97% | 111.33% | +| | 5% | 0.00% | 25.00% | 66.67% | 0.00% | 0.00% | 0.00% | 1.17% | 23.24% | 46.43% | +| | 50% | 16.67% | 42.86% | 61.54% | -0.01% | -0.04% | -0.05% | 4.19% | 46.95% | 87.61% | +| | 95% | | | | 2.37% | 0.21% | 2.55% | 10.70% | 68.89% | 149.63% | + +**Table 7.4.1.1.2.1-2: Indoor (FR1) dynamic SBFD vs. semi-static SBFD, {XXXXU} (dynamic SBFD Option 3, large packet size)** + +| Simple description of key assumptions (RSI based on 1dB desense, Twice area & same TxRUs (Option 2), SBFD slot configuration {XXXXU}, dynamic SBFD Option 3, DL: 0.5Mbytes, UL: 0.125Mbytes) | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----------|-------------|-----------|----------|-------------|-----------| +| | | [33] | | | [41] | | | +| | | Low load | Medium load | High load | Low load | Medium load | High load | +| DL average-UPT gain | Mean | 19.30% | 18.43% | 18.70% | 32.90% | 49.05% | 56.18% | +| | 5% | 1.78% | 5.96% | 38.30% | 33.37% | 72.40% | -25.17% | +| | 50% | 20.09% | 13.55% | 15.33% | 32.19% | 51.14% | 81.01% | +| | 95% | 26.38% | 28.01% | 27.96% | 33.33% | 34.12% | 43.62% | +| UL average-UPT gain | Mean | 27.08% | 7.86% | -22.54% | 58.40% | -1.07% | -33.77% | +| | 5% | 28.25% | 14.21% | -27.26% | 53.82% | -16.62% | -50.30% | +| | 50% | 26.32% | 7.47% | -20.45% | 58.96% | -2.20% | -35.29% | +| | 95% | 27.51% | 4.14% | -23.16% | 60.81% | 14.60% | -16.51% | +| DL packet-Latency increase | Mean | -14.42% | -15.00% | -29.78% | -24.64% | -41.19% | -39.99% | +| | 5% | -23.45% | -19.42% | -16.77% | -27.19% | -25.17% | -28.42% | +| | 50% | -12.73% | -12.43% | -16.72% | -24.25% | -36.30% | -32.58% | +| | 95% | -14.32% | -16.62% | -37.88% | -25.68% | -44.16% | -45.42% | +| UL packet-Latency | Mean | -12.15% | 1.80% | 55.99% | -34.80% | 12.32% | 75.39% | + +| | | | | | | | | +|----------|-----|---------|---------|--------|---------|---------|---------| +| increase | 5% | -44.60% | -28.43% | -5.42% | -35.25% | -22.76% | 27.29% | +| | 50% | -11.26% | 4.42% | 50.65% | -41.65% | 12.26% | 62.60% | +| | 95% | -0.02% | 8.73% | 99.72% | -22.09% | 27.34% | 100.45% | + +**Table 7.4.1.1.2.1-3: Indoor (FR1) dynamic SBFD vs. semi-static SBFD, {XXXXU} (dynamic SBFD Option 3, small packet size)** + +| Simple description of key assumptions (RSI based on 1dB desense, Twice area & same TxRUs (Option 2), SBFD slot configuration {XXXXU}, dynamic SBFD Option 3, DL: 4Kbytes, UL: 1Kbytes) | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-------------|-------------|-----------|--|--|--| +| | | [33] | | | | | | +| | | Low load | Medium load | High load | | | | +| DL average-UPT gain | Mean | 1.63% | 1.13% | 3.80% | | | | +| | 5% | 1.20% | 0.49% | 18.12% | | | | +| | 50% | 1.61% | 0.75% | 1.07% | | | | +| | 95% | 2.82% | 2.62% | 1.75% | | | | +| UL average-UPT gain | Mean | -36.25% | -30.41% | -21.12% | | | | +| | 5% | -38.67% | -34.53% | -30.06% | | | | +| | 50% | -36.02% | -30.32% | -20.15% | | | | +| | 95% | -35.00% | -26.71% | -17.04% | | | | +| DL packet-Latency increase | Mean | 9.07% | 7.30% | -4.54% | | | | +| | 5% | -3.56% | -2.24% | -1.85% | | | | +| | 50% | -2.15% | -1.88% | -4.07% | | | | +| | 95% | 69.31% | 59.50% | -13.33% | | | | +| UL packet-Latency increase | Mean | 72.03% | 51.27% | 31.59% | | | | +| | 5% | 10.17% | 11.21% | 8.10% | | | | +| | 50% | 90.00% | 65.60% | 37.60% | | | | +| | 95% | 68.33% | 37.26% | 33.31% | | | | + +7.4.1.1.2.2 SBFD slot configuration {XXXX} + +In this sub-section, SBFD slot configuration {XXXX} is assumed. + +Large packet size is assumed for results in Table 7.4.1.1.2.2-1 and small packet size is assumed for results in Table 7.4.1.1.2.2-2. + +**Table 7.4.1.1.2.2-1: Indoor (FR1) dynamic SBFD vs. semi-static SBFD, {XXXX} (dynamic SBFD Option 3, large packet size)** + +| Simple description of key assumptions (RSI based on 1dB desense, Twice area & same TxRUs (Option 2), SBFD slot configuration {XXXX}, dynamic SBFD Option 3, DL: 0.5Mbytes, UL: 0.125Mbytes) | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-------------|-------------|-----------|-------------|-------------|-----------| +| | | [24] | | | [33] | | | +| | | Low load | Medium load | High load | Low load | Medium load | High load | +| DL average-UPT gain | Mean | 32.65% | 35.00% | 31.96% | 10.49% | 9.87% | 10.60% | +| | 5% | 33.23% | 39.11% | 44.69% | 6.47% | 11.10% | 8.71% | +| | 50% | 32.39% | 34.88% | 31.75% | 8.73% | 9.33% | 10.31% | +| | 95% | 32.50% | 32.22% | 27.02% | 16.00% | 14.05% | 12.84% | +| UL average-UPT gain | Mean | 264.37% | 253.52% | 201.41% | 109.34% | 92.93% | 77.47% | +| | 5% | 255.85% | 238.76% | 161.13% | 119.78% | 112.31% | 96.01% | +| | 50% | 262.11% | 254.31% | 204.02% | 107.47% | 92.85% | 82.28% | +| | 95% | 271.38% | 264.72% | 230.10% | 106.69% | 79.87% | 62.71% | +| DL packet-Latency increase | Mean | -24.96% | -27.90% | -25.87% | -8.04% | -9.59% | -12.61% | +| | 5% | -25.20% | -25.16% | -23.97% | -17.87% | -15.41% | -10.28% | +| | 50% | -24.14% | -23.32% | -27.86% | -8.00% | -6.27% | -8.72% | + +| | | | | | | | | +|-----------------------------------|-------------|---------|---------|---------|---------|---------|---------| +| | 95% | -29.28% | -29.19% | -28.16% | -11.11% | -16.09% | -14.39% | +| UL packet-Latency increase | Mean | -72.13% | -68.95% | -54.04% | -48.60% | -45.79% | -40.45% | +| | 5% | -73.79% | -73.74% | -73.54% | -66.28% | -56.86% | -48.13% | +| | 50% | -72.25% | -71.63% | -57.60% | -43.31% | -45.83% | -41.12% | +| | 95% | -72.62% | -60.95% | -48.69% | -40.03% | -37.04% | -27.95% | + +**Table 7.4.1.1.2.2-2: Indoor (FR1) dynamic SBFD vs. semi-static SBFD, {XXXXX} (dynamic SBFD Option 3, small packet size)** + +| Simple description of key assumptions (RSI based on 1dB desense, Twice area & same TxRUs (Option 2), SBFD slot configuration {XXXXX}, dynamic SBFD Option 3, DL: 4Kbytes, UL: 1Kbytes) | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------|--------------------|------------------| +| | | [33] | | | +| | | Low load | Medium load | High load | +| DL average-UPT gain | Mean | -1.17% | -2.02% | -5.27% | +| | 5% | -1.70% | -2.02% | -9.21% | +| | 50% | -0.89% | -1.91% | -4.46% | +| | 95% | -1.34% | -2.22% | -3.89% | +| UL average-UPT gain | Mean | -6.64% | 1.32% | 17.53% | +| | 5% | -6.39% | 1.72% | 29.42% | +| | 50% | -6.49% | 0.91% | 16.23% | +| | 95% | -5.92% | 1.61% | 9.26% | +| DL packet-Latency increase | Mean | 3.17% | 3.58% | 8.45% | +| | 5% | 0.05% | 0.19% | 0.75% | +| | 50% | 1.16% | 2.03% | 5.32% | +| | 95% | 27.01% | 7.44% | 11.66% | +| UL packet-Latency increase | Mean | 9.47% | -4.23% | -28.84% | +| | 5% | 0.91% | 0.27% | -1.96% | +| | 50% | 6.64% | 0.00% | -21.09% | +| | 95% | 11.53% | -7.92% | -45.97% | + +#### 7.4.1.1.2.3 Summary of the Observations + +For the following observations, UPT gain in the range of {-5%, 5%} is considered as similar UPT. + +For indoor scenario (FR1), for dynamic SBFD compared to semi-static SBFD: + +- For slot configurations {XXXXU} for dynamic SBFD and semi-static SBFD, + - In case of large packet size and dynamic SBFD option 2, based on results from 3 sources, + - dynamic SBFD has similar or lower mean and 5% UL Average-UPT for all load levels, + - and dynamic SBFD has higher mean and 5% DL Average-UPT for all load levels, except one source reported lower 5% DL Average-UPT for high load level. + - In case of large packet size and dynamic SBFD option 3, based on results from 2 sources, + - dynamic SBFD has higher mean and 5% UL Average-UPT for low load level, similar or higher mean UL Average-UPT for medium load level, higher or lower 5% UL Average-UPT for medium load level, and lower mean and 5% UL Average-UPT for high load level, + - and dynamic SBFD has higher mean DL Average-UPT for low load level, similar or higher 5% DL Average-UPT for low load level, higher mean and 5% DL Average-UPT for medium load level, higher mean DL Average-UPT for high load level, and higher or lower 5% DL Average-UPT for high load level. + - In case of small packet size and dynamic SBFD option 3, based on results from 1 source, + +- dynamic SBFD has lower mean and 5% UL Average-UPT for all load levels, +- and dynamic SBFD has similar mean and 5% DL Average-UPT for all load levels, except higher 5% DL Average-UPT for high load level. +- For slot configurations {XXXXX} for dynamic SBFD and semi-static SBFD, + - In case of large packet size and dynamic SBFD option 3, based on results from 2 sources, + - dynamic SBFD has higher mean and 5% UL Average-UPT for all load levels, + - and dynamic SBFD has higher mean and 5% DL Average-UPT for all load levels. + - In case of small packet size and dynamic SBFD option 3, based on results from 1 source, + - dynamic SBFD has lower mean and 5% UL Average-UPT for low load level, similar mean and 5% UL Average-UPT for medium load level, and higher mean and 5% UL Average-UPT for high load level, + - and dynamic SBFD has similar mean and 5% DL Average-UPT for low and medium load levels and lower mean and 5% DL Average-UPT for high load level. + +### 7.4.1.2 Urban Macro (FR1) + +3 sources provided the SLS evaluation results of dynamic SBFD for Urban Macro (FR1). + +The co-site spatial isolation + digital isolation assumed by [41], [21] and [33] are 93dB, 110dB and 100dB respectively. + +#### 7.4.1.2.1 Dynamic SBFD vs. dynamic TDD + +In this sub-section, UPT and latency gain/increase of dynamic SBFD compared to dynamic TDD for Urban Macro (FR1) are provided. Evaluation results of different slot configurations are summarized in 7.4.1.2.1.1 and 7.4.1.2.1.2 respectively. + +##### 7.4.1.2.1.1 Slot configuration {XXXXU} vs. {FFFFU} + +In this sub-section, slot configurations {XXXXU} and {FFFFU} are assumed for dynamic SBFD and dynamic TDD respectively. + +Dynamic SBFD Option 2 is assumed for results in Table 7.4.1.2.1.1-1, and dynamic SBFD Option 3 is assumed for results in Table 7.4.1.2.1.1-2 and 7.4.1.2.1.1-3. + +No CLI handling is assumed for results in 7.4.1.2.1.1-1 and 7.4.1.2.1.1-2, and CLI handling is assumed for results in 7.4.1.2.1.1-3. + +**Table 7.4.1.2.1.1-1: Urban Macro (FR1) dynamic SBFD vs. dynamic TDD, {XXXXU} vs. {FFFFU} (dynamic SBFD Option 2, w/o CLI handling)** + +| Simple description of key assumptions (RSI based on 1dB desense, Twice area & same TxRUs (Option 2), dynamic SBFD slot configuration {XXXXU}, dynamic TDD slot configuration {FFFFU}, dynamic SBFD Option 2, DL: 0.5Mbytes, UL: 0.125Mbytes) | | [41] | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------|--------------------|------------------| +| | | Low load | Medium load | High load | +| DL average-UPT gain | Mean | -4.42% | -21.32% | -44.09% | +| | 5% | -5.17% | -28.32% | -69.51% | +| | 50% | -5.03% | -23.03% | -51.10% | +| | 95% | -2.60% | -13.71% | -27.91% | +| UL average-UPT gain | Mean | -28.33% | 6.38% | 11.01% | +| | 5% | 17.55% | 1.32% | -6.96% | +| | 50% | -26.36% | 8.25% | 12.05% | +| | 95% | -33.24% | 6.60% | 10.53% | +| DL packet-Latency increase | Mean | 6.30% | 44.90% | 268.14% | +| | 5% | 1.03% | 14.08% | 35.97% | +| | 50% | 6.00% | 33.69% | 110.47% | + +| | | | | | +|-----------------------------------|-------------|--------|--------|---------| +| | 95% | 10.50% | 56.63% | 437.25% | +| UL packet-Latency increase | Mean | 1.32% | -4.73% | -9.02% | +| | 5% | 86.34% | -7.54% | -7.44% | +| | 50% | 17.64% | -8.07% | -14.67% | +| | 95% | -5.70% | -5.07% | -6.33% | + +**Table 7.4.1.2.1.1-2: Urban Macro (FR1) dynamic SBFD vs. dynamic TDD, {XXXXU} vs. {FFFFU} (dynamic SBFD Option 3, w/o CLI handling)** + +| Simple description of key assumptions (RSI based on 1dB desense, Twice area & same TxRUs (Option 2), dynamic SBFD slot configuration {XXXXU}, dynamic TDD slot configuration {FFFFU}, dynamic SBFD Option 3, DL: 0.5Mbytes, UL: 0.125Mbytes) | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------|--------------------|------------------|-----------------|--------------------|------------------| +| | | [41] | | | [33] | | | +| | | Low load | Medium load | High load | Low load | Medium load | High load | +| DL average-UPT gain | Mean | -4.49% | -22.00% | -44.17% | 4.45% | 1.88% | -2.41% | +| | 5% | -6.36% | -30.88% | -69.86% | -8.95% | -13.39% | -33.80% | +| | 50% | -4.81% | -23.64% | -51.30% | 3.25% | 2.40% | -6.87% | +| | 95% | -2.43% | -14.06% | -28.01% | 7.12% | 4.23% | 6.61% | +| UL average-UPT gain | Mean | 4.14% | 2.76% | 9.28% | -25.46% | -22.18% | -38.22% | +| | 5% | 8.47% | -0.31% | -1.13% | 54.65% | 29.34% | 131.48% | +| | 50% | 3.91% | 3.92% | 11.87% | -40.14% | -41.40% | -65.05% | +| | 95% | 4.52% | 3.78% | 7.73% | -1.92% | -2.54% | -22.35% | +| DL packet-Latency increase | Mean | 6.26% | 44.11% | 264.61% | 18.08% | -30.64% | 56.10% | +| | 5% | 1.08% | 15.07% | 36.30% | -6.04% | -6.71% | -3.88% | +| | 50% | 6.16% | 35.40% | 110.65% | -2.01% | -2.85% | 5.42% | +| | 95% | 10.61% | 56.37% | 425.64% | 50.30% | 72.89% | 319.31% | +| UL packet-Latency increase | Mean | -3.71% | -2.93% | -8.07% | 96.13% | 127.44% | 249.35% | +| | 5% | -3.47% | -3.01% | -5.22% | 9.74% | 8.50% | 35.38% | +| | 50% | -2.90% | -4.45% | -12.64% | 59.01% | 73.46% | 207.83% | +| | 95% | -5.82% | -3.52% | -6.25% | 213.62% | 196.12% | 308.43% | + +**Table 7.4.1.2.1.1-3: Urban Macro (FR1) dynamic SBFD vs. dynamic TDD, {XXXXU} vs. {FFFFU} (dynamic SBFD Option 3, w/ CLI handling)** + +| Simple description of key assumptions (RSI based on 1dB desense, Twice area & same TxRUs (Option 2), dynamic SBFD slot configuration {XXXXU}, dynamic TDD slot configuration {FFFFU}, dynamic SBFD Option 3, DL: 0.5Mbytes, UL: 0.125Mbytes) | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------|--------------------|------------------| +| | | [33] | | | +| | | Low load | Medium load | High load | +| DL average-UPT gain | Mean | 8.39% | 2.22% | -10.33% | +| | 5% | 16.86% | -6.56% | -13.16% | +| | 50% | 6.83% | 6.10% | -9.37% | +| | 95% | 7.99% | 3.82% | -7.28% | +| UL average-UPT gain | Mean | -25.50% | -22.36% | -23.18% | +| | 5% | 109.17% | 29.37% | 108.50% | +| | 50% | -38.93% | -40.04% | -59.58% | +| | 95% | -3.10% | -0.46% | 2.59% | +| DL packet-Latency increase | Mean | 5.09% | -24.33% | -2.37% | +| | 5% | -6.17% | -6.84% | 3.50% | +| | 50% | -6.65% | -1.82% | 15.44% | +| | 95% | 54.92% | 14.34% | 64.81% | +| UL packet-Latency increase | Mean | 59.05% | 118.03% | 127.40% | + +| | | | | | +|--|------------|---------|---------|---------| +| | 5% | 12.96% | 8.61% | 0.28% | +| | 50% | 62.32% | 65.34% | 150.58% | +| | 95% | 154.39% | 184.25% | 104.27% | + +#### 7.4.1.2.1.2 Slot configuration {XXXXX} vs. {FFFFF} + +In this sub-section, slot configurations {XXXXX} and {FFFFF} are assumed for dynamic SBFD and dynamic TDD respectively. + +**Table 7.4.1.2.1.2-1: Urban Macro (FR1) dynamic SBFD vs. dynamic TDD, {XXXXX} vs. {FFFFF} (dynamic SBFD Option 3, w/ & w/o CLI handling)** + +| Simple description of key assumptions (RSI based on 1dB desense, Twice area & same TxRUs (Option 2), dynamic SBFD slot configuration {XXXXX}, dynamic TDD slot configuration {FFFFF}, dynamic SBFD Option 3, DL: 0.5Mbytes, UL: 0.125Mbytes) | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------------------|--------------------|------------------|------------------------|--------------------|------------------| +| | | [33] | | | | | | +| | | w/o CLI handling | | | w/ CLI handling | | | +| | | Low load | Medium load | High load | Low load | Medium load | High load | +| DL average-UPT gain | Mean | 0.13% | -7.34% | -21.55% | 3.87% | -2.43% | -16.13% | +| | 5% | -24.40% | -26.88% | -91.68% | -14.31% | -14.02% | -29.74% | +| | 50% | -1.31% | -8.67% | -28.97% | 3.99% | -2.38% | -19.02% | +| | 95% | 7.22% | -1.17% | 3.54% | 7.56% | 5.11% | -6.69% | +| UL average-UPT gain | Mean | -29.87% | -31.66% | -51.62% | -25.21% | -23.09% | -25.99% | +| | 5% | -36.57% | -14.79% | -92.39% | -10.41% | 8.05% | 57.91% | +| | 50% | -46.89% | -51.81% | -68.51% | -35.55% | -35.74% | -55.15% | +| | 95% | -4.09% | -4.24% | -40.53% | -3.65% | -1.66% | -10.72% | +| DL packet-Latency increase | Mean | 28.63% | 88.41% | 736.77% | 18.63% | 19.34% | 85.39% | +| | 5% | -7.69% | -6.50% | 7.86% | -7.79% | -7.18% | 14.42% | +| | 50% | 7.41% | 9.60% | 27.00% | -0.74% | 4.72% | 20.91% | +| | 95% | 91.81% | 358.29% | 3270.52% | 61.15% | 44.66% | 246.37% | +| UL packet-Latency increase | Mean | 133.68% | 133.39% | 579.20% | 103.30% | 92.62% | 97.43% | +| | 5% | 11.88% | 16.04% | 78.16% | 10.18% | 7.21% | 22.06% | +| | 50% | 98.37% | 110.64% | 169.36% | 61.73% | 56.17% | 124.49% | +| | 95% | 188.06% | 132.99% | 747.40% | 187.23% | 106.61% | 28.04% | + +#### 7.4.1.2.1.3 Summary of the Observations + +For the following observations, UPT gain in the range of {-5%, 5%} is considered as similar UPT. + +For Urban Macro (FR1), for dynamic SBFD compared to dynamic TDD: + +- For slot configurations {XXXXU} for dynamic SBFD and {FFFFU} for dynamic TDD, + - In case of large packet size and dynamic SBFD option 2 w/o CLI handling, based on results from 1 source, + - dynamic SBFD has higher or lower mean and 5% UL Average-UPT for all load levels, except similar 5% UL Average-UPT for medium load level, + - and dynamic SBFD has lower mean and 5% DL Average-UPT for all load levels, except similar mean DL Average-UPT for low load level. + - In case of large packet size and dynamic SBFD option 3 w/o CLI handling, based on results from 2 sources, + - dynamic SBFD has similar, higher or lower mean and 5% UL Average-UPT for all load levels, + - and dynamic SBFD has similar or lower mean and 5% DL Average-UPT for all load levels. + - In case of large packet size and dynamic SBFD option 3 w/ CLI handling, based on results from 1 source, + +- dynamic SBFD has lower mean UL Average-UPT for all load levels, and higher 5% UL Average-UPT for all load levels, +- and dynamic SBFD has higher mean and 5% DL Average-UPT for low load level, similar or lower mean and 5% DL Average-UPT for medium load level and lower mean and 5% DL Average-UPT for high load level. +- For slot configurations {XXXXX} for dynamic SBFD and {FFFFF} for dynamic TDD, + - In case of large packet size and dynamic SBFD option 3 w/o CLI handling, based on results from 1 source, + - dynamic SBFD has lower mean and 5% UL Average-UPT for all load levels, + - and dynamic SBFD has lower mean and 5% DL Average-UPT for all load levels, except similar mean DL Average-UPT for low load level. + - In case of large packet size and dynamic SBFD option 3 w/ CLI handling, based on results from 1 source, + - dynamic SBFD has lower mean UL Average-UPT for all load levels, lower 5% UL Average-UPT for low load level, and higher 5% UL Average-UPT for medium and high load levels. + - and dynamic SBFD has lower mean and 5% DL Average-UPT for all load levels, except similar mean DL Average-UPT for low load level. + +#### 7.4.1.2.2 Dynamic SBFD vs. semi-static SBFD + +In this sub-section, UPT and latency gain/increase of dynamic SBFD compared to semi-static SBFD for Urban Macro (FR1) are provided. Evaluation results of different SBFD slot configurations are summarized in 7.4.1.2.2.1 and 7.4.1.2.2.2 respectively. + +##### 7.4.1.2.2.1 SBFD slot configuration {XXXXU} + +In this sub-section, SBFD slot configuration {XXXXU} is assumed. + +Dynamic SBFD Option 2 is assumed for results in Table 7.4.1.2.2.1-1, and dynamic SBFD Option 3 is assumed for results in Table 7.4.1.2.2.1-2 and 7.4.1.2.2.1-3. + +For results in Table 7.4.1.2.2.1-1, two sources assume CLI handling and no CLI handling respectively. No CLI handling is assumed for results in 7.4.1.2.2.1-2, and CLI handling is assumed for results in 7.4.1.2.2.1-3. + +**Table 7.4.1.2.2.1-1: Urban Macro (FR1) dynamic SBFD vs. semi-static SBFD, {XXXXU} (dynamic SBFD Option 2, w/ & w/o CLI handling)** + +| Simple description of key assumptions (RSI based on 1dB desense, Twice area & same TxRUs (Option 2), SBFD slot configuration {XXXXU}, dynamic SBFD Option 2, DL: 0.5Mbytes, UL: 0.125Mbytes) | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------------------------|--------------------|------------------|--------------------------------|--------------------|------------------| +| | | [21] (w/ CLI handling) | | | [41] (w/o CLI handling) | | | +| | | Low load | Medium load | High load | Low load | Medium load | High load | +| DL average-UPT gain | Mean | 19.60% | 9.80% | -5.80% | 27.59% | 21.20% | 19.48% | +| | 5% | 14.00% | 15.80% | 15.00% | 29.06% | 28.77% | 0.71% | +| | 50% | 17.40% | 8.90% | -8.30% | 25.25% | 21.64% | 23.31% | +| | 95% | | | | 31.78% | 21.84% | 17.87% | +| UL average-UPT gain | Mean | -9.50% | -4.10% | -1.20% | -19.52% | -22.38% | -19.99% | +| | 5% | -2.70% | 1.40% | -0.30% | -32.74% | -20.56% | -8.99% | +| | 50% | -16.70% | -4.60% | -1.00% | -22.00% | -24.09% | -24.23% | +| | 95% | | | | -15.84% | -19.71% | -17.78% | +| DL packet-Latency increase | Mean | -16.95% | -10.14% | 1.24% | -22.49% | -22.81% | -0.54% | +| | 5% | -25.00% | -25.00% | 0.00% | -24.77% | -16.28% | -12.77% | +| | 50% | -11.11% | -10.00% | 5.26% | -18.74% | -18.69% | -16.04% | +| | 95% | | | | -24.10% | -23.36% | 1.99% | +| UL packet-Latency increase | Mean | 7.58% | 0.00% | -1.71% | 25.44% | 15.60% | 16.78% | +| | 5% | 0.00% | 16.67% | 0.00% | 13.19% | 22.01% | 16.19% | + +| | | | | | | | | +|--|------------|--------|-------|-------|--------|--------|--------| +| | 50% | 20.00% | 0.00% | 0.00% | 29.37% | 37.65% | 38.80% | +| | 95% | | | | 30.65% | 7.10% | 8.82% | + +**Table 7.4.1.2.2.1-2: Urban Macro (FR1) dynamic SBFD vs. semi-static SBFD, {XXXXU} (dynamic SBFD Option 3, w/o CLI handling)** + +| Simple description of key assumptions (RSI based on 1dB desense, Twice area & same TxRUs (Option 2), SBFD slot configuration {XXXXU}, dynamic SBFD Option 3, DL: 0.5Mbytes, UL: 0.125Mbytes) | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------|--------------------|------------------|-----------------|--------------------|------------------| +| | | [33] | | | [41] | | | +| | | Low load | Medium load | High load | Low load | Medium load | High load | +| DL average-UPT gain | Mean | 7.76% | -0.70% | 31.62% | 27.49% | 20.14% | 19.32% | +| | 5% | -4.74% | -12.69% | 829.06% | 27.45% | 24.18% | -0.44% | +| | 50% | 7.42% | -3.88% | 46.53% | 25.54% | 20.67% | 22.81% | +| | 95% | 15.56% | 7.16% | 14.71% | 32.01% | 21.35% | 17.70% | +| UL average-UPT gain | Mean | 29.33% | 16.36% | 8.69% | 16.94% | -25.02% | -21.24% | +| | 5% | 6.84% | 4.52% | 173.45% | -37.93% | -21.84% | -3.30% | +| | 50% | 11.08% | -14.71% | 57.64% | 10.07% | -27.13% | -24.36% | +| | 95% | 42.70% | 39.36% | 7.23% | 31.76% | -21.84% | -19.87% | +| DL packet-Latency increase | Mean | -6.41% | -14.66% | -73.36% | -22.52% | -23.23% | -1.49% | +| | 5% | -18.17% | -15.90% | -12.23% | -24.73% | -15.56% | -12.56% | +| | 50% | -0.45% | 8.42% | -32.91% | -18.62% | -17.65% | -15.97% | +| | 95% | -10.89% | -13.76% | -78.35% | -24.02% | -23.48% | -0.21% | +| UL packet-Latency increase | Mean | -2.18% | 1.52% | -36.52% | 19.21% | 17.78% | 18.00% | +| | 5% | -34.14% | -29.78% | -5.63% | -41.36% | 27.99% | 18.98% | +| | 50% | -15.35% | 26.62% | -33.71% | 6.78% | 43.07% | 42.10% | +| | 95% | 20.45% | 15.87% | -37.62% | 30.48% | 8.84% | 8.91% | + +**Table 7.4.1.2.2.1-3: Urban Macro (FR1) dynamic SBFD vs. semi-static SBFD, {XXXXU} (dynamic SBFD Option 3, w/ CLI handling)** + +| Simple description of key assumptions (RSI based on 1dB desense, Twice area & same TxRUs (Option 2), SBFD slot configuration {XXXXU}, dynamic SBFD Option 3, DL: 0.5Mbytes, UL: 0.125Mbytes) | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------|--------------------|------------------| +| | | [33] | | | +| | | Low load | Medium load | High load | +| DL average-UPT gain | Mean | 9.97% | -0.11% | -14.03% | +| | 5% | 3.86% | -18.29% | -32.49% | +| | 50% | 9.49% | -0.39% | -16.04% | +| | 95% | 16.27% | 6.08% | -6.20% | +| UL average-UPT gain | Mean | 32.11% | 42.20% | 22.15% | +| | 5% | 44.65% | 19.24% | -4.13% | +| | 50% | 23.82% | 50.97% | 0.19% | +| | 95% | 41.75% | 46.53% | 33.55% | +| DL packet-Latency increase | Mean | -16.18% | -20.09% | 65.80% | +| | 5% | -18.27% | -16.11% | -4.16% | +| | 50% | -4.84% | 7.67% | 26.11% | +| | 95% | 59.44% | -5.90% | 91.48% | +| UL packet-Latency increase | Mean | -22.88% | -27.94% | -23.03% | +| | 5% | -32.30% | -31.33% | -23.67% | +| | 50% | -17.68% | -33.45% | -6.63% | +| | 95% | -8.29% | 0.75% | -8.26% | + +#### 7.4.1.2.2.2 SBFD slot configuration {XXXXX} + +In this sub-section, SBFD slot configuration {XXXXX} is assumed. + +**Table 7.4.1.2.2.2-1: Urban Macro (FR1) dynamic SBFD vs. semi-static SBFD, {XXXXX} (dynamic SBFD Option 3, w/ & w/o CLI handling)** + +| Simple description of key assumptions (RSI based on 1dB desense, Twice area & same TxRUs (Option 2), SBFD slot configuration {XXXXX}, dynamic SBFD Option 3, DL: 0.5Mbytes, UL: 0.125Mbytes) | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|------------------|-------------|-----------|-----------------|-------------|-----------| +| | | [33] | | | | | | +| | | w/o CLI handling | | | w/ CLI handling | | | +| | | Low load | Medium load | High load | Low load | Medium load | High load | +| DL average-UPT gain | Mean | 5.27% | 4.99% | -1.82% | 7.71% | -3.19% | -28.18% | +| | 5% | -5.78% | 84.29% | -1.40% | 8.43% | 12.77% | -29.06% | +| | 50% | 4.52% | 5.65% | 9.59% | 7.14% | -4.85% | -30.68% | +| | 95% | 13.63% | 1.26% | -5.92% | 13.74% | 6.00% | -20.00% | +| UL average-UPT gain | Mean | 52.73% | 88.66% | 30.04% | 60.49% | 87.42% | 66.19% | +| | 5% | -1.05% | NAN | NAN | 79.95% | NAN | NAN | +| | 50% | 9.58% | 62.54% | 55.92% | 33.59% | 60.88% | 90.03% | +| | 95% | 109.57% | 119.17% | 41.80% | 110.79% | 114.88% | 90.84% | +| DL packet-Latency increase | Mean | -4.60% | -69.78% | -29.47% | 5.48% | -4.65% | 125.91% | +| | 5% | -15.46% | -14.49% | 1.12% | -15.54% | -14.75% | 8.64% | +| | 50% | 3.28% | 2.01% | -0.25% | -2.41% | 13.15% | 53.30% | +| | 95% | 21.51% | -77.84% | -24.74% | 4.75% | 10.11% | 329.52% | +| UL packet-Latency increase | Mean | -9.62% | -60.97% | -30.81% | -26.44% | -51.38% | -78.52% | +| | 5% | -54.99% | -51.15% | -24.86% | -55.61% | -54.02% | -40.19% | +| | 50% | -16.08% | -23.74% | -12.80% | -27.89% | -40.10% | -46.37% | +| | 95% | 2.02% | -74.14% | -22.99% | -1.67% | -59.07% | -85.57% | + +#### 7.4.1.2.2.3 Summary of the Observations + +For the following observations, UPT gain in the range of {-5%, 5%} is considered as similar UPT. + +For Urban Macro (FR1), for dynamic SBFD compared to semi-static SBFD: + +- For slot configurations {XXXXX} for dynamic SBFD and semi-static SBFD, + - In case of large packet size and dynamic SBFD option 2 w/ CLI handling, based on results from 1 source, + - dynamic SBFD has similar mean and 5% UL Average-UPT for all load levels, except lower mean UL Average-UPT for low load level, + - and dynamic SBFD has higher mean and 5% DL Average-UPT for all load levels, except lower mean DL Average-UPT for high load level. + - In case of large packet size and dynamic SBFD option 2 w/o CLI handling, based on results from 1 source, + - dynamic SBFD has lower mean and 5% UL Average-UPT for all load levels, + - and dynamic SBFD has higher mean and 5% DL Average-UPT for all load levels, except similar 5% DL Average-UPT for high load level. + - In case of large packet size and dynamic SBFD option 3 w/o CLI handling, based on results from 2 sources, + - dynamic SBFD has higher or lower mean and 5% UL Average-UPT for all load levels, + - and dynamic SBFD has similar or higher mean and 5% DL Average-UPT for all load levels, except one source reported lower 5% DL Average-UPT for medium traffic load. + - In case of large packet size and dynamic SBFD option 3 w/ CLI handling, based on results from 1 source, + +- dynamic SBFD has higher mean and 5% UL Average-UPT for all load levels, except similar 5% UL Average-UPT for high load level, +- and dynamic SBFD has higher mean DL Average-UPT, similar 5% DL Average-UPT for low load level, similar mean DL Average-UPT for medium load level, lower 5% DL Average-UPT for medium load level, and lower mean and 5% DL Average-UPT for high load level. +- For slot configurations {XXXXX} for dynamic SBFD and semi-static SBFD, based on results from 1 source, +- In case of large packet size and dynamic SBFD option 3 w/ & w/o CLI handling, + - dynamic SBFD has higher mean and 5% UL Average-UPT for all load levels, except a similar 5% UL Average-UPT for low load level without CLI handling, + - and dynamic SBFD has similar, higher or lower mean and 5% DL Average-UPT for low and medium load levels, and similar mean and 5% DL Average-UPT for high load level without CLI handling, and lower mean and 5% DL Average-UPT for high load level with CLI handling. + +## 7.4.2 Inter-gNB CLI handling schemes + +The detailed SLS evaluation assumptions and results of semi-static SBFD with enhanced CLI handling schemes applied compared to semi-static SBFD without enhanced CLI handling schemes applied is provided in Annex B.3.2. + +### 7.4.2.1 Inter-gNB CLI handling scheme 1: Spatial Domain Coordination Scheme for gNB Tx-Beam Nulling + +#### 7.4.2.1.1 Reference scheme for performance comparison + +- Source 1 ([19]) + - Semi-static SBFD without gNB Tx-Beam nulling +- Source 2 ([26]) + - Semi-static SBFD without gNB Tx-Beam nulling + +#### 7.4.2.1.2 Proposed scheme + +- Source 1 ([19]) + - Scheme#1: Beam nulling based on steering vector. + - Scheme#2: Beam nulling based on gNB-gNB channel measurement. +- Source 2 ([26]) + - Beam nulling based on gNB-gNB channel measurement. + +#### 7.4.2.1.3 Performance evaluation or analysis + +2 sources ([19], [26]) provide SLS evaluation results for performance comparison between SBFD without aggressor gNB Tx beam nulling and SBFD with aggressor gNB Tx beam nulling. + +The summary of DL average-UPT gain and UL average-UPT gain are provided in Table 7.4.2.1.3-1, 7.4.2.1.3-2 and 7.4.2.1.3-3. + +**Table 7.4.2.1.3-1: Spatial domain coordination scheme for gNB Tx-Beam nulling (SBFD Alt-4)** + +| Simple description of key assumptions (FR1 Urban Macro, RSI based on 1dB desense, SBFD slot configuration Alt-4 ({DDDSU} vs. {XXXXX}), Twice area & same TxRUs (Option 2)) | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----------------|-------------|-----------|----------------|-------------|-----------|----------|-------------|-----------| +| | | [19, Scheme#1] | | | [19, Scheme#2] | | | [26] | | | +| | | Low load | Medium load | High load | Low load | Medium load | High load | Low load | Medium load | High load | +| DL average-UPT gain | Mean | -2.04% | 2.30% | 2.33% | -2.72% | 1.54% | -4.72% | -1.80% | -3.65% | -5.49% | +| | 5% | -30.04 % | NaN | NaN | -39.90% | NaN | NaN | -15.18% | -54.42% | -81.05% | +| | 50% | -2.24% | 9.71% | -3.44% | -4.08% | 5.07% | -8.01% | -0.59% | -1.51% | -5.11% | + +| | | | | | | | | | | | +|----------------------------|------|--------|---------|---------|---------|---------|---------|---------|----------|-----------| +| UL average-UPT gain | 95% | 2.76% | -3.68% | 3.63% | 1.27% | 0.79% | -2.63% | -0.34% | -0.61% | -0.67% | +| | Mean | 3.51% | 17.64% | 44.17% | 6.37% | 22.10% | 53.27% | 0.66% | 2.00% | 2.78% | +| | 5% | NaN | NaN | NaN | NaN | NaN | NaN | 2.49% | 129.91% | 149.91% | +| | 50% | 13.19% | 28.40% | 172.51% | 17.45% | 42.31% | 209.26% | 0.29% | 0.51% | 1.06% | +| | 95% | -7.05% | -1.09% | 13.05% | -3.61% | 2.78% | 17.45% | 0.02% | 0.26% | 0.14% | +| DL packet-Latency increase | Mean | 6.28% | -36.42% | -12.97% | -12.17% | -28.51% | 1.74% | 1.09% | -383.45% | -506.56% | +| | 5% | 0.00% | 0.00% | -5.56% | 0.00% | 0.00% | 0.00% | 0.00% | -3.23% | -6.45% | +| | 50% | 0.00% | -7.69% | -5.56% | 4.55% | -5.13% | 1.85% | 3.92% | -1.96% | -15.69% | +| | 95% | -3.03% | -18.38% | -14.79% | -5.05% | -15.14% | 1.76% | -30.03% | -698.15% | -3953.53% | +| UL packet-Latency increase | Mean | 2.61% | -18.23% | -1.25% | 16.75% | -16.91% | 8.73% | 61.00% | 34.14% | 49.03% | +| | 5% | 0.00% | 0.00% | -11.54% | 0.00% | 0.00% | -11.54% | 56.94% | 56.28% | 56.46% | +| | 50% | -5.08% | 14.29% | 15.66% | 8.47% | 20.00% | 19.28% | 63.23% | 61.61% | 60.65% | +| | 95% | 1.34% | -30.25% | 0.00% | 10.75% | -25.16% | 12.63% | 11.63% | 11.82% | -5.18% | + +Note: In the evaluation of source 1 ([19]), 100dB(spatial isolation)+10dB(digital isolation) for inter-sector CLI and Packet Size with 0.5Mbytes for DL and 0.125Mbyte for UL are assumed. And in the evaluation of source 2 ([26]), 93dB(spatial isolation)+10dB(digital isolation) for inter-sector CLI and Packet Size with 4Kbytes for DL and 1Kbyte for UL are assumed. + +**Table 7.4.2.1.3-2: Spatial domain coordination scheme for gNB Tx-Beam nulling (SBFD Alt-2)** + +| Simple description of key assumptions (FR1 Urban Macro, RSI based on 1dB desense, SBFD slot configuration Alt-2 ({DDDSU} vs. {XXXXU}), Twice area & same TxRUs (Option 2), 100dB(spatial isolation)+10dB(digital isolation) for inter-sector CLI and Packet Size with 0.5Mbytes for DL and 0.125Mbyte for UL) | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----------------|-------------|-----------|----------------|-------------|-----------| +| | | [19, Scheme#1] | | | [19, Scheme#2] | | | +| | | Low load | Medium load | High load | Low load | Medium load | High load | +| DL average-UPT gain | Mean | -1.52% | 0.23% | 2.62% | -8.16% | -1.81% | -0.91% | +| | 5% | -19.11% | NaN | NaN | -45.77% | NaN | NaN | +| | 50% | -5.34% | 0.88% | 1.72% | -10.83% | -0.75% | -6.65% | +| | 95% | 4.81% | 7.30% | 8.11% | -0.31% | 3.83% | 8.11% | +| UL average-UPT gain | Mean | 0.17% | 13.34% | 32.67% | 2.55% | 15.86% | 37.52% | +| | 5% | NaN | NaN | NaN | NaN | NaN | NaN | +| | 50% | 6.09% | 20.45% | 62.44% | 12.39% | 30.29% | 78.36% | +| | 95% | -0.57% | 2.08% | 14.30% | 0.72% | 4.09% | 16.76% | +| DL packet-Latency increase | Mean | -40.65% | -24.34% | 6.96% | 0.36% | -27.93% | 6.74% | +| | 5% | 0.00% | 0.00% | -4.00% | 7.14% | 0.00% | -8.00% | +| | 50% | 3.70% | -3.92% | -2.47% | 11.11% | -1.96% | 0.00% | +| | 95% | 3.13% | -23.70% | 8.49% | 44.79% | -24.81% | 7.45% | +| UL packet-Latency increase | Mean | -28.55% | -21.91% | -2.88% | -27.00% | -20.67% | -5.27% | +| | 5% | 9.09% | -7.69% | -7.69% | 9.09% | -7.69% | -7.69% | +| | 50% | 17.86% | 1.64% | 16.95% | 35.71% | 31.15% | 25.42% | +| | 95% | -10.07% | -25.99% | -17.33% | -7.19% | -27.87% | -14.96% | + +**Table 7.4.2.1.3-3: Spatial domain coordination scheme for gNB Tx-Beam nulling (SBFD Alt-1)** + +| Simple description of key assumptions (FR1 Urban Macro, RSI based on 1dB desense, SBFD slot configuration Alt-1 ({DDDSU} vs. {XXXXU}), Twice area & same TxRUs (Option 2), 100dB(spatial isolation)+10dB(digital isolation) for inter-sector CLI and Packet Size with 0.5Mbytes for DL and 0.125Mbyte for UL) | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----------------|-------------|-----------|----------------|-------------|-----------| +| | | [19, Scheme#1] | | | [19, Scheme#2] | | | +| | | Low load | Medium load | High load | Low load | Medium load | High load | +| DL average-UPT gain | Mean | 0.79% | -1.44% | -4.19% | -1.84% | -5.67% | -4.82% | +| | 5% | -4.18% | 11.45% | -11.62% | -17.07% | -22.68% | -100.00% | +| | 50% | 2.53% | -4.66% | -3.97% | 2.09% | -1.98% | -9.63% | +| | 95% | -2.10% | 0.41% | 1.21% | -2.68% | -5.62% | -0.35% | +| UL average-UPT gain | Mean | 2.30% | 6.83% | 19.19% | 3.32% | 9.73% | 22.26% | +| | 5% | NaN | NaN | NaN | NaN | NaN | NaN | +| | 50% | 2.71% | 20.68% | 49.12% | 2.58% | 29.00% | 60.53% | +| | 95% | 3.43% | 3.35% | 8.51% | 3.90% | 3.32% | 11.13% | +| DL packet-Latency increase | Mean | 2.78% | -5.81% | 11.62% | -1.52% | 0.52% | 20.80% | +| | 5% | 0.00% | -5.26% | -4.00% | 0.00% | 0.00% | -4.00% | +| | 50% | -3.70% | 0.00% | -3.41% | -3.70% | 0.00% | -1.14% | +| | 95% | 9.47% | -1.47% | 17.94% | -2.11% | -2.94% | 23.98% | +| UL packet-Latency increase | Mean | 1.06% | -12.06% | -6.00% | -15.32% | -1.96% | -6.42% | +| | 5% | 0.00% | 0.00% | 0.00% | 0.00% | 0.00% | 0.00% | +| | 50% | 33.82% | 1.45% | 31.67% | 4.41% | 14.49% | 36.67% | +| | 95% | -8.16% | -15.77% | -9.55% | -7.26% | -5.38% | -3.73% | + +## **Summary of observations** + +For the following observations, UPT gain in the range of $\{-5\%, 5\%\}$ is considered as similar UPT. + +For SBFD with aggressor gNB Tx beam nulling: + +In case of SBFD Alt 4, based on results from 2 sources, + +- Aggressor gNB Tx beam nulling based on steering vector has similar mean DL Average-UPT and lower or similar 5% DL Average-UPT for all load levels. +- Aggressor gNB Tx beam nulling based on gNB-gNB channel measurement has lower or similar mean and 5% DL Average-UPT for all load levels. +- Aggressor gNB Tx beam nulling based on steering vector has higher or similar mean UL Average-UPT and similar 5% UL Average-UPT for all load levels. +- Aggressor gNB Tx beam nulling based on gNB-gNB channel measurement has higher or similar mean and 5% UL Average-UPT for all load levels. + +In case of SBFD Alt 2, based on results from 1 source, + +- Aggressor gNB Tx beam nulling based on steering vector has similar mean DL Average-UPT and lower or similar 5% DL Average-UPT for all load levels. +- Aggressor gNB Tx beam nulling based on gNB-gNB channel measurement has lower or similar mean and 5% DL Average-UPT for all load levels. +- Aggressor gNB Tx beam nulling based on steering vector has higher or similar mean UL Average-UPT and similar 5% UL Average-UPT for all load levels +- Aggressor gNB Tx beam nulling based on gNB-gNB channel measurement has higher or similar mean UL Average-UPT and similar 5% UL Average-UPT for all load levels + +In case of SBFD Alt 1, based on results from 1 source, + +- Aggressor gNB Tx beam nulling based on steering vector has similar mean DL Average-UPT and similar 5% DL Average-UPT for low load level, higher 5% DL Average-UPT for medium load level and lower 5% DL Average-UPT for high load level. +- Aggressor gNB Tx beam nulling based on gNB-gNB channel measurement has lower or similar mean DL Average-UPT and lower 5% DL Average-UPT for all load levels. +- Aggressor gNB Tx beam nulling based on steering vector has higher or similar mean UL Average-UPT and similar 5% UL Average-UPT for all load levels. +- Aggressor gNB Tx beam nulling based on gNB-gNB channel measurement has higher or similar mean UL Average-UPT and similar 5% UL Average-UPT for all load levels. + +Comparing beam nulling based on steering vector to beam nulling based on gNB-gNB channel measurement, according to the results from source 1, beam nulling based on gNB-gNB channel measurement has larger mean UL Average-UPT for all load levels due to better flexibility to perform beam nulling. + +### **7.4.2.1.4 Specification impact of the proposed scheme** + +The potential specification impact is to define reference signals for gNB-gNB channel measurement and information exchange between gNBs of the CLI resource configuration and/or CLI measurement reports + +### **7.4.2.2 Inter-gNB CLI handling scheme 2: UL Resource Muting-based scheme for measuring the gNB-to-gNB CLI interference covariance matrix** + +#### **7.4.2.2.1 Reference scheme for performance comparison** + +- Source 1 ([19]) + - Semi-static SBFD without inter-gNB CLI handling + +#### 7.4.2.2.2 Proposed scheme + +- Source 1 ([19]) + - [19], Scheme#1: Non-Transparent UL resource muting based IRC assuming UL OH: 1 symbol and DL OH: 1 symbol + - [19], Scheme#2: Transparent UL resource muting based IRC assuming UL OH: 3 symbols and DL OH: 1 symbol + - [19], Scheme#3: Transparent UL resource muting based IRC assuming UL OH: 4 symbols and DL OH: 1 symbol + +#### 7.4.2.2.3 Performance evaluation or analysis + +One source ([19]) provides SLS evaluation results for performance comparison between Non-transparent UL resource muting based IRC and Transparent UL resource muting based IRC with different uplink overhead. + +The summary of DL average-UPT gain and UL average-UPT gain are provided in Table 7.4.2.2.3-1, 7.4.2.2.3-2 and 7.4.2.2.3-3. + +**Table 7.4.2.2.3-1: UL resource muting-based scheme for measuring the gNB-to-gNB CLI interference covariance matrix (SBFD Alt-4)** + +| Simple description of key assumptions (FR1 Urban Macro, RSI based on 1dB desense, SBFD slot configuration Alt-4 ({DDDSU} vs. {XXXXX}), Twice area & same TxRUs (Option 2), 100dB(spatial isolation)+10dB(digital isolation) for inter-sector CLI and Packet Size with 0.5Mbytes for DL and 0.125Mbyte for UL) | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----------------|-------------|-----------|----------------|-------------|-----------|----------------|-------------|-----------| +| | | [19, Scheme#1] | | | [19, Scheme#2] | | | [19, Scheme#3] | | | +| | | Low load | Medium load | High load | Low load | Medium load | High load | Low load | Medium load | High load | +| DL average-UPT gain | Mean | -1.22% | 1.77% | -14.90% | -3.62% | -4.61% | -16.97% | -5.79% | -5.79% | -14.46% | +| | 5% | 25.25% | NaN | NaN | 23.38% | NaN | NaN | -0.71% | NaN | NaN | +| | 50% | -5.98% | 3.91% | -18.97% | -3.67% | -2.72% | -21.26% | -10.12% | -5.37% | -18.95% | +| | 95% | 0.82% | -0.58% | -16.16% | -3.54% | -7.00% | -14.45% | -5.31% | -7.28% | -12.37% | +| UL average-UPT gain | Mean | 9.94% | 20.43% | 5.02% | -7.02% | 6.02% | -6.38% | -15.46% | -10.75% | -12.91% | +| | 5% | NaN | NaN | NaN | NaN | NaN | NaN | NaN | NaN | NaN | +| | 50% | 16.31% | 31.11% | -3.39% | -2.10% | 8.44% | -41.97% | -14.44% | -18.10% | -45.34% | +| | 95% | -2.80% | 9.39% | 2.75% | -15.63% | -9.29% | -8.37% | -21.31% | -17.35% | -13.03% | +| DL packet-Latency increase | Mean | -65.33 % | -12.36% | 32.56% | -54.23% | 2.99% | 59.29% | -50.29% | -5.86% | 36.15% | +| | 5% | 9.09% | 6.67% | 16.67% | 9.09% | 6.67% | 16.67% | 9.09% | 6.67% | 16.67% | +| | 50% | 4.55% | 5.13% | 27.78% | 4.55% | 10.26% | 33.33% | 9.09% | 10.26% | 27.78% | +| | 95% | -16.16 % | 0.00% | 58.80% | -17.17% | 13.51% | 69.01% | -6.06% | 14.59% | 41.55% | +| UL packet-Latency increase | Mean | 12.29% | -13.68% | 44.60% | 19.10% | -2.82% | 11.16% | 48.79% | 10.34% | 7.90% | +| | 5% | 0.00% | -5.00% | -7.69% | 18.75% | 10.00% | 3.85% | 25.00% | 20.00% | 7.69% | +| | 50% | -18.64 % | 10.00% | 1.20% | 33.90% | 1.43% | -8.43% | 35.59% | 34.29% | -6.02% | +| | 95% | 2.11% | -23.73% | 61.81% | 19.39% | -3.26% | 20.06% | 40.69% | 9.39% | 9.55% | + +**Table 7.4.2.2.3-2: UL resource muting-based scheme for measuring the gNB-to-gNB CLI interference covariance matrix (SBFD Alt-2)** + +| Simple description of key assumptions (FR1 Urban Macro, RSI based on 1dB desense, SBFD slot configuration Alt-2 ({DDDSU} vs. {XXXXU}), Twice area & same TxRUs (Option 2), 100dB(spatial isolation)+10dB(digital isolation) for inter-sector CLI and Packet Size with 0.5Mbytes for DL and 0.125Mbyte for UL) | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----------------|-------------|-----------|----------------|-------------|-----------|----------------|-------------|-----------| +| | | [19, Scheme#1] | | | [19, Scheme#2] | | | [19, Scheme#3] | | | +| | | Low load | Medium load | High load | Low load | Medium load | High load | Low load | Medium load | High load | +| DL average-UPT gain | Mean | -7.45% | -12.41% | -13.96% | -9.64% | -13.26% | -9.37% | -9.17% | -9.59% | -12.14% | +| | 5% | -19.00 % | NaN | NaN | -14.12% | NaN | NaN | 2.66% | NaN | NaN | +| | 50% | -9.99% | -19.19% | -15.35% | -13.60% | -17.20% | -14.25% | -12.48% | -13.13% | -16.46% | +| | 95% | -3.26% | -8.84% | -10.89% | -3.89% | -13.00% | -1.84% | -7.19% | -8.15% | -4.07% | +| UL average-UPT gain | Mean | 2.51% | -0.07% | -0.01% | -9.34% | -8.72% | -9.53% | -16.00% | -14.38% | -22.43% | +| | 5% | NaN | NaN | NaN | NaN | NaN | NaN | NaN | NaN | NaN | +| | 50% | 8.51% | 5.45% | 12.62% | -11.97% | -3.92% | -5.06% | -22.90% | -12.96% | -33.21% | +| | 95% | 1.52% | 0.48% | 2.10% | -6.83% | -7.55% | -11.74% | -11.96% | -11.20% | -17.40% | + +| | | | | | | | | | | | +|-----------------------------------|------|----------|---------|--------|---------|---------|--------|---------|---------|--------| +| DL packet-
Latency
increase | Mean | -60.39 % | -16.57% | 42.71% | -35.99% | -16.47% | 33.34% | -57.08% | -20.81% | 46.97% | +| | 5% | 7.14% | 10.53% | 12.00% | 7.14% | 21.05% | 8.00% | 7.14% | 15.79% | 12.00% | +| | 50% | 14.81% | 17.65% | 25.93% | 18.52% | 21.57% | 18.52% | 14.81% | 15.69% | 28.40% | +| | 95% | 3.13% | -11.85% | 71.64% | 28.13% | -0.74% | 51.97% | 14.58% | 0.74% | 75.57% | +| UL packet-
Latency
increase | Mean | 5.84% | 0.75% | 10.35% | -7.00% | 9.32% | 16.80% | 14.21% | 25.95% | 46.06% | +| | 5% | 9.09% | -7.69% | 0.00% | 9.09% | 7.69% | 15.38% | 27.27% | 15.38% | 15.38% | +| | 50% | -19.64 % | 16.39% | 8.47% | 58.93% | 13.11% | 20.34% | 28.57% | 21.31% | 33.90% | +| | 95% | -4.80% | -1.13% | 11.11% | 9.35% | 2.45% | 13.19% | 26.38% | 31.45% | 51.70% | + +**Table 7.4.2.2.3-3: UL resource muting-based scheme for measuring the gNB-to-gNB CLI interference covariance matrix (SBFD Alt-1)** + +| Simple description of key assumptions (FR1 Urban Macro, RSI based on 1dB desense, SBFD slot configuration Alt-1 ({DDDSU} vs. {DXXXU}), Twice area & same TxRUs (Option 2), 100dB(spatial isolation)+10dB(digital isolation) for inter-sector CLI and Packet Size with 0.5Mbytes for DL and 0.125Mbyte for UL) | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----------------|-------------|-----------|----------------|-------------|-----------|----------------|-------------|-----------| +| | | [19, Scheme#1] | | | [19, Scheme#2] | | | [19, Scheme#3] | | | +| | | Low load | Medium load | High load | Low load | Medium load | High load | Low load | Medium load | High load | +| DL average-
UPT gain | Mean | -5.80% | -5.53% | -12.93% | -7.46% | -8.54% | -9.91% | -7.99% | -7.99% | -14.16% | +| | 5% | -1.53% | 82.27% | 57.90% | 0.83% | 39.11% | -6.11% | 10.69% | 100.61% | 9.49% | +| | 50% | -4.38% | -6.60% | -17.41% | -7.55% | -9.29% | -15.48% | -6.74% | -9.63% | -23.92% | +| | 95% | -10.86 % | -6.05% | -6.41% | -9.21% | -10.69% | -1.00% | -12.62% | -9.10% | -8.44% | +| UL average-
UPT gain | Mean | 0.28% | 8.15% | 1.16% | -7.32% | -11.23% | -15.97% | -17.21% | -14.43% | -24.81% | +| | 5% | NaN | NaN | NaN | NaN | NaN | NaN | NaN | NaN | NaN | +| | 50% | 1.87% | 17.13% | 6.50% | -10.61% | -4.90% | -16.44% | -21.96% | -12.02% | -26.56% | +| | 95% | -2.02% | 5.82% | -0.24% | -2.15% | -11.86% | -16.33% | -9.86% | -16.05% | -22.23% | +| DL packet-
Latency
increase | Mean | 2.87% | -7.72% | 25.41% | 13.73% | -6.65% | 18.08% | 4.60% | 8.12% | 24.33% | +| | 5% | 7.14% | 0.00% | 8.00% | 7.14% | 5.26% | 8.00% | 7.14% | 5.26% | 8.00% | +| | 50% | 0.00% | 8.16% | 23.86% | 7.41% | 8.16% | 20.45% | 7.41% | 10.20% | 23.86% | +| | 95% | -1.05% | -16.54% | 38.83% | 3.16% | -11.03% | 13.70% | -5.26% | 9.19% | 26.26% | +| UL packet-
Latency
increase | Mean | 36.75% | -15.61% | 11.18% | 61.72% | 19.15% | 18.15% | 64.24% | 14.06% | 22.80% | +| | 5% | 0.00% | -7.69% | 0.00% | 8.33% | 7.69% | 15.38% | 16.67% | 15.38% | 23.08% | +| | 50% | 19.12% | -13.04% | 11.67% | 51.47% | 4.35% | 28.33% | 61.76% | 2.90% | 8.33% | +| | 95% | 10.20% | -11.69% | 27.61% | 29.93% | 25.60% | 25.82% | 48.53% | 24.68% | 43.43% | + +**Summary of observations** + +For the following observations, UPT gain in the range of {-5%, 5%} is considered as similar UPT. + +For SBFD with UL resource muting-based scheme for measuring the gNB-to-gNB CLI interference covariance matrix: + +In case of SBFD Alt 4, based on results from 1 source, + +- Non-Transparent UL resource muting based IRC assuming UL OH: 1 symbol and DL OH: 1 symbol has similar mean DL Average-UPT for low and medium load level, lower mean DL Average-UPT for high load level and higher or similar 5% DL Average-UPT for all load levels. +- Transparent UL resource muting based IRC assuming UL OH: 3 symbols and DL OH: 1 symbol has lower or similar mean DL Average-UPT and higher or similar 5% DL Average-UPT for all load levels. +- Transparent UL resource muting based IRC assuming UL OH: 4 symbols and DL OH: 1 symbol has lower mean DL Average-UPT and similar 5% DL Average-UPT for all load levels +- Non-Transparent UL resource muting based IRC assuming UL OH: 1 symbol and DL OH: 1 symbol has higher mean UL Average-UPT and similar 5% UL Average-UPT for all load levels. +- Transparent UL resource muting based IRC assuming UL OH: 3 symbols and DL OH: 1 symbol has lower mean UL Average-UPT for low and high load levels, higher UL Average-UPT for medium load level and similar 5% UL Average-UPT for all load levels. +- Transparent UL resource muting based IRC assuming UL OH: 4 symbols and DL OH: 1 symbol has lower mean UL Average-UPT and similar 5% UL Average-UPT for all load levels. + +In case of SBFD Alt 2, based on results from 1 source, + +- Non-Transparent UL resource muting based IRC assuming UL OH: 1 symbol and DL OH: 1 symbol has lower mean DL Average-UPT and lower or similar 5% DL Average-UPT for all load levels. +- Transparent UL resource muting based IRC assuming UL OH: 3 symbols and DL OH: 1 symbol has lower mean DL Average-UPT and lower or similar 5% DL Average-UPT for all traffic load level. +- Transparent UL resource muting based IRC assuming UL OH: 4 symbols and DL OH: 1 symbol has lower mean DL Average-UPT and similar 5% DL Average-UPT for all traffic load level. +- Non-Transparent UL resource muting based IRC assuming UL OH: 1 symbol and DL OH: 1 symbol has similar mean and 5% UL Average-UPT for all load levels. +- Transparent UL resource muting based IRC assuming UL OH: 3 symbols and DL OH: 1 symbol has lower mean UL Average-UPT and similar 5% UL Average-UPT for all load levels. +- Transparent UL resource muting based IRC assuming UL OH: 4 symbols and DL OH: 1 symbol has lower mean UL Average-UPT and similar 5% UL Average-UPT for all load levels. + +In case of SBFD Alt 1, based on results from 1 source, + +- Non-Transparent UL resource muting based IRC assuming UL OH: 1 symbol and DL OH: 1 symbol has lower mean DL Average-UPT and higher or similar 5% DL Average-UPT for all load levels. +- Transparent UL resource muting based IRC assuming UL OH: 3 symbols and DL OH: 1 symbol has lower mean DL Average-UPT for all load levels and similar 5% DL Average-UPT for low load level, higher 5% DL Average-UPT for medium load level, and lower 5% DL Average-UPT for high load level. +- Transparent UL resource muting based IRC assuming UL OH: 4 symbols and DL OH: 1 symbol has lower mean DL Average-UPT for and higher 5% DL Average-UPT for all traffic load level. +- Non-Transparent UL resource muting based IRC assuming UL OH: 1 symbol and DL OH: 1 symbol has higher or similar mean UL Average-UPT and similar 5% UL Average-UPT for all load levels. +- Transparent UL resource muting based IRC assuming UL OH: 3 symbols and DL OH: 1 symbol has lower mean UL Average-UPT and similar 5% UL Average-UPT for all load levels. +- Transparent UL resource muting based IRC assuming UL OH: 4 symbols and DL OH: 1 symbol has lower mean UL Average-UPT and similar 5% UL Average-UPT for all load levels. + +Comparing Non-Transparent UL resource muting based IRC (scheme 1) to Transparent UL resource muting based IRC (scheme 2 and scheme 3), based on the results from source 1, Non-Transparent UL resource muting based IRC has higher mean UL Average-UPT for all load levels due to the larger overhead of muted UL resources assumed for the transparent scheme, i.e. 3 or 4 symbols per slot for the transparent scheme and 1 symbol per slot for the non-transparent scheme. + +Both Transparent and Non-transparent schemes have lower mean DL Average-UPT for all load levels compared to semi-static SBFD without inter-gNB CLI handling due to the overhead from DL symbol muting, i.e. mute 1 symbol per slot. + +#### 7.4.2.2.4 Specification impact of the proposed scheme + +As described in section 8.3.1A.4, the potential specification impact of the proposed scheme is to define non-transparent UL muting resource patterns including its time and frequency location (e.g. symbol-level and/or RB-level and/or RE-level) with potential impact on PUSCH resource mapping. + +### 7.4.3 Inter-UE CLI handling schemes + +The detailed SLS evaluation assumptions and results of semi-static SBFD with enhanced CLI handling schemes applied compared to semi-static SBFD without enhanced CLI handling schemes applied is provided in Annex B.3.2. + +#### 7.4.3.1 Inter-UE CLI handling scheme 1: Coordinated scheduling + +##### 7.4.3.1.1 Reference scheme for performance comparison + +- Source 1 ([19]) + +- Semi-static SBFD without inter-UE CLI handling +- Source 2 ([33]) + - For a cell, in a SBFD slot, there is no restriction on the gNB scheduling for the transmission directions within one cluster, i.e., DL transmission and UL transmission can be scheduled among different UEs within the same cluster in the same SBFD slot. + +#### 7.4.3.1.2 Proposed scheme + +- Source 1 ([19]) + - Scheme#1: Coordinated scheduling based on L3 UE-UE CLI measurement + - Scheme#2: Coordinated scheduling based on L1 UE-UE CLI measurement. + - Note: simulations assumptions on UE processing/reporting delays was not provided by the source. +- Source 2 ([33]) + - intra-cell coordinated scheduling + - For a cell, in a SBFD slot, there is only one transmission direction that gNB can schedule within one cluster, i.e., the scheduled UEs within a cluster can only be allocated as the same transmission direction in a SBFD slot. + - There is no specification impact + +#### 7.4.3.1.3 Performance evaluation or analysis + +2 sources ([19], [33]) provide SLS evaluation results for performance comparison with coordinated scheduling. + +The summary of DL average-UPT gain and UL average-UPT gain are provided in Table 7.4.3.1.3-1, 7.4.3.1.3-2 and 7.4.3.1.3-3. + +**Table 7.4.3.1.3-1: Coordinated scheduling (SBFD Alt-4)** + +| Simple description of key assumptions (FR1 Urban Macro, RSI based on 1dB desense, SBFD slot configuration Alt-4 ({DDDSU} vs. {XXXXX}), Twice area & same TxRUs (Option 2), and Packet Size with 0.5Mbytes for DL and 0.125Mbyte for UL) | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------|--------------------|------------------|-----------------------|--------------------|------------------|-----------------|--------------------|------------------| +| | | [19, Scheme#1] | | | [19, Scheme#2] | | | [33] | | | +| | | Low load | Medium load | High load | Low load | Medium load | High load | Low load | Medium load | High load | +| DL average-UPT gain | Mean | 20.20% | 37.84% | 39.73% | 18.99% | 36.76% | 40.89% | 3.25% | 0.90% | 0.79% | +| | 5% | 101.99% | NaN | NaN | 93.44% | NaN | NaN | -7.66% | -15.36% | -26.38% | +| | 50% | 16.39% | 46.89% | 41.32% | 18.05% | 42.38% | 48.63% | 2.77% | -1.10% | -0.94% | +| | 95% | 7.79% | 9.64% | 13.30% | 7.88% | 12.85% | 8.98% | 4.05% | 4.87% | 7.76% | +| UL average-UPT gain | Mean | 1.84% | 0.18% | -12.96% | 1.96% | 10.17% | -6.50% | 25.63% | -8.76% | -28.58% | +| | 5% | NaN | NaN | NaN | NaN | NaN | NaN | 142.32% | -60.24% | -98.65% | +| | 50% | 4.61% | 0.76% | -43.17% | 4.26% | 9.43% | -28.22% | 19.29% | -39.95% | -78.11% | +| | 95% | -2.51% | -0.56% | -2.65% | -2.51% | 6.19% | -5.60% | 35.82% | 29.12% | 14.57% | +| DL packet-Latency increase | Mean | -80.92% | -50.92% | -21.92% | -80.46% | -50.53% | -24.32% | 10.22% | 156.82% | 64.99% | +| | 5% | 0.00% | -6.67% | -5.56% | 0.00% | -6.67% | -5.56% | -0.73% | -1.17% | -2.08% | +| | 50% | -13.64% | -23.08% | -14.81% | -13.64% | -20.51% | -20.37% | -1.67% | -0.29% | -2.09% | +| | 95% | -45.45% | -42.70% | -11.62% | -44.44% | -41.62% | -28.17% | 89.56% | 105.91% | 98.23% | +| UL packet-Latency increase | Mean | 33.13% | -6.43% | 40.15% | -1.11% | -0.03% | 30.71% | -12.64% | 76.76% | 311.76% | +| | 5% | 0.00% | 0.00% | -11.54% | 0.00% | -5.00% | -11.54% | -22.99% | -20.49% | -15.44% | +| | 50% | -5.08% | 8.57% | 51.81% | -22.03% | 24.29% | 38.55% | -13.24% | 83.84% | 339.72% | +| | 95% | 4.03% | -5.74% | 52.07% | 1.54% | -10.69% | 28.16% | -13.79% | 62.69% | 198.83% | + +Note: In the evaluation of source 1 ([19]), 100dB(spatial isolation)+10dB(digital isolation) for inter-sector CLI is assumed. And in the evaluation of source 2 ([33]), 93dB(spatial isolation) for inter-sector CLI is assumed. + +**Table 7.4.3.1.3-2: Coordinated scheduling (SBFD Alt-2)** + +| Simple description of key assumptions (FR1 Urban Macro, RSI based on 1dB desense, SBFD slot configuration Alt-2 ({DDDSU} vs. {XXXXU}), Twice area & same TxRUs (Option 2), and Packet Size with 0.5Mbytes for DL and 0.125Mbyte for UL) | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------|--------------------|------------------|-----------------------|--------------------|------------------|-----------------|--------------------|------------------| +| | | [19, Scheme#1] | | | [19, Scheme#2] | | | [33] | | | +| | | Low load | Medium load | High load | Low load | Medium load | High load | Low load | Medium load | High load | +| DL average-UPT gain | Mean | 8.73% | 20.81% | 28.67% | 11.83% | 18.18% | 29.17% | -16.47% | -20.91% | -25.30% | +| | 5% | 35.64% | NaN | NaN | 46.68% | NaN | NaN | -12.24% | -14.83% | -35.40% | +| | 50% | 4.94% | 17.97% | 33.03% | 8.17% | 16.11% | 31.92% | -17.65% | -23.36% | -28.28% | +| | 95% | 5.30% | 10.34% | 9.30% | 9.69% | 17.29% | 19.50% | -16.59% | -17.19% | -16.33% | +| UL average-UPT gain | Mean | 2.90% | -4.18% | -20.36% | 5.01% | -6.50% | -19.37% | 48.10% | 11.36% | -1.11% | +| | 5% | NaN | NaN | NaN | NaN | NaN | NaN | 201.56% | 124.54% | 178.17% | +| | 50% | 11.93% | -8.10% | -21.12% | 11.22% | -14.56% | -15.29% | 13.88% | -47.35% | -61.71% | +| | 95% | 5.22% | -3.33% | -15.02% | 7.92% | -0.29% | -9.88% | 96.90% | 88.53% | 81.73% | +| DL packet-Latency increase | Mean | -69.53 % | -48.14% | -1.17% | -71.76% | -46.51% | -8.15% | 59.34% | 207.79% | 87.39% | +| | 5% | 0.00% | 0.00% | -4.00% | 0.00% | 0.00% | -8.00% | 22.24% | 21.95% | 21.23% | +| | 50% | -3.70% | -9.80% | -4.94% | -7.41% | -7.84% | -6.17% | 23.79% | 29.79% | 38.69% | +| | 95% | -20.83 % | -40.00% | 1.86% | -26.04% | -38.15% | -4.14% | 66.68% | 220.22% | 240.50% | +| UL packet-Latency increase | Mean | 12.26% | 45.92% | 109.45% | 23.43% | 53.51% | 98.37% | -20.15% | 12.74% | -6.81% | +| | 5% | 0.00% | 0.00% | 7.69% | 0.00% | -7.69% | 7.69% | -47.61% | -45.24% | -41.81% | +| | 50% | 12.50% | 32.79% | 167.80% | 5.36% | 9.84% | 138.98% | -14.03% | 101.07% | 166.02% | +| | 95% | 5.76% | 73.07% | 112.59% | -4.08% | 102.26% | 106.37% | -17.61% | -32.30% | -61.40% | + +Note: In the evaluation of source 1 ([19]), 100dB(spatial isolation)+10dB(digital isolation) for inter-sector CLI is assumed. And in the evaluation of source 2 ([33]), 93dB(spatial isolation) for inter-sector CLI is assumed. + +**Table 7.4.3.1.3-3: Coordinated scheduling (SBFD Alt-1)** + +| Simple description of key assumptions (FR1 Urban Macro, RSI based on 1dB desense, SBFD slot configuration Alt-1 ({DDDSU} vs. {XXXXU}), Twice area & same TxRUs (Option 2), 100dB(spatial isolation)+10dB(digital isolation) for inter-sector CLI and Packet Size with 0.5Mbytes for DL and 0.125Mbyte for UL) | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------|--------------------|------------------|-----------------------|--------------------|------------------| +| | | [19, Scheme#1] | | | [19, Scheme#2] | | | +| | | Low load | Medium load | High load | Low load | Medium load | High load | +| DL average-UPT gain | Mean | 12.29% | 21.72% | 25.62% | 11.75% | 23.80% | 32.10% | +| | 5% | 61.12% | 370.50% | 722.56% | 50.53% | 423.01% | 937.28% | +| | 50% | 14.72% | 22.34% | 28.16% | 14.64% | 24.64% | 38.06% | +| | 95% | 1.96% | 6.48% | 9.79% | 0.72% | 8.59% | 16.51% | +| UL average-UPT gain | Mean | 0.58% | -1.09% | -8.33% | -1.60% | 1.89% | -9.47% | +| | 5% | NaN | NaN | NaN | NaN | NaN | NaN | +| | 50% | -6.11% | 4.86% | -12.23% | -10.33% | 5.30% | -8.69% | +| | 95% | 3.94% | 0.05% | -5.57% | 3.63% | -1.94% | -8.35% | +| DL packet-Latency increase | Mean | -21.76% | -33.27% | -20.28% | -20.38% | -37.34% | -28.56% | +| | 5% | -7.14% | -10.53% | -12.00% | -7.14% | -10.53% | -12.00% | +| | 50% | -14.81% | -16.33% | -12.50% | -14.81% | -16.33% | -19.32% | +| | 95% | -34.74% | -45.22% | -19.41% | -33.68% | -46.69% | -33.12% | +| UL packet-Latency increase | Mean | -5.94% | -1.01% | 17.56% | 12.28% | -2.72% | 24.56% | +| | 5% | 0.00% | 0.00% | 0.00% | -8.33% | 0.00% | 15.38% | +| | 50% | 0.00% | 14.49% | 28.33% | -11.76% | -1.45% | 36.67% | +| | 95% | 0.00% | -0.37% | 25.82% | 6.80% | -1.30% | 43.13% | + +**Summary of observations** + +For the following observations, UPT gain in the range of {-5%, 5%} is considered as similar UPT. + +For SBFD with coordinated scheduling: + +In case of SBFD Alt 4, based on results from 2 sources, + +- Coordinated scheduling based on L3 UE-UE CLI measurement has higher mean DL Average-UPT and higher or similar 5% DL Average-UPT for all load levels. +- Coordinated scheduling based on L1 UE-UE CLI measurement has higher mean DL Average-UPT and higher or similar 5% DL Average-UPT for all load levels. + +- Intra-cell coordinated scheduling has similar mean DL Average-UPT and lower 5% DL Average-UPT for all load levels. +- Coordinated scheduling based on L3 UE-UE CLI measurement has similar mean UL Average-UPT for low and medium load levels, lower mean UL Average-UPT for high load level and similar 5% UL Average-UPT for all load levels. +- Coordinated scheduling based on L1 UE-UE CLI measurement has higher or similar mean UL Average-UPT for low and medium load level, lower mean UL Average-UPT for high load level, and similar 5% UL Average-UPT for all load levels. +- Intra-cell coordinated scheduling has higher mean UL Average-UPT for low load level, lower mean UL Average-UPT for medium and high load level and higher 5% UL Average-UPT for low load level, lower 5% UL Average-UPT for medium and high load level. + +In case of SBFD Alt 2, based on results from 2 sources, + +- Coordinated scheduling based on L3 UE-UE CLI measurement has higher mean DL Average-UPT and higher or similar 5% DL Average-UPT for all load levels. +- Coordinated scheduling based on L1 UE-UE CLI measurement has higher mean DL Average-UPT and higher or similar 5% DL Average-UPT for all load levels. +- Intra-cell coordinated scheduling has lower mean and 5% DL Average-UPT for all load levels. +- Coordinated scheduling based on L3 UE-UE CLI measurement has lower or similar mean UL Average-UPT and similar 5% UL Average-UPT for all load levels. +- Coordinated scheduling based on L1 UE-UE CLI measurement has higher mean UL Average-UPT for low load level, lower mean UL Average-UPT for medium and high load level and similar 5% UL Average-UPT for all load levels. +- Intra-cell coordinated scheduling has higher or similar mean UL Average-UPT and higher 5% UL Average-UPT for all load levels. + +In case of SBFD Alt 1, based on results from 1 source, + +- Coordinated scheduling based on L3 UE-UE CLI measurement has higher mean and 5% DL Average-UPT for all load levels. +- Coordinated scheduling based on L1 UE-UE CLI measurement has higher mean and 5% DL Average-UPT for all load levels. +- Coordinated scheduling based on L3 UE-UE CLI measurement has lower or similar mean UL Average-UPT and similar 5% UL Average-UPT for all load levels. +- Coordinated scheduling based on L1 UE-UE CLI measurement has lower or similar mean UL Average-UPT and similar 5% UL Average-UPT for all load levels. + +According to source 1, Coordinated scheduling based on L3 UE-UE CLI measurement (scheme 1) and coordinated scheduling based on L1/L2 UE-UE CLI measurement (scheme 2) can achieve better mean DL Average-UPT than semi-static SBFD without inter-UE CLI handling (reference scheme). However, there is a slight loss in mean UL Average-UPT at low and medium load levels and moderate loss at high load level since for both scheme 1 and scheme 2, DL scheduling is prioritized over UL in case there is strong UE-UE CLI. In addition, coordinated scheduling based on L3 UE-UE CLI measurement has similar DL average-UPT gain compared to coordinated scheduling based on L1 UE-UE CLI measurement for all load levels. + +#### 7.4.3.1.4 Specification impact of the proposed scheme + +For L1/L2 based UE-UE CLI measurement, the potential specification impact is described in section 8.4.1.3. For L3 based UE-UE CLI measurement, there is no specification impact. + +For intra-cell coordinated scheduling, there is no specification impact. + +## 7.4.4 Inter-gNB and Inter-UE CLI handling schemes + +### 7.4.4.1 Inter-gNB and Inter-UE CLI handling scheme 1: Spatial Domain Coordination Scheme for gNB Tx-Beam Nulling and UL Resource Muting-based scheme for measuring the gNB-to-gNB CLI interference covariance matrix + +#### 7.4.4.1.1 Reference scheme for performance comparison + +- Source 1 ([19]) +- Semi-static SBFD without inter-gNB and inter-UE CLI handling + +#### 7.4.4.1.2 Proposed scheme + +- Source 1 ([19]) +- gNB-gNB CLI: Beam nulling based on gNB-gNB channel + Non-transparent UL resource muting based IRC +- UE-UE CLI: Coordinated scheduling based L3 UE-UE CLI measurement + +#### 7.4.4.1.3 Performance evaluation or analysis + +One source ([19]) provides SLS evaluation results for performance comparison with spatial Domain coordination scheme for gNB Tx-Beam nulling and UL resource muting-based scheme for measuring the gNB-to-gNB CLI interference covariance matrix. + +The summary of DL average-UPT gain and UL average-UPT gain are provided in Table 7.4.4.1.3-1. + +**Table 7.4.4.1.3-1: gNB Tx-Beam nulling and UL resource muting-based scheme for measuring the gNB-to-gNB CLI interference covariance matrix** + +| | | [19] | | | | | | | | | +|-----------------------------------|-------------|------------------------------------|--------------------|------------------|------------------------------------|--------------------|------------------|------------------------------------|--------------------|------------------| +| | | Alt-4 ({DDDSU} vs. {XXXXX}) | | | Alt-2 ({DDDSU} vs. {XXXXU}) | | | Alt-1 ({DDDSU} vs. {DXXXU}) | | | +| | | Low load | Medium load | High load | Low load | Medium load | High load | Low load | Medium load | High load | +| DL average-UPT gain | Mean | 6.71% | 20.48% | 18.32% | -1.21% | 8.62% | 15.13% | -3.30% | 11.26% | 8.66% | +| | 5% | 59.02% | NaN | NaN | 14.98% | NaN | NaN | 22.57% | 436.59% | 422.46% | +| | 50% | 5.55% | 25.97% | 14.61% | -3.53% | 5.74% | 15.55% | -3.28% | 13.33% | 12.06% | +| | 95% | -1.69% | 1.57% | 0.03% | -3.14% | 2.42% | 5.56% | -9.33% | -0.99% | -1.63% | +| UL average-UPT gain | Mean | 14.76% | 59.96% | 84.53% | 8.97% | 20.37% | 13.12% | 7.45% | 17.88% | 16.05% | +| | 5% | NaN | NaN | NaN | NaN | NaN | NaN | NaN | NaN | NaN | +| | 50% | 23.76% | 81.15% | 274.32% | 23.35% | 40.69% | 50.00% | 13.47% | 49.02% | 52.86% | +| | 95% | -0.33% | 20.45% | 28.88% | 6.03% | 7.39% | -0.58% | 6.21% | 2.92% | -1.99% | +| DL packet-Latency increase | Mean | -77.96% | -44.47% | -3.65% | -68.26% | -42.44% | 20.64% | -1.14% | -29.96% | 2.26% | +| | 5% | 9.09% | 6.67% | 0.00% | 7.14% | 10.53% | 0.00% | 7.14% | 0.00% | -4.00% | +| | 50% | -4.55% | -5.13% | 1.85% | 3.70% | 1.96% | 9.88% | 0.00% | -4.08% | 0.00% | +| | 95% | -39.39% | -30.81% | 7.39% | -10.42% | -31.11% | 42.24% | -16.84% | -43.38% | -2.45% | +| UL packet-Latency increase | Mean | 15.17% | -12.46% | 24.58% | 15.14% | 46.69% | 115.45% | 9.14% | -3.43% | 42.71% | +| | 5% | 0.00% | -15.00% | -23.08% | 9.09% | -7.69% | 0.00% | 0.00% | 0.00% | 15.38% | +| | 50% | 67.80% | 50.00% | 43.37% | 48.21% | 68.85% | 147.46% | 48.53% | 42.03% | 96.67% | +| | 95% | 21.31% | -27.90% | 18.71% | 14.39% | 87.19% | 134.22% | 24.04% | -0.56% | 51.19% | + +### Summary of observations + +For the following observations, difference between the UPT gain of the reference scheme and the UPT gain of the proposes scheme in the range of {-5%, 5%} is considered as similar UPT. + +For SBFD with spatial domain coordination scheme for gNB Tx-beam nulling and UL resource muting-based scheme for measuring the gNB-to-gNB CLI interference covariance matrix: + +In case of SBFD Alt 4, based on results from 1 source, + +- Spatial domain coordination scheme for gNB Tx-beam nulling and UL resource muting-based scheme for measuring the gNB-to-gNB CLI interference covariance matrix has higher mean DL Average-UPT and higher or similar 5% DL Average-UPT for all load levels. +- Spatial domain coordination scheme for gNB Tx-beam nulling and UL resource muting-based scheme for measuring the gNB-to-gNB CLI interference covariance matrix has higher mean UL Average-UPT and similar 5% UL Average-UPT for all load levels + +In case of SBFD Alt 2, based on results from 1 source, + +- Spatial domain coordination scheme for gNB Tx-beam nulling and UL resource muting-based scheme for measuring the gNB-to-gNB CLI interference covariance matrix has higher or similar mean and 5% DL Average-UPT for all load levels. +- Spatial domain coordination scheme for gNB Tx-beam nulling and UL resource muting-based scheme for measuring the gNB-to-gNB CLI interference covariance matrix has higher mean UL Average-UPT and similar 5% UL Average-UPT for all load levels + +In case of SBFD Alt 1, based on results from 1 source, + +- Spatial domain coordination scheme for gNB Tx-beam nulling and UL resource muting-based scheme for measuring the gNB-to-gNB CLI interference covariance matrix has higher or similar mean UL Average-UPT and higher 5% DL Average-UPT for all load levels. +- Spatial domain coordination scheme for gNB Tx-beam nulling and UL resource muting-based scheme for measuring the gNB-to-gNB CLI interference covariance matrix has higher mean UL Average-UPT and similar 5% UL Average-UPT for all load levels + +#### 7.4.4.1.4 Specification impact of the proposed scheme + +For beam nulling based on gNB-gNB channel, the potential specification impact is to define reference signals for gNB-gNB channel measurement and information exchange between gNBs of the CLI resource configuration and/or CLI measurement reports. + +For Non-transparent UL resource muting based IRC, the potential specification impact is to define non-transparent UL muting resource patterns including its time and frequency location (e.g. symbol-level and/or RB-level and/or RE-level) with potential impact on PUSCH resource mapping. + +For coordinated scheduling based L3 UE-UE CLI measurement, there is no specification impact. + +## 8 Potential enhancements and analysis for dynamic/flexible TDD + +### 8.1 Deployment scenarios + +The following scenarios are considered for dynamic/flexible TDD evaluation for single operator case: + +- FR1 + - 1-layer scenario + - Indoor office + - (Optional) Urban Macro + - 2-layer Scenario B + - Layer 1: Urban Macro + - Layer 2: + - Baseline: Indoor office + +- Optional: Indoor factory +- FR2-1 + - 1-layer scenario + - Indoor office + - (Optional) Dense Urban Macro layer + +The layouts and UE distributions for these scenarios can be found in Annex A.1. + +## 8.2 Evaluation methodologies + +### 8.2.1 System level simulation + +#### Channel model + +The channel model for dynamic/flexible TDD evaluation is the same as that for SBFD evaluation which can be found in Annex A.3. + +#### Performance metrics + +The following metrics are considered. The detailed definitions can be found in Annex A.4. + +- UPT related performance metrics + - Mean/5%/50%/95% Average-UPT, Average-UPT CDF + - Mean/5%/50%/95% Tail-UPT, Tail-UPT CDF + - Mean/5%/50%/95% Median-UPT, Median-UPT CDF +- Latency related performance metrics + - Baseline: Mean/5%/50%/95% Packet-Latency, Packet-Latency CDF + - Optional: Mean/5%/50%/95% UE-Average-Latency, UE-Average-Latency CDF +- Unfinished/dropped Packet Rate +- RU: Type-1 RU + +#### Traffic model + +FTP model 3 is used and the details can be found in Annex A.6. + +#### Assumption on baseline and target dynamic/flexible TDD operation for comparison + +| | | Target dynamic/flexible TDD operation | Baseline operation for comparison | +|----------------------------------|-----------------|----------------------------------------------------------------------------|---------------------------------------------------------------------------| +| 1-layer scenario | | Using dynamic TDD UL/DL assignment based on potential enhancements | Using dynamic TDD UL/DL assignment based on Rel-17 specifications | +| 2-layer Scenario (NOTE 1) | Option 1 | Layer 2 using legacy static TDD {DSUUU} based on potential enhancements | Layer 2 using legacy static TDD {DDDSU} based on Rel-17 specifications | +| | Option 2 | Layer 2 using dynamic TDD UL/DL assignment based on potential enhancements | Layer 2 using dynamic TDD UL/DL assignment based on Rel-17 specifications | + +NOTE 1: For 2-layer Scenario, layer 1 uses legacy static TDD {DDDSU} for both target and baseline operation +NOTE 2: + +- For legacy static TDD {DDDSU} and {DSUUU}, S=[12D:2G:0U] is assumed. +- For dynamic TDD UL/DL assignment, {FFFFF} is assumed and companies are encouraged to report the guard symbols assumed. Other configurations for dynamic TDD are not precluded and can be reported by companies. + +## **SLS assumptions** + +The SLS assumptions common to SBFD and dynamic/flexible TDD can be found in Table B.1-1 in Annex B. + +The SLS assumptions specific to dynamic/flexible TDD can be found in Table B.1-5 in Annex B. + +# **8.3 Inter-gNB CLI handling schemes** + +For study of potential enhancement to dynamic/flexible TDD and/or SBFD, followings are considered as candidates of potential enhancement method of gNB-to-gNB CLI handling, where further prioritization/down-scoping of candidate schemes for study can be done: + +- gNB-to-gNB CLI measurement and reporting +- Coordinated scheduling +- Spatial domain enhancements +- Advanced receiver +- UE and gNB transmission and reception timing +- Power control based solution +- Potential enhancements to Rel-16 RIM +- Sensing based mechanism +- Note: Whether or not a particular scheme requires OTA or backhaul information exchange should be identified +- Note: Any other scheme(s) for inter-gNB CLI handling is/are not precluded. +- Note: For potential enhancements to dynamic/flexible TDD and/or SBFD, utilize the outcome of discussion in Rel-15 and Rel-16 while avoiding the repetition of the same discussion. + +RAN1 deprioritized the discussion on both potential enhancement to Rel-16 RIM and sensing based mechanism for gNB-to-gNB co-channel CLI handling which can be specific for dynamic/flexible TDD and/or common for both SBFD and dynamic/flexible TDD. + +## **8.3.1 gNB-to-gNB co-channel CLI measurement and/or channel measurement** + +### **8.3.1.1 Description** + +RAN1 studies the feasibility and potential benefits of gNB-to-gNB co-channel CLI measurement for gNB-to-gNB CLI handling, which can be specific for dynamic/flexible TDD and/or common for both SBFD and dynamic/flexible TDD. In the study, at least followings are included: + +- Measurement resource configuration +- Measurement details +- Relevant information exchange +- Usage of measurement + +Also, for gNB-to-gNB co-channel CLI measurement, the potential benefit of uplink resources muting is studied further. + +### **Measurement Resource, Performance Metric and Relevant information exchange** + +In the study for gNB-to-gNB co-channel CLI measurement, it is considered as baseline to reuse existing DL channel(s)/signal(s)/measurement resource(s), for example, SSB, NZP/ZP-CSI-RS, DMRS for PDCCH/PDSCH, CSI-IM, RSSI measurement resource, etc. + +In the study, beam level (i.e., based on measurement result per SSB resource and/or per CSI-RS resource) CLI measurement can be considered. + +In the study, RAN1 assumed that exchange of configuration for NZP CSI-RS /SSB can be an enabler for gNB-to-gNB CLI measurement and/or channel measurement. + +### **UL Resource Muting** + +For enhancement of gNB-to-gNB co-channel CLI measurement and/or channel measurement, following options are studied for UL resource muting. + +- Option 1: Transparent UL resource muting method (e.g., avoid the scheduling on measurement resource) +- Option 2: Non-transparent UL resource muting method (e.g., define UL resource muting pattern with one or more RE/RB muting patterns) + +### **Issues on reception timing misalignment** + +For gNB-to-gNB co-channel CLI measurement and/or channel measurement, RAN1 studies the impact on system performance because of CLI measurement inaccuracy at victim gNB due to misalignment between UL timing at victim gNB and DL reception timing at victim gNB of CLI measurement resource transmitted from one or more aggressor gNB. In the study, potential impact on UL performance is included. + +#### **8.3.1.2 Performance evaluation or analysis** + +In the study of gNB-to-gNB co-channel CLI measurement and/or channel measurement, it is assumed that periodic NZP CSI-RS/SSB is the baseline. Also, for the study, it is assumed that both CD-SSB and NCD-SSB can be used for gNB-to-gNB CLI measurement. From the study of gNB-to-gNB co-channel CLI measurement and/or channel measurement, followings are observed: + +- gNBs, which measure gNB-to-gNB co-channel CLI using CD-SSBs from neighbor cells, might require muting/skipping some of the CD-SSBs if the time/frequency resource of CD-SSBs for the gNBs is overlapping. + - This approach might at least incur impact on initial access / cell search / RRM measurement performance +- In order to address the above issue, NCD-SSBs provided to neighbor gNBs can be used for CLI measurement at victim gNBs. +- SSB resources may be useful for coarse tracking of CLI levels +- NZP CSI-RS resource configurations provided to neighbor gNBs can be used for the purpose of estimating inter-gNB CLI levels. +- NZP CSI-RS resource configurations provided to neighbor gNBs also can be used for the purpose of estimating inter-gNB channel which helps Tx / Rx gNBs perform beamforming to reduce inter-gNB CLI. + +From the study of UL resource muting for gNB-to-gNB co-channel CLI measurement, channel measurement, the followings are observed: + +- The UL resource muting can be used to measure the gNB-to-gNB CLI levels with less interference from UL. +- The UL resource muting can be used to measure the gNB-to-gNB channel with less interference from UL. +- The UL resource muting can be used to measure the gNB-to-gNB CLI interference covariance matrix with less interference from UL. + +Note: Above can be done using current specification which supports transparent UL resource muting with gNB scheduling. UL resource muting could incur UL performance loss. + +For performance evaluation of *UL Resource Muting-based scheme for measuring the gNB-to-gNB CLI interference covariance matrix*, three sources ([19], [24], [35]) provide the evaluation results. The evaluation results are summarized in section 8.3.1A and the tables for the evaluation result are shown in Annex B.4. + +### 8.3.1.3 Specification impact + +For gNB-to-gNB co-channel CLI measurement, RAN1 discussed potential exchange of information among gNBs on Reference Signal/Channel (e.g., NZP CSI-RS, NCD-SSB) configuration. + +Specification impact of *UL Resource Muting-based scheme for measuring the gNB-to-gNB CLI interference covariance matrix* is summarized in section 8.3.1A.4. + +## 8.3.1A Inter-gNB CLI scheme 1A: UL Resource Muting-based scheme for measuring the gNB-to-gNB CLI interference covariance matrix + +### 8.3.1A.1 Reference scheme for performance comparison + +- Source 1 ([19]) + - Reference scheme 1: + - UL resource muting is not applied and the gNB-to-gNB CLI interference covariance matrix is obtained based on UL DMRS. + - Reference scheme 2: + - Transparent UL resource muting by not scheduling a number of symbols in a slot for PUSCH is assumed and the gNB-to-gNB CLI covariance matrix is estimated on the transparent UL muting resources. + - DL symbol of aggressor gNB is muted at the corresponding PUSCH DMRS and UL channel estimation is only interfered by UE-gNB interference. +- Source 2 ([24]) + - E-LMMSE-IRC (Rel-14 NR Study Item phase. TR 38.802, Section 10) without UL muting. +- Source 3 ([35]) + - Scheme 1 (No UL resource muting): + - The UL channel estimation is impacted by gNB-to-gNB CLI and the gNB-to-gNB CLI covariance matrix is not considered at the MMSE-IRC receiver + - Scheme 2 (DL symbol muting and Transparent UL resource muting): + - The UL channel estimation is not impacted by gNB-to-gNB CLI assuming the DL symbol is muted at aggressor gNB corresponding to the PUSCH DMRS + - The gNB-to-gNB CLI covariance matrix is obtained based on transparent UL muting resource + +### 8.3.1A.2 Proposed Scheme + +- Source 1 ([19]) + - The gNB-to-gNB CLI interference covariance matrix is obtained by muting some resources for the UL transmissions, based on a predefined pattern (in the evaluation, a comb-like muting pattern on one symbol for a PUSCH occasion is assumed) and the CLI can be suppressed by the MMSE-IRC receiver. + - Ideal channel estimation for UL PUSCH of victim gNB is assumed in the simulation results submitted to RAN1#113 and realistic channel estimation for UL PUSCH of victim gNB is assumed in the simulation results submitted to RAN1#114. DL symbol of aggressor gNB is muted at the corresponding PUSCH DMRS and UL channel estimation is only interfered by UE-gNB interference. +- Source 2 ([24]) + +- E-LMMSE-IRC with UL muting (no resources colliding with aggressor gNBs resources used for interference estimation). +- Covariance matrix estimation based on assisted information exchange of the CLI aggressor characteristics over the Xn interface. +- Source 3 ([35]) + - The UL channel estimation is not impacted by gNB-to-gNB CLI assuming the DL symbol is muted at aggressor gNB corresponding to the PUSCH DMRS + - The gNB-to-gNB CLI covariance matrix is obtained based on non-transparent UL muting resource where a comb-like UL resource muting pattern with 1/2 REs over the frequency is assumed and the UL resource muting pattern occurs on two PUSCH UL symbols + +### 8.3.1A.3 Performance evaluation or analysis + +3 sources ([19], [24], [35]) provided SLS evaluation results for performance comparison between measuring inter-gNB CLI covariance matrix based on UL DMRS and muted UL resource. The evaluation results are captured in Annex B.4. + +The summary of DL average-UPT gain and UL average-UPT gain are provided in Table 8.3.1A.3-1 to 8.3.1A.3-5, where large packet size is assumed. + +In the evaluation, the baseline operation and target operation for each source are as below: + +**Source 1 ([19]) and Source 3 ([35]) choose Option 1:** + +- Baseline operation for comparison: legacy static TDD {DDDSU} based on Rel-17 specifications +- Target flexible TDD operation: legacy static TDD {DSUUU} based on potential enhancements +- The UPT gains of the reference scheme(s) and proposed scheme over the baseline operation for comparison are presented in Table 8.3.1A.3-1, Table 8.3.1A.3-2, Table 8.3.1A.3-3, Table 8.3.1A.3-4 and Table 8.3.1A.3-5. +- In the tables, (1) is the reference scheme 1 as described in section 8.3.1A. (2) and (3) belong to reference scheme 2 (as described in section 8.3.1A) which are transparent UL resource muting schemes with 3 and 4 UL symbols muted respectively. (4) is the proposed scheme which is non-transparent scheme with a comb-2 muting pattern occurring on 2 symbols. + +**Source 2 ([24]) choose Option 2:** + +- Baseline operation (for computing UPT gain of reference and target operations): dynamic TDD UL/DL assignment based on Rel-17 specifications with LMMSE-IRC receiver assuming that the gNB-to-gNB interference covariance matrix can't be estimated and therefore it is not used as input for the gNB's receiver. +- Reference operation (for drawing observations on the difference in UPT gain of the potential enhancements compared to reference operation): dynamic TDD UL/DL assignment based on Rel-17 specifications with E-LMMSE-IRC receiver assuming that the victim gNB is able to estimate the gNB-to-gNB interference covariance matrix based on UL DMRS. +- Target flexible TDD operation: dynamic TDD UL/DL assignment based on potential enhancements including: + - Transparent UL resource muting: E-LMMSE-IRC receiver assuming that the gNB-to-gNB interference covariance matrix is estimated based on transparent UL resource muting. It is assumed that one OFDM symbol is muted. + - Non-transparent UL resource muting (upper bound): E-LMMSE-IRC receiver assuming that the gNB-to-gNB interference covariance matrix is estimated based on non-transparent UL resource muting. It is assumed that RE puncturing is not applied on UL resource, resulting in an upper bound of non-transparent UL resource muting. + +In the tables, the UPT gains of reference and target operations over baseline operation are calculated as $X\%$ ( $= (\text{Reference or Target UPT}) / (\text{Baseline UPT} - 1)$ ). + +For the performance comparison between reference scheme (e.g., measuring inter-gNB CLI covariance matrix based on UL DMRS) and proposed scheme (e.g., measuring inter-gNB CLI covariance matrix based on muted UL resource), the UPT gain of proposed scheme is compared with the UPT gain of reference scheme for drawing observations. + +**Table 8.3.1A.3-1: MMSE-IRC vs. UL resource muting-based E-MMSE-IRC (Large Packet Size (0.5Mbyte for DL and 0.125 Mbytes for UL))** + +| | | Medium load | | | | High load | | | | +|---------------------|------|-------------------------|------------------------|-------------------------|------------------------|-------------------------|------------------------|-------------------------|------------------------| +| | | Source 1 ([19]) | | | | Source 1 ([19]) | | | | +| | | Without joint reception | | With joint reception | | Without joint reception | | With joint reception | | +| | | (1)
Reference Scheme | (4)
Proposed Scheme | (1)
Reference Scheme | (4)
Proposed Scheme | (1)
Reference Scheme | (4)
Proposed Scheme | (1)
Reference Scheme | (4)
Proposed Scheme | +| DL average-UPT gain | Mean | -1% | 1% | -1% | 1% | -3% | -1% | -3% | -1% | +| | 5% | 49% | 53% | 49% | 53% | 53% | 40% | 53% | 40% | +| UL average-UPT gain | Mean | 77% | 174% | 83% | 179% | 166% | 299% | 131% | 200% | +| | 5% | 7% | 72% | 14% | 22% | 174% | 368% | 62% | 92% | + +Note: In the evaluation of source 1 ([19]), FR1 2-layer Scenario B is assumed. + +**Table 8.3.1A.3-2: MMSE-IRC vs. UL resource muting based E-MMSE-IRC (Transparent/Non-transparent) (Symmetric Large Packet Size (0.5Mbytes for DL/UL), with joint reception)** + +| | | Low Load | | | | Medium Load | | | | High Load | | | | +|---------------------------------|------|-----------------|-------|-------|-------|-----------------|-------|-------|------|-----------------|-------|-------|-------| +| | | Source 1 ([19]) | | | | Source 1 ([19]) | | | | Source 1 ([19]) | | | | +| | | (1) | (2) | (3) | (4) | (1) | (2) | (3) | (4) | (1) | (2) | (3) | (4) | +| DL average-UPT gain for layer-1 | Mean | -0.0% | -5.2% | -8.6% | -7.8% | 1.5% | -7.2% | -8.3% | -7.7 | 8.57 | -5.9% | -9.5% | -2.4% | +| | 5% | 28% | 21.7 | -3.0% | 11.4 | 16.4 | 6.13 | 4.46 | % | % | 74.6 | 47.5 | 69.7 | +| DL average-UPT gain for layer-2 | Mean | -42% | -48% | -44% | -45% | -63% | -64% | -64% | -64% | -70% | -73% | -74% | -73% | +| | 5% | -10% | -12% | -12% | -9% | -70% | -69% | -70% | -69% | -67% | -69% | -61% | -75% | +| UL average-UPT gain for layer-1 | Mean | -4% | 6.13 | 4.92 | 5.61 | 1.47 | -0.6% | 1.59 | -0.4 | 0.84 | -0.9% | -3.5% | 2.41 | +| | 5% | 16% | 18.5 | 24.1 | 18.6 | 8.16 | 2.48 | 3.21 | % | % | 2.0% | 2.05 | -0.7% | +| UL average-UPT gain for layer-2 | Mean | 159% | 129% | 108% | 168% | 116% | 161% | 125% | 202% | 95% | 237% | 196% | 335% | +| | 5% | 93% | 127% | 109% | 166% | 113% | 234% | 139% | 252% | 209% | 621% | 457% | 996% | + +Note: In the evaluation of source 1 ([19]), FR1 2-layer Scenario B is assumed. + +**Table 8.3.1A.3-3: MMSE-IRC vs. UL resource muting based E-MMSE-IRC (Transparent/Non-transparent) (Large Packet Size (0.5Mbyte for DL and 0.125 Mbytes for UL), without joint reception)** + +| | | Low Load | | | | Medium Load | | | | High Load | | | | +|---------------------------------|------|-----------------|-------|-------|-------|-----------------|-------|-------|------|-----------------|-------|-------|------| +| | | Source 1 ([19]) | | | | Source 1 ([19]) | | | | Source 1 ([19]) | | | | +| | | (1) | (2) | (3) | (4) | (1) | (2) | (3) | (4) | (1) | (2) | (3) | (4) | +| DL average-UPT gain for layer-1 | Mean | -0.6% | -8.8% | -9.4% | -6.9% | 4.99 | -9.6% | -9.0% | -9.2 | -0.7% | -9.5% | -12% | -11% | +| | 5% | 90.2 | 40.9 | 36.8 | 41.8 | 43.3 | 9.49 | 16.5 | % | 39% | 22.7 | 4.39 | 8.6% | +| DL average-UPT gain for layer-2 | Mean | -46% | -45% | -45% | -46% | -54% | -52% | -53% | -54% | -56% | -62% | -62% | -62% | +| | 5% | -16% | -15% | -16% | -15% | -55% | -58% | -58% | -56% | -59% | -48% | -54% | -48% | +| UL average-UPT gain for layer-1 | Mean | -0.9% | -1.2% | -1.8% | 0.86 | 0.15 | 4.41 | 8.4% | 6.94 | -0.4% | -1.1% | -1.3% | 2.3% | +| | 5% | 6.7% | 8.9% | 7.9% | 2.25 | 9.76 | 15.4 | 12.1 | 8.26 | 6.7% | 9.54 | 13.6 | 7.71 | +| UL average-UPT gain for layer-2 | Mean | 225% | 153% | 121% | 204% | 309% | 321% | 231% | 343% | 109% | 120% | 82.7 | 194% | +| | 5% | 168% | 129% | 106% | 168% | 97.3 | 157% | 125% | 200% | 71% | 247% | 198% | 345% | + +| | | | | | | | | | | | | | | +|-----------------------------|------------|------|------|------|------|------|------|------|------|--------|--------|--------|------| +| UPT gain for layer-2 | 5% | 291% | 180% | 105% | 279% | 260% | 302% | 234% | 344% | 22.0 % | 31.1 % | 47.1 % | 120% | +| | 50% | 223% | 150% | 127% | 198% | 295% | 327% | 229% | 341% | 90.6 % | 118% | 73.4 % | 200% | + +Note: In the evaluation of source 1 ([19]), FR1 2-layer Scenario B is assumed. + +**Table 8.3.1A.3-4: Inter-gNB CLI covariance matrix estimation based on UL DMRS vs. Transparent UL muting vs. Non-transparent UL muting (Large Packet Size (0.5Mbyte for DL and 0.125 Mbytes for UL))** + +| | | Low Load | | | Medium Load | | | High Load | | | +|----------------------------------------|-------------|------------------------|------------|------------|------------------------|------------|------------|------------------------|------------|------------| +| | | Source 2 ([24]) | | | Source 2 ([24]) | | | Source 2 ([24]) | | | +| | | (1) | (2) | (3) | (1) | (2) | (3) | (1) | (2) | (3) | +| DL average-UPT gain for layer-1 | Mean | 0% | 0% | 0% | 0.01% | 0.01% | -0.02% | -0.05% | -0.02% | -0.01% | +| | 50% | 0% | 0% | 0% | 0% | -0.95% | -0.95% | 1.55% | 1.11% | 0.67% | +| DL average-UPT gain for layer-2 | Mean | 0.01% | 0.02% | 0.03% | -0.22% | 3.24% | 3.33% | -4.22% | 9.64% | 12.61% | +| | 50% | 0% | 0% | 0% | 2.87% | -2.87% | -2.87% | 0% | -0.05% | -0.05% | +| UL average-UPT gain for layer-1 | Mean | -14.16% | -6.49% | 0.05% | -22.25% | -8.95% | 0.17% | -32.82% | -12.08% | 0.2% | +| | 50% | -17.71% | -6.82% | 0% | -34.48% | -10.38% | 3.42% | -46.69% | -20.87% | 1.16% | +| UL average-UPT gain for layer-2 | Mean | -19.2% | -9.66% | -1.69% | -25.89% | -8.8% | 0.64% | -38.46% | -13.33% | 1.75% | +| | 50% | 15.93% | 54.66% | 69.09% | 8.28% | 99.83% | 119.63 % | -11.11% | 61.55% | 86.41% | +| | 50% | -17.46% | -17.1% | 0.54% | -19.21% | -28.17% | -6.04% | -0.28% | -9.25% | 2% | +| | 50% | 30.45% | 113.29 % | 129.66 % | 3.16% | 100.94 % | 122.65 % | -44.03% | 73.13% | 111.19 % | + +Note 1: (1) reference scheme is Inter-gNB CLI Covariance Matrix Estimation based on UL DMRS. And (2) and (3) proposes schemes are Inter-gNB CLI Covariance Matrix Estimation based on Transparent UL muting and upper bound of Non-transparent UL muting, respectively. + +Note 2: In the evaluation of source 2 ([24]), FR1 2-layer Scenario B is assumed. + +**Table 8.3.1A.3-5: Inter-gNB CLI covariance matrix estimation based on UL DMRS vs. Transparent/ Non-transparent UL muting (Symmetric Large Packet Size (0.5Mbytes for DL/UL))** + +| | | Low Load | | | Medium Load | | | High Load | | | +|----------------------------------------|-------------|------------------------|------------|------------|------------------------|------------|------------|------------------------|------------|------------| +| | | Source 3 ([35]) | | | Source 3 ([35]) | | | Source 3 ([35]) | | | +| | | (1) | (2) | (4) | (1) | (2) | (4) | (1) | (2) | (4) | +| DL average-UPT gain for layer-1 | Mean | -3% | -12.88% | -14.15% | 3.74% | -5.86% | -10.16% | -4.79% | -17.99% | -17.85% | +| | 50% | 15.65% | -19.43% | 4.94% | 51.84% | 48.85% | 22.7% | 29.63% | -2.98% | -0.89% | +| DL average-UPT gain for layer-2 | Mean | 19.4% | -9.09% | -9.09% | 3.37% | -7.07% | -10.68% | -2.03% | -20.46% | -19.62% | +| | 50% | -40.47% | -41.97% | -40.01% | -47.54% | -49.82% | -50.87% | -73.11% | -73.29% | -73.71% | +| UL average-UPT gain for layer-1 | Mean | -51.74% | -53.04% | -50.76% | -46.91% | -47.83% | -49.6% | -63.78% | -68.63% | -66.93% | +| | 50% | -37.23% | -36.5% | -35.64% | -45.18% | -48.79% | -47.95% | -78.77% | -80.58% | -80.08% | +| UL average-UPT gain for layer-2 | Mean | -2.06% | 5% | -3.78% | 1.5% | 4.43% | 5.75% | 0.84% | -5.23% | 2.48% | +| | 50% | 0.22% | 3.29% | 3.9% | -2.99% | 2.9% | 3.14% | 3.81% | 9.56% | 9.42% | +| | 50% | -9.23% | -5.75% | -4.81% | 3.32% | 4.2% | 4.29% | 1.41% | -6.08% | 0.5% | +| | Mean | 167.28 % | 130.34 % | 169.7% % | 115.56 % | 133.87 % | 180.59 % | 63.72% % | 210.32 % | 312.98 % | +| | 50% | 118.37 % | 130.11 % | 177.92 % | 75% % | 129.69 % | 203.09 % | 111.76 % | 534.73 % | 904.56 % | +| | 50% | 182.09 % | 130.49 % | 166.2% % | 106.12 % | 137.65 % | 180.56 % | 44.96% % | 201.61 % | 310.99 % | + +Note: In the evaluation of Source 3 ([35]), FR1 2-layer Scenario B is assumed. + +### Summary of observations + +For the following observations, difference between the UPT gain of the reference scheme and the UPT gain of the proposes scheme in the range of {-5%, 5%} is considered as similar UPT. + +For measuring CLI covariance matrix based on Transparent/ Non-transparent muted UL resource compared to measuring CLI covariance matrix based on UL DMRS: + +- (1) FR1 2-layer Scenario B scenario + +In case of symmetric large packet size, based on results from 2 sources, + +- Measuring CLI covariance matrix based on Transparent/ Non-transparent muted UL resource has lower or similar mean and 5% DL Average-UPT for layer-1 for all load levels due to overhead from DL symbol muting. +- Measuring CLI covariance matrix based on Transparent/ Non-transparent muted UL resource has similar mean and 5% DL Average-UPT for layer-2 for all load levels. +- Measuring CLI covariance matrix based on Transparent/ Non-transparent muted UL resource has higher or similar mean and 5% UL Average-UPT for layer-1 for all load levels. +- Measuring CLI covariance matrix based on Transparent/ Non-transparent muted UL resource has lower mean and 5% UL Average-UPT for layer-2 for low load level when joint reception is not applied; measuring CLI covariance matrix based on Transparent/ Non-transparent muted UL resource has lower mean UL Average-UPT and higher 5% UL Average-UPT for layer-2 for low load level when joint reception is applied; measuring CLI covariance matrix based on Transparent muted UL resource has higher or lower mean and 5% UL Average-UPT for layer-2 for medium and high load levels depending on the overhead of muted UL resources; measuring CLI covariance matrix based on Non-transparent muted UL resource has higher mean and 5% UL Average-UPT for layer-2 for medium and high load levels. + +In case of large packet size, based on results from 1 source, + +- Measuring CLI covariance matrix based on Transparent/ Non-transparent muted UL resource has similar mean and 5% DL Average-UPT for layer-1 for all load levels. +- Measuring CLI covariance matrix based on Transparent/ Non-transparent UL muted resource has similar mean and 5% DL Average-UPT for layer-2 for low and medium load levels, and higher or similar mean and 5% DL Average-UPT for layer-2 for high load level. +- Measuring CLI covariance matrix based on Transparent/ Non-transparent muted UL resource has higher mean and 5% UL Average-UPT for layer-1 for all load levels. +- Measuring CLI covariance matrix based on Transparent/ Non-transparent muted UL resource has higher or similar mean and 5% UL Average-UPT for layer-2 for all load levels. + +For measuring CLI covariance matrix based on non-transparent muted UL resource compared to measuring CLI covariance matrix based on transparent muted UL resource: + +#### (1) FR1 2-layer Scenario B scenario + +In case of symmetric large packet size, based on results from 2 sources and in case of large packet size, + +- Measuring CLI covariance matrix based on non-transparent muted UL resource has higher mean and 5% UL Average-UPT for layer-2 for all load levels due to the larger overhead of muted UL resources assumed for the transparent scheme, i.e., up to 4 symbols per slot for the transparent scheme and 1 symbol per slot for the non-transparent scheme +- Measuring CLI covariance matrix based on non-transparent muted UL resource has similar mean and 5% DL Average-UPT for layer-2 for all load levels. Both Transparent and Non-transparent schemes have lower mean and 5% DL Average-UPT for layer-1 for all load levels compared to measuring CLI covariance matrix based on UL DMRS due to the overhead from DL symbol muting, i.e., mute 1 symbol per slot. + +In case of large packet size, based on results from 1 source + +- The upper bound of measuring CLI covariance matrix based on non-transparent muted UL resource (as no RE puncturing applied on UL resource and also with ideal inter-gNB CLI covariance matrix) has higher mean and 5% UL Average-UPT for layer-2 compared to measuring CLI covariance matrix based on transparent muted UL resource, for all load levels. +- The upper bound of measuring CLI covariance matrix based on non-transparent muted UL resource (as no RE puncturing applied on UL resource and also with ideal inter-gNB CLI covariance matrix) has similar mean and 5% DL Average-UPT for both layer-1 and layer-2 compared to measuring CLI covariance matrix based on + +transparent muted UL resource, for all load levels. This source does not assume DL resource muting in their evaluation. + +### 8.3.1A.4 Specification impact of the proposed scheme + +- Source 1 ([19]) + - Non-transparent UL muting resource patterns (e.g. predefined) including its time and frequency location (e.g. symbol-level and/or RB-level and/or RE-level) with potential impact on PUSCH resource mapping. +- Source 2 ([24]) + - Signaling of assistance information for interference/channel estimation over Xn interface. Potential signaling of UL muting pattern. +- Source 3 ([35]) + - Same as proposed scheme from Source 1 + +## 8.3.2 Coordinated scheduling for time/frequency resources between gNBs + +### 8.3.2.1 Description + +The feasibility and potential benefits of coordinated scheduling for time/frequency resources between gNBs for gNB-to-gNB co-channel CLI handling, which can be specific for dynamic/flexible TDD and/or common for both SBFD and dynamic/flexible TDD, are studied. The study at least includes: + +- Details of coordinated scheduling for time/frequency resources +- Relevant information exchange + +### 8.3.2.2 Performance evaluation or analysis + +From the study of the benefit of knowledge among gNBs of semi-static SBFD time and frequency configuration, followings are observed: + +- The knowledge among gNBs of semi-static SBFD time and frequency configuration can be beneficial depending on gNB implementation + +For performance evaluation of **Time Domain Scheme using UL slot(s) aligned between gNBs**, two sources ([44], [32]) provide the evaluation results. The evaluation results are summarized in section 8.3.2A and the tables for the evaluation result are shown in Annex B.4. + +For performance evaluation of **Frequency Domain Coordination Scheme**, two sources ([26], [24]) provide the evaluation results. The evaluation results are summarized in section 8.3.2B and the tables for the evaluation result are shown in Annex B.4. + +### 8.3.2.3 Specification impact + +For CLI handling based on coordinated scheduling for time/frequency resource, RAN1 discussed potential exchange of information among gNBs on intended TDD UL-DL configuration, SBFD time/frequency configuration. + +Specification impact of **Time Domain Scheme using UL slot(s) aligned between gNBs** and **Frequency Domain Coordination Scheme** are summarized in section 8.3.2A.4 and 8.3.2B.4, respectively. + +## 8.3.2A Inter-gNB CLI scheme 2A: Time domain scheme using UL slot(s) aligned between gNBs + +### 8.3.2A.1 Reference scheme for performance comparison + +- Source 1 ([44]) + - Dynamic TDD (dTDD) has TDD UL/DL configuration FFFFF, as per RAN1 agreement. +- Source 2 ([32]) + +- For 2-layer Scenario B (HetNet with Urban Macro and Indoor), semi-static TDD pattern {DDDSU} is used for both Urban Macro cell (layer 1) and Indoor office cell (layer 2) and there is no time domain coordinated scheduling. + +### 8.3.2A.2 Proposed scheme + +- Source 1 ([44]) + - Dynamic TDD with “protected” UL-only slot (p-dTDD) has TDD UL/DL configuration FFFFU. All gNBs coordinate to configure the same UL-only slot such that it is free of CLI. For example, the UL-only slot can be used by gNBs for reliable reception of UL control channels to support HARQ for the downlink. + - Source 1 shows SLS results at low, medium, and high load comparing dynamic TDD with protected UL-only slot (p-dTDD) to baseline dynamic TDD (dTDD). +- Source 2 ([32]) + - For 2-layer Scenario B (HetNet with Urban Macro and Indoor), semi-static TDD pattern {DDDSU} and {DSUUU} are used for Urban Macro cell (layer 1) and Indoor office cell (layer 2), respectively. + - The gNB schedules the UE suffering severe gNB-to-gNB interference on the UL slots without CLI (i.e., the last UL slot in each TDD period) to avoid the impact of gNB-to-gNB CLI. + +### 8.3.2A.3 Performance evaluation or analysis + +2 sources ([44], [32]) provided SLS evaluation results for performance comparison between dynamic/flexible TDD with aligned UL slot(s) between gNBs and the reference scheme (i.e., dynamic TDD with full flexible slots for source 1([44]), static TDD for source 2 ([32])). The evaluation results are captured in Annex B.4. + +The summary of DL average-UPT gain and UL average-UPT gain are provided in Table 8.3.2A.3-1, where large packet size is assumed. + +**Table 8.3.2A.3-1: Time domain scheme using UL slot(s) aligned between gNBs vs. Reference scheme (Large Packet Size (0.5Mbyte for DL and 0.125 Mbytes for UL))** + +| | | Low load | | Medium load | | High load | | +|----------------------------------------|-------------|--------------------|--------------------|--------------------|--------------------|--------------------|--------------------| +| | | Source 1
([44]) | Source 2
([32]) | Source 1
([44]) | Source 2
([32]) | Source 1
([44]) | Source 2
([32]) | +| DL average-UPT gain for layer-1 | Mean | -17.05% | -2.43% | -23.83% | -6.16% | NaN | -9.9% | +| | 5% | -18.23% | -3.71% | NaN | -12.36% | NaN | -24.33% | +| | 50% | -17.34% | -4.33% | -25.21% | -6.79% | NaN | -16.28% | +| DL average-UPT gain for layer-2 | Mean | | -77.47% | | -85.28% | | -87.47% | +| | 5% | | -82.06% | | -94.66% | | -93.03% | +| | 50% | | -80.18% | | -88.13% | | -91.71% | +| UL average-UPT gain for layer-1 | Mean | 10.18% | 0.34% | 1630.98% | 0.17% | NaN | 0.61% | +| | 5% | 97.08% | 0% | NaN | 1.77% | NaN | 13.09% | +| | 50% | 15.28% | -0.12% | 5770.71% | 0.34% | NaN | 0.6% | +| UL average-UPT gain for layer-2 | Mean | | 189.71% | | 214.49% | | 253.72% | +| | 5% | | 99.97% | | 240.18% | | 452.05% | +| | 50% | | 197.68% | | 211.98% | | 242.67% | + +Note: In the evaluation of source 1 ([44]), FR1 Urban macro (i.e., 1-layer) is assumed. And in the evaluation of source 2 ([32]), FR1 2-layer Scenario B is assumed. + +Note 2: If the gain for DL/UL Average-UPT is quoted as NaN, it means that the throughput for the reference scheme (baseline) is zero. + +### Summary of observations + +For the following observations, UPT gain in the range of {-5%, 5%} is considered as similar UPT. + +For dynamic/flexible TDD with aligned UL slot(s) between gNBs compared to reference scheme (i.e., dynamic TDD with full flexible slots for source 1([44]), static TDD for source 2 ([32])): + +#### (1) FR1 Urban Macro scenario + +In case of large packet size, based on results from 1 source, + +- Time Domain Scheme using UL slot(s) aligned between gNBs has lower mean DL Average-UPT for low and medium load levels, higher mean DL Average-UPT for high load level, lower 5% DL Average-UPT for low load level, and higher 5% DL Average-UPT for medium and high load levels. +- Time Domain Scheme using UL slot(s) aligned between gNBs has higher mean and 5% UL Average-UPT for all load levels. + +## (2) FR1 2-layer Scenario B + +In case of large packet size, based on results from 1 source, + +- Time Domain Scheme using UL slot(s) aligned between gNBs has lower or similar mean and 5% DL Average-UPT for all load levels. +- Time Domain Scheme using UL slot(s) aligned between gNBs has higher or similar mean and 5% UL Average-UPT for all load levels. + +### 8.3.2A.4 Specification impact of the proposed scheme + +- Source 1 ([44]) + - No specification impacts +- Source 2 ([32]) + - No specification impacts + +## 8.3.2B Inter-gNB CLI scheme 2B: Frequency domain coordination scheme + +### 8.3.2B.1 Reference scheme for performance comparison + +- Source 1 ([26]) + - Deployment scenario #1: Indoor office (InH) with dynamic TDD assignment (FFFFF). + - Deployment scenario #2: Urban Macro (UMa) with dynamic TDD assignment (DFFFU) of either DL-heavy (DDDSU) or UL-heavy (DSUUU) TDD pattern. +- Source 2 ([24]) + - Two-layer scenario with Rel-17 dynamic TDD. + +### 8.3.2B.2 Proposed scheme + +- Source 1 ([26]) + - The frequency resources within a carrier are split into a DL-only resource (i.e., DL subband) and UL-only resources (UL-subband) [in asynchronous/CLI slots]. + - This subband split provides frequency isolation between aggressor and victim gNBs which helps mitigate inter-gNB co-channel CLI. + - Each gNB can either transmit in the downlink resource or receive in the uplink resource +- Source 2 ([24]) + - Layer-1 gNBs assume static TDD [DDDSU] while the Layer-2 gNBs use [DFFFU]. During “F” slots, Layer 2 gNBs prioritizes UL scheduling in case that DL and UL traffic is available for transmission at gNB and UEs buffers. In case that a traffic from a single direction is available, gNBs will use the corresponding resource in the given “F” slot. The Layer-1 gNBs will ensure that there is no DL transmission scheduled on the legacy TDD DL slots that overlaps with the UL resource of the “F” slots of the Layer-2 gNBs. + +### 8.3.2B.3 Performance evaluation or analysis + +2 sources ([26], [24]) provided SLS evaluation results for performance comparison between dynamic TDD without frequency domain resource coordination and dynamic TDD with frequency domain resource coordination. The evaluation results are captured in Annex B.4. + +The summary of DL average-UPT gain and UL average-UPT gain are provided in Table 8.3.2B.3-1 and 8.3.2B.3-2, where large packet size and small packet size are assumed respectively. + +**Table 8.3.2B.3-1: Frequency Domain Coordination Scheme vs. No Coordination (Large Packet Size (0.5Mbyte for DL and 0.125 Mbytes for UL))** + +| | | Low load | | | Medium load | | | High load | | | +|---------------------------------|------|------------------------|-----------------------------|-----------------|------------------------|-----------------------------|-----------------|------------------------|-----------------------------|-----------------| +| | | Source 1 ([26]) Indoor | Source 1 ([26]) Urban Macro | Source 2 ([24]) | Source 1 ([26]) Indoor | Source 1 ([26]) Urban Macro | Source 2 ([24]) | Source 1 ([26]) Indoor | Source 1 ([26]) Urban Macro | Source 2 ([24]) | +| DL average-UPT gain for layer-1 | Mean | -23.81% | -13.90% | -21.87% | -19.9% | -20.05% | -24.29% | -17.99% | -31.80% | -28.3% | +| | 5% | -25.71% | -23.01% | -36.01% | -20.6% | -74.00% | -43.44% | -21.17% | -100.00% | -55.13% | +| | 50% | -22.97% | -15.08% | -16.83% | -18.88% | -26.67% | -24.4% | -15.46% | -48.17% | -30.02% | +| DL average-UPT gain for layer-2 | Mean | | | -29.7% | | | -44.17% | | | -53.65% | +| | 5% | | | -53.39% | | | -60.52% | | | -44.41% | +| | 50% | | | -33.92% | | | -51.9% | | | -80.45% | +| UL average-UPT gain for layer-1 | Mean | -56.89% | -34.87% | 19.27% | -31.07% | -22.68% | -0.45% | -25.18% | -7.40% | -6.89% | +| | 5% | -53.93% | NAN | 123.91% | -8.67% | NAN | 33.28% | 32.45% | NAN | -4.93% | +| | 50% | -56.18% | -25.98% | 3.56% | -30.66% | 54.94% | -21.57% | -23.72% | NAN | -34.32% | +| UL average-UPT gain for layer-2 | Mean | | | -47.14% | | | -31.01% | | | 4.62% | +| | 5% | | | -18.33% | | | -22.29% | | | -12.24% | +| | 50% | | | -46.91% | | | -25.59% | | | 32.86% | + +Note: In the evaluation of source 1 ([26]), Indoor office and FR1 Urban Macro are assumed, respectively. And in the evaluation of source 2 ([24]), FR1 2-layer Scenario B is assumed. + +Note 2: If the gain for DL/UL Average-UPT is quoted as NaN, it means that the throughput for the reference scheme (baseline) is zero. + +**Table 8.3.2B.3-2: Frequency domain coordination scheme vs. no coordination (Small Packet Size (4Kbytes for DL and 1Kbyte for UL))** + +| | | Low load | | Medium load | | High load | | +|---------------------|------|------------------------|-----------------------------|------------------------|-----------------------------|------------------------|-----------------------------| +| | | Source 1 ([26]) Indoor | Source 1 ([26]) Urban Macro | Source 1 ([26]) Indoor | Source 1 ([26]) Urban Macro | Source 1 ([26]) Indoor | Source 1 ([26]) Urban Macro | +| DL average-UPT gain | Mean | -1.13% | 4.27% | -0.76% | 0% | -0.36% | -8.56% | +| | 5% | -1.47% | -21.03% | -0.48% | -60.33% | -0.94% | -98.78% | +| | 50% | -1.23% | 6.26% | -0.65% | 5.35% | -0.16% | 2.01% | +| UL average-UPT gain | Mean | 0.52% | 34.24% | 0.65% | 54.77% | 6.59% | 103.83% | +| | 5% | 0.37% | 265.84% | 0.35% | 95803.92% | 58.13% | N/A% | +| | 50% | 0.4% | 32.7% | 0.58% | 51.75% | 0.72% | 185.86% | + +Note: In the evaluation of source 1 ([26]), Indoor office and FR1 Urban Macro are assumed, respectively. + +#### Summary of observations + +For the following observations, UPT gain in the range of {-5%, 5%} is considered as similar UPT. + +For Frequency Domain Coordination Scheme compared to No Coordination: + +(1) FR1 Urban Macro scenario + +In case of large packet size, based on results from 1 source, + +- Frequency Domain Coordination Scheme has lower mean and 5% DL Average-UPT for all load levels. + +- Frequency Domain Coordination Scheme has lower UL Average-UPT mean and higher 5% UL Average-UPT for all load levels. + +In case of small packet size, based on results from 1 source, + +- Frequency Domain Coordination Scheme has lower or similar mean and 5% DL Average-UPT for all load levels. +- Frequency Domain Coordination Scheme has higher mean and 5% UL Average-UPT for all load levels. + +## (2) Indoor office scenario + +In case of large packet size, based on results from 1 source, + +- Frequency Domain Coordination Scheme has lower mean and 5% DL Average-UPT for all load levels. +- Frequency Domain Coordination Scheme has lower mean UL Average-UPT for all load levels, lower 5% UL Average-UPT for low and medium load levels and higher 5% UL Average-UPT for high load. + +In case of small packet size, based on results from 1 source, + +- Frequency Domain Coordination Scheme has similar mean and 5% DL Average-UPT for all load levels. +- Frequency Domain Coordination Scheme has similar mean and 5% UL Average-UPT for low and medium load levels, and higher mean and 5% UL Average-UPT for high load level + +## (3) FR1 2-layer Scenario B + +In case of large packet size, based on results from 1 source, + +- Frequency Domain Coordination Scheme has lower or similar mean and 5% DL Average-UPT for all load levels. +- Frequency Domain Coordination Scheme has higher or similar mean and 5% UL Average-UPT for layer-1 for low and medium load levels, and lower or similar mean and 5% UL Average-UPT for layer-1 for high load levels +- Frequency Domain Coordination Scheme has lower or similar mean and 5% UL Average-UPT for layer-2 for all load levels. + +### 8.3.2B.4 Specification impact of the proposed scheme + +- Source 1 ([26]) + - Information exchange between gNBs of the locations of the frequency domain resources reserved for DL-only transmission or UL-only reception. +- Source 2 ([24]) + - Information exchange between gNBs. + +## 8.3.3 Spatial domain coordination method + +### 8.3.3.1 Description + +RAN1 studies the feasibility and potential benefits of spatial domain coordination method for gNB-to-gNB co-channel CLI handling, which can be specific for dynamic/flexible TDD and/or common for both SBFD and dynamic/flexible TDD. In the study, at least followings are included: + +- Details for spatial domain coordination +- Relevant information exchange + +Note1: Study can include method for FR1 and FR2 + +For details of spatial domain coordination method for gNB-to-gNB co-channel CLI handling, at least followings can be studied. + +- Recommended/restricted Beams between gNBs +- Beam nulling between gNBs +- Beam pairing between gNBs +- Other schemes are not precluded. + +For spatial domain coordination, the exchange of beam related information among gNB(s) (e.g., victim gNB(s) and aggressor gNB(s)) can be an enabler for inter-gNB co-channel CLI management. + +- For example 1 (from aggressor gNB to victim gNB), DL beam indication from aggressor gNB(s) +- For example 2 (from victim gNB to aggressor gNB), preferred/restricted DL beam and associated resource configuration, beam based inter-gNB co-channel CLI measurement result from victim gNB + +Note: The above examples are only provided as starting point for further discussions + +For spatial domain enhancement of gNB-to-gNB co-channel CLI handling, RAN1 has discussed the exchange of DL Tx beam information of the gNB between gNBs. + +Reference signal resource ID (e.g., NZP-CSI-RS resource ID, SSB index) RAN1 has discussed the exchange of beam information between gNBs. + +For spatial domain enhancement of gNB-to-gNB CLI handling, RAN1 studies the benefit and the procedure of the information exchange of at least the preferred/non-preferred DL beams of the aggressor gNBs, based on the beam information exchanged between gNBs. + +### 8.3.3.2 Performance evaluation or analysis + +For performance evaluation of *Spatial Domain Coordination Scheme for gNB Tx-Beam Nulling*, three sources ([43], [26], [42]) provide the evaluation results. The evaluation results are summarized in section 8.3.3A and the tables for the evaluation result are shown in Annex B.4. + +### 8.3.3.3 Specification impact + +For CLI handling based on spatial domain coordination, RAN1 discussed potential exchange of information among gNBs on DL Tx beam information of the gNB, Reference signal resource ID such as NZP-CSI-RS resource ID, SSB index, preferred/non-preferred DL beam and associated resource configuration. + +Specification impact of *Spatial Domain Coordination Scheme for gNB Tx-Beam Nulling* is summarized in section 8.3.3A.4. + +## 8.3.3A Inter-gNB CLI scheme 3A: Spatial domain coordination scheme for gNB Tx-Beam nulling + +### 8.3.3A.1 Reference scheme for performance comparison + +- Source 1 ([43]) + - No Tx beam nulling since the aggressor gNB does not know the channel information between the aggressor gNB and victim gNB. +- Source 2 ([26]) + - Deployment scenario #1: Indoor office (InH) with Dynamic TDD without aggressor (Tx) gNB nulling due to lack of inter-gNB channel information and lack of inter-gNB CLI measurements. + - Deployment scenario #2: Urban Macro (UMa) with Semi-static SBFD without aggressor (Tx) gNB nulling due to lack of inter-gNB channel information and lack of inter-gNB CLI measurement. +- Source 3 ([42]) + +- No Tx beam nulling since the aggressor gNB does not know the channel information between the aggressor gNB and victim gNB. + +### 8.3.3A.2 Proposed Scheme + +- Source 1 ([43]) + - Tx beam nulling is performed by the aggressor gNB. + - The victim gNB measures the channel information based on the NZP CSI-RS transmitted from the aggressor gNB to the victim gNB and then delivers the measured channel information to the aggressor gNB. + - The aggressor gNB determines the DL precoder for its serving UEs by considering the channel information between aggressor gNB and victim gNB so that the DL transmission beam has the least interference to the victim gNB. +- Source 2 ([26]) + - Aggressor gNB Tx nulling towards victim gNB(s) based on knowledge of the channel between the aggressor and victim gNB(s). + - Victim gNB(s) are identified based on inter-gNB CLI measurements. +- Source 3 ([42]) + - Same as the proposed scheme of source 1 + +### 8.3.3A.3 Performance evaluation or analysis + +3 sources ([42], [26], [43]) provided SLS evaluation results for performance comparison between dynamic TDD without aggressor gNB Tx beam nulling and dynamic TDD with aggressor gNB Tx beam nulling. The evaluation results are captured in Annex B.4. + +The summary of DL average-UPT gain and UL average-UPT gain are provided in Table 8.3.3A.3-1 and 8.3.3A.3-2, where large packet size and small packet size are assumed respectively. + +**Table 8.3.3A.3-1: gNB Tx-Beam nulling vs. no aggressor gNB Tx-Beam nulling (Large Packet Size (0.5Mbyte for DL and 0.125 Mbytes for UL))** + +| | | Low load | | | Medium load | | | High load | | | +|---------------------------------|-------------------|--------------------------|-----------------------------|-----------------|--------------------------|-------------------------------------------|-----------------|--------------------------------|-------------------------------------------|---------------------| +| | | Source 1 ([43]) | Source 2 ([26]) | Source 3 ([42]) | Source 1 ([43]) | Source 2 ([26]) | Source 3 ([42]) | Source 1 ([43]) | Source 2 ([26]) | Source 3 ([42]) | +| DL average-UPT gain for layer-1 | Mean
5%
50% | 1.99%
-2.7%
3.85% | -9.84%
-23.54%
-6.71% | | 1.94%
1.12%
2.61% | -12.76
%
-29.12
%
-11.09
% | | 1.68%
-27.65
%
1.03% | -13.25
%
-30.24
%
-10.76
% | -4.9%
~
-5.7% | +| DL average-UPT gain for layer-2 | Mean
5%
50% | | | | | | | | | | +| UL average-UPT gain for layer-1 | Mean
5%
50% | 0.47%
24.34%
2.16% | 9.59%
16.77%
11.04% | | 6.36%
32.04%
0.33% | 73.07%
97.95%
74.05% | | 20.67%
360.03
%
16.4% | 114.8%
311.7%
123.5% | | +| UL average-UPT gain for layer-2 | Mean
5%
50% | | | | | | | | | 21% ~
28% | + +Note: In the evaluation of source 1 ([43]), FR1 Urban Macro is assumed. In the evaluation of source 2 ([26]), FR1 Indoor office is assumed. In the evaluation of source 3 ([42]), FR1 field test under 2-layer Scenario B is assumed + +**Table 8.3.3A.3-2: gNB Tx-Beam nulling vs. no aggressor gNB Tx-Beam nulling (Small Packet Size (4Kbytes for DL and 1Kbyte for UL))** + +| | | Low load | Medium load | High load | +|--|--|-----------------|-----------------|-----------------| +| | | Source 2 ([26]) | Source 2 ([26]) | Source 2 ([26]) | + +| | | | | | +|----------------------------|-------------|--------|--------|--------| +| DL average-UPT gain | Mean | -0.36% | -0.85% | -1.51% | +| | 5% | -0.96% | -0.31% | -5.48% | +| | 50% | -0.26% | -0.68% | -0.5% | +| UL average-UPT gain | Mean | 0.28% | 0.37% | 7.5% | +| | 5% | 0.47% | 0.41% | 65.99% | +| | 50% | 0.25% | 0.29% | 0.75% | + +Note: In the evaluation of source 2 ([26]), FR1 Indoor office is assumed. + +### **Summary of observations** + +For the following observations, UPT gain in the range of {-5%, 5%} is considered as similar UPT. + +For gNB Tx-Beam Nulling compared to no gNB Tx-Beam Nulling: + +In case of large packet size, based on results from 3 sources, + +- gNB Tx-Beam Nulling has lower or similar mean and 5% DL Average-UPT for all load levels. +- gNB Tx-Beam Nulling has higher or similar mean and 5% UL Average-UPT for all load levels. + +In case of small packet size, based on results from 1 source, + +- gNB Tx-Beam Nulling has lower or similar mean and 5% DL Average-UPT for all load levels. +- gNB Tx-Beam Nulling has higher or similar mean and 5% UL Average-UPT for all load levels. + +### **8.3.3A.4 Specification impact of the proposed scheme** + +- Source 1 ([43]) + - The information exchange between the aggressor gNB and victim gNB, including the measurement resource and the measurement results. +- Source 2 ([26]) + - Co-channel CLI/channel measurements based on information exchange between gNBs of the CLI resource configuration and CLI measurement reports. + - Note: CLI measurement reports are needed to identify victim gNB(s) and CLI resource configuration (e.g. CSI-RS resource) is needed to estimate the channel between the aggressor and victim gNBs. +- Source 3 ([42]) + - Same as the specification impact of the proposed scheme of source 1 + +## **8.3.4 UE and gNB transmission and reception timing** + +### **8.3.4.1 Description** + +For gNB-gNB co-channel CLI measurement and channel measurement, RAN1 studies the impact on system performance because of CLI measurement inaccuracy at victim gNB due to misalignment between UL timing at victim gNB and DL reception timing at victim gNB of CLI measurement resource transmitted from one or more aggressor gNB. + +- Including potential impact on UL performance + +## **8.3.5 Power control based solution** + +### **8.3.5.1 Description** + +RAN1 studies the effect on DL performance and the UL performance of DL Tx power adjustment to evaluate the feasibility of such scheme to overcome the gNB-to-gNB co-channel CLI. + +RAN1 studies the effect on DL/UL performance and specification impact of applying separate open-loop/closed-loop power control parameters with cochannel CLI and without cochannel CLI for the uplink power control of a UE + +### 8.3.5.2 Performance evaluation or analysis + +For performance evaluation of *Power Control scheme based on gNB Tx Power Adjustment*, two sources ([24], [26]) provide the evaluation results. The evaluation results are summarized in section 8.3.5A and the tables for the evaluation result are shown in Annex B.4. + +For performance evaluation of *Power Control scheme based on UE Tx Power Adjustment*, two sources ([24], [26]) provide the evaluation results. The evaluation results are summarized in section 8.3.5B and the tables for the evaluation result are shown in Annex B.4. + +### 8.3.5.3 Specification impact + +Specification impact of *Power Control scheme based on gNB Tx Power Adjustment* and *Power Control scheme based on UE Tx Power Adjustment* are summarized in section 8.3.5A.4 and 8.3.5B.4, respectively. + +## 8.3.5A Inter-gNB CLI scheme 5A: Power control scheme based on gNB Tx power adjustment + +### 8.3.5A.1 Reference scheme for performance comparison + +- Source 1 ([24]) + - Dynamic TDD baseline operation. +- Source 2 ([26]) + - No DL power adjustment by the aggressor gNB with dynamic TDD assignment. + +### 8.3.5A.2 Proposed scheme + +- Source 1 ([24]) + - Aggressor gNB decreases the transmit power in agreed intervals with the victim gNB to ensure that the gNB-gNB CLI is kept within the tolerable limits at the victim gNB. +- Source 2 ([26]) + - DL power adjustment (e.g., power back-off) by the aggressor gNB at slots with inter-gNB CLI. + +### 8.3.5A.3 Performance evaluation or analysis + +2 sources ([24], [26]) provided SLS evaluation results for performance comparison between No DL power adjustment and DL power adjustment (e.g., power back-off) by the aggressor gNB. The evaluation results are captured in Annex B.4. + +In case of large packet size, the summary of DL average-UPT gain and UL average-UPT gain are provided in Table 8.3.5A.3-1 to 8.3.5A.3-3, where 3, 6 and 10 dB power back off are assumed, respectively. + +In case of small packet size, the summary of DL average-UPT gain and UL average-UPT gain are provided in Table 8.3.5A.3-4 to 8.3.5A.3-6, where 3, 6 and 10 dB power back off are assumed, respectively. + +**Table 8.3.5A.3-1: DL power adjustment (e.g., power back-off) by the aggressor gNB vs. No DL power adjustment (Large Packet Size (0.5Mbyte for DL and 0.125 Mbytes for UL), 3 dB Power back off)** + +| | | Low load | | | Medium load | | | High load | | | +|---------------------------------|------|-----------------|------------------------|-------------------------|-----------------|------------------------|-------------------------|-----------------|------------------------|-------------------------| +| | | Source 1 ([24]) | Source 2 ([26]) Indoor | Source 2 ([26]) 2-layer | Source 1 ([24]) | Source 2 ([26]) Indoor | Source 2 ([26]) 2-layer | Source 1 ([24]) | Source 2 ([26]) Indoor | Source 2 ([26]) 2-layer | +| DL average-UPT gain for layer-1 | Mean | -0.05% | -2.65% | 4.21% | -0.06% | -3.78% | 6.26% | -0.17% | -4.98% | 8.57% | +| | 5% | 0% | -6.38% | 6.87% | 0% | -4.46% | 96.65% | 11.2% | -7.17% | 1166% | +| | 50% | 0% | -2.24% | 3.09% | -0.07% | -4.35% | 5.85% | -0.49% | -4.67% | 8.11% | +| DL average-UPT gain for layer-2 | Mean | -0.01% | | 7.55% | 0.1% | | 32.39% | 1.02% | | 59.96% | +| | 5% | 0% | | 12.58% | 6.83% | | 46.6% | 0.05% | | 238.9% | +| | 50% | 0% | | 6.32% | 0.54% | | 33.31% | 4.79% | | 56.05% | +| UL average-UPT gain for layer-1 | Mean | 0% | 2.76% | 2.09% | -0.06% | 16.06% | 5.68% | -0.27% | 24.11% | 7.43% | +| | 5% | 0% | 3.19% | 6.45% | -0.08% | 19.37% | 271.2% | -5.23% | 50.71% | 290% | +| | 50% | 0% | 4.35% | 0.64% | -0.45% | 17.02% | 2.82% | 0.46% | 26% | 4.34% | + +| | | | | | | | | | | | +|---------------------------------|------|-------|--|-------|-------|--|--------|--------|--|--------| +| UL average-UPT gain for layer-2 | Mean | 0.47% | | 2.15% | 5.29% | | 11.83% | 7.9% | | 16.86% | +| | 5% | 0% | | 3.49% | 3.21% | | 51.49% | -0.06% | | 5635% | +| | 50% | 0.62% | | 2.03% | 4.86% | | 13.13% | 8.75% | | 16.02% | + +Note: In the evaluation of Source 1 ([24]), FR1 2-layer Scenario B is assumed. Also, in the evaluation of Source 2 ([26]), FR1 Indoor office and FR1 2-layer Scenario B are assumed, respectively. + +**Table 8.3.5A.3-2: DL power adjustment (e.g., power back-off) by the aggressor gNB vs. No DL power adjustment (Large Packet Size (0.5Mbyte for DL and 0.125 Mbytes for UL), 6 dB Power back off)** + +| | | Low load | | | Medium load | | | High load | | | +|---------------------------------|-------------------|----------------------|------------------------------|----------------------------|----------------------------|----------------------------|----------------------------|----------------------------|----------------------------------|-----------------------------| +| | | Source 1 ([24]) | Source 2 ([26]) Indoor | Source 2 ([26]) 2-layer | Source 1 ([24]) | Source 2 ([26]) Indoor | Source 2 ([26]) 2-layer | Source 1 ([24]) | Source 2 ([26]) Indoor | Source 2 ([26]) 2-layer | +| DL average-UPT gain for layer-1 | Mean
5%
50% | -0.14%
0%
0% | -5.87%
-11.43 %
-5.09% | 6.9%
13.62%
5.37% | -0.42%
-2.62%
-0.18% | -7.89%
-9.4%
-7.91% | 11.22%
221.0%
9.68% | -0.4%
-4.63%
-0.67% | -10.99 %
-13.77 %
-12.16 % | 16.38%
586923 %
14.7% | +| DL average-UPT gain for layer-2 | Mean
5%
50% | -0.03%
0%
0% | | 13.45%
16.24%
12.53% | -0.37%
-2.77%
0.09% | | 68.37%
126.5%
69.27% | 1.27%
-0.14%
6.16% | | 221.7%
7672%
307.6% | +| UL average-UPT gain for layer-1 | Mean
5%
50% | 0%
0%
0% | 6.15%
7.61%
8.29% | 3.81%
10.85%
1.16% | -0.01%
3.25%
0.23% | 33.45%
44.55%
32.69% | 11.22%
380.7%
5.11% | -0.33%
-0.72%
-2.69% | 48.7%
101.4%
53.4% | 14.15%
23344 %
6.74% | +| UL average-UPT gain for layer-2 | Mean
5%
50% | 0.94%
0%
0.63% | | 4.42%
13.85%
4.06% | 10.01%
-4.86%
11.16% | | 23.43%
91.28%
25.19% | 15.96%
0.75%
18.02% | | 35.82%
16230 %
35.31% | + +Note: In the evaluation of Source 1 ([24]), FR1 2-layer Scenario B is assumed. Also, in the evaluation of Source 2 ([26]), FR1 Indoor office and FR1 2-layer Scenario B are assumed, respectively. + +**Table 8.3.5A.3-3: DL power adjustment (e.g., power back-off) by the aggressor gNB vs. No DL power adjustment (Large Packet Size (0.5Mbyte for DL and 0.125 Mbytes for UL), 10 dB Power back off)** + +| | | Low load | | | Medium load | | | High load | | | +|---------------------------------|-------------------|----------------------------|----------------------------------|----------------------------|---------------------------|--------------------------------|----------------------------|----------------------------|----------------------------------|------------------------------| +| | | Source 1 ([24]) | Source 2 ([26]) Indoor | Source 2 ([26]) 2-layer | Source 1 ([24]) | Source 2 ([26]) Indoor | Source 2 ([26]) 2-layer | Source 1 ([24]) | Source 2 ([26]) Indoor | Source 2 ([26]) 2-layer | +| DL average-UPT gain for layer-1 | Mean
5%
50% | -0.47%
-0.85%
-0.01% | -10.99 %
-18.82 %
-11.24 % | 11.62%
87.21%
10.01% | -1.08%
-2%
-0.62% | -14.3%
-16.64 %
-15.46 % | 17.75%
289.7%
16.28% | -1.63%
-7.94%
-2.44% | -20.21 %
-27.89 %
-23.34 % | 25.81%
671219 %
24.76% | +| DL average-UPT gain for layer-2 | Mean
5%
50% | -0.06%
0%
0% | | 17.04%
14.03%
14.75% | -0.65%
0%
-0.6% | | 93.14%
146.6%
92.38% | 1.17%
-0.33%
6.13% | | 368.8%
27726 %
465.4% | +| UL average-UPT gain for layer-1 | Mean
5%
50% | 0%
0%
0% | 9.81%
16.42%
11.93% | 6.22%
39.32%
1.96% | 0.12%
3.25%
-0.9% | 56.24%
71.8%
57.29% | 16.38%
451.0%
9.46% | -0.03%
-2.05%
-0.86% | 82.33%
177.1%
93.13% | 24.51%
52460 %
13.69% | +| UL average-UPT gain for layer-2 | Mean
5%
50% | 1.51%
0%
1.84% | | 8.31%
30.33%
5.6% | 16.75%
1.21%
19.33% | | 42.61%
188.1%
43.85% | 26.68%
-1.47%
30.51% | | 70.35%
38236 %
66.23% | + +Note: In the evaluation of Source 1 ([24]), FR1 2-layer Scenario B is assumed. Also, in the evaluation of Source 2 ([26]), FR1 Indoor office and FR1 2-layer Scenario B are assumed, respectively. + +**Table 8.3.5.A.3-4: DL power adjustment (e.g., power back-off) by the aggressor gNB vs. No DL power adjustment (Small Packet Size (4Kbytes for DL and 1Kbyte for UL), 3 dB Power back off)** + +| | | Low load | | Medium load | | High load | | +|--|--|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| | | Source 2 ([26]) | Source 2 ([26]) | Source 2 ([26]) | Source 2 ([26]) | Source 2 ([26]) | Source 2 ([26]) | + +| | | Indoor | 2-layer | Indoor | 2-layer | Indoor | 2-layer | +|---------------------------------|------|--------|---------|--------|---------|--------|----------| +| DL average-UPT gain for layer-1 | Mean | 0.01% | 0.1% | 0.09% | 1.16% | -0.09% | 3.39% | +| | 5% | 0.02% | 0.15% | -0.09% | 3.97% | -0.11% | 6096.27% | +| | 50% | -0.12% | 0.04% | 0.05% | 0.12% | -0.07% | 0.25% | +| DL average-UPT gain for layer-2 | Mean | | 0.22% | | 2.05% | | -1.19% | +| | 5% | | -0.13% | | 3.58% | | -16.29% | +| | 50% | | 0.4% | | 1.47% | | 0.84% | +| UL average-UPT gain for layer-1 | Mean | 0.11% | 0.07% | 0.16% | 2.26% | 5.05% | 5.69% | +| | 5% | 0.26% | -0.19% | 0.11% | 16.54% | 50.87% | 1330.07% | +| | 50% | 0.05% | -0.06% | 0.07% | 0.11% | 0.23% | 0.31% | +| UL average-UPT gain for layer-2 | Mean | | -0.21% | | 4.62% | | 7.98% | +| | 5% | | -6.42% | | 11.75% | | 2991.93% | +| | 50% | | -0.34% | | 2.42% | | 8.8% | + +Note: In evaluation of Source 2 ([26]), FR1 Indoor office and FR1 2-layer Scenario B are assumed, respectively. + +**Table 8.3.5A.3-5: DL power adjustment (e.g., power back-off) by the aggressor gNB vs. No DL power adjustment (Small Packet Size (4Kbytes for DL and 1Kbyte for UL), 6 dB Power back off)** + +| | | Low load | | Medium load | | High load | | +|---------------------------------|------|------------------------|-------------------------|------------------------|-------------------------|------------------------|-------------------------| +| | | Source 2 ([26]) Indoor | Source 2 ([26]) 2-layer | Source 2 ([26]) Indoor | Source 2 ([26]) 2-layer | Source 2 ([26]) Indoor | Source 2 ([26]) 2-layer | +| DL average-UPT gain for layer-1 | Mean | -0.03% | 0.14% | 0.17% | 1.58% | -0.04% | 5.71% | +| | 5% | 0.01% | 0.32% | 0.07% | 7.63% | -0.26% | 14728.28% | +| | 50% | 0.04% | 0.16% | 0.34% | 0.26% | -0.02% | 0.41% | +| DL average-UPT gain for layer-2 | Mean | | 0.28% | | 4.11% | | 1.94% | +| | 5% | | 0.13% | | 9.69% | | -0.85% | +| | 50% | | 0.2% | | 3.1% | | 3.43% | +| UL average-UPT gain for layer-1 | Mean | 0.21% | 0.13% | 0.3% | 3.59% | 6.91% | 10.51% | +| | 5% | 0.34% | -0.05% | 0.2% | 18.67% | 62.5% | 2875.02% | +| | 50% | 0.15% | -0.02% | 0.17% | 0.3% | 0.49% | 0.47% | +| UL average-UPT gain for layer-2 | Mean | | -0.47% | | 8.05% | | 13.11% | +| | 5% | | -6.69% | | 53.81% | | 14512.05% | +| | 50% | | -0.58% | | 2.91% | | 10.33% | + +Note: In evaluation of Source 2 ([26]), FR1 Indoor office and FR1 2-layer Scenario B are assumed, respectively. + +**Table 8.3.5A.3-6: DL power adjustment (e.g., power back-off) by the aggressor gNB vs. No DL power adjustment (Small Packet Size (4Kbytes for DL and 1Kbyte for UL), 10 dB Power back off)** + +| | | Low load | | Medium load | | High load | | +|---------------------------------|------|------------------------|-------------------------|------------------------|-------------------------|------------------------|-------------------------| +| | | Source 2 ([26]) Indoor | Source 2 ([26]) 2-layer | Source 2 ([26]) Indoor | Source 2 ([26]) 2-layer | Source 2 ([26]) Indoor | Source 2 ([26]) 2-layer | +| DL average-UPT gain for layer-1 | Mean | -0.28% | 0.22% | 0.32% | 2.92% | 0.08% | 9.76% | +| | 5% | -0.21% | 0.12% | 0.04% | 9.2% | -0.07% | 20686.98% | +| | 50% | -0.26% | 0.19% | 0.41% | 0.4% | 0.14% | 0.65% | +| DL average-UPT gain for layer-2 | Mean | | 0.42% | | 5.39% | | 5.6% | +| | 5% | | -0.04% | | 14.26% | | 21.94% | +| | 50% | | 0.54% | | 3.79% | | 4.39% | +| UL average-UPT gain for layer-1 | Mean | 0.29% | 0.18% | 0.42% | 3.77% | 7.44% | 12.23% | +| | 5% | 0.45% | 0.27% | 0.36% | 18.98% | 65.43% | 2964.35% | +| | 50% | 0.22% | 0.01% | 0.29% | 0.57% | 0.74% | 0.73% | +| UL average-UPT gain for layer-2 | Mean | | -0.49% | | 11.39% | | 20.42% | +| | 5% | | -5.61% | | 107.64% | | 31118.67% | +| | 50% | | -0.66% | | 3.36% | | 11.01% | + +Note: In evaluation of Source 2 ([26]), FR1 Indoor office and FR1 2-layer Scenario B are assumed, respectively. + +## Summary of observations + +For the following observations, UPT gain in the range of {-5%, 5%} is considered as similar UPT. + +For DL power adjustment (e.g., power back-off) by the aggressor gNB compared to no DL power adjustment: + +- (1) FR1 2-layer Scenario B scenario + +In case of large packet size, based on results from 2 sources, + +- DL power adjustment (e.g., power back-off) by the aggressor gNB has higher or similar mean and 5% DL Average-UPT for all load levels. +- DL power adjustment (e.g., power back-off) by the aggressor gNB has higher or similar mean and 5% UL Average-UPT for all load levels. + +In case of small packet size, based on results from 1 source, + +- DL power adjustment (e.g., power back-off) by the aggressor gNB has higher or similar mean and 5% DL Average-UPT for all load levels. +- DL power adjustment (e.g., power back-off) by the aggressor gNB has higher or similar mean and 5% UL Average-UPT for all load levels. + +## (2) FR1 Indoor office scenario + +In case of large packet size, based on results from 1 source, + +- DL power adjustment (e.g., power back-off) by the aggressor gNB has lower mean and 5% DL Average-UPT for all load levels. +- DL power adjustment (e.g., power back-off) by the aggressor gNB has higher mean and 5% UL Average-UPT for all load levels. + +In case of small packet size, based on results from 1 source, + +- DL power adjustment (e.g., power back-off) by the aggressor gNB has similar mean and 5% DL Average-UPT for all load levels. +- DL power adjustment (e.g., power back-off) by the aggressor gNB has similar mean and 5% UL Average-UPT for all low and medium load levels and higher mean and 5% UL Average-UPT for high load. + +### 8.3.5A.4 Specification impact of the proposed scheme + +- Source 1 ([24]) + - Xn signaling enhancements to support the handshake agreement between victim and aggressor gNB for the DL transmit power reduction, for example: + - Step 0: Measurements and identification of aggressor(s). + - Step 1: Indication of DL Tx power reduction by the victim gNB. + - Step 2: Confirmation by the aggressor gNB on whether it can accept the new DL Tx power conditions. +- Source 2 ([26]) + - Information exchange between gNBs of recommended DL power adjustment of aggressor gNB based on CLI measurements. + +### 8.3.5B Inter-gNB CLI scheme 5B: Power control scheme based on UE Tx power adjustment + +#### 8.3.5B.1 Reference scheme for performance comparison + +- Source 1 ([24]) + - Dynamic TDD baseline operation. +- Source 2 ([26]) + - Dynamic TDD with same UL power control parameters for slots with CLI (asynchronous slots) and slots without CLI (synchronous slots). + +### 8.3.5B.2 Proposed Scheme + +- Source 1 ([24]) + - UE Tx power optimization to improve the UL SINR condition on the victim gNBs +- Source 2 ([26]) + - Different UL power control parameters for slots with CLI and slots without CLI. + +### 8.3.5B.3 Performance evaluation or analysis + +2 sources ([24], [26]) provided SLS evaluation results for performance of UE Tx power adjustment. The evaluation results are captured in Annex B.4. + +For the 1st proposed scheme (i.e., UE Tx power optimization of source 1 ([24])), the summary of DL average-UPT gain and UL average-UPT gain are provided in Table 8.3.5B.3-1, where large packet size is assumed. + +For the 2nd proposed scheme (i.e., different UL power control parameters of source 2 ([26])), the summary of DL average-UPT gain and UL average-UPT gain are provided in Table 8.3.5B.3-2 to Table 8.3.5B.3-5, where large packet size and small packet size are assumed. + +**Table 8.3.5B.3-1: UE Tx power optimization vs. Dynamic TDD baseline operation (Large Packet Size (0.5Mbyte for DL and 0.125 Mbytes for UL), 5/10/15 dB P0 offset)** + +| | | Low load | | | Medium load | | | High load | | | +|---------------------------------|------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| | | Source 1 ([24]) | | | Source 1 ([24]) | | | Source 1 ([24]) | | | +| | | 5 dB P0 offset | 10 dB P0 offset | 15 dB P0 offset | 5 dB P0 offset | 10 dB P0 offset | 15 dB P0 offset | 5 dB P0 offset | 10 dB P0 offset | 15 dB P0 offset | +| DL average-UPT gain for layer-1 | Mean | -0.02% | -0.20% | -0.17% | -0.03% | -0.29% | -0.23% | -0.03% | -0.31% | -0.22% | +| | 5% | -0.22% | -6.59% | -1.97% | -0.22% | -5.85% | -4.68% | -0.22% | -4.36% | -6.16% | +| DL average-UPT gain for layer-2 | Mean | 0.00% | -0.15% | -0.37% | 0.00% | -0.15% | -0.47% | 0.00% | -0.15% | -0.32% | +| | 50% | -0.03% | -2.11% | -2.97% | -0.04% | -2.78% | -4.14% | -0.04% | -2.71% | -5.10% | +| UL average-UPT gain for layer-1 | Mean | 0.00% | -0.04% | 0.26% | 0.06% | -0.18% | -0.18% | 0.06% | 0.19% | -0.17% | +| | 50% | 0.00% | -7.43% | 3.82% | 0.00% | -0.13% | 6.26% | 0.00% | -1.58% | 6.70% | +| UL average-UPT gain for layer-2 | Mean | 0.00% | -0.94% | 1.07% | 0.00% | -2.15% | 0.63% | 0.00% | -0.71% | 1.99% | +| | 50% | 33.96% | 56.07% | 40.24% | 34.68% | 58.98% | 39.28% | 34.68% | 58.33% | 38.74% | +| | 5% | 34.43% | 40.59% | 15.13% | 34.50% | 40.83% | 17.91% | 34.50% | 40.59% | 12.16% | +| | 50% | 44.95% | 54.11% | 35.94% | 44.97% | 58.44% | 37.75% | 44.97% | 55.93% | 35.94% | + +Note: In evaluation of Source 1 ([24]), FR1 2-layer Scenario B is assumed. + +**Table 8.3.5B.3-2: Different UL power control parameters vs. Same UL power control parameters (Large Packet Size (0.5Mbyte for DL and 0.125 Mbytes for UL), -33/-83dBm P0)** + +| | | Low load | | Medium load | | High load | | +|---------------------|------|-----------------|------------|-----------------|------------|-----------------|------------| +| | | Source 2 ([26]) | | Source 2 ([26]) | | Source 2 ([26]) | | +| | | -33 dBm P0 | -83 dBm P0 | -33 dBm P0 | -83 dBm P0 | -33 dBm P0 | -83 dBm P0 | +| DL average-UPT gain | Mean | -6% | 8.08% | -25.05% | 2.22% | -36.17% | 6.95% | +| | 5% | -4.18% | 11.2% | -25.45% | -2.04% | -45.26% | 7.28% | +| UL average-UPT gain | Mean | -5.22% | 6.53% | -26.14% | 4.53% | -40.75% | 10.94% | +| | 50% | 15.76% | -44.82% | 93.4% | -95.7% | 145.68% | -99.7% | +| | 5% | 27.38% | -48.39% | 116.18% | -100% | 310.56% | -100% | +| | 50% | 16.96% | -47.09% | 99.16% | -100% | 157.68% | -100% | + +Note: In evaluation of Source 2 ([26]), FR1 Indoor office is assumed. + +**Table 8.3.5B.3-3: Different UL power control parameters vs. Same UL power control parameters (Small Packet Size (4Kbytes for DL and 1Kbyte for UL), -33/-83dBm P0)** + +| | | Low load | | Medium load | | High load | | +|----------------|------|-----------------|------------|-----------------|------------|-----------------|------------| +| | | Source 2 ([26]) | | Source 2 ([26]) | | Source 2 ([26]) | | +| | | -33 dBm P0 | -83 dBm P0 | -33 dBm P0 | -83 dBm P0 | -33 dBm P0 | -83 dBm P0 | +| DL average-UPT | Mean | -0.28% | 0.53% | 0.47% | -0.02% | -1.02% | 0.52% | + +| | | | | | | | | +|----------------------------|-------------|--------|--------|-------|---------|--------|-------| +| gain | 5% | -0.14% | 0.44% | 0.2% | -0.03% | -4.41% | 0.31% | +| | 50% | -0.33% | 0.5% | 0.89% | 0.02% | -0.48% | 0.32% | +| UL average-UPT gain | Mean | -2.29% | -0.29% | 0.56% | -96.87% | 7.8% | -100% | +| | 5% | -4.57% | -0.56% | 0.4% | -100% | 65.91% | -100% | +| | 50% | -2.64% | -0.07% | 0.39% | -100% | 1.02% | -100% | + +Note: In evaluation of Source 2 ([26]), FR1 Indoor office is assumed. + +**Table 8.3.5B.3-4: Different UL power control parameters vs. Same UL power control parameters (Large Packet Size (0.5Mbyte for DL and 0.125 Mbytes for UL), -40/-70dBm P0)** + +| | | Low load | | Medium load | | High load | | +|----------------------------------------|-------------|------------------------|-------------------|------------------------|-------------------|------------------------|-------------------| +| | | Source 2 ([26]) | | Source 2 ([26]) | | Source 2 ([26]) | | +| | | -40 dBm P0 | -70 dBm P0 | -40 dBm P0 | -70 dBm P0 | -40 dBm P0 | -70 dBm P0 | +| DL average-UPT gain for layer-1 | Mean | -0.98% | 0.11% | -5.94% | 0.56% | -7.65% | -0.26% | +| | 5% | -6.89% | 1.14% | -100% | 20.29% | -100% | 8560.78% | +| | 50% | -1.01% | -0.08% | -4.99% | -0.17% | -7.34% | -1.23% | +| DL average-UPT gain for layer-2 | Mean | -0.85% | 0.17% | -50.27% | 1.45% | -41.4% | 11.49% | +| | 5% | -1.8% | -0.47% | -98.62% | 5.45% | -72.49% | 39.26% | +| | 50% | -0.28% | 0.61% | -52.41% | -0.11% | -79.13% | 11.7% | +| UL average-UPT gain for layer-1 | Mean | -1.06% | 0.07% | -3.45% | 0.15% | -4.43% | 0.32% | +| | 5% | -0.68% | 0.18% | -45.26% | 6% | 30.79% | -1.6% | +| | 50% | -0.38% | 0.14% | -1.62% | -0.04% | -4.85% | 0.29% | +| UL average-UPT gain for layer-2 | Mean | 14.78% | -24.77% | 69.69% | -62.81% | 108.34% | -79.75% | +| | 5% | 51.86% | -40.62% | 367.86% | -100% | 69134.24% | -100% | +| | 50% | 10.25% | -27.62% | 75.29% | -65.55% | 106.92% | -89.91% | + +Note: In evaluation of Source 2 ([26]), FR1 2-layer Scenario B is assumed. + +**Table 8.3.5B.3-5: Different UL power control parameters vs. Same UL power control parameters (Small Packet Size (4Kbytes for DL and 1Kbyte for UL), -40/-70dBm P0)** + +| | | Low load | | Medium load | | High load | | +|----------------------------------------|-------------|------------------------|-------------------|------------------------|-------------------|------------------------|-------------------| +| | | Source 2 ([26]) | | Source 2 ([26]) | | Source 2 ([26]) | | +| | | -40 dBm P0 | -70 dBm P0 | -40 dBm P0 | -70 dBm P0 | -40 dBm P0 | -70 dBm P0 | +| DL average-UPT gain for layer-1 | Mean | -0.06% | 0.04% | -3.72% | -0.53% | -5.41% | 0.28% | +| | 5% | -0.01% | 0% | -83.63% | -1.13% | -100% | 48.24% | +| | 50% | -0.03% | -0.02% | -0.22% | 0.01% | -0.14% | 0.09% | +| DL average-UPT gain for layer-2 | Mean | 0.05% | -0.02% | -0.93% | 0.01% | -0.88% | 0.07% | +| | 5% | 0.2% | 0.3% | -3.81% | -2.82% | -5.06% | 3.22% | +| | 50% | 0.13% | 0.09% | -0.6% | 0.16% | -0.77% | -0.08% | +| UL average-UPT gain for layer-1 | Mean | -0.21% | -0.14% | -0.7% | -0.18% | -1.77% | -0.11% | +| | 5% | -0.33% | -0.19% | -9.6% | -4.69% | -61.5% | -1.72% | +| | 50% | -0.31% | -0.28% | -0.31% | -0.01% | -0.35% | 0.05% | +| UL average-UPT gain for layer-2 | Mean | 0.83% | -5.39% | 9.13% | -61% | 14.62% | -70.12% | +| | 5% | 0.43% | -45.45% | 56.67% | -100% | 22136.34% | -100% | +| | 50% | -0.15% | -1.02% | 2.51% | -76.48% | 8.34% | -99.92% | + +Note: In evaluation of Source 2 ([26]), FR1 2-layer Scenario B is assumed. + +### **Summary of observations** + +For the following observations, UPT gain in the range of {-5%, 5%} is considered as similar UPT. + +For the 1st proposed scheme (i.e., UE Tx power optimization) compared to dynamic TDD baseline operation: + +(1) FR1 2-layer Scenario B scenario + +In case of large packet size, based on results from 1 source, + +- UE Tx power optimization has similar or lower mean and 5% DL Average-UPT for all load levels, except higher 5% DL Average-UPT for high load level +- UE Tx power optimization has higher mean and 5% UL Average-UPT for all load levels. + +For the 2nd proposed scheme (i.e., Different UL power control parameters) to same UL power control parameters: + +## (1) FR1 Indoor office scenario + +In case of large packet size, based on results from 1 source, + +- Different UL power control parameters has lower or similar mean and 5% DL Average-UPT for all load levels in case of higher UE Tx power. +- Different UL power control parameters has higher mean and 5% UL Average-UPT for all load levels in case of higher UE Tx power. +- But, +- Different UL power control parameters has higher or similar mean and 5% DL Average-UPT for all load levels in case of lower UE Tx power. +- Different UL power control parameters has lower or similar mean and 5% UL Average-UPT for all load levels in case of lower UE Tx power. + +In case of small packet size, based on results from 1 source, + +- Different UL power control parameters has similar mean and 5% DL Average-UPT for all load levels in case of higher UE Tx power. +- Different UL power control parameters has similar mean and 5% UL Average-UPT for low and medium load levels, higher mean and 5% UL Average-UPT for high load level in case of higher UE Tx power. +- But, +- Different UL power control parameters has similar mean and 5% DL Average-UPT for all load levels in case of lower UE Tx power. +- Different UL power control parameters has similar mean and 5% UL Average-UPT for low load level, and lower mean and 5% UL Average-UPT for medium and high load levels in case of lower UE Tx power. + +## (2) FR1 2-layer Scenario B scenario + +In case of large packet size, based on results from 1 source, + +- Different UL power control parameters has lower or similar mean and 5% DL Average-UPT for all load levels in case of higher UE Tx power. +- Different UL power control parameters has higher or similar mean and 5% UL Average-UPT for all load levels in case of higher UE Tx power. +- But, +- Different UL power control parameters has higher or similar mean and 5% DL Average-UPT for all load levels in case of lower UE Tx power. +- Different UL power control parameters has lower or similar mean and 5% UL Average-UPT for all load levels in case of lower UE Tx power. + +In case of small packet size, based on results from 1 source, + +- Different UL power control parameters has lower and similar mean and 5% DL Average-UPT for all load levels in case of higher UE Tx power. +- Different UL power control parameters has higher and similar mean and 5% UL Average-UPT for all load levels in case of higher UE Tx power. +- But, +- Different UL power control parameters has similar mean and 5% DL Average-UPT for all load levels in case of lower UE Tx power. +- Different UL power control parameters has lower and similar mean and 5% UL Average-UPT for all load levels in case of lower UE Tx power. + +### 8.3.5B.4 Specification impact of the proposed scheme + +- Source 1 ([24]) + - Indication of specific open loop power control parameters is supported since URLLC studies for dynamic grant scheduling. + - Other UL signals do not support such flexibility and specifications changes can be discussed +- Source 2 ([26]) + - Different UL power control mechanisms (both closed-loop and open-loop) for slots with CLI and without CLI. + +## 8.4 Inter-UE CLI handling schemes + +For study of potential enhancement to dynamic/flexible TDD and/or SBFD, followings are considered as candidates of potential enhancement method of UE-to-UE CLI handling, where further prioritization/down-scoping of candidate schemes for study can be done: + +- Potential enhancements to UE-to-UE CLI measurement/reporting +- Coordinated scheduling +- Spatial domain enhancements, +- Advanced Receiver +- UE and gNB transmission and reception timing +- Power control based solution +- Sensing based mechanism +- Note: Whether or not a particular scheme requires OTA or backhaul information exchange should be identified +- Note: Any other scheme(s) for UE-to-UE CLI handling is/are not precluded. +- Note: For potential enhancements to dynamic/flexible TDD and/or SBFD, utilize the outcome of discussion in Rel-15 and Rel-16 while avoiding the repetition of the same discussion. + +RAN1 deprioritized the discussion on sensing-based mechanism (i.e. LBT) and UE side advanced receiver for UE-to-UE co-channel CLI handling which can be specific for dynamic/flexible TDD and/or common for both SBFD and dynamic/flexible TDD. + +### 8.4.1 UE-to-UE co-channel CLI measurement and reporting + +#### 8.4.1.1 Description + +RAN1 studies the feasibility and potential benefit of UE-to-UE co-channel CLI measurement and reporting, which can be specific for dynamic/flexible TDD and/or common for both SBFD and dynamic/flexible TDD. At least followings are included: + +- Measurement resource/reporting configuration +- Measurement/reporting details (including UE processing delay) +- Relevant information exchange (between gNBs) if needed +- Usage of measurement at gNB + +For UE-to-UE co-channel CLI measurement, reusing existing channel(s)/signal(s)/measurement resource(s) is considered as baseline. For example, SRS resources defined in Rel-16 for SRS-RSRP measurement, CLI-RSSI resources defined in Rel-16 for CLI-RSSI measurement can be considered. + +For UE-to-UE co-channel CLI handling, L1/L2 based UE-to-UE CLI measurement and reporting is studied: + +- Note: Accounting for UE processing/reporting delay – companies are encouraged to share their assumptions +- Note: Proponents are encouraged to provide the mechanism of L1/L2 based CLI measurement and reporting, and to provide the benefits of L1/L2 based CLI measurement and reporting compared with existing L3 CLI/CSI measurement and report with evaluation result +- Note: Accounting for information exchange delay between gNBs (if applicable) + +For the purpose of UE-to-UE CLI mitigation, the following potential enhancements are considered: + +- For L1/L2 UE-to-UE CLI reporting, periodic, semi-persistent, aperiodic or event triggered reporting. +- For L1/L2 UE-to-UE CLI measurement, periodic, semi-persistent, or aperiodic measurement resource. + +For L1/L2 based UE-to-UE CLI measurement, SRS-RSRP and CLI-RSSI are to be further studied as baseline metrics. + +For the study of L1/L2 based UE-to-UE co-channel CLI measurement, measurement resource for CLI-RSSI measurement as defined in Rel-16 and SRS resource for SRS-RSRP measurement as defined in Rel-16 can be considered. Enhancement of measurement resource can be studied. + +For L1/L2 based UE-to-UE co-channel CLI measurement and reporting mechanism, the following measurement and report framework are studied. + +- Use existing CSI framework as the baseline. +- Others are not precluded. + +#### 8.4.1.2 Performance evaluation or analysis + +From the study of UE-to-UE co-channel CLI measurement and reporting, followings are observed: + +- The L1/L2 based UE-to-UE CLI measurement can be optimized for short term interference measurement +- The L1/L2 based UE-to-UE CLI measurement can be optimized for low latency +- The L1/L2 based UE-to-UE CLI measurement and reporting can facilitate gNB adjusting UE scheduling for inter-UE CLI reduction + +Above does not imply that L3 based measurement and reporting cannot be used for similar purposes. + +#### 8.4.1.3 Specification impact + +The potential specification impact to support enhancements to inter-UE CLI measurement resources and reporting: + +- For L1/L2 UE-to-UE CLI reporting, periodic and/or semi-persistent and/or aperiodic reporting. +- For L1/L2 UE-to-UE CLI measurement, periodic and/or semi-persistent and/or aperiodic measurement resource. + +### 8.4.2 Coordinated scheduling for time/frequency resources between gNBs + +#### 8.4.2.1 Description + +RAN1 studies the feasibility and potential benefits of coordinated scheduling for time/frequency resources between gNBs (if needed) for UE-to-UE co-channel CLI handling, which can be specific for dynamic/flexible TDD and/or common for both SBFD and dynamic/flexible TDD. In the study, at least followings are included: + +- Details of coordinated scheduling for time/frequency resources +- Relevant information exchange (if needed) + +#### 8.4.2.2 Performance evaluation or analysis + +The knowledge among gNBs of semi-static SBFD time and frequency configuration can be beneficial depending on gNB implementation. + +#### 8.4.2.3 Specification impact + +For CLI handling based on coordinated scheduling for time/frequency resource, RAN1 discussed potential exchange of information among gNBs on intended TDD UL-DL configuration, SBFD time/frequency configuration. + +### 8.4.3 Spatial domain coordination method + +#### 8.4.3.1 Description + +RAN1 studies the feasibility and potential benefit of UE-to-UE co-channel CLI handling based on spatial domain coordination method, which can be specific for dynamic/flexible TDD and/or common for both SBFD and dynamic/flexible TDD. In the study, at least followings are included: + +- Details for spatial domain coordination by gNB +- Relevant information exchange (if needed) + +Note: Study can include method for FR1 and FR2. + +#### 8.4.3.2 Performance evaluation or analysis + +RAN1 studied coordinating the transmissions of aggressor UEs and the reception of victim UEs in the spatial domain. + +This may require victim UE to measure CLI with different Rx beams for different Tx beams from aggressor UE. The performance impact is not evaluated in RAN1. + +Implementing spatial domain coordination for UE-to-UE CLI may increase measurement complexity. The effectiveness of the coordination method can vary based on user mobility and channel variation. + +### 8.4.4 UE and gNB transmission and reception timing + +#### 8.4.4.1 Description + +For UE-to-UE co-channel CLI measurement, RAN1 studies the impact on system performance because of CLI measurement inaccuracy at victim UE due to misalignment between DL reception timing at victim UE of DL channel/signal transmitted from serving gNB and DL reception timing at victim UE of CLI measurement resource transmitted from aggressor UE(s). + +### 8.4.5 Power control based solution + +#### 8.4.5.1 Description + +For UE-to-UE co-channel CLI handling, it is studied whether/how to enhance UL power control mechanism. In the study, existing UL power control mechanism is assumed as baseline. + +#### 8.4.5.2 Performance evaluation or analysis + +UE Tx power adjustment based UE-to-UE CLI handling was studied. The performance evaluation for UE Tx power adjustment is provided in section 8.3.5B.3. + +#### 8.4.5.3 Specification impact + +The specification impact of UE Tx power adjustment is summarized in section 8.3.5B.4. + +--- + +## 9 Implementation feasibility of SBFD + +### 9.1 Background for analysis + +In an SBFD-capable BS, the receiver in the uplink sub-band potentially experiences interference from multiple sources. In the study these sources include: + +- The base stations own transmitter transmitting in the downlink sub-bands; + +- Other sectors transmitting in the downlink sub-bands; +- Other base stations of the same operator transmitting in the downlink sub-bands; +- Other operators base stations transmitting on other carriers within the same band. + +Throughout the study, it is assumed that all other sectors and other base stations belonging to the same operator do not transmit in the uplink sub-band during SBFD slots, that is, that SBFD is deployed in all sectors and sites and the SBFD configuration is the same in all sectors and sites. The case where SBFD is not deployed at all sites or SBFD configurations could differ has not been examined as part of the study. + +Self-interference has been assessed using a framework named as “Residual Self Interference Calculation”, RSIC in a table. It is important to take into account that although the table is a useful and convenient means to break down the analysis of self-interference mitigation steps for the purposes of proposing an overall self-interference mitigation solution, the table should be interpreted with care. The individual components in the table are not independent of one another and are not independent of the total TX power level and RX parameters. Although the table expresses the interference suppression as a dB value, the dB interference suppression would change for other TX power or RX parameters. Thus, the values in the table should not be seen as a generic approach to scaling interference, but rather as a breakdown of how the SBFD may operate under a certain set of assumptions that is used to visualize how the analysis of feasibility has been worked out. + +Furthermore, the overall impact of analogue components is considered rather than the behavior of each individual transmitter/receiver. Due to production variations between radios and deviations in the exact level of isolation between TX and RX some transceivers may perform better and others worse in reality. The RSIC table should be seen as an overall example of the distribution of interference mitigation performances, but not an exact calculation based on individual transmitter/receivers. + +An obvious baseline for assessing the radio performance is a transmitter / receiver performance that just meets RAN4 minimum requirements. However, it is to be expected that to a reasonable extent the performance could be extended beyond the minimum needed for meeting for 3GPP requirements and thus examples are provided considering both the baseline and some improvement. The associated complexity of improvement should be considered. + +It is important to note that the antenna isolation can vary depending on the beam direction although this variation with beam direction may reduce after beam nulling is applied. In some companies’ input, worst case is considered. Meanwhile some figures presented in the tables from other companies are “typical”. For “good” beam directions, the residual interference may be reduced. However, there may be other beam steering directions for which the power may greater than used in these estimates. Individual RSIC descriptions capture the extent of expected variation with beam direction. + +The impact of and ability to suppress inter-sector interference is captured in a similar manner to the self-interference cancellation with a table termed the co-channel co-site inter-sector interference table. The same considerations apply to the table for inter-sector interference as for the self-interference table. + +The impact of interference between different gNBs on the same SBFD carrier at other sites is not considered as part of the RAN4 study on feasibility, because the relevant analysis highly depends on the practical network deployment. However, RAN4 have advised RAN1 on how to consider inter-subband leakage and the receiver blocking model and RAN1 then consider the impact of such interference as a performance issue, on which the relevant conclusion has been captured. + +The impact of interference from other operators may be considered by RAN1 in the performance assessment and is considered by RAN4 as part of the co-existence study. + +The downlink sub-band transmissions can impact the performance in the uplink sub-bands by two basic mechanisms: + +- Unwanted emissions from the downlink sub-bands occur at frequencies corresponding to the uplink sub-band and cause interference. The impacts of such effects are described qualitatively below and assessed quantitatively in subsequent sections. +- A high downlink power from the downlink sub-bands passing through the uplink receiver can induce interference in the uplink sub-band due to non-linearities in the RF. The impacts of such effects are described qualitatively below and assessed quantitatively in subsequent sections. + +When considering the RSIC for self-interference and inter-sector interference, the following aspects and self-interference mitigation techniques have been considered: + +## **Antenna isolation** + +For self-interference suppression, isolation between the transmitter and receiver antennas can be used to reduce both the transmitter leakage power transferred to the uplink sub-band and the power level of the TX sub-band signals that must be handled by the receiver. The antenna isolation may be impacted by the beamforming applied at both the transmitter and receiver. + +Physical distance between the transmitter and receiver sub-arrays produces isolation. The isolation can be significantly increased by means of isolation structures, isolating materials and/or RF chokes. + +The antenna isolation needs to be achieved over at least a bandwidth covering all of the carriers that the basestation transmits. Since BS hardware is generally built with the ability to configure or re-configure carriers within the 3GPP band(s) or sub-band(s) covered by the BS, and only applies analogue filtering to suppress the transmitter outside of the band(s) then the isolation may need to be achieved between a TX carrier or sub-band anywhere within the 3GPP (sub-)band(s) transmitted by the BS and the UL sub-band. + +Inter-sector interference occurs due to propagation of side/grating lobes and backlobes between sectors. The positioning of sectors is likely to be limited by site constraints. Potentially inter-sector isolation may be increased by increasing physical distance between sectors or by means of adding isolation materials (which may depend on factors such as weight, wind-load, weather resistance etc.). + +## **TX beam nulling** + +SBFD assumes an AAS array at the BS with a large antenna array. The degrees of freedom available from the array can be used for steering transmitter nulls towards the receive sub-panel, such that the transmitter leakage to the receiver is reduced. A possible cost of applying TX beam nulling is that the EIRP towards downlink users is reduced, and that downlink MIMO performance may be impacted. The RSIC analysis provides details of additional isolation achieved and the downlink impact of the TX beam nulling. + +## **Suppression of transmitter leakage (frequency isolation)** + +The unwanted emissions from the transmitter that fall into the receiver sub-band arise from the spectral widening of the OFDM signal and from intermodulation products in the transmitter RF. Spectrum widening of the OFDM signal can be managed by means of digital filtering. Non-linearity in the transmitter RF chain is typically mitigated by techniques including Crest Factor Reduction (CFR) and Digital Pre-Distortion (DPD). Using these techniques, the interference in the UL sub-band due to transmitter leakage can be suppressed. The amount of suppression is captured in the RSIC tables. + +## **Analogue interference cancellation** + +Analogue interference cancellation refers to techniques that involve capture of the transmitted signal in the downlink (including both the DL sub-bands and potentially also the leakage signal to the UL sub-band at the transmitter) and feedback to and removal from the received signal. This can involve both cancellation of the leakage signal in the UL sub-band and removal of the signal in the downlink sub-band in order to reduce the total power entering the analogue receive chain. + +The analogue cancellation theoretically requires feedback from every transmitter to every receiver, although techniques have been proposed that reduce the number of TX-RX paths that need to be implemented. The feedback needs to take into account the coupling between the TX and RX (S parameters), any filtering or other processing that take place in between the TX capture and RX cancellation points and any impact of scattering or reflections from the environment around the base station. + +## **Digital interference cancellation** + +Digital interference cancellation refers to the use of digital processing to remove interference in the uplink sub-bands. Digital processing can refer to several different techniques. One technique is to capture and sample the leakage from the transmitter in order to subtract the leakage signal in the digital domain at the receiver. In this case, the impact of coupling within the array, receiver RF and scattering / reflection needs to be modelled in the cancellation signal. The complexity of such cancellation depends on the number of transmitters and number of receivers. Digital cancellation of this type can attenuate transmitter interference but cannot reduce the magnitude of the TX signal entering the receiver RF analogue front end. + +Another type of digital processing is the use of the receiver equalization and combining to mitigate interference due to the transmitter, potentially including the leakage signal and non-linearities created within the receiver. A channel + +estimate is needed for the wanted received signal. For the interference components, it may be possible to estimate the characteristics of the coupling and distortions between transmitter and receiver. Alternatively, co-variance estimations of the interference can be used in the receiver equalization processing. The receiver algorithm should aim to maximize SINR at the receiver. + +### **Receive beamforming** + +The receiver beamforming can be used to steer nulls towards sources of interference, such as the transmitter or other sectors. The process of receiver beamforming is implicitly captured in the receiver MMSE combining as described above. The receiver combining will aim to maximize RX SINR by means of optimizing the beamforming gain towards the wanted signal and rejection towards interferers. + +### **Receiver linearity performance** + +The receiver analogue chain contains RF imperfections. For a large input signal, the receive chain may be driven towards compression and create intermodulation products. The self-interference signal from the transmitter (and other nearby sectors) is a high-power signal that enters the receiver and can cause such effects. + +Several approaches may be considered to mitigate the impact of receiver non-linearity, each of which will have trade-offs. One possibility is to use components, in particular LNAs with an increased linearity. This will mitigate receiver non-linearity behaviors at a cost of some increase in energy consumption and potentially size. A second possibility is to use automatic gain control to reduce the receiver gain and hence the magnitude of the received signals. Reduction of gain will increase the receiver noise figure, and so careful consideration is needed on the balance between mitigating RX interference and increasing the noise figure (which decreases coverage). + +A further possibility is the use of filtering before or within the RF front end. Filtering prior to the LNA or in the first stages of the receiver chain that filters out the downlink power from the transmitter can reduce interference. There may be drawbacks from filtering such as filter insertion loss, which can increase noise figure. The need to be specifically tuned to the RF frequency of the UL sub-band and impacts to size and integration. More analysis of filtering solutions is provided in the feasibility sub-sections. Filtering further down the chain, such as between LNA stages has less impact on noise figure but requires early stages of the RX chain to have high linearity. + +The RSIC tables present estimates of linearity performance considering the advantages and disadvantages of mitigation approaches. + +### **Phase noise** + +Phase noise in the receiver can lead to interference. Reciprocal mixing of receiver phase noise on a high-power signal in the DL sub-band can cause interference into an UL sub-band. In general, phase noise is not a significant contributor to cause interference into an UL sub-band unless phase noise is high and the DL signal is received at very high power + +### **Other considerations** + +Another factor that can impact the self- and inter-sector interference suppression can be the dynamic range of the ADC in the receiver. The dynamic range of the ADC needs to be sufficient to accommodate both the TX signal in the DL sub-band and the lower power RX signal in the UL sub-band. It is generally straightforward to reduce the signal power in the TX sub-band by means of filtering at an intermediate frequency immediately prior to the ADC and so ADC dynamic range is not seen as a problem. (A more advanced solution could be needed for direct conversion receiver architectures). + +## **9.2 Feasibility of FR1 wide area BS aspects** + +### **9.2.1 Self-interference analysis** + +#### **9.2.1.1 Summary table for self-interference analysis** + +Based upon RAN4 agreements, the RSIC capability is broken down into four aspects: (1) spatial isolation; (2) frequency isolation; (3) beam nulling/isolation and (4) digital IC. Accordingly, based upon the inputs from companies, the ranges for values of (1)-(4) are summarized in reply LS [46]; however, the detailed ranges are the supersets of results provided from source companies which require further feasibility analysis. Therefore, RAN4 further carried out the study based on a more detailed self-interference analysis framework [47], which is used to capture inputs from companies. + +**Table 9.2.1.1-1: FR1 WA BS Self-interference Analysis Summary** + +| FR1 | | | Samsung | Samsung | Ericsson | Huawei | Huawei | Qualcomm | CATT | Nokia | +|-------------------------------------|---------------------------------------------------|----------------------------------------|-------------------------------------------------|-------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| BS class | | | Wide Area BS (subband filter-1) | Wide Area BS (subband filter-2) | Wide Area BS | Wide Area BS example 1 | Wide Area BS example 2 | Wide Area BS | Wide Area BS | Wide Area BS | +| BS TX Power = ① dBm | | | 49 dBm | 49 dBm | 53 dBm | 47 | 53 | 49 dBm | 49 | 54 | +| Component capability and parameters | Frequency isolation at TX | Frequency isolation capability = ② dBc | 45 dBc | 45 dBc | 45 dBc | 45 | 45 | 45 dBc | 45 | 45 dBc | +| | | Frequency isolation techniques used | DPD utilized | DPD utilized | Digital filtering, CFR, DPD | DPD | DPD | DPD | CFR, DPD | Digital filtering or windowing to clean UL sub-band; DPD to suppress PA distortion | +| | Spatial isolation | Spatial isolation capability = ③ dBc | 80 dBc | 80 dBc | 70 dB | 80 | 80 | 80 dBc | 70 | 65 dBc | +| | | Spatial isolation techniques used | TX/RX panel separation and RF barrier structure | TX/RX panel separation and RF barrier structure | A combination of spatial isolation, chokes, absorption, mushroom EBG.

70dB is indicative average; isolation varies from around 55dB to more than 80dB depending on beam direction. | Spatial separation between TX/RX panel with absorbing material and choke structure. | Spatial separation between TX panel with absorbing material and choke structure. | Two separate panels with added electromagnetic spatial duplexer for additional cancellation | TX/RX panel separation, isolation structures, isolation material, cross polarization | Spatial separation between TX/RX panels; EM shielding structures between TX/RX panels

65dB is indicative average; isolation varies from around 53 dB to 73dB depending on beam direction.. | +| | TX Beam nulling /isolation in TX sub-band = ④ dBc | | 10 dBc | 10 dBc | 10 dBc

TX beam nulling reduces the variation with beam direction, and hence spatial | 10 | 10 | 15 dBc | 10 | 12 dBc | + +| | | | | | | | | | | +|------------------------------------|------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|--------------------------|-----------------------------------------------------------|-------------------------------------------------------------------------------------|--------------------------------------------------|---------------------------------------------------| +| | | | | isolation + TX nulling can be around 80dB for most directions. | | | | | | +| | DL EIRP impact due to beam nulling in TX sub-band | Limited, ~0dB | Limited, ~0dB | Up to 1-5dB EIRP loss, depending on beam direction | Less than 0.5 dB loss | Less than 0.5 dB loss | | | 0.8 dB maximum | +| | Self-interference leakage in gNB RX subband due to non-ideal TX, measured at RX ant. (Note 1) | -86 dBm
Note: provided by ①-②-③-⑨ dBm | -86 dBm
Note: provided by ①-②-③-⑨ dBm | -72 dBm | -94 | -88 | -91 dBm
(=①-②-③-④) | -89.01
①-②-③-⑨-⑦-10*log 10 (40/20) | -62 dBm/20 MHz | +| RF IC and other tech. (before LNA) | RF IC capability and other tech. in TX sub-band = ⑤ dBc | 15 dBc | 11.8 dBc | 0 dBc | N/A | 10 | | 0 | 0 dBc | +| | RF IC capability and other tech. in RX sub-band = ⑧ dBc | 0dBc | 0dBc | 0 dBc | N/A | N/A | | 0 | 0 dBc | +| | RF IC techniques and other tech. (before LNA) | subband filtering (20MHz passband, 2* 5PRB transition band used for roll-off between passband/stopband) | subband filtering (24.8MHz passband, 2*3.8MHz transition band used for roll-off between passband/stopband) | None; see section 9.2.1.2.2 for analysis. | N/A | Analog filter is put after LNA | | | None apply due to feasibility concerns | +| | Impacts to RX sensitivity (due to e.g. insertion losses) due to RF IC or other techniques before LNA | Limited | Limited | N/A | N/A | | | 0 | N/A dBc | +| | Self-Interference signal in gNB TX subband, measured at the input of LNA (Note 1) | -56 dBm
Note: provided by ①-③-④-⑤dBm | -52.8 dBm
Note: provided by ①-③-④-⑤dBm | -27 dBm | -43 | -37 | | -31
Rx is blocked
①-③-④-⑤ | -23 dBm with some variations depending on TX beam | +| Blocker Suppression at RX | Frequency isolation capability ⑥ dBc | 40 dBc | 40 dBc | 0 dBc | digital filter: 60-80 dB | sub-band analog filter: 10 dB
digital filter: 60-80 dB | 15 dBc | 65 | 0 dBc | +| | Frequency isolation techniques | Filtering | Filtering | The receiver is in high non-linearity; no possibility for interference mitigation | digital filtering | sub-band analog filter and digital filtering | Filtering (does not protect most of the receiver. Right in front of the ADC, by the | Digital filter for ACS | None apply due to feasibility concerns | + +| | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------|--|------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|-------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------| +| | | | | | as part of the digital receive combining algorithms. | | | time blocker is there, damage already has been done). | | | +| RX IMD | | Rx IIP3 capability (dBm) | With subband filtering, RX non-linearity impact is neglectable | With subband filtering, RX non-linearity impact is neglectable | -32dBm (Minimum for RAN4 requirement)
-22dBm (Realistic for AAS)
-10dBm (optimistic for AAS) | -10 | 0 | Not a significant contributor on the gNB Rx capability. | -10 | -10 dBm at maximum sensitivity;
+10 dBm at maximum linearity (at NF penalty) | +| | | Rx IM3 contribution (dBm) | | | Even without ADC overload:
-17 dBm (RAN4 minimum receiver)
-37 dBm (Realistic)
-61 dBm (Optimistic) | -109 | -121 | | -73
$(\textcircled{1}-\textcircled{3}-\textcircled{4}-\textcircled{5})-2*(\text{IIP3}-(\textcircled{1}-\textcircled{3}-\textcircled{4}-\textcircled{5}))$ | Negligible (at NF penalty) | +| Other RX | | Any other RX impacts if significant (e.g. ADC noise, phase noise etc.) | N/A | N/A | ADC overload can be mitigated with filtering prior to ADC except for direct conversion architectures. | ADC noise: -109
reciprocal phase noise mixing:-112 | ADC noise: -113
reciprocal phase noise mixing:-116 | Noise figure can be modeled as a function of total input power (signal + jammer) with a piecewise linear model. | -116 | Negligible | +| Self-Interference signal in gNB RX subband caused by non-ideal RX selectivity, gain-normalized (Note 1, 2) | | | -96 dBm
Note: provided by $\textcircled{1}-\textcircled{3}-\textcircled{4}-\textcircled{5}-\textcircled{6}$ dBm | -92.8 dBm
Note: provided by $\textcircled{1}-\textcircled{3}-\textcircled{4}-\textcircled{5}-\textcircled{6}$ dBm | Receiver in high non-linearity | -105 | -111 | | -96
$\textcircled{1}-\textcircled{3}-\textcircled{4}-\textcircled{5}-\textcircled{6}$ | -73 dBm/20MHz (at 50 dBc ACS) | +| RX Beam nulling /isolation in RX sub-band = $\textcircled{9}$ dBc | | | 10 dBc | 10 dBc | RX processing does not mitigate analogue non-linearity | 10 | 10 | | 10 | 0 dBc | +| RX sensitivity degradation caused by RX beam nulling | | | Limited, ~0dB | Limited, ~0dB | Receiver saturated | Less than 0.5 dB loss | Less than 0.5 dB loss | | | 0 dBc; should not assume further UL beamforming loss to maintain | + +| | | | | | | | | | | +|----------------------------------------------------------------------|--|------------------|------------------|--------------------------------------------------------------------------------------------------------------------------------------|---------------------|---------------------|-----------------------------------|----------|----------------------| +| | | | | | | | | | any UL gains | +| Digital IC = ⑦ dBc | | 20 dBc | 20 dBc | Digital IC not possible due to receiver non-linearity and would anyhow be highly complex due to large number of TX/RX for wide area. | 15 | 15 | 15 dB | 10 | 0 dBc | +| Overall RSIC capability (Note 1) | | 154.6 dBc | 154.2 dBc | Transmitter: 125 dB
Receiver: N/A due to receiver saturation | -150.6 | -155.3 | 155 dB
(②+③+④+⑦) | 121.86 | 122 dBc | +| Noise floor ⑩dBm | | -96dBm/20MHz | -96dBm/20MHz | -96 dBm/CBW | -96 dBm/20 MHz | -96 dBm/20 MHz | -96 dBm/20 MHz @ 5dB noise figure | -95.99 | -96 dBm/CBW (20 MHz) | +| Residual Interference budget with 1 dB desens target (⑪dBm=⑩dBm-6dB) | | -102 dBm | -102 dBm | -102 dBm | -102 dBm | -102 dBm | -102 dBm | -101.99 | -102 dBm | +| Required RSIC budget (①-⑪dBc) | | 151 dBc | 151 dBc | 155 dBc | 149 | 155 | 151 dBc | 150.99 | 156 dBc | +| SBFD configuration | | DUD(40-20-40MHz) | DUD(40-20-40MHz) | 40-20-40 MHz | DUD [40, 20, 40] | DUD [40, 20, 40] | DUD | 40-20-40 | DUD (40/20/40 MHz) | +| Guardband assumption (if exist) | | 5 PRB | 5 PRB | 5 PRB. | Existing SU | Existing SU | 5 PRBs | | 5 RB (1.8 MHz) | +| bandwidth over which suppression is achieved | | 100MHz | 100MHz | >300 MHz | Several hundred MHz | Several hundred MHz | 100MHz | | | +| Others | | | | | | | | | | + +## 9.2.1.2 Feasibility study on self-interference + +### 9.2.1.2.1 Samsung + +When SBFD is implemented at the gNB, the received UL signal at the gNB is subject to co-channel self-interference from the gNB side transmitter. Methods to cancel the self-interference include passive methods which rely on the antenna isolation between Tx and Rx antennas, active methods which utilize RF or digital signal processing, hybrid methods using a combination of these, and filtering. + +Achieving a sufficient level of residual self-interference suppression and cancellation is the most critical part when implementing SBFD at the gNB. Without adequate SIC capability, the interference from the transmitted DL signal would corrupt the received UL signal as illustrated in Figure 9.2.1.2.1-1 (a). To solve this problem, various SIC schemes can be used. Using the example of Figure 9.2.1.2.1-1 (b), SIC capability can be provided through the antenna or panel design (A), can be applied in RF domain to the RF signal (B) or in digital signal domain (C), or a combination of these. + +![Figure 9.2.1.2.1-1: gNB transceiver architecture with self-interference cancellation capability. (a) Typical TDD RF front-end: Shows multiple ports (Port #1 to Port #N) connected to a central antenna panel. Each port has a Power Amplifier (PA) for transmission and a Low Noise Amplifier (LNA) for reception. Arrows indicate signal flow from PAs to the antenna and from the antenna to LNAs. A dashed line labeled 'Internal coupling' shows interference from the transmit path to the receive path. (b) Self-interference cancelling capability: Shows the same architecture as (a) but adds three cancellation blocks: (A) Antenna/Panel design, (B) RF domain cancellation, and (C) Digital domain cancellation. These blocks are shown intercepting the interference path before it reaches the LNAs, resulting in a cleaner 'UL signal' output.](0d9149a10167a487a93c349f5d848b7d_img.jpg) + +Figure 9.2.1.2.1-1: gNB transceiver architecture with self-interference cancellation capability. (a) Typical TDD RF front-end: Shows multiple ports (Port #1 to Port #N) connected to a central antenna panel. Each port has a Power Amplifier (PA) for transmission and a Low Noise Amplifier (LNA) for reception. Arrows indicate signal flow from PAs to the antenna and from the antenna to LNAs. A dashed line labeled 'Internal coupling' shows interference from the transmit path to the receive path. (b) Self-interference cancelling capability: Shows the same architecture as (a) but adds three cancellation blocks: (A) Antenna/Panel design, (B) RF domain cancellation, and (C) Digital domain cancellation. These blocks are shown intercepting the interference path before it reaches the LNAs, resulting in a cleaner 'UL signal' output. + +**Figure 9.2.1.2.1-1: gNB transceiver architecture with self-interference cancellation capability** + +For example, antenna SIC can be used to minimize the leakage power from the Tx ports to the Rx ports of the panel, and digital SIC is then used to handle any residual interference after antenna SIC. DL out-band signal power flowing into the UL Rx path can be effectively suppressed below the noise floor level to guarantee the UL receiver performance. Also, by combining digital pre-distortion (DPD) at the Tx path and digital SIC at the Rx path, the out-band interference from the DL signal to the UL signal can be effectively mitigated by the gNB such that the need for a guard band between the UL and DL signals is minimized. + +#### Spatial Isolation by Antenna Design + +In the analysis it's assumed separate panels for simultaneous downlink transmission and uplink reception as separate-TX/RX antenna array for evaluation of SBFD operation. The basic spatial isolation between RX and TX antenna panels can be achieved by directional isolation. + +Firstly, Tx/Rx isolation can be increased by increasing the spatial distance. Furthermore, an additional RF barrier structure could be useful to further improve Tx/Rx isolation performance, and using the RF barrier between the Tx and Rx panels could also affect the required spatial distance separating the Tx and Rx panels. A well-designed RF barrier can minimize the need for large spatial separation and mostly preserve the existing antenna form factor and enclosed volume comparable to legacy TDD. To design an efficient RF barrier, various electromagnetic resonator structures can be incorporated into the antenna design, e.g., wall(s), gap(s), or a combination of them. These result in surface wave nulling and can further block the undesired leakage signals from the Tx panel to the Rx panel. + +Figure 9.2.1.2.1-2 demonstrates the S21 measurement results with respect to the distance between upper and lower antenna panels in our FR1 3.5 GHz SBFD testbed. + +![Figure 9.2.1.2.1-2: FR1 testbed and SIC performance when varying distance between upper and lower panel. The figure consists of three parts: a photograph of the FR1 testbed on a rooftop, a schematic diagram of the upper and lower panels with an electromagnetic conjugated structure between them, and a line graph showing S21 (dB) vs. Distance (cm).](4faf621bddd7d6e9f24a27325de96015_img.jpg) + +The figure illustrates the FR1 testbed and its SIC performance. On the left is a photograph of the testbed setup on a rooftop. In the center is a schematic showing the 'Upper panel' and 'Lower panel' separated by an 'Electro-magnetic Conjugated structure' at a specific 'Distance'. On the right is a line graph plotting S21 (dB) against Distance (cm). + +| Distance (cm) | S21 (dB) | +|---------------|----------| +| 10 | 70 | +| 15 | 76 | +| 25 | 79 | +| 35 | 82 | +| 45 | 83 | +| 55 | 86 | +| 65 | 87 | + +Figure 9.2.1.2.1-2: FR1 testbed and SIC performance when varying distance between upper and lower panel. The figure consists of three parts: a photograph of the FR1 testbed on a rooftop, a schematic diagram of the upper and lower panels with an electromagnetic conjugated structure between them, and a line graph showing S21 (dB) vs. Distance (cm). + +**Figure 9.2.1.2.1-2: FR1 testbed and SIC performance when varying distance between upper and lower panel** + +While it can be expected that spatial isolation numbers vary depending on the form and particular layout configuration of antenna elements in the upper and lower panels, we have shown that >80 dB antenna isolation is possible between the Tx and Rx panels in FR1, with reasonable separation distance between upper and lower panel. + +An important design consideration for increased spatial isolation provided by the RF barrier is whether such stopband performance is stable over a wide enough frequency range. Electromagnetic (EM) isolators and resonant structures are designed around a specific center frequency, e.g., 3.5 GHz. Therefore, design of the resonant structure must account properly for the channel bandwidth and NR operating band under consideration to provide a sufficiently large stopband between Tx and Rx panel. Another consideration is that undesired Tx/Rx interference is created by multiple EM sources, e.g., antenna elements in the Tx panel. Therefore, diffusion of the corresponding surface waves is more challenging when isolating the Tx and Rx panel. Despite these challenges, our FR1 3.5 GHz testbed have achieved isolation performance that show almost uniform antenna and panel isolation performance with respect to frequency for the 100 MHz channel BW of the NR carrier in 3.5 GHz. + +According to the applied mechanisms and measurement results, the achievable level for TX and RX spatial isolation without impact on radiation pattern based on compact antenna size is around 80dB for FR1. + +### **TX and RX beam nulling/isolation** + +The effect of beam nulling for isolation depends on implementation and antenna array size. For both TX and RX panels, the large number of antenna elements for TX/RX beamforming can provide the ability to provide nulling to mitigate the self-interference by increasing the isolation. For FR1 up to 10dB isolation by beam nulling can be contributed to residual interference suppression. + +### **Frequency isolation at TX** + +For SBFD, in which the Tx signal and the Rx signal are respectively allocated to non-overlapping frequency-domain resources on the same time-domain symbol for simultaneous transmission and reception, at least the waveform roll-off therefore reduces the magnitude of the Tx-Rx interference to which the Rx signal is subjected. Additionally, BB filtering can be applied to further increase the achievable isolation. The use of frequency-domain isolation between the Tx and Rx signal allocations is primarily an approach that serves the purpose of reducing the amount of self-interference which must be further cancelled by a digital cancellation stage. + +In the case of gNB-side SBFD operation, the SBFD UL subband can be considered as out-of-channel with respect to the 1 or 2 SBFD DL subband(s). Undesired spectral leakage from the DL Tx signal in the gNB into the Rx path are reduced similar to the case of out-of-channel leakage, e.g., comparable to the gNB Tx-side Adjacent Channel Leakage Ratio (ACLR) for coexistence between two operators on adjacent channels in the same NR band. Note that ACLR is determined by the non-linear characteristics of the PA and corresponding RF requirements are set by RAN4, e.g., 45 dBc for the gNB Tx. + +While it can be assumed that the achievable Tx-to-Rx interference from the SBFD DL subband to the UL subband can only guarantee performance according to the less stringent in-channel RF requirements, our FR1 3.5 GHz testbed implementation shows that the use of digital pre-distortion (DPD) techniques to improve upon the non-linearity characteristics of the PA can achieve 45 dBc isolation between the SBFD DL and UL subbands. Figure 9.2.1.2.1-3 shows the achievable isolation in frequency domain for FR1 SFBD when Tx-to-Rx leakage is also compensated for by DPD based on the FR1 3.5 GHz testbed. + +![Figure 9.2.1.2.1-3: FR1 testbed and PSD for SBFD DL and UL SBs after antenna isolation and digital pre-distortion. The plot shows a Power Spectral Density (PSD) with a central UL signal and two DL leakage signals on either side. The UL signal is centered at 2.58 GHz with a power level around -85 dBm. The DL leakage signals are at approximately 2.56 GHz and 2.60 GHz with power levels around -40 dBm. The x-axis represents frequency from 2.56 GHz to 2.60 GHz, and the y-axis represents power density from -140 dBm to -40 dBm.](4b48a3fdfe130217b1ff29b9b0592a45_img.jpg) + +Figure 9.2.1.2.1-3: FR1 testbed and PSD for SBFD DL and UL SBs after antenna isolation and digital pre-distortion. The plot shows a Power Spectral Density (PSD) with a central UL signal and two DL leakage signals on either side. The UL signal is centered at 2.58 GHz with a power level around -85 dBm. The DL leakage signals are at approximately 2.56 GHz and 2.60 GHz with power levels around -40 dBm. The x-axis represents frequency from 2.56 GHz to 2.60 GHz, and the y-axis represents power density from -140 dBm to -40 dBm. + +**Figure 9.2.1.2.1-3: FR1 testbed and PSD for SBFD DL and UL SBs after antenna isolation and digital pre-distortion** + +**Frequency isolation at RX and RF SIC** + +Note that TDD gNB radio unit design must also account for ADC and LNA in the receiver path, e.g., to prevent Rx saturation or blocking by the spectral leakage created from the undesired Tx signal. To prevent ADC saturation in the Rx path of the gNB radio unit supporting SBFD, Rx filtering can be used to suppress the leakage from the Tx side interfering signal. Additional Rx filters can provide protection to avoid potential dynamic range and saturation issues for ADC or LNA when demodulating the UL subband in the Rx path of the gNB. Note that for RF filters with sharp roll-off's, the order of the filter must increase, and so must then the size of the filter. Additional insertion losses are incurred which negatively affect the link budget. + +High-Q value RF filter can provide enough attenuation towards high power level interference in the DL subband(s), not only for the self-interference but also other co-channel interference sources from co-site inter-sector and inter-site gNBs. As illustrated in the below figure, for RF direct-sampling receiver (which shall be regarded as the receiver architecture more difficult to implement subband filter compared to super heterodyne and homodyne/zero-IF receivers) to have the RF subband filter be located between the two-stage cascaded LNAs, the normal design is to have the UL subband as passband and reserve a few number of PRBs (e.g., 5PRB assumed) for transition band(s) to allow a certain suppression to filter out interference signals over DL subband(s). + +![Figure 9.2.1.2.1-4: Improved direct-RF sampling receiver with subband filtering between the two-stage cascaded LNAs. The top part is a block diagram showing the signal flow: Antenna -> Band Filter -> LNA -> Mixer -> Subband Filter -> Mixer -> LNA -> ADC -> Baseband Processing. The bottom part is a frequency response graph showing the UL Subband as the passband, flanked by Guard Bands and DL Subbands. The BS Channel Bandwidth is indicated.](4e953ed2839e2e77fd0c293cd76c3de9_img.jpg) + +Figure 9.2.1.2.1-4: Improved direct-RF sampling receiver with subband filtering between the two-stage cascaded LNAs. The top part is a block diagram showing the signal flow: Antenna -> Band Filter -> LNA -> Mixer -> Subband Filter -> Mixer -> LNA -> ADC -> Baseband Processing. The bottom part is a frequency response graph showing the UL Subband as the passband, flanked by Guard Bands and DL Subbands. The BS Channel Bandwidth is indicated. + +**Figure 9.2.1.2.1-4: Improved direct-RF sampling receiver with subband filtering between the two-stage cascaded LNAs** + +The key difficult is to design a high Q-value RF subband filter, which should also be restricted by the limited space in the integrated base station design. The RF filter performance for Q-values of 1500 and 5000 has been studied by using RF simulation tool as provided as below, by providing the transmission S21 and reflection S11 goal for the targeted 20MHz passband, 20dB return loss, stopband and 25dB attenuation. + +![Two side-by-side plots showing analog filter performance for Q=1500 (left) and Q=5000 (right). Both plots show Attenuation [dB] vs Frequency [MHz] from 3460 to 3540 MHz. The left plot for Q=1500 shows a passband from 3490 to 3510 MHz with a return loss of 20.0 dB. The right plot for Q=5000 shows a similar passband but with sharper transitions and deeper stopband ripples. Both plots include a legend for S21 Synthesis, S11 Synthesis, S21 Goal, and S11 Goal. The right plot also includes a matrix showing S parameters: S11 = 1.018998878, S21 = 0.0, S31 = 0.0, S41 = 0.0, and S51 = 0.0.](989009560da743352b1416921a20e624_img.jpg) + +Two side-by-side plots showing analog filter performance for Q=1500 (left) and Q=5000 (right). Both plots show Attenuation [dB] vs Frequency [MHz] from 3460 to 3540 MHz. The left plot for Q=1500 shows a passband from 3490 to 3510 MHz with a return loss of 20.0 dB. The right plot for Q=5000 shows a similar passband but with sharper transitions and deeper stopband ripples. Both plots include a legend for S21 Synthesis, S11 Synthesis, S21 Goal, and S11 Goal. The right plot also includes a matrix showing S parameters: S11 = 1.018998878, S21 = 0.0, S31 = 0.0, S41 = 0.0, and S51 = 0.0. + +**Figure 9.2.1.2.1-5: Analog filter performance for Q=1500 (left) and 5000 (right), for 3.5GHz operating freq. and 20MHz passband** + +The feasibility of high Q-value RF subband filter with reasonable size/weight to be integrated into current gNB implementation has been challenged by some companies in previous RAN4 meetings. On the other hand, it should be noted that some novel designs are recently proposed, which could be based on some new structure for ceramic dielectric filter to have very good RF filtering performance as requested, and there are some preliminary results simulated by HFSS, which are based on the ceramic dielectric filter with the cascaded quadruplet structure dimensioned by 19.5mm\*19.5mm\*6mm illustrated in the below figure, that shall be regarded as reasonable small size/weight and feasible to be integrated in current gNB design. + +![A 3D CAD model of a ceramic dielectric filter structure. It shows a rectangular base with several cylindrical resonators of varying heights and diameters arranged in a specific pattern. A coordinate system (X, Y, Z) is shown, with the Z-axis pointing upwards. A scale bar at the bottom indicates dimensions from 0 to 20 mm.](4f6c3a94eee3c535b8899f9806014d44_img.jpg) + +A 3D CAD model of a ceramic dielectric filter structure. It shows a rectangular base with several cylindrical resonators of varying heights and diameters arranged in a specific pattern. A coordinate system (X, Y, Z) is shown, with the Z-axis pointing upwards. A scale bar at the bottom indicates dimensions from 0 to 20 mm. + +**Figure 9.2.1.2.1-6: New cascaded quadruplet structure for ceramic dielectric filter** + +Furthermore, one alternative solution with relaxed Q-value subband filter but with more flexibility for subband configuration is also studied. As illustrated by the below figure, subband filter can still be implemented between the two-stage cascaded LNAs, and what different is the designed filter shall have a passband wider than the configured UL subband and the transition band could be much relaxed from 5PRB. For example, to support 20MHz UL subband, we can implement a subband filter easier to be implemented, e.g., {larger passband than 20MHz, more PRB for transition band} being considered. + +![Figure 9.2.1.2.1-7: Block diagram and frequency response plot for an alternative solution with relaxed Q-value subband filtering. The block diagram shows an antenna connected to a Band Filter, then an LNA, then a mixer. The mixer has a local oscillator input and a 'Relaxed Q-value Subband Filter' input. The output of the mixer goes to another LNA, then an ADC, and finally to Baseband Processing. The frequency response plot shows a passband (red curve) that is wider than the UL Subband, allowing some DL Subband signals to pass through. The BS Channel Bandwidth is indicated by a double-headed arrow.](bdee2715697a4142d16a360549fa7c7f_img.jpg) + +The diagram illustrates a radio receiver chain. An antenna is connected to a Band Filter, followed by an LNA. The signal then enters a mixer. One input of the mixer is a local oscillator, and the other is a 'Relaxed Q-value Subband Filter'. The output of the mixer is amplified by another LNA, converted to digital by an ADC, and then processed by Baseband Processing. Below the block diagram, a frequency response plot shows the passband (red curve) of the relaxed subband filter. The plot indicates the UL Subband, DL Subband, Guard Band, and the overall BS Channel Bandwidth. The passband is intentionally wider than the UL Subband to allow some DL interference to pass through, which is then handled in the digital domain. + +Figure 9.2.1.2.1-7: Block diagram and frequency response plot for an alternative solution with relaxed Q-value subband filtering. The block diagram shows an antenna connected to a Band Filter, then an LNA, then a mixer. The mixer has a local oscillator input and a 'Relaxed Q-value Subband Filter' input. The output of the mixer goes to another LNA, then an ADC, and finally to Baseband Processing. The frequency response plot shows a passband (red curve) that is wider than the UL Subband, allowing some DL Subband signals to pass through. The BS Channel Bandwidth is indicated by a double-headed arrow. + +**Figure 9.2.1.2.1-7: Alternative solution with relaxed Q-value subband filtering** + +With the above design, the motivation of introducing UL subband filter is to reduce DL interference level to avoid RX blocking, rather than to remove all DL interference signals, thus making the filtering passband to be equal to UL subband unnecessary. If the subband filter with larger passband could prevent RX blocking, the residual interference not filtered by the subband filter can be further handled by the operation in the digital domain, including digital filtering and digital interference cancellation. + +For instance, we designed the filter with <25MHz passband and <4MHz used for roll-off transition band between passband/stopband and 25dB suppression (better suppression performance, but still easier to be implemented because of larger transition bands). We would also like to use HFSS-based RF simulation to demonstrate the feasibility of this design. There are some numerical results of the well-designed advanced RF filter for which we evaluate the performance by HFSS-based RF simulation. The filter is also based on the ceramic dielectric filter with the cascaded quadruplet structure with the same dimension as previous filter design (i.e., 19.5mm\*19.5mm\*6mm) but different structure illustrated as the below figure, that shall also be regarded as reasonable small size/weight and feasible to be integrated in current gNB design. + +![Figure 9.2.1.2.1-8: 3D rendering of a new cascaded quadruplet structure for a ceramic dielectric filter. The image shows a green ceramic substrate with several circular resonators arranged in a specific pattern. A scale bar at the bottom indicates 0, 5, and 10 mm.](b06daabf0756b0c89478f311255358bc_img.jpg) + +The image shows a 3D perspective view of a ceramic dielectric filter. It consists of a rectangular green ceramic base with several circular resonators of different sizes arranged on its surface. The resonators are arranged in a cascaded quadruplet structure. A scale bar at the bottom indicates a length of 10 mm, with a midpoint at 5 mm. + +Figure 9.2.1.2.1-8: 3D rendering of a new cascaded quadruplet structure for a ceramic dielectric filter. The image shows a green ceramic substrate with several circular resonators arranged in a specific pattern. A scale bar at the bottom indicates 0, 5, and 10 mm. + +**Figure 9.2.1.2.1-8: New cascaded quadruplet structure for ceramic dielectric filter for filter design with 24.8MHz passband (intentionally larger than 20MHz UL subband)** + +![S Parameter Plot 1 showing the RF simulation results for a filter design. The plot displays the magnitude of the S-parameter (dB) versus frequency (GHz). The passband is centered around 3.50 GHz, with a width of approximately 24.8 MHz. The plot includes markers m1 through m6, indicating key points on the curve. The data points are as follows: m1 (3.5090, -0.4024), m2 (3.4888, 3.1671), m3 (3.5136, 3.0780), m4 (3.4850, -35.3594), m5 (3.5174, -26.0461), and m6 (3.4781, -24.8023).](5d88a496799eb6e06d3d697bf071b8f3_img.jpg) + +S Parameter Plot 1 showing the RF simulation results for a filter design. The plot displays the magnitude of the S-parameter (dB) versus frequency (GHz). The passband is centered around 3.50 GHz, with a width of approximately 24.8 MHz. The plot includes markers m1 through m6, indicating key points on the curve. The data points are as follows: m1 (3.5090, -0.4024), m2 (3.4888, 3.1671), m3 (3.5136, 3.0780), m4 (3.4850, -35.3594), m5 (3.5174, -26.0461), and m6 (3.4781, -24.8023). + +**Figure 9.2.1.2.1-9: RF simulation results for filter design with 24.8MHz passband (intentionally larger than 20MHz UL subband)** + +As demonstrated in the above figure, for this RF filter design, the passband (the point m2 to m3 in the above figure) is 24.8MHz, which is intentionally larger than 20MHz as UL subband bandwidth. Even by considering 25dB suppression, the transmission bands are less than 3.8MHz for both lower and higher frequency sides. + +We can assume the worst case that 4.8MHz DL interference signals (24.8MHz passband – 20MHz UL subband BW) are not filtered out at all, and the DL interference at 2x 3.8MHz transition bands is filtered out by -14dB (for the worst case estimation by separating 3.8MHz into several parts). Therefore, we can derive the residual self-interference signal in gNB RX subband (caused by non-ideal RX selectivity) gain-normalized = 49dBm - 80dB - 5dB - 11.8dB (subband filtering) - 40dB = -87.8dB, which is still 6.8dB smaller than the residual self-interference leakage in UL subband due to non-ideal TX. It should be noted that the equivalent suppression provided by subband filtering can be calculated as $10 \cdot \log_{10}((4.8\text{MHz}/80\text{MHz}) \cdot 10^{(0\text{dB}/10)} + (2 \cdot 3.8\text{MHz}/80\text{MHz}) \cdot 10^{(-14\text{dB}/10)} + (67.6\text{MHz}/80\text{MHz}) \cdot 10^{(-25\text{dB}/10)}) = -11.8\text{dB}$ . Therefore, with the alternative solution with the subband filtering having a larger passband than the configured UL subband and larger transition bands for roll-off, the RF filter will be easier to be designed. + +Additionally, analog filters such as IF and BB filters can be employed. For example, when the receiver is designed to use zero IF architecture, the receiver can use the lowpass filter to further remove the leakage signal after applying the mixer. By combining multiple LNAs, filter loss can be compensated more easily. + +### **Digital IC** + +As aforementioned theoretically, the digital IC should be with the capability to remove all remaining self-interference if the total level to be handled by ADC input is within its dynamic range. For 12bit ADC with assumption of 12dB PRPA signal, the dynamic range is >50dB. + +The desired received signal is mixed with the undesired DL leakage signal in the Rx path of the gNB radio, e.g., after ADC. The unwanted DL leakage signal must be removed by receiver processing using digital SIC. It is necessary to estimate the interference channel between the Tx panel and the Rx panel. Digital SIC performance is helped when synchronization to accurately remove the Tx signal from the Rx signal can be obtained. In principle, two methods exist to estimate the interference channel. One approach is to store information on a Tx signal that has passed through the PA with a feedback link and then estimate the interference channel over-the-air to remove the interference from the Rx signal. Another approach is to use only over-the-air estimation. Without a feedback link, the whole combined channel can still be estimated through the Rx panel. We used the first approach in the FR1 3.5 GHz testbed. + +### **9.2.1.2.2 Ericsson** + +The corresponding technique input in the summary Table 9.2.1.1-1 presents an overview of the self-interference mitigation potential for a wide area BS with 53 dBm transmit power. + +When considering the transmitter sub-band emissions that leak into the RX sub-band, the emissions are suppressed to a level of around -72dBm using transmitter and analog suppression techniques, which is around 24dB above the noise floor. In principle, digital techniques could to some extent be used to further suppress the TX interference, however the + +receiver is blocked. From the receiver perspective, the input power is too high and the receiver is blocked. A detailed description is provided in the summary table. + +The following are more detailed considerations of modelling and techniques captured in table 9.2.1.1-1. + +### **TX – RX isolation** + +Transmitter to receiver isolation is achieved by means of separating the transmit and receive panels. Spatial separation alone achieves in the order of 30-40 dB isolation. However, a number of techniques exist to significantly improve the TX-RX panel isolation including chokes, absorption, mushroom EBG etc. A detailed electromagnetic simulation of these techniques is presented in [67], which demonstrates that the isolation between a TX panel and RX sub-array varies depending on beam direction between 55 to 80dB. An example of the electromagnetic simulations is depicted in figure 9.2.1.2.2-1 and 9.2.1.2.2-2. The first figure visualizes the EM propagation between the sub-arrays, whereas the second figure indicates the TX panel to RX sub-array isolation for several TX beam steering directions. The simulations take into account an advanced suppression structure between the sub-arrays. + +![Figure 9.2.1.2.2-1: Full-wave averaged E-field magnitude on an XZ plane cut based on EM simulation. The image shows a color-coded field distribution with a color bar on the right ranging from -10 dB(V/m) to 30 dB(V/m). A coordinate system at the bottom right indicates the X and Z axes.](393809f56a51b00ce58ce3bc686803b9_img.jpg) + +Figure 9.2.1.2.2-1: Full-wave averaged E-field magnitude on an XZ plane cut based on EM simulation. The image shows a color-coded field distribution with a color bar on the right ranging from -10 dB(V/m) to 30 dB(V/m). A coordinate system at the bottom right indicates the X and Z axes. + +**Figure 9.2.1.2.2-1: Full-wave averaged E-field magnitude on an XZ plane cut based on EM simulation** + +![Figure 9.2.1.2.2-2: TX panel to RX sub-array coupling magnitude curves. The figure consists of six subplots arranged in a 2x3 grid. The top row shows co-polarized coupling magnitude [dB] vs Frequency [GHz] (3.50 to 4.50 GHz) for (a) 0 degree (boresight), (b) 15 degrees (TX steers main beam toward RX), and (c) -15 degrees (TX steers main beam away from RX). The bottom row shows cross polarized coupling magnitude [dB] vs Frequency [GHz] for the same three beam steering conditions: (d) 0 degree (boresight), (e) 15 degrees (TX steers main beam toward RX), and (f) -15 degrees (TX steers main beam away from RX). Each plot contains multiple curves representing different RX sub-arrays.](f603c6acdc3f09cfd451a07b47c4730f_img.jpg) + +Figure 9.2.1.2.2-2: TX panel to RX sub-array coupling magnitude curves. The figure consists of six subplots arranged in a 2x3 grid. The top row shows co-polarized coupling magnitude [dB] vs Frequency [GHz] (3.50 to 4.50 GHz) for (a) 0 degree (boresight), (b) 15 degrees (TX steers main beam toward RX), and (c) -15 degrees (TX steers main beam away from RX). The bottom row shows cross polarized coupling magnitude [dB] vs Frequency [GHz] for the same three beam steering conditions: (d) 0 degree (boresight), (e) 15 degrees (TX steers main beam toward RX), and (f) -15 degrees (TX steers main beam away from RX). Each plot contains multiple curves representing different RX sub-arrays. + +**Figure 9.2.1.2.2-2: TX panel to RX sub-array coupling magnitude curves considering co-polarized (top) and cross polarized (bottom) ports. Each curve represents the coupling magnitude of the TX panel to a single RX sub-array. Each sub-figure corresponds to a specific elevation angle.** + +The specific value depends on the scheduled users, and 70dB has been taken as a representative value. With TX beam nulling, as described in the subsequent section the variation can be reduced and the achievable isolation becomes around 80dB. + +### **TX beam nulling** + +The transmit panel has a large number of transmit elements and hence a high number of degrees of freedom to perform beamforming. Beam Nulling can be used in the transmit panel to reduce the power at the receive panel. It is not clear that beam nulling has the same impact on both the transmitted signal and the transmitter leakage, however for simplicity this has been assumed. A simulation investigation has been presented in [50], which demonstrated the possibility to increase the spatial isolation to around 80dB using beam nulling. Furthermore, beam nulling reduces the variation of the spatial isolation due to beam direction. Thus, 80dB of spatial isolation is assumed. + +The beam nulling has an impact on DL EIRP depending on the beam direction. The impact to DL MIMO performance was not investigated. + +### **Analogue interference cancellation** + +Analogue interference cancellation could be considered as a means for suppressing both interference in the RX sub-band and power in the TX sub-band entering the receiver. Analogue IC requires and inter-connections/routing paths to detect the signal at each transmitter as well as remove the interference in the receiver. In order to ensure that the removed signal is not impacted by receiver processing, the interference subtraction must take place in the first stage of the receiver chain, before the LNA and thus insertion losses caused by the coupling will degrade the noise figure. + +Analogue interference cancellation is a promising technology for some smaller BS types and simulations demonstrate potential for mitigating interference for larger arrays. However, the complexity of interconnections between all TX and RX elements in a large commercial BS and the losses associated with the combining and subtracting would lead to a performance decrease and size and weight increase for an AAS to the level of a doubtful feasibility. Thus, analogue interference cancellation has not been considered for a high power, large array AAS. + +### **Receiver analogue filtering** + +For the wide area BS, the main performance issue is the large power in the TX sub-bands entering the receiver, -27dBm. The minimum RAN4 requirement for a receiver is to produce a 6dB desensitization when a carrier of -43dBm is applied in a 2nd adjacent channel, and thus the application of -27dBm directly next to the RX sub-band is very challenging. Although the linearity performance can be improved, the LNA linearity cannot be directly improved to become sufficient. + +A possible solution is to use analogue filters before the LNA to remove the DL sub-band power. Investigations in [50] demonstrate that it is not possible to build analogue filters with an achievable Q-factor without a large insertion loss. + +![Three stacked plots showing analogue filter performance for Q=1500. Each plot shows S21-1 f (black solid line) and S12-1 rms (dashed lines) across a frequency range from 3460 to 3540 MHz. The top plot shows m4 S21-1 f at 3495 MHz (-7.6 dB), m3 S12-1 rms 10 MHz (3495 - 3505 MHz, -4.35 dB), and m2 S21-1 rms 20 MHz (3506.8 - 3526.8 MHz, -26.1 dB). The middle plot shows m4 S21-1 f at 3490 MHz (-7.39 dB), m3 S12-1 rms 20 MHz (3490 - 3510 MHz, -3.13 dB), and m2 S21-1 rms 20 MHz (3511.8 - 3531.8 MHz, -27.2 dB). The bottom plot shows m4 S21-1 f at 3485 MHz (-7.83 dB), m3 S12-1 rms 30 MHz (3485 - 3515 MHz, -2.64 dB), and m2 S21-1 rms 20 MHz (3516.8 - 3536.8 MHz, -27 dB).](94edd4dad9a6d1f95e2ab1822c06bf1a_img.jpg) + +Three stacked plots showing analogue filter performance for Q=1500. Each plot shows S21-1 f (black solid line) and S12-1 rms (dashed lines) across a frequency range from 3460 to 3540 MHz. The top plot shows m4 S21-1 f at 3495 MHz (-7.6 dB), m3 S12-1 rms 10 MHz (3495 - 3505 MHz, -4.35 dB), and m2 S21-1 rms 20 MHz (3506.8 - 3526.8 MHz, -26.1 dB). The middle plot shows m4 S21-1 f at 3490 MHz (-7.39 dB), m3 S12-1 rms 20 MHz (3490 - 3510 MHz, -3.13 dB), and m2 S21-1 rms 20 MHz (3511.8 - 3531.8 MHz, -27.2 dB). The bottom plot shows m4 S21-1 f at 3485 MHz (-7.83 dB), m3 S12-1 rms 30 MHz (3485 - 3515 MHz, -2.64 dB), and m2 S21-1 rms 20 MHz (3516.8 - 3536.8 MHz, -27 dB). + +**Figure 9.2.1.2.2-3: Analogue filter performance for Q=1500** + +**Table 9.2.1.2.2-1: Insertion losses for Q=1500 filters** + +| Filter type | Edge insertion loss | Average insertion loss | +|--------------------|---------------------|------------------------| +| 10 MHz UL sub-band | 7.6 dB | 4.4 dB | +| 20 MHz UL sub-band | 7.4 dB | 3.1 dB | +| 30 MHz UL sub-band | 7.8 dB | 2.6 dB | + +Another alternative is to place analogue filters between a first stage and a second stage LNA. Using this approach, the linearity of the receiver chain could in principle be improved with a much-reduced impact to the noise floor. However, there are a number of significant problems with such an approach: + +- The first LNA stage needs high linearity and becomes very power consuming. +- The tight integration needed to achieve power and weight efficient AAS BS is no longer feasible due to the filter size. Hence there will be further increases in power consumption due to reduced integration and thermal management issues. + +- The filters would need to be tuned specifically to the UL sub-band if implemented in RF. Hence, non-reconfigurable, operator specific hardware would be needed for every BS. The alternative is to use a mixer to bring the signal down to IF or baseband, but then the mixer linearity would compromise the receiver performance and the blocking performance would not be achieved. +- There would need to be a number of filters for every branch due to e.g. 2 polarizations, support for DL slots, UL slots and SBFD slots with different filtering requirements (even more filters if there would be multi-carrier support). Also switches would be needed, which would compromise linearity and add further space. It is doubtful all of the filters could be accommodated without further losses. + +Due to the above reasons, analogue filtering is not considered to be a realistic approach for a commercially relevant BS and so is not considered the feasibility analysis. + +### **Digital interference cancellation and digital processing** + +Digital TX interference cancellation and subtraction, and RX combining taking into account interference covariance have the potential to mitigate interference in the receiver. Digital processing has not been considered because the power level in the analogue front end of the receiver is high enough to saturate the receiver. Digital interference subtraction would require a very high computational complexity for a wide area AAS due to the large number of TX-RX combinations. + +#### **9.2.1.2.3 Huawei** + +For FR1 our analysis and evaluation are provided in the summary table, we show two examples for Wide Area BS to consider different max TX power. One is 47 dBm max TX power and the other is 53 dBm. The major difference for WA example 2 is the adoption of analog filter to counteract the higher RX blocking from TX sub-band. + +Analogue filter prior to the LNA would introduce also insertion loss which will cause sensitivity loss. Hence it is not suitable. Meanwhile putting analogue filter after LNA could tolerance the high insertion loss. The filter can be RF analog filter in the front-end or base-band analogue filter before the ADC. In the example we use RF analog filter which is put after LNA. The filter performance can be found in Figure below. A Q-value of 1500 and 5 poles are assumed in the simulator. It can be found that the insertion loss is less than 5 dB and ~15 dB suppression is achievable, with some margin to address the manufacturing accuracy and temperature drift. + +![Figure 9.2.1.2.3-1: Performance of an example sub-band filter. The graph shows the magnitude response (in dB) of a filter over a frequency range from 3580 to 3640 MHz. The y-axis ranges from -40 dB to 0 dB. The filter has a passband centered around 3608 MHz with a peak gain of approximately -4 dB. The stopbands show significant attenuation, reaching below -32 dB at 3580 MHz and 3640 MHz. The filter exhibits a sharp roll-off around 3600 MHz and 3616 MHz.](5b492020399ae8fbcc9714c8d83aebca_img.jpg) + +Figure 9.2.1.2.3-1: Performance of an example sub-band filter. The graph shows the magnitude response (in dB) of a filter over a frequency range from 3580 to 3640 MHz. The y-axis ranges from -40 dB to 0 dB. The filter has a passband centered around 3608 MHz with a peak gain of approximately -4 dB. The stopbands show significant attenuation, reaching below -32 dB at 3580 MHz and 3640 MHz. The filter exhibits a sharp roll-off around 3600 MHz and 3616 MHz. + +**Figure 9.2.1.2.3-1: Performance of an example sub-band filter** + +As shown in the example below, putting analogue filter after LNA, since the front-end LNA can provide substantial gain on the wanted signal, the impact to overall noise figure is negligible (2.21dB vs 2.24 dB), and the RX IIP3 prior to the filter is high enough to cope with high blocking level, such as ~-30 dBm. The OIP3 of gain block in LNA might need to be increased a bit, which results the addition of power consumption. However the addition is quite limited, which is less than 0.5% of overall power consumption. + +**Table 9.2.1.2.3-1: Cascaded NF and IIP3** + +| Receiver | Band Filter | LNA | ATT | subband Filter | +|-------------|-------------|-------|--------|----------------| +| GAIN(dB) | -1.20 | 25.00 | -2.00 | -5.00 | +| NF(dB) | 1.20 | 1.00 | 2.00 | 5.00 | +| OIP3(dBm) | 100.00 | 34.00 | 100.00 | 100.00 | +| C_gain(dB) | -1.20 | 23.80 | 21.80 | 16.80 | +| C_NF(dB) | 1.20 | 2.20 | 2.21 | 2.24 | +| C_OIP3(dBm) | 100.00 | 34.00 | 32.00 | 27.00 | +| C_IIP3(dBm) | 101.20 | 10.20 | 10.20 | 10.20 | + +Analogue sub-band filter after LNA can provide the needed suppression for the receiver parts after the filter, and the impacts to RX sensitivity due to insertion loss is negligible. If analogue sub-band filter is adopted in the solution, the blocking performance can be improved at least 10 dB. + +#### 9.2.1.2.4 Qualcomm + +To enable proper reception of the uplink signal at the gNB receiver with simultaneously transmission DL signal, gNB should mitigate the direct self-interference ‘leakage’ and any significant clutter reflections. The self-interference could be mitigated by different techniques such as spatial isolation, analog subband filter, analog interference cancellation, beamforming and digital interference cancellation. In the following, we discuss in detail the knobs for gNB transceiver that enable the mitigation of both component of self-interference, namely direct leakage and clutter reflections. + +##### Antenna techniques and spatial isolation + +For SBFD deployments, gNB antenna configurations should be based on two panels configuration with split of the antenna elements for simultaneous downlink transmission and uplink reception as shown in Figure 9.2.1.2.4-1 on the other hand, for legacy TDD deployments, gNB antenna configuration is based on single panel for downlink transmission or uplink reception. With the split panel architecture, the gNB can enable larger spatial isolation is an essential component to mitigate self-interference. In addition, the physical separation between the two panels could be used to add electro-magnetic spatial duplexer that enhances the spatial isolation between the panels. + +![Diagram comparing SBFD and TDD antenna modes. SBFD Mode shows a single panel with separate Tx and Rx sections, allowing simultaneous Tx and Rx. TDD Mode shows two separate panels, each with Tx or Rx capability, but not simultaneously.](9c12d7993e786817c8c569e6f2d5a0a9_img.jpg) + +The diagram illustrates two antenna configurations for gNB. On the left, labeled 'SBFD Mode', a single rectangular panel is shown, divided into two horizontal sections. The top section is labeled 'Tx' and the bottom section is labeled 'Rx'. A green arrow points left from the top section, and a blue arrow points right from the bottom section. The text 'Simultaneous Tx and Rx' is positioned to the left of the panel. On the right, labeled 'TDD Mode', two separate rectangular panels are shown, one above the other. Each panel has a label 'Tx or Rx' next to it. A green arrow points left from the top panel, and a blue arrow points right from the bottom panel. + +Diagram comparing SBFD and TDD antenna modes. SBFD Mode shows a single panel with separate Tx and Rx sections, allowing simultaneous Tx and Rx. TDD Mode shows two separate panels, each with Tx or Rx capability, but not simultaneously. + +**Figure 9.2.1.2.4-1: gNB antenna/panels configuration in TDD and SBFD modes** + +RF measurements for the Tx-Rx spatial has been conducted and results are shown in Figure 9.2.1.2.4-2. Each curve represents the spatial isolation measured between all transmit chains of one array to one receiver chain of the other array. This includes the near field transmit and receive antenna gains. The results show more than 80 dB of isolation is achieved at the band of interest. + +![Figure 9.2.1.2.4-2: Measured spatial Isolation with Radome On. A line graph showing S21 (dB) on the y-axis (from -100 to -60) versus Frequency (GHz) on the x-axis (from 3 to 4). Multiple colored lines represent different measurement results. A horizontal dashed line at -80 dB is labeled '80dB Isolation Frequency Support' with an arrow pointing to it.](c327245fb6a613288de330f6f5afa783_img.jpg) + +Figure 9.2.1.2.4-2: Measured spatial Isolation with Radome On. A line graph showing S21 (dB) on the y-axis (from -100 to -60) versus Frequency (GHz) on the x-axis (from 3 to 4). Multiple colored lines represent different measurement results. A horizontal dashed line at -80 dB is labeled '80dB Isolation Frequency Support' with an arrow pointing to it. + +**Figure 9.2.1.2.4-2: RF measurements of Tx-Rx spatial isolation between for FR1** + +### Frequency isolation + +DL and UL transmissions can be separated in the frequency domain via multiplexing of the DL and UL using non-overlapping DL and UL sub-bands. As a result, large frequency isolation for the UL signal reception is attained as shown in Figure 9.2.1.2.4-3. For RAN4 further considerations, the frequency isolation represents the ratio of the power of non-linear leakage into the UL subband to the power of the DL signal at the DL subband, which can be approximated by the ACLR requirements specified by RAN4. RAN1 has requested RAN4 to provide value range for the frequency isolation capability of the gNB as well as the accompanying assumptions to those values. + +![Figure 9.2.1.2.4-3: Frequency isolation. A schematic diagram showing a DL signal as a rectangular pulse. To the right of the pulse, a shaded triangular area represents 'DL non-linearities' that leak into the UL subband. A vertical double-headed arrow between the top of the DL pulse and the top of the shaded area is labeled 'Freq. isolation'.](f79cb254efa2e37d7facb055cf90086e_img.jpg) + +Figure 9.2.1.2.4-3: Frequency isolation. A schematic diagram showing a DL signal as a rectangular pulse. To the right of the pulse, a shaded triangular area represents 'DL non-linearities' that leak into the UL subband. A vertical double-headed arrow between the top of the DL pulse and the top of the shaded area is labeled 'Freq. isolation'. + +**Figure 9.2.1.2.4-3: Frequency isolation** + +A guardband may be needed at the gNB to protect UL reception within the UL subband and reduce the impact of self-interference. In some scenarios, depending on the gNB implementation, a very small guardband or even no guardband may be needed at all. However, from UE perspective, given that there is no UE selectivity, a guardband may be needed to protect the DL reception from the inter-UE CLI. To further analyse this, 80 MHz system bandwidth, the 60 MHz DL subband is allocated with 161 RBs (starting from first RBs at band edge) and the 20 MHz UL subband is allocated with 51 RBs. A guard band of 5RBs in between UL and DL subband. The Tx waveform is pushed to the PA to derive max Tx power of 47 dBm. The subband frequency isolation is defined at the ratio between the power leakage within the 20 MHz UL subband as compared to the transmit signal power within the 60 MHz DL subband as shown in Figure 9.2.1.2.4-4. + +![Figure 9.2.1.2.4-4: PSD of DL waveform and frequency isolation. The top part shows a frequency spectrum diagram with a total bandwidth of 80 MHz. It is divided into a 60 MHz Downlink (DL) section (161 RBs), a 5 RB Guard Band (GB), a 20 MHz Uplink (UL) section (51 RBs), and 940 KHz guard bands at the edges. A double-headed arrow above the main components indicates a span of 217 RBs. The bottom part is a Power Spectral Density (PSD) plot in dBm/30KHz versus Frequency in MHz. The plot shows a green curve for the DL signal and a blue curve for the UL signal. The DL signal has a flat top at approximately 15 dBm between -40 MHz and 20 MHz. The UL signal has a flat top at approximately -20 dBm between 40 MHz and 60 MHz. The plot includes performance metrics: Pout = 46.9785 dBm, LR = 50.38 dB, and EVM = -42.8905 dB. An arrow labeled 'SEM' points to the blue curve.](ce8b1b60587224b653aaef31adb64ac4_img.jpg) + +**BW = 80MHz - SC = 30 KHz - DL RBs = 161 RB - GB = 5 RBs** + +Pout = 46.9785 dBm + LR = 50.38 dB + EVM = -42.8905 dB + +Figure 9.2.1.2.4-4: PSD of DL waveform and frequency isolation. The top part shows a frequency spectrum diagram with a total bandwidth of 80 MHz. It is divided into a 60 MHz Downlink (DL) section (161 RBs), a 5 RB Guard Band (GB), a 20 MHz Uplink (UL) section (51 RBs), and 940 KHz guard bands at the edges. A double-headed arrow above the main components indicates a span of 217 RBs. The bottom part is a Power Spectral Density (PSD) plot in dBm/30KHz versus Frequency in MHz. The plot shows a green curve for the DL signal and a blue curve for the UL signal. The DL signal has a flat top at approximately 15 dBm between -40 MHz and 20 MHz. The UL signal has a flat top at approximately -20 dBm between 40 MHz and 60 MHz. The plot includes performance metrics: Pout = 46.9785 dBm, LR = 50.38 dB, and EVM = -42.8905 dB. An arrow labeled 'SEM' points to the blue curve. + +**Figure 9.2.1.2.4-4: PSD of DL waveform and frequency isolation** + +### Beam isolation and beamforming/nulling + +In FR1, the DL precoder and UL combiner weights could be optimized to provide some beamform nulling for the clutter and/or self-interference. The massive MIMO antenna has large number of degrees of freedom in both digital and analog (i.e., hybrid beamforming) that provide the ability to create some spatial nulls. Beamforming nulling is an efficient technique for clutter mitigation. + +### Digital self-interference mitigation + +The nonlinearities introduced within the gNB front's end due to non-ideal components of the Tx chain will lead to residual non-linear self-interference that cannot be fully captured in the RF or analog domain due to the associated high complexity, high sensitivity of the canceler and the system's stability. In this regard, leveraging adaptive filtering and non-linear modeling of the residual self-interference to accurately model and cancel the residual self-interference is performed to provide additional mitigation in the digital domain and enable higher MCS. With the knowledge of the DL samples and the non-linear model, an adaptive filter can be used to synthesize the non-linear leakage and cancel it out from the Rx signal as shown in Figure 9.2.1.2.4-5. This technique can be used for cancellation of both self-interference and clutter echo by having multiple taps cancellation. + +![Block diagram of digital self-interference cancellation. A transmitter (TxFE) sends a signal to an adaptive filter. The adaptive filter outputs an 'Interference Estimate'. A receiver (RxFE) sends a signal to a summation node (Σ). The 'Interference Estimate' is subtracted from the receiver signal at the summation node. The output of the summation node is labeled 'TO FFT'. The adaptive filter, summation node, and IC are collectively labeled as 'IC' (Integrated Circuit).](cf8d9315f7f99ef87b4040c7312c5c6f_img.jpg) + +Block diagram of digital self-interference cancellation. A transmitter (TxFE) sends a signal to an adaptive filter. The adaptive filter outputs an 'Interference Estimate'. A receiver (RxFE) sends a signal to a summation node (Σ). The 'Interference Estimate' is subtracted from the receiver signal at the summation node. The output of the summation node is labeled 'TO FFT'. The adaptive filter, summation node, and IC are collectively labeled as 'IC' (Integrated Circuit). + +**Figure 9.2.1.2.4-5: Digital self-interference cancellation** + +### 9.2.1.2.5 CATT + +For FR1 Wide Area BS SI analysis, the following assumptions are used. + +**Table 9.2.1.2.5-1: SI analysis assumptions for Wide area BS** + +| Parameters | Wide Area BS | +|---------------------------------------------------|--------------| +| Reference sensitivity level degradation due to SI | 1dB | +| Channel bandwidth | 100MHz | +| Subband configuration | {DUD} | +| DL subband width | 40MHz*2 | +| UL subband width | 20MHz | +| Tx output power over whole channel | 49dBm | +| Adjacent subband Leakage Power Ratio | 45dB | +| Noise Figure | 5dB | + +In SI capability analysis, the following techniques are used, + +- CFR is used to improve component efficiency, DPD is used for high power equipment to optimize ACLR. +- Tx antennas panel and Rx antennas panel are separate, there are also some isolation materials between them, and cross polarization is also used. +- RF subband RF filter is assumed for Tx and Rx path. +- Digital filter is used to resolve the adjacent subband (i.e. Tx subband) interference issue. +- Beam nulling is used to improve isolation between Tx and Rx. +- Digital IC is used to reduce interference in the UL sub-bands. The interference is leakage from the transmitter, similar as DPD, digital domain needs to capture and sample the interference signals, then subtract the interference at receiver. + +From the analysis provided in the summary table, the receiver may be blocked. Some specific techniques need to be used to improve the spatial ISO. Requirement of IIP3 is relatively high and the ACS requirement is improved largely compared with the legacy BS. It seems wide area SBFD BS design may need much improvement from several aspects to make it feasible. + +### 9.2.1.2.6 Nokia + +The Nokia input in the summary table presents the company’s view on the self-interference mitigation analysis for a wide area base station with 54 dBm total output power. The RSIC capability corresponds to 110 dBc for the Rx subband and between 122 dBc for TX sub-band which are achieved using a combination of spatial isolation (65 dBc), frequency separation (45 dBc), and Tx beam nulling (5-10 dBc, only applicable to the Tx subband isolation). Under such considerations, the self-interference observed in the UL subband is -62 dBm/20 MHz (dominated by ACLR from the transmitter) which is 34 dB above the noise floor. Such level of interference would result in high desensitization of the + +receiver which makes it unpractical for wide-area deployments where coverage is one of the main KPIs. A detailed description of the assumed techniques and other assumptions is provided in the summary table. + +### **BS TX Power** + +To study the feasibility for wide area base stations, including powerful mMIMO base stations, an output power of 55 dBm (as e.g. in the case of 64 TX paths with 5 W each) is assumed. Considering 80%/20% DL/UL frequency resource split in an SBFD configuration, this amounts to 54 dBm. + +If lower power is assumed for wide area base stations, correspondingly the deployment scenario would require a denser ISD. + +### **Frequency isolation at TX** + +We think 45 dB frequency isolation is feasible. This is in line with the 45 dB ACLR requirement that is typical for base stations, albeit for D-U-D sub-band configuration, slightly more difficult to achieve. + +The techniques to achieve sufficient frequency isolation may include: + +- Transmitter digital filtering or windowing to clean the UL sub-band. This is required to clean the IFFT output of the linear leakage of the signal, otherwise the sinc spectrum of the IFFT will dominate the emissions on the UL sub-band. Requires new filter design with potentially tighter suppression requirements compared to the channel filter, due to the desire to minimize guard bands between DL and UL sub-bands. +- Tighter filter suppression requirements may mean longer filter impulse response and lead to signal EVM degradation. +- Transmitter digital pre-distortion to linearize the transmit chain and suppress PA distortion components. Achieving the same performance for sub-band leakage ratio as for ACLR will be more challenging, as the UL sub-band is closer to the DL sub-band(s) than the adjacent channel. The ACLR is averaged over the same bandwidth as the DL channel, with emissions likely decaying somewhat with offset. For inter-sub-band leakage, the offset is generally small, indicating tighter DPD requirements for the same absolute level of emissions. Moreover, the DUD frequency configuration will be challenging due to spectral regrowth from both sides of the UL sub-band, compared to DU configuration or the ACLR case. +- Higher DPD complexity translates to higher energy consumption. +- Higher energy consumption leads to increased heating, worse PA performance and thermal management issues. This may require larger and heavier cooling solutions. + +### **Spatial isolation** + +For the achievable spatial isolation for separate TX and RX antenna arrays, we find that 65 dB may be a reasonable assumption for a well-designed antenna in an average case, if assuming EM shielding structures between the arrays. + +The techniques to achieve sufficient spatial isolation may include: + +- Separate TX and RX antennas or antenna arrays. Increased separation from TX to RX will improve isolation. +- To maintain the same or similar physical size of the antenna, the number of elements per array need to be halved. This reduces the achievable array gain by at least 3 dB in both link directions and has been demonstrated by simulations to degrade the system performance. +- To maintain baseline system performance, the number of antenna elements per array must be maintained, leading to an increased antenna size by at least 2x. This in turn means higher weight and wind load, increased complexity, increased trace losses which may need to be compensated, and in general higher cost. +- Separate TX and RX antenna arrays requires separate PWBs for the TX and RX, leading to a higher cost. +- Separate TX and RX antenna arrays leads to loss of reciprocity in the DL and UL channels and makes reliable channel state measurements more difficult and complicated. The extent of this loss has not been studied. +- EM shielding techniques such as wave traps or chokes between the TX and RX arrays. + +### **TX Beam nulling /isolation in TX sub-band** + +The beamforming coefficients of the transmit beamforming may be modified so that the energy coupled to the receive antenna elements is minimized. We have conducted EM simulations that measure the TX-RX isolation based on the most exposed RX antenna element/subarray, where this element/subarray is determined separately, with and without beam nulling. Those findings are found in contribution [48]. We observe that the level of self-interference depends on the beam direction. We have measured a minimum of 8 dB of beam nulling gain for all the Tx beams and up to 14 dB of gain for the beam with lowest isolation to the receive antenna elements as illustrated in Figure 9.2.1.2.6-1. The observed DL EIRP impact was between 0dB - 0.8 dB depending on beam direction, although 90% of the transmit beams experienced a DL EIRP loss below 0.3 dB. Note also that: + +- The modification of TX beamforming coefficients reduces the transmitted EIRP toward the intended UE, leading to further reduced DL performance unless compensated by increased conducted power. +- Based on simulations, some TX beams may be affected more than others, leading to potential scheduler restrictions in which UEs may be scheduled during the SBFD time slots. +- The transmit beam nulling is most effective on the DL sub-band, for which the transmit signal is known and can be beamformed. It is not assumed that transmit beam nulling is effective on the UL sub-band, which contains only unwanted emission components from the transmitter. + +![Figure 9.2.1.2.6-1: Empirical CDF of isolation between each Tx beam towards worst-affected Rx port. The graph shows two curves: 'without beam nulling' (blue) and 'with beam nulling' (orange). The x-axis is 'dBc' ranging from 50 to 85, and the y-axis is 'CDF' ranging from 0 to 1. The 'without beam nulling' curve starts at 0 CDF at 50 dBc and reaches 1 CDF at approximately 70 dBc. The 'with beam nulling' curve starts at 0 CDF at 65 dBc and reaches 1 CDF at approximately 82 dBc. This indicates that beam nulling significantly improves the isolation between Tx beams and the worst-affected Rx port.](6127ca80a1bc3d6a86b357a6ac43cb98_img.jpg) + +Figure 9.2.1.2.6-1: Empirical CDF of isolation between each Tx beam towards worst-affected Rx port. The graph shows two curves: 'without beam nulling' (blue) and 'with beam nulling' (orange). The x-axis is 'dBc' ranging from 50 to 85, and the y-axis is 'CDF' ranging from 0 to 1. The 'without beam nulling' curve starts at 0 CDF at 50 dBc and reaches 1 CDF at approximately 70 dBc. The 'with beam nulling' curve starts at 0 CDF at 65 dBc and reaches 1 CDF at approximately 82 dBc. This indicates that beam nulling significantly improves the isolation between Tx beams and the worst-affected Rx port. + +**Figure 9.2.1.2.6-1: Empirical CDF of isolation between each Tx beam towards worst-affected Rx port. Tx beams are generated within $\pm 45^\circ$ azimuth and elevation angles.** + +#### **RF IC and other tech. (before LNA)** + +The following techniques have been evaluated, but have significant challenges in FR1 wide area base station implementations: + +- Analog cancellation in the RF domain. This method may be used to subtract the unwanted coupled TX signal components from the RX signal path, before the LNA. With proper phase shift and amplitude scaling, the TX component may be cancelled. +- There has been a proposal of an AFIR type of canceler solution in which the canceler unit is made of $M+N$ individual cancelers, where $M$ is the number of TXs and $N$ the number of RXs. The canceler unit is connected to TX and RX antenna panels. If $M=N=64$ there will be 64 RF connections from TX panel to the canceler unit and 64 RF connections from canceler unit to RX panel. That might be doable in a common mechanics but in the case that all three units are separate, it is not feasible anymore. Since the distance of the TX and RX antenna panels need to be quite high (due to needed spatial isolation) and receiver and transmitter chains need to be located close to antenna filters (to avoid excessive insertion losses that cannot be compensated), separate TX and RX PWBs are needed. +- Valid mathematics have been presented that $M+N$ cancelers are sufficient for RF IC but that it is true only when one set of beamforming coefficients are valid at a time e.g. in the mmW arrays. For MU MIMO there is a need for $(M+N) \times U \times L$ cancelers where $M$ and $N$ are as above and $U$ is the number of users and $L$ is the average number of layers per use. For a typical 5G case that would be starting from 5120 cancelers. On top of + +that, all of them have to be updated every time when the beamforming coefficients are updated. That leads to an intolerable complexity and processing burden when solving mathematics for each of those individually. + +### **Frequency isolation at RX** + +Sub-band filtering techniques before or after the LNA may improve frequency isolation, but have significant challenges in FR1 wide area base station implementations and therefore are not assumed to be feasible: + +- High insertion loss before the LNA will increase the receiver noise figure and negate any system gains of SBFD. +- If a sub-band filter would be used between the two LNAs, i.e. as an inter-stage filter: + - Very high linearity is required from the first stage LNA, which will lead to increased cost, power consumption and thermal management issues. + - Inter-stage filter does not help to protect the first LNA from direct ACLR from the aggressor. If the first stage LNA is saturated, the receiver would not work. +- High insertion loss placed after the LNA does not reduce LNA linearity requirements. Improved linearity LNAs are needed that add to cost and power consumption, which leads to thermal management issues. Other challenges include: + - Significant insertion loss → NF increase that can hardly be accommodated in the 1 dB desensitization budget. + - Considerable transition band and temperature dependency of the passband position → larger guard band between the sub-bands needed and less BW is usable for UL + - Group delay distortion close to the cut-off frequencies + - Incompatibility with a typical multi-carrier gNB design + - Increased complexity as switches are needed for by-pass in UL slots for full BW + - Additional space needed in RX chain that is not available in typical gNB design + - Overall additional power consumption which leads to thermal management issues + - Frequency drift over temperature that will impact filter insertion loss and rejection performance, hence impacts the RX lineup performance +- The new sub-band specific filters would be operator's spectrum specific and locking the spectrum configuration for any further changes or tuning. The existing bandpass filters for the operating band would anyway be required, suggesting that the new filters would double the filter size for the UL antenna panel. This all means higher cost and complexity. +- Besides, some preliminary analyses with simulations of filters with Q-values of 1500 and even up to 5000 have been presented by companies. In one of the analyses, it has been shown that the guard bands would become very wide or excessive losses would be obtained otherwise. Also, it is important to note that these simulations have not taken the manufacturing tolerances into consideration nor the temperature drift, which have an effect of paramount importance when implementing a working filtering solution. Last but not least, these filtering solutions would be too large to be suited for mMIMO BS, and they add large amount of cost to the BOM of a BS. + +### **RX Beam nulling / isolation in RX sub-band** + +We assume 0 dB for RX beam nulling; as the SBFD feature is about enhancing uplink performance, we do not think the UL beamforming can be compromised further than the loss of channel reciprocity (due to separate TX and RX arrays) brings. + +RX beamforming operates in the digital domain in a mMIMO system. The digital signal streams of the relevant receivers are combined using suitable amplitude and phase coefficients. Hence RX beam nulling will not relax the receiver dynamic range and linearity requirements. + +### **Digital IC** + +The following techniques have been evaluated, but have significant challenges in FR1 wide area base station implementations: + +- Digital cancellation. With knowledge of the TX signal, a properly scaled and phase shifted TX component may be subtracted from the RX signal to improve cancellation performance. +- The TX signal may be available from observation receiver that is used in the DPD processing. For a mMIMO implementation, the DPD system may utilize only a few observation receivers, that sample the TX chains sequentially. It may be necessary to multiply the number of observation receivers to be able to sample each TX chain, leading to increased cost and energy consumption. +- Each RX chain contains signals that are coupled from every TX chain. This means that the cancellation signal for each RX chain must be formed of every TX chains. The complexity can easily become extreme in a mMIMO implementation, with 32 or 64 TRXs. The complexity of the cancellation results in high energy consumption. +- The cancellation may work with different performance for the DL signal fundamental components (i.e. the DL PRBs) than for the unwanted emission components (i.e. leakage on UL sub-band). The DL signal may be easier to cancel than the unwanted emissions. For the unwanted emissions, it is more efficient to cancel them at the TX DPD. + +### 9.2.1.3 Conclusion + +Based on the self-interference analysis provided in Section 9.2.1 for FR1 wide area BS, it can be observed that the implementation feasibility of controlling the residual interference to meet the 1dB receiver desensitization target depends on the implementation aspects including: + +- Maximum BS transmit power +- Spatial isolation capability +- beam nulling/ isolation capability +- Blocker suppression at the RX +- Frequency isolation at the TX and RX +- The digital interference suppression/cancellation capabilities + +Based on the different assumptions and/or technique adoption for the above-mentioned implementations aspects, and based on 6 companies' technical inputs, companies have come to the following conclusions: + +- 1dB receiver desensitization target is achievable by self-interference cancellation capability according to 3 companies. + +1dB receiver desensitization target is not achievable or is challenging based on existing technology and technology roadmaps that are viewed as viable in the current time or foreseeable future according to 3 companies. + +## 9.2.2 Co-channel inter-sub-band co-site inter-sector interference analysis + +### 9.2.2.1 Summary table for co-channel inter-sub-band co-site inter-sector interference analysis + +RAN4 has carried out the study based on an analysis framework as provided in the following table to capture co-site inter-sector co-channel interference impact [49], which is used to capture inputs from companies. + +**Table 9.2.2.1-1: FR1 WA BS Co-site Inter-sector Co-channel Interference Analysis Summary** + +| FR1 | | | Samsung | Samsung | Ericsson | Huawei | Nokia | | +|------------------------------------------------------------------------|---------------------------|----------------------------------------------------------------------|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------|----------------------------------------------------------------------------------|------------------------------------------------------------|--| +| BS class | | | Wide Area BS (subband filter-1) | Wide Area BS (subband filter-2 and EM conjugated structure) | Wide Area BS | Wide Area BS | Wide Area BS | | +| BS TX Power = ① dBm | | | 49 dBm | 49 dBm | 53 dBm | 53 dBm | 54 dBm | | +| Number of co-site co-channel sectors considered | | | 1 | 1 | 2 | 2 | 2 (plus 1 sector for self-interference) | | +| Component capability and parameters | Frequency isolation at TX | Frequency isolation capability = ② dBc | 45 dBc | 45 dBc | 45 dBc | 45 dBc | 45 dBc | | +| | | Frequency isolation techniques used | DPD utilized | DPD utilized | DPD, CFR | DPD | DPD, digital filtering | | +| | Spatial isolation | Co-channel Co-site Inter-sector Spatial isolation capability = ③ dBc | 75 dBc | 100 dBc | 75-90 dBc (Varies depending on scheduled beam directions) | 85 dBc | 60-80 dBc | | +| | | Co-channel Co-site Inter-sector Spatial isolation techniques used | Based on 75dB for typical spatial isolation | Based on 75dB for typical spatial isolation and additional 25dB by installing EM conjugated structure between sectors | Typical site layout with around 400mm between sectors | Spatial separation between TX panel with absorbing material and choke structure. | Spatial separation between TX/RX panel; cross polarization | | +| TX Beam nulling /isolation of inter-sector interference in TX sub-band | | | 10 dBc | 10 dBc | 0 dBc | 10 dB | 0 dBc | | + +| | | | | | | | | | +|------------------------------|---------------------------------------------------------------------------------------------------------------------------|---------------------------|----------------------------------------------------------------|-------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------|----------------------------------------------|--| +| | = ④ dBc | | | | | | | | +| | DL EIRP impact due to beam nulling in TX sub-band (considering all nulling for self- and inter-sector interference) | | Neglectable | Neglectable | 0 dB | Less than 0.5 dB loss | n.a | | +| | Interference leakage in gNB RX subband due to non-ideal TX, measured at RX ant. due to inter-sector interference (Note 1) | | -81dBm | -106dBm | -79 to -64 dBm (Varies depending on scheduled beam directions) | -74 dBm | -74...-54 dBm | | +| | Interference signal in gNB TX subband, measured at the input of LNA (Note 1) due to inter-sector interference | | -51dBm (-36dBm and further suppressed by 15dB subband filter) | -72.8dBm (-61dBm and further suppressed by 11.8dB subband filter) | -34 to -19 dBm (Varies depending on scheduled beam directions) | -39 dBm | -23...-3 dBm (receiver will be blocked) | | +| Blocker
Suppression at RX | Frequency isolation capability ⑥ dBc | | 40 dBc | 40 dBc | 0 dBc | sub-band analog filter: 10 dB
digital filter: 60-80 dB | 46 dBc | | +| | Frequency isolation techniques | | Filtering | Filtering | None; see section 9.2.1.2.2 for analysis.. | sub-band analog filter put after LNA; digital filter | Digital filtering, FFT frequency selectivity | | +| | RX IMD | Rx IIP3 capability (dBm) | With subband filtering, RX non-linearity impact is neglectable | With subband filtering, RX non-linearity impact is neglectable | -32dBm (Minimum for RAN4 requirement)
-22dBm (Realistic for AAS)
-10dBm (optimistic for AAS) | 0 dBm | Included in the NF model | | +| | | Rx IM3 contribution (dBm) | | | -18 to +9 dBm (Minimum RAN4 receiver)
-38 to -12dBm (Realistic for AAS)
-62 to -35 dBm (optimistic for AAS)
(Varies depending on scheduled beam directions) | -127 | | | + +| | | | | | | | | | +|--------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------|-------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------|--------------------------------------------------------------|--| +| | Other RX | Any other RX impacts if significant (e.g. ADC noise, phase noise etc.) | N/A | N/A | (IM3 due to inter-sector interference only, assuming the presence of both self- and inter-sector interference in the receiver) | Negligible | | | +| | Interference signal in gNB RX subband caused by non-ideal RX selectivity, gain-normalized due to co-site inter-sector co-channel interference only (Note 1, 2) | | -91dBm | -112.8dBm | -18 to +9 dBm (Minimum RAN4 receiver)
-38 to -12dBm (Realistic for AAS)
-62 to -35 dBm (optimistic for AAS)
(Varies depending on scheduled beam directions) | Note: Each company to explain if/how they have separated CSSI and SI when considering IM3 | Inf dBm (receiver will be blocked above -25 dBm input level) | | +| | RX Beam nulling /isolation in RX sub-band = ⑨ dBc | | 10 dB | 10 dB | 0 dB | 10 dB | 0 dB | | +| | RX sensitivity degradation caused by RX beam nulling | | Neglectable | Neglectable | Receiver saturated; RX processing not feasible | Less than 0.5 dB loss | n.a. | | +| | Digital processing interference suppression capability | | 20dB | 20dB | No digital cancellation between sectors. RX Saturated | 12 | 0 dB | | +| Total interference in RX SB (dBm) (Note 2) | | | -100.6 dBm | -125.2 dBm | -18 to +9 dBm (Minimum RAN4 receiver)
-38 to -12dBm (Realistic for AAS)
-62 to -35 dBm (optimistic for AAS)
(Additional interference due to inter-sector interference only)
(Varies depending on scheduled beam directions) | -102 dBm/20 MHz | Inf dBc | | + +| Noise floor @dBm | -96 dBm/CBW | -96 dBm/CBW | -96 dBm/CBW | -96 dBm/CBW | Inf dBm/CBW | | +|----------------------------------------------|---------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|------------------------------|---------------------|--------------------|--| +| Calculated Desensitization (dB) | 1.29 dB relative to normal RX REFSENS (1.05 dB relative to normal RX REFSENS) | Neglectable | Receiver saturated (>> 30dB) | 1 dB | Inf dB | | +| SBFD configuration | DUD(40-20-40MHz) | DUD(40-20-40MHz) | 40-20-40 MHz | DUD [40, 20, 40] | DUD (40-20-40 MHz) | | +| Guardband assumption (if exist) | 5 PRB | 5 PRB | 5 PRB. | Existing SU | 5 PRB | | +| bandwidth over which suppression is achieved | 20MHz | 20MHz | >300 MHz | Several hundred MHz | | | +| Others | subband filtering (20MHz passband, 2*5PRB transition band used for roll-off between passband/stop band) | subband filtering (24.8MHz passband, 2*3.8MHz transition band used for roll-off between passband/stop band) | | | | | + +## 9.2.2.2 Feasibility study on co-channel inter-sub-band co-site inter-sector interference + +### 9.2.2.2.1 Samsung + +The achievable antenna isolation is key factor to analyze the co-site inter-sector co-channel gNB-gNB CLI. For the below interested scenario, antenna isolation (with the achievable coupling loss) is to be evaluated: + +- 3 sector scenario is under consideration: + - The angle between every two sectors' boresight directions is 120 degrees; + - Sector antenna panel's width is 180mm; + - Between two sectors' antenna panel: + - The center-to-center distance is: 150mm; + - The nearest distance between edge to edge is: 60mm; + - Three antenna elements are used to form the antenna port. + - 3.5GHz operating frequency with 100MHz bandwidth. + +The above simulation scenario can be illustrated in Figure 9.2.2.2.1-1. In the right part of below figure, the top view is presented with the concerned panels of sector 1 and sector 2. + +![Figure 9.2.2.2.1-1: (Left figure) 3-sector scenario for co-channel co-site inter-sector antenna isolation study; (Right figure) top view for the 2-sector scenario.](7adece84bcb18fcd9f28c138beb9d4d9_img.jpg) + +The image contains two diagrams. The left diagram is a 3D perspective view of three antenna panels arranged in a circular fashion, each with a grid of elements. The right diagram is a top-down 2D view showing two antenna panels, labeled 'Sector 1' and 'Sector 2'. Sector 1 is a horizontal bar with four elements numbered 1 to 4. Sector 2 is a tilted bar, also with four elements numbered 1 to 4. A dashed blue line with arrows indicates a center-to-center distance of 150 mm between the two sectors. Another dashed blue line with arrows indicates an edge-to-edge distance of 60 mm between the two sectors. + +Figure 9.2.2.2.1-1: (Left figure) 3-sector scenario for co-channel co-site inter-sector antenna isolation study; (Right figure) top view for the 2-sector scenario. + +**Figure 9.2.2.2.1-1: (Left figure) 3-sector scenario for co-channel co-site inter-sector antenna isolation study; +(Right figure) top view for the 2-sector scenario.** + +Accordingly, we have performed HFSS-based RF simulation for the above 3-sector scenario, by evaluating the isolation from sector 2 to sector 1. Specifically, S-parameters between two antenna ports from two sectors are evaluated, by considering each pair of antenna ports with co/cross-polarization relationships, which is illustrated in Figure 9.2.2.2.1-2. The RF evaluation results have been provided in the Table 9.2.2.2.1-1. + +![Diagram illustrating S-parameters for antenna port pairs in Sector 1 and Sector 2. Each sector has a 4x4 grid of ports labeled P/N. Sector 1 ports are 5, 6, 7, 8 (top row), 1, 2, 3, 4 (second row), a, b, c, d (third row), and e, f, g, h (bottom row). Sector 2 ports are 5, 6, 7, 8 (top row), 1, 2, 3, 4 (second row), a, b, c, d (third row), and e, f, g, h (bottom row). Red boxes highlight port pairs (1,2), (3,4), (a,b), (c,d) in both sectors. Red arrows point from these highlighted pairs in Sector 1 to those in Sector 2. Legend: * N ↔ N : Co-Pol, * N ↔ P : Cross-Pol.](29aa6165ccf449dee0b4335676fa7b1a_img.jpg) + +Diagram illustrating S-parameters for antenna port pairs in Sector 1 and Sector 2. Each sector has a 4x4 grid of ports labeled P/N. Sector 1 ports are 5, 6, 7, 8 (top row), 1, 2, 3, 4 (second row), a, b, c, d (third row), and e, f, g, h (bottom row). Sector 2 ports are 5, 6, 7, 8 (top row), 1, 2, 3, 4 (second row), a, b, c, d (third row), and e, f, g, h (bottom row). Red boxes highlight port pairs (1,2), (3,4), (a,b), (c,d) in both sectors. Red arrows point from these highlighted pairs in Sector 1 to those in Sector 2. Legend: \* N ↔ N : Co-Pol, \* N ↔ P : Cross-Pol. + +Figure 9.2.2.2.1-2: Illustration of S-parameters for antenna port pair. + +Table 9.2.2.2.1-1: S-parameter evaluation results. + +| | N1 | | | | | | | | N2 | | | | | | | | +|-----------------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------| +| | N_a | N_b | N_c | N_d | P_a | P_b | P_c | P_d | N_a | N_b | N_c | N_d | P_a | P_b | P_c | P_d | +| 150 mm distance | -82.1 | -69.7 | -74.3 | -72.7 | -66.6 | -71.9 | -78.7 | -78.0 | -81.1 | -90.9 | -76.8 | -83.9 | -72.2 | -74.9 | -78.1 | -78.8 | + +| | N1 | | | | | | | | N2 | | | | | | | | +|-----------------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------| +| | N_e | N_f | N_g | N_h | P_e | P_f | P_g | P_h | N_e | N_f | N_g | N_h | P_e | P_f | P_g | P_h | +| 150 mm distance | -62.1 | -71.9 | -81.3 | -77.6 | -66.8 | -72.8 | -75.1 | -73.2 | -78.2 | -79.7 | -80.9 | -83.2 | -77.6 | -83.6 | -78.0 | -77.2 | + +| | N3 | | | | | | | | N4 | | | | | | | | +|-----------------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------| +| | N_a | N_b | N_c | N_d | P_a | P_b | P_c | P_d | N_a | N_b | N_c | N_d | P_a | P_b | P_c | P_d | +| 150 mm distance | -93.0 | -80.9 | -80.2 | -74.7 | -81.1 | -80.3 | -82.1 | -79.2 | -85.0 | -82.5 | -77.9 | -74.1 | -73.4 | -77.2 | -78.8 | -71.6 | + +| | N3 | | | | | | | | N4 | | | | | | | | +|-----------------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------| +| | N_e | N_f | N_g | N_h | P_e | P_f | P_g | P_h | N_e | N_f | N_g | N_h | P_e | P_f | P_g | P_h | +| 150 mm distance | -86.3 | -81.3 | -72.0 | -74.9 | -76.2 | -78.7 | -86.9 | -86.5 | -73.5 | -85.1 | -79.0 | -91.5 | -82.6 | -78.7 | -78.1 | -68.2 | + +Based on the numerical results, the variance of spatial isolation for different antenna port pairs and different co-/cross-polarization relationships can be demonstrated. Moreover, the edge effect (the wave traversing the surface of antenna panel is condensed and reflected arbitrary at the edge of the antenna panel or any obstacles) further complicates the results. + +By comparing the same pair of antenna ports but with co-polarization and cross-polarization, it is hard to have a simple observation for which one is higher, but different observations depend on the designated antenna pair. The results could be explainable by the +45degree and -45degree placement for two polarizations. Within a panel, the co-pol and cross-pol can be guaranteed, while 3-sector case may make the alignment disappear. + +The RF simulation has shown the antennal isolation for co-channel co-site inter-sector gNB-gNB CLI is in the range of 62-93dB, depending on different antenna pair and co/cross-polarization, and 75dB can be regarded as typical value as RAN4 agreement. + +It is worth noting that the above spatial isolation values (typical value for 75dB) based on HFSS simulation have not yet reflected EM conjugated structure as used in the testbed for two panels within a sector. In the testbed to evaluate self-interference within a sector, the EM conjugated structure can improve around 20~30dB additionally. It is anticipated that the similar improvement if the EM conjugated structure is installed between two-sector antennas. Hence, with the EM conjugated structure, it is expected that the achievable antenna isolation shall be improved by around 25dB. + +#### 9.2.2.2.2 Ericsson + +The input provided in Table 9.2.2.1-1 presents an analysis of the inter-sector interference effects for wide area FR1 BS. It should be noted that, as demonstrated in section 9.2.1.2.2, the receiver is already driven into saturation due to self-interference. In addition to the self-interference, the inter-sector interference in the TX sub-bands is also very high power and would drive the receiver into saturation. + +##### **Inter-sector isolation** + +Due to capacity optimization and site costs, outdoor sites will typically host several sectors, as well as potentially co-located base stations. Some examples of different types of deployment are depicted in figure 9.2.2.2.2-1. Site space constraints (considering zoning, rental, weight, wind-load and other factors) typically mean that the potential to increase distance between sectors or to mount additional structures between sectors and base stations can be very limited. + +To avoid direct interference to the SBFD receive resources, all sectors using the same carrier must apply SBFD simultaneously in the same slots. If this is the case, then the SBFD receiver will still experience significant power from the TX sub-band of the other sectors, and from other base stations. The isolation between the TX sub-band of other sectors and the RX panel can potentially be less than the TX sub-band within the own base station since the possibilities for building an efficient isolating structure between sectors is less than within a BS. + +![A collage of six photographs showing various outdoor base station (BS) deployments. The images show antennas mounted on building roofs, streetlights, and trees against a blue sky with clouds.](f3a212725e08adb7b81020a6d010ee05_img.jpg) + +A collage of six photographs illustrating different outdoor base station (BS) deployments. The top-left image shows a tall antenna array on a building roof. The top-right image shows a single antenna unit mounted on a streetlight pole. The middle-left image shows a streetlight pole with multiple antenna units. The middle-right image shows an antenna unit mounted on a tree. The bottom-left image shows a building roof with several antenna units. The bottom-right image shows a tall antenna array on a pole. + +A collage of six photographs showing various outdoor base station (BS) deployments. The images show antennas mounted on building roofs, streetlights, and trees against a blue sky with clouds. + +**Figure 9.2.2.2.2-1: Examples of outdoor BS deployments** + +Isolation between sectors has been simulated using electromagnetic simulations in [68] with an assumption of 400mm sector separation. The isolation varies to some degree with separation, but not to an extent that would change the overall results. For most practical site deployments, addition of materials between sectors is not likely to be feasible (and may reduce network performance). The simulation set-up is depicted in figure 9.2.2.2.2-2. In additional to a horizontal separation, a height separation between TX and RX panels is assumed. + +![Figure 9.2.2.2.2-2: EM simulation setup for 3-sector site. (a) Top-down view showing three sectors (Sector 1, Sector 2, Sector 3) arranged in a triangle with a distance of 400.05mm between Sector 2 and Sector 3. (b) Side view showing the three sectors stacked vertically with a height of 300.00mm between Sector 1 and Sector 2.](33d95af6c9ade7cf0415756cc5ea9803_img.jpg) + +Figure 9.2.2.2.2-2: EM simulation setup for 3-sector site. (a) Top-down view showing three sectors (Sector 1, Sector 2, Sector 3) arranged in a triangle with a distance of 400.05mm between Sector 2 and Sector 3. (b) Side view showing the three sectors stacked vertically with a height of 300.00mm between Sector 1 and Sector 2. + +**Figure 9.2.2.2.2-2: EM simulation setup for 3-sector site** + +Figure 9.2.2.2.2-3 depicts the EM simulation results. The left hand plot shows the isolation with azimuth steering and elevation in boresight and the right hand plot with elevation steering and azimuth on boresight. The isolation between sectors is highly dependent on the beam direction. Although an “average” isolation can be given, this would mask the fact that for certain beam directions isolation is good and for others it is not good. Since the beam direction depends on the physical positions of users, advanced co-ordination of beam directions may not be possible if other constraints such as capacity and latency are to be optimized. Even with an optimization, the isolation would be less than 80dB. + +![Figure 9.2.2.2.2-3: Inter-sector isolation (between two sectors) results from EM modelling. (a) Azimuth beam steering with elevation at boresight. (b) Downtilt elevation beam steering with azimuth at boresight. Both plots show RX/TX coupling magnitude [dB] vs Frequency [GHz] for different beam directions.](efcb7264b716b845a750e9090562f601_img.jpg) + +(a) Azimuth beam steering with elevation at boresight + +(b) Downtilt elevation beam steering with azimuth at boresight + +Figure 9.2.2.2.2-3: Inter-sector isolation (between two sectors) results from EM modelling. (a) Azimuth beam steering with elevation at boresight. (b) Downtilt elevation beam steering with azimuth at boresight. Both plots show RX/TX coupling magnitude [dB] vs Frequency [GHz] for different beam directions. + +**Figure 9.2.2.2.2-3: Inter-sector isolation (between two sectors) results from EM modelling.** + +It should also be considered that there are likely to be two interfering sectors, as well as potentially other co-located BS (for example, from other operators). + +#### **Beam nulling** + +There may be some potential for beam nulling to mitigate interference between sectors. However, it is not sufficient to avoid that the power into the receiver drives the receiver into saturation for the wide area scenario. + +#### **Receiver filtering** + +Analogue filtering in the receiver is not assumed for reasons described in section 9.2.1.2.2. + +### **9.2.2.2.3 Huawei** + +On digital IC aspect, in our view, since the information of non-linear product is already got in the digital domain, and it can be exchanged between sectors within a BBU, hence digital IC can be applied for this case. + +On the achievable coupling loss in the case of co-site inter-sector gNB-gNB, RF measurements for the spatial isolation has been conducted. Figure 9.2.2.3-2 shows measurements results for two 120° sectors which is 2.5 m distance in horizontal. The curve represents the spatial isolation between a TX full power transmission of one sector to one receiver chain of the other sector. Form the measurements it can be found that the larger angle beam steering, the isolation becomes smaller. The isolation at worst case is ~76 dB. It is a test on legacy AAS BS. There are some methods can be adopted to improve the isolation for a BS capable of SBFD operation, e.g. mounting EM absorber materials next to the antenna array in the base station. ~10 dB improvement is foreseen based on our evaluations. For co-site inter-sector case better spatial isolation than RSI case is achievable. + +![A photograph of a base station tower with two antenna arrays. Two yellow rectangular boxes highlight the antennas, indicating the locations used for spatial isolation measurements.](3a6347f9ba293dba971fe22b739bdeef_img.jpg) + +A photograph of a base station tower with two antenna arrays. Two yellow rectangular boxes highlight the antennas, indicating the locations used for spatial isolation measurements. + +**Figure 9.2.2.3-1: Spatial isolation measurements** + +![A scatter plot titled 'Measured spatial isolation (dB)'. The y-axis represents isolation in dB, ranging from -90 to -70. The x-axis represents beam direction in degrees, ranging from 0 to 70. Data points are plotted for five beam directions: -60° (blue), -30° (red), 0° (green), 30° (purple), and 60° (light blue). The plot shows that as the beam direction angle increases, the measured spatial isolation generally decreases (becomes less negative). The 0° beam direction shows the lowest isolation values, while the -60° direction shows the highest isolation values.](f296a66479e113c37204a53a2133c094_img.jpg) + +A scatter plot titled 'Measured spatial isolation (dB)'. The y-axis represents isolation in dB, ranging from -90 to -70. The x-axis represents beam direction in degrees, ranging from 0 to 70. Data points are plotted for five beam directions: -60° (blue), -30° (red), 0° (green), 30° (purple), and 60° (light blue). The plot shows that as the beam direction angle increases, the measured spatial isolation generally decreases (becomes less negative). The 0° beam direction shows the lowest isolation values, while the -60° direction shows the highest isolation values. + +**Figure 9.2.2.3-2: Measurements results at different beam directions** + +#### 9.2.2.2.4 Nokia + +The co-site inter-sector interference analysis of values for FR1 Wide Area BS is provided in the summary table. + +##### **Spatial isolation techniques** + +The spatial isolation mechanisms for co-site inter-sector case are in principle similar to the self-interference case. In addition, these aspects need to be considered: + +- Element-to-element isolation is easier to manage within a single antenna enclosure, where all parameters and physical dimensions can be controlled. Isolation between sectors occurs due to unwanted radiation towards the back of the antenna, which is more difficult to control. The geometry between the antennas of different sectors can be difficult to adjust precisely, meaning that the element coupling can be difficult to predict. +- It has been suggested that EM shielding material between sectors may be used. This is not possible in all installations but may possibly be an option in some installations. The effectiveness of the EM shielding has not been studied. + +- Transmit beam nulling across different sectors is theoretically possible, but the practical implementation may be too costly since it may be necessary to calculate the beamforming vector for each subcarrier. + +### 9.2.2.3 Conclusion + +Based on the analysis on co-site inter-sector co-channel inter-subband interference provided in Section 9.2.2 for FR1 wide area BS, it can be observed that the implementation feasibility of controlling the co-site inter-sector co-channel inter-subband interference to meet the target (i.e., being less than certain level of receiver desensitization) depends on the implementation aspects including: + +- Maximum BS transmit power +- Number of co-site, co-channel sectors and the separation between them and other site constraints +- The achievable spatial isolation and use of absorbing material and choke structure depending on site constraints +- Beam nulling/isolation capability +- Frequency isolation at the TX and RX +- The digital interference suppression/cancellation capability. + +Based on the different assumptions and/or technique adoption for the above-mentioned implementations aspects, and based on 4 companies' technical inputs, companies have come to the following conclusions: + +- the implementations can achieve reasonable residual level for co-site inter-sector co-channel inter-subband interference, up to 1dB desensitization, according to 2 companies. +- the implementations are not able to achieve that because the receiver is saturated, and the RX processing is not feasible, based on co-site deployment limitation, existing technology and technology roadmaps that are viewed as viable in the current time or foreseeable future according to 2 companies. + +It should be noted that gNB-to-gNB co-channel CLI handling schemes provided in Section 8.3 have not yet been considered in concluding the implementation feasibility study for controlling the co-site inter-sector co-channel inter-subband interference. + +## 9.2.3 Co-channel inter-sub-band inter-site interference analysis + +On the feasibility and how to model inter-site gNB-gNB CLI modelling considering unwanted emission and receiver selectivity, RAN4 agree that + +- The same transmitter leakage and receiver impairment model as used for investigating gNB self-interference, but antenna isolation is replaced with inter-site isolation. +- TX leakage baseline: gNB ACLR +- Receiver impairment can be studied with gNB ACS as baseline for system level simulation and feasibility study, and further study on the possibility of improved receiver impairment performance compared to gNB ACS shall not be precluded in future RAN4 works. + +## 9.2.4 Summary + +Based on RAN4 feasibility study on FR1 wide area BS, specifically the analysis on self-interference, co-site inter-sector co-channel inter-subband interference and inter-site inter-subband interference, RAN4 concluded that: + +- For self-interference analysis, the implementation feasibility of controlling the residual interference to meet the 1dB receiver desensitization target depends on the implementation aspects mentioned in clause 9.2.1. Based on the different assumptions and/or technique adoption for the above-mentioned implementations aspects, and based on 6 companies' technical inputs, 3 companies have come to the conclusion that 1dB receiver desensitization target is achievable by self-interference cancellation capability, while other 3 companies have come to the conclusion that 1dB receiver desensitization target is not achievable or is challenging based on technology roadmaps that are viewed by the 3 companies as viable in the current time or foreseeable future. +- For co-site inter-sector co-channel inter-subband interference, that the implementation feasibility of controlling the co-site inter-sector co-channel inter-subband interference to meet the target (i.e., being less than certain level of receiver desensitization) depends on the implementation aspects mentioned in clause 9.2.2. Based on the + +different assumptions and/or technique adoption for the above-mentioned implementations aspects, and based on 4 companies' technical inputs, 2 companies have come to the conclusion that the implementations can achieve reasonable residual level for co-site inter-sector co-channel inter-subband interference, up to 1dB desensitization, while other 2 companies have come to the conclusion that the implementations are not able to achieve that because the receiver is saturated, and the RX processing is not feasible, based on co-site deployment limitation and technology roadmaps that are viewed by the 2 companies as viable in the current time or foreseeable future. It should be noted that gNB-to-gNB co-channel CLI handling schemes provided in Section 8.3 have not yet been considered in concluding the implementation feasibility study for controlling the co-site inter-sector co-channel inter-subband interference. + +- For inter-site co-channel inter-subband interference, since the feasibility is deployment-dependent, RAN4 has provided the inter-site gNB-gNB CLI modelling used for coexistence study by considering unwanted emission and receiver selectivity modelling. + +## 9.3 Feasibility of FR1 medium range BS aspects + +### 9.3.1 Self-interference analysis + +#### 9.3.1.1 Summary table for self-interference analysis + +Table 9.3.1.1-1 summarizes the analysis from different companies on the FR1 MR base station. This section is based on the self-interference analysis framework. + +**Table 9.3.1.1-1: Summary of FR1 medium range BS self-interference analysis** + +| FR1 | | | Nokia | Ericsson | | | | ZTE | Huawei | Samsung | +|-------------------------------------|---------------------------------------------------|----------------------------------------|---------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|------------------------------|---------------------------------------|------------------------|----------------------------------------|-------------------------------------------------| +| BS class | | | Medium Range BS | Medium Range (3GPP minimum requirements) | Medium range (Realistic) | Medium Range (Optimistic RX) | Medium Range (Realistic, lower power) | MR | Medium Range BS | Medium Range BS | +| BS TX Power = ① dBm | | | 36 dBm | 38 dBm | 38 dBm | 38 dBm | 35 dBm | 30 | 38 dBm | 38 dBm | +| Component capability and parameters | Frequency isolation at TX | Frequency isolation capability = ② dBc | 45 dBc | 45 dBc | 45 dBc | 45 dBc | 45 dBc | 51 | 45 | 45 dBc | +| | | Frequency isolation techniques used | Digital filtering or windowing to clean UL sub-band; DPD to suppress PA distortion | Digital filtering, CFR, DPD | | | | DPD utilized | DPD | DPD utilized | +| | Spatial isolation | Spatial isolation capability = ③ dBc | 60 dBc (if omnidirectional antennas are used, this would be less) | 65-70 dBc | 65-70 dBc | 65-70 dBc | 65-70 dBc | 60 | 80 | 80 dBc | +| | | Spatial isolation techniques used | Spatial separation between TX/RX panels; EM shielding structures between TX/RX panels | A combination of spatial isolation, chokes, absorption, mushroom EBG. 70dB is indicative average; isolation varies from around 55dB to more than 80dB | | | | TX/RX panel separation | spatial separation between TX/RX panel | TX/RX panel separation and RF barrier structure | +| | TX Beam nulling /isolation in TX sub-band = ④ dBc | | 0-5 dBc | 10 dBc
Note that the TX beam nulling reduces the variation due to beam direction, and hence spatial isolation + TX nulling can be assumed to be 80dB for most directions. | | | | 0 | 5 | 5 dBc | +| | DL EIRP impact due to beam nulling in TX sub-band | | 1 dB maximum | Up to 5dB EIRP loss, depending on beam direction | | | | N/A | Limited | Limited, ~0dB | + +| | | | | | | | | | | +|------------------------------------|------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|----------|-------------------|------|-------------------|------------------------------------------| +| | Self-interference leakage in gNB RX subband due to non-ideal TX, measured at RX ant. (Note 1) | -75 dBm/20 MHz | -87 dBm | -87 dBm | - 87 dBm | -90 dBm | -101 | -98 | -92 dBm
Note: provided by ①-②-③-⑨ dBm | +| RF IC and other tech. (before LNA) | RF IC capability and other tech. in TX sub-band = ⑤ dBc | 0 dBc | 0 dBc | 0 dBc | 0 dBc | 0 dBc | 20 | N/A | 0 dBc | +| | RF IC capability and other tech. in RX sub-band = ⑧ dBc | 0 dBc | 0 dBc | 0 dBc | 0 dBc | 0 dBc | 0 | N/A | 0 dBc | +| | RF IC techniques and other tech. (before LNA) | None apply due to feasibility concerns (depends on the number of TRX) | None; see section 9.3.1.2.2 for analysis. | | | Subband filtering | | N/A | N/A | +| | Impacts to RX sensitivity (due to e.g. insertion losses) due to RF IC or other techniques before LNA | N/A dBc | >=5dBc if e.g. filtering or analogue IC would be applied. | | | N/A | | N/A | | +| | Self-Interference signal in gNB TX subband, measured at the input of LNA (Note 1) | -24 dBm to -29 dBm depending on TX beam | -42 dBm | -42 dBm | -42 dBm | -45 dBm | -50 | -47 | -47 dBm
Note: provided by ①-③-④-⑤dBm | +| Blocker Suppression at RX | Frequency isolation capability ⑥ dBc | 0 dBc | 0 dBc | | | 60 | | digital filtering | 40 dBc | +| | Frequency isolation techniques | None apply due to feasibility concerns | Digital IC of TX. The impact of scattering / reflection in the environment has not been considered. Digital baseband combining may improve self-interference suppression, at the cost of suppression of other interferers and RX beamforming gain. Reference scenarios are needed to assess the overall potential from RX baseband combining. | | | Digital Filtering | | digital filtering | Filtering | + +| | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------|---------------------------|----------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|----------|-----------|----------|------------|-------------------------------------------| +| RX IMD | Rx IIP3 capability (dBm) | -10 dBm at maximum sensitivity; +10 dBm at maximum linearity (at NF penalty) | -27.6 dBm | -17.6 dBm | -13 dBm | -17.6 dBm | -5 | -5 | -20 | +| | Rx IM3 contribution (dBm) | Negligible | -70.8 dBm | -90.8 dBm | -100 dBm | -100 dBm | -140 | -131 | -101dBm | +| | Other RX | Any other RX impacts if significant (e.g. ADC noise, phase noise etc.) | Negligible | No significant issues for medium range BS power level other than mentioned above | | | Marginal | negligible | N/A | +| Self-Interference signal in gNB RX subband caused by non-ideal RX selectivity, gain-normalized (Note 1, 2) | | -74 to -79 dBm/20MHz (at 50 dBc ACS) | -70.8 dBm | -90.8 dBm | -100 dBm | -100 dBm | -110 | negligible | -87 dBm
Note: provided by ①-③-④-⑤-⑥dBm | +| RX Beam nulling /isolation in RX sub-band = ⑨ dBc | | 0 dBc | 0-10 dBc
RX beam nulling is in effect part of the digital baseband combining. See “frequency isolation techniques” | | | | 0 | 5 | 5 dBc | +| RX sensitivity degradation caused by RX beam nulling | | 0 dBc; should not assume further UL beamforming loss to maintain any UL gains | | | | | N/A | Limited | Limited, ~0dB | +| Digital IC = ⑦ dBc | | 5-10 dBc (Improved linearization could provide here additional 5dB. Digital IC depends on the implementation ) | 10-15 dBc (Transmitter) | | | | 20 | 10 | 10 | +| Overall RSIC capability (Note 1) | | 110 dBc to 120 dBc | 109 dBc | 128-138 dBc | 135 dBc | 134 dBc | 130.5 | 146 | 134 dBc | + +| | | | | | | | | | +|----------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------|-------------|-------------|-------|----------------|------------------| +| Noise floor ⑩dBm | -92 dBm/CBW (20 MHz) | -90 dBm/CBW | -90 dBm/CBW | -90 dBm/CBW | -90 dBm/CBW | -91.0 | -90 dBm/20 MHz | -90 dBm/CBW | +| Residual Interference budget with 1 dB desens target (⑪dBm=⑩dBm-6dB) | -98 dBm | -96 dBm | -96 dBm | -96 dBm | -96 dBm | -97.0 | -96 dBm | -96dBm | +| Required RSIC budget (①-⑪dBc) | 134 dBc | 134 dBc | 134 dBc | 134 dBc | 131 dBc | 127.0 | 134 | 134 dBc | +| SBFD configuration | DUD (40/20/40 MHz) | 40-20-40 | | | | | 40-20-40 | DUD(40-20-40MHz) | +| Guardband assumption (if exist) | 5 RB (1.8 MHz) | 5 PRB | | | | | Existing SU | 5 PRB | +| bandwidth over which suppression is achieved | | <300MHz | | | | | | 100MHz | +| Others | | | | | | | | | +| | Note 1: Relevant metrics are derived from other parameters for checking purpose.
Note 2: The relevant metric is gain-normalized, with reference point assumed to be at RX antenna.
Note 3: The notations ①②③④⑤⑥⑦⑧⑨⑩⑪ are used to indicate the decimal values of the corresponding metrics. | | | | | | | | + +### 9.3.1.2 Feasibility study on self-interference + +#### 9.3.1.2.1 Nokia + +Table 9.3.1.1-1 presents the company's view on the self-interference mitigation analysis for a medium range base station with 36 dBm total output power. The RSIC capability corresponds to 110 to 120 dBc which is achieved using a combination of spatial isolation (60 dBc), Tx beam nulling (0-5 dB, only applicable in the Tx subband), frequency separation (45 dBc), and digital IC techniques (5-10 dBc). Under such considerations, the self-interference observed in the 20 MHz UL subband is dominated by transmitter ACLR and receiver selectivity with a magnitude of approximately -74 dBm prior to digital IC and up to -84 dBm after digital IC, while the noise floor is -91.0 dBm. This results in a non-negligible desensitization of the receiver which would degrade more or less the system performance depending on the deployment ISD, UL link budget, etc. + +The assumptions and corresponding justification are presented below with focus on the main differences with respect to the wide-area analysis in Section 9.2.1.2.6. + +#### Spatial isolation + +The same techniques to achieve spatial isolation in FR1 wide-area base stations can be applied to medium-range base stations as well. Nevertheless, the following differences should be noted: + +- Medium range BS have typically smaller form-factor than the wide-area BS, e.g. down to 30x30x10 cm. The absolute physical separation between Tx and Rx panels needs to be smaller than for wide-area BS to keep the relative increase of the BS enclosure to a reasonable level. +- Medium range base stations may have a lower number of TRXs as compared to wide-area base stations. This could result in higher coupling per Rx chain. + +Considering these two aspects, 60 dBc of spatial isolation is considered. + +#### TX Beam nulling / isolation in TX sub-band + +With only a relatively low number of TRXs, the potential of Tx beam nulling techniques is reduced. Only 0-5 dBc is considered, under the assumption of at most 1 dB of EIRP loss. + +#### RF IC and other tech. (before LNA) + +If the number of TRX is significantly lowered compared to massive MIMO, there is a possibility for RF IC to be feasible. However, this all depends on the implementation. With a low number of TRXs, the spatial isolation to a single RX port would likely be lower than for an implementation with a large number of TRXs – possibility necessitating RF cancellation paths to compensate. The overall SIC capability would be similar in both cases. + +#### Frequency isolation at RX + +This all depends on the implementation. + +#### Digital IC + +If the number of TRX is significantly lowered compared to massive MIMO, there is a possibility for digital IC to be feasible. However, this all depends on the implementation. Digital IC can be achieved by improving the DPD in the transmitter side to reduce the unwanted transmitter leakage components that fall in the UL subband, while receiver-side digital IC techniques are also required to suppress the self-interference signal in gNB RX subband caused by non-ideal RX selectivity. + +#### 9.3.1.2.2 Ericsson + +For the medium range BS, four implementation scenarios are presented in Table 9.3.1.1-1. In the first scenario, the RF is assumed to perform at the absolute minimum needed to meet the 3GPP requirements. In the second scenario, an improved RF performance that is still likely to be a reasonable commercial implementation is considered (called realistic). Two further scenarios are considered; one in which the receiver linearity is assumed to exceed the realistic scenario, which could lead to more significant compromises in power consumption, size etc. The other scenario is one in which realistic RF performance is assumed, but the transmitter is assumed to be 3dB lower than the maximum transmitter limit in power. + +It can be observed that for a BS only built to meet 3GPP minimum requirements, the receiver performance is not sufficient to operate SBFD without significant desensitization. To operate SBFD, either receiver digital processing is needed with the realistic assumptions (the feasibility of achieving sufficient gain with such processing depends on the wider deployment scenario), or somewhat better receiver performance, or lower transmit power than the 3GPP maximum limit. + +An explanation for the assumptions in the table are provided below. + +### **Spatial isolation and beam nulling** + +For a medium range size AAS array, simulations show a spatial isolation of around 65-70dB, depending on the beam direction. With beam nulling, the isolation can be lifted to around 80dB, with in general less than 1dB cost in the downlink. + +### **Analogue interference cancellation** + +With a smaller array size, analogue interference cancellation may be more feasible for a MR BS than for a WA BS. However, the number of interconnections is still significant. Furthermore, analogue IC requires that the same beam steering is applied on all RBs and all carriers, preventing sub-band precoding and multi-carrier operation. Also, in general analogue IC is not needed to avoid receiver saturation. Analogue IC has not been taken into account. + +### **Analogue filtering** + +Analogue filtering is not realistic in an implementation for the same reasons described for the WA BS in section 9.2.1.2.2. Furthermore, analogue filtering is not really needed as the input power level to the MR receiver is generally manageable. + +### **Digital interference cancellation and receiver processing** + +Digital sampling of the TX leakage interference and subtraction at RX is more feasible for a MR BS than for a WA BS. An alternative to digital cancellation of TX leakage could be an improved PA linearization at the transmitter side. The possibility of either improved PA linearization or digital IC is captured as 15dB digital IC. + +At the receiver, the interference co-variance matrix can be estimated and the receiver MMSE-IRC algorithm can mitigate interference. The extent to which the receiver can mitigate interference depends on the overall interference structure, which depends on the profile of interfering UEs, other sectors and other base stations as well as the fading channel profiles in the environment. The study has not considered the deployment environment when considering feasibility of self-interference suppression, and hence a specific number for the suppression by means of receiver processing is not provided. However, it is noted that for the MR to operate with the “realistic” receiver and the maximum allowed transmit power, several dB of suppression would need to be achieved by digital processing. + +#### **9.3.1.2.3 ZTE** + +Table 9.3.1.1-1 presents the company’s view on the self-interference mitigation analysis for a medium range base station. + +#### **9.3.1.2.4 Samsung** + +Table 9.3.1.1-1 presents the company’s view on the self-interference mitigation analysis for a medium range base station. + +#### **9.3.1.2.5 Huawei** + +Table 9.3.1.1-1 presents the company’s view on the self-interference mitigation analysis for a medium range base station. + +#### **9.3.1.3 Conclusion** + +Based on the self-interference analysis provided in Section 9.3.1 for FR1 medium range BS, it can be observed that the implementation feasibility of controlling the residual interference to meet the 1dB receiver desensitization target depends on the implementation aspects, including: + +- Maximum BS transmit power +- Spatial isolation capability + +- Beam nulling/ isolation capability +- Blocker suppression at the RX +- Frequency isolation at the TX and RX +- The digital interference suppression/ cancellation capabilities + +Based on the different assumptions and/ or techniques adopted for the above-mentioned implementation aspects, based on 5 companies’ technical inputs, companies have come to the following conclusions: + +- It is feasible to achieve the 1 dB desensitization target according to 4 companies. +- It is not feasible to achieve the 1 dB desensitization target for a base station that strictly meets the RAN4 minimum requirements and/or operates with the maximum BS transmit power according to 2 companies. +- Note: Among 5 companies, 1 company shows different feasibility results based on different assumptions. + +### 9.3.2 Co-channel inter-sub-band co-site inter-sector interference analysis + +#### 9.3.2.1 Summary table for co-channel inter-subband co-site inter-sector interference analysis + +Table 9.3.2.1-1 summarizes the analysis on the co-channel inter-subband co-site inter-sector interference for FR1 MR base station. This section is based on the co-channel inter-subband co-site interference analysis framework. + +**Table 9.3.2.1-1: Summary of FR1 medium range BS co-channel inter-subband co-site inter-sector interference analysis** + +| FR1 | | | Ericsson | Nokia | Samsung | +|-------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------|----------------------------------------------------------------|------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------| +| BS class | | | Medium Range BS | Medium Range BS | Medium Range BS | +| BS TX Power = ① dBm | | | 38 dBm | 36 dBm | 38 dBm | +| Number of co-site co-channel sectors considered | | | 2 | 2 | 1 | +| Component capability and parameters | Frequency isolation at TX | Frequency isolation capability = ② dBc | 45 dBc | 45 dBc | 45 dBc | +| | | Frequency isolation techniques used | DPD, CFR | DPD, digital filtering | DPD utilized | +| | Spatial isolation | Co-channel Co-site Inter-sector Spatial isolation capability = ③ dBc | 75-90 dBc (Varies depending on scheduled beam directions) | 60-80 dBc | 90dBc | +| | | Co-channel Co-site Inter-sector Spatial isolation techniques used | Typical site layout with around 400mm between sectors | Spatial separation between TX/RX panel; cross polarization | Depends on practical deployment, and additional isolation distance for deployment can provide extra spatial isolation required. | +| | TX Beam nulling /isolation of inter-sector interference in TX sub-band = ④ dBc | | 0 dBc | 0 dBc | 5 dBc | +| | DL EIRP impact due to beam nulling in TX sub-band (considering all nulling for self- and inter-sector interference) | | 0 dB | N/A | Neglectable | +| | Interference leakage in gNB RX subband due to non-ideal TX, measured at RX ant. due to inter-sector interference (Note 1) | | -94 to -79 dBm (Varies depending on scheduled beam directions) | -92 dBm to -72 dBm | -102 dBm | +| | Interference signal in gNB TX subband, measured at the input of LNA (Note 1) due to inter-sector interference | | -49 to -34 dBm (Varies depending on scheduled beam directions) | -44 dBm to -24 dBm | -52dBm | +| | Blocker Suppression | Frequency isolation capability | 0 dBc | 0 dBc | 40 dBc | + +| | | | | | | | | +|---------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------|------------------------------------------------------------------------|--|--| +| at RX | ⑥ dBc | | | | | | | +| | Frequency isolation techniques | | Filtering prior to the LNA would imply the need for the BS hardware to be specifically tuned to the SBFD carrier and no multi-carrier possibilities. Filter would be bulky to integrate into an AAS. Insertion loss would degrade sensitivity.

Filtering in-between LNA stages could increase linearity, but still a large number of filters to incorporate multi-carrier configurations would not be feasible. Loss of integration would cause increases in size, energy etc. | Digital filtering, FFT frequency selectivity | Digital filtering can provide frequency isolation capability required. | | | +| | RX IMD | Rx IIP3 capability (dBm) | -13 dBm ("Optimistic" value) | Included in the NF model | -20dBm | | | +| | | Rx IM3 contribution (dBm) | -101 dBm to -74 dBm | | Not a significant contributor on the gNB Rx capability | | | +| | Other RX | Any other RX impacts if significant (e.g. ADC noise, phase noise etc.) | (IM3 due to inter-sector interference only, assuming the presence of both self- and inter-sector interference in the receiver) | | N/A | | | +| | Interference signal in gNB RX subband caused by non-ideal RX selectivity, gain-normalized due to co-site inter-sector co-channel interference only (Note 1, 2) | | -101 dBm to -74 dBm (Additional interference due to inter-sector interference only) (Depending on beam direction) | -90 dBm to -70 dBm | -97 dBm | | | +| | RX Beam nulling /isolation in RX sub-band = ⑨ dBc | | 0 dB | 0 dB | 5 dB | | | +| | RX sensitivity degradation caused by RX beam nulling | | 0 dB | N/A | Neglectable | | | +| | Digital processing interference suppression capability | | No digital cancellation between sectors. | 0 dB | 0 – 10dB depends on adoption of digital cancellation between sectors | | | +| | Total interference in RX SB (dBm) (Note 2) | | -94 To -74 dBm (Additional interference due to inter-sector interference only) (Depending on beam direction) | -90 dBm to -70 dBm (Self-interference not considered here) | -96dBm to -106dBm | | | +| Noise floor @dBm | | | -96 dBm/CBW | -96 dBm/ 20 MHz | -90 dBm/CBW | | | +| Calculated Desensitization (dB) | | | 4 to 22 dB | 6 to 26 dB | 1dB or neglectable | | | + +| | (Depending on beam direction.
Additional degradation due to inter-sector interference only) | | (depending on the adoption of digital cancellation) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------|------------------|-----------------------------------------------------| +| SBFD configuration | 40-20-40 MHz | 40 – 20 – 40 MHz | 40-20-40 MHz | +| Guardband assumption (if exist) | 5 PRB. | 5 PRB | 5 PRB. | +| bandwidth over which suppression is achieved | >300 MHz | | 20MHz | +| Others | | | | +| Note 1: Relevant metrics are derived from other parameters for checking purpose.
Note 2: The relevant metric is gain-normalized, with reference point assumed to be at RX antenna.
Note 3: The notations ①②③④⑤⑥⑦⑧⑨⑩⑪ are used to indicate the decimal values of the corresponding metrics.
Note 4: The abbreviation CSSI refers to co-site co-channel inter-sector interference in this table | | | | + +### 9.3.2.2 Feasibility study on co-channel inter-subband co-site inter-sector interference analysis + +#### 9.3.2.2.1 Nokia + +Medium range base stations are commonly deployed with omnidirectional antennas, but some deployments use directional antennas also with the target to boost coverage or capacity. In case of 3-sector site deployment with directional antennas, the techniques described in Section 9.2.2.2.4 apply here as well, although it is important to note that it may be more difficult to add large horizontal separation between sectors if the site footprint is small. + +In a case a 3-sector site deployment are considered, our analysis is presented in table 9.3.2.1-1 above. We considered the same spatial isolation as considered in the urban macro cell case. As our input to the table shows, the total interference in RX subband is between -90 dBm and -70 dBm, which is already above the noise floor and would cause desensitization of the receiver. It is also important to note that this analysis does not consider the self-interference, so in reality the desensitization would be greater. + +#### 9.3.2.2.2 Ericsson + +Table 9.3.2.1-1 presents an analysis of the inter-sector interference effects for medium range FR1 BS. The table considers the “optimistic” receiver considered in section 9.3.2.1.2; i.e., a receiver that is more capable than in a current BS. If the “realistic” receiver would be considered, then the indicated desensitizations would be greater. + +The level of inter-sector interference only varies depending on the beam direction from around 4dB to 22dB. The total desensitization would include self-interference and would be around 1dB greater. There may be some potential to increase inter-sector isolation using TX beam nulling (not shown in the table), however clearly mitigating inter-sector interference will be a challenge also for MR BS. + +#### Inter-sector isolation + +Isolation between sectors has been simulated using electromagnetic simulations in [68] with an assumption of 400mm sector separation. The isolation varies to some degree with separation, but not to an extent that would change the overall results. For most practical site deployments, addition of materials between sectors is not likely to be feasible (and may reduce network performance). + +The isolation between sectors is highly dependent on the beam direction. Although an “average” isolation can be given, this would mask the fact that for certain beam directions isolation is good and for others it is not good. + +#### Beam nulling + +There may be some potential for beam nulling to mitigate interference between sectors. To achieve complete isolation between sectors, more than 20dB beam nulling would be needed. + +#### Receiver filtering + +Analogue filtering in the receiver is not assumed for reasons described in section 9.3.2.1.2. + +### 9.3.2.2.3 Samsung + +For FR1 medium range BS, it is not necessarily to require co-site multi-sector deployment while omni-directional antenna could also be the deployment option. And the co-site inter-sector interference is only present for the case where directional antennas are used. + +For the case of 3-sector site deployment with directional antenna, Table 9.3.2.1-1 presents the company's view on the co-site inter-sector interference analysis for a medium range base station. Similar to FR1 wide area BS counterpart, the achievable antenna isolation is key factor to analyze the co-site inter-sector co-channel gNB-gNB CLI. It has been demonstrated that even without analog subband filter implemented, the residual co-site inter-sector interference can be well controlled with proper implementation of spatial isolation, frequency isolation, beam nulling, and optional digital cancellation for FR1 medium range BS. + +### 9.3.2.3 Conclusion + +Sectorized deployments of medium range BS are by no means universal. Dependent on the deployment needs, single sector MR BS are often deployed at least in some locations. In case a three sector deployment is used, based on the co-site inter-sector co-channel inter-sub-band interference analysis in Section 9.3.2, it can be observed that the implementation feasibility of controlling the co-site inter-sector co-channel inter-subband interference to meet the target (i.e., being less than certain level of receiver desensitization) depends on the implementation aspects including: + +- Number of co-site, co-channel sectors and the separation between them and other site constraints +- The achievable spatial isolation and use of absorbing material and choke structure depending on site constraints +- Beam nulling/isolation capability +- Frequency isolation at the TX and RX +- The digital interference suppression/cancellation capability. + +For the case with multiple co-site sectors, based on the different assumptions and/or technique adoption for the above-mentioned implementations aspects, and based on 3 companies' technical inputs: + +- The total interference caused by two co-site sectors would be above the noise floor, causing a desensitization of the receiver, according to 2 companies. +- The residual co-site inter-sector interference can be controlled, causing reasonable residual self-interference, causing up to 1 dB desensitization of the receiver, according to 1 company. + +It should be noted that gNB-to-gNB co-channel CLI handling schemes provided in Section 8.3 have not yet been considered in concluding the implementation feasibility study for controlling the co-site inter-sector co-channel inter-subband interference. + +### 9.3.3 Co-channel inter-sub-band inter-site interference analysis + +On the feasibility and how to model inter-site gNB-gNB CLI modelling considering unwanted emission and receiver selectivity, RAN4 agree that + +- The same transmitter leakage and receiver impairment model as used for investigating gNB self-interference, but antenna isolation is replaced with inter-site isolation. +- TX leakage baseline: gNB ACLR +- Receiver impairment can be studied with gNB ACS as baseline for system level simulation and feasibility study, and further study on the possibility of improved receiver impairment performance compared to gNB ACS shall not be precluded in future RAN4 works. + +### 9.3.4 Summary + +Based on RAN4 feasibility study on FR1 medium range BS, specifically the analysis on self-interference, co-site inter-sector co-channel inter-subband interference and inter-site inter-subband interference, RAN4 concluded that: + +- For self-interference analysis, the implementation feasibility of controlling the residual interference to meet the 1dB receiver desensitization target depends on the implementation aspects mentioned in clause 9.3.1. Based on + +the different assumptions and/or technique adoption for the above-mentioned implementation aspects, based on 5 companies' technical inputs, companies have come to the following conclusions: + +- 1dB receiver desensitization target is achievable according to 4 companies. +- 1dB receiver desensitization target is not achievable for a base station that strictly meets the RAN4 minimum requirements and/or operates with the maximum BS transmit power according to 2 companies. +- Note: Among 5 companies, 1 company shows different feasibility results based on different assumptions. +- Sectorized deployments of medium range BS are by no means universal. Dependent on the deployment needs, single sector MR BS are often deployed at least in some locations. In case a three sector deployment is used, for co-site inter-sector co-channel inter-subband interference, it can be observed that the implementation feasibility of controlling the co-site inter-sector co-channel inter-subband interference to meet the target (i.e., being less than certain level of receiver desensitization) depends on the implementation aspects mentioned in clause 9.3.2. Based on the different assumptions and/or technique adoption for the above-mentioned implementations aspects, and based on 3 companies' technical inputs companies concluded that: + - The total interference caused by two co-site sectors would be above the noise floor, causing a desensitization of the receiver, according to 2 companies. + - The residual co-site inter-sector interference can be controlled, causing reasonable residual self-interference, causing up to 1 dB desensitization of the receiver, according to 1 company. +- It should be noted that gNB-to-gNB co-channel CLI handling schemes provided in Section 8.3 have not yet been considered in concluding the implementation feasibility study for controlling the co-site inter-sector co-channel inter-subband interference. +- For inter-site co-channel inter-subband interference, since the feasibility is deployment-dependent, RAN4 has provided the inter-site gNB-gNB CLI modelling used for coexistence study by considering unwanted emission and receiver selectivity modelling. + +## 9.4 Feasibility of FR1 local area BS aspects + +### 9.4.1 Self-interference analysis + +#### 9.4.1.1 Summary table for self-interference analysis + +Table 9.4.1.1-1 summarizes the self-interference analysis results from companies. + +Table 9.4.1.1-1: SI feasibility study for FR1 Local Area BS + +| FR1 | | | Ericsson (preliminary) | | ZTE | CATT | Huawei | Nokia | Samsung | +|-------------------------------------|-----------------------------------------------------------------------------------------------|---------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|------------------------------|------------------------|--------------------------------------------------------------------------------------|--------------------------------------------------|---------------------------------------------------------------------------------------|-------------------------------------------------| +| BS class | | | Local Area BS (3GPP minimum) | Local Area BS (Realistic RX) | LA | LA | LA | Local Area BS | Local Area BS | +| BS TX Power = ① dBm | | | 24 | 24 | 23 | 24 | 24 | 23 | 24 | +| Component capability and parameters | Frequency isolation at TX | Frequency isolation capability = ② dBc | 45 | 45 | 45 | 45 | 45 | 45 | 45 | +| | | Frequency isolation techniques used | Digital filtering, CFR, DPD | | DPD utilized | CFR | DPD | Digital filtering or windowing to clean UL sub-band; DPD to suppress PA distortion | DPD utilized | +| | Spatial isolation | Spatial isolation capability = ③ dBc | 70 | 70 | 60 | 70 | 70 | 60 (if omnidirectional antennas are used, this would be less) | 80 | +| | | Spatial isolation techniques used | Physical distance, isolation structures | | TX/RX panel separation | TX/RX panel separation, isolation structures, isolation material, cross polarization | Spatial separation between TX panel to single RX | Spatial separation between TX/RX panels; EM shielding structures between TX/RX panels | TX/RX panel separation and RF barrier structure | +| | TX Beam nulling /isolation in TX sub-band = ④ dBc | | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | DL EIRP impact due to beam nulling in TX sub-band | | TX beam nulling not assumed due to array size | | N/A | TX Beam nulling is not assumed due to the array size | N/A | TX Beam nulling is not assumed due to the array size | N/A | +| | Self-interference leakage in gNB RX subband due to non-ideal TX, measured at RX ant. (Note 1) | | -91 | -91 | -101 | -104.01 | -97 | -88
(①-②-③-④-
$10^{\circ}\log_{10}(80/20)$ ) | -101
Note: provided by ①-②-③-⑨ | +| | RF IC and other tech. (before LNA) | RF IC capability and other tech. in TX sub-band = ⑤ dBc | 0 | 0 | 0 | 0 | N/A | 0 | 0 | +| | | RF IC capability and other tech. in RX sub-band = ⑧ dBc | 0 | 0 | 0 | 0 | N/A | 0 | 0 | +| | | RF IC techniques and other tech. (before LNA) | Analogue IC could be considered for this case, but is restrictive on pre-coding and multi-carrier. Digital IC has instead been | | subband filtering | 0 | N/A | 0 | N/A | + +| | | | | | | | | | | +|---------------------------|----------|------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------|------------------------------|-------------------|------------------------------|------------------------------------| +| | | | assumed. | | | | | | | +| | | Impacts to RX sensitivity (due to e.g. insertion losses) due to RF IC or other techniques before LNA | 0 | 0 | 0 | 0 | N/A | 0 | N/A | +| | | Self-Interference signal in gNB TX subband, measured at the input of LNA (Note 1) | -46 | -46 | -50 | -46 | -46 | -37 | -56
Note: provided by ①-③-④-⑤ | +| Blocker Suppression at RX | | Frequency isolation capability ⑥ dBc | xxx dBc | | 60 | 55 | 60-80 | | 40 | +| | | Frequency isolation techniques | Digital IC of TX. The impact of scattering / reflection in the environment has not been considered. It is assumed that RX ACS is very large due to time alignment and achieving orthogonality between the TX and RX signals in the digital domain. | | Digital Filtering | Digital filter for ACS | Digital filtering | | Digital filtering | +| | RX IMD | Rx IIP3 capability (dBm) | -24.6 | -10 | -5 | -16 | -5 | -10 | -20 | +| | | Rx IM3 contribution (dBm) | -88.8 | Negligible | -140 | -106 | -128 | Negligible | -128 | +| | Other RX | Any other RX impacts if significant (e.g. ADC noise, phase noise etc.) | No other significant impacts other than those mentioned above | | Marginal | No other significant impacts | negligible | No other significant impacts | N/A | +| | | Self-Interference signal in gNB RX subband caused by non-ideal RX selectivity, gain-normalized (Note 1, 2) (dBm) | -88.8 | -110 | -110 | -101 | negligible | -87 (at 50 dB ACS) | -96
Note: provided by ①-③-④-⑤-⑥ | +| | | RX Beam nulling /isolation in RX sub-band = ⑨ dBc | 0-3 dBc
RX beam nulling is in effect part of the digital baseband | | 0 | 0 | N/A | 0 | 0 | + +| | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------|----------|----------------|------------|------------------| +| | | combining. Digital baseband combining may improve self-interference suppression, effectively at the cost of suppression of other interferers and RX beamforming gain. Reference scenarios are needed to assess the overall potential from RX baseband combining. | | | | | | | +| | | RX sensitivity degradation caused by RX beam nulling | | N/A | | N/A | | N/A | +| | | Digital IC = ⑦ dBc | | 15 dBc on transmitter | 20 | 10 | N/A | 5 to 10 | +| Overall RSIC capability (Note 1) | | 112 dBc | 128 dBc | 130.5 | 122.33 | 121 | 110 to 115 | 129 | +| Noise floor @dBm | | -87 dBm/CBW | -87 dBm/CBW | -91.0 | -87.99 | -87 dBm/20 MHz | -91.0 | -87 | +| Residual Interference budget with 1 dB desens target (⑪ dBm=@dBm-6dB) | | -93 dBm | -93 dBm | -97.0 | -93.99 | -93 dBm | -97.00 | -93 | +| Required RSIC budget (①-⑪ dBc) | | 117 dBc | 117 dBc | 127.0 | 117.99 | 117 | 120.0 | 117 | +| SBFD configuration | | 40-20-40 | | 40-20-40 | 40-20-40 | 40-20-40 | 40-20-40 | DUD(40-20-40MHz) | +| Guardband assumption (if exist) | | 5 PRB | | | | Existing SU | 5 PRB | 5 PRB | +| bandwidth over which suppression is achieved | | <300MHz | | | | | | 20MHz | +| Others | | The conclusion does not take into account interference increase due to scattering effects, or the possibility for receiver algorithms to mitigate scattering, inter-sector and inter-site and self-interference (reference scenarios needed). | | | | | | | +| Note 1: Relevant metrics are derived from other parameters for checking purpose.
Note 2: The relevant metric is gain-normalized, with reference point assumed to be at RX antenna.
Note 3: The notations ①②③④⑤⑥⑦⑧⑨⑩⑪ are used to indicate the decimal values of the corresponding metrics. | | | | | | | | | + +## 9.4.1.2 Feasibility study on self-interference + +### 9.4.1.2.1 Ericsson + +The self-interference suppression expectations for the LA BS class are provided in table 9.4.1.1-1. Two examples are provided. The first is an LA BS with RF performance just enough to meet 3GPP minimum requirements. The second is an LS BS with improved receiver performance, but still likely sufficient for a commercially viable solution. + +The table suggests that, depending on variation in the achievable spatial isolation, some degree of improved receiver and/or digital cancellation may be needed for LA SBFD. However, in general self-interference suppression appears feasible. + +#### Spatial isolation and beam nulling + +The spatial isolation for LA is more difficult to quantify, as the array size and form-factor for a LA BS may vary significantly. LA SBFD could even be operated by placing TX and RX LA base stations at some distance. 70dB isolation has been assumed, and obviously the conclusions may vary if a smaller isolation is achieved. Beam nulling is not assumed, since a small array size is assumed. + +#### Analogue interference cancellation + +Analogue interference cancellation is more feasible for a LA BS with a smaller array size. The drawback would be the need to beamform on the same way on all RB and all carriers for a LA BS. Potentially analogue IC could be considered if the isolation for a particular design would be substantially less than 70dB. + +#### Analogue filtering + +Analogue filtering is not really needed for a LA BS due to the lower power in the TX sub-bands. + +#### Digital interference cancellation and receiver processing + +Digital sampling of the TX leakage interference and subtraction at RX is feasible for a LA BS. An alternative to digital cancellation of TX leakage could be an improved PA linearization at the transmitter side. The possibility of either improved PA linearization or digital IC is captured as 15dB digital IC. + +Receiver combining could also potentially mitigate some interference although with a smaller array size, the degrees of freedom with which to do so would be lower than other BS classes. + +### 9.4.1.2.2 CATT + +In SI capability analysis, the following techniques are used, + +- CFR is used to improve equipment efficiency, DPD is used for high power equipment to optimize ACLR. +- Tx antennas panel and Rx antennas panel are separate, there are some isolation material between them, and cross polarization is also used. +- Digital filter is used to resolve the adjacent sub-band (i.e. TX subband) interference issue. +- Digital IC is used to reduce interference in the UL sub-bands. + +From the analysis in Table 9.4.1.1-1, the following capabilities are needed, + +- Frequency isolation capability of frequency isolation at TX is 45dB +- Spatial isolation is 70dB +- ACS is 55dBc +- IIP3 is -16dBm +- Digital IC is 10dB + +The above capabilities except frequency isolation are improved compared with legacy LA BS, but it's feasible from implementation point of view. + +#### 9.4.1.2.3 Nokia + +The Nokia input in the Table 9.4.1.1-1 presents the company's view on the self-interference mitigation analysis for a local area base station with 24 dBm total output power. The RSIC capability corresponds to 110 to 115 dBc for the Rx which is achieved using a combination of spatial isolation (60 dBc), frequency separation (45 dBc), and digital IC techniques (5-10 dBc). Under such considerations, the self-interference observed in the 20 MHz UL subband is dominated by transmitter ACLR and receiver selectivity with a combined magnitude of approximately -85 dBm prior to digital IC and -90 dBm to -95 dBm after digital IC, while the noise floor is -91.0 dBm. Even though there is a small desensitization of the receiver, it is feasible to operate the base station with acceptable performance as the coverage is not the primary target of local area deployments where the UL link budget and received UL power is generally very high. + +A detailed description of some of the key assumptions is provided below. + +##### **Spatial isolation and beam nulling** + +Approximately 60 dB of spatial isolation can be achieved for ceiling- or wall-mounted base stations with directive antenna radiation patterns although at the expense of larger form-factor to reach sufficient physical separation between Tx and Rx. For typical LA base stations with omni-directional antennas, the spatial isolation would be significantly lower, e.g., 30 dB or less, thus SBFD operation would be much more challenging or potentially unfeasible. + +Tx beam nulling is not assumed due to relatively low number of TRXs. + +##### **Digital Interference cancellation techniques** + +Since the number of TRX is significantly lowered compared to mMIMO, there is a possibility for digital IC to be feasible. Digital IC can be achieved by improving the DPD in the transmitter side to reduce the unwanted transmitter leakage components that fall in the UL subband, while receiver-side digital IC techniques are also required to suppress the self-interference signal in gNB RX subband caused by non-ideal RX selectivity. + +#### 9.4.1.2.4 ZTE + +Table 9.4.1.1-1 presents the company's view on the self-interference mitigation analysis for a local area base station. + +#### 9.4.1.2.5 Huawei + +Table 9.4.1.1-1 presents the company's view on the self-interference mitigation analysis for a local area base station. + +#### 9.4.1.3 Conclusion + +Based on the feasibility study on self-interference in Section 9.4.1.2 and the summary table provided in Section 9.4.1.1, it can be concluded that with the proper implementation of component techniques including spatial isolation, frequency isolation, beam nulling, digital IC or a combination of these, the SBFD residual self-interference for FR1 LA BS can be controlled to the level of 6dB below the noise floor, which results in 1dB sensitivity degradation. + +### 9.4.2 Co-channel inter-sub-band inter-site interference analysis + +On the feasibility and how to model inter-site gNB-gNB CLI modelling considering unwanted emission and receiver selectivity, RAN4 agree that + +- The same transmitter leakage and receiver impairment model as used for investigating gNB self-interference, but antenna isolation is replaced with inter-site isolation. +- TX leakage baseline: gNB ACLR +- Receiver impairment can be studied with gNB ACS as baseline for system level simulation and feasibility study, and further study on the possibility of improved receiver impairment performance compared to gNB ACS shall not be precluded in future RAN4 works. + +### 9.4.3 Summary + +For self-interference of FR1 LA BS, it can be concluded that the SBFD self-interference 1dB sensitivity degradation is achievable. It is assumed that LA scenarios are not sectorized deployments. + +For inter-site co-channel inter-subband interference, since the feasibility is deployment-dependent, RAN4 has provided the inter-site gNB-gNB CLI modelling used for coexistence study by considering unwanted emission and receiver selectivity modelling. + +In summary, from implementation point of view, it is feasible for FR1 LA SBFD BS. + +## 9.5 Feasibility of FR2-1 BS aspects + +### 9.5.1 Self-interference analysis + +#### 9.5.1.1 Summary table for self-interference analysis + +The self-interference analysis from companies' inputs for FR2-1 SBFD-capable gNB are summarized in Table 9.5.1.1-1. Both self-interference leakage in gNB RX sub-band due to non-ideal TX and Self-Interference signal in gNB RX sub-band caused by non-ideal RX selectivity are studied in the analysis framework. The self-interference cancellation techniques including spatial isolation, frequency isolation, beam nulling and digital are considered. + +**Table 9.5.1.1-1: self-interference analysis** + +| FR2-1 | | Samsung | Huawei | Qualcomm | Ericsson | | | Nokia | +|-------------------------------------|-----------------------------------------------------------------------------------------------|----------------------------------------|-------------------------------------------------|-------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------|-----------------------------------------------------------------------|---------|----------------------------------------------------------------------------------| +| BS class | | FR2-1 BS | FR2-1 BS | FR2-1 BS | FR2-1 BS | | | FR2-1 BS (preliminary) | +| BS TX Power = ① dBm | | 30 dBm | 35 dBm | 30 dBm | 40 dBm | 35 dBm | 30 dBm | 37 dBm | +| Component capability and parameters | Frequency isolation at TX | Frequency isolation capability = ② dBc | 28 dBc | 28 dBc | 28 dBc | 28 dBc | 28 dBc | 28 dBc | +| | | Frequency isolation techniques used | Without DPD | DPD | DPD | Digital Filtering, CFR | | Without DPD | +| | Spatial isolation | Spatial isolation capability = ③ dBc | 87 dBc | 85-95 dBc | 85-95 dBc | 80 dBc | 80 dBc | 80 dBc | +| | | Spatial isolation techniques used | TX/RX panel separation and RF barrier structure | Spatial separation between TX/RX panel, with absorbing material and choke structure | Two separate panels with added electromagnetic spatial duplexer for additional cancellation | A combination of spatial isolation, chokes, absorption, mushroom EBG. | | Separate TX and RX panels with absorptive RF barriers, physical walls and chokes | +| | TX Beam nulling /isolation in TX sub-band = ④ dBc | | 10 dB | 10 dBc | 5-10 dBc | 10 dBc | 10 dBc | 10 dBc | +| | DL EIRP impact due to beam nulling in TX sub-band | | Limited, ~0dB | Less than 0.5 dB loss | | Up to 5dB EIRP loss, depending on beam direction | | < 0.5 dB | +| | Self-interference leakage in gNB RX subband due to non-ideal TX, measured at RX ant. (Note 1) | | -95 dBm
Note: provided by ①-②-③-⑨ dBm | -94~-104 dBm | -88 dBm | -78 dBm | -83 dBm | -87 dBm
Note: provided by ①-②-③-④-10*log 10 (160/40) dBm | +| | RF IC and | RF IC capability | 0 dBc | N/A | | 0 dBc | 0 dBc | Not | + +| | | | | | | | | | | +|-----------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------|---------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|----------------------------------------------------------------|----------------------------------------------------------------|----------------------------------------------------------------|----------------------------------------------------------------------------| +| other tech. (before LNA) | and other tech. in TX sub-band = ⑤ dBc | | | | | | | | applicable | +| | RF IC capability and other tech. in RX sub-band = ⑧ dBc | 0 dBc | N/A | | 0 dBc | 0 dBc | 0 dBc | | Not applicable | +| | RF IC techniques and other tech. (before LNA) | Not applicable | N/A | | | | | | Not applicable | +| | Impacts to RX sensitivity (due to e.g. insertion losses) due to RF IC or other techniques before LNA | No impact | N/A | | 0 dBc | 0 dBc | 0 dBc | | Not applicable | +| Self-Interference signal in gNB TX subband, measured at the input of LNA (Note 1) | | -67 dBm
Note: provided by ①-③-④-⑤dBm | -60 ~ -70 | | -50 dBm | -55 dBm | -60 dBm | | -53 dBm | +| Blocker Suppression at RX | Frequency isolation capability ⑥ dBc | 24 dBc | N/A | 15 dBc | | | | | Not applicable | +| | Frequency isolation techniques | Filtering | - | Filtering (does not protect most of the receiver. Right in front of the ADC, by the time blocker is there, damage already has been done). | | | | | Not Applicable
Filtering would not prevent in-band blocking in any case | +| | RX IMD | Rx IIP3 capability (dBm) | IM3 contribution is Neglectable | negligible | Similar conclusion as FR1 (i.e., IIP3 and IM3 are not dominant) | -35 dBm | -35 dBm | -35 dBm | -35 dBm | +| | | Rx IM3 contribution (dBm) | | negligible | | | | | Negligible | +| | Other RX | Any other RX impacts if significant (e.g. ADC noise, phase noise etc.) | N/A | negligible | Noise figure can be modeled as a function of total input power (signal + jammer) with a piecewise linear | Reciprocal phase noise mixing will add noise at around -95dBm. | Reciprocal phase noise mixing will add noise at around -100dBm | Reciprocal phase noise mixing will add noise at around -105dBm | | + +| | | | | | | | | | | +|----------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------|-------------------------------------------|-----------------------|----------------|-------------|-------------|-------------|----------|----------------| +| | | | | | model. | | | | | +| | Self-Interference signal in gNB RX subband caused by non-ideal RX selectivity, gain-normalized (Note 1, 2) | -91 dBm
Note: provided by ①-③-④-⑤-⑥dBm | negligible | | | -80 dBm | -94 dBm | -104 dBm | -77 dBm | +| | RX Beam nulling /isolation in RX sub-band = ⑨ dBc | 10 dBc | 10 | 5-10 dBc | TBC dBc | | | | TBC | +| | RX sensitivity degradation caused by RX beam nulling | Limited, ~0dB | Less than 0.5 dB loss | | | | | | - | +| | Digital IC = ⑦ dBc | 10 dBc | - | 10 dB | 10 dBc | 10 dBc | 10 dBc | 10 dBc | 5dBc | +| Overall RSIC capability (Note 1) | | 129.5 dBc | 129 ~ 139 | 128 dB | 119 dBc | 125,5dBc | 127 dBc | | 119 dBc | +| Noise floor @dBm | | -83 dBm/100MHz | -88 dBm/40 MHz | -88 dBm/40 MHz | -87 dBm/CBW | -87 dBm/CBW | -87 dBm/CBW | | -87 dBm/40 MHz | +| Residual Interference budget with 1 dB desens target (⑩dBm=⑪dBm-6dB) | | -89 dBm | -94 dBm | -94 dBm | -93 dBm | -93 dBm | -93 dBm | | -93 dBm | +| Required RSIC budget (①-⑪dBc) | | 119 dBc | 129 | 124 dBc | 133 dBc | 128 dBc | 123 dBc | | 130 dBc | +| SBFD configuration | | DU (100MHz-100MHz) | DUD [80,40,80] | DUD | 75-50-75 | | | | DUD [80,40,80] | +| Guardband assumption (if exist) | | 5PRB | Existing SU | 5 PRBs | 3 RB | | | | | +| bandwidth over which suppression is achieved | | 100MHz | Several GHz | 200MHz | Several GHz | | | | | + +## 9.5.1.2 Feasibility study on self-interference + +### 9.5.1.2.1 Samsung + +Different from FR1 counterpart, the difference of feasibility analysis on self-interference for FR2 BS will be provided here for different factors. + +#### Spatial Isolation by Antenna Design + +It's observed that similar and even better antenna isolation performance with the FR2-1 26 GHz testbed where panel separation can be exploited. + +Figure 9.5.1.2.1-1 shows the FR2-1 testbed using 2 Tx panels and 2 Rx panels. Like described in the case of the FR1 3.5 GHz testbed, the Tx panel and the Rx panel in the FR2-1 26 GHz testbed are separated by a separation distance. Additional Tx/Rx isolation performance is then enabled by using an RF barrier, e.g., an additional EM resonant between the panels. In the case of FR2-1 26 GHz, since each panel can perform more directive beam in analog domain than possible in FR1 using mMIMO panels, the FR2-1 antenna isolation performance is better than what is achievable in FR1. + +![Figure 9.5.1.2.1-1: FR2-1 testbed and SIC performance when varying the operating frequency. The top part shows a photograph of the testbed with labels for TX panel, Isolator, and RX panel. The bottom part is a line graph showing S21 (dB) vs Frequency (GHz) from 26.28 to 26.42 GHz. The data points are approximately: (26.30, 83), (26.31, 85), (26.32, 83), (26.33, 88), (26.34, 85), (26.35, 87), (26.36, 85), (26.37, 84), (26.38, 86), (26.39, 87), (26.40, 88).](bf4c705bba1ea48c6e9cace4844d01c4_img.jpg) + +Figure 9.5.1.2.1-1: FR2-1 testbed and SIC performance when varying the operating frequency. The top part shows a photograph of the testbed with labels for TX panel, Isolator, and RX panel. The bottom part is a line graph showing S21 (dB) vs Frequency (GHz) from 26.28 to 26.42 GHz. The data points are approximately: (26.30, 83), (26.31, 85), (26.32, 83), (26.33, 88), (26.34, 85), (26.35, 87), (26.36, 85), (26.37, 84), (26.38, 86), (26.39, 87), (26.40, 88). + +**Figure 9.5.1.2.1-1: FR2-1 testbed and SIC performance when varying the operating frequency** + +Similar as FR1, an important design consideration for increased spatial isolation provided by the RF barrier is whether such stopband performance is stable over a wide enough frequency range. Our FR2-1 26 GHz testbeds have achieved isolation performance that show almost uniform antenna/ panel isolation performance with respect to frequency for 100 MHz CC BW in 26 GHz. Figure 9.5.1.2.1-1 shows measurement results from the FR2-1 testbed with respect to achievable antenna isolation as a function of the operating frequency. + +According to the applied mechanisms and measurement results, the achievable level for TX and RX spatial isolation without impact on radiation pattern based on compact antenna size is around 87dB for FR2. + +### Frequency isolation at TX + +In the case of FR2-1, frequency-domain isolation for SBFD is of particular importance. Non-linear characteristics of mmWave PAs are worse than those of FR1 mid-band PAs. RAN4 ACLR requirements are more relaxed in FR2-1 when compared to FR1. This is due to beamforming providing isolation in FR2-1, implying that the probability of a blocker coming from the same direction is much lower than in FR1. Another consideration is that in FR1, the difference between the out-of-channel requirements like the ACLR and in-channel requirements like EVM is large. The PA linearity requirement is therefore dominated by out-of-channel emission requirements, e.g., ACLR. In FR2-1, these are at comparable levels. Spectral regrowth due to IM3 is dominant for in-channel requirements and as such, PA linearity requirements are rather driven by EVM and possibly in-band emissions. Another design challenge for DPD in FR2-1 is that PA characteristics must be carried through a feedback link from the output of the PA. In the case of mmWave, it is more difficult than in FR1 to create such a feedback link due to signal attenuation. Therefore, it is significantly more challenging to exploit DPD in FR2-1 such as done for FR1. + +Despite these design challenges for gNB-side SBFD operation, our FR2-1 26 GHz testbed measurement results in Figure 9.5.1.2.1-2 show that 28 dBc leakage ratio between DL and UL subband (or component carriers) are still possible, e.g., similar to ACLR as existing out-of-channel requirement for FR2-1. + +![Figure 9.5.1.2.1-2: FR2-1 testbed and PSD for SBFD DL and UL subbands after antenna isolation and filtering. The graph shows Spectral density (dB/150kHz) vs Frequency (MHz) from -215.76 to 215.76 MHz. It highlights three subbands: 1CC (DL), 2CC (DL), and 4CC (DL). A red box highlights a region of the spectrum with the text 'SI even after 87 dB spatial isolation'.](e8f4bfb5095e82627472029c18c4effb_img.jpg) + +Figure 9.5.1.2.1-2: FR2-1 testbed and PSD for SBFD DL and UL subbands after antenna isolation and filtering. The graph shows Spectral density (dB/150kHz) vs Frequency (MHz) from -215.76 to 215.76 MHz. It highlights three subbands: 1CC (DL), 2CC (DL), and 4CC (DL). A red box highlights a region of the spectrum with the text 'SI even after 87 dB spatial isolation'. + +**Figure 9.5.1.2.1-2: FR2-1 testbed and PSD for SBFD DL and UL subbands after antenna isolation and filtering** + +### **Frequency isolation at RX and RF SIC** + +Considering the input power at LNA for FR2 BS could be much less than FR1 WA BS, because of the better spatial isolation and lower BS output power, there is no necessity to have subband filtering to improve the linearity of LNA. + +### **Digital IC** + +Similar as FR1, the digital SIC performance is helped when synchronization is achieved between Tx and Rx to accurately remove the Tx signal from the Rx signal can be obtained. As described in our analysis for FR1 WA BS, two methods exist to estimate the interference channel. One approach is to store information on a Tx signal that has passed through the PA with a feedback link and then estimate the interference channel over-the-air to remove the interference from the Rx signal. Another approach is to use only over-the-air estimation. Without a feedback link, the whole combined channel can still be estimated through the Rx panel. We used the second approach in the FR2-1 26 GHz testbed. + +#### **9.5.1.2.2 Huawei** + +As shown in the 9.5.1.1, it can be found that the blocking level to RX panel is weak and should be even lower at each LNA input. Hence the IM3 is not a limited factor. Due to the same reason that the blocking level is relatively weak, the other RX impacts due to blocker in Tx sub-band can also be negligible. Hence, we think that the evaluation on Self-Interference leakage in gNB RX subband would be sufficient for FR2-1. + +#### **9.5.1.2.3 Qualcomm** + +In the following, we discuss in detail the knobs for FR2 gNB transceiver that enable the mitigation of both component of self-interference, namely direct leakage and clutter reflections. + +### **Antenna techniques and spatial isolation** + +Similar to FR1, FR2 gNB Radio unit architecture with two physically separated panels for simultaneous transmission and reception enable large spatial isolation. To highlight this more, RF measurements for the Tx-Rx spatial has been conducted at 28 GHz frequency with two separate panels. The Tx and Rx measurement setup of the full duplex antenna array is shown in Figure 9.5.1.2.3-1. This measurement setup is on top of the building roof with antenna pointing to the sky, in which case could be without clutter impact or with negligible clutter impact. In this setup, the Tx and Rx beam sweeping is synchronized which is the worst-case scenario - without including clutter. The measurement results, presented in Figure 9.5.1.2.3-2, show at least 80-90 dB spatial isolation can be achieved between the two Tx and Rx panels. If the antenna array center-to-center distance is 65 cm, the spatial isolation could be achieved at -86.9 dB or better. + +![Figure 9.5.1.2.3-1: Measurement setup for Tx-Rx spatial isolation of the full duplex antenna array at 28 GHz. The image shows two antenna panels, labeled 'RX' and 'TX', mounted on a rooftop. The RX panel is on the left and the TX panel is on the right. Both panels have red arrows indicating their look angles, labeled 'Φ=0, θ=RX look angle' and 'Φ=0, θ=TX look angle' respectively. The background shows a cityscape with buildings and trees.](f40b62ac3beebf7c156d65b3f9a7da86_img.jpg) + +Figure 9.5.1.2.3-1: Measurement setup for Tx-Rx spatial isolation of the full duplex antenna array at 28 GHz. The image shows two antenna panels, labeled 'RX' and 'TX', mounted on a rooftop. The RX panel is on the left and the TX panel is on the right. Both panels have red arrows indicating their look angles, labeled 'Φ=0, θ=RX look angle' and 'Φ=0, θ=TX look angle' respectively. The background shows a cityscape with buildings and trees. + +**Figure 9.5.1.2.3-1: Measurement setup for Tx-Rx spatial isolation of the full duplex antenna array at 28 GHz** + +![Line graph showing S21 (dB) vs Rx Look Angle (Degrees) for isolation at different look angles. The y-axis ranges from -120 to -80 dB, and the x-axis ranges from -40 to 40 degrees. Multiple colored lines represent different look angles, showing fluctuations in isolation levels. A red box at the top indicates 'Array center to center distance=65cm'.](870febccb98ab2774dee3ad16c85b0ac_img.jpg) + +Isolation at different look angles. +Array center to center distance=65cm + +Line graph showing S21 (dB) vs Rx Look Angle (Degrees) for isolation at different look angles. The y-axis ranges from -120 to -80 dB, and the x-axis ranges from -40 to 40 degrees. Multiple colored lines represent different look angles, showing fluctuations in isolation levels. A red box at the top indicates 'Array center to center distance=65cm'. + +Worse case isolation -86.9dB. + +Figure 9.5.1.2.3-2: RF measurements of Tx-Rx spatial isolation between two subarrays for FR2 + +**Beam isolation and beamforming/nulling** + +In FR2, spatially isolated and narrow Tx and Rx beam could be selected to provide extra ‘beam’ isolation, which is a combined factor with the antenna isolation. For direct leaked self-interference, it is less related to the beam direction although there is still some dependency. However, for clutter, the signal transmitted from the Tx panel goes through the wireless medium, scattered by the reflectors and then gets back to the Rx panel, which generally has longer delay compared with direct leaked self-interference. The clutter is direction specific, in which case proper selection of Tx and Rx beam pair can alleviate such clutter impact. For FR2, clutter measurements have been conducted for a typical conference room. The measurement setup and results are shown in Figure 9.5.1.2.3-3. In the measurement setup, the Tx and Rx beam sweeping is synchronized, which is the worst-case scenario. + +![Heatmap titled 'Max Clutter (dB)' showing clutter levels across different Azimuth (Az) and Elevation (El) angles. The x-axis (Az) ranges from -75 to 75, and the y-axis (El) ranges from -30 to 30. A color bar on the right indicates clutter power from -120 dB to -80 dB. A callout box explains that at Az=0, El=0, the clutter source is 25.6ft away. A room layout diagram on the right shows the measurement setup with a TV, conference table, and windows.](45f6ef490318427c69f507d3fd26bcc5_img.jpg) + +The annotated numbers on the pixel plots show the **range** of the dominant clutter in that direction. At Az=0,El=0, the clutter source is **25.6ft away**. The color shows the level of the clutter. + +28GHz +Max Clutter (dB) + +346° +Double Door +Room = 28.8' x 23.8' x 10' +TV Monitor: 74.5" x 43", 6ft off floor +Conference Table +Distance of TV is 6ft off floor +37° +286° +Window + ++ Azimuth: CW +- Azimuth: CCW ++ Elevation: Pointing Up +- Elevation: Pointing Down + +Heatmap titled 'Max Clutter (dB)' showing clutter levels across different Azimuth (Az) and Elevation (El) angles. The x-axis (Az) ranges from -75 to 75, and the y-axis (El) ranges from -30 to 30. A color bar on the right indicates clutter power from -120 dB to -80 dB. A callout box explains that at Az=0, El=0, the clutter source is 25.6ft away. A room layout diagram on the right shows the measurement setup with a TV, conference table, and windows. + +Figure 9.5.1.2.3-3: Clutter measurements for FR2 indoor deployments + +**Digital self-interference mitigation** + +In FR2, non-linear interference cancellation (NLIC) measurements have been conducted at 60 GHz for a typical conference room setup. For FR2, the measurement results are shown in for both low MCS and high MCS showing that NLIC could provide ~10 dB improvement on SNR performance. + +### 9.5.1.2.4 Ericsson + +An overview of the self-interference mitigation potential for FR2-1 (28GHz) for three output power levels can be found in Table 9.5.1.1-1. It can be seen that mitigation of self-interference with less than 1dB receiver desensitization appears feasible for 30dBm. With 35dBm, the desensitization is around 1.5dB from self-interference. There may be some potential to further refine the performance. For 40dBm output power, mitigation of self-interference becomes significantly more challenging. + +#### TX – RX isolation + +A number of techniques exist to improve the TX-RX panel isolation including chokes, absorption, mushroom EBG etc. A detailed electromagnetic simulation of these techniques is presented in [50], which demonstrates that the isolation between a TX panel and RX sub-array is around 80dB. Unlike for FR1, the self-isolation does not seem to vary significantly with beam direction. Figure 9.5.1.2.4-1 shows EM simulation results and a visualization of the EM isolation. + +![Figure 9.5.1.2.4-1: EM simulation results for FR2 self-isolation. The figure consists of six subplots (a-f) showing Coupling Magnitude [dB] vs Frequency [GHz] from 26 to 34 GHz. The top row (a, b, c) shows co-polarized elements, the middle row (d, e, f) shows cross-polarized elements. Each row has three columns: (a, d) boresight, (b, e) +15 deg. toward RX, and (c, f) -15 deg. away from RX. The bottom row (d, e, f) also includes 3D visualizations of the EM propagation field.](e4c1d52d98aeae48bc84361381836c4c_img.jpg) + +(a) boresight (b) +15 deg. toward RX (c) -15 deg. away from RX + +(d) boresight (e) +15 deg. toward RX (f) -15 deg. away from RX + +Figure 9.5.1.2.4-1: EM simulation results for FR2 self-isolation. The figure consists of six subplots (a-f) showing Coupling Magnitude [dB] vs Frequency [GHz] from 26 to 34 GHz. The top row (a, b, c) shows co-polarized elements, the middle row (d, e, f) shows cross-polarized elements. Each row has three columns: (a, d) boresight, (b, e) +15 deg. toward RX, and (c, f) -15 deg. away from RX. The bottom row (d, e, f) also includes 3D visualizations of the EM propagation field. + +**Figure 9.5.1.2.4-1: EM simulation results for FR2 self-isolation (top) co-polarized (middle) cross polarized elements (bottom) visualization of the EM propagation** + +#### TX beam nulling + +The transmit panel has a large number of transmit elements and hence a high number of degrees of freedom to perform beamforming. Beam Nulling can be used in the transmit panel to reduce the power at the receive panel. It is not clear that beam nulling has the same impact on both the transmitted signal and the transmitter leakage, however for simplicity this has been assumed. + +### **Interference cancellation** + +Analogue and digital interference cancellation have not been considered due to the complexity and losses of building interconnectors for FR2, the high bandwidth and large amount of digital processing required. + +### **Digital processing** + +Digital RX combining taking into account interference covariance have the potential to mitigate interference in the receiver. The gains from digital combining depend on the BS environment considering other interference sources such as other sectors, gNB and UEs. + +### **Phase noise reciprocal mixing** + +Reciprocal mixing of phase noise causes a more significant amount of noise in the receiver in FR2-1 compared to FR1. However, the analysis suggests that also for FR2-1, reciprocal mixing of phase noise will not cause a significant degradation. + +#### **9.5.1.2.5 Nokia** + +Nokia's views on the self-interference analysis for FR2-1 base stations are presented in Table 9.5.1.1-1. Our analysis shows that considering an BS TX power equal to 37 dBm, it is not possible to achieve the required residual self-interference. In our analysis, the required RSIC budget is 130 dBc, while the overall RSIC capability is 119 dB, which would result in a residual self-interference that would cause more than 1 dB desensitization of the receiver. Below, we discuss the key aspects considered in this analysis. + +### **Spatial isolation and Tx Beam nulling** + +For the achievable spatial isolation, we find that 80 dB may be a reasonable assumption considering the increased isolation from using higher frequencies and narrow Tx and Rx analog beams. Similar as discussed in our FR1 analysis in clause 9.2.1.2.6, separate Tx and Rx panels with EM shielding structures between the arrays are assumed, which in turn leads to an increase in antenna size and weight if baseline system performance needs to be maintained. + +In FR2-1, TX beam nulling can be used to reduce self-interference, at least in the TX subband. It can be used with digital and analog beamforming. Our simulations show that in the latter case, beam nulling works well as illustrated in Figure 9.5.1.2.5-1 where at most 10 dB of additional isolation is obtained over a relatively large frequency range (500 MHz). However, in case multiple Tx panels are used for MU-MIMO or higher-rank transmissions, the gains of beam nulling are reduced since analog beamforming does not allow the use of beam nulling to suppress interference from more than one TX panel. + +![Figure 9.5.1.2.5-1: Empirical CDF of isolation between each Tx beam towards worst-affected Rx port. The graph shows the Cumulative Distribution Function (CDF) of isolation in dBc for various Tx beam frequencies. The x-axis represents isolation in dBc, ranging from 65 to 100. The y-axis represents the CDF, ranging from 0 to 1. The legend indicates: 'without beam nulling' (blue line), '29.750 GHz' (orange line), '29.875 GHz' (yellow line), '30.000 GHz' (green line), '30.125 GHz' (light green line), and '30.250 GHz' (cyan line). The 'without beam nulling' curve is shifted to the left, indicating lower isolation values compared to the curves with beam nulling at different frequencies.](4c5a5c93221c0a5b9f6d1b0d4bdcfe81_img.jpg) + +Figure 9.5.1.2.5-1: Empirical CDF of isolation between each Tx beam towards worst-affected Rx port. The graph shows the Cumulative Distribution Function (CDF) of isolation in dBc for various Tx beam frequencies. The x-axis represents isolation in dBc, ranging from 65 to 100. The y-axis represents the CDF, ranging from 0 to 1. The legend indicates: 'without beam nulling' (blue line), '29.750 GHz' (orange line), '29.875 GHz' (yellow line), '30.000 GHz' (green line), '30.125 GHz' (light green line), and '30.250 GHz' (cyan line). The 'without beam nulling' curve is shifted to the left, indicating lower isolation values compared to the curves with beam nulling at different frequencies. + +**Figure 9.5.1.2.5-1: Empirical CDF of isolation between each Tx beam towards worst-affected Rx port. Tx beams are generated within $\pm 45^\circ$ azimuth and elevation angles.** + +We assume 0 dB for RX beam nulling; as the SBFD feature is about enhancing uplink performance, we do not think the UL beamforming can be compromised further than the loss of channel reciprocity (due to separate TX and RX arrays) brings. + +### Digital IC + +We consider $\sim 5$ dBc possibility for digital IC with maximum ratio combining of RX. Self-interference cancellation might be achieved since the direction of wanted signal and interference signal are not the same. + +### 9.5.1.3 Conclusion + +Based on the provided studies in clause 9.5.1.1, it can be concluded that it is feasible to meet the 1 dB desensitization target considering self-interference suppression for FR2-1 BS with TX output power levels up to around 33 dBm. + +## 9.5.2 Co-channel inter-sub-band co-site inter-sector interference analysis + +### 9.5.2.1 Summary table for co-channel inter-sub-band co-site inter-sector interference analysis + +The Co-channel inter-sub-band co-site inter-sector interference analysis from companies' input for FR2 SBFD-capable gNB is summarized in Table 9.5.2.1-1. Both self-interference leakage in gNB RX subband due to non-ideal TX and Self-Interference signal in gNB RX subband caused by non-ideal RX selectivity are studied in the analysis framework. The interference cancellation techniques including spatial isolation, frequency isolation, beam nulling and digital/RF cancellation are considered in the analysis framework. + +**Table 9.5.2.1-1: Co-channel inter-sub-band co-site inter-sector interference analysis** + +| FR1 (or FR2-1) | | | Samsung | Huawei | Ericsson | | | +|-------------------------------------------------|---------------------------|---------------------------------------------------|-------------|--------|----------------------------------------|------------------------|------------------------| +| BS class | | | FR2-1 BS | | | | | +| BS TX Power = ① dBm | | | 30 dBm | 35 dBm | 30 dBm | 35 dBm | 40 dBm | +| Number of co-site co-channel sectors considered | | | 1 | 2 | 2 | 2 | 2 | +| Component capability and parameters | Frequency isolation at TX | Frequency isolation capability = ② dBc | 28 dBc | 28 dB | 28 dBc | 28 dBc | 28 dBc | +| | | Frequency isolation techniques used | Without DPD | DPD | Digital Filtering, CFR | Digital Filtering, CFR | Digital Filtering, CFR | +| | Spatial isolation | Co-channel Co-site Inter-sector Spatial isolation | 87 dBc | 100 dB | 75-98 dBc (depending on beam steering) | | | + +| | | | | | | | +|--------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------|--------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------|--------------------------------------------------------------------|-------------------------------------------------------------------| +| | capability
= ③ dBc | | | directions) | | | +| | Co-channel Co-site
Inter-sector
Spatial isolation
techniques used | Based on
87dB for
typical
spatial
isolation | Spatial
separation
between
TX/RX
panel and
surface
wave
suppression
techniques | Typical site
deployment
with 400mm
between
sectors | | | +| | TX Beam nulling /isolation of inter-sector interference in TX sub-band
= ④ dBc | 20 dBc | - | 0 dB | 0 dB | 0 dB | +| | DL EIRP impact due to beam nulling in TX sub-band (considering all nulling for self- and inter-sector interference) | Neglectable | - | 0 dB | 0 dB | 0 dB | +| | Interference leakage in gNB RX subband due to non-ideal TX, measured at RX ant. due to inter-sector interference (Note 1) | -105 dBm | -96 | -93 dBm to -70 dBm
(depending on
beam steering
directions) | -88 to -65 dBm
(depending
on beam
steering
directions) | -83 to -60dBm
(depending
on beam
steering
directions) | +| | Interference signal in gNB TX subband, measured at the input of LNA (Note 1) due to inter-sector interference | -77 dBm | -62 | -65 dBm to -42 dBm
(depending
on beam
steering
directions) | -60 to -37 dBm
(depending
on beam
steering
directions) | -55 to -32dBm
(depending
on beam
steering
directions) | +| Blocker
Suppression
at RX | Frequency isolation
capability
⑥ dBc | 24 dBc | - | 0 dB | 0 dB | 0 dB | +| | Frequency isolation
techniques | Filtering | - | 0 dB | 0 dB | 0 dB | +| | RX IMD
Rx IIP3 capability
(dBm) | IM3
contribution
is
Neglectable | - | -35 dBm | -35 dBm | -35 dBm | +| | Rx IM3
contribution (dBm) | | - | -109 to -56 dBm | -101.5 to -41 dBm | -91 to -26 dBm | +| | Other RX
Any other RX
impacts if
significant (e.g.
ADC noise, phase
noise etc.) | N/A | - | RX phase
noise is -105
dBm | RX phase
noise is
-100 dBm | RX phase
noise is
-95 dBm | +| | Interference signal in gNB RX subband caused by non-ideal RX selectivity, gain-normalized due to co-site inter-sector co-channel interference only (Note 1, 2) | -101 dBm | - | -103.5 to -56 dBm | -97.5 to -41 dBm | -89.5 to -26 dBm | +| | RX Beam nulling /isolation in RX sub-band
= ⑨ dBc | 20 dB | - | 0 dB | 0 dB | 0 dB | +| | RX sensitivity degradation caused by RX beam nulling | Neglectable | - | 0 dB | 0 dB | 0 dB | +| | Digital processing interference suppression capability | 0 dB | - | 0 dB | 0 dB | 0 dB | +| Total interference in RX SB (dBm) (Note 2) | | -99.5 dBm | -96 dBm | -93 to -56 dBm | -87.5 to -41 dBm | -82 to -26 dBm | +| Noise floor @dBm | | -83 dBm/100MHz | -88 dBm/40 MHz | -87 dBm | -87 dBm | -87 dBm | +| Calculated Desensitization (dB) | | 0.1dB | 0.6 dB | 1 to 31 dB
(depending on | 2.8 to 46 dBm | 6 to 61 dB
(Dependin | + +| | | | beam direction) | (Depending on beam direction) | g on beam direction) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|-------------|-----------------|-------------------------------|----------------------| +| SBFD configuration | DU (100MHz-100MHz) | DUD | 75-50-75 | | | +| Guardband assumption (if exist) | 5PRB | Existing SU | 3 RB | | | +| bandwidth over which suppression is achieved | 100MHz | Several GHz | Several GHz | | | +| Others | | | | | | +| Note 1: Relevant metrics are derived from other parameters for checking purpose.
Note 2: The relevant metric is gain-normalized, with reference point assumed to be at RX antenna.
Note 3: The notations ①②③④⑤⑥⑦⑧⑨⑩⑪ are used to indicate the decimal values of the corresponding metrics.
Note 4: The abbreviation CSSI refers to co-site co-channel inter-sector interference in this table | | | | | | + +## 9.5.2.2 Feasibility study on co-channel inter-sub-band co-site inter-sector interference + +### 9.5.2.2.1 Samsung + +Different from the self-interference, the digital IC is not of necessity for the co-channel interference from co-site inter-sector BS. Furthermore, the isolation achieved by TX and RX beamforming nulling will be larger due to the different beamforming directions from different sectors. + +### 9.5.2.2.2 Huawei + +For FR2 inter-sector isolation, some measurements based on existing modules are proceed as below. The AAS mounting in the same mast would be worse cases for radiated isolation. The following two cases are the typical site deployments for the worse cases. The left one (Case 1) is up-down installation and the right one (case 2) is 120° installation. + +![Figure 9.5.2.2.2-1: Measurements of inter-sector isolation. The image shows two side-by-side photographs of a radio base station (RBS) mounted on a mast in a large anechoic chamber. The left photo (Case 1) shows an up-down installation where two RBS units are mounted vertically on the same mast. The right photo (Case 2) shows a 120-degree installation where two RBS units are mounted on the same mast at a 120-degree angle to each other. The background consists of large, dark, pyramid-shaped electromagnetic wave absorbers lining the walls of the chamber.](cb2548913628a6332ad07b161877fecf_img.jpg) + +Figure 9.5.2.2.2-1: Measurements of inter-sector isolation. The image shows two side-by-side photographs of a radio base station (RBS) mounted on a mast in a large anechoic chamber. The left photo (Case 1) shows an up-down installation where two RBS units are mounted vertically on the same mast. The right photo (Case 2) shows a 120-degree installation where two RBS units are mounted on the same mast at a 120-degree angle to each other. The background consists of large, dark, pyramid-shaped electromagnetic wave absorbers lining the walls of the chamber. + +**Figure 9.5.2.2.2-1: Measurements of inter-sector isolation** + +For each case, $60 \times 60 = 3600$ beam combinations are measured. The results are shown in Table 9.5.2.2.2-1 for existing modules and Table 9.5.2.2.2-2 for improved modules. Some surface wave suppression measures can be used to improve the isolation, e.g. reflection and absorption structure. Using these measures, more than 10 dB improvement can be achieved for the case with poor isolation. As shown in the measurements, 100 dB inter-sector isolation is achievable for FR2 + +**Table 9.5.2.2.2-1: Inter-sector isolation for existing modules** + +| Test cases | Existing modules | 95% CDF | 90% CDF | 50% CDF | +|------------|----------------------|---------|---------|---------| +| Case 1 | up-down installation | 96 | 99 | 103 | +| Case 2 | 120° installation | 85 | 90 | 100 | + +**Table 9.5.2.2.2-2: Inter-sector isolation for improved modules** + +| Test cases | Improved modules | 95% CDF | 90% CDF | 50% CDF | +|------------|----------------------|---------|---------|---------| +| Case 1 | up-down installation | 101 | 103 | 104 | +| Case 2 | 120° installation | 100 | 101 | 102 | + +### 9.5.2.2.3 Ericsson + +An analysis of the inter-sector interference effects for FR2-1 BS can be found in Table 9.5.2.1-1. The analysis suggests that inter-sector interference can lead to substantial degradations. Apart from with the most optimal beam directions settings and 30dBm TRP, degradations due to inter-sector interference are substantial. Although TX beam nulling may be considered to reduce inter-sector interference, in excess of 30dB-60dB suppression (depending on output power) would be needed to mitigate interference for all beam directions. + +For 30dBm TRP, RX processing or improvements in the TX interference suppression may improve the inter-sector performance. However, the degradation will not be reduced to well below 1dB (taking into account also degradation from self-interference will occur) for all beam directions. + +Thus co-sectorization is likely to pose technical challenges for SBFD deployments in FR2. + +#### Inter-sector isolation + +Isolation between sectors has been simulated using electromagnetic simulations in [68] with an assumption of 400mm sector separation. The isolation varies to some degree with separation, but not to an extent that would change the overall results. For most practical site deployments, addition of materials between sectors is not likely to be feasible (and may reduce network performance). Figure 9.5.2.2.3-1 depicts the EM simulation setup. + +![Figure 9.5.2.2.3-1: Simulation setup for FR2 multi-sector EM modelling. The diagram shows two views of a three-sector antenna array. The left view is a top-down perspective showing Sector 1 at the top, Sector 2 at the bottom left, and Sector 3 at the bottom right, with a 400.00 mm separation between Sector 2 and Sector 3. The right view is a side elevation showing Sector 1 at the bottom and Sectors 2 and 3 mounted on a vertical panel above it, with a 100.00 mm vertical separation between Sector 1 and the panel. Coordinate axes (x, y, z) are shown for both views.](55649f88568b3835d933b30ca8e00279_img.jpg) + +Figure 9.5.2.2.3-1: Simulation setup for FR2 multi-sector EM modelling. The diagram shows two views of a three-sector antenna array. The left view is a top-down perspective showing Sector 1 at the top, Sector 2 at the bottom left, and Sector 3 at the bottom right, with a 400.00 mm separation between Sector 2 and Sector 3. The right view is a side elevation showing Sector 1 at the bottom and Sectors 2 and 3 mounted on a vertical panel above it, with a 100.00 mm vertical separation between Sector 1 and the panel. Coordinate axes (x, y, z) are shown for both views. + +**Figure 9.5.2.2.3-1: Simulation setup for FR2 multi-sector EM modelling** + +Figure 9.5.2.2.3-2 depicts the achievable isolation. The left hand plot shows the isolation with azimuth steering and elevation in boresight and the right hand plot with elevation steering and azimuth on boresight. The isolation between sectors is highly dependent on the beam direction. Although an “average” isolation can be given, this would mask the fact that for certain beam directions isolation is good and for others it is not good. Since the beam direction depends on the physical positions of users, advanced co-ordination of beam directions may not be possible if other constraints such as capacity and latency are to be optimized. + +![Figure 9.5.2.2.3-2(a): Azimuth beam steering with elevation at boresight. A line graph showing RX/TX coupling magnitude [dB] vs Frequency [GHz] for Boresight (blue), 30 deg (red), and 60 deg (yellow).](f9a7651f6e25578aded68c3bce114452_img.jpg) + +This graph shows the RX/TX coupling magnitude in dB for an FR2 antenna with 400 mm edge to edge coupling. The x-axis represents Frequency in GHz, ranging from 26 to 34. The y-axis represents RX/TX coupling magnitude in dB, ranging from -100 to 0. Three curves are plotted: Boresight (blue), 30 deg (red), and 60 deg (yellow). The Boresight curve is relatively flat around -80 dB. The 30 deg and 60 deg curves show more variation, with the 60 deg curve reaching a minimum of approximately -95 dB at 32 GHz. + +Figure 9.5.2.2.3-2(a): Azimuth beam steering with elevation at boresight. A line graph showing RX/TX coupling magnitude [dB] vs Frequency [GHz] for Boresight (blue), 30 deg (red), and 60 deg (yellow). + +(a) Azimuth beam steering with elevation at boresight + +![Figure 9.5.2.2.3-2(b): Downtilt elevation beam steering with azimuth at boresight. A line graph showing RX/TX coupling magnitude [dB] vs Frequency [GHz] for Boresight (blue), -10 deg (red), -15 deg (yellow), and -20 deg (green).](2785e0afc1cc382b8b668164369fb1d4_img.jpg) + +This graph shows the RX/TX coupling magnitude in dB for an FR2 antenna with 400 mm edge to edge coupling. The x-axis represents Frequency in GHz, ranging from 26 to 34. The y-axis represents RX/TX coupling magnitude in dB, ranging from -100 to 0. Four curves are plotted: Boresight (blue), -10 deg (red), -15 deg (yellow), and -20 deg (green). The Boresight curve is relatively flat around -80 dB. The -10 deg, -15 deg, and -20 deg curves show more variation, with the -20 deg curve reaching a minimum of approximately -95 dB at 32 GHz. + +Figure 9.5.2.2.3-2(b): Downtilt elevation beam steering with azimuth at boresight. A line graph showing RX/TX coupling magnitude [dB] vs Frequency [GHz] for Boresight (blue), -10 deg (red), -15 deg (yellow), and -20 deg (green). + +(b) Downtilt elevation beam steering with azimuth at boresight + +Figure 9.5.2.2.3-2: FR2 antenna with 400 mm edge to edge coupling magnitude + +### Beam nulling + +There may be some potential for beam nulling to mitigate interference between sectors. To achieve complete isolation between sectors, more than 30dB beam nulling would be needed. + +### 9.5.2.3 Conclusion + +Based on the provided studies in clause 9.5.2.1, two companies conclude that it is feasible to suppress inter-sector interference to a level that it meets 1 dB desensitization target, whereas one company concludes that it is not feasible for a proportion of beam directions. The difference between the conclusions is mainly due to differences in assumption on whether it is possible to build isolation materials within sites and whether sufficient beam nulling is possible in all directions. + +## 9.5.3 Co-channel inter-sub-band inter-site interference analysis + +On the feasibility and how to model inter-site gNB-gNB CLI modelling considering unwanted emission and receiver selectivity, RAN4 agree that + +- The same transmitter leakage and receiver impairment model as used for investigating gNB self-interference, but antenna isolation is replaced with inter-site isolation. +- TX leakage baseline: gNB ACLR +- Receiver impairment can be studied with gNB ACS as baseline for system level simulation and feasibility study, and further study on the possibility of improved receiver impairment performance compared to gNB ACS shall not be precluded in future RAN4 works. + +## 9.5.4 Summary + +Based on RAN4 feasibility study on FR2-1 wide area BS, specifically the analysis on self-interference, co-site inter-sector co-channel inter-subband interference and inter-site inter-subband interference, RAN4 concluded that: + +- For self-interference analysis, the implementation feasibility of controlling the residual interference to meet the 1dB receiver desensitization target depends on the implementation aspects mentioned in clause 9.5.1. Based on the companies' technical inputs, it can be concluded that it is feasible to meet the 1 dB desensitization target considering self-interference suppression for FR2-1 BS with TX output power levels up to around 33dBm. +- For co-site inter-sector co-channel inter-subband interference, the implementation feasibility of controlling the co-site inter-sector co-channel inter-subband interference to meet the target (i.e., being less than certain level of receiver desensitization) depends on the implementation aspects mentioned in clause 9.5.2. Based on the different assumptions and/or technique adoption for the above-mentioned implementations aspects, and based on 3 companies' technical inputs, two companies conclude that it is feasible to suppress inter-sector interference to a level that it meets 1 dB desensitization target, whereas one company concludes that it is not feasible for a proportion of beam directions. The difference between the conclusions is mainly due to differences in + +assumption on whether it is possible to build isolation materials within sites and whether sufficient beam nulling is possible in all directions. + +- For inter-site co-channel inter-subband interference, since the feasibility is deployment-dependent, RAN4 has provided the inter-site gNB-gNB CLI modelling used for coexistence study by considering unwanted emission and receiver selectivity modelling. + +## 9.6 FR1 Feasibility of UE aspects + +### 9.6.1 Interference analysis + +#### 9.6.1.1 General + +In the objective of this study item, half duplex operation at UE side is assumed. In this part of feasibility of UE aspects, FR1 is considered. + +In the UE feasibility study in FR1, the co-channel inter-subband UE-UE CLI model and adjacent channel UE-UE CLI model are mainly discussed. Co-channel/adjacent channel interference models at the UE side are summarized in Table 9.6.1.1-1. For co-channel interference models, the UE IBE requirement can be used for the interference modelling at Tx side; for receiver in-channel adjacent subband selectivity performance, no rejection/attenuation due to RF/BB filtering is assumed and the selectivity and performance of the FFT is included in the study. For adjacent channel models, UE ACLR and adjacent channel selectivity requirements can be used for the interference modeling at Tx and Rx side, respectively. + +**Table 9.6.1.1-1. Existing UE interference models based on RF requirements in RAN4** + +| Co-channel RF interference models | | Adjacent channel RF interference models | | +|-----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------|------------------------------| +| Tx side | Rx side | Tx side | Rx side | +| UE IBE for Tx | In-channel adjacent subband selectivity (Note 1) | Power dependent ACLR as described in Section 9.6.1.3.2 | Adjacent channel selectivity | +| Note 1: | For legacy UE, there is no existing UE RF requirement for in-channel adjacent subband selectivity . It is only used in SBFD feasibility study purpose and no indication that this requirement shall or shall not be defined in the normative phase. | | | + +#### 9.6.1.2 UE-UE co-channel inter-subband CLI modeling + +##### 9.6.1.2.1 Overview and analysis framework + +The objectives of UE-UE co-channel inter sub-band CLI modeling is to analyze the impact of interference that occurs between two UEs in close proximity, operating on adjacent sub-bands within the same channel. This interference occurs when UL transmission of an aggressor UE in the channel interferes with the DL reception of a victim UE in the same channel. + +For this SI RAN4 has decided to use typical UE parameters in the analysis, as different from worst-case parameters that are commonly used to define minimum performance requirements. The evaluation of gNB performance improvements is underway in RAN1, taking into account a population of typical UEs rather than worst-case UEs. + +In-channel adjacent subband selectivity is a measure of a receiver's ability to receive an NR signal on its assigned downlink subband in the presence of an interference power on the adjacent uplink subband. The value of in-channel adjacent subband selectivity is the ratio of the receiver attenuation on the assigned downlink subband to the receiver attenuation on the adjacent uplink subband. In an ideal scenario, the UL transmission of the aggressor UE should not impact the DL reception of the victim UE due to the OFDM wave orthogonality. However, non-ideal FFT suppression can cause interference to the victim UE, particularly when the UL sub-band has frequency errors and is not perfectly time-synchronized with the DL sub-band. The analysis indicates that the IBE interference could be more significant than the in-channel adjacent subband selectivity, and frequency and time offset are not significant factors influencing UE-UE interference. It is worth noting that the RF degradations can cause inter-subband interference as well and the impact will depend on the targeted Rx IM and EVM performance. The measurement data submitted by one company shows the achievable in-channel adjacent subband selectivity of FR1 UE can be 33 dB. Nonetheless, the typical interference will normally not be any worse than this value. For this reason, the 33 dB was agreed for modeling the in-channel adjacent subband selectivity. + +For legacy UE, no sub-band filtering is considered. + +To model the NF for co-channel CLI in a system level simulation, a fixed value noise figure of 9 dB is used. AGC is not modeled if a fixed NF model is used. + +Apart from the in-channel adjacent subband selectivity, it is important to mention that degradation can also be caused by transmitter leakage from the UL sub-band into the DL sub-band. For co-channel cases, the leakage was agreed to be modelled based on IBE based model with details provided in clause 9.6.1.2.2. + +#### 9.6.1.2.2 UE co-channel Tx model + +##### In-Band Emissions + +For UE co-channel Tx model, RAN4 has decided to use the IBE minimum requirements from 38.101-1 clause 6.4.2.3 as shown in Table 9.6.1.2.2-1 in the feasibility study. This IBE-based model consists of three parts: General, IQ image, and Carrier leakage. In the system level simulation, the general and IQ image parts shall be considered, while the carrier leakage part can be ignored. For DUD configuration, the IQ image from the uplink is fully contained in the UL sub-band and does not land in the DL subband, thus the IQ image can also be ignored in the simulation. The granularity of this model is 1RB and it is not pursued to simplify this model to a frequency flat model. It is understood that these requirements are minimum performance requirements as opposed to typical requirements. RAN4 has agreed to use typical requirements for the UE parameters. Since typical values for the UE parameters were not determined, the formulation from the current specification is being used. + +**Table 9.6.1.2.2-1: Requirements for in-band emissions in TS 38.101-1** + +| Parameter description | Unit | Limit (NOTE 1) | | Applicable Frequencies | +|-----------------------|------|----------------|----------------------------------------------|----------------------------------------| +| General | dB | | | Any non-allocated (NOTE 2) | +| IQ Image | dB | -28 | Image frequencies when output power > 10 dBm | Image frequencies (NOTES 2, 3) | +| | | -25 | Image frequencies when output power ≤ 10 dBm | | +| Carrier leakage | dBc | -28 | Output power > 10 dBm | Carrier leakage frequency (NOTES 4, 5) | +| | | -25 | 0 dBm ≤ Output power ≤ 10 dBm | | +| | | -20 | -30 dBm ≤ Output power < 0 dBm | | +| | | -10 | -40 dBm ≤ Output power < -30 dBm | | + +It should also be assumed the LO location is in the center of the channel for the purposes of system studies in RAN4. The LO location is important as it allows placement of the image. + +#### 9.6.1.2.3 UE co-channel Rx model + +For UE co-channel Rx model, currently there is no corresponding RF requirement for this model. In the feasibility of UE co-channel Rx model, the definition of in-channel adjacent subband selectivity is introduced for SBFD feasibility study purpose: + +- In-channel adjacent subband selectivity is a measure of a receiver's ability to receive an NR signal on its assigned downlink subband in the presence of an interference power on the adjacent uplink subband. The value of in-channel adjacent subband selectivity is the ratio of the receiver attenuation on the assigned downlink subband to the receiver attenuation on the adjacent uplink subband. + +For legacy UE, no sub-band filtering is assumed in the feasibility study, and accordingly no rejection/attenuation due to RF/BB filtering is assumed and only the selectivity performance of the FFT operation is studied. 33 dB was agreed for FR1 in RAN4 for in-channel adjacent subband selectivity considering FFT operation. + +##### Thermal self-noise performance + +RAN4 decided on using a simplified fixed-value noise figure model for the UE receiver. Generally, the receiver noise figure will vary with the input power level, however the single value noise figure model was regarded to be sufficient for the purpose of system studies for SBFD operation. RAN4 decided on a noise figure value of 9 dB for FR1 UE. + +### **Effect of jammer – non-thermal self-noise aspect** + +There are a few factors to consider in determining the in-channel subband interference in the presence of a co-channel jammer. With an in-channel adjacent-subband interferer the 3rd order distortion, reciprocal mixing, residual sideband, quantization noise, phase noise, ADC distortion, and analog filtering should be considered. + +In RAN4 study, measurements were made of a UE receiver for various signal levels, interferer levels, interferer offsets, sub-band bandwidths, and interferer bandwidths. The measurements have included the impact of the entire receiver, which includes everything through the FFT operation, in which 120 various conditions were measured. + +### **FFT leakage and selectivity** + +In the SBFD system an aggressor UE (UE2) operating in the UL sub-band may interfere with a UE (UE1) receiving in the adjacent DL sub-band. The UL signal from UE2 may arrive at UE1 misaligned in time or frequency, which can potentially cause UE1 DL SINR degradation in the FFT operation. + +The simulation involved the conversion of the OFDM waveform to a spectrum by using FFT, along with the introduction of timing and frequency errors. A 5 RB guard band was assumed. The analysis revealed that time-misalignment was the main cause of the spectral leakage, and even minor timing errors resulted in leakage. + +It appears reasonable to consider the leakage as a single average value, and the data shows about 33 dB down from the jammer level would be appropriate. The leakage effect should be taken into consideration and compared to the interference caused by the aggressor IBE. It has been observed that the interference in the victim sub-band can be modelled as 33 dB below the input jammer power level, and the interference is approximately frequency flat across the victim subband. + +![Figure 9.6.1.2.3-1: FFT leakage into adjacent sub-band. A scatter plot showing FFT leakage into adjacent sub-band (dB wrt jammer) on the y-axis (ranging from -45 to -15) versus Time Offset (nsec) on the x-axis (ranging from 0 to 4500). The data points are scattered, with most values between -30 dB and -40 dB, indicating significant leakage across the time offset range.](1dad8c32864c128e058d2bb26f34c378_img.jpg) + +Figure 9.6.1.2.3-1: FFT leakage into adjacent sub-band. A scatter plot showing FFT leakage into adjacent sub-band (dB wrt jammer) on the y-axis (ranging from -45 to -15) versus Time Offset (nsec) on the x-axis (ranging from 0 to 4500). The data points are scattered, with most values between -30 dB and -40 dB, indicating significant leakage across the time offset range. + +**Figure 9.6.1.2.3-1: FFT leakage with time and frequency misaligned blocker (5 RB guard band)** + +### **9.6.1.3 UE-UE adjacent channel CLI modelling** + +#### **9.6.1.3.1 Overview** + +The UE-UE adjacent channel CLI occurs when the UL transmission of the aggressor UE in a channel interferes with the DL reception of the victim UE in an adjacent channel. Unlike the case of co-channel interference, there is no need to consider any FFT selectivity in the adjacent channel scenario. Apart from the selectivity, it is necessary to account for + +the leakage from the UL sub-band into the DL sub-band caused by the transmitter. It was decided to assume the power-dependent ACLR of the aggressor UE and selectivity of the victim UE when modeling adjacent channel interference. + +To model the NF for adjacent channel CLI in a system-level simulation, a fixed value noise figure of 9dB is used. The effect of AGC is not modeled when a fixed noise figure model is used. Additionally, UE ACLR should be modeled as 30 dB at max power, improving 1 dB/dB with back-off up to a maximum of 10 dB of improvement. Therefore, when the back-off is 10 dB, the ACLR is 40 dB. When the victim and aggressor UEs are close, between 1 and 50m, and close to the cell edge, with low desired signal level, and potentially high interference level, it cannot be guaranteed that the UE receiver will operate in the linear region. + +#### 9.6.1.3.2 UE adjacent channel Tx model + +UE adjacent channel leakage ratio is used in the feasibility study for adjacent channel UE-UE CLI Tx model. Only ACLR in 1st adjacent channel was considered in the study item and ACLR in 2nd adjacent channel was precluded. In the UE Tx model, only power class 3 was assumed. UE ACLR is modelled as 30 dB at max power that improves 1dB/dB with backoff up to a maximum 10 dB of improvement. This means at 10 dB backoff the ACLR is 40 dB. Partially allocated UL subband was not considered in the system simulation. This ACLR model can be seen as frequency flat model, and the distortion is modelled as a flat power spectral density across the frequency range of the distortion. + +#### 9.6.1.3.3 UE adjacent channel Rx model + +UE adjacent channel selectivity (33dB for FR1) is used as adjacent channel UE-UE CLI model under the assumption that the blocker from adjacent channel does not exceed the maximum input level (-25 dBm) for UE. If the blocker is higher than -25dBm, it is assumed that it will result large receiver degradation and hence the RX will not correctly decode the data (100% packet loss). + +### 9.6.2 Summary + +For co-channel interference case, RAN4 concluded that the RF effect could be dominant, and the frequency offset and time offset are not significant factors influencing UE-UE interference. Furthermore, the leakage can be modelled by using the in-band emission (IBE) requirement based model. + +As for the adjacent channel case, RAN4 concluded to assume power-dependent ACLR of the aggressor UE and adjacent channel selectivity of the victim UE when modeling adjacent channel interference. + +For legacy UE, no sub-band filtering is considered. + +A fixed value noise figure of 9 dB has been used to model the AGC and NF modeling for co-channel and adjacent channel CLI in a system level simulation. + +Based on the study, reusing existing UE RF requirements is the conclusion of the study phase, since no issues related to existing UE RF requirements has been identified in the co-existence study. + +## 9.7 FR2-1 feasibility of UE aspects + +### 9.7.1 Interference analysis + +#### 9.7.1.1 UE-UE co-channel inter-subband CLI modeling + +##### 9.7.1.1.1 Receiver aspects + +###### Existing co-channel UE RX performance requirements + +For legacy UEs, the current UE RF architecture can be assumed without any RF architecture modification. Currently there are no RF requirements for UE co-channel Rx performance. + +###### Sub-band filtering and legacy UEs + +For legacy UEs, no sub-band filtering is implemented, and therefore RAN4 has not assumed any subband filtering. + +###### Thermal self-noise aspects (both adjacent channel and co-channel) + +RAN4 decided on a simple fixed-value noise figure model for the UE receiver. Generally, the receiver noise figure will vary with the input power level, however the single value noise figure model was considered sufficient for the purpose of system studies for SBFD, therefore AGC effect on self-noise is not modelled. RAN4 decided on a NF of 10dB. + +#### **Subband in-channel selectivity** + +It is worth noting that the RF degradations can cause inter-subband interference. An analysis of the FR2-1 receiver's design was conducted. Various factors, such as residual sideband, reciprocal mixing, integrated phase noise, IM3 distortion, and ADC distortions, were considered. The effect of all these distortions is lumped into a single parameter referred to as selectivity. Based on the discussion and analysis from the meeting, contributions suggested possible the sub-band selectivity values from 20 dB to 34 dB. The receiver performance is simply modelled as being 23 dB below the jammer power level. The definition of Subband in-channel selectivity is introduced for clarity in the SBFD feasibility study + +- In-channel adjacent subband selectivity is a measure of a receiver's ability to receive an NR signal on its assigned downlink subband in the presence of an interference power on the adjacent uplink subband. The value of in-channel adjacent subband selectivity is the ratio of the receiver attenuation on the assigned downlink subband to the receiver attenuation on the adjacent uplink subband. + +#### **FFT leakage and selectivity** + +In an ideal scenario, the UL transmission of the aggressor UE should not impact the DL reception of the victim UE due to the OFDM wave orthogonality. However, non-ideal FFT suppression can cause interference to the victim UE, particularly when the UL sub-band has frequency errors and is not time-synchronized with the DL sub-band. The analysis indicates that the IBE interference is higher and dominates the sub-band co-channel selectivity, and frequency and time offset are not significant factors influencing UE-UE interference. It is worth noting that the RF degradation can cause inter-subband interference as well and the impact will depend on the targeted Rx IM and EVM performance. Nonetheless, this interference will not be any worse than the selectivity value. For this reason, the 23 dB was agreed upon for modeling the inter-sub-band selectivity. + +### **9.7.1.1.2 Transmitter aspects** + +#### **Inband emissions (co-channel)** + +RAN4 has decided to use the IBE requirements from TS 38.101-2 clause 6.4.2.3.4 (power class 3 UE). It is understood these requirements are minimum performance requirements as opposed to typical requirements. RAN4 has agreed to use typical requirements for the UE parameters, however, no final conclusion has been made regarding typical values. Consequently, the formulation from the current specification is being utilized. + +It should also be assumed the LO location is in the center of the channel for the purposes of system studies in RAN4. The LO location is important as it allows placement of the image. + +Analysis indicates that the IBE interference is higher and dominates the sub-band in-channel selectivity, + +Apart from the selectivity, the degradation can be caused by transmitter leakage from the UL sub-band into the DL sub-band. For co-channel case, the leakage was agreed to be modelled using IBE based model. Additionally, the IQ image contribution for the IBE model for co-channel CLI can be ignored for the DUD configuration. + +For UE co-channel Tx model, UE IBE in TS 38.101-2 can be used in the feasibility study as shown in Table 9.7.1.1.2-1. This model consists of three parts, General, IQ image, Carrier leakage. In the system level simulation, the general and IQ image parts shall be considered, while the carrier leakage part can be ignored in the feasibility study. For DUD configuration, the IQ image from the uplink is fully contained in the UL sub-band and does not land in the DL subband, thus the IQ image can also be ignored in the simulation. + +**Table 9.7.1.1.2-1: Requirements for in-band emissions in TS 38.101-2 (For Power class 3)** + +| Parameter description | Unit | Limit (NOTE 1) | | | Applicable Frequencies | +|------------------------|------|----------------|--------------------------------|-------------------------------------|--------------------------------| +| General | dB | | | | Any non-allocated (NOTE 2) | +| | | | Output power for FR2-1 | Output Power for FR2-2 | | +| IQ Image | dB | -25 | > 10 dBm | > 8.1 dBm | Image frequencies (NOTES 2, 3) | +| | | -20 | ≤ 10 dBm | ≤ 8.1 dBm | | +| Carrier leakage | dBc | -25 | > 0 dBm | > -1.9dBm | Carrier frequency (NOTES 4, 5) | +| | | -20 | -13 dBm ≤ Output power ≤ 0 dBm | -14.9 dBm ≤ Output power ≤ -1.9 dBm | | + +## 9.7.1.2 UE-UE adjacent channel CLI modeling + +### 9.7.1.2.1 Receiver aspects + +#### Effect of adjacent channel aggressor UE jammer + +An analysis of the FR2-1 receiver's design was conducted. Various factors, such as residual sideband, reciprocal mixing, integrated phase noise, IM3 distortion, and ADC distortions, were considered. The receiver's performance is simply represented as 34 dB lower than the jammer power level. + +### 9.7.1.2.2 Transmitter aspects + +#### ACLR (adjacent channel) + +ACLR is one aspect modelled as an interference aspect from a nearby aggressor UE transmitting in an adjacent UL subband. When the victim and aggressor UEs are close, between 1 and 50m, and close to the cell edge, with low desired signal level, and high interference level, it might be the case that the victim UE will not always operate in the linear region, resulting in dominance of the ACLR from the aggressor UE. UE ACLR is modeled as 24 dB at max power, improving 1 dB/dB with backoff up to a maximum of 10 dB of improvement. Therefore, when the backoff is 10 dB, the ACLR is 34 dB. This model is an approximation of the performance of a typical UE. + +## 9.7.2 Summary + +For co-channel interference case, RAN4 concluded that the RF effect could be dominant, and the frequency offset and time offset are not significant factors influencing UE-UE interference. Furthermore, the leakage can be modelled by using the in-band emission (IBE) requirement based model. + +As for the adjacent channel case, RAN4 concluded to assume power-dependent ACLR of the aggressor UE and adjacent channel selectivity of the victim UE when modeling adjacent channel interference. + +For legacy UE, no sub-band filtering is considered. + +A fixed value noise figure of 10 dB has been used to model the AGC and NF modeling for co-channel and adjacent channel CLI in a system level simulation. + +Based on the study, reusing existing UE RF requirements is the conclusion of the study phase, since no issues related to existing UE RF requirements has been identified in the co-existence study. + +## 10 Impact on RF requirements + +### 10.1 Impact on BS RF requirements + +#### 10.1.1 General + +During Rel-18 SI, for SBFD-capable BS, RF requirement was only studied based on the semi-static configuration of subband time and frequency location, which is supported by SBFD-capable BS. RAN4 mainly focused on the following multi-carrier configuration for SBFD-capable BS: + +- SBFD operates in only one BS carrier, and legacy TDD operates in other intra-band BS carrier(s) contiguous or non-contiguous to the SBFD carrier. + +During Rel-18 SI, RAN4 didn't study the following multi-carrier configuration for SBFD-capable BS: + +- SBFD operates in more than one BS carriers, and legacy TDD operates in the other intra-band BS carrier(s) (if any), which is contiguous or non-contiguous to the SBFD carriers. + +Regarding the baseline assumption for the maximum number of UL sub-bands of SBFD capable BS, RAN4 agreed to restrict the maximum number to be one in an SBFD symbol/slot within a TDD carrier. In addition, RAN4 agreed that RF requirement impacts for SBFD operation in symbols/slots configured as UL in *TDD-UL-DL-ConfigCommon* is treated as 2nd priority. + +For SBFD-capable BS, the existing RF requirements shall be applied in the OFDM symbols/slots others than SBFD symbols/slots and RF requirement impacts in the SBFD symbols/slots will be further clarified in details in the following sections. + +Some requirements might need to be tested in both SBFD and non-SBFD slots even when the requirement is the same. The reason would be if it could be expected that the BS operating condition may differ between SBFD and non-SBFD slots. Whether to apply a test in both SBFD and non-SBFD slots should be discussed on a requirement by requirement basis in the conformance part of a WI. + +#### 10.1.2 Impact on BS TX requirements + +##### 10.1.2.1 Base Station output power and radiated transmit power + +Since configuration (e.g. antenna, power configuration etc) between SBFD and non-SBFD symbols/slots might be different, RAN4 reached the following consensus for the BS RF requirement of BS output power for both conducted and OTA output power: + +- It is allowed to have the different conducted declaration for normal DL symbols/slots and SBFD DL symbols/slots. +- It is allowed to have different EIRP/TRP declaration (for level and direction) for normal DL symbols/slots and SBFD DL symbols/slots. +- Accuracy requirement for TRP/EIRP and conducted power shall be the same for normal DL symbols/slots and SBFD DL symbols/slots. + +##### 10.1.2.2 Output power dynamics + +Regarding the output power dynamic requirement, which mainly consists of RE power control dynamic range requirement and total dynamic range requirement, RAN4 reached the following consensus: + +- To reuse the existing RE power control dynamic range requirement for SBFD BS; +- The total dynamic range requirement is applicable for SBFD-capable BS during normal DL symbols/slots, it is agreed to define the output power dynamic range requirement for SBFD as the ratio of the declared rated output power with all DL RBs active for SBFD (maximum) and the same single RB power as non-SBFD (minimum). + +### 10.1.2.3 Transmit ON/OFF power + +Regarding the transmitter ON/OFF power requirement, RAN4 mainly focus on the ON-OFF time mask and concluded that transmit ON/OFF power requirement is not applicable within SBFD time slot. + +### 10.1.2.4 Transmitted signal quality + +Regarding the transmitter signal quality, RAN4 agreed that all the existing requirement for frequency error, modulation quality (EVM) and time alignment error (TAE) shall also be applied to BS in SBFD symbols/slots. + +- Further discuss the joint measurement for normal DL symbols/slots and SBFD DL symbols/slots during WI phase. + +### 10.1.2.5 Unwanted emissions + +Regarding the unwanted emission requirement, it mainly consist of OBW requirement, ACLR requirement, OBUE requirement, transmitter spurious emission requirement and co-location and coexistence requirement, RAN4 reached the following consensus for SBFD-capable BS respectively: + +- For BS OBW requirement, the existing OBW requirement shall be applied for the whole BS channel bandwidth in SBFD symbols/slots instead of DL sub-band. +- For ACLR requirement, it shall be defined outside of the whole carrier instead of sub-band for SBFD DL symbols/slots and ACLR requirement is still defined as the ratio of sum of TX power within the whole carrier to the adjacent carrier. +- For OBUE requirement, the RF bandwidth edge from which OBUE is defined is the edge of the carrier (same for both SBFD and non-SBFD symbols/slots). +- For transmitter spurious emission requirement, all the existing requirements shall also be applied to SBFD-capable BS in SBFD symbols/slots. The requirement of protection of the BS receiver of own or different BS is not applicable for TDD operation. +- For inter-band co-location and co-existence requirement or SBFD-capable BS, it was agreed not to update on existing inter-band co-location requirements and manufacturer will declare whether support co-location requirements in SBFD symbols/slots. + +### 10.1.2.6 Transmitter intermodulation + +For transmitter intermodulation requirement for SBFD-capable BS, it was concluded that further study is needed on the following aspects in the normative phase: + +- whether the transmitter intermodulation requirement is applicable in SBFD slots/symbols. +- the applicable co-location coupling loss assumption and the applicable receiver degradation for the transmitter intermodulation requirement, if transmitter intermodulation requirement is applicable in SBFD slots/symbols + +## 10.1.3 Impact on BS RX requirements + +### 10.1.3.1 Reference sensitivity level and OTA sensitivity + +Regarding Reference sensitivity requirement for SBFD-capable BS, due to the self interference caused internally to receiver side, RAN4 reached the following consensus: + +- For BS type 1-H if supported: The existing requirement for conducted reference sensitivity level shall also be applied to BS in SBFD symbols, i.e, no sensitivity degradation is allowed. +- Otherwise, OTA sensitivity requirement could be derived based on the following equation: + +-G + +- The candidate value [0.5~1.0]dB degradation and final value will be specified in the WI phase. +- The following aspects need more discussion during a WI phase + +- The declaration of maximum TRP for the requirement of OTA sensitivity within SBFD time slot +- If OTA sensitivity should be defined considering all of the scenarios including self-interference, inter-site interference and inter-sector interference. + +### 10.1.3.2 Dynamic range + +Regarding the dynamic range requirement, this requirement is still applicable for SBFD-capable BS. The IoT level and wanted signal power level could be further discussed in the WI phase. + +### 10.1.3.3 In-band selectivity and blocking + +Regarding ACS requirement and in-band blocking requirement, RAN4 reached the following consensus: + +- ACS requirement and the interference level shall be determined by RAN4 co-existence study, and for the definition of ACS requirement: + - Conducted ACS: Take the existing wanted signal of ACS requirement by using the existing reference sensitivity level. + - OTA ACS: The OTA sensitivity degradation shall be taken into account to determine the level of wanted signal and interference signal mean power. +- In-band blocking requirement and the interference level shall be determined by RAN4 co-existence study, and for the definition of In-band blocking requirement: + - Conducted In-band blocking: Take the existing wanted signal of In-band blocking requirement by using the existing reference sensitivity level. + - OTA In-band blocking: The OTA sensitivity degradation shall be taken into account to determine the level of wanted signal and interference signal mean power. + - For in-band selectivity and blocking, the requirements shall be defined out of the BS channel bandwidth instead of uplink subband bandwidth. + +### 10.1.3.4 Out-of-band blocking + +Regarding Out-of-band blocking requirement, the existing OOB blocking requirement is still applicable for SBFD-capable BS except for OTA sensitivity degradation with the power level of wanted signal taken into account. + +### 10.1.3.5 Receiver spurious emissions + +Regarding the receiver spurious emission requirement, apart from existing requirements for normal reception on UL symbols/slots, it's not necessary to specify additional receiver spurious emissions requirement for SBFD operation in SBFD symbols/slots. + +### 10.1.3.6 Receiver intermodulation + +Regarding the receiver intermodulation requirement, in general, RX intermodulation requirement and the interference levels shall be determined by RAN4 co-existence study, and for the definition of RX intermodulation requirement RAN4 reached the following consensus: + +- Conducted RX intermodulation: Adopt the existing wanted signal of RX intermodulation requirement by using the existing reference sensitivity level. +- OTA RX intermodulation: The OTA sensitivity degradation shall be taken into account to determine the level of wanted signal and interference signal mean power. + +### 10.1.3.7 In-channel selectivity + +Regarding the receiver in-channel selectivity requirement, the requirement shall be studied based on that the wanted signal and UL interfering signal shall be located in the configured UL subband, and the wanted signal and interfering signal levels could be further studied in the WI phase. + +## 10.1.4 Potentially new requirements for SBFD operation + +### 10.1.4.1 Transmitter transient period + +For transmitter transient period between SBFD and non-SBFD or SBFD reconfigurations if needed, the requirement shall be introduced to BS in SBFD symbols/slots, by defining the transient period as the time period which the transmitter is changing from the SBFD operation to non-SBFD operation or vice versa, or during SBFD reconfigurations. + +Regarding the transition period requirement, RAN4 mainly focus on the transition period related with SBFD. Based on the RAN4 study, between the non-SBFD slot and SBFD slot and vice versa, a transition period is needed. If the SBFD configuration between adjacent SBFD slots is the same, then no transition period is needed. + +### 10.1.4.2 In-channel adjacent subband leakage ratio + +For the potential new requirement of in-channel adjacent subband leakage ratio, it is concluded that further study is needed on the necessity of this requirement in normative phase. + +### 10.1.4.3 In-channel adjacent subband Blocking and adjacent subband selectivity + +For the potential new requirements of in-channel adjacent subband blocking and selectivity, it is concluded that further study is needed on the necessity of this requirement in normative phase. + +## 10.2 Impact on UE RF requirements + +RAN4 has analyzed inter-UE co-channel inter-subband CLI modeling and adjacent channel CLI modelling. In Table 10.2-1, in-channel RF assumptions (e.g., IBE and subband selectivity) and adjacent channel RF assumptions (e.g., ACLR and ACS) for the coexistence study are presented for UE Tx/Rx interference modelling. + +**Table 10.2-1: UE RF assumptions for interference modelling** + +| In-channel RF assumptions | FR1 | FR2-1 | +|----------------------------------------|---------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------| +| Tx Model: IBE | Existing UE IBE requirement in TS38.101-1 | Existing UE IBE requirement in TS38.101-1 | +| Rx Model: Subband Selectivity | 33dB for simulation usage purpose | 23 dB for simulation usage purpose | +| Adjacent channel RF assumptions | FR1 | FR2-1 | +| Tx Model: ACLR | 30 dB at max power that improves 1dB/dB with backoff up to a maximum 10 dB of improvement | 24 dB at max power that improves 1dB/dB with backoff up to a maximum 10 dB of improvement | +| Rx Model: ACS | 33 dB under the assumption that the blocker from adjacent channel does not exceed the maximum input level (-25 dBm) | 23 dB under the assumption that the blocker from adjacent channel does not exceed the maximum input level (-25 dBm) | + +For UE in-channel RF assumptions, existing UE IBE requirements in TS 38.101-1/2 were assumed for the Tx model; for the Rx model, RAN4 defined subband selectivity for co-existence simulation purpose, and the value of 33dB for FR1 and 23dB for FR2-1 are derived from the performance of typical user. In the existing 3GPP specification, subband selectivity is not specified as UE RF requirement and it is proposed for the co-existence study usage only in this study item. + +For UE adjacent channel RF assumptions, the values of ACLR/ACS for FR1/FR2 are based on the existing UE RF requirements. The existing ACLR requirement was defined with the assumption of the maximum output power. In order to model typical UE performance, this model was revised considering the cases in which UE transmit power is less than the maximum power. + +Based on the study, existing UE RF requirements has been applied as default assumptions for study phase conclusion, since no issues related to existing UE RF requirements has been identified in the co-existence study. + +# 11 Adjacent channel co-existence evaluation results + +## 11.1 Introduction + +The adjacent channel co-existence studies were performed to the deployment scenarios described in Table 11.1-1 below. The co-existence cases are described in the Table 11.1-2 below, and they were performed for each scenario listed in Table 11.1-1. The detailed assumptions associated with these scenarios and cases can be found in Annex E. + +**Table 11.1-1: Adjacent channel co-existence scenarios** + +| Scenario | FR | Aggressor | Victim | +|----------------|-------|---------------|---------------| +| 1 | FR1 | Urban Macro | Urban Macro | +| 2 | FR1 | Urban Hotspot | Urban Hotspot | +| 3 | FR1 | Indoor | Indoor | +| 4 | FR1 | Urban Macro | Micro | +| 5 | FR1 | Micro | Micro | +| 6 | FR2-1 | Urban Macro | Urban Macro | +| 7 1 | FR2-1 | Urban Hotspot | Urban Hotspot | +| 8 | FR2-1 | Urban Dense | Urban Dense | +| 9 | FR2-1 | Indoor | Indoor | + +Note 1: This scenario has been down-selected. + +**Table 11.1-2: Adjacent channel co-existence cases** + +| Case | Aggressor | Victim | Slot allocation | | +|------|-----------|--------|-------------------------------------------------------------------------------------|----------------------------------------------------------------------------------| +| | | | Aggressor | Victim | +| 1 | SBFD | TDD DL |

Image: Slot allocation for Case 1 Aggressor: D (yellow) followed by U (blue)

|

Image: Slot allocation for Case 1 Victim: D (yellow)

| +| 2 | SBFD | TDD UL |

Image: Slot allocation for Case 2 Aggressor: D (yellow) followed by U (blue)

|

Image: Slot allocation for Case 2 Victim: U (blue)

| +| 3 | TDD DL | SBFD |

Image: Slot allocation for Case 3 Aggressor: D (yellow)

|

Image: Slot allocation for Case 3 Victim: D (yellow) followed by U (blue)

| +| 4 | TDD UL | SBFD |

Image: Slot allocation for Case 4 Aggressor: U (blue)

|

Image: Slot allocation for Case 4 Victim: D (yellow) followed by U (blue)

| + +Note: Case 3 and Case 4 are down-selected for Scenario 4. + +The Urban Hotspot reuses most parameter assumptions as Urban Macro, except that Urban Macro adopts random dropping method for UE while Urban Hotspot adopts cluster-based dropping method for UE. Other differences are described in Annex E, in Table E.2.1-1, Table E.2.1-2, and Table E.2.1-3. + +The co-existence evaluation captures cases where TDD and SBFD are both victim and aggressor networks. This to evaluate impact on legacy TDD networks if SBFD is introduced in an adjacent channel as well as to understand the impact of legacy TDD network on SBFD network, as described in Annex E, Table E.1-2. It is worth noting that RAN4 has only considered the case of {D, U} as an SBFD configuration as it is comparable to the {D, U, D} SBFD configuration in terms of performance (based on the agreed RAN4 models and parameters related to leakage). + +Additionally, it should be noted that the RAN4 co-existence studies have special assumptions due to the adopted simulation methodologies such as: + +- Power control scheme is only used to compensate path loss. That's the reason why final SINR for UL is less than assumed target SINR. But commercial UE UL SINR could meet target SINR value according to the power control scheme in TS 38.213. +- It is assumed that all the slots configurations are the same with the time-invariant ACLR modelling assumption. Compared with the average throughput over all time slots with different configuration, this is the worst case with largest degradation value. + +Moreover, in the following sections, all the throughput degradation data are given in a range, where these data are defined as follows: + +- The {positive number} means the co-existence evaluation shows throughput loss; +- The {negative number} means the co-existence evaluation shows throughput gain; + +- The {n/a} means the co-existence evaluation finds the performance basis have no throughput, thus throughput degradation percentage cannot be mathematically calculated from such basis. + +## 11.2 Summary of all simulation results + +The simulation results submitted for the adjacent channel co-existence study from all contributing companies in RAN4 were summarized into three attached files in [69] to this report. + +The basic structure and outline of these summary documents are described below for better readability. + +- The word document “Summary of all simulation results” provides the summary results for all 8 scenarios and 4 cases defined in Table 11.1-1 and Table 11.1-2. And this file summarizes the results with the following format: + - For scenario [num], Case [num], Victim [link type], [assumption 1, 2, 3...], [num] companies show simulation results: + - Average and 5th percentile (at cell-edge) SINR/throughput degradation. + - For ACIR is [Relative ACIR / +2 / +4 / +6 / +8 dB], throughput loss is in the range [lowest loss, highest loss], and Median is [median loss]. Besides, [num] companies provides N/A. + - Results with four optional assumptions: BS antenna configuration, BS Tx power level, grid shift, and noise figure enhancement. +- The excel document “Summary of all simulation results” provides the summary results for all 8 scenarios and 4 cases defined in Table 11.1-1 and Table 11.1-2. And this file summarizes the results with the following format: + - One sheet covers one scenario with all 4 cases, and in each sheet the table is shown as below: + +| Case | Victim | Antenna config | Grid shift | gNB Tx power | Enhanced NF | Number of company | ACIR value | Performance metric | Max | Min | Median | Nan number | +|------|--------|----------------|------------|--------------|-------------|-------------------|------------|--------------------|-----|-----|--------|------------| +|------|--------|----------------|------------|--------------|-------------|-------------------|------------|--------------------|-----|-----|--------|------------| + +- The excel document “Collection of simulation results from all companies” provides the break-down of detailed results for all 8 scenarios and 4 cases defined in Table 11.1-1 and Table 11.1-2. + +Additionally, the simulation results carried out for the co-existence cases/scenarios are provided for the baseline ACIR as well as enhanced ACIR. The former (i.e., baseline ACIR, termed Relative ACIR in the simulation compilation file) is equivalent to the ACIR when considering the baseline ACLR and ACS as provided in Annex E, following the below formulation with all parameters in linear scale: + +The baseline ACIR is derived from the ACLR and ACS values listed in Annex E, in Tables E.2.3-1, E.2.3-2, and E.2.4-1. On the other hand, the enhanced ACIR that RAN4 has considered in the coexistence study represents the case where the baseline ACIR is enhanced with x dB, ranging from 2dB till 8dB, while some numbers can't be met because ACIR enhancement can be limited by the ACLR/ACS of the legacy TDD network or UE operating in the adjacent channel as highlighted below for the different cases: + +- Case 1 (Legacy UE as a victim and SBFD network as an aggressor): ACIR enhancements can be done. Legacy UE ACS is assumed to be fixed (33 dB in FR1 and 23 dB in FR2-1). However, the BS-to-UE ACIR enhancement cannot exceed 0.3 dB in FR1 and 1.2 dB in FR2-1 based on the limitation of the UE ACS simulation assumption. +- Case 2 (Legacy BS as a victim and SBFD network as aggressor): ACIR enhancements can be done. Legacy BS ACS is assumed to be fixed (50 dB in FR1 and 24 dB in FR2-1). However, the BS-to-BS ACIR enhancement cannot exceed 6.2 dB in FR1 and 1.5 dB in FR2-1 based on the limitation of the legacy BS ACS simulation assumption. +- Case 3 (SBFD-capable BS as a victim and legacy BS as aggressor): ACIR enhancements can be done. Legacy BS ACLR is assumed to be fixed (50 dB in FR1 and 24 dB in FR2-1). However, the BS-to-BS ACIR enhancement cannot exceed 1.2 dB in FR1 and 5.5 dB in FR2-1 based on the limitation of the legacy BS ACLR simulation assumption. + +- Case 4 (SBFD-aware UE as a victim and legacy UE as aggressor): ACIR enhancements can be done. Legacy TDD UE ACLR is assumed to be fixed (30 dB in FR1 and 24 dB in FR2-1). However, the UE-to-BS ACIR enhancement is 0 dB in FR1 and cannot exceed 3.0 dB in FR2-1 based on the limitation of the legacy UE ACS. + +Furthermore, the above mentioned ACIR enhancement limitations were only derived from the simulation assumptions of legacy TDD BS and UE devices adopted in RAN4 co-existence study, which limitations can be further studied for new frequency bands or band-specific assumptions. It is possible to have the ACIR enhancement to exceed those limitations under certain conditions, if we consider the SBFD deployment in certain frequency bands where the TDD legacy network devices have better performance. + +It should be noted that the “baseline assumptions” mentioned Section 11 are defined in Annex E. + +## 11.3 Conclusion + +This section will capture adjacent channel co-existence simulation results categorized by cases and scenarios. + +### 11.3.1 Case 1: aggressor SBFD DU victim NR TDD DL + +Case 1 considers legacy TDD in DL slot as a victim while SBFD is operating in the adjacent channel for both FR1 and FR2-1. The conclusions are listed per scenario in Table 11.3.1-1. + +**Table 11.3.1-1: Case 1 co-existence conclusions** + +| Deployment Scenario (Aggressor -> Victim) | Frequency range | Co-existence conclusion | +|------------------------------------------------------------------------|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Urban Macro -> Urban Macro
Scenario 1 and
Scenario 6 | FR1 and FR2-1 | No DL throughput degradation on the victim legacy TDD DL network for both average throughput and cell edge throughput is observed for different BS Tx powers (46dBm to 53 dBm for FR1 and 30 dBm for FR2-1), grid-shifts (5% to 100%), and different SBFD BS antenna configurations. | +| Urban Hotspot -> Urban Hotspot
Scenario 2 | FR1 | DL throughput degradation is observed only at cell edge due to inter-UE CLI for different grid-shifts (5% to 100%) and BS Tx powers (49 dBm to 53 dBm). | +| Urban Macro -> Urban Micro
Scenario 4 | FR1 | No DL throughput degradation for both average throughput and cell edge throughput is observed. | +| Indoor -> Indoor
Scenario 3 and
Scenario 9 | FR1 and FR2-1 | | +| Urban Micro/Dense -> Urban Micro/Dense
Scenario 5 and
Scenario 8 | FR1 and FR2-1 | | + +### 11.3.2 Case 2: aggressor SBFD DU victim NR TDD UL + +Case 2 considers legacy TDD in UL slot as a victim while SBFD is operating in the UL slot in the adjacent channel for both FR1 and FR2-1. The conclusions are listed per scenario in Table 11.3.2-1. + +**Table 11.3.2-1: Case 2 co-existence conclusions** + +| Deployment Scenario (Aggressor -> Victim) | Frequency range | Co-existence conclusion | +|--------------------------------------------|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Urban Macro -> Urban Macro Scenario 1 | FR1 |

The TDD UL has significant throughput degradation for different SBFD BS antenna configuration and different BS Tx powers.

  • - The cell edge throughput degradation is worse than the average throughput degradation.
  • - The throughput degradation is due to the inter-BS ACI introduced by SBFD, which increases as grid-shift (BS-to-BS distance) decreases in scenario 1, 2 and 5. In scenario 4 (UMa-to-UMi scenario), the degradation increases and then decreases due to the relative distance and elevation angle between UMa and UMi base stations. This is a result of the grid-shift reduction and consequent changes in antenna discrimination.
  • - The throughput degradation increases with SBFD BS Tx power.
  • - SBFD BS antenna configuration slightly impacts the throughput degradation.
| +| Urban Hotspot -> Urban Hotspot Scenario 2 | | | +| Urban Macro -> Urban Micro Scenario 4 | | | +| Urban Micro -> Urban Micro Scenario 5 | | | +| Indoor -> Indoor Scenario 3 and Scenario 9 | FR1 and FR2-1 | No TDD UL throughput degradation is observed. | +| Urban Macro -> Urban Macro Scenario 6 | FR2-1 | TDD UL throughput degradation is observed at cell edge, no strong degradation is observed for the average throughput. | +| Urban Dense -> Urban Dense Scenario 8 | | | + +### 11.3.3 Case 3: aggressor NR TDD DL victim SBFD DU + +Case 3 considers SBFD as a victim while NR TDD is operating DL in the adjacent channel for both FR1 and FR2-1. The conclusions are listed per scenario for SBFD DL in Table 11.3.3-1 and for SBFD UL in Table 11.3.3-2. + +**Table 11.3.3-1: Case 3 SBFD DL co-existence conclusions** + +| Deployment Scenario (Aggressor -> Victim) | Frequency range | Co-existence conclusion | +|------------------------------------------------------------------|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Urban Macro -> Urban Macro Scenario 1 and Scenario 6 | FR1 and FR2-1 | No observed throughput degradation on the SBFD DL for both average throughput and cell edge throughput for different BS Tx powers, ranging (46dBm to 53 dBm for FR1 and 30 dBm for FR2-1), grid-shifts (5% to 100%), and different SBFD BS antenna configurations. | +| Urban Hotspot -> Urban Hotspot (N/A for FR2-1) Scenario 2 | | | +| Indoor -> Indoor Scenario 3 and Scenario 9 | | | +| Urban Micro/Dense -> Urban Micro/Dense Scenario 5 and Scenario 8 | | | + +**Table 11.3.3-2: Case 3 SBFD UL co-existence conclusions** + +| Deployment Scenario (Aggressor -> Victim) | Frequency range | Co-existence conclusion | +|------------------------------------------------------------------------|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Urban Macro -> Urban Macro
Scenario 1 and
Scenario 6 | FR1 | Under baseline assumptions, SBFD UL throughput degradation is observed only for cell edge throughput, and minor degradation but acceptable to some companies for average throughput. With other assumptions (higher BS Tx power and lower grid-shifts), the degradation is increased for cell edge throughput and average throughput. | +| | FR2-1 | Under baseline assumptions, no degradation on the SBFD UL is observed for both cell edge throughput and average throughput. Throughput loss is observed with higher BS Tx power and lower grid-shifts. | +| Urban Hotspot -> Urban Hotspot
Scenario 2 | FR1 | Under baseline assumptions, SBFD UL throughput degradation is observed at cell edge throughput and average throughput. With higher BS Tx power and lower grid-shifts, the degradation is increased. | +| Indoor -> Indoor
Scenario 3 and
Scenario 9 | FR1 and FR2-1 | No SBFD UL throughput degradation for both average throughput and cell edge throughput is observed. | +| Urban Micro/Dense -> Urban Micro/Dense
Scenario 5 and
Scenario 8 | FR1 | Under FR1 Urban micro 38dBm Tx power assumption, no degradation on the SBFD UL is observed for both cell edge throughput and average throughput. Throughput loss is observed with higher BS Tx power (46dBm) and lower grid shifts. | +| | FR2-1 | Under baseline assumptions, SBFD UL throughput degradation is observed only for cell edge throughput and no degradation is observed for average throughput. | + +### 11.3.4 Case 4: aggressor NR TDD UL victim SBFD DU + +Case 4 considers SBFD as a victim while NR TDD is operating UL in the adjacent channel for both FR1 and FR2-1. The conclusions are listed per scenario for SBFD DL in Table 11.3.4-1 and for SBFD UL in Table 11.3.4-2. + +**Table 11.3.4-1: Case 4 SBFD DL co-existence conclusions** + +| Deployment Scenario (Aggressor -> Victim) | Frequency range | Co-existence conclusion | +|------------------------------------------------------------------------|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Urban Macro -> Urban Macro
Scenario 1 and
Scenario 6 | FR1 and FR2-1 | No observed throughput degradation on the SBFD DL for both average throughput and cell edge throughput respectively for different BS Tx powers (ranging from 46dBm to 53 dBm for FR1 and 30 dBm for FR2-1), grid-shifts (5% to 100%), and SBFD BS antenna configurations. | +| Indoor -> Indoor
Scenario 3 and
Scenario 9 | | | +| Urban Micro/Dense -> Urban Micro/Dense
Scenario 5 and
Scenario 8 | | | +| Urban Hotspot -> Urban Hotspot
Scenario 2 | FR1 | Some companies' results show SBFD DL throughput degradation is observed only for cell edge throughput due to inter-UE CLI for different grid-shifts (5% to 100%), BS Tx powers (46dBm to 53 dBm) and for all antenna configurations. However more companies show that there is no observed degradation for cell edge throughput and cell average throughput for 100% grid-shift, 49dBm BS Tx power and SBFD BS antenna configuration 2. | + +**Table 11.3.4-2: Case 4 SBFD UL co-existence conclusions** + +| Deployment Scenario (Aggressor -> Victim) | Frequency range | Co-existence conclusion | +|---------------------------------------------------------------------|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Urban Macro -> Urban Macro
Scenario 1 and Scenario 6 | FR1 and FR2-1 | No observed throughput degradation on the SBFD UL for both average throughput and cell edge throughput for different BS Tx powers (ranging from 46dBm to 53 dBm for FR1 and 30 dBm for FR2-1), grid-shifts (5% to 100%), and SBFD BS antenna configurations. | +| Indoor -> Indoor
Scenario 3 and Scenario 9 | | | +| Urban Micro/Dense -> Urban Micro/Dense
Scenario 5 and Scenario 8 | | | +| Urban Hotspot -> Urban Hotspot
Scenario 2 | | | + +## 11.3.5 General remarks on coexistence findings + +For the cases where no throughput degradation has been observed assuming SBFD-capable BS and SBFD-aware UE having same ACLR or ACS as legacy TDD BS and UE, no additional coexistence measures are required for SBFD deployment. On the other hand, for other cases where throughput degradation has been observed, interference mitigation techniques will need to be considered. + +# 12 Regulatory aspects for deploying the duplex enhancements in TDD unpaired spectrum + +## 12.1 ITU Region 1 + +### 12.1.1 Europe + +The European Conference of Postal and Telecommunications Administrations (CEPT) made coexistence studies with adjacent services assuming a certain DL/UL ratio for International Mobile Telecommunications (IMT) TDD bands, e.g., 3.4 – 3.8 GHz band in Europe [51]. The evolution of NR duplex operation would bring changes to the frame structures of legacy TDD operation and consequently may affect the outcomes of the coexistence studies and, consequently, the regulated license conditions. + +To address the cross-border issue and facilitate coordination, the Electronics Communications Committee (ECC) recommended the usage of two frame structures in the 3.4 – 3.8 GHz frequency band [52]. Additionally, a technique for cross-border interference mitigation was studied in [53] based on DL symbol blanking on overlapping UL/DL resources between two geographically adjacent networks. + +However, enabling operation with various TDD patterns and removing the need of synchronized networks, CEPT has specified additional baselines for unsynchronized or semi-unsynchronized networks. Nevertheless, those baselines are more stringent, making the BS design more challenging, impacting final cost and possibly product's volume and weight. As an example, for the 3.4 – 3.8 GHz band, inside the band, ECC specified below and above the block edge a restricted baseline of -34 dBm/5MHz EIRP for non AAS BS or -43 dBm/MHz TRP for AAS BS [54] operators, the situation may be reported to the competent authority for resolution. + +## 12.2 ITU Region 2 + +### 12.2.1 North America + +In the United States, TDD network operators operating in proximal geographic areas in adjacent bands are encouraged and sometimes required to synchronize their networks and coordinate their TDD configurations to avoid mutual interference. Unsynchronized operation is allowed, more stringent regulation parameters have not been specified for such case but, again, operators would have to work their differences to avoid any claim to Federal Communications Commission (FCC) and Innovation, Science and Economic Development Canada (ISED). FCC requires 3450 – 3550 + +MHz service (AMBIT band) licensees to negotiate with 3550 – 3700 MHz (CBRS band) licensees to enable TDD synchronization across these services [55]-[56]. Notice that the term TDD synchronization refers to aligning TDD uplink and downlink slots. FCC recognizes the potential for harmful interference from a high-power AMBIT band downlink transmission to a CBRS band uplink. Licensees in the 3700 – 3980 MHz band (C-Band) are encouraged to explore synchronization of TDD operations to minimize interference between adjacent band services [57]. + +The shared band 48/n48 (3550 – 3700 MHz), also known as the CBRS band, requires spectrum sharing among three tiers of users controlled by one or multiple spectrum access systems (SASs) [58]. Coexistence, including TDD synchronization, among cellular users within the band is supported by OnGo Alliance coexistence requirements set forth in OnGo-TS-2001 [59]. + +The ISED Canada is reallocating portions of the 3500 to 4200 MHz band as TDD bands for cellular use. The ISED is considering TDD synchronization as a means of facilitating sharing and co-existence with adjacent band services [60]. + +Currently there are no specific regulatory requirements for SBFD operation in North America. Some SBFD operations result in similar interference scenarios as found in unsynchronized TDD systems. The potential coexistence risk introduced by SBFD may break the standard body agreement on TDD synchronization by OnGo Alliance coexistence requirements set forth in OnGo-TS-2001 [59]. + +## 12.3 ITU Region 3 + +### 12.3.1 Australia + +In Australia there are frame structure requirements which only apply when interference occurs between licences and there is no agreement between licensees on how to resolve it. Operators can use different frame structures if there are no issues. + +### 12.3.2 China + +In China, spectrum is allocated with clearly stating it for TDD or FDD operation. Besides, spectrum is allocated to operators with specified RF requirements. + +For the same TDD operation band, now only synchronization operation is allowed between operators owning adjacent carriers among one TDD operation band. The Ministry of Industry and Information Technology (MIIT) has specified RF requirements assuming the synchronization operation. There are no regulatory requirements about the TDD pattern choice, instead, operators will determine final TDD pattern provided adjacent channel network are synchronized operation. + +For adjacent TDD operation band and FDD operation band, inter-operator gNB-gNB CLI occurs. To avoid such interference, MIIT specify some interference mitigation scheme, e.g., frequency guard band and minimum spatial isolation requirement. One example is the interference between band 39 and band 1/band 3. To avoid severe gNB-to-gNB interference, a 5MHz frequency guard band is reserved between two adjacent operation bands. Besides, 50dB MCL is required between different operators' gNB. + +There are no SBFD regulatory requirements in China until now. MIIT mainly cares interference between different operators. Necessary interference coordination mechanism and solutions may be proposed by MIIT to avoid interference before any SBFD deployment. + +### 12.3.3 India + +In India no frame structure is mandated. In case operators have incompatible frame structures resulting in interference then the responsibility of mitigating interference falls amongst the operators. + +### 12.3.4 Japan + +No TDD pattern has been mandated in Japan, but operators are required to coordinate their TDD patterns. Operators are allowed to use unsynchronized operation if operators can get necessary agreements with the stakeholders. + +### 12.3.5 Korea + +In Korea, there is no frame structure that is mandated. The principle is that the operators should confer among themselves to solve any coexistence problems, if such problems exist, and implement an interference protection and avoidance plan in the “Frequency Use Plan”. + +According to “Ministry of Science and ICT Announcement No. 2018-235,” frequency allocation notice for mobile communications (3.5GHz), it was an official requirement in Korea that operators have to present a “Frequency Use Plan”, in which the solution or network construction plan to avoid interference must be officially listed [61]. + +Based on Article 11 of Enforcement Decree Of The Radio Waves Act in Korea, “Matters related to frequency use and technology methods,” a new regulatory requirement has been adopted whenever a new spectrum is introduced regardless the band is licensed or unlicensed. Additionally, the regulatory requirement clearly describes what multiplexing technology, modulation technology, frequency band, occupied bandwidth, etc. are used. MSIT in Korea could review the SBFD as a new multiplexing technology, in which new regulatory requirement might be introduced [62]. + +### 12.3.6 New Zealand + +In New Zealand a TDD pattern has been mandated and in addition the networks must be time synchronised. Operator deployments that do not conform to the synchronisation requirement must not interfere with deployments that are conforming with the described synchronisation requirements, and therefore cannot claim protection from interference [63]. Therefore, it will be difficult to introduce SBFD without a regulatory rule change. + +## 12.4 Summary + +At present, many bands are issued by regulators with clearly defined duplex modes, i.e., FDD or TDD, and probably SDL or SUL. The evolution of NR duplex operation, as a new technology, may require regulators to consider the new regulatory requirements and/or update the ruling. + +At least for regions studied so far, there is no regulation rule directly related to SBFD operation. The evolution of NR duplex operation would bring changes to the frame structures of legacy TDD operation, which has been assumed in many regions for coexistence. As a result, rules related to TDD synchronization and interference to incumbent services may be impacted. + +Regulators try to harmonize spectrum usage and pay attention to the use of new technologies that might create interference to incumbent services operating in or adjacent to the considered spectrum. When allocating spectrum to IMT TDD operation, many regulators made coexistence studies with incumbent services assuming a certain TDD configuration. Based on the conclusions of those studies, regulators have then specified the corresponding parameters to enable such deployment. Existing 3GPP specifications e.g., TS 38.104, assume the TDD base stations deployed in the same geographical area and using the same or adjacent operating bands are synchronized. Unsynchronized operations have not been considered and so, no specific RF requirements are defined for the unsynchronized operations. + +Some regulators and regional organizations (e.g., CEPT ECC in Europe) have recommended specific TDD frame structure usage to facilitate coordination, addressing the cross-border issues between countries. In most studied regions, to avoid cross-link interference situations, regulatory conditions at the national/regional level define the common TDD frame structures for multiple operators’ operations in or adjacent to the considered spectrum, or administrations ask MNOs to agree on a common frame structure for Macro cellular deployments. + +To enable unsynchronized TDD deployments without creating interference in the network(s) deployed in the same geographic areas, some regulators have specified more stringent parameters (e.g., CEPT specified below and above the block edge a restricted baseline of -34dBm/5 MHz EIRP for non-AAS BS or -43dBm/MHz TRP for AAS BS), which usually increases BS design’s complexity. For adjacent TDD operation band and FDD operation band, some regulators (e.g., MIIT in China) specify interference mitigation scheme such as guard band and minimum spatial isolation requirement. + +Nevertheless, when deployed in environments that guarantee and prevent any interference in the adjacent spectrum (e.g., isolated indoor deployment), neither specific condition nor recommendation has been specified by the Regulators, allowing any TDD deployment in such environments as long as no interference disturbs adjacent services. For example, in a single operator’s TDD network, there may be no limitation on the frame structure and it is up to the operator’s choice. It is already possible today to use different TDD frame structures for isolated deployment, e.g., isolated indoor factory, as long as the obligation to avoid interference is guaranteed. For such types of deployments, existing regulation rules should not be impacted when operating SBFD. + +SBFD operation would allow simultaneous transmission and reception in different sub-bands within the same carrier. New regulatory requirements or changes to current regulations may be needed to allow SBFD operation for multiple operators’ deployment. + +## 13 Conclusions and recommendations + +### 13.1 SBFD + +#### 13.1.1 RAN1 + +##### 13.1.1.1 UPT performance + +All conclusions are based on SLS evaluation results with no less than 3 sources for single operator scenarios (SBFD deployment case 1) and no less than 2 sources for 2-Layer scenarios (SBFD deployment case 3-2) and two operator scenarios (SBFD deployment case 4), respectively. + +RAN1 did not draw any conclusion on the performance of SBFD operation with “same total number of antenna elements and half the total number of TxRUs” and “same total number of antenna elements and same total number of TxRUs” with respect to semi-static TDD due to fewer than 3 sources for SBFD deployment case 1 and 2 sources for SBFD deployment case 3-2 and SBFD deployment case 4. The summary of observations for the above cases are included in Section 7.3.1. + +All conclusions are drawn with assumption of 1dB desense for self-interference suppression and “twice the total number of antenna elements and same total number of TxRUs”. + +In the Urban Macro or Dense Urban Macro layer, the co-site inter-sector spatial isolation value is categorized into three cases. + +- Less than 93dB for FR1 (98dB for FR2-1) includes spatial isolation values of no lower than 75dB (88dB for FR2-1), which is a typical spatial isolation value from RAN4. +- Equal to 93dB for FR1 (98dB for FR2-1) is the best spatial isolation value from RAN4. +- No less than 93dB for FR1 (98dB for FR2-1) includes spatial isolation values of up to 110dB (115dB for FR2-1) including 10dB digital cancelation value. + +In this section, {X%,Y%,Z%} notation represents X% UPT gain or loss for low load level, Y% UPT gain or loss for medium load level, and Z% UPT gain or loss for high load level, respectively. The values X, Y, Z are median values of all evaluation result for a given evaluation assumption. + +#### **SBFD deployment case 1 (Non-coexistence case with same SBFD configuration amongst gNBs)** + +For SBFD deployment case 1, SBFD with XXXXX slot format (X is SBFD slot with UL/DL subband) are assumed as compared to semi-static TDD (DDDSU) + +- For FR1 indoor scenario, semi-static SBFD provides performance improvement for both DL and UL for all load levels and small/large packet size except for limited 5% DL UPT loss at medium load level and large packet sizes + - In case of small packet size, + - {9.56%, 9.35%, 8.58%} / {10.50%, 12.71%, 8.79%} for mean/5% DL UPT gain + - {101.83%, 97.42%, 93.85%} / {107.58%, 105.44%, 106.52%} for mean/5% UL UPT gain + - In case of large packet size, + - {1.86%, 2.21%, 2.73%} / {1.73%, -1.19%, 0.54%} for mean/5% DL UPT gain/loss + - {10.78%, 13.38%, 13.75%} / {14.13%, 19.91%, 17.70%} for mean/5% UL UPT gain +- For FR2-1 indoor scenario, semi-static SBFD provides performance improvement for both DL and UL for all load levels and both small/large packet sizes, except 5% DL UPT loss at high load level and small packet sizes + - In case of small packet size, + +- {4.84%, 7.57%, 5.95%} / {5.18%, 4.45%, -10.25%} for mean/5% DL UPT gain/loss +- {55.30%, 54.71%, 72.66%} / {50.71%, 46.45%, 59.26%} for mean/5% UL UPT gain +- In case of large packet size, + - {3.63%, 3.36%, 3.60%} / {6.03%, 6.67%, 3.35%} for mean/5% DL UPT gain + - {16.60%, 22.22%, 20.61%} / {38.79%, 71.05%, 86.18%} for mean/5% UL UPT gain +- For Urban Macro (FR1), if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is no less than 93 dB, + - In case of small packet size, semi-static SBFD provides performance improvement for DL for low load level and for UL for all load levels (for at least one of mean and 5% UPT) + - {6.53%, -1.96%, -19.87%} / {-0.51%, -68.33%, -85.70%} for mean/5% DL UPT gain/loss + - {97.24%, 69.31%, 62.22%} / {67.19%, 38.66%, -0.67%} for mean/5% UL UPT gain/loss + - In case of large packet size, semi-static SBFD provides performance improvement for UL for low load level + - {-8.17%, -30.29%, -33.03%} / {-9.59%, -73.35%, -89.16%} for mean/5% DL UPT loss + - {24.00%, -2.88%, -17.64%} / {164.97%, -52.87%, -69.03%} for mean/5% UL UPT gain/loss +- For Urban Macro (FR1), if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is equal to 93 dB, + - In case of small packet size, semi-static SBFD provides performance improvement for UL for low load level and medium load levels (for at least one of mean and 5% UPT) + - {-2.59%, -6.88%, -17.55%} / {-37.98%, -48.89%, -78.27%} for mean/5% DL UPT loss + - {34.65%, 18.85%, -1.33%} / {18.12%, -13.03%, -38.49%} for mean/5% UL UPT gain/loss + - In case of large packet size, semi-static SBFD provides performance improvement for UL for low load level + - {-8.47%, -34.75%, -32.86%} / {-4.26%, -88.67%, -84.60%} for mean/5% DL UPT loss + - {8.54%, -23.92%, -78.23%} / {187.62%, -45.51%, -69.03%} for mean/5% UL UPT gain/loss +- For Urban Macro (FR1), if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is less than 93 dB, + - In case of small packet size, semi-static SBFD provides no performance improvement + - {-14.55%, -15.11%, -20.87%} / {-78.16%, -98.06%, -99.62%} for mean/5% DL UPT loss + - {-6.50%, -27.59%, -43.73%} / {-98.32%, -100%, -100%} for mean/5% UL UPT loss + - In case of large packet size, semi-static SBFD provides no performance improvement + - {-25.70%, -40.50%, -45.29%} / {-75.30%, -94.59%, -97.64%} for mean/5% DL UPT loss + - {-31.00%, -74.48%, -86.16%} / {-100%, -100%, -100%} for mean/5% UL UPT loss +- For Dense Urban Macro (FR1), if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is no less than 93 dB, + - In case of small packet size, semi-static SBFD provides performance improvement for UL for all load levels (for at least one of mean and 5% UPT) + - {1.90%, -5.76%, -12.57%} / {0.01%, -24.09%, -67.74%} for mean/5% DL UPT gain/loss, + - {94.73%, 63.40%, 32.12%} / {36.17%, -37.56%, -88.59%} for mean/5% UL UPT gain/loss + +- In case of large packet size, semi-static SBFD provides performance improvement for DL and UL for low load level (for at least one of mean and 5% UPT) + - {1.18%, -5.57%, -11.35%} / {-1.49%, -27.51%, -58.09%} for mean/5% DL UPT gain/loss + - {20.54%, -12.87%, -49.27%} / {15.51%, -59.62%, -96.97%} for mean/5% UL UPT gain/loss +- For Dense Urban Macro (FR1), if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is equal to 93 dB, + - In case of large packet size, semi-static SBFD provides performance improvement for UL for all load levels + - {1.18%, -1.58%, -6.07%} / {-1.49%, -5.34%, -10.59%} for mean/5% DL UPT gain/loss, + - {28.96%, 21.52%, 17.32%} / {52.17%, 55.17%, 25.98%} for mean/5% UL UPT gain +- For Dense Urban Macro layer (FR2-1), if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is no less than 98 dB, + - In case of small packet size, semi-static SBFD provides performance improvement for both DL and UL for all load levels except 5% DL UPT loss at high load level + - {4.69%, 2.57%, 0.90%} / {4.20%, 1.27%, -7.41%} for mean/5% DL UPT gain/loss + - {57.78%, 49.40%, 41.22%} / {65.51%, 63.03%, 96.07%} for mean/5% UL UPT gain + - In case of large packet size, semi-static SBFD provides performance improvement for DL for low load level and performance improvement for UL for all load levels + - {2.45%, 2.18%, 1.48%} / {2.30%, 1.17%, -1.37%} for mean/5% DL UPT gain/loss + - {37.31%, 30.11%, 3.11%} / {19.44%, 30.93%, 11.76%} for mean/5% UL UPT gain +- For Dense Urban Macro layer (FR2-1), if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is less than 98 dB, + - In case of large packet size, semi-static SBFD provides limited performance improvement for DL for low and medium load levels and significant performance improvement for 5% UL UPT for low and medium load levels (for at least one of mean and 5% UPT) + - {1.48%, 1.65%, 1.23%} / {2.17%, 0.70%, -2.28%} for mean/5% DL UPT gain/loss + - {8.88%, -31.13%, -74.61%} / {159.27%, 127.28%, -52.69%} for mean/5% UL UPT gain/loss +- For Dense Urban Macro layer (FR2-1), if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is equal to 98 dB, + - In case of large packet size, semi-static SBFD provides limited performance improvement for DL for low and medium load levels (for at least one of mean and 5% UPT) and performance improvement for UL for all load levels (for at least one of mean and 5% UPT) + - {1.33%, 1.60%, 1.36%} / {1.71%, -1.26%, -5.34%} for mean/5% DL UPT gain/loss, + - {36.23%, 18.49%, -17.88%} / {18.52%, 28.87%, 10.78%} for mean/5% UL UPT gain/loss + +For SBFD deployment case 1, SBFD with XXXXU slot format is assumed, + +- For FR1 indoor scenario, semi-static SBFD provides performance improvement for UL but may suffer from degradation for DL +- In case of small packet size, + - {-0.52%, -1.19%, -6.26%} / {-0.35%, -1.66%, -17.59%} for mean/5% DL UPT loss + - {99.50%, 98.83%, 104.00%} / {116.24%, 110.00%, 127.81%} for mean/5% UL UPT gain + +- In case of large packet size, + - {-20.38%, -26.30%, -33.95%} / {-22.88%, -29.57%, -53.83%} for mean/5% DL UPT loss + - {78.53%, 93.92%, 113.75%} / {81.03%, 106.39%, 150.17%} for mean/5% UL UPT gain +- For FR2-1 indoor scenario, semi-static SBFD provides performance improvement for UL but may suffer from degradation for DL + - In case of small packet size, + - {-4.40%, -6.90%, -22.06%} / {-22.33%, -30.02%, -40.36%} for mean/5% DL UPT loss + - {78.57%, 91.25%, 149.67%} / {84.98%, 102.86%, 201.41%} for mean/5% UL UPT gain +- For Urban Macro (FR1), if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is no less than 93 dB, + - In case of small packet, semi-static SBFD provides significant performance improvement for UL but suffers from degradation for DL + - {-2.92%, -10.59%, -20.61%} / {-7.18%, -18.66%, -57.30%} for mean/5% DL UPT loss + - {126.08%, 120.22%, 107.06%} / {199.31%, 206.18%, 205.37%} for mean/5% UL UPT gain + - In case of large packet, semi-static SBFD provides performance improvement for UL but suffers from degradation for DL + - {-25.62%, -28.92%, -47.44%} / {-25.50%, -57.92%, -85.67%} for mean/5% DL UPT loss + - {66.15%, 53.69%, 40.66%} / {170.00%, 82.67%, 50.34%} for mean/5% UL UPT gain +- For Urban Macro (FR1), if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is less than 93 dB, + - In case of large packet, semi-static SBFD provides no performance improvement, except limited mean UL UPT gain for low load level and 5% UL UPT gain for high load + - {-32.72%, -50.26%, -52.78%} / {-73.00%, -96.20%, -99.73%} for mean/5% DL UPT loss + - {1.27%, -37.96%, -35.17%} / {-31.70%, -26.68%, 14.21%} for mean/5% UL UPT gain/loss +- For Urban Macro (FR1), if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is equal to 93 dB, + - In case of small packet, semi-static SBFD provides significant performance improvement for UL but suffers from degradation for DL + - {-0.04%, -2.62%, -12.55%} / {-0.30%, -5.88%, -23.21%} for mean/5% DL UPT loss + - {71.55%, 89.49%, 102.27%} / {273.08%, 238.46%, 198.00%} for mean/5% UL UPT gain + - In case of large packet, semi-static SBFD provides performance improvement for UL but suffers from degradation for DL + - {-25.79%, -35.29%, -51.62%} / {-25.50%, -57.92%, -81.73%} for mean/5% DL UPT loss + - {63.70%, 44.06%, 40.66%} / {203.20%, 55.93%, 42.37%} for mean/5% UL UPT gain +- For Dense Urban Macro (FR1), if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is no less than 93 dB, + - In case of large packet size, semi-static SBFD provides significant performance improvement for UL for all load levels. + - {-26.93%, -31.81%, -38.12%} / {-27.97%, -42.92%, -64.49%} for mean/5% DL UPT loss + - {90.67%, 97.71%, 68.10%} / {102.57%, 103.45%, 147.37%} for mean/5% UL UPT gain + +- For Dense Urban Macro (FR1), if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is equal to 93 dB, + - In case of large packet, semi-static SBFD provides significant performance improvement for UL but suffers from degradation for DL + - {-21.92%, -21.92%, -28.36%} / {-33.05%, -32.32%, -51.08%} for mean/5% DL UPT loss + - {123.47%, 112.72%, 123.71%} / {104.36%, 139.28%, 147.37%} for mean/5% UL UPT gain +- For Dense Urban Macro layer (FR2-1), if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is no less than 98 dB, + - In case of large packet size, semi-static SBFD provides performance improvement for UL but suffers from degradation for DL + - {-20.50%, -28.49%, -37.91%} / {-22.48%, -47.88%, -49.87%} for mean/5% DL UPT loss + - {79.47%, 96.75%, 123.96%} / {75.86%, 139.31%, 100.01%} for mean/5% UL UPT gain + +For SBFD deployment case 1, SBFD with DXXXU slot format is assumed, + +- For Urban Macro (FR1), if the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is no less than 93 dB, + - In case of large packet size, semi-static SBFD provides performance improvement for UL but suffers from degradation for DL + - {-23.21%, -35.27%, -50.23%} / {-46.49%, -78.32%, -79.73%} for mean/5% DL UPT loss + - {72.55%, 47.69%, 33.76%} / {126.00%, 90.91%, 55.81%} for mean/5% UL UPT gain + +### **SBFD deployment case 3-2 (Co-channel co-existence case)** + +For the indoor layer of 2-layer scenario (FR1) in SBFD deployment case 3-2, when SBFD with XXXXX slot format for indoor layer and TDD with DDDSU for Macro layer are assumed, + +- In case of small packet, semi-static SBFD provides performance improvement for DL at low and medium load levels and UL for all load levels (for at least one of mean and 5% UPT) + - {5.69%, 5.29%, -2.27%} / {6.87%, 3.42%, -50.93%} for mean/5% DL UPT gain/loss + - {91.80%, 89.00%, 78.10%} / {93.70%, 26.42%, -37.25%} for mean/5% UL UPT gain/loss +- In case of large packet, semi-static SBFD provides performance improvement for UL but suffers from degradation for DL + - {-5.38%, -7.29%, -9.20%} / {-10.49%, -11.87%, -12.30%} for mean/5% DL UPT loss + - {3.90%, 3.38%, 14.78%} / {17.83%, 68.34%, 71.07%} for mean/5% UL UPT gain + +For the indoor layer of 2-layer scenario (FR1) in SBFD deployment case 3-2, when SBFD with DXXXU slot format for indoor layer and DDDSU slot format for Macro layer are assumed, + +- In case of small packet size, semi-static SBFD provides significant performance improvement for UL but may suffer from degradation for DL for all load levels (for at least one of mean and 5% UPT for DL at low load) + - {0.43%, -1.58%, -13.98%} / {-0.01%, -7.82%, -80.99%} for mean/5% DL UPT gain/loss + - {99.80%, 102.60%, 110.12%} / {104.37%, 91.69%, 218.36%} for mean/5% UL UPT gain +- In case of large packet, semi-static SBFD provides significant performance improvement for UL but may suffer from degradation for DL for all load levels + +- {-24.90%, -28.31%, -36.34%} / {-28.72%, -32.62%, -51.41%} for mean/5% DL UPT loss +- {91.29%, 116.68%, 123.40%} / {41.77%, 106.71%, 174.07%} for mean/5% UL UPT gain + +#### **SBFD deployment case 4 (Adjacent channel co-existence)** + +For SBFD deployment case 4 (FR1) with 0% grid shift, and the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is no less than 93 dB, spatial isolation for co-site adjacent-channel CLI is no less than 93dB, and SBFD with XXXXX slot format and large packet size are assumed, + +- For the SBFD operator, semi-static SBFD provides performance improvement for UL at all load levels (for at least one of mean and 5% UPT for UL at high load) but suffers from degradation for DL for all load levels + - {-11.54%, -13.46%, -13.37%} / {-39.64%, -50.44%, -68.58%} for mean/5% DL UPT loss of SBFD operator + - {21.09%, 18.52%, 3.26%} / {47.60%, 0%, -19.36%} for mean/5% UL UPT gain/loss of SBFD operator +- For the legacy TDD operator, regarding the performance impact of semi-static SBFD to legacy TDD of another operator, there may be limited or large degradation for UL and DL performance + - {-6.46%, -6.73%, -5.22%} / {-29.43%, -39.73%, -53.81%} for mean/5% DL UPT loss of legacy TDD operator + - {-16.16%, -24.42%, -27.10%} / {-16.18%, 0%, 0%} for mean/5% UL UPT loss of legacy TDD operator + +For SBFD deployment case 4 (FR1) with 0% grid shift, and the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is no less than 93 dB, spatial isolation for co-site adjacent-channel CLI is no less than 93dB, and SBFD with XXXXU slot format and large packet size are assumed, + +- For the SBFD operator, semi-static SBFD provides performance improvement for UL but suffer from degradation for DL for all load levels + - {-22.97%, -21.22%, -26.20%} / {-27.07%, -52.53%, -65.36%} for mean/5% DL UPT loss of SBFD operator + - {59.89%, 26.32%, 23.29%} / {168.31%, 37.37%, 24.69%} for mean/5% UL UPT gain of SBFD operator +- For the legacy TDD operator, regarding the performance impact of semi-static SBFD to legacy TDD of another operator, there may be limited improvement and degradation for UL and DL performance + - {-0.45%, -2.12%, -3.39%} / {-1.52%, -2.25%, -4.86%} for mean/5% DL UPT loss of legacy TDD operator + - {-0.01%, 0.04%, 0.13%} / {0.07%, 0.10%, 2.08%} for mean/5% UL UPT gain/loss of legacy TDD operator + +For SBFD deployment case 4 (FR1) with 0% grid shift, and the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is equal to 93 dB, spatial isolation for co-site adjacent-channel CLI is equal to 93 dB, and SBFD with XXXXX slot format and large packet size are assumed, + +- For the SBFD operator, semi-static SBFD provides performance improvement for UL at low load level but suffers from degradation for DL for all load levels + - {-0.6%, -5.70%, -12.29%} / {3.34%, -10.72%, -23.48%} for mean/5% DL UPT gain/loss of SBFD operator + - {3.50%, -36.04%, -55.59%} / {114.57%, -18.46%, -69.36%} for mean/5% UL UPT gain/loss of SBFD operator +- For the legacy TDD operator, regarding the performance impact of semi-static SBFD to legacy TDD of another operator, there may be limited or large degradation for UL and DL performance + - {-0.44, -3.39%, -4.45%} / {-1.25%, -6.93%, -7.97%} for mean/5% DL UPT loss of legacy TDD operator + +- {-7.43%, -30.66%, -39.94%} / {-16.18%, -46.23%, -49.99%} for mean/5% UL UPT loss of legacy TDD operator + +For SBFD deployment case 4 (FR1) with 0% grid shift, and the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is equal to 93 dB, spatial isolation for co-site adjacent-channel CLI is equal to 93dB, and SBFD with XXXXU slot format and large packet size are assumed, + +- For the SBFD operator, semi-static SBFD provides performance improvement for UL but suffers from degradation for DL for all load levels + - {-23.27%, -29.59%, -40.53%} / {-23.08%, -38.52%, -49.36%} for mean/5% DL UPT loss of SBFD operator + - {88.87%, 68.41%, 34.44%} / {168.31%, 37.37%, 24.69%} for mean/5% UL UPT gain of SBFD operator +- For the legacy TDD operator, regarding the performance impact of semi-static SBFD to legacy TDD of another operator, there may be limited improvement or degradation for UL and DL performance + - {-0.45%, -2.12%, -3.39%} / {-1.52%, -2.25%, -4.86%} for mean/5% DL UPT loss of legacy TDD operator + - {-0.01%, 0.04%, 0.13%} / {0.07%, 0.10%, 2.08%} for mean/5% UL UPT gain/loss of legacy TDD operator + +For SBFD deployment case 4 (FR1) with 100% grid shift, and the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is no less than 93 dB, and SBFD with XXXXX slot format and large packet size are assumed, + +- For the SBFD operator, semi-static SBFD provides performance improvement for UL for low and medium load levels but suffers from degradation for DL for all load levels + - {-0.85%, -5.76%, -10.65%} / {-3.79%, -13.28%, -22.06%} for mean/5% DL UPT loss of SBFD operator + - {21.64%, 13.37%, -11.43%} / {32.42%, 10.67%, -3.28%} for mean/5% UL UPT gain/loss of SBFD operator +- For the legacy TDD operator, regarding the performance impact of semi-static SBFD to legacy TDD of another operator, there may be limited or large degradation for UL and DL performance + - {-0.35%, -3.31%, -5.38%} / {-2.64%, -9.41%, -7.68%} for mean/5% DL UPT loss of legacy TDD operator + - {-13.50%, -21.26%, -16.74%} / {-24.39%, -0.53%, -0.90%} for mean/5% UL UPT loss of legacy TDD operator + +For SBFD deployment case 4 (FR1) with 100% grid shift, and the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is no less than 93 dB, and SBFD with XXXXU slot format and large packet size are assumed, + +- For the SBFD operator, semi-static SBFD provides performance improvement for UL but suffers from degradation for DL for all load levels + - {-22.30%, -24.57%, -25.84%} / {-21.49%, -31.46%, -51.80%} for mean/5% DL UPT loss of SBFD operator + - {90.01%, 94.07%, 36.70%} / {94.35%, 58.67%, 38.16%} for mean/5% UL UPT gain of SBFD operator +- For the legacy TDD operator, regarding the performance impact of semi-static SBFD to legacy TDD of another operator, there may be limited degradation for DL performance and no change for UL performance + - {-0.30%, -1.61%, -3.21%} / {-0.16%, -3.59%, -3.92%} for mean/5% DL UPT loss of legacy TDD operator + - {0%, 0%, 0%} / {0%, 0%, 0%} for mean/5% UL UPT gain/loss of legacy TDD operator + +For SBFD deployment case 4 (FR1) with 100% grid shift, and the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is equal to 93 dB, and SBFD with XXXXX slot format and large packet size are assumed, + +- For the SBFD operator, semi-static SBFD provides performance improvement for both UL and DL for low load levels but suffers from degradation for both UL and DL for medium and high load levels + - {3.11%, -5.76%, -10.65%} / {2.27%, -13.28%, -22.06%} for mean/5% DL UPT gain/loss of SBFD operator + - {9.77%, -30.95%, -65.59%} / {89.73%, -17.62%, -53.26%} for mean/5% UL UPT gain/loss of SBFD operator +- For the legacy TDD operator, regarding the performance impact of semi-static SBFD to legacy TDD of another operator, there may be limited or large degradation for UL and DL performance + - {-0.35%, -2.94%, -4.37%} / {-1.40%, -7.02%, -6.72%} for mean/5% DL UPT loss of legacy TDD operator + - {-6.75%, -26.88%, -37.96%} / {-12.59%, -44.22%, -50.22%} for mean/5% UL UPT loss of legacy TDD operator + +For SBFD deployment case 4 (FR1) with 100% grid shift, and the total capability of spatial isolation and digital isolation for co-site inter-sector CLI is equal to 93 dB, and SBFD with XXXXU slot format and large packet size are assumed, + +- For the SBFD operator, semi-static SBFD provides performance improvement for UL for all load levels but suffers from degradation for DL for all load levels + - {-24.13%, -24.72%, -25.84%} / {-15.39%, -17.56%, -33.07%} for mean/5% DL UPT loss of SBFD operator + - {101.42%, 95.42%, 36.70%} / {120.78, 58.67%, 38.16%} for mean/5% UL UPT gain of SBFD operator +- For the legacy TDD operator, regarding the performance impact of semi-static SBFD to legacy TDD of another operator, there may be limited degradation for DL performance and no change for UL performance + - {-0.30%, -1.61%, -3.21%} / {-0.16%, -3.59%, -3.92%} for mean/5% DL UPT loss of legacy TDD operator + - {0%, 0%, 0%} / {0%, 0%, 0%} for mean/5% UL UPT gain/loss of legacy TDD operator + +RAN1 concluded that DL/UL UPT gain and loss at least come from the following reasons + +- In case of using SBFD with XXXXX slot format, the UL UPT gain at least comes from more UL transmission opportunities for semi-static SBFD compared to legacy TDD, and the DL UPT gain at least comes from the more DL transmission opportunities for semi-static SBFD compared to legacy TDD. +- In case of using SBFD with XXXXU or DXXXU slot format, the UL UPT gain at least comes from more UL resources and more UL transmission opportunities for semi-static SBFD compared to legacy TDD, and the DL UPT loss for SBFD at least comes from less DL resources for semi-static SBFD compared to legacy TDD. +- The UL UPT loss at least comes from inter-site gNB-gNB CLI and co-site inter-sector gNB-gNB CLI for Urban Macro and Dense Urban Macro layer. The impact of co-site inter-sector gNB-gNB CLI depends on co-site inter-sector CLI suppression capability. Also, the UL UPT loss at least comes from noise figure increase due to higher blocker power. +- For SBFD deployment case 4, for the SBFD operator, the UL UPT loss at least comes from inter-site adjacent-channel gNB-gNB CLI and co-site adjacent-channel gNB-gNB CLI for Urban Macro and Dense Urban Macro layer. The impact of co-site adjacent-channel gNB-gNB CLI depends on co-site adjacent-channel CLI suppression capability. Also, the UL UPT loss at least comes from noise figure increase due to higher blocker power by adjacent-channel CLI. +- For SBFD deployment case 4, for the legacy TDD operator in the case of XXXXX slot format, adjacent channel gNB-gNB CLI causes loss. + +- The DL UPT loss at least comes from UE-to-UE CLI. + +### 13.1.1.2 Coverage performance + +Based on link level simulation, comparing SBFD with XXXXU slot format and legacy TDD with DDDSU slot format, RAN1 observed, with assumption of 1dB desense for self-interference suppression and different co-site inter-sector isolation values, + +- semi-static SBFD with PUSCH repetition type A without/with joint channel estimation provides the UL coverage gain in range of {0.00~6.75} dB and median value of 5.41dB from 13 sources in FR1 UMa and in range of {5.86~8.76} dB and median value of 6.92dB from 4 sources in FR2-1 Dense UMa, respectively. +- semi-static SBFD with TBoMS with/without joint channel estimation provides the UL coverage gain in range of {2.83~6.88} dB and median value of 5.09dB from 4 sources in FR1 UMa and in range of {4.49~7.82} dB and median value of 5.72dB from 2 sources in FR2-1 Dense UMa, respectively. + +### 13.1.1.3 SBFD operation scheme + +SBFD operation at gNB for UEs was studied under the following assumptions, + +- SBFD operation within a TDD carrier. +- SBFD scheme within a single configured DL and UL BWP pair with aligned center frequencies, and +- Up to one UL subband for SBFD operation in an SBFD symbol (excluding legacy UL symbol) within a TDD carrier. + +RAN1 concluded SBFD operation Option 4 is feasible for RRC\_CONNECTED state from the RAN1 specification perspective, where SBFD operation Option 4 assumes + +- Both time and frequency locations of subbands for SBFD operation are known to SBFD aware UEs. +- UE behaviors for non-SBFD aware UEs follow existing specifications. +- From RAN1 perspective, new UE behaviors can be introduced for SBFD aware UEs based on the time and frequency locations of subbands for SBFD operation. + +Non-SBFD aware UEs, including legacy UEs, and SBFD aware UEs can coexist in cells with SBFD operation at gNB side from RAN1 specification point of view. + +To support SBFD operation Option 4 for RRC\_CONNECTED state, RAN1 identified the following potential specification impact for SBFD-aware UE: + +- Indication of time and frequency domain locations of SBFD subbands to UEs. +- UE transmission, reception and measurement behavior and procedures in SBFD symbols and/or non-SBFD symbols. + +### 13.1.1.4 CLI handling scheme + +For semi-static SBFD, the gNB-to-gNB co-channel CLI handling schemes and UE-to-UE co-channel CLI handling schemes were studied, including performance and specification impact, which are included in Section 7.4.2, Section 7.4.3 and Section 7.4.4. The summary of observations for co-channel CLI handling schemes are included in Section 7.4. + +## 13.1.2 RAN4 + +RAN4 has studied the implementation feasibility of SBFD-capable BS considering self-interference, co-channel inter-sub-band co-site inter-sector interference and co-channel inter-sub-band inter-site interference. Both FR1 and FR2 BS classes are studied, including FR1 wide area BS, FR1 medium range BS, FR1 local area BS and FR2-1 wide area BS. When considering the RSIC for self-interference and inter-sector interference, the following aspects and self-interference mitigation techniques have been considered: spatial antenna isolation, Tx beam nulling, suppression of transmitter leakage (i.e., frequency isolation), analogue interference cancellation, digital interference cancellation, receive beam-forming, receiver linearity performance, phase noise and other considerations. + +RAN4 has also studied the implementation feasibility of UE considering modeling of UE-UE co-channel inter-sub-band CLI and UE-UE adjacent channel CLI. Both FR1 and FR2-1 UE are studied and CLI modeling combines both Tx and Rx parts. It's worth noting that half duplex operation at UE side is assumed according to the objective of this study item. + +Besides, the impact on both BS and UE RF requirements are studied. For the BS aspects, impact on Tx requirements, impact on Rx requirements and potentially new requirements for SBFD operation are analyzed. For the UE aspects, reusing existing UE RF requirements is the conclusion of the study phase, since no issues related to existing UE RF requirements has been identified in the co-existence study. + +Moreover, the adjacent channel co-existence studies were performed under a total of 8 deployment scenarios as described in Table 11-1. For each deployment scenario, a total of 4 cases were performed as described in Table 11-2. The performance metrics were throughput loss at the cell edge and cell average. + +In the summary sub-section, value ranges and median values are collected from all companies' simulation results with respect to the different scenarios, cases, victims, and the four kinds of simulation parameters. The final conclusion is derived for the four "victim/ aggressor" network combinations. + +Finally, regulatory considerations for deploying the duplex enhancements in TDD unpaired spectrum are summarized with respect to three ITU Regions, namely ITU Region 1, ITU Region 2 and ITU Region 3. + +Regarding detailed conclusions, Table 13.1.2-1 below summarizes the different study conclusions and their respective section. + +**Table 13.1.2-1: RAN4 conclusions reference** + +| Study conclusion | Section | +|--------------------------------------------|----------------| +| Feasibility of FR1 wide area BS aspects | 9.2.4 | +| Feasibility of FR1 medium range BS aspects | 9.3.4 | +| Feasibility of FR1 local area BS aspects | 9.4.3 | +| Feasibility of FR2 BS aspects | 9.5.4 | +| Feasibility of FR1 UE aspects | 9.6.2 | +| Feasibility of FR2 UE aspects | 9.7.2 | +| Impact on RF requirements (BS and UE) | 10 | +| Adjacent channel co-existence evaluation | 11.3 | +| Regulatory aspects | 12.4 | + +## 13.2 Dynamic/flexible TDD + +For dynamic/flexible TDD, the gNB-to-gNB co-channel CLI handling schemes and UE-to-UE co-channel CLI handling schemes, which can be specific for dynamic/flexible TDD and/or common for both SBFD and dynamic/flexible TDD, were studied, including analysis, performance and specification impact, which are included in Section 8.3 and Section 8.4. The summary of observations for gNB-to-gNB CLI handling schemes are included in Section 8.3. + +RAN4 did not conduct any adjacent channel co-existence studies with dynamic TDD in Rel-18 SI as similar discussions took place under Rel-16 and were captured in TR 38.828. The following recommendations were made in section 6.3.1.1 of TR 38.828 + +- Concerning Urban Macro to Urban Macro scenario in FR1, "Performance degradation was observed from the BS-to-BS interference for macro-macro scenario, which suggests that dynamic TDD should not be operated in such scenarios." +- Concerning indoor network and a macro network scenario in FR1 and vice versa, "Performance degradations were not observed from operating dynamic TDD between an indoor network and a macro network and vice versa if there is sufficient isolation between them. No significant impact from operating dynamic TDD for the indoor scenario was observed as long as the BS and UE powers are similar and the operator's co-ordinate so that base station positions are offset. If higher BS power is assumed, some throughput degradation in the indoor scenario was observed due to BS-to-BS interference. The observations imply that dynamic TDD can be used in indoors as long as care is taken." + +The recommendations for dynamic TDD in TR38.828 are still valid and should be taken into consideration. Any mitigation techniques of dynamic TDD to address adjacent channel interference can apply to SBFD operation in symbols configured as flexible. + +--- + +## Annex : Evaluation methodologies + +Please see separate MS Word file for Annex A. + +--- + +## Annex : System level simulation + +### B.1 System level simulation assumptions + +Please see separate MS Word file for Annexes B.1 and B.2. + +--- + +### B.2 System level simulation results for semi-static SBFD + +Please see separate MS Word file for Annexes B.1 and B.2. + +--- + +### B.3 System level simulation results of schemes for SBFD + +Please see separate MS Word file for Annex B.3. + +--- + +### B.4 System level simulation results for dynamic TDD + +Please see separate MS Word file for Annex B.4. + +--- + +## Annex : System level simulation calibration + +Please see separate MS Word file for Annexes C and D. + +--- + +## Annex : Link level evaluation for coverage performance + +Please see separate MS Word file for Annexes C and D. + +--- + +## Annex : Adjacent channel co-existence evaluation + +Please see separate MS Word file for Annex E. + +## Annex : Change history + +| Change history | | | | | | | | +|----------------|-------------|------------|----|-----|-----|------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-05 | RAN1#109-e | R1-2205399 | | | | Skeleton | 0.0.1 | +| 2022-05 | RAN1#109-e | R1-2205692 | | | | Endorsed skeleton | 0.0.2 | +| 2022-11 | RAN1#111 | R1-2212374 | | | | Capture evaluation methodology agreements until RAN1#110-b meeting | 0.1.0 | +| 2023-02 | RAN1#112 | R1-2300997 | | | | Capture evaluation methodology agreements until RAN1#111 meeting | 0.2.0 | +| 2023-04 | RAN1#112b-e | R1-2303230 | | | | Version not formally endorsed by RAN1. Capture evaluation methodology agreements until RAN1#112 meeting; Update TR skeleton of RAN4 part | 0.3.0 | +| 2023-05 | RAN1#113 | R1-2305091 | | | | Capture agreements and TP until RAN1#112b-e meeting | 0.4.0 | +| 2023-06 | RAN1#113 | R1-2306344 | | | | MCC clean-up - no changes compare to v0.4.0 | 0.4.1 | +| 2023-08 | RAN1#114 | R1-2308675 | | | | Capture endorsed TPs made in RAN1#114 meeting | 0.5.0 | +| 2023-09 | RAN#101 | RP-232421 | | | | Submitted to RAN for information | 1.0.0 | +| 2023-11 | RAN1#115 | R1-2312309 | | | | MCC clean-up | 1.0.1 | +| 2023-11 | RAN1#115 | R1-2312778 | | | | Capture the TP (R1-2312429) endorsed in RAN1#115 and the TP (R4-2318925) endorsed in RAN4#109 | 1.1.0 | +| 2023-12 | RAN#102 | RP-232763 | | | | Submitted to RAN for approval | 2.0.0 | +| 2023-12 | RAN#102 | | | | | Rel-18 TR under change control further to RAN approval | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38867/34f788b0e5bc8af774fa5561c22e6d01_img.jpg b/marked/Rel-18/38_series/38867/34f788b0e5bc8af774fa5561c22e6d01_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..622b43cf98d1787f3ef26ca0b1c26e27f3d89472 --- /dev/null +++ b/marked/Rel-18/38_series/38867/34f788b0e5bc8af774fa5561c22e6d01_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:332f3d55735395378144e96040a79ad33e82a1f2869645b57b28ba7812054388 +size 17698 diff --git a/marked/Rel-18/38_series/38867/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38867/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..733fca41476d28c3120522800fb427061a579176 --- /dev/null +++ b/marked/Rel-18/38_series/38867/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:40833e378a317e152cc7d804ddad10c43bc2ae89afa778c95d791c75b1876971 +size 9828 diff --git a/marked/Rel-18/38_series/38867/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38867/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed2da7b5064ab9ca2c97e6cc57aad01be11c1d38 --- /dev/null +++ b/marked/Rel-18/38_series/38867/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:84add26a6324ef42e38d34314b78a6e4825344a2450a564bd57fff7499416403 +size 5834 diff --git a/marked/Rel-18/38_series/38867/7f17c430b9598e4d748a8041457810b3_img.jpg b/marked/Rel-18/38_series/38867/7f17c430b9598e4d748a8041457810b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bbe7db194a4330e24a8f9145932c13fbc0bed0f1 --- /dev/null +++ b/marked/Rel-18/38_series/38867/7f17c430b9598e4d748a8041457810b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:305dd8c917f282791e474ba3ad98493b4e4eba4136369b2c2ca88e6d6d4164e3 +size 49429 diff --git a/marked/Rel-18/38_series/38867/8e14350b4b669119a3bdfca7869110ca_img.jpg b/marked/Rel-18/38_series/38867/8e14350b4b669119a3bdfca7869110ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..02cbdea7cfb5aba10b05cc31d7615841f8454791 --- /dev/null +++ b/marked/Rel-18/38_series/38867/8e14350b4b669119a3bdfca7869110ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd2df3eab2665512d5695cd10987c86bcbaa1ffa247f94dbe2091a32b68ac2d0 +size 79707 diff --git a/marked/Rel-18/38_series/38867/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-18/38_series/38867/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3b217ee70b0bea589d9f3eb2f4c59bb09c84c5e1 --- /dev/null +++ b/marked/Rel-18/38_series/38867/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f7d3a7b69b3d203a0e9c0408fb60b18cecd1cd797bc6d50142c0f53628fcfcf7 +size 47499 diff --git a/marked/Rel-18/38_series/38867/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-18/38_series/38867/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b6de3023553e61bdc8c9b7983843f2fa60eed6de --- /dev/null +++ b/marked/Rel-18/38_series/38867/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b6825b1a518be2429087fc0dca15180bb73660ac732c4a294a26dedad9e9255 +size 58400 diff --git a/marked/Rel-18/38_series/38867/raw.md b/marked/Rel-18/38_series/38867/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..50da1af6f20a6d2bd310a53c2e4ab0d5f46a4428 --- /dev/null +++ b/marked/Rel-18/38_series/38867/raw.md @@ -0,0 +1,592 @@ + + +# 3GPP TR 38.867 V18.0.0 (2022-09) + +*Technical Report* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access network; Study on NR network-controlled repeaters; (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' 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. + +© 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..... | 6 | +| 3.1 Terms..... | 6 | +| 3.2 Abbreviations ..... | 6 | +| 4 Introduction..... | 7 | +| 5 Modelling of network-controlled repeater ..... | 7 | +| 6 Side control information ..... | 8 | +| 6.1 Beam information..... | 8 | +| 6.2 Timing information ..... | 8 | +| 6.3 Information on UL-DL TDD configuration..... | 8 | +| 6.4 ON-OFF information..... | 9 | +| 6.5 Power control information ..... | 9 | +| 7 L1/L2 signalling for side control information..... | 9 | +| 7.1 Signalling for side control information ..... | 9 | +| 7.1.1 Signalling for beam information ..... | 9 | +| 7.1.2 Signalling for timing information..... | 10 | +| 7.1.3 Signalling for UL-DL TDD configuration ..... | 10 | +| 7.1.4 Signalling for ON-OFF information..... | 10 | +| 7.1.5 Signalling for power control information..... | 10 | +| 7.2 Configuration of signalling ..... | 10 | +| 8 Repeater management..... | 11 | +| 8.1 Solution on repeater management..... | 11 | +| 8.1.1 Solution 1 ..... | 11 | +| 8.1.2 Solution 2..... | 12 | +| 8.1.3 Solution 3..... | 12 | +| 8.1.4 Solution 4..... | 13 | +| 8.2 Specification impacts ..... | 14 | +| 9 Performance evaluation..... | 18 | +| Annex<A>: Cost evaluations..... | 20 | +| Annex <B>: Change history | 20 | + +# 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 from the study item "Study on NR Network-controlled Repeaters" [2]. + +The SI includes the study and identification of side control information (i.e., beamforming information, Timing information, information on UL-DL TDD configuration, ON-OFF information and power control information) for network-controlled repeaters and corresponding L1/L2 signaling (including its configuration) to carry the side control information. The scope of the study also includes the study on the aspects (i.e., identification and authorization) of network-controlled repeater management + +The study on NR network-controlled repeaters is to focus on the following scenarios and assumptions: + +- Network-controlled repeaters are inband RF repeaters used for extension of network coverage on FR1 and FR2 bands, while during the study FR2 deployments may be prioritized for both outdoor and O2I scenarios. +- For only single hop stationary network-controlled repeaters +- Network-controlled repeaters are transparent to UEs +- Network-controlled repeater can maintain the gNB-repeater link and repeater-UE link simultaneously + +NOTE1: Cost efficiency is a key consideration point for network-controlled repeaters. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". + +[2] 3GPP RP-213700: " New SI: Study on NR Network-controlled Repeaters ". + +[3] 3GPP TR 38.380: "Study on NR coverage enhancements". + +# 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 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]. + +| | | +|-----|-----------------------------| +| NCR | Network-controlled repeater | +|-----|-----------------------------| + +| | | +|---------|------------------------| +| NCR-MT | NCR-Mobile termination | +| NCR-Fwd | NCR-Forwarding | +| C-link | Control link | + +# 4 Introduction + +Coverage is a fundamental aspect of cellular network deployments. Mobile operators rely on different types of network nodes to offer blanket coverage in their deployments. Deployment of regular full-stack cells is one option but it may not always be possible (e.g., no availability of backhaul) or economically viable. + +As a result, new types of network nodes have been considered to increase mobile operators' flexibility for their network deployments. For example, Integrated Access and Backhaul (IAB) was introduced in Rel-16 and enhanced in Rel-17 as a new type of network node not requiring a wired backhaul. Another type of network node is the RF repeater which simply amplify-and-forward any signal that they receive. RF repeaters have seen a wide range of deployments in 2G, 3G and 4G to supplement the coverage provided by regular full-stack cells. In Rel-17, RAN4 specified RF and EMC requirements for such RF repeaters for NR targeting both FR1 and FR2. + +While an RF repeater presents a cost effective means of extending network coverage, it has its limitations. An RF repeater simply performs an amplify-and-forward operation without being able to take into account various factors that could improve performance. Such factors may include information on semi-static and/or dynamic downlink/uplink configuration, adaptive transmitter/receiver spatial beamforming, ON-OFF status, and so on. + +A network-controlled repeater is an enhancement over conventional RF repeaters with the capability to receive and process side control information from the network. Side control information could allow a network-controlled repeater to perform the amplify-and-forward operation in a more efficient manner. Potential benefits could include mitigation of unnecessary noise amplification, transmissions and receptions with better spatial directivity, and simplified network integration. + +# 5 Modelling of network-controlled repeater + +The Network-controlled repeater is modelled as Figure 5-1, which includes the NCR-MT and NCR-Fwd. + +The NCR-MT is defined as a function entity to communicate with a gNB via a Control link (C-link) to enable exchange of control information (e.g. side control information at least for the control of NCR-Fwd). The C-link is based on NR Uu interface. + +The NCR-Fwd is defined as a function entity to perform the amplify-and-forwarding of UL/DL RF signal between gNB and UE via backhaul link and access link. The behavior of the NCR-Fwd will be controlled according to the received side control information from gNB. + +![Figure 5-1: Conceptual model of network-controlled repeater. The diagram shows a gNB on the left connected to a Network-controlled repeater (NCR) on the right. The NCR is a dashed box containing two sub-components: NCR-MT (Mobile termination) and NCR-Fwd (Forwarding). A 'Control link' (black arrow) connects the gNB to the NCR-MT. A 'Backhaul link' (red arrow) connects the gNB to the NCR-Fwd. An 'Access link' (red arrow) connects the NCR-Fwd to a UE (User Equipment) on the far right.](34f788b0e5bc8af774fa5561c22e6d01_img.jpg) + +Figure 5-1: Conceptual model of network-controlled repeater. The diagram shows a gNB on the left connected to a Network-controlled repeater (NCR) on the right. The NCR is a dashed box containing two sub-components: NCR-MT (Mobile termination) and NCR-Fwd (Forwarding). A 'Control link' (black arrow) connects the gNB to the NCR-MT. A 'Backhaul link' (red arrow) connects the gNB to the NCR-Fwd. An 'Access link' (red arrow) connects the NCR-Fwd to a UE (User Equipment) on the far right. + +**Figure 5-1: Conceptual model of network-controlled repeater** + +Additionally, at least one of the NCR-MT's carrier(s) should operate in the frequency band forwarded by the NCR-Fwd. And the NCR-MT and NCR-Fwd operating in the same frequency band is prioritized for the study. + +As baseline, same large-scale properties of the channel, i.e., channel properties in Type-A and Type-D (if applicable), are expected to be experienced by C-link and backhaul link (at least when the NCR-MT and NCR-Fwd are operating in same frequency band). + +For the transmission/reception of C-link and backhaul link by NCR, + +- The DL of C-link and DL of backhaul link can be performed simultaneously or in TDM way + +- The UL of C-link and UL of backhaul link can be performed in TDM way. + +The multiplexing is under the control of gNB with consideration for NCR capability and simultaneous transmission of the UL of C-link and UL of backhaul link is also subject to NCR capability + +# --- 6 Side control information + +## 6.1 Beam information + +For the backhaul link and C-link, both fixed beam and adaptive beam can be considered at NCR, where the fixed beam refers to the case that beam at NCR for both C-link and backhaul-link cannot be changed. Beam correspondence is assumed to apply for DL/UL of the backhaul link at NCR-Fwd, as well as the DL/UL of the C-link at NCR-MT. + +As a baseline, the same TCI states as C-link are assumed for beams at NCR-Fwd for backhaul link if the NCR-MT's carrier(s) is operating within the frequency band forwarded by the NCR-Fwd. In case that the adaptive beams are adopted for C-link and backhaul link, the indication and determination of beams of backhaul link can be achieved by: + +- Option 1: The beam of backhaul link is indicated by a new signaling. The new signaling is dynamic signaling and/or semi-static signaling (e.g., RRC signaling/ MAC CE) indicating a beam(s) from the set of beams of the C-link. This does not imply that the beam of backhaul link is always indicated by the new signaling +- Option 2: The beam of backhaul link is determined by a pre-defined rule, e.g., in slots/symbols with simultaneous DL receptions / UL transmissions in both C-link and backhaul link, the beam of backhaul link is the same as the beam of C-link. Otherwise, the beam of backhaul link follows one of the beams of the C link. + +Other predefined rules are not precluded. + +At least for the access link, and at least for FR2, beam information is beneficial and recommended as the side control information for a network-controlled repeater to control the behaviour of the NCR for the access link. + +Regarding the access link beam indication, the beam of access link for NCR-Fwd is indicated by a beam index where both dynamic indication and semi-static indication, including semi-persistent indication, are considered + +The time domain resource corresponding to an access link beam is explicitly determined based on the explicitly indicated time domain resources per beam indication. A single beam indication can indicate one or multiple beams. Different parameters may be indicated for semi-static or dynamic beam indication. + +Beam correspondence is assumed for the DL/UL of the access link at NCR-Fwd, i.e., a DL beam and a UL beam on the access side which correspond to each other have the same beam index. The forwarding direction of an indicated beam in access link can be determined based on its corresponding time domain resource and the UL/DL TDD configuration. The forwarding behaviour (or the forwarding direction) of an indicated beam in access link in flexible symbols is separately discussed in clause 6.3. + +## 6.2 Timing information + +For the timing of NCR, the following assumption is considered as baseline: + +- The DL receive timing of the NCR-Fwd is aligned with the DL receive timing of the NCR-MT. +- The UL transmit timing of the NCR-Fwd is aligned with the UL transmit timing of the NCR-MT. +- The DL transmit timing of the NCR-Fwd is delayed after the DL receive timing of the NCR-MT (or the NCR-Fwd) by an internal delay; +- The UL receive timing of the NCR-Fwd is advanced before the UL transmit timing of the NCR-MT (or the NCR-Fwd) by an internal delay. + +It is concluded that legacy UE mechanism is sufficient to achieve DL/UL timing for NCR-MT. + +## 6.3 Information on UL-DL TDD configuration + +For the TDD UL/DL configuration of network controller repeater, at least semi-static TDD UL/DL configuration is needed for network-controlled repeater for links including C-link, backhaul link and access link. On the flexible symbols based on the semi-static configuration (e.g., TDD-UL-DL-ConfigCommon, TDD-UL-DL-ConfigDedicated), the following behaviours of the NCR-Fwd are considered: + +- Option 1: The NCR-Fwd is expected to be OFF or not forwarding over these symbols +- Option 2: The NCR-Fwd will follow the TDD operation determined by NCR-MT, i.e., determined by NCR-MT based on the received SFI indication or scheduling from gNB. It means that no new side control signalling is needed. +- Option 3: The NCR-Fwd will follow a new dynamic side control signalling of DL/UL forwarding over these symbols to NCR-Fwd + +The same TDD UL/DL configuration is always assumed for backhaul link and access link. Additionally, the same TDD UL/DL configuration is assumed for C-link, backhaul link and access link if NCR-MT and NCR-Fwd operate in the same frequency band. + +## 6.4 ON-OFF information + +ON-OFF information is beneficial and recommended for network-controlled repeater to control the behaviour of NCR-Fwd. + +The NCR-Fwd is always expected to be "OFF" unless otherwise explicitly or implicitly indicated by the gNB. This applies regardless of the RRC state of NCR-MT. Indication (e.g., received when NCR-MT in RRC-connected) or DRX state of NCR-MT to control the ON-OFF behaviour of NCR-Fwd when the NCR-MT is in RRC-idle/inactive is not precluded. + +The following options can be considered to indicate the ON-OFF information from gNB to NCR for controlling the behaviour of NCR-Fwd: + +- Option 1: Explicit indication with ON-OFF state (e.g., via dynamic or semi-static signalling) or ON-OFF pattern (e.g., periodic/semi-static ON-OFF pattern or new DRX-like pattern for ON-OFF) +- Option 2: Implicit indication via the signalling for other side-control information (e.g., beam, DL/UL configuration, or PC information). It should be noticed that this example does not imply that PC information is necessary or not. + +Other solutions (e.g., potential combination of explicit and implication solution) can be further discussed in normative phase. + +## 6.5 Power control information + +The controlling of the amplifying gain of NCR-Fwd is considered to enable the power control of NCR-Fwd if PC is recommended as side control information for NCR in Rel-18. + +# --- 7 L1/L2 signalling for side control information + +## 7.1 Signalling for side control information + +### 7.1.1 Signalling for beam information + +From the perspective of signaling design, both dynamic beam indication and semi-static beam indication are recommended for access link. The semi-static beam indication includes the semi-persistent indication. + +The time at which the NCR applies an access link beam indication should be considered. + +As for the time-domain granularity of the access link beam indication and determination, both slot-level and symbol-level granularity are recommended. + +### 7.1.2 Signalling for timing information + +For the signaling of the side control information of timing to align transmission/reception boundaries at the NCR, new signaling is unnecessary. + +### 7.1.3 Signalling for UL-DL TDD configuration + +For the signaling of information on UL-DL TDD configuration, if the NCR-MT can acquire its TDD configuration as legacy UEs or from OAM, new signaling may not be necessary. The same TDD UL/DL configuration is assumed for C-link and backhaul link and access link if the NCR-MT and the NCR-Fwd are in the same frequency band. Other cases, where new signaling may be necessary, can be discussed in normative phase. + +### 7.1.4 Signalling for ON-OFF information + +For an indication of NCR-Fwd ON-OFF for efficient interference management and improved energy efficiency, both dynamic and semi-static indication can be considered. Whether/how to handle the forwarding of broadcast and cell-specific signals/channels can be discussed in normative phase. + +### 7.1.5 Signalling for power control information + +Void + +## 7.2 Configuration of signalling + +For the configuration of signalling, the NCR-MT can obtain the necessary configuration for receiving the L1/L2 signaling of the side control information. + +- Option 1: The necessary configuration is from RRC. +- Option 2: The necessary configuration is from OAM or hard-coded. +- Option 3: The necessary configuration is partially configured by RRC and partially configured by OAM or hard-coded. + +The necessary configurations from RRC and/or OAM (or hard-coded) contain: + +- The configurations of PHY channels to carry the L1/L2 signaling including + - The configurations for receiving PDCCH and PDSCH. + - The configurations for transmitting PUCCH, if needed. + - The configurations for transmitting PUSCH, if needed. +- The configurations of L1/L2 signaling including + - The configurations for DCI. + - The configurations for UCI, if needed. + - The configurations for MAC CE, if needed. + +For the parameters in the necessary configurations for L1/L2 signaling, the existing parameters for PDCCH, PDSCH, PUCCH, PUSCH, DCI, UCI and MAC CE in Rel-17 are the baseline for further discussion. + +# 8 Repeater management + +## 8.1 Solution on repeater management + +### 8.1.1 Solution 1 + +In this solution, the identification and authorization/validation of NCR device are done at RAN side. The general procedure of the solution 1 is illustrated in below figure: + +![Sequence diagram for solution 1 showing the interaction between NCR, gNB, and AMF. The diagram illustrates the call flow for solution 1, starting with the NCR sending a RACH preamble (MSG1) to the gNB. The gNB responds with a RAR (MSG2), followed by the NCR sending an RRCSetupRequest (MSG3). The gNB responds with an RRCSetup (MSG4), and the NCR completes the setup with an RRCSetupComplete (MSG5). The gNB then sends an INITIAL UE MESSAGE to the AMF. The AMF responds with an INITIAL CONTEXT SETUP REQUEST to the gNB. The gNB then initiates the SecurityModeProcedure and UECapability Procedure with the NCR. The NCR sends an RRCReconfiguration Procedure to the gNB. The gNB then sends an INITIAL CONTEXT SETUP RESPONSE to the AMF. The NCR then sends an RRC message (NCR credential info from NCR device) to the gNB. The gNB verifies the NCR device and performs NCR validation.](8e14350b4b669119a3bdfca7869110ca_img.jpg) + +``` + +sequenceDiagram + participant NCR + participant gNB + participant AMF + Note left of NCR: Legacy AS/NAS procedure + NCR->>gNB: 1. RACH preamble(MSG1) + gNB-->>NCR: 2. RAR(MSG2) + NCR->>gNB: 3.RRCSetupRequest(MSG3) + gNB-->>NCR: 4.RRCSetup(MSG4) + NCR->>gNB: 5. RRCSetupComplete(MSG5) + Note right of NCR: (alt: NCR indication info) + gNB->>AMF: 6.INITIAL UE MESSAGE + AMF->>gNB: 7.INITIAL CONTEXT SETUP REQUEST + gNB-->>NCR: 8. SecurityModeProcedure + gNB-->>NCR: 9. UECapability Procedure + Note right of NCR: (alt: NCR indication info) + NCR->>gNB: 10.RRCReconfiguration Procedure + gNB->>AMF: 11.INITIAL CONTEXT SETUP RESPONSE + Note right of NCR: NCR validation + NCR->>gNB: 12. RRC message + Note right of NCR: (NCR credential info from NCR device) + Note right of gNB: 13. RAN verifies the NCR device. + +``` + +Sequence diagram for solution 1 showing the interaction between NCR, gNB, and AMF. The diagram illustrates the call flow for solution 1, starting with the NCR sending a RACH preamble (MSG1) to the gNB. The gNB responds with a RAR (MSG2), followed by the NCR sending an RRCSetupRequest (MSG3). The gNB responds with an RRCSetup (MSG4), and the NCR completes the setup with an RRCSetupComplete (MSG5). The gNB then sends an INITIAL UE MESSAGE to the AMF. The AMF responds with an INITIAL CONTEXT SETUP REQUEST to the gNB. The gNB then initiates the SecurityModeProcedure and UECapability Procedure with the NCR. The NCR sends an RRCReconfiguration Procedure to the gNB. The gNB then sends an INITIAL CONTEXT SETUP RESPONSE to the AMF. The NCR then sends an RRC message (NCR credential info from NCR device) to the gNB. The gNB verifies the NCR device and performs NCR validation. + +Figure 8.1.1-1. Call flow for solution 1 + +Sequence of this solution: + +1. The NCR firstly accesses to RAN and CN as a normal UE, no additional impact to NG-C interface. For example, the operator can allocate specific slice for NCR, and further identify the NCR based on the slice information. After authorized the NCR, the CN provides dedicated Allowed NSSAI to the gNB. Based on this information, the gNB be aware the NCR is authorized. +2. NCR identification can be implemented by reporting an NCR indicator in Msg5 (in addition to sending any NCR-related radio capability) and/or by reporting an NCR indicator (implicitly or explicitly) in UE's radio capability signaling. +3. If required, NCR validation is used to further check the validity of NCR, the details can be further discussed in normative phase. After AS security is established between the gNB and the NCR device, the NCR sends NCR credential information for NCR validation to the gNB via RRC message (e.g. UE Assistance Information). The NCR credential information are pre-allocated by the operator. After receiving the NCR credential information, the gNB validates the NCR device by checking its local stored information. + +The validation steps (e.g. step 12 and step 13) are optionally performed based on the operator's requirement. + +### 8.1.2 Solution 2 + +In this solution, the NCR is identified at RAN side and the authorization/validation are performed by local RAN OAM. CN is absent in this solution. The general procedure of the solution is illustrated in below figure: + +![Sequence diagram for Solution 2 showing the call flow between NCR, gNB, and OAM.](7f17c430b9598e4d748a8041457810b3_img.jpg) + +``` + +sequenceDiagram + participant NCR + participant gNB + participant OAM + Note right of gNB: (NCR indication info, OAM container) + NCR->>gNB: 1. RACH preamble(MSG1) + gNB-->>NCR: 2. RAR(MSG2) + NCR->>gNB: 3.RRCSetupRequest(MSG3) + gNB-->>NCR: 4.RRCSetup(MSG4) + NCR->>gNB: 5. RRCSetupComplete(MSG5) + Note right of gNB: (NCR indication info, OAM container) + gNB->>OAM: 6. OAM procedure + Note right of gNB: ( OAM container ) + Note over gNB,OAM: 7.OAM procedures for authorizing the NCR device + OAM-->>gNB: 8. Authorization response + +``` + +The diagram illustrates the call flow for Solution 2. It involves three main entities: NCR (Network Control Radio), gNB (Next Generation NodeB), and OAM (Operation, Administration, and Management). The sequence of messages is as follows: + + +- The NCR sends a RACH preamble (MSG1) to the gNB. +- The gNB responds with a RAR (MSG2). +- The NCR sends an RRCSetupRequest (MSG3) to the gNB. +- The gNB responds with an RRCSetup (MSG4). +- The NCR sends an RRCSetupComplete (MSG5) to the gNB. This message includes an NCR indication info and an OAM container. +- The gNB sends an OAM procedure message to the OAM, which includes the OAM container. +- A block labeled "7.OAM procedures for authorizing the NCR device" spans the interaction between the gNB and the OAM. +- The OAM sends an Authorization response back to the gNB. + +Sequence diagram for Solution 2 showing the call flow between NCR, gNB, and OAM. + +Figure 8.1.2-1. Call flow for solution 2 + +Sequence of this solution: + +1. NCR establishes RRC connection based on legacy signaling procedure (Msg1~Msg5), but the gNB will not establish NGAP signaling association for the NCR. +2. NCR identification can be implemented by reporting an NCR indicator in Msg5. +3. Different from Msg5 sent by a normal NR UEs, an OAM container is included in Msg5 and there is no NAS container. Based on the NCR indicator, the gNB applies NCR-specific handling, e.g. not to establish the NGAP association and forwards the OAM container to OAM. +4. The NCR authorization and validation is then performed between OAM and NCR. The information exchanged between OAM and NCR can be leveraged by an OAM container. Over Uu interface, the OAM container can be transferred via RRC message or via a DRB (which without PDU session). The security of OAM traffic can be provided by application layer security mechanism, such as SSH/TLS between the NCR and OAM. (Note that, the procedure for authorization/validation in OAM can be either specified or left to implementation) + +### 8.1.3 Solution 3 + +In this solution, NCR identification is done at RAN side, and NCR authorization is done at CN side, similar to the handling of IAB-MT. The general procedure of the solution is illustrated in below figure: + +![Sequence diagram for solution 3 showing interactions between NCR, gNB, and AMF. The sequence starts with NG SETUP from gNB to AMF, followed by NG SETUP RESPONSE (NCR Supported) from AMF to gNB. Then, RACH preamble (MSG1) from NCR to gNB, RAR (MSG2) from gNB to NCR, RRCSetupRequest (MSG3) from NCR to gNB, RRCSetup (MSG4) from gNB to NCR, and RRCSetupComplete (NCR Indication info) from NCR to gNB. Next, gNB selects an NCR capable AMF, sends INITIAL UE MESSAGE (NCR Indication info) to AMF, and receives UE CONTEXT SETUP/MODIFICATION (NCR is Authorized) from AMF.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +``` + +sequenceDiagram + participant NCR + participant gNB + participant AMF + Note right of gNB: 8.Select NCR capable AMF + gNB->>AMF: 1.NG SETUP + AMF-->>gNB: 2.NG SETUP RESPONSE +(NCR Supported) + NCR->>gNB: 3. RACH preamble(MSG1) + gNB-->>NCR: 4. RAR(MSG2) + NCR->>gNB: 5.RRCSetupRequest(MSG3) + gNB-->>NCR: 6.RRCSetup(MSG4) + NCR->>gNB: 7.RRCSetupComplete +(NCR Indication info) + Note right of gNB: 8.Select NCR capable AMF + gNB->>AMF: 9. INITIAL UE MESSAGE +(NCR Indication info) + AMF-->>gNB: 10. UE CONTEXT SETUP/ +MODIFICATION +(NCR is Authorized) + +``` + +Sequence diagram for solution 3 showing interactions between NCR, gNB, and AMF. The sequence starts with NG SETUP from gNB to AMF, followed by NG SETUP RESPONSE (NCR Supported) from AMF to gNB. Then, RACH preamble (MSG1) from NCR to gNB, RAR (MSG2) from gNB to NCR, RRCSetupRequest (MSG3) from NCR to gNB, RRCSetup (MSG4) from gNB to NCR, and RRCSetupComplete (NCR Indication info) from NCR to gNB. Next, gNB selects an NCR capable AMF, sends INITIAL UE MESSAGE (NCR Indication info) to AMF, and receives UE CONTEXT SETUP/MODIFICATION (NCR is Authorized) from AMF. + +Figure 8.1.3-1. Call flow for solution 3 + +Sequence of this solution: + +1. During NG-C setup procedure, the AMF should inform the gNB whether it supports NCR, e.g. by including "NCR-supported" indicator in NG SETUP RESPONSE message. +2. NCR establishes RRC connection and NCR identification can be implemented by reporting an NCR indicator in Msg5 (in addition to sending any NCR-related radio capability) and/or by reporting an NCR indicator (implicitly or explicitly) in UE's radio capability signaling. The gNB selects an AMF which supports NCR function, and forwards the NCR indicator to the AMF. +3. AMF and other CN entities do further authorization, and provides "NCR authorized" to the gNB. + +### 8.1.4 Solution 4 + +In this solution, NCR authorization is performed at CN side. The NCR authorization information is sent from the AMF to the gNB. Similarly to the handling of e.g. D2D, V2X, it seems appropriate for NCR authorization information to come from the UE subscription information in the 5GC (a trusted source of information). This information would be stored in the gNB in the UE context for the NCR-MT. The general procedure of this solution is illustrated in below figure: + +![Sequence diagram showing the call flow for solution 4 between NCR, gNB, and AMF.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +``` +sequenceDiagram + participant NCR + participant gNB + participant AMF + Note right of AMF: 7. Upon NAS registration, AMF authorizes the NCR and sends ind to RAN + NCR->>gNB: 1. RACH preamble(MSG1) + gNB-->>NCR: 2. RAR(MSG2) + NCR->>gNB: 3.RRCSetupRequest(MSG3) + gNB-->>NCR: 4.RRCSetup(MSG4) + NCR->>gNB: 5.RRCSetupComplete + gNB->>AMF: 6. INITIAL UE MESSAGE + AMF->>gNB: 8. UE CONTEXT SETUP + Note left of gNB: (NCR-authorized indication) +``` + +The diagram illustrates the call flow for solution 4 involving three entities: NCR, gNB, and AMF. The sequence of messages is as follows: 1. NCR sends a RACH preamble (MSG1) to gNB; 2. gNB responds with a RAR (MSG2); 3. NCR sends an RRCSetupRequest (MSG3) to gNB; 4. gNB responds with an RRCSetup (MSG4); 5. NCR sends an RRCSetupComplete message to gNB; 6. gNB sends an INITIAL UE MESSAGE to AMF; 7. Upon NAS registration, the AMF authorizes the NCR and sends an indication to the RAN (this step is shown in a separate box); 8. The AMF sends a UE CONTEXT SETUP message to gNB, which includes an (NCR-authorized indication). + +Sequence diagram showing the call flow for solution 4 between NCR, gNB, and AMF. + +Figure 8.1.4-1 Call flow for solution 4 + +Sequence of this solution: + +1. The NCR first accesses the network as a normal UE. +2. AMF authorizes the NCR and sends the indication to gNB in the UE CONTEXT SETUP REQUEST message. + +## 8.2 Specification impacts + +The specification impacts for each solution are listed in Table 8.2-1. + +Table 8.2-1. Comparison of solutions. + +| | Uu impact | RAN OAM impact | NG-C/NAS impact (Yes/No) | Authorization entity(RAN/CN/OAM) | Support of full protocol stack in control plane (RRC, NAS) (Yes/No) | Inter-vendor interoperability | Security | +|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|---------------------------------|----------------------------------------------------------------|----------------------------------------------------------------------------|--------------------------------------|-----------------------------------------------------------------------------------------| +| Solution 1 | Yes
1. Add NCR indicator in Msg5 and/or UE radio capability;
2. Add NCR credential information in a UL RRC message (FFS on which RRC message) | No
NO: If NCR validation is not secured.
YES: If secure NCR validation is needed. | No | CN(Uses slicing signaling to convey authorization information) | Yes | Yes | Uu uses legacy security

Optionally, NCR validation needs to be performed in RAN. | + +| | | | | | | | | +|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|-----------------------------------------------------------------------|-----|-----------------------------------------------|-----------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------| +| Solution 2 | Yes
1. Add NCR indicator and OAM container in Msg5;

2.a If RRC signalling is used for OAM traffic, add OAM container in UL RRC message (FFS on which RRC message, FFS on the need of DL RRC message).

2.b If DRB is used for OAM traffic, define a new DRB type (e.g. not associated with PDU session).

3. Further details on procedures impacts due to not having NAS are FFS and will be discussed in a potential WI. | Yes

Requires new OAM connectivity mechanism over RRC with NG-NR proxy function. | No | OAM | No

NAS is not needed for control plane | No

(Whether a specific OAM for NCR is needed belongs to deployment implementation based on Operator's policy.) | No security on Uu.

NCR authorization and validation needs to be secured via OAM. | +| Solution 3 | Yes
1. Add NCR indicator in Msg5 and/or UE radio capability; | No | Yes
NCR-indication and authorization via NG-C

No NAS impact | CN | Yes | Yes | Uu uses legacy security

CN provides secure NCR validation. | + +| | | | | | | | | +|------------|----|----|----------------------------------------------------|----|-----|-----|---------------------------------------------------------------| +| Solution 4 | No | No | Yes
No NAS impact
NCR authorization via NG-C | CN | Yes | Yes | Uu uses legacy security
CN provides secure NCR validation. | +|------------|----|----|----------------------------------------------------|----|-----|-----|---------------------------------------------------------------| + +Note: The remaining FFS will be addressed in normative phase. + +# 9 Performance evaluation + +Though there is no commonly agreed set of simulation assumptions in the study, in order to study side control information for NCR, evaluations have been performed in the submitted contributions and the following are observed: + +- For access link beam information: + - For FR2: + - [R1-2203237] shows that the NCRs with beam information can improve the SINR performance for UEs especially at 5%-tile, 50%-tile SINR. Meanwhile, compared to the conventional RF repeater, the additional interference due to the introduction of repeater can be mitigated for the UEs with above 95%-tile SINR. + - [R1-2203578] shows that the SINR performance of the UEs is improved compared with the case when there is no repeater when the NCR-Fwd beam is fixed to steer towards the cell edge. For cell edge UEs, the SINR gain is 2.3 dB for the 10%-tile SINR. When the NCR-Fwd beam is steering dynamically towards the UE, the SINR performance of the UEs is further improved compared to the case of the fixed NCR-Fwd beam. For cell edge UEs, the SINR gain is about 6.3 dB for the 10%-tile SINR. + - [R1-2203921] shows that by introducing repeaters with beamforming, 2.34 dB, 6.15 dB, and 6.53 dB gain can be achieved at 5%-tile, 50%-tile, and 95%-tile SINR compared to the case of NR system without repeaters, respectively. In addition, 2.03 dB, 5.18 dB, and 6.53 dB gains at 5%-tile, 50%-tile, and 95%-tile SINR can be achieved compared to the case with conventional repeaters, respectively. + - [R1-2204653] shows that performance gain on SINR can be achieved by introducing semi-static repeater gain/power configuration, and additional performance gain can be achieved by introducing dynamic repeater gain/power configuration. More than 5 dB gain can be further achieved by using large SCI payload for beam control for large NCR-Fwd antenna configuration. + - [R1-2205047] shows that adaptive access-link beamforming will offer performance gain by providing a larger beamforming gain and reducing the interference due to use of narrower beams, e.g., the median SINR can improve by 11dB. + - [R1-2206927] shows that the NCR with beamforming has SINR gains over gNB only and conventional RF repeater. Compared with gNB only, NCR has SINR improvements of about 1.42 dB, 1.44 dB, and 3.06 dB at 5%-tile, 50%-tile, and 95%-tile SINR. NCR could improve the coverage compared with gNB only and deployment with conventional RF repeaters. + - [R1-2206055] shows that the SINR performance of the UEs is further improved compared with the case of the fixed NCR-Fwd access link beam when the NCR beam is set adaptively towards the serving UE. Especially for the cell edge UE, the UL SINR gain is about 6.3 dB at 10%-tile of CDF and DL SINR gain is 8 dB for 10%-tile of CDF. + - [R1-2205875] shows that based on the evaluation methodology defined for NR coverage enhancements [3], the performance of NCR is evaluated for FR2 assuming a target data rates of 25 Mbps for DL and 5 Mbps for UL, target ISD of 200m, gNB EIRP of 65 dBm, UE EIRP of 29 dBm, NCR with DL EIRP of 40 dBm and gain of 90 dB. The achieved ISD by gNB only can be up to $140 \times \sqrt{3} = 242\text{m}$ for DL, and $100 \times \sqrt{3} = 173\text{m}$ for UL. With NCR, the DL coverage can be extended to an ISD of $175 \times \sqrt{3} = 300\text{m}$ , and the UL coverage can be extended to an ISD of $135 \times \sqrt{3} = 233\text{m}$ . + - For FR1: + +- [R1-2206018] shows that with indicated beam information, the SINR performance on FR1 in the O2I scenario are improved with around 5dB for 5%-tile SINR and 2dB for 50%-tile SINR after the deployment of NCR over gNB only, and NCR provides SINR gain compared to conventional RF repeater in all cases. According to the deterministic simulation based on Ray-tracing (RT) with realistic outdoor maps, NCRs with beam information can also improve the SINR performance on FR1 with 3dB gain for 5%-tile SINR and around 7 dB gain for the minimum value of SINR over gNB only. +- [R1-2206957] shows that NCR can provide SINR gains for more than 80% of indoor UEs in case that side control information (SCI as defined in clause 6.1) with 4 bits are used for beam information compared to the conventional repeater while the UE SINR with gNB only case (from 0%-tile SINR to 40%-tile SINR) is around 1 dB better than the case with either NCR or conventional repeaters. +- [R1-2205875] shows that based on the evaluation methodology defined for NR coverage enhancements [3], the performance of NCR is evaluated for FR1 assuming a target data rates of 10 Mbps for DL and 1 Mbps for UL, target ISD of 500m, gNB EIRP of 70 dBm, UE EIRP of 26 dBm, NCR with DL EIRP of 32 dBm and gain of 65 dB. The achieved ISD by gNB only can be up to $400 \times \sqrt{3} = 693$ m for both UL and DL. The target coverage for FR1 can be achieved with BS only. +- For the ON-OFF information used to control the ON-OFF behaviour of NCR-Fwd: + - [R1-2203237] shows that NCRs with ON-OFF information can mitigate the interference for high SINR UEs while maintain the performance of low SINR UEs, and also ON-OFF information can provide efficient interference management in FR1. + - [R1-2203578] shows that about 9.8dB gain can be achieved for the 10%-tile UEs on the SINR performance after introducing ON-OFF indication. + - [R1-2203921] shows that additional gain is observed for the repeater by both applying beamforming and on/off management compare to the NR system with the repeater only applying beamforming. + - [R1-2205047] shows that about 2 dB gains on median SINR can be achieved by introducing dynamic on-off information. +- For the power control information used to control the behaviour of NCR-Fwd for the DL of access link and/or UL of backhaul link: + - [R1-2203133] shows that for the uplink transmission via NCR, a fixed NCR amplifying gain may lead to interference to the gNB or NCR UL coverage loss. For the downlink transmission via NCR, a fixed NCR amplifying gain may lead to NCR-Fwd saturation or NCR DL coverage loss. + - [R1-2203578] shows that the optimal system performance can be achieved when repeater's gain is set to a proper value. + - [R1-2204653] shows that dynamic repeater gain/power control can provide additional SINR gain over semi-static repeater gain/power configuration. + - [R1-2204642] shows that the gain control is needed for self-interference management due to repeater oscillation. + +# 10 Conclusion + +RAN1 has studied the side control information for NCR with corresponding signalling (including its configuration). The SI phase is completed in RAN1 and the following are recommended to be specified as part of Rel-18 NCR WI from RAN1's perspective: + +- Beam information as side control information +- ON-OFF information as side control information +- UL-DL TDD configuration and NCR's behaviour over flexible symbols. + +Based on RAN3 analysis, the 4 candidate solutions may be further discussed pending confirmation from SA3 and SA5. With the captured content in TR38.867, RAN3 believe the SI phase is completed. + +Based on RAN2 analysis, early identification (via Msg1 or Msg3) for NCR is not needed. From security point of view, the feasibility of NCR validation procedure in solution 1 and the feasibility of solution 2 will be decided by SA3 in + +potential WI. With the captured content in TR38.867, RAN2 believe the SI phase is completed. Down selection of all captured solutions may take place in potential WI phase based on the feedback from other groups. + +# --- Annex A: Cost evaluations + +Two companies provided cost analysis results for network controlled repeaters in [R1-2205875] and [R1-2206018]. Note that there was no RAN1 conclusion or observation with reference to cost analysis of network controlled repeaters. + +# --- Annex B: Change history + +| Change history | | | | | | | | +|----------------|-----------|------------|----|-----|-----|-----------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-05 | RAN1#109e | R1-2205231 | | | | TR Skeleton | 0.0.0 | +| 2022-05 | RAN1#109e | R1-2205496 | | | | Capture the agreement in RAN1#109e | 0.1.0 | +| 2022-08 | RAN1#110 | R1-2208314 | | | | Capture the agreement in RAN1#110 with conclusion for RAN1;
Capture the endorsed TP from RAN3 and RAN2 | 0.2.0 | +| 2022-09 | RAN#97e | RP-222323 | | | | For one step approval to RAN#97e plenary | 1.0.0 | +| 2022-09 | RAN#97e | | | | | TR under change control further to RAN approval as part of Rel-18 | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38869/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-18/38_series/38869/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98e74761b854fecf1363232a71f4c0c0c5ffa36d --- /dev/null +++ b/marked/Rel-18/38_series/38869/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:653bc0cd5d9ba2b8109b3c24f159a9b992ff0cf5048549a3364f7f80e79a9660 +size 17468 diff --git a/marked/Rel-18/38_series/38869/01465752f3ac36c403672804f406a676_img.jpg b/marked/Rel-18/38_series/38869/01465752f3ac36c403672804f406a676_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b177db1e70265fc645c50f1301a614b5e405133a --- /dev/null +++ b/marked/Rel-18/38_series/38869/01465752f3ac36c403672804f406a676_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:033b3a2d822c994c50d0ad1086435fe5946aba8956e991975585ca0801e51512 +size 40218 diff --git a/marked/Rel-18/38_series/38869/04867b54e8cdb31a034edbb472a41162_img.jpg b/marked/Rel-18/38_series/38869/04867b54e8cdb31a034edbb472a41162_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..01352e50305e2e5d2a9dc7652752cd5d867fd565 --- /dev/null +++ b/marked/Rel-18/38_series/38869/04867b54e8cdb31a034edbb472a41162_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6afc35b01e405a903575f091d20369d10c8875501c373204238e012a156bb465 +size 15645 diff --git a/marked/Rel-18/38_series/38869/068b3a3247570c4b78342a943f15de9e_img.jpg b/marked/Rel-18/38_series/38869/068b3a3247570c4b78342a943f15de9e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9cd2947a596fae5ca9f0204aabc700067257df4e --- /dev/null +++ b/marked/Rel-18/38_series/38869/068b3a3247570c4b78342a943f15de9e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6118bf049ba7c48b9ee526ef39c300cc8858792851d7ea58b139f6ab7ea763f5 +size 25031 diff --git a/marked/Rel-18/38_series/38869/0efa7ad912af40ff136572a5e4b7634e_img.jpg b/marked/Rel-18/38_series/38869/0efa7ad912af40ff136572a5e4b7634e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3d90c4ab04deb4a852f9796a3658441f81ce9fad --- /dev/null +++ b/marked/Rel-18/38_series/38869/0efa7ad912af40ff136572a5e4b7634e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f2433da4c158988b465f02a9f9ee0a4d2f7c2bf6eb622665713f62d21ee23ced +size 47339 diff --git a/marked/Rel-18/38_series/38869/1049b682c4030f4146b73523cf5f1836_img.jpg b/marked/Rel-18/38_series/38869/1049b682c4030f4146b73523cf5f1836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ecf19a8e9aa89207ce986b45d9a12025cd6ad045 --- /dev/null +++ b/marked/Rel-18/38_series/38869/1049b682c4030f4146b73523cf5f1836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d105d4c13082012013d023c1babd8bc51eb2cd4c74edd13104c7dd25edac24b +size 66425 diff --git a/marked/Rel-18/38_series/38869/11db12d759747ec7aecc281e18d56461_img.jpg b/marked/Rel-18/38_series/38869/11db12d759747ec7aecc281e18d56461_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d4487b579a60cd1d8af71d1182d3508a999ae61c --- /dev/null +++ b/marked/Rel-18/38_series/38869/11db12d759747ec7aecc281e18d56461_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bdd11174ce04453144cfbd105ae9df01f38b55de9582f1fecd4a25e54c208e59 +size 83139 diff --git a/marked/Rel-18/38_series/38869/12b521317c2c8ea33a1382d83e2b76be_img.jpg b/marked/Rel-18/38_series/38869/12b521317c2c8ea33a1382d83e2b76be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..164fba629c1778d1ceef69e934460e2d8e8b6d23 --- /dev/null +++ b/marked/Rel-18/38_series/38869/12b521317c2c8ea33a1382d83e2b76be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5458738070ab4b9105a6d61cd644bd1dd7f6cedcf46b60f26f2c01f3fcdc845f +size 122830 diff --git a/marked/Rel-18/38_series/38869/13ad8b2f9a6880472489e44a4740290f_img.jpg b/marked/Rel-18/38_series/38869/13ad8b2f9a6880472489e44a4740290f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6451a7491e0070aa89728ac11509021b9d79e55 --- /dev/null +++ b/marked/Rel-18/38_series/38869/13ad8b2f9a6880472489e44a4740290f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:486879fe94e7d7a4efd5ec994cf82dc6897d81b38d3807f7e7467ab3382c83fe +size 52840 diff --git a/marked/Rel-18/38_series/38869/1406d3fbba2b2fce2607beceace3b6fa_img.jpg b/marked/Rel-18/38_series/38869/1406d3fbba2b2fce2607beceace3b6fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5bd78ad112e7522c4fc4ab0e0379e8c9e0073d7f --- /dev/null +++ b/marked/Rel-18/38_series/38869/1406d3fbba2b2fce2607beceace3b6fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:61a5fb40e0c5751ec2403484ede190837074a8663a17915844c8231048c14528 +size 133109 diff --git a/marked/Rel-18/38_series/38869/1412b8b99f2a03e5f16e3a6d3bc4f946_img.jpg b/marked/Rel-18/38_series/38869/1412b8b99f2a03e5f16e3a6d3bc4f946_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cadb400673c3dbf1c21e89b0c0035675b89b15ec --- /dev/null +++ b/marked/Rel-18/38_series/38869/1412b8b99f2a03e5f16e3a6d3bc4f946_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:618b57466fd22d04489b174f19557da0805019e4bd2fd71b2ca40dd87247331e +size 30876 diff --git a/marked/Rel-18/38_series/38869/145582dc8830099a0aa6ca1234f0acd1_img.jpg b/marked/Rel-18/38_series/38869/145582dc8830099a0aa6ca1234f0acd1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1aff4669b54154c27d07a700350afd1c2b6faaac --- /dev/null +++ b/marked/Rel-18/38_series/38869/145582dc8830099a0aa6ca1234f0acd1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9638486417ad7d1246c3d0fd908d2223cdbfaaf49ef797d3856a2b6154d10e00 +size 137981 diff --git a/marked/Rel-18/38_series/38869/16e0c05af74544fa9507b96945de0a53_img.jpg b/marked/Rel-18/38_series/38869/16e0c05af74544fa9507b96945de0a53_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ad2649f880173fb3167c5c2da1423f808439482 --- /dev/null +++ b/marked/Rel-18/38_series/38869/16e0c05af74544fa9507b96945de0a53_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3fecf6ca76e58bc7a026708020350b92e9a52b6b4fdfffbaf81fc5f84e264b8b +size 77860 diff --git a/marked/Rel-18/38_series/38869/19d41b4b2af3e9bd470c86b6067a822e_img.jpg b/marked/Rel-18/38_series/38869/19d41b4b2af3e9bd470c86b6067a822e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c3a99184743cbb0c7de2a188279919182e1ec6ea --- /dev/null +++ b/marked/Rel-18/38_series/38869/19d41b4b2af3e9bd470c86b6067a822e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b12ea3f4706954192e09090655d4baf46657062eac6929b94f6f3d8a86834419 +size 83507 diff --git a/marked/Rel-18/38_series/38869/1a09fb1ec1922a373a14bff45ebf433e_img.jpg b/marked/Rel-18/38_series/38869/1a09fb1ec1922a373a14bff45ebf433e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb3bd971c02120c7509ea44e13646ae82f262efe --- /dev/null +++ b/marked/Rel-18/38_series/38869/1a09fb1ec1922a373a14bff45ebf433e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b28cdd083fad8067001c3076970d716cd808b591aae19b9bedf5da3dbb5859b0 +size 28143 diff --git a/marked/Rel-18/38_series/38869/1b1f1c6f7ba93ebe3c4f9b812d7476f9_img.jpg b/marked/Rel-18/38_series/38869/1b1f1c6f7ba93ebe3c4f9b812d7476f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a3d3a999a054f2247d69fb06d5cc91139a7fbe3f --- /dev/null +++ b/marked/Rel-18/38_series/38869/1b1f1c6f7ba93ebe3c4f9b812d7476f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5bd7b5c6cc6e3826e07f883df0816d703f83f43dc64629948f7e83fdfbd36c99 +size 50999 diff --git a/marked/Rel-18/38_series/38869/1bc1bf231ada31f57cd9f0d8791b784b_img.jpg b/marked/Rel-18/38_series/38869/1bc1bf231ada31f57cd9f0d8791b784b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b15e000077136cb36aac3b7f5b5e7a91fe4b5764 --- /dev/null +++ b/marked/Rel-18/38_series/38869/1bc1bf231ada31f57cd9f0d8791b784b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c070e38e00e6b0c222342df402e78cd9090c0baab52f2f45b6c7e6b552a31716 +size 123848 diff --git a/marked/Rel-18/38_series/38869/1c29dadab94c3fa552d270434db09c81_img.jpg b/marked/Rel-18/38_series/38869/1c29dadab94c3fa552d270434db09c81_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc9c43f15e9addbeff6d8ca0e8beacd19855afa5 --- /dev/null +++ b/marked/Rel-18/38_series/38869/1c29dadab94c3fa552d270434db09c81_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b317720c9ef822fa4e60ad8cec8f61213c326cd96002c5fb65577fac9ac90e1d +size 20636 diff --git a/marked/Rel-18/38_series/38869/1c4139270d1edff9631800a63eabf7f5_img.jpg b/marked/Rel-18/38_series/38869/1c4139270d1edff9631800a63eabf7f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db613ae12be1abd91d0d162054b275746e07e2a9 --- /dev/null +++ b/marked/Rel-18/38_series/38869/1c4139270d1edff9631800a63eabf7f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c3340a22c274e03ee1a8e414e95f4b8159e31e397aebde2a2f965703baac897c +size 53964 diff --git a/marked/Rel-18/38_series/38869/1da66f5fec34c001912c84a9abf145d7_img.jpg b/marked/Rel-18/38_series/38869/1da66f5fec34c001912c84a9abf145d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cea426baadab35417745786bd01906a7cee92209 --- /dev/null +++ b/marked/Rel-18/38_series/38869/1da66f5fec34c001912c84a9abf145d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bdf1f166f80503a72e8a00604d2613cd4570b7b9f7b0631b3d743d197b0d8532 +size 27694 diff --git a/marked/Rel-18/38_series/38869/1e5fb3b39d2ba42bd8f27bbd48277f26_img.jpg b/marked/Rel-18/38_series/38869/1e5fb3b39d2ba42bd8f27bbd48277f26_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db61cb165da75940de42fe233a5754f7f4a781b9 --- /dev/null +++ b/marked/Rel-18/38_series/38869/1e5fb3b39d2ba42bd8f27bbd48277f26_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de8815b76001bd946078bbd25a340d775fa7c32fd44c097591f6d67ac717bcfa +size 148505 diff --git a/marked/Rel-18/38_series/38869/1ecdc32fbc05ff26a3181147d0c3ba29_img.jpg b/marked/Rel-18/38_series/38869/1ecdc32fbc05ff26a3181147d0c3ba29_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ee80a2d36541c4752494f3744bacf960a43989e4 --- /dev/null +++ b/marked/Rel-18/38_series/38869/1ecdc32fbc05ff26a3181147d0c3ba29_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9c5d27fbd134654e78e75b105f44d6fd8d3744d9af944fb1969d4d5c31b3a98 +size 108678 diff --git a/marked/Rel-18/38_series/38869/20136850feb70fd71c7d41cdae203ebb_img.jpg b/marked/Rel-18/38_series/38869/20136850feb70fd71c7d41cdae203ebb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e36c20850b3dbd1805c1ae71add57dd376a9d47 --- /dev/null +++ b/marked/Rel-18/38_series/38869/20136850feb70fd71c7d41cdae203ebb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d1ef419ad810381d00be9c2b54246e095e01ddca1826f0a940225c3721e9bf7 +size 18286 diff --git a/marked/Rel-18/38_series/38869/201de44da5d99899a8cf58eac2fa7bc9_img.jpg b/marked/Rel-18/38_series/38869/201de44da5d99899a8cf58eac2fa7bc9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d11661ea6048a6d4db8543237205d182bfd4d6f --- /dev/null +++ b/marked/Rel-18/38_series/38869/201de44da5d99899a8cf58eac2fa7bc9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6628482f9a91be9cb24490001a0cd693d0c620c32ae67a8eb1c8e53d0fc3b6d +size 119743 diff --git a/marked/Rel-18/38_series/38869/21282638f01b60bb72acf07272e24942_img.jpg b/marked/Rel-18/38_series/38869/21282638f01b60bb72acf07272e24942_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82661930c9ce5e39667812cf695459f86ca9b5be --- /dev/null +++ b/marked/Rel-18/38_series/38869/21282638f01b60bb72acf07272e24942_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d21e1e0668de98502cd7de6faee7772d81c7bd27c4f2a6822cd7defd27259ec3 +size 55754 diff --git a/marked/Rel-18/38_series/38869/24f9540e133ae0abdd0948928f8431a3_img.jpg b/marked/Rel-18/38_series/38869/24f9540e133ae0abdd0948928f8431a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a5f366b09a0c49707160f306c95e7a2db5ff462 --- /dev/null +++ b/marked/Rel-18/38_series/38869/24f9540e133ae0abdd0948928f8431a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dae70015023b42f942aabec46e1b887adf51d5f61911285df319085b4e3ca500 +size 129314 diff --git a/marked/Rel-18/38_series/38869/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Rel-18/38_series/38869/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bb7bf5e6723ff1029508ddc11162021df8443dbc --- /dev/null +++ b/marked/Rel-18/38_series/38869/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c8a30ba4a632403fac492a1dbfccaf4576252f03279979a021bd9ba2e9fd2b6 +size 57428 diff --git a/marked/Rel-18/38_series/38869/288a76ff69a5008dc84b35f1587f2896_img.jpg b/marked/Rel-18/38_series/38869/288a76ff69a5008dc84b35f1587f2896_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba8f6a20b582817f4527f82fdcf6a1113d43be9f --- /dev/null +++ b/marked/Rel-18/38_series/38869/288a76ff69a5008dc84b35f1587f2896_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4dcd0b7e391d809e39425ed3e763446cfef7219127720e0b4102b47e4dca4964 +size 71957 diff --git a/marked/Rel-18/38_series/38869/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-18/38_series/38869/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..33d38212680677e0c02521bda8dd125b9f28037a --- /dev/null +++ b/marked/Rel-18/38_series/38869/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b2b666a685e629028ca88f53b14d5d2fd33223b58e6f2a0277fff676974eb76f +size 13186 diff --git a/marked/Rel-18/38_series/38869/28eba83fac6219415e57d8d2d5f37a2b_img.jpg b/marked/Rel-18/38_series/38869/28eba83fac6219415e57d8d2d5f37a2b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd2815c12acd7f752c0ff05adb00483d37d3c4db --- /dev/null +++ b/marked/Rel-18/38_series/38869/28eba83fac6219415e57d8d2d5f37a2b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de0ff45225ad090cad945aa2d5ff515495892903082d79133a0fc0215b93e484 +size 107522 diff --git a/marked/Rel-18/38_series/38869/2cf3896394a2342a2b46c504ab9a8830_img.jpg b/marked/Rel-18/38_series/38869/2cf3896394a2342a2b46c504ab9a8830_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e54ef5e06366f2e1d256ceab4d85ecb2488f76bc --- /dev/null +++ b/marked/Rel-18/38_series/38869/2cf3896394a2342a2b46c504ab9a8830_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:15023b28fdc37f8378d5f61702ccac79e7aa985bbb39e2bff479a9047149feed +size 50076 diff --git a/marked/Rel-18/38_series/38869/2d62ff2bded0c21414a0f40fdf8fd537_img.jpg b/marked/Rel-18/38_series/38869/2d62ff2bded0c21414a0f40fdf8fd537_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60a39ee4c3f53e57a2da4271ab404903b802d448 --- /dev/null +++ b/marked/Rel-18/38_series/38869/2d62ff2bded0c21414a0f40fdf8fd537_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2fd8c7cc8c3537f0a441c84db76a4abf03a6ed3c3f03c6d04a40f6f928efdc69 +size 20112 diff --git a/marked/Rel-18/38_series/38869/2ef0ed2df58828f36a728bc60148d841_img.jpg b/marked/Rel-18/38_series/38869/2ef0ed2df58828f36a728bc60148d841_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f0b1a3b6c2c8357b309f8063509df7cbf597e04 --- /dev/null +++ b/marked/Rel-18/38_series/38869/2ef0ed2df58828f36a728bc60148d841_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:775a093d703fe16500bd62c4703d64efc40a88cc68cd4d314129261cb456da33 +size 93144 diff --git a/marked/Rel-18/38_series/38869/2fd08022cb2acbb95b368fd2e788864b_img.jpg b/marked/Rel-18/38_series/38869/2fd08022cb2acbb95b368fd2e788864b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..66fb05d844c76725fc8229d81eceb219845d2f82 --- /dev/null +++ b/marked/Rel-18/38_series/38869/2fd08022cb2acbb95b368fd2e788864b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:74a308c5f46470a0033d890eec14716867cc90f15e3dea5947f81747ea647a50 +size 100642 diff --git a/marked/Rel-18/38_series/38869/343e05a9fd8a8c8743428fa4ae6e2736_img.jpg b/marked/Rel-18/38_series/38869/343e05a9fd8a8c8743428fa4ae6e2736_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d4f721eb981b75ee7554eab8d537e34bb7db0c0 --- /dev/null +++ b/marked/Rel-18/38_series/38869/343e05a9fd8a8c8743428fa4ae6e2736_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4638f1734a5c970a9fdbabc57b14180bdf5cecec1be44f8f915c9ee063387973 +size 25047 diff --git a/marked/Rel-18/38_series/38869/37a96d647a34d2c514364514c7f85f41_img.jpg b/marked/Rel-18/38_series/38869/37a96d647a34d2c514364514c7f85f41_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8cc256d7b6796fc0c520d0b658d8f0a59b26dc00 --- /dev/null +++ b/marked/Rel-18/38_series/38869/37a96d647a34d2c514364514c7f85f41_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ef56b091fc0fd8c0e9271c7d6a00c5cc0eb30044e98b13ea6964de0589f9240 +size 26029 diff --git a/marked/Rel-18/38_series/38869/3cf35f2c4cf5c2e828f8ca6d6fbfffe7_img.jpg b/marked/Rel-18/38_series/38869/3cf35f2c4cf5c2e828f8ca6d6fbfffe7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e652b0693fde7491ecaf59846677b16eb0417f77 --- /dev/null +++ b/marked/Rel-18/38_series/38869/3cf35f2c4cf5c2e828f8ca6d6fbfffe7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5fa8c87955444c509e2d1ba1e64bf4a476618de228c90dbd7edae8cba773d6d +size 70502 diff --git a/marked/Rel-18/38_series/38869/440236efe61277b409f0f16c982945c4_img.jpg b/marked/Rel-18/38_series/38869/440236efe61277b409f0f16c982945c4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56db5f2ce398012f4429c840c10db91244d5a67c --- /dev/null +++ b/marked/Rel-18/38_series/38869/440236efe61277b409f0f16c982945c4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:42c5ae170b56081ccc06628d4ba94ce9d189b16cab5a537b634b3ce1f5581c74 +size 79528 diff --git a/marked/Rel-18/38_series/38869/449d2799e97657d8fa5897b2e74a88bd_img.jpg b/marked/Rel-18/38_series/38869/449d2799e97657d8fa5897b2e74a88bd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a1a0bb4bf7f1a344ea5dea50fde359e8f947346 --- /dev/null +++ b/marked/Rel-18/38_series/38869/449d2799e97657d8fa5897b2e74a88bd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9da51e8329a4cf21f708efa45c6fb77968d8dec6c52d1e460fb6c73ac8c1cb7c +size 30495 diff --git a/marked/Rel-18/38_series/38869/46354e78fc94fa64a2d49f26a2a24c80_img.jpg b/marked/Rel-18/38_series/38869/46354e78fc94fa64a2d49f26a2a24c80_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c673fc74e9c60f3b68cf25dc37a6b816d3ef4d3d --- /dev/null +++ b/marked/Rel-18/38_series/38869/46354e78fc94fa64a2d49f26a2a24c80_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:754c79d22e69b9b9dbec5f6a18c4e313ae05ba3cf3bef781ccd3fa199e910ac0 +size 146271 diff --git a/marked/Rel-18/38_series/38869/475c496c4cd20198211aeaa241af7279_img.jpg b/marked/Rel-18/38_series/38869/475c496c4cd20198211aeaa241af7279_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..34b09236342fadbc9802605d2660e1dc0aeace51 --- /dev/null +++ b/marked/Rel-18/38_series/38869/475c496c4cd20198211aeaa241af7279_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0fb4be022aa8c2b40913c29d0120634a920e37982c61d978fc16786293d00b8e +size 63979 diff --git a/marked/Rel-18/38_series/38869/47b777ee3717213cab7c153aa17f11a0_img.jpg b/marked/Rel-18/38_series/38869/47b777ee3717213cab7c153aa17f11a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1090ce1ec9ab8229c9cd17fcd6174ed36e333fc9 --- /dev/null +++ b/marked/Rel-18/38_series/38869/47b777ee3717213cab7c153aa17f11a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:129112074fc0204dd7316e636b4059b29228a82d810205ec8830ced760348a98 +size 41025 diff --git a/marked/Rel-18/38_series/38869/48fc91e19c1a9b6674b120fbdd89b203_img.jpg b/marked/Rel-18/38_series/38869/48fc91e19c1a9b6674b120fbdd89b203_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4649a12e3189f640ff4c951cb46ac4a36c687b5d --- /dev/null +++ b/marked/Rel-18/38_series/38869/48fc91e19c1a9b6674b120fbdd89b203_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b3f9a2a4b965a425f2d7e5466a636d0d76b01360b6eb08e37d636b5e2276f3e1 +size 41232 diff --git a/marked/Rel-18/38_series/38869/4908c132d4fbad657b6fc84561c43fbb_img.jpg b/marked/Rel-18/38_series/38869/4908c132d4fbad657b6fc84561c43fbb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2408573db7d622f0e757066931ad2eba8fbafc75 --- /dev/null +++ b/marked/Rel-18/38_series/38869/4908c132d4fbad657b6fc84561c43fbb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c75c4bfdfa0affd5beb9a69e345840b918f51376219b90ba32a7e894f4e80c5 +size 27193 diff --git a/marked/Rel-18/38_series/38869/4a1a443e646ed6c5b8e0973a9e434c63_img.jpg b/marked/Rel-18/38_series/38869/4a1a443e646ed6c5b8e0973a9e434c63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e224d50e60f8d5a2191cea11270bdd79a01633ba --- /dev/null +++ b/marked/Rel-18/38_series/38869/4a1a443e646ed6c5b8e0973a9e434c63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:92913aba586d52f0cb49bdf95c26631fa49e551c17672879e39fab6d2c180d59 +size 65265 diff --git a/marked/Rel-18/38_series/38869/4a8f09807c20be2a38e37e719a575eac_img.jpg b/marked/Rel-18/38_series/38869/4a8f09807c20be2a38e37e719a575eac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f69bcd8041069986ec8342f6869f9154df5aa9a --- /dev/null +++ b/marked/Rel-18/38_series/38869/4a8f09807c20be2a38e37e719a575eac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1c3aa0abbcc2faaf10694b2227e1e6fc6d9a97a48b1815e7feffaa0d737c4e48 +size 92764 diff --git a/marked/Rel-18/38_series/38869/4ab1525224406b5595a7773da65d3d62_img.jpg b/marked/Rel-18/38_series/38869/4ab1525224406b5595a7773da65d3d62_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..552ec8311b6bfc0d9929edb74354db959612df95 --- /dev/null +++ b/marked/Rel-18/38_series/38869/4ab1525224406b5595a7773da65d3d62_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67ef793d6fd092bc2aede0cf1684c3a9205cace45192bbcaf28dcb34fe2eea14 +size 157085 diff --git a/marked/Rel-18/38_series/38869/4bff5f22997753bcf1997c715118012d_img.jpg b/marked/Rel-18/38_series/38869/4bff5f22997753bcf1997c715118012d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cbd6d160d8c8643320c72f21935d2d3e4c1914a0 --- /dev/null +++ b/marked/Rel-18/38_series/38869/4bff5f22997753bcf1997c715118012d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b14f779c10081899151522c46f26634fa869e0657fa7d190c5b87c63b57efb3 +size 29423 diff --git a/marked/Rel-18/38_series/38869/4d34414c7275440623d6ea15c13713f7_img.jpg b/marked/Rel-18/38_series/38869/4d34414c7275440623d6ea15c13713f7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74ee0eb691e6abc0bfd9ba3c91e71ae32744551d --- /dev/null +++ b/marked/Rel-18/38_series/38869/4d34414c7275440623d6ea15c13713f7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d817368a11592921120d2cf9c4207ebe035aebd6a756411d1fc6556031c5ffa +size 94579 diff --git a/marked/Rel-18/38_series/38869/516d9f1866cc2e359a35fb1d8c046454_img.jpg b/marked/Rel-18/38_series/38869/516d9f1866cc2e359a35fb1d8c046454_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3208b7eccacc5649513972c53a2653ed9d511ee0 --- /dev/null +++ b/marked/Rel-18/38_series/38869/516d9f1866cc2e359a35fb1d8c046454_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:641def96b8a8997f0d704bf1ca03dc538a2853666fed74c14797ac9e3c1c1a09 +size 32266 diff --git a/marked/Rel-18/38_series/38869/578d2763eaf3edf3f1bd6657455ad54a_img.jpg b/marked/Rel-18/38_series/38869/578d2763eaf3edf3f1bd6657455ad54a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bed1ed05451e2b48a2c64dfb0803cf35457c1ed6 --- /dev/null +++ b/marked/Rel-18/38_series/38869/578d2763eaf3edf3f1bd6657455ad54a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e1982acf7e7422ec9f4ab3cc400d51795a014e8c81da4e1f3cedbb699dff9bd4 +size 107576 diff --git a/marked/Rel-18/38_series/38869/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg b/marked/Rel-18/38_series/38869/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4431e0235aa410408c23afb073757114c16c1599 --- /dev/null +++ b/marked/Rel-18/38_series/38869/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:63820457dad9889ed96bf21945a6d132857286bd2612efe6702f5bb5bd702529 +size 37812 diff --git a/marked/Rel-18/38_series/38869/5edd3710b7b5d815ca793a5a5acd806e_img.jpg b/marked/Rel-18/38_series/38869/5edd3710b7b5d815ca793a5a5acd806e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..46d43f1b982227c18e94f36804bbcf937a970005 --- /dev/null +++ b/marked/Rel-18/38_series/38869/5edd3710b7b5d815ca793a5a5acd806e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:200fbde6144a99497bea47325f23262099929bdd4e1c701a48ac935886192f89 +size 84570 diff --git a/marked/Rel-18/38_series/38869/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38869/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8968497670357ddaa018ae71d16c4e068eae784f --- /dev/null +++ b/marked/Rel-18/38_series/38869/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:79fe1102465ce6d931313f3b8b2cb56207e26bc86bb234be28bab48f94ea74a1 +size 9367 diff --git a/marked/Rel-18/38_series/38869/60e76fd7ce476eeef8a30381323fb97c_img.jpg b/marked/Rel-18/38_series/38869/60e76fd7ce476eeef8a30381323fb97c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82f37d74f81424c2a5c00a2d89159b878d8e852d --- /dev/null +++ b/marked/Rel-18/38_series/38869/60e76fd7ce476eeef8a30381323fb97c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c6b398768f7af23b33770550df9526da74585bbc4241de1e519a7259d8982873 +size 106228 diff --git a/marked/Rel-18/38_series/38869/61e3d8dbce06e400d42d8b708d1fa4f4_img.jpg b/marked/Rel-18/38_series/38869/61e3d8dbce06e400d42d8b708d1fa4f4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..72ef61f711941a8ac03cc62da41f18b9d7a0a59c --- /dev/null +++ b/marked/Rel-18/38_series/38869/61e3d8dbce06e400d42d8b708d1fa4f4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d0cc6af097911a12b2f1b0b52891ba725f17481a781647582a83f5f9c86cdea5 +size 122600 diff --git a/marked/Rel-18/38_series/38869/625ccd1bc0767416d87b542a7fa16bba_img.jpg b/marked/Rel-18/38_series/38869/625ccd1bc0767416d87b542a7fa16bba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5532e6cd7e6545c9edaa155bf3f63730b77ab5f --- /dev/null +++ b/marked/Rel-18/38_series/38869/625ccd1bc0767416d87b542a7fa16bba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83ff3d83c8fad04904129a00b2c18a319504ecb4ac463e8afd461c9c4f02d0ac +size 66804 diff --git a/marked/Rel-18/38_series/38869/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38869/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1605c3cb6d349bda36d9f5c70b59043bdd5571c9 --- /dev/null +++ b/marked/Rel-18/38_series/38869/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75696ee6874020e27b2eed572765d70cf129861cbfbfb7ed091ce7aeb4c33053 +size 5529 diff --git a/marked/Rel-18/38_series/38869/6470d350326789d5306eabcb76533951_img.jpg b/marked/Rel-18/38_series/38869/6470d350326789d5306eabcb76533951_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..123281ed88e75a460ee4d4842edf73a16a306a27 --- /dev/null +++ b/marked/Rel-18/38_series/38869/6470d350326789d5306eabcb76533951_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1a1deca95d1b214e81eca74e4e8b04f6af42b03c1943af27ac03ef1feeccaf9 +size 30284 diff --git a/marked/Rel-18/38_series/38869/677895e18a11676be0d822ac49108de3_img.jpg b/marked/Rel-18/38_series/38869/677895e18a11676be0d822ac49108de3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82a8d58c67c3fc0bff64fed2a172f1d435790819 --- /dev/null +++ b/marked/Rel-18/38_series/38869/677895e18a11676be0d822ac49108de3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f6fbdc2f290d27bfc5f9062e0a98a9a668d327b3d26dde7b39475dda8fe0c717 +size 79291 diff --git a/marked/Rel-18/38_series/38869/6f1d6debd3f3eada4104f0302c912672_img.jpg b/marked/Rel-18/38_series/38869/6f1d6debd3f3eada4104f0302c912672_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f56924578a5aad563eed8a94ce50adb67353c37 --- /dev/null +++ b/marked/Rel-18/38_series/38869/6f1d6debd3f3eada4104f0302c912672_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:54288af3dd44bbd6a12f6ce48698155f31b859d59547817e2ed5bcf111ab6f50 +size 49473 diff --git a/marked/Rel-18/38_series/38869/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg b/marked/Rel-18/38_series/38869/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac034dd8a354cec9cccb3dde6c6fbfbec3a29c09 --- /dev/null +++ b/marked/Rel-18/38_series/38869/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de315f788dd3c449cf919267e7ae4456d63b06c7287bb34fa87629c9e5b3f733 +size 9575 diff --git a/marked/Rel-18/38_series/38869/70ececdbb871824c3e57cace6262c4d6_img.jpg b/marked/Rel-18/38_series/38869/70ececdbb871824c3e57cace6262c4d6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c270def2b0d28f581ea07f6e5fee4e6c658758f --- /dev/null +++ b/marked/Rel-18/38_series/38869/70ececdbb871824c3e57cace6262c4d6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5829ba85860153d4755032eb576587814ae4b18a2ae21bb7c03dffe7d8e9b866 +size 41695 diff --git a/marked/Rel-18/38_series/38869/71e280cefea925145ac0bf9a48da8637_img.jpg b/marked/Rel-18/38_series/38869/71e280cefea925145ac0bf9a48da8637_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..595516a455bcad68f7aada1457466c5223ba05b4 --- /dev/null +++ b/marked/Rel-18/38_series/38869/71e280cefea925145ac0bf9a48da8637_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:367f545d1717145f9d7689b56ac8bfe5affed3950b858325b7e08cc418d3a0a1 +size 99251 diff --git a/marked/Rel-18/38_series/38869/73da53f7da73c0e2ead71eb1e2f746fb_img.jpg b/marked/Rel-18/38_series/38869/73da53f7da73c0e2ead71eb1e2f746fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d6503389ce5bab63f889ece82f080e448e5e9f5e --- /dev/null +++ b/marked/Rel-18/38_series/38869/73da53f7da73c0e2ead71eb1e2f746fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc61ef2d243e7a377656147ae09a63b47bd9644c36a0dce84629f67a3efbb5c5 +size 14897 diff --git a/marked/Rel-18/38_series/38869/740849dde4b891055485e0c3eea8664a_img.jpg b/marked/Rel-18/38_series/38869/740849dde4b891055485e0c3eea8664a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..674ff265efc46f3179578361d75911fcc00ee22f --- /dev/null +++ b/marked/Rel-18/38_series/38869/740849dde4b891055485e0c3eea8664a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1b1da8167fe3dd033b46fe417c9bb6cb2c3bc33051cc4e65343c93e7a3d38f0d +size 88343 diff --git a/marked/Rel-18/38_series/38869/74448f9178da618d823e5a5dadc56fb5_img.jpg b/marked/Rel-18/38_series/38869/74448f9178da618d823e5a5dadc56fb5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e009c87c714447d1f1899d1eba4fa30fc281fbdf --- /dev/null +++ b/marked/Rel-18/38_series/38869/74448f9178da618d823e5a5dadc56fb5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2afad6f4d5d24eedb7dc39605414f213895fefbe47e395f049b95bbc26441b00 +size 28886 diff --git a/marked/Rel-18/38_series/38869/7498bf530d9e13633524982a399d4439_img.jpg b/marked/Rel-18/38_series/38869/7498bf530d9e13633524982a399d4439_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..89f789a14b497e2139d3ee901e9050f00dc377e3 --- /dev/null +++ b/marked/Rel-18/38_series/38869/7498bf530d9e13633524982a399d4439_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:efb27a2f36ddb34ee220b07fdfb869c1fbe891c4954eb29d85900f6395e1bfe9 +size 66473 diff --git a/marked/Rel-18/38_series/38869/7518a1d0ad9e40b0a3e476e85693f23a_img.jpg b/marked/Rel-18/38_series/38869/7518a1d0ad9e40b0a3e476e85693f23a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b423bff0b3ff24d05e90737cd86eb646c4202c8a --- /dev/null +++ b/marked/Rel-18/38_series/38869/7518a1d0ad9e40b0a3e476e85693f23a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:938016c8c60262abf61184843fbd05358eb0d18408f330a9a091d55e3c3563c8 +size 82622 diff --git a/marked/Rel-18/38_series/38869/757a306a97d3f49cdd35ed06d9610d3e_img.jpg b/marked/Rel-18/38_series/38869/757a306a97d3f49cdd35ed06d9610d3e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d291f498c7b7c0e35cd6a99270528ba4e7bd117 --- /dev/null +++ b/marked/Rel-18/38_series/38869/757a306a97d3f49cdd35ed06d9610d3e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:12f6de4a5c19ded47a98cc63a2a4ea7c89e60bfa0f5afbe9e285721d34c2a899 +size 197401 diff --git a/marked/Rel-18/38_series/38869/75b9cb95f5815d6f3bbe57020a049504_img.jpg b/marked/Rel-18/38_series/38869/75b9cb95f5815d6f3bbe57020a049504_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5997a18a7bd707a1dad0f349e47dce3680abeaff --- /dev/null +++ b/marked/Rel-18/38_series/38869/75b9cb95f5815d6f3bbe57020a049504_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:698bb1db35ee5b982dc4582b91e1f4f0c0ff19c0f4d62f9474351d38e86ab024 +size 54689 diff --git a/marked/Rel-18/38_series/38869/771c18f874d31c59c3b8c4e247be16ca_img.jpg b/marked/Rel-18/38_series/38869/771c18f874d31c59c3b8c4e247be16ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a5beb97fc73080c368f834acd0a121c6dcc87169 --- /dev/null +++ b/marked/Rel-18/38_series/38869/771c18f874d31c59c3b8c4e247be16ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a3c1d903f91ed65df9adc77e2720b1a9dfc52fea8768bc905cbbc1f0fd09fd2 +size 66745 diff --git a/marked/Rel-18/38_series/38869/78de09c382ab51b5c3e87979204228c8_img.jpg b/marked/Rel-18/38_series/38869/78de09c382ab51b5c3e87979204228c8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e96bc7367d9a1a4d6d72b55b4a426cd426672a41 --- /dev/null +++ b/marked/Rel-18/38_series/38869/78de09c382ab51b5c3e87979204228c8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:81551d0eb8db26ba988098cdd952b160ac6ea8b7bf7a1ba06464ce5ec0c88245 +size 36644 diff --git a/marked/Rel-18/38_series/38869/79cb7fa0e9c78ec5cd0b0de977824f8d_img.jpg b/marked/Rel-18/38_series/38869/79cb7fa0e9c78ec5cd0b0de977824f8d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8edd08408769cef243309cfa67568bc2e54c41fc --- /dev/null +++ b/marked/Rel-18/38_series/38869/79cb7fa0e9c78ec5cd0b0de977824f8d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9709b6ae85b7322524c6f123a34a41ea14722c1e7762358af7a4838cd34f3cee +size 7982 diff --git a/marked/Rel-18/38_series/38869/7a0777bbad359aeb869022b345b827ef_img.jpg b/marked/Rel-18/38_series/38869/7a0777bbad359aeb869022b345b827ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc4b6b79e5105d07f2a38509ffefb582d4ef7527 --- /dev/null +++ b/marked/Rel-18/38_series/38869/7a0777bbad359aeb869022b345b827ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ffc481bd3d5ee1d378079fb96aaaddcdb6545af7c60f4568bdc0f6d4409f0fd +size 30461 diff --git a/marked/Rel-18/38_series/38869/7cf394a7ad158bf3aa4f8d58e7d4ebc5_img.jpg b/marked/Rel-18/38_series/38869/7cf394a7ad158bf3aa4f8d58e7d4ebc5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d667406143c352685970d44848d925cf8d5d26ae --- /dev/null +++ b/marked/Rel-18/38_series/38869/7cf394a7ad158bf3aa4f8d58e7d4ebc5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6bc25bd45cd1e24645db4d148515e46292d106cda62b7a7455a596c316e3a2a7 +size 73787 diff --git a/marked/Rel-18/38_series/38869/82b40cb8b2a5ac361973859400fa128a_img.jpg b/marked/Rel-18/38_series/38869/82b40cb8b2a5ac361973859400fa128a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22b72ce5d12de2986d1545ad82526119c2418951 --- /dev/null +++ b/marked/Rel-18/38_series/38869/82b40cb8b2a5ac361973859400fa128a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5ae183d9fe249df61bd1b6ff255ae4a6092c580b319d96763e4b7366e4846b4 +size 17650 diff --git a/marked/Rel-18/38_series/38869/843c1635ec8d9d05abf22214cb262fb4_img.jpg b/marked/Rel-18/38_series/38869/843c1635ec8d9d05abf22214cb262fb4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0275433cc705cc520bd3e1b140b4853aa2840121 --- /dev/null +++ b/marked/Rel-18/38_series/38869/843c1635ec8d9d05abf22214cb262fb4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ac254bf88fb56dc1d26677371fe1e27c39e878b207ee9521bc6b9cb9b5e2ed9 +size 105791 diff --git a/marked/Rel-18/38_series/38869/8c6dab3f9214d3a8d26736830d364527_img.jpg b/marked/Rel-18/38_series/38869/8c6dab3f9214d3a8d26736830d364527_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e1b13b916e1a975cc05c381e515676e145a1623 --- /dev/null +++ b/marked/Rel-18/38_series/38869/8c6dab3f9214d3a8d26736830d364527_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d7828023ec6b806361f81d95468330a47e65306f6f54d578b00608e4d374368 +size 96100 diff --git a/marked/Rel-18/38_series/38869/8c9229031a956b18d984fe72daa442c8_img.jpg b/marked/Rel-18/38_series/38869/8c9229031a956b18d984fe72daa442c8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..188a3316cd5f566d9cb394a6447b239cc92f3fcc --- /dev/null +++ b/marked/Rel-18/38_series/38869/8c9229031a956b18d984fe72daa442c8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f7fc07bb2bbadf135d8aac5347d499ccf1c02047ec97aba9e5dfeb584cebb5b +size 54334 diff --git a/marked/Rel-18/38_series/38869/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg b/marked/Rel-18/38_series/38869/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9341059be6831de50905700bbaf9ae7455eefe29 --- /dev/null +++ b/marked/Rel-18/38_series/38869/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a8c22fa6f8985514d3f13358f0d3c87b49dab0eed2ddcaaea89733b33c96f7c9 +size 23583 diff --git a/marked/Rel-18/38_series/38869/8e6f0b87d128da8e5d79d274d0c14ed5_img.jpg b/marked/Rel-18/38_series/38869/8e6f0b87d128da8e5d79d274d0c14ed5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da175ca58c54740b1009f4c92bdb0a69d18b1a64 --- /dev/null +++ b/marked/Rel-18/38_series/38869/8e6f0b87d128da8e5d79d274d0c14ed5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f34b58ac474a803649dd7e6219ea8c4f187454a40519e50345f6ce461c222a7 +size 59209 diff --git a/marked/Rel-18/38_series/38869/8e73cd115c6601092abc41abdf7d6772_img.jpg b/marked/Rel-18/38_series/38869/8e73cd115c6601092abc41abdf7d6772_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..629627bc1b8828358de3abf8c87384263679e263 --- /dev/null +++ b/marked/Rel-18/38_series/38869/8e73cd115c6601092abc41abdf7d6772_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d9db8246bbdc43b8c00f0133722886eda05468facf5298107ce716901c3df137 +size 112008 diff --git a/marked/Rel-18/38_series/38869/8e80de0cac529b2c3775d677c5203133_img.jpg b/marked/Rel-18/38_series/38869/8e80de0cac529b2c3775d677c5203133_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..115479920cc4bb99ba7082a3ba14636cdda94c4a --- /dev/null +++ b/marked/Rel-18/38_series/38869/8e80de0cac529b2c3775d677c5203133_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:87a6488106ca9fce8c1d63b475bb6d6a3bee87047cc773cd0a5bb3267019b9dd +size 45153 diff --git a/marked/Rel-18/38_series/38869/95520f6525ad4eba23a46d9cbb178902_img.jpg b/marked/Rel-18/38_series/38869/95520f6525ad4eba23a46d9cbb178902_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1072239df3612ddbf18f6828fe6f84dbc57c219a --- /dev/null +++ b/marked/Rel-18/38_series/38869/95520f6525ad4eba23a46d9cbb178902_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ff9f75e33ccad8df9660a8c307fc7f7e405888b2d06763f14c7f25bdbcac6c3a +size 25333 diff --git a/marked/Rel-18/38_series/38869/97044adf6c74dba676df34647a122614_img.jpg b/marked/Rel-18/38_series/38869/97044adf6c74dba676df34647a122614_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bb5a874a69b4cbb2d00b8e69cd82b8161e21c66e --- /dev/null +++ b/marked/Rel-18/38_series/38869/97044adf6c74dba676df34647a122614_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e7ca9dff552c76ed68b92465f0f0708e179c8c54b1a231bd54a543890659e16 +size 118099 diff --git a/marked/Rel-18/38_series/38869/98b62930d76058dbb3945fc335f36330_img.jpg b/marked/Rel-18/38_series/38869/98b62930d76058dbb3945fc335f36330_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..86f51a9e95608fe0eab7d5f0d02c891723767f27 --- /dev/null +++ b/marked/Rel-18/38_series/38869/98b62930d76058dbb3945fc335f36330_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:112fc4c4972e6657405d661ebb63dd423e84c8ecb73e808fa5acd0dec0c669e9 +size 144118 diff --git a/marked/Rel-18/38_series/38869/98ea5e21d919b389f3ce8b17ef4e65f6_img.jpg b/marked/Rel-18/38_series/38869/98ea5e21d919b389f3ce8b17ef4e65f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df7aeff03a14c282cad0360c118cfaed655ae22d --- /dev/null +++ b/marked/Rel-18/38_series/38869/98ea5e21d919b389f3ce8b17ef4e65f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eba6d6a516df79ca848fec41547b517b8cb6ecf3ef690ca947e384a317fafc33 +size 27790 diff --git a/marked/Rel-18/38_series/38869/991d185f7e22b857cf895c5486d0886d_img.jpg b/marked/Rel-18/38_series/38869/991d185f7e22b857cf895c5486d0886d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..477f3e4aaca4d51e8f1b552e0df97655e4e03a96 --- /dev/null +++ b/marked/Rel-18/38_series/38869/991d185f7e22b857cf895c5486d0886d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd311e58667e2f22616141e24928704b27a1e550a9a8c77d86be29516604bfde +size 156969 diff --git a/marked/Rel-18/38_series/38869/9c888dd6588358989047de6ced8b2bdb_img.jpg b/marked/Rel-18/38_series/38869/9c888dd6588358989047de6ced8b2bdb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d0bc2e51b6e9c7d7dcf010882b80fd0fb42251e3 --- /dev/null +++ b/marked/Rel-18/38_series/38869/9c888dd6588358989047de6ced8b2bdb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b0d51df3b831df75547834d4b14e5fe8292a9f728eb001f74b68b9667883370b +size 28233 diff --git a/marked/Rel-18/38_series/38869/9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg b/marked/Rel-18/38_series/38869/9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f23a977887bfa0c4d7f5081b8e09a3464889ba3 --- /dev/null +++ b/marked/Rel-18/38_series/38869/9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b4b399523d5c896f9d7238199a8641f51743580daace1d49256f1f85fcd3cfda +size 16698 diff --git a/marked/Rel-18/38_series/38869/9f92854fe6ecaf47760515c891a4fccc_img.jpg b/marked/Rel-18/38_series/38869/9f92854fe6ecaf47760515c891a4fccc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3cf84c910c370fdce4cdd7ece56250a2b7286290 --- /dev/null +++ b/marked/Rel-18/38_series/38869/9f92854fe6ecaf47760515c891a4fccc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af7aed0e158cc961febe2c0aadff23ff7003fce101c8dcae26debe0c1e24ef0c +size 49875 diff --git a/marked/Rel-18/38_series/38869/a03f88e0ac174f2614e86f19e75f7b1d_img.jpg b/marked/Rel-18/38_series/38869/a03f88e0ac174f2614e86f19e75f7b1d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..02c0f4d8e95b337ed252b32e1f352fa62af2f091 --- /dev/null +++ b/marked/Rel-18/38_series/38869/a03f88e0ac174f2614e86f19e75f7b1d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b197ee25fe965e4bb678ba956b0d6689c2b069b5ee193c2a78abd8daecffa7f +size 25298 diff --git a/marked/Rel-18/38_series/38869/a0ef559f2bd4147ec203cff042d7369a_img.jpg b/marked/Rel-18/38_series/38869/a0ef559f2bd4147ec203cff042d7369a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..983d8cd7b3378fc5ce4ef150443caf92d6f681cf --- /dev/null +++ b/marked/Rel-18/38_series/38869/a0ef559f2bd4147ec203cff042d7369a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fbef95fe336a8d35c94075d8759b30eaf7f4f8d9ed676869bb3c674a3f3371d0 +size 88518 diff --git a/marked/Rel-18/38_series/38869/a175bdeacb50b8a60869f6c68c5d0a07_img.jpg b/marked/Rel-18/38_series/38869/a175bdeacb50b8a60869f6c68c5d0a07_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d9b60b9349775905bc2a08c5b21b3bd08817e58 --- /dev/null +++ b/marked/Rel-18/38_series/38869/a175bdeacb50b8a60869f6c68c5d0a07_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:acd54ed1a605045c52f10edd8d05be376186628b915bfdda745058e0ca25fab3 +size 39079 diff --git a/marked/Rel-18/38_series/38869/a27134bc3a3c899782febdd02b502240_img.jpg b/marked/Rel-18/38_series/38869/a27134bc3a3c899782febdd02b502240_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60848372e48133316f4405324e324b3c11acf6ed --- /dev/null +++ b/marked/Rel-18/38_series/38869/a27134bc3a3c899782febdd02b502240_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c6becdbe73898c15a8621823e9b8dd8fd9cbfb7ee5189f5af86fa7fcb020139e +size 26699 diff --git a/marked/Rel-18/38_series/38869/a68a23db77099456e2f763fce520c087_img.jpg b/marked/Rel-18/38_series/38869/a68a23db77099456e2f763fce520c087_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..330d47db2df917da6e9725e87aea695cd0552e14 --- /dev/null +++ b/marked/Rel-18/38_series/38869/a68a23db77099456e2f763fce520c087_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b3e41bb14427f3446fc5a25a2e4bda45b3d60f5848d8a4e359c881a7c5327b1 +size 44300 diff --git a/marked/Rel-18/38_series/38869/a756b11a82d229c04c8c5d78f40ff16d_img.jpg b/marked/Rel-18/38_series/38869/a756b11a82d229c04c8c5d78f40ff16d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7eb5179266476dae0e7aaaaa3000b5c51bb68db8 --- /dev/null +++ b/marked/Rel-18/38_series/38869/a756b11a82d229c04c8c5d78f40ff16d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5838e0589d5d88db91702a17f120db2a2bebda33d97bd6fc1f2bf0136a8fa78d +size 115383 diff --git a/marked/Rel-18/38_series/38869/a75c2cd397490e8a9b0fa811a6a1b2c3_img.jpg b/marked/Rel-18/38_series/38869/a75c2cd397490e8a9b0fa811a6a1b2c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a3e1dbcef5f9fad801549cf8f1a15e9dc0bda217 --- /dev/null +++ b/marked/Rel-18/38_series/38869/a75c2cd397490e8a9b0fa811a6a1b2c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e344df2260456a6fd23a6d747bcb16a0fcead80f531f7c7fb93788dd03540e2d +size 111990 diff --git a/marked/Rel-18/38_series/38869/ada2aa7cce9cff9cf116d9ae2b8b7c27_img.jpg b/marked/Rel-18/38_series/38869/ada2aa7cce9cff9cf116d9ae2b8b7c27_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb4b314d685f3ab3e30899e8971b9a05ab020700 --- /dev/null +++ b/marked/Rel-18/38_series/38869/ada2aa7cce9cff9cf116d9ae2b8b7c27_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1743c05b0411b937e378588cbaaf071ad858eb03c14d6b711815b90dac444151 +size 33248 diff --git a/marked/Rel-18/38_series/38869/b1c27d955a3589957e99cc4f284ddcb1_img.jpg b/marked/Rel-18/38_series/38869/b1c27d955a3589957e99cc4f284ddcb1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb872c45ee29b86d0719f710a43ab674db46daa4 --- /dev/null +++ b/marked/Rel-18/38_series/38869/b1c27d955a3589957e99cc4f284ddcb1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:41f7e5c569d05503e06810a6c066b93321af4107beb9f702f21a1df3cb60c58a +size 141955 diff --git a/marked/Rel-18/38_series/38869/b4936c448378a2bf419ef27695a798ae_img.jpg b/marked/Rel-18/38_series/38869/b4936c448378a2bf419ef27695a798ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2aaf7b60f1507a13462b4ea42b56a9d5f231ea66 --- /dev/null +++ b/marked/Rel-18/38_series/38869/b4936c448378a2bf419ef27695a798ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a74d52b1d81454281645d0e898fe22f4ddfc29584840a210dadadebc63bc85c5 +size 101868 diff --git a/marked/Rel-18/38_series/38869/b9eb2f58f854a342d2452f842630a06a_img.jpg b/marked/Rel-18/38_series/38869/b9eb2f58f854a342d2452f842630a06a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b0430ed1085c97177fb21fb684ee23d1290133c5 --- /dev/null +++ b/marked/Rel-18/38_series/38869/b9eb2f58f854a342d2452f842630a06a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8bbef2664d74486d2e052b1dd6e1d3f255d7037d537821c894d3fe75c7923f73 +size 127149 diff --git a/marked/Rel-18/38_series/38869/ba101937c4401ed203088650cb91db1c_img.jpg b/marked/Rel-18/38_series/38869/ba101937c4401ed203088650cb91db1c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9dcc437588c0cb06ef93bd2511fd0eb4d5d414a2 --- /dev/null +++ b/marked/Rel-18/38_series/38869/ba101937c4401ed203088650cb91db1c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dc049c622539f8385ccc82e2c20cd06c26eeda2f26748c481d5e3f175566e8b7 +size 158187 diff --git a/marked/Rel-18/38_series/38869/bbce254e33d654e2077bd1e3e9beae8a_img.jpg b/marked/Rel-18/38_series/38869/bbce254e33d654e2077bd1e3e9beae8a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..afa6e0b8c3fe2f9528b22b266a15cc27a4eadf44 --- /dev/null +++ b/marked/Rel-18/38_series/38869/bbce254e33d654e2077bd1e3e9beae8a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce763210d85b1bc3ae5d1021ac20ace802c9293fb0df4457675e96bd94d9269d +size 25762 diff --git a/marked/Rel-18/38_series/38869/bc3afa6786f4e6e882edded4b64a3ed0_img.jpg b/marked/Rel-18/38_series/38869/bc3afa6786f4e6e882edded4b64a3ed0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..049eb8aa2be29877908b643dcbb3baeb6e187635 --- /dev/null +++ b/marked/Rel-18/38_series/38869/bc3afa6786f4e6e882edded4b64a3ed0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e28f4c95a1aa2833362f70702acab4a378e274a0498b7d9bb5678aca02b1cb4f +size 128829 diff --git a/marked/Rel-18/38_series/38869/bc9fe6d1f3411f724ddf3b8c11a37f7e_img.jpg b/marked/Rel-18/38_series/38869/bc9fe6d1f3411f724ddf3b8c11a37f7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2391367ba726e5739e279af546b89c2ef886013d --- /dev/null +++ b/marked/Rel-18/38_series/38869/bc9fe6d1f3411f724ddf3b8c11a37f7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d836c3917d6a39f3b0c29050b1ad8d2a5692704f52aa9213b5950415b2556e2d +size 79334 diff --git a/marked/Rel-18/38_series/38869/bdcc4eb452fcc6ba091949b77546a6d4_img.jpg b/marked/Rel-18/38_series/38869/bdcc4eb452fcc6ba091949b77546a6d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..470abb7ab6888eaba8b0b1db35e6bef589575aca --- /dev/null +++ b/marked/Rel-18/38_series/38869/bdcc4eb452fcc6ba091949b77546a6d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf686ffdb0f51f71088d629e0d73e0e4f0754b2d264a481d769fb809db49548a +size 26561 diff --git a/marked/Rel-18/38_series/38869/be2d9105109f6a87907ab68cb88548d9_img.jpg b/marked/Rel-18/38_series/38869/be2d9105109f6a87907ab68cb88548d9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c755385a443a72962fae1a907a1e1f0e233f4bea --- /dev/null +++ b/marked/Rel-18/38_series/38869/be2d9105109f6a87907ab68cb88548d9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8e50ef0d785127e6669184f19b0759f77fa1bf2e8e89302b8ea43c1cb234fc6 +size 85404 diff --git a/marked/Rel-18/38_series/38869/be340a80845e55d744bd90a4f2c0dd67_img.jpg b/marked/Rel-18/38_series/38869/be340a80845e55d744bd90a4f2c0dd67_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b5b395cff01d4afe32ae13b3d44268833ae3b6d6 --- /dev/null +++ b/marked/Rel-18/38_series/38869/be340a80845e55d744bd90a4f2c0dd67_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a0d7a489d9902dd0a94b8b8be1051a45a81219809848826d2f7afc32042e462 +size 92901 diff --git a/marked/Rel-18/38_series/38869/bec54a43401eceb0270c022d21e71a3e_img.jpg b/marked/Rel-18/38_series/38869/bec54a43401eceb0270c022d21e71a3e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f081759725303da52a923bdc054a342a61d6cf26 --- /dev/null +++ b/marked/Rel-18/38_series/38869/bec54a43401eceb0270c022d21e71a3e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aaffe572aa729aada61f36e41c8c7889238da10e4ab61382844d2caef2e998f2 +size 110380 diff --git a/marked/Rel-18/38_series/38869/c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg b/marked/Rel-18/38_series/38869/c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..081864e83fbc08997c65233d531c12c2879ee0f2 --- /dev/null +++ b/marked/Rel-18/38_series/38869/c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0aa36097ef585da35d4708801a93420f15bf21aa0348459390ac5d0b5df0959d +size 136935 diff --git a/marked/Rel-18/38_series/38869/c725c5cdd568eb2ba1793def3680b20e_img.jpg b/marked/Rel-18/38_series/38869/c725c5cdd568eb2ba1793def3680b20e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bdde6ce943f01f24508de03b9982fda1b268982e --- /dev/null +++ b/marked/Rel-18/38_series/38869/c725c5cdd568eb2ba1793def3680b20e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f46fe24232608093fbd380ce878f15e2ca4292c2699e42365b0294230725857 +size 120450 diff --git a/marked/Rel-18/38_series/38869/c9c3809709886a056c616a3aaece0c6d_img.jpg b/marked/Rel-18/38_series/38869/c9c3809709886a056c616a3aaece0c6d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a5f4dec93ffa51cc392c0aafe440ba5cd8160ec5 --- /dev/null +++ b/marked/Rel-18/38_series/38869/c9c3809709886a056c616a3aaece0c6d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d05e46b94fcae24b8ef0358adb261797b603dfdfe8bde403f56b238fb6d7c8ab +size 27470 diff --git a/marked/Rel-18/38_series/38869/cbb007765df371cbaa0dfd8596fce353_img.jpg b/marked/Rel-18/38_series/38869/cbb007765df371cbaa0dfd8596fce353_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15866508cf43806e5ede4531eba6259f2aeaeefb --- /dev/null +++ b/marked/Rel-18/38_series/38869/cbb007765df371cbaa0dfd8596fce353_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ecf05e185a30ec38a2e0042c77af9307f1649fa99d97c721b0a318a16ceadf2 +size 51734 diff --git a/marked/Rel-18/38_series/38869/cc4a284d42136d1539eb2e13a68cbc50_img.jpg b/marked/Rel-18/38_series/38869/cc4a284d42136d1539eb2e13a68cbc50_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb1fd94f93a4558c8b34fec18eab2d020d69abf0 --- /dev/null +++ b/marked/Rel-18/38_series/38869/cc4a284d42136d1539eb2e13a68cbc50_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:426e7671312b9fc69acc5d3c8f14d863aa8ee81b8a4ca3c5944c7eec577f9d5c +size 103694 diff --git a/marked/Rel-18/38_series/38869/ce951c49dba8deb9a7fda642899b99a4_img.jpg b/marked/Rel-18/38_series/38869/ce951c49dba8deb9a7fda642899b99a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bcdca6a9273ee44e98d12ac43042737af2ac53ff --- /dev/null +++ b/marked/Rel-18/38_series/38869/ce951c49dba8deb9a7fda642899b99a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d03a15acbd3ad0aee0fb4345b0f30369a43eb8a6818dc62b83462e46ad64b81b +size 83313 diff --git a/marked/Rel-18/38_series/38869/ce9ded033e82bd248b3a2a57305d6767_img.jpg b/marked/Rel-18/38_series/38869/ce9ded033e82bd248b3a2a57305d6767_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e17ef065f2e8a765b5099a1602d3521275ade1b0 --- /dev/null +++ b/marked/Rel-18/38_series/38869/ce9ded033e82bd248b3a2a57305d6767_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dace51706a4113c8b9144abf5763b55f47007a580ac756b47177c80df11fb295 +size 121359 diff --git a/marked/Rel-18/38_series/38869/d0b8566e8744891c3f8a7f1359aa4214_img.jpg b/marked/Rel-18/38_series/38869/d0b8566e8744891c3f8a7f1359aa4214_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..80eca60aec916e36c37e8de72b1ca96973acd0fa --- /dev/null +++ b/marked/Rel-18/38_series/38869/d0b8566e8744891c3f8a7f1359aa4214_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:46ea6688212ecce47fdf0f71d23d93d575e428fbf58f47011f3f4956b2eb2f6a +size 91561 diff --git a/marked/Rel-18/38_series/38869/d4852169b63bedb68b1f3c5b3b9b0cc0_img.jpg b/marked/Rel-18/38_series/38869/d4852169b63bedb68b1f3c5b3b9b0cc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dbc355db7b84bb7b72ccc5f757490267e70c9528 --- /dev/null +++ b/marked/Rel-18/38_series/38869/d4852169b63bedb68b1f3c5b3b9b0cc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6efbb36a4a4f3f85ebd5dfda65acc4f86c55d176da67a55ec6dbeb77e32d5637 +size 51326 diff --git a/marked/Rel-18/38_series/38869/d58ddc0c76684eabc4244486807245fe_img.jpg b/marked/Rel-18/38_series/38869/d58ddc0c76684eabc4244486807245fe_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..83de1ab8d641f78210eaf01c827dea35e307ddc7 --- /dev/null +++ b/marked/Rel-18/38_series/38869/d58ddc0c76684eabc4244486807245fe_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d19e6ee05673757a3cab3fc40a4715f883c127ec31199178de35387804e5f0bb +size 115642 diff --git a/marked/Rel-18/38_series/38869/d6e773bd03b27399c513d3958f1c87d6_img.jpg b/marked/Rel-18/38_series/38869/d6e773bd03b27399c513d3958f1c87d6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dfec44f8ea983223a9577df0026220453405845e --- /dev/null +++ b/marked/Rel-18/38_series/38869/d6e773bd03b27399c513d3958f1c87d6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d627d13a9201bb65f96a7634ca31faeffe09d99e577d43dc530d6b55943783b +size 58264 diff --git a/marked/Rel-18/38_series/38869/d7efe1d3c9fce95c7bacefb7e7d7faff_img.jpg b/marked/Rel-18/38_series/38869/d7efe1d3c9fce95c7bacefb7e7d7faff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..716fbb28f6f4890e735483d91481d3c0afe15f3c --- /dev/null +++ b/marked/Rel-18/38_series/38869/d7efe1d3c9fce95c7bacefb7e7d7faff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:507334060781f570683d53e523ebb8e009e1fe77e93a116cbc06df8247254b66 +size 21639 diff --git a/marked/Rel-18/38_series/38869/da0d310d0e9ecc6bfd61fe15aad963aa_img.jpg b/marked/Rel-18/38_series/38869/da0d310d0e9ecc6bfd61fe15aad963aa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a10a927f386b87b154c9c88c467c5cb476d3212e --- /dev/null +++ b/marked/Rel-18/38_series/38869/da0d310d0e9ecc6bfd61fe15aad963aa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe3502b774314cc6700bf4934c39cf108acb3e93c580186440b37d06f9289f2e +size 27595 diff --git a/marked/Rel-18/38_series/38869/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg b/marked/Rel-18/38_series/38869/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e5721c93530326c0a8b271caa64b05b5729bb70 --- /dev/null +++ b/marked/Rel-18/38_series/38869/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:13421a59fe267d6c5b09565415f41388d26441457583a772e88ce3e2f05e0b6c +size 39544 diff --git a/marked/Rel-18/38_series/38869/dd7579e21d9f956489a04e28c9d8abc0_img.jpg b/marked/Rel-18/38_series/38869/dd7579e21d9f956489a04e28c9d8abc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..23c2043eb196ff899b81183eed010fe961bd99f7 --- /dev/null +++ b/marked/Rel-18/38_series/38869/dd7579e21d9f956489a04e28c9d8abc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:54faa857786f5c17b729a0d6b9b45a1f147f211539bcb07edb11b9243a36168c +size 25746 diff --git a/marked/Rel-18/38_series/38869/ddfefccc6c2fcfadf4e398109548faf8_img.jpg b/marked/Rel-18/38_series/38869/ddfefccc6c2fcfadf4e398109548faf8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c41603c61b3c8d1609d64a8ced51390d3e91423e --- /dev/null +++ b/marked/Rel-18/38_series/38869/ddfefccc6c2fcfadf4e398109548faf8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b28795b56a71cbecfd4fa199851df2d0251335a378298d7ec8005951cc1c26dd +size 27630 diff --git a/marked/Rel-18/38_series/38869/df942da5e715e03b194b733d9f5998ad_img.jpg b/marked/Rel-18/38_series/38869/df942da5e715e03b194b733d9f5998ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5afd7e5d58445826c9d8f50ea676bd5f7c19acc1 --- /dev/null +++ b/marked/Rel-18/38_series/38869/df942da5e715e03b194b733d9f5998ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de489637924a41d1b69a8c9dbade2c40706a04e71c02c180c00ac6225b6157a0 +size 110443 diff --git a/marked/Rel-18/38_series/38869/dfb5a77d296b5c152ba6033adef76a80_img.jpg b/marked/Rel-18/38_series/38869/dfb5a77d296b5c152ba6033adef76a80_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b5830c0765c3642d3697d4508957249314c8b0a2 --- /dev/null +++ b/marked/Rel-18/38_series/38869/dfb5a77d296b5c152ba6033adef76a80_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19f6612aee3a3d97baf79b37d3283fd23e72008f2568332c143373fb9d8db81e +size 86338 diff --git a/marked/Rel-18/38_series/38869/e0113695dbf148bf5ec34354e544414b_img.jpg b/marked/Rel-18/38_series/38869/e0113695dbf148bf5ec34354e544414b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..27bd3e6e6f64d080b80708b96d3e22b3286b4a2d --- /dev/null +++ b/marked/Rel-18/38_series/38869/e0113695dbf148bf5ec34354e544414b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1cbd12ee05a407795852617c5ec48ccc4f5cbe80802938acb3f0807f095e0bc2 +size 46726 diff --git a/marked/Rel-18/38_series/38869/e0f4d30e14bac25c9a4d673acf4e22e9_img.jpg b/marked/Rel-18/38_series/38869/e0f4d30e14bac25c9a4d673acf4e22e9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0bc948ac3a4dc64ac8692cd76fcf22c364c25557 --- /dev/null +++ b/marked/Rel-18/38_series/38869/e0f4d30e14bac25c9a4d673acf4e22e9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9cae8ef667be219db4198d424daecdc9dbca1d95359c4aa69fc835c090c9218 +size 58317 diff --git a/marked/Rel-18/38_series/38869/e29665b8abcea967ef289c6aff07ae4c_img.jpg b/marked/Rel-18/38_series/38869/e29665b8abcea967ef289c6aff07ae4c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4d41fc3a2c3ff90300a479b19727a68f6f76216 --- /dev/null +++ b/marked/Rel-18/38_series/38869/e29665b8abcea967ef289c6aff07ae4c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f22259ae62b0d3df001583cb9d7c25cc47d2c75bdb9cc3dee851db5a8644decf +size 17744 diff --git a/marked/Rel-18/38_series/38869/e2ddd0f0705e7e69df4ffa6380e1b1ed_img.jpg b/marked/Rel-18/38_series/38869/e2ddd0f0705e7e69df4ffa6380e1b1ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67ba44acdee50466f45c51a6914029953582fd2e --- /dev/null +++ b/marked/Rel-18/38_series/38869/e2ddd0f0705e7e69df4ffa6380e1b1ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:577e445d75580530b9747e73f1c2b960eaedad37032aecb0cf9f7dc174ee7666 +size 70039 diff --git a/marked/Rel-18/38_series/38869/e416935e4c3e0c070050bb3ae2465074_img.jpg b/marked/Rel-18/38_series/38869/e416935e4c3e0c070050bb3ae2465074_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ffd2c2adc1e9183049e5c220c0837b9ad650443 --- /dev/null +++ b/marked/Rel-18/38_series/38869/e416935e4c3e0c070050bb3ae2465074_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75136f39a1bbc97643540f6850d7231aa3e7605df32cb794930b2ccb290c44f9 +size 128725 diff --git a/marked/Rel-18/38_series/38869/e6d17113d3c65cc31531ae8a73fe011f_img.jpg b/marked/Rel-18/38_series/38869/e6d17113d3c65cc31531ae8a73fe011f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b87d7e796660f2880357775d4e1d4834006396f2 --- /dev/null +++ b/marked/Rel-18/38_series/38869/e6d17113d3c65cc31531ae8a73fe011f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:86e5f71789be5b5364a05e37bd2172bd6cee170007c5fa8e5f87a6580eeb1475 +size 44521 diff --git a/marked/Rel-18/38_series/38869/e7010c66da16316c2935dfbbef5056b3_img.jpg b/marked/Rel-18/38_series/38869/e7010c66da16316c2935dfbbef5056b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..54db2bbbeedbf35e9c6e0e3e5fc71c3b648d9251 --- /dev/null +++ b/marked/Rel-18/38_series/38869/e7010c66da16316c2935dfbbef5056b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:89513c0773967128ddb58edbe16131d29b4c2eaeddedd5cfc30e6292f033e469 +size 27674 diff --git a/marked/Rel-18/38_series/38869/e84de38c2eac283d770e2c8acdf64308_img.jpg b/marked/Rel-18/38_series/38869/e84de38c2eac283d770e2c8acdf64308_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6dc3c3b465a32f9f1705be19dc3a68ac5bae2488 --- /dev/null +++ b/marked/Rel-18/38_series/38869/e84de38c2eac283d770e2c8acdf64308_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:17b4aad051b7560568b3902b18ff348db5d2a50f071bd9275deed3468006149c +size 69180 diff --git a/marked/Rel-18/38_series/38869/e94343421418a4f626e885ec73be542d_img.jpg b/marked/Rel-18/38_series/38869/e94343421418a4f626e885ec73be542d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5fcdb6658979f4661aaf6881c16920f673fffe84 --- /dev/null +++ b/marked/Rel-18/38_series/38869/e94343421418a4f626e885ec73be542d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:71f9398391623e3b66eb18a858103e7a71f16c3133eb028d78a404f8eb72fab8 +size 92059 diff --git a/marked/Rel-18/38_series/38869/ed2c3e8ce1a7479b617b38a843c6b782_img.jpg b/marked/Rel-18/38_series/38869/ed2c3e8ce1a7479b617b38a843c6b782_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0216263e81e7bc63012d10a3a6b7fa2d68bef61d --- /dev/null +++ b/marked/Rel-18/38_series/38869/ed2c3e8ce1a7479b617b38a843c6b782_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c7892dbbd77fccde6681587a2de7e6fa80238190f90e895db486c3195b559519 +size 63497 diff --git a/marked/Rel-18/38_series/38869/f0633112a6de512a522905ccb5de7975_img.jpg b/marked/Rel-18/38_series/38869/f0633112a6de512a522905ccb5de7975_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..985f2fab874e5ea4d3eaa3d2a7fa6ed0cd21f3e6 --- /dev/null +++ b/marked/Rel-18/38_series/38869/f0633112a6de512a522905ccb5de7975_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe5ae055e11cf74c3e81093f03e3c250ffa132623c45ff4e4fa2f2cf3932810e +size 118363 diff --git a/marked/Rel-18/38_series/38869/f217ea7a6e9347a9ca4d6173ed57c33e_img.jpg b/marked/Rel-18/38_series/38869/f217ea7a6e9347a9ca4d6173ed57c33e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..06b27cb156319da5dbd96923e25cec01e45a18e3 --- /dev/null +++ b/marked/Rel-18/38_series/38869/f217ea7a6e9347a9ca4d6173ed57c33e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f6d38295569c28548848b02f2985d2fda746758d5955852e0f464b0730626bbf +size 232058 diff --git a/marked/Rel-18/38_series/38869/f2ea0f64a770b22b902820457d262265_img.jpg b/marked/Rel-18/38_series/38869/f2ea0f64a770b22b902820457d262265_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e850542a8d7ea78e9cd9dfa11ea9ab33672472cd --- /dev/null +++ b/marked/Rel-18/38_series/38869/f2ea0f64a770b22b902820457d262265_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cfa7fecc1de999129442a114d1d2d0ab5e8d5063457ca3fb02e2a974c12f0380 +size 28960 diff --git a/marked/Rel-18/38_series/38869/f8b22299fe23201d5b3fdece96436fca_img.jpg b/marked/Rel-18/38_series/38869/f8b22299fe23201d5b3fdece96436fca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..71904507be912ef47714087db077062a55802ae8 --- /dev/null +++ b/marked/Rel-18/38_series/38869/f8b22299fe23201d5b3fdece96436fca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e8e80ffe908457f09903218df7dcca962aaffd09d0c90cb3c04a3627e58b09eb +size 111147 diff --git a/marked/Rel-18/38_series/38869/f9625fa3465b009051f85d91cfa1da7e_img.jpg b/marked/Rel-18/38_series/38869/f9625fa3465b009051f85d91cfa1da7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d3782f5703cb4ba45e8547c03a0bc1468205ac25 --- /dev/null +++ b/marked/Rel-18/38_series/38869/f9625fa3465b009051f85d91cfa1da7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c187099b9df2cf00f3a7aee5ebcfcb9a16d1c6ea5ec677ae392b60b2889d9e5b +size 50572 diff --git a/marked/Rel-18/38_series/38869/fad415ab62a56119f4584c45e1d9a55c_img.jpg b/marked/Rel-18/38_series/38869/fad415ab62a56119f4584c45e1d9a55c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..83bbcb7e807829cd49001b0381cb77c7c3bbd5f7 --- /dev/null +++ b/marked/Rel-18/38_series/38869/fad415ab62a56119f4584c45e1d9a55c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6bd7b2e3347dd8550842c761f3a82f914ce2eaa919e7e0b826b74906d4638ae8 +size 101802 diff --git a/marked/Rel-18/38_series/38869/fbd0e6c1cf946b0609a26529c031ae7f_img.jpg b/marked/Rel-18/38_series/38869/fbd0e6c1cf946b0609a26529c031ae7f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5532e6cd7e6545c9edaa155bf3f63730b77ab5f --- /dev/null +++ b/marked/Rel-18/38_series/38869/fbd0e6c1cf946b0609a26529c031ae7f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83ff3d83c8fad04904129a00b2c18a319504ecb4ac463e8afd461c9c4f02d0ac +size 66804 diff --git a/marked/Rel-18/38_series/38869/fcbc3c31776721edc98ceb1944ec438f_img.jpg b/marked/Rel-18/38_series/38869/fcbc3c31776721edc98ceb1944ec438f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c1208d77ecefa70c3cbcda5c288ab7bfb1e981e --- /dev/null +++ b/marked/Rel-18/38_series/38869/fcbc3c31776721edc98ceb1944ec438f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:575b6e37a37d563bf0d9580a2aabb904c1a53fc7eff0b9355b4d9d20dd36b608 +size 51526 diff --git a/marked/Rel-18/38_series/38869/fe8840a79cf6b30f8b2284064f3d2a36_img.jpg b/marked/Rel-18/38_series/38869/fe8840a79cf6b30f8b2284064f3d2a36_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c8bb2d46d1e7866b64068fd6ec87ade554c2adc --- /dev/null +++ b/marked/Rel-18/38_series/38869/fe8840a79cf6b30f8b2284064f3d2a36_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a42c0f4c3b9c55d16b4da58a46483b9d1cdcec47760bd7852f4a5855caf3c55d +size 107646 diff --git a/marked/Rel-18/38_series/38869/raw.md b/marked/Rel-18/38_series/38869/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..bc2bbde568b12aec879f3257c970bb7807ea40e9 --- /dev/null +++ b/marked/Rel-18/38_series/38869/raw.md @@ -0,0 +1,9118 @@ + + +# 3GPP TR 38.869 V18.0.0 (2023-12) + +*Technical Report* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on low-power wake-up signal and receiver 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 letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, stylized font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' underneath. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 +16 + +--- + +Internet + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | | +|------------|---------------------------------------------------------------------|----| +| 1 | Scope..... | 10 | +| 2 | References..... | 10 | +| 3 | Definitions of terms, symbols and abbreviations..... | 12 | +| 3.1 | Terms..... | 12 | +| 3.2 | Symbols..... | 13 | +| 3.3 | Abbreviations..... | 13 | +| 4 | Introduction..... | 14 | +| 5 | Use cases & KPI..... | 15 | +| 6 | Evaluation methodology..... | 16 | +| 6.1 | General performance metrics..... | 16 | +| 6.2 | Evaluation assumptions..... | 17 | +| 6.2.1 | General evaluation assumptions..... | 17 | +| 6.2.2 | Coverage evaluation assumptions..... | 18 | +| 6.2.3 | Link performance evaluation assumptions..... | 20 | +| 6.3 | Power consumption model..... | 23 | +| 6.3.1 | Power model for Main Radio (MR)..... | 23 | +| 6.3.2 | Power model for LP-WUR (LR)..... | 24 | +| 7 | LP-WUR and LP-WUS design..... | 25 | +| 7.1 | LP-WUS receiver architectures..... | 25 | +| 7.1.1 | General description of receiver types..... | 25 | +| 7.1.1a | Analysis of LP-WUR architectures..... | 32 | +| 7.1.1a.1 | OOK-1/2/4..... | 33 | +| 7.1.1a.1.1 | RF envelope detection..... | 33 | +| 7.1.1a.1.2 | Heterodyne architecture with IF envelope detection..... | 33 | +| 7.1.1a.1.3 | Homodyne/zero-IF architecture with baseband envelope detection..... | 33 | +| 7.1.1a.2 | FSK..... | 34 | +| 7.1.1a.2.1 | Parallel RF envelope detection..... | 34 | +| 7.1.1a.2.2 | Parallel heterodyne architecture..... | 34 | +| 7.1.1a.2.3 | Parallel homodyne architecture..... | 34 | +| 7.1.1a.2.4 | Heterodyne architecture with frequency to amplitude conversion..... | 35 | +| 7.1.1a.2.5 | Homodyne architecture with frequency to amplitude conversion..... | 35 | +| 7.1.1a.3 | OFDMA-based signal..... | 35 | +| 7.1.1a.3.1 | Time-domain correlation (without FFT)..... | 35 | +| 7.1.1a.3.2 | Frequency-domain correlation (with FFT)..... | 35 | +| 7.1.2 | RAN4 studies of the receiver..... | 36 | +| 7.1.2.1 | General..... | 36 | +| 7.1.2.2 | ACS evaluation..... | 37 | +| 7.1.2.3 | ASCS evaluation..... | 56 | +| 7.1.2.4 | Phase noise..... | 66 | +| 7.1.2.5 | gNodeB RF impacts..... | 66 | +| 7.1.2.6 | Multi-band capability..... | 67 | +| 7.1.2.7 | Noise Figure..... | 67 | +| 7.1.2.8 | Band operation for LP-WUS..... | 67 | +| 7.2 | LP-WUS design and L1 procedure..... | 67 | +| 7.2.1 | Signal design..... | 68 | +| 7.2.1.1 | Waveform..... | 68 | +| 7.2.1.1.1 | MC-ASK waveform..... | 69 | +| 7.2.1.1.2 | FSK waveform..... | 71 | +| 7.2.1.1.3 | OFDM waveform..... | 71 | +| 7.2.1.2 | Bandwidth and location..... | 71 | +| 7.2.1.3 | LP-WUS content..... | 72 | +| 7.2.2 | L1 procedures..... | 73 | +| 7.2.2.1 | RRM measurements..... | 73 | +| 7.2.2.2 | Synchronization of LP-WUR..... | 74 | + +| | | | +|-----------|--------------------------------------------------------------------------------------|-----| +| 7.2.2.3 | LP-WUS monitoring..... | 75 | +| 7.2.2.4 | Activation/Deactivation procedures of LP-WUS..... | 75 | +| 7.2.2.5 | Coverage..... | 75 | +| 7.2.2.6 | Additional L1 procedures for RRC CONNECTED mode..... | 76 | +| 7.2.2.7 | Additional L1 procedures for RRC IDLE/INACTIVE modes..... | 77 | +| 7.2.2.8 | Others..... | 77 | +| 7.3 | Higher-layer aspects..... | 77 | +| 7.3.1 | RRC IDLE/INACTIVE mode..... | 77 | +| 7.3.1.1 | RRC IDLE/INACTIVE mode procedures..... | 77 | +| 7.3.1.2 | LP-WUS monitoring and wake up procedure..... | 77 | +| 7.3.1.3 | LP-WUS coverage and trigger condition..... | 79 | +| 7.3.1.4 | Configuration..... | 80 | +| 7.3.1.5 | System information update and PWS..... | 80 | +| 7.3.1.6 | Mobility and RRM..... | 80 | +| 7.3.2 | RRC CONNECTED mode..... | 81 | +| 7.3.2.1 | RRC CONNECTED mode procedures..... | 81 | +| 7.3.2.2 | LP-WUS monitoring..... | 81 | +| 7.3.2.3 | LP-WUS use options..... | 82 | +| 7.3.2.4 | Configuration..... | 85 | +| 7.3.2.5 | LP-WUS coexistence with DCP..... | 86 | +| 7.4 | RAN4 RRM study..... | 86 | +| 8 | Evaluation results..... | 87 | +| 8.1 | Power and latency evaluation..... | 87 | +| 8.1.1 | RRC IDLE/INACTIVE mode..... | 87 | +| 8.1.1.1 | Duty cycled LP-WUS..... | 87 | +| 8.1.1.1.1 | Collection of the results..... | 88 | +| 8.1.1.1.2 | Observations..... | 92 | +| 8.1.1.2 | Continuous monitoring results and results with duty cycle ratio = 50% LP-WUS..... | 94 | +| 8.1.1.2.1 | Collection of the results..... | 94 | +| 8.1.1.2.2 | Observations..... | 97 | +| 8.1.1.3 | Various LP-WUR relative power for duty-cycled monitoring..... | 99 | +| 8.1.1.3.1 | Collection of the results..... | 101 | +| 8.1.1.3.2 | Observations..... | 104 | +| 8.1.1.4 | Compared with eDRX..... | 106 | +| 8.1.1.4.1 | Collection of the results..... | 107 | +| 8.1.1.4.2 | Observations..... | 109 | +| 8.1.1.5 | RRM for LP-WUR duty-cycled monitoring..... | 110 | +| 8.1.1.5.1 | Collection of the results..... | 110 | +| 8.1.1.5.2 | Observations..... | 111 | +| 8.1.1.6 | RRM for LP-WUR continuously monitoring..... | 113 | +| 8.1.1.6.1 | Collection of the results..... | 113 | +| 8.1.1.6.2 | Observations..... | 114 | +| 8.1.1.7 | Impact by various MR sync/re-sync assumptions..... | 115 | +| 8.1.1.7.1 | Collection of the results..... | 115 | +| 8.1.1.7.2 | Observations..... | 117 | +| 8.1.1.8 | Impact by various MR ramp-up time/transition energy assumptions and sleep state..... | 118 | +| 8.1.1.8.1 | Collection of the results..... | 118 | +| 8.1.1.8.2 | Observations..... | 120 | +| 8.1.2 | RRC CONNECTED mode..... | 122 | +| 8.1.2.1 | XR traffic model..... | 122 | +| 8.1.2.1.1 | Collection of the results..... | 123 | +| 8.1.2.1.2 | Observations..... | 127 | +| 8.1.2.2 | FTP 3 and IM traffic model..... | 129 | +| 8.1.2.2.1 | Collection of the results..... | 130 | +| 8.1.2.2.2 | Observations..... | 135 | +| 8.2 | Coverage..... | 138 | +| 8.2.1 | Comparison between LP-WUS and NR reference channel..... | 138 | +| 8.2.1.1 | Summary of the performance gap between LP-WUS and NR reference channel..... | 138 | +| 8.2.1.2 | NR Coverage for comparison..... | 143 | +| 8.2.2 | Results for urban..... | 145 | +| 8.2.2.1 | OOK, Urban, normal UE, PDCCH..... | 146 | + +| | | | +|-----------|-------------------------------------------------------------|-----| +| 8.2.2.2 | OOK, Urban, Redcap UE, PDCCH..... | 149 | +| 8.2.2.3 | OOK, Urban, Normal UE, Msg.3..... | 151 | +| 8.2.2.4 | OOK, Urban, Redcap UE, Msg.3..... | 153 | +| 8.2.2.5 | FSK, Urban, Normal UE, PDCCH..... | 155 | +| 8.2.2.6 | FSK, Urban, Redcap UE, PDCCH..... | 158 | +| 8.2.2.7 | FSK, Urban, Normal UE, Msg.3..... | 160 | +| 8.2.2.8 | FSK, Urban, Redcap UE, Msg.3..... | 161 | +| 8.2.2.9 | OFDM, Urban, Normal UE, PDCCH..... | 162 | +| 8.2.2.10 | OFDM, Urban, Redcap UE, PDCCH..... | 167 | +| 8.2.2.11 | OFDM, Urban, Normal UE, Msg.3..... | 169 | +| 8.2.2.12 | OFDM, Urban, Redcap UE, Msg.3..... | 170 | +| 8.2.3 | Results for rural..... | 170 | +| 8.2.3.1 | OOK, Rural, normal UE, PDCCH..... | 171 | +| 8.2.3.2 | OOK, Rural, Redcap UE, PDCCH..... | 174 | +| 8.2.3.3 | OOK, Rural, Normal UE, Msg.3..... | 176 | +| 8.2.3.4 | OOK, Rural, Redcap UE, Msg.3..... | 177 | +| 8.2.3.5 | FSK, Rural, normal UE, PDCCH..... | 178 | +| 8.2.3.6 | FSK, Rural, Redcap UE, PDCCH..... | 178 | +| 8.2.3.7 | FSK, Rural, Normal UE, Msg.3..... | 179 | +| 8.2.3.8 | FSK, Rural, Redcap UE, Msg.3..... | 180 | +| 8.2.3.9 | OFDM, Rural, normal UE, PDCCH..... | 181 | +| 8.2.3.10 | OFDM, Rural, Redcap UE, PDCCH..... | 184 | +| 8.2.3.11 | OFDM, Rural, Normal UE, Msg.3..... | 187 | +| 8.2.3.12 | OFDM, Rural, Redcap UE, Msg.3..... | 189 | +| 8.3 | LLS results observations..... | 190 | +| 8.3.1 | Timing error..... | 190 | +| 8.3.1.1 | Results for timing error (without sliding window)..... | 190 | +| 8.3.1.1A | Observation for timing error (without sliding window):..... | 194 | +| 8.3.1.2 | Results for timing error (with sliding window)..... | 194 | +| 8.3.1.2A | Observation for timing error (with sliding window):..... | 197 | +| 8.3.2 | Frequency error..... | 197 | +| 8.3.2.1 | Results for frequency error..... | 197 | +| 8.3.2.1A | Observation for frequency error..... | 203 | +| 8.3.3 | Spectral efficiency..... | 203 | +| 8.3.4 | RSRP RRM measurement accuracy..... | 208 | +| 8.3.4.1 | Results for LP-SS RSRP RRM measurement, TDL-C..... | 208 | +| 8.3.4.1A | Observation RSRP LP-SS, TDL-C:..... | 210 | +| 8.3.4.2 | Results for LP-SS RSRP RRM measurement, AWGN..... | 210 | +| 8.3.4.2A | Observation RSRP LP-SS, AWGN:..... | 212 | +| 8.3.4.3 | Results for SSS RSRP RRM measurement, TDL-C..... | 212 | +| 8.3.4.3A | Observation for SSS RSRP RRM measurement, TDL-C..... | 213 | +| 8.3.5 | RSRQ RRM measurement accuracy..... | 213 | +| 8.3.5.1 | Results LP-SS, AWGN..... | 213 | +| 8.3.5.1A | Observation RSRQ LP-SS, AWGN:..... | 214 | +| 8.3.5.2 | Results LP-SS, TDL-C..... | 215 | +| 8.3.5.2A | Observation RSRQ LP-SS, TDL-C:..... | 216 | +| 8.4 | Network power consumption..... | 216 | +| 8.4.1 | Collection of the results..... | 216 | +| 8.4.2 | Observations..... | 217 | +| 8.5 | System overhead..... | 218 | +| 8.5.1 | Collection of the results..... | 218 | +| 8.5.1.1 | RRC IDLE/INACTIVE..... | 218 | +| 8.5.1.1.1 | LP-WUS..... | 218 | +| 8.5.1.1.2 | LP-SS..... | 232 | +| 8.5.1.2 | RRC CONNECTED..... | 234 | +| 8.5.2 | Observations..... | 235 | +| 9 | Conclusions..... | 237 | +| 9.1 | Power/latency/coverage/overhead/network energy..... | 237 | +| 9.2 | LP-WUR architecture..... | 240 | +| 9.3 | LLS performance and LP-WUS design/L1 procedure..... | 240 | +| 9.4 | RAN4 RF study..... | 242 | + +| | | | +|-----------------|-----------------------------------------------------------------------------------|------------| +| 9.5 | RAN4 RRM aspects for serving cell RSRP/RSRQ measurement offloading to LP-WUR..... | 243 | +| 9.6 | Higher-layer aspects..... | 243 | +| Annex..... | | 243 | +| Annex 7.1.1a | Analysis of LP-WUR architectures..... | 243 | +| Annex 8.1 | Power evaluation..... | 243 | +| Annex 8.2 | Coverage..... | 244 | +| Annex 8.3 | LLS results..... | 244 | +| Annex 8.4 | Network power consumption..... | 244 | +| Annex 8.4.1 | [8A-11]..... | 244 | +| Annex 8.4.2 | [8A-13]..... | 246 | +| Annex 8.4.3 | [8A-3]..... | 247 | +| Annex 8.4.4 | [8A-5]..... | 248 | +| Annex 8.5 | System Overhead..... | 248 | +| Annex 8.5.1 | [8A-11]..... | 248 | +| Annex 8.5.2 | [8A-13]..... | 250 | +| Annex 8.5.3 | [8A-5]..... | 252 | +| Annex 8.5.4 | [8A-16]..... | 252 | +| Annex 8.5.5 | [8A-4]..... | 254 | +| Annex 8.5.6 | [8A-3]..... | 257 | +| Annex 8.5.7 | [8A-9]..... | 259 | +| Annex X: | Change history..... | 261 | + +# 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 study item for " Study on low-power wake up signal and receiver for NR" [2]. + +The study includes investigations to + +- the impact of low-power wake-up signal and receiver , including power saving benefit, coverage, system overhead impact, network energy impact and other related aspects. +- the receiver architecture for low-power wake-up receiver and provide analysis for power consumption, noise figure and etc. +- L1 designs and procedures changes needed to support the wake-up signal and evaluations for the link performances. +- higher layer protocol changes needed to support the wake-up signals +- related RAN4 impacts + +# --- 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-222644: " Study on low-power wake up signal and receiver for NR". +- [3] 3GPP TR38.840: "Study on User Equipment (UE) power saving in NR" +- [4] 3GPP TR38.830: "Study on NR coverage enhancements" +- [5] 3GPP TR38.838: "Study on XR (Extended Reality) evaluations for NR" +- [6] 3GPP TR38.875: "Study on support of reduced capability NR devices" +- [7A-1] 3GPP R1-2306549: "Discussion on architecture of LP-WUS receiver", Huawei, HiSilicon. +- [7A-2] 3GPP R1-2306692: " Discussion on LP-WUS receiver architectures", InterDigital, Inc. +- [7A-3] 3GPP R1-2308472: "Remaining issues on low power wake-up receiver architecture", vivo. +- [7A-4] 3GPP R1-2307063: "Low-power WUS receiver architectures and its performance", CATT. +- [7A-5] 3GPP R1-2307143: "LP-WUS receiver architectures", ZTE, Sanechips. +- [7A-6] 3GPP R1-2307700: "Receiver architecture for LP-WUS", Samsung. +- [7A-7] 3GPP R1-2307990: "Low power WUS receiver architectures", Ericsson. +- [7A-8] 3GPP R1-2307949: "Receiver architecture for LP-WUS", Qualcomm Incorporated. +- [7A-9] 3GPP R1-2307300: "On low power wake-up receiver architectures", Apple, Inc. + +- [7A-10] 3GPP R1-2308068: "Low power WUS receiver architectures", MediaTek, Inc. +- [7B-1] 3GPP R4-2314665: " Discussions on low-power wake-up receiver architectures", vivo. +- [7B-2] 3GPP R4-2311502: " Evaluation of Low power wake-up receiver architectures", Nokia, Nokia Shanghai Bell. +- [7B-3] 3GPP R4-2315194: " Discussion on LP-WUS ACS and ASCS requirements", CMCC. +- [7B-4] 3GPP R4-2312248: " Further consideration on LP-WUS/WUR", Huawei, HiSilicon. +- [7B-5] 3GPP R4-2311902: " TP to TR 38.869: Low-power wake-up receiver RF aspects", Qualcomm Inc. +- [7B-6] 3GPP R4-2316697: " TP to TR 38.869: Low-power wake-up receiver RF aspects", Qualcomm Inc. +- [7B-7] 3GPP R4-2313476: " LS reply on low-power wake-up receiver architectures ", Ericsson. +- [7B-8] 3GPP R4-2316280: " TP on WUS guard RB", Ericsson. +- [7B-9] 3GPP R4-2320546: " TP on ADC impairment", Ericsson. +- [7B-10] 3GPP R4-2315206: " Low-power wake-up receiver RF aspects", Nokia, Nokia Shanghai Bell. +- [8A-1] 3GPP R1-2307299 On performance evaluation for low power wake-up signal APPLE +- [8A-2] 3GPP R1-2307062 Remaining issues of Deployment scenarios and evaluation methodologies and preliminary performance results of LP-WUR CATT +- [8A-3] 3GPP R1-2308438 Low power WUS evaluations Ericsson +- [8A-4] 3GPP R1-2306428 Evaluation of LP-WUS and Performance Results FUTUREWEI +- [8A-5] 3GPP R1-2306548 Evaluations for LP-WUS Huawei, HiSilicon +- [8A-6] 3GPP R1-2306691 Discussion on evaluation on LP-WUS InterDigital +- [8A-7] 3GPP R1-2308067 Evaluation on low power WUS MediaTek +- [8A-8] 3GPP R1-2307699 Evaluation on LP-WUS/WUR Samsung +- [8A-9] 3GPP R1-2308563 Evaluation for lower power wake-up signal OPPO +- [8A-10] 3GPP R1-2306665 Discussion on evaluation on low power WUS Spreadtrum +- [8A-11] 3GPP R1-2308249 Evaluation results for R18 LP-WUS/WUR vivo +- [8A-12] 3GPP R1-2306921 Evaluation of low-power WUS Sony +- [8A-13] 3GPP R1-2307142 Evaluation on LP-WUS ZTE, Sanechips +- [8A-14] 3GPP R1-2307356 Evaluation on low power WUS xiaomi +- [8A-15] 3GPP R1-2308234 Low power WUS Evaluation Methodology Nokia, Nokia Shanghai Bell +- [8A-16] 3GPP R1-2307948 Evaluation methodology for LP-WUS Qualcomm +- [8A-17] 3GPP R1-2304803 Evaluations on LP WUS Intel +- [8B-1] 3GPP R1-2306429 LP-WUS Physical Signal Design and Performance FUTUREWEI +- [8B-2] 3GPP R1-2306550 Further details on signal design and procedure for LP-WUS Huawei, HiSilicon +- [8B-3] 3GPP R1-2306626 Discussion on L1 signal design and procedure for low power WUS EURECOM +- [8B-4] 3GPP R1-2306666 Discussion on L1 signal design and procedure for low power WUS Spreadtrum Communications + +| | | | | +|---------|-----------------|-------------------------------------------------------------------------------|--------------------------------------| +| [8B-5] | 3GPP R1-2306682 | L1 signal design and procedure for low power WUS | TCL | +| [8B-6] | 3GPP R1-2306693 | Discussion on L1 signal design and procedure for LP-WUS | InterDigital, Inc. | +| [8B-7] | 3GPP R1-2306771 | Discussion on physical signal and procedure for low power WUS | vivo | +| [8B-8] | 3GPP R1-2306805 | Discussion on low power wake up signal design | Panasonic | +| [8B-9] | 3GPP R1-2306922 | On L1 signal design and procedures for LP-WUS | Sony | +| [8B-10] | 3GPP R1-2306927 | WUS Design Considerations and Impact on WUR Power | Everactive | +| [8B-11] | 3GPP R1-2307064 | Physical layer signals/procedures and higher layer protocol for Low-Power WUR | CATT | +| [8B-12] | 3GPP R1-2307116 | Discussion on L1 signal design and procedure for LP-WUS | NEC | +| [8B-13] | 3GPP R1-2307144 | LP-WUS design and related procedure | ZTE, Sanechips | +| [8B-14] | 3GPP R1-2307216 | Discussion on L1 signal design for low power WUS | CMCC | +| [8B-15] | 3GPP R1-2308469 | On the L1 signal design and procedures for low power wake-up signal | Apple | +| [8B-16] | 3GPP R1-2307357 | Discussions on L1 signal design and procedure for low power WUS | xiaomi | +| [8B-17] | 3GPP R1-2307420 | L1 signal design and procedures for low power WUS | Nokia, Nokia Shanghai Bell | +| [8B-18] | 3GPP R1-2307491 | L1 signal design and procedure for low power WUS | NTT DOCOMO, INC. | +| [8B-19] | 3GPP R1-2307557 | Design consideration on lower power wake-up signal and procedure | OPPO | +| [8B-20] | 3GPP R1-2307625 | Discussion on signal design and procedure for LP-WUS | China Telecom | +| [8B-21] | 3GPP R1-2307701 | Signal design and procedure for LP-WUS | Samsung | +| [8B-22] | 3GPP R1-2307795 | Discussion on L1 signal design and procedure for LP-WUS | LG Electronics | +| [8B-23] | 3GPP R1-2307856 | Discussion on L1 signal design and procedure for low power WUS | Sharp | +| [8B-24] | 3GPP R1-2307950 | L1 signal design and procedures for LP-WUR | Qualcomm Incorporated | +| [8B-25] | 3GPP R1-2307991 | L1 signal design and procedure for low power WUS | Ericsson | +| [8B-26] | 3GPP R1-2308022 | On LP-WUS signal design | Nordic Semiconductor ASA | +| [8B-27] | 3GPP R1-2308069 | L1 signal design and procedure for low power WUS | MediaTek Inc. | +| [8B-28] | 3GPP R1-2308102 | Discussion on the L1 signal design and procedure for low power WUS | Lenovo | +| [8B-29] | 3GPP R1-2308647 | R18 SI LLS results | Moderator (Nordic Semiconductor ASA) | + +# --- 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]. + +| | | +|-------------|---------------------------------------------------------------------------------| +| ACS | Adjacent Channel Selectivity | +| ADC | Analog to Digital Converter | +| ASCS | Adjacent Subcarrier selectivity | +| ASK | Amplitude Shift Keying | +| BB | Base Band | +| BLER | Block Error Rate | +| BPF | Band Pass Filter | +| BWP | Bandwidth part | +| CFO | Center frequency offset | +| CORESET | Control resource set | +| CRC | Cyclic redundancy check | +| CP-OFDMA | Cyclic Prefix-Orthogonal Frequency-Division Multiple Access | +| CSI | Channel state information | +| DCI | Downlink Control Information | +| DCP | DCI with CRC scrambled by PS-RNTI | +| DRX | Discontinuous Reception | +| DFT-S-OFDMA | Discrete Fourier Transform-Spread-Orthogonal Frequency-Division Multiple Access | +| eDRX | Extended DRX | +| EPRE | Energy Per Resource Element | +| FAR | False Alarm Rate | +| FCS | Frame Check Sequence | +| FSK | Frequency Shift Keying | +| FLL | Frequency Locked Loop | +| FFT | Fast Fourier Transform | +| FR1 | Frequency range 1 | +| FR2 | Frequency range 2 | +| ICS | In-channel Selectivity | +| IF | Intermediate Frequency | +| LP-WUS | Low Power-Wake Up Signal | +| LP-WUR | Low Power-Wake Up Receiver | +| LP-SS | Low Power- Synchronization Signal | +| LO | Local Oscillator | +| LNA | Low Noise Amplifier | +| LPF | Low Pass Filter | +| LR | LP-WUR | +| MDR | Miss Detection Rate | +| MC-ASK | Multiple Carrier-Amplitude Shift Keying | +| MC-FSK | Multiple Carrier-Frequency Shift Keying | +| MR | Main Radio | +| NF | Noise Figure | +| OOK | On-Off keying | +| OFDM | Orthogonal Frequency Division Multiplexing | +| PDCCH | Physical Downlink Control Channel | +| PUCCH | Physical Uplink Control Channel | +| PUSCH | Physical Uplink Shared Channel | +| PDSCH | Physical Downlink Shared Channel | +| PRACH | Physical Random Access Channel | +| PEI | Paging Early Indication | + +| | | +|------|-----------------------------------------| +| PO | Paging Occasion | +| PTW | Paging Time Window | +| PLL | Phase Locked Loop | +| PAPR | Peak to Average Power Ratio | +| RRC | Radio Resource Control | +| RRM | Radio Resource Management | +| RLM | Radio Link Monitoring | +| RS | Reference Signal | +| RSRP | Reference Signal Received Power | +| RSRQ | Reference Signal Received Quality | +| RTC | Real Time Clock | +| RF | Radio Frequency | +| SSB | Synchronization Signal Block | +| SSSG | Search Space Set Group | +| SINR | Signal to Interference plus Noise Ratio | +| SNR | Signal to Noise Ratio | +| SC | Subcarrier | +| UE | User Equipment | +| XR | Extended reality | + +# --- 4 Introduction + +5G systems are designed and developed targeting for both mobile telephony and vertical use cases. Besides latency, reliability, and availability, UE energy efficiency is also critical to 5G. Currently, 5G devices may have to be recharged per week or day, depending on individual's usage time. In general, 5G devices consume tens of milliwatts in RRC idle/inactive state and hundreds of milliwatts in RRC connected state. Designs to prolong battery life is a necessity for improving energy efficiency as well as for better user experience. + +Energy efficiency is even more critical for UEs without a continuous energy source, e.g., UEs using small rechargeable and single coin cell batteries. Among vertical use cases, sensors and actuators are deployed extensively for monitoring, measuring, charging, etc. Generally, their batteries are not rechargeable and expected to last at least few years as described in TR 38.875. Wearables include smart watches, rings, eHealth related devices, and medical monitoring devices. With typical battery capacity, it is challenging to sustain up to 1-2 weeks as required. + +The power consumption depends on the configured length of wake-up periods, e.g., paging cycle. To meet the battery life requirements above, eDRX cycle with large value is expected to be used, resulting in high latency, which is not suitable for such services with requirements of both long battery life and low latency. For example, in fire detection and extinguishment use case, fire shutters shall be closed and fire sprinklers shall be turned on by the actuators within 1 to 2 seconds from the time the fire is detected by sensors, long eDRX cycle cannot meet the delay requirements. eDRX is apparently not suitable for latency-critical use cases. Thus, the intention is to study ultra-low power mechanism that can support low latency in Rel-18, e.g. lower than eDRX latency. + +Currently, UEs need to periodically wake up once per DRX cycle, which dominates the power consumption in periods with no signalling or data traffic. If UEs are able to wake up only when they are triggered, e.g., paging, power consumption could be dramatically reduced. This can be achieved by using a wake-up signal to trigger the main radio and a separate receiver which has the ability to monitor wake-up signal with ultra-low power consumption. Main radio works for data transmission and reception, which can be turned off or set to deep sleep unless it is turned on. + +The power consumption for monitoring wake-up signal depends on the wake-up signal design and the hardware module of the wake-up receiver used for signal detecting and processing. + +The study should primarily target low-power WUS/WUR for power-sensitive, small form-factor devices including IoT use cases (such as industrial sensors, controllers) and wearables. Other use cases are not precluded, e.g. XR/smart glasses, smart phones. + +As opposed to the work on UE power savings in previous releases, this study will not require existing signals to be used as WUS. All WUS solutions identified shall be able to operate in a cell supporting legacy UEs. Solutions should target substantial gains compared to the existing Rel-15/16/17 UE power saving mechanisms. Other aspects such as detection performance, coverage, UE complexity, should be covered by the evaluation. + +## **The study item includes the following objectives:** + +- Identify evaluation methodology (including the use cases) & KPIs [RAN1] + - Primarily target low-power WUS/WUR for power-sensitive, small form-factor devices including IoT use cases (such as industrial sensors, controllers) and wearables + - Other use cases are not precluded +- Study and evaluate low-power wake-up receiver architectures [RAN1, RAN4] +- Study and evaluate wake-up signal designs to support wake-up receivers [RAN1, RAN4] +- Study and evaluate L1 procedures and higher layer protocol changes needed to support the wake-up signals [RAN2, RAN1] +- Study potential UE power saving gains compared to the existing Rel-15/16/17 UE power saving mechanisms, the coverage availability, as well as latency impact of low-power WUR/WUS. System impact, such as network power consumption, coexistence with non-low-power-WUR UEs, network coverage/capacity/resource overhead should be included in the study [RAN1] + - Note: The need for RAN2 evaluation will be triggered by RAN1 when necessary. + +Use the following terminology for future discussion, + +- Main radio (MR): the Tx/Rx module operating for NR signals/channels apart from signals/channel related to low-power wake-up +- LP-WUR (LR): The Rx module operating for receiving/processing signals/channel related to low-power wake-up. + +# --- 5 Use cases & KPI + +*Editor's note: The following SI Objective is included in this clause.* + +- Identify evaluation methodology (including the use cases) & KPIs [RAN1] + - Primarily target low-power WUS/WUR for power-sensitive, small form-factor devices including IoT use cases (such as industrial sensors, controllers) and wearables + - Other use cases are not precluded + +The following characteristics for target use cases are considered in the study item: + +- IoT cases including e.g., industrial wireless sensors, controllers, actuators and etc, including the following characteristics, + - primary for small form devices + - power-sensitive + - static, nomadic or limited mobility +- Wearable cases including e.g., smart watches, rings, eHealth related devices, and medical monitoring devices etc., + - primary for small form devices, + - power-sensitive + - low/medium speed, FFS: high speed +- eMBB cases including e.g., XR/smart glasses, smart phones and etc., + +- devices form is various and not restricted +- power-sensitive +- low/medium speed, FFS: high speed + +Note: other use cases/characteristics are not precluded if any. + +The latency for LP-WUS/WUR are considered as follows + +- Latency for RRC CONNECTED mode can be up to tens of milliseconds. +- Latency for RRC IDLE/INACTIVE mode can be in the order of seconds, for I-DRX use cases, and the latency can be larger for eDRX use cases. + +Both RRC IDLE/INACTIVE and CONNECTED modes were studied as part of the LP-WUS/WUR SI. + +# 6 Evaluation methodology + +*Editor's note: The clause includes evaluation methodology for this SI* + +## 6.1 General performance metrics + +For system impact analysis, the following performance metrics are considered to be provided, + +**Table 6.1-1: Performance metrics for system impact analysis** + +| Performance Metric | Note | +|------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| System overhead | expressed as percentage of used part of all REs for LP-WUS (including guard band or time or others resource used for LP-WUR if any) among all resources
Other assumptions related to the system overhead analysis can be reported, e.g., the LP-WUR raw data rate evaluated in the coverage evaluations. | +| Capacity impact | Evaluate the system capacity impact due to introducing of LP-WUS
Note: it is for UEs which are in connected mode. Definition is the same as in XR TR. | +| NW power consumption / Energy Efficiency | Impact of LP-WUS/WUR operation on gNB energy consumption as performance metric in system impact analysis. | + +For power and latency evaluation of the LP-WUS, the following performance metrics definitions provided for future study + +**Table 6.1-2: Performance metrics for power and latency evaluation** + +| Performance Metric | Note | +|--------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Power consumption | Relative power consumption in units. The power consumption includes main radio and LP-WUR. For comparison, the relative power consumption and evaluation period for baseline schemes should also be provided, as well as the power saving gain (i.e., percentage of power consumption reduction of the proposed power saving scheme from the baseline scheme). | +| Latency | For IDLE/INACTIVE state,
  • - the latency is the time interval between the data arrival time at the gNB and the time of the first PO UE can monitor the paging message
  • - alternatively, if UE is not required to monitor a PO after wake-up, company to report detailed procedure and definition of the latency
  • - sync/re-sync for main radio is included
| +| UPT | The definition is the same as in TR38.840
Note: it is for connected mode purpose. | + +- Companies to report baseline scheme, e.g., PO monitoring with i-DRX, e-DRX, with or without PEI +- Companies to report the power consumption / power saving gain considering the FAR impact, latency considering MDR impact + +- Other performance metrics (e.g., mobility) can be reported by companies (if any) + +## 6.2 Evaluation assumptions + +### 6.2.1 General evaluation assumptions + +#### RRC IDLE/INACTIVE evaluation assumptions + +The following is assumed for RRC IDLE/INACTIVE evaluation, + +**Table 6.2-1: RRC IDLE/INACTIVE evaluation assumptions** + +| Parameters | Value | +|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| i-DRX cycle length | 1.28s and other values not precluded and reported by companies, consider both with PEI/ without PEI | +| e-DRX cycle length | 20.48s, 61.44s and other values not precluded, company to report which value(s) are used. Note: 'ultra-deep sleep' state can be assumed for eDRX whenever necessary for baseline UE | +| Number of POs in Paging Frame | 1 | +| Number of DRXs per PTW | 4 | +| Number of SSB before PO / PEI | 1, 2 or 3, (used for e.g., AGC adjustment, T/F tracking, serving cell and intra-F measurement)
company to report which value(s) are used
Note: the assumptions is for MR wakes from 'Deep sleep' | +| Sync/re-sync after ultra-deep sleep | companies to report the timeline of sync/re-sync and X value, X is the time for sync/re-sync | +| RRM Measurement | Company to report whether and how the RRM measurement is assumed, e.g., whether RRM performed by main radio or LP-WUR, whether RRM is relaxed or not. | +| LP-WUS monitoring | Option 1: continuously monitoring
Option 2: discontinuously monitoring, with [T] ms as the period for complete an on-and-off cycle, and [D] ms as the active time for monitoring LP-WUS every cycle. | +| Traffic | Option 1 (baseline):
  • - The traffic arrival is modelled as a Poisson Arrival Process where inter-arrival times are exponentially distributed, the mean arrival time is P = Y_{REF} / R_{E, REF}, where
    • - R_{E, REF} = 1\%, 0.1\%, 0.01\% or 0.001\% and Y_{REF} = 1.28\text{s}
    • - Per group paging probability R_G = 1 - (1 - R_E)^N, where N is the number of UEs in the group
      • - FFS: Value of N
    • - For LP-WUS
      • - Both per group and UE paging can be assumed.
Note:
  • - For i-DRX with cycle duration Y second,
    • - Per UE paging probability R_E = 1 - (1 - R_{E, REF})^{Y/Y_{REF}}
  • - For e-DRX with K i-DRX cycles duration, PTW duration of L i-DRX cycles, and an i-DRX cycle duration Y second
    • - Per UE paging probability is
      • - R_E = 1 - (1 - R_{E, REF})^{(K-L+1)Y/Y_{REF}} for the first i-DRX cycle within the PTW
      • - R_E = 1 - (1 - R_{E, REF})^{Y/Y_{REF}} for each of the remaining L-1 i-DRX cycles within the PTW
    • - L=4
Other options are not precluded can be reported by companies. | +| Others | Reported by companies | + +The period of synchronization signal that LP-WUR used for at least power evaluation can be + +- Existing SSB periodicity can be used from gNB transmission perspective for evaluations assuming SSB, companies to report how often used for LP-WUR +- For evaluations assuming LP-SS + - {320ms, 640ms, 1280ms, 2560ms, 5120ms, 10240ms} + +- Companies to report other important assumptions if any, e.g., durations of LP-SS to achieve enough T/F accuracy +- Other values are not precluded + +Note: companies to report the purpose of the synchronization signal along with evaluations, e.g. can be for LR synchronization (i.e., time and/or frequency tracking) and/or measurement. + +For reference setting for further study on LP-SS performance and resource overhead (including sync and/or measurement), companies to report the following used in their evaluations + +- the number of slots or symbols per period +- the periodicity +- the functionality of the LP-SS + +#### RRC CONNECTED mode evaluation assumptions + +For R18 LP-WUS/WUR power evaluation in RRC connected mode, the following can be considered, + +- XR traffic model with evaluation methodologies and assumptions captured in TR 38.838. +- eMBB traffic model with evaluation methodologies and assumptions captured in TR 38.840 +- Heartbeat traffic models in TR 38.875. +- Other models are not precluded. + +Company to further provide the followings, + +- Parameters (e.g., frame rate, data rate, jitter range, DRX configurations and etc if needed.) +- How to use LP-WUS, e.g., LP-WUS to trigger/adapt PDCCH monitoring +- Other details if any + +For all RRC IDLE/INACTIVE/CONNECTED mode, + +- Power pooling between OFDM symbols is not assumed for evaluation purposes. Average EPRE is defined per OFDM symbol. + +### 6.2.2 Coverage evaluation assumptions + +For evaluation of the coverage of LP-WUS, the methodology and assumptions in R17 CovEnh SI (described in TR38.830) are reused as baseline. + +- MIL is used as the metric for LP-WUS coverage evaluation +- urban (2.6GHz/4GHz), rural(700MHz) scenario for FR1 are considered to be evaluated, others (e.g., FR2) are not precluded. + +Note: For IoT/wearables devices, refer to R17 Redcap SI TR38.875 if the assumptions differ from TR38.830. + +Companies report any other assumptions which differ from the TR38.875/ TR38.830, e.g., Tx and Rx loss + +Companies are encouraged to compare LP-WUS with at least PDCCH for paging, PUSCH, others are not precluded. +FFS: Target coverage of LP-WUS + +For LP-WUS coverage evaluation, the noise figure of LP-WUR is + +- Options : 9, 12, 15, 18, 21, 24 dB, Other values can be reported by companies + +FFS: how to determine the NF option. + +The values provided are for the purpose of studying coverage of LP-WUS, and they can be further revisited depending on the receiver architecture discussion. + +For evaluation, 1 Rx chain for LP-WUS receiver is baseline. + +For coverage evaluation, the following is used, + +**Table 6.2-2: Coverage evaluation assumptions** + +| | | | +|------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------| +| Number of RX chains at the UE's MR | Case 1: 1 Rx for Redcap
Case 2: 2 Rx
Case 3: 4 Rx
Company to report which case is being used. | | +| Number of RX chains for LP-WUR | 1 Rx | | +| Scenario and frequency | Urban: 4GHz (TDD), 2.6GHz (TDD)
Rural: 700MHz (FDD) | | +| Reference data rates for MR | Urban: PDSCH 10Mbps, PUSCH 1Mbps
Rural: PDSCH 1Mbps, PUSCH 100kbps | | +| Reference PDCCH configuration | SCS | 30kHz for TDD, 15kHz for FDD. | +| | Aggregation level | 8, 16
Company to report which case is being used.
Further decision on aggregation level for coverage is FFS. | +| | Payload | 40 bits | +| | CORESET size | 2 symbols, 48 PRBs | +| | Tx Diversity | Reported by companies | +| | BLER | 1% BLER, | +| Pathloss model (select from LoS or NLoS) | Urban: NLoS
Rural: NLoS | | +| Bandwidth | 100MHz for 4GHz and 2.6GHz.
20MHz (optional for 10MHz) for 700MHz. (FDD) | | +| Channel model for link-level simulation | TDL-C for NLOS | | +| Delay spread | Urban: 300ns, optional: 1000ns and companies to provide descriptions for such scenarios
Rural: 300ns | | +| UE velocity | Urban: 3km/h
Rural: 3km/h, FFS: 120km/h (optional 30km/h) for outdoor | | +| Number of antenna elements for BS | - Urban: 192 antenna elements for 4GHz and 2.6GHz, (M,N,P,Mg,Ng) = (12,8,2,1,1)
(optional) 128 antenna elements for 4GHz, (M,N,P,Mg,Ng) = (8,8,2,1,1)
- Rural: 16 antenna elements for 700MHz (M,N,P,Mg,Ng) = (4,2,2,1,1) | | +| Number of TxRUs for BS | gNB architectures to study:
- 2 or 4 TXRUs for 700 MHz
- 64TxRUs for 2.6 and 4 GHz. | | + +RAN1 further study the designs [target]/techniques of LP-WUS to have a comparable coverage as NR channel X. The NR channel X is + +- Option #1: PDCCH for paging +- Option #2: PUSCH for message3 +- FFS other options, e.g., between option1 and option2 (better than PUSCH, worse than PDCCH) + +- The final design will jointly consider the coverage with other KPIs + +Use the same channel specific assumptions as defined in TR38.830 for reference PUSCH for message3, i.e., + +| Parameter | Value | +|------------------------------|-------------------------------------------------------------------| +| Frequency hopping | w/ or w/o frequency hopping | +| Number of UE transmit chains | 1, 2 (optional) | +| Number of DMRS symbol | w/o frequency hopping: 3,
w/ frequency hopping: 2 for each hop | +| Waveform | DFT-s-OFDM | +| SCS | 30kHz for TDD, 15kHz for FDD. | +| HARQ configuration | Whether HARQ is adopted is reported by companies. | +| PUSCH duration | 14 OS | +| Number of PRBs | 2 | +| TBS | 56 bits | +| Other parameters | Reported by companies. | + +### 6.2.3 Link performance evaluation assumptions + +For link-level simulation of LP-WUS, the following table is used as starting point, + +- Note: The assumptions are not intended to limit the scope of the study or the design. + +**Table 6.2-3: Simulation assumptions for LP-WUS** + +| Attributes | Assumptions | +|-------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Carrier Frequency | 2.6GHz/4GHz/700MHz | +| Waveform | OOK , FSK , OFDM
Company to report which option for OOK /FSK /OFDM is used | +| Channel structure |
  • - Option 1: Sync signal /sequence+ payload + CRC,
  • - Option 2: Sequence only,
  • - Option 3: Payload+CRC,
  • - Other options are not precluded
  • - Company to report the sequence length, payload size, CRC length (may or may not be presence).
| +| SCS of OFDM generator for NR signal | 30kHz/15KHz | +| Configuration for LP-WUS signal | For OOK/FSK waveform,
  • - Option 1a: M=1 and SCSs = 15kHz (same as NR signal)
  • - Option 1b: M=1 and SCSs = 30kHz (same as NR signal)
  • - Option 2a: M =2/4/8 for SCS = 15KHz (same as NR signal)
  • - Option 2b: M =2/4/8 for SCS = 30 kHz (same as NR signal)
  • - Option 3: M=1 and SCSs = 60kHz/120kHz/240kHz
  • - Note: M is referred to the definition of "M" in the agreements for OOK-1/2/3/4 and FSK-1/2
For OFDM: FFS, e.g., ZC sequence.

Other options are up to companies to report | +| WUS duration | Number of OFDM symbols: e.g., 1,2,4, 8, 16,24 symbols | +| MDR/FAR assumption | The miss-detection rate (MDR) of LP-WUS 1%,
The false-alarm rate (FAR) of LP-WUS
  • - 0.1%, 1%
  • - Other values are not precluded for studying, reported by companies
Note: if LP-WUS for wake-up indication consists of two parts or even multiple parts, the proposed MDR/FAR should take into account the reception performance of the two or more parts jointly
The above values are applied in both RRC CONNECTED and IDLE/INACTIVE mode.
FFS FAR requirement based on the study outcome of the impact of FAR on power consumption / power saving gain / system overhead. | + +| | | +|----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

The FAR definition does NOT include the impact of the falsely alarmed for wake-up due to the detection of a LP-WUS which is intended to wake-up/alarm the LP-WUR of another UE within the same UE group.

For evaluation purpose, FAR target is determined across a reference time duration T of one or multiple LP-WUS attempts/trials,

  • - UE has N attempts within T,
  • - Company to report (FAR target, T, N)
  • - For example,
  • - if UE makes a single decision based on multiple correlations for a sequence in the monitor occasion, these correlations are considered as UE implementation in ONE trial/attempt.
  • - if UE performs decoding in a monitor occasion, a single decoding is considered as ONE trial/attempt.
  • - If UE performs N non-overlap attempts within the reference time duration, the false alarm event for the attempts are assumed as independent.

Companies to provide the assumed side conditions to attain the used FAR over T or per one attempt e.g. CRC/sequence length in LP-WUS design.

| +| Code scheme | Companies to report, if any, the coding scheme (e.g., Manchester code or any other schemes) and the code rate (e.g., 1/2, 1/4, ....) | +| gNB Channel BW | 20MHz, FFS other values | +| LP-WUS BW |

Option 1:

  • - 5MHz including subcarriers for guard band
  • - 4.32MHz (i.e., 12 RBs) for LP-WUS transmission for 30kHz SCS

Option 2:

  • - {2.16, 4.32} MHz including subcarriers for guard band
  • - 1.44MHz, 2.88MHz (i.e., {4, 8} RBs) for LP-WUS transmission for 30kHz SCS

Other options are up to companies to report

GB is symmetrically placed on each side of LP-WUS

| +| Filter |

X-th Order filter (e.g. Butterworth, Chebyshev, ...) with Y MHz bandwidth,

  • - X = {3, 5}
  • - Companies to report Y

Companies to report any other assumptions if needed

| +| Adjacent subcarrier interference |

PDSCH mapped on resources other than that for WUS and guard band;

EPRE of LP-WUS / EPRE of PDSCH = \rho, where \rho=0 dB as baseline, \rho=\{3, 6\} dB as optional

| +| Sampling Rate | Companies to report. | +| ADC bit width | 1-bit, 4-bit, 8-bit, ideal and other options are not precluded | +| Channel Model | See link coverage assumption table (Refer to Table 6.2-2) | +| Impairment modelling |

Frequency and time error model is referred to Tables 6.2-4 and 6.2-5

Phase noise up to company report, e.g. the modelling used for 802.11ba

Other cell interference is up to company to report

| + +For evaluation of LP-WUR frequency and time errors, the following is used, + +**Table 6.2-4: Frequency error/drifting** + +| Parameter | Value | +|-----------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Oscillator max frequency error [ppm],
Oscillator frequency drift [ppm/s] |

option 1: (200, 0.1)

option 2: (50, 0.1)

option 3: (10, 0.05)

option 4: (5, 0.05)

Other values are not precluded for studying, reported by companies

| +| RTC max frequency error [ppm] |

20

RTC drift report by company

| + +- Company to report how to use the clocks for LR on/off states +- The above clock assumptions for LR assume the MR is in 'ultra-deep sleep' power state. + +- Note: Assumptions important for achieving performance by option 1/2/3/4 clock for LR should be declared, including active on/off power, transition energy/ ramp-up time $T_{LR, ramp-up}$ for LR and etc. +- If MR is in other states than 'ultra-deep sleep state', the clock running for MR can be used for LR. + - assumptions important for achieving performance by using MR clock for LR should be declared +- Other clock accuracy options are not precluded. Companies to report options based on a feasibility analysis of clock power consumption and UE power consumption to use the clock accuracy option +- Company to report the frequency error assumption for the detection of LP-WUS/synchronization signal, +- The following are examples for consideration, other approaches are not precluded, + - Model 1: + - The relationship between a drifted frequency error( $\Delta F$ ), frequency drift ( $F'$ ) over a time ( $T1$ ) is $\Delta F = \pm F' * T1$ + - When frequency displacement [ $F_d$ ] reaches max frequency error, it is assumed to be equalled to max frequency error + - $T1$ is the time from the previous frequency synchronization. $T1$ may take different values depending on the chosen frequency synchronization approach. + - For Model 1 of frequency error, Frequency displacement ( $F_d$ ), defined as the difference between ideal frequency and frequency due to 1) clock drifting ( $\Delta F$ ); and 2) residual frequency error from previous synchronization/calibration ( $F_r$ ), is given as $F_d (ppm) = \Delta F (ppm) + F_r(ppm)$ , + - Companies to report $F_r$ and important assumptions for achieving $F_r$ , e.g., if MR can assist to calibrate LP-WUR to correct the frequency error or if LP-WUR can only correct the frequency error based on LP-WUS synchronization signal +- Company to report the timing drifting error assumption for the detection of LP-WUS/synchronization signal, +- The following are examples for consideration, other approaches are not precluded, + - Model 1 [R1-2301438] [R1-2301558][R1-1714993]: + - The relationship between the maximum frequency error( $F_e$ ) and corresponding timing drift( $\Delta T$ ) over a time( $T$ ) is $\Delta T = \pm F_e * T$ (linear region) + - The relationship between a frequency drift( $F'$ ), and corresponding timing drift( $\Delta T$ ) over a time( $T$ ) is $\Delta T = F_r * T \pm 0.5 * F' * T^2$ (transient region) + - The transition between transient and linear region (from synchronization or calibration point/time) occurs at time $[T_s = (F_e - F_r) / (F')]$ + +![A graph showing Timing drift = ΔT on the y-axis versus Time: t on the x-axis. The graph illustrates three regions: Calibration (a short initial segment), Transient region (a curved segment starting from the end of calibration), and Linear region (a straight line segment starting from the end of the transient region). A vertical dashed line marks the transition point Ts. The y-axis is labeled 'Timing drift = ΔT' and the x-axis is labeled 'Time: t'. The regions are labeled 'Calibration', 'Transient region', and 'Linear region'.](79cb7fa0e9c78ec5cd0b0de977824f8d_img.jpg) + +A graph showing Timing drift = ΔT on the y-axis versus Time: t on the x-axis. The graph illustrates three regions: Calibration (a short initial segment), Transient region (a curved segment starting from the end of calibration), and Linear region (a straight line segment starting from the end of the transient region). A vertical dashed line marks the transition point Ts. The y-axis is labeled 'Timing drift = ΔT' and the x-axis is labeled 'Time: t'. The regions are labeled 'Calibration', 'Transient region', and 'Linear region'. + +- $T$ is the time from the previous time synchronization. $T$ may take different values depending on the chosen synchronization approach +- FFS: Time error ( $T_e$ ) before detection of a current sync signal is defined as the difference between ideal time of the current sync signal and the time error due to 1) clock time drift ( $\Delta T$ ); and 2) residual time error from previous synchronization/calibration ( $T_r$ ); $T_e = \Delta T + T_r$ + +The following for usage of the clock is assumed for LP-WUR OFF/ON. + +**Table 6.2-5: Assumptions for the usage of the LP-WUR clock** + +| Assumption on LP-WUR OFF power | Assumptions on the clock usage | +|--------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0.001 |

When LP-WUR is OFF

  • - Time offset cumulated in the off period cannot be calculated based on the parameters of the oscillator option 1/2/3/4. RTC should be used(Only RTC is running during sleep.)

When LP-WUR is ON, frequency offset and time offset calculation can follow the parameters of the oscillator option 1/2/3/4 (cumulating based on the frequency drift and not exceeding maximum frequency error)

  • - The initial frequency offset when LP-WUR switches on can be set to the [FFS: maximum frequency error or a random value within the maximum frequency error] following the parameters of the oscillator option 1/2/3/4.
  • - When LP-WUR is synced with LP-SS/SSB or MR is used to assist to calibrate LP-WUR to correct the time/frequency error, residual frequency error F_r is assumed at the time when the synchronization/calibration is done.
| +| >0.001 |

For both LP-WUR OFF and ON

  • - Time offset cumulated in the off period can be calculated based on the parameter of the oscillator option 1/2 or option 3/4. RTC can be used too.
  • - Frequency offset calculation can follow the parameter of the oscillator option 1/2 or option 3/4 (cumulating based on the second value in the value pair and not exceeding maximum frequency error).

When at the time point after LP-WUR is synced with LP-SS/SSB or if MR can assist to calibrate LP-WUR to correct the frequency error

  • - Frequency offset is the F_r, which is residual frequency error from previous synchronization/calibration
| + +Note1: Any additional LO/FLL/PLL could start running during LP-WUR On duration. The power consumption of any of those LO/FLL/PLL is captured in LP-WUR On power + +Note3: The clock error (of both RTC and LO) could be improved to be less than max ppm error of option 1,2,3,4 with clock calibration based on sync signal such as LP-SS or preamble. + +## 6.3 Power consumption model + +### 6.3.1 Power model for Main Radio (MR) + +Take the following power model for main radio for evaluation in LP-WUS/WUR SI, + +- For IoT and wearable cases, reuse TR38.875 power model as baseline. +- For eMBB and other cases, reuse TR38.840 power model as baseline. +- Introduce '*Ultra-deep sleep*' power state for main radio of UEs with LP-WUS receiver + +The following power models are used for '*Ultra-deep sleep*' power state for main radio for evaluation. + +**Table 6.3-1: Power model for Main Radio** + +| Power State | Relative Power (unit) | Ramp-up and down transition energy (Note1): (unit multiplied by ms) | Ramp-up time | Time for sync/re-sync | +|------------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Ultra-deep sleep | 0.015 |

For evaluation, at least for FR1 MR ultra-deep sleep state, (Ramp-up and down transition energy, ramp-up time) is as follows,

  • - Alt 1: (15000, 400ms) as baseline
  • - Alt 2: (40000, 800ms)

Company to report which alternative they use for which use cases.

| |

For MR, at least for FR1 evaluation,

  • - Number of SSBs for sync/re-sync for MR is up to 10
  • - Companies to report timeline and energy consumption
| + +Note1: + +- Ramp-up time may consist of the procedure for main radio hardware tune on e.g., boot, memory load and etc., +- Time for sync/re-sync consists of the procedure for main radio to re-synchronization with the serving gNB etc., + - Companies can report the assumption of X in the initial evaluation. +- Ramp up and down energy includes power for ramp-up and ramp-down. Energy consumption for sync/re-sync is separately calculated. + +The total time for main radio transition from ultra-deep sleep to active/micro sleep state is the sum of ramp-up time and time for sync/re-sync. + +Note 2: The power state transitions in this table refer to transitions between ultra deep sleep state and active / micro sleep state. + +### 6.3.2 Power model for LP-WUR (LR) + +The following power model for LP-WUR is used for evaluation for FR1. + +**Table 6.3-2: Power model for LP-WUR** + +| Power State | Relative Power (unit) | Additional transition energy:
(unit multiplied by ms) | Ramp-up time
$T_{LR, ramp-up}$ (ms) | +|--------------------|-------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------| +| Off [1] | 0.001/ 0.02/ 0.1,
For 0.1, [oscillator option 3/4] are not used
for envelope detection based receiver | $T_{LR, ramp-up} \cdot (P_{ON} - P_{OFF})/2$

Note: this assumes the power consumption during the transition time is sum of additional transition energy and LP-WUR OFF energy, e.g., similar definition as the additional transition energy in TR38.840 | company to report $T_{LR, ramp-up}$ | +| On [2] | 0.01/0.05/0.1/0.2/0.5/1/2/4/10/20/30 | | | + +[1] Relative power unit for LP-WUR 'off' state, i.e., the LP-WUR does not perform monitoring +[2] Relative power unit for LP-WUR 'on' state, i.e., the LP-WUR performs monitoring + +- FFS: whether further categorization/sub-categorization is needed and how. +- FFS: Mapping from values to a LP-WUR architecture or LP-WUR mode of operation +- For evaluation, 10/20/30 for LP-WUR ON power state are not used for envelope detection based receiver for LP-WUS monitoring. +- For evaluation, 10/20/30 for LP-WUR ON power state are used for OFDM receiver when noise figure is less than [MR noise figure + 2.5dB], [0.2/0.5/1/2/4] for LP-WUS can be assumed for other NF values larger than [MR noise figure + 2.5dB] +- FFS: LP-WUR power consumption values for FR2. + +Note1: A unit of power is defined to be the same for main receiver and LP-WUS receiver. + +Note2: The values provided are for the purpose of studying power saving gain, and the values can be further revisited and categorized depending on the receiver architecture discussion. + +Note3: For LP-WUR 'on' state, more than one value within the above range may be used for evaluation (e.g. for a single LP-WUR architecture) + +Note4: For WUR Off value 0.001, oscillator options 1, 2, 3, 4 are not assumed and only RTC is maintained; + [For WUR Off value 0.02, oscillator options 1, 2 and RTC can be maintained; ] + +Note5: Up to companies to report whether same or different values are assumed for WUS monitoring and time/frequency synchronization. + +# 7 LP-WUR and LP-WUS design + +## 7.1 LP-WUS receiver architectures + +This clause includes the studies for LP-WUR architectures. It does not intend to mandate the implementation of any specific type(s) of LP WUR architecture at the UE. Note this does not prevent RAN4 from defining requirements for LP WUR in the normative phase. + +For the study on LP WUR architecture, power consumption relative to the deep sleep state of the MR is provided. + +- Deep sleep state of non-RedCap UE should be assumed + +For the LP WUR architectures analysis, in addition to LP-WUS detection, consider the following functions when necessary: + +- Synchronization signal processing and time/frequency synchronization for LP-WUR +- RRM measurement at least for the serving cell + +### 7.1.1 General description of receiver types + +Study at least the following three types of receiver architectures for LP-WUR: + +- Architecture with RF envelope detection +- Heterodyne architecture with IF envelope detection +- Homodyne/zero-IF architecture with baseband envelope detection +- Note: The details of each type of receiver architecture are discussed separately. +- Note: Above receiver architectures are considered suitable for OOK modulation. Some of the architectures can be applicable for other modulations such as FSK. + +#### A) RF envelope detection + +The architecture with RF envelope detection is based on at least the following diagram for LP-WUR. + +- The RF signal is converted into baseband signal directly via an RF envelope detector. +- There is no Local Oscillator (LO) and no Phase-Locked Loop (PLL). +- 1 bit or multi-bit ADC is applied. +- Some component(s), e.g., RF LNA and/or BB AMP, can be optionally applied. +- High-Q matching network and/or RF BPF [and/or BB LPF] can be used to suppress adjacent channel interference or interference from legacy NR signals and/or other LP WUS on adjacent subcarriers. +- FFS the support of band and/or carrier tuning + +![Block diagram of RF envelope detection based LP-WUR architecture. The signal flow starts from an antenna, passing through a Matching network, RF BPF, RF LNA, RF Envelope Detector, BB AMP, BB LPF, 1-bit or multi-bit ADC, and finally Digital BB processing.](73da53f7da73c0e2ead71eb1e2f746fb_img.jpg) + +``` +graph LR; Antenna --> Matching_network[Matching network]; Matching_network --> RF_BPF[RF BPF]; RF_BPF --> RF_LNA[RF LNA]; RF_LNA --> RF_Envelope_Detector[RF Envelope Detector]; RF_Envelope_Detector --> BB_AMP[BB AMP]; BB_AMP --> BB_LPF[BB LPF]; BB_LPF --> ADC[1-bit or multi-bit ADC]; ADC --> Digital_BB_processing[Digital BB processing]; +``` + +Block diagram of RF envelope detection based LP-WUR architecture. The signal flow starts from an antenna, passing through a Matching network, RF BPF, RF LNA, RF Envelope Detector, BB AMP, BB LPF, 1-bit or multi-bit ADC, and finally Digital BB processing. + +Figure 7.1.1-1: RF envelope detection based LP-WUR diagram + +For the architecture with RF envelope detection, + +- It can achieve relatively low power consumption due to the removal of LO/PLL. +- Interference suppression for adjacent channel interference requires very high-Q matching network and/or RF BPF, which is challenging due to the high Q values and may require off-chip components. +- Interference suppression for interference from legacy NR signals and/or other LP WUS on adjacent subcarriers, if performed in RF, requires very high-Q matching network and/or RF BPF, which is challenging due to the high Q values and may require off-chip components. +- The support of multiple bands and/or carriers may require multiple high-Q matching networks and/or RF BPFs or multiple off-chip components. +- RF LNA can be applied to improve sensitivity, with the cost of additional power consumption. +- The noise figure can be relatively high. + +#### B) Heterodyne architecture with IF envelope detection + +The heterodyne architecture with IF envelope detection is based on at least the following diagram for LP-WUR. + +- The RF signal is down converted into IF signal via an RF mixer with a LO. The IF signal is converted into baseband signal via an IF envelope detection. +- There may be one or multiple IF stages depending on design. +- The choice of the LO is one of the major factors that determine the power consumption. +- Lower power consumption can be achieved by relaxing the accuracy and stability requirements of the LO. However, such increased frequency offset and phase noise should be taken into account in the design and evaluation. +- FLL (frequency locked loop) may replace PLL for non-coherent detection. +- 1-bit or multi-bit ADC is applied. +- High-Q matching network and/or RF BPF and/or IF BPF [and/or BB LPF] can be used to suppress adjacent channel interference or interference from legacy NR signals and/or other LP WUS on adjacent subcarriers. +- Some component(s), e.g., RF LNA and/or IF AMP and/or BB AMP, can be optionally applied. +- Image rejection filter or an image rejection mixer is required. +- FFS the support of band and/or carrier tuning +- FFS the choice of IF frequency range + +![Block diagram of the heterodyne architecture with IF envelope detection based LP-WUR. The signal flow starts from an antenna, passing through a Matching network, RF BPF, RF LNA, Mixer (with LO input), IF AMP, IF BPF, IF Envelope Detector, BB AMP, BB LPF, 1-bit or multi-bit ADC, and finally Digital BB processing.](8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg) + +``` + +graph LR + Antenna[Antenna] --> Matching[Matching network] + Matching --> RF_BPF[RF BPF] + RF_BPF --> RF_LNA[RF LNA] + RF_LNA --> Mixer[Mixer] + LO((LO)) --> Mixer + Mixer --> IF_AMP[IF AMP] + IF_AMP --> IF_BPF[IF BPF] + IF_BPF --> IF_Envelope[IF Envelope Detector] + IF_Envelope --> BB_AMP[BB AMP] + BB_AMP --> BB_LPF[BB LPF] + BB_LPF --> ADC[1-bit or multi-bit ADC] + ADC --> Digital[Digital BB processing] + +``` + +Block diagram of the heterodyne architecture with IF envelope detection based LP-WUR. The signal flow starts from an antenna, passing through a Matching network, RF BPF, RF LNA, Mixer (with LO input), IF AMP, IF BPF, IF Envelope Detector, BB AMP, BB LPF, 1-bit or multi-bit ADC, and finally Digital BB processing. + +**Figure 7.1.1-2: Heterodyne architecture with IF envelope detection based LP-WUR diagram** + +For heterodyne architecture with IF envelope detection, + +- For the support of band and/or carrier tuning, the band and/or carrier tuning can be achieved via tuning the LO frequency. +- The matching network and RF BPF for LP WUR may or may not reuse those of the main radio. + +- It is more effective and less complex to use IF BPF instead of high-Q matching network and/or RF BPF to suppress adjacent channel interference or interference from legacy NR signals and/or other LP WUS on adjacent subcarriers. +- Using FLL instead of PLL consumes less power, but it may result in larger frequency error. +- The IF frequency can be properly selected to avoid LO leakage (DC offset) and flicker ( $1/f$ ) noise. +- Image rejection can be done via either image rejection filter or image rejection mixer. + - Image rejection filter can be done in either RF or IF, which may require high-Q filter. + - Image rejection mixer requires two-branch (I/Q) mixing with good matching in gain and phase, which consumes additional power. +- RF LNA and/or IF AMP can be applied to improve sensitivity, with the cost of additional power consumption. + +#### C) Homodyne/zero-IF architecture with baseband envelope detection + +The homodyne/zero-IF architecture with baseband envelope detection is based on at least the following diagram for LP-WUR. + +- The RF signal is directly down converted into baseband signal via an RF mixer with a LO. +- Baseband envelope detection can be done either in analog domain or in digital domain depending on design, which is not explicitly shown in the diagram. +- The choice of the LO is one of the major factors that determine the power consumption. +- Lower power consumption can be achieved by relaxing the accuracy and stability requirements of the LO. However, such increased frequency offset and phase noise should be taken into account in the design and evaluation. +- FLL (frequency locked loop) may replace PLL for non-coherent detection. +- 1-bit or multi-bit ADC is applied. +- High-Q matching network and/or RF BPF and/or BB BPF [and/or BB LPF] can be used to suppress adjacent channel interference or interference from legacy NR signals and/or other LP WUS on adjacent subcarriers. +- No image rejection filter is required. +- Some component(s), e.g., RF LNA and/or BB AMP, can be optionally applied. + +![Block diagram of Homodyne/zero-IF architecture with baseband envelope detection based LP-WUR. The signal flow starts from an antenna, passing through a Matching network, RF BPF, RF LNA, Mixer (with LO input), BB AMP, BB LPF or BPF, 1-bit or multi-bit ADC, and finally Digital BB processing.](20136850feb70fd71c7d41cdae203ebb_img.jpg) + +``` + +graph LR + Antenna[Antenna] --> Matching[Matching network] + Matching --> RF_BPF[RF BPF] + RF_BPF --> RF_LNA[RF LNA] + RF_LNA --> Mixer[Mixer] + LO((LO)) --> Mixer + Mixer --> BB_AMP[BB AMP] + BB_AMP --> BB_LPF[BB LPF or BPF] + BB_LPF --> ADC[1-bit or multi-bit ADC] + ADC --> Digital[Digital BB processing] + +``` + +Block diagram of Homodyne/zero-IF architecture with baseband envelope detection based LP-WUR. The signal flow starts from an antenna, passing through a Matching network, RF BPF, RF LNA, Mixer (with LO input), BB AMP, BB LPF or BPF, 1-bit or multi-bit ADC, and finally Digital BB processing. + +**Figure 7.1.1-3: Homodyne/zero-IF architecture with baseband envelope detection based LP-WUR diagram** + +For homodyne/zero-IF architecture with baseband envelope detection, + +- For the support of band and/or carrier tuning, the band and/or carrier tuning can be achieved via tuning the LO frequency. +- The matching network and RF BPF for LP WUR may or may not reuse those of the main radio. + +- It is more effective and less complex to use BB BPF/LPF instead of high-Q matching network and/or RF BPF to suppress adjacent channel interference or interference from legacy NR signals and/or other LP WUS on adjacent subcarriers. +- Using FLL instead of PLL consumes less power, but it may result in larger frequency error. +- It can suffer from LO leakage (DC offset) and flicker ( $1/f$ ) noise. The impact may be alleviated by using BB BPF in some cases. +- RF LNA can be applied to improve sensitivity, with the cost of additional power consumption. +- The baseband envelope detection can be done in either analog domain (before ADC) or digital domain (after ADC). + +#### D) FSK receiver + +Two examples for FSK receiver architectures are shown below: + +- Example 1: parallel OOK receivers and a comparator circuit, e.g., + - Each path can be implemented using either of [the architecture with RF envelope detection,] heterodyne architecture with IF envelope detection, or homodyne/zero-IF architecture with baseband envelope detection. + +![Figure 7.1.1-4: FSK receiver with parallel OOK receivers and a comparator circuit based LP-WUR diagram. The diagram shows an input signal s_{2F SK}(t) branching into two parallel paths. Each path consists of a Band Pass Filter (BPF) labeled f1 and f0 respectively, followed by an Envelope Detector. The outputs of these detectors are labeled r1(t) and r0(t). Both r1(t) and r0(t) are then fed into a Sampling decision block, which produces the final Output.](e29665b8abcea967ef289c6aff07ae4c_img.jpg) + +Figure 7.1.1-4: FSK receiver with parallel OOK receivers and a comparator circuit based LP-WUR diagram. The diagram shows an input signal s\_{2F SK}(t) branching into two parallel paths. Each path consists of a Band Pass Filter (BPF) labeled f1 and f0 respectively, followed by an Envelope Detector. The outputs of these detectors are labeled r1(t) and r0(t). Both r1(t) and r0(t) are then fed into a Sampling decision block, which produces the final Output. + +**Figure 7.1.1-4: FSK receiver with parallel OOK receivers and a comparator circuit based LP-WUR diagram** + +Study the parallel receiver architectures (as examples that can be captured in the TR) for FSK based on the following diagrams: + +- Parallel homodyne architecture + +![Figure 7.1.1-5: Parallel homodyne architecture. The diagram shows a signal path starting from an antenna through a Matching network, RF BPF, RF LNA, and a mixer. The mixer also receives a local oscillator (LO) signal. The output of the mixer is amplified by a BB AMP. The signal then splits into two parallel branches. Each branch contains a Band Pass Filter (BPF) labeled f0 and f1 respectively, followed by a 1-bit or multi-bit ADC. The outputs of these ADCs are then processed by a Digital BB processing block.](82b40cb8b2a5ac361973859400fa128a_img.jpg) + +Figure 7.1.1-5: Parallel homodyne architecture. The diagram shows a signal path starting from an antenna through a Matching network, RF BPF, RF LNA, and a mixer. The mixer also receives a local oscillator (LO) signal. The output of the mixer is amplified by a BB AMP. The signal then splits into two parallel branches. Each branch contains a Band Pass Filter (BPF) labeled f0 and f1 respectively, followed by a 1-bit or multi-bit ADC. The outputs of these ADCs are then processed by a Digital BB processing block. + +**Figure 7.1.1-5: Parallel homodyne architecture** + +- The observations made for homodyne/zero-IF architecture with baseband envelope detection in clause 7.1.1-(C) are also applicable here. +- Parallel heterodyne architecture + +![Figure 7.1.1-6: Parallel heterodyne architecture. The diagram shows a signal path starting from an antenna through a Matching network, RF BPF, RF LNA, and a mixer. The mixer also receives a local oscillator (LO) signal. The output of the mixer is amplified by an IF AMP. The signal then splits into two parallel branches. Each branch contains an Intermediate Frequency Band Pass Filter (IF BPF) labeled f0 and f1 respectively, followed by an IF envelope detector, a BB AMP, and a BB LPF. The outputs of these BB LPFs are then fed into a Sampling decision block, which produces the final Digital BB output.](bdcc4eb452fcc6ba091949b77546a6d4_img.jpg) + +Figure 7.1.1-6: Parallel heterodyne architecture. The diagram shows a signal path starting from an antenna through a Matching network, RF BPF, RF LNA, and a mixer. The mixer also receives a local oscillator (LO) signal. The output of the mixer is amplified by an IF AMP. The signal then splits into two parallel branches. Each branch contains an Intermediate Frequency Band Pass Filter (IF BPF) labeled f0 and f1 respectively, followed by an IF envelope detector, a BB AMP, and a BB LPF. The outputs of these BB LPFs are then fed into a Sampling decision block, which produces the final Digital BB output. + +**Figure 7.1.1-6: Parallel heterodyne architecture** + +- The observations made for heterodyne architecture with IF envelope detection in clause 7.1.1-(B) are also applicable here. + +- Note: Other architectures are not precluded. +- The OOK receiver architectures agreed for study in RAN1#110bis-e are also examples that can be captured in the TR + +For FSK receiver based on parallel OOK receivers with heterodyne or zero-IF architecture, + +- If no interference between the segments' detectors is allowed, the frequency gap between two adjacent frequency segments should not be smaller than two times the maximum frequency offset, and at least two times of the max frequency offsets within the frequency gap should not be used by other DL signals/channels or other WUS signals. +- If some interference between the segments' detectors is allowed, it can be possible to have frequency gap between two adjacent frequency segments smaller than two times the maximum frequency offset, where the gap is not used by other DL signals/channels or other WUS signals. +- Example 2: using an FM-to-AM detector [or an FM detector] + - Alt 1: Use an analog FM-to-AM detector with a similar architecture as for OOK (e.g. heterodyne or zero-IF architecture), except that the envelope detector is replaced by a FM-to-AM detector. + - Analog FM-to-AM detector can be implemented at least in BB or low-IF. + +![Figure 7.1.1-7: FSK LP-WUS receiver with FM-AM detector- Alt 1. The block diagram shows a linear signal flow: FSK signal -> BPF -> FM-AM detector -> Low order ADC -> BB proc.](705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg) + +``` + +graph LR + A[FSK signal] --> B[BPF] + B --> C[FM-AM detector] + C --> D[Low order ADC] + D --> E[BB proc] + +``` + +Figure 7.1.1-7: FSK LP-WUS receiver with FM-AM detector- Alt 1. The block diagram shows a linear signal flow: FSK signal -> BPF -> FM-AM detector -> Low order ADC -> BB proc. + +**Figure 7.1.1-7: FSK LP-WUS receiver with FM-AM detector- Alt 1** + +- Alt 2: Use a FM-to-AM detector [or an FM detector] implemented in digital domain after ADC, with a heterodyne or zero-IF architecture. + - Digital FM-to-AM detector implementation can be considered as part of digital baseband processing. + - Here is an example of using zero-IF architecture: + +![Figure 7.1.1-8: FSK LP-WUS receiver with FM-AM detector - Alt 2. The block diagram shows a zero-IF receiver architecture: Antenna -> Matching network -> RF BPF -> RF LNA -> Mixer (with LO input) -> BB AMP -> BB LPF or BPF -> 1-bit or multi-bit ADC -> FM detector -> Digital BB processing.](9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg) + +``` + +graph LR + Antenna --> MN[Matching network] + MN --> RBP[RF BPF] + RBP --> RLNA[RF LNA] + RLNA --> Mixer + LO((LO)) --> Mixer + Mixer --> BBAMP[BB AMP] + BBAMP --> BLPF[BB LPF or BPF] + BLPF --> ADC[1-bit or multi-bit ADC] + ADC --> FM[FM detector] + FM --> DBB[Digital BB processing] + +``` + +Figure 7.1.1-8: FSK LP-WUS receiver with FM-AM detector - Alt 2. The block diagram shows a zero-IF receiver architecture: Antenna -> Matching network -> RF BPF -> RF LNA -> Mixer (with LO input) -> BB AMP -> BB LPF or BPF -> 1-bit or multi-bit ADC -> FM detector -> Digital BB processing. + +**Figure 7.1.1-8: FSK LP-WUS receiver with FM-AM detector - Alt 2** + +- The FM-AM detector can be implemented using a frequency discriminator, which converts frequency variations into amplitude changes. It can be implemented in either analog domain (as in Alt 1) or digital domain (as in Alt 2). + - One example, as shown in the figure below, is a conventional quadrature FM discriminator. It multiplies received frequency modulated signal with a phase shifted version, followed by a low pass filter. The amplitude of the output signal is proportional to the frequency of the input signal. + +![Block diagram of an FSK LP-WUS receiver using a quadrature frequency discriminator. An FM signal enters a dashed box labeled 'Quadrature frequency discriminator'. Inside, the signal is split: one path goes to a mixer, and the other goes to a 'Phase Shifter circuit'. The output of the phase shifter is also fed into the mixer. The mixer's output passes through an LPF to produce an 'AM signal', which is then processed by an 'Amplitude detector'.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +Block diagram of an FSK LP-WUS receiver using a quadrature frequency discriminator. An FM signal enters a dashed box labeled 'Quadrature frequency discriminator'. Inside, the signal is split: one path goes to a mixer, and the other goes to a 'Phase Shifter circuit'. The output of the phase shifter is also fed into the mixer. The mixer's output passes through an LPF to produce an 'AM signal', which is then processed by an 'Amplitude detector'. + +**Figure 7.1.1-9: FSK LP-WUS receiver with FM-AM detector by using a frequency discriminator** + +- Note: Other architectures are not precluded. + +Study the receiver architectures (as examples that can be captured in the TR) for FSK with frequency to amplitude conversion based on the following diagrams: + +- Homodyne architecture with frequency to amplitude conversion + - I/Q branches are required for frequency to amplitude conversion in digital BB. + +![Block diagram of a homodyne architecture. The RF signal passes through a 'Matching network', 'Bandpass Filter', and 'LNA'. It is then mixed with a local oscillator (LO) signal, which is phase-shifted by pi/2. The resulting I and Q signals, s_I(t) and s_Q(t), are amplified (AMP), filtered (LPF), and digitized (ADC). These digital signals are then processed in 'Digital BB processing' using differentiators (d/dt) and mixers to produce the final AM signal s_AM(t).](f2ea0f64a770b22b902820457d262265_img.jpg) + +Block diagram of a homodyne architecture. The RF signal passes through a 'Matching network', 'Bandpass Filter', and 'LNA'. It is then mixed with a local oscillator (LO) signal, which is phase-shifted by pi/2. The resulting I and Q signals, s\_I(t) and s\_Q(t), are amplified (AMP), filtered (LPF), and digitized (ADC). These digital signals are then processed in 'Digital BB processing' using differentiators (d/dt) and mixers to produce the final AM signal s\_AM(t). + +**Figure 7.1.1-10: Homodyne architecture with frequency to amplitude conversion** + +- Heterodyne architecture with frequency to amplitude conversion + +![Block diagram of a heterodyne architecture. The RF signal passes through a 'Matching network', 'RF BPF', and 'RF LNA'. It is then mixed with an LO signal to produce an IF signal. This IF signal is amplified (IF AMP), filtered (IF BPF), and then converted from frequency to amplitude (FM-to-AM conversion). The resulting signal is amplified (BB AMP), filtered (BB LPF), and digitized (1-bit or multi-bit ADC) for 'Digital BB processing'.](1c29dadab94c3fa552d270434db09c81_img.jpg) + +Block diagram of a heterodyne architecture. The RF signal passes through a 'Matching network', 'RF BPF', and 'RF LNA'. It is then mixed with an LO signal to produce an IF signal. This IF signal is amplified (IF AMP), filtered (IF BPF), and then converted from frequency to amplitude (FM-to-AM conversion). The resulting signal is amplified (BB AMP), filtered (BB LPF), and digitized (1-bit or multi-bit ADC) for 'Digital BB processing'. + +**Figure 7.1.1-11: Heterodyne architecture with frequency to amplitude conversion** + +- Companies provide the exact type of frequency to amplitude conversion being studied. +- Note: Other architectures are not precluded. + +Observation for FSK with frequency to amplitude conversion: + +- The FSK architectures with frequency to amplitude conversion is applicable to single-SC FSK, but it may be challenging to make the frequency to amplitude conversion work well with multi-subcarrier FSK. +- Note: single-SC FSK refers to the waveform where each frequency segment has a single subcarrier, and multi-subcarrier FSK refers to the waveform where each frequency segment has multiple subcarriers, as described in the agreements for FSK-1 and FSK-2. + +For the FSK architectures with frequency to amplitude conversion, the bandwidth between the frequency segments used for FSK transmissions may not be used for other LP-WUSs or legacy NR transmission in order to allow frequency to amplitude conversion to work properly. + +#### E) OFDMA-based signals/channels detection + +For OFDMA-based signals/channels, study the receiver architectures based on the following diagrams: + +- I/Q branches are required for digital BB processing. +- Digital BB processing may or may not include FFT (companies to provide details on how). +- For sequence-based OFDM signals/channels, digital BB processing includes sequence correlation in either time domain (without FFT) or frequency domain (after FFT). +- Proponent companies should at least provide details on power consumption reduction compared to the MR regarding the RF and digital BB processing. + - Companies are encouraged to provide the break-down for the components. + - The potential power reduction compared to the main radio may come from e.g.: + - Lower performance LNA/amplifier + - Oscillator/PLL with relaxed performance requirements + - ADC with lower sampling rate and smaller bit-width + - Reduced BB processing complexity compared to the MR + - Companies are encouraged to provide the performance analysis corresponding to the considered power consumption considering the impact of e.g. phase noise, I/Q mismatch. + - Companies to report whether the LP WUR is assumed to share components with MR. In case of component sharing, the potential impact on the MR ultra-deep sleep state should be considered. + - Companies to report the possible number of information bits +- In addition, companies should consider the power consumption in the OFF state and the transition energy. + +![Block diagram of an OFDMA-based receiver architecture. The signal path starts with an antenna connected to a 'Matching network', followed by an 'RF BPF' (Band Pass Filter) and an 'RF LNA' (Low Noise Amplifier). The signal then splits into two parallel branches. Each branch contains a mixer (represented by a circle with an 'X'), a 'BB AMP' (Baseband Amplifier), a 'BB LPF' (Baseband Low Pass Filter), and an 'ADC' (Analog-to-Digital Converter). A local oscillator (LO) is connected to both mixers, with a phase shifter labeled 'π/2' between the LO and the top mixer. The outputs of the two ADCs are fed into a large block labeled 'Digital BB processing'.](6470d350326789d5306eabcb76533951_img.jpg) + +Block diagram of an OFDMA-based receiver architecture. The signal path starts with an antenna connected to a 'Matching network', followed by an 'RF BPF' (Band Pass Filter) and an 'RF LNA' (Low Noise Amplifier). The signal then splits into two parallel branches. Each branch contains a mixer (represented by a circle with an 'X'), a 'BB AMP' (Baseband Amplifier), a 'BB LPF' (Baseband Low Pass Filter), and an 'ADC' (Analog-to-Digital Converter). A local oscillator (LO) is connected to both mixers, with a phase shifter labeled 'π/2' between the LO and the top mixer. The outputs of the two ADCs are fed into a large block labeled 'Digital BB processing'. + +**Figure 7.1.1-12: OFDMA-based signals/channels detection** + +For the receiver architecture for OFDMA-based signals/channels, + +- The receiver architectures for OFDMA-based signals/channels can be used for OOK/ASK and FSK modulated LP-WUS +- For sequence-based OFDM signals/channels, one example diagram with time domain correlator (without FFT) for LP-WUS detection is shown below: + +![Figure 7.1.1-13: Example for time domain correlator (without FFT) for LP-WUS detection. The diagram shows a dashed box containing a multiplier (circle with an X), an integrator (circle with an integral symbol), and an LP-WUS detection block. An input signal enters the multiplier from the left. A 'Stored sequence' block is connected to the bottom of the multiplier. The output of the multiplier goes to the integrator, which then connects to the LP-WUS detection block. The output of the LP-WUS detection block exits the dashed box to the right.](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +Figure 7.1.1-13: Example for time domain correlator (without FFT) for LP-WUS detection. The diagram shows a dashed box containing a multiplier (circle with an X), an integrator (circle with an integral symbol), and an LP-WUS detection block. An input signal enters the multiplier from the left. A 'Stored sequence' block is connected to the bottom of the multiplier. The output of the multiplier goes to the integrator, which then connects to the LP-WUS detection block. The output of the LP-WUS detection block exits the dashed box to the right. + +**Figure 7.1.1-13 Example for time domain correlator (without FFT) for LP-WUS detection** + +#### F) Additional LP-WUR related designs + +For the baseband processing of the LP WUR architectures, + +- The baseband processing may use Goertzel filters as an alternative for FFT to compute the signals for one or more tones. Tone energy is computed and a detection algorithm is used to detect the presence of LP-WUS. One example diagram is shown below: + +![Figure 7.1.1-14: Example for using Goertzel filters as an alternative for FFT to compute the signals for one or more tones. The diagram shows a dashed box containing multiple parallel processing paths. Each path consists of a Goertzel filter block labeled G(f_{m=1}), G(f_{m=2}), ..., G(f_{m=k}), followed by an energy computation block labeled ||^2. The outputs of these energy computation blocks are summed and then sent to an LP-WUS detection block. A 'Received Energy Computation' block is also shown, with its output sent to the LP-WUS detection block. The output of the LP-WUS detection block exits the dashed box to the right.](dc1f232cfd39be5c20b21374ad4c04c0_img.jpg) + +Figure 7.1.1-14: Example for using Goertzel filters as an alternative for FFT to compute the signals for one or more tones. The diagram shows a dashed box containing multiple parallel processing paths. Each path consists of a Goertzel filter block labeled G(f\_{m=1}), G(f\_{m=2}), ..., G(f\_{m=k}), followed by an energy computation block labeled ||^2. The outputs of these energy computation blocks are summed and then sent to an LP-WUS detection block. A 'Received Energy Computation' block is also shown, with its output sent to the LP-WUS detection block. The output of the LP-WUS detection block exits the dashed box to the right. + +**Figure 7.1.1-14: Example for using Goertzel filters as an alternative for FFT to compute the signals for one or more tones** + +- This can be used with the receiver architecture for OFDMA-based signals/channels for OOK-3. +- This can be used with heterodyne receiver architecture with IF envelope detection or the homodyne receiver architecture with baseband envelope detection for [OOK-1]/FSK-2. + +### 7.1.1a Analysis of LP-WUR architectures + +For the analysis of different LP-WUR receiver types, at least the following aspects have been considered, and the corresponding power consumption and noise figure have been estimated. + +- Assumed modulation/waveform/coding +- Presence of a RF LNA / IF AMP / BB AMP, and the corresponding gain, if any +- Local oscillator + - Type of oscillator and the corresponding frequency accuracy/drifting +- Handling of time/frequency impairments (e.g. synchronization signal processing and time/frequency synchronization for LP-WUR) +- Presence of PLL or FLL + +- ADC: sampling rate, bit-width +- Assumed signal bandwidth and guard band, and frequency location within a carrier (including whether it is fixed or can be flexible) +- RF/IF/BB filter characteristics (e.g. type of filter, order, cut-off frequency/frequencies), if any +- Baseband processing (e.g., sequence correlation detection / decoding, other signal processing, if any) +- Assumed frequency band(s) and the support of band and/or carrier tuning +- Duty cycle handling of WUS and other signals (if any) +- Interference rejection capability (including both adjacent-channel interference and interference from adjacent subcarriers occupied by legacy NR signals or other LP WUS) +- Handling of inter-cell interference +- Whether there is any mobility support function, e.g. measurement capability + +The results are summarized for each receiver architecture considering different waveform candidates (more details can be found in Annex 7.1.1a and the references are in 7.1.1a.4). The analysis is very high level, and the actual power consumption and noise figure are very implementation specific. Note that the power consumption is provided in relative unit, relative to the deep sleep state of the MR for a non-RedCap UE following the non-RedCap UE power model defined in clause 8.1 of TR 38.840. + +For the analysis, + +- FR1 is considered. +- Most sources assumed RF LNA is present for improved sensitivity. +- For LP-WUS bandwidth, most sources consider at least 5MHz. Some sources think the analysis is also applicable to bandwidth up to 20MHz. + +#### 7.1.1a.1 OOK-1/2/4 + +##### 7.1.1a.1.1 RF envelope detection + +For OOK-1/2/4 with RF envelope detection, some sources ([7A-1] [7A-2] [7A-3] [7A-4] [7A-5] [7A-6]) provided analysis, with relative power consumption and noise figure summarized in Table 7.1.1a-1. + +- The relative power consumption for ON state is in the range of 0.01~0.2. +- The noise figure is in the range of 12~22 dB. + +**Table 7.1.1a-1: Relative power consumption and noise figure for OOK-1/2/4 with RF envelope detection** + +| Source reference | [7A-1] | [7A-2] | [7A-3] | [7A-4] | [7A-5] | [7A-6] | +|------------------------------|---------------------------------------------------------|--------|----------|--------|----------|----------| +| Power consumption (ON state) | 0.05 for single-branch, 0.01 for each additional branch | 0.01 | 0.01~0.1 | 0.01 | 0.01~0.1 | 0.05~0.2 | +| Noise figure (dB) | 20 | 17~22 | [12-18] | 20 | 15 | 20 | + +##### 7.1.1a.1.2 Heterodyne architecture with IF envelope detection + +For OOK-1/2/4 with heterodyne architecture with IF envelope detection, some sources ([7A-1] [7A-2] [7A-3] [7A-4] [7A-5] [7A-6] [7A-7] [7A-8]) provided analysis, with relative power consumption and noise figure summarized in Table 7.1.1a-2. + +- The relative power consumption for ON state is in the range of 0.1~4. +- The noise figure is in the range of 9~15 dB. + +**Table 7.1.1a-2: Relative power consumption and noise figure for OOK-1/2/4 with heterodyne architecture with IF envelope detection** + +| Source reference | [7A-1] | [7A-2] | [7A-3] | [7A-4] | [7A-5] | [7A-6] | +|------------------------------|--------------------------------------------------------|--------|--------|--------|--------|--------| +| Power consumption (ON state) | 0.1 for single-branch, 0.01 for each additional branch | 0.5 | 0.1~1 | 0.1 | 0.1~1 | 1~4 | +| Noise figure (dB) | 15 | 10~15 | [9-15] | 15 | 12 | 12~15 | + +##### 7.1.1a.1.3 Homodyne/zero-IF architecture with baseband envelope detection + +For OOK-1/2/4 with homodyne/zero-IF architecture with baseband envelope detection, some sources ([7A-1] [7A-2] [7A-3] [7A-4] [7A-5] [7A-6] [7A-7] [7A-8] [7A-9] [7A-10]) provided analysis, with relative power consumption and noise figure summarized in in Table 7.1.1a-3. + +- The relative power consumption for ON state is in the range of 0.05~4. +- The noise figure is in the range of 10~16 dB. + +**Table 7.1.1a-3: Relative power consumption and noise figure for OOK-1/2/4 with homodyne/zero-IF architecture with baseband envelope detection** + +| Source reference | [7A-1] | [7A-2] | [7A-3] | [7A-4] | [7A-5] | [7A-6] | [7A-7] | [7A-8] | [7A-9] | [7A-10] | +|------------------------------|-----------------------------------------------------------------|--------|---------|--------|----------|--------|---------|--------|--------|---------| +| Power consumption (ON state) | 0.09 for single-branch, 0.01 or 0.02 for each additional branch | 0.5 | 0.1~1 | 0.1 | 0.05~0.5 | 0.5~1 | 0.1~0.5 | 4 | ~1 | 0.1~0.5 | +| Noise figure (dB) | 15 | 10~15 | [10-16] | 15 | 12 | 15 | 12~15 | 15 | ~15 | 12 | + +#### 7.1.1a.2 FSK + +##### 7.1.1a.2.1 Parallel RF envelope detection + +For FSK with parallel RF envelope detection, some sources ([7A-1] [7A-4]) provided analysis, with relative power consumption and noise figure summarized in Table 7.1.1a-4. + +**Table 7.1.1a-4: Relative power consumption and noise figure for FSK with parallel RF envelope detection** + +| Source reference | [7A-1] | [7A-4] | +|------------------------------|---------------------------------------------------------|--------| +| Power consumption (ON state) | 0.05 for single-branch, 0.01 for each additional branch | 0.01 | +| Noise figure (dB) | 20 | 20 | + +##### 7.1.1a.2.2 Parallel heterodyne architecture + +For FSK with parallel heterodyne architecture, some sources ([7A-1] [7A-2] [7A-3] [7A-4]) provided analysis, with relative power consumption and noise figure summarized in Table 7.1.1a-5. + +- The relative power consumption for ON state is in the range of 0.1~1. +- The noise figure is in the range of 9~15 dB. + +**Table 7.1.1a-5: Relative power consumption and noise figure for FSK with parallel heterodyne architecture** + +| | | | | | +|------------------------------|--------------------------------------------------------|--------|--------|--------| +| Source reference | [7A-1] | [7A-2] | [7A-3] | [7A-4] | +| Power consumption (ON state) | 0.1 for single-branch, 0.01 for each additional branch | 0.5 | 0.1~1 | 0.1 | +| Noise figure (dB) | 15 | 10~15 | [9~15] | 15 | + +##### 7.1.1a.2.3 Parallel homodyne architecture + +For FSK with parallel homodyne architecture, some sources ([7A-1] [7A-2] [7A-3] [7A-4]) provided analysis, with relative power consumption and noise figure summarized in Table 7.1.1a-6. + +- The relative power consumption for ON state is in the range of 0.1~1. +- The noise figure is in the range of 10~16 dB. + +**Table 7.1.1a-6: Relative power consumption and noise figure for FSK with parallel homodyne architecture** + +| | | | | | +|------------------------------|-----------------------------------------------------------------|--------|---------|--------| +| Source reference | [7A-1] | [7A-2] | [7A-3] | [7A-4] | +| Power consumption (ON state) | 0.09 for single-branch, 0.01 or 0.02 for each additional branch | 0.5 | 0.1~1 | 0.1 | +| Noise figure (dB) | 15 | 10~15 | [10~16] | 15 | + +##### 7.1.1a.2.4 Heterodyne architecture with frequency to amplitude conversion + +For FSK with heterodyne architecture with frequency to amplitude conversion, some sources ([7A-1] [7A-3]) provided analysis, with relative power consumption and noise figure summarized in Table 7.1.1a-7. + +**Table 7.1.1a-7: Relative power consumption and noise figure for FSK with heterodyne architecture with frequency to amplitude conversion** + +| | | | +|------------------------------|---------------------|--------| +| Source reference | [7A-1] (for SC-FSK) | [7A-3] | +| Power consumption (ON state) | 0.1 | 1 | +| Noise figure (dB) | 15 | TBD | + +##### 7.1.1a.2.5 Homodyne architecture with frequency to amplitude conversion + +For FSK with homodyne architecture with frequency to amplitude conversion, 1 source ([7A-1]) estimated that for SC-FSK, the relative power consumption for ON state is 0.1, and the noise figure is 15dB. + +#### 7.1.1a.3 OFDMA-based signal + +For OFDMA-based signal, companies have considered sequence-based signal, where the LP WUR performs either time-domain correlation without FFT or frequency-domain correlation after FFT. + +##### 7.1.1a.3.1 Time-domain correlation (without FFT) + +For OFDM-based signal with time-domain correlation, some sources ([7A-1] [7A-3] [7A-5] [7A-6] [7A-7] [7A-8] [7A-9]) provided analysis, with relative power consumption and noise figure summarized in Table 7.1.1a-8. + +- The relative power consumption for ON state is in the range of 0.15~30. +- The noise figure is in the range of 7~25 dB. + +**Table 7.1.1a-8: Relative power consumption and noise figure for OFDM-based signal with time-domain correlation** + +| Source reference | [7A-1] | [7A-3] | [7A-5] | [7A-6] | [7A-7] | [7A-8] | [7A-9] | +|------------------------------|----------|--------|-----------|--------|--------|--------|--------| +| Power consumption (ON state) | 0.15~0.2 | 10 | 10~20 | 10~30 | 1~5 | 10~20 | ~5 | +| Noise figure (dB) | 15 | 9.5 | 9.5 or 12 | 9 | 7~10 | 9 | 15~25 | + +##### 7.1.1a.3.2 Frequency-domain correlation (with FFT) + +For OFDM-based signal with frequency-domain correlation, some sources ([7A-2] [7A-3] [7A-5] [7A-7] [7A-10]) provided analysis, with relative power consumption and noise figure summarized in Table 7.1.1a-9. + +- The relative power consumption for ON state is in the range of 1~30. +- The noise figure is in the range of 7~12 dB. + +**Table 7.1.1a-9: Relative power consumption and noise figure for OFDM-based signal with frequency-domain correlation** + +| Source reference | [7A-2] | [7A-3] | [7A-5] | [7A-7] | [7A-10] | [7A-10] | +|------------------------------|--------|--------|-----------|--------|---------|---------| +| Power consumption (ON state) | 10 | 30 | 20~30 | 1~5 | 10 | 4 | +| Noise figure (dB) | 7~12 | 7 | 9.5 or 12 | 7~10 | 9 | 12 | + +### 7.1.2 RAN4 studies of the receiver + +#### 7.1.2.1 General + +This Clause captures the study outcome of LP-WUR RF impacts. RAN4 focus on FR1 frequency ranges as first priority, 2.6GHz is selected as an example band for evaluation purpose. + +For evaluation purpose, RAN4 defines a new term named as guard RB for LP-WUS, which is Granularity of RB for ACS/ASCS protection. Meanwhile, the traditional guardband for NR channel bandwidth defined in Clause 5.3, TS 38.101-1 is unchanged. The LP-WUS guard RB definition can be described differently for ASCS and ACS as following: + +- For ASCS guard RB, the required guard RB(s) should be blanked RB(s), which belong to WUS carrier/BW (i.e., WUS signal plus ASCS guard RB(s)) +- For ACS guard RB, the required guard RB(s) are RB(s) between WUS signal edge and nearest edge of guardband of channel bandwidth + - It includes ASCS guard RB(s) (if allocated) and RBs (which could be blanked RBs or RBs used for NR transmission) between WUS carrier/BW edge and nearest edge of guardband of channel bandwidth as defined in spec TS 38.101-1 + +RAN4 agrees there is no need to restrict symmetric guard RBs for interference rejection of WUS, both ACS and ASCS. + +RAN4 suggests overall bandwidth of the wake-up signal in the NR channel i.e., desired signal along with all the required guard RBs shall fit in the maximum transmission bandwidth configuration as defined in Table 5.3.2-1 of TS 38.101-1. + +![Diagram of UE channel bandwidth configuration for case 1: LP-WUS within large channel. It shows a wide channel with a central WUS signal flanked by NR and blanked RBs, with guard RBs for ACS protection at the edges.](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +The diagram illustrates the frequency domain representation of a UE channel. The total UE channel BW is approximately 20/100MHz. Within this, the Transmission Bandwidth Configuration $N_{RB}$ is shown. A central WUS carrier/BW contains the WUS signal. To the left of the WUS signal is an NR signal block, and to the right is a block of RBs (NR or blanked RB). Guard RBs for ACS protection are indicated between the WUS signal and the NR/blanked RB blocks. A legend indicates that a white rectangle represents the Guardband of UE channel. + +Diagram of UE channel bandwidth configuration for case 1: LP-WUS within large channel. It shows a wide channel with a central WUS signal flanked by NR and blanked RBs, with guard RBs for ACS protection at the edges. + +(case 1: LP-WUS within large channel) + +![Diagram of UE channel bandwidth configuration for case 2: WUS within narrow channel. It shows a narrower channel where the WUS signal and its associated guard RBs take up a significant portion of the total channel bandwidth.](fcbc3c31776721edc98ceb1944ec438f_img.jpg) + +This diagram shows a narrower UE channel BW. The Transmission Bandwidth Configuration is smaller than in case 1. The WUS carrier/BW and the WUS signal are more prominent. The channel is divided into RBs (NR or blanked RB) on the left and right of the WUS signal. Guard RBs for ACS protection are shown. The same legend for the Guardband of UE channel is included. + +Diagram of UE channel bandwidth configuration for case 2: WUS within narrow channel. It shows a narrower channel where the WUS signal and its associated guard RBs take up a significant portion of the total channel bandwidth. + +(case 2: WUS within narrow channel, WUS bandwidth is comparable with channel bandwidth) + +Figure 7.1.2.1-1: Definition of the guardband of NR channel and guard RBs for both LP-WUS ACS and ASCS + +#### 7.1.2.2 ACS evaluation + +Adjacent channel selectivity (ACS) is a measure of a receiver's ability to receive an NR signal at its assigned channel frequency in the presence of an adjacent channel signal at a given frequency offset from the centre frequency of the assigned channel. ACS is the ratio of the receive filter attenuation on the assigned channel frequency to the receive filter attenuation on the adjacent channel(s). + +In general, NR ACS requirement is derived based on co-existence study to meet max 5% throughput loss metric. While for LP-WUS, the purpose in the study of ACS is not for justification of co-existence between contained LP-WUS and adjacent NR carrier, but to evaluate the required guard RBs in-between the different signals. Given the WUS waveform would be different from NR signal, the traditional throughput loss metric can not be reused. Therefore, RAN4 agrees to focus on the evaluation of required guard RB rather than ACS requirements with co-existence simulation. + +Framework in RAN4 to evaluate ACS and ASCS vs guard RBs: + +- ACS and ASCS guard RB can be evaluated based on the following aspects: + - Typical filter characteristic, e.g., filter order, pass BW, cut-off frequency + - Guard RB size + +- RF impairment can also be considered +- RAN4 adopts two approaches for guard RB evaluation, i.e., filter suppression level analysis and link level simulation +- Averaged power attenuation at ACS or ASCS frequency range +- FFS whether SINR of the wanted signal at detector input is needed +- FFS whether to use ICS instead of ASCS +- FFS Coexistence-simulation-based framework can also be considered + - FFS on details of coexistence study (if needed) of LP-WUS + - Coverage should be considered + +RAN4 Considers a limited set of LP-WUS scenarios for study purpose in RAN4, as shown in Table 7.1.2.2-1. + +**Table 7.1.2.2-1: Common LP-WUS evaluation parameters for ACS** + +| | | +|------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| NR RF channel BW | 20MHz/100MHz for 5MHz WUS | +| Guardband of NR channel | Unchanged, defined in Clause 5.3.3 in TS 38.101-1.
810kHz for wanted cell1 20MHz (5MHz WUS at edge), and
510kHz for interference cell2 5MHz. | +| WUS BW within NR channel | Max 5.04 MHz | +| WUS RB allocation (Note 1) | 24 RB (15kHz SCS) or 12 RB (30kHz SCS) within 5.04 MHz; | +| WUS placement within NR channel | Edge of channel, i.e., close to guardband | +| Guard RB size of LP-WUS | 0 RB, 0.5RB, 1RB, 2RB, 3RB | +| ACS interferer (cell 2) | 5MHz with guardband | +| Filter characteristic | 2nd to 5th order Butterworth
lowpass@ baseband
bandpass@100 MHz
bandpass@2.6 GHz | +| Filter passband BW | Same as WUS bandwidth (number of RBs) | +| Target ACS | TBD; reuse NR value as starting point | +| Target WUS SNR | TBD | +| WUS SNR condition | TBD | +| NR power level | TBD | +| RF impairment | Max. Center frequency offset based on companies report | +| Note 1: For easy evaluation, the number of allocated WUS RBs is fixed. The number of Guard RBs is changed. | | + +The frequency response of 2nd to 5th order Butterworth filters are shown as below: + +![Four plots showing the frequency response of 2nd, 3rd, 4th, and 5th order Butterworth filters. Each plot shows Magnitude (dB) on the y-axis and Frequency (MHz) on the x-axis (90 to 110 MHz). The 2nd order filter has a flat response at 0 dB between 98 and 102 MHz. Higher order filters show steeper roll-offs outside the passband. The 5th order filter reaches -70 dB at 90 MHz and 110 MHz.](771c18f874d31c59c3b8c4e247be16ca_img.jpg) + +Four plots showing the frequency response of 2nd, 3rd, 4th, and 5th order Butterworth filters. Each plot shows Magnitude (dB) on the y-axis and Frequency (MHz) on the x-axis (90 to 110 MHz). The 2nd order filter has a flat response at 0 dB between 98 and 102 MHz. Higher order filters show steeper roll-offs outside the passband. The 5th order filter reaches -70 dB at 90 MHz and 110 MHz. + +Figure 7.1.2.2-1: Frequency response of Butterworth filters + +For ACS guard RB evaluation, RAN4 focuses on the LP-WUS at the edge of NR channel case, as shown in Figure 7.1.2.2-2. + +![Diagram of LP-WUS at the edge of NR channel. It shows two NR cells (NR cell 1 and NR cell 2) with a 20/100MHz spacing. NR cell 1 contains an NR signal and a WUS 24RBs block. NR cell 2 contains an NR signal and a 5MHz BW_interferer. Guardbands are shown between the NR signals and the WUS/interferer blocks. Labels include 'NR cell 1 20/100MHz', 'NR cell 2', 'NR', 'WUS 24RBs', '5MHz BW_interferer', 'ASCS Guard RBs', and 'ACS Guard RBs'. A legend indicates: Required Guard RBs for WUS (shaded), Guardband of NR cell 1 (white), and Guardband of NR cell 2 (white).](5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg) + +Diagram of LP-WUS at the edge of NR channel. It shows two NR cells (NR cell 1 and NR cell 2) with a 20/100MHz spacing. NR cell 1 contains an NR signal and a WUS 24RBs block. NR cell 2 contains an NR signal and a 5MHz BW\_interferer. Guardbands are shown between the NR signals and the WUS/interferer blocks. Labels include 'NR cell 1 20/100MHz', 'NR cell 2', 'NR', 'WUS 24RBs', '5MHz BW\_interferer', 'ASCS Guard RBs', and 'ACS Guard RBs'. A legend indicates: Required Guard RBs for WUS (shaded), Guardband of NR cell 1 (white), and Guardband of NR cell 2 (white). + +Figure 7.1.2.2-2: LP-WUS at the edge of NR channel + +##### **Conclusions for RAN4 ACS guard RB analysis:** + +Based on the analysis above, RAN4 observed that for 5th order filter, the guard RB number for LP-WUS ACS is in the range of 1RB ~ 6RBs for 30kHz SCS, or 2RBs ~12RBs for 15kHz SCS. For lower power, i.e., lower order filters, the required guard RBs may increase. There is no recommendation on which filter order should be considered to the baseline in SI phase. + +- As the analysis from companies did not comprehensively consider all impairments, and individual results are missing the impact of one or many of the following: phase noise, non-linearity, frequency error, implementation margin. For the evaluation, companies have used OOK waveform and FSK waveform, other type of WUS signals are not used. Final conclusion on the number of guard RB is left to WI discussion. + +Companies' input on simulation analysis of ACS have been presented as following: + +###### **Filter suppression level analysis:** + +For filter suppression level calculation, the suppression level is calculated with averaged power attenuation at ACS frequency range. + +[7B-1] + +The parameter assumption is aligned with that in Table 7.1.2.2-1. The required guard RB is provided in the Table 7.1.2.2-2 below. CFO from 0ppm~200ppm is considered as RF impairment impacts. + +**Table 7.1.2.2-2: Required number of guard RBs for 5MHz ACS** + +| Filter order | Guard RB CBW | Frequency Offset | ACS, BW interference = 5MHz | | | | | +|-----------------|---------------------|------------------|----------------------------------------|--------|--------|--------|--------| +| | | | 0RB | 0.5RB | 1RB | 2RB | 3RB | +| 5 th | 20MHz, SCS = 15kHz | 0 ppm | -28.20 | -29.51 | -30.37 | -32.43 | -34.40 | +| | | 5 ppm | -27.95 | -29.26 | -30.11 | -32.18 | -34.14 | +| | | 10 ppm | -27.69 | -29.01 | -29.86 | -31.92 | -33.88 | +| | | 50 ppm | -25.73 | -27.02 | -27.87 | -29.92 | -31.87 | +| | | 200 ppm | -19.35 | -20.52 | -21.31 | -23.24 | -25.13 | +| | 100MHz, SCS = 30kHz | 0 ppm | -34.51 | -36.33 | -38.07 | -41.33 | -44.33 | +| | | 5 ppm | -34.25 | -36.07 | -37.81 | -41.07 | -44.07 | +| | | 10 ppm | -33.99 | -35.81 | -37.55 | -40.81 | -43.81 | +| | | 50 ppm | -31.97 | -35.53 | -33.79 | -38.79 | -41.79 | +| | | 200 ppm | -25.21 | -27.00 | -28.72 | -31.97 | -34.97 | +| 4 th | 20MHz, SCS = 15kHz | 0 ppm | -23.71 | -24.70 | -25.35 | -26.92 | -28.42 | +| | | 5 ppm | -23.51 | -24.50 | -25.15 | -26.72 | -28.22 | +| | | 10 ppm | -23.31 | -24.30 | -24.94 | -26.51 | -28.01 | +| | | 50 ppm | -21.75 | -22.73 | -23.37 | -24.92 | -26.41 | +| | | 200 ppm | -16.73 | -17.61 | -18.20 | -19.65 | -21.08 | +| | 100MHz, SCS = 30kHz | 0 ppm | -28.35 | -29.76 | -31.11 | -33.64 | -35.97 | +| | | 5 ppm | -28.14 | -29.55 | -30.90 | -33.43 | -35.77 | +| | | 10 ppm | -27.94 | -29.34 | -30.69 | -33.22 | -35.56 | +| | | 50 ppm | -26.34 | -27.74 | -29.08 | -31.61 | -33.95 | +| | | 200 ppm | -20.98 | -22.34 | -23.67 | -26.17 | -28.50 | +| 3 rd | 20MHz, SCS = 15kHz | 0 ppm | -18.80 | -19.49 | -19.94 | -21.04 | -22.10 | +| | | 5 ppm | -18.65 | -19.34 | -19.79 | -20.89 | -21.94 | +| | | 10 ppm | -18.50 | -19.19 | -19.64 | -20.74 | -21.79 | +| | | 50 ppm | -17.36 | -18.04 | -18.48 | -19.56 | -20.61 | +| | | 200 ppm | -13.68 | -14.29 | -14.69 | -15.70 | -16.69 | +| | 100MHz, SCS = 30kHz | 0 ppm | -21.90 | -22.90 | -23.87 | -25.70 | -27.39 | +| | | 5 ppm | -21.75 | -22.75 | -23.72 | -25.54 | -27.24 | +| | | 10 ppm | -21.59 | -22.60 | -23.56 | -25.39 | -27.09 | +| | | 50 ppm | -20.41 | -21.41 | -22.37 | -24.19 | -25.88 | +| | | 200 ppm | -16.46 | -17.43 | -18.36 | -20.14 | -21.82 | +| 2 nd | 20MHz, SCS = 15kHz | 0 ppm | -13.43 | -13.84 | -14.11 | -14.77 | -15.41 | +| | | 5 ppm | -13.34 | -13.75 | -14.02 | -14.68 | -15.31 | +| | | 10 ppm | -13.25 | -13.65 | -13.92 | -14.58 | -15.22 | +| | | 50 ppm | -12.52 | -12.92 | -13.18 | -13.83 | -14.45 | +| | | 200 ppm | -10.16 | -10.53 | -10.77 | -11.36 | -11.95 | +| | 100MHz, SCS = 30kHz | 0 ppm | -15.18 | -15.80 | -16.40 | -17.54 | -18.62 | +| | | 5 ppm | -15.08 | -15.70 | -16.30 | -17.44 | -18.52 | +| | | 10 ppm | -14.98 | -15.60 | -16.20 | -17.34 | -18.41 | +| | | 50 ppm | -14.22 | -14.83 | -15.42 | -16.56 | -17.62 | +| | | 200 ppm | -11.70 | -12.28 | -12.85 | -13.94 | -14.98 | + +[7B-2] + +The evaluation parameters are listed in Table 7.1.2.2-3 below. + +**Table 7.1.2.2-3: Evaluation assumptions.** + +| | | +|------------------------|-------------| +| WUS signal bandwidth | 4.32 MHz | +| Interferer power level | 0 dBc | +| F0 | 2.6 GHz | +| Filter Type | Butterworth | + +**Table 7.1.2.2-4: Guard required in kHz for a target interference level of -10 dBc.** + +| CFO | Filter order | | | | | +|-----------|--------------|--------|--------|-------|-------| +| | 1 | 2 | 3 | 4 | 5 | +| ± 0 ppm | 4320.0 | 1598.4 | 972.0 | 691.2 | 540 | +| ± 5 ppm | 4346.0 | 1608.0 | 977.9 | 695.4 | 543.3 | +| ± 50 ppm | 4580.0 | 1694.6 | 1030.5 | 732.8 | 572.5 | +| ± 100 ppm | 4840.0 | 1790.8 | 1089.0 | 774.4 | 605.0 | +| ± 200 ppm | 5360.0 | 1983.2 | 1206.0 | 857.6 | 670.0 | + +Based on the results in Table 7.1.2.2-4, it is suggested that for 5th order filter, the guard RB number for LP-WUS can be 2RBs for 30kHz SCS, or 3RBs ~ 4RBs for 15kHz SCS. + +[7B-3] + +Following list our filter evaluation analysis assumption. + +**Table 7.1.2.2-5: LP-WUS evaluation scenarios** + +| | | +|---------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NR RF channel BW | 20MHz/100MHz for 5MHz WUS | +| Guardband of NR channel | Unchanged, defined in Clause 5.3.3 in TS 38.101-1, i.e.
For 15kHz SCS, 242.5kHz guardband for 5MHz CBW and 452.5kHz guard band for 20MHz CBW
For 30kHz SCS, 505kHz guardband for 5MHz CBW and 845kHz guard band for 100MHz CBW | +| WUS BW within NR channel | 5.04 MHz | +| WUS RB allocation (Note 1) | 24 RB, i.e. total 4.32MHz | +| WUS placement within NR channel | Carrier edge for ACS and carrier center for ASCS | +| Guard RB size of LP-WUS | 0 RB, 0.5 RF, 1RB, 2RBs, 3RB at each side.
Only symmetric guard RB has been considered | +| ACS interferer | 5MHz | +| Filter characteristic | 2 nd and 5 th order Butterworth
Both analog and digital filter can be considered | +| Filter passband BW | 4.32/2=2.16MHz for low-pass filter
4.32MHz for band-pass filter | + +Following list the S21 of 2nd and 5th order butterworth filters and related parameters. + +![Figure 7.1.2.2-3: Frequency response of 2nd Butterworth filters. The graph shows two curves: a blue curve for S21 (dB) and a pink curve for S11 (dB). The x-axis represents Frequency (Hz) from 40M to 70M. The y-axis for S21 ranges from -80 to 0 dB, and for S11 from -40 to 0 dB. The S21 curve has a sharp peak at 50M Hz, while the S11 curve has a sharp dip at the same frequency.](516d9f1866cc2e359a35fb1d8c046454_img.jpg) + +Figure 7.1.2.2-3: Frequency response of 2nd Butterworth filters. The graph shows two curves: a blue curve for S21 (dB) and a pink curve for S11 (dB). The x-axis represents Frequency (Hz) from 40M to 70M. The y-axis for S21 ranges from -80 to 0 dB, and for S11 from -40 to 0 dB. The S21 curve has a sharp peak at 50M Hz, while the S11 curve has a sharp dip at the same frequency. + +Figure 7.1.2.2-3: Frequency response of 2nd Butterworth filters + +![Figure 7.1.2.2-4: Frequency response of 5th Butterworth filters. Similar to Figure 7.1.2.2-3, this graph shows S21 (blue) and S11 (pink) curves. The S21 curve at 50M Hz is broader and flatter than in the 2nd order filter, indicating a wider passband. The S11 curve shows a less sharp dip at 50M Hz.](74448f9178da618d823e5a5dadc56fb5_img.jpg) + +Figure 7.1.2.2-4: Frequency response of 5th Butterworth filters. Similar to Figure 7.1.2.2-3, this graph shows S21 (blue) and S11 (pink) curves. The S21 curve at 50M Hz is broader and flatter than in the 2nd order filter, indicating a wider passband. The S11 curve shows a less sharp dip at 50M Hz. + +Figure 7.1.2.2-4: Frequency response of 5th Butterworth filters + +Following table list ACS value based on low-pass filter for zero-IF envelop detector architecture, in which pass bandwidth is $4.32/2=2.16\text{MHz}$ . + +Table 7.1.2.2-6: Evaluated ACS based on low-pass filter with 2.16MHz pass bandwidth + +| Filter order | Guard RB CBW | Frequency Offset | ACS, $BW_{\text{interference}} = 5\text{MHz}$ | | | | | +|-----------------|---------------------|------------------|-----------------------------------------------|--------------|------------|------------|------------| +| | | | 0RB/30kSCS | 0.5RB/30kSCS | 1RB/30kSCS | 2RB/30kSCS | 3RB/30kSCS | +| 5 th | 20MHz, SCS = 15kHz | 0 ppm | -27.75 | -29.88 | -31.9 | -35.65 | -39.07 | +| | | 5 ppm | -27.6 | -29.73 | -31.76 | -35.52 | -38.95 | +| | | 10 ppm | -27.44 | -29.58 | -31.61 | -35.39 | -38.83 | +| | | 50 ppm | -26.15 | -28.35 | -30.45 | -34.34 | -37.87 | +| | | 200 ppm | -21.1 | -23.47 | -25.78 | -30.11 | -34.03 | +| | 100MHz, SCS = 30kHz | 0 ppm | -35.00 | -36.78 | -38.47 | -41.65 | -44.59 | +| | | 5 ppm | -34.87 | -36.65 | -38.35 | -41.54 | -44.49 | +| | | 10 ppm | -34.74 | -36.52 | -38.23 | -41.43 | -44.38 | +| | | 50 ppm | -33.66 | -35.5 | -37.25 | -40.53 | -43.55 | +| | | 200 ppm | -29.36 | -31.4 | -33.35 | -36.97 | -40.27 | +| 2 nd | 20MHz, SCS = 15kHz | 0 ppm | -12.62 | -13.28 | -13.93 | -15.18 | -16.34 | +| | | 5 ppm | -12.57 | -13.24 | -13.89 | -15.13 | -16.3 | +| | | 10 ppm | -12.52 | -13.19 | -13.84 | -15.09 | -16.26 | +| | | 50 ppm | -12.12 | -12.8 | -13.47 | -14.74 | -15.93 | +| | | 200 ppm | -10.59 | -11.3 | -12.01 | -13.36 | -14.63 | +| | 100MHz, SCS = | 0 ppm | -14.96 | -15.56 | -16.13 | -17.24 | -18.28 | + +| | | | | | | | | +|--|-------|---------|--------|--------|--------|--------|--------| +| | 30kHz | 5 ppm | -14.91 | -15.51 | -16.09 | -17.2 | -18.24 | +| | | 10 ppm | -14.87 | -15.47 | -16.05 | -17.16 | -18.21 | +| | | 50 ppm | -14.51 | -15.13 | -15.72 | -16.85 | -17.91 | +| | | 200 ppm | -13.12 | -13.77 | -14.41 | -15.62 | -16.76 | + +Following table is based on analog band-pass filter for RF/IF envelop detector architecture, in which pass bandwidth is 4.32MHz. + +**Table 7.1.2.2-7: Evaluated ACS based on analog band-pass filter with 4.32MHz pass bandwidth** + +| Filter order | Guard RB
CBW | Frequency
Offset | ACS, BW interference = 5MHz | | | | | +|-----------------|---------------------|---------------------|----------------------------------------|------------------|----------------|----------------|----------------| +| | | | 0RB/
30kSCS | 0.5RB/
30kSCS | 1RB/
30kSCS | 2RB/
30kSCS | 3RB/
30kSCS | +| 5 th | 20MHz, SCS = 15kHz | 0 ppm | -17.96 | -19.16 | -20.34 | -22.64 | -24.83 | +| | | 5 ppm | -17.88 | -19.08 | -20.26 | -22.56 | -24.75 | +| | | 10 ppm | -17.79 | -18.99 | -20.18 | -22.48 | -24.68 | +| | | 50 ppm | -17.09 | -18.3 | -19.49 | -21.82 | -24.05 | +| | | 200 ppm | -14.46 | -15.67 | -16.89 | -19.3 | -21.63 | +| | 100MHz, SCS = 30kHz | 0 ppm | -22.23 | -23.35 | -24.44 | -26.55 | -28.56 | +| | | 5 ppm | -22.15 | -23.27 | -24.36 | -26.47 | -28.49 | +| | | 10 ppm | -22.07 | -23.19 | -24.29 | -26.4 | -28.42 | +| | | 50 ppm | -21.41 | -22.54 | -23.66 | -25.8 | -27.84 | +| | | 200 ppm | -18.86 | -20.05 | -21.22 | -23.47 | -25.63 | +| 2 nd | 20MHz, SCS = 15kHz | 0 ppm | -8.18 | -8.56 | -8.94 | -9.7 | -10.43 | +| | | 5 ppm | -8.15 | -8.53 | -8.92 | -9.67 | -10.4 | +| | | 10 ppm | -8.12 | -8.51 | -8.89 | -9.64 | -10.38 | +| | | 50 ppm | -7.9 | -8.28 | -8.67 | -9.43 | -10.17 | +| | | 200 ppm | -7.05 | -7.44 | -7.83 | -8.6 | -9.36 | +| | 100MHz, SCS = 30kHz | 0 ppm | -9.56 | -9.93 | -10.3 | -11.02 | -11.72 | +| | | 5 ppm | -9.53 | -9.91 | -10.27 | -10.99 | -11.69 | +| | | 10 ppm | -9.51 | -9.88 | -10.25 | -10.97 | -11.67 | +| | | 50 ppm | -9.29 | -9.67 | -10.04 | -10.76 | -11.47 | +| | | 200 ppm | -8.47 | -8.85 | -9.23 | -9.97 | -10.7 | + +Less pass bandwidth will lead to better filter suppression capability, so table 7.1.2.2-6 with less pass bandwidth will have better performance. + +###### Link-level simulation analysis: + +[7B-1] + +The detailed parameters are listed in Table 7.1.2.2-8. + +**Table 7.1.2.2-8: LP-WUS ACS and ASCS simulation parameters** + +| Attributes | Assumptions | | | +|-------------------------------|---------------------------------------------------------------------------------------------------------------------------|---------------------------|--------------------------| +| Carrier Frequency | 2.6GHz | | | +| Case name | OOK-1 waveform | OOK-2 waveform | OOK-4 waveform | +| Channel structure | data: 6 bits CRC: 8 bits | data: 20 bits CRC: 8 bits | data: 20bits CRC: 8 bits | +| Chip rate | M=1 | M=2 | M=2 | +| WUS duration | 28 symbols | | | +| Waveform | OOK -1/OOK-2/OOK-4 | | | +| Coding | 1/2 rate Manchester coding | | | +| Time error | 0 | | | +| residual Frequency error | 0/10/20/50/22700 ppm(for ASCS evaluation) | | | +| SCS | 30kHz | | | +| gNB Channel BW | 20MHz (50 RB) | | | +| WUS BW | 12RB ~4.32MHz | | | +| Guardband of NR channel (ACS) | 27RE~810kHz for wanted cell1 20MHz (5MHz WUS at edge), and 510kHz for interference cell2 5MHz. | | | +| Guard RB | Outer GB:2/1/0.5RB on each side of LP-WUS bandwidth (2 RB for ACS)
Inner GB: 4RE between segments | | | +| Filter | 3th/5th Order lowpass Butterworth with 4.32MHz bandwidth
(2.1 MHz bandwidth for OOK-2 M=2) | | | +| ASCS | PDSCH mapped on RBs not used for LP-WUS and Guard RB;
EPRE of PDSCH /EPRE of LP-WUS = 0 dB
Same PSD with WUS signal | | | +| ACS | PDSCH mapped on RBs(14RB~5MHz), one side;
EPRE of PDSCH /EPRE of LP-WUS = 31.5 dB
31.5dB higher | | | +| Sampling Rate | 7.68MHz | | | +| ADC bit width | 4 bits ADC for ASCS, 8 bits ADC for ACS; | | | +| Phase noise | unable | | | +| Power boosting | 0dB for OOK-1/4
3dB for OOK-2 | | | +| Channel Model | TDL-C 300 | | | +| Performance metric | {FAR, MDR}: {1%, 1%} | | | + +The simulation results are in Figure 7.1.2.2-5 for ACS. + +![Three line graphs showing BLER vs SNR for 2.6G-w/ ACS-OOK-1, 2.6G-w/ ACS-OOK-2, and 2.6G-w/ ACS-OOK-4 with 8 bit ADC. Each graph compares different CFO and filter configurations.](c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg) + +The figure consists of three subplots, each showing the Bit Link Error Rate (BLER) on a logarithmic y-axis (from 10-3 to 100) against the Signal-to-Noise Ratio (SNR) on a linear x-axis (from -10 to 10). All three plots are for '2.6G-w/ ACS-OOK-X, 8 bit ADC' where X is 1, 2, or 4. + +Each plot contains six data series representing different Carrier Frequency Offset (CFO) and filter settings: + + +- CFO=0ppm-GB =810+510+180kHz-3rd order filter (green dashed line with triangles) +- CFO=0ppm-GB =810+510+180kHz-5th order filter (green dotted line with circles) +- CFO=0ppm-GB =810+510+360kHz-3rd order filter (red dashed line with triangles) +- CFO=0ppm-GB =810+510+360kHz-5th order filter (red dotted line with circles) +- CFO=0ppm-GB =810+510+720kHz-3rd order filter (blue dashed line with triangles) +- CFO=0ppm-GB =810+510+720kHz-5th order filter (blue dotted line with circles) + +In the OOK-1 plot, all series show a steep decrease in BLER as SNR increases, reaching 10-3 around SNR=4. In the OOK-2 plot, the 5th order filter series (dotted lines) continue to decrease until SNR=6, while the 3rd order filter series (dashed lines) reach an error floor. In the OOK-4 plot, the 5th order filter series reach an error floor around SNR=2 to 4, while the 3rd order filter series remain at a high BLER floor (around 10-1). + +Three line graphs showing BLER vs SNR for 2.6G-w/ ACS-OOK-1, 2.6G-w/ ACS-OOK-2, and 2.6G-w/ ACS-OOK-4 with 8 bit ADC. Each graph compares different CFO and filter configurations. + +Figure 7.1.2.2-5: ACS guard RB evaluation + +It can be observed that 1 RB of 30kHz SCS with 5th order filtering is sufficient for OOK-1, OOK-2, and OOK-4 LP-WUS. + +[7B-4] + +The 5MHz interferer is 31.5dB higher than the wanted signal for ACS simulation. Simulations for the waveforms in Figure 7.1.2.2-6 have been performed. + +![Figure 7.1.2.2-6: Some of the LP-WUS waveform options. The diagram shows five options: Option OOK-1, Option OOK-2, Option OOK-4, Option FSK-1, and Option FSK-2. Each option shows a frequency spectrum with Legacy NR signals at the edges and LPWUS segments in the center. Option OOK-1 has a single LPWUS segment. Option OOK-2 has four LPWUS segments (seg0 to seg3) with inner guard bands. Option OOK-4 has a single LPWUS segment with dashed lines representing time domain segment boundaries. Option FSK-1 has two segment pairs (pair0 and pair1) with inner guard bands. Option FSK-2 has four LPWUS segments (seg0 to seg3) with inner guard bands. Guard bands are indicated at the top and bottom of each spectrum.](8e80de0cac529b2c3775d677c5203133_img.jpg) + +Figure 7.1.2.2-6: Some of the LP-WUS waveform options. The diagram shows five options: Option OOK-1, Option OOK-2, Option OOK-4, Option FSK-1, and Option FSK-2. Each option shows a frequency spectrum with Legacy NR signals at the edges and LPWUS segments in the center. Option OOK-1 has a single LPWUS segment. Option OOK-2 has four LPWUS segments (seg0 to seg3) with inner guard bands. Option OOK-4 has a single LPWUS segment with dashed lines representing time domain segment boundaries. Option FSK-1 has two segment pairs (pair0 and pair1) with inner guard bands. Option FSK-2 has four LPWUS segments (seg0 to seg3) with inner guard bands. Guard bands are indicated at the top and bottom of each spectrum. + +Figure 7.1.2.2-6: Some of the LP-WUS waveform options + +For waveform options of OOK-2, FSK-1 and FSK-2, since segmented RB allocations are considered, several narrower filters would be needed to filter out the interference in contrast to a single filter used for OOK-1 and OOK-4. + +Figure 7.1.2.2-7 shows the simulation results for the aforementioned waveforms. + +![Graph a) Guard RB evaluation of OOK-1. The y-axis is BLER (log scale from 10^-3 to 10^0) and the x-axis is SNR [dB] (from -8 to 3). Four curves are shown: 'No ACI' (solid line with circles), 'ACI GB=510kHz' (dashed line with circles), 'ACI GB=510+360kHz' (dashed line with crosses), and 'ACI GB=510+360x2 kHz' (dashed line with squares). The 'No ACI' curve shows the best performance, while the 'ACI GB=510+360x2 kHz' curve shows the worst performance.](4bff5f22997753bcf1997c715118012d_img.jpg) + +Graph a) Guard RB evaluation of OOK-1. The y-axis is BLER (log scale from 10^-3 to 10^0) and the x-axis is SNR [dB] (from -8 to 3). Four curves are shown: 'No ACI' (solid line with circles), 'ACI GB=510kHz' (dashed line with circles), 'ACI GB=510+360kHz' (dashed line with crosses), and 'ACI GB=510+360x2 kHz' (dashed line with squares). The 'No ACI' curve shows the best performance, while the 'ACI GB=510+360x2 kHz' curve shows the worst performance. + +a) Guard RB evaluation of OOK-1 + +![Graph b) Guard RB evaluation of OOK-2. The y-axis is BLER (log scale from 10^-3 to 10^0) and the x-axis is SNR [dB] (from -8 to 3). Four curves are shown: 'No ACI' (solid line with circles), 'ACI GB=510kHz' (dashed line with circles), 'ACI GB=510+360kHz' (dashed line with crosses), and 'ACI GB=510+360x2 kHz' (dashed line with squares). The 'No ACI' curve shows the best performance, while the 'ACI GB=510+360x2 kHz' curve shows the worst performance.](37a96d647a34d2c514364514c7f85f41_img.jpg) + +Graph b) Guard RB evaluation of OOK-2. The y-axis is BLER (log scale from 10^-3 to 10^0) and the x-axis is SNR [dB] (from -8 to 3). Four curves are shown: 'No ACI' (solid line with circles), 'ACI GB=510kHz' (dashed line with circles), 'ACI GB=510+360kHz' (dashed line with crosses), and 'ACI GB=510+360x2 kHz' (dashed line with squares). The 'No ACI' curve shows the best performance, while the 'ACI GB=510+360x2 kHz' curve shows the worst performance. + +b) Guard RB evaluation of OOK-2 + +![Graph c) Guard RB evaluation of OOK-4. The y-axis is BLER (log scale from 10^-3 to 10^0) and the x-axis is SNR [dB] (from -8 to 3). Four curves are shown: 'No ACI' (solid line with circles), 'ACI GB=510kHz' (dashed line with circles), 'ACI GB=510+360kHz' (dashed line with crosses), and 'ACI GB=510+360x2 kHz' (dashed line with squares). The 'No ACI' curve shows the best performance, while the 'ACI GB=510+360x2 kHz' curve shows the worst performance.](1a09fb1ec1922a373a14bff45ebf433e_img.jpg) + +Graph c) Guard RB evaluation of OOK-4. The y-axis is BLER (log scale from 10^-3 to 10^0) and the x-axis is SNR [dB] (from -8 to 3). Four curves are shown: 'No ACI' (solid line with circles), 'ACI GB=510kHz' (dashed line with circles), 'ACI GB=510+360kHz' (dashed line with crosses), and 'ACI GB=510+360x2 kHz' (dashed line with squares). The 'No ACI' curve shows the best performance, while the 'ACI GB=510+360x2 kHz' curve shows the worst performance. + +c) Guard RB evaluation of OOK-4 + +![Graph d) Guard RB evaluation of FSK-1. The y-axis is BLER (log scale from 10^-3 to 10^0) and the x-axis is SNR [dB] (from -8 to 3). Four curves are shown: 'No ACI' (solid line with circles), 'ACI GB=510kHz' (dashed line with circles), 'ACI GB=510+360kHz' (dashed line with crosses), and 'ACI GB=510+360x2 kHz' (dashed line with squares). The 'No ACI' curve shows the best performance, while the 'ACI GB=510+360x2 kHz' curve shows the worst performance.](dd7579e21d9f956489a04e28c9d8abc0_img.jpg) + +Graph d) Guard RB evaluation of FSK-1. The y-axis is BLER (log scale from 10^-3 to 10^0) and the x-axis is SNR [dB] (from -8 to 3). Four curves are shown: 'No ACI' (solid line with circles), 'ACI GB=510kHz' (dashed line with circles), 'ACI GB=510+360kHz' (dashed line with crosses), and 'ACI GB=510+360x2 kHz' (dashed line with squares). The 'No ACI' curve shows the best performance, while the 'ACI GB=510+360x2 kHz' curve shows the worst performance. + +d) Guard RB evaluation of FSK-1 + +![Figure 7.1.2.2-7: ACS guard RB evaluation for several waveforms. A log-linear plot titled 'FSK2' showing BLER vs SNR [dB]. The y-axis (BLER) ranges from 10^-3 to 10^0. The x-axis (SNR [dB]) ranges from -8 to 3. Three curves are shown: 'No ACI' (blue line with circles), 'ACI GB=510kHz' (blue line with circles), and 'ACI GB=510+360kHz' (blue line with crosses). All curves show a steep decrease in BLER as SNR increases, with the 'No ACI' curve reaching BLER 10^-3 at approximately -4.5 dB SNR, and the other two curves reaching it at approximately -4.8 dB SNR.](068b3a3247570c4b78342a943f15de9e_img.jpg) + +Figure 7.1.2.2-7: ACS guard RB evaluation for several waveforms. A log-linear plot titled 'FSK2' showing BLER vs SNR [dB]. The y-axis (BLER) ranges from 10^-3 to 10^0. The x-axis (SNR [dB]) ranges from -8 to 3. Three curves are shown: 'No ACI' (blue line with circles), 'ACI GB=510kHz' (blue line with circles), and 'ACI GB=510+360kHz' (blue line with crosses). All curves show a steep decrease in BLER as SNR increases, with the 'No ACI' curve reaching BLER 10^-3 at approximately -4.5 dB SNR, and the other two curves reaching it at approximately -4.8 dB SNR. + +e) Guard RB evaluation of FSK-2 + +Figure 7.1.2.2-7: ACS guard RB evaluation for several waveforms + +For the evaluated waveform options of OOK-1, OOK-2, OOK-4, FSK-1 and FSK-2, guard RB with the size of one 30kHz SCS RB could provide necessary protection of LP-WUS from interference of adjacent NR carrier. For 5th order Butterworth filter assumption, it is proposed to reserve 1 RB for 30kHz SCS or 2RBs for 15kHz SCS for protection of LP-WUS from interference of the adjacent NR carrier. + +[7B-5], [7B-6] + +Simulations were done to evaluate the impact of adjacent channel and adjacent subcarrier interference. The simulation configuration was created closely match with existing RAN4 minimum requirement for adjacent channel selectivity. Minor adaptations needed to be done as 30 kHz SCS was used. The details of the simulation configuration are provided in Table 7.1.2.2-9. + +Table 7.1.2.2-9: Simulation configuration + +| | | +|----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NR system BW | 20 MHz | +| Subcarrier spacing | 30 kHz | +| Guardband of NR channel | 810 kHz | +| WUS BW within NR channel | 12 RB = 4.32 MHz | +| WUS signal | OOK-4 | +| Guard RB size of LP-WUS | 0 or 1 RB. GB is placed outside of the 12 RB carrying WUS | +| WUS placement within NR channel | 1) Immediately adjacent to system BW edge, NR channel GB is respected
2) Additional 3RB = 1.08 MHz offset from system BW edge compared to case 1)
3) Additional 6 RB = 2.16 MHz offset from system BW edge compared to case 1
4) Additional 12 RB = 4.32 offset from system BW edge compared to case 1
NOTE: Together with 1 RB GB, total offset from system BW edge to first WUS RB is reported offset + 360 kHz | +| ACS interferer signal | 12 RB = 4.32 MHz, center of interferer 2.52 MHz offset from system BW channel edge | +| ACS interferer signal level | Relative difference to signals within system BW aligned with Table 7.5-3 in TS 38.101-1 for 20 MHz channel bandwidth | +| Adjacent subcarrier interference | Except for the Guard RB size of LP-WUS of 0 or 1 RB, all subcarriers within system BW carry OFDM QPSK data | +| Filter characteristic | 2 nd to 5 th order Butterworth | +| Filter passband BW (-3 dB) | 4.32 MHz
5 MHz
6 MHz | +| LO frequency | In the middle of WUS | +| Frequency error | 0, 50, 100 ppm | +| Phase noise | Not modelled | + +| | | +|----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Non-linearities | Not modelled | +| Channel model | TDL-C 300 ns | +| NR system BW | 20 MHz | +| Subcarrier spacing | 30 kHz | +| Guardband of NR channel | 810 kHz | +| WUS BW within NR channel | 12 RB = 4.32 MHz | +| WUS signal | OOK-4 | +| Guard RB size of LP-WUS | 0 or 1 RB. GB is placed outside of the 12 RB carrying WUS | +| WUS placement within NR channel | Immediately adjacent to system BW edge, NR channel GB is respected
Additional 3RB = 1.08 MHz offset from system BW edge compared to case 1)

NOTE: Together with 1 RB GB, total offset from system BW edge to first WUS RB is 4 RB = 1.44 MHz | +| ACS interferer signal | 12 RB = 4.32 MHz, center of interferer 2.52 MHz offset from system BW channel edge | +| ACS interferer signal level | Relative difference to signals within system BW aligned with Table 7.5-3 in TS 38.101-1 for 20 MHz channel bandwidth | +| Adjacent subcarrier interference | Except for the Guard RB size of LP-WUS of 0 or 1 RB, all subcarriers within system BW carry OFDM QPSK data | +| Filter characteristic | 2 nd to 5 th order Butterworth | +| Filter passband BW (-3 dB) | 4.32 MHz
5 MHz
6 MHz | +| LO frequency | In the middle of WUS | +| Frequency error | Not modelled | +| Phase noise | Not modelled | +| Non-linearities | Not modelled | +| Channel model | TDL-C 300 ns | + +Simulation results are also optimistic as no frequency error, phase noise or non-linearities were modelled. For filter passband BW 3 options were used. With the narrowest passband BW the filter already cuts into WUS with 3 dB attenuation at WUS edges. Wider bandwidths are used to model practical implementation imperfections as well as possibility of missing or simplified calibration for filter corner frequency. + +First an example of ACI impact and GB impact are presented in Figures 7.1.2.2-8 and 7.1.2.2-9. + +![Figure 7.1.2.2-8: Impact of ACI, 3rd order filter, 4.32 MHz filter BW, WUS at system BW edge with GB = 0 RB. The figure contains two plots. The left plot shows BER (Y-axis, log scale from 10^-4 to 10^0) vs SNR (dB) (X-axis, from -10 to 10). The right plot shows SINR (dB) (Y-axis, from -15 to 10) vs SNR (dB) (X-axis, from -10 to 10). Both plots compare 'ACI off' (blue line with circles) and 'ACI on' (orange line with diamonds). In the left plot, the 'ACI off' curve decreases sharply from BER ~10^-1 at -10 dB SNR to BER ~10^-4 at 5 dB SNR, while the 'ACI on' curve remains flat at BER ~10^-1. In the right plot, the 'ACI off' curve increases linearly from SINR ~-10 dB at -10 dB SNR to SINR ~8 dB at 10 dB SNR, while the 'ACI on' curve increases more slowly from SINR ~-12 dB at -10 dB SNR to SINR ~-2 dB at 10 dB SNR.](48fc91e19c1a9b6674b120fbdd89b203_img.jpg) + +Figure 7.1.2.2-8: Impact of ACI, 3rd order filter, 4.32 MHz filter BW, WUS at system BW edge with GB = 0 RB. The figure contains two plots. The left plot shows BER (Y-axis, log scale from 10^-4 to 10^0) vs SNR (dB) (X-axis, from -10 to 10). The right plot shows SINR (dB) (Y-axis, from -15 to 10) vs SNR (dB) (X-axis, from -10 to 10). Both plots compare 'ACI off' (blue line with circles) and 'ACI on' (orange line with diamonds). In the left plot, the 'ACI off' curve decreases sharply from BER ~10^-1 at -10 dB SNR to BER ~10^-4 at 5 dB SNR, while the 'ACI on' curve remains flat at BER ~10^-1. In the right plot, the 'ACI off' curve increases linearly from SINR ~-10 dB at -10 dB SNR to SINR ~8 dB at 10 dB SNR, while the 'ACI on' curve increases more slowly from SINR ~-12 dB at -10 dB SNR to SINR ~-2 dB at 10 dB SNR. + +**Figure 7.1.2.2-8: Impact of ACI, 3rd order filter, 4.32 MHz filter BW, WUS at system BW edge with GB = 0 RB** + +![Two plots showing the impact of guard band (GB) on BER and SINR. The left plot shows BER vs SNR(dB) for GB off and GB on. The right plot shows SINR(dB) vs SNR(dB) for GB off and GB on.](70ececdbb871824c3e57cace6262c4d6_img.jpg) + +The figure contains two plots. The left plot shows the Bit Error Rate (BER) on a logarithmic y-axis (from 10-4 to 100) against the Signal-to-Noise Ratio (SNR) in dB on the x-axis (from -10 to 10). Two curves are shown: 'GB off' (blue line with diamond markers) and 'GB on' (orange line with diamond markers). Both curves are nearly horizontal, starting at a BER of approximately 0.3 at -10 dB SNR and slightly decreasing to about 0.2 at 10 dB SNR. The right plot shows the Signal-to-Interference-plus-Noise Ratio (SINR) in dB on the y-axis (from -14 to -6) against the SNR in dB on the x-axis (from -10 to 10). Two curves are shown: 'GB off' (blue line with diamond markers) and 'GB on' (orange line with diamond markers). Both curves start at approximately -14 dB at -10 dB SNR and increase as SNR increases. The 'GB on' curve increases more rapidly, reaching about -6.5 dB at 10 dB SNR, while the 'GB off' curve reaches about -9.5 dB at 10 dB SNR. + +Two plots showing the impact of guard band (GB) on BER and SINR. The left plot shows BER vs SNR(dB) for GB off and GB on. The right plot shows SINR(dB) vs SNR(dB) for GB off and GB on. + +**Figure 7.1.2.2-9: Impact of GB, 3rd order filter, 4.32 MHz filter BW, WUS at system BW edge with GBoff meaning GB = 0RB and with GBon meaning 1 RB GB. ACI is on for both curves.** + +It can be seen that for the chosen example scenario, adding ACI results in extremely poor BER. With no ACI present, there is clear relationship between SNR and BER. Whether guard band of 1 RB = 360 kHz is present or not does not change the results meaningfully. When looking at the SINR vs. SNR, the explanation is clear: when ACI is present, SINR never increase above -7 dB when SNR increases to 10 dB. + +Next results are presented for different filter bandwidths and filter orders when ACI is present in Figures 7.1.2.2-10 and 7.1.2.2-11. + +![Two plots showing BER vs SNR for different filter orders (2, 3, 4, 5) with ACI present. The left plot is for 4.32 MHz filter BW and the right plot is for 5 MHz filter BW. Both plots show BER vs SNR(dB) for GB = 1 RB.](f9625fa3465b009051f85d91cfa1da7e_img.jpg) + +The figure contains two plots. The left plot shows the Bit Error Rate (BER) on a logarithmic y-axis (from 10-4 to 100) against the Signal-to-Noise Ratio (SNR) in dB on the x-axis (from -10 to 10) for a 4.32 MHz filter bandwidth. Four curves are shown for different filter orders: 2 order filter (blue), 3 order filter (orange), 4 order filter (yellow), and 5 order filter (purple). The 2 order filter curve is nearly horizontal at a BER of approximately 0.3. The 3 order filter curve is slightly lower, around 0.2. The 4 order filter curve starts at 0.3 and decreases to about 0.1. The 5 order filter curve starts at 0.3 and decreases significantly to about 0.01. The right plot shows the same BER vs SNR curves for a 5 MHz filter bandwidth. The trends are similar, but the overall BER values are slightly higher than in the 4.32 MHz case. The 5 order filter curve decreases to about 0.02 at 10 dB SNR. + +Two plots showing BER vs SNR for different filter orders (2, 3, 4, 5) with ACI present. The left plot is for 4.32 MHz filter BW and the right plot is for 5 MHz filter BW. Both plots show BER vs SNR(dB) for GB = 1 RB. + +**Figure 7.1.2.2-10: Left: BER vs. SNR, 4.32 MHz filter BW, WUS at system BW edge, GB = 1 RB; Right: BER vs. SNR, 5 MHz filter BW, WUS at system BW edge, GB = 1 RB** + +![Two line graphs showing BER vs. SNR for different filter bandwidths (4.32 MHz and 5 MHz) with WUS at system BW edge and GB = 0 RB. The left graph is for 4.32 MHz filter BW and the right graph is for 5 MHz filter BW. Both graphs show BER on a logarithmic scale from 10^-4 to 10^0 against SNR(dB) from -10 to 10. Four filter orders are plotted: 2 order (blue diamonds), 3 order (orange squares), 4 order (yellow triangles), and 5 order (purple circles). In both cases, the 5 order filter shows the lowest BER, while the 2 order filter shows the highest BER.](9f92854fe6ecaf47760515c891a4fccc_img.jpg) + +Two line graphs showing BER vs. SNR for different filter bandwidths (4.32 MHz and 5 MHz) with WUS at system BW edge and GB = 0 RB. The left graph is for 4.32 MHz filter BW and the right graph is for 5 MHz filter BW. Both graphs show BER on a logarithmic scale from 10^-4 to 10^0 against SNR(dB) from -10 to 10. Four filter orders are plotted: 2 order (blue diamonds), 3 order (orange squares), 4 order (yellow triangles), and 5 order (purple circles). In both cases, the 5 order filter shows the lowest BER, while the 2 order filter shows the highest BER. + +**Figure 7.1.2.2-11: Left: BER vs. SNR, 4.32 MHz filter BW, WUS at system BW edge, GB = 0 RB; Right: BER vs. SNR, 5 MHz filter BW, WUS at system BW edge, GB = 0 RB** + +It can be seen that with 1 RB GB, BER is starting to be borderline acceptable with higher SNR levels only with 5th order filter for which the -3 dB bandwidth is exactly aligned with WUS BW. This is when no phase noise, non-linearities, frequency error, or practical filter implementation aspects are considered. Also with 15 kHz SCS, the NR channel GB would be narrower and performance with the same 360 kHz GB would be worse. Therefore, we conclude that 360 kHz GB at channel edge does not enable low-power low-cost RF implementation of wake-up receiver. + +To estimate the required GB we simulated how the performance changes if 3 additional RBs, i.e. additional 1.08 MHz, are used for guard band at channel edge. These RBs carry NR OFDM signal. Together with the WUS GB of 0 or 1 RB, the total separation from system BW edge is up to 1.44 MHz, and this is on top of the NR channel GB of 810 kHz. Results are shown in Figures 7.1.2.2-12 to 7.1.2.2-13. + +![Three line graphs showing BER vs. SNR for different filter bandwidths (4.32 MHz, 5 MHz, and 6 MHz) with WUS 3 RB offset from system BW edge and GB = 0 RB. The left graph is for 4.32 MHz filter BW, the middle for 5 MHz filter BW, and the right for 6 MHz filter BW. All graphs show BER on a logarithmic scale from 10^-4 to 10^0 against SNR(dB) from -10 to 10. Four filter orders are plotted: 2 order (blue diamonds), 3 order (orange squares), 4 order (yellow triangles), and 5 order (purple circles). In all cases, the 5 order filter shows the lowest BER, while the 2 order filter shows the highest BER.](1b1f1c6f7ba93ebe3c4f9b812d7476f9_img.jpg) + +Three line graphs showing BER vs. SNR for different filter bandwidths (4.32 MHz, 5 MHz, and 6 MHz) with WUS 3 RB offset from system BW edge and GB = 0 RB. The left graph is for 4.32 MHz filter BW, the middle for 5 MHz filter BW, and the right for 6 MHz filter BW. All graphs show BER on a logarithmic scale from 10^-4 to 10^0 against SNR(dB) from -10 to 10. Four filter orders are plotted: 2 order (blue diamonds), 3 order (orange squares), 4 order (yellow triangles), and 5 order (purple circles). In all cases, the 5 order filter shows the lowest BER, while the 2 order filter shows the highest BER. + +**Figure 7.1.2.2-12: Left: BER vs. SNR, 4.32 MHz filter BW, WUS 3 RB offset from system BW edge, GB = 0 RB; Middle: BER vs. SNR, 5 MHz filter BW, WUS 3 RB offset from system BW edge, GB = 0 RB; Right: BER vs. SNR, 6 MHz filter BW, WUS 3 RB offset from system BW edge, GB = 0 RB** + +![Three line graphs showing BER vs. SNR for different filter bandwidths (4.32 MHz, 5 MHz, and 6 MHz) with WUS 3 RB offset from system BW edge and GB = 1 RB. The left graph is for 4.32 MHz filter BW, the middle for 5 MHz filter BW, and the right for 6 MHz filter BW. All graphs show BER on a logarithmic scale from 10^-4 to 10^0 against SNR(dB) from -10 to 10. Four filter orders are plotted: 2 order (blue diamonds), 3 order (orange squares), 4 order (yellow triangles), and 5 order (purple circles). In all cases, the 5 order filter shows the lowest BER, while the 2 order filter shows the highest BER.](6f1d6debd3f3eada4104f0302c912672_img.jpg) + +Three line graphs showing BER vs. SNR for different filter bandwidths (4.32 MHz, 5 MHz, and 6 MHz) with WUS 3 RB offset from system BW edge and GB = 1 RB. The left graph is for 4.32 MHz filter BW, the middle for 5 MHz filter BW, and the right for 6 MHz filter BW. All graphs show BER on a logarithmic scale from 10^-4 to 10^0 against SNR(dB) from -10 to 10. Four filter orders are plotted: 2 order (blue diamonds), 3 order (orange squares), 4 order (yellow triangles), and 5 order (purple circles). In all cases, the 5 order filter shows the lowest BER, while the 2 order filter shows the highest BER. + +**Figure 7.1.2.2-13: Left: BER vs. SNR, 4.32 MHz filter BW, WUS 3 RB offset from system BW edge, GB = 1 RB; Middle: BER vs. SNR, 5 MHz filter BW, WUS 3 RB offset from system BW edge, GB = 1 RB; Right: BER vs. SNR, 6 MHz filter BW, WUS 3 RB offset from system BW edge, GB = 1 RB** + +In Figure 7.1.2.2-14 and 7.1.2.2-15, BER vs. SNR results are presented for case where LP-WUS is placed 6 RB offset from system BW edge, and when additional 1 RB GB is applied on top of this. + +![Figure 7.1.2.2-14: Three plots showing BER vs. SNR for different filter bandwidths (4.32 MHz, 5 MHz, 6 MHz) with LP-WUS 6 RB offset from system BW edge. Each plot compares 2, 3, 4, and 5 order filters. The 5th order filter shows the best performance, reaching a BER of 10^-4 at the lowest SNR.](75b9cb95f5815d6f3bbe57020a049504_img.jpg) + +Figure 7.1.2.2-14: Three plots showing BER vs. SNR for different filter bandwidths (4.32 MHz, 5 MHz, 6 MHz) with LP-WUS 6 RB offset from system BW edge. Each plot compares 2, 3, 4, and 5 order filters. The 5th order filter shows the best performance, reaching a BER of 10^-4 at the lowest SNR. + +Figure 7.1.2.2-14: + +**Left:** BER vs. SNR with ASCI and ACI, 4.32 MHz filter BW, LP-WUS 6 RB offset from system BW edge with no RB GB towards ASCS. + +**Middle:** BER vs. SNR with ASCI and ACI, 5 MHz filter BW, LP-WUS 6 RB offset from system BW edge with no RB GB towards ASCS. + +**Right:** BER vs. SNR with ASCI and ACI, 6 MHz filter BW, LP-WUS 6 RB offset from system BW edge with no RB GB towards ASCS. + +![Figure 7.1.2.2-15: Three plots showing BER vs. SNR for different filter bandwidths (4.32 MHz, 5 MHz, 6 MHz) with LP-WUS 6+1 RB offset from system BW edge. Each plot compares 2, 3, 4, and 5 order filters. The 5th order filter shows the best performance, reaching a BER of 10^-4 at the lowest SNR.](1c4139270d1edff9631800a63eabf7f5_img.jpg) + +Figure 7.1.2.2-15: Three plots showing BER vs. SNR for different filter bandwidths (4.32 MHz, 5 MHz, 6 MHz) with LP-WUS 6+1 RB offset from system BW edge. Each plot compares 2, 3, 4, and 5 order filters. The 5th order filter shows the best performance, reaching a BER of 10^-4 at the lowest SNR. + +Figure 7.1.2.2-15: + +**Left:** BER vs. SNR with ASCI and ACI, 4.32 MHz filter BW, LP-WUS 6+1 RB offset from system BW edge with no RB GB towards ASCS. + +**Middle:** BER vs. SNR with ASCI and ACI, 5 MHz filter BW, LP-WUS 6+1 RB offset from system BW edge with no RB GB towards ASCS. + +**Right:** BER vs. SNR with ASCI and ACI, 6 MHz filter BW, LP-WUS 6+1 RB offset from system BW edge with no RB GB towards ASCS. + +The results in above Figures show that performance is still far from ideal with lower order filters even with 6 RB offset. When looking at the data, there are some things to consider: while frequency error, phase noise and non-linearities will make the performance even worse, RAN4 allows a significant relaxation to wanted signal level in ACS test. Therefore, the correct SNR range to be looked at would be rather towards the right side of the plots. + +Finally Figure 7.1.2.2-16 shows performance with 3rd filter with different offsets from system BW edge. + +![Figure 7.1.2.2-16: Performance with 3rd order filter at different RB offsets from system BW edge with 4.32 MHz filter BW. The graph shows BER vs SNR(dB) for four cases: 3 RB from edge (blue diamonds), 6 RB from edge (orange diamonds), 12 RB from edge (yellow diamonds), and spectrum center (purple diamonds). The spectrum center case shows a sharp drop in BER after SNR=0 dB, while the edge cases show a more gradual drop. The 3 RB from edge case has the highest BER at high SNR.](2d62ff2bded0c21414a0f40fdf8fd537_img.jpg) + +Figure 7.1.2.2-16: Performance with 3rd order filter at different RB offsets from system BW edge with 4.32 MHz filter BW. The graph shows BER vs SNR(dB) for four cases: 3 RB from edge (blue diamonds), 6 RB from edge (orange diamonds), 12 RB from edge (yellow diamonds), and spectrum center (purple diamonds). The spectrum center case shows a sharp drop in BER after SNR=0 dB, while the edge cases show a more gradual drop. The 3 RB from edge case has the highest BER at high SNR. + +**Figure 7.1.2.2-16: Performance with 3rd order filter at different RB offsets from system BW edge with 4.32 MHz filter BW** + +The results in Figures 7.1.2.2-8 to Figure 7.1.2.2-13 show that even with total of 1.44 MHz separation from system BW edge, on top of the 810 kHz NR channel GB the SINR with 3rd order filter will not rise above 0 dB. This is with the filter BW matched to WUS BW, no nonlinearities, no frequency error and no phase noise present. If some practical filter implementation aspects are considered and therefore 5 MHz filter BW is considered, only 5th order filter reaches acceptable performance. With 15 kHz SCS the NR channel GB would be narrower, and performance would be worse. + +The results in Figures 7.1.2.2-14 to Figure 7.1.2.2-16 further show that more than 2.16 MHz offset from system BW edge, on top of the NR channel GB, is preferred for improved system performance with lower complexity implementation. + +When frequency error is considered in addition, there is additional negative impact to performance, as exemplified in Figure 7.1.2.2-17. + +![Figure 7.1.2.2-17: SINR vs. SNR with ASCI and ACI, 3rd order filter with 4.32 MHz filter BW. The figure contains two subplots. The left subplot is for LP-WUS 3 RB offset from system BW edge with 1 RB GB towards ASCS. The right subplot is for LP-WUS 6 RB offset from system BW edge with 1 RB GB towards ASCS. Both plots show SINR(dB) vs SNR(dB) for three frequency error (Fe) cases: Fe = 0 (blue diamonds), Fe = 50 ppm (orange diamonds), and Fe = 100 ppm (yellow diamonds). In both cases, the SINR increases with SNR, but the Fe = 0 case consistently shows higher SINR than the cases with frequency error. The 6 RB offset case (right) shows higher SINR than the 3 RB offset case (left).](d4852169b63bedb68b1f3c5b3b9b0cc0_img.jpg) + +Figure 7.1.2.2-17: SINR vs. SNR with ASCI and ACI, 3rd order filter with 4.32 MHz filter BW. The figure contains two subplots. The left subplot is for LP-WUS 3 RB offset from system BW edge with 1 RB GB towards ASCS. The right subplot is for LP-WUS 6 RB offset from system BW edge with 1 RB GB towards ASCS. Both plots show SINR(dB) vs SNR(dB) for three frequency error (Fe) cases: Fe = 0 (blue diamonds), Fe = 50 ppm (orange diamonds), and Fe = 100 ppm (yellow diamonds). In both cases, the SINR increases with SNR, but the Fe = 0 case consistently shows higher SINR than the cases with frequency error. The 6 RB offset case (right) shows higher SINR than the 3 RB offset case (left). + +**Figure 7.1.2.2-17:** + +**Left: SINR vs. SNR with ASCI and ACI, 3rd order filter with 4.32 MHz filter BW, LP-WUS 3 RB offset from system BW edge with 1 RB GB towards ASCS.** + +**Right: SINR vs. SNR with ASCI and ACI, 3rd order filter with 4.32 MHz filter BW, LP-WUS 6 RB offset from system BW edge with 1 RB GB towards ASCS.** + +In Figure 7.1.2.2-17 it can be seen that frequency error has a clear negative impact to SINR, and e.g. in case of 6+1 RB offset from adjacent channel, having frequency error in place can result in need of up to 7 dB higher input SNR to reach the same SINR when compared against case with no frequency error. With 3+1RB offset to band edge in left sub-figure, impact of frequency error makes it very difficult to reach SINR range where successful operation would be possible. It should be noted that while LP-WUS receiver is expected to periodically synchronize itself, there will also be long sleep periods during which frequency can drift. Therefore, considering large frequency offsets is not unreasonable. + +If full flexibility for WUS location within NR channel bandwidth is needed, the opportunities for low-power implementation are severely limited for envelope detection based RF implementations. Analog filtering is not sufficient if WUS is placed on the RBs closest to channel edge. Even with 4RB, i.e., 1.44 MHz offset with 30 kHz SCS, + +performance challenges remain unless complex high order filtering with accurate filter BW is used. For 15 kHz, the performance is expected to be worse due to narrower NR channel GB. + +To enable digital filtering, analog-to-digital conversion needs to have sufficient dynamic range to digitize also the interfering signal. Increase in ADC complexity results in higher power consumption. + +Analog envelope detection architectures will perform poorly or require a complex implementation if WUS is placed immediately adjacent to channel edge. To improve the likelihood of successful operation and allowing possibilities for low-power implementation, greater than 2.16 MHz offset from outermost RB edge at channel edge is preferred, but exact value needs further study. For architectures using digital detection, placing WUS away from channel edge can enable use of simpler RF HW and power savings. + +In case only adjacent subcarrier interference is considered, situation is greatly improved. Figure 7.1.2.2-18 shows impact to performance with 3rd order filter (4.32 MHz filter BW) with and without 1 RB GB between WUS and other NR subcarriers: + +![Figure 7.1.2.2-18: Two line graphs showing BER vs. SNR (dB) for ASCI only, 3rd order filter with 4.32 MHz filter BW. The left graph shows LP-WUS 3 RB offset from system BW edge, and the right graph shows LP-WUS 6 RB offset from system BW edge. Both graphs compare 'GB off' (blue line with circles) and 'GB on' (orange line with diamonds). In both cases, the BER curves for 'GB off' and 'GB on' are nearly identical, showing that the guard band does not significantly impact performance.](e6d17113d3c65cc31531ae8a73fe011f_img.jpg) + +The figure consists of two side-by-side line graphs. Both plots have 'BER' on the y-axis (logarithmic scale from 10-4 to 100) and 'SNR(dB)' on the x-axis (linear scale from -10 to 10). The left plot is for 'LP-WUS 3 RB offset from system BW edge' and the right plot is for 'LP-WUS 6 RB offset from system BW edge'. In both plots, two data series are shown: 'GB off' (blue line with circle markers) and 'GB on' (orange line with diamond markers). The curves for both series are nearly perfectly overlaid, showing that the presence of a guard band (GB) has no significant impact on the Bit Error Rate (BER) performance in this scenario. + +Figure 7.1.2.2-18: Two line graphs showing BER vs. SNR (dB) for ASCI only, 3rd order filter with 4.32 MHz filter BW. The left graph shows LP-WUS 3 RB offset from system BW edge, and the right graph shows LP-WUS 6 RB offset from system BW edge. Both graphs compare 'GB off' (blue line with circles) and 'GB on' (orange line with diamonds). In both cases, the BER curves for 'GB off' and 'GB on' are nearly identical, showing that the guard band does not significantly impact performance. + +Figure 7.1.2.2-18: + +**Left: BER vs. SNR with ASCI only, 3rd order filter with 4.32 MHz filter BW, LP-WUS 3 RB offset from system BW edge. Comparison between 0 and 1 RB GB.** + +**Right: BER vs. SNR with ASCI only, 3rd order filter with 4.32 MHz filter BW, LP-WUS 6 RB offset from system BW edge. Comparison between 0 and 1 RB GB.** + +Based on the results, guard band does not impact the performance and no guard band is required between WUS and other NR subcarriers. + +[7B-7],[7B-8] + +The simulation parameters are listed in Table 7.1.2.2-10 below. + +**Table 7.1.2.2-10: LLS parameters** + +| Parameters | Value | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|----------------------|--|--|---------|----------|----------|--------|--|--|--|-------|-------|-------|-------|--------|--------|------|--------|--------|------|------|------| +| Carrier frequency | 2.6 GHz | | | | | | | | | | | | | | | | | | | | | | | | +| Channel | AWGN | | | | | | | | | | | | | | | | | | | | | | | | +| SCS | 30 kHz | | | | | | | | | | | | | | | | | | | | | | | | +| UE Rx antennas | 1 for WUR | | | | | | | | | | | | | | | | | | | | | | | | +| WUR sampling rate | 10 Msps | | | | | | | | | | | | | | | | | | | | | | | | +| WUS bandwidth | For OOK WUS:
5 MHz (for 30 kHz SCS: 12 PRBs+ ~ 1 PRB guard band each side of WUS) | | | | | | | | | | | | | | | | | | | | | | | | +| Number of ADC bits | 8 | | | | | | | | | | | | | | | | | | | | | | | | +| Receiver filter | 4, 6 , 8 and 10 th order of chebyshev filter, filter BW is the same as WUS BW | | | | | | | | | | | | | | | | | | | | | | | | +| Non-WUS transmissions | Adjacent channel interference from other NR transmissions is considered. | | | | | | | | | | | | | | | | | | | | | | | | +| Max. false alarm due to noise or random symbols | 0.1% | | | | | | | | | | | | | | | | | | | | | | | | +| Frequency offset (ppm) | For OOK WUS:
50 ppm maximum frequency error | | | | | | | | | | | | | | | | | | | | | | | | +| Rx approach | Payload based: based on Manchester decoding. | | | | | | | | | | | | | | | | | | | | | | | | +| RF impairments | Phase noise profile
Phase noise (dBc/Hz)
NF 9 dB NF 12 dB NF 15 dB
Offset
@5MHz -99.4 -99.4 -99.4
@10MHz -108.1 -105 -102.1
@15MHz -120 -117 -114
| | Phase noise (dBc/Hz) | | | NF 9 dB | NF 12 dB | NF 15 dB | Offset | | | | @5MHz | -99.4 | -99.4 | -99.4 | @10MHz | -108.1 | -105 | -102.1 | @15MHz | -120 | -117 | -114 | +| | Phase noise (dBc/Hz) | | | | | | | | | | | | | | | | | | | | | | | | +| | NF 9 dB | NF 12 dB | NF 15 dB | | | | | | | | | | | | | | | | | | | | | | +| Offset | | | | | | | | | | | | | | | | | | | | | | | | | +| @5MHz | -99.4 | -99.4 | -99.4 | | | | | | | | | | | | | | | | | | | | | | +| @10MHz | -108.1 | -105 | -102.1 | | | | | | | | | | | | | | | | | | | | | | +| @15MHz | -120 | -117 | -114 | | | | | | | | | | | | | | | | | | | | | | + +For ASCS case, phase noise has little impact on the needed guard RB. For ACS case, the phase noise may degrade the SNR at least 3 dB for filter order of 8 and 10. + +The number of guard RB within the WUS carrier/BW for ASCS case does not need to be greater than 1 as illustrated in Figure 7.1.2.2-19, increasing the number of the guard RB within the WUS carrier/BW may have penalty on the SNR in Figure 7.1.2.2-20. + +For ACS case, there is a need to shift the WUS away from the adjacent carrier to get more filter attenuation for the adjacent carrier, the number of the shifted RB depends on the WUR filter order and the number of bits per OFDM symbol. For example, it is preferred placing the WUS signal in the middle of 20MHz channel for OOK-2 for WUR with a filter of order 6. For OOK1 and for WUR with a filter of order 6, the WUS signal should be placed with 6 to 10 RB away from the Adjacent carrier channel edge excluding the NR channel guard band. This is illustrated in Figure 7.1.2.2-21. + +The observations from ACS simulation impacts the ACS test case design. The ACS is to test the UE receiver selectivity and the requirement is specified with a special test condition, e.g., ACI level, the UL and DL RB placement. From the simulation results, it can be observed that it is necessary to introduce additional offset from the edge of WUS signal to ACI for certain filter design. As it is not clear whether to test OOK1, OOK2 or OOK4 and which filter order WUR should be implemented, the detailed design of ACS test case could be discussed in work item phase. + +Observed from the simulation, there is no need to introduce additional guard RB beyond the WUS BW. For ACS, blanking more RB adjacent to the WUS BW does not help to attenuate the leakage power from ACI, shifting the WUS signal away from the ACI helps more to attenuate ACI because the leakage power from ACI much higher than leakage power from adjacent subcarrier. + +![Four subplots showing BLER vs SNR for OOK1 with various BPF orders and phase noise settings. The top-left plot is for nGuardRB=1, top-right for nGuardRB=1/2, and the bottom two plots show zoomed-in views of the error floors. Each plot compares BPF orders 4, 6, 8, and 10 with phase noise ON and OFF against a 1% BLER target.](201de44da5d99899a8cf58eac2fa7bc9_img.jpg) + +The figure consists of four subplots arranged in a 2x2 grid, showing the Block Error Rate (BLER) versus the Signal-to-Noise Ratio (SNR) in dB for the OOK1 modulation scheme. All plots share the same simulation parameters: DL\_1BSANT\_1UEANT\_AWGN, ACI=0, OOK1, nShiftRB=0. The top-left plot is for nGuardRB=1, and the top-right plot is for nGuardRB=1/2. The bottom-left and bottom-right plots are zoomed-in views of the error floors of the top-left and top-right plots, respectively. Each plot compares the performance of different Bandpass Filter (BPF) orders (4, 6, 8, and 10) with phase noise ON and OFF. A horizontal dashed line at BLER = 1% indicates the target performance level. The zoomed-in plots show that higher BPF orders and phase noise OFF result in lower error floors. + +Four subplots showing BLER vs SNR for OOK1 with various BPF orders and phase noise settings. The top-left plot is for nGuardRB=1, top-right for nGuardRB=1/2, and the bottom two plots show zoomed-in views of the error floors. Each plot compares BPF orders 4, 6, 8, and 10 with phase noise ON and OFF against a 1% BLER target. + +Figure 7.1.2.2-19: BLER for OOK1 w/w phase noise for ASCS case + +![A single plot showing BLER vs SNR for OOK1 with BPF order 4 and various guard RB numbers (0.5, 1, 1.5) with phase noise ON/OFF.](449d2799e97657d8fa5897b2e74a88bd_img.jpg) + +This plot shows the BLER versus SNR for the OOK1 modulation scheme with a BPF order of 4. The simulation parameters are DL\_1BSANT\_1UEANT\_AWGN, ACI=0, OOK1, nShiftRB=0, and nGuardRB values of 0.5, 1, and 1.5. The plot compares the performance with phase noise ON and OFF for each guard RB number. A horizontal dashed line at BLER = 1% indicates the target performance level. The results show that increasing the guard RB number improves the performance, and phase noise has a more significant impact at higher guard RB numbers. + +A single plot showing BLER vs SNR for OOK1 with BPF order 4 and various guard RB numbers (0.5, 1, 1.5) with phase noise ON/OFF. + +Figure 7.1.2.2-20: BLER for OOK1 with phase noise ON/OFF for ASCS case and Guard RB number =1/2, 1 and 1.5 for filter order 4 + +![Four subplots showing BLER performance for BFP order = 6 and different # of shift RB with ACI = 33 dB. The subplots are arranged in a 2x2 grid. Top-left: Sim: (1049390) DL_1BSANT_1UEANT_AWGN, ACI = 33, OOK1, BPF order = 6, Phase noise OFF. Top-right: Sim: (1049389) DL_1BSANT_1UEANT_AWGN, ACI = 33, OOK1, BPF order = 6, Phase noise ON. Bottom-left: Sim: (1049391) DL_1BSANT_1UEANT_AWGN, ACI = 33, OOK2, BPF order = 6, Phase noise OFF. Bottom-right: Sim: (1049388) DL_1BSANT_1UEANT_AWGN, ACI = 33, OOK2, BPF order = 6, Phase noise ON. Each plot shows BLER vs SNR [dB] for nShiftRB values of 0, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20. The curves show that as nShiftRB increases, the BLER performance improves, especially at higher SNR values.](1bc1bf231ada31f57cd9f0d8791b784b_img.jpg) + +Four subplots showing BLER performance for BFP order = 6 and different # of shift RB with ACI = 33 dB. The subplots are arranged in a 2x2 grid. Top-left: Sim: (1049390) DL\_1BSANT\_1UEANT\_AWGN, ACI = 33, OOK1, BPF order = 6, Phase noise OFF. Top-right: Sim: (1049389) DL\_1BSANT\_1UEANT\_AWGN, ACI = 33, OOK1, BPF order = 6, Phase noise ON. Bottom-left: Sim: (1049391) DL\_1BSANT\_1UEANT\_AWGN, ACI = 33, OOK2, BPF order = 6, Phase noise OFF. Bottom-right: Sim: (1049388) DL\_1BSANT\_1UEANT\_AWGN, ACI = 33, OOK2, BPF order = 6, Phase noise ON. Each plot shows BLER vs SNR [dB] for nShiftRB values of 0, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20. The curves show that as nShiftRB increases, the BLER performance improves, especially at higher SNR values. + +Figure 7.1.2.2-21: BLER performance for BFP order =6 and different # of shift RB with ACI = 33 dB + +#### 7.1.2.3 ASCS evaluation + +To evaluate the in-channel interference, RAN4 has defined a new metric as Adjacent Subcarrier Selectivity (ASCS) for evaluation purpose, which is the ratio of the receive filter attenuation on the assigned channel frequency to the receive filter attenuation on the adjacent sub-carrier(s). + +The ACSC BWinterference is set as 5MHz, for both ~5MHz and ~1.4MHz LP-WUS cases, as a starting point for ASCS evaluation. The same PSD of LP-WUS and NR signal is assumed within the channel. + +As shown in Figure 7.1.2.3-1, WUS at the center of NR channel would be the worst case of ASCS. For ASCS, the required guard RBs belongs to LP-WUR bandwidth. + +![Diagram of LP-WUS at the centre of NR channel. It shows an NR cell with a 20/100MHz bandwidth. A 5MHz WUR bandwidth is centered within it, containing 24 WUS RBs. On either side of the WUS are 5MHz BW_interferer blocks. Guardbands are shown at the edges of the NR cell. ASCS Guard RBs (0~2) are indicated between the WUS and the interferers. A legend indicates that grey rectangles represent 'Required Guard RBs for WUS' and white rectangles represent 'Guardband of NR cell'. Text below the diagram specifies 'Case 1: WUS at center of NR channel, Adjacent NR SubCarrier wider than WUS signal'.](2cf3896394a2342a2b46c504ab9a8830_img.jpg) + +Diagram of LP-WUS at the centre of NR channel. It shows an NR cell with a 20/100MHz bandwidth. A 5MHz WUR bandwidth is centered within it, containing 24 WUS RBs. On either side of the WUS are 5MHz BW\_interferer blocks. Guardbands are shown at the edges of the NR cell. ASCS Guard RBs (0~2) are indicated between the WUS and the interferers. A legend indicates that grey rectangles represent 'Required Guard RBs for WUS' and white rectangles represent 'Guardband of NR cell'. Text below the diagram specifies 'Case 1: WUS at center of NR channel, Adjacent NR SubCarrier wider than WUS signal'. + +**Figure 7.1.2.3-1: LP-WUS at the centre of NR channel, only ASCS needs to be considered.** + +**Table 7.1.2.3-1: LP-WUS evaluation parameters for WUS at centre** + +| | | +|---------------------------------|-----------------------------------------------------------------------------------------------------------------| +| NR RF channel BW | 20MHz/100MHz for 5MHz WUS | +| Guardband of NR channel | Unchanged, defined in Clause 5.3.3 in TS 38.101-1 | +| WUS BW within NR channel | Max 5.04 MHz | +| WUS RB allocation (Note 1) | 24 RB (15kHz SCS) or 12 RB (30kHz SCS) in 5.04 MHz; | +| WUS placement within NR channel | case 1: Center; | +| Guard RB size of LP-WUS | 0 RB, 0.5RB, 1RB, 2RB, 3RB at each side
Symmetric guard RB | +| ASCS interferer | 5MHz | +| Filter characteristic | 2 nd to 5 th order Butterworth
lowpass@ baseband
bandpass@100MHz
bandpass@2.6GHz | +| Filter passband BW | Same as WUS bandwidth (number of RBs) | +| Target ACS | TBD | +| Target ASCS | TBD | +| Target WUS SNR | TBD | +| NR power level | Same PSD with WUS signal | +| RF impairment | Max. Center frequency offset = 5, 10, 50, 200 ppm. Initial search | +| Note 1: | For easy evaluation, the number of allocated WUS RBs is fixed. The number of Guard RBs is changed. | + +##### **Conclusion for RAN4 ASCS guard RB analysis:** + +Based on the following analysis, RAN4 observed that for 5th order filter, the guard RB number for LP-WUS ASCS is in the range of 0RB ~ 1RBs for 30KHz SCS, or 0RBs ~2RBs for 15KHz SCS. Similar number of guard RBs could be applied also with lower filter orders as performance was observed to remain similar with 3rd order filter. + +Companies' input on simulation analysis of ASCS have been presented as following: + +##### **Filter suppression level analysis:** + +[7B-1] + +The parameter assumption is aligned with that in Table 7.1.2.2-1. The required guard RB is provided in the Table 7.1.2.3-2 below. + +**Table 7.1.2.3-2: 5MHz LP-WUS ASCS results for WUS at center** + +| Filter order | Guard RB CBW | Frequency Offset | ASCS, BW interference = 5MHz | | | | | +|-----------------|---------------------|------------------|-----------------------------------------|--------|--------|--------|--------| +| | | | 0RB | 0.5RB | 1RB | 2RB | 3RB | +| 5 th | 20MHz, SCS = 15kHz | 0 ppm | -19.25 | -20.67 | -21.63 | -24.04 | -26.39 | +| | | 5 ppm | -19.04 | -20.45 | -21.40 | -23.79 | -26.13 | +| | | 10 ppm | -18.83 | -20.22 | -21.17 | -23.55 | -25.89 | +| | | 50 ppm | -17.26 | -18.54 | -19.42 | -21.68 | -23.95 | +| | | 200 ppm | -12.73 | -13.63 | -14.26 | -15.96 | -17.81 | +| | 100MHz, SCS = 30kHz | 0 ppm | -18.24 | -20.63 | -22.97 | -27.59 | -31.80 | +| | | 5 ppm | -18.03 | -20.40 | -22.72 | -27.34 | -31.54 | +| | | 10 ppm | -17.82 | -20.17 | -22.48 | -27.08 | -31.28 | +| | | 50 ppm | -16.25 | -18.42 | -20.61 | -25.11 | -29.28 | +| | | 200 ppm | -11.74 | -13.27 | -14.90 | -18.70 | -22.60 | +| 4 th | 20MHz, SCS = 15kHz | 0 ppm | -16.99 | -18.06 | -18.78 | -20.58 | -22.34 | +| | | 5 ppm | -16.82 | -17.88 | -18.60 | -20.39 | -22.14 | +| | | 10 ppm | -16.56 | -17.71 | -18.42 | -20.20 | -21.95 | +| | | 50 ppm | -15.37 | -16.36 | -17.03 | -18.73 | -20.42 | +| | | 200 ppm | -11.54 | -12.28 | -12.80 | -14.15 | -15.57 | +| | 100MHz, SCS = 30kHz | 0 ppm | -16.03 | -17.84 | -19.57 | -23.06 | -26.27 | +| | | 5 ppm | -15.87 | -17.65 | -19.38 | -22.86 | -26.06 | +| | | 10 ppm | -15.70 | -17.47 | -19.19 | -22.65 | -25.86 | +| | | 50 ppm | -14.42 | -16.08 | -17.72 | -21.10 | -24.27 | +| | | 200 ppm | -10.61 | -11.87 | -13.15 | -16.05 | -18.99 | +| 3 rd | 20MHz, SCS = 15kHz | 0 ppm | -14.18 | -14.92 | -15.42 | -16.65 | -17.86 | +| | | 5 ppm | -14.05 | -14.79 | -15.28 | -16.51 | -17.71 | +| | | 10 ppm | -13.92 | -14.66 | -15.15 | -16.37 | -17.57 | +| | | 50 ppm | -12.95 | -13.64 | -14.11 | -15.28 | -16.45 | +| | | 200 ppm | -9.95 | -10.51 | -10.89 | -11.87 | -12.87 | +| | 100MHz, SCS = 30kHz | 0 ppm | -13.33 | -14.58 | -15.76 | -18.17 | -20.42 | +| | | 5 ppm | -13.20 | -14.44 | -15.62 | -18.02 | -20.27 | +| | | 10 ppm | -13.07 | -14.31 | -15.48 | -17.87 | -20.12 | +| | | 50 ppm | -12.10 | -13.28 | -14.40 | -16.73 | -18.95 | +| | | 200 ppm | -9.13 | -10.07 | -10.10 | -13.04 | -15.08 | +| 2 nd | 20MHz, SCS = 15kHz | 0 ppm | -10.71 | -11.15 | -11.44 | -12.17 | -12.88 | +| | | 5 ppm | -10.62 | -11.06 | -11.35 | -12.08 | -12.78 | +| | | 10 ppm | -10.54 | -10.98 | -11.27 | -11.99 | -12.69 | +| | | 50 ppm | -9.89 | -10.31 | -10.59 | -11.29 | -11.98 | +| | | 200 ppm | -7.86 | -8.22 | -8.46 | -9.06 | -9.67 | +| | 100MHz, SCS = 30kHz | 0 ppm | -10.05 | -10.79 | -11.49 | -12.92 | -14.27 | +| | | 5 ppm | -9.97 | -10.71 | -11.40 | -12.82 | -14.18 | +| | | 10 ppm | -9.89 | -10.62 | -11.31 | -12.73 | -14.08 | +| | | 50 ppm | -9.25 | -9.96 | -10.62 | -12.00 | -13.33 | +| | | 200 ppm | -7.24 | -7.85 | -8.42 | -9.65 | -10.87 | + +[7B-2] + +The evaluation parameters are listed in Table 7.1.2.3-3 below. + +**Table 7.1.2.3-3: Evaluation assumptions.** + +| | | +|------------------------|-------------| +| WUS signal bandwidth | 4.32 MHz | +| Interferer power level | 0 dBc | +| F 0 | 2.6 GHz | +| Filter Type | Butterworth | + +**Table 7.1.2.3-4: Guard required in KHz for a target interference level of -10 dBc.** + +| CFO | Filter order | | | | | +|-----------|--------------|--------|--------|-------|-------| +| | 1 | 2 | 3 | 4 | 5 | +| ± 0 ppm | 4320.0 | 1598.4 | 972.0 | 691.2 | 540 | +| ± 5 ppm | 4346.0 | 1608.0 | 977.9 | 695.4 | 543.3 | +| ± 50 ppm | 4580.0 | 1694.6 | 1030.5 | 732.8 | 572.5 | +| ± 100 ppm | 4840.0 | 1790.8 | 1089.0 | 774.4 | 605.0 | +| ± 200 ppm | 5360.0 | 1983.2 | 1206.0 | 857.6 | 670.0 | + +Based on the above table, we suggest that for 5th order filter, the guard RB number for LP-WUS can be 2RBs for 30kHz SCS, or 3RBs ~ 4RBs for 15kHz SCS. + +[7B-3] + +Following table is based on low-pass filter for zero-IF envelop detector architecture, in which pass bandwidth is 4.32/2=2.16MHz. + +**Table 7.1.2.3-5: Evaluated ASCS based on low-pass filter with 2.16MHz pass bandwidth** + +| Filter order | Guard RB
CBW | Frequency
Offset | ASCS, BW interference = 5MHz | | | | +|-----------------|-----------------------|---------------------|-----------------------------------------|--------|--------|--------| +| | | | 0RB/ | 1RB/ | 2RB/ | 4RB/ | +| | | | 15kSCS | 15kSC | 15kSC | 15kSC | +| 5 th | 20MHz, SCS
= 15kHz | 0 ppm | -20.05 | -22.39 | -24.75 | -29.25 | +| | | 5 ppm | -19.89 | -22.22 | -24.58 | -29.1 | +| | | 10 ppm | -19.72 | -22.05 | -24.41 | -28.94 | +| | | 50 ppm | -18.44 | -20.7 | -23.05 | -27.67 | +| | | 200 ppm | -14.31 | -16.06 | -18.08 | -22.66 | +| 2 nd | 20MHz, SCS
= 15kHz | 0 ppm | -10.71 | -11.42 | -12.12 | -13.47 | +| | | 5 ppm | -10.65 | -11.37 | -12.07 | -13.42 | +| | | 10 ppm | -10.6 | -11.31 | -12.02 | -13.38 | +| | | 50 ppm | -10.19 | -10.9 | -11.61 | -12.99 | +| | | 200 ppm | -8.66 | -9.36 | -10.07 | -11.49 | + +Following table is based on analog band-pass filter for RF/IF envelop detector architecture, in which pass bandwidth is 4.32MHz. + +**Table 7.1.2.3-6: Evaluated ASCS based on analog low-pass filter with 4.32MHz pass bandwidth** + +| Filter order | Guard RB
CBW | Frequency
Offset | ASCS, BW interference = 5MHz | | | | | +|-----------------|-----------------------|---------------------|-----------------------------------------|--------|--------|--------|--------| +| | | | 0RB/ | 1RB/ | 2RB/ | 4RB/ | 0RB/ | +| | | | 15kSCS | 15kSC | 15kSC | 15kSC | 15kSCS | +| 5 th | 20MHz, SCS
= 15kHz | 0 ppm | -14.41 | -15.59 | -16.79 | -19.2 | -21.56 | +| | | 5 ppm | -14.33 | -15.51 | -16.71 | -19.12 | -21.48 | +| | | 10 ppm | -14.24 | -15.42 | -16.62 | -19.03 | -21.39 | +| | | 50 ppm | -13.58 | -14.74 | -15.93 | -18.34 | -20.72 | +| | | 200 ppm | -11.24 | -12.29 | -13.39 | -15.73 | -18.13 | +| 2 nd | 20MHz, SCS
= 15kHz | 0 ppm | -7.25 | -7.64 | -8.02 | -8.79 | -9.54 | +| | | 5 ppm | -7.22 | -7.61 | -8 | -8.76 | -9.52 | +| | | 10 ppm | -7.2 | -7.58 | -7.97 | -8.73 | -9.49 | +| | | 50 ppm | -6.97 | -7.36 | -7.74 | -8.51 | -9.27 | +| | | 200 ppm | -6.14 | -6.52 | -6.91 | -7.68 | -8.45 | + +Less pass bandwidth will lead to better filter suppression capability, so Table 7.1.2.3-5 with less pass bandwidth will have better performance. + +##### Link-level simulation analysis: + +[7B-1] + +The detailed parameters are listed in Table 7.1.2.2-3. The simulation results are in Figure 7.1.2.3-2 with consideration of CFO RF impairment. + +![Six subplots showing BLER vs SNR for 2.6G-OOK-1, 2.6G-OOK-2, and 2.6G-OOK-4 waveforms with 6SC and 12SC guard bands. Each plot compares 3rd and 5th order filters for CFO values of 0, 10, 20, 50, and 200 ppm.](f217ea7a6e9347a9ca4d6173ed57c33e_img.jpg) + +The figure consists of six subplots arranged in a 3x2 grid, showing the Bit Link Error Rate (BLER) versus the Signal-to-Noise Ratio (SNR) for different waveform configurations under Carrier Frequency Offset (CFO) RF impairment. The waveforms are 2.6G-OOK-1, 2.6G-OOK-2, and 2.6G-OOK-4, each evaluated with 6SC and 12SC guard bands. The SNR ranges from -10 to 15 dB, and the BLER is on a logarithmic scale from 10-3 to 100. + +Each subplot compares the performance of 3rd and 5th order filters for CFO values of 0, 10, 20, 50, and 200 ppm. The legend in each plot indicates: + +- CFO=0ppm-3rd order filter (green dashed line with triangles) +- CFO=0ppm-5th order filter (green dashed line with circles) +- CFO=10ppm-3rd order filter (orange dashed line with triangles) +- CFO=10ppm-5th order filter (orange dashed line with circles) +- CFO=20ppm-3rd order filter (blue dashed line with triangles) +- CFO=20ppm-5th order filter (blue dashed line with circles) +- CFO=50ppm-3rd order filter (red dashed line with triangles) +- CFO=50ppm-5th order filter (red dashed line with circles) +- CFO=200ppm-3rd order filter (magenta dashed line with triangles) +- CFO=200ppm-5th order filter (magenta dashed line with circles) + +The subplots are titled as follows: + +- Top-left: 2.6G-OOK-1, GB=6SC +- Top-right: 2.6G-OOK-1, GB=12SC +- Middle-left: 2.6G-OOK-2, GB=6SC +- Middle-right: 2.6G-OOK-2, GB=12SC +- Bottom-left: 2.6G-OOK-4, GB=6SC +- Bottom-right: 2.6G-OOK-4, GB=12SC + +Six subplots showing BLER vs SNR for 2.6G-OOK-1, 2.6G-OOK-2, and 2.6G-OOK-4 waveforms with 6SC and 12SC guard bands. Each plot compares 3rd and 5th order filters for CFO values of 0, 10, 20, 50, and 200 ppm. + +Figure 7.1.2.3-2: ASCS guard RB evaluation with CFO RF impairment + +[7B-4] + +Different from ACS, for evaluation of ASCS we consider the PSD for all RBs including both LP-WUS and NR signal is flat and no power boosting is considered for LP-WUS signal. Figure 7.1.2.3-3 shows the ASCS guard band evaluation for several different waveforms, all the simulations are based on 5th order Butterworth filter. + +![OOK1, GB=6SC plot showing BLER vs SNR [dB] for No CFO, CFO=10ppm, CFO=20ppm, and CFO=50ppm. The curves show a steep drop in BLER as SNR increases from -8 dB to -4 dB.](98ea5e21d919b389f3ce8b17ef4e65f6_img.jpg) + +OOK1, GB=6SC + +Y-axis: BLER (log scale, 10-3 to 100) + +X-axis: SNR [dB] (-8 to 3) + +Legend: No CFO (blue line with circles), CFO=10ppm (blue line with circles), CFO=20ppm (blue line with crosses), CFO=50ppm (blue line with squares) + +OOK1, GB=6SC plot showing BLER vs SNR [dB] for No CFO, CFO=10ppm, CFO=20ppm, and CFO=50ppm. The curves show a steep drop in BLER as SNR increases from -8 dB to -4 dB. + +![OOK1, GB=12SC plot showing BLER vs SNR [dB] for No CFO, CFO=10ppm, CFO=20ppm, and CFO=50ppm. The curves show a steep drop in BLER as SNR increases from -8 dB to -4 dB.](a03f88e0ac174f2614e86f19e75f7b1d_img.jpg) + +OOK1, GB=12SC + +Y-axis: BLER (log scale, 10-3 to 100) + +X-axis: SNR [dB] (-8 to 3) + +Legend: No CFO (blue line with circles), CFO=10ppm (blue line with circles), CFO=20ppm (blue line with crosses), CFO=50ppm (blue line with squares) + +OOK1, GB=12SC plot showing BLER vs SNR [dB] for No CFO, CFO=10ppm, CFO=20ppm, and CFO=50ppm. The curves show a steep drop in BLER as SNR increases from -8 dB to -4 dB. + +a) ASCS guard RB evaluation for OOK-1 + +![OOK2, GB=6SC plot showing BLER vs SNR [dB] for No CFO, CFO=10ppm, CFO=20ppm, and CFO=50ppm. The curves show a steep drop in BLER as SNR increases from -6 dB to -2 dB.](4908c132d4fbad657b6fc84561c43fbb_img.jpg) + +OOK2, GB=6SC + +Y-axis: BLER (log scale, 10-3 to 100) + +X-axis: SNR [dB] (-8 to 3) + +Legend: No CFO (blue line with circles), CFO=10ppm (blue line with circles), CFO=20ppm (blue line with crosses), CFO=50ppm (blue line with squares) + +OOK2, GB=6SC plot showing BLER vs SNR [dB] for No CFO, CFO=10ppm, CFO=20ppm, and CFO=50ppm. The curves show a steep drop in BLER as SNR increases from -6 dB to -2 dB. + +![OOK2, GB=12SC plot showing BLER vs SNR [dB] for No CFO, CFO=10ppm, CFO=20ppm, and CFO=50ppm. The curves show a steep drop in BLER as SNR increases from -6 dB to -2 dB.](1da66f5fec34c001912c84a9abf145d7_img.jpg) + +OOK2, GB=12SC + +Y-axis: BLER (log scale, 10-3 to 100) + +X-axis: SNR [dB] (-8 to 3) + +Legend: No CFO (blue line with circles), CFO=10ppm (blue line with circles), CFO=20ppm (blue line with crosses), CFO=50ppm (blue line with squares) + +OOK2, GB=12SC plot showing BLER vs SNR [dB] for No CFO, CFO=10ppm, CFO=20ppm, and CFO=50ppm. The curves show a steep drop in BLER as SNR increases from -6 dB to -2 dB. + +b) ASCS guard RB evaluation for OOK-2 + +![OOK4, GB=6SC plot showing BLER vs SNR [dB] for No CFO, CFO=10ppm, CFO=20ppm, and CFO=50ppm. The curves show a steep drop in BLER as SNR increases from -5 dB to -1 dB.](95520f6525ad4eba23a46d9cbb178902_img.jpg) + +OOK4, GB=6SC + +Y-axis: BLER (log scale, 10-3 to 100) + +X-axis: SNR [dB] (-8 to 3) + +Legend: No CFO (blue line with circles), CFO=10ppm (blue line with circles), CFO=20ppm (blue line with crosses), CFO=50ppm (blue line with squares) + +OOK4, GB=6SC plot showing BLER vs SNR [dB] for No CFO, CFO=10ppm, CFO=20ppm, and CFO=50ppm. The curves show a steep drop in BLER as SNR increases from -5 dB to -1 dB. + +![OOK4, GB=12SC plot showing BLER vs SNR [dB] for No CFO, CFO=10ppm, CFO=20ppm, and CFO=50ppm. The curves show a steep drop in BLER as SNR increases from -5 dB to -1 dB.](bbce254e33d654e2077bd1e3e9beae8a_img.jpg) + +OOK4, GB=12SC + +Y-axis: BLER (log scale, 10-3 to 100) + +X-axis: SNR [dB] (-8 to 3) + +Legend: No CFO (blue line with circles), CFO=10ppm (blue line with circles), CFO=20ppm (blue line with crosses), CFO=50ppm (blue line with squares) + +OOK4, GB=12SC plot showing BLER vs SNR [dB] for No CFO, CFO=10ppm, CFO=20ppm, and CFO=50ppm. The curves show a steep drop in BLER as SNR increases from -5 dB to -1 dB. + +c) ASCS guard RB evaluation for OOK-4 + +![Plot for FSK1 with 6SC guard RBs showing BLER vs SNR for various CFO levels.](9c888dd6588358989047de6ced8b2bdb_img.jpg) + +This plot shows the Bit Error Rate (BLER) versus the Signal-to-Noise Ratio (SNR) in dB for FSK1 with 6SC guard RBs. The y-axis is BLER on a logarithmic scale from 10-3 to 100. The x-axis is SNR [dB] from -8 to 3. Four curves are shown: 'No CFO' (solid line with circles), 'CFO=10ppm' (dashed line with circles), 'CFO=20ppm' (dashed line with crosses), and 'CFO=50ppm' (dashed line with squares). All curves show a sharp decrease in BLER as SNR increases, starting around SNR = -5 dB. The 'No CFO' curve reaches a BLER of 10-3 at approximately -1.5 dB SNR. + +Plot for FSK1 with 6SC guard RBs showing BLER vs SNR for various CFO levels. + +![Plot for FSK1 with 12SC guard RBs showing BLER vs SNR for various CFO levels.](da0d310d0e9ecc6bfd61fe15aad963aa_img.jpg) + +This plot shows the BLER versus SNR for FSK1 with 12SC guard RBs. The axes and legend are identical to the previous plot. The performance is similar, with all curves showing a sharp decrease in BLER as SNR increases. The 'No CFO' curve reaches a BLER of 10-3 at approximately -1.5 dB SNR. + +Plot for FSK1 with 12SC guard RBs showing BLER vs SNR for various CFO levels. + +**d) ASCS guard RB evaluation for FSK-1** + +![Plot for FSK2 with 6SC guard RBs showing BLER vs SNR for various CFO levels.](ddfefccc6c2fcfadf4e398109548faf8_img.jpg) + +This plot shows the BLER versus SNR for FSK2 with 6SC guard RBs. The axes and legend are identical to the previous plots. The performance is similar, with all curves showing a sharp decrease in BLER as SNR increases. The 'No CFO' curve reaches a BLER of 10-3 at approximately -4 dB SNR. + +Plot for FSK2 with 6SC guard RBs showing BLER vs SNR for various CFO levels. + +![Plot for FSK2 with 12SC guard RBs showing BLER vs SNR for various CFO levels.](c9c3809709886a056c616a3aaece0c6d_img.jpg) + +This plot shows the BLER versus SNR for FSK2 with 12SC guard RBs. The axes and legend are identical to the previous plots. The performance is similar, with all curves showing a sharp decrease in BLER as SNR increases. The 'No CFO' curve reaches a BLER of 10-3 at approximately -4 dB SNR. + +Plot for FSK2 with 12SC guard RBs showing BLER vs SNR for various CFO levels. + +**e) ASCS guard RB evaluation for FSK-2** + +**Figure 7.1.2.3-3: ASCS guard RB evaluation** + +Less guard RB is required for ASCS compared to ACS between LP-WUS and NR signals. Considering frequency offset impact, guard RB with the size of one 15kHz SCS RB could provide necessary protection of LP-WUS from interference of adjacent NR sub-carriers. + +[7B-7],[7B-9] + +For ASCS, it can be observed that 1st order filter performs worst while and even with adding 6 guard RBs, the link performance only slightly improves., This means that guard RB does not considerably help if filter order is so low in WUR implementation. For higher than 2nd and 3rd order, the needed Guard RB is not obvious. In simulated link performance vs # RB for 3rd order filter in Figure 7.1.2.3-4, the SNR improvement for 2 RB is 0.2 dB. + +![Two line graphs showing BER vs SNR for OOK1 modulation. The left graph is for a 2nd order filter with 5 MHz BW, and the right graph is for a 5 MHz WUS bandwidth. Both graphs show performance for different guard band (GB) configurations: no GB, 1 RB GB (total), 2 RBs GB, 4 RBs GB, and 6 RBs GB. The curves show that as the guard band increases, the BER performance improves, especially at higher SNR values.](e0113695dbf148bf5ec34354e544414b_img.jpg) + +Two line graphs showing BER vs SNR for OOK1 modulation. The left graph is for a 2nd order filter with 5 MHz BW, and the right graph is for a 5 MHz WUS bandwidth. Both graphs show performance for different guard band (GB) configurations: no GB, 1 RB GB (total), 2 RBs GB, 4 RBs GB, and 6 RBs GB. The curves show that as the guard band increases, the BER performance improves, especially at higher SNR values. + +**Figure 7.1.2.3-4: Link performance for ASCS selectivity with different filter order** + +If the filter order is higher than and equal to 2, smaller guard RB (1 to 2 RB) is sufficient between adjacent subcarrier of eMBB signal and a WUS signal. If the filter order is too low, the guard RB does not help to improve the ASCS selectivity. + +To investigate the ADC impact on the ASCS, the below simulation with different ADC setting is assumed. The following ADC parameters are used: + +ADC number of bit [2, 4, 6, 8] and ADC sampling rate [down sampling factor 4, 8, 16, 32] + +It can be observed that generally there is SNR degradation when sampling rate down-sampling factor is increased from 4 to 32 for the same number of ADC bits and the same BPF order. Such SNR degradation is most prominent for ADC 2 bit case where 1.8 dB SNR degradation is observed in 7.1.2.3-5. Higher ADC bits can reduce the SNR degradation. For example, for ADC bits of 4, 6 and 8, the SNR degradation is around 1 dB. With Higher BPF order ( $\geq 6$ ), SNR degradation can be further reduced to around 0.5 dB. + +![Two line graphs showing BLER vs SNR for OOK1 modulation. The left graph is for filter order 2, and the right graph is for filter order 6. Both graphs show performance for different ADC bit settings (2, 4, 6, 8) and down-sampling factors (4, 32). The curves show that higher ADC bits and lower down-sampling factors result in better BLER performance. The degradation is more significant for filter order 2 and 2-bit ADCs.](288a76ff69a5008dc84b35f1587f2896_img.jpg) + +Two line graphs showing BLER vs SNR for OOK1 modulation. The left graph is for filter order 2, and the right graph is for filter order 6. Both graphs show performance for different ADC bit settings (2, 4, 6, 8) and down-sampling factors (4, 32). The curves show that higher ADC bits and lower down-sampling factors result in better BLER performance. The degradation is more significant for filter order 2 and 2-bit ADCs. + +**Figure 7.1.2.3-5: Link performance for ASCS selectivity for filter order 4 and 6 when ADC impairment is enabled.** + +[7B-10] + +Link-level simulations to evaluate the required guard RBs for ASCS were performed based on the assumptions as listed in Table 7.1.2.3-7. Simulations were done for OOK1 and OOK4 modulation. Simulations were repeated for different filter order, guard RBs, and residual frequency error. SNR required to achieve 1% BLER are reported in the following tables. + +**Table 7.1.2.3-7: LP-WUS link-level simulation parameters.** + +| Attributes | Assumptions | | +|-------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------|--------------------------| +| Carrier Frequency | 2.6 GHz | | +| Case name | OOK-1 waveform | OOK-4 waveform | +| Channel structure | data: 6 bits CRC: 8 bits | data: 20bits CRC: 8 bits | +| Chip rate | M=1 | M=2 | +| WUS duration | 28 symbols | | +| Waveform | OOK -1/OOK-4 | | +| Coding | 1/2 rate Manchester coding | | +| Time error | 0 | | +| residual Frequency error | 0/10/20/50/200 ppm | | +| SCS | 30kHz | | +| gNB Channel BW | 20MHz (50 RB) | | +| WUS BW | 12RB ~ 4.32MHz | | +| Position within channel | Center | | +| Guardband of NR channel, both wanted cell and interfer cell (ACS) | 27RE~810kHz for wanted cell1 20MHz (5MHz WUS at edge), and 510kHz for interference cell2 5MHz. | | +| Guard RB | Outer GB:2/1RB on each side of LP-WUS bandwidth (2 RB for ACS)
Inner GB: 4RE between segments | | +| Filter | 3th/5th Order lowpass Butterworth with 4.32MHz bandwidth | | +| ASCS | PDSCH mapped on RBs not used for LP-WUS and Guard RB;
EPRE of PDSCH /EPRE of LP-WUS = 0 dB
Same PSD with WUS signal | | +| ADC bit width | No ADC. | | +| Phase noise | none | | +| Power boosting | 0dB for OOK-1/4 | | +| Channel Model | TDL-C 300 | | +| Performance metric | BLER 1% | | + +**Table 7.1.2.3-8: SNR required for 1% BLER with 3rd order filter. Modulation used is OOK1.** + +| Guard RBs | CFO | | | | | | +|-----------|---------|----------|----------|----------|-----------|-----------| +| | ± 0 ppm | ± 10 ppm | ± 20 ppm | ± 50 ppm | ± 100 ppm | ± 200 ppm | +| 1 | 2.31 | 2.3 | 2.36 | 2.34 | 2.5 | 3.09 | +| 2 | 2.31 | 2.28 | 2.38 | 2.34 | 2.5 | 3 | + +**Table 7.1.2.3-9: SNR required for 1% BLER with 4th order filter. Modulation used is OOK1.** + +| Guard RBs | CFO | | | | | | +|-----------|---------|----------|----------|----------|-----------|-----------| +| | ± 0 ppm | ± 10 ppm | ± 20 ppm | ± 50 ppm | ± 100 ppm | ± 200 ppm | +| 1 | 2.28 | 2.28 | 2.34 | 2.31 | 2.5 | 3.09 | +| 2 | 2.28 | 2.27 | 2.34 | 2.33 | 2.48 | 2.97 | + +**Table 7.1.2.3-10: SNR required for 1% BLER with 5th order filter. Modulation used is OOK1.** + +| Guard RBs | CFO | | | | | | +|-----------|---------|----------|----------|----------|-----------|-----------| +| | ± 0 ppm | ± 10 ppm | ± 20 ppm | ± 50 ppm | ± 100 ppm | ± 200 ppm | +| 1 | 2.25 | 2.25 | 2.3 | 2.31 | 2.47 | 3.09 | +| 2 | 2.28 | 2.31 | 2.3 | 2.31 | 2.47 | 2.95 | + +**Table 7.1.2.3-11: SNR required for 1% BLER with 3rd order filter. Modulation used is OOK4.** + +| Guard RBs | CFO | | | | | | +|-----------|-------------|--------------|--------------|--------------|---------------|---------------| +| | $\pm 0$ ppm | $\pm 10$ ppm | $\pm 20$ ppm | $\pm 50$ ppm | $\pm 100$ ppm | $\pm 200$ ppm | +| 1 | 4.23 | 4.22 | 4.25 | 4.3 | 4.53 | 5.47 | +| 2 | 4.25 | 4.22 | 4.25 | 4.3 | 4.53 | 5.02 | + +**Table 7.1.2.3-12: SNR required for 1% BLER with 4th order filter. Modulation used is OOK4.** + +| Guard RBs | CFO | | | | | | +|-----------|-------------|--------------|--------------|--------------|---------------|---------------| +| | $\pm 0$ ppm | $\pm 10$ ppm | $\pm 20$ ppm | $\pm 50$ ppm | $\pm 100$ ppm | $\pm 200$ ppm | +| 1 | 4.19 | 4.19 | 4.22 | 4.25 | 4.5 | 5.44 | +| 2 | 4.2 | 4.19 | 4.22 | 4.25 | 4.5 | 5 | + +**Table 7.1.2.3-13: SNR required for 1% BLER with 5th order filter. Modulation used is OOK4.** + +| Guard RBs | CFO | | | | | | +|-----------|-------------|--------------|--------------|--------------|---------------|---------------| +| | $\pm 0$ ppm | $\pm 10$ ppm | $\pm 20$ ppm | $\pm 50$ ppm | $\pm 100$ ppm | $\pm 200$ ppm | +| 1 | 4.19 | 4.17 | 4.22 | 4.25 | 4.53 | 5.47 | +| 2 | 4.19 | 4.19 | 4.2 | 4.25 | 4.53 | 5 | + +Based on the above presented data, following observations can be made: One PRB worth of guard RB with 30 kHz SCS is enough, provided the CFO is under $\pm 100$ ppm. However, in case of $\pm 200$ ppm of residual frequency error, there is a minor improvement in the required SNR by an additional guard RB. Given the low chip rate, filter order doesn't seem to impact performance, as in, given a modulation scheme, number of guard RBs and residual frequency error, increasing the filter order does not provide significant reduction in the required SNR. + +Therefore, in for 30kHz SCS one PRB worth of guard RB can be used. + +#### 7.1.2.4 Phase noise + +At WUR receiver, reciprocal mixing occurs when a high-power level adjacent interferer signal that is present at antenna mixes with the oscillator noise sideband (phase noise). The reciprocal mixing generates cochannel interference to the WUR receiver passband as illustrated in Figure 7.1.2.4-1. + +![Figure 7.1.2.4-1: Reciprocal mixing for ACI case. The figure consists of two diagrams. The left diagram, labeled 'No reciprocal mixing', shows a WUS signal at frequency f0 and an adjacent interferer (ACI) at frequency f1. The ACI signal has a large ACS (Adjacent Channel Selectivity) component. The right diagram, labeled 'Reciprocal mixing', shows the same WUS signal at f0 and ACI at f1, but with a phase noise sideband from the oscillator mixing with the ACI signal, resulting in a cochannel interference component at f0.](7a0777bbad359aeb869022b345b827ef_img.jpg) + +Figure 7.1.2.4-1: Reciprocal mixing for ACI case. The figure consists of two diagrams. The left diagram, labeled 'No reciprocal mixing', shows a WUS signal at frequency f0 and an adjacent interferer (ACI) at frequency f1. The ACI signal has a large ACS (Adjacent Channel Selectivity) component. The right diagram, labeled 'Reciprocal mixing', shows the same WUS signal at f0 and ACI at f1, but with a phase noise sideband from the oscillator mixing with the ACI signal, resulting in a cochannel interference component at f0. + +**Figure 7.1.2.4-1: Reciprocal mixing for ACI case** + +#### 7.1.2.5 gNodeB RF impacts + +The power boosting of 3 dB or 6 dB of a WUS signal relative to the average power of a configured NR carrier can improve the WUS signal coverage. It is beneficial to enable the 3dB or 6 dB power boosting at the existing network. Therefore, RAN4 assumes to reuse the legacy RF specification as a starting point. Some company observed that 3 dB or 6 dB power boosting for a 24 RB WUS signal may not be feasible for some of deployed gNB when average power is kept the same before and after power boosting. It is feasible to configure different PSD carriers in a multiple carrier + +configuration where WUS signal can be placed in a higher PSD carrier among all configured carriers. The amount of boosting is up to manufacturer declaration following the legacy manufacturer declaration. + +BS manufacturer could declare if power boosting for WUS signal is supported and the boosting level in the range of [0] to [6] dB is considered. Final power boosting level and the condition of power boosting will be decided based on further analysis in WI phase. + +#### 7.1.2.6 Multi-band capability + +RF envelop detection architecture is more appropriate for single-band operation. IF envelop detection and BB envelop detection are more appropriate for multi-bands operation. Multi-band here still means that only one band at a time is being received. Multi-band capability for other architectures is FFS. + +#### 7.1.2.7 Noise Figure + +RAN4 noticed that the assumed NF in RAN1 simulation may be different with RAN4. RAN4 will derive RF requirement based on NF which is feasible from coverage and implementation perspective. RAN4 will focus on sensitivity evaluation instead of specific NF value in the normative work. + +Generally, noise figure and power consumption are competing specifications, it is very challenging to achieve both low noise figure and low power consumption at the same time, and power consumption typically increases when sensitivity is improved. There is a delicate balance between lower power consumption, e.g., higher noise figure, and system performance. + +#### 7.1.2.8 Band operation for LP-WUS + +RAN4 has discussed the band operation for LP-WUS according to the scenarios listed below with the understanding that the associated RF aspects could be analysed in the work item phase, depending on the scope of the related normative work. + +- 1) The band for the low-power radio (LR) and main radio (MR) can be the same, e.g., WUS is located within the NR band used for LP-WUR. In this scenario the WUS and NR DL could be multiplexed according to TDM/FDM modes. +- 2) The band for LR and MR can be different, e.g., WUS is located within an NR band for LP-WUR, and another NR band is used for the MR. + +Additionally, RAN4 has concluded the following aspects from RF perspective, which are provided for information: + +- WUS located in an SDO band in TS 36.101 is proposed by some companies, and RAN4 recognizes that there exist dependencies on other WGs that have not been considered in this study. + +Note: Some companies have expressed a concern that SDO bands may not be IMT bands. + +## 7.2 LP-WUS design and L1 procedure + +- When evaluating and/or comparing link performance of MC-ASK, MC-FSK, and CP-OFDMA waveforms of LP-WUS at least + - raw information bit-size + - Alt 1: + - average EPRE within the [time]/frequency resources used for LP-WUS (including any guard bands) + - time/frequency resources used for LP-WUS (including any guard bands) + - Alt 2: + - average EPRE within the [time]/frequency resources used for LP-WUS (including any guard bands) + - FFS: false alarm probability/rate + +- FFS: misdetection probability/rate +- are kept [comparable or fixed]. +- Study at least + - impact of timing error + - impact of frequency error + - impact of phase noise and I/Q imbalance, if applicable + - impact of ADC resolution and sampling rate + - impact of interference + - impact of delay spread + - impact of doppler spread + - Companies to report + - how they modelled SINR + - SNR is calculated as average EPRE divided by power of noise [and interference]. + - whether and how power pooling across and within MR OFDMA symbols is used. + - FFS: PAPR applicable to LP-WUS + - time/frequency resources (including any guard bands) for the scheme + - false alarm probability/rate and misdetection probability/rate + - receiver architecture type and its relative power consumption + - When comparing waveforms of LP-WUS, consider the impact to gNB for each of the waveform generation schemes. Consider whether there is impact to PAPR and a need for additional hardware for WUS. + +### 7.2.1 Signal design + +#### 7.2.1.1 Waveform + +- Study generation and link performance of multi-carrier (MC)-ASK (including OOK) waveform + - study techniques to generate waveform by modulating sub-carriers of CP-OFDM symbol, consider up to M bits transmitted per OFDM symbol, where M is FFS. + - Note that above does not preclude DFT-S-OFDMA +- Study generation and link performance of multi-carrier (MC)-FSK waveforms + - study techniques to generate waveform by modulating sub-carriers of CP-OFDM symbol symbol, consider up to M bits transmitted per OFDM symbol, where M is FFS. +- Study link performance of OFDMA-based signals/channels considering at least the existing signal/channel structure (e.g. CSI-RS, SSS) + - Other signal/channel structures are not precluded + +For MC-ASK or MC-FSK waveform generation, SCS of a CP-OFDM symbol used for LP-WUS generation can be the same as SCS used for other NR transmissions in CP-OFDM symbol overlapping in time with, study whether SCS can be different, also study + +- FDM/TDM multiplexing with other NR transmissions + +- link performance +- impact to legacy UEs +- impact on gNB + +For waveform generation the following observations are made + +- Flat spectrum in frequency domain provides robustness against frequency selective fading compared to concentrated energy in frequency domain. + - for OOK-4, sequence before DFT/LS with variation in phase via such as ZC, M-sequence or QAM sequence can achieve more flattened spectrum. +- Sequence(s) used in LP-WUS symbol generation with different pulse shape or spectral shape may have different performance. +- Knowledge of sequence(s) used in LP-WUS waveform generation may improve performance for at least a receiver with I/Q branches + +Further discuss the following potential observations for waveform generation: + +- When DFT is employed in OOK-4 ( $M \geq 2$ ), -1/1 alternation in time or frequency shift in frequency domain may be needed to match CP-OFDM generation. +- Pre-storing of the generated frequency domain samples at gNB may reduce complexity of waveform generation at gNB with memory requirement depending on number of possible combination. This may be up to gNB implementation. +- Quantization of generated waveform in frequency domain to existing constellation (e.g. 64QAM) has low impact on performance and reduces complexity. This may be up to gNB implementation. +- Repetition of a sequence(s) used in LP-WUS generation in frequency can be used to improve diversity for MC-OOK and robustness against frequency offsets for MC-FSK. + +##### 7.2.1.1.1 MC-ASK waveform + +For MC-ASK waveform generation, where $K$ is size of iFFT of CP-OFDMA, $N$ is number of SCs used by LP-WUS including potential guard-bands, study further + +- Option OOK-1: Single-bit in 1 OFDM symbol, SCs of LP-WUS are + - OOK=1 means all SCs are modulated + - OOK=0 means all SCs are zero power (from base-band point of view) + +![Diagram illustrating the MC-ASK waveform generation process. On the left, two input signals are shown: 'Legacy NR signal' and 'LP-WUS 0..(N-1)'. The 'Legacy NR signal' is connected to an 'iFFT + CP' block via a path labeled 'SC#K-1'. The 'LP-WUS' signal is connected to the same 'iFFT + CP' block via a path labeled 'SC#1' and 'SC#0'. The output of the 'iFFT + CP' block is a '1 OFDM symbol' waveform, which is a step-like signal with a constant amplitude for the first part and zero for the second part.](d7efe1d3c9fce95c7bacefb7e7d7faff_img.jpg) + +Diagram illustrating the MC-ASK waveform generation process. On the left, two input signals are shown: 'Legacy NR signal' and 'LP-WUS 0..(N-1)'. The 'Legacy NR signal' is connected to an 'iFFT + CP' block via a path labeled 'SC#K-1'. The 'LP-WUS' signal is connected to the same 'iFFT + CP' block via a path labeled 'SC#1' and 'SC#0'. The output of the 'iFFT + CP' block is a '1 OFDM symbol' waveform, which is a step-like signal with a constant amplitude for the first part and zero for the second part. + +- Option OOK-2: Parallel M-bit OOK in frequency domain, + - $N$ SCs of LP-WUS is further separated into $M$ segments ( $M=2$ in Figure) possibly with guard-bands in-between and/or around + - OOK=1 means all SCs in segment are modulated + - OOK=0 means all SCs in segment are zero power (from base-band point of view) + +- OOK-2 can be received using the agreed receiver architectures for OOK with parallel envelope detection. + +![Diagram for OOK-2 showing the mapping of Legacy NR signal segments to subcarriers for an iFFT + CP block. The input is divided into two segments: n=0..N/2-1 (mapped to subcarriers SC#0 to SC#1) and n=N/2..N-1 (mapped to subcarriers SC#K-1). The output is a single OFDM symbol.](343e05a9fd8a8c8743428fa4ae6e2736_img.jpg) + +Diagram for OOK-2 showing the mapping of Legacy NR signal segments to subcarriers for an iFFT + CP block. The input is divided into two segments: n=0..N/2-1 (mapped to subcarriers SC#0 to SC#1) and n=N/2..N-1 (mapped to subcarriers SC#K-1). The output is a single OFDM symbol. + +###### - Option OOK-3: Multi-tone single-bit OOK + +- N SCs of LP-WUS is separated into L segments ( $L=2$ on Figure) without guard-bands in-between segment, but possibly around +- OOK=1 means 1 sub-carrier (known by UE) of each segment is modulated, rest of SC is zero power (from base-band point of view) +- OOK=0 means all SCs in all segments are zero power (from base-band point of view) +- receiver architecture refers to clause 7.1.1-F + +![Diagram for OOK-3 showing the mapping of Legacy NR signal segments to subcarriers for an iFFT + CP block. The input is divided into two segments: l=0 (n=0..N/2-1, mapped to subcarriers SC#0 to SC#1) and l=1 (n=N/2..N-1, mapped to subcarriers SC#K-1). The output is a single OFDM symbol.](ada2aa7cce9cff9cf116d9ae2b8b7c27_img.jpg) + +Diagram for OOK-3 showing the mapping of Legacy NR signal segments to subcarriers for an iFFT + CP block. The input is divided into two segments: l=0 (n=0..N/2-1, mapped to subcarriers SC#0 to SC#1) and l=1 (n=N/2..N-1, mapped to subcarriers SC#K-1). The output is a single OFDM symbol. + +###### - Option OOK-4: Transform M-bit OOK in time domain + +- N SCs of OOK-1 are generated by a transformation (DFT/Least square) +- N' samples are generated from M-bits +- signal modification may or may NOT be used +- truncation or other additional modification may or may NOT be used, if not used, N is the same as N' +- N' can be the same as K + +![Diagram for OOK-4 showing the signal processing flow. It starts with LP-WUS time 0..(N-1) and M=4 bits (e.g., 1001). These are processed through 'Signal generation and modification n', 'DFT/Least Square', and 'Truncation N->N and modification' to produce LP-WUS 0..(N-1). This LP-WUS signal is then combined with a 'Legacy NR signal' and processed by an 'iFFT + CP' block to produce the final '1 OFDM symbol including CP'.](01465752f3ac36c403672804f406a676_img.jpg) + +Diagram for OOK-4 showing the signal processing flow. It starts with LP-WUS time 0..(N-1) and M=4 bits (e.g., 1001). These are processed through 'Signal generation and modification n', 'DFT/Least Square', and 'Truncation N->N and modification' to produce LP-WUS 0..(N-1). This LP-WUS signal is then combined with a 'Legacy NR signal' and processed by an 'iFFT + CP' block to produce the final '1 OFDM symbol including CP'. + +- FFS modulated SCs are e.g. QAM symbols, sequences or other signals + +- Companies to report their assumptions +- potential guard-band SCs are zero power (from base-band point of view) +- optionally, 2 additional segments, one always modulated and one always zero power (from baseband point of view) can be transmitted +- Other options are not precluded (e.g. OOK-1 with multiple bits in one OFDM symbol) + +Study further methods to modulate input signal of the DFT/Least-Square block for OOK-4, and methods to modulate input signal of N SCs for other MC-ASK/FSK schemes + +- study methods with respect to + - improving frequency diversity by flattening the spectrum, frequency repetition and frequency hopping + - impact to dynamic range of RE power in frequency domain + - FFS: impact to PAPR of generated time domain modulated MC-ASK/FSK symbol + - improving robustness to timing error necessary spectrum adjustment for compatibility with CP-OFDM generation + +##### 7.2.1.1.2 FSK waveform + +For M-bit MC-FSK generation study further the following options + +- Option FSK-1: N SCs of LP-WUS are separated to M pairs of segments with potential guard-bands in-between and around. + - segment comprises one sub-carrier or multiple contiguous SCs + - in a pair of segments one segment is modulated, other segment is zero power (from base-band point of view) +- Option FSK-2: N SCs of LP-WUS are separated to $2^M$ segments with potential guard-bands in-between and around. + - segment comprises one sub-carrier or multiple contiguous SCs + - one segment from $2^M$ segments is modulated, other segments of SCs are zero power (from baseband point of view) +- $M > 0$ +- $N > 1$ +- Study how to generate segment in time domain, e.g. OOK-1 or OOK-4 +- Other options are not precluded. + +In FSK2-envelope-IF waveform generation, the N SCs of LP-WUS can be used to generate $2^M$ segments at the envelope of the LP-WUR's received signal in baseband where each segment comprises one or more tones. + +##### 7.2.1.1.3 OFDM waveform + +#### 7.2.1.2 Bandwidth and location + +For the purpose of study, the BW of one LP-WUS is not greater than X (FFS X is 5 or 20) MHz for FR1, study further + +- whether BW of LP-WUS is configurable (implicitly or explicitly) +- size of guard band [FFS: within or outside of BW X], if any + +- whether there is different X for Idle, Connected, Inactive modes + +FFS: Whether FR2 is included in the scope of LP-WUS SI + +- From RAN1 perspective, LP-WUS and signals/channels used by MR can be within the same FR1 band. + - At least LP-WUS and signals/channels by MR can be on the same carrier in the band +- Study further + - Whether LP-WUS and signals/channels used by MR can be different carriers in the band + - Details on the LP-WUS location within a carrier + - Band can be different than band of signals/channels used by MR + - LP-WUS association with BWP + - LP-WUS can be configurable within guard-band of a band (like NB-IoT) +- Study RRC connected mode LP-WUS BW, whether same as IDLE/Inactive mode or different + +At least for IDLE/Inactive mode, at least one BW-size $\leq 5\text{MHz}$ is recommended to be supported for FR1 + +- Other BW sizes are not precluded + - if additional BW-size(s) are recommended to be supported, BW-size can be up to 20MHz +- LP-WUS bandwidth size (including guard-bands) is assumed to be an integer number of PRBs + +From RAN1 perspective, for multiplexing with other NR signals and channels, it is beneficial if LP-WUS can be flexibly configured within a carrier. + +#### 7.2.1.3 LP-WUS content + +- For IDLE/INACTIVE mode study at least following candidates for content of LP-WUS + - information on which user(s) is/are targeted by the LP-WUS + - e.g. UE-group, -subgroup or -ID + - FFS: cell information + - FFS: SI change and ETWS/CMAS information, tracking area information, and RAN area information +- For CONNECTED mode, study at least following candidates for content of LP-WUS + - information on which user(s) is/are targeted by the LP-WUS + - e.g. UE-group, -subgroup or -ID + - indication to wake-up to PDCCH monitoring. +- Other information candidates are not precluded +- Study pros and cons of including above information to LP-WUS. +- Note: the information may be explicitly or implicitly indicated. +- Study further following alternatives to carry the LP-WUS information using: + - Alt 1: by sequence(s) detection/selection + - FFS sequence type + - Alt 2: by encoded bits + +- FFS: what type of encoding scheme +- FFS: with or without other bits (e.g. CRC/FCS) +- Other alternatives are not precluded +- Study whether LP-WUS information needs to be preceded by known one or more sequence(s). + +### 7.2.2 L1 procedures + +#### 7.2.2.1 RRM measurements + +Study potential measurement metric used for RRM measurements performed by LP-WUR. + +- examples of measurement metric are signal quality, signal power, detection rate of LP-WUS/synch signal +- companies to report assumption of signal used for measurements + +For at least RRM serving cell measurement performed by LP-WUR based on reference signal(s), RAN1 identified at least the following metrics for further study and evaluation (including feasibility, complexity, power consumption, etc) + +- LP-RSSI or Energy detection: linear average of total received power over a RSSI resource. + - FFS RSSI resource. +- LP-RSRP: linear average of received power of resource of reference signal(s) or signal(s) parts. + - FFS resource of reference signal(s) or signal(s) parts +- LP-SINR = LP-RSRP/(power of interference and noise) + - FFS how to define "power of interference and noise" +- LP-RSRQ= $[N \times] LP-RSRP/LP-RSSI$ , where N is the factor of resource size difference for evaluation LP-RSRP and LP-RSSI. +- Accounting AGC accuracy, ADC of at least 4 bits is required. + +Note: Reference signal for performing measurements can be e.g. SSB (PSS/SSS/PBCH DMRS), LP-WUS-waveform sequence, LP-SS + +Note: The definition of metrics could be further refined based on future study + +##### **RRC IDLE/INACTIVE mode** + +For a UE support LP-WUR in IDLE/INACTIVE mode, + +- Study how to reduce UE power consumption due to existing RRM measurement requirements at least for mobility support, + - study feasibility of RRM measurements performed by LP-WUR, at least for serving/camping cell, based on signals detected by LP-WUR + - FFS: measurement metric + - FFS: whether and how to identify cell/ tracking area + - FFS: need for neighbouring cells + - FFS: need for relaxation of existing RRM measurement requirements (for UE) +- For Idle/Inactive mode, study offloading of RRM measurements of serving cell to LP-WUR under certain conditions, if any, and relaxation of serving/neighboring cell RRM measurements in MR considering + +- Periodic reference signal(s) is/are used for LR measurements. + - FFS: reference signal(s) to measure, e.g. PSS/SSS/PBCH DMRS, LP-WUS waveform sequence, LP-SS + - FFS: periodicity, content +- MR performs measurements + - Alt2: with relaxed periodicity if RRM measurement in MR is relaxed. + - FFS: Condition for relaxation if any + - Can apply for both neighboring and serving cell + - Alt3: only when reference signal(s) based measurements by LP-WUR satisfy certain condition(s), e.g. are below threshold. + - FFS threshold. + - Above MR measurement under certain conditions can apply for both neighboring and serving cell + - Potentially with relaxation methods for MR neighboring cell measurement + - Other alternatives are not precluded +- FFS: Feasibility of RRM measurements of neighbour cells by LP-WUR + +The followings are observed, + +- At least for LP-WUR that cannot receive existing PSS/SSS, periodic LP-SS signal is beneficial for the following functionality. + - RRM measurements by LP-WUR, if supported + - at least coarse time synchronization of LP-WUR. + - at least coarse frequency synchronization of LP-WUR. +- Additional periodic LP-SS system overhead depends on LP-SS periodicity, system BW, # of beams, and resource required to fulfil the target functionality, etc. Periodic signal if used for coarse synchronization may reduce overhead of signal preceding LP-WUS, if any. LP-SS can be designed to be common among UE groups (cell-specific) and such further reduce system overhead. +- For LP-WUR that can receive existing PSS/SSS potentially assisted by PBCH DMRS/TRS for synchronization, existing PSS/SSS potentially assisted by PBCH DMRS/TRS may be used for above functionality. +- Periodic LP-SS coverage should be equal to or better than that of LP-WUS. +- For fine time and frequency synchronization, a signal (e.g. preamble) preceding or part of LP-WUS may be used. + +##### **RRC CONNECTED mode** + +Additional descriptions for RRM RRC CONNECTED mode can be found in 7.2.2.6. + +#### **7.2.2.2 Synchronization of LP-WUR** + +Study synchronisation signal used by LP-WUR, if needed, based on + +- Option 1: aperiodic signal transmitted as part of LP-WUS + - FFS: Whether the signal can additionally be transmitted separately from LP-WUS +- Option 2: periodic signal transmitted separately from LP-WUS + +- Option 3: Option1 + Option2 + +Additional description of synchronization of LP-WUR can be found in 7.2.2.1. + +#### 7.2.2.3 LP-WUS monitoring + +Study further pros and cons of the following monitoring behaviours of LP-WUR + +- Option1: Duty cycle, corresponds to LP-WUR switches between ON/OFF states +- Option2: Continuous monitoring, corresponds to LP-WUR is ON all the time + +#### 7.2.2.4 Activation/Deactivation procedures of LP-WUS + +- Study RRC connected mode LP-WUS activation/deactivation procedures. +- For Idle/Inactive mode, following options for activation and deactivation of LP-WUS monitoring by LP-WUR for a UE can be considered for study + - Alt 1a: + - gNB transmits legacy paging indication and LP-WUS + - UE activation and/or deactivation of LP-WUS WUS monitoring is up to UE implementation. + - This behavior may apply based on channel condition, e.g. when coverage is sufficient/insufficient. + - Alt 1b: + - gNB transmits legacy paging indication and LP-WUS + - UE activation and/or deactivation of LP-WUS monitoring is based on preconfigured criteria + - This behavior may apply based on channel condition, e.g. when coverage is sufficient/insufficient. + - Alt 2: + - activation and/or deactivation of LP-WUS monitoring in a cell is based on signalling. + - Paging misdetection performance shall not be impacted. +- In RRC CONNECTED mode, LP-WUS monitoring can be activated/deactivated by at least one or more of + - by gNB RRC signaling, with or without UE assistance. + - by gNB L1/L2 LP-WUS activation/deactivation signaling, with or without UE assistance. + - based on pre-configured condition(s), such as timer. + - LP-WUS monitoring by UE is known to gNB, study whether it could be transparent to gNB. + - other options are not precluded. + +#### 7.2.2.5 Coverage + +- Study techniques/mechanisms to enhance coverage performance of LP-WUS +- Study potential gains available as well as drawback(s) of the technique(s)/mechanisms(s), e.g. system overhead, increased complexity network energy consumption etc... +- Study potential issues and corresponding solutions for the case when LP-WUS coverage is insufficient + - At least study fallback mechanisms where the Main Radio switches to legacy operation in case the channel condition of LP-WUS is not sufficient, e.g. below threshold. +- Study the following techniques/mechanisms to enhance coverage performance of LP-WUS + +- low complex channel coding + - FEC + - spreading code in time domain + - time domain repetition + - with combining before or after ED + - time-domain interleaving + - Note: Also Manchester coding can be considered as channel code +- non-contiguous transmission in the frequency domain +- frequency domain repetition +- frequency-hopping +- power-boosting +- transmit diversity +- study whether any above techniques could be transparent to UE. + +#### 7.2.2.6 Additional L1 procedures for RRC CONNECTED mode + +- Study RRC connected mode LP-WUS functionality/purpose/procedures +- In RRC connected, study the relationship between LP-WUS and legacy UE power saving techniques. +- In RRC CONNECTED mode, study benefit of LP-WUS over existing Rel-15, R16, and R17 power saving techniques for following functionalities: + - LP-WUS with similar functionality as R16 DCP. + - LP-WUS activates/resumes PDCCH monitoring when LP-WUS is received. + - interaction with legacy power saving techniques, if any + - other functionalities are not precluded + - for evaluation + - companies to report + - assumption on MR sleep state when LP-WUR is monitoring LP-WUS + - deep sleep, + - light sleep, + - micro sleep + - how to activate/deactivate LP-WUS monitoring and deactivate/activate PDCCH monitoring + - LP-WUS waveform +- For RRC connected mode, the following is assumed for LP-WUS study in RAN1 + - RLM/BFD/CSI are performed by UE Main Radio (MR) + - RRM measurements are performed by UE Main Radio (MR) + - Ultra-deep sleep state is not allowed for MR. +- Study additional support of RRM measurement by LP-WUR for RRC connected mode + +#### 7.2.2.7 Additional L1 procedures for RRC IDLE/INACTIVE modes + +#### 7.2.2.8 Others + +## 7.3 Higher-layer aspects + +### 7.3.1 RRC\_IDLE/INACTIVE mode + +#### 7.3.1.1 RRC\_IDLE/INACTIVE mode procedures + +In RRC\_IDLE and RRC\_INACTIVE states, UEs shall perform RRC\_IDLE/INACTIVE mode procedures defined in TS 38.304 and TS 38.331, which specify how UEs shall monitor paging, keep system information up to date, receive ETWS/CMAS information, and perform RRM measurements and corresponding cell selection/re-selection to ensure that UE is camping on the best cell. These procedures may need to be modified to accommodate operation using LP-WUS/WUR. + +Though the network may use different signals to page UE for the case that UE monitors LP-WUS and the case that UE doesn't monitor LP-WUS, the network doesn't need to be aware of whether the UE is monitoring LP-WUS or not in RRC\_IDLE/RRC\_INACTIVE. Otherwise, it requires the UE to switch on MR or wake up MR to inform the network whether the UE is monitoring LP-WUS or not, which leads to further signalling overhead, Uu resource consumption and also UE power consumption accordingly. + +With LP-WUS/WUR, the Main Receiver (MR) of a UE could enter ultra-deep sleep state, which denotes a state when the MR may sleep or turn off. Such ultra-deep sleep state could be entered when predefined condition (e.g. quality of LP-SS and/or SSB is better than the threshold) is fulfilled. An operation like the one for Mobile Initiated Communication Only (MICO), where both monitoring of the downlink and RRM measurements are stopped until there is a subsequent uplink transmission, is however not feasible for LP-WUS/WUR. The point with LP-WUS/WUR is to reduce UE power consumption while maintaining some downlink monitoring functionality, and this is not possible if either the UE stops monitoring in downlink or if the UE does not detect that it has moved into a new cell/area and therefore apply the incorrect configuration for downlink monitoring. According to TS 38.300, the functionality to be supported over Uu interface in RRC\_IDLE and RRC\_INACTIVE includes PLMN selection, SI reception, cell re-selection mobility, and paging, etc. Therefore, it is feasible to introduce LP-WUS/WUR as a power saving feature for RRC\_IDLE and RRC\_INACTIVE, while ultra-deep sleep state as a power saving state for RRC\_IDLE and RRC\_INACTIVE. + +#### 7.3.1.2 LP-WUS monitoring and wake up procedure + +Paging reception in RRC\_IDLE and RRC\_INACTIVE is supported both with discontinuous reception (DRX), and from Rel-17 and Rel-18, respectively, with extended DRX (eDRX). LP-WUS/WUR could also be supported with or without duty-cycled operation, i.e., as 'continuous' or as 'duty-cycled'. Since the LP-WUS/WUR feature is introduced to lower the UE energy consumption, it is for these two options feasible to introduce support for the LP-WUR option which can introduce the greatest UE energy consumption reduction compared to baseline as discussed above in section 6. If the gain is similar, the magnitude of implementation complexity, specification impact, and latency impact should be the determining factors for which LP-WUR option to support. + +Currently, paging monitoring in RRC\_IDLE/INACTIVE mode is based on the configured I-DRX, as well as PEI is also designed as 'duty-cycled' associated with legacy PO. The specification impact for 'continuous' and 'duty-cycled' depends on the detailed design. While, a potential benefit of 'continuous' is shorter downlink latency. That is, since the UE monitors the downlink continuously the downlink latency could potentially be shorter. + +Due to the transition time to start up the main receiver however, LP-WUR operation may always have worse latency performance than legacy, i.e., comparing to legacy continuous monitoring or DRX. 'Continuous' could still provide shorter downlink latency compared to 'duty-cycled', comparing at the same UE energy consumption reduction gain. This however depends on the UE procedure triggered by LP-WUS and the LP-WUS payload content and size. + +On one hand, after waking up by LP-WUS, the legacy paging monitoring procedure could be triggered for the main receiver. That is, if the UE detects LP-WUS it would start up its main receiver to monitor legacy paging, i.e., the PDCCH scheduling of the paging message on PDSCH, and at first after finding its own *PagingRecord* in the paging message the UE could determine that it is being paged (similar to Rel-15 WUS for NB-IoT/LTE-M or Rel-17 PEI). In this case, the downlink latency will be determined by the periodicity of the legacy paging occasions (POs). + +- In some case, 'continuous' mode may not have latency benefit compared to 'duty-cycled'. That is, even if LP-WUS is immediately received using 'continuous' mode the UE might anyway need to wait for the subsequent PO (i.e., maybe a same PO as if 'duty-cycled' is used). +- In some other case, the beneficial part comes from the margin that LP-WUS could be received earlier in case 'continuous' than 'duty-cycled', which would wake up the main receiver earlier and an earlier PO will be monitored by main receiver after waking up by LP-WUS. +- On the other hand, after waken up by LP-WUS, the main receiver could also monitor legacy PEI defined in Rel-17, if it is configured by network and it is supported by UE. Especially for the case that LP-WUS doesn't have full coverage compared to legacy signalling, e.g. SSB, main receiver needs to wake up to perform legacy operation out of LP-WUS coverage. In this case, network could still configure PEI for the use of fallback mechanism to save UE power consumption for paging monitoring. It means, the network would configure and transmit both LP-WUS and PEI for the UE, especially when the network is not aware of UE's entry/exit of LP-WUS monitoring. From UE perspective, LP-WUS may be used together with PEI if both LP-WUS and PEI are configured, to achieve more power saving gain. + +The corresponding pros/cons of the above UE wake up procedures are listed as below: + +**Table 7.3.1.2-1: Pros and Cons of different alternatives for wake-up procedures** + +| | Alt1.1: LP-WUS+ Paging | Alt 1.2: LP-WUS+PEI+paging | +|-----------------------------|-------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------| +| Access latency | LP-WUS reception+ paging reception+ random access procedure | LP-WUS reception + PEI reception + paging reception +random access procedure | +| False Alarm | Can be reduced by use of UE subgrouping for LP-WUS. | Unclear if and how it can be further reduced if UE subgrouping mechanism is used in LP-WUS and PEI together. | +| Complexity of LP-WUS Design | Low | It is higher if UE subgrouping mechanism is used in LP-WUS and PEI together | +| Integration with legacy | Smooth as LP-WUS replaces PEI | Unclear what PEI functionality adds on top of LP-WUS | + +After waking up from LP-WUS, in case UE needs to monitor PO, the time offset between LP-WUS and the PO should be long enough to include the transition time to start up the main receiver to be ready for PDCCH monitoring, which depends on the design of LP-WUR and the detailed procedure after waking up. After waking up from LP-WUS, some PO(s) needs to be monitored. Whether there is association between LP-WUS and PO, and how to define the association if yes, depends on the detailed procedure. For reference, in legacy, Rel-17 PEI supports mapping of up to 8 POs (configured the parameter *po-NumPerPEI*), and Rel-15 WUS and Rel-16 GWUS for NB-IoT/LTE-M supports mapping of up to 4 POs, but only when the UE is configured with eDRX. + +Furthermore, after waking up from LP-WUS, either all UEs could be triggered to wake up to monitor paging in associated PO(s), or just a subset of the UEs sharing the PO, so called LP-WUS UE subgrouping. The latter can be used to reduce the negative impact from false paging, i.e., unnecessary energy consumption in the UE caused by paging intended for another UE. In the latter case, LP-WUS UE subgrouping information corresponding to 2 bits or more, would be indicated by LP-WUS. How to indicate the subgrouping information, e.g. included in the LP-WUS payload or from the use of multiple LP-WUS signals corresponding to different subgroups, etc., depends on the design of LP-WUS. For reference, both Rel-17 PEI and Rel-16 GWUS for NB-IoT/LTE-M support up 8 subgroups per PO (configured by the parameters *subgroupsNumPerPO* and *GWUS-NumGroups*, respectively). The number of subgroups depends on the decision on payload of LP-WUS + +Both these features rely on I-DRX and UEs already being distributed over the different POs in the cell, and the UE subgrouping therefore refers to further subgrouping of the UEs already divided into the same PO. This would be the same for 'duty-cycled' operation. For 'continuous' operation, UE should monitor the downlink continuously. false paging could apply to all UEs in the cell since all UEs are monitoring the downlink continuously. False paging would therefore be much more severe for 'continuous' and a larger number of LP-WUS/WUR UE subgroups would be required to achieve the same false paging rate. + +A summary of the impact from carrying a UE subgroup indication in the LP-WUS is given below. + +**Table 7.3.1.2-2: Impact from the inclusion of UE subgroup information in the LP-WUS payload.** + +| | UE subgroup indication in LP-WUS: | +|------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Procedure triggered by LP-WUS reception: | Legacy monitoring of paging in PO or PEI | +| gNB transmission upon paging: | LP-WUS and legacy paging (PDCCH+PDSCH). | +| False paging: | False paging among all UEs in the cell using 'Continuous', and among all UEs sharing a PO using 'duty-cycled'.
False paging is reduced by use of UE subgrouping and an increasing number of UE subgroups. | +| Latency impact: | DL latency determined by I-DRX cycle length and PRACH periodicity. | + +In Rel-17 PEI, two subgrouping methods were introduced, which includes: CN assigned and UE\_ID based subgrouping. For CN assigned subgrouping, UE's subgroup is assigned by CN taking into account the UE's characters, such as mobility pattern, paging probabilities, etc. While for UE\_ID based subgrouping, UE's subgroup is formed based on UE\_ID and the subgroup number in RAN. UE supporting CN assigned subgrouping in RRC\_IDLE or RRC\_INACTIVE state can be assigned a subgroup ID by AMF through NAS signalling. The UE belonging to the assigned subgroup ID monitors its associated PEI which indicates the paged subgroup(s). Paging with UE\_ID based subgrouping is used in the cell which supports UE\_ID based subgrouping. It is up to network configuration to determine which subgrouping should be used. + +Similar as PEI, the subgrouping methods for LP-WUS could include the CN assigned, and UE\_ID based subgrouping. Details, e.g. which one/both should be supported, how to support/provide the configuration, etc., could be further determined during WI phase. + +#### 7.3.1.3 LP-WUS coverage and trigger condition + +According to evaluation in section 8.2, LP-WUS link performance is considerably worse than legacy physical channels (e.g., PDCCH or PUSCH), and there could be partial LP-WUS coverage in the cell. Another possible scenario is LP-WUS could also have same coverage as legacy cell, while the details depend on the signalling and LP-WUR design. For the partial coverage case, UE may need to keep track of whether it moves in and out of LP-WUS coverage in the cell, this to be able to fall back to monitoring paging using the main receiver when the coverage of LP-WUS is not sufficient (see network awareness in 7.3.1.1 above). The UE could determine this based on the measured RSRP, e.g., compared to an RSRP threshold in system information. + +For the partial coverage case, UE's MR could stay in ultra-deep sleep power state only when UE is in the coverage of LP-WUS. When UE moves out of the coverage of LP-WUS, the network cannot wake up UE's MR via LP-WUS. Hence, UE should start up its MR when it moves out of the coverage of LP-WUS to avoid missing the paging message. In this way, one of the exit conditions for using LP-WUS or ultra-deep sleep power state should be that the UE is out of LP-WUS coverage. A quality threshold of target Reference Signal can be pre-configured to UE to define the exit condition for using LP-WUS. With this threshold, UE can stop using LP-WUS and exit the ultra-deep sleep power state when the quality of target Reference Signal is lower than the threshold. + +During ultra-deep sleep or when using LP-WUS, UE's MR may not perform measurement as per legacy procedures and requirements. Thus, in order to be applicable for all cases, the pre-configured exit condition should be based on the measurement of target Reference Signal by LR and / or MR. + +Similarly, the measurements and trigger conditions would need to be defined for using LP-WUS. One way is to define a quality threshold for the target Reference Signal measurement to determine the coverage. One entry condition for using LP-WUS could be configured to UE based on this quality threshold. From network perspective, the threshold could be set based on the coverage of LP-WUS. With this threshold, LP-WUS could be used, and UE's MR could enter ultra-deep-sleep power state when the quality of target Reference Signal is better than the threshold. + +Before the entry condition is fulfilled, UE should perform legacy measurement on serving cell based on legacy SSB, e.g. for cell (re)selection purpose. Hence, it is straightforward to use the legacy SSB as the target Reference Signal for pre-configured entry condition. That is, when the quality of the serving cell's SSB measured by MR is better than a pre-configured threshold, UE considers the entry condition is fulfilled, then, LP-WUS could be used and MR could enter ultra-deep-sleep power state for power saving. Alternatively, LP-SS could be introduced for LR measurement, the pre-condition could be also defined based on the measurement on LP-SS via LR. In this way, the target Reference Signal could be the LP-SS sent by the serving cell, i.e. when the quality of the LP-SS measured by LR is better than a pre-configured threshold, UE considers the entry condition for using LP-WUS is fulfilled. The solution requires the UE to perform measurement on LP-SS via LR before using LP-WUS. In this way, the UE needs to turn on its LR before + +entering ultra-deep-sleep power state, which may lead to extra power consumption, but it is not an issue as the power consumption of LR is very low. + +From the network perspective, if a unique UE identifier (e.g., 48-bit 5G-S-TMSI or 24/40-bit I-RNTI) is not carried in the LP-WUS payload, a gNB may need to transmit both LP-WUS and the associated legacy PDCCH and PDSCH for the paging message. In this case, the gNB would in principle not need to consider whether the UE is within LP-WUS coverage in the cell or not, but in case it is not there would be some unnecessary control signalling overhead from the transmission of LP-WUS. If instead a unique UE identifier is carried in the LP-WUS payload, the gNB could either transmit LP-WUS or legacy paging depending on if the UE is within LP-WUS coverage or not. However, without any signalling from the UE upon LP-WUS coverage change, or from being in the cell or not, this would have to be done blindly and would be left to the gNB implementation (similar to paging the UE in two different cells, i.e., up to trial and error). With partial coverage, the most severe error case would be if the UE from inaccurate measurements incorrectly concludes that it is in LP-WUS coverage when it is not, and therefore becomes unreachable in the downlink (the UE only monitors using LP-WUR but is outside LP-WUS coverage). + +#### 7.3.1.4 Configuration + +Regarding the LP-WUS configuration, both UE and gNB must have a common understanding of when LP-WUS should be applied to avoid that UEs become unreachable in the downlink, as mentioned above in 7.2.3.1.3. Both UE and gNB could apply LP-WUS if LP-WUS has been configured in the cell in SI. This would further determine the conditions for entering and leaving LP-WUS monitoring operation as being tied to the monitoring of paging in a cell: A UE enables LP-WUS monitoring if it is configured with LP-WUS and camp on a cell in RRC\_IDLE or RRC\_INACTIVE state in which LP-WUS is configured, for example when re-selecting a cell in which LP-WUS is configured or being released from RRC\_CONNECTED in a cell in which LP-WUS is configured. + +#### 7.3.1.5 System information update and PWS + +Reception of system information (SI) broadcast and ETWS/CMAS are RRC\_IDLE mode procedures which must be supported for UE with LP-WUS/WUR. When the UE initiates the acquisition of SI, for example when SI has become outdated or upon cell change, the UE anyway needs to start up the main receiver for the reception of the SI message(s). However, this is not the case for a gNB notification of SI update and it must be possible to notify also UEs with LP-WUR about an upcoming SI change in the cell. For reference, in Rel-16 GWUS for NB-IoT/LTE-M this is done by a subgroup common to all UEs (configured by the parameter *commonSequence*), whereas for Rel-17 PEI the gNB must transmit PEI to all subgroups separately and upon the reception of PEI UEs continue to, as in legacy operation, monitor for the *systemInfoModification* and *systemInfoModification-eDRX* in the Short Messages transmitted on PDCCH using P-RNTI. When UE is using LP-WUS, UE could wake up by LP-WUS firstly and then receive the notification of SI change based on the *systemInfoModification* and *systemInfoModification-eDRX* in the Short Messages transmitted on PDCCH using P-RNTI as legacy. + +ETWS/CMAS is regulatory requirement for UEs supporting ETWS/CMAS. Therefore, even for UE in ultra-deep sleep, the ETWS/CMAS messages should be ensured to be reachable if the UE is capable of ETWS/CMAS. As in legacy, the gNB would upon ETWS/CMAS information need to wake up UE by LP-WUS from ultra-deep sleep. Similar to the notification of SI change, when UE is using LP-WUS, UE could wake up by LP-WUS and receive the notification of ETWS/CMAS notification based on *etwsAndCmasIndication* in the Short Messages. + +#### 7.3.1.6 Mobility and RRM + +To ensure a UE in RRC\_IDLE or RRC\_INACTIVE is camping on the best cell it needs to perform mobility measurements as specified in TS 38.304. RRM measurement for mobility includes serving cell measurements and neighbour cell measurements, which can be intra-frequency or inter-frequency (including inter-RAT) measurements. In general, the neighbour cell measurements however only need to be performed by the UE if the serving cell is not strong enough, i.e., when the intra-frequency cell re-selection criterion ( $S_{rxlev} > S_{intraSearchP}$ and $S_{qual} > S_{intraSearchQ}$ ) or the inter-frequency cell re-selection criterion ( $S_{rxlev} > S_{nonIntraSearchP}$ and $S_{qual} > S_{nonIntraSearchQ}$ ) is not fulfilled. For the majority of UEs, and in a well deployed network without coverage holes, it is therefore the serving cell measurements that need to be performed the most frequently, and therefore they will also have the biggest impact on UE energy consumption. + +For a UE operating with LP-WUR, infrequently starting up the main receiver (MR) for neighbour cell measurements is not expected to have any significant impact on UE energy consumption. However, using the MR for serving cell measurements has a significant impact on UE energy consumption and reduce the LP-WUS/WUR gain according to the observations from the study evaluation results. This since according to Clause 4.2.2.2 in TS 38.133, serving cell measurements must be performed every or every second I-DRX cycle in FR1 (and somewhat more relaxed in FR2). + +Starting the main receiver for RRM measurements every I-DRX cycle removes a large part of the UE energy consumption reductions from LP-WUS/WUR. + +In order to achieve the UE power saving gain by LP-WUS/WUR, the RRM measurement on serving cell and neighbouring cell via MR is relaxed or may be stopped when UE is using LP-WUS or MR is in ultra-deep sleep. In Rel-16/17 PowSav and RedCap WI, RRM measurement relaxation on neighbouring cell was introduced. But here, further relaxation or even no measurement by MR could be considered while serving cell measurements are offloaded to LR. The relaxation on RRM measurement may impact the performance of mobility performance in RRC\_IDLE or RRC\_INACTIVE. In order to avoid or minimize such impact, the RRM measurement on LP-WUR could be considered. Thus, the above RRM measurement relaxation on serving cell and neighbouring cell should be premised on the feasibility or support of RRM measurement on LR. + +### 7.3.2 RRC\_CONNECTED mode + +#### 7.3.2.1 RRC\_CONNECTED mode procedures + +For legacy UE in RRC\_CONNECTED state, it should keep MR monitoring PDCCH in C-DRX active time, if C-DRX is configured, also when there is nothing scheduled for the UE. As a result, the power consumption caused by unnecessary PDCCH monitoring is unavoidable. The gain for legacy UE power saving features in RRC\_CONNECTED, such as Short C-DRX, Long C-DRX, Rel-16 PDCCH-based WUS, or Rel-17 PDCCH monitor adaptation, comes from reducing the PDCCH monitoring time. + +Both Rel-16 DCP and Rel-17 PDCCH monitor adaptation are both PDCCH based signalling. For a UE equipped with LR, the MR can be in a sleep state while the LR remains active to monitor Low-Power Wake-Up Signal (LP-WUS), and when LP-WUS is received by LR, it will trigger the MR to wake up to monitor PDCCH. As LR would adopt a minimalistic design, the power consumption of LR is expected to be significantly lower than legacy PDCCH based signaling using the main receiver (MR) in some cases. In this way, LP-WUS in RRC\_CONNECTED can potentially further reduce the UE energy consumption by being able to monitor the downlink with a LR such that the MR used for PDCCH monitoring can be kept in a sleep state. The LP-WUS/WUR solution should target power saving gain compared to the existing Rel-15/16/17 UE power saving mechanisms, e.g., according to the evaluation results above, {6%~15%} additional UE power saving gain with no capacity loss in both low load and high load cases for DL only XR traffic compared to the existing Rel-15/16/17 power saving solutions. + +Compared with UE in RRC\_IDLE/INACTIVE state, UE in RRC\_CONNECTED state is more sensitive to the latency. Therefore, the RAN2 study on LP-WUS procedures in RRC\_CONNECTED should target to reduce power consumption while guarantee the latency performance. + +The MR sleep states considered for LP-WUS/WUR evaluation in RRC\_CONNECTED are the same as for baseline: deep sleep state with a 20 ms transition time, light sleep state with a 6 ms transition time, or micro sleep without any transition time, as described TR 38.840. Ultra-deep sleep state is not considered for LP-WUS/WUR in RRC\_CONNECTED state as a 400 ms transition time is too long to allow the MR to be ready for PDCCH monitoring from the ultra-deep sleep state considering the traffic requirements for NR. Therefore, the power saving gain for LP-WUS/WUR would be determined by the time duration in which the MR can be kept in a sleep state, and significantly lower power consumed by LP-WUS/LP-WUR compared to the PDCCH monitoring by MR. Regarding latency, the transition time for the MR to start up upon LP-WUS detection by LP-WUR would in principle not be worse comparing to the existing power saving mechanism since the MR could be in micro, light, or deep sleep state as legacy, but is not allowed to be in ultra-deep sleep state when LR is monitoring LP-WUS, as described above. + +When using LP-WUS, other conditions could also trigger MR to wake up for PDCCH monitor, e.g. UL transmission by MR, which would be similar to using baseline solutions, e.g. C-DRX, with the same MR sleep state. + +#### 7.3.2.2 LP-WUS monitoring + +Similar as in RRC\_IDLE/INACTIVE, there are two mechanisms to monitor LP-WUS for LP-WUS in RRC\_CONNECTED, i.e. 'continuous' and 'duty-cycled' mode. For 'continuous' mode, LP-WUS is monitored continuously in time, while for 'duty-cycled' mode, LP-WUS is monitored based on a defined duty cycle, which is similar as DRX mechanism. 'Continuous' mode could be expected to have lower latency than 'duty-cycled' mode, but both solutions will have the same lower latency bound from the MR transition time as described above, and in the same way as for legacy C-DRX the duty cycle length for 'duty-cycled' mode would be defined or configured based on the downlink latency requirement. Therefore, any performance comparison of these two LP-WUS monitoring mechanisms, + +or any down selection between them, should be considered based on the downlink latency requirement. The corresponding pros/cons for these two mechanisms are summarized in the below table. + +**Table 7.3.2.2-1: Pros and Cons of 'duty-cycled' and 'continuous' mode for LP-WUS in RRC\_CONNECTED mode** + +| | 'Duty-cycled' mode for LP-WUS | 'Continuous' mode for LP-WUS | +|-------------|-------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| Pros | More UE power saving gain than continuous mode LP-WUS. | Potentially shorter DL latency than 'Duty-cycled' mode.
LP-WUR does not need to keep track of slot or radio frame numbering (i.e., DRX timing). | +| Cons | LP-WUR must keep track of slot and/or radio frame numbering (i.e., DRX timing).
Potentially longer DL latency. | Higher power consumption than duty-cycled LP-WUS. | + +Two examples for UE operations for 'duty-cycled' mode and 'continuous' mode are shown in the below two Figures. + +![Figure 7.3.2.2-1: Example for 'Duty-cycled WUR' operation. This diagram illustrates the power states and signaling for a UE in 'duty-cycled' mode. The top part shows the timeline: starting from 'Idle/Inactive', the UE enters 'Connected' mode with RACH, RRC Setup, Data, and PDCCH. A 'WUR inactivity timer' starts after the last PDCCH. The UE then enters 'Sleep' for the MR. The WUR remains 'Inactive' initially but becomes 'Active' periodically to monitor for PDCCH during a 'WUR PDCCH monitoring window'. This window is defined by a 'WUR time offset' and a 'WUR duty-cycle length'. After the monitoring window, the WUR becomes 'Inactive' again. Finally, an 'RRP Release' occurs, returning the UE to 'Idle/Inactive'.](a68a23db77099456e2f763fce520c087_img.jpg) + +Figure 7.3.2.2-1: Example for 'Duty-cycled WUR' operation. This diagram illustrates the power states and signaling for a UE in 'duty-cycled' mode. The top part shows the timeline: starting from 'Idle/Inactive', the UE enters 'Connected' mode with RACH, RRC Setup, Data, and PDCCH. A 'WUR inactivity timer' starts after the last PDCCH. The UE then enters 'Sleep' for the MR. The WUR remains 'Inactive' initially but becomes 'Active' periodically to monitor for PDCCH during a 'WUR PDCCH monitoring window'. This window is defined by a 'WUR time offset' and a 'WUR duty-cycle length'. After the monitoring window, the WUR becomes 'Inactive' again. Finally, an 'RRP Release' occurs, returning the UE to 'Idle/Inactive'. + +**Figure 7.3.2.2-1: Example for 'Duty-cycled WUR' operation** + +![Figure 7.3.2.2-2: Example for 'Continuous WUR' operation. This diagram illustrates the power states and signaling for a UE in 'continuous' mode. Similar to the duty-cycled mode, it shows the transition from 'Idle/Inactive' to 'Connected' and back. However, in this mode, the WUR remains 'Active' continuously throughout the 'Connected' state, rather than periodically. The MR power state follows the same pattern of 'Active' and 'Sleep'. The 'WUR inactivity timer', 'WUR time offset', and 'WUR PDCCH monitoring window' parameters are still indicated, but the WUR itself does not cycle between active and inactive states while connected.](47b777ee3717213cab7c153aa17f11a0_img.jpg) + +Figure 7.3.2.2-2: Example for 'Continuous WUR' operation. This diagram illustrates the power states and signaling for a UE in 'continuous' mode. Similar to the duty-cycled mode, it shows the transition from 'Idle/Inactive' to 'Connected' and back. However, in this mode, the WUR remains 'Active' continuously throughout the 'Connected' state, rather than periodically. The MR power state follows the same pattern of 'Active' and 'Sleep'. The 'WUR inactivity timer', 'WUR time offset', and 'WUR PDCCH monitoring window' parameters are still indicated, but the WUR itself does not cycle between active and inactive states while connected. + +**Figure 7.3.2.2-2: Example for 'Continuous WUR' operation** + +#### 7.3.2.3 LP-WUS use options + +As described above, in order to save UE power consumption for PDCCH monitoring and guarantee the latency, the basic design is: when MR is in a sleep state, LR will remain active to monitor LP-WUS. When LP-WUS is received by LR, it will trigger the MR to wake up to monitor PDCCH. + +The use of LP-WUS in RRC\_CONNECTED could be considered to replace the legacy methods, e.g. Short C-DRX, Long C-DRX, Rel-16 PDCCH-based WUS (DCP), Rel-17 PDCCH skipping, Rel-17 SSSG switching, etc. or be an + +enhancement thereof when configured, an example is Rel-16 PDCCH-based WUS is an enhancement on top of Long C-DRX. The detailed design for the use of LP-WUS could be in different directions as below, which is summarized in Table X. + +**Table 7.3.2.3-1: LP-WUS operation methods in RRC\_CONNECTED** + +| LP-WUS application | Details | Start PDCCH monitoring condition | Stop PDCCH monitoring condition | +|--------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Direction 1: LP-WUS monitoring occasion is determined based on timer(s) related C-DRX | Option 1: similar to Rel-16 DCP, i.e. the LP-WUS monitoring occasion is located before drx-onDurationTimer . | If LP-WUS addressed to UE or UE's subgroup is detected and the legacy drx-onDurationTimer is started | It could follow legacy, i.e. at expiration of a C-DRX timer, e.g. C-DRX drx-OnDurationTimer or when the UE receives Rel-17 PDCCH skipping indication (if supported and configured). | +| | Option 2: the LP-WUS monitoring occasion is located at any time outside DRX active time to indicate UE to enter into active time | If LP-WUS addressed to UE or UE's subgroup is detected | | +| Direction 2: LP-WUS monitoring occasion is not determined based on timer(s) related C-DRX | Option 4: the LP-WUS monitoring occasion is located at any time regardless of whether DRX is configured or not. | | | +| Direction 3: LP-WUS is transparent to current MAC operation | The LP-WUS monitoring occasion should be determined based on physical layer design/restriction. This direction may not have any impact on MAC. | N/A | N/A | + +Note: The above directions/solutions are NOT Mutually Exclusive absolutely, e.g. some overlap may exist between direction 3 and direction 2, or between option 2 and option 4, based on the detailed design for each direction/option. The detailed design would be further determined in WI, if included. + +In direction 1 above, LP-WUS is used in conjunction with C-DRX. LP-WUS could be configured outside the DRX active time with either of the following two options. + +- Same function as Rel-16 DCP to indicate whether to start the next *drx-onDurationTimer* (i.e. option 1 above) +- To indicate UE to enters into active time for PDCCH monitoring (i.e. option 2 above) + +Some examples for different options in direction 1 are shown as illustrated in the below figures. + +For option 1: LP-WUS is used similar as Rel-16 DCP, an example is shown as below (note that a longer time offset may likely have to be applied to cover the MR transition time compared to DCP): + +![Timing diagram for option 1 showing LP-WUS occasions and DRX active times. A horizontal timeline shows two 'OnDuration' blocks (orange) representing DRX active times. Each 'OnDuration' is preceded by an LP-WUS occasion (blue vertical bar). The time between the start of one LP-WUS and the start of the next is labeled 'DRX cycle'. The time from the LP-WUS occasion to the start of the 'OnDuration' is labeled 'offset'.](04867b54e8cdb31a034edbb472a41162_img.jpg) + +Timing diagram for option 1 showing LP-WUS occasions and DRX active times. A horizontal timeline shows two 'OnDuration' blocks (orange) representing DRX active times. Each 'OnDuration' is preceded by an LP-WUS occasion (blue vertical bar). The time between the start of one LP-WUS and the start of the next is labeled 'DRX cycle'. The time from the LP-WUS occasion to the start of the 'OnDuration' is labeled 'offset'. + +**Figure 7.3.2.3-1: Example for option 1** + +For option 2: LP-WUS could be used at any time outside C-DRX active time to indicate UE to enter into active time, different examples for both 'duty-cycled' and 'continuous' mode are shown as below: + +![Timing diagram for option 2 with 'duty-cycled' LP-WUS. A horizontal timeline shows a repeating pattern of 'On-Duration' (dashed boxes) and 'LP-WUS' (blue vertical bars). A solid orange box labeled 'Active time' is shown within an 'On-Duration'. A 'Timer' (double-headed arrow) indicates the duration when LP-WUS is detected. A legend on the right shows a blue square for 'LP-WUS occasion and LP-WUS is detected' and a grey square for 'LP-WUS occasion and LP-WUS is not detected'.](a27134bc3a3c899782febdd02b502240_img.jpg) + +Timing diagram for option 2 with 'duty-cycled' LP-WUS. A horizontal timeline shows a repeating pattern of 'On-Duration' (dashed boxes) and 'LP-WUS' (blue vertical bars). A solid orange box labeled 'Active time' is shown within an 'On-Duration'. A 'Timer' (double-headed arrow) indicates the duration when LP-WUS is detected. A legend on the right shows a blue square for 'LP-WUS occasion and LP-WUS is detected' and a grey square for 'LP-WUS occasion and LP-WUS is not detected'. + +**Figure 7.3.2.3-2: Example for option 2 with 'duty-cycled' LP-WUS** + +![Figure 7.3.2.3-3: Example for option 2 with 'continuous' LP-WUS. The diagram shows a timeline with 'On-Duration' periods (dashed lines) and 'Continuous LP-WUS monitoring' periods (grey). 'Active time' (orange) occurs during the monitoring periods. A 'Timer' (double-headed arrow) indicates the duration when LP-WUS is detected (blue). A 'DRX cycle' is indicated by a long double-headed arrow.](e7010c66da16316c2935dfbbef5056b3_img.jpg) + +Legend: + Blue box: LP-WUS is detected + Grey box: Continuous LP-WUS monitoring + Timer: the duration when LP-WUS is detected + +Figure 7.3.2.3-3: Example for option 2 with 'continuous' LP-WUS. The diagram shows a timeline with 'On-Duration' periods (dashed lines) and 'Continuous LP-WUS monitoring' periods (grey). 'Active time' (orange) occurs during the monitoring periods. A 'Timer' (double-headed arrow) indicates the duration when LP-WUS is detected (blue). A 'DRX cycle' is indicated by a long double-headed arrow. + +**Figure 7.3.2.3-3: Example for option 2 with 'continuous' LP-WUS** + +In direction 2 above, LP-WUS is used in conjunction with C-DRX as the direction 1 or without C-DRX. In the latter case, the LP-WUS is used to indicate UE to activate/resume PDCCH monitoring. Some other solutions used to indicate UE to stop the PDCCH monitoring should be used in conjunction with LP-WUS, e.g. Rel-17 PDCCH monitoring adaptation. + +For option 4: LP-WUS could be used at any time regardless of whether C-DRX is configured or not, different examples for both 'duty-cycled' and 'continuous' mode are shown as below: + +![Figure 7.3.2.3-4: Example for option 4 with 'duty-cycled' LP-WUS. The top part shows 'LP-WUS' (grey) and 'Active time' (orange) with a 'timer' (double-headed arrow). The bottom part shows 'LP-WUS' (grey), 'Active time' (orange), and 'PDCCH skipping indication' (black).](78de09c382ab51b5c3e87979204228c8_img.jpg) + +Figure 7.3.2.3-4: Example for option 4 with 'duty-cycled' LP-WUS. The top part shows 'LP-WUS' (grey) and 'Active time' (orange) with a 'timer' (double-headed arrow). The bottom part shows 'LP-WUS' (grey), 'Active time' (orange), and 'PDCCH skipping indication' (black). + +**Figure 7.3.2.3-4: Example for option 4 with 'duty-cycled' LP-WUS** + +![Figure 7.3.2.3-5: Example for option 4 with 'continuous' LP-WUS. The top part shows 'Continuous LP-WUS monitoring' (grey) and 'Active time' (orange) with a 'timer' (double-headed arrow). The bottom part shows 'PDCCH skipping indication' (black) and 'Active time' (orange) with a 'timer' (double-headed arrow).](a175bdeacb50b8a60869f6c68c5d0a07_img.jpg) + +Continuous LP-WUS monitoring + +Figure 7.3.2.3-5: Example for option 4 with 'continuous' LP-WUS. The top part shows 'Continuous LP-WUS monitoring' (grey) and 'Active time' (orange) with a 'timer' (double-headed arrow). The bottom part shows 'PDCCH skipping indication' (black) and 'Active time' (orange) with a 'timer' (double-headed arrow). + +**Figure 7.3.2.3-5: Example for option 4 with 'continuous' LP-WUS** + +In direction 3, the detailed design should be determined based on physical layer design/restriction. + +The corresponding pros/cons for the above options on LP-WUS using in RRC\_CONNECTED are summarized in the below table. + +**Table 7.3.2.3-2: Pros and Cons of LP-WUS using options in RRC\_CONNECTED** + +#### 7.3.2.4 Configuration + +A UE is expected to be configured with LP-WUS/WUR in RRC\_CONNECTED mode, e.g. upon RRC connection establishment, i.e., either during RRC Connection Setup or RRC Connection Resumption. Therefore, UE specific LP-WUS/WUR configuration is possible in RRC\_CONNECTED mode. + +The time gap between the LP-WUS monitoring occasion and the PDCCH monitoring occasion for MR must be designed or configured long enough to cover the transition time of the MR to be ready for PDCCH monitoring. Another alternative is similar to Rel-15 WUS for NB-IoT/LTE-M, different transition time gaps, if introduced, could be defined as UE capability. Then, gNB could, based on this capability, know which time gap to configure for the UE (which if, several sleep states are supported, lets the UE to determine the MR sleep state to apply). + +For partial LP-SS/LP-WUS coverage in the cell, LP-WUS should only be configured/used for a UE within LP-SS/LP-WUS coverage: + +- In one solution, the coverage determination is similar as in RRC\_IDLE/INACTIVE, which is based on the measurement of LR and/or MR, and the corresponding threshold determined/configured by network. Furthermore, when UE moves out of LP-WUS coverage, LP-WUS cannot be used at the UE, as it is unreachable by the gNB for LP-WUS. It should be either released or de-activated by the network. Otherwise, some conditions would have to be introduced to ensure the UE could autonomously fall back to legacy operation without LP-WUS. +- In another solution, monitoring LP-WUS can be explicitly activated and de-activated by the network, e.g., entry/exit condition(s) of using LP-WUS may not be needed. + +| LP-WUS options | Pros | Cons | +|----------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Option 1: LP-WUS is used similar as Rel-16 DCP | More Power Saving gain is expected compared to legacy DCP due to the difference on power consumption between LP-WUS monitor and PDCCH monitor; Less specification impact and complexity from reuse of DCP functionality compared to other solutions, e.g. option 2 option 3. | It would result in having redundant mechanism for the same purpose.
Artificially limiting WUR duty-cycle to the C-DRX cycle length (can easily be avoided using separate configuration parameters). | +| Option 2: LP-WUS could be used at any time outside C-DRX active time to indicate UE to enter into active time | Power saving gain is expected compared to current C-DRX mechanism.
LP-WUS configuration is more flexible than option 1 and option 3, e.g. since WUR duty-cycle is not locked to C-DRX cycle; If a shorter WUR duty-cycle is compared to a longer C-DRX cycle, or continuous mode is used, DL data transmission latency could be reduced compared to C-DRX mechanism and option 1 by not limiting the DL data transmission to a C-DRX onDuration. | More complexity: how to coexist with current C-DRX mechanism;
More specification impacts: new PDCCH monitoring mechanism needs to be captured, e.g. separate WUR duty-cycle (different from C-DRX cycle), and WUR-specific on-duration timer for PDCCH monitoring must be introduced. | +| [Option 3: LP-WUS could be used after the beginning of drx-onDurationTimer] | Power Saving gain is expected by reducing unnecessary PDCCH monitoring for XR traffic than legacy C-DRX if there is one-stream XR traffic with a non-changing fps which can be matched by the DRX cycle. | More specification impacts considering it may change the current PDCCH monitoring behaviour
Given the ramp-up time from micro/deep sleep, it may be useable in the limited cases, e.g., long drx-onDurationTimer . | +| Option 4: LP-WUS could be used at any time regardless of whether C-DRX is configured or not | Power Saving gain is expected compared to current C-DRX mechanism and DCP since LP-WUS monitoring consumes less power than PDCCH monitoring; LP-WUS configuration is more flexible than other options above; DL data transmission latency could be reduced compared to current C-DRX mechanism. | More complexity: we need to discuss how to stop the PDCCH monitoring and how to configure the LP-WUS; | + +Meanwhile, for full LP-SS/LP-WUS coverage in the cell, no special configuration would be required. That is, LP-WUS could be configured/activated for a UE in the cell, and not used when it is released/de-activated in the cell. + +According to above analysis, LP-WUS in RRC\_CONNECTED with partial LP-WUS coverage is expected to have more standardization impacts than the scenario with full LP-WUS coverage. + +#### 7.3.2.5 LP-WUS coexistence with DCP + +On one hand, LP-WUS could be configured together with Rel-16 DCP for a specific UE. However, the UE may only use one of them at any time, e.g. depend on the network configuration or link quality, etc. It should be noted that this operation is more useful for the partial LP-SS/LP-WUS coverage as described in 7.3.2.4. For example, for partial LP-SS/LP-WUS coverage, when the UE is in LP-SS/LP-WUS coverage, UE could monitor LP-WUS autonomously or UE could monitor LP-WUS if the gNB activate the LP-WUS monitoring. When UE moves out of LP-SS/LP-WUS coverage, the measurement quality of LP-SS via LR is not good enough, UE could consider to use Rel-16 DCP as in legacy in this case. + +On the other hand, the LP-WUS could be used in conjunction with Rel-16 DCP. That is, the UE firstly monitor LP-WUS and, in case the MR is waked up by the LP-WUS, then, the UE will continue to monitor DCP. + +## 7.4 RAN4 RRM study + +This clause captures the outcome of RAN4 review on RRM aspects for LP-WUR during SI phase. + +RAN4 confirms that the evaluation methodology by RAN1 in TR38.869 for serving cell RSRP/RSRQ measurement offloading to LP-WUR for IDLE/INACTIVE mode is reasonable for SI phase. + +- The evaluation methodology refers to the consideration of SNR side conditions, number of measurement samples and measurement accuracy. +- In addition, in RAN4, RF impairment margin is considered. + +RAN4 understands that the determination of SNR target for serving cell RSRP/RSRQ measurement offloading to LP-WUR should consider at least the NF difference between LP-WUR and MR and the applicable coverage conditions of LP-WUR. + +# 8 Evaluation results + +## 8.1 Power and latency evaluation + +### 8.1.1 RRC IDLE/INACTIVE mode + +The following '**Effective per UE paging arrival rate (i.e., $R_{eff}$ )**' is defined as (without taking FAR into account) + +- Per UE paging probability $R_E$ if LP-WUS is per UE paging +- Per group paging probability $R_G = 1 - (1 - R_E)^N$ , if LP-WUS is per group paging (N is the number of UEs in the group) + +The following names are used, + +- Effective per UE paging arrival rate + - the period for complete an on-and-off cycle for LP-WUS duty-cycled monitoring, + - the active time for monitoring LP-WUS every cycle for LP-WUS duty-cycled monitoring +- LP-WUR duty cycle ratio = $D/T$ +- LP-WUR on state power +- LP-WUR off state power + +#### 8.1.1.1 Duty cycled LP-WUS + +In this clause, duty cycled LP-WUS is studied and compared to I-DRX cases. In addition, the following is assumed, + +- no RRM measurement performed by MR or LR, or RRM measurement offloaded to LR or MR RRM relaxed at least 8 times of I-DRX cycle +- MR in ultra-deep sleep if no traffic is arrival +- MR ramp-up time, transition energy = 400ms, 15000unit, +- I-DRX cycle = 1.28s +- FAR $\leq 1\%$ (0%, 0.001%, 0.1%, 1%) + +##### 8.1.1.1.1 Collection of the results + +###### 8.1.1.1.1.1 LR (PWURON, R, FAR) = (<10unit, <=1%, <=1%) + +I-DRX cycle = 1.28s, LP-WUR on state power <10unit, LP-WUR duty cycle ratio <=1%, FAR <=1% (0%, 0.001%, 0.1%, 1%) + +![Bar chart showing Power saving gain [%] for various configurations (8A-3 to 8A-17) across three effective per UE paging arrival rate categories: <=0.1%, 0.1%<=1%, and 1%<=8%. The chart displays min, mean, and max power saving gains.](46354e78fc94fa64a2d49f26a2a24c80_img.jpg) + +The chart displays power saving gains for different UE paging arrival rates and configurations. The Y-axis represents the Power saving gain [%] from -40% to 120%. The X-axis is divided into three categories based on effective per UE paging arrival rate: <=0.1%, 0.1%<=1%, and 1%<=8%. Each category contains bars for configurations 8A-3, 8A-13, 8A-17, 8A-16, 8A-15, 8A-1, 8A-11, 8A-12, and 8A-4. For each configuration, three bars are shown: min:Power saving gain [%] (blue), mean:Power saving gain [%] (orange), and max:Power saving gain [%] (grey). The values are labeled above each bar. + +| Effective per UE paging arrival rate | Configuration | min:Power saving gain [%] | mean:Power saving gain [%] | max:Power saving gain [%] | +|--------------------------------------|---------------|---------------------------|----------------------------|---------------------------| +| <=0.1% | 8A-3 | 94% | 99% | 99% | +| | 8A-13 | 15% | 78% | 99% | +| | 8A-17 | 59% | 73% | 91% | +| | 8A-16 | 87% | 92% | 97% | +| | 8A-15 | 92% | 98% | 98% | +| | 8A-1 | 37% | 75% | 93% | +| | 8A-11 | 39% | 83% | 99% | +| | 8A-12 | 76% | 87% | 98% | +| | 8A-4 | -31% | 43% | 45% | +| 0.1%<=1% | 8A-3 | 90% | 97% | 92% | +| | 8A-13 | 90% | 99% | 92% | +| | 8A-7 | 88% | 88% | 88% | +| | 8A-5 | 68% | 82% | 92% | +| | 8A-17 | 22% | 30% | 39% | +| | 8A-9 | 61% | 70% | 70% | +| | 8A-16 | 70% | 80% | 88% | +| | 8A-8 | 46% | 73% | 92% | +| | 8A-10 | 84% | 85% | 85% | +| 1%<=8% | 8A-15 | 59% | 88% | 96% | +| | 8A-1 | 35% | 71% | 88% | +| | 8A-11 | 32% | 68% | 93% | +| | 8A-12 | 90% | 90% | 90% | +| | 8A-4 | -31% | 42% | 90% | +| | 8A-3 | 77% | 79% | 83% | +| | 8A-8 | 39% | 62% | 85% | +| | 8A-10 | 55% | 68% | 79% | +| | 8A-15 | 78% | 83% | 92% | +| 8A-1 | 22% | 53% | 65% | | + +Bar chart showing Power saving gain [%] for various configurations (8A-3 to 8A-17) across three effective per UE paging arrival rate categories: <=0.1%, 0.1%<=1%, and 1%<=8%. The chart displays min, mean, and max power saving gains. + +Figure 8.1.1.1-1 + +Note1: The results combine different LP-WUR(ON, OFF) power values. And detailed simulated combinations can be seen in Table 8.1.1.3-1 + +Note2: [8A-12] assumes MR ramp-up time, transition energy is 100ms, 2000unit(not aligned with agreed assumption) + +Note3: WUS monitoring duration is assumed as follows: + +- [8A-16](2ms)/ [8A-11](2ms)/ [8A-17](1ms)/ [8A-9] (1ms)/ [8A-3] (1/1.5/2.5ms)/ [8A-12] (1.26ms)/ [8A-8] (1.28ms)/ [8A-7] (0.25) assume very short WUS monitoring duration. +- [8A-11](12.8ms)/ [8A-10](8ms)/ [8A-1] (10ms)/ [8A-5] (10ms)/ [8A-15] (6/9/10/12ms)/ [8A-8] (12.8ms)/ [8A-3] (6/10/13ms)/ [8A-4] (13ms)/ [8A-13] (10ms) assume long WUS monitoring duration. + +Note4: FAR is assumed as follows: + +- FAR = 0 is simulated by [8A-3], [8A-11], [8A-8], [8A-5] +- FAR = 0.001% is simulated by [8A-12], [8A-15]] + +- FAR = 0.1% is simulated by [8A-3], [8A-4], [8A-17], [8A-11], [8A-13], [8A-16], [8A-8] +- FAR = 1% is simulated by [8A-3], [8A-4], [8A-17], [8A-11], [8A-13], [8A-1], [8A-10], [8A-16], [8A-8], [8A-7] + +Note5: All the possible values for LP-WUR ON power < 10 are mixed together, further split is shown in clause 8.1.1.3 + +###### 8.1.1.1.1.2 LR (PWURON, R, FAR) = (<10unit, (1%,5%], <=1%) + +I-DRX cycle = 1.28s, LP-WUR on state power <10unit, 1%< LP-WUR duty cycle ratio <=5%, FAR <=1% (0.001%, 0.1%, 1%) + +![Bar chart showing power saving gain percentages for different scenarios. The chart compares min, mean, and max power saving gains across five categories based on UE paging arrival rates and simulation parameters (8A-3, 8A-7, 8A-15).](ce951c49dba8deb9a7fda642899b99a4_img.jpg) + +| Scenario | min:Power saving gain [%] | mean:Power saving gain [%] | max:Power saving gain [%] | +|--------------------------------------------------------|---------------------------|----------------------------|---------------------------| +| 8A-3 Effective per UE paging arrival rate <= 0.1% | 95% | 98% | 98% | +| 8A-3 0.1% < Effective per UE paging arrival rate <= 1% | 91% | 95% | 97% | +| 8A-7 | 91% | 91% | 91% | +| 8A-15 | 58% | 87% | 92% | +| 8A-3 1% < Effective per UE paging arrival rate <= 8% | 78% | 81% | 83% | + +Bar chart showing power saving gain percentages for different scenarios. The chart compares min, mean, and max power saving gains across five categories based on UE paging arrival rates and simulation parameters (8A-3, 8A-7, 8A-15). + +Figure 8.1.1.1-2 + +Note1: The results combine different LP-WUR(ON, OFF) power values. And detailed simulated combinations can be seen in Table 8.1.1.3-1 + +Note2: FAR is assumed as follows: + +- FAR = 0.001% is simulated by [8A-15] +- FAR = 0.1% is simulated by [8A-3] +- FAR = 1% is simulated by [8A-7] + +Note3: All the possible values for LP-WUR ON power < 10 are mixed together, further split is shown in clause 8.1.1.3 + +Note 4: Results with duty cycle ratio 5~30% are provided by [8A-3], [8A-5], [8A-8], [8A-11], and included in the spread sheet for power evaluation + +###### 8.1.1.1.1.3 LR (PWURON, R, FAR) = (>=10unit, <=1%, <=1%) + +I-DRX cycle = 1.28s, LP-WUR on state power >=10unit, LP-WUR duty cycle ratio <=1%, FAR <=1% (0%, 0.001%, 0.1%, 1%) + +![Bar chart showing Power saving gain [%] for various configurations. The chart is divided into three groups based on effective per UE paging arrival rate: <=0.1%, 0.1% <= rate <= 1%, and 1% <= rate <= 8%. Each group contains bars for configurations 8A-3, 8A-16, 8A-15, 8A-1, 8A-11, 8A-13, 8A-7, 8A-9, 8A-16, 8A-8, 8A-10, 8A-15, 8A-1, 8A-11, 8A-3, 8A-8, 8A-10, 8A-15, 8A-1. The legend indicates min (blue), mean (orange), and max (grey) power saving gain.](ce9ded033e82bd248b3a2a57305d6767_img.jpg) + +| Effective per UE paging arrival rate | Configuration | min:Power saving gain [%] | mean:Power saving gain [%] | max:Power saving gain [%] | +|----------------------------------------------------|---------------|---------------------------|----------------------------|---------------------------| +| Effective per UE paging arrival rate <= 0.1% | 8A-3 | 92% | 99% | 98% | +| | 8A-16 | 77% | 70% | 45% | +| | 8A-15 | 91% | 90% | 88% | +| | 8A-1 | 88% | 88% | 88% | +| | 8A-11 | 51% | 93% | 87% | +| 0.1% <= Effective per UE paging arrival rate <= 1% | 8A-3 | 99% | 99% | 99% | +| | 8A-13 | 71% | 73% | 83% | +| | 8A-7 | 25% | 41% | 56% | +| | 8A-9 | 46% | 68% | 83% | +| | 8A-16 | 85% | 63% | 64% | +| | 8A-8 | 2% | 46% | 85% | +| | 8A-10 | 56% | 83% | 83% | +| | 8A-15 | 83% | 83% | 83% | +| | 8A-1 | 83% | 83% | 83% | +| | 8A-11 | 26% | 84% | 73% | +| | 8A-3 | 73% | 90% | 90% | +| | 8A-8 | 42% | 40% | 78% | +| | 8A-10 | 56% | 67% | 80% | +| | 8A-15 | 78% | 80% | 66% | +| 1% <= Effective per UE paging arrival rate <= 8% | 8A-1 | 66% | 66% | 66% | + +Bar chart showing Power saving gain [%] for various configurations. The chart is divided into three groups based on effective per UE paging arrival rate: <=0.1%, 0.1% <= rate <= 1%, and 1% <= rate <= 8%. Each group contains bars for configurations 8A-3, 8A-16, 8A-15, 8A-1, 8A-11, 8A-13, 8A-7, 8A-9, 8A-16, 8A-8, 8A-10, 8A-15, 8A-1, 8A-11, 8A-3, 8A-8, 8A-10, 8A-15, 8A-1. The legend indicates min (blue), mean (orange), and max (grey) power saving gain. + +Figure 8.1.1.1-3 + +Note1: The results combines different LP-WUR(ON, OFF) power values. And detailed simulated combinations can be seen in Table 8.1.1.3-1 + +Note2: WUS monitoring duration is assumed as follows: + +- [8A-7](0.25ms)/ [8A-16] (2ms)/ [8A-8] (1.28/2.56ms)/ [8A-3] (1/1.5/2.5ms)/ [8A-11] (2ms)/ [8A-9] (1ms)/ [8A-10] (2ms) assume very short WUS monitoring duration. +- [8A-15](6/9/10/12ms)/ [8A-8](6.4/12.8ms)/ [8A-3] (6/10ms)/ [8A-11] (12.8ms)/ [8A-1] (10ms)/ [8A-13] (10ms) assume long WUS monitoring duration. + +Note3: FAR is assumed as follows: + +- FAR = 0 is simulated by [8A-3], [8A-11], [8A-8] +- FAR = 0.001% is simulated by [8A-15] +- FAR = 0.1% is simulated by [8A-3], [8A-9], [8A-11], [8A-13], [8A-16], [8A-8] +- FAR = 1% is simulated by [8A-3], [8A-11], [8A-13], [8A-1], [8A-10], [8A-16], [8A-8], [8A-7] + +Note4: all the possible values for LP-WUR ON power > 10 are mixed together, further split is shown in clause 8.1.1.3 + +###### 8.1.1.1.1.3 Latency + +I-DRX cycle = 1.28s, LP-WUR duty cycle ratio <=1%, effective per UE paging arrival rate <=8% + +![Bar chart showing latency metrics for various configurations (8A-3 to 8A-17). The chart compares min:LP-WUS Latency [ms], mean:LP-WUS Latency [ms], max:LP-WUS Latency [ms], and mean:I-DRX latency [ms].](4d34414c7275440623d6ea15c13713f7_img.jpg) + +| Configuration | min:LP-WUS Latency [ms] | mean:LP-WUS Latency [ms] | max:LP-WUS Latency [ms] | mean:I-DRX latency [ms] | +|---------------|-------------------------|--------------------------|-------------------------|-------------------------| +| 8A-3 | 1090 | 1094 | 1230 | | +| 8A-13 | 1909 | 1909 | 1909 | | +| 8A-7 | 982 | 1022 | 1062 | 672 | +| 8A-5 | 1150 | 1150 | 1150 | 670 | +| 8A-17 | 1152 | 1217 | 1253 | 768.49 | +| 8A-16 | 1053 | 1053 | 1053 | 494.70 | +| 8A-8 | 1060 | 1107 | 1692 | 588.23 | +| 8A-10 | 1888 | 1888 | 1880 | 691.83 | +| 8A-15 | 1220 | 1220 | 1220 | 489.78 | +| 8A-1 | 1090 | 1090 | 1090 | 560.73 | +| 8A-11 | 1242 | 1264 | 1287 | 640 | +| 8A-4 | 1100 | 1150 | 1220 | 690 | + +Bar chart showing latency metrics for various configurations (8A-3 to 8A-17). The chart compares min:LP-WUS Latency [ms], mean:LP-WUS Latency [ms], max:LP-WUS Latency [ms], and mean:I-DRX latency [ms]. + +Figure 8.1.1.1-4: Legacy PO + +Note: [8A-5] assumes UE-specific indication and therefore latency is the time interval between data arrival at the gNB until the UE finish sync/re-sync for MR, while other companies assume latency is the time interval between data arrival at the gNB until the first PO that UE can monitor for paging message. + +![Bar chart titled 'Dynamic PO' showing latency values for different configurations (8A-13, 8A-8, 8A-11). The chart compares min, mean, and max LP-WUS latency with mean I-DRX latency.](e0f4d30e14bac25c9a4d673acf4e22e9_img.jpg) + +| Configuration | min:LP-WUS Latency [ms] | mean:LP-WUS Latency [ms] | max:LP-WUS Latency [ms] | mean:I-DRX latency[ms] | +|---------------|-------------------------|--------------------------|-------------------------|------------------------| +| 8A-13 | 1080 | 1080 | 1080 | - | +| 8A-8 | 568 | 568 | 568 | 687 | +| 8A-11 | 599 | 599 | 599 | 638 | + +Bar chart titled 'Dynamic PO' showing latency values for different configurations (8A-13, 8A-8, 8A-11). The chart compares min, mean, and max LP-WUS latency with mean I-DRX latency. + +Figure 8.1.1.1-5: Dynamic PO + +Note: [8A-13] assumes LP-WUS duty cycle is 1280ms. + +Note: [8A-8] assumes the effective monitoring periodicity for LP-WUS is 128ms. + +Note: [8A-11] assumes LP-WUS duty cycle is 200ms + +##### 8.1.1.1.2 Observations + +For duty-cycled LP-WUS monitoring, the following observations are made with the assumption that + +- no RRM measurement performed by MR or LR, or RRM measurement offloaded to LR or MR RRM relaxed at least 8 times of I-DRX cycle +- MR in ultra-deep sleep if no traffic is arrival +- MR ramp-up time, transition energy = 400ms, 15000unit, +- I-DRX cycle = 1.28s +- FAR <=1% (0%, 0.001%, 0.1%, 1%) +- effective per UE paging arrival rate <=8% + +- 1) For WUR ON power < 10unit (i.e., 0.01/0.05/0.1/0.5/1/2/4 unit) with no more than duty cycle ratio 1% + - Effective per UE paging arrival rate<=1% + +- Results in [8A-1], [8A-3], [8A-4], [8A-5], [8A-7], [8A-8], [8A-9], [8A-10], [8A-11], [8A-12], [8A-13], [8A-15], [8A-16], [8A-17] show that compared with i-DRX with or without PEI, LP-WUS provides mean power saving gain (average: 77%, range: 30%~97%) + - $1\% < \text{Effective per UE paging arrival rate} \leq 8\%$ + - Results in [8A-1], [8A-3], [8A-5], [8A-8], [8A-10] show that compared with i-DRX with or without PEI, LP-WUS provides mean power saving gain (average: 69%, range: 53%~83%) +- 2) For WUR ON power $< 10\text{unit}$ (i.e., 0.01/0.05/0.1/0.5/1/2/4 unit) with duty cycle ratio between 1% and 5% +- Effective per UE paging arrival rate $\leq 1\%$ + - Results in [8A-3], [8A-7], [8A-15] show that compared with i-DRX with or without PEI, LP-WUS provides mean power saving gain (average: 92%, range 87%~98%) + - $1\% < \text{Effective per UE paging arrival rate} \leq 8\%$ + - Results in [8A-3] show that compared with i-DRX with or without PEI, LP-WUS provides mean power saving gain (81%). +- 3) For WUR ON power $\geq 10\text{unit}$ (i.e., 10/20/30 unit) with no more than duty cycle ratio 1% +- Effective per UE paging arrival rate $\leq 1\%$ + - Results in [8A-1], [8A-3], [8A-7], [8A-8], [8A-9], [8A-10], [8A-11], [8A-13], [8A-15], [8A-16] show that compared with i-DRX with or without PEI, LP-WUS provides mean power saving gain (average: 62%, range: -13%~95%) + - $1\% < \text{Effective per UE paging arrival rate} \leq 8\%$ + - Results in [8A-1], [8A-3], [8A-8], [8A-10], [8A-15] show that compared with i-DRX with or without PEI, LP-WUS provides mean power saving gain (average: 63%, range: 42%~81%) +- 4) For latency +- Legacy PO + - Results in [8A-1], [8A-4], [8A-5], [8A-7], [8A-8], [8A-11], [8A-15], [8A-17] show that compared with i-DRX with or without PEI mean paging latency (0.638~0.768) second, LP-WUS will result in mean paging latency (1.022~1.264) second, which increases mean paging latency (52%~98%) + - Results in [8A-3], [8A-10], [8A-13], [8A-16] show that compared with i-DRX with or without PEI paging latency, LP-WUS will result in mean paging latency (1.053~1.909) second without baseline i-DRX latency. + - Dynamic PO + - Results in [8A-8], [8A-11] show that compared with i-DRX with or without PEI mean paging latency (0.638~0.687) second, LP-WUS will result in mean paging latency (0.568~0.599) second, which decreases mean paging latency (6%~17%) + +- Results in [8A-13] show that compared with i-DRX with or without PEI paging latency, LP-WUS will result in mean paging latency (1.08) second without baseline i-DRX latency. + +#### 8.1.1.2 Continuous monitoring results and results with duty cycle ratio = 50% LP-WUS + +In this clause, continuous monitoring of LP-WUS and LP-WUS monitoring with duty cycle ratio of 50% are studied and the following is assumed, + +- Continuous monitoring results and results with duty cycle ratio = 50% LP-WUS comparing with I-DRX is as baseline +- FAR target is determined across a reference time duration T of multiple LP-WUS attempts/trials. +- no RRM measurement performed by MR or LR, or RRM measurement offloaded to LR or MR RRM relaxed at least 8 times of I-DRX cycle +- MR in ultra-deep sleep if no traffic is arrival +- MR ramp-up time, transition energy = 400ms, 15000unit +- I-DRX cycle = 1.28s +- FAR<=1% (0%, 0.001%, 0.1%, 1%) + +**Table 8.1.1.2-1: FAR assumptions of different sources** + +| Sources | (FAR_target, N, T) | +|---------|---------------------------------------------| +| [8A-2] | Not considered as FAR=0 | +| [8A-3] | (0.1%, 1, 5ms) | +| [8A-4] | N=1280, T=1.28s | +| [8A-5] | N=1500, T=1.28s | +| [8A-7] | (1%, 1, 1.28s) | +| [8A-8] | (0%, 1, 1.28s) / (1%, 1, 1.28s) | +| [8A-9] | (0.1%, 1280, 1.28s) | +| [8A-11] | (0.1%, 1, 1.28s) / (1%, 1, 1.28s) | +| [8A-13] | (0.1%, N=1~64, 1.28s) / (1%, N=1~64, 1.28s) | +| [8A-14] | (0, 1280, 1.28s) | +| [8A-15] | (0.001%, 1, 1ms) | +| [8A-16] | (0.1%, 1280, 1.28s) / (1%, 1280, 1.28s) | + +##### 8.1.1.2.1 Collection of the results + +###### 8.1.1.2.1.1 LR (PWURON, FAR) = (<= 1unit, <=1%) + +I-DRX cycle = 1.28s, T = I-DRX cycle, LP-WUR on state power <=1unit, FAR<=1% (0%, 0.001%, 0.1%, 1%) + +![Bar chart showing Power saving gain [%] for various configurations (8A-13 to 8A-17, 8A-2(1), 8A-2(2), 8A-5, 8A-16, 8A-15, 8A-11, 8A-4, 8A-3, 8A-7, 8A-9, 8A-8, 8A-14). The chart is divided into three sections based on UE paging arrival rate: Effective per UE paging arrival rate ≤ 0.1%, 0.1% < Effective per UE paging arrival rate ≤ 1%, and 1% < Effective per UE paging arrival rate ≤ 8%. The legend indicates min:Power saving gain [%] (blue), mean:Power saving gain [%] (orange), and max:Power saving gain [%] (grey).](df942da5e715e03b194b733d9f5998ad_img.jpg) + +| Configuration | min:Power saving gain [%] | mean:Power saving gain [%] | max:Power saving gain [%] | +|---------------|---------------------------|----------------------------|---------------------------| +| 8A-13 | -8% | 62% | 98% | +| 8A-2(1) | 95% | 99% | 99% | +| 8A-2(2) | 43% | 53% | 53% | +| 8A-5 | 87% | 94% | 94% | +| 8A-17 | 29% | 65% | 98% | +| 8A-16 | 18% | 59% | 89% | +| 8A-15 | 81% | 88% | 88% | +| 8A-11 | -9% | 67% | 99% | +| 8A-4 | -103% | 25% | 92% | +| 8A-3 | -18% | 12% | 12% | +| 8A-13 | 38% | 65% | 92% | +| 8A-7 | 88% | 88% | 88% | +| 8A-2(1) | 95% | 99% | 99% | +| 8A-2(2) | 41% | 52% | 52% | +| 8A-5 | 20% | 75% | 90% | +| 8A-17 | -7% | 21% | 43% | +| 8A-9 | 40% | 63% | 70% | +| 8A-16 | 2% | 48% | 87% | +| 8A-8 | 61% | 81% | 89% | +| 8A-14 | 43% | 70% | 86% | +| 8A-15 | 55% | 78% | 78% | +| 8A-11 | -16% | 49% | 92% | +| 8A-4 | -103% | 24% | 89% | +| 8A-8 | 32% | 45% | 58% | +| 8A-15 | 66% | 70% | 80% | + +Bar chart showing Power saving gain [%] for various configurations (8A-13 to 8A-17, 8A-2(1), 8A-2(2), 8A-5, 8A-16, 8A-15, 8A-11, 8A-4, 8A-3, 8A-7, 8A-9, 8A-8, 8A-14). The chart is divided into three sections based on UE paging arrival rate: Effective per UE paging arrival rate ≤ 0.1%, 0.1% < Effective per UE paging arrival rate ≤ 1%, and 1% < Effective per UE paging arrival rate ≤ 8%. The legend indicates min:Power saving gain [%] (blue), mean:Power saving gain [%] (orange), and max:Power saving gain [%] (grey). + +Figure 8.1.1.2-1 + +Note1: The results tagged with [8A-2](1) are for LP-WUS UEs, and the results tagged with [8A-2](2) are for the system UEs which contain both LP-WUS UEs and legacy UEs who are unable to apply LP-WUS monitoring + +Note2: For (FAR, N, T), [8A-3] assumes (T= 5ms, N=1), [8A-15] assumes (T=1ms, N=1), while other companies assume T = I-DRX cycle period, N value in (FAR, N, T) is summarized in table 8.1.1.2-1. + +Note3: FAR is assumed as follows: + +- FAR = 0 is simulated by [8A-2], [8A-5], [8A-11], [8A-8], [8A-14] +- FAR = 0.001% is simulated by [8A-15] +- FAR = 0.1% is simulated by [8A-3], [8A-4], [8A-5], [8A-17], [8A-9], [8A-11], [8A-13], [8A-16] +- FAR = 1% is simulated by [8A-4], [8A-5], [8A-17], [8A-11], [8A-13], [8A-7], [8A-16], [8A-8] + +###### 8.1.1.2.1.2 LR (PWURON, FAR) = ( > 1unit, ≤1%) + +I-DRX cycle = 1.28s, T = I-DRX, LP-WUR on state power >1unit, FAR≤1% (0% , 0.1%, 1%) + +![Bar chart showing Power saving gain [%] for min, mean, and max across different UE paging arrival rate categories. The chart shows significant power savings for some configurations, with values ranging from -1027% to 61%.](be2d9105109f6a87907ab68cb88548d9_img.jpg) + +| Effective per UE paging arrival rate | min:Power saving gain [%] | mean:Power saving gain [%] | max:Power saving gain [%] | +|-------------------------------------------------------|---------------------------|----------------------------|---------------------------| +| Effective per UE paging arrival rate <= 0.1% | -89% | -55% | -58% | +| 0.1% < Effective per UE paging arrival rate <= 1% | -24% | -23% | -21% | +| 1% < Effective per UE paging arrival rate <= 8% | -1019% | -647% | -357% | +| 8% < Effective per UE paging arrival rate <= 16% | -130% | -6% | -33% | +| 16% < Effective per UE paging arrival rate <= 32% | -96% | -12% | -13% | +| 32% < Effective per UE paging arrival rate <= 64% | -124% | -14% | -98% | +| 64% < Effective per UE paging arrival rate <= 128% | -819% | -231% | 38% | +| 128% < Effective per UE paging arrival rate <= 256% | -314% | -233% | -287% | +| 256% < Effective per UE paging arrival rate <= 512% | -764% | -262% | 61% | +| 512% < Effective per UE paging arrival rate <= 1024% | -339% | -85% | 57% | +| 1024% < Effective per UE paging arrival rate <= 2048% | -1027% | -674% | -364% | +| 2048% < Effective per UE paging arrival rate <= 4096% | -131% | -8% | -332% | +| 4096% < Effective per UE paging arrival rate <= 8192% | -785% | -87% | -72% | + +Bar chart showing Power saving gain [%] for min, mean, and max across different UE paging arrival rate categories. The chart shows significant power savings for some configurations, with values ranging from -1027% to 61%. + +Figure 8.1.1.2-2 + +Note1: FAR is assumed as follows: + +- FAR = 0 is simulated by [8A-5], [8A-11], [8A-8], [8A-14] +- FAR = 0.1% is simulated by [8A-4], [8A-17], [8A-9], [8A-11], [8A-16] +- FAR = 1% is simulated by [8A-4], [8A-17], [8A-11], [8A-16], [8A-8] + +Note2: For (FAR, N, T), [8A-3] assumes (T= 5ms, N=1), [8A-15] assumes (T=1ms, N=1), while other companies assume T = I-DRX cycle period, N value in (FAR, N, T) is summarized in table 8.1.1.2-1. + +###### 8.1.1.2.1.3 Latency + +I-DRX cycle = 1.28s, T = I-DRX cycle, effective per UE paging arrival rate <=8% + +![Bar chart showing Legacy PO latency metrics (min, mean, max LP-WUS and mean I-DRX) for various configurations (8A-3 to 8A-17).](578d2763eaf3edf3f1bd6657455ad54a_img.jpg) + +This bar chart displays latency metrics for Legacy PO across eleven configurations. The y-axis represents latency in milliseconds, ranging from 0 to 1800. The x-axis lists configurations: 8A-3, 8A-13, 8A-7, 8A-5, 8A-17, 8A-16, 8A-8, 8A-14, 8A-15, 8A-11, and 8A-4. For each configuration, four bars are shown: min:LP-WUS Latency [ms] (blue), mean:LP-WUS Latency [ms] (orange), max:LP-WUS Latency [ms] (grey), and mean:I-DRX latency[ms] (yellow). The exact values are labeled above each bar. + +| Configuration | min:LP-WUS Latency [ms] | mean:LP-WUS Latency [ms] | max:LP-WUS Latency [ms] | mean:I-DRX latency[ms] | +|---------------|-------------------------|--------------------------|-------------------------|------------------------| +| 8A-3 | 1090 | 1090 | 1091 | | +| 8A-13 | 1383 | 1383 | 1382 | | +| 8A-7 | 902 | 902 | 902 | 672 | +| 8A-5 | 420 | 571 | 990 | 670 | +| 8A-17 | 1153 | 1178 | 1213 | 768 | +| 8A-16 | 1050 | 1050 | 1053 | 791 | +| 8A-8 | 1069 | 1133 | 1281 | 715 | +| 8A-14 | 1076 | 1189 | 1526 | 640 | +| 8A-15 | 1220 | 1220 | 1220 | 640 | +| 8A-11 | 1104 | 1162 | 1162 | 636 | +| 8A-4 | 1100 | 1159 | 1220 | 640 | + +Bar chart showing Legacy PO latency metrics (min, mean, max LP-WUS and mean I-DRX) for various configurations (8A-3 to 8A-17). + +Figure 8.1.1.2-3: Legacy PO + +Note: [8A-5] assumes UE-specific indication and therefore latency is the time interval between data arrival at the gNB until the UE finish sync/re-sync for MR, while other companies assume latency is the time interval between data arrival at the gNB until the first PO that UE can monitor for paging message. + +![Bar chart showing Dynamic PO latency metrics (min, mean, max LP-WUS and mean I-DRX) for configurations 8A-13, 8A-5, and 8A-11.](21282638f01b60bb72acf07272e24942_img.jpg) + +This bar chart displays latency metrics for Dynamic PO across three configurations: 8A-13, 8A-5, and 8A-11. The y-axis represents latency in milliseconds, ranging from 0 to 800. The x-axis lists the configurations. For each configuration, four bars are shown: min:LP-WUS Latency [ms] (blue), mean:LP-WUS Latency [ms] (orange), max:LP-WUS Latency [ms] (grey), and mean:I-DRX latency[ms] (yellow). The exact values are labeled above each bar. + +| Configuration | min:LP-WUS Latency [ms] | mean:LP-WUS Latency [ms] | max:LP-WUS Latency [ms] | mean:I-DRX latency[ms] | +|---------------|-------------------------|--------------------------|-------------------------|------------------------| +| 8A-13 | 450 | 450 | 450 | | +| 8A-5 | 420 | 420 | 420 | 670 | +| 8A-11 | 500 | 500 | 500 | 637 | + +Bar chart showing Dynamic PO latency metrics (min, mean, max LP-WUS and mean I-DRX) for configurations 8A-13, 8A-5, and 8A-11. + +Figure 8.1.1.2-4: Dynamic PO + +##### 8.1.1.2.2 Observations + +For continuous and duty cycle ratio = 50% based LP-WUS monitoring, the following observations are made with the assumption that + +- I-DRX cycle = 1.28s + - T = I-DRX cycle + - MR ramp-up time, transition energy = 400ms, 15000unit + - no RRM measurement performed by MR or LR, or RRM measurement offloaded to LR or MR RRM relaxed at least 8 times of I-DRX cycle + - MR in ultra-deep sleep. + - FAR $\leq$ 1% (0%, 0.001%, 0.1%, 1%) + - effective per UE paging arrival rate $\leq$ 8% +- 1) For WUR ON power $\leq$ 1unit +- Effective per UE paging arrival rate $\leq$ 1% + - Results in [8A-2], [8A-4], [8A-5], [8A-7], [8A-8], [8A-9], [8A-11], [8A-13], [8A-14], [8A-15], [8A-16], [8A-17] show that compared with i-DRX with or without PEI, LP-WUS provides mean power saving gain (average: 61.5%, range: 21%~97%, which assumes FAR reference time T= 1280ms. + - Results in [8A-3] show that compared with i-DRX with or without PEI, LP-WUS provides mean power saving gain (-12%) which assumes FAR reference time T= 5ms. + - 1%$ 1unit +- Effective per UE paging arrival rate $\leq$ 1% + - Results in [8A-4], [8A-5], [8A-8], [8A-9], [8A-11], [8A-14], [8A-16], [8A-17] show that compared with i-DRX with or without PEI, LP-WUS provides mean power saving gain (average: -248.5%, range: -674%~61%) + - 1%eff, R) = (<=1%, (0.1%,1%], (1%,10%] ) + +I-DRX cycle = 1.28s, 0.1%< Effective per UE paging arrival rate <=1%, 1% 16times | 8A-3 | -193% | -193% | -193% | +| | 8A-13 | 72% | 72% | 72% | +| | 8A-17 | 44% | 44% | 44% | +| | 8A-16 | 78% | 78% | 78% | +| | 8A-8 | 66% | 66% | 66% | +| | 8A-15 | 90% | 90% | 90% | +| MR offload RRM to LR | 8A-3 | -41% | -41% | -41% | +| | 8A-7 | 99% | 99% | 99% | +| | 8A-5 | 88% | 88% | 88% | +| | 8A-17 | 92% | 92% | 92% | +| | 8A-16 | 91% | 91% | 91% | +| | 8A-8 | 97% | 97% | 97% | + +Bar chart showing Power saving gain [%] for various configurations. The chart is divided into four groups: 'no RRM relaxed', 'MR relaxed < 8times', '8times <= MR relaxed <= 16times', and 'MR offload RRM to LR'. Each group contains multiple bars for configurations 8A-3, 8A-16, 8A-8, 8A-15, 8A-11, and 8A-12. Each bar is labeled with its percentage value, ranging from -702% to 99%. + +Figure 8.1.1.5-1 + +Note1: [8A-15] assumes that the MR is in deep sleep when there is no any MR RRM relaxation, while other companies assume MR ultra-deep sleep + +Note2: [8A-12] assumes MR ramp-up time, transition energy is 100ms, 2000unit(not aligned with agreed assumption) + +Note3: FAR is assumed as follows: + +- FAR = 0 is simulated by [8A-3], [8A-11], [8A-8], [8A-5] +- FAR = 0.001% is simulated by [8A-12], [8A-15] +- FAR = 0.1% is simulated by [8A-3], [8A-4], [8A-17], [8A-11], [8A-13], [8A-16], [8A-8] +- FAR = 1% is simulated by [8A-3], [8A-17], [8A-1], [8A-10], [8A-16], [8A-8], [8A-7], [8A-4] + +Note 4: Different LR measurement periodicity are used by companies + +##### 8.1.1.5.2 Observations + +For RRM with duty-cycled LP-WUS monitoring, the following observations are made with the assumption that + +- I-DRX cycle = 1.28s +- MR in ultra-deep sleep +- Effective per UE paging arrival rate $\leq 1\%$ +- LP-WUR duty cycle ratio $\leq 1\%$ +- MR ramp-up time, transition energy = 400ms, 15000unit +- FAR $\leq 1\%$ (0%, 0.001%, 0.1%, 1%) + +###### Observations: + +- 1) For (Effective per UE paging arrival rate, LP-WUR on state power, FAR) = ( $\leq 1\%$ , $\leq 1$ unit, $\leq 1\%$ ), compared with i-DRX, LP-WUS operation with + - No MR RRM relaxed + - Results in [8A-3], [8A-8], [8A-11], [8A-12], [8A-16] show that compared with i-DRX with or without PEI, LP-WUS provide mean power saving gain (average: -211%, range: -624%~-5%), assuming MR enters ultra-deep sleep + - Results in [8A-15] show that compared with i-DRX with or without PEI, LP-WUS provides power saving gain 21%, assuming MR enters deep sleep + - MR relaxed $< 8$ times + - Results in [8A-1], [8A-3], [8A-8], [8A-9], [8A-15], [8A-16] show that compared with i-DRX with or without PEI, LP-WUS provide mean power saving gain (average: 4%, range: -18%~50%) + - $8$ times $\leq$ MR relaxed $\leq 16$ times + - Results in [8A-1], [8A-3], [8A-4], [8A-8], [8A-9], [8A-11], [8A-12], [8A-13], [8A-15] show that compared with i-DRX with or without PEI, LP-WUS provide mean power saving gain (average: 40%, range: -18%~60%) + - MR relaxed $> 16$ times + - Results in [8A-1], [8A-3], [8A-4], [8A-8], [8A-11], [8A-13], [8A-15], [8A-16], [8A-17] show that compared with i-DRX with or without PEI, LP-WUS provide mean power saving gain (average: 60%, range: 22%~90%) + - MR offload RRM to LR + - Results in [8A-3], [8A-4], [8A-5], [8A-7], [8A-8], [8A-10], [8A-11], [8A-15], [8A-16], [8A-17] show that compared with i-DRX with or without PEI, LP-WUS provide mean power saving gain (average: 83%, range: 76%~94%) + +#### 8.1.1.6 RRM for LP-WUR continuously monitoring + +In this clause, measurement performed by MR only and MR RRM relaxed X times and RRM offload to LR are studied for continuous LP-WUS monitoring. In addition, the following is assumed, + +- I-DRX cycle = 1.28s +- MR in ultra-deep sleep +- LP-WUR on state power $\leq 1$ unit +- Effective per UE paging arrival rate $\leq 1\%$ +- MR ramp-up time, transition energy = 400ms, 15000unit +- FAR $\leq 1\%$ (0%, 0.001%, 0.1%, 1%) + +##### 8.1.1.6.1 Collection of the results + +###### 8.1.1.6.1.1 LR ( $R_{\text{eff}}$ , $P_{\text{WURON}}$ , FAR) = ( $\leq 1$ unit, $\leq 1\%$ , $\leq 1\%$ ) + +I-DRX cycle = 1.28s, Effective per UE paging arrival rate $\leq 1\%$ , LP-WUR on state power $\leq 1$ unit, baseline: I-DRX, FAR $\leq 1\%$ (0%, 0.001%, 0.1%, 1%) + +![Bar chart showing power saving gain percentages for various RRM configurations. The chart compares min, mean, and max power saving gains across four main categories: no RRM relaxed, MR relaxed < 8times, 8times <= MR relaxed <= 16times, MR relaxed > 16times, and MR offload RRM to LR. Each category has sub-bars for different MR and LP-WUR configurations.](97044adf6c74dba676df34647a122614_img.jpg) + +| RRM Configuration | MR / LP-WUR | min:Power saving gain [%] | mean:Power saving gain [%] | max:Power saving gain [%] | +|---------------------------------------|-------------|---------------------------|----------------------------|---------------------------| +| 8A-16 no RRM relaxed | 8A-16 | -77% | 20% | 20% | +| | 8A-15 | -77% | 20% | 20% | +| | 8A-11 | -13% | -567% | -644% | +| 8A-9 MR relaxed < 8times | 8A-9 | 7% | 11% | 11% | +| | 8A-16 | 49% | 99% | 57% | +| | 8A-15 | 25% | 20% | 20% | +| 8A-13 8times <= MR relaxed <= 16times | 8A-13 | -8% | 20% | 20% | +| | 8A-5 | 10% | 67% | 55% | +| | 8A-9 | 55% | 58% | 57% | +| | 8A-15 | 30% | 55% | 58% | +| | 8A-11 | -16% | 55% | 58% | +| | 8A-4 | -103% | 2% | 55% | +| 8A-13 MR relaxed > 16times | 8A-13 | -7% | 77% | 74% | +| | 8A-5 | 53% | 54% | 44% | +| | 8A-17 | 43% | 43% | 41% | +| | 8A-16 | 89% | 89% | 89% | +| | 8A-8 | 78% | 73% | 73% | +| | 8A-15 | 53% | 53% | 53% | +| | 8A-11 | 37% | 37% | 37% | +| | 8A-4 | -42% | 83% | 83% | +| 8A-7 MR offload RRM to LR | 8A-7 | 45% | 84% | 98% | +| | 8A-5 | 4% | 68% | 89% | +| | 8A-17 | 2% | 52% | 73% | +| | 8A-16 | 86% | 86% | 86% | +| | 8A-8 | 43% | 83% | 83% | +| | 8A-14 | 31% | 99% | 92% | +| | 8A-15 | 68% | 68% | 68% | +| | 8A-11 | 4% | 4% | 4% | + +Bar chart showing power saving gain percentages for various RRM configurations. The chart compares min, mean, and max power saving gains across four main categories: no RRM relaxed, MR relaxed < 8times, 8times <= MR relaxed <= 16times, MR relaxed > 16times, and MR offload RRM to LR. Each category has sub-bars for different MR and LP-WUR configurations. + +Figure 8.1.1.6-1 + +Note1: [8A-15] assumes that the MR is in deep sleep when there is no any MR RRM relaxation while other companies assume ultra-deep sleep. + +Note2: FAR is assumed as follow: + +- FAR = 0 is simulated by [8A-11], [8A-8], [8A-5], [8A-14] +- FAR = 0.001% is simulated by [8A-15] +- FAR = 0.1% is simulated by [8A-4], [8A-17], [8A-11], [8A-13], [8A-16], [8A-9], [8A-5] +- FAR = 1% is simulated by [8A-4], [8A-17], [8A-11], [8A-16], [8A-8], [8A-7], [8A-5] + +Note3: For (FAR, N, T), [8A-3] assumes (T= 5ms, N=1), [8A-15] assumes (T=1ms, N=1), while other companies assume T = I-DRX cycle period, N value in (FAR, N, T) is summarized in table 8.1.1.2-1. + +##### 8.1.1.6.2 Observations + +For RRM with continuous LP-WUS monitoring, the following observations are made with the assumption that + +- I-DRX cycle = 1.28s +- MR in ultra-deep sleep +- LP-WUR on state power $\leq$ 1unit +- Effective per UE paging arrival rate $\leq$ 1% +- MR ramp-up time, transition energy = 400ms, 15000unit +- FAR $\leq$ 1% (0%, 0.001%, 0.1%, 1%) + +###### Observations + +1) For (Effective per UE paging arrival rate, ON power, FAR) = ( $\leq$ 1%, $\leq$ 1unit, $\leq$ 1%), compared with i-DRX, LP-WUS operation with + +- No MR RRM relaxed + - Results in [8A-11], [8A-16], show that compared with i-DRX with or without PEI, LP-WUS provides mean power saving gain (average: -325.5%, range: -644%~-7%) assuming MR enters ultra-deep sleep + - Results in [8A-15] show that compared with i-DRX with or without PEI, LP-WUS provides power saving gain 20%, assuming MR enters deep sleep +- MR relaxed $<$ 8 times + +- Results in [8A-8], [8A-15], [8A-16] show that compared with i-DRX with or without PEI, LP-WUS provides mean power saving gain (average: 22%, range: 7%~49%) +- 8 times $\leq$ MR relaxed $\leq$ 16 times + - Results in [8A-4], [8A-5], [8A-9], [8A-11], [8A-13], [8A-15] show that compared with i-DRX with or without PEI, LP-WUS provide mean power saving gain (average: 32%, range: 2%~61%) +- MR relaxed $>$ 16 times + - Results in [8A-4], [8A-5], [8A-8], [8A-11], [8A-13], [8A-15], [8A-16], [8A-17] show that compared with i-DRX with or without PEI, LP-WUS provide mean power saving gain (average: 57%, range: 37%~80%) +- MR offload RRM to LR + - Results in [8A-4], [8A-5], [8A-7], [8A-8], [8A-11], [8A-14], [8A-15], [8A-16], [8A-17] show that compared with i-DRX with or without PEI, LP-WUS provide mean power saving gain (average: 74%, range: 52%~87%) + +#### 8.1.1.7 Impact by various MR sync/re-sync assumptions + +##### 8.1.1.7.1 Collection of the results + +###### 8.1.1.7.1.1 LR ( $R_{\text{eff}}$ , $R$ , $P_{\text{WURON}}$ , FAR) = ( $\leq 1\%$ , $\leq 1\%$ , $\leq 4$ unit, $\leq 1\%$ ) + +- I-DRX cycle = 1.28s, +- FAR $\leq 1\%$ , (0%, 0.1%, 1%) +- Effective per UE paging arrival rate $\leq 1\%$ , +- duty cycle ratio $\leq 1\%$ , +- no RRM measurement performed by MR or LR, or RRM measurement offloaded to LR or MR RRM relaxed at least 8 times of I-DRX cycle +- baseline: I-DRX + +![Bar chart showing Power saving gain [%] for various configurations. The chart compares min, mean, and max power saving gains across different MR sync/re-sync energy consumption levels and configurations (8A-16, 8A-4, 8A-7, 8A-5, 8A-8, 8A-4, 8A-17, 8A-9, 8A-10, 8A-11, 8A-4).](fe8840a79cf6b30f8b2284064f3d2a36_img.jpg) + +| Configuration | min:Power saving gain [%] | mean:Power saving gain [%] | max:Power saving gain [%] | +|---------------|---------------------------|----------------------------|---------------------------| +| 8A-16 | 70% | 82% | 97% | +| 8A-4 | 18% | 58% | 92% | +| 8A-7 | 85% | 87% | 88% | +| 8A-5 | 68% | 82% | 92% | +| 8A-8 | 51% | 74% | 92% | +| 8A-4 | 45% | 66% | 92% | +| 8A-17 | 22% | 61% | 91% | +| 8A-9 | 61% | 67% | 70% | +| 8A-10 | 81% | 83% | 85% | +| 8A-11 | 32% | 77% | 99% | +| 8A-4 | -5% | 41% | 89% | + +Bar chart showing Power saving gain [%] for various configurations. The chart compares min, mean, and max power saving gains across different MR sync/re-sync energy consumption levels and configurations (8A-16, 8A-4, 8A-7, 8A-5, 8A-8, 8A-4, 8A-17, 8A-9, 8A-10, 8A-11, 8A-4). + +Figure 8.1.1.7-1 + +Note: For [8A-4] results, different SNR assumptions for the baseline scheme contribute to the difference in power saving gain between (sync/re-sync energy $\leq 1000$ ) and ( $1000 < \text{sync/re-sync energy} \leq 3000$ ). + +Note: FAR is assumed as follow: + +- FAR = 0 is simulated by [8A-11], [8A-8], [8A-5] +- FAR = 0.1% is simulated by [8A-4], [8A-17], [8A-11], [8A-16], [8A-9], [8A-8] +- FAR = 1% is simulated by [8A-4], [8A-17], [8A-11], [8A-10], [8A-16], [8A-8], [8A-7] + +8.1.1.7.1.2 LR ( $R_{\text{eff}}$ , $R$ , $P_{\text{WURON}}$ , FAR) = ( $\leq 1\%$ , $\leq 1\%$ , $\geq 10\text{unit}$ , $\leq 1\%$ ) + +- DRX cycle = 1.28s, +- FAR $\leq 1\%$ , (0%, 0.1%, 1%) +- Effective per UE paging arrival rate $\leq 1\%$ , +- duty cycle ratio $\leq 1\%$ , +- no RRM measurement performed by MR or LR, or RRM measurement offloaded to LR or MR RRM relaxed at least 8 times of I-DRX cycle + +- baseline: I-DRX + +![Bar chart showing Power saving gain [%] for different MR sync/re-sync energy consumption scenarios. The chart compares min, mean, and max power saving gains across six categories: 8A-16, 8A-7, 8A-8, 8A-9, 8A-10, and 8A-11. The y-axis ranges from -150% to 150%.](5edd3710b7b5d815ca793a5a5acd806e_img.jpg) + +| Scenario | min:Power saving gain [%] | mean:Power saving gain [%] | max:Power saving gain [%] | +|---------------------------------------------------------|---------------------------|----------------------------|---------------------------| +| MR sync/re-sync energy consumption ≤ 1000 (8A-16) | 45% | 71% | 91% | +| 1000 < MR sync/re-sync energy consumption ≤ 3000 (8A-7) | 75% | 79% | 83% | +| (8A-8) | 2% | 46% | 85% | +| MR sync/re-sync energy consumption > 3000 (8A-9) | 25% | 41% | 56% | +| (8A-10) | 65% | 70% | 74% | +| (8A-11) | -105% | 42% | 93% | + +Bar chart showing Power saving gain [%] for different MR sync/re-sync energy consumption scenarios. The chart compares min, mean, and max power saving gains across six categories: 8A-16, 8A-7, 8A-8, 8A-9, 8A-10, and 8A-11. The y-axis ranges from -150% to 150%. + +Figure 8.1.1.7-2 + +Note: FAR is assumed as follow: + +- FAR = 0 is simulated by [8A-8], [8A-11] +- FAR = 0.1% is simulated by [8A-11], [8A-16], [8A-9], [8A-8] +- FAR = 1% is simulated by [8A-11], [8A-16], [8A-8], [8A-7], [8A-10] + +### 8.1.1.7.2 Observations + +For various MR sync/re-sync evaluation, the following observations are made with the assumption that + +- I-DRX cycle = 1.28s +- LP-WUR duty cycle ratio ≤ 1% +- Effective per UE paging arrival rate ≤ 1% +- no RRM measurement performed by MR or LR, or RRM measurement offloaded to LR or MR RRM relaxed at least 8 times of I-DRX cycle + +- MR in ultra-deep sleep. +- FAR $\leq 1\%$ (0%, 0.1%, 1%) + +Observations: + +- 1) For (Effective per UE paging arrival rate, duty cycle ratio, ON power, FAR) = ( $\leq 1\%$ , $\leq 1\%$ , $\leq 4$ unit, $\leq 1\%$ ) + - $1000\text{unit} < \text{MR sync/re-sync energy consumption} \leq 3000\text{unit}$ + - Results in [8A-4], [8A-5], [8A-7], [8A-8] show that compared with i-DRX with or without PEI, LP-WUS provides mean power saving gain (66%~87%) + - $\text{MR sync/re-sync energy consumption} > 3000\text{unit}$ + - Results in [8A-4], [8A-9], [8A-10], [8A-11], [8A-17] show that compared with i-DRX with or without PEI, LP-WUS provides mean power saving gain (41%~83%) +- 2) For (Effective per UE paging arrival rate, duty cycle ratio, ON power, FAR) = ( $\leq 1\%$ , $\leq 1\%$ , $\geq 10$ unit, $\leq 1\%$ ) + - $1000\text{unit} < \text{MR sync/re-sync energy consumption} \leq 3000\text{unit}$ + - Results in [8A-7], [8A-8] show that compared with i-DRX with or without PEI, LP-WUS provides mean power saving gain (46%~79%) + - $\text{MR sync/re-sync energy consumption} > 3000\text{unit}$ + - Results in [8A-9], [8A-10], [8A-11] show that compared with i-DRX with or without PEI, LP-WUS provides mean power saving gain (41%~70%) + +### 8.1.1.8 Impact by various MR ramp-up time/transition energy assumptions and sleep state + +#### 8.1.1.8.1 Collection of the results + +##### 8.1.1.8.1.1 LR ( $R_{\text{eff}}$ , $R$ , $P_{\text{WURON}}$ , FAR) = ( $\leq 1\%$ , $\leq 1\%$ , $\leq 4$ unit, $\leq 1\%$ ) + +- DRX cycle = 1.28s, +- Effective per UE paging arrival rate $\leq 1\%$ , +- duty cycle ratio $\leq 1\%$ , +- no RRM measurement performed by MR or LR, or RRM measurement offloaded to LR or MR RRM relaxed at least 8 times of I-DRX cycle- +- baseline: I-DRX + +- FAR<=1% (0%, 0.001%, 0.1%, 1%) + +![Bar chart showing Power saving gain [%] for various configurations (8A-3 to 8A-17) across three sleep modes: 450, 15000, and 40000. The chart compares min, mean, and max power saving gains. The y-axis ranges from -80% to 120%.](b9eb2f58f854a342d2452f842630a06a_img.jpg) + +| Sleep Mode | Configuration | min:Power saving gain [%] | mean:Power saving gain [%] | max:Power saving gain [%] | +|------------|---------------|---------------------------|----------------------------|---------------------------| +| 450 | 8A-3 | 65% | 64% | 58% | +| | 8A-7 | 34% | 34% | 34% | +| | 8A-10 | 40% | 45% | 45% | +| | 8A-1 | 47% | 54% | 54% | +| | 8A-11 | 50% | 50% | 54% | +| 15000 | 8A-3 | 45% | 92% | 99% | +| | 8A-13 | 15% | 80% | 99% | +| | 8A-7 | 85% | 85% | 88% | +| | 8A-5 | 68% | 82% | 92% | +| | 8A-17 | 22% | 61% | 91% | +| | 8A-9 | 61% | 67% | 70% | +| | 8A-16 | 70% | 82% | 97% | +| | 8A-8 | 46% | 73% | 92% | +| | 8A-10 | 81% | 85% | 88% | +| | 8A-15 | 59% | 90% | 98% | +| | 8A-1 | 35% | 73% | 93% | +| | 8A-11 | 32% | 77% | 99% | +| | 8A-4 | -31% | 43% | 92% | +| 40000 | 8A-13 | -70% | 88% | 88% | +| | 8A-7 | -60% | 14% | 90% | +| | 8A-1 | -60% | 37% | 84% | +| | 8A-17 | -60% | 37% | 84% | + +Bar chart showing Power saving gain [%] for various configurations (8A-3 to 8A-17) across three sleep modes: 450, 15000, and 40000. The chart compares min, mean, and max power saving gains. The y-axis ranges from -80% to 120%. + +Figure 8.1.1.8-1 + +Note1: 450 is associated with MR deep sleep and 15000/40000 is associated with MR ultra-deep sleep + +Note2: FAR is assumed as follows: + +- FAR = 0 is simulated by [8A-3], [8A-11,] [8A-5], [8A-8] +- FAR = 0.001% is simulated by [8A-15] +- FAR = 0.1% is simulated by [8A-3], [8A-17], [8A-11], [8A-16], [8A-9], [8A-13], [8A-8] +- FAR = 1% is simulated by [8A-3], [8A-17], [8A-11], [8A-16], [8A-13], [8A-8], [8A-10], [8A-1], [8A-7] + +8.1.1.8.1.2 LR (Reff, R, PWURON, FAR) = (<=1%, <=1%,>=10unit, <=1%) + +- DRX cycle = 1.28s, +- Effective per UE paging arrival rate <=1% +- duty cycle ratio<=1% +- no RRM measurement performed by MR(including measurement offloaded to LR) or MR RRM relaxed at least 8 times of I-DRX cycle, + +- baseline: I-DRX +- FAR<=1% (0%, 0.001%, 0.1%, 1%) + +![Bar chart showing power saving gain percentages for various configurations (8A-7, 8A-10, 8A-1, 8A-11, 8A-3, 8A-13, 8A-9, 8A-16, 8A-8, 8A-15) across different sleep durations (450, 15000, 40000). The chart displays min, mean, and max power saving gains. Notable values include -254% for 8A-13 at 450 sleep duration and 97% for 8A-3 at 450 sleep duration.](fad415ab62a56119f4584c45e1d9a55c_img.jpg) + +| Sleep Duration | Configuration | min:Power saving gain [%] | mean:Power saving gain [%] | max:Power saving gain [%] | +|----------------|---------------|---------------------------|----------------------------|---------------------------| +| 450 | 8A-7 | 22% | 29% | 29% | +| | 8A-10 | 22% | 29% | 29% | +| | 8A-1 | 51% | 51% | 51% | +| | 8A-11 | 5% | 30% | 43% | +| | 8A-3 | 87% | 93% | 97% | +| | 8A-13 | -254% | -11% | 77% | +| | 8A-7 | 77% | 75% | 82% | +| | 8A-9 | 25% | 41% | 56% | +| | 8A-16 | 45% | 71% | 91% | +| | 8A-8 | 2% | 46% | 85% | +| | 8A-15 | 65% | 76% | 91% | +| 15000 | 8A-1 | 83% | 88% | 88% | +| | 8A-11 | -105% | 42% | 93% | +| | 8A-13 | -27% | 25% | 61% | +| | 8A-1 | 66% | 70% | 70% | + +Bar chart showing power saving gain percentages for various configurations (8A-7, 8A-10, 8A-1, 8A-11, 8A-3, 8A-13, 8A-9, 8A-16, 8A-8, 8A-15) across different sleep durations (450, 15000, 40000). The chart displays min, mean, and max power saving gains. Notable values include -254% for 8A-13 at 450 sleep duration and 97% for 8A-3 at 450 sleep duration. + +Figure 8.1.1.8-2 + +Note1: 450 is associated with MR deep sleep and 15000/40000 is associated with MR ultra-deep sleep + +Note2: FAR is assumed as follows: + +- FAR = 0 is simulated by [8A-3], [8A-11], [8A-8] +- FAR = 0.001% is simulated by [8A-15] +- FAR = 0.1% is simulated by [8A-3], [8A-9], [8A-11], [8A-16], [8A-13], [8A-8] +- FAR = 1% is simulated by [8A-3], [8A-11], [8A-16], [8A-13], [8A-8], [8A-10], [8A-1], [8A-7] + +### 8.1.1.8.2 Observations + +For various MR ramp-up time/transition energy evaluation, the following observations are made with the assumption that + +- I-DRX cycle = 1.28s +- Effective per UE paging arrival rate <=1% + +- FAR $\leq 1\%$ (0%, 0.001%, 0.1%, 1%) +- LP-WUR duty cycle ratio $\leq 1\%$ +- no RRM measurement performed by MR or LR, or RRM measurement offloaded to LR or MR RRM relaxed at least 8 times of I-DRX cycle- +- MR in ultra-deep sleep when MR transition energy is 15000/40000unit +- MR in deep sleep when MR transition energy is 450unit. + +Observations: + +- 1) For (Effective per UE paging arrival rate, duty cycle ratio, ON power, FAR) = ( $\leq 1\%$ , $\leq 1\%$ , $\leq 4$ unit, $\leq 1\%$ ) + - (Baseline for MR ultra-deep sleep) MR ramp-up time, energy consumption = 400ms, 15000unit + - Results in [8A-1], [8A-3], [8A-4], [8A-5], [8A-7], [8A-8], [8A-9], [8A-10], [8A-11], [8A-13], [8A-15], [8A-16], [8A-17] show that compared with i-DRX with or without PEI, LP-WUS provide mean power saving gain (average: 76%, range: 43%~92%) + - (Optional for MR ultra-deep sleep) MR ramp-up time, energy consumption = 800ms, 40000unit + - Results in [8A-1], [8A-13], [8A-17] show that compared with i-DRX with or without PEI, LP-WUS provides mean power saving gain (average: 44%, range: 14%~82%) + - (MR deep sleep) MR ramp-up time, energy consumption = 10~20ms, 450unit + - Results in [8A-1], [8A-3], [8A-7], [8A-10], [8A-11] show that compared with i-DRX with or without PEI, LP-WUS provides mean power saving gain (average: 49%, range: 34%~64%) +- 2) For (Effective per UE paging arrival rate, duty cycle ratio, ON power, FAR) = ( $\leq 1\%$ , $\leq 1\%$ , $\geq 10$ unit, $\leq 1\%$ ) + - (Baseline for MR ultra-deep sleep) MR ramp-up time, energy consumption = 400ms, 15000unit + - Results in [8A-1], [8A-3], [8A-7], [8A-8], [8A-9], [8A-10], [8A-11], [8A-13], [8A-15], [8A-16] show that compared with i-DRX with or without PEI, LP-WUS provide mean power saving gain (average: 60%, range: -11%~93%) + - (Optional for MR ultra-deep sleep) MR ramp-up time, energy consumption = 800ms, 40000unit + - Results in [8A-1], [8A-13] show that compared with i-DRX with or without PEI, LP-WUS provides mean power saving gain (average: 49%, range: 25%~73%) + - (MR deep sleep) MR ramp-up time, energy consumption = 10~20ms, 450unit + - Results in [8A-1], [8A-7], [8A-10], [8A-11] show that compared with i-DRX with or without PEI, LP-WUS provides mean power saving gain (average: 35%, range: 29%~51%) + +## 8.1.2 RRC CONNECTED mode + +### 8.1.2.1 XR traffic model + +In this clause, the usage of LP-WUS for XR traffic is studied. + +The following schemes are compared, and the description of the schemes are as follows, + +- Always on + - i.e., no DRX, UE is always available for gNB scheduling +- C-DRX + - Including long and short DRX +- R17 PDCCH Scheme + - i.e., R17 PDCCH skipping and/or R17 SSSG switching, with or without C-DRX configuration +- R18 enhanced C-DRX + - i.e., aligning C-DRX cycle with non-integer traffic periodicity +- LP-WUS + - LP-WUS triggers the resumption of MR PDCCH monitoring from micro/light sleep e.g., via starting a PDCCH monitoring timer. + +Note: MR based RRM measurements were not explicitly modelled for power saving evaluation. + +8.1.2.1.1 Collection of the results + +8.1.2.1.1.1 DL only traffic + +![Bar chart titled 'Power saving gain (DL only traffic)' showing power saving percentages for various configurations. The y-axis ranges from 0.00% to 30.00%.](757a306a97d3f49cdd35ed06d9610d3e_img.jpg) + +| Configuration | Power Saving Gain | +|-----------------------------------------------------------------------------|-------------------| +| [8A-3] micro sleep WU R ON power r=4 unit low load jitter range: [-4, +4]ms | 12% | +| [8A-3] micro sleep WU R ON power r=4 unit high load | 11% | +| [8A-11] micro sleep WUR ON power <=1 unit low load | 8% | +| [8A-11] light sleep ON power <=1 unit low load | 14% | +| [8A-3] micro sleep WU R ON power r=4 unit low load | 2% | +| [8A-11] micro sleep WUR ON power <=1 unit high load | 7% | +| [8A-11] light sleep ON power <=1 unit high load | 12% | +| [8A-3] micro sleep WU R ON power r=4 unit high load | 2% | +| [8A-11] micro sleep WUR ON power <=1 unit low load | 15% | +| [8A-11] light sleep ON power <=1 unit low load | 26% | +| [8A-11] micro sleep WUR ON power <=1 unit high load | 15% | +| [8A-11] light sleep ON power <=1 unit high load | 24% | +| [8A-14] micro sleep WU R ON power r<=1 unit low load | 23% | +| [8A-13] micro sleep WUR ON power <=1 unit high load | 11% | +| [8A-7] sleep ON power <=1 unit high load | 19% | +| [8A-7] micro sleep WU R ON power r=10 unit high load | 7% | +| [8A-7] micro sleep WU R ON power r=4 unit high load | 14% | +| [8A-13] micro sleep WU R ON power r<=1 unit high load | 12% | +| [8A-14] micro sleep WU R ON power r<=1 unit low load | 7% | +| [8A-13] micro sleep WU R ON power r<=1 unit high load | 18% | + +Bar chart titled 'Power saving gain (DL only traffic)' showing power saving percentages for various configurations. The y-axis ranges from 0.00% to 30.00%. + +Figure 8.1.2.1-1 + +Note: The values shown in the figure are averaged gain. + +Note: For XR, all companies assume 60FPS DL only traffic. [8A-11], [8A-13] and [8A-7] assume the data rate of DL traffic is 30Mbps, [8A-14] assumes the data rate of DL traffic is 45Mbps. + +Note: For the case of R17 PDCCH as the baseline, [8A-13] evaluation included C-DRX, while [8A-14], [8A-7] results did not include C-DRX configuration + +![Bar chart titled 'Capacity (DL only traffic, low load)' showing various configurations and their utilization percentages.](4a8f09807c20be2a38e37e719a575eac_img.jpg) + +**Capacity (DL only traffic, low load)** + +| Configuration | Subframe Setting | Utilization | +|-------------------------|------------------|-------------| +| always on | [8A-11] | 100% | +| | [8A-14] | 98% | +| | [8A-3] | 100% | +| LP-WUS | [8A-11] | 100% | +| | [8A-14] | 97% | +| | [8A-3] | 100% | +| micro sleep | [8A-11] | 100% | +| | [8A-3] | 100% | +| light sleep | [8A-11] | 99% | +| | [8A-3] | 99% | +| short C-DRX | [8A-11] | 100% | +| R17 PDCCH+R18 enh.C-DRX | [8A-11] | 100% | +| | [8A-3] | 100% | +| R17 PDCCH | [8A-14] | 95% | +| | [8A-11] | 98% | +| R18 enh. C-DRX | [8A-14] | 100% | +| | [8A-11] | 100% | +| always on | [8A-11] | 100% | +| | [8A-14] | 99% | +| LP-WUS | [8A-11] | 100% | +| | [8A-3] | 100% | +| micro sleep | [8A-11] | 100% | +| | [8A-3] | 100% | +| light sleep | [8A-11] | 99% | +| | [8A-3] | 100% | +| R17 PDCCH+R18 enh.C-DRX | [8A-11] | 100% | + +Bar chart titled 'Capacity (DL only traffic, low load)' showing various configurations and their utilization percentages. + +Figure 8.1.2.1-2 + +![Bar chart titled 'Capacity (DL only traffic, high load)' showing various configurations and their utilization percentages under high load conditions.](d58ddc0c76684eabc4244486807245fe_img.jpg) + +**Capacity (DL only traffic, high load)** + +| Configuration | Subframe Setting | Utilization | +|-------------------------|------------------|-------------| +| always on | [8A-11] | 97.8% | +| | [8A-3] | 93.9% | +| | [8A-3] | 95.3% | +| LP-WUS | [8A-11] | 97.8% | +| | [8A-3] | 93.9% | +| | [8A-3] | 91.5% | +| micro sleep | [8A-7] | 80.5% | +| | [8A-11] | 81.9% | +| light sleep | [8A-3] | 86.5% | +| | [8A-11] | 97.8% | +| short C-DRX | [8A-3] | 94.3% | +| R17 PDCCH+R18 enh.C-DRX | [8A-11] | 90.3% | +| | [8A-3] | 97.8% | +| R17 PDCCH | [8A-3] | 93.9% | +| | [8A-7] | 95.8% | +| always on | [8A-11] | 90.2% | +| | [8A-3] | 82.5% | +| | [8A-11] | 96.9% | +| LP-WUS | [8A-3] | 90.9% | +| | [8A-11] | 90.2% | +| micro sleep | [8A-3] | 100% | +| | [8A-11] | 100% | +| light sleep | [8A-3] | 100% | +| | [8A-11] | 100% | +| R17 PDCCH+R18 enh.C-DRX | [8A-11] | 100% | + +jitter range: [-4, +4]ms + +Bar chart titled 'Capacity (DL only traffic, high load)' showing various configurations and their utilization percentages under high load conditions. + +Figure 8.1.2.1-3 + +Note: The results with the setting that number of deployed UE per cell exceeds the upper bound of system capacity are excluded. + +Note: High load and low load are reported by companies, or the low load is for the case that number of UE per cell is no more than half of the capacity upper bound and high load is for the others. + +Note: The values shown in the figure are averaged gain. + +8.1.2.1.1.2 DL + UL traffics + +![Bar chart titled 'Power saving gain (DL+ UL traffic)' showing power saving percentages for various configurations of [8A-3] and [8A-11] micro sleep and WUR settings under low and high load conditions. The chart compares these settings to R17 PDCCH+R18 enh.CDRX.](145582dc8830099a0aa6ca1234f0acd1_img.jpg) + +| Configuration | Power Saving Gain | Load | Jitter Range | +|-------------------------------------------|-------------------|------|--------------------------| +| [8A-3] micro sleep WUR ON power =4 unit | 4% | low | jitter range: [-4, +4]ms | +| [8A-3] micro sleep WUR ON power =4 unit | 3% | high | | +| [8A-11] micro sleep WUR ON power <=1 unit | 10% | low | jitter range: [-4, +4]ms | +| [8A-11] light sleep WUR ON power <=1 unit | 18% | low | | +| [8A-3] micro sleep WUR ON power =4 unit | 0% | high | jitter range: [-4, +4]ms | +| [8A-11] micro sleep WUR ON power <=1 unit | 9% | high | | +| [8A-11] light sleep WUR ON power <=1 unit | 16% | high | jitter range: [-4, +4]ms | +| [8A-3] micro sleep WUR ON power =4 unit | 0% | low | | +| [8A-11] micro sleep WUR ON power <=1 unit | 12% | low | jitter range: [-8, +8]ms | +| [8A-11] light sleep WUR ON power <=1 unit | 20% | low | | +| [8A-11] micro sleep WUR ON power <=1 unit | 10% | high | jitter range: [-8, +8]ms | +| [8A-11] light sleep WUR ON power <=1 unit | 17% | high | | + +Compared to R17 PDCCH+R18 enh.CDRX + +Bar chart titled 'Power saving gain (DL+ UL traffic)' showing power saving percentages for various configurations of [8A-3] and [8A-11] micro sleep and WUR settings under low and high load conditions. The chart compares these settings to R17 PDCCH+R18 enh.CDRX. + +Figure 8.1.2.1-4 + +Note: [8A-11] provides both the results for single DL flow or two DL flows (DL video flow: 60FPS, 30Mbps and 10ms PDB; DL audio flow: 10ms periodicity, 0.756Mbps and 30ms PDB) and single UL flow (UL pose flow: 16.67ms periodicity and 10ms PDB). + +Note: [8A-3] provide the results for DL two flows (DL video flow: 60FPS and 10ms PDB; DL audio flow: 10ms periodicity and 30ms PDB) and single UL flow (UL pose flow: 4ms periodicity and 10ms PDB). + +Note: The values shown in the figure are averaged gain. + +![Bar chart showing Capacity (DL +UL traffic, low load) for various configurations. The Y-axis ranges from 70.00% to 105.00%. The X-axis shows configurations for always on, LP-WUS (micro sleep, light sleep), short C-DRX, R17 PDCCH+R18 enh.C-DRX, and R17 PDCCH+R18 enh.C-DRX with jitter ranges [-4, +4]ms and [-8, +8]ms. Bars are labeled with values like 100%, 99%, 98%, 93%.](a75c2cd397490e8a9b0fa811a6a1b2c3_img.jpg) + +### Capacity (DL +UL traffic, low load) + +| Configuration | Sub-Configuration | Value | +|-------------------------|---------------------|-------| +| always on | [8A-11] | 100% | +| | [8A-3] | 100% | +| LP-WUS | micro sleep [8A-11] | 100% | +| | micro sleep [8A-3] | 99% | +| | light sleep [8A-11] | 99% | +| short C-DRX | [8A-3] | 98% | +| R17 PDCCH+R18 enh.C-DRX | [8A-11] | 100% | +| | [8A-3] | 99% | +| always on | [8A-11] | 100% | +| | [8A-11] | 99% | +| | light sleep [8A-11] | 93% | +| | [8A-11] | 99% | + +jitter range: [-4, +4]ms + +jitter range: [-8, +8]ms + +Bar chart showing Capacity (DL +UL traffic, low load) for various configurations. The Y-axis ranges from 70.00% to 105.00%. The X-axis shows configurations for always on, LP-WUS (micro sleep, light sleep), short C-DRX, R17 PDCCH+R18 enh.C-DRX, and R17 PDCCH+R18 enh.C-DRX with jitter ranges [-4, +4]ms and [-8, +8]ms. Bars are labeled with values like 100%, 99%, 98%, 93%. + +Figure 8.1.2.1-5 + +![Bar chart showing Capacity (DL +UL traffic, high load) for various configurations. The Y-axis ranges from 70.00% to 100.00%. The X-axis shows configurations for always on, LP-WUS (micro sleep, light sleep), short C-DRX, R17 PDCCH+R18 enh.C-DRX, and R17 PDCCH+R18 enh.C-DRX with jitter ranges [-4, +4]ms and [-8, +8]ms. Bars are labeled with values like 98%, 94%, 89%, 82%, 87%, 92%, 96%.](dfb5a77d296b5c152ba6033adef76a80_img.jpg) + +### Capacity (DL +UL traffic, high load) + +| Configuration | Sub-Configuration | Value | +|-------------------------|---------------------|-------| +| always on | [8A-11] | 98% | +| | [8A-3] | 94% | +| LP-WUS | micro sleep [8A-11] | 98% | +| | micro sleep [8A-3] | 89% | +| | light sleep [8A-11] | 82% | +| short C-DRX | [8A-3] | 87% | +| R17 PDCCH+R18 enh.C-DRX | [8A-11] | 98% | +| | [8A-3] | 92% | +| always on | [8A-11] | 98% | +| | [8A-11] | 96% | +| | light sleep [8A-11] | 82% | +| | [8A-11] | 97% | + +jitter range: [-4, +4]ms + +jitter range: [-8, +8]ms + +Bar chart showing Capacity (DL +UL traffic, high load) for various configurations. The Y-axis ranges from 70.00% to 100.00%. The X-axis shows configurations for always on, LP-WUS (micro sleep, light sleep), short C-DRX, R17 PDCCH+R18 enh.C-DRX, and R17 PDCCH+R18 enh.C-DRX with jitter ranges [-4, +4]ms and [-8, +8]ms. Bars are labeled with values like 98%, 94%, 89%, 82%, 87%, 92%, 96%. + +Figure 8.1.2.1-6 + +- Note: The results with the setting that number of deployed UE exceed the upper bound of system capacity are excluded. +- Note: High load and low load are reported by companies, or the low load is for the case that Number of UE per cell is no more than half of the capacity upper bound and high load is for the others. +- Note: The values shown in the figure are averaged gain. + +#### 8.1.2.1.2 Observations + +Note: The average value, the min and max value in the range is calculated across all companies' results + +For **DL only** XR traffic in **low load**, compared with legacy schemes, + +- For power saving gain, LP-WUS can provide + - Results in [8A-3], [8A-11], [8A-14] show that power saving gain (average: 11.2%, range: 2%~23%), assuming MR enters **micro** sleep during LP-WUS monitoring. + - Results in [8A-11] show that power saving gain (average: 20%, range: 14%~26%), assuming MR enters **light** sleep during LP-WUS monitoring. + - the legacy schemes evaluated by companies included R17 PDCCH skipping, SSSG switching, R18 enhanced DRX, R15 short CDRX. +- For satisfied UE rate, LP-WUS can provide + - Results in [8A-3], [8A-11], [8A-14] show that the relative impact of satisfied UE rate (average: +0.3%, range: -1%~+2%), assuming MR enters **micro** sleep during LP-WUS monitoring. + - Results in [8A-11] show that the relative impact of satisfied UE rate -1%, assuming MR enters **light** sleep during LP-WUS monitoring. + - the legacy schemes evaluated by companies included R17 PDCCH skipping, SSSG switching, R18 enhanced DRX, R15 short CDRX. + +For **DL only** XR traffic in **high load**, compared with legacy schemes, + +- For power saving gain, LP-WUS can provide + - Results in [8A-3] [8A-11] [8A-13] [8A-7] show that power saving gain (average: 11.6%, range: 2%~19%), assuming MR enters **micro** sleep during LP-WUS monitoring. + - Results in [8A-11] show that power saving gain (average: 18%, range: 12%~24%), assuming MR enters **light** sleep during LP-WUS monitoring. + - the legacy schemes evaluated by companies included R17 PDCCH skipping, SSSG switching, R18 enhanced DRX, R15 short CDRX. +- For satisfied UE rate, LP-WUS can provide + - Results in [8A-3] [8A-11] [8A-13] [8A-7] show that the relative impact of satisfied UE rate (average: +0.96%, range: -3.8%~+5%), assuming MR enters **micro** sleep during LP-WUS monitoring. + +- Results in [8A-11] show that the relative impact of satisfied UE rate (average: -15.2%, range: -15.9%~--14.4%), assuming MR enters **light** sleep during LP-WUS monitoring. +- the legacy schemes evaluated by companies included R17 PDCCH skipping, SSSG switching, R18 enhanced DRX, R15 short CDRX. + +For **DL + UL XR** traffics in **low load**, compared with legacy schemes, + +- For power saving gain, LP-WUS can provide + - Results in [8A-3] [8A-11] show that power saving gain (average: 6.5%, range: 0%~12%), assuming MR enters **micro** sleep during LP-WUS monitoring; + - Results in [8A-11] show that power saving gain (average: 19%, range: 18%~20%), assuming MR enters **light** sleep during LP-WUS monitoring; + - the legacy schemes evaluated by companies included R17 PDCCH skipping, SSSG switching, R18 enhanced DRX, R15 short CDRX. +- For satisfied UE rate, LP-WUS can provide + - Results in [8A-3] [8A-11] show that the relative impact of satisfied UE rate (average: +0.25%, range: 0%~+1%), assuming MR enters **micro** sleep during LP-WUS monitoring; + - Results in [8A-11] show that the relative impact of satisfied UE rate (average: -3.5%, range: -6%~--1%), assuming MR enters **light** sleep during LP-WUS monitoring; + - the legacy schemes evaluated by companies included R17 PDCCH skipping, SSSG switching, R18 enhanced DRX, R15 short CDRX. + +For **DL + UL XR** traffics in **high load**, compared with legacy schemes, + +- For power saving gain, LP-WUS can provide + - Results in [8A-3] [8A-11] show that power saving gain (average: 5.5%, range: 0%~10%), assuming MR enters **micro** sleep during LP-WUS monitoring; + - Results in [8A-11] show that power saving gain (average: 16.5%, range: 16%~17%), assuming MR enters **light** sleep during LP-WUS monitoring; + - the legacy schemes evaluated by companies included R17 PDCCH skipping, SSSG switching, R18 enhanced DRX, R15 short CDRX. +- For satisfied UE rate, LP-WUS can provide + - Results in [8A-3] [8A-11] show that the relative impact of satisfied UE rate (average: -0.5%, range: -3%~+2%), assuming MR enters **micro** sleep during LP-WUS monitoring; + - Results in [8A-11] show that the relative impact of satisfied UE rate (average: -15.5%, range: -16%~--15%), assuming MR enters **light** sleep during LP-WUS monitoring; + - the legacy schemes evaluated by companies included R17 PDCCH skipping, SSSG switching, R18 enhanced DRX, R15 short CDRX. + +### 8.1.2.2 FTP 3 and IM traffic model + +In this clause, the usage of LP-WUS for FTP3 and IM traffic is studied. + +For the evaluated FTP3 traffic, packet size: 0.5Mbyte and average inter-arrival time: 200ms are assumed by companies, unless otherwise noted. + +For the evaluated IM traffic, packet size: 0.1 Mbyte and average inter-arrival time: 2seconds are assumed by companies, unless otherwise noted. + +The following schemes are compared, and the description of the schemes are as follows, + +- Always on + - i.e., no DRX , UE is always available for gNB scheduling +- C-DRX +- DCP + - R16 wake-up signal for RRC CONNECTED UE +- R17 PDCCH Scheme + - i.e., R17 PDCCH skipping and/or R17 SSSG switching +- LP-WUS scheme 1 + - LP-WUS to trigger the resumption of MR PDCCH monitoring from micro/light/deep sleep. + - Note: LP-WUS scheme1 does not require C-DRX configuration. +- LP-WUS scheme 2 + - LP-WUS to replace DCP, i.e. LP-WUS to trigger the start of the *drx\_onDurationTimer*. + - LP-WUS to replace DCP outside DRX active time, and LP-WUS to trigger the resumption of MR PDCCH monitoring during DRX active time (including *drx\_onDurationTimer* and *drx-inactivityTimer*). (evaluated by [8A-1]) + - Note: LP-WUS scheme 2 can only be used with C-DRX configuration. + +Note: MR based RRM measurements were not explicitly modelled for power saving evaluation. + +8.1.2.2.1 Collection of the results + +8.1.2.2.1.1 LP-WUS Scheme 1 + +![Bar chart titled 'Power saving gain (for LP-WUS scheme 1, WUR on power <=4unit, MR enter deep sleep)'. The chart shows power saving percentages for various FTP3 configurations compared to C-DRX and R17 PDCCH+CDRX. The y-axis ranges from 0% to 100%.](0efa7ad912af40ff136572a5e4b7634e_img.jpg) + +**Power saving gain (for LP-WUS scheme 1, WUR on power <=4unit, MR enter deep sleep)** + +| Comparison Category | Power Saving Gain | +|--------------------------------------------|-------------------| +| FTP3 Compared to C-DRX (160ms)+DCP | 68% | +| FTP3 Compared to C-DRX (40ms)+DCP | 24% | +| FTP3 Compared to C-DRX (320ms)+DCP | 46% | +| IM Compared to C-DRX (160ms) | 69% | +| FTP3 Compared to C-DRX (160ms) | 75% | +| FTP3 compared to R17 PDCCH+CDRX(160ms)+DCP | 86% | +| FTP3 compared to R17 PDCCH+CDRX(320ms)+DCP | 62% | +| IM compared to R17 PDCCH+CDRX(320ms)+DCP | 44% | +| IM compared to R17 PDCCH+CDRX(320ms)+DCP | 79% | + +Bar chart titled 'Power saving gain (for LP-WUS scheme 1, WUR on power <=4unit, MR enter deep sleep)'. The chart shows power saving percentages for various FTP3 configurations compared to C-DRX and R17 PDCCH+CDRX. The y-axis ranges from 0% to 100%. + +Figure 8.1.2.2-1a: (deep sleep) + +![Bar chart titled 'Power saving gain (for LP-WUS scheme 1, WUR on power <=4unit, MR enter light sleep)'. The chart shows power saving percentages for various FTP3 configurations compared to C-DRX and R17 PDCCH+CDRX. The y-axis ranges from -160% to 80%.](13ad8b2f9a6880472489e44a4740290f_img.jpg) + +**Power saving gain (for LP-WUS scheme 1, WUR on power <=4unit, MR enter light sleep)** + +| Comparison Category | Power Saving Gain | +|--------------------------------------------|-------------------| +| FTP3 Compared to C-DRX (160ms)+DCP | 28% | +| FTP3 Compared to C-DRX (40ms)+DCP | -3% | +| FTP3 Compared to C-DRX (160ms) | 29% | +| FTP3 compared to R17 PDCCH+CDRX(160ms)+DCP | 41% | +| FTP3 compared to R17 PDCCH+CDRX(320ms)+DCP | -11% | +| IM compared to R17 PDCCH+CDRX(320ms)+DCP | 18% | +| IM compared to R17 PDCCH+CDRX(320ms)+DCP | -150% | + +Bar chart titled 'Power saving gain (for LP-WUS scheme 1, WUR on power <=4unit, MR enter light sleep)'. The chart shows power saving percentages for various FTP3 configurations compared to C-DRX and R17 PDCCH+CDRX. The y-axis ranges from -160% to 80%. + +Figure 8.1.2.2-1b: (light sleep) + +![Bar chart titled 'Power saving gain (for LP-WUS scheme 1, WUR on power <= 4unit, MR enter micro sleep)'. The y-axis ranges from -480% to 160%. The x-axis shows various FTP3 traffic scenarios with different sleep configurations. The bars show gains of 40%, 53%, -30%, -74%, -25%, -26%, and -452%.](1049b682c4030f4146b73523cf5f1836_img.jpg) + +| Configuration | Power Saving Gain | +|----------------------------------------------------|-------------------| +| [8A-11] FTP3 Compared to always on | 40% | +| [8A-14] FTP3 Compared to always on | 53% | +| [8A-11] FTP3 Compared to CDRX (160ms) +DCP | -30% | +| [8A-11] FTP3 Compared to CDRX (40ms) +DCP | -74% | +| [8A-14] FTP3 Compared to CDRX (160ms) | -25% | +| [8A-15] FTP3 compared to R17 PDCCH+CDRX(160ms)+DCP | -26% | +| [8A-15] FTP3 compared to R17 PDCCH+CDRX(320ms)+DCP | -452% | + +Bar chart titled 'Power saving gain (for LP-WUS scheme 1, WUR on power <= 4unit, MR enter micro sleep)'. The y-axis ranges from -480% to 160%. The x-axis shows various FTP3 traffic scenarios with different sleep configurations. The bars show gains of 40%, 53%, -30%, -74%, -25%, -26%, and -452%. + +Figure 8.1.2.2-1c: (micro sleep) + +- Note: [8A-7] assume duty cycled LP-WUS monitoring with 40 or 80ms duty cycle. And the others assume continuous LP-WUS monitoring. +- Note: [8A-14] assumes the packet size of FTP3 traffic is 0.1Mbyte. +- Note: The values shown in the figure are average gain. + +![Bar chart titled 'Power saving gain (for LP-WUS scheme 1, WUR ON power >= 10units)'. The y-axis ranges from -200.00% to 100.00%. The x-axis shows various FTP3 traffic scenarios with different sleep configurations. The bars show gains of 23%, -114%, -33%, 24%, 56%, 12%, 58%, -40%, and 33%.](2ef0ed2df58828f36a728bc60148d841_img.jpg) + +| Configuration | Power Saving Gain | +|----------------------------------------------------------------|-------------------| +| [8A-7] deep sleep FTP3 Compared to CDRX (160ms) +DCP | 23% | +| [8A-11] micro sleep FTP3 Compared to CDRX (40ms) +DCP | -114% | +| [8A-11] light sleep FTP3 Compared to CDRX (40ms) +DCP | -33% | +| [8A-11] deep sleep FTP3 Compared to CDRX (40ms) +DCP | 24% | +| [8A-7] deep sleep IM Compared to CDRX (320ms) +DCP | 56% | +| [8A-13] light sleep FTP3 Compared to CDRX (160ms) | 12% | +| [8A-13] deep sleep FTP3 Compared to CDRX (160ms) | 58% | +| [8A-13] light sleep FTP3 compared to R17 PDCCH+CDRX(160ms)+DCP | -40% | +| [8A-13] deep sleep FTP3 compared to R17 PDCCH+CDRX(160ms)+DCP | 33% | + +Bar chart titled 'Power saving gain (for LP-WUS scheme 1, WUR ON power >= 10units)'. The y-axis ranges from -200.00% to 100.00%. The x-axis shows various FTP3 traffic scenarios with different sleep configurations. The bars show gains of 23%, -114%, -33%, 24%, 56%, 12%, 58%, -40%, and 33%. + +Figure 8.1.2.2-2 + +- Note: [8A-7] assume duty cycled LP-WUS monitoring with 40 or 80ms duty cycle. And the others assume continuous LP-WUS monitoring. +- Note: The values shown in the figure are average gain + +![Bar chart titled 'UPT gain (for LP-WUS scheme1, MR enter deep sleep)'. It compares Min, Mean, and Max UPT gain across six scenarios. The y-axis ranges from -100% to 700%.](ed2c3e8ce1a7479b617b38a843c6b782_img.jpg) + +**UPT gain (for LP-WUS scheme1, MR enter deep sleep)** + +| Scenario | Min:UPT gain | Mean:UPT gain | Max:UPT gain | +|--------------------------------------------|--------------|---------------|--------------| +| FTP3 Compared to CDRX (160ms)+DCP | -4% | 4% | 4% | +| FTP3 Compared to CDRX (40ms)+DCP | 13% | 55% | 194% | +| IM Compared to CDRX (320ms)+DCP | 15% | 82% | 774% | +| FTP3 Compared to C-DRX (160ms) | -26% | 36% | 26% | +| FTP2 compared to R17 PDCCH+CDRX(160ms)+DCP | 1% | 1% | 1% | +| IM compared to R17 PDCCH+CDRX(320ms)+DCP | -9% | 9% | 94% | + +Bar chart titled 'UPT gain (for LP-WUS scheme1, MR enter deep sleep)'. It compares Min, Mean, and Max UPT gain across six scenarios. The y-axis ranges from -100% to 700%. + +Figure 8.1.2.2-3a: (deep sleep) + +![Bar chart titled 'UPT gain (for LP-WUS scheme1, MR enter light sleep)'. It shows UPT gain for five scenarios, all represented by blue bars. The y-axis ranges from 0% to 800%.](7cf394a7ad158bf3aa4f8d58e7d4ebc5_img.jpg) + +**UPT gain (for LP-WUS scheme1, MR enter light sleep)** + +| Scenario | UPT gain | +|--------------------------------------------|----------| +| FTP3 Compared to CDRX (160ms)+DCP | 65% | +| FTP3 Compared to CDRX (40ms)+DCP | 87% | +| FTP3 Compared to C-DRX (160ms) | 36% | +| FTP3 compared to R17 PDCCH+CDRX(160ms)+DCP | 86% | +| IM compared to R17 PDCCH+CDRX(320ms)+DCP | 453% | + +Bar chart titled 'UPT gain (for LP-WUS scheme1, MR enter light sleep)'. It shows UPT gain for five scenarios, all represented by blue bars. The y-axis ranges from 0% to 800%. + +Figure 8.1.2.2-3b: (light sleep) + +![Bar chart titled 'UPT gain (for LP-WUS scheme 1, MR enter micro sleep)'. The y-axis shows percentages from 0% to 500%. The x-axis shows six categories with their respective UPT gain values: FTP3 always on (124%), FTP3 LP-WUS scheme 1 (124%), FTP3 always on (180%), FTP3 LP-WUS scheme 1 (180%), FTP3 LP-WUS scheme 1 (128%), and IM (2260%).](19d41b4b2af3e9bd470c86b6067a822e_img.jpg) + +| Comparison Category | UPT Gain (%) | +|------------------------------------------------------------|--------------| +| FTP3 always on Compared to CDRX (160ms)+DCP | 124% | +| FTP3 LP-WUS scheme 1 Compared to CDRX (160ms)+DCP | 124% | +| FTP3 always on Compared to CDRX (40ms)+DCP | 180% | +| FTP3 LP-WUS scheme 1 Compared to CDRX (40ms)+DCP | 180% | +| FTP3 LP-WUS scheme 1 compared to R17 PDCCH+CDRX(160ms)+DCP | 128% | +| IM LP-WUS scheme 1 compared to R17 PDCCH+CDRX(320ms)+DCP | 2260% | + +Bar chart titled 'UPT gain (for LP-WUS scheme 1, MR enter micro sleep)'. The y-axis shows percentages from 0% to 500%. The x-axis shows six categories with their respective UPT gain values: FTP3 always on (124%), FTP3 LP-WUS scheme 1 (124%), FTP3 always on (180%), FTP3 LP-WUS scheme 1 (180%), FTP3 LP-WUS scheme 1 (128%), and IM (2260%). + +Figure 8.1.2.2-3c: (micro sleep) + +8.1.2.2.1.2 LP-WUS Scheme 2 + +For LP-WUS used as to replace DCP, the power saving and UPT impact are summarized in figure 8.1.2.2-4 and 8.1.2.2.5, respectively. + +![Bar chart titled 'Power saving gain (for LP-WUS scheme 2, FTP3 traffic)'. The y-axis shows percentages from 0% to 160%. The x-axis shows six categories with Min, Mean, and Max power saving gain values. The legend indicates: Min: Power saving gain [%] (blue), Mean: Power saving gain [%] (orange), Max: Power saving gain [%] (grey).](d6e773bd03b27399c513d3958f1c87d6_img.jpg) + +| Comparison Category | Min [%] | Mean [%] | Max [%] | +|--------------------------------------|---------|----------|---------| +| [8A-11] Compared to CDRX (160ms)+DCP | 6% | 7% | 8% | +| [8A-2] Compared to CDRX (160ms)+DCP | 11% | 47% | 88% | +| [8A-8] Compared to CDRX (160ms)+DCP | 11% | 11% | 11% | +| [8A-15] Compared to CDRX (160ms)+DCP | 1% | 2% | 3% | +| [8A-11] Compared to CDRX (40ms)+DCP | 19% | 30% | 47% | +| [8A-15] Compared to CDRX (40ms)+DCP | 18% | 24% | 31% | +| [8A-2] Compared to CDRX (320ms)+DCP | 11% | 41% | 78% | +| [8A-8] Compared to CDRX (320ms)+DCP | 9% | 9% | 9% | +| [8A-2] Compared to CDRX (640ms)+DCP | 10% | 34% | 63% | + +Bar chart titled 'Power saving gain (for LP-WUS scheme 2, FTP3 traffic)'. The y-axis shows percentages from 0% to 160%. The x-axis shows six categories with Min, Mean, and Max power saving gain values. The legend indicates: Min: Power saving gain [%] (blue), Mean: Power saving gain [%] (orange), Max: Power saving gain [%] (grey). + +Figure 8.1.2.2-4 + +![Bar chart titled 'UPT gain (for LP-WUS scheme2 )' showing Min, Mean, and Max UPT gain for various configurations. The y-axis ranges from -60% to 40%.](e94343421418a4f626e885ec73be542d_img.jpg) + +**UPT gain (for LP-WUS scheme2 )** + +Legend: ■ Min:UPT gain ■ Mean:UPT gain ■ Max:UPT gain + +| Configuration | Min:UPT gain | Mean:UPT gain | Max:UPT gain | +|----------------------------------------------------------|--------------|---------------|--------------| +| [8A-11] [8A-2] FTP3 [8A-15] Compared to CDRX (160ms)+DCP | -6% | 5% | 3% | +| [8A-2] FTP3 | 0% | 0% | 0% | +| [8A-15] | 0% | 0% | 0% | +| [8A-11] [8A-15] FTP3 Compared to CDRX (40ms) +DCP | -22% | 11% | -2% | +| [8A-2] FTP3 | 0% | 0% | 0% | +| [8A-15] | 0% | 0% | 0% | +| [8A-2] FTP3 Compared to CDRX (320ms) +DCP | 0% | 0% | 0% | +| [8A-2] FTP3 Compared to CDRX (640ms) +DCP | 0% | 0% | 0% | + +Bar chart titled 'UPT gain (for LP-WUS scheme2 )' showing Min, Mean, and Max UPT gain for various configurations. The y-axis ranges from -60% to 40%. + +Figure 8.1.2.2-5 + +Note: + +- [8A-2] , [8A-8] , [8A-11] assume LP-WUS is used to replace DCP and LP-WUR ON power value no more than 1 unit, +- [8A-15] assumes LP-WUS is used to replace DCP and LP-WUR ON power value is 0.1/4/10units. +- 200ms/400ms/800ms/1.6s/5s/10s average interval times for FTP3 traffic are evaluated by [8A-2]. +- The assumed ramp up time of MR from deep/light sleep is 10ms/3ms + +In [8A-1]'s evaluation, in addition to DCP replacement, LP-WUS is also used to trigger the resumption of MR PDCCH during DRX active time(including drx\_onDurationTimer and drx-inactivityTimer) and LP-WUR ON power value is 1/4/10 unit. The results are shown in Figures 8.1.2.2-6 and 8.1.2.2-7. + +![Bar chart titled 'Power saving gain (for LP-WUS scheme 2, FTP3 traffic)' showing power saving gain for deep, light, and micro sleep states.](1412b8b99f2a03e5f16e3a6d3bc4f946_img.jpg) + +**Power saving gain (for LP-WUS scheme 2, FTP3 traffic)** + +| Sleep State | Power saving gain | +|-----------------------------------------------------------|-------------------| +| deep sleep | 50% | +| light sleep [8A-11] compared to R17 PDCCH+CDRX(160ms)+DCP | 29% | +| micro sleep | 8% | + +Bar chart titled 'Power saving gain (for LP-WUS scheme 2, FTP3 traffic)' showing power saving gain for deep, light, and micro sleep states. + +Figure 8.1.2.2-6 + +![Bar chart showing UPT gain for LP-WUS scheme2 across three sleep states: deep sleep (-35%), light sleep [8A-1] FTP3 (-15%), and micro sleep (34%). The baseline is R17 PDCCH+CDRX(160ms)+DCP.](8e6f0b87d128da8e5d79d274d0c14ed5_img.jpg) + +**UPT gain (for LP-WUS scheme2 )** + +| Sleep State | UPT Gain (%) | +|-------------------------|--------------| +| deep sleep | -35% | +| light sleep [8A-1] FTP3 | -15% | +| micro sleep | 34% | + +compared to R17 PDCCH+CDRX(160ms)+DCP + +Bar chart showing UPT gain for LP-WUS scheme2 across three sleep states: deep sleep (-35%), light sleep [8A-1] FTP3 (-15%), and micro sleep (34%). The baseline is R17 PDCCH+CDRX(160ms)+DCP. + +**Figure 8.1.2.2-7** + +Note: [8A-1] assumes the ramp up time of MR from deep/light sleep is 20ms/6ms + +#### 8.1.2.2.2 Observations + +Note: the average value, the min and max value in the range is calculated across all companies' results + +**For the usage of LP-WUS is to trigger the resumption of PDCCH monitoring (i.e., LP-WUS scheme1),** + +- For FTP3 traffic, when WUR ON power setting is **NO more than 4units**, + - LP-WUS compared with **CDRX or CDRX+DCP** provide + - Results in [8A-11] [8A-7] [8A-13] [8A-14] show that power saving gain 24%~86% (average: 61.3%) when MR is allowed to enter in **deep-sleep** state during LP-WUS monitoring + - Results in [8A-11] [8A-13] [8A-14] show that power saving gain -3%~41% (average: 23.75%) when MR is allowed to enter in **light-sleep** state during LP-WUS monitoring + - Results in [8A-11] [8A-14] show that power saving gain -74%~25% (average: -36%) when MR is allowed to enter in **micro-sleep** state during LP-WUS monitoring + - LP-WUS compared with **R17 PDCCH + CDRX+ DCP** provide + - Results in [8A-5] [8A-13] show that power saving gain 44%~62% (average: 53%) when MR is allowed to enter in **deep-sleep** state during LP-WUS monitoring + - Results in [8A-5] [8A-13] show that power saving gain -11%~18% (average: 3.5%) when MR is allowed to enter in **light-sleep** state during LP-WUS monitoring + +- Results in [8A-5] shows that power saving gain -26% when MR is allowed to enter in **micro-sleep** state during LP-WUS monitoring +- LP-WUS compared with **always on** provide + - Results in [8A-11] shows that power saving gain 40%~53% (average: 46.5%) when MR is allowed to enter in **micro-sleep** state during LP-WUS monitoring +- For FTP3 traffic, when WUR ON power setting is equal to **10 units**, + - LP-WUS compared with **CDRX or CDRX+ DCP** provide + - Results in [8A-7] [8A-11] [8A-13] show that power saving gain 24%~58% (average: 40.25) when MR is allowed to enter in **deep-sleep** state during LP-WUS monitoring + - Results in [8A-11] [8A-13] show that power saving gain -33%~12% (average: -10.5%) when MR is allowed to enter in **light-sleep** state during LP-WUS monitoring + - Results in [8A-11] shows that power saving gain -114% when MR is allowed to enter in **micro-sleep** state during LP-WUS monitoring + - LP-WUS compared with **R17 PDCCH + CDRX+ DCP** provide + - Results in [8A-13] shows that power saving gain 33% when MR is allowed to enter in **deep-sleep** state during LP-WUS monitoring + - Results in [8A-13] shows that power saving gain -40% when MR is allowed to enter in **light-sleep** state during LP-WUS monitoring +- For IM traffic, when WUR ON power setting is **NO more than 4 units**, + - LP-WUS compared with **CDRX or CDRX+DCP** provide + - Results in [8A-7] shows that power saving gain 69% when MR is allowed to enter in **deep-sleep** state during LP-WUS monitoring + - LP-WUS compared with **R17 PDCCH + CDRX+ DCP** provide + - Results in [8A-5] shows that power saving gain 79% when MR is allowed to enter in **deep-sleep** state during LP-WUS monitoring + - Results in [8A-5] shows that power saving gain -150% when MR is allowed to enter in **light-sleep** state during LP-WUS monitoring + - Results in [8A-5] shows that power saving gain -425% when MR is allowed to enter in **micro-sleep** state during LP-WUS monitoring +- For IM traffic, when WUR ON power setting is **equal to 10 units**, + - LP-WUS compared with **CDRX+ DCP** provide + - Results in [8A-7] shows that power saving gain 56% when MR is allowed to enter in **deep-sleep** state during LP-WUS monitoring +- For FTP3 traffic, + - LP-WUS compared with **CDRX or CDRX+DCP** provide + +- Results in [8A-11] [8A-7] [8A-13] show that UPT gain -26%~194% (average: 10.75%) when MR is allowed to enter in **deep-sleep** state during LP-WUS monitoring +- Results in [8A-11] [8A-13] show that UPT gain 36%~87% (average: 62.7%) when MR is allowed to enter in **light-sleep** state during LP-WUS monitoring +- Results in [8A-11] shows that UPT gain 124%~180% (average: 152%) when MR is allowed to enter in **micro-sleep** state during LP-WUS monitoring +- LP-WUS compared with **R17 PDCCH + CDRX+ DCP** provide + - Results in [8A-5] [8A-13] show that UPT gain -9%~1% (average: -4%) when MR is allowed to enter in **deep-sleep** state during LP-WUS monitoring + - Results in [8A-5] [8A-13] show that UPT gain 59%~86% (average: 72.5%) when MR is allowed to enter in **light-sleep** state during LP-WUS monitoring + - Results in [8A-5] shows that UPT gain 128% when MR is allowed to enter in **micro-sleep** state during LP-WUS monitoring +- LP-WUS compared with **always-on** provides + - Results in [8A-11] shows that the same UPT performance as always-on when MR is allowed to enter in **micro-sleep** state during LP-WUS monitoring +- For IM traffic, + - LP-WUS compared with **CDRX+ DCP** provide + - Results in [8A-7] show that UPT gain 44%~774% (average: 184%) when MR is allowed to enter in **deep-sleep** state during LP-WUS monitoring + - LP-WUS compared with **R17 PDCCH + CDRX+ DCP** provide + - Results in [8A-5] show that UPT gain 94% when MR is allowed to enter in **deep-sleep** state during LP-WUS monitoring + - Results in [8A-5] show that UPT gain 453% when MR is allowed to enter in **light-sleep** state during LP-WUS monitoring + - Results in [8A-5] show that UPT gain 2260% when MR is allowed to enter in **micro-sleep** state during LP-WUS monitoring + +**For the usage of LP-WUS to replace DCP (i.e., LP-WUS scheme2) for FTP3 traffic,** + +- The scheme of LP-WUS for DCP replacement compared with **CDRX+DCP** provide (LP-WUR ON power no more than 1 unit) + - Results in [8A-2] [8A-8] [8A-11] [8A-15] show that power saving gain (1%~88%, average: 16.75%) when CDRX cycle length is 160ms; + - Results in [8A-11] [8A-15] show that power saving gain (18%~47%, average: 27%) when CDRX cycle length is 40ms; + - Results in [8A-2] [8A-8] show that power saving gain (9%~78%, average: 25%) when CDRX cycle length is 320ms; + - Results in [8A-2] show that power saving gain (10%~63%, average: 34%) when CDRX cycle length is 640ms; + +- The scheme of LP-WUS to replace DCP outside DRX active time and to trigger the resumption of MR PDCCH monitoring during DRX active time (*including drx\_onDurationTimer and drx-inactivityTimer*) compared with **R17 PDCCH+CDRX+DCP** provide +- Results in [8A-1] show that power saving gain (8%, 29%, 50%) for the case MR enters (micro sleep, light sleep, deep sleep) during LP-WUS monitoring, respectively; +- The scheme of LP-WUS for DCP replacement compared with **CDRX+DCP** provide +- Results in [8A-2] [8A-11] [8A-15] show that UPT gain (-6%~0%, average: -1.7%) when CDRX cycle length is 160ms; +- Results in [8A-11] [8A-15] show that UPT gain (-22%~0%, average: -5.5%) when CDRX cycle length is 40ms; +- Results in [8A-2] show that the same UPT performance when CDRX cycle length is 320ms; +- Results in [8A-2] show that the same UPT performance when CDRX cycle length is 640ms; +- The scheme of LP-WUS to replace DCP outside DRX active time and to trigger the resumption of MR PDCCH monitoring during DRX active time (*including drx\_onDurationTimer and drx-inactivityTimer*) compared with **R17 PDCCH+CDRX+DCP** provide +- Results in [8A-1] show that UPT gain (34%, -15%, -35%) for the case MR enters (micro sleep, light sleep, deep sleep) during LP-WUS monitoring, respectively; + +## 8.2 Coverage + +### 8.2.1 Comparison between LP-WUS and NR reference channel + +#### 8.2.1.1 Summary of the performance gap between LP-WUS and NR reference channel + +The results are summarized in clause 8.2.2 and clause 8.2.3. A subset of the results are selected to draw observations for comparison between coverage of LP-WUS and reference NR channel. The selection and comparison are performed based on following criterion. + +- The relative difference for MIL gap between LP-WUS and NR channel is calculated per each company. +- If companies only report MIL of NR reference channel or only MIL of LP-WUS, no performance gap can be derived from input from this company. +- If company only input Msg3 results, and PDCCH results is not provided, only performance gap between LP-WUS and MSG3 can be derived from this company. +- To find whether LP-WUS can achieve similar to or better then MIL of reference NR channels per each companies' results and then observe the amount of resources required per bit in LP-WUS required for LP-WUS, the following is considered, +- MIL margin of LP-WUS is defined as $Y = (\text{MIL of LP-WUS} - \text{MIL of NR channel})$ , and when $Y \geq -1\text{dB}$ , the LP-WUS sample is considered to have similar to or better than reference NR channels. + +- If there are multiple samples fulfil above condition from one company, only the sample with minimum resource per bit is kept to draw conclusion. +- The resource required per bit is provided in terms of X MHz\*Symbol/bit. For example, if X= 8.64 and WUS BW is 4.32MHz, it means 2 OFDM symbols are required for LP-WUS to achieve MIL similar to or better than that of NR channel. +- If no samples can fulfil the above condition (i.e. Y<-1dB), observation is drawn based on the range of X and Y value across companies. + - If multiple results were provided by one company, the result with minimum abs(Y) value is selected + +The summary of the observation is provided in the following **Table 8.2 -1**. In each case, only the samples fulfil above condition are collected, where company A: [X (MHz\*Symbol/bit), Y (dB)] means company A results show LP-WUS configuration with X MHz\*Symbol/bit can achieve MIL similar to or better than MIL of reference channel, and the MIL of LP-WUS – MIL of ref channel is Y dB. + +**Table 8.2.1-1: Summary of the performance gap between LP-WUS and NR reference channel** + +| Company: [X (MHz*Symbol/bit), Y (dB)] | | | OOK | | FSK | | OFDM | | +|---------------------------------------|------------------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| | | | Results | Observation | Results | Observation | Results | Observation | +| Urban | Normal UE | AL16,4Rx | - | 8.2.2.1 | - | 8.2.2.5 | - | 8.2.2.9 | +| | | AL8,4Rx | [8A-13]: [46.08, -0.4] | 8.2.2.1
- X = 46.08, Y = -0.4, reported by 1 source. | - | | [8A-13]: [34.56, 2.59]
[8A-8]: [0.31, 2.08] | 8.2.2.9
- X = 34.56, Y = 2.59, reported by 1 source.
- X = 0.31, Y = 2.08, reported by 1 source. | +| | | AL16,2Rx | - | | - | | [8A-3]: [2.16, -0.71]
[8A-8]: [0.31, 2.18] | 8.2.2.9
- X = 2.16, Y = -0.71, reported by 1 source.
- X = 0.31, Y = 2.18, reported by 1 source. | +| | | AL8,2Rx | [8A-3]: [604.8, 0.91]
[8A-11]: [28.8, -0.53] | 8.2.2.1
- X = 28.8, Y = -0.53, reported by 1 source.
- X = 604.8, Y = 0.91, reported by 1 source. | - | 8.2.2.5 | [8A-3]: [2.16, 1.79]
[8A-8]: [0.31, 5.38]
[8A-11]: [18, 0.02] | 8.2.2.9
- X = 0.31~2.16, Y = 1.79~5.38, reported by 1 source.
- X = 18, Y = 0.02, reported by 1 source. | +| | | Msg3 | [8A-3]: [241.92, -0.96] (Msg3 with 4dB HARQ gain)
[8A-5]: [8.64, -0.93]
[8A-7]: [17.28, 0.06]
[8A-8]: [3.24, 3.23]
[8A-11]: [1.8, 2.2]
[8A-13]: [2.88, 0.78] | 8.2.2.3
- X = 1.8~8.64, Y = -0.93~11.97, reported by 6 source, no power boosting for LP-WUS;
- X = 17.28, Y = 0.06, reported by 1 | [8A-2]: [4.32, -0.31]
[8A-5]: [4.32, -0.42]
[8A-7]: [25.92, -0.34] | 8.2.2.7
- X=4.32, Y=-0.31, reported by 1 source.
- X= 4.32, Y=-0.42 reported by 1 source.
- X= 25.92, Y=-0.34, reported by one | [8A-3]: [2.16, 2.82] (Msg3 with 4dB HARQ gain)
[8A-5]: [1.8, 0.06]
[8A-7]: [1.08, -0.24]
[8A-8]: [0.31, 18.03]
[8A-11]: [3.6, 4.84]
[8A-13]: [4.32, 5.82]
[8A-11](2): [3.6, | 8.2.2.11
- X= 0.31~4.32, Y=0.06~16.01 reported by 4 sources.
- X= 1.08, Y=-0.24, reported by one source, assumes antenna element | + +| | | | | | | | | | +|------------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| | | | [8A-2]: [8.64, 1.79]
[8A-6]: [8.64, 11.97]
[8A-11](2): [4.32, -0.99] (assumes BS array gain correction for LP-WUS 4dB more than Msg3)

[8A-11]: [0.9, 0.68] (p=3dB)
[8A-14]: [3.24, 1.24] (p=3dB)
[8A-2]: [4.32, -0.61] (p=3dB) | sources, assumes antenna element gain of LP-WUR is 3dB worse than MR.
- X = 241.92, Y = -0.96, reported by 1 sources, assuming 4dB HARQ gain from 2 retransmissions for Msg3 PUSCH and no power boost for LP-WUS.
- X=0.9~4.32, Y=-0.61~1.24, reported by 3 sources, assuming 3dB power boosting for LP-WUS. | | source, assumes antenna element gain of LP-WUR is 3dB worse than MR. | 0.84] (assumes BS array gain correction for LP-WUS 4dB more than Msg3) | gain of LP-WUR is 3dB worse than MR.
- X=2.16, Y=2.82, reported by 1 source, assuming 4dB HARQ gain from 2 retransmissions for Msg3 PUSCH. | +| Redcap UE | AL16,2Rx | - | | | - | | - | | +| | AL8, 2Rx | - | | | - | | - | | +| | AL16,1Rx | [8A-3]: [302.4, -0.79]
[8A-16]: [23.04, 0.47]
[8A-2]: [4.32, -0.38] | 8.2.2.2
- X=4.32, Y=-0.31, reported by 1 source.
- X = 23.04, Y = 0.47, reported by 1 source.
- X = 302.4, Y = -0.79, reported by 1 source. | [8A-2]: [4.32, 2.92] | 8.2.2.6
- X=4.32, Y=2.92, reported by 1 source. | [8A-3]: [2.16, 2.92]
[8A-11]: [7.2, -0.48]
[8A-8]: [0.43, 1.2] | 8.2.2.10
X=0.43~2.16, Y=1.2~2.92, reported by 2 sources
X=7.2, Y=-0.48, reported by 1 source. | | +| | AL8, 1Rx | [8A-3]: [120.96, -0.89]
[8A-7]: [60.48, -0.92]
[8A-8]: [12.96, -0.02]
[8A-11]: [7.2, -0.7]
[8A-13]: [5.76, 0.12]
[8A-2]: [4.32, 1.32] | 8.2.2.2
- X=4.32~12.96, Y=-0.02~1.32, reported by 4 sources.
- X=60.48~120.96, Y=-0.89~-0.92, reported by 2 sources. | [8A-2]: [4.32, -0.12]
[8A-7]: [51.84, 0.18] | 8.2.2.6
- X=4.32, Y=-0.12, reported by 1 source.
- X= 51.84, Y=0.18, reported by 1 source. | [8A-3]: [2.16, 4.99]
[8A-7]: [2.16, 0.48]
[8A-8]: [0.31, 9.28]
[8A-11]: [3.6, -0.33]
[8A-13]: [4.32, 0.97] | 8.2.2.10
- X= 0.31~4.32, Y=-0.33~9.28, reported by 5 sources. | | +| | Msg3 | [8A-3]: [241.92, -0.96] (Msg3 with 4dB HARQ gain)
[8A-7]: [17.28, 0.06]
[8A-16]: [2.88, 0.16]
[8A-8]: [3.24, 1.72]
[8A-11]: [1.8, 2.2]
[8A-13]: [2.88, 0.78]
[8A-2]: [8.64, 1.79]
[8A-5]: [8.64, -0.93]

[8A-11](2): [2.52, -0.96] | 8.2.2.4
- X=1.8~8.64, Y=-0.93~2.2, reported by 6 sources, no power boosting for LP-WUS.
- X=17.28, Y=0.06, reported by 1 sources, no power boosting for LP-WUS, assumes antenna element gain of LP-WUR is 3dB worse than MR. | [8A-2]: [4.32, -0.31]
[8A-7]: [25.92, 0.04]
[8A-5]: [4.32, -0.43] | 8.2.2.8
- X=4.32, Y=-0.43~-0.31, reported by 2 sources.
- X=25.92, Y=0.04, reported by 1 source, assumes antenna element gain of LP-WUR is 3dB worse than MR. | [8A-3]: [2.16, 2.82] (Msg3 with 4dB HARQ gain)
[8A-7]: [1.08, -0.24]
[8A-8]: [0.31, 18.03]
[8A-11]: [3.6, 6.84]
[8A-13]: [4.32, 5.82]
[8A-5]: [1.8, 0.06]

[8A-11](2): [3.6, 2.84] (assumes BS array gain correction | 8.2.2.12
- X= 0.31~4.32, Y=~18.03, reported by 4 sources.
- X= 1.08, Y=-0.24, reported by 1 source, assumes antenna element gain of LP-WUR is 3dB worse than MR.
- X=2.16, Y=2.82, reported by 1 | | + +| | | | | | | | | | | +|-------|------------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|-----------------------------------------------------------|--|---------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------| +| | | | 2.24] (assumes BS array gain correction for LP-WUS 4dB more than Msg3)

[8A-2]: [4.32, -0.61] (p=3dB)
[8A-11]: [0.9, 0.68] (p=3dB)
[8A-14]: [3.24, 1.24] (p=3dB)
[8A-11](2): [1.68, 2.24] (p=3dB) (assumes BS array gain correction for LP-WUS 4dB more than Msg3) | antenna element gain of LP-WUR is 3dB worse than MR.
- X=241.92, Y=-0.96, reported by 1 source, assuming 4dB HARQ gain from 2 retransmissions for Msg3 PUSCH.
- X=0.9~4.32, Y=-0.61~1.24, reported by 3 sources, assuming 3dB power boosting for LP-WUS. | | | | for LP-WUS 4dB more than Msg3) | source, assuming 4dB HARQ gain from 2 retransmissions for Msg3 PUSCH. | +| Rural | Normal UE | AL16,4Rx | - | | - | | | - | | +| | | AL8,4Rx | - | | - | | | - | | +| | | AL16,2Rx | [8A-11]: [69.12, -0.96] | 8.2.3.1
- X =69.12, Y =-0.96, reported by 1 source. | - | | | - | 8.2.3.9 | +| | | AL8,2Rx | [8A-11]: [28.8, 0.09]
[8A-13]: [46.08, -0.25] | 8.2.3.1
- X =28.8 ~ 46.08, Y =-0.25 ~ 0.09, reported by 2 sources. | - | | | [8A-11]: [7.2, -0.29]
[8A-13]: [34.56, -0.18] | 8.2.3.9
- X =34.56, Y =-0.18, reported by 1 source.
- X =7.2, Y =-0.29, reported by 1 source. | +| | | Msg3 | [8A-11]: [1.8, 1.07]
[8A-13]: [2.88, 4.71]
[8A-6]: [4.32, 11.57]
[8A-5]: [8.64, -0.37]
[8A-3]: [120.96, 1.56] (Msg3 with 4dB HARQ gain)

[8A-11]: [0.9, -0.49] (p=3dB)
[8A-14]: [3.02, -0.04] (p=3dB) | 8.2.3.3
- X =1.8 ~ 8.64, Y =-0.37 ~ 11.57, reported by 4 sources, no power boosting for LP-WUS.
- X =0.9 ~ 3.02, Y =-0.49~-0.04, reported by 2 sources, 3dB power boosting for LP-WUS.
- X= 120.96, Y= 1.56, reported by 1 source, assuming 4dB HARQ gain from 2 retransmissions for Msg3 PUSCH. | [8A-5]: [4.32, 0.13] | 8.2.3.7
- X =4.32, Y=0.13, reported by 1 source | | [8A-11]: [3.6, 3.8]
[8A-13]: [2.16, 4.36]
[8A-5]: [1.8, 0.62] | 8.2.3.11
- X =1.8 ~ 3.6, Y =0.62 to 4.36, reported by 3 sources. | +| | Redc ap UE | AL16,2Rx | - | | - | | | - | | +| | | AL8, 2Rx | - | | - | | | - | | +| | | AL16,1Rx | [8A-16]: [46.08, -0.25] | 8.2.3.2 | - | | | [8A-11]: [7.2, -0.28] | 8.2.3.10 | + +| | | | | | | | | | +|--|--|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|---------------------------------------------------------------|---------------------------------------------------------------------|-------------------------------------------------------------------------------| +| | | | 1.92] | - X =46.08, Y =1.92,
reported by 1 source | | | | - X =7.2, Y =-0.28,
reported by 1 source. | +| | | AL8, 1Rx | [8A-11]: [3.78, -0.32]
[8A-13]: [11.52, -0.62] | 8.2.3.2
- X =3.78 ~ 11.52, Y =-0.62 ~ -0.32,
reported by 2 source. | - | | [8A-11]: [3.6, -0.21]
[8A-13]: [17.28, 3.7] | 8.2.3.10
- X =3.6 ~ 17.28, Y =-0.21 ~ 3.7,
reported by 2 source. | +| | | Msg3 | [8A-16]: [0.18, 0.65]
[8A-11]: [1.8, 1.07]
[8A-13]: [2.88, 4.71]
[8A-5]: [8.64, -0.37]
[8A-3]: [120.96, 1.56] (Msg3 with 4dB HARQ gain)

[8A-11]: [0.9, -0.49] (p=3dB)
[8A-14]: [3.02, -0.04] (p=3dB) | 8.2.3.4
- X =0.18 ~ 8.64, Y =-0.37 ~ 4.71,
reported by 4 sources, no power boosting for LP-WUS.
- X =0.9 ~ 3.02, Y =-0.49 ~ -0.04, 3dB power boosting for LP-WUS reported by 2 sources.
- X = 120.96, Y = 1.56, reported by 1 source, assuming 4dB HARQ gain from 2 retransmissions for Msg3 PUSCH. | [8A-5]: [4.32, 0.13] | 8.2.3.8
- X =4.32, Y =0.13,
reported by 1 source | [8A-11]: [3.6, 3.8]
[8A-13]: [2.16, 4.36]
[8A-5]: [1.8, 0.62] | 8.2.3.12
- X =1.8 ~ 3.6, Y =0.62 ~ 4.36,
reported by 3 sources. | + +### 8.2.1.2 NR Coverage for comparison + +The NR coverage for comparison are provided in the following tables + +**Table 8.2.1-2: NR Coverage, Urban, Normal UE** + +| | Source | Scenarios | AL16, 4Rx | AL8, 4Rx | AL16, 2Rx | AL8, 2Rx | AL16, 1RX | AL8, 1RX | PUSCH eMBB | PUSCH Msg3 | +|-----------|---------|--------------|-----------|----------|-----------|----------|-----------|----------|------------|--------------------------------------| +| Normal UE | [8A-11] | Urban 2.6GHz | | | 154.94 | 152.33 | | | 138.28 | [8A-11]:141.85
[8A-11] (2):145.85 | +| | [8A-15] | Urban 2.6GHz | 166.27 | 164.28 | 162.86 | 160.74 | | | 137.62 | 147.20 | +| | [8A-14] | Urban 4GHz | | | 162.65 | 159.84 | | | 130.69 | 146.77 | +| | [8A-5] | Urban 2.6GHz | | | | | | | | 149.61 | +| | [8A-9] | Urban 2.6GHz | | | | 163.54 | | | 135.88 | | +| | [8A-2] | Urban 2.6GHz | 158.80 | | | | | | | 147.83 | +| | [8A-3] | Urban 2.6GHz | 159.96 | 157.26 | 156.76 | 154.26 | | | | 153.23 | +| | [8A-8] | Urban 4GHz | 168.30 | 162.21 | 162.11 | 158.91 | | | | 146.26 | +| | [8A-6] | Urban 2.6GHz | | | 165.55 | | | | | 135.46 | +| | [8A-13] | Urban 2.6GHz | | 162.54 | | | | | | 151.53 | +| | [8A-7] | Urban 2.6GHz | 160.81 | 158.31 | | | | | 142.51 | 148.73 | + +Note: "[8A-11](2)" assumes UL 4dB correction factor better than DL, "[8A-11]" assumes UL and DL same correction factor in coverage evaluation template. For the figures in clause 8.2.2 and 8.2.3, the meanings of '[8A-11]' and '[8A-11] 2' refer to this. + +**Table 8.2.1-3: NR Coverage, Urban, Redcap UE** + +| | Company Name | Scenarios | AL16, 4Rx | AL8, 4Rx | AL16, 2Rx | AL8, 2Rx | AL16, 1RX | AL8, 1RX | PUSCH H eMBB | PUSCH Msg3 | +|-----------|--------------|--------------|-----------|----------|-----------|----------|-----------|----------|--------------|--------------------------------------| +| Redcap UE | [8A-11] | Urban 2.6GHz | | | | | 148.72 | 146.02 | 134.96 | [8A-11]:138.85
[8A-11](2): 142.85 | +| | [8A-15] | Urban 2.6GHz | | | 159.86 | 157.74 | 156.61 | 153.17 | 134.62 | 144.20 | +| | [8A-16] | Urban 2.6GHz | | | | | 152.96 | | | 147.27 | +| | [8A-17] | Urban 2.6GHz | | | | | 157.81 | | | | +| | [8A-2] | Urban 2.6GHz | | | | | 144.60 | 142.90 | | 147.83 | +| | [8A-3] | Urban 2.6GHz | | | | | 153.76 | 151.06 | | 153.23 | +| | [8A-14] | Urban 4GHz | | | | | 156.40 | 153.11 | 127.69 | 143.77 | +| | [8A-13] | Urban 2.6GHz | | | | | | 153.38 | | 148.53 | +| | [8A-7] | Urban 2.6GHz | | | | | 154.61 | 152.11 | 142.51 | 148.73 | +| | [8A-8] | Urban 4GHz | | | | | 155.35 | 152.01 | | 143.26 | +| | [8A-5] | Urban 2.6GHz | | | | | | | | 146.61 | + +Note: "[8A-11](2)" assumes UL 4dB correction factor better than DL, "[8A-11]" assumes UL and DL same correction factor in coverage evaluation template. For the figures in clause 8.2.2 and 8.2.3, the meanings of '[8A-11]' and '[8A-11] 2' refer to this. + +**Table 8.2.1-4: NR Coverage, Rural, Normal UE** + +| | Company Name | Scenarios | AL16, 4Rx | AL8, 4Rx | AL16, 2Rx | AL8, 2Rx | AL16, 1RX | AL8, 1RX | PUSCH H eMBB | PUSCH H Msg3 | +|-----------|--------------|--------------|-----------|----------|-----------|----------|-----------|----------|--------------|--------------| +| Normal UE | [8A-11] | Rural 700MHz | | | 154.99 | 152.32 | | | 143.97 | 143.60 | +| | [8A-15] | Rural 700MHz | | | 154.73 | 152.75 | | | 138.97 | 140.20 | +| | [8A-14] | Rural 700MHz | | | 157.36 | 154.24 | | | 134.78 | 140.76 | +| | [8A-6] | Rural 700MHz | | | | | 154.35 | | | 133.27 | +| | [8A-13] | Rural 700MHz | | | | 150.00 | | | | 135.23 | +| | [8A-5] | Rural 700MHz | | | | | | | | 145.3 | +| | [8A-3] | Rural 700MHz | | | 156.63 | | | | | 148.97 | + +**Table 8.2.1-5: NR Coverage, Rural, Redcap UE** + +| | Company Name | Scenarios | AL16 , 4Rx | AL8 , 4Rx | AL16, 2Rx | AL8, 2Rx | AL16, 1Rx | AL8, 1Rx | PUSCH H eMBB | PUSCH H Msg3 | +|-----------|--------------|--------------|------------|-----------|-----------|----------|-----------|----------|--------------|--------------| +| Redcap UE | [8A-11] | Rural 700MHz | | | | | 149.31 | 146.61 | 140.97 | 140.60 | +| | [8A-15] | Rural 700MHz | | | 151.73 | 149.75 | 149.45 | 145.48 | 135.97 | 136.09 | +| | [8A-16] | Rural 700MHz | | | | | 153.72 | | | 138.99 | +| | [8A-14] | Rural 700MHz | | | | | 150.59 | 146.80 | 131.78 | 137.76 | +| | [8A-13] | Rural 700MHz | | | | | | 143.46 | | 132.23 | +| | [8A-5] | Rural 700MHz | | | | | | | | 142.3 | +| | [8A-3] | Rural 700MHz | | | | | 152.83 | | | 148.97 | + +It can be observed that for a given NR channel, there is a MIL difference among companies. One of the reasons contributes to this difference could be the different assumptions for antenna gain corrections for gNB Tx and Rx. Another reason could be different HARQ assumption for MSG3. Another reason could be different link performance between different companies. The assumed antenna gain correction values used by companies for link budget evaluation is summarized as in Table 8.2.1-6 + +**Table 8.2.1-6: Antenna gain correction value (dB) in the link budget evaluation** + +| Company | Urban | | | | Rural | | | | +|---------|--------|--------|---------------------------------------|-------|-------|-------|------|-------| +| | PDCCH | WUS | Msg3 | PUSCH | PDCCH | WUS | Msg3 | PUSCH | +| [8A-3] | 6 | 6 | 4 | NA | 4 | 4 | 4 | NA | +| [8A-11] | 2.65+8 | 2.65+8 | [8A-11]: 2.65+8
[8A-11](2): 2.65+4 | 0 | 2.65 | 2.65 | 2.65 | 0 | +| [8A-5] | NA | 10.06 | 4.04 | NA | NA | 10.06 | 4.04 | NA | +| [8A-15] | 5.77 | NA | 5.77 | 5.77 | 5.68 | NA | 5.68 | 5.68 | +| [8A-9] | 1.5 | 1.5 | NA | 0 | NA | NA | NA | NA | +| [8A-14] | 5.77 | 3 | 5.77 | 5.77 | 3 | 3 | 0 | NA | +| [8A-16] | 8.05 | 8 | 3 | NA | 0 | 0 | 0 | NA | +| [8A-7] | 8 | 8 | 4.04 | NA | NA | NA | NA | NA | +| [8A-2] | 8 | 8 | 8 | NA | NA | NA | NA | NA | +| [8A-13] | 2.95 | 2.95 | 2.95 | NA | 7.55 | 7.55 | 7.55 | NA | +| [8A-6] | 5.77 | 2.65+8 | 0 | NA | 5.68 | 2.65 | 0 | NA | +| [8A-8] | 5.77 | 5.77 | 5.77 | NA | NA | NA | NA | NA | + +## 8.2.2 Results for urban + +In the evaluation, FAR of $\leq 0.1\%$ and $\leq 1\%$ was used by companies. + +The LP-WUR noise figure assumed for coverage evaluation is + +- For OOK based LP-WUS, 12~20dB +- For FSK based LP-WUS, 12~20dB +- For OFDM based LP-WUS, 9~15dB + +### 8.2.2.1 OOK, Urban, normal UE, PDCCH + +Table 8.2.2.1-1: Gap with PDCCH AL16, 4RX, Urban, MR is normal UE + +![Bar chart showing Average Gap w/ AL16, 4Rx for various OOK configurations. The chart includes a table at the bottom with columns for Waveform family, Scenario, per bit resource, Noise figure, # of info bits, and Waveform.](1406d3fbba2b2fce2607beceace3b6fa_img.jpg) + +The figure is a bar chart titled 'Average Gap w/ AL16, 4Rx' showing the performance gap in dB for various OOK configurations compared to a reference PDCCH AL16, 4RX. The y-axis represents the gap in dB, ranging from -40.00 to 0.00. The x-axis lists various OOK configurations. The bars show that most configurations have a negative gap, indicating better performance than the reference. The best performance is seen with OOK-4 at 48 bits and 13 bits per resource, achieving a gap of -35.72 dB. + +| Waveform family | Scenario | per bit resource (MHz*Symbol/bit) | Noise figure (dB) | # of info bits | Waveform | +|----------------------------------------------|----------|-----------------------------------|-------------------|----------------|----------------------------------------------| +| OOK-1 | 8 | 4.32 | -19.32 | 20 | OOK-1 | +| OOK-1 | 8 | 4.32 | -16.31 | 20 | OOK-1, p=3 dB | +| OOK-1 | 8 | 4.32 | -14.58 | 15 | OOK-1 | +| OOK-1 | 8 | 8.64 | -13.92 | 20 | OOK-1, p=3 dB | +| OOK-1 | 8 | 4.32 | -11.58 | 15 | OOK-1 | +| OOK-1 | 8 | 8.64 | -10.91 | 20 | OOK-1, p=3 dB | +| OOK-1 | 8 | 4.32 | -9.18 | 15 | OOK-1 | +| OOK-1 | 8 | 8.64 | -6.18 | 20 | OOK-1, p=3 dB | +| OOK-4 | 48 | 2.61 | -20.79 | 13 | OOK-4 | +| OOK-4 | 8 | 4.86 | -18.79 | 13 | OOK-4 | +| OOK-4 | 8 | 9.72 | -16.29 | 13 | OOK-4 | +| OOK-4 with repetition | 48 | 13.05 | -16.09 | 13 | OOK-4 with repetition | +| sequence based LPWUS (OOK-1) | 48 | 10.44 | -14.29 | 13 | sequence based LPWUS (OOK-1) | +| OOK-4 with repetition | 48 | 26.1 | -14.29 | 13 | OOK-4 with repetition | +| sequence based LPWUS (OOK-1) | 8 | 19.44 | -13.29 | 13 | sequence based LPWUS (OOK-1) | +| OOK-4 with repetition | 8 | 60.48 | -11.29 | 13 | OOK-4 with repetition | +| sequence based LPWUS (OOK-1) | 8 | 77.76 | -10.29 | 13 | sequence based LPWUS (OOK-1) | +| sequence based LPWUS (OOK-1) | 1 | 120.96 | -9.79 | 13 | sequence based LPWUS (OOK-1) | +| sequence based LPWUS (OOK-1) | 1 | 41.92 | -7.69 | 13 | sequence based LPWUS (OOK-1) | +| sequence based LPWUS (OOK-1) | 1 | 302.4 | -6.99 | 13 | sequence based LPWUS (OOK-1) | +| sequence based LPWUS (OOK-1) with repetition | 1 | 604.8 | -4.79 | 13 | sequence based LPWUS (OOK-1) with repetition | +| OOK-3 | 4 | 8.64 | -35.72 | 12 | OOK-3 | +| OOK-3 | 4 | 8.64 | -34.72 | 12 | OOK-3 | +| OOK-4 | 4 | 8.64 | -24.72 | 12 | OOK-4 | +| OOK-4 | 4 | 8.64 | -19.72 | 12 | OOK-4 | +| OOK-1 | 4 | 8.64 | -18.72 | 12 | OOK-1 | +| OOK-1 | 4 | 8.64 | -17.72 | 12 | OOK-1 | +| OOK-1 | 4 | 8.64 | -16.72 | 12 | OOK-1 | +| OOK-1 | 4 | 8.64 | -16.62 | 12 | OOK-1 | +| OOK-4 | 1 | 4.32 | -15.02 | 12 | OOK-4 | +| OOK-1 | 1 | 17.28 | -14.22 | 12 | OOK-1 | +| OOK-4 | 1 | 8.64 | -12.02 | 12 | OOK-4 | +| OOK-1 | 1 | 17.28 | -12.02 | 12 | OOK-1 | +| OOK-1 | 1 | 43.2 | -11.82 | 12 | OOK-1 | +| OOK-1 | 1 | 69.12 | -11.32 | 12 | OOK-1 | +| OOK-4 | 1 | 34.56 | -11.32 | 12 | OOK-4 | +| OOK-4 | 1 | 30.24 | -9.72 | 12 | OOK-4 | +| OOK-1 | 1 | 77.76 | -9.72 | 12 | OOK-1 | +| OOK-1 | 1 | 138.24 | -9.72 | 12 | OOK-1 | +| OOK-1 | 1 | 246.08 | -9.62 | 12 | OOK-1 | +| OOK-4 | 4 | 6.48 | -23.56 | 15 | OOK-4 | +| OOK-4 | 4 | 6.48 | -23.30 | 15 | OOK-4 | +| OOK-1 | 4 | 3.24 | -20.32 | 15 | OOK-1 | +| OOK-4 | 4 | 3.24 | -18.81 | 15 | OOK-4 | +| OOK-1 | 4 | 6.48 | -18.13 | 15 | OOK-1 | +| OOK-1 | 4 | 6.48 | -17.44 | 15 | OOK-1 | +| OOK-1 | 4 | 12.96 | -16.01 | 15 | OOK-1 | +| OOK-4 | 4 | 6.48 | -15.89 | 15 | OOK-4 | +| OOK-1 | 4 | 12.96 | -15.54 | 15 | OOK-1 | +| OOK-4 | 4 | 6.48 | -15.38 | 15 | OOK-4 | +| OOK-4 | 4 | 6.48 | -14.75 | 15 | OOK-4 | +| OOK-4 | 4 | 12.96 | -14.08 | 15 | OOK-4 | +| OOK-4 | 4 | 12.96 | -13.31 | 15 | OOK-4 | + +Bar chart showing Average Gap w/ AL16, 4Rx for various OOK configurations. The chart includes a table at the bottom with columns for Waveform family, Scenario, per bit resource, Noise figure, # of info bits, and Waveform. + +### Observation: + +For normal UE and urban scenario, comparing MIL of OOK based LP-WUS to legacy PDCCH AL16, 4Rx for paging + +- [8A-2], [8A-3], [8A-6], [8A-7] and [8A-8] show that with the LP-WUS resource of X=8.64~604.8 MHz\*Symbol/bit , the MIL margin Y is -17.72~-4.79 dB + +**Table 8.2.2.1-2: Gap with PDCCH AL8, 4RX, Urban, MR is normal UE** + +![Bar chart showing the gap with PDCCH AL8, 4RX, Urban, MR is normal UE. The chart displays various OOK configurations and their corresponding MIL values. The Y-axis represents the gap in dB, ranging from -20 to 5. The X-axis lists different waveform families and scenarios. The data is categorized into three groups: [8A-13], [8A-3], and [8A-7].](24f9540e133ae0abdd0948928f8431a3_img.jpg) + +The figure is a bar chart titled 'Average: Gap w/ AL8, 4Rx'. The Y-axis represents the gap in dB, ranging from -20 to 5. The X-axis lists various waveform families and scenarios. The data is categorized into three groups: [8A-13], [8A-3], and [8A-7]. + +| Group | Waveform family | Scenario | per bit resource (MHz*symbol/bit) | Noise figure (dB) | # of info bits | Gap w/ AL8, 4Rx (dB) | +|---------|----------------------------------------------|----------|-----------------------------------|-------------------|----------------|----------------------| +| [8A-13] | OOK-4 | | 24 | 12 | 2.88 | -10.23 | +| | OOK-4 | | 8 | 12 | 4.32 | -9.56 | +| | OOK-4 | | 24 | 12 | 46.08 | -0.4 | +| | OOK-4 | | 8 | 12 | 69.12 | 0.69 | +| | OOK-4 | | 48 | 13 | 2.61 | -18.09 | +| | OOK-4 | | 8 | 13 | 4.86 | -16.09 | +| | OOK-4 | | 8 | 13 | 9.72 | -13.59 | +| | OOK-4 with repetition | | 48 | 13 | 13.05 | -13.39 | +| | OOK-1 | | 48 | 13 | 10.44 | -11.59 | +| | sequence based LPWUS (OOK-1) | | 1 | 13 | 17.28 | -11.59 | +| [8A-3] | OOK-4 with repetition | | 48 | 13 | 26.1 | -11.59 | +| | OOK-1 | | 48 | 13 | 19.44 | -10.59 | +| | sequence based LPWUS (OOK-1) | | 1 | 13 | 60.48 | -8.59 | +| | OOK-4 with repetition | | 8 | 13 | 77.76 | -7.59 | +| | sequence based LPWUS (OOK-1) | | 1 | 13 | 120.96 | -7.09 | +| | sequence based LPWUS (OOK-1) | | 1 | 13 | 241.92 | -4.99 | +| | sequence based LPWUS (OOK-1) | | 1 | 13 | 302.4 | -4.29 | +| | sequence based LPWUS (OOK-1) with repetition | | 1 | 13 | 604.8 | -2.09 | +| | OOK-1 | | 1 | 12 | 8.64 | -14.22 | +| | OOK-4 | | 1 | 12 | 4.32 | -14.12 | +| [8A-7] | OOK-1 | | 1 | 12 | 17.28 | -12.52 | +| | OOK-4 | | 1 | 12 | 8.64 | -11.72 | +| | OOK-1 | | 1 | 12 | 17.28 | -9.52 | +| | OOK-1 | | 1 | 12 | 43.2 | -9.52 | +| | OOK-1 | | 1 | 12 | 69.12 | -9.32 | +| | OOK-4 | | 1 | 12 | 34.56 | -8.82 | +| | OOK-4 | | 1 | 12 | 30.24 | -7.22 | +| | OOK-1 | | 1 | 12 | 77.76 | -7.22 | +| | OOK-1 | | 1 | 12 | 138.24 | -7.22 | +| | OOK-4 | | 1 | 12 | 60.48 | -7.12 | +| [8A-8] | OOK-1 | | 4 | 15 | 6.48 | -17.47 | +| | OOK-4 | | 4 | 15 | 6.48 | -17.21 | +| | OOK-1 | | 4 | 15 | 3.24 | -14.23 | +| | OOK-4 | | 4 | 15 | 3.24 | -12.72 | +| | OOK-1 | | 4 | 15 | 6.48 | -12.04 | +| | OOK-1 | | 4 | 15 | 6.48 | -11.35 | +| | OOK-1 | | 4 | 15 | 12.96 | -9.92 | +| | OOK-4 | | 4 | 15 | 6.48 | -9.8 | +| | OOK-1 | | 4 | 15 | 12.96 | -9.45 | +| | OOK-4 | | 4 | 15 | 6.48 | -9.29 | +| OOK-4 | | 4 | 15 | 6.48 | -8.66 | | +| OOK-4 | | 4 | 15 | 12.96 | -7.99 | | +| OOK-4 | | 4 | 15 | 12.96 | -7.22 | | + +Bar chart showing the gap with PDCCH AL8, 4RX, Urban, MR is normal UE. The chart displays various OOK configurations and their corresponding MIL values. The Y-axis represents the gap in dB, ranging from -20 to 5. The X-axis lists different waveform families and scenarios. The data is categorized into three groups: [8A-13], [8A-3], and [8A-7]. + +**Observation:** + +For normal UE and Urban scenario, comparing MIL of OOK based LP-WUS to legacy PDCCH AL8, 4Rx for paging + +- [8A-13] shows it is feasible to achieve comparable MIL (i.e. MIL margin $Y \geq -1\text{dB}$ ) with LP-WUS of $X = 46.08\text{ MHz} \cdot \text{Symbol/bit}$ , MIL margin $Y = -0.4\text{dB}$ +- [8A-3], [8A-7] and [8A-8] show that with the LP-WUS resource of $X = 12.96 \sim 604.8\text{ MHz} \cdot \text{Symbol/bit}$ , the MIL margin $Y$ is $-7.22 \sim -2.09\text{ dB}$ + +Table 8.2.2.1-3: Gap with PDCCH AL8, 2RX, Urban, MR is normal UE + +![A bar chart and data table showing the gap with PDCCH AL8, 2RX for various OOK-based LP-WUS configurations. The chart displays MIL margin values in dB for different waveform families and scenarios. The table below provides detailed parameters for each configuration.](61e3d8dbce06e400d42d8b708d1fa4f4_img.jpg) + +Average: Gap w/ AL8, 2Rx + +| Waveform family | Scenario | per bit resource (MHz*symbol/bit) | Noise figure (dB) | # of info bits | Gap w/ AL8, 2Rx (dB) | +|------------------------------|----------|-----------------------------------|-------------------|----------------|----------------------| +| OOK-4, p=3 dB | [8A-11] | 12 | 8 | 12 | -9.8 | +| OOK-4, p=3 dB | [8A-11] | 12 | 8 | 12 | -9.41 | +| OOK-4, p=3 dB | [8A-11] | 12 | 8 | 12 | -8.93 | +| OOK-4, p=3 dB | [8A-11] | 12 | 8 | 12 | -8.89 | +| OOK-4 | [8A-11] | 12 | 8 | 12 | -8.57 | +| OOK-4 | [8A-11] | 12 | 8 | 12 | -8.28 | +| OOK-4 | [8A-11] | 12 | 8 | 12 | -8.24 | +| OOK-4 | [8A-11] | 12 | 8 | 12 | -7.96 | +| OOK-4 | [8A-11] | 12 | 8 | 12 | -7.47 | +| OOK-4 | [8A-11] | 12 | 8 | 12 | -5.52 | +| OOK-4 | [8A-11] | 12 | 8 | 12 | -4.01 | +| OOK-4 | [8A-11] | 12 | 8 | 12 | -0.66 | +| OOK-4 | [8A-11] | 12 | 8 | 12 | -0.62 | +| OOK-4 | [8A-11] | 12 | 8 | 12 | -0.53 | +| OOK-4 | [8A-11] | 12 | 8 | 12 | -0.38 | +| OOK-4 | [8A-11] | 12 | 8 | 12 | -0.12 | +| OOK-4 | [8A-11] | 12 | 8 | 12 | 0.25 | +| OOK-4 | [8A-11] | 12 | 8 | 12 | 0.48 | +| OOK-4 | [8A-11] | 12 | 8 | 12 | 0.7 | +| OOK-4 | [8A-11] | 12 | 8 | 12 | 0.98 | +| OOK-4 | [8A-11] | 12 | 8 | 12 | 1.17 | +| OOK-1, p=3 dB | [8A-14] | 20 | 48 | 12 | -11.83 | +| OOK-1, p=3 dB | [8A-14] | 20 | 48 | 12 | -9.55 | +| OOK-1, p=3 dB | [8A-14] | 20 | 48 | 12 | -7.47 | +| OOK-1, p=3 dB | [8A-14] | 20 | 48 | 12 | -15.09 | +| OOK-1, p=3 dB | [8A-14] | 20 | 48 | 12 | -13.09 | +| OOK-1, p=3 dB | [8A-14] | 20 | 48 | 12 | -10.59 | +| OOK-1, p=3 dB | [8A-14] | 20 | 48 | 12 | -10.39 | +| OOK-4 with repetition | [8A-3] | 48 | 8 | 12 | -8.59 | +| OOK-4 with repetition | [8A-3] | 48 | 8 | 12 | -7.59 | +| OOK-4 with repetition | [8A-3] | 48 | 8 | 12 | -5.59 | +| OOK-4 with repetition | [8A-3] | 48 | 8 | 12 | -4.59 | +| OOK-4 with repetition | [8A-3] | 48 | 8 | 12 | -4.09 | +| OOK-4 with repetition | [8A-3] | 48 | 8 | 12 | -1.99 | +| OOK-4 with repetition | [8A-3] | 48 | 8 | 12 | -1.29 | +| OOK-4 with repetition | [8A-3] | 48 | 8 | 12 | 0.91 | +| sequence based LPWUS (OOK-1) | [8A-8] | 1 | 48 | 12 | -14.17 | +| sequence based LPWUS (OOK-1) | [8A-8] | 1 | 48 | 12 | -13.91 | +| sequence based LPWUS (OOK-1) | [8A-8] | 1 | 48 | 12 | -10.93 | +| sequence based LPWUS (OOK-1) | [8A-8] | 1 | 48 | 12 | -9.42 | +| sequence based LPWUS (OOK-1) | [8A-8] | 1 | 48 | 12 | -8.74 | +| sequence based LPWUS (OOK-1) | [8A-8] | 1 | 48 | 12 | -8.05 | +| sequence based LPWUS (OOK-1) | [8A-8] | 1 | 48 | 12 | -6.62 | +| sequence based LPWUS (OOK-1) | [8A-8] | 1 | 48 | 12 | -6.5 | +| sequence based LPWUS (OOK-1) | [8A-8] | 1 | 48 | 12 | -6.15 | +| sequence based LPWUS (OOK-1) | [8A-8] | 1 | 48 | 12 | -5.99 | +| sequence based LPWUS (OOK-1) | [8A-8] | 1 | 48 | 12 | -5.36 | +| sequence based LPWUS (OOK-1) | [8A-8] | 1 | 48 | 12 | -4.69 | +| sequence based LPWUS (OOK-1) | [8A-8] | 1 | 48 | 12 | -3.92 | +| sequence based LPWUS (OOK-1) | [8A-9] | 1 | 48 | 12 | -22.05 | +| sequence based LPWUS (OOK-1) | [8A-9] | 1 | 48 | 12 | -12.54 | +| sequence based LPWUS (OOK-1) | [8A-9] | 1 | 48 | 12 | -9.76 | + +A bar chart and data table showing the gap with PDCCH AL8, 2RX for various OOK-based LP-WUS configurations. The chart displays MIL margin values in dB for different waveform families and scenarios. The table below provides detailed parameters for each configuration. + +**Observation:** + +For normal UE and Urban scenario, comparing MIL of OOK based LP-WUS to legacy PDCCH AL8, 2Rx for paging + +- [8A-3] and [8A-11] show it is feasible to achieve comparable MIL (i.e. MIL margin $Y \geq -1\text{dB}$ ) +- [8A-11] shows the resource of LP-WUS $X = 28.8 \text{ MHz} \cdot \text{Symbol/bit}$ , MIL margin $Y = -0.53\text{dB}$ +- [8A-3] shows the resource of LP-WUS $X = 604.8 \text{ MHz} \cdot \text{Symbol/bit}$ , MIL margin $Y = 0.91\text{dB}$ +- [8A-8], [8A-9] and [8A-14] show that with the LP-WUS resource of $X = 0.72 \sim 12.96 \text{ MHz} \cdot \text{Symbol/bit}$ , the MIL margin $Y$ is $-9.76 \sim -3.92 \text{ dB}$ + +### 8.2.2.2 OOK, Urban, Redcap UE, PDCCH + +**Table 8.2.2.2-1: Gap with PDCCH AL16, 1RX** + +![A bar chart titled 'Average Gap w/ AL16, 1RX' showing performance gaps for various LP-WUS configurations grouped by test cases [8A-11] through [8A-8]. The y-axis shows gap in dB from -25 to 10. Bars represent individual configurations with values labeled above or below. Key data points include [8A-2] with a gap of -0.38 dB and [8A-16] with a gap of 0.47 dB.](be340a80845e55d744bd90a4f2c0dd67_img.jpg) + +**Average Gap w/ AL16, 1RX** + +| Group | Resource X (MHz*Symbol/bit) | MIL Margin Y (dB) | +|---------|-----------------------------|-------------------| +| [8A-16] | 23.04 | 0.47 | +| [8A-2] | 4.32 | -0.38 | +| [8A-3] | 302.4 | -0.79 | +| [8A-14] | 14.4 ~ 30.24 | -11.39 ~ -1.49 | +| [8A-17] | 8.64 ~ 51.84 | -19.95 ~ -2.11 | +| [8A-7] | 4.32 ~ 69.12 | -10.52 ~ -3.52 | +| [8A-8] | 3.24 ~ 12.96 | -13.63 ~ -3.36 | + +A bar chart titled 'Average Gap w/ AL16, 1RX' showing performance gaps for various LP-WUS configurations grouped by test cases [8A-11] through [8A-8]. The y-axis shows gap in dB from -25 to 10. Bars represent individual configurations with values labeled above or below. Key data points include [8A-2] with a gap of -0.38 dB and [8A-16] with a gap of 0.47 dB. + +**Observation:** + +For RedCap UE and Urban scenario, comparing MIL of OOK based LP-WUS to legacy PDCCH AL16, 1Rx for paging + +- [8A-2], [8A-3] and [8A-16] show it is feasible to achieve comparable MIL (i.e.MIL margin $Y \geq -1\text{dB}$ ) + - [8A-2] shows the resource of LP-WUS $X = 4.32 \text{ MHz} \cdot \text{Symbol/bit}$ , MIL margin $Y = -0.38\text{dB}$ + - [8A-16] show the resource of LP-WUS $X = 23.04 \text{ MHz} \cdot \text{Symbol/bit}$ , MIL margin $Y = 0.47\text{dB}$ + - [8A-3] show the resource of LP-WUS $X = 302.4 \text{ MHz} \cdot \text{Symbol/bit}$ , MIL margin $Y = -0.79\text{dB}$ +- [8A-7], [8A-8], [8A-11], [8A-14] and [8A-17] show that with the LP-WUS resource of $X = 3.02 \sim 60.48 \text{ MHz} \cdot \text{Symbol/bit}$ , the MIL margin $Y$ is $-13.85 \sim -1.49 \text{ dB}$ + +Table 8.2.2.2-2: Gap with PDCCH AL8, 1RX + +![Bar chart and data table showing MIL margin (Y) for various OOK configurations. The chart shows MIL margin in dB for different OOK configurations, with values ranging from -11.89 dB to 9.72 dB. The table below provides detailed parameters for each configuration.](677895e18a11676be0d822ac49108de3_img.jpg) + +| Scenario | OOK Type | Repetition | Bandwidth (MHz) | Symbol Rate (Symbol/bit) | MIL Margin (dB) | +|----------|-----------------------|------------|-----------------|--------------------------|-----------------| +| [8A-11] | OOK-4_p=3 dB | 12 | 8 | 8 | -6.49 | +| | OOK-4_p=3 dB | 12 | 8 | 8 | -6.1 | +| | OOK-4_p=3 dB | 12 | 8 | 8 | -5.58 | +| | OOK-4_p=3 dB | 12 | 8 | 8 | -5.26 | +| | OOK-4_p=3 dB | 12 | 8 | 8 | -4.97 | +| | OOK-4_p=3 dB | 12 | 8 | 8 | -4.93 | +| | OOK-4_p=3 dB | 12 | 8 | 8 | -4.93 | +| | OOK-4_p=3 dB | 12 | 8 | 8 | -4.65 | +| | OOK-4_p=3 dB | 12 | 8 | 8 | -4.16 | +| | OOK-4_p=3 dB | 12 | 8 | 8 | -2.31 | +| | OOK-4_p=3 dB | 12 | 8 | 8 | -0.73 | +| | OOK-4_p=3 dB | 12 | 8 | 8 | -0.7 | +| | OOK-4_p=3 dB | 12 | 8 | 8 | -0.54 | +| [8A-13] | OOK-4 | 12 | 8 | 8 | -0.52 | +| | OOK-4 | 12 | 8 | 8 | 0.52 | +| | OOK-4 | 12 | 8 | 8 | 1.03 | +| | OOK-4 | 12 | 8 | 8 | 1.05 | +| | OOK-4 | 12 | 8 | 8 | 1.08 | +| | OOK-4 | 12 | 8 | 8 | 1.21 | +| | OOK-4 | 12 | 8 | 8 | -4.07 | +| | OOK-4 | 12 | 8 | 8 | -3.4 | +| | OOK-4 | 12 | 8 | 8 | -0.12 | +| | OOK-4 | 12 | 8 | 8 | 0.93 | +| | OOK-4 | 12 | 8 | 8 | -8.1 | +| | OOK-4 | 12 | 8 | 8 | -5.82 | +| | OOK-4 | 12 | 8 | 8 | -3.74 | +| [8A-14] | OOK-1_p=3 dB | 12 | 20 | 20 | -3.42 | +| | OOK-1_p=3 dB | 12 | 20 | 20 | -3.42 | +| | OOK-1_p=3 dB | 12 | 20 | 20 | -3.42 | +| | OOK-1_p=3 dB | 12 | 20 | 20 | -3.42 | +| | OOK-1_p=3 dB | 12 | 20 | 20 | -3.42 | +| | OOK-1_p=3 dB | 12 | 20 | 20 | -3.42 | +| | OOK-1_p=3 dB | 12 | 20 | 20 | -3.42 | +| | OOK-1_p=3 dB | 12 | 20 | 20 | -3.42 | +| | OOK-1_p=3 dB | 12 | 20 | 20 | -3.42 | +| | OOK-1_p=3 dB | 12 | 20 | 20 | -3.42 | +| | OOK-1_p=3 dB | 12 | 20 | 20 | -3.42 | +| | OOK-1_p=3 dB | 12 | 20 | 20 | -3.42 | +| | OOK-1_p=3 dB | 12 | 20 | 20 | -3.42 | +| [8A-2] | OOK-1 | 12 | 8 | 8 | -0.41 | +| | OOK-1 | 12 | 8 | 8 | 1.32 | +| | OOK-1 | 12 | 8 | 8 | 1.98 | +| | OOK-1 | 12 | 8 | 8 | 4.32 | +| | OOK-1 | 12 | 8 | 8 | 4.99 | +| | OOK-1 | 12 | 8 | 8 | 6.72 | +| | OOK-1 | 12 | 8 | 8 | 9.72 | +| | OOK-1 | 12 | 8 | 8 | -11.89 | +| | OOK-1 | 12 | 8 | 8 | -9.89 | +| | OOK-1 | 12 | 8 | 8 | -7.39 | +| | OOK-1 | 12 | 8 | 8 | -7.39 | +| | OOK-1 | 12 | 8 | 8 | -5.39 | +| | OOK-1 | 12 | 8 | 8 | -5.39 | +| [8A-3] | OOK-4 with repetition | 12 | 8 | 8 | -4.39 | +| | OOK-4 with repetition | 12 | 8 | 8 | -2.39 | +| | OOK-4 with repetition | 12 | 8 | 8 | -1.39 | +| | OOK-4 with repetition | 12 | 8 | 8 | -0.89 | +| | OOK-4 with repetition | 12 | 8 | 8 | 1.21 | +| | OOK-4 with repetition | 12 | 8 | 8 | 1.91 | +| | OOK-4 with repetition | 12 | 8 | 8 | 4.11 | +| | OOK-4 with repetition | 12 | 8 | 8 | -8.02 | +| | OOK-4 with repetition | 12 | 8 | 8 | -7.92 | +| | OOK-4 with repetition | 12 | 8 | 8 | -6.32 | +| | OOK-4 with repetition | 12 | 8 | 8 | -5.52 | +| | OOK-4 with repetition | 12 | 8 | 8 | -3.32 | +| | OOK-4 with repetition | 12 | 8 | 8 | -3.32 | +| [8A-7] | OOK-4 | 12 | 8 | 8 | -3.12 | +| | OOK-4 | 12 | 8 | 8 | -2.62 | +| | OOK-4 | 12 | 8 | 8 | -1.02 | +| | OOK-4 | 12 | 8 | 8 | -1.02 | +| | OOK-4 | 12 | 8 | 8 | -1.02 | +| | OOK-4 | 12 | 8 | 8 | -0.92 | +| | OOK-4 | 12 | 8 | 8 | -10.27 | +| | OOK-4 | 12 | 8 | 8 | -10.01 | +| | OOK-4 | 12 | 8 | 8 | -7.03 | +| | OOK-4 | 12 | 8 | 8 | -5.52 | +| | OOK-4 | 12 | 8 | 8 | -4.84 | +| | OOK-4 | 12 | 8 | 8 | -4.15 | +| | OOK-4 | 12 | 8 | 8 | -2.72 | +| [8A-8] | OOK-4 | 12 | 8 | 8 | -2.6 | +| | OOK-4 | 12 | 8 | 8 | -2.25 | +| | OOK-4 | 12 | 8 | 8 | -2.09 | +| | OOK-4 | 12 | 8 | 8 | -1.46 | +| | OOK-4 | 12 | 8 | 8 | -0.79 | +| | OOK-4 | 12 | 8 | 8 | -0.02 | +| | OOK-4 | 12 | 8 | 8 | 0.02 | +| | OOK-4 | 12 | 8 | 8 | 0.02 | +| | OOK-4 | 12 | 8 | 8 | 0.02 | +| | OOK-4 | 12 | 8 | 8 | 0.02 | +| | OOK-4 | 12 | 8 | 8 | 0.02 | +| | OOK-4 | 12 | 8 | 8 | 0.02 | +| | OOK-4 | 12 | 8 | 8 | 0.02 | + +Bar chart and data table showing MIL margin (Y) for various OOK configurations. The chart shows MIL margin in dB for different OOK configurations, with values ranging from -11.89 dB to 9.72 dB. The table below provides detailed parameters for each configuration. + +**Observation:** + +For RedCap UE and Urban scenario, comparing MIL of OOK based LP-WUS to legacy PDCCH AL8, 1Rx for paging + +- [8A-2], [8A-3], [8A-7], [8A-8], [8A-11] and [8A-13] show it is feasible to achieve comparable MIL (i.e. MIL margin $Y \geq -1\text{dB}$ ) +- [8A-2], [8A-11], [8A-13] and [8A-8] show the resource of LP-WUS $X = 4.32 \sim 12.96 \text{ MHz} \cdot \text{Symbol/bit}$ , MIL margin $Y = -0.02 \sim 1.32 \text{ dB}$ +- [8A-3] and [8A-7] show the resource of LP-WUS $X = 60.48 \sim 120.96 \text{ MHz} \cdot \text{Symbol/bit}$ , MIL margin $Y = -0.89 \sim -0.92\text{dB}$ +- [8A-14] show that with the LP-WUS resource of $X = 3.02 \text{ MHz} \cdot \text{Symbol/bit}$ , the MIL margin $Y = -3.74 \text{ dB}$ + +### 8.2.2.3 OOK, Urban, Normal UE, Msg.3 + +Table 8.2.2.3: OOK, Urban, Normal UE, Msg.3 + +![Bar chart showing Average Gap w/ PUSCH Msg.3 for various OOK configurations. The chart includes a data table at the bottom with columns for waveform family, scenario, gap, per bit resource, noise figure, and number of info bits.](cc4a284d42136d1539eb2e13a68cbc50_img.jpg) + +Average Gap w/ PUSCH Msg.3 + +| Waveform family | Scenario | Average Gap w/ PUSCH Msg.3 | per bit resource (MHz*symbol/bit) | Noise figure (dB) | # of info bits | +|-----------------|----------|----------------------------|-----------------------------------|-------------------|----------------| +| OOK-4 | p=3 dB | 0.68 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | 1.07 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | 1.55 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | 1.59 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | 1.91 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | 2.2 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | 2.24 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | 2.52 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | 3.01 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | 4.96 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | 6.47 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | 9.82 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | 9.86 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | 9.95 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | 10.1 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | 10.36 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | 10.73 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | 10.96 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | 11.18 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | 11.46 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | 11.65 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | 0.78 | 24 | 8 | 12 | +| OOK-4 | p=3 dB | 1.45 | 8 | 8 | 12 | +| OOK-4 | p=3 dB | 10.61 | 24 | 8 | 12 | +| OOK-4 | p=3 dB | 11.7 | 8 | 8 | 12 | +| OOK-4 | p=3 dB | 1.24 | 20 | 8 | 12 | +| OOK-4 | p=3 dB | 3.52 | 20 | 8 | 12 | +| OOK-4 | p=3 dB | 5.6 | 20 | 8 | 12 | +| OOK-1 | | -8.35 | 8 | 8 | 12 | +| OOK-1 | p=3 dB | -5.34 | 8 | 8 | 12 | +| OOK-1 | p=3 dB | -3.61 | 15 | 8 | 12 | +| OOK-1 | p=3 dB | -2.95 | 20 | 8 | 12 | +| OOK-1 | p=3 dB | -0.61 | 15 | 8 | 12 | +| OOK-1 | p=3 dB | 0.06 | 20 | 8 | 12 | +| OOK-1 | p=3 dB | 1.79 | 15 | 8 | 12 | +| OOK-1 | p=3 dB | 4.79 | 15 | 8 | 12 | +| OOK-4 | p=3 dB | -3.32 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | -2.93 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | -2.45 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | -2.41 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | -2.09 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | -1.8 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | -1.76 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | -1.48 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | -0.99 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | 0.96 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | 2.47 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | 5.82 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | 5.86 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | 5.95 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | 6.1 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | 6.36 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | 6.73 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | 6.96 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | 7.18 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | 7.46 | 12 | 8 | 12 | +| OOK-4 | p=3 dB | 7.65 | 12 | 8 | 12 | + +Bar chart showing Average Gap w/ PUSCH Msg.3 for various OOK configurations. The chart includes a data table at the bottom with columns for waveform family, scenario, gap, per bit resource, noise figure, and number of info bits. + +![Bar chart showing Average Gap w/ PUSCH Msg3 for various waveform families and scenarios. The chart includes data for OOK, sequence based LPWUS, and OOK+FSK joint Modulation across scenarios [8A-3], [8A-5], [8A-6], [8A-7], and [8A-8].](bec54a43401eceb0270c022d21e71a3e_img.jpg) + +The figure is a bar chart titled 'Average Gap w/ PUSCH Msg3'. The y-axis represents the MIL margin in dB, ranging from -20 to 10. The x-axis lists various waveform configurations categorized by scenario: [8A-3], [8A-5], [8A-6], [8A-7], and [8A-8]. + +| Scenario | Waveform Family | Gap w/ PUSCH Msg3 (dB) | per bit resource (MHz*symbol/bit) | Noise figure (dB) | # of info bits | +|----------|----------------------------------|------------------------|-----------------------------------|-------------------|----------------| +| [8A-3] | OOK-4 | -14.06 | 48 | 13 | 2.61 | +| | OOK-4 | -12.06 | 8 | 13 | 4.86 | +| | OOK-4 | -9.56 | 8 | 13 | 9.72 | +| | OOK-4 with repetition | -9.36 | 48 | 13 | 13.05 | +| | OOK-4 with repetition | -7.56 | 48 | 13 | 10.44 | +| | OOK-4 with repetition | -7.56 | 1 | 13 | 17.28 | +| | OOK-4 with repetition | -7.56 | 48 | 13 | 26.1 | +| | OOK-4 with repetition | -6.56 | 1 | 13 | 19.44 | +| | OOK-4 with repetition | -6.56 | 8 | 13 | 60.48 | +| | OOK-4 with repetition | -4.56 | 1 | 13 | 77.76 | +| | OOK-4 with repetition | -3.56 | 8 | 13 | 120.96 | +| | OOK-4 with repetition | -3.56 | 1 | 13 | 41.92 | +| | OOK-4 with repetition | -0.26 | 1 | 13 | 302.4 | +| [8A-5] | OOK-4 | -12.13 | 48 | 15 | 2.16 | +| | OOK-4 | -11.63 | 48 | 15 | 2.16 | +| | OOK-4 | -11.53 | 48 | 15 | 2.16 | +| | OOK-4 | -11.43 | 48 | 15 | 2.16 | +| | OOK-4 | -9.53 | 48 | 15 | 2.16 | +| | OOK-4 with concentrated waveform | -8.12 | 48 | 15 | 2.16 | +| | OOK-4 with concentrated waveform | -7.63 | 48 | 15 | 2.16 | +| | OOK-4 with concentrated waveform | -7.44 | 48 | 15 | 2.16 | +| | OOK-4 with concentrated waveform | -7.43 | 48 | 15 | 2.16 | +| | OOK-4 with concentrated waveform | -7.3 | 48 | 15 | 2.16 | +| | OOK-4 with concentrated waveform | -7.03 | 48 | 15 | 2.16 | +| | OOK-4 with concentrated waveform | -3.93 | 48 | 15 | 8.64 | +| | OOK-4 with concentrated waveform | -2.83 | 48 | 15 | 4.32 | +| [8A-6] | OOK-4 | -2.63 | 48 | 15 | 8.64 | +| | OOK-4 | -0.93 | 48 | 15 | 8.64 | +| | OOK-4 | -6.03 | 4 | 12 | 8.64 | +| | OOK-4 | -5.03 | 4 | 12 | 8.64 | +| | OOK-4 | 4.97 | 4 | 12 | 8.64 | +| | OOK-4 | 9.97 | 4 | 12 | 8.64 | +| | OOK-4 | 10.97 | 4 | 12 | 8.64 | +| | OOK-4 | 11.97 | 4 | 12 | 8.64 | +| | OOK-4 | -4.64 | 1 | 12 | 8.64 | +| | OOK-4 | -4.54 | 1 | 12 | 8.64 | +| | OOK-4 | -2.94 | 1 | 12 | 8.64 | +| | OOK-4 | -2.14 | 1 | 12 | 8.64 | +| | OOK-4 | 0.06 | 1 | 12 | 17.28 | +| [8A-7] | OOK-4 | 0.06 | 48 | 15 | 2.16 | +| | OOK-4 | 0.26 | 48 | 15 | 2.16 | +| | OOK-4 | 0.76 | 48 | 15 | 2.16 | +| | OOK-4 | 2.36 | 48 | 15 | 2.16 | +| | OOK-4 | 2.36 | 48 | 15 | 2.16 | +| | OOK-4 | 2.36 | 48 | 15 | 2.16 | +| | OOK-4 | 2.46 | 48 | 15 | 2.16 | +| | OOK-4 | -1.52 | 4 | 15 | 6.48 | +| | OOK-4 | -1.26 | 4 | 15 | 6.48 | +| | OOK-4 | 1.72 | 4 | 15 | 3.24 | +| | OOK-4 | 3.23 | 4 | 15 | 3.24 | +| | OOK-4 | 3.91 | 4 | 15 | 6.48 | +| | OOK-4 | 4.6 | 4 | 15 | 6.48 | +| [8A-8] | OOK-4 | 6.03 | 48 | 15 | 2.16 | +| | OOK-4 | 6.15 | 48 | 15 | 2.16 | +| | OOK-4 | 6.5 | 48 | 15 | 2.16 | +| | OOK-4 | 6.66 | 48 | 15 | 2.16 | +| | OOK-4 | 7.29 | 48 | 15 | 2.16 | +| | OOK-4 | 7.96 | 48 | 15 | 2.16 | +| | OOK-4 | 8.73 | 48 | 15 | 2.16 | +| | OOK-4 | -1.52 | 4 | 15 | 6.48 | +| | OOK-4 | -1.26 | 4 | 15 | 6.48 | +| | OOK-4 | 1.72 | 4 | 15 | 3.24 | +| | OOK-4 | 3.23 | 4 | 15 | 3.24 | +| | OOK-4 | 3.91 | 4 | 15 | 6.48 | +| | OOK-4 | 4.6 | 4 | 15 | 6.48 | + +Bar chart showing Average Gap w/ PUSCH Msg3 for various waveform families and scenarios. The chart includes data for OOK, sequence based LPWUS, and OOK+FSK joint Modulation across scenarios [8A-3], [8A-5], [8A-6], [8A-7], and [8A-8]. + +**Observation:** + +For Normal UE in Urban, [8A-2], [8A-3], [8A-5], [8A-6], [8A-7], [8A-8], [8A-11], [8A-13] and [8A-14], show OOK based LP-WUS is feasible to achieve comparable MIL (i.e.MIL margin $Y \geq -1\text{dB}$ ) than PUSCH for Msg.3 + +- [8A-2], [8A-5], [8A-6], [8A-8], [8A-11] and [8A-13] show that, with LP-WUS resource $X = 1.8 \sim 8.64 \text{ MHz} \cdot \text{Symbol/bit}$ , MIL margin $Y = -0.93 \sim 11.97 \text{ dB}$ , assuming no power boosting for LP-WUS; +- [8A-7] show that, with LP-WUS resource $X = 17.28 \text{ MHz} \cdot \text{Symbol/bit}$ , MIL margin $Y = 0.06 \text{ dB}$ , assuming antenna element gain of LP-WUR is 3dB worse than MR. +- [8A-3] show that, with LP-WUS resource $X = 241.92 \text{ MHz} \cdot \text{Symbol/bit}$ , MIL margin $Y = -0.96 \text{ dB}$ , assuming 4dB HARQ gain from 2 retransmissions for Msg3 PUSCH and no power boost for LP-WUS +- [8A-2], [8A-11] and [8A-14], show that, with LP-WUS resource $X = 0.9 \sim 4.32 \text{ MHz} \cdot \text{Symbol/bit}$ , MIL margin $Y = -0.61 \text{ dB} \sim 1.24 \text{ dB}$ , assuming 3dB power boosting for LP-WUS + +### 8.2.2.4 OOK, Urban, Redcap UE, Msg.3 + +Table 8.2.2.4: OOK, Urban, Redcap UE, Msg.3 + +![Bar chart and data table showing performance metrics for various OOK waveforms. The chart displays 'Average:Gap w/ PUSCH Msg3' on the y-axis (ranging from -20 to 5) against different waveform configurations on the x-axis. The table below provides detailed metrics including number of repetitions, bits per symbol, noise figure, and info bits for each waveform.](f8b22299fe23201d5b3fdece96436fca_img.jpg) + +**Average:Gap w/ PUSCH Msg3** + +| Waveform family | Scenario | Gap w/ PUSCH Msg3 | per bit resource (MHz*symb/bit) | Noise figure (dB) | # of info bits | Waveform | +|-----------------|----------|-------------------|---------------------------------|-------------------|----------------|----------------------------------------------| +| OOK-4 | | -14.06 | 48 | 13 | 2.61 | OOK-4 | +| OOK-4 | | -12.06 | 8 | 13 | 4.86 | OOK-4 | +| OOK-4 | | -9.56 | 8 | 13 | 9.72 | OOK-4 | +| OOK-4 | | -9.36 | 48 | 13 | 13.05 | OOK-4 with repetition | +| OOK-4 | | -7.56 | 48 | 13 | 10.44 | OOK-1 | +| OOK-4 | | -7.56 | 1 | 13 | 17.28 | sequence based LPWUS (OOK-1) | +| OOK-4 | | -7.56 | 1 | 13 | 26.1 | OOK-4 with repetition | +| OOK-4 | | -6.56 | 8 | 13 | 19.44 | OOK-1 | +| OOK-4 | | -4.56 | 1 | 13 | 60.48 | sequence based LPWUS (OOK-1) | +| OOK-4 | | -3.56 | 8 | 13 | 77.76 | OOK-4 with repetition | +| OOK-4 | | -3.06 | 1 | 13 | 120.96 | sequence based LPWUS (OOK-1) | +| OOK-4 | | -0.96 | 1 | 13 | 241.92 | sequence based LPWUS (OOK-1) | +| OOK-4 | | -0.26 | 1 | 13 | 302.4 | sequence based LPWUS (OOK-1) | +| OOK-4 | | 1.94 | 1 | 13 | 604.8 | sequence based LPWUS (OOK-1) with repetition | +| OOK-4 | | -12.13 | 48 | 15 | 2.16 | OOK-4 | +| OOK-4 | | -11.63 | 48 | 15 | 2.16 | OOK-2 | +| OOK-4 | | -11.53 | 48 | 15 | 2.16 | OOK-2 | +| OOK-4 | | -11.43 | 48 | 15 | 2.16 | OOK-2 | +| OOK-4 | | -9.53 | 48 | 15 | 2.16 | OOK-4 with concentrated waveform | +| OOK-4 | | -8.12 | 48 | 15 | 2.16 | OOK-FSK joint Modulation | +| OOK-4 | | -7.63 | 48 | 15 | 2.16 | OOK-4 | +| OOK-4 | | -7.44 | 48 | 15 | 2.16 | OOK-FSK joint Modulation | +| OOK-4 | | -7.43 | 48 | 15 | 2.16 | OOK-4 | +| OOK-4 | | -7.3 | 48 | 15 | 2.16 | OOK-FSK joint Modulation | +| OOK-4 | | -7.03 | 48 | 15 | 2.16 | OOK-4 with concentrated waveform | +| OOK-4 | | -3.93 | 48 | 15 | 8.64 | OOK-4 | +| OOK-4 | | -2.83 | 48 | 15 | 4.32 | OOK-4 | +| OOK-4 | | -2.63 | 48 | 15 | 8.64 | OOK-2 | +| OOK-4 | | -0.93 | 48 | 15 | 8.64 | OOK-4 | +| OOK-4 | | -4.64 | 1 | 12 | 8.64 | OOK-1 | +| OOK-4 | | -4.54 | 1 | 12 | 4.32 | OOK-4 | +| OOK-4 | | -2.94 | 1 | 12 | 17.28 | OOK-1 | +| OOK-4 | | -2.14 | 1 | 12 | 8.64 | OOK-4 | +| OOK-4 | | 0.06 | 1 | 12 | 17.28 | OOK-4 | +| OOK-4 | | 0.06 | 1 | 12 | 43.2 | OOK-1 | +| OOK-4 | | 0.26 | 1 | 12 | 69.12 | OOK-1 | +| OOK-4 | | 0.76 | 1 | 12 | 34.56 | OOK-4 | +| OOK-4 | | 2.36 | 1 | 12 | 30.24 | OOK-4 | +| OOK-4 | | 2.36 | 1 | 12 | 77.76 | OOK-1 | +| OOK-4 | | 2.36 | 1 | 12 | 138.24 | OOK-1 | +| OOK-4 | | 2.46 | 1 | 12 | 60.48 | OOK-4 | +| OOK-4 | | -1.52 | 4 | 15 | 6.48 | OOK-1 | +| OOK-4 | | -1.26 | 4 | 15 | 6.48 | OOK-1 | +| OOK-4 | | 1.72 | 4 | 15 | 3.24 | OOK-1 | +| OOK-4 | | 3.23 | 4 | 15 | 3.24 | OOK-4 | +| OOK-4 | | 3.91 | 4 | 15 | 6.48 | OOK-1 | +| OOK-4 | | 4.6 | 4 | 15 | 6.48 | OOK-1 | +| OOK-4 | | 6.03 | 4 | 15 | 12.96 | OOK-1 | +| OOK-4 | | 6.15 | 4 | 15 | 6.48 | OOK-4 | +| OOK-4 | | 6.5 | 4 | 15 | 12.96 | OOK-1 | +| OOK-4 | | 6.66 | 4 | 15 | 6.48 | OOK-4 | +| OOK-4 | | 7.29 | 4 | 15 | 6.48 | OOK-4 | +| OOK-4 | | 7.96 | 4 | 15 | 12.96 | OOK-4 | +| OOK-4 | | 8.73 | 4 | 15 | 12.96 | OOK-4 | + +Bar chart and data table showing performance metrics for various OOK waveforms. The chart displays 'Average:Gap w/ PUSCH Msg3' on the y-axis (ranging from -20 to 5) against different waveform configurations on the x-axis. The table below provides detailed metrics including number of repetitions, bits per symbol, noise figure, and info bits for each waveform. + +![Bar chart titled 'Average Gap w/ PUSCH Msg3' showing MIL margin (Y) in dB for various scenarios. The chart includes a data table below the bars with columns for waveform family, scenario, per bit resource, noise figure, and number of info bits. Scenarios are grouped into [8A-11], [8A-13], [8A-14], [8A-16], [8A-2], and [8A-11](2).](28eba83fac6219415e57d8d2d5f37a2b_img.jpg) + +The figure is a bar chart titled 'Average Gap w/ PUSCH Msg3' showing the MIL margin (Y) in dB for various scenarios. The y-axis ranges from -10 to 6 dB. The x-axis lists scenarios categorized into groups: [8A-11], [8A-13], [8A-14], [8A-16], [8A-2], and [8A-11](2). Each scenario is represented by a blue bar with its value labeled on top. Below the chart is a data table with the following columns: Waveform family, Scenario, per bit resource (MHz\*Symbol/bit), Noise figure (dB), # of info bits, and Waveform. + +| Waveform family | Scenario | per bit resource (MHz*Symbol/bit) | Noise figure (dB) | # of info bits | Waveform | +|-----------------|----------|-----------------------------------|-------------------|----------------|----------| +| OOK-4, p=3 dB | [8A-11] | 12 | 0.9 | 0.68 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 8 | 1.08 | 1.07 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 8 | 1.8 | 1.59 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 12 | 2.7 | 1.91 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 12 | 1.8 | 2.2 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 12 | 1.68 | 2.24 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 12 | 2.52 | 2.24 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 8 | 4.32 | 2.52 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 12 | 8.64 | 3.01 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 12 | 3.78 | 4.96 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 12 | 7.2 | 6.44 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 12 | 17.28 | 6.47 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 8 | 10.8 | 6.47 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 12 | 8.64 | 6.63 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 12 | 30.24 | 6.65 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 12 | 20.16 | 7.69 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 12 | 14.4 | 8.2 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 12 | 21.6 | 8.22 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 8 | 17.28 | 8.25 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 24 | 2.88 | 8.38 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 8 | 4.32 | 0.78 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 24 | 5.76 | 1.45 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 8 | 8.64 | 4.97 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 20 | 3.24 | 5.78 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 20 | 3.46 | 1.24 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 20 | 3.02 | 3.52 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 6 | 5.76 | 5.6 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 6 | 2.88 | -1.84 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 6 | 11.52 | 0.16 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 6 | 5.76 | 0.16 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 6 | 23.04 | 2.16 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 6 | 92.16 | 6.16 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 6 | 4.32 | 6.16 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 8 | 4.32 | -8.35 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 8 | 4.32 | -5.34 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 8 | 4.32 | -3.61 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 8 | 8.64 | -2.95 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 8 | 4.32 | -0.61 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 8 | 8.64 | 0.06 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 8 | 8.64 | 1.79 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 8 | 8.64 | 4.79 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 12 | 0.9 | -3.32 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 8 | 1.08 | -2.93 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 12 | 1.8 | -2.41 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 12 | 2.7 | -2.09 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 12 | 1.8 | -1.8 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 12 | 1.68 | -1.76 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 12 | 2.52 | -1.76 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 8 | 2.16 | -1.48 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 1 | 4.32 | -0.99 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 1 | 8.64 | 0.96 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 32 | 3.78 | 2.44 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 12 | 7.2 | 2.47 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 1 | 17.28 | 2.47 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 8 | 10.8 | 2.63 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 8 | 8.64 | 2.65 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 1 | 30.24 | 3.69 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 12 | 20.16 | 4.2 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 12 | 14.4 | 4.22 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 8 | 21.6 | 4.25 | OOK-4 | +| OOK-4, p=3 dB | [8A-11] | 8 | 17.28 | 4.38 | OOK-4 | + +Bar chart titled 'Average Gap w/ PUSCH Msg3' showing MIL margin (Y) in dB for various scenarios. The chart includes a data table below the bars with columns for waveform family, scenario, per bit resource, noise figure, and number of info bits. Scenarios are grouped into [8A-11], [8A-13], [8A-14], [8A-16], [8A-2], and [8A-11](2). + +**Observation:** + +For Redcap UE in Urban, [8A-2], [8A-3], [8A-5], [8A-7], [8A-8], [8A-11], [8A-13], [8A-14] and [8A-16] show OOK based LP-WUS is feasible to achieve comparable MIL (i.e.MIL margin $Y \geq -1\text{dB}$ ) than PUSCH for Msg.3 + +- [8A-2], [8A-5], [8A-8], [8A-11], [8A-13] and [8A-16] show that, with LP-WUS resource $X=1.8 \sim 8.64 \text{ MHz} \cdot \text{Symbol/bit}$ , MIL margin $Y = -0.93\text{dB} \sim 2.2\text{dB}$ , assuming no power boosting for LP-WUS +- [8A-7] show that with LP-WUS resource $X=17.28 \text{ MHz} \cdot \text{Symbol/bit}$ , MIL margin $Y=0.06\text{dB}$ , assuming no power boosting for LP-WUS, assumes antenna element gain of LP-WUR is 3dB worse than MR. +- [8A-3] show that with LP-WUS resource $X=241.92 \text{ MHz} \cdot \text{Symbol/bit}$ , MIL margin $Y=-0.96\text{dB}$ , assuming no power boosting for LP-WUS and 4dB HARQ gain from 2 retransmissions for Msg3 PUSCH. +- [8A-2], [8A-11] and [8A-14] show that with LP-WUS resource $X=0.9 \sim 4.32 \text{ MHz} \cdot \text{Symbol/bit}$ , MIL margin $Y=-0.61\text{dB} \sim 1.24\text{dB}$ , assuming 3dB power boosting for LP-WUS. + +### 8.2.2.5 FSK, Urban, Normal UE, PDCCH + +Table 8.2.2.5-1: Gap with PDCCH AL16, 4RX + +![Bar chart and data table showing the gap with PDCCH AL16, 4RX for various FSK configurations. The chart shows negative values for most configurations, indicating a power saving gap. The table below provides the specific parameters for each bar.](e2ddd0f0705e7e69df4ffa6380e1b1ed_img.jpg) + +Average:Gap w/ AL16,4Rx + +| FSK-1 | FSK-1, p=3 dB | FSK-1 | FSK-1 | FSK-1, p=3 dB | FSK-1, p=3 dB | FSK-1 | FSK-1, p=3 dB | FSK-1 | FSK-2 | FSK-1 or FSK-2 | FSK-1 or FSK-2 | FSK-1 | FSK-1 | FSK-1 | FSK-1 | FSK-1 | +|--------|---------------|--------|--------|---------------|---------------|--------|---------------|--------|--------|----------------|----------------|--------|--------|--------|-------|--------| +| 8 | 8 | 8 | 8 | 8 | 8 | 8 | 8 | 8 | 8 | 48 | 8 | 1 | 1 | 1 | 1 | 1 | +| 20 | 20 | 15 | 20 | 15 | 20 | 15 | 15 | 13 | 13 | 13 | 13 | 12 | 12 | 12 | 12 | 12 | +| 4.32 | 4.32 | 4.32 | 4.32 | 4.32 | 4.32 | 4.32 | 4.32 | 4.86 | 4.86 | 5.22 | 9.72 | 8.64 | 25.92 | 34.56 | 51.84 | 138.24 | +| -22.32 | -19.31 | -17.58 | -16.02 | -14.58 | -13.01 | -11.28 | -8.28 | -26.79 | -23.79 | -21.09 | -19.79 | -15.42 | -12.04 | -11.86 | | -8.52 | +| [8A-2] | | | | | | | | [8A-3] | | | [8A-7] | | | | | | + +Bar chart and data table showing the gap with PDCCH AL16, 4RX for various FSK configurations. The chart shows negative values for most configurations, indicating a power saving gap. The table below provides the specific parameters for each bar. + +#### Observation: + +For normal UE and Urban scenario, comparing MIL of FSK based LP-WUS to legacy PDCCH AL16, 4Rx for paging + +- [8A-2], [8A-3] and [8A-7] show that with the LP-WUS resource of X=4.32~51.84 MHz\*Symbol/bit , the MIL margin Y is -19.79~-5.52 dB + +**Table 8.2.2.5-2: Gap with PDCCH AL8, 4RX** + +![Bar chart showing Average Gap w/ AL8, 4Rx for various FSK configurations. The Y-axis ranges from -30 to 0 dB. The X-axis shows different FSK-1 and FSK-2 configurations with their respective per bit resource, noise figure, and number of info bits. The gap values are: -24.09, -21.09, -18.39, -17.09, -12.92, -9.54, -9.36, -6.02, -6.02 dB.](8c9229031a956b18d984fe72daa442c8_img.jpg) + +| FSK-1 | FSK-2 | FSK-1 or FSK-2 | FSK-1 or FSK-2 | FSK-1 | FSK-1 | FSK-1 | FSK-1 | FSK-1 | +|--------|--------|----------------|----------------|--------|-------|--------|-------|--------| +| 8 | 8 | 48 | 8 | 1 | 1 | 1 | 1 | 1 | +| 13 | 13 | 13 | 13 | 12 | 12 | 12 | 12 | 12 | +| 4.86 | 4.86 | 5.22 | 9.72 | 8.64 | 25.92 | 34.56 | 51.84 | 138.24 | +| -24.09 | -21.09 | -18.39 | -17.09 | -12.92 | -9.54 | -9.36 | -6.02 | -6.02 | +| | | [8A-3] | | | | [8A-7] | | | + +Bar chart showing Average Gap w/ AL8, 4Rx for various FSK configurations. The Y-axis ranges from -30 to 0 dB. The X-axis shows different FSK-1 and FSK-2 configurations with their respective per bit resource, noise figure, and number of info bits. The gap values are: -24.09, -21.09, -18.39, -17.09, -12.92, -9.54, -9.36, -6.02, -6.02 dB. + +**Observation:** + +For normal UE and Urban scenario, comparing MIL of FSK based LP-WUS to legacy PDCCH AL8, 4Rx for paging + +- [8A-3] and [8A-7] show that with the LP-WUS resource of X=9.72~51.84 MHz\*Symbol/bit , the MIL margin Y is -17.09~-6.02 dB + +Table 8.2.2.5-3: Gap with PDCCH AL8, 2RX + +![Bar chart showing Average Gap w/ AL8, 2Rx for various FSK scenarios. The chart includes five bars with values -21.09, -18.09, -15.39, -14.09, and -24.14. Below the chart is a table with columns for FSK-1, FSK-2, FSK-1 or FSK-2, and FSK-1, containing parameters like per bit resource, noise figure, and number of info bits.](cbb007765df371cbaa0dfd8596fce353_img.jpg) + +Average Gap w/ AL8, 2Rx + +| FSK-1 | FSK-2 | FSK-1 or FSK-2 | FSK-1 or FSK-2 | FSK-1 | +|--------|--------|----------------|----------------|--------| +| 8 | 8 | 48 | 8 | 48 | +| 13 | 13 | 13 | 13 | 15 | +| 4.86 | 4.86 | 5.22 | 9.72 | 0.72 | +| -21.09 | -18.09 | -15.39 | -14.09 | -24.14 | + +[8A-3] [8A-9] + +Bar chart showing Average Gap w/ AL8, 2Rx for various FSK scenarios. The chart includes five bars with values -21.09, -18.09, -15.39, -14.09, and -24.14. Below the chart is a table with columns for FSK-1, FSK-2, FSK-1 or FSK-2, and FSK-1, containing parameters like per bit resource, noise figure, and number of info bits. + +**Observation:** + +For normal UE and Urban scenario, comparing MIL of FSK based LP-WUS to legacy PDCCH AL8, 2Rx for paging + +- [8A-3] and [8A-9] show that with the LP-WUS resource of X=0.72~9.72 MHz\*Symbol/bit , the MIL margin Y is -24.14~-14.09 dB + +### 8.2.2.6 FSK, Urban, Redcap UE, PDCCH + +Table 8.2.2.6-1: Gap with PDCCH AL16, 1RX + +![Bar chart and data table showing the gap with PDCCH AL16, 1RX for various FSK configurations. The chart shows MIL margin values for different scenarios, with a table below providing detailed parameters for each bar.](a0ef559f2bd4147ec203cff042d7369a_img.jpg) + +Average: Gap w/ AL16, 1RX + +| [8A-2] | | | | | | | | [8A-3] | | | | [8A-7] | | | | | +|--------|--------------------|-------|-------|--------------------|--------------------|-------|--------------------|--------|--------|----------------|----------------|--------|-------|-------|-------|--------| +| FSK-1 | FSK-1, $\rho=3$ dB | FSK-1 | FSK-1 | FSK-1, $\rho=3$ dB | FSK-1, $\rho=3$ dB | FSK-1 | FSK-1, $\rho=3$ dB | FSK-1 | FSK-2 | FSK-1 or FSK-2 | FSK-1 or FSK-2 | FSK-1 | FSK-1 | FSK-1 | FSK-1 | FSK-1 | +| 8 | 8 | 8 | 8 | 8 | 8 | 8 | 8 | 8 | 8 | 48 | 8 | 1 | 1 | 1 | 1 | 1 | +| 20 | 20 | 15 | 20 | 15 | 20 | 15 | 15 | 13 | 13 | 13 | 13 | 12 | 12 | 12 | 12 | 12 | +| 4.32 | 4.32 | 4.32 | 4.32 | 4.32 | 4.32 | 4.32 | 4.32 | 4.86 | 4.86 | 5.22 | 9.72 | 8.64 | 25.92 | 34.56 | 51.84 | 138.24 | +| -8.12 | -5.11 | -3.38 | -1.82 | -0.38 | 1.19 | 2.92 | 5.92 | -20.59 | -17.59 | -14.89 | -13.59 | -9.22 | -5.84 | -5.66 | -2.32 | -2.32 | + +Bar chart and data table showing the gap with PDCCH AL16, 1RX for various FSK configurations. The chart shows MIL margin values for different scenarios, with a table below providing detailed parameters for each bar. + +**Observation:** + +For RedCap UE and Urban scenario, comparing MIL of FSK based LP-WUS to legacy PDCCH AL16, 1Rx for paging + +- [8A-2] show it is feasible to achieve comparable MIL (i.e.MIL margin $Y \geq -1$ dB) with LP-WUS resource $X=4.32$ MHz\*Symbol/bit, MIL margin $Y=2.92$ dB +- [8A-3] and [8A-7] show that with the LP-WUS resource of $X=9.72 \sim 51.84$ MHz\*Symbol/bit , the MIL margin $Y$ is $-13.59 \sim -2.32$ dB + +**Table 8.2.2.6-2: Gap with PDCCH AL8, 1RX** + +![Bar chart showing the gap with PDCCH AL8, 1RX for various FSK configurations. The Y-axis represents the gap in dB, ranging from -20 to 10. The X-axis lists different FSK-1 and FSK-2 configurations. The data is as follows: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FSK-1FSK-1, p=3 dBFSK-1FSK-1FSK-1, p=3 dBFSK-1, p=3 dBFSK-1FSK-1, p=3 dBFSK-1FSK-2FSK-1 or FSK-2FSK-1 or FSK-2FSK-1FSK-1FSK-1FSK-1FSK-1
888888888848811111
2020152015201515131313131212121212
4.324.324.324.324.324.324.324.324.864.865.229.728.6425.9234.5651.84138.24
-6.42-3.41-1.68-0.121.322.894.627.62-17.89-14.89-12.19-10.89-6.72-3.34-3.160.180.18
[8A-2][8A-3][8A-7]
+

+ +
ρ=3 dB | OOK-4,
ρ=3 dB | OOK-4,
ρ=3 dB | OOK-4,
ρ=3 dB | OOK-4 | OOK-4 | OOK-4 | OOK-4 | OOK-4 | OOK-4 | OOK-4 | OOK-4 | OOK-4 | OOK-4 | OOK-4 | OOK-4 | OOK-4 | OOK-4 | OOK-4 | OOK-4 | OOK-4 | OOK-4 | OOK-4 | OOK-4 | OOK-4 | OOK-1,
ρ=3 dB | OOK-1,
ρ=3 dB | OOK-1,
ρ=3 dB | +| 12 | 8 | 12 | 8 | 12 | 8 | 8 | 12 | 1 | 1 | 1 | 12 | 8 | 12 | 8 | 1 | 12 | 1 | 12 | 8 | 8 | 24 | 8 | 24 | 8 | 20 | 20 | 20 | +| 12 | 12 | 12 | 12 | 12 | 12 | 12 | 12 | 12 | 12 | 12 | 12 | 12 | 12 | 12 | 12 | 12 | 12 | 12 | 12 | 12 | 12 | 12 | 12 | 12 | 12 | 12 | 12 | +| 0.9 | 1.08 | 1.26 | 1.35 | 1.8 | 2.16 | 2.7 | 2.52 | 4.32 | 8.64 | 17.28 | 28.8 | 34.56 | 40.32 | 43.2 | 120.96 | 80.64 | 138.24 | 57.6 | 86.4 | 69.12 | 2.88 | 4.32 | 46.08 | 69.12 | 3.24 | 3.46 | 3.02 | +| -9.21 | -8.92 | -8.59 | -8.49 | -7.65 | -7.38 | -7.29 | -7.11 | -6.45 | -4.57 | -2.86 | 0.09 | 0.25 | 0.33 | 0.45 | 1.05 | 1.4 | 1.43 | 1.45 | 1.51 | 1.71 | -10.06 | -9.5 | -0.25 | 0.88 | -18.52 | -15.2 | -13.52 | + +Bar chart and data table showing performance gaps for OOK variants compared to AL8, 2Rx. The chart shows values ranging from -18.52 to 1.71. The table below provides detailed parameters for each variant. + +**Observation:** + +For normal UE and Rural scenario, comparing MIL of OOK based LP-WUS to legacy PDCCH AL8, 2Rx for paging + +- [8A-11] and [8A-13] show that it is feasible to achieve comparable MIL (i.e. MIL margin $\geq -1\text{dB}$ ) when LP-WUS resource $X=28.8\sim 46.08\text{ MHz}\cdot\text{Symbol/bit}$ , MIL margin $Y=-0.25\sim 0.09\text{dB}$ +- [8A-14] shows that with the LP-WUS resource of $X=3.02\text{ MHz}\cdot\text{Symbol/bit}$ , the MIL margin $Y$ is $-13.52\text{ dB}$ + +### 8.2.3.2 OOK, Rural, Redcap UE, PDCCH + +#### Gap with AL16, 1Rx + +Table 8.2.3.2-1: Gap with AL16, 1Rx, OOK, Rural, normal UE, PDCCH + +![A bar chart and data table showing the gap with AL16, 1Rx for various OOK configurations. The chart displays MIL margin values for different scenarios, with a detailed data table below it.](60e76fd7ce476eeef8a30381323fb97c_img.jpg) + +The figure is a bar chart titled 'Average: Gap w/ AL16, 1RX'. The y-axis represents the MIL margin in dB, ranging from -20 to 5. The x-axis lists various OOK configurations. The bars show the following MIL margin values (in dB): -9.2, -8.91, -8.58, -8.48, -7.64, -7.37, -7.28, -7.1, -6.44, -4.56, -3.24, -3.05, -3.02, -2.85, -2.79, -1.84, -1.58, -1.4, -1.21, -1.08, -17.87, -14.55, -12.87, -14.08, -14.08, -8.08, -4.08, 1.92, 1.92, -5.8, -2.3. + +| Scenario | OOK-4, p=3 dB | OOK-4 | OOK-1, p=3 dB | sequence based LPWUS (OOK-1) | +|----------|---------------|-------|---------------|------------------------------| +| [8A-11] | 12 | 12 | 0.9 | -9.2 | +| [8A-14] | 20 | 12 | 3.24 | -17.87 | +| [8A-16] | 6 | 15 | 0.72 | -14.08 | +| [8A-3] | 8 | 13 | 19.44 | -5.8 | + +A bar chart and data table showing the gap with AL16, 1Rx for various OOK configurations. The chart displays MIL margin values for different scenarios, with a detailed data table below it. + +#### Observation: + +For RedCap UE and Rural scenario, comparing MIL of OOK based LP-WUS to legacy PDCCH AL16, 1Rx for paging + +- [8A-16] shows that it is feasible to achieve comparable MIL (i.e. MIL margin $\geq -1\text{dB}$ ) when LP-WUS resource $X=46.08\text{ MHz}\cdot\text{Symbol/bit}$ , MIL margin $Y=1.92\text{dB}$ + +- [8A-3], [8A-11] and [8A-14] show that with the LP-WUS resource of X=3.02~120.96 MHz\*Symbol/bit, the MIL margin Y is -12.87~-1.08 dB + +**Gap with AL8, 1Rx** + +**Table 8.2.3.2-2: Gap with AL8, 1Rx, OOK, Rural, normal UE, PDCCH** + +![Bar chart and data table showing the Gap with AL8, 1Rx for various OOK configurations. The chart shows MIL margin in dB for different scenarios, with values ranging from -14.08 dB to 1.62 dB. The table below provides detailed parameters for each scenario.](71e280cefea925145ac0bf9a48da8637_img.jpg) + +**Average:Gap w/ AL8, 1Rx** + +| Scenario | OOK-4, p=3 dB | OOK-4 | OOK-1, p=3 dB | +|----------|---------------|-------|---------------| +| 12 | 8 | 12 | 20 | +| 12 | 12 | 12 | 12 | +| 0.9 | 1.08 | 1.26 | 1.35 | +| 1.8 | 2.16 | 2.7 | 2.52 | +| 4.32 | 8.64 | 7.2 | 8.64 | +| 3.78 | 17.28 | 10.8 | 30.24 | +| 14.4 | 17.28 | 20.16 | 21.6 | +| 2.88 | 4.32 | 11.52 | 17.28 | +| 3.24 | 3.46 | 3.02 | | + +**MIL Margin (dB) Data:** + +- 6.5, -6.21, -5.88, -5.78, -4.94, -4.67, -4.58, -4.4, -3.74, -1.86, -0.54, -0.35, -0.32, -0.15, -0.09, 0.86, 1.12, 1.3, 1.49, 1.62, -6.52, -5.96, -0.62, 0.29, -14.08, -10.76, -9.08 + +Bar chart and data table showing the Gap with AL8, 1Rx for various OOK configurations. The chart shows MIL margin in dB for different scenarios, with values ranging from -14.08 dB to 1.62 dB. The table below provides detailed parameters for each scenario. + +**Observation:** + +For RedCap UE and Rural scenario, comparing MIL of OOK based LP-WUS to legacy PDCCH AL8, 1Rx for paging + +- [8A-11] and [8A-13] show that it is feasible to achieve comparable MIL (i.e. MIL margin $\geq -1$ dB) when LP-WUS resource X=3.78~11.52 MHz\*Symbol/bit, MIL margin Y=-0.62dB~-0.32dB +- [8A-14] shows that with the LP-WUS resource of X=3.02 MHz\*Symbol/bit, the MIL margin Y is -9.08 dB + +### 8.2.3.3 OOK, Rural, Normal UE, Msg.3 + +Table 8.2.3.3: OOK, Rural, Normal UE, Msg.3 + +![Bar chart and data table showing Average Gap w/ PUSCH Msg3 for various OOK configurations. The chart shows MIL margin in dB for different resource allocations and waveform types. The table below provides detailed parameters for each bar.](8e73cd115c6601092abc41abdf7d6772_img.jpg) + +Average: Gap w/ PUSCH Msg3 + +| Scenario | Waveform | Power Boosting (dB) | Bandwidth (MHz) | Symbol Rate (Symbol/bit) | MIL Margin (dB) | +|----------|----------------------------------|---------------------|-----------------|--------------------------|-----------------| +| [8A-11] | OOK-4, p=3 dB | 12 | 12 | 0.9 | -0.49 | +| | OOK-4, p=3 dB | 8 | 12 | 1.08 | -0.2 | +| | OOK-4, p=3 dB | 12 | 12 | 1.26 | 0.13 | +| | OOK-4, p=3 dB | 8 | 12 | 1.35 | 0.23 | +| | OOK-4 | 12 | 12 | 1.8 | 1.07 | +| | OOK-4 | 8 | 12 | 2.16 | 1.34 | +| | OOK-4 | 8 | 12 | 2.7 | 1.43 | +| | OOK-4 | 12 | 12 | 2.52 | 1.61 | +| | OOK-4 | 1 | 12 | 4.32 | 2.27 | +| | OOK-4 | 1 | 12 | 8.64 | 4.15 | +| | OOK-4 | 12 | 12 | 17.28 | 5.86 | +| | OOK-4 | 8 | 12 | 28.8 | 8.81 | +| | OOK-4 | 12 | 12 | 34.56 | 8.97 | +| | OOK-4 | 8 | 12 | 40.32 | 9.05 | +| [8A-13] | OOK-4 | 12 | 12 | 43.2 | 9.17 | +| | OOK-4 | 1 | 12 | 120.96 | 9.77 | +| | OOK-4 | 12 | 12 | 80.64 | 10.12 | +| | OOK-4 | 1 | 12 | 138.24 | 10.15 | +| | OOK-4 | 12 | 12 | 57.6 | 10.17 | +| | OOK-4 | 8 | 12 | 86.4 | 10.23 | +| | OOK-4 | 8 | 12 | 69.12 | 10.43 | +| | OOK-4 | 24 | 12 | 2.88 | 4.71 | +| | OOK-4 | 8 | 12 | 4.32 | 5.27 | +| | OOK-4 | 24 | 12 | 46.08 | 14.52 | +| | OOK-4 | 8 | 12 | 69.12 | 15.65 | +| | OOK-1, p=3 dB | 20 | 12 | 3.24 | -5.04 | +| | OOK-1, p=3 dB | 20 | 12 | 3.46 | -1.72 | +| | OOK-1, p=3 dB | 20 | 12 | 3.02 | -0.04 | +| [8A-14] | sequence based LPWUS (OOK-1) | 8 | 13 | 19.44 | -1.94 | +| | sequence based LPWUS (OOK-1) | 1 | 13 | 120.96 | 1.56 | +| | OOK-2 | 48 | 15 | 2.16 | -10.97 | +| | OOK-4 | 48 | 15 | 2.16 | -7.07 | +| [8A-5] | OOK-4 | 48 | 15 | 2.16 | -6.74 | +| | OOK-4 | 48 | 15 | 2.16 | -6.47 | +| | OOK-4 with concentrated waveform | 48 | 15 | 8.64 | -3.37 | +| | OOK-4 | 48 | 15 | 4.32 | -2.27 | +| | OOK-2 | 48 | 15 | 8.64 | -2.07 | +| | OOK-4 | 48 | 15 | 8.64 | -0.37 | +| | OOK-3 | 4 | 12 | 4.32 | -5.63 | +| | OOK-3 | 4 | 12 | 4.32 | -4.63 | +| | OOK-2 | 4 | 12 | 4.32 | 7.37 | +| | OOK-4 | 4 | 12 | 4.32 | 11.57 | +| [8A-6] | OOK-1 | 4 | 12 | 4.32 | 14.37 | +| | OOK-1 | 4 | 12 | 4.32 | 15.37 | +| | OOK-1 | 4 | 12 | 4.32 | 15.37 | + +Bar chart and data table showing Average Gap w/ PUSCH Msg3 for various OOK configurations. The chart shows MIL margin in dB for different resource allocations and waveform types. The table below provides detailed parameters for each bar. + +#### Observation: + +For Normal UE in Rural, based on the results, [8A-3], [8A-5], [8A-6], [8A-11], [8A-13] and [8A-14] show OOK based LP-WUS is feasible to achieve comparable MIL (i.e. MIL margin $Y \geq -1\text{dB}$ ) than MSG3 PUSCH, + +- [8A-5], [8A-6], [8A-11] and [8A-13] show that with LP-WUS resource $X=1.8 \sim 8.64 \text{ MHz} \cdot \text{Symbol/bit}$ , MIL margin $Y=-0.37\text{dB} \sim 11.57\text{dB}$ +- [8A-11] and [8A-14] show that with LP-WUS resource $X=0.9 \sim 3.02 \text{ MHz} \cdot \text{Symbol/bit}$ , MIL margin $Y=-0.49\text{dB} \sim -0.04\text{dB}$ , assuming 3dB power boosting for LP-WUS. +- [8A-3] shows that with LP-WUS resource $X=120.96 \text{ MHz} \cdot \text{Symbol/bit}$ , MIL margin $Y=1.56\text{dB}$ , assuming 4dB HARQ gain from 2 retransmissions for Msg3 PUSCH. + +### 8.2.3.4 OOK, Rural, Redcap UE, Msg.3 + +Table 8.2.3.4: OOK, Rural, Redcap UE, Msg.3 + +![Bar chart showing Average Gap w/ PUSCH Msg3 for various OOK configurations. The chart includes a data table at the bottom with columns for waveform family, per bit resource, noise figure, # of info bits, and waveform.](1ecdc32fbc05ff26a3181147d0c3ba29_img.jpg) + +Average Gap w/ PUSCH Msg3 + +| Waveform family | Scenario | Gap w/ PUSCH Msg3 (dB) | per bit resource (MHz*symbol/bit) | Noise figure (dB) | # of info bits | Waveform | +|----------------------------------|----------|------------------------|-----------------------------------|-------------------|----------------|----------| +| OOK-4 | p=3 dB | -0.49 | 12 | 12 | 0.9 | [8A-11] | +| OOK-4 | p=3 dB | -0.2 | 8 | 12 | 1.08 | [8A-11] | +| OOK-4 | p=3 dB | 0.13 | 12 | 12 | 1.26 | [8A-11] | +| OOK-4 | p=3 dB | 0.23 | 8 | 12 | 1.35 | [8A-11] | +| OOK-4 | | 1.07 | 12 | 12 | 1.8 | [8A-11] | +| OOK-4 | | 1.34 | 8 | 12 | 2.16 | [8A-11] | +| OOK-4 | | 1.43 | 8 | 12 | 2.7 | [8A-11] | +| OOK-4 | | 1.61 | 12 | 12 | 2.52 | [8A-11] | +| OOK-4 | | 2.27 | 1 | 12 | 4.32 | [8A-11] | +| OOK-4 | | 4.15 | 1 | 12 | 8.64 | [8A-11] | +| OOK-4 | | 5.47 | 12 | 12 | 7.2 | [8A-11] | +| OOK-4 | | 5.66 | 8 | 12 | 8.64 | [8A-11] | +| OOK-4 | | 5.69 | 32 | 12 | 3.78 | [8A-11] | +| OOK-4 | | 5.86 | 1 | 12 | 17.28 | [8A-11] | +| OOK-4 | | 5.92 | 8 | 12 | 10.8 | [8A-11] | +| OOK-4 | | 6.87 | 1 | 12 | 30.24 | [8A-11] | +| OOK-4 | | 7.13 | 12 | 12 | 14.4 | [8A-11] | +| OOK-4 | | 7.31 | 8 | 12 | 17.28 | [8A-11] | +| OOK-4 | | 7.5 | 12 | 12 | 20.16 | [8A-11] | +| OOK-4 | | 7.63 | 8 | 12 | 21.6 | [8A-11] | +| OOK-4 | | 4.71 | 24 | 12 | 2.88 | [8A-11] | +| OOK-4 | | 5.27 | 8 | 12 | 4.32 | [8A-11] | +| OOK-4 | | 10.61 | 24 | 12 | 11.52 | [8A-11] | +| OOK-4 | | 11.52 | 8 | 12 | 17.28 | [8A-11] | +| OOK-1 | p=3 dB | -5.04 | 20 | 12 | 3.24 | [8A-14] | +| OOK-1 | p=3 dB | -1.72 | 20 | 12 | 3.46 | [8A-14] | +| OOK-1 | p=3 dB | -0.04 | 20 | 12 | 3.02 | [8A-14] | +| OOK-4 | | 0.65 | 6 | 15 | 0.72 | [8A-16] | +| OOK-4 | | 0.65 | 6 | 15 | 0.18 | [8A-16] | +| OOK-4 | | 6.65 | 6 | 15 | 5.76 | [8A-16] | +| OOK-4 | | 10.65 | 6 | 15 | 5.76 | [8A-16] | +| OOK-4 | | 16.65 | 6 | 15 | 46.08 | [8A-16] | +| OOK-4 | | 16.65 | 6 | 15 | 184.32 | [8A-16] | +| sequence based (PWUS OOK-1) | | -1.94 | 8 | 13 | 19.44 | [8A-3] | +| sequence based (PWUS OOK-1) | | 1.56 | 1 | 13 | 120.96 | [8A-3] | +| OOK-2 | | -10.97 | 48 | 15 | 2.16 | [8A-5] | +| OOK-4 | | -7.07 | 48 | 15 | 2.16 | [8A-5] | +| OOK-4 | | -6.74 | 48 | 15 | 2.16 | [8A-5] | +| OOK-4 | | -6.47 | 48 | 15 | 2.16 | [8A-5] | +| OOK-4 with concentrated waveform | | -3.37 | 48 | 15 | 8.64 | [8A-5] | +| OOK-4 | | -2.27 | 48 | 15 | 4.32 | [8A-5] | +| OOK-4 | | -2.07 | 48 | 15 | 8.64 | [8A-5] | +| OOK-2 | | -0.37 | 48 | 15 | 8.64 | [8A-5] | +| OOK-4 | | -0.37 | 48 | 15 | 8.64 | [8A-5] | + +Bar chart showing Average Gap w/ PUSCH Msg3 for various OOK configurations. The chart includes a data table at the bottom with columns for waveform family, per bit resource, noise figure, # of info bits, and waveform. + +#### Observation: + +For RedCap UE in Rural, based on the results, [8A-3], [8A-5], [8A-16], [8A-11], [8A-13] and [8A-14] show OOK based LP-WUS is feasible to achieve comparable MIL (i.e. MIL margin $Y \geq -1\text{dB}$ ) than MSG3 PUSCH, + +- [8A-5], [8A-11], [8A-13] and [8A-16] show that with LP-WUS resource $X = 0.18 \sim 8.64 \text{ MHz} \cdot \text{Symbol/bit}$ , MIL margin $Y = -0.37\text{dB} \sim 4.71\text{dB}$ , assuming no power boosting for LP-WUS +- [8A-11] and [8A-14] show that with LP-WUS resource $X = 0.9 \sim 3.02 \text{ MHz} \cdot \text{Symbol/bit}$ , MIL margin $Y = -0.49\text{dB} \sim -0.04\text{dB}$ , assuming 3dB power boosting for LP-WUS + +- [8A-3] shows that with LP-WUS resource $X=120.96 \text{ MHz} \cdot \text{Symbol/bit}$ , MIL margin $Y=1.56 \text{ dB}$ , assuming 4dB HARQ gain from 2 retransmissions for Msg3 PUSCH. + +#### 8.2.3.5 FSK, Rural, normal UE, PDCCH + +No input + +#### 8.2.3.6 FSK, Rural, Redcap UE, PDCCH + +No input + +### 8.2.3.7 FSK, Rural, Normal UE, Msg.3 + +Table 8.2.3.7: FSK, Rural, Normal UE, Msg.3 + +![Bar chart showing Average Gap w/ PUSCH Msg3 for various FSK configurations. The chart includes a data table at the bottom with columns for per bit resource, Noise figure, # of info bits, and Waveform.](625ccd1bc0767416d87b542a7fa16bba_img.jpg) + +Average Gap w/ PUSCH Msg3 + +| per bit resource (MHz*symbol/bit) | Noise figure (dB) | # of info bits | Waveform | Average Gap w/ PUSCH Msg3 | +|-----------------------------------|-------------------|----------------|----------|---------------------------| +| 2.16 | -10.87 | 15 | FSK-1 | -10.87 | +| 2.16 | -8.17 | 15 | FSK-2 | -8.17 | +| 4.32 | 0.13 | 15 | FSK-2 | 0.13 | +| 8.64 | 0.73 | 15 | FSK-2 | 0.73 | +| 8.64 | 3.03 | 15 | FSK-2 | 3.03 | + +[8A-5] + +Bar chart showing Average Gap w/ PUSCH Msg3 for various FSK configurations. The chart includes a data table at the bottom with columns for per bit resource, Noise figure, # of info bits, and Waveform. + +Observation: + +For normal UE and Rural scenario, [8A-5] shows FSK based LP-WUS is feasible to achieve comparable MIL (i.e. MIL margin $Y \geq -1\text{dB}$ ) than MSG3 PUSCH when + +- LP-WUS resource $X=4.32\text{MHz}\cdot\text{Symbol/bit}$ , MIL margin $Y=0.13\text{dB}$ + +### 8.2.3.8 FSK, Rural, Redcap UE, Msg.3 + +Table 8.2.3.8: FSK, Rural, Redcap UE, Msg.3 + +![Bar chart showing Average Gap w/ PUSCH Msg3 for various FSK configurations. The chart includes a data table at the bottom with columns for per bit resource, Noise figure, # of info bits, and Waveform.](fbd0e6c1cf946b0609a26529c031ae7f_img.jpg) + +Average Gap w/ PUSCH Msg3 + +| per bit resource (MHz*symbol/bit) | Noise figure (dB) | # of info bits | Waveform | Average Gap w/ PUSCH Msg3 | +|-----------------------------------|-------------------|----------------|----------|---------------------------| +| 2.16 | -10.87 | 15 | FSK-1 | -10.87 | +| 2.16 | -8.17 | 15 | FSK-2 | -8.17 | +| 4.32 | 0.13 | 15 | FSK-2 | 0.13 | +| 8.64 | 0.73 | 15 | FSK-2 | 0.73 | +| 8.64 | 3.03 | 15 | FSK-2 | 3.03 | + +[8A-5] + +Bar chart showing Average Gap w/ PUSCH Msg3 for various FSK configurations. The chart includes a data table at the bottom with columns for per bit resource, Noise figure, # of info bits, and Waveform. + +**Observation:** + +For RedCap UE and Rural scenario, [8A-5] shows FSK based LP-WUS is feasible to achieve comparable MIL (i.e. MIL margin $Y \geq -1\text{dB}$ ) than MSG3 PUSCH when + +- LP-WUS resource $X=4.32\text{MHz} \cdot \text{Symbol/bit}$ , MIL margin $Y=0.13\text{dB}$ + +### 8.2.3.9 OFDM, Rural, normal UE, PDCCH + +#### Gap with PDCCH AL16, 2Rx + +Table 8.2.3.9-1 Gap with PDCCH AL16, 2Rx + +![Bar chart and data table showing the gap with PDCCH AL16, 2Rx for various OFDM configurations. The chart shows negative values for each configuration, with the most significant gap at -7.59.](740849dde4b891055485e0c3eea8664a_img.jpg) + +Average:Gap w/ AL16, 2Rx + +| OFDM | OFDM | OFDM | OFDM | OFDM | OFDM | OFDM | OFDM | +|-------|------|-------|------|-------|-------|-------|-------| +| 12 | 8 | 12 | 8 | 12 | 8 | 12 | 8 | +| 12 | 12 | 9.5 | 9.5 | 9.5 | 9.5 | 12 | 12 | +| 3.6 | 4.32 | 3.6 | 4.32 | 7.2 | 8.64 | 14.4 | 17.28 | +| -7.59 | -7.4 | -5.59 | -5.4 | -2.96 | -2.79 | -2.47 | -2.36 | + +[8A-11] + +Bar chart and data table showing the gap with PDCCH AL16, 2Rx for various OFDM configurations. The chart shows negative values for each configuration, with the most significant gap at -7.59. + +Observation: + +- For normal UE and Rural scenario, comparing MIL of OFDM based LP-WUS to legacy PDCCH AL16, 2Rx +- [8A-11] show that with the LP-WUS resource of $X=17.28 \text{ MHz} \cdot \text{Symbol/bit}$ , the MIL margin $Y$ is $-2.36 \text{ dB}$ . + +**Gap with PDCCH AL8 2Rx** + +**Table 8.2.3.9-2: Gap with PDCCH AL8, 2Rx** + +![Bar chart and data table showing 'Average:Gap w/ AL8, 2Rx' for various waveform configurations. The chart shows values ranging from -13.27 to 2.86. The table below provides details for scenarios [8A-11] and [8A-13].](a756b11a82d229c04c8c5d78f40ff16d_img.jpg) + +**Average:Gap w/ AL8, 2Rx** + +| [8A-11] | | | | | | | | [8A-13] | | | | | | | | +|---------|-------|-------|-------|-------|-------|------|-------|-----------------------------|-----------------------------|-----------------------------|-----------------------------|-----------------------------|-----------------------------|-----------------------------|-----------------------------| +| OFDM | OFDM | OFDM | OFDM | OFDM | OFDM | OFDM | OFDM | sequence based LPWUS (OFDM) | sequence based LPWUS (OFDM) | sequence based LPWUS (OFDM) | sequence based LPWUS (OFDM) | sequence based LPWUS (OFDM) | sequence based LPWUS (OFDM) | sequence based LPWUS (OFDM) | sequence based LPWUS (OFDM) | +| 12 | 8 | 12 | 8 | 12 | 8 | 12 | 8 | 24 | 8 | 24 | 8 | 24 | 8 | 24 | 8 | +| 12 | 12 | 9.5 | 9.5 | 9.5 | 9.5 | 12 | 12 | 12 | 12 | 9.5 | 9.5 | 12 | 12 | 9.5 | 9.5 | +| 3.6 | 4.32 | 3.6 | 4.32 | 7.2 | 8.64 | 14.4 | 17.28 | 2.16 | 2.16 | 2.16 | 2.16 | 34.56 | 34.56 | 34.56 | 34.56 | +| -4.92 | -4.73 | -2.92 | -2.73 | -0.29 | -0.12 | 0.2 | 0.31 | -13.27 | -12.41 | -11.27 | -10.41 | -0.18 | 0.86 | 1.82 | 2.86 | + +Bar chart and data table showing 'Average:Gap w/ AL8, 2Rx' for various waveform configurations. The chart shows values ranging from -13.27 to 2.86. The table below provides details for scenarios [8A-11] and [8A-13]. + +**Observation:** + +For normal UE and Rural scenario, [8A-11] and [8A-13] show OFDM based LP-WUS is feasible to achieve comparable MIL (i.e. MIL margin $Y \geq -1\text{dB}$ ) than MSG3 PUSCH + +- [8A-13] shows that with LP-WUS resource $X=34.56 \text{ MHz} \cdot \text{Symbol/bit}$ , MIL margin $Y=-0.18\text{dB}$ + +- [8A-11] shows that with LP-WUS resource X=7.2MHz\*Symbol/bit, MIL margin Y=-0.29dB + +### 8.2.3.10 OFDM, Rural, Redcap UE, PDCCH + +#### Gap with PDCCH AL16 1Rx + +Table 8.2.3.10-1: Gap with PDCCH AL16 1Rx + +![Bar chart and data table showing the gap with PDCCH AL16 1Rx for various OFDM configurations. The chart shows negative values for most configurations, indicating a gap. The table below provides the specific parameters for each bar.](440236efe61277b409f0f16c982945c4_img.jpg) + +Average:Gap w/ AL16, 1RX + +| OFDM | OFDM | OFDM | OFDM | OFDM | OFDM | OFDM | OFDM | +|-------|-------|-------|-------|-------|-------|-------|-------| +| 12 | 8 | 12 | 8 | 12 | 8 | 12 | 8 | +| 12 | 12 | 9.5 | 9.5 | 12 | 12 | 9.5 | 9.5 | +| 3.6 | 4.32 | 3.6 | 4.32 | 7.2 | 8.64 | 7.2 | 8.64 | +| -4.91 | -4.72 | -2.91 | -2.72 | -2.28 | -2.11 | -0.28 | -0.11 | + +[8A-11] + +Bar chart and data table showing the gap with PDCCH AL16 1Rx for various OFDM configurations. The chart shows negative values for most configurations, indicating a gap. The table below provides the specific parameters for each bar. + +#### Observation: + +For Redcap UE in Rural, [8A-11] shows OFDM based LP-WUS is feasible to achieve comparable MIL (i.e. MIL margin Y>=-1dB) than PDCCH AL16 1Rx for paging when + +- LP-WUS resource X=7.2 MHz\*Symbol/bit, MIL margin Y=-0.28dB + +Gap with PDCCH AL8 1Rx + +Table 8.2.3.10-2: Gap with PDCCH AL8 1Rx + +![Bar chart and data table showing the gap with PDCCH AL8 1Rx for various waveform configurations. The chart shows values ranging from -9.73 to 3.7. The table below provides the specific parameters for each bar.](2fd08022cb2acbb95b368fd2e788864b_img.jpg) + +Average:Gap w/ AL8\_1RX + +| [8A-11] | | | | | | | | [8A-13] | | | | | | | | +|---------|-------|-------|-------|------|------|------|------|-----------------------------|-----------------------------|-----------------------------|-----------------------------|-----------------------------|-----------------------------|-----------------------------|-----------------------------| +| OFDM | OFDM | OFDM | OFDM | OFDM | OFDM | OFDM | OFDM | sequence based LPWUS (OFDM) | sequence based LPWUS (OFDM) | sequence based LPWUS (OFDM) | sequence based LPWUS (OFDM) | sequence based LPWUS (OFDM) | sequence based LPWUS (OFDM) | sequence based LPWUS (OFDM) | sequence based LPWUS (OFDM) | +| 12 | 8 | 12 | 8 | 12 | 8 | 12 | 8 | 24 | 8 | 24 | 8 | 24 | 8 | 24 | 8 | +| 12 | 12 | 9.5 | 9.5 | 12 | 12 | 9.5 | 9.5 | 12 | 12 | 9.5 | 9.5 | 12 | 12 | 9.5 | 9.5 | +| 3.6 | 4.32 | 3.6 | 4.32 | 7.2 | 8.64 | 7.2 | 8.64 | 2.16 | 2.16 | 2.16 | 2.16 | 17.28 | 17.28 | 17.28 | 17.28 | +| -2.21 | -2.02 | -0.21 | -0.02 | 0.42 | 0.59 | 2.42 | 2.59 | -9.73 | -8.87 | -7.73 | -6.87 | 0.25 | 1.7 | 2.25 | 3.7 | + +Sources: Gap w/ AL8\_1RX, per bit resource (MHz\*symbol/bit), Noise figure (dB), # of info bits, Waveform + +Bar chart and data table showing the gap with PDCCH AL8 1Rx for various waveform configurations. The chart shows values ranging from -9.73 to 3.7. The table below provides the specific parameters for each bar. + +Observation: + +For Redcap UE in Rural, [8A-11] and [8A-13] show OFDM based LP-WUS is feasible to achieve comparable MIL (i.e. MIL margin $Y \geq -1\text{dB}$ ) than PDCCH AL8 1Rx for paging when + +- LP-WUS resource $X=3.6\sim 17.28\text{ MHz}\cdot\text{Symbol/bit}$ , MIL margin $Y=-0.21\text{dB}\sim 3.7\text{dB}$ + +### 8.2.3.11 OFDM, Rural, Normal UE, Msg.3 + +Table 8.2.3.11: OFDM, Rural, Normal UE, Msg.3 + +![Bar chart and data table showing 'Average:Gap w/ PUSCH Msg3' for various waveform configurations. The chart shows values ranging from -2.69 to 17.63. The table below provides details for each bar, categorized into groups [8A-11], [8A-13], and [8A-5].](e416935e4c3e0c070050bb3ae2465074_img.jpg) + +Waveform family [dropdown] Scenario [dropdown] + +Average:Gap w/ PUSCH Msg3 + +| Group | Waveform | per bit resource (MHz*symbols/bit) | Noise figure (dB) | # of info bits | Average:Gap w/ PUSCH Msg3 | +|---------|----------------------------------|------------------------------------|-------------------|----------------|---------------------------| +| [8A-11] | OFDM | 12 | 12 | 3.6 | 3.8 | +| | OFDM | 8 | 12 | 4.32 | 3.99 | +| | OFDM | 12 | 9.5 | 3.6 | 5.8 | +| | OFDM | 8 | 9.5 | 4.32 | 5.99 | +| | OFDM | 12 | 9.5 | 7.2 | 8.43 | +| | OFDM | 8 | 9.5 | 8.64 | 8.6 | +| | OFDM | 12 | 12 | 14.4 | 8.92 | +| | OFDM | 8 | 12 | 17.28 | 9.03 | +| [8A-13] | sequence based LPWUS (OFDM) | 24 | 12 | 2.16 | 1.5 | +| | sequence based LPWUS (OFDM) | 8 | 12 | 2.16 | 2.36 | +| | sequence based LPWUS (OFDM) | 24 | 9.5 | 2.16 | 3.5 | +| | sequence based LPWUS (OFDM) | 8 | 9.5 | 2.16 | 4.36 | +| | sequence based LPWUS (OFDM) | 24 | 12 | 34.56 | 14.59 | +| | sequence based LPWUS (OFDM) | 8 | 12 | 34.56 | 15.63 | +| | sequence based LPWUS (OFDM) | 24 | 9.5 | 34.56 | 16.59 | +| | sequence based LPWUS (OFDM) | 8 | 9.5 | 34.56 | 17.63 | +| [8A-5] | OOK-4 with concentrated waveform | 48 | 15 | 2.16 | -2.69 | +| | sequence based LPWUS (OFDM) | 48 | 15 | 1.8 | -1.09 | +| | sequence based LPWUS (OFDM) | 48 | 15 | 2.16 | 0.01 | +| | sequence based LPWUS (OFDM) | 48 | 15 | 1.8 | 0.62 | +| | OOK-4 with concentrated waveform | 48 | 15 | 4.32 | 1.95 | +| | sequence based LPWUS (OFDM) | 48 | 15 | 2.16 | 2.93 | +| | OOK-4 with concentrated waveform | 48 | 15 | 8.64 | 4.73 | + +Bar chart and data table showing 'Average:Gap w/ PUSCH Msg3' for various waveform configurations. The chart shows values ranging from -2.69 to 17.63. The table below provides details for each bar, categorized into groups [8A-11], [8A-13], and [8A-5]. + +**Observation:** + +For normal UE in Rural, [8A-5], [8A-11] and [8A-13] show OFDM based LP-WUS is feasible to achieve comparable MIL (i.e. MIL margin $Y \geq -1\text{dB}$ ) than PUSCH for MSG.3 when + +- LP-WUS resource $X=1.8\sim 3.6\text{ MHz}\cdot\text{Symbol/bit}$ , MIL margin $Y=0.62\text{dB}\sim 4.36\text{dB}$ + +### 8.2.3.12 OFDM, Rural, Redcap UE, Msg.3 + +**Table 8.2.3.12: OFDM, Rural, Redcap UE, Msg.3** + +![Bar chart and data table showing Average Gap w/ PUSCH Msg3 for various waveforms. The chart shows values ranging from -2.69 to 14.93. The table below provides details for each waveform, including subcarrier spacing, CP length, and bandwidth.](b1c27d955a3589957e99cc4f284ddcb1_img.jpg) + +Average:Gap w/ PUSCH Msg3 + +| Waveform | SCS (kHz) | CP | BW (MHz) | Average Gap w/ PUSCH Msg3 | +|----------------------------------|-----------|-----|----------|---------------------------| +| OFDM | 12 | 8 | 12 | 3.8 | +| OFDM | 12 | 12 | 8 | 3.99 | +| OFDM | 12 | 9.5 | 12 | 5.8 | +| OFDM | 12 | 9.5 | 8 | 5.99 | +| OFDM | 12 | 12 | 12 | 6.43 | +| OFDM | 12 | 12 | 8 | 6.6 | +| OFDM | 12 | 9.5 | 12 | 8.43 | +| OFDM | 12 | 9.5 | 8 | 8.6 | +| sequence based LPWUS (OFDM) | 24 | 12 | 8 | 1.5 | +| sequence based LPWUS (OFDM) | 8 | 12 | 8 | 2.36 | +| sequence based LPWUS (OFDM) | 24 | 9.5 | 24 | 3.5 | +| sequence based LPWUS (OFDM) | 8 | 9.5 | 8 | 4.36 | +| sequence based LPWUS (OFDM) | 24 | 12 | 24 | 11.48 | +| sequence based LPWUS (OFDM) | 8 | 12 | 8 | 12.93 | +| sequence based LPWUS (OFDM) | 24 | 9.5 | 24 | 13.48 | +| sequence based LPWUS (OFDM) | 8 | 9.5 | 8 | 14.93 | +| OOK-4 with concentrated waveform | 48 | 15 | 48 | -2.69 | +| sequence based LPWUS (OFDM) | 48 | 15 | 48 | -1.09 | +| sequence based LPWUS (OFDM) | 48 | 15 | 48 | 0.01 | +| sequence based LPWUS (OFDM) | 48 | 15 | 48 | 0.62 | +| OOK-4 with concentrated waveform | 48 | 15 | 48 | 1.95 | +| sequence based LPWUS (OFDM) | 48 | 15 | 48 | 2.93 | +| OOK-4 with concentrated waveform | 48 | 15 | 48 | 4.73 | + +Bar chart and data table showing Average Gap w/ PUSCH Msg3 for various waveforms. The chart shows values ranging from -2.69 to 14.93. The table below provides details for each waveform, including subcarrier spacing, CP length, and bandwidth. + +**Observation:** + +For RedCap UE in Rural, [8A-5], [8A-11] and [8A-13] show OFDM based LP-WUS is feasible to achieve comparable MIL (i.e. MIL margin $Y \geq -1\text{dB}$ ) than PUSCH for MSG.3 when + +- LP-WUS resource $X=1.8\sim 3.6\text{ MHz}\cdot\text{Symbol/bit}$ , MIL margin $Y=0.62\text{dB}\sim 4.36\text{dB}$ + +## 8.3 LLS results observations + +In this clause and sub-clauses it is assumed that "tolerate" means that SNR degradation $\leq 2\text{dB}$ compared to error free case. Clause is based on contributed results in [8B-29]. + +### 8.3.1 Timing error + +#### 8.3.1.1 Results for timing error (without sliding window) + +The results are generated so that script finds a pair of results from a single source that differ only in timing error column. The SNR degradation is extracted, and the smallest degradation shown by a source is taken as representative value for the source. + +For the following Waveforms: + +- OOK-1 30kHz SCS +- OOK-1 60kHz SCS +- OOK-1 120kHz SCS +- OOK-2 M=2 +- OOK-2 M=4 +- OOK-3 +- OOK-4 M=2 +- OOK-4 M=4 +- OOK-4 M>4 +- FSK M=1 +- FSK-1 M=2 + +- FSK-2 M=2 +- OFDMA + +With the following assumption + +- ADC bit-width is 4 or more bits. +- Frequency error is 0 ppm. +- Other parameters are not restricted. + +Results are captured in Table 8.3-1. + +**Table 8.3-1: Timing error without sliding window.** + +| Te [us] | OOK-1
30kHz SCS | | OOK-1
60kHz SCS | | OOK-1
120kHz SCS | | OOK-3 | | +|----------------------------------------|----------------------------------------------------------|---------------|---------------------------------------------|--------------------------|---------------------------------------|---------------------------------|-----------------|---------------| +| | <2dB sources | >=2dB sources | <2dB sources | >=2dB sources | <2dB sources | >=2dB sources | <2dB sources | >=2dB sources | +| 1 | [8B-7][8B-11]
[8B-17][8B-2]
[8B-24][8B-27] | | [8B-2][8B-17]
[8B-7][8B-28] | | [8B-17][8B-2]
[8B-28] | | | | +| 2 | [8B-7][8B-11]
[8B-17][8B-2]
[8B-24][8B-27] | | [8B-7][8B-1][8B-21]
[8B-17][8B-2][8B-28] | | [8B-28] | [8B-1][8B-17]
[8B-2][8B-21] | [8B-15] | | +| 3 | [8B-17] | | [8B-17] | | | [8B-17] | [8B-15] | | +| 4 | [8B-7][8B-1]
[8B-11][8B-17]
[8B-2][8B-24][8B-27] | | [8B-1][8B-17][8B-7] | [8B-21][8B-2]
[8B-28] | | [8B-17][8B-2]
[8B-28][8B-21] | [8B-15] | | +| 5 | [8B-3] | | | | | | | | +| 10 | | [8B-3] | | | | | | | +| 15 | | [8B-3] | | | | | | | +| 20 | | [8B-3] | | | | | | | +| Sampling rate range [MHz] | 0,96-
15,36 | | 1,12-
7,68 | | 1,12-
7,68 | | 30,72-
30,72 | | +| Inner GB BW range, if applicable [kHz] | 0-
180 | | N/A | | N/A | | N/A | | +| Total Source | [8B-7][8B-1][8B-11][8B-17]
[8B-2][8B-3][8B-24][8B-27] | | [8B-7][8B-1][8B-21]
[8B-17][8B-2][8B-28] | | [8B-1][8B-21][8B-17]
[8B-2][8B-28] | | [8B-15] | | + +| Te [us] | OOK-2 M=2 | | OOK-2 M=4 | | OOK-4 M=2 | | OOK-4 M=4 | | OOK-4 M>4 | | +|----------------------------------------|-------------------------------------------------|-------------------|-----------------------------------------------------------|--------------------------|---------------------------------------------------------------------|--------------------------------------------|---------------------------------------------------------------------|--------------------------------------------------|--------------|---------------| +| | <2dB sources | >=2dB sources | <2dB sources | >=2dB sources | <2dB sources | >=2dB sources | <2dB sources | >=2dB sources | <2dB sources | >=2dB sources | +| SNR deg [dB] | | | | | | | | | | | +| 1 | [8B-8][8B-7]
[8B-11][8B-17]
[8B-2][8B-24] | | [8B-8][8B-7]
[8B-1][8B-11]
[8B-17][8B-2]
[8B-24] | | [8B-7][8B-11]
[8B-17][8B-2]
[8B-24][8B-27] | | [8B-7][8B-1]
[8B-17][8B-2]
[8B-3][8B-24] | [8B-11] | [8B-3] | [8B-1] | +| 2 | [8B-8][8B-7]
[8B-11][8B-17]
[8B-2][8B-24] | | [8B-8][8B-1]
[8B-11][8B-17]
[8B-2][8B-24] | [8B-7] | [8B-7][8B-1]
[8B-21][8B-17]
[8B-2][8B-24]
[8B-27] | [8B-11] | [8B-13][8B-3]
[8B-7] | [8B-1][8B-11]
[8B-21][8B-17]
[8B-2][8B-24] | | [8B-3] | +| 3 | [8B-17] | | [8B-17] | | [8B-17] | | [8B-3] | [8B-17] | | [8B-3] | +| 4 | [8B-8][8B-17]
[8B-2][8B-24] | [8B-11]
[8B-7] | [8B-8][8B-17]
[8B-2] | [8B-11][8B-7]
[8B-24] | [8B-7][8B-27] | [8B-11][8B-21]
[8B-17][8B-2]
[8B-24] | [8B-7] | [8B-11][8B-21]
[8B-17][8B-2]
[8B-3][8B-24] | | [8B-3] | +| 5 | | | | | [8B-3] | | | [8B-3] | | [8B-3] | +| 10 | | | | | | [8B-3] | | [8B-3] | | [8B-3] | +| 15 | | | | | | [8B-3] | | [8B-3] | | [8B-3] | +| 20 | | | | | | [8B-3] | | [8B-3] | | [8B-3] | +| Sampling rate range [MHz] | 0,96-15,36 | | 0,96-15,36 | | 1,92-15,36 | | 1,92-15,36 | | 3,4-7,68 | | +| Inner GB BW range, if applicable [kHz] | 120-480 | | 120-480 | | N/A | | N/A | | N/A | | +| Total Sources | [8B-7][8B-11]
[8B-17][8B-2][8B-24] | | [8B-7][8B-1][8B-11]
[8B-17][8B-2][8B-24] | | [8B-7][8B-1][8B-11][8B-21]
[8B-17][8B-2][8B-3]
[8B-24][8B-27] | | [8B-7][8B-1][8B-11][8B-21]
[8B-17][8B-13][8B-2]
[8B-3][8B-24] | | [8B-1][8B-3] | | + +| Te [us] | FSK M=1 | | FSK-1 M=2 | | FSK-2 M=2 | | OFDMA | | +|--------------|-------------------------------------|---------------|--------------------------------|---------------|-----------------------------------------------------|-------------------|--------------|---------------| +| | <2dB sources | >=2dB sources | <2dB sources | >=2dB sources | <2dB sources | >=2dB sources | <2dB sources | >=2dB sources | +| SNR deg [dB] | | | | | | | | | +| 1 | [8B-7]
[8B-17][8B-24]
[8B-27] | | [8B-8][8B-17]
[8B-7][8B-24] | | [8B-7]
[8B-11][8B-1]
[8B-17][8B-2]
[8B-24] | | [8B-28] | 0 | +| 2 | [8B-17]
[8B-7][8B-27] | [8B-24] | [8B-17] | [8B-7][8B-24] | [8B-17][8B-2]
[8B-11][8B-1] | [8B-7]
[8B-24] | [8B-28] | 0 | + +| | | | | | | | | | +|----------------------------------------|---------------------------------|---------------|----------------------|---------------|---------------------------------------------|--------------------------|-----------|---| +| 3 | [8B-17] | | [8B-17] | | [8B-1] [8B-17] | | | | +| 4 | [8B-17][8B-27] | [8B-7][8B-24] | [8B-17] | [8B-7][8B-24] | [8B-1][8B-17]
[8B-2] | [8B-11]
[8B-7][8B-24] | [8B-28] | 0 | +| 10 | 0 | | 0 | | 0 | | | | +| Sampling rate range [MHz] | 0,96-8,64 | | 0,96-8,64 | | 0,96-15,36 | | 3,84-7,68 | | +| Inner GB BW range, if applicable [kHz] | 0-480 | | 180-480 | | 0-480 | | N/A | | +| Total Sources | [8B-7][8B-17]
[8B-24][8B-27] | | [8B-17][8B-7][8B-24] | | [8B-7][8B-1][8B-11]
[8B-17][8B-2][8B-24] | | [8B-28] | | + +**Table 8.3-2: Tolerance to timing error by waveform** + +| Waveform | Tolerance up to timing error [ $\mu\text{s}$ ] | Note | +|------------------|------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| OOK-1 30kHz SCS | 5 | | +| OOK-1 60kHz SCS | 3 | | +| OOK-1 120kHz SCS | 1 | | +| OOK-3 | 4 | single source | +| OOK-2 M=2 | 4 | | +| OOK-2 M=4 | 3 | | +| OOK-4 M=2 | 3 | | +| OOK-4 M=4 | 1 | [8B-2] shows that performance degrade more than 2dB for 1us, with assumption of TDL-C 1000ns, but degrades <2dB for 1us with assumption of TDL-C 300ns. The 300ns delay spread was baseline. | +| OOK-4 M>4 | 1 | | +| FSK M=1 | 2 | | +| FSK-1 M=2 | 1 | | +| FSK-2 M=2 | 2/3 | [8B-1] [8B-17] sources showed tolerance up to 3us. | +| OFDMA | 4 | [8B-28] shows that OFDMA can be tolerant up to 4us. | + +### 8.3.1.1A Observation for timing error (without sliding window): + +There are the following observations for timing error from Table 8.3-2: + +- OOK/FSK waveform with longer time segment and with a single or multiple frequency segments is comparable (0 us) or more robust (up to 4us) to timing error than waveform with shorter time segment. +- [8B-28] shows that without sliding window, OFDMA tolerates up to 4us timing error, when SCS $\leq 30\text{kHz}$ , and receiver did not perform FFT. + +### 8.3.1.2 Results for timing error (with sliding window) + +For the following waveforms: + +- OOK-1 30kHz SCS +- OOK-1 60kHz SCS +- OOK-1 120kHz SCS +- OOK-2 M=2 +- OOK-2 M=4 +- OOK-3 +- OOK-4 M=2 +- OOK-4 M=4 +- OOK-4 M>4 +- FSK M=1 +- FSK-1 M=2 +- FSK-2 M=2 +- OFDMA + +With the following assumption + +- ADC bit-width is 4 or more bits. +- Frequency error is 0 ppm. +- Other parameters are not restricted. + +Results are presented in Table 8.3-3: + +**Table 8.3-3: Timing error with time sliding window** + +| Te [us] | OOK-1
30kHz SCS | | OOK-2
M=2 | | OOK-2
M=4 | | +|----------------------------------------|--------------------|---------------|--------------|---------------|--------------|---------------| +| | <2dB sources | >=2dB sources | <2dB sources | >=2dB sources | <2dB sources | >=2dB sources | +| SNR deg [dB] | | | | | | | +| 1 | [8B-8] | | [8B-8] | | [8B-8] | | +| 2 | [8B-8] | | [8B-8] | | [8B-8] | | +| 4 | [8B-8] | | [8B-8] | | [8B-8] | | +| 10 | [8B-8] | | [8B-8] | | [8B-8] | | +| Sampling rate range [MHz] | 0,96-7,68 | | 0,96-7,68 | | 0,96-7,68 | | +| Inner GB BW range, if applicable [kHz] | N/A | | 180-180 | | 180-180 | | +| Total Source | [8B-8] | | [8B-8] | | [8B-8] | | + +| Te [us] | FSK M=1 | | FSK-1
M=2 | | FSK-2
M=2 | | +|----------------------------------------|--------------|---------------|--------------|---------------|--------------|---------------| +| | <2dB sources | >=2dB sources | <2dB sources | >=2dB sources | <2dB sources | >=2dB sources | +| SNR deg [dB] | | | | | | | +| 1 | [8B-8] | | [8B-8] | | [8B-8] | | +| 2 | [8B-8] | | | [8B-8] | | [8B-8] | +| 3 | | | | | | | +| 4 | | [8B-8] | | [8B-8] | | [8B-8] | +| 10 | | [8B-8] | | [8B-8] | | [8B-8] | +| Sampling rate range [MHz] | 0,96-7,68 | | 0,96-7,68 | | 0,96-7,68 | | +| Inner GB BW range, if applicable [kHz] | 180-180 | | 180-180 | | 180-180 | | +| Total Sources | [8B-8] | | [8B-8] | | [8B-8] | | + +| Te
[us] | OFDMA | | +|-------------------------------------------|-----------------------------------------------|------------------| +| | <2dB
sources | >=2dB
sources | +| SNR deg [dB] | | | +| 1 | [8B-2][8B-21] [8B-15] | | +| 2 | [8B-25][8B-17][8B-13][8B-15] | [8B-21] | +| 3 | | [8B-15] | +| 4 | [8B-25][8B-21] | | +| 10 | | | +| Sampling
rate range [MHz] | 3,84
30,72 | | +| Inner GB BW
range, if applicable [kHz] | N/A | | +| Total Sources | [8B-15][8B-21][8B-17][8B-2]
[8B-13][8B-25] | | + +### 8.3.1.2A Observation for timing error (with sliding window): + +There are the following observations for timing error in Table 8.3-3: + +- For OFDMA, tolerance to timing error varies with sliding window size assumed by a receiver and was shown to tolerate timing error up to 4us if proper sliding window size is assumed by a receiver. + +## 8.3.2 Frequency error + +### 8.3.2.1 Results for frequency error + +The results are generated so that script finds a pair of results from a single source that differ only in frequency error column. The SNR degradation is extracted, and the smallest degradation shown by company is taken as representative value for the source. + +For the following waveforms: + +- OOK-1 30kHz SCS +- OOK-1 60kHz SCS +- OOK-1 120kHz SCS +- OOK-2 M=2 +- OOK-2 M=4 + +- OOK-3 +- OOK-4 M=2 +- OOK-4 M=4 +- OOK-4 M>4 +- FSK M=1 +- FSK-1 M=2 +- FSK-2 M=2 +- OFDMA + +With the following assumptions: + +- ADC bit-width is 4 or more bits. +- Timing error is 0 micro sec. +- Other parameters are not restricted. + +Results are presented in Table 8.3-4: + +**Table 8.3-4: Frequency error robustness for different waveforms** + +| Fe [kHz] | OOK-1
30kHz SCS | | Fe [kHz] | OOK-1
60kHz SCS | | Fe [kHz] | OOK-1
120kHz SCS | | Fe [kHz] | OOK-2
M=2 | | +|-------------------------------------------------|------------------------------------------------------------------------------------|---------------|----------|----------------------------------------------|---------------|----------|-----------------------------------|---------------|----------|---------------------------------------------------------|----------------| +| | <2dB sources | >=2dB sources | | <2dB sources | >=2dB sources | | <2dB sources | >=2dB sources | | <2dB sources | >=2dB sources | +| 2 | [8B-17] | | 2 | [8B-17] | | 2 | [8B-17] | | 2 | [8B-17] | | +| 2,6 | [8B-8] | | 4 | [8B-17] | | 4 | [8B-17] | | 2,6 | [8B-8] | | +| 4 | [8B-17] | | 10 | [8B-17] | | 10 | [8B-17] | | 4 | [8B-17] | | +| 5,2 | [8B-8] | | 13 | [8B-2][8B-7] | | 20 | [8B-17] | | 5,2 | [8B-8] | | +| 10 | [8B-17] | | 20 | [8B-17] | | 26 | [8B-2] | | 13 | [8B-8][8B-2]
[8B-7] | | +| 13 | [8B-8][8B-27]
[8B-2]
[8B-7] | | 26 | [8B-2] | | 40 | [8B-21] | | 20 | [8B-17] | | +| 20 | [8B-17] | | 40 | [8B-21] | | 100 | [8B-17] | | 26 | [8B-8][8B-2] | | +| 26 | [8B-8][8B-27]
[8B-2] | | 100 | [8B-17] | | 200 | [8B-17] | | 40 | [8B-24] | | +| 40 | [8B-24] | | 200 | [8B-7] | | 260 | [8B-1] | | 52 | [8B-7] | | +| 100 | [8B-17] | | 260 | [8B-17] | | 300 | [8B-17] | | 100 | [8B-17] | | +| 130 | [8B-22][8B-8]
[8B-11][8B-3]
[8B-7][8B-27] | | 300 | [8B-7][8B-1] | | 400 | [8B-21][8B-17] | | 130 | [8B-8][8B-25]
[8B-7][8B-11] | | +| 200 | [8B-24][8B-17] | | 400 | [8B-17] | | | | | 200 | [8B-24][8B-17] | | +| 260 | [8B-1][8B-8]
[8B-11][8B-3]
[8B-7] | | | | | | | | 260 | [8B-8][8B-11]
[8B-7] | | +| 300 | [8B-17] | | | | | | | | 300 | [8B-17] | | +| 390 | [8B-3] | | | | | | | | 400 | | [8B-24] | +| 400 | [8B-24][8B-17] | | | | | | | | 520 | | [8B-25][8B-11] | +| 520 | [8B-11][8B-3]
[8B-22][8B-7] | | | | | | | | 600 | | [8B-24] | +| 600 | [8B-24] | | | | | | | | 800 | | [8B-24] | +| 800 | [8B-24] | | | | | | | | | | | +| Sampling rate range [MHz] | 0,96-15,36 | | | 1,12-4,32 | | | 1,12-4,32 | | | 0,96-15,36 | | +| Inner GB BW range, if applicable [kHz] | N/A | | | N/A | | | N/A | | | 120-480 | | +| # of sources with/wo time domain sliding window | [8B-8]/
[8B-24][8B-17]
[8B-22][8B-1] [8B-2][8B-11]
[8B-3][8B-7][8B-27] | | | [-]/
[8B-17][8B-21]
[8B-1][8B-2][8B-7] | | | [-]
[8B-21][8B-17][8B-2][8B-1] | | | [8B-8]/ [8B-24][8B-17][8B-25]
[8B-2][8B-11][8B-7] | | +| # of sources with/wo frequency adjustment | [-]/
[8B-8][8B-24][8B-17]
[8B-22][8B-1] [8B-2][8B-11]
[8B-3][8B-7][8B-27] | | | [-]/
[8B-17][8B-21]
[8B-1][8B-2][8B-7] | | | [-] [8B-21][8B-17][8B-2][8B-1] | | | [-]/ [8B-24][8B-17][8B-25]
[8B-8][8B-2][8B-11][8B-7] | | + + + +| Fe [kHz] | OOK-2 M=4 | | Fe [kHz] | OOK=4 M=2 | | Fe [kHz] | OOK=4 M=4 | | Fe [kHz] | OOK=4 M>4 | | +|-------------------------------------------------|---------------------------------------------------------------------|-------------------------|----------|---------------------------------------------------------------------------------|---------------|----------|-------------------------------------------------------------------------------------|---------------|----------|--------------------------|---------------| +| | <2dB sources | >=2dB sources | | <2dB sources | >=2dB sources | | <2dB sources | >=2dB sources | | <2dB sources | >=2dB sources | +| 2 | [8B-17] | | 2 | [8B-17] | | 2 | [8B-17] | | 130 | [8B-3] | | +| 2,6 | [8B-8] | | 4 | [8B-17] | | 4 | [8B-17] | | 260 | [8B-3][8B-1] | | +| 4 | [8B-17] | | 10 | [8B-17] | | 7 | [8B-13] | | 390 | [8B-3] | | +| 5,2 | [8B-8] | | 13 | [8B-27][8B-2]
[8B-7] | | 10 | [8B-17] | | | | | +| 13 | [8B-8][8B-2]
[8B-7] | | 20 | [8B-17] | | 13 | [8B-2] | | | | | +| 20 | [8B-17] | | 26 | [8B-27][8B-2] | | 20 | [8B-17] | | | | | +| 26 | [8B-8][8B-2]
[8B-1] | | 32 | [8B-24] | | 26 | [8B-13][8B-2] | | | | | +| 40 | [8B-24] | | 40 | [8B-21][8B-24] | | 40 | [8B-21][8B-24]
[8B-13] | | | | | +| 52 | [8B-7] | | 100 | [8B-17] | | 52 | [8B-2] | | | | | +| 100 | [8B-17] | | 130 | [8B-25][8B-3]
[8B-11][8B-7]
[8B-27] | | 100 | [8B-17] | | | | | +| 130 | [8B-8][8B-11]
[8B-22] | [8B-7] | 200 | [8B-24][8B-17] | | 130 | [8B-25][8B-22]
[8B-3][8B-2]
[8B-11] | | | | | +| 200 | [8B-24][8B-17] | | 260 | [8B-11][8B-3]
[8B-7][8B-1] | | 200 | [8B-24][8B-17] | | | | | +| 260 | | [8B-8][8B-11]
[8B-7] | 300 | [8B-24] | | 260 | [8B-11][8B-3]
[8B-1] | | | | | +| 300 | [8B-17] | | 390 | [8B-3] | | 390 | [8B-3] | | | | | +| 400 | [8B-24] | | 400 | [8B-21][8B-24]
[8B-17] | | 400 | [8B-21][8B-24]
[8B-17] | | | | | +| 520 | | [8B-11][8B-22] | 520 | [8B-11][8B-3]
[8B-7] | | 520 | [8B-11][8B-3]
[8B-22] | | | | | +| 600 | [8B-24] | | 600 | [8B-24] | | 600 | [8B-24] | | | | | +| 800 | [8B-24] | | 800 | [8B-24] | | 800 | [8B-24] | | | | | +| | | | 1200 | [8B-24] | | | | | | | | +| | | | | | | | | | | | | +| | | | | | | | | | | | | +| Sampling rate range [MHz] | 0,96-15,36 | | | 1,92-15,36 | | | 1,92-15,36 | | | 3,4-7,68 | | +| Inner GB BW range, if applicable [kHz] | 120-480 | | | N/A | | | N/A | | | N/A | | +| # of sources with/wo time domain sliding window | [8B-8]/
[8B-24][8B-17][8B-22]
[8B-1][8B-8][8B-2][8B-11][8B-7] | | | [-]/ [8B-24][8B-17][8B-25]
[8B-21][8B-1][8B-2][8B-11]
[8B-3][8B-7][8B-27] | | | [-]/
[8B-24][8B-17][8B-25]
[8B-13][8B-21][8B-22]
[8B-1][8B-2][8B-11][8B-3] | | | [-]/
[8B-3]
[8B-1] | | +| # of sources with/wo frequency adjustment | [-]/
[8B-24][8B-17][8B-22] | | | [-]/ [8B-24][8B-17][8B-25]
[8B-21][8B-1][8B-2] | | | [-]/
[8B-24][8B-17][8B-25] | | | [-]/ | | + +| | | | | | | | | +|--|-------------------------------------|--|----------------------------|--|----------------------------------------------------|--|------------------| +| | [8B-1][8B-8][8B-2]
[8B-11][8B-7] | | [8B-11][8B-3][8B-7][8B-27] | | [8B-13][8B-21][8B-22]
[8B-1][8B-2][8B-11][8B-3] | | [8B-3]
[8B-1] | +|--|-------------------------------------|--|----------------------------|--|----------------------------------------------------|--|------------------| + +| Fe
[kHz] | FSK M=1 | | Fe
[kHz] | FSK-1
M=2 | | Fe
[kHz] | FSK-2
M=2 | | Fe
[kHz] | OFDMA | | | +|-------------------------------------------------------|---------------------------------------------------------|--------------------|-------------|---------------------------------|-------------------|-------------|-----------------------------------------------------|------------------|-------------|--------------------------|--------------------------------------------------------------|--| +| | <2dB
sources | >=2dB
sources | | <2dB
sources | >=2dB
sources | | <2dB
sources | >=2dB
sources | | <2dB
sources | >=2dB
sources | | +| 2,6 | [8B-8][8B-17]
[8B-27] | | 2,6 | [8B-8] | 0 | 2,6 | [8B-8][8B-17] | | 1,4 | [8B-13] | 0 | | +| 5,2 | [8B-8][8B-17]
[8B-27] | | 5,2 | [8B-8]
[8B-17] | 0 | 5,2 | [8B-8][8B-17] | | 2 | [8B-17] | 0 | | +| 13 | [8B-8][8B-27]
[8B-7] | | 13 | [8B-8][8B-7] | 0 | 13 | [8B-8][8B-2] | | 2,6 | [8B-27][8B-7]
[8B-15] | 0 | | +| 26 | [8B-8][8B-17] | | 26 | [8B-8]
[8B-17] | 0 | 26 | [8B-8][8B-17]
[8B-2] | | 3,5 | [8B-13] | 0 | | +| 32 | [8B-24] | | 40 | [8B-24] | 0 | 40 | [8B-24] | | 5,2 | [8B-13][8B-7]
[8B-15] | [8B-27] | | +| 40 | [8B-24] | | 52 | [8B-7] | 0 | 130 | [8B-8][8B-17]
[8B-11][8B-1] | | 7 | [8B-13] | | | +| 52 | [8B-7] | | 130 | [8B-8]
[8B-17] | [8B-7] | 200 | [8B-24] | | 8 | [8B-21][8B-13] | | | +| 130 | [8B-8][8B-17]
[8B-27][8B-7] | | 200 | | [8B-24] | 260 | [8B-8][8B-1] | [8B-17][8B-11] | 13 | [8B-13] | [8B-15][8B-7] | | +| 200 | [8B-24] | | 260 | [8B-8] | [8B-17]
[8B-7] | 400 | 0 | [8B-24] | 20 | [8B-17] | [8B-13] | | +| 260 | [8B-8][8B-17]
[8B-7] | | 400 | | [8B-24] | 520 | 0 | [8B-11] | 26 | [8B-25][8B-2]
[8B-7] | [8B-13] | | +| 300 | [8B-24] | | 520 | | [8B-17] | 600 | 0 | [8B-24] | 40 | | [8B-13] | | +| 400 | | [8B-24] | 600 | | [8B-24] | 800 | 0 | [8B-24] | 52 | [8B-2] | | | +| 520 | | [8B-17]
[8B-25] | | | | | | 0 | 100 | | [8B-17] | | +| 600 | | [8B-24] | | | | | | | 200 | | [8B-17] | | +| 800 | | [8B-24] | | | | | | | 300 | | [8B-17] | | +| 1200 | | [8B-24] | | | | | | | 400 | | [8B-17] | | +| Sampling
rate range [MHz] | 0,96-
10 | | | 0,96-
8,64 | | | 0,96-
15,36 | | | 3,84-
50 | | | +| Inner GB BW
range, if applicable
[kHz] | 0-
480 | | | 120-
480 | | | 0-
480 | | | N/A | | | +| # of sources
with/wo time domain
sliding window | [8B-8]/
[8B-24][8B-17][8B-25]
[8B-8][8B-7][8B-27] | | | [8B-8]/
[8B-24][8B-17][8B-7] | | | [8B-8]/ [8B-24][8B-17][8B-1][8B-8][8B-2]
[8B-11] | | | | [-]/
[8B-17][8B-25][8B-13]
[8B-21][8B-15][8B-2][8B-27] | | + +| | | | | | | | | +|-------------------------------------------|---------------------------------------------------------|--|----------------------------------|--|-----------------------------------------------------|--|--------------------------------------------------------------| +| # of sources with/wo frequency adjustment | [8B-8]/
[8B-24][8B-17][8B-25]
[8B-8][8B-7][8B-27] | | [8B-8]/
[8B-24] [8B-17][8B-7] | | [8B-8]/ [8B-24][8B-17][8B-1][8B-8][8B-2]
[8B-11] | | [-]/
[8B-17][8B-25][8B-13]
[8B-21][8B-15][8B-2][8B-27] | +|-------------------------------------------|---------------------------------------------------------|--|----------------------------------|--|-----------------------------------------------------|--|--------------------------------------------------------------| + +| Fe
[kHz] | OOK-3 | | +|----------------------------------------------------|-----------------|------------------| +| | <2dB
sources | >=2dB
sources | +| 9.984 | [8B-15] | | +| 13 | | [8B-15] | +| Sampling
rate range [MHz] | 30,72-
30,72 | | +| Inner GB BW
range, if applicable [kHz] | N/A | | +| # of sources
with/wo time domain sliding window | [-]/
[8B-15] | | +| # of sources with/wo
frequency adjustment | [-]/
[8B-15] | | + +Frequency error tolerance for the waveform is captured by the following Table 8.3-5. + +**Table 8.3-5: Frequency tolerance of waveforms** + +| Waveform | Tolerance up to frequency error [kHz] | Note | +|---------------------|---------------------------------------|------------------------------------------------------------------------------------------------------------------| +| OOK-1
30kHz SCS | 800 | max simulated value | +| OOK-1
60kHz SCS | 400 | max simulated value | +| OOK-1
120kHz SCS | 400 | max simulated value | +| OOK-3 | 9.984 | [8B-15] result | +| OOK-2 M=2 | 300 | | +| OOK-2 M=4 | 200 | 4 segment OOK-2 is less robust than 2 segment OOK-2 | +| OOK-4 M=2 | 1200 | max simulated value | +| OOK-4 M=4 | 800 | max simulated value | +| OOK-4 M>4 | 390 | max simulated value | +| FSK M=1 | 300 | two segments
[8B-8] assumes frequency adjustment which may cause frequency error | +| FSK-1 M=2 | 130 | four segments, and 2 are ON at given time
[8B-8] assumes frequency adjustment which may cause frequency error | +| FSK-2 M=2 | 200 | four segments, but only 1 is ON
[8B-8] assumes frequency adjustment which may cause frequency error | +| OFDMA | 26 | | + +### 8.3.2.1A Observation for frequency error + +There are the following observations for frequency error Table 8.3-5: + +- Single frequency segment OOK (except OOK3) waveform is more robust to frequency error (of 390 kHz) than OOK/FSK waveforms with multiple frequency segments (depending on guard-band size between segments) and both are more robust than OFDMA waveform assuming no frequency compensation/synchronization. +- [8B-1] showed that single frequency segment FSK2-envelop-IF waveform is more robust to frequency error (of 260 kHz) than OOK/FSK waveforms with multiple frequency segments (depending on guard-band size between segments) and both are more robust than OFDMA waveform assuming no frequency compensation/synchronization. + +### 8.3.3 Spectral efficiency + +For the following waveforms: + +- OOK-1 30kHz SCS +- OOK-1 60kHz SCS + +- OOK-1 120kHz SCS +- OOK-2 M=2 +- OOK-2 M=4 +- OOK-3 +- OOK-4 M=2 +- OOK-4 M=4 +- OOK-4 M>4 +- FSK M=1 +- FSK-1 M=2 +- FSK-2 M=2 +- OFDMA + +With the following assumptions: + +- Timing error = 0us. +- Frequency error = 0ppm. +- Only TDL-C results. +- Other parameters are not restricted. + - table includes results across different receiver types, different power pooling assumption, different sampling rates, different tx antenna configurations, FAR target for the same waveform. + - best result within a company/source is considered for the table. + +Table 8.3-6 presents the results: + +**Table 8.3-6: Spectral efficiency for different range and waveforms** + +| OOK-1 30kHz | | | | | | +|----------------|----------------|---------------------|-----------------|-----------------|--------------| +| SNR Range [dB] | SE median [dB] | SE average [b/s/Hz] | SE Min [b/s/Hz] | SE Max [b/s/Hz] | #Sources [-] | +| [-50, -9] | 0,003241 | 0,003241 | 0,003241 | 0,003241 | [8B-11] | + +| | | | | | | +|----------------|------------------------|---------------------|-----------------|-----------------|--------------------------------------------------------------------------| +| [-9, -3] | 0,003241 | 0,003241 | 0,003241 | 0,003241 | [8B-11][8B-17] | +| [-3, 3] | 0,003241 | 0,00321 | 0,00144 | 0,006481 | [8B-25][8B-3][8B-1][8B-2][8B-7][8B-22][8B-28][8B-8][8B-24][8B-27][8B-11] | +| [3, 9] | 0,003241 | 0,004028 | 0,001389 | 0,01037 | [8B-20][8B-17][8B-1][8B-7][8B-8][8B-27][8B-16] | +| [9, 50] | 0,013889 | 0,016152 | 0,008642 | 0,025926 | [8B-1][8B-2][8B-16] | +| OOK-1 60kHz | | | | | | +| SNR Range [dB] | SE 50% percentile [dB] | SE average [b/s/Hz] | SE Min [b/s/Hz] | SE Max [b/s/Hz] | #Sources [-] | +| [-50, -9] | NA | | | | | +| [-9, -3] | 0,00216 | 0,00216 | 0,00216 | 0,00216 | [8B-21] | +| [-3, 3] | 0,004321 | 0,004295 | 0,000926 | 0,006481 | [8B-21][8B-1][8B-2][8B-7][8B-28][8B-17] | +| [3, 9] | 0,006481 | 0,006327 | 0,003241 | 0,009259 | [8B-3][8B-7][8B-17] | +| [9, 50] | NA | | | | [8B-3][8B-7][8B-17] | +| OOK-1 120kHz | | | | | | +| SNR Range [dB] | SE 50% percentile [dB] | SE average [b/s/Hz] | SE Min [b/s/Hz] | SE Max [b/s/Hz] | #Sources [-] | +| [-50, -9] | NA | | | | | +| [-9, -3] | NA | | | | | +| [-3, 3] | 0,007562 | 0,007562 | 0,006481 | 0,008642 | [8B-21][8B-28] | +| [3, 9] | 0,010802 | 0,010802 | 0,008642 | 0,012963 | [8B-21][8B-1][8B-2][8B-17] | +| [9, 50] | 0,012963 | 0,012963 | 0,012963 | 0,012963 | [8B-17] | +| OOK-2 M=2 | | | | | | +| SNR Range [dB] | SE 50% percentile [dB] | SE average [b/s/Hz] | SE Min [b/s/Hz] | SE Max [b/s/Hz] | #Sources [-] | +| [-50, -9] | NA | | | | | +| [-9, -3] | 0,012963 | 0,012963 | 0,012963 | 0,012963 | [8B-11] | +| [-3, 3] | 0,006481 | 0,007562 | 0,003241 | 0,012963 | [8B-24][8B-2][8B-11] | +| [3, 9] | 0,00463 | 0,004455 | 0,00144 | 0,006481 | [8B-25][8B-2][8B-7][8B-8][8B-17] | +| [9, 50] | 0,006481 | 0,006481 | 0,006481 | 0,006481 | [8B-8] | +| OOK-2 M=4 | | | | | | +| SNR Range [dB] | SE 50% percentile [dB] | SE average [b/s/Hz] | SE Min [b/s/Hz] | SE Max [b/s/Hz] | #Sources [-] | +| [-50, -9] | NA | | | | | +| [-9, -3] | NA | | | | | +| [-3, 3] | 0,014583 | 0,014583 | 0,003241 | 0,025926 | [8B-2][8B-11] | +| [3, 9] | 0,012963 | 0,012963 | 0,012963 | 0,012963 | [8B-24][8B-2] | +| [9, 50] | 0,012037 | 0,013014 | 0,006481 | 0,025926 | [8B-1][8B-2][8B-7][8B-22][8B-8][8B-17] | +| OOK-4 M=2 | | | | | | +| SNR Range [dB] | SE 50% percentile [dB] | SE average [b/s/Hz] | SE Min [b/s/Hz] | SE Max [b/s/Hz] | #Sources [-] | +| [-50, -9] | NA | | | | | +| [-9, -3] | 0,002566 | 0,004639 | 0,000463 | 0,012963 | [8B-21][8B-7][8B-27][8B-11] | +| [-3, 3] | 0,004321 | 0,004515 | 0,00144 | 0,006481 | [8B-21][8B-25][8B-3][8B-1][8B-2][8B-7][8B-24][8B-27][8B-17] | +| [3, 9] | 0,006481 | 0,008025 | 0,006481 | 0,011111 | [8B-3][8B-7][8B-27] | +| [9, 50] | NA | | | | [8B-3][8B-7][8B-27] | + +| OOK-4 M=4 | | | | | | +|----------------|------------------------|---------------------|-----------------|-----------------|--------------------------------------------------------------| +| SNR Range [dB] | SE 50% percentile [dB] | SE average [b/s/Hz] | SE Min [b/s/Hz] | SE Max [b/s/Hz] | #Sources [-] | +| [-50, -9] | NA | | | | | +| [-9, -3] | 0,004321 | 0,007121 | 0,000463 | 0,025926 | [8B-13][8B-21][8B-3][8B-2][8B-7][8B-11] | +| [-3, 3] | 0,011111 | 0,010328 | 0,000463 | 0,025926 | [8B-13][8B-21][8B-25][8B-3][8B-2][8B-7][8B-28][8B-24][8B-11] | +| [3, 9] | 0,012037 | 0,010976 | 0,006481 | 0,012963 | [8B-13][8B-3][8B-1][8B-2][8B-7][8B-22][8B-28][8B-17] | +| [9, 50] | 0,019444 | 0,019444 | 0,012963 | 0,025926 | [8B-2][8B-22] | +| OOK-4 M>4 | | | | | | +| SNR Range [dB] | SE 50% percentile [dB] | SE average [b/s/Hz] | SE Min [b/s/Hz] | SE Max [b/s/Hz] | #Sources [-] | +| [-50, -9] | NA | | | | | +| [-9, -3] | 0,009722 | 0,009722 | 0,009722 | 0,009722 | [8B-3] | +| [-3, 3] | 0,015394 | 0,015394 | 0,004861 | 0,025926 | [8B-3][8B-24] | +| [3, 9] | 0,021605 | 0,021605 | 0,017284 | 0,025926 | [8B-3][8B-1] | +| [9, 50] | NA | | | | [8B-3][8B-1] | +| FSK M=1 | | | | | | +| SNR Range [dB] | SE 50% percentile [dB] | SE average [b/s/Hz] | SE Min [b/s/Hz] | SE Max [b/s/Hz] | #Sources [-] | +| [-50, -9] | NA | | | | | +| [-9, -3] | 0,00054 | 0,00054 | 0,00054 | 0,00054 | [8B-27] | +| [-3, 3] | 0,006481 | 0,005401 | 0,003241 | 0,006481 | [8B-24][8B-27][8B-17] | +| [3, 9] | 0,005556 | 0,005118 | 0,002881 | 0,006481 | [8B-25][8B-8][8B-7][8B-27] | +| [9, 50] | 0,006481 | 0,006481 | 0,006481 | 0,006481 | [8B-8] | +| FSK-1 M=2 | | | | | | +| SNR Range [dB] | SE 50% percentile [dB] | SE average [b/s/Hz] | SE Min [b/s/Hz] | SE Max [b/s/Hz] | #Sources [-] | +| [-50, -9] | NA | | | | | +| [-9, -3] | NA | | | | | +| [-3, 3] | NA | | | | | +| [3, 9] | 0,012963 | 0,012963 | 0,012963 | 0,012963 | [8B-24][8B-17] | +| [9, 50] | 0,012963 | 0,016667 | 0,011111 | 0,025926 | [8B-8][8B-7][8B-2] | +| FSK-2 M=2 | | | | | | +| SNR Range [dB] | SE 50% percentile [dB] | SE average [b/s/Hz] | SE Min [b/s/Hz] | SE Max [b/s/Hz] | #Sources [-] | +| [-50, -9] | NA | | | | | +| [-9, -3] | 0,008102 | 0,008102 | 0,003241 | 0,012963 | [8B-2][8B-11] | +| [-3, 3] | 0,012963 | 0,012963 | 0,012963 | 0,012963 | [8B-24][8B-2][8B-17] | +| [3, 9] | 0,011111 | 0,010905 | 0,008642 | 0,012963 | [8B-1][8B-7][8B-2] | +| [9, 50] | 0,019444 | 0,019444 | 0,012963 | 0,025926 | [8B-8][8B-2] | +| OFDMA | | | | | | +| SNR Range [dB] | SE 50% percentile [dB] | SE average [b/s/Hz] | SE Min [b/s/Hz] | SE Max [b/s/Hz] | #Sources [-] | +| [-50, -9] | 0,025926 | 0,025926 | 0,025926 | 0,025926 | [8B-21] | + +| | | | | | | +|----------------|------------------------|---------------------|-----------------|-----------------|--------------------------------------------------------| +| [-9, -3] | 0,012963 | 0,018426 | 0,001768 | 0,077778 | [8B-13][8B-21][8B-25][8B-2][8B-15][8B-27][8B-17] | +| [-3, 3] | 0,012626 | 0,015788 | 0,003241 | 0,038889 | [8B-13][8B-25][8B-2][8B-7][8B-28][8B-24][8B-27][8B-17] | +| [3, 9] | 0,012472 | 0,020819 | 0,006481 | 0,051852 | [8B-13][8B-7][8B-27][8B-17] | +| [9, 50] | NA | | | | [8B-13][8B-7][8B-27][8B-17] | +| OOK-3 | | | | | | +| SNR Range [dB] | SE 50% percentile [dB] | SE average [b/s/Hz] | SE Min [b/s/Hz] | SE Max [b/s/Hz] | #Sources [-] | +| [-50, -9] | | | | | | +| [-9, -3] | 0.004 | 0.004 | 0.004 | 0.004 | [8B-15] | +| [-3, 3] | | | | | | +| [3, 9] | | | | | | +| [9, 50] | | | | | | + +Note 1: The spectral efficiency of OFDMA waveform is dependent on the selection of sequences + +Note 2: Spectral efficiency: $SE = \text{LP-WUS information size [bits]} / \text{LP-WUS length [s]} / \text{LP-WUS BW [Hz]}$ + +## 8.3.4 RSRP RRM measurement accuracy + +### 8.3.4.1 Results for LP-SS RSRP RRM measurement, TDL-C + +Given assumption: + +- Resource unit is defined as total resource used for measurement, i.e. resource length [sym] \* # of samples used for averaging. +- X is the SNR target for measurement, Y is the measurement accuracy (delta-RSRP for 90% measurements) +- Results are shown per each value of X in particular Resource unit range. +- Impairments considered are shown in the table. +- TDL-C 300 channel +- X is SNR observed by LP-WUR. Corresponding SNR observed by MR depends on e.g. NF difference between MR and LR + +Results are summarised in Table 8.3-7 + +**Table 8.3-7: RSRP TDL-C channel RSRP accuracy** + +| Resource unit [sym] range
1-10 | | | | | | | | | +|------------------------------------|--------------|----------------|------------|------------|--------------|----------------|--------------|--------------| +| X=-9 Y=-> | 10 | 3 | 10 | 3 | 10 | | | | +| Source | [8B-25] | [8B-25] | [8B-25] | [8B-25] | [8B-25] | | | | +| Impairment | Te:0
Fe:0 | Te:0 Fe:0 | Te:0 Fe:50 | Te:0 Fe:50 | Te:2
Fe:0 | | | | +| # samples | 1 | 2 | 1 | 2 | 2 | | | | +| X=-6 Y=-> | 1,01 | | | | | | | | +| Source | [8B-13] | | | | | | | | +| Impairment | Te:0
Fe:0 | | | | | | | | +| # samples | 1 | | | | | | | | +| X=-3 Y=-> | 1,5 | 0,8 | 1,5 | 0,8 | 5 | 2,3 | 2,25 | | +| Source | [8B-25] | [8B-25] | [8B-25] | [8B-25] | [8B-25] | [8B-25] | [8B-1] | | +| Impairment | Te:0
Fe:0 | Te:0 Fe:0 | Te:0 Fe:50 | Te:0 Fe:50 | Te:2
Fe:0 | Te:2 Fe:0 | Te:0
Fe:0 | | +| # samples | 1 | 2 | 1 | 2 | 1 | 2 | 1 | | +| Resource unit [sym] range
11-20 | | | | | | | | | +| X=-11 Y=-> | 7,4 | 7,51 | 7,58 | | | | | | +| Source | [8B-7] | [8B-7] | [8B-7] | | | | | | +| Impairment | Te:0
Fe:0 | Te:0
Fe:200 | Te:4 Fe:0 | | | | | | +| # samples | 1 | 1 | 1 | | | | | | +| X=-9 Y=-> | 2 | 2 | 7 | 3,5 | 6,87 | 7,07 | 7,16 | 1,38 | +| Source | [8B-25] | [8B-25] | [8B-25] | [8B-25] | [8B-7] | [8B-7] | [8B-7] | [8B-13] | +| Impairment | Te:0
Fe:0 | Te:0 Fe:50 | Te:2 Fe:0 | Te:0 Fe:0 | Te:0
Fe:0 | Te:0
Fe:200 | Te:4
Fe:0 | Te:0
Fe:0 | +| # samples | 3 | 3 | 3 | 1 | 1 | 1 | 1 | 1 | +| X=-6 Y=-> | 5,93 | 6,12 | 6,29 | 0,78 | | | | | + +| | | | | | | | | | +|--------------------------------------------|--------------|----------------|----------------|-----------|------|------|--|--| +| Source | [8B-7] | [8B-7] | [8B-7] | [8B-13] | | | | | +| Impairment | Te:0
Fe:0 | Te:0
Fe:200 | Te:4 Fe:0 | Te:0 Fe:0 | | | | | +| # samples | 1 | 1 | 1 | 1 | | | | | +| X=-3 Y=-> | 0,5 | 0,5 | 1,8 | | | | | | +| Source | [8B-25] | [8B-25] | [8B-25] | | | | | | +| Impairment | Te:0
Fe:0 | Te:0 Fe:50 | Te:2 Fe:0 | | | | | | +| # samples | 3 | 3 | 3 | | | | | | +| Resource unit [sym] range
21-30 | | | | | | | | | +| X=-11 Y=-> | 4,82 | 5,39 | 5,44 | | | | | | +| Source | [8B-7] | [8B-7] | [8B-7] | | | | | | +| Impairment | Te:0
Fe:0 | Te:0
Fe:200 | Te:4 Fe:0 | | | | | | +| # samples | 2 | 2 | 2 | | | | | | +| X=-9 Y=-> | 2,8 | 4,93 | 5,08 | 5,15 | | | | | +| Source | [8B-25] | [8B-7] | [8B-7] | [8B-7] | | | | | +| Impairment | Te:0
Fe:0 | Te:0 Fe:0 | Te:0
Fe:200 | Te:4 Fe:0 | | | | | +| # samples | 1 | 2 | 2 | 2 | | | | | +| X=-6 Y=-> | 4,27 | 4,4 | 4,58 | | | | | | +| Source | [8B-7] | [8B-7] | [8B-7] | | | | | | +| Impairment | Te:0
Fe:0 | Te:0
Fe:200 | Te:4 Fe:0 | | | | | | +| # samples | 2 | 2 | 2 | | | | | | +| Resource unit [sym] range
31-50 | | | | | | | | | +| X=-11 Y=-> | 4,34 | 4,41 | 4,46 | | | | | | +| Source | [8B-7] | [8B-7] | [8B-7] | | | | | | +| Impairment | Te:0
Fe:0 | Te:0
Fe:200 | Te:4 Fe:0 | | | | | | +| # samples | 3 | 3 | 3 | | | | | | +| X=-9 Y=-> | 1,8 | 4,05 | 4,15 | 4,23 | | | | | +| Source | [8B-25] | [8B-7] | [8B-7] | [8B-7] | | | | | +| Impairment | Te:0
Fe:0 | Te:0 Fe:0 | Te:0
Fe:200 | Te:4 Fe:0 | | | | | +| # samples | 1 | 3 | 3 | 3 | | | | | +| X=-6 Y=-> | 3,51 | 3,62 | 3,75 | | | | | | +| Source | [8B-7] | [8B-7] | [8B-7] | | | | | | +| Impairment | Te:0
Fe:0 | Te:0
Fe:200 | Te:4 Fe:0 | | | | | | +| # samples | 3 | 3 | 3 | | | | | | +| Resource unit [sym] range
51-70 | | | | | | | | | +| X=-11 Y=-> | 3,78 | 3,36 | 3,83 | 3,37 | 3,87 | 3,48 | | | + +| | | | | | | | | | +|------------|--------------|-----------|----------------|----------------|--------------|-----------|--------------|--| +| > | | | | | | | | | +| Source | [8B-7] | [8B-7] | [8B-7] | [8B-7] | [8B-7] | [8B-7] | | | +| Impairment | Te:0
Fe:0 | Te:0 Fe:0 | Te:0
Fe:200 | Te:0
Fe:200 | Te:4
Fe:0 | Te:4 Fe:0 | | | +| # samples | 4 | 5 | 4 | 5 | 4 | 5 | | | +| X=-9 Y=-> | 3,53 | 3,13 | 3,6 | 3,18 | 3,65 | 3,28 | 0,57 | | +| Source | [8B-7] | [8B-7] | [8B-7] | [8B-7] | [8B-7] | [8B-7] | [8B-13] | | +| Impairment | Te:0
Fe:0 | Te:0 Fe:0 | Te:0
Fe:200 | Te:0
Fe:200 | Te:4
Fe:0 | Te:4 Fe:0 | Te:0
Fe:0 | | +| # samples | 4 | 5 | 4 | 5 | 4 | 5 | 5 | | +| X=-6 Y=-> | 3,05 | 2,71 | 3,14 | 2,78 | 3,27 | 2,92 | 0,32 | | +| Source | [8B-7] | [8B-7] | [8B-7] | [8B-7] | [8B-7] | [8B-7] | [8B-13] | | +| Impairment | Te:0
Fe:0 | Te:0 Fe:0 | Te:0
Fe:200 | Te:0
Fe:200 | Te:4
Fe:0 | Te:4 Fe:0 | Te:0
Fe:0 | | +| # samples | 4 | 5 | 4 | 5 | 4 | 5 | 5 | | + +### 8.3.4.1A Observation RSRP LP-SS, TDL-C: + +For OOK based LP-SS RSRP measurement accuracy ([8B-1][8B-13],[8B-7],[8B-25]) + +- at SNR X=-6, to achieve 90 % accuracy of measurement $+Y \leq 3\text{dB}$ , [8B-13],[8B-7] show 51-70 symbols spread over 4-5 periods of LP-SS are sufficient, [8B-13] shows 11-20 symbols spread over 1 period is sufficient. +- at SNR X=-3, to achieve 90 % accuracy of measurement $+Y \leq 3\text{dB}$ , less than 10 symbols spread over 1-2 periods is sufficient. [8B-25][8B-1] +- at SNR X=-9, to achieve 90 % accuracy of measurement $+Y \leq 5\text{dB}$ , [8B-25],[8B-7] show 21-30 symbols spread over 4-5 periods of LP-SS are sufficient, [8B-13] shows that 11-20 symbols within 1 period are sufficient +- at SNR X=-6, to achieve 90 % accuracy of measurement $+Y \leq 5\text{dB}$ , [8B-7] shows 21-30 symbols spread over 4-5 periods of LP-SS are sufficient, [8B-13] shows that 11-20 symbols within 1 period are sufficient. + +### 8.3.4.2 Results for LP-SS RSRP RRM measurement, AWGN + +Given assumptions: + +- Resource unit is defined as total resource used for measurement, i.e., resource length [sym] \* # of samples used for averaging. +- X is the SNR target for measurement, Y is the measurement accuracy (delta-RSRP for 90% measurements) +- Results are shown per each value of X in particular Resource unit range. +- Impairments and Sources are shown as well. +- AWGN channel. + +Results are summarised in Table 8.3-8 + +**Table 8.3-8: RSRP AWGN channel RSRP accuracy** + +| Resource unit [sym] range
1-10 | | | | | | +|-----------------------------------|--|---------|---------|--|--| +| X=-9 Y=-> | | 3 | 2 | | | +| Source | | [8B-25] | [8B-25] | | | + +| | | | | | | +|--------------------------------------------|-----------|-------------|-------------|-----------|-----------| +| Impairment | Te:0 Fe:0 | Te:0 Fe:0 | | | | +| # samples | 1 | 2 | | | | +| | | | | | | +| X=-6 Y=-> | 0,81 | | | | | +| Source | [8B-13] | | | | | +| Impairment | Te:0 Fe:0 | | | | | +| # samples | 1 | | | | | +| | | | | | | +| X=-3 Y=-> | 0,75 | 0,55 | | | | +| Source | [8B-25] | [8B-25] | | | | +| Impairment | Te:0 Fe:0 | Te:0 Fe:0 | | | | +| # samples | 1 | 2 | | | | +| Resource unit [sym] range
11-20 | | | | | | +| | | | | | | +| X=-11 Y=-> | 3,89 | 4,25 | 4,32 | | | +| Source | [8B-7] | [8B-7] | [8B-7] | | | +| Impairment | Te:0 Fe:0 | Te:0 Fe:200 | Te:4 Fe:0 | | | +| # samples | 1 | 1 | 1 | | | +| | | | | | | +| X=-9 Y=-> | 1,7 | 2,22 | 2,73 | 2,78 | 1,17 | +| Source | [8B-25] | [8B-7] | [8B-7] | [8B-7] | [8B-13] | +| Impairment | Te:0 Fe:0 | Te:0 Fe:0 | Te:0 Fe:200 | Te:4 Fe:0 | Te:0 Fe:0 | +| # samples | 3 | 1 | 1 | 1 | 1 | +| | | | | | | +| X=-6 Y=-> | 1,15 | 1,3 | 1,33 | 0,64 | | +| Source | [8B-7] | [8B-7] | [8B-7] | [8B-13] | | +| Impairment | Te:0 Fe:0 | Te:0 Fe:200 | Te:4 Fe:0 | Te:0 Fe:0 | | +| # samples | 1 | 1 | 1 | 1 | | +| | | | | | | +| X=-3 Y=-> | 0,5 | | | | | +| Source | [8B-25] | | | | | +| Impairment | Te:0 Fe:0 | | | | | +| # samples | 3 | | | | | +| Resource unit [sym] range
21-30 | | | | | | +| X=-11 Y=-> | 3,28 | 3,21 | 3,28 | | | +| Source | [8B-7] | [8B-7] | [8B-7] | | | +| Impairment | Te:0 Fe:0 | Te:0 Fe:200 | Te:4 Fe:0 | | | +| # samples | 2 | 2 | 2 | | | +| | | | | | | +| Resource Range unit | 30 | 50 | | | | +| | | | | | | +| X=-6 Y=-> | 0,38 | | | | | +| Source | [8B-13] | | | | | +| Impairment | Te:0 Fe:0 | | | | | +| # samples | 5 | | | | | +| Resource unit [sym] range
51-70 | | | | | | + +| | | | | | | +|------------|-----------|--|--|--|--| +| X=-9 Y=-> | 0,52 | | | | | +| Source | [8B-13] | | | | | +| Impairment | Te:0 Fe:0 | | | | | +| # samples | 5 | | | | | +| | | | | | | +| X=-6 Y=-> | 0,3 | | | | | +| Source | [8B-13] | | | | | +| Impairment | Te:0 Fe:0 | | | | | +| # samples | 5 | | | | | + +### 8.3.4.2A Observation RSRP LP-SS, AWGN: + +For OOK based LP-SS RSRP measurement accuracy ([8B-13],[8B-7][8B-25]), + +- at SNR X=-9, to achieve 90 % accuracy of measurement $+Y \leq 3\text{dB}$ , $\leq 10$ OFDMA symbols over 1-3 periods are sufficient. +- at SNR X=-11, to achieve 90 % accuracy of measurement $+Y \leq 5\text{dB}$ , 11-20 OFDMA symbols over 1-3 periods are sufficient. + +### 8.3.4.3 Results for SSS RSRP RRM measurement, TDL-C + +Given assumptions: + +- Resource unit is defined as total resource used for measurement, i.e. resource length [sym] \* # of samples used for averaging. +- X is the SNR target for measurement, Y is the measurement accuracy (delta-RSRP for 90% measurements) +- Results are shown per each value of X in particular Resource unit range. +- Impairments and Sources are shown as well. +- Only TDL-C 300 results + +Results are summarised in Table 8.3-9. + +**Table 8.3-9: RSRP SSS TDL-C** + +| Resource unit [sym] | | | | | | | +|---------------------|-----------|------------|-----------|-----------|-----------|-----------| +| 1 | | | | | | | +| X=-6 Y=-> | 1,5 | 1,85 | 1,8 | | | | +| Source | [8B-25] | [8B-25] | [8B-25] | | | | +| Impairment | Te:0 Fe:0 | Te:0 Fe:10 | Te:2 Fe:0 | | | | +| # samples | 1 | 1 | 1 | | | | +| | | | | | | | +| X=-3 Y=-> | 0,95 | 1,25 | 1,3 | 1,6443 | 1,7817 | 2,2314 | +| Source | [8B-25] | [8B-25] | [8B-25] | [8B-27] | [8B-27] | [8B-27] | +| Impairment | Te:0 Fe:0 | Te:0 Fe:10 | Te:2 Fe:0 | Te:0 Fe:0 | Te:0 Fe:1 | Te:0 Fe:2 | +| # samples | 1 | 1 | 1 | 1 | 1 | 1 | +| Resource unit [sym] | | | | | | | +| 2 | | | | | | | +| X=-6 Y=-> | 1,2 | 1,4 | 1,3 | | | | + +| | | | | | | | +|----------------------------------|-----------|------------|-----------|-----------|-----------|-----------| +| Source | [8B-25] | [8B-25] | [8B-25] | | | | +| Impairment | Te:0 Fe:0 | Te:0 Fe:10 | Te:2 Fe:0 | | | | +| # samples | 2 | 2 | 2 | | | | +| | | | | | | | +| X=-3 Y=-> | 0,7 | 0,85 | 0,9 | 1,0021 | 1,0608 | 1,5672 | +| Source | [8B-25] | [8B-25] | [8B-25] | [8B-27] | [8B-27] | [8B-27] | +| Impairment | Te:0 Fe:0 | Te:0 Fe:10 | Te:2 Fe:0 | Te:0 Fe:0 | Te:0 Fe:1 | Te:0 Fe:2 | +| # samples | 2 | 2 | 2 | 2 | 2 | 2 | +| Resource unit [sym]
3 | | | | | | | +| | | | | | | | +| X=-6 Y=-> | 0,9 | 1,1 | 1,1 | | | | +| Source | [8B-25] | [8B-25] | [8B-25] | | | | +| Impairment | Te:0 Fe:0 | Te:0 Fe:10 | Te:2 Fe:0 | | | | +| # samples | 3 | 3 | 3 | | | | +| | | | | | | | +| X=-3 Y=-> | 0,5 | 0,65 | 0,65 | | | | +| Source | [8B-25] | [8B-25] | [8B-25] | | | | +| Impairment | Te:0 Fe:0 | Te:0 Fe:10 | Te:2 Fe:0 | | | | +| # samples | 3 | 3 | 3 | | | | +| Resource unit [sym]
4 | | | | | | | +| | | | | | | | +| X=-3 Y=-> | 0,6481 | 0,7332 | 1,2474 | | | | +| Source | [8B-27] | [8B-27] | [8B-27] | | | | +| Impairment | Te:0 Fe:0 | Te:0 Fe:1 | Te:0 Fe:2 | | | | +| # samples | 4 | 4 | 4 | | | | +| Resource unit [sym]
5 | | | | | | | +| | | | | | | | +| X=-3 Y=-> | 0,6195 | 0,7151 | 1,0843 | | | | +| Source | [8B-27] | [8B-27] | [8B-27] | | | | +| Impairment | Te:0 Fe:0 | Te:0 Fe:1 | Te:0 Fe:2 | | | | +| # samples | 5 | 5 | 5 | | | | + +### 8.3.4.3A Observation for SSS RSRP RRM measurement, TDL-C + +For SSS based RSRP RRM measurement accuracy ([8B-27][8B-25]) + +- at SNR X=-6, to achieve 90 % accuracy of measurement $+Y \leq 3\text{dB}$ , 1 symbol is sufficient +- at SNR X=-3, to achieve 90 % accuracy of measurement $+Y \leq 3\text{dB}$ , 1 symbol is sufficient + +## 8.3.5 RSRQ RRM measurement accuracy + +### 8.3.5.1 Results LP-SS, AWGN + +Given assumptions: + +- Resource unit is defined as total resource used for measurement, i.e. resource length [sym] \* # of samples used for averaging. + +- X is the SNR target for measurement, Y is the measurement accuracy (delta-RSRQ for 90% measurements) +- Results are shown per each value of X in particular Resource unit range. +- Impairments and Sources are shown as well. +- AWGN channel + +The results are summarized in Table 8.3-10. + +**Table 8.3-10: RSRQ measurement accuracy LP-SS, AWGN** + +| Resource unit [sym] range
11-20 | | | | +|------------------------------------|-----------|----------------|-----------| +| X=-11 Y=-> | 3,87 | 4,23 | 4,3 | +| Source | [8B-7] | [8B-7] | [8B-7] | +| Impairment | Te:0 Fe:0 | Te:0
Fe:200 | Te:4 Fe:0 | +| # samples | 1 | 1 | 1 | +| X=-9 Y=-> | 2,2 | 2,35 | 2,39 | +| Source | [8B-7] | [8B-7] | [8B-7] | +| Impairment | Te:0 Fe:0 | Te:0
Fe:200 | Te:4 Fe:0 | +| # samples | 1 | 1 | 1 | +| X=-6 Y=-> | 1,13 | 1,19 | 1,21 | +| Source | [8B-7] | [8B-7] | [8B-7] | +| Impairment | Te:0 Fe:0 | Te:0
Fe:200 | Te:4 Fe:0 | +| # samples | 1 | 1 | 1 | +| Resource Range unit | 20 | 30 | | +| X=-11 Y=-> | 2,93 | 3,2 | 3,26 | +| Source | [8B-7] | [8B-7] | [8B-7] | +| Impairment | Te:0 Fe:0 | Te:0
Fe:200 | Te:4 Fe:0 | +| # samples | 2 | 2 | 2 | + +### 8.3.5.1A Observation RSRQ LP-SS, AWGN: + +For OOK-based LP-SS. RSRQ measurement accuracy ([8B-7]) + +- at SNR X=-6, to achieve 90 % accuracy of measurement $+Y \leq 3\text{dB}$ , 11-20 OFDMA symbols over 1 period are sufficient. +- at SNR X=-6, to achieve 90 % accuracy of measurement $+Y \leq 5\text{dB}$ , 11-20 OFDMA symbols over 1 period are sufficient. +- at SNR X=-9, to achieve 90 % accuracy of measurement $+Y \leq 5\text{dB}$ , 11-20 OFDMA symbols over 1 period are sufficient. + +### 8.3.5.2 Results LP-SS, TDL-C + +Given assumptions: + +- Resource unit is defined as total resource used for measurement, i.e. resource length [sym] \* # of samples used for averaging. +- X is the SNR target for measurement, Y is the measurement accuracy (delta-RSRQ for 90% measurements) +- Results are shown per each value of X in particular Resource unit range. +- Impairments and Sources are shown as well. +- TDL-C channel + +The results are summarized in Table 8.3-11. + +**Table 8.3-11: RSRQ measurement accuracy LP-SS, TDL-C** + +| Resource unit [sym] range
11-20 | | | | | | | +|------------------------------------|-----------|-------------|-----------|--|--|--| +| X=-11 Y=-> | 7,14 | 7,27 | 7,33 | | | | +| Source | [8B-7] | [8B-7] | [8B-7] | | | | +| Impairment | Te:0 Fe:0 | Te:0 Fe:200 | Te:4 Fe:0 | | | | +| # samples | 1 | 1 | 1 | | | | +| X=-9 Y=-> | 6,45 | 6,67 | 6,74 | | | | +| Source | [8B-7] | [8B-7] | [8B-7] | | | | +| Impairment | Te:0 Fe:0 | Te:0 Fe:200 | Te:4 Fe:0 | | | | +| # samples | 1 | 1 | 1 | | | | +| X=-6 Y=-> | 5,13 | 5,35 | 5,51 | | | | +| Source | [8B-7] | [8B-7] | [8B-7] | | | | +| Impairment | Te:0 Fe:0 | Te:0 Fe:200 | Te:4 Fe:0 | | | | +| # samples | 1 | 1 | 1 | | | | +| Resource unit [sym] range
20-30 | | | | | | | +| X=-11 Y=-> | 5,16 | 5,23 | 5,27 | | | | +| Source | [8B-7] | [8B-7] | [8B-7] | | | | +| Impairment | Te:0 Fe:0 | Te:0 Fe:200 | Te:4 Fe:0 | | | | +| # samples | 2 | 2 | 2 | | | | +| X=-9 Y=-> | 4,65 | 4,81 | 4,88 | | | | +| Source | [8B-7] | [8B-7] | [8B-7] | | | | +| Impairment | Te:0 Fe:0 | Te:0 Fe:200 | Te:4 Fe:0 | | | | +| # samples | 2 | 2 | 2 | | | | +| X=-6 Y=-> | 3,75 | 3,89 | 4,05 | | | | +| Source | [8B-7] | [8B-7] | [8B-7] | | | | +| Impairment | Te:0 Fe:0 | Te:0 Fe:200 | Te:4 Fe:0 | | | | +| # samples | 2 | 2 | 2 | | | | +| Resource unit [sym] range
30-50 | | | | | | | +| X=-11 Y=-> | 4,21 | 4,29 | 4,33 | | | | +| Source | [8B-7] | [8B-7] | [8B-7] | | | | +| Impairment | Te:0 Fe:0 | Te:0 Fe:200 | Te:4 Fe:0 | | | | +| # samples | 3 | 3 | 3 | | | | + +| | | | | | | | +|--------------------------------------------|-----------|-------------|-------------|-------------|-----------|-----------| +| | | | | | | | +| X=-9 Y=-> | 3,84 | 3,94 | 4,02 | | | | +| Source | [8B-7] | [8B-7] | [8B-7] | | | | +| Impairment | Te:0 Fe:0 | Te:0 Fe:200 | Te:4 Fe:0 | | | | +| # samples | 3 | 3 | 3 | | | | +| | | | | | | | +| X=-6 Y=-> | 3,08 | 3,22 | 3,34 | | | | +| Source | [8B-7] | [8B-7] | [8B-7] | | | | +| Impairment | Te:0 Fe:0 | Te:0 Fe:200 | Te:4 Fe:0 | | | | +| # samples | 3 | 3 | 3 | | | | +| Resource unit [sym] range
50-70 | | | | | | | +| X=-11 Y=-> | 3,68 | 3,27 | 3,72 | 3,29 | 3,77 | 3,39 | +| Source | [8B-7] | [8B-7] | [8B-7] | [8B-7] | [8B-7] | [8B-7] | +| Impairment | Te:0 Fe:0 | Te:0 Fe:0 | Te:0 Fe:200 | Te:0 Fe:200 | Te:4 Fe:0 | Te:4 Fe:0 | +| # samples | 4 | 5 | 4 | 5 | 4 | 5 | +| | | | | | | | +| X=-9 Y=-> | 3,35 | 2,96 | 3,43 | 3,03 | 3,47 | 3,12 | +| Source | [8B-7] | [8B-7] | [8B-7] | [8B-7] | [8B-7] | [8B-7] | +| Impairment | Te:0 Fe:0 | Te:0 Fe:0 | Te:0 Fe:200 | Te:0 Fe:200 | Te:4 Fe:0 | Te:4 Fe:0 | +| # samples | 4 | 5 | 4 | 5 | 4 | 5 | +| | | | | | | | +| X=-6 Y=-> | 2,69 | 2,38 | 2,81 | 2,48 | 2,94 | 2,62 | +| Source | [8B-7] | [8B-7] | [8B-7] | [8B-7] | [8B-7] | [8B-7] | +| Impairment | Te:0 Fe:0 | Te:0 Fe:0 | Te:0 Fe:200 | Te:0 Fe:200 | Te:4 Fe:0 | Te:4 Fe:0 | +| # samples | 4 | 5 | 4 | 5 | 4 | 5 | + +### 8.3.5.2A Observation RSRQ LP-SS, TDL-C: + +For OOK-based LP-SS measurement accuracy ([8B-7]) + +- at SNR X=-6, to achieve 90 % accuracy of measurement $+Y \leq 3\text{dB}$ , 51-70 symbols over 4 periods are sufficient. +- at SNR X=-6, to achieve 90 % accuracy of measurement $+Y \leq 5\text{dB}$ , 21-30 symbols over 2 periods are sufficient. +- at SNR X=-9, to achieve 90 % accuracy of measurement $+Y \leq 5\text{dB}$ , 21-30 symbols over 2 periods are sufficient. + +## 8.4 Network power consumption + +### 8.4.1 Collection of the results + +Evaluation of the network power consumption for introducing LP-SS is summarized in Table 8.4. + +It is assumed that the LP-SS periodicity is 320ms. And for more results and details, it can be found in Annex 8.4. + +**Table 8.4: Summary of network power consumption increases for introducing LP-SS** + +| Network load | Company | LP-SS periodicity | LP-SS duration/BW | beam | Additional NW power consumption | +|--------------|---------|-------------------|-------------------------------------------------|------|---------------------------------| +| zero | [8A-11] | 320ms | 14symbols per beam, 8 slots in total and 11PRBs | 8 | 1.097%~3.55% | +| | [8A-13] | 320ms | 7symbols per beam, 4slots in total and 12 PRBs | 4 | 0.06%~0.50% | +| | [8A-5] | 320ms | 28symbols per beam, 5Mhz | 4 | 0.122% | +| | [8A-3] | 320ms | 14 symbol duration (1 slot) per beam, 5MHz | 8 | 3.9% | +| | | 320ms | 42 symbol duration per beam, 5MHz | 8 | 11.4% | +| | | 320ms | 4 symbol duration per beam, 5MHz | 8 | 1.1% | +| low | [8A-11] | 320ms | 14symbols per beam, 8 slots in total and 11PRBs | 8 | 0.912%~2.716% | +| | [8A-13] | 320ms | 7symbols per beam, 4slots in total and 12 PRBs | 4 | 0.07%~0.7% | +| Medium | [8A-11] | 320ms | 14symbols per beam, 8 slots in total and 11PRBs | 8 | 0.388%~1.076% | + +Note: The definition of network load is given in TR 38.864. + +| For evaluation purpose,
- A load (L) % of a cell is a percentage of resources used for UE specific PDSCH / PUSCH
- The following load scenarios are considered | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------| +| Load scenario | Characteristics | +| Idle/empty load | Include cell-specific signals and channels, and $L = 0$ | +| Low load | Include cell-specific signals and channels, and $0 < L \leq 15$ | +| Light load | Include cell-specific signals and channels, and $15 < L \leq 30$ | +| Medium load | Include cell-specific signals and channels, and $30 < L \leq 50$ | +| For CA, the companies report whether the load is defined per CC or across all CCs. | | + +## 8.4.2 Observations + +When 320ms LP-SS periodicity, 4 or 8 beams and no more than 14 symbols LP-SS duration is assumed, + +- For zero load, results in [8A-3] [8A-11] [8A-13] show that additional increased network power consumption rate is (0.06%~3.9%); +- For low load, results in [8A-11] [8A-13] show that additional increased network power consumption rate is (0.07%~2.716%); +- For medium load, results in [8A-11] show that additional increased network power consumption rate is (0.388%~1.076%). + +When 320ms LP-SS periodicity, 4 beams and 28 symbols LP-SS duration is assumed, + +- For zero load, results in [8A-5] show that additional increased network power consumption rate is 0.122%; + +When 320ms LP-SS periodicity, 8 beams and 42 symbols LP-SS duration is assumed, + +- For zero load, results in [8A-3] show that additional increased network power consumption rate is 11.4%; + +Lower impact to the network power consumption is expected when LP-SS is transmitted FDM with NR SSB/SIB-1. + +LP-SS is assumed to be additional signal transmission than the existing NR signal/channels. + +## 8.5 System overhead + +### 8.5.1 Collection of the results + +Evaluation of the LP-WUS and LP-SS overhead are summarized in Table 8.5. And for more results and details, it can be found in Annex 8.5. + +#### 8.5.1.1 RRC IDLE/INACTIVE + +##### 8.5.1.1.1 LP-WUS + +The system overhead of LP-WUS for RRC IDLE/INACTIVE is summarized in Table 8.5.1-1. + +**Table 8.5.1-1: Summary of System overhead for LP-WUS for RRC IDLE/INACTIVE** + +| Source | Signal | # of info bits carried by signal | Overhead (%) | T resources per beam | F resources | SCS | number of paged UE per second | Number of LP-WUS transmissions per second | System configuration, e.g., BW and etc. | the target channel | LP-WUS MIL | Notes | +|---------|--------|----------------------------------|--------------|----------------------|-------------|-------|-------------------------------|-------------------------------------------|-----------------------------------------|--------------------|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| [8A-11] | LP-WUS | 1 | 0.0150% | 1 symbol | 5.04 MHz | 30kHz | 10 | 10 | 100MHz, 8beams | Msg .3 | 144.86 | For IoT, cases, Assuming 1,000,000 user/km2 connection density [ITU M.2412], with packet arrival every 1 message/2 hours/device [ITU M.2412], assuming 500m ISD with 3 sectors. The coverage of LP-WUS with 1/4/5 symbols is comparable to or better than Msg 3 coverage. OOK LP-WUS is assumed. | +| [8A-11] | LP-WUS | 1 | 0.0030% | 1 symbol | 5.04 MHz | 30kHz | 10 | 3 | 100MHz, 8beams | Msg .3 | 144.86 | | +| [8A-11] | LP-WUS | 8 | 0.0600% | 4 symbols | 5.04 MHz | 30kHz | 10 | 10 | 100MHz, 8beams | Msg .3 | 144.37 | | +| [8A-11] | LP-WUS | 8 | 0.0100% | 4 symbols | 5.04 MHz | 30kHz | 10 | 3 | 100MHz, 8beams | Msg .3 | 144.37 | | +| [8A-11] | LP-WUS | 8 or 12 | 0.0750% | 5 symbols | 5.04 MHz | 30kHz | 10 | 10 | 100MHz, 8beams | Msg .3 | 144.05 | | +| [8A-11] | LP-WUS | 8 or 12 | 0.0130% | 5 symbols | 5.04 MHz | 30kHz | 10 | 3 | 100MHz, 8beams | Msg .3 | 144.05 | | +| [8A-11] | LP-WUS | 1 | 0.0730% | 1 symbol | 5.04 MHz | 30kHz | 10 | 10 | 20MHz, 8beams | Msg .3 | 144.86 | | +| [8A-11] | LP-WUS | 1 | 0.0180% | 1 symbol | 5.04 MHz | 30kHz | 10 | 3 | 20MHz, 8beams | Msg .3 | 144.86 | | +| [8A-11] | LP-WUS | 8 | 0.2900% | 4 symbols | 5.04 MHz | 30kHz | 10 | 10 | 20MHz, 8beams | Msg .3 | 144.37 | | +| [8A-11] | LP-WUS | 8 | 0.0700% | 4 symbols | 5.04 MHz | 30kHz | 10 | 3 | 20MHz, 8beams | Msg .3 | 144.37 | | +| [8A-11] | LP-WUS | 8 or 12 | 0.3630% | 5 symbols | 5.04 MHz | 30kHz | 10 | 10 | 20MHz, 8beams | Msg .3 | 144.05 | | +| [8A-11] | LP-WUS | 8 or 12 | 0.0880% | 5 symbols | 5.04 MHz | 30kHz | 10 | 3 | 20MHz, 8beams | Msg .3 | 144.05 | | +| [8A-11] | LP-WUS | 1 | 0.0550% | 1 symbol | 5.04 MHz | 30kHz | 39 | 39 | 100MHz, 8beams | Msg .3 | 144.86 | | +| [8A-11] | LP-WUS | 1 | 0.0150% | 1 symbol | 5.04 MHz | 30kHz | 39 | 10 | 100MHz, 8beams | Msg .3 | 144.86 | | +| [8A-11] | LP-WUS | 8 | 0.2200% | 4 symbols | 5.04 MHz | 30kHz | 39 | 39 | 100MHz, 8beams | Msg .3 | 144.37 | | + +| | | | | | | | | | | | | | +|---------|---------------|---------|---------|----------------------------|----------|-------------|----------------------------------------------------------------------------------------------|----|-----------------------|--------|----------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| [8A-11] | LP-WUS | 8 | 0.0600% | 4 symbols | 5.04 MHz | 30kHz | 39 | 10 | 100MHz, 8beams | Msg .3 | 144.37 | 5,000 users/cell population density, and per UE paging arrival rate = 1% when paging i-DRX cycle is $T_{\text{pagingcycle}} = 1.28\text{s}$ The coverage of LP-WUS with 1/4/5 symbols is comparable to or better than Msg 3 coverage. OOK LP-WUS is assumed. | +| [8A-11] | LP-WUS | 8 or 12 | 0.2750% | 5 symbols | 5.04 MHz | 30kHz | 39 | 39 | 100MHz, 8beams | Msg .3 | 144.05 | | +| [8A-11] | LP-WUS | 8 or 12 | 0.0750% | 5 symbols | 5.04 MHz | 30kHz | 39 | 10 | 100MHz, 8beams | Msg .3 | 144.05 | | +| [8A-11] | LP-WUS | 1 | 0.2800% | 1 symbol | 5.04 MHz | 30kHz | 39 | 39 | 20MHz, 8beams | Msg .3 | 144.86 | | +| [8A-11] | LP-WUS | 1 | 0.0700% | 1 symbol | 5.04 MHz | 30kHz | 39 | 10 | 20MHz, 8beams | Msg .3 | 144.86 | | +| [8A-11] | LP-WUS | 8 | 1.1200% | 4 symbols | 5.04 MHz | 30kHz | 39 | 39 | 20MHz, 8beams | Msg .3 | 144.37 | | +| [8A-11] | LP-WUS | 8 | 0.2800% | 4 symbols | 5.04 MHz | 30kHz | 39 | 10 | 20MHz, 8beams | Msg .3 | 144.37 | | +| [8A-11] | LP-WUS | 8 or 12 | 1.4000% | 5 symbols | 5.04 MHz | 30kHz | 39 | 39 | 20MHz, 8beams | Msg .3 | 144.05 | | +| [8A-11] | LP-WUS | 8 or 12 | 0.3500% | 5 symbols | 5.04 MHz | 30kHz | 39 | 10 | 20MHz, 8beams | Msg .3 | 144.05 | | +| [8A-13] | LP-WUS | 8 | <1% | 7 or 14 symbols | 5MHz | 15KHz/30kHz | Paging rate:1%,0.1%,0.01%,0.001%; POs number per PF: 1,2,4; PFs number per cycle: 1,2,4,8,16 | | 20M, 100M; Beams:1, 4 | Msg .3 | For LP-WUS with 7 symbols, LP-WUS MIL is 152.28 ; For LP-WUS with 14 symbols, LP-WUS MIL is 156.94 | Only one case when 20M system bandwidth , 4beams, no grouping, 15KHz, 14OFDM symbols, paging rate 1%, maximum POs per PF, maximum PFs per cycle are configured, the system overhead may reach 1.6%. OOK LP-WUS is assumed. | +| [8A-5] | LP-WUS +LP-SS | 24 | 0.1230% | 12 symbols (no repetition) | 5MHz | 30KHz | 50 paging per second | 50 | 100M, 1 beam | | Sequence modulation w/o repetition: 149.06 Sequence on top of OOK with 3dB power | Resource overhead for 56kbps data rate, which corresponds to the following waveforms to match comparable Msg3 MIL: sequence | + +| | | | | | | | | | | | | | +|--------|--------------|----|---------|------------------------------|------|-------|----------------------|----|---------------|--|---------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | | | | | | | | | boosting:
149.36 | modulation w/o repetition Sequence on top of OOK with 3dB power boosting | +| [8A-5] | LP-WUS+LP-SS | 24 | 0.2300% | 24 symbols for 2 repetitions | 5MHz | 30KHz | 50 paging per second | 50 | 100M, 1 beam | | FSK-2 transmission with 2 repetitions:
149.18 Sequence on top of OOK/FSK with 2 repetitions:
151 | Resource overhead for 28kbps data rate, which corresponds to the following waveforms to match comparable Msg3 MIL:
FSK-2 transmission with 2 repetitions Sequence on top of OOK/FSK with 2 repetitions | +| [8A-5] | LP-WUS+LP-SS | 24 | 0.4440% | 48 symbols for 4 repetitions | 5MHz | 30KHz | 50 paging per second | 50 | 100M, 1 beam | | OOK transmission with 4 repetitions:
148.68 | Resource overhead for 14kbps data rate, which corresponds to the following waveforms to match comparable Msg3 MIL:
OOK transmission with 4 repetitions | +| [8A-5] | LP-WUS+LP-SS | 24 | 0.4910% | 12 symbols (no repetition) | 5MHz | 30KHz | 50 paging per second | 50 | 100M, 4 beams | | Sequence modulation w/o repetition:
149.06 Sequence on top of OOK with 3dB power boosting:
149.36 | Resource overhead for 56kbps data rate, which corresponds to the following waveforms to match comparable Msg3 MIL:
sequence modulation w/o repetition Sequence on top of OOK with 3dB power | + +| | | | | | | | | | | | | | +|---------|------------------|----|-------------|---------------------------------|------|-------|----------------------|--------|---------------|-------|--------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | | | | | | | | | | boosting | +| [8A-5] | LP-WUS
+LP-SS | 24 | 0.920
0% | 24 symbols
for 2 repetitions | 5MHz | 30KHz | 50 paging per second | 50 | 100M, 4 beams | | FSK-2 transmission with 2 repetitions: 149.18 Sequence on top of OOK/FSK with 2 repetitions: 151 | Resource overhead for 28kbps data rate, which corresponds to the following waveforms to match comparable Msg3 MIL: FSK-2 transmission with 2 repetitions Sequence on top of OOK/FSK with 2 repetitions | +| [8A-5] | LP-WUS
+LP-SS | 24 | 1.777
0% | 48 symbols
for 4 repetitions | 5MHz | 30KHz | 50 paging per second | 50 | 100M, 4 beams | | OOK transmission with 4 repetitions: 148.68 | Resource overhead for 14kbps data rate, which corresponds to the following waveforms to match comparable Msg3 MIL: OOK transmission with 4 repetitions | +| [8A-16] | LP-WUS | 6 | 0.169
2% | 0.6ms | 5MHz | 30KHz | 20 Groups I-DRX | 11.28 | 20MHz | Msg 3 | 147.44 | I-DRX cycle = 1.28sec | +| [8A-16] | LP-WUS | 6 | 0.169
2% | 0.6ms | 5MHz | 30KHz | 20 Groups, I-DRX | 11.28 | 20MHz | Msg 3 | 147.44 | I-DRX cycle = 1.28sec | +| [8A-16] | LP-WUS | 6 | 0.846
1% | 0.6ms | 5MHz | 30KHz | 100 Groups, I-DRX | 56.43 | 20MHz | Msg 3 | 147.44 | I-DRX cycle = 1.28sec | +| [8A-16] | LP-WUS | 6 | 0.846
1% | 0.6ms | 5MHz | 30KHz | 100 Groups, I-DRX | 56.43 | 20MHz | Msg 3 | 147.44 | I-DRX cycle = 1.28sec | +| [8A-16] | LP-WUS | 6 | 0.003
6% | 0.6ms | 5MHz | 30KHz | 20 Groups, eDRX | 0.2413 | 20MHz | Msg 3 | 147.44 | eDRX cycle = 82.9sec | +| [8A-16] | LP-WUS | 6 | 0.003
6% | 0.6ms | 5MHz | 30KHz | 20 Groups, | 0.2413 | 20MHz | Msg 3 | 147.44 | eDRX cycle = 82.9sec | +| [8A-16] | LP-WUS | 6 | 0.018
1% | 0.6ms | 5MHz | 30KHz | 100 Groups, eDRX | 1.2063 | 20MHz | Msg 3 | 147.44 | eDRX cycle = 82.9sec | +| [8A-16] | LP-WUS | 6 | 0.018
1% | 0.6ms | 5MHz | 30KHz | 100 Groups, eDRX | 1.2063 | 20MHz | Msg 3 | 147.44 | eDRX cycle = 82.9sec | +| [8A-4] | LP-WUS | 16 | | 24 OFDM symbols | 5MHz | 30KHz | 10 | 10 | 20MHz, 1 beam | Msg 3 | 154.68 | LP-WUS waveforms: OOK-4 when 24 OFDM symbols are used | +| [8A-4] | LP-WUS | 16 | 0.054
1% | 24 OFDM symbols | 5MHz | 30KHz | 10 | 2.5 | 20MHz, 1 beam | Msg 3 | 154.68 | | + +| | | | | | | | | | | | | | +|--------|--------|----|-------------|-------------------------------|------|-------|-----|-----|------------------|----------|--------|--| +| | | | | M
symb
ols | | | | | | | | | +| [8A-4] | LP-WUS | 16 | | 24
OFD
M
symb
ols | 5MHz | 30KHz | 10 | 10 | 20MHz,4
beam | Msg
3 | 154.68 | | +| [8A-4] | LP-WUS | 16 | 0.866
0% | 24
OFD
M
symb
ols | 5MHz | 30KHz | 10 | 2.5 | 20MHz,4
beam | Msg
3 | 154.68 | | +| [8A-4] | LP-WUS | 16 | 0.216
5% | 24
OFD
M
symb
ols | 5MHz | 30KHz | 10 | 10 | 20MHz,8
beam | Msg
3 | 154.68 | | +| [8A-4] | LP-WUS | 16 | 1.732
1% | 24
OFD
M
symb
ols | 5MHz | 30KHz | 10 | 2.5 | 20MHz,8
beam | Msg
3 | 154.68 | | +| [8A-4] | LP-WUS | 16 | 0.433
0% | 24
OFD
M
symb
ols | 5MHz | 30KHz | 10 | 10 | 100MHz,1
beam | Msg
3 | 154.68 | | +| [8A-4] | LP-WUS | 16 | 0.043
3% | 24
OFD
M
symb
ols | 5MHz | 30KHz | 10 | 2.5 | 100MHz,1
beam | Msg
3 | 154.68 | | +| [8A-4] | LP-WUS | 16 | 0.010
8% | 24
OFD
M
symb
ols | 5MHz | 30KHz | 10 | 10 | 100MHz,4
beam | Msg
3 | 154.68 | | +| [8A-4] | LP-WUS | 16 | 0.173
2% | 24
OFD
M
symb
ols | 5MHz | 30KHz | 10 | 2.5 | 100MHz,4
beam | Msg
3 | 154.68 | | +| [8A-4] | LP-WUS | 16 | 0.043
3% | 24
OFD
M
symb
ols | 5MHz | 30KHz | 10 | 10 | 100MHz,8
beam | Msg
3 | 154.68 | | +| [8A-4] | LP-WUS | 16 | 0.346
4% | 24
OFD
M
symb
ols | 5MHz | 30KHz | 10 | 2.5 | 100MHz,8
beam | Msg
3 | 154.68 | | +| [8A-4] | LP-WUS | 16 | 0.086
6% | 24
OFD
M
symb
ols | 5MHz | 30KHz | 0.8 | 0.8 | 20MHz,1
beam | Msg
3 | 154.68 | | +| [8A-4] | LP-WUS | 16 | 0.018
0% | 24
OFD
M
symb
ols | 5MHz | 30KHz | 0.8 | 0.2 | 20MHz,1
beam | Msg
3 | 154.68 | | +| [8A-4] | LP-WUS | 16 | 0.004
5% | 24
OFD
M
symb
ols | 5MHz | 30KHz | 0.8 | 0.8 | 20MHz,4b
eam | Msg
3 | 154.68 | | +| [8A-4] | LP-WUS | 16 | 0.072
2% | 24
OFD
M
symb
ols | 5MHz | 30KHz | 0.8 | 0.2 | 20MHz,4
beam | Msg
3 | 154.68 | | +| [8A-4] | LP-WUS | 16 | 0.018
0% | 24
OFD
M
symb
ols | 5MHz | 30KHz | 0.8 | 0.8 | 20MHz,8
beam | Msg
3 | 154.68 | | +| [8A-4] | LP-WUS | 16 | 0.144
3% | 24
OFD
M
symb
ols | 5MHz | 30KHz | 0.8 | 0.8 | 20MHz,8
beam | Msg
3 | 154.68 | | + +| | | | | | | | | | | | | | +|--------|--------|----|-------------|--------------------|------|-------|-----|-----|------------------|----------|--------|------------------------------------------------------------| +| | | | | symb
ols | | | | | | | | | +| [8A-4] | LP-WUS | 16 | 0.036
1% | 24 OFDM
symbols | 5MHz | 30KHz | 0.8 | 0.2 | 20MHz,8
beam | Msg
3 | 154.68 | | +| [8A-4] | LP-WUS | 16 | 0.003
6% | 24 OFDM
symbols | 5MHz | 30KHz | 0.8 | 0.8 | 100MHz,1
beam | Msg
3 | 154.68 | | +| [8A-4] | LP-WUS | 16 | 0.000
9% | 24 OFDM
symbols | 5MHz | 30KHz | 0.8 | 0.2 | 100MHz,1
beam | Msg
3 | 154.68 | | +| [8A-4] | LP-WUS | 16 | 0.014
4% | 24 OFDM
symbols | 5MHz | 30KHz | 0.8 | 0.8 | 100MHz,4
beam | Msg
3 | 154.68 | | +| [8A-4] | LP-WUS | 16 | 0.003
6% | 24 OFDM
symbols | 5MHz | 30KHz | 0.8 | 0.2 | 100MHz,4
beam | Msg
3 | 154.68 | | +| [8A-4] | LP-WUS | 16 | 0.028
9% | 24 OFDM
symbols | 5MHz | 30KHz | 0.8 | 0.8 | 100MHz,8
beam | Msg
3 | 154.68 | | +| [8A-4] | LP-WUS | 16 | 0.007
2% | 24 OFDM
symbols | 5MHz | 30KHz | 0.8 | 0.2 | 100MHz,8
beam | Msg
3 | 154.68 | | +| [8A-4] | LP-WUS | 16 | 0.108
3% | 12OFDM
symbols | 5MHz | 30KHz | 10 | 10 | 20MHz,1
beam | Msg
3 | 151.78 | LP-WUS waveform: FSK-2 (M=2) when 12 OFDM symbols are used | +| [8A-4] | LP-WUS | 16 | 0.027
1% | 12OFDM
symbols | 5MHz | 30KHz | 10 | 2.5 | 20MHz,1
beam | Msg
3 | 151.78 | | +| [8A-4] | LP-WUS | 16 | 0.433
0% | 12OFDM
symbols | 5MHz | 30KHz | 10 | 10 | 20MHz,4b
eam | Msg
3 | 151.78 | | +| [8A-4] | LP-WUS | 16 | 0.108
3% | 12OFDM
symbols | 5MHz | 30KHz | 10 | 2.5 | 20MHz,4
beam | Msg
3 | 151.78 | | +| [8A-4] | LP-WUS | 16 | 0.866
0% | 12OFDM
symbols | 5MHz | 30KHz | 10 | 10 | 20MHz,8
beam | Msg
3 | 151.78 | | +| [8A-4] | LP-WUS | 16 | 0.216
5% | 12OFDM
symbols | 5MHz | 30KHz | 10 | 2.5 | 20MHz,8
beam | Msg
3 | 151.78 | | +| [8A-4] | LP-WUS | 16 | 0.021
7% | 12OFDM
symbols | 5MHz | 30KHz | 10 | 10 | 100MHz,1
beam | Msg
3 | 151.78 | | +| [8A-4] | LP-WUS | 16 | 0.005
4% | 12OFDM
symbols | 5MHz | 30KHz | 10 | 2.5 | 100MHz,1
beam | Msg
3 | 151.78 | | +| [8A-4] | LP-WUS | 16 | 0.086
6% | 12OFDM
symbols | 5MHz | 30KHz | 10 | 10 | 100MHz,4
beam | Msg
3 | 151.78 | | +| [8A-4] | LP-WUS | 16 | 0.021
7% | 12OFDM
symbols | 5MHz | 30KHz | 10 | 2.5 | 100MHz,4
beam | Msg
3 | 151.78 | | + +| | | | | | | | | | | | | | +|--------|--------------------------|----|-------------|-----------------------|------|-------|------|------|------------------|----------------------|--------|-----------------------------------------------------------------------------| +| | | | | symbols | | | | | | | | | +| [8A-4] | LP-WUS | 16 | 0.173
2% | 12OF
DM
symbols | 5MHz | 30KHz | 10 | 10 | 100MHz,8
beam | Msg
3 | 151.78 | | +| [8A-4] | LP-WUS | 16 | 0.043
3% | 12OF
DM
symbols | 5MHz | 30KHz | 10 | 2.5 | 100MHz,8
beam | Msg
3 | 151.78 | | +| [8A-4] | LP-WUS | 16 | 0.009
0% | 12OF
DM
symbols | 5MHz | 30KHz | 0.8 | 0.8 | 20MHz,1
beam | Msg
3 | 151.78 | | +| [8A-4] | LP-WUS | 16 | 0.002
3% | 12OF
DM
symbols | 5MHz | 30KHz | 0.8 | 0.2 | 20MHz,1
beam | Msg
3 | 151.78 | | +| [8A-4] | LP-WUS | 16 | 0.036
1% | 12OF
DM
symbols | 5MHz | 30KHz | 0.8 | 0.8 | 20MHz,4b
eam | Msg
3 | 151.78 | | +| [8A-4] | LP-WUS | 16 | 0.009
0% | 12OF
DM
symbols | 5MHz | 30KHz | 0.8 | 0.2 | 20MHz,4
beam | Msg
3 | 151.78 | | +| [8A-4] | LP-WUS | 16 | 0.072
2% | 12OF
DM
symbols | 5MHz | 30KHz | 0.8 | 0.8 | 20MHz,8
beam | Msg
3 | 151.78 | | +| [8A-4] | LP-WUS | 16 | 0.018
0% | 12OF
DM
symbols | 5MHz | 30KHz | 0.8 | 0.2 | 20MHz,8
beam | Msg
3 | 151.78 | | +| [8A-4] | LP-WUS | 16 | 0.001
8% | 12OF
DM
symbols | 5MHz | 30KHz | 0.8 | 0.8 | 100MHz,1
beam | Msg
3 | 151.78 | | +| [8A-4] | LP-WUS | 16 | 0.000
5% | 12OF
DM
symbols | 5MHz | 30KHz | 0.8 | 0.2 | 100MHz,1
beam | Msg
3 | 151.78 | | +| [8A-4] | LP-WUS | 16 | 0.007
2% | 12OF
DM
symbols | 5MHz | 30KHz | 0.8 | 0.8 | 100MHz,4
beam | Msg
3 | 151.78 | | +| [8A-4] | LP-WUS | 16 | 0.001
8% | 12OF
DM
symbols | 5MHz | 30KHz | 0.8 | 0.2 | 100MHz,4
beam | Msg
3 | 151.78 | | +| [8A-4] | LP-WUS | 16 | 0.014
4% | 12OF
DM
symbols | 5MHz | 30KHz | 0.8 | 0.8 | 100MHz,8
beam | Msg
3 | 151.78 | | +| [8A-4] | LP-WUS | 16 | 0.003
6% | 12OF
DM
symbols | 5MHz | 30KHz | 0.8 | 0.2 | 100MHz,8
beam | Msg
3 | 151.78 | | +| [8A-3] | OOK
WUS
+LP-
SS | 1 | 0,042
7% | 5
slots | 5MHz | 30KHz | 0.25 | 0.25 | 20MHz,
1beam | Msg
3
0rtx | 149.23 | Assume
250 idle
UEs per
cell,
R_E=0.1
%,
1UE/subg
roup | +| [8A-3] | OOK
WUS
+LP-
SS | 1 | 0,051
9% | 8
slots | 5MHz | 30KHz | 0.25 | 0.25 | 20MHz,
1beam | Msg
3
2rtx | 153.23 | | +| [8A-3] | OOK
WUS
+LP-
SS | 1 | 0,054
9% | 9
slots | 5MHz | 30KHz | 0.25 | 0.25 | 20MHz,
1beam | PD
CC
H
1rx | 153.76 | | +| [8A-3] | OOK
WUS
+LP-
SS | 1 | 0,088
5% | 20
slots | 5MHz | 30KHz | 0.25 | 0.25 | 20MHz,
1beam | PD
CC
H
2rx | 156.76 | | +| [8A- | OOK | 8 | 0,058 | 10 | 5MHz | 30KHz | 0.25 | 0.25 | 20MHz, | Msg | 149.23 | | + +| | | | | | | | | | | | | +|--------|----------------------|----|--------------|------------------|-------------|-------|------|------|-----------------|----------------------|--------| +| 3] | WUS
+LP-SS | | 0% | slots | | | | | 1beam | 3
0rtx | | +| [8A-3] | OOK
WUS
+LP-SS | 8 | 0,112
9% | 28
slots | 5MHz | 30KHz | 0.25 | 0.25 | 20MHz,
1beam | Msg
3
2rtx | 153.23 | +| [8A-3] | OOK
WUS
+LP-SS | 8 | 0,143
4% | 38
slots | 5MHz | 30KHz | 0.25 | 0.25 | 20MHz,
1beam | PD
CC
H
1rx | 153.76 | +| [8A-3] | OOK
WUS
+LP-SS | 8 | 0,296
0% | 88
slots | 5MHz | 30KHz | 0.25 | 0.25 | 20MHz,
1beam | PD
CC
H
2rx | 156.76 | +| [8A-3] | OOK
WUS
+LP-SS | 48 | 0,125
1% | 32
slots | 5MHz | 30KHz | 0.25 | 0.25 | 20MHz,
1beam | Msg
3
0rtx | 149.23 | +| [8A-3] | OOK
WUS
+LP-SS | 48 | 0,384
5% | 117
slots | 5MHz | 30KHz | 0.25 | 0.25 | 20MHz,
1beam | Msg
3
2rtx | 153.23 | +| [8A-3] | OOK
WUS
+LP-SS | 48 | 0,454
7% | 140
slots | 5MHz | 30KHz | 0.25 | 0.25 | 20MHz,
1beam | PD
CC
H
1rx | 153.76 | +| [8A-3] | OOK
WUS
+LP-SS | 48 | 1,217
7% | 390
slots | 5MHz | 30KHz | 0.25 | 0.25 | 20MHz,
1beam | PD
CC
H
2rx | 156.76 | +| [8A-3] | OOK
WUS
+LP-SS | 1 | 0,341
8% | 5
slots | 5MHz | 30KHz | 0.25 | 0.25 | 20MHz,
8beam | Msg
3
0rtx | 149.23 | +| [8A-3] | OOK
WUS
+LP-SS | 1 | 0,415
0% | 8
slots | 5MHz | 30KHz | 0.25 | 0.25 | 20MHz,
8beam | Msg
3
2rtx | 153.23 | +| [8A-3] | OOK
WUS
+LP-SS | 1 | 0,439
5% | 9
slots | 5MHz | 30KHz | 0.25 | 0.25 | 20MHz,
8beam | PD
CC
H
1rx | 153.76 | +| [8A-3] | OOK
WUS
+LP-SS | 1 | 0,708
0% | 20
slots | 5MHz | 30KHz | 0.25 | 0.25 | 20MHz,
8beam | PD
CC
H
2rx | 156.76 | +| [8A-3] | OOK
WUS
+LP-SS | 8 | 0,463
9% | 10
slots | 5MHz | 30KHz | 0.25 | 0.25 | 20MHz,
8beam | Msg
3
0rtx | 149.23 | +| [8A-3] | OOK
WUS
+LP-SS | 8 | 0,903
3% | 28
slots | 5MHz | 30KHz | 0.25 | 0.25 | 20MHz,
8beam | Msg
3
2rtx | 153.23 | +| [8A-3] | OOK
WUS
+LP-SS | 8 | 1,147
5% | 38
slots | 5MHz | 30KHz | 0.25 | 0.25 | 20MHz,
8beam | PD
CC
H
1rx | 153.76 | +| [8A-3] | OOK
WUS
+LP-SS | 8 | 2,368
2% | 88
slots | 5MHz | 30KHz | 0.25 | 0.25 | 20MHz,
8beam | PD
CC
H
2rx | 156.76 | +| [8A-3] | OOK
WUS
+LP-SS | 48 | 1,001
0% | 32
slots | 5MHz | 30KHz | 0.25 | 0.25 | 20MHz,
8beam | Msg
3
0rtx | 149.23 | +| [8A-3] | OOK
WUS
+LP-SS | 48 | 3,076
2% | 117
slots | 5MHz | 30KHz | 0.25 | 0.25 | 20MHz,
8beam | Msg
3
2rtx | 153.23 | +| [8A-3] | OFD
M
WUS | 1 | 0,000
66% | 4
symb
ols | 3.81
MHz | 30KHz | 0.25 | 0.25 | 20MHz,
1beam | Msg
3
0rtx | 149.23 | +| [8A-3] | OFD | 1 | 0,000 | 5 | 3.81 | 30KHz | 0.25 | 0.25 | 20MHz, | Msg | 153.23 | + +| | | | | | | | | | | | | | +|--------|----------------|---|-----------|-------------|----------|-------|------|------|--------------|-------------|--------|--------------------------------------------------------| +| 3] | M WUS | | 83% | symb ols | MHz | | | | 1beam | 3 2rtx | | | +| [8A-3] | OFD M WUS | 1 | 0,001 00% | 6 symb ols | 3.81 MHz | 30KHz | 0.25 | 0.25 | 20MHz, 1beam | PD CC H 1rx | 153.76 | | +| [8A-3] | OFD M WUS | 1 | 0,001 83% | 11 symb ols | 3.81 MHz | 30KHz | 0.25 | 0.25 | 20MHz, 1beam | PD CC H 2rx | 156.76 | | +| [8A-3] | OFD M WUS | 8 | 0,001 99% | 12 symb ols | 3.81 MHz | 30KHz | 0.25 | 0.25 | 20MHz, 1beam | Msg 3 0rtx | 149.23 | | +| [8A-3] | OFD M WUS | 8 | 0,001 99% | 12 symb ols | 3.81 MHz | 30KHz | 0.25 | 0.25 | 20MHz, 1beam | Msg 3 2rtx | 153.23 | | +| [8A-3] | OFD M WUS | 8 | 0,001 99% | 12 symb ols | 3.81 MHz | 30KHz | 0.25 | 0.25 | 20MHz, 1beam | PD CC H 1rx | 153.76 | | +| [8A-3] | OFD M WUS | 8 | 0,002 49% | 15 symb ols | 3.81 MHz | 30KHz | 0.25 | 0.25 | 20MHz, 1beam | PD CC H 2rx | 156.76 | | +| [8A-3] | OFD M WUS | 1 | 0,005 32% | 4 symb ols | 3.81 MHz | 30KHz | 0.25 | 0.25 | 20MHz, 8beam | Msg 3 0rtx | 149.23 | | +| [8A-3] | OFD M WUS | 1 | 0,006 64% | 5 symb ols | 3.81 MHz | 30KHz | 0.25 | 0.25 | 20MHz, 8beam | Msg 3 2rtx | 153.23 | | +| [8A-3] | OFD M WUS | 1 | 0,007 97% | 6 symb ols | 3.81 MHz | 30KHz | 0.25 | 0.25 | 20MHz, 8beam | PD CC H 1rx | 153.76 | | +| [8A-3] | OFD M WUS | 1 | 0,014 62% | 11 symb ols | 3.81 MHz | 30KHz | 0.25 | 0.25 | 20MHz, 8beam | PD CC H 2rx | 156.76 | | +| [8A-3] | OFD M WUS | 8 | 0,015 95% | 12 symb ols | 3.81 MHz | 30KHz | 0.25 | 0.25 | 20MHz, 8beam | Msg 3 0rtx | 149.23 | | +| [8A-3] | OFD M WUS | 8 | 0,015 95% | 12 symb ols | 3.81 MHz | 30KHz | 0.25 | 0.25 | 20MHz, 8beam | Msg 3 2rtx | 153.23 | | +| [8A-3] | OFD M WUS | 8 | 0,015 95% | 12 symb ols | 3.81 MHz | 30KHz | 0.25 | 0.25 | 20MHz, 8beam | PD CC H 1rx | 153.76 | | +| [8A-3] | OFD M WUS | 8 | 0,019 93% | 15 symb ols | 3.81 MHz | 30KHz | 0.25 | 0.25 | 20MHz, 8beam | PD CC H 2rx | 156.76 | | +| [8A-3] | OOK WUS +LP-SS | 1 | 0,042 7% | 5 slots | 5MHz | 30KHz | 0.25 | 0.25 | 20MHz, 1beam | Msg 3 0rtx | 149.23 | Assume 250 idle UEs per cell, R_E=0.1 %, 4UE/subg roup | +| [8A-3] | OOK WUS +LP-SS | 1 | 0,051 9% | 8 slots | 5MHz | 30KHz | 0.25 | 0.25 | 20MHz, 1beam | Msg 3 2rtx | 153.23 | | +| [8A-3] | OOK WUS +LP-SS | 1 | 0,054 9% | 9 slots | 5MHz | 30KHz | 0.25 | 0.25 | 20MHz, 1beam | PD CC H 1rx | 153.76 | | +| [8A-3] | OOK WUS +LP-SS | 1 | 0,088 5% | 20 slots | 5MHz | 30KHz | 0.25 | 0.25 | 20MHz, 1beam | PD CC H 2rx | 156.76 | | +| [8A-3] | OOK WUS +LP-SS | 8 | 0,058 0% | 10 slots | 5MHz | 30KHz | 0.25 | 0.25 | 20MHz, 1beam | Msg 3 0rtx | 149.23 | | +| [8A-3] | OOK WUS +LP- | 8 | 0,112 9% | 28 slots | 5MHz | 30KHz | 0.25 | 0.25 | 20MHz, 1beam | Msg 3 2rtx | 153.23 | | + +| | SS | | | | | | | | | | | +|--------|----------------|---|-----------|------------|----------|-------|------|------|--------------|-------------|--------| +| [8A-3] | OOK WUS +LP-SS | 8 | 0,143 4% | 38 slots | 5MHz | 30KHz | 0.25 | 0.25 | 20MHz, 1beam | PD CC H 1rx | 153.76 | +| [8A-3] | OOK WUS +LP-SS | 8 | 0,296 0% | 88 slots | 5MHz | 30KHz | 0.25 | 0.25 | 20MHz, 1beam | PD CC H 2rx | 156.76 | +| [8A-3] | OOK WUS +LP-SS | 1 | 0,341 8% | 5 slots | 5MHz | 30KHz | 0.25 | 0.25 | 20MHz, 8beam | Msg 3 0rtx | 149.23 | +| [8A-3] | OOK WUS +LP-SS | 1 | 0,415 0% | 8 slots | 5MHz | 30KHz | 0.25 | 0.25 | 20MHz, 8beam | Msg 3 2rtx | 153.23 | +| [8A-3] | OOK WUS +LP-SS | 1 | 0,439 5% | 9 slots | 5MHz | 30KHz | 0.25 | 0.25 | 20MHz, 8beam | PD CC H 1rx | 153.76 | +| [8A-3] | OOK WUS +LP-SS | 1 | 0,708 0% | 20 slots | 5MHz | 30KHz | 0.25 | 0.25 | 20MHz, 8beam | PD CC H 2rx | 156.76 | +| [8A-3] | OOK WUS +LP-SS | 8 | 0,463 9% | 10 slots | 5MHz | 30KHz | 0.25 | 0.25 | 20MHz, 8beam | Msg 3 0rtx | 149.23 | +| [8A-3] | OOK WUS +LP-SS | 8 | 0,903 3% | 28 slots | 5MHz | 30KHz | 0.25 | 0.25 | 20MHz, 8beam | Msg 3 2rtx | 153.23 | +| [8A-3] | OOK WUS +LP-SS | 8 | 1,147 5% | 38 slots | 5MHz | 30KHz | 0.25 | 0.25 | 20MHz, 8beam | PD CC H 1rx | 153.76 | +| [8A-3] | OOK WUS +LP-SS | 8 | 2,368 2% | 88 slots | 5MHz | 30KHz | 0.25 | 0.25 | 20MHz, 8beam | PD CC H 2rx | 156.76 | +| [8A-3] | OFD M WUS | 1 | 0,000 66% | 4 symbols | 3.81 MHz | 30KHz | 0.25 | 0.25 | 20MHz, 1beam | Msg 3 0rtx | 149.23 | +| [8A-3] | OFD M WUS | 1 | 0,000 83% | 5 symbols | 3.81 MHz | 30KHz | 0.25 | 0.25 | 20MHz, 1beam | Msg 3 2rtx | 153.23 | +| [8A-3] | OFD M WUS | 1 | 0,001 00% | 6 symbols | 3.81 MHz | 30KHz | 0.25 | 0.25 | 20MHz, 1beam | PD CC H 1rx | 153.76 | +| [8A-3] | OFD M WUS | 1 | 0,001 83% | 11 symbols | 3.81 MHz | 30KHz | 0.25 | 0.25 | 20MHz, 1beam | PD CC H 2rx | 156.76 | +| [8A-3] | OFD M WUS | 8 | 0,001 99% | 12 symbols | 3.81 MHz | 30KHz | 0.25 | 0.25 | 20MHz, 1beam | Msg 3 0rtx | 149.23 | +| [8A-3] | OFD M WUS | 8 | 0,001 99% | 12 symbols | 3.81 MHz | 30KHz | 0.25 | 0.25 | 20MHz, 1beam | Msg 3 2rtx | 153.23 | +| [8A-3] | OFD M WUS | 8 | 0,001 99% | 12 symbols | 3.81 MHz | 30KHz | 0.25 | 0.25 | 20MHz, 1beam | PD CC H 1rx | 153.76 | +| [8A-3] | OFD M WUS | 8 | 0,002 49% | 15 symbols | 3.81 MHz | 30KHz | 0.25 | 0.25 | 20MHz, 1beam | PD CC H 2rx | 156.76 | +| [8A-3] | OFD M WUS | 1 | 0,005 32% | 4 symbols | 3.81 MHz | 30KHz | 0.25 | 0.25 | 20MHz, 8beam | Msg 3 0rtx | 149.23 | +| [8A-3] | OFD M WUS | 1 | 0,006 64% | 5 symbols | 3.81 MHz | 30KHz | 0.25 | 0.25 | 20MHz, 8beam | Msg 3 2rtx | 153.23 | + +| | | | | | | | | | | | | | +|--------|----------------|----|-----------|------------|----------|-------|------|------|--------------|-------------|--------|----------------------------------------------------| +| [8A-3] | OFDM WUS | 1 | 0,007 97% | 6 symbols | 3.81 MHz | 30KHz | 0.25 | 0.25 | 20MHz, 8beam | PD CC H 1rx | 153.76 | | +| [8A-3] | OFDM WUS | 1 | 0,014 62% | 11 symbols | 3.81 MHz | 30KHz | 0.25 | 0.25 | 20MHz, 8beam | PD CC H 2rx | 156.76 | | +| [8A-3] | OFDM WUS | 8 | 0,015 95% | 12 symbols | 3.81 MHz | 30KHz | 0.25 | 0.25 | 20MHz, 8beam | Msg 3 0rtx | 149.23 | | +| [8A-3] | OFDM WUS | 8 | 0,015 95% | 12 symbols | 3.81 MHz | 30KHz | 0.25 | 0.25 | 20MHz, 8beam | Msg 3 2rtx | 153.23 | | +| [8A-3] | OFDM WUS | 8 | 0,015 95% | 12 symbols | 3.81 MHz | 30KHz | 0.25 | 0.25 | 20MHz, 8beam | PD CC H 1rx | 153.76 | | +| [8A-3] | OFDM WUS | 8 | 0,019 93% | 15 symbols | 3.81 MHz | 30KHz | 0.25 | 0.25 | 20MHz, 8beam | PD CC H 2rx | 156.76 | | +| [8A-3] | | | | | | | | | | | | | +| [8A-3] | OOK WUS +LP-SS | 1 | 0,097 7% | 5 slots | 5MHz | 30KHz | 2.5 | 2.5 | 20MHz, 1beam | Msg 3 0rtx | 149.23 | Assume 250 idle UEs per cell, R_E=1%, 1UE/subgroup | +| [8A-3] | OOK WUS +LP-SS | 1 | 0,189 2% | 8 slots | 5MHz | 30KHz | 2.5 | 2.5 | 20MHz, 1beam | Msg 3 2rtx | 153.23 | | +| [8A-3] | OOK WUS +LP-SS | 1 | 0,219 7% | 9 slots | 5MHz | 30KHz | 2.5 | 2.5 | 20MHz, 1beam | PD CC H 1rx | 153.76 | | +| [8A-3] | OOK WUS +LP-SS | 1 | 0,555 4% | 20 slots | 5MHz | 30KHz | 2.5 | 2.5 | 20MHz, 1beam | PD CC H 2rx | 156.76 | | +| [8A-3] | OOK WUS +LP-SS | 8 | 0,247 7% | 10 slots | 5MHz | 30KHz | 2.5 | 2.47 | 20MHz, 1beam | Msg 3 0rtx | 149.23 | | +| [8A-3] | OOK WUS +LP-SS | 8 | 0,790 4% | 28 slots | 5MHz | 30KHz | 2.5 | 2.47 | 20MHz, 1beam | Msg 3 2rtx | 153.23 | | +| [8A-3] | OOK WUS +LP-SS | 8 | 1,091 9% | 38 slots | 5MHz | 30KHz | 2.5 | 2.47 | 20MHz, 1beam | PD CC H 1rx | 153.76 | | +| [8A-3] | OOK WUS +LP-SS | 8 | 2,599 5% | 88 slots | 5MHz | 30KHz | 2.5 | 2.47 | 20MHz, 1beam | PD CC H 2rx | 156.76 | | +| [8A-3] | OOK WUS +LP-SS | 48 | 0,921 6% | 32 slots | 5MHz | 30KHz | 2.5 | 2.5 | 20MHz, 1beam | Msg 3 0rtx | 149.23 | | +| [8A-3] | OOK WUS +LP-SS | 48 | 3,515 6% | 117 slots | 5MHz | 30KHz | 2.5 | 2.5 | 20MHz, 1beam | Msg 3 2rtx | 153.23 | | +| [8A-3] | OOK WUS +LP-SS | 48 | 4,217 5% | 140 slots | 5MHz | 30KHz | 2.5 | 2.5 | 20MHz, 1beam | PD CC H 1rx | 153.76 | | +| [8A-3] | OOK WUS +LP-SS | 48 | 11,84 69% | 390 slots | 5MHz | 30KHz | 2.5 | 2.5 | 20MHz, 1beam | PD CC H 2rx | 156.76 | | +| [8A-3] | OOK WUS +LP- | 1 | 0,781 3% | 5 slots | 5MHz | 30KHz | 2.5 | 2.5 | 20MHz, 8beam | Msg 3 0rtx | 149.23 | | + +| | SS | | | | | | | | | | | +|--------|----------------|---|-----------|-------------|----------|-------|-----|------|--------------|-------------|--------| +| [8A-3] | OOK WUS +LP-SS | 1 | 1,513 7% | 8 slots | 5MHz | 30KHz | 2.5 | 2.5 | 20MHz, 8beam | Msg 3 2rtx | 153.23 | +| [8A-3] | OOK WUS +LP-SS | 1 | 1,757 8% | 9 slots | 5MHz | 30KHz | 2.5 | 2.5 | 20MHz, 8beam | PD CC H 1rx | 153.76 | +| [8A-3] | OOK WUS +LP-SS | 1 | 4,443 4% | 20 slots | 5MHz | 30KHz | 2.5 | 2.5 | 20MHz, 8beam | PD CC H 2rx | 156.76 | +| [8A-3] | OOK WUS +LP-SS | 8 | 1,981 4% | 10 slots | 5MHz | 30KHz | 2.5 | 2.47 | 20MHz, 8beam | Msg 3 0rtx | 149.23 | +| [8A-3] | OOK WUS +LP-SS | 8 | 6,323 2% | 28 slots | 5MHz | 30KHz | 2.5 | 2.47 | 20MHz, 8beam | Msg 3 2rtx | 153.23 | +| [8A-3] | OOK WUS +LP-SS | 8 | 8,735 4% | 38 slots | 5MHz | 30KHz | 2.5 | 2.47 | 20MHz, 8beam | PD CC H 1rx | 153.76 | +| [8A-3] | OOK WUS +LP-SS | 8 | 20,79 59% | 88 slots | 5MHz | 30KHz | 2.5 | 2.47 | 20MHz, 8beam | PD CC H 2rx | 156.76 | +| [8A-3] | OFD M WUS | 1 | 0,006 6% | 4 symb ols | 3.81 MHz | 30KHz | 2.5 | 2.5 | 20MHz, 1beam | Msg 3 0rtx | 149.23 | +| [8A-3] | OFD M WUS | 1 | 0,008 3% | 5 symb ols | 3.81 MHz | 30KHz | 2.5 | 2.5 | 20MHz, 1beam | Msg 3 2rtx | 153.23 | +| [8A-3] | OFD M WUS | 1 | 0,010 0% | 6 symb ols | 3.81 MHz | 30KHz | 2.5 | 2.5 | 20MHz, 1beam | PD CC H 1rx | 153.76 | +| [8A-3] | OFD M WUS | 1 | 0,018 3% | 11 symb ols | 3.81 MHz | 30KHz | 2.5 | 2.5 | 20MHz, 1beam | PD CC H 2rx | 156.76 | +| [8A-3] | OFD M WUS | 8 | 0,019 7% | 12 symb ols | 3.81 MHz | 30KHz | 2.5 | 2.47 | 20MHz, 1beam | Msg 3 0rtx | 149.23 | +| [8A-3] | OFD M WUS | 8 | 0,019 7% | 12 symb ols | 3.81 MHz | 30KHz | 2.5 | 2.47 | 20MHz, 1beam | Msg 3 2rtx | 153.23 | +| [8A-3] | OFD M WUS | 8 | 0,019 7% | 12 symb ols | 3.81 MHz | 30KHz | 2.5 | 2.47 | 20MHz, 1beam | PD CC H 1rx | 153.76 | +| [8A-3] | OFD M WUS | 8 | 0,024 6% | 15 symb ols | 3.81 MHz | 30KHz | 2.5 | 2.47 | 20MHz, 1beam | PD CC H 2rx | 156.76 | +| [8A-3] | OFD M WUS | 1 | 0,053 2% | 4 symb ols | 3.81 MHz | 30KHz | 2.5 | 2.5 | 20MHz, 8beam | Msg 3 0rtx | 149.23 | +| [8A-3] | OFD M WUS | 1 | 0,066 4% | 5 symb ols | 3.81 MHz | 30KHz | 2.5 | 2.5 | 20MHz, 8beam | Msg 3 2rtx | 153.23 | +| [8A-3] | OFD M WUS | 1 | 0,079 7% | 6 symb ols | 3.81 MHz | 30KHz | 2.5 | 2.5 | 20MHz, 8beam | PD CC H 1rx | 153.76 | +| [8A-3] | OFD M WUS | 1 | 0,146 2% | 11 symb ols | 3.81 MHz | 30KHz | 2.5 | 2.5 | 20MHz, 8beam | PD CC H 2rx | 156.76 | +| [8A-3] | OFD M WUS | 8 | 0,157 5% | 12 symb ols | 3.81 MHz | 30KHz | 2.5 | 2.47 | 20MHz, 8beam | Msg 3 0rtx | 149.23 | +| [8A- | OFD | 8 | 0,157 | 12 | 3.81 | 30KHz | 2.5 | 2.47 | 20MHz, | Msg | 153.23 | + +| | | | | | | | | | | | | | +|--------|----------------|---|-----------|-------------|----------|-------|-----|------|--------------|-------------|--------|-----------------------------------------------------| +| 3] | M WUS | | 5% | symb ols | MHz | | | | 8beam | 3 2rtx | | | +| [8A-3] | OFD M WUS | 8 | 0,157 5% | 12 symb ols | 3.81 MHz | 30KHz | 2.5 | 2.47 | 20MHz, 8beam | PD CC H 1rx | 153.76 | | +| [8A-3] | OFD M WUS | 8 | 0,196 9% | 15 symb ols | 3.81 MHz | 30KHz | 2.5 | 2.47 | 20MHz, 8beam | PD CC H 2rx | 156.76 | | +| [8A-3] | OOK WUS +LP-SS | 1 | 0,097 2% | 5 slots | 5MHz | 30KHz | 2.5 | 2.48 | 20MHz, 1beam | Msg 3 0rtx | 149.23 | Assume 250 idle UEs per cell, R_E=1%, 4UE/subg roup | +| [8A-3] | OOK WUS +LP-SS | 1 | 0,188 0% | 8 slots | 5MHz | 30KHz | 2.5 | 2.48 | 20MHz, 1beam | Msg 3 2rtx | 153.23 | | +| [8A-3] | OOK WUS +LP-SS | 1 | 0,218 3% | 9 slots | 5MHz | 30KHz | 2.5 | 2.48 | 20MHz, 1beam | PD CC H 1rx | 153.76 | | +| [8A-3] | OOK WUS +LP-SS | 1 | 0,551 3% | 20 slots | 5MHz | 30KHz | 2.5 | 2.48 | 20MHz, 1beam | PD CC H 2rx | 156.76 | | +| [8A-3] | OOK WUS +LP-SS | 8 | 0,224 6% | 10 slots | 5MHz | 30KHz | 2.5 | 2.2 | 20MHz, 1beam | Msg 3 0rtx | 149.23 | | +| [8A-3] | OOK WUS +LP-SS | 8 | 0,708 0% | 28 slots | 5MHz | 30KHz | 2.5 | 2.2 | 20MHz, 1beam | Msg 3 2rtx | 153.23 | | +| [8A-3] | OOK WUS +LP-SS | 8 | 0,976 6% | 38 slots | 5MHz | 30KHz | 2.5 | 2.2 | 20MHz, 1beam | PD CC H 1rx | 153.76 | | +| [8A-3] | OOK WUS +LP-SS | 8 | 2,319 3% | 88 slots | 5MHz | 30KHz | 2.5 | 2.2 | 20MHz, 1beam | PD CC H 2rx | 156.76 | | +| [8A-3] | OOK WUS +LP-SS | 1 | 0,777 3% | 5 slots | 5MHz | 30KHz | 2.5 | 2.48 | 20MHz, 8beam | Msg 3 0rtx | 149.23 | | +| [8A-3] | OOK WUS +LP-SS | 1 | 1,503 9% | 8 slots | 5MHz | 30KHz | 2.5 | 2.48 | 20MHz, 8beam | Msg 3 2rtx | 153.23 | | +| [8A-3] | OOK WUS +LP-SS | 1 | 1,746 1% | 9 slots | 5MHz | 30KHz | 2.5 | 2.48 | 20MHz, 8beam | PD CC H 1rx | 153.76 | | +| [8A-3] | OOK WUS +LP-SS | 1 | 4,410 2% | 20 slots | 5MHz | 30KHz | 2.5 | 2.48 | 20MHz, 8beam | PD CC H 2rx | 156.76 | | +| [8A-3] | OOK WUS +LP-SS | 8 | 1,796 9% | 10 slots | 5MHz | 30KHz | 2.5 | 2.2 | 20MHz, 8beam | Msg 3 0rtx | 149.23 | | +| [8A-3] | OOK WUS +LP-SS | 8 | 5,664 1% | 28 slots | 5MHz | 30KHz | 2.5 | 2.2 | 20MHz, 8beam | Msg 3 2rtx | 153.23 | | +| [8A-3] | OOK WUS +LP-SS | 8 | 7,812 5% | 38 slots | 5MHz | 30KHz | 2.5 | 2.2 | 20MHz, 8beam | PD CC H 1rx | 153.76 | | +| [8A-3] | OOK WUS +LP-SS | 8 | 18,55 47% | 88 slots | 5MHz | 30KHz | 2.5 | 2.2 | 20MHz, 8beam | PD CC H 2rx | 156.76 | | +| [8A- | OFD | 1 | 0,006 | 4 | 3.81 | 30KHz | 2.5 | 2.48 | 20MHz, | Msg | 149.23 | | + +| | | | | | | | | | | | | | +|--------|-----------|----|----------|-------------|----------|-------|-----|------|--------------|-------------|--------|---------------------------------------------------------------------------------------------------| +| 3] | M WUS | | 6% | symb ols | MHz | | | | 1beam | 3 0rtx | | | +| [8A-3] | OFD M WUS | 1 | 0,008 2% | 5 symb ols | 3.81 MHz | 30KHz | 2.5 | 2.48 | 20MHz, 1beam | Msg 3 2rtx | 153.23 | | +| [8A-3] | OFD M WUS | 1 | 0,009 9% | 6 symb ols | 3.81 MHz | 30KHz | 2.5 | 2.48 | 20MHz, 1beam | PD CC H 1rx | 153.76 | | +| [8A-3] | OFD M WUS | 1 | 0,018 1% | 11 symb ols | 3.81 MHz | 30KHz | 2.5 | 2.48 | 20MHz, 1beam | PD CC H 2rx | 156.76 | | +| [8A-3] | OFD M WUS | 8 | 0,017 5% | 12 symb ols | 3.81 MHz | 30KHz | 2.5 | 2.2 | 20MHz, 1beam | Msg 3 0rtx | 149.23 | | +| [8A-3] | OFD M WUS | 8 | 0,017 5% | 12 symb ols | 3.81 MHz | 30KHz | 2.5 | 2.2 | 20MHz, 1beam | Msg 3 2rtx | 153.23 | | +| [8A-3] | OFD M WUS | 8 | 0,017 5% | 12 symb ols | 3.81 MHz | 30KHz | 2.5 | 2.2 | 20MHz, 1beam | PD CC H 1rx | 153.76 | | +| [8A-3] | OFD M WUS | 8 | 0,021 9% | 15 symb ols | 3.81 MHz | 30KHz | 2.5 | 2.2 | 20MHz, 1beam | PD CC H 2rx | 156.76 | | +| [8A-3] | OFD M WUS | 1 | 0,052 7% | 4 symb ols | 3.81 MHz | 30KHz | 2.5 | 2.48 | 20MHz, 8beam | Msg 3 0rtx | 149.23 | | +| [8A-3] | OFD M WUS | 1 | 0,065 9% | 5 symb ols | 3.81 MHz | 30KHz | 2.5 | 2.48 | 20MHz, 8beam | Msg 3 2rtx | 153.23 | | +| [8A-3] | OFD M WUS | 1 | 0,079 1% | 6 symb ols | 3.81 MHz | 30KHz | 2.5 | 2.48 | 20MHz, 8beam | PD CC H 1rx | 153.76 | | +| [8A-3] | OFD M WUS | 1 | 0,145 0% | 11 symb ols | 3.81 MHz | 30KHz | 2.5 | 2.48 | 20MHz, 8beam | PD CC H 2rx | 156.76 | | +| [8A-3] | OFD M WUS | 8 | 0,140 3% | 12 symb ols | 3.81 MHz | 30KHz | 2.5 | 2.2 | 20MHz, 8beam | Msg 3 0rtx | 149.23 | | +| [8A-3] | OFD M WUS | 8 | 0,140 3% | 12 symb ols | 3.81 MHz | 30KHz | 2.5 | 2.2 | 20MHz, 8beam | Msg 3 2rtx | 153.23 | | +| [8A-3] | OFD M WUS | 8 | 0,140 3% | 12 symb ols | 3.81 MHz | 30KHz | 2.5 | 2.2 | 20MHz, 8beam | PD CC H 1rx | 153.76 | | +| [8A-3] | OFD M WUS | 8 | 0,175 4% | 15 symb ols | 3.81 MHz | 30KHz | 2.5 | 2.2 | 20MHz, 8beam | PD CC H 2rx | 156.76 | | +| [8A-9] | LP- WUS | 48 | 0,072 0% | 8 | 5.04 | 30 | 10 | 10 | 20 | Msg 3 | 143.78 | 1 beam LP-WUS is assumed. OOK-4 when 8 OFDM symbols are used. OOK-1 when 64 OFDM symbols are used | +| [8A-9] | LP- WUS | 48 | 0.280 8% | 8 | 5.04 | 30 | 39 | 39 | 20 | Msg 3 | 143.78 | | +| [8A-9] | LP- WUS | 48 | 0.360 0% | 8 | 5.04 | 30 | 50 | 50 | 20 | Msg 3 | 143.78 | | +| [8A-9] | LP- WUS | 48 | 0.576 0% | 64 | 5.04 | 30 | 10 | 10 | 20 | Msg 3 | 141.49 | | +| [8A-9] | LP- WUS | 48 | 2.246 4% | 64 | 5.04 | 30 | 39 | 39 | 20 | Msg 3 | 141.49 | | +| [8A-9] | LP- WUS | 48 | 2.880 0% | 64 | 5.04 | 30 | 50 | 50 | 20 | Msg 3 | 141.49 | | +| [8A-9] | LP- WUS | 48 | 0.014 4% | 8 | 5.04 | 30 | 10 | 10 | 100 | Msg 3 | 143.78 | | +| [8A-9] | LP- WUS | 48 | 0,056 2% | 8 | 5.04 | 30 | 39 | 39 | 100 | Msg 3 | 143.78 | | +| [8A-9] | LP- WUS | 48 | 0.072 0% | 8 | 5.04 | 30 | 50 | 50 | 100 | Msg 3 | 143.78 | | +| [8A-9] | LP- WUS | 48 | 0.115 2% | 64 | 5.04 | 30 | 10 | 10 | 100 | Msg 3 | 141.49 | | + +| | | | | | | | | | | | | +|--------|--------|----|-------------|----|------|----|----|-----|-----|----------|--------| +| [8A-9] | LP-WUS | 48 | 0.449
3% | 64 | 5.04 | 30 | 39 | 39 | 100 | Msg
3 | 141.49 | +| [8A-9] | LP-WUS | 48 | 0.576
0% | 64 | 5.04 | 30 | 50 | 50 | 100 | Msg
3 | 141.49 | +| [8A-9] | LP-WUS | 48 | 0.007
2% | 8 | 5.04 | 30 | 10 | 1 | 20 | Msg
3 | 143.78 | +| [8A-9] | LP-WUS | 48 | 0.028
1% | 8 | 5.04 | 30 | 39 | 3.9 | 20 | Msg
3 | 143.78 | +| [8A-9] | LP-WUS | 48 | 0.036
0% | 8 | 5.04 | 30 | 50 | 5 | 20 | Msg
3 | 143.78 | +| [8A-9] | LP-WUS | 48 | 0.057
6% | 64 | 5.04 | 30 | 10 | 1 | 20 | Msg
3 | 141.49 | +| [8A-9] | LP-WUS | 48 | 0.224
6% | 64 | 5.04 | 30 | 39 | 3.9 | 20 | Msg
3 | 141.49 | +| [8A-9] | LP-WUS | 48 | 0.288
0% | 64 | 5.04 | 30 | 50 | 5 | 20 | Msg
3 | 141.49 | +| [8A-9] | LP-WUS | 48 | 0.001
4% | 8 | 5.04 | 30 | 10 | 1 | 100 | Msg
3 | 143.78 | +| [8A-9] | LP-WUS | 48 | 0.005
6% | 8 | 5.04 | 30 | 39 | 3.9 | 100 | Msg
3 | 143.78 | +| [8A-9] | LP-WUS | 48 | 0.007
2% | 8 | 5.04 | 30 | 50 | 5 | 100 | Msg
3 | 143.78 | +| [8A-9] | LP-WUS | 48 | 0.011
5% | 64 | 5.04 | 30 | 10 | 1 | 100 | Msg
3 | 141.49 | +| [8A-9] | LP-WUS | 48 | 0.044
9% | 64 | 5.04 | 30 | 39 | 3.9 | 100 | Msg
3 | 141.49 | +| [8A-9] | LP-WUS | 48 | 0.057
6% | 64 | 5.04 | 30 | 50 | 5 | 100 | Msg
3 | 141.49 | + +### 8.5.1.1.2 LP-SS + +The System overhead of LP-SS for RRC IDLE/INACTIVE is summarized in Table 8.5.1-2 + +**Table 8.5.1-2: Summary of System overhead for LP-SS for RRC IDLE/INACTIVE** + +| Source | Signal | Overhead (%) | T resources per beam | F resources | SCS | number of pages UE per second or signal periodicity | System configuration, e.g., BW and etc. | the target channel | LP-SS MIL | Notes | +|---------|--------|--------------|----------------------|-------------|-------|-----------------------------------------------------|-----------------------------------------|--------------------|-----------|----------------------------------------------------------------------------------------------------------------------| +| [8A-11] | LP-SS | 0.0630% | 14 symbols | 5.04MHz | 30kHz | 320ms | 100MHz, 8beam | > Msg.3 | 150.78 | The LP-SS coverage is better than msg.3 coverage; The derivation of LP-SS frequency: 4.32MHz + 2RB (30kHz) = 5.04MHz | +| [8A-11] | LP-SS | 0.0158% | 14 symbols | 5.04MHz | 30kHz | 1280ms | 100MHz, 8beam | > Msg.3 | 150.78 | | +| [8A-11] | LP-SS | 0.0020% | 14 symbols | 5.04MHz | 30kHz | 10240ms | 100MHz, 8beam | > Msg.3 | 150.78 | | +| [8A-11] | LP-SS | 0.3150% | 14 symbols | 5.04MHz | 30kHz | 320ms | 20MHz, 8beam | > Msg.3 | 150.78 | | +| [8A-11] | LP-SS | 0.0790% | 14 symbols | 5.04MHz | 30kHz | 1280ms | 20MHz, 8beam | > Msg.3 | 150.78 | | +| [8A-11] | LP-SS | 0.0100% | 14 symbols | 5.04MHz | 30kHz | 10240ms | 20MHz, 8beam | > Msg.3 | 150.78 | | +| [8A-13] | LP-SS | 0.125%, | 14 symbols | 5MHz | 15kHz | 160ms | 100M, 4beam | Msg.3 | 158.44 | 2.6GHz for LP-SS MIL | +| [8A-13] | LP-SS | 0.625%, | 14 symbols | 5MHz | 15kHz | 160ms | 20M, 4beam | Msg.3 | 158.44 | | +| [8A-13] | LP-SS | 0.0625%, | 14 symbols | 5MHz | 15kHz | 320ms | 100M, 4beam | Msg.3 | 158.44 | | +| [8A-13] | LP-SS | 0.3125% | 14 symbols | 5MHz | 15kHz | 320ms | 20M, 4beam | Msg.3 | 158.44 | | + +| | | | | | | | | | | | +|---------|-------|-----------|----------------------|------|-------|----------|----------------|-------|--------|--| +| [8A-13] | LP-SS | 0.0625%, | 14 symbols | 5MHz | 30KHz | 160ms | 100M, 4beam | Msg.3 | 158.44 | | +| [8A-13] | LP-SS | 0.3125% | 14 symbols | 5MHz | 30KHz | 160ms | 20M, 4beam | Msg.3 | 158.44 | | +| [8A-13] | LP-SS | 0.125%, | 14 symbols | 5MHz | 30KHz | 160ms | 100M, 8beam | Msg.3 | 158.44 | | +| [8A-13] | LP-SS | 0.6250% | 14 symbols | 5MHz | 30KHz | 160ms | 20M, 8beam | Msg.3 | 158.44 | | +| [8A-13] | LP-SS | 0.03125%, | 14 symbols | 5MHz | 30KHz | 320ms | 100M, 4beam | Msg.3 | 158.44 | | +| [8A-13] | LP-SS | 0.1563% | 14 symbols | 5MHz | 30KHz | 320ms | 20M, 4beam | Msg.3 | 158.44 | | +| [8A-13] | LP-SS | 0.0625%, | 14 symbols | 5MHz | 30KHz | 320ms | 100M, 8beam | Msg.3 | 158.44 | | +| [8A-13] | LP-SS | 0.3125% | 14 symbols | 5MHz | 30KHz | 320ms | 20M, 8beam | Msg.3 | 158.44 | | +| [8A-5] | LP-SS | 0.0160% | 28symbols | 5MHz | 30KHz | 320ms | 100M, 1beam | | | | +| [8A-5] | LP-SS | 0.0630% | 28symbols | 5MHz | 30KHz | 320ms | 100M, 4beam | | | | +| [8A-16] | LP-SS | 0.1000% | 1ms, 4 repetitions | 5MHz | 30KHz | 1000ms | 20MHz | Msg.3 | 147.44 | | +| [8A-16] | LP-SS | 0.2000% | 1ms, 4 repetitions | 5MHz | 30KHz | 500ms | 20MHz | Msg.3 | 147.44 | | +| [8A-16] | LP-SS | 0.5000% | 1ms, 4 repetitions | 5MHz | 30KHz | 200ms | 20MHz | Msg.3 | 147.44 | | +| [8A-16] | LP-SS | 0.1500% | 1.5ms, 4 repetitions | 5MHz | 30KHz | 1000ms | 20MHz | Msg.3 | 147.44 | | +| [8A-16] | LP-SS | 0.3000% | 1.5ms, 4 repetitions | 5MHz | 30KHz | 500ms | 20MHz | Msg.3 | 147.44 | | +| [8A-16] | LP-SS | 0.7500% | 1.5ms, 4 repetitions | 5MHz | 30KHz | 200ms | 20MHz | Msg.3 | 147.44 | | +| [8A-4] | LP-SS | 0.0113% | 4 OFDM symbols | 5MHz | 30KHz | 320 ms | 20MHz, 1beams | Msg.3 | 155.18 | | +| [8A-4] | LP-SS | 0.0056% | 4 OFDM symbols | 5MHz | 30KHz | 640 ms | 20MHz, 1beams | Msg.3 | 155.18 | | +| [8A-4] | LP-SS | 0.0028% | 4 OFDM symbols | 5MHz | 30KHz | 1280 ms | 20MHz, 1beams | Msg.3 | 155.18 | | +| [8A-4] | LP-SS | 0.0014% | 4 OFDM symbols | 5MHz | 30KHz | 2560 ms | 20MHz, 1beams | Msg.3 | 155.18 | | +| [8A-4] | LP-SS | 0.0007% | 4 OFDM symbols | 5MHz | 30KHz | 5120 ms | 20MHz, 1beams | Msg.3 | 155.18 | | +| [8A-4] | LP-SS | 0.0004% | 4 OFDM symbols | 5MHz | 30KHz | 10240 ms | 20MHz, 1beams | Msg.3 | 155.18 | | +| [8A-4] | LP-SS | 0.0450% | 4 OFDM symbols | 5MHz | 30KHz | 320 ms | 20MHz, 4beams | Msg.3 | 155.18 | | +| [8A-4] | LP-SS | 0.0225% | 4 OFDM symbols | 5MHz | 30KHz | 640 ms | 20MHz, 4beams | Msg.3 | 155.18 | | +| [8A-4] | LP-SS | 0.0113% | 4 OFDM symbols | 5MHz | 30KHz | 1280 ms | 20MHz, 4beams | Msg.3 | 155.18 | | +| [8A-4] | LP-SS | 0.0056% | 4 OFDM symbols | 5MHz | 30KHz | 2560 ms | 20MHz, 4beams | Msg.3 | 155.18 | | +| [8A-4] | LP-SS | 0.0028% | 4 OFDM symbols | 5MHz | 30KHz | 5120 ms | 20MHz, 4beams | Msg.3 | 155.18 | | +| [8A-4] | LP-SS | 0.0014% | 4 OFDM symbols | 5MHz | 30KHz | 10240 ms | 20MHz, 4beams | Msg.3 | 155.18 | | +| [8A-4] | LP-SS | 0.0900% | 4 OFDM symbols | 5MHz | 30KHz | 320 ms | 20MHz, 8beams | Msg.3 | 155.18 | | +| [8A-4] | LP-SS | 0.0450% | 4 OFDM symbols | 5MHz | 30KHz | 640 ms | 20MHz, 8beams | Msg.3 | 155.18 | | +| [8A-4] | LP-SS | 0.0225% | 4 OFDM symbols | 5MHz | 30KHz | 1280 ms | 20MHz, 8beams | Msg.3 | 155.18 | | +| [8A-4] | LP-SS | 0.0113% | 4 OFDM symbols | 5MHz | 30KHz | 2560 ms | 20MHz, 8beams | Msg.3 | 155.18 | | +| [8A-4] | LP-SS | 0.0056% | 4 OFDM symbols | 5MHz | 30KHz | 5120 ms | 20MHz, 8beams | Msg.3 | 155.18 | | +| [8A-4] | LP-SS | 0.0028% | 4 OFDM symbols | 5MHz | 30KHz | 10240 ms | 20MHz, 8beams | Msg.3 | 155.18 | | +| [8A-4] | LP-SS | 0.0023% | 4 OFDM symbols | 5MHz | 30KHz | 320 ms | 100MHz, 1beams | Msg.3 | 155.18 | | +| [8A-4] | LP-SS | 0.0011% | 4 OFDM symbols | 5MHz | 30KHz | 640 ms | 100MHz, 1beams | Msg.3 | 155.18 | | +| [8A-4] | LP-SS | 0.0006% | 4 OFDM symbols | 5MHz | 30KHz | 1280 ms | 100MHz, 1beams | Msg.3 | 155.18 | | + +| | | | | | | | | | | | +|--------|-------|---------|----------------|------|-------|----------|----------------|-------|--------|--| +| [8A-4] | LP-SS | 0.0003% | 4 OFDM symbols | 5MHz | 30KHz | 2560 ms | 100MHz, 1beams | Msg.3 | 155.18 | | +| [8A-4] | LP-SS | 0.0001% | 4 OFDM symbols | 5MHz | 30KHz | 5120 ms | 100MHz, 1beams | Msg.3 | 155.18 | | +| [8A-4] | LP-SS | 0.0001% | 4 OFDM symbols | 5MHz | 30KHz | 10240 ms | 100MHz, 1beams | Msg.3 | 155.18 | | +| [8A-4] | LP-SS | 0.0090% | 4 OFDM symbols | 5MHz | 30KHz | 320 ms | 100MHz, 4beams | Msg.3 | 155.18 | | +| [8A-4] | LP-SS | 0.0045% | 4 OFDM symbols | 5MHz | 30KHz | 640 ms | 100MHz, 4beams | Msg.3 | 155.18 | | +| [8A-4] | LP-SS | 0.0023% | 4 OFDM symbols | 5MHz | 30KHz | 1280 ms | 100MHz, 4beams | Msg.3 | 155.18 | | +| [8A-4] | LP-SS | 0.0011% | 4 OFDM symbols | 5MHz | 30KHz | 2560 ms | 100MHz, 4beams | Msg.3 | 155.18 | | +| [8A-4] | LP-SS | 0.0006% | 4 OFDM symbols | 5MHz | 30KHz | 5120 ms | 100MHz, 4beams | Msg.3 | 155.18 | | +| [8A-4] | LP-SS | 0.0003% | 4 OFDM symbols | 5MHz | 30KHz | 10240 ms | 100MHz, 4beams | Msg.3 | 155.18 | | +| [8A-4] | LP-SS | 0.0180% | 4 OFDM symbols | 5MHz | 30KHz | 320 ms | 100MHz, 8beams | Msg.3 | 155.18 | | +| [8A-4] | LP-SS | 0.0090% | 4 OFDM symbols | 5MHz | 30KHz | 640 ms | 100MHz, 8beams | Msg.3 | 155.18 | | +| [8A-4] | LP-SS | 0.0045% | 4 OFDM symbols | 5MHz | 30KHz | 1280 ms | 100MHz, 8beams | Msg.3 | 155.18 | | +| [8A-4] | LP-SS | 0.0023% | 4 OFDM symbols | 5MHz | 30KHz | 2560 ms | 100MHz, 8beams | Msg.3 | 155.18 | | +| [8A-4] | LP-SS | 0.0011% | 4 OFDM symbols | 5MHz | 30KHz | 5120 ms | 100MHz, 8beams | Msg.3 | 155.18 | | +| [8A-4] | LP-SS | 0.0006% | 4 OFDM symbols | 5MHz | 30KHz | 10240 ms | 100MHz, 8beams | Msg.3 | 155.18 | | + +### 8.5.1.2 RRC CONNECTED + +The System overhead of LP-WUS for RRC CONNECTED is summarized in Table 8.5.1 - 3 + +**Table 8.5.1-3: Summary of System overhead for LP-WUS for RRC CONNECTED** + +| Source | Signal | # of info bits carried by signal | Overhead (%) | T resources per beam | F resources | SCS | traffic types | Number of UEs per cell | System configuration, e.g., BW and etc. | the target channel | LP-WUS MIL | Notes | +|---------|--------|----------------------------------|--------------|----------------------|-------------|--------|---------------|------------------------|-----------------------------------------|------------------------|------------|----------------------------------------------------------------------------------------------| +| [8A-11] | LP-WUS | 1 | 0.8600 % | 8 symbols | 5.04MHz | 30k Hz | XR (16.67 ms) | 10 | 100MHz | unicast PDCC H AL2-4Rx | 157.99 | The coverage of LP-WUS with 8/32/40 symbols is comparable to unicast PDCCH AL2-4Rx coverage. | +| [8A-11] | LP-WUS | 8 | 3.4300 % | 32 symbols | 5.04MHz | 30k Hz | XR (16.67 ms) | 10 | 100MHz | unicast PDCC H AL2-4Rx | 158.23 | | +| [8A-11] | LP-WUS | 12 | 4.2900 % | 40 symbols | 5.04MHz | 30k Hz | XR (16.67 ms) | 10 | | unicast PDCC H AL2-4Rx | 158.07 | | +| [8A-11] | LP-WUS | 1 | 0.0700 % | 8 symbols | 5.04MHz | 30k Hz | FTP3 (200ms) | 10 | 100MHz | unicast PDCC H AL2-4Rx | 157.99 | | +| [8A-11] | LP-WUS | 8 | 0.2900 % | 32 symbols | 5.04MHz | 30k Hz | FTP3 (200ms) | 10 | 100MHz | unicast PDCC H AL2-4Rx | 158.23 | | +| [8A-11] | LP-WUS | 12 | 0.3600 % | 40 symbols | 5.04MHz | 30k Hz | FTP3 (200ms) | 10 | 100MHz | unicast PDCC H AL2-4Rx | 158.07 | | + +## 8.5.2 Observations + +### For RRC IDLE/INACTIVE, + +- For LP-WUS carrying 1-bit information, depending on the time-frequency occupation, traffic inter-arrival time, number of beams, system BW, the system overhead varies, +- Results in [8A-11] shows that for OOK based LP-WUS system overhead is [0.003%~0.055%] for LP-WUS with 8 beams, 100MHz system BW based on varies configurations as described in the Table 8.5.1 - 1 (per beam LP-WUS duration is 1 symbol, coverage target is PUSCH Msg.3) +- Results in [8A-11] shows that for OOK based LP-WUS, system overhead is [0.018%~0.28%] for LP-WUS with 8 beams, 20MHz system BW based on varies configurations as described in the Table 8.5.1 – 1 (LP-WUS duration is 1symbol coverage target is PUSCH Msg.3) + +- Results in [8A-3] shows that for LP-WUS with 1 or 8 beams, 20MHz system BW based on varies configurations as described in the Table 8.5.1 – 1, and coverage target is PUSCH Msg.3 with and without retransmissions (2 retransmissions) + - For OOK based LP-WUS+LPSS with duration 5 or 8 slots, the system overhead is [0.0427%~1.5137%] + - For OFDM based LP-WUS with duration 4 or 5 symbols, the system overhead is [0.00066%~0.0664%] +- Results in [8A-3] shows that for LP-WUS with 8 beams, 20MHz system BW based on varies configurations as described in the Table 8.5.1 – 1, and coverage target is PDCCH AL[16] with 1Rx or 2Rx + - For OOK based LP-WUS+LPSS with duration 9~20 slots, the system overhead is [0.0549%~4.4434%] + - For OFDM based LP-WUS with duration 6~11 symbols, the system overhead is [0.001%~0.1462%] +- For LP-WUS carrying multiple bits information, depending on the time-frequency occupation, traffic inter-arrival time, number of beams, system BW, the system overhead varies, + - For LP-WUS carrying 48 bit information, + - Results in [8A-3] shows that for LP-WUS with 1 or 8 beams, 20MHz system BW based on varies configurations as described in the Table 8.5.1 – 1 + - For OOK based LP-WUS+LPSS with duration 32 or 117 slots, the system overhead is [0.1251%~3.5156%], assuming coverage target is PUSCH Msg.3 with and without retransmissions (2 retransmissions), + - For OOK based LP-WUS+LPSS with duration 140 or 390 slots, the system overhead is [0.4547%~11.8469%], assuming coverage target is PDCCH AL[16] with 1Rx or 2Rx + - Results in [8A-9] shows that system overhead is [0.0014%~0.5760%] for OOK based LP-WUS with 1 beam, 100MHz system BW. (per beam LP-WUS duration is 8/64 symbols, coverage target is PUSCH Msg.3) + - Results in [8A-9] shows that system overhead is [0.0072%~2.8800%] for OOK based LP-WUS with 1 beam, 20MHz system BW. (per beam LP-WUS duration is 8/64 symbols, coverage target is PUSCH Msg.3) + - For LP-WUS carrying 6~24 bits information, + - Results in [8A-3] [8A-4] [8A-11][8A-13][8A-16] show that system overhead is [0.0023%~1.9814%], for 6~24bits LP-WUS with 1~8 beams, 20MHz system BW;(per beam LP-WUS duration is 4/5/7/12/14/16.8/24 symbols or 10 slots, coverage target is PUSCH Msg.3 without retransmission) + - The evaluated waveform for LP-WUS includes OOK, FSK-2 + - Results in [8A-3] shows that system overhead is [0.0580%~1.9814 %], for 8bits OOK based LP-WUS+LP-SS with 1 or 8 beams, 20MHz system BW;(per beam LP-WUS duration is 10 slots, coverage target is PUSCH Msg.3 without retransmission) + - Results in [8A-3] shows that system overhead is [0.1129%~6.3232%], for 8bits OOK based LP-WUS+LP-SS with 1 or 8 beams, 20MHz system BW;(per beam LP-WUS duration is 28 slots, coverage target is PUSCH Msg.3 two retransmission) + - Results in [8A-3] shows that system overhead is [0.1434%~20.7959%], for 8bits OOK based LP-WUS+LP-SS with 1 or 8 beams, 20MHz system BW;(per beam LP-WUS duration is 38 or 88 slots, coverage target is PDCCH [AL16] with 1Rx or 2Rx) + - Results in [8A-3] shows that system overhead is [0.00199%~0.1575%], for 8bits OFDM based LP-WUS with 1 or 8 beams, 20MHz system BW;(per beam LP-WUS duration is 12symbols coverage target is PUSCH Msg.3 without retransmission or with two transmissions) + - Results in [8A-3] shows that system overhead is [0.00199%~0.1969%], for 8bits OFDM based LP-WUS with 1 or 8 beams, 20MHz system BW;(per beam LP-WUS duration is 12 or 15 symbols, coverage target is PDCCH [AL16] with 1Rx or 2Rx) + +- Results in [8A-4] [8A-5] [8A-11] shows that system overhead is [0.0005%~1.777%] for 7~24bits LP-WUS with 1~8 beams, 100MHz system BW. (per beam LP-WUS duration is 4/5/12/24 symbols or 12symbols with 1/2/4 repetitions, coverage target is PUSCH Msg.3) + - The evaluated waveform for LP-WUS includes OOK, FSK-2, sequence on top of OOK/FSK and OFDM sequence +- For LP-SS based on OOK with 320ms \* X periodicity, 1 slot (30kHz) \* Y and 5MHz \* Z time-frequency occupation, with 8 beams\*W and 20MHz\*T system bandwidth, the system overhead is no more than $0.4\% * Y * Z * W / X / T$ . +- Example setting for LP-SS, + - Set 1: approximately 5MHz LP-SS BW, 1 slot (30KHz) duration, 320ms periodicity, 8 beams, 20MHz system bandwidth (overhead no more than 0.4%). + - Set 2: approximately 5MHz LP-SS BW, 1 slot (30KHz) duration, 160ms periodicity, 8 beams, 20MHz system bandwidth (overhead no more than 0.8%). + - Set 3: approximately 5MHz LP-SS BW, 2 slot (30KHz) duration, 320ms periodicity, 8 beams, 20MHz system bandwidth (overhead no more than 0.8%). + - Set 4: approximately 5MHz LP-SS BW, 1 slot (30KHz) duration, 1000ms periodicity, 8 beams, 20MHz system bandwidth (overhead no more than 0.1%). + - Note: the overhead for the above reference sets are derived based on the above formula. + +#### For RRC CONNECTED + +- Results in [8A-11] shows that + - For XR (16.67ms, 60FPS) and 10 UEs per cell (maximum system capacity), 100MHz system BW, + - The overhead of LP-WUS based on OOK with 8 symbol duration and 1-bit information is 0.86%; + - The overhead of LP-WUS based on OOK with 32/40 symbol duration and 8 or 12-bits information is 3.43%~4.29%; + - For FTP3 (200ms mean arrival time) and 10 UEs per cell (RU is 40%), 100MHz system BW, + - The overhead of LP-WUS based on OOK with 8 symbol duration and 1-bit information is 0.07%; + +The overhead of LP-WUS based on OOK with 32/40 symbol duration and 8 or 12-bits information is 0.29%~0.36%. + +## 9 Conclusions + +### 9.1 Power/latency/coverage/overhead/network energy + +RAN1 has identified use cases of LP-WUS/WUR for power sensitive devices including IoT, wearable and eMBB, and for both IDLE/INACTIVE and CONNECTED mode usage. RAN1 has identified the performance metrics and KPIs for the studies of LP-WUS/WUR including UE power consumption, coverage, latency and UPT as well as metrics and KPIs for network impact including the impact to system overhead, system capacity (XR traffic), and network energy consumption. + +RAN1 has developed evaluation methodologies for the study of LP-WUS/WUR including power models for LR and MR, traffic characteristics, coverage targets, LR clocks and oscillator assumptions, etc. + +RAN1 has carried out system level evaluations for the UE power saving and latency benefit of using LP-WUS/WUR for IDLE/INACTIVE UEs. + +- UE power saving gain cannot be observed if the existing Rel-18 MR RRM measurement periodicity for serving and neighbour cells are applied and UE MR enters in ultra-deep sleep during LP LP-WUS monitoring, therefore MR serving and neighbour cell measurement with further time domain relaxation than that is allowed in Rel-18 specification for IDLE/INACTIVE and/or at least serving cell RRM offloaded from MR to LR are beneficial. +- Compared with existing I-DRX operation, + - Significant UE power saving gain (up to more than 90%) is observed by using LP-WUS/WUR to trigger UE MR paging monitoring compared with existing I-DRX operation (with and without PEI), if sufficient relaxation to MR RRM measurement is applied. + - For duty-cycled LP-WUS monitoring and same duty ratio, higher power saving gain is observed if the relative power consumption of LP-WUR ON for LP-WUS monitoring is lower. + - For continuous LP-WUS monitoring, UE power saving gain is only observed if the relative power consumption of LP-WUR ON for LP-WUS monitoring is lower, e.g. no larger than 1 unit. + - If the MR enters ultra deep sleep while monitoring LP-WUS, compared with legacy I-DRX operation with same I-DRX cycle, moderate paging latency increase (e.g. ~400ms) is observed by using LP-WUS/WUR, due to the ramp up and re-sync procedure of MR from ultra-deep sleep state and if legacy paging occasion is reused. From RAN1 perspective, potential techniques to decrease the latency e.g. using shorter I-DRX cycles, dynamic paging occasion determination, UE MR transmit PRACH directly after wake-up by LP-WUS, UE MR entering deep sleep during LP LP-WUS monitoring, were proposed and evaluated. +- Compared with existing eDRX operation, significant paging latency reduction and moderate UE power saving gain is observed, if LP-WUS monitoring and the corresponding paging monitoring after MR wake-up is performed not restricted within existing PTW of eDRX. Significant UE power gain and moderate paging latency increase is observed if LP-WUS monitoring is restricted within existing PTW of eDRX and existing paging occasion determination is reused. + +RAN1 has carried out system level evaluations for the UE power saving and UPT benefit of using LP-WUS/WUR for CONNECTED mode UEs with different traffic types including XR, FTP and IM. Existing power saving techniques, including Rel-15 long/short C-DRX cycle, Rel-16 DCP, Rel-17 PDCCH skipping/SSSG switching and Rel-18 enhanced C-DRX for non-integer periodicities are used for in the evaluation comparison. + +- For XR traffic and LP-WUS to trigger the UE MR PDCCH monitoring, + - Moderate UE power saving gain (up to more than 10%) across different types of XR traffic and system load scenarios can be observed, larger UE power saving gain can be observed if the UE MR can enter light sleep instead of micro sleep during LP-WUS monitoring by LR. + - The impact to the XR capacity is marginal for low load scenarios. For high load scenarios, the impact to the XR capacity is also marginal when the UE MR enters the micro sleep state and relatively larger when MR enters the light sleep state during LR LP-WUS monitoring. +- For FTP and IM traffic, + - For the usage of LP-WUS to trigger the UE MR PDCCH monitoring, + - Compared with existing UE power saving techniques, significant UE power saving gain (up to more than 60%) and moderate UPT improvement (up to more than 10%) when the UE MR enters deep sleep state during LR LP-WUS monitoring, larger UPT improvement (up to more than 180%) is observed for traffic with small packets, e.g. IM. Relatively lower or no UE power saving gain can be observed when the UE MR enters light sleep during LR LP-WUS monitoring, but the UPT improvement is higher (up to more than 50%). + - Compared with UE MR always-on PDCCH monitoring, significant UE power saving gain (up to more than 40%) and similar UPT performance can be observed, when UE MR enters micro sleep during LR LP-WUS monitoring. + - For the usage of LP-WUS as the wake-up mechanism of C-DRX similar to DCP + +- Significant UE power saving gain (up to more than 30%) and moderate degradation to the UPT (less than 10%) can be observed, especially when the C-DRX cycle is shorter (e.g. 40ms) . + +RAN1 has carried out coverage evaluation to compare the MIL performance of LP-WUS with that of legacy NR channels (e.g. PUSCH for MSG3, PDCCH for Paging). It is observed that for LP-WUS can achieve comparable MIL performance with that of NR PUSCH MSG3, with the assumed resource for each LP-WUS transmission is as the following, in which RedCap and non-RedCap UE cases are not further distinguished. + +- For Urban scenario and single PUSCH MSG3 transmission + - For OOK-based LP-WUS, the required resource reported is 0.9~17.28 MHz\*Symbol/bit + - For FSK-based LP-WUS, the required resource reported is 4.32~25.92 MHz\*Symbol/bit + - For OFDM-based LP-WUS, the required resource reported is 0.31~4.32 MHz\*Symbol/bit +- For Urban scenario and PUSCH MSG3 transmission with two retransmissions (one source) + - For OOK-based LP-WUS, the required resource reported is 241.92 MHz\*Symbol/bit + - For OFDM-based LP-WUS, the required resource reported is 2.16 MHz\*Symbol/bit +- For Rural scenarios and single PUSCH MSG3 transmission + - For OOK-based LP-WUS, the required resource reported is 0.18~8.64MHz\*Symbol/bit + - For FSK-based LP-WUS, the required resource reported is 4.32 MHz\*Symbol/bit (one source) + - For OFDM-based LP-WUS, the required resource reported is 1.8~3.6MHz\*Symbol/bit +- Note the above OFDM symbol assumes subcarrier spacing 30kHz +- In general, it is much more challenging for LP-WUS to reach comparable MIL as legacy PDCCH with AL16/AL8, more resources occupancy and/or coverage enhancement techniques for LP-WUS transmission would be required to reach such challenging MIL target. + +For the overhead of LP-WUS used for RRC IDLE/INACTIVE UEs, it depends on the number of information bits, time-frequency occupation, traffic inter-arrival time, number of beams, system BW. + +- For 5MHz LP-WUS with single PUSCH MSG 3 as MIL target + - For OFDM based LP-WUS carrying information of up to 24bits, the overhead is marginal (up to 0.16%) for 20MHz or 100MHz system BW + - For OOK/FSK-2 based LP-WUS carrying information up to 24bit, the overhead is marginal (up to 1.98%) for 20MHz. Note that in this case, the overhead evaluation in some sources includes LP-WUS and LP-SS. The reported maximum payload and maximum overhead are from different sources and are not corresponds to each other. +- For 5MHz LP-WUS with paging PDCCH (AL8/AL16) as the MIL target and 20MHz system BW, + - For OFDM based LP-WUS carrying information up to 8bits, the overhead is marginal (up to 0.19%) (one source) + - For OOK-based LP-WUS carrying information up to 48bits, the overhead can be significant (up to 21%). Note that in this case, the overhead evaluation in some sources includes LP-WUS and LP-SS + +For the overhead of LP-WUS used RRC CONNECTED mode (One source) + +- For XR and 10 UEs per cell (maximum system capacity) and 100MHz system BW, the overhead of OOK-based LP-WUS carrying up to 12bits information bits is small (up to 4.3%); +- For FTP3 traffic and 10 UEs per cell, RU 40%, 100MHz system BW, the overhead of OOK-based LP-WUS carrying up to 12 information bits is marginal (up to 0.36%); + +For OOK based LP-SS with 5MHz, 8 beams and 20MHz system bandwidth, the overhead is 0.4% for 320ms LP-SS periodicity and 1 slot (30kHz) duration per beam, and 0.3% for 1280ms LP-SS periodicity and 3 slots (30KHz) duration per beam. The overhead of other configurations can be derived by scaling accordingly. + +The additional increased network power consumption due to LP-SS is also studied assuming LP-SS is an additional signal transmission than the existing NR signal/channels. When 320ms LP-SS periodicity, 4 or 8 beams and no more than 14 symbols LP-SS duration is assumed, the additional increased network power consumption rate is marginal (0.06%~3.9%), (0.07%~2.716%), (0.388%~1.076%) for zero load, low load and medium load respectively. For 320ms LP-SS periodicity, 8 beams and 42 symbols LP-SS duration, one source shows the additional increase network power consumption rate is 11.4%. + +Lower impact to the network power consumption is expected when LP-SS is transmitted FDM with NR SSB/SIB-1. + +## 9.2 LP-WUR architecture + +For the LP-WUR architecture, + +- For OOK waveform, 3 types of receiver architectures have been considered: RF envelope detection, heterodyne architecture with IF envelope detection, and homodyne/zero-IF architecture with baseband envelope detection. + - For RF envelope detection, the reported relative power consumption for ON state is in the range of 0.01~0.2, and the reported noise figure is in the range of 12~22 dB. + - For heterodyne architecture, the reported relative power consumption for ON state is in the range of 0.1~4, and the reported noise figure is in the range of 9~15 dB. + - For homodyne/zero-IF architecture, the reported relative power consumption for ON state is in the range of 0.05~4, and the reported noise figure is in the range of 10~16 dB. +- For FSK waveform, the architectures with parallel OOK receivers and with frequency to amplitude conversion have been considered. Among the architectures that have more than 2 sources providing the analysis, + - For parallel heterodyne architecture, the reported relative power consumption for ON state is in the range of 0.1~1, and the reported noise figure is in the range of 9~15 dB. + - For parallel homodyne/zero-IF architecture, the reported relative power consumption for ON state is in the range of 0.1~1, and the reported noise figure is in the range of 10~16 dB. +- For OFDMA-based signals, sequence-based signals have been considered, where the LP WUR performs either time-domain correlation without FFT or frequency-domain correlation after FFT. + - For time-domain correlation, the reported relative power consumption for ON state is in the range of 0.15~10/30, and the reported noise figure is in the range of 7~25. + - For frequency-domain correlation, the reported relative power consumption for ON state is in the range of 1~30, and the reported noise figure is in the range of 7~12. +- Note that: + - Some of the inconsistent ranges for the architectures for OOK and FSK waveforms (e.g., power consumption for the homodyne/zero-IF architecture for OOK and the parallel homodyne/zero-IF architecture for FSK) is due to the fact that not all sources provided analysis for all the architectures. + - For each individual source, the power consumption for FSK is similar as or slightly higher than the power consumption for OOK with the same architecture type. + - Note that some of the wide ranges for the different architectures is due to the fact that different sources made different assumptions and there is a tradeoff between power consumption and noise figure. + +## 9.3 LLS performance and LP-WUS design/L1 procedure + +RAN1 studied robustness of OOK-1, OOK-2, OOK-3, OOK-4, FSK-1, FSK-2 and OFDMA waveform to time and frequency offset in Clauses 8.3.1, and 8.3.2 resp. and observed the following: + +- OOK/FSK waveform with longer time segment and with a single or multiple frequency segments is comparable (0 us) or more robust (by 4us) to timing error than waveform with shorter time segment. +- One source shows that without sliding window, OFDMA tolerates up to 4us timing error, when SCS $\leq 30\text{kHz}$ , and receiver did not perform FFT. +- For OFDMA, tolerance to timing error varies with sliding window size assumed by a receiver and was shown to tolerate timing error up to 4us if proper sliding window size is assumed by a receiver. +- Single frequency segment OOK (except OOK3) waveform is more robust to frequency error (of 390kHz) than OOK/FSK waveforms with multiple frequency segments (depending on guard-band size between segments) and both are more robust than OFDMA waveform assuming no frequency compensation/synchronization. +- One source showed that single frequency segment FSK-envelop-IF waveform is more robust to frequency error (of 260 kHz) than OOK/FSK waveforms with multiple frequency segments (depending on guard-band size between segments) and both are more robust than OFDMA waveform assuming no frequency compensation/synchronization. + +In RAN1 also the impact of sampling rate on performance has been studied. + +RAN1 studied spectral efficiency of OOK-1, OOK-2, OOK-3, OOK-4, FSK-1, FSK-2 and OFDMA waveform, where the best results (of spectral efficiency) from results reported by each company for each waveform are summarized in Clause 8.3.3. Results among companies were combined across different receiver types, different power pooling assumption, different sampling rates, different tx antenna configurations, FAR target for the same waveform. + +RAN1 studied RSRP and RSRQ measurement accuracy based on LP-SS (based on OOK which can be received by envelop detector) assuming TDL-C channel and observed that depending on SNR target $X = \{-3, -6, -9, -11\}$ dB as seen by LP-WUR, and depending on 90% accuracy of 3 or 5 dB, different number symbols (1 -70) spread over 1-5 periods is required. Timing and frequency impairments were also considered. RAN1 studied RSRP and RSRQ measurement accuracy based on LP-SS (based on OOK which can be received by envelop detector) assuming AWGN channel and observed that depending on SNR target $X = \{-9, -11\}$ dB as seen by LP-WUR, and depending on 90% accuracy of 3 or 5 dB, different number symbols (1 -20) spread over 1-3 periods is required. Timing and frequency impairments were also considered. Corresponding SNR observed by MR and LR is different due to NF difference between them. Accuracy of RSRP and RSRQ measurement depends on sampling rate. + +RAN1 studied RSRP measurement accuracy based on SSS (OFDMA received by I/Q detector) and observed that depending on SNR target $X = [-3, -6]$ dB as seen by LP-WUR, and depending on 90% accuracy of 3dB, 1 OFDMA symbol in 1 period is required, assuming TDL-C. Timing and frequency impairments were also considered. + +For waveform generation of OOK/FSK the following observations were made. Flat spectrum in frequency domain provides robustness against frequency selective fading compared to concentrated energy in frequency domain. For OOK-4, sequence before DFT/LS with variation in phase via such as ZC, M-sequence or QAM sequence can achieve more flattened spectrum. Sequence(s) used in LP-WUS symbol generation with different pulse shape or spectral shape may have different performances. Knowledge of sequence(s) used in LP-WUS waveform generation may improve performance for at least a receiver with I/Q branches. + +Pre-storing of the generated frequency domain samples to be mapped to LP-WUS sub-carrier segment of iFFT at gNB may reduce complexity of waveform generation at gNB with memory requirement depending on number of possible combinations. The number of combinations is function of number of supported LP-WUS bandwidth sizes, supported values of M for OOK-4, etc. Pre-storing of the generated frequency domain samples may be up to gNB implementation. For OOK4, Manchester coding will reduce the number of combinations for OOK-4 given the same time/frequency resource. + +RAN1 studied LP-WUS bandwidth, at least for IDLE/Inactive mode, at least one BW-size smaller or equal to 5MHz is recommended to be supported for FR1. Other BW sizes are not precluded, however if additional BW-size(s) are recommended to be supported, BW-size can be up to 20MHz. LP-WUS bandwidth size (including guard-bands) is assumed to be an integer number of PRBs. From RAN1 perspective, LP-WUS and signals/channels by MR can be at + +least on the same carrier in the same band. From RAN1 perspective, for multiplexing with other NR signals and channels, it is beneficial if LP-WUS can be flexibly configured within a carrier. + +RAN1 studied synchronization of LP-WUR. At least for LP-WUR that cannot receive existing PSS/SSS, periodic LP-SS signal is beneficial for the following functionalities: (a) RRM measurements by LP-WUR, if supported (b) At least coarse time synchronization of LP-WUR. (c) At least coarse frequency synchronization of LP-WUR. Additional periodic LP-SS system overhead depends on LP-SS periodicity, system BW, number of beams, and resource required to fulfil the target functionality, etc. Periodic signal if used for coarse synchronization may reduce the overhead of signal preceding LP-WUS, if any. LP-SS can be designed to be common among UE groups (cell-specific) and further reduce system overhead. For LP-WUR that can receive existing PSS/SSS potentially assisted by PBCH DMRS/TRS for synchronization, existing PSS/SSS potentially assisted by PBCH DMRS/TRS may be used for above functionality. Periodic LP-SS coverage should be equal or better than that of LP-WUS. For fine time and frequency synchronization, a signal (e.g., preamble) preceding or part of LP-WUS may be used. + +OFDMA waveform can provide coverage for LP-WUS with lower resource overhead. LP-WUR receiving OFDMA waveform can reuse PSS/SSS to perform RRM measurement and synchronization avoiding the introduction of periodic LP-SS within the carrier. Timing error robustness can be further improved using a sliding window at the receiver. + +Single frequency segment OOK-1/OOK-4 can provide a range of spectral efficiencies while being the most robust waveform to frequency error while robustness to timing error decreases with the increasing of M, but could be addressed by using a sliding window at the receiver or by pulse shaping in time domain. OOK-4 with variable M can provide a flexible range of spectral efficiencies for a fixed LP-WUS resource. Sequences to generate ON duration in OFDMA transmitter, if specified, can help receiver (with I/Q branches) performance. + +FSK-2 can provide a range of spectral efficiencies by varying M while having good robustness to frequency error and moderate robustness to timing error. Frequency error robustness can be further improved using frequency error correction (i.e., utilizing $2^M$ parallel receiver structure or frequency domain sliding window), larger guard band between segments at the expense of less frequency diversity, and/or single frequency segment FSK2-envelope IF. Timing error robustness can be further improved using a sliding window or by pulse shaping in the time domain. Uniform distribution of frequency spectrum density can be achieved using single frequency segment FSK2-envelope IF which can provide robustness against frequency fading. Sequences to generate ON duration in OFDMA transmitter, if specified, can help receiver (with I/Q branches) performance. + +## 9.4 RAN4 RF study + +During the SI study for LP-WUS/WUR, RAN4 had discussed and analysed the RF related issues, some of the key issues are listed as following: + +- LP-WUR UE architectures including the variant implementations +- Guard RBs for ACS and ASCS cases with RF impairments (e.g., CFO, phase noise, non-linearities) for RAN1 assumed LP-WUS waveforms +- Guard RB definition and placement for ACS and ASCS cases +- gNodeB RF impacts including BS in-band power boosting for LP-WUS +- Operating bands (same band or different bands) for LP-WUS +- LP-WUS channel bandwidth +- Link-level simulation and filter suppression level analysis regarding the guard RBs analysis +- Noise figure for LP-WUR +- REFSENS for the assumed coverage target +- Multi-band capability + +Based on the study, RAN4 reached the following conclusions: + +- RAN4 studied ACS and ASCS of LP-WUS, RAN4 concluded that the LP-WUS signal can coexist with existing NR signal/channels in the same channel, or in an adjacent channel(s) with proper number of guard RBs. + +- It is beneficial to enable power boosting for LP-WUS to improve the WUS signal coverage. The supporting of LP-WUS power boosting and boosting level can be declared by manufacturer. +- RAN4 discussed band operation for LP-WUS and concluded that the operating band for the low-power radio (LR) and main radio (MR) can be the same or different from RF perspective. + +Besides the above conclusions, RAN4 also identified some issues which could be further discussed in WI phase, e.g., + +- Specifying at least the REFSSENS, ACS and ASCS requirements with consideration of possible new methodology +- Impacts of different architecture on RF requirements, if any +- Specific guard RBs for ACS and ASCS cases +- Study and specify BS power boosting value/range for LP-WUS +- Specific IMT operating band(s) for LP-WUS if necessary +- Possible testability issues + +It is noted that all above issues to be considered in WI stage are all based on the final agreed waveforms decided by RAN1/RAN-P. + +## 9.5 RAN4 RRM aspects for serving cell RSRP/RSRQ measurement offloading to LP-WUR + +RAN4 confirms that the evaluation methodology as described in clause 8.3.4 and 8.3.5 for serving cell RSRP/RSRQ measurement offloading to LP-WUR for IDLE/INACTIVE mode is reasonable for the study item. + +## 9.6 Higher-layer aspects + +For RRC\_IDLE/INACTIVE mode: + +- RAN2 has studied the procedure where network configures LR for LP-WUS monitoring and concluded that LP-WUS to control paging/PEI monitoring with no UE reporting of WUS coverage status or change is feasible. Details are to be decided in WI phase. +- RAN2 has studied and concluded to support subgrouping for LP-WUS, detailed design depends on the payload of LP-WUS. +- RAN2 has studied the entry and exit condition of using LP-WUS, and concluded the condition(s) could be at least based on the serving cell measurement using LR and/or MR. +- RAN2 has studied LP-WUS configuration, at least via system information broadcast. +- RAN2 has studied and concluded the feasibility for RRM measurement relaxation (including no measurement) for serving cell by MR and neighboring cell by MR at least if RRM measurement on LR for serving cell is feasible/supported. + +For RRC\_CONNECTED mode + +- RAN2 has studied the procedure where network control/configure/activate LR for LP-WUS monitoring, and concluded the feasibility for LP-WUS to control PDCCH monitoring by MR with / without C-DRX. Detailed design is to be decided in WI. + +**Note:** Both duty-cycled and/or continuous monitoring for LP-WUS could be further discussed in WI phase for RRC\_IDLE/INACTIVE and RRC\_CONNECTED mode. + +# Annex + +## Annex 7.1.1a Analysis of LP-WUR architectures + +RAW data are attached as file in the TR. + +## Annex 8.1 Power evaluation + +RAW data are attached as file in the TR. + +## Annex 8.2 Coverage + +RAW data are attached as file in the TR. + +## Annex 8.3 LLS results + +RAW data can be found in 3GPP R1-2308647. + +## Annex 8.4 Network power consumption + +### Annex8.4.1[8A-11] + +**Table Annex8.4.1-1: Assumption on baseline and LP-SS configuration** + +| Parameter | Assumption | +|-------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Baseline:
SSB and SIB1 transmitted in FDM manner;
RACH monitoring | - Periodicity of SSB/SIB1 transmission, RACH monitoring: 20ms
- SSB: 4 slots with 2 SSBs in each slot, where 1 SSB occupies 4 OFDM symbols and 20 PRBs
- SIB 1: occupies 4 slots and 48 PRBs
- RACH: occupies 1 slot | +| System load | Zero, low, light, medium load, which follows the agreed definition in R18 NES SI. | +| LP-SS | - Periodicity of LP-SS: P=320, 640, 1280, 2560, 5120, 10240ms
- One LP-SS (per beam) T-F duration is one slot and 11PRBs
- 4 or 8 beams assumed for LP-SS | +| FDM pattern | LP-SS fully FDM with SSB/SIB1; No time gap between them | +| TDM pattern | LP-SS is right after SSB/SIB1 | +| Note: | The NW power consumption of LP-WUS transmission is not accounted in the simulation due to sparse traffic arrival rate. | + +**Table Annex8.4.1-2: Network power consumption caused by LP-SS with 8 beams for RRC idle/inactive mode** + +| Load | Scheme | Case | Cat 1 | | Cat 2 | | +|-----------|--------------|----------|---------------------------|--------------------------|---------------------------|--------------------------| +| | | | Mean BS Power consumption | Gain/loss (vs. Baseline) | Mean BS Power consumption | Gain/loss (vs. Baseline) | +| Zero load | FDM with SSB | Baseline | 23.287 | | 3.466 | | +| | | P=320ms | 23.706 | 1.799% | 3.504 | 1.097% | +| | | P=640ms | 23.497 | 0.900% | 3.485 | 0.549% | +| | | P=1280ms | 23.392 | 0.450% | 3.476 | 0.274% | +| | | P=2560ms | 23.340 | 0.225% | 3.471 | 0.137% | + +| | | | | | | | +|-------------|--------------|-----------|--------|--------|-------|--------| +| Low load | | P=5120ms | 23.314 | 0.113% | 3.468 | 0.065% | +| | | P=10240ms | 23.302 | 0.061% | 3.467 | 0.031% | +| | TDM with SSB | Baseline | 23.287 | | 3.466 | | +| | | P=320ms | 24.114 | 3.551% | 3.538 | 2.076% | +| | | P=640ms | 23.701 | 1.776% | 3.502 | 1.038% | +| | | P=1280ms | 23.494 | 0.888% | 3.484 | 0.519% | +| | | P=2560ms | 23.391 | 0.444% | 3.475 | 0.259% | +| | | P=5120ms | 23.332 | 0.192% | 3.470 | 0.124% | +| | | P=10240ms | 23.309 | 0.093% | 3.468 | 0.055% | +| | FDM with SSB | Baseline | 27.992 | | 3.948 | | +| | | P=320ms | 28.364 | 1.328% | 3.984 | 0.912% | +| | | P=640ms | 28.168 | 0.627% | 3.966 | 0.459% | +| | | P=1280ms | 28.087 | 0.340% | 3.957 | 0.233% | +| | | P=2560ms | 28.040 | 0.170% | 3.952 | 0.118% | +| | | P=5120ms | 28.017 | 0.087% | 3.950 | 0.057% | +| | | P=10240ms | 28.004 | 0.043% | 3.949 | 0.029% | +| | | Baseline | 27.992 | | 3.948 | | +| | TDM with SSB | P=320ms | 28.753 | 2.716% | 4.016 | 1.725% | +| | | P=640ms | 28.368 | 1.343% | 3.982 | 0.865% | +| | | P=1280ms | 28.183 | 0.681% | 3.965 | 0.435% | +| | | P=2560ms | 28.090 | 0.350% | 3.956 | 0.222% | +| | | P=5120ms | 28.041 | 0.173% | 3.952 | 0.113% | +| | | P=10240ms | 28.016 | 0.084% | 3.950 | 0.050% | +| Medium load | FDM with SSB | Baseline | 53.788 | | 6.649 | | +| | | P=320ms | 54.141 | 0.657% | 6.675 | 0.388% | +| | | P=640ms | 53.952 | 0.305% | 6.662 | 0.198% | +| | | P=1280ms | 53.875 | 0.162% | 6.656 | 0.105% | +| | | P=2560ms | 53.822 | 0.064% | 6.653 | 0.059% | +| | | P=5120ms | 53.805 | 0.031% | 6.651 | 0.030% | +| | | P=10240ms | 53.796 | 0.015% | 6.650 | 0.015% | +| | | Baseline | 53.788 | | 6.649 | | +| | TDM with SSB | P=320ms | 54.367 | 1.076% | 6.698 | 0.742% | +| | | P=640ms | 54.137 | 0.648% | 6.674 | 0.375% | +| | | P=1280ms | 53.967 | 0.333% | 6.662 | 0.200% | +| | | P=2560ms | 53.880 | 0.172% | 6.656 | 0.109% | +| | | P=5120ms | 53.831 | 0.080% | 6.653 | 0.053% | +| | | P=10240ms | 53.809 | 0.039% | 6.651 | 0.029% | + +**Table Annex 8.4.1-3: Network power consumption caused by LP-SS with 4 beams for RRC idle/inactive mode** + +| Load | Scheme | Case | Cat 1 | | Cat 2 | | +|-----------|--------------|-----------|---------------------------|--------------------------|---------------------------|--------------------------| +| | | | Mean BS Power consumption | Gain/loss (vs. Baseline) | Mean BS Power consumption | Gain/loss (vs. Baseline) | +| Zero load | FDM with SSB | Baseline | 23.2873 | | 3.4662 | | +| | | P=320ms | 23.3048 | 0.075% | 3.46826 | 0.059% | +| | | P=640ms | 23.296 | 0.037% | 3.46723 | 0.030% | +| | | P=1280ms | 23.2917 | 0.019% | 3.46671 | 0.015% | +| | | P=2560ms | 23.2895 | 0.009% | 3.46645 | 0.007% | +| | | P=5120ms | 23.2884 | 0.005% | 3.46633 | 0.004% | +| | | P=10240ms | 23.2884 | 0.005% | 3.46633 | 0.004% | +| | TDM with SSB | Baseline | 23.2873 | | 3.4662 | | +| | | P=320ms | 23.6888 | 1.724% | 3.50218 | 1.038% | +| | | P=640ms | 23.488 | 0.862% | 3.48419 | 0.519% | +| | | P=1280ms | 23.3877 | 0.431% | 3.47519 | 0.259% | +| | | P=2560ms | 23.3375 | 0.216% | 3.47069 | 0.130% | + +| | | | | | | | +|-------------|--------------|-----------|-------------|--------|-------------|--------| +| | | P=5120ms | 23.3124 | 0.108% | 3.46845 | 0.065% | +| | | P=10240ms | 23.3124 | 0.108% | 3.46845 | 0.065% | +| Low load | FDM with SSB | Baseline | 27.99219 | | 3.947543 | | +| | | P=320ms | 28.00813 | 0.057% | 3.949475 | 0.049% | +| | | P=640ms | 28.00016 | 0.028% | 3.948511 | 0.025% | +| | | P=1280ms | 27.9962 | 0.014% | 3.948034 | 0.012% | +| | | P=2560ms | 27.99417 | 0.007% | 3.947789 | 0.006% | +| | | P=5120ms | 27.99328 | 0.004% | 3.947671 | 0.003% | +| | | P=10240ms | 27.99328 | 0.004% | 3.947671 | 0.003% | +| | | Baseline | 27.99219 | | 3.947543 | | +| | TDM with SSB | Baseline | 27.99219 | | 3.947543 | | +| | | P=320ms | 28.34794 | 1.271% | 3.981592 | 0.863% | +| | | P=640ms | 28.15971 | 0.598% | 3.964701 | 0.435% | +| | | P=1280ms | 28.08326 | 0.325% | 3.956271 | 0.221% | +| | | P=2560ms | 28.03778 | 0.163% | 3.95196 | 0.112% | +| | | P=5120ms | 28.01555 | 0.083% | 3.949791 | 0.057% | +| | | P=10240ms | 28.01555 | 0.083% | 3.949791 | 0.057% | +| | | Baseline | 27.99219 | | 3.947543 | | +| Medium load | FDM with SSB | Baseline | 53.7879 | | 6.649008095 | | +| | | P=320ms | 53.79838571 | 0.019% | 6.65037619 | 0.021% | +| | | P=640ms | 53.79342857 | 0.010% | 6.649718571 | 0.011% | +| | | P=1280ms | 53.79104286 | 0.006% | 6.649399524 | 0.006% | +| | | P=2560ms | 53.78975238 | 0.003% | 6.649232381 | 0.003% | +| | | P=5120ms | 53.78898095 | 0.002% | 6.649135238 | 0.002% | +| | | P=10240ms | 53.78898095 | 0.002% | 6.649135238 | 0.002% | +| | | Baseline | 53.7879 | | 6.649008095 | | +| | TDM with SSB | Baseline | 53.7879 | | 6.649008095 | | +| | | P=320ms | 54.14139048 | 0.657% | 6.67342 | 0.367% | +| | | P=640ms | 53.95587143 | 0.312% | 6.661481905 | 0.188% | +| | | P=1280ms | 53.87204286 | 0.156% | 6.655593333 | 0.099% | +| | | P=2560ms | 53.83029524 | 0.079% | 6.652702857 | 0.056% | +| | | P=5120ms | 53.80868571 | 0.039% | 6.651096667 | 0.031% | +| | | P=10240ms | 53.80868571 | 0.039% | 6.651096667 | 0.031% | + +## Annex 8.4.2[8A-13] + +Assumptions on baseline scheme, LP-SS and LP-WUS configuration are shown in **Table Annex 8.4.2-1**. + +**Table Annex 8.4.2-1: Assumption on baseline and LP-SS configuration** + +| | Scheme | Assumption | +|--------------------------------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Baseline: SSB and SIB1 transmitted in FDM manner | |
  • - Periodicity of SSB transmission: 20ms
  • - Periodicity of SIB1 transmission: 40ms
  • - SSB: 4 slots with 2 SSBs in each slot, where 1 SSB occupies 4 OFDM symbols and 20 PRBs
  • - SIB1: occupies 8 slots and 12 PRBs
| +| LP-SS and LP-WUS | |
  • - Periodicity of LP-SS: 320ms; Offset with SSB: 0 and 10ms; Beams: 4
  • - Periodicity of LP-WUS: 1280ms; Offset with SSB: 0 and 5ms; Beams: 4
  • - LP-SS: 4 slots with 1 LP-SS in each slot, where 1 LP-SS occupies 7 OFDM symbols and 12 PRBs
  • - LP-WUS: 4 slots with 1 LP-WUS in each slot, where 1 LP-WUS occupies 14 OFDM symbols and 12 PRBs
  • - No LP-WUS assumption under zero-load scenario
| +| Assumption for UE specific wake-up | |
  • - Paging cycle: 1280ms
  • - Paging rate: 1%
| + +Simulation results for zero-load and low-load scenarios based on Cat2 NW power model are shown in **Table Annex 8.4.2-2**. + +**Table Annex8.4.2-2: Network power consumption and power increase under LP-SS and LP-WUS configuration** + +| Cell load | Cases | Network power consumption (Cat2) | Network power increase (%) | +|---------------------------|-------------------------------------------------------------|----------------------------------|----------------------------| +| Zero-load scenario | Baseline
SSB+SIB1 | 7.0249 | | +| | Case1: FDM
SSB+SIB1
LP-SS 320-0-4 | 7.0292 | 0.0624 | +| | Case2: TDM
SSB+SIB1
LP-SS 320-10-4 | 7.0602 | 0.5027 | +| | | | | +| Low-load scenario | Baseline
SSB+SIB1 | 7.3673 | | +| | Case1: FDM
SSB+SIB1
LP-SS 320-0-4
LP-WUS 1280-0-4 | 7.3726 | 0.0716 | +| | Case2: TDM
SSB+SIB1
LP-SS 320-10-4
LP-WUS 1280-5-4 | 7.4192 | 0.7048 | +| | | | | + +**Annex8.4.3[8A-3]** + +| | | +|---------------------|--------------------------------------------| +| Baseline assumption | Zero load scenario, 8SSBs@20ms, SIB1@160ms | +|---------------------|--------------------------------------------| + +**Table Annex8.4.3-1: Additional power consumption for LP-SS (42 symbol duration (3 slots) per beam, 8 beams)** + +| LP-SS (42 symbol duration (3 slots) per beam, 8 beams) | | | | | | | | +|--------------------------------------------------------|-------------------------------------|-------------------------------------|-------------------------------------|--------------------------------------|--------------------------------------|--------------------------------------|---------------------------------------| +| | 8SSBs@20ms, SIB1@160ms, LP-SS@160ms | 8SSBs@20ms, SIB1@160ms, LP-SS@320ms | 8SSBs@20ms, SIB1@160ms, LP-SS@640ms | 8SSBs@20ms, SIB1@160ms, LP-SS@1280ms | 8SSBs@20ms, SIB1@160ms, LP-SS@2560ms | 8SSBs@20ms, SIB1@160ms, LP-SS@5120ms | 8SSBs@20ms, SIB1@160ms, LP-SS@10240ms | +| Additional power consumption | 22.8% | 11.4% | 5.7% | 2.8% | 1.4% | 0.7% | 0.4% | + +**Table Annex8.4.3-2: Additional power consumption for LP-SS (14 symbol duration (1 slot) per beam, 8 beams)** + +| LP-SS (14 symbol duration (1 slot) per beam, 8 beams) | | | | | | | | +|-------------------------------------------------------|-----------------------------|-----------------------------|-----------------------------|-----------------------------|-----------------------------|-----------------------------|-----------------------------| +| | 8SSBs@20ms, SIB1@160ms, LP- | 8SSBs@20ms, SIB1@160ms, LP- | 8SSBs@20ms, SIB1@160ms, LP- | 8SSBs@20ms, SIB1@160ms, LP- | 8SSBs@20ms, SIB1@160ms, LP- | 8SSBs@20ms, SIB1@160ms, LP- | 8SSBs@20ms, SIB1@160ms, LP- | +| | | | | | | | | + +| | SS@160 ms | SS@320 ms | SS@640 ms | SS@1280 ms | SS@2560 ms | SS@5120 ms | SS@10240 ms | +|------------------------------|-----------|-----------|-----------|------------|------------|------------|-------------| +| Additional power consumption | 7.7% | 3.9% | 1.9% | 1.0% | 0.5% | 0.2% | 0.1% | + +**Table Annex8.4.3-3: Additional power consumption for LP-SS (4 symbols per beam, 8 beams)** + +| LP-SS (4 symbols per beam, 8 beams) | | | | | | | | +|-------------------------------------|----------------------------------------|----------------------------------------|----------------------------------------|-----------------------------------------|-----------------------------------------|-----------------------------------------|------------------------------------------| +| | 8 SSBs@20 ms, SIB1@160 ms, LP-SS@160ms | 8 SSBs@20 ms, SIB1@160 ms, LP-SS@320ms | 8 SSBs@20 ms, SIB1@160 ms, LP-SS@640ms | 8 SSBs@20 ms, SIB1@160 ms, LP-SS@1280ms | 8 SSBs@20 ms, SIB1@160 ms, LP-SS@2560ms | 8 SSBs@20 ms, SIB1@160 ms, LP-SS@5120ms | 8 SSBs@20 ms, SIB1@160 ms, LP-SS@10240ms | +| Additional power consumption | 2.2% | 1.1% | 0.6% | 0.3% | 0.1% | 0.1% | 0.0% | + +## Annex8.4.4[8A-5] + +**Table Annex8.4.4-1: Assumptions for network energy consumption evaluation** + +| | | +|--------------------------|-------------------------------------------------------------------------------------------------| +| System bandwidth | 100M | +| SCS | 30KHz | +| LP-SS assumption | Periodicity: 320ms
Time domain resources: 1ms (28 OFDM symbols)
Frequency bandwidth: 5MHz | +| Beam sweeping assumption | {1, 4} beams | + +**Table Annex8.4.4-2: Network power consumption due to LP-SS** + +| Number of paging per second | Beam number | Network energy increasing | +|-----------------------------|-------------|---------------------------| +| 0 (LP-SS only) | 1 | 0.031% | +| 0 (LP-SS only) | 4 | 0.122% | + +## Annex 8.5 System Overhead + +### Annex 8.5.1 [8A-11] + +**Table Annex 8.5.1-1: Resource overhead of LP-WUS to the overall system resource for RRC idle/inactive mode.** + +| Source | # of info. bits | Overhead (%) | T-F resources | Number of paged UE per second | Number of LP-WUS transmissions per second | System configuration, e.g., BW and beam number etc. | Notes | +|---------|-----------------|--------------|-------------------------------|-------------------------------|-------------------------------------------|-----------------------------------------------------|------------------------------------------------------------------------------| +| [8A-11] | 1 | 0.015% | 1 symbol, 5.04MHz (30kHz SCS) | 10 | 10 | 100MHz, 8beams | For IoT, cases, Assuming 1,000,000 user/km2 connection density [ITU M.2412], | +| | 1 | 0.003% | | 10 | 3 | | | + +| | | | | | | | | +|--|---------|--------|-----------------------------------------|----|----|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 8 | 0.06% | 4 symbols,
5.04MHz
(30kHz
SCS) | 10 | 10 | 20MHz,
8beams | with packet arrival every 1 message/2 hours/device [ITU M.2412], assuming 500m ISD with 3 sectors.

The coverage of LP-WUS with 1/4/5 symbols is comparable to or better than Msg 3 coverage | +| | 8 | 0.01% | | 10 | 3 | | | +| | 8 or 12 | 0.075% | 5 symbols,
5.04MHz
(30kHz
SCS) | 10 | 10 | | | +| | 8 or 12 | 0.013% | | 10 | 3 | | | +| | 1 | 0.073% | 1 symbol,
5.04MHz
(30kHz
SCS) | 10 | 10 | | | +| | 1 | 0.018% | | 10 | 3 | | | +| | 8 | 0.29% | 4 symbols,
5.04MHz
(30kHz
SCS) | 10 | 10 | | | +| | 8 | 0.07% | | 10 | 3 | | | +| | 8 or 12 | 0.363% | 5 symbols,
5.04MHz
(30kHz
SCS) | 10 | 10 | | | +| | 8 or 12 | 0.088% | | 10 | 3 | | | +| | 1 | 0.055% | 1 symbol,
5.04MHz
(30kHz
SCS) | 39 | 39 | 100MHz,
8beams | For eMBB cases, Assuming very high population density, e.g., sports event with 5,000 users/cell population density, and per UE paging arrival rate = 1% when paging i-DRX cycle is $T_{\text{pagingcycle}} = 1.28\text{s}$

The coverage of LP-WUS with 1/4/5 symbols is comparable to or better than Msg 3 coverage | +| | 1 | 0.015% | | 39 | 10 | | | +| | 8 | 0.22% | 4 symbols,
5.04MHz
(30kHz
SCS) | 39 | 39 | | | +| | 8 | 0.06% | | 39 | 10 | | | +| | 8 or 12 | 0.275% | 5 symbols,
5.04MHz
(30kHz
SCS) | 39 | 39 | | | +| | 8 or 12 | 0.075% | | 39 | 10 | | | +| | 1 | 0.280% | 1 symbol,
5.04MHz
(30kHz
SCS) | 39 | 39 | | | +| | 1 | 0.070% | | 39 | 10 | | | +| | 8 | 1.12% | 4 symbols,
5.04MHz
(30kHz
SCS) | 39 | 39 | | | +| | 8 | 0.28% | | 39 | 10 | | | +| | 8 or 12 | 1.400% | 5 symbols,
5.04MHz
(30kHz
SCS) | 39 | 39 | 20MHz,
8beams | | +| | 8 or 12 | 0.350% | | 39 | 10 | | | + +**Table Annex 8.5.1-2: Resource overhead of LP-WUS to the overall system resource for RRC connected mode** + +| Source | # of info. bits | Overhead (%) | T-F resources | Traffic type | Number of UE per cell | System configuration, e.g., BW and beam number etc. | Notes | +|---------|-----------------|--------------|------------------------------------------|-----------------|---------------------------------|-----------------------------------------------------|----------------------------------------------------------------------------------------------| +| [8A-11] | 1 | 0.86% | 8 symbols,
5.04MHz
(30kHz
SCS) | XR
(16.67ms) | 10
(maximum system capacity) | 100MHz, one beam | The coverage of LP-WUS with 8/32/40 symbols is comparable to unicast PDCCH AL2-4Rx coverage. | +| | 8 | 3.43% | 32 symbols,
5.04MHz
(30kHz
SCS) | | 10 | | | +| | 12 | 4.29% | 40 symbols,
5.04MHz
(30kHz
SCS) | | 10 | | | + +| | | | | | | | | +|--|----|-------|---------------------------------|------------------------------------|----|------------------|--| +| | | | SCS) | | | | | +| | 1 | 0.07% | 8 symbols, 5.04MHz (30kHz SCS) | FTP3 (mean packet interval= 200ms) | 10 | 100MHz, one beam | | +| | 8 | 0.29% | 32 symbols, 5.04MHz (30kHz SCS) | | 10 | | | +| | 12 | 0.36% | 40 symbols, 5.04MHz (30kHz SCS) | | 10 | | | + +**Table Annex 8.5.1-3: Resource overhead of LP-SS to the system resource for RRC idle/inactive mode** + +| Source | # of info. bits | Overhead (%) | T-F resources | LP-SS periodicity (ms) | System configuration, e.g., BW and beam number etc. | Notes | +|---------|-----------------|--------------|---------------------------------|------------------------|-----------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------| +| [8A-11] | 1 | 0.063% | 14 symbols, 5.04MHz (30kHz SCS) | 320ms | 100MHz, 8beam | The LP-SS coverage is better than msg.3 coverage ; The derivation of LP-SS frequency: 4.32MHz +2RB (30kHz) = 5.04MHz | +| | 1 | 0.0158% | | 1280ms | 100MHz, 8beam | | +| | 1 | 0.002% | | 10240ms | 100MHz, 8beam | | +| | 1 | 0.315% | | 320ms | 20MHz, 8beam | | +| | 1 | 0.079% | | 1280ms | 20MHz, 8beam | | +| | 1 | 0.01% | | 10240ms | 20MHz, 8beam | | +| | 1 | 0.01% | | | | | + +## Annex 8.5.2 [8A-13] + +**Table Annex 8.5.2-1: Assumptions for system overhead evaluation** + +| | | +|---------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------| +| System bandwidth | 100M, 20M | +| SCS | 15KHz, 30KHz | +| LP-SS assumption | Periodicity{160ms, 320ms}
Time domain resources: 14 symbols
Frequency bandwidth: 5MHz | +| LP-WUS assumption | Time domain resources: N2 symbols: 7, 14
Frequency bandwidth 5MHz | +| Assumption for UE specific wake-up | Number of beams: 1, 4 for 15KHz and 1, 4, 8 for 30KHz
$R_{E\_REF} = 1\%, 0.1\%, 0.01\% \text{ or } 0.001\%$ and $Y_{REF} = 1.28$ | +| Assumption for group specific wake-up | Number of UEs in a group: 4, 8 | + +**Table Annex 8.5.2-2: Results summary for system overhead** + +| Source | Signal | Overhead (%) | T-F resources | Inter-arrival time | System configuration, e.g., BW and etc. | Notes | +|---------|--------|----------------------------------------------|------------------------------------------------------------------------|--------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| [8A-13] | LP-SS | 0.125%, 0.625%, | 14 symbols, 5MHz, SCS=15KHz | 160ms | 100M, 20M, 4beam | | +| | LP-SS | 0.0625%, 0.3125% | 14 symbols, 5MHz, SCS=15KHz | 320ms | 100M, 20M, 4beam | | +| | LP-SS | 0.0625%, 0.3125% | 14 symbols, 5MHz, SCS=30KHz | 160ms | 100M, 20M, 4beam | | +| | LP-SS | 0.125%, 0.625% | 14 symbols, 5MHz, SCS=30KHz | 160ms | 100M, 20M, 8beam | | +| | LP-SS | 0.03125%, 0.15625% | 14 symbols, 5MHz, SCS=30KHz | 320ms | 100M, 20M, 4beam | | +| | LP-SS | 0.0625%, 0.3125% | 14 symbols, 5MHz, SCS=30KHz | 320ms | 100M, 20M, 8beam | | +| | LP-WUS | Almost all the cases has <1% system overhead | SCS=15KHz/30KHz
Time domain: 7 / 14 symbols
Frequency domain: 5M | | System bandwidth: 20M, 100M;
Beams:1,4
Number of UE in a group:1,4,8
SCS:15KHz,30KHz
OFDM symbols:7,14
Paging rate:1%,0.1%,0.01%,0.001%
POs number per PF: 1,2,4
PFs number per cycle: 1,2,4,8,16 | Only one case when 20M system bandwidth, 4beams, no grouping, 15KHz, 14OFDM symbols, paging rate 1%, maximum POs per PF, maximum PFs per cycle are configured, the system overhead may reach 1.6%. | + +**Table Annex 8.5.2-3: Some example configuration in extreme conditions and system overhead for LP-WUS** + +| System bandwidth | SCS | Grouping | OFDM symbols | Beams | UE number | Paging rate | PO per PF | PF per cycle | System overhead (%) | +|------------------|-----|----------|--------------|-------|-----------|-------------|-----------|--------------|---------------------| +| 20 | 0 | 1 | 14 | 4 | 20.48 | 0.01 | 4 | 16 | 1.6 | +| 20 | 0 | 1 | 7 | 4 | 20.48 | 0.01 | 4 | 16 | 0.8 | +| 20 | 0 | 1 | 14 | 4 | 10.24 | 0.01 | 4 | 8 | 0.8 | +| 20 | 0 | 1 | 14 | 4 | 10.24 | 0.01 | 2 | 16 | 0.8 | +| 20 | 1 | 1 | 14 | 4 | 20.48 | 0.01 | 4 | 16 | 0.8 | +| 20 | 0 | 1 | 7 | 4 | 10.24 | 0.01 | 4 | 8 | 0.4 | +| 20 | 0 | 1 | 7 | 4 | 10.24 | 0.01 | 2 | 16 | 0.4 | +| 20 | 0 | 1 | 14 | 1 | 20.48 | 0.01 | 4 | 16 | 0.4 | +| 20 | 0 | 1 | 14 | 4 | 5.12 | 0.01 | 4 | 4 | 0.4 | +| 20 | 0 | 1 | 14 | 4 | 5.12 | 0.01 | 2 | 8 | 0.4 | +| 20 | 0 | 1 | 14 | 4 | 5.12 | 0.01 | 1 | 16 | 0.4 | +| 20 | 0 | 4 | 14 | 4 | 20.48 | 0.01 | 4 | 16 | 0.4 | +| 20 | 1 | 1 | 7 | 4 | 20.48 | 0.01 | 4 | 16 | 0.4 | +| 20 | 1 | 1 | 14 | 4 | 10.24 | 0.01 | 4 | 8 | 0.4 | +| 20 | 1 | 1 | 14 | 4 | 10.24 | 0.01 | 2 | 16 | 0.4 | +| 100 | 0 | 1 | 14 | 4 | 20.48 | 0.01 | 4 | 16 | 0.32 | +| 20 | 0 | 1 | 7 | 1 | 20.48 | 0.01 | 4 | 16 | 0.2 | +| 20 | 0 | 1 | 7 | 4 | 5.12 | 0.01 | 4 | 4 | 0.2 | +| 20 | 0 | 1 | 7 | 4 | 5.12 | 0.01 | 2 | 8 | 0.2 | +| 20 | 0 | 1 | 7 | 4 | 5.12 | 0.01 | 1 | 16 | 0.2 | +| 20 | 0 | 1 | 14 | 1 | 10.24 | 0.01 | 4 | 8 | 0.2 | +| 20 | 0 | 1 | 14 | 1 | 10.24 | 0.01 | 2 | 16 | 0.2 | +| 20 | 0 | 1 | 14 | 4 | 2.56 | 0.01 | 4 | 2 | 0.2 | +| 20 | 0 | 1 | 14 | 4 | 2.56 | 0.01 | 2 | 4 | 0.2 | +| 20 | 0 | 1 | 14 | 4 | 2.56 | 0.01 | 1 | 8 | 0.2 | +| 20 | 0 | 4 | 7 | 4 | 20.48 | 0.01 | 4 | 16 | 0.2 | +| 20 | 0 | 4 | 14 | 4 | 10.24 | 0.01 | 4 | 8 | 0.2 | +| 20 | 0 | 4 | 14 | 4 | 10.24 | 0.01 | 2 | 16 | 0.2 | +| 20 | 0 | 8 | 14 | 4 | 20.48 | 0.01 | 4 | 16 | 0.2 | + +| | | | | | | | | | | +|-----|---|---|----|---|-------|------|---|----|------| +| 20 | 1 | 1 | 7 | 4 | 10.24 | 0.01 | 4 | 8 | 0.2 | +| 20 | 1 | 1 | 7 | 4 | 10.24 | 0.01 | 2 | 16 | 0.2 | +| 20 | 1 | 1 | 14 | 1 | 20.48 | 0.01 | 4 | 16 | 0.2 | +| 20 | 1 | 1 | 14 | 4 | 5.12 | 0.01 | 4 | 4 | 0.2 | +| 20 | 1 | 1 | 14 | 4 | 5.12 | 0.01 | 2 | 8 | 0.2 | +| 20 | 1 | 1 | 14 | 4 | 5.12 | 0.01 | 1 | 16 | 0.2 | +| 20 | 1 | 4 | 14 | 4 | 20.48 | 0.01 | 4 | 16 | 0.2 | +| 100 | 0 | 1 | 7 | 4 | 20.48 | 0.01 | 4 | 16 | 0.16 | +| 100 | 0 | 1 | 14 | 4 | 10.24 | 0.01 | 4 | 8 | 0.16 | +| 100 | 0 | 1 | 14 | 4 | 10.24 | 0.01 | 2 | 16 | 0.16 | + +## Annex 8.5.3 [8A-5] + +**Table Annex 8.5.3-1: Assumptions for system overhead evaluation** + +| | | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------| +| System bandwidth | 100M | +| SCS | 30KHz | +| LP-SS assumption | Periodicity: 320ms
Time domain resources: 1ms (28 OFDM symbols)
Frequency bandwidth: 5MHz | +| LP-WUS assumption | Bit length: 24
Time domain resources: {12, 24, 48} OFDM symbols, for {1, 2, 4} repetitions
Frequency bandwidth: 5MHz | +| Beam sweeping assumption | {1, 4} beams | +| Paging number per second | 0 for LP-SS only (i.e. empty load)
50 for LP-SS and LP-WUS | + +**Table Annex 8.5.3-2: Results summary for system overhead** + +| Number of paging per second | Repetition number of LP-WUS | Beam number | Resource overhead | +|-----------------------------|-----------------------------|-------------|-------------------| +| 0 (LP-SS only) | - | 1 | 0.016% | +| 0 (LP-SS only) | - | 4 | 0.063% | +| 50 (LP-SS+LP-WUS) | 1 | 1 | 0.123% | +| 50 (LP-SS+LP-WUS) | 2 | 1 | 0.230% | +| 50 (LP-SS+LP-WUS) | 4 | 1 | 0.444% | +| 50 (LP-SS+LP-WUS) | 1 | 4 | 0.491% | +| 50 (LP-SS+LP-WUS) | 2 | 4 | 0.920% | +| 50 (LP-SS+LP-WUS) | 4 | 4 | 1.777% | + +## Annex 8.5.4 [8A-16] + +**Table Annex 8.5.4-1: LP-WUS system overhead** + +| LP-WUS overhead | | | | | | | | | | +|-----------------|--------------------------------------|------------------------|-----------------------|-------------------------|------------------------|------------------------|-----------------------|-------------------------|------------------------| +| | Note | IDRX, 20Groups, 10kbps | IDRX, 20Groups, 5kbps | IDRX, 100Groups, 10kbps | IDRX, 100Groups, 5kbps | eDRX, 20Groups, 10kbps | eDRX, 20Groups, 5kbps | eDRX, 100Groups, 10kbps | eDRX, 100Groups, 5kbps | +| System config | system BW (MHz) | 20 | 20 | 20 | 20 | 20 | 20 | 20 | 20 | +| | total number of Idle UEs in the cell | 20 | 20 | 100 | 100 | 20 | 20 | 100 | 100 | +| LP-WUS | # of info | 6 | 6 | 6 | 6 | 6 | 6 | 6 | 6 | + +| | | | | | | | | | | +|------------------|---------------------------------------------------------------------------------------------------|---------|---------|---------|---------|---------|---------|---------|---------| +| config | bits | | | | | | | | | +| | data rate (kbps) | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | +| | LP-WUS time duration (ms) | 0.6 | 0.6 | 0.6 | 0.6 | 0.6 | 0.6 | 0.6 | 0.6 | +| | bandwidth (MHz) | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | +| | Monitoring occasion periodicity (ms) | 1280 | 1280 | 1280 | 1280 | 82900 | 82900 | 82900 | 82900 | +| | LP-WUS resource per group (ms*MHz) | 3 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | +| | WUS group size | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | +| | number of LP-WUS groups | 20 | 20 | 100 | 100 | 20 | 20 | 100 | 100 | +| Page Traffic | per group page inter arrival time (sec) | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| | R_G per group per periodicity | 0.7220 | 0.7220 | 0.7220 | 0.7220 | 1.0000 | 1.0000 | 1.0000 | 1.0000 | +| | # of LP-WUS transmission per sec | 11.2807 | 11.2807 | 56.4033 | 56.4033 | 0.2413 | 0.2413 | 1.2063 | 1.2063 | +| System Resources | total system resources per LP-WUS periodicity (ms*MHz) | 25600 | 25600 | 25600 | 25600 | 1658000 | 1658000 | 1658000 | 1658000 | +| LP-WUS resources | actually used monitoring occasion resources used for LP-WUS tx per group per periodicity (ms*MHz) | 2.17 | 2.17 | 2.17 | 2.17 | 3.00 | 3.00 | 3.00 | 3.00 | +| | total LP-WUS resources per LP-WUS periodicity | 43.32 | 43.32 | 216.59 | 216.59 | 60.00 | 60.00 | 300.00 | 300.00 | +| | LP-WUS overhead (%) | 0.1692% | 0.1692% | 0.8461% | 0.8461% | 0.0036% | 0.0036% | 0.0181% | 0.0181% | + +**Table Annex 8.5.4-2: LP-SS system overhead** + +| LP-SS overhead | | | | | | | | +|-----------------|--------------------------------------------------------|------------------------------------|-----------------------------------|-----------------------------------|------------------------------------|-----------------------------------|-----------------------------------| +| | Note | 10bits,
periodicity
= 1000ms | 10bits,
periodicity
= 500ms | 10bits,
periodicity
= 200ms | 15bits,
periodicity
= 1000ms | 15bits,
periodicity
= 500ms | 15bits,
periodicity
= 200ms | +| System config | system BW (MHz) | 20 | 20 | 20 | 20 | 20 | 20 | +| LP-SS config | # of info bits | 10 | 10 | 10 | 15 | 15 | 15 | +| | data rate (kbps) | 10 | 10 | 10 | 10 | 10 | 10 | +| | LP-WUS time duration (ms) | 1 | 1 | 1 | 1.5 | 1.5 | 1.5 | +| | bandwidth (MHz) | 5 | 5 | 5 | 5 | 5 | 5 | +| | Monitoring occasion periodicity (ms) | 1000 | 500 | 200 | 1000 | 500 | 200 | +| | LP-SS resource per periodicity (ms*MHz) | 5 | 5 | 5 | 7.5 | 7.5 | 7.5 | +| Resources | total system resources per LP-WUS periodicity (ms*MHz) | 20000 | 10000 | 4000 | 20000 | 10000 | 4000 | +| LP-SS resources | # of LP-SS repetition per LP-SS burst | 4 | 4 | 4 | 4 | 4 | 4 | +| | total LP-SS resources per periodicity | 20 | 20 | 20 | 30 | 30 | 30 | +| | LP-SS overhead (%) | 0.10% | 0.20% | 0.50% | 0.15% | 0.30% | 0.75% | + +## Annex 8.5.5 [8A-4] + +For coverage and resource overhead evaluation, we consider a LP-WUS consisting of a payload field carrying 16 information bits and a Frame Check Sequence (FCS) field carrying 8 CRC bits. The LP-SS is a 32-bit low density sequence (i.e., a sequence with lower number of 1 bits compared to 0 bits, 2 ON bits are considered in every 8 bits) occupying 4 OFDM symbols. + +- LP-WUS-1: Waveform Option OOK-4 with M=2 +- LP-WUS-2: Waveform Option FSK-2 with M=2 +- LP-SS: Waveform Option OOK-4 with M=8 + +For both LP-WUS options, a SCS of 30 kHz, a 4.32 MHz LP-WUS bandwidth, and a 2.6 GHz Urban scenario (TDL-C 300) are considered. A 1/2 Manchester code is used for LP-WUS-1 resulting in an information data rate of 28kbps leading to payload+CRC occupying a total of 24 OFDM symbols. On the other hand, an information data rate of 56kbps is achieved by LP-WUS-2 leading to payload+CRC only occupying a total of 12 OFDM symbols. The coverage evaluation methodology in TR38.830 is used and the analysis is shown in **Table Annex 8.5.5-1** below. + +**Table Annex 8.5.5-1: Link budget analysis for PUSCH (Msg.3) and LP-WUS/LP-SS** + +| Channel for evaluation | Msg.3 PUSCH | LP-WUS-1 | LP-WUS-2 | LP-SS | +|--------------------------------|--------------------|--------------------|--------------------|--------------------| +| Scenario and Carrier Frequency | FR1: Urban 2.6 GHz | FR1: Urban 2.6 GHz | FR1: Urban 2.6 GHz | FR1: Urban 2.6 GHz | +| Cell area reliability (%) | 90% | 99% | 99% | 99% | +| Transmitter | | | | | +| (1) Number of transmit antenna | 1 | 192 | 192 | 192 | + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------|-------------|-------------| +| elements | | | | | +| (2) Number of transmit TxRUs | - | 64 | 64 | 64 | +| (2a) Number of transmit chains modelled in LLS | 1 | 2 | 2 | 2 | +| (3) Total transmit power (dBm) | 23 | 53 | 53 | 53 | +| Note: total transmit power for system bandwidth | | | | | +| (3a) System bandwidth for downlink, or occupied bandwidth for uplink (Hz) | 720000 | 100000000 | 100000000 | 100000000 | +| (3b) Power Spectrum Density = (3) - 10 log( (3a) / 1000000 ) (dBm/MHz) | 24.42667504 | 33 | 33 | 33 | +| (3c) Bandwidth used for the evaluated channel (Hz) | 720000 | 4320000 | 4320000 | 4320000 | +| (3bis) Total transmit power for occupied bandwidth = (3b) + 10 log ( (3c) / 1000000 ) (dBm) | 23 | 39.35483747 | 39.35483747 | 39.35483747 | +| (4) Total antenna gain at antenna gain component 3 & antenna gain component 4 of transmitter = (4a) – (4b) (dB) | 0 | 12.77121255 | 12.77121255 | 12.77121255 | +| (4a) Antenna gain at antenna gain component 3 & antenna gain component 4 of transmitter | | | | | +| = (4c) + 10 log ( (1) / (2) ) (dB) for downlink, and | 0 | 12.77121255 | 12.77121255 | 12.77121255 | +| = (4c) + 10 log ( (1) / (2a) ) (dB) for uplink | | | | | +| (4b) Antenna gain correction factor at antenna gain component 3 & antenna gain component 4 of transmitter (dB) | 0 | 0 | 0 | 0 | +| (4c) Gain of antenna element (dBi) | 0 | 8 | 8 | 8 | +| (5) Total antenna gain at antenna gain component 2 of transmitter = (5a) - (5b) (dB) | 0 | 15.05149978 | 15.05149978 | 15.05149978 | +| Note: zero for uplink | | | | | +| (5a) Antenna gain at antenna gain component 2 of transmitter = 10 log( (2)/(2a)) (dB) | 0 | 15.05149978 | 15.05149978 | 15.05149978 | +| Note: zero for uplink | | | | | +| (5b) Antenna gain correction factor at antenna gain component 2 of transmitter (dB) | 0 | 0 | 0 | 0 | +| Note: zero for uplink | | | | | +| (8) Cable, connector, combiner, body losses, etc. (enumerate sources) (dB) (feeder loss must be included for and only for downlink) | 1 | 3 | 3 | 3 | +| (9) EIRP = (3bis) + (4) + (5) – (8) dBm | 22 | 64.1775498 | 64.1775498 | 64.1775498 | +| Receiver | | | | | +| (10) Number of receive antenna elements | 192 | 1 | 1 | 1 | +| (10a) Number of receive TxRUs | 64 | - | - | - | +| Note: this row is void (empty) for downlink | | | | | +| (10b) Number of receive chains modelled in LLS | 2 | 1 | 1 | 1 | +| (11) Total antenna gain at antenna gain component 3 & antenna gain component 4 of receiver = (11a) - (11b) (dB) | 12.77121255 | 0 | 0 | 0 | +| (11a) Antenna gain at antenna gain component 3 & antenna gain component 4 of receiver | 12.77121255 | 0 | 0 | 0 | + +| | | | | | +|------------------------------------------------------------------------------------------------------------------------------------|--------------|--------------|--------------|--------------| +| $= (11c) + 10 \log ( (10)/(10a) )$ (dB) for uplink | | | | | +| $= (11c) + 10 \log ( (10)/(10b) )$ (dB) for downlink | | | | | +| (11b) Antenna gain correction factor at antenna gain component 3 & antenna gain component 4 of receiver (dB) | 0 | 0 | 0 | 0 | +| (11c) Gain of antenna element (dBi) | 8 | 0 | 0 | 0 | +| (11bis) Total antenna gain at antenna gain component 2 of receiver $= (11bis-a) - (11bis-b)$ (dB) | 15.05149978 | 0 | 0 | 0 | +| Note: zero for downlink | | | | | +| (11bis-a) Antenna gain at antenna gain component 2 of receiver $= 10 \log ( (10a)/(10b) )$ (dB) | 15.05149978 | 0 | 0 | 0 | +| Note: zero for downlink | | | | | +| (11bis-b) Antenna gain correction factor at antenna gain component 2 of receiver (dB) | 0 | 0 | 0 | 0 | +| Note: zero for downlink | | | | | +| (12) Cable, connector, combiner, body losses, etc. (enumerate sources) (dB) (feeder loss must be included for and only for uplink) | 3 | 1 | 1 | 1 | +| (13) Receiver noise figure (dB) | 5 | 12 | 12 | 12 | +| (14) Thermal noise density (dBm/Hz) | -174 | -174 | -174 | -174 | +| (15) Receiver interference density (dBm/Hz) | -165.7 | -169.3 | -169.3 | -169.3 | +| (16) Total noise plus interference density $= 10 \log ( 10^{((13) + (14))/10} + 10^{((15)/10)} )$ (dBm/Hz) | -164.0335231 | -161.2583889 | -161.2583889 | -161.2583889 | +| (18) Effective noise power $= (16) + 10 \log ((3c))$ (dBm) | -105.4601981 | -94.90355143 | -94.90355143 | -94.90355143 | +| (19) Required SNR (dB) | -2.2 | 1.4 | 4.3 | 0.9 | +| (20) Receiver implementation margin (dB) | 2 | 2 | 2 | 2 | +| (21) H-ARQ gain (dB) | | | | | +| Note: Only applicable if HARQ is not considered in LLS | 0.5 | 0 | 0 | 0 | +| (22) Receiver sensitivity $= (18) + (19) + (20) - (21)$ (dBm) | -106.1601981 | -91.50355143 | -88.60355143 | -92.00355143 | +| (22bis) MCL $= (3bis) - (22) + (5) + (11bis)$ (dB) | 144.2116979 | 145.9098887 | 143.0098887 | 146.4098887 | +| (23) Hardware link budget, a.k.a. MIL $= (9) + (11) + (11bis) - (12) - (22)$ (dB) | 152.9829104 | 154.6811012 | 151.7811012 | 155.1811012 | + +The resource overhead incurred only by the LP-SS is evaluated in **Table Annex 8.5.5-2** where system bandwidths $\in \{20 \text{ MHz}, 100 \text{ MHz}\}$ and number of beams $\in \{1, 4, 8\}$ are considered. Further, periodicities $\in [320 \text{ ms}, 10240 \text{ ms}]$ are considered. + +**Table Annex 8.5.5-2: Resource overhead for LP-SS** + +| System Bandwidth | 20 MHz | | | 100 MHz | | | +|-------------------|---------|---------|---------|---------|---------|---------| +| Number of Beams | 1 | 4 | 8 | 1 | 4 | 8 | +| LP-SS Periodicity | | | | | | | +| 320 ms | 0.0113% | 0.0450% | 0.0900% | 0.0023% | 0.0090% | 0.0180% | +| 640 ms | 0.0056% | 0.0225% | 0.0450% | 0.0011% | 0.0045% | 0.0090% | + +| | | | | | | | +|-----------------|---------|---------|---------|---------|---------|---------| +| 1280 ms | 0.0028% | 0.0113% | 0.0225% | 0.0006% | 0.0023% | 0.0045% | +| 2560 ms | 0.0014% | 0.0056% | 0.0113% | 0.0003% | 0.0011% | 0.0023% | +| 5120 ms | 0.0007% | 0.0028% | 0.0056% | 0.0001% | 0.0006% | 0.0011% | +| 10240 ms | 0.0004% | 0.0014% | 0.0028% | 0.0001% | 0.0003% | 0.0006% | + +Next, the resource overhead for LP-WUS-1 and LP-WUS-2 is evaluated in **Table Annex 8.5.5-3** for IoT use case according to the mMTC usage scenario with a connection density requirement of $\geq 10^6$ devices/ as defined in the ITU-R M.2410 report on "Minimum requirements related to technical performance for IMT-2020 radio interface(s)". Additionally, paging arrival is considered according to the traffic model with 1 message/2 hours/device or 1 message/day/device as defined in the ITU-R M.2412 report on "Guidelines for evaluation of radio interface technologies for IMT-2020". Further, a hexagonal network layout with inter-site distance (ISD) of 500m and 3 Transmission Reception Points (TRxPs) per site is considered. The average number of UEs to be simultaneously addressed in a LP-WUS is assumed to be $N_a \in \{1, 4\}$ . The results in **Table Annex 8.5.5-2** and **Table Annex 8.5.5-3** suggest that LP-SS/LP-WUS can be supported for IoT use case in urban deployments with coverage close to or exceeding that of PUSCH Msg3 at a resource overhead considering devices/km2 connection density, system bandwidth $\geq 20$ MHz, number of transmission beams $\leq 8$ , and per UE paging arrival rate $\leq 1$ message/2 hours. + +**Table Annex 8.5.5-3: Resource overhead for LP-WUS considering devices/km2 connection density** + +| System Bandwidth | | 20 MHz | | | 100 MHz | | | | +|------------------|----------------------------------------------------------------------------------|-----------------|---------|---------|---------|---------|---------|---------| +| Number of Beams | | 1 | 4 | 8 | 1 | 4 | 8 | | +| Waveform | Traffic Model, | | | | | | | | +| | LP-WUS-1 | Model-1, | 0.2165% | 0.8660% | 1.7321% | 0.0433% | 0.1732% | 0.3464% | +| | | Model-1, | 0.0541% | 0.2165% | 0.4330% | 0.0108% | 0.0433% | 0.0866% | +| | | Model-2, | 0.0180% | 0.0722% | 0.1443% | 0.0036% | 0.0144% | 0.0289% | +| | | Model-2, | 0.0045% | 0.0180% | 0.0361% | 0.0009% | 0.0036% | 0.0072% | +| | LP-WUS-2 | Model-1, | 0.1083% | 0.4330% | 0.8660% | 0.0217% | 0.0866% | 0.1732% | +| | | Model-1, | 0.0271% | 0.1083% | 0.2165% | 0.0054% | 0.0217% | 0.0433% | +| | | Model-2, | 0.0090% | 0.0361% | 0.0722% | 0.0018% | 0.0072% | 0.0144% | +| | | Model-2, | 0.0023% | 0.0090% | 0.0180% | 0.0005% | 0.0018% | 0.0036% | +| | Model-1: 1 message/2 hours/device
Model-2: 1 message/day/device | | | | | | | | + +### Annex 8.5.6 [8A-3] + +We show network overhead impact with LP-WUS for different cases below. Evaluation details are given in RANI#113 contribution [4]. + +- The total available resources are calculated assuming carrier bandwidth of 20 MHz (51 PRBs with 30 kHz SCS) and a TDD pattern with 4:1 ratio for DL:UL +- WUS payload: + - 1bit,8bits,48bits +- WSU Coverage target + - Msg3-PUSCH: {w/o retransmission, w/ two retransmissions} + - PDCCH: {1Rx, AL16}, {2Rx, AL16} + - Note: WUS structure to meet the coverage target is based on results in clause 2.1 +- Beam-sweeping assumptions: + - No beam-sweeping + - Beam-sweeping for both RRM and WUS monitoring assuming 8 beams + +- Traffic + - $R\_E = 0.1\%$ (additional results for $R\_E = 1\%$ included in the spreadsheet attached to this document) + - Total 250 idle-mode UEs in a cell +- FAR assumption (FAR\_target, N, T) + - $\{0.1\%, 1, 1.28s\}$ +- Number of UEs per subgroup: + - $\{1, 4\}$ , 4 only applied for $\{1, 8\}$ bit WUS payload +- Duty cycled WUS monitoring with 1.28s duty cycle is assumed for the results +- LP-SS overhead of 3slots per 1.28s assumed for case of $P\_WUR=0.5$ , no extra sync signal overhead assumed for $P\_WUR = \{4, 10\}$ . + +**Table Annex 8.5.6-1: Network overhead for different cases with 1UE/subgroup** + +| 1UE per subgroup | Payload | 1bit | | | | 8bit | | | | 48bit | | | | +|----------------------------------------------|-----------------|-----------|-----------|-------------|-------------|-----------|-----------|-------------|-------------|-----------|-----------|-------------|-------------| +| $R\_E = 0.1\%$ | | Msg3 0rtx | Msg3 2rtx | PDCC H 1 Rx | PDCC H 2 Rx | Msg3 0rtx | Msg3 2rtx | PDCC H 1 Rx | PDCC H 2 Rx | Msg3 0rtx | Msg3 2rtx | PDC CH 1 Rx | PDC CH 2 Rx | +| No beam sweeping (single beam) | $P_{WUR} = 0.5$ | 0,0427 % | 0,0519 % | 0,0549 % | 0,0885 % | 0,0580 % | 0,1129 % | 0,1434 % | 0,2960 % | 0,125 1% | 0,384 5% | 0,454 7% | 1,217 7% | +| | $P_{WUR} = 4$ | 0,0006 6% | 0,0008 3% | 0,0010 0% | 0,0018 3% | 0,0019 9% | 0,0019 9% | 0,0019 9% | 0,0024 9% | | | | | +| | $P_{WUR} = 10$ | 0,0006 6% | 0,0008 3% | 0,0010 0% | 0,0018 3% | 0,0019 9% | 0,0019 9% | 0,0019 9% | 0,0024 9% | | | | | +| Beam sweeping on LP-SS +LP-WUS (eight beams) | $P_{WUR} = 0.5$ | 0,3418 % | 0,4150 % | 0,4395 % | 0,7080 % | 0,4639 % | 0,9033 % | 1,1475 % | 2,3682 % | 1,001 0% | 3,076 2% | ** | ** | +| | $P_{WUR} = 4$ | 0,0053 2% | 0,0066 4% | 0,0079 7% | 0,0146 2% | 0,0159 5% | 0,0159 5% | 0,0159 5% | 0,0199 3% | | | | | +| | $P_{WUR} = 10$ | 0,0053 2% | 0,0066 4% | 0,0079 7% | 0,0146 2% | 0,0159 5% | 0,0159 5% | 0,0159 5% | 0,0199 3% | | | | | + +\*\* Due to long WUS duration, beam-sweeping for LP-WUS with 48bits payload will be longer than paging cycle 1.28s +Baseline overhead based on PDCCH, AL16, 2 OFDM symbols with 8 beams is 0.012%. + +**Table Annex 8.5.6-2: Network overhead for different cases with 4UE/subgroup** + +| 4UE per subgroup | Payload | 1bit | | | | 8bit | | | | +|--------------------------------|-----------------|-----------|-----------|------------|------------|-----------|-----------|------------|------------| +| $R\_E = 0.1\%$ | | Msg3 0rtx | Msg3 2rtx | PDCCH 1 Rx | PDCCH 2 Rx | Msg3 0rtx | Msg3 2rtx | PDCCH 1 Rx | PDCCH 2 Rx | +| No beam sweeping (single beam) | $P_{WUR} = 0.5$ | 0,0427% | 0,0519% | 0,0549% | 0,0885% | 0,0580% | 0,1129% | 0,1434% | 0,2960% | +| | $P_{WUR} = 4$ | 0,00066% | 0,00083% | 0,00100% | 0,00183% | 0,00199% | 0,00199% | 0,00199% | 0,00249% | +| | $P_{WUR} = 10$ | 0,00066% | 0,00083% | 0,00100% | 0,00183% | 0,00199% | 0,00199% | 0,00199% | 0,00249% | +| Beam sweeping on | $P_{WUR} = 0.5$ | 0,3418% | 0,4150% | 0,4395% | 0,7080% | 0,4639% | 0,9033% | 1,1475% | 2,3682% | + +| | | | | | | | | | | +|--------------------------------------------------------------------------------|-----------------------------|----------|----------|----------|----------|----------|----------|----------|----------| +| LP-SS +LP-WUS
(eight beams) | PWUR = 4 | 0,00532% | 0,00664% | 0,00797% | 0,01462% | 0,01595% | 0,01595% | 0,01595% | 0,01993% | +| | PWUR = 10 | 0,00532% | 0,00664% | 0,00797% | 0,01462% | 0,01595% | 0,01595% | 0,01595% | 0,01993% | +| Baseline overhead based on PDCCH, AL16, 2 OFDM symbols with 8 beams is 0.012%. | | | | | | | | | | + +Overall following observations can be made on NW overhead based on the results in this and previous contributions. + +For WUS to match PDCCH 2Rx coverage, following overhead values for different WUS candidates (including sync resource overhead) are observed from the evaluations (250 Idle UEs/cell assumed): + +- For per UE paging rate of 0.1% (1%) + - Baseline overhead for paging PDCCH is 0.012% (0.12%) + - For OFDM (SSS-sequence-based) WUS with 8-bit payload (4UEs/subgroup): ~1.65x (~1.45x) higher overhead compared to baseline is required + - For OOK-WUS with 8 bit payload (4UEs/subgroup): ~196x (~154x) higher overhead compared to baseline is required + - For OOK-WUS with 48 bit payload (no subgrouping): ~830x higher overhead compared to baseline (for 1% UE paging rate, overhead is prohibitively high) + +Following general observations can be made for network overhead from the evaluations. + +- Regarding WUR on power (PWUR) + - Overhead for OOK-based-WUS (e.g., PWUR=0.5) is roughly ~50-100x higher compared to that of OFDM-based-WUS (e.g., PWUR=4, 10) as the OOK-based WUS duration required to achieve the same coverage target as OFDM-based WUS is much higher and there is a need for additional periodic LP-SS transmissions. +- Regarding WUS payload + - Overhead for OOK-based WUS with 48-bit payload is significantly higher than that of OOK-based WUS with 1- or 8-bit payload (~ 5x higher for single beam and eight beams). + - Overhead for 8-bit WUS is slightly higher than that of 1-bit WUS. +- Regarding number of UEs per subgroup + - Overhead with 4 UEs per subgroup is similar to that of 1 UE per subgroup as the assumed low paging rate results in low probability of having UEs being paged in the same group in the same paging cycle. + +## Annex 8.5.7 [8A-9] + +**Table Annex 8.5.7-1: System overhead for LP-WUS for RRC IDLE/INACTIVE** + +| Signal | # of info bits carried by signal | Overhead (%) | T resources per beam | F resources | SCS | number of paged UE per second or signal periodicity | number of UE per group | Number of LP-WUS transmissions per second | System configuration, e.g., BW and etc. | the target channel | Notes | +|--------|----------------------------------|--------------|----------------------|-------------|-------|-----------------------------------------------------|------------------------|-------------------------------------------|-----------------------------------------|--------------------|--------------------------------------------------------------------------| +| LP-WUS | 48 | 0.0720 % | 48 symbols | 5.04MHz | 30kHz | 10 | 1 | 10 | 20MHz, 1beam | Msg.3 | OOK-4 when 8 OFDM symbols are used. OOK-1 when 64 OFDM symbols are used. | +| LP-WUS | 48 | 0.2808 % | 48 symbols | 5.04MHz | 30kHz | 39 | 1 | 39 | 20MHz, 1beam | Msg.3 | | +| LP-WUS | 48 | 0.3600 % | 48 symbols | 5.04MHz | 30kHz | 50 | 1 | 50 | 20MHz, 1beam | Msg.3 | | +| LP-WUS | 48 | 0.5760 % | 48 symbols | 5.04MHz | 30kHz | 10 | 1 | 10 | 20MHz, 1beam | Msg.3 | | +| LP-WUS | 48 | 2.2464 % | 48 symbols | 5.04MHz | 30kHz | 39 | 1 | 39 | 20MHz, 1beam | Msg.3 | | +| LP-WUS | 48 | 2.8800 % | 48 symbols | 5.04MHz | 30kHz | 50 | 1 | 50 | 20MHz, 1beam | Msg.3 | | + +| | | | | | | | | | | | | +|--------|----|----------|------------|---------|-------|----|---|-----|---------------|-------|-------------| +| LP-WUS | 48 | 0.0144 % | 48 symbols | 5.04MHz | 30kHz | 10 | 1 | 10 | 100MHz, 1beam | Msg.3 | Is are used | +| LP-WUS | 48 | 0.0562 % | 48 symbols | 5.04MHz | 30kHz | 39 | 1 | 39 | 100MHz, 1beam | Msg.3 | | +| LP-WUS | 48 | 0.0720 % | 48 symbols | 5.04MHz | 30kHz | 50 | 1 | 50 | 100MHz, 1beam | Msg.3 | | +| LP-WUS | 48 | 0.1152 % | 48 symbols | 5.04MHz | 30kHz | 10 | 1 | 10 | 100MHz, 1beam | Msg.3 | | +| LP-WUS | 48 | 0.4493 % | 48 symbols | 5.04MHz | 30kHz | 39 | 1 | 39 | 100MHz, 1beam | Msg.3 | | +| LP-WUS | 48 | 0.5760 % | 48 symbols | 5.04MHz | 30kHz | 50 | 1 | 50 | 100MHz, 1beam | Msg.3 | | +| LP-WUS | 48 | 0.0072 % | 48 symbols | 5.04MHz | 30kHz | 10 | 1 | 1 | 20MHz, 1beam | Msg.3 | | +| LP-WUS | 48 | 0.0281 % | 48 symbols | 5.04MHz | 30kHz | 39 | 1 | 3.9 | 20MHz, 1beam | Msg.3 | | +| LP-WUS | 48 | 0.0360 % | 48 symbols | 5.04MHz | 30kHz | 50 | 1 | 5 | 20MHz, 1beam | Msg.3 | | +| LP-WUS | 48 | 0.0576 % | 48 symbols | 5.04MHz | 30kHz | 10 | 1 | 1 | 20MHz, 1beam | Msg.3 | | +| LP-WUS | 48 | 0.2246 % | 48 symbols | 5.04MHz | 30kHz | 39 | 1 | 3.9 | 20MHz, 1beam | Msg.3 | | +| LP-WUS | 48 | 0.2880 % | 48 symbols | 5.04MHz | 30kHz | 50 | 1 | 5 | 20MHz, 1beam | Msg.3 | | +| LP-WUS | 48 | 0.0014 % | 48 symbols | 5.04MHz | 30kHz | 10 | 1 | 1 | 100MHz, 1beam | Msg.3 | | +| LP-WUS | 48 | 0.0056 % | 48 symbols | 5.04MHz | 30kHz | 39 | 1 | 3.9 | 100MHz, 1beam | Msg.3 | | +| LP-WUS | 48 | 0.0072 % | 48 symbols | 5.04MHz | 30kHz | 50 | 1 | 5 | 100MHz, 1beam | Msg.3 | | +| LP-WUS | 48 | 0.0115 % | 48 symbols | 5.04MHz | 30kHz | 10 | 1 | 1 | 100MHz, 1beam | Msg.3 | | +| LP-WUS | 48 | 0.0449 % | 48 symbols | 5.04MHz | 30kHz | 39 | 1 | 3.9 | 100MHz, 1beam | Msg.3 | | +| LP-WUS | 48 | 0.0576 % | 48 symbols | 5.04MHz | 30kHz | 50 | 1 | 5 | 100MHz, 1beam | Msg.3 | | + +## Annex X: Change history + +| Change history | | | | | | | | +|----------------|-------------|---------------------------|----|-----|-----|--------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-10 | RAN1#110bis | R1-2208666 | | | | Baseline TR skeleton | 0.0.0 | +| 2022-10 | RAN1#110bis | R1-2210430 | | | | Baseline TR skeleton after discussion | 0.0.1 | +| 2023-02 | RAN1#112 | R1-2302236 | | | | Update TR and incorporating agreements for evaluation and receiver architecture from RAN1#110bis and RAN1#111 | 0.1.0 | +| 2023-05 | RAN1#113 | R1-2305954 | | | | Update TR and incorporates agreements from RAN1#112 and RAN1#112bis | 0.2.0 | +| 2023-08 | RAN1#114 | R1-2308386 | | | | Implemented all the agreements until RAN1#113
Resolved FFS issues according to the consensus in offline discussion.
Other format and editorial issues. | 0.3.0 | +| 2023-08 | RAN1#114 | R1-2308729 | | | | Incorporates agreements after RAN1#114 | 0.4.0 | +| 2023-09 | RAN#101 | RP-231814 | | | | Submit to RAN Plenary for information | 1.0.0 | +| 2023-10 | RAN1#114bis | R1-2310652 | | | | Incorporating RAN4 agreements, other miscellaneous cleanings | 1.1.0 | +| 2023-10 | RAN1#114bis | R1-2310773 | | | | MCC clean-up | 1.1.1 | +| 2023-12 | RAN1#115 | R1-2312819
/ RP-233068 | | | | Incorporates RAN2 and RAN4 TPs. Editorial corrections. | 2.0.0 | +| 2023-12 | RAN#102 | R1-2312819 | | | | Rel-18 TR under change control further to RAN approval | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38881/3493d7ba4c86f944e159de1bf45ff03d_img.jpg b/marked/Rel-18/38_series/38881/3493d7ba4c86f944e159de1bf45ff03d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..33d1565b251a745eba63ec5e063d06fb7f5074d1 --- /dev/null +++ b/marked/Rel-18/38_series/38881/3493d7ba4c86f944e159de1bf45ff03d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7d4e1c2750a9deb49d6b1e8bd668397b35b779058be55bfbc6d4aca84b9cd6c9 +size 42775 diff --git a/marked/Rel-18/38_series/38881/6279fafb3a874e174648eb907385c954_img.jpg b/marked/Rel-18/38_series/38881/6279fafb3a874e174648eb907385c954_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c107a67fa15c4b6d293b68f32996de7565a8d16 --- /dev/null +++ b/marked/Rel-18/38_series/38881/6279fafb3a874e174648eb907385c954_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f82112a2685124b81d674b4b66f2290ec437135df99ac84c74c277e1e3a47cac +size 36193 diff --git a/marked/Rel-18/38_series/38881/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/marked/Rel-18/38_series/38881/65e8c0628536d6d4245e9ab46ba070c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..158f7f7013ab7e79f65f3e9c79d1d9735bf7bbc3 --- /dev/null +++ b/marked/Rel-18/38_series/38881/65e8c0628536d6d4245e9ab46ba070c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f0a1a0ef924f661659c6f3bb6e56f6893793a0286cad3c67d5f09d7ab35029d +size 20794 diff --git a/marked/Rel-18/38_series/38881/a85105fd544c64ef624aa45c72378647_img.jpg b/marked/Rel-18/38_series/38881/a85105fd544c64ef624aa45c72378647_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e2620caf8d0459aec5f6027601e50cef3e12bc0 --- /dev/null +++ b/marked/Rel-18/38_series/38881/a85105fd544c64ef624aa45c72378647_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c6dc3940466717806e3758e40975eb7ae53054920cc60b839d66f960bc1a547b +size 42555 diff --git a/marked/Rel-18/38_series/38892/1eadbbe42cfcac5c0023577110aec5e3_img.jpg b/marked/Rel-18/38_series/38892/1eadbbe42cfcac5c0023577110aec5e3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c795918a58278af90ef3407ff5504ed6e4e8ccf2 --- /dev/null +++ b/marked/Rel-18/38_series/38892/1eadbbe42cfcac5c0023577110aec5e3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a53c84fd21dd4429d1116b6ed4b6b6e5932c79644a9827dfd4e6334e06b407e2 +size 28335 diff --git a/marked/Rel-18/38_series/38892/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38892/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b5996c34ba7d331cc98324a7a10606ca06de05b --- /dev/null +++ b/marked/Rel-18/38_series/38892/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b4184804d42dd3d658dcaa38810ae72acac57a56388926aa4924a668b3a06848 +size 9539 diff --git a/marked/Rel-18/38_series/38892/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38892/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d21ed91496861f11965a7af016e81e9bb24c96ba --- /dev/null +++ b/marked/Rel-18/38_series/38892/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b7204739b17432a635122ac4bdf4e1dd57fae4e01741bffc7f4b7eff75a599a6 +size 5728 diff --git a/marked/Rel-18/38_series/38892/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg b/marked/Rel-18/38_series/38892/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8480dd5e4462be2ad732fcab19450306b528054b --- /dev/null +++ b/marked/Rel-18/38_series/38892/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0ae009ed31af3a7e8a50c803c80d83534e3fc97f90438d017c5979befa75c3e +size 24320 diff --git a/marked/Rel-18/38_series/38892/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/Rel-18/38_series/38892/d26959f4514c26ca19c3d6f00da85956_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3d89df085eefc647adda21ebe5edcadd8d1ac0f3 --- /dev/null +++ b/marked/Rel-18/38_series/38892/d26959f4514c26ca19c3d6f00da85956_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:388d6c2887cc898f499fcc30361b1bd60c07a6e14bdd47031648fd24a123b43a +size 89584 diff --git a/marked/Rel-18/38_series/38892/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-18/38_series/38892/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fe52cc932b6be100eb3694cd1d60616844a9b28a --- /dev/null +++ b/marked/Rel-18/38_series/38892/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a6ecf6120eae30be6fb60e0c67089d69bf75a340b07be7027a1424c589094493 +size 37008 diff --git a/marked/Rel-18/38_series/38892/raw.md b/marked/Rel-18/38_series/38892/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..77e33e6df9da84d9798468062fd740da75b17aab --- /dev/null +++ b/marked/Rel-18/38_series/38892/raw.md @@ -0,0 +1,480 @@ + + +# 3GPP TR 38.892 V18.0.0 (2023-03) --- + +*Technical Report* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; APT600 MHz NR Band ; (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a 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 + +## --- **Keywords** + + + +--- + +## **3GPP** + +## --- **Postal address** + +## --- **3GPP support office address** + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + +--- + + + +## --- **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..... | 5 | +| 2 References..... | 5 | +| 3 Definitions, symbols and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Symbols..... | 6 | +| 3.3 Abbreviations ..... | 6 | +| 4 Background ..... | 7 | +| 5 Frequency band arrangement..... | 8 | +| 5.1 Operating band, channel bandwidth and channel arrangement..... | 8 | +| 5.2 Duplex spacing..... | 9 | +| 6 Compatibility with B71/n71 ..... | 9 | +| 7 UE and BS requirements for APT 600 MHz ..... | 12 | +| 7.1 UE requirements..... | 12 | +| 7.1.1 UE transmitter characteristics..... | 12 | +| 7.1.2 UE receiver characteristics ..... | 12 | +| 7.2 Network nodes requirements..... | 13 | +| 8 Expected Output and Time Scale..... | 14 | +| Annex A: Change history ..... | 15 | + +# --- Foreword + +This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document is a technical report for the work item of APT 600 MHz NR band. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] ETSI EN 300 422-1 (V1.4.2) (2011-08): "Electromagnetic compatibility and Radio spectrum Matters (ERM); Wireless microphones in the 25 MHz to 3 GHz frequency range; Part 1: Technical characteristics and methods of measurement". +- [3] 3GPP TS 36.101: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception". +- [4] 3GPP TS 36.104: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) radio transmission and reception". +- [5] 3GPP TR 36 820, "LTE for 700 MHz digital dividend". +- [6] 3GPP TR 36 755, "US 600 Mhz band for LTE". +- [7] RP 221778, WID on APT 600 MHz band. +- [8] 3GPP TR 38 860, "Study on Extended 600 MHz NR band". +- [9] R4-2215942, "Asymmetric bandwidths for APT 600 MHz", Ericsson. +- [10] R4-2220016, "TP for TR 38.892: n105 compatibility with legacy n71 UEs", T-Mobile USA. +- [11] R4-2300031, "Text Proposals for section 6 of TR 38 892", Spark NZ, Nokia. +- [12] R4-2302457, "TP to TR 38.892: n71 and n105 compatibility (section 6)", Huawei, HiSilicon. +- [13] R4-2302708, "TP for TR 38.892: Compatibility with Band 71/n71", Qualcomm Incorporated. +- [14] RP-223265, "Revised WID on APT 600 MHz NR band", ZTE. + +# 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------| +| $BW$ | Bandwidth | +| $\Delta f$ | Separation between the channel edge frequency and the nominal -3dB point of the measuring filter closest to the carrier frequency | +| $\Delta f_{max}$ | The largest value of $\Delta f$ used for defining the requirement | +| $F_{DL\_low}$ | The lowest frequency of the downlink operating band | +| $F_{DL\_high}$ | The highest frequency of the downlink operating band | +| $F_{UL\_low}$ | The lowest frequency of the uplink operating band | +| $F_{UL\_high}$ | The highest frequency of the uplink operating band | +| $f\_offset$ | Separation between the channel edge frequency and the centre of the measuring filter | +| $f\_offset_{max}$ | The maximum value of $f\_offset$ used for defining the requirement | +| $N_{DL}$ | Downlink EARFCN | +| $N_{Offs-DL}$ | Offset used for calculating downlink EARFCN | +| $N_{Offs-UL}$ | Offset used for calculating uplink EARFCN | +| $N_{UL}$ | Uplink EARFCN | +| $P_{REFSENS}$ | Reference Sensitivity power level | + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|--------|-------------------------------------------------| +| ACLR | Adjacent Channel Leakage Ratio | +| BS | Base Station | +| CBRS | Citizens Broadband Radio Service | +| CIM | Counter-InterModulation | +| CW | Continuous Wave | +| DL | Downlink | +| DTV | Digital Television | +| EARFCN | E-UTRA Absolute Radio Frequency Channel Number | +| eCFR | electronic Code of Federal Regulation | +| EIRP | Effective Isotropic Radiated Power | +| ERP | Effective Radiated Power | +| ETSI | European Telecommunications Standards Institute | +| E-UTRA | Evolved UTRA | +| FCC | Federal Communications Commission | +| FDD | Frequency Division Duplex | +| HAAT | Height Above Average Terrain | +| LA | Local Area | +| LO | Local Oscillator | +| MOP | Maximum Output Power | +| MR | Medium Range | +| MSR | Multi-Standard Radio | + +| | | +|---------|--------------------------------------------| +| NF | Noise Figure | +| NRAO | National Radio Astronomy Observatory | +| NSF | National Science Foundation | +| PA | Power Amplifier | +| PRB | Physical Resource Block | +| RAS | Radio Astronomy Service | +| REFSENS | Reference Sensitivity | +| RF | Radio Frequency | +| RX | Receiver | +| SEM | Spectrum Emission Mask | +| TX | Transmitter | +| UE | User Equipment | +| UHF | Ultra High Frequency | +| UL | Uplink | +| UMTS | Universal Mobile Telecommunications System | +| UTRA | UMTS Terrestrial Radio Access | +| VLBA | Very Long Baseline Array | +| WA | Wide Area | +| WMTS | Wireless Medical Telemetry Service | + +# 4 Background + +The text in this section is largely from the WID [7], [14] + +The 470-694 MHz frequency range is allocated to the broadcasting service and mobile service on a co-primary basis in ITU Region 3. The frequency band 470-698 MHz, or parts thereof, was identified by WRC-15 in 7 countries in Region 3 through new footnote No. **5.296A** for use by those administrations as listed wishing to implement terrestrial IMT systems. In addition, there is interest from other significant markets to do the same. Elsewhere, USA, Mexico and several other countries in ITU Region 2 also identified this band for IMT through footnotes **5.295** and **5.308A**. It is noted that *resolves* 2 of revised Resolution **224 (Rev.WRC-19)** to encourage administrations to take into account results of the existing relevant ITU Radio communication Sector studies, when implementing IMT applications/systems in the frequency bands 694-862 MHz in Region 1, in the frequency band 470-806 MHz in Region 2, in the frequency band 790-862 MHz in Region 3, in the frequency band 470-698 MHz, or portions thereof, for those administrations mentioned in No. **5.296A**, and in the frequency band 698-790 MHz, or portions thereof, for those administrations mentioned in No. **5.313A**. + +Spectrum below 1 GHz is expectedly well suited for mobile broadband applications. In particular, the unique propagation characteristics of the bands below 1 GHz allow for wider area coverage, which in turn requires fewer infrastructures and facilitates service delivery to rural or sparsely populated areas. In this regard, the 700MHz ecosystem is growing swiftly: there are over 34 commercial networks deployments. (see ).The APT700 band plan coming out from Region 3 played a huge role in its success globally. Outside of APAC, countries in Region 2 have adopted or plan to adopt the APT700 band plan (3GPP band 28) for LTE system deployments. The lower duplexer of APT700 plan has also been adopted for Region 1 since the conclusion of WRC-15. + +As the utilisation of the 700MHz spectrum increases over time, it is desirable to look at additional spectrum that could be considered as a companion besides 3GPP Band 28. Therefore, the use of parts of the 600MHz band for the mobile broadband service would provide a vital means of delivering high quality, wide area broadband services including in rural areas and deep inside buildings. The timely availability of frequency arrangements is essential for the development of IMT specifications and standards and the early consideration by Administrations in the footnotes referred to above of suitable frequency arrangements. + +The APT region is very diverse and consists of highly developed and developing countries and some with extremely large and rural population base. The sub 1 GHz bands is well suited for the later. + +During the last year or so, 3GPP RAN 4 has completed a study item on the feasibility of various duplex filter options for use in this band. The results of this study are documented in TR 38.860 [8] This study was sent to the AWG in an LS RP-212629 in Sep 2021 with a request to provide guidance on a preferred band plan and information on regulatory aspects for the normative work to begin. + +The AWG 28 meeting has considered the request of the 3GPP and has provided a response to this LS. In this response the LS has indicated a preference for option B1 (full band)- see Fig 4-1 below, and has also requested for the work to begin immediately with a view to completion by Dec 2022. Additionally, the answers to the regulatory questions sought by the 3GPP have now been provided via a reply LS RP 221045. + +To facilitate the development of additional spectrum in the APT region it is proposed to develop the following band option: + +![Diagram of the proposed band option B1. It shows a frequency spectrum from 612 MHz to 703 MHz. The spectrum is divided into Downlink (612-652 MHz) and Uplink (663-703 MHz) regions, with a gap between them. The Downlink region contains 8 channels, and the Uplink region contains 8 channels. The gap between Downlink and Uplink is shaded.](c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg) + +**B1: full band** + +The diagram illustrates the proposed band option B1. It shows a frequency spectrum from 612 MHz to 703 MHz. The spectrum is divided into Downlink (612-652 MHz) and Uplink (663-703 MHz) regions, with a gap between them. The Downlink region contains 8 channels, and the Uplink region contains 8 channels. The gap between Downlink and Uplink is shaded. + +Diagram of the proposed band option B1. It shows a frequency spectrum from 612 MHz to 703 MHz. The spectrum is divided into Downlink (612-652 MHz) and Uplink (663-703 MHz) regions, with a gap between them. The Downlink region contains 8 channels, and the Uplink region contains 8 channels. The gap between Downlink and Uplink is shaded. + +Figure 4-1: Proposed band option. + +# 5 Frequency band arrangement + +## 5.1 Operating band, channel bandwidth and channel arrangement + +NR band APT600 is designed to operate in the operating band defined in Table 5.1-1. + +**Table 5.1-1: NR operating band for APT600 band** + +| Operating Band | Uplink (UL) operating band
BS receive
UE transmit | | Downlink (DL) operating band
BS transmit
UE receive | | Duplex Mode | +|----------------|---------------------------------------------------------|----------------|-----------------------------------------------------------|----------------|-------------| +| | $F_{UL\_low}$ | $F_{UL\_high}$ | $F_{DL\_low}$ | $F_{DL\_high}$ | | +| n105 | 663 MHz | 703 MHz | 612 MHz | 652 MHz | FDD | + +The requirements in the TR apply to the combination of channel bandwidths, SCS and operating bands shown in Table 5.1-2. + +**Table 5.1-2: Channel bandwidth and SCS parameters for APT600 band** + +| SCS (kHz) | channel bandwidth (MHz) | | | | | | | +|-----------|-----------------------------------------------------------|----|----|----|-----------------|-----------------|-----------------| +| | 5 | 10 | 15 | 20 | 25 3 | 30 3 | 35 3 | +| 15 | | | | | | | | +| 30 | | 10 | 15 | 20 | 25 3 | 30 3 | 35 3 | +| NOTE 3: | This UE channel bandwidth is applicable only to downlink. | | | | | | | + +The channel raster of APT600 band is 100 kHz based (the same as band 71/n71). The applicable NR-ARFCN entries for band n105 are defined in Table 5.1-3. + +**Table 5.1-3: Applicable NR-ARFCN for APT600 band** + +| NR operating band | $\Delta F_{\text{Raster}}$ (kHz) | Uplink range of $N_{\text{REF}}$ (First – – Last) | Downlink range of $N_{\text{REF}}$ (First – – Last) | +|-------------------|----------------------------------|---------------------------------------------------------------|-----------------------------------------------------------------| +| n105 | 100 | 132600 – <20> – 140600 | 122400 – <20> – 130400 | + +The synchronization raster for APT600 band is given in Table 5.1-4. + +**Table 5.1-4: Applicable SS raster entries for APT600 band** + +| NR operating band | SS Block SCS | SS Block pattern (NOTE 1) | Range of GSCN (First – – Last) | +|-------------------|--------------|---------------------------|--------------------------------------------| +| n105 | 15 kHz | Case A | 1535 – <1> – 1624 | + +## 5.2 Duplex spacing + +The default TX channel (carrier centre frequency) to RX channel (carrier centre frequency) separation (default duplex spacing) for NR band n105 as given by Table 5.1-1: NR operating band for APT600 band is 51 MHz as defined in Table 5.2-1. + +**Table 5.2-1: UE TX-RX frequency separation for APT600 band** + +| NR Operating Band | TX – RX carrier centre frequency separation | +|-------------------|---------------------------------------------| +| n105 | -51 MHz | + +# 6 Compatibility with B71/n71 + +Band n71 was introduced for Region 2 during Rel-15 back in 2017, under the LTE600\_US work item [6]. UEs supporting operating band n71 are already on the market. + +Even if it was not the objective of the APT600 band introduction, consideration of band n71 eco-system reuse was recognized during the discussion to be beneficial from both market, and international UE roaming point of view. + +The main difference among band n105 and band n71 is in their frequency arrangement, where duplex spacing of the n105 is 5 MHz larger as compared to band n71, with its DL starting as 612 MHz (compared to 617 MHz for band n71), as detailed in Table 6-1. + +The band plan for Band n105 shares a similar frequency range with that of the existing Band 71/n71, but differs in two important aspects. The first difference is Band n105 enables an additional 2x5 MHz of spectrum for a total of 2x40 MHz whereas Band 71/n71 is only specified for 2x35 MHz. The second difference is that the default Tx-Rx separation between uplink and downlink frequency blocks within Band n105 is 51 MHz while it is 46 MHz for Band 71/n71. + +![Figure 6-1: Frequency band diagrams for Band n71 and Band n105. Band n71 shows a 35 MHz downlink passband (617-652 MHz) and a 46 MHz Tx-Rx separation. Band n105 shows a 40 MHz downlink passband (612-652 MHz) and a 51 MHz Tx-Rx separation. Both bands have 7 channel blocks labeled A-G.](e6df2733626a85205c1db682e6259c46_img.jpg) + +Figure 6-1: Frequency band diagrams for Band n71 and Band n105. Band n71 shows a 35 MHz downlink passband (617-652 MHz) and a 46 MHz Tx-Rx separation. Band n105 shows a 40 MHz downlink passband (612-652 MHz) and a 51 MHz Tx-Rx separation. Both bands have 7 channel blocks labeled A-G. + +Figure 6-1: Band n71 and Band n105 differ in passband bandwidth and Tx-Rx separation. + +Table 6-1: Comparison of n71 and n105 frequency arrangement + +| 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 | +|-------------------|--------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|-------------| +| n71 | 663 MHz – 698 MHz | 617 MHz – 652 MHz | FDD | +| n105 | 663 MHz – 703 MHz | 612 MHz – 652 MHz | FDD | + +Studies have been conducted to explore the possibility of enabling compatibility between Band n105 and Band 71/n71. Specifically, the feasibility and modifications needed to enable existing Band 71/n71 UE's to operate in a network intended for Band n105 was studied. This would be advantageous before Band n105 devices are widely available. In the longer term, it is expected that devices would support both Band n71 and Band n105 [13]. + +One scheme described in [9] proposed to mandate the support of asymmetric UL/DL bandwidths for the Band n105 UE using the same asymmetric bandwidth combination set mandated for band n71 (BCS set 0). A variable duplex was claimed to be a byproduct of the support for asymmetric UL/DL bandwidths since the narrower UL channel could be placed arbitrarily within a frequency range where the fullband UL channel would have resided for a symmetric UL/DL configuration. Not all companies agreed with this interpretation and also observed UE requirements are not tested for variable duplex by virtue of asymmetric channel bandwidth. One example of a configuration is shown below with four 10 MHz symmetric operator blocks. The DL channel bandwidth configured by the BS is wider than the DL operator block. In order to fully allocate all channels within the band for different operators, PRB blanking would need to be used at the network side with active PRBs strictly within the DL operator block aligning to the Band n105 spectrum allocation. This may imply degraded selectivity for UEs and may be also imply coordination between neighboring networks and potential interference across networks if not properly coordinated. The edge spectrum blocks are unusable by Band n71 UE's since they are outside of the range of Band n71 and therefore outside of the Tx and Rx filter passband for the UE. These blocks would only be accessible to Band n105 UE's. + +![Figure 6-2: Diagram illustrating a variable duplex scheme with PRB blanking. It shows a frequency spectrum from 612 to 703 MHz with a center gap at 652-663 MHz. Below, four 10 MHz operator blocks are shown with their respective DL and UL frequencies. The diagram indicates PRB blanking in the n105/n71 cell region and n105 cell only regions. Formulas for F_{DL,n71} and F_{UL,n71} are provided for each block.](1eadbbe42cfcac5c0023577110aec5e3_img.jpg) + +Formulas shown in the diagram: + +- $F_{DL,n71} + \Delta F_{Tx-Rx} = F_{DL,n105} - \Delta F_{Tx-Rx}$ +- $F_{UL,n71} + \Delta F_{Tx-Rx} = F_{UL,n105} - \Delta F_{Tx-Rx}$ + +Figure 6-2: Diagram illustrating a variable duplex scheme with PRB blanking. It shows a frequency spectrum from 612 to 703 MHz with a center gap at 652-663 MHz. Below, four 10 MHz operator blocks are shown with their respective DL and UL frequencies. The diagram indicates PRB blanking in the n105/n71 cell region and n105 cell only regions. Formulas for F\_{DL,n71} and F\_{UL,n71} are provided for each block. + +Figure 2: 2 x 10 MHz operator blocks in n105 with n71 indicated by MFBI in the n71 region. + +Figure 6-2: An example of one variable duplex scheme with PRB blanking + +Another scheme described in [1] proposes to use different configurations depending on whether the channel is located at the bottom, middle, or upper part of Band n105. For channels in the lower part of the band, n71 devices would be configured for symmetric UL and DL using 46 MHz duplex. There is 2x5 MHz blocks which are not accessible to these n71 devices, but might be available to n105 devices using a larger UE specific channel bandwidth configuration with 51 MHz duplex or by intra-band contiguous carrier aggregation using mixed duplex between PCC and SCC. + +![Figure 6-3: An example of another variable duplex scheme for partial coverage with n71 and using channel specific bandwidth configuration or CA for n105. The diagram shows two frequency band representations. The left one shows n71 channels A-G and n105 channels 0-7, with a note 'Requires variable duplex spacing for n105'. Below are boxes for 'License DL', 'SIB1 BW DL', 'Initial BWP', and 'n71 DL'. The right one shows n71 channels A-G and n105 channels 0-7, with boxes for 'License UL', 'SIB1 BW UL', 'Initial BWP', and 'n71 UL'. At the bottom, 'Alt. 1: (requires UE specific channel BW not on the 100 kHz raster)' and 'UE CHBW > SIB1 CHBW' point to 'n105 UE specific channel BW'. 'Alt. 2: UL and DL CA' points to 'DL CA' and 'n105 DL' on the left, and 'n105 UL' and 'UL CA' on the right.](d26959f4514c26ca19c3d6f00da85956_img.jpg) + +Figure 6-3: An example of another variable duplex scheme for partial coverage with n71 and using channel specific bandwidth configuration or CA for n105. The diagram shows two frequency band representations. The left one shows n71 channels A-G and n105 channels 0-7, with a note 'Requires variable duplex spacing for n105'. Below are boxes for 'License DL', 'SIB1 BW DL', 'Initial BWP', and 'n71 DL'. The right one shows n71 channels A-G and n105 channels 0-7, with boxes for 'License UL', 'SIB1 BW UL', 'Initial BWP', and 'n71 UL'. At the bottom, 'Alt. 1: (requires UE specific channel BW not on the 100 kHz raster)' and 'UE CHBW > SIB1 CHBW' point to 'n105 UE specific channel BW'. 'Alt. 2: UL and DL CA' points to 'DL CA' and 'n105 DL' on the left, and 'n105 UL' and 'UL CA' on the right. + +**Figure 6-3: An example of another variable duplex scheme for partial coverage with n71 and using channel specific bandwidth configuration or CA for n105.** + +For channels in the middle and upper part of the band the n71 devices use asymmetric channel bandwidth with DL 5 MHz larger than uplink. The remaining 5 MHz uplink is lost to n71 devices but could be used by n105 devices with UE specific channel configuration or intra-band contiguous UL CA. For this scheme, Band n71 devices are limited in the spectrum available to them. For example, assuming the 2x40 MHz of Band n105 is allocated equally to 4 operators in 2x10 MHz blocks, n71 is only able to access 50% of the spectrum. Band n105 devices can access all of the spectrum, but would need to support UE specific channel bandwidth configurations larger than SIB bandwidth and channel location off of the 100 kHz raster. Or the network would need to be divided into two networks and then recombined using carrier aggregation losing efficiency. + +None of these schemes to enable compatibility of Band 71/n71 devices to a network intended for Band n105 could be agreed. They all have shortcomings, introducing additional requirements in Band n105 UE design and network deployment complexity. At the same time, it is unclear whether the benefit of a Band 71/n71 UE ecosystem – even in a short-term transitional phase – would actually be realizable. The Band 71/n71 UE ecosystem is predominantly composed of devices designed and intended for networks in the US. These devices do not support the bands and CA combinations needed for countries in Asia Pacific or future use of this band in ITU Region 1 where Band n105 is expected to be deployed. Thus, the benefit might only be for US operators and devices roaming into Band n105 for temporary connectivity. The benefit for APT operators and users is limited since these devices would not be useful as home devices native to the n105 countries in the absence of support for the other APT bands. Instead, it is recommended to maximize the use of spectrum in the most efficient manner by developing a Band n105 ecosystem directly. It is anticipated that devices will support both Band n71 and Band n105 using common modem and RF hardware to fulfil market demands. + +Referring to the LS in [12], AWG has indicated that from the UE perspective, the device should ideally support both band n105, as well as n71 for international UE roaming purposes. From roaming point of view, we can distinguish the following cases: + +1. Legacy n71 UE trying to access network operating n105 band: despite lack of -51 MHz duplex support, in this case a legacy n71 UEs would not be able to access downlink on 612-617 MHz, or uplink on 698-703 MHz. +2. n105 UE trying to access n71 network: such n105 UE would need to support -46 MHz duplex spacing; such duplex spacing flexibility was discussed in this work item under term “variable duplex”, but not concluded. As the n71 frequency range is embedded within n105 band, one may expect that some of the future n105 UE implementations may support both bands to enable roaming. + +Considering high level of commonalities among those bands the underlying duplexer designs, it is expected that future UE devices supporting band n71 will also support band n105. Whether this would be achieved with the same RF frontend or not, is an implementation issue. However, possibility of using existing n71 devices with their -46 MHz duplex in n105 markets is not technically feasible with the existing Rel-17 specification. + +Finally, it shall be stressed that APAC region mobile network operators willing to deploy band n105 with -51 MHz Tx-Rx spacing, will not be mandated by their regional regulations to support band n71, which was defined in 3GPP for Region 2 based on FCC guidance. + +The NR bands n71 and n105 have transmit/receive (duplex) spacings of -46 and -51 MHz respectively. Concurrent operation of UEs with both duplex spacings are not considered as this is a short-term measure only according to R4-2302708. Due to the essentially large commonality of the transmitter/receiver requirement for the modem, specifications of n71 and n105 it is expected that new generation n71 UEs and n105 UEs will support both bands. The immediate issue using existing n71 UEs in an n105 market will not be there in the long term. Therefore, it is anticipated that devices will support both Band n71 and Band n105 using common modem and RF hardware to fulfill market demands [11]. + +# 7 UE and BS requirements for APT 600 MHz + +## 7.1 UE requirements + +### 7.1.1 UE transmitter characteristics + +#### 7.1.1.1 UE TX maximum output power + +Power class 3 is specified for Band n105 with a maximum output power of 23 dBm. The tolerance is +2/-2.5 dB similar to Band n71. + +Table 7.1.1.1-1: UE TX maximum output power + +| NR band | Class 1 (dBm) | Tolerance (dB) | Class 1.5 (dBm) | Tolerance (dB) | Class 2 (dBm) | Tolerance (dB) | Class 3 (dBm) | Tolerance (dB) | +|---------|---------------|----------------|-----------------|----------------|---------------|----------------|---------------|----------------| +| n105 | | | | | | | 23 | +2/-2.5 | + +#### 7.1.1.2 NS value and Spectrum Emission Mask + +No additional spurious emission requirements have at this time been identified for Band n105. Therefore, no NS other than the default NS\_01 has been specified. In the future if regulators deem it necessary to impose additional spurious emission requirements to protect adjacent or nearby services for deployment in certain countries, the NS specifications for Band n105 can be revised accordingly. + +The spectrum emission mask follows the general mask as specified in clause 6.5.2.2 of TS 38.101-1. No additional spectrum mask is applicable to Band n105. + +### 7.1.2 UE receiver characteristics + +#### 7.1.2.1 UE REFSSENS + +Reference sensitivity for Band n105 has been agreed as follows + +Table 7.1.2.1-1: UE REFSSENS + +| Operating band / SCS / Channel bandwidth | | | | | | | | | | | | +|------------------------------------------|---------|--------------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------| +| Operating Band | SCS kHz | 5 MHz (dBm) | 10 MHz (dBm) | 15 MHz (dBm) | 20 MHz (dBm) | 25 MHz (dBm) | 30 MHz (dBm) | 35 MHz (dBm) | 40 MHz (dBm) | 45 MHz (dBm) | 50 MHz (dBm) | +| n105 | 15 | -97.2 8 | -94.0 | -91.6 | -86.9 | -85.1 | -83.8 | -82.5 | | | | +| | 30 | | -94.3 | -91.9 | -87.9 | -85.5 | -84.3 | -82.6 | | | | + +NOTE 8: DL channels overlapping the 612-617MHz range have 0.5dB added to the REFSSENS + +#### 7.1.2.2 In-band blocking + +In-band blocking for Band n105 has been specified as Case 1, Case 2, and Case 5. Case 5 is specified with an interferer power of -22 dBm except for Band n105 channels overlapping the lowermost 5 MHz of the band where it is relaxed to -34 dBm. + +**Table 7.1.2.2.-1: In-band blocking for NR bands with $F_{DL\_high} < 2700$ MHz and $F_{UL\_high} < 2700$ MHz** + +| NR band | Parameter | Unit | Case 1 | Case 2 | Case 3 | Case 4 | Case 5 | +|---------|---------------------------|------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|--------|------------------------|-------------------| +| | $P_{interferer}$ | dBm | -56 | -44 | -15 | -38 | -22 4 | +| | $F_{interferer}$ (offset) | MHz | $-BW_{Channel}/2 - F_{Ioffset, case 1}$
and
$BW_{Channel}/2 + F_{Ioffset, case 1}$ | $\leq -BW_{Channel}/2 - F_{Ioffset, case 2}$
and
$\geq BW_{Channel}/2 + F_{Ioffset, case 2}$ | | $-BW_{Channel}/2 - 11$ | | +| n105 | $F_{interferer}$ | MHz | NOTE 2 | $F_{DL\_low} - 12$
to
$F_{DL\_high} + 15$ | | | $F_{DL\_low} - 7$ | + +NOTE 1: The absolute value of the interferer offset $F_{interferer}$ (offset) shall be further adjusted to $(\lceil |F_{interferer}| / SCS \rceil + 0.5) SCS$ MHz with SCS the sub-carrier spacing of the wanted signal in MHz. The interferer is an NR signal with 15 kHz SCS. + +NOTE 2: For each carrier frequency, the requirement applies for two interferer carrier frequencies: a: $-BW_{Channel}/2 - F_{Ioffset, case 1}$ ; b: $BW_{Channel}/2 + F_{Ioffset, case 1}$ + +NOTE 3: n48 follows the requirement in this frequency range according to the general requirement defined in Clause 7.1. + +NOTE 4: For Band n105 channels overlapping the 612 - 617 MHz frequency range, $P_{interferer}$ is modified to -34 dBm. + +#### 7.1.2.3 Out-of-band blocking + +Out-of-band blocking for Band n105 is specified generally as it is for other bands below 2700 MHz. + +**Table 7.1.2.3.-1: Out of-band blocking for NR bands with $F_{DL\_high} < 2700$ MHz and $F_{UL\_high} < 2700$ MHz** + +| NR band | Parameter | Unit | Range 1 | Range 2 | Range 3 | +|---------|-----------------------|------|---------------------------------------------------------------------|---------------------------------------------------------------------------|---------------------------------------------------------------------------------| +| | $P_{interferer}$ | dBm | -44 | -30 | -15 | +| n105 | $F_{interferer}$ (CW) | MHz | $-60 < f - F_{DL\_low} < -15$
or
$15 < f - F_{DL\_high} < 60$ | $-85 < f - F_{DL\_low} \leq -60$
or
$60 \leq f - F_{DL\_high} < 85$ | $1 \leq f \leq F_{DL\_low} - 85$
or
$F_{DL\_high} + 85 \leq f \leq 12750$ | + +## 7.2 Network nodes requirements + +With the introduction on band n105, the following network node specifications were updated to reflect required modifications: + +- NR BS core and conformance testing specifications, +- IAB core and conformance testing specifications, +- NR Repeater core and conformance testing specifications. + +The following technical modifications were implemented, where applicable: + +- Adding n105 to the list of operating bands for Operating Band Unwanted Emission (Category A, and Category B Option 1) limits, +- Transmitter spurious emission requirements: + - co-existence requirements updated for n105 introduction, + - co-location requirements updated for n105 introduction, +- Receiver blocking: co-location requirements updated for n105 introduction. + +# 8 Expected Output and Time Scale + +**Table 8-1: New specifications to be introduced** + +| New specifications {One line per specification. Create/delete lines as needed} | | | | | | +|---------------------------------------------------------------------------------------|--------------|---------------------|------------------|----------------------|---------| +| Type | TS/TR number | Title | For info at TSG# | For approval at TSG# | Remarks | +| Internal TR | 38.892 | APT 600 MHz NR band | | RAN#99 | | + +**Table 8-2: Impacted specifications** + +| Impacted existing TS/TR {One line per specification. Create/delete lines as needed} | | | | +|--------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|----------------------------|------------| +| TS/TR No. | Description of change | Target completion plenary# | Remarks | +| 38.101-1 | NR; UE Radio transmission and reception | RAN#99 | Core part | +| 38.133 | NR; Requirements for support of radio resource management | RAN#99 | Core part | +| 38.104 | NR; BS Radio transmission and reception | RAN#99 | Core part | +| 38.141-1 | NR; Base Station (BS) conformance testing Part 1: Conducted conformance testing | RAN#99 | Perf. Part | +| 38.141-2 | NR; Base Station (BS) conformance testing Part 2: Radiated conformance testing | RAN#99 | Perf. Part | +| 36.104 | E-UTRA; BS Radio transmission and reception | RAN#99 | Core part | +| 36.141 | E-UTRA; BS conformance testing | RAN#99 | Perf. Part | +| 37.104 | E-UTRA, UTRA and GSM/EDGE; Multi-Standard Radio (MSR) Base Station (BS) radio transmission and reception | RAN#99 | Core part | +| 37.141 | E-UTRA, UTRA and GSM/EDGE; Multi-Standard Radio (MSR) Base Station (BS) conformance testing | RAN#99 | Perf. Part | +| 37.105 | Active Antenna System (AAS) Base Station (BS) transmission and reception | RAN#99 | Core part | +| 37.145-1 | Active Antenna System (AAS) Base Station (BS) conformance testing; Part 1: conducted conformance testing | RAN#99 | Perf. Part | +| 37.145-2 | Active Antenna System (AAS) Base Station (BS) conformance testing; Part 2: radiated conformance testing | RAN#99 | Perf. Part | +| 38.174 | NR; Integrated access and backhaul radio transmission and reception | RAN#99 | Core part | +| 38.176-1 | NR; Integrated Access and Backhaul (IAB) conformance testing; Part 1: Conducted conformance testing | RAN#99 | Perf. Part | +| 38.176-2 | NR; Integrated Access and Backhaul (IAB) conformance testing; Part 2: Radiated conformance testing | RAN#99 | Perf. Part | +| 38.106 | NR repeater radio transmission and reception | RAN#99 | Core part | +| 38.115-1 | NR; Repeater conformance testing - Part 1: Conducted conformance testing | RAN#99 | Perf. Part | + +# Annex A: Change history + +| Change history | | | | | | | | +|----------------|-------------------|------------|--------|-----|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | C
R | Rev | Cat | Subject/Comment | New version | +| 2022-08 | 3GPP RAN4#104e | R4-2211530 | | | | TR skeleton | 0.1.0 | +| 2022-08 | 3GPP RAN4#104e | R4-2211532 | | | | Text Proposals to the TR, for sections 2, 3, and 4. | 0.1.0 | +| 2022-10 | 3GPP RAN4#104ebis | R4-2217125 | | | | Text Proposals to the TF, for section 5.1 | 0.2.0 | +| 2022-11 | 3GPP RAN4#105 | R4-220486 | | | | Text Proposals to the TR for section 5.2 | 0.3.0 | +| 2022-11 | 3GPP RAN4#105 | R4-2219860 | | | | Text Proposals to the TR for section 7.2 | 0.3.0 | +| 2023-03 | 3GPP RAN4#106 | R4-2300029 | | | | TR 38.982 update to include expected output and time scale at section 8 | 0.4.0 | +| 2023-03 | 3GPP RAN4#106 | R4-2303726 | | | | Revised TP for TR 38.892: Compatibility with Band 71/n71 (R4-2303697)
TP for section 6, B71/n71 compatibility ( R4 2302457)
TP for section 6 B71/n71 compatibility ( R4-2300031)
TP for section 7.2 BS RF requirements ( R4-2302458)
TP for section 7.1 UE requirements ( R4-2302707)
TP for section 6 B71/n71 compatibility ( R4 23027080) | 0.5.0 | +| 2023-03 | RP-99 | RP-230059 | | | | TR 38.892 as submitted to RAN #99 for 1-step approval | 1.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2023-03 | RP-99 | | | | | 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/38893/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38893/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a399dfb2f6f7df7debabfd3ddf56142621ed1b05 --- /dev/null +++ b/marked/Rel-18/38_series/38893/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:62027005016414782efe29c6df95770365c15b659d0cf8c32631006c0923e03a +size 9599 diff --git a/marked/Rel-18/38_series/38893/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38893/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45534320803a5a02d188b5902b843c218c2f7590 --- /dev/null +++ b/marked/Rel-18/38_series/38893/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7557ff9f874f5f2b58dbdb934a1c86a8b74e30135d552eb3bccf674d867633bf +size 5797 diff --git a/marked/Rel-18/38_series/38893/raw.md b/marked/Rel-18/38_series/38893/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a1f0954b55909251109da41c0f45cb5b5c0282ad --- /dev/null +++ b/marked/Rel-18/38_series/38893/raw.md @@ -0,0 +1,306 @@ + + +# **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on UE support of regionally-defined subsets of an NR band (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller 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 + +## **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 ..... | 6 | +| 3.1 Terms..... | 6 | +| 3.2 Symbols..... | 6 | +| 3.3 Abbreviations ..... | 6 | +| 4 Root cause..... | 7 | +| 5 Other Issues..... | 8 | +| 5.1 Roaming UEs ..... | 8 | +| 6 Possible solutions ..... | 8 | +| 6.1 General ..... | 8 | +| 6.2 Solution A: New Band introduction for sub-band ..... | 8 | +| 6.3 Solution B: New Band Number ..... | 9 | +| 6.4 Solution C (reuse existing NR band number, new signalling)..... | 10 | +| 7 Conclusions and recommendations..... | 11 | +| Annex A (informative): Change history..... | 12 | + +# 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 + +3GPP defines specifications that are applicable worldwide including the definition of NR frequency bands across both FR-1 and FR-2 frequency ranges. In general, 3GPP seeks to enable economies of scale and commonality of bands across multiple countries and regions around the globe. This can lead to bands with very wide bandwidth to be able to capture the frequency ranges within this band that might be available within different countries. Hence, the band definitions are not necessarily tailored to the frequency ranges available in any one country but may be broad enough to enable applicability across many countries. In addition, mechanisms such as NS signaling have been introduced in RAN4 specifications to enable the network to indicate additional or unique country or deployment-specific requirements on top of the general requirements associated with the band. + +In order for a UE to declare support of a band, it must support the entire band including all of the general requirements as well as all NS requirements specified for this band. Consequently, the UE is able to operate on the band in any country where this band or portion thereof is deployed while also meeting any country specific requirements or regulations that may be applicable. However, it has been observed recently that there are situations where the UE can only operate on one or more subsets of the band within a particular country. This was reported for Band n77 first in the US and then again in Canada. In both of these cases, Band n77 was defined as a very wide band with global applicability, but the regulators in the US and in Canada only made available portions of the band for mobile usage. Moreover, different portions of the band were made available at different times, so there was the possibility that UE's might support one or more-than-one subset of the band depending on when the UE was designed, manufactured, and/or certified with respect to the timing of spectrum release and regulations in the country. To be clear, to meet 3GPP requirements, the UE must support the entire band. However, the situation described above pertains to regulatory compliance rather than compliance to 3GPP requirements. If the UE is not certified by a country's regulator to operate on a certain part of the band, irrespective of what is specified in 3GPP, the UE is not allowed to operate on that part of the band in the country. + +Specific solutions were identified and specified for Band n77 to resolve the issues related to spectrum subsets in the US and Canada. However, it is anticipated that issues such as this may become more commonplace and therefore a RAN level study item to consider a more generalized solution was agreed. This technical report captures the contents of the study item. + +# 1 Scope + +The present document captures the study on UE support of regionally-defined subsets of an NR band. In accordance with 3GPP specifications, a UE is required to support the entire frequency range of a band as defined by [2], [3], or [4]. However, it was found that for some bands, there may be regional regulatory restrictions to this frequency range in some countries. The scope of this study is to investigate the root causes that may require 3GPP specification changes to accommodate as well as to consider possible general solutions if needed. + +# 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-1: "User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone". +- [3] 3GPP TS 38.101-2: "User Equipment (UE) radio transmission and reception; Part 2: Range 2 Standalone". +- [4] 3GPP TS 38.101-5: "User Equipment (UE) radio transmission and reception; Part 5: Satellite access Radio Frequency (RF) and performance requirements". + +# 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]. + +| | | +|-----|-------------------------| +| DOD | Department Of Defense | +| MPR | Maximum Power Reduction | + +# 4 Root cause + +The first step of this study item is to identify root causes using Band n77 in the US and Canada as an example. + +The regulatory bodies of some countries limit device certification to the designated spectrum and limit operation of certified devices to that designated spectrum. This has not created issues for 3GPP because usually there were regulations for an entire band when spectrum was licensed and because regional spectrum allocations seldom change. The introduction of very wide bands, e.g., 900 MHz wide NR band n77, created a situation where regulations existed for only part of the band in some countries. For example, in the United States, initially 3700-3980 MHz was available for mobile services, auctioned in December 2020, but other parts of n77 were not available at that time. In order to be able to certify devices, Note 12 was added to 38.101-1 Table 5.2-1, which read: + +"NOTE 12: In the USA this band is restricted to 3700 – 3980 MHz". + +The problem with this solution was that there was no plan to handle the situation where additional spectrum in n77 would become available for licensing. Later, when 3450-3550 MHz became available to be auctioned in October 2021, assignment of a new 3GPP band for the 3450-3550 MHz frequency range was considered, but it was decided in 3GPP that re-use of n77 was a more expedient course for incorporating the additional US allocation. The note was therefore modified as follows: + +"NOTE 12: In the USA this band is restricted to 3450 – 3550 MHz and 3700 – 3980 MHz." + +But this led to a situation where early US FCC certified devices would only operate on 3700-3980 MHz and not on 3450-3550 MHz. Roaming UEs not certified for 3450-3550 MHz in the US might attempt to access that part of the band, but such UE behaviour was not specified so concerns were raised that the gNBs needed to know if the UE was allowed to operate in that part of the band for handovers and CA configuration. To inform the gNB if the UE supported 3450-3550 MHz in the US, a new UE capability was introduced: extendedBand-n77-r16. However, concerns were also raised that a roaming UE that did not indicate extendedBand-n77-r16 might attempt to access 3450-3550 MHz, causing confusion and potentially negative consequences. To prevent a UE that does not indicate extendedBand-n77-r16 from accessing 3450-3550 MHz in the US, a new NS value (NS\_55) was created. Where normally NS values indicate additional emissions requirements for a band, in this case NS\_55 is used to bar UEs that do not support extendedBand-n77-r16 from accessing 3450-3550 MHz in the US. + +There is a similar situation in Canada, where the initial licensed spectrum was 3450-3650 MHz was auctioned in June 2021 and then 3650-3980 MHz is expected to be auctioned in Early 2023. + +It should be noted that while the UE only supports a part of the band in certain countries, e.g., the US and Canada in the above examples, the UE still shall support the entire band when roaming to other countries to be compliant with 3GPP requirements. + +The root cause of the issue requiring UE band subset support is summarized by the combination of the factors listed below + +1. A regional regulator makes an initial frequency allocation of portions/subsets of the 3GPP band, i.e., not including the entire band +2. The region requires UE certification for all UEs operating within the borders of the region. +3. The regional certification only applies to the frequency allocation at the time of certification. +4. The UE must confine its operation to the frequency band for which it was certified. +5. The regional regulator subsequently allocates other portions/subsets of the band [and/or regulations change within the existing sub-bands]. +6. Newer UEs are certified for both the original allocation and subsequent allocations. + +This combination of factors leads to different UEs supporting different subsets of the band. The network needs to be able to distinguish between these different UEs to enable efficient handover and SCell/PsCell activation. + +# --- 5 Other Issues + +## 5.1 Roaming UEs + +In some countries it is neither the operator nor the base station that takes responsibility for the UE meeting regulations. In the USA UE vendors can only allow their devices to operate in parts of the band where there are FCC regulations at the time of device certification. + +UE vendors may choose to pursue certification for some countries but not others. In view of the regional regulatory differences described above, we recognize that there may be ambiguity with regards to exactly which regulatory requirements are supported in any given UE implementation. It is important to understand how this ambiguity could affect regulatory compliance when UEs roam in countries in which they are not certified. Two scenarios are identified for clarification for feasibility of roaming: + +- The first scenario is if a UE is certified to operate only in part of a band (e.g. band n77 cases UE in Canada/US). In this scenario, the UE is only allowed to operate within the subset of the band for which it is certified in the country where this certification is necessary. Because the UE in addition to the above regulatory certification is also compliant to 3GPP requirements (e.g., for Band n77), it is required that the UE can support the entire band. Therefore, this UE when roaming to a country which does not have any regional regulatory requirements shall be able to operate on the entirety of the band. If this country does have regional requirements, the UE shall abide by them to operate in this country. +- The second scenario is if a UE can support the frequency range of a band based on the 3GPP requirements but not certified for additional regional requirements in a subset of the band in a certain foreign country. This aspect has to be evaluated for each country based on prevailing regulation. Whether the roaming UE is allowed to operate without certification from the country's regulator is subject to each country's laws. + +# --- 6 Possible solutions + +## 6.1 General + +The solutions in clause 6 should be at least capable of solving the issues indicated in clauses 4 and 5. Moreover, solutions should be applicable for handling existing UEs which were already deployed in the market before the introduction of new regionally-defined subsets of an NR band or new released regulation. + +Regarding all solutions, considering accommodations for cases where the UE subset support precludes the possibility to test some MSD exceptions: If the UE supported subset precludes the possibility to test some MSD exceptions, just like with Note 12 for n77 either the MSD configuration can be changed so the MSD is testable in the country that uses the sub-band or a note can be added to waive the MSD. + +## 6.2 Solution A: New Band introduction for sub-band + +Introducing a new band is a well-known technique for RAN4, which has been used to differentiate between different (sub-)bands or portions thereof in 3GPP specifications. For instance, Band 26/n26 are supersets of Band 5/n5, and Band 25/n25 are supersets of Band 2/n2. Also, Band 19/n19 are regional subsets of Band 5/n5. These new bands have separate band combinations and separate RF requirements, including different refsens and MSD. However, in the case of Band 26 and 25, the superset bands were introduced in 3GPP after the smaller B5 and B2 were in the specification, so it is not quite the same situation as with Band n77, where there is an existing wider band, but a need for a regional sub-band. + +One downside of introducing a new band for a regional sub-band is that new band combinations are required for the new bands. This can create significant workload for RAN4 because of the redundant effort. Also, RAN4 would need to specify all of the requirements for the sub-band including RF and performance requirements. + +The use of new bands for regional sub-bands would provide a means to limit access to spectrum in a region that only has regulations for the sub-band, but it could lead market fragmentation if vendors introduce UEs that only support the new regional band, and not the wider full band. + +## 6.3 Solution B: New Band Number + +Another potential solution is to introduce a new band number, which is not a new band. The difference between solution A (a new band) and solution B (a new band number) is that all the same RF and performance requirements of the original band (i.e. parent band) should apply to the new band-number without generating new requirements with respect to existing system, RF, RRM and demodulation requirements (i.e., "parent" bands requirements), but the new band number would allow for differentiation of which part of the spectrum a UE is certified to operate in the region. All the band combinations that apply to the parent band would also apply to the new band number. One example of a new band number is n90, which is identical to n41 and applies the same requirements except that n90 also supports the 100 kHz raster and the 7.5 kHz uplink shift. There are no band combinations defined for n90 because all the n41 combinations apply to n90 also. In the case of n90, the new band number was more of a capability signalling mechanism to allow the network to identify UEs that support the 100 kHz raster and 7.5 kHz shift, and bar n41 only UEs that don't support those features. + +For regional sub-bands, the new band number can be thought of more as a signalling mechanism used to allow or bar devices based on support for a particular part of the band. It is similar to the extendedBand-n77-r16 / NS\_55 solution, except that it uses existing UE capability signalling and barring and does not require any new network signalling. + +An example of how this would work is that at some point in time 3300-3450 MHz might become available in the USA for Mobile use. If this spectrum does become available, then a new band number could be allocated to indicate that a UE supports 3300-3450 MHz, as well as 3450-3550 and 3700-3980 MHz, in the US. Only the new band number would be signalled from cells in the new frequency range in the US so that only UEs that support the new band number would attempt to access 3300-3450 MHz in the US. Also, when the gNB examines the UE capabilities, it would know if the UE supports 3300-3450 MHz in the US based on if it reports support for the new band number or not in its UE capabilities. + +The benefits of the new band number approach are: + +- No new RAN2 signalling needed as new parts of the band become available. +- No new NS values required for barring UEs +- Only to change the semantics of 3GPP frequency bands and need 3GPP clarification + +There are many available band numbers (i.e. 107 out of 1024 have been used so far for NR), so there is no concern on the band numbers shortage. + +3GPP would pro-forma select a new band number based on regional frequency allocations within an existing 3GPP band, the existing band being referred to as the parent band. + +If the network wants to avoid that a legacy device supporting only the parent band (but not indicating support for the new band number) will camp on a cell in the new sub-band, the network can indicate only the new band number on cells in the new sub-band. In this manner the technique of a new band number should prevent UEs which are not compliant to the requirements of the new sub-band from camping on or accessing the cell in such a sub-band. And the gNB sees from UE capabilities the bands and band numbers that the UE supports and hence the gNB knows if the UE can be handed over to a cell in the new sub-band. + +The new band number would apply the RF requirements from the parent band. It assumes that there is no dedicated sub-band hardware for the UE such as RF filters to be utilized for the new band number. Whether the sub-band corresponding to a new band number may include previously (chronologically) introduced sub-bands of the same parent band. This is to be considered case by case and depending on different factors (e.g., whether sub-bands are defined within the same geographical region. To avoid market fragmentation and to support UE roaming, it should be mandated that the new band number can only be supported by a UE which also supports the associated parent band. If a UE including, roaming UEs, is not certified to operate in new band number based on regional regulatory certification, the UE shall not advertise the new band number in its capabilities nor shall it attempt to connect to a cell broadcasting this new band number. + +In current practice, adding a new band triggers introduction of new band combinations, which would add many new band combinations to the specification and UE capability signalling. By contrast, adding a new band number, such as when n90 was added, does not require new band combinations, but rather text stating that combinations for the parent band apply to the new band number. Furthermore, inter-band or intra-band CA is determined with consideration of the parent band and not the sub-band(s). To ensure that UE capability signalling is not adversely impacted by the number of supported band combinations, this technique requires that the new band number corresponding to the new sub-band has a reference to the parent band for signalling carrier aggregation (CA) and dual-connectivity (DC) band combinations. + +NOTE 1: It should be studied further whether a UE shall report band combinations for the parent and sub-bands, and if not, which specification impact it will have. + +NOTE 2: The introduction of a new band number should not have impact on the parent band. + +NOTE 3: Any other optimizations based on new band number approach are not precluded. + +This technique should require no new signalling and can work for any release UEs, but it does change the semantics of 3GPP frequency bands and 3GPP should clarify the association between a new band number and their parent band in signalling requirements. If the new band number approach is applied, 3GPP RAN4 should: + +- Ensure that the number of new band number definitions does not exhaust the range of possible band numbers: Rel-17 signaling supports 1024 NR band numbers, or which 104 are assigned in Rel-17. Exhaustion of the range of band numbers is not anticipated to be an issue. + +## 6.4 Solution C: Reuse existing NR band number, new signalling + +With this solution, the existing NR band is re-used, but there is also explicit signalling for different regions – either from the UE to the network, from the network to the UE, or both – providing further information to the communicating entities regarding which sub-bands are supported. Hence for the sake of clarity we will focus separately on potential options for signalling for both communication sides. + +The premise for introduction of signalling from the network to the UE can prevent legacy UEs from camping on particular sub-bands which they do not support. The easiest way to accomplish this is to define new NS value associated with the corresponding band. With this approach the network broadcasting new NS value can be always sure that a legacy UE will not camp on a particular sub-band. It does not matter how many sub-bands are added and in which release – as long as every sub-band is associated with a particular NS value, the network remains in controls of permissible cells for camping destinations. + +As for the UE to the network signalling, one of the main reasons to have it is to provide the network with additional information regarding which sub-bands a UE supports to facilitate network sub-band selection for re-direction and handover procedures. This information on supported sub-bands can be implemented in at least the following ways (not precluding other options): + +- **Option A:** The UE capability is implemented as an explicit capability in the UE capability container, whereupon it can be as simple as one bit or something more versatile. Since such a generic UE capability does not exist, RAN WG4 will need to contact RAN WG2 every time such a capability is needed (as it already happened with the DOD-band). To reduce such issues, a generic approach (as illustrated by the next alternative) could be preferable +- **Option B (via e.g., *modifiedMPR-Behaviour* field bitmap or a new bitmap):** This approach is logically identical to the previous alternative, with the difference being that instead of asking RAN WG2 to define a new capability for each new sub-band, a more generic signalling is used, which can be defined as per-band signalling and whose content can be defined by RAN WG4. Two options below are examples of how it can be accomplished. + - a) One option is that the existing capability *modifiedMPR-Behaviour* can be leveraged for this purpose. The *modifiedMPR-Behaviour* can already be signalled for every band not requiring any RAN WG2 changes. Since it is up to RAN WG4 to define the purpose and meaning of every value of that field, UE can use this capability to indicate supported sub-bands based on meaning defined in RAN4. However, this would be changing the original intent of this capability since it relates to MPR, not to sub-bands, and Repurposing the existing capability may create unforeseen issues. + - b) Another option is to include a new band subset indication to UE capabilities. In this proposal, the parent 3GPP band designation may be followed by an indicator which identifies which sub-allocation of the band applies to the region in question. From the signalling perspective this approach is similar to *modifiedMPR-Behaviour* described above, but a new dedicated capability would be defined by RAN2 WG2, content of which will be further specified by RAN WG4. This proposal avoids the issue of parent-band association, but at the cost of defining new signalling. + +As an example, the solution adopted for band n77 was a combination of the following elements: + +- UE-to-NW signalling: defining the explicit UE capability indications (extendedBand-n77-r16 and extendedBand-n77-2-r17); and +- NW-to-UE signalling: defining new value NS\_55 and NS\_57 for barring UE access to the sub-bands. + +# --- 7 Conclusions and recommendations + +The study item has reviewed possible responses to situations in which regional regulatory bodies may allocate subbands of the existing 3GPP bands in a phased fashion. In these cases, UEs may be certified for different subsets of the 3GPP band(s) and must therefore operate only within the subbands for which certification has been received. Further, networks should not attempt to redirect these UEs to frequencies not in the subbands for which certification has been received. Different proposals for ensuring these behaviours are documented herein. + +For band standardization issues which arise from cases where regionally-defined subbands do not occupy an entire 3GPP band, we offer the following conclusions. + +Solutions A, B or C are valid approaches which could be used to solve the problem with the regional sub-bands. Solution B is expected to have a lower standardization workload and hence, should be adopted over Solution A if no issues are identified. However due to related workload, it is recommended that solution B with applying the same requirements (i.e., "parent" band requirements), is preferred over solution C if this approach is confirmed by the working groups. Which method (e.g., new band number, new NS flag, new band, etc.) is chosen for a particular band can be decided on a case by case basis under a dedicated work item. + +RAN2 and RAN4 should fully evaluate the specification, implementation, and test impacts of the new band number approach during the first work item associated with a regionally-defined subband and adopt an appropriate solution based on their evaluation. + +Finally, it is recommended that care should be taken to ensure that the UE behaviour is predictable when operating within the regionally-defined subband and when the UE is operating in the parent band when it in a location where the regionally-defined subband is not applicable. + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|---------|-----------|----|-----|-----|------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-09 | RP-97e | RP-222221 | - | - | - | Skeleton TR for 38.893 | 0.0.1 | +| 2022-09 | RP-97e | RP-222681 | - | - | - | Add content on root cause and other issues | 0.1.0 | +| 2023-03 | RP-99 | RP-230339 | - | - | -- | TR 38.893 as submitted to RAN #99 for 1-step approval | 1.0.0 | +| 2023-03 | RP-99 | RP-230815 | - | - | - | TR 38.893 as submitted to RAN #99 for 1-step approval | 1.0.1 | +| 2023-03 | RP-99 | - | - | - | - | TR 38.893 as approved by RAN #99 (incl. alignments with 3GPP drafting rules) | 18.0.0 | \ No newline at end of file